AT&T's "Customer Not Ready" Process for Switch Translations |
Overview
This document will outline the changes that need to be made to switch translations on AT&T's Prime trunk and line services to complete the "Customer Not Ready" process.
The Customer Not Ready (CNR) process allows for billing the customer for the installed circuit 30 calendar days after the Local Exchange Carrier's Concurred Due Date (LCDD), even if the customer is not ready to accept the service. All efforts will be made to work with the customer to get them to accept the circuit on the due date and within 30 calendar days after the due date expires. If the coordinated efforts are not effective, the AT&T's Provisioning Service will begin billing the customer for the circuit (CNR billing) 30 calendar days after the LEC's concurred due date.
Part 1: DMS Switch
Step One (Applicable to Prime Digital, PrimeXpress, PrimePlex, and PrimeConnect trunks)
Change the Billing Telephone Number (BTN) in the translation(s) to the provided AT&T Local Network Service's telephone number.
Position on the customer's CLLI in table TRKGRP (Trunk Group):
----------------------------------------------------------------------------------------- # The BTN in this PrimeXpress example is: 4102295900 >TABLE TRKGRP >POS CYVLMDDKHA1_2W CYVLMDDKHA1_2W PX 0 NPDGP NCRT 2W NIL ASEQ N NC0003 CYVL 410 410 LCL NONE RTE1 CYVL N N 759 LOCL 4102295900 NODIALTN N Y 0222 Y L238 N $ # The BTN in this PrimePlex PRI example is: 4433943737 >TABLE TRKGRP >POS OWMLMDFHHA0_PRI OWMLMDFHHA0_PRI PRA 0 NPDGP NCRT ASEQ 4433943737 (PRI1 335)$ $ -----------------------------------------------------------------------------------------
Use the table editor command CHA to change the "BILLDN" field.
Step Two
Remove any Telephone Numbers (TN) which may be in the routing tables.
Verify that there are no TNs (AT&T Local Network Services or ported) in the switch routing to customer trunks:
----------------------------------------------------------------------------------------- >TABLE DNROUTE >LIS ALL(4 EQ IBNRTE/2/3 XXXX) -----------------------------------------------------------------------------------------
Remove any TNs associated with the customer's route(s) in SERVORD using the OUTDN command. Do not delete from table DNROUTE (Directory Number Route). This includes any local TNs.
Step Three
Populate critical dates and update the order log.
Complete the TDD critical date and include in the Access Service Request (ASR) log notes the following:
Step One (Applicable to PrimePath, Prime NBX, and PrimePath NBX trunks)
Add the Special Billing (SPB) option.
The SPB option allows a number other than the subscriber's directory number to be used for billing.
The Switch Production Agent will add the Special Billing (SPB) option using SERVORD to every line:
----------------------------------------------------------------------------------------- >SERVORD SO: >ADO # Add Option SONUMBER: NOW 3 12 5 PM > # Hit 'Enter' DN_OR_LEN: >SA12 35 0 01 08 # Line Equipment Number OPTION: >SPB # Special Billing Option SPBDN: >NPANXXXXXX # Add Billing TN OPTION: >$ # End COMMAND AS ENTERED: ADO NOW 3 12 5 PM SA12 35 0 01 08 (SPB NPANXXXXXX) $ ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT >Y -----------------------------------------------------------------------------------------
Complete for all DS0 lines, including related orders.
Step Two
Populate critical dates and update the order log.
Complete the TDD critical date and include in the Access Service Request (ASR) log notes the following:
Part 2: #5 ESS Switch
Step One (Applicable to Prime Digital, PrimeXpress, PrimePlex, and PrimeConnect trunks)
Change the Billing Telephone Number (BTN) in the translation(s) to the provided AT&T Local Network Service's telephone number.
Change the BTN in Recent Change/View 5.1, field #242:
----------------------------------------------------------------------------------------- 233. DATARATE _______ 244. SPA BILL DN _______ 234. INVERSION N 245. SDN STAT GRP N 235. WB RATE _______ 246. SPA SUPV N 236. WB TSA TYPE _______ 247. ANI6 N 237. INTER SM TRK N 248. ANI7 N 238. DIR CON DN _______ 249. TOPAS TPNUM _______ 239. FACILITY TYPE _______ 250. ASI PROXY N 240. FACILITY NBR _______ 251. FGD CIC SZ _______ 241. RTE NBR PLAN _______ 252. SPEECH TRMTS N 242. BILLING DN 9168305000 253. MLT ISLC OPT N 243. ACP SDN _______ 254. MAI S -----------------------------------------------------------------------------------------
Step Two
Change the main Directory Number (DN) in the translation(s) to the provided AT&T Local Network Service's telephone number.
Change the main DN in Recent Change/View 5.1, field #142:
----------------------------------------------------------------------------------------- 134. STA ID _______ 146. CPN DISC N 135. UUI N 147. INHIBIT TCM N 136. CODE SET7 _______ 148. RDTA GRP N 137. SDN DAS _______ 149. E911 CPN N 138. CBC N 150. CPN BILLING N 139. DEDICATED SRV _______ 151. ALLOW AMA N 140. VOICE CUT THRU NORMAL 152. STD RN SRC N 141. DATA CUT THRU NORMAL 153. RN SCRN N 142. MAIN DN 9168305000 154. RN DISC N 143. CPN DN OPT NONE 155. RN BILLING N 144. PRIV OVER N 156. ALW DATA ONLY N -----------------------------------------------------------------------------------------
Step Three
Remove any TNs that may be in routing tables and delete all DIDs associated with the RTI.
Go to Recent Change/View 1.5 and 4.14 and query by RTI (Route Index) or HRI:
-----------------------------------------------------------------------------------------
*1. TN 9164310208 SPEC TRN NONE
22. RAX 1 COMP LOSS _______
23. LCC DID
38. RTI 422 SCD SCNING N
HRI _______ 127. LRN INDEX _______
57. TSTCODE NONE 129. NON COND TRIG N
59. RMK SACP0300406
-----------------------------------------------------------------------------------------
Step Four
Populate critical dates and update the order log.
Complete the TDD critical date and include in the Access Service Request (ASR) log notes the following:
Step One (Applicable to PrimePath, Prime NBX, and PrimePath NBX trunks)
Add the BTN provided on the Access Service Request.
In Recent Change/View 1.6, field #19 add the BTN from the service request:
-----------------------------------------------------------------------------------------
*1. TN 9168309911 18. MFRI N 30. BRCS Y
*2. OE _______ 19. BTN (NOT=TN) 9168309910 31. BAUTO N
*5. PTY _______ MULTIDN N 32. SHARED N
*6. MLHG _______ DEPENDN N 33. SAUTO N
*7. MEMB _______ 22. RAX 11 34. FLS N
23. LCC 4AI 35. SUSO N
9. CHNG TN 9168309911 LATA ______ 36. SUST N
10. CHNG OE N 00600117102 25. COIN N 37. ICP N
11. CHNG PTY I 26. GST N 38. RTI _______
14. CHNG MLHG _______ 27. EL N HRI _______
15. CHNG MEMB _______ 28. SERHLN _______ 40. BCK LNK N
16. NEW TN _______ 29. TTC Y 41. NODL N
-----------------------------------------------------------------------------------------
Step Two
Populate critical dates and update the order log.
Complete the TDD critical date and include in the Access Service Request (ASR) log notes the following: