Programmation Par Commandes AMOS ANG PDF

Siemens AMOs
AMOs
Contents
1 Access to the HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 HiPath 4300/4500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Access via the Customer LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 AMO access via the HiPath 4000 Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.5 Direct AMO access via the customer LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.6 Direct AMO access via the Atlantic LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.7 Direct AMO access via V.24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 Syntax for AMO Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Example of AMO Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2 AMO SYNTAX DETAILS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3 Selecting Important Verbs and Nouns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3 Protection of software features (codeword) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2 Codeword variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3 Codew description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.4 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.5 Generation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.6 Relevant AMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4 Administration Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.1 Switching and Configuration AMOs in the CC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2 BCSU - Configuring Mounting Locations for Modules in the SWU . . . . . . . . . . . . . . . 30
4.3 Functions of the AMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.3.1 ADD-BCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1
EN4401EN00EN_0005
© 2005 Siemens AG
AMOs Siemens
4.3.2 CHANGE-BCSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.3.3 DELETE-BCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3.4 DISPLAY-BCSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3.5 REGENERATE-BCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5 BSSU - Board Switch, Switching Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.1.1 ACTIVATE-BSSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.1.2 DEACTIVATE-BSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.1.3 RESTART-BSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6 UCSU - Unit Configuration of Switching Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.1.1 ADD-UCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.1.2 CHANGE-UCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1.3 DELETE-UCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1.4 DISPLAY-UCSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1.5 REGENERATE-UCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7 USSU - Unit Switch of Switching Unit SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.1.1 ACTIVATE-USSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.1.2 DEACTIVATE-USSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.1.3 DISPLAY-USSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.2 SDSU Status Display of SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.2.1 Example: Displaying the Status of Circuit 1 of a peripheral board . . . . . . . . . 55
8 AMOs in the User Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9 Configuration of a subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
9.1 UP0/E - subscriber. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
9.2 Configuration of an IP-subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10 Deletion of a subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
11 Structure of the DPLN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
11.1 Overview of the CPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
12 WABE - Digit Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
12.1 ADD-WABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
12.2 DISPLAY-WABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
12.3 REGENERATE-WABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
13 COSSU - Classes of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.1 ADD-COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.2 CHANGE-COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
13.3 DELETE-COSSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
13.4 DISPLAY-COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
13.5 REGENERATE-COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
14 TAPRO - Key Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
14.1 CHANGE-TAPRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
14.2 DISPLAY-TAPRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
14.3 REGENERATE-TAPRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
2
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens AMOs
15 ZIEL - Destination Addresses for Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

15.1 ADD-ZIEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
15.2 DISPLAY-ZIEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
15.3 REGENERATE-ZIEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
16 ACTDA - Activation of User Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
16.1 ADD-ACTDA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
16.2 DELETE-ACTDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
16.3 DISPLAY-ACTDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
16.4 REGENERATE-ACTDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
17 SDAT - Administration of Individual Subscriber
Attributes and General Subscriber Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
17.1 CHANGE-SDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
17.1.1 Changing Attributes / Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
17.1.2 Changing General Subscriber Data (Branch DATA) . . . . . . . . . . . . . . . . . . . 96
17.1.3 Changing Subscriber Data (Branch DATA1). . . . . . . . . . . . . . . . . . . . . . . . . 96
17.2 DELETE-SDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
17.3 DISPLAY-SDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
17.4 REGENERATE-SDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
18 PERSI - Personal Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
18.1 ADD-PERSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
18.2 CHANGE-PERSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
18.3 DELETE-PERSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
18.4 DISPLAY-PERSI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
18.5 REGENERATE-PERSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
3
EN4401EN00EN_0005
© 2005 Siemens AG
AMOs Siemens
4
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Access to the HiPath 4000
1 Access to the HiPath 4000

With HiPath 4000 assistant a new service platform is created which offers also many new ser-
vice tools besides an extended system access. The new platform is Web-based and automates
many events. With the UW7 platform it is also possible to use existing network wide standards
such as Telnet and FTP. Through it an almost complete integration into the data world is possi-
ble.
1.1 HiPath 4300/4500
Common Service Access for all Products

HTS via VPN Server
External access is achieved via a virtual pri-
vate network (VPN). An explicit VPN ad-
Service Technician dress, starting with "10", is given to every
system and server.
TAP
MTS
ISDN
PPP-Link
SNS-Server
for HTS
WAML Customer-LAN
SNS-Server
Control
8
TAP V24 to RMX RMX
9
FAMOS
SCSI
10
Terminal V24 or UNIX
11 SL200
192.0.2.222 PPP-Link 221
using Script: Siemens.CPPP .5
.3 .4
Atlantic LAN 192.0.2.0
.6 SNS-Server
Access to Applications via Port-Server

As a rule the SL200 receives an IP address from the customer
LAN. On first installation it has the IP address 192.1.2.5.
5
EN4401EN00EN_0005
© 2005 Siemens AG
Access to the HiPath 4000 Siemens
1.2 HiPath 4000
Common Service Access for all Products

HTS via VPN Server
External access is achieved via a virtual pri-
vate network (VPN). An explicit VPN ad-
Service Technician dress, starting with "10", is given to every
system and server.
TAP
MTS
ISDN
PPP-Link
SNS-Server
for HTS
Customer-LAN
WAML
SNS-Server
Steuerung DSCXL
TAP Atlantik/Service LAN
10
Customer LAN
8/11
.5
.3 .4
Atlantic LAN 192.0.2.0
As a rule the SL200 receives an IP address from the customer

LAN. On first installation it has the IP address 192.1.2.5.
6
EN4401EN00EN_0005
© 2005 Siemens AG
1.3 Access via the Customer LAN

Interfaces to use:
● SL200 modul of the DSCX processor respectively DPC5 processor of the HiPath 4300/
4500 - upper connector.
● Customer-LAN interface of the DSCXL processor of the HiPath 4000.
On first installation it has the IP address 192.1.2.5. The SL200 respectively the customer LAN
interface will be reconfigured to the customer IP address as follows.
Base Administration --> Unix Base Administration --> LAN Configuration --> LAN Cards
Information about the IP settings you will get from the LAN administrator.
Address: unique customer IP address
Netmask: depends on the IP class of the LAN card, e.g. for class C: 255.255.255.0
Broadcast: depends on the IP address of the LAN card. For the LAN card address 1.30.31.5
the Broadcast address is 1.30.31.255
It is necessary to restart the UW7 server after changing IP parameters.
7
EN4401EN00EN_0005
© 2005 Siemens AG
1.4 AMO access via the HiPath 4000 Assistant

Is the Customer LAN interface configured the system can be administrated via the Assistant
4000 or via AMOs with the Expert Access. Therefore the programm HiPath 4000 Expert Access
must be installed.
8
EN4401EN00EN_0005
© 2005 Siemens AG
1.5 Direct AMO access via the customer LAN

Therefore the programm HiPath 4000 Expert Access must be installed. The window “Connect”
provides the configuration of profiles for the access via V.24 respectively LAN .
Interfaces to use:
● SL200 modul of the DSCX processor respectively DPC5 processor of the HiPath 4300/
4500 - upper connector.
● Customer LAN interface of the DSCXL processor of the HiPath 4000.
V.24 LAN
9
EN4401EN00EN_0005
© 2005 Siemens AG
Profil for the AMO access via the customer LAN
10
EN4401EN00EN_0005
© 2005 Siemens AG
1.6 Direct AMO access via the Atlantic LAN

Interfaces to use:
● Atlantic LAN access via the backplane of the HiPath 4300.
● Atlantic LAN access via the HUBC of the HiPath 4500.
● Atlantic LAN interface of the DSCXL processor of the HiPath 4000.
● Atlantic LAN access via the SF2X8
Profil for the AMO access via thev Atlantic LAN:
11
EN4401EN00EN_0005
© 2005 Siemens AG
1.7 Direct AMO access via V.24

Interfaces to use:
● V.24-1 and V.24-2 (line 8 and line 9) with the HiPath 4300/4500 (DSCX respectively DPC5).
Profil for the AMO access via V.24 (line 8):
12
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: Syntax for AMO Input
2 Syntax for AMO Input

COMMAND CODE: PARAMETER, PARAMETER ....;
ACTIVITY - FUNCTIONS PARAMETER NAME =PARAMETER VALUE

VERB - NOUN or
ADD - AUN POSITION-DEPENDENT PARAMETER (VALUE)
( ) EXPLANATORY TEXT PASSAGES

[ ] PARAMETER NAME and PARAMETER VALUE may be entered.
<> Name of PARAMETER VALUE, all possible values are explained
separately..
{ } Entry of at least one PARAMETER, rest optional
: Separating COMMAND CODE and PARAMETER
- Separating ACTIVITY and FUNCTIONS OF THE COMMAND CODE
; END of AMO INPUT
PARAMETER NAME = PARAMETER VALUE

One of the given PARAMETER VALUES must be assigned to the
PARAMETER NAME.
PARAMETER NAME = <PARAMETER VALUE>

An individual value, a string of individual values, or a group of individual values
must be allocated to the PARAMETER NAME.
[PARAMETER NAME = <PARAMETER VALUE>]

Optional input of PARAMETER NAME, PARAMETER VALUE.
& & STRING of INDIVIDUAL VALUES

&& GROUP of INDIVIDUAL VALUES
I OR GATING - one of the given parameters is entered up to the semicolon as
an alternative.
<number> PARAMETER consists of DECIMAL NUMBER(S)
<param> PARAMETER VALUE consists of LETTERS A...Z, DIGITS 0...9
<string> PARAMETER VALUE consists of CHARACTERS (all except ', ”)
<key-num> PARAMETER VALUE consists of CHARACTERS 0...9, A...D, *, #
<a-b-c...> PARAMETER VALUE consists of PARAMETER ARGUMENTS
<identifier> PARAMETER VALUE consists of CHARACTERS (A...Z, 0...9)
1. character is a letter
<name> = <param>
13
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: Syntax for AMO Input Siemens
2.1 Example of AMO Input

Procedure Overview
Command Code Parameter
DISPLAY-PERSI TYPE =SYS;
I TYPE = COPIN, [COPIN=<number>] ;
I TYPE = MODULO ;
I TYPE = NAME, [STNO=<number>] ;
I TYPE = PIN, [PIN=<string>]
,[PINTYPE=<number>] ;
I TYPE = STN, [STNO=<number>],
PINTYPE=<string>] ;
I TYPE = CCMS,
[CCMSCD=<keynum>],[DPLN=<number>],[STNO
=<number>] ;
Command Code Parameter

DISPLAY-SCSU [STNO]=<number>,
e.g.ITYPE =COS, COSNO=<number>;
14
EN4401EN00EN_0005
© 2005 Siemens AG
2.2 AMO SYNTAX DETAILS

An AMO input is made by entering a string of characters consisting of:
a verb such as ”DISPLAY” or ”ADD”
a dash (used as a separator) ”-”
and the AMO name, e.g.”DATE”
Example
DISPLAY-DATE: Following this entry the AMO DATE would then start.
Not all the characters of the verb are required by the system; a short form can be used,
e.g.
DIS for Display
DEL for DELETE
Once the AMO is started it will ask for certain parameters to qualify the task desired, e.g.
DIPSP-SCSU:
All
ATTR
CONN
COS
HW
LCOSD
LCOSV
Entry Modes
– POSITION-ORIENTATED ENTRY
(VERB-NOUN:value1,value2,,,value5,value n)
– KEYWORD-ORIENTATED ENTRY
(VERB-NOUN:name3=value3,name1=value1,name n=value n)
– Prompting (input request)
The POSITION-orientated entry consists of a sequence of parameters, each separated
by a comma. If a parameter is not to be assigned a value, the comma is still entered to
maintain the sequence, i.e. in the example above, value 3 and value 4 are represented by
commas.
With the KEYWORD-orientated entry the parameters to be entered are identified by en-
tering their respective keyword first, e.g. STNO=2104.
Since each parameter is attached to an identifying keyword, the sequence on the input line
is not important; any order is possible.
15
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: Syntax for AMO Input Siemens
The colon ”:” is used to separate the AMO command code from the parameter block. The
semicolon ”;” is the command line termination character. When it is used, values for any
optional parameters which may be entered in the command line are not requested by the
system.
To enter the command line CTRL +C or the RETURN key ( ) is used depending on the
type of terminal.
Blanks between the different parts of the input (verb, hyphen, colon, parameter, equals sign,
comma, and semi-colon) may be used for subdividing the input.
The AMO will ask for Parameter Values if not all of the mandatory parameters have
been supplied with values as yet.
If you input a ’?’, the system will display all of the possible parameter values, and then
prompt for an entry.
A mixture of Position- and keyword-oriented inputs is not possible.
Before the first input with the AMO a system LOGON (CTRL + T) must be made.
16
EN4401EN00EN_0005
© 2005 Siemens AG
2.3 Selecting Important Verbs and Nouns

The maximum number of inputs for the AMO for the verb (action)
VERB - NOUN
ADD - PERSI
CHAnge - PERSI
DISplay - PERSI
DELete - PERSI
REGenerate - PERSI
Test - APS
Copy - APS
EXEC - UPDAT
STArt - INFO
STOP - BELIN
DUMP - APS
COLLECT - SELS
ACTivate - DSSU
DEACTivate - DSSU
SWITCH - DSSM
● AMO - code explained in the BCSU example
B C S U
B board C configuration SU switching unit

(console) SM server module
S subscriber S switch/subscriber VM voicemail module
L line D display
U unit
D device
C cabinet
T trunk
A attendant
17
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: Protection of software features (codeword) Siemens
3 Protection of software features (codeword)
3.1 Feature description

Features are sold in feature packages. Each package is allocated a marketing value. The fea-
ture quantities purchased by a customer are encrypted as an alphanumeric "codeword."
The new hardware, HiPath 4000 V2, features a SIM card on the DSCXL board (ADP). The don-
gle used for existing hardware is upwards compatible. However, if the system is upgraded to
Hipath 4000 V2.0 then a new codeword has to be installed.
New hardware: Old hardware:

SIM card on the DSCXL board (ADP) Dongle for existing systems
The dongle or the SIM card and the codeword "tell" the system which feature packages and
quantities were purchased by the customer. When the system is configured, a special plausi-
bility check is used to ensure that the configuration data corresponds to the purchased features
and quantities.
18
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: Protection of software features (codeword)
PNE
ComScendo CC-AP for AP Emergency
Remote Survivability Cordless E
Voice com-
Entry Agent
pression IP
CODEWORD
Protection of software features
3.2 Codeword variants
In HiPath 4000 V2.0 and later, the CODEWORD will feature four variants:
1. Normal mode:
This is the approved operating mode as implemented in HiPath 1.0. In normal mode, a
codeword and licenses are requested for all relevant licenses in the database.
2. Trial mode:
This feature introduces a time-limited trial mode. When you activate trial mode, you can
skip the license restrictions that are temporarily displayed. During this time, the AMOs work
as if unrestricted licenses were available except that an advisory message is sent to the
users if license restriction violations occur.
3. Emergency mode:
The system activates the Emergency mode, in case of special situations.
Special situations are:
Validity of the Codeword is expired;
Dongle resp. SIM card is missing;
Codeword is missing;
19
EN4401EN00EN_0005
© 2005 Siemens AG
Dongle resp. SIM card does not match to Codeword;

In the Emergency mode the AMO execution is blocked in the SWU. The only AMOs that
can be executed are the AMO CODEW / DATE.
4. Escalated Emergency mode:
The feature triggers an additional system operation restriction (it blocks the FEASU fea-
ture) when the system is in escalation mode for an extended period of time. This restriction
is known as escalation of the Emergency mode.
CODEW variants with dongle in HiPath 4000 V2.0

The HiPath 4000 V1.0 operating mode is maintained if the old hardware is used with a dongle.
However, you must download a new codeword if you migrate to HiPath 4000 V2.0.
TYPE Description Dongle Sim Card

TYPE 1 (Customer) standard: 2 x Test mode each for 30 days X X
( then a new Codeword is required)
TYPE 2 (Special) Via LMT (Licence Mangement Tool) with a time X X
limit of 60 days or an agreed time limit
Via LMT(Licence Management Tool) without a X X
time limit
● In a network the network codeword from the Hipath 4000 Manager (LMT) is used.
The original Codeword must be added previously in the system.
The Network codeword then overwites the Codeword on a daily basis. If this does not hap-
pen then a 60 day test mode begins.
● The 30 Day Service-Dongle will no longer be given in Hipath4000 V2.0.
● The Type 2 codeword will only be given in special cases.(applied for as an extra).
● The creation date is coded in the Codeword and is stored in the database, when the Code-
word is added in the system. The possibility to add an older Codeword is blocked in this
way.
20
EN4401EN00EN_0005
© 2005 Siemens AG
3.3 Codew description
Unit Description AMOs Parameter

COMSCENDO Counting/marketing ACSU ACTYPE=AC4/ACW2Q/ACW-
per configured B channel/ana- MQ
log channel to: BCSU TYPE=SIGNOFF
– station (optiset = 1 B chan- RCSU RECAPL=ACDR/ACDMUS/
nel; optiset E or optiPoint 500 HMUSIC
... with adapter = 2 B chan-
nels; optiip = 1 B channel, but SBCSU DVCFIG=
ANAFAX/ANADTE/ANADEV/
max. 2 B channels per Up0E)
FAX/DTE/OPTIP500/OP-
or attendant console
TISET/S0PP/S2PP/SET600/
OPTIIP
SCSU DVCFIG=ANATE/ANATECM/
AUXDIGI
SSC TYPE=GENANS/MSGR/EX-
TANN/CC/VMXMWI
SBCSU ART=OPTIERW
– Trunk or tie TACSU DEVTYPE=TC/TC1/TC2/NW/
(including ATM Networking) TT/TT1/TT2/TT3/TT4
TDCSU DEV=S0COD/S0CONN/
S1COD/S1CONN/S1PVC/
S1SVC/LAN/S1PVCCO/
S2COD/S2CONN/S2PVC/
S2SVC/S2PVCCO/VCCOD/
VCCONN/HG3550/CDG-
CONN/CDGCOD/30/ATMS-
VC/ATMPVC3/ATMPVC7/
ATMPVC15/ATMPVC23/
ATMPVC2X/ATMPVC30/
ATMPVCCO
TSCSU DEV=CC/CCM/ANS/RA/RAS/
DICT/SPKR/DOOR
CORDLESS E Counting/marketing of the acti- SBCSU DVCFIG=BASE
vation license per B channel (for
example SLC16 to base station)
irrespective of the operating
software
21
EN4401EN00EN_0005
© 2005 Siemens AG
Unit Description AMOs Parameter

PNE Counting/marketing per VPN B TDCSU DEV=S2CONN
channel configured from/to the
board with PNEDIUS2 line type
(use the AMO BGDAT to check
the line type of a board)
HIPATH PRO- Counting/marketing per active AGENT AGTID=<number>
CENTER EN- (logged in) agent
TRY AGENT
HIPATH AP Counting the IPDA survivability APRT CONF=ROUTER/AP
REMOTE remote shelves for connections
SURVIVABILITY over ISDN (ID9206)
(AMO SIPCO parameter SURV-
NET)
CC-AP FOR Counting/marketing per CC con- APESU DATA=CCAP
AP EMERGEN- figured for AP Emergency
CY
3.4 Service information

● The counters bear no relationship to the feature dimensioning values administered with the
AMO DIMSU.
● For the purposes of software feature protection, "ComScendo" is the equivalent of "station"
for the following components:
– Optiset E
– optiPoint 500 / optiPoint 400 / optiPoint 410
– ANATE
– ANATECM
– AUXDIGI
– Signed off TSI instead of signed off station
– PP (all S0/S2)
– FBUS (all call numbers)
● The dongle or the SIM card is immediately activated on startup.
● The validity of a codeword may be limited to a specific period. It is calculated in days from
the creation date.
22
EN4401EN00EN_0005
© 2005 Siemens AG
● The expiry date is shown after each LOGON command or after the initial ADD command.
You can also check the date with the DISPLAY-CODEW command.
● A new codeword is needed every time the purchased quantity is expanded.
(Except "HIPATH AP VOICE COMPRESSION IP" where only the coding is dynamically
changed (from G.729 to G.711) when the limit is reached.)
The purchased quantity can be temporarily expanded in trial mode (see Section 1.2).
● An installed codeword only can be replaced by a new one. The creation date is saved in
the codeword; the serial number is used for information purposes only.
● The codeword can be changed with the codeword tool.
● The hardware ID and codeword must match.
● In order to enter a codeword the date of the system must be valid.
● In the event of contractual violation, the user interface is disabled and you are prevented
from starting any more SWU AMOs (for configuration).
● If the system prevents access although the codeword and dongle are valid, you can acti-
vate the dongle with the following actions: unplug/plug in the dongle, enable line8 or per-
form an A1 soft restart.
● Further information on the AMO CODEW can be found in the AMO description in the
service manual.
3.5 Generation (example)

● Add a codeword (dongle or SIM card must be inserted):
ADD-CODEW:CODEW1=
W1RAZWX6HPK8HS5G39TKV6X9MKVAM9ENERJTVTZBDX34KFNHRUTP4GU1EC132N93,
CODEW2=LJJ9MKK381DASTYEZNNU67366HMWAM33VVKKRKG7UHTDUGFWJN2PBBREGX;
● Display counters for purchased quantities / configured quantities:
23
EN4401EN00EN_0005
© 2005 Siemens AG
1. Customer Dongle / SIM (TYPE 1 - Codeword)
DISPLAY-CODEW;
H500: AMO CODEW STARDED
SALES UNIT COUNTERS

===================
CODEWORD: AFTKSB3CJYN4LKZN7GNWZH8TXH63M29A5GA2L2JN261LGKEA8CPHLZV5UGKHVPHP
XGRZDWDF83BG6BLE2U6LSP8GYS8VY5NADW88BUAE6RA58HXMD2N99TJSC9
VERSION : H205
SERIAL NUMBER: 7
HARDWARE ID : C6EB8F3B
ENTRY DATE : 22.02.2004
TRIAL MODE : NOT ACTIVATED
CONFIRMATION : 3706
+---------------------------------------------+-------+-------+-------+-------+
| | | | | |
| UNIT | CON- | USED | FREE |BLOCKED|
| | TRACT | | | |
+---------------------------------------------+-------+-------+-------+-------+
| COMSCENDO | 976 | 913 | 63 | |
| CORDLESS E | 0 | 0 | 0 | |
| PNE | 0 | 0 | 0 | |
| HIPATH PROCENTER ENTRY AGENT | 0 | 0 | 0 | |
| SIGNALING SURVIVABILITY | 0 | 0 | 0 | |
| CC-AP FOR AP EMERGENCY | 0 | 0 | 0 | |
+---------------------------------------------+-------+-------+-------+-------+
H07: THE TEST MODE IS AVAILABLE (ANOTHER) 2 TIMES.
AMO-CODEW-111 CODEWORD FOR ADMINISTRATION LOCK IN SWU

DISPLAY COMPLETED;
24
EN4401EN00EN_0005
© 2005 Siemens AG
1. Dongle / SIM with TYPE 2 - Codeword
DISPLAY-CODEW;
DISPLAY-CODEW;
H500: AMO CODEW STARTED
SALES UNIT COUNTERS

===================
CODEWORD: 3SK2N24LR9RF4G9919DZL3GN8C8SVWTN7RX7BWNBCTLTZPGMZN9FBXP97RRFTT72
R283HCUX6LSJXW5YD147WGWTV9FXD2CZBSWN7RY63VL9R7ASMWJ546YM7R
VERSION : H205
SERIAL NUMBER: 0
HARDWARE ID : 7ED439FB
ENTRY DATE : 07.01.2004
VALID UNTIL : 17.12.2005
CONFIRMATION : 0
+---------------------------------------------+-------+-------+-------+-------+
| | | | | |
| | TRACT | | | |
+---------------------------------------------+-------+-------+-------+-------+
| COMSCENDO | | 110 | | |
| CORDLESS E | | 0 | | |
| PNE | | 0 | | |
| HIPATH PROCENTER ENTRY AGENT | | 0 | | |
| SIGNALING SURVIVABILITY | | 0 | | |
| CC-AP FOR AP EMERGENCY | | 0 | | |
+---------------------------------------------+-------+-------+-------+-------+
H12: CURRENT CODEWORD IS A TYPE 2 CODEWORD.

DISPLAY COMPLETED;
25
EN4401EN00EN_0005
© 2005 Siemens AG
Trial mode
The purchased quantity can be temporarily expanded with trial mode.
Trial mode is activated with CHANGE-CODEW. Utilization is not unlimited (maximum number
specified in codeword, generally 2) and has a maximum utilization time (generally 30 days).
SWU administration is not disabled even if license violation is shown in trial mode ("!!!!!" in the
"FREE" column). A mark that can be displaced with the AMO SDSU is applied to elements that
exceed the license limit (stations, trunks, etc.). The number of units marked is also displayed in
the AMO CODEW.
Trial mode is automatically terminated if not manually deactivated within the maximum time lim-
it. When this happens, marked elements are disabled for security reasons and can only be en-
abled if an appropriate codeword is set up.
No elements are marked or disabled for the features HIPATH PROCENTER ENTRY AGENT
and HIPATH AP VOICE COMPRESSION IP. However, when trial mode ends, no agents above
and beyond the license limits can log on and compressed connections cannot be set up.
Trial mode does not apply to the features HIPATH AP REMOTE SURVIVABILITY and CC-AP
FOR AP EMERGENCY. The codeword’s license limit cannot be exceeded here.
● Activate trial mode:
CHANGE-CODEW:TRIAL=YES;
....(activated after consultation)
● Administration above and beyond the quantities purchased:

ADD-SCSU:STNO=4711,DVCFIG=ANATE;
26
EN4401EN00EN_0005
© 2005 Siemens AG
● Display codeword the test mode is expired:

DISPLAY-CODEW;
DISP-CODEW;
H500: AMO CODEW STARTED
SALES UNIT COUNTERS

===================
CODEWORD: 3SK2N24LR9RF4G9919DZL3GN8C8SVWTN7RX7BWNBCTLTZPGMZN9FBXP97RRFTT72
R283HCUX6LSJXW5YD147WGWTV9FXD2CZBSWN7RY63VL9R7ASMWJ546YM7R
VERSION : H205
SERIAL NUMBER: 0
HARDWARE ID : 7ED439FB
ENTRY DATE : 18.12.2003
VALID UNTIL : 17.12.2004
CONFIRMATION : 0
+---------------------------------------------+-------+-------+-------+-------+
| | | | | |
| | TRACT | | | |
+---------------------------------------------+-------+-------+-------+-------+
| COMSCENDO | 110 | 110 | !!!!! | 1 |
| CORDLESS E | | 0 | | |
| PNE | | 0 | | |
| HIPATH PROCENTER ENTRY AGENT | | 0 | | |
| SIGNALING SURVIVABILITY | | 0 | | |
| CC-AP FOR AP EMERGENCY | | 0 | | |
+---------------------------------------------+-------+-------+-------+-------+
H12: THE TEST MODE IS AVAILABLE (ANOTHER) ONCE.

DISPLAY COMPLETED;
27
EN4401EN00EN_0005
© 2005 Siemens AG
DISPLAY-SDSU:STATUS=LICMARK,TYPE=PEN,LEVEL=PER3;
....(a component is marked if it was installed with the purchased

quantities configured and the system is being operated in trial mode.)
DISPLAY-SDSU:STATUS=LICBLOCK,TYPE=PEN,LEVEL=PER3;
....(specifies the stations disabled on account of license violation
when the trial mode expired.)
3.6 Relevant AMO

AMO Parameter Sprache/ Beschreibung/ Description
Language
EINR-CODEW CODEW1 d Erster Teil des Codewortes
CODEW2 d Zweiter Teil des Codewortes
ADD-CODEW CODEW1 e First part of codeword
CODEW2 e Second part of codeword
AE-CODEW TESTMOD d Testmodus ein/ausschalten
CHANGE-CODEW TRIAL e Activate/deactivate trial mode
AB-SDSU LICMARK d Markierte Lizenz (im Testmodus)
LICBLOCK d Gesperrte Lizenez (Testmodus abge-
laufen)
DISP-SDSU LICMARK e Marked License (in testmode)
LICBLOCK e Blocked License (testmode expired)
28
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: Administration Software
4 Administration Software
4.1 Switching and Configuration AMOs in the CC
LTG and LTU SLOT CIRCUIT

Unit Board Device
Configure: SCSU/SBCSU
add ACSU
change UCSU BCSU SSC
delete TACSU/TDCSU
TSCSU
Switch:
activate USSU BSSU DSSU
deactivate
display SCSU/SBCSU
brief UCSU BCSU ACSU
information SSC
TACSU/TDCSU
TSCSU
display SDSU (STATUS DISPLAY)
status
information Boards PERI1
Circuits PERI2
Devices PERI3
29
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: Administration Software Siemens
4.2 BCSU - Configuring Mounting Locations for Modules in the SWU
This AMO is used to configure peripheral modules, ringing current generator modules, and
SIUs in the LTU.
The module is entered in the SWU database (reference configuration) and, if the correct
module is plugged in, loaded and put into service.
4.3 Functions of the AMO
• ADD-BCSU : Equip modules in the reference configuration

• CHANGE-BCSU : Change modules in the reference configuration
• DELETE-BCSU : Remove modules from the reference configuration
• DISPLAY-BCSU : Interrogate the modules
• REGENERATE-BCSU : Regenerate the modules
4.3.1 ADD-BCSU
Assign the desired module type.
The LTU in which the module is to be configured must already be assigned. (AMO UCSU).
Caused by feature IPDA there are two different kind of LTUs from now on. The range for tradi-
tional LTUs in HHS (Hicom Host System) are from 1 to HW max. value which depends on the
particular platform - and AP shelves (Access Points). The range for these AP shelves starts
generally from 17 and goes up to 99.
During the load of a HHS shelf (Shelf Broadcast) no module can be configured in that shelf.
The AMO is canceled, producing an error message in case a configuration is attempted in that
state.
Assigning a SIU:
Assigning a SIU requires the actions as follows:
a) Manually blocking of LTU shelf (AMO USSU)
b) assigning a SIU
c) Putting the LTU shelf in service
30
EN4401EN00EN_0005
© 2005 Siemens AG
Assigning an IP gateway (STMI board for IPDA usage):

Feature IPDA needs a gateway supporting the payload connections to the AP shelves
(connected via an IP link). The new STMI board will be used for this purpose.
To be able to build up payload connections to the AP shelves and for reasons of performance
distribution the STMI board needs some additional configurations. For this reason, the following
parameters are used:
● Parameter IPADDR:
Address from the SL net table. This table must previously have been configured by means
of AMO-SIPCO.
● Parameter BCHLCNT:
Is also used to control performance distribution. Via this parameter the amount of usable b-
channels can be configured for each STMI board.
4.3.2 CHANGE-BCSU
Modification of module data.

It is only possible to change code numbers of modules within the same module-line-type (e.g.
SLMA).
Exception: The change of some boards with newer HW modules is possible even though the
module-line-type is different and is handled AMO internally (e.g. STMD<->STMD2, SLMS<-
>SLMS2, DIUS2<->DIUN2,...).
If the module is not already blocked, the AMO blocks it. After the change is carried out, the mod-
ule is put back into service.
Examples
1. Change the SLMA module with the code number Q2041-X and the parameters LTG=1,
LTU=1, SLOT=31 to an SLMA module with the code number Q2057-X100.
Input:
CHANGE-BCSU:PARTNO,1,1,31,,"Q2057-X100";
31
EN4401EN00EN_0005
© 2005 Siemens AG
2. Change all SLMA modules of LTG 1 with the code number Q2041-X to SLMA modules with
the code number Q2057-X100.
Input:
CHANGE-BCSU:PARTNO,1,,,"Q2041-X","Q2057-X100";
Output:
H01: BG 1.1. 25 CHANGED - IN SERVICE
H01: BG 1.1. 31 CHANGED - OUT OF SERVICE (NPR)
4.3.3 DELETE-BCSU
Example
1. Remove the RG module having the parameters LTG=1, LTU=1 and SLOT=19.
Input:
DELETE-BCSU:RG,1,1,19;
4.3.4 DISPLAY-BCSU
The type of output is controlled exclusively by parameter TYPE.
● Interrogate the configuration of an LTU with modules in the following format:
– a statistics
– a table
– a table of modules with variable modes
● Interrogate the operating mode RG, ACGEN, SIU- and DIUC- modules.
● Interrogate the connection status of pens.
● Interrogate base stations.
● Interrogate source groups (see also AMO-UCSU).
32
EN4401EN00EN_0005
© 2005 Siemens AG
Examples
1. Generate statistics of the reference configuration of the entire system. Parameters (LTG,
LTU, SLOT,CFIG and PARTNO) are assigned default values.
Input:
DISPLAY-BCSU:STAT;
Output:
TOTAL OF THE REFERENCE CONFIGURATION
PARTNO FID TYPE | NUMBER

-------------------------+---------------------------------------------------
Q2057-X SLMA | 6 => 96 LINE CIRCUITS / PORTS
Q2058-X RG | 1 => 0 LINE CIRCUITS / PORTS
Q2052-X SLMB | 5 => 40 LINE CIRCUITS / PORTS
Q2027-X TMX21 | 6 => 12 LINE CIRCUITS / PORTS
Q2032-X TMBP | 2 => 8 LINE CIRCUITS / PORTS
Q2033-X TMBC | 2 => 8 LINE CIRCUITS / PORTS
Q2025-X200 TMBD | 11 => 44 LINE CIRCUITS / PORTS
Q2248-X LTUCE | 6
Q2014-X TMOM | 4 => 8 LINE CIRCUITS / PORTS
Q2013-X TMBM | 2 => 4 LINE CIRCUITS / PORTS
Q2233-X 2 SIUX | 1 => 8 LINE CIRCUITS / PORTS
Q2065-X1 TMAG | 1 => 2 LINE CIRCUITS / PORTS
Q2066-X1 TMAU | 4 => 12 LINE CIRCUITS / PORTS
Q2064-X TLMR | 2 => 4 LINE CIRCUITS / PORTS
Q2067-X100 TMASF | 1 => 4 LINE CIRCUITS / PORTS
Q2064-X100 TMLR | 2 => 4 LINE CIRCUITS / PORTS
2. List the data for all modules in LTG 1 / LTU 3.

Input:
DISPLAY-BCSU:TBL,1,3;
Output:
ADDRESS : LTG 1 LTU 3 SOURCE GROUP 1
-----+-----------+---------+---+---+-+------------+-----+--------+------------+
| ASSIGNED | MODULE |FCT|HWY| | INSERTED | | | MODULE |
PEN | MODULE | TYPE |ID |BDL| | MODULE |STATE| HW-INFO| STATUS |
-----+-----------+---------+---+---+-+------------+-----+--------+------------+
19 | Q7065-X APPS |*| AVAILABLE | | | NPR |
25 | Q2117-X SLMS A |*| | | | NPR |
31 | AVAILABLE | | AVAILABLE | | | |
43 | Q2303-X STMI 1 A |*| | | | NPR |
+-----------------------------+-+------------+-----+--------+------------+
| IP ADDRESS : 198. 16. 16. 63 BCHLCNT : 20 |
33
EN4401EN00EN_0005
© 2005 Siemens AG
+-----------------------------+-+------------+-----+--------+------------+
61 | Q2303-X STMI 1 A |*| | | | NPR |
+-----------------------------+-+------------+-----+--------+------------+
| IP ADDRESS : 198. 16. 16. 64 BCHLCNT : 30 |
+-----------------------------+-+------------+-----+--------+------------+
73 | Q2248-X LTUCE | | Q2248-X | 1 | -A2 - | READY |
79 | Q2144-X SLMO A | | Q2144-X | 1 | -D1 - | READY |
85 | Q2158-X SLMO24 1 A |*| | | | NPR |
91 | Q2115-X SLMU16 A | | Q2115-X | 1 | C812-G | READY |
97 | Q2150-X SLMB A | | Q2150-X | 1 | C360-L | READY |
103 | Q2150-X SLMB A |*| | | | NPR |
109 | Q2141-X SLMA A | | Q2141-X | 1 | B008-D | READY |
115 | Q2025-X300 TMBD A |*| | | | NPR |
121 | Q2121-X TMBCT A |*| | | | NPR |
If there is an inconsistency between reference and actual configuration, the identifier ’*’ is
entered.
Only one status is output for the dependability and AM module status, which may consist of a
combination of states.
Possible output : NPR not present

MAN_AMO blocked via AMO
MAN_KEY blocked via key
DEFECT blocked due to module fault
WBT incorrect module type
UNACH hierarchically blocked
UNACA blocked due to interrelationship
READY in operation
3. List the data for all modules in LTG 1 / AP shelf 32 (19" shelf).
Input:
DISPLAY-BCSU:TBL,1,32;
Output:
ADDRESS : LTG 1 LTU 32 SOURCE GROUP 6
-----+-----------+---------+---+---+-+------------+-----+--------+------------+
| ASSIGNED | MODULE |FCT|HWY| | INSERTED | | | MODULE |
PEN | MODULE | TYPE |ID |BDL| | MODULE |STATE| HW-INFO| STATUS |
-----+-----------+---------+---+---+-+------------+-----+--------+------------+
1 | AVAILABLE | | AVAILABLE | | | NPR |
34
EN4401EN00EN_0005
© 2005 Siemens AG
2 | Q2117-X SLMS A |*| | | | NPR |

4 | Q2302-X NCUI 1 | | Q2302-X | 1 | -A2 - | READY |
9 | Q2158-X SLMO24 1 A |*| | | | NPR |
10 | Q2115-X SLMU16 A | | Q2115-X | 1 | C812-G | READY |
11 | Q2150-X SLMB A | | Q2150-X | 1 | C360-L | READY |
12 | Q2150-X SLMB A |*| | | | NPR |
4.3.5 REGENERATE-BCSU
For program technical reasons configured base stations will be regenerated before all regular
boards.
Example
Regenerate all modules in the system.
Input:
REGENERATE-BCSU:;
Output:
ADD-BCSU:PER,1,1,61,"Q2144-X ",0,0,,NO,300,700,300,A;
ADD-BCSU:PER,1,1,67,"Q2158-X ",1,0,,NO,300,700,300,A;
ADD-BCSU:PER,1,1,73,"Q2115-X ",0,0,,NO,,,,A;
ADD-BCSU:PER,1,1,79&&85,"Q2150-X ",0,0,,,,,,A;
ADD-BCSU:PER,1,1,91,"Q2141-X ",0,0,,,,,,A;
ADD-BCSU:PER,1,1,97,"Q2025-X300",0,0,,,,,,A;
ADD-BCSU:PER,1,1,103,"Q2121-X ",0,0,,,,,,A;
ADD-BCSU:PER,1,2,31,"Q2117-X ",0,0,,,,,,A;
ADD-BCSU:PER,1,2,55,"Q2214-X ",0,0,,,,,,A;
ADD-BCSU:PER,1,2,61,"Q2208-X100",0,0,,,,,,A;
ADD-BCSU:DIU,1,2,79,"Q2096-X200",0,,,,,0,,,,,A;
ADD-BCSU:DIU,1,2,85,"Q2096-X200",0,,,,,0,,,,,A;
ADD-BCSU:DIU,1,2,91,"Q2096-X200",0,,,,,0,,,,,A;
ADD-BCSU:DIU,1,2,97,"Q2096-X200",0,,,,,0,,,,,A;
ADD-BCSU:PER,1,2,103,"Q2235-X ",0,0,,,,,,A;
ADD-BCSU:PER,1,2,109,"Q2235-X100",0,0,,,,,,A;
ADD-BCSU:DIU,1,2,115,"Q2096-X200",0,,,,,0,,,,,A;
ADD-BCSU:PER,1,2,121,"Q2174-X ",0,0,,,,,,A;
35
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: BSSU - Board Switch, Switching Unit Siemens
5 BSSU - Board Switch, Switching Unit

This AMO is used to process modules of the switching unit (SWU).
● Activate:
Modules can be activated either with conditional or with unconditional loading.
● Deactivate:
It is possible to deactivate the module with or without being pre-blocked.
● Restart: Deactivate without pre-blocking and Activate with unconditional loading has been
combined in one action.
● Display:
The statistic counters of the specified module(s) can be displayed and reset.
● ACTIVATE-BSSU : Activate modules

● DEACTIVATE-BSSU : Deactivate modules
● RESTART-BSSU : Reset (Deactivate/activate) modules
● DISPLAY-BSSU : Display module statistic counters
5.1.1 ACTIVATE-BSSU
Individual modules are activated, i.e. any ’manual blocking’ status is removed. Hierarchically
subordinate trunks and terminals are also activated.
Before a module is activated, its status is checked. If it is manually blocked, the block is
removed.
If a pre-blocking is in effect for the module to be activated, the activate job removes the pre-
blocking.
Activation can be carried out:
● with conditional loading
● with unconditional loading
● without loading
In the case of an activate job with conditional loading, the trunk circuit data is only loaded when
necessary.
36
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: BSSU - Board Switch, Switching Unit
After the activate job is executed, a message is output supplying information regarding the
switching state achieved. The message does not specify whether or not the deactivated module
had been manually blocked before the deactivate job.
STMI2-HFA boards
The AMO performs the activation (bring-into-service) action of a STMI2-HFA board from which
IP terminals have been automatically switched from. Because of a board error, either
– without switching back the IP terminals
– with switching back the IP terminals
This command is called after the defective board has been replaced by a board which is ex-
pected to be O.K.
HFASW = IPSTNBCK : AMO switchs (reconfigures) back the IP terminals which had been
originally configured at the specified board and activates the specified board. The DC state of
the specified (standby) board must be MAN_AMO/DEF, where the destination board ( from
which the IP terminals are switched from ) must be DEF or READY.
HFASW = STBYRDY : AMO activates the specified board and changes its Standby Mode
from ...STDBY_DEF to ...STDBY_READY.
HFASW = NONE : AMO just activates the STMI2-HFA board .
HFASW parameter is only valid for STMI2-HFA board, for the rest of the boards this parameter
is ignored.
The following system responses to ACTIVATE-BSSU are possible

– State ’OPERATIONAL’
H2: MODULE <pen> ACTIVATED
– State ’NOT OPERATIONAL’

Hnn: MODULE <pen> ACTIVATED - NOT OPERATIONAL <state>:<loaderror>
– State remains unchanged

F11: MODULE <pen> NOT ACTIVATED (JOB ERROR)
Description <pen>:
<pen> = <LTG number>.<LTU number>.<Slot>
37
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: BSSU - Board Switch, Switching Unit Siemens
Description of <state>:
DEF Module defect
NPR Module not present
UNACA Module blocked due to interrelationship
UNACH Module hierarchically blocked (superordinate unit blocked)
UA/UH Module blocked hierarchically and due to interrelationships
WBT Wrong board type found
Description of <loaderror>:
1 No load files for this module
2 Error occurred during data transmission
3 Fault in module hardware
Example
The module at LTG 1, LTU 2, SLOT 25 is to be activated with conditional loading.
Input:
ACTIVATE-BSSU:AT,1,2,25;
Output:
H02: MODULE 1.2.25 ACTIVATED
or
H12: MODULE 1.2.25 ACTIVATED - NOT OPERATIONAL (UNACH-NPR)
(The module is not operational since it is hierarchically blocked (UNACH) and not present
(NPR). Any existing manual block was removed.)
5.1.2 DEACTIVATE-BSSU
Individual modules are deactivated, i.e., the status ’manual blocking’ or ’pre-blocking’ is set.
When a module is deactivated, all the hierarchical blocks for subordinate units are also set.
Before a module is deactivated, its status is checked. If the module is in a state that does not
permit deactivation, a deactivate job is not issued and, after a corresponding message is sent
to the operator, the AMO is terminated.
Two types of deactivate jobs are possible:
Deactivate jobs with pre-blocking, i.e. existing connections are not released.
Deactivate jobs without pre-blocking, i.e., without regard for existing connections.
The operator receives an advisory message to say that the switching job is executed. The
message does not specify whether or not the deactivated module had been manually blocked.
38
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: BSSU - Board Switch, Switching Unit
If the current reference clock generator is on the module(s) to be deactivated, and there are
other reference clock generators available outside the specified range, the optional parameter
REFOFF is prompted with the advisory H26.
The advisory H27 is prompted if the job affects all reference clock generators. In this case, a
prompt is also given if the value YES was specified when the AMO was started.
The operator can determine what the AMO is supposed to do using the values YES or NO for
the new parameter REFOFF.
The value YES means that if applicable, the module with the current reference clock generator
should also be deactivated.
The value NO means that the module with the current reference clock generator should not be
deactivated. In this case, the AMO responds with the advisory H28.
The value PROMPT (default value) means that the parameter should be prompted if the current
reference clock generator is within the specified range.
5.1.3 RESTART-BSSU
This function resets boards; that means the commands DEACTIVATE and ACTIVATE are
combined in one order. For ranges all devices will be deactivated first and activated afterwards.
All deactivations will be done with OFFTYPE= DI, all activations will be done with
ONTYPE=AUL. The last reference clock generator can not be reset by means of this function,
the message H28 will be displayed.
WTIME parameter is used to have a pause time between activation and deactivation process.
HFASW parameter is only valid for STMI2-HFA board, for the rest of the boards this parameter
is ignored.
Example
The module at LTG 1, LTU 2, SLOT 25 is to be activated with conditional loading.
Input:
RESTART-BSSU:1,2,25;
Output:
H23: MODULE 1.2.25 DEACTIVATED
H02: MODULE 1.2.25 ACTIVATED
39
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: UCSU - Unit Configuration of Switching Unit Siemens
6 UCSU - Unit Configuration of Switching Unit
By means of AMO UCSU the

● Line/Trunk Group (LTG),
● Line/Trunk Unit (LTU) or
● Line/Trunk Units for NBCS access points (AP)
are configured.
The data of the centralized modules is basically initialized in the HW structure memory of the
SWU-DB. With the action ’ADD a call processing unit’ the status execpt the central SIU ’not
equipped’ is cancelled.
Note
The AMO itself determines in which type of system it is running and reacts accordingly.
● ADD-UCSU : Create LTG and LTU

● CHANGE-UCSU : Change LTU, SIPARTNO, MTS/CONF-Module and configure
overlay-LTUs
● DELETE-UCSU : Cancel LTG, LTU and overlay-LTUs
● DISPLAY-UCSU : Interrogate status of LTG, LTU
● REGENERATE-UCSU : Regenerate LTG and LTU
6.1.1 ADD-UCSU
Create LTG
With the creation of an LTG the LTG status ’not equipped’ is cancelled and the LTG is assigned
the status ’not loaded’.
The LTG newly created by AMO UCSU can be placed into service by means of AMO USSU
following complete configuration.
Since EV3.0 only one LTG (LTG1) can be configured. The parameter itself will not be canceled
for certain reasons.
40
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: UCSU - Unit Configuration of Switching Unit
Create LTU or AP
The data (module type, identification code) required for the creation of an LTU is read out of the
module table (UBGDAT) reloaded by the AMO and entered in the hardware structure memory
of the SWU database. Before an LTU is created the associated LTG must be set up.
The LTPARTNO parameter specifies which LTUC board will be added.
If the LTUC board doesn’t correspond to the system type the AMO will be aborted.
Possible LTUC boards:
PARTNO UNIT System type
Q2148-X LTUCE Compact shelf
Q2136-X SCC 80CM(X)
Q2166-X LTUCX SIPAC Compact shelf
Q2189-X100 LTUCC SIPAC Compact shelf
Q2189-X300 LTUCC SIPAC Compact shelf
Q2248-X LTUCW SIPAC Compact shelf
Q2261-X100 DSCX 80CXE / 40CMX
Q2266-X LTUCA 600 cPCI
Q2302-X NCUI SIPAC Compact shelf on
AP, 19" box on AP
Q2302-X10 NCUI SIPAC Compact shelf on
AP, 19" box on AP
Q2305-X NCUI2 SIPAC Compact shelf on
AP, 19" box on AP
Q2305-X10 NCUI2 SIPAC Compact shelf on
AP, 19" box on AP
The LTUCC board is not released in the moment and therefore all parameters which are used
to control the „central byte manipulation“ and „echo cancelation“ are not ieffective.
LTUC default value: Q2166-X.
41
EN4401EN00EN_0005
© 2005 Siemens AG
With parameter FRMTYPE the type of the LTU-shelf can be determined. The following table
gives an overview, which frametypes are allowed in which LTU of the different HICOM-types:
CLASS ASSEMBLY HICOM TYPE PLATFORM FRAMETYPE LTU

HICOM40 EXT_COMPACT_DSC H40CMX BASE ATLANTIK CC40F 1
HICOM80 EXT_COMPACT_X H80CMX ATLANTIK CC80W 1
L80XW 2-n
HICOM80 EXT_COMPACT_X H80CMX ATLANTIK L80XF 17 - 99
INCH19
HICOM80 EXT_COMPACT_DSC H80CMX-DSC ATLANTIK CC80F 1
L80XF 2-n
HICOM80 EXT_COMPACT_DSC H80CMX-DSC ATLANTIK L80XF 17 - 99
INCH19
HICOM80 EXT_COMPACT_CXE H80CXE ATLANTIK CC80F 1
(H330E) L80XF 2-n
HICOM80 EXT_COMPACT_CXE H80CXE ATLANTIK L80XF 17 - 99
(H330E) INCH19
HICOM600 NON_COMPACT H600 PREATLANTIK PREATLANTIK 1-n
HICOM600 COMPACT H600C PREATLANTIK PREATLANTIK 1-n
HICOM600 EXT_COMPACT H600EC PREATLANTIK PREATLANTIK 1-n
HICOM600 EXT_COMPACT_X H600ECX ATLANTIK LTUW 1-n
(H350E)
HICOM600 EXT_COMPACT_X H600ECX ATLANTIK L80XF 17 - 99
(H350E) INCH19
HICOM600 EXT_COMPACT_X H600ECS ATLANTIK LTUW 1-n
(H350E) L80XF
HICOM600 EXT_COMPACT_X H600ECS ATLANTIK L80XF 17 - 99
(H350E) INCH19
HICOM600 CPCI H600CPCI ATLANTIK LTUW 1-n
L80XF
INCH19
n ... max number of possible LTUs according HW type
Existing HICOM Types
New HICOM Types
With UNIT=LTU and UNIT=LTU parameter LTG is only a single value.
42
EN4401EN00EN_0005
© 2005 Siemens AG
Examples
1. Create LTU=1.
Input:
ADD-UCSU:LTU,1,1,,LTUW,LOCAL;
Output:
LTU 1.1 ADDED - IN OPERATION
Possible outputs:
LTU 1.1 ADDED - IN OPERATION
LTU 1.1 ADDED - OUT OF OPERATION
LTU 1.1 ADDED - OUT OF OPERATION (NOT PRESENT)
LTU 1.1 NOT ADDED
| |
| |
| +------ LTU
|
+-------- LTG
2. Create LTU 1 to 4 (LTG 1)

Input:
ADD-UCSU:LTU,1,1&&4,"Q2248-X ",LTUW,LOCAL,,"OCEAN DRIVE 17";
Output:
H01: LTU 1.1 ADDED - IN OPERATION (READY)
H02: LTU 1.2 ADDED - OUT OF OPERATION (DEF)
F14: LTU 1.3 ALREADY ADDED
F02: LTU 1.4 NOT ADDED (ORDER ERROR)
3. Create AP 20 (LTG 1)
Input:
ADD-UCSU:AP,1,20,"Q2302-X ",5,INCH19,APDL,,,234,"WILSHIRE BOULEVARD
123",6338234,6338236,30;
Output:
H15: PARAMETER APRTADDR CAN NOT BE CHECKED FOR A PLAUSIBLE VALUE.
THIS CHECK WILL BE DONE LATER WITHIN AMO-APRT.
H03: ADD DATA FOR LTU 1.20 WITH AMO CONSY
43
EN4401EN00EN_0005
© 2005 Siemens AG
6.1.2 CHANGE-UCSU
Modify by means of the action CHANGE:
– type of LTUC module and some other parameters of LTU
– PARTNO of central SIU
– Only the following LTUC/NCUI boards can be modified:
LTUC-old direction LTUC-new

Q2148-X ---> Q2248-X
Q2248-X <---> Q2166-X
Q2248-X <---> Q2189-X?00
Q2166-X <---> Q2189-X?00
Q23??-X <---> Q23??-X10
6.1.3 DELETE-UCSU
Delete LTG and LTUs

1. Delete LTG
The associated LTUs and the peripheral modules must be deleted first.
2. Delete LTU or AP shelf
The associated peripheral modules must be deleted first (AMOs BSSU and BCSU).
When deleting LTG or LTU the consy data will be checked and an appropriate advisory
message will be output if still assigned.
Examples
1. Delete LTU 2
Input:
DELETE-UCSU:UNIT=LTU,,2;
Output:
LTU 1.2 DELETED
LTU 1.2 NOT DELETED
| |
| +------ LTU no.
+-------- LTG no.
44
EN4401EN00EN_0005
© 2005 Siemens AG
2. Delete LTU 2 to 4 (LTG 1)

Input:
DELETE-UCSU:UNIT=LTU,LTG=1,LTU=1&&4;
Output:
H10: LTU 1.1 IS ALREADY DELETED
H07: LTU 1.2 DELETED
H07: LTU 1.3 DELETED
F07: LTU 1.4 NOT DELETED (ORDER ERROR)
6.1.4 DISPLAY-UCSU
The configuration and states of LTG and LTU can be determined by means of the action
DISPLAY.
Note
If the parameter LTG is not specified for UNIT=LTG, all LTGs are interrogated. In neither
parameter LTU nor parameter LTG is specified for UNIT=LTU, all LTUs are interrogated.
Examples
1. List all LTGs and LTUs. Overlay LTU 10 is assigned to standard LTU 3.
Input:
DISPLAY-UCSU:LTU;
Output:
+-----------+---------------------+-----------------------+------------+
| ADDRESS | EXPECTED CONFIGUR. | STATE OF A/B HALF | PARTNO SIU |
+-----------+---------------------+-----------------------+------------+
| LTG 1 | ADDED | READY / ? | Q2261-X |
+-----------+---------------------+-----------------------+------------+
+---------+-------------------+---------+--------------+----------+--------+
|ADDRESS |EXPECTED CONFIGUR. |STATE |LTUC MODULE |LTU-TYPE |FRMTYPE |
| +-------------------+---------+--------------+----------+--------+
| |CONNTYPE LOCATIONID LOCATION SRCGRP |
| |PHONE: FAX: |
| |AMOUNT VCOM CHIPS CHIPMODE1 CHIPMODE2 CHIPMODE3 CHIPMODE4 |
| | CHIPMODE5 CHIPMODE6 CHIPMODE7 CHIPMODE8 |
| |LOWER THRESHOLD HIGHER THRESHOLD RESERVED FOR AMC |
+---------+-------------------+---------+--------------+----------+--------+
45
EN4401EN00EN_0005
© 2005 Siemens AG
|LTU 1.1 |ADDED |READY |Q2261-X |CC80F |CC80F |

| +-------------------+---------+--------------+----------+--------+
| |LOCAL 1 |
| |PHONE: FAX: |
| | |
| | |
| | |
+---------+-------------------+---------+--------------+----------+--------+
|LTU 1.2 |ADDED |NPR |Q2166-X |EXT_COMP_X|L80XF |
| +-------------------+---------+--------------+----------+--------+
| |LOCAL 1 |
| |PHONE: FAX: |
| | |
| | |
| | |
+---------+-------------------+---------+--------------+----------+--------+
| +-------------------+---------+--------------+----------+--------+
| |LOCAL 1 |
| |PHONE: FAX: |
| | |
| | |
| | |
+---------+-------------------+---------+--------------+----------+--------+
| +-------------------+---------+--------------+----------+--------+
| |LOCAL 1 |
| |PHONE: FAX: |
| | |
| | |
| | |
+---------+-------------------+---------+--------------+----------+--------+
|ADDRESS |EXPECTED CONFIGUR. |STATE |LTUC MODULE |LTU-TYPE |FRMTYPE |
| +-------------------+---------+--------------+----------+--------+
| |CONNTYPE LOCATIONID LOCATION SRCGRP |
| |PHONE: FAX: |
| |LSRTADDR APRTADDR BCHL BCHLCNT PLCHECK SIGNAL. |
| |CURRENT BANDWITH KONVLAW |
+---------+-------------------+---------+--------------+----------+--------+
|AP 1.20|ADDED |UNACH |Q2305-X10 | |L80XF |
| +-------------------+---------+--------------+----------+--------+
| |APNW 234 MOOSLACKENGASSE 45 |
| |PHONE: FAX: |
| |167.123.111.012 123.000.111.012 120 120 NO LAN |
| | 100 MBIT/S NO |
+---------+-------------------+---------+--------------+----------+--------+
46
EN4401EN00EN_0005
© 2005 Siemens AG
2. List LTG 1.
Input:
DISPLAY-UCSU:LTG,1;
Output:
+-----------+---------------------+-----------------------+------------+
| ADDRESS | EXPECTED CONFIGUR. | STATE OF A/B HALF | PARTNO SIU |
+-----------+---------------------+-----------------------+------------+
| LTG 1 | ADDED | READY / READY | Q2234-X |
+-----------+---------------------+-----------------------+------------+
Only one status is output for the dependability and AM status, which may consist of a combi-
nation of statuses.
Possible outputs:
MANAMO = disabled by AMO

UNACH = disabled by hierarchy
UNACA = disabled due to interrelationship
DEFECT = disabled due to error
NPR = not present
READY = in operation
NL = not loaded
ORDER ERROR = order cannot be processed by DC
NEQ = not equipped
WBT = wrong board type
LOCKED = blocked
BUSY = busy
6.1.5 REGENERATE-UCSU
By means of this order, position-oriented commands for the regeneration of MBU, LTG or LTU
data are output.
Note
If parameter LTG is not specified for UNIT=LTG, regenerate commands are created for all
LTGs set up. If neither parameter LTU nor parameter LTG is specified for UNIT=LTU,
regenerate commands are created for all LTUs set up.
47
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: USSU - Unit Switch of Switching Unit SWU Siemens
Example
1. Regenerate all
REGENERATE-UCSU;
Output:
REGENERATE-UCSU;
H500: AMO UCSU STARTED

ADD-UCSU:LTG,1,"Q2261-X ";
ADD-UCSU:LTU,1,1,"Q2261-X ",CC80F,LOCAL,,"
",,,,,,;
ADD-UCSU:LTU,1,2,"Q2166-X ",L80XF,LOCAL,,"
",,,,,,;
",,,,,,;
",,,,,,;
ADD-UCSU:AP,1,20,"Q2305-X10 ",45,L80XF,APNW,167.123.111.12,123.0.111.12,
234,"MOOSLACKENGASSE ",,,,0,100,120,NO;
7 USSU - Unit Switch of Switching Unit SWU

This AMO is used to process the switching unit system units. The server modules are
processed by other AMOs.
LTG, LTUs, central SIUs, RTM and HDLC-DCL highways are activated and LTUs are deacti-
vated. Peripheral SIUs has to be switched by means of AMO BSSU.
● ACTIVATE-USSU : Activate system units

● DEACTIVATE-USSU : Deactivate system units
● EXEC-USSU AP Shelf configuration and deconfiguration.
● DISPLAY-USSU Display Background Loading status of the files ( for AP
shelves)
48
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: USSU - Unit Switch of Switching Unit SWU
7.1.1 ACTIVATE-USSU
Activation of system units in the SWU.
1. Activating an LTU
2. Activating the LTG
3. Activating an central SIU
4. Activating an HDLC-DCL highway
5. Activating RTM board.
Activating an LTU involves removing the state "manual blocking". When an LTU is activated, all
hierarchically subordinate units are also unblocked by the CDC (Device Configuration, a part
of Dependability).
The system units are activated without testing.
Before it is activated, the state of the LTU is interrogated. If the LTU is in a state that does not
permit activation, the "activate" order is not issued, error message F22 is issued to the operator
and the AMO is terminated.
After the "activate" order has been executed, a message is output providing information about
the new switching state. No test is made after an LTU has been activated.
If an LTU is not specified, the LTG is activated.
Before activating the LTG, the AMO checks that it is configured. If it is configured, then the
presence of the LTG is reported to the operating system. Activating the LTG may take up to
several minutes. Thus, the AMO does not wait until the activation job is completed, but termi-
nates immediately issuing advisory message H13. The present loadingstate of the LTG is
displayed on DB-board.
When activating an central SIU, the AMO first sends a deactivation command which is immedi-
ately followed by the activation command. This ensures that the current circuit data is reloaded.
In the case of a duplex LTG, both central SIUs of the LTG are reloaded. In such cases, the
operator receives two advisories. Peripheral SIUs has to be switched by means of AMO BSSU.
Activating an HDLC-DCL highway may take up to several minutes. Thus, the AMO does not wait
until the activation job is completed, but terminates immediately issuing the advisory message
H25.
Activation of RTM board has two types : BOARD and DATA. BOARD type activation is handled
same as the SIU activation. The error and advisory messages ; F24, F25, F26 , H19 and H28
are used both for SIU and RTM activation.
For AP shelves (LTU from 17 to 99), there is a new mechanism. The AP shelf can not be
activated before the connection to the AP shelf is established via EXEC-USSU.
49
EN4401EN00EN_0005
© 2005 Siemens AG
Examples:
1. Activate LTU3 of LTG1

Input:
ACTIVATE-USSU:LTG,1,3;
Output:
H06: LTU ACTIVATED - NOT OPERATIONAL (NPR)
LTU3 of LTG1 has been manually unblocked. The module does not exist (NPR).Activate LTG1
Input:
ACTIVATE-USSU:LTG,1;
Output:
H13: LTG ACTIVATED
LTG1 has been introduced to the operating system.

2. Activate LTU3
Input:
ACTIVATE-USSU:LTG,,3;
Output:
H06: LTU ACTIVATED - NOT OPERATIONAL (NPR)
LTU3 has been manually unblocked. The module does not exist (NPR).
3. Activate the SIU
Input:
ACTIVATE-USSU:SIU;
Output:
H28: SIU IN A-HALF WILL BE SWITCHED
H19: SIU ACTIVATED
H28: SIU IN B-HALF WILL BE SWITCHED
H19: SIU ACTIVATED
4. Activate HDLC-DCL highway #4 in LTG1

Input:
ACTIVATE-USSU:HDLC,1,4;
50
EN4401EN00EN_0005
© 2005 Siemens AG
Output:
H25: HDLC-DCL HIGHWAY ACTIVATED
The HDLC highway is being activated though the process is not yet complete.
5. Activate LTU17
Input:
ACTIVATE-USSU:LTG,1,17;
F30: ACTIVATION OF THE AP SHELF NOT POSSIBLE.FIRST EXECUTE
’EXEC-USSU:CONFAP’.
6. Activate RTM
Input:
ACTIVATE-USSU:RTM,BOARD;
Output:
H28: RTM IN A-HALF WILL BE SWITCHED
H19: RTM ACTIVATED
H28: RTM IN B-HALF WILL BE SWITCHED
H19: RTM ACTIVATED
7.1.2 DEACTIVATE-USSU
Individual LTG or LTUs are deactivated. Deactivation involves setting of state "manual
blocking". When the LTG or an LTU is deactivated, all hierarchically subordinate units are also
deactivated by the CDC.
Before the LTG or an LTU is deactivated, its state is interrogated. If the LTG or LTU is in a state
which does not permit deactivation, no deactivation order is issued and the AMO is terminated
after issuing error message F22 to the operator. After the deactivation order has been success-
fully executed, the operator receives a positive acknowledgement.
For deactivating the LTG the AMO does not wait until the activation job is completed, but termi-
nates immediately issuing advisory message H26. The present loadingstate of LTG is
displayed on DB-board.
The AMO also checks whether the deactivation job involves the current reference clock
generator. If the current reference clock generator is on the LTG or LTU to be deactivated, and
other reference clock generators are present outside the specified LTG or LTU, the operator is
prompted for a value for the optional parameter REFOFF with advisory H22.
51
EN4401EN00EN_0005
© 2005 Siemens AG
Message H23 is issued in the event the job affects all reference clock generators. In this case,
the user is also warned if the value Y was entered for parameter REFOFF.
The operator can specify what to do with regard to the reference clock by giving parameter
REFOFF the apropriate value. The value Y means that, if applicable, the LTG or LTU with the
current reference clock supply may be deactivated. The value N means that the LTU with the
current reference clock supply should not be deactivated. In this case, the AMO responds by
issuing advisory H24 or H27.
The value PROMPT for parameter REFOFF (the default value) means that, in the event the
current reference clock generator is within the specified LTU, the operator will be interrogated
as to whether or not the LTU should really be deactivated.
Examples:
1. Deactivate LTU3 of LTG1

Input:
DEACTIVATE-USSU:1,3;
Output:
H03: LTU DEACTIVATED
LTU3 of LTG1 was deactivated. Hierarchically subordinate modules were also deactivated.
2. Deactivate LTU1
Input:
DEACTIVATE-USSU:1,1;
Output:
F16: LTU NOT DEACTIVATED (ACTIVATION/DEACTIVATION IN PROGRESS)
LTU1 of LTG1 has not been deactivated, because an order for activation/deactivation of this
LTU is currently in progress.
52
EN4401EN00EN_0005
© 2005 Siemens AG
7.1.3 DISPLAY-USSU
Background loading status of a specific LTU (valid only for AP shelves) is displayed. It also
provides :
● LTU number,
● Source group index,
● Name of the particular LW file or SIU tone files and
● load status
The masks corresponding to each control flag value are as follows :
FLAG MASK
LOAD_NULL NEVER LOADED
LOAD_STARTED STARTED
LOAD_IN_PROGRESS IN PROGRESS
LOAD_FINISHED FINISHED
LOAD_FAILED FAILED
Display mask looks like as follows :
+------------------------------------------------------------------------------+
| LTU: 1 SOURCE GROUP: 3 READY |
| LW FILE : XXXXXXXX FINISHED SIU TONES: XXXXXXXX FAILED |
| SIU RECV : XXXXXXXX IN PROGRESS SIU ANN : XXXXXXXX FAILED |
| SIU MOH : XXXXXXXX FAILED SIU TDS : XXXXXXXX NEVER LOADED|
+------------------------------------------------------------------------------+
53
EN4401EN00EN_0005
© 2005 Siemens AG
7.2 SDSU Status Display of SWU

In the Common Control (CC) the status of all modules, ports, devices and servers is stored in
the memory.
Using the AMO SDSU (Status Display of Switching Unit) one receives a status overview of all
modules, ports and devices of the SWU and the overall status of the servers.
The AMO runs in the active half of the CC.
Possible status messages:
READY ready
NOGEN not generated
GENNR pre-generated
SOFTLOCK soft lock (always in combination with the states AMO, KEY)
LOCK hard lock (always in combination with the states AMO, KEY)
DEPLOCK Lock as a result of an L2 error
BUSY busy
DEF locked by the dependability due to a fault
NPR not present
WBT wrong board type
UNACH hierarchy lock
UNACA locked due to an interrelationship
DEFIL line alarm
TRS remote lock
AMO locked manually by an AMO
(always in combination with the states SOFTLOCK, LOCK)
HIRAMO hierarchy lock by an AMO
SIGNOFF signed off
NL module not loaded
WAIT waiting for an event (e.g. loading completed)
DEP seized by dependability
CP seized by call processing
CPH CPH bit of call processing
LMB local maintenance block
LHB local hardware block
LSB local software block
RMB remote maintenance block
RHB remote hardware lock
54
EN4401EN00EN_0005
© 2005 Siemens AG
RSB remote software lock

RES reserve
ALL all states
SPEC output of the states on the basis of the
DB_M_QC_STATUS_SET for test purposes
7.2.1 Example: Displaying the Status of Circuit 1 of a peripheral board

DISPLAY-SDSU:STATUS=ALL,TYPE=PEN,LEVEL=PER3,LTG=1,LTU=2,SLOT=79,CCT=1;
H500: AMO SDSU STARTED
LTG1 (PERIPHERY)
------
MOUNTING LOCATION MODULE NAME BDL BD(#=ACT) STATUS
------------------- LTG 1 --------------------- READY
-------L80XF------- LTU 2 --------------------- READY
P102.C80 1.L80 2.079 SLMO24 A Q2168-X READY
CCT LINE STNO SI BUS TYPE
001 136 OPTI ONLY READY
MULTLINE 8. . . . . . . . . . . . . . .READY
000 NO CONN
001 SUBUNIT . . . . . DIGITE MAIN READY
(OPTISET )
LINE: 179 STNO: 7441 SI: VOICE
001 . . . . . . . . DIGITE SUB A READY
002 . . . . . . . . DIGITE SUB A READY
003 . . . . . . . . DIGITE SUB C READY
002 NO CONN
003 NO CONN
004 NO CONN
005 NO CONN
006 NO CONN
007 NO CONN
008 NO CONN
AMO-SDSU -94 STATUS DISPLAY IN SWITCHING UNIT
DISPLAY COMPLETED;
55
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: AMOs in the User Area Siemens
8 AMOs in the User Area
WABE LRNGZ VBZ COSSU TAPRO

Dialing plan SPDC lists and ITR matrix Classes of Standard
Speed dialing No. service
User no. List no. ITR group COS no.

WABE group LCOS (V/D)
ZAND SXSU
SCSU / SBCSU STN
Exchange of
ZANDE Per STN No. personal and
STNNo.
Voice Terminals
device-related data
STN RNGZ COSX ITR group

No. 1, 2 group
TACSU
Line config.
SDAT individual night
STN
Administration of
subscr.-related HOTLN
features. Hotline/
Code blue TGER
Destinations Sharing of
ZRNGZ NV terminals
SPDC
TAPRO dest. call
Key numbers VBZA
programming ITR matrix NAVAR
indiv. ID card, ID Night
card reader options
PERSI BERUZ
COSX SA
Personal time
identification controlled Hunt group
PIN / Name data
BERUM AUN
Call pick-up
CHESE COSX
group SSC
Exec./secretary manually
Secretary controlled Special Subscr.
system MESSENGER
Messen-
ger no.
RCSU RUFUM ZIEL

Adding music Number mapping Dest. no. for MESSGR, FWD,
per user combi-code No.Redial, SPDI, DSS, Name, dest.
key
56
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: AMOs in the User Area
AUN Call pick-up groups

BERUM Class-of-service changeover
BERUZ Class-of-service changeover times
CHESE Executive/secretary system (integrated outer office system)
COSSU Classes of service
HOTLN Destinations for HOTLINE/CODE BLUE
LRNGZ Lists for central number generator
NAVAR Administration of the stat. night variant data
PERSI Personal identification
RCSU Announcement devices in the SWU
RUFUM Number mapping
SA Hunt group
SBCSU Terminals and S0 bus configuration in the SWU
SCSU Configuration of users in the SWU
SDAT Administration of user-related features
SSC Configuration of special users
SXSU Reconfiguration of user voice terminals
TACSU Configuration of analog line ports
TAPRO Key programming for digital terminals
TGER User devices assignment
VBZ Internal traffic restriction (ITR) matrix
VBZA ITR for users with ID card readers
VBZGR ITR groups
WABE Dialing assessment
ZAND Central system data
ZANDE Central system data - extended
ZIEL Destination addresses for users
ZRNGZ Central number generator destinations
57
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: Configuration of a subscriber Siemens
9 Configuration of a subscriber
9.1 UP0/E - subscriber

Configuation of an optiPoint 500 subscriber with a description of the parameter and cross refe-
rences to the related AMOs.
New subscriber number:

Related AMO: WABE
DAR=STN has to be reserved (R) , destination
number (DESTNO) = 0
PEN:
optional parameter, system is using the
next free PEN of a SLMO24/SLMOP, if the
parameter PEN isn’t used.
Related AMO: BCSU/SDSU
58
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: Configuration of a subscriber
Authorizations (COS)- and

LCR-Authorizations (LCOS) classes
LCOSV for service voice
LCOSD for service data
1 for day authorization
2 for night authorization
Related AMOs:
- for content:
COSSU, SDAT
- for LCR:
LDPLN, LDAT
DPLN-group 0-15
Standard=0
Related AMO:
WABE
ITR-group 0-15
Standard=0
Related AMO:
COSX-group 0-15 VBZ
Standard=0
Related AMOs:
BERUM, BERUZ for switching
Secret station number
FEASU: COSXCD, COSXDB, COSXKEY, CO-
If “yes” is selected, the setting of the AMO
SXATND, COSXT
ZAND instead of PERSI is used.
WABE: DAR ACOSX/DCOSX
Related AMOs:
PERSI: PIN for COPIN 7 for the STN
ZAND: ALLDATA2, DISPNUUM=XXX
If ONLYEXT is selected, it is possible to trans-
mit an other number instead of the extension
number.
Related AMO:
KNMAT: MODCON=REPEXT
Central speed calling lists: 0-15
SPDC1: table 1
SPDC2: table 2 Speed Calling Individual
“16” code for deleting 0, 10, 20, 30 destinations
Related AMOs: Related AMOs:
LRNGZ, ZRNGZ DIMSU: SPDI
DIMSU: SPDCL, SPDCD FEASU: SPDI
FEASU: SPDC WABE: KZP=SPDI and SPDIPROG
WABE: DAR SPDC1, SPDC2 ZIEL
59
EN4401EN00EN_0005
© 2005 Siemens AG
IDCR
Station with identity card reader
Number of add-on devices

dependent of the device: 0-4
Key layout standard

Secretary Standard=0-127
Subscriber is secretary of a “CHESE” Related AMO:
executive-secretary group TAPRO
Related AMO:
CHESE
Station in service
yes/no or signed off (no PEN is used)
Alarmnumber
0: no alarm assigned
8-519: number of directional alarm group
520-583: number of personal alarm group
Related AMOs:
VADSU
Reject call back on busy

Attention to parameter CBKBMAX in AMO
SBCSU.
Related AMOs:
FEASU: CBK, DCBB, DCBNOA
ZAND: ALLDATA, CBKNO
(number of callbacks for a STN activated in
case of busy or no answer)
Reject call back on no answer

Attention to parameter CBKBMAX in AMO
Max. number of callback SBCSU.
1-5 or 99
Attention to parameter RCBKB in AMO SBCSU Related AMOs:
Related AMOs: FEASU: CBK, DCBB, DCBNOA
FEASU: CBK, DCBB, DCBNOA ZAND: ALLDATA, CBKNO
ZAND: ALLDATA, CBKNO (number of callbacks for a STN activated in
(number of callbacks for a STN activated in case of busy or no answer)
case of busy or no answer)
60
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: Configuration of a subscriber
Headset
WITHIND Headset with HW indication
NOIND: Headset ohne HW indication
Attention to parameter HSKEY in AMO SBCSU
Function of the HS key (Head set key)

NORMAL: HS key must be used for answer
HSGIND: HS key for indication of the head set
Related AMO:
TAPRO
Callback on no answer is stored in the mail-

box
Attention to parameter RCBKNA in AMO SBC-
SU
Related AMOs:
FEASU: CBK, DCBB, DCBNOA
ZAND: ALLDATA, CBKNO
Text selector for display
Related AMOs:
ZAND: ALLDATA2, TEXTSEL
In ACTIVE TEXTSEL up to 5 languages can be
selected.
An user should select the language with a key:
TAPRO: key LANSEL
SDAT: Attribute LNGDYN or LNGSTAT
61
EN4401EN00EN_0005
© 2005 Siemens AG
9.2 Configuration of an IP-subscriber

An IP-device like e.g. optiPoint 400, optiPoint 410, optiPoint 420 and optiPoint 600 will be con-
figured in priciple like a UP0/E subscriber. Additional resp. other parameters will be shown in
the next part.
IP: connected to a STMI

IP2: connected to a STMI2
Password for IP login procedure.
Codec, used by the Ressource

Manager.
62
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: Deletion of a subscriber
10 Deletion of a subscriber
63
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: Structure of the DPLN Siemens
11 Structure of the DPLN

Digit Analysis is comprised of a general DPLN (WABE) part and one of 16 DPLN groups.
Tabelle 1:
DPLN - General Part (valid for all dial plans)
DIS-WABE:GEN;
Here are listed all codes for those digit analysis results (DAR) which are
displays only the
to be accessible for all stations (valid for all dial plans).
general part!
All stations (DAR=STN) must be listed here.
DPLN 0 DPLN 1 DPLN 2 . . .14 DPLN 15

Codes for digit analy-
sis results (DAR) in
this area are only
accessible for stations
belonging to DPLN 1.
Station Number DIS-WABE:GEN,1;
displays all DPLN entries for

stations with DPLN 1.
(DPLN general part and
DPLN 1)
4511
If STN is assigned to DPLN 1, SCSU/
S(B)CSU must have parameter DPLN=1.
With this he gets access to all codes of
the DPLN valid for all DPLN groups as
well as the codes of DPLN 1.
64
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: Structure of the DPLN
11.1 Overview of the CPS

Possible AMO values: 0 - 22 (from Version V 2.3 --» V 3.x )
Tabelle 2:
0 Auxiliary CPS for networking (DAR NETRTE)

1 Suffix dialing (station / attendant)
2 Switching of in-house call at attendant console
3 Switching of central office call at attendant console
4 Prefix dialing at attendant console
5 Prefix dialing by station
6 CO incoming DID
7 IDN connection from CO incoming DID
8 Consultation of station user from in-house call
9 Consultation of a station user from CO call
10 Incoming station line traffic
11 Incoming tie line traffic
12 Incoming link traffic
13 Seizure from satellite PABX for data traffic
14 CHECK mode on attendant console
15 CHECK mode on HICOM terminal
16 Seizure in private network
17 Seizure during consultation in private network
18 Single code calling device: code digits in suffix dialing
19 Expiration of time supervision
20 Function assignment to key on HICOM terminal
21 Used only in USA
22 Consultation of station user from conference
65
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: WABE - Digit Analysis Siemens
12 WABE - Digit Analysis

"Digit analysis" refers to the assignment of a digit analysis result (DAR) to a dialed digit se-
quence or code. This assignment is dependent on the call progress state (CPS) and digit anal-
ysis group or dial plan (DPLN).
There are two types of digit analysis result: DARs with a specific dialing outcome (e.g. ’STN’;
dialing result is station number), and DARs whose dialing outcome must be defined in other
AMOs (e.g. ’CO’; the trunk routes which can be accessed via this DAR are defined with the
AMO RICHT).
Associated digit analysis results are combined into a digit analysis result pair.
Add simultaneously
DAR 1 DAR 2
AFWDREM DFWDREM
AFWDDTE DFWDDTE
AFWDFAX DFWDFAX
AFFWDDTE DFFWDDTE
AFFWDFAX DFFWDFAX
AFFWDVCE DFFWDVCE
ACBK DCBK
AHTDTE DHTDTE
AHTFAX DHTFAX
AHTVCE DHTVCE
AREM DREM
VMOWN VMFOR
MBON MBOFF
Digit analysis result pairs
Must be entered in sequence

Enter first Enter second
SPDC1 SPDC2
CCS CCSURG
CCMS CCMSURG
DAR pairs for sequential processing
66
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: WABE - Digit Analysis
12.1 ADD-WABE
With this command it is possible to create 1 DAR for one or more CDs or several DARs for one
CD.
In the case of digit analysis result pairs, it is possible to assign both partners for the same sta-
tion number if the desired call progress states are completely mutually exclusive.
If parameter DPLN is omitted, the DAR is created without DPLN branching for all DPLN groups.
If CHECK is not specified, CHECK=ALL is taken as default value.
Example
1. Assign the DAR=STN (station) to station numbers 3200-3299 for all call progress states
allowed for STN.
Input:
ADD-WABE:CD=3200&&3299,DAR=STN;
12.2 DISPLAY-WABE
This function allows the user to
1. display the contents of the DPLN tables according to various criteria (TYPE=GEN).
2. display STN seizures throughout the network based on the destination numbers
(TYPE=STN) or the destination node numbers (TYPE=DNNO).
3. output all CPS values valid for specific DARs (TYPE=CPS).
4. view the office codes currently assigned to the ARNs (TYPE=ARN). This display reflects
the current data stored in the ARN to office code assignment table for digit code display.
In the TYPE=GEN branch, all dial plan data is listed in a table, that is valid independent of
DPLN groups. This is followed by the specific tables for the individual DPLN groups. These ta-
bles show the CDs and CPSs for which a DAR is set up. To obtain a complete output (indepen-
dent of DPLN groups and all DPLN group specific), enter the parameter DPLN=0&&15. If no
value is entered for the parameter DPLN, then the table with the DPLN-independent entries is
only output.
The column for additional information (RESERVED and so on) shows which route DARs are
predefined in the dial plan and are not otherwise used in the system. This is shown by the value
’R’. The same information is output for DAR=STN. If dialed number conversion is assigned to
a station, then this will be shown by the value ’C’ in this column (It is assigned by the AMO RU-
FUM). If a station is assigned as destination for DNI by ACD, then this will be shown by the value
67
EN4401EN00EN_0005
© 2005 Siemens AG
’D’ in this column (It is assigned by the AMO DNIT). The output of an ARN assigned to a CD
of DAR OWNNODE in the dial plan is done also in this column as well as the output of a DEST-
NO and DNNO assigned to a CD of DAR STN, NETW, NETRTE.
Apart from the parameter TYPE, all parameters are optional. If parameters are not explicitly de-
clared, the inputs are initialized with the maximum permitted range in most cases. The default
range for the parameter DESTNO is the entire possible range (0...254); the default value for
DAR is ALL. The exception is parameter DPLN, which must be specified if any DPLN group
specific data should be output.
In the DISPLAY command with TYPE=GEN, a range for the parameter CD may be specified
both, with special characters and different length.
Notes for displayed tables

If value 0 is displayed for DESTNO, the DAR is located in the local node (e.g. for DAR=STN
it is an internal subscriber). In this case, the DNNO of the own node is displayed.
If value > 0 is displayed for DESTNO, the DAR is located in a remote node (e.g. for
DAR=STN it is an external subscriber). The DESTNO corresponding to the AMO RICHT
configuration is output for this.
If value 0-0-0 is displayed for DNNO, the destination node number is undefined, i.e. there
is (still) no route assigned (CD is reserved) in the case of DESTNO>0 or there is (still) no
value defined for own node (AMO ZAND) in the case of DESTNO=0.
For TYPE=STN and TYPE=DNNO there are advisory messages displayed only if there
were no STNs assigned for the DESTNO/DNNO range.
Examples
1. Display the DPLN data with the DAR=ADND
Input:
DISPLAY-WABE:DAR=ADND;
Output:
------------------------------------------------------------------------------
| DIGIT INTERPRETATION VALID FOR ALL DIAL PLANS |
------------------------------------------------------------------------------
| | CALL PROGRESS STATE | DIGIT | RESERVED/CONVERT |
| STATION NUMBER | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| 812 |. ....* ..... ..... ..... ..| ADND | |
| *12 |. ....* ..... ..... ..... ..| ADND | |
------------------------------------------------------------------------------
68
EN4401EN00EN_0005
© 2005 Siemens AG
2. Display the DPLN data for DPLN=2, access codes=0-999,

DAR=STN, SNR and NETW, NETRTE.
Input:
DISPLAY-WABE:DPLN=2,CD=0&&999,DAR=STN&SNR&NETW&NETRTE; Output:
------------------------------------------------------------------------------
| DIGIT INTERPRETATION VALID FOR ALL DIAL PLANS |
------------------------------------------------------------------------------
| STATION NUMBER | 1 11111 11112 22| ANALYSIS| DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| 03 - 07 |* ..... ..... ..... ..... ..| NETRTE | |
| 2100 - 2139 |. .**** ***** **... ..... ..| STN | |
| | | |DESTNO 0 |
| | | |DNNO 3- 28-472* |
| 2140 |. .**** ***** **... ..... ..| STN | R |
| | | |DESTNO 0 |
| | | |DNNO 3- 28-472* |
| 2149 - 2195 |. .**** ***** **... ..... ..| STN | |
| | | |DESTNO 241 |
| | | |DNNO 5- 31-189 |
| 2196 |. .**** ***** **... ..... ..| STN | C |
| | | |DESTNO 0 |
| | | |DNNO 3- 28-472* |
| 3300 - 3302 |. .**** ***** **... ..... ..| NETW | R |
| | | |DESTNO 213 |
| | | |DNNO 0- 0- 0 |
| 3303 |. .**** ***** **... ..... ..| STN | D |
| | | |DESTNO 0 |
| | | |DNNO 3- 28-472* |
------------------------------------------------------------------------------
------------------------------------------------------------------------------
| DIGIT INTERPRETATION DPLN 2 |
------------------------------------------------------------------------------
| STATION NUMBER | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------
| 972 |. ***.* ..**. ..... ..... ..| SNR | |
------------------------------------------------------------------------
69
EN4401EN00EN_0005
© 2005 Siemens AG
3. Display the data for the STNs with DESTNO 0 to 2.

Input:
DIS-WABE:STN,0&&2;
Output:
-----------------------------
| STN FOR DESTNO 0 |
| DNNO 3- 28-472 |
| OWN NODE |
-----------------------------
| 30001 - 30013 |
| 30152 |
| 30537 - 31871 |
| 31888 - 31924 |
-----------------------------
-----------------------------
| STN FOR DESTNO 2 |
| DNNO 8- 17-394 |
-----------------------------
| 30067 - 30096 |
| 32518 - 32519 |
-----------------------------
4. Display the standard CPS allocations for the ’STN’ DAR.
Input:
DIS-WABE:CPS,STN;
Output:
-----------------------------------------
| STANDARD CPS SUBSETS |
-----------------------------------------
| | 1 11111 11112 22|
| DAR |0 12345 67890 12345 67890 12|
-----------------------------------------
| STN |. .**** ***** **... ..... .. |
-----------------------------------------
70
EN4401EN00EN_0005
© 2005 Siemens AG
12.3 REGENERATE-WABE
REGENERATE is similar to DISPLAY. First the commands are output which are valid for all
DPLN (DLN group independent), followed by those that are valid for individual DPLN groups.
All commands are output with CHECK=N.
The DARs STN always are treated as internal reserved stations. After the last ADD command
is output, external stations are searched and the CHANGE commands are output for increasing
order of station numbers.
The DARs OWNNODE are always displayed with the actual ARNs, stored in the dial plan. To
rebuild the ARN to office code assignment table for digit code display, the CHANGE commands
of TYPE=ARN are created after the last ADD command is output.
For the parameters of the REGENERATE command please refer the notes for the parameters
of action DISPLAY / TYPE=GEN.
Example:
Regenerate the DPLN group 2
Input:
REG-WABE:DPLN=2;
Output:
ADD-WABE: 0 , , 9, ANSINT , N,,,,, , ;
ADD-WABE: 00 , , 2, SPDC1 , N,,,,, , ;
ADD-WABE: 00 , , 3, SPDC1 , N,,,,, , ;
ADD-WABE: 20 , , 2, SPDC2 , N,,,,, , ;
ADD-WABE: 28 , , 5, HUNT , N,,,,, , ;
ADD-WABE: 3111 , , , ATNDDID , N,,,,, , ;
ADD-WABE: 3112 &&3199 , , 6, STN , N,,,,, , ;
ADD-WABE: 401 , , 10, ATNDIND , N,,,,, , ;
ADD-WABE: 722 , , 5, AFWDDTE , N,,,,, , ;
ADD-WABE: 726 , , 5, DFWDDTE , N,,,,, , ;
ADD-WABE: DD8 , , , NETRTE , N,,,,, , ;
ADD-WABE: 21011 , 2, 5, TIEATND , N,,,,, , ;
ADD-WABE: 401 , 2, , CONF3 , N,,,,, , ;
ADD-WABE: 401 , 2, 8, PRESCONF, N,,,,, , ;
ADD-WABE: 500 , 2, , CCMANS , N,,,,, , ;
ADD-WABE: 51 , 2, 9, CCMS , N,,,,, , ;
ADD-WABE: 50 , 2, 16, CCMSURG , N,,,,, , ;
ADD-WABE: 70* , 2, , VMOWN , N,,,,, , ;
ADD-WABE: 70# , 2, , VMFOR , N,,,,, , ;
ADD-WABE: 7A , 2, , NETW , N,,,,, 213, ;
CHANGE-WABE: 3127 &&3136 , 172;
CHANGE-WABE: 3137 &&3139 , 11;
71
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: COSSU - Classes of Service Siemens
13 COSSU - Classes of Service

The classes of service contain combinations of authorizations and features and are assigned
to one or more stations (AMO ACSU, AMO SBCSU, AMO SCSU or AMO SSCSU).
COS authorizations are also assigned to trunk circuits for call traffic.
Each class of service is divided into three services:
● Voice (VCE)
● Facsimile (FAX)
● Data Terminal Equipment (DTE)
This table is only a compilation of classmarks. It does not allow you to establish cross-referenc-
es between the different authorizations.
The “without direct trunk access” and “without tie trunk access” authorizations for the specified
service are indicated by the fact that the direct trunk access and tie trunk access authorizations
are not set for the corresponding service.
COS 0 is not a valid class of service.
● LCR classes of service
Change, display, and regenerate LCR classes of service, each with up to 64 LCR authoriza-
tions and LCR options (for example, LCR expensive route tone).
Sixty-four LCR classes of service are permanently configured, 32 of which are for voice, fax,
and 32 of which are for data.
LCOSV=1 is initialized for the attendant console with all the authorizations. The others are ini-
tialized without contents and edited by means of the branch CHANGE.
13.1 ADD-COSSU
A COS can be added in several different ways:
1. Add a new COS while specifying the COS number
ADD-COSSU:NEWCOS=.., .. plus the selected authorizations
2. Add a new COS by copying an existing COS and changing the contents
a) Specify the number of the new COS
ADD-COSSU:COPYCOS=..,NEWCOS=.., .. plus the desired changes
b) The new COS can have any number (1 - 1000)
ADD-COSSU:COPYCOS=.., plus the desired changes
72
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: COSSU - Classes of Service
3. Add a new COS without specifying the COS number and without specifying a COS to be
copied. Only the selected authorizations are specified.
a) If an identical class of service exists, a new COS is not added. The number of the iden-
tical COS is returned.
b) If an identical class of service does not exist, a new COS is added with the specified
authorizations.
4. Add an “empty” COS.
ADD-COSSU:;
In each case, the number of the COS added is output with an advisory message.
The authorizations are inserted by means of the parameters AVCE, AFAX, ADTE or deleted by
means of the parameters DVCE, DFAX, DDTE.
Examples
1. Add a new COS (see item 3.) with the voice authorizations TA, HOT, CDRS, TRACE and
the fax authorization BASIC.
Input:
ADD-COSSU:AVCE=RTA1&RTA6&HOT&CDRS&TRACE,AFAX=BASIC;
Output:
H04: THE NUMBER OF THE CLASS OF SERVICE ADDED IS 27.
2. Add a COS by copying COS 23 (see item 2b.) and inserting the new authorization CDRS.
Input:
ADD-COSSU:COPYCOS=13,AVCE=CDRS;
Output:
3. Add COS 30 by copying COS 1 and assigning the external class of service COEX 5 (see
item 2a.)
Input:
ADD-COSSU:COPYCOS=1,NEWCOS=30,COEX=5;
Output:
73
EN4401EN00EN_0005
© 2005 Siemens AG
13.2 CHANGE-COSSU
If a COS is changed, the change affects all the stations or trunk circuits to which this COS is
assigned. You can display this assignment by means of the AMOs ACSU, SCSU/SBCSU and
TACSU.
Example
1. Change authorizations in COS 16.
(delete BASIC for FAX, insert RTA3 for voice)
CHANGE-COSSU:TYPE=COS,COS=16,AVCE=RTA3,DFAX=BASIC;
13.3 DELETE-COSSU
Classes of service can be deleted provided that they are not used by any stations or trunk cir-
cuits.
Example
Delete COS 27.
DELETE-COSSU:COS=27;
13.4 DISPLAY-COSSU
1. Output all classes of service.
All the configured classes of service, the 16 COEX (even if not assigned to a COS) and all
the LCR classes of services are output.
2. Selectively output one or more COS.
3. Output the COS containing the specified authorizations (TYPE = COS ).
4. Output the external classes of service (COEX).
5. You can display all the LCR classes of service for voice (TYP=LCOSV parameter only) or
all the LCR classes of service for data (TYP=LCOSD parameter only) along with their LCR
authorizations and options.
You can display specific LCR classes of service for voice (TYPE=LCOSV plus LCOSV pa-
rameter) or specific LCR classes of service for data (TYP=LCOSD plus LCOSD parame-
ter) along with their LCR authorizations and options.
6. However, you can also display the numbers of the LCR classes of service containing at
least one of maximum five predefined LCR authorizations (TYPE=LCOS and LCOS pa-
rameter).
74
EN4401EN00EN_0005
© 2005 Siemens AG
7. Finally, you can also output the station numbers of all the stations and the port equipment
numbers of all the circuits (by specifying the associated AMO for each) to which a specific
COS or a specific LCOSV/D is assigned (TYPE=COS with FORMAT=REF or
TYPE=LCOSV/D with FORMAT=REF).
Examples
1. Display COS 1 and 3 to 5
DISPLAY-COSSU:TYPE=COS,COS=1&3&&5;
Output:
+-----+----------------+----------------+----------------+
| COS | VOICE | FAX | DTE |
+-----+----------------+----------------+----------------+
| 1 |>EXAMPLE 1 |
| | RTA1 | RTA1 | RTA1 |
| | RTA4 | RTA4 | RTA4 |
| 3 |>EXAMPLE 3 |
| | RTA3 | NOTIE | NOTIE |
| | RTA4 | RTA4 | RTA4 |
| 4 |> |
| | RTA | NOTIE | NOTIE |
| | TTCR3 | RTA | RTA |
| | TTCR4 | BASIC | BASIC |
| | COSXCD | | |
| | COEX1 | | |
| | | | |
+-----+----------------+----------------+----------------+
Only COS 1, 3 and 4 are configured. In this case, no INFOTEXT is configured for COS 4.
2. Display the COS containing the specified authorization pattern.
DISPLAY-COSSU:TYPE=AUTH,COND=SUBSET,VCE=RTA&RTA1&RTA2&TTCR1&TTCR2;
(Note: COND=SUBSET parameter does not have to be specified because the value
of SUBSET is assumed to be the DEFAULT value.)
Output:
+------------------------------------------------------+
| THE CLASS MARKS ARE CONTAINED IN THE FOLLOWING COS |
+----------+----------+----------+----------+----------+
| COS 24 | COS 25 | | | |
+----------+----------+----------+----------+----------+
75
EN4401EN00EN_0005
© 2005 Siemens AG
3. OUTPUT LCOSS 2 TO 5
Input:
DISPLAY-COSSU:TYPE=LCOSV,LCOSV=2&&5;
Output:
+----+----------------------------------------------------------------+-----+
|LCOS| LAUTH | LCR |
| V | 1 2 3 4 5 6 |OPTS=|
| |1234567890123456789012345678901234567890123456789012345678901234|LCRET|
| |>SERVICE INFORMATION | LCR |
+----+----+----|----+----|----+----|----+----|----+----|----+----|----+-----+
| 2|XX..............................................................| . |
| 3|XX..............................................................| . |
| 4|.............X......................X...........................| X |
| 5|................................................................| . |
+----+----------------------------------------------------------------+-----+
4. OUTPUT ALL LCOS WITH LAUTH 4 AND 8

Input:
DISPLAY-COSSU:TYPE=LCOS,LCOS=4&8;
Output:
THE LCR CLASSMARKS ARE CONTAINED IN THE FOLLOWING LCOS :
+-----+-----------------------------------------------------------------+
| LCOS| LCOSV | LCOSD |
| | 1 2 3 | 1 2 3 |
| |12345678901234567890123456789012|12345678901234567890123456789012|
| |>SERVICE INFORMATION |
+-----+----+----|----+----|----+----|--+----+----|----+----|----+----|--+
| 4 |XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX|X |
| 8 |XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX|X |
+---- +-----------------------------------------------------------------+
76
EN4401EN00EN_0005
© 2005 Siemens AG
5. OUTPUT ALL ACs, stations, circuits with LCOSS=1, 2 AND 3

INPUT:
DISPLAY-COSSU:TYPE=LCOSV,LCOSV=1&&3;
OUTPUT:
+----+----------------------------------------------------------------+-----+
|LCOS| LAUTH | LCR |
| V | 1 2 3 4 5 6 |OPTS=|
| |1234567890123456789012345678901234567890123456789012345678901234|LCRET|
| |>SERVICE INFORMATION | LCR |
+----+----+----|----+----|----+----|----+----|----+----|----+----|----+-----+
| 1|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX| . |
| |>LCR Attendant for voice |
+----+----------------------------------------------------------------+-----+
13.5 REGENERATE-COSSU
If no parameter is entered, all the COS, COEX and LCR COS are regenerated.
1. Regenerate all configured classes of service (TYPE=COS only) or the specified COS (in
addition to TYPE=COS, also COS=<number>).
The regenerated COS is distributed over several commands (one command per service). If
a COS is assigned to a COEX, a CHANGE command with TYPE=COEX is also generated.
2. Regenerate external classes of service (COEX) only.
3. You can regenerate all the LCR classes of service for voice (TYPE=LCOSV parameter on-
ly) or all the LCR classes of service for data (TYPE=LCOSD parameter only) along with
their LCR authorizations and LCR options. You can regenerate specific LCR classes of
service along with their LCR authorizations and LCR options (TYPE=LCOSV/D plus
LCOSV/D parameter).
Examples
1. Regenerate class of service 16
INPUT:
REGERATE-COSSU:COS=16;
OUTPUT:
ADD-COSSU:,16,TA&TNOTCR&CDRATN&CDRSTN&CDRINT,,,,,,,,,,,;
77
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: TAPRO - Key Programming Siemens
14 TAPRO - Key Programming

The AMO TAPRO is used for loading the programmable key functions of digital voice terminals.
Various standard or individual key assignments can be loaded. The AMO TAPRO also allows
individual key functions to be changed. Furthermore, the AMO is used for the administration of
the standard key assignments.
Functions
The AMO TAPRO can be used for the following terminal types:
● optiset E T3 / T8 / T12
● optipoint 500 T8 / T12 / T19
● optipoint 600 T19
● optiPoint 400 T12
● optiPoint 410 T8 / T12 / T19
● optiPoint 420 T12 / T18
● as well as the various add-on terminal types for optiset E and optipoint 500/600/410/420.
With the AMO TAPRO, it is not necessary to set up the standard key assignments, since all 127
for optiset valid standard assignments for each terminal type are already stored in the data-
base. All terminals are allocated one of these standard assignments when they are first config-
ured.
14.1 CHANGE-TAPRO
Change the standard key layout or change the freely-programmable key layout for one or more
stations.
The changes are carried out as follows:
● Changing a standard key layout.
For this, the number of the standard key layout must be specified instead of a station num-
ber. Changing a standard key layout has no direct effect on the key layouts already loaded
at the various terminals.
Hints for changing the standard key layouts:
– Max. 4 RNGXFER keys and max. 4 PUS keys.
78
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: TAPRO - Key Programming
– The remaining functions (except VACANT, LINE, NAME and DSS) may only be as-
signed once. When allocating an existing key function to a different key during a stand-
ard key layout change, the old key allocation is canceled automatically.
● Assigning the key functions
For this, at least one station number must be specified. If a standard key layout number is
also specified, a standard key layout is assigned. If no standard key layout is specified, the
AMO assumes that only the functions of the freely-programmable keys are to be loaded.
Only one command is necessary to change the standard key layout and assign new func-
tions to the freely-programmable keys of the specified station(s).
Hints for assigning the key functions
– Max. 4 RNGXFER keys (execpt subscriber is executive) and max. 4 PUS keys.
– Max. 1 RNGXFER key if subscriber is executive
A standard with more than 1 RNGXFER key can be assigned to a executive, but the
executive can only use the first RNGXFER key and the others are only allocated with
this function. If one RNGXFER key is indiviual changed, all other RNGXFER keys are
deleted.
– The remaining functions (except VACANT, LINE, NAME and DSS) may only be as-
signed once. When allocating an existing key function to a different key during a stand-
ard key layout change, the old key allocation is canceled automatically.
– The MB key function cannot be re-assigned if the user’s "mailbox" contains new (i.e.
unheard) messages.
– The following keys must not be deleted while in the active state:
FWD key, REP key, KNOVR key, DND key and HT key.
Note
The terminal will be not deactivated from the AMO TAPRO, exeption deletion of DSS keys.
If the terminal was deactivated befor the processing, it remain deactivated.
A standard key layout with add-on terminal can be assigned to a subscriber OPTISET without
add-on terminal, but only the key functions of the basic terminal are accepted.
Examples
1. Change the standard key layout 5 for all optiset terminals. Change KY01 to call forwarding
and KY02 - KY04 to name keys.
Input:
CHANGE-TAPRO:STD=5,DIGTYP=OPTISET,KY01=FWD,KY02=NAME,KY03=NAME,KY04=NAME;
79
EN4401EN00EN_0005
© 2005 Siemens AG
Output:
H04: STANDARD 5 CHANGED FOR OPTISET.
2. Load the new standard 5 at the optiset terminal of station 3154, and change the function
of key 12 to TIME.
Input:
CHANGE-TAPRO:STNO=3154,STD=5,DIGTYP=OPTISET,KY12=TIME;
Output:
H03: FUNCTION KEY LAYOUT CHANGED FOR STATION 3154.
14.2 DISPLAY-TAPRO
This function is used to output the following information:
1. all valid standard key layouts and all loaded key layouts for all stations with digital terminals.
2. specific standard key layouts in a specific output format. Patternsearch in info service field.
3. key layouts loaded at specific stations.
Examples
1. Display the key layout of standard 7 and standards 38 to 40 for optiset.
Input:
DISPLAY-TAPRO:TYPE=STD,STD=7&38&&40,DIGTYP=OPTISET;
Output:
+-----+---------+--------------------------------------------------------------+
| STD | DIGTYP | "SERVICE INFORMATION’ KEY LAYOUT |
+-----+---------+--------------------------------------------------------------+
| 7 | OPTIT3 | "3 KEYS U.S. STD 3: HOLD/PARK (SYSTEM ORBIT) " |
| | | 1 HOLD 2 SPARK 3 LINE |
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| | OPTIA1 | 1 VACANT 2 VACANT 3 VACANT 4 VACANT 5 VACANT |
| | | 6 VACANT 7 VACANT 8 VACANT 9 VACANT 10 VACANT |
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
80
EN4401EN00EN_0005
© 2005 Siemens AG
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
+-----+---------+--------------------------------------------------------------+
| 38 | OPTIT19 | "19 KEYS I.M. STD 6: ADVANCED KEY 5 LINES " |
| | | 1 CH 2 SNR 3 MB 4 SPKR 5 PU |
| | | 6 PARK 7 HOLD 8 LINE 9 LINE 10 LINE |
| | | 11 LINE 12 LINE 13 NAME 14 NAME 15 NAME |
| | | 16 NAME 17 NAME 18 NAME 19 RLS |
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
+-----+---------+--------------------------------------------------------------+
| 39 | OPTIT19 | "19 KEYS U.S. STD 0: 2 LINE PHONEMAIL " |
| | | 1 PHML 2 NAME 3 CH 4 MENU 5 CL |
| | | 6 NAME 7 NAME 8 NAME 9 NAME 10 NAME |
| | | 11 NAME 12 PU 13 PARK 14 CONF 15 CONS |
| | | 16 CNCT 17 HOLD 18 LINE 19 LINE |
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
+-----+---------+--------------------------------------------------------------+
| 40 | OPTIT19 | "19 KEYS U.S. STD 1: ACD AGENT " |
| | | 1 PHML 2 SCROL 3 CH 4 MENU 5 CL |
| | | 6 ACDLOG 7 ACDNAV 8 ACDWORK 9 ACDAV 10 ACDSPVM |
81
EN4401EN00EN_0005
© 2005 Siemens AG
| | | 11 ACK 12 NAME 13 ACDPQS 14 AUTOM 15 CONS |

| | | 16 CNCT 17 HOLD 18 LINE 19 LINE |
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
+-----+---------+--------------------------------------------------------------+
2. Display the program key layout for stations 2190 to 2194.

Input:
DISPLAY-TAPRO:TYPE=STN,STNO=2190&&2194;
Output:
+--------------+-----+---------+----------------------------------------------+
| STATION | STD | DIGTYP | FUNCTION KEYS WHICH DIFFER FROM STANDARD |
+--------------+-----+---------+----------------------------------------------+
| 2190 | 0 | OPTISET | 4 VACANT 10 DOOR 11 SPKR |
+--------------+-----+---------+----------------------------------------------+
| 2191 | 1 | OPTISET | 1 MB 2 ST 3 SNR 5 VACANT |
+--------------+-----+---------+----------------------------------------------+
| 2193 | 1 | OPTISET | 2 CONS 8 MB |
| | + - - - - + - - - - - - - - - - - - - - - - - - - - - - -+
| | | OPTIA1 | 12 WW |
+--------------+-----+---------+----------------------------------------------+
| 2194 | 1 | OPTISET | 2 CONS 8 MB |
| | + - - - - + - - - - - - - - - - - - - - - - - - - - - - -+
| | | OPTIA2 | 9 DR |
| | + - - - - + - - - - - - - - - - - - - - - - - - - - - - -+
| | | OPTIA4 | 8 DOOR 12 SNR |
+--------------+-----+---------+----------------------------------------------+
The key layout is displayed for all terminals whose station numbers lie within the specified range
of 2190 to 2191, regardless of the terminal type.
82
EN4401EN00EN_0005
© 2005 Siemens AG
3. Display the key layout for all stations with optiset terminals and the standard key layout 0.
Input:
DISPLAY-TAPRO:TYPE=STN,STD=0,DIGTYP=OPTISET;
Output:
+--------------+-----+---------+--------------------------------------------+
| STATION | STD | DIGTYP | FUNCTION KEYS WHICH DIFFER FROM STANDARD |
+--------------+-----+---------+--------------------------------------------+
| 2191 | 0 | OPTISET | 1 MB 2 ST 3 SNR 5 VACANT |
+--------------+-----+---------+--------------------------------------------+
| 3500 | 0 | OPTISET | |
| | + - - - - + - - - - - - - - - - - - - - - - - - - - - -+
| | | OPTIA2 | 1 RR |
+--------------+-----+---------+--------------------------------------------+
All digital optiset terminals with the specified standard key layout are output according to station
number.
4. Display service Informations for key standards 0.
Input:
DISPLAY-TAPRO:TYPE=STD,STD=0,FORMAT=S,INFOPAT="12 KEYS";
Output:
+-----+---------+--------------------------------------------------------------+
| STD | DIGTYP | "SERVICE INFORMATION' KEY LAYOUT |
+-----+---------+--------------------------------------------------------------+
| 8 | OPTIT12 | "12 KEYS I.M. STD 0: BASIC12 /SPEAKER12 " |
+-----+---------+--------------------------------------------------------------+
| 9 | OPTIT12 | "12 KEYS I.M. STD 1: BASIC12 /SPEAKER12 ALTERNATIVE" |
+-----+---------+--------------------------------------------------------------+
| 10 | OPTIT12 | "12 KEYS I.M. STD 2: 4 PERSON TEAM " |
+-----+---------+--------------------------------------------------------------+
| 11 | OPTIT12 | "12 KEYS I.M. STD 3: 8 PERSON TEAM (1 KEU) " |
+-----+---------+--------------------------------------------------------------+
| 12 | OPTIT12 | "12 KEYS I.M. STD 4: SECRETARY 1/1 (1 KEU) " |
+-----+---------+--------------------------------------------------------------+
| 13 | OPTIT12 | "12 KEYS I.M. STD 5: SECRETARY 1/2 OR 2/2 (1 KEU) " |
+-----+---------+--------------------------------------------------------------+
| 14 | OPTIT12 | "12 KEYS I.M. STD 6: SECRETARY 4/1 OR 4/2 (1 KEU) " |
+-----+---------+--------------------------------------------------------------+
| 15 | OPTIT12 | "12 KEYS I.M. STD 7: SECRETARY MEMBER OF MINI CHESE" |
+-----+---------+--------------------------------------------------------------+
| 16 | OPTIT12 | "12 KEYS I.M. STD 8: EXECUTIVE MEMBER OF MINI CHESE" |
+-----+---------+--------------------------------------------------------------+
| 17 | OPTIT12 | "12 KEYS I.M. STD 9: ACD AGENT 1 " |
+-----+---------+--------------------------------------------------------------+
| 18 | OPTIT12 | "12 KEYS I.M. STD 10: ACD SUPERVISOR 1 " |
83
EN4401EN00EN_0005
© 2005 Siemens AG
+-----+---------+--------------------------------------------------------------+
| 19 | OPTIT12 | "12 KEYS I.M. STD 11: ACD AGENT 2 " |
+-----+---------+--------------------------------------------------------------+
| 20 | OPTIT12 | "12 KEYS I.M. STD 12: ACD SUPERVISOR (1 KEU) " |
+-----+---------+--------------------------------------------------------------+
| 21 | OPTIT12 | "12 KEYS I.M. STD 13: BASIC12 /SPEAKER12 KEY STD " |
+-----+---------+--------------------------------------------------------------+
| 22 | OPTIT12 | "12 KEYS I.M. STD 14: ADVANCED KEY 4 LINES " |
+-----+---------+--------------------------------------------------------------+
| 23 | OPTIT12 | "12 KEYS I.M. STD 15: ADVANCED KEY (1 KEU) " |
+-----+---------+--------------------------------------------------------------+
| 24 | OPTIT12 | "12 KEYS I.M. STD 16: ADVANCED KEY (2 KEU) " |
+-----+---------+--------------------------------------------------------------+
| 25 | OPTIT12 | "12 KEYS I.M. STD 17: BASIC KEY AGENT " |
+-----+---------+--------------------------------------------------------------+
| 26 | OPTIT12 | "12 KEYS I.M. STD 18: BASIC KEY SUPERVISOR (1 KEU) " |
+-----+---------+--------------------------------------------------------------+
| 27 | OPTIT12 | "12 KEYS I.M. STD 19: ADVANCED KEY AGENT (1 KEU) " |
+-----+---------+--------------------------------------------------------------+
| 28 | OPTIT12 | "12 KEYS I.M. STD 20: ADV. KEY SUPERVISOR (1 KEU) " |
+-----+---------+--------------------------------------------------------------+
+-----+---------+--------------------------------------------------------------+
| 97 | OPTIT12 | "12 KEYS U.S. STD 1: 1 LINE PHONEMAIL PICKUP " |
+-----+---------+--------------------------------------------------------------+
| 98 | OPTIT12 | "12 KEYS U.S. STD 2: 2 LINE MB " |
+-----+---------+--------------------------------------------------------------+
| 99 | OPTIT12 | "12 KEYS U.S. STD 3: 2 LINE ACD AGENT PHONEMAIL " |
+-----+---------+--------------------------------------------------------------+
| 100 | OPTIT12 | "12 KEYS U.S. STD 4: 2 LINE ACD SUPERVISOR " |
+-----+---------+--------------------------------------------------------------+
| 101 | OPTIT12 | "12 KEYS U.S. STD 5: 1 LINE DDS " |
+-----+---------+--------------------------------------------------------------+
| 102 | OPTIT12 | "12 KEYS U.S. STD 6: 2 LINE INTERCOM " |
+-----+---------+--------------------------------------------------------------+
+-----+---------+--------------------------------------------------------------+
| 104 | OPTIT12 | "12 KEYS U.S. STD 8: 1 LINE PHML (1 KEU: DDS) " |
+-----+---------+--------------------------------------------------------------+
| 105 | OPTIT12 | "12 KEYS U.S. STD 9: 1 LINE PHML (1 KEU: EXECUTIVE)" |
+-----+---------+--------------------------------------------------------------+
| 106 | OPTIT12 | "12 KEYS U.S. STD 10: 1 LINE PHML (1 KEU: LINES) " |
+-----+---------+--------------------------------------------------------------+
| 107 | OPTIT12 | "12 KEYS U.S. STD 11: ACD SUPERVISOR (KEU) " |
+-----+---------+--------------------------------------------------------------+
| 108 | OPTIT12 | "12 KEYS U.S. STD 11: ACD SUPERVISOR (KEU) " |
+-----+---------+--------------------------------------------------------------+
84
EN4401EN00EN_0005
© 2005 Siemens AG
14.3 REGENERATE-TAPRO
This function is used to output a command batch with the following information:
1. all valid standard key layouts and all loaded key layouts for all stations with digital terminals.
2. specific standard key layouts.
3. key layouts loaded at specific stations.
For 1 and 3, the parameters are only output for those terminals whose key function alloca-
tion differs from the standard key layout.
Example
1. Regenerate standard key layout 0 for optiset.
Input:
REGENERATE-TAPRO:TYPE=STD,STD=0,DIGTYP=OPTISET;
Output:
CHANGE-TAPRO:,0,OPTIT8,MB,ST,RLS,FWD,CDK,SNR,CONS,SPKR,,,,,,,,,,,,"8 KEYS I.M. STD
0: ENTRY 8";
CHANGE-
TAPRO:,0,OPTIA1,VACANT,VACANT,VACANT,VACANT,VACANT,VACANT,VACANT,VACANT,VACANT,VAC
ANT,VACANT,VACANT,VACANT,VACANT,VACANT,,,,,;
CHANGE-
CHANGE-
CHANGE-
2. Regenerate the functions which differ from standard for stations 3154 to 3200.
Input:
REGENERATE-TAPRO:TYPE=STN,STNO=3154&&3200;
Output :
CHANGE-TAPRO:2190,,OPTISET,,,,VACANT,,,,,,DOOR,SPKR,,,,,,,,,;
CHANGE-TAPRO:2191,,OPTISET,MB,ST,SNR,,VACANT,,,,,,,,,,,,,,,;
CHANGE-TAPRO:2193,,OPTISET,,CONS,,,,,,MB,,,,,,,,,,,,;
CHANGE-TAPRO:2193,,OPTIA3,,,,,,,,,,,,SNR,,,,,,,,;
CHANGE-TAPRO:2194,,OPTISET,,CONS,,,,,,MB,,,,,,,,,,,,;
CHANGE-TAPRO:2194,,OPTIA2,,,,,,,,,DR,,,,,,,,,,,;
CHANGE-TAPRO:2194,,OPTIA4,,,,,,,,DOOR,,,,SNR,,,,,,,,;
85
EN4401EN00EN_0005
© 2005 Siemens AG
The key layout is regenerated for all terminals whose station numbers lie within the specified
range of 3154 to 3200, regardless of the terminal type, and whose key layout differs from stan-
dard.
3. Regenerate the key layouts which differ from standard for all optiset terminals with stand-
ard 0.
Input:
REGENERATE-TAPRO:TYPE=STN,STD=0,DIGTYP=OPTISET;
Output:
CHANGE-TAPRO:2191,,OPTISET,MB,ST,SNR,,VACANT,,,,,,,,,,,,,,,;
CHANGE-TAPRO:3500,,OPTIA2,CBK,,,,,,,,,,,,,,,,,,,;
All digital optiset terminals with the specified standard key layout, and whose key layout differs
from standard, are output according to station number.
86
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: ZIEL - Destination Addresses for Stations
15 ZIEL - Destination Addresses for Stations

This AMO is used to enter, interrogate or regenerate destinations in the database (DB) for the
following features:
● Call forwarding - fixed (FWD)
● Messenger Call (MSGR)
● Direct station select keys (DSS)
● Name/repertory key (NAME)
● Individual speed dialling (SPDI)
● Saved Number Redial (SNR)
● Attendant Console Direct Destination Select keys (DDS)
● Destinations for the BUZZ Feature
AMO-ZIEL is also used to add, delete, interrogate or regenerate for:
● dialing external servers to deposit messages
● identifying external servers when retrieving messages with the START key
Call forwarding - fixed

Two forwarding variants are possible:
● STATION forwarding
can be added or deleted by AMO ZIEL or by the subscriber, and activated or deactivated
by the subscriber or by AMO ACTDA.
● SYSTEM forwarding is a new forwarding type
Adding and deleting destinations is only possible by AMO ZIEL, whereby different destina-
tions can be entered for different forwarding types (eg.busy, no response), immaterial, if the
incoming call is internal or external. The forwarding can be activated or deactivated by
AMO ACTDA, or by the subscriber using the relevant codes.
● Call forwarding on no response
The fixed call forwarding destinations do not act ad destinations for call forwarding on no
response any more. These can be added as fixed destinations for forwarding type CFNR
(no response) or CFB (busy) in the SYSTEM forwarding (AMO ZIEL), and activated by
AMOACTDA, or can be added and activated as variable forwarding (CFNR or CFB) (AMO
ACTDA).
87
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: ZIEL - Destination Addresses for Stations Siemens
Fixed destinations can be created for each service. This AMO however does not activate or de-
activate forwarding. Destinations can be entered in the services VCE (voice), FAX and DTE.
Destinations for devices working to the DSS1 protocol can only be activated as variable for-
warding destinations by AMO ACTDA.
Destinations can be entered for all created STNOs (station numbers) with the exception of at-
tendant terminals, irrespective of whether or not the station concerned has any terminal devic-
es.
The following diversion types can be used:
for SYSTEM forwarding
● CFU (Call Forward Unconditional)
● CFB (Call Forward Busy)
● CFNR (Call Forward No Reply)
● CFDND (Call Forward Do Not Disturb)
for STATION forwarding
● CFU (Call Forward Unconditional)
At the system forwarding it is distinguished, whether it is operative for internal or external calls.
Destinations can be entered for all added phone numbers except attendant consoles, immate-
rial, if a device is installed or not.
The following destinations are allowed:
● Existing station numbers and hunting group masters for each service
● Personal attendant call numbers
● General attendant call numbers
● Specific hunting groups
● PSs (paging systems, also ’code calling’ systems)
● Voice mailboxes
● Announcements via TMOM (adapter set for special equipment)
● External destinations
● ACD (automatic call distribution) DNIS (dialed number identification service) routing num-
ber
Destinations are not checked any more, except for few cases. To external destinations a name
can be assigned.
More informations about call forwarding can be found in the service handbook.
88
EN4401EN00EN_0005
© 2005 Siemens AG
Messenger Call
The members of an integrated executive/secretary system can have a messenger call key on
their voice terminal for which a fixed destination can be entered. This destination can also be
programmed at the administration and maintenance terminal. Only analog stations are permit-
ted.
Direct station select keys

Direct station select (DSS) keys can be assigned to all terminals.
The key functions for OPTISET and Optipoint 500 are defined with the help of the AMO TAPRO.
Only internal destinations are possible (analog telephone, digital voice terminal, and personal
attendant call number).
In addition to entering the destination in the database, the AMO ZIEL also enters partner infor-
mation for the destination station (controls the lamps in the DSS key).
Name/repertory key
The key functions for the OPTISET and Optipoint 500 are defined with the help of the AMO
TAPRO. Destinations can only be entered after the key functions have been defined. The des-
tination entry may be any combination of digits comprising a maximum of 22 characters.
Destination entries may be protected against changing and deleting by the destination terminal
user, using parameter PROTECT=YES. Changing or deleting by AMO will be possible further-
more.
Name/repertory keys of OPTISET / Optipoint 500 add on terminals have two levels to store des-
tination entries. A level can be selected by entering a value for parameter LEVEL.
Individual speed dialling

Stations that are permitted to use the SPDI are provided an SPDI list when created by means
of AMO SBCSU. Stations with an analog telephone, a voice terminal, mobile users (without a
device, but with a separate terminal connection), and DTE stations may use the SPDI. Voice
terminals can also used name/repertory keys and DSS keys.
Saved Number Redial

Each analog telephone and voice terminal can store a dialed number with up to 22 digits for
redial. The destination can be any combination of digits (0-9,*,#,A,B,C,D).
Attendant Console Direct Destination Select keys

Each attendant console has 42 destination (DDS) keys
● 40 destinations via the destination keys
● 2 destinations via R1, R2 keys (trunk group keys for reserving lines).
89
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: ZIEL - Destination Addresses for Stations Siemens
The destinations are entered into a storage area that can hold up to 42
The configuration is carried out when the attendant console is created by means of AMO AC-
SU.
The destination keys write memory locations 1-40, while the trunk group keys R1 and R2 are
always defined at locations 41 and 42.
Destinations for the BUZZ Feature

The buzz feature allows a user to alert (buzz) a predefined keyset or DFT (Optiset and Optipoint
500) by pressing the BUZZ key or by keying an access code. Voice communication is not pos-
sible. Buzz causes the target keyset or DFT to be alerted and the originator’s station number
to be displayed for two seconds. The buzz target (destination) and the originator must be locat-
ed in the same node.
15.1 ADD-ZIEL
Example
A fixed call forwarding destination for diversion type CFNR to STNO 3101 for the VOICE service
can be created for voice station 2100.
Input:
ADD-ZIEL:TYPE=FWD,SRCNO=2100,SI=VCE,DESTNOF=3101,DTYPE=CFNR,ITYPE=GEN
,CFVAR=SYSTEM;
15.2 DISPLAY-ZIEL
Example
Interrogate the call forwarding destination for station 2100.
Input:
DISPLAY-ZIEL:TYPE=FWD,SRCNO=2100;
Output:
FWD
SOURCE | SERVICE | DTYPE | ITYPE | CFVAR | DESTINATION
-------+----------+-------+---------+---------+-----------------------
2100 | VCE | CFU | INT | SYSTEM | 3140
90
EN4401EN00EN_0005
© 2005 Siemens AG
15.3 REGENERATE-ZIEL
Example
Regenerate the call forwarding destination for station 2100.
Input:
REGENERATE-ZIEL:TYPE=FWD,SRCNO=2100;
Output
ADD-ZIEL :FWD,2100,VCE,2100,VCE,3101,,CFNR,GEN,SYSTEM;
91
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: ACTDA - Activation of User Features Siemens
16 ACTDA - Activation of User Features

The AMO ACTDA is used to regenerate feature-specific data entered by a user via the terminal.
The functions DISPLAY, REGENERATE, ADD and DELETE are implemented. The AMO en-
ables these data to be saved while the software version (APS) is being changed.
Using the DISPLAY function, the user data recorded by ACTDA can be displayed on the admin-
istration and maintenance terminal.
A command batch is generated with the REGENERATE function, based on the user data. This
command batch is used for reinitializing the database.
The ADD function initializes the database with the user data.
The AMO ACTDA is used mainly for regenerating data. In addition, it can be used for test pur-
poses.
In special cases it can be necessary to deactivate the acivated call forwarding of a station. This
function has been implemented in the branch DELETE.
TYPE Feature
STN DND Do-not-disturb
FWD Fixed call forwarding
Variable call forwarding
OPTISET individual optiset E / optipoint 500 settings
OUTHUNT switch out of hunt group
RCUTOFF Ringer Cutoff
REMIND Timed reminder
REPSECR Deputy for secretary
RNGXFER Ring transfer
VCR Voice call rejection
ATNDGR NOPT Night variant for ATNDGR
ITR DNDGR Group do-not-disturb function
ISTR Controlled station-to-station restriction
Controlled station-to-station restriction for all ISTR groups
MOBHFA MLOGOFF Logoff of mobile hfa-user
MLOGON Logon of mobile hfa-user
92
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: ACTDA - Activation of User Features
Some user data is already administrated by other AMOs. These data are not additionally ad-
ministrated by ACTDA.
AMO Feature-specific data
CHESE Secretarial transfer function destinations
ZIEL Individual speed dialing numbers
Call numbers for stored number redial
Name/repertory key data for DIGITEs
DSS (direct station selection) destinations
Messenger call destinations
Name/repertory key data for ATNDs
TAPRO Store key functions for DIGITEs
BERUM Data for class-of-service changeovers (individual, group, all)
16.1 ADD-ACTDA
Create the feature-specific user data in the database.
Note:
If no entry is made for parameter ACT in the branch ATNDGR, the entered night option will be
preselected, but not activated.
Examples
1. Enter a variable call-forwarding destination (and activate) and enter a timed reminder for
STN 62850.
Input:
ADD-ACTDA:STN,62850,FWD,STATIONV,CFU,GEN,VCE,63627;
ADD-ACTDA:STN,62850,REMIND,01130;
2. Activate night option 3 for ATND group 2.

Input:
ADD-ACTDA:ATNDGR,2,3,ACT;
Output:
H04 : NIGHT SWITCH FOR ATND GROUP 2 ACTIVATED.
93
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: ACTDA - Activation of User Features Siemens
16.2 DELETE-ACTDA
Deactivate the features FWD and ’Voice Call Rejection’ for a station.
Example 1
Deactivate FWD for station 250123 in service FAX.
Input:
DELETE-ACTDA:STN,250123,FWD,,,,FAX;
16.3 DISPLAY-ACTDA
Interrogate the feature-specific data in the database for a specific station, ITR groups, or ATND
groups.
Examples
1. Display the features for the stations 250200 to 250220.
Input:
DISPLAY-ACTDA:STN,250200&&250220;
Output:
+--------------------------------------------------------------------+
| STATION NUMBER 250200 |
+--------------------------------------------------------------------|
| DIVERSION : |
| DESTINATION NUMBER | CFVAR | DTYPE | ITYPE | SI |
| | | | | |
+------------------------+----------+----------+----------+----------+
| 250201 | STATIONV | CFBNR | GEN | VCE |
+------------+-----------+----------+----------+----------+----------+
| DO NOT | VOICE CALL| RING | REP. | REMIND | RINGER- |
| DISTURB | REJECT | XFER .| SECR. | HH:MM | CUTOFF |
+------------+-----------+----------+----------+----------+----------+
| | x | | | 11:00 | |
+------------+-----------+----------+----------+----------+----------+
| INDIVIDUAL SETTINGS FOR OPTISET AND OPTIPOINT 500: |
| RINGVOL : 3 RINGSOUN: 5 ALERTVOL: 3 CALLVOL: 3 |
| SPKRVOL : 2 ROOMCHAR: NORMAL |
+--------------------------------------------------------------------+
+--------------------------------------------------------------------+
+--------------------------------------------------------------------+
| DIVERSION : |
| DESTINATION NUMBER | CFVAR | DTYPE | ITYPE | SI |
| | | | | |
94
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: ACTDA - Activation of User Features
+------------------------+----------+----------+----------+----------+
| 08972247230 | STATIONV | CFU | EXT | VCE |
| 03038652226 | STATIONV | CFU | GEN | FAX |
+------------+-----------+----------+----------+----------+----------+
+------------+-----------+----------+----------+----------+----------+
| | x | | | 11:00 | |
+------------+-----------+----------+----------+----------+----------+
+--------------------------------------------------------------------+
| SWITCHED OUT OF HUNT GROUP IN SERVICE: VCE |
+------------+-----------+----------+----------+----------+----------+
+--------------------------------------------------------------------+
+------------+-----------+----------+----------+----------+----------+
+------------+-----------+----------+----------+----------+----------+
| | x | | | 11:00 | |
+------------+-----------+----------+----------+----------+----------+
+--------------------------------------------------------------------+
16.4 REGENERATE-ACTDA
Example
Regenerate the feature-specific data in the database.
Input:
REGENERATE-ACTDA;
Output:
ADD-ACTDA:STN,62850,FWD,STATIONV,CFBNR,GEN,VCE,636271154;
ADD-ACTDA:STN,62850,REMIND,01130;
ADD-ACTDA:ITR,,DNDGR;
95
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: SDAT - Administration of Individual Subscriber Attributes and Siemens
17 SDAT - Administration of Individual Subscriber

Attributes and General Subscriber Data
The AMO SDAT can be used to administer subscriber-related attributes and features for the
voice service. It can process subscribers who have been added with the AMO SCSU, SBCSU,
or SBCSU.
It can also be used to administer general data that is independent of any particular device.
17.1 CHANGE-SDAT
17.1.1 Changing Attributes / Features

When attributes are changed (added / removed), compatibility checks are carried out to test the
following:
a) whether the attributes entered - or those already existing - are compatible with each
other,
b) whether the attributes entered are compatible with the type of equipment belonging to
the subscriber,
c) whether the attributes entered are compatible with special subscriber data
When attributes are added for ACD SUPERVISOR a check is carried out to establish whether
there are sufficient purchased subscribers of this type.
When an ACD attribute is removed, a check is carried out to establish whether there are still
ACD group relationships.
17.1.2 Changing General Subscriber Data (Branch DATA)

In this branch, it is possible to change general subscriber data that is independent of any
device. This data consists of parameters that are processed in the AMO SBCSU and in the
AMO SCSU and SSCSU.
The checks correspond to the checks in the AMO with which the subscriber being changed was
added.
17.1.3 Changing Subscriber Data (Branch DATA1)

In this branch, it is possible to change additional subscriber data. This data consists of param-
eters that are processed with AMO SDAT only. AMO SBCSU, SCSU and SSCSU can not pro-
cess this data.
96
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: SDAT - Administration of Individual Subscriber Attributes and
17.2 DELETE-SDAT
The action DELETE-SDAT can be used to delete specific subscriber attributes which were con-
figured with CHANGE-SDAT, TYPE=DATA1.
PUBNUM
When deleting PUBNUM the parameters TON and NPI are deleted, too.
17.3 DISPLAY-SDAT
The action DISPLAY-SDAT results in the following:
1. In the branch SUBDATA
the general subscriber data and the subscriber-related attributes / features of a subscriber
are output in tabular form.
2. In the branch SUBFIND
subscribers with a particular subscriber-related attribute / feature are output in tabular
form.
3. In the branch SUBOV
the assigned device and the AMO used to add the subscriber are output in tabular form for
the subscribers entered.
4. In the branch NNOFIND
subscribers with a particular NNO are output in tabular form.
Example 1
Input:
DISP-SDAT:2100,SUBDATA;
Output:
--------------------------- SUBSCRIBERDATA ----------------------------
STNO = 2100 COS1 = 22 DPLN = 0 SSTNO = NO
PEN : 1- 1- 25- 0 COS2 = 1 ITR = 7 TRACE = NO
DVCFIG : ANATE LCOSV1 = 1 COSX = 0 ALARMNO = 0
AMO : SCSU LCOSV2 = 1 SPDI = 10 RCBKB = NO
KEYSYS: LCOSD1 = 1 SPDC1 = 0 RCBKNA = NO
LCOSD2 = 1 SPDC2 = 1
-----------------------------------------------------------------------
CDRACC =
97
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: SDAT - Administration of Individual Subscriber Attributes and Siemens
SRCGRP = (1) CLASSMRK =

PUBNUM = TON = NPI =
KNNR = 1-1-15 HOTIDX =
--------------------------- ATTRIBUTES -----------------------------
AGENT AUTOLOG NORELOC
Example 2
Input:
DISP-SDAT:2100&&2120,SUBFIND,AGENT;
Output:
-------------------------------------------
STNO DVCFIG AMO CDRACC NNO
-------------------------------------------
2100 ANATE SCSU 1-1-15
Example 3
Input:
DISP-SDAT:2100&&2110,SUBOV;
Output:
STNO = 2100 DVCFIG: ANATE AMO: SCSU
--------------------------------------------
STNO DVCFIG AMO CDRACC NNO
--------------------------------------------
2100 ANATE SCSU 1-1-15
2101 ANATE 1-1-15
2102 ANATE 1-1-15
2103 ANATE 1-1-15
2104 ANATE 1-1-15
2105 ANATE 1-1-15
2106 ANATE 1-1-15
98
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: SDAT - Administration of Individual Subscriber Attributes and
17.4 REGENERATE-SDAT
The action REGENERATE-SDAT can be used to restrict the output to subscribers with
particular subscriber-related attributes / features.
Example:
Input:
REGEN-SDAT:2190,ATTRIBUT;
Output:
CHANGE-SDAT:2190,AATTR=AGENT&AUTOLOG&DNDSR&CBSTMON;
99
EN4401EN00EN_0005
© 2005 Siemens AG
Administration: PERSI - Personal Identification Siemens
18 PERSI - Personal Identification

The AMO PERSI is used to administer personal data. The cross-reference to the person is in-
variably established via the station number.
a) Names
Each station number can be assigned either one or several (any number of) names;
the name entered first will be displayed on DIGITE displays. All other names are used
for ETD functions. The name can also be made up of 2 parts:
1. Surname, simple or composite, e.g. Hr. Meier, Fr. Dr. Huber
2. Name, and additional information, e.g. Anna, Dept. A3
The characters of the "surname" are separated from those of the "name" by
means of a "*".
Digitedisplay: The DIGITE has a 24-character display. The type of display, e.g. station
number plus name or name only is defined by means of AMO ZAND, TYPE=ALLDATA,
DISPMODE-MODE1 to MODE5 (see examples). There is no verification of the last
name. The number of blanks between the station number and the name is exactly one.
Examples
Input: Dr. v. Ritter*Martin
Display
MODE1: 32857 DR. V. RITTER M.
MODE2: 32857
MODE3: DR. V. RITTER MARTIN
MODE4: DR. V. RITTER
MODE5: # DR. V. RITTER
b) Organizational unit
Each name can be assigned an organizational unit (for ETD functions).
If a station number has not been assigned a name, no org. unit can be assigned.
If station number has been assigned several names, but not everyone of these names
has been assigned an organizational unit, the organizational unit which was assigned
last is automatically assigned to the remaining names.
c) Personal identification number (PIN)
The PIN is used for personal identification of a person to the system. Each station
number can be assigned any number of PINs. The length of a particular PIN type is
determined centrally. The PIN length may or may not be the same for the types of PINs
described above. Each PIN (except COSXCD) must be unique throughout the system.
100
EN4401EN00EN_0005
© 2005 Siemens AG
Siemens Administration: PERSI - Personal Identification
The "class of PIN" (COPIN) is used for each PIN type in order to implement the PIN display
feature and in order to distinguish between the different PIN types.
The characteristics of the COPINs (1 through 15) are summarized in the so-called COPIN table
in which the following default values are assigned to the type of PIN:
PINTYPE PIN COTYPE PIN Meaning of a type of PIN

(COPIN)
1 = PIN1 MOBILE Manual identification
2 = PIN2 BUSLONG Identification of business calls (remains active until
manual deletion or timeout).
3 = PIN3 BUSSHRT Identification of business calls
4 = PIN4 PRIVSHRT Identification of private calls
5 = PIN5 PCODE Identification of a project for a call (project code =
PCODE).
6 = PINC PINCARD Identification by means of a magnetic/chip card which is
inserted into the card reader of the terminal.
7 = COSXCD COSXCD Identification of users which are authorized to activate
COS changeover from the terminal.
8 = SI SI Pin for service id
9 = CDRAC PCODE CDR account code
10 = PIN10 PCODE PIN for dialing pattern check
18.1 ADD-PERSI
1. Definition of general PIN data
Create length of pins for each PIN type.
Create pin-display for each PIN type.
Create class of service changeover to COS2 with COSXCD.
Create number of failed attempts to enter the pin
2. Assigning a company code to an ITR group
3. Assigning the name and PIN to the STNO; assigning org. unit to name.
4. STNO-Code calling number conversion for CCMS.
If a range of station numbers is to be specified, the parameter ALLOC can be used to de-
termine whether the specified code calling number is to be assigned to all station numbers
101
EN4401EN00EN_0005
© 2005 Siemens AG
(ALLOC=SAME) or whether, starting with the specified code calling number, each station
number is to be assigned a new code calling number in ascending order (ALLOC=AS-
CEND).
5. Create project code (PCODE)
6. Create service id (SI)
7. Create account code (CDRAC)
Examples
1. Create the length of the personal ID number (card) (=8) and the pointer to the personal ID
number (card) (=7) (the manual personal ID numbers and the codes for class of service
changeover remain blocked).
Input:
ADD-PERSI:TYPE=SYS,PINCLEN=8,PINPOINT=7;
2. Create the personal ID number (card) for directory number.3123

Name=Schmidt MEIER*JUERGEN
PINC- No. 6000006, organizational unit=PN KD3
Input:
ADD-PERSI:TYPE=STN,STNO=3123,NAME=SCHMIDT MEIER*JUERGEN,
PINC=60000006,,,ORG-PN KD3;
3. Create a STNO-Code calling number allocation for CCMS with code *7, with station
number range 2500-2520, with code calling number 300 to be allocated in ascending order.
Input:
ADD-PERSI:TYPE=CCMS,CCMSCD=*7,STNO=2500&&2520,CCNO=300,ALLOC=ASCEND;
4. Create the pin display for pin type 1 and 3

Input:
ADD-PERSI:TYPE=SYS,PINDISP=1&3;
5. Create a project code

Input:
ADD-PERSI:TYPE=PCODE,PCODE=600600;
6. Create the same pin for pinc and pin1 (length of pinc, pin1 and pin4=8)
Input:
ADD-PERSI:TYPE=STN,STNO=2100,PINC=21000000,PIN1=21000000,PININDIV=YES;
102
EN4401EN00EN_0005
© 2005 Siemens AG
18.2 CHANGE-PERSI
1. Change the length entries for each pin type. Any type of PIN can be deactivated by speci-
fying "0" as PIN length.
(this is only possible if the relevant PINs have not been created already)
2. Change the pointer indicating the card personal ID number
3. Change the company code or the pointer indicating the company code
4. Change one of the assigned names
5. Change one of the assigned ORG entries. This entry will be automatically changed for all
names to which it is assigned.
6. Change one of the assigned ORG entries for all names assigned to the specified station
number(s).
7. Change one of the assigned ORG entries for a specific name.
8. Change specific codes
(OLDCODE and NEWCODE must be of equal length)
If the same COSXCD is assigned to several different station numbers, the code can be
changed only for the station concerned by specifying the station number. If the station
number is omitted, the code will be changed for all station numbers.
9. Change the code-calling number associated with a registered station number for a partic-
ular CCMS.
10. Change the COPIN in the COPIN table
11. Change the modulo check algorithm
Notes:
CHANGE-PERSI:TYPE=ORGSYS or TYPE=ORGSTNO:
If several OLDORGs are to be changed to a NEWORG (new organizational unit), the NEWORG
must be specified only once. All remaining OLDORGs will then be assigned this NEWORG.
CHANGE-PERSI:TYPE=ORGNAME:
If a NEWORG is to be allocated for several names (change existing ORG to another), then the
NEWORG need be entered only once. All remaining names are then allocated the new orga-
nizational unit.
CHANGE-PERSI:TYPE=NAME:
If the first name (i.e. the name which is displayed on the screen) is to be changed, the param-
eter OLDNAME can be omitted and the name which used to be the first name is overwritten
with the first NEWNAME.
103
EN4401EN00EN_0005
© 2005 Siemens AG
CHANGE-PERSI:TYPE=PIN:
If the same COSXCD is assigned to several different stations, the STNO parameter needs to
be specified only when changing the COSXCD.
Examples
Assignment of station number.3109 designated ’FLIERL*GABI’ to a new organizational unit
designated ’PN V8332’.
Input:
CHANGE-PERSI:TYPE=ORGNAME,STNO=3109,NAME=FLIERL*GABI,NEWORG=PN V8332;
18.3 DELETE-PERSI
1. All assigned company codes are deleted for the specified traffic relation groups.
2. Delete all name entries (NAME and ORG) of a station DN
3. Delete Name(s) and ORG allocated to a station DN
4. Delete the specified ORG for all assigned names.
5. Delete all ORG units which are assigned to all names of a station number.
6. Delete the ORG unit which is assigned to a specific name of a station number.
7. Delete all codes indicated
Only for the PIN types specified under PINTYPE, or for all PIN types if the parameter is not
specified.
If the same COSXCD is assigned to several different station numbers, the code can be de-
leted only for the station concerned by specifying the station number. If the station number
is omitted, the code will be deleted for all station numbers.
8. Delete the codes assigned to the station numbers specified
Only for the PIN types specified under PINTYPE, or for all PIN types if the parameter is not
specified.
9. Delete station(s) from STNO/CCNO table for a particular CCMS.
Note
When NAMES or an organizational units which have been assigned to NAMES are deleted, the
surname and the name (but not any additional information) are compared with the station num-
ber entry.
The NAME may be abbreviated. Care should, however, be taken to specify as many letters as
104
EN4401EN00EN_0005
© 2005 Siemens AG
necessary to ensure that a specific station number entry is unique (see example of input).
If several entries of the same name exist for the same station number, the first of these entries
will be deleted.
Examples
1. Delete name ’RICCATO*’ from directory no.3100
Input:
DELETE-PERSI:TYPE=NAME,STNO=3100,NAME=RICCATO*;
Output:
H01: NAME TO BE DELETED RICCATO IS ONLY NAME FOR
ORG : ORG IS DELETED
2. Delete pin 12345678

Input:
DELETE-PERSI:TYPE=pin,pin=12345678;
3. The personal ID numbers (card) assigned to station number 7580 are to be deleted
DELETE-PERSI:TYPE=STN,STNO=7580,PINTYPE=6;
4. Delete the PINs, names and ORG assigned to station 2100.

Input:
DELETE-PERSI:TYPE=ALLNAME,STNO=2100;
DELETE-PERSI:TYPE=TLN,STNO=2100;
18.4 DISPLAY-PERSI
1. Interrogation of general personal ID data
(PIN length and pointer, COCO and pointer)
(Pin display for each pin type and class of service changeover)
2. Display the names and the assigned ORG for the specified/all station numbers.
3. Display PIN for all station numbers or for the specified station number(s).
4. Interrogation of STNO/CCNO entries for a particular CCMS.
5. Display the specified/all PINs for the specified/all pin types.
6. Display the specified/all COPINs of the COPIN table
7. Display all modulo check algorithms
105
EN4401EN00EN_0005
© 2005 Siemens AG
Examples
Interrogating the general PERSI data.
Input:
DISPLAY-PERSI:TYPE=SYS;
Output:
+---------------------------------------------+
| COPIN |
| 1 PIN1LEN 10 |
| 2 PIN2LEN 8 |
| 3 PIN3LEN 6 |
| 4 PIN4LEN 10 |
| 5 PIN5LEN 6 |
| 6 PINCLEN 8 PINPOINT 10 |
| 7 COSLEN 4 COSXCOS2 N |
| 8 SILEN 10 |
| 9 CDRACLEN 5 COSXCOS2 N |
| 10 PIN10LEN 4 |
| 11 PIN11LEN 2 |
| 12 PIN12LEN 2 |
| 13 PIN13LEN 2 |
| 14 PIN14LEN 2 |
| 15 PIN15LEN 2 |
| |
| ATTEMPTS 5 (NUMBER OF FAILED ATTEMPTS)|
| |
| ITR COCO CPOINT |
| 04 SIE 4 |
| 06 SIE 4 |
| 07 AGFA 8 |
| 08 BMW 6 |
+---------------------------------------------+
8. Interrogation of personal ID of station nos. 3100 to 3104

Input:
DISPLAY-PERSI:TYPE=NAME,STNO=3100&&3104;
Output:
+--------+---------------------------------+--------------------------+
| STNO | CHRISTIAN AND SURNAME | ORGANIZATIONAL UNIT |
+--------+---------------------------------+--------------------------+
| 3100 | RICCATO* | |
| 3101 | BINDER* | PNEA 41 |
| 3102 | DUMONT* | |
| 3103 | BULLE* | |
| 3104 | TEAM ASSISTANT* | |
+--------+---------------------------------+--------------------------+
106
EN4401EN00EN_0005
© 2005 Siemens AG
9. Interrogation of directory numbers of card personal ID numbers 12345678, 23456789 and

20007777
Input:
DISPLAY-PERSI:TYPE=PIN,PIN=12345678&23456789&20007777
Output:
+--------------+--------+------------------------------------+
| PIN | STNO | PINTYPE |
| | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15|
+--------------+--------+------------------------------------+
| 12345678 | 7580 | X . . . . X . . . . . . . . . |
| 23456789 | 4500 | X . . . . X . . . . . . . . . |
| 20007777 | 7580 | X . . . . X . . . . . . . . . |
+--------------+--------+------------------------------------+
10. Interrogation of card personal ID numbers to station numbers 4700 and 5600
Input:
DISPLAY-PERSI:TYPE=STN,STNO=4700&5600,PINTYPE=6;
Output:
+--------+-----------+------------------------------------+
| STNO | PIN | PINTYPE |
| | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15|
+--------+-----------+------------------------------------+
| 4700 | 10000009 | . . . . . X . . . . . . . . . |
| 5600 | 12345678 | X . . . . X . . . . . . . . . |
| 5600 | 23456789 | X . . . . X . . . . . . . . . |
+--------+-----------+------------------------------------+
11. Interrogation of specified pin types.

Input:
DISPLAY-PERSI:TYPE=PIN,PINTYPE=1&3&5;
Output:
+--------------+--------+------------------------------------+
| | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15|
+--------------+--------+------------------------------------+
| 1111 | 4711 | X . X . . . . . . . . . . . . |
| 1234 | 4712 | X X X . . . . . . . . . . . . |
| 12345 | ---- | . . . . X . . . . . . . . . . |
+--------------+--------+------------------------------------+
107
EN4401EN00EN_0005
© 2005 Siemens AG
12. Interrogation of the pin 4444444.

Input:
DISPLAY-PERSI:TYPE=PIN,PIN=4444444;
Output:
+--------------+--------+------------------------------------+
| | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15|
+--------------+--------+------------------------------------+
| 4444444 | 4712 | . . . . . . X . . . . . . . . |
+--------------+--------+----------------------------------+
13. Interrogation of all pins with the assigned station number 4711
Input:
DISPLAY-PERSI:TYPE=STN,STNO=4711;
Output:
+--------+--------------+------------------------------------+
| STNO | PIN | PINTYPE |
| | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15|
+--------+--------------+------------------------------------+
| 4711 | 1111 | X . X . . . . . . . . . . . . |
| | 22222 | . . . X . . . . . . . . . . . |
+--------+--------------+------------------------------------+
14. Interrogation of all COPINs of the COPIN table

The example shows the initialisation of the COPIN table.
Input:
DISPLAY-PERSI:TYPE=COPIN;
Output:
+-------+-------------------------------------------------+
| COPIN | COPIN-PARAMETER |
+-------+-------------------------------------------------+
| 1 | COTYPE = MOBILE |
| | PINTEXT = ’MAN. PIN MOBILE USER’ |
| | PIN1LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
| | DISPRSTN = NO IDHOME = NO |
| | PINTEST = TABLE DISPID = PERMDISP |
| | TRKCD = 0 TRACE = NO |
| | TRKCDTYP = NO PINEXT = NO |
| | PINDUR = TIME DISPPIN = NO |
| | TRANSFER = ALL PINNKEY = NO |
| | DEACKEY = NO POSCHKN = 1 |
108
EN4401EN00EN_0005
© 2005 Siemens AG
| | COSHOME = NO PINLCOS2 = NO |
| | DPTEST = NO DISPTRKC = NO |
+-------+-------------------------------------------------+
| 2 | COTYPE = BUSLONG |
| | PINTEXT = ’BUSINESS PIN, LONG ’ |
| | PIN2LEN = 0 |
| | CDRTEXTS = YES |
| | CDRTEXT = ’+ 0 ’ |
| | DISPRSTN = YES IDHOME = NO |
| | PINTEST = TABLE DISPID = TIMEDISP |
| | PINDUR = PERM DISPPIN = NO |
| | TRANSFER = NO PINNKEY = NO |
+-------+-------------------------------------------------+
| 3 | COTYPE = BUSSHRT |
| | PINTEXT = ’BUSINESS PIN, 1 CALL’ |
| | PIN3LEN = 0 |
| | CDRTEXT = ’+ 1 ’ |
| | TRKCDTYP = UNICD PINEXT = NO |
| | PINDUR = ONE DISPPIN = NO |
+-------+-------------------------------------------------+
| 4 | COTYPE = PRIVSHRT |
| | PINTEXT = ’PRIVATE PIN, 1 CALL ’ |
| | PIN4LEN = 0 |
| | CDRTEXT = ’+ 2 ’ |
| | TRKCDTYP = UNICD PINEXT = NO |
| | PINDUR = ONE DISPPIN = NO |
+-------+-------------------------------------------------+
| 5 | COTYPE = PCODE |
| | PINTEXT = ’PROJECT CODE, 1 CALL’ |
| | PIN5LEN = 0 |
| | CDRTEXTS = NO |
109
EN4401EN00EN_0005
© 2005 Siemens AG
| | CDRTEXT = ’ ’ |
| | PINTEST = LENGTH DISPID = PERMDISP |
| | TRKCDTYP = NO PINEXT = YES |
| | PINDUR = ONE DISPPIN = YES |
+-------+-------------------------------------------------+
| 6 | COTYPE = PIN CARD |
| | PINTEXT = ’ID CARD, MOBILE USER’ |
| | PINCLEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
| | TRKCD = - TRACE = NO |
| | PINDUR = PERM DISPPIN = NO |
+-------+-------------------------------------------------+
| 7 | COTYPE = COSXCD |
| | PINTEXT = ’COS SWITCHOVER CODE ’ |
| | COSLEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
| | TRKCD = - TRACE = NO |
| | PINDUR = - DISPPIN = NO |
+-------+-------------------------------------------------+
| 8 | COTYPE = SI |
| | PINTEXT = ’PIN FOR SERVICE ID ’ |
| | SILEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
| | PINDUR = - DISPPIN = NO |
110
EN4401EN00EN_0005
© 2005 Siemens AG
+-------+-------------------------------------------------+
| | PINTEXT = ’CDR ACCOUNT CODE ’ |
| | CDRACLEN = 5 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
| | PINTEXT = ’FAC, 1 CALL ’ |
| | PIN10LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
| | PIN11LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
| | PIN12LEN = 0 |
111
EN4401EN00EN_0005
© 2005 Siemens AG
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
| | PIN13LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
| | PIN14LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
| | PIN15LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
112
EN4401EN00EN_0005
© 2005 Siemens AG

+-------+-------------------------------------------------+
18.5 REGENERATE-PERSI
1. Regeneration of the general or of all general and individual user data for personal identifi-
cation, of the CCMS data, project codes and service ids.
2. Regeneration of the individual user data for personal identification.
3. Regeneration of project codes
4. Regeneration of service ids
5. Regeneration of CDR account codes
6. Regeneration of COPINs
7. Regeneration of modulo check algorithm
If no parameter is specified, all general and individual user data as well as all CCMS data is
regenerated for personal identification.
If parameter STNO is omitted, all names, organizational units, and PINs in the system are re-
generated.
1. Regenerate all entries
Input:
REG-PERSI:;
Output:
ADD-PERSI:CCMS,922,,33&2100
,2105,GLEICH;
ADD-PERSI:ALG,7,3,5,6,5,5,5,6,10,5,4,2,2,2,2,2,1&2,JA;
ADD-PERSI:STN,3110,"SCHMIDT*HANNES","ORG1","60231100"&"70244817",
,,,,,,,,,,,YES,;
ADD-PERSI:PCODE,"600600"&"606060",5;
ADD-PERSI:SI,"5005005005";
ADD-PERSI:CDRAC,12345;
CHANGE-PERSI:COPIN,1,MOBILE,"MAN. PIN MOBILE USER",NO,,NO,TA-

BLE,0,NO,TIME,ALL,NO,PERMDISP,NO,YES,YES,NO,NO,1,NO,NO,NO,NO;
CHANGE-PERSI:COPIN,2,BUSLONG,"BUSINESS PIN, LONG ",YES,"+ 0",YES,TA-
BLE,0,NO,PERM,NO,NO,TIMEDISP,NO,NO,NO,NO,NO,1,NO,NO,NO,NO;
CHANGE-PERSI:COPIN,3,BUSSHRT,"BUSINESS PIN, 1 CALL",YES,"+ 1",YES,TA-
113
EN4401EN00EN_0005
© 2005 Siemens AG
BLE,0,UNICD,ONE,NO,NO,TIMEDISP,NO,NO,NO,NO,NO,1,NO,NO,NO,NO;
CHANGE-PERSI:COPIN,4,PRIVSHRT,"PRIVATE PIN, 1 CALL ",YES,"+ 2",YES,TA-
BLE,0,UNICD,ONE,NO,NO,TIMEDISP,NO,NO,NO,NO,NO,1,NO,NO,NO,NO;
CHANGE-PERSI:COPIN,5,PCODE,"PROJECT CODE, 1
CALL",NO,,NO,LENGTH,0,NO,ONE,NO,NO,PERMDISP,NO,YES,YES,NO,NO,1,NO,NO,NO,NO;
CHANGE-PERSI:COPIN,6,,"ID CARD, MOBILE USER",NO,,NO,TABLE,,NO,,ALL,NO,PERM-
DISP,NO,NO,NO,NO,NO,1,NO,NO,NO,NO;
CHANGE-PERSI:COPIN,7,,"COS SWITCHOVER CODE ",NO,,NO,TABLE,,NO,,NO,NO,TIME-
DISP,NO,NO,NO,NO,NO,1,NO,NO,NO,NO;
CHANGE-PERSI:COPIN,9,,"CDR ACCOUNT CODE ",NO,,NO,LENGTH,0,NO,ONE,NO,NO,PERM-
DISP,NO,YES,YES,NO,NO,1,NO,NO,NO,NO;
CHANGE-PERSI:COPIN,10,PCODE,"FAC, 1 CALL ",NO,,NO,LENGTH,0,NO,ONE,NO,NO,PERM-
DISP,NO,YES,YES,NO,NO,1,NO,NO,NO,NO;
CHANGE-PERSI:MODULO,1,2-1-2-1-2-1-2-1-2-1-2-1,SUMPRO,10,1,COMPREM;
114
EN4401EN00EN_0005
© 2005 Siemens AG

Programmation Par Commandes AMOS ANG PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Programmation Par Commandes AMOS ANG PDF

Uploaded by

Copyright:

Available Formats

Siemens AMOs

15 ZIEL - Destination Addresses for Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

1 Access to the HiPath 4000

1.1 HiPath 4300/4500

Common Service Access for all Products

Access to Applications via Port-Server

1.2 HiPath 4000

Common Service Access for all Products

As a rule the SL200 receives an IP address from the customer

1.3 Access via the Customer LAN

It is necessary to restart the UW7 server after changing IP parameters.

1.4 AMO access via the HiPath 4000 Assistant

1.5 Direct AMO access via the customer LAN

Profil for the AMO access via the customer LAN

1.6 Direct AMO access via the Atlantic LAN

1.7 Direct AMO access via V.24

2 Syntax for AMO Input

ACTIVITY - FUNCTIONS PARAMETER NAME =PARAMETER VALUE

( ) EXPLANATORY TEXT PASSAGES

PARAMETER NAME = PARAMETER VALUE

PARAMETER NAME = <PARAMETER VALUE>

[PARAMETER NAME = <PARAMETER VALUE>]

& & STRING of INDIVIDUAL VALUES

2.1 Example of AMO Input

Command Code Parameter

2.2 AMO SYNTAX DETAILS

2.3 Selecting Important Verbs and Nouns

● AMO - code explained in the BCSU example

B board C configuration SU switching unit

3 Protection of software features (codeword)

3.1 Feature description

New hardware: Old hardware:

ComScendo CC-AP for AP Emergency

Remote Survivability Cordless E

Protection of software features

3.2 Codeword variants

Dongle resp. SIM card does not match to Codeword;

CODEW variants with dongle in HiPath 4000 V2.0

TYPE Description Dongle Sim Card

3.3 Codew description

Unit Description AMOs Parameter

Unit Description AMOs Parameter

3.4 Service information

3.5 Generation (example)

1. Customer Dongle / SIM (TYPE 1 - Codeword)

SALES UNIT COUNTERS

AMO-CODEW-111 CODEWORD FOR ADMINISTRATION LOCK IN SWU

1. Dongle / SIM with TYPE 2 - Codeword

SALES UNIT COUNTERS

AMO-CODEW-111 CODEWORD FOR ADMINISTRATION LOCK IN SWU

● Administration above and beyond the quantities purchased:

● Display codeword the test mode is expired:

SALES UNIT COUNTERS

AMO-CODEW-111 CODEWORD FOR ADMINISTRATION LOCK IN SWU

....(a component is marked if it was installed with the purchased

3.6 Relevant AMO

4.1 Switching and Configuration AMOs in the CC

LTG and LTU SLOT CIRCUIT

4.2 BCSU - Configuring Mounting Locations for Modules in the SWU

4.3 Functions of the AMO

• ADD-BCSU : Equip modules in the reference configuration

Assigning an IP gateway (STMI board for IPDA usage):

Modification of module data.