Numbers that connect to your voice platform.
Plan local and international numbering with routing, documentation and inbound delivery in mind.
| Number / market | Type | Assigned route | State |
|---|---|---|---|
| +1 212 555 0104 | Local | Demo trunk A | Assigned |
| +1 305 555 0112 | Local | Demo trunk B | Assigned |
| +44 · masked example | Geographic | Unassigned | Review |
| +49 · masked example | Geographic | Demo trunk C | Assigned |
Number coverage is more than a country list.
Choose the number type around the use case
A local presence, a national contact number and a toll-free service can have different reachability, documentation and charging rules. Specify the country, locality and intended use first. Then confirm the number type and inbound delivery needed by your platform. Availability must be checked for the actual request.
Treat setup charges, recurring rental and inbound usage as separate commercial items. If numbers will be assigned to end customers, establish who supplies end-user information, who maintains it and who is authorized to request changes.
Manage the full number lifecycle
Provisioning is only one stage. Record the customer assignment, receiving trunk, application owner and release process for every number. Include port-in dependencies and service activation in the same operational record so the commercial and technical states do not drift apart.
For a port, validate the existing service record and authorization requirements with the responsible team. Keep existing service in place until the agreed completion. After activation, test incoming calls and the application that receives them before closing the migration.
Where it fits in your network
- 01Calling party
- 02DID number
- 03Number routing
- 04Your application
Plan the connection around your traffic
Coverage by number type
Confirm local, national, mobile or toll-free availability for the exact market and use case.
Provisioning requirements
Check end-user documentation, address requirements and permitted use before assigning numbers.
Routing and lifecycle
Document the receiving trunk, assignment owner and release process. Keep porting dependencies visible to operations.
Agree the details before production
| Parameter | Planning detail |
|---|---|
| Inventory | Live availability and pricing are confirmed through your account workflow. |
| Markets | Request coverage by country, locality and number type. |
| Portability | Confirm eligibility and authorization before scheduling. |
| Charges | Review recurring, setup and inbound usage charges separately. |
What to review with your team
| Review area | What to establish |
|---|---|
| Coverage request | Country, locality, number type, quantity and intended use. |
| Delivery mapping | Receiving SIP trunk, application and ownership record. |
| Lifecycle | Documentation, activation, porting and release responsibilities. |
Before the next step
Does the map show live number inventory?
No. The illustration is conceptual. Number availability, documentation and prices are confirmed for the selected market and request.
Can every number receive the same services?
No. Voice reachability and other capabilities vary by number type and market. Confirm every required capability before purchasing or porting.
Choose the number before choosing the workflow
A DID is an address into a communications service. Its value depends on the callers it needs to reach, the number type and the application that receives calls. Begin with the country, locality and use case: a local customer-service line, a direct number for a user or an inbound entry point for a platform. Then confirm availability and permitted use.
Local, national and toll-free products can carry different rules and charges. A number’s voice capability does not automatically establish messaging or other features. Keep those requirements separate in the request so the proposed service matches what you will advertise to your customers.
Inventory is more than a list of digits
Each number should have an assignment owner, a receiving destination and a lifecycle state. That record helps your team answer practical questions: who uses this number, where should its calls go and can it be released? Keep the commercial record connected to the routing record so a canceled service does not retain an unexpected number charge.
The sample interface illustrates that relationship without presenting live inventory. A real availability check happens through the approved sales or account process. If you are building provisioning automation, use the confirmed integration specification rather than treating a visual example as an API promise.
Move numbers without losing the customer journey
A port changes service responsibility; it does not automatically recreate greetings, queues or forwarding rules. Build the receiving call flow before the agreed activation window. Validate the current account information and authorization, and identify a person who can test the business outcome immediately after the change.
After activation, place external test calls and verify the number reaches the correct application. Keep the prior service active until completion is established. For inbound delivery behavior, continue to voice origination; for the migration sequence, use the porting checklist.
Questions about this service
Can I reserve the numbers shown in the example?
No. The illustrated numbers are reserved examples or masked values. Request actual availability through the sales or account workflow.
Does a voice DID automatically support messaging?
No. Confirm each required capability for the number type and market before building or selling a service around it.
When should I cancel the old service during porting?
Keep it active until the agreed port completion and test the receiving call flow. Coordinate any remaining dependencies with the existing provider.
From available inventory to a working call path.
- 1
Check availability
Confirm market, number type and required capabilities.
- 2
Validate the record
For ports, reconcile authorization and account information.
- 3
Configure delivery
Map the number to the approved SIP destination.
- 4
Test and accept
Call the number and validate the receiving application.
Port timing and inventory depend on the selected service. See number-porting preparation.
A number is ready when its destination is ready
Consider an application adding a customer number. Availability is checked for the required market and capabilities. Once the number is assigned through the agreed process, the application maps it to the correct tenant or receiving service. That mapping must be checked independently of the inventory entry.
The final test calls the number from an external origin and confirms the expected destination, identity handling and two-way audio. If the number appears in inventory but the customer never rings, investigate the assignment and application routing separately. Keep a record of the number owner and service association so future changes do not leave orphaned routes. This is an illustrative provisioning workflow.