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

Andrew Kohlsmith akohlsmith-asterisk at benshaw.com
Wed May 31 08:39:30 MST 2006


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.



More information about the asterisk-dev mailing list