Dialog PackageRohan Mahy

rohan@cisco.com

“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.

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”

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.