Source note · Number porting and LNP workflows
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 · Checked 2026-09-24
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- porting-interval
- Deployment
- pstn, multi-tenant
- Region
- us
- Release range
- current as of 2026-09-24
- Status
- inferred
- Checked
- 2026-09-24
Sources
- 47 CFR § 52.35 - Porting Intervals — Legal Information Institute (Cornell Law School), reproducing the Code of Federal Regulations · tier 1 standards and regulators · 47 CFR 52.35(a) and (d), read with the simple port definition in kelleydrye-2010-fcc-lnp-porting-order
Cite this note
APA
WarmTransfer. (2026, September 24). Number porting and LNP workflows: source note number-porting-enterprise-ports-usually-non-simple. WarmTransfer. https://warmtransfer.net/knowledge/claims/number-porting-enterprise-ports-usually-non-simple
BibTeX
@misc{warmtransfer-claim-number-porting-enterprise-ports-usually-non-simple,
title = {Number porting and LNP workflows: source note number-porting-enterprise-ports-usually-non-simple},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/number-porting-enterprise-ports-usually-non-simple},
note = {Source note number-porting-enterprise-ports-usually-non-simple, checked 2026-09-24}
}