1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000679.2015 Interworking between Session Initiation Protocol (SIP) and ISDN User Part As a leading technology and solutions development organization, the Alliance for Telecommunications Industry Solutions (ATIS) brings together the top global
2、ICT companies to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currently working to address the All-IP transition, network functions virtualization, big data analytics, cloud services, device solutions, emergency services, M2M, cyber security, network
3、evolution, quality of service, billing support, operations, and much more. These priorities follow a fast-track development lifecycle from design and innovation through standards, specifications, requirements, business use cases, software toolkits, open source solutions, and interoperability testing
4、. ATIS is accredited by the American National Standards Institute (ANSI). The organization is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global initiative, a member of and major U.S. contributor to the International T
5、elecommunication Union (ITU), as well as a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit www.atis.org. AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and o
6、ther criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majorit
7、y, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has appr
8、oved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standar
9、d. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this s
10、tandard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receiv
11、e current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer all users of this standard are therefore encouraged to investigate the possibility of applying the most recent edition of the standards and other references listed below. NOTE
12、 All IETF Standards Track RFCs directly referenced by this Standard are listed in Annex C. ATIS-1000113.2005(R2010), Signaling System No. 7 (SS7) - Integrated Service Digital Network User Part (ISUP).1ATIS-1000607.2014, Digital Subscriber Signaling System No. 1 - Layer 3 Signaling Specification for
13、Circuit Switched Bearer Service.2ATIS-1000607.a.2006(2011), Supplement to ATIS-10006073. ATIS-1000611.1991(R2013), Signalling System Number 7 (SS7) - Supplementary Services for Non-ISDN Subscribers.4ATIS-1000613.1991(R2012), Integrated Services Digital Network (ISDN) - Call Waiting Supplementary Ser
14、vice.5 ATIS-1000616.2014, Integrated Services Digital Network (ISDN) Call Hold Supplementary Service.6 ATIS-1000619.1992(R2010), Integrated Services Digital Network (ISDN) - Multi-Level Precedence and Preemption (MLPP) Service Capability.71This document is available from the Alliance for Telecommuni
15、cations Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 2This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 3This document is available from the Alliance for Telecommunicati
16、ons Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 4This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 5This document is available from the Alliance for Telecommunications
17、Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 6This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 ATIS-1000679.2015 3 ATIS-1000619.a.1994(R2012), Integrated Services Digit
18、al Network (ISDN) - Multi-Level Precedence and Preemption (MLPP) Service Capability (MLPP Service Domain and Cause Value Changes).8ATIS-1000621.2014, Integrated Services Digital Network (ISDN) User-to-User Signaling Supplementary Service.9ATIS-1000622.1999(R2013), Message Waiting Indicator Control a
19、nd Notification Supplementary Services and Associated Switching and Signaling Specifications.10ATIS-1000622.a.1998(R2013), Supplement to ATIS-1000622.1999(R2008) - Message Waiting Indicator Control and Notification Supplementary Services and Associated Switching and Signaling Specifications.11ATIS-1
20、000625.1993(R2013), Integrated Services Digital Network (ISDN) - Calling Line Identification Presentation and Restriction Supplementary Services.12ATIS-1000625.a.1998(R2013), Supplement to ATIS-1000625.1993(R2008) - Integrated Services Digital Network (ISDN) - Calling Line Identification Presentatio
21、n and Restriction Supplementary Services, Application of Standard to Wireless PCS Applications.13ATIS-1000628.2000(R2010), Emergency Calling Service.14ATIS-1000628.a.2001(R2010), ECS-Connection and Ring Back Addendum Supplement to ATIS-1000628.2000(R2010).15ATIS-1000632.1993(R2014), ISDN Supplementa
22、ry Service Normal Call Transfer.16ATIS-1000639.1995(R2011), Calling Name Identification Restriction.17ATIS-1000639.a.2001(R2011), Supplement to Calling Name Identification Restriction.18ATIS-1000641.2014, Calling Name Identification Presentation.19ATIS-1000641.a.2002(R2012), Supplement to Calling Na
23、me Identification Presentation.207This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 8This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Sui
24、te 500, Washington, DC 20005 9This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 10This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite
25、500, Washington, DC 20005 11This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 12This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 50
26、0, Washington, DC 20005 13This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 14This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500,
27、 Washington, DC 20005 15This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 16This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, W
28、ashington, DC 20005 17This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 18This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Was
29、hington, DC 20005 19This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 20This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washi
30、ngton, DC 20005 ATIS-1000679.2015 4 ATIS-1000642.2014, Integrated Services Digital Network (ISDN) Supplementary Service Call Deflection.21ATIS-1000643.1998(R2013), Integrated Services Digital Network (ISDN) Explicit Call Transfer Supplementary Service.22ATIS-1000647.1995(R2010), Integrated Services
31、Digital Network (ISDN) Conference Calling Supplementary Service.23ATIS-1000647.a.1998(R2010), Integrated Services Digital Network (ISDN) - Conference Calling Supplementary Service - Operations Across Multiple Interfaces.24ATIS-1000653.1996(R2010), Integrated Services Digital Network (ISDN) Call Park
32、 Supplementary Service.25ATIS-1000653.a.1998(R2010), Integrated Services Digital Network (ISDN) Call Park Supplementary Service Generic Procedures for the Control of ISDN Supplementary Services, Clarification for Number Identification.26ITU-T Recommendation Q.1912.5, Interworking between Session Ini
33、tiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part.27ITU-T Recommendation Q.850, Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part.273GPP TS 24.229, IP multimedia call control protocol based
34、 on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3, clause 7.2A.12, CPC and OLI tel URI parameter definition.283 Definitions For a list of common communications terms and definitions, please visit the ATIS Telecom Glossary, which is located at . For ISUP specific t
35、erminology, refer to ATIS-1000113.2005, chapter 2. For SIP and SDP specific terminology, refer to RFC 3261 and RFC 2327, respectively. Definitions for additional terminology used in this interworking Standard are as follows: 3.1 Adjacent SIP Node (ASN): A SIP node (e.g., SIP Proxy or Back-to-Back Us
36、er Agent or the SIP side of an IWU) that has established a direct trust relation (association) with Incoming or Outgoing IWU entities. The SIP Proxy and Back-to-Back User Agent are defined in accordance with RFC 3261. 3.2 Incoming Interworking Unit (I-IWU): This physical entity, which can be combine
37、d with an ISUP exchange, terminates incoming calls using SIP and originates outgoing calls using the ISUP protocol. 3.3 Incoming or Outgoing: In this Standard, indicates the direction of a call (not signaling information) with respect to a reference point. 3.4 Incoming SIP or ISUP Network: The netwo
38、rk from which the incoming calls are received; uses the SIP or ISUP protocol. Without the term “network,” simply refers to the protocol. 21This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 22This documen
39、t is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 23This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 24This document
40、is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 25This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 26This document is
41、 available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 27This document is available from the International Telecommunications Union. 28This document is available from the Third Generation Partnership Project (3GPP) at . ATIS
42、-1000679.2015 5 3.5 Outgoing Interworking Unit (O-IWU): This physical entity, which can be combined with an ISUP exchange, terminates incoming calls using ISUP and originates outgoing calls using SIP. 3.6 Outgoing SIP or ISUP Network: The network, to which the outgoing calls are sent, uses SIP or IS
43、UP protocol. Without the term “network,” simply refers to the protocol. 3.7 SIP with Encapsulated ISUP (SIP-I): The use of SIP with a message body that encapsulates the ISUP information according to the requirements in this Standard. 3.8 SIP Precondition: Indicates the support of the SIP “preconditi
44、on procedure” as defined in RFC 3312. In addition, this Standard makes use of the terms header field, message, message body, method, provisional response, and User Agent, which are defined in RFC 3261, clause 6. It uses the term payload type as defined in RFC 3550, and static and dynamic payload typ
45、e as defined in that RFC. Finally, it uses the terms attribute and session as defined in RFC 2327. Within this document the following terminology is used: Pass to ISUP procedures describes an operation internal to the IWU; and Send describes the transmission of a message on the applicable external n
46、etwork interface. 4 Abbreviations Parameters; Information elements and Messages. Examples: Called Party Number parameter, Initial Address Message. 2. The definition of a parameter value is written in italics and is inserted between quotation marks. ATIS-1000679.2015 8 Example: Nature of Address valu
47、e 0000011 “national (significant) number.” 5.2 Conventions for Representation of SIP/SDP Information 1. All letters of SIP method names are capitalized. Examples: INVITE, INFO. 2. SIP header fields are identified by the unabbreviated header field name as defined in the relevant RFC, including capita
48、lization and enclosed hyphens but excluding the following colon. Examples: To, From, Call-ID. 3. Where it is necessary to refer with finer granularity to components of a SIP message, the component concerned is identified by the ABNF rule name used to designate it in the defining RFC (generally from
49、clause 25 of RFC 3261), in plain text without surrounding angle brackets. Examples: Request-URI, the userinfo portion of a sip: URI. 4. URI schemes are represented by the lower-case identifier followed by a colon and the abbreviation “URI.“ Examples: sip: URI, tel: URI. 5. SIP provisional and final responses other than 2XX are represented by the status code followed by the normal reason phrase for that status code, with initial letters capitalized. Examples: 100 Trying, 484 Address Incomplete. 6. Because of potential ambiguity within a call flow
