Re: [Serusers] Nathelper/RTPProxy not working for agents behind NAT

Dear Vivienne, I wrote the rtpproxy section, so I'll respond for Paul. See inline. g-) ---- Original Message ---- From: Vivienne Curran To: Java Rockx ; serusers(a)lists.iptel.org Sent: Friday, April 01, 2005 12:25 PM Subject: Re: [Serusers] Nathelper/RTPProxy not working for agents behind NAT Please note that the example in the document is based on the setup (figure) found at the beginning of the document. The tests done to detect NAT will match for your two private clients as they will have private addresses. Thus, calls between the two will be proxied even though it is not necessary (as I believe you want). The nat_uac_test() function can be modifed to do other tests if you have some knowledge (due to registration or other processing) about whether the caller/callee is NATed or not. As to the Grandstream config, there is no need to have them listen on different ports as they will have different IP addresses. Do you register to SER with the server's public IP address or the private? If you use the public, SIP messaging will go through your NAT and if you have a SIP ALG (application layer gateway), it will attempt to change the addresses to public for the phone using port 5060 and (maybe) not for the one using 5061. The simplest is to use the private address in the Grandstream phones as SIP server address. The Getting Started document is built on 0.9.0, which will shortly be released as stable (according to the core team). The has_totag() can be found in the uri module. Please verify that have the latest rtpproxy.cfg file as there were a couple of issues with an early version. I recommend that you download the 0.9.0 Getting Started source package on http://onsip.org/ and forget about 0.8.14 unless you have some very special reasons for not doing so. Regards, Greger