[asterisk-dev] [PATCH] Silently drop non-conformingcirpack keep-alive packets

[James Greasley]

My two pence worth is that the core product should not cater for vendor
bugs.
What happens when those bugs are solved or, worse, change?
Does this affect the stability of the core product and cause more problems
than it first solved etc etc

J

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Andrew Kohlsmith
Sent: 31 May 2006 16:40
To: asterisk-dev at lists.digium.com
Subject: Re: [asterisk-dev] [PATCH] Silently drop non-conformingcirpack
keep-alive packets

On Wednesday 31 May 2006 11:16, Kevin P. Fleming wrote:
> No, this is completely invalid behavior on their part. We cannot make
> code changes to check for this stuff when it is completely outside the
> specs.

I think that that is a poor stance on interoperability.  Every vendor I can 
think of (Cisco and Lucent, ok I haven't thought too hard) has options for 
workarounds.

This was discussed on #asterisk-dev earlier this week.  Something like 
"stupidvendorinterop=0x00000501", with each bit defining one stupid or odd 
workaround needed for some vendor.

Obviously not all options would be valid together, but having the ability to

add workarounds for vendors (even unsupported) can only help.

-A.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev