[OpenSER-Users] NAT question

Papadopoulos Georgios geop at altectelecoms.gr
Thu Aug 2 13:27:06 CEST 2007


Hello all,
 
I need some advice from all you NAT experts. Assume that we have two
OpenSER proxies serving two different domains and they both use
nathelper. Also assume that their configuration is identical and looks
roughly like:
 
route {
...
        record_route();
 
        if (nat_uac_test("23")) {
                if (method!="REGISTER" &&
!is_present_hf("Record-Route")) {
                    fix_nated_contact();
                }
        }
 
        t_on_reply("1");
}
 
onreply_route[1] {
        if (nat_uac_test("23")) {
                fix_nated_contact();
        };
}

clientA and clientB are both behind NAT. clientA at domainA sends an INVITE
to clientB at domainB through proxyA:
 
clientA at domainA  -----> ProxyA -----> ProxyB ------> clientB at domainB
 
ProxyA detects that clientA is behind NAT and fixes the contact. ProxyB
finds the Record-Route header, so it does not fix the contact. My
question is about how to handle the 200 OK. With this configuration both
proxies detect that clientB is behind NAT and the contact gets fixed
twice. Is there a way to avoid this?
 
thank you
 
George
 
 
 
 

Disclaimer
The information in this e-mail and any attachments is confidential. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately. Unless you are the intended recipient or his/her representative you are not authorized to, and must not, read, copy, distribute, use or retain this message or any part of it. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20070802/06d0b117/attachment.htm>


More information about the sr-users mailing list