[Serusers] Nathelper/Rtpproxy not working for two natted clients

[Greger V. Teigre]

Vivienne,

>From your config: 

       if (nat_uac_test("3")){

                if (method == "REGISTER" || ! search("^Record-Route:")){

                        log("Log: Someone trying to register from private IP,rew

riting\n");

            fix_nated_contact(); #Rewrite contact with source IP

                        if (method == "INVITE"){

                                fix_nated_sdp("1"); #Add direction=active to SDP

                        };

                        force_rport(); # Add rport parameter to topmost Via

                        setflag(6); # Mark as Nated

                };



Here you don't proxy the call, you just add the direction=active.  If you want to rtp proxy the calls, you need to have a force_rtp_proxy() for the initial INVITE.  Read section 1 of the Getting Started document at ONsip.org to understand what is supposed to happen and how to read the SDP payload and see the rtpproxy example found in the document.  

Your config will process the OK and proxy the rtp stream from the callee, but not the caller's.

g-)


---- Original Message ----
From: Vivienne Curran
To: serusers at lists.iptel.org
Sent: Thursday, March 31, 2005 05:55 PM
Subject: [Serusers] Nathelper/Rtpproxy not working for two natted
clients 

> Hi,
> 
> I am having problems troubleshooting a problem I am experiencing with
> my SER configuration. I have ser 0.8.14 running with rtpproxy and
> nathelper enabled. I have two phones on the same subnet behind nat
> and I would like to make a call between the two. I want to invoke
> rtpproxy for this as they both have private address [I know this
> isn't the most efficient way as they're both on the same subnet but I
> can worry about that later].      
> 
> When I ring from the phone 1 (2092) to phone 2 (2093), 2092 can hear
> voice but 2093 can't. When 2093 ring 2092, there's no audio. These
> phones are Grandstream BT100's. They have been configured to listen
> on different SIP and RTP ports.   
> 
> 2092: SIP Port: 5060
> 2092: RTP Port: 5004
> 2093: SIP Port: 5061
> 2093: RTP Port: 5005
> 
> I have included my ser.cfg file the messages received on my SER
> server (using ngrep SIP-q)in an attachment. I can confirm that my
> rtpproxy is working (originally I thought it wasn't) by using "strace
> -d <rtpproxy  pid> -f -F". I can see a signal being returned.   
> 
> Any help would be appreciated or advise as to how I can proceed
> troubleshooting. 
> Kindest Regards,
> Vivienne.
> Send instant messages to your online friends
> http://uk.messenger.yahoo.com 
> 
> 
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050404/34d35b49/attachment.htm>