Message Waiting for SIP
description
Transcript of Message Waiting for SIP
![Page 2: Message Waiting for SIP](https://reader036.fdocuments.us/reader036/viewer/2022062802/568144fe550346895db1c9ce/html5/thumbnails/2.jpg)
2Presentation_ID © 1999, Cisco Systems, Inc.
Current ExpectationsCurrent Expectations
• Users expect notification of new messages wherever they are
IP phones/appliances
Analog or PBX phones
Mobile phones
• MWI is traditionally just a boolean
• Must provide comparable service on SIP-capable devices
![Page 3: Message Waiting for SIP](https://reader036.fdocuments.us/reader036/viewer/2022062802/568144fe550346895db1c9ce/html5/thumbnails/3.jpg)
3Presentation_ID © 1999, Cisco Systems, Inc.
QuestionsQuestions
• Why not use another protocol?
No other compelling choice?
SUBSCRIBE/NOTIFY is sufficient and pre-standard implementations already exist
• Why not just use a simple boolean?
We can do better:
Time: NTPTransfer: HTTPDirectory: LDAPMessage SIP + Waiting: Sub/Ntfy?
“You have 3 new messages (1 urgent)”
![Page 4: Message Waiting for SIP](https://reader036.fdocuments.us/reader036/viewer/2022062802/568144fe550346895db1c9ce/html5/thumbnails/4.jpg)
4Presentation_ID © 1999, Cisco Systems, Inc.
OverviewOverview
• UA subscribes to message-summary events for a period of time
• Uses SUBSCRIBE/NOTIFY for subscription management and fetches
• Message Summary delivered in text or XML
![Page 5: Message Waiting for SIP](https://reader036.fdocuments.us/reader036/viewer/2022062802/568144fe550346895db1c9ce/html5/thumbnails/5.jpg)
5Presentation_ID © 1999, Cisco Systems, Inc.
Why two formats?Why two formats?
• Simple text: minimal display requirements
traditional boolean MWI +
basic summaries
• XML: extensible display options
basic summaries +
multiple mail folders
use with XSL style sheets
![Page 6: Message Waiting for SIP](https://reader036.fdocuments.us/reader036/viewer/2022062802/568144fe550346895db1c9ce/html5/thumbnails/6.jpg)
6Presentation_ID © 1999, Cisco Systems, Inc.
Example of XML formatExample of XML format
<MESSAGE_SUMMARY><MAILBOX> <NAME>Inbox</NAME> <VOICEMAIL>
<UNTOUCHED total="1"><READ total="2"/><ANSWERED total="1”
urgent="1”/><DELETED total="2"/>
</VOICEMAIL></MAILBOX>
</MESSAGE_SUMMARY>
![Page 7: Message Waiting for SIP](https://reader036.fdocuments.us/reader036/viewer/2022062802/568144fe550346895db1c9ce/html5/thumbnails/7.jpg)
7Presentation_ID © 1999, Cisco Systems, Inc.
LinearizationLinearization
In IMAP4 flags can overlap (ex: \Seen, \Answered, \Deleted, and \Flagged). Create precedence.
DeletedAnsweredFlaggedReadSkippedUntouched
Mapping media types from VPIM multipart/Voice-Message -> voice multipart/Fax-Message -> fax multipart/Video-Message -> videoeverything else -> email
![Page 8: Message Waiting for SIP](https://reader036.fdocuments.us/reader036/viewer/2022062802/568144fe550346895db1c9ce/html5/thumbnails/8.jpg)
8Presentation_ID © 1999, Cisco Systems, Inc.
To doTo do
• Consistent SUBSCRIBE behavior from Bar BOF
• Clean up XML format<read total="25" urgent="4"/>
vs.<read urgent="4">25</read>
• VPIM WG input
• Examples with XSL
• real mime-type registration?
![Page 9: Message Waiting for SIP](https://reader036.fdocuments.us/reader036/viewer/2022062802/568144fe550346895db1c9ce/html5/thumbnails/9.jpg)
9Presentation_ID © 1999, Cisco Systems, Inc.
ContactsContacts
• Rohan Mahy ([email protected])
• Ilya Slain ([email protected])
• Thank You
![Page 10: Message Waiting for SIP](https://reader036.fdocuments.us/reader036/viewer/2022062802/568144fe550346895db1c9ce/html5/thumbnails/10.jpg)
10Presentation_ID © 1999, Cisco Systems, Inc.
Messaging Server
IP
SIP Proxy
Notifications
![Page 11: Message Waiting for SIP](https://reader036.fdocuments.us/reader036/viewer/2022062802/568144fe550346895db1c9ce/html5/thumbnails/11.jpg)
11Presentation_ID © 1999, Cisco Systems, Inc.
Messaging Server
IP
SIP Proxy
Notifications
Presence Proxy