1. Overview
This KB defines the process for procuring different types of numbers — including Long Codes (LC), Toll-Free Numbers (TFN), International Numbers, Short codes, Alpha Codes, and Canadian Numbers.
2. Scope
This KB applies to the Teir-1 Support team responsible for number procurement and publishing. It covers both domestic (U.S. and Canada) and international procurement workflows.
3. Requirements
Before beginning procurement, ensure access to:
- Inteliquent Portal (credentials required)
- Tata Communications Support Portal or email: cis-support-amer@tatacommunications.com
- Aerialink V5 Portal for publishing and testing numbers
- Local Calling Guide: https://www.localcallingguide.com
- Active Zendesk ticket containing:
- Area code or prefix requested (Optional)
- Destination country (for international)
- Traffic type (for international)
- Brand name and purpose of number (for international)
- Expected message volume (for international)
4. Process
A. Procuring Long Code (LC) from Inteliquent Portal
Part 1 – When Requested Area Code Is Available
- Log in to the Inteliquent Portal with valid credentials.
2. Navigate to Home → Order Numbers.
3. Check if the requested area code is available.
- If available, proceed to reserve the long code.
- If not, request an alternate area code from the customer.
4. Select the Routing Option, then click Next.
5. On the Order Telephone page, click Next, then Save Order.
6. Verify activation by navigating to Search Assigned Numbers.
Part 2 – When Requested Area Code Is Not Available
- Open the Local Calling Guide at https://www.localcallingguide.com/lca_prefix.php.
- Enter the NPA (Area Code) or NXX (Prefix).
- Click Submit.
4. From the results, note a valid Rate Center or LATA code.
5. Return to Inteliquent Portal → Order New, and enter the Rate Center/LATA.
6. Repeat the same process as in Part 1, Steps 3–7 to complete the order.
B. Procuring Toll-Free Number (TFN) from Inteliquent Portal
Part 1 – Procuring a TFN
- Copy the customer request prefix.
- Log in to Inteliquent Portal → TN Order.
- Follow the same steps as Long Code Procurement (Part 1, Steps 3–7).
Part 2 – Ordering a TFN
- Copy the customer request prefix.
- After logging into the portal, navigate to Toll-Free Order.
- On the next page, click Next.
- Under Order Details, select the correct routing RespOrg ID.
- Complete the order and verify confirmation.
C. Procuring and Provisioning an International Code
Step 1: Submit Request
- Identify the customer’s requirement from the Zendesk ticket.
- Ensure the following details are provided:
- Destination Country (e.g., Ireland)
- Type of Traffic (Transactional/Promotional)
- Brand Name (e.g., Gerry O’Carroll Photography)
- Expected Monthly Volume (~2,000 messages)
- Purpose of the Number (e.g., confirmation messages, preparation details)
Reference Zendesk ticket# - https://goconvey.zendesk.com/agent/tickets/9386
Step 2: Open a Case with Tata Communications
- Submit the request via the Tata Communications Support Portal or email:
cis-support-amer@tatacommunications.com. - Record the Case/Ticket ID (e.g., INC0320190).
- Maintain consistent follow-up and communication with Tata.
- Request an estimated completion timeline.
Step 3: Number Procurement Confirmation
- Once provisioned, Tata Communications will send a confirmation email with:
- The procured number (e.g., 353861978194)
- Confirmation of functionality
- Verify the details:
- Number format
- Correct destination country
Step 4: Configure the International Number
- Log in to the Aerialink V5 Portal and switch account where you want to publish the international number.
- Navigate to Code Management, then click the “+” icon to publish the number.
- Follow the table below when you publish an International number.
For International
| Field | Description / Selection |
| Codes (Requested Numbers) | (Ordered numbers) |
| Connection | As requested by the customer |
| Code Type | LC/TFN - Leased |
| Code Source | CLX International |
| Item Code | LC-INTL |
| Number | (Leave blank) |
| ESPID | NA |
| TON | International |
| NPI | 1 (Keep NPI value always 1) |
| Provider | A2P-INTL-T-CLX International –A2P Transactional Traffic |
| Campaign ID | N/A |
- Conduct a test message using:
“How to Send a Test Message in Telq – Aerialink Operations – Confluence.” - Confirm that the international number is fully functional.
D. Procuring and Provisioning an Alpha Code
Step 1: Submit Request
- Identify the customer’s requirement from the Zendesk ticket.
- Ensure the following details are provided:
- Destination Country (e.g., Ireland)
- Type of Traffic (Transactional/Promotional)
- Expected Monthly Volume (~2,000 messages)
- Purpose of the Number (e.g., orders management details)
Step 2: Open a Case with Tata Communications
- Submit the request via the Tata Communications Support Portal or email:
cis-support-amer@tatacommunications.com. - Record the Case/Ticket ID (e.g., INC0276027).
- Maintain consistent follow-up and communication with Tata.
- Request an estimated completion timeline.
Step 3: Number Procurement Confirmation
- Once provisioned, Tata Communications will send a confirmation email with:
- The procured number (e.g., NICWEBPHOTO)
- Confirmation of functionality
- Verify the details:
- Number format
- Correct destination country
Step 4: Configure the Alpha Number
- Log in to the Aerialink V5 Portal and switch account where you want to publish the international number.
- Navigate to Code Management, then click the “+” icon to publish the number.
- Follow the table below when you publish an Alpha number.
For Alpha Code
| Field | Description / Selection |
| Codes (Requested Numbers) | (Ordered numbers) |
| Connection | As requested by the customer |
| Code Type | ALPHA-Leased |
| Code Source | AlphaNumeric Defined (A2P INTL only), any provider |
| Item Code | LC-INTL |
| Number | (Leave blank) |
| ESPID | NA |
| TON | Alphanumeric |
| NPI | 1 (Keep NPI value always 1) |
| Provider | (Source Provider) |
| Campaign ID | N/A |
E. Procuring and Provisioning an Short Code.
Step 1: Short Code Procurement (Compliance)
To initiate Short Code procurement, reach out to the Compliance team.
The Compliance team is responsible for:
Short Code application submission
Use-case and content review
Carrier approval coordination (US/Canada)
Proceed to provisioning only after Compliance confirms the Short Code has been approved and is ready for publishing.
Step 2: Short Code Provisioning (Provisioning Team)
Once the Short Code is approved, compliance Team will reach the Provisioning team to publish the Short Code using the configuration details below.
Required Configuration Details:
Use the following values as reference from the shared configuration table:
-
CodeType ID
3 – SC US/CAN
-
CodeSource ID
800 – CSCA, Common Short Code United States801 – CWTA, Common Short Code Canada
-
Item Code (as applicable)
103 – SC-USA-SHARED104 – SC-USA-DEDICATED-RANDOM105 – SC-USA-DEDICATED-VANITY106 – SC-CANADA-DEDICATED107 – SC-INTL-SHARED108 – SC-INTL-DEDICATED
-
Provider (select based on ShortCode procured)
7 – mGage Primary SMS16 – mGage (SF Connection)24 – Sinch SC SMS
-
ESPID
CSCA
-
TON / NPI
TON:
3NPI:
1
F. Procuring and Provisioning an Canadian Code
Step 1: Procuring a Canadian Number (EspressoDID – Iristel)
Log in to the EspressoDID portal (Iristel).
Navigate to DID Orders.
Click Add Orders.
Select the appropriate Routing Profile.
Click Add New Product.
From the Region dropdown, select the required Canadian region.
Enter the Quantity of numbers requested.
Click Create Order to submit the request.
Once the order is completed, confirm that the numbers are successfully allocated.
Step 2: Provisioning the Canadian Number
For provisioning the Canadian number, refer to the Provisioning KB article in Zendesk that outlines the standard number provisioning process.
Important Exception – Canadian Numbers
Canadian numbers do not require Campaign ID linking.
Do not associate or publish Canadian numbers against any Campaign ID during provisioning.
Ensure all campaign-related steps in the referenced Zendesk KB are skipped for Canadian numbers.
Note
For all number procurement and publishing activities, it is strongly recommended to perform end-to-end testing before notifying the customer.
Validate MT (Mobile Terminated) message delivery
Validate MO (Mobile Originated) message reception
Confirm routing, delivery status, and overall message flow
Only tell the customer the number is ready after MT and MO testing works successfully.
Comments
0 comments
Please sign in to leave a comment.