[OpenSIPS-Users] rtpengine 12.5.1.16 complains of "Incomplete SDP specification"

Pyle, Jeff JPyle at fusionconnect.com
Tue Jan 21 17:34:25 UTC 2025


Hello,

I have a user with a Cisco Cube sending traffic to OpenSIPS 3.4 with media handled by rtpengine 12.5.1.16. An example SDP from them is:

    v=0
    o=CiscoSystemsSIP-GW-UserAgent 3885 101 IN IP4 172.16.0.13
    s=SIP Call
    c=IN IP4 172.16.0.13
    t=0 0
    m=audio 33032 RTP/AVP 0 101
    c=IN IP4 172.16.0.13
    a=rtpmap:0 PCMU/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=ptime:20
    a=inactive
    m=video 0 RTP/AVP 255
    c=IN IP4 172.16.0.13
    a=inactive
    a=label:11
    a=content:main
    m=application 0 RTP/AVP 255
    c=IN IP4 172.16.0.13
    a=inactive

This is offered in-dialog, probably when they put a call on hold. So ugly. Still, though, can you tell me why rtpengine declares this an "Incomplete SDP specification"? I'll need to find some way to handle it with OpenSIPS and rtpengine.

I fire the following command today from OpenSIPS to handle this request:

  rtpengine_offer("ICE=remove address-family=IP4 RTP SDES-no DTLS=no replace-origin no-rtcp-attribute endpoint-learning=immediate NAT-wait")

I'm interested only in the audio stream (this is an audio-only call). I'm considering supplementing the rtpengine_offer() with sdp-media-remove options to leave only the audio stream in the SDP, removing the m=video and m=application streams. What would the rtpengine_offer() command look like to do that? Something like:

  rtpengine_offer("... sdp-media-remove-video sdp-media-remove-application")

?



Regards,
Jeff

This message is subject to Fusion Connect, Inc.'s email communication policy: www.fusionconnect.com/email-policy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250121/43f2a48f/attachment-0001.html>


More information about the Users mailing list