Hi,
  thanks for your timely suggestions.

Regards,
TR Naidu.

-----Original Message-----
From: Martin Larochelle [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 03, 2006 12:39 AM
To: Ramesh Tellapati
Cc: [email protected]; Reddaiah Tellapati
Subject: Re: [Sip-implementors] Nonce expired .... keep SUBSCRIPTION
alive !!

Ramesh Tellapati wrote:

>Hi,
>   
>    1. My initial SUBSCRIBE with 300 seconds expires is successfully
accepted my 
>       SIP Server.
>    2. On the same dialog, my first refresh SUBSCRIBE is sent after 270
seconds (but 
>       with expires 300 seconds) to keep my SUBSCRIPTION active. It is
successfully 
>       accepted by SIP Server.
>    3. On the same dialog, my second refresh SUBSCRIBE is sent after
540 seconds
>        (270 seconds  + 270 seconds). Proxy is responding with "401
Unauthenticated". 
>        When I examined the log messages at Server, I understand that
nonce is 
>        expired.
>  
>
I would imagine that the 401 response contains a WWW-Authenticate header
that contains a new nonce and perhaps a stale=true parameter.


>    4. Am I supposed to send second refresh without authentication
information sothat
>         Server respond with "401 Unauthenticated" ?
>  
>
Yes, you should include that last used authentication information,

>    5. Do I have to pick the updated nonce from the "401
Unautheticated" response and 
>          construct refresh SUBSCRIBE with this new nonce ? 
>  
>
 when you receive a challenge with a new nonce, you build new 
authentication information. Then you send a new request, with 
incremented CSeq, with this new Authorization header.

>    6. Is there any other standard based approach to keep my
SUBSCRIPTION active at 
>       Server ?
>   
>
Not that I know of.

-- 
Martin Larochelle
Software Developer
Macadamian Technologies
martin AT macadamian.com
(613) 739-5976 ext.149
www.macadamian.com

The information contained in this email is intended by Macadamian
Technologies Inc. for the use by the named individual or entity to which
it is addressed and may contain information that is privileged or
confidential. It is not intended for transmission to, or receipt by, any
individual or entity other than the named addressee expressly permitted
in this email. If you have received this email in error, please delete
it without copying or forwarding it, and notify the sender.


_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to