Wholesale: Products & Services

Blocking Job Aid - V 14.0

History Log

Product Description

The following information includes specific blocking situations and the ordering requirements by Activity Type, Product and EASE System Release.


CenturyLink provisions blocking using the entries in the BA and BLOCK fields of the product-specific forms: RS, CRS, PS, NP, and LSNP.

When submitting your request, you no longer provide blocking USOCs or FIDs on your requests. The entries will be derived by CenturyLink from the BA and BLOCK field entries.

Blocking USOCs and FIDs are prohibited on the product-specific forms and will be rejected by the system if they are incorrectly entered by your request. The prohibited USOCs and FIDs are shown below.

Blocking Activity Values
BA A (Add) has been discontinued.

The new BA values are:

  • E-End State
  • N-No Change
  • D-Delete
  • Z-Remove All Blocking
  • Blank/Not Populated

E indicates you are providing in the BLOCK field the blocking you want to end up with. You may be adding, retaining, or disconnecting (or all three) BLOCK values. If you use BA E and a BLOCK value is not shown in the BLOCK field, it will not be added to or retained on your end-user's account.

N indicates you want to keep the existing blocking with no change. The use of the BLOCK field is prohibited with BA N. CenturyLink will retain whatever blocking your end-user currently has.

D indicates you want to remove one or more BLOCK values, as indicated in the BLOCK field. BA D requires the use of the BLOCK field.

Z indicates you want to remove all blocking on the line in question. The use of the BLOCK field is prohibited with BA Z.

The Meaning of a Blank/Not Populated BA
ACTIVITY V, Z, N, T-Blank BA equates to no blocking/remove all blocking
ACTIVITY C-Blank BA equates to no change to blocking

BLOCK Values:

A table of the new BLOCK values can be accessed from the following hyperlinks:

Block Values (Except Public Access Lines)

Block Values for Public Access Lines (PAL)

NOTE:  The following blocking values are REQUIRED on all PAL LSRs:  2, 3, 7, 8, A, K, and M (Blocks Pay Per Use, Incoming Fraud Protection, Blocks 900/Pay Per Call). 

In addition to the BLOCK values you have seen in the past, new BLOCK values 2-8 have been added to represent pay-per-use blocking.

New BLOCK values 0-screen 0+-and 9-screen all casual calling-have also been added. These BLOCK values were needed to enable CenturyLink to distinguish Long Distance Restriction from CustomNet.

Because you are not providing USOCs or FIDs, you need to select a BLOCK value or a group of BLOCK values that equates to a valid CenturyLink product. Some products, for instance, Billed Number Screening, equate to a single BLOCK value-in this case, A, B, or C. Other products comprise a group of BLOCK values, for instance, Long Distance Restriction equates to F, G, H, K, M, N.

Some products may be combined with others. For instance, Billed Number Screening, which blocks incoming calls, may be combined with Long Distance Restriction, which blocks outgoing calls.

Some products are not compatible with others. For instance, Long Distance Restriction and CustomNet are not compatible, because they both block or screen outgoing calls.

For Centrex Plus, Centrex Prime®, Centrex 21, and Centron®, some blocking may be provisioned by Line Class Code (LCC). In these cases, in addition to populating the BA and BLOCK fields, also provide LCC that includes blocking in FEATURE DETAIL following line USOC in FEATURE.

The rules in the LSOG and the Developer Worksheets have been updated to indicate valid single BLOCK values and valid combinations of BLOCK values. These rules also indicate the product represented by each single BLOCK value or combination or combination of values. This information enables you to refer to the PCATs as needed, to aid you in selecting the right product for your end-user.

Recap Functionality

Blocking USOCs and FIDs are now prohibited in the FEATURE and FEATURE DETAIL fields of the product-specific forms. When using the Recap functionality to pull a CSR into EASE, you will need to review the CSR and remove any blocking USOCs and FIDs, even if you want to keep them on the account. If you do want to keep them, you need to follow the new rules for the requested ACTIVITY.


It is not necessary to address blocking on ACT C, unless you want to change or remove it. For instance, you can request a PIC change on a line or add a new call forwarding feature without touching the blocking. (You can also use a BA N, if desired.)

Prohibited USOCs and FIDs

Last Update: April 23, 2023

Last Reviewed: March 28, 2024