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

[Kevin P. Fleming]

On 06/01/2012 02:20 AM, Saúl Ibarra Corretgé wrote:

>>
>> This is why I've proposed this set of changes; I'd much rather fail that
>> session setup completely than respond with such a broken answer. The
>> changes required to respond with a non-broken answer are significantly
>> more invasive than what I've proposed and would certainly not be
>> candidates for existing release branches. They *may* make it into
>> Asterisk 11, but they aren't on the current 'committed work' list
>> (primarily because it's rare that these problems affect calls, except
>> when unusual endpoints are in use).
>>
> I see. Do you have numbers in how big the impact would be? I mean, if people prepared their stacks to be gentle in what they receive but now Asterisk just rejects their offer that would be a bad thing IMHO.

No, I don't know of any way to arrive at such numbers. That's why I 
started this thread, to get feedback from people in the community who 
are/might be aware of real interop issues this change might cause.

At this point, I'm of the opinion that the ignore/reject changes should 
not go into the release branches, but should go into trunk (which will 
become Asterisk 11).

-- 
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