Identifies the provider circuit ID or multiple circuit IDs.
NOTE 1: The provider assigning this circuit identifier determines the content of this field in accordance with COMMON LANGUAGE standards maintained by Telcordia Technologies.
NOTE 2: When a component within the format is purposely omitted, the component should still be delimited and compressed to eliminate any spaces.
NOTE 3: All components within the ECCKT should be delimited by either virgules or periods.
NOTE 4: If all positions in a component within the ECCKT are not populated, the component should be compressed to eliminate any spaces.
NOTE 5: Use of ranging is based on customer/provider negotiations. Ranges should be shown within the appropriate component of the ID by specifying the lowest value of the component, hyphen, highest value of the component, e.g., trunk numbers 3500 through 3512 would be shown as 3500-3512.
NOTE 6: When disconnecting all circuits in a given account, “ALL” should be entered in this field, the BAN field populated, and the ACT field should contain a “D”.
NOTE 7: The COMMON LANGUAGE Special Service Circuit Code in this field should not reflect a value that equates to the EVC circuit identification.
NOTE 8: The format and structure of the field is defined in ANSI approved standards.
VALID ENTRIES:
1. COMMON LANGUAGE Special Service Circuit Codes (CLCI S/S Codes) as defined in the ANSI approved standard, ATIS-0300097:, Structure for the Identification of Telecommunications Connections for the North American Telecommunications Systems or by COMMON LANGUAGE in BR-795-402-100. A brief summary of the format can be found in ASOG Practice 000, Section 2.14.3 and 2.14.4.
EXAMPLES: A 2 / S B F S / 2 0 1 / 9 8 1 / 3 5 0 0 / / 1 2 3
A 2 / L B F S / 0 3 2 7 1 9 / 0 0 1 / N Y
2. COMMON LANGUAGE Message Trunk Circuit Codes (CLCI MSG Codes) as defined in the ANSI approved standard, ATIS-0300097: Structure for the Identification of Telecommunications Connections for the North American Telecommunications System or by COMMON LANGUAGE in BR-795-400-100. A brief summary of the format can be found in ASOG Practice 000, Section 2.14.2.
EXAMPLE: 1 2 3 4 / A F 5 4 I E C N / M D S N W I 1 6 C G 0 / M -
/ D S N W I 0 2 0 I T
/ D F 5 5 I E / B S T N M A A A C G 0 / M -
/ M C D N M A C O C G 1
3. COMMON LANGUAGE Facility Codes (CLFI Codes) as defined in the ANSI approved standard, ATIS-0300097, Structure for the Identification of Telecommunications Connections for the North American Telecommunications System or by COMMON LANGUAGE in BR-795-450-100. A brief summary of the format can be found in ASOG Practice 000, Section 2.14.5.
NOTE 1: For identification of an unbundled multiplexer (including the collocation cross-connect), unbundled transport or a high capacity facility to a HUB location.
NOTE 2: Either Location A or Z must be 11 characters.
EXAMPLE: 1 0 1 / T 1 / N Y C M N Y 5 0 / N Y C M N Y 5 4 W 0 1
USAGE: This field is conditional.
NOTE 1: Prohibited when the EVCI or PVCI field is “A”.
NOTE 2: Required when the ACT field is “C”, “D”, “M” or “T” and the first position of the TQ field is not “S”.
NOTE 3: Required when the ACT field is “N”, the first position of the TQ field is not “S”, and the CCVN field is populated.
NOTE 4: Required when the ACT field is “N” or “R”, the first position of the TQ field is not “S”, and an ECCKT has been previously provided to the customer.
NOTE 5: Otherwise optional.
DATA CHARACTERISTICS: 53 alpha/numeric characters.