[SR-Users] RTPPROXY & BRANCH

marino.mileti at alice.it marino.mileti at alice.it
Tue Sep 23 10:35:42 CEST 2014


Hi 

I've a problem with rtpproxy during a parallel ring scenario.
I've two client behind NAT (192.168.10.20 & 192.168.10.50) and when I try to call them in parallel mode (ringall) rtpproxy module sends in to the INVITE the same RTP ports.

Is it possible to manage rtpproxy in order to generate a couple of new port for each branch?

My rtpproxy string in the kamailio conf (in manage branch section):
 
rtpproxy_manage("bFAIE","192.168.10.10");


Brief extract of 2 SIP INVITE message send by kamailio to natted clients:

192.168.10.10 --> 192.168.10.20
User Datagram Protocol, Src Port: sip (5060), Dst Port: 6090 (6090)
Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:1001 at 192.168.10.20:6090 SIP/2.0
Message Header
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): 1004 1476 1657 IN IP4 192.168.10.10
Session Name (s): Talk
Connection Information (c): IN IP4 192.168.10.10
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 62910 RTP/AVP 111 110 0 8 101
Media Description, name and address (m): video 47160 RTP/AVP 102
Media Attribute (a): nortpproxy:yes


192.168.10.10 --> 192.168.10.50
User Datagram Protocol, Src Port: sip (5060), Dst Port: 6090 (6090)
Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:1002 at 192.168.10.50:6090 SIP/2.0
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): 1004 1476 1657 IN IP4 192.168.10.10
Session Name (s): Talk
Connection Information (c): IN IP4 192.168.10.10
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 62910 RTP/AVP 111 110 0 8 101
Media Description, name and address (m): video 47160 RTP/AVP 102
Media Attribute (a): nortpproxy:yes

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20140923/c812b8eb/attachment.html>


More information about the sr-users mailing list