Comments inline...

Thanks,
Nataraju A B
 
> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of kavitha menneni
> Sent: Friday, May 23, 2008 6:17 PM
> To: [email protected]
> Subject: [Sip-implementors] Refresher not received in 
> session-expires headerof 200OK for INVITE
> 
> Hi,
>   I have a query regarding the Session Timer. Please find the 
> call flow below and let me know what should be he UAC and UAS 
> Behavior.
> 
>   INVITE( Session-Expires:  120;refresher=uas) |  
> |-------------------------------------------------------------
> -------------------->|
>  |                     100  Trying                            
>                     |
>  
> |<------------------------------------------------------------
> ---------------------|
>  |                     180                                    
>                       |
>  
> |<------------------------------------------------------------
> ---------------------|
>  |                     200  (Session-Expires:  1800)           |  
>  
> |<------------------------------------------------------------
> ---------------------|
>  |                     ACK                                    
>                     |
>  
> |-------------------------------------------------------------
> ------------------->  | .Here though the RFC says "The UAS 
> MUST set the value of the refresher parameter in 
> theSession-Expires header field in the 2xx response". 200Ok 
> is received with our refresher parameter but INVITE has set 
> the refresher as uas.
> 
> Can any one suggest what should the UAC should perform here - 
> 1. Set the Refresher to Local i.e uac and perform the Refreshes.
> 2. Keep the refresher as uas itself and do not perform the 
> refreshes and send    the BYE after session expiry.
[ABN] UAS is little bit violating the rfc4021 mandation, but for UAC
perspective, it would be better to accept this call and go on...
Probably decide to go with refresher as UAC is a better option...
Specifying refresher=uas in INVITE request is a query, but not a
mandation. Anyway there is definitely no need for disconnecting the
call...

> 
> 
>        
> ---------------------------------
>  Best Jokes, Best Friends, Best Food. Get all this and more 
> on  Best of Yahoo! Groups.
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> 

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

www.wipro.com

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

Reply via email to