IP transition checklist

April 10, 2026

There's been an uptick in activity to clear regulatory obstacles and accelerate the transition from TDM to IP interconnections in the U.S. voice network. If these efforts are successful, would your voice service provider business be ready for copper retirement? Here's a checklist of things we think you should plan for.

This list is focused on services you currently provide using TDM-related facilities, which you might need to replicate in an IP environment, and new services to be performed on those calls. Let's take a look.

Location Routing Number (LRN) lookup

If you originate calls from a TDM switch, then your switch might perform LRN lookups. You would need to provision LRN lookups on the SIP-capable switch. You might have arranged this already, but it should be on your checklist to confirm.

CNAM lookup

If you terminate calls on a TDM switch, then the switch might perform CNAM lookups. You would need to provision CNAM lookups on the SIP-capable switch—another item for the checklist.

Branded caller name display at call termination

You may be able to reduce the number of CNAM lookups you make by provisioning the display of the branded caller name. For example, calls sent with Branded Caller ID^™ information provide the caller's name in a secure, verified format within the STIR/SHAKEN framework. This information is available to you at no charge.

If you register as a BCID-authorized Terminating Service Provider, you can get paid for sending the branded calling information to your subscribers' handsets. That's right—get paid for displaying secure, vetted, trustworthy information instead of paying for CNAM.

STIR/SHAKEN

Calls originated and terminated on an IP network must be authenticated and verified using the STIR/SHAKEN framework. Your STIR/SHAKEN solution for IP calls should be able to handle this, and it should be on your checklist to confirm.

Do-Not-Originate (DNO) blocking

Terminating Service Providers are required to block calls that originated with calling numbers that are on a reasonable Do-Not-Call list or are invalid or unassigned. You should include this on your checklist.

SIP 603+ blocking notification and redress

Regulations allow service providers to block calls that are likely to be illegal based on reasonable analytics. Most subscribers want their voice service providers to block such calls.

Recent regulations require service providers to return a SIP 603+ immediate blocking notification message for calls that they blocked using analytics. You should put this on your checklist.

Businessman planning with notes on a whiteboard

TransNexus solutions

Our ClearIP and NexOSS software platforms provide turnkey solutions for all the checklist items listed above. We can make it quick and easy for you to get ready for the completion of your IP transition.

More information

TransNexus is a leader in developing innovative software to manage and protect telecommunications networks worldwide. The company has over 25 years of experience in providing telecom software solutions including toll fraud prevention, robocall mitigation and prevention, CDR and call analytics, advanced call routing, billing support, STIR/SHAKEN, and branded calling.

This information will only be used to respond to your inquiry. TransNexus will not share your data with any third parties. We will retain your information for as long as needed to retain a record of your inquiry. For more information about how we use personal data, please see our privacy statement.