[SIPForum-discussion] Session Refresher - RFC 4028

[HM Kias]

A re-INVITE is used to change the session parameters of an existing or
pending call. In the initial INVITE request, a Session-Expires header field
indicates a timer interval after which stateful proxies may discard state
information about the session. User agents must tear down the call after
the expiration of the timer. The caller can send re-INVITEs to refresh the
timer, enabling a “keep alive” mechanism.

Regards,

Kias Hanifa

Fonicom


On Tue, Jan 29, 2013 at 5:32 AM, GASCA, GONZALO <gg608f at att.com> wrote:

>  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****
>
> ** **
>
> ** **
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>


-- 
HM Kias
91-9443467600
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130131/5286bc61/attachment-0002.html>