1 / 6

Enhanced SIP Session Timer Protocol: Key Changes and Implications

This document presents a significant overhaul of the SIP session timer functionality, detailing how it differs from previous versions. It addresses the dynamics of UAS and UAC support for session timers, particularly in scenarios where only one entity is aware of the session timer extension. Key call flow adjustments are highlighted, along with the behavior of proxies in these transactions. The document further discusses challenges related to reinvites and the impact on call handling, providing clarity on supported and unsupported scenarios.

orien
Télécharger la présentation

Enhanced SIP Session Timer Protocol: Key Changes and Implications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SIP Session Timer Jonathan Rosenberg dynamicsoft

  2. Significant overhaul from previous version Motivation: list discussion on supporting function when only one of UAS/UAC knows extension Works since you don’t need to support it to receive re-invites Want either side to perform reinvites Changes

  3. UAC supports, UAS doesn’t 200 OK won’t have S-T Last proxy that inserted S-T inserts S-T value + Require into response Requires stateful S-T proxies Call Flow INV; k:timer S-T: 500 INV; k:timer 200 OK Require: timer S-T: 500 200 OK ACK ACK INV; k:timer S-T: 500 INV; k:timer UAC Proxy UAS

  4. UAS supports, UAC doesn’t No Supported in INVITE Proxy inserts S-T anyway UAS reflects S-T, no Require, knows it is doing re-INVITES Call Flow INV S-T: 500 INV 200 OK S-T: 500 200 OK S-T: 500 ACK ACK INV; k:timer S-T: 500 INV; k:timer S-T: 500 UAC Proxy UAS

  5. Neither Supports Proxy inserts S-T timer even though no Supported No S-T in response Proxy doesn’t insert S-T or Require Call Flow INV S-T: 500 INV 200 OK 200 OK ACK ACK UAC Proxy UAS

  6. Both Support Same as previous drafts UAC will perform timer Open issues reinvite issues? Call Flow INVk:timer S-T: 500 INVk:timer 200 OK S-T: 500 Require: timer 200 OK S-T: 500 Require: timer ACK ACK INV; k:timer S-T: 500 INV; k:timer UAC Proxy UAS

More Related