Porting numbers to Webex Calling

See also

Sources

1. 1
   When adding numbers in Control Hub, an admin can turn on 'Activate Numbers Later'. The numbers can then be configured immediately but stay inactive, and the article says to contact the carrier to activate them. Cisco presents this option for numbers the admin plans to port later.

   Manage phone numbers in Control Hub · section 'Add phone numbers' · Checked 2026-09-25
2. 2
   A Cisco Calling Plan port can be requested for any time within the supported porting window of 9 AM to 4 PM on regular business days, but the time is not guaranteed until FOC.

   Cisco Calling Plan number porting guidelines and policies · section 'Requested port date and time' · Checked 2026-09-25
3. 3
   A single Control Hub add-numbers action accepts up to 1,000 comma-separated numbers.

   Manage phone numbers in Control Hub · section 'Add phone numbers' · Checked 2026-09-25
4. 4
   After port activation, Cisco says to allow at least 15 minutes (30 minutes for project or complex ports) before the numbers start working.

   Cisco Calling Plan number porting guidelines and policies · section 'Port activation and postport advice' · Checked 2026-09-25
5. 5
   The carrier bill uploaded with a Cisco Calling Plan port order must be dated within the last 30 days; Control Hub accepts it as PNG or PDF.

   Get Started with the Cisco Calling Plans · section 'Port in phone numbers', step uploading the previous carrier bill · Checked 2026-09-25
6. 6
   The BTN on a Cisco Calling Plan port order must match the losing carrier's records exactly, and an order is rejected if the BTN is among the numbers being ported and no new billing number is given.

   Cisco Calling Plan number porting guidelines and policies · BTN guidance and section 'Port rejections' · Checked 2026-09-25
7. 7
   After FOC, changing or cancelling a Cisco Calling Plan port requires a support case with Cisco PSTN Technical Services (PTS), and the losing carrier may still drop the lines on the scheduled date.

   Cisco Calling Plan number porting guidelines and policies · section on order changes and cancellations (post-FOC) · Checked 2026-09-25
8. 8
   Before FOC, a customer can change or cancel a Cisco Calling Plan port order in Control Hub without risk of the numbers being ported.

   Cisco Calling Plan number porting guidelines and policies · section on order changes and cancellations (pre-FOC) · Checked 2026-09-25
9. 9
   Cisco's advertised 10 to 35 business day port processing, and its five-business-day minimum lead time, do not conflict with the FCC's one-business-day simple-port interval. The FCC interval applies to the carrier-to-carrier step after a valid request, while Cisco's figures cover the whole order, including validation, rejections and FOC scheduling.inferred

   47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(a), read against the 01sijg timeline sections · Checked 2026-09-25
10. 10
    Top rejection reasons that Cisco lists for Cisco Calling Plan ports: the losing carrier has a pending LSR on the account; BTN or ATN mismatch; numbers inactive, disconnected or not on the end user's account; location information mismatch; missing passcode or PIN; account number mismatch; and service address mismatch.

    Cisco Calling Plan number porting guidelines and policies · section 'Port rejections' · Checked 2026-09-25
11. 11
    A customer admin starts a Cisco Calling Plan port in Control Hub under PSTN & Routing > Numbers: Manage > Add, choose the location and number type, then choose 'Port Numbers Over'. The wizard then asks for the numbers, the requested completion date and time, carrier account details, the carrier bill and the signed LOA.

    Get Started with the Cisco Calling Plans · section 'Port in phone numbers', steps 1-14 · Checked 2026-09-25
12. 12
    The Cisco Calling Plan getting-started article lists fixed port time slots on weekdays: 8 AM to 3 PM in Switzerland, Belgium and Sweden; 9 AM to 4 PM in the Netherlands, Lithuania, Luxembourg and Denmark; and 8 AM to 5 PM in Finland. Out-of-hours requests are handled case by case.

    Get Started with the Cisco Calling Plans · porting time-slot list in section 'Port in phone numbers' · Checked 2026-09-25
13. 13
    A Customer Service Record (CSR) from the losing carrier is needed for complex ports in the US and Canada, and Cisco recommends getting a current CSR in other cases to make the porting information accurate.

    Cisco Calling Plan number porting guidelines and policies · CSR guidance in section 'Port order requirements' · Checked 2026-09-25
14. 14
    In some countries the Cisco Calling Plan LOA is an electronic LOA (eLOA) filled in automatically in Control Hub; in others the LOA must be completed, signed and uploaded by hand during the porting workflow.

    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements', LOA paragraph · Checked 2026-09-25
15. 15
    When the losing carrier rejects the FOC, the Control Hub fix is to update the Port Complete date on the PSTN order and resubmit.

    Get Started with the Cisco Calling Plans · common porting errors table, row 'FOC rejected by losing carrier' · Checked 2026-09-25
16. 16
    For the Control Hub port error 'Multiple BTNs', the listed fix is to cancel the current PSTN order and create several new orders.

    Get Started with the Cisco Calling Plans · common porting errors table, row 'Multiple BTNs' · Checked 2026-09-25
17. 17
    For the Control Hub port error 'TN not portable', the listed fix is to remove the affected numbers and resubmit the PSTN order.

    Get Started with the Cisco Calling Plans · common porting errors table, row 'TN not portable' · Checked 2026-09-25
18. 18
    By default, the emergency service address (ESA) entered for a location during Cisco Calling Plan setup applies to all phone numbers at that location, ported numbers included. Individual users can be given custom ESAs.

    Get Started with the Cisco Calling Plans · emergency service address section · Checked 2026-09-25
19. 19
    The requested port date and time for a Cisco Calling Plan port are not confirmed until the losing carrier returns a Firm Order Commitment (FOC).

    Cisco Calling Plan number porting guidelines and policies · section 'Requested port date and time' · Checked 2026-09-25
20. 20
    An inactive number assigned to a user, workspace or feature stays inactive until an admin activates it (Services > PSTN & Routing > Numbers > More Options > Activate).

    Manage phone numbers in Control Hub · section 'Activate phone numbers' · Checked 2026-09-25
21. 21
    The numbers being ported must stay active with the losing carrier throughout the port; the customer should not disconnect service until the port is complete and verified.

    Cisco Calling Plan number porting guidelines and policies · section 'Tips for successful porting' · Checked 2026-09-25
22. 22
    The requested port date for a Cisco Calling Plan port can be at most 30 days after the order is submitted.

    Cisco Calling Plan number porting guidelines and policies · section 'Requested port date and time' · Checked 2026-09-25
23. 23
    Cisco advises requesting a port date at least five business days after submission, or two to three weeks for larger ports.

    Cisco Calling Plan number porting guidelines and policies · section 'Requested port date and time' · Checked 2026-09-25
24. 24
    For a Premises-based PSTN (Local Gateway) location, any number port runs between the customer and their own PSTN carriers outside the Cisco Calling Plan port workflow and Cisco PTS; Webex Calling only needs the numbers added to the location and activated in Control Hub.inferred

    Configure Webex Calling for your organization · PSTN connection options, Premises-based PSTN; read with wkj3f0 'Add phone numbers' · Checked 2026-09-25
25. 25
    A PSTN connection change to Cisco Calling Plans may need several port orders (for example when multiple carriers are involved). These orders are linked so they complete together, the location's connection switches only after the last linked order finishes porting, and with multiple carriers this can take up to 10 business days.

    Configure Webex Calling for your organization · section 'Migrate to Cisco Calling plans' · Checked 2026-09-25
26. 26
    A Cisco Calling Plan port order requires a Letter of Agency (LOA), which authorizes Cisco to act on the customer's behalf with the losing carrier.

    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements' · Checked 2026-09-25
27. 27
    An existing location can switch from Premises-based PSTN or non-integrated Cloud Connected PSTN to Cisco Calling Plans through a PSTN connection change in Control Hub (Management > Locations > Calling > PSTN > Manage), which creates the port orders for the location's numbers.disputed

    Configure Webex Calling for your organization · section 'Migrate to Cisco Calling plans', subsection 'How to initiate a PSTN connection change' · Checked 2026-09-25
28. 28
    During a PSTN connection change to Cisco Calling Plans, all portable numbers keep working apart from a short interruption at the scheduled port completion time.

    Configure Webex Calling for your organization · section 'Migrate to Cisco Calling plans' · Checked 2026-09-25
29. 29
    A PSTN connection change to Cisco Calling Plans cannot start from an integrated IntelePeer location or from a Dedicated Instance location. Inactive (non-portable) numbers must be cleared first, and only customer administrators can start the change because it requires signing an E911 agreement.

    Configure Webex Calling for your organization · section 'Migrate to Cisco Calling plans', limitations and notes · Checked 2026-09-25
30. 30
    Control Hub distinguishes a standard port from a 'mixed operator port', which is a more complex port involving multiple operators, for example a block whose numbers belong to different network operators.

    Get Started with the Cisco Calling Plans · section 'Port in phone numbers', porting types · Checked 2026-09-25
31. 31
    Numbers can be moved between Webex Calling locations only within the same country, and only when the same PSTN provider or a local gateway provides them.

    Manage phone numbers in Control Hub · section 'Move phone numbers from one location to another' · Checked 2026-09-25
32. 32
    The Cisco Calling Plan prerequisites in the organization setup article say the location must be new, and that pre-existing locations that have had other PSTN capabilities assigned aren't currently eligible.disputed

    Configure Webex Calling for your organization · Cisco Calling Plan prerequisites list · Checked 2026-09-25
33. 33
    Cisco's porting guidelines tie port volume to licensing: a customer holding only one license can port only one number.

    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements' · Checked 2026-09-25
34. 34
    Each Webex Calling location has exactly one PSTN option (Cisco Calling Plan, Cloud Connected PSTN, or Premises-based PSTN through a local gateway), but different locations can use different options.

    Configure Webex Calling for your organization · PSTN connection options for a location · Checked 2026-09-25
35. 35
    Control Hub PSTN orders for ported numbers show one of these statuses: Pending, Action Required, Submitted, FOC Received, Completed, Rejected, Canceled. 'FOC Received' means the previous provider has confirmed the Firm Order Commitment date.

    Get Started with the Cisco Calling Plans · Control Hub PSTN orders status table · Checked 2026-09-25
36. 36
    Cisco's guidelines classify port orders as simple (1 number), standard (1 to 50 numbers), project (more than 50 numbers) and complex (multiple BTNs, rate centers or carriers), and give 10 to 35 business days as the processing range for each type.

    Cisco Calling Plan number porting guidelines and policies · order-type / processing-time table under 'Requested port date and time' · Checked 2026-09-25
37. 37
    For a Cisco Calling Plan port, the customer must demonstrate ownership of the numbers, using a current bill or invoice from the current carrier together with the LOA.

    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements' · Checked 2026-09-25
38. 38
    In a partial port where the account's main number (Billing Telephone Number, BTN) is being ported, a number that is not being ported is designated as the replacement BTN.

    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements', BTN paragraph · Checked 2026-09-25
39. 39
    In the partner view of Control Hub, numbers from an import (port) request appear straight away as Pending; the customer can assign them to people, but they only work after the port completes.

    Check The Status of Your Number and Order Requests · section on import requests / phone number status · Checked 2026-09-25
40. 40
    While a port order is pending on a losing-carrier account, more numbers from that same account can't be submitted for porting; a second submission is rejected.

    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements' · Checked 2026-09-25
41. 41
    A submitted Cisco Calling Plan port order stays Pending until Cisco validates and accepts it.

    Get Started with the Cisco Calling Plans · section 'Port in phone numbers', note after final step · Checked 2026-09-25
42. 42
    The Cisco Calling Plan getting-started article lists these countries: United States, Canada, Belgium, Denmark, Finland, France, Germany, Greece, Ireland, Italy, Lithuania, Luxembourg, Netherlands, Poland, Sweden, Switzerland, United Kingdom, Australia and New Zealand.

    Get Started with the Cisco Calling Plans · country availability list · Checked 2026-09-25
43. 43
    When a Cisco Calling Plan ends, the customer alone is responsible for porting the numbers to another provider if they want to keep them; numbers not ported out are released after a reasonable period.

    Cisco Calling Plan number porting guidelines and policies · service cancellation / termination paragraph · Checked 2026-09-25
44. 44
    Cisco grades the risk of a post-FOC change by the time left before the port: 72 hours or more is minimal, 48 to 72 hours low, 24 to 48 hours moderate, and under 24 hours high.

    Cisco Calling Plan number porting guidelines and policies · post-FOC change risk table · Checked 2026-09-25
45. 45
    Cisco positions Premises-based PSTN (Local Gateway) for customers who want to keep their current PSTN provider or connect non-cloud sites with cloud sites.

    Configure Webex Calling for your organization · PSTN connection options, Premises-based PSTN · Checked 2026-09-25
46. 46
    Cisco PSTN Technical Support (PTS) is available 24 hours a day, 5 days a week, and aims to respond to new cases within 2 hours.

    Cisco Calling Plan number porting guidelines and policies · section 'PTS support and hours' · Checked 2026-09-25
47. 47
    A port rejection can reset the porting SLA, depending on the country.

    Cisco Calling Plan number porting guidelines and policies · section 'Port rejections' · Checked 2026-09-25
48. 48
    Numbers on the same losing-carrier account must port at the same time, even if they are in different Cisco Calling Plan port orders.

    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements' · Checked 2026-09-25
49. 49
    The toll-free article says a toll-free port becomes active when the FOC is received, and that activation can't be postponed beyond 10 business days after FOC.

    Toll-free and non-geographical numbers support for Webex Calling · toll-free port order section · Checked 2026-09-25
50. 50
    Cisco Calling Plan (Cisco PSTN) supports new, port and move orders for inbound toll-free numbers in Control Hub. Non-geographic numbers are not supported on Cisco Calling Plans, and provisioning toll-free numbers needs the BCIBTFTN license.

    Toll-free and non-geographical numbers support for Webex Calling · Cisco Calling Plan (Cisco PSTN) section and licensing note · Checked 2026-09-25
51. 51
    In the US and Canada, toll-free numbers must be ported on orders separate from DID numbers.

    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements', toll-free note · Checked 2026-09-25
52. 52
    US rules set a four-business-day interval for non-simple wireline-to-wireline and non-simple intermodal port requests.

    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35 (paragraph reported as (d); verify) · Checked 2026-09-25
53. 53
    In the US, carriers required by the FCC to port numbers must complete a simple wireline-to-wireline or simple intermodal port request within one business day.

    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(a) · Checked 2026-09-25
54. 54
    US rules require interconnected VoIP providers to take all steps necessary to allow port-ins and port-outs, directly or through their telecommunications carriers, without unreasonable delay, and forbid agreements that would stop an end user from porting between interconnected VoIP providers.

    47 CFR § 52.34 - Obligations regarding local number porting to and from interconnected VoIP or Internet-based TRS providers · 47 CFR 52.34(a) and (b) · Checked 2026-09-25

Documents

Cite this page

WarmTransfer. (2026, September 25). Porting numbers to Webex Calling. WarmTransfer. https://warmtransfer.net/knowledge/webex-calling-number-porting

@misc{warmtransfer-webex-calling-number-porting,
  title  = {Porting numbers to Webex Calling},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-calling-number-porting},
  note   = {Verified 2026-09-25}
}