Hi George,

each proxy should fix what it detects. ProxyA will take care of the traffic related to A (since it detects A as NATed) and ProxyB should take care of traffic for B (as it sees B as nated). So, the 200 OK must be fixed only by proxyB.

Regards,
bogdan

Papadopoulos Georgios wrote:
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. [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> sends an INVITE to [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> through proxyA: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -----> ProxyA -----> ProxyB ------> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 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.

------------------------------------------------------------------------

_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users

Reply via email to