Current Location ：
Porting Numbers to a New Provider: A Risk-Free Planning Guide
Number porting is the step most likely to cause a lost day of business, because it depends on paperwork that is easy to get subtly wrong and impossible to fix quickly. The porting reference must match the current carrier's record exactly, including punctuation. A mismatch does not produce an error message at submission; it produces a request sitting unprocessed until someone chases it on the day of the cutover.
What the Chasing Party Actually Needs
| Detail | Common source of error | How to verify |
|---|---|---|
| Current carrier name | Trading name versus legal entity name | Check the current bill, not the website |
| Account or customer reference | Multiple numbers on one account share a reference | Confirm with the current provider in writing |
| Individual circuit references | Reference covers one circuit, not all numbers | Request the full list of circuit references |
| Exact address format | Punctuation, spacing, and abbreviation differences | Copy exactly from the invoice |
| Service type | Analogue versus VoIP, and SIP versus ISDN | Confirm the underlying service type |
| Number list | Ranges versus individual numbers | List every number individually |
Lead Times and the Real Cutover Window
Porting lead times vary considerably by carrier and by service type, and the published figure is often the best case rather than the typical case. Two weeks is commonly assumed and can be optimistic for complex numbers. Build the plan so that the port completes comfortably before the deadline, and confirm the earliest and latest acceptable cutover date in writing with the receiving provider.
Interim Routing
The safest cutover pattern is interim routing: the current carrier forwards calls to the new provider while both trunks are live. This gives a testing window before the port completes and a fallback if something is wrong. It costs a small forwarding fee, and it converts a high-risk cutover into a staged change.
The Testing That Must Happen Before Cutover
- Inbound calls from an external line to every number in the port
- Outbound calls from every extension with caller ID showing the correct number
- Fax transmission, if fax numbers are included in the port
- Emergency calling from each site, with registered addresses updated
- Recording and voicemail behaviour for calls to each number
- Caller ID presentation on outbound calls, since presentation errors are common after porting
- Toll-free and premium rate numbers, which follow different porting rules
Common Failures and Their Causes
| Symptom | Likely cause | Prevention |
|---|---|---|
| Port rejected or stalled | Reference or address does not match the carrier record | Verify details with the current provider before submitting |
| One-way audio after cutover | Codec or NAT settings not aligned on the new trunk | Test a representative call before final cutover |
| No caller ID on outbound | Caller ID presentation not enabled on the new trunk | Confirm presentation settings during testing |
| Some numbers missing | Ranges listed instead of individual numbers | List each number explicitly |
| Fax broken | T.38 not supported on the new carrier | Verify T.38 before cutover, not after |
Redstone Approach
Redstone supports number porting by preparing trunk provisioning against the ported numbers, configuring number presentation and routing on the Redstone IP-PBX, and testing each number before the current service is released. Redstone can also sequence the migration so that new numbers are proven in service before old service is cancelled, avoiding any window with no working numbers.
Redstone provides porting coordination support, including trunk configuration, per-number verification, and a cutover sequence that keeps every number in service throughout the change.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
