[asterisk-dev] Improving how Asterisk handles forked SIP requests.

[David Vossel]

----- Original Message -----
> From: "Klaus Darilion" <klaus.mailinglists at pernau.at>
> To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
> Cc: "Olle E. Johansson" <oej at edvina.net>
> Sent: Tuesday, July 20, 2010 2:45:44 AM
> Subject: Re: [asterisk-dev] Improving how Asterisk handles forked SIP requests.
> I just checked the RFC but could not find a detailed description how
> the
> 2nd request should be constructed. I only found:
> 
> If a UA receives a Proxy-Authenticate header field value in a 401/407
> response to a request with a particular Call-ID, it should
> incorporate credentials for that realm in all subsequent requests
> that contain the same Call-ID. These credentials MUST NOT be cached
> across dialogs; however, if a UA is configured with the realm of its
> local outbound proxy, when one exists, then the UA MAY cache
> 
> So, it seems that a nonce is correlated with a call-id. So, in case of
> incoming forked call, why not sending back the same nonce on both
> branches?

I don't see how sending the same nonce in response to both branches will benefit us here.  Will my method of requiring the rURI of the incoming Request containing authentication credentials match the previous supplied rURI work?  I don't see any reason why the rURI should be allowed to change.

David Vossel
Digium, Inc. | Software Developer, Open Source Software
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org
The_Boy_Wonder in #asterisk-dev