Issues and Status in App Interaction Team Jonathan Rosenberg dynamicsoft
Status • Design team has submitted new versions of its documents – Draft-rosenberg-sipping-app-interaction-framework-01 – Draft-burger-sipping-kpml-02 – Draft-jennings-sip-app-info-01 • There is really one main open issue (the big one) – next slide • We don’t believe the design team alone can resolve this last issue • We believe the group needs to make a decision on whether to adopt this work
Changes from Previous Rev • Framework – Removed client-remote UI feature interaction sections – Mention MESSAGE for one -shot and monitoring KPML usages – Remove bit about using KPML along with clientremote VXML driven UI for purposes of zero-latency barge-in • App-Info – No error reporting mechanism – Motivate instance and class names – Sips as authorization mechanism – Will use callee-caps instead of an Allow-Schemes • KPML – Added digit suppression – MESSAGE for reporting
The open issue: KPML DTMF reporting • INFO – Can’t work within call dialog – But spec mandates its only within a dialog • NOTIFY w. Implicit subscription – Known issues • Explicit subscription from application – GRUU problem – Authorization • HTTP – Not returning a script in proposed scope • New method – What does this buy us? • MESSAGE – Seems to work – Adam raised some UI issues though if its misrouted – Kind of ugly • Design team reluctantly chose MESSAGE
Proposal • Continue to hammer out the open issue on the list – Hopefully it will conclude • Adopt the framework and KPML as sipping items – They need broader input now
PIDF Phone
What is it? • A set of presence states that describe a “phone” as an application – Considered black phones, wireless, enterprise • States are things like in/out of call, registered, callwaiting, etc. • Presence is a simple issue, but the presence states are related to phones, and thus sipping expertise • These are important in the “device” and “service” views that have been discussed in SIMPLE • Looking for comments and inputs to this work