[asterisk-dev] RFC: chan_sip SDP parsing changes in behavior

Kevin P. Fleming kpfleming at digium.com
Wed May 30 09:52:47 CDT 2012

On 05/30/2012 08:34 AM, Olle E. Johansson wrote:
> 30 maj 2012 kl. 15:08 skrev Kevin P. Fleming:
>> On 05/30/2012 07:46 AM, Olle E. Johansson wrote:
>>> I don't understand the reason for this.
>> The reason for this is to reduce the likelihood of partially broken calls getting setup (in addition to improving the ability of Asterisk users to be able to diagnose SDP parsing issues).
>>> Instead of rejecting the call - why not reject the media stream if there are other media streams we do support?
>> That's certainly an option, but since the SDP-related data structures in chan_sip don't currently have any way to represent the scenarios that I outlined in my message, chan_sip cannot properly construct a response that declines those media streams. The code changes required to do that would be much more extensive and definitely wouldn't be a candidate for release branches.
> It would break a lot of installations.
> I would not do this in a release, especially not a LTS.

Can you give me an example (or two, or more) of an installation that 
would be 'broken' by this set of changes? All of the proposed changes 
are for exceptional cases that should rarely, if ever, occur in a 
properly configured endpoint.

Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming at digium.com | SIP: kpfleming at digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org

More information about the asterisk-dev mailing list