Hi,
I have a question about indexing in section B.1. PBX Voicemail call floww.
F6 INVITE Example.com -> VM
<snip/>
History-Info: <sip:vm at example.com;\
target=sip:bob at example.com;cause=408>\
index=1.3;mp=1.2
This mp-value is "1.2".
If this HI is mapped from 1.2, should the index be 1.2.x?
Or, if this is mapped from "1"(ie bob at example.com), should
the mp-value be "1"?
Regards,
Shinji.
internet-drafts at ietf.org
Sun, 30 Oct 2011 05:22:28 -0700
>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session
>Initiation Protocol Core Working Group of the IETF.
>
> Title : An Extension to the Session Initiation Protocol (SIP) for Request History Information
> Author(s) : Mary Barnes
> Francois Audet
> Shida Schubert
> Detecon International Gmbh
> Christer Holmberg
> Filename : draft-ietf-sipcore-rfc4244bis-06.txt
> Pages : 65
> Date : 2011-10-30
>
> This document defines a standard mechanism for capturing the history
> information associated with a Session Initiation Protocol (SIP)
> request. This capability enables many enhanced services by providing
> the information as to how and why a SIP request arrives at a specific
> application or user. This document defines an optional SIP header
> field, History-Info, for capturing the history information in
> requests. The document also defines SIP header field parameters for
> the History-Info and Contact header fields to tag the method by which
> the target of a request is determined. In addition, this
> specification defines a value for the Privacy header field specific
> to the History-Info header field. This document obsoletes RFC 4244.
>
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-sipcore-rfc4244bis-06.txt
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>This Internet-Draft can be retrieved at:
>ftp://ftp.ietf.org/internet-drafts/draft-ietf-sipcore-rfc4244bis-06.txt
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.