[SR-Users] rtpproxy_manage and ip addresses [SOLVED]

[tonchek at mac.com]

SOLVED.

Solution: 

r - flags that IP address in SDP should be trusted. Without this flag, rtpproxy ignores address in the SDP and uses source address of the SIP message as media address which is passed to the RTP proxy.

Anton

On 13 Jun 2014, at 21:44, tonchek at mac.com wrote:

> HI to ALL!
> 
> As I understand the logic of rpproxy_manage work, it uses packet source IP and port number from m= field of SDP as socket for rtpproxy process.
> So, we can see it in SIP and  rtpproxy debug messages:
> 
> IP 77.94.133.231.5060 > 77.94.133.232.5060: UDP, length 1170
> 
> [...headers stripped...]
> 
> v=0
> o=root 1523540081 1523540081 IN IP4 188.40.66.75
> s=Asterisk PBX 1.6.1.20
> c=IN IP4 188.40.66.75
> t=0 0
> m=audio 15260 RTP/AVP 8 0 101
> 
> [...sdp stripped...]
> 
> Jun 13 21:38:09 puma rtpproxy[4728]: INFO:handle_command: new session on a port 57680 created, tag FppNrF9K7S8gF;1
> Jun 13 21:38:09 puma rtpproxy[4728]: INFO:handle_command: pre-filling caller's address with 77.94.133.231:15260
> 
> where 172.22.11.16 is SIP packet source IP address and 17646 is the port number from SDP.
> 
> Is it possible to change this behavior and use IP address from incoming SDP as well as port number?
> 
> Thank you
> 
> Anton
> 
> 
> 
> 
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

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