Numbering Guidelines address issues associated with planning, administration, allocation, assignment and use of the North American Numbering Plan (NANP) numbering resources within the NANP area. They are used by the North American Numbering Plan Administration (NANPA), the Number Pool Administration (PA) in the management of numbering resources and the Canadian Radio-Television and Telecommunications Commission (CRTC) in the management of numbering resources.
Many standards, technical requirements, technical reports, bulletins, Best Practices, and annual reports have been published to address network reliability improvement. These documents provide valuable guidance regarding a multitude of industry specific issues. Several are the result of investigating and responding to various FCC issues and concerns regarding network events.
These documents support ordering, billing, provisioning, and the exchange of information relating to interconnection services and other connectivity between telecommunications providers and customers. Specifically, they enable automated exchange of information needed to support Local, Access, and Wireless service ordering, along with the standards for inter-company billing and record exchange, for IP-based and TDM-based networks.
A work program was established to address call termination issues being encountered by rural telephone companies and their customers, including situations in which: the calling party hears ringing but the called party hears nothing (or there is an unusually long call set-up), the called party’s phone rings, but the party hears dead air when the call is answered; or there is extremely poor quality on answerable calls.
As a result of the program, the Intercarrier Call Completion/Call Termination Handbook was developed, which is publicly available from the ATIS Document Center on a complimentary basis. Additionally, an Intercarrier Troubleshooting Quick Reference Tool is also available to assist in troubleshooting call terminations. More information on the program can be found here.
International Mobile Subscriber Identities (IMSI) guidelines and procedures are for the assignment and use of IMSIs in the United States with consideration given to other North American Numbering Plan (NANP) countries. In certain circumstances, these guidelines may also apply to Territories of the United States. The IMSI was created and formatted to provide the unique international identification of mobile terminals and mobile users and to enable these terminals and users to roam among public networks which offer public mobility services.
The ATIS XML Schema Development Guidelines unify the style and maximize the readability, reusability, and the forward and backward compatibility of XML schemas developed in the various ATIS Committees. This document provides recommendations that will help members avoid common pitfalls and choose consistent naming conventions and styles when developing schemas. It is assumed that the reader has a working knowledge of W3C XML Schema and the XML language. The document covers XML schema design, coding, and issues regarding evolution and compatibility of successive schema versions. The recommendations within this document are the result of a collaboration of ATIS Committees and using inputs from other accredited standards organizations.
Cable Reel Identification Codes (Cable Reel ID) identify ownership and reel size. The Cable Reel ID can be utilized by the cable purchaser to track the cable reels from the time they are received and subsequently moved to various transfer points, including company and customer locations, until the empty cable reels are returned to the cable provider. The reels may be those owned by the cable provider or the company purchasing the cable. This identification system can greatly facilitate the return of empty cable reels to minimize the charges imposed by the cable provider when specific cable reels are not returned within a specified time frame. These requirements were developed primarily for cable reels constructed of metallic materials and intended for use as returnable containers. Users may also request a code.