Port a US toll-free number to DIDHub

US toll-free porting is a RespOrg change in SOMOS, not a normal LNP order. This tutorial covers the LOA fields, RespOrg handoff, FCC rules, and expected timeline (typically 3-7 business days).

What you need before you start

• A copy of your most recent toll-free invoice (must show the number and current carrier name).
• The customer of record's billing address — must match the losing carrier's records exactly.
• A signed Letter of Authorization (LOA) on the customer's letterhead.

Step 1: Submit the porting request

Dashboard → Numbers → Port In → US Toll-Free. Fill:

Step 2: DIDHub submits to SOMOS

Within 1 business day DIDHub files the RespOrg change in SOMOS. The losing RespOrg has 5 business days to respond (accept, reject, or no-response = auto-accept).

Step 3: Schedule the activation window

Once accepted, you can schedule the cutover. Recommended: a 30-minute window during low traffic. Cutover is effectively instant once DIDHub becomes the RespOrg.

Step 4: Configure routing in DIDHub before the cutover

Routes are pre-configured but inactive. The minute the cutover lands, traffic flows. Pre-configure either:

• SIP trunk routing (most common)
• Microsoft Teams Direct Routing (see tutorial — same flow for US)
• IVR / forwarding to a fallback PSTN number

Common reasons US toll-free ports get rejected

• "CSR mismatch": service address on LOA does not match losing carrier records. Pull a current CSR (Customer Service Record) from the losing carrier first.
• "PIN required": some RespOrgs require a customer-set PIN before releasing. Get the PIN from your losing carrier's portal.
• "Pending order": there is an open order (e.g. feature change, upgrade) that must complete first.