Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1 New Initial version 4/25/2008 0.2 Updated on feedback 6/27/2008 1.0 Major Updated and revised the technical content. 8/15/2008 1.01 Minor Revised and edited the technical content. 9/12/2008 1.02 Minor Revised and edited the technical content. 12/12/2008 2.0 Major Updated and revised the technical content. 2/13/2009 2.01 Minor Revised and edited the technical content. 3/13/2009 2.02 Minor Revised and edited the technical content. 7/13/2009 2.03 Major Revised and edited the technical content 8/28/2009 2.04 Editorial Revised and edited the technical content 11/6/2009 2.05 Editorial Revised and edited the technical content 2/19/2010 2.06 Editorial Revised and edited the technical content
3/31/2010 2.07 Major Updated and revised the technical content 4/30/2010 2.08 Editorial Revised and edited the technical content 6/7/2010 2.09 Editorial Revised and edited the technical content 6/29/2010 2.10 Editorial Changed language and formatting in the technical content. 7/23/2010 2.10 None No changes to the meaning, language, or formatting of the technical content. 9/27/2010 3.0 Major Significantly changed the technical content. 11/15/2010 3.0 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 3.0 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 3.0 None No changes to the
meaning, language, or formatting of the technical content. 6/10/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 4.0 Major Significantly changed the technical content. 4/11/2012 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 4.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 4.0.1 Editorial Changed language and formatting in the technical content. 2/11/2013 4.0.1 None No changes to the meaning, language, or formatting of the technical content.
7/30/2013 4.0.1 None No changes to the meaning, language, or formatting of the technical content. 11/18/2013 4.0.1 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 4.0.1 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 4.1 Minor Clarified the meaning of the technical content. 7/31/2014 4.2 Minor Clarified the meaning of the technical content. 10/30/2014 4.2 None No changes to the meaning, language, or formatting of the technical content. 3/30/2015 5.0 Major Significantly changed the technical content. 9/4/2015 5.0 None No changes to the meaning, language,
or formatting of the technical content. 7/15/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 9/29/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 4/27/2018 6.0 Major Significantly changed the technical content. 7/24/2018 7.0 Major Significantly changed the technical content.
Messages Transport This protocol relies on transport. Message Syntax This protocol uses the format, as specified in section 7, and extends definitions of parameters and headers by adding new values for parameter and header names as well as their corresponding values. isGateway The isGateway parameter is defined by this protocol as a new Contact header field parameter. The original , as defined in , for the Contact header field, as specified in section 25, is extended as follows. The Contact header field extension is the second line. contact-params = c-p-q / c-p-expires / c-p-gw / contact-extension c-p-gw = "isGateway" The syntax of the Contact header with the SIP Contact header field extension is illustrated as follows. The extension is the final ;isGateway. CONTACT: <sip:a@example.com;gruu;opaque=srvr:MediationServer:xxx;grid=yyy>;isGateway phone-context This protocol extends the semantics of the phone-context parameter but does not change its syntax, as specified in . The phone-context value for a is the provisioned location profile name of the user. The phone-context extension defines the following two phone-context names: "dialstring" "enterprise" The first one is used if a user location profile name is not provisioned, and the second is used if a holds a phone number in a non- format that is a result of applying enterprise rules. The syntax of a SIP URI with a phone-context parameter is illustrated as follows: sip:12345;phone-context=lp1@example.com;user=phone In the previous line, example.com is the host part of the SIP URI. It is not affected by the parameter. ms-call-source The , as defined in , for the ms-call-source SIP header is as follows:
55 N 10 O local events 24 outbound call examples isGateway SIP contact header parameter 28 27 ms-accepted-content-id SIP header 52 49 ms-bypass SIP supported header option tag 45 43 ms-early-media SIP supported header option tag 37 38 36 ms-mediation-generated SIP header 57 56 ms-trunking-peer SIP header 55 phone-context SIP URI parameter 32 31 11 P 58 17 18 18 18 19 19 19 18 14 29 29 30 29 31 32 31 12 12 59 R 10 10 10 12 S Security 58 58 SIP headers 22 21 19 20 24 23 SIP URI 17 13 Supported header ms-bypass option tag example 39 42 T Timer events 21 17 23 22 20 21 24 23 19 Timers 21 17 23 22 19 20 24 23 18 61 14 V 13 12