1. History of Voicemail Cullen Jennings Mary Barnes

2. Solutions Many users want Voicemail. Many vendors want to provide it. Two class of solutions: 1.History: proxies that retarget include some information about where and why they retargeted. Voicemail uses that to decide what to do. History-Info: ;index=1 2.Voicemail-URI: proxies figure out what service they want voicemail to provide and tell the voicemail to do that. INVITE sip:bob@um.example.com;target=bob;cause=486 SIP/2.0

3. Voice Jail at the IETF levy-sip-diversion –00 Oct 2000 –01 Nov 2000 –02 May 2001 –03 Oct 2001 –04 Jun 2002 –05 Jan 2003 –06 Jul 2003 –07 Sep 2003 jennings-sip-voicemail-uri –00 Oct 2003 –01 Feb 2004 –02 Jul 2004 bharatia-sipping- redirect –00 Nov 2001 watson-sipping-req- history –00 Feb 2002 –01 Apr 2002 –02 Jun 2002 ietf-sipping-req-history –00 Aug 2002 –01 Dec 2002 –02 Feb 2003 –03 May 2003 –04 Jun 2003 barnes-sipping-history –00 Oct 2002 –01 Dec 2002 –02 Feb 2003 ietf-sip-history-info –00 Jun 2003 –02 Oct 2003 –03 Feb 2004 –04 Jul 2004

4. Changes in Voicemail-URI Changes from 01 Version The reason information was moved from using the Reason header to being a tag in the URI. Changes from 00 Version The reason information was moved from being a tag in the URI to using the Reason header.

5. Using Both? Perhaps the long discussion was caused because there are two basic mechanisms; we need and both can be used for an application called “voicemail” –Proxy can add retargets and also may use voicemail URI or it can just do one of these –Voicemail can use URI for basic information and look at History for advanced services –Information in two headers does not conflict These do not cause harm or restrict what is possible. Many people want to use them.

6. Recommendation Choose something now –History, URI, or Both Our recommendation is both –They do different things –They work together Decide something and advance it now.