ANSI ATIS 1000017-2008 Interworking between the ISDN User-Network Interface Protocol and the Session Initiation Protocol (SIP) with ANSI Extensions to the Narrowband Signaling Synt.pdf

《ANSI ATIS 1000017-2008 Interworking between the ISDN User-Network Interface Protocol and the Session Initiation Protocol (SIP) with ANSI Extensions to the Narrowband Signaling Synt.pdf》由会员分享，可在线阅读，更多相关《ANSI ATIS 1000017-2008 Interworking between the ISDN User-Network Interface Protocol and the Session Initiation Protocol (SIP) with ANSI Extensions to the Narrowband Signaling Synt.pdf（56页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000017.2008(R2013) Interworking between the ISDN User-Network Interface Protocol and the Session Initiation Protocol (SIP) with ANSI Extensions to the Narrowband Signaling Syntax (NSS) As a leading technology and solutions development organiza

2、tion, ATIS brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, q

3、uality of service, billing support, operations, and more. These priorities follow a fast-track development lifecycle from design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredi

4、ted by the American National Standards Institute (ANSI). ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunicati

5、ons sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit. AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been

6、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 majority, but not necessarily unanimity. Con

7、sensus 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 approved the standards or not, from manuf

8、acturing, 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 Standard. Moreover, no person shall have the

9、 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 standard. CAUTION NOTICE: This America

10、n 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 receive current information on all standard

11、s by calling or writing the American National Standards Institute. Notice of Disclaimer all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid

12、 ITU-T Recommendations is regularly published. Interworking Function DSS1 SIP with ANSI NSS Scope of this Standard Figure 1 - Scope of this Standard ATIS-1000017.2008 2 ATIS-1000113.2005(R2010), July 2005, Signalling System No.7 (SS7) Integrated Services Digital Network (ISDN) User Part.1ATIS-100060

13、7.2000(R2009), August 2000, Integrated Services Digital Network (ISDN) Layer 3 Signalling Specification for Circuit Switched Bearer Service for Digital Subscriber Signalling System Number 1 (DSS1).1ATIS-1000008.2006(R2011), January 2006, ANSI Extensions to the Narrowband Signaling Syntax (NSS).1ISO

14、3166-1 (1997), Codes for the representation of names of countries and their subdivisions - Part 1: Country codes.2ITU-T Q.1980.1, The Narrowband Signalling Syntax Syntax Definition.3RFC 3261, SIP: Session Initiation Protocol, June 2002.4RFC 3966, The tel URI for Telephone Numbers, December 2004.43 D

15、EFINITIONS, ACRONYMS, charge= “addr-spec” Where the last is one type of Billing-Info-param is Charge-param asserting an Acct-Charge-URI. ATIS-1000017.2008 5 DSS1 INFORMATION ELEMENTS SENT TO IWF RESULTING SIP HEADERS OR NSS Dialed Number Information Service (DNIS) NSS MIME body parameters: 1GEA,diad

16、,dd,a,a,a,a,# (type,noa,npi,cni,pi,si,#) Network Specific Facilities NSS Trunk Group information (RFC 4904): 1ton, nip, nid, nsp ind maps to the trunk-context Network-specific facility specication maps to trgp (and is specific to the trunk-context) Original Called Number (OCN) From: header Referred-

17、By: header Note: Dependency on INVITE, UPDATE and REFER message usage. Original Dialed Number (ODN) To: header History-Info: header Redirecting Number History-Info: header User Entered Code 2 NSS MIME body parameters: 1GED,d,d,# (tod,es,#) FDC,ged,tod*,a,1*(2Hex) Note: a= instruction selected and 1*

18、(2Hex) contains entered code type of digits Note that zero or more occurrences of this GED-FDC set is possible. User to User NSS MIME body parameters: 1UUS,a,1*(2Hex) Note: “a” is protocol discriminator and 1*(2Hex) carriers the user-user information. 1 The MIME body starts with parameters (“a” valu

19、es inserted according to standard): VER,aaaa PRN,isdn*,aaa,aaaa,aaaa Here were mapping from ISDN into NSS IAM, NOTE: Other headers not identified above that are required / optional for the INVITE Request are not dictated by the contents of the PRI SETUP message. These are populated independent of th

20、e contents of the PRI SETUP message. 2This IE is an extension to standard ISDN ATIS-1000017.2008 6 Table 2.a - DSS1 Bearer Capability IE to SDP Offer/Answer Headers DSS1 INFORMATION ELEMENT SENT TO IWF RESULTING SDP OFFER/ANSWER Bearer Capability: Voice is converted to speech or 3.1 kHz / data is co

21、nverted 56 rate adapted or 64 unrestricted based upon subscription at PRI or bandwidth information provided in SDP Media lines (m): m=audio for speech, 3.1 kHz, m= audio/clearmode for 64 kbps data, 56 rate adapted data or packet data Bandwidth (b): Used with (m) to determine Bearer Capability if pro

22、vided High Layer Compatibility No action Low Layer Compatibility No action 5.1.2 ALERTING Message Information Elements Table 3 shows the mapping of DSS1 Alerting message information elements to SIP headers and NSS bodies. Table 3 DSS1 ALERTING IE to SIP 180 Ringing Response Headers DSS1 INFORMATION

23、ELEMENTS SENT TO IWF RESULTING SIP HEADERS OR NSS Call Reference Call-ID: The gateway will maintain the Call-ID to Call Reference association for the duration of the call. Progress Indicator - #8 This is not included in the 180 Ringing response. A 183 Session Progress response must be sent with sess

24、ion value of media instead of the 180 Ringing response 1NOTE: Other headers not identified above that are required / optional for the 180 Ringing response are not dictated by the contents of the PRI ALERTing message. These are populated independent of the contents of the PRI ALERTing message. 1 Sess

25、ion header is not a standard SIP header. 5.1.3 PROGRESS Message Information Elements Table 4 shows the mapping of DSS1 Progress message information elements to SIP headers and NSS bodies. Table 4 DSS1 PROGRESS IE to SIP 183 Session Progress Response Headers DSS1 INFORMATION ELEMENTS SENT TO IWF RESU

26、LTING SIP HEADERS OR NSS Call Reference Call-ID: The gateway will maintain the Call-ID to Call Reference association for the duration of the call. Progress Indicator - #1, #8 183 with SDP containing Answer Progress Indicator - #10 Send 183 without SDP ATIS-1000017.2008 7 DSS1 INFORMATION ELEMENTS SE

27、NT TO IWF RESULTING SIP HEADERS OR NSS Cause - (ignore as only causes that provide supplementary information are allowed) NOTE: Other headers not identified above that are required / optional for the 183 Session Progress response are not dictated by the contents of the PRI PROGress message. These ar

28、e populated independent of the contents of the PRI PROGress message. 5.1.4 CONNECT Message Information Elements Table 5 shows the mapping of DSS1 Connect message information elements to SIP headers and NSS bodies. Table 5 DSS1 CONNECT IE to SIP 200OK Response Headers DSS1 INFORMATION ELEMENTS SENT T

29、O IWF RESULTING SIP HEADERS OR NSS Call Reference Call-ID: The gateway will maintain the Call-ID to Call Reference association for the duration of the call. Progress Indicator - #2 Warning 399 : miscellaneous warning NOTE: Other headers not identified above that are required / optional for the 200 O

30、K response are not dictated by the contents of the PRI CONNect message. These are populated independent of the contents of the PRI CONNect message. 5.2 Mid-Call Messages Table 6 shows the mapping of mid-call messages from DSS1 to SIP. Table 6 DSS1 to SIP Mid-Call Messages DSS1 MESSAGE NAME SENT TO I

31、WF RESULTING SIP REQUEST/RESPONSE FACILITY INFONOTIFY NOTIFY5.2.1 FACILITY Message Information Elements Table 7 shows the mapping of DSS1 Facility message information elements to SIP headers and NSS bodies. Table 7 DSS1 FACILITY IE to SIP INFO Headers DSS1 INFORMATION ELEMENTS SENT TO IWF RESULTING

32、SIP HEADERS OR NSS Operation Value from Code Set NSS MIME body parameters: 1GNO,dd Note: “a” values inserted as appropriate and “dd” is the 2-digit notification indicator selected from the list provided in NSS standard. ATIS-1000017.2008 8 DSS1 INFORMATION ELEMENTS SENT TO IWF RESULTING SIP HEADERS

33、OR NSS Network Specific Facilities (parameterized network management data) NSS Trunk Group information (RFC 4904): 1ton, nip, nid, nsp ind maps to the trunk-context Network-specific facility specication maps to trgp (and is specific to the trunk-context) User Entered Code NSS MIME body parameters: 1

34、GED,d,d,# (tod,es,#) FDC,ged,tod*,a,1*(2Hex) Note: a= instruction selected and 1*(2Hex) contains entered code type of digits Note that zero or more occurrences of this GED-FDC set is possible. User to User Information NSS MIME body parameters: 1UUS,a,1*(2Hex) Note: “a” is protocol discriminator and

35、1*(2Hex) carriers the user-user information. 1 The MIME body starts with parameters (“a” values inserted according to standard): VER,aaaa PRN,isdn*,aaa,aaaa,aaaa Here were mapping from ISDN into NSS FAC, NOTE: Other headers not identified above that are required / optional for the 200 OK response ar

36、e not dictated by the contents of the PRI CONNect message. These are populated independent of the contents of the PRI CONNect message. 5.2.2 NOTIFY Message Information Elements Table 8 shows the mapping of DSS1 Notify message information elements to SIP headers and NSS bodies. Table 8 DSS1 NOTIFY IE

37、 to SIP NOTIFY Headers DSS1 INFORMATION ELEMENTS SENT TO IWF RESULTING SIP HEADERS OR NSS Operation Value from Code Set NSS MIME body parameters: 1GNO,dd Note: “dd” is the 2-digit notification indicator selected from the list in the NSS standard Redirect Status History-Info: header Redirection Infor

38、mation History-Info: header (response code 489 Bad Event) ATIS-1000017.2008 9 DSS1 INFORMATION ELEMENTS SENT TO IWF RESULTING SIP HEADERS OR NSS User User Indicators NSS MIME body parameters: 1UUI,aaaa,a,a,a,a Note: “a” is value selected from the list in the NSS standard 1 The MIME body starts with

39、parameters (“a” values inserted according to standard): VER,aaaa PRN,isdn*,aaa,aaaa,aaaa , This should be either RES (resume) or SUS (suspend) depending on value of notification indicator IE NOTE: Other headers not identified above that are required / optional for the 200 OK response are not dictate

40、d by the contents of the PRI CONNect message. These are populated independent of the contents of the PRI CONNect message. 5.3 Call Clearing Table 9 shows the mapping of call clearing messages from DSS1 to SIP. Table 9 DSS1 to SIP Call Clearing Messages DSS1 MESSAGE NAME SENT TO IWF RESULTING SIP REQ

41、UEST/RESPONSE First Call Clearing message (i.e., DISCONNECT, RELEASE, or RELEASE COMPLETE as appropriate) BYE Request / CANCEL Request / 4xx, 5xx, 6xx Response, depending of SIP session status RESTART BYE Request / CANCEL Request if an active call on the B-channel (s) restarted RESTART ACKNOWLEDGE 2

42、00 OK Response if appropriate based upon what initiated the initial RESTART NOTE: Responses are not “mapped”, they are generated locally. This applies to the full section 5.3. Cause #16 is the generic call clearing message. 5.3.1 First Call Clearing Message Information Elements Table 10 shows the ma

43、pping of DSS1 First Call Clearing message information elements to SIP headers and NSS bodies. Table 10 DSS1FIrst Call Clearing IE to SIP BYE/CANCEL Request Headers DSS1 INFORMATION ELEMENTS SENT TO IWF RESULTING SIP HEADERS OR NSS Call Reference Call-ID: The gateway will maintain the Call-ID to Call

44、 Reference association for the duration of the call. Cause - #16 - (normal clearing indication, see below for non normal clearing ) ATIS-1000017.2008 10 DSS1 INFORMATION ELEMENTS SENT TO IWF RESULTING SIP HEADERS OR NSS Operation Value from Code Set NSS MIME body: VER,1.00 PRN,aaaaa,aaa,aaaaa,aaaa R

45、EL, GNO,dd Note: dd = 13 other party disconnected, when applicable User-User Information UUS NOTE: Other headers not identified above that are required / optional for the BYE / CANCEL Request response are not dictated by the contents of the PRI DISConnect message. These are populated independent of

46、the contents of the PRI DISConnect message. 5.3.2 DSS1 Cause Values The following Cause Code mapping is aligned with ATIS-1000679.2004(R2010). When the Cause Value Information Element indicates anything other than normal clearing the following response codes should be used: Table 11 DSS1 Cause Value

47、 to SIP Responses DSS1 MESSAGE NAME SENT TO IWF RESULTING SIP REQUEST/RESPONSE Cause Value Information Element SIP Response / SIP Request ITU_T Causes #1 unallocated number 404 Not Found Response #2 no route to specified transit network 404 Not Found Response #3 no route to destination 404 Not Found

48、 Response #6 - channel unacceptable 400 Bad Request Response #7 call awarded and being given in an established channel - (not sent when clearing call) # 16 normal clearing BYE / CANCEL Request (see above) #17 user busy 486 Busy Here Response #18 no user responding 480 Temporarily Unavailable Respons

49、e #19 - user alerting, no answer 480 Temporarily Unavailable Response #20 subscriber absent 480 Temporarily Unavailable Response #21 call rejected 403 Forbidden #22 number changed 410 Gone #26 non selected user clearing 404 Not Found Response ATIS-1000017.2008 11 DSS1 MESSAGE NAME SENT TO IWF RESULTING SIP REQUEST/RESPONSE #27 destination out of order 502 Bad Gateway #28 Address Incomplete 484 Address Incomplete #29 Facility Rejected 501 Not Impleemented #30 response