Creating a separate sofia profile just for this gateway definitely works, just wondering whether there is a cleaner solution. The register-proxy params seems to do something very similar..

On Sun, Jun 21, 2009 at 1:39 PM, Jan Kubr <jan.kubr@gmail.com> wrote:
I have found this: http://jira.freeswitch.org/browse/MODENDP-184
Thanks to which I know that adding    

 <param name="outbound-proxy" value="78.24.13.197"/>

 to the profile XML does almost what I need. Is it possible to configure outbound proxy per gateway though?

Cheers,
Jan

On Sun, Jun 21, 2009 at 1:04 PM, Jan Kubr <jan.kubr@gmail.com> wrote:
We have a SIP gateway behind NAT which I haven't been able to set up
to work with Freeswitch. The configuration I thought would work is:

<include>
 <gateway name="nat">
   <param name="username" value="user"/>
   <param name="password" value="pass"/>
   <param name="realm" value="11.12.13.10"/>
   <param name="proxy" value="78.24.13.197"/>
 </gateway>
</include>

This, however, sends

REGISTER sip:78.24.13.197;transport=udp SIP/2.0

whereas I need

REGISTER sip:11.12.13.10;transport=udp SIP/2.0

When I set "register-proxy" to the public address (78.24.13.197) and
comment the "proxy" param out, it successfully registers. Though any
other SIP messages are sent to 11.12.13.10 which obviously fails.

Basically what I need Freeswitch to do is to send everything to the
public address, but put the private one everywhere in the SIP
messages. How do I do this?

Thanks,
Jan