Message Waiting for SIP

1

Message Waiting for Message Waiting for SIPSIP

Rohan MahyRohan [email protected]@cisco.com

2Presentation_ID © 1999, Cisco Systems, Inc.

Current ExpectationsCurrent Expectations

• Users expect notification of new messages wherever they are

IP phones/appliancesAnalog or PBX phonesMobile phones

• MWI is traditionally just a boolean• Must provide comparable service on SIP-capable devices

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)”

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

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

6Presentation_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?

7Presentation_ID © 1999, Cisco Systems, Inc.

ContactsContacts

• Rohan Mahy ([email protected])• Ilya Slain ([email protected])

• Thank You

8Presentation_ID © 1999, Cisco Systems, Inc.

Messaging Server

IP

SIP Proxy

Notifications