WarmTransfer
numbering identity · published

Number porting and LNP workflows

Verified 2026-09-24 · 60 sources · tier 1–5

Under 47 CFR 52.21, number portability enables users to keep their existing telephone numbers at the same location when switching carriers without impairing quality, reliability, or convenience 43. Federal regulations define standard execution intervals across wireline, wireless, and interconnected VoIP services, while cloud calling platforms impose specific order structures and operational lead times 44​7​22.

Regulatory frameworks and porting intervals

47 CFR 52.21 defines location portability separately from number portability between carriers, while defining service portability as keeping a number when switching from one telecommunications service to another without changing carrier 47​51. The Local Number Portability Administrator (LNPA) is defined as an independent, non-governmental entity unaligned with any industry segment whose duties are determined by the NANC 46. iconectiv operates the Number Portability Administration Center (NPAC) as the US LNPA, covering virtually all US telephone numbers including wireless, wireline, and VoIP 33​32. To route calls to ported numbers, the NPAC maintains Location Routing Numbers, which are unique 10-digit numbers assigned to each switch 34.

Under 47 CFR 52.34(a), an interconnected VoIP provider must facilitate an end-user customer's valid number portability request, and 47 CFR 52.34(b) prohibits agreements that would stop an end user from porting between VoIP providers or to or from a telecommunications carrier 57​58. Telecommunications carriers must likewise facilitate valid port requests to or from an interconnected VoIP provider under 47 CFR 52.34(c) 39.

The FCC defines a simple port as an order involving no unbundled network elements, covering an account for a single line only, having no complex switch translations such as Centrex or ISDN, and involving no reseller 54. For porting intervals under 47 CFR 52.35, intermodal ports include wireline-to-wireless, wireless-to-wireline, and ports involving interconnected VoIP service 44. Port intervals apply according to 47 CFR 52.35 as follows: 55​59​50

Port type Mandatory interval
Simple wireline-to-wireline or intermodal 1 business day 55
Simple port under Commission waiver 4 business days 59
Non-simple wireline-to-wireline or intermodal 4 business days 50

These 1-business-day and 4-business-day intervals apply unless the customer or the new provider requests a longer period 45​59​50. Business days for simple ports under 47 CFR 52.35(a) are Monday through Friday with minimum business hours of 8 a.m. to 5 p.m., excluding company-defined holidays of the current provider 38. To qualify for activation at midnight the same day, the current provider must receive an accurate and complete simple port Local Service Request (LSR) between 8 a.m. and 1 p.m. local time; an LSR received after the 1 p.m. cutoff is treated as received at 8 a.m. on the next business day 49​48.

WarmTransfer's reading of the sources is that multi-line enterprise ports into UCaaS calling plans usually fail the single-line requirement of the FCC simple port definition, making the 4-business-day non-simple interval the governing regulatory bound rather than the 1-day interval 14. Historical compliance deadlines required non-small providers to meet the 1-business-day interval by August 2, 2010, while small providers had to comply by February 2, 2011 37​56. In DA 24-649, released July 5, 2024, the FCC waived the July 8, 2024 compliance date for SIM-swap and port-out fraud rules until OMB review ends and a Federal Register compliance notice is published, while declining petitioner requests to postpone compliance to March 10, 2025 53​52.

For toll-free numbering, when the losing Resp Org requires a valid LOA, the gaining Resp Org must submit the toll-free Resp Org change through the Somos ROC system 35. Somos states that toll-free Resp Org change requests submitted through ROC must be addressed within 2 business days 36.

Cisco Calling Plan porting workflows

In Control Hub, a Cisco Calling Plan port order is started from PSTN & Routing > Numbers, then Manage > Add > Port Numbers Over 4. Cisco sends the request to the losing carrier, the losing carrier returns a Firm Order Commitment (FOC), and activation occurs at the FOC date and time 6. Cisco Calling Plan port orders move through the statuses Pending, Action Required, Submitted, FOC Received, Completed, Rejected, and Canceled 9.

Cisco Calling Plan port orders have specific order parameters and restrictions:

  • Orders can include up to 1000 phone numbers 1.
  • Submissions require a current bill or invoice from the losing carrier dated within the last 30 days 3.
  • Numbers on the same carrier account must port at the same time, even if placed on different port orders 11.
  • Toll-free numbers must be on separate port orders from DID numbers 12.
  • Cisco advises allowing at least 5 business days, or 2 to 3 weeks for larger ports, between submitting a port and the requested port date 7.
  • The earliest requested date varies by country, carrier, and order type, from 1 to 35 business days, and can be requested up to 30 days from submission 5​8.
  • Port activation can be requested between 9 AM and 4 PM on regular business days; the article does not state a time zone 2.
  • Once the losing carrier issues an FOC, the order can no longer be modified in Control Hub; the customer must open a case with Cisco PTS 10.
  • When service is cancelled, the customer is responsible for porting numbers out, and unported numbers are released after a reasonable period 13.

Microsoft Calling Plan porting workflows

A single Teams admin center port order requires every number to share the same service provider, account number, BTN, number type, and service address 26. Requests of 1,000 or more numbers must bypass the Teams admin center wizard and be submitted manually through the Telephone Number Services (TNS) Service Desk 21.

Microsoft says port requests for the same account number are processed one at a time; overlapping requests cause the losing provider to reject all but the first, or all of them 29. Microsoft identifies the Customer Service Record (CSR) as the US document of record and the Equipment Record as the Canadian equivalent 17. Microsoft advises not disconnecting service with the current provider before porting completes because inactive or disconnected numbers cannot be ported 18. An account freeze at the losing provider causes order rejection; Microsoft says removing a freeze can take 1 to 3 weeks 20.

Operating timelines and service parameters for Microsoft Calling Plans include:

  • Minimum lead times are 5 days in the US and 10 days in Canada, with target port dates permitted up to 30 calendar days out 22. Microsoft recommends a conservative target port date at least 15 business days after submission for all ports 16.
  • Losing provider response SLAs are 3 to 5 business days in the US and 5 to 7 business days in Canada 23.
  • In the new US and Canada porting wizard, Microsoft acknowledges port requests within 72 business hours 15.
  • US user numbers can be scheduled between 8am and 8pm US Eastern, while Canadian numbers and US toll-free numbers are scheduled at 11:30am Eastern 28.
  • Order changes for US ports must be requested at least 2 business days prior to the port date, and cancellations require at least 1 business day notice 30.
  • Mobile number porting into Microsoft Calling Plans is available only in the US, Puerto Rico, and Canada, and the wizard requires the losing account PIN (which Microsoft says is not the same as a BTN freeze PIN) 25​24.
  • Ported US toll-free numbers can serve voice apps and audio conferencing, but not user assignments 31.
  • When moving numbers from Direct Routing or Operator Connect into Calling Plans, preassignment is not allowed; existing assignments are kept in the US and Canada, whereas numbers arrive unassigned elsewhere 19.
  • In the field, reports suggest that ports out of Microsoft Calling Plans are started by the new carrier and authorized with a 10-digit porting PIN set under Manage porting PIN in the Teams admin center 27.

WarmTransfer's reading of the sources is that vendor lead times of 5 or more business days exceed US regulatory porting intervals, most likely because they add vendor validation, LSR rejections and resubmissions, and customer date preferences on top of carrier execution 60.

See also

Applicability

Applies to: iconectiv NPAC, Somos Resp Org Change (ROC), Webex Calling - Cisco Calling Plan, and Teams Phone - Microsoft Calling Plans. Deployments: multi-tenant, interconnected-voip, pstn, and wireless. Sources checked 2026-09-24. Historical compliance deadlines applied August 2, 2010, for standard providers and February 2, 2011, for small providers under 47 CFR 52.35 37​56. Microsoft mobile number port-ins are restricted to the United States, Canada, and Puerto Rico 25; regional response SLAs are given for the United States and Canada 23. Toll-free separation rules for Cisco Calling Plans apply to the US and Canada 12.

What remains uncertain

The official Microsoft procedure for porting Calling Plan numbers out of Teams is not covered by the sources below, beyond community reports concerning a 10-digit PIN. The current compliance status of SIM-swap and port-out rules following DA 24-649 is not covered by the sources below. Ofcom General Condition B3 number portability timescales for UK fixed and mobile is not covered by the sources below. Porting responsibility for Webex Calling Local Gateway and Cloud Connected PSTN locations is not covered by the sources below. Number porting for Webex Contact Center entry points and BYO PSTN is not covered by the sources below. Porting numbers into Teams Operator Connect versus Calling Plans is not covered by the sources below. Vendor porting fees for Cisco and Microsoft calling plans are not covered by the sources below. EU EECC Article porting and number retention rules are not covered by the sources below.

See also

Referenced by

Sources

  1. 1
    A single Cisco Calling Plan port order can include up to 1000 phone numbers.
    Get Started with the Cisco Calling Plans · porting numbers section · Checked 2026-09-24
  2. 2
    Cisco Calling Plan port activation can be requested for any time between 9 AM and 4 PM on regular business days; the article does not state a time zone.
    Cisco Calling Plan number porting guidelines and policies · section 'Requested port date and time' · Checked 2026-09-24
  3. 3
    A Cisco Calling Plan port order needs a current bill or invoice from the losing carrier, dated within the last 30 days.
    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements' · Checked 2026-09-24
  4. 4
    In Control Hub, a Cisco Calling Plan port is started from PSTN & Routing > Numbers, then Manage > Add > Port Numbers Over.
    Get Started with the Cisco Calling Plans · porting numbers section · Checked 2026-09-24
  5. 5
    For Cisco Calling Plans, the earliest port date that can be requested varies by country, carrier and order type, from 1 to 35 business days.
    Cisco Calling Plan number porting guidelines and policies · section 'Requested port date and time' · Checked 2026-09-24
  6. 6
    For Cisco Calling Plan port-ins, Cisco sends the request to the losing carrier, the losing carrier returns a Firm Order Commitment (FOC), and the port activates at the FOC date and time.
    Cisco Calling Plan number porting guidelines and policies · porting process section · Checked 2026-09-24
  7. 7
    Cisco advises allowing at least five business days, or 2-3 weeks for larger ports, between submitting a Cisco Calling Plan port and the requested port date.
    Cisco Calling Plan number porting guidelines and policies · section 'Requested port date and time' · Checked 2026-09-24
  8. 8
    For Cisco Calling Plans, the requested port date can be up to 30 days from the date of submission.
    Cisco Calling Plan number porting guidelines and policies · section 'Requested port date and time' · Checked 2026-09-24
  9. 9
    Cisco Calling Plan port orders move through the statuses Pending, Action Required, Submitted, FOC Received, Completed, Rejected and Canceled.
    Get Started with the Cisco Calling Plans · port order status list · Checked 2026-09-24
  10. 10
    Once the losing carrier has given FOC, a Cisco Calling Plan port order can no longer be modified in Control Hub; the customer must open a case with Cisco PSTN Technical Services (PTS).
    Cisco Calling Plan number porting guidelines and policies · section 'Reschedule or cancel a port' · Checked 2026-09-24
  11. 11
    For Cisco Calling Plans, numbers on the same carrier account must port at the same time, even if they are on different port orders.
    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements' · Checked 2026-09-24
  12. 12
    For Cisco Calling Plans, toll-free numbers must be on separate port orders from DID numbers.
    Cisco Calling Plan number porting guidelines and policies · section 'Port order requirements' · Checked 2026-09-24
  13. 13
    When Cisco Calling Plan service is cancelled, the customer is responsible for porting numbers out, and numbers not ported out are released after a reasonable period.
    Cisco Calling Plan number porting guidelines and policies · section 'Service cancellation' · Checked 2026-09-24
  14. 14
    Multi-line enterprise ports into UCaaS calling plans usually fail the single-line test of the FCC simple port definition, so the four-business-day non-simple interval, not the one-day interval, is the relevant US regulatory bound.inferred
    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(a) and (d), read with the simple port definition in kelleydrye-2010-fcc-lnp-porting-order · Checked 2026-09-24
  15. 15
    In the new US and Canada porting wizard, Microsoft acknowledges port requests within 72 business hours.
    Transfer phone numbers to Microsoft Teams · tab 'Porting wizard - New (U.S. & Canada)', section 'Confirmation' · Checked 2026-09-24
  16. 16
    Microsoft recommends a conservative target port date at least 15 business days after submission for all ports.
    What's a port order? - Microsoft Teams · section 'Plan for port event date', Approach 2 · Checked 2026-09-24
  17. 17
    Microsoft identifies the Customer Service Record (CSR) as the US document of record for porting and the Equipment Record as the Canadian equivalent.
    What's a port order? - Microsoft Teams · section 'Planning a number port event' · Checked 2026-09-24
  18. 18
    Microsoft advises not disconnecting service with the current provider before porting completes, because inactive or disconnected numbers cannot be ported.
    What's a port order? - Microsoft Teams · section 'When to disconnect your existing phone lines with your current service provider' · Checked 2026-09-24
  19. 19
    When numbers move from Direct Routing or Operator Connect into Calling Plans, preassignment is not allowed; in the US and Canada existing assignments can be kept, while elsewhere numbers arrive unassigned.
    Transfer phone numbers to Microsoft Teams · port order status table, row 'Approved (FOCAccepted)' · Checked 2026-09-24
  20. 20
    An account freeze at the losing provider causes a Microsoft port order to be rejected, and Microsoft says removing a freeze can take one to three weeks.
    What's a port order? - Microsoft Teams · sections 'Common mistakes' and 'Remove any freeze on your current account' · Checked 2026-09-24
  21. 21
    Microsoft Calling Plan port requests of 1,000 or more numbers must bypass the Teams admin center wizard and be submitted manually through the Telephone Number Services (TNS) Service Desk.
    What's a port order? - Microsoft Teams · section 'Large port requests' · Checked 2026-09-24
  22. 22
    For Microsoft Calling Plan ports, the minimum lead time is five days in the US and ten days in Canada, and target port dates cannot be more than 30 calendar days out.
    What's a port order? - Microsoft Teams · section 'Plan lead-time for port request processing' · Checked 2026-09-24
  23. 23
    Microsoft gives the losing service provider's response SLA as 3-5 business days in the United States and 5-7 business days in Canada.
    What's a port order? - Microsoft Teams · section 'What happens after you submit a port order request' · Checked 2026-09-24
  24. 24
    The Teams porting wizard requires the losing account's PIN for all mobile numbers, and Microsoft says that account PIN is not the same as a BTN freeze PIN.
    Transfer phone numbers to Microsoft Teams · tab 'Porting wizard - New (U.S. & Canada)', section 'Account information' · Checked 2026-09-24
  25. 25
    Porting mobile numbers into Microsoft Calling Plans is available only in the United States, Puerto Rico and Canada.
    What's a port order? - Microsoft Teams · section 'Numbers eligible for porting' · Checked 2026-09-24
  26. 26
    A single Teams admin center port order requires every number to share the same service provider, account number, BTN, number type and service address.
    What's a port order? - Microsoft Teams · section 'How many port requests do I need?' · Checked 2026-09-24
  27. 27
    Community answers report that ports out of Microsoft Calling Plans are started by the new carrier and authorized with a 10-digit porting PIN set under Manage porting PIN in the Teams admin center.field report
    How to port MS calling plan numbers to other carrier. - Microsoft Q&A · answer posted 2025-09-10 · Checked 2026-09-24
  28. 28
    For US user numbers on Microsoft Calling Plans, port times can be chosen between 8am and 8pm US Eastern; Canadian numbers and US toll-free numbers are scheduled at 11:30am Eastern.
    What's a port order? - Microsoft Teams · section 'Plan for port event to process during business hours' · Checked 2026-09-24
  29. 29
    Microsoft says port requests for the same account number are processed one at a time; overlapping requests on one account cause the losing provider to reject all but the first, or all of them.
    What's a port order? - Microsoft Teams · section 'How port requests are processed' · Checked 2026-09-24
  30. 30
    For US Microsoft Calling Plan ports, changes must be requested at least 2 business days, and cancellations at least 1 business day, before the approved port date.
    Phone number management for the United States · FAQ row 'Can I change or cancel my port order?' · Checked 2026-09-24
  31. 31
    In the US, toll-free numbers ported to Microsoft Calling Plans can serve voice apps and audio conferencing but not user assignments.
    Phone number management for the United States · table 'What number types can I port?' · Checked 2026-09-24
  32. 32
    iconectiv states that the NPAC covers virtually all US telephone numbers, including wireless, wireline and VoIP numbers.
    About NPAC · About NPAC page, scope statement · Checked 2026-09-24
  33. 33
    iconectiv operates the Number Portability Administration Center (NPAC) as the US Local Number Portability Administrator.
    About NPAC · About NPAC page, operator statement · Checked 2026-09-24
  34. 34
    NPAC keeps Location Routing Numbers: a unique 10-digit number assigned to each switch, used to route calls to ported numbers.
    About NPAC · About NPAC page, LRN description · Checked 2026-09-24
  35. 35
    When the losing Resp Org requires a valid LOA, a gaining Resp Org must submit the toll-free Resp Org change through the Somos ROC system.
    Utilizing the ROC System for Toll-Free Number Port Changes · article body, LOA requirement sentence · Checked 2026-09-24
  36. 36
    Somos states that toll-free Resp Org change requests submitted through ROC must be addressed within 2 business days.
    Utilizing the ROC System for Toll-Free Number Port Changes · article body, response timeline · Checked 2026-09-24
  37. 37
    According to the 2010 advisory, providers other than small providers had to comply with the one-business-day simple port interval by August 2, 2010.
    FCC Issues Order Standardizing Number Porting Process · advisory paragraph on compliance deadlines · Checked 2026-09-24
  38. 38
    For simple ports under 47 CFR 52.35(a), Monday through Friday are mandatory business days and 8 a.m. to 5 p.m. are minimum business hours, excluding the current provider's company-defined holidays.
    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(a), business-day sentence · Checked 2026-09-24
  39. 39
    Under 47 CFR 52.34(c), telecommunications carriers must facilitate a valid port request to or from an interconnected VoIP provider.
    47 CFR § 52.34 - Obligations regarding local number porting to and from interconnected VoIP or Internet-based TRS providers · 47 CFR 52.34(c) · Checked 2026-09-24
  40. 40
    As displayed by LII at access, 47 CFR 52.37(h) says compliance with the section is not required until that paragraph is removed.
    47 CFR § 52.37 - Number portability requirements for wireless providers · 47 CFR 52.37(h) · Checked 2026-09-24
  41. 41
    47 CFR 52.37(b) requires a CMRS provider to use secure methods to authenticate the customer before carrying out a port-out request, and to review those methods regularly.
    47 CFR § 52.37 - Number portability requirements for wireless providers · 47 CFR 52.37(b) · Checked 2026-09-24
  42. 42
    47 CFR 52.37 applies to all commercial mobile radio service (CMRS) providers, including resellers.
    47 CFR § 52.37 - Number portability requirements for wireless providers · 47 CFR 52.37(a) · Checked 2026-09-24
  43. 43
    47 CFR 52.21 defines number portability as users keeping their existing numbers at the same location, without impairing quality, reliability or convenience, when switching carriers.
    47 CFR § 52.21 - Definitions · 47 CFR 52.21, definition of number portability · Checked 2026-09-24
  44. 44
    For 47 CFR 52.35, intermodal ports include wireline-to-wireless, wireless-to-wireline, and ports involving interconnected VoIP service.
    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(e), intermodal ports definition · Checked 2026-09-24
  45. 45
    The one-business-day simple port interval in 47 CFR 52.35(a) applies unless the new provider or the customer requests a longer period.
    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(a), first sentence · Checked 2026-09-24
  46. 46
    47 CFR 52.21 defines the Local Number Portability Administrator as an independent, non-governmental entity that is not aligned with any industry segment and whose duties are determined by the NANC.
    47 CFR § 52.21 - Definitions · 47 CFR 52.21, definition of Local Number Portability Administrator · Checked 2026-09-24
  47. 47
    47 CFR 52.21 defines location portability, meaning a user keeps a number when moving between physical locations, separately from number portability between carriers.
    47 CFR § 52.21 - Definitions · 47 CFR 52.21, definition of location portability · Checked 2026-09-24
  48. 48
    A simple port LSR received after the 1 p.m. cutoff is treated as received at 8 a.m. local time on the next business day.
    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(a), final sentence · Checked 2026-09-24
  49. 49
    To be eligible for activation at midnight the same day, the current provider must receive an accurate and complete simple port LSR between 8 a.m. and 1 p.m. local time.
    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(a), LSR receipt sentence · Checked 2026-09-24
  50. 50
    Under 47 CFR 52.35(d), a non-simple wireline-to-wireline or non-simple intermodal port must be completed within four business days unless the new provider or customer requests a longer period.
    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(d) · Checked 2026-09-24
  51. 51
    47 CFR 52.21 defines service portability as keeping a number when switching from one telecommunications service to another without changing carrier.
    47 CFR § 52.21 - Definitions · 47 CFR 52.21, definition of service portability · Checked 2026-09-24
  52. 52
    The FCC declined the petitioners' request to postpone SIM-swap and port-out fraud compliance to March 10, 2025.
    FCC Amends SIM Swapping/Port-Out Fraud Compliance Date · post body, final point · Checked 2026-09-24
  53. 53
    In DA 24-649, released July 5, 2024, the FCC waived the July 8, 2024 compliance date for the SIM-swap and port-out fraud rules until OMB review ends and a Federal Register compliance notice is published.
    FCC Amends SIM Swapping/Port-Out Fraud Compliance Date · post body, summary of DA 24-649 · Checked 2026-09-24
  54. 54
    The FCC defines a simple port as one that involves no unbundled network elements, covers an account for a single line only, has no complex switch translations such as Centrex or ISDN, and involves no reseller.
    FCC Issues Order Standardizing Number Porting Process · advisory paragraph quoting the simple port definition · Checked 2026-09-24
  55. 55
    Under 47 CFR 52.35(a), US carriers required 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), first sentence · Checked 2026-09-24
  56. 56
    Small providers, as described in the 2009 LNP Porting Interval Order, had to comply with 47 CFR 52.35 by February 2, 2011.
    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(b) · Checked 2026-09-24
  57. 57
    Under 47 CFR 52.34(a), an interconnected VoIP provider must facilitate an end-user customer's valid number portability request.
    47 CFR § 52.34 - Obligations regarding local number porting to and from interconnected VoIP or Internet-based TRS providers · 47 CFR 52.34(a) · Checked 2026-09-24
  58. 58
    Under 47 CFR 52.34(b), an interconnected VoIP provider may not enter any agreement that would stop an end user from porting between VoIP providers or to or from a telecommunications carrier.
    47 CFR § 52.34 - Obligations regarding local number porting to and from interconnected VoIP or Internet-based TRS providers · 47 CFR 52.34(b) · Checked 2026-09-24
  59. 59
    Carriers holding a Commission waiver must complete a simple wireline-to-wireline or simple intermodal port within four business days unless a longer period is requested.
    47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(c) · Checked 2026-09-24
  60. 60
    Vendor lead times of five or more business days exceed the US regulatory porting intervals, most likely because they add vendor validation, LSR rejections and resubmissions, and customer date preferences on top of carrier execution.inferred
    What's a port order? - Microsoft Teams · sections 'What happens after you submit a port order request' and 'Plan lead-time', compared with 47 CFR 52.35 · Checked 2026-09-24

Documents

tier 1 standards and regulators

47 CFR § 52.21 - Definitions

Legal Information Institute (Cornell Law School), reproducing the Code of Federal Regulations · 2015-10-29 · accessed 2026-09-24

tier 1 standards and regulators

47 CFR § 52.34 - Obligations regarding local number porting to and from interconnected VoIP or Internet-based TRS providers

Legal Information Institute (Cornell Law School), reproducing the Code of Federal Regulations · 2015-10-29 · accessed 2026-09-24

tier 1 standards and regulators

47 CFR § 52.35 - Porting Intervals

Legal Information Institute (Cornell Law School), reproducing the Code of Federal Regulations · 2015-10-29 · accessed 2026-09-24

tier 1 standards and regulators

47 CFR § 52.37 - Number portability requirements for wireless providers

Legal Information Institute (Cornell Law School), reproducing the Code of Federal Regulations · 2023-12-08 · accessed 2026-09-24

tier 2 current vendor documentation

About NPAC

iconectiv, LLC · 2026-01-01 · accessed 2026-09-24

tier 2 current vendor documentation

Cisco Calling Plan number porting guidelines and policies

Cisco Systems · 2025-05-21 · accessed 2026-09-24

tier 2 current vendor documentation

Get Started with the Cisco Calling Plans

Cisco Systems, Inc. (Webex Help Center) · 2026-08-05 · accessed 2026-09-15

tier 2 current vendor documentation

Phone number management for the United States

Microsoft · 2023-05-15 · accessed 2026-09-24

tier 2 current vendor documentation

Transfer phone numbers to Microsoft Teams

Microsoft · 2026-05-28 · accessed 2026-09-21

tier 2 current vendor documentation

Utilizing the ROC System for Toll-Free Number Port Changes

Somos, Inc. · 2019-12-05 · accessed 2026-09-24

tier 2 current vendor documentation

What's a port order? - Microsoft Teams

Microsoft · 2026-05-28 · accessed 2026-09-24

tier 4 archived vendor documentation

FCC Amends SIM Swapping/Port-Out Fraud Compliance Date

Telecommunications Law Professionals PLLC · 2024-07-08 · accessed 2026-09-24

tier 4 archived vendor documentation

FCC Issues Order Standardizing Number Porting Process

Kelley Drye & Warren LLP · 2010-05-24 · accessed 2026-09-24

tier 5 independent technical research

How to port MS calling plan numbers to other carrier. - Microsoft Q&A

Microsoft Q&A (community forum) · 2025-09-10 · accessed 2026-09-24

Cite this page

APA

WarmTransfer. (2026, September 24). Number porting and LNP workflows. WarmTransfer. https://warmtransfer.net/knowledge/number-porting

BibTeX

@misc{warmtransfer-number-porting,
  title  = {Number porting and LNP workflows},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/number-porting},
  note   = {Verified 2026-09-24}
}