---
> >> From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-
> >> implementors-boun...@lists.cs.columbia.edu] On Behalf Of Paul Kyzivat
> >> Sent: Wednesday, July 22, 2015 1:52 PM
> >> To: sip-implementors@lists.cs.columbia.edu
> >> Subject
lumbia.edu
Subject: Re: [Sip-implementors] No Session Expire Header in 200 OK
I generally agree with what Tarun is saying, but have one clarification
On 7/22/15 1:39 PM, Tarun2 Gupta wrote:
Hi
Please refer Section 7.2 of RFC 4028.
If the UAS did not include a SE header in 200 OK response, it mean
.cs.columbia.edu [mailto:sip-
> implementors-boun...@lists.cs.columbia.edu] On Behalf Of Paul Kyzivat
> Sent: Wednesday, July 22, 2015 1:52 PM
> To: sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] No Session Expire Header in 200 OK
>
> I generally agree with
I generally agree with what Tarun is saying, but have one clarification
On 7/22/15 1:39 PM, Tarun2 Gupta wrote:
Hi
Please refer Section 7.2 of RFC 4028.
If the UAS did not include a SE header in 200 OK response, it means that it
does not want / support session expiration. In this case, UAC ca
Hi
Please refer Section 7.2 of RFC 4028.
If the UAS did not include a SE header in 200 OK response, it means that it
does not want / support session expiration. In this case, UAC can perform
refreshes but for its own benefit only. UAC should behave as if the 200 OK
response contained refresher
Dear All,
I need your help to understand a logic behind the session expires.
My doubt is.
--> Invite have "session-expire" header in Invite (from UAC to UAS)
--> UAS did not included "session-expire" header in 200 OK to the
correspondence of initial invite.
1) So in this case what we should as
