[SIPForum-discussion] Session Refresher - RFC 4028

[Yuksel ERSOY]

UAC: a user agent client (caller).
UAS: a user agent server (callee).

The roles of UAC and UAS are logical entities and they last for only the duration of a transaction.  This means if a UA (makes a request, it is a UAC, and if it receives a request, it will be UAS.
So the new UAC  is SIP MCU,

Thanks,

Yuksel

From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of GASCA, GONZALO
Sent: Tuesday, January 29, 2013 12:03 AM
To: discussion at sipforum.org
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/20130201/c959e50a/attachment-0002.html>