1、 ATIS-0300106 ATIS Standard on - INTERCARRIER CALL COMPLETION/CALL TERMINATION HANDBOOK As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, ne
2、arly 200 companies address cloud services, device solutions, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities follow a fast-track development lifecyclefrom design and innovation through solutions that include
3、standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partne
4、r of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit .Notice of Disclaimer Describes some of the problems being en
5、countered; Discusses some of the industry standards and practices relevant to ensuring call completion, particularly signaling, routing, and trouble handling; Attempts to relate these standards and practices to the call completion problems reported; and Offers some best practices for ensuring call c
6、ompletion, especially in the management of intermediate or underlying carriers. 1.2 Purpose This handbook was initiated to provide a resource to carriers to address issues as they are encountered related to intercarrier (long distance) call completion/call termination. 1.3 Application 1.3.1 Problems
7、 Reported ATIS understands that, according to an industry survey, customers of some telecommunications service providers (particularly those in rural areas) have experienced difficulties with the receipt of long distance calls via their phone service, including problems that generally fell into the
8、following categories: Call completion failure: Failure scenarios reported included: o The calling party hears ringing but the called party hears nothing (no ringing). o The called partys phone rings, but the called party hears dead air when the call is answered. o The calling party hears local busy
9、tone (when the line was not busy). o The calling party hears fast or network busy, or hears a network failure announcement including inappropriate “number not in service”. Very long post dial delay. Poor transmission quality (both voice and fax). Misidentification of calling party. 1Here PSTN is use
10、d to refer to the set of networks used to complete calls using E.164 number addressing. ATIS-0300106 2 In addition, carriers reporting these problems attributed them to the acts and omissions of intermediate or underlying service providers handling such calls. 2 References The following documents/st
11、andards contain information which is referenced within this guideline. At the time of publication, the editions indicated were valid. All documents/standards are subject to revision, and the reader is encouraged to investigate the possibility of applying the most recent editions of the standards and
12、/or documents indicated below. ATIS-0300009, NGIIF Reference Document Part I- Installation and Maintenance Responsibilities for Special Access Services, WATS Access Lines, and Switched Access Services Feature Group “A“.2ATIS-0300010, NGIIF Reference Document Part II- Installation and Maintenance Res
13、ponsibilities for Switched Access Services Feature Groups “B,“ “C,“ and “D“.2ATIS 0300011, NGIIF Reference Document Part II- Installation and Maintenance Responsibilities for Switched Access Services Feature Groups “B,“ “C,“ and “D“.2ATIS-0300012, NGIIF Reference Document Part III- Attachment A- MTP
14、 Compatibility Tests.2ATIS-0300013, NGIIF Reference Document Part III- Attachment B- ISUP Compatibility Tests.2ATIS-0300014, NGIIF Reference Document Part III- Attachment C- SCCP Protocol Class 0 Compatibility Tests.2ATIS-0300015, NGIIF Reference Document Part III- Attachment D- Test Severity Analys
15、is Criteria.2ATIS-0300016, NGIIF Reference Document Part III- Attachment E- SS7 Network Gateway Screening.2ATIS-0300017, NGIIF Reference Document Part III- Attachment F- SS7 ISUP Tests for ISDN Network Interconnection.2ATIS-0300018, NGIIF Reference Document Part III- Attachment G- SS7 Link Diversity
16、 Validation Guidelines.2ATIS-0300019, NGIIF Reference Document Part III-Attachment H SS7 Cause Codes and Tones and Announcements.2ATIS-0300020, NGIIF Reference Document Part III- Attachment I- SS7 Security Base Guidelines.2ATIS-0300021, NGIIF Reference Document Part III- Attachment J- SS7 Software V
17、alidation.2ATIS-0300022, NGIIF Reference Document Part III- Attachment K- Dual STP Failure Prevention Procedures.2ATIS-0300023, NGIIF Reference Document Part IV- Installation and Maintenance Responsibilities for X.75 Gateway Services.2ATIS-0300024, NGIIF Reference Document Part V- Test Line Guidelin
18、es.2ATIS-0300030, NGIIF Reference Document Part IX- Installation, Testing, and Maintenance Responsibilities for Facilities.2ATIS-0300032, Next Generation Interconnection Interoperability (NGIIF) Reference Document: Part X, Interconnection Between LECS Operations Handbook Local Interconnection Servic
19、e Arrangement.2ATIS-0300035, NGIIF Reference Document Part XII- Toll Free Industry Test Plan.2ATIS-0300051, Central Office Code (NXX) Assignment Guidelines.2ATIS-0300082, Guidelines for Reporting Local Number Portability Troubles in a Multiple Service Provider Environment.2ATIS-0300105, NGIIF Auto D
20、ialers Reference Document - Auto Dialers Basics.22This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. ATIS-0300106 3 ATIS-0300209.2003 (R2007), Operations, Administration, Maintenance and Provisioning (OA
21、M Stage 3.43 Definitions, Acronyms, NS/EP (National Security/Emergency Preparedness); NII (National Information Infrastructure); spectrum sharing; radar; radio communications (including HF ALE radio); television (including UHF, VHF, cable TV, and HDTV); facsimile; networks (e.g., intelligent network
22、s, open network architecture, ISDN, broadband ISDN, and network management); fiber optic communications; communications security; data processing; premises wiring; photonics; and telegraphy. The intent is to provide a uniform, up-to-date set of definitions for the general terminology used in telecom
23、munications. Terms and definitions used in this document are aligned with the ATIS Telecom Glossary, which can be accessed online at . 3.1 Acronyms 2) there was inband signaling on the path; 3) SIP-SS7 interworking was not handled properly; or 4) CPN was removed by some entity in the call path. Miss
24、ing CPN may interfere with terminating the call e.g., if anonymous call rejection is engaged. More information can be found in section 7, Existing Regulatory Environment. 4.1.1.2 Bad or Incorrect Caller ID The issue of bad or incorrect Caller ID, as seen by the called party, may be the result when a
25、 CPN, other than that normally associated with the calling party, is delivered to the terminating end office. This may be the result of an entity in the call path explicitly manipulating the CPN, or of a call being terminated and then re-originated in the process of routing to the terminating end of
26、fice. (In the latter case, CPN may be a number associated with the network element that re-originates the call. Note that this differs from call forwarding, which retains the original CPN information in the Original Called Number parameter in the Initial Address Message.) Changes in the CPN delivere
27、d may also interfere with terminating the call. More information can be found in section 7, Existing Regulatory Environment. 4.1.1.3 Identification of the Chargeable Party SS7 Initial Address Messages may also include identification of the chargeable party for the call. When the number to be charged
28、 differs from the CPN, it is carried in the Initial Address Message in the Charge Number (CN) parameter See ATIS-1000113.2.2005 (R2012), section 2.25A, and ATIS-1000113.3.2005 (R2012), section 3.10. Standards provide that where the Charge Number is the same as the CPN, the originating exchange can s
29、ignal just the CPN and a valid OLI parameter ATIS-1000113.2.2005 (R2012), section 2.1.9.3A. In SIP, the mechanism for population of the comparable information is not yet standardized. Therefore, an ISUP-SIP mapping has not been standardized in ATIS-1000679.2004 (R2010). The IETF work developing a P-
30、Charge-Info header draft-york-sipping-p-charge-info-12 (2011-09-15) may form a basis for this in the future. Note also that a SIP mechanism corresponding to the SS7 OLI parameter has not been finalized. See the expired IETF work in draft-patel-dispatch-cpc-oli-parameter-03. Note that while the Calli
31、ng Partys Category (cpc) portion of the IETF work is incorporated into the definition in 3GPP TS 24.229, Annex J, the OLI portion is not. Where signaling from an originating exchange is inband (MF) a billing number (ANI) can be signaled (e.g., from a LEC to an IXC). ANI can be mapped into CN but is
32、not mapped into CPN. 4.1.2 Cause Codes, Tones, for example, incorrect provision of busy tone or number-not-in-service announcements which may mislead callers about the status of the called party, and hinder the carrier maintaining the retail long distance relationship with caller from detecting call
33、 completion problems. 4.1.2.1.5.1 No Circuit Announcement (NCA) This announcement is played when there are no circuits available for the call to be completed. An example of such a recording is as follows: “All circuits are busy now. Please try your call again later”. 4.1.2.1.5.2 Reorder Announcement
34、 (ROA) This announcement is played when a call did not traverse the network to completion for a myriad of reasons. An example of such a recording is as follows: “Were sorry, your call did not go through. Please try your call again later”. 4.1.2.1.5.3 Intercept (INT) This announcement is played when
35、a customer dials a number that has been disconnected or no longer in service. An example of such a recording is as follows: ATIS-0300106 9 “Were sorry, you have reached a number that has been disconnected or is no longer in service. If you feel you have reached this recording in error, please check
36、the number and try your call again”. 4.1.2.1.5.4 Vacant Code Announcement (VCA) This announcement is played when a customer mis-dialed or the NPA/NXX is not valid. An example of such a recording is as follows: “Were sorry; your call cannot be completed as dialed. Please check the number and dial aga
37、in”. 4.1.2.1.5.5 Ineffective Other There should be announcements with the appropriate verbiage for the following situations, and will be determined by the service provider: Prefix or access code dialing irregularity. Improper initial coin deposit. Screened line access denial. Dialing irregularity. A
38、t a minimum, the announcements should include the following information: The call cannot be completed as dialed. Instructions for correct dialing procedures. The customer should try the call again (except for Customer Calling Feature Calling). In addition to announcements, there are instances when t
39、he application of a tone is the applicable treatment for a call. The following clauses describe tones that are normally applied as treatments. 4.1.2.1.5.6 Busy Tone (BT) Busy Tone is applied to an originating customers line when the called party is engaged in another call or the phone is at an off h
40、ook condition. The tone applied to the originating customers line will be at a rate of 60 impulses per minutes (60 IPM). 4.1.2.1.5.6 Reorder Tone (RO) Reorder tone is applied to the originating customers line when the call cannot be completed, which may be due to insufficient facilities. In such ins
41、tances a tone will be applied at a rate of 120 impulses per minute (120 IPM). This tone may be applied in lieu of an announcement. 4.1.2.1.6 Mapping Matrix Indicated below are examples of Cause Codes received by each network or Customer Premises Equipment (CPE) and the Cause Codes sent by each netwo
42、rk or CPE. The Action that generated the Cause Code is listed to indicate the network or CPE where the event occurred (YY and XX represent different Cause Codes): Indicates direction of Cause Code. Indicates direction of Cause Code. ATIS-0300106 10 Arrow facing towards Cause Code indicates Cause Cod
43、e being generated. Arrow facing away from Cause Code indicates Cause Code being passed. Table 1: Examples of Cause Codes Received and Sent by Each Network or CPE XX (message) Cause Code Generated by or Received at Network of CPE XX (action/message) Network or CPE generated Cause Code XX XX (action/m
44、essage) Network or CPE generated Cause Code XX XX (action/message) Network or CPE generated Cause Code XX in both directions XX (action/message) Cause Code XX being passed to next network or CPE XX (action/message) Cause Code XX being passed to next network or CPE XX (action/message) Cause Code XX b
45、eing passed in both directions YYXX (message) Network or CPE receives Cause Code XX from (message) XXYY previous network or CPE and maps Cause Code XX to Cause Code YY At the end office, treat the call per Cause Code XX for analog or Non-ISDN call. 4.1.2.2 Other Applicable Standards Addressing Tones
46、 Reorder Tone; and Special Information Tones. Announcements addressed include: Reorder; No Circuit; Vacant Code; Intercept; and Ineffective Other. This standard also addresses the mapping of Cause Indicator Values specified for the ISDN User Part (ISUP) and Digital Subscriber Signaling System Number
47、 1 (DSS1) in ATIS-1000113.2005 (R2010) and ATIS-1000607.2000 (R2009), respectively, and the tones and announcements identified in this standard. This mapping is for use in call processing involving two or more interconnecting networks (ICNs) when Signaling System Number 7 (SS7) is used for call cont
48、rol. This standard considers the provision of these tones and announcements by originating, intermediate, and terminating ICNs. 4.1.2.2.2 ATIS-1000113, Signaling System No. 7 (SS7) Integrated Services Digital Network (ISDN) User Part The Integrated Services Digital Network (ISDN) User Part defines t
49、he protocol which supports the signaling functions required to provide voice and non-voice services in an Integrated Services Digital Network. This standard is based on the Specification of Signaling System No. 7 for international use issued by ITU-T Study Group 11 in the year 2000 and subsequent amendments. This standard is based on and uses, where applicable, the same signaling procedures, parameters, and message types as the internationally specified ISDN User
