Administration PDF

Siemens Administration
Administration
Contents
1 HiPath 4000 Service Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 Syntax for AMO Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1 Example of AMO Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 AMO SYNTAX DETAILS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Selecting Important Verbs and Nouns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Extended Access Protection (Login) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1 System Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4 AMO authorizations in the HiPath 4000 V2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.1 ADP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.2 CC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5 Log Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.1 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.2 Log Book Virtual Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.3 Data Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.4 Evaluation of the Log Book Data with the LOGBK AMO . . . . . . . . . . . . . . . . . . . . . . 31
6 Administration Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.1 Switching and Configuration AMOs in the CC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.2 BGDAT - Display the Board Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.3 Switching AMOs for the SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
7 BCSU - Configuring Mounting Locations for Modules in the SWU . . . . . . . . . . . 40
7.1 ADD-BCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7.2 CHANGE-BCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.3 DELETE-BCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
1
EN4402EN00EN_0003
© 2004 Siemens AG
Administration Siemens
7.4 DISPLAY-BCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
7.5 REGENERATE-BCSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
8 Protection of software features (codeword) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.2 Codeword variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8.3 Codew description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
8.4 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.5 Generation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.6 Relevant AMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
9 DIMSU - Feature Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.1 ADD-DIMSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.2 DISPLAY-DIMSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
9.3 REGENERATE-DIMSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.4 TEST-DIMSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.5 EXEC-DIMSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
10 ZAND-Central System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
11 ZANDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
12 KNDEF - Virtual Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
12.1 DISPLAY-KNDEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13 FEASU - Features (Bit String) in the SWU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
13.1 CHANGE-FEASU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
13.2 DISPLAY-FEASU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
14 AMOs in the User Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
15 Structure of the DPLN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
15.1 Overview of the CPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
16 WABE - Digit Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
16.1 ADD-WABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
16.2 DISPLAY-WABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
16.3 REGENERATE-WABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
17 VBZ - Internal Traffic Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
17.1 CHANGE-VBZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
17.2 DISPLAY-VBZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
18 ACTDA - Activation of User Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
18.1 ADD-ACTDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
18.2 DELETE-ACTDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
18.3 DISPLAY-ACTDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
18.4 REGENERATE-ACTDA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
19 ZIEL - Destination Addresses for Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
19.1 Key Layout of the Digital Voice Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
20 COSSU - Classes of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
20.1 ADD-COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
20.2 CHANGE-COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
20.3 DELETE-COSSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
20.4 DISPLAY-COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
2
EN4402EN00EN_0003
© 2004 Siemens AG
20.5 REGENERATE-COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

21 BERUM - Class of Service Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
21.1 CHANGE-BERUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
21.2 DISPLAY-BERUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
22 BERUZ - Times at which Class of Service Switchover is to Occur . . . . . . . . . . 123
22.1 ADD-BERUZ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
22.2 DISPLAY-BERUZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
22.3 REGENERATE-BERUZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
23 TAPRO - Key Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
23.1 CHANGE-TAPRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
23.2 DISPLAY-TAPRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
23.3 REGENERATE-TAPRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
24 LRNGZ - List of Central Speed Dialing Numbers. . . . . . . . . . . . . . . . . . . . . . . . . 136
24.1 ADD-LRNGZ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
24.2 CHANGE-LRNGZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
24.3 DELETE-LRNGZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
24.4 DISPLAY-LRNGZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
25 ZRNGZ - Central Speed Calling Digit Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
25.1 DELETE-ZRNGZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
25.2 DISPLAY-ZRNGZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
25.3 REGENERATE-ZRNGZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
26 SBCSU - Station and S0 Bus Configuration of SWU . . . . . . . . . . . . . . . . . . . . . . 142
26.1 ADD-SBCSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
26.2 CHANGE-SBCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
26.3 DELETE-SBCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
26.4 DISPLAY-SBCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
26.5 REGENERATE-SBCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
27 DSS 1 Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
27.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
27.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
27.3 Service Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
27.4 Generation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
27.5 AMO Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
27.6 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
28 SCSU - Subscriber Configuration of Switching Unit . . . . . . . . . . . . . . . . . . . . . . 180
28.1 ADD-SCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
28.2 CHANGE-SCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
28.3 DELETE-SCSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
28.4 DISPLAY-SCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
28.5 REGENERATE-SCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
29 SDAT - Administration of Individual Subscriber
Attributes and General Subscriber Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
29.1 CHANGE-SDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
29.2 DELETE-SDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
3
EN4402EN00EN_0003
© 2004 Siemens AG
29.3 DISPLAY-SDAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

29.4 REGENERATE-SDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
30 PERSI - Personal Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
30.1 ADD-PERSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
30.2 CHANGE-PERSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
30.3 DELETE-PERSI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
30.4 DISPLAY-PERSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
30.5 REGENERATE-PERSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
31 Call Log for optiset E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
31.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
31.2 Feature Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
31.3 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
31.4 AMO Modifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
31.5 AMO Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
32 Data Security with optiset E / optiPoint 500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
32.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
32.3 AMO Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
32.4 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
33 Integrated Key Functionality Multi-Line Access. . . . . . . . . . . . . . . . . . . . . . . . . . 224
33.2 AMO Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
33.3 Overview AMO Modifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
34 Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
34.1 Local Call Pickup Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
35 CHESE - Executive/Secretary Arrangements (Integrated Arrangements) . . . . . 247
35.1 ADD-CHESE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
35.2 CHANGE-CHESE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
35.3 DELETE-CHESE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
35.4 DISPLAY-CHESE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
36 Hunting Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
37 Attendant Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
37.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
37.3 Comfort Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
37.4 Nodes without an Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
37.5 AMO Usage Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
37.6 Function-Enhancements for the Attendant Queues. . . . . . . . . . . . . . . . . . . . . . . . . . 270
37.7 Automatic Night Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
37.8 Attendant Intercept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
37.9 Extend Call to Paged User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
37.10 Remote Activation of Call Forwarding for Station Users at the Attendant Console . . 289
37.11 Attendant Control of Diversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
38 Least Cost Routing (LCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
4
EN4402EN00EN_0003
© 2004 Siemens AG
38.1 General Definition of the Term LCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

38.2 The Most Important Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
38.3 Brief Description of the AMOs which are Used for the
Call Processing LCR Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
38.4 “Classical” Call Processing LCR Interrogation Sequences. . . . . . . . . . . . . . . . . . . . 302
39 Configuration of a subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
39.1 UP0/E - subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
39.2 Configuration of an IP-subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
39.3 Configuration of an optiset/optiPoint Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
40 Deletion of a subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
41 optiClient 130 V5.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
41.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
41.2 Installation and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
41.3 Generating of the optiClient 130 V5.0 in the HiPath 4000 V2.0 . . . . . . . . . . . . . . . . 321
41.4 Short description of the user interface of the optiClients 130 V5.0 . . . . . . . . . . . . . . 323
42 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
42.1 Terminal settings for optiPoint 410 entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
42.2 Generating of the optiPoint 410 in the HiPath 4000 V2.0 . . . . . . . . . . . . . . . . . . . . . 341
5
EN4402EN00EN_0003
© 2004 Siemens AG
6
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: HiPath 4000 Service Access
1 HiPath 4000 Service Access
1.1 General
With HiPath 4000 a new service platform is created which offers also many new service 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 possible.
Common Service Access for all Products

HTS via VPN Server
External access is achieved via a virtual

Service Technician private network (VPN).
An explicit VPN address, starting with "10",
TAP is given to every system and server.
MTS
ISDN
PPP-Link
SNS-Server
for HTS Customer-LAN
WAML
SNS-Server
Control
8
TAP V24 to RMX RMX
9
FAMOS
SCSI
10
Terminal V24 or UNIX
11 SL100
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 SL100 (SL200) receives an IP address

from the customer LAN.
On first installation it has the IP address 192.1.2.5.
7
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Syntax for AMO Input Siemens
2 Syntax for AMO Input

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

VERB - NOUN or
ASSIGN - 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>
8
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Syntax for AMO Input
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, [OLDPIN=<string>] ;
I TYPE = STN, [STNO=<number>],
CTYPE=<string>] ;
I TYPE = CCMS,
[CCMSCD=<keynum>],[DPLN=<number>],[STNO
=<number>] ;
Command Code Parameter

DISPLAY-SCSU [STNO]=<number>,
[TYPE] = COS, COSNO=<number>;
I[TYPE] = HW, STNTYPE=<param>;
I[TYPE] = [COS],LCOS=<number>;
I[TYPE] = ALL;
9
EN4402EN00EN_0003
© 2004 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.
DIAL
STNO
TYPE
NAME
BUCODE
Example of typical parameter values:
DIAL = DTMF
STNO = 2105&&2112
TYPE = HW
NAME = ”RECEPTION”
BUCODE = ?
If you know the AMO sequence and the parameters required, you can enter the sequence
in a single line format.
Entry Options
Display-ZRNGZ:SPDNO,0,67; or : TYPE=SPDNO,LST=0,SPDNO=
67;
Display-SCSU:HW,DTMF; or : TYPE=HW,STNTYPE=DTMF;
Display-SCSU:2105; or : STNO=2105;
Many AMO sequences require the entry of essential parameter words. These essential
parameters must be entered, and can appear in any position within the AMO sequence.
10
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Syntax for AMO Input
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.
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. Fur-
ther operating instructions are on the next pages.
11
EN4402EN00EN_0003
© 2004 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
12
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Extended Access Protection (Login)
3 Extended Access Protection (Login)

System access protection was extended by the introduction of user IDs in the Hicom 300E V2.0
variant. Sessions can only be started with the right user ID. The user must identify himself by
user name and password which makes the corresponding user ID known to the system. Certain
COS are assigned to every user ID allowing the user to execute certain MML commands. Dur-
ing logging of the MML commands, the identification number of the ID (user ID = UID) calling
the commands is registered. A privileged user, the so called system administrator, administers
the user IDs.
● New AMO handling

● Individual configuration of AMO rights
● AMO language depends on user id
13
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Extended Access Protection (Login) Siemens
3.1 System Administrator Tasks
3.1.1 Initialised User IDs

One user ID is initialised in the ADS data base of the application program system (APS):
1. ROOT with Password XXXXX
To make it impossible for unauthorized people to use the initialised ID, the passwords with the
ROOT ID should be changed immediately after a new APS variant has been uploaded to a cus-
tomer system!
The initialised user ID always has the user ID 1 and cannot be deleted. ROOT is also used for
internal command processing.
3.1.2 Query User IDs

The system user IDs can be listed using the command DIS-USER.
Input:
DIS-USER;
Output:
|UID| NAME | RIGHTS | STATUS | ADDITION | TRIES | TIME |
| | |5432109876543210| |L|R|C|F|P|E|T|I| | (MIN) |
+===+==========+================+========+=+=+=+=+=+=+=+=+=======+=======+
| 1 | ROOT | XXXXXXXXXXX| INIT. |X X X X X | 99 | 0 |
| 2 | MAYER | XXXXXX| |X X X X X X | 99 | 0 |
| 3 | SCHMIDT | XXX| |X X X X X X | 99 | 0 |
| 4 | SMITH | XXX| |X X X X X X X| 99 | 0 |
14
EN4402EN00EN_0003
© 2004 Siemens AG
3.1.3 Set New User IDs

New user IDs can be set using AMO USER. The maximum number of IDs is 99. The AMO au-
tomatically assigns the user ID. The new user IDs cannot be used immediately. The system
administrator must assign a preliminary password using PASSW. Exceptions are user IDs with-
out the option P (see chapter Options).
3.1.3.1 User Name

At the user interface the user identity is defined by the user name (also called user ID or login
name) which may consist of maximum 8 characters (capitals, digits and special characters in
any combination). The name must be unambiguous and assigned only once. The user will then
login using this user name.
The system administrator assigns and also modifies, if required, the user names in agreement
with the users. Every user should have his/her own user ID. This helps in cases of unauthorized
access to determine which user ID was used for the access attempt.
3.1.3.2 Authorization Assignment

The system administrator assigns one or more executional authorizations to every user ID.
These authorizations allow the user to execute certain MML commands (AMO actions) (see
Figure 1).
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Execution rights:
Rights for normal

user
reserve
Rights of
ROOT
Rights for
1 = Execution allowed special users
0 = Execution not allowed
Bild 3-1 Execution authorizations of a user
A "necessary execution authorization" also known as class, is assigned to every AMO action.
A user can call an AMO action only if the class of the AMO action is contained in his/her cata-
logue of execution authorizations. If the authorizations are insufficient, an error message is dis-
played and the AMO action is not performed. The action can only be carried out, if a user ID
with the required rights is used.
15
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Extended Access Protection (Login) Siemens
In this system variant the classes of AMO actions are predefined. They are based on the old
hierarchical password class structure. It is useful to follow the previous password classes of
PASSW AMO when assigning authorizations (see Table 1). The lowest authorization is 0. au-
thorizations > 10 are reserved for special users.
previous class: Rights:

5 0&&5
4 0&&4
3 0&&3
2 0&&2
1 0&1
0 0
Tabelle 3-1 Assignment of authorizations following previous password classes
The advantages of the new access concept are:

● Protection of AMO actions with class 0
● Access control is no longer hierarchical
The system administrator can modify the AMO action classes using AMO AUTH.
16
EN4402EN00EN_0003
© 2004 Siemens AG
3.1.4 Options
One or more options can be set for one user ID using the OPTIONS parameter. There are the
following options:
Option Meaning
L Local use. The ID can be used locally (devices CON1 to CON6).
R Remote use.The ID can be used from remote AM (device FAS) (modem or
LAN).
C Change own password.The user can change his/her password.
F Forced password change. The user is forced to change the temporary pass-
word.
P Password required. The user has a password (without password means: no
password prompting during login).
E Erasable. The ID can be deleted.
T Timeout. Forced logoff after timeout (after ca. 2 minutes).
I International session language (English).
Table 1
When new user IDs are set the options L to E (all options with the exception of option T) and,
if required I, are set as defaults. The default value for option I, used to specify the session lan-
guage, depends on the session which sets the ID.
ROOT cannot be deleted. It is sometimes better to disable an unused user ID instead of delet-
ing it. The ID can no longer be used. But it is possible to reconstruct the user actions on the
system (LOGBK AMO), if required.
Input:
CHA-USER:NAME=<name>,AUTH=0&&5;
17
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: AMO authorizations in the HiPath 4000 V2.0 Siemens
4 AMO authorizations in the HiPath 4000 V2.0
4.1 ADP
A C D D R O A D S S S S E O C D D I U S
D H E I E U C E W T T E X U O U I N M A
D A L S G T T A I A O T E T P M A P B M
N E P E P I C T R P C P Y P L U E M
G T L N U V T C T U O T N E
E E A E T A I H T G N L
Y R T V O . E N
A E A V . N
T T E .
E E R
ACMSM 4 4 4 4 4
AFR 5 5 5 0 0 0 5 5 5
ANUM 2 0 2
APC 0 0 2 2 2
APP 3
APS 0 0 2 2 2
ASPIK 2
ASSGN 2 0 2 0
ATCSM 2 2 2 0 2
AUTH 10 0 2
BACK 2 2 2 0 2 2 2 2 2
BCSM 2 2 0 2 2 2
CABA 2 2 2 2 2
CDBR 2 0 2 2
CDSM 0
CLIST 2
CMP 2
CMUID 5
18
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: AMO authorizations in the HiPath 4000 V2.0
Y R T V O . E N
A E A V . N
T T E .
E E R
CONSY 2 2 2 0 2 2
COPY 3
CPCI 2 0 2
CPSM 2 2 2 0 2
CPTP 2 2 0 2
CRON 5 5 5 0 2
DAGR 1 1 1 1 2 1
DASM 2 2
DATE 2 0
DAVF 1 1 2
DCSM 2 2 2
DDRSM 2 2 2 5
DDSM 0 2
DEBUG 3 3 3
DEFPP 2 2 2 0 2
DEFTM 2 2 2 0 2
DEL 3
DISPA 3 3
DLSM 2 2
DSSM 2 2 2 2
DPSM 2 2
DTSM 2 2 2 2
19
EN4402EN00EN_0003
© 2004 Siemens AG
Y R T V O . E N
A E A V . N
T T E .
E E R
DUP 3
DVU 2 2 2
FAMOS 2 2 0 2 2 2
FAMUP 2 2 2 2 2 2 2 2 2 5
FBTID 2 2 2 2
0
FBTN 1 1 1 2
FEACG 4 4 0 2
FETA 1 1 1 2
FINF 2 2
FORM 3
FTBL 1 1 1 1 1
FTCSM 2 2 2 2 2
FTRNS 2 0 2
FUNCT 2 0 2
GEFE 2 0 2
GENDB 5
GETAB 1 1 0 2 1 1
GETPD 0
GEZAB 1 1 1 1 1 1 1
GEZU 2 2 2 0 2
GRA 2 2
GRZW 1 1 1 0 2
20
EN4402EN00EN_0003
© 2004 Siemens AG
Y R T V O . E N
A E A V . N
T T E .
E E R
HISTA 2 2 2 0 0 2 2 2 2
INFO 2
INIT 3 0 3
JOB 5 0
KDEV 1 1 1 1 1 1
KDGZ 1 1 1 0 1
LCSM 2 2 2 0 2
LDB 3
LIST 2
LOGBK 5 5
LSSM 0 2 2 0
PASSW 5 5 5 5 2
PATCH 2 2 2 0 2 2 2 2
RCUT 1 1 1 1 2
REGEN 5
REN 3
REST 2 0 0 2
SAVCO 3
SAVE 3
SDSM 0
SELG 1 1 1 1 2 1
SELL 1 1 1 2
21
EN4402EN00EN_0003
© 2004 Siemens AG
Y R T V O . E N
A E A V . N
T T E .
E E R
SELS 0 2 1 1 1 1
SIGNL 2 2 2 0 2 0 2 2 2 5
SONUS 2 0 2 2
SPES 2 2 0 2 2 2
SYNC 5 0 5 5
TABT 1 1 1 1 2
TCSM 2 2 2 0 2
TEST 0 0
TEXT 1 1 0 2
TINFO 2 0 2
TLZO 1 1 1 1 2
TRACA 2 2 2
TRACS 2 2 2
TTBL 1 1 1 1 2
UPDAT 2 0 2 2
USER 10 10 10 0 2 10 10 2
UW7 5 5 5
VADSM 2 0 2 2 2
VEGAS 2 2 0
XAPC 0 0 0 0
22
EN4402EN00EN_0003
© 2004 Siemens AG
4.2 CC
A C D D R O A D S S S S E O C D T R D I O D
D H E I E U C E W T T E X U O U E E I N P I
D A L S G T T A I A O T E T P P S S A P T A
N E P E P I C T R P C P Y T T L U I G
G T L N U V T C T U A O T M N
E E A E T A I H T R G I O
Y R T V O T . Z S
A E A V . E E
T T E .
E E R
ACDGP 2 2 2 0 2
ACDRS 2 2 2 0 2
ACDRT 2 2 2 0 2 4 2 2
ACDSD 2 0 2
ACSU 2 2 2 0 2
ACTDA 2 2 0 2
AGENT 2 2 2 0 2
ANSU 2 0 2
APRT 2 2 2 2 2
AUN 2 2 2 0 2
AUTHO 0
BCSU 2 2 2 0 2
BDAT 2 2 2 0 2 2
BGDAT 2
BERUM 2 0
BERUZ 2 0 2
BGDAT 2
BPOOL 2 2 2 0 2
BSSU 2 2 2 2 5
BUEND 2 2 2 0 2
CDSU 0
23
EN4402EN00EN_0003
© 2004 Siemens AG
Y R T V O T . Z S
A E A V . E E
T T E .
E E R
CHESE 2 2 2 0 2
CODEW 5 3 5 5 3 5
COMGR 2 2 2 2 2
COP 2 2 2 0 2 2 5
COSSU 2 2 2 0 2
COT 2 2 2 0 2 2 5
CTIME 2 0 2
DBC 3 5 0 0 3
DBSUM 0
DCIC 2 2 2 0 2
DIAGS 2 0 5 5 5
DIDCR 2 2 2 0 2
DIMSU 4 0 2 4 0
DISPS 3 3 3 3
DNIT 2 2 2 0 2
DSSU 2 2 2 2 5 2 5
DTIM1 2 0 2
DTIM2 2 0 2
FEASU 4 0 2
FUNSU 2 0 2 2
GKREG 2 2 2 2 2
GKTOP 5 5 5 5 5
24
EN4402EN00EN_0003
© 2004 Siemens AG
Y R T V O T . Z S
A E A V . E E
T T E .
E E R
HFAB 2 2 0 2 2
HIDMP 2 2
HOTLN 2 2 2 0 2
KCSU 2 2 2 0 2
KNDEF 2 2 2 0 2
KNFOR 2 2 2 4 4 4
KNLCR 2 2 2 0 2
KNMAT 2 0 2
KNPRE 2 2 2 0 2
KNTOP 2 2 2 0 2 2
LANC 2 2 2 0 2 2 2
LAUTH 3 3 3 4 4
LDAT 2 2 2 0 2
LDPLN 2 2 2 0 2 2
LDSRT 2 2 2 0 2
LEMAN 2
LIN 2 2 2 2 2
LODR 2 2 0 2
LPROF 2 2 2 0 2
LRNGZ 2 2 2 0 2
LSCHD 2 0 2
LW 0
25
EN4402EN00EN_0003
© 2004 Siemens AG
Y R T V O T . Z S
A E A V . E E
T T E .
E E R
LWCMD 3
LWPAR 2 2 2 0 2 2
MFCTA 2 0 2 2
NAVAR 2 2 2 0 2
PERSI 1 1 1 1 1
PETRA 2 0 2 2
PRODE 2 0 2 2
PSTAT 2 2 2
PTIME 2 0 2 2
RCSU 2 2 2 0 2
REFTA 2 2 2 0 2 2
RICHT 2 2 2 0 2
RUFUM 2 2 0 2
SA 2 2 2 0 2
SBCSU 2 2 2 0 2
SCREN 2 2 2 0 2
SCSU 2 2 2 0 2
SDAT 2 0 2 5
SDSU 0
SIPCO 2 2 2 2 2
SSC 2 2 0 2
STMIB
26
EN4402EN00EN_0003
© 2004 Siemens AG
Y R T V O T . Z S
A E A V . E E
T T E .
E E R
SSCSU 2 2 2 0 2
STMIB 3
SXSU 2
SYNCA 2 2 2 0 2 2
TACSU 2 2 2 0 2 5 5 5
TAPRO 2 0 2 2
TDCSU 2 2 2 0 1 2 2
TGER 2 2 0 2
TREF 5 0 2 5 5
TSCSU 2 2 2 0 2
TSU 2 2 5
TWABE 2 2 0 2
UCSU 2 2 2 0 2
UPLOL 5
UPLO2 5
USSU 2 2
VADSU 2 2 2 0 2 2 2
VBZ 2 0 2
VBZA 2 0 2
VBZGR 2 2 0 2
VFGKZ 2 2 2 0 2
VFGR 2 2 2 0 2
27
EN4402EN00EN_0003
© 2004 Siemens AG
Y R T V O T . Z S
A E A V . E E
T T E .
E E R
VOICO 2 2 0 2 2 2
WABE 2 2 2 0 2
XAPPL 4 4 4 0 4
ZAND 2 0 2 5 5 5
ZANDE 2 0 2
ZAUSL 0
ZIEL 2 2 0 2
ZIELN 2 2 0 2
ZRNGZ 2 2 0 2
28
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Log Book
5 Log Book
PABX systems which have to fulfill more stringent security requirements, must offer a degree
of access control and reviewability. This includes the logging of administration actions for eval-
uation at a later date. In Hicom systems, access logging is now accomplished with the “Log
Book” function. The log book contains information on the last 2,000 administration actions, and
cannot be manipulated. The log book data is stored in a restart-safe and reload-safe database
file system on the Hicom hard disk. The log book information can only be read by authorized
personnel, with the aid of the LOGBK AMO.
Hicom 300
AMO AMO
SWU und Server
ISp
AMO AMO
Hard Disk
Logging
internal entry local entry MMIlocal entry remote entry Log Book
point point point point
USER
V.24 V.24 V.24
async. async. sync.
CON1 CON9
RMA
AMO Administration & Maintenance Order CON Console

MMI Man Machine Interface USER internal user
ISp Integrated Server, primary RMA Remote Maintenance and
SW Switching Unit Administration
U
Bild 5-1 Logging the Administrative Actions in a Hicom System
29
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Log Book Siemens
5.1 Logging
The Log Book function logs all actions carried out at one of the central administration interfac-
es: the local administration interfaces (CON1 to CON9), the remote administration interface
(RMA), and the internal administration interface (USER). Administration actions which are car-
ried out via standard user telephones are not logged.
For logging purposes, an administration action is considered to be any kind of MML command
(man-machine language) entered via the MMI (man-machine interface). The log book distin-
guishes between the following four types, and records each type in a separate category:
1. complete MML command strings (TYPE=START)
2. corrected MML command strings, i.e. after an AMO prompts an entry (TYPE=CONTINUE)
3. Error Messages and Advisories (F-messages, H-messages and S-messages), which are
output by an AMO or AMC (TYPE=OUTPUT)
4. The “end” or confirmation message, i.e. COMPLETED, PARTIALLY COMPLETED, NOT
COMPLETED or CANCELED (TYPE=END)
Data types 1 and 4 (START and END) are always logged, for each administrative action. Data
types 2 and 3 (CONTINUE and OUTPUT), may be logged several times per action or not at all,
depending on how many times the AMO prompts an entry or outputs a message. Log book en-
tries for administration actions which are run in parallel are mixed, i.e. each event or data type
is logged as it occurs. Error messages output by the MMI (“M” messages) and AMO outputs
such as display tables or regenerate batches are not logged.
For each log entry, the following additional information is stored in a database file system:
1. a running log number, which shows the chronological sequence in which the data was
logged
2. the administration interface (DEV), at which the administration action was initiated:
a) CON1 - CON9
b) FAS
c) USER
3. the terminal session number (TSN) assigned to each administration action
4. the user ID (UID)used to open the session
5. the AMO noun/acronym (NOUN)
6. the TYPE of log entry (as explained above):
a) START
b) CONTINUE
30
EN4402EN00EN_0003
© 2004 Siemens AG
c) OUTPUT
d) END
7. a time “stamp” (TIME), which shows when the action was logged
This additional information allows the log book entries to be reviewed for specific actions.
5.2 Log Book Virtual Memory

The log book occupies a fixed virtual memory area on the hard disk. This is a cyclic FIFO (first
in, first out) storage area with enough space for 10,000 entries. The cyclic data storage princi-
ple means that the system returns to the beginning as soon as the area is full, and begins to
overwrite the older entries sequentially again.
5.3 Data Protection

The log book data con only be output or evaluated by authorized personnel (highest password
level), with the aid of the LOGBK AMO. The individual log files on the hard disk area are read
and write-protected, and the data area itself cannot be moved or deleted. This means that the
area cannot be accessed by any other AMOs (e.g. DEL, COPY, LIST, CLIST, REN etc.).
The log book function cannot be deactivated, except in the following two cases:
● When the database is generated with the GENDB AMO, the MML commands executed by
GENDB are only logged if expressly required (GENDB parameter LOGGING=Y). This is
to improve the runtime performance of the generating run.
● The log book function cannot work if the hard disk area which contains the virtual memory
is deactivated. However, the DEA-DSSM command required to deactivate the hard disk
will still be logged.
5.4 Evaluation of the Log Book Data with the LOGBK AMO
The LOGBK AMO has a multi-level display function, which allows users to limit the output by
defining a specific search criterion (“Query by Example”). A search criterion is defined by com-
bining the required parameters. If no parameters are specified, the entire log book is output.
Users can search for entries made within a defined time period, by specifying the STIME and
ETIME parameters. The output will then only include entries with a time “stamp” (TIME entry)
which lies between the start time (STIME) and the end time (ETIME) specified by the user. In
some cases, however, the time “stamp” can be invalid, e.g. if the system clock was incorrectly
set or not working when the action was logged. In this case, users should use the chronological
log entry number (sequence number) for orientation, and avoid using the time parameters. Us-
ers can also search for entries which contain a specific text string (TEXT parameter). In this
31
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Log Book Siemens
case, the system searches for logged MML commands which contain the required string. Since
this search criterion can take quite a while, the display output should be further limited with ad-
ditional search parameters (e.g. by specifying the TYPE parameter).
By default, the log book entries are output in chronological order, i.e. beginning with the older
entries. Users can also display the data in reverse order (i.e. newer entries first), by specifying
an earlier date for the ETIME parameter than for the STIME parameter or by using START in-
stead of QUERY. Both the STIME and the ETIME parameter must be declared in TIME search-
es.
The following figure shows how the data logged for the administration action ADD-BUEND is
displayed by the LOGBK AMO. Each log entry contains a header line which shows the addi-
tional information logged for the sequence. This information can also be specified as a search
criterion.
Log book sequence number

Administration interface AMO noun
Session number Type
User ID Time “stamp”
P0033 DEV:CON1 TSN:1234 UID:1 NOUN:BUEND TYPE:START TIME:1999-12-31

09:34:12 (MML command)
AD-BUEND:22,,30,;
P0034 DEV:CON1 TSN:1234 UID:1 NOUN:BUEND TYPE:OUTPUT TIME:1999-12-31

09:34:13 (MML output)
F01: TGRP 22 ALREADY EXISTSS
(MML command input after AMO prompting)
P0035 DEV:CON1 TSN:1234 UID:1 NOUN:BUEND TYPE:CONTINUE TIME:1999-12-31

09:34:25 (MML completion message)
AD-BUEND:25,,30,;
P0036 DEV:CON1 TSN:1234 UID:1 NOUN:BUEND TYPE:END TIME:1999-12-31

09:34:28
ADD COMPLETED;
Bild 1 Example of a Log Book Output
32
EN4402EN00EN_0003
© 2004 Siemens AG
5.4.1 Examples
5.4.1.1 Display Entire Log Book

● Display entire log book without prompting after each page (ANS=C):
STA-LOGBK:ANS=C;
5.4.1.2 Write Entire Log Book to a File

● Assign the RESULT device for the current session to a file with the desired name, e.g.
"LOGDEZ1999":
CHA-ASSGN:TBL=SCT,SDEV=RESULT,LDEV=FILE,FILE="LOGDEZ1999";
● Output the file contents:
STA-LIST:DATNAM=”:AMD:LOGDEZ1999”,AUSART=M;
Contrary to the log book the file is not access protected and must be deleted after
evaluation for data protection reasons.
● Output log book for December (caution: always specify “continue without prompting”!):
STA-LOGBK:STIME=”1999-12-01/00:000:00”,ETIME=”1999-12-31/23:59:59”,ANT=F;
● Re-assign RESULT device to original output device, e.g. Console 1:
CHA-ASSGN:TAB=SCT,SDEV=RESULT,LDEV=CO1;
5.4.1.3 Display with Search Criterion (Query by Example)

● Display all BUEND commands entered at the administration interface Console 1:
STA-LOGBK:TYPE=START, DEV=CON1, NOUN=BUEND;
5.4.1.4 Display with Specific Text String

● Display all AMOs which were terminated with errors:
STA-LOGBK:TYPE=END, TEXT="CANCELED";
The TEXT search criterion may take a long time, and should always be qualified by
specifying further parameters, if possible (e.g. TYPE). Since the STA-LOGBK com-
mand itself is logged, don’t be surprised if you find it among the display results!
5.4.1.5 Display Log Book in Reverse Order

● Display entire log book in reverse order (beginning with latest entry) by using START in-
stead of QUERY:
AB-LOGBK;
The output will be halted at the end of each screen page. You can continue by specifying
ANS=Y or terminate the display output by specifying ANS=N.
33
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Administration Software Siemens
6 Administration Software
6.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
34
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Administration Software
6.2 BGDAT - Display the Board Table

The AMO BGDAT is used to display the most important data of the UBGDAT Board Table. The
UBGDAT, which content cannot be changed per AMO, is stored on the hard disk in the file
:PDS:APSU/BGDAT00. The data of the UBGDAT is used by the AMOs BCSU and UCSU for
the configuration of boards resp. shelves.
The type and the Q-number (part number) of a board must be entered, if a board is configured.
The boards of type PER, DIU, TMD, IPGW, RG, WGEN, SIUP and PERHW are configured with
AMO BCSU and the boards of type AP, LTG and LTU with AMO UCSU. The function ID (FC-
TID) must only be entered if the board is a multifunctional board, which funktion must be de-
fined when the board is configured. There exist also multifunctional boards which functions (at
present maximal two) can operate parallel, for instance, the STHC board.
The loadware for the different boards and board functions is stored in files on the hard disk. The
path :PDS:APSP/LTG/ contains all loadware files. Only the last 13 characters of the loawdare
file names are displayed by the AMO.
35
EN4402EN00EN_0003
© 2004 Siemens AG
6.3 Switching AMOs for the SWU

AMO:
LTU USSU
MOD MOD BSSU
PORT PORT FUNSU
TERM
DSSU
Bus
TERM TERM
6.3.1 Description of the Switching AMOs for the SWU
6.3.1.1 USSU Switching of SWU Units

This AMO is used to configure the system units of the Switching Unit (SWU).
The processing of the service modules takes place using the AMO USSM.
LTGs, LTUs, the central SIU and the HDLC-DCL links are switched on; LTGs and LTUs are
switched off. Peripheral SIUs can only be switched using the AMO BSSU.
36
EN4402EN00EN_0003
© 2004 Siemens AG
6.3.1.2 Examples: Switching System Units

1. Switching on LTG 1
Input:
ACT-USSU:UNIT=LTG,LTG=1;
Output:
H13: LTG ACTIVATED
2. Switching on LTU 3
Input:
ACT-USSU:UNIT=LTG,LTU=3;
Output:
H06: LTU ACTIVATED - NOT OPERATIONAL (NPR)
3. Switching on the SIU

Input:
ACT-USSU:UNIT=SIU;
Output:
H28: SIU IN A-HALF WILL BE SWITCHED
H19: SIU ACTIVATED
H28: SIU IN B-HALF WILL BE SWITCHED
H19: SIU ACTIVATED
37
EN4402EN00EN_0003
© 2004 Siemens AG
6.3.1.3 BSSU Board Switching, SWU

This AMO is used to process modules of the Switching Unit (SWU).
● Activate:
Modules can be activated either with or without conditional loading.
● Deactivate:
It is possible to deactivate the module with or without being preblocked.
● Restart:
Deactivate without pre-blocking and Activate with unconditional loading has been com-
bined in one action.
● Display:
Statistics counters of the specified module(s) can be displayed and reset.
6.3.1.4 Examples: Switching Boards

The module of LTG 1, LTU 2, SLOT 25 is to be activated with unconditional loading.
Input:
ACT-BSSU:ONTYPE=AUL,LTG=1,LTU=2,SLOT=25;
Output:
H2: 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). A possible manual disable has been lifted.)
6.3.1.5 DSSU Device Switching, SWU

The AMO DSSU can be used to switch devices of the Switching Unit (SWU) on or off. In the
Restart command switching off and switching on are combined. In addition terminals can be
signed off from or signed on to a port equipment number (Autoset Relocate feature). In this
AMO description the term "devices" is used to cover subscriber ports, terminals and line ports.
Devices are switched based on their port address (TYPE = PEN) or their station number
(TYPE = STNO).
In the case of configurations with several devices of different services on one number (e.g. on
the S0 bus), with only a few exceptions these can also be switched on a service-specific basis.
38
EN4402EN00EN_0003
© 2004 Siemens AG
All functional terminals on the S0 bus can only be processed in total. The DIENST parameter
may not be specified here.
MSN numbers:
The AMO allows CP disabling and enabling of MSN numbers/MSN secondary station
numbers.
The MSN service has been introduced for this. If this service is specified for a non-MSN num-
ber/MSN secondary station number the command is rejected with error message F23. Switch-
ing on can only be performed using ONTYPE=ANL which sets the READY bit at the CP level.
When switching off with OFFTYPE=DC only the READY bit is reset; with OFFTYPE=DI the CP
is induced to immediately initiate all transactions of the processed MSN number.
(see also the AMO SBCSU)
Point-to-point S0/S2 connections (FPP):
Only main numbers of an FPP connection established in accordance with the new concept can
now be switched on. "Old" connections are rejected with error message F26. In addition to main
numbers of new FPP connections, main numbers and B-channel numbers of "old" connections
can still be switched off.
B-channel on the S0 line port:
The second B-channel of the S0 line port can be switched individually. Switching is always per-
formed with "switching without loading" or "switch off long-term". If the entered port equipment
number does not lead to an S0 line port the message F22 is output.
The security status can be queried using the AMO SDSU.
DIUS7 B-channels:
For B-channels of a DIUS7 port the setting and lifting of the status “local maintenance blocking”
can be activated (BLOCK/UNBLOCK). In addition the lifting of all statuses of the B-channels
(both local and remote) can be activated with simultaneous initiation of possibly existing con-
nections (RESET).
The “blocking” status of the B-channels can be queried using the AMO SDSU.
6.3.1.6 Example: Activation of Terminal Equipment

1. The line module and the terminal equipment with the STNO 204 is to be activated with
unconditioned loading.
Input:
ACT-DSSU:ONTYPE=AUL,TYPE=STNO,STNO=204;
Output:
H01: STNO 204 ACTIVATED (READY)
H01: DCI 204 ACTIVATED (READY)
39
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: BCSU - Configuring Mounting Locations for Modules in the Siemens
7 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 mod-
ule is plugged in, loaded and put into service.
7.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 NBCS there are two different kind of LTUs from now on. The range for tra-
ditional 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
In "normal" shelfs one SIU board per LTU half will be able to get assigned. In "compact" shelfs
(C, EC, ECX) one SIU board per LTU quarter will be able to be assigned.
This rule will not be checked by AMO. Generally a advisory message about this rule will be
printed if a SIU board has to be assigned.
One SIU is not taken into operation during installation. Because of time slot allocation, the SIU
is taken into operation by means of a hard restart. If a second (redundant) control unit is avail-
able, the hard restart for Hicom 370 must be simultaneously initiated in both SWU’s; in the case
of Hicom 390 the hard restart must be initiated simultaneously in both the LTGA and the LTGB.
To prevent a loss of the preinitialized SIU data in those cases where a hard restart escalates
into a RELOAD, the data should be written to the hard disk using AMO UPDAT before initiating
the hard restart.
40
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: BCSU - Configuring Mounting Locations for Modules in the
Advisory: If a SIUX board is added as peripheral SIU the parameter FCTID will have to be spec-
ified. Via this parameter the right function of the board - as SIU type 2 (MFV), SIU type 3 (MFC),
type 4 (TDS), SIU type 5 (ANI) , SIU type 6 (MFS) or SIU Type 7 (Line Testing) - will be select-
ed.
Note for SIU type 4:
If such a SIU is added, a TDS port will be configured by the AMO. For the amount of TDS ports
(SIU type 4) in the system the following rule exists:
● Only one TDS port may be konfigured in the whole HHS shelf range (1 - 15). This
means, that in this whole range only one SIU type 4 can be configured with AMO BC-
SU. On some system platforms it is furthermore possible, to configure a central SIU
(DSCX/SIUCO) with AMO UCSU. In this case a TDS port will be configured by AMO
UCSU for this central SIU. If such a DSCX/SIUCO is configured as central SIU, it is
not possible to configure a peripheral SIU type 4.
● In the AP shelf range (17 - 99) one TDS port may be configured per LTU. This Port will
be configured by AMO UCSU, when the NCUI board is added. That means: it is not
possible, to configured a SIU type 4 in an AP shelf.
The timeslots, which are usually reservered for SIU boards, can be used by a voice compres-
sion (VC) connection (from EV1.0). In this case a SIU board can only be assigned if the VC
connections have been deactivated by AMO-VOICO first. All affected VC connections will be
displayed in a corresponding error message.
Assigning a Ringing/Dialing AC Generator:

Any desired number of ringing AC generator or dialing AC generator can be assigned.
However, only one ringing AC generator and one dialing AC generator may be put into service
per backup unit (e.g. HICOM 370 : LTU 1-3, LTU 4-6, HICOM 390 : LTU 1-2, LTU 3-4, LTU 5-
6, etc.)
Advisory: For CC80 shelf the wiring connections on back plan must be connected like de-
scribed in service manual. If this advisory is ignored the ringing AC generator will be destroyed.
For feature message waiting Thailand the US ringing AC generator is used for all hardware
platforms. The OPMODE has to be UN20H85V. If an other OPMODE is specified by user for
the US ringing AC generator (Q2468-X) the AMO will overwrite the OPMODE with the right val-
ue. If the user specifies an other ringing AC generator for OPMODE UN20H85V the AMO will
prompt the right value for part number.
Following shelf types require special treatment:

– For feature NBCS a new shelf type "INCH 19" has been introduced. The HW of this
19" shelf consists of one 19" base box and one 19" expansion box.
The 19" base box allows the configuration of three boards and one NCUI board in-
41
EN4402EN00EN_0003
© 2004 Siemens AG
stead of LTUC (AMO-UCSU). The slot numbers are 1 to 3 for peripheral boards and 4
for the NCUI board. The 19" base box can be considered as left shelf half.
The 19" expansion box allows the configuration of four peripheral boards. The slot
numbers are 9 to 12. The 19" expansion box can be considered as right shelf half.
– Also if the 19" expansion box is not mounted, AMO-BCSU can configure boards in the
according slots. The AMO-BCSU considers the 19" base box and 19" expansion box
as one shelf unit.
– It is not possible to configure some special boards (e.g. Ringing AC generators or Di-
aling AC generators, VCM board) on this 19" shelf. AMO-BCSU will check this against
restrictions contained in the UBGDAT.
– The 19" shelf is only possible for usage in the AP shelf range.
Following slots require special treatment:

– In compact shelves, slot 19 is usually reserved for configuring an RG, an ACGEN, a
SIU or a PSIO.
Adding signed off PENs for feat. "autoset relocate":

For feat. "autoset relocate" (see also service manual) it is neccessary to prepare PENs (Port
equipment numbers) (Circuits on boards) in that way, that added and signed off devices on this
PEN would be able to signed on by a key number or by AMO-DSSU.
This will be done in two steps:
– Adding the board as before
– Change the PEN with the command CHANGE-BCSU:TYPE=SIGNOFF,... to this state
At a signed off PEN can only devices but no line circuits or switch boards be added !
At signing off circuits, a parameter OPS enables the user, to mark circuits on SLMA boards for
off premises usage (OPS=YES). If OPS=YES is entered for circuits on other boards than SL-
MAs, an advisory message will be displayed, that the parameter will be ignored.
With the command CHANGE-BCSU:TYPE=RELEASE,... a signed off PEN will be switched to
state "free". At this PEN a line cicuit can be added.
Sign off is only valid for following board types:
SLMA, SLMB, STMD, SLMO, SLMQ, SLMS, SLMU, SLMQ16 and WAML2 (=SLMPX)
PENs at a WAML2-board are subordinated a PFS-check (Telecommuting). Only as many
PENs can be signed off as the PFS-counter allows, depending on the contracted respectively
the already assigned value. If the counter is exceeded this is announced by the AMO producing
an error message.
42
EN4402EN00EN_0003
© 2004 Siemens AG
At all other boards, the signed off circuits are subordinated a PFS-check too (TEILNEHMER/
SUBSCRIBER). In this case, the signed off B-Channels are counted.
For analog boards one signed off circuit represents one B-channel, for digital boards the signed
off subscribers on a circuit ( up to 8 sign offs possible ) will be counted as maximal 2 signed off
B-channels. If the counter is exceeded this is announced by the AMO producing an error mes-
sage.
Special treatments for assigning peripheral boards:

For certain boards the number of circuits, which have to be configured, can be reduced from
the UBGDAT value because in a 80CM system the number of available lines is quite low. The
parameter CIRCNT will be ignored with a corresponding advisory for all boards with a fixed
number of circuits.
From EV1.0 also periheral boards can have more functions like SIUX boards (e.g. WAML, ST-
MA, SLMO24). These functions can be specified by parameter FCTID.
The first used line (Begin Line = circuit 0) of the STMA-board is added to the reference clock-
table. The REFTA-entry can therefore only be changed in AMO-REFTA.
Only one Unix-pocessor-board (DMP5L) can be assigned for each PBX. Two slots are needed.
An exception is the PBC 10 (slot 61) in the 80CMX - base-frame. Due to the physical order only
one single slot is used.
The DMP5L board may be configured in following LTUs (depending on the HICOM type):
Tabelle 1:
SYSTEM PERMITTED LTU

600ECX 1, 5, 6, 10, 11, 12
600ECS 1, 4, 5, 8, 9, 12, 13
80CMX 1, 2
80CMX-DSC 1, 2
80CXE 1, 2
NOTE:
for HICOM600:
Because the AMO can not distinguish between a HICOM 600ECX and a HICOM 600ECS the
possible user input for parameter LTU are values between 1 and 15. The systemadministrator
must ensure that, depending on the HICOM type, the DMP5L will be configured only in the
LTUs described above.
43
EN4402EN00EN_0003
© 2004 Siemens AG
If a 80CMX-DSC is used with the small version power supply (PSDSC), only 4 boards can be
configured in LTU 1. The AMO can not check, if the configuration was done with a strong ver-
sion power supply (PSAFE) and a small poower supply is used during the full action. This case
can lead up to destroyment of the switch.
Feature "Wireless Server":

If the Feature "Wireless Server" is activated, adding of boards is limited to:
Tabelle 2:
Boardtype Configurable amount

SLMA 1
DIUS2 2
STMD 2
SLMC 2
WAML 1
CDG 2
The attempt, to configure other boards than described above, will be rejected with an error
message.
If the amount of configureable boards of a certain type is already reached and the user tries to
add such a board, the ADD-command will be rejected with an error-message.
7.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 module is put back into service.
– In the case of a DIUC, the parameters FIDX1/2 and LWPAR1/2 of the associated PCM
paths can be modified.
44
EN4402EN00EN_0003
© 2004 Siemens AG
– With the new branch "HWYBDL" the access to the upper (F) or lower (A) highwaybun-
dle of a board can be set, to use a previously by AMO UCSU configured overlay con-
figuration. At the moment, bundle "F" can only be used for STMI, DIUN2- and DIUN4
boards.
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";
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)
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
3. Change the highwaybundle of a DIUN2 to bundle "F":

CHANGE-BCSU:HWYBDL,1,1,37,Q2196-X,1,F;
7.3 DELETE-BCSU
Before a peripheral module is removed, the line circuits must be canceled.
For certain modules the AMO creates a modulespecific memory in the database, where certain
modulespecific data are administered. This means that data which for example can be added
or changed by means of AMO-BDAT, AMO-STMIB and so on, will be deleted without any warn-
ing.
An exception is only the WAML1 board, which can only be deleted if the corresponding data
have explicitely been deleted before.
45
EN4402EN00EN_0003
© 2004 Siemens AG
Example
1. Remove the RG module having the parameters LTG=1, LTU=1 and SLOT=19.
Input:
DELETE-BCSU:RG,1,1,19;
7.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).
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
46
EN4402EN00EN_0003
© 2004 Siemens AG
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 |
+-----------------------------+-+------------+-----+--------+------------+
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 en-
tered.
47
EN4402EN00EN_0003
© 2004 Siemens AG
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:
-----+-----------+---------+---+---+-+------------+-----+--------+------------+
-----+-----------+---------+---+---+-+------------+-----+--------+------------+
1 | AVAILABLE | | AVAILABLE | | | NPR |
2 | Q2117-X SLMS A |*| | | | NPR |
4 | Q2302-X NCUI 1 | | Q2302-X | 1 | -A2 - | READY |
9 | Q2158-X SLMO24 1 A |*| | | | NPR |
12 | Q2150-X SLMB A |*| | | | NPR |
48
EN4402EN00EN_0003
© 2004 Siemens AG
4. Interrogate the module modes in LTG 1.

Input:
DISPLAY-BCSU:MODE,1;
Output:
ADDRESS | ASSIGNED MDL| TYPE | MODE
---------+-------------+---------+----------
1.1. 19 | Q2058-X | RG | UN25H65V
1.2. 25 | Q2085-X | DIUC | LWPAR1: 3 FIDX1: 10
1.4. 25 | Q2185-X | DIUC64 | LWPAR1: 3 FIDX1: 10
2. PCM PATH | LWPAR2: 2 FIDX2: 5
1.5. 31 | Q2031-X 2 | SIUP 3 | FCT. 1-8
| R2F
| R2B
| R2F
| R2B
| SOCFF
| SOCFB
| SOCFF
| SOCFB
1.5. 85 | Q2160-X | STMA | ATMPBB
1.6. 25 | Q2160-X | STMA | ATMIW
5. Interrogate a pen for autoset relocate.

Input:
DISPLAY-BCSU:PEN,1,1,55;
Output:
PEN | STATUS GERTYPE COFIDX
--------------------+---------------------------------
1. 1. 55.0 | SIGNED OFF
1. 1. 55.1 | NOT CONNECTED
1. 1. 55.2 | CONNECTED
1. 1. 55.3 | CONNECTED
1. 1. 55.4 | SIGNED OFF
1. 1. 55.5 | SIGNED OFF
1. 1. 55.6 | SIGNED OFF
1. 1. 55.7 | NOT CONNECTED
49
EN4402EN00EN_0003
© 2004 Siemens AG
6. Interrogate base stations.

Input:
DISPLAY-BCSU:PERHW;
Output:
ADDED BASIS STATIONS :
PARTNO | LOADWARE | FCT-ID

------------+----------+--------
Q5473-X | 0 | 0
7. Display Module Treshold.

Input:
DISPLAY-BCSU:FLOWCTRL,1,1;
Output:
ADDRESS | ASSIGNED MODULE FID | FC MODULE | SHORT LONG PERM | ACTIVE |
----------+-------------------------+-----------+--------------------+--------+
1.1 . 19 | Q2058-X RG | NO | - - - | |
1.1 . 25 | Q2117-X SLMS | NO | - - - | - |
1.1 . 31 | AVAILABLE | | | |
1.1 . 37 | AVAILABLE | | | |
1.1 . 43 | Q2246-X SLMA24 | NO | - - - | - |
1.1 . 49 | Q2233-X SIUX 2 | NO | - - - | - |
1.1 . 55 | AVAILABLE | | | |
1.1 . 61 | AVAILABLE | | | |
1.1 . 67 | AVAILABLE | | | |
1.1 . 73 | Q2248-X LTUCE | NO | - - - | - |
1.1 . 79 | Q2144-X SLMO | YES | 300 500 300 | NO |
1.1 . 85 | Q2144-X SLMO | YES | 300 500 300 | NO |
1.1 . 91 | Q2115-X SLMU16 | YES | 500 500 300 | NO |
1.1 . 97 | Q2150-X SLMB | NO | - - - | - |
1.1 .103 | Q2150-X SLMB | NO | - - - | - |
1.1 .109 | Q2141-X SLMA | NO | - - - | - |
1.1 .115 | Q2025-X300 TMBD | NO | - - - | - |
1.1 .121 | Q2121-X TMBCT | NO | - - - | - |
50
EN4402EN00EN_0003
© 2004 Siemens AG
8. List the data for all modules in source group 6.

Input:
DISPLAY-BCSU:SRCGRP,6;
Output:
-----+-----------+---------+---+---+-+------------+-----+--------+------------+
-----+-----------+---------+---+---+-+------------+-----+--------+------------+
19 | Q7065-X APPS |*| AVAILABLE | | | NPR |
25 | Q2117-X SLMS A |*| | | | NPR |
73 | Q2302-X NCUI 1 | | Q2302-X | 1 | -A2 - | READY |
79 | Q2144-X SLMO A | | Q2144-X | 1 | -D1 - | READY |
85 | Q2158-X SLMO24 1 A |*| | | | NPR |
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 |

-----+-----------+---------+---+---+-+------------+-----+--------+------------+
-----+-----------+---------+---+---+-+------------+-----+--------+------------+
1 | AVAILABLE | | AVAILABLE | | | NPR |
2 | Q2117-X SLMS A |*| | | | NPR |
4 | Q2302-X NCUI 1 | | Q2302-X | 1 | -A2 - | READY |
9 | Q2158-X SLMO24 1 A |*| | | | NPR |
12 | Q2150-X SLMB A |*| | | | NPR |
51
EN4402EN00EN_0003
© 2004 Siemens AG
7.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;
52
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens General Features: Protection of Software Features
8 Protection of software features (codeword)
8.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.
53
EN4402EN00EN_0003
© 2004 Siemens AG
General Features: Protection of Software Features Siemens
PNE
ComScendo CC-AP for AP Emergency
Remote Survivability Cordless E
Voice com-
Entry Agent
pression IP
CODEWORD
Protection of software features
8.2 Codeword variants
In HiPath 4000 V2.0 and later, the CODEWRD will feature four variants:
9. 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.
10. 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.
11. 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;
Dongle resp. SIM card does not match to Codeword;
54
EN4402EN00EN_0003
© 2004 Siemens AG
Components without licence and not marked as LICMARK

In the Emergency mode the AMO execution is blocked in the SWU. The only AMOs that
can be executed are the AMO CODEW / DATE.
12. 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 60 days X X
( then a new Codeword is required)
TYPE 2 (Special) Via LMT (Licence Mangement Tool)with a time X X
limit longer than 60 Days
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 try to add an older Codeword is blocked in this way.
55
EN4402EN00EN_0003
© 2004 Siemens AG
8.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-
SBCSU DVCFIG=
nels; optiip = 1 B channel, but
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
SXSU 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
56
EN4402EN00EN_0003
© 2004 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
57
EN4402EN00EN_0003
© 2004 Siemens AG
8.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.
● 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.
58
EN4402EN00EN_0003
© 2004 Siemens AG
● Further information on the AMO CODEW can be found in the AMO description in the
service manual.
8.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:
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 | |
59
EN4402EN00EN_0003
© 2004 Siemens AG
| 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;
2. 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 | | | |
+---------------------------------------------+-------+-------+-------+-------+
60
EN4402EN00EN_0003
© 2004 Siemens AG
| 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;
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;
61
EN4402EN00EN_0003
© 2004 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;
62
EN4402EN00EN_0003
© 2004 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.)
63
EN4402EN00EN_0003
© 2004 Siemens AG
8.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)
64
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: DIMSU - Feature Capacities
9 DIMSU - Feature Capacities

The AMO DIMSU allows an administrator to create and change database memory allocations
to satisfy the requirements of a particular customer.
This flexible memory administration facility is known as FLEXAMA.
The limits for memory partitioning are set at the theoretical maximum for extreme capacity con-
figurations. Standards (standard layouts) should be determined for the allocation procedure,
and the default values in the database should be used.
The variant specific maximum values of each parameter will be taken from the database.
9.1 ADD-DIMSU
This action allocates or changes the memory entries. The AMO verifies the input parameters
and displays an advisory message showing the value update (ACTUAL) in case of a valid input.
The value ACTUAL determines the number of storage elements to be assigned.
The memory allocations are processed in the sequence of the parameters in the parameter
tree.
If the requested memory space is insufficient for a specified parameter value, then an error
message is output. The memory allocations processed before the error message are correct.
The memory allocations processed for subsequent parameters after the error message are
also correct if the memory space is sufficient.
If some of the assigned storage elements are no longer required for a parameter, the ACTUAL
value can be reduced to the highest used element (MAX_USED). If no assigned storage ele-
ment is used, the ACTUAL value can be reset to 0.
Exception, parameters CCIDXS and CCIDXD: These parameters can only be in-
> creased.
Attention
7 The following parameters use only dynamic memory. The default value should be
used for these parameters (if necessary, the value can be increased).
ACDCQ, ACDLOGON, ATNDCQ, CBK, CFWHIST, COSTI, CPB, CPDBUF, DTIT-
MD, GENBUF, HGMEMB, HT, HTCQB, LODS0, LODTMD, PINBUF, SILI, SYNAN
The branch-off parameter is optional. Only parameters of the same branch can be used in one
ADD-command.
65
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: DIMSU - Feature Capacities Siemens
9.2 DISPLAY-DIMSU
Each parameter has three status values. These are as follows:
● ACTUAL
● USED
● MAX-USED
The value ACTUAL defines the number of storage elements allocated and is changed using the
action ADD.
Exception, parameter COS and LODR: The number of the created class of service
> or outdial rule for least cost routing is equivalent to the index of the memory location.
(e.g. If creating COS 1, 200 and 400 with AMO COSSU, the ACTUAL value of the
DIMSU parameter COS must be at least 400.)
The value USED describes the number of used memory elements. A comparison with the AC-
TUAL value shows how much of the allocated memory is still unused and can be used for cre-
ating devices and/or features.
The value MAX-USED describes the index of largest storage elements used. A comparison
with the ACTUAL value shows how much of the allocated memory is still free, and can be real-
located.
The reduction of the memory entries to MAX-USED can be carried out in the case of a memory
shortage, if, during operation, it is seen that ACTUAL > MAX-USED. The reduction of the mem-
ory entries to a value lower than MAX-USED is only possible if the USED value is 0.
Each further AMO which configures elements from the allocated memory pool, changes the ad-
ministration data USED and MAX-USED.
When deleting devices or features, MAX-USED is not changed.
The database contains the maximum values and default values for each parameter depending
on the capacity configuration of the system. These values can be interrogated using the DIS-
PLAY branch of the AMO.
The branch-off parameter is optional.
66
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: DIMSU - Feature Capacities
9.3 REGENERATE-DIMSU
Example
Input:
REGENERATE-DIMSU;
Output:
REGENERATE-DIMSU;
H500: AMO DIMSU STARTED
ADD-DIMSU:ADMCC,1500,1500;
ADD-DIMSU:ADMLTG,400;
ADD-DIMSU:APPLICAT,98,5,20,600,3000,256,128,256,128,
1500,512,300,900,300,256,3200,2000,2000,2000,
256;
ADD-DIMSU:BASIC,12000,12600,12000,6000,32,300,1800,2,0,
40,2400,600,800,275,1450,850,818,10,600,
3000,6000,13500,6000,55000,12042,1200,1920,1800,6000,
16000,2700;
ADD-DIMSU:NETWORK,3,400,400,200,20,512,1024,200,1000,
500,1000,60,200,50,180,0,0,1500,600;
ADD-DIMSU:SYSTEM,1980,1600,1,15,15,480,40,40,83;
ADD-DIMSU:USER,18000,2400,6000,600,1200,16,1000,2400,12000,
500,18000,1200,12000,24000,1200,20,3200,400,18000,
24000,3600,3600,63,30;
AMO-DIMSU-170 DIMENSIONING OF FEATURES, SWITCHING UNIT
REGENERATE COMPLETED;
9.4 TEST-DIMSU
This action can be used to verify that the memory capacity of a particular system is sufficient
for assigning the required feature memory dimensions. It functions similarly to the ADD com-
mand branch, the only difference being that the memory dimensions entered are not physically
assigned. When the TEST command has been executed, the advisory message H01 is output.
If the available memory is sufficient (i.e. less than 100 per cent of available memory), the pa-
rameter values of the TEST command can simply be taken over into the ADD command, with
which memory dimensions are physically assigned.
In order to verify the availability of memory space with the TEST action, only the parameter val-
ues to be changed must be entered. If no parameter values are entered the percentages of the
Flexama memory used at the moment are displayed.
Additional Flexama memory for device search (MASTERGROUPS and SUBGROUPS) is nec-
essary for adding routes (AMO RICHT), trunk groups (AMO BUEND), hunt groups (AMO SA),
night variants (AMO NAVAR) and attendant console groups (AMO VFGR). AMO LRNGZ allo-
cates speed dialing lists. This has to be considered for TEST-DIMSU in case the database is
not completely generated.
67
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: DIMSU - Feature Capacities Siemens
Examples
1. Determine percentage values of the currently allocated memory.
Input:
TEST-DIMSU;
Output:
TEST-DIMSU;
H500: AMO DIMSU STARTED
H01: CC: 65 % OF THE TOTAL STATIC MEMORY AREAS AND 41 % OF THE TOTAL
DYNAMIC MEMORY AREAS RESERVED FOR THE FLEXAMA WILL BE USED.
(UP TO 20% OF THE MEMORY MAY NOT BE AVAILABLE IF IT IS HEAVILY
FRAGMENTED).
H01: LTG: 51 % OF THE TOTAL STATIC MEMORY AREAS AND 48 % OF THE TOTAL
DYNAMIC MEMORY AREAS RESERVED FOR THE FLEXAMA WILL BE USED.
(UP TO 20% OF THE MEMORY MAY NOT BE AVAILABLE IF IT IS HEAVILY
FRAGMENTED).
AMO-DIMSU-170 DIMENSIONING OF FEATURES, SWITCHING UNIT
TEST COMPLETED;
9.5 EXEC-DIMSU
This action assigns memory according to the database default values. It is intended to simplify
the setup of a system with default feature capacities. Customer-specific variations from the de-
fault values can be done afterwards with the command ADD-DIMSU.
The memory entries which will be allocated are the same as in the action ADD-DIMSU. The
AMO checks for each memory, whether the default value is larger than the highest element cur-
rently used (MAX-USED-value).
Error message F01 is issued for all parameters where the default value is smaller than the cor-
responding MAX-USED value. This can occur only in an already created database. In this case,
the action will be executed partially. Starting with an empty database it is guaranteed that all
memory entries can be assigned with their respective default values.
68
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: ZAND-Central System Data
10 ZAND-Central System Data

The Central system data define the way features are executed, e.g. CALL TRANSFER by push
or pull, or COS expansion for Expansion of undialed lines etc...
The central system data are set to a defined value by the basic database initialisation. The val-
ues can be modified using AMO ZAND:
CHA-ZAND:TYPE=ALLDATA,... or TYPE=ALLDATA2 or TYPE=ALLDATA3;
There are further data types which are also administrated using AMO ZAND:
LCR COS settings for LCR

RNGTYPE call types
LOADWARE change loadware for individual line modules or SIU
CCM parameters for multiple CSM
CIT configures virtual stations, settlings for API interface
TONES Tone table, assignment of CP tones to SIU tones
TN Selection of country-specific settings for SIU, DTR, CONFO and CONFC
CONFC Selection of country-specific settings for CODE, CONFAT, STNAT
OPTLOAD Load optionstable from hard disk
OPTTBL Modify option table in database
CCD Modify call charge display for station and attendant
DIUSL Errortypes which cause softlocks may be entered
ATND Settings for attendant console
RESERVE Setting of reserve parameters whose meaning is descripted in the release
notes
OPTISET Settings for optiset E / optiPoint 500 devices
SIUXPER Settings for peripheral SIUX boards
ACD Settings for ACD-G
VMI Settings for Voice Mail interface
DOMAIN Settings for domain indentification of CUG
KEYSYS Settings for Key system
DIST Modify diversion sequence table
ACC Settings for account code
LEDTYPE Assigment of LED cadences to 5 LED situations
MLPP Multi-level precedence and preemption service
69
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: ZANDE Siemens
11 ZANDE
● ALLDATA
– SCALLOG Y -> Source number in callog;
After transfer the transfered subscriber (Subscriber_A)
is registered in the callog of the Subscriber_C;
N -> After transfer the transferring subscriber (Subscriber_B)
is registered in the callog of the Subscriber_C;
– VCANNCNF Y/N -> Voice Compression for conference and announcement
situations;
– H235SEC Y/N -> Activates / deactivates H.235 Security for STMI2IGW
boards;
– GATEKPR Y/N -> PBX with Large Enterprise Gatekeeper (LEGK);
– DECTPS Y/N -> Via this parameter the DECT Positioning System (laca-
ting of DECT Mobile phones) will be activated resp.
deactivated;
– NONPIIW Y/N -> For detailed describtion see ComWin300 Edit; (only
used in US);
– DAJB Y/N -> The configuring of the Jitter Buffer is not possible in the
WBM of a STMI2 board, if this parameter is set. The set-
ting in AMO STMIB branch DSP are used;
– NOVNIDCO Y/N -> Since HP4K V1.0 AMO KNMAT corrects the virtual
node ID to avoid dependences from node to node in dif-
ferent regions.If NOVNIDCO=YES is set, this behaviour
is disabled, what means, that the KNMAT modification
works like HP4K V1.0 before.
– IMPRPKZ Y/N -> If this parameter is set, both levels of one name key can
be chained for PKZ usage;
– SILMON Y/N -> If this parameter is set, Silent Monitoring is only possible
for member of the ACD group of the monitorer. If this pa-
rameter is not set, there are no restrictions to any ACD
groups.
● OPTISET
70
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: ZANDE
– EDITDIAL Y/N Edited dialing for Up0E terminals (Deleting of single

numbers by using with the arrow key (positioning) and
the “-” key; For starting the call, use the OK key);
● MLPP Multi-level precedence and preemption service;
Special feature for the army (US);
71
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: KNDEF - Virtual Nodes Siemens
12 KNDEF - Virtual Nodes

AMO KNDEF is used to administrate the virtual node table. A virtual node is a set of numbers
with the same numbering plan attributes. Each subscriber (resp. attendant console) in a net-
work belongs to exactly one virtual node. A virtual node can contain many subscribers, which
can be domiciled also in different systems (physical nodes). Thus a virtual node can cover one
or more systems and can be also one of more virtual nodes within the same system. Virtual
nodes should not be confounded with physical nodes, which determine one system within a
network and by that the network topology (see AMO ZAND parameter PNNO and AMO KN-
TOP). In a system there are two different types of virtual nodes:
1. Type OWN
2. Type FOREIGN
Virtual nodes make numbering plan attributes available to subscribers, virtual nodes of type
OWN to subscribers of the own system and virtual nodes of type FOREIGN to subscribers of
foreign systems.
Within a system at least one virtual node of type OWN must be configured. Always exactly one
of the virtual nodes from typ OWN has the attribute DFLT. Newly created subsribers are auto-
matically associated with this virtual node when nothing else is entered. The Field POPULA-
TION in the display output shows, how many subscribers of a system are assigned to a given
virtual node of type OWN. A virtual node where the field POPULATION is unequal zero cannot
be deleted.
Virtual nodes of type FOREIGN must be configurated only in exceptional cases, e.g., when a
partner node (e.g., an other system) only sends a station number which has to be extended.
For fictitious nodes, which are defined by the AMOs TACSU, TDCSU and TSCSU, generally no
entries are needed in the virtual node table. Virtual nodes that are defined in one system as
type OWN must not be defined in all other systems as type FOREIGN.
Virtual nodes are identified with a node number that consists of up to 3 levels. All (virtual and
physical) node numbers of a network must be unique and should all have the same level.
12.1 DISPLAY-KNDEF
This command allows you to display virtual nodes that are entered in the virtual node table. If
the command is entered without parameters, then all virtual nodes are displayed. The output
can be limited by parameters NNO or TYPE to one specific virtual node resp. to all virtual nodes
of a given type.
72
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: KNDEF - Virtual Nodes
Example
Output all existing virtual nodes.
Input:
DISPLAY-KNDEF;
Output:
VIRTUAL NODE TABLE
+-----------+-------+--------------+--------------+-----------+-----+-----+----+
| VIRTUAL | TYPE | ISDN (E.164) | PRIVATE(PNP) | UNKNOWN |POPU-| CAC |DFLT|
| NODE | | CC | L2 | | LA- | PRE-| |
| NUMBER | | AC | L1 | |TION | FIX | |
| | | LC SK | L0 SK | NODECD SK | | | |
| | | UL | UL | | | | |
+===========+=======+==============+==============+===========+=====+=====+====+
| 3- 1- 20 |OWN | 49 | | | 210| 010 | Y |
| | | 89 | | | | | |
| | | 722 3 | 99 2 | 100 3 | | | |
| | | EXT | EXT | | | | |
+-----------+-------+--------------+--------------+-----------+-----+-----+----+
| 3- 1- 21 |OWN | 49 | | | 108| 010 | |
| | | 89 | | | | | |
| | | 636 3 | 96 2 | 101 3 | | | |
| | | EXT | EXT | | | | |
+-----------+-------+--------------+--------------+-----------+-----+-----+----+
73
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: FEASU - Features (Bit String) in the SWU Siemens
13 FEASU - Features (Bit String) in the SWU

By means of AMO FEASU, customer-specific features (CM) can be released (activated) or
blocked (deactivated). The features are represented by symbolic abbreviations (8 characters
maximum). A somewhat longer description (50 characters max) for these abbreviations may be
obtained by entering CHANGE-FEASU:TYPE=A,CM=?;
The order of appearence for the values of parameter CM listed there was fixed by the evolution
of the AMO. A list of them is given here under the title “Parameter Description” in alphabetical
order of their English names. Feature bits that are activated in the standard customer package
are especially designated there by an asterisk in the first column of the table.
13.1 CHANGE-FEASU
Activating and deactivating features
By means of the function CHANGE FEASU features can be activated or deactivated. If the input
for parameter ’TYPE’ is equal to ’A’, the specified features will be activated. If the input for pa-
rameter ’TYPE’ is equal to ’D’, the features will be deactivated.
There are pairs within the allowed values of parameter CM which form exclusive pairs, i.e. pairs
of feature bits both of which may not be activated at one time. At present the values PININT
and PINNW (internal PIN1 and network wide PIN) as well as the the values XFBACALL and
XFBADIAL (Transfer before Answer from Call State and Transfer before Answer from Dial
State) constitute such exclusive pairs.
Examples
1. The features central speed dialing, individual speed dialing, and hunting group are to be
activated.
Input:
CHANGE-FEASU: TYPE=A,CM=SPDC&SPDCI&HTVCE;
2. The features central speed dialing, individual speed dialing, and hunting group are to be
deactivated.
Input:
CHANGE-FEASU: TYPE=D,CM=SPDC&SPDCI&HTVCE;
1. PIN: Personal Identification Number
74
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: FEASU - Features (Bit String) in the SWU
13.2 DISPLAY-FEASU
By calling DISPLAY-FEASU we obtain a list of all the features treated by the AMO divided into
two groups: the first group shows the features that are activated (if any), the second shows
those that are deactivated (if any).
Example
The state (on/off) of all features is to be shown.
Input:
DISPLAY-FEASU;
Output:
DISPL-FEASU;
H500: AMO FEASU STARTED
ACTIVATED FEATURES
SPDC SPDI HTVCE HTFAX HTDTE OVR FRKN NIGHT

COSXCD COSXKEY DCOSX COSXATND COSXT COSXDP ICPTDID HOTRCL
DND VARCONF TRACE SNR RKNOVR CBK DSS SPLIT
ONHKTRNS PU RSVCO SER ISTR RNG SYNCANN CDRINH
CDRIC CDROGNW CDROGTR DISCHINH DISCHNW DISCHTR LCRET POSTBUSY
POSTFREE RELOCATE HTNW PININT TIMEDREM ATTR CPS INCPRIO
CALOGOPT DIRCPCKP
DEACTIVATED FEATURES
CRITM LDME DDTES NOCHRG WTATND TRACCO LEDSIGN VMSDP

RELCON RERING AUTOV EMOVR EMRLS DCBB DCBNOA VOICO
PINNW ECFW XFBACALL XFBADIAL CDRE DCPA NCT RCCB
MLPP CDRACC
AMO-FEASU-237 CUSTOMER FEATURE LIST
DISPLAY COMPLETED;
75
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: AMOs in the User Area Siemens
14 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
Per STN No. personal and Voice Terminals
device-related data STNNo.
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
76
EN4402EN00EN_0003
© 2004 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
ZIEL Destination addresses for users
ZRNGZ Central number generator destinations
77
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Structure of the DPLN Siemens
15 Structure of the DPLN

Digit Analysis is comprised of a general DPLN (WABE) part and one of 16 DPLN groups.
Tabelle 3:
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.
78
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Structure of the DPLN
15.1 Overview of the CPS

Possible AMO values: 0 - 22 (from Version V 2.3 --» V 3.x )
Tabelle 4:
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
79
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: WABE - Digit Analysis Siemens
16 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).
The DARs NETW, NETWFAX and NETWDTE have a special status; for these DARs
the AMO WABE enters supplementary information (parameter DESTNO) as well as the digit
analysis result. In addition, information entered with the AMO RICHT for the NETRTE DAR is
relevant for call processing purposes.
The DAR STN in HICOM networks has a special status very similar to the DAR NETW. If an
STN is in another node, it is added in the local node with the parameter DESTNO. Then it is
used just like NETW. Every DAR STN is only permissible independently of DPLN, i.e. without
specifying the parameter DPLN.
Like the DAR STN, the DAR ATNDIND is only permissible independently of DPLN.
DAR NETRTE also has a special position: Just as with STN, it must be assigned independently
of DPLN groups and only for CPS=0, so that it cannot be directly dialed.
Associated digit analysis results are combined into a digit analysis result pair.
Some digit analysis result pairs are viable only if both parts are assigned (e.g. activate call hunt
group - deactivate call hunt group). An expanded input is provided so that such pairs can be
handled together if changes are made in the DPLN table. Parameters exist for the partner DAR
in the ADD and DELETE commands (CD2, CPS2 & CDDP2). The parameter DPLN applies to
both DARs of a pair. In the DELETE command with TYPE=CD, the partner DAR must always
be explicitly included. This is done automatically in the ADD command (default value
CHECK=ALL), even if CHECK=PART is specified. By specifying CHECK=N, the user is able to
specifically exclude the partner DAR. This can save time in some cases; however, the user
must remember to create a new partner DAR with the appropriate command. The REGENER-
ATE command generates an ADD command batch with CHECK=N in each case (i.e. with less
parameters). This speeds up a generate comand sequence because of less parameter checks.
The DARs APIN1 to APIN15 (activate personal identification number for copin1 to copin15) and
the DAR DPIN (deactivate personal identification number) have a special status within the digit
analysis result pairs. These DARs are practicable only in pairs, but have to be added with single
AMO calls. This is because there is only 1 deactivation DAR for the 15 activation DARs. Inde-
pendent of DPLN or for a specific DPLN, if one of the DARs APIN1 to APIN15 exists, the user
is responsible for ensuring that the DAR DPIN exists and vice versa.
80
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: WABE - Digit Analysis
In addition, some DARs belong to specific DAR sequences, in other words, within the specific
DPLN group and CD category a predecessor DAR must be entered before the successor DAR
in the sequence can be added. The sequence must also be adhered to when deleting. The se-
quence may be ignored if CHECK=N is specified.
Associated pairs for simultaneous processing are listed in Tabelle 16-1 and pairs for sequential
processing in Tabelle 16-2. Digit analysis results AFWDVCE, ADND and ACOSX can also be
used as ’feature toggling’ digit analysis results. Thus, in the case of these digit analysis results,
it is no longer necessary to handle them in pairs with the corresponding deactivation digit anal-
ysis results.
Simultaneous updating of the TWABE tables is not carried out automatically. In order to speed
up call processing, it is recommended that the desired data be imported with the AMO TWABE
(e.g. all CDs to DAR=STN).
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
Tabelle 16-1 Digit analysis result pairs
Must be entered in sequence

Enter first Enter second
SPDC1 SPDC2
CCS CCSURG
CCMS CCMSURG
Tabelle 16-2 DAR pairs for sequential processing
81
EN4402EN00EN_0003
© 2004 Siemens AG
There are more features connected to special DARs, e.g. there are only decimal digits allowed
with DAR STN or FLASHCD, also only 1 digit is allowed for DAR FLASHCD.
DAR for devices with dial pulse only option

If CD assigned to the DAR in question should also be available to terminals which only sup-
port the dial pulse option (previously known as pulse dialing), but contains special charac-
ters (SC),
● the parameter CDDP must be specified (except when CHECK=PART/N).
● the parameter CDDP1 must be specified in the case of DAR pairs (except when
CHECK=PART/N).
● neither the parameter CDDP nor CDDP2 may be specified in the case of a CPS ex-
pansion.
Hicom 300 / HiPath 4000 Networks:

All STN codes in a Hicom 300 / HiPath 4000 network are stored with the DAR STN in the
tables of each node. To the external STNs (these are the STNs in other nodes) the DEST-
NO is assigned with a separate CHANGE action.
With DAR NETW now only those codes are stored, that must be reached from all nodes of
the network.
If an external STN becomes an internal one, first the DESTNO must be changed to 0.
The station number (CD) of DAR OWNNODE is used for feature networking route optimi-
zation of the AMO ZAND TYPE=ALLDATA, parameter NODECD. Before changing or de-
leting this digit code, the relating information has to be changed or deleted with the AMO
ZAND.
The ISDN dial plan has been implemented via QSIG since Hicom 300 E V1.0 and V3.5.
With this dial plan it is possible to image the public dial plan on a private network.
If a Hicom system is connected to or in a network that operates using the ISDN dial plan,
the network access code to the ISDN network must be created with DAR=TIE (tie-trunk)
instead of DAR=CO (attention must also be paid here to the CPS-dependent creation of
the DAR TIE). There is no longer a CO DAR there as only the LCR decides whether the
call is routed to a real public exchange or to a carrier.
Use of the ISDN dial plan for access to systems smaller than EV1.0 / V3.5 is not allowed
in the private network.
Range inputs:
If a job with range inputs cannot be carried out completely, only the permissible entries are
made in the DPLN table. The dominant parameter is the station number or digit code (CD).
Error messages are generated for the entries that cannot be executed.
82
EN4402EN00EN_0003
© 2004 Siemens AG
CPS range:
Call progress states (CPS) cannot be specified as ranges. However, it is possible not to
specify the parameter CPS, in which case all CPSs permitted for the associated digit anal-
ysis results are intended. The permitted values are defined in a table that cannot be
changed by administration and maintenance.
The DISP-WABE TYPE=CPS command allows the user to output either the complete table or
a specific row (DAR=<param>).
Note for Optiset terminals:

The function of some digit analysis results can be called via the Optiset menu. This func-
tion is only displayed in the Optiset menu if at least one CD was set up for an Optiset-rel-
evant DAR. Optiset-relevant digit analysis results are required to be added with full CPS
range, i.e. with all CPSs permitted for the associated digit analysis result. This is achieved
by entering no value for the CPS value. The CPS range permitted for the associated digit
analysis result is stored in a read only table in the database of the system. This table, i.e.
the CPS amount of digit analysis results, can be displayed using DISPLAY-
WABE:TYPE=CPS,[DAR=<param>];.
Always create without CPS specification

ACC ACDAV ACDEMMSG ACDLOGOF ACDLOGON ACDEMMSG
ACDNAV ACDPGS ACDPQS ACDSGS ACDSQS ACWORK
ACOSX ADND AFFWDVCE AFWDREM AFWDVCE AHTVCE
APIN1 APIN2 APIN3 APIN4 APIN5 APIN10
APIN11 APIN12 APIN13 APIN14 APIN15 CBKKY
CCANS CCKY CCMANS CCMS CCMSURG CCSCD
CCSN CDRACC CONFKY CONSKY CTLS DAKY
DCOSX DDND DFFWDVCE DFWDVCE DHTVCE DICT
DISUOFF DISUON DNDKY DPIN DSSKY DTMFCONV
EOVR EXHOLDKY FWDKY FWDREM GENANS HOLDKY
HTKY IUSEKY KNOVRKY KYPROG LNRKY MBKY
MONSLNT MONTONE MSGRKY NAMEKY PARKKY PRIVKY
PUDIR RA RCTOFFKY RELEASE REMKY RLSKY
SNRKY SPDC! SPDI SPDIPROG STKY TOGGLEKY
TRACE TRNSKY VCKY VCRKY VMFOR VMOWN
Tabelle 16-3 Optiset-relevant DARs to be created without CPS specification
83
EN4402EN00EN_0003
© 2004 Siemens AG
NOTE!
If the CPS range permitted for a digit analysis result has been enlarged, e.g. caused
by a change request, all configured access codes for that digit analysis result must be
expanded to fit the new CPS range. This can be done using the command ADD-
WABE with CHECK=N. This action must be called for each access code assigned to
the respective digit analysis result (see example below). If the additional new call
progress states are specified in the ADD command, the advisory message H07 is dis-
played and the action is performed using the full new CPS range to ensure that the
CPS expansion really fits the full CPS range.
Example:
Optiset-relevant digit analysis result APIN1 has been enlarged from CPS 5 to
5&8&9&17:
DIS-WABE:TYPE=GEN,DPLN=0&&15,DAR=APIN1;
------------------------------------------------------------------------------
| DIGIT INTERPRETATION VALID FOR ALL DIAL PLANS |
------------------------------------------------------------------------------
| | CALL PROGRESS STATE | DIGIT | RESERVED/DIALCONV|
| CODE | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| 881 |. ....* ..... ..... ..... ..| APIN1 | |
| *81 |. ....* ..... ..... ..... ..| APIN1 | |
------------------------------------------------------------------------------
DIS-WABE:TYPE=CPS,DAR=APIN1;
-----------------------------------------
| STANDARD CPS SUBSETS |
-----------------------------------------
| | 1 11111 11112 22|
| DAR |0 12345 67890 12345 67890 12|
-----------------------------------------
| APIN1 |. ....* ..**. ..... .*... ..|
-----------------------------------------
84
EN4402EN00EN_0003
© 2004 Siemens AG
Expand the access codes *81 and 881 assigned to the respective digit analysis result
APIN1 to the full CPS range using the command ADD-WABE with CHECK=N (one
command, giving the new, additional CPS values - therefore H07 - and one command
without parameter CPS):
ADD-WABE:CD=881,CPS=8&9&17,DAR=APIN1,CHECK=N;
H07: OPTISET-RELEVANT DAR MUST ALWAYS HAVE FULL CPS SET.
- PARAMETER CPS WILL BE IGNORED.
- ACTION CONTINUES WITH FULL CPS SET.
ADDITION COMPLETE;
ADD-WABE:CD=*81,DAR=APIN1,CHECK=N;
ADDITION COMPLETE;
DISP-WABE:TYPE=GENERAL,DAR=APIN1;
------------------------------------------------------------------------------
------------------------------------------------------------------------------
| | CALL PROGRESS STATE | DIGIT | RESERVED/CONVERT |
| CODE | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| 881 |. ....* ..**. ..... .*... ..| APIN1 | |
| *81 |. ....* ..**. ..... .*... ..| APIN1 | |
------------------------------------------------------------------------------
16.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.
When DARs for central offices and tie trunks are created, the AMO prevents the assignment of
another CO/tie trunk DAR to the same station number using different CPS‘s only. The assign-
ment is also prevented in the case of various long station numbers for CO and tie trunk DARs
that correspond up to the number of digits of the shorter station number.
85
EN4402EN00EN_0003
© 2004 Siemens AG
When a DAR for station is created, the AMO prevents the assignment of an individual attendant
console DAR to the same station number using different CPS‘s only and vice versa. This is
because stations are stored in station line memory only depending of the station number, but
data cannot be stored depending on CPS.
The DAR NETRTE can be preset for a suitable route with the AMO WABE. The connection
between all DARs NETW, NETWFAX and NETWDTE with the same DESTNO and a suitable
NETRTE must be set up with the AMO RICHT.
If CHECK is not specified, CHECK=ALL is taken as default value.
The DAR STN can be marked as external with DESTNO as supplementary information. For op-
erating reasons, the DESTNO should only be specified for individual STNs in the ADD com-
mand but for ranges in the CHA command. In the case of regeneration, normal ADD commands
(without DESTNO) are also created for the external STN, followed by a list of CHA commands
sorted in ascending order added to the end.
Station numbers for DAR=STN should, where possible, be set up in closed ranges. This applies
both to external and internal STNs, as no external/internal distinction is made in WABE. This
saves a significant amount of memory and runtime.
The specification of a value greater than 00 for the parameter ARN is only permitted in the case
of a CD containing up to 4 digits and the DAR OWNNODE. The CD is then assigned to the ARN
as office code for call number display. This action overwrites any previous office code assignment.
The assignment of CFREMVAR and/or CFREMSE is only permitted in the case of the DARs
AFWDREM, DFWDREM and FWDREM.
Station number categories

A number of special characters cannot be dialed from all terminals. The digits are therefore split
into categories:
a) A,B,C,D only for devices with a 16-key keypad
b) *, # also for devices with a 12-key keypad
c) 0...9 for all devices
The highest value that occurs must correspond in both specified access codes.
Examples:
CD=A35 CD2=C* permitted
CD=#5 CD2=*48 permitted
CD=#A37 CD2=B permitted
CD=A CD2=# not permitted
CD=*12 CD2=123 not permitted
The following table provides a summary of the possible combinations of input parameters.
86
EN4402EN00EN_0003
© 2004 Siemens AG
Add CHECK CD CDDP CD2 CDDP2

1. Indep. DAR w/o SC in any case DARw/oSC
2. " " with SC PART,N DAR w SC
3. " " " SC (ALL) DAR w SC DARw/oSC
4. DAR pair w/o SC (ALL),PART DARw/oSC DARw/oSC
5. " " " SC N DARw/oSC
6. " " with SC (ALL) DAR w SC DARw/oSC DAR w SC DARw/oSC
7. " " " SC PART DAR w SC DAR w SC
8. " " " SC N DAR w SC
Explanation:
SC: Special Characters
Digit analysis result without special characters
Digit analysis result with special characters
CD,CD2: Code 0 to 9, *, #, A to D
CDDP,CDDP2: Code for dial pulsing devices 0 to 9
Tabelle 16-4 Combinations of possible input parameters
Examples
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;
2. Assign the DAR ’saved number redial’ in DPLN group 2, for the CPSs ’station prefix dialing’,
’in-house consultation’, ’CO consultation’; code = *11 for dial pulsing = 5111.
Input:
ADD-WABE:CD=*11,DPLN=2,CPS=5&8&9,DAR=SNR,CDDP=5111;
3. Assign the DAR ’add station to hunt group, voice’ in DPLN group 2 for all CPSs allowed for
AHTVCE, with code = *56, dial pulsing = 5156. Since the DAR is part of a DAR pair,
reporting of the partner code = #56 or 5256 in the CPS = ’station prefix dialing’.
Input:
ADD-WABE:CD=*56,DPLN=2,DAR=AHTVCE,CDDP=5156,CD2=#56,CPS2=5,CDDP2=5256;
4. Assign the DAR ’network point’, without taking individual DPLN groups into account, in all
CPSs provided for CDs 4800 to 4999, with DESTNO 213.
87
EN4402EN00EN_0003
© 2004 Siemens AG
Input:
ADD-WABE:CD=4800&&4999,DAR=NETW,DESTNO=213;
5. Assign the DAR ’add station to hunt group, voice’ in DPLN group 3, for all CPSs permitted
for this DAR and CD = *86. Assign the partner DAR ’DHTVCE’ with CD2 = #86, without
associated DP station numbers.
Input:
ADD-WABE:CD=*86,DPLN=3,DAR=AHTVCE,CHECK=PART,CD2=#86;
CPS expansion
Each DAR is assigned a fixed range of possible CPSs (display with DIS-WABE:TYPE=CPS).
By specifying the parameter CPS, a CD for a DAR can also be added for a subset of the pos-
sible CPSs of a DAR. The CD can be extended to the other CPSs by repeating the ADD action.
Please note that the parameters CDDP, CD2 and CDDP2 must not be specified. The ADD ac-
tion must be activated separately for CPS expansion for the CDDP, CD2 and CDDP2 station
number. A CPS expansion is only possible for the applicable CPS range: for the relevant DAR,
provided a DAR has not yet been assigned for this CD/CPS combination (neither this nor an-
other).
Example:
1. Add a DAR pair with CPS subset (specify parameter CD2)
Input:
ADD-WABE:CD=*75,CPS=1,DAR=CAFAFWD,CD2=#75,CPS2=1;
2. CPS expansion for the new station numbers of the DAR pair (parameter CD2 must not be
specified - separate ADD command necessary for partner DAR)
Input:
ADD-WABE:CD=*75,CPS=5,DAR=CAFAFWD;
ADD-WABE:CD=#75,CPS=5,DAR=CAFDFWD;
3. Add a DAR for devices with dial pulse only option with DAR subset (specify parameter
CDDP)
Input:
ADD-WABE:CD=*76,CPS=2,DAR=HUNT,CDDP=876;
4. CPS expansion for the new station numbers of the DAR for devices with dial pulse only
option (parameter CDDP must not be specified - separate ADD command necessary for
CDDP station number)
88
EN4402EN00EN_0003
© 2004 Siemens AG
Input:
ADD-WABE:CD=*76,CPS=3,DAR=HUNT;
ADD-WABE:CD=876,CPS=3,DAR=HUNT;
16.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
’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.
89
EN4402EN00EN_0003
© 2004 Siemens AG
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:
------------------------------------------------------------------------------
------------------------------------------------------------------------------
| STATION NUMBER | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| 812 |. ....* ..... ..... ..... ..| ADND | |
| *12 |. ....* ..... ..... ..... ..| ADND | |
------------------------------------------------------------------------------
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;
90
EN4402EN00EN_0003
© 2004 Siemens AG
Output:
------------------------------------------------------------------------------
------------------------------------------------------------------------------
| 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 | |
------------------------------------------------------------------------
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 |
-----------------------------
91
EN4402EN00EN_0003
© 2004 Siemens AG
| 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 |. .**** ***** **... ..... .. |
-----------------------------------------
5. Display the data for the STNs with DNNO 9-137-48.
Input:
DIS-WABE:DNNO,9-137-48;
Output:
-----------------------------
| STN FOR DNNO 9-137- 48 |
----------------------------
| 30067 - 30096 |
| 32518 - 32519 |
-----------------------------
92
EN4402EN00EN_0003
© 2004 Siemens AG
16.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,,,,, , ;
93
EN4402EN00EN_0003
© 2004 Siemens AG
ADD-WABE: 7A , 2, , NETW , N,,,,, 213, ;

CHANGE-WABE: 3127 &&3136 , 172;
CHANGE-WABE: 3137 &&3139 , 11;
94
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: VBZ - Internal Traffic Restrictions
17 VBZ - Internal Traffic Restrictions

The internal traffic restriction matrix regulates communications among the traffic groups (ITR
groups). Stations and trunks are combined into ITR groups which have an identical traffic re-
striction matrix, i.e. which have the same traffic restrictions to other ITR groups.
Relations between ITR groups can be set up and changed as desired with the ITR matrix.
Only a portion of the total communications of the switching unit is regulated with the ITR matrix.
The matrix is only queried when the dialing outcome is a station (also master station in a hunt
group).
The following traffic relations between two groups are possible:
● A = allowed
● D = denied
Thus directional traffic restrictions between two ITR groups can also be regulated.
E.g.: ITR-Gr 05 --> 03 allowed

ITR-Gr 03 --> 05 denied
The trafic relation within one group must always be allowed. For that reason, the diagonal line
of the matrix may not be altered (always contains the entry "A").
A second static matrix is used to regulate traffic relations between card users and card readers.
This matrix is administrated by the AMO VBZA.
The features "controlled station restriction" and "controlled station restriction - group", as well
as "controlled station-to-station restriction", do not affect the ITR matrix. For these features, a
separate table exists, which is administrated by the AMO ACTDA.
The ITR matrix is created from the database and initialized with A (= allowed). As a result, an
ADD branch for the AMO VBZ is not necessary.
17.1 CHANGE-VBZ
Example
The denied traffic relations in both directions between groups 00 and 13 are to be allowed.
Input:
CHANGE-VBZ:ITRSRC=00,ITRGR=AA,ITRDEST=13,EXEC=Y;
95
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: VBZ - Internal Traffic Restrictions Siemens
17.2 DISPLAY-VBZ
Display the traffic restrictions between traffic groups. Output in the form of a matrix.
Example
Display the ITR matrix.
Input:
DISPLAY-VBZ;
Output:
| ITR-GROUPS (DESTINATION)
ITR - |
MATRIX | 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
----------|-----------------------------------------------
0 | A D D A A A D A A A D D A A A D
1 | A A A A D D A D A A A A A D D D
3 | D D D A D D D D D D D D D D D D
4 | D D D D A D D D D D D D D D D D
5 | D D D D D A D D D D D D D D D D
ITR-GROUPS 6 | D D D D D D A D D D D D D D D D
7 | D D D D D D D A D D D D D D D D
(SOURCE) 8 | D D D D D D D D A D D D D D D D
9 | D D D D D D D D D A D D D D D D
10 | D D D D D D D D D D A D D D D D
11 | D D D D D D D D D D D A D D D D
12 | D D D D D D D D D D D D A D D D
-----------------------------------------------------------
(A=allowed,D=denied)
96
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: ACTDA - Activation of User Features
18 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 ad-
ministration 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
97
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: ACTDA - Activation of User Features Siemens
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)
18.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.
98
EN4402EN00EN_0003
© 2004 Siemens AG
18.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;
Note:
If one of the parameters CFVAR, DTYPE, ITYPE or SI is specified, only the corresponding for-
warding destination is interrogated. For parameters that have not been specified, every possi-
ble value is interrogated. In the example above every FWD that has been found for service FAX
is deactivated for the station.
18.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 |
99
EN4402EN00EN_0003
© 2004 Siemens AG
| SPKRVOL : 2 ROOMCHAR: NORMAL |

+--------------------------------------------------------------------+
+--------------------------------------------------------------------+
+--------------------------------------------------------------------+
| DIVERSION : |
| DESTINATION NUMBER | CFVAR | DTYPE | ITYPE | SI |
| | | | | |
+------------------------+----------+----------+----------+----------+
| 08972247230 | STATIONV | CFU | EXT | VCE |
| 03038652226 | STATIONV | CFU | GEN | FAX |
+------------+-----------+----------+----------+----------+----------+
+------------+-----------+----------+----------+----------+----------+
| | x | | | 11:00 | |
+------------+-----------+----------+----------+----------+----------+
+--------------------------------------------------------------------+
| SWITCHED OUT OF HUNT GROUP IN SERVICE: VCE |
+------------+-----------+----------+----------+----------+----------+
+--------------------------------------------------------------------+
+------------+-----------+----------+----------+----------+----------+
+------------+-----------+----------+----------+----------+----------+
| | x | | | 11:00 | |
+------------+-----------+----------+----------+----------+----------+
+--------------------------------------------------------------------+
Note:
Only those parts of the table that contain data are displayed.
100
EN4402EN00EN_0003
© 2004 Siemens AG
2. Display the features for the ITR groups.

Input:
DISPLAY-ACTDA:ITR;
Output:
+------------------+
| ITR DNDGR ISTR |
| |
| 0 X X |
| 1 X |
| 2 X |
| 3 X X |
| 4 X |
| 5 X |
| 6 X |
| 7 X |
| 8 X X |
| 9 X |
| 10 X |
| 11 X X |
| 12 X |
| 13 X X |
| 14 X |
| 15 X |
+------------------+
3. Display the features for the ATND groups

Input:
DISPLAY-ACTDA:ATNDGR;
Output:
+-------------+
|ATNDGR NOPT |
| |
| 0 1 |
| 1 1 |
+-------------+
18.4 REGENERATE-ACTDA
Regenerate the changed database entries.
Note
VCR deactivated by DELETE-ACTDA will not be regenerated!
101
EN4402EN00EN_0003
© 2004 Siemens AG
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;
102
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: ZIEL - Destination Addresses for Stations
19 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).
103
EN4402EN00EN_0003
© 2004 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.
104
EN4402EN00EN_0003
© 2004 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).
105
EN4402EN00EN_0003
© 2004 Siemens AG
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.
Entries for dialling external servers

Any INFO 2000 server can be connected via a Common Voice Mail Interface (EVM). To this
end, the type of seizure of the server, a master hunting group number for dialing the server, and
if necessary, a call code for identifying the call code for PREDIA=Y (AMO SCSU) must be as-
signed to one another.
The following types of seizure are implemented:
FWD Call Forwarding

FWDNANS Seizure after no answer forward
DSZINT Direct Seizure internal
DSZCO Direct Seizure CO Call
EXPR Expressbox Seizure - achieved through suffix dialing
ATND Seizure for EVM Attendant - allows simplified recording of messages without
specifying ID or mailbox number
The following types of seizure can be grouped together:
● FWD/FWDNANS
● DSZINT/DSZCO/EXPR/ATND
If the type of seizure is entered in concatenated form, the AMO does not check for the validity
of the entry.
The station number assigned to the type of seizure must be the station number of a master
hunting group. The AMO simply checks as to whether the station number leads to the digit anal-
ysis result STN.
106
EN4402EN00EN_0003
© 2004 Siemens AG
If the interfaces with the server have been parameterized as PREDIA=Y using AMO SCSU,
each type of seizure must be assigned a call code; for PREDIA=N, the call code should not be
specified. The AMO does not check this interrelationship. The call code must match the server.
Entries for message retrieval using the START key

When the START key is pressed to retrieve voice or FAX messages from an external server,
the server must first be identified. For the VOICE service, the code VMWON is entered in the
database; for the FAX service, the codes FAX and VMOWN are entered.
If the server is located in a remote node, the code NETW or TIE is entered for the VOICE ser-
vice and the codes FAX and NETW or FAX and TIE are entered for the FAX service in the da-
tabase of the local node.
19.1 Key Layout of the Digital Voice Terminals

For standard key layout numbers for programmable function keys, see AMO TAPRO.
19.1.1 ADD-ZIEL
Creation of destinations for
1. call forwarding - fixed
2. messenger call
3. DSS keys
4. name/repertory keys
5. individual speed dialer
6. saved no. redial
7. DDS keys for attendant console
8. BUZZ feature
Enter data for
9. dialing external servers to deposit messages
10. identifying external servers when retrieving messages with the START key
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:
107
EN4402EN00EN_0003
© 2004 Siemens AG
ADD-ZIEL:TYPE=FWD,SRCNO=2100,SI=VCE,DESTNOF=3101,DTYPE=CFNR,ITYPE=GEN
,CFVAR=SYSTEM;
19.1.2 DELETE-ZIEL
Cancel destinations for:
2. messenger call
3. DSS keys
5. individual speed dialer
6. saved no. redial
7. DDS keys
8. BUZZ feature
Delete data for
Note
If one or more of the parameters CFVAR, DTYPE, ITYPE or SI is entered, the AMO deletes
forwarding destinations to the entered values, otherwise destinations to all possible values of
the not entered parameters are deleted.
19.1.3 DISPLAY-ZIEL
Interrogate destinations for
2. messenger call
3. DSS keys
5. individual speed dialing
6. saved no. redial
7. DDS keys
108
EN4402EN00EN_0003
© 2004 Siemens AG
8. BUZZ feature
9. all specified features
Interrogate data for
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
Display EVM-Server
Input:
DISPLAY-ZIEL:TYPE=EVMTAB;
Output:
EVMTAB
SZTYPE | EVMCD | SZCD
--------+-------+----------
FWD | |
FWDNANS| |
DSZINT | |
DSZCO | |
EXPR | |
ATND | |
Display EVMACC
Input:
DISPLAY=ZIEL:TYPE=EVMACC;
Output:
SERVER
EVMACC | MRCD
109
EN4402EN00EN_0003
© 2004 Siemens AG
-------+---------
VCE |
FAX |
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;
110
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: COSSU - Classes of Service
20 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. The pertinent authorizations
are identified in Table 1 in the “Application” column (AMO TACSU, AMO TDCSU, AMO TSCSU).
Each class of service is divided into three services:
● Voice (VCE)
● Facsimile (FAX)
● Data Terminal Equipment (DTE)
The authorizations for the corresponding services are summarized in Table 1.
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.
● For the
– release control,
– rering and
– automatic override
China features, three voice authorizations (RELCON, RERING, AUTOV) have been intro-
duced as well as the external classes of service COEX 1-16 (Class of External), which are
assigned to both the internal and the external station in the system. In addition to the three
authorizations listed above, these COEX contain all the authorizations of the standard
COS.
111
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: COSSU - Classes of Service Siemens
By means of CHA-COSSU:TYPE=COEX,COEX=<number>,COS=<number>;
the max. 16 COEX are assigned to a configured COS containing the corresponding autho-
rizations.
One of the 16 COEX with the value COEX in the COS1 and COS2 (AMO SBCSU/SCSU/
SSCSU) is assigned to the internal station.
For incoming traffic, the pertinent authorizations of the external station are transferred by
means of MFC signaling and translated to COEX (1-16) in the system in the MFC tables
(AMO-MFCTA).
20.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
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:;
5. Assign an external COS (COEX).
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.
112
EN4402EN00EN_0003
© 2004 Siemens AG
Examples
1. Add a new COS (see item 3.) with the voice authorizations RTA1, RTA6, 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:
20.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.
1. Change one or more classes of service with the specified parameters. The same COS can
be generated several times.
For information on the special characteristics of direct trunk/tie trunk access authoriza-
tions, see the parameter description.
The COEX parameter has been added for the China features. This parameter can be used
to assign an “external class of service” (COEX 1-16) to a COS (also see introduction to
AMO).
This assignment can be deleted by specifying COEX=0.
113
EN4402EN00EN_0003
© 2004 Siemens AG
2. Assign authorizations to a COEX (external class of service).

This is done by specifying a COS in which the pertinent authorizations (e.g. RELCON, RE-
RING and AUTOV) are set.
This assignment can be changed by specifying a different COS.
“Deletion” of a COEX by removing the assignment to a COS is not available because it is
unnecessary.
3. Insert and delete LCR classes of service for voice, fax.
4. Insert and delete LCR classes of service for data (DTE).
Examples
1. Change authorizations in COS 16.
(delete BASIC for FAX, insert RTA3 for voice)
CHANGE-COSSU:TYPE=COS,COS=16,AVCE=RTA3,DFAX=BASIC;
2. Assign COEX 1 to COS 4.
CHANGE-COSSU:TYPE=COS,COS=4,COEX=1;
3. Assign an existing COS 50 with China authorizations (such as RELCON, RERING or AU-
TOV) to COEX 1.
CHANGE-COSSU:TYPE=COEX,COEX=1,COS=50;
4. Delete the COEX from COS 4.
CHANGE-COSSU:TYPE=COS,COS=4,COEX=0;
5. The LCR class of service 1 should not contain any LCR authorization.
CHANGE-COSSU:TYPE=LCOS,LCOS=1;
20.3 DELETE-COSSU
Classes of service can be deleted provided that they are not used by any stations or trunk cir-
cuits and are not assigned to a COEX.
Example
Delete COS 27.
DELETE-COSSU:COS=27;
114
EN4402EN00EN_0003
© 2004 Siemens AG
20.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 (COND = SUBSET parameter) or
the identical COS (COND = EQUAL parameter).
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).
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 |
115
EN4402EN00EN_0003
© 2004 Siemens AG
| | 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 | | | |
+----------+----------+----------+----------+----------+
3. Display COEX and the associated classes of service.

DISPLAY-COSSU:TYPE=COEX;
Output:
+------+-----+
| COEX | COS |
+------+-----+
| 1 | 50 |
| 2 | - |
| 3 | - |
| 4 | 51 |
| 5 | - |
| 6 | - |
| 7 | - |
| 8 | - |
| 9 | - |
| 10 | - |
| 11 | - |
| 12 | - |
| 13 | - |
| 14 | - |
116
EN4402EN00EN_0003
© 2004 Siemens AG
| 15 | - |
| 16 | - |
+------+-----+
4. 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|................................................................| . |
+----+----------------------------------------------------------------+-----+
5. 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 |
+---- +-----------------------------------------------------------------+
117
EN4402EN00EN_0003
© 2004 Siemens AG
6. 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 |
+----+----------------------------------------------------------------+-----+
20.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,,,,,,,,,,,;
118
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: BERUM - Class of Service Switchover
21 BERUM - Class of Service Switchover

Stations are allocated two classes of service (COS1 and COS2) in (COS1 = normal or day COS
COS2 = alternative or night COS) in their line tables.
The class of service are maintained by AMO COSSU and assigned to stations with the AMOs
SCSU and SBCSU.
An identifier (COS pointer) in the line tables indicates which COS is active.
AMO SCSU and AMO SBCSU subdivides the stations into COS switchover groups (COSX
groups). This is performed in order to group stations so that a certain COS can be switched
active for all of them.
If no specific allocation has been made, a station belongs to COSX group 00. Stations with an
active key switch (KEYSTN) are not changed over, but they are still assigned to a COSX group.
The COSX groups are independent of other station groups formed on the basis of other fea-
tures.
Switchover between the two classes of service can be performed from a station, from an atten-
dant console, centrally using the AMO, via data channel and/or by means of a timed switchover.
a) COS Switchover from the Station
A station authorized for this type of switchover can switch over between the COSs us-
ing the personal ID number (PIN) and a code for switchover using an active key switch
(KEYSTN).
As long as the alternative COS (COS2) is active, the user hears the special dial tone
when he lifts the receiver.
The station is assigned the authorization COSXCD (COS switchover by code) by AMO
COSSU in order to be able to perform a switchover using the PIN.
The PIN (maximum of 12 digits) is defined by the AMO PERSI.
b) COS Switchover from the Attendant Console (ATND)
Switchover of the normal COS of the COSX groups to an alternative COS can be per-
formed from every attendant console, including the night attendant console (performed
with the task BEZUM).
c) COS Switchover by AMO
COS switchover for COSX groups of stations can be performed using the AMO
BERUM.
d) COS switchover using a data processing system (DVA) is implemented via a data
channel.
e) Automatic COS Switchover
119
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: BERUM - Class of Service Switchover Siemens
The COS switchover for COSX groups can be carried out automatically at a specific,
definable time. This time is defined using the AMO BERUZ (time table for times at
which class of service switchover is to occur). Switchover is carried out by the task
BEZUM.
Priorities for COS Switchover

The last COS switchover performed for a station is always in effect, regardless of where this
change was carried out (from the station, from the attendant console or automatically).
21.1 CHANGE-BERUM
Enter the code indicating which COS is active.
1. For stations (TYPE=STN)
Activate a selected or alternative COS.
2. for COSX groups (TYPE=COSX)
Activate a selected COS.
For stations associated with a DCI, the code (COS pointer) is also changed in the line tables of
the DCI.
If the active state of at least one COSX group is changed, the AMO initiates updating of the
instant display buffers of all attendant consoles.
Note
Switchover is not possible for stations with key-lock (COS KEYSTN).
Examples
1. Switch COS2 to active for stations 2100, 2106, and 2121-2139.
Input:
CHANGE-BERUM:TYPE=STN,STNO=2100&2106&2121&&2139,COSACT=2;
Output:
F02 : 2123 IS NOT A STATION NUMBER
CHANGE PARTIALLY COMPLETED;
2. Switch COS2 to active for COSX group 1-2

Input:
CHANGE-BERUM:BUM,1&2,2;
120
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: BERUM - Class of Service Switchover
3. Change the active state for station 2109 to the alternative COS
Input:
CHANGE-BERUM:STN,2109;
21.2 DISPLAY-BERUM
Interrogate the active COS state, output the code (COS pointer) indicating which COS is active
1. For specific stations (TYPE=STN)
2. For specific COS switchover groups (TYPE=COSX)
3. For all stations (TYPE=ALLSTN)
4. For all COS switchover groups (TYPE=ALLCOSX)
Example
1. Interrogate the active states of stations 2100, 2105, and 2121 through 2140.
Input:
DISPLAY-BERUM:TYPE=STN,STNO=2100&2105&2121&&2140;
Output:
+===========================================================================+
| CLASS OF SERVICE SWITCHOVER FOR S T A T I O N S |
+===========================================================================+
| CA : COS POINTER ( =1 : COS1 IS ACTIVE, =2 : COS2 IS ACTIVE ) |
| CD=A : STATION WITH KEY-LOCK (KEYSTN) - NO SWITCHOVER |
+------------------+------------------+------------------+------------------+
| C C | C C | C C | C C |
| STNO COS A D | STNO COS A D | STNO COS A D | STNO COS A D |
+------------------+------------------+------------------+------------------+
| 2100 1 1 | 2105 3 1 | 2121 11 1 | 2122 11 1 |
| 2124 11 1 | 2125 11 1 | 2126 11 1 | 2127 11 1 |
| 2128 11 1 | 2129 11 1 | 2130 11 1 | 2131 11 1 |
| 2132 13 1 | 2133 13 1 | 2134 13 1 | 2135 13 1 |
| 2136 13 1 | 2137 13 1 | 2138 13 1 | 2139 13 1 |
+===========================================================================+
2. Interrogate the active states of COS switchover groups 4 to 9.

Input:
DISPLAY-BERUM:TYPE=COSX,COSX=4&&9;
121
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: BERUM - Class of Service Switchover Siemens
Output:
+===========================================================================+
| CLASS OF SERVICE SWITCHOVER FOR CLASS OF SERVICE SWITCHOVER GROUPS |
+===========================================================================+
| |
| CA : COS POINTER ( =1 : COS1 IS ACTIVE , =2 : COS2 IS ACTIVE ) |
| CD=A : STATION WITH KEY-LOCK (KEYSTN) - NO SWITCHOVER |
| COS1/COS2 : ACTIVE COS OF COSX |
+------------------+------------------+------------------+------------------+
| C C | C C | C C | C C |
| STNO COS A D | STNO COS A D | STNO COS A D | STNO COS A D |
+------------------+------------------+------------------+------------------+
+-COSX 4 (COS2)---+------------------+------------------+------------------+
| 2109 1 2 | 2110 1 2 | 3122 5 2 A | 3125 6 1 A |
| 3131 7 1 A | 3133 7 1 A | 3135 7 1 A | |
+-COSX 5 (COS1)---+------------------+------------------+------------------+
| 2111 1 1 | 2112 1 1 | 3110 6 1 A | 3123 5 1 A |
| 3132 7 1 A | 3134 7 1 A | 3136 7 1 A | 3137 6 1 A |
+===========================================================================+
122
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: BERUZ - Times at which Class of Service Switchover is to Oc-
22 BERUZ - Times at which Class of Service

Switchover is to Occur
Stations (configured by AMO SCSU and AMO SBCSU) are allocated two classes of service
COS1 and COS2) in their line tables. A class of service contains the authorizations of a station.
An identifier (COS pointer) in the line tables indicates which COS is active, i.e. which of the sta-
tion’s authorizations are currently activated; this is usually COS1.
AMO SCSU and AMO SBCSU subdivides stations into COS switchover groups. This is per-
formed in order to group stations so that a certain COS can be switched active for all of them.
The COSX groups are independant of other station groups formed by other features.
If no specific allocation has been made, a station belongs to COSX group 0. Stations with an
active key switch (KEYSTN) are not switched over, but they are still assigned to a COSX group.
The classes of service can be switched over from a station, from an attendant console, y means
of AMO BERUM, via data channel, and/or by means of a timed switchover.
Switchover at a fixed Time (timed Switchover)
A table is created in the database, in which the following data is entered for each day of the
week and for each COS switchover group:
● A time at which COS1 is switched to active (COS1T),
● A time at which COS2 is switched to active (COS2T),
● A program switch indicating whether the displayed switchover to COS1 is to be carried out
on that day (COS1),
● A program switch indicating whether the displayed switchover to COS2 is to be carried out
on that day (COS2).
AMO BERUZ administrates this table. (The switchover is carried out with the task BEZUM.)
MON(1) TUE(2) WED(3) THU(4) FRI(5) SAT(6) SUN(7)
06.55 06.55 06.55 06.55 06.55 00.00 00.00
COSX 0 15.40 15.40 15.40 15.40 15.40 00.00 00.00
off/on off/on on/on on/on on/on off/off off/off
06.55 06.55 06.55 06.55 06.55 00.00 00.00
COSX 1 15.40 15.40 15.40 15.40 15.40 00.00 00.00
on/on on/on on/on on/on on/on off/off off/off
06.55 06.55 06.55 06.55 06.55 00.00 00.00
COSX 2 15.40 15.40 15.40 15.40 15.40 12.00 12.00
on/on on/on on/on on/on on/on on/on off/off
...............................
Table 2 Layout of the time table
123
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: BERUZ - Times at which Class of Service Switchover is to Oc- Siemens
MON(1) TUE(2) WED(3) THU(4) FRI(5) SAT(6) SUN(7)

00.00 00.00 00.00 00.00 00.00 00.00 00.00
COSX15 00.00 00.00 00.00 00.00 00.00 00.00 00.00
off/off off/off off/off off/off off/off off/off off/off
(COSX = Class of service switchover group)
Table 2 Layout of the time table

This table is implemented as a static FIXAMA table.
22.1 ADD-BERUZ
Assign switchover times
The following is entered in the table:
● Two time entries which determine the switchover time (COS1T, COS2T).
● A pair of program switches (COS1, COS2).
● One or more COS switchover groups and one or more days of the week.
Values already contained in the table are overwritten.
Examples
1. For COS switchover groups 0 to 2, entries are to be made for Monday to Friday and the
times 6:55 each day for switchover to COS1 and 15:40 each day for switchover to COS2.
The switchovers are to be carried out.
Input:
ADD-BERUZ:COSX=0&&2,DAY=1&&5,COS1T=06-55,COS1=ON,COS2T=15-40,COS2=ON;
2. No switchover is to be made for groups 0 and 1 on the weekend, and the times 00.00 and
12.00 are to be entered for group 2, where switchover is to be carried initially only on Sat-
urday.
a) Input:
ADD-BERUZ:COSX=0&1,DAY=6&7,COS1=OFF,COS2=OFF;
b) Input:
ADD-BERUZ:COSX=2,DAY=6&7,COS1T=00-00,COS1=ON,COS2T=12-00,COS2=ON;
c) Input:
ADD-BERUZ:COSX=2,DAY=7,COS1=OFF,COS2=OFF;
124
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: BERUZ - Times at which Class of Service Switchover is to Oc-
22.2 DISPLAY-BERUZ
Interrogate the entries for one, several, or all of the COS switchover groups. The output is gen-
erated in a tabular form.
Example
Interrogate all COSX groups
Input:
DISPLAY-BERUZ:0&&2;
Output:
+------------------------------------------------------------------------------+
| |
| TIME ENTRIES FOR AUTOMATIC TIMED CLASS OF SERVICE SWITCHOVER |
| |
| UPPER TIME : COS1 IS ACTIVATED |
| LOWER TIME : COS2 IS ACTIVATED |
| (HH.MM) : SWITCHOVER AT SPECIFIED TIME IS SUPPRESSED |
| |
| COSX = CLASS OF SERVICE SWITCHOVER GROUP |
| C = ACTIVE COS OF GROUP ( 1=COS1, 2=COS2, OTHERWISE:NONEXST) |
| |
+------+-+---------+---------+---------+---------+---------+---------+---------+
| COSX |C| MON(1) | TUE(2) | WED(3) | THU(4) | FRI(5) | SAT(6) | SUN(7) |
+------+-+---------+---------+---------+---------+---------+---------+---------+
| |1| (06.55) | 06.55 | 06.55 | 06.55 | 06.55 | (00.00) | (00.00) |
| 0 | | 15.40 | (15.40) | 15.40 | 15.40 | 15.40 | (00.00) | (00.00) |
+------+-+---------+---------+---------+---------+---------+---------+---------+
| | | 06.55 | 06.55 | 06.55 | 06.55 | 06.55 | (00.00) | (00.00) |
| 1 |2| 15.40 | 15.40 | 15.40 | 15.40 | 15.40 | (00.00) | (00.00) |
+------+-+---------+---------+---------+---------+---------+---------+---------+
| | | 06.55 | 06.55 | 06.55 | 06.55 | 06.55 | 00.00 | (00.00) |
| 2 |2| 15.40 | 15.40 | 15.40 | 15.40 | 15.40 | 12.00 | (12.00) |
+------+-+---------+---------+---------+---------+---------+---------+---------+
+------+-+---------+---------+---------+---------+---------+---------+---------+
22.3 REGENERATE-BERUZ
Interrogate the entries for one, several, or all COS switchover groups. The output is generated
as a command listing for the ADD action of the AMO.
Example
Regenerate COSX groups 0-2.
125
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: BERUZ - Times at which Class of Service Switchover is to Oc- Siemens
Input:
REGENERATE-BERUZ:COSX=0&&2;
Output:
ADD-BERUZ: 0, 7, 0-00, OFF, 0-00, OFF;
ADD-BERUZ: 0, 1, 6-55, OFF, 15-40, ON;
ADD-BERUZ: 0, 2, 6-55, ON, 15-40, OFF;
ADD-BERUZ: 0, 3, 6-55, ON, 15-40, ON;
ADD-BERUZ: 0, 4, 6-55, ON, 15-40, ON;
ADD-BERUZ: 0, 5, 6-55, ON, 15-40, ON;
ADD-BERUZ: 0, 6, 0-00, ON, 0-00, OFF;
ADD-BERUZ: 1, 7, 0-00, OFF, 0-00, ON;
ADD-BERUZ: 1, 1, 6-55, ON, 15-40, ON;
ADD-BERUZ: 1, 2, 6-55, ON, 15-40, ON;
ADD-BERUZ: 1, 3, 6-55, ON, 15-40, ON;
ADD-BERUZ: 1, 4, 6-55, ON, 15-40, ON;
ADD-BERUZ: 1, 5, 6-55, ON, 15-40, ON;
ADD-BERUZ: 1, 6, 0-00, OFF, 0-00, OFF;
ADD-BERUZ: 2, 7, 0-00, OFF, 12-00, OFF;
ADD-BERUZ: 2, 1, 6-55, ON, 15-40, ON;
ADD-BERUZ: 2, 2, 6-55, ON, 15-40, ON;
ADD-BERUZ: 2, 3, 6-55, ON, 15-40, ON;
ADD-BERUZ: 2, 4, 6-55, ON, 15-40, ON;
ADD-BERUZ: 2, 5, 6-55, ON, 15-40, ON;
ADD-BERUZ: 2, 6, 0-00, ON, 12-00, ON;
126
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: TAPRO - Key Programming
23 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.
In the generation sequence, AMO TAPRO is called at two points in the batch: before AMO
SBCSU to change standard key assignments, and after AMO SBCSU/SSCSU to change indi-
vidual keys.
Functions
The AMO TAPRO can be used for the following terminal types:
● optiset E T3
● optiset E T8
● optiset E T12
● optipoint 500 T8
● optipoint 500 T12
● optipoint 500/600 T19
● as well as the various add-on terminal types for optiset E and optipoint 500.
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.
23.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.
127
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: TAPRO - Key Programming Siemens
Hints for changing the standard key layouts:

– Max. 4 RNGXFER keys and max. 4 PUS keys.
– 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.
128
EN4402EN00EN_0003
© 2004 Siemens AG
Type of digital terminal
Options No terminal Add-on

Add-on
for Basic terminal(s) type and basic
terminal(s)
STD,STNO specified terminals
STD Load new std. key Load new standard Error message Error
layout for sp. basic key layout for add-on F03 Message
terminal type terminal F04
STNO Load new function for Load new function for Load new function for
freely-prog., ind. keys freely-programmable, freely prog., ind. keys
at sp. STNs with sp. indiv. keys at at spec. terminals.
(basic) terminal type specified add-on
terminal.
STNO and STD Load new standard Error message Load new std. key
key layout plus new F05 layout at spec. STN
functions for freely- and freely-prog. key
prog., ind. keys at functions at basic
spec. STNs with terminal.
spec. (basic) terminal
type.
No values rejected by MMI
specified
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;
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.
129
EN4402EN00EN_0003
© 2004 Siemens AG
23.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 |
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
+-----+---------+--------------------------------------------------------------+
| 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 |
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
130
EN4402EN00EN_0003
© 2004 Siemens AG
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
+-----+---------+--------------------------------------------------------------+
| 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 |
| | | 11 ACK 12 NAME 13 ACDPQS 14 AUTOM 15 CONS |
| | | 16 CNCT 17 HOLD 18 LINE 19 LINE |
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
131
EN4402EN00EN_0003
© 2004 Siemens AG
| + - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
+-----+---------+--------------------------------------------------------------+
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.
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 |
+--------------+-----+---------+--------------------------------------------+
132
EN4402EN00EN_0003
© 2004 Siemens AG
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 " |
+-----+---------+--------------------------------------------------------------+
| 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) " |
133
EN4402EN00EN_0003
© 2004 Siemens AG
+-----+---------+--------------------------------------------------------------+
| 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) " |
+-----+---------+--------------------------------------------------------------+
23.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;
134
EN4402EN00EN_0003
© 2004 Siemens AG
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,,,,,,,,;
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.
135
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: LRNGZ - List of Central Speed Dialing Numbers Siemens
24 LRNGZ - List of Central Speed Dialing Numbers

The central speed dialing facility (SPDC) is used to simplify dialing. Long call numbers (desti-
nation numbers) - usually external numbers - can be transmitted by means of a speed dialing
number.
The allocation of speed dialing numbers to destination numbers is stored in the central speed
dialing lists.
Up to 16 of these lists (0 to 15) can be set up, each with a maximum of 1000 speed dialing num-
bers.
Each user can access up to 2 of these lists, which are allocated to him with parameters SPDC1
(List 1) and SPDC2 (LIST 2) of a subscriber AMO (e.g. AMO SCSU or SBCSU).
The AMO LRNGZ is used to set up the lists and to allocate speed dialing numbers to each of
them. The allocation of destination numbers is carried out using AMO ZRNGZ.
The SPDC feature is accessed by dialing a code following the speed dialing number.
There are two versions of access.
a) Access of both lists via only one dialing code (digit analysis result SPDC1 in AMO
WABE).
In this case the speed dialing numbers of the lists, allocated to the user (parameter
SPDC1 and SPDC2 of the subscriber AMO) must be different, since it is the speed di-
aling number which determines whether the 1st or 2nd list is dialed. The administrator
of the switch has to take care of the so called „unambiguousness“ of the speed dialing
number ranges. Because of the various combinations of speed dialing lists, allocated
to the users (any two lists out of the available lists 0 to 15 can be allocated to any user),
AMO LRNGZ is not able to check the unambiguousness.
In the case of 3 digit speed dialing numbers a user can access a maximum speed di-
aling number range of 000 to 999, divided over the two allocated lists. Therefore with
this version of access a user has access to maximum 1000 speed dialing numbers.
b) Access of both lists via 2 dialing codes (digit analysis results SPDC1 and SPDC2 in
AMO WABE). Via dialing code of digit analysis result SPDC1, the user has access to
the 1st list, allocated to the user (parameter SPDC1 of the subscriber AMO) and via
dialing code of SPDC2 to the 2nd list (parameter SPDC2 of the subscriber AMO)
In this case the speed dialing numbers of the lists, allocated to the user can be the
same, i.e. the speed dialing number ranges can overlap, since the Lists are accessed
via the dialing code (digit analysis results SPDC1 and SPDC2 in AMO WABE) and not
via the speed dialing number.
136
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: LRNGZ - List of Central Speed Dialing Numbers
In the case of 3 digit speed dialing numbers a user can access a maximum speed di-
aling number range range of 000 to 999 per list. Therefore with this version of access
a user has access to maximum 2000 speed dialing numbers.
The AMO DIMSU is used to establish how many lists (parameter SPDCL) and destinations (pa-
rameter SPDCD) can be set up in the system.
24.1 ADD-LRNGZ
The speed dialing numbers are allocated in ascending, consecutive order.
List lengths are determined by the lowest and the highest speed dialing number.
24.2 CHANGE-LRNGZ
Change the range of speed dialing numbers in a list of central speed dialing numbers.
1. Change the range of speed dialing numbers in a list.
2. Change the number of speed dialing numbers in a list (extension)
24.3 DELETE-LRNGZ
Cancel a list of central speed dialing numbers or a range of central speed dialing numbers in a
list.
1. Cancel a list.
2. Change the number of speed dialing numbers in a list (shortening)
Examples
1. Cancel list 00. It is to be canceled only if no more station users in the system can access it.
Input:
DELETE-LRNGZ:TYPE=LST,LST=00,DEL=N;
Output:
F08: USERS CAN STILL ACCESS THE LIST.
AMO-LRNGZ -... SPEED CALL DIALING CENTRAL,LISTS
DELETE NOT COMPLETED;
2. Cancel speed dialing numbers 170-199 in list 2.

Input:
DELETE-LRNGZ:TYPE=SPDNO,LST=2,SPDNO=170;
137
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: LRNGZ - List of Central Speed Dialing Numbers Siemens
24.4 DISPLAY-LRNGZ
Interrogate the range of speed dialing numbers of one or of all lists of the central speed dialing
register with output in list format.
1. All lists in the system.
2. A specific list.
Only the created lists are displayed, i.e. lists that are not created do not result in a negative out-
put.
Example
Interrogating the speed dialing number ranges of all lists in the system.
Input:
DISPLAY-SPDC:TYPE=SYS;
Output:
LST : 00 SPDNO RANGE: 00 TO 99
138
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: LRNGZ - List of Central Speed Dialing Numbers
24.4.1 REGENERATE-LRNGZ
1. All lists in the system.
2. Only one specific list.
Example
Interrogating the speed dialing number ranges of all lists in the system for regeneration.
Input:
REGENERATE-LRNGZ:TYPE=SYS;
Output:
ADD-LRNGZ:00, 00, 99;
ADD-LRNGZ:02, 00, 45;
ADD-LRNGZ:03, 00, 99;
ADD-LRNGZ:05, 00, 24;
ADD-LRNGZ:06, 00, 99;
ADD-LRNGZ:15, 00, 99;
139
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: ZRNGZ - Central Speed Calling Digit Series Siemens
25 ZRNGZ - Central Speed Calling Digit Series

The central automatic dialer is a memory area of abbreviated numbers which is distributed
among several lists. All system subscribers can access a maximum of two lists each.The speed
dialing lists are created by AMO LRNGZ.
An abbreviated number is used to simplify dialing. Each abbreviated number can be assigned
an unabbreviated number. The number of suffix dialing digits describes the number of digits in
the unabbreviated number which are to be transmitted with a time lag during automatic suffix
dialing.
ADD-ZRNGZ
Creating destinations for abbreviated numbers of the central automatic dialer.
If a destination has already been created for the abbreviated number, the previous entry is de-
leted automatically.
Example
The external subscriber with directory number 0897220 is to be accessed with abbreviated
number 00; the final digit of the destination directory number is to be transmitted with a time
lag. The name of the external subscriber is SIEMENS MUNICH. The list has the number 12.
Input:
ADD-ZRNGZ:LST=12,SPDNO=00,DESTNO=00897220,SUPDIAL=1,NAME=SIEMENS MUNICH;
25.1 DELETE-ZRNGZ
Delete the entries for the abbreviated numbers in the central automatic dialer list.
25.2 DISPLAY-ZRNGZ
Interrogating the entries for the abbreviated numbers in the central automatic dialer lists (with
output in list form).
1. All lists in the system
2. One list in the system
3. Specific abbreviated numbers in a list
140
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: ZRNGZ - Central Speed Calling Digit Series
Example
Displaying abbreviated numbers 00 to 49 in list number 12.
Input:
DISPLAY-ZRNGZ:TYPE=SPDNO,LST=12,SPDNO=00&&49;
Output:
LST: 12 SPDNO RANGE: 00 TO 49
SPDNO DESTNO SUPDIAL NAME
00 00897221 1 SIEMENS MUNICH
02 003432564738 0 SPAIN
03 0613111515 0 MAINZ MOVIE THEATER SERVICE
25.3 REGENERATE-ZRNGZ
1. All lists in the system
2. One list in the system
3. Specific abbreviated numbers in a list
Example
Regenerating all abbreviated numbers in list number 12.
Input:
REGENERATE-ZRNGZ:TYPE=LST,LST=12;
Output:
ADD-ZRNGZ:12, 00, 0897221, 1,
"SIEMENS MUNICH ";
ADD-ZRNGZ:12, 02, 003432564738, 0,
"SPAIN ";
ADD-ZRNGZ:12, 03, 0613111515, 0,
"MAINZ MOVIE THEATER SERVICE ";
141
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: SBCSU - Station and S0 Bus Configuration of SWU Siemens
26 SBCSU - Station and S0 Bus Configuration of SWU

The AMO SBCSU configures terminal devices (stations) at S0 bus connections, S0 interfaces,
Up0 or Up0/E interfaces, and on the ATM switch. A maximum of one voice terminal may be as-
signed to an S0 bus. A maximum of three terminals with three different station numbers can be
set up per Up0/E access. Apart from configuring stations, the AMO SBCSU offers the options
of displaying, regenerating and changing the associated data, as well as cancelling station as-
signments.
The AMO SBCSU assigns all station combinations which contain the following terminals. All
other station combinations are assigned with the aid of the AMOs SCSU or SSCSU.
The following terminals are configured for the VOICE service:
● OPTISET: Digital telephone for Up0/E interface and CorNet-TS protocol
● OPTIP500: Digital telephone for Up0/E interface and CorNet-TS protocol
● OPTIIP: Digital telephone for IP interface and CorNet-TS protocol
● SET600: Digital telephone for S0 interface and
Q931, EDSS1 (EURO-ISDN) or NI-BRI protocol
● ANADEV: Analog voice terminal
(connected to Up0/E via terminal adapter a/b)
● Terminal equipment for Cordless Multicell Integration ( CMI Version >= V2.2 ) :
BASE: CMI base station with Up0/E interface and CorNet-TS protocol
RADIO: CMI mobile user with Up0/E interface and CorNet-TS protocol
CMIADM: CMI administration user with Up0/E interface and CorNet-TS protocol
EXTLINE: CMI Extension connection with S0 interface and
Q931 and EDSS1 (EURO-ISDN) protocol
● Voice terminal equipment with S0 or S2 interfaces
The following terminals are configured for non-voice services only:
● API: Workstation protocol interface and
CorNet protocol (DATA service)
● ANADEV: analog non-voice terminal
(connected to Up0/E via terminal adapter a/b)
● ANADTE: analog DTE (connected to Up0/E via terminal adapter a/b)
● ANAFAX: analog FAX (connected to Up0/E via terminal adapter a/b)
● DTE:
– digital DTE with S0 interface, CCITT-Q931 protocol
142
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: SBCSU - Station and S0 Bus Configuration of SWU
– digital DTE with U2B1Q interface, NI-BRI protocol

– digital DTE with X.21 interface (connected via terminal adapter)
– digital DTE with V.24 interface (connected via terminal adapter),
CCITT-Q931 protocol
– digital DTE with U2B1Q interface (connected via terminal adapter),
NI-BRI protocol
– analog DTE (connected to S0 via terminal adapter a/b and modem)
● FAX:
– Group 2 and 3 (connected to S0 via terminal adapter a/b)
– Group 4, CCITT-Q931 or NI-BRI ??? protocols
● Non-voice terminal equipment with S0 or S2 interfaces, e.g. DP systems, LANs, Servers.
The type of non-voice terminal equipment for DTE and FAX connected to S0 (analog, digital
S0, digital X.21) is not taken into account for the purpose of assignment in this AMO. In addition
to the terminal name, only the protocol type parameter DPROT resp. FPROT must be declared.
The terminal attributes, which are not relevant for assignment purposes, are determined when
the terminal first responds to a polling message at the bus connection or the station line circuit.
The terminals are assigned to the following modules:
SLMS (S0 interface)
STMD, STMD2 (S0 interface)
DIU-N2, DIU-N4 (S2 interface)
DIU-S2 (S2 interface)
SLMQ (ANSI-U interface)
In the case of extremely long lines
(from 1-2 km up to 9 km), use
SLMQ3 (U2B1Q interface)
SLC16 (Up0/E interface)
SLMO, SLMO16, (Up0/E interface)
SLMO24,SLMOP, SLOP2
STHC, STHC2 (combination of STMD and SLMO, i.e. S0 as well as Up0/E in-
terface)
STMA (IWU to the ATM switch)
STMI-HFA (HFA gateway to IP)
143
EN4402EN00EN_0003
© 2004 Siemens AG
In particular, the following combinations are possible:

1. Functional bus with 3 alternative connection paths
>> refer to Feature Usage Example Terminal Configuration <<
– Direct connection to SLMS or STMD via S0 line
– Connection to SLMQ or SLMQ3 via PNT
– Connection to STMD as external station
Non-voice terminals connected to a functional bus do not have associated voice terminals.
Thus, only terminals with an independent dialing circuit may be connected.
With this bus type, only one station number can be assigned per bus connection, and a maxi-
mum of one terminal per service.
To assign additional station numbers, please refer to chap. “Multiple Subscriber Numbers
(MSN) - MSN on the S0 bus”.
The functional non-voice terminals for FAX and DTE shown in the figure below are optional.
144
EN4402EN00EN_0003
© 2004 Siemens AG
Alternatives: System
SET600 S
S0-Bus L *1
M
FAX S
DEE
S
S0 L
PNT M
ANSI-U Q
public network (PTT)

S
S0 S0 T
PCM2TD PCM2TD M
D
*1 As an alternative to the SLMS, an STMD can be assigned
Bild 26-1 Alternative connection paths for functional bus
2. OPTISET configuration with three connection options

>> refer to Feature Usage Example optiset E Telephone Configuration <<
– Connection via PNT-Q to SLMQ-EXT (parts number Q2153 -X only)
or SLMQ3
– Connection via the Up0/E line direct to SLMO (w/o FCTID)
or SLMO (FCTID=1)
– Connection via the Up0/E line direct to STMA (FCTID=4)
as ATM-IWU in the PSW (Port Switching) operating mode
With an OPTISET connection to the SLMO, SLMQ-EXT or STMA-PSW a maximum of three
terminals under a maximum of three different station numbers can be set up. Permitted termi-
nals for this purpose are: CorNet-TS terminals (OPTISET, OPTIP500), analog terminals
(ANADEV, ANAFAX, ANADTE) or terminals with an S0 interface (API, SET600, FAX, DTE).
145
EN4402EN00EN_0003
© 2004 Siemens AG
One OPTISET or OPTIP500 must always be set up for the main station number. A further OP-
TISET or OPTIP500 may be set up for a secondary station number; i.e. a maximum of two OP-
TISET / OPTIP500 devices can be operated per OPTISET connection. Per main station num-
ber or per secondary station number, a maximum of two S0 devices can be installed.
Unlike with the S0 bus, functional terminals can also be set up for a secondary station number,
providing these all have the same call number. For administration all functional terminals
(SET600, FAX, DTE) then count collectively as just one device.
Only one analog terminal (regardless of which type) can be set up on an OPTISET connection:
either an analog non-voice terminal (i.e. ANAFAX or ANADTE) on the main station number or
a general analog terminal (ANADEV) under a secondary station number.
A functional terminal of one type can be set up only once per OPTISET access. However, up
to a maximum of two CorNet-TS and CorNet-T terminals of the same type can be installed.
Functional terminals can also be reached via MSN station numbers (see also Chapter “Multiple
Subscriber Numbers (MSN) - MSN for OPTISET configurations”).
Within each service, terminals with different protocols may be installed; i.e. via the OPTISET
configuration, the voice terminals OPTISET / OPTIP500 (CorNet-TS) and SET600 (functional
protocol) or a functional DTE can be operated at the same time.
In order to connect additional terminals, the following OPTISET / OPTIP500 Adapters may be
necessary:
● a maximum of one OPTISET E / OPTIPOINT500 Slave Phone Adapter
*** cannot be specified explicitly, but is instead generated implicitly by AMO ***
*** and displayed in the OPTISPA field of the DISPLAY mask ***
to connect a second OPTISET / OPTIP500 device
● a maximum of one OPTISET E / OPTIPOINT500 S0 Adapter
*** and displayed in the OPTIS0A field of the DISPLAY mask ***
to connect S0 devices
● a maximum of one OPTISET E / OPTIPOINT500 a/b Adapter
*** and displayed in the OPTIABA field of the DISPLAY mask ***
to connect analog devices
● a maximum of one OPTIPOINT500 USB Adapter (integrated)
(optionally working as S0 Adapter, Control Adapter or Data Adapter)
*** and displayed in the OPTIUSB field of the DISPLAY mask ***
to connect S0 devices
● a maximum of two OPTISET E Control Adapters (OPTICA parameter)
to connect a PC dialer
146
EN4402EN00EN_0003
© 2004 Siemens AG
● a maximum of two OPTISET E Data Adapters (OPTIDA parameter)

to connect a data terminal
– OPTISET E / OPTIPOINT500 Slave Phone Adapter (OPTISPA) and
OPTISET E / OPTIPOINT500 a/b Adapter (OPTIABA) are mutually exclusive
– The total of OPTIS0A, OPTISPA, OPTIABA, OPTIUSB (each implicitly configured),
OPTICA and OPTIDA must not exceed two
Also, per OPTISET voice terminal, a maximum of four add-on devices or a maximum of three
add-on devices and one identity card reader (IDCR) can be connected.
Per OPTIP500 voice terminal, a maximum of two add-on devices or a maximum of one add-on
device and one SartCard Reader (IDCR) can be connected.
SET600 S
Up0/E ANSI-U L
OPTISET PNT-Q M
FAX Q
DEE
API
S
OPTISET
Up0/E
L *1
OPTIS0A OPTISPA
M
O
S0
Up0/E
OPTISET
*1 As an alternative to the SLMO (w/o FCTID), an SLMO (FCTID=1) can be assigned
Bild 26-2 Connection alternatives via the OPTI configuration (part 1)
147
EN4402EN00EN_0003
© 2004 Siemens AG
S
OPTISET
Up0/E L *1
M
OPTIS0A OPTIABA
O
S0
SET600
ANAFAX ANADEE
FAX
DEE
S0
API
S
OPTISET
Up0/E *1
L
OPTIS0A OPTIABA
M
O
ANAEG
*1 As an alternative to the SLMO (w/o FCTID), an SLMO (FCTID=1) can be assigned
Bild 26-3 Connection alternatives via the OPTI configuration ( part 2 )
3. CMI configuration ( CMI version >= V2.2 )

– Connection directly to SLC16 via Up0/E line
>>refer to "Cordless Products", "Hicom cordless E 2.2, Service Manual"<<
4. Point-to-point connections for functional S0/S2 terminals
>>refer to Feature Usage Example Adding an S2 station <<
148
EN4402EN00EN_0003
© 2004 Siemens AG
– Direct voice/non-voice connection with a maximum of two b-channels to STMD via an

S0 line.
For short lines a SLMS can be used instead of an STMD.
– Direct voice/non-voice connection with a maximum of 30 b-channels to DIU-S2, DIU-
N2 or DIU-N4 via an S2 line
The individual b-channels of the S0/S2 line will no longer be permanently assigned to different
call numbers - instead, any number of MSN station numbers are assigned to the termination,
of which up to 2 (for S0) or 30 (for S2) MSN station numbers may be in the calling condition
simultaneously. Which b-channel is used for the connection is left to chance.
Point-to-point connections can be set up for non-voice terminals with S0/S2 interfaces, e.g. DP-
systems, LANs, servers.
To assign additional station numbers, please refer to chap. “Multiple Subscriber Numbers
(MSN) - MSN for functional point-to-point connections”.
System
MSN 1
S (MSN 2)
S0 *1 T | |
DEV M | |
D | |
(MSN n)
S0 Up0 MSN 1
DEV PNT S (MSN 2)
L | |
M | |
Q | |
(MSN m)
*1 As an alternative to the SLMS, an STMD can be assigned
Bild 26-4 Connection of a terminal with 2 b-channels (S0 or Up0)
149
EN4402EN00EN_0003
© 2004 Siemens AG
System
D MSN 1
S2 *1 I (MSN 2)
DEV | |
U | |
- | |
S | |
2 (MSN n)
*1 As an alternative to the DIU-S2, a DIU-N2 or DIU-N4 can be assigned
Bild 26-5 Connection of a terminal with 30 b-channels (S2)
5. Multiple Subscriber Numbers (MSN)

a) MSN on the S0 bus
>> refer to Feature Usage Example EURO-ISDN Terminals <<
For the bus type described above:
– Functional bus
there is also the possibility of enhancing the existing bus configuration to include so called Mul-
tiple subscriber numbers (MSN). In this way
– an existing functional device, which belongs to the main station number, can be
reached using different station numbers (whereby the actual dialled number is always
displayed)
– further functional devices for a service already configured on the bus can be attached
and reached respectively by their own station numbers.
A restriction to functional devices of a special service is not possible.
The devices attached to the bus must be set to the station numbers used.
Fundamentally the following distinction applies:
● An MSN station number
is a new number on the bus by which each existing functional device of the main station number
can be reached.
In this respect, there is no limitation as to the number of MSN station numbers which can be
configured on the bus.
150
EN4402EN00EN_0003
© 2004 Siemens AG
b) MSN for OPTISET configurations

>> refer to Feature Usage Example optiset E Telephone Configuration <<
Via the OPTISET configuration, the existing device constellation can be expanded by so-called
MSN station numbers (Multiple Subscriber Numbers). This has the following advantages:
– An existing functional device set up for a main station number or a secondary station
number can be reached at several station numbers; (however, it is always the dialed
station number that is displayed).
– Other functional devices of a service already configured via an OPTISET configuration
can be connected and can be reached at their own station numbers.
Restricting this to functional terminals with certain services is not possible.
The functional terminals connected via the OPTISET configuration must be set to the station
numbers that have been set up.
The following distinction must always be made:
is an additional station number for the OPTISET configuration at which any existing functional
terminal can be reached.
There is no restriction on the number of MSN station numbers per OPTISET configuration.
● An MSN secondary station number
is an existing station number without functional services that is connected via the OPTISET
configuration (irrespective of whether main or secondary station number) and that is extended
in such a manner that each existing functional terminal of the OPTISET configuration can also
be reached at this station number. If the functional services are set up for a secondary station
number, unlike with the S0 bus, the main station number can also be an MSN secondary station
number.
The number of MSN secondary station numbers via the OPTISET configuration is subject to
the following restrictions: The total number of CorNet-TS terminals, CorNet-T terminals, func-
tional terminals (each service here counting individually), and MSN secondary station numbers
must not exceed eight; however, the MSN share of a station number counts only as a single
terminal, irrespective of how many functional services are in fact thus reachable.
c) MSN for functional point-to-point connections
>> refer to Feature Usage Example Adding an S2 station <<
The Point-to-Point connections for functional S0/S2 terminals described before may also be ex-
tended by so called MSN station numbers (Multiple Subscriber Numbers).
A restriction to functional devices of a special service is not possible.
151
EN4402EN00EN_0003
© 2004 Siemens AG

is a new number on the bus by which each existing functional device of the main station number
can be reached.
In this respect, there is no limitation as to the number of MSN station numbers which can be
configured on the bus.
6. Signed-off subscribers
>> refer to Feature Usage Example AUTOSET RELOCATE Applications <<
Terminals OPTISET and OPTIP500 can also be installed as signed-off subscribers. These are
not assigned a location. Locations entered for signed-off subscribers are ignored. Signed-off
subscribers can sign on by means of a registration code number and PIN at any suitable termi-
nal, or they can sign on via a suitable terminal at the appropriate location, or they can be signed
on at a suitable location by means of AMO DSSU.
Suitable locations for the various terminals are:
a) for OPTISET / OPTIP500:
– with PNT-Q to SLMQ or SLMQ3
– direct to SLMO
– with OPTISPA to an OPTISET / OPTIP500 master terminal
(except if connected to SLMQ3).
However, the location or the TSI at which a signed-off subscriber can be signed on must be
signed off.
26.1 ADD-SBCSU
The action ADD-SBCSU is used to assign station terminals. One assignment order is required
for each station number. The first station number is called the main station number. It is used
as a reference, if further station numbers (secondary or MSN station numbers) of a bus, OPTI
or S0/S2 point-to-point connection will be assigned. The following alternatives are possible:
● Assigning a functional bus connection (OPT=FBUS).
● Assigning the main station number of a CorNet-TS-OPTISET configuration (OPT=OPTI).
● Setting up the main station number for the components (base station, mobile user, admin-
istration user, extension connection) of a CorNet-TS-CMI configuration (OPT=CMI).
● Expanding an OPTISET configuration by a secondary station number (OPT=OPTIEXP).
A maximum of two secondary station numbers can be set up per OPTISET configuration.
● Expanding a CMI configuration by a secondary station number (OPT=CMIEXP).
A maximum of one secondary station number is possible on a CMI configuration.
152
EN4402EN00EN_0003
© 2004 Siemens AG
● Assigning a MSN station number for a FBUS/OPTISET configuration (OPT=MSN).

● Expanding an OPTISET configuration with an MSN secondary station number
(OPT=MSN).
● Expanding station capabilities by adding a service which is not currently assigned to the
station number (bus connections and OPTISET configuration) (OPT=SVC).
MSN station numbers or MSN secondary station numbers already assigned to the bus will
be automatically extended to the new service(s).
● Setting up the main station number for an S0/S2 point-to-point connection (OPT=FPP).
● Assigning a MSN station number via an S0/S2 point-to-point connection (OPT=MSN).
A S0/S2 connection may be extended by any number of MSN station numbers.
Each OPTISET configuration can be expanded by further station numbers with OPT=OP-
TIEXP, providing the usual general conditions for the OPTISET configuration are complied with
(maximum three terminals, maximum three station numbers).
The parameter PEN specifies the location or port equipment number (LTG-LTU-SLOT-CCT) at
which the station devices are connected with the station number STNO. If this parameter is not
specified, then the first free location in the system is taken, which corresponds to the other pa-
rameter values specified (OPT, CONN, DVCFIG).
The device configuration, to which a port equipment number or location is to be assigned, is
declared with the parameter DVCFIG.
The parameters OPT, STNO, PEN, CONN, and DVCFIG, as well as TSI and if required, are
used to define what devices are to be assigned and where they are to be assigned. The remain-
ing parameters are used to describe device attributes.
The parameter INS does not reflect the exact state of a terminal device. For INS=Y the trunk
will be released for call processing, but it will not necessarily be active. A deviation of the ter-
minal devices states and the trunk state is not possible. The exact states of terminal devices
and trunks can be interrogated via the AMO SDSU. In the actions DISPLAY and REGENER-
ATE of the AMO SBCSU INS=Y will be output for trunk states different from long term deacti-
vation. A trunk assigned with INS=N is in the state long term deactivation.
The parameters are divided into the following groups:

1. Addressing parameters :
OPT, CONN, PEN, TSI, MAINO.
2. General parameters (for all device types):
STNO, DVCFIG, COS1, COS2, LCOSV1, LCOSV2, LCOSD1, LCOSD2, DPLN, ITR, SST-
NO, COSX, SPDI, SPDC1, SPDC2, INS, RCBKB, RCBKNA, CBKBMAX, ALARMNO,
HMUSIC, DTMFCTRD, DTMFBLK.
153
EN4402EN00EN_0003
© 2004 Siemens AG
3. Parameters for CorNet terminals:

IDCR, REP, STD, SECR, DSSTNA, DSSTNB, DIGNODIS, OPTICA, OPTIDA, OPTICOM,
HEADSET, HSKEY, CBKNAMB, TEXTSEL, CALLOG, PMIDX, COMGRP, APICLASS, AC-
FAPPL, DNIDSP, DCFWBUSY.
4. Parameter for IP terminals:
IPPASSW.
5. Parameters for general analog terminal:
DFSVCANA, FLASH.
6. Parameters for functional terminals:
SPROT, FPROT, DPROT, PERMACT, SOPTIDX, FOPTIDX, DOPTIDX, BASICSVC.
The optional protocol type parameters must be declared, if a terminal has already been de-
clared for the relevant service with parameter DVCFIG, e.g. DPROT for DTE.
The BASICSVC parameter must be declared, if the NI BRI protocol has been specified for
a protocol type parameter, e.g. DPROT=SBNIBRI for DTE.
7. Parameters for S0/S2 point-to-point connections:
PERMACT, PROT, OPTIDX, LWPAR.
8. Board-specific parameters
EXTBUS, ASYNCT, PATTERN, VPI, VCI.
If an existing OPTISET/CMI configuration is expanded with a secondary station number
(OPT=OPTIEXP/CMIEXP), then the values specified for the main station number are used as
default values, as far as possible.
If a data terminal (DTE) is assigned together with a voice terminal, then the voice terminal is
always associated with the data terminal.
Examples
1. Connecting an OPTISET configuration directly to an SLMO with an OPTISET voice termi-
nal with three add-on devices and a functional non-voice terminal of service FAX. The nec-
essary S0 adapter OPTIS0A is implicitly configured by the AMO SBCSU.
Input:
ADD-SBCSU:STNO=3427,OPT=OPTI,CONN=DIR,PEN=1-1-67-1,DVCFIG=OPTISET&FAX,
DPLN=0,ITR=0,COS1=5,COS2=6,LCOSV1=11,LCOSV2=12,LCOSD1=21,LCOSD2=22,
REP=3,FPROT=SBDSS1,FOPTIDX=10;
Output:
H05: 3427 THIS STATION IS ASSIGNED AT PEN 1- 1- 67- 1
H35: 3427 THE TERMINAL ADAPTER OPTIS0A
FOR CONNECTING S0 DEVICES
MUST BE PLUGGED AT MAIN STATION NUMBER 3427.
H08: 3427 STATION RELEASED FOR CALL PROCESSING
154
EN4402EN00EN_0003
© 2004 Siemens AG
2. Expand the OPTISET configuration (of example no.1) with an OPTIP500. The OPTISET
configuration to be expanded is specified with the parameter MAINO.
Input:
ADD-SBCSU:STNO=3428,OPT=OPTIEXP,MAINO=3427,DVCFIG=OPTIP500,
DPLN=0,ITR=0,COS1=5,COS2=6;
Output:
H35: 3428 THE TERMINAL ADAPTER OPTISPA
FOR CONNECTING THIS OPTIP500
MUST BE PLUGGED AT MAIN STATION NUMBER 3427.
3. Expand the OPTISET configuration (of example no.2) with a MSN secondary station
number
Input:
ADD-SBCSU:STNO=3428,OPT=MSN,MAINO=3427;
Output:
H22: 3428 MSN STATION NUMBER HAS BEEN ASSIGNED
FOR THE SERVICE FAX.
4. Assign a MSN station number to the OPTISET configuration (of example no.3)
Input:
ADD-SBCSU:STNO=4999,OPT=MSN,MAINO=3427;
Output:
H22: 4999 MSN STATION NUMBER HAS BEEN ASSIGNED
FOR THE SERVICE FAX.
5. Expand the Main Station Number (of example no.4) with a functional non-voice terminal
with DTE service
Input:
ADD-SBCSU:STNO=3427,OPT=SVC,DVCFIG=DTE,DPROT=SBDSS1,DOPTIDX=10;
155
EN4402EN00EN_0003
© 2004 Siemens AG
Output:
H24: 3428 MSN STATION NUMBER HAS BEEN EXTENDED
BY THE SERVICE DTE.
H24: 4999 MSN STATION NUMBER HAS BEEN EXTENDED
BY THE SERVICE DTE.
6. Configure an S0 bus connection with NI-BRI protocol via PNT (SLMQ3 module) with a
SET600 voice terminal and functional non-voice terminals with DTE and FAX services.
Input:
ADD-SBCSU:STNO=3525,OPT=FBUS,CONN=PNT,DVCFIG=SET600&DTE&FAX,
DPLN=0,ITR=0,COS1=5,COS2=6,LCOSV1=11,LCOSV2=12,LCOSD1=21,LCOSD2=22,
SPROT=SBNIBRI,DPROT=SBNIBRI,FPROT=SBNIBRI,BASICSVC=UDI64;
Output:
7. Assign an S2 point-to-point connection as an external station.

Input:
ADD-SBCSU:STNO=3460,OPT=FPP,CONN=EXT,DVCFIG=S2PP,
COS1=15,COS2=16,LCOSV1=11,LCOSV2=12,LCOSD1=21,LCOSD2=22,
DPLN=0,ITR=0,PROT=SBQ9311,OPTIDX=9,INS=N;
Output:
H09: 3460 THE STATION IS NOT ACTIVATED
26.2 CHANGE-SBCSU
The parameter STNO is mandatory. This parameter is used to specify the station to be
changed. All other parameters are optional. However, at least one of these parameters must be
declared. The parameter OPT must only be specified if OPT-specific parameters are to be
changed.
MSN station numbers will also be processed!
The following users cannot be assigned a new station number (parameter NEWNO):
● Users who have already been entered as a Route-to-Extension destination in an ACD
Routing Table (AMO ACDRT).
● Users for whom ACD attributes have already been set (AMO SDAT).
156
EN4402EN00EN_0003
© 2004 Siemens AG
The parameters are divided into the following groups:

1. General parameters (for all device types):
STNO, NEWNO, COS1, COS2, LCOSV1, LCOSV2, LCOSD1, LCOSD2, DPLN, ITR, SST-
NO, COSX, SPDI, SPDC1, SPDC2, TRACE, ALARMNO, RCBKB, RCBKNA, CBKBMAX,
HMUSIC, OPT, DTMFCTRD, DTMFBLK.
2. Parameters for CorNet terminals:
IDCR, REP, SECR, DSSTNA, DSSTNB, DIGNODIS, OPTICA, OPTIDA, OPTICOM,
HEADSET, HSKEY, CBKNAMB, TEXTSEL, CALLOG, PMIDX, COMGRP, APICLASS, AC-
FAPPL, DNIDSP, DCFWBUSY.
3. Parameter for IP terminals:
IPPASSW.
4. Parameters for general analog terminal:
DFSVCANA, FLASH.
5. Parameters for functional terminals:
SPROT, FPROT, DPROT, PERMACT, SOPTIDX, FOPTIDX, DOPTIDX, BASICSVC.
The protocol type parameters are ignored, unless a terminal has also been specified for
the relevant service, e.g. DPROT for DTE.
The BASICSVC parameter is ignored, unless the NI BRI protocol has also been specified
for a protocol type parameter, e.g. DPROT=SBNIBRI for DTE.
6. Parameters for S0/S2 point-to-point connections:
PERMACT, PROT, CONN, OPTIDX, LWPAR.
7. Board-specific parameters
EXTBUS, ASYNCT, PATTERN, VPI, VCI.
If SECR has to be changed, the circuit must be locked. This can be done by AMO DSSU or by
specifying parameter OFFTYPE in the CHANGE command.
Changes for the circuit specific parameters
ASYNCT, EXTBUS, IPPASSW, LWPAR, PERMACT, PATTERN, VPI, VCI
will only become effective after having the new data downloaded into the module.
Downloading will be triggered by
● de- and re-activation "with unconditional loading" (e.g. RESTART-DSSU)
● parameter OFFTYPE=DC (Default) or OFFTYPE=DI. The circuit must be in READY or UN-
ACH state (can be interrogated by AMO SDSU). In UNACH state, data is loaded automat-
ically when hierarchy becomes ready.
157
EN4402EN00EN_0003
© 2004 Siemens AG
26.3 DELETE-SBCSU
The DELETE action is used to delete
● specific service assignments to a station number (by specifying STNO and SVC).
MSN station numbers or MSN secondary station numbers assigned to the S0 bus or at the
OPTISET configuration will be automatically shortened by the service deleted for the Main
Station Number.
● specific MSN station numbers or MSN secondary station numbers (by specifying STNO
and SVC=MSN).
● specific station numbers (by specifying STNO and SVC=ALL).
Ranges and concatenated single values can be specified for parameter STNO in both cases.
Any station-device allocations which exist (assigned with AMO TGER) are automatically delet-
ed.
The following services or stations cannot be deleted:
● Services assigned to a hunting group.
● Stations which belong to a call pickup group.
● Stations which belong to an executive/secretary system or are assigned to a night option.
In these cases, the relevant assignment must first be explicitly deleted using the AMOs
CHESE and NAVAR.
● Users who are still entered as a Route-to-Extension destination in an ACD Routing Table
(AMO ACDRT).
● Users for whom ACD attributes are still set (AMO SDAT).
● Users who are logged on to a SLMPX as teleworkers.
In this case the user must first be signed off.
● Voice terminals which are upgraded to keysystem terminals (AMO KCSU).
Note
The configuration to be deleted must either first be deactivated (blocked) with the AMO DSSU
or by using parameter OFFTYPE with the DELETE command.
This does also apply to signed-off subscribers!
Exception: A CMI administration user can only be deactivated by blocking the board using AMO
BSSU!
158
EN4402EN00EN_0003
© 2004 Siemens AG
Examples
1. Delete specific service from main station number
Input:
DEL-SBCSU:STNO=3427,SVC=FAX; /* camp-on deactivation */
Output:
H06: 3427 STATION DATA DELETED.
H25: 3428 MSN STATION NUMBER HAS BEEN SHORTENED
BY THE SERVICE FAX.
H25: 4999 MSN STATION NUMBER HAS BEEN SHORTENED
BY THE SERVICE FAX.
2. Delete MSN secondary station number from OPTISET configuration

Input:
DEL-SBCSU:STNO=3428,SVC=MSN; /* immediate deactivation */
Output:
H23: 3428 MSN STATION NUMBER HAS BEEN DELETED
FOR THE SERVICE DTE.
3. Delete MSN station number from OPTISET configuration

Input:
DEL-SBCSU:STNO=4999,SVC=MSN,OFFTYPE=DC; /* immediate deactivation !! */
Output:
4. Delete secondary station number from OPTISET configuration

Input:
DEL-SBCSU:STNO=3428,SVC=ALL,OFFTYPE=DC; /* camp-on deactivation */
Output:
H36: 3428 THE TERMINAL ADAPTER OPTISPA PLUGGED AT MAIN STATION NUMBER 3427
FOR CONNECTING THIS OPTIP500 IS NO LONGER NEEDED.
159
EN4402EN00EN_0003
© 2004 Siemens AG
5. Delete main station number of OPTISET configuration

Input:
DEL-SBCSU:STNO=3427,SVC=ALL,OFFTYPE=DI; /* immediate deactivation */
Output:
H36: 3427 THE TERMINAL ADAPTER OPTIS0A PLUGGED AT MAIN STATION NUMBER 3427
FOR CONNECTING S0 DEVICES IS NO LONGER NEEDED.
26.4 DISPLAY-SBCSU
With the DISPLAY action, terminal data, bus configurations and MSN links can be interrogated.
The type of output can be specified by declaring the parameter TYPE:
● TYPE=TERMDATA
The parameter values with which the terminals in the specified range were configured are
output in tabular form for each STNO (even if MSN).
● TYPE=BUS
The bus/OPTISET configurations in the specified station number range are output. For
each bus/OPTISET configuration, a table is displayed with the following data: type of bus,
type of connection, port equipment number, all STNOs allocated to the bus, terminal con-
figurations of each station number with corresponding TSI numbers allocated and MSN
station numbers or MSN secondary station numbers eventually assigned.
● TYPE=BUSDATA
Combination of TYPE=TERMDATA and TYPE=BUS for all configurations in the station
number range specified.
● TYPE=FPP
This outputs the corresponding MSN station numbers for all existing S0/S2 point-to-point
connections. For each connection, a table is output with the following data: type of connec-
tion, port equipment number and a list of all MSN station numbers assigned.
● TYPE=MSN
Those station numbers in the specified station number range are output, which have been
configured with DVCFIG=MSN.
● TYPE=OPTIDAT
For all OPTISET / OPTIP500 / OPTIIP terminals installed within the specified station num-
ber range, the assigned individual terminal data (phone ID, asset ID, SW version, self-test
result) and the currently valid hardware settings (ringing volume, ringing tone, warning sig-
nal volume, call volume via handset, call volume via loudspeaker, hands-free characteris-
tics,display contrast, rollover volume) are output.
160
EN4402EN00EN_0003
© 2004 Siemens AG
● TYPE=SEARCH
Those station numbers in the specified station number range are output, which meet a cer-
tain search criterion as specified by the optional parameters CONN, DEV, COSNO,
LCOSV, LCOSD, TRACE, KEYSYS and INS.
Examples
1. Display the configuration data for STNO 3427
Input:
DISP-SBCSU:STNO=3427;
Output:
---------------------------- USER DATA ---------------------------------------
STNO =3427 OPT =OPTI COS1 =5 DPLN =0
MAINO =3427 CONN =DIR COS2 =6 ITR =0
PEN = 1- 1- 67- 1 LCOSV1 =11 COSX =0
INS =Y ASYNCT =500 LCOSV2 =12
PERMACT = LCOSD1 =21
SSTNO =N EXTBUS = LCOSD2 =22 CBKBMAX =5
TRACE =N RCBKB =N
ALARMNO =0 DFSVCANA= SPDI =0 RCBKNA =N
HMUSIC =0 FLASH = SPDC1 = CBKNAMB =Y
PMIDX =0 SPDC2 =
COMGRP =0
SECR =N DIGNODIS=N DSSTNA =N
STD =0 CALLOG =NONE DSSTNB =Y TEXTSEL =SPANISH
REP =0 OPTICOM =N OPTIUSB : VPI =

IDCR =N OPTICA =0 OPTIS0A :1 VCI =
OPTIDA =0 OPTISPA :1 PATTERN =
OPTIABA :0
DCFWBUSY=N HEADSET =N APICLASS=
DNIDSP =N HSKEY =NORMAL ACFAPPL =0
DTMFBLK =N IPPASSW =
DTMFCTRD=N BASICSVC=
DVCFIG =OPTISET TSI =1 SPROT = SOPTIDX =
DTE 5 DPROT =SBDSS1 DOPTIDX =10
FAX 2 FPROT =SBDSS1 FOPTIDX =10
------------------- ACTIVATION IDENTIFIERS FOR FEATURES ----------------------
FWDS :N HTOS :N DND :N
FWDD :N HTOD :N VCP :Y TWLOGIN :N
FWDF :N HTOF :N CWT :N
------------------- FEATURES AND GROUP MEMBERSHIPS ---------------------------
PUGR :10 ESSTN :
KEYSYS :Y NOPTNO :5
HUNT CD :N
------------------- SUBSCRIBER ATTRIBUTES (AMO SDAT) -------------------------
AGENT SUPER AUTOLOG CAF DNDSR CASTMON CBSTMON ANI10
KN RKNOVR EOVR OFHKRC VC
161
EN4402EN00EN_0003
© 2004 Siemens AG
------------------------------------------------------------------------------
The output data for a station is subdivided into 4 groups:

1. Data which is also contained in the input command.
2. Activation identifiers for the features.
3. Features and group memberships which are not assigned by the AMO SBCSU
4. Subscriber attributes which are assigned by the AMO SDAT
Explanation of ACTIVATION IDENTIFIERS FOR FEATURES :

FWDS = Call forwarding for voice (speech)
FWDF = Call forwarding for FAX
FWDD = Call forwarding for data terminal equipment (DTE)
HTOS = Hunting group out, voice (release from hunting group)
HTOF = Hunting group out, FAX
HTOD = Hunting group out, DTE
DND = Do-not-disturb
VCP = Voice call protection
CWT = Call waiting - terminating
TWLOGIN = Teleworking LOGIN Status
Explanation of FEATURES AND GROUP MEMBERSHIPS :

PUGR = Station assigned to a call pickup group
ESSTN = Station in executive/secretary system
ROLE = Role in the executive/secretary system (see AMO CHESE)
KEYSYS = Station upgraded to a Keysystem (AMO KCSU)
NOPTNO = Station assigned to a night option
HUNT CD = Station assigned to a hunting group
Explanation of SUBSCRIBER ATTRIBUTES (AMO SDAT) :

see AMO SDAT
2. Interrogate the bus configuration with STNO 3427

Input:
DISP-SBCSU:STNO=3427,TYPE=BUS;
162
EN4402EN00EN_0003
© 2004 Siemens AG
Output:
+-------------------------------------------------+
| CONFIGURATION: OPTI |
+-------------------------------------------------+
| CONNECTION: DIR |
| |
| LOCATION (PEN): 1- 3- 67- 1 |
+=================================================+
| STNO DVCFIG TSI |
+-------------------------------------------------+
| 3427 OPTISET 1 |
| DTE 5 |
| FAX 2 |
| 3428 OPTIP500 3 |
| MSN 4 |
| 4999 MSN - |
+-------------------------------------------------+
THE MSN STATION NUMBERS HAVE BEEN ASSIGNED

FOR THE SERVICES FAX,DTE
3. Interrogate the MSN station numbers for an S0/S2 point-to-point connection

Input:
DISP-SBCSU:STNO=3460,TYPE=FPP;
Output:
MAINO =3460 CONN =EXT PEN = 1- 2- 25- 0
DVCFIG =S2PP
----------------- MSN STATION NUMBERS ----------------
3461 3462
------------------------------------------------------
4. Interrogate all stations to which COS 6 is assigned (COS1 or COS2)

Input:
DISP-SBCSU:TYPE=SEARCH,COSNO=6;
Output:
-------- SUBSCRIBER WITH --------------------------
DEV : CONN :
TRACE : COSNO : 6
KEYSYS : LCOSV :
INS : LCOSD :
---------------------------------------------------
3400 3401 3402 3403 3404 3405
163
EN4402EN00EN_0003
© 2004 Siemens AG
3427 3428 3525

---------------------------------------------------
5. Interrogate all signed-off keysystems

Input:
DISP-SBCSU:TYPE=SEARCH,KEYSYS=Y,INS=SIGNOFF;
Output:
-------- SUBSCRIBER WITH --------------------------
DEV : CONN :
TRACE : COSNO :
KEYSYS : Y LCOSV :
INS : SIGNOFF LCOSD :
---------------------------------------------------
2189 2190
---------------------------------------------------
6. Interrogate all MSN station numbers/ MSN secondary station numbers

Input:
DISP-SBCSU:TYPE=MSN;
Output:
| | S E R V I C E |
STNO | MAINO | VOICE | FAX | DTE |
--------+---------+----------+----------+----------+
3428 | 3427 | OPTIP500 | MSN | MSN |
3461 | 3460 | MSN | MSN | MSN |
3462 | 3460 | MSN | MSN | MSN |
4999 | 3427 | | MSN | MSN |
--------+---------+----------+----------+----------+
Note:
All MSN station numbers/MSN secondary station numbers for a specific main station number
of a bus or OPTISET configuration may be found with
DISP-SBCSU: TYPE=BUS, STNO=...;
All MSN station numbers for a specific FPP main station number may be found with
DISP-SBCSU: TYPE=FPP, STNO=...;
164
EN4402EN00EN_0003
© 2004 Siemens AG
7. Interrogate individual OPTISET / OPTIP500 / OPTIIP terminal data and hardware settings.
Input:
DISP-SBCSU:STNO=3427,TYPE=OPTIDAT;
Output:
+--------------------------------------------------------------------------+
| INDIVIDUAL DEVICE DATA OPTISET STNO = 3427 |
+-----------------------------------+-------------+------------+-----------+
| PHONE-ID / OPTION-ID | ASSET-ID | SW-VERSION | SELF TEST |
+-----------------------------------+-------------+------------+-----------+
| OPTISET E ADVANCE CONFERENCE | 51 10 80 34 | D517-C1 | 5 |
| OPTISET E KEY MODULE #1 | | A258-2 | 0 |
| OPTISET E KEY MODULE #2 | | 0000000 | 0 |
| OPTISET E KEY MODULE #3 | | 0000000 | 0 |
+-----------------------------------+-------------+------------+-----------+
| HARDWARE SETTINGS |
+--------------------------------------------------------------------------+
| RINGVOL : 4 ALERTVOL : 2 CALLVOL : 1 SPKRVOL : 4 |
| RINGSOUN : 2 DISPCONT : ROLLVOL : 3 ROOMCHAR : NORMAL |
+--------------------------------------------------------------------------+
26.5 REGENERATE-SBCSU
The REGENERATE action outputs the data of an S0 bus configuration as one or more position-
oriented command listings for the ADD action of this AMO. The type of data output corresponds
to that of the DISPLAY action with TYPE=TERMDATA.
By specifying any station number of a bus, OPTISET configuration or S0/S2 point-to-point con-
nection all ADD commands will be regenerated.
Examples
1. Regenerate the OPTISET configuration with STNO 3427
Input:
REGEN-SBCSU:3427;
Output:
ADD-SBCSU:3427,OPTI,DIR,1-1-67-1,OPTISET&DTE&FAX,1&5&2,
5,6,11,12,21,22,0,0,N,0,0,,,N,0,0,N,
"SBDSS1","SBDSS1",Y,0,N,N,N,Y,N,10,10,
,,,,,5,,,,N,NORMAL,
Y,SPANISH,0,,,0,,,,,,,;
ADD-SBCSU:3428,OPTIEXP,3427,OPTIP500,3,
5,6,11,12,21,22,0,0,N,0,0,,,N,0,0,N,
,,,0,N,N,N,Y,N,,,,,,,,5,N,NORMAL,,
165
EN4402EN00EN_0003
© 2004 Siemens AG
Y,SPANISH,0,,,0,,,,,,,;
ADD-SBCSU:3428,MSN,3427,,5,6,11,12,21,22,0,N,0,0,,,Y,N,N,5,;
2. Regenerate the S0 bus configuration with STNO 3525

Input:
REGEN-SBCSU:3525;
Output:
ADD-SBCSU:3525,FBUS,PNT,1-3-67-1,SET600&DTE&FAX,
5,6,11,12,21,22,0,0,N,0,0,,,
"SBNIBRI","SBNIBRI","SBNIBRI",Y,Y,0,,,,UDI64,,N,N,,5,0,;
3. Regenerate the S2 point-to-point connection with STNO 3460

Input:
REGEN-SBCSU:3460;
Output:
ADD-SBCSU:3460,FPP,EXT,1-2-25-0,S2PP,5,6,11,12,21,22,0,0,N,0,0,,,
"SBQ9311",Y,Y,0,,N,N,,,5,0;
166
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: DSS 1 Terminals
27 DSS 1 Terminals
27.1 Feature Description

From versions 2.0 and V3.6 any terminals available on the open market can be connected to
the PBX. All DSS1 functions are guaranteed.
Multiple connection
S0 Bus
e.g. Profiset 70
SBQ9312
S0 Bus
PNTQ
UP0
TA S0
S0 Point to Point
SBQ9312
S2 Point to Point
SBQ9312
The features are activated via the Supplementary Services in the Hicom instead of codes,
provided the terminal offers the required features.
DSS1 stations in bus configuration must be configured identically for all services. Generally,
the option table 10 should be assigned to the service protocols.
167
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: DSS 1 Terminals Siemens
27.1.1 Supported Features
27.1.1.1 V1.0 / 3.5
COS DSS1 LM Default Comment

MSN MSN set Multiple Subscriber Number; only with functional stations
SPECAR CLIP/ only activated, if the configured station number is not to
COLP be checked.
SUBCAL SUB using subaddressing, the station number of the calling
party is signalled at the called party.
SUBDB SUB using subaddressing, the own station number is signalled
at the called party
SUBMSN SUB using subaddressing, the MSN is signalled at the called
party
UUS1IM UUS set authorization to use the UUS1 implicit service
UUS3 UUS authorization to use the UUS3 service
CDRATN AOC With activated CDR the option table can be used to set
CDRSTN whether AOC-D and AOC-E or only AOC-E is released.
,CDRINT
168
EN4402EN00EN_0003
© 2004 Siemens AG
27.1.1.2 V2.0 / 3.6

OVCAT COLR even if the station number of the called party is secret it is
displayed at the station.
COLR set the called party has the COS to temporarily suppress the
display of the own station number at the calling party (sta-
tion controlled)
CFU "Immediate call forwarding of all incoming calls" switches
all incoming calls to a station defined by the user.
CFNR "Call forwarding on no response" switches an incoming call
to a station defined by the user, if the user does not answer
CFB the call within a certain timer period.
CD "Call forwarding on busy" switches an incoming call to a
station defined by the user, if the user is busy.
"Call forwarding by the user" allows the optional manual
forwarding of a call.
This feature is not supported by the Hicom 300 E.
ECT "Call transfer" allows a user with a held and an active con-
nection to connect those two parties.
CW CW set the called party has the COS for Call Waiting
HOLD "Hold" allows a user to put a call on hold and to resume the
call later. During "Hold" the user can establish another call
or answer an incoming call.
CCBS CCBS set a calling party meeting a busy station can activate function-
al callback; IMPORTANT: Bit 5 of byte 3 must be set in the
option table.
In order to be able to use the above Supplementary Services, the DSS1 terminal must be con-
figured in such a way that it can handle more than one signaling connection simultaneously
(Class of service parameter: "MULTRA"=Multitransaction).
169
EN4402EN00EN_0003
© 2004 Siemens AG
27.1.1.3 V3.0

TRACE MCID this COS must be set together with MCIDM to allow the
automatic registration of all incoming calls. Additional man-
ual registration is not possible.
MCIDA automatic registration of nuisance callers; they are calling
users who release the line before the connection is estab-
lished.
TP TP set a user in active talk state can park a call for a maximum of
2 minutes.
27.2 User Interface

The features are activated independent from the Hicom codes by standard protocol elements
which are transmitted from the station to the Hicom. This results on varying user interfaces
depending on the station used.
27.2.1 Call Forwarding (CFU, CFB, CFNR, and CD)

Two different methods for call forwarding will be implemented for stations using DSS1:
● forwarding using the existing Hicom concept (FWD, FWDBSY and FNAN) if FWD is pro-
grammed via keypad. The forwarding (FWD or BUL) is then carried out on the A side, which
corresponds to the procedure known from Hicom system terminals and terminals using
1TR6/D channel signaling protocols.
● forwarding according to DSS1 protocol (CFU, CFB, CFNR and CD) if FWD is programmed
functionally. Forwarding is then carried out on the B side.
The old and new forwarding methods are mutually exclusive. If forwarding is programmed using
one of the two methods and a forwarding destination has been programmed using the other
forwarding method, the latter forwardings are all deleted.
If a forwarding destination is programmed according to both the Hicom concept and the DSS1
concept, then, due to data inconsistencies, the Hicom concept dominates.
27.2.1.1 Differences to Previous Forwardings (General)

● The terminal can initiate programming for several destination numbers and/or services.
● The A station number must be checked during programming (transmitted by the terminal
in the request!).
170
EN4402EN00EN_0003
© 2004 Siemens AG
● The terminal performs a status inquiry, also for several terminals.

● Automatic status transmission to the terminal reporting a programmed call forwarding for
every outgoing call.
● Both the data of the first forwarding party and of the last forwarding party must be transmit-
ted in the message when the destination is seized.
● A customer wants the last forwarding party displayed on the terminal (terminal function).
The called party number is displayed on system terminals.
27.2.1.2 Call Forward Unconditional (CFU)

Differences to the previous FWD with Hicom
● Execution at station B. For the calling party, B has not activated FWD and is seized.
27.2.1.3 Call Forward Busy (CFB)

Differences to the previous FWDBSY with Hicom
● Execution at station B (initiated by message from the terminal). For the CP, the station is
idle (presently as well, if MULTRA is set), and must be seized.
● Up to five forwardings must be possible.
27.2.1.4 Call Forward No Reply (CFNR)

Differences to the previous FNAN with Hicom.
● Up to five forwardings must be possible.
● CFNR cannot be used as FNAN in a hunting group. Terminals supporting CFNR according
to DSS1 protocol can therefore not be used in hunting groups.
27.2.2 Call on Hold

● A station can put a call on hold, without initiating consultation call, with the following con-
sequences:
● after placing a call on hold, the station can pick-up an incoming call instead of initiating a
consultation call.
● Consultation call of a DSS 1 terminal is evaluated as a normal basic call (CPS station pre-
fix)
● A consultation call on a DSS1 terminal cannot be picked up, only transferred using ECT.
171
EN4402EN00EN_0003
© 2004 Siemens AG
● The demand that the held party can also hold a connection results in the following:
– transfer by release is no longer possible.
– Station transfer security is not longer possible (automatic recall on no answer using
ECT is still supported).
27.2.3 Call Transfer (ECT)

● The information about the call transfer type is no longer connection-related but station-
related (status of the new partner) which could result in differing messages at the stations
(TRANSFER_TALKING and TRANSFER_RINGING).
● Information on whether call transfer is carried out in talk or ringing state is station-related
(information about the partner transaction can be derived from the "CONNECT sent to
DH").
● Call transfer is always initiated on the held transaction.
27.2.4 Three-Party Conference in Hicom

● The three-party conference is not initiated from a normal consultation hold. The required
memory concatenation is therefore not available.
27.2.5 Call Waiting (CW)

● Several calls can be signaled using CW.
● The B party needs an individual COS in order to be able to use this feature.
● CFB is performed with NDUB without signaling the call using CW.
● CFB is performed with UDUB if all stations acknowledged the CW call negatively (the rea-
son for release is stored in the DH. USER_BUSY overwrites all other release reasons but
is not overwritten).
27.2.6 Callback in Hicom (CCBS) WP3

● Only Callback on busy is supported. Callback on no answer is not possible.
● The system waits for a certain period of time after the destination station goes on-hook
before activating the callback.
● During this time, or while the idle state is being signaled to the requesting party, the station
cannot be seized by incoming calls(NDUB).
● The station can query the status of the callbacks (or a callback to a certain station).
172
EN4402EN00EN_0003
© 2004 Siemens AG
● If callback cannot be initiated the A station must be informed.

● Callback request of stations which then became busy become inactive.
As soon as the requesting party becomes idle the callback request becomes active.
This information is entered in the callback queue.
● CCBS is only available for all services for DSS1 connections. For the Telephony service
CCBS is always available (also for mixed connections e.g. DSS1 with system terminal).
27.2.7 Called Party Display Suppression (COLR)

● If a system terminal calls just such a DSS1 station
– the station number and the name of the called party is displayed before an ALERT is
transmitted. The COLR service is therefore not possible on system terminals.
– first the ringing tone is injected followed by the busy tone if the DSS1 terminal is busy
or does not answer the call. This fact was discovered with cordless stations and
declared unacceptable. This behaviour cannot, however, be avoided when DSS1
is implemented.
– callback on busy is no longer available for system terminals (there is no busy station).
This is also applicable, if there are no available B channels (Feature Call Waiting CW).
● A DSS1 station can call itself (under it’s own station number).
● Any DSS1 station in a hunting group is always the terminating station, as it is always idle
(for the system). It can, however, report busy. The call is then not transferred to an idle sta-
tion in the hunting group. Concatenation of hunting group and CFx is therefore performed.
● If this restriction is not desired for certain stations (e.g. cordless), then the MULTRA param-
eter must not be assigned.
27.2.8 Advice of Charge

If CDR is activated, the option table can be used to define whether AOC-D and AOC-E or only
AOC-E is enabled.
If bit 4 in byte 3 of the option table is activated, AOC-D is blocked.
173
EN4402EN00EN_0003
© 2004 Siemens AG
27.2.9 Malicious Call Identification
27.2.9.1 Feature Description

MCID includes the following variants:
● automatic recording of the calling party’s data
● recording of nuisance callers: those are users who release the line before the connection
is established. If a new incoming call is signalled at the called party and the call is released,
the calling party is registered in the destination PBX.
● manual activation of MCID: in active call state and immediately after the release of the con-
nection the called party can instigate registration in the destination PBX by either pressing
the appropriate key or by dialling the corresponding code.
27.2.9.2 Feature Characteristics

In addition to the station numbers of the calling parties, the station numbers of forwarded par-
ties are also registered.
27.2.9.3 AMO Batch for Stations

Malicious Call Identification is administrated for all stations using COSSU AMO. The following
configuration variants are possible:
● automatic registration of all incoming calls
CHA-COSSU: TYPE=COS,COS=6, AVCE=MCIDM&TRACE;
● manual registration of calls in call state and after the release of the connection by the
calling party
CHA-COSSU: TYPE=COS,COS=6, AVCE=MCIDM;
● registration of nuisance callers:
CHA-COSSU: TYPE=COS,COS=6, AVCE=MCIDA;
The MCIDA and MCIDM authorizations can be combined. This allows the registration of both
nuisance and individual calls.
Attention: MCIDM, TRACE and MCIDA should not be combined as automatic registration also
records nuisance calls.
174
EN4402EN00EN_0003
© 2004 Siemens AG
27.2.9.4 AMO Batch for Networks

If a connection which uses a DSS1 gateway is to be registered throughout a network the COP
parameter MICC must be set at the DSS1 gateway (user side). This allows network-wide reg-
istration after the connection release.
CHA-COT:COTNO=4, COTTYPE=COTADD, PAR=MICC;
If network-wide registration is activated, setting the COT parameter MIIH will instigate registra-
tion in a node. If the parameter is set, the registration request is not transferred to the origination
node.
CHA-COT:COTNO=4, COTTYPE=COTADD, PAR=MIIH;
27.2.10 Terminal Portability

Terminal Portability allows short-time parking of a call. By entering a two digit identification
number the call is parked in the node. As long as the call is not resumed, the terminal can be
exchanged or disconnected. It is also possible to resume the call from a different terminal linked
to the bus by entering the identification number.
A call can only be parked for a maximum of two minutes.
● configuration:
In COS, the parameter TP must be activated for the voice service and bit 6 in byte 3 of the
assigned option table must be set.
● restriction:
if the station is member of a call pick-up group, the call cannot be parked in the PU. It is,
however, possible to transfer a parked call from the PU.
27.3 Service Information

● DSS 1 terminals should always be configured for the VOICE&FAX & DATA services.
● If a busy DSS1 terminal is called by a system terminal, the ringing tone is injected first,
followed by the busy tone.
● The COS of the terminals must include the MULTRA parameter. Otherwise, the new
services cannot be used.
● Calls on hold are released when the holding party goes on-hook. There is no recall.
● A separate buffer for FWD must be generated in DIMSU AMO. Dimension the buffer
as follows: number of DSS1 terminals x 3.
● In ZAND AMO, the OPTLOAD table must be adjusted (development).
● The maximum number of callbacks is set in SBCSU AMO.
175
EN4402EN00EN_0003
© 2004 Siemens AG
● New COS are implemented in AMO COSSU.

● If the MULTRA parameter is set, a DSS1 terminal can no longer be used in a hunting
group.
● The secretary function is not implemented.
● Changes to the AMO surface.
● COSSU parameters for CCBS and Call Waiting.
● New branch for FWDDSS1 (AMO ZIEL).
● Transfer by release is not possible (separate function).
● Callback from a system terminal is possible with restrictions.
● COLR to a system terminal is not possible.
● DSS1 terminal can call itself: yes
● If on a Profiset50 a 4-digit number is displayed without a name, the first digit
disappears after a brief period of time.
● The feature groupcall in AUN-Group is not possible for DSS1 terminals.
● DSS1 terminals cannot dial the code for PSE (paging equipment)
27.4 Generation Notes
27.4.1 Configuration Examples

● Configure COS for the DSS1 terminal
ADD-COSSU:NEWCOS=22,AVCE=TA&TNOTCR&DATA&MSN&MULTRA&
CCBS&COLR&CW,AFAX=TA&TNOTCR&BASIC&MSN&MULTRA,
ADTE=TA&TNOTCR&BASIC& MSN&MULTRA,.....;
● Bus configuration of the MAINO 7185 with MSN 7186 on S0 bus (SLMS)
ADD-SBCSU:STNO=7185,OPT=FBUS,CONN=DIR,PEN=1-2-37-5,
DVCFIG=SET600&DTE&FAX&TTX&VTX,COS1=22,COS2=5,LCOSV1=1,
LCOSV2=1,LCOSD1=1,LCOSD2=1,SPROT="SBDSS1",TPROT="SBDSS1",VPROT="S
BDSS1",FPROT="SBDSS1",DPROT="SBDSS1",PERMACT=Y,INS=Y,ALARMNO=0,SO
PTIDX=10,TOPTIDX=10,VOPTIDX=10,FOPTIDX=10,DOPTIDX=10,EXTBUS=Y,CBK-
BMAX=5;
● ADD-SBCSU:
STNO=7186,OPT=MSN,MAINO=7185, COS1=22,COS2=5,
LCOSV1=1, LCOSV2=1,LCOSD1=1,LCOSD2=1, INS=Y;
176
EN4402EN00EN_0003
© 2004 Siemens AG
● Point-to-point configuration on SLMS/STMD with MAINO 7184

Unlike with bus configuration, all possible services are configured identically.
ADD-SBCSU:STNO=7184,OPT=FPP,CONN=DIR,DVCFIG=S0PP,COS1=22,COS2=5,
LCOSV1=1,LCOSV2=1,LCOSD1=1,LCOSD2=1,DPLN=0,PROT="SBDSS1",INS=Y,
OPTIDX=10,CBKBMAX=5;
● Configuration of the MAINO 7183 via PNT on SLMU
ADD-SBCSU:STNO=7183,OPT=FBUS,CONN=PNT,DVCFIG=SET600&
DTE&FAX&TTX&VTX,COS1=24,COS2=5,LCOSV1=1,LCOSV2=1,LCOSD1=1,LCOSD2
=1,DPLN=0,SPROT="SBDSS1",TPROT="SBDSS1",BPROT="SBDSS1",FPROT=
"SBDSS1",DPROT="SBDSS1",INS=Y, SOPTIDX=10,TOPTIDX=10,VOPTIDX=10,
FOPTIDX=10, DOPT=10,CBKBMAX=5;
27.4.2 Option Table

The option table consists of a series of hexadecimal numbers which partly have switch func-
tions and are partly used for the configuration of feature parameters such as CCBS and UUS.
All other fields of the option table must not be changed since this would endanger protocol con-
form functioning.
The following table contains the option table assigned to the corresponding station:
Tabelle 3
Station Protocol variant Option table

EURO-ISDN station of the KRONE company SBQ9311 2
Integrated terminal adapter SBQ9311 2
CMI/NW-CHESE SBQ9311 6
UNIX in ADS SBQ9312 3
DKZ-N1 station SBDKZN1 1
DSS1 station SBDSS1 10
Terminal adapter ELMEG 1TR6 SB1TR61 1
S0 Cards (No output of layer 3 fault messages) SBQ9311 4
● Assigning an option index to a station

Assign a certain option index (1-10, see table) per configured service to the functional
stations on the bus using the SBCSU AMO. The option index then refers to the correspond-
ing option in the database:
177
EN4402EN00EN_0003
© 2004 Siemens AG
ADD-SBCSU:STNO=4711,OPT=<FBUS/MBUS/OPTI/OPTIEXP>,...
,SOPTIDX=<opt-voice>,TOPTIDX=<opt-ttx>,VOPTIDX=<opt-vtx>
,FOPTIDX=<opt-fax>,DOPTIDX=<opt-dte>;
or for point-to-point connections:
ADD-SBCSU:STNO=4711,OPT=<FPP/MSN>,OPT=<opt>;
If no OPT or xOPT-(X=S/T/B/F/D) value is set during terminal configuration, the

AMO automatically enters xOPT=1 or OPT=1.
● Later option modification

If problems occur with EURO-ISDN features although the option table was loaded (DIS-
ZAND:TYPE=OPTTBL), the adjustment of an option in the database could be required.
Every option consists of 100 bytes. It is possible to modify an option in the database
byte-by-byte using AMO ZAND: address the option via the table index (1-10) and the num-
ber of the byte to be modified (1-100). Enter the new value to be assigned to the byte in
hexadecimal form. Every option also has a name that can be modified:
CHA-ZAND:TYPE=OPTTBL,IDX=number,BYTE=number,VALUEOPT=FF[,NAME="..."];
Due to the meaning of the individual bytes only known CP internally, options should
only be modified by specialists and should only be performed (with the exception of
name modification) after consultation with ICN WN ES D.
Every new HD option table (e.g. APS modification) must be loaded into the database
using AMO ZAND. The AMO, however, only allows loading of entire tables (selective
reloading of individual options is not possible). All options in the database are there-
fore overwritten and any previous individual adjustments are lost.
178
EN4402EN00EN_0003
© 2004 Siemens AG
27.5 AMO Modifications

Language
COSSU UUS1IM d User-User Service 1 Implicit
UUS1IM e User-User Service 1 Implicit
UUS3 d User-User Service 3
UUS3 e User-User Service 3
MCIDM d manual MCID allowed
MCDIM e manual MCID allowed
MCIDA d MCID for ring-disturber
MCDIA e MCID for ring-disturber
TP d Terminal Portability
TP e Terminal Portability
COT MICC d MCID Auslösekontrolle notwendig
MICC e MCID release control necessary
MIIH d Lokales Audrucken von MCID durchführen
MIIH e execute lokal printout of MCID
27.6 Glossary
NDUB network-determined user busy
UDUB user-determined user busy
179
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: SCSU - Subscriber Configuration of Switching Unit Siemens
28 SCSU - Subscriber Configuration of Switching Unit

AMO SCSU is used to configure ports for the connection of the following terminals:
● ANATE to SLMA, SLMA1, SLMA2, SLMA3, SLMA24, SLMAB, SLMAR
● Charge Metering ANATE (ANATECM) to SLMAR
● AUXDIGI to SLMB, SLMB4
The digital terminals at S0/Up0/UpoE such as SET600/OPTISET/OPTIP500 are set up using
AMO SBCSU.
Special subscribers (e.g. Hicom Trading Board subscribers) are configured by AMO SSCSU.
Each STN number can be assigned personalized data such as names or personal identification
numbers (PIN) using AMO PERSI.
AMO TGER is used to assign additional station numbers to non-voice terminals which have al-
ready been assigned a number (AMO SCSU/SBCSU).
It is also possible to configure "virtual" ports for all device types which have not been assigned
to a module but are configured in the same way as regular physical ports. Virtual ports are iden-
tified as INS=FLOAT or INS=ACLSTN. These ports are used by any ID card user who identifies
himself at another terminal by inserting his ID card or by keying in the PIN, and who then makes
the call using the features of his virtual port such as classmarks, speed dialing digit series
etc..An ANATECM is not allowed to be configured as virtual port.
It is also possible to install a signed off fictive station by depicting INS=SIGNOFF. A signed off
station can only be an ANATE. Signed off stations can be signed on
– by entering a PIN-Number and a key number at the specific terminal or
– by being signed on terminal by means of service staff
– by administration command (AMO DSSU)
Signed off stations can be added to communication groups such as pick up groups, hunting
groups etc. This allows a complete preconfiguration of subscribers.
For "virtual" ports (e.g. INS=FLOAT) PEN-specific parameters (e.g. COFIDX) are ignored.
A suffix-dialing connection is required for connecting special facilities such as VMX servers.
This connection is identified as SPEC=SUFDIAL and parameterized using the parameter DH-
PAR.
For special stations (e.g. COMTEL) and for special country specific adaptions in SLMA1/
SLMA2/SLMA3/SLMA24/SLMAB/SLMAR-Loadware parameterization can be done by using
parameter DHPAR.
Some special subscribers like Voice Pagers etc. are configured using parameter SPEC.
180
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: SCSU - Subscriber Configuration of Switching Unit
28.1 ADD-SCSU
The ADD command will only be completed successfully if the following preconditions are met:
the required station numbers must be entered in the dial plan (DAR=STN), the relevant module
must have a free circuit and the required classes-of-service must be set up.
The parameter PEN designates the port equipment number (LTG-LTU-SLOT-CCT) to which the
device with the STNO (station number) is connected. If this parameter is missing, a search is
made automatically for an available equipment number in the system which is compatible with
the other parameter values. For signed off and floating stations the PEN is ignored without an
advisory message.
The connection type (parameter CONN) defines how a station is connected to the system: Ei-
ther via direct line (DIR) or off premised via TMDNH or SLMA board (OPST1/OPSSLMA). This
information is kept in a PEN-specific memory. This is the reason why it does not move with the
subscriber during signoff/signon process but remains tied together the physical port (PEN).
Please note when specifying ranges:
Ranges and/or strings of single values may be entered for STNO, but not for the parameter
PEN. In this case, a single entered PEN is used as a starting point for the automatic port
search.
Exception: Automatic port search for ANATE’s does not consider SLMAR-PEN, even if a SL-
MAR-PEN is entered as starting point for the search.
Automatic port search for ANATECM’s considers only SLMAR-PEN’s.
The device configuration for which the PEN is to be assigned is defined by the parameter DVC-
FIG.
Non-voice terminals can only be used by the user if the basic classmark (BASIC) for the rele-
vant service has been added (AMO COSSU) to his class-of-service.
If INS=Y (default), the added connection together with all voice and non-voice terminals will be
transferred to the dependability system for further processing. When all preconditions are met,
the relevant terminal will be taken into operation.
If INS=N, the subscriber remains in a state which will not be processed by the dependability
system, the terminal will not be taken "into operation", and advance provision will only be made
with respect to the data required. AMO DSSU allows the terminal to be "ACTIVATED" , "DEAC-
TIVATED" at a later stage. The exact state of the terminal can be queried using AMO SDSU.
The LCOS-Parameters for voice and data are mandatory, because of path selection is always
done by Least Cost Routing mechanism. If a device has no data equipment, the LCOSD-Pa-
rameters are required but without effect.
181
EN4402EN00EN_0003
© 2004 Siemens AG
Examples
1. Assign subscriber 3653 with an ANATE voice terminal at a specific PEN.
Input:
ADD-SCSU:STNO=3653,PEN=1-2-121-5,DVCFIG=ANATE,DPLN=0,ITR=0,COS1=9,
COS2=9,LCOSV1=9,LCOSV2=9,LCOSD1=9,LCOSD2=9,DIAL=VAR;
Output:
H06: 3653 THIS STATION IS CONFIGURED AT PEN 1-2-121-5.
H11: 3653 CONTROL HAS BEEN PASSED TO CALL PROCESSING FOR STATION ACTIVATION
2. Assign 3 ANATEs with charge metering. The required SLMAR-Port is determined automat-
ically by AMO. The search for free PENs should start at 1-1-43-0 (in this example, the cir-
cuits 0,1,3 are assumed to be already seized)
Input:
ADD-SCSU:STNO=2161&&2163,PEN=1-1-43-0,DVCFIG=ANATECM,DPLN=0,ITR=0,COS1=9,COS2=8,
LCOSV1=7,LCOSV2=6,LCOSD1=5,LCOSD2=4,PULSTYPE=POL12,PULSLEV=VEFF5;
Output:
H45: THE AUTOMATIC PEN SEARCH FOR FREE PENS TAKES PLACE IN LTU SHELVES WITH
SOURCE-GROUP=1 (SEE AMO UCSU).
H33: 2161 FOR DVCFIG = ANATECM CHARGE PULSE DURATION AND PAUSE CAN BE CHANGED
BY AMO PTIME.
H06: 2161 THIS STATION IS CONFIGURED AT PEN 1-1-43-2
BY AMO PTIME.
BY AMO PTIME.
28.2 CHANGE-SCSU
All data except
● the device configuration,
● the Port Equipment Number (PEN)
can be changed.
AMO SXSU is used for changing the DVCFIG or PEN and for exchanging station numbers (be-
tween two stations).
182
EN4402EN00EN_0003
© 2004 Siemens AG
If TEXTSEL has to be changed, the circuit must be locked. This can be performed by AMO
DSSU or by specifying parameter OFFTYPE in AMO SCSU.
Changing some circuit specific data requires downloading into the module. Such data includes
the parameters COFIDX, CCTIDX, PULSTYPE, PULSLEV and DHPAR=[LEDSIGN, MWLED,
RING1] and DIAL. The data is loaded using
– the commands DEACTIVATE and (re-)ACTIVATE-DSSU "with unconditional loading"
(e.g. RESTART-DSSU)
– parameter OFFTYPE=DC (Default) or OFFTYPE=DI. The circuit must be in READY or
UNACH state (can be interrogated by AMO SDSU). In UNACH state, data is loaded
automatically when hierarchy becomes ready.
A station number cannot be changed to another station number if the original station number
is in an ACD Routing Table or has assigned an ACD-Attribute.
Example
Change COS 1 and 2 for subscriber 261.
Input:
CHANGE-SCSU:STNO=261,COS1=5,COS2=6;
Output:
H09: 261 STATION DATA CHANGED.
28.3 DELETE-SCSU
This action can be used to delete
● specific STN data (parameter CMIND) or
● the connection as such (CMIND=ALL).
Prior to deleting the connection, the connection must be blocked:
– the station is locked by AMO DSSU or
– in command the parameter OFFTYPE=DC is specified and the station is not busy in
call processing (DC is the default value of OFFTYPE)
– in command the parameter OFFTYPE=DI is specified
It should be noted that a connection can only be deleted if it is not part of one of the following
groupings:
● Hunting group (AMO SA)
● Night variant (AMO NAVAR)
183
EN4402EN00EN_0003
© 2004 Siemens AG
● Call pickup group (AMO AUN)

● ACD Routing Table (AMO ACDRT)
● ACD-Attribute assigned (AMO SDAT)
All other assignments of the station number such as DSS destinations, call forwarding destina-
tions, individual night station, call backs etc. are cleared automatically upon deletion.
Deleting CMIND=DHPAR or CMIND=SUFDIAL requires eventually downloading of changed
data to the board. For that, the cross reference to AMO DSSU respectively parameter
OFFTYPE has to be considered (as specified for action CHANGE).
Example
Delete subscriber 280 with all its features.
1. Blocking the subscriber
Input:
DEACTIVATE-DSSU:TYPE=STNO,STNO=280;
Output:
H03: 280 DEACTIVATED
2. Cancel the subscriber after explicit locking

Input:
DELETE-SCSU:STNO=280,CMIND=ALL,OFFTYPE=NL;
Output:
3. Lock and cancel the subscriber

Input:
DELETE-SCSU:STNO=280,CMIND=ALL,OFFTYPE=DI; /* IMMEDIATE LOCK */
or
DELETE-SCSU:STNO=280,CMIND=ALL; /* CAMP-ON LOCK */
or
DELETE-SCSU:STNO=280,CMIND=ALL,OFFTYPE=DC; /* CAMP-ON LOCK */
184
EN4402EN00EN_0003
© 2004 Siemens AG
28.4 DISPLAY-SCSU
The following data can be displayed:
1. Station numbers of users who have been assigned a specific COS.
2. Station numbers of users with specific characteristics (see parameter STNTYPE).
3. Station numbers of users who have been assigned a specific LCOSV.
4. Station numbers of users who have been assigned a specific LCOSD.
5. Station numbers with a specific attribute (see parameter ATTR).
6. Station numbers with a specific connection type.
7. All connection-specific data.
Examples
1. Interrogate all subscribers with COS=1 assigned
Input:
DISPLAY-SCSU:TYPE=COS,COSNO=1;
Output:
--------------------------------------------------------
STATION WITH COS = 1
--------------------------------------------------------
2100 2109 2110 2111 2112 2113
2114 3105 3106 3107 3114 3115
3153 3154 3158 3160
--------------------------------------------------------
2. Interrogate all analog subscribers with charge metering equipment

Input:
DISPLAY-SCSU:TYPE=HW,STNTYPE=ANATECM;
Output:
--------------------------------------------------------
STATION(S) WITH CHARGE METERING
--------------------------------------------------------
450 451 452 453 454 455
470 471 472 473 474 475
--------------------------------------------------------
185
EN4402EN00EN_0003
© 2004 Siemens AG
3. Interrogate the subscribers in the directory number range 200 to 230 with the subscriber
class of service DTMF (dual tone multifrequency pushbutton dialing).
Input:
DISPLAY-SCSU:STNO=200&&230,TYPE=HW,STNTYPE=DTMF;
Output:
--------------------------------------------------------
STATION WITH DUAL TONE MULTIPLE FREQUENCY
--------------------------------------------------------
200 201 202 203 204 205
206 207 208 209 220 221
222 223 224 225 226 227
228
--------------------------------------------------------
4. Interrogate all signed off stations

Input:
DISPLAY-SCSU:TYPE=ATTR,ATTR=SIGNOFF;
Output:
--------------------------------------------------------
SIGNED OFF STATION(S)
--------------------------------------------------------
2140 2141 2142
--------------------------------------------------------
5. Interrogate all data for subscriber 2110

Input:
DISPLAY-SCSU:STNO=2110;
Output:
------------------------------- USER DATA -----------------------------------
STNO =2110 COS1 =22 DPLN =0 SPDI =10
PEN = 1- 1- 25- 0 COS2 =1 ITR =7 SPDC1 =0
DVCFIG =ANATE LCOSV1 =1 COSX =0 SPDC2 =1
INS =YES LCOSV2 =1 RCBKB =NO
ALARMNO =0 LCOSD1 =1 HMUSIC =0 RCBKNA =NO
SSTNO =NO COTRACE =NO LCOSD2 =1 SPEC =
COFIDX =0 DIAL =DTMF PULSTYPE= PULSLEV=
CCTIDX = ACKST = TEXTSEL=
DHPAR =
CONN =DIR FLASH =YES DTMFBLK =NO WITKEY :NO
------------------- ACTIVATION IDENTIFIERS FOR FEATURES ---------------------
FWDS :NO FWDF :NO FWDD :NO DND :NO CWT :NO
HTOS :NO HTOF :NO HTOD :NO VCP :NO
--------------------- FEATURES AND GROUP MEMBERSHIPS ------------------------
186
EN4402EN00EN_0003
© 2004 Siemens AG
PUGR :1 HUNTING GROUP : NO

NIGHT OPTION : YES
------------------------- STATION ATTRIBUTES (AMO SDAT) ---------------------
KN VC
-----------------------------------------------------------------------------
THIS STATION IS ENTERED IN NIGHT OPTION 1.
The output data for a station is subdivided into 3 groups:

1. Data which are also contained in the input command (marked by "=").
2. Activation identifiers for the features.
3. Features and group memberships which are not assigned by the AMO SCSU.
Explanation of ACTIVATION IDENTIFIERS FOR FEATURES
FWDS : Call forwarding for voice (speech)

FWDF : Call forwarding for FAX
FWDD : Call forwarding for data terminal equipment (DTE)
HTOS : Hunting group out, voice (release from hunting group)
HTOF : Hunting group out, FAX
HTOD : Hunting group out, DTE
DND : Do-not-disturb
VCP : Voice call protection
CWT : Call waiting - terminating
WITKEY : Witness Key
Explanation of FEATURES AND GROUP MEMBERSHIPS
PUGR : Included in a call pickup group

HUNTING GROUP : Included in a call hunting group
NIGHT VARIANT : Included in a night service variant
STATION ATTRIBUTES : Attributes which can only be set and reset by AMO SDAT.
The description of the attributes can be found in AMO
description (AD) of SDAT
187
EN4402EN00EN_0003
© 2004 Siemens AG
28.5 REGENERATE-SCSU
Example
Regenerate the subscribers with station numbers 2100, 2102 and 2103.
Input:
REGENERATE-SCSU:STNO=2100&2102&2103;
Output:
ADD-SCSU:2100,1-1-25-0,ANATE,0,7,22,1,1,1,1,1,0,1,0,10,0,,,
DTMF,,,,,YES,,NO,,,,0,DIR,YES,NO;
ADD-SCSU:2102,1-1-25-2,ANATE,0,7,2,4,1,1,1,1,0,,1,10,0,,,
DTMF,,,,,YES,CHR&TE,NO,,,,0,DIR,YES,NO;
ADD-SCSU:2103,1-1-25-3,ANATE,0,0,3,4,1,1,1,1,,,1,10,0,,,
DTMF,,,,,YES,CHR,NO,,,,0,DIR,YES,NO;
Permitted device combinations (DVCFIG) of a subscriber to the modules (the sequence of the
devices in a combination is as desired).
DEVICE COMBINATION MODULE

ANATE SLMA/1/2/3/24/B/R (1)
TMDNH
ANATE FAX SLMA/1/2/3/24/B/R (1)
TMDNH
ANATE DTEANA SLMA/1/2/3/24/B/R (1)
TMDNH
ANATECM SLMAR
AUXDIGI SLMB, SLMB4
(1) Means: SLMA, SLMA1, SLMA2, SLMA3, SLMA24, SLMAB or SLMAR, note that the SL-
MAR board is skipped for free PEN search.
188
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: SDAT - Administration of Individual Subscriber Attributes and
29 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.
29.1 CHANGE-SDAT
29.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.
29.1.2 Compatibility between the Attributes

● AUTOLOG can only be set in combination with AGENT.
● DNDSR can only be set in combination with AGENT or SUPER.
● HOT cannot be set with AGENT, SUPER, CASTMON, DNDSR, or OFHKRC.
● KN and KNOVR cannot be set at the same time.
● LNGDYN and LNGSTAT cannot be set at the same time.
● TEAMSECR and TEAMEXEC cannot be set at the same time.
● ROUTINE, PRTY, IMMED, FLASH and/or FLASHOV can not be set at the same time
189
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: SDAT - Administration of Individual Subscriber Attributes and Siemens
29.1.3 Compatibility of Attributes with Equipment
Tabelle 5:
AGENT/ SUPE DNDS CA CAS HOT/KN/ AN LOADF/ SPKR-
AUTOLOG/ R R F TMO KNVOR/ I LOSC/ CALL/
NORELOC/ N/ RKNVOR/ LOENB/ BROADC
ALOGONTW CBS EOVR/ LNGSTAT/ ST
TMO VC/OFH- LNGDYN/
N KRC TEAM-
CHEF/
TEAMSEC
R/ COM-
SPK/ ETD
Anate * - * - * * * - *
external - - - - - - - - -
DTE
Optiset/ * * * * * * * * *
Optipoint
500
Set600 - - - - - * * - -
FPP S0 / - - - - - * * - -
S2
CMI-Base - - - - - - - - -
CMI-Extline - - - - - - - - -
CMI-ADM - - - - - - - - -
CMI-Radio * * * * * * * - -
Sky-Mana- - - - - - - * - -
ger
Sky-Extline - - - - - - * - -
Sky-Phone - - - - - * * - -
Sky-Line * * * * * * * - -
TC-Logopti - - - - - * * - -
TCVLV - - - - - - * - -
190
EN4402EN00EN_0003
© 2004 Siemens AG
CFNR, DSSDEST, DSFWDEXT, NOSPKFWD, ROUTINE, PRTY, FLASH, FLASHOV, PROT

and MLPPS are possible for all equipment types.
* Attribute is possible for the subscriber.
- Attribute is not possible for the subscriber
29.1.4 Compatibility of Attributes with Special Subscriber
Tabelle 6:
Merkmale AGENT/ SUPER DNDSR CAF CAST CBST

AUTOLOG MON MON
Station signed off * * * * * *
Floating station - - - - - -
Station with * * * * * *
assosiated DCI
CHESE executive) - * * * * -
CHESE secretary - - - - - -
CHESE * * * * * *
representative
Attributes which were not mentioned are possible for all special subscribers described
above.
* Attribute is possible for the subscriber.
- Attribute is not possible for the subscriber
Note:
Agent should not be set for SBCSU or SCSU subscribers with SECR=YES.
29.1.5 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.
191
EN4402EN00EN_0003
© 2004 Siemens AG
29.1.6 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.
NNO
Only vitual nodes which are marked as "subscriber" (TYPE=OWN, see AMO KNDEF) will be
administered. It is only possible to change one node id to another. If no default node id is con-
figured by AMO SCSU, SBCSU or SSCSU AMO SDAT can not assigned another node id.
The virtual node id can contain max. 3 levels
Form: <level2>-<level1>-<level0> (e.g. 1-2-3 or 3-15 or 222)
Levels have to be filled from low to high (e.g not allowed 1-0-12 or 1-0-0)
Possible Values: level2: 0-29, level1: 0-253, level 0: 1-999
CDRACC
The Account Code (ACC) is used to bill call cost and time to individual customers or projects.
CDR Account Code is a new feature and will not affect the existing Project Code (PCODE) fea-
ture. When a CDR Account Code is configured as default (automatic) Account Code for a de-
vice by AMO SDAT, this Account Code is assigned to all internal, outgoing or incoming calls of
this station.
A static assignement of an account code to all station numbers is possible, except all "functional
devices" (including ANATE behind OPTISET) and "Teleworking devices" (AMO SSCSU).
PUBNUM, TON, NPI

Administration of a public telephone number for subscriber devices can be done by AMO SDAT.
This public telephone number is used in conjunction with calls placed to the public network via
PRI trunks. The public telephone number has to be used whenever a number related to a given
HiPath 4000 subscriber device must be signalled to the public network via PRI.
192
EN4402EN00EN_0003
© 2004 Siemens AG
Only the following combinations of parameter NPI and TON are allowed:
Tabelle 7:
Explicit Format Implicit Format

NPI=UNKNOWN
NPI=ISDN(E164) NPI=PNP(private)
TON=INTERNAT TON=L2REGIO TON=UNKNOWN
(international number) (level 2 regional number)
TON=NATIONAL TON=L1REGIO
(national number) (level 1 regional number)
TON=SUBSCR TON=LOCAL
(subscriber number) (local number)
TON=UNKNOWN TON=UNKNOWN
(unknown) (unkown)
TON=ABBR
(abbreviated number)
If PUBNUM shoud be configured and no values for TON and/or NPI are entered and no valid
value for TON and/or NPI is configured, the default value UNKNOWN will be assigned for TON
and/or NPI.
SRCGRP/CLASSMRK
The source group of a subscriber is always initialized with default value zero. Via this default
value the subscriber belongs to the source group of the LTU shelf where it is configured. AMO
SDAT can configure the subscriber also in an other source group.
The classmarks of a subscriber are initialized with default value G711, EC and G729OPT. With
CLASSMRK=INIT the classmarks are reset to this initial values. If classmark NONE or INIT is
specified no other values are allowed in combination with.
HOTIDX
AM administrates a table with up to 512 destinations for Hotline / Off Hook. This will be done
by AMO-HOTLN.
Each station with Hotline / Off Hook classmark has to get a Hotline index. This will be adminis-
tered per STNO with AMO SDAT. AMO SDAT checks neither that every station with HOT or OF-
HKRC classmark has a Hotline Index because AMO COSSU administrates HOT and OFH-
KRC, too, nor the entered Hotline Index leads to a valid entry from AMO HOTLN.
193
EN4402EN00EN_0003
© 2004 Siemens AG
29.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.
29.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 =
194
EN4402EN00EN_0003
© 2004 Siemens AG
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
195
EN4402EN00EN_0003
© 2004 Siemens AG
29.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;
196
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: PERSI - Personal Identification
30 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.
The same class of service changeover code (COSXCD) can be assigned to any
number of stations. When a COSXCD that was previously assigned to a station is con-
figured, the system outputs advisory message H38 to notify the user of this fact, and
the command is still executed. If the user does not want the COSXCD to be assigned
197
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: PERSI - Personal Identification Siemens
to multiple stations, he can delete the COSXCD for the station with DEL-PER-
SI:TYPE=PIN,PIN=number,STNO=number ;
In the case of PINC, it must also be determined at which position on the magnetic/chip
card the PINC begins. (PIN pointer)
A ’Class of PIN’ (COPIN) must be introduced for each type of PIN to be able to imple-
ment the PIN display feature and to be able to differentiate between the various types
of PINs.
The COPIN defines the characteristics and functions of individual PIN applications
such as the type of PIN (PINM, PINC, COSXCD, PCODE etc.), PIN length, PIN texts
and various flags used to disable or enable specific functions.
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 CO-
PIN 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
The COPIN table allows the administration of all entries except the timer administration
(AMO CTIME) using the AMO PERSI. Please note that the type of PIN can only be
changed for COPINs 1-5,10-15 and that for the PIN card only COPIN 6 is used, COS
changeover only COPIN 7 is used whereas for service id only COPIN 8 and CDR ac-
count code only COPIN 9 is used.
198
EN4402EN00EN_0003
© 2004 Siemens AG
Each PIN has at least one COPIN for identification of the PIN type.
However, a PIN may also be valid for several PIN types. Such a PIN is assigned more
than one COPIN.
For data protection reasons, manually keyed-in PINs are not displayed, instead a wild-
card ’*’ is displayed for each character.
To allow the user to check whether he has entered the PIN or PCODE correctly, he can
use the parameter PINDISP or parameter DISPPIN (TYPE=COPIN) which allows
each type of PIN to be administered separately.
The parameter COSXCOS2 is used for COS changeover to COS2 with or without a
COSXCD.
d) Company code (COCO)
If several companies share a system, a 1- to 4-digit COCO on the magnetic/chip card
indicates the card owner’s company code. As a result of this, several companies can
be assigned the same PIN.
The company code pointer (CPOINT) marks the position at which the COCO begins
on the ID card. This position may coincide with that of the PINC.
The COCO is assigned for each ITR group since the STNs are categorized into ITR
groups if several companies share the same system.
e) STNO-Code calling number conversion for code calling system, multiple (CCMS).
Some CCMSs have a repertory of code calling numbers which differs from the sys-
tem’s station number plan. Since individual persons are paged via their station num-
bers, it is necessary to convert the STNOs into CCMS code calling numbers. During
conversion, several station numbers may be assigned the same code calling number,
but not vice-versa.
A maximum of 2 CCMSs can be connected to the system. This is why, during STNO-
Code calling number conversion the relevant CCMS is identified by its code (or else by
the DPLN group it belongs to).
The size of the memories to be used for PERSI data (NAME, ORG, PIN) is defined by
means of AMO DIMSU. For each ’STNO-Code calling number’ conversion one table
is available for each CCMS (1000 entries).
This AMO is non-resident and is only called down by the AM.
f) project code (PCODE)
The PCODE is used to assign call charges to specific projects. For this reason, it is not
assigned to any of the users.
The PCODE is activated with the same code as the PIN.
The PCODE remains active only for the duration of a call.
The PCODE can also be entered while a PIN is active (mobile STN). In this case, the
data and the classes of service of the PIN’s home station are valid.
199
EN4402EN00EN_0003
© 2004 Siemens AG
g) service id (SI)
The service id is used to sign off resp. sign on a station.
The service id is activated with the sign off resp. sign on code.
h) CDR account code (CDRAC)
The CDR account code is used as account code for incoming and outgoing call, which
are listed in the call charge data output.
i) modulo check algorithm
The validity check on a PIN or project code cannot only be performed by comparing
the entry in the PIN/Project code table created by the PERSI AMO but also using a
module check algorithm. It is possible to define 3 modulo check algorithms in the sys-
tem (action CHANGE TYPE=MODULO), see also Chapter "AMO applications" in the
Service Manual.
With which of the 3 algorithms the check is to be carried out can be specified individ-
ually for each type of PIN.
30.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
(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)
200
EN4402EN00EN_0003
© 2004 Siemens AG
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;
30.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
201
EN4402EN00EN_0003
© 2004 Siemens AG
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.
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.
202
EN4402EN00EN_0003
© 2004 Siemens AG
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;
30.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
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.
203
EN4402EN00EN_0003
© 2004 Siemens AG
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;
30.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
Examples
Interrogating the general PERSI data.
Input:
DISPLAY-PERSI:TYPE=SYS;
204
EN4402EN00EN_0003
© 2004 Siemens AG
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* | |
+--------+---------------------------------+--------------------------+
205
EN4402EN00EN_0003
© 2004 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 STNO/CCNO conversion table for CCMSCD=922 (CCMS) and

STNO=2100&&2110
Input:
DISPLAY-PERSI:TYPE=CCMS,CCMSCD=922,STNO=2100&&2115;
Output:
+--------+--------+
| STNO | CCNO |
+--------+--------+
| 2100 | 2105 |
| 2101 | 2108 |
+--------+--------+
206
EN4402EN00EN_0003
© 2004 Siemens AG
12. 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 . . . . . . . . . . |
+--------------+--------+------------------------------------+
13. 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 . . . . . . . . |
+--------------+--------+----------------------------------+
14. 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 . . . . . . . . . . . |
+--------+--------------+------------------------------------+
207
EN4402EN00EN_0003
© 2004 Siemens AG
15. 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 |
| | 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 |
208
EN4402EN00EN_0003
© 2004 Siemens AG
+-------+-------------------------------------------------+
| 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 |
| | 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 |
209
EN4402EN00EN_0003
© 2004 Siemens AG
| | 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 |
+-------+-------------------------------------------------+
| | PINTEXT = ’CDR ACCOUNT CODE ’ |
| | CDRACLEN = 5 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
| | PINTEXT = ’FAC, 1 CALL ’ |
| | PIN10LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
210
EN4402EN00EN_0003
© 2004 Siemens AG
+-------+-------------------------------------------------+
| | PIN11LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
| | PIN12LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
| | PIN13LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
211
EN4402EN00EN_0003
© 2004 Siemens AG
| | PIN14LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
| | PIN15LEN = 0 |
| | CDRTEXTS = NO |
| | CDRTEXT = ’ ’ |
+-------+-------------------------------------------------+
16. Display all modulo check algorithms

The example shows the initialisation.
Input:
DISPLAY-PERSI:TYPE=MODULO;
Output:
+--------+-------------------------------------------------+
| MODULO | MODULO CHECK ALGORITHM PARAMETER |
+--------+-------------------------------------------------+
| 1 | VALENCE = 1-1-1-1-1-1-1-1-1-1-1-1 |
| | TYPESUM = SUMPRO MODULUS = 10 |
| | CHKNLEN = 1 TYPECHKN = COMPREM |
+--------+-------------------------------------------------+
| 2 | VALENCE = 2-1-2-1-2-1-2-1-2-1-2-1 |
+--------+-------------------------------------------------+
| 3 | VALENCE = 2-1-2-1-2-1-2-1-2-1-2-1 |
+--------+-------------------------------------------------+
212
EN4402EN00EN_0003
© 2004 Siemens AG
30.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-
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-
213
EN4402EN00EN_0003
© 2004 Siemens AG
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;
214
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Call Log for optiset E
31 Call Log for optiset E

This feature is available from V3.0. It is also known as call journal.
0089722333 Huber
Busy 31.12.1999 17:19
0567478 Allgaier
Per entry the following data is stored: free 31.12.1999 18:19
● station number max. 22 digits Call list

Call journal
● name (if available) max. 30
characters
● date/time
60%
● Info: free / busy / call state
80%
100%

The last incoming and outgoing calls are logged for optiset E terminals with display. The user
can query the stored information and use the entries to establish outgoing connections.
In the part of the call log reserved for outgoing calls the last six called users are entered. In the
part reserved for incoming calls the last twelve calling users are stored. The entries are sorted
starting from the newest and ending with the oldest entry.
The following data is stored for every entry:
● station number max. 22 digits
● name (if available) max. 30 digits
● date / time
● info: free / busy / call state
215
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Call Log for optiset E Siemens
31.2 Feature Characteristics

● The feature can only be used with optiset E terminals.
● There are two different ways to log incoming calls, depending on the station:
– Logging of all incoming calls regardless of whether a connection was established or
not. => ALL
– Logging of the unsuccessful connection attempts. => TRIES
– Calls are also logged during a temporary failure of the terminal as unsuccessful call
attempts.
● The dialed destination number is logged, even if a different destination was reached due
to call forwarding.
● Outgoing calls established by using number redial, direct call or repertory key are not
stored in the outgoing calls log.
● Outgoing calls established by using the optiset ENB or a data adapter / dialing aid are
logged.
● If a call is signalled on several stations, e.g. group call, RNA, HG, the call is logged in the
call log of all called stations.
● CHESE calls for the executive which are picked-up by the secretary, are logged in the ex-
ecutive’s call log.
● There is no key to query the call log. Readout is performed using the user interface dialog.
● If Autoset Relocate is set, the call log is also moved.
● The call log can only be read on the home station.
● The call log cannot be modified or stored using administration and maintenance.
● With optiset E, the call log is protected against unauthorized use by the feature Data Se-
curity .
● The call log contents is retained after hard and soft restarts.
● Call log is only realized for voice services.
216
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Call Log for optiset E

● An optiset with display requires approximately 1.1 KB memory space which must be gen-
erated in DIMSU.
● In V3.0 memory space is reserved in DIMSU AMO for app. 30% of optisets. Regardless of
this memory, additional memory can be reserved for the call log, depending on the PBX.
● Depending on the basic DIMSU configuration the maximum number of optisets can be ex-
panded to the following maximum values, depending on the memory capacity:
PBX type Memory capacity in MB Number in %

310 32 60
330 36 80
350 48 100
350 64 100
● This feature is marketed with every station and needs no special release by code word.
● If stations with COM-manager or for e.g. with their own integrated call logs are used, the
internal Hicom call log should not be configured.
● This feature is not available for Cordless Multicell Integration and Hicom Trading E.
31.4 AMO Modifications

Language
DIMSU CALLOG d CC2: Anzahl der optiset mit Anrufliste
CALLOG e CC2: Number of optiset with call log
FEASU ANRLSOPT d Anrufliste für optiset
CALOGOPT e Call log for optiset
SBCSU RJOURNAL d KEIN: Kein Rjournal ist gesetz
VERSUCH: Nur erfolglose, ankommende Verbindungen
ALLE: Alle ankommenden Verbindungen
CALLOG e NONE No call log activated
TRIES: Only unsuccessful incoming connections
ALL: All incoming connections
217
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Call Log for optiset E Siemens
31.5 AMO Commands
31.5.1 Call Log Configuration

1. Release the call log feature in the system:
CHA-FEASU:A,CALOGOPT;
2. Define the number of users with call log authorization in the system:
ADD-DIMSU:TYPE=CC2,CALLOG=n;
3. Assign the feature to an optiset E station:
a) Logging of unsuccessful connection attempts
CHA-SBCSU:STNO=nr,CALLOG=TRIES;
b) Logging of all incoming calls
CHA-SBCSU:STNO=nr,CALLOG=ALL;
31.5.2 Protection of the Individual Call Log

If the COS changeover is set to COSACT=1, browsing in the call log is always allowed. The call
log is protected, if the COS is set to COSACT=2.
Note: See Data Security with optiset E / optiPoint 500
218
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Data Security with optiset E / optiPoint 500
32 Data Security with optiset E / optiPoint 500

Depending on the level, this feature inhibits unauthorized access to key contents and the cor-
responding key functions for every type of optiset E and optiPoint 500 terminal.
Three level locking possibilities

a) protected functions
Electronic Notebook (ENB)
b) Servicemenu key
Callback
Do-not-disturb
etc.
c) Dialing aid:
Repertory key
DSS key
Timed reminder
Number redial
Speed dialing
Activation by:
User Attendant console Time / BERUZ
Locking is possible for individual users or groups
Locked features can’t be activated by using a feature code
219
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Data Security with optiset E / optiPoint 500 Siemens

● This feature need not be dimensioned (AMO CODEW, AMO DIMSU), nor is a special re-
lease necessary (AMO FEASU)
● After setting the appropriate protective parameters using SDAT AMO, the feature is effec-
tive (only for optiset E and optiPoint 500 terminals) with every activation by a COS
changeover.
● Locking possibilities can be combined.
● The terminal is protected depending on the COS.
32.3 AMO Changes
AMO Parameter Sprache/ Beschreibung/

Language Description
SDAT SPAWH d Sperre aller Wahlhilfefunktionen,
d.h. der Ziel-, Direktruf-, Wahlwiederholungs-, Kurzwahl-
Taste
LOADF e Locking of all dialing aid functions, i.e. the repertory, DSS,
number redial and speed dialing keys
SPSC d Sperre der Check-Funktion (für Endgeräte ohne Display)
bzw. des Service Menüs,
d.h. es kann
- keine Umleitung (fest oder variabel)
programmiert oder abgefragt,
die feste Umleitung hingegen aktiviert und
jede Umleitung (fest oder variabel) deaktiviert
- kein Direktruf, Rückruf, Termin,
keine Wahlwiederholung (SNR, LNR), Zielwahl
programmiert, abgefragt oder angewendet
- kein Anrufschutz, Ansprechschutz
aus- oder eingeschaltet
- keine Tastenbelegung geändert
werden
220
EN4402EN00EN_0003
© 2004 Siemens AG
AMO Parameter Sprache/ Beschreibung/

Language Description
LOSC e Locking of the Check function (for terminals without display)
or the service menu,
this means
- no forwarding (fixed or variable)
can be programmed or queried,
however fixed forwarding can be activated and
both forwarding types (fixed or variable) can be deactivated
- no DSS call, callback, timed reminder,
number redial (SNR, LNR), repertory dialing
can be programmed, queried or used
- no DND, stop voice calling can be activated or
deactivated
- no key layout can be modified
SPENB d Sperre des Elektronischen Telefonbuchs
im optiset E memory (ENB),
d.h. Daten können weder eingetragen noch abgefragt wer-
den
LOENB e Locking of the electronic telephone book
in the optiset E memory (ENB),
i.e. it is not possible to either enter or query data
32.4 Generation
Activation of access protection (here: for station 7140):
32.4.1 Query whether the Required Protective Parameters Have Been

Set
DIS-SBCSU:STNO=7140;
or
DIS-SDAT:STNO=7140,TYPE=SUBDATA;
Make sure that the terminal is an optiset E or optiPoint 500, using the output data
(field DVCFIG shows OPTISET resp. OPTIP500).
Attributes already set can be found either under the SUBSCRIBER ATTRIBUTES (AMO
SDAT) section of the DIS-SBCSU output or under the ATTRIBUTES section of the
DIS-SDAT output.
221
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Data Security with optiset E / optiPoint 500 Siemens
32.4.2 Set the Required (e.g. all) Protective Attributes

CHA-SDAT:STNO=7140,TYPE=ATTRIBUT,AATTR=LOADF&LOSC&LOENB;
The terminal is locked by COS changeover. There are several possibilities to change the COS :
● on a terminal with ID card reader by inserting/pulling through the ID card
● from the terminal by dialing procedure
● from the attendant console
● from the service terminal (AMO BERUM)
● after timeout for an entire COS changeover group
32.4.3 Reset the Corresponding Protective Attributes

CHA-SDAT:STNO=7140,TYPE=ATTRIBUT,DATTR=LOADF&LOSC&LOENB;
Regardless of the set COS, all previously locked keys and functions can now be accessed.
32.4.4 Configuration of the COS Changeover (BERUM)

Note: BERUM need only be set if the feature has not yet been configured.
DIS-WABE:TYPE=GEN,DPLN=0&&15,DAR=ACOSX&DCOSX;
If necessary, configure codes (e.g. *18 for activation and #18 for deactivation) either DPLN de-
pendent (code is only valid for one or several DPLN, such as 0 to 5) or DPLN independent (with-
out specification of the DPLN parameter) with:
ADD-WABE:CD=*18 [,DPLN=0&&5] ,DAR=ACOSX,CDDP=818;
/* CDDP as substitute code */
/* for non DTMF devices */
ADD-WABE:CD=#18 [,DPLN=0&&5] ,DAR=DCOSX,CDDP=8018;
/* CDDP as substitute code */
/* for non DTMF devices */
32.4.5 Configure the Authorization for "COS Changeover with Code"

Establish COS1 and COS2
DIS-SBCSU:STNO=7140;
or
DIS-SDAT:STNO=7140,TYPE=SUBDATA;
222
EN4402EN00EN_0003
© 2004 Siemens AG
Query the COS authorizations:

DIS-COSSU:TYPE=COS,COS=<cos1>&<cos2>;
Should the authorization COSXCD not be set in the column VOICE, the authorization has to be
added to the COS of the station" :
CHA-COSSU:TYPE=COS,COS=<cos1>&<cos2>,AVCE=COSXCD;
32.4.6 Configure the Station-Specific COSXCD for BERUM

Query if a PIN is assigned for BERUM.
DIS-PERSI:TYPE=STN,STNO=7140,PINTYPE=7;
If no specification has been made, check that the preconditions for configuring COSXCDs have
been met:
DIS-PERSI:TYPE=SYS;
Define the general code length for the COS changeover (e.g. every COSXCD has 4 digits), if
necessary:
ADD-PERSI:TYPE=SYS,COSLEN=4;
Configure the COS changeover code for the station (e.g. 1234), if necessary:
ADD-PERSI:TYPE=STN,STNO=7140,COSXCD=1234;
32.4.7 Activate/Deactivate COS Changeover from the Terminal

Input of the activation code (from WABE ACOSX e.g. *18) followed by COSXCD (as added in
AMO PERSI e.g.1234) on the terminal. After the changeover, a special dial tone should be in-
jected instead of the normal one, when the handset is lifted.
Enter the deactivation code to unlock the respective keys or functions:
Enter the deactivation code (e.g. #18) on the terminal.
After the COS changeover the normal dialing tone is injected when the handset is lifted.
Delete the protective parameters for the station to unlock the keys after a COS changeover:
223
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Integrated Key Functionality Multi-Line Access Siemens
33 Integrated Key Functionality Multi-Line Access

The Integrated Key Functionality feature is available from Hicom 300E V3.0.
The feature functions are similar to team systems or multi-line key telephone systems.
Primary
Max. 28 lines per terminal
Max. 40 terminals per line Line 1
12 pre-configured keylayouts of which 4
Line 2
are reserved for ACD terminals
Functional on all optiset E telephones Line 3
Line status display by LED
Line 4
Not allowed with the executive/secretary
feature. Line 5
Keyset
Line 6
Line 7
Keyset
Primary
Keyset Line 1
Line 2
Available from Hicom 300 E V3.0
Feature can be used only locally Line 3
Release by code Line 4
Number of keysystems limited by DIMSU
Line 5
Keyset
Line 6
Keysystem Line 7
Teamset
Key telephone system
Multi-line key telephone systems
224
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Integrated Key Functionality Multi-Line Access

Multi-line access is available from Hicom 300E V3.0. It comprises new features and affects
many existing features.
Multi-line access can only be activated by Optisets which have been specially configured using
AMO KCSU. Optisets configured for this purpose will be referred to as Keysets in this docu-
ment.
Multi-line access allows seizure of a primary line (initial line) and up to 28 secondary lines from
a Keyset for incoming and outgoing calls. Every line corresponds to a station number. One line
can be assigned to as many as 40 different optisets. For every line there is a line key with LED
on the terminal. The LED signals the line state. Free: LED is off, seized: LED is on, call state:
LED flashes rapidly, call on hold: LED flashes slowly.
33.1.1 Brief Description of Keyset Features

● Every Keyset has an initial or primary line which is reached via the main station num-
ber. This line can be assigned to other Keysets as secondary line.
● A phantom line is assigned to other terminals as a secondary line and is not assigned to
any terminal as a primary line. A phantom line is configured as a logged-off Keyset, i.e once
the phantom line is configured (SBCSU:ins=signoff). It must be added as a prime line in
KCSU to enable it to be added as a secondary line on other Keysets.
● Call: Every line can be configured to be either a line with, or without, ringing (KCSU, RIOP
parameter). Ringing tone is activated as soon as a call is signalled on one of the lines for
which ringing has been configured for this particular station. The LED of the line key flash-
es. Several simultaneous calls are signalled in the order of their arrival. Different ringing
can be set for all line keys for which the ringing tone has been programmed. If the ringing
tone cannot be injected because the Keyset is busy an alerting tone is activated (if config-
ured, KCSU, BUSYRING parameter).
● Line selection: Automatic and manual line selection is available.
– With automatic line selection one of the configured lines is automatically seized as
soon as the user goes off-hook to initiate or answer a call. Several options can be set
defining the preferences of outgoing and incoming connections.
– Depending on the configured option either the primary line (KCSU, ORL-
NPF=PRIME), the last used line (KCSU, ORLNPF=LAST), any free line (KCSU;
ORLNPF=IDLE) or no line (KCSU; ORLNPF=NONE -- > manual selection re-
quired) is seized for outgoing connections.
– Depending on the configured option, either a calling line (KCSU; TML-
NPF=RING), any incoming line (the calling lines are queried first, followed by lines
not set for ringing, on a FIFO basis. KCSU; TMLNPF=ALER) or no line (KCSU;
225
EN4402EN00EN_0003
© 2004 Siemens AG
TMLNPF=NONE) is selected for incoming connections. Calls on the primary

line can be set to be answered with priority regardless of the time of their arrival
(KCSU; TMLNPF=RINGP or ALERP).
● Using manual line selection a user can bypass the automatic line selection by pressing a
line key before going off-hook. The options: single key mode, preselection mode or subse-
quent line selection can be configured.
– In single key mode (KCSU; SGLBMOD= YES) the line is selected by pressing a line
key. The Keyset is switched to hands-free mode with on-hook handset.
– In preselection mode (KCSU; SGLBMOD=NO) the line key is pressed in idle state
and the required line is preselected as soon as the user goes off-hook, presses either
the loudspeaker, name, DSS or number redial keys or enters dialing digits. The prese-
lection is valid for 10 seconds (configurable via AMO). If a line with ringing has been
configured, the calling party is displayed when the line key is pressed until the prese-
lection time expires. After preselection the incoming call can be received on the prese-
lected line by going off-hook.
– Subsequent line selection. The user lifts the handset and presses a line key to sub-
sequently choose or change the line to be used.
● Classes of service: Calls can be initiated using any line on any terminal. Depending on
the system configuration, the line COS or the COS of the Keyset is used (AMO ZAND,
COSLNBAS parameter). There are, however, features which always use the COS as-
signed to the used terminal or the used line.
● Display: During the call, and after answering a call, the display of the called party normally
displays <Station number and name > of the primary line of the calling station or the used
line, depending on the system configuration (AMO ZAND, DISLNBAS parameter). The key
also affects the display of the calling party after the B party answers.
● General and exclusive hold. Hold allows a user to hold a connection and then to go on-
hook or to initiate or answer a call on a different line without losing the held connection.
Only two-party calls can be held. Holding of consultation calls is not possible.
– If general hold is set, the held connection can be picked up by all Keysets where
the respective line is assigned (the LED flashes slowly on those stations) by
pressing the line key.
– If exclusive hold is set, the held connection can only be resumed by the Keyset which
put the line on hold (the LED flashes slowly only on this station) by pressing the line
key.
There are three ways to put a line on hold: by pressing either the "Hold" or "Exclusive hold" keys
or by selection from the dialog menu. Changing to another line or pressing the line key of the
current line also puts a line on hold (or releases it, depending on the system configuration, AMO
ZAND, HDNOACKY parameter).
226
EN4402EN00EN_0003
© 2004 Siemens AG
If exclusive hold is set, the Keyset which put the line on hold receives a recall with priority, if the
held line is not resumed after the timeout. If general hold is set, a recall is signalled at all Key-
sets where the line is assigned.
● Multiple consultation. A user with several assigned lines can initiate a three-party confer-
ence by pressing the line key of the line he wishes to override. A three-party conference is
established, if a two-party call (A-B) is active on the selected line and no private call has
been initiated. Conference tone is injected at all three parties (A, B, C) if multiple consulta-
tion is activated. Only one station can enter into an existing connection.
● Private call. This feature protects the Keyset user against multiple consultation by another
Keyset user. Automatic and manual private calls are possible. Automatic private call (con-
figured using AMO KCSU, APRIVAT=YES) is activated as soon as a call is initiated. Key-
sets without the automatic private call feature are protected for one connection by activat-
ing the feature manually.
● Display of seized line. The line currently seized or selected by the Keyset is displayed, as
soon as the handset is lifted. Automatic display of the currently seized line is activated as
soon as a line is selected. The currently used line can be queried manually in various
states via the function key "I-USE" or selection of the menu "Show seized line?" in the ser-
vice menu.
● Idle The user can deactivate ringing at the Keyset by pressing the "Idle" key or selecting
"Switch off ringing?" in the service menu. The LED of the corresponding function key is "on"
if this feature is activated. Incoming calls are only signalled optically by the flashing LED
on the line key(s). All incoming calls are signalled at their required destination, but only
visually (LED, display). They can be answered as usual. Some call types override Idle, e.g.
exclusive calls, ACD.
33.1.2 Effect on Other Features

The key system functionality also affects pre-version 3.0 features. They are:
● Dialing aids such as speed dialing, name, DSS or number redial keys are station specific.
They can be used with any line assigned to a Keyset. The LED of the DSS key shows the
state of the entered destination line.
● Call forwarding: Every terminal can forward all assigned lines.(this is done on an in-
dividual line basis) The LED of the forwarding key always signals the state of the pri-
mary line of the respective terminal. Forwarding of secondary lines is not signalled.
● Do not disturb: If DND is activated for a line none of the Keysets where this line is
assigned receive any calls. Select "Idle" for protection against incoming calls on
Keysets instead of DND.
227
EN4402EN00EN_0003
© 2004 Siemens AG
● Callback: If a Keyset uses a line and enters a callback request, the primary line is dis-
played as callback source. As soon as callback is possible, the primary line is called exclu-
sively. After the callback source answers, the callback destination is called non-exclusively,
i.e., every Keyset where this line is assigned can answer the call.
● Mailbox. Entries can be left in the mailbox of the Keyset where the used line is as-
signed as primary line. Browsing in the mailbox and initiation of callbacks is only
possible on this Keyset,
● Call waiting is executed on seized lines. The display of the Keyset using this particular line
shows the appropriate message and the call pickup LED flashes. Automatic call waiting is
also executed on the Keyset using this particular line, if call waiting is allowed.
● Override is executed on seized lines. The Keyset using this particular line is overridden,
the corresponding message is displayed and the call pickup LED flashes.
● Paging. Every line can be routed for paging purposes and the user can answer a paging
call on any line. The paging key is always assigned to the seized line.
● Call pickup group. Calls within a call pickup group are only signalled (display, LED and
alerting tone) on the Keyset where the particular line is assigned as primary line. Calls sig-
nalled on this Keyset can be picked up using any assigned line.
● Group call. Parallel signalling is executed at specially marked stations within the call pick-
up group. On Keysets group call is exclusive, which means that the call is not signalled on
secondary lines and can also not be answered by other Keysets. This exclusive call can be
deactivated using "Idle".
● Direct call pickup can be activated by seizing any line.
● Call parking: A user can transfer the other party into the park queue of the call pick-
up group where the primary line is assigned, regardless which line was seized.
Parked calls can be picked up by Keysets within the call pickup group by seizing any
assigned line.
● Hunting group: Similar to terminals, lines can be combined to form hunting groups. Calls
in the hunting group are signalled on all Keysets where this line is assigned. The hunting
group key always remains assigned to the primary line of the respective terminal.
● Voice calling. The called terminal is directly switched to hands-free mode, if the called par-
ty has not activated "Stop voice calling". In the case of Keysets, voice calling is executed
on the terminal where the selected line is assigned as primary line. If this particular Keyset
is busy, a normal call is signalled instead.
● Timed reminder service. This feature is terminal-specific. It is only signalled on the termi-
nal of the respective user, provided call forwarding has not been activated. A timed remind-
er service call is exclusive.
228
EN4402EN00EN_0003
© 2004 Siemens AG
● COS changeover can be executed by any assigned line and switches between COS1 and
COS2 on the used terminal.
● Identification (PIN manual / ID card). PIN activation/deactivation can be performed
via any assigned line on the used terminal. The PIN is only valid for outgoing con-
nections established from this terminal regardless of which assigned line is used.
The COS (COS1) and data (e.g. name and station number) of the station for which
the PIN is assigned is used. The PIN does not affect other keysets using the line of
a terminal with activated PIN.
● The Call log is assigned to the primary line. Only incoming calls for the primary line
are entered. Outgoing calls are entered in the log of the primary line, regardless of
the actual seized line.
● Call charge recording can be executed either per terminal or per line (see "Call charge
recording").
33.1.3 Service Information

● The feature can only be used with Optiset E
● All Keysets where a line is assigned must be located in the same PBX. Network-wide Multi-
line access is not possible.
● Relations to other features:
– secretary system
Keysystem and secretary system are mutually exclusive. It is not even possible to up-
grade a station intended as secretary to a Keyset using SBCSU AMO (SECR=YES).
– Autoset Relocate:
optiset E with Keysystem functionality can move using Autoset Relocate. Optiset E ter-
minals (with or without Keysystem functions) can then log on at the previous port. To log
on an optiset E with Keysystem functions, a simple optiset E connection which has been
prepared accordingly suffices.
● New hardware is not required.
● The feature need not be released using AMO FEASU.
The maximum number of configured Keysets is limited by the PFS codeword (AMO
CODEW) and the existing Flexama memory capacity (AMO DIMSU).
● Keysystem functionality can be used in all countries.
229
EN4402EN00EN_0003
© 2004 Siemens AG
33.1.4 Keysystem Flowchart
CODEW DIMSU
COUNTS KEYSYS CC2 KEYSYS
ZAND
CTIME
ALLDATA DISPMODE;
CP CTHLDREC
KEYSYSTEM COSLNBAS
DTIM1 ACTDA DISLNBAS
DIGITE CTPRESEL STN RCUTOFF HOLDACKY
HDNOACKY
TAPRO For Optiset

WABE
STD 19 ENTRY KEY NUMBER REDIAL
DAR HOLDKY
20 ENTRY KEY CONSULTATION KEY
EXHOLDKY
21 BASIC KEY
PRIVKY
22 BASIC KEY OFFICE
IUSEKEY
23 BASIC KEY MAIL
RCTOFFKY
24 BASIC KEY STD
TRNSKY
25 ADVANCED KEY 5L
RLSKY
26 ADVANCED KEY ADDON 1
TOGGLEKEY
27 ADVANCED KEY ADDON 2
CONSKY
28 BASIC KEY AGENT
CBKKY
29 BASIC KEY SUPERVISOR
APRIV
30 ADVANCED KEY AGENT
DPRIV
31 ADVANCED KEY SUPERVISOR
r
Phantom station
SBCSU SBCSU
STD 19&&31 STD 19&&31
SECR NO SECR NO
INS YES INS SIGNOFF
230
EN4402EN00EN_0003
© 2004 Siemens AG
KCSU
PRIM PRIMKEY
RIOP
ORLNPF KCSU
TMLNPF SEC KYNO
SGLBMOD STNOSEC
BUSYRING RIOP
APRIVAT OFFTYPE
AICS
OFFTYPE
Own Line Partner-Line

or
oder
Phantom line
231
EN4402EN00EN_0003
© 2004 Siemens AG
33.2 AMO Commands

Configuration of a Keyset:
1. Check the permitted number of marketable Keyset units:
DISPLAY-CODEW:TYPE=COUNTS;
Line KEY 300, column FREE should display a value > 0 - if not, a new PFS code is re-
quired.
2. Configure or define appropriate standard key layout for Keysets (standard key lay-
outs with line keys):
DIS-TAPRO:TYPE=STD,DIGTYP=OPTISET,STD=19&&31;
(the new standard key layouts 19,..,31 were introduced for the Keysets)
Change the existing standard key layout, if there are no LINE keys:
CHA-TAPRO:TYPE=STD,DIGTYP=OPTIT12,STD=26,
KY01=LINE,KY02=LINE,KY03=LINE,
KY04=IUSE,KY05=HOLD,KY06=EXCLHOLD,
KY07=PRIVAT,...,KY12=RCUTOFF;
The new Keyset-specific standard key layouts have the following effects:
(only on optiset E which have been reconfigured to Keysets!!):
Max. number
Key function Description per
Keyset
LINE Line key 29
IUSE Key to identify the own used line key amongst several ac- 1
tive line keys.
HOLD Key to put a call on hold. Every other Keyset can pickup 1
the held call.
EXCLHOLD Key to put a call on exclusive hold. No other Keyset, ex- 1
cept the Keyset which put the call on hold, can pickup the
call.
PRIVAT Key to prevent other Keysets from overriding a connection 1
(conference) or to remove overriding Keysets from the
connection.
RCUTOFF Key to activate or deactivate the ringing tone for all line 1
keys.
232
EN4402EN00EN_0003
© 2004 Siemens AG
3. Configure optiset E with standard Keyset key layout:

a) If the optiset E is configured, assign standard Keyset key layout:
CHA-TAPRO:STNO=4711,STD=26;
b) If the optiset E has not yet been configured:
ADD-SBCSU:STNO=4711,OPT=<OPTI/OPTIEXP>,DVCFIG=OPTISET,..., STD=26;
4. Check Flexama memory for Keyset:
DIS-DIMSU:TYPE=CC,CCTLOPT=KEYSYS;
Expand insufficient memory:
ADD-DIMSU:TYPE=CC2,KEYSYS=<sufficient_size>;
5. Configure optisets as Keysets and assign primary lines:
The first step is to upgrade all optisets to Keysets using AMO KCSU (TYPE=PRIM). The
own station number (primary line) must be assigned to a line key.
The used parameters have the following effect:
Parameter Description Standard value

(TYPE=PRIM)
STNO Station number of the optiset to be upgraded to a Key- STNO must be
set. specified
PRIMKEY Key number of the primary line: Key number of the
1 - 12 (terminal) first free LINE key
13 - 28 (ADD_ON 1 - if configured)
RIOP Ringing option, i.e. signalling type of incoming calls YES
on the primary line:
YES- by ring tone + LED + display
NO - only by LED (+ display depending on the TML-
NPF setting)
ORLNPF Preferences for outgoing connections: PRIME
NONE - no preference
IDLE - any free line
(the primary line is preferred)
LAST - last used line
PRIME - primary line
233
EN4402EN00EN_0003
© 2004 Siemens AG

(TYPE=PRIM)
TMLNPF Preferences for incoming connections: RING
NONE - no preference
ALER - any incoming line
(signalling by ring tone or LED)
ALERP - like ALER,
but the primary line is preferred
RING - calling line
RINGP - like RING,
but the primary line is preferred
SGLBMOD Single-key mode: YES
YES - pressing a line key not only selects but also
seizes the line
NO - pressing a line key only preselects the line.
The line is only seized when the handset is
lifted.
BUSYRING Signalling of a second incoming call (on a line config- NORING
ured with RIOP=YES) if the terminal is in call state:
ALERT - by LED + alerting tone
NORING - only by LED
APRIVAT Automatic private call: NO
YES - other Keysets cannot override the connection
(a configured PRIVATE key is automatically
activated when a connection is established)
NO - other Keysets can override a connection
(conference)
(a configured PRIVATE key is not
activated when a connection is established
AICS Automatic answering on the primary line with head- YES
set:
YES - incoming calls are automatically answered
NO - incoming calls must be answered manually
OFFTYPE Type of station blocking during modification using DC
TYPE=PRIM:
NO - no blocking
DC - with pre-blocking
DI - without pre-blocking
234
EN4402EN00EN_0003
© 2004 Siemens AG
Example: configuration of a Keyset. The primary line is assigned to the first LINE key. In-
coming calls are signalled on this line by ringing tone. Other Keysets cannot override es-
tablished connections:
ADD-KCSU:STNO=4711,TYPE=PRIM,RIOP=YES,APRIVAT=YES;
If the primary line is not to be assigned to the first available LINE key, the PRIMKEY pa-
rameter must be specified (e.g. PRIMKEY=13, if the primary line is to be assigned to the
first LINE key of the automatic dialer. This is only possible, if the automatic dialer has been
configured and the 13th key is a LINE key).
6. Configure secondary lines of the Keyset:
The second step is to assign the remaining line keys with the station numbers of other Key-
sets (secondary lines) using AMO KCSU (TYPE=SEC).
The used parameters have the following effect:

(TYPE=SEC)
STNO Station number of the Keysets for which the second- STNO must be
ary line is to be configured specified
KYNO Key number of the secondary line: KYNO must be
1 - 12 (terminal) specified
RIOP Ringing option, i.e. signalling type of incoming calls on NO
the secondary line:
YES - by ring tone + LED + display
NO - only by LED
(+ display only if the TMLNPF is not set to RING or
RINGP)
STNOSEC Station number of the secondary line STNOSEC must
be specified
AICS Automatic answering on the secondary line with head- NO
set:
YES- incoming calls are automatically answered
NO - incoming calls must be answered manually
235
EN4402EN00EN_0003
© 2004 Siemens AG

(TYPE=SEC)
OFFTYPE Type of station blocking during modification using DC
TYPE=SEC:
NO - no blocking
DC - with pre-blocking
DI - without pre-blocking
Example: seizure of the 2nd. and 3rd. LINE key. Incoming calls are signalled on the 2nd.
LINE key only visually (by the corresponding LED):
ADD-KCSU:STNO=4711,TYPE=SEC,KYNO=2,STNOSEC=4712;
ADD-KCSU:STNO=4711,TYPE=SEC,KYNO=3,STNOSEC=4713,RIOP=YES;
7. Modify system-wide Keyset settings:
Query Keyset-specific settings:
DIS-ZAND:TYPE=KEYSYS;
The displayed parameters have the following effect:
Parameter Description DB initializa-

(TYPE=KEYSYS) tion
COSLNBAS Check of the COS assigned to the used line: NO
YES - the COS assigned to a line are valid for the
A party
NO - The COS assigned to the primary line are
valid for the A party
DISLNBAS Station number/name display assigned to the seized NO
line:
YES - The user data of the other party assigned to the
seized line are displayed
NO - The user data of the other party assigned to
the primary line are displayed
HOLDACKY A call is put on hold by pressing the corresponding line YES
key:
YES - the current connection is put on hold by press-
ing
the assigned active line key
NO - the current connection is terminated by
pressing the assigned active line key
236
EN4402EN00EN_0003
© 2004 Siemens AG
Parameter Description DB initializa-

(TYPE=KEYSYS) tion
HDNOACKY A call is put on hold by pressing another line key: YES
YES - the current connection is put on hold by press-
ing another line key
NO - the current connection is terminated by
pressing another line key
Example: change the system settings so that active connections are put on hold and not
released:
CHA-ZAND:TYPE=KEYSYS,HOLDACKY=YES,HDNOACKY=YES;
Comment: The parameter values for COSLNBAS and DISLNBAS should be the same!
If a Keyset is to be rechanged to an optiset, carry out the following steps:
8. Delete all secondary lines of the Keysets:
First, delete all line keys to other Keysets:
DEL-KCSU:STNO=4711,TYPE=SEC [,KYNO=2&3&...];
If the KYNO parameter is not specified, all secondary lines are deleted.
9. Delete the primary line of the Keyset and reconfigure the Keyset into an optiset:
The primary line is then deleted (the line keys of other Keysets which have a secondary
line to the Keyset which will be deleted, are corrected). Now the Keyset becomes a normal
optiset:
DEL-KCSU:STNO=4711,TYPE=PRIM;
The command
DEL-KCSU:STNO=4711;
has the same effect as the two previous individual commands!
10. Assign the non-Keyset key layout to the optiset E:
The Keyset-specific keys can no longer be used. Assign a standard key layout designed
for optisets without Keyset functions (in this example 4) to the terminal:
CHA-TAPRO:STNO=4711,STD=4;
237
EN4402EN00EN_0003
© 2004 Siemens AG
33.3 Overview AMO Modifications

Language
ACTDA RCUTOFF d Ringer Cutoff
ACTDA RCUTOFF e Ringer Cutoff
CTIME KDHLDREC d Kontroll-Timer fuer Dauer des manuellen
Gespraechshaltens
CTIME CTHLDREC e timer to control the duration of a manual hold of a call
DIMSU KEYSYS d Maximale Anzahl der Keysysteme
DIMSU KEYSYS e Maximum number of Key Systems
DTIM1 KDPRESEL d Kontrollzeitglied zur manuellen Vorauswahl einer Lei-
tung
CTPRESEL e Control timer for manual preselection of a line
KCSU ----------- d Neuer AMO, siehe Abschnitt 33.2
KCSU ----------- e New AMO, see Chapter 33
TAPRO TDxx = d Tastenfunktion fuer die Taste Nummer xx:
LEITUNG Leitungstaste
HALTEN Halten
EXHALTEN Exclusives Halten
PRIVAT Privatgespraech
ANZLEIT RU- Anzeigen meiner benutzten Leitungstaste
FAUS Rufabschaltung der Leitungstasten
TAPRO KYxx = e Key function to be assigned to key number xx:
LINE Line Key

HOLD Hold
EXCLHOLD Exclusive Hold
PRIVACY Privacy
IUSE Display actual used line
RCUTOFF Ringer Cutoff
238
EN4402EN00EN_0003
© 2004 Siemens AG

Language
WABE KZP = d Kennzahlpunkt für:
HALTETA Haltetaste
EXHALTTA Exclusiv Haltetaste
PRIVTA Privatgesprächtaste
ANZLEITA meine-benutzte-leitungstaste-anzeigen-Taste
RUFAUSTA Rufabschaltungstaste
UEGTA Uebergabetaste
TRTA Trenntaste
MATA Makeltaste
RFTA Rueckfragetaste
RRTA Rueckruftaste
WAWILTA Wahlwiederholungstaste (letzte Rufnummer)
WAWITA Wahlwiederholungstaste (gespeicherte Nummer)
PRIVE Privatgespraech einschalten

PRIVA Privatgespraech ausschalten
WABE DAR = e Digit analysis result for:
HOLDKY Hold Key

EXHOLDKY Exclusive Hold Key
PRIVKY Privacy Key
IUSEKY I-use Key
RCTOFFKY Ringer Cutoff Key
TRNSKY RL- Call Transfer Key
SKY Cancel Key
TOGGLEKY Toggle Key
CONSKY Consultation Key
CBKKY Call Back Key
LNRKY Last Number Redial Key
SNRKY Saved Number Redial Key
APRIV Privacy on
DPRIV Privacy off
ZAND TYP= d zur Auswahl des Zweiges mit den Einstellungen für
KEYSYS Key Systeme
COSLNBAS d COS der aktiven Line verwenden anstatt der des zu-
geordneten Gerätes.
ANZLNBAS d Rufnummer und Name der aktiven Line anzeigen an-
statt die des zugeordneten Gerätes.
239
EN4402EN00EN_0003
© 2004 Siemens AG

Language
HALTAKT d Gespräch wird in Haltezustand gebracht durch
Drücken derselben Leitungstaste
HALTNAKT d Aktuelles Gespräch wird in Haltezustand gebracht
durch Drücken einer anderen Leitungstaste
ZAND TYPE = e
KEYSYS to select the branch for settings for Key Systems
COSLNBAS e Use COS belonging to the line appearance instead of
COS belonging to the device hosting the line
appearance.
DISLNBAS e Display station number and subcriber name belong-
ing to the line appearance instead of those
belonging to the device hosting the line appearance.
HOLDACKY e Put active call into hold when pressing the line key
corresponding to the active call.
HDNOACKY e Put active call into hold when pressing the another
line key not corresponding to the active call
240
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Pickup
34 Pickup
34.1 Local Call Pickup Groups
*7
*7 *7
*7
*7
34.1.1 General
Stations in a Hicom node who can pick up each other’s incoming calls are combined to a local
call pickup group (PU group). The calls are picked up by either pressing a key or by dialing a
code (PU) configured system wide.
PU groups are configured using AMO AUN. A PU group consists of analog or digital terminals
within the own Hicom node. If network-wide call pickup is configured, such a PU group can be
linked to a PU group in a remote Hicom node (via so-called "remote links").
241
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Pickup Siemens
● Group-specific attributes:
The display of the calling party (DISTNO) and the alerting tone after timeout (NOTRNG)
can be set per PU group.
To pick up waiting calls the parameter PUSECOND=YES must be set. The way incoming
calls are signaled at the terminals of a group can be set using the SIGNAL parameter.
● Terminal-specific attributes:
The COS GRPCAL in COSSU AMO defines if a terminal is to participate in a group call
(see Abschnitt 34.1.2), i.e. if an incoming call is signalled acoustically (instead of by LED
or display). This feature is also called "Parallel call". It is possible for PU groups both locally
and network wide.
● Restrictions:
The maximum number of participants (terminals + remote links) in a PU group is 255.
Up to 255 Digites may be configured per group. However, if more than 25 Digites are con-
figured, full signaling (SIGNAL=ALL) is no longer recommended. In this case, AMO AUN
sets SIGNAL=LED or, with more than 75 Digits SIGNAL=NONE as default. This setting can
be modified for individual cases.
Up to 1000 PU groups can be configured. The current value is set and displayed (PUGR)
using AMO DIMSU. A group number specified in AMO AUN during configuration must be
smaller than the PUGR value.
A terminal can belong to only one PU group.
Terminals in a PU group may not be MASTER in a hunting group (HG).
The terminals in a PU group may not be the analog side of a modem.
The terminals in a PU group may not be used for witness (listener) interface.
Any special terminals configured using AMO SSCSU may not be members of a PU group.
Any terminals configured as executive or secretary in a secretary system may not be en-
tered in a PU group.
A PU group must consist of at least one terminal. Groups with only one remote link are
therefore not allowed.
The alerting tone (NOTRNG) only applies for digital terminals (digi 211, digi 260, set 500,
set 700 and Optiset. The set 400 is treated separately).
● Moving of terminals from one PU group to another
It is possible, from Hicom 300 E V3.0 with the software release x, to move terminals or re-
mote links from one PU group to another specified PU group. The original group number
need not be specified as it is derived by AMO AUN. You need only specify the terminal(s)
(or 1 remote link) and, if necessary, the destination group where the terminal(s) are to be
242
EN4402EN00EN_0003
© 2004 Siemens AG
moved. It is also possible to move a range of terminals. AMO AUN selects the terminals
from the corresponding groups and collects them in the destination group. If the destination
group is not specified, AMO AUN will create the next free group.
● Selection of PU groups during configuration/expansion using AMO AUN
It is possible, from Hicom 300 E V3.0 with software release x, to mark a PU group by spec-
ifying a station number of one the PU group members. For this purpose the GRSTNO pa-
rameter was implemented.
– if neither the GRNO parameter nor the GRSTNO parameter are specified in the ADD-
AUN command: The AMO creates the next free PU group in ascending order (e.g.
group 1, 2, 3, 10 exist: group 4 is newly created).
– only the GRNO parameter is specified and not GRSTNO in ADD-AUN: The AMO ex-
pands the PU group marked by the GRNO parameter.
– only the GRSTNO parameter is specified and not GRNO in ADD-AUN: The AMO ex-
pands the PU group where the terminal specified by the GRSTNO parameter is a
member.
– both parameters (GRNO and GRSTNO) are specified in ADD-AUN: Not allowed. The
command is rejected with an error message.
● Deletion of terminals from different PU groups
It is possible, from Hicom 300 E V3.0 with software release x, to omit the group number
(GRNO) in the DEL-AUN command. In this case, the AMO will find out to which group the
terminal belongs. This makes it possible to delete several terminals, even if they are mem-
bers in different PU groups.
● Modification of PU group attributes
From Hicom 300 E V3.0 with software release 1, modification of the PU group attributes
(as well as the remote link attributes) using the CHANGE command of AMO AUN is pos-
sible. In older variants this was performed using the ADD command.
● Type branching with display /regenerate in AMO AUN
From Hicom 300 E V3.0 with software release 1 type branching with the DISPLAY and RE-
GENERATE command is optional. You can enter e.g.
- DISP-AUN instead of ---> DISP-AUN:TYPE=SYS;
- DISP-AUN:STNO=2100 instead of---> DISP-AUN:TYPE=STN,STNO=2100;
243
EN4402EN00EN_0003
© 2004 Siemens AG
34.1.2 PU Group Call

This feature is available without a patch from Hicom 300E V2.0 rel 7 (WP 3).
From Hicom 300 E

V2.0, the group call is
Group call on analog implemented in the
terminals via a/b adapt- AUN.
er is available from ver-
sion V2.08
If a terminal (Anate or Digite) is called, other terminals belonging to the same group (provided
they can be seized) can be acoustically called (parallel call). All terminals which are called in
parallel are assigned the same call type (normal, trunk or special ringing) and, for Digits, the
same display information.
The call is assigned to the group member who goes off-hook first or who accepts the call by
pressing the AUN key or dialing the PU code.
● All terminals which are to be called in parallel must be members of the same PU group
and be specially marked by AMO (be in the appropriate Class of Service COS).
● All Digite in the PU group not marked for parallel call are assigned the usual PU group
signaling (display, LED and alerting tone).
● If the flag for parallel call is not set in the alternative COS the user can switch between
the attributes "parallel call for terminal" and "only PU signaling for terminal" using the
COS changeover. (this may affect other features e.g. data security)
244
EN4402EN00EN_0003
© 2004 Siemens AG
● If parallel call is activated, the COS for pickup/accepting a call is not checked. When
configuring a group, make sure that all terminals are assigned the appropriate COS. If
not, answering a parallel call would receive a negative acknowledgment.
● Group call is implemented for Anate, Digite, Set400,500,700 and Optiset but not for
functional terminals. From Hicom 300 E V2.0 with software release 8, group call is also
allowed for Anates connected to Optiset via Terminal a/b adapter.
● The maximum number of groups which can be configured for group call corresponds
to the maximum number of PU groups:
1000!
● The maximum number of terminals which can be called in parallel in a group is 255 (as
with PU groups). Note: only one ring generator is available per shelf. If more than 10
Anates are to be supplied by the same ring generator the tone could be less audible.
● The parallel call to the group is only performed after the initial call. If a terminal be-
comes free the remaining calls cannot "move up" as no check for further calls is exe-
cuted.
34.1.3 AMO Batch

● Release the feature:
CHA-FEASU:TYPE=A,CM=PU;
● Set the number of possible PU groups using the PUGR parameter in AMO DIMSU. This
value corresponds to the maximum group number.
ADD-DIMSU:PUGR=number;
● Set the PU code:
ADD-WABE:CD=key-num,DAR=PU;
● Configure the PU group:
1. use default values:
ADD-AUN:STNO=number;
2. do not use default values:
ADD-AUN:STNO=number[,DISTNO=YES][,NOTRNG=
PERIOD1][,PUSECOND=YES][,SIGNAL=LED];
3. the PU group number is defined by the user:
ADD-AUN:GRNO=21,STNO=number;
4. move terminals from various PU groups to a new PU group:
(number1, number2, number3 are members of different PU groups):
ADD-AUN:STNO=number1&number2&number3;
245
EN4402EN00EN_0003
© 2004 Siemens AG
● Expand the PU group:

1. the existing PU group is defined by the group number:
ADD-AUN:GRNO=1,STNO=number;
2. the existing PU group is defined by a group member:
ADD-AUN:GRSTNO=number,STNO=number;
● Modify the group-specific parameters of an existing PU group:
CHA-AUN:TYPE=GR,GRNO=1,{[,DISTNO=YES][,NOTRNG=ONIDLE1][,PUSEC-
OND=YES][,SIGNAL=NONE]};
The set 400 must be handled With regard to the alerting tone and the time this tone
is injected, the set 400 must be treated separate from all other DIGITEs.
Set the single or triple alerting tone for the set 400 using the AMO SCSU, parameter
ALERT (with ADD or CHANGE).
ADD-SCSU:STNO=number,....,ALERT=3;
CHA-SCSU:STNO=number,ALERT=3;
● The setting of the alerting tone is for the set 400, set 500 and set 700 is only accepted after
a terminal restart.
ACT-TAPRO:STNO=number;
● The NOTRNG parameter defines, whether or not the alerting tone is injected: (default:
ON3 = multiple alerting tone in all states)
CHA-AUN:TYPE=GR,GRNO=number,NOTRNG=param;
● For PU and CHESE, the time until the alerting tone is injected is set using AMO DTIM1,
TYPE=DIGITE, parameter BURST (default: 15 sec.).
CHA-DTIM1:TYPEDH=DIGITE,BURST=sec;
For a set 400, the display delete time is used for this function. Set this time using the
DISDEL parameter. It is then activated by downloading.
CHA-DTIM1:TYPEDH=DIGITE,DISDEL=sec; (1 to 254 seconds, default=5)
● Set the time interval for the cyclic alerting tone (NOTRNG=PERIOD1,PERIOD3):
CHA-CTIME:TYPESWU=CPTIME,NOTRNG=sec; (5 to 30 Seconds, Standard=5)
● Define the parallel call for the PU member using the following AMO:
CHA-COSSU: TYPE=COS, COS=number, AVCE=GRPCAL;
34.1.4 Further Comments
With CHANGE and DELETE of PU groups the "Call pickup" feature is no longer
blocked. This prevents any waiting time.
246
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: CHESE - Executive/Secretary Arrangements (Integrated Ar-
35 CHESE - Executive/Secretary Arrangements

(Integrated Arrangements)
The integrated executive/secretary arrangement is a special group configuration of system sta-
tions as executive, secretary stations and maybe some more representative stations. In one in-
tegrated arrangement are four executive, two secretary and for each secretary two more sta-
tions allowed. Only digital terminals e.g. Optiset E can be users of an integrated arrangement.
Executive and secretary stations must not be configured as "DIGITE with no display" (*1).
Every integrated arrangement has a special group code, which can be 1 to 1000. The level will
be fixed by AMO DIMSU.
Each executive and secretary station can only belong to one group. The stations with represen-
tative function can belong to more than one group. Secretary stations can also be used as rep-
resentative stations. Secretary stations can also belong to one group without relation to an ex-
ecutive.
Secretary stations have to be signed as such by AMO SBCSU (SECR = Y).
Executive and secretary stations have to have special function key:
● Executive station
– PU (call pickup) key for each executive
– DSS (direct station select) key for the secretary
– (and possibly for representative stations)
● Secretary station
– PU key for each executive
– DSS key for each executive
– RNGXFER key (deactivation of secretarial intercept)
– REP (secretarial transfer) key for each executive
In the database there are some standard key functions for executive and secretary stations for
different terminals specified. With AMO SBCSU these function keys are configured for the ter-
minals.
The standard function keys can be changed with AMO TAPRO and also can some new function
keys be created.
The special function keys for integrated arrangements can not be programmed by the termi-
nals.
247
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: CHESE - Executive/Secretary Arrangements (Integrated Ar- Siemens
Tone Ringing
The Hicom terminal (DIGITE) usually has a single tone ringing (one frequency). Ring discrimi-
nation for calls between the executive and the secretary is implemented by means of special
ring cadences which are administrable. (parameter MULTN)
Delayed Notification Ringing

Where calls are signalled simultaneously e.g. to executive and secretary, an acoustic notifica-
tion is normally applied after a predetermined (AMO parameter) delay. The notification to be
applied can be a single or multiple burst, the burst being applied either only when the station is
in the idle state, in all states, or not at all.
Additional Features
Additional special features are created by means of other AMOs:
● An executive station has a secrete directcall
phonenumber. Calls on these second number, will not be transferred to the secretary sta-
tion. This is managed by AMO SA with a code, which is the same as the secrete phone-
number.
● Secondary stations are possible. AMO AUN defines these secondary telephones for exec-
utive and secretary stations.
● Call Forwarding (FWD) and Ring No Answer (RNA): The call is routed to a Voice Mailbox
specified by AMO CHESE. Possible values are:
– NONE: The call for the appropriate executive is not routed for FWD and RNA to any
mailbox.
– EXEC: The call for the appropriate executive is routed for FWD and RNA into the ex-
ecutive’s mailbox.
– SECR: The call for the appropriate executive is routed for FWD and RNA into the sec-
retary’s mailbox.
The setting is assigned to a specific executive and becomes effective if
– the intercept key is not activated (executive is not intercept destination) and
– the Voice Mailbox is activated as FWD/RNA-destination for the executive
An activated deputy secretary does not affect this feature. An activated FWD-All-Calls is
given preference.
248
EN4402EN00EN_0003
© 2004 Siemens AG
35.1 ADD-CHESE
This function allows to create a complete integrated arrangement consisting 1 to four executive,
two secretary and two more stations with representative function.
The sequence of executive and secretary station phonenumbers and the parameter ALLOC fix-
es the relations between executive and secretary stations.
For all station numbers (executive, secretary, representative) dummy numbers (000000) may
be entered. The meaning of these numbers is to reserve space, i.e. the affected spot in the in-
tegrated arrangement remains free. So any configuration can be generated by one ADD com-
mand.
The sequence of the numbers of representative stations is important to find the relations to the
first and second secretary phonenumbers. If it is necessary to give the second secretary a rep-
resentative station, then one must enter a dummy-number (000000) for the first representative
station.
It is rejected, if a number of a hunting group master is entered as executive or representative
station number.
Radio connected stations (CMI, AMO SBCSU)) and special subcsribers configured by AMO
SSCSU, are rejected as members of executive/secretary arrangements.
Keyset subscibers are rejected as executive or secretary but allowed as representative.
Subscribers with "Automatic Call Distribution" attribute AGENT are rejected as executive. Sub-
scribers with at least one of the ACD attributes AGENT, SUPER, AUTOLOG or CAF are reject-
ed as secretary.
The parameters MBOX1 to MBOX4 are correlated to the executive station numbers defined in
parameter EXEC.
Example
Create an integrated executive/secretary arrangement belonging to groupnumber 20 and with
two executives, two secretaries, and with multi-tone ringing. Each executive is assigned to a
separate secretary. Secretary 2 is assigned a deputy secretary. The executives are added as
executive 1 and executive 3.
Input:
ADD-CHESE:GRNO=20,EXEC=4700&000000&4710,SECR=4705&4715,ALLOC=E1S1&E3S2
,MULTN=Y,REP=000000&6115,MBOX1=SECR,MBOX3=NONE;
It is not necessary to specify MBOX3 in this example because NONE is the default value.
249
EN4402EN00EN_0003
© 2004 Siemens AG
35.2 CHANGE-CHESE
The following changes are possible:
1. Add station (executive, secretary, deputy secretary), or change the allocation/assignment
of secretaries to executives
2. Executive number
3. Secretary number
4. Multi-tone ringing
5. Notification burst after preset delay
6. Voice Mailbox
Depending on the requirements, case 1 above results in the following actions being necessary:
Secretary already entered in the Secretary not yet entered in the

executive/secretary arrangement executive secretary arrangement
Executive al- 1. Executive is not yet assigned to the Enter secretary
ready entered in secretary: Delete old allocation
the exec/secr delete old allocation Enter new allocation
system enter new allocation Possible error messages:
2. Executive is already assigned to Number of secretaries > 2
the secretary:
no change
Executive not Enter executive Enter executive
yet entered in Enter allocation Enter secretary
the exec/secr Possible error messages: Enter allocation
system Number of executives > 4 Possible error messages:
Number of executives > 4
Number of secretaries > 2
Executive not No change Enter secretary
specified in Possible error messages:
command Number of secretaries > 2
– When a deputy secretary is specified, old entries are overwritten only if the secretary
already entered is not active.
Changes in the hierarchical relationships are not permitted (e.g., an executive cannot
become a secretary).
– If one of the specified stations is already a member of another executive/ secretary ar-
rangements, the job is rejected (with the exception of deputy secretaries).
250
EN4402EN00EN_0003
© 2004 Siemens AG
– When stations are changed (OLD ---> NEW), the existing activations of the old station
(RNGXFER for executive or REP for secretary) are reset.
– As a NEWEXEC or Representative station number it is not allowed to enter a number
of a hunting group master.
– Radio connected stations (CMI, AMO SBCSU)) and special subcsribers configured by
AMO SSCSU, are rejected as EXEC, NEWEXEC, SECR, NEWSECR and REP.
– Keyset subscribers are rejected as EXEC, NEWEXEC, SECR, NEWSECR.
– Subscribers with "Automatic Call Distribution" attribute AGENT are rejected as EXEC
and NEWEXEC. Subscribers with at least one of the ACD attributes AGENT, SUPER,
AUTOLOG or CAF are rejected as SECR and NEWSECR.
Examples
Following integrated arrangement is configured:
+------------------------------------------------+
| GROUP NO. : 1 |
| MULTITONE RING : Y |
| NOTIFICATION RING : ON3 |
| |
| EXEC SECR REP MBOX |
| 3101 3103 3106 EXEC |
| 3110 3104 3103 NONE |
| |
+------------------------------------------------+
1. Executive 2 should also have secretary 1

Input:
CHANGE-CHESE:GRNO=1,TYPE=ADDSTN,EXEC=3110,SECR=3103;
Secretary 2 is after this change a second secretary:

+------------------------------------------------+
| GROUP NO. : 1 |
| |
| 3101 3103 3106 EXEC |
| 3110 NONE |
| 3104 3103 |
| |
+------------------------------------------------+
251
EN4402EN00EN_0003
© 2004 Siemens AG
2. Secretary 2 now is to be related to an executive

Input:
CHANGE-CHESE:GRNO=1,TYPE=ADDSTN,EXEC=3112,SECR=3104;
following picture is now to see:

+------------------------------------------------+
| GROUP NO. : 1 |
| |
| 3101 3103 3106 EXEC |
| 3110 NONE |
| 3112 3104 3103 NONE |
| |
+------------------------------------------------+
3. the secretary phonenumber 3103 will be changed into 3105

Because this number also is entered as representative for secretary 2, one has to create
two commands (the sequence is not important).
Input:
CHANGE-CHESE:GRNO=1,TYPE=SECR,OLDSECR=3103,NEWSECR=3105;
CHANGE-CHESE:GRNO=1,TYPE=ADDSTN,SECR=3104,REP=3105;
new configuration:
+------------------------------------------------+
| GROUP NO. : 1 |
| |
| 3101 3105 3106 EXEC |
| 3110 NONE |
| 3112 3104 3105 NONE |
| |
+------------------------------------------------+
4. For FWD/RNA, the executives 3101 and 3110 want to assign the mailboxes of their secre-
taries.
Input:
CHANGE-CHESE:GRNO=1,TYPE=EXECATTR,EXEC=3101,MBOX=SECR;
CHANGE-CHESE:GRNO=1,TYPE=EXECATTR,EXEC=3110,MBOX=SECR;
252
EN4402EN00EN_0003
© 2004 Siemens AG
new configuration:
+------------------------------------------------+
| GROUP NO. : 1 |
| |
| 3101 3105 3106 SECR |
| 3110 SECR |
| 3112 3104 3105 NONE |
| |
+------------------------------------------------+
35.3 DELETE-CHESE
The following options exist for cancellations:
1. all integrated executive/secretary arrangements in a system
2. one integrated executive/secretary arrangements or individual station
Parameter EXEC, AMO-Action

SECR or REP
none the whole group with GRNO will be deleted.
EXEC executive will be deleted.
SECR a secretary will be deleted, if no executive is in relation. A re-
lated representative secretary also will be deleted.
EXEC and SECR executive and secretary will be deleted, if the secretary is re-
lated only to one executive
A representative related to the secretary also will be deleted.
REP rep. secretary will be deleted in those groups,where entered
(max. two deletes possible).
REP and SECR or rep. secretary will be deleted, where related to SECR (or to
EXEC the secretary of EXEC)
● If there is more than the minimum configuration (one EXEC and one SECR) in a group de-
leted, the whole group will be cancelled.
● A message is output where an implicit deletion has occurred.
● A representative secretary will only be cancelled, if it is deactivated.
● When an executive or a secretary is cancelled, the existing activations are reset.
253
EN4402EN00EN_0003
© 2004 Siemens AG
● To cancel an integrated arrangement the users of an executive and the secretary stations
have to be locked and afterwards unlocked.
● Mailbox assignments cannot be deleted. This function can be performed by a CHANGE-
command with parameter MBOX=NONE.
Examples
following arrangement exists:
+------------------------------------------------+
| GROUP NO. : 1 |
| |
| 3101 3103 3106 EXEC |
| 3110 3104 3106 NONE |
| |
+------------------------------------------------+
1. The representative station has to be deleted.

Input:
DELETE-CHESE:TYPE=GR,GRNO=1,REP=3106;
2. The representative station of secretary 3104 has to be deleted.

Input:
DELETE-CHESE:TYPE=GR,GRNO=1,SECR=3104,REP=3106;
or
DELETE-CHESE:TYPE=GR,GRNO=1,EXEC=3110,REP=3106;
254
EN4402EN00EN_0003
© 2004 Siemens AG
35.4 DISPLAY-CHESE
1. Interrogate all integrated executive/secretary arrangements in a system
2. Interrogate one integrated executive/secretary arrangements
3. Interrogate individual stations to determine if they are members of an integrated executive/
secretary arrangements
Because a station can simultaneously be a member of one executive/secretary system (secre-
tary) and a representative secretary for another executive/secretary system, several different
types of output are possible for (3).
When the system is interrogated, only created executive/secretary arrangements are output,
i.e., negative acknowledgements are not output for executive/secretary systems that are not as-
signed. When individual stations are interrogated, all the data of the associated executive/sec-
retary arrangements is output.
Example
Interrogate the integrated executive/secretary arrangements having group number 1.
Input:
DISPLAY-CHESE:TYPE=GR,GRNO=1;
Output:
+------------------------------------------------+
| GROUP NO. : 1 |
| |
| 3101 3103 3104 EXEC |
| 3112 SECR |
| 3110 3104 3103 NONE |
| |
+------------------------------------------------+
255
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Hunting Groups Siemens
36 Hunting Groups
A hunting group incorporates several terminals which are required to be reached under a com-
mon call number. This number may be a code or the number of the first station of the HT group,
which is referred to as the MASTER station.
The following seizure types are possible:
● cyclic,
i.e. idle stations are seized one by one. Only after the last idle station has been seized does
hunting start over again.
● linear,
i.e. hunting is invariably started from the beginning of the defined sequence, with the first
free station.
Hunting groups can be formed for all service types, the hunting group code or MASTER station
number not being service-related. The services are selected using a separate code number.
A terminal can belong to several hunting groups. However, it cannot be MASTER of more than
one and cannot appear more than once in one and the same hunting group. For a voice hunting
group, an overflow to a call queuer can be established or a mailbox be added to the voice mail
server in case all stations of a hunting group are busy.
A hunting group member station can be reached separately under its number or randomly un-
der the hunting group code. The MASTER station can only be reached as a hunting group
member. It must always be the first station of a hunting group. Attendant terminals cannot be
integrated in a hunting group. They have to be accessed via the ATND group by dialling the DI-
DATND or ATND group codes.
By specifying the CPS in the SA AMO availability of the HT group can be restricted, e.g.: not
available for DID or consultation hold. The DPLN group must be specified if the hunting group
code has been added in the DPLN with a DPLN group branch.
Basically, a HUNT group can be reached under several code numbers, e.g.: *80 and by replac-
ing *, under 880.
The HUNT group must then be duplicated for each further code. This is very simple using the
ADD command and the DUPL (duplicate) type branch and specifying the existing and an addi-
tional code.
Changes made to such hunting groups apply to all code numbers.
● Enable the feature
(SAS = Service Voice)
SAF = " FAX
SAT = " TTX
SAB = " BTX
SAD = " DEE)
CHA-FEASU:TYPE=A,CM=HTVCE;
256
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Hunting Groups
● Assign a HUNT group DAR in the DPLN

AD-WABE:CD=key-num,DAR=HUNT;
Assign DAR for deactivation of hunt group member (VOICE service)
AD-WABE:CD=key-num,DAR=DHTVCE;
Assign DAR for re-activation of hunt group member (VOICE service)
AD-WABE:CD=key-num,DAR=AHTVCE;
● Assign a hunting group with linear device search (VOICE service)
AD-SA:TYPE=VCE,CD=number,TYPE=LIN,CQMAX=number;
● Assign a hunting group with cyclic device search
AD-SA:TYPE=VCE,CD=number,TYPE=CYC,CQMAX=number;
A maximum of 10 users can be added with one command. If a larger hunting group
is required, the following command can be used to expand to hunting group by a fur-
ther 10 users:
ADD-SA:TYPE=STN;
This applies to all services.
In addition, the parameter POS can be used to specify the position in the hunting
group at which the station is to be included.
For further information on the administration of hunting groups, please refer to the
SA AMO-description.
257
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Attendant Console Siemens
37 Attendant Console
37.1 Overview
The Hipath 4000 V1.0 attendant consoles may be of the type AC4 or the windows based con-
soles ACWin-4.x (DQ) and ACWinMQ-2.x (MQ). This document describes the configuration of
attendant consoles and associated attendant groups,

An attendant is given an individual number known as the personal number with the code
ATNDIND
Unlike user station terminals and trunk circuits, the Attendants are not yet ready for operation,
they invariably have to be assigned to an ATND group (VFGR).
This is done using the VFGR AMO. Since night options are also assigned to every attendant
terminal (at least one dummy option if night service is not provided), they have to be created
beforehand with the NAVAR AMO.
The following night options can be assigned with the AMO NAVAR:
NONE Dummy option
STN Night answer station
GENANS Universal night answer
CASEXT External Centralized ATND Service group
CASINT Internal Centralized ATND Service group
With the release of Hipath 4000 V1.0 Night attendants are not supported any more.
The VFGR AMO is used to allocate all the relevant ATNDs as well as night options to the ATND
group to be set up.
A choice of the following type of attendants: AC4, AC-WIN and AC-WIN MQ. is made by the
parameter ACTYPE in AMO ACSU
For a group of AC-WIN MQs the AMO-VFGR has to create an attendant group with QUE-
MODE=MQ (multiple queue) whereas a group of other attendants (AC4, ACWin-4.x) is created
via QUEMODE=DQ (double queue).
AC-WIN MQ attendants cannot be within the same attendant group with other type of atten-
dants.
258
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Attendant Console
The night options are given a neutral number created in the NAVAR AMO and allocated in the
ATNDGR as night option 1, 2 etc.
Once the ATND group has been defined it is assigned the codes:
● ATNDDID for direct inward dialling (incoming CO (central office) calls to the attendant),
● ATND attendant code, (internal calls to the attendant)
● GENANS, if trunk answer from any station has been implemented
It is necessary to assign the ATNDDID access code and also the ATND access code for every
used attendant group (VFGR) via the AMO VFGKZ. The attendant group cannot be reached
without the assignment of these access codes (even in case of intercept calls or personal calls
to the attendant).
If an ATND group takes over the tasks of another ATNDGR as a night variant, it becomes a
"Centralized Attendant Services" group (CASGR). This CASGR can be in the home system
(CASINT) or in another node of a network (CASEXT).
An ITR group and/or DPLN group does not need to be specified unless access to the attendant
terminal group is to be restricted. This is necessary, for example, if several customers share
one system and one ATND group is set up per customer.
If all customers share a common attendant group, up to 1000 ATNDDID access codes can be
assigned for incoming CO calls and for each access code a particular company name can be
assigned.
This is done via AMO-ZAND, TYPE=ATND, COMP1000=YES and the appropriate AMO VF-
GKZ assignments for the access codes and the company names.
If the AMO-ZAND value COMP1000 is set to NO then up to 10 ATNDDID code numbers can
be added per customer for incoming CO calls and each number (00-09) can be assigned to a
particular company name (VBZGR AMO). Before the implementation of up to 1000 company
names this limit was 10 company names. The limited option is kept in order to simplify the soft-
ware upgrade of switches to a higher software release.
ATNDs can be added to, or deleted from, an ATND group any time; one ATND may not belong
to more than one ATNDGR at a time. Night ATNDs are not supported anymore.
Special night answer stations (ANATE or DIGITE) can be assigned to several night options.
Only one station (ANATE), which is assigned with the SSC AMO, is entered in the GENANS
night option.
Before being deleted, day ATNDs, special night answer positions and GENANS positions must
be cancelled from any groups to which they are assigned (ATNDGR, night option, hunting
groups).
Before an ATNDGR is deleted, any code allocation and integration into the device search must
be deleted with the VFGKZ AMO.
259
EN4402EN00EN_0003
© 2004 Siemens AG
The overflow position option, (required when all positions of an ATNDGR are busy), is de-
scribed in detail in the VFGR AMO Description.
The individual attendant terminals can be assigned a name and an organizational unit under
their respective call numbers using the PERSI AMO.
Attendant consoles cannot be configured in hunting groups.

In the case of systems without attendant console an ATND group must still be con-
figured, complete with an assigned night answer station! (No hardware required!)
Up to 16 attendant groups can be configured in one system.

Special access authorizations must be entered for stations assigned as special night answer
stations (using the AMO ZAND). When the night switch is active, the authorizations contained
in COS1/COS2 of these stations are replaced by the authorizations defined with the AMO
ZAND.
The central parameters for the attendant consoles can be found in the TYPE=ATND
branch of the ZAND AMO.
260
EN4402EN00EN_0003
© 2004 Siemens AG
37.3 Comfort Attendant Console

As of the version Hipath 4000 V1.0 the features are worldwide released to multiple queue (MQ)
and parallel display in addition to the double queue (DQ) for the windows attendant console.
37.3.1 Overview AC-WIN (DQ)

The Hipath 4000 V1.0 feature "double queue" is the standard for the queue mode of arrange-
ment groups. This mode supports two spring queues, which submits incoming calls and is tak-
en to disconnected mode there as administered. All calls incoming with such a AC group are
shown to the attendant console according to the configuration.
Calls waiting
in the queues
Active
Calls
Status
261
EN4402EN00EN_0003
© 2004 Siemens AG
37.3.2 Overview AC-Win MQ

Released world wide from Hipath 400 V1.0 is the feature Multiple Queues and Parallel Presen-
tation Windows console.
The Hipath 4000 V1.0 feature Multiple Queues and Parallel Presentation provides a new
Queue mode for Attendant Groups. This Queue mode supports 12 Source Queues to which
calls are directed and queued according to the administration in AMO BUEND and AMO VFGR.
All incoming calls to such an Attendant Group are parallel presented to the Attendants of the
group. Directed calls to special Attendants and personal calls are also queued but presented
to this special Attendant only. This Queue mode is named MQ (Multiple Queues) and is the al-
ternative to the DQ (Double Queue) mode.
Calls waiting
in the queues
Active calls
Calls in
progress
Status
262
EN4402EN00EN_0003
© 2004 Siemens AG
Valid Attendant types in these groups can be:
Attendant Group Queue Mode Attendant type

DQ (Double Queue) AC4, AC-Win 4.x
MQ (Multiple Queue) AC-Win MQ 2.x
The feature can be used networkwide in a homogeneous Hipath 4000/Hicom 300 HV1.0 and
mixed Hipath4000/Hicom 300 HV1.0 / DX networks.
There are no changes to hardware required for this new feature the Multiple Queue version of
the AC-Win utilizes the same hardware as the previous ACWin-xx. The feature requires a dif-
ferent software package to be loaded on the PC.
263
EN4402EN00EN_0003
© 2004 Siemens AG
37.4 Nodes without an Attendant Console
Feature description
Ensure that an attendant group with a "STN" (station) or an empty variant night switch option
is assigned in nodes without ATNDs.
Service information
● This requires no HW (AC)!
Example
● Assign a "STN" night switch option
AD-NAVAR:NOPTNO=number,TYPE=STN,STNO=number;
or as an empty variant:
AD-NAVAR:NOPTNO=number,TYPE=NONE;
● Assign a console group with station
AD-VFGR:ATNDGR=number,NOPT1=number,OPT=number,CQMAXF=number;
Relevant AMOs
AMO Parameter Sprache/ Beschreibung/Description

Language
NAVAR NAVARNU d NACHTVARIANTENNUMMER
NOPTNO e NUMBER OF NIGHT SWITCHING OPTION
TYP d GERAETETYP DER NACHTVARIANTE
TYPE e NIGHT ANSWER CATEGORY
TLNNU d RUFNUMMER EINER NEBENSTELLE
STNO e TATION NUMBER
VFGR VFGRU d NUMMER DER VF - GRUPPE
ATNDGR e ATTENDANT GROUP NUMBER
EINGVA d IM NACHTSCHALTUNGSFALL ZU AKTIVIERENDE
VARIANTE
OPT e NIGHT OPTION ON ACTIVATION OF NIGHT MODE
NTVAx d DER NACHTVARIANTE x ZUGEORDNETE VARIANTE
x = 1 ... 8
NOPTx e DEVICE(S) ASSIGNED TO NIGHT OPTION x
x = 1 ... 8
264
EN4402EN00EN_0003
© 2004 Siemens AG
37.5 AMO Usage Examples
37.5.1 Assign an Attendant (AC)

● Assign attendant telephone number in AMO WABE
ADD-WABE=CD=<Individual Attendant Console number>,DAR=ATNDIND;
● Assign a class-of-service in AMO COSSU
ADD-COSSU:AVCE=parameter...;
● Assign attendant console in AMO ACSU
ADD-ACSU:ATNDNO=<Individual Attendant Console number>,PEN =<port equipment num-
ber of the attendant: ltg-ltu-slot-cct>,DPLN =<feature access group / dial plan>,COS =<class
of service>,LCOSV =<LCR class of service for voice-services of this attendant: 1...32
(1)>,LANG =<language parameter for Attendant: e.g. ENG for english (DE)>,ACTYPE =<Atten-
dant Console type parameter: ACWIN / AC4>;
Parameter ACWIN is used for all AC-Win x.x and AC-Win MQ x.x types.
Parameter AC4 is used for normal AC types.
37.5.2 Assign an Attendant Group (ATNDGR)

● Assign the digit analysis results in AMO WABE
ADD-WABE:CD=<Internal Operator group number>,DAR=ATND;
ADD-WABE:CD=<Indial number to Operator group>,DAR=ATNDDID;
● Assign the Attendants in AMO ACSU
● Assign the night options in AMO NAVAR
ADD-NAVAR:NOPTNO=<Night Option number>,TYPE=<Night option type>,....;
NOTE : from Hipath 4000 V1.0 Night attendants are no longer supported
● Assign the attendant group in AMO VFGR
For each Attendant group it must be decided in which Queue mode the group shall be op-
erated.
Attendant groups with Double Queue mode (DQ) can consist of AC4 and AC-Win 4.x At-
tendant types.
265
EN4402EN00EN_0003
© 2004 Siemens AG
ADD-VFGR:ATNDGR=<Atnd.Grp.number>,QUEMODE=DQ,ATNDNO=<num-
ber>,NOPT1=<Night option number>,OPT=<Selected Night Option parameter NOPTx on
activation of Night mode:1...8 >;
Attendant groups with Multiple Queues mode (MQ) can consist of AC-Win MQ 2.x Atten-
dant type only.
ADD-VFGR:ATNDGR=<Atnd.Grp.number>,QUEMODE=MQ,ATNDNO=<num-
ber>,NOPT1=<Night option number>,OPT=<Selected Night Option parameter NOPTx on
activation of Night mode:1...8 >;
The AMO VFGR automatically puts all attendant consoles into operation.
● Assign dialing codes (internal operator group and indial to operator group dialing code) to
the new defined Attendant Group
ADD-VFGKZ:TYPE=ATNDGR,CD=<key-num>,ATNDGR=<Attendant Group number>;
37.5.3 Assign a Name to an ATND Group

In shared systems for each of up to 1000 ATNDDID access codes a company name can be
assigned via AMO VFGKZ. This company name appears on the display of the attendant con-
sole.
● Assign a name to a console number
ADD-VFGKZ:TYPE=NAME,CD=<key-num>,NAME=<string>;
For attendant intercept, the ITR group of the user station or of the trunk circuit is checked and
the name assigned to this ITR group is displayed on the terminal. The customer name is allo-
cated to the ITR group with the VBZGR AMO.
● Assign the same name for attendant intercept
AD-VBZGR:GROUP=<number>,TYPE=CUSNAME,NAME=<string>;
The stations assigned to the ITR groups can be interrogated with the AMO
SCSU/SBCSU.
266
EN4402EN00EN_0003
© 2004 Siemens AG
37.5.4 Remove an ATND from an ATNDGR and Delete

● Remove the attendant from the attendant group
CHA-VFGR:ATNDGR=<number>,ATNDNO=<number>,FUNCT=DEL;
● Delete the attendant
DEL-ACSU:ATNDNO=<number>,DELOPT=ALL;
● Delete attendant telephone number from the DPLN (if necessary)
DEL-WABE:TYPE=CD,CD=<key-num>,DAR=ATNDIND;
37.5.5 Change Personal Number of Attendant

● Change the number in the DPLN
CHA-WABE:CD=key-num,CDNEW=key-num,DAR=ATNDIND;
● Change number:
CHA-ACSU:ATNDNO=number,NEWNO=number;
37.5.6 Change ATND Internal Access and Answer Codes

● Assign the station number in the DPLN
AD-WABE:CD=<key-num>,DAR=<ATNDDID or ATND>;
● Assign new codes to the ATND group
CHA-VFGKZ:TYPE=ATNDGR,CD=<key-num>,ATNDGR=<number>;
● Delete old codes in the DPLN (if necessary)
DEL-WABE:TYPE=CD,CD=<key-num>,DAR=<ATNDDID or ATND>;
37.5.7 Add an ATND to an ATNDGR

Prerequisite: the ATND must be configured.
● Add ATND to ATNDGR
CHA-VFGR:ATNDGR=<number>,ATNDNO=<number>,FUNCT=ADD;
37.5.8 Centralized Attendant Services (Internal)

The internal centralized Attendant services group (CASINT) is assigned in the home node. This
function enables the entire range of attendant functions of an ATNDGR to be transferred to an-
other ATNDGR. If an attendant group takes on the attendant terminal traffic of another AT-
NDGR in addition to its own, it functions as a central attendant group. Thus, an ATNDGR which
takes over the functions of another ATNDGR within the same node is known as an internal Cen-
267
EN4402EN00EN_0003
© 2004 Siemens AG
tralized Attendant Services group (CASINT). The assignment of an ATNDGR is entered as a

night option with the AMO NAVAR, which is in turn assigned to another ATNDGR (CASINT).
Only one CASINT may be assigned to a night option. Please note that an ATNDGR must be
allocated at least one normal night option. A CASINT may also switch over to an internal night
option. The CASINT can only be operated as a night variant, even if no ATND is assigned.
● Assign an attendant console
● Assign night options for the CASINT
ADD-NAVAR:NOPTNO=<number>,TYPE=CASINT,ATNDGR=<number>;
More than one night option can be assigned a CASINT as a destination.
● Assign an attendant group to a CASINT night option

ADD-VFGR:ATNDGR=number,{NOPT1...NTVA8},OPT=number,CQMAXF=number;
37.5.9 External Centralized Attendant Services Group

An external centralized attendant services group (CASEXT) is located in a ’foreign’ node. Sev-
eral CASEXT can be assigned and active within one network or even within the same system.
Each ATNDGR is unambiguously accessible for incoming attendant traffic. Access is obtained
by dialling the internal telephone number or indirectly via ATNDGR or DPLNGR.
● Assign night options for the CASEXT
ADD-NAVAR:NOPTNO=number,TYPE=CASEXT,CD=number,DESTNO=number;
The parameter CD must be the internal access code of the destination system. A 22-
digit call number can be specified with the "CD" parameter. In open numbering
plans, this call number consists of the tie-line access code and the ATND access
code. In closed numbering plans, the ATND access code of the attendant group in
the destination system must be entered. This code must lead to a "NETW" digit anal-
ysis result (DAR) in the dial plan.
● Assign a night option to an ATNDGR

ADD-VFGR:ATNDGR=number,{NOPT1...NTVA8},OPT=number,CQMAXF=number;
268
EN4402EN00EN_0003
© 2004 Siemens AG
Relevant AMOs
AMO Parameter Sprache/ Beschreibung/ Discription

Language
ACSU GEVFNU d geheime vf-nummer (JA,NEIN,NUREXT)
SATNDNO e secret ac number (YES, NO, ONLYEXT)
KNNR d virtuelle Knotennummer
NNO e virtual node identification
SRCGRP d source gruppen index
e source group index
CLASSMRK d classmarks for ip connection
e classmarks for ip connection
PUBNUM d public telephone number
e public telephone number
VFGR AOMODUS d anrufordner modus
QUEMODE e call queuer mode
AULSTEU d steuerung des anrufs bei anrufumleitung beim zielteil-
nehmer
COD e control of diversion when calling target station
ENACHTPR d prioritaet der einzelnachtschaltung
INIGHTPR e priority of individual night service
269
EN4402EN00EN_0003
© 2004 Siemens AG
37.6 Function-Enhancements for the Attendant Queues

The priority assignment to calls in call queues of an AC group is improved.
ATNDGR=0
No longer strict call assignment for
the answer keys L1 (trunk) and L2
(attendant line).
8 freely assignable priority levels per

trunk group and calling unit.
AC group overflow after timeout

can be administrated per ATNDGR
ATNDGR=1
Free assignment of the answer keys

L2 attendant line
L1 trunk
predefined standard
Enhanced priority control, priority increase and call overflow

The feature is indicated by the following three qualities:
● Incoming calls are bound one and processed in the call queue after new priority criteria.
● At calls in the call queue waiting longer the priority level is increased after time.
● Calls in the call queue waiting longer are diverted (overflow) after time to another manual
switching position group.
270
EN4402EN00EN_0003
© 2004 Siemens AG
37.6.1 Priority Calculation and Queue Assignment
Feature description
There is a flexible mechanism to direct incoming calls over different trunks or with different call
types to the call answering queues of the Attendant Groups. This mechanism can be used to
adapt each customer specific profile for incoming calls to the defined Attendant groups.
For every Attendant group eight priority levels per queue can be configured:
– DQ mode: Priority level 1...8 for answer key L1 and 1...8 for answer key L2,
– MQ mode: Priority level 1...8 for each Source Queue key SQ01...SQ12.
Incoming calls can be freely assigned to an Queue key and a priority level. The highest priority
level is 1.
Definition of priority numbers and their assignment to a priority level

available per ATNDGR
available per HiPath4000
Answer Key Priority Level
priority number
Emergency call PNo1 PNo 1 L2 or L1 / S01..S12 1
Trunk PRI Local First call PNo 40 PNo 2 L2 or L1 / S01..S12 7
PNo 3 L2 or L1 / S01..S12 5
group number
1 1-48
2 1-48
3 1-48
4 1-48
5 1-48
● ● PNo 47
L2 or L1 / S01..S12 3
PNo 48 L2 or L1 / S01..S12 4
● ●
● ● CO-recall PNo16 ANSKEY PROLEV
● ● Overflow CO-call PNo16
● ● Combination of call types to one

priority number (AMO VFGR)
510 1-48 Assignment of priority
Any number of call types can be numbers with one priority
511 1-48 assigned to one priority number.
and one answer key,
512 1-48
(AMO VFGR).
Combination of trunk groups to one prior- Several priority numbers
ity number 1-48 (AMO BUEND). Any can be assigned to one
number of trunk groups can be assigned priority level.
to the same priority number.
CorNet-NQ
e.g.PNo16
PNo n = Priority number n = 1......48
L1 n = O-call with prio n = 1.........8
If the COT parameter (PRIO) is set, the priority number transmitted by Cor- L2 n = AT-call with prio n = 1........8
Net is used. Up to 16 priority classes can be transmitted. If the COT S01.12 = Source keys on AC-Win MQ
parameter is not set, the priority number of the trunk group is used.
271
EN4402EN00EN_0003
© 2004 Siemens AG
The priority level for incoming calls are assigned in two steps
Incoming calls are assigned to priority numbers (0-48) The priority number of incoming calls
can be established in various ways.
With external first calls (including calls by intercept) according to their origin, i.e. trunk group
specific (AMO BUEND). The established priority number is then the same for all AC groups
within one PBX.
With external first calls via transit connections (CASMCF) using CorNet-NQ, the priority num-
ber of the originating node can be transmitted (can be administrated in the destination node
using COT parameter PRI).
With transmission via CorNet NQ, they also apply within a system network. Transmitted via Cor-
Net NQ will be the priority numbers 1...16 only. Higher priority numbers (17...48) are mapped
to priority number 16. The priority level can then be determined from the priority number. The
originating node must be a homogeneous Hicom network with at least Hicom 300 HV1.0. In
transit nodes the priority number is switched transparently through, subject to the COT param-
eter PRI being set in the transit node for the incoming trunk. With internal calls from an origi-
nating node the priority number of the outgoing trunk group is transmitted. The COT parameter
PRI is an old parameter (transmission of the priority number via CorNet-NQ in homogeneous
Hicom HV1.0 networks) but changes function with this new usage.
● For all other calls the priority numbers are assigned according to the call type.
Calls with the same priority level within a call queue (answer key) are answered by the Atten-
dants according to the FIFO principle. The longest waiting call is the first transferred to a free
station (AC Win or Night station).
Service information
● A priority order for the calls can be defined per AC group.
● The incoming calls can be freely assigned to either answer key L1 or L2. The fixed rule that
trunk calls are assigned to answer key L1and all other calls are assigned to answer key L2
no longer applies.
This allows the assignment of all calls to only one answer key (single distribution).
● Priority numbers of the trunk groups apply to all AC groups within a Hicom. With transmis-
sion via CorNet-NQ, they also apply within a system network.
● The priority number transmission via CorNet-NQ is only supported within a homogeneous
Hicom network (with COT parameter PRI set).
In transit nodes the priority number is switched transparently through, provided the COT
parameter PRIO is set in the transit node for the incoming trunk.
With internal calls from an originating node the priority number of the outgoing trunk group
is transmitted.
272
EN4402EN00EN_0003
© 2004 Siemens AG
● The COT parameter PRI is an old parameter the meaning of which has been changed.
– Transmission of the priority number via CorNet-NQ in homogeneous Hicom HV1.0 net-
works.
– Original meaning: Priority establishment for prioritized trunk groups for calls to the call
queue. This meaning is no longer relevant
With heterogeneous networks (E V1.0, E V2.0 HV1.0) with CASMFC in HV1.0, the
PBXs with the older version require a patch in order to differentiate between trunk
and attendant line calls.
273
EN4402EN00EN_0003
© 2004 Siemens AG
Following Call Types are supported
Call Type Definition Basic Initialization Basic Initialization

DQ priono MQ priono
EMERG EMERGENCY CALL 3 36
HOT HOTLINE CALL 3 36
LOFC LOCAL FIRST CALL 2 46
LOREC LOCAL RECALL 2 42
LOPRIC LOCAL PRIO CALL 4 45
COREC CO RECALL 5 40
COSER CO SERIAL CALL 5 40
COINCO CO IN CONSULTATION 5 43
COONHOOK CO ON HOOK IN CON- 5 43
SULTATION
TIREC TIE RECALL 2 41
TISERTT TIE SERIAL CALL 2 41
TIINCO TIE IN CONSULTATION 2 44
TIONHOOK TIE ON HOOK IN CON- 2 44
SULTATION
OVLOFC OVERFLOW LOCAL 2 39
FIRST CALL
OVLOPRIC OVERFLOW LOCAL 2 38
PRIO CALL
OVCOFC OVERFLOW CO FIRST 5 37
CALL
OVTIFC OVERFLOW TIE FIRST 2 38
CALL
PERSONAL PERSONAL CALL -- 48
ACLOOP ATND. LOOP TRANS- -- 47
FER
The following tables show the standard initialization values for the various call types and their
priority levels
274
EN4402EN00EN_0003
© 2004 Siemens AG
DOUBLE QUEUE (DQ)
Priority Number PRIONO ANSKEY PRIOLEV

1(CO first call-AMO BUEND) L1 3
2 (int &ext calls init AMO-BUEND L2 3
3 L2 1
4 L2 2
5 L1 2
6-8 L2 8
9 (CO call from Hicom 300 <HV1.0 L1 3
10 (call from Hicom 300 <HV1.0 L2 3
11-48 L2 8
Multiple Queues (MQ)

1 SQ01 3
2 SQ02 3
3-8 SQ012 8
9 (CO call from Hicom300 <HV1.0 SQ01 3
10 ( call from Hicom300 <HV1.0 SQ02 3
11-35 SQ012 8
36 SQ07 1
37 SQ07 3
38 SQ07 5
39 SQ07 7
40 SQ08 3
41 SQ08 5
42 SQ08 7
43 SQ09 3
44 SQ09 5
45 SQ10 3
275
EN4402EN00EN_0003
© 2004 Siemens AG

46 SQ10 5
47 SQ11 3
48 SQ11 8
Application examples:
1. For trunk calls from a certain trunk group assign the priority level 1 on the answer key L1
for ATNDGR 0 and priority level 4 on the answer key L2 for ATNDGR 1.
● Search for an existing priority number with the priority level of a different trunk group.
Enter this priority number for the CO trunk group.
In this example there is no such priority number. A free priority number is used.
The new priority number (e.g. PNo.8) is entered in the trunk group of the incoming
trunk (e.g. TG No. =201):
CHA-BUEND:TGRP=201,PRIONO=8;
● Assign the priority level 1 on answer key T to the priority number 8 for ATNDGR 0:
CHA-VFGR:ATNDGR=0,TYPE=PRIOLEV,PRIONO=8,ANSKEY=L1,PRIOLEV=1;
● Assign the priority level 4 on answer key O to the priority number 8 for ATNDGR 1:
2. for local first calls, assign the priority level 8 on answer key L1 for ATNDGR 0 and the pri-
ority level 4 on answer key L2 for ATNDGR 1.
● There is no corresponding priority level for ATNDGR 0. Assign a new, unused priority
number for this ATNDGR (e.g. PNo. 9).
CHA-VFGR:ATNDGR=0,TYPE=PRIOCALL,LOFC=9;
● Assign the priority level 8 on answer key L1 to the priority number 9 for ATNDGR 0:
● The priority level 4 on answer key L2 has already been assigned for ATNDGR 1 (first
example). Enter the corresponding priority number 8 for the call type:
CHA-VFGR:ATNDGR=1,TYPE=PRIOCALL,LOFC=8;
3. Assign the priority level 6 on answer key L1 for recalls (trunk, tie and internal) to ATNDGR0.
● There is no corresponding priority level for ATNDGR 0. Assign a new priority number
(e.g. PNo. 10).
CHA-VFGR:ATNDGR=0,TYPE=PRIOCALL,LOREC=10,COREC=10,TIREC=10;
● Assign the priority level 8 on answer key T to the priority number 10 for ATNDGR 0:
276
EN4402EN00EN_0003
© 2004 Siemens AG
4. For trunk calls from a certain trunk group in an originating node assign the priority level 2
on answer key L1 for ATNDGR 1 in the destination node (only possible in homogenous Hi-
com networks via CorNet-NQ)
● Enter a free priority number, unassigned in the system network, (e.g. PNo. 11) in the
trunk group of the originating node as described under 1).
● Set the COT parameter PRIO (e.g. COT No. 20) for the incoming CorNet-NQ trunk in
the destination node:
CHA-COT:COTNO=20,COTTYPE=COTADD,PAR=PRIO;
● Assign the priority level 2 on answer key T to the priority number 11 for ATNDGR 1.
5. For internal calls in an originating node assign the priority level 7 on answer key L2 for AT-
NDGR 1 in the destination node (only possible in homogeneous Hicom networks via Cor-
Net-NQ)
● Enter a free priority number (e.g. PNo. 12) at the outgoing trunk group (e.g. BNo. 21)
of the originating node.
CHA-BUEND:TGRP=21,PRIONO=12;
● Set the COT parameter PRIO (e.g. COT no. 20) for the incoming CorNet-NQ trunk:
CHA-COT:COTNO=20,COTTYPE=COTADD,PAR=PRIO;
● Assign the priority level 7 on answer key O for ATNDGR 1.
CHA-VFGR:ATNDGR=1,TYPE=PRIOLEV,PRIONO=12,ANSKEY=O,PRIOLEV=7;
6. Activate the priority increase and change the timer to 30 seconds
● Activate the priority increase using AMO FEASU
CHA-FEASU:TYPE=A,LM=INCPRIO;
● Change the priority timer
CHA-CTIME:TYPESWU=ATNDTIME,CQPRIO=30;
7. Direct the overflow of ATNDGR 0 to ATNDGR 1. Change the overflow timer to 40 seconds.
8. Activate the overflow by entering an overflow ATNDGR using AMO VFGR
CHA-VFGR:ATNDGR=0,TYPE=GENERAL,OFLGR=1;
Note: the parameter "OFLGR=*" deactivates the overflow for this ATNDGR.
9. Change the overflow timer
CHA-CTIME:TYPESWU=ATNDTIME,CQOFL=40;
277
EN4402EN00EN_0003
© 2004 Siemens AG
Relevant AMOs

Language
BUEND PRIONUM d Prioritätsnummer 1-16
PRIONO e Priority number 1-16
COT PRIO d Priorität von der Unteranlage übernehmen für den
kommenden Anruf.
Achtung: neue Bedeutung in der E V3.0
PRI e Accept priority from the satellite PBX for the incoming
call.Attention: new meaning in EV3.0
VFGR PRIOCALL d Verzweigungsparameter (Typ=PRIOCALL)
ARUEAMT Auflegen in Rückfrage - Amt
ARUEQUE Auflegen in Rückfrage - Quer
EAINT Erstanruf intern
EABVT Erstanruf bevorzugte TLN intern
EINTRAMT Eintreteaufforderung Amt
EINTRQUE Eintreteaufforderung Quer
KETAMT Kettenanruf Amt
KETQUE Kettenanruf Quer
NOTRUF Notruf /* Vorleistung*/
ROE Röcheln
UEBVT Überlauf intern - bevorzugte tln
UEEAAMT Überlauf Erstanruf - amt
UEEAI Überlauf erstanruf - intern
UEEAQUE Überlauf Erstanruf - quer
WAAMT Wiederanruf amt
WAINT Wiederanruf intern
WAQUE Wiederanruf quer
278
EN4402EN00EN_0003
© 2004 Siemens AG

Language
PRIOCALL e Branch: priority numbers of call types
COONHOOK co on hook in consultation
TIONHOOK tie on hook in consultation
LOFC local first call
LOPRIC local prio call
COINCO co in consultation
TIINCO tie in consultation
COSER co serial call
TISERTT tie serial call
HOT hotline call
EMERG emergency calling /* Vorleistung */
OVLOPRIC overflow local prio call
OVCOFC overflow co first call
OVLOFC overflow local first call
OVTIFC overflow tie first call
COREC co recall
LOREC local recall
TIREC tie recall
PRIOLEV d Verzweigung (TYP=PRIOLEV)
AO Abfrageorgan
PRIONUM Prioritätsnummer
PRIOLEV Priority Level
PRIOLEV e Branch:
ANSKEY Answer key
PRINO priority number
PRIOLEV priority level
UELGR d Überlaufgruppe
OFLGR e overflow attendant group
279
EN4402EN00EN_0003
© 2004 Siemens AG
37.6.2 Priority Upgrade
Feature description
Calls waiting longer are diverted after time to another Attendant group. This behavior is admin-
isterable. Every Attendant group (VFGR) has an overflow aim of its own. The overflow is active
then if another Attendant group than overflow aim is registered.
The priority level of calls with a low priority level is increased to the highest priority level (priority
level 2) after timeout. Priority level 1 is reserved for Emergency calls only and can not be
reached by Priority Upgrade.
Service information
● Overflow after timeout is not executed for directed calls to an Attendant (serial call, re-call,
personal call etc.). Exception: this Attendant is pre-blocked or is unplugged.
● The priority level is newly calculated at the overflow Attendant. For the internal and external
first calls (incl. intercept), as well as for prioritized stations, the priority numbers of the con-
figured overflow call types apply.
● Every attendant group has its own overflow destination.
● The overflow is active if an AC group has been specified as overflow destination.
● The over–running time is centrally adjustable.
Generation example
● Priority Upgrade is activated using AMO FEASU:
CHANGE-FEASU:TYPE=<A>,CM=<CQPRI>;
● The timer for the priority increase can be set using AMO CTIME:
CHANGE-CTIME:TYPESWU=ATND,CQPRIO=<5...240>;
● Overflow to another Attendant group after timeout.
Calls waiting for a longer period of time in the call queue are transferred to another Atten-
dant group after timeout. This feature can be administrated using AMO VFGR:
CHANGE-VFGR:ATNDGR=<number>,TYPE=GENERAL,OFLGR=<assigned overflow atten-
dant group>,
● The overflow timer can be set using AMO CTIME.
CHANGE-CTIME:TYPESWU=ATND,CQOFL=<5...240>;
280
EN4402EN00EN_0003
© 2004 Siemens AG
Relevant AMOs

Language
CTIME CQOFL d Zeitglied für den Überlauf
CQOFL e Overflow timer
CQPRIO d Zeitglied für die Prioritäterhöhung
CQPRIO e Timer for priority increase
FEASU ERHPRIO d Erhöhen der Priorität nach Zeitablauf
INCPRIO e Increase priority level after timeout
VFGR UELGR d Überlaufgruppe
OFLGR e overflow attendant group
37.7 Automatic Night Service
Feature description
For each Attendant group it can be defined if it works with an Automatic night switch,i.e. call
forwarding - no answer for each Attendant of the group to Night option NOPT 8 after a timeout.
If a call is ringing on the Attendants and the Attendant does not execute any call processing
actions or switch settings then the Attendant console will switch to Night mode automatically
after time out.
Service information
● This feature works in different ways, dependant on the used group Queue mode:
Attendant Group with Double Queue mode (DQ):
If the Attendant is not the last Attendant in the group then the calls are distributed new
to the other Attendants of the group in Day Service. Personal calls are released.
If the Attendant is the last Attendant in the group then all waiting calls are forwarded to
the NOPT8 destination. Personal calls are released.
Attendant Group with Multiple Queues mode (MQ):
If the Attendant is not the last Attendant in the group then the calls will be presented
to the other Attendants of the group in Day Service further. Directed calls to this special
Attendant will be changed to parallel presented calls. Personalcalls are released.
If the Attendant is the last Attendant in the group then all waiting calls are forwarded
to the NOPT8 destination. Personal calls are released.
281
EN4402EN00EN_0003
© 2004 Siemens AG
● The AMO ZAND parameter AUTNS has no impact for MQ Attendant groups.
● In both cases the Attendant Console changes to Night Service.
As a refinement of this behavior the Automatic Night Service can be executed for the ringing
call only. The ringing call is newly distributed or forwarded to the NOPT8 destination only after
time out. The Attendant console remains in Day Service.Therefore administrate the following
parameter in addition to the VFGR parameter:
Generation example
Set automatic night option for an attendant group:
CHANGE-VFGR:ATNDGR=<number>,TYPE=GENERAL,AUTNS=ON;
Change the timer:
CHANGE-CTIME:TYPESWU=ATND,ATNDCALL=<10...90 seconds>;
Set automatic night option only for incoming calls:
CHANGE-ZAND:TYPE=ATND,AUTNS=YES;
Relevant AMOs

Language
CTIME ATNDCALL d Zeitglied für den ATTENDANT-CALL
ATNDCALL e Timer ATTENDANT CALL
ZAND AUNA d AUTOMATISCHE NACHTSCHALTUNG
AUTNS e AUTOMATIC NIGHT SWITCH
VFGR AUNA d AUTOMATISCHE NACHTSCHALTUNG
AUTNS e AUTOMATIC NIGHT SWITCH
282
EN4402EN00EN_0003
© 2004 Siemens AG
37.8 Attendant Intercept
Feature description
Intercept of calls by the attendant terminal is controlled in accordance with ITR groups:
The allocation of the ITR group to the attendant group intercept is entered in a table by the
VFGR AMO. An automatic process ensures that each of the groups 0-15 (though not all may
have been entered) is assigned one ATNDGR. This is effected automatically by entering this
ATNDGR in all ITR groups of the table when the first ATNDGR is set up with the VFGR AMO
Further ATNDGR can now be set up specifying precisely from which ITR group calls should be
intercepted by this ATNDGR. The original entries will then be overwritten.
Service information
● If the dialled station number leads to a station in the same system, the dialled station’s ITR
group is used for selecting the attendant console group to which the call is forwarded.
● If the dialled station number leads to a station in a remote system within a CorNet-N private
network, the ITR group depends on the ITRN parameter value of the class-of-trunk (COT)
of the calling line:
– If ITRN ist set, the dialled station’s ITR group is used for selecting the attendant con-
sole group to which the call is forwarded.
– If ITRN ist not set, the calling line’s ITR group is used for selecting the attendant con-
sole group to which the call is forwarded.
● If the dialled station number leads to a station in a non-networked remote system, the call-
ing line’s ITR group is always used for selecting the attendant console group to which the
call is forwarded.
Hint:
Before an ATNDGR can be deleted, and unless it is the only one in the system, another AT-
NDGR must be entered with the CHANGE VFGR action as intercept destination.
Assign an ATNDGR to an ITRGR as an intercept destination (ITDEST), e.g. 5.
AD-VFGR:ATNDGR=number,{NOPT1...NTVA8},OPT=number,CQMAXF=number
,ITDEST=5;
Generation (example)
Abwurf von externen Anrufen (CO-Trunks) bei "nicht vorhanden" auf eine eigene VFGR mit
Nachtschaltung auf ein Ansagegerät an einem analogen Port, um die Vermittlung zu entlasten:
(hier nur die primär zur Einrichtung wichtigen Kommandos)
283
EN4402EN00EN_0003
© 2004 Siemens AG
/* Allow feature intercept */

CHANGE-FEASU:TYPE=A,CM=ICPTDID;
/* Cot with IVAC */
ADD-COT:COTNO=100,PAR=IVAC,INFO="INTERCEPT";
/* Trunks, with ITR 15 */
CHANGE-TDCSU:PEN=<LTG-LTU-EBT-PORT>,COTNO=100,ITR=15;
/* SLMA1 for announcement */
ADD-BCSU:MTYPE=PER,LTU=1,SLOT=55,PARTNO=Q2141-X;
/* Configure station for announcement */
ADD-SCSU:STNO=2100,PEN=1-1-55-0,DVCFIG=AN-
ATE,DPLN=1,ITR=0,COS1=380,COS2=380,LCOSV1=8,LCOSV2=7,LCOSD1=1,LCOSD2=1;
SOND=SOTL&NAWA,WAHL=MFV,DHPAR=MFVTLN,INBETR=JA,GETLNNU=NEIN;
/* Station as night option (e.g. No. 128) */
ADD-NAVAR:NOPTNO=128,TYPE=STN,STNO=2100;
/* Install ATNDGR with night option for intercept ITR (15) of trunks */
ADD-VFGR:ATNDGR=2,NOPT1=128,OPT=1,CQMAXF=3,ITDEST=15;
/* Activate call queues */
ADD-VFGKZ:TYPE=ATNDGR,CD=98,ATNDGR=2;
ADD-VFGKZ:TYPE=ATNDGR,CD=99,ATNDGR=2;
/* Activate night option for ATNDGR */
ADD-ACTDA:TYPE=ATNDGR,ATNDGR=2,NOPT=1,ACT=ACT;
/* Setup Interalia MMU2-62AB */
Operating Type:Ring Start with Loop Current Check. Dipfix-Switch:
S1 = on \
S2 = on > Message 1 on all lines
S3 = on /
S4 = off \
S5 = on \
S6 = off > Ring Start Mode on all lines
S7 = on /
S8 = on > separate ansage
284
EN4402EN00EN_0003
© 2004 Siemens AG
Relevant AMOs

Language
NAVAR NAVARNU d NACHTVARIANTENNUMMER
NOPTNO e NUMBER OF NIGHT SWITCHING OPTION
TYP d GERAETETYP DER NACHTVARIANTE
TYPE e NIGHT ANSWER CATEGORY
RNR d PLATZKENNZAHL DER EXTERNEN ZVFGR
CD e CODE FOR EXT. CENTRALIZED ATND SERVICE
VFGRU d VF-GRUPPENNUMMER
ATNDGR e ATND GROUP NO.
TLNNU d RUFNUMMER EINER NEBENSTELLE
STNO e STATION NUMBER
FEASU LM d Leistungsmerkmal
CM e feature, class mark, facility
VFGR VFGRU d NUMMER DER VPL - GRUPPE
ATNDGR e ATTENDANT GROUP NUMBER
NTVA1 d NACHTVARIANTE 1 ZUGEORDNETE VARIANTE
NOPT1 e DEVICE(S) ASSIGNED TO NIGHT OPTION 1
ABWVBZ d vbz-gruppen die diese vfgr als Abwurfziel haben
ITDEST e int. traffic groups having atnd group as intercept dest.
EINGVA d im Nachtschaltungsfall zu aktivierende Variante
OPT e night option on activation of night mode
VFGKZ RNR d Kennzahl einer Vermittlungsfernsprechergruppe
CD e attendant console group access code
VFGRU d Vermittlungsfernsprechergruppe
ATNDGR e attendant group number
ACTDA VFGRU d vf-Gruppennummer
ATNDGR e attendant group number
NAVAR d Nachtvariante fuer vf-Gruppe
NOPT e night options for attendant
ACT d Aktivierungsparameter fuer Nachtvariante
ACT e activation parameter for night option
285
EN4402EN00EN_0003
© 2004 Siemens AG
37.9 Extend Call to Paged User
37.9.1 Overview
The requirement of this feature is to allow the Attendant to connect a caller in a held state with
a party in talk state via a new function key JOIN
“Telephone Call for Mr X please

call 5000”
A will be Held
Attendant can proceed with normal

call handling while A is held
After the activation of the

join key the waiting party
B
“Join”+subunit key
is connected to the B calls attendant Personal

paged user number
286
EN4402EN00EN_0003
© 2004 Siemens AG
37.9.2 Feature Description

This feature is released for the global market with Hipath4000 V1.0
If the attendant is not able to contact the wanted user at their extension. The attendant either
places the calling party on hold, or parks the calling party, and pages the wanted user.When
the wanted user calls the attendant (Personal key) and the attendant accepts the call, then the
attendant is able to join the calling party and the wanted party by pressing the JOIN key and
then selecting the held or parked calling party. The call is then automatically released from the
attendant as a 2 party call
37.9.3 User Interface

The Extend Call to Paged User feature can be used by the attendant to join a call that is either
held at the T, O or R (recall)sub-units or parked, with a paged user who calls into the attendant
P sub-unit.(Personal Key) The two parties are connected following depression of the JOIN key
and then selection of the relevant held or parked party.
This feature is available network-wide.
It is envisaged that this feature will be utilized by the attendant for the following scenarios
After a transferred call to a user has not been answered and the call has recalled to the
attendant. The attendant then has the option to page the wanted user
An internal user may not be able to contact a user at their extension and request assistance
from the attendant.
The attendant has the option of extending any call received at the P sub-unit (Personal key) to
any held or parked call at the other sub-units.(Trunk key, Attendant key or Parked call).
37.9.3.1 Extend Call to Paged User Feature Invocation from AC

The following description is applicable to:-
AC4 on Upoe interface
There are two states that the incoming call can be in while the Attendant waits for the response
to the paged call, these being held at the T, O or R sub-unit, which is described in case 1 below;
or parked which is described in case 2 below.
Case 1 - Held Call
The incoming call is on hold at either the T,O or R sub-unit.A call held at either the T or R sub-
unit is interchangeable.
The attendant pages the desired extension and carries on with normal call handling
287
EN4402EN00EN_0003
© 2004 Siemens AG
The returned paged call arrives at the P sub-unit (Personal Key) of the Attendant, and the P
sub-unit key will be flashing, the Attendant has an indication on the display of the waiting call
against the P in the display, in addition to alerting tone
The Attendant accepts the incoming call by depressing the P key. The associated LED is now
lit, and the Attendant display changes to show the calling party number and CONNETED.
The Attendant now depresses the JOIN key, the JOIN LED is lit and the Attendant now selects
the sub-unit which is to be joined to the call on the P sub-unit (E.G. the T Key), by depressing
the T key. The two parties are now joined together and released from the Attendant.The Atten-
dant display returns to normal
Case 2 - Parked Call
The incoming call is parked, the hold led is lit.The returned paged call arrives at the P sub-unit
(P Key) of the Attendant, and the P key led will be flashing, the attendant display shows the
calling party, the Attendant accepts the call by pressing the P key and the P key led is lit
steady.The attendant now presses the JOiN key and the JOIN led is lit and the AC display
shows connected.The park key is pressed and the park position which is to be “joined” to the
call on the P sub-unit is selected.The two parties are connected together and the calls are re-
leased from the attendant, where the display returns to normal.
37.9.3.2 Extend Call to Paged User Feature Invocation from AC-Win

The principle behind the feature invocation for ACWin and ACWinMQ Upoe is the same as that
for AC4.
The returned paged call to be joined arrives at the P sub-unit of the Attendant. An indication
associated with the P sub-unit is shown. The Attendant can join a call received at the P sub-
unit to a held call at either the T, O or R sub-units, or a parked call.
The new JOIN key will reside in the AC-Win Buttons window.
The incoming call (returned paged call) will appear in the AC-Win Call Control window.
When the attendant accepts the incoming call, it will be shown as CONNECTED in the AC-WIN
Call Control window. The call to be JOINed can be held at either the T, O or R sub-units, or
parked.
For held calls, the attendant clicks the JOIN key in the AC-Win Buttons window, or uses the key-
board, and then selects the sub-unit key (where the calling party is held) in the AC-Win Call
Control window, both calls are now connected and released from the attendant.
For parked calls, the attendant clicks the JOIN key in the AC-Win Buttons window and then ei-
ther double clicks to the call in the PARK window, or single clicks to the park position and then
presses RECONNECT on the keyboard, the 2 parties are now connected and released from
the attendant.
288
EN4402EN00EN_0003
© 2004 Siemens AG

The feature is an integrated S/W solution.
After the JOIN key has been pressed, only the following keys will appear active to the user:-
JOIN key again to toggle between on/off,
RELEASE (CLEAR REQUEST) key - to deactivate the JOIN key and release the call on
the active subunit.
NIGHT SERVICE key - to activate/deactivate the blocking of the attendant console for new
incoming calls. JOIN remains active
TAPE RECORDING key - to activate/deactivate tape recording. JOIN remains active
FUNCTIONAL 1 key - to activate/deactivate the call trace. JOIN remains active,
HANDSET PLUG OFF for blocking the AC, JOIN will be deactivated
All Voice Subunit key’s (except that active - to execute JOIN)
After JOIN and PA-Subunit key the attendant can select a park position (0-9) or exit the
park menu by pressing the CHECK key.
All other keys will appear none functional to the user.
37.10 Remote Activation of Call Forwarding for Station Users at the

Attendant Console
37.10.1 Overview
Variable call forwarding (FWD) can be activated or deactivated for any station (forwarding ob-
ject) in the network at the attendant console (ATND). The call forwarding destination can be any
call forwarding destination which the station user would normally be allowed to activate.
To begin with, you must assign the digit analysis results for remote activation (AFWDATND) and
remote deactivation (DFWDATND) of call forwarding at the attendant console with the WABE
AMO.
In order to enable the remote activation and deactivation feature, you must specify the COT pa-
rameter CFOS for both the incoming and outgoing digital tie lines in the path between the ATND
and the telephone for which remote FWD activation is to be allowed. The connection path be-
tween ATND and forwarding object must be set up with LCR.
289
EN4402EN00EN_0003
© 2004 Siemens AG

To perform remote FWD, the ATND must have the COS FWDFAS. COSSU AMO is used for the
administration of the COS.
The function is for DQ and MQ variants possible.
37.10.3 Generation example

● Assign digit analysis results:
AD-WABE:CD=<code for AFWDATND>,DAR=AFWDATND,CD2=<code for DFWDATND>;
● COT parameters for enabling remote FWD:
CHA-COT:COTNO=<COT_number>,COTTYPE=COTADD,PAR=CFOS;
● COT parameters for disabling remote FWD:
CHA-COT:COTNO=<COT_number>,COTTYPE=COTDEL,PAR=CFOS;
37.10.4 Relevant AMOs

Language
COT COTPAR d PARAMETERWERTE FUER EINE COT
AUAT = PROGRAMMIERUNG DER ANRUFUMLEI-
TUNG FUER ANDERE TLN MOEGLICH
PAR e PARAMETER VALUES OF A COT
CFOS = CALL FORWARDING PROGRAMMING
FOR OTHER SUBSCRIBERS
WABE KZP d KENNZAHLPUNKT
AULEREM = ANRUFUMLEITUNG EINSCHALTEN
REMOTE/FOLLOW ME
DAR e DIGIT ANALYSIS RESULT
AFWDREM = ACT CALL FORWARDING REMOTE/
FOLLOW ME
290
EN4402EN00EN_0003
© 2004 Siemens AG
37.11 Attendant Control of Diversion
37.11.1 Overview
The feature ’Control of Diversion’ offers the operator (using ACWin MQ) a convenient method
to control a diversion (Call Forwarding Unconditional - CFU often referred to as call forwarding
immediate CFI)
Ring
AC-Win M Q Call Forward

Unconditional
Applikat ion
Statistische Daten
Siemens Bellavist a Telefonbuch V1.0
N amen:Liste
Name: OK
Vorname: Abbrechen
Abt eilung:
Rufnummer:
Fax:
C:\
( immediate )
Programmanager
Step
37.11.2 Feature Description

The feature can be enabled or disabled system wide by using settings in AMO ZAND and set
into operating mode per attendant group by AMO VFGR. If active for the attendant group the
operator, when encountering a diversion, is informed and can choose to follow the diversion or
override it by the use of the buttons STEP or RING. If the feature is enabled in the system but
not enabled for the attendant group then the operator has to press the DES key prior to calling
a station with call forward immediate set i.e. the STEP and RING keys do not appear automat-
ically and the attendant has know that the station has CFI set.
The feature works on different types of extensions, analog, digital and functional devices are
supported
291
EN4402EN00EN_0003
© 2004 Siemens AG

The feature ’Control of Diversion’ controls CFB and CFU only, not CFNR (Call Forwarding No
Reply).
If the called extension has ICF (Interactive Call Forwarding) activated, no control of diversion is
possible.
If the called extension has a diversion to a call centre activated, no control of diversion is pos-
sible.
The feature works network wide only from Hicom HV1.0/Hipath4000 V1.0 and Realities/DX
over CorNet NQ or CorNet NQ/DPNSS1.
The feature works for transit traffic over HICOM (older version) with CorNet NQ.
For other digital or analogue trunks a control of diversion is not possible. The call follows the
diversion.
37.11.4 AMO Usage

● To enable or disable the feature the AMO ZAND is used:
CHA-ZAND:TYPE=ATND,COD=<YES/NO>;
If the feature is disabled a call always follows an existing diversion. The CoD buttons are without
any function. The exception is if a loop subunit is reserved (’In Use’ is displayed) and before the
first digit is dialed, the reaction for the DES button is that ’NOT POSSIBLE is displayed.
● If the feature in enabled, it can operated in 2 different operation modes, depending on the
selection in AMO VFGR:
CHA-VFGR:ATNDGR=<nr>,TYPE=GENERAL,COD=ON;
With this setting the feature is enabled permanently. For each extension with a diversion (CFU
or CFB) a decision to STEP or RING is necessary when it is requested. The DES button is with-
out any function.
CHA-VFGR:ATNDGR=<nr>,TYPE=GENERAL,COD=OFF;
With this setting the feature is enabled temporary and the operator has to use the DES button
to activate the feature for next call before dialing is started. Toggling is possible in this state.
The information ’DES ACTIVE’ is displayed or removed from the call control window. If the di-
aled extension has CFU or CFB activated, so the available information about the extension and
diversion is displayed and the operator has to decide to follow (STEP button) or override (RING
button) the diversion.
292
EN4402EN00EN_0003
© 2004 Siemens AG
37.11.5 Relevant AMOs

Language
ZAND AULSTEU d Kontrollierte Anruflenkung in der Anlage
aktiviert
COD e Control of diversion enabled for the sys-
tem
VFGR AULSTEU d Kontrollierte Anrufumlenkung automatisch
setzen J/N
COD e Control of diversion set automatically Y/N
Tabelle 37-1
293
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Least Cost Routing (LCR) Siemens
38 Least Cost Routing (LCR)
In this chapter:
a) the key terms are defined;
b) the “classical” LCR-AMOs are explained;
c) the “classical” call processing LCR-sequences (no generic sequences) are
elucidated excluding special control mechanisms.
38.1 General Definition of the Term LCR

The generally used appellation Least Cost Routing (LCR) points out, that a private branch ex-
change comprises the ability to optimally control the channel selection for a connection. There-
fore, LCR is often referred to as “take the cheapest path”.
The digits dialed by the calling party must, essentially, fit into a system defined digit pattern
(AMO LDPLN). This results into a direction allowing several path alternatives to the called par-
ty (AMO LDAT). Depending on the chosen path, the dialed digits may be, subsequently, ma-
nipulated with the LCR dialing rules (AMO LODR). Additionally, the choice of the directions to
be seized resp. the route alternatives can be controlled. The subscriber data of the calling party
are used for controlling (LCOS (LAUTHs)), ITR group, DPLN group, Source group).
Searching a free port is handled either once during call set up or repeatedly based on wait loop
control. A set is seized only after a complete check of the dial plan. Receiving a congestion sig-
nal of the partner switch does not necessarily result in an abortion of the call setup. In case of
rerouting another path is determined to the desired destination, if available. Call setup is con-
tinued via this path.
External calls are routed to the private node, which is located closest to the destination. This is
only reasonable, if the destination can be found within the local exchange area of a node in the
private net. This results in an cost optimized Central Office Breakout.
294
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Least Cost Routing (LCR)
38.2 The Most Important Definitions
38.2.1 Node Numbers

General
From SP300E-V1.0 on the node number has been hierarchically structured. A net may contain
up to three levels resulting into, maximal, three-stage node numbers. The presentation on the
AMO-surface is (except for AMO KNMAT) aa-bbb-ccc. This reads:
aa = Level 2 (domain) area number (0-29)
bbb = Level 1 (sub domain) area number (0-253)
ccc = Level 0 (node) node number (0-999)
A multilevel node number is deemed to be unique, if it differs at least at one level from all other
node numbers. The number 0 of the lower levels means “any” (e.g. 2-0-0). Leading zeros may
be omitted
(e.g. 0-0-2 = 2).
Physical Node Numbers
A physical node number is assigned to every node (HiPath 4000). This node number must be
unique within the net and defines the PABX. The number is entered in the central equipment
data (AMO ZAND, parameter PNNO).
It is the basis for the automatic determination of the network topology (AMO KNTOP) and for
generating the Call IDs and Leg IDs (charge recording).
Virtual node number
A virtual node number characterizes a node with all its subscribers and operator consoles.
AMO SDAT defines, which node a sub or a console is assigned to.
At least one virtual node must be defined within a physical node. This may well extend over
several physical nodes or could be one of many virtual nodes within the same physical node.
Virtual node numbers are managed in a separate table with AMO KNDEF, Type=OWN and
must differ from the physical node number. This applies to alternate routing (LCR) and display
number modification.
295
EN4402EN00EN_0003
© 2004 Siemens AG
● Example for node number definition:
32072 +49 30 3687 - X
HiPath 4000
1-30-100
Virtual node
ISDN
32073
1-30-100
OWN
1-30-100 +49-30-3687-32072 +49 89 722 - X
AMO KNDEF
42113 Virtual node
Munich
1-89-160 43113
IPDA
OWN
1-89-160 +49-89-722-42113
Berlin 1-89-160
Physical node: 10-30-100 (AMO ZAND: ALLDATA)
Interrogation of the AMO KNDEF

Virtual Node Table
+-----------+-------+--------------+--------------+-----------+-----+-----+----+
| VIRTUAL | TYPE | ISDN (E.164) | PRIVATE(PNP) | UNKNOWN |POPU-| CAC |DFLT|
| Node- | | CC | L2 | | LA- | PRE-| |
| NUMBER | | AC | L1 | KNOTEN- |TION | FIX | |
| | | LC SK | L0 SK | KZ SK | | | |
| | | UL | UL | | | | |
+===========+=======+==============+==============+===========+=====+=====+====+
|1- 30-100 |OWN | 49 | | | 58| | Y |
| | | 30 | | | | | |
| | | 3687 4 | | | | | |
| | | EXT | EXT | | | | |
+-----------+-------+--------------+--------------+-----------+-----+-----+----+
|1- 89-160 |OWN | 49 | | | 10| | |
| | | 89 | | | | | |
| | | 722 3 | | | | | |
| | | EXT | EXT | | | | |
+-----------+-------+--------------+--------------+-----------+-----+-----+----+
Station Numbers
296
EN4402EN00EN_0003
© 2004 Siemens AG
Referring to called number, in HiPath 4000 we distinguish between:

a) two numbering plans (closed or open), which entail different LCR-sequences.
b) three types of numbers (Unknown, ISDN and PNP (Private)) for each numbering
plan
Dialing Station Number
e.g. 45000
Open Numbering:
The first field is entered in
Closed Numbering: WABE as DAR=TIE (break-
out);
The called number is entered in
WABE as DAR=STN resp.
DAR=NETW; e.g. 0-722-45000(Local) e.g. 0-567-45000(Local)
0-089-722-45000(Nat.) 0-034-567-45000(Lev1)
0-0049-89-722-45000(Intern.) 0-0012-34-567-45000(Lev2)
e.g. 91-45000
Only the Type of The station num- The ISDN Number of The PNP Number
Number UN- ber (45000) of the the called party follows of the called party
KNOWN contains called party fol- the exit code (e.g. 0) at follows the exit code
closed numbered lows the exit code one of the three possi- (e.g. 0) at one of the
station numbers. (91) in the Num- ble levels (LOCAL, NA- three possible lev-
bering plan UN- TIONAL, or INTERNA- els (LOCAL, LEV-
KNOWN. TIONAL) in the ISDN EL 1, or LEVEL 2)
This type of num- Numbering plan. in the PNP Num-
ber is to be used These three level codes bering plan. These
within the HiPath are standardized three level codes
4000 network (fixed). are arbitrary.
only. The own tie This type of number This type of number
code is generally may be used within the is to be used within
inscribed as network but also for the network only.
DAR=OWN- the public network The prefixes (L1)
NODE in the (central office). and 00 (L2) are
WABE. The prefixes 0 (Nat.) usually not to be
and 00 (Intern.) are sent.
usually not to be sent.
297
EN4402EN00EN_0003
© 2004 Siemens AG
38.2.2 Number Modification

Generally (without using special control mechanisms) the HiPath 4000 tries to shorten both
the Called number and the Calling number (display) as far as possible. The aim is achieved,
if the called number terminates on DAR=STN in the own node. Otherwise the call is in a transit
situation and the sequence for leaving the transit node starts again. The reduction mechanisms
are dependent on the numbering type and the numbering plan. For this purpose the AMOs
WABE, KNMAT, KNPRE and KNDEF may be used.
The following table reveals the correlation of the reduction mechanisms:
numbering type AMO description

Closed Numbering no mechanism Sending only the extension, either direct-
(UNKNOWN only) necessary ly reaches the destination in the partner
node (extension of the own node) or it
leads to a DAR=STN in an external node
(transit cause). The latter results in an-
other sequence leaving this node.
Open Numbering WABE WABE evaluates the called number
UNKNOWN KNMAT (e.g. 91-45000) in the partner node. If the
destination is located in the partner node,
the own DAR=TIE can be found as
DAR=OWNNODE in the WABE. This
causes the number to be shortened and
induces a re-evaluation of the rest (ex-
tension number). If the partner node is a
transit system, the call is evaluated again
in AMO WABE as a DAR=TIE. The latter
results in another sequence leaving the
node.
The own DAR=TIE is added to the call-
ing number by AMO KNMAT.
298
EN4402EN00EN_0003
© 2004 Siemens AG
open numbering ISDN KNDEF The called number (e.g. 89-722-45000

KNPRE (national)) is compared with the entries in
AMO KNDEF, column ISDN of the part-
ner node and shortened in case of con-
sistency. The end is reached, if reduction
is possible down to the extension (rest
leads to DAR=STN of the own node in
AMO WABE). If reduction is not possible
down to the extension prefix and exit
code of the transit system must be
added to the called number. This is ac-
complished by AMO KNPRE, branch IS-
DN.
(89-722-45000 -> 0-089-722-45000) The
calling number is processed by the
same mechanisms (KNDEF and KN-
PRE).
open numbering PRI- KNDEF The called number (e.g. 34-567-45000
VATE KNPRE (LEVEL 1)) is compared with the entries
in AMO KNDEF, column PRIVATE of the
partner node and shortened in case of
consistency. The end is reached, if re-
duction is possible down to the extension
(rest leads to DAR=STN of the own node
in AMO WABE). If reduction is not possi-
ble down to the extension prefix and
exit code of the transit system must be
added to the called number. This is ac-
complished by AMO KNPRE, branch
PRIVATE.
(34-567-45000 ->0-034-567-45000)
The calling number is processed by the
same mechanisms (KNDEF and KN-
PRE).
299
EN4402EN00EN_0003
© 2004 Siemens AG
38.3 Brief Description of the AMOs which are Used for the
Call Processing LCR Sequences
AMO description
BERUM determination of the active COS and LCOS (1 or 2) of the calling party
BUEND defines trunkgroups within the system; trunks (TDCSU) are assigned to every
trunkgroup, which can be seized
KNDEF determination of the virtual node data
KNMAT adding the own DAR=TIE to the calling number;
conducted in the originating equipment in conjunction with open numbering
UNKNOWN;
the entries are origin- and destination node dependent
KNPRE adding prefix and exit code to called and calling number, if necessary;
conducted in conjunction with open numbering ISDN and PRIVATE
LDAT LCR file:
places all route alternatives of a selected route for an LCR-subscriber;
every trunkgroup entry is provided with a lock, the subscriber needs a key
(LAUTH) to seize a trunkgroup;
additionally every trunkgroup entry is assigned a dialing rule (ODR) from the
AMO LODR, defining the actual dial information on the trunk.
LDPLN LCR Dialing Plan:
provides the digit pattern for open numbering;
when dialing with exit code, the evaluation is based on the digit pattern with
maximum accordance.
DPLN-examples:
91-X (digit pattern with 2 ECHO FIELDS)
0-W-722-X (digit pattern with 4 ECHO FIELDS)
0-W-0-89-722-X (digit pattern with 6 ECHO FIELDS)
0-W-00-49-89-722-X (digit pattern with 7 ECHO FIELDS)
after dialing “0”, the echo field W results in the insertion of the dial tone.
LODR LCR out dialing Rule:
defines dialing rules, i.e. defining the actual dial information on the trunk;
the dialing information is deduced from the structure of the digit patterns used
with open numbering (q.v. LDPLN with echo fields);
only one echo field is existing for closed numbering (echo field 1);
additionally, the type of number (Unknown, ISDN or PRIVATE) and the sent lev-
el are defined.
300
EN4402EN00EN_0003
© 2004 Siemens AG
LPROF defines LCR profiles subject to the source group number of the calling party.
Based on different SRCGRP, subscribers with the same digit pattern (AMO LD-
PLN) can be routed to different LCR routes (LRTEs);
this control mechanism is valid for open numbering only
LSCHD defines maximum 8 periods (A-H) for the seizure of trunkgroups in AMO LDAT;
the corresponding tables are dependent on the ITR groups.
RICHT defines the route (LRTE), which is selected for leaving the node when dealing
with closed or open numbering;
provides all trunkgroups which can be accepted in AMO LDAT
an LCR subscriber leaves the node via AMO LDAT not via AMO RICHT
SDAT determines the needed data of the calling party (COS1 or 2 / LCOSx 1 or 2 /
WABE group / ITR group / NNO / SRCGRP).
TDCSU sets up digital trunks (S0 and S2) which are related to a trunkgroup.
WABE inscribed DARs dependent on the type of numbering:
closed Numbering.: STN, NETW, NETRTE;
Open Numbering.: TIE (central office), OWNNODE;
ZAND determines the physical node number of the system
Who is who in LCR?
LAUTH LCR individual class of service for the route / the dialling plan
LCOSV class of service packet for LCR (voice & FAX) containing n LAUTHs
LCOSD class of service packet for LCR (DATA) containing n LAUTHs
LDAT LCR route;
containing all trunkgroups which may be used for this route.
1. LAUTH authorization for the selected route (trunkgroups)
2. dialing rule for this trunkgroup
3. attributes of the periods A-H (free / expensive / restricted)
4. determination of network operator and zoning (charge recording)
sequence of seizure:
1. low priced providers in the sequence of entry
2. high priced providers in the sequence of entry
NWLCR LDAT table for closed numbering plan
LCR LDAT table for open numbering plan
CD RICHT entry for a closed numbered route
301
EN4402EN00EN_0003
© 2004 Siemens AG
38.4 “Classical” Call Processing LCR Interrogation Sequences
38.4.1 Collecting General, Dialing Independent Information
calling party data (7100):
TLN: 7100 AMO SDAT:

COS 1/2:
the LCR generation routes the call in case the COS holds the au-
thorization TA (i.e. its LCOS is active).
LCOS 1/2:
shows its authorization key (LAUTHs) for leaving the PABX.
ITR:
shows its traffic relation group.
DPLN:
shows its DPLN group.
SRCGRP:
shows its source group.
NNO:
shows the virtual node number of the subscriber.
determination of the active COS (LCOS) 1 or 2:

AMO BERUM
PABX
system data (PABX):
AMO ZAND:ALLDATA
PNNO:
physical node number of the system
AMO KNDEF:
characteristic data of the virtual system the A subscriber is
assigned to (q.v. SDAT parameter NNO).
302
EN4402EN00EN_0003
© 2004 Siemens AG
38.4.2 NWLCR Closed Numbering Plan UNKNOWN

Dialling information outgoing: 7240
Tip:
Cursively marked parameters

1) DISP-WABE:TYPE=GEN (in italics) are for further use!
,CD=7240;
CD 7240
DAR STN
DESTNO 0 -> own node
>0 -> external node 2) DISP-RICHT:MODE=CD,SVC=VCE,DNNO=?
DNNO ? MODE CD
3) DISP-WABE:TYPE=GEN,CD=? CD ?
CD 200 LRTE ?
DAR NETRTE TRGP
SVC
DNNO
4) DISP-LDAT:LRTE=? DESTNO
LROUTE 1 2 3
schedule (A-H) 6) DISP-LSCHD:ITR=# of calling number
LAUTH output of the used
schedules for STN of this
TGRP ? ? ?
ITR-group
ODR ? ? ?
labels in the schedule field:

* -> disposable trunkgroups in the
schedule
- -> blocked trunkgroups in the schedule
E -> trunkgroup, labeled to be expensive
in the schedule
5) DISP-LODR:LWR=?
ODR
CMD echo 1 7) DISP-BUEND:TGRP=?
CMD NPI UNKNOWN output of the
UNKNOWN
ports (PENs)
CMD TON
CMD END 9) DISP-SDSU:............
status of the
ports
8) DISP-TDCSU:PEN=?
PEN
303
EN4402EN00EN_0003
© 2004 Siemens AG
38.4.3 LCR Open Numbering Plan

Dialling information outgoing
e.g. ISDN national: 0-089-722-7240
Tip:
Cursively marked parameters

1) DISP-WABE:TYPE=GEN,CD=0; (in italics) are for further use!
CD 0
DAR NETWl
at breakout the dialling
information undergoes a 3) DISP-LPROF:PROFIDX=?
subsequent evaluation in SRCGRP
AMO LDPLN; according to
SRCGRP of the
2) DISP-LDPLN:TYPE=CD,CD=00897227240 calling party
PROFIDX ? LRTE
or LROUTE ?
corresponding to the 3) DISP-RICHT:ART=LRTE,LRTE=?
DPLN-group of the MODE LRTE
calling party
LRTE ?
LDP 0-W-0-89-722-x
TRGP
4) DISP-LDAT:LRTE=? SVC
LROUTE 1 2 3 DNNO
schedule (A-H) 6) DISP-LSCHD:ITR=# of calling number

LAUTH output of the devoted
TRGP ? ? ? schedules for STN of this
ITR-group
ODR ? ? ?
labels in the schedule field:
* -> disposable trunkgroups in the
schedule
5) DISP-LODR:LWR=? - -> blocked trunkgroups in the schedule
E -> trunkgroup, labeled to be expensive
ODR in the schedule
CMD echo 4
CMD echo 5 7) DISP-BUEND:TRGP=?
CMD echo 6 output of the
ports (PENs)
CMD NPI ISDN
9) DISP-SDSU:............
CMD TON NATIONAL
status of the
CMD END 8) DISP-TDCSU:PEN=? ports
PEN
304
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Configuration of a subscriber Siemens
39 Configuration of a subscriber
39.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
305
EN4402EN00EN_0003
© 2004 Siemens AG
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
306
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Configuration of a subscriber
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)
307
EN4402EN00EN_0003
© 2004 Siemens AG
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
308
EN4402EN00EN_0003
© 2004 Siemens AG
39.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.
309
EN4402EN00EN_0003
© 2004 Siemens AG
39.3 Configuration of an optiset/optiPoint Adapter

An optiset resp. optiPoint 500 can use different adapters, which are connected on the bottom
side of the main device. They are used to connect one or two more devices. Devices, which are
connected via an adapter are configured in principle like the main device. Additional resp. other
parameters will be shown in the next part.
39.3.1 ISDN-Adapter
Attention: special COS-authorization for

DSS1-subscriber!
310
EN4402EN00EN_0003
© 2004 Siemens AG
39.3.2 Phone-Adapter
Attention: If you do not select special COS/

LCOS-group the COS/LCOS-group of the
main device is used.
311
EN4402EN00EN_0003
© 2004 Siemens AG
39.3.3 Analog-Adapter
Attention: If you do not select special COS/

LCOS-group the COS/LCOS-group of the
main device is used.
312
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Deletion of a subscriber
40 Deletion of a subscriber
313
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: optiClient 130 V5.0 Siemens
41 optiClient 130 V5.0
41.1 Description
The optiClient 130 V5.0 is the succession product of the Version V2.5 for the HiPath 4000 V2.0
and the HiPath 3000. It supports the feature Direct Media Connection (DMC) and is connected
to a STMI2 board. The used protocol is HFA.
41.2 Installation and Settings

In this document only the basic steps are described. For detailed information please use the
Administration resp. User manual.
The installation will be started with the Setup.exe file. Then follow the menu of the installation
routine.
After starting the optiClient 130 V5.0 on the PC, the following settings and entries are required.
.
1.
2.
3.
314
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: optiClient 130 V5.0
If an user ID is added without a password, the login window will not be display-
ed for future starts of the client. To get the login window, e.g. to change set-
tings, it is necessary to press the Shift-key during the client boot.
3.
315
EN4402EN00EN_0003
© 2004 Siemens AG
Select the desired Audio-Scheme and move it to the

upper position.
316
EN4402EN00EN_0003
© 2004 Siemens AG
In this menu it is possible to integrate features as function keys in the menu

bar.
The phone interface with the first 4 Defines the number of extended key
function keys, extended key pad with 8 pads, which should be displayed in the
function keys and up to 2 additional key optiClient:
pads (add on devices) are fixed integra- 1 = only extended key pad with
ted in the mainbar or can be positioned 8 function keys;
unrestrictedly. 2 = extended key pad with 8 function
keys and the first add on device;
3 = extended key pad with 8 function
keys and both add on devices;
317
EN4402EN00EN_0003
© 2004 Siemens AG
Extension number of the optiClient from AMO WABE and

SBCSU.
User password from AMO SBCSU,Parameter=IPPASSW
IP addresse of the STMI2 board from AMO HFAB.
Type options are HiPath 3000 resp. HiPath 4000.
318
EN4402EN00EN_0003
© 2004 Siemens AG
Settings of the Central Office (CO) access:
319
EN4402EN00EN_0003
© 2004 Siemens AG
Only the function keys F2 up to F11 of the PC can be used!
320
EN4402EN00EN_0003
© 2004 Siemens AG
41.3 Generating of the optiClient 130 V5.0 in the HiPath 4000 V2.0
10. Define the number of STMIHFA2 boards:
ADD-DIMSU:TYPE=SYSTEM,STMIHFA2=xx;
11. Define the number of optiClients:
CHANGE-ZAND:TYPE=CIT,APIMAX=xxx;
ADD-DIMSU:TYPE=APPLICAT,WSPROT=xxx;
(the same value xxx is to set in both AMOs !)
12. Activate the feature Direct Media Connection (DMC) system wide:
CHANGE-DIAGS:PROCID=CC,COMP=CP2,S08=OFF;
13. Add the STMI2 board:
ADD-BCSU:MTYPE=PER,LTG=1,LTU=2,SLOT=25,PARTNO=Q2316-x/Q2316-x10,
FCTID=3;
ADD-HFAB:MTYPE=STMIHFA2,LTU=2,SLOT=25,SMODE=NORMAL,
IPADDR=1.40.31.70,NETMASK=255.255.255.0,DEFRT=1.40.31.254;
14. Add the optiClient 7375 with TAPI:
ADD-SBCSU:STNO=7375,OPT=OPTI,CONN=IP2,PEN=1-2-25-0,
DVCFIG=OPTIIP&API,COS1=33,COS2=30,LCOSV1=9,LCOSV2=1,LCOSD1=9,
LCOSD2=1,DPLN=0,ITR=0,COSX=0,SPDI=30,REP=1,STD=101,SECR=NO,
INS=YES,HEADSET=NO,HSKEY=NORMAL,TEXTSEL=ENGLISH,
CALLOG=TRIES,APICLASS=TSX,IPPASSW=xxxxxxxx,IPCODEC=G711PREF;
For using the HiPath 4000 Headset, the parameter HEADSET= WITHIND is to be
set.
If a user password is set in the “HiPath-Provider “ settings, this password must be
set in the parameter IPPASSW.
321
EN4402EN00EN_0003
© 2004 Siemens AG
15. Activate the authorization for Direct Media Connection (DMC) for the subscriber:
CHANGE-SDAT:STNO=7375,TYPE=ATTRIBUT,AATTR=DMCALLWD;
322
EN4402EN00EN_0003
© 2004 Siemens AG
323
Using the right mouse key in the main bar, the following functions can be selected:
41.4
Siemens
It is not possible to make basic changes in the “Setting-Menu”, like extension

number, Gatekeeper, Audio settings etc.. Do you want to make such changes,
the “Setting-Menu” has to be activated during the program start.
Administration: optiClient 130 V5.0
© 2004 Siemens AG
EN4402EN00EN_0003
Short description of the user interface of the optiClients 130 V5.0
© 2004 Siemens AG
EN4402EN00EN_0003

Using the fuction button, the extended key pads (additional 8 function key pad, and the add on modules, if
configured in the HiPath 4000) resp. the callog resp. the internal phone book are shown:
Siemens
324
325
Extended key pads. The add on modules can be fade inr or fade out with the arrows. Siemens
© 2004 Siemens AG
EN4402EN00EN_0003
© 2004 Siemens AG
EN4402EN00EN_0003

Key descriptions can be changed individualy (use the right mouse key on the desired key):
Siemens
326
327
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Relevant AMOs Siemens
42 Relevant AMOs

Language
SBCSU GERKON d OPTIIP Sprachterminal IP (optiPoint 400/410//600 und
optiClient 130)
DVCFIG e OPTIIP digital voice terminal IP (optiPoint400/410/600
and optiClient 130 )
ANSCHL d IP, wenn an STMI, IP2, wenn an STMI2 angeschlossen
CONN e IP, if connected to STMI; IP2, if connected to STMI2;
TAWL d Ausweisleser vorhanden
IDCR e station with identity card reader
TAPRO DIGTYP d OPTIT8 (optiPoint 410 entry), OPTIT12 (optiPoint 410
eco / standard), OPTIT18 (optiPoint 410 advance SLK),
OPTIT19 (optiPoint 410 advance)
DIGTYP e OPTIT8 (optiPoint 410 entry), OPTIT12 (optiPoint 410
eco / standard), OPTIT18 (optiPoint 410 advance SLK),
OPTIT19 (optiPoint 410 advance)
ZAND: V2RUFKLG d Initalisierungswert für optiPoint Rufklangfarbe
Optiset
V2RINGSO e Initial value for optiPoint 500 ringer sound

AUSGBKON d Initalisierungswert für optiPoint Ausgabe Kontrast.
DISPCONT e Initial value for optiPoint Display Contrast.
ROLLLAUT d Initalisierungswert für Rollover-Laut.
ROLLVOL e Initial value for rollover ring volume
RFOUEB d Rückfrage ohne Uebergeben durch Einhängen
CONSONLY e Consult Only
HAMESCR d Ein/ausschalten 'Hauptmenu ueber Scrolltasten'
MAMESCRL e Act/deact system option 'Mainmenu by scrollkey
SRVANRUF d Ein/ausschalten 'Kein Servicemenue bei aktivem
Lautsprecher'
MAMESCRL e Act/deact system option 'Mainmenu by scrollkey'
PICKOPT d Ein/ausschalten 'Pick oder Pick-Pick '
328
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration: Relevant AMOs

Language
PICKOPT e Act/deact system option 'pick or pick-pick mode'
ATONNULL d Aufmerksamkeitston kann null sein
ATONZERO e Alerttone volume can be set to zero
329
EN4402EN00EN_0003
© 2004 Siemens AG
Administration: Siemens
42.1 Terminal settings for optiPoint 410 entry
42.1.1 Entering the administration area

edg Press the keys simultaneously
The status of all 8 LEDs should be ON
o Enter admin password (default: 123456 -> see 91 in original)
r Terminate the operation.
You are now in the Administration Area (All 8 LEDs flash).
The top two function keys take over the following functions in this
area:
1st Function key
<PROG> Press key to make settings.
2nd Function key
<View> Press key to view settings.
42.1.2 Only if no DCHP-Server
Change to the Administration Area.
<PROG> Press key (Key 1).

ddd Enter code to switch the DHCP IP assign off.

de Enter code.
o Enter IP-Adresse of the optiPoint 410 entry (to edit see -> page
93 in original)
330
EN4402EN00EN_0003
© 2004 Siemens AG
Siemens Administration:

df Enter code.
o Enter Netzwork mask of the optiPoint 410 entry (to edit see ->
page 93 in original)

dg Enter code.
o Enter Default Route of the optiPoint 410 entry (to edit see -> page
93 in original)
42.1.3 Working in a virtual LAN (VLAN)

fid Enter code to define the manual configuration of the VLAN
Discovery Mode.

fh Enter code.
o Enter (0 - 4095) for the Virtual LAN ID -> page 80 in original ((to
edit see -> page 93 in original)
331
EN4402EN00EN_0003
© 2004 Siemens AG
42.1.4 Other settings

All other settings of your optiPoint 410 entry must be made through
the "Web-based Management Tool"
Öffnen Sie Seite „System“ in Ihren Browser und tragen Sie folgende
Parameter ein:
● PBX address
● Station number
● Station password
● System type
Confirm your entries and start the telephone:
mm Enter code.
After the start, the telephone is silent and you can make the other
settings
42.1.5 Administration
There are different ways to make settings for the optiPoint 410 entry.
● Locally on the terminal:
– optiPont 410 entry ---> page 48 in original
● Remote maintenance via LAN:
– Web-based Management Tool -> page 53 in original
– Deployment Tool ((for further information see "Administra-
tion Manual Deployment Tool").
332
EN4402EN00EN_0003
© 2004 Siemens AG
42.1.6 View settings
You can make the system display the important settings of your op-
tiPoint 410 entry.
Change to the Administration Area.
<View> Press the 2nd function key from the top.
o Enter 2-digit code (Table -> page 102 in orginal) for the desired
function.
The settings are displayed through different illuminations of
the LEDs. The table on -> page 99 describes the meaning of the
LEDs.
42.1.7 Restart
Change to the Administration Area
ehk Press keys simultaneously.
or
gir Press keys simultaneously.
o Enter the Administrator password
(default: 123456 -> page 91 in original).
During start-up the LEDs momentarily illuminate in succession.
333
EN4402EN00EN_0003
© 2004 Siemens AG
42.1.8 Reset factory setting

The resetting can lead to the failure of all the functions of the
Atlantic. Ensure that you have all the necessary information for
start up
-> Seite 14 im Original.
For default values, see -> page 95 in original.
Change to the administration menu:

edg Press keys simultaneously.
The status of all 8 LEDs should be ON.
o Enter admin password (default: 123456 -> see 91 in original)
You are now in the Administration Area (All 8 LEDs flash).
flm Press keys simultaneously.
(The status of all 8 LEDs should be ON.)
o Enter the “Factory Reset” Password 124816.
334
EN4402EN00EN_0003
© 2004 Siemens AG
42.1.9 Error messages

The LEDs flash till you switch to the Administration Mode -> page
17 (in original).
LEDs am Telefon: No IP address

The DHCP server cannot assign a terminal IP address -> page 79
(in original).
Possible solution
Check the DHCP server.
No Terminal Mask
The DHCP server cannot assign a terminal screen -> page 79 (in
original).
Possible solution
No Default Route
The DHCP server cannot assign a default route -> page 67 (i.O.)
Possible solution
335
EN4402EN00EN_0003
© 2004 Siemens AG
No IP address is set
DHCP IP Assignment (i.O.) is switched off and there is no terminal
IP address configured.
Possible solution
Activate the DHCP IP assignment -> page 15 (i.O.) .
Enter the terminal IP address -> page 15 (i.O.) .
No Terminal Mask is set

DHCP IP Assignment -> page 68 (i.O.) is switched off and no termi-
nal mask is configured.
Possible solution
Enter the terminal IP address -> page 15 (i.O.) .
No Default Route is set

DHCP IP Assignment -> page 68 (i.O.) is switched off and no default
route is configured.
Possible solution
Enter the default route -> page 15 (i.O.) .
No station number / password

The Number -> page 79 and/or password ->‡ page 79 (i.O.) are not
configured.
Possible solution
Enter station number -> page 16 (i.O.) .
Enter station password -> page 16 (i.O.) .
336
EN4402EN00EN_0003
© 2004 Siemens AG
No network
The telephone cannot find the network.
Possible solution
Check the network cable.
No PBX address
No PBX address -> page 77 (i.O.)
Possible solution
Enter PBX address -> page 16 (i.O.).
PBX does not react

The terminal cannot find the PBX -> page 84 (i.O.).
Possible solution
Check PBX.
Login failed
The PBX No. -> page 77 (i.O.), station No.-> page 79 (i.O.), and/or
station password -> page 79 (i.O.) are invalid.
Possible solution
Change the PBX address -> page 77 (i.O.).

Change the station No. -> page 79 (i.O.).
Change the station password -> page 79 (i.O.).
337
EN4402EN00EN_0003
© 2004 Siemens AG
42.1.10 Status Messages

Quiescent state Administration System error
state
LED = OFF
LED = ON
338
EN4402EN00EN_0003
© 2004 Siemens AG
42.1.11 Binary encoded ASCII table

The table illustrates in which way characters are displayed on the LEDs of the
optipoint 410 entry.
. 0 1 2 3 4 5 6 7 8 9
LED is ON
LED is OFF
339
EN4402EN00EN_0003
© 2004 Siemens AG
42.1.12 Operation codes summary

● Administration area
Function optiPoint 410 entry Refer to

Administration area edg (simultaneous) o r Æ Page 18
● Configurations
<PROG>
<PROG>
Default Route dg o r --> Page 67
DHCP IP Assignment v dd o r --> Page 68
<PROG>
Factory Reset flm (simultaneous) o r --> Page 70
<PROG>
Terminal IP Address de o r --> Page 79
<PROG>
Terminal Mask df o r --> Page 79
<PROG>
VLAN id fh o r --> Page 80
VLAN Method fi o r --> Page 80
● Additional functions

Restart phone ehk (simultaneous)
oder
g ir (simultaneous)
o(Administrator password) r
Start phone <PROG> mm r
340
EN4402EN00EN_0003
© 2004 Siemens AG
42.2 Generating of the optiPoint 410 in the HiPath 4000 V2.0

1. Define the number of STMIHFA2 boards:
ADD-DIMSU:TYPE=SYSTEM,STMIHFA2=xx;
2. Activate the feature Direct Media Connection (DMC) system wide:
CHANGE-DIAGS:PROCID=CC,COMP=CP2,S08=OFF;
3. Add the STMI2 board:
ADD-BCSU:MTYPE=PER,LTG=1,LTU=2,SLOT=25,PARTNO=Q2316-x/Q2316-x10,
FCTID=3;
ADD-HFAB:MTYPE=STMIHFA2,LTU=2,SLOT=25,SMODE=NORMAL,
IPADDR=1.40.31.70,NETMASK=255.255.255.0,DEFRT=1.40.31.254;
4. a) Add the optiPoint 410 entry:
DVCFIG=OPTIIP,COS1=33,COS2=30,LCOSV1=9,LCOSV2=1,LCOSD1=9,
INS=YES,DIGNODIS=YES,TEXTSEL=ENGLISH,CALLOG=NONE,
IPCODEC=G711PREF;
b) Add the optiPoint 410 eco/std/adv:
DVCFIG=OPTIIP,COS1=33,COS2=30,LCOSV1=9,LCOSV2=1,LCOSD1=9,
INS=YES,TEXTSEL=ENGLISH,CALLOG=xxxxx,IPPASSW=xxxxxxx,
IPCODEC=G711PREF;
If the parameter IPPASSW is used, the password has to set in the terminal
(Menu: Configuration -> 02=System).
Activate the authorization for Direct Media Connection (DMC) for the subscriber:
CHANGE-SDAT:STNO=7375,TYPE=ATTRIBUT,AATTR=DMCALLWD;
341
EN4402EN00EN_0003
© 2004 Siemens AG

Administration PDF

Uploaded by

Copyright:

Available Formats

Administration 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

Administration PDF

Uploaded by

Copyright:

Available Formats

What are the steps to generate an optiPoint 410 in the HiPath 4000 V2.0?

What are the steps to generate an optiPoint 410 in the HiPath 4000 V2.0?

What parameters need to be configured when adding an optiPoint 410?

What parameters need to be configured when adding an optiPoint 410?

Siemens Administration

20.5 REGENERATE-COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

29.3 DISPLAY-SDAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

38.1 General Definition of the Term LCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

1 HiPath 4000 Service Access

Common Service Access for all Products

External access is achieved via a virtual

Access to Applications via Port-Server

As a rule the SL100 (SL200) receives an IP address

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 Extended Access Protection (Login)

● New AMO handling

3.1 System Administrator Tasks

3.1.1 Initialised User IDs

3.1.2 Query User IDs

3.1.3 Set New User IDs

3.1.3.1 User Name

3.1.3.2 Authorization Assignment

Rights for normal

previous class: Rights:

The advantages of the new access concept are:

4 AMO authorizations in the HiPath 4000 V2.0

AMO Administration & Maintenance Order CON Console

Bild 5-1 Logging the Administrative Actions in a Hicom System

5.2 Log Book Virtual Memory

5.3 Data Protection

Log book sequence number

P0033 DEV:CON1 TSN:1234 UID:1 NOUN:BUEND TYPE:START TIME:1999-12-31

P0034 DEV:CON1 TSN:1234 UID:1 NOUN:BUEND TYPE:OUTPUT TIME:1999-12-31

P0035 DEV:CON1 TSN:1234 UID:1 NOUN:BUEND TYPE:CONTINUE TIME:1999-12-31

P0036 DEV:CON1 TSN:1234 UID:1 NOUN:BUEND TYPE:END TIME:1999-12-31

Bild 1 Example of a Log Book Output

5.4.1.1 Display Entire Log Book

5.4.1.2 Write Entire Log Book to a File

5.4.1.3 Display with Search Criterion (Query by Example)

5.4.1.4 Display with Specific Text String

5.4.1.5 Display Log Book in Reverse Order

6.1 Switching and Configuration AMOs in the CC

LTG and LTU SLOT CIRCUIT

6.2 BGDAT - Display the Board Table

6.3 Switching AMOs for the SWU

MOD MOD BSSU

PORT PORT FUNSU