On Wed, 2005-11-02 at 10:32 +0000, Michael Procter wrote:
> Jeroen van Bemmel wrote:
>
> > IMO the proper abstraction here would be an object
> > representing a "call attempt", not a call id. It is recommended
> > to use new Call-ID and From-tag for each authentication attempt
> > (see authentication examples draft)
Not so - the tag should not change.
RFC 3261 section 8.1.1.4 Call-ID:
... Note that when requests are retried after certain
failure responses that solicit an amendment to a request (for
example, a challenge for authentication), these retried requests are
not considered new requests, and therefore do not need new Call-ID
header fields; see Section 8.1.3.5.
and then section 8.1.3.5 Processing 4xx Responses:
Certain 4xx response codes require specific UA processing,
independent of the method.
If a 401 (Unauthorized) or 407 (Proxy Authentication Required)
response is received, the UAC SHOULD follow the authorization
procedures of Section 22.2 and Section 22.3 to retry the request with
credentials.
[...]
In all of the above cases, the request is retried by creating a new
request with the appropriate modifications. This new request
constitutes a new transaction and SHOULD have the same value of the
Call-ID, To, and From of the previous request, but the CSeq should
contain a new sequence number that is one higher than the previous.
--
Scott Lawrence tel:+1-781-938-5306;ext=162 or sip:[EMAIL PROTECTED]
Consulting Engineer - Pingtel Corp. http://www.pingtel.com/
sipXpbx project coordinator - SIPfoundry http://www.sipfoundry.org/sipX
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
