Hi Ahmed,
The two "c" is a perfectly legitimate case - the first one is the
per-session session (affecting all streams), the second is per stream
(affecting only the current stream, the 'm' line).
So, your device is buggy, not respecting the SDP RFC.
Try using the "c" flag in both offer/answer :
/ c/ - flags to change the session-level SDP connection (c=) IP if
media-description also includes connection information.
http://www.opensips.org/html/docs/modules/2.4.x/rtpproxy.html#func_rtpproxy_engage
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit 2019
https://www.opensips.org/events/Summit-2019Amsterdam/
On 03/13/2019 09:32 PM, Ahmed Shabana wrote:
Dears, First sorry it you received the below content of this email with wrong
subject
The issue we face with some of our sip peers complaint that we sent in our SDP
contains two 'c='
v=0.
o=- 1552491282093 1 IN IP4 192.168.104.200.
s=Our Local Private Media Server.
c=IN IP4 **192.168.104.200.**
t=0 0.
m=audio 36356 RTP/AVP 8 0 101.
c=IN IP4 **Public.Interface.RTPPRoxy.**
a=sendrecv.
a=rtcp:36357 IN IP4 Public.Interface.RTPPRoxy.
a=ptime:20.
a=rtpmap:0 pcmu/8000.
a=rtpmap:101 telephone-event/8000.
a=rtpmap:8 pcma/8000.
I am using RTPProxy inside the script just like below
rtpproxy_offer("nt60T60", "$avp(advertised_address)", "$avp(mediaSet)",)
rtpproxy_answer("ocnt50T50", "{{ ips.opensips }}","$avp(mediaSet)" , ) ;
how could I hide private IPs in above SDP that reach our trunk side ?
Best regards ,
Shabana
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
