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 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. 11/18/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 5.0 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 5.1 Clarified the meaning of the technical content. 7/31/2014 5.2 Minor Clarified the meaning of the technical content. 10/30/2014 5.2 None No changes to the meaning, language, or formatting of the technical content. 3/30/2015 6.0 Major Significantly changed the technical content. 9/4/2015 7.0 Major Significantly changed the technical content.
Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces. Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire. The changes made to this document are listed in the following table. For more information, please contact . Section Tracking number (if applicable) and description Major change (Y or N) Change type Appendix E: Product Behavior Updated the list format for applicable products. N Content update.
Index A Abstract data model 78 78 78 73 37 51 51 51 79 38 68 69 69 69 68 69 46 42 76 72 49 76 46 55 56 56 68 69 69 69 68 69 71 58 75 40 Agent anonymity extensions 78 78 78 93 79 78 79 message processing 79 78 sequencing rules 79 79 78 19 C Call context extensions 73 88 74 73 75 74 74 75 31 35 34 34 34 31 31 35 33 33 32 73 101 74 74 75 75 73 31 35 34 34 34 31 31 35 33 33 32 19 108 Client 37 37 37 37 37 37 37 37 37 23 29 D Data - abstract 78 78 78 73 37 51 51 51
79 38 68 69 69 69 68 69 46 42 76 72 49 76 46 55 56 56 68 69 69 69 68 69 71 58 75 40 Dialog state recover 51 Dialog state recovery abstract data model 51 51 83 higher-layer triggered events 52 initialization 52 55 30 message processing 52 53 53 51 sequencing rules 52 53 53 timer events 55 timers 52 E E911 79 79 79 INVITE 94 80 80 80 80 messages 36 79 PIDF Extension 102 80 80 80 80 79 36 EPID mechanism 38 38 38 38 38 40 39 39 39 39 37 39 39 39 39 39 38 81 Examples 93 88 83 94 81 87 82 81 86 83 Multipart MIME 89 Multi-part MIME 91 82 87 88 routing preamble 84 85 85 86 81 29 29 F Federation extension 68 69 69
Schemas 101 102 100 97 Security 96 96 Sequencing rules agent anonymity extensions 79 74 74 75 37 dialog state recovery 52 53 53 80 80 80 39 39 39 39 70 70 70 47 47 43 45 43 ICE SDP interworking 78 77 72 73 73 message routing with redundant server 50 multipart MIME 78 77 47 47 number resolution 56 70 70 70 71 71 71 routing script preamble 65 59 65 65 64 64 64 65 61 65 59 76 41 42 41 37 20 Contact header ( 22, 22) Path header ( 21, 22) Record-Route header field ( 21, 22) Request-URI header ( 22, 22) Route header field ( 21, 22, 22) SIP.INSTANCE mechanism 40 81 41 41 40 40 42 41 42 41 40 41 42 41 42 40 19 20 22 T events 79 75 37 dialog state recovery 55 80 39 70 48 45 78 73 50 78 48 57 70 71 routing script preamble 68 68 67 68 76 42 Timers 78 73