1 / 11

Message Waiting for SIP

Message Waiting for SIP. Rohan Mahy rohan@cisco.com. Current 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.

kyria
Download Presentation

Message Waiting for SIP

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. Message Waiting for SIP Rohan Mahyrohan@cisco.com

  2. Current 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

  3. Questions Time: NTP Transfer: HTTP Directory: LDAP Message SIP + Waiting: Sub/Ntfy? • 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: “You have 3 new messages (1 urgent)”

  4. Overview • 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

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

  6. Example 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>

  7. Linearization • In IMAP4 flags can overlap (ex: \Seen, \Answered, \Deleted, and \Flagged). Create precedence. • Deleted • Answered • Flagged • Read • Skipped • Untouched • Mapping media types from VPIM • multipart/Voice-Message -> voice • multipart/Fax-Message -> fax • multipart/Video-Message -> video • everything else -> email

  8. To 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?

  9. Contacts • Rohan Mahy (rohan@cisco.com) • Ilya Slain (islain@cisco.com) • Thank You

  10. SIP Proxy Messaging Server Notifications IP

  11. SIP Proxy Presence Proxy Messaging Server Notifications IP

More Related