1 / 4

Dialog Package

The discussion focuses on enhancements to the Dialog Package, particularly concerning hold management. A significant need has been identified for a passive/active flag for 'hold' status. A new feature tag for interactivity is proposed amid ongoing debates. Suggestions include removing hold-related parameters into a separate document and introducing several critical parameters: one to indicate attention to sending a BYE, another for unknowns in media reception, and a new state for dialog management. These proposals aim to clarify functionality and improve communication within SIP User Agents.

dustin-boyle
Télécharger la présentation

Dialog Package

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. Dialog Package • Rohan Mahy • rohan@cisco.com

  2. “Hold” Issue • Hold: Lots of folks wanted a passive/active flag or other indicator they could use for hold. • Proposed adding a new callee-caps feature tag for “interactivity”. Lots of controversy and discussion on list • options for moving forward with the dialog package.... • 0. remove all hold-related parameters from document and do separate document for these parameters1. have one parameter: "i'm paying enough attention to send a bye"2. a) parameter for "don't know how to send bye", b) "i'm not receiving ANY of your media"3. 2+ c) i'm just along for the ride with another more active SIP UA.

  3. Option 2: concrete proposal • Proposed names for the two parameters • “byeless” parameter: used when UA can’t reasonably determine when to send a BYE (ex:continuous announcement service) or is unable to send a BYE (ex: human call center agent in some call centers) • “rendering” parameter: is UA rendering ANY of the media it is receiving? • “rendering” EQUAL “no” / “yes” / “unknown”

  4. Two other open issues • Cullen brought up an issue about adding a state for before sending an INVITE or after receiving BYE • option 1) better document the existing hack • option 2) add a new state ("not ready") • What is the lifetime of a dialog that is in the terminated state? • you only send “terminated” state in partial update. Proposal: add text to clarify this.

More Related