1. App Interaction Framework
Jonathan Rosenberg
dynamicsoft

2. Main Issue: How to Deliver DTMF
Current draft makes a new proposal
Two separate UI types are recognized
Presentation Capable
HTML, WML, VoiceXML
Presentation Free
KPML
Presentation Capable
Application sends REFER to UA
Refer-To has HTTP URI
URI references the markup
Presentation Free
Application sends a SUBSCRIBE to UA
Subscribe body has KPML
NOTIFY contains DTMF

3. Example KPML Flow Caller App Server Callee (1) INVITE (2) INVITE
(3) 200 OK
(4) 200 OK
(5) ACK
(6) ACK
(7) SUBSCRIBE
(8) 200 OK
(9) NOTIFY
(10) 200 OK

4. Example HTML Flow Caller App Server Callee (1) INVITE (2) INVITE
(3) 200 OK
(4) 200 OK
(5) ACK
(6) ACK
(7) REFER
(8) 200 OK
(9) NOTIFY
(10) 200 OK
(11) HTTP GET
(12) 200 OK
(13) HTTP POST
(14) 200 OK

5. Implications App-Info Header Not Used GRUU is needed in both cases
No ability to push updated scripts for presentation capable case
GRUU is needed in both cases
Needs to be unique for each dialog
Applications authorize any REFER/SUB made to GRUU
Applications can establish app sessions at any time
Application authentication to client done using normal SIP means
App sessions terminate with dialog
For presentation-free, can terminate earlier
Solves the forking problem
Much simpler overall

6. Next Steps Consensus on this approach?
If so, one more rev and we should be done
KPML needs a rev for alignment as well