Cisco Calling Plan number porting guidelines and policies

Publisher

Cisco Systems (Webex Help Center)

URL

https://help.webex.com/en-us/article/01sijg/Cisco-Calling-Plan-number-porting-guidelines-and-policies

Published

2025-05-21

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Cisco website terms of use; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Cisco Calling Plan ports activate automatically at the FOC time; allow at least 15 minutes, or 30 for project or complex ports, before numbers work. in context
• For Cisco Calling Plan ports, the customer can change or cancel a port order in Control Hub before the losing carrier gives FOC; after FOC, changes need a support case with Cisco PSTN Technical Services. in context
• Cisco's Calling Plan porting guidelines give Simple, Standard and Project port orders 10 to 35 business days to process and ask for at least five business days' lead time, or two to three weeks for larger ports. in context
• Cisco says numbers on the same losing-carrier account must port at the same time, even if they are on different orders. in context
• For Cisco Calling Plan ports in the US and Canada, toll-free numbers must go on separate orders from DID numbers. in context
• 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. in context
• After port activation, Cisco says to allow at least 15 minutes (30 minutes for project or complex ports) before the numbers start working. in context
• 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. in context
• 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. in context
• Before FOC, a customer can change or cancel a Cisco Calling Plan port order in Control Hub without risk of the numbers being ported. in context
• 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. in context
• 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. in context
• 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. in context
• 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). in context
• 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. in context
• The requested port date for a Cisco Calling Plan port can be at most 30 days after the order is submitted. in context
• Cisco advises requesting a port date at least five business days after submission, or two to three weeks for larger ports. in context
• 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. in context
• Cisco's porting guidelines tie port volume to licensing: a customer holding only one license can port only one number. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• A port rejection can reset the porting SLA, depending on the country. in context
• Numbers on the same losing-carrier account must port at the same time, even if they are in different Cisco Calling Plan port orders. in context
• In the US and Canada, toll-free numbers must be ported on orders separate from DID numbers. in context

Cite this source record

APA

WarmTransfer. (2025, May 21). Cisco Calling Plan number porting guidelines and policies. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-01sijg-calling-plan-porting-guidelines

BibTeX

@misc{warmtransfer-cisco-help-01sijg-calling-plan-porting-guidelines,
  title  = {Cisco Calling Plan number porting guidelines and policies},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-01sijg-calling-plan-porting-guidelines},
  note   = {Cisco Systems (Webex Help Center), accessed 2026-09-24}
}