verizon east release overvie · 2012-05-18 · verizon east release overview release overview...

Verizon East Release Overview

Release Overview October 2005

Publication 08/04/2005 Version 1.1 – 09/01/2005

VERIZON Restricted


Publication Date: September 1, 2005

- 2 -

Notice This Release Overview document is intended to provide an encapsulated look at initiatives scheduled for implementation in the next Verizon technical release. This document is not recommended for use to program interfacing systems and does not replace the Business Rules or other technical specification documents.



- 3 -

Revision History

CR Revision Date Revision Summary Appendix B 09/01/2005 Added October Q&A’s



- 4 -

Table of Contents Verizon East Release Overview ...........................................................................................................................1 October 2005 Release Overview..........................................................................................................................5 CLEC Affecting Release Overview .......................................................................................................................5

LSOG 9 Implementation....................................................................................................................................5 C04-0053/386561 – Enhance Trouble Administration Process to Return More Current Status Codes............7 C04-1297/389111 – T5 Associating To and From Move Orders ......................................................................8 C04-1309/389112 - Parsed CSR for 800 Service .............................................................................................9 C05-0359/392942 – Use of LTN Field for Emergency 911 Telephone Number Listings ................................10

Non CLEC System Impacting Release Overviews .............................................................................................12 C04-1782/390436 – Migrate the Bulk Loop Qualification – Verizon West and the PAVA Bulk Loop Qualification Extract – Verizon East to the Verizon Wholesale Platform ........................................................12 C04-2264/391499 – Process SUP When Record Orders Have Completed ...................................................14 C04-2558/391882 – Deployment of Replacement Packet Switch Technology in Massachusetts ..................15 C05-0230/392562.1 – Subsequent Order Activity on Grandfathered Lines....................................................16 C05-0658/393442 – Flow Through South Centrex Post Migration Changes ..................................................18

APPENDIX A ......................................................................................................................................................19 Business Rules Engine Updates.....................................................................................................................19

APPENDIX B ......................................................................................................................................................36 October Q&A’s ................................................................................................................................................36



- 5 -

October 2005 Release Overview

CLEC Affecting Release Overview

LSOG 9 Implementation

Jurisdiction Verizon East

CR Type Type 3 – Industry Standard

Description This project covers the modifications based on the LSOG 9 industry specifications. Listed are the associated LSOG 9 initiatives:

• C04-1506/389412 – LSOG 9 Order – LSR, EU, HGI, RS, PS

• C04-1507/389413 – LSOG 9 Order – Loop/LNP

• C04-1508/389414 – LSOG 9 Order – Directory

• C04-1510/389474 – LSOG 9 Order – CRS, DDPS, IS, RPL, RFR

• C04-1511/389466 – LSOG 9 Order – Return Feeds

• C04-1512/389469 – LSOG 9 – Service Order Inquiry Process

• C04-1513/389470 – LSOG 9 Pre-Order – Multiple Pre-Order Transactions

• C04-1514/389471 – LSOG 9 Pre-Order – LMU, Loop Qual, xDSL Loop Qual

• C04-1515/389472 – LSOG 9 Pre-Order – CSI/ CSR

• C04-1516/389473 – LSOG 9 Pre-Order – Directory

• C04-1524/389493 – LSOG 5 Sunset

Phase Information N/A

Details For details on the LSOG 9 project please go to: http://www22.verizon.com/wholesale/lsp/lsogtransition/#



- 6 -

Business Rules Impacts Summarized For details on the LSOG 9 project please go to: http://www22.verizon.com/wholesale/lsp/lsogtransition/#

Edit Impacts Summarized For details on the LSOG 9 edits, please go to: http://www22.verizon.com/wholesale/lsp/lsogtransition/# and click on Related Topics - Business Rules.



- 7 -

C04-0053/386561 – Enhance Trouble Administration Process to Return More Current Status Codes


CR Type Type 5 – CLEC Initiated

Description The Local Service Interface - Trouble Administration Status Inquiry and Enhanced Status Inquiry transactions have been improved to provide the most current status of a pending repair trouble ticket.


Details This initiative implements system enhancements that will evaluate a more comprehensive set of status codes so that the most current ticket status can be provided.

This new process will improve the ticket status displayed on the Status Inquiry and the Enhanced Status Inquiry windows. By navigating from the Enhanced Status Inquiry to the trouble ticket details, the user will have an opportunity to request a list of current and previous statuses and their associated date and time. In all cases the status code field will hot link to a list defining the code.

As a result, the CLEC will not have to call into the Regional CLEC Maintenance Center (RCMC) to request status information.

Business Rules Impacts Summarized N/A

Edit Impacts Summarized N/A



- 8 -

C04-1297/389111 – T5 Associating To and From Move Orders



Description The purpose of this initiative is to modify the criteria in which a SUP 2 can be submitted. In addition, notes will be added to the DDDO (Desired Due Date Out) field to clarify the use of this field.


Details In cases where the new Account Telephone Number (ATN) does not equal the Existing Account Telephone Number (EATN) the F order and the T order can have different due dates.

In cases where the ATN = EATN, depending on Dual Service criteria being met, Dual Service may or may not be available.

SUP 2 is being expanded to include changes to the DDDO field and/or the DDD field only.

Business Rules Impacts Summarized

Form, Transaction or

Section Field Number and Name

Action (Add

Change Delete) Section Data

LSOG 6 - 018 - DDDO

A Valid Entry Notes

Add new Valid Entry Note

LSOG 9 - 021 - DDDO

A Field Notes Add two new Field Notes

LSOG 6 - 030 - SUP

C Valid Entry Change Valid Entry

LSR Form

LSOG 9 - 036 - SUP

C Valid Entry Notes

Change Valid Entry Note




- 9 -

C04-1309/389112 - Parsed CSR for 800 Service



Description The purpose of this initiative is to enhance the parsing logic for the Pre-Order CSR transaction so that 800 Service telephone numbers will display in the FEATURE DETAIL field instead of creating a separate Working Telephone Number (WTN) occurrence.


Details The WTN field is obtained from the floating FIDs: TN, CX, and PX in the S&E section of the CSR. When the above FIDs are found a TN group is created. Today, the parsing logic is creating an additional TN group when an 800 Service telephone number is found. This initiative will parse the 800 Service telephone number to the FEATURE DETAIL field instead of the WTN field. When the TN FID is preceded by an 800 Service USOC, e.g. W1E or 819S+, the telephone number following the TN, i.e. 888-NXX-LINE will be parsed to the Feature Detail field.





- 10 -

C05-0359/392942 – Use of LTN Field for Emergency 911 Telephone Number Listings



Description This initiative will allow CLECs to submit 911 Emergency Telephone Number listing requests through existing interfaces without contacting the NMC for a project number and manual handling.


Details Currently the Listing Telephone Number (LTN) field on the Directory Listing (DL) form requires a 10 digit numeric entry. This initiative will allow a 3 digit numeric to be entered for Emergency Telephone Number listings and allow the request to continue processing. When utilized for Emergency Telephone Number listings, 911 must be entered in the first three positions of the LTN field and positions 4-10 must be blank.

Only listings for 911 will be accepted and the Type of Account (TOA) field must equal C (County), F (Federal), L (Local or City Government) or S (State Government).

The Directory Identifier (DIRIDL) field is required when the LTN field is populated with 911 and the Listing Activity Indicator (LACT) field is N or I.


Form, Transaction or

Section Field Number and Name

Action (Add

Change Delete) Section ** Data

A Valid Entry Notes

Add two new Valid Entry Notes

LSOG 6 - 038 – LTN LSOG 9 - 038 - LTN

A Usage Notes

Add new Usage Note

Directory Listing

LSOG 6 - 032 – DIRIDL LSOG 9 - 032 - DIRIDL

A Usage Notes

Add new Usage Note



- 11 -

Edit Impacts Summarized

Action LSOG Version

Form Error Code

Field #

Field Error Code Description / Notes

New 6 & 9 DL TBD 038 LTN LTN 911 requires TOA equal to C, F, L or S.”

A new Edit will be implemented requiring the TOA to equal C, F, L, or S when 911 is populated in the LTN field.

New 6 & 9 DL TBD 038 LTN “LTN not in correct format”

A new Edit will be implemented when LTN is less than 10 numerics and 911 is not in positions 1-3 or when the LTN is populated with 911 in positions 1-3 and positions 4-10 contain numerics.

New 6 & 9 DL TBD 032 DIRIDL “(DL:CK) Directory Identifier CK Required when ((the DL.LACT = to "N" or "I") and (LTN field positions 1-3 = 911.)).

A new Edit will be implemented indicating the DIRIDL field is required when LTN is populated with 911 in Pos 1-3.



- 12 -

Non CLEC System Impacting Release Overviews

C04-1782/390436 – Migrate the Bulk Loop Qualification – Verizon West and the PAVA Bulk Loop Qualification Extract – Verizon East to the Verizon Wholesale Platform

Jurisdiction

Verizon East and West

Description

The purpose of this initiative is to migrate certain CLEC reports from the current FTP Report platform to the new Customer Wholesale Portal (CWP) Reports platform. The following East Report is impacted by this initiative

• PAVA Bulk Loop Qualification Extract – Verizon East With the transition, there will be no impact to the structure of the existing report. In addition, a dual environment for the PAVA Bulk Loop Qualification report will be maintained for 30 days during the user ID/password set up period to allow for gradual migration to the CWP Report platform.

Phase Information

N/A

Details

Current Process: CLECs can request the PAVA Bulk Loop Qualification Extract – Verizon East via the FTP (File Transfer Protocol).

New Process: The PAVA Bulk Loop Qualification Extract – Verizon East will be available to those CLECs that have Verizon East License Agreements for the East Bulk Loop Qualification Extract and have registered via the Customer Wholesale Portal Platform in Verizon East. CLECs will access both extracts from www.verizon.com/wholesale using a standard web browser with secured HTTPS. Login IDs and passwords will utilize a delegated user registration model. File Availability: There will be no change to the file availability of the PAVA Bulk Loop Qualification Extract – Verizon East. This file, formerly called the PAVA Bulk Loop Makeup Extract, includes the fGTE areas that have converted to fBA systems and will be in the same format as the Verizon West Bulk Loop Qualification Extract (see example below). New files will be available weekly. The files will be zipped and .tar. There will also be a date on each file in the following format: ccyymmdd.



- 13 -

W|WC#|WireCenterName|

Line for each working TN in the Wire Center: T|Telephone#|CLLI|Parsed Address fields – SAPR, SANO, SASF, SASD, SASN, SATH, LD1 & LV1, LD2 & LV2, LD3 & LV3, CITY, State, Zip Code, |PrivacyIndicator|BTQ|BTLEN|LoopLength|26GaugeLength|Load Coil quantity|RNQ|Service TypelnnnnnnnnnnnlNNNNNN /ELL/HILD/D4A/D4ALST/HLST/Z

Establishing Connectivity to Customer Wholesale Portal (CWP) Reports For new users, you will need to send a request with contact information to: [email protected] Upon receipt of a request a registration letter will be forwarded. Please do not submit request for this report until October 9, 2005. Each CLEC must designate the primary interface or Customer User Administrator (CUA) for company access to the Customer Wholesale Portal Reports. Each company must have at least one CUA to access these reports. The CUA will have the responsibility to approve/reject access to other designated users within their company. A company may request more than one CUA.


N/A

Edit Impacts Summarized

N/A



- 14 -

C04-2264/391499 – Process SUP When Record Orders Have Completed

Jurisdiction Verizon – NJ, PA, DE

Description This initiative will automate processing of SUP requests when record orders have been completed but the provisioning order is still pending.


Details When a SUP 2 or SUP 3 is received on an LSR that has record orders which have completed, but the provisioning order is still pending; the applications will issue new record orders to reverse the information on the completed order and then process the SUP. This process will address both end user N and R orders for listings, where the provisioning order is pending due to a jeopardy status.





- 15 -

C04-2558/391882 – Deployment of Replacement Packet Switch Technology in Massachusetts

Jurisdiction Verizon – MA

Description The purpose of this initiative is to prevent UNE-Switching Services in central offices that have been converted to Packet Switch technology.


Details The following LSRs will be rejected for areas converting to Packet Switch technology when the Desired Due Date (DDD) field is greater than 14 calendar days prior to the switch conversion date:

• REQTYP DB (UNE – Platform) *

• REQTYP FB (UNE Port)

• REQTYP MB (Combined Loop and UNE Port)

• REQTYP NB when the Product (P) field = B or C

• REQTYP NB when the Product (P) field = D *

• REQTYP AB and 2nd character of the TOS = P *


Edit Impacts Summarized An existing edit will be used

SR228 Product not available, unable to process request.

* Contingent upon a Wholesale Advantage Contract Agreement



- 16 -

C05-0230/392562.1 – Subsequent Order Activity on Grandfathered Lines


Description This initiative will care for the automated processing of certain ordering scenarios for accounts that due to the packet switch conversion, were changed from UNE-P Linesplitting to Resale Linesharing.

A Provider Notification (PN) will be sent to the data provider (DLEC) to advise of a change to the voice portion of the account.


Details The following ordering scenarios will now be processed for these Resale Linesharing accounts:

• Resale Lineshare voice migration to another Reseller

• Resale Lineshare data disconnect

PN will now be sent to the DLEC to advise of a change to the voice portion of the account:

• Resale Lineshare voice migration to another Reseller

o Key fields sent on this PN are:

NT = “B” (Line share notification)

NTA = “H” (Configuration Change)

ECCKT (Current Circuit)

• Resale Lineshare change of telephone number



NTA = “B” (End user change telephone number)


TNC (New Telephone Number)

• Resale Lineshare full line disconnect



NTA = “A” (End user disconnect)



- 17 -






- 18 -

C05-0658/393442 – Flow Through South Centrex Post Migration Changes

Jurisdiction Verizon South

Description This initiative will automate Platform and Resale Centrex post-migration changes for the following:

• LPIC/PIC changes

• Features: Add/Change/Delete

• Add Auxiliary lines (Centrex and POTS)

• Telephone number changes


Details These changes for Platform and Resale Centrex post-migration changes, which are currently handled manually, will now begin to flow through.





- 19 -

APPENDIX A

Business Rules Engine Updates

As of this release the East Matrices functionality has been incorporated into the Business Rules Engine Database for Pre-Order, Order, Service Order Status and Trouble Administration. Below is a summary of the fields that reference specific appendices. Quick Links have been provided for ease of navigation. Order Advanced Intelligent Network/Line Information Data Base Form Appendix 3.5 - LIDB Matrix FEATURE, FEATURE DETAIL CENTREX Resale Services Form Appendix 3.4.7 - Verizon East Blocking Matrix BLOCK DID/DOD/PBX Services Form Appendix 3.4.8 & 3.4.9 - Verizon East Blocking Matrix BLOCK Directory Listing Form Appendix 3.6 - UNE Listing Account Comparison Matrix ALI Appendix 2.4 - Address Validation Requirements Matrix section 2.5 Thoroughfare Standards, in Pre-Order LATH Appendix 2.4 - Address Validation Requirements Matrix section 2.10 Community Abbreviations, in Pre-Order LALOC Appendix 2.4 - Address Validation Requirements Matrix section 2.9 Location Designator (LD1) Values, in Pre-Order LD1 Appendix 2.4 - Address Validation Requirements Matrix section 2.9 Location Designator (LD) Values, in Pre-Order LD2 Appendix 2.4 - Address Validation Requirements Matrix section 2.7 Location Designator 3 (LD3) Values, in Pre-Order



- 20 -

LD3 End User Information Form Appendix 2.4 - Address Validation Requirements Matrix section 2.5 Thoroughfare Standards, in Pre-Order SATH Appendix 2.4 - Address Validation Requirements Matrix section 2.8 Location Value 2 (LV2) Examples, in Pre-Order LV2 Appendix 2.4 - Address Validation Requirements Matrix section 2.6 Location Value 3 (LV3) Values, in Pre-Order LV3 Appendix 2.4 - Address Validation Requirements Matrix section 2.10 Community Abbreviations, in Pre-Order CITY Appendix 3.1 - Billing Account Structure Matrix EATN ISDN BRI/PRI Service Form Appendix 3.3 - Ordering Matrix footnotes LNA Appendix 3.4.10 & 3.4.11 - Verizon East Blocking Matrix BLOCK Local Service Request Form Appendix 3.3 - Ordering Matrix REQTYP, ACT Appendix 3.1 - Billing Account Structure Matrix ATN, BI1, BAN1, BI2, BAN2 Appendix 3.2 - Loop and Platform ISDN Tables SLI, TOS, NC, NCI, SECNCI Port Service Form Appendix 3.4.1, 3.4.2, 3.4.3 & 3.4.4 - Verizon East Blocking Matrix BLOCK Appendix 3.3 - Ordering Matrix footnotes LNA, FA Resale Private Line Form



- 21 -

Appendix 2.4 - Address Validation Requirements Matrix section 2.10 Community Abbreviations, in Pre-Order CITY Appendix 2.4 - Address Validation Requirements Matrix section 2.8 Location Value 2 (LV2) Examples, in Pre-Order LV2 Appendix 2.4 - Address Validation Requirements Matrix section 2.6 Location Value 3 (LV3) Values, in Pre-Order LV3 Appendix 2.4 - Address Validation Requirements Matrix section 2.5 Thoroughfare Standards, in Pre-Order SATH Resale Service Form Appendix 3.4.5 & 3.4.6 - Verizon East Blocking Matrix BLOCK Appendix 3.3 - Ordering Matrix footnotes LNA, FA



- 22 -

In creating these matrices, version 6.7.2 was used as a baseline, below is a list of changes that are not documented in the system generated change logs since details would not be specific. LSOG 6 Changes 3.3 ORDERING MATRIX (Documentation change only) Footnote # 8 was modified as follows; From: DL form is required when the ELT field on the EU form is populated with “E” or “P”, otherwise the DL form is prohibited. To: The DL Form is required when the ELT field on the EU Form is populated with a value of "E" or "P", otherwise the DL Form is prohibited when the ELT field on the EU Form is populated with "A" or "B". LSOG 9 Changes since 180 Day Initial Draft Distribution 3.3 ORDERING MATRIX (Documentation change only) Footnote # 8 was modified as follows; From: DL form is required when the ELT field on the EU form is populated with “E” or “P”, otherwise the DL form is prohibited. To: The DL Form is required when the ELT field on the EU Form is populated with a value of "E" or "P", otherwise the DL Form is prohibited when the ELT field on the EU Form is populated with "A" or "B". (CR# C04-1510) The CENTREX Resale heading was modified as follows: Added New sub-heading Standalone Directory listing: ACT = J, no CRS Form required, LSR, EU and DL Forms required Modified Post Migration Changes sub-heading From: ACT = C LNA = C To: ACT = C LNA = C, D, N Modified Post Migration Standalone Directory Listings sub-heading ACT = C ACT = J The DID/DOD/PBX Service heading was modified as follows: Modified Post Migration Changes sub-heading From: ACT = C LNA = C To: ACT = C LNA = C, D, N, X, P27 Added new footnote: #27 - the value of "P" is only applicable for TACT



- 23 -

The ISDN Service heading was modified as follows: Deleted the following ACT values from the Post Migration Changes sub-heading, as they are not supported for the REQTYP = QB ACT = B (Restore) ACT = S (Suspend) ACT = Y (Deny SNP)



- 24 -

Pre-Order Access Billing Customer Service Record Query and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.6 – Error Response Matrix PRESPC, PRESPD Address Validation Inquiry and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.4 – Address Validation Requirements AFT, SANO, SASF, SASD, SASN, SATH, SASS, LD1, LV1, LD2, LV2, LD3, LV3, CITY, WTN Appendix 2.5 – Thoroughfare Standards SATH Appendix 2.6 – Location Value 3 Values LV3 Appendix 2.7 – Location Designator 3 Values LD3 Appendix 2.8 – Location Value 2 Examples LV2 Appendix 2.9 – Location Designator 1 Values LD1 Appendix 2.10 – Community Abbreviations CITY Appendix 2.15 – Error Response Matrix PRESPC, PRESPD



- 25 -

Conversational TN Reservation / Return Inquiry and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.4 – Address Validation Requirements AFT, SANO, SASF, SASD, SASN, SATH, SASS, LD1, LV1, LD2, LV2, LD3, LV3, CITY Appendix 2.5 – Thoroughfare Standards SATH Appendix 2.6 – Location Value 3 Values LV3 Appendix 2.7 – Location Designator 3 Values LD3 Appendix 2.8 – Location Value 2 Examples LV2 Appendix 2.9 – Location Designator 1 Values LD1 Appendix 2.10 – Community Abbreviations CITY Conversational TN Selection Inquiry and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.4 – Address Validation Requirements AFT, SANO, SASF, SASD, SASN, SATH, SASS, LD1, LV1, LD2, LV2, LD3, LV3, CITY Appendix 2.5 – Thoroughfare Standards SATH



- 26 -

Appendix 2.6 – Location Value 3 Values LV3 Appendix 2.7 – Location Designator 3 Values LD3 Appendix 2.8 – Location Value 2 Examples LV2 Appendix 2.9 – Location Designator 1 Values LD1 Appendix 2.10 – Community Abbreviations CITY Collocation Assignment Validation Query and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.15 – Error Response Matrix PRESPC, PRESPD Customer Service Record Information Query and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.4 – Address Validation Requirements AFT, SANO, SASF, SASD, SASN, SATH, SASS, LD1, LV1, LD2, LV2, LD3, LV3, CITY, Appendix 2.5 – Thoroughfare Standards SATH, LATH Appendix 2.6 – Location Value 3 Values LV3 Appendix 2.7 – Location Designator 3 Values LD3



- 27 -

Appendix 2.8 – Location Value 2 Examples LV2 Appendix 2.9 – Location Designator 1 Values LD1 Appendix 2.10 – Community Abbreviations CITY Directory Listing Query and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.6 – Error Response Matrix PRESPC, PRESPD Appendix 2.13 – Directory Listings LTN, FINDINGNAME, DIRIDL, FIRSTLVLSUBCAP, LISTID, PKGID, MDNIND Fiber Availability Inquiry and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.4 – Address Validation Requirements AFT, SANO, SASF, SASD, SASN, SATH, SASS, LD1, LV1, LD2, LV2, LD3, LV3, CITY, Appendix 2.5 – Thoroughfare Standards SATH Appendix 2.6 – Location Value 3 Values LV3 Appendix 2.7 – Location Designator 3 Values LD3 Appendix 2.8 – Location Value 2 Examples LV2 Appendix 2.9 – Location Designator 1 Values



- 28 -

LD1 Appendix 2.10 – Community Abbreviations CITY Location Porting Query and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.15 – Error Response Matrix PRESPC, PRESPD Loop Makeup Query and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.4 – Address Validation Requirements AFT, SANO, SASF, SASD, SASN, SATH, SASS, LD1, LV1, LD2, LV2, LD3, LV3, CITY, Appendix 2.5 – Thoroughfare Standards SATH Appendix 2.6 – Location Value 3 Values LV3 Appendix 2.7 – Location Designator 3 Values LD3 Appendix 2.8 – Location Value 2 Examples LV2 Appendix 2.9 – Location Designator 1 Values LD1 Appendix 2.10 – Community Abbreviations CITY



- 29 -

Loop Qualification Query and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.4 – Address Validation Requirements AFT, SANO, SASF, SASD, SASN, SATH, SASS, LD1, LV1, LD2, LV2, LD3, LV3, CITY, Appendix 2.5 – Thoroughfare Standards SATH Appendix 2.6 – Location Value 3 Values LV3 Appendix 2.7 – Location Designator 3 Values LD3 Appendix 2.8 – Location Value 2 Examples LV2 Appendix 2.9 – Location Designator 1 Values LD1 Appendix 2.10 – Community Abbreviations CITY Product/Service Availability Query and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.15 – Error Response Matrix PRESPC, PRESPD Appendix 2.16 – Product And Service Availability Response – Parsing Rules PICDETAILS, LPICDETAILS, CALL, CIS, CP, CAS, MPG, DIRDET, CCALL, NPA/NXX, DR, CFII, BK, CAC, PS, ID, VM, SC, TELE Reservation Maintenance Inquiry and Response



- 30 -

Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.15 – Error Response Matrix PRESPC, PRESPD Reservation Maintenance Modification Inquiry and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.15 – Error Response Matrix PRESPC, PRESPD Scheduling Inquiry/Availability Query and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.15 – Error Response Matrix PRESPC, PRESPD Appendix 2.17 – Scheduling And Availability – Parsing Rules APPRES Service Analyzer Inquiry and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values



- 31 -

TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.15 – Error Response Matrix PRESPC, PRESPD xDSL Loop Qualification Query and Response Appendix 2.1 – TXTYP Valid Values TXTYP Appendix 2.2 – TXACT Valid Values TXACT Appendix 2.3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 2.4 – Address Validation Requirements AFT, SANO, SASF, SASD, SASN, SATH, SASS, LD1, LV1, LD2, LV2, LD3, LV3, CITY, Appendix 2.5 – Thoroughfare Standards SATH Appendix 2.6 – Location Value 3 Values LV3 Appendix 2.7 – Location Designator 3 Values LD3 Appendix 2.8 – Location Value 2 Examples LV2 Appendix 2.9 – Location Designator 1 Values LD1 Appendix 2.10 – Community Abbreviations CITY



- 32 -

Service Order Status Installation Status Query and Response Appendix 1 – TXTYP Valid Values TXTYP Appendix 2 – TXACT Valid Values TXACT Appendix 3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 4 – Installation Job Status Codes INSTSTAT Appendix 5 – Circuit ID Formats For Installation Requests CKTTYPE, ECCKT Appendix 6 – Error Response Matrix PRESPC, PRESPD Service Order Inquiry Request and Response Appendix 1 – TXTYP Valid Values TXTYP Appendix 2 – TXACT Valid Values TXACT Appendix 3 – TXTYP/TXACT Combinations TXTYP, TXACT Appendix 6 – Error Response Matrix PRESPC, PRESPD



- 33 -

Trouble Administration ADSL High Band Special Service Test Request and Response Appendix C – Valid Circuit ID Format For Special Service Testing ECCKT Enhanced Status Inquiry Request and Response Appendix E – Valid Circuit ID Formats TRPTCKTID Appendix K – Status Codes STATCODE Extended Trouble History Request and Response Appendix B – Trouble Type Codes THITTYPCODE Appendix E – Valid Circuit ID Formats ECCKT Appendix Z – Special Services Final Status History THITTFINSTAT Special Service Test Request and Response Appendix C – Valid Circuit ID Format For Special Service Testing ECCKT Status Inquiry Request and Response Appendix C – Valid Circuit ID Format For Special Service Testing ECCKT Appendix H – Interpreting Status Inquiry Codes TTSTAT Trouble History Request and Response Appendix B – Trouble Type Codes THITTYPCODE Appendix E – Valid Circuit ID Formats ECCKT Appendix Z – Special Services Final Status History THITTFINSTAT



- 34 -

Trouble Ticket Close Request and Response Appendix E – Valid Circuit ID Formats ECCKT Appendix H – Interpreting Status Inquiry Codes TTSTAT Appendix J – Allowable For Close Out ADDLERRINFO Trouble Ticket Create Request and Response Appendix B – Trouble Type Codes TTYPCODE Appendix E – Valid Circuit ID Formats ECCKT Appendix F – Test Result Codes TESTRLTCODE Appendix G – Valid Override Handle Codes OVERHANDCODE Trouble Ticket Inquiry Request and Response Appendix B – Trouble Type Codes TTYPCODE Appendix E – Valid Circuit ID Formats ECCKT Appendix F – Test Result Codes TESTRLTCODE Appendix G – Valid Override Handle Codes OVRHANDCODE Trouble Ticket Modify Request and Response Appendix B – Trouble Type Codes TTYPCODE Appendix E – Valid Circuit ID Formats ECCKT Appendix G – Valid Override Handle Codes OVRHANDCODE



- 35 -

Trouble Ticket Partial ID Search Request and Response Appendix E – Valid Circuit ID Formats ECCKT Trouble Ticket Service Recovery Request and Response Appendix E – Valid Circuit ID Formats ECCKT Appendix H – Interpreting Status Inquiry Codes TTSTAT Trouble Ticket Test Request and Response Appendix B – Trouble Type Codes TTYPCODE Appendix E – Valid Circuit ID Formats ECCKT Appendix F – Test Result Codes TESTRLTSUM Vertical Feature Verification Request and Response Appendix E – Valid Circuit ID Formats ECCKT



- 36 -

APPENDIX B

October Q&A’s

# Date received

CLEC CR Subject Question Answer Business Rules Impact

1 08/17/05 AT&T C04-1512

LSOG 9 HNTYP Field on the HGI Form, not clear on valid entries if need to be zero filled.

Business rules will be updated to add a Field Note for clarification.

Y

2 08/17/05 Broadview C04-0053

Trouble Administration Process to Return More Current Status Codes

Can we provide screen snap shots for the window that returns status codes?

Yes, we will provide screen snap shots.

N

3 08/17/05 AT&T C04-1297

T5 Associating To and From Move Orders

On full migrations, when do they know if there is fiber or dual service on the line? When there is fiber on the line at what point do they get a reject and if it’s after the FOC what does it look like?

The validation occurs up front. Since the validation is done upfront, the 2nd question is not applicable.

N

4 08/17/05 AT&T C05-0359

Use of LTN Field for Emergency 911 Telephone Number Listings

In general would the Listed Name contain the Government Name or Agency?

Yes. N

5 08/17/05 AT&T C04-2558

Deployment of Replacement Packet Switch Technology in Massachusetts

What switches will not support UNE-P requests, can we provide a list. Also was there a notification sent out?

Refer to the Industry Notification distributed on May 27th and updated on August 12th. This notification provides all the names and conversion dates.

N

6 08/17/05 AT&T C04-2558

Deployment of Replacement Packet Switch Technology in Massachusetts

Will we be able to order UNE-P service for the customers in these switches?

It depends. A CLEC must have an amendment or contract on file. Contact the account manager for specific details.

N



- 37 -

7 08/17/05 Neustar N/A LSOG 6.8.0, EDI technical specs

Regarding the technical specs change log, Order – EDI examples have been changed for EU and LSR forms. Compared the examples between V 6.7.2 and 6.8.0 and found there are no EDI example changes on the EU form but for the LSR form, the font style is regular but not italic for the Field PROJINDR. Field OLDCCNA in the LSR EDI example is missing. I checked the LSOG 6.8 business rules and the field is still supported by Verizon and it's listed in the field spec. My question is: What are the exact changes made in the LSOG 6.8 EDI examples? LSOG 6.8.0, Pre-Order - EDI examples have been changed for DLA, CSA and ISA. In the example for DLA, the field font style is regular, which is inconsistent with the other EDI examples. The reason for the change is formatting fixed. My question is, can we use italic font style for the fields to distinguish with the EDI qualifier? For CSA and ISA, can we list the changing fields in the change log?

EDI has responded with the following: 1- LSOG 6.8.0 Order - There should have been no changes to LSR or EU examples. PROJINDR will be re-italicized, and OLDCCNA will be re-added. 2 - LSOG 6.8.0 Preorder – the DLA response formatting was lost. The fields will be re- italicized, as in the previous version. LSOG 6.8.0 Preorder For CSA and ISA responses, changes are as follows: (cleanup indicates the following) A.)CSA Example (parsed): OV field's extra asterisk between OV and SO-RSQ Account group: PID*X**TI*OV****SO-RSQ*OV B.)CSA Example (parsed): fixed typo LAZ changed to LAZC Account group: N4** LAST* LAZC C.) DLR Guide: Fixed comment for Hunting Type Code Field from "See Table 4 for Conversion" to "See Table 4.1 for Conversion" D.) ISR Example: corrected field CKTYPE example: from PID*X**TI*CKTTYP*CKTYPE E added to data value in example.

Y

verizon east release overvie · 2012-05-18 · verizon east release overview release overview...

Documents