Converting a P2P number to an A2P number

More and more customers are needing to move from P2P to A2P messaging as mobile carriers (operators) want their customers to use A2P messaging.

Sinch allows you to migrate your P2P numbers to A2P numbers with no disruption in your services. Follow the steps outlined below.
 

Customer Requirements

Before you, can migrate your P2P number(s) to A2P number(s) you need to have the following:

• P2P NNID with A2P exceptions.
  Note: For T-Mobile numbers this will need to be provisioned with T-Mobile.

• Active CampaignID that has been registered with the Campaign Registry (TCR) and approved by Sinch as the DCA (Direct Connectivity Aggregator).
   

Testing and Processing Steps

Step 1 - Update or validate the Override Service Registry (OSR) database to see there is a P2P NNID (with A2P exception) updated in the OSR database.

Step 2 – Send test MO and MT to see if they work.

Step 3 - If your testing is successful, import your number(s) using the Import number API or you can import number using the Sinch Build Dashboard. Ensure you link the number(s) to an active and approved campaign where Sinch is the DCA. This step (using the API or Dashboard processes) will also update the SMS App ID as part of same process (which is a prerequisite).

Step 4 – Again send test MO and MT to see if they work.

Step 5 - If your testing is successful, update the OSR with the CampaignID, A2P context and change to the new A2P NNID.

Note: You can use NetNumber APIs to complete this update process.

Step 6 - Again send test MO and MT to see if they work.

We recommend you complete these test and processing steps for several numbers to determine everything is working properly, and then you can use the simplified process below for the rest of your numbers.
 

Simplified Process once you have completed testing

Step 1 - Import your number(s) using the Import number API or you can import number using the Sinch Build Dashboard. Ensure you link the number(s) to an active and approved campaign where Sinch is the DCA. This step (using the API or Dashboard processes) will also update the SMS App ID as part of same process (which is a prerequisite).

Step 2 - Update the OSR with the CampaignID, A2P context and new A2P NNID.
 

Click here to learn more about how you can get access to a complete range of carefully-tested phone numbers, to use with all your communication services from Sinch.