[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    Re: [Sip-implementors] 202 for subscribe
From:       "Sanjay Sinha \(sanjsinh\)" <sanjsinh () cisco ! com>
Date:       2007-07-25 21:10:55
Message-ID: 8983EC086A9D954BA74D9763E853CF3E0397AEEC () xmb-rtp-215 ! amer ! cisco ! com
[Download RAW message or body]

Yes and then look for the expires parameter in initial Notify and adjust
the timer accordingly 

>-----Original Message-----
>From: sip-implementors-bounces@lists.cs.columbia.edu 
>[mailto:sip-implementors-bounces@lists.cs.columbia.edu] On 
>Behalf Of Shankarachar Subramanya-a22587
>Sent: Wednesday, July 25, 2007 1:08 PM
>To: sip-implementors@lists.cs.columbia.edu
>Subject: [Sip-implementors] 202 for subscribe
>
>Hi,
>        When we get 202 for subscribe it doesn't mean that the 
>subscription has been created at the notifier, but should we 
>take the expires timer value in the 202 message and start the 
>expiration timer at the subscriber side..? 
> 
>Regards,
>Subramanya
>_______________________________________________
>Sip-implementors mailing list
>Sip-implementors@lists.cs.columbia.edu
>https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>


[prev in list] [next in list] [prev in thread] [next in thread]