Simon, It's possible that RTPengine is replacing both payload specific and session level c lines. Does your downstream SDP contain a session level c line ? >From the documentation it sounds like rtpengine might be introducing one.
On Fri, Nov 15, 2024, 4:18 AM Simon Gajski via Users < [email protected]> wrote: > Hi > > We are doing a SIP interconnection with one of carriers that sends us > Invite with SDP where "c=IN" parameter is defined twice. > v=0 o=- 33593 33593 IN IP4 172.29.1.2 s=- *c=IN IP4 172.29.3.4* t=0 0 > a=sendrecv m=audio 36440 RTP/AVP 8 18 96 *c=IN IP4 172.29.3.4* b=RR:0 > b=RS:0 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=yes > a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=maxptime:40 > > We are using opensips 3.4.2 with rtpengine 10.5.0.0 to act as SBC > Problem is that when opensips forwards such INVITE to next hop, rtpengine > changes accordinly only second line of 'c' parameter, resulting in no media. > > I never ran into duplicate line of 'c' param in SDP. > > My question: Is it possible to remove one of duplicated lines before > rtpengine handles it or if anyone knows how to process both lines in > rtpengine? > Carrier is one of national telcos and won't remove it. So I need to figure > out how to solve it on our side. > > Thank you for any tip > > BR > Simon > _______________________________________________ > 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
