VoIP.infoThe independent guide to business communications.
VoIP.info Guide

Business number porting: a cutover checklist

Keep ownership records, dependencies and a fallback plan aligned with the gaining provider’s process.

Reviewed 2026-10-17Foundational

Inventory before submitting

List every number, current service owner, account details and associated services. Identify numbers used by fax, alarms or other special devices and investigate their supported migration separately. A main number may be bundled with services that need to remain active.

Port the number without losing the route
Keep the old service active while the receiving provider validates the port. Prepare the new inbound route, coordinate cutover and verify incoming calls before closing the old service.

Timing and eligibility depend on carrier and jurisdiction. This is a coordination sequence, not a guaranteed porting schedule.

Coordinate with the gaining provider

Obtain its current requirements, authorization process and confirmed schedule. Do not infer a guaranteed completion date from a generic online estimate. Keep the existing service active until the transfer process and dependencies are understood.

Prepare the destination first

Build and test the new call handling with a temporary or noncritical number. Verify staff devices, opening hours, voicemail and fallback before the published number moves. Confirm emergency-service setup directly with the provider through its approved procedure.

Verify the cutover

Test incoming calls from independent networks, outgoing identity and required special workflows. Keep escalation contacts and account evidence available. Record partial failures and avoid cancelling remaining services until the provider confirms what has transferred and what still depends on the old account.

Jurisdiction and carrier scope

The CRTC reference is Canadian guidance. Portability eligibility, authorization and timing must be confirmed with the receiving carrier for the number and jurisdiction involved. Do not cancel the existing service before coordinating the transfer.

Keep a provider portal claim separate from an accepted port

QuestBlue advertises number search, ordering and real-time porting. The QuestBlue provider record treats those controls as workflow evidence rather than proof of current inventory, eligibility, a completed transfer or the final PBX route. Preserve dated submissions, acceptance, activation and independent inbound tests.

Prepare SIPcity PBX routing before cutover

SIPcity says an active registered or peered PBX receives ported calls automatically at cutover; otherwise calls may reach generic voicemail. Its published reversal or emergency-return window is four hours and availability is not guaranteed. Preserve the SIPcity provider record, scheduled window, portal state, delivered number and rollback contact.

Keep Toku portability attached to number type and market

Toku documents Singapore geographic portability while excluding Level 3 national VoIP portability; the reviewed Malaysia and Indonesia pages also mark portability unsupported. Preserve the Toku provider record, exact number category, subscriber evidence and dated eligibility result.

Bind an IP Telecom portability statement to the exact order

IP Telecom says geographic, non-geographic, DDI and freephone numbers can be ported. The provider record still requires exact eligibility, authorization, accepted date, temporary routing, destination and rollback.

Bind Clearfly number service to the exact order

Clearfly markets local, long-distance and toll-free service. The provider record still requires number eligibility, authorization, accepted port date, delivered identity and destination, temporary routing and rollback.

Control Redcentric number migration as a cutover project

Redcentric includes number migration and management among possible project services. The provider record still requires exact inventory, portability, authority, activation, delivered identity, call flows, temporary routing and rollback.

Do not turn a TelVox number pool into portability proof

TelVox documents dashboard-only DID claiming from an available pool. The provider record still requires country, number type, portability, losing-carrier data, accepted date, routing and rollback evidence for the selected number.

Prepare VoIPline routing without declaring the port complete

VoIPline allows call-flow preparation before port completion and documents a possible cutover interruption. The provider profile preserves acceptance evidence for the active number.

Verify the first Voip Unlimited delivery after the port

Voip Unlimited directs customers to inspect inbound call logs after certain ports. The DDI diagnostic preserves completion, provider attempt, delivered number and PBX route.

Keep a Voipfone port completion separate from routing

A completed port, account registration and number-routing destination are different records. Use the Voipfone diagnostic for the first post-port call path.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Continue your research

Guide

Plan a business phone system

Turn staff workflows and continuity needs into a testable brief for hosted or self-managed VoIP.

Read guide →
Hub

FreePBX

Plan and administer a FreePBX 17 system on Debian 12 using the supported project installation path.

Explore topic →
Interactive tool

Concurrent call planning calculator

Turn an explicit simultaneous-use assumption into a rounded-up external-call scenario.

Open tool →
Provider research · QuestBlue current SIP Trunking, pricing, frequently asked questions, number-porting, Emergency Calling API and customer-support pages reviewed October 13, 2026; public pages do not prove the selected account, order, SIP authentication, registration, inbound format, codec, DTMF, fax, encryption, failover, capacity, emergency entitlement, messaging eligibility, price or support response, and no account, portal, credential, number, port, PBX, SBC, packet, call, media stream, fax, failover event, load test, message or emergency call was inspected or tested

QuestBlue SIP Trunking: connection, number and acceptance boundaries

Keep the portal account, SIP connection, outbound voice profile, numbers, porting, emergency capability, messaging and commercial evidence attached to the selected QuestBlue order.

Read guide →
Provider research · SIPcity SIP Trunking, registration and peering, generic registration, 3CX, network ports and IPs, number-porting, channel, billing and master-service-agreement pages reviewed October 13, 2026; public material does not prove the selected account, order, number inventory, account-specific host, failover behavior, compatibility, negotiated media, fax entitlement, protected path, channel ceiling, call-start rate, price, support response or observed call result, and no account, portal, credential, number, PBX, packet, call, media stream, fax, failover event, load exercise, message or emergency call was inspected or tested

SIPcity SIP trunks: registration, peering and 000 boundaries

Keep SIPcity credential registration, static-IP peering, DID routing, published media parameters, channel entitlement and Australian 000 dependencies attached to the selected order.

Read guide →
Provider research · Toku Carrier Services, Microsoft Teams, Voice Connectivity, Singapore, Malaysia and Indonesia number, Singapore subscriber, portability, regulation and wholesale pages reviewed October 14, 2026; public material does not prove the selected account, universal SIP authentication or registration, DID inventory, customer failover contract, generic trunk encryption, fax, account capacity, price, compatibility, support response or observed call result, and no account, order, credential, trunk, number, PBX, SBC, packet, call, media stream, fax, failover event, load exercise, message or emergency call was inspected or tested

Toku carrier voice: APAC numbers, media and country boundaries

Keep Toku carrier coverage, selected-country numbering, E.164 delivery, media capabilities, purchased channel capacity and emergency rules attached to the exact market and order.

Read guide →
Provider research · Current IP Telecom SIP Trunks, SIP Trunking product terms, Fair Use Policy, Ireland copper-transition and contact pages reviewed October 15, 2026; authentication method, registrar and proxy values, DNS behavior, technical routing, codecs, DTMF, RTP addresses, fax, emergency calling, messaging, exact failover, capacity entitlement, availability, compatibility, pricing and support performance remain order specific, and no account, quote, credential, number, port, PBX, endpoint, access circuit, packet, media stream, failover event, load exercise, message, emergency call or live call was inspected or tested

IP Telecom SIP trunks: Irish service, resilience and demarcation boundaries

Scope IP Telecom channel capacity, number porting, access resilience, optional TLS and SRTP, provider demarcation and unresolved technical handoff to the exact Irish business order.

Read guide →
Provider research · Current Clearfly service, FAQ, partner, support and legal pages reviewed October 15, 2026; authentication, registrar and proxy values, DNS behavior, codecs, DTMF, RTP ranges, signaling and media protection, T.38, emergency behavior, capacity limits, routing triggers, current availability, compatibility, exact pricing and support performance remain order specific, and no account, quote, credential, number, port, PBX, endpoint, circuit, portal session, packet, media stream, failover event, load exercise, message, emergency call or live call was inspected or tested

Clearfly SIP trunking: service scope, portal controls and acceptance boundaries

Scope Clearfly trunk quantity, number services, routing features, portal controls, support and unresolved technical handoff to the exact partner-managed order.

Read guide →
Provider research · Current Redcentric voice-modernisation, communications, support and status pages reviewed October 15, 2026; the public SD032 v2.1 PDF is retained only as a legacy service-design reference, not a current contract or topology. Authentication, registrar and proxy, DNS, codecs, DTMF, RTP, TLS and SRTP, capacity, fax, messaging, emergency process, pricing, SLA, availability and compatibility remain order specific. No account, quote, order, credential, trunk, number, port, PBX, SBC, circuit, portal session, packet, media stream, failover event, emergency call or live call was inspected or tested

Redcentric SIP trunks: managed migration, circuit dependency and acceptance boundaries

Scope Redcentric SIP trunks to the exact managed-voice order, current handoff, circuit design, number migration, cutover and support responsibilities.

Read guide →
Provider research · Current TelVox Connect trunk, authentication, call, number, recording, webhook, pricing and security documentation plus Renav Limited company identification reviewed October 16, 2026; Connect is live but its API is v0.x, and coverage, portability, emergency calling, fax, messaging, codecs, DTMF transport, RTP, media protection, redundancy, concurrency, call-start limits, availability, compatibility, exact pricing and support performance remain account, order, route or version specific; no account, API key, trunk, SIP credential, number, registration, webhook, callback, recording, packet, media stream, emergency call or live call was inspected or tested

TelVox Connect SIP trunks: provisioning, credentials and call evidence

Separate TelVox API access, trunk lifecycle, SIP registration, webhooks, callbacks and call outcomes while keeping pre-v1 and account-specific limits explicit.

Read guide →
Provider research · Current VoIPline Telecom Australian SIP-trunk product, pricing, legal index, Voice and SMS (IP) service schedule, SIP-trunk critical-information summary, network, number-porting and service-status material reviewed October 16, 2026. Registration, SIP URI diversion and Microsoft Teams gateway are documented as distinct operation modes; the service schedule documents public-internet and private-IP delivery, ordered concurrent-call channels, default bidirectional service and selected codec boundaries. The selected order, registrar values, number inventory, caller identity, routing, DTMF, fax, messaging, emergency service, signaling and media protection, failover, price, SLA, availability and compatibility remain order, location, contract or observation specific. No account, order, credential, trunk, number, registration, port, packet, media stream, emergency call or live call was inspected or tested

VoIPline Telecom SIP trunks: modes, channels and call evidence

Qualify one Australian VoIPline SIP trunk by its ordered operation mode, interconnect, channels, numbers, caller identity, negotiated media, contractual boundary and observed calls.

Read guide →
Troubleshooting · Current VoIPline Telecom Australian SIP-trunk product, pricing, legal index, Voice and SMS (IP) service schedule, SIP-trunk critical-information summary, network, number-porting and service-status material reviewed October 16, 2026. Registration, SIP URI diversion and Microsoft Teams gateway are documented as distinct operation modes; the service schedule documents public-internet and private-IP delivery, ordered concurrent-call channels, default bidirectional service and selected codec boundaries. The selected order, registrar values, number inventory, caller identity, routing, DTMF, fax, messaging, emergency service, signaling and media protection, failover, price, SLA, availability and compatibility remain order, location, contract or observation specific. No account, order, credential, trunk, number, registration, port, packet, media stream, emergency call or live call was inspected or tested

VoIPline trunk registers but calls or audio fail

Separate operation mode, interconnect, number and caller-identity routing, channel scope, SIP response, SDP and both media directions before changing credentials or firewall rules.

Read guide →
Provider research · Current public Voip Unlimited SIP-trunk, voice, partner, legal and Master Services Agreement V3.0 material plus RFC 3263, RFC 2782 and RFC 3403 reviewed October 17, 2026. The SIP service schedule defines a trunk as one registration containing one or more channels, describes account-issued credential details, headline-number and DDI alias routing, portal diversion, non-registration SMS alerts, porting checks and emergency-address obligations. Public product material documents SIP Lite, SIP Unlimited, Bundle Plus, NAPTR, SRV, IPv6, SRTP and T.38-bypass concepts. The selected order, issued registrar and credentials, active binding, assigned and ported numbers, delivered identities, PBX routes, caller identity, codec, DTMF, negotiated protection, fax outcome, DNS answers, access path, service incident, price, availability and compatibility remain account, contract or observation specific. No account, order, portal, credential, PBX, trunk, number, port, resolver, packet, media stream, fax, emergency call or live call was inspected or tested

Voip Unlimited SIP trunks: registration, DDI routing and call evidence

Qualify one Voip Unlimited SIP service by its issued registration, channel model, headline number, DDI aliases, DNS path, portal controls, negotiated media and observed calls.

Read guide →
Troubleshooting · Current public Voip Unlimited SIP-trunk, voice, partner, legal and Master Services Agreement V3.0 material plus RFC 3263, RFC 2782 and RFC 3403 reviewed October 17, 2026. The SIP service schedule defines a trunk as one registration containing one or more channels, describes account-issued credential details, headline-number and DDI alias routing, portal diversion, non-registration SMS alerts, porting checks and emergency-address obligations. Public product material documents SIP Lite, SIP Unlimited, Bundle Plus, NAPTR, SRV, IPv6, SRTP and T.38-bypass concepts. The selected order, issued registrar and credentials, active binding, assigned and ported numbers, delivered identities, PBX routes, caller identity, codec, DTMF, negotiated protection, fax outcome, DNS answers, access path, service incident, price, availability and compatibility remain account, contract or observation specific. No account, order, portal, credential, PBX, trunk, number, port, resolver, packet, media stream, fax, emergency call or live call was inspected or tested

Voip Unlimited trunk registers but inbound DDI calls fail

Follow one affected DDI from provider assignment, port and headline alias through the registered Contact, first INVITE, PBX identity match, loaded route, destination and caller outcome.

Read guide →
Troubleshooting · Current first-party Voipfone registration, third-party PBX, number-routing, call-divert, porting, emergency-address and terms documentation reviewed October 17, 2026. Account-number registration, telephone-number routing, PBX delivery and customer-side fallback remain separate controls. Portal labels and legacy chan_sip examples do not establish a current PJSIP profile, one universal delivered DID form or the behavior of an uninspected account. No account, credential, number, port, route, divert, extension, PBX, registration, provider attempt, packet, media stream, emergency workflow or live call was inspected or tested

Voipfone inbound number or fallback is wrong

Trace one inbound call through telephone-number routing, account registration, provider delivery, PBX matching, divert precedence, fallback and media.

Read guide →