Transaction Language: Level 1
TL1 is a Man Machine Interface Language which allows us to communicate to
the DACS (Digital Access Cross Connect System) in our Network. It provides
a formatted language that will direct the equipment to perform specific
functions and create designated paths for the passage of digital signaling.
The language itself is very structured and requires precise punctuation to be
properly used. TL1 is broken down into specific blocks and each of these
blocks holds designated information. Sometimes the information is optional
and sometimes it is a required field.
THE BLOCKS
BLOCK#1: Verb-Modifier [-Modifier] Block
Definition: The Verb-Modifier block identifies the type of action (verb) that a
specific entity (modifier) should perform.
Below is an illustration, which shows the position of block #1 in the basic
command format.
VERB-MOD[-MOD] : [tid] : aid : ctag : : command specific parameters;
RTRV-ALM-ALL:
ENT-CRS-T1:
DGN-EQPT:
ACT-USER:
ENT-T1:
ED-STS1:
There are some requirements that are specific to each block. For Block #1
the following are required:




First required block
Verb: command action (what)
Modifier: entity performing action (to whom)
[-modifier]: additional information describing entity type
Follow the rules below to assign valid VERB-MODIFIER values.


Use a hyphen to separate the Verb and the Modifier.
Use a hyphen to separate a first Modifier from a second Modifier (if
used).
NOTES
BLOCK#2: [Target Identifier] Block
Definition: Typically used by Operational Support Systems (OSSs), the
[Target Identifier] or [tid] block identifies a specific network element.
The illustration below shows the position of block #2 in the basic command
format.
VERB-MOD[-MOD] : [tid] : aid : ctag : : command specific parameters;
RTRV-ALM-ALL:
ENT-CRS-T1:
DGN-EQPT:
ACT-USER:
ENT-T1:
ED-STS1:
:
:
:
:
:
:
There are some requirements that are specific to each block. For Block #2
the following are required:


Second required block
Identifies a Network Element (NE) other than the present equipment
you are logged into.
Follow the rules below to assign valid [tid] values.


Information within the brackets is optional.
Enter a value to identify a network element other than the present
equipment that you are logged into (default).
NOTES
BLOCK #3: Address Identifier Block
Definition: The Address Identifier Block, or aid block, identifies the exact
entity location where the command action will take place.
The illustration below shows the position of block #3 in the basic command
format.
VERB-MOD[-MOD] : [tid] : aid : ctag : : command specific parameters;
RTRV-ALM-ALL:
ENT-CRS-T1:
DGN-EQPT:
ACT-USER:
ENT-T1:
ED-STS1:
:
:
:
:
:
:
:
9-1,vt1-121-5-1:
MM-109:
Tellabs:
18-6&&-7:
STS1-81:
There are some requirements that are specific to each block. For Block #3
the following are required:


Third required block
Identifies entity or entities of command action
 Depending upon the command action, aid values may or may not be
required.
Follow the rules below to assign valid aid values.




Use a comma to separate values.
Enter as a single or ranged identifier.
Use && to denote through in a ranged entry.
Use a colon as a placeholder if a value is not entered.
NOTES
BLOCK #4: Correlation Tag Block
Definition: The Correlation Tag Block, or ctag block, is an alphanumeric
identifier that correlates input directly to a command response message. The
ctag identifies command ownership.
The illustration below shows the position of block #4 in the basic command
format.
VERB-MOD[-MOD] : [tid] : aid : ctag : : command specific parameters;
RTRV-ALM-ALL:
ENT-CRS-T1:
DGN-EQPT:
ACT-USER:
ENT-T1:
ED-STS1:
:
:
:
:
:
:
:
ctag;
9-1,vt1-121-5-1:ctag;
MM-109:
ctag:
Tellabs:
ctag:
18-6&&-7:
ctag:
STS1-81:
ctag:
There are some requirements that are specific to each block. For Block #4
the following are required:

Fourth and last required block
Follow the rules below to assign valid ctag.





The ctag can be 1-6 characters.
If the ctag begins with a number, the remaining characters must also be
numbers.
If the ctag begins with a letter, the remaining characters can be
alphanumeric.
Use a semi-colon at the end of the ctag if you are ending and entering
the command.
If you are continuing a command entry after the ctag, enter a single
colon after the ctag.
NOTES
BLOCK #5: General Block
Definition: The General block is presently an unused block. It is, however,
considered a required block in commands that continue after the ctag.
Therefore, a placeholder value is required to denote its identity within a
command.
The illustration below shows the position of block #5 in the basic command
format.
VERB-MOD[-MOD] : [tid] : aid : ctag : : command specific parameters;
RTRV-ALM-ALL:
ENT-CRS-T1:
DGN-EQPT:
ACT-USER:
ENT-T1:
ED-STS1:
:
:
:
:
:
:
:
ctag;
9-1,vt1-121-5-1:ctag;
MM-109:
ctag:
Tellabs:
ctag:
18-6&&-7:
ctag:
STS1-81:
ctag:
:
:
:
:
:
:
Follow the rules below to enter the General Block placeholder.


Enter a single colon only to acknowledge block.
This block has not been identified yet and will result in a failed
command if an entry is made.
NOTES
BLOCK #6 - #8: Command Specific Parameters Block
Definition: Command Specific Parameter blocks are used to identify values
that define additional command-specific actions.
The illustration below shows the position of block #6 - #8 in the basic
command format.
VERB-MOD[-MOD] : [tid] : aid : ctag : : command specific parameters;
RTRV-ALM-ALL:
ENT-CRS-T1:
DGN-EQPT:
ACT-USER:
ENT-T1:
:
:
:
:
:
:
ctag;
9-1,vt1-121-5-1:ctag;
MM-109:
ctag:
Tellabs:
ctag:
18-6&&-7:
ctag:
:
:
:
:
:
,3;
Tellabs#1;
DGR:linecde=b8zs,FMT=ESF:IS;
ED-STS1:
:
STS1-81:
ctag: :
::OOS;
Follow the rules below When working with command-specific parameter
blocks.






Use commas to separate parameters from other parameter values with
the block.
Use a comma as a placeholder if not entering a value in a positional
parameter position.
Use a colon (:) to separate parameter blocks
Enter keyword and value exactly as listed in any Equipment Specific
Command Reference materials.
Brackets surround optional parameters and keywords.
Keywords are not case-sensitive.
NOTES
The table below compares the three types of command specific parameter
blocks that can occupy blocks 6-8 of a command.
PARAMETER BLOCK TYPES
Single Parameter Block
Multiple Parameter Block





User State Blocks

CRITICAL ATTRIBUTES
Only one value between colons
May contain required or optional
parameters.
Two or more values possible between
colons
May be positional blocks:
- Parameters occupy certain
positions.
May be keyword required blocks:
- Parameters occupy any position
and are identified by keyword
PST value in either block 7 or 8
depending on command
The table below compares critical attributes of positional parameters and
keyword parameters as they apply to multiple- parameter blocks.
PARAMETER TYPE
Positional
Keyword Required






KEY ELEMENTS
Two or more associated values per positional
keyword
Occupies certain position within the block
Enter value only if needed (keyword optional)
Must be entered
Keyword identifies the parameter, not the
position
Parameters are defined in Command Reference
material for the specific equipment (i.e.,
LINECDE=B8ZS)
NOTE: Positional & Keyword parameters are never entered together in the same block.
The user state block is used to place an entity (facility or hardware) in a state
where the user expects, or does not expect service to be provided.


Last optional block
Identifies the Present State of given entity
- In-Service (IS)
- Out-of-Service (OOS)
VERB-MOD[-MOD] : [tid] : aid : ctag : : command specific parameters;
RTRV-ALM-ALL:::ctag;
ENT-CRS-T1::9-1,vt1-121-5-1:ctag;
DGN-EQPT::MM-109:ctag:: ,3;
ACT-USER::Tellabs:ctag::Tellabs#1;
ENT-T1::18-6&&-7:ctag::DGR:linecde=b8zs,FMT=ESF:IS;
ED-STS1::STS1-81:ctag::::OOS
The commands built in this lesson represent the following:

RTRV-ALM-ALL is an example of a mull aid

ENT-CRS-T1 is an example of two aids in an aid block

DGN-EQPT is an example of a positional parameter block

ACT-USER is an example of a single parameter block

ENT-T1 is an example of a keyword parameter block

ED-STS1 is am example of all eight block used, no parameter
NOTES
Company Interface Databases:
Hekimian React 2001:



Indirect interface properties with the DACS Equipment
Unit allowing interface for cross connects and status is NE Control
Database includes Testing facilities
Opening Screen:
ACCESS TO DATABASE

Enter designated Username

Enter assigned Password

Click on OK
Message screen and Database menu will be
opened on
Database Menu:
ACCESSING NE CONTROL

Menu contains Units
labeled File, Testing,
Smartest and Utilities

Each Unit contains subsets

Highlight Utilities to
locate NE Control

Highlight to open entry
screen
NE Access Screen:
NE ACCESS

Enter TID (Target Identifier)

Click on OK
If in doubt of the TID use the
Reference list located on page ## of
this manual.
NE Control Interface Screen:
INTERFACE MODE:

Select Enter CMD

Click on OK to send the
command string

Type TL1 command string
in the large message entry
screen on the left side


Do not use semi-colons in
command strings
Equipment responses are
displayed in the results
screen

Click on Cancel to exit the
Database
TelNet Sessions:




Direct interface sessions with the DACS equipment located in POP or Switch
Sites in the Company Network
TelNet Sessions generally contain shortcut function keys and help menus
Available function keys and menus vary per DACS vendor
Telnet Sessions are group password protected
Accessing Individual TelNet Sessions:
PROGRAM DATABASES PROVIDING TELNET ACCESS

Exceed Database offers TelNet access through HOST ACCESS

Some computers are set up with Hummingbird Neighborhood showing on
their computer Desktop

Access Hummingbird Neighborhood and then open the VT folder for
access to the individual sessions

Some computers are set up with a TelNet icon which opens a listing of all
available sessions as accessed by their IP addresses
Open Session screen:
OPEN SESSION

Profiles for each session are
listed by location name or ID
information

Highlight the profile that is
matches the equipment and
location that you need to open
a TelNet Session for

Double Click or select the
Connect button, which will now
show active
DACS TelNet Entry Screen:
ACCESSING THE TELNET SESSION (T:DAX)

UID: Type in the ID (User Id), hit enter All caps in TDAX / Varies in the
other vendors

PID: Enter the PID (Group assigned password), hit enter

DATE: Hit enter

TIME: Hit enter
ALCATEL SESSION

LOGIN: ACT-USER::uid:::pid;

User id and passwords are
assigned to each group.

Use CANC-USER; to exit
session
TELLABS TITAN 5500 SESSION

LOGIN: ACT-USER::uid:ctag::pid;

User id and passwords are assigned
to each group.

Use CANC-USER; to exit session
Menu Modes:
TDAX MENUS



Tadiran has created several helpful shortcuts into the TL1 format of their
product. These are menu modes that function in a direct or combined
entry method.
Hitting the “/” key on the number pad of the keyboard will access the
DIRECT menu mode which leads you through a series of selections to
reach the entry screen associated with the command you are trying to
enter.
Typing in a partial command (ENT-CRS-T1) and then hitting the CTRL “B”
will open an additional help screen that will show you a sample command
for you to use as a guide to complete the command that you are entering.
ALCATEL MENU MODE

F7 exits the direct entry screen and enters a menu selection screen.
Arrowing down to the appropriate menu item will in secondary and possibly
tertiary menus to provide a screen that will show all possible requirements
for a command and allow you to enter needed data.

Typing in the primary command string, verb and modifier, then selecting F7
will take you directly to the command appropriate screen.
Tellabs Titan 5500 contains a help menu that is similar to the Control “B” function in
Tadiran. It will bring up a sample command to give you a guide to follow but does
not provide the in-depth menus that the other vendor’s products provide. Tellabs
provides in-depth research material on their CD and in their Operations and
Maintenance manual. The reference materials are loaded on our system through
Inspire. Go to Inspire through the Internet then follow this path:
Departments/Network/Operations/Documentation
Not only will you be able to access the Tellabs documentation, but Tadiran and
Alcatel is also available.
What are TID’s?
TID’s specifically are individual equipment location addresses. In our Network
currently we have 2 identifiable addresses for each DACS. This is due to the
institution of the Metasolv database. The TID that have been used in the past are
formatted in a relatively simplistic style. They are broken down as follows:
BRHMALOWBHM =
BRHM
> the first four designated city abbreviation / this may not be characteristic
of the common abbreviation as widely known for that location.
AL > the state abbreviation.
OW > this represents that is Deltacom’s DACS equipment
BHM
(Owned)
> this is a repeat of the first three letters of the city abbreviation.
There are variables to this format that change due to multiple pieces of DACS
equipment in one switch site or a specific change in type of equipment in the
location. The variables are:
DSC DACS: the last three characters are DX and the first letter of the city
abbreviation.
Example:
DACS information for these requests can be found in the REACT 2001
Database.




Open REACT 2001
Go to Utilities and open NE Control
The NE Access box will appear. Type in the Target Identifier (TID) to
access the BHM Titan 5500 Tellabs DACS. [BRHMALOWBHM]
Use the mouse to select OK
This will bring up your interface entry screen. Here you will be able to verify
the current status of existing DS1’s and DS3’s. To do this you will enter a
command for each step of the process and verify the data that is returned.
To activate the entry process, use the mouse and select CMD. Next use the
mouse to open the interface section by clicking in the white open space below
the selection box.
Entering DS1/DS3 Cross Connects in the Titan 5500 DACS:
 Step 1:
Verify the current status of the requested cross-connect by entering the
following command. Both sides of the cross–connect circuit will have to be
checked. Enter the command below for each channel (for example a DS1 to
DS3 or DS3 to DS3).
Enter: RTRV-CRS-T1::123-01:AA;
 RTRV-CRS-T1 This portion of the command requests for the cross
connection status of the channel. It is the actual request for the information.

123-01 This is information which pertains to the DS1/3 circuit lines. In
this instance it may contain the Bay, Shelf and Slot data for the request.

AA This is the C-tag or correlation tag. Here it is shown as AA but during
entries, which you perform, it will be your initials. The C-tag is your
initials.
Note: It is very important to enter the command exactly as you see it above
other than the C-tag or the individual Bay, Shelf and Slot data. All hyphens,
colons, semi-colons, punctuation marks or symbols should be entered as
shown in the command phrase. An exception to this would be when you
access the DACS through the use of a TelNet session. When using a TelNet
session you will have to use the “;” to execute or send the command phrase
but when using NE Control you will not be able to use the “;” to execute the
command. Simply typing the command phrase without the final “;” and using
the mouse to select OK will enter your request.
The command string above is comprised of TL1 language. To become
acquainted with the formatting and structure of this language we will
breakdown the command for better understanding. This will only be done
when a new command is used. Further instructions will be given without such
additional information. Refer to this information when needed in future for
clarification.
 Step 2:
After verifying the cross connect status of the channels it is now time to check
their current optioning status. Entering a command that will retrieve data
specific to each DS1 or DS3 singularly does this. The data retrieved will allow
you to determine if the channel is operational (active) or if it is optioned (the
functioning characteristics of the individual connection) correctly.
Enter: RTRV-T1::123-01:AA;

RTRV-T1 Requests for the system to check the current status of the
individual channel/line. This retrieve will tell you if the line is already
assigned, out of service, or how it is optioned.
*Note: Type all punctuation or symbols as shown.
 Step 2-A:
As stated above this command will provide data that is specific to the
individual channel/line. Through your interface with the DACS, you will
receive the information you require to direct you in the process of making the
actual cross connection. Below are statements that will be retrieved and what
step you will then perform to prepare the circuit for connection.
BRHMALOWBHM 99-09-02 15:30:43
TD COMPLD
"0246-01:CST:PMAID=PM30246,TACC=0,IDLECDE=AIS,OOSCDE=AIS,
FMT=ESF,GOS=2,ALM=INH,ALMPF=99,LPRST=YES,,,FENDPMTYPE=AN
SI403,DS1ADDR=C,CSUADDR=B,TMG=THRU,FLTRC=NA:PST=IS-NR"
BRHMALOWBHM 99-09-02 15:27:49
TD COMPLD
"0299-01:CST::PST=OOS-ANR-UAS"
OOS > (Out of Service)
ANR > (Abnormal rate)
UAS > (Unassigned)
If the system response returned to you after your retrieve shows you a circuit
that has specific options and has a present state (PST) of “IS-NR” (in service–
normal rate) like the example on the previous page for circuit 246-01, then
process to Step 3. If you receive the message shown for circuit 299-01 it is
an indication that this circuit needs to be “grown”. To do this follow the steps
below.
An important factor to determine when you are “entering” or “growing” a
circuit is it’s circuit group type. First you should determine if the channel is
“digroup” or “constituent”. A DS1 line will be digroup, which is identified as
DGR and a DS3 line will be constituent which is identified as CST.
DS1 = DGR
To “grow” a DS1 line enter:
DS3 = CST
ENT-T1::123-01:AA::DGR

ENT-T1 Requests that the channel be “entered” which will put the line in
active service but this will not specify the optioning available on the line.

DGR This represents “digroup”. It is used to indicate the type of line that
you are opening to service. This is a DS1 line so it is digroup / DGR.
To “grow” a DS3 line enter:

ENT-T1::123-01:AA::CST
CST This represents “constituent”. It is used to indicate the type of line
that you are opening to service. This is a DS3 line so it is constituent or
CST.
SHORTCUT: You can enter your facility with all of the parameters that you need it to be
optioned in one step. To do this you enter the command below:
ENT-T1::123-01:AA::(CST/DGR):FMT=ESF,LINECDE=B8ZS,GOS=2,
ALM=INH:IS

Mode=frcd is not needed for this command. "IS" is used to put it in service eliminating
the need to do that step as well.
 Step 2-A-1:
If the circuit is DGR, now enter:

ED-T1::123-01:AA::DGR::IS
ED-T1 This indicates to edit the T1 to create specific circuit parameters
for operation
 IS Indicates “in service”
If the circuit is CST, now enter: ED-T1::123-01:AA::CST::IS
By use of the above command you are editing the T1 lines into service in their
functional group states, either as di-group or constituent.
 Step 3:
It may be necessary to option the line to make it compatible for its intended
use during operation. Optioning involves setting specific parameters to insure
line operation and use compatibility. Some circuits will require that all
indicated options are set while others may only require limited optioning.
If the circuit you are working with is in service and optioned, it is important to
review the parameters and insure they are correct for your order
specifications. If they meet all requirements ten you may proceed to step 4.
If you had to enter the circuit and edit it into service then it has to be
optioned as outlined below. This would also apply if one or more parameters
needed to be changed to match the individual specifications of the circuitry.

For a DS1/DGR circuit enter:
ED-T1::123-01:AA::DGR:FMT=ESF,LINECDE=B8ZS,GOS=2,ALM=INH,
MODE=FRCD;

FMT
Refers to the formatting on the line

ESF Means “Extended Super Frame” which is a method of formatting the
data structure on the line.

LINECDE Refers to the type of line coding

B8ZS

GOS=2

ALM=INH

MODE=FRCD

For a DS3/CST circuit enter:
Means “Bipolar Eight Zero Substitution (Line Coding)
Designates the Grade of Service
Designates that the alarm will be inhibited.
The mode is forced.
ED-T1-123-01:AA::CST:FMT=ESF,GOS=2,ALM=INH,MODE=FRCD;
The formatting and the line-coding on an individual DS1 or DS3 may also be
optioned as SF/AMI. SF is a format parameter that refers to super frame and
AMI is a linecode parameter that refers to alternate mark inversion.
 Step 4:
Once the status of both circuits has been established and all factors are
present for functionality you are then ready to create the software cross
connection between the two lines.
Enter: ENT-CRS-T1::123-01,345-28:AA;
 Disconnecting a cross connect for a T1:
To disconnect a software cross connection use the following command string.
Enter: DLT-CRS-T1::123-01,345-28:AA;
DLT
This is the command indicating delete
Loop-backs in the Titan 5500 DACS:
There will be specific instances where you will be required to put a loop-back
in place on a circuit. The most common of these will be when you receive an
order that calls for a DSO port to be grown or mapped. These orders usually
have a loop-back set up on the DS1 side of the T1 cross connect that is
associated with the port. This function serves to inhibit the alarms generated
in the DSC DACS equipment by providing it a signal to sync to pending
turning up.
 To set up a standard near-end loop-back:
Enter: OPR-LPBK-T1::123-01:AA::NEND,,,LINE,FRCD;
OPR-LPBK Represents the command to operate loop-back
NEND Indicates the location of the loop-back in this instance it in the nearend side of the T1
 To set up a standard far-end loop-back (Sending C-bits):
Enter: OPR-LPBK-T1::123-01:AA::FEND,,,LINE,FRCD;
FEND Indicates the location of the loop-back in this instance it in the farend side of the T1
 To set up a standard near-end internal loop-back:
Enter: OPR-LPBK-T1::###-##:AA::NEND,,,INTL,FRCD;
INTL
Creates a near-end internal loop-back on the facility
These commands can also be used for the following facilities as well if needed.
The only change required to the command string itself would be to change the
identifying element such as T1 to T3.
NEAR-END:
T1s, T2s, T3s, and EC1s
FAR-END:
T1s and T2s
 To take down any standard loop-back:
Enter: RLS-LPBK-T1::123-01:AA;
RLS
Represents the release command
This command will remain the same for every type of loop back except when
the circuit changes as shown in the list above. Simply adjust the identifier
here, as well from T1 to the specified circuit type and the command will
function as needed.
To verify if a loop back is up on a particular circuit, you will have to retrieve
the T1 and scroll across the message data to find a reference like the
statement below. If there is no loop back on the circuit this phrase will not be
found in the message returned by the DACS.
BRHMALOWBHM 99-10-27 13:26:43
TD COMPLD
“0228-05:DGR:PMAID=PM1D-227-05, TACC=0,IDLECDE=AIS,
OOSCDE=AIS, LINECDE=B8ZS,FMT=ESF,EQLZ=1,GOS=2,ALM=INH,
ALMPF=99,CMDLPBKREQ=NENDLINE,FENDPMTYPE=ANSI403,
DS1ADDR=C,CSUADDR=B,TMG=THRU,FLTRC=NA:PST=IS-NR"
OC3 Cross Connects in the Titan 5500 DACS:
Performing this type of cross connect in the Titan 5500 DACS is basically the
same as a regular cross connect procedure except for slight differences which
pertain to the VT1 circuit. The numbering of this circuit in the DACS requires
the usage of a circuit type identifier. In this case that would be to label the
VT1 circuit as part of its AID. For example VT1 circuit 305-1 will appear as
VT1-305-1. This could also be labeled as VT1-305-1-1. Our current software
edition allows for this variable in the numbering method that is used.
When retrieving a VT1 circuit you must modify the command string and
correctly label the circuit. For instance, your main command might be RTRVCRS-T1 but for it to be a valid request for this type of facility it would have to
be stated as RTRV-CRS-VT1. The circuit itself is also unique to this structure,
as it must also be identified as a VT1 circuit in its AID. The chart below shows
the numbering structure of a VT1 circuit.
Numbering
Option 1
VT1-305-1
VT1-305-2
VT1-305-3
VT1-305-4
VT1-305-5
VT1-305-6
VT1-305-7
VT1-305-8
VT1-305-9
VT1-305-10
VT1-305-11
VT1-305-12
VT1-305-13
VT1-305-14
OR
Numbering
Option 2
VT1-305-1-1
VT1-305-1-2
VT1-305-1-3
VT1-305-1-4
VT1-305-2-1
VT1-305-2-2
VT1-305-2-3
VT1-305-2-4
VT1-305-3-1
VT1-305-3-2
VT1-305-3-3
VT1-305-3-4
VT1-305-4-1
VT1-305-4-2
Numbering
Option 1
VT1-305-15
VT1-305-16
VT1-305-17
VT1-305-18
VT1-305-19
VT1-305-20
VT1-305-21
VT1-305-22
VT1-305-23
VT1-305-24
VT1-305-25
VT1-305-26
VT1-305-27
VT1-305-28
OR
Numbering
Option 2
VT1-305-4-3
VT1-305-4-4
VT1-305-5-1
VT1-305-5-2
VT1-305-5-3
VT1-305-5-4
VT1-305-6-1
VT1-305-6-2
VT1-305-6-3
VT1-305-6-4
VT1-305-7-1
VT1-305-7-2
VT1-305-7-3
VT1-305-7-4
Numbering option 1 is the same as numbering option 2. You can enter a
command using either AID.
Example: RTRV-CRS-VT1::VT1-305-1:AA;
OR
RTRV-CRS-VT1::VT1-305-1-1:AA;
Either entry will return data for the same circuit. The main difference is that
option 2 specifies the type of circuit (VT1)- the shelf number (305)- and the
group count (1-1). The group count refers to the individual numbering of the
VT1 circuit. In this instance, the first one is group 1 of 7 and the second 1 is
the first slot of 4 on this VT1 facility. In basic terms there are 7 VT1 groups
on VT1-305 and each individual group has 4 slots that total 28 circuits.
The other difference between the two numbering options is how they function
in the equipment. Option #1 can only be used for command entry purposes
but Option #2 is used for command entry, system responses and systemgenerated reports. This is very important since all system responses will be
shown using option #2 even if the command entered used option #1.
Entering VT1 to DS1/3 Cross Connects:
 Step1: Retrieve current cross connection status of a single circuit.
RTRV-CRS-VT1::VT1-305-1:AA;

Step 2: Retrieve the current parameter status of the T1 circuit.
RTRV-VT1::VT1-305-1:AA;
 Step 2-A: If the message you receive during your retrieve for parameter status indicates
that the circuit is out of service it will have to be grown using the following commands.
Currently all defaults are the designated parameters for the facility and no additional
optioning would be required for a VT1.
Enter: ENT-VT1::VT1-305-1:AA;
Then enter: ED-VT1::VT1-305-1:AA::::IS;

Step 4: Entering the cross connection for a T1 or T3 to a VT1 facility.
ENT-CRS-T1::123-45,VT1-305-1:AA;
Entering a VT1 to a VT1 cross connect:
ENT-CRS-T1::VT1-307-4,VT1-305-1:AA;
 Disconnecting a cross connect for a T1:
DLT-CRS-T1::123-45,VT1-305-1:AA;
Additional Functions and Commands:
RTRV-COND-T1::T1-096-2:AA;
This command will provide information regarding the immediate status of the Facility in
the DACS Equipment.
BRHMALOWBHM 02-02-04 10:07:56
M TD COMPLD
"0045-03,T1:NA,INHALM,NSA,03-25,04-25-11,NEND,,,\"Alarm Monitoring has been
inhibited (via command)\""
RTRV-ALM-T1::T1-096-2:AA;
This command will inform you of any alarms that are currently present on the Facility in
question. Please NOTE!!! Never use this command and set the Facility to ALL. There are
an extreme amount of individual facilities in the Equipment and this will severely hamper
the ability to perform additional retrievals until the system has CHECKED every facility
for alarms.
BRHMALOWBHM 02-02-04 10:09:26
M TD COMPLD
The above response indicates that no alarms were present on the facility that was
entered.
T3 Speed Growth:
T2’s
1
2
3
Embedded T1
245
(T3)
4
5
6
7
T1’s
1
2
3
4
9
10
11
12
17
18
19
20
25
26
27
28
5
6
7
8
13
14
15
16
21
22
23
24
The Tellabs Titan 5500 uses a
mux element in the equipment
for routing and growth of the
facilities. The basic process is
to break down the larger circuit
carrier into individual mapping
units. A DS1 that rides a DS3
has to have the mux component
grown in the equipment to
enable the 28 T1 channels that
are associated with it. The
musing takes place via the 7
T2’s that must be provisioned
on the T1 port. The equipment
defines this type of embedded
T1 as the T3 port.
This command defines and configures a T3 termination, and optionally T2 and T1
terminations.
The AUTOCST parameter defines the level in which auto provisioning is performed. If
AUTOCST=T2 is specified, then auto provisioning shall only include the constituent T2s
of the T3. If AUTOCST=T1 is specified, then auto provisioning shall include the
constituent T2s and T1s of the T3.
A command to enter a T3, with automatic constituent provisioning selected, shall apply
the following conditions for the T3 level:
· All attributes of the T3 are assigned the values specified on the T3 command line;
otherwise, if no value is specified on the T3 command line for an attribute, the
attribute is assigned the system default value.
A command to enter a T3 termination which includes auto provisioning of the
constituent T2, shall apply the following behaviors to enter the constituent T2s (Behavior
responses related to T2 provisioning are described in ENT-T2):
· Enter the T3 as stated above.
· The PST attribute of the constituent T2s is assigned the value specified on the T3
command line; otherwise, it is assigned to the system default value.
· The ALMPF attribute of the constituent T2s is assigned the value specified on the
T3 command line; otherwise, it is assigned to the system default value.
· The ALM attribute of the constituent T2s is assigned the value specified on the T3
command line; otherwise, it is assigned to the system default value.
A command to enter a T3 termination which includes auto provisioning of the
constituent T1s, shall apply the following behaviors to enter the constituent T1s
(Behavior responses related to T1 provisioning are described in ENT-T1):
· Enter the T3 and constituent T2s as stated above.
· The PST attribute of the constituent T1s are OOS.
· All remaining attributes of the constituent T1s are assigned the system default
values.
ENT-T3::245:CTAG::DGR:AUTOCST=T2,ALM=INH:IS;
(grows the T3 and
all T2’s in one command and provisions them to default status for general parameters
and the alarms in an inhibited state)
ENT-T3::245:CTAG::DGR:AUTOCST=T1,ALM=INH:IS;
(grows the T3, all T2’s
and T1’s in one command and provisions them to default status for general parameters and the
alarms in an inhibited state)
Traditional growth methods require that each component be grown for the prescribed
facility. This takes multiple commands to enter.
EXAMPLE:
ENT-T3::245:CTAG:::ALM=INH:IS;
ENT-T2::245-1&&-7:CTAG:::ALM=INH:IS;
ENT-T1::245-1&&-28:CTAG::CST:FMT=ESF,GOS=2,ALM=INH:IS;
OR………..
ENT-T3::245:CTAG::::IS;
ED-T3::245:CTAG:::ALM=INH,MODE=FRCD:IS;
ENT-T2::245-1&&-7:CTAG::::IS;
ED-T2::245-1&&-7:CTAG:::ALM=INH,MODE=FRCD:IS;
ENT-T1::245-1&&-28:CTAG::CST::IS;
ED-T1::245-1&&-28:CTAG::CST:FMT=ESF,GOS=2,ALM=INH,
MODE=FRCD:IS;
This assumes that everything is grown in a range method which can provision multiple
facilities at once instead of one at a time. It saves time but if the parameter to inhibit
the alarms is not used it will leave multiple units alarming in the equipment.
KEYWORD AND PARAMETER
FIELD
DESCRIPTION
The comma (,) is omitted if keyword and parameter field immediately follow (CST:).
Example: ENT-T3::22:ctag::CST:ALMPF=2,GOS=3:IS;
,XBIT=DS3_x-bit_treatment
specifies the way this termination is to handle yellow signal insertion:
Enter YELLOW if yellow signal insertion is to be enabled in the outgoing DS3 signal, for the duration of a DS3
Red or AIS failure, by the X-bits of the incoming DS3 signal.
Enter FORCE0 if yellow signal insertion is to be disabled by forcing the X-bits of the incoming DS3 signal to
maintain all zeroes.
Enter FORCE1 if yellow signal insertion is to be disabled by forcing the X-bits of the incoming DS3 signal to
maintain all ones.
Enter LOOP if the X-bits of the incoming DS3 signal are to be looped toward the facility.
The system default is YELLOW.
The command default is no change in current parameter status.
,OOSCDE=DS3_oos_code
specifies the code used for the termination when it is out-of-service:
Enter AIS to specify alarm indication signal.
Enter IDLE to specify idle.
Enter ALL-ONES to specify unframed.
Enter ALL-ZEROS to specify no signal.
The system default is AIS.
The command default is no change in current parameter status.
,MAP=DS3_cst_map
specifies the mapping parameter for a DS3 constituent termination:
Enter ASYNC for asynchronous.
Enter INTACT for intact.
The system default is ASYNC.
,ALMPF=alm_profile
specifies the alarm profile:
Enter the appropriate number in the 0, 1-20, or 99 range.
The system default is 99.
To group use &, e.g., 1&4&6. (only for RTRV-ATTR-xxx commands).
NOTE: The grouping feature is not applicable to ED and ENT commands.
,FMT=DS3_format
specifies the framing format used on this termination:
Enter M23 to specify if framing format supports DS1 to DS3 multiplexing via DS2.
Enter CBPAR to specify C-bit parity.
Enter UNF to specify unframed.
The system default is M23.
The command default is no change in current parameter status.
,GOS=grade_of_service
specifies the grade-of-service table:
Enter the appropriate number: 0, 1-20, 97, 98 or 99.
The system default is 99.
The command default is no change in current parameter status.
,AISTYPE=DS3_ais_type
specifies the type of AIS (Alarm Indication Signal) that will be recognized when it is received:
Enter IST1 to specify Framed 1010 (ignore stuffing) and All 1s (Unframed).
Enter SST1 to specify Framed 1010 with stuck stuffing and All 1s (Unframed).
Enter IST to specify Framed 1010 (ignore stuffing).
Enter SST to specify Framed 1010 with stuck stuffing.
The system default is SST.
The command default is no change in current parameter status.
Note: this specification does not affect the AIS which is transmitted when necessary - it is always framed 1010
with stuck stuffing.
,ALM=alarming_enabled
specifies whether facility events are monitored on this termination:
Enter ALW for allow.
Enter INH for inhibit.
The system default is ALW.
,PARITY=DS3_parity_type
specifies the DS3 parity errors as either path or line:
Enter LINE or PATH.
The system default is PATH.
The command default is no change in current parameter status.
,AUTOCST=DS3_autocst
specifies the level at which terminations are addressed:
Enter T3 to specify the T3 termination alone.
Enter T2 to specify the T3 termination and its associated T2 constituents.
Enter T1 to specify the T3 termination and the associated T2 and T1 constituents
A DS3 carrys 28 individual
DS1 circuits. A T1 that “rides”
in a DS3 is called an
Embedded T1. In the Tellabs
DACS each individual T1 has
it’s own specific number.
A DS3 is connected into the
equipment and the individual
DS1’s are divided out into the
DS3 cards in the equipment
shelf.
DS3
1
2
3
4
T1 > 362
D
S
3
C
A
R
D
1
2
3
4
T1 > 363
T1 > 364
25
26
27
28
1
2
3
4
25
26
27
28
DS0 Port
DS0
Level
DACS
1
2
3
4
21
22
23
24
Each one of the individual
channels on a T1 can be
“muxed” down to the DS0
level. This is the most
basic level of service. It is
the “last available drop” of
service that can be derived
from the carrier. These
can be used for voice or
data traffic as optioned
and assigned in the
equipment doing the
“muxing”.
25
26
27
28
A T1 channel is physically wired to the port in the
Digital Access Cross Connect equipment and
supplies the circuit capacity for the DS0’s to be
muxed. Each individual T1 channel has the
capacity to have 24 DS0’s mapped when it is
wired into a port on the supporting equipment.
28 T1s x 24 DS0’s = 672 total available per T1
28 DSs X 28 DS1s = 784 784 T1 CHANNELS X 24 POSSIBLE DS0s = 18816