Porting support:
Virtual Front Office (SPIDs 7178, 7280, and 8994)
Use Virtual Front Office to port out phone numbers from legacy TW telecom (SPIDs 7178, 7280, and 8994). For access to Virtual Front Office, contact us.
Contacts for SPIDs 7178, 7280, and 8994 (formerly TW telecom)
| Level | Contact information |
| 1 | Escalation mailbox (Please allow four hours for a response.) |
| 2 | 303‑566‑1569 |
| 3 | Christian Aguilar (LNP manager) 720‑888‑1563 |
Policies and processes for all port-out requests
- Lumen ports telephone numbers following all applicable regulatory rules and industry guidelines.
- Lumen honors port-out requests from any authorized carrier (including cellular carriers) where the carrier indicates that they have a letter of authorization (LOA) from the end-user customer.
- Lumen reviews requests for expedited port out intervals on an individual case basis with particular focus on preventing emergency services (such as 911, police, fire, ambulance, or medical facilities) from being out of service, but we do not guarantee that we can meet the shortened interval.
- LOA: the LOA is not a required attachment to an LSR before Lumen will accept it. It is only necessary to have the AGAUTH box populated with the LOA name.
- Changes or cancellations: The NSP must submit a supplement LSR to Lumen a minimum of 24 hours before the scheduled cut over. Large changes or additions to the LSR may affect the original due date.
- Rejects or clarifications to the LSR: Lumen rejects LSRs when they don't provide sufficient information to process our disconnect service order. Lumen rejects LSRs for the following reasons:
- If all 14 required fields are not complete for simple ports.
- If the end user name does not match our customer of record.
- If the service address on the LSR does not match the service address of record.
- If porting out all numbers that are part of a contractually bundled service.
(You must contact your Lumen representative to determine remaining products and pricing.)
- If all 14 required fields are not complete for simple ports.
- Lumen issues a firm order commitment (FOC) when all open clarifications or rejects have been resolved.
- NPAC activation of TNs: To help ensure concurrence on the FOC date, the gaining carrier must build an NPAC subscription for the TNs porting a minimum of 18 business hours prior to the due date.
- Any ring-to telephone number associated with a toll-free number will be disconnected at time of port. To avoid an outage, toll-free numbers should be ported (Resp Org) prior to, or on the same day as, the numbers porting.
Porting 100+ numbers (project orders)
Projects are defined as a local service request (LSR) to port 100 or more numbers. Project requests require a minimum of five business days. You include “Project/End User Name” in the remarks section of the LSR page and fill in all required fields (highlighted in yellow) within the Virtual Front Office (VFO) tool. Once approved and free of rejects or clarifications, Lumen responds with a FOC and your due date for the project. LSRs submitted as a project are subject to normal LSR validation.
Requesting a customer service record (CSR)
To request a CSR, email PortOutCSR@lumen.com and include the following:
- customer name
- service address
- billing phone number (BTN)
Ordering intervals
- An FOC or error status will be returned back to the NSP within 24 hours of receipt of the LSR.
- After receiving a clean LSR, Lumen requires a minimum of four business days to process an order.
- A due-date supplement will be required if numbers are not ported on FOC date. If a supplement is not received 24 hours before FOC date, the order will be cancelled the following business day.
LSR requirements and field definitions
Order Initiation section
Field | Required? | Description | Field must contain |
Managed Esp | Yes | Your company name ‑ drop down | |
Order Number | Yes | Your PON what you pick | |
Receiver Code | No | ||
Version | Autofilled | ||
Guideline Version | No | ||
Service | Yes | CB ‑ number portability | CB |
Activity | Yes | V ‑ conversion | V |
Template | No |
LSR page
LSR Admin section
Field | Required? | Description | Field must contain |
LOCQTY | Yes | Need equal LOC to PORT | |
AN | Yes | The main account number assigned by the NSP. This field contains 20 alphanumeric characters. | The BTN or ATN |
REQTYP | Yes | CB | |
RTR | Yes | Identifies the type of local response requested by the customer. This field contains 1 letter. Valid values are:
| C |
CCNA | Yes | Your company code |
Authorization section
Field | Required? | Description | Field must contain |
Dated | Yes | LOA date | |
Authnm | Yes | Must be person who signed the LOA | |
NNSP | Yes | Identifies the number portability administration center (NPAC) service provider identifier (SPI) of the new network service provider (NSP). This field is required and contains 4 alphanumeric characters. | |
DDD | Yes | Date for port (desired due date) | |
NPDI | Yes | The direction of LNP conversion activity on this request. This field contains 1 alpha character. Valid values are:
| D |
AUTH INFORM GRP section
Field | Required? | Description | Field must contain |
Agauth | Yes | Indicates that you are acting as an end‑user's agent and have authorization on file. This field contains 1 alpha character. | Y |
LSP_AUTH_NAME | Yes | Identifies the name of the person who signed the authorization letter. This field is conditional and contains 15 alphanumeric characters. |
Contact section
Field | Required? | Description |
INIT | Yes | The name of your company's representative who originated this request. This field is required and can contain up to 15 alphanumeric characters. |
INIT_TEL_NO | Yes | The phone number for your company's representative who originated this request. This field is required and contains 15 alphanumeric characters. |
INIT_EMAIL | Yes | The email address for your company's representation who initiated this request. This field is required and can contain up to 60 alphanumeric characters. |
Remarks section
Field | Required? | Description |
REMARKS_INFO | Optional | Use this field to expand upon or clarify other data on this form. This field is optional and can contain up to 160 alphanumeric characters. |
End user page
LOC_ACCESS section
Field | Required? | Description |
NAME | Yes | Identifies the name of the end user. This field is required and can contain up to 25 alphanumeric characters. |
SVC_ADDR_GRP section
Field | Required? | Description |
SANO | Yes | The number of the service address. This field is required and can contain up to 10 alphanumeric characters. |
SASN | Yes | The street name of the service address. This field is required and can contain up to 60 alphanumeric characters. |
CITY | Yes | The city, village, township, etc. This field is required and can contain up to 32 alphanumeric characters. |
STATE | Yes | The abbreviation for the state or province. This field is required and can contain up to 2 alpha characters. |
ZIP | Yes | The ZIP code, ZIP code + extension, or postal code. This field is required and can contain up to 12 alphanumeric characters. |
Number port page
NP_ADMIN section
Field | Required? | Description | Field must contain |
SIMPLE_PORT_IND | Yes | Identifies simple port indicator. This field contains list values of Y and N. | N (default value) |
NPQTY | Yes | The quantity of ported numbers involved in this service request. This field is required and can contain up to 5 digits. | |
PORTED_NBR | Yes | The telephone number (TN) or consecutive range of TNs residing in the same switch to be ported. This field is required and contains 15 alphanumeric characters (excluding 2 preprinted hyphens). |
SVC_DET_GRP section
Field | Required? | Description | Field must contain |
LNUM | Yes | The line or trunk as a unique number and each additional occurrence as a unique number. This field is required and contains 4 numeric characters. | |
LNA | Yes | The activity involved at the line level. This field is required and contains 1 alpha character. Valid value:
| V |