Get Involved with ATIS Committees
New participation in ATIS Committees is always welcome. If you or anyone you know would be interested in getting involved with the work outlined in this Report, please contact Rich Moran, ATIS Membership Director.
Click on a committee name below to display this month's issues.
NGIIF: Next Generation Interconnection Interoperability Forum
- Issue: 0070
- Title: Update ATIS-0300046, Recommended Notification Procedures to Industry for Changes in Network Routing Architecture
- Statement: Update ATIS-0300046, Recommended Notification Procedures to Industry for Changes in Network Routing Architecture. CIGRR has reviewed and is recommending changes to industry routing timelines to be more consistent with the timelines the industry is using to make routing modifications.
- Resolution: NGIIF updated Attachment A of ATIS-0300046, Recommended Notification Procedures to Industry for Changes in Network Routing Architecture, per feedback provided by CIGRR.
- Status: Final Closure
For more information, visit the NGIIF home page or contact Anna Karditzas.
PTSC: Packet Technologies and Systems Committee
- Issue: 0161
- Title: Poison Control Center Call Routing
- Statement: Legislation enacted in 2019 amended the federal Public Health Service Act to give the U.S. Department of Health and Human Services (HHS) responsibility “to the extent technically and economically feasible, to ensure that communications with the national toll-free number are routed to the appropriate poison control center based on the physical location of the contact rather than the area code of the contact device.” The communications industry should support HHS’s effort to address this important public policy issue.
Some calls to the Poison Control Center Hotline toll-free number are routed to the poison control center other than the center serving the state in which the caller is located, because the NPA-NXX information associated with the call and provided by the originating service provider does not correspond to the caller’s location. This is in part due to the mobile and nomadic capabilities of wireless and Voice over IP (VoIP) services that enable a user to originate calls from outside the geographic area associated with the NPA-NXX in the user’s 10-digit NANP telephone number. Today, the Toll Free routing platform, by design and in accordance with direction from HHS, is dependent on the NPA-NXX data provided from other carriers passed in either the JIP, Charge Number, or Calling Party Number in order to route calls based on the caller’s location. Some carriers have mechanisms to approximate physical location, while others may not. The NGIIF Reference Document documents Rules for Populating the JIP. This and other methods should be reviewed to ensure originating carriers are providing accurate location information for both wireline and wireless calls, to the extent technically and economically feasible.
- Resolution: The PTSC conducted an extensive analysis of the Poison Control Center (PCC) call routing issue and determined that in order to resolve this issue, it would be necessary to either take a more granular approach to call routing (e.g. local call routing rather than interexchange toll-free), similar to how certain N11 calls are handled, or re-engineer how JIP might better represent the location of the calling party. JIP is an available approach that requires no standards changes, but is a legacy parameter originally designed to manage number portability and carrier billing and is not implemented consistently within the industry. Use of an abbreviated dialing code as a potential longer-term solution was considered, however significant changes would need to be made across the existing PCC routing implementation to allow more granular routing. The efforts necessary to implement a new 3-digit code would also divert attention and resources from regulatory compliance mandates like STIR/SHAKEN and implementation of 988. Although no changes to the current ATIS documentation to resolve the location granularity issue have been identified, it was determined that the protocol mechanism to transmit JIP between service providers is working as documented in the standards. The PTSC notes that this issue could potentially be revisited in the future as the FCC considers related issues in the 988 context that may be relevant to PCC call routing as well. This Issue was placed into Initial Closure with no changes to PTSC guidelines.
- Status: Initial Closure
For more information, visit the PTSC home page or contact Anna Karditzas.
- New Issue: Business, operational, or technical needs that a committee has reached consensus to address.
- Issue in Initial Closure: Issues for which a committee has reached consensus on a proposed resolution. The industry has a 21 calendar day period to review and comment on the consensus resolution developed by the committee. The committee's consensus resolution concludes its work on an issue unless new or substantive information is brought forth. During the 21 day review period, comments on a consensus resolution may be provided to the committee contact and committee leaders.
- Issue in Initial Pending: Issues previously in Initial Closure for which new and substantive information impacting the consensus resolution has been received. An issue may also be in Initial Pending if output that may impact the consensus resolution is expected from another industry group, regulatory body or similar organization.
- Issue in Final Closure: Issues for which work is completed and the resolution accepted by the industry.
Recently Approved ATIS Standards
- Document Number: ATIS-0300046(2022-05)
- Title: Recommended Notification Procedures to Industry for Changes in Access Network Architecture
- Type: Revision
- View on ATIS Workspace
Recent Policy Filings