New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inactive video stream: can't find media IP in the message #3406
Comments
This should be addressed in rtpengine, BUT https://datatracker.ietf.org/doc/html/rfc8866#name-connection-information-c A session description MUST contain either at least one "c=" line in each media description or a single "c=" line at the session level. It MAY contain a single session-level "c=" line and additional media-level "c=" line(s) per-media-description, in which case the media-level values override the session-level settings for the respective media. |
Thanks for point to the RFC, that's great for my ticket to Audiocodes :-) Still we do not have any possibilities on our side. Am I right that the only possibility Kamailio offers is to do it with textops? Still very difficult to check with regex:
This is bad. But I see the point: yes! It is the others fault. |
@schoberw: maybe you can sort it out with the body line cursors: You can also take in consideration to process the body in Lua, JS or Python, via Kemi exports (you can do inline execution of a script, not full replacement of routing blocks with kemi). I am going to close this one, based on the links to rfc. Further discussions can be done on sr-users mailing list. |
Description
In some situations the other side UA must reply with an inactive media stream. E.g. if video was added but not supported by the other side. The UAS then must answer with an m=video 0 RTP/.. line.
It seams that the video section must contain a c= line with an IP address for rtpengine to function. If there is no c line (no IP address) the SDP body cannot be parsed and thus no RTP proxy is invoked.
Troubleshooting
Not easy to reproduce since the answer must bei "wrong". Is it correct to reply an SDP body (media = video) like this?
Maybe not (but Audiocodes SBC lates LTS version does it) - so we are dependent on other side now that this service works.
Reproduction
reInvite with Video to a UA that has no video Support (e.g. Bria -> Snom). Drop the c line in the video part with some textops in 200 OK (just to reproduce of course).
A -> B, connect the call
A -> + video, B has no video support
A presses hold
Log Messages
Incoming 200 OK after doing hold with an inactive video:
Compare to working SDP parsing:
Possible Solutions
Tried to fix in script:
But since sdpops cannot parse it cannot remove the buggy media, too. See the log: non of the xlog is logging.
If there is inactive media the c line is not mandatory. The parser should accept this by adding a default IP of 0.0.0.0, if needed
Doing tricks with textops is not a easy nor performant solution to accept this wrong SDP from other parties.
Additional Information
Debian Bullseye
The text was updated successfully, but these errors were encountered: