[SIPForum-discussion] Session Refresher - RFC 4028

[Stephen James]

In all cases below the refresher is the MCU - the refresher value (uas/uac) is 
from the perspective of the sender of the request.
Line 119 - uas is the receiver of the request (INVITE) the sender of the 200 OK 
(MCU)
Line 723 - uac is the sender of the request (INVITE) (MCU)
 
Stephen James 
sjames_1958 at yahoo.com
 
We are not princes of the earth, we are the descendants of worms, and any 
nobility must be earned.





________________________________
From: "GASCA, GONZALO" <gg608f at att.com>
To: "discussion at sipforum.org" <discussion at sipforum.org>
Sent: Wed, January 30, 2013 10:10:55 AM
Subject: [SIPForum-discussion] Session Refresher - RFC 4028

 
I have the following call:
 
SIP Phone (UAC) dials to a SIP MCU (UAS)
 
UAC à UAS
 
UAS answers 200 OK including:
                Line 119: <Line Value="Session-Expires: 1800;refresher=uas">
 
After call is established, UAS sends a RE-INVITE refresher=uac in the RE-INVITE 
message:
 
                Line 723: <Line Value="Session-Expires: 1800;refresher=uac">
                Line 931: <Line Value="Session-Expires: 1800;refresher=uac">
                Line 1059: <Line Value="Session-Expires: 1800;refresher=uac">
                Line 1267: <Line Value="Session-Expires: 1800;refresher=uac">

Question:
For this REINVITE message is UAS (SIP MCU) now the “new” uac or it is just 
indicating that original uac (SIP Phone) should send session refresh INVITE?
 
This is not clear as SIP MCU is the one continuously sending SIP REINVITEs.
 
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130130/c9cb6dfc/attachment-0002.html>