<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>configure SER to work as a gateway</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Hello all,<BR>
<BR>
Solved the installation problem I had, now I am trying to configure SER in a certain way.<BR>
My configuration is the following one:<BR>
<BR>
Client ------------------------- SER ---------------------------- Server/Proxy<BR>
192.168.x.x 192.168.x.y 10.1.x.x 10.1.x.y<BR>
<BR>
Unlike the normal case where SER is used as the Registrar, my client (in a private LAN) must register in a Server/Proxy<BR>
and SER has to act as a SIP gateway. However, at the same time, SER has to register locally this client (for internal calls).<BR>
<BR>
So, put in other words, SER should forward the REGISTER message (directed from the client to the Server/Proxy) and save locally the<BR>
location of that client. Once registered the user, SER should act as a transparent proxy.<BR>
<BR>
But in the practice, it does nothing if I put that the client registers in the Server/Proxy. The messages reach SER but it does not<BR>
forward them, nor it registers locally the clients.<BR>
So I tried configuring the client to register in SER instead of the Server/Proxy and then SER started to work.<BR>
<BR>
Is a listening problem? What I have to include to the ser.cfg so SER handles also messages which are not directed to it but to the Server/Proxy?<BR>
I hope somebody could help me.<BR>
<BR>
Thanks in advance,<BR>
Rebeca Martinez<BR>
</FONT>
</P>
</BODY>
</HTML>