My approach was covered here: http://openser.org/pipermail/users/2008-September/000473.html
Will use record_route_preset(public vs. private) in our logic, and change back the value of advertised address back to the private IP for local traffic to route logically.... Thanks Again Bogdan! Nick. On 3/19/13, Nick Khamis <[email protected]> wrote: > Hello Bogdan, > > Thank you so much for your response. We did have an RR problem that > did not allow for an "ACK" to our "200 OK". Our solution was to change > "advertised_address" to use the public IP instead of the local net, > which seemed to get the RR problem solved. The server related global > parameters we are using are as follow: > > alias=<public ip> > auto_aliases=no > disable_dns_failover=yes > sip_warning=no > > port=5060 > listen=udp:192.168.2.5:5060 > advertised_address=<public ip> > > This got the external ACK responses to our 200, but only one way audio > (probably RTP proxy related, and started a new message for that > issue). > > The question is, Should I change "advertised_address" back to private > IP, and use "record_route_preset" instead? In the meanwhile, I will > try it. > > Nick. > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
