CLLI?
Diane Dubinsky
character
code for identifying End Office Locations.
Diane Dubinsky
ccmail....@nynex.com
Scott Statton
Not quite....
CLLI is used for much more than End Offices -- any terminal also has
a CLLI, and certain customer premises have CLLIs as well ...
The general format of a CLLI is 11 characters, broken down into four fields:
4 characters City Identifier
2 characters State
2 characters Building
3 characters Entity within a building.
These last two fields get tinkered with the most -- sometimes it's not a
building, but a code identifier meaning "some customer premises in that
area..."
Some examples (from memory -- errors mine)
CMBRMABE03T -- A big toll tandem for the Boston area
CMBRMA Cambridge, MA
BE Bent Street facility (180 Bent)
03T The toll tandem there
CMBRMABECG0 The 1A at that same location (probably gone by now, sniff)
SNFCCA2143T -- Where nearly all IXC service in San Francisco comes from
SNFCCA San Francisco, CA
21 Pacific Bell numbers their offices -- This one is Montgomery
street, I think.
43T A toll tandem.
End offices end with Entity codes like MG0, MG9 for Crossbars,
CG0, CG1 for ESS 1 and 1A, DS0 for 5Es and DMS (barf), nnT for toll
switches. There's other's that I've seen ... A customer location
might be (I hope i'm not stepping on toes here)
SNFCCAWDD07 An IXC switch
SNFCCA San Francisco, California
WD A code for "IXCs"
D07 A sequence within the WD group.
I've also seen customer locations with the suffix being AFN01 for a T-3
terminal. I used to have a big list of the CLLIs for one of my previous
client's network -- every Mux, had a seperate CLLI...
Scott
Dave Sellers
Scott Statton <n1...@netcom.com> wrote:
>In article <2poed3$f...@news.nynexst.com>,
>Diane Dubinsky <ccmail....@nynex.com> wrote:
>>CLLI stand for Common Language Location Identifier. It is an 8
>>character
>>code for identifying End Office Locations.
>>
>>Diane Dubinsky
>>ccmail....@nynex.com
>
>Not quite....
>
>CLLI is used for much more than End Offices -- any terminal also has
>a CLLI, and certain customer premises have CLLIs as well ...
>
>The general format of a CLLI is 11 characters, broken down into four fields:
>4 characters City Identifier
>2 characters State
>2 characters Building
>3 characters Entity within a building.
>
>These last two fields get tinkered with the most -- sometimes it's not a
>building, but a code identifier meaning "some customer premises in that
>area..."
>
I believe the lenght can be like 32 characters. In a Telco, you
can take the identification right down to the floor, aisle, bay, shelf, etc.
It is not restricted to Telco stuff either. Any building, equipment, etc.
can be registered and given an ID.
I know Bell Canada had a database of this stuff, but I haven't played with
it for a while. Like any standard, the names got/get too long for anyone
to remember them. They are usually shortened to <8 characters, plus they
take up a lot of VDU screen space......
--
Dave Sellers, Managing Consultant
BELL Sygma - Telecom Solutions
Floor 17 Grey, 160 Elgin St. Ottawa, Ont., Canada, K2P 2C4
sel...@ON.Bell.ca VOICE= (613) 785-2694 IIS= SELLERS ENVOY= DA.SELLERS
Jay Hennigan
>CLLI stand for Common Language Location Identifier. It is an 8
>character
>code for identifying End Office Locations.
Way back in the 1970s, I remember the beginnings of this. I was working
microwave radio for Pacific Bell, and they assugned four-letter location
identifiers to the various microwave station locations, usually along the
lines of the following:
STPK = Strawberry Peak
PAHL = Padua Hills
LYCK = Lytle Creek
KLPK = Keller Peak
and so on.
All went well until they got to the installation at Furnace Creek. The
obvious happened. I don't remember what they changed it to.
Al Varney
>In article <n1gakCo...@netcom.com>,
>Scott Statton <n1...@netcom.com> wrote:
>>In article <2poed3$f...@news.nynexst.com>,
>>Diane Dubinsky <ccmail....@nynex.com> wrote:
>>>CLLI stand for Common Language Location Identifier. It is an 8
>>>character
>>>code for identifying End Office Locations.
>>
>>Not quite....
>>
>>CLLI is used for much more than End Offices -- any terminal also has
>>a CLLI, and certain customer premises have CLLIs as well ...
>>
>>The general format of a CLLI is 11 characters, broken down into four fields:
>>4 characters City Identifier
>>2 characters State
>>2 characters Building
>>3 characters Entity within a building.
>>
>>These last two fields get tinkered with the most -- sometimes it's not a
>>building, but a code identifier meaning "some customer premises in that
>>area..."
>>
>It's been a while, but I don't think this is correct either.
>I believe the lenght can be like 32 characters. In a Telco, you
>can take the identification right down to the floor, aisle, bay, shelf, etc.
I hate to appear to explain what Bellcore claims as a trademark (CLLI and
the whole set of "COMMON LANGUAGE" codes). The term CLLI refers to a LOCATION,
encoded into 11 characters. These are subdivided as Scott described above.
These codes are primarily useful as part of a more elaborate identifier,
for circuits, facilities or equipment.
For example, a CLCI (common language circuit identifier) is a 44 character
code that uniquely describes a particular voice, data or other circuit type
between two end-points. In the case of public telephone switches acting as
the end-points, the CLLI of the two switches appears in the circuit code.
CLCIs look like (spaces are not part of the code):
nnnn AAAAAAAAAAA ZZZZZZZZZZZ uuu uuuuuuuuuuuuuuu
where "nnnn" is a decimal number identifying a unique "member" of the circuit
group, AAAAAAAAAAA identifies "office A", ZZZZZZZZZZZ identifies "office Z"
and the remainder describes, in various subfields, the type of information
carried (message telephone service, operator, etc.), type of signaling used
and other such details. One rule to avoid duplicate assignment is that office
A is always the "lower" CLLI of the switch pair, sorted alphanumerically.
Bellcore maintains the extensive database of code values for each sub-field
in each Common Language code. They also maintain a manufacturer-specific set
of USO FIDs (universal service order field identifiers). Together, these
allow TELCos to develop inventory, billing, provisioning and planning tools
that will work with all their equipment and vendors. In addition, most
RBOCs use a Bellcore-maintained group of integrated software packages called
TIRKS (trunk integrated record-keeping system) to plan, provision and maintain
their trunk circuit plant. TIRKS relies on the use of CLCIs.
Many RBOCs require central office equipment to carry CLEI (common language
equipment identification) codes, supplied by the vendor. Even plug-in "units"
must carry this identification on bar-code labels. See Bellcore TR-STS-000383
for more information.
Al Varney - just my opinion