[asterisk-dev] [Code Review] Make sure that a declined media stream ends in '\r\n'

Matt Jordan reviewboard at asterisk.org
Mon Jan 28 13:37:38 CST 2013

This is an automatically generated e-mail. To reply, visit:

Review request for Asterisk Developers, Mark Michelson and kmoore.


r369028 updated chan_sip's processing of media streams in an SDP to better handle multiple offered media streams. Part of that change modified how streams were declined. Previously, declined streams were not handled in an RFC compliant manner - in Asterisk 11, we now set the port number to 0 in the media stream definition and proceed on with the next media stream.

Unfortunately, the formatting of the declined media stream forgot to append a '\r\n' to the end of the media stream. This is normally added to the accepted media streams later on in the processing of the SDP. Since the declined media stream uses a different buffer than the accepted media streams (and is a malloc'd buffer as opposed to a struct ast_str), it's easier to just put the '\r\n' in the declined media stream buffer rather than attempt to append it later on.

This addresses bug ASTERISK-20908.


  /branches/11/channels/chan_sip.c 380249 

Diff: https://reviewboard.asterisk.org/r/2297/diff


Patch fixed the problem for the issue reporter. Prior to the patch, X-Lite 3.0 would reject the call and log a "ParseException dereferenced ParseBuffer eof" in its debug log - post patch, it works.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130128/3ec31e41/attachment.htm>

More information about the asterisk-dev mailing list