-----Original Message-----
From: Paul Kyzivat [mailto:[EMAIL PROTECTED]
Sent: Monday, September 27, 2004 7:29 PM
To: Nataraju Alilaghatta (WT01 - TELECOM SOLUTIONS)
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Sip-implementors] Session Timer question
Using UAC and UAS to identify the parties gets ambiguous when there is
more than one transaction involved. To clarify, lets say that the dialog
was established by A inviting B. At that time it was agreed to establish
a session timer, and that the UAC (A) would be responsible for
refreshing at time T1.
My interpretation is that *every* reINVITE (and UPDATE) refreshes (or
else cancels) the session timer. So the reinvite sent B will determine
the status of the session timer going forward. Any old obligation on the
part of A to refresh at time T1 will be removed. It is possible that the
result will be a *new* obligation on the part of A to refresh, at some
new time, T2.
So if A and B want an ongoing session timer for as long as they have a
dialog, then both have to work to maintain it. In this case, B must
again specify the need for the session timer in its reinvite.
[Nataraju A.B.] Right, I am not telling UAS could send reInvite before
initial invite been completed. But what I meant was that reInvite sent
by either party must be considered as session refresh request... here I
assume the reInvite carries the earlier negotiated SE value if session
timer needs to be there for that particular session.
Paul
[EMAIL PROTECTED] wrote:
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
Christina
> Zhao
> Sent: Monday, September 27, 2004 9:07 AM
> To: [EMAIL PROTECTED]
> Subject: [Sip-implementors] Session Timer question
>
> Hi, I have a question for Session Timer:
>
> If uac is the refresher and it receives a "real re-INVITE" (not for
> session refresh) from UAS right before the uac is going to send the
> session refresh request, what should the uac do in this case? Should
> it still send the Invite/Update as scheduled? Or should it wait till
> the "real re-INVITE" transaction is finished?
>
> [Nataraju A.B.] I feel UAC should have updated the session timer value
> once it had received the re-Invite from the UAS even though UAC was
> negotiated to be the refresher. Because even the re-Invite from UAS
does
> serve the purpose of session refresh. Basically the refresh timer
needs
> to be restarted (by refresher) once we receive the re-Invite from
other
> entity also...
>
> Note: it's my personal feeling only; I am not very sure whether this
> fact had been documented in any section of the draft...
>
> Thanks in advance for any advice.
>
> Christina.
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
>
>
> Confidentiality Notice
>
> 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 confidential
or privileged information. If
> you are not the intended recipient, please notify the sender at Wipro
or [EMAIL PROTECTED] immediately
> and destroy all copies of this message and any attachments.
>
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
Confidentiality Notice
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 confidential or privileged
information. If
you are not the intended recipient, please notify the sender at Wipro or [EMAIL
PROTECTED] immediately
and destroy all copies of this message and any attachments.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
