[Asterisk-Dev] ast_xxx function..?

[Matt Hess]

Kevin P. Fleming wrote:
> Matt Hess wrote:
> 
>> I didn't quite follow your meaning.. if my patch breaks rfc 
>> conformance it would not be included is what I think you are saying.
> 
> 
> Actually, what I meant was that if the patch was intended allow a 
> non-conforming device to communicate with Asterisk, but it would reduce 
> performance for conforming devices, then we would probably not accept it.

I agree.. it would allow a rfc-broken device to function properly and on 
that reason alone should not be done. As a counter-point to that.. 
doesn't asterisk put in stuff to inter-operate better with other almost 
rfc compliant devices?

> 
> MikeJ has already commented on this properly; if the existing code is 
> trying to strip quotes from the value but not successful, then we need 
> to fix that. If the device is actually sending a string containing a 
> quote as part of the nonce, then it is broken :-)

I guess my first step then is to display the nonce value being claimed 
as stale.


> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mhess.vcf
Type: text/x-vcard
Size: 288 bytes
Desc: not available
Url : http://lists.digium.com/pipermail/asterisk-dev/attachments/20050930/51100c13/mhess.vcf