Thanks for the information, that seems to at least change the Via, but RTPproxy is still not handling this well. It will only give it's private IP back to OpenSIPS, so I end up wtih:
Connection Information (c): IN IP4 10.250.7.164 I will try and see if I can work around this on the RTPproxy side of things. -dg On Wed, Oct 7, 2009 at 2:10 PM, Bogdan-Andrei Iancu <bog...@voice-system.ro> wrote: > Hi Daniel, > > try using the advertise_address and advertise_port to force opensips in > using the public IPs of the NAT: > http://www.opensips.org/Resources/DocsCoreFcn#toc24 > > Regards, > Bogdan > > Daniel Goepp wrote: >> I am trying to setup OpenSIPs to run behind a firewall, and not >> finding much information regarding how to get OpenSIPs to be aware of >> the public IP for it's signaling. The firewall is setup with a 1 to 1 >> NAT for the public and private IPs, and right now all udp and tcp >> traffic is being passed directly through. Has anyone successfully >> gotten OpenSIPs setup like this? If so, can you please provide any >> information on how it was setup. >> >> TIA >> >> -dg >> >> _______________________________________________ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
