If you want 2 NATed devices to talk to each other, you MUST use an RTP proxy (except you want to manually configure the NAT router of every participant).
Sessions between one public and one NATed client might work depending on the used SIP applications. Therefore, using an RTP proxy as soon at least one client is behind NAT is suggested!
It's very simple, take a look at the config script at: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/etc/nathelper.cfg?r...
This will show you how to test if user agents are behind a NAT, how to rewrite the SIP messages and how to integrate the RTP proxy.
Note: NAT traversal using RTP proxies and the nathelper module works only if the SIP client is symmetric (=sending and receiving on the same port, SIP and RTP).
regards, Klaus
-----Original Message----- From: Pablo Murillo [mailto:ser@rednet.com.ar] Sent: Thu 11.12.2003 21:20 To: serusers@lists.iptel.org Cc: Subject: [Serusers] Totally lost! proxies, firewalls, gateways, etc, etc,etc ... Hi
I'm totally lost I have ser working very well (at least, I think so), with ans_machine (sems), varius exec_dset, numbering, etc, etc, etcBut I Don't know (or found) how to solve the "connectios" troubles
For example:
Two devices (hard/soft phone) with public IP, NO PROBLEM, works OK On device with public, one with private IP, works some times, NOT allways Two device with private IP, never work :(
I know where is the problem (IPs), but I don't know where to find a "soft" solution or a "hard" solution, NOT to expensive
Stun server Vovida: I don't like product without docs Some knows other STUN server ?
RTP_proxy: I can't understand how it works :( I tested with nat, but I can't understand how it's work For example, how can I choose who will need to use nat helper and who not ?
I don't know what other solutions are there
Ideas ?
Thanks in advance Pablo Murillo
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Thanks Klaus, but ...
If, I use RTP proxy all the traffic would go through my server or am I mistaken?
----- Original Message ----- If you want 2 NATed devices to talk to each other, you MUST use an RTP proxy (except you want to manually configure the NAT router of every participant).
Sessions between one public and one NATed client might work depending on the used SIP applications. Therefore, using an RTP proxy as soon at least one client is behind NAT is suggested!
It's very simple, take a look at the config script at: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/etc/nathelper.cfg?r...
This will show you how to test if user agents are behind a NAT, how to rewrite the SIP messages and how to integrate the RTP proxy.
Note: NAT traversal using RTP proxies and the nathelper module works only if the SIP client is symmetric (=sending and receiving on the same port, SIP and RTP). --------------------------------
Pablo Murillo
On Dec 12, 2003 at 12:06, Pablo Murillo pm@rednet.com.ar wrote:
Thanks Klaus, but ...
If, I use RTP proxy all the traffic would go through my server or am I mistaken?
Yes, all the RTP traffic will go through your RTP proxy. The ideea is to do this only when necessary. From ser.cfg you should "force" RTP proxy usage only if the caller, the callee or both of them are behind a symmetric nat. You can try to get arround nat with STUN and fall back to RTP proxy only for UAs which don't support it or are behind symmetric nats (if STUN is used the sip packets will contain the nat public address, so they will look like "normal" not-behind-nat UAs).
Andrei
On Friday 12 December 2003 10:13, Andrei Pelinescu-Onciul wrote:
On Dec 12, 2003 at 12:06, Pablo Murillo pm@rednet.com.ar wrote:
Thanks Klaus, but ...
If, I use RTP proxy all the traffic would go through my server or am I mistaken?
Yes, all the RTP traffic will go through your RTP proxy. The ideea is to do this only when necessary. From ser.cfg you should "force" RTP proxy usage only if the caller, the callee or both of them are behind a symmetric nat. You can try to get arround nat with STUN and fall back to RTP proxy only for UAs which don't support it or are behind symmetric nats (if STUN is used the sip packets will contain the nat public address, so they will look like "normal" not-behind-nat UAs).
Right. For example in our network we always ship out units to our customers, preconfigured for STUN or Port Forwarding. I neither is possible then we set them for our RTPProxy. Right now we only have about 5% of our users going through the RTPProxy. And we are quite happy with that! Before we had the RTPProxy we had to turn those customers away.
Andres http://www.telesip.net
Andrei
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers