[Asterisk-Dev] ast_xxx function..?

[Matt Hess]

Chris St Denis wrote:
> Possible workaround if only a few clients are affected by this non-RCF
> compliant problem. Route them through a SER server the sole purpose of which
> it to strip the quotes with the textops module. Don't know if it'll work but
> it's a potential solution. 
> 

Unfortunately, the majority (90%) of cpe we have is from one vendor (AC) 
and routing them all through a ser server does not feel like an elegant 
solution in this circumstance.. granted, that a band-aid fix is not 
elegant either.. but my belief is that it sure has less potential to be 
customer affecting.. which is why I was turning to the avenue of just 
stripping the "<sp> out at the asterisk level. I figured a simple check 
on the nonce to ensure it has no nastification (and if so scrub it 
clean) is more efficient in the end.

Also, I do have a trouble ticket open with AC on this issue and have 
complained that it is a service affecting bug (shh, not really but it 
would be if I was to upgrade to 1.2-beta/head).. no ETA has been given 
for when a fix will be supplied but they do recognize that this is a 
bug. My estimated ETA on their fix: Soon.

Let me take a minute to say thank you for the feedback I've received, it 
has been very positive.

(there is no sP^Hoon)


> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com
> [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Kevin P. Fleming
> Sent: Friday, September 30, 2005 3:05 PM
> To: Asterisk Developers Mailing List
> Subject: Re: [Asterisk-Dev] ast_xxx function..?
> 
> Matt Hess wrote:
> 
> 
>>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?
> 
> 
> Yes, but only when it doesn't cause a performance penalty or maintenance 
> burden.
> 
> 
>>I guess my first step then is to display the nonce value being claimed 
>>as stale.
> 
> 
> Sounds like a good idea!
> _______________________________________________
> 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
> 
> _______________________________________________
> 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/1a83f99b/mhess.vcf