OpenScape 4000 V7, Volume 3 - Feature Usage Examples, Service Documentation, Issue 6.

OpenScape 4000 V7 
Feature Usage Examples

Service Documentation
A31003-H3170-S103-6-7620
Provide feedback to further optimize this document to [email protected].
As reseller please address further presales related questions to the responsible presales organization at Unify or at your
distributor. For specific technical inquiries you may use the support knowledgebase, raise - if a software support contract is in
place - a ticket via our partner portal or contact your distributor.
Our Quality and Environmental Management Systems are

implemented according to the requirements of the ISO9001 and
ISO14001 standards and are certified by an external certification
company.

Copyright © Unify Software and Solutions GmbH & Co. KG 02/2019
All rights reserved.
Reference No.: A31003-H3170-S103-6-7620
The information provided in this document contains merely general descriptions or
characteristics of performance which in case of actual use do not always apply as 
described or which may change as a result of further development of the products. 
An obligation to provide the respective characteristics shall only exist if expressly agreed in
the terms of contract.
Availability and technical specifications are subject to change without notice.
Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify Software and
Solutions GmbH & Co. KG. All other company, brand, product and service names are
trademarks or registered trademarks of their respective holders.

unify.com
Contents
Contents
1 Feature Usage Examples - Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

2 Highlights and Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.1 Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.2 Hints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3 AMO Authorizations in the PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.3 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4 AMO Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.3 AMO Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5 Device Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6 DIMSU Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.2.1 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.2.2 Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7 Editing Line Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.2 Adding an Incoming Line Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.2.1 Analog Line Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.2.2 Digital Line Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.3 Adding an Outgoing Line Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.4 Configuring MFC Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.5 Deleting a Trunk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8 Extended Access Protection (Login) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.1 System Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.1.1 Initialized User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.1.2 Displaying User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.1.3 Adding New User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.1.3.1 User Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.1.3.2 Rights Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.1.3.3 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.1.3.4 Limiting unauthorized Logon Attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.1.3.5 Disabling the User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.1.3.6 Disabling the Terminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.1.4 Deleting User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.1.5 Disabling and Enabling User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8.1.6 Changing User ID Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
A31003-H3170-S103-6-7620, 02/2019
OpenScape 4000 V7, Feature Usage Examples, Service Documentation 3
Contents
8.1.7 Configuring Preliminary Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

8.1.8 AMO PASSW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.1.9 Logging MML Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.1.10 Upload of Existing IDs with APS Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.1.10.1 New APS Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.1.10.2 New APS Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.1.11 User forgets password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.2 User Possibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
8.2.1 Opening a Session (login) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
8.2.2 Closing a Session (logout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
8.2.3 Executional Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.2.4 Changing Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.2.5 Forced Password Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.2.6 Displaying all Open Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.2.7 Cancelling and Deleting AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.2.8 Further Important Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
9 Load Behavior of Flash Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
9.2.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
9.2.2 Load Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
9.3.1 CHANGE-ZANDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
9.3.2 DISPLAY-ZANDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.3.3 REGEN-ZANDE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
9.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
10 Loadware Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
10.1 Feature Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
10.2 Configuration (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
10.3 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
11 Logical Partitioning in OpenScape 4000 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
12 Optional Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
12.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
12.2 Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
12.3 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
12.4 Overview of the Assigned Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
13 Partial Digit Analysis TWABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
14 Power Fail Interrupt Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
15 Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
15.1 Assign a route to the Telecommunications Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
15.2 Assign a Route to the Voice Mail Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
15.3 LCR Routes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
16 Recovery of Peripheral Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
16.2 Feature Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
16.3 User Interface: AMO PSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
16.4 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
16.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
A31003-H3170-S103-6-7620, 02/2019
4 OpenScape 4000 V7, Feature Usage Examples, Service Documentation
Contents
16.6 Generation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

17 Subscriber Search Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
17.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
17.2 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
17.3 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
18 System Backup & Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
18.1 Important Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
18.2 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
19 Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
20 Account Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
22 Basic Networking Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
22.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
22.2 Network Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
22.2.1 Meshed network, fully meshed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
22.2.2 Meshed network, partially meshed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
22.2.3 Star-type network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
22.3 Digit Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
22.4 Station Numbers and Codes throughout the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
22.4.1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
22.4.2 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
22.4.3 Generation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
22.4.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
22.5 Physical and Virtual Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
22.6 Node Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
22.6.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
22.6.2 Structure Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
22.6.3 Service Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
22.6.4 Physical Node Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
22.6.5 Virtual Node Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
22.6.6 Fictive Node Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
22.6.7 Originating Node Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
22.6.8 Destination Node Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
22.7 Node Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
22.7.1 Physical Node Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
22.7.2 Virtual Node Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
22.7.3 Area, Area Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
22.7.4 Area Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
22.7.5 Destination System Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
22.7.6 Route Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
22.7.7 Area-Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
22.7.8 Tie Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
22.7.9 Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
22.7.10 Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
22.7.11 Source Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
23 Alternate Routing on Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
23.1.1 Main goals for the alternate routing destination numbers in respect to OOS scenario. . . . . . . . . . . 152
23.1.2 Usage of Alternate Routing Destination Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
23.1.3 Philosophy of loop avoidance in public/ OpenScape 4000/HiPath 4000 network . . . . . . . . . . . . . . 155
A31003-H3170-S103-6-7620, 02/2019
Contents
23.1.4 Philosophy of supplementation (parameter EXTNO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

23.1.5 Implausible conditions for supplementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
23.1.6 Plausibility of alternate routing destination numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
23.1.7 Advisory output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
23.2 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
23.2.1 Called subscribers (A,B,C,D,E of one source group), are not reachable, because of device/board errors
166
23.2.2 Called subscribers (A) is not reachable, because deactivated via AMO with additional request for
alternate routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
23.2.3 Called HFA IP phones (A,B) are not reachable, because of IP errors, they moved their logon location
from OpenScape 4000 to OpenScape Business/HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
23.2.4 Called HFA IP phones are not reachable, because of system failure errors, they moved their logon
location from OpenScape 4000 to another OpenScape 400 (MWI Indication) . . . . . . . . . . . . . . . . 171
23.2.5 Called subscribers (A,B) in its APs are in an APE situation to AP of the calling device . . . . . . . . 173
23.3.1 General plausibility information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
23.3.2 Special restriction information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
23.4 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
23.5 Realization via A&S Tools: Screenshots and additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
23.5.1 Realization via AMO: AMO or AMO Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
23.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
23.7 Frequently Asked Questions (FAQs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
24 Analog Trunking USA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
24.1 Tie Traffic Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
24.1.1 TMEMUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
24.1.1.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
24.1.1.2 Service Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
24.1.1.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
24.1.1.4 Protocols Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
24.1.1.5 Generation - Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
24.1.1.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
24.1.2 TMDNH - T1BOS for TIE Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
24.1.2.3 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
24.1.2.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
24.2 Central Office Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
24.2.1 TMC16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
24.2.1.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
24.2.1.4 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
24.2.1.5 Generation Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
24.2.1.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
24.2.2 TMDID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
24.2.2.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
24.2.2.4 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
24.2.2.5 Generation Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
24.2.2.6 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
A31003-H3170-S103-6-7620, 02/2019
Contents
24.2.2.7 Configuration Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

24.2.2.8 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
24.2.3 TMDNH -> T1BOS for Direct Inward Dialing Calls (T1DID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
24.2.3.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
24.2.3.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
24.2.3.3 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
24.2.3.4 Generation Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
24.2.3.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
24.2.4 TMDNH-T1BOS for Incoming and Outgoing Trunk Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
24.2.4.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
24.2.4.3 Generation Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
24.2.4.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
24.3 Recorded Announcement Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
24.3.2.1 With Privileged Station AMO SSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
24.3.2.2 Synchronous / Asynchronous Recorded Announcement with TMOM Module . . . . . . . . . . . . . 251
24.4 DIT Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
24.4.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
24.4.4 Generation Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
24.4.4.1 German . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
24.4.4.2 English. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
24.4.5 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
24.5 Supplemantary dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
24.6 Real Dialtone from Central-Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
24.7 RealTrunk Group Overflow (Rerouting) for Trunks in the Event of a Fault . . . . . . . . . . . . . . . . . . . . . . . 254
24.7.1 Original Trunk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
24.7.2 Trunk Group Overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
25 ANIF Automatic Number Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
25.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
25.4 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
26 Automatic Node Topology Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
26.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
26.3.1 Feature Activation / Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
26.3.2 Feature Parameterization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
26.3.3 What Information Does the Feature Provide? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
26.3.4 Diagnostic options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
26.3.5 Regenerate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
26.3.6 Switching the Tie Trunk Circuits On and Off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
26.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
27 Cornet NQ Interworking with DPNSS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
A31003-H3170-S103-6-7620, 02/2019
Contents
27.2 Application Field of PBXXX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

27.3 PBXXX Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
27.3.1 Partial Integration Ring Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
27.3.2 Partial Integration DIUS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
27.3.3 Full-integration Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
27.4 Feature Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
27.5 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
27.5.1 Software and Data Base Loading (Flash Loading Concept) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
27.5.2 PBXXX Partial Integration RG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
27.5.3 PBXXX Partial Integration (DIU-S2-Emulation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
27.5.4 PBXXX Full Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
27.6 Administration/Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
27.8 AMO Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
27.9.1 Configuration of ’Partial-integration-RG’ solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
27.9.2 Configuration of ’Partial-integration-DIUS2’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
27.9.3 Configuration of ’Full-integration’ solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
27.9.4 Usage of AMO LWCMD command interface: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
27.9.5 COP for PBXXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
27.9.6 Protocol changes for PBXXX to activate the ASEG COP-parameter . . . . . . . . . . . . . . . . . . . . . . . 292
27.9.7 COT Parameter for full integrated PBXXX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
27.9.8 Changes of standard LWPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
27.9.9 Remote registration of diversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
27.9.10 Class of Service Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
27.9.11 Trunk Identity Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
27.9.12 Routing DX calls to AC-Win MQ source keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
27.9.13 Automatic redirection to voicemail on busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
27.9.14 Trunking: Private ISDN networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
27.10 Relevante AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
28 CorNet-VN (CorNet Virtual Networking) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
28.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
28.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
29 Country-Specific Connection Techniques With Analog Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
29.1 Trunk Connections Versus Tie Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
29.2 Dial Tone, Proceed-to-Send Signal on Outgoing Seizure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
29.2.1 Real Dial Tone (Time-Dependent) From the Central Office (CO) . . . . . . . . . . . . . . . . . . . . . . . . . . 310
29.3 Dialing Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
29.4 End-of-Dial and Answer on Outgoing Seizure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
29.4.1 End-of-Dial Code With ’#’. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
29.4.2 End-of-Dial According to the 1A Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
29.4.3 End-of-Dial by Line Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
29.4.4 End-of-Dial With First Call Charge Pulse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
29.4.5 Effect of the End-of-Dial, Call Charge Pulse, and Answer Signals . . . . . . . . . . . . . . . . . . . . . . . . . 312
29.4.6 Configuring the End-of-Dial Monitoring and End-of-Dial 1A Timers . . . . . . . . . . . . . . . . . . . . . . . . 313
29.5 Dial Tone on Incoming Seizure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
29.6 Test Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
29.6.1 CH (Switzerland) Test Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
A31003-H3170-S103-6-7620, 02/2019
Contents
29.6.2 BEL Test Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

29.6.3 RSA Test Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
29.6.4 CIS Test Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
29.7 Extension of Trace Signaling for Calls to the Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
29.8 Line With Loop Start Signaling and Straightforward Direct Inward Dialing (DID). . . . . . . . . . . . . . . . . . . 317
29.8.1 Feature Description (User Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
29.8.2 Operational Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
29.8.3 Important Note on the ’Trunks’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
29.9 Connection to External Systems Using TC-SL Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
29.9.1 Outgoing Calls (OpenScape 4000 to External System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
29.9.2 Incoming Calls (External System to OpenScape 4000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
29.9.3 Consultation Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
29.9.3.1 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
29.9.4 Trunk Grounding/Trunk Flash. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
29.9.4.1 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
29.9.4.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
29.9.5 Picking Up a Consultation Hold in Straightforward Trunk Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
29.9.5.1 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
29.9.5.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
29.9.6 Suffix Dialing To Remote System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
29.9.7 Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
29.10 Testing and Measuring the DTMF and MFC Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
29.10.1 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
29.11 Extension of the Override Features With Intercept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
29.12 Reversed Charges Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
30 Customer Groups, Shared Systems CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
31 DTMF Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
31.1.1 Local DTMF functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
31.1.2 Network DTMF functionality / Trunks that allow DTMF negotiation.. . . . . . . . . . . . . . . . . . . . . . . . . 330
31.1.3 Outgoing DTMF functionality / Trunks that do NOT allow DTMF negotiation. . . . . . . . . . . . . . . . . . 330
31.1.4 Incoming DTMF functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
31.1.5 DTMF signaling in a conference concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
31.1.6 Feature Activation when DTMF signaling is active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
31.1.7 Affected Talk States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
31.1.8 Digit Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
31.3 Generation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
31.3.1 DTMF dialing configuration - Station basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
31.3.2 DTMF dialing configuration - Trunk (route) basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
31.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
32 ECMA QSIG Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
32.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
32.2 QSIG Protocol Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
32.2.1 B-channel negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
32.2.2 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
32.2.3 AMO Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
32.2.4 Instructions for generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
33 EDSS1 System Interface / Trunk Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
A31003-H3170-S103-6-7620, 02/2019
Contents
33.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

33.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
33.5 Configuration of the EDSS1 system interface with Screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
33.5.1 Configuration of the system interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
33.5.2 A station number verification (screening). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
33.5.3 EDSS1 Use Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
34 EURO-ISDN Exchange Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
34.1 Direct Dialing In (DDI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
34.2 Calling and Connected Number Displays (CLIP/CLIR and COLP/COLR) . . . . . . . . . . . . . . . . . . . . . . . 363
34.2.1 Format-dependent INS/STNO Modification in Incoming Direction. . . . . . . . . . . . . . . . . . . . . . . . . . 365
34.2.2 Format-dependent INS/STNO Modification in Outgoing Direction. . . . . . . . . . . . . . . . . . . . . . . . . . 365
34.2.3 COT-Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
34.2.4 Handling of extension numbers unknown to the exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
34.2.5 Classes of service OVCAT and SPECAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
35 Features Available Throughout the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
35.1 Call Forward/Forward No Reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
35.1.1 Call Forward/Forward No Reply with Open Numbering Scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . 369
35.1.2 Call Forward/Forward No Reply after Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
35.2 Announcement Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
35.3 Override, Camp-On, Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
35.4 Public Address System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
35.5 Dictation Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
35.6 Door Opener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
35.7 Code Calling - Normal and Multiple Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
35.8 Callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
35.9 Speed Dialling Facility Throughout the Network (S0,S2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
36 ISDN Protocol Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
36.1 Notes on protocol handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
36.2 Notes for upgrading a previous version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
36.3 Example: Copying a protocol from the hard disk to the database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
36.3.1 Current PRODE configuration should be regenerated first.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
36.3.2 Displaying the assignment of protocol variants to the protocols loaded in the database: . . . . . . . . 378
36.3.3 Deleting unwanted protocol variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
36.3.4 Querying the number (PDNO) under which the required protocol description (PDSTRING) is saved on
the HD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
36.3.5 Copying the protocol from the hard disk to the database memory . . . . . . . . . . . . . . . . . . . . . . . . . 382
36.3.6 Assigning a protocol variant to the memory location in the database . . . . . . . . . . . . . . . . . . . . . . . 382
37 LCR (Least Cost Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
37.1 Routing with LCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
37.1.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
37.1.3 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
37.1.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
37.2 Routing with LCR with Rerouting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
37.2.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
37.3 Routing via LCR with Internal Rerouting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
A31003-H3170-S103-6-7620, 02/2019
Contents
37.3.1 Description of Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

37.3.3 Generation (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
37.3.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
37.4 Central Office Breakout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
37.5 Indirect Network Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
37.6 Dialing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
37.7 Closed Numbering NWLCR (without LCR DIALING PLAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
37.7.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
37.8 Open Numbering LCR (with LCR DIALING PLAN)). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
37.8.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
37.9 Time Based LCR (AMO LSCHD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
37.9.2 Special Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
37.9.5 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
37.10 LCR Restriction Tables (AMO LDSRT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
37.10.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
37.10.2 Service Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
37.10.3 Generation (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
37.10.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
37.11 LCR Autorization PIN (Forced Authorization Code). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
37.11.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
37.11.4 Generation (Examples). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
37.11.5 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
37.12 LCR Classes of Service LCOS (AMO COSSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
37.12.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
37.13 LCR Authorization Codes (AMO LAUTH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
37.13.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
37.14 LCR Source Dependant (AMO KNLCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
37.14.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
37.15 LCR Source Groups (AMO LPROF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
A31003-H3170-S103-6-7620, 02/2019
Contents
37.15.3 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

37.15.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
37.16 LCR Dial Rules (AMO LODR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
37.16.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
37.16.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
37.17 LCR Traffic Dependant (Line Reservation AMO BUEND) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
37.17.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
37.18 Inserting/Removing in a Queue (AMO LDAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
37.18.1 Interrupting B Channel Search with Route Advance Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
37.18.1.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
37.18.1.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
37.18.1.3 Service Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
37.18.1.4 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
37.18.1.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
37.18.2 Off-Hook Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
37.18.2.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
37.18.2.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
37.18.3 ON-hook Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
37.18.3.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
37.18.3.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
37.19 LCR Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
38 LCR Rerouting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
38.1 Internal Rerouting Disabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
38.2 External Rerouting Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
39 MFC-R2 Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
39.1 Introduction to MFC-R2 Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
39.1.1 Compelled Signaling According to MFC-R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
39.1.2 Example of a Connection Set-Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
39.1.3 The Meaning of the MFC-R2 Signals According to UIT Q.441 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
39.1.4 MFC-R2 Signals and MFCTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
39.2 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
39.2.1 Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
39.2.2 SIU for MFC-R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
39.2.3 Trunk - SIU Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
39.3 General Information on the MFC Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
39.3.1 Identification With Master Number (Outgoing Seizure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
39.3.1.1 A Number Identification Examples (Generated, Outgoing Seizure) . . . . . . . . . . . . . . . . . . . . . 452
39.3.2 Counter When Retrieving the A-Number (Terminating Seizure) . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
39.3.3 Identification With MFC-R2 (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
39.3.3.1 Generation Notes on A Station Identification (Before the B Number) . . . . . . . . . . . . . . . . . . . 455
A31003-H3170-S103-6-7620, 02/2019
Contents
39.3.3.2 Generation Notes on A Station Identification (After the B Number) . . . . . . . . . . . . . . . . . . . . . 455

39.3.4 Use Identified Calling Number for Redial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
39.3.5 Acknowledged Identification Request (HUNGARY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
39.3.6 Handling the Signals in Generated Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
39.3.7 Note on Message F5607 MFC-MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
39.3.7.1 F5607 MFC-MONITORING for all terminating connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
39.3.8 Monitoring the MFC Signal Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
39.3.9 Dialing Monitoring Combined With Intercept to Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . 461
39.3.10 Tracing End-of-Dial Without Charges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
39.3.11 END TO END Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
39.3.12 Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
39.3.13 New User Categories for Private Networks (With MFC Signaling) . . . . . . . . . . . . . . . . . . . . . . . . . 463
39.3.14 Using the ITR (Internal Traffic Restriction Group) With MFC-R2 . . . . . . . . . . . . . . . . . . . . . . . . . . 464
40 National ISDN Basic Rate Interface (NI BRI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
40.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
40.3.1 Connecting NI BRI Data Devices via the SLMQ3 Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
40.3.2 Connecting NI BRI Date Devices via the SLMO Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
40.3.2.1 Restrictions With the TA S0 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
40.3.2.2 General Configuration Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
40.3.2.3 Connecting NI BRI Data Devices via the optiPoint Telephone . . . . . . . . . . . . . . . . . . . . . . . . . 468
40.3.3 NI BRI Partner Products Supported by OpenScape 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
40.4.1 First-Time Loading of the NI BRI Protocol Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
40.4.2 Connecting NI BRI Data Devices via the SLMQ3 Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
40.4.3 Connecting NI BRI Data Devices via the SLMO Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
40.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
41 Network Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
41.2 Methods of Preventing Network Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
41.4.1 Network with Open Numbering; Alternate Routing with Complete Set of Prefix Codes . . . . . . . . . . 479
41.4.2 Network with Open Numbering; Alternate Routing with one Prefix Code. . . . . . . . . . . . . . . . . . . . . 480
41.4.3 Network with Closed Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
41.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
42 Number Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
42.1 General Description and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
42.1.1 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
42.1.2 Phone numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
42.1.2.1 Structure a phone number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
42.1.2.2 Explicit and implicit phone numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
42.1.3 US EPNP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
42.1.3.1 The (multi-level) node numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
42.1.4 Number signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
42.1.4.1 Destination and information numbers: The general modification method . . . . . . . . . . . . . . . . . 494
42.1.4.2 The influence of LCR on Info Number Signaling (INS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
42.1.4.3 Info Number Signaling (INS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
42.2 Examples for the configuration of the number modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
A31003-H3170-S103-6-7620, 02/2019
Contents
42.2.1 One-level network (only Level 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503

42.2.1.1 Closed-numbered area with digital ISDN CO connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
42.2.1.2 Closed-numbered area with analog CO connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
42.2.1.3 Closed-numbered area with CO connection and subsystems . . . . . . . . . . . . . . . . . . . . . . . . . 507
42.2.1.4 Mixed-numbered network with digital ISDN trunk access points . . . . . . . . . . . . . . . . . . . . . . . 507
42.2.1.5 Source/destination-dependent number modification in the ISDN or PNP numbering plan . . . 513
42.2.2 Multi-level network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
42.2.2.1 Three-level, open-numbered network/one-level OpenScape 4000 specific numbering plan . . 517
42.2.2.2 Closed numbering of network in OpenScape 4000 specific numbering plan . . . . . . . . . . . . . . 524
42.2.2.3 Open-numbered network, three-level, OpenScape 4000 specific numbering plan . . . . . . . . . 526
42.2.3 Open-numbered heterogeneous network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
42.2.3.1 Heterogeneous network with nodes that know only one node number . . . . . . . . . . . . . . . . . . 529
42.2.3.2 Heterogeneous network with nodes that already modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
42.2.3.3 Heterogeneous network with nodes that do not modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
42.2.3.4 Three-level, open-numbered network/one-level OpenScape 4000 specific numbering plan,
overlapping virtual nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
42.2.3.5 Three-level, open-numbered network/one-level OpenScape 4000 specific numbering plan,
overlapping virtual nodes with ambiguous extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
42.2.3.6 US EPNP network with overlapping L0 codes for extension, without exit or prefixes . . . . . . . 547
42.2.3.7 US EPNP network with overlapping L0 codes for extension, with exit, without prefixes . . . . . 550
42.3 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
43 PIN and Follow-Me Network-Wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
43.2 Functions / Restrictions when using a PIN network-wide / external . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
43.3 Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
43.3.1 Activating and Deactivating a Network-Wide PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
43.3.2 Identification via "APIN" Code (Manual PIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
43.4 Identification via Chip Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
43.5 Input Procedure for Network-Wide Follow-Me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
43.5.1 Follow-Me Activation/Deactivation with the FWD key (PIN/Chip Card Active) . . . . . . . . . . . . . . . . 561
43.5.2 Follow-Me Activation/Deactivation by Dialling the Codes for "Variable Call Forwarding On/Off" (PIN/
Chip Card Active). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
43.6 Follow-Me Activation/Deactivation via Service Menu:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
43.6.1 Activating Follow-Me via the Service Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
43.6.2 Deactivating Follow-Me via the Service Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
43.7 PIN Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
43.8 Network-Wide PIN and Follow-Me in 1 Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
44 Preventing Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
44.1 Single Level Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
44.2 Multi Level Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
45 Public PRI Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
45.1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
45.1.1 Supplementary Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
45.1.1.1 ACPN (Additional Calling Party Number) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
45.1.1.2 Network Call Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
45.1.1.3 Calling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
45.1.1.4 Equal Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
45.1.1.5 CND (Calling Name Delivery). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
45.1.1.6 ISDN-PRI RN (ISDN-PRI Redirecting Number) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
45.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
A31003-H3170-S103-6-7620, 02/2019
Contents
45.2.1 CND (Calling Name Delivery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

45.2.2 ISDN-PRI RN (ISDN-PRI Redirecting Number) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
45.4 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
45.4.1 Calling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
45.4.2 B-Channel Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
45.4.3 ACPN (Additional Calling Party Number) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
45.4.4 CND (Calling Name Delivery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
45.4.5 ISDN-PRI RN (ISDN-PRI Redirecting Number) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
45.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
46 Public Network Exchange Signalling DTMF (Suffix Dialling) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
47 REFTA Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
47.1 Network Synchronization Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
47.1.1 Clock Hierarchy Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
47.2 Definition of Hierarchy Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
47.2.1 Synchronous Private Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
47.2.2 Plesiochronous or Pseudosynchronous Private Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
47.2.3 Limiting Level Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
47.2.4 Reducing Level Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
47.3 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
47.3.1 Synchronization Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
47.3.2 Clock-Transparent Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
47.3.3 Connections with External Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
47.4 AMO REFTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
47.4.1 Value Range of Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
47.4.2 Priority Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
47.4.3 Networks with Several Masters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
47.4.4 AMOs LWPAR & SYSPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
47.4.5 Clock Generator and Front Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
47.4.6 Changes with cPCI Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
47.5 Selection of Clock Generators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
47.5.1 Exactness of Free-Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
47.5.2 Performance for Network Operation/Normal Clock Generators . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
47.5.3 Hold Over Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
47.5.4 ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
47.5.5 External Clock Box (AECB, AICB, etc.) for OpenScape 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
47.5.6 Network Clock Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
47.5.7 SDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
47.5.8 HiPath Cordless (CMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
47.5.9 Network-Wide Synchronization for Cordless (ISS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
47.5.10 ATM Interface (STMA Board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
47.5.11 Special Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
47.5.12 Front Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
47.5.13 S0 Interface not Permanently Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
47.5.14 Setting the REFTA Error Counter to 16 000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
47.5.15 T4 Clock Output/Previously T3ab, APT3 Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
47.6 Notes/Experience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
47.7 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
48 Restricted Call Duration for Transit Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
A31003-H3170-S103-6-7620, 02/2019
Contents

48.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
49 Route Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
49.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
49.4.1 Heterogeneous Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
49.4.2 Network with Several Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
49.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
50 S0/S2 Trunk Parameterization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
51 Satellite Paths Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
52 Screening on the EDSS1 Trunk Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
52.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
52.3 Screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
52.3.1 Allocate memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
52.3.2 Configure screening patterns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
52.4 CLIP/CLIR, COLP/COLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
52.5 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
53 Single Point of Access (SPoA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
53.1 Description of the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
53.1.1 SPoA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
53.1.2 Option SESAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
53.1.3 SIRA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
53.2 SPoA Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
53.3 Possible SPoA scenarios and network access on customer site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
53.3.1 Remote Connectivity via Customer own SPoA (ISDN / DSL and VPN) . . . . . . . . . . . . . . . . . . . . . 633
53.3.2 Remote Connectivity via supported SPoA Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
53.3.2.1 SPoA Router in the Customer LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
53.3.2.2 Direct Access SPoA Router with netpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
53.4 Configuration of the Huawei - Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
53.4.1 Display and Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
53.4.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
54 Transmission and Loss Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
54.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
55 Trunk Access with the STMA When Using the ATM Networking V2.0 Feature . . . . . . . . . . . . . . . . . . 645
55.3 Example Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
56 Trunk to Trunk Supervised Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
56.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
56.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
A31003-H3170-S103-6-7620, 02/2019
Contents

56.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
57 Virtual Numbering (VNR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
57.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
57.1.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
57.1.2 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
57.1.2.1 Branch network optimization - a company with a branch network with a single physical system . .
651
57.1.2.2 Shared Use of a OpenScape 4000 by Different Companies. . . . . . . . . . . . . . . . . . . . . . . . . . . 653
57.2 Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
57.2.1 Station Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
57.2.2 Feature Principles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
57.2.3 Special Features and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
57.2.4 Limiting Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
57.2.5 Converting to VNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
57.3 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
57.3.1 Tasks Involved in Switching to VNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
57.3.2 Network Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
57.3.3 Description of the AMO Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
57.3.3.1 Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
57.3.3.2 Digit Analysis and Node Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
57.3.3.3 Station Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
57.3.3.4 Trunk Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
57.3.3.5 LCR Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
57.3.3.6 Brief Description of 2-Level LCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
57.3.3.7 Future Expansions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
57.3.4 Connecting External Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
57.4 OpenScape 4000 Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
57.4.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
57.4.2 Modifying the User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
57.4.2.1 "System" Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
57.4.2.2 "Station" Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
57.4.2.3 "Virtual Nodes (KNDEF)" Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
57.4.2.4 Station Relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
57.5 AMO Interrelationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
57.5.1 Attendant Console Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
57.5.1.2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
57.5.2 VNR with Code Calling/Multiple Code Calling (CC/MCC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
57.5.3 VNR with Alternate Routing on Error (ARoE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
57.5.4 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
57.5.5 Modified Display for E.164 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
57.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
58 Voice Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
58.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
58.1.1 Task of the Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
58.1.2 The Voice Compression Board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
58.1.3 Description of Synonyms which are Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
58.1.4 Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
58.1.4.1 Figures of Symmetric Voice Compression Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
58.1.5 VCM Transit Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
A31003-H3170-S103-6-7620, 02/2019
Contents
58.1.6 Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706

58.2 Basic Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
58.2.1 Allocation of Needed Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
58.2.2 Costumer Feature List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
58.2.3 VCM Board Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
58.2.4 Class of Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
58.2.5 Trunk Group Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
58.2.6 Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
58.2.7 Activation/Deactivation of Boards and Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
58.2.8 LCR Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
58.2.9 Voice Compression Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
58.2.10 Deactivation/Activation of Voice Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
58.3 Extended Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
58.3.1 Mixed Routes (compressed/not compressed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
58.3.2 No Voice Compression for Particular Subscribers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
58.3.2.1 Connections from Intern to Intern/External. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
58.3.2.2 Connections from External to Intern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
58.3.3 More Data Channels or More Speech Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
58.3.4 Route Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
58.4 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
59 Call Detail Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
59.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
59.2 Call Detail Recording Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
59.3 Call Detail Recording Overload Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
59.4 Relevant AMOs for Call Detail Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
59.5 Cross-References between AMOs and the AMO SELG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
59.6 Types of Call Detail Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
59.6.1 Internal Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
59.6.1.1 Voice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
59.6.1.2 Non-Voice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
59.6.2 Incoming Trunk Calls and Tie Trunk Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
59.6.3 Outgoing Tie Trunk Traffic (Networking) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
59.6.3.1 Configuring System Features for Outgoing Tie Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
59.6.3.2 Configuring System Features for Outgoing CO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
59.6.4 Call Detail Recording for Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
59.6.5 Network-Wide Call Detail Recording With Call ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
59.6.6 Euro ISDN Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
59.7 Call Charge Display on the Digite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
59.8 Types of Charge Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
59.9 Data Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
59.10 Data Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
59.11 Selection Group Operating States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
59.12 Validity Check of the Selection Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
59.13 Data Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
59.13.1 Immediate Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
59.13.2 Data Output on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
60 Call Detail Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
60.1 Requirements for Call Detail Transmission to the DPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
60.2 Transmission of Individual Call Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
60.3 Message Sequences for Transmitting Individual Call Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
60.3.1 Data Retrieval Initiated by the DPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
A31003-H3170-S103-6-7620, 02/2019
Contents
60.3.2 Data Retrieval Initiated by OpenScape 4000 for Scheduled Batch Job or Forced Output . . . . . . . . 760
60.3.3 Immediate Output at the End of a Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
60.3.4 Data Output Initiated by OpenScape 4000 for a Scheduled Batch Job or Forced Output . . . . . . . . 763
60.3.5 Data Transmission in RJE Operation (RJE = Remote Job Entry) . . . . . . . . . . . . . . . . . . . . . . . . . . 764
60.3.5.1 Data Retrieval Initiated by the DPA (SNA RJE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
60.3.5.2 Data Output Initiated by OpenScape 4000 for Scheduled Batch Job or Forced Output (SNA-RJE)
767
60.4 Messages When Transmitting Individual Call Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
60.4.1 Message ”Send CDR Information” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
60.4.2 Message "CDR information block on demand" or "CDR information block with immediate output" . 769
60.4.3 Message ”Good/Bad CDR information end” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
60.4.4 Message ”CDR information processed” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
60.4.5 Message "CDR data retrieval request" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
60.4.6 Message ”Repeat the same call data record (for immediate output only)” . . . . . . . . . . . . . . . . . . . . 775
60.4.7 Verification of Connection (”Heartbeat”). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
60.5 Types of Elements When Transmitting Call Detail Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
60.5.1 Elements with a Fixed Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
60.5.2 Configurable Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
60.6 List of the Record Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
61 Call Detail Information for Heterogeneous Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
61.1 Call Charge Display Parameters in AMO COT and AMO COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
61.2 Charge-Related COT Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
61.2.1 AOCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
61.2.2 IICB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
61.2.3 SNBE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
61.2.4 IGID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
61.2.5 TRSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
61.2.6 DPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
61.2.7 ICZO and ICZL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
61.2.8 CCTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
61.2.9 DFNN and LWNC on Tie Trunks to an Expression 450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
61.3 Charge-Related TDCSU Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
61.3.1 ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
61.4 Charge-Related FEASU Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
61.4.1 DISCHNW and CDROGNW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
61.5 Charge-Related LDAT Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
61.5.1 LATTR Parameter NOCHDISP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
62 CDRe - Call Detail Recording enhanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
62.1 Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
62.2 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
62.3 Modified Cost Unit Assignment Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
62.4 Special Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
62.5 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
62.7 AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
62.7.1 Enabling and Disabling Call Data Recording Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
62.7.2 Important Fields in the Call Detail Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
62.7.3 Modified Cost Unit Assignment Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
62.7.4 Processing Sequence for Entries in DEFPP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
62.7.5 Changes in the AMO GEFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
A31003-H3170-S103-6-7620, 02/2019
Contents
63 Call Detail Recording enhanced Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823

63.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
63.4 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
63.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
64 Call Detail Recording - Account Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
64.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
64.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
65 Call Charge Data Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
65.1 Call Charge Data Display from the CDRS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
65.2 Call Charge Data Display on Supplementary Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
66 Call Charge Data - Immediate Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
66.1 Immediate Output to GC 3001 A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
66.2 Immediate Output to CDRC1 File on HD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
66.3 Immediate Output to File Transfer File on HD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
66.4 Immediate Output to Magnetic Tape Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
66.5 Immediate Output to PT80i (Optional Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
67 Call Charge Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
67.1 Output Format 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
67.2 Charge Output at the ATND (CDRATND) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
67.3 Charge Output with PT80i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
67.3.1 Charge Output per Line with PT80i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
67.3.2 Charge Output per Station with PT90i (CDRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
67.4 Charge Output to DPS via WAML Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
67.4.1 Adding the WAML Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
67.4.1.1 AMO DIMSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
67.4.1.2 AMO BCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
67.4.1.3 AMO DIMSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
67.4.2 Configuration for TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
67.4.2.1 AMO WABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
67.4.2.2 AMO LANC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
67.4.2.3 AMO CPTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
67.4.2.4 AMO FAMOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
67.4.3 Direct Call Data Exchange Between OpenScape 4000 and ACom PC. . . . . . . . . . . . . . . . . . . . . . 858
67.4.4 ACom ACL Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
67.4.4.1 ACom Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
67.4.4.2 Ticket Output in the Output Window of the ACom User Interface . . . . . . . . . . . . . . . . . . . . . . 862
68 Call Charge Recording-Elapsed Time Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
68.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
68.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
68.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
A31003-H3170-S103-6-7620, 02/2019
Contents
69 Central Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865

69.1 Flexible Memory Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
69.2 Central System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
69.2.1 Affected AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
69.2.1.1 AMO ZAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
69.2.1.2 AMO FEASU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
69.2.1.3 AMO FEACG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
69.2.1.4 AMO CTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
69.2.1.5 AMO KNMAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
69.2.1.6 AMO KNPRE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
69.2.2 Configuration Commands for Central System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
69.3 Tariff Group Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
69.4 Tarif Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
69.5 Call Data Recording for Outgoing Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
69.6 Call Data Recording for Incoming Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882
69.7 Call Data Recording for Internal Node Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
69.8 Call Charge Display at the Attendant Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886
69.9 CDR Records, Central and per Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
69.10 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
69.10.1 Internal Call Data Recording in the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
69.10.2 Tie Traffic with Incoming Charges and Trunk Traffic in Transit . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
70 Charge Pulse Metering & Sending to Analog Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
70.1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
70.1.1 Operating limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
70.1.2 Areas of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
70.1.3 Activating the feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
70.2.1 Charges for analog stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
70.2.2 Increasing the line length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
70.3 Generation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
70.3.1 AMOs for charges on analog stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
70.3.2 FEASU - Enabling metering pulse sending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
70.3.3 BCSU - Configuring an SLMAR board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
70.3.4 XAPX - Managing classes of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
70.3.5 SCSU - Configuring an SLMAR station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
70.3.6 TTBL- Configuring the tariff table for pulse sending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
70.3.7 TTBL - Managing the tariff group table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
70.3.8 VBZGR - Managing the internal traffic restriction group zone matrix . . . . . . . . . . . . . . . . . . . . . . . . 902
70.3.9 GEFE - Managing the CDR parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
70.3.10 ZAND - Managing central system data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
70.3.11 PTIME - Managing timers for peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
70.4 Forwarding charges from the CO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
70.4.1 Configuring the board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
70.4.2 Feature enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
70.4.3 Output loadware version of SLMAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
70.4.4 Activating call detail recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
70.4.5 PUPHON tariff table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
70.4.6 Station entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
70.5 Configuring internal call detail recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
70.5.1 Configuring internal zones for call detail recording. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
70.5.2 Assigning type public telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
A31003-H3170-S103-6-7620, 02/2019
Contents
70.5.3 Enabling internal call detail recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905

70.5.4 Tariff table for metering pulse sending. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
70.5.5 Tariff tables for public telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
71 Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
71.1 Country-Specific Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
71.2 Connection Limits Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
71.3 Output Text Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
71.4 File Sizes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
72 DPS Interface Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
73 INFO 2000 Outcalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913
74 Per-Second Invoicing with Prices in 1/100000 Currency Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
75 Station Number Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
76 Audible Ringing on Rollover Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
76.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934
76.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
76.6 Interrelationship with other Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
77 Call Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
77.1 Directed Call Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
77.2 Local Call Pickup Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
77.2.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
77.2.3 Pickup Group Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
77.2.5 Other Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
77.3 Network-wide Call Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945
77.3.1 Network-wide Call Pickup Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946
77.3.2 Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946
77.3.3 Directed Call Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
77.3.3.2 Special Aspects of the Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
77.3.4 Service Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
77.3.5 Generation Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
77.3.5.1 Network-wide Call Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
77.3.5.2 Directed Call Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
77.3.5.3 Display on Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
77.3.5.4 Configure call pickup throughout the network on PBXXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
77.3.6 AMO Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953
78 CHESE - Integrated Executive/Secretary System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955
78.1 Assign a Secretary Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957
78.2 Assignment of the Messenger Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958
A31003-H3170-S103-6-7620, 02/2019
Contents
79 CHESE/ Team Functions Network-wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959

79.1.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
79.1.2 Team Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
79.1.3 Network-wide Team in Combination With Additional Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
79.1.4 Comparison of Current Chese With Network-wide Team Function . . . . . . . . . . . . . . . . . . . . . . . . . 964
79.2 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
79.2.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
79.2.2 Detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
79.2.3 Flowchart for Chese 1/1 over 2 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
79.3 Generation (Examples) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
79.3.1 Two Executives, One Secretary, Spread Over 3 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
79.3.1.1 Configure Network-wide Call Pickup for TSC Signaling in Nodes 89-200 . . . . . . . . . . . . . . . . 979
79.3.1.4 Configure Executive 1 in System 89-399 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
79.3.1.5 Configure Executive 2 in System 89-400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
79.3.1.6 Configure Secretary in System 89-200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
79.3.2 Two Executives and Two Secretaries, Spread Over 3 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
79.3.2.1 General Section in System 3 (Node 300) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
79.3.2.4 Configure Executive 1 in Node 300. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
79.3.2.5 Configure Executive 2 in Node 400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
79.3.2.6 Configure Secretary 1 in Node 300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
79.3.2.7 Configure Secretary 2 in Node 400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
80 Class of Service Switch-Over COSX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
81 COM Group Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
81.1 Feature Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
81.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
81.4 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
81.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999
82 COM Group Speaker Call -Two-Way . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
82.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
82.2 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
82.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
82.4 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
82.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
83 Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
83.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
83.3 Feature Interactions for Hunt Group with Parallel Ringing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
83.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
84 Hunt Group Network-wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
84.1 Expansion of the Call Queue Overflow Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
84.2 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
A31003-H3170-S103-6-7620, 02/2019
Contents
84.3 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018

85 Keyset Preview Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
85.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
85.2 Feature Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
85.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
85.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
86 Integrated Key Functionality / Multi Line Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
86.1.1 Brief Description of Keyset Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
86.1.2 Display of incoming calls on secondary lines of a keysystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
86.1.2.2 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
86.1.3 Keysystem Flowchart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
86.2 Trading-Executive in a Keysystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
86.2.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
86.2.2 Installing a local Keysystem with the new features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
86.2.2.1 Local Keysystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
86.2.2.2 Direct station selection line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
86.2.2.3 Mailbox per Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
86.2.2.4 Silent monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
86.2.2.5 Ring Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
86.2.2.6 Repeat dial function for the used line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045
86.2.3 Direct Station Selection network wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
86.2.3.1 Installation of the keysystem network wide via two nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
86.2.3.2 Direct station selection line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
86.3 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056
87 Parallel Ringing - One Number Service (ONS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
87.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
87.2.1 General Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
87.2.2 Interactions with other Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
87.2.3 Notes on Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
87.2.4 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
87.2.5 ONS Groups with SIP Subscriber as Master/Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
87.3.1 Configuration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
87.3.2 Example with Auxiliary Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068
87.3.3 Example with SIP Subscriber (Master and Slave) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
87.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
88 Personal Device Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073
88.2.1 Supported Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073
88.2.2 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
88.2.3 Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
88.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084
A31003-H3170-S103-6-7620, 02/2019
Contents
89 Speaker Call - One-Way - Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087

89.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087
89.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088
89.4 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088
89.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089
90 Fax Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1091
90.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1092
91 Number Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093
91.2 Example of Station Number Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094
91.3 Combination Code (FAX, DTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094
91.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1095
92 Automatic Number Identification (ANI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097
92.3 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097
92.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097
93 Autoset Relocate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1099
93.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1099
93.1.1 Terms Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1100
93.1.2 Prerequisites for Signing Off and On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1101
93.2 Devices and Configurations which support Autoset Relocate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102
93.2.1 Anate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102
93.2.2 Digital System Telephone (without second Telephone) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102
93.3 Devices which do not support Autoset Relocate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102
93.4 AMOs Usage Examples for Autoset Relocate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103
93.4.1 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103
93.4.2 Signing Off and On via AMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103
93.4.2.1 Signing off with DSSU AMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103
93.4.2.2 Signing on with AMO DSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104
93.4.3 Signing Off and Enabling PENs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104
93.4.3.1 Signing Off a Free PEN (or TSI) with AMO BCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104
93.4.3.2 Enabling a Signed Off PEN (or TSI) with AMO BCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105
93.4.4 Configuring Users/Stations with SIGNED_OFF Status (without PEN) . . . . . . . . . . . . . . . . . . . . . . 1105
93.4.5 Display Signed Off Users and PENs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105
93.4.5.1 Display Signed Off Users with AMO SCSU / AMO SBCSU . . . . . . . . . . . . . . . . . . . . . . . . . . 1105
93.4.5.2 Display Signed Off PENs with AMO BCSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105
93.4.5.3 Display Signed Off Users and PENs with AMO SDSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106
93.4.6 Emergency calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106
94 Babyphone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
94.3 User Interface and Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
94.3.1 Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
94.3.2 Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
A31003-H3170-S103-6-7620, 02/2019
Contents
94.3.3 Monitoring the room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109

94.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1110
95 Block Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1111
95.3 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1111
95.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
96 Buzz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115
96.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115
96.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116
97 Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117
97.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119
97.2.1 Variable Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119
97.2.2 Fixed Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1120
97.2.3 System Call Forwarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1120
97.2.4 Call Forwarding/Call Forwarding Busy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121
97.2.5 Call Forwarding Unconditional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121
97.2.6 Chaining FWD Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121
97.3.1 AMO ACTDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123
97.3.2 AMO COSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123
97.3.3 AMO COT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124
97.3.4 AMO DIMSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124
97.3.5 AMO TDCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125
97.3.6 AMO WABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125
97.3.6.1 FWD Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125
97.3.6.2 FWD Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127
97.3.6.3 FWD System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129
97.3.6.4 Special Digit Analysis Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129
97.3.7 AMO ZAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1130
97.3.8 AMO ZIEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131
97.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1132
98 Call Forward no Reply (CFNR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135
98.1 Call Forward no Reply after Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135
98.1.3 Interaction with other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135
98.2 Call Forward No Reply and Rerouting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136
99 Call Hold analog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137
99.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137
99.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138
A31003-H3170-S103-6-7620, 02/2019
Contents
99.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139

100 Call ID (Name and Number) on Analog Port with PRI NI2 Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141
100.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141
100.2 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141
100.3 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141
101 Calling Line Identification (CLI) Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143
101.2 Realization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143
101.3 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
101.4 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145
101.5 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147
101.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148
102 Calling Line Identification (CLI) Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1151
102.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154
102.5 Further Features in Connection with CLIR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154
102.5.1 Display Control for a Single Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154
102.5.1.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155
102.5.1.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155
102.5.2 Display Control for a Replacement Number for Calls to an External Station . . . . . . . . . . . . . . . . 1156
102.5.2.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157
102.5.3 Display Control (using parameters DISPTGNA/INDNADIS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158
102.5.3.3 Generation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
102.5.3.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
102.5.4 Exceptions to Honoring Presentation Restriction Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161
102.5.4.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162
102.5.5 Display Suppression for Analog and T1 Trunks (only US) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162
102.5.5.3 Generation (Examples for US) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163
102.5.5.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165
102.6 CLIR on an Individual Subscriber Basis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165
103 Calling Line Identification (CLI) Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
103.1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
104 Call Log for optiPoint 410/420, OpenStage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169
104.2 Feature Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1170
A31003-H3170-S103-6-7620, 02/2019
Contents

104.4 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1171
104.4.1 Call log configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1171
104.4.2 Set up menu option: delete call log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172
104.4.3 Setup: save originating number on transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172
104.4.4 Protection of the individual call log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172
104.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172
105 Call Parking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175
105.1 System Park . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175
105.1.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175
105.1.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176
105.1.3 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177
105.2 Directed Call Parking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1178
105.2.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1178
105.2.3 Feature Operation by User Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179
105.2.3.1 Directed Call Park Feature Invocation from Anates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179
105.2.3.2 Directed Call Park Feature Invocation from Terminals (with display) . . . . . . . . . . . . . . . . . . 1180
105.2.3.3 Directed Call Park Feature Invocation from AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181
105.2.3.4 Directed Call Park Feature Invocation from ACWin (MQ) . . . . . . . . . . . . . . . . . . . . . . . . . . 1182
105.2.4 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182
105.2.5 Interworking between devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183
105.3 Call Park Within a Pickup Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183
105.3.1 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183
105.4.1 System Park. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184
105.4.2 Directed Call Park . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184
105.4.3 Park within a Pickup group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186
105.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186
106 Connect Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189
106.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189
106.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1190
107 Controlled Trunk and Line Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1191
107.2 Effects on other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192
107.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1193
107.3.1 Data editing for CorNet-NQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1193
107.3.2 Provision of path selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
107.3.3 System Reactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197
107.5.1 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1200
108 Desktop Callback Idle Display Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201
108.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202
A31003-H3170-S103-6-7620, 02/2019
Contents
109 Dictation Equipment DICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1203

110 Digital Station with S0 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205
110.1 Functional Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205
110.2 Bus Extenders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206
110.2.1 Adding NV Services to the Functional Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206
110.2.2 Adding MSN Call Numbers to the Functional Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207
110.2.3 Deleting Devices at the S0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208
111 Direct Station Selection (DSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1211
111.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1212
112 Disable Flash on Analog Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213
112.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213
112.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213
112.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214
113 Disable Message Waiting Lamps on OPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
113.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
113.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
113.5 Generarion (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216
113.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216
114 DNIS (Directory Number Identification Services). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217
114.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217
114.2.1 Definition of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217
114.2.2 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218
114.2.3 AMO Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218
114.4 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
114.4.1 AMO WABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
114.4.2 AMO TDCSU (Digital), AMO TACSU (Analog ) Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . 1219
114.4.3 AMO BUEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1220
114.4.4 GDTR Conversion for only Called Party Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1220
114.4.5 GDTR Conversion for Called Part Number and SID/ANI info. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1222
114.4.6 DNIT table GDTRSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224
114.4.7 GDTR Digit Conversion (DNIS) without SID/ANI signalling without PRI services . . . . . . . . . . . . 1225
114.4.8 GDTR Digit Conversion (DNIS) with SID/ANI signalling without PRI-Services for USA-PRI Trunks.. .
1225
114.4.9 GDTR Digit Conversion (DNIS) with SID/ANI signalling with PRI Services for USA-PRI Trunks for ACD
call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1226
114.4.10 GDTR Digit Conversion for Cornet-NQ PRI Trunks.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1227
114.4.11 Without DNIS feature configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1227
114.4.12 DIDCR Digit Conversion without services for analog trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1227
114.4.13 DIDCR Digit Conversion with SID/ANI signalling with Trunking Services for USA-T1 Trunks. . 1228
114.4.14 DID call blocking DIDBLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229
A31003-H3170-S103-6-7620, 02/2019
Contents
114.4.15 Call Routing when no CLI present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229

114.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1230
115 DSS 1 Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1233
115.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
115.2.1 Call Forwarding (CFU, CFB, CFNR, and CD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
115.2.1.1 Differences to previous forwardings (general) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236
115.2.1.2 Call Forward Unconditional (CFU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236
115.2.1.3 Call Forward Busy (CFB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236
115.2.1.4 Call Forward No Reply (CFNR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236
115.2.2 Call on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237
115.2.3 Call Transfer (ECT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237
115.2.4 Three-Party Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237
115.2.5 Call Waiting (CW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237
115.2.6 Callback (CCBS) WP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238
115.2.7 Called Party Display Suppression (COLR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238
115.2.8 Advice of Charge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239
115.2.9 Malicious Call Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239
115.2.9.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239
115.2.9.2 Feature Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239
115.2.9.3 AMO Batch for Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239
115.2.9.4 AMO Batch for Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240
115.2.10 Terminal Portability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240
115.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244
115.6 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244
116 E911 Emergency Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1245
116.2 Central Office (CO) Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
116.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
116.3.1 Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
116.3.2 Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
116.3.2.1 Central System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
116.3.2.2 Port and Subscriber Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
116.3.2.3 Call Handling and Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247
116.5 AMO Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247
116.5.1 Basic AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247
116.5.1.1 PRODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247
116.5.1.2 DIMSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248
116.5.1.3 ZAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248
116.5.1.4 SDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248
116.5.1.5 BUEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248
116.5.1.6 REFTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248
116.5.1.7 WABE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249
116.5.1.8 RICHT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249
116.5.1.9 LIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249
116.5.1.10 COT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249
116.5.2 ISDN Connection to the C.O.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1250
116.5.2.1 TDCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1250
A31003-H3170-S103-6-7620, 02/2019
Contents
116.5.2.2 COT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1250

116.5.2.3 LODR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1250
116.5.2.4 LDPLN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1251
116.5.3 Analog Connection to the C.O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1251
116.5.3.1 LODR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1251
116.5.3.2 LDPLN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252
116.5.4 Digital Networking OpenScape 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252
116.5.4.1 TDCSU node 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252
116.5.4.2 TDCSU node 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253
116.5.4.3 LIN node 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253
116.5.5 Digital Networking V6.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253
116.5.6 Analog Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254
116.5.6.1 LODR node 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254
116.5.6.2 LDPLN node 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254
116.5.6.3 COT node 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254
116.5.6.4 LIN node 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254
116.5.6.5 TACSU node 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255
116.5.7 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255
117 Emergency Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257
117.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1258
118 Emergency Override/Disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1261
118.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1263
119 Entrance Telephone with Door Opener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267
120 EURO ISDN Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269
120.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269
120.1.1 Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269
120.1.2 Option Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1270
120.1.3 Station class of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1272
120.2 Additional Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273
120.2.1 Multiple Subscriber Numbers (MSN) on the S0 Bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273
120.2.1.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274
120.2.2 Deleting of an Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277
120.2.2.1 Displaying an MSN Number of an S0 Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279
120.3 Subaddressing (SUB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279
120.3.1 Malicious Call Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280
120.3.2 User-to-User Signalling (UUS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280
120.3.3 Terminal Portability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280
120.3.4 Call Waiting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280
120.3.5 Call Completion Busy Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
120.3.6 COLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
120.3.7 Advice of Charge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
121 Executive Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
121.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
121.1.1 DSS lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
A31003-H3170-S103-6-7620, 02/2019
Contents
121.1.2 Mailboxes per line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283

121.1.3 Entry without tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
121.1.4 Ring transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
121.1.5 Redial destinations for trunks used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284
121.2 Example: Configuration over two Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284
121.3 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1290
122 Flexible optiPoint Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1293
122.3 User Interface/Display Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1293
122.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1295
123 Hotline/Off-Hook Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1297
123.1 Relevante AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298
124 Ignore Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1301
124.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1301
125 Malicious Call Identification/Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1303
125.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1303
125.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1305
126 Manual Hold of Consultation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307
126.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307
126.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307
127 Multilingual User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1309
127.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1311
128 Name and Organization to a Number (ORG Assigning) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1313
129 Number Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315
130 On Hook Transfer per User or a Group of Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317
130.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318
131 OpenStage TDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319
131.1 Boards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319
131.2 OpenStage terminal types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319
131.3 Transmission Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319
131.4 Accessories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1322
131.5 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323
131.5.1 Terminal Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323
A31003-H3170-S103-6-7620, 02/2019
Contents
131.5.2 Key assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323

131.5.3 Master/Slave Configuration Downstream from Up0 Extender (Phone Adapter). . . . . . . . . . . . . . 1324
131.5.4 OpenStage Busy Lamp Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327
131.5.5 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328
131.6 TDM Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1329
131.6.1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1329
131.6.2 Restriction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1329
131.6.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1330
132 PIN (Personal Identification Number) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1331
132.1 PIN Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1331
132.2 Functions / Restrictions when using a PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333
132.3 PIN / PCODE Activation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334
132.4 Length of PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334
132.5 Manual PIN Types (PIN1 to PIN4 and PIN10-15) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1335
132.6 PIN Card (Chip Card). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1335
132.7 Class of Service Changeover Code (COSXCD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336
132.8 Class of Service Changeover to COS2 without COSXCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336
132.9 PIN Display on DIGITE Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336
132.10 Project Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336
132.11 Service Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337
132.12 Account Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337
132.13 Forced Authorization Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338
132.14 PIN Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338
132.14.1 PIN Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338
132.14.2 Duration of PIN Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1339
132.14.3 User Identification Display on Digite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1339
132.14.4 PIN-Identification at Home Station Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1340
132.14.5 Transferring classes of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1340
132.14.6 COS and Key Function Transfer from Home Station (internal PIN only) . . . . . . . . . . . . . . . . . . 1340
132.14.7 PIN-Entry in Repertory Keys and Speed Dialing List (internal PIN only). . . . . . . . . . . . . . . . . . 1341
132.14.8 Automatic Exchange Seizure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1341
132.14.9 Additional Text for Call Data Recording (internal PIN only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1342
132.14.10 Verifying the PIN/PCODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1342
132.14.10.1 Algorithmic "MODULO-N" Verification of PIN/PCODE . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343
132.14.11 Station Number of Home/Foreign Station for CDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346
132.14.12 PIN/PCODE and Call Transfer (Extension) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346
132.14.13 Detecting PIN/PCODE Hackers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347
132.14.14 Deactivation of PIN by pressing Release or Delete Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347
132.14.15 PIN Valid for Digit Pattern Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347
132.15 Company Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348
132.16 SMART Transfer Facility between Mailbox and Remote Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348
132.17 PIN/PCODE for Voice and Non-Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348
132.18 PIN/PCODE in the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348
132.18.1 Network-Wide PIN Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1349
132.18.1.1 Mobile Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1350
132.18.1.2 Configuration Commands for Network-Wide PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1350
132.18.1.3 Configuration Commands for Follow-Me Function (with Netw-Wide PIN). . . . . . . . . . . . . . 1351
132.18.2 PIN and Follow-Me in 1 Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1351
132.19 Restart Security of PIN/PCODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1351
133 PNT E for Connecting Standardized S0 Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1353
A31003-H3170-S103-6-7620, 02/2019
Contents
133.2 PNT E for Connecting Functional Station Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354

133.3 PNT E for Connecting Functional NV Station Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1355
133.4 PNT E for Connecting Video Conference Equipment With Two Calling Numbers . . . . . . . . . . . . . . . 1356
133.5 PNT E With Channel Bundling for NV Station Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1357
134 Public Address System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1359
134.2 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1359
134.2.1 SLMA Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1359
134.2.2 TMOM Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1360
134.2.3 TIE or CO trunk Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1360
134.3 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1360
134.4.1 SLMA Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1360
134.4.2 TMOM Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1361
134.4.3 TIE or CO Trunk Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1361
134.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1362
135 Redial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
135.1 Saved Number Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
135.1.1 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
135.2 Last Number Redialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
135.2.1 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
136 Repeat ID Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1365
136.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1365
136.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1366
137 S2 Station Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1367
137.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368
138 Smart Card Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1369
138.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370
138.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1371
139 Speaker Call - One-Way . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1373
139.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1373
139.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1373
139.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374
140 Special Ring Tone depending on Caller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1377
141 Speed Dialling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1379
141.1 Speed dialing, individual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1379
A31003-H3170-S103-6-7620, 02/2019
Contents
141.1.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1379

141.1.2 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1379
141.2 Speed Dialing, Central (SPDC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1379
141.3 Extended functions for central speed dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1380
141.3.1 4-digit speed dialing facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1380
141.3.2 5-digit speed dialing facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1382
141.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384
142 Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387
142.1 Adding a Station (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1389
142.2 Displaying Station Class of Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1389
142.3 Displaying a Station from a Specific Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390
142.4 Displaying Station Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390
142.5 Changing a Station’s COS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390
142.6 Station Number Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1391
142.6.2 Service Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1391
142.6.3 Generation (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1391
142.7 Swapping Station Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392
142.8 Changing the Station Port Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1393
142.9 Exchanging Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394
142.10 Station Port Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1396
143 Station Controlled Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1399
143.1.1 Hold a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1400
143.1.2 Pick a Call and add to Conference, or Create a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1401
143.1.3 Station Controlled Conference in the Private Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1401
143.1.4 Prevention of consultation, transfering and hold by networked conference party . . . . . . . . . . . . 1402
143.1.5 Starting a Conference using Keyset Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1402
143.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1403
143.2.1 Create and add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1403
143.2.2 Hold of a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
143.2.3 Pick a Call and Create a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
143.2.4 Pick a Call and add to the Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1406
143.2.5 Removal of a Conference Member. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1406
143.2.6 Optiguide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1406
143.2.7 Station Controlled Conference in the Private Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407
143.4 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1409
143.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1409
144 Station Relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1413
A31003-H3170-S103-6-7620, 02/2019
Contents

144.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414
145 Step by Step Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1415
145.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1415
145.2 Supported Hardware, Lines, Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1416
145.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1416
145.4 Basic Configuration Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1416
145.4.1 No Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1416
145.4.2 Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417
145.4.3 Outdial Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417
145.4.4 COT/COP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417
145.4.5 Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417
145.5 Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418
145.5.1 ECMA Protocol with Announcement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418
145.5.2 Dial Pulsing Circuits (DIUC64) with ANSWER from the Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . 1419
145.5.3 DTMF Circuits (DIUC64) with ANSWER from the Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1419
145.5.4 Dial Pulsing Circuits (TMEMW) with ANSWER from the Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . 1420
145.5.5 Dial Pulsing Circuits (DIUC64) without ANSWER from the Trunk . . . . . . . . . . . . . . . . . . . . . . . . 1421
145.5.6 DTMF Circuits (DIUC64) without ANSWER from the Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421
145.5.7 Dial Pulsing Circuits (TMEMW) without ANSWER from the Trunk . . . . . . . . . . . . . . . . . . . . . . . 1422
145.5.8 DTMF Circuits (TMEMW) without ANSWER from the Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1423
145.5.9 Configuration Data for Step by Step Dialing via ECMAV2 (Analog Dial Pulsing Circuit) . . . . . . . 1423
145.5.10 Configuration Data for Step by Step Dialing via ECMAV2 (DTMF analog) . . . . . . . . . . . . . . . . 1424
146 Suffix Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1425
146.2 Flashing Signal at AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427
146.3 Busy Override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427
146.4 TFZ Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427
146.5 EB5/NAL signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
147 Suppression of the FWD Destination at the Caller’s Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1433
147.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1434
148 Transfer before Answer ex Call State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1435
148.3 Effects on other features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1438
148.5 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1439
148.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1439
149 User Signaling for the U.S. Market . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1441
149.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1441
149.4.1 LED Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1441
149.4.2 Ring Cadences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1442
149.4.3 Tones on Display Phones: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1443
A31003-H3170-S103-6-7620, 02/2019
Contents
149.4.3.1 Campon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444

149.4.3.2 Trunk Dial Tone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
149.4.3.3 Confirmation Tone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
149.4.3.4 Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
149.4.3.5 Other loadware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1445
149.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1445
150 User-to-User Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1447
150.3.1 AMO batch for DSS1 terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1449
150.3.2 AMO batch for CMI and network-wide CHESE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1450
150.3.3 AMO batch for networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1450
150.3.3.1 Configuration of UUS1 Implicit: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1450
150.3.3.2 Configuration of UUS1 Explicit: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451
150.3.3.3 Configuration of UUS3: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451
150.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1452
151 Variable Call Forwarding No Reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455
151.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455
152 Witness Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457
152.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1458
153 Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1461
153.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1461
153.3 Comfort Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1463
153.3.1 Overview AC-WIN (DQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1463
153.3.2 Overview AC-Win MQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464
153.4 Nodes without an Attendant Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1465
153.4.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1466
153.5 Usage - Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467
153.5.1 Assign an Attendant (AC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467
153.5.2 Assign an Attendant Group (ATNDGR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467
153.5.3 Assign a Name to an ATND Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468
153.5.4 Remove an ATND from an ATNDGR and Delete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468
153.5.5 Change personal number of attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469
153.5.6 Change ATND Internal Access and Answer Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469
153.5.7 Add an ATND to an ATNDGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469
153.5.8 Internal Centralized Attendant Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469
153.5.9 External Centralized Attendant Services Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1470
153.6 Function-Enhancements for the Attendant Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1471
153.6.1 Priority Calculation and Queue Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1472
A31003-H3170-S103-6-7620, 02/2019
Contents

153.6.1.2 Service Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474
153.6.1.3 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1476
153.6.1.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478
153.6.2 Priority Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1480
153.6.2.2 Service Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1480
153.6.2.3 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1480
153.6.2.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1481
153.7 Automatic Night Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1481
153.7.3 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1482
153.7.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1482
153.8 Attendant Intercept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1483
153.8.3 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484
153.8.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1485
153.9 Extend Call to Paged User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1486
153.9.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1486
153.9.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1487
153.9.3.1 Extend Call to Paged User feature invocation from AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1487
153.9.3.2 Extend Call to Paged User feature invocation from AC-Win . . . . . . . . . . . . . . . . . . . . . . . . 1488
153.10 Remote Activation of Call Forwarding for Users at the Attendant Console . . . . . . . . . . . . . . . . . . . 1489
153.10.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1489
153.10.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1490
153.10.3 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1490
153.10.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1490
153.11 Attendant Control of Diversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
153.11.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
153.11.2 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
153.11.3 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
153.11.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1493
153.12 Displaying of the Source Dialling Number instead of Number of the Attendant Console . . . . . . . . . 1493
153.12.2 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1493
153.12.3 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1493
154 Attendant Light. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495
154.1.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495
154.1.2 Interworking with other features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496
154.1.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1497
154.2.1 Master Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1497
154.2.2 Code Hunt Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1498
154.2.3 Configure key layout for busy lamp field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1499
154.3 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1499
A31003-H3170-S103-6-7620, 02/2019
Contents
155 Call Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1501

155.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1503
156 Code Calling System Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505
156.1 CC in DISPLAY OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506
156.2 CC in VOICE ANNOUNCEMENT Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1507
156.3 CC in MEET-ME Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1507
156.4 Code Calling in MIXED MODE Operation with CODE DIGIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508
156.5 Code Calling in TRANSPARENT MODE Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508
157 General Night Switching Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1511
157.4 Expand a Night Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1513
157.5 Reduce a Night Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1513
157.6 Delete a Night Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1514
157.7 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1514
158 Multiple Code Calling System CCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517
158.1 CCM in Display Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518
158.2 CCM in Meet-me Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1519
158.3 CCM in Meet-me Operation with Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1520
158.4 Reversing the Number Display Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1520
158.5 Left-Justified/Right-Justified A-Number Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521
158.6 CCM with Block Separators and End-of-Block Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521
158.7 CCM with Code Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522
158.8 Parallel Ringing of Exchange Calls if FWD/FNANS Activated to CCM in Meet-me Operation . . . . . . 1523
158.9 Priority Signalling of Urgent Exchange Calls for CCM in Meet-me Operation . . . . . . . . . . . . . . . . . . . 1523
158.10 Announcements for CCM in Meet-Me Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1523
158.11 Display Number Modification with AMO KNMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1525
158.12 Multiple code calling of the same paging number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1527
158.13 Suffix dialing to CCM with busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1527
158.14 Paging with on-hook handset internally and throughout network . . . . . . . . . . . . . . . . . . . . . . . . . . . 1527
158.15 CTIME Timers for CCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1528
159 Remote Night Station Changeover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1531
159.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1532
160 Trunk Night Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1533
160.1.1 Console night service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1533
160.1.2 Group night service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534
160.1.3 Trunk night service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1535
160.2 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1535
160.3 AMO Usage Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1536
160.4 Generation (Examples) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1537
160.4.1 Trunk Night Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1537
160.4.2 Centralized Attendant Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1538
A31003-H3170-S103-6-7620, 02/2019
Contents
160.4.2.1 Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539

160.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1540
161 Universal Night Answer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1543
161.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545
162 ACD (Automatic Call Distriution) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1547
162.1 Enhanced Agent Feature Operation after Soft Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1547
162.1.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1548
162.2 Phantom Lines as Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1548
162.2.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549
162.2.3 AMO Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1550
162.2.3.1 Create a Phantom Agent Via Feature Access Code for Sign-Off. . . . . . . . . . . . . . . . . . . . . 1550
162.2.3.2 Create a Phantom Agent Via AMOs Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1550
162.2.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1551
162.3 PhoneMail Ports as Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1551
162.3.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1552
162.3.3 AMO Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1553
162.3.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554
162.4 Special Outpulsing Devices (SODs) as Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1555
162.4.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1555
162.4.3 AMO Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1556
162.4.3.1 Creation of SOD and Outpulsing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1556
162.4.3.2 Creation of SOD as Autologon Agent for Special Work Mode Activation. . . . . . . . . . . . . . . 1556
162.4.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1556
162.5 Silent/Tone Monitoring of Non-Agent Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557
162.5.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557
162.5.3 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557
162.6 Consultation Calls from Conference into ACD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558
162.6.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558
162.7 Honoring of Call Forwarding for ACD Routes Offsite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558
162.8 Automatic Call Acceptance (ACD Zip Tone) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558
162.8.2 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559
162.9 Personal Call Notification (AICS for ACD calls only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559
162.9.3 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1560
162.10 Display the A Number at the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1560
162.10.2 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
162.10.3 Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1562
A31003-H3170-S103-6-7620, 02/2019
Contents
162.11 Ringback Tone for Diverted Call to analog CallDirector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1562

162.11.2 Service Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1563
162.11.3 Generation (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1563
162.11.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564
162.12 Divert Call Request Support of Reroute Internal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564
162.12.1 Divert Call Requests if the Destination is a Trunk with Reroute Internal . . . . . . . . . . . . . . . . . . 1564
162.12.1.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1566
162.12.2 ACL Set Forward Command Support for Reroute Internal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1566
162.12.2.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1567
162.13 Application Populated Caller ID (APCID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1568
162.14 Displaying the ACD Pilot Number and Name for Outgoing System-Internal Calls. . . . . . . . . . . . . . . 1571
162.14.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1573
162.15 DNIT Number Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1574
163 Flexrouting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1577
163.1.1 The fundamental routing functions of the ACD package are: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1577
163.1.2 Server Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1577
163.1.3 The following is a short description of the features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1578
163.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1579
163.4.1 Defining ACD call numbers, groups and users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584
163.4.2 Defining routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1587
163.5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1591
164 Flexrouting Silent/Tone Monitoring PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601
164.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601
164.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1602
164.3.1 Feature Activation with Positive Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1602
164.3.2 Feature Activation with Negative Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1602
164.3.3 Feature Deactivation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1603
164.5 Feature Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604
164.7 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1606
165 Whisper Annoucement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609
165.2 Realization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609
A31003-H3170-S103-6-7620, 02/2019
Contents
165.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609

165.3.1 ACD WHISPER ANNOUNCEMENT Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609
165.3.2 Breakdown of Whisper monitor Connection - Monitoring Party . . . . . . . . . . . . . . . . . . . . . . . . . . 1611
165.3.3 Breakdown of Whisper Monitor Connection - Monitored Party / Non-Monitored Party . . . . . . . . 1612
165.3.4 Breakdown of Whisper monitor Connection - Monitor Party Wait State . . . . . . . . . . . . . . . . . . . 1612
165.3.5 Reestablishing the Whisper Monitor Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1613
165.3.6 Whisper Announcement Feature and Whisper Monitor Connections over a CC Soft Restart. . . 1613
165.4 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1613
165.5 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614
166 Announcement Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1615
166.1 Assignment of Announcement Unit for General Text (internal). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1615
166.2 Announcement Unit for Greeting Text and General Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1616
167 Music Source External. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1619
167.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1619
168 Synchronized Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1621
168.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1621
168.2 Connecting Announcement Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1627
168.2.1 Prerequisites, Interrelationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1630
168.3 Help for Setting Synchronized Announcements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1640
168.4 Possible Reasons why Announcements may not Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1647
168.4.1 General Requirements: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1647
168.4.2 Announcements for Attendant Call Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1649
168.4.3 Announcements for Calls to Multiple CCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1650
168.4.4 Announcements for Hunting Group Call Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1651
168.4.5 General Announcements if Called Station is Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1651
168.4.6 Announcement for Automatic Camp-on on Busy Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1652
168.4.7 General Announcements with call to station and no answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1653
168.4.8 Announcements for Suffix Dialing if Called Station is Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1654
168.4.9 Announcements for Suffix Dialing if Station User does not Answer . . . . . . . . . . . . . . . . . . . . . . 1655
168.4.10 Announcements for Direct Inward Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1656
168.4.11 Announcement for call to AC in night service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1656
169 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1659
170 Specific terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1661
171 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1663
172 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1665
172.1 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1665
172.2 Global switch configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1672
172.2.1 Global configuration for trunk searching (SMEO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1673
172.2.2 Global configuration for DSN Hotline (SMEO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1675
172.3 Announcements (via Musiphone) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676
172.4 Assignment of the Information Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1679
172.5 Assignment of Ringing Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1680
172.6 Basic Trunk Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1681
172.6.1 General Administration of T1 MOS (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1681
172.6.1.1 DIU2U for T1 MOS NI-2 Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1681
172.6.1.2 TMDNH for T1 MOS NI-2 Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1683
A31003-H3170-S103-6-7620, 02/2019
Contents
172.6.2 General Administration of T1 BOS (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1683

172.6.2.1 TMDNH for T1 BOS EMW TIE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1683
172.6.3 General administration for E1 CAS (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684
172.6.4 Outpulsing Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1686
172.6.5 Trunk Supervisory Preemption with E&M Wink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1686
172.6.6 Emergency Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1686
172.6.7 NI2 Precedence Level IE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1687
172.6.8 DISC MSG Information Cause Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1688
172.6.9 Signal Information Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1688
172.7 Calls in Queue to the Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1689
172.7.1 Assignment of the MLPP call queues with AMO-VFGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1689
172.7.2 Assignment of the MLPP call queues on AC-Win-MQ Application . . . . . . . . . . . . . . . . . . . . . . . . 1690
172.8 CDR Fields (SMEO). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1691
172.9 DSN Hotline Service (SMEO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1692
172.9.1 Protected Hotline Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1692
172.9.2 Pair Protected Hotline Calling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1693
172.9.3 Unprotected Hotline Receiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1693
172.9.4 Protected Hotline Receiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694
172.10 Outgoing and tandem call trace (SMEO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694
172.10.1 Creating a new list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694
172.10.2 Displaying the list of destination numbers that will be traced . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695
172.10.3 Adding a new destination number to the list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695
172.10.4 Deleting a number from the list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
172.10.5 Deleting the list of destination numbers to be traced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
172.11 Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
172.11.1 Change host to aLaw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
172.11.2 Change host to uLaw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
172.11.3 Law conversion on AP3700IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
172.11.4 Number Routing on US Military Bases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
172.11.4.1 Number Routing for 7-digit On-Base-Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
172.11.4.2 Number Routing for 5-digit On-Base-Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1698
172.11.4.3 7-digit On-Base-Number Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1698
172.11.4.4 5-digt On-Base-Number Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1699
172.11.5 Setting the Precedence-Digit representation and the Route Digit on CAS Outpulsing. . . . . . . . 1701
173 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1703
173.1 Originating User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1703
173.2 Destination User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704
173.2.1 Called MLPP subscriber is idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704
173.2.2 Called MLPP subscriber is busy (with camp on) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704
173.2.3 Called MLPP subscriber busy (without camp on) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704
173.3 Invocation and operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704
173.4 Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706
173.5 Precedence Call Diversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706
173.6 Precedence Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706
173.7 Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1707
173.8 Three Way Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1707
173.9 Defense Switched Network World Wide Numbering and Dialing Plan. . . . . . . . . . . . . . . . . . . . . . . . . 1708
173.10 Calls in Queue to the Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1708
173.11 Call Waiting for Anate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1708
A31003-H3170-S103-6-7620, 02/2019
Contents

173.11.4 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1709
174 Generic Switching Center Requirements (GSCR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711
174.1 Interswitch and Intraswitch Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711
174.2 Seven-Digit Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711
174.3 Ten-Digit Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711
174.4 Emergency Service 911 Conflict Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1712
175 Default values for COP and COT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1713
175.1 Default parameters for COP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1713
175.2 Default parameters for COT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1715
175.3 Variant table and value in the database for COP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1717
175.4 Variant table and value in the database for COT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719
176 Parameter Generation and Signaling for International Markets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1721
176.1 Exchange Traffic and Tie Traffic for UK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1721
176.2 Parameter Overview for UK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1722
176.3 Exchange Traffic and Tie Traffic for France . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1723
176.4 Parameter Overview for France . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1723
177 Organization of COP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1725
177.1 COP parameter description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1726
177.2 COP parameter usage for different signaling methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1736
177.2.1 Overview of COP for Alternating Current. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1737
177.2.2 Overview of COP for loop signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1738
177.2.3 Overview of COP for Tone Frequency Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1739
177.2.4 Overview of COP for E & M Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1741
177.2.5 Overview of COP for MOSIG/DP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744
177.3 Configurations for foreign countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1745
178 ALUL - A- to Mu- Law Convertor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1747
179 COTT - CO-Tone in Transit Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1749
180 NAAT - North America Analog Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751
181 Organization of COT parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1753
181.1 COT Parameter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1755
181.2 Examples of COT Parameter Initializations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1771
181.2.1 Digital exchange traffic via S0/S2 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1772
181.2.2 Digital main/satellite PBX traffic via S0/S2 interface (OpenScape 4000/OpenScape 4000) . . . . 1773
181.2.3 Digital tie-line traffic via S0/S2 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1776
181.2.4 Digital Inter-PBX traffic via S0/S2 Interface (OpenScape 4000/OpenScape 4000= Local Internal
Network). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1778
181.2.5 Main / Satellite PBX traffic with loop signalling or WTK signalling . . . . . . . . . . . . . . . . . . . . . . . . 1780
181.2.6 Digital exchange (CO) traffic with speed dialling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1783
181.2.7 Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784
181.3 Configurations for foreign countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1786
A31003-H3170-S103-6-7620, 02/2019
Contents
182 ADIU - Attenuation of DIUC trunk circuits (CIS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1787

183 AICF - ATND intercept if the call is identified as forwarded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1789
184 ANNC - Activate local announcement to calling system for incoming seizure of analog trunk . . 1791
185 ANS - Trunk signaling answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1793
186 ATRS - Activate network loop check with transit counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1795
187 BCNE - B-channel negotiation for EDSS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1797
188 BLOC - Signal "end-of-dial” to partner nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1799
189 BRAR - Backward Release (of an incoming CO call). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1801
190 CDN - Call Deflection network-wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1803
191 CFBN - Call Forward Busy network-wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1805
192 CFOS - Call forwarding programming for other subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1807
193 CFTR - Activate, deactivate and check routes for call forwarding in central office . . . . . . . . . . . . 1809
194 CFVA - Enable connectivity validation for call forwarding destinations in network . . . . . . . . . . . 1811
195 CTLN - Prevent controlled line and trunk selection in an external system . . . . . . . . . . . . . . . . . . . 1813
196 CTLS - Controlled trunk and line selection network-wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1815
197 CUG - Release Closed User Groups network-wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1817
198 DISN - Only display the dialed number on A station display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1819
199 DSIT - Disconnect Supervision for Incoming Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1821
200 DTNE - Provide external dial tone to calling system for incoming seizure . . . . . . . . . . . . . . . . . . . 1823
201 ETSC - UUS ETSI conform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825
202 FAX1 - Call forwarding from incoming FAX CO lines to Phonemail . . . . . . . . . . . . . . . . . . . . . . . . 1827
203 FAX2 - Call forwarding from incoming FAX CO lines to Phonemail . . . . . . . . . . . . . . . . . . . . . . . . 1829
204 FNAN - Enable rerouting for network-wide forwarding on no answer to source node . . . . . . . . . 1831
205 FWDN - Release rerouting for network-wide call forwarding to source node. . . . . . . . . . . . . . . . . 1835
206 ITRN - Internal traffic restriction group (ITR) network-wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1837
207 KNDI - Camp-on in DID calls (TC and TT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1839
208 KNOR - Knocking override possible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1841
209 LINC - Handling implicit numbers when connecting to a carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . 1843
210 LINO - Line with implicit number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1845
211 LPRN - Permanent station number suppression for EDSS1 CO . . . . . . . . . . . . . . . . . . . . . . . . . . . 1847
212 LRPM - Line to Phonemail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1849
213 MFCL - Line with MFC (Multi-Frequency Code) signaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1851
214 MICC - MCID call clearing control required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1853
215 MIIH - Make MCID here, print out MCID locally. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1855
216 MLPR - Multi-level precedence and preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1857
217 NAAT - North America Analog Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1859
218 NCT - Network Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1861
A31003-H3170-S103-6-7620, 02/2019
Contents
219 NCTP - Partner node cannot execute network-wide call forwarding after transfer . . . . . . . . . . . . . 1863
220 NIN2 - No multi-level precedence and preemption on trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1865
221 NITO - No intercept in networking transit lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1867
222 NLCR - Partner system sends no LCR authorizations in Voice or Fax service . . . . . . . . . . . . . . . . 1869
223 NLHT - No local hold tone, hold tone sent by remote system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1871
224 NLRD - Partner system sends no LCR authorizations in the Data service. . . . . . . . . . . . . . . . . . . . 1873
225 NMLT - No multi-level precedence and preemption on trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1875
226 NOFT - No Flag Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1877
227 NOHO - No Hold for NW Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1879
228 NORR - No rerouting with LCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1881
229 NOSD - No Simple Dialog Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1883
230 NOTO - No Tone for Unsuccessful Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1885
231 NOVC - No override on CO connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1887
232 NPIS - Numbering Plan ISDN on outgoing trunk calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1889
233 NPPR - Numbering Plan PRIVATE on outgoing trunk calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1891
234 NPUN - Numbering Plan UNKNOWN on outgoing trunk calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1893
235 NQNP - Neighboring node does not support CorNet-NQ network-wide call pickup . . . . . . . . . . . . 1895
236 NQPI - Neighboring node does not support CorNet-NQ network-wide call pickup information . . 1897
237 NTON - Do not connect dial tone or announcement for incoming seizure of analog circuits . . . . 1899
238 OHKQ - Off Hook Queuing for transit connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1901
239 PINR - Signal PIN features network-wide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1903
240 PRI - Network-wide prioritized control of incoming calls at ATND . . . . . . . . . . . . . . . . . . . . . . . . . . 1905
241 RCL -Recall to attendant console or to transferring party if user hangs up in consultation call. . 1907
242 RCLS - Recalls to ATND suppressed in node without attendant console . . . . . . . . . . . . . . . . . . . . 1909
243 RLIN - Receive Trailing LIN digits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1911
244 SANH - Synchronized Announcement of Non OpenScape 4000 Switch . . . . . . . . . . . . . . . . . . . . . 1913
245 SDID - Deactivate partial digit analysis in the device handler, activate single digit direct inward dialing
1915
246 SECO - Send Emergency Call Outgoing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1917
247 SIRI - Single ring burst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1919
248 SPAH - Park system and hold analog connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1921
249 SPCM - Define a speech-compressed trunk group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1923
250 SPSR - Identify lines for a Phone Mail or Voice Mail server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925
251 SUPN - Suppress name network-wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1927
252 T4WA - Level switching on T reference point for device class TMA4WIRE . . . . . . . . . . . . . . . . . . . 1929
253 TCC - Signal incoming calls on analog tie trunk circuits as trunk calls . . . . . . . . . . . . . . . . . . . . . . 1931
254 TCET - Through-connect a networking transit connection after call extend in call status. . . . . . . 1933
A31003-H3170-S103-6-7620, 02/2019
Contents
255 TGRE - Control LCR rerouting on the basis of cause values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935
256 TR6T -Tones are supplied as in a 1TR6 CO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1937
257 TNDV - Tone in end-of-dialing signals activates partner device of trunk . . . . . . . . . . . . . . . . . . . . 1939
258 TRBA - Transfer before answer to first connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1941
259 TWDS - Transfer Allowed without Disconnect Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1943
260 UUS1 - Implicit user-to-user signaling no. 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945
261 VCMN - Voice compression not allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1947
262 AOCC - Request charges per line for remote station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1949
263 CATR - Charge transfer via analog CO trunk circuits which are operated as tie trunk circuits in transit
1951
264 CCTN - Apply trunk number as A number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1953
265 CDBO - Set record point in network for call data recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955
266 CDFD - Call data recording for PNE lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1957
267 DFNN - Use default node number for trunk as a dummy source node number . . . . . . . . . . . . . . . 1959
268 DPRE - Send dial information actually sent to partner system as destination number with prefix digits
to call data recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1961
269 DSDL - Don’t send diversion LEG information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1963
270 ICZL - Incoming call data recording by zone or from line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965
271 ICZO - Incoming call data recording by zone only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1967
272 IICB - Ignore incoming billing information element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1969
273 LWNC - Line protocol without node number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1971
274 NCDR - No CDR-E-specific signaling messages to partner node . . . . . . . . . . . . . . . . . . . . . . . . . . 1973
275 NCHD - No charge data during call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975
276 SNBE - Send no billing element to the partner system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1977
277 TRSC - Trunk sends call charges to source node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1979
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
A31003-H3170-S103-6-7620, 02/2019
Contents
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
Feature Usage Examples - Overview
General Information
General Information
1 Feature Usage Examples - Overview

This chapter contains feature usage examples for the basic system.
In this section the usage and parameters of the relevant AMOs for each
application are shown. Please note that not all parameters are given, but often
only the most important ones. If you require further information on other
parameters, please refer to the AMO descriptions. The commands are shown as
keyword-oriented commands (parameter acronym followed by equals sign
followed by parameter value). Specific parameter values are only given in cases
where they are necessary for the application concerned.
Beneath the table of content the content is sorted to the following 14 subjects:
Subject ACD
ACD (Automatic Call Distribution)

Flexrouting
Flexrouting Silent/Tone Monitoring PIN
Whisper Annoucement
Subject Applications
Announcement Unit
Music Source External
Synchronized Announcements
LRPM - Line to Phonemail
SPSR - Identify lines for a Phone Mail or Voice Mail server
Subject Attendant Console
Attendant Console
Attendant Light
Call Retrieval
Code Calling System Basic
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
General Night Switching Options

Ignore call forwarding
Multiple Code Calling System CCM
Remote Night Station Changeover
Trunk Night Service
Universal Night Answer
AICF - ATND intercept if the call is identified as forwarded
CFOS - Call forwarding programming for other subscribers
NIN2 - No multi-level precedence and preemption on trunk
NITO - No intercept in networking transit lines
PRI - Networkwide prioritized control of incoming calls at ATND
RCL -Recall to attendant console or to transferring party if user hangs up
in consultation call
RCLS - Recalls to ATND suppressed in node without attendant console
Subject Call Detail Recording - Basic Information
Call Detail Recording

Call Detail Transmission
Call Detail Information for Heterogeneous Networks
Subject Call Detail Recording - Usage Examples
CDRE - Call Detail Recording enhanced

Call Detail Recording enhanced Traffic
Call Detail Recording - Account Code
Call Charge Data Display
Call charge data - immediate output
Call charge output
Call Charge Recording-Elapsed Time Display
Central Configuration
Charge Pulse Metering & Sending to Analog Stations
Default Values
DPS Interface Data
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
INFO 2000 Outcalls

Per-Second Invoicing with Prices in 1/100000 Currency Units
Station Number Modification
Subject Call Detail Recording - COT Parameter
AOCC - Request charges per line for remote station

CATR - Charge transfer via analog CO trunk circuits which are operated as
tie trunk circuits in transit
CCTN - Apply trunk number as A number
CDBO - Set record point in network for call data recording
CDFD - Call data recording for PNE lines
DFNN - Use default node number for trunk as a dummy source node number
DPRE - Send dial information actually sent to partner system as destination
number with prefix digits to call data recording
DSDL - Don’t send diversion LEG information
ICZL - Incoming call data recording by zone or from line
ICZO - Incoming call data recording by zone only
IICB - Ignore incoming billing information element
LWNC - Line protocol without node number
NCDR - No CDR-E-specific signaling messages to partner node
NCHD - No charge data during call
SNBE - Send no billing element to the partner system
TRSC - Trunk sends call charges to source node
Subject COP
COP and COT Parameter

COP Parameter
ALUL - A- to Mu- Law Convertor
COTT - CO-Tone in Transit Traffic
NAAT - North America Analog Trunks
Default values for COP and COT
Organization of COP parameters
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
Parameter Generation and Signaling for International Markets
Subject COT

COT Parameter
ADIU - Attenuation of DIUC trunk circuits
AICF - ATND intercept if the call is identified as forwarded
ANNC - Activate local announcement to calling system for incoming
seizure of analog trunk
ANS - Trunk signaling answer
ATRS - Activate network loop check with transit counter
BCNE - B-channel negotiation for EDSS1
BLOC - Signal "end-of-dial” to partner nodes
BRAR - Backward Release (of an incoming CO call) if a system-initiated
recall to the attendant or night station is not answered
CDN - Call Deflection network-wide
CFBN - Call Forward Busy Networkwide
CFTR - Activate, deactivate and check routes for call forwarding in central
office
CFVA - Enable connectivity validation for call forwarding destinations in
network
CTLN - Prevent controlled line and trunk selection in an external system
CTLS - Controlled trunk and line selection network-wide
CUG - Release Closed User Groups network-wide
DISN - Only display the dialed number on A station display
DSIT - Disconnect Supervision for Incoming Trunk
DTNE - Provide external dial tone to calling system for incoming seizure
ETSC - UUS ETSI conform
FAX1 - Call forwarding from incoming FAX CO lines to Phonemail
FNAN - Enable rerouting for network-wideforwarding on no answer to
source node
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
FWDN - Release rerouting for network-wide call forwarding to source

node
ITRN - Internal traffic restriction group (ITR) network-wide
KNDI - Camp-on in DID calls (TC and TT)
KNOR - Knocking override possible
LINC - Handling implicit numbers when connecting to a carrier
LINO - Line with implicit number
LPRN - Permanent station number suppression for EDSS1 CO
LRPM - Line to Phonemail
MFCL - Line with MFC (Multi-Frequency Code) signaling
MICC - MCID call clearing control required
MIIH - Make MCID here, print out MCID locally
MLPR - Multi-level precedence and preemption
NAAT - North America Analog Trunks
NCT - Network Call Transfer
NCTP - Partner node cannot execute network-wide call forwarding after
transfer
NITO - No intercept in networking transit lines
NLCR - Partner system sends no LCR authorizations in Voice or Fax
service
NLHT - No local hold tone, hold tone sent by remote system
NLRD - Partner system sends no LCR authorizations in the Data service
NMLT - No multi-level precedence and preemption on trunk
NOFT - No flagtrace
NOHO - No Hold for NW Conference
NORR - No rerouting with LCR
NOSD - No Simple Dialog Available
NOTO - No Tone for Unsuccessful Call
NOVC - No override on CO connections
NPIS - Numbering Plan ISDN on outgoing trunk calls
NPPR - Numbering Plan PRIVATE on outgoing trunk calls
NPUN - Numbering Plan UNKNOWN on outgoing trunk calls
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
NQNP - Neighboring node does not support CorNet-NQ network-wide

call pickup
NQPI - Neighboring node does not support CorNet-NQ network-wide call
pickup information
NTON - Do not connect dial tone or announcement for incoming seizure
of analog circuits
OHKQ - Off Hook Queuing for transit connections
PINR - Signal PIN features network-wide
PRI - Network-wide prioritized control of incoming calls at ATND
RCLS - Recalls to ATND suppressed in node without attendant console
RLIN - Receive Trailing LIN digits
SANH - Synchronized Announcement of Non HiPath Switch
SDID - Deactivate partial digit analysis in the device handler, activate
single digit direct inward dialing
SECO - Send Emergency Call Outgoing
SIRI - Single ring burst
SPAH - Park system and hold analog connection
SPCM - Define a speech-compressed trunk group
SPSR - Identify lines for a Phone Mail or Voice Mail server
SUPN - Suppress name network-wide
T4WA - Level switching on T reference point for device class TMA4WIRE
TCC - Signal incoming calls on analog tie trunk circuits as trunk calls
TCET - Through-connect a networking transit connection after call extend
in call status
TGRE - Control LCR rerouting on the basis of cause values
TR6T -Tones are supplied as in a 1TR6 CO
TNDV - Tone in end-of-dialing signals activates partner device of trunk
TRBA - Transfer before answer to first connection
TWDS - Transfer Allowed without Disconnect Supervision
UUS1 - Implicit user-to-user signaling no. 1
VCMN - Voice compression not allowed
AOCC - Request charges per line for remote station
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
CATR - Charge transfer via analog CO trunk circuits which are operated
as tie trunk circuits in transit
CCTN - Apply trunk number as A number
CDBO - Set record point in network for call data recording
CDFD - Call data recording for PNE lines
DFNN - Use default node number for trunk as a dummy source node
number
DPRE - Send dial information actually sent to partner system as
destination number with prefix digits to call data recording
DSDL - Don’t send diversion LEG information
ICZL - Incoming call data recording by zone or from line
ICZO - Incoming call data recording by zone only
IICB - Ignore incoming billing information element
LWNC - Line protocol without node number
NCDR - No CDR-E-specific signaling messages to partner node
NCHD - No charge data during call
SNBE - Send no billing element to the partner system
TRSC - Trunk sends call charges to source node
COT parameter organization
Default values for COP and COT
Subject Groups
Audible Ringing on Rollover Lines

Call Pickup
CHESE - Integrated Executive/Secretary System
CHESE/Team Functions Network-wide
Class of service switch-over COSX
COM Group Call
COM Group Speaker Call -Two-Way
Hunt Group
Hunt group network-wide
Keyset Preview Key
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
Integrated key functionality / multi line access

Parallel Ringing - One Number Service (ONS)
Personal Device Group
Speaker Call - One-Way - Broadcast
CUG - Release Closed User Groups networkwide
Subject OpenScape 4000 Assistant
Account Management
Subject IP
Access Point Emergency (APE)

Different Time Zones (DTZ)
H323 / H323 Annex Connectivity
HiPath Cordless IP
HiPath Feature Access (HFA)
Gateways HG 3500 and HG 3575
IP Distributed Architecture (IPDA)
IP Terminals
Large Enterprise Gatekeeper (LEGK)
Mobile HFA
OpenScape Access
OpenScape 4000 SoftGate
Payload Switching DMC
RG 8350a
Separate LAN Connectivity for Administration and VoIP
Signaling and Payload Encryption (SPE)
SIP Connectivity
T.38 Fax
Subject Multi Level Precedence and Preemption (MLPP)
Administration
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
Feature Description
Generic Switching Center Requirements (GSCR)
Overview
Specific terminology
User interface
Subject Networking
Basic Principles
Alternate Routing on Error
Analog Trunking USA
ANIF Automatic Number Identification
Automatic Node Topology Detection
Cornet NQ interworking with DPNSS1
CorNet-VN (CorNet Virtual Networking)
COP Parameter
ALUL - A- to Mu- Law Convertor
COTT - CO-Tone in Transit Traffic
COT Parameter
ANS - Trunk signaling answer
ATRS - Activate network loop check with transit counter
BLOC - Signal "end-of-dial” to partner nodes
CDN - Call Deflection Networkwide
CFBN - Call Forward Busy network-wide
CTLN - Prevent controlled line and trunk selection in an external system
CTLS - Controlled trunk and line selection networkwide
CUG - Release Closed User Groups networkwide
DTNE - Provide external dial tone to calling system for incoming seizure
FNAN - Enable rerouting for networkwide forwarding on no answer to
source node
FWDN - Release rerouting for networkwide call forwarding to source
node
ITRN - Internal traffic rescriction group (ITR) networkwide
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
KNOR - Knocking override possible

LPRN - Permanent station number suppression for EDSS1 CO
MFCL - Line with MFC (Multi-Frequency Code) signaling
NCT - Network Call Transfer
NCTP - Partner node cannot execute networkwide call forwarding after
transfer
NLCR - Partner system sends no LCR authorizations in Voice or Fax
service
NLRD - Partner system sends no LCR authorizations in the Data service
NOHO - No Hold for NW Conference
NORR - No rerouting with LCR
NOTO - No Tone for Unsuccessful Call
NOVC - No override on CO connections
NPIS - Numbering Plan ISDN on outgoinging trunk calls
NPPR - Numbering Plan PRIVATE on outgoinging trunk calls
NPUN - Numbering Plan UNKNOWN on outgoinging trunk calls
NQNP - Neighboring node does not support CorNet-NQ networkwide call
pickup
NQPI - Neighboring node does not support CorNet-NQ networkwide call
pickup information
OHKQ - Off Hook Queuing for transit connections
PINR - Signal PIN features networkwide
SANH - Synchronized Announcement of Non HiPath Switch
SIRI - Single ring burst
SPAH - Park system and hold analog connection
SUPN - Suppress name networkwide
T4WA - Level switching on T reference point for device class TMA4WIRE
TCET - Through-connect a networking transit connection after call extend
in call status
TGRE - Control LCR rerouting on the basis of cause values
TR6T -Tones are supplied as in a 1TR6 CO
TNDV - Tone in end-of-dialing signals activates partner device of trunk
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
TRBA - Transfer before answer to first connection

Country-Specific Connection Techniques With Analog Trunks
Customer Groups, Shared Systems CUG
DTMF Dialing
ECMA QSIG Protocol
EDSS1 System Interface / Trunk Interface
EURO-ISDN Exchange Interface
Features available throughout the network
Hunt group network-wide
ISDN protocol variants
LCR (Least Cost Routing)
LCR Rerouting
MFC-R2 Signaling
National ISDN Basic Rate Interface (NI BRI)
Network Loops
Number Modification
PIN and Follow-Me Network-Wide
Preventing connections
Public PRI Networking
Public Network Exchange Signalling DTMF (Suffix Dialling)
RefTa Synchronisation
Restricted Call Duration for Transit Calls
Route Optimization
S0/S2 Trunk Parameterization
Satellite Paths Limiting
Screening on the EDSS1 Trunk Interface
Single Point of Access (SPoA)
Transmission and Loss Plan
Trunk Access with the STMA When Using the ATM Networking V2.0 Feature
Trunk to Trunk Supervised Connection
Virtual Numbering (VNR)
Voice Compression
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
Subject Non Voice
Fax Machine
Number Conversion
Subject System
AMO Authorizations in the PBX

AMO Caching
Call Forwarding
Device Switching
DIMSU Warning
Editing Line Circuits
Emergency Call
Extended Access Protection (Login)
LAN Monitoring
Flash Boards: Load Behavior
Loadware Variants
Logical Partitioning in HiPath 4000 Systems
Optional Patches
Partial Digit Analysis TWABE
Power Fail Interrupt Settings
Routes
Recovery of peripheral units
Subscriber Search Enhancements
System Backup & Restore
Timers
KNDI - Camp-on in DID calls (TC and TT)
MLPR - Multi-level precedence and preemption
NMLT - No multi-level precedence and preemption on trunk
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
Subject Terminals
Attendant Light
Automatic Number Identification (ANI)
Autoset Relocate
Babyphone
Block Dialing
Buzz
Call forward no reply after transfer
Call forward no reply and rerouting
Call Hold analog
Call ID (Name and Number) on Analog Port with PRI NI2 Calls
Calling Line Identification Enhancements
Calling Line Ident. Restriction (CLIR)
Calling Line Identification Translation
Call log for optiPoint 410/420, OpenStage
Call Parking
Call Waiting for Anate
Connect Key
Controlled Trunk and Line Selection
Data Security at the Terminal
Desktop Callback Idle Display Option
Dictation Equipment DICT
Digital Station with S0 Interface
Direct Station Selection (DSS)
Disable Flash on Analog Phones
Disable MW Lamps on OPS
Display of calling party number in Call Center
DNIS (Directory Number Identification Services)
DSS 1 Terminals
E911 Emergency Call
Emergency Call
Emergency Override/Disconnect
Entrance Telephone with Door Opener
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
EURO-ISDN Terminals
Executive features
Flexible optiPoint Display
Hotline/Off-Hook Recal
Ignore call forwarding
Malicious Call Identification/Tracing
Manual Hold of Consultation
Multilingual User Interface
Name and Organization to a Number (ORG Assigning)
Number Identification
On Hook Transfer per User or a Group of Users
OpenStage TDM
OpenStage Busy Lamp Field for optiPoint 500
PIN (Personal Identification Number)
PNT E for Connecting Standardized S0 Telephones
Public Address System
Redial
Repeat ID Key
S2 station configuration
Smart Card Application
Speaker Call - One-Way
Special Ring Tone depending on Caller
Speed Dialing
Stations
Station Controlled Conference
Station Relocation
Step by Step Dialing
Suffix-Dialing
Suppression of the FWD destination at the caller’s display
Transfer before Answer ex Call State
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
User Signaling for the U.S. Market

User-to-User Service
Variable Call Forwarding No Reply
Witness facility
DISN - Only display the dialed number on A station display
ETSC - UUS ETSI conform
MICC - MCID call clearing control required
MIIH - Make MCID here, print out MCID locally
UUS1 - Implicit user-to-user signaling no. 1
A31003-H3170-S103-6-7620, 02/2019
al_anw_en.fm
General Information
A31003-H3170-S103-6-7620, 02/2019
_highlights_hinweise_en.fm
Highlights and Hints
Highlights
2 Highlights and Hints
2.1 Highlights
Current issue
• New features with OpenScape 4000 V7 R1:
– Attendant Light (see Chapter 154, “Attendant Light”)
– RQ00033609: Emergency call (see Chapter 117, “Emergency Call”)
• Important information regarding the feature Automatic Node Topology

Detection (see Section 26.3, “Service Information”).
• Restriction to malicious call identification added (see Section 125.2, “Service

Information”).
• Enhancements in MLPP for feature DSN Hotline (see Section 172.2.2,

“Global configuration for DSN Hotline (SMEO)”).
• Product Renaming HiPath 4000 V7 -> OpenScape 4000 V7
Issue 01
• New feature restricted call duration for transit calls. For more information
please refer to Chapter 48, “Restricted Call Duration for Transit Calls”.
2.2 Hints
Please have a look at the release notes / sale release documentation for the
complete released feature content.
A31003-H3170-S103-6-7620, 02/2019
_highlights_hinweise_en.fm
Highlights and Hints
Hints
A31003-H3170-S103-6-7620, 02/2019
amober_en.fm
System
System
3 AMO Authorizations in the PBX
3.1 Feature Description

A "required execution authorization", called a class, is permanently assigned to
each AMO action. A user can only start an AMO action if the class of the AMO
action is included in the set of his or her execution rights. If the authorizations are
not sufficient, an error message appears and the user cannot perform the AMO
action.
The system administrator assigns one or more of the execution rights to each
user ID; these authorize the user of the ID to execute specific 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:
Authorizations for
normal users
reserve
Authorization of the
ROOT ID
Authorizations for
1 = execution allowed special users
0 = execution not allowed
Figure 1 Breakdown of User Execution Rights
It is possible to use the AMO AUTH at any time to grant and change the AMO
authorizations for individual actions if the user has the authorization needed to do
this (see chapter with log in concept).
3.2 Service Information

• If no other parameters are specified when calling the AMO AUTH, the user
receives a list of all system AMOs with their corresponding actions.
• It is possible to administer the classes of the AMO actions.
• As a default, a user must have an ID with class of service 10, which is usually
the ROOT ID, to change the classes of service.
• Any change to a class affects both AMO languages simultaneously.
A31003-H3170-S103-6-7620, 02/2019
amober_en.fm
Generation (Example)
• To be able to perform an AMO action, the user must explicitly have the
authorization because there is no longer a hierarchy (for example, class 4
does not automatically include classes 1 to 3).
3.3 Generation (Example)

• Requesting all AMO action classes in a system:
DISPLAY-AUTH:;
H500: AMO AUTH STARTED
CLASS OF
AMO ACTION SERVICE
---------------------------
ACMSM ADD 4
ACMSM CHANGE 4
ACMSM DELETE 4
ACMSM DISPLAY 4
ACMSM REGENERATE 4
AFR ACTIVATE 5
...
• Display the current AMO action classes for the AMO LDPLN:
DISPLAY-AUTH:AMO="LDPLN";
• Change the current AMO action class for "ADD" for the AMO LDPLN to 5:
CHANGE-AUTH:AMO="LDPLN",ACTION="ADD",CLASS=5;
3.4 Relevant AMOs
AMO Parameter Sprache/ Beschreibung/ Description

Language
AUTH AMO d Noun: Auswahl eines AMOs
AMO e Noun: selection of an AMO
AKTION d Verb: Auswahl einer Aktion innerhalb des
AMOs
ACTION e verb: selection of an action within the AMO
TYP d Verzweigunsparameter fuer
Ausgabeeinschraenkung
TYPE e branching parameter for restricting output
KLASSE d neue Ausfuehrungsberechtigung
A31003-H3170-S103-6-7620, 02/2019
amober_en.fm
Relevant AMOs

Language
CLASS e new execute permission
A31003-H3170-S103-6-7620, 02/2019
amober_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
amo_caching_en.fm
AMO Caching
Overview
4 AMO Caching
4.1 Overview
The following description of the new overlay handling concept is based on the
AMO overlay handling, but the concept in general effects all kind of overlays.
Memory
TDCSU OVERLAY <RELOVL;

APSN SBCSU Delete the Overlay
PERSI Memory
SDAT
Loaded AMO’s remain in a cache memory until there is nor more free space for new
ones to be loaded or the system command RELOVL to remove the overlay memeory
is issued.
With AMO DBC the memory for the overlay can be configured
AMO Subsystems are kept loaded until a predefined limit is exceeded even if they
are still not in use. The limit is defined by the number of slots (selectors) and the
amount of memory all loaded subsystems occupy.
The limits for SLOT and MEM can be defined with new parameters of AMO DBC
processor specific (ADPSLOT, SWUSLOT, MONOSLOT, ADPMEM, SWUMEM,
MONOMEM). If the parameter values are set to zero, the old behaviour is
performed.
System command RELOVL

The new overlay handling concept requires the new command RELOVL to
release all currently loaded overlays by user request. RELOVL is a system
command like the well known system commands TSN, BREAK, etc. and can be
entered any time these commands can be entered. This is at
• session input prompt "<"
• system session prompt "PLEASE ENTER COMMAND <<"
RELOVL will also work in the case of old overlay handling behaviour (zero values
for SLOT and MEM).
When RELOVL is entered by a user
A31003-H3170-S103-6-7620, 02/2019
amo_caching_en.fm
AMO Caching
Service Information
• all overlays that are still not in use are released immediately
• all overlays which are still in use are marked to be released after the last using
process ended
• a new process which wants to use a marked overlay will be delayed or

rejected until the marked overlay is released

• With EXEC- DBC a standard configuration is made depending on the system
type
• The Technician may only change the configuration under the instructions of
developement.
• When the memory is to small administration runs slower.
• When the values for Overlay are set to zero then the old procedure is used.
4.3 AMO Usage

CHANGE-
DBC:ADPSLOT=200,SWUSLOT=200,MONOSLOT=200,ADPMEM=10,SWUMEM=10,MON
OMEM=10;
4.4 Relevant AMOs

Language
DBC ADPSLOT d Anzahl der Slots für den ADP
ADPSLOT e Number of slots for ADP processors
SWUSLOT d Anzahl der Slots für die SWU
SWUSLOT e Number of slots for SWU processors
MONOSLOT d Anzahl der Slots bei Mono Prozessoren
MONOSLOT e Number of slots for mono processors
ADPMEM d Overlay Speicher für den ADP (vielfaches
von 100KB)
ADPMEM e Overlay memory for ADP (Multiple of 100
KB)
SWUMEM d Overlay Speicher für die SWU (vielfaches
von 100KB)
A31003-H3170-S103-6-7620, 02/2019
amo_caching_en.fm
AMO Caching
Relevant AMOs

Language
SWUMEM e Overlay memory for ADP (Multiple of 100
KB)
MONOMEM d Overlay Speicher für den Monoprozessor
(vielfaches von 100KB)
MONOMEM e Overlay memory for Mono processors
(Multiple of 100 KB)
RELOL d System Kommando zum Löschen des
V Overlay-Speichers
MONOMEM e System command to erase the overlay
memory
A31003-H3170-S103-6-7620, 02/2019
amo_caching_en.fm
AMO Caching
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
devswit_en.fm
Device Switching
5 Device Switching
• Activate a terminal
AC-DSSU:[ONTYPE=param],STNO=number,STNO=number,SVC=param;
• Reset a terminal:
RESTART-DSSU:TYPE=STNO,STNO=number,
The commands DEACTIVATE and ACTIVATE are always combined in one
job, whereby OFFTYPE=DI and ONTYPE=AUL.
IMPORTANT: The SVC parameter is only required if a terminal is connected

to a S0-Bus.
• Activate station line circuit

AC-DSSU:[ONTYPE=param],TYPE=PEN,PEN=pen;
• Deactivate a station line circuit by specifying a station number
DEA-DSSU:[OFFTYPE=param],TYPE=STNO,STNO=number;
• Reset a terminal:
RESTART-DSSU:TYPE=PEN,PEN=lage;
The commands DEACTIVATE and ACTIVATE are always combined in one
job, whereby OFFTYPE=DI and ONTYPE=AUL
IMPORTANT: Functional S0-bus terminals cannot be switched separately.
• Deactivate a station line circuit

DEA-DSSU:[OFFTYPE=param],TYPE=PEN,PEN1=pen,REFOFF=param;
IMPORTANT: The REFOFF parameter is only relevant if the circuit is the

current reference clock supplier.
The 2nd b-channel of an S0-bus can be deactivated and activated separately.

AC-DSSU:TYPE=BCHANS0, PEN1=pen; 
DEA-DSSU:TYPE=BCHANS0,PEN1=pen;
The parameters ONTYPE and OFFTYPE are automatically set internally by
the DSSU AMO.
• If a circuit is deactivated with soft blocking (OFFTYPE=DC), and the circuit in

question is a voice compression destination, the appropriate partner circuit of
the VCM board is also soft-blocked.
DEA-DSSU:OFFTYPE=DC,TYPE=PEN,PEN1=port equipment number;
A31003-H3170-S103-6-7620, 02/2019
devswit_en.fm
Device Switching
• When (re)activating a circuit which is a voice compression destination, the

appropriate partner circuit of the VCM board is also (re)activated.
AC-DSSU:[ONTYPE=param],TYPE=PEN,PEN1=port equipment number;
A31003-H3170-S103-6-7620, 02/2019
dimsu_warning_en.fm
DIMSU Warning
Feature Description
6 DIMSU Warning

Requirements:
An alarm is created when DIMSU parameters usage initiated by AMOs or by

subscriber activities approaches 90 % or 100% or if 10% of DIMSU parameter is
available again.
When the DIMSU parameters EXTNAME, NAME, ORG, CFWDEST, KEYSYS,

STN, OPTCC, OPTEXP, DPLNCD, PUGR, ACDAGT, ACDGRP, ACDLOGON,
ACDPRIM, ACDRT, ACDRTX, ACDSHIFT, DNI, DPDNI reach 90% of usage a
minor alarm is to be created. A major alarm indicates that 100% of a DIMSU
parameter is used. If 10% are available again the previously activated alarm has
to be reset.
AMOs using memory of the DIMSU parameters are:
• AMO PERSI,
• AMO ZIEL,
• AMO ACTDA,
• AMO KCSU,
• AMO SBCSU,
• AMO SXSU,
• AMO AUN,
• Flexrouting AMO ACDRT,
• AMO ACDRS-rs,
• AMO ACDRS-ds and
• AMO DNIT.
Subscriber adtivities:
Activate a call forwarding destination or logging on/off of ACD agents.
A31003-H3170-S103-6-7620, 02/2019
dimsu_warning_en.fm
DIMSU Warning
Service Information

DB calculates the percentage of usage of the DIMSU parameters and sends a
message to SysDep to generate an alarm when 90%, 100% are used or 10% are
free again. To avoid an overflow of messages only one 90%-message is sent.
This is triggered by a flag per parameter. For this purpose 256 bytes of
DB_D_RESERVE_CC_TBL (10) are used.
The flags are reset after a restart (reload, hard restart or soft restart). That means
that the alarm messages could occur again, when the DIMSU parameter are used
although they has been sent already before the restart.
If the value of a DIMSU parameter is changed by AMO DIMSU the flags are reset.
The alarm message could occur again afterwards.
The existing SWU central alarm 24 (SYSTEM MESSAGES) will be assigned to

the DIMSU warning messages. The error counter of this alarm will be
incremented by 8 in case of 90% DIMSU parameter usage, by 10 in case of 100%
usage and it will be reset to 0 if 10% are free again. After proper setting of VADSU
(see administration part) this results minor, major or no alarm depending on the
DIMSU warning messages.
Examples for the alarm messages are:

• Minor alarm:
F4016 M4 N0062 NO ACT BPA DB ADVISORY 06-11-23 13:35:16
ALARM CLASS:CENTRAL:024
FORMAT:33
90% OF DIMSU PARAMETER ORG/ORG USED
• Major alarm:
FORMAT:33
100% OF DIMSU PARAMETER ORG/ORG USED
• No alarm (alarm is reset):
FORMAT:33
10% OF DIMSU PARAMETER ORG/ORG AVAILABLE AGAIN
A31003-H3170-S103-6-7620, 02/2019
dimsu_warning_en.fm
DIMSU Warning
6.2.1 Restrictions
This feature is not possible when the optional diagnosis patches s20362, s20405,
s20416, s20417, s20419 with activation flag 52 are active, because these
patches use DB_D_RESERVE_CC_TBL too.
6.2.2 Remarks
For DIMSU parameter values < 10 the percentage figures in the first and third
alarm messages are not exact.

The settings for the SWU cantral alarm 24 (SYSTEM MESSAGES) has to be
changed at each customer who needs the alarm in case of DIMSU warning:
CHANGE-
VADSU:ALARMGR=CENTRAL,ALARMNO=24,THRESHD1=8,THRESHD2=10,TIME1=10
,TIME2=10;
Manual deletion of the alarm might be necessary after changing the DIMSU
parameters:
DELETE-GRA:UNIT=BP,ALARMNO1=24;
6.4 Relevant AMOs

Language
VADSU SCHWELL1 d Schwellwert fuer nichtdringenden Alarm
THRESH1 e threshold for minor alarm
VADSU SCHWELL2 d Schwellwert fuer dringenden Alarm
THRESH2 e threshold for major alarm
VADSU ZEIT1 d Validierungszeit fuer nichtdringenden Alarm
TIME1 e validation time for minor alarm
VADSU ZEIT2 d Validierungszeit fuer dringenden Alarm
TIME2 e validation time for major alarm
GRA ALARMNR1 d Alarmnummer 1
ALARMNO1 e Alarm number 1
A31003-H3170-S103-6-7620, 02/2019
dimsu_warning_en.fm
DIMSU Warning
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
satz_en.fm
Introduction
7 Editing Line Circuits
7.1 Introduction
You can use AMO TACSU, AMO TDCSU and AMO TSCSU to configure and edit
the line circuits in an existing trunk group.
The line-specific parameters are grouped into various classes and are assigned
with the AMO COP (Class of Parameter). The call processing parameters of the
line circuits are assigned with the AMO COT (Class of Trunk).
The COS (class-of-service) is relevant for transit and satellite PABX traffic.
Only the direct trunk access and tie-trunk classmarks are evaluated. If you want
to prevent a trunk from being seized with a tie trunk, you must remove the direct
trunk access classmark from the tie trunk’s COS (AMO COSSU).
Use the AMO BUEND to define a trunk group. All line circuits in a trunk group
must have identical properties. The AMO TACSU, AMO TDCSU and AMO
TSCSU are used to assign line circuits to a trunk group. You can use the AMO
BUEND’s NO parameter to set the maximum number of line circuits/B channels
to be configured. Changes to line circuit parameters are automatically saved by
the AMO TACSU, AMO TDCSU and AMO TSCSU to the memories of all line
circuits assigned to this trunk group.
Outgoing routes are defined with the AMO RICHT and THE LCR AMOs.
A trunk group may be assigned to several routes.
However, a line circuit or a B channel group may only be assigned to one trunk
group.
AMO TACSU
The AMO TACSU handles all analog trunk circuits, tie-line circuits and satellite
PABX tie trunks.
AMO TDCSU
The AMO TDCSU handles the digital circuits (S0, S1 or S2).
AMO TSCSU
The AMO TSCSU edits all line circuits for special configurations (APSE).
A31003-H3170-S103-6-7620, 02/2019
satz_en.fm
Adding an Incoming Line Circuit
7.2 Adding an Incoming Line Circuit
7.2.1 Analog Line Circuits

• Add the module configuration data (peripheral line module):
AD-
BCSU:MTYPE=PER,LTU=number,SLOT=number,PARTNO=string,[LWVAR=st
ring];
IMPORTANT: As a rule, line modules are loaded with the loadware for
Germany. Some modules, however, require different loadware variants in
order to comply with PTT requirements in foreign countries (e.g. SLMA
Q2141-X). The parameter ’LWVAR’ can be used in order to specify the
required loadware variant when the modules are configured. For a list of
possible loadware variants for each module, please consult the appropriate
module description. Once the module has been configured, the loadware
variant can be changed with the AMO ZAND.
• Assign a class of service:

AD-COSSU:AVCE=param;
• Assign a class of parameter (device handler parameters):
AD-COP:PAR=param;
• Assign a class of trunk
AD-COT:PAR=param;
• Lines for incoming traffic only are normally not assigned to trunk groups.
• Assign an analog line circuit:

AD-
TACSU:PEN=pen,COTNO=number,COPNO=number,LCOSV=number,LCOSD=nu
mber, DEVTYPE=<circuit_type>,DEV=<circuit_type>;
7.2.2 Digital Line Circuits

Digital line circuits that signal incoming traffic with ANY_CHANNEL (for example,
connections to fax servers) require special configuration for incoming traffic:
• Each line circuit must be configured in a separate trunk group.
• As usual, these trunk groups are grouped together to form an LCR route for
outgoing traffic (as described under LCR).
• Afterwards, each of these trunk groups must also be assigned an individual

route (AMO RICHT).
A31003-H3170-S103-6-7620, 02/2019
satz_en.fm
Adding an Incoming Line Circuit
• A separate LDAT entry must be created for each of these routes (AMO
LDAT).
Note
Each trunk group configured in AMO RICHT must have an LDAT entry. If this is not done
the follwoing advisory message is displayed each time when changing, adding,
displaying or deleting LDAT:
H25: NOT ALL TRUNKS ENTERED IN RICHT ARE CONFIGURED IN LDAT
(LROUTE:@@@@@) TOO
THIS CAN LEAD TO PROBLEMS FOR TRUNK B-CHANNEL SEARCH,
THIS IS ESPECIALLY IMPORTANT FOR IP-TRUNKING TO WORK
CORRECTLY.
!! ALL TRUNKS CONFIGURED IN RICHT SHOULD BE ENTERED IN
LDAT !!
Example:
A configuration is connected to the OpenScape 4000 with three line circuits. The
examples only contain the parameters essential for comprehension.
• Add trunk groups:

AD-BUEND: TGRP=<bunr1>,NO=<B-channel number>,NAME="<trunk
group name>";
group name>";
group name>";
• Add line circuits:
AD-TDCSU:PEN=<pen1>,DEV=<S0CONN/
S2CONN>,TGRP=<bunr1>,BCNEG=N,...;
S2CONN>,TGRP=<bunr2>,BCNEG=N,...;
S2CONN>,TGRP=<bunr3>,BCNEG=N,...;
• Add an outgoing route to the server:
AD-RICHT:LRTE=<lrtgnr>,TGRP1=<bunr1&tgrp2&tgrp3>,...;
• Add outgoing LCR routes:
AD-LDAT:LROUTE=<lrtgnr>,TGRP=<bunr1>,...;
AD-LDAT:LROUTE=<lrtgnr>,TGRP=<bunr2>,...;
AD-LDAT:LROUTE=<lrtgnr>,TGRP=<bunr3>,...;
• Finally add additional routes for incoming traffic with “Any Channel”:
AD-RICHT:LRTE=<lrtgnr_b1>,TGRP1=<bunr1>,...;
AD-RICHT:LRTE=<lrtgnr_b2>,TGRP1=<bunr2>,...;
AD-RICHT:LRTE=<lrtgnr_b3>,TGRP1=<bunr3>,...;
• To conclude, add the associated LCR routes for incoming traffic:
A31003-H3170-S103-6-7620, 02/2019
satz_en.fm
Adding an Outgoing Line Circuit
AD-LDAT:LRTE=<lrtgnr_b1>,TGRP=<bunr1>,...;
AD-LDAT:LRTE=<lrtgnr_b2>,TGRP=<bunr2>,...;
AD-LDAT:LRTE=<lrtgnr_b3>,TGRP=<bunr3>,...;
Explanation:
If CHI=ANY CHANNEL appears in an incoming SETUP, the trunk group entry is

used to determine the route last configured for this trunk group. The mechanisms
used for an outgoing connection are applied to this route to find an available B
channel.
7.3 Adding an Outgoing Line Circuit

• Add the module configuration data:
AD-BCSU:MTYPE=PER,LTU=number,SLOT=number,PARTNO=string;
• Assign LCR class of service for voices:
CHA-COSSU:TYPE=LCOSV,LCOSV=number,ALCR=number,LRCOPTS=param;
• Assign LCR class of service for data:
CHA-COSSU:TYPE=LCOSD,...
• Assign a class of parameter:
AD-COP:PAR=param;
• Assign a class of trunk:
AD-COT:PAR=param;
• Assign a trunk group:
AD-BUEND:NO=number;
• Assign a line module and allocate it to a trunk group:
AD-
TACSU:PEN=pen,COTNO=number,COPNO=number,LCOSV=number,LCOSD=nu
mber,DEVTYPE=(circuit type),DEV=(circuit type);
• Configure the LCR route as described under LCR
7.4 Configuring MFC Trunks

• Add the module configuration data:
• Add the module configuration data for a SIU-TYPE 3:
A31003-H3170-S103-6-7620, 02/2019
satz_en.fm
Deleting a Trunk
AD-
BCSU:MTYPE=SIUP,LTU=number,SLOT=number,PARTNO=string,MFCTYPE=
param,[FCTID=number];
AD-COP:PAR=param;
AD-COP:PAR=param;
• Assign a trunk group:
AD-BUEND:NO=number;
• Assign a number to the MFC variant (this number must later be entered for
the parameter MFCVAR in the AMO TACSU).
COP-MFCTA:MFCVARI=number;
• Add the MFC trunk:
– Add incoming MFC trunk

AD-TACSU:COTNO=number,COPNO=number,DEVTYPE=(circuit
type),DEV=(circuit type);
– Add bothway MFC trunk
AD-
TACSU:COTNO=number,COPNO=number,TGRP=number,DEVTYPE=(circu
it type),DEV=(circuit type);
• Configure the LCR route as described under LCR
Changing the MFC Variant Tables

CHA-
MFCTA:MFCVAR=number,TYPE=MFCVAR,OPT=MISC,{BACKTYPE=param,FORWTYP
E...};
Changing the MFC Tables

CHA-MFCTA:MFCVAR=number,TYPE=TBLB,OPT=...; (Backward) 
CHA-MFCTA:MFCVAR=number,TYPE=TBLF,OPT=...; (Forward)
Changing the MFC Timers

Timers for MFC signaling and for testing (DTMF/MFC tones).
CHA-
DTIM1:TYPEDH=MFCDID,{RNG=number,BUSY=number,TSUPV1=number,..};
7.5 Deleting a Trunk

• Deactivate trunk:
A31003-H3170-S103-6-7620, 02/2019
satz_en.fm
Deleting a Trunk
DEA-DSSU:TYPE=PEN,PEN1=pen;
• Delete trunk:
DEL-TACSU:PEN=ltg-ltu-slot-cct; (for analog trunks) 
DEL-TDCSU:PEN=ltg-ltu-slot-cct; (for digital trunks) 
DEL-TSCSU:PEN=ltg-ltu-slot-cct; (for special trunks in the SWU)
A31003-H3170-S103-6-7620, 02/2019
login_en.fm
System Administrator Tasks
8 Extended Access Protection (Login)

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. During 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.
8.1 System Administrator Tasks
8.1.1 Initialized User IDs

One user ID is initialized 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 initialized ID, the
passwords with the ROOT ID should be changed immediately after a new APS
variant has been uploaded to a customer system!
The initialized user ID ROOT always has the user ID 1 and cannot be deleted.
ROOT is also used for internal command processing.
8.1.2 Displaying User IDs

The user IDs configured in the system can be listed using the DISPLAY-USER
command.
Input:
DISPLAY-USER;
Output:
USER TABLE
|UID| NAME | AUTH | STATUS | OPTIONS | RE- | LOCK- |
| | |111111 | | | | | | | | | | 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 |
A31003-H3170-S103-6-7620, 02/2019
login_en.fm
8.1.3 Adding New User IDs

New user IDs can be set using AMO USER. The maximum number of IDs is 99.
The AMO automatically 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 without the option P (see chapter Options).
8.1.3.1 User Name
At the user interface the user identity is defined by the user name (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.
8.1.3.2 Rights Assignment
The system administrator assigns one or more executional rights to every user
ID. These rights allow the user to execute certain MML commands (AMO actions)
(see Figure 2).
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
Figure 2 Execution rights of a user
A "necessary execution right" 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 catalogue of execution rights. If the rights are insufficient, an
error message is displayed and the AMO action is not performed. The action can
only be carried out, if a user ID with the required rights is used.
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 rights (see ). The lowest right
is 0. Rights > 10 are reserved for special users.
A31003-H3170-S103-6-7620, 02/2019
login_en.fm
AMO PASSW Class Rights

5 0&&5
4 0&&4
3 0&&3
2 0&&2
1 0&1
0 0
Table 1 Assignment of rights following password classes of AMO PASSW

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.
8.1.3.3 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
password.
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).
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 language, depends on the session which sets the ID.
A31003-H3170-S103-6-7620, 02/2019
login_en.fm
8.1.3.4 Limiting unauthorized Logon Attempts
Every device and every user ID has a counter which counts the number of
unsuccessful login attempts by a user ID. The counter is reset with every
successful attempt. Every counter has a limiting value and a disable time. As
soon as the limiting value is reached the device or ID is disabled for the duration
of the disable time. The limiting values and disable times can be set individually
for the IDs and devices.
8.1.3.5 Disabling the User ID
The limiting value and the disable time for a user ID are set using the ATTEMPTS
and DISTIME parameters in AMO USER. The limiting value in ATTEMPTS can
be set from 1 to 99 and the disable time in DISTIME from 1-9999 minutes.
DISTIME=0 means: "no disable", the number of unauthorized access attempts is
unlimited in this case. DISTIME= * means: "permanent disable".
IMPORTANT: Automatic disabling of user IDs could result in problems. Unautho-

rized access attempts could render the IDs useless and block the administration!
8.1.3.6 Disabling the Terminal
The limiting value and the disable time for terminals are still set using PASSW
AMO and are valid for all terminals.
Input:
ADD-PASSW:TYPE=LOCK,COUNT=<number>,TIME=<number>;
The limiting value in COUNT can be set from 1 to 99 and the disable time in TIME
from 0 to 240 hours. TIME=0 means: "no disable", in this case the number of
unauthorized access attempts is unlimited.
8.1.4 Deleting User ID

User IDs can be deleted using DELETE-USER.
Input:
DELETE-USER:<name>;
ROOT cannot be deleted. It is sometimes better to disable an unused user ID
instead of deleting it. The ID can no longer be used. But it is possible to
reconstruct the user actions on the system (LOGBK AMO), if required.
A31003-H3170-S103-6-7620, 02/2019
login_en.fm
8.1.5 Disabling and Enabling User IDs

User IDs can be disabled using DEACTIVATE-USER or released using
ACTIVATE-USER. It is unimportant, if the ID was disabled manually, with AMO
USER or automatically after unsuccessful login attempts.
8.1.6 Changing User ID Data

All data which can be set when installing a new ID can also be modified using
CHANGE-USER. Modification of ROOT data, however, is restricted.
Example: Change executional rights of a user ID.
Input:
CHANGE-USER:NAME=<name>,AUTH=0&&5;
8.1.7 Configuring Preliminary Password

Newly configured user IDs cannot be used. The system administrator must
assign a preliminary password using the system command PASSW. Exception:
user IDs without option P (see Section 8.1.3.3, “Options”).
Input:
IMPORTANT: PASSW must be entered in in upper case!
PASSW:<name >
Output:
NEW PASSW = <password >
PLEASE REENTER NEW PASSWORD
NEW PASSW = <password >
During password entry the echo is switched off and the terminal is darkened, the
password is therefore not visible during input. The password must be entered
twice as typing mistakes cannot be seen due to the darkened terminal. The
password setting is immediately effective, EXEC-UPDAT is therefore
unnecessary. The password can consist of 8 characters (upper case letters, digits
and special characters in any combination). For safety reasons, the minimum
length is 6 characters. Shorter passwords are rejected. When a user logs in the
first time he/she is forced to change the preliminary password (exception: users
without options C or F). Passwords are stored in encoded form only. Decoding is
not possible (one-way encoding). The system command PASSW is not recorded
in the logbook.
A31003-H3170-S103-6-7620, 02/2019
login_en.fm
8.1.8 AMO PASSW

Passwords are only set or modified using the system command PASSW. The AMO
PASSW is now used to set the terminal block, i.e. to set the disable time and the
number of password input attempts which result in a terminal block.
Input:
ADD-PASSW: TYPE=LOCK, COUNT=<number>, TIME=<number>;
All other functions are without meaning.
8.1.9 Logging MML Commands

During MML command logging in the logbook the identification number of the ID
calling the commands is registered. Using AMO LOGBK and the user ID it is
possible to directly search for entries of a certain user.
Input:
DISPLAY-LOGBK:UID=3;
Output:
56 HITS
CONTINUE (Y/N/C): Y

P4711 DEV:CON1 TSN:1234 UID:3 NOUN:BUEND TYPE:START TIME:98-03-
01 06:23:45
ADD-BUEND:TGRP=22,NO=30;
.
.
.
8.1.10 Upload of Existing IDs with APS Exchange
8.1.10.1 New APS Version
When a new APS version has been uploaded to the harddisk, all existing user IDs
which were stored in the ADS database can be uploaded into the new APS by
updating the database.
Input before Reload:

EXEC-UPDAT:A1,ALL;
This procedure is only possible, when the version and not the variant has been
changed.
A31003-H3170-S103-6-7620, 02/2019
login_en.fm
8.1.10.2 New APS Variant
After an upload of a new APS variant the database must be regenerated. For user
identifications the REGEN-USER command from the REGEN batch must be
uploaded. The initialized user IDs ROOT are not regenerated. After uploading a
new APS variant the passwords with the ROOT identifications must be changed
immediately, to prevent unauthorized accesses. User IDs with rights > 10 are not
regenerated either and must be reconfugured manually.
As the user passwords are stored in the database in encoded form, they cannot
be regenerated. Instead, the user IDs are transferred to a backup file in encoded
form, and the COPY-USER command is regenerated. After exchange of the APS
this command can be used to download the user IDs from the backup file.
However, this command only works after an exchange of the APS and as long as
no new IDs were installed.
Input before APS exchange:

REGEN-USER;
Output:
COPY-USER;
The user IDs are stored in the AMD:UDT file.
Input after APS exchange:

COPY-USER;
Output:
H06: USER ID <name> COPIED
H06: USER ID <name> COPIED
.
.
.
The data contained in the file AMD:UDT were uploaded into the database. The
ADS must now be updated.
8.1.11 User forgets password

If a user forgets his/her password, the system administrator may assign a
temporary new password (see chapter: Configure preliminary password). In case
the system administrator forgets his/her own password, the following solution is
provided. The ROOT ID can be accessed without password, if the service dongle
is plugged in and the dongle code word was entered using CODEW AMO.
IMPORTANT: To enter the service code word at least one user ID must still be
usable.
A31003-H3170-S103-6-7620, 02/2019
login_en.fm
User Possibilities
8.2 User Possibilities
8.2.1 Opening a Session (login)

After connection setup with Ctrl-T or LOGON, the user must identify himself/
herself with user name and the password. The user name is used to establish the
user ID. The entered password is encoded and compared with the one stored
under the user ID. Unlike the user name the password is not visible when entered.
Input:
<Ctrl-T>
LOGIN = <name>
PASSW = <password>
If both the user name and the password are correct, the following message is
displayed and the user logged in:
--------------------------------------------------------------------
TERMINAL-1 L O G O N 01-03-98 14:15:51
--------------------------------------------------------------------
>
If one of the two entries is wrong, all entries are rejected with the following
message and the input must be repeated:
LOGIN INVALID
LOGIN =
The user does not know, whether the user name or the password was incorrect.
8.2.2 Closing a Session (logout)

A user should always logoff when leaving the terminal, to prevent unauthorized
access using the ID of the user. Logoff is always possible by entering either Ctrl-
X or LOGOFF:
Input:
> <Ctrl-X>
Output:
--------------------------------------------------------------------
TERMINAL-1 L O G O F F 01-03-98 14:18:45
--------------------------------------------------------------------
DISCONNECTED
The connection is also closed down. If the option T is set for the user ID (see
chapter: Options) the session is automatically closed after a timeout (ca. 2
minutes).
A31003-H3170-S103-6-7620, 02/2019
login_en.fm
User Possibilities
8.2.3 Executional Rights

The system administrator assigns one or more executional rights to the user ID.
These rights allow the user to execute certain MML commands (AMO actions),
(see Figure 2). A "required execution right", also known as class, is fixedly
assigned to every AMO action. The classes are predefined. They can be modified
by the system administrator using AMO AUTH A user can only call an AMO
action, if the class of the AMO action is also contained in his assigned list of
execution rights. If not, the following error message is displayed:
M43: CLASS INSUFFICIENT, EXECUTION NOT POSSIBLE
8.2.4 Changing Password

Every user can change his/her password using the system command PASSW
(not AMO PASSW):
Input:
PASSW;(must be in upper case)
Output:
OLD PASSW=<password>
NEW PASSW=<password>
PLEASE REENTER NEW PASSWORD
NEW PASSW=<password>
During password entry the "Echo" is switched off and the terminal is in non-
displaying mode. The password remains invisible during entry. To prevent
unauthorized password changes during an opened session, the old password
must be entered first. The new password must be entered twice, because typing
errors may not be recognized in non-displaying mode.
The password change is effective immediately, EXEC-UPDAT need not be called.
8.2.5 Forced Password Change

The system administrator assigns a temporary password to newly installed user
IDs. After the first login, the user is forced to change this temporary password.
Exceptions: options F, C or P are not set, see Section 8.1.3.3, “Options”.
PASSWORD EXPIRED - PLEASE ENTER NEW PASSWORD
NEW PASSW = <password>
PLEASE REENTER NEW PASSWORD
NEW PASSW =<password>
This new password, changed by the user, is also unknown to the system
administrator.
A31003-H3170-S103-6-7620, 02/2019
login_en.fm
User Possibilities
8.2.6 Displaying all Open Sessions

Several sessions, opened by several users, can be simultaneously active. Every
user can see an overview of all other active sessions, using the TSN function:
Input:
TSN;
Output:
TSN | NOUN | LOG DEV | TIME | USER
-----+-------+---------+----------+----------
1004 TASK 14 15 53 ROOT
1013 CHESE CON 1 * 16 42 25 MAYER
8.2.7 Cancelling and Deleting AMOs

Every user could cancel or delete hanging AMOs using the BREAK and CANCEL
functions. This possibility is restricted as follows to prevent users interfering with
other users:
• The AMOs of any user can be cancelled or deleted from ROOT.
• All AMOs started on a terminal can be cancelled or deleted from this terminal.
• Users can (only) cancel or delete those AMOs they themselves have called.
IMPORTANT: Be careful with using BREAK and CANCEL. Cancelling an AMO can
cause inconsistencies in the system.
• BREAK: Breaks a running command.
• CANCEL: Cancels the task specified by the task sequence number.
IMPORTANT: CANCEL should only be used if BREAK has failed!
8.2.8 Further Important Commands

• RELOVL: Force release of all overlays (e.g. AMOs)
• RELTRPOOL: force tracer to release the trace bufferpool
• RESTART: Soft Restart of processor A1
A31003-H3170-S103-6-7620, 02/2019
load_behaviour_flash_board_en.fm
Load Behavior of Flash Boards
Feature Description
9 Load Behavior of Flash Boards

The load behavior of flash boards can be configured in AMO ZANDE, branches
HRBHV (Hard Restart BeHaVior) and LWSRC (LoadWare SouRCe).
The default values are HRBV=HRNOLOAD (HardRestartNOLOAD --> which

means no reset of periphery and no load during restart) and LWSRC=FLASH
(loadware ID check is carried out)
In case of a SoftRestart or CC switchover no periphery will be reset and

consequently no loadware loaded and the default values remain unchanged.
In case of a Reload the periphery will be always be reset and a loadware ID

check is done (all values changed via LOADBHV are ignored).
Changed values are only stored within the DB RAM and are returned to default
automatically after each Hardrestart or Reload of CC.
That means, changing within branch HRBHV will only be used once, if the next
restart is a HardRestart.
9.2.1 General Information

• The CHANGE branch of AMO FUNSU does not have any functionality
anymore. However, the branch and its parameters remain. If the user
executes CHANGEFUNSU, an advisory message is displayed:
Hxx: Administration of the loading behavior of boards is
moved to CHANGE-ZANDE:TYPE=LOADBHV.
• After a Hardrestart or Reload in case of CHANGE or DISPLAY-ZANDE
following message can be displayed. The command must then be repeated
later.
F14: FLASH HANDLING NOT YET FINISHED,
AT THE MOMENT THERE IS NO CHANGE/DISPLAY POSSIBLE.
PLEASE WAIT UNTIL FLASH HANDLING IS FINISHED.
(HISTA F4266: "CHANGE OF LOADBHV IN AMO ZANDE NOW POSSIBLE")
THIS CAN TAKE SOME MINUTES"
• OpenScape 4000 SoftGate/OpenScape Access are not affected by the new
load concept. OpenScape 4000 SoftGate/OpenScape Access always loading
the loadware locally.
A31003-H3170-S103-6-7620, 02/2019
9.2.2 Load Behavior
Figure 3 Simplified presentation of load behavior
Restart Scenarios
• EXEC-REST:TYPE=MODUL,MODUL=BP,RSLEVEL=HARD;
The settings from PIT=HRBHV are applied.
• RES-BSSU or plug the board in and out:

The settings from PIT=LWSRC will be used
• RES-USSU or press Reset button on NCUI

NCUI: Always a LW-ID-Check is carried out and dependant of this, the
loadware will be loaded from hard disk or flash.
For all other boards within the shelf will used the values from PIT=LWSRC.
• EXEX-REST:TYPE=MODUL,MODUL=BP,RSLEVEL=RELOAD;
A reset of the periphery and LW-ID-Check always is carried out and
dependent of this, the loadware will be loaded from hard disk or flash.
9.3.1 CHANGE-ZANDE
The load behavior of boards can be set with AMO ZANDE:
A31003-H3170-S103-6-7620, 02/2019
CHANGE-ZANDE: TYPE=LOADBHV
PIT=HRBHV,LOAD=<param>;
PIT=LWSRC,[PARTNO=<string>],[FCTID=<number>],
LOADDEV=<param>;
Table 2 Set load behavior of boards in AMO ZANDE
IMPORTANT: Settings within HRBHV (HardRestartBeHaVior) only take effect in

case of HardRestart.
For all other actions the settings from LWSRC apply.
Case 1: PIT=HRBHV, LOAD=HRNOLOAD (default)

--> No reset of periphery occurs and loadware won’t be loaded new. The settings
of load source (LWSRC) is also not relevant.
Case 2: PIT=HRBHV, LOAD=LWLOAD

--> A reset of periphery occurs. The load behavior is dependant on settings from
load source (LWSRC)
The load source is set by branch LWSRC.
Case 3: PIT=LWSRC, LOADDEV=FLASH (Default)

--> A loadware ID check is carried out. If the loadware on the HD is the same as
in the flash memory then it will be loaded from the flash memory. In case of
different loadwares the loadware will be loaded from the hard disk.
Case 4: PIT=LWSRC, LOADDEV=HD

--> The loadware is loaded from hard disk without any loadware ID check.
IMPORTANT: LOADDEV=HD doesn't apply for NCUI boards. For these boards
a loadware ID check always is carried out.
An "enforced" loading is done using EXEC-USSU:TYPE=NCUILOAD,
FILES=LW;.
IMPORTANT: LOADDEV=HD also doesn't apply for OpenScape 4000 SoftGate/

OpenScape Access 500 and virtual boards where they will never be loadware
loaded in case of HardRestart/Reload.
Optionally within the branch LWSRC can be limited for specified boards via
FTCID and PARTNO settings.
A31003-H3170-S103-6-7620, 02/2019
• If both parameters are entered, the change will be performed for the specified
board.
• If only PARTNO is entered, the change will be performed for all board types
with that PARTNO (even with different FCTIDs).
• Entering only FCTID does not make sense and is therefore rejected with an
error message:
Fxx: FCTID has to be entered together with PARTNO.
• If neither PARTNO or FCTID is entered, the change will affect all configured
flash boards. A confirmation check is added to indicate that this is the correct
intention and the administrator will confirm/reject it.
Attention: If PARTNO and FCTID are not entered, all
configured flash boards will be affected! Are you sure? (yes/
no)
• OpenScape Access Boards
If the part number (PARTNO) / function ID (FUNCTID) entered belongs to a
OpenScape Access board, the change will be carried out for the entered
OpenScape Access board and also for the corresponding "classical" board.
The same is also valid conversely (i.e. if the entered board has a
corresponding OpenScape Access board, the change will affect the
"classical" and also the corresponding OpenScape Access board). In both
cases, the following advisory message is displayed:
H22: Changes are made for HPA board ^OpenScape access board^
and corresponding classic board ^board^.
9.3.2 DISPLAY-ZANDE
DISPLAY-ZANDE:TYPE=LOADBHV,[LIST=<param>];
The LIST parameter has the following values:
• ALL: All flash board types are listed.
• CONFIG (default): Only flash board types configured on the system are listed.
Example of output:
DISP-ZANDE:TYPE=LOADBHV,LIST=CONFIG;
H500: AMO ZANDE STARTED

HRBHV:
==========================
LOAD = LWLOAD

FLASH:
===========================
PARTNO FCTID LOADDEV
-------- ----- -------
A31003-H3170-S103-6-7620, 02/2019
QXXX1-Y1 0 FLASH
QXXX2-Y2 0 FLASH
QXXX3-Y3 1 HD
QXXX4-Y4 1 HD
QXXX5-Y5 1 FLASH

AMO-ZANDE-111 SYSTEM DATA - EXTENDED
DISPLAY COMPLETED;
<
IMPORTANT: All displayed changes are only valid until the next HardRestart or
Reload. Afterwards the default values are set and displayed again.
OpenScape Access boards:

If one of the boards of a "OpenScape Access and corresponding classical board
pair" is configured, both of them are displayed and the following advisory is
issued:
H21: HPA as well as the corresponding classic board are
displayed in this list even if only one of them is
configured.
9.3.3 REGEN-ZANDE
The values entered in CHANGE-ZANDE:TYPE=LOADBHV; are regenerated in
REGEN-ZANDE.
For LWSRC branch, only records that differ from the default value are
regenerated. If we assume the default LOADDEV value (the value in UBGDAT)
of the board types in the sample DISPLAY output is HD, the REGEN output is as
follows:
IMPORTANT: REGEN-ZANDE:TYP=LOADBHV and AMO UPDAT are not

possible.
REG-ZANDE;
H500: AMO ZANDE STARTED
...
...(other ZANDE output)
...
CHANGE-ZANDE:TYPE=LOADBHV,PIT=LWLOAD;
CHANGE-ZANDE:TYPE=LOADBHV,PIT=LWSRC,PARTNO=QXXX1-
Y1,FCTID=0,LOADDEV=FLASH;
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
AMO-ZANDE-111 SYSTEM DATA EXTENDED
REGENERATE COMPLETED;
<
9.4 Relevant AMOs
AMO Parameter Sprache/ Beschreibung/Description

Language
ZANDE TYP=LOADBH d Ladeverhalten
TYPE=LOADBHV e Load behavior
PIT=HRBHV d Verhalten bei Hard Restart
PIT=HRBHV e Behavior in case of hard restart
LOAD d Mögliche Werte:
HRNOLOAD (HardRestartNOLOAD) oder
LWLOAD
LOAD e Possible values:
HRNOLOAD (HardRestartNOLOAD) or
LWLOAD
PIT=LWSRC d Ladequelle der Loadware
PIT=LWSRC e Loadware source
LOADDEV d Gerät von dem die Loadware geladen wird
LOADDEV e Device the loadware will be loaded from
A31003-H3170-S103-6-7620, 02/2019
lwvar_en.fm
Loadware Variants
Feature Description
10 Loadware Variants

It is not possible to configure different loadware variants for the same board type
within a PBX. After a soft restart the last entered variant is loaded for all boards
of this type.
For the configuration of a new board type state the loadware variant in AMO
BCSU (parameter LWVAR e.g. 0=FRG, K=USA, if it deviates from the variant
which is in the UBGDAT module table). 
This saves later modifications in AMO ZAND and subsequent loading of the
board (see example).
The loadware for the various modules and module functions is stored in files on
the hard disk. 
Various loadware files are located in the following directory: PDS:APSP/LTG.
10.2 Configuration (Example)

• It is possible to display the installed loadware variants via the AMO ZAND:
DISPLAY-ZAND:TYPE=LOADWARE;
• The current assignment of a module to loadware (type and variant, etc.) can
be displayed via the AMO BGDAT:
DISPLAY-BGDAT;
• Proceed as follows to change the loadware variant for certain board types:
CHA-ZAND:TYPE=LOADWARE,LWTYPE=param,LWVAR=param;
• Reload the boards by switching the boards on and off.
DEA-BSSU:[LTG=number],LTU=number,SLOT=number; 
AC-BSSU:ONTYPE=AUL,[LTG=number],LTU=number,SLOT=number;
or
RESTART-
BSSU:ADDRTYPE=PEN,[LTG=number],LTU=number,SLOT=number;
or
RESTART-BSSU:ADDRTYPE=PARTNO,[PARTNO=string],[FCTID=number];
A31003-H3170-S103-6-7620, 02/2019
lwvar_en.fm
Loadware Variants
Relevant AMOs
10.3 Relevant AMOs

Language
BGDAT SORT d Sortiert nach
(N Baugruppenname, Q Quellennummer)
SORT e Sorted by
(N Boardname, Q Q-number)
ZAND TYP d Auswahl des Datentyps
(LOADWARE)
TYPE e Desired system option
(LOADWARE)
LWTYP d LOADWARE FUER SATZBAUGRUPPEN
UND SIU
LWTYPE e LOADWARE FOR TRUNK MODULES AND
SIU
LWVAR d Loadware Variante
LWVAR e Loadware variant
A31003-H3170-S103-6-7620, 02/2019
logical_partitioning_en.fm
Logical Partitioning in OpenScape 4000 Systems
11 Logical Partitioning in OpenScape 4000 Systems

Requirements
With the change is government regulations today a customer can terminate a
PST PRI line and a VoiP/Leased line on the same PBX. But there are certain
preconditions that the PBX must satisfy.
We have this feature of Logical Partitioning in our OpenScape 4000 systems but
have certain limitation and hence our existing customers cannot avail of the new
regulation.
The following features are a must for logical partitioning of a PBX:
1. The subscriber of the system should not be able to transfer a call from the
public line to private line and vice versa.
2. The subscriber should not be able to setup a conference call between the
public line and private line.
3. The transfer of call from public line to public line is allowed.
4. The conference call between 2 external parties connected on public line only
is allowed.
5. The transfer of call from private line to private line is allowed.
6. The conference call between 2 external parties connected on private line only
is allowed.
OpenScape 4000 support only 1, 3 and 5 of the requirement of logical partitioning

can be configured in the OpenScape 4000 systems.
Conference
Authorisation can be given to accept CO trunk connections in a conference by
COT parameter XFER. This does not solve the requirements as this forbids or
accepts to connect a CO trunk call to a conference independently of the other
members' trunk types.
• Realisation
Additional checks are made before creating a conference --- either after
consultation or after accepting a second call --- or allowing a new member to
join an existing conference, in order to filter out the different trunk type
categories: i.e. CO trunks and private trunks. Mixing is prohibited.
ACLC: If the patches of the CR is activated on a switch the ACLC Conference
Call Request is also working according to the requested functionality of this
CR.
• Prerequisites
A31003-H3170-S103-6-7620, 02/2019
logical_partitioning_en.fm
Logical Partitioning in OpenScape 4000 Systems
None. The solution filters out the conferences with mixed trunk type from the
otherways acceptable ones.
• User interface
The user attempting to initiate a mixed trunk type conference will have the
usual "CONFERENCE NOT POSSIBLE" display message and stays in
connection with the active party.
Call transfer
The requirements concerning the connection of the internal trunks and public
trunks via call transfer can be solved by configuration using AMO KNMAT.
Administration (configuration example):
Configuring OpenScape 4000 system 1 in order to prohibit the call transfer from
OpenScape 4000 system 2 to the public line:
In the tests the situation was as follows:
• Node number of OpenScape 4000 2 is 1-2-99
• Node number of the public network is 1-2-100
• The LEVEL is 0: we compare the values 99 and 100

CHA-KNMAT:NPI=UNKNOWN,LEVEL=0,ONNO=99,DNNO=100,CONN=D;
Activation
CHANGE-ZAND:TYPE=RESERVE,ELNUM=173,ACTIVE=YES;
A31003-H3170-S103-6-7620, 02/2019
optpatch_en.fm
Optional Patches
General
12 Optional Patches
12.1 General
Optional patches are used to activate features or special functions for certain
users. The activiation is now done by activation flags. These activation flags
which are assigned to one or more specific patches can now be set or deleted
using an AMO. The functions/features assigned to flags can thus be activated or
deactivated.
12.2 Advantages
When updating a customer system from an old to a new release, all previously
activated features are automatically activated in the new release after database
update by means of the default customer database update using the standard
update.
12.3 Procedure
The AMO PATCH will be used to set the relevant activation flags. The
corresponding patches (one or more per flag) are then automatically copied from
the ":PDS:OPT/" directory to ":PDS:PATCHINPUT/" and activated. The patches
can be displayed in Patch Administration with DIS-PATCH and have the
activation flag as group code.
Activation
• SWU
ACT-PATCH:OPT,S,flag;
• ADP
ACT-PATCH:OPT,D,flag;
Deactivation
To deactivate a feature activated in this manner, the commands
DEACT-PATCH:OPT, ...
etc. are used.
A31003-H3170-S103-6-7620, 02/2019
optpatch_en.fm
Optional Patches
Overview of the Assigned Flags
The associated patches are deactivated and deleted from Patch Administration.
They remain, however, in :PDS:OPT/.
IMPORTANT: These patches cannot be activated and deactivated directly by

specifying the patch name.
After successful activation / deactivation you have to execute an EXEC-UPDAT
(note: the AMO PATCH also comes up with this hint).
12.4 Overview of the Assigned Flags

• An overview of all integrated features available with a release and the
corresponding activation flags can be found in the KMOSS PRB database
under "Type of Correction".
• An overview of all integrated features available in a revision level and the

corresponding activation flags can be found in the KMOSS PRB database
under "Revision Level" or alternatively using the "FindIt" tool.
• An overview of all patches that have been assigned an activation flag can be
found using the "FindIt" tool.
A31003-H3170-S103-6-7620, 02/2019
partana_en.fm
13 Partial Digit Analysis TWABE

Partial digit analysis (AMO TWABE) is used to pre-evaluate dialled digits in the
device handler. 
Entries in the TWABE tables can be made for all possible digit combinations
throughout the network. 
The TWABE tables, unlike the DPLN, do not take the call progress situations into
account. In the case of short digit combinations contained in longer digit
combinations, only the shortest possible combination must be entered in the
TWABE tables, since both combinations may lead to different DARs in the dial
plan.
E.g. DPLN group 1 430 DAR = X

DPLN group 2 43 DAR = Y
In the above example, if the digit combination 430 were to be entered in the
TWABE tables, the shorter combination 43 would not be passed on to the DPLN.
When entering digit combinations in the TWABE tables, the digit combination to
be evaluated is entered first (max. 3 digits), followed by the number of digits (up
to 18) which must be dialled before the number is passed on to the DPLN for
evaluation. 
Add digit combination 456 with a length of 6 digits, i.e. all digit sequences which
begin with 456 are not passed on to the DPLN for evaluation until the 6th digit has
been dialled.
ADD-TWABE:STNO=456,LEN=6;
A31003-H3170-S103-6-7620, 02/2019
partana_en.fm
A31003-H3170-S103-6-7620, 02/2019
powerfai_en.fm
14 Power Fail Interrupt Settings

Starting with the Atlantik platforms (for example, 600ECX/600ECS, 80CMX-DSC,
80CXE systems), the software supports a battery manager (with power fail
interrupt).
If the entire system power supply (line-powered converter plus any redundant
units) fails, there is a switchover (hardware) to a battery, if there is one. If the
battery capacity then also nears its limit, a so-called power fail interrupt (PFI) is
generated approximately 1 minute before the end of the battery capacity. As a
result of this PFI interrupt, the error message BATTERY DOWN is signaled and
the UNIX operating system is informed so that critical data can be saved on the
hard disk or so that the UNIX operating system can be brought down.
The software cannot detect on its own whether the hardware generates a PFI.
Therefore it retrieves this information from a variable that you must set with the
AMO FUNCT.
The call is as follows: ‘CHANGE-FUNCT:PFI=WITHPFI;’ (PFI can be evaluated)

or ‘CHANGE-FUNCT:PFI=WOUTPFI;’ (PFI cannot be evaluated).
You can also set the power supply devices that you use with ’CHANGE-FUNCT’
in the POWERSYS parameter.
You can assign the POWERSYS parameter the following values:
ACDCWR .... AC/DC system with power supply unit redundancy
ACDCWOR .... AC/DC system without power supply unit redundancy
DCDCWR .... DC/DC system with power supply unit redundancy
DCDCWOR .... DC/DC system without power supply unit redundancy
The call is as follows: ‘CHANGE-FUNCT:POWERSYS=ACDCWR;’
If you have specified a redundancy in an AC/DC system, for example, and a

power supply unit fails, POW FAIL REDUND LOSS AC/DC SYS is signaled and
a minor alarm set. If you put the power supply unit back Into operation, POW FAIL
REDUND BACK AC/DC SYS is signaled and the mInor alarm is cancelled.
If you have specified a redundancy in an AC/DC system, for example, and more
than one power supply unit fails, POW FAIL START AC/DC SYS is signaled and
a major alarm is set. In addition, the system switches over to a battery is there is
one. If you put the power supply units back into operation, POW FAIL END AC/
DC SYS is signaled and the major alarm is cancelled.
If you have not specified redundancy in an AC/DC system, for example, and one
power supply unit fails, POW FAIL START AC/DC SYS is signaled and a major
alarm is set. In addition, the system switches over to a battery if there is one. If
you put the power supply unit back into operation, POW FAIL END AC/DC SYS
is signaled and the major alarm is cancelled.
A31003-H3170-S103-6-7620, 02/2019
powerfai_en.fm
You can check the current PFI setting with the call DISPLAY-FUNCT;.
A31003-H3170-S103-6-7620, 02/2019
routes_en.fm
Routes
Assign a route to the Telecommunications Service
15 Routes
Trunk groups are assigned to outgoing routes with the AMO RICHT. These routes
are allocated on or more access codes. The sequence in which the trunk groups
are entered in the ADD-RICHT command also determines the seizure priorities,
and thus also decides the overflow and alternate routing procedures.
A trunk group may be assigned to several routes. For this reason, the route
parameters are specified separately for each trunk group in the AMO RICHT.
However, a trunk may only be assigned to one trunk group!
15.1 Assign a route to the Telecommunications Service

• Assign the route codes in the DPLN
The same codes are used as for the route to the Voice Mail Server.
AD-WABE:CD=key-num,DAR=VMOWN,CD2=key-num;
CD = route via DAR ’VMOWN’ 
CD2 = route via DAR ’VMFOR’
• Add trunk group

AD-BUEND:NO=number;
(NO = number of trunks times 2)
• Assign a line circuit on an SLMD for TTX

AD-TSCSU:COTNO=number,TGRP=number,DEV=SMTTX;
• Assign a line circuit on an SLMD for FAX
AD-TSCSU:COTNO=number,TGRP=number,DEV=SMFAX;
• Assign a route
AD-RICHT:TYPE=CD,CD=key-num,SVC=TTX,SM=VM,TGRP1=number; 
AD-RICHT:TYPE=CD,CD=key-num,SVC=FAX,SM=VM,TGRP1=number;
A separate route must be assigned for each service using different trunk
groups.
15.2 Assign a Route to the Voice Mail Service

• Add the codes in the DPLN
AD-WABE:CD=key-num,DAR=VMOWN,CD2=key-num;
CD = route via DAR ’VMOWN’ 
CD2 = route via DAR ’VMFOR’
A31003-H3170-S103-6-7620, 02/2019
routes_en.fm
Routes
LCR Routes
• Add trunk group

AD-BUEND:NO=number; (NO = number of trunks times 2)
• Assign a line circuit on an SLMD
AD-TSCSU:COTNO=number,TGRP=number,DEV=SMVM;
• Assign a route
AD-RICHT:TYPE=CD,CD=key-num,SVC=VCE,SM=VM,TGRP1=number;
• Delete a route
DEL-RICHT:TYPE=CD,CD=key-num,SVC=param,TYPE=TGRP,TGRP=number;
• Delete the trunk group
DEL-BUEND:TGRP=number;
15.3 LCR Routes

See Chapter 37, “LCR (Least Cost Routing)”!
A31003-H3170-S103-6-7620, 02/2019
boardrec_en.fm
Recovery of Peripheral Units
Feature Description
16 Recovery of Peripheral Units
• Up tp 8 automatic recoveries of peripheral units.
• Pre-initialised timer values for automatic recovery.
• Different recovery times for LTUC, board, trunk and terminal.
• Monitoring of the peripheral units for stable operation.
• Timer can be configured for all functions.
Using this feature, defective peripheral units can be restarted once or, if
necessary, several times (LTUC, boards, trunks and terminals).
After a defect the corresponding device is locked for a certain period of time
(LOCKTIM). It is then restarted and monitored for stable operation (STABTIM). If
all restart attempts fail, the device remains in defect state.
16.2 Feature Characteristics

• Possibilities:
A31003-H3170-S103-6-7620, 02/2019
boardrec_en.fm
User Interface: AMO PSTAT
As default, up to 5 recoveries can be executed. 

Using PSTAT AMO, between one and up to eight restarts for the levels LTUC,
boards, trunks and terminals can be selected. 
The time until recovery (lock time), and the monitoring time until stabilization,
can be modified.
16.3 User Interface: AMO PSTAT

• Query of the locking times: 
all locking times for the levels LTUC, boards, trunks and terminals are
displayed (INIT and ACTUAL)
• Query of the stabilization times: 

one stabilization time per level LTUC, boards, trunks and terminals is
displayed (INIT and ACTUAL)
• Modification of the locking times: 

the locking times can be modified for every level. The values are between 0
and 60 minutes.
At least one locking time must be >0. 
The locking times must be selected in ascending order. The reason being,
that it makes sense to increase the locking times with every recovery. 
The first three locking times should be under 10 minutes for a speedy
recovery of the unit and to avoid alarm messages to the Service Center (see
also the section on Service Information). 
A locking time of 1 minute could be too short which would result in a second
recovery.
After the modification the original time is stored as INIT value.
• Modification of the stabilization times:

these times can be modified on every level. The values are between 10 and
30 minutes. 

Regeneration of the locking times: 
this is executed in case of deviations between the INIT and the ACTUAL
values. 

Regeneration of the stabilization times: 
this is executed in case of deviations between the INIT and the ACTUAL
values.
• Application areas: 
no restriction
A31003-H3170-S103-6-7620, 02/2019
boardrec_en.fm
Service Information

• The delay time before alarm messages are sent to the Service Center is 10
minutes. 
If a locking time exceeds the 10 minute threshold and a renewed defect
exceeds the alarm threshold set for a group of devices, an alarm could be
released.
• Instead of individual timers a central timer is used per device to set the locking
and stabilizing times. The times are therefore subject to deviations of up to 60
seconds. A locking time of 1 minute could therefore lie between 0 and 60
seconds, a locking time of 2 minutes could lie between 60 and 120 seconds.
• Restrictions:
For technical reasons, certain modules are excempt from the recovery:
RGEN, WGEN, PSIO, CONF and the central SIU.
• If all timers are set to the maximum value the recovery could last for up to 5
and a half hours.
16.5 Relevant AMOs

Language
PSTAT LOCKTIM d Sperrzeit vor Wiederinbetriebnahme
LOCKTIM e Locking time before recovery
STABTIM d Überwachungszeit nach der
Inbetriebnahme
STABTIM e Stabilization time after automatic recovery
16.6 Generation Information

The locking time (LOCKTIM) and stabilization time (STABTIM) tables receive
their contents from the database during startup. The INIT and ACTUAL times
have the same values.
The PSTAT AMO can be used to query, modify and regenerate the ACTUAL
times.
A31003-H3170-S103-6-7620, 02/2019
boardrec_en.fm
Generation Information
Query of the locking times

DIS-PSTAT:TYPE=LOCKTIM;
Comment:
The values described under "INIT" represent the initializing values. This shows
the deviations from the basic initialization value and the current value. 
The value 0 under e.g. TIM6 means that this timer is inactive.
H500: AMO PSTAT STARTED
+-----------------------------------------------------------------------+ 
| LOCKING TIMES (IN MINUTES) | 
| OF THE AUTOMATIC RECOVERY | 
+---------------+-------------------------------------------------------+ 
| LEVEL | TIM1 | TIM2 | TIM3 | TIM4 | TIM5 | TIM6 | TIM7 | TIM8 | 
+---------------+------+------+------+------+------+------+------+------+ 
| BOARD ACTUAL | 2 | 5 | 9 | 20 | 60 | 0 | 0 | 0 | 
| INIT | 2 | 5 | 9 | 20 | 60 | 0 | 0 | 0 | 
+---------------+------+------+------+------+------+------+------+------+ 
| CIR ACTUAL | 2 | 5 | 9 | 20 | 60 | 0 | 0 | 0 | 
| INIT | 2 | 5 | 9 | 20 | 60 | 0 | 0 | 0 | 
+---------------+------+------+------+------+------+------+------+------+ 
| DEV ACTUAL | 2 | 5 | 9 | 20 | 60 | 0 | 0 | 0 | 
| INIT | 2 | 5 | 9 | 20 | 60 | 0 | 0 | 0 | 
+---------------+------+------+------+------+------+------+------+------+ 
| LTUC ACTUAL | 2 | 5 | 9 | 20 | 60 | 0 | 0 | 0 | 
| INIT | 2 | 5 | 9 | 20 | 60 | 0 | 0 | 0 | 
+---------------+------+------+------+------+------+------+------+------+ 
AMO-PSTAT-153 PERIPHERAL STATISTICS
Modification of the locking times, e.g. for boards:

CHA-PSTAT:LOCKTIM,BOARD,2,4,8,16,30,60,60,60;
H500: AMO PSTAT STARTED
H06: BY INCREASING THE LOCKING TIME TO A VALUE >= 10 MINUTES 
THE ALARM ASSIGNED TO THIS BOARD CAN BE ACTIVATED.
Modification of the locking times e.g. for terminals:

CHA-PSTAT:LOCKTIM,DEV,1,3,5,9,0;
H500: AMO PSTAT STARTED
A31003-H3170-S103-6-7620, 02/2019
boardrec_en.fm
Query of the stabilizing times

DIS-PSTAT:TYPE=STABTIM;
Comment:
The values described under "INIT" represent the initializing values. This shows
the deviations from the basic initialization value and the current value.
+-------------------------------------------+ 
| STABILIZING TIME (IN MINUTES) | 
| OF THE AUTOMATIC RECOVERY | 
+-------------+--------------+--------------+ 
| LEVEL | INIT | AKTUALL | 
+-------------+--------------+--------------+ 
| BOARD | 20 | 20 | 
+-------------+--------------+--------------+ 
| CIR | 20 | 20 | 
+-------------+--------------+--------------+ 
| DEV | 20 | 20 | 
+-------------+--------------+--------------+ 
| LTUC | 20 | 20 | 
+-------------+--------------+--------------+ 
AMO-PSTAT-153 PERIPHERAL STATISTICS
Modification of the stabilizing time, e.g. for trunks:

CHA-PSTAT:STABTIM,CIR,10;
H500: AMO PSTAT STARTED
A31003-H3170-S103-6-7620, 02/2019
boardrec_en.fm
A31003-H3170-S103-6-7620, 02/2019
subscriber_search_enhancements_en.fm
Feature Description
17 Subscriber Search Enhancements

For searching for stations in a specific source group and/or in a specific cluster
branches are available in AMO SDAT.
Furthermore, a branch is implemented on AMO SBCSU for querying the stations

with a specific IP address and listing stations in a specific network. It is possible
for the user to enter the IP address and get the station number that owns this
address. It is also possible to list all stations that are in a network by entering a
partial IP address.
Search for stations in a specific source group
DISPLAY-SDAT:TYPE=SRCFIND,SRCGRP=<xy>;
Output:
DISP-SDAT:TYPE=SRCFIND,SRCGRP=5;
H500: AMO SDAT STARTED
STNO = 105 SRCGRP = 5 
STNO = 106 SRCGRP = 5

AMO-SDAT -111 ADMINISTRATION OF SUBSCRIBER ATTRIBUTES AND
DATA 
<
Search for stations in a specific cluster
DISPLAY-SDAT:TYPE=CLUSFIND,CLUSTID=<xy>;
Output:
DISP-SDAT:TYPE=CLUSFIND,CLUSTID=5;
H500: AMO SDAT STARTED
STNO = 105 CLUSTID = 5 
STNO = 106 CLUSTID = 5

A31003-H3170-S103-6-7620, 02/2019
AMO-SDAT -111 ADMINISTRATION OF SUBSCRIBER ATTRIBUTES AND

DATA 
<
Search for a station with a specific IP address
DISPLAY-SBCSU:TYPE=IPSEARCH,IPADDR=192.168.10.20;
Output:
DISP-SBCSU:TYPE=IPSEARCH,IPADDR=192.168.10.20;
H500: AMO SBCSU STARTED
STNO = 105 IPADDR = 192.168.10.20 

AMO-SBCSU -111 STATION AND S0-BUS CONFIGURATION OF
SWITCHING UNIT 
DISPLAY COMPLETED;
<
Search for stations in a specific network
DISPLAY-SBCSU:TYPE=IPSEARCH,IPADDR=192.168.2.*;
The user can enter an asterisk (*) for each number. It will then be possible to
specify network IPADDR as
• *.*.*.*
• X.*.*.*
• X.Y.*.*
• X.Y.Z.*
Output:
DISP-SBCSU:TYPE=IPSEARCH,IPADDR=192.168.2.*;
H500: AMO SBCSU STARTED
STNO = 105 IPADDR=192.168.2.10
STNO = 106 IPADDR=192.168.2.5
STNO = 107 IPADDR=192.168.2.29
STNO = 108 IPADDR=192.168.2.7
STNO = 233 IPADDR=192.168.2.46

AMO-SBCSU -111 STATION AND S0-BUS CONFIGURATION OF
SWITCHING UNIT 
<
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
17.3 Relevant AMOs

Language
SDAT TYP=SRCSUCH d Suche nach Teilnehmern in einer
bestimmten Source Group
TYPE=SRCFIND e Search for stations in a specific source
group
TYP=CLUSSUCH d Suche nach Teilnehmern in einem
bestimmten Cluster
TYPE=CLUSFIND e Search for stations in a specific cluster
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
system_backup_restore_en.fm
Important Information
18 System Backup & Restore
18.1 Important Information
WICHTIG: For a Duplex or Separated Duplex system the function “Recovery

HD” can't be used in case only one node is down even if this is node A.
18.2 Scenarios
The following use cases exist:
1. Recovery of DSCXL2 board (Duplex system) due to hardware problems
a) Both nodes of a Duplex deployment are down due to problems with the
cluster:
• Shut down the system from OpenScape 4000 Platform Administration

(Portal) (OpenScape 4000 Platform Administration (Portal) >
Maintenance > Shutdown/Reboot > select option Shutdown) or if
OpenScape 4000 Platform Administration (Portal) is not available
make a shutdown via ssh connection on all nodes (e.g. shutdown –
h now or init0).
• Remove all hard disks from the HDTR (node 1).
• Insert the recovery hard disk into the upper tray of the HDTR.

Please refer to the online help of OpenScape 4000 Platform Adminis-
tration (Portal) how to create a Recovery HD.
• Remove the HA (corosync) and Atlantic cable between the nodes.
• Switch on the DSCXL2 from node 1 corresponding to HDTR.


The system boots using the software version stored on the recovery
hard disk.
• Telephony will be restored immediately.


All resources will start. CCA will reach active state in approximately 3
minutes. Telephony will be usable again in 5 to 10 minutes
(depending on the system size).
A31003-H3170-S103-6-7620, 02/2019
Scenarios
• Reinstall using the first installation image on node 1 (with the same
version the recovery HD has) using as deployment Duplex Repla-
cement.

If a xml file is used than node configuration for this board in slot5
should contain data that it is a replacement board.

<entry key="node-replacement">1</entry>
• After installation and configuration is done on node 2 connect the HA

(corosync) and Atlantic cable between the two boards.
• OpenScape 4000 Assistant image, OpenScape 4000 Assistant data,

OpenScape 4000 CSTA image and OpenScape 4000 Platform
Administration data will be provided to node 2 via DRBD and remote
copy from node 1 automatically.
• To recover the latest data (from the time the Recovery HD was
created until last Data/Logical Backup was done) use the
OpenScape 4000 Backup & Restore > Data/Logical Restore.

Please refer to the online help of OpenScape 4000 Backup & Restore
for more information.
b) One of the nodes of a Duplex deployment is down due to problems with

the cluster:
If one node is down then reinstall using the first installation image (with
the same version the other nodes have) with the right configuration
(replacement board) .
If a xml file is used than node configuration should contain data that it is
a board replacement.
c) Board replacement (hardware has crashed / Linux does not boot
anymore / the whole board (DSCXL2) must be replaced).
To recover the board use the first installation image (image version should
be the same as on the other node) and a xml file containg system confi-
guration. xml node configuration should contain data that it is a board
replacement.
OpenScape 4000 Assistant image, OpenScape 4000 Assistant data,
OpenScape 4000 CSTA image and OpenScape 4000 Platform Administ-
ration data will be provided to new board via DRBD and remote copy from
the other node (only possible for Duplex and Separated Duplex deploy-
ments).
A31003-H3170-S103-6-7620, 02/2019
Scenarios
d) Board recovery in case of SOCO2/DRBD problems but Linux is still

working (problems with the cluster - only possible for Duplex and
Separated Duplex deployments).
To recover the board use the first installation image (image version should
be the same as on the other node/nodes) and a xml file containg system
configuration. xml node configuration should contain data that it is a board
replacement.
In the future: Script based recovery
2. Recovery of Simplex / Survivable SoftGate
• To recover the system use the latest Recovery HD.

Please refer to the online help of OpenScape 4000 Platform Administ-
ration (Portal) how to create a Recovery HD.
• To recover the latest data (from the time the Recovery HD was created
until last Data/Logical Backup was done) use the OpenScape 4000
Backup & Restore > Data/Logical Restore.
Please refer to the online help of OpenScape 4000 Backup & Restore for
more information.
3. Recovery of Separated Duplex
a) All three nodes of a Separated Duplex deployment are down due to

problems with the cluster.
• Shut down the system from OpenScape 4000 Platform Administration

(Portal)(OpenScape 4000 Platform Administration (Portal) >
Maintenance > Shutdown/Reboot > select option Shutdown) or if
OpenScape 4000 Platform Administration (Portal) is not available
make a shutdown via ssh connection on all nodes (e.g. shutdown –
h now or init0).
• Remove all hard disks from the HDTR (node 1).
• Insert the recovery hard disk into the upper tray of the HDTR.

Please refer to the online help of OpenScape 4000 Platform Adminis-
tration (Portal) how to create a Recovery HD.
• Remove the HA (corosync) and Atlantic cable from all nodes except
node 1.
• Switch on the DSCXL2 from slot 1 of node 1 corresponding to HDTR.
• The system boots using the software version of the recovery hard
disk.
A31003-H3170-S103-6-7620, 02/2019
Scenarios
• To restore the telephony immediately using only one node enter the
following command in a Linux console from node 1:

standalone_operation enable 

All resources will start, CCA will reach active state in approximately 3
• Reinstall using the first installation image (with the same version that
the recovery HD has) on the other nodes of the system (node 2 and
Quorum) with the right configuration.

If a xml file is used than the node configuration should contain data
that it is a board replacement.

• After all configuration is redone connect the HA (corosync) and

Atlantic cable for all existing nodes of the system.
• At this point it is mandatory to disable standalone mode. To do this

use following command in a Linux console from node 1:

standalone_operation disable

Administration data will be provided to node 2 via DRBD and remote
copy from node 1.
• To recover the latest data (from the time the Recovery HD was
created until last Data/Logical Backup was done) use the
OpenScape 4000 Backup & Restore > Data/Logical Restore.

Please refer to the online help of OpenScape 4000 Backup & Restore
for more information.
b) One node of a Separated Duplex deployment is down due to problems

with the cluster.
If one node is down then reinstall using the first installation image (with
same version the other nodes have) with the right configuration (board
replacement).
If a xml file is used than node configuration should contain data that it is
a board replacement.
c) node 1 and node 2 of a Separated Duplex deployment are down due to
problems with the cluster.
A31003-H3170-S103-6-7620, 02/2019
Scenarios
Follow the steps described in All three nodes of a Separated Duplex

deployment are down due to problems with the cluster.
d) node 1 and Quorum or node 2 & Quorum of a Separated Duplex deplo-

yment are down.
If node 1 and Quorum or node 2 and Quorum are donw then:
• Shut down the nodes that are not working (OpenScape 4000
Platform Administration (Portal) > Maintenance > Shutdown/
Reboot > select option Shutdown).
• To restore the telephony immediately using only one node the

following command in a Linux console on the remaining node:

standalone_operation enable 

All resources will start. CCA will reach active state in apporximately 3
• Reinstall using the first installation image (with the same version the
remaining node has) on the other nodes of the system with the right
configuration.

If a xml file is used than the node configuration should contain data
that it is a board replacement.

• At this point it is mandatory to disable standalone mode. To do this

use following command in a Linux console from node 1:

standalone_operation disable

Administration data will be provided to the other node via DRBD and
remote copy.
4. Recovery of Access Point Emergency, RG 8300, OpenScape Access, Survi-

vable SoftGate.
For these deployments no HD Recovery is possible.
• To recover these systems use the first installation image (firstinst-

netw.sh) and a xml file containg the system configuration.
• To recover the data use the OpenScape 4000 Assistant Backup &
Restore > APE Restore.
more information.
A31003-H3170-S103-6-7620, 02/2019
Scenarios
5. Recovery of OpenScape Access/RG 8350a and OpenScape Access/Survi-

vable SofGate (no HD Recovery possible on this hardware deployments)
• To recover these systems use the first installation image (firstinst-

netw.sh) and a xml file containg the system configuration.
• To recover the data use the OpenScape 4000 Assistant Backup &
Restore. The backup server must be outside the system bcause the
OpenScape 4000 host system isn’t working also.
more information.
6. Recovery of SoftGate Standalone
• To recover these systems use the first installation image (image version
should be the same as the one from the Host system) and a xml file
containg the system configuration.
• Loadware update of the gateways
• HG 3550 M Auto-Restore
With the Web Based Management of the board the externally stored
configuration data can be loaded to the gateway.
WBM > Maintenance > Configuration > Configuration Data > (right-
click) Load to Gateway > Loading via HTTP
In the Backup/Restore menu of the Web Based Management, you can
backup (export) the vHG 3500 HFA configuration data and the security
configuration locally. This local backup can be loaded (imported) and
activated.
WBM > Maintenance > Backup/Restore > Import Config
Please refer to the online help of the WBM for more information.
7. Recovery of SoftGate in case that the OpenScape 4000 SoftGate doesn’t

startup anymore, but Linux is still ok.
To recover these systems use the first installation image (image version
should be the same as the one from the Host system) and a xml file containg
the system configuration. The whole Linux must be reinstalled even if it’s ok.
In the future: new feature to Re-InstallSoftGate-RPM triggered by Web Based
Management.
A31003-H3170-S103-6-7620, 02/2019
timers_en.fm
Timers
19 Timers
There are numerous timers in the system all of which are initialized. The majority
of these timers can be changed by administration and maintenance. In view of the
large number of timers, it was necessary to divide them up between several
AMOs. Innerhalb eines AMO wurden die Zeitglieder zu Gruppen
zusammengefaßt.
• The AMO CTIME changes the call processing timers.

AE-CTIME:ARTSWU=
- CP General timers for call processing part 1

- CP2 General timers for call processing part 2
- TRK Timers for trunk circuits
- ATND Timers of the attendant terminals
- CCM Timers for multiple code calling equipment
- VECOTIME VECO timers
• AMO DTIM1 changes the timers for the device handler.

AE-DTIM1:ARTDH=
- DIGITE Timers for Digite

- CO Timers for trunk calls
- TIE Timers for tie traffic
- STN Timers for stations
- ALTA Timers for branch circuits for Austria
- MTLC Timers for main system tie line circuits
- TCOM Timers for adapters for special equipment
- MFCDID Timers for DTMF DID and test program
- EXPTONE Timers for expensive tone
• AMO DTIM2 also changes the timers for the device handler
AE-DTIM2:ARTDH=
- LNGBN Timers for line circuits, general

- MKBK Make/break ratios for CO and tie-line circuits
- GEN General timers
- DSS1 call back on dss1 protocol
• AMO PTIME changes the timers of the periphery.

AE-PTIME:ARTEE=
- SLMA subscriber line module analog resp. analog devices

- SLMA1 subscriber line module analog individual
A31003-H3170-S103-6-7620, 02/2019
timers_en.fm
Timers
- REST all other device types
A31003-H3170-S103-6-7620, 02/2019
account_management_en.fm
Account Management
OpenScape 4000 Assistant
20 Account Management
With the account management of the OpenScape 4000 Assistant the following
functions are possible:
Change the Password of an Account
To change the password of an account logon via SecM (a so-called ASbum

account). But you can also use the following command:
# /opt/bum/bin/bum_passwd account new_password
account name of the account

new_password enter the new password
IMPORTANT: It is recommended to surround “new_password” by single or

double quotes to avoid the shell being confused by some special characters.
Automatically Lock an Account after Several Wrong Password Inputs
# /opt/bum/bin/bum_passwd -l account
-l lock an account
Unlock an account
# /opt/bum/bin/bum_passwd -u account
-u unlock an account
Force an user to change the password with next login
# /opt/bum/bin/bum_passwd -f account
-f force the user to change the password with next login
A31003-H3170-S103-6-7620, 02/2019
account_management_en.fm
Account Management
Delete the password of an account
# /opt/bum/bin/bum_passwd -d account
-d delete the password of an account (“-f” is implied in this option)

An OS account that is attached to an ASbum account is adjusted automatically

by bum_passwd.
A31003-H3170-S103-6-7620, 02/2019
ip_en.fm
IP Solutions
IP Solutions
You can find a complete description of the following features in the Service
Manual OpenScape 4000, Section 4 - IP Solutions.
• Access Point Emergency (APE)
• Different Time Zones (DTZ)
• H323 / H323 Annex Connectivity
• HiPath Cordless IP
• HiPath Feature Access (HFA)
• Gateways HG 3500 and HG 3575
• IP Distributed Architecture (IPDA)
• IP Terminals
• Large Enterprise Gatekeeper (LEGK)
• Mobile HFA
• OpenScapeAccess
• OpenScape 4000 SoftGate
• Payload Switching DMC
• RG 8350a
• Separate LAN Connectivity for Administration and VoIP
• Signaling and Payload Encryption (SPE)
• SIP Connectivity
• T.38 Fax
A31003-H3170-S103-6-7620, 02/2019
ip_en.fm
IP Solutions
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Basic Networking Principles
Networking
Networking
22 Basic Networking Principles
22.1 General Information

In this case, networking means interconnecting systems with different network
structures, such as
• several OpenScape 4000/HiPath 4000 systems with another or with old

systems via S0/S2 lines,
or
• virtual networking of several OpenScape 4000/HiPath 4000 systems with one

another or with old systems via carrier.
Networking can use either closed or open numbering (see Chapter 37, “LCR
(Least Cost Routing)”).
Heterogeneous networking, which is networking with systems from other

manufacturers, is also possible.
Note that in the case of network nodes without attendant console, you must
configure one console group with a night switch option as "station". This does not
require any hardware (see Chapter 153, “Attendant Console”).
22.2 Network Structures
22.2.1 Meshed network, fully meshed

In this type of network, each system has a direct connection to every other
system. Because of the large number of lines, this type of network is not useful in
large networks.
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Network Structures
A B
1-89-200
1-89-100
D C
1-89-300
1-89-400
Figure 4 Meshed Network, Fully Meshed
22.2.2 Meshed network, partially meshed

In this type of network, only some systems have a direct connection to every other
system.
A B
1-89-200
1-89-100
D C
1-89-300
1-89-400
Figure 5 Meshed Network, Partially Meshed
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Digit Analysis
22.2.3 Star-type network
A
Level 0
B C
Level 1
D E F
Level 2
Figure 6 Star-Type Network (hierarchical)
22.3 Digit Analysis

Store all numbers and codes (route and service codes) of a node and the
numbers and codes that should be available in other nodes in the digit analysis
of each node. Route and service codes lead to the digit analysis result (DAR)
"NETW" with the destination number (DESTNO) as additional information.
Network-wide station numbers lead to the DAR "STN" and also indicate the
DESTNO. For this reason, you must allocate one or more destination numbers (1
- 255), unambiguous throughout the network, to each node in a closed numbering
network.
You must assign each node a physical node number (PNNO in AMO ZAND) that
is unambiguous throughout the network. You must also assign at least one virtual
node number (NNO in AMO KNDEF) in each network node. The destination
number makes the connection between digit analysis and device search (AMO
RICHT) and only has to be unambiguous within a node.
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Station Numbers and Codes throughout the Network
You must manage the central office code in the dial plan (DPLN) on digit analysis
point CO or TIE (but not NETW!) if you want to use it to reach an external node.
In DAR pairs, select CHECK=N if you do not want the DAR partner to be treated
at the same time. Then you must configure the necessary partner with another
command. This improves the runtime.
IMPORTANT: The action REGEN only generates ADD command with

CHECK=N.
The default value is CHECK=ALL. If the station number contains special

characters and TEST=ALL is specified, then this either this is DAR without the
"dial pulsing" property or you must specify the parameter CDDP and, for DAR
pairs, the parameter CDDP2.
22.4 Station Numbers and Codes throughout the Network
22.4.1 Feature description

You store the entire station number household of a network in the DPLN of all
nodes.
With ADD WABE, you assign all network station numbers to the DAR=STA.
With CHA WABE, you assign all node-external station numbers a DESTNO.
If the nodes are not fully meshed, configure fictive routes with the destination
number of the destination node over the transit node. This is done with a separate
code to DAR "NETRTE" with the same trunk group that leads to the transit node,
but with the destination number on which the station device is configured. 
This does not apply to the central office code in nodes without trunks.
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Stn. 2100 - 2150 Stn. 2151 - 2300

Stn. 2151 - 2300 DESTNO 2 Stn. 2100 - 2150 DESTNO 1
Stn. 2400 - 2700 DESTNO 3 Stn. 2400 - 2700 DESTNO 3
A B
DESTNO 1 DESTNO 2
Stn. 2400 - 2700
Stn. 2100 - 2150 DESTNO 1
Stn. 2151 - 2300 DESTNO 2
DESTNO 3
Figure 7 Network with 3 Nodes, Fully Meshed
You can also configure several routes between 2 nodes and these routes can be
a mixture of analog and digital. You can assign a separate destination number to
each route. 
If you have configured the route with the digit analysis result NETRTE, you
determine the route that should be seized after this code is dialed by specifying
the appropriate DESTNO.
22.4.2 Service information
IMPORTANT: If there are several destination numbers to a destination system,

you must enter the correct destination number in the circuits of each of the routes
with the AMO TDCSU.
22.4.3 Generation (example)

You assign the station numbers to the separate nodes as follows (see figure
Network With 3 Nodes, Fully Meshed).
• Commands for node A:
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
ADD-WABE:CD=2100&&2300,DAR=STN; 
Assign the DESTNO for nodes of external stations as follows:
CHA-WABE:CD=2151&&2300,DESTNO=2; (station in node B) 
CHA-WABE:CD=2400&&2700,DESTNO=3; (station in node C)
• Commands for node B:
CHA-WABE:CD=2100&&2150,DESTNO=1; (station in node A)
CHA-WABE:CD=2400&&2700,DESTNO=3; (station in node C)
• Commands for node C:
CHA-WABE:CD=2100&&2150,DESTNO=1; (station in node A)
CHA-WABE:CD=2151&&2300,DESTNO=2; (station in node B)
The hunt group in node B (code = 83) should also be accessible from nodes A
and C (fully meshed).
• Configure the code in node B as follows:

ADD-WABE:CD=83,DAR=HUNT;
• To ensure that the hunt group in node B is accessible from node A, you must
enter the following command in node A:
ADD-WABE:CD=83,DAR=NETW,DESTNO=2;
• To ensure that the hunt group in node B is accessible from node C, you must
enter the following command in node A:
ADD-WABE:CD=83,DAR=NETW,DESTNO=2;
IMPORTANT: If a hunt group moves to another node, you must delete the hunt
group and the code and then add them to the new node. The only way to change
DAR=HUNT to DAR=NETW is by deleting it and then adding it again.
22.4.4 Relevant AMOs

Language
WABE RNR d Verzweigungsparameter
CD e access code / station number
KZP d Kennzahlpunkt
DAR e Digit analysis result
ZLNR d Zielnummer
DESTNO e destination number
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Physical and Virtual Node
22.5 Physical and Virtual Node

The physical node defines the PABX, virtual nodes define groups of subscribers
with the same numbering plan. Every subscriber and Attendant console must be
assigned to a virtual node (by. AMO SDAT). Virtual nodes are managed with the
AMO KNDEF. The numbering plan data for ISDN E.164/ PNP number plans and
for the OpenScape 4000 implicit numbering plan can be defined for every node
.Within a physical node at least one virtual node must be defined. However, this
can also extend over several physical nodes, or several virtual nodes be within
the same physical node.
A virtual node must be defined as a default node. The default node is used to
enable a node number for phone numbers, e.g. attendant and attendant group
code numbers which are not explicitly assigned to a virtual node..
The introduction of virtual nodes became necessary by the introduction of two

new features:
• IPDA:
Due to The subscribers of access points being assigned to different locations
If e.g. an Access Point is in Berlin, a different one in Munich, then the
participants in Munich shall be accessed under a Munich C.O. phone number
and in Berlin under a Berlin C.O number, This is achieved by assigning the
participants to two virtual nodes ,these both lie on the same physical node but
have different E.164 numbering plan data.
• USA EPNP:
U.S. American PABX's often have not one but several main office phone
numbers.This means that the public number plan in the USA can often
provide no more sufficient free direct dial numbers ranges in the required size
. E.g. a business needs 1800 Direct Dial numbers, perhaps it must buy 2 3-
digit direct dialling areas at 1000 numbers each and has therefore two E.164
Local destination codes.
Moving a station in a private network retaining the phone number (E.164/
PNP/OpenScape 4000 Numbering plan)has to be possible.
The normal case is: A physical node has a virtual node.
Virtual nodes are, identified by the virtual node number, physical nodes by the
physical node number.
Virtual nodes have a virtual node code for the OpenScape 4000 numbering plan
and /or E.164 or PNP codes. physical nodes have a physical node code.
The following pictures show the normal configuration and the application case
mentioned:
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Physical and Virtual Node
physical node physical node

phys. node id: 1-1-1 phys. node id: 1-1-2
phys. node number: 111 phys. node number: 112
4715 4716 2245
virtual node
virtual node virt. node id: 5-5-2
virt. node id: 5-5-1 virt. node number: 52
virt. node number: 51 E.164 codes: 49 89 636
E.164 codes: 49 89 722
Figure 8 Normal configuration for 2 PABX’s
4715 4716 2245

physical node
IP Netz
phys. node id: 1-1-1
phys. node number: 111 Muenchen, Berlin,
E.164: 49 89 722 E.164: 49 30 386
3789
Hamburg,
E.164:49 40 6371
virtual node virtual node

virt. node id: 5-5-1 virt. node id: 5-5-2
virt. node number: 51 virt. node number: 52
virtual node
virt. node id: 5-5-3
virt. node number: 53
Figure 9 IPDA Configuration
3 virtual nodes exist on a physical node.
Normal configuration after a move of stn 4716 taking with it the phone number
and the E.164 number in the implicit OpenScape 4000 number plan ( open
numbering)
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Node Number
physical node physical node

phys. node id: 1-1-1 phys. node id: 1-1-2
phys. node number: 111 phys. node number: 112
4715 4716 2245
virtual node virtual node

virt. node id: 5-5-1 virt. node id: 5-5-2
virt. node number: 51 virt. node number: 52
virtual node
virt. node id: 5-5-1
virt. node number: 51
Figure 10 Normal configuration after a move of a station
The virtual node 5-5-1 has extended itself into the physical node 1-1-2 and is
identicaly configured on both physical nodes.
22.6 Node Number
22.6.1 Feature Description

The node number serves administration and routing purposes. The numbers are
allocated by the network configurator and must be unique network-wide. The
Node number for a system is configured in every individual node with the AMO
ZAND, Parameter PNNO. This applies to both open and closed numbering
schemes.
A distinction is made between a physical and virtual (fictitious) node numbers .
For this function (LCR) an originating node number (ONNO) and an destination
node number (DNNO) were defined. These always describe entry and end-points
of a connection (not the transit nodes!)
Node number parameters are specified in the following AMOs:

ZAND, RICHT, KNMAT, TACSU, TDCSU, TSCSU, LDAT, KNFOR, WABE
(display only), ACSU, KNDEF, KNLCR, KNTOP and SDAT.
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Node Number
22.6.2 Structure Overview

The node numbers have a hierarchical structure. A network can have up to 3
levels , therefore the node numbers have up to to 3 levels. The representation at
the AMO-Interface is (except with AMO KNMAT)
aa-bbb-ccc, where
aa = Level 2 (Domain) Area number (0-29)

bbb = Level 1 (Subdomain) Area number (0-253)
ccc = Level 0 (Node) Node number (0-999)
A multi level node number is regarded as unique if it is different in at least one

level of the other node numbers.The node number 0 in lower levels means "any"
(e.g. 2-0-0). High-order zeros can be left out (e.g. 0-0-2 = 2).
22.6.3 Service Information

The AMO user is informed by a note (also see AMO application descriptions).
22.6.4 Physical Node Number

A physical node number in the AMO ZAND (configured with the parameter
PNNO) is the node number which defines a system (PABX).
Per system only one physical node number is possible..
The Phyisical Node number serves as a base for the automatic determination of
the network topology (AMO KNTOP) and the generation of the call IDs and leg
IDs.
22.6.5 Virtual Node Number

A virtual node number marks a virtual node with all its subscribers and attendants.
The virtual node numbers are managed in a table of their own with the AMO
KNDEF under the type =OWN and must be different from the physical node
number. Application examples can be found in the sections alternate routing
(LCR) and the Phone number modification.
22.6.6 Fictive Node Number

These are a special form of a virtual node number to manage connections to
systems or facilities (e.g. servers) which do not recognize node numbers.
It is possible to enter the fictitious node number as the ONNO of the remote
system(e.g. CO connections , VMS, Dictation equipment, PSE, Foreign system,
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Node Codes
analog Tie, digital Tie circuits to a foreign node). The number is assigned to a
circuit with the AMO TACSU, TDCSU and TSCSU (activation by means of COT
parameters) and an accompanying entry in the AMO KNDEF (under type =
FOREIGN with the required codes )is also required.
22.6.7 Originating Node Number

The Originating node number (ONNO) is the virtual or fictitious node numbers
which are at the starting point of a connection.
22.6.8 Destination Node Number

Destination Node numbers (DNNO) are those virtual or fictitious node numbers
which are destinations of a connection or connection set-up.
IMPORTANT: All node numbers of a network must be unique and should have
the same level format.
22.7 Node Codes
22.7.1 Physical Node Code

This node code number is the code number with which a physical node can be
reached by other nodes network wide. A node code number must be defined for
every node in the network. This applies to both open and closed numbering (
because of the feature route Optimization). The physical node code is configured
with AMO ZAND, Parameter PNODECD , and with AMO WABE with the DAR
OWNNODE.
22.7.2 Virtual Node Code

This node code number is the code number with which a virtual node can be
reached by other nodes network wide. The virtual node code number is provided
with AMO KNDEF, parameter NODECD for the unknown numbering plan and
also AMO WABE with the DAR OWNNODE. 
Note: If a physical node contains several virtual nodes, then several entries are
also necessary in the AMO KNDEF. For each virtual node number the
parameters NODECD and OWNNODE (with AMO WABE) have to be
configured..
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Node Codes
The node code is for open numbering and is modified by AMO KNMAT for the
phone number("calling numbers") modification feature.
22.7.3 Area, Area Numbering

The area which comprises all the nodes of a network corresponds to Level 0 of a
hierarchical network structure
An area defines all the nodes of a network including its sub-networks (see also
definition of hierarchical node numbers). The area number defines the area for
administration purposes. A Level 0 area includes all the networked nodes of that
level, and all the sub-networks at sub-network levels 1 and 2 which are accessible
through the nodes of the level 0 area. A Level1 area includes all the networked
nodes of the sub-network accessible through a particular node in a Level 0 area
as well as any sub-networks at sub-network level 2 which are accessible through
the nodes of the level 1 area.
22.7.4 Area Code

The area code forms part of a station number in the UNKNOWN OpenScape
4000 numbering scheme for open numbering. The area code is the route code
dialled to access a specific area. The area codes can correspond to the node
number hierarchy level, but do not have to. For example, the node with the node
number 1-2-3 may have the node code "99". This is the standard case in single-
level networks converted to multi-level networks, if the station numbers are to
remain unmodified. The node may also have the 3-level code 11-80-99. In this
case, the level 2 area code is 11, the level 1 area code is 80, and the level 0 area
code is 99. A station number 4711 within that node must then be dialled as
1180994711 from other nodes in the network.
The area codes are entered under the appropriate network level in the KNMAT
AMO (LEVEL=0 or 1 or 2).
22.7.5 Destination System Number

The destination system number (DESTNO) is used in closed numbering schemes
to assign the dialed network call number to the routes of outgoing trunk groups.
The DESTNO only needs to be unambiguous within a node.
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Node Codes
22.7.6 Route Code

The route code is the dialed digit sequence by means of which a particular route
is seized (e.g. trunk code, tie trunk code). Only in a closed numbering scheme are
there "fictitious" route codes which are not dialed.
22.7.7 Area-Code
An Area (also called domain here) is a closed numbered sub network concealed
within an open numbered network with several virtual nodes. You reach an Area
with a common code number, the Area code.. These must be set up in every
node in the Area (with AMO WABE) with DAR OWNNODE .From "the outside"
the Area looks like a single node which is reached with the Area Code. Also a
(physical node number) PNNO must be assigned to every node in the Area. For
the feature “Route Optimization” you must in addition establish a physical node
code number (PNODECD) which must be unique within the complete Area.
The Area code number is entered as the open numbering node code number in
AMO KNMAT for modification of station numbers.
IMPORTANT: An Area may be established only in level 0!
22.7.8 Tie Code

Another expression for the Route code number (colloquial)
IMPORTANT: In principle, every node can be dialed in the network with several
code numbers.These codes must then lead to AMO wabe DAR= OWNNODE.
You must, however, add one of these code numbers as a physical node code
number (with AMO ZAND, parameter PNODECD).
22.7.9 Route
Station-station connection, station-circuit connection or circuit-station connection
involving at least 2 PABXs in a network
22.7.10 Path
Station-station connection, station-circuit connection or circuit-station connection
within a PABX.
A31003-H3170-S103-6-7620, 02/2019
aanetbeg_en.fm
Node Codes
22.7.11 Source Group

A source group SRCGRP is a subdivision of a physical node into single groups
which doesn't have to be limited to a location. E.g. the subdivision into source
groups makes possible group dependent or shelf dependent LCR within a PABX
e.g. for emergency numbers.
A31003-H3170-S103-6-7620, 02/2019
alternate_routing_on_err_en.fm
Feature Description
23 Alternate Routing on Error

This feature provides an additional possibility to reach an alternate destination in
case of voice calls, if the called subscriber/ personal attendant is in an
out_of_service (OOS) situation.
The feature performs a new kind of alternate routing mechanism, using new
predefined alternate routing destination numbers, which can be subscriber
individual or source group related. In some cases (see below), new authorizations
will be validated.
In total, 6 different OOS scenarios of the called subscriber/ personal attendant will
be handled.
1. The called subscriber / personal attendant is OOS because of a device/board

error.
(no additional authorization necessary)
2. The called subscriber / personal attendant is OOS because switched off by

AMO.
(authorization necessary for doing alternate routing when manual switched
off by AMO)
3. The accesspoint (AP) of the called subscriber is in an AccessPoint

Emergency (APE) situation in relation to the AP of the calling device.
(no additional authorization necessary)
4. The called HFA IP phone is in OOS and has registered at OpenScape

Business/HiPath 3000 because of IP errors.
(authorization necessary for move logon from OpenScape 4000 to
OpenScape Business/HiPath 3000)
5. The called HFA IP phone is OOS because of a system failure and has been
moved to / has logged on to antoher OpenScape 4000 node.
(authorization necessary for move logon from OpenScape 4000 to another
OpenScape 4000 node)
6. For HFA IP subscribers, which have deregistered and are newly registered
somewhere else, a TSC setup from a XPRESSION server for indication of a
voice message, will be alternate routed to that switch, where the HFA IP
subscriber is registered actually.
Normally, alternate routing will be done only once for a call. In case of an alternate
routing because of APE, it might be necessary to execute another alternate
routing again for on of the other 3 mentioned OOS scenarios.
A31003-H3170-S103-6-7620, 02/2019
Feature Description
The reason why is, that in kind of APE, in the AP of the calling device, it can not
be verified for sure, whether the called subscriber in the target AP is in a seizable
condition.
Because of this consideration, it is possible to administer two types of alternate

routing destination numbers (OOS and APE) for a subscriber or a whole source
group with different alternate destinations.
23.1.1 Main goals for the alternate routing destination

numbers in respect to OOS scenario
• Device/ board error
The goal is, to reach the called subscriber either with its mobile phone
number, with an alternate number, via PSM or to lead the call to attendant,
voice mail, phonemail or something else.
• Manual deactivated (by AMO) with activated authorization for alternate

routing
If subscribers are manuel deactivated by AMO command, alternate routing
will only be performed, if the subscribers are authorized for requesting
alternate routing when called after a manual deactivation.
The goal are identical as for device/ board errors.
• APE situation between APs of calling device and called subscriber/ peronal
attendant.
In case of an APE situation between APs of calling device and called
subscriber/personal_attendant, the involved APs act as single switches.
The goal is, to reach the called subscriber in its AP via public trunk access.
As a precondition, a public trunk access has to be administered between the
related APs with routing elements without internal rerouting possibilities.
Routing elements, that are defined as with internal rerouting, will not be used
for alternate routing on error in general.
• Deregistered HFA IP phones (OpenScape 4000 --> OpenScape Business/

HiPath 3000).
Special authorized HFA IP phones can move their logon location from
OpenScape 4000 to OpenScape Business/HiPath 3000 in case of IP errors.
The goal is, to reach this HFA IP phones in their new logon location via public
trunk access under their individual (modified) extension numbers.
TSC setups with service MWI to a unregistered HFA IP subscriber will be
alternate routed to that switch, where the HFA IP phone is actually registered.
A31003-H3170-S103-6-7620, 02/2019
Feature Description
This is a special usage of the feature, as in this scenario, alternate routing

only will be started, if the administered alternate routing destination number
points to a tie trunk (no public trunk).
The reason for this is, that it is not possible to transport a MWI service via
public network.
• Deregistered HFA IP phones (OpenScape 4000 --> OpenScape 4000).

HFA IP phones are normally registered at a OpenScape 4000 node with
Xpressions. Special authorized HFA IP phones can move their logon location
from OpenScape 4000 to another OpenScape 4000 node in case of system
failure.
The goal is, to reach this HFA IP phones in their new logon location via tie
trunk access under their individual (modified) extension numbers and the
HFA IP phones will be supplied with MWI update information of the
Xpressions server.
The MWI led will be switched on or switched off at the HFA subscriber. The
HFA subscriber now has the possibility to call the Xpression server from the
alternate OpenScape 4000 via tie trunk access in order to pick up its voice
messages.
If the HFA subscriber has different numbers in default node and alternate
node, it may be necessary to use the mailbox number of the default node also
when picking up the voice messages out of alternate node.
Alternate Routing on Error via tie trunks to another OpenScape 4000 should
be used very restrictive. Furthermore, the administration should only be done
subscriber individual and not source group related.
23.1.2 Usage of Alternate Routing Destination

Numbers
You can administer an alternate routing destination number either as a subscriber
individual alternate routing destination number for one subscriber or a source
group related alternate routing destination number for a whole source group of
the related subscribers.
In order not to waste memory, for some OOS scenarios, it might be enough, You
would confine to source group related alternate routing destination numbers.
As You can administer a source group related alternate routing destination

number either as a complete number (EXTNO = 0) or as a incomplete number
(EXTNO > 0), You also have the possibility to reach subscriber individual
destinations with the supplementation. request (EXTNO > 0).
A supplementation will be done at time of alternate routing execution by call

processing with the administered length (EXTNO) of the called subscribers
extension number.
A31003-H3170-S103-6-7620, 02/2019
Feature Description
If You administer both kinds, and the numbers are different, the subscriber
individual alternate routing destination numbers will be used with higher priority
than the source group related alternate routing destination numbers. With this
design, You can treat special subscribers (vips) different than the rest of
subscribers of a source group.
In case of usage, the alternate routing destination number will be checked for
being usable to reach an alternate destination successfully. If it is not possible,
to reach an alternate destination with the subscriber individual alternate number,
another attempt will be done with the source group related alternate routing
destination number.
Depending of the OOS scenario (1 --> 4) the alternate routing destination

numbers will be checked for usage in following hierarchical manner:
• OOS because device/board error
– subscriber individual alternate routing destination number for OOS
– source group related alternate routing destination number for OOS
• OOS because manual deactivated with activated authorization for alternate

routing
• OOS of deregistered HFA IP phones with activated authorization for move

logon
• OOS because of APE situation between APs of called subscriber and calling
device
– subscriber individual alternate routing destination number for APE
– source group related alternate routing destination number for APE

If the called subscriber is not a HFA IP phone with the activated authorization
for move logon, 2 additional attempts will be done
– scriber individual alternate routing destination number for OOS
Device / board Manual Moved logon AP Emergency

error deactivated
subscr. indiv. subscr. indiv. subscr. indiv (OOS) subscr. indiv. (APE)
(OOS) (OOS)
A31003-H3170-S103-6-7620, 02/2019
Feature Description
Device / board Manual Moved logon AP Emergency

error deactivated
srcgrp. related srcgrp. related srcgrp. related scrgrp. related
(OOS) (OOS) (OOS) (APE)
subscr. indiv (OOS)
scrgrp. related
(OOS)
23.1.3 Philosophy of loop avoidance in public/

OpenScape 4000/HiPath 4000 network
If the administered alternate routing number leads to an external destination
within the OpenScape 4000/HiPath 4000 network, special classmark information
will be transported in the call_setup message, that takes care of loop avoidance
in the target OpenScape 4000 switch. No additional administration is necessary
for that case.
If the administered alternate routing number leads to an external destination

within the OpenScape 4000/HiPath 4000 network but using a partly routing via
public network, this classmarks cannot be transported. In this case, the loop
avoidance only can be done with use of an enlarged alternate routing destination
number. For this purpose, 2 DARs "ALTRTOOS, ALTRTAPE" are newly created.
Example_1:
In case of AP Emergency, the calling device out of AP_x wants to reach the
called subscriber in AP_y via public network.
Called subscribers extension number = 4711, outgoing public trunk access =

004989, incoming trunk access = 722, digit string, that leads to DAR
"ALTRTAPE" in the switch = 99.
The individual alternate routing number could be = 004989-722-99-4711.
The source-group related alternate routing number could be = 004989-722-99.
Example_2:
In case of OOS, for the called device (NOT_READY) in switch_1, the alternate
routing number will be designed in that way to reach an alternate subscriber in
OpenScape 4000 (switch_2) via public network.
Extension number of alternate subscriber in switch_2 = 4812, outgoing public

trunk access = 004989, incoming trunk access (switch_2) = 723, digit_string, that
leads to DAR ’ ALTRTOOS" in switch_2 = 98.
The individual alternate routing number could be = 004989-723-98-4812
A source-group related alternate routing number is not allowed in this case.
A31003-H3170-S103-6-7620, 02/2019
Feature Description
Warning:
The use of the 2 new DARs "ALTRTAPE" , "ALTRTOOS" for designing the
alternate routing number is only an option for loop avoidance in public network.
The necessity to use this option is much higher in case of alternate routing for
APE than for OOS. Nevertheless, the option in general should be used only in
following cases:
• An alternate destination should be reached in a OpenScape 4000 switch

partly routed via public network.
• The used new DARs "ALTRTAPE" or "ALTRTOOS" have to be administered

in the target OpenScape 4000 switch.
If the DARs are unknown, the digit translation in the target switch surely will not
find a valid result.
If this option is used in case of a routing only in OpenScape 4000/HiPath 4000

network, it does not create a problem at all, but it is not necessary.
23.1.4 Philosophy of supplementation (parameter

EXTNO)
If You administer a source group related incomplete alternate routing destination
number, You also have to define the number of the called subscribers digits for
the supplementation.
If You administer the source group related alternate routing destination number
as a complete number, You have to set the parameter EXTNO = 0;
If You administer the source group related alternate routing destination number
as a incomplete number, You have to set the parameter EXTNO to the number of
the called subscribers digits, that are requested for supplementation.
The plausibility of a supplementation (design and usage) depends from WABE

result of the source group related alternate routing destination number as well as
from the alternate routing type.
The plausibility checks of the AMO APRT allow the input of EXTNO > 0 only for
those alternate routing destination numbers, that do not lead to WABE result =
subscriber. But there are a lot of other possibilities that are not restricted by the
AMO, but cannot be executed at the time of usage for special alternate routing
scenarios.
A switch can be devided into several virtual switches. In every virtual swich,
subscribers can have numbers, that are also allocated in other virtual switches. It
is only possible, to distinquish this numbers with help of their virtual node access
code, which is a part of the subscribers number.
When administering the parameter EXTNO, You must be aware of this.
A31003-H3170-S103-6-7620, 02/2019
Feature Description
• Usage of supplementation for APE

If You want to reach the subscribers, that are in APE situations, via public
trunk loop in their own APs under their individual subscriber numbers, You
must administer a source group related incomplete alternate routing
destination number for type = APE, that contains a trunk access code for
going public network and a incoming trunk access code to reach the APs,
where the subscribers are located in, and as an option the digit string, that
leads to DAR = "ALTRTOOS".
The missing subscribers extension numbers will be supplemented at time of
call execution by call processing.
You have to administer, how many digits of the subscribers extension
numbers should be used for supplementation with setting the parameter
EXTNO > 0.
In this example, it is obvious, that EXTNO has to be set to the length of the
subscribers extension numbers.
If You set the parameter EXTNO bigger than the length of the subscribers
extension numbers, it is tolerated and will be decremented to the real length.
If You set the parameter EXTNO smaller than the length of the subscribers
extension numbers, this alternate routing destination number can not be used
for that case.
Example 3:
Outgoing public trunk access = 004989, incoming trunk access = 722,
Number (subscriber_A) = 54321, digit_string, that leads to DAR "ALTRTAPE" =

99
Administered source_group related alternate routing number = 004989-(99)-722
EXTNO = 5 --> supplementation done / result = 004989-722-(99)-54321

EXTNO = 6 --> supplementation done / result = 004989-722-(99)-54321
EXTNO = 4 --> supplementation not possible
EXTNO = 0 --> supplementation not requested / the number 004989722(99) do not
lead to a valid destination, but neither by AMO nor at time of usage,
this can be verified.
• Usage of supplementation for OOS (device/ board error or deactivated by

AMO)
If you want to reach the subscribers, that are in OOS situation, with searching
via PSM under their individual search numbers, You must administer a source
group related alternate routing destination number for type = OOS, that
contains the PSM access code.
The missing subscribers extension numbers will be supplemented at time of
call execution by call processing.
A31003-H3170-S103-6-7620, 02/2019
Feature Description

EXTNO > 0.
If the PSM is designed with search length = 0, the parameter EXTNO has to
be set to the length of the called subscriber numbers.
If the PSM is designed with search length = x, the parameter EXTNO has to
be set to that value (x). The normal situation is, that the search length is
smaller than the length of called subscribers. In this case, the
supplementation result leads to a cut search number. The cutting will be done
from right hand side.
Example 4:
PSM access code = #77
Number (subscriber_A) = 54321
Administered source group related alternate routing number = #77
Search length = 3
EXTNO = 3 --> supplementation done / result = #77-543

EXTNO = 0 --> supplementation not requested / invalid
Example 5:
PSM access code = #77
Number (subscriber_A) = 54321
Administered source group related alternate routing number = #77
Search length = 0
source group related alternate routing number = #77

EXTNO = 0 --> supplementation not requested / invalid
• Usage of supplementation for OOS in case of moved logon

If You want to reach the HFA IP phones, that have moved their logon location
from OpenScape 4000 to OpenScape Business/HiPath 3000 in their new
logon switch under their individual extension number, You have to administer
a source group related incomplete alternate routing destination number for
A31003-H3170-S103-6-7620, 02/2019
Feature Description
type = OOS, that contains a trunk access code for outgoing public network
and an incoming trunk access code, to reach the OpenScape Business/
HiPath 3000.
The missing subscriber extension numbers will be supplemented at time of
call execution by Call processing.
EXTNO > 0.
It may be possible, that OpenScape Business/HiPath 3000 works with a
different number scheme than OpenScape 4000.
If the HFA IP phone extension numbers are identically in both switches, You
have to set the parameter EXTNO to the identical extension number length of
the HFA IP phones.
If the HFA IP phone extension numbers in OpenScape Business/HiPath 3000
are smaller than in OpenScape 4000 (see example 4), You have to set the
parameter EXTNO to the smaller HFA IP phone extension number length. in
OpenScape Business/HiPath 3000. The later performed supplementation
then will cut the HFA IP phone extension numbers from left hand side on.
If the HFA IP phone extension numbers in OpenScape Business/HiPath 3000
are bigger than in OpenScape 4000 (see example 5), You have to set the
parameter EXTNO to the length of the HFA IP phone extension number in the
OpenScape 4000. As the extension numbers in OpenScape Business/HiPath
3000 starts with an additional digit (9), You must add this as a prefix to the
source group related alternate routing number.
Example 6:
Outgoing public trunk access = 004989,
Incoming trunk access for OpenScape Business/HiPath 3000 = 865
Number (HFA IP phone_A in OpenScape 4000) = 54321
Number (HFA IP phone_A in OpenScape Business/HiPath 3000) = 4321
Administered source group related alternate routing number = 004989-865
EXTNO = 4 --> supplementation done / result = 004989-865-4321

EXTNO = 5 --> supplementation done / result = 004989-865-54321
In OpenScape Business/HiPath 3000 -, the correct HFA IP phone can
not be reached.
No kind of syntax check can avoid this malfunction.
EXTNO = 3 --> supplementation done / result = 00498986-5321
In OpenScape Business/HiPath 3000 -, the correct subscriber can not
be reached.
EXTNO = 0 --> supplementation is not requested / invalid
A31003-H3170-S103-6-7620, 02/2019
Feature Description
Example 7:
Outgoing public trunk access = 004989,
Incoming trunk access for OpenScape Business/HiPath 3000 = 865
Number (HFA IP phone_A in OpenScape 4000) = 54321
Number (HFA IP phone in OpenScape Business/HiPath 3000) = 9-54321
Administered source group related alternate routing number = 004989-865-9
EXTNO = 4 --> supplementation possible / result = 004989-865-9-4321

In OpenScape Business/HiPath 3000, the correct subscriber can not
be reached
EXTNO = 5 --> supplementation done / result = 004989-865-9-54321
EXTNO = 6 --> supplementation done / result = 004989-865-9-54321
EXTNO = 0 --> supplementation is not requested / invalid
23.1.5 Implausible conditions for supplementation

1. The administered source group related alternate routing destination number
leads to WABE result unequal trunk or PSM/PSE and the parameter EXTNO
was set > 0.
– It makes no sense, to supplement a source group related alternate

routing destination number, that leads to a destination unequal trunk or
PSM.
This will be rejected by syntax check of AMO APRT.
2. In case of routing type APE, the administered source group related alternate
routing destination number, leads to a public trunk access.
– If the value of parameter EXTNO is administered smaller than the length

of the called subscribers extension number, the related subscriber can
not be reached.
The implausibility of the source group related alternate routing destination
number for this OOS scenario cannot be detected by the syntax checks
of AMO APRT and will only be verified at time of usage.
The result is, that this alternate routing destination number can not be
used for routing type APE.
– If the value of parameter EXTNO is administered bigger than the length

of the called subscriber extension number, it will be ignored.
In order to avoid wrong or misleading displays, the supplementation then
will be done only up to the real length of the called subscribers extension
number.
A31003-H3170-S103-6-7620, 02/2019
Feature Description
– If the value of parameter EXTNO is administered bigger than the

maximum length of subscribers extension number, the command will be
rejected by syntax check of AMO APRT.
– If the administered source group related alternate routing destination

number contains only a trunk access into public network and the value of
parameter EXTNO = 0, neither an alternate destination nor the called
subscriber in its AP can be reached.
A supplementation is necessary in this situation and a value of parameter
EXTNO = length of called subscriber must be set.
number for this routing scenario cannot be detected by the syntax checks
used for routing type APE.
3. In case of alternate routing type = OOS because of device/board error or

manual deactivated by AMO, the administered source group related
alternate routing destination number leads to WABE result = trunk.
– If the value of parameter EXTNO is > 0, a supplementation with the called

subscribers extension number is requested. This makes no sense in
general, as this subscriber is in OOS state and cannot be seized
successfully, even if doing a loop over public or tie trunk.
used for this routing scenario
4. In case of alternate routing type = APE or OOS because device/board error

or deactivated by AMO, the administered source group related alternate
routing number contains the access code for PSM/ PSE
• If the PSM/ PSE is designed with search length = 0, a supplementation is

necessary with the length of called subscribers number.
– If the administered parameter EXTNO is smaller than length of called

subscriber, a PSM search cannot be successful.

The implausibility of the source group related alternate routing
destination number for this routing scenario cannot be detected by
the syntax checks of AMO APRT and will only be verified at time of
usage.

used for this routing scenario
A31003-H3170-S103-6-7620, 02/2019
Feature Description
– If the administered parameter EXTNO is bigger than length of called

subscriber, a PSM search is possible.

The supplementation will done with the real length of the subscribers
extension number.
– If the administered parameter EXTNO is bigger than maximum

extension number length, the command will be rejected by syntax
check of AMO APRT
• If the PSM is designed with search length = x, a supplementation is

necessary with this length x
– If the administered parameter EXTNO is smaller than search length

x, a PSM search cannot be successful.

The implausibility of the source group related alternate routing
destination number for this routing scenario cannot be detected by
the syntax checks of AMO APRT and will only be verified at time of
usage.
– If the administered parameter EXTNO is bigger than search length x,

a PSM search is possible.

The supplementation will done up to the search length x.
5. In case of alternate routing type = OOS because HFA move logon from
OpenScape 4000 to OpenScape Business/HiPath 3000, the administered
source group related alternate routing destination number has to be designed
in that way, that is possible to reach the moved subscriber in its new switch
location via trunk access.
– If the administered parameter EXTNO = 0, the source group related

alternate routing destination number is designed as a complete number.
As it is not possible, to reach individual HFA IP phones with a unique
unsupplemented alternate routing destination number, this number
cannot be used for this routing scenario.
– If the value of parameter EXTNO is bigger than the length of the called
subscriber number in OpenScape 4000, the supplementation will be done
up to the real extension number length of the HFA IP phone in
OpenScape 4000.
A31003-H3170-S103-6-7620, 02/2019
Feature Description
23.1.6 Plausibility of alternate routing destination

numbers
The AMOs SDAT, ACSU and APRT allow only numbers, that leads to a valid
wabe result. Call processing, when trying to use the administered alternate
routing destination number does a lot of additional plausibility checks in relation
to the OOS scenario, the involved devices, the READY state of the alternate
destination etc.
The main goal of this additional checks are, to avoid loops in the network and to
allow other alternate destinations (call_forward), if the designed alternate routing
numbers would lead to a invalid or not seizable destination.
HFA IP phones with the authorization for moving their logon from OpenScape
4000 to OpenScape Business/HiPath 3000 may be deregidtered already in
OpenScape 4000 and not yet regidtered in OpenScape Business/HiPath 3000. In
order to avoid an alternate routing loop between this 2 locations, the IP address
of the partner gateway has to be administered for the related source group (of the
HFA IP phones).
Call processing, when finding out, that the calling device transports the same IP
address as administered in the source group of the called HFA IP phone, avoids
an alternate routing.
23.1.7 Advisory output

In order to be informed about not usable administered alternate routing data, You
can request a advisory printout with following AMO command.
CHANGE-DIAGS:PROCID=CC,COMP=CP2,S07=ON
Whenever at time of execution, alternate routing on error is not possible because
of invalid alternate routing number administration, an advisory printout like
following example will be printed out.
F4066 M4 N0093 NO ACT BPA CP ADVISORY
03-09-10 13:32:14
CC:15359 EC: 2017 UA:9740:4BB6 SP:C078:1136 LD:01-01-079-004
DT:6C ST:6C SN:B401 CEVT:EF CSEV: 0 CST: 0
FORMAT:24 MESSAGE-ID: 00060
1. 5. 9. 13.
17. 21. 25. 29.
1A8B3A00 1D3D001C 01040303 04040000 584F7070 B8003000
C04ED84E 84117DC1
02040000 00000000 00000000 00000000 00000000 00000000
00000303 04040000
A31003-H3170-S103-6-7620, 02/2019
Feature Description
01000001 03000000 03040000 00030504 00000000 00000000

00000000 00000000
00000000 00000000 00000000 02010000 08000000 00000103
080C0000 08050000
00000100 00000000 00000000 01
byte 1: diagnose format (1A)
byte 2: format length (8B)
byte 3-4: calling loden (3A00)
byte 5: calling device type: (1D) =
DB_CP_DEVTYP_DIGITE_SUB_A
byte 6-7: called loden (3D00)
byte 8: called device type (1C) =
DB_CP_DEVTYP_DIGITE_MAIN
byte 9: called source group (01)
byte 10: called number length (04)
byte 11-32: called number (03 03 04 04
......................)
byte 33: altern route reason (02) 01: OOS AP
emergency
02: OOS
deactivated by AMO
03: OOS device
/ board error
04: OOS move
HFA move logon
byte 34: altern rej reason (04) 01: no gateway_IP
address defined
02: defined
gateway_IP = received gateway_IP
03: no valid
wabe result for alt_rt_on_err
04: alt_rt_nr
too short
05: alt_rt_nr
equals to calling/ redir nr
06: supplementation
of alt_rt_nr. impossible
07: alt_rt_nr is/
becomes too long
08: alt_rt_nr
same as redir_nr
09: length of
supplementation invalid
10: alt_rt_nr
leads to not allowed dest
A31003-H3170-S103-6-7620, 02/2019
Feature Description
11: alt_rt_nr not

usable for PSM cond.
12: alt_rt_nr not
usable for PSE cond.
13: alt_rt_nr not
usable for PSE_CZ ond.
14: dest. of
alt_rt_nr not free
15: no loden
found with alt_rt_nr
16: alt_rt_nr
equals calling or called nr
17: suppl. not
allowed for OOS
18: alt_rt_nr is
source_group complete
19: no emergency nr
defined for HFA IP phone
20: alt_rt_nr
defined but not usable
21: general
implausibility in alt_rt_on_err
byte 35 length subscr. indiv. alternate routing number
for type = APE
byte 36 - 57 subscriber individual alternate routing number
for type = APE
byte 58 length srcgrp related alternate routing number
for type = APE
byte 59 - 80 source group related alternate routing number
for type = APE
byte 81: number of supplemented digits for type= APE
byte 82 - 85 gateway_IP address ( not used )
byte 86 length subscr. indiv. alternate routing number
for type= OOS
byte 87 - 108 subscr. indiv. alternate routing number for
type= OOS
byte 109 length srcgrp related alternate routing number
for type= OOS
byte 110 - 131 source group related alternate routing number
for type= OOS
byte 132 number of supplemented digits for type = OOS
byte 133 - 136 gateway_IP address for HFA move logon
byte 137 - 140 gateway_IP address in CPB
A31003-H3170-S103-6-7620, 02/2019
User interface
23.2 User interface
23.2.1 Called subscribers (A,B,C,D,E of one source

group), are not reachable, because of device/board
errors
• What are the main goals ?
Calling a subscriber specific individual alternate routing destination number
(mobile phone number)
Calling a general destination like voicemail or attendant.
• What is possible ?
The alternate routing number can be designed to reach any other destination.
If the alternate routing destination number leads to a outgoing trunk access,
only those route elements will be used for alternate routing, that are defined
as with " no internal rerouting ".
• What You want is:
– Calls to subscriber_A should be alternate routed to a mobile phone

number 017nn...nn.
– Calls to subscriber_B should be alternate routed to subscriber_F
– Calls to all other subscribers of the related source group, (C,D,E) should
be alternate routed to the attendant.
For the related source group (C,D,E), You can define a source group
related complete alternate routing destination number for routing type =
OOS
ADD-APRT:TYP=ALTERR,SCRGRP=<sg_subscr>,ALTRTYPE=OOS,
AlTRTNR=<no_melden>;
For routing type = OOS, You must define a subscriber individual
alternating routing destination number for subscriber_A
CHANGE-SDAT: STNO=<no_subscr_A>,TYPE=DATA1,STNOOOS=<017nn-
--nn>;
For routing type = OOS, You must define a subscriber individual alternate
routing destination number for subscriber_B
CHANGE-SDAT:
STNO=<no_subscr_B>,TYPE=DATA1,STNOOOS=<no_subscr_F>
Make sure, that the maximum number of individual alternate routing
destination numbers is big enough, otherwise increase the maximum
number value by AMO DIMSU
ADD-DIMSU: TYP=USER, ALTERR =<new_value>;
A31003-H3170-S103-6-7620, 02/2019
User interface
• What You want is: Calls to all subscribers of source group = 2 should be
alternate routed to PSM
It will be assumed, that the PSM works with LENGTH_SEARCH_NO = 0.
For routing type = OOS, You must define a source group related incomplete
alternate routing destination number for that source group, the called
subscribers are members of.
As for every subscriber an individual search number is requested, the
alternate routing destination number must be a incomplete number containing
only the access code for PSM.
You must set the number of the supplemented digits (parameter EXTNO)
equal the number length of subscribers extension number.
ADD-
APRT:TYP=ALTERR,SRCGRP=<sg__subscr>,ALRTYPE=OOS,ALTRTNR=<no_p
sm>, EXTNO=<length_subscr_no>;
If the PSM works with length search no = x (1-6), You must administer the
parameter EXTNO = <length_search_no>l
IMPORTANT: If You change the source group of a subscriber with AMO

SDAT, the administered source group related alternate routing informations
may not be valid anymore for this subscriber !
• Voicemail is the chosen destination of the alternate routing on error
NOTE: If a voicemail is the chosen destination of the ARoE (e.g. via

STNOOOS) then COT ARCF is needed to ensure a Diversion Leg is
generated towards the Voicemail and the correct mailbox is reached.
23.2.2 Called subscribers (A) is not reachable,

because deactivated via AMO with additional request
for alternate routing
Calling a subscriber specific individual alternate routing destination number
(mobile phone number)
Calling a general destination like voicemail or attendant.
The alternate routing number can be designed to reach any other destination.
A31003-H3170-S103-6-7620, 02/2019
User interface

• What You want is: Calls to a deactivated subscriber_A should be alternate

routed to voicemail.
For routing type = OOS, You must define either a subscriber individual
alternate routing destination number for the subscriber_A or a source group
related alternate routing destination number for that source group,
subscriber_A is a member of.
CHANGE-SDAT:
STNO=<no_subscr_A>,TYP=DATA1,STNOOOS=<no_voicemail>; or
ADD-APRT:TYP=ALTERR,SRCGRP=<sg_subscr_A>,ALTRTYPE=OOS,
ALTRTNR=<no_voicemail>
You must set a request for alternate routing, before deactivating the
subscriber_A with AMO SDAT
CHANGE-SDAT:STANO=<no_subscr_A>,TYP=DATA1,AMOALTRT=J;
If You set this request and no kind of alternate routing destination number was
administered before, the AMO SDAT will print out a hint-message.
23.2.3 Called HFA IP phones (A,B) are not reachable,

because of IP errors, they moved their logon location
from OpenScape 4000 to OpenScape Business/
HiPath 3000
• Device configuration:
OpenScape 4000 OpenScape Business/

HiPath 3000
number (HFA IP phone A): 54711 4711
number (HFA IP phone B): 54712 4712
station number length: 5 4

The main goal is, to call the OpenScape 4000 deregistered HFA IP phone in
its new logon switch (OpenScape Business/HiPath 3000) via public trunk
under its new or identical subscriber number.
The alternate routing destination number can be designed as outgoing public
trunk access or outgoing tie trunk access followed by incoming trunk access
to reach the OpenScape Business/HiPath 3000.
A31003-H3170-S103-6-7620, 02/2019
User interface
The alternate routing destination number can be designed as a subscriber

individual alternate routing number or as an incomplete source group related
alternate routing number (with supplementation request).
Not allowed is a source group related complete alternate routing number, as
it is not possible, to reach individual subscribers in this way.
Not allowed are alternate routing numbers, that do not lead to a trunk access.
• What You want is: Calls to not reachable HFA IP phones, that have moved
their logon location from OpenScape 4000 to OpenScape Business/HiPath
3000, should be routed to the new logon location via public network. In
OpenScape Business/HiPath 3000, the HFA IP phones have a different
number scheme than in OpenScape 4000.
You must authorize those HFA IP phones, that can move their logon location
from OpenScape 4000 to HiPath 300
AEND-SDAT: STANO = <no_hfa_ip_A>, TYP=DATA1, UZHFAIP=J;
AEND-SDAT: STANO = <no_hfa_ip_B>, TYP=DATA1, UZHFAIP=J;
You must set the gateway_IP address(es) for the source group(s), the HFA IP
phones are members of. This is necessary to avoid loops within OpenScape
4000 and OpenScape Business network/HiPath 3000 network.
For example, it could be possible, that a HFA IP phone is already
deregistered in OpenScape 4000 and not yet registered in OpenScape
Business/HiPath 3000. In this case, every switch tries to perform an alternate
routing to the other switch (ping/pong).
ADD-APRT: TYP= ALTERR, SRCGRP=<srcgrp_hfa_ip_A>,ALRTTYPE=OOS,
GWIPADR=<ip_addr_gateway>;
For type= OOS, You must define either subscriber individual alternate routing
destination numbers for every HFA IP phone (A,B) or a source group related
incomplete alternate routing destination number for the source group(s), the
HFA IP phones are members of.
A incomplete alternate routing destination number will be supplemented at
time of usage with the extension number of the called HFA IP phone and with
the administered length (parameter EXTNO). This makes it possible to reach
individual subscribers in other switches.
If You want to use only subscriber individual alternate routing destination
numbers, You have to administer a subscriber individual alternate number for
both HFA IP phones with outgoing trunk access to public network (004989),
with incoming trunk access to reach the OpenScape Business/HiPath 3000 (
568 ) and the shortened part of the extension numbers ( 4711, 4712 ).
AEND-SDAT:STANO=<no_hfa_ip_A>, TYP = DATA1, STNOOOS=<004989-
568-4711;
A31003-H3170-S103-6-7620, 02/2019
User interface
AEND-SDAT:STANO=<no_hfa_ip_B>, TYP = DATA1, STNOOOS=<004989-

568-4712;
If You want to use only source group related incomplete alternate routing
destination numbers, You have to administer the source group related
alternate destination number with outgoing trunk access to public network
(004989) and with incoming trunk access ( 568 ) to reach the OpenScape
Business/HiPath 3000.
Furthermore, You must set the supplementary length (parameter EXTNO) to
the length of the HFA IP phones number in the OpenScape Business/HiPath
3000, which is = 4.
ADD-APRT: TYP=ALTERR, SRCGRP=<srcgrp_hfa_ip_A>,ALRTTYPE=OOS,
ALTRTNR=004989-568,EXTNO=4;
OpenScape 4000 OpenScape Business/

HiPath 3000
number (HFA IP phone A): 54711 954711
number (HFA IP phone B): 54712 954712
station number length: 5 6
• What You want is: Calls to not reachable HFA IP phone, that have moved their
logon location from OpenScape 4000 to OpenScape Business/HiPath 3000,
should be routed to the new logon location via public network. In OpenScape
Business/HiPath 3000, the HFA IP phones have a different number scheme
than in OpenScape 4000.
You must authorize those HFA IP phones, that can move their logon location
from OpenScape 4000 to HiPath 300
AEND-SDAT:STANO=<no_hfa_ip_A>,TYP=DATA1,UZHFAIP=J;
AEND-SDAT:STANO=<no_hfa_ip_B>,TYP=DATA1,UZHFAIP=J;
You must set the gateway_IP address(es) for the source group(s), the HFA IP
phones are members of. This is necessary to avoid loops within OpenScape
4000 and OpenScape Business network/HiPath 3000 network. For example,
it could be possible, that a OpenScape 4000 deregistered HFA IP phone is
not yet registered in OpenScape Business/HiPath 3000 and every switch tries
to perform an alternate routing to the other switch (ping/pong).
ADD-APRT:TYP=LTERR,SRCGRP=<srcgrp_hfa_ip_A>,ALRTTYPE=OOS,
GWIPADR=<ip_addr_gateway>;
For type= OOS, You must define either subscriber individual alternate routing
destination numbers for every HFA IP phone (A,B) or a source group related
incomplete alternate routing destination number for the source group(s), the
HFA IP phones are members of.
A31003-H3170-S103-6-7620, 02/2019
User interface
A incomplete alternate routing destination number will be supplemented at

time of usage with the extension number of the called HFA IP phone and with
If You want to use only subscriber individual alternate routing destination
numbers, You have to administer a subscriber individual alternate number for
both HFA IP phones with outgoing trunk access to public network (004989),
with incoming trunk access to reach the OpenScape Business/HiPath 3000 (
568 ) , with a number prefix ( 9 ) and the extension numbers ( 54711,5 4712 ).
AEND-SDAT:STANO=<no_hfa_ip_A>,TYP=DATA1,STNOOOS=<004989-568-
9-54711;
AEND-SDAT:STANO=<no_hfa_ip_B>,TYP=DATA1,STNOOOS=<004989-568-
9-54712;
If You want to use only source group related incomplete numbers, You have
to administer the source group related alternate destination number with
outgoing trunk access to public network (004989) and with incoming trunk
access ( 568 ) to reach the OpenScape Business/HiPath 3000.
the length of the HFA IP phones number in the OpenScape 4000, which is 5,
ADD-APRT:TYP=ALTERR,SRCGRP=<srcgrp_hfa_ip_A>,ALTRTYPE=OOS,
ALTRTNR=004989-568-9,EXTNO=5;
23.2.4 Called HFA IP phones are not reachable,

because of system failure errors, they moved their
logon location from OpenScape 4000 to another
OpenScape 400 (MWI Indication)
• Scenario
HFA IP phones are normally registered at a OpenScape 4000 node with
Xpressions. Special authorized HFA IP phones can move their logon location
from OpenScape 4000 to another OpenScape 4000 node in case of IP errors.
• Main goal
The goal is, to reach this HFA IP phones in their new logon location via tie
trunk access under their individual (modified) extension numbers and the
HFA IP phones will be supplied with MWI update information of the
Xpressions server.
The MWI led will be switched on or switched off at the HFA subscriber. The
HFA subscriber now has the possibility to call the Xpression server from the
alternate OpenScape 4000 via tie trunk access in order to pick up its voice
messages.
A31003-H3170-S103-6-7620, 02/2019
User interface
If the HFA subscriber has different numbers in default node and alternate
node, it may be necessary to use the mailbox number of the default node also
when picking up the voice messages out of alternate node.
Alternate Routing on Error via tie trunks to another OpenScape 4000 should
be used very restrictive. Furthermore, the administration should only done
subscriber individual and not source group related.
• Administration
In the node with Xpression allocation, following administration has to be done:
– For HFA subscriber, it is necessary to set a mark for moving logon

location
CHANGE-SDAT:STNO=4711,TYPE=DATA1,MVHFAIP=YES;
– In order to avoid network loops, it is necessary to set the partner gateway
IP address for that sourcegroup, that is allocated to the related HFA
subscribers.
ADD-
APRT:TYPE=ALTERR,SRCGRP=1,ALRTYPE=OOS,GWIPADR=<ip_address_
of_gw>;
– For the HFA subscriber, it is necessary to administer an alternate routing
destination number, which leads via tie trunk to an alternate OpenScape
4000 node.
ADD-SDAT:STNO=4711,TYPE=DATA1,STNOOOS=723-4711;
– There is an other possibility, to administer an alternate routing destination
number for the complete source group, the HFA subscriber is a member
of (not recommended).
ADD-
APRT:TYPE=ALTERR,SRCGRP=1,ALRTYPE=OOS,ALTRTNR=723,GWIPADR=
<ip_address_of_gw>,EXTNO=4;
In the node, to which the alternate routing on error points, following
administrations have to be done:
It is necessary to install a relation between subscriber and XPRESSION. In
this case, the subscriber is that number with what the HFA subscriber from
the node with the XPRESSION is logged on in the alternate node.
CREATE-RICHT:MODE=PM,IDX=1,SAN=nnnnn,NAME=PHONEMAIL;
CHANGE-SBCSU: STNO=4711,PMIDX=1;
Interdependencies with other Requests:
Alternate routing on error for MWI uses the functionality of common Alternate
routing on error for HFA phone, that can change its logon location in case of
IP quality problems (loss of LAN connection etc.) This means, that this feature
only can be used, if the basic Alternate routing on error works also fine.
A31003-H3170-S103-6-7620, 02/2019
User interface
23.2.5 Called subscribers (A,B) in its APs are in an

APE situation to AP of the calling device
number (subscriber_A) = 4711
number (subscriber_B) = 4712
subscriber A,B in same source group

The main goal is, to reach the subscribers, that are in APE situation to the
calling device, via public trunk loop in their own APs.
Another goal may be, to reach the subscriber via its individual mobile phone
number.
All other alternate routing destination numbers, that lead to a valid internal or
external phone number, are possible.
The alternate routing destination number can be designed as outgoing public
trunk access or tie trunk access followed by an incoming trunk access to
reach an AP. In case of a partly routing via public trunk, in order to avoid
possible loops in public network, it would be a good option to enlarge the
alternate routing destination number with that number, that will be evaluated
in the target OpenScape 4000 switch to the result "ALTRTAPE"
The alternate routing destination number can be designed as a subscriber
individual alternate routing number or as a source group related incomplete
alternate routing number (with supplementation request).
If the alternate routing destination number is designed as a source group
related incomplete number, the supplementation can only be done with the
identical subscribers extension number (parameter EXTNO = length of
subscribers extension number).
• What You want is: Calls subscribers A,B, that are in an APE situation to the
calling device, should be routed to the called subscribers in its AP via public
trunk loop.
In case of APE, in the AP of the calling devices, it can not be verified, whether
the called subscribers in their own AP are in a seizable situation or not.
Therefore, it makes sense, to alternate route the call to the originally called
subscribers in their own APs via public trunk loop. The incoming trunk at
target AP, then can verify for sure the real state of the called subscribers.
A31003-H3170-S103-6-7620, 02/2019
User interface
For type = APE, You have to administer either subscriber individual alternate
routing numbers of type = APE for subscriber A and B or incomplete source
group related alternate routing numbers of type = APE for the source
group(s), the subscriber A,B are members of.
If You are sure, You don’t need different alternate routing destinations for type
= OOS, You also can administer the mentioned alternate routing destination
numbers for type = OOS for use of APE.
An incomplete alternate routing destination number will be supplemented at
time of usage with the extension number of the called subscriber A,B and with
If You use subscriber individual alternate routing destination numbers, You
have to administer a subscriber individual alternate number for the
subscribers A and B with outgoing trunk access to public network (004989),
with incoming trunk access to reach the OpenScape 4000 ( 723 ) and with the
individual subscriber numbers of subscriber_A and subscriber_B. If You use
the option for loop avoidance, You have to enlarge the alternate routing
destination number with that digit string, that will be evaluated in the target
OpenScape 4000 switch to the result ’ALTRTAPE" (99)
AEND-SDAT:STANO=<no_subscriber_A>,TYP=DATA1,STNOOOS=<004989-
723-(99)- 4711;
AEND-SDAT:STANO=<no_subscriber_B>,TYP=DATA1,STNOOOS=<004989
723-(99)-4712;
If You use only source group related incomplete alternate routing destination
numbers, You have to administer the source group related alternate
destination number with outgoing trunk access to public network (004989)
and with incoming trunk access ( 723 ) to reach the AP of the called
subscriber (A,B) in OpenScape 4000.
If You use the option for loop avoidance, You have to enlarge the alternate
routing destination number with that digit string, that will be evaluated in the
target OpenScape 4000 switch to the result ’ALTRTAPE" (99).
the length of the subscriber number in the OpenScape 4000, which is = 4. In
this case, You must not use a different value for EXTNO than the length of the
subscriber number of subscriber A or B.
ADD-APRT:TYP=ALTERR,SRCGRP=<srcgrp_subscriber_A,ALRTTYPE=APE,
ALTRTNR=004989-723-(99), EXTNO=4;
• What You want is: Calls to not ready subscribers of source group 1, that are
in an APE situation to the calling device, should be routed to the attendant
console. Calls to not ready subscriber_A, of source group 1, that is in an APE
situation to the calling device, should be routed to a subscriber individual
mobile phone number.
For type = APE, You must define a source group related complete alternate
routing destination number for the source group = 1.
A31003-H3170-S103-6-7620, 02/2019
Service Information
ADD-
APRT:TYP=ALTERR,SRCGRP=1,ALTRTYPE=APE,ALTRTNR=<no_melden>;
For type = APE and for subscriber_A, You must set the subscriber individual
alternate routing number to the individual mobile phone number.
AEND-SDAT:STANO=<no_subscriber_A>,TYP=DATA1,STNOAPE=<0-0049-
1712272123;
If You are sure, You will not use different alternate routing destination
numbers for OOS and APE situations, it may be enough to define only
alternate routing destination numbers for the type = OOS.
ADD-
APRT:TYP=ALTERR,SRCGRP=1,ALRTTYPE=OOS,ALTRTNR=<no_melden>;
AEND-SDAT:STANO=<no_subscriber_A>,TYP=DATA1,STNOOOS=<0-0049-
1712272123;
23.3.1 General plausibility information

The amo syntax checks cannot verify all implausible administered alternate
routing informations.
The administrator therefore has to verify itself very careful, whether alternate
routing destination numbers in networking leads to seizable destinations.
Even if implausible alternate routing data passes the amo syntax check, call
processing will prevent system confusion like loops in switch or networking.
Unusable alternate routing destination numbers will be indicated by advisory

outputs at usage time, if the related DIAGS switches are set.
23.3.2 Special restriction information

The AMO SDAT allows, to set the parameters UZHFAIP and AMOALTRT in
parallel for HFA IP phones. Specially for this type of subscriber, the combination
of this 2 parameters does not make sense, because a HFA IP phone, that is
authorized for moving its logon location from OpenScape 4000 to OpenScape
Business/HiPath 3000 in case of IP errors (UZHFAIP) must not request alternate
routing, if manuel deactivated by amo (AMOALTRT).
The parameter AMOALTRT only makes sense for those HFA IP phones, that are
not authorized for moving their logon location.
The related checks are performed only from call processing at time of execution.
A31003-H3170-S103-6-7620, 02/2019
Generation
23.4 Generation
Please refer to Section 23.2, “User interface”.
23.5 Realization via A&S Tools: Screenshots and additional information

An adaptation of A&S is necessary and requested and will be handed in later.
23.5.1 Realization via AMO: AMO or AMO Batch
AMO Feature Relevant Meaning

Commands
DIMSU ADD - TEST - DISP • Define the maximum number of
subscriber individual alternate routing
destination numbers
SDAT CHANGE - DEL - DISP • Administer the subscriber individual
alternate routing destination number
for OOS
• Administer the subscriber individual

for APE
• Set the authorization to move the

logon location for a HPA IP phone
• Set the authorization for alternate

routing on error, when deactivated by
AMO
APRT ADD - CHANGE - DEL - DISP • Administer the source group related
for OOS
• Administer the source group related

alternate routing number for APE
• Administer the source group related

gateway_IP address for OOS (move
logon)
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
AMO Feature Relevant Meaning

Commands
ACSU ADD - CHANGE - DEL - DISP • Administer the subscriber individual
alternate routing destination for OOS
• Administer the subscriber individual

for APE
• Set the authorization for alternate

routing on error, when deactivated by
AMO
23.6 Relevant AMOs

Language
DIMSU ALTERR d Anzahl der teilnehmerindividuellen
alternativen Routing Ziel-Nummern
ALTERR e number of subscriber individual alternate
routing destination numbers
SDAT UZHFAIP d Berechtigung fuer Logon in OpenScape
Business/HiPath 3000
MVHFAIP e Authorization for move logon to OpenScape
Business/HiPath 3000
AMOALTRT d Berechtigung fuer alternatives Routing, falls
mittels AMO deaktiviert
AMOALTRT e Authorization for alternate routing on error if
manual deactivated by AMO
TLNNUOOS d Teilnehmer individuelle alternative Routing
Nummer fuer OOS
STNOOOS e Subscriber individual alternate routing
number for OOS
TLNNUAPE d Teilnehmer individuelle alternative Routing
Nummer fuer APE
STNOAPE e Subscriber individual alternate routing
number for APE
ACSU AMOALTRT d Berechtigung fuer alternatives Routing, falls
mittels AMO deaktiviert
AMOALTRT e Authorization for alternate routing on error if
manual deactivated by AMO
TLNNUOOS d Teilnehmer individuelle alternative Routing
Nummer fuer OOS
A31003-H3170-S103-6-7620, 02/2019
Frequently Asked Questions (FAQs)

Language
STNOOOS e Subscriber individual alternate routing
number for OOS
TLNNUAPE d Teilnehmer individuelle alternative
Rufnummer fuer APE
STNOAPE e Subscriber individual alternate routing
number for OOS
APRT ALTERR d Typenausscheidung fuer den neuen Zweig
Alternatives Routen im Fehlerfall
ALTERR e Type definition for new brach = alternate
routing on error
ALTRTYPE d Typ des alternate Routings (OOS oder
APE)
ALTRTYPE e Typ of alternate routing (OOS or APE)
ALTRTNR d Source Gruppe bezogene alternative
Routing Nummber fuer OOS oder APE
ALTRTNT e source group related alternate routing
number for OOS or APE
ERWANZ d Erweiterungsangabe zur alternative
Routing Nummer fuer OOS oder APE
EXTNO e supplementation information for alternate
routing number for OOS or APE
GWIPADR d Gateway_IP Adresse fuer den Typ = OOS
GWIPADR e Gateway_IP address for typ = OOS
COT ARCF d Konvertiert Alternate Routing zu CFU im
Fehlerfall
ARCF e Convert alternate routing on error to CFU
23.7 Frequently Asked Questions (FAQs)

• Question: Why do we need ARoE and what does it do?
– If a call is made to an unavailable (OOS or AP Emergency mode) station

or a personal attendant console (AC), the call is routed to an alternate
destination if this has been administered appropriately.
– If a call to an attendant console group is made from an AP in AP

Emergency mode, if an individual AC or an night station cannot be called,
the call is routed to the HHS/AP where the AC is physically installed, if the
source group = 0 has been administered appropriately.
A31003-H3170-S103-6-7620, 02/2019
– If CCM paging or a page attempt is initiated from an AP in AP Emergency

mode when CCM is unavailable (perhaps because it was configured in
the HHS), the call can be routed to the relevant HHS/AP if the CCM
source group can be administered.
• Question: In which scenarios is ARoE used?
– For calls to stations or personal attendant consoles that are in

"NOT_READY" mode.
– For calls to attendant console groups for which there are no available
consoles or night stations.
– For CCM paging and page attempts when CCM is unavailable.

The following different scenarios exist:
1. The station/personal AC is in NOT_READY mode due to a device/

module error.
2. The station/personal AC is in NOT_READY mode because it was

deactivated using an AMO command. Concurrently a privilege for
ARoE is set by AMO command when the station/personal AC is
deactivated.
3. The station is an HFA_IP telephone with Move_ Logon privilege in

NOT READY mode. It has deregistered from the OpenScape 4000
due to an IP error and has registered to a backup node (OpenScape
Business/HiPath 3000).
4. The station/personal AC is in NOT READY mode because its access

point (AP) which connects to the AP of the calling station is in AP
Emergency (APE) mode.
5. The station is an HFA IP telephone and is inactive.
6. Due to AP Emergency, none of the AC group stations are available.
7. Due to AP Emergency, CCM paging and page attempts are not

possible.
The NOT_READY scenarios 1, 2, 3 and 5 are classed as OOS while
scenarios 4, 5 and 6 are classed as APE.
• Question: Which alternate numbers can be administered?
– In principle, more alternate numbers can be administered for each

implementation scenario than is practical. The syntax checks for the
AMOs SDAT, ACSU and APRT are very rudimental.
Call Processing checks the usability of the alternate numbers for the
relevant call scenario much more precisely and rejects the number if
necessary. For example, CP does not permit an internal station number
to be used as an alternate phone number for HFA_IP Move_logoff/Logon.
A31003-H3170-S103-6-7620, 02/2019
• Question: Which alternate numbers are practical for each of the following
implementation scenarios?
1. OOS due to device/module error:

Mobile number/paging number/attendant code/hunt group/etc.
2. OOS due to deactivation via AMO:
3. OOS due to logon of HFA IP telephones to an alternate node
An external phone number to the alternate node with the station number.
4. APE scenario between the caller and the called station.
A public network phone number with the station number.
5. An HFA IP telephone is inactive.
6. Due to AP Emergency, there are no attendant group devices available.
An external phone number to the HHS/AP where the AC is physically
installed.
7. Due to AP Emergency, CCM paging and page attempts are not possible.
An external phone number to the HHS/AP where CCM is physically
installed.
• Question: How are alternate phone numbers configured?
– Station-specific alternate phone numbers can be configured for OOS and/

or APE using the AMO SDAT or ACSU.
– Source-group (destination source group) related alternate phone

numbers can be configured for OOS and/or APE using the AMO APRT.
• Question: Can the configuration of nonsensical phone numbers cause

problems for the switching system?
– The AMO syntax checks for administering the alternate phone numbers
are very rudimental. Call Processing, however, checks the suggested
alternate phone numbers carefully before executing ARoE and rejects all
nonsensical numbers.
• Question: How often can a call be routed to an alternate destination?
– ARoE in response to OOS should be performed once only internally and

network-wide. After ARoE in response to APE, ARoE can be performed
again for OOS.
• Question: How do calling and called parties know when ARoE has been
performed?
A31003-H3170-S103-6-7620, 02/2019
– The alternate routing is not displayed to the calling or the called party.
However, a different number to that dialed is shown on the calling party’s
display. This is the alternate number.
• Question: Why are there station-specific alternate numbers and additional

source group-relevant alternate numbers?
– In principle, it should be possible to assign an individual phone number to

each station for both OOS and APE. However, this is memory-intensive.
If you can manage with a single alternate phone number for an entire
source group, then it is sufficient to administer this number for the relevant
source group using APRT instead of providing each station in the source
group with the same individual alternate phone number.
This number can be composed of a cascade of trunk access codes
followed by a station number supplement.
If both number variants are available, the station-specific alternate
number is always used first. This procedure ensures that specific stations
(VIPs) in a source group can be treated differently to the rest of the
stations in that group.
• Question: What is supplementing?
– If you administer the alternate number on a source group basis, you can
configure the number so that it contains several trunk access codes that
provide a loop to the called party AP via the public network. In this case,
the actual station number is not part of the alternate number to be
administered but is automatically added to the alternate number by Call
Processing in accordance with the specifications for supplementing.
The same procedure is applied to ARoE for CCM. In this case the CCM
code is the alternate number to be administered and the station number
is the part to be supplemented.
It is also possible to define a supplement with fewer digits than the called
party number. This is practical, for example, if the numbering scheme for
the alternate node at which the HFA IP telephones registers in the event
of an error, has a different station number length.
If the number is to be supplemented with a number shorter than that of
the station number, the corresponding section of the station number is
truncated. With ARoE to CCM, the number is truncated from the right. In
all other cases, it is truncated from the left.
• Question: Is there a means of avoiding loops in OpenScape 4000 or the

public network?
– Yes. This is performed automatically when ARoE is executed in an

OpenScape 4000/HiPath 4000 network.
A31003-H3170-S103-6-7620, 02/2019
– Yes. When ARoE is executed via the public network and the alternate
number contains a supplement which produces a valid ARoE-relevant
digit analysis result in the end node (ALTRTOOS/ ALTRTAPE).
Note: This supplementary number should only be part of the alternate
phone number if you have ensured that the digit analysis result has been
configured.
– Yes, if the gateway IP address of the alternate node was administered for
the HFA IP telephones. In this case, the system checks if the call
originated from the node to which alternate routing should be performed.
• Question: Is there anything in particular that must be observed when ARoE

is configured for analog phonemail?
– Yes. In order for the phonemail to play the correct announcement, it

requires the phone number of the unavailable station. This is only
possible by converting "ARoE to the phonemail" to "CFU to the
phonemail". To do this, the following administration tasks must be
performed: ADD-ZIEL: TYPE = EVMTAB, SZTYPE = FWD, CD =
<no_phonemail>;
• Question: Is there anything in particular that must be observed when ARoE

is configured for digital phonemail?
– Yes. In order for the digital phonemail to play the correct announcement,
it requires the phone number of the unavailable station. This is only
possible by converting "ARoE to the phonemail" to "CFU to the
phonemail".
For trunks that are characterized by the COT parameter LRPM, this
conversion is performed automatically when an outgoing line is seized.
If the COT parameter LRPM is not set, the COT parameter ARCF should
be set (see next question).
• Question: Are there other scenarios in which ARoE should be converted to

CFU?
– Yes, for carriers which do not permit calls whose calling number does not
belong to the system to which the carrier is connected. In the case of
ARoE, the carriers request a redirection number. Again, this is only
possible by converting ARoE to CFU. To ensure automatic conversion
while seizing an outgoing trunk line, the COT parameter ARCF must be
set for the outgoing seized line.
• Question: Is ARoE performed for direct calls to a station in NOT_READY

mode?
– No, due to a device error or deactivation via AMO.
– Yes, in response to log off/on of HFA IP telephones and APE.
A31003-H3170-S103-6-7620, 02/2019
• Question: Is ARoE performed if a console makes a consultation call to a

station in NOT_READY mode?
– That depends on the Zand setting. (ZAND / ATND /ACEXTWFT). If this

flag is set, then yes.
• Question: Is ARoE performed if the destination Exec in an executive/

secretary configuration is in NOT_READY mode?
– That depends on the status of the RNGXFER key.

If the RNGXFER key is not pressed, then ARoE is only performed if the
secretary is also in NOT_READY mode.
If the RNGXFER key is pressed, ARoE is performed immediately.
The alternate number must be configured for this for the executive and
the executive source group.
• Question: Is ARoE performed for hotline after timeout on a station in

NOT_READY mode?
– Yes.
• Question: Is ARoE performed for a hotline call on a station in NOT_READY

mode?
– Yes.
• Question: Is ARoE performed if the destination is a hunt group member in

NOT_READY mode?
– No. In the case of hunt groups, no attempt is made to seize a member in

NOT_READY mode. ARoE is therefore not performed.
• Question: Is ARoE performed for on-hook MCC paging when the paged party
is in NOT_READY mode?
– Yes, in response to the log off/on of HFA IP telephones and APE.
• Question: Is ARoE performed if, during third-party monitoring, the third party
is in NOT_READY mode?
– Yes, in response to log off/on of HFA IP telephones and APE. In the case
of APE, the system checks that the alternate number actually contains the
destination number. If the third party is a device in another node, ARoE is
treated in the same way as for normal calls since there is no knowledge
of the existence of remote third-party monitoring network-wide.
• Question: When performing ARoE, is an ITR check performed between the

called party and the alternate destination (if this is a station)?
A31003-H3170-S103-6-7620, 02/2019
– No. This type of test is purposely not performed.
• Question: Is there any interplay between ARoE and Call Forwarding?
– YES in an AP Emergency scenario. If there is an AP Emergency between

the calling station AP and the called station AP, it is assumed that the CF
data for the destination in the calling station AP is not up to date. CF is
therefore not performed if a valid number is available for ARoE for APE.
If there are no valid numbers available for ARoE for APE, CF is performed
with the aim of reaching an alternate destination.
• Question: Is there any interplay between ARoE and Trace?
– Yes. In the diagnosis printouts, the number of the station that invoked
ARoE is recorded as with call forwarding.
• Question: Are there any special requirements for LCR?
– Yes, if the alternate number is an external number. In this case, only route
elements that do not include internal reroutes are accepted.
The caller’s LCR class-of-service is upgraded. ZAND / LCR/ LCRCOSUP
• Question: Is ARoE performed for Call Forwarding - No Reply after a

Timeout?
– No, not for general CFNR.
– Yes, for quick CFNR on a station in NOT_READY mode.
– Yes, for individual night service on a station in NOT_READY mode.
• Question: Is AR0E activated for No Answer Recall?
– No, not for normal No Answer Recall.
– Yes, for No Answer Recall on a night station.
• Question: Is ARoE performed for calls to a phantom station (without physical

connection) that is in NOT_READY mode?
– No, not for APE.

Since the deregistered station cannot be assigned a physical line, an AP
Emergency cannot be determined.
– Yes, for OOS. For example, if the station was deactivated via AMO
command.
The alternate number may be administered on a station-specific or
source-group-specific basis. Because there is no physical connection
(source group = 0), the alternate number is determined in this case using
source group = 0.
A31003-H3170-S103-6-7620, 02/2019
• Question: Is ARoE performed for Callback, if the callback destination is in

NOT_READY mode?
– No. The callback entry is retained and can be executed once

NOT_READY mode is quit.
• Question: Can the alternate numbers for OOS also be used for APE?
– Yes, if alternate numbers are not already configured for APE or are
unusable.
This does not apply to HFA IP telephones, which are set for automatic
logoff/logon in the event of an error.
• Question: Is ARoE performed in response to OOS for HFA IP telephones

with Logoff/Logon functionality, if these devices were deactivated via AMO
command?
– No, since it must be assumed that in this scenario the HFA IP telephones
are not registered to alternate nodes. This also applies if the COS for
ARoE was set using the AMO SDAT.
• Question: What type of additional diagnosis can be performed to detect

ARoE malfunctions?
– If you set flag 7 using DIAGS in CC or CP2, advisory messages with

diagnostic information are output in the case of incorrect administration or
situation-dependent unusability.
• Question: Is ARoE performed for Autoset Relocate?
– Yes, if the station is deregistered.
• Question: Who bears the costs if ARoE is performed via public trunks?
– The costs are borne by the station, for which ARoE was performed.
• Question: Which number is being paged when suffix-dialing is performed

after ARoE to CCM?
– The number that appears on the caller’s display is the number being
paged. In other words, the alternate number.
• Question: Is there any interplay between ARoE and synchronized

announcement?
– The announcement type is selected on the basis of the ITR number of the
dialed destination. In the case of call forwarding, the ITR of the first
destination dialed is the announcement type. If ARoE is performed for the
first station number dialed, the ITR for that station is used for selecting the
announcement type.
• Question: Is ARoE performed when there are no available consoles or night

stations?
A31003-H3170-S103-6-7620, 02/2019
– If, for example, an attendant intercept is to be activated in an AP that is in

AP Emergency mode and there are no physical consoles or night stations
available in the AP, it is impractical to perform source-group-specific
ARoE. If the call were to follow the alternate routing number assigned to
the source group of the last checked night station, the call would end up
at the AP where the night station is physically installed.
The solution is as follows:
Source group-independent routing is performed if an alternate routing
number is administered for source group = 0 using the AMO APRT of the
type APE. In this case, calls should generally be routed to the HHS.
With this type of administration, the loop avoidance code for OOS must
be included in the alternate routing number (ALTRTOOS).
• Question: Is ARoE performed if CCM is not available due to AP Emergency?
– If, for example, a station configured in an AP that is in AP Emergency

mode cannot reach CCM because it is configured in the HHS, ARoE is
performed if the following conditions are fulfilled:
– A source_group-based alternate routing number for the CCM

source_group is configured as an incomplete number. The value of
the extension number is irrelevant in this case as long as it is greater
than 0.
– The CCM code should not contain any special characters as these
cannot be transported via the public exchange.
Likewise, ARoE is performed if a station configured in an AP that is in AP
Emergency mode wants to respond to a paging call from the CCM in
HHS. The attendant code used here should also not contain any special
characters.
It is not possible to perform on-hook paging from an AP in AP Emergency
mode.
• Question: Is there an administration tool for assisting in creating the alternate

routing number?
– Yes. Specially-authorized devices (auth_test_equipment) can dial the

access code for ALTRTOOS or ALTRTAPE followed by the station
number.
If a valid alternate routing number is administered, it is this number that is
called. If there is no valid alternate routing number, the station is called as
normal.
This method can also be used for attendant intercept calls with the
attendant code. This applies to APE scenarios only (ALTRTAPE).
• Question: Are there other means of adjusting the ARoE GUI?
A31003-H3170-S103-6-7620, 02/2019
– Yes. There is a range of default settings that can be inversed using

customer-specific patches. These settings include:
• The administered alternate numbers for OOS can also be used for
alternate routing for APE if the alternate numbers administered for
APE cannot be used for the scenario in question (Default = TRUE).
• The administered alternate numbers for OOS may also be used for
alternate routing for APE if no alternate numbers are administered for
APE (Default = TRUE).
• ARoE is only performed if the alternate destination is in READY mode

(Default = TRUE). An alternate destination can only be accepted in
NOT READY mode if no other alternate destinations are configured.
Alternate routing is also performed if the alternate destination is a
device in NOT READY status. The advantage of this is that the call
forwarding configured for this device can be used in this case if
necessary. In addition, ARoE is possible for OOS, if the current ARoR
is an APE.
• More thorough plausibility check of the alternate number (Default =

TRUE).
• For testing/configuration purposes, it is possible to activate ARoE for

APE for calls to stations in NOT READY mode even if there is no
Access Point Emergency between the calling and destination stations
(Default = FALSE).
Calls to stations in NOT READY mode are always classed as AP
Emergency between the caller and the destination.
• Question: Is ARoE possible for SIP stations?

Yes.
A31003-H3170-S103-6-7620, 02/2019
A31003-H3170-S103-6-7620, 02/2019
analog_trunking_usa_en.fm
Analog Trunking USA
Tie Traffic Features
24 Analog Trunking USA

• First of all, tie traffic (see Section 24.1, “Tie Traffic Features”) and CO traffic
(see Section 24.2, “Central Office Features” ) is described.
• Special instructions follow regarding the DIT feature (dedicated inward

trunking), automatic camp-on, trunk group overflow with rerouting,
Connecting rela Dialtone from Central Office and the application and
specimen configuration data of USA-specific modules (TMEMUS, TMDID,
TMC16 and TMDNH).
• The ADD batches listed are to be understood as examples only and must be
adapted on a customer-specific basis when necessary.
• For use in the U.S., some system initial settings has to be done. This settings
are for the correct initialisation of country code, the differnt tones, the SIU-
setting and the dialtone receiver
German:
AENDERN-ZAND:TYP=DATENALL,LANDKZ=K;
AENDERN-ZAND:TYP=TOENE,SIU="0K",HZE="0K";
AENDERN-ZAND:TYP=SIUXPER,PEGMFV=1;
English:
CHANGE-ZAND:TYPE=ALLDATA,CNTRYCD=K;
CHANGE-ZAND:TYPE=TONES,SIU=”0K”,CP=”0K”;
CHANGE-ZAND:TYPE=SIUXPER,LEVDTMF=1;
24.1 Tie Traffic Features
24.1.1 TMEMUS
24.1.1.1 Feature Description
The TMEMUS circuit is a tie trunk circuit for incoming and outgoing traffic. The
circuits can be operated with pulse dialing or DTMF dialing. Three protocols can
be configured: Wink Start, Delay Start, Immediate. As a special-purpose
configuration, the module can also be configured for Hoot & Holler application.
24.1.1.2 Service Information
• The use of the module is intended for tie trunks USA only.
• This module uses the DS102VA device handler
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
• The TMEMUS module uses no PTIME parameters; these are fixed in the
Loadware.
• For test purposes, incoming and outgoing circuits can be connected to each
other. In this context, they must be configured for the same protocol. No
incoming circuit is required for Hoot and Holler; it is sufficient to connect a
speaker and microphone.
24.1.1.3 Block Diagram
Bothway Traffic
OpenScape 4000 PABX
Signaling Wires or
E E
CO
T M M
M
E
M
Voice Wires
U Tx Tx
S Tx Tx
Rx Rx
Rx Rx
24.1.1.4 Protocols Used
Parameter description for the various protocols.
• EMD= Delay Dial
• EMW=Wink Dial
• EMI= Immediate Start (Dial Tone Start)
• EMH= Hoot & Holler
x= Parameter mandatory ; y= Parameter optional y*= If yes, both parameters

must be set. n=forbidden
Protokoll EMD EMI EMH EMW

AMO-COP
SACK - BELQ x
SDL - WABR x x
EOD - WEND
ANS - MELD x x x x
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

AMO-COP
LSUP-LUEW n n n n
SFRM- SFOR x x
NSDL-NOWA x x
DTN - WTKB y*
DTT - WTON y*
NAAT-NAAT x x x x
DTMF-MFVW y y y y
DTM1-MFV1 y y y y
BR64-IPVH y y y y

AMO-COT
ANS - MVLT x x x x
RLC - AERF y y y y
NTON - KTON y y y y
NAAT - NAAT x x x x
24.1.1.5 Generation - Examples
• German
a) Wink Start Protocol (EMW):

EINRICHTEN-BCSU:PER,1,2,109,Q2469-X ,,;
EINRICHTEN-WABE:RNR=523,KZP=QUER,PRUEF=NEIN;
EINRICHTEN-BUEND:BUNUM=223,NAME="TMEMUS-EMW
",ANZ=4,RESERV=N,ANZFANG=0,ANZACD=*,PRIONUM=1,TDDRFLAG=ON,
GDTRRGL=0,ACDPMGRP=0;
EINRICHTEN-
COP:COPNU=223,COPPAR=IPVH&RALA&MELD&NAAT&UWZ1&WABR&SFOR&ZW
Z1; /* Für Impulswahl */
EINRICHTEN-
COP:COPNU=223,COPPAR=MFVW&MFV1&RALA&NAAT&WABR&SFOR&PVW1 /*
FürMFV-Wahl*
EINR-COT:COTNU=:223,COTPAR=AERF&KTON&MVLT&NAAT&STUE,,QS-
EMW;
EINRICHTEN-COSSU:NEWCOS=220,ESBER=FBKW&QVKW&GEZ;
EINRICHTEN-TACSU:LAGE=1-1-97-
0,COTNR=223,COPNR=223,WABE=0,VBZ=0,COS=220,LCOSS=1,LCOSD=1
,BUNR=223,COFIDX=0,SATZNR="TMEMUS-EMW
",ZLNR=0,ALARMNR=2,CARRIER=1,ZONE=LEER,LIN=0,CIDDGTS=KEINE
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
,CBMATTR=KEINE,SRCGRP=1,CLASSMRK=EC&G711,TCCID="
",DITIDX=0,TRTBL=GDTR,RULEIDX=0,ATNTYP=COLOW,INBETR=J,GERT
YP=QS,GER=EMW ;
EINRICHTEN-
RICHT:ART=LRTGNEU,LRTG=223,LDIENST=SPR,NAME="EMW
",BUNUM=223,ZKNNR=1-1-
500,REROUT=NEIN,ROUTATT=NEIN,EMCYRTT=NEIN,PZKNNR=1-1-0;
EINRICHTEN-LODR:LWR=2,LWREL=ECHOFELD,FELD=2;
EINRICHTEN-
LDAT:LRTG=223,LDIENST=SPR,LWERT=1,BUNUM=223,LWR=2,LBER=1,C
ARRIER=1,ZONE=LEER,LATTR=KEINE,
b) Delay Dial Protocol (EMD):
EINRICHTEN-BUEND:BUNUM=223,NAME="TMEMUS-EMD
EINRICHTEN-
COP:COPNU=223,COPPAR=IPVH&RALA&MELD&NAAT&UWZ1&WABR&BELQ&SF
OR&ZWZ1;/* Für Impulswahl */
EINRICHTEN-
COP:COPNU=223,COPPAR=MFVW&MFV1&RALA&NAAT&WABR&BELQ&SFOR&PV
W1/* FürMFV-Wahl*
EMD;
,BUNR=223,COFIDX=0,SATZNR="TMEMUS-EMD
YP=QS,GER=EMD ;
EINRICHTEN-
EINRICHTEN-
c) Immediate Start Protocol (EMI):
EINRICHTEN-BUEND:BUNUM=223,NAME="TMEMUS-EMI
EINRICHTEN-
COP:COPNU=223,COPPAR=IPVH&RALA&MELD&NAAT&NOWA&UWZ1&ZWZ1;/*
Für Impulswahl */
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
EINRICHTEN-
COP:COPNU=223,COPPAR=MFVW&MFV1&RALA&NAAT&NOWA&PVW1/* Für
MFV-Wahl*
EMI;
,BUNR=223,COFIDX=0,SATZNR="TMEMUS-EMI
YP=QS,GER=EMI ;
EINRICHTEN-
EINRICHTEN-
d) Hoot & Holler Protocol (EMH):
EINRICHTEN-BUEND:BUNUM=223,NAME="TMEMUS-EMH
EINRICHTEN-
COP:COPNU=223,COPPAR=IPVH&RALA&MELD&NAAT&UWZ1&NOWA&ZWZ1;/*
Für Impulswahl */
EINRICHTEN-
COP:COPNU=223,COPPAR=MFVW&MFV1&RALA&NAAT&NOWA&PVW1/* Für
MFV-Wahl*
EMI;
,BUNR=223,COFIDX=0,SATZNR="TMEMUS-
EMH",ZLNR=0,ALARMNR=2,CARRIER=1,ZONE=LEER,LIN=0,CIDDGTS=KE
INE,CBMATTR=KEINE,SRCGRP=1,CLASSMRK=EC&G711,TCCID="
YP=QS,GER=EMH ;
EINRICHTEN-
EINRICHTEN-
ARRIER=1,ZONE=LEER,LATTR=KEINE;
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
• English
a) Wink Start Protocol (EMW):

ADD-BCSU:MTYPE=PER,LTG=1,LTU=2,SLOT=109,PARTNO="Q2469-X
",FCTID=0,LWVAR="K",HWYBDL=A;
ADD-WABE:CD=542,DAR=TIE,CHECK=N;
ADD-BUEND:TGRP=242,NAME="TMUS-WINK
",NO=4,RSV=N,TRACENO=0,ACDTHRH=*,PRIONO=2,TDDRFLAG=ON,GDTR
RULE=0,ACDPMGRP=0;
ADD-
COP:COPNO=242,PAR=SDL&ANS&SFRM&RLSA&BR64&NAAT&TIM1&IDP1,TR
K=TA,TOLL=TA; /*For DP dialing*/
CHANGE-COP:COPNO=242,COPTYPE=COPADD,DEV=INDEP,INFO="QS-
EMW-DP";
ADD-
COP:COPNO=242,PAR=SDL&ANS&SFRM&RLSA&DTMF&DTM1NAAT&TIM1&PDP
1,TRK=TA,TOLL=TA; /*For DTMF dialing*/
EMW-DTMF";
ADD-COT:COTNO=242,PAR=RCL&ANS&IEVT&NAAT&NTON;
CHANGE-COT:COTNO=242,COTTYPE=COTADD,DEV=INDEP,INFO="QS-
EMW-IWV";
ADD-COSSU:NEWCOS=220,AVCE=TA&TNOTCR&CDRC;
ADD-TACSU:PEN=1-2-109-
1,COTNO=242,COPNO=242,DPLN=0,ITR=0,COS=220,LCOSV=1,LCOSD=1
,TGRP=243,COFIDX=0CCT="QS-EMW
",DESTNO=0,ALARMNO=0,CARRIER=1,ZONE=EMPTY,LIN=0,CIDDGTS=NO
NE,CBMATTR=NONE,SRCGRP=1,CLASSMRK=EC&G711,TCCID="
",DITIDX=0,TRTBL=GDTR,RULEIDX=0,ATNTYP=TIE,INS=Y,DEVTYPE=T
T,DEV=EMW;
ADD-RICHT:LRTENEW,242,VCE,"TMEMUS WINK ", 242,1-1-
500,,NO, ,,"",,,,,,NO, ,NO,"",1-1-0;
ADD-LODR:ODR=2,CMD=ECHO,FIELD=2;
ADD-LODR:ODR=2,CMD=END;
ADD-LODR:ODR=2,INFO="TMEMUS";
ADD-
LDAT:LROUTE=242,LSVC=VCE,LVAL=1,TGRP=242,ODR=2,LAUTH=1,CAR
RIER=1,ZONE=EMPTY,LATTR=NONE,DNNO=5,VCCYC=4;
ADD-LDPLN:LDP="542"-"X",LROUTE=242,LAUTH=1,SPC=22,PINDP=N;
b) Delay Dial Protocol (EMD):
RULE=0,ACDPMGRP=0;
ADD-
COP:COPNO=242,PAR=SACK&SDL&ANS&SFORL&RLSA&BR64&NAAT&TIM1&I
DP1,TRK=TA,TOLL=TA; /*For DP dialing*/
EMD-DP";
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
ADD-
COP:COPNO=242,PAR=SACK&SDL&ANS&SFOR&RLSA&DTMF&DTM1NAAT&TIM
1&PDP1,TRK=TA,TOLL=TA; /*For DTMF dialing*/
EMD-DTMF";
EMD";
,TGRP=243,COFIDX=0,CCT="QS-EMW
T,DEV=EMD;
ADD-RICHT:LRTENEW,242,VCE,"TMEMUS WINK ", 242,1-1-
500,,NO, ,,"",,,,,,NO, ,NO,"",1-1-0;
ADD-
c) Immediate Start Protocol (EMI):
RULE=0,ACDPMGRP=0;
ADD-
COP:COPNO=242,PAR=ANS&RLSA&BR64&NAAT&NSDL&TIM1&IDP1,TRK=TA
,TOLL=TA; /*For DP dialing*/
EMI-DP";
ADD-
COP:COPNO=242,PAR=ANS&RLSA&DTMF&DTM1&NSDL&NAAT&TIM1&PDP1,T
RK=TA,TOLL=TA; /*For DTMF dialing*/
EMI-DTMF";
EMI";
,TGRP=243,COFIDX=0,CCT="QS-EMI
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
T,DEV=EMI;
ADD-RICHT:LRTENEW,242,VCE,"TMEMUS IM ", 242,1-1-500,,NO,
,,"",,,,,,NO, ,NO,"",1-1-0;
ADD-
d) Hoot & Holler Protocol (EMH):
ADD-BUEND:TGRP=242,NAME="TMUS-HOOT
RULE=0,ACDPMGRP=0;
ADD-
COP:COPNO=242,PAR=SACK&SDL&ANS&SFRM&RLSA&BR64&NAAT&TIM1&ID
P1,TRK=TA,TOLL=TA; /*For DP dialing*/
EMH-DP";
ADD-
COP:COPNO=242,PAR=SACK&SDL&ANS&SFRM&RLSA&DTMF&DTM1NAAT&TIM
1&PDP1,TRK=TA,TOLL=TA; /*For DTMF dialing*/
EMH-DTMF";
EMH";
,TGRP=243,COFIDX=0,CCT="QS-EMH
T,DEV=EMH;
ADD-RICHT:LRTENEW,242,VCE,"TMEMUS HOOT ", 242,1-1-500,,NO,
,,"",,,,,,NO, ,NO,"",1-1-0;
ADD-
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
24.1.1.6 Relevant AMOs
x = System-specific, w = optional, need not be entered

Language
BCSU TYP PER
LTG <x>
LTU <x>
EBT <X>
SACHNR Q2469-x
FCTID <w>
LWVAR <w>
SATZANZ <x>
AKTFC <w>
STERM <w>
LTERM <w>
PTERMO <w>
HWYBDL <w>
BCSU MTYPE PER
LTG <x>
LTU <x>
SLOT <x>
PARTNO Q2469-x
FCTID <w>
LWVAR <w>
CIRCNT% <w>
AKTFC <w>
STERM <w>
LTERM <w>
PTERMO <w>
HWYBDL <w>
WABE RNR <x>
WABE <w>
VKS <w>
KZP QUER ->Kennzahlpunkt-QUER (nur für gehend
PRUEF <w> relevant)
RIW <w>
RN2 <w>
VS2 <w>
RI2 <w>
ZLNR <w>
ARN <w>
CFREMVAR <w>
CFREMSE <w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
WABE CD <x>
DPLN <w>
CPS <w>
DAR TIE
CHECK <w>
CDDP <w>
CD2 <w>
CPS2 <w>
CDDP2 <w>
DESTNO <w>
ARN <w>
CFREMVAR <w>
CFREMSE <w>
COT COTNU <w> Standartwerte werden angegeben, es
COTPAR MVLT sind aber Kundenindividuelle Werte
AERF wenn nötig einzusetzen.
STUE AERF: Ist zu setzen wenn
KTON UNPLAUSIBLE_EVENT registriert
NAAT werden sollen
GER <w> KTON: generell für US-Trunks zu setzen
INFO <w>
COT COTNO <w> IEVT: Is only to set if
PAR ANS UNPLAUSIBLE_EVENT errors should
RCL be registried
IEVT NTON: set for all US-Trunks genrally
NTON
NAAT
DEV <w>
INFO <w>
COP COPNU <w> Die COP-Parameter sind für das
COPPAR MFVW gewünschte Protokoll einzustellen
MFV1 (siehe Section 24.1.1.4, “Protocols
BELQ Used”, on page 190), es sind nur
WEND Standartwerte angegeben,
WABR Kundenindividuelle Werte sind wenn
LUEW nötig zusätzlich zu setzen
IPVH MFVW: MFV-Wahl
NAAT MFV1: MFV-Wahl
WTON IPVH: Impulswahl
WTKB WTON:Der Parameter ist beim EMI
SFOR Protocol mit Warten auf Wählton zu
RALA setzen
MELD WTBK: Der Parameter ist beim EMI
ZWZ1 Protocol mit Warten auf Wählton zu
UWZ1 setzen
PVW1
BERAMT <w>
BERFERN <w>
GER <w>
INFO >w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
COP For COP-Parameters see Protocoll
description Section 24.1.1.4, “Protocols
COPNO <w> Used”, on page 190,
PAR DTMF only Standartvalues are described,
DTM1 Customerindividuek Values are to set if
SACK necessary
EOD DTMF: ForDTMF Dial
SDL DTM1: For DTMF Dialing
LSUP BR64: For PulseDialing
BR64 DTT: Set this Parameter if waiting for
NAAT Dial-tone is necessary
DTT DTN: Set this Parameter if waiting for
DTN Dial-tone is necessary
SFRM
RLSA
ANS
IDP1
TIM1
PDP1
TRK <w>
TOLL <w>
DEV <w>
INFO <w>
COSSU COPYCOS <w> ESBER: Kundenindividuelle Parameter
NEWCOS <w> sind zu setzen
ESBER <x>
COSSU COPYCOS <w> AVCE: Paramters to set as Customer
NEWCOS <w> requirements
AVCE <x>
BUEND BUNUM <w> ANZ: maximale Zahl zuzuordnender
NAME <w> Sätze
ANZ <w>
RESERV <w>
ANZFANG <w>
ANZACD <w>
PRIONUM <w>
TDDRFLAG <w>
GDTRRGL <w>
ACDPMGRP <w>
BUEND TGRP <w> only for outgoing Trunks necessary
NAME <w> NO: maximum number of trunks
NO <w>
RSV <w>
TRACENO <w>
ACDTHRH <w>
PRIONO <w>
TDDRFLAG <w>
GDTRULE <w>
ACDPMGRD <w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU LAGE <x> DITIDX : nur zu setzen mit COP-
ANZ <x> Parameter DIT und wenn AMO-HOTLN
COTNR <x> eingerichtet
COPNR <x> GER: Das Gerät ist für das
WABE <w> entsprechende Protokoll einzustellen
VBZ <w> (EMW,EMD,EMI oder EMH)
COS <x> ZIVOQ1: Ziffernvoreinstellung nur
LCOSS <x> zusammen mit COP-Parameter DITR
LCOSD <x> und ohne DIT zu setzen
ENACHT <w>
BUNR <x>
COFIDX <w>
SATZNR <w>
ZLNR <w>
KNNR <w>
ALARMNR <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMARK <w>
TCCID <w>
DITIDX <w>
UMWTAB <w>
REGELIDX <w<>
TREFTYP <w>
INBETR <w>
GERTYP QS
GER <x>
ZIVOQ1 <W>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU PEN <x> DITIDX: Only set a Value =/ 0 if COT-
NO <x> Parameter DIT is set
COTNO <x> DEV: The Board is to generate for the
COPNO <x> corresponding Dev-Type
DPLN <w> (EMW,EMD,EMI or EMH)
ITR <w>
COS <x>
LCOSV <x>
LCOSD <x>
INIGHT <w>
TGRP <x>
COFIDX <w>
CCT <w>
DESTNO <w>
NNO <w>
ALARMNO <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMRK <w>
TCCID <w>
DITIDX <w>
TRTBL <w>
RULEIDX <w<>
ATNTYP <w>
INS <w>
DEVICETYP TT
DEV <x>
DIGITPTR1 <w>
DTIM1 ARTDH=QV Standart Werte werden verwendet
AUSLZ1 <w>
AUSLZ2 <w>
FERNSPQ <w>
MFERNS <w>
BELUEW <w>
PAUWAHL <w>
BTBUEGEG <w>
FREIGAB1 <w>
FREIGAB2 <w>
FREIGAB3 <w>
FREIGAB4 <w>
FREIGAB5 <w>
BELVER <w>
EMPFUEW <w>
PRUEF1 <w>
PRUEF2 <w>
GLTAPR1 <w>
GLTAPR2 <w>
GLTAPR3 <w>
RESTRTNA <w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
DTIM1 TYPEDH=TIE Default values will be used
RLSC1 <w>
RLSC2 <w>
BTSUPV <w>
REMBLKAC <w>
SZUPV <w>
PAUDIAL <w>
RESET1 <w>
RESET2 <w>
RESET3 <w>
RESET4 <w>
RESET5 <w>
SZAT <w>
RLSSUPV <w>
TEST1 <w>
TEST2 <w>
CTLSTST1 <w>
CTLSTST2 <w>
CTLSTST3 <w>
RESTRTNA <w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
DTIM2 ARTDH=SATZALL WABUEBZ1 Standart Werte werden verwendet
G WABUEBZ2
WABUEBZ3
WABUEBZ4
PAUVWA1
PAUVWA2
PAUVWA3
PAUVWA4
ZWWAHLZ1
ZWWAHLZ2
ZWWAHLZ3
ZWWAHLZ4
DTRANFO
WEUEBZ
WE1A
WBSFS
WAHLAUFN
DELTIM1
DELTIM2
REQTIM1
REQTIM”
ARTDH=ALLG TONZEIT
WTONZT1
BTONZT1
QTONZT1
WAHLPAUZ
NACHWALZ,
UEBERNAZ
CEANFOR
EFREITON
EANKLTON
, EHILTON1>
, EHILTON2
BTN1
BTN2
BTN3
STAFFELW
BTONFANG
NUTON
OHDELAY1
PAUSDIAL
CMPOBEEP
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
DTIM2 TYPEDH=LNGEN, STADIAL1 Standart Values are used
STADIAL2
STADIAL3
STADIAL4
PDLY1
PDLY2
PDLY3
PDLY4
IDGT1
IDGT2
IDGT3
IDGT4
DTRFIND
EOD
EOD1A
RESZBLK
DIALSTA
DELTIM1
DELTIM2
REQTIM1
REQTIM2
DTNT1
TYPEDH=GEN ANATN
BSYON
ACKTN1
DIALPAUT
POSTDIAL
FLSHSUPV
CRFIND
FRNGBK
FCO
FAUXTN1
FAUXTN2
BSGNL1
BSGNL2
BSGNL3,
CUTTHRUD
BSIGCONN
NUTONE
OHDELAY1
PAUSDIAL
CMPOBEEP
CTIME ARTSWU=TTIME PREEMT Standart Werte werden verwendet
NOANSCON
NOCALLTR
TRANSTOA
REPSEIZ
REPSZEND
PRREQI
PRREQC
NEUVERB
AUSJOIN
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
CTIME TYPESWU=TRK PREEMT Standart Values are used
NOANSCON
NOCALLTR
ATNDTRNS
RPTSZ
RPTSZEND
PRREQI
PRREQC
NEWCONN
RELJOIN
RICHT ART LRTGNEU nur für gehende Belegung relevant
LRTG <x> MFVUMS: für MFV-Nachwahl zu setzen
LDIENST <w> (FIX wenn keine spezielle Kennzahl
NAME <w> gewählt werden muss)
BUNUM <x>
ZKNNR <w>
ROUTOPT <w>
REROUT <w>
MFVUMS <w>
MFVANZ <w>
MFVTEXT <w>
MFVPULS <w>
VLVER <w>
UMLVER <w>
ZLNR <w>
PIN <w>
ROUTATT <w>
EMCYRTT <w>
INFO <w>
PZKNNR <w>
RICHT MODE LRTENEW only for outgoing Trunks necessary
LRTE <x> DTMFCNV: is to set for DTMF
LSVC <w> Postdialing (FIX to send all digits to the
NAME <w> line)
TGRP <x>
DNNO <w>
ROUTOPT <w>
REROUT <w>
DTMFCNV <w>
DTMFDISP <w>
DTMFTEXT <w>
DTMFPULS <w>
PLB <w>
FWDBL <w>
DESTNO <w>
PIN <w>
ROUTATT <w>
EMCYRTT <w>
INFO <w>
PDNNO; <w>
LODR nur für gehende belegung relevant,
siehe LCR-Einrichtungen
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
LODR only for outgoing Trunks necessary, see
LCR administration
LDAT nur für gehende belegung relevant,
LDAT only for outgoing Trunks necessary, see
LCR administration
LDPLN nur für gehende belegung relevant,
LDPLN only for outgoing Trunks necessary, see
LCR administration
24.1.2 TMDNH - T1BOS for TIE Lines
The TMDNH (T1BOS) module is used as a digital tie trunk circuit for incoming and
outgoing traffic. The circuits can be operated with pulse dialing or DTMF dialing.
Four protocols can be configured: Wink Start, Delay Start, Immediate Start and
PLAR.
• The module is intended for use in the USA only.
• When using the TMDNH (T1BOS) for tie trunks, the DS102VA device handler
is used.
• Protocols used
Parameter description for the various protocols.
• T1EMD= Delay Dial
• T1EMW=Wink Dial
• T1EMI= Immediate Start
• T1PLAR= PLAR
x= Parameter mandatory ; y= Parameter optional, n=forbidden
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
Protokoll T1EMD T1EMI T1EMW T1PLAR

AMO-COP
SACK - BELQ x
SDL - WABR x x
EOD - WEND
ANS - MELD x x x x
LSUP-LUEW n n n n
SFRM- SFOR x x
NSDL-NOWA x x
DTN - WTKB y y y
DTT - WTON y y y y
NAAT-NAAT x x x x
DTMF-MFVW y y y y
DTM1-MFV1 y y y y
BR64-IPVH y y y y
24.1.2.3 Generation
The generation example is given for a T1EMI with pulse dialing; for other
signaling methods (T1EMW,T1EMD,T1PLAR and DTMF signaling), the COP
parameters must be modified accordingly and the system configured correctly in
AMO TACSU.
• German
AENDERN-
LWPAR:TYP=TMD,TMDTYP=TMDBOSBLNR=1,OPMODE=BDETON&BISUB80N&FRAM
EESF&NETUSER,CABLETYP=1,OESDISTH=30,OESREQTH=4,SESDISTH=10,SE
SREQTH=10;
AENDERN-
LWPAR:TYP=TMD,TMDTYP=TMDBOSBLNR=2,OPMODE=BDETON&BISUB80N&FRAM
EESF,CABLETYP=1,OESDISTH=30,OESREQTH=4,SESDISTH=10,SESREQTH=1
0;
EINRICHTEN-BCSU:TYP=TMD,LTG=1,LTU=1,EBT=97,SACHNR="Q2192-X
",FCTID=1,LWVAR="K",LWPAR=2,HWYBDL=A;
EINRICHTEN-BCSU:TYP=TMD,LTG=1,LTU=2,EBT=109,SACHNR="Q2192-X
EINRICHTEN-BUEND:BUNUM=242,NAME="T1EMI
",ANZ=2,RESERV=N,ANZFANG=0,ANZACD=*,PRIONUM=2,TDDRFLAG=ON,GDT
RRGL=0,ACDPMGRP=0;
EINRICHTEN-
COP:COPNU=242,COPPAR=MELD&RALA&IPVH&NAAT&UWZ1&NOWA&ZWZ1,BERAM
T=FBKW,BERFERN=FBKW;
AENDERN-COP:COPNU=242,COPART=COPZU,GER=UNAB,INFO="T1-EMI";
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
EINRICHTEN-COT:COTNU=242,COTPAR=AERF&MVLT&STUE&NAAT&KTON;
AENDERN-COT:COTNU=242,COTART=COTZU,GER=UNAB,INFO="T1-EMI";
1,COTNR=242,COPNR=242,WABE=0,VBZ=0,COS=220,LCOSS=1,LCOSD=1,BU
NR=243,COFIDX=0,SATZNR="QSGUS-IM
",ZLNR=0,ALARMNR=0,CARRIER=1,ZONE=LEER,LIN=0,CIDDGTS=KEINE,CB
MATTR=KEINE,SRCGRP=1,CLASSMRK=EC&G711,TCCID="
",DITIDX=0,TRTBL=GDTR,RULEIDX=0,ATNTYP=TIE,INBETR=J,GERTYP=QS
,GER=T1EMI;
NR=242,COFIDX=0,SATZNR="QSGUS-IM
",DITIDX=0,TRTBL=GDTR,RULEIDX=0,ATNTYP=TIE,INBETR=J,GERTYP=QS
,GER=T1EMI;
EINRICHTEN-REFTA:TYP=SATZ,LAGE=1-1-97-
0,PRIO=0,SPERRE=N,READYASY=N;
EINRICHTEN-REFTA:TYP=SATZ,LAGE=1-2-109-
0,PRIO=0,SPERRE=N,READYASY=N;
EINRICHTEN-RICHT:ART=LRTGNEU,LRTG=242,LDIENST=SPR,NAME="T1EMI
EINRICHTEN-
LDAT:LRTG=242,LDIENST=SPR,LWERT=1,BUNUM=242,LWR=2,LBER=1,CARR
IER=1,ZONE=LEER,LATTR=KEINE,ZKNNR=5,VCCYK=4;
EINRICHTEN-LODR:LWR=2,LWREL=ECHOFELD,FELD=2;
EINRICHTEN-LODR:LWR=2,LWREL=ENDE;
EINRICHTEN-LODR:LWR=2,INFO="QUER A3 OFFEN";
EINRICHTEN-LDPLN:LWM="543"-
"X",LRTG=242,LBER=1,IPS=22,PINDP=NEIN;
• English
CHANGE-
LWPAR:TYPE=TMD,TMDTYPE=TMDBOS,BLNO=1,OPMODE==BDETON&BISUB80N&
FRAMEESF&NETUSER,CABLETYP=1,OESDISTH=30,OESREQTH=4,SESDISTH=1
0,SESREQTH=10;
CHANGE-
LWPAR:TYPE=TMD,TMDTYPE=TMDBOS,BLNO=2,OPMODE=BDETON&BISUB80N&F
RAMEESF,CABLETYP=1,OESDISTH=30,OESREQTH=4,SESDISTH=10,SESREQT
H=10;
ADD-BCSU:MTYPE=TMD,LTG=1,LTU=1,SLOT=97,PARTNO="Q2192-X
ADD-BUEND:TGRP=242,NAME="T1EMI
",NO=2,RSV=N,TRACENO=0,ACDTHRH=*,PRIONO=2,TDDRFLAG=ON,GDTRRUL
E=0,ACDPMGRP=0;
ADD-
COP:COPNO=242,PAR=ANS&RLSA&BR64&NAAT&TIM1&NSDL&IDP1,TRK=TA,TO
LL=TA;
CHANGE-COP:COPNO=242,COPTYPE=COPADD,DEV=INDEP,INFO="T1-EMI";
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
CHANGE-COT:COTNO=242,COTTYPE=COTADD,DEV=INDEP,INFO="T1-EMI";
1,COTNO=242,COPNO=242,DPLN=0,ITR=0,COS=220,LCOSV=1,LCOSD=1,TG
RP=243,COFIDX=0,CCT="QSGUS-IM
",DESTNO=0,ALARMNO=0,CARRIER=1,ZONE=EMPTY,LIN=0,CIDDGTS=NONE,
CBMATTR=NONE,SRCGRP=1,CLASSMRK=EC&G711,TCCID="
",DITIDX=0,TRTBL=GDTR,RULEIDX=0,ATNTYP=TIE,INS=Y,DEVTYPE=TT,D
EV=T1EMI;
RP=242,COFIDX=0,CCT="QSGUS-IM
",DITIDX=0,TRTBL=GDTR,RULEIDX=0,ATNTYP=TIE,INS=Y,DEVTYPE=TT,D
EV=T1EMI;
ADD-REFTA:TYPE=CIRCUIT,PEN=1-1-97-0,PRI=0,BLOCK=N,READYASY=N;
ADD-REFTA:TYPE=CIRCUIT,PEN=1-2-109-
0,PRI=0,BLOCK=N,READYASY=N;
ADD-RICHT:LRTENEW,242,VCE,"T1EMI ", 242,1-1-
500,,NO, ,,"",,,,,,NO,,NO,"",1-1-0;
ADD-
LDAT:LROUTE=242,LSVC=VCE,LVAL=1,TGRP=242,ODR=2,LAUTH=1,CARRIE
R=1,ZONE=EMPTY,LATTR=NONE,DNNO=5,VCCYC=4;
ADD-LODR:ODR=2,INFO="QUER A3 OFFEN";

Language
LWPAR TYP TMD ->BLNR: Blocknummer frei zu vergeben
TMDTYP TMDBOS später im BCSU einzutragen
BLNR <x> -> NETUSER: Für einen Trunk ist NETUSER
OPMODE BDETON zu setzen für die gegenseite nicht
BISUB8ON
FRAMEESF
NETUSER
CABLETYP 1
OESDISTH 30
OESREQTH 4
SESDISTH 10
SESREQTH 10
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
LWPAR TYPE TMD BLNO: Block-Number free later fill in in BCSU
TMDTYPE TMDBOS NETUSER: To set for one Trunk , not to set
BLNO <x> for partner Trunk
OPMODE BDETON
BISUB8ON
FRAMEESF
NETUSER
CABLETYP 1
OESDISTH 30
OESREQTH 4
SESDISTH 10
SESREQTH 10
BCSU TYP TMD FCTID=1: Für BOS Anwendung
LTG <x> LWPAR: Es ist die unter LWAR angegebene
LTU <x> BLNR anzugeben
EBT <x>
SACHNR Q2192-x
FCTID 1
LWVAR
LWPAR <x>
AKTFC
STERM
LTERM
PTERM
HWYBDL
BCSU MTYPE TMD FCTID=1: For BOS
LTG <x> LWPAR: Set the Blocknumer (BLNO)
LTU <x> definedwith LWPAR
SLOT <x>
PARTNO Q2192-x
FCTID 1
LWVAR
LWPAR <x>
ACTFC
STERM
LTERM
PTERM
HWYBDL
WABE KZP QUER Kennzahlpunkt-QUER (nur für gehend
relevant)
WABE DAR TIE Digit Anylis result=TIE (only necessary for
outgoing )
COT COTPAR MVLT ->STUE: Ist zu setzen wenn
AERF UNPLAUSIBLE_EVENT registriert werden
STUE sollen
KTON NAAT: für alle US-Trunks genrell zu setzen
NAAT
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
COT PAR ANS IEVT: Is only to set if UNPLAUSIBLE_EVENT
RCL errors should be registried
IEVT NAAT: to set generally for all US-trunks
NTON
NAAT
COP COPPAR MFVW Die COP-Parameter sind für das gewünschte
MFV1 Protocol einzustellen siehe Section 24.1.1.2,
BELQ “Service Information”, on page 189
WEND
WABR
LUEW
IPVH
NAAT
SFOR
RALA
MELD
ZWZ1
UWZ1
PVW1
COP PAR DTMF For COP-Parameters see Protocoll
DTM1 description Section 24.1.1.2, “Service
SACK Information”, on page 189
EOD
SDL
LSUP
BR64
NAAT
SFRM
RLSA
ANS
IDP1
TIM1
PDP1
COSSU COPYCOS <w> ESBER: Kundenindividuelle Parameter sind
NEWCOS <w> zu setzen
ESBER <x>
AVCE <x>
BUEND BUNUM <w> ANZ: maximale Zahl zuzuordnender Sätze
NAME <w>
ANZ <w>
RESERV <w>
ANZFANG <w>
ANZACD <w>
PRIONUM <w>
TDDRFLAG <w>
GDTRRGL <w>
ACDPMGRP <w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
NAME <w>
NO <w>
RSV <w>
TRACENO <w>
ACDTHRH <w>
PRIONO <w>
TDDRFLAG <w>
GDTRULE <w>
ACDPMGRD <w>
TACSU LAGE <x> DITIDX: nur zu setzen mit COP-Parameter
ANZ <x> DIT und wenn AMO-HOTLN eingerichtet
COTNR <x> GER: Das Gerät ist für das entsprechende
COPNR <x> Prot.einzustellen (T1EMW,T1EMD,T1EMI
WABE <w> oderT1PLAR)
VBZ <w> ZIVOQ1: Ziffernvoreinstellung nur zusammen
COS <x> mit COP-Parameter DITR und ohne DIT zu
LCOSS <x> setzen
LCOSD <x>
ENACHT <w>
BUNR <x>
COFIDX <w>
SATZNR <w>
ZLNR <w>
KNNR <w>
ALARMNR <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMARK <w>
TCCID <w>
DITIDX <w>
UMWTAB <w>
REGELIDX <w<>
TREFTYP <w>
INBETR <w>
GERTYP QS
GER <x>
ZIVOQ1 <W>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU PEN <x> DITIDX: Only set a Value =/ 0 if COT-
NO <x> Parameter DIT is set
COTNO <x> DEV: The Board is to generate for the
COPNO <x> corresponding Dev-Type
DPLN <w> (T1EMW,T1EMD,T1EMI or T1PLAR)
ITR <w>
COS <x>
LCOSV <x>
LCOSD <x>
INIGHT <w>
TGRP <x>
COFIDX <w>
CCT <w>
DESTNO <w>
NNO <w>
ALARMNO <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMRK <w>
TCCID <w>
DITIDX <w>
TRTBL <w>
RULEIDX <w<>
ATNTYP <w>
INS <w>
DEVICETYP TT
DEV <x>
DIGITPTR1 <w>
REFTA TYP SATZ LAGE: Es is tLine Nr. 0 anzugebent
LAGE <x>
PRI <x>
SPERRE <x>
READYASY <x>
REFTA TYPE CIRCUIT PEN: Give Line Nt. 0
PEN <x>
PRIO <x>
BLOCK <x>
READYASY <x>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
LDIENST <w>
NAME <w>
BUNUM <x>
ZKNNR <w>
ROUTOPT <w>
REROUT <w>
MFVUMS <w>
MFVANZ <w>
MFVTEXT <w>
MFVPULS <w>
VLVER <w>
UMLVER <w>
ZLNR <w>
PIN <w>
ROUTATT <w>
EMCYRTT <w>
INFO <w>
PZKNNR <w>
RICHT MODE LRTENEW only for outgoing trunks necessary
LRTE <x> DTMFCNV: is to set for DTMF Postdialing
LSVC <w>
NAME <w>
TGRP <x>
DNNO <w>
ROUTOPT <w>
REROUT <w>
DTMFCNV <w>
DTMFDISP <w>
DTMFTEXT <w>
DTMFPULS <w>
PLB <w>
FWDBL <w>
DESTNO <w>
PIN <w>
ROUTATT <w>
EMCYRTT <w>
INFO <w>
PDNNO; <w>
LODR nur für gehende Belegung relevant, siehe
LCR Administration
LODR only fpr outgoing Trunks necessary, see LCR
administration
LDAT nur für gehende Belegung relevant,siehe LCR
Administration
LDAT only fpr outgoing Trunks necessary,see LCR
administration
LDPLN nur für gehende Belegung relevant,siehe LCR
Administration
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
Central Office Features

Language
LDPLN only fpr outgoing Trunks necessary, see LCR
administration
24.2 Central Office Features
24.2.1 TMC16
The TMC16 is used for incoming (PSS call for switching) and outgoing (MSI) CO
traffic. The module can be operated with Loop Start or Ground Start. Both pulse
dialing or DTMF dialing is possible.
24.2.1.2 User Interface
An incoming CO call is signaled as an initial call during switching. In the case of

an outgoing connection, the circuit is seized after selection of an Access-Code
and the CO connection can be established. If it has been parameterized, you
must wait for a tone from the CO.
• The module is intended for use in the USA only. Configuration for Ground
Start or Loop Start is based on the type of CO connected and also on whether
the connected CO is operated with pulse dialing or DTMF dialing.
• If a call process tone from the CO is to be waited for in the case of an outgoing
seizure, the COP parameter SDL must be set (a dial tone receiver is then
switched in the outgoing circuit and the tone received from the CO is
analyzed).
• If the CO does not transmit a seizure acknowledgement in the case of an

outgoing connection (if provided for in the protocol), the CYCSET
(DTIM1:CO) Timer in the OpenScape 4000 runs out first, followed by the
STADIAL2 (DTIM2:LNGEN) Timer. Once the STADIAL2 Timer has expired,
OUTGOING SEIZURE is attempted again. This sequence of timers and
attempts at outgoing seizure is repeated infinitely until positive
acknowledgement is received from the CO.
• DTMF post-dialing must be configured in AMO RICHT.
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
• In the case of an outgoing seizure, the circuits of the TMC16 must, in

principle, be configured in such a way that the last digit is not transmitted until
expiry of the WE1A timer (this is necessary as no answer is transmitted by
the trunk and especially necessary in the case of Automatic Subscriber-
Stations which report immediately upon dialing and subsequently expect
DTMF post-dialing). If absolutely all digits are to be transmitted prior to expiry
of the WE1A timer, the COP parameter NO1A (Without Signaling Method 1A)
must be set in the circuit. Another possibility of completing dialing
immediately is to complete the dialing with “#” , or to administrate the AMO
LDPLN with “z” instead of “x” (the circuit is consequently not seized at all until
after the final digit has been transmitted).
• The module uses the DS101VA device handler
OpenScape 4000
Bothway Traffic
T
M
C DTMF / Pulse
CO
1
6
24.2.1.5 Generation Example
• German
a) For Loop Start:

EINRICHTEN-BCSU:TYP=PER,LTG=1,LTU=1,EBT=097,SACHNR="Q2485-
X",FCID=0,LWVAR="0";
EINRICHTEN-WABE:RNR=523,KZP=AMT,PRUEF=NEIN;
EINRICHTEN-BUEND:BUNUM=223,NAME="TMC16
EINRICHTEN-COP:COPNU=223,COPPAR=IPVH&NAAT&UWZ1&NOWA&ZWZ1;/
* Für Impulswahl */
EINRICHTEN-COP:COPNU=223,COPPAR=MFVW&MFV1&NAAT&NOWA&PVW1/*
Für MFV-Wahl*
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
EINRICHTEN-
COT:COTNU=223,COTPAR=AERF&LTVW&STUE&KGZL&NAAT&KTON;
,BUNR=223,COFIDX=0,SATZNR="TMC16
YP=AS,GER=LPSTR,MFCVAR=0,ANZUNT=0,ANZZIFF=0,PRUEFNR=1,CIRC
IDX=2,GEB=1,SATZINFO=0,WAHLART=IWV-IWV,WAHLVAR=0-0,COEX=0;
EINRICHTEN-
RICHT:ART=LRTGNEU,LRTG=223,LDIENST=SPR,NAME="TMC16
EINRICHTEN-
ARRIER=1,ZONE=LEER,LATTR=KEINE,VCCYK=4;
b) For Ground Start:
EINRICHTEN-BCSU:TYP=PER,LTG=1,LTU=1,EBT=097,SACHNR="Q2485-
X",FCID=0,LWVAR="0";
EINRICHTEN-WABE:RNR=523,KZP=AMT,PRUEF=NEIN;
EINRICHTEN-COP:COPNU=223,COPPAR=IPVH&NAAT&UWZ1&NOWA&ZWZ1;/
* Für Impulswahl */
EINRICHTEN-COP:COPNU=223,COPPAR=MFVW&MFV1&NAAT&NOWA&PVW1/*
Für MFV-Wahl*
EINRICHTEN-
COT:COTNU=223,COTPAR=AERF&LTVW&STUE&KGZL&NAAT&KTON;
,BUNR=223,COFIDX=0,SATZNR="TMC16
YP=AS,GER=GRDSTR,MFCVAR=0,ANZUNT=0,ANZZIFF=0,PRUEFNR=1,CIR
CIDX=2,GEB=1,SATZINFO=0,WAHLART=IWV-IWV,WAHLVAR=0-
0,COEX=0;
EINRICHTEN-
RICHT:ART=LRTGNEU,LRTG=223,LDIENST=SPR,NAME="TMC16
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
EINRICHTEN-
ARRIER=1,ZONE=LEER,LATTR=KEINE,VCCYK=4;
• English
a) Loop Start
",FCTID=0,LWVAR="0",HWYBDL=A;
ADD-BUEND:TGRP=223,NAME="TMC16 LOOP
RULE=0,ACDPMGRP=0;
ADD-COP:COPNO=223,PAR=BR64&NAAT&TIM1&NSDL&IDP1;
ADD-COT:COTNO=223,PAR=RCL&AEOD&IEVT&ICZL&NAAT&NTON;
,TGRP=223,COFIDX=0,CCT="TMC16 LOOP
NE,CBMATTR=NONE,SRCGRP=1,CLASSMRK=EC&G711,TCCID="",DITIDX=
0,TRTBL=GDTR,RULEIDX=0,ATNTYP=COLOW,INS=Y,DEVTYPE=TC,DEV=L
PSTR,MFCVAR=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=3,CDRIN
T=1,CCTINFO=0,DIALTYPE=DIP-DIP,DIALVAR=0-0,COEX=0;
ADD-RICHT:LRTENEW,223,VCE,"TMC16 LOOP ", 223,1-1-
500,,NO, ,,"",,,,,,NO,,NO,"",1-1-0;
ADD-LODR:ODR=2,INFO="TMC16";
ADD-
RIER=1,ZONE=EMPTY,LATTR=NONE,VCCYC=4;
b) Ground Start
ADD-BUEND:TGRP=223,NAME="TMC16GROUND
RULE=0,ACDPMGRP=0;
ADD-COP:COPNO=223,PAR=BR64&NAAT&TIM1&NSDL&IDP1;
ADD-COT:COTNO=223,PAR=RCL&AEOD&IEVT&ICZL&NAAT&NTON;
,TGRP=223,COFIDX=0,CCT="TMC16 GROUND
NE,CBMATTR=NONE,SRCGRP=1,CLASSMRK=EC&G711,TCCID="",DITIDX=
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
0,TRTBL=GDTR,RULEIDX=0,ATNTYP=COLOW,INS=Y,DEVTYPE=TC,DEV=G
RDSTR,MFCVAR=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=3,CDRI
NT=1,CCTINFO=0,DIALTYPE=DIP-DIP,DIALVAR=0-0,COEX=0;
ADD-RICHT:LRTENEW,223,VCE,"TMC16 GROUND ", 223,1-1-
500,,NO, ,,"",,,,,,NO,,NO,"",1-1-0;
ADD-LODR:ODR=2,INFO="TMC16";
ADD-
RIER=1,ZONE=EMPTY,LATTR=NONE,VCCYC=4;

Language
DTIM1 ARTDH AMTSVER WBSGEH: Belegunssperre gehend nach
WBSGEH Ausloesen
WBSKOM WBSKOM: Belegungssperre kommend nach
AUFRICHT Auslösen
ZYKLAUFR ZYKLAUFR: Zeit für erneutes
PAUZWZIF Belegungsversuch zum Amt
FANGAM
WANS1
DANS1
WANS2
DANS2
DITR
PWABHKZ
DTIM1 TYPEDH CO RESZO: outgoing reseize barring after an
RESZO outgoing co call
RESZI RESZI: outgoing reseize barring after an
SETUPULS incoming co call
CYCSET CYCSET: cyclic setup of line alarms for pulse
DSUPVOP signaling systems
TRACCO
WANN1
DANN1
WANN2
DANN2
DITR
PEODMS
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
DTIM2 ARTDH SATZALLG WABUEBZ2: Prüfzeit ob AMT wieder bereit
WABUEBZ1 (nach Fehler beim Belegen des Amtes)
WABUEBZ2
WABUEBZ3
WABUEBZ4
PAUVWA1
PAUVWA2
PAUVWA3
PAUVWA4
ZWWAHLZ1
ZWWAHLZ2
ZWWAHLZ3
ZWWAHLZ4
DTRANFO
WEUEBZ
WE1A
WBSFS
WAHLAUFN
DELTIM1
DELTIM2
REQTIM1
REQTIM”
ARTDH ALLG
TONZEIT
WTONZT1
BTONZT1
QTONZT1
WAHLPAUZ
NACHWALZ
UEBERNAZ
CEANFOR
EFREITON
EANKLTON
EHILTON1
EHILTON2
BTN1
BTN2
BTN3
STAFFELW
BTONFANG
NUTON
OHDELAY1
PAUSDIAL
CMPOBEEP
BTONZT1
CEANFOR
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
DTIM2 TYPEDH, LNGEN
STADIAL1
STADIAL2
STADIAL3
STADIAL4
PDLY1
PDLY2
PDLY3
PDLY4
IDGT1
IDGT2
IDGT3
IDGT4
DTRFIND
EOD
EOD1A
RESZBLK
DIALSTA
DELTIM1
DELTIM2
REQTIM1
TYPEDH REQTIM2
GEN
DTNT1
ANATN
BSYON
ACKTN1
DIALPAU
POSTDIAL
FLSHSUPV
CRFIND
FRNGBK
FCO
FAUXTN1
FAUXTN2
BSGNL1
BSGNL2
BSGNL3
CUTTHRUD
BSIGCONN
NUTONE
OHDELAY1
PAUSDIAL
CMPOBEEP
BCSU TYP PER
LTG <x>
LTU <x>
EBT <x>
SACHNR Q2485-x
FCTID
LWVAR
HWYBDL
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
BCSU MTYPE PER
LTG <x>
LTU <x>
SLOT <x>
PARTNO Q2485-x
FCTID
LWVAR
HWYBDL
WABE KZP AMT Einrichten eines Kennzahlpunktes AMT
WABE DAR CO
COP COPPAR IPVH Für Impulswahl:
NAAT IPVH&NAAT&UWZ1&NOWA&ZWZ1
UWZ1 Für MFV-
NOWA Wahl:.MFVW&MFV1&NAAT&NOWA&PVW1
ZWZ1
MFVW
MFV1
PVW1
COP PAR DTMF DTMF: for DTMF.
DTM1 DTM1: for DTMF
NSDL BR64: for DP
BR64 PDP1: for DTMF
NAAT
IDP1
TIM1
PDP1
COT COTPAR AERF KGZL: Für Anzeige von Unplausiblen Events
LTVW NAAT: ist für US-Trunks genrell zu setzen
STUE
KGZL
KTON
NAAT
COT PAR RCL NAAT: has to be set genrally for US-trunks
AEOD
IEVT
ICZL
NTON
NAAT
COSSU COPYCOS <w> ESBER: Kundenindividuelle Parameter sind zu
NEWCOS <w> setzen
ESBER <x>
AVCE <x>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
NAME <w>
ANZ <w>
RESERV <w>
ANZFANG <w>
ANZACD <w>
PRIONUM <w>
TDDRFLAG <w>
GDTRRGL <w>
ACDPMGRP <w>
NAME <w>
NO <w>
RSV <w>
TRACENO <w>
ACDTHRH <w>
PRIONO <w>
TDDRFLAG <w>
GDTRULE <w>
ACDPMGRD <w>
PTIME Standart Werte werden verewendet
PTIME Standart values will be used
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU LAGE <x>
COTNR <x>
COPNR <x>
WABE <w>
VBZ <w>
COS <w>
LCOSS <x>
LCOSD <x>
BUNR <x>
COFIDX <x>
SATZNR <w>
ZLNR <w>
ALARMNR <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMRK <w>
TCCID <w>
DITIDX <w>
TRTBL <w>
RULEIDX <w>
ATNTYP <w>
INBETR <w>
GERTYP AS
GER LPSRT or
MFCVAR GDSTR
,ANZUNT <w>
ANZZIFF <w>
PRUEFNR <w>
CIRCIDX <w>
GEB <w>
SATZINFO <w>
WAHLART <w>
WAHLVAR IWV-IWV/
COEX= MFV-MFV
<w<>
<w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU PEN <x>
COTNO <x>
COPNO <x>
DPLN <w>
ITR <w>
COS <x>
LCOSV <x>
LCOSD <x>
TGRP <x>
COFIDX <w>
CCT <w>
DESTNO <w>
ALARMNO <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMRK <w>
TCCID <w>
DITIDX <w>
TRTBL <w>
RULEIDX <w>
ATNTYP <w>
INS <w>
DEVTYPE TC
DEV LPSTR or
MFCVAR GRDSTR
SUPPRESS <w>
,DGTCNT <w>
TESTNO <w>
CIRCIDX <w>
CDRINT <w>
CCTINFO <w>
DIALTYPE <w>
DIALVAR <w>
COEX <x>
<w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
LDIENST <w>
NAME <w>
BUNUM <x>
ZKNNR <w>
ROUTOPT <w>
REROUT <w>
MFVUMS <w>
MFVANZ <w>
MFVTEXT <w>
MFVPULS <w>
VLVER <w>
UMLVER <w>
ZLNR <w>
PIN <w>
ROUTATT <w>
EMCYRTT <w>
INFO <w>
PZKNNR <w>
LSVC <w>
NAME <w>
TGRP <x>
DNNO <w>
ROUTOPT <w>
REROUT <w>
DTMFCNV <w>
DTMFDISP <w>
DTMFTEXT <w>
DTMFPULS <w>
PLB <w>
FWDBL <w>
DESTNO <w>
PIN <w>
ROUTATT <w>
EMCYRTT <w>
INFO <w>
PDNNO; <w>
LODR nur für gehende Belegung relevant, siehe LCR
Administration
administration
LDAT nur für gehende Belegung relevant, siehe LCR
Administration
LDAT only fpr outgoing Trunks necessary, see LCR
administration
LDPLN nur für gehende Belegung relevant, siehe LCR
Administration
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
administration
24.2.2 TMDID
This circuit is used as a direct inward dialing (DiD) circuit in the USA. The
following protocols are possible: Wink Start, Delay Start or Immediate Dialing.
The module is only to be used for incoming traffic.
The type of protocol is configured by means of various COP parameters.
y = optional x= mandatory n= forbidden
Protokoll Delay Immediate Wink

AMO-COP
SACK - BELQ n n x
SDL - WABR x n x
NSDL-NOWA x
EOD - WEND x x x
NAAT-NAAT x x x
BR63-IPVH y y y
DTMF-MFVW y y y
DTM1-MFV1 y y y
LSUP-LUEW n n n
PTIME-PTIME P5=2 P5=2 P5=2
• The module uses the DS120VA,DS120VB,DS120VC device handlers
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
Direct inward dialing traffic

OpenScape 4000
T
M
D DTMF / Pulse
CO
I
D
The following protocols are envisaged:
a) Immediate Dial
b) Wink Start
c) Delay Dial

AMO-COP
SACK - BELQ n n x
SDL - WABR x n x
NSDL-NOWA x
EOD - WEND x x x
NAAT-NAAT x x x
BR63-IPVH y y y
DTMF-MFVW y y y
DTM1-MFV1 y y y
LSUP-LUEW n n n
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

AMO-COP
24.2.2.7 Configuration Example:
• German
EINR-BCSU:PER,1,1,97,Q2452-X,;
KOP-PTIME:113,2;AE-PTIME:REST,2,PARA,,,,,2;
EINRICHTEN-
COP:COPNU=223,COPPAR=IPVH&RALA&RALB&NAAT&UWZ1&WABR&BELQ&ZWZ1;
/* Für Impulswahl Prot. WINK*/
EINRICHTEN-
COP:COPNU=223,COPPAR=MFVW&MFV1&RALA&RALB&NAAT&WABR&BELQ&PVW1/
* Für MFV-Wahl Prot. WINK*
EINRICHTEN-
COP:COPNU=223,COPPAR=IPVH&RALA&RALB&NAAT&UWZ1&WABR&ZWZ1;/*
Für Impulswahl Prot. DELAY*/
EINRICHTEN-
COP:COPNU=223,COPPAR=MFVW&MFV1&RALA&RALBNAAT&WABR&PVW1/*
FürMFV-Wahl Prot. DELAY*
EINRICHTEN-
COP:COPNU=223,COPPAR=IPVH&RALA&RALB&NAAT&UWZ1&NOWA&ZWZ1;/*
Für Impulswahl Prot. IMMEDIATE*/
EINRICHTEN-
COP:COPNU=223,COPPAR=MFVW&MFV1&RALA&RALB&NAAT&NOWA&PVW1/* Für
MFV-Wahl Prot.IMMEDIATE*
EINR-COT:COTNU=223,COTPAR=AERF&KTON&STUE&NAAT;
0,COTNR=223,COPNR=223,WABE=0,VBZ=0,COS=220,LCOSS=1,LCOSD=1,CO
FIDX=0,SATZNR="TMDID
",DITIDX=0,TRTBL=GDTR,RULEIDX=0,ATNTYP=COLOW,INBETR=J,GERTYP=
AS,GER=DID,MFCVAR=0,ANZUNT=0,ANZZIFF=0,PRUEFNR=1,CIRCIDX=2,GE
B=1,SATZINFO=0,WAHLART=IWV-IWV or MFV-MFV,WAHLVAR=0-0,COEX=0;
• English
COPY-PTIME:INIBLOCK=113,TBLK=3;
CHANGE-PTIME:TYPE=REST,TBLK=3,BTYPE=PARA,P5=2;
ADD-
COP:COPNO=223,PAR=RLSB&RLSA&BR64&TIM1&NSDL&IDP1,TRK=TA,TOLL=T
A; /* DP with IMMEDIATE Prot. */
ADD-
COP:COPNO=223,PAR=RLSB&RLSA&BR64&TIM1&SACK&SDL&IDP1,TRK=TA,TO
LL=TA; /* DP with WINK Prot. */
ADD-
COP:COPNO=223,PAR=RLSB&RLSA&BR64&TIM1&SDL&IDP1,TRK=TA,TOLL=TA
; /* DP with DELAY Prot. */
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
ADD-
COP:COPNO=223,PAR=RLSB&RLSADTMF&DTM1&PDP1&TIM1&NSDL,TRK=TA,TO
LL=TA; /*DTMF with IMMEDIATE Prot. */
ADD-
COP:COPNO=223,PAR=RLSB&RLSA&DTMF&DTM1&PDP1&TIM1&SACK&SDL,TRK=
TA,TOLL=TA; /*DTMF with WINK Prot. */
ADD-
COP:COPNO=223,PAR=RLSB&RLSA&DTMF&DTM1&PDP1&TIM1&SDL,TRK=TA,TO
LL=TA; /*DTMF with DELAY Prot. */
CHANGE-COP:COPNO=223,COPTYPE=COPADD,DEV=ANMOSIG,INFO="TMDID";
ADD-COT:COTNO=223,PAR=RCL&IEVT&NTON&NAAT;
RP=223,COFIDX=0,CCT="DID USA IWV
CBMATTR=NONE,SRCGRP=1,CLASSMRK=EC&G711,TCCID="",DITIDX=0,TRTB
L=GDTR,RULEIDX=0,ATNTYP=COLOW,INS=Y,DEVTYPE=TC,DEV=DID,MFCVAR
=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=3,CDRINT=1,CCTINFO=0,
DIALTYPE=DIP-DIP,DIALVAR=0-0,COEX=0;

Language
BCSU TYP PER
LTG <x>
LTU <x>
EBT <x>
SACHNR Q2452x
FCTID
LWVAR
HWYBDL
BCSU MTYPE PER
LTG <x>
LTU <x>
SLOT <x>
PARTNO Q2452-x
FCTID
LWVAR
HWYBDL
PTIME REST PAR5=2
PTIME ..
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
COP COPPAR IPVH Die Paramter BELQ,WABR oder NOWA sind
NAAT entspr. dem verwendeten Prot. zu setzen
UWZ1 IPVH: Für Impulswahl
NOWA ZWZ1: Für Impulswahl
ZWZ1 MFVW: Für MFV-Wahl
MFVW MFV1: Für MFV-Wahl
MFV1 PVW1: Für MFV-Wahl
PVW1
BELQ
WABR
NOWA
COP PAR DTMF The Parameters SACK,SDL,NSDL are to set
DTM1 for the used Protocoll
NSDL DTMF: for DTMF.
BR64 DTM1: for DTMF
NAAT BR64: for DP
IDP1 PDP1: for DTMF
TIM1
PDP1
SACK
SLD
NSDL
COT COTPAR AERF STUE: Für Anzeige von Unplausiblen Events
STUE NAAT: USA Trunk (wichtig für kommende
KTON Gebührenerfassung)
NAAT
COT PAR RCL NAAT: Relevant for incoming charges
IEVT
NTON
NAAT
ESBER <x>
AVCE <x>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU LAGE <x>
COTNR <x>
COPNR <x>
WABE <w>
VBZ <w>
COS <w>
LCOSS <x>
LCOSD <x>
BUNR <x>
COFIDX <x>
SATZNR <w>
ZLNR <w>
ALARMNR <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMRK <w>
TCCID <w>
DITIDX <w>
TRTBL <w>
RULEIDX <w>
ATNTYP <w>
INBETR <w>
GERTYP AS
GER DID
MFCVAR <w>
,ANZUNT <w>
ANZZIFF <w>
PRUEFNR <w>
CIRCIDX <w>
GEB <w>
SATZINFO <w>
WAHLART IWV-IWV/
WAHLVAR MFV-MFV
COEX= <w<>
<w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU PEN <x>
COTNO <x>
COPNO <x>
DPLN <w>
ITR <w>
COS <x>
LCOSV <x>
LCOSD <x>
TGRP <x>
COFIDX <w>
CCT <w>
DESTNO <w>
ALARMNO <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMRK <w>
TCCID <w>
DITIDX <w>
TRTBL <w>
RULEIDX <w>
ATNTYP <w>
INS <w>
DEVTYPE TC
DEV DID
MFCVAR <w>
SUPPRESS <w>
,DGTCNT <w>
TESTNO <w>
CIRCIDX <w>
CDRINT <w>
CCTINFO <w>
DIALTYPE <x>
DIALVAR <w>
COEX <w>
24.2.3 TMDNH -> T1BOS for Direct Inward Dialing

Calls (T1DID)
The TMDNH (T1BOS -> T1DID) module is used as a digital trunk circuit for
incoming direct inward dialing operation. The circuits can be operated with pulse
dialing or DTMF dialing. The following protocols can be configured: Wink Start,
Delay Start and Immediate Start.
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

AMO-COP
SACK - BELQ n n x
SDL - WABR x n x
NSDL-NOWA x
EOD - WEND x x x
NAAT-NAAT x x x
BR63-IPVH y y y
DTMF-MFVW y y y
DTM1-MFV1 y y y
LSUP-LUEW n n n
• The module uses the DS120VA,DS120VB,DS120VC device handlers.
• German
/* TMDNH fuer T1-BOS T1DID CO*/
/* Trunk 1 auf Lage 1-2-109-1 IWV IMMEDIATE*/
/* Trunk 1 auf Lage 1-2-109-2 MFV IMMEDIATE*/
/* Trunk 1 auf Lage 1-2-109-3 IWV WINK Start*
/* Trunk 1 auf Lage 1-2-109-3 IWV WINK Start*/
/* Trunk 1 auf Lage 1-2-109-4 MFV WINK Start*/
/* Trunk 1 auf Lage 1-2-109-5 IWV DELAY Start*/
/* Trunk 1 auf Lage 1-2-109-6 MFV DELAY Start*/
AE-
LWPAR:TMD,TMDBOS,1,FRAMEESF&BISUB8ON&BDETON&NETUSER,1,30,4,10
,10;
EINR-BCSU:TMD,1,2,109,Q2192-X,1,,1,,,,,A;
EINRICHTEN-BUEND:BUNUM=242,NAME="T1EMI-IWV",ANZ=1;
EINRICHTEN-BUEND:BUNUM=243,NAME="T1EMI-MFV",ANZ=1;
EINRICHTEN-BUEND:BUNUM=244,NAME="T1EMW-IWV",ANZ=1;
EINRICHTEN-BUEND:BUNUM=245,NAME="T1EMW-MFV",ANZ=1;
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
EINRICHTEN-BUEND:BUNUM=246,NAME="T1EMD-IWV",ANZ=1;
EINRICHTEN-BUEND:BUNUM=247,NAME="T1EMD-MFV",ANZ=1;
/* COP 242 for IWV IMMEDIATE*/
EINR-
COP:242,IPVH&RALA&RALB&NOWA&UWZ1&NAAT,FBKW,FBKW,ANHKZ,TMDID;
/* COP 243 for MFV IMMEDIATE*/
EINR-
COP:243,MFVW&MFV1&RALA&RALB&NOWA&PVW1&NAAT,FBKW,FBKW,ANHKZ,TM
DID;
/* COP 244 for IWV WINK */
EINR-
COP:244,IPVH&RALA&RALB&BELQ&WABR&UWZ1&NAAT,FBKW,FBKW,ANHKZ,TM
DID;
/* COP 245 for MFV WINK */
EINR-
COP:245,MFVW&MFV1&RALA&RALB&BELQ&WABR&PVW1&NAAT,FBKW,FBKW,ANH
KZ,TMDID;
/* COP 246 for IWV DELAY */
EINR-
COP:246,IPVH&RALA&RALB&WABR&UWZ1&NAAT,FBKW,FBKW,ANHKZ,TMDID;
/* COP 247 for MFV DELAY */
EINR-
COP:247,MFVW&MFV1&RALA&RALB&WABR&PVW1&NAAT,FBKW,FBKW,ANHKZ,TM
DID;
EINR-COT:242,AERF&KTON&STUE&NAAT;
1,COTNR=242,COPNR=242,COS=220,LCOSS=1,LCOSD=1,BUNR=242,SATZNR
="T1DID IM IWV",NBETR=J,GERTYP=AS,GER=T1DID,WAHLART=IWV-IWV;
="T1DID IM MFV",INBETR=J,GERTYP=AS,GER=T1DID,WAHLART=MFV-MFV;
="T1DID WI IWV",INBETR=J,GERTYP=AS,GER=T1DID,WAHLART=IWV-IWV;
="T1DID WI MFV",INBETR=J,GERTYP=AS,GER=T1DID,WAHLART=MFV-MFV;
="T1DID DE IWV",INBETR=J,GERTYP=AS,GER=T1DID,WAHLART=IWV-IWV;
="T1DID DE MFV",INBETR=J,GERTYP=AS,GER=T1DID,WAHLART=MFV-MFV;
EINR-REFTA:SATZ,1-2-109-0,0;
• English
/* TMDNH fuer T1-BOS T1DID CO*/
/* Trunk 1 pen 1-2-109-1 IWV IMMEDIATE*/
/* Trunk 1 pen 1-2-109-2 MFV IMMEDIATE*/
/* Trunk 1 pen 1-2-109-3 IWV WINK Start*
/* Trunk 1 pen 1-2-109-3 IWV WINK Start*/
/* Trunk 1 pen1-2-109-4 MFV WINK Start*/
/* Trunk 1 pen 1-2-109-5 IWV DELAY Start*/
/* Trunk 1 pen 1-2-109-6 MFV DELAY Start*/
CHANGE-
0,SESREQTH=10;
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
ADD-BUEND:TGRP=242,NAME="T1EMI-IWV
E=0,ACDPMGRP=0;
ADD-BUEND:TGRP=243,NAME="T1EMI-MFV
E=0,ACDPMGRP=0;
ADD-BUEND:TGRP=244,NAME="T1EMW-IWV
E=0,ACDPMGRP=0;
ADD-BUEND:TGRP=245,NAME="T1EMW-MFV
E=0,ACDPMGRP=0;
ADD-BUEND:TGRP=246,NAME="T1EMD-IWV
E=0,ACDPMGRP=0;
ADD-BUEND:TGRP=247,NAME="T1EMD-MFV
E=0,ACDPMGRP=0;
ADD-COSSU:NEWCOS=220,AVCE=TA&TNOTCR&CDRC;
/* COP 242 for IWV IMMEDIATE*/
ADD-
COP:COPNO=242,PAR=RLSB&RLSA&BR64&NAAT&TIM1&NSDL,TRK=TA,TOLL=T
A;
CHANGE-COP:COPNO=242,COPTYPE=COPADD,DEV=ANMOSIG,INFO="TMDID";
/* COP 243 for MFV IMMEDIATE*/
ADD-
COP:COPNO=243,PAR=DTMF&RLSB&RLSA&NAAT&PDP1&DTM1,TRK=TA,TOLL=T
A;
/* COP 244 for IWV WINK */
ADD-
COP:COPNO=244,PAR=SDL&SACK&RLSB&RLSA&BR64&NAAT&TIM1,TRK=TA,TO
LL=TA;
/* COP 245 for MFV WINK */
ADD-
COP:COPNO=245,PAR=DTMF&SDL&SACK&RLSB&RLSA&NAAT&TIM1&PDP1&DTM1
,TRK=TA,TOLL=TA;
/* COP 246 for IWV DELAY */
ADD-
COP:COPNO=246,PAR=SDL&RLSB&RLSA&BR64&NAAT&TIM1,TRK=TA,TOLL=TA
;
/* COP 247 for MFV DELAY */
ADD-
COP:COPNO=247,PAR=DTMF&SDL&RLSB&RLSA&NAAT&TIM1&PDP1&DTM1,TRK=
TA,TOLL=TA;
CHANGE-COP:COPNO=247,COPTYPE=COPADD,DEV=ANMOSIG,INFO="TMDID";
ADD-COT:COTNO=242,PAR=RCL&IEVT&NTON&NAAT;
RP=242,COFIDX=0,CCT="T1DID IM
IWV",DESTNO=0,ALARMNO=2,CARRIER=1,ZONE=EMPTY,LIN=0,CIDDGTS=NO
NE,CBMATTR=NONE,SRCGRP=1,CLASSMRK=EC&G711,TCCID="",DITIDX=0,T
RTBL=GDTR,RULEIDX=0,ATNTYP=CO,INS=Y,DEVTYPE=TC,DEV=T1DID,MFCV
AR=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=3,CDRINT=1,CCTINFO=
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
0,DIALTYPE=DIP-DIP,DIALVAR=0-0,COEX=0;
RP=243,COFIDX=0,CCT="T1DID IM
MFV",DESTNO=0,ALARMNO=2,CARRIER=1,ZONE=EMPTY,LIN=0,CIDDGTS=NO
NE,CBMATTR=NONE,SRCGRP=1,CLASSMRK=EC&G711,TCCID="“,DITIDX=0,T
0,DIALTYPE=DTMF-DTMF,DIALVAR=0-0,COEX=0;
RP=244,COFIDX=0,CCT="T1DID WI
RP=245,COFIDX=0,CCT="T1DID WI
RP=246,COFIDX=0,CCT="T1DID DE
RP=247,COFIDX=0,CCT="T1DID DE
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
LWPAR TYP TMD BLNR: Blocknummer frei zu vergeben später
TMDTYP TMDBOS im BCSU einzutragen
BLNR <x> NETUSER: Für einen Trunk ist NETUSER zu
OPMODE BDETON setzen für die gegeseite nicht
BISUB8ON
FRAMEESF
NETUSER
CABLETYP 1
OESDISTH 30
OESREQTH 4
SESDISTH 10
SESREQTH 10
TMDTYPE TMDBOS NETUSER: To set for one Trunk , not ot set by
BLNO <x> partenr Trunk
OPMODE BDETON
BISUB8ON
FRAMEESF
NETUSER
CABLETYP 1
OESDISTH 30
OESREQTH 4
SESDISTH 10
SESREQTH 10
BCSU TYP TMD FCTID: Für BOS Anwendung
EBT <x>
SACHNR Q2192-x
FCTID 1
LWVAR
LWPAR <x>
AKTFC
STERM
LTERM
PTERM
HWYBDL
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
BCSU MTYPE TMD FCTID: For BOS
LTG <x> LWPAR: Set the Blocknumer defined under
LTU <x> LWPAR
SLOT <x>
PARTNO Q2192-x
FCTID 1
LWVAR
LWPAR <x>
ACTFC
STERM
LTERM
PTERM
HWYBDL
COP COPPAR IPVH Die Paramter BELQ,WABR oder NOWA sind
NAAT entspr. dem verwendeten Prot. zu setzen
UWZ1 IPVH: Für Impulswahl
NOWA ZWZ1: Für Impulswahl
ZWZ1 MFVW: Für MFV-Wahl
MFVW MFV1: Für MFV-Wahl
MFV1 PVW1: Für MFV-Wahl
PVW1
BELQ
WABR
NOWA
COP PAR DTMF The Parameters SACK,SDL,NSDL are to set
DTM1 for the used Protocoll
NSDL DTMF: for DTMF.
BR64 DTM1: for DTMF
NAAT BR64: for DP
IDP1 PDP1: for DTMF
TIM1
PDP1
SACK
SLD
NSDL
STUE NAAT: Wichtig für kommende
KTON Gebührenerfassung bei DID
NAAT (Durchwahlsätzen)
COT PAR RCL NAAT: Relevant for incoming DID Trunks for
IEVT charge-recording
NTON
NAAT
ESBER <x>
AVCE <x>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU LAGE <x>
COTNR <x>
COPNR <x>
WABE <w>
VBZ <w>
COS <w>
LCOSS <x>
LCOSD <x>
BUNR <x>
COFIDX <x>
SATZNR <w>
ZLNR <w>
ALARMNR <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMRK <w>
TCCID <w>
DITIDX <w>
TRTBL <w>
RULEIDX <w>
ATNTYP <w>
INBETR <w>
GERTYP AS
GER T1DID
MFCVAR <w>
,ANZUNT <w>
ANZZIFF <w>
PRUEFNR <w>
CIRCIDX <w>
GEB <w>
SATZINFO <w>
WAHLART IWV-IWV/
WAHLVAR MFV-MFV
COEX= <w<>
<w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU PEN <x>
COTNO <x>
COPNO <x>
DPLN <w>
ITR <w>
COS <x>
LCOSV <x>
LCOSD <x>
TGRP <x>
COFIDX <w>
CCT <w>
DESTNO <w>
ALARMNO <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMRK <w>
TCCID <w>
DITIDX <w>
TRTBL <w>
RULEIDX <w>
ATNTYP <w>
INS <w>
DEVTYPE TC
DEV T1DID
MFCVAR <w>
SUPPRESS <w>
,DGTCNT <w>
TESTNO <w>
CIRCIDX <w>
CDRINT <w>
CCTINFO <w>
DIALTYPE <x>
DIALVAR <w>
COEX <w>
24.2.4 TMDNH-T1BOS for Incoming and Outgoing

Trunk Calls
The TMDNH (T1BOS -> T1GRDSTR/T1LPSTR) module is used as a trunk circuit

for incoming and outgoing traffic. The circuits can be operated with pulse dialing
or DTMF dialing. The circuits can be operated as Loop Start or Ground Start.
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
• The module uses the DS101VA device handler.
• German
/* TMDNH fuer T1-BOS T1GRDSTR/LPSTR */
/* Trunk 1 auf Lage 1-2-109-1 GRDSTR IWV*/
/* Trunk 1 auf Lage 1-2-109-2 GRDSTR MFV*/
/* Trunk 1 auf Lage 1-2-109-3 LPSTR IWV*/
/* Trunk 1 auf Lage 1-2-109-3 LPSTR MFV*/
EINRICHTEN-WABE:542,,,AMT;
EINRICHTEN-WABE:545,,,AMT;
AE-
LWPAR:TMD,TMDBOS,1,FRAMEESF&BISUB8ON&BDETON&NETUSER,1,30,4,10
,10;
EINR-BCSU:TMD,1,2,109,Q2192-X,1,,1,,,,,A;
EINRICHTEN-BUEND:BUNUM=242,NAME="T1GRD-IWV",ANZ=1;
EINRICHTEN-BUEND:BUNUM=243,NAME="T1GRD-MFV",ANZ=1;
EINRICHTEN-BUEND:BUNUM=244,NAME="T1LPS-IWV",ANZ=1;
EINRICHTEN-BUEND:BUNUM=245,NAME="T1LPS-MFV",ANZ=1;
/* COP 242 for IWV GRD/LPSTR*/
EINR-COP:242,IPVH&NOWA&UWZ1&NAAT&ZWZ1,FBKW,FBKW;
/* COP 243 for MFV GRD/LPSTR*/
EINR-COP:243,MFVW&MFV1&NOWA&PVW1&NAAT,FBKW,FBKW;
EINR-COT:242,AERF&KTON&STUE&NAAT&LTVW;
="T1GRDSTR-IWV",INBETR=J,GERTYP=AS,GER=T1GRDSTR,WAHLART=IWV-
IWV;
="T1GRDSTR-MFV",INBETR=J,GERTYP=AS,GER=T1GRDSTR,WAHLART=MFV-
MFV;
="TILPSTR-IWV",INBETR=J,GERTYP=AS,GER=T1LPSTR,WAHLART=IWV-
IWV;
="T1LPSTR-MFV",INBETR=J,GERTYP=AS,GER=T1LPSTR,WAHLART=MFV-
MFV;
EINRICHTEN-RICHT:LRTGNEU,242,SPR,"TMC16 GRD",242,1-1-
500,,NEIN,,,,,,,,,NEIN,NEIN,,1-1-0;
EINRICHTEN-
IER=1,ZONE=LEER,LATTR=KEINE,VCCYK=4;
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
EINR-LDPLN:LWM=542-X,LRTG=242,LBER=1;
EINRICHTEN-RICHT:LRTGNEU,243,SPR,"TMC16 GRD",243,1-1-
500,,NEIN,,,,,,,,,NEIN,NEIN,,1-1-0;
EINRICHTEN-
EINRICHTEN-RICHT:LRTGNEU,244,SPR,"TMC16 LPS",244,1-1-
500,,NEIN,,,,,,,,,NEIN,NEIN,,1-1-0;
EINRICHTEN-
EINRICHTEN-RICHT:LRTGNEU,245,SPR,"TMC16 LPS",245,1-1-
500,,NEIN,,,,,,,,,NEIN,NEIN,,1-1-0;
EINRICHTEN-
EINR-REFTA:SATZ,1-2-109-0,0;
• English
ADD-WABE:CD=542,DAR=CO,CHECK=N;
ADD-WABE:CD=545,DAR=CO,CHECK=N;
CHANGE-
0,SESREQTH=10;
ADD-BUEND:TGRP=242,NAME="T1GRD-IWV
E=0,ACDPMGRP=0;
ADD-BUEND:TGRP=243,NAME="T1GRD-MFV
E=0,ACDPMGRP=0;
ADD-BUEND:TGRP=244,NAME="T1LPS-IWV
E=0,ACDPMGRP=0;
ADD-BUEND:TGRP=245,NAME="T1LPS-MFV
E=0,ACDPMGRP=0;
ADD-
COP:COPNO=242,PAR=BR64&NAAT&TIM1&NSDL&IDP1,TRK=TA,TOLL=TA;
ADD-COT:COTNO=242,PAR=RCL&AEOD&IEVT&NAAT&NTON;
RP=242,COFIDX=0,CCT="T1GRDSTR-
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
RTBL=GDTR,RULEIDX=0,ATNTYP=CO,INS=Y,DEVTYPE=TC,DEV=T1GRDSTR,M
FCVAR=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=3,CDRINT=1,CCTIN
FO=0,DIALTYPE=DIP-DIP,DIALVAR=0-0,COEX=0;
RP=243,COFIDX=0,CCT="T1GRDSTR-
RTBL=GDTR,RULEIDX=0,ATNTYP=CO,INS=Y,DEVTYPE=TC,DEV=T1GRDSTR,M
FCVAR=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=3,CDRINT=1,CCTIN
FO=0,DIALTYPE=DTMF-DTMF,DIALVAR=0-0,COEX=0;
RP=244,COFIDX=0,CCT="TILPSTR-IWV
L=GDTR,RULEIDX=0,ATNTYP=CO,INS=Y,DEVTYPE=TC,DEV=T1LPSTR,MFCVA
R=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=3,CDRINT=1,CCTINFO=0
,DIALTYPE=DIP-DIP,DIALVAR=0-0,COEX=0;
RP=245,COFIDX=0,CCT="T1LPSTR-MFV
",DITIDX=0,TRTBL=GDTR,RULEIDX=0,ATNTYP=CO,INS=Y,DEVTYPE=TC,DE
V=T1LPSTR,MFCVAR=0,SUPPRESS=0,DGTCNT=0, TESTNO=1,CIRCIDX=3,
CDRINT=1,CCTINFO=0,DIALTYPE=DTMF-DTMF,DIALVAR=0-0,COEX=0;
ADD-RICHT:LRTENEW,242,VCE,"TMC16 GRD ", 242,1-1-
500,,NO,,,"",,,,,,NO,,NO,"",1-1-0;
ADD-RICHT:LRTENEW,243,VCE,"TMC16 GRD ", 243,1-1-
500,,NO, ,,"",,,,,,NO, ,NO,"",1-1-0; 
ADD-RICHT:LRTENEW,244,VCE,"TMC16 LPS ",244,1-1-500,,NO,
,,"",,,,,,NO, ,NO,"",1-1-0;
ADD-RICHT:LRTENEW,245,VCE,"TMC16 LPS ", 245,1-1-
500,,NO, ,,"",,,,,,NO, ,NO,"",1-1-0;
ADD-LODR:ODR=2,INFO="QUER A3 OFFEN";
ADD-
R=1,ZONE=EMPTY,LATTR=NONE,VCCYC=4;
ADD-
ADD-
ADD-
R=1,ZONE=EMPTY,LATTR=NONE,VCCYC=4;
ADD-LDPLN:LDP="542"-"X",LROUTE=242,LAUTH=1,SPC=22,PINDP=N;
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
LWPAR TYP TMD BLNR: Blocknummer frei zu vergeben später
TMDTYP TMDBOS im BCSU einzutragen
BLNR <x> NETUSER: Für einen Trunk ist NETUSER zu
OPMODE BDETON setzen für die gegeseite nicht
BISUB8ON
FRAMEESF
NETUSER
CABLETYP 1
OESDISTH 30
OESREQTH 4
SESDISTH 10
SESREQTH 10
TMDTYPE TMDBOS NETUSER: To set for one Trunk , not ot set by
BLNO <x> partenr Trunk
OPMODE BDETON
BISUB8ON
FRAMEESF
NETUSER
CABLETYP 1
OESDISTH 30
OESREQTH 4
SESDISTH 10
SESREQTH 10
BCSU TYP TMD FCTID: Für BOS Anwendung
EBT <x>
SACHNR Q2192-x
FCTID 1
LWVAR
LWPAR <x>
AKTFC
STERM
LTERM
PTERM
HWYBDL
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
BCSU MTYPE TMD FCTID: For BOS
LTG <x> LWPAR: Set the Blocknumer defined under
LTU <x> LWPAR
SLOT <x>
PARTNO Q2192-x
FCTID 1
LWVAR
LWPAR <x>
ACTFC
STERM
LTERM
PTERM
HWYBDL
WABE KZP AMT Kennzahlpunkt-AMT (nur für gehend relevant)
WABE DAR CO Digit Anylis result=CO (only necessary for
outgoing )
COP COPPAR IPVH Für Impulswahl:
NAAT IPVH&NAAT&UWZ1&NOWA&ZWZ1
UWZ1 Für MFV-
NOWA Wahl:.MFVW&MFV1&NAAT&NOWA&PVW1
ZWZ1
MFVW
MFV1
PVW1
COP PAR DTMF DTMF: for DTMF.
DTM1 DTM1: for DTMF
NSDL BR64: for DP
BR64 PDP1: for DTMF
NAAT
IDP1
TIM1
PDP1
LTVW
STUE
KGZL
KTON
NAAT
COT PAR RCL
AEOD
IEVT
ICZL
NTON
NAAT
ESBER <x>
AVCE <x>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
NAME <w>
ANZ <w>
RESERV <w>
ANZFANG <w>
ANZACD <w>
PRIONUM <w>
TDDRFLAG <w>
GDTRRGL <w>
ACDPMGRP <w>
NAME <w>
NO <w>
RSV <w>
TRACENO <w>
ACDTHRH <w>
PRIONO <w>
TDDRFLAG <w>
GDTRULE <w>
ACDPMGRD <w>
PTIME Standart Werte werden verewendet
PTIME Standart values will be used
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU LAGE <x>
COTNR <x>
COPNR <x>
WABE <w>
VBZ <w>
COS <w>
LCOSS <x>
LCOSD <x>
BUNR <x>
COFIDX <x>
SATZNR <w>
ZLNR <w>
ALARMNR <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMRK <w>
TCCID <w>
DITIDX <w>
TRTBL <w>
RULEIDX <w>
ATNTYP <w>
INBETR <w>
GERTYP AS
GER T1LPSRT or
T1GDSTR
MFCVAR <w>
,ANZUNT <w>
ANZZIFF <w>
PRUEFNR <w>
CIRCIDX <w>
GEB <w>
SATZINFO <w>
WAHLART IWV-IWV/
WAHLVAR MFV-MFV
COEX= <w<>
<w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
TACSU PEN <x>
COTNO <x>
COPNO <x>
DPLN <w>
ITR <w>
COS <x>
LCOSV <x>
LCOSD <x>
TGRP <x>
COFIDX <w>
CCT <w>
DESTNO <w>
ALARMNO <w>
CARRIER <w>
ZONE <w>
LIN <w>
CIDDGTS <w>
CBMATTR <w>
SRCGRP <w>
CLASSMRK <w>
TCCID <w>
DITIDX <w>
TRTBL <w>
RULEIDX <w>
ATNTYP <w>
INS <w>
DEVTYPE TC
DEV T1LPSTR or
T1GRDSTR
MFCVAR <w>
SUPPRESS <w>
,DGTCNT <w>
TESTNO <w>
CIRCIDX <w>
CDRINT <w>
CCTINFO <w>
DIALTYPE <w>
DIALVAR <x>
COEX <w>
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA

Language
LDIENST <w>
NAME <w>
BUNUM <x>
ZKNNR <w>
ROUTOPT <w>
REROUT <w>
MFVUMS <w>
MFVANZ <w>
MFVTEXT <w>
MFVPULS <w>
VLVER <w>
UMLVER <w>
ZLNR <w>
PIN <w>
ROUTATT <w>
EMCYRTT <w>
INFO <w>
PZKNNR <w>
LSVC <w>
NAME <w>
TGRP <x>
DNNO <w>
ROUTOPT <w>
REROUT <w>
DTMFCNV <w>
DTMFDISP <w>
DTMFTEXT <w>
DTMFPULS <w>
PLB <w>
FWDBL <w>
DESTNO <w>
PIN <w>
ROUTATT <w>
EMCYRTT <w>
INFO <w>
PDNNO; <w>
LODR nur für gehende belegung relevant, siehe LCR
Administration
administration
LDAT nur für gehende belegung relevant, siehe LCR
Administration
LDAT only fpr outgoing Trunks necessary, see LCR
administration
LDPLN nur für gehende belegung relevant, siehe LCR
Administration
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
Recorded Announcement Feature

Language
administration
24.3 Recorded Announcement Feature

In the event of an incoming call, a recorded announcement can be played to the
calling subscriber. This announcement can originate from a recorded
announcement device or take the form of a preconfigured OpenScape 4000
recorded announcement.
24.3.2.1 With Privileged Station AMO SSC
• The COP parameter ANNC (local recorded announcement) is to be set in the

incoming circuit. A configured local recorded announcement is then created
for the incoming seizure. The COP parameters DTN (incoming seizure dial
tone) and ANNC are mutually exclusive.
• If the system is to use a predefined recorded announcement or music, the

local recorded announcements must be assigned the desired value in AMO
ZAND:TYPE=TONES.
• If an external recorded announcement device is to be used, a privileged

station must be configured with the AMO SSC with the TYPE=EXTANN and
the CPCALL=LOCANN. The external recorded announcement device is
connected to this privileged station.
24.3.2.2 Synchronous / Asynchronous Recorded

Announcement with TMOM Module
• See Chapter 168, “Synchronized Announcements”/Asynchronous Recorded

Announcement
• The TMOM module and a recorded announcement device are required.
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
DIT Feature
24.4 DIT Feature

If an analog trunk (CO or tie) is seized in the incoming direction, the call is
forwarded to the number configured in the Hotline Table.
24.4.2 User Interface

In the event of seizure of an incoming circuit, a CO or tie trunk subscriber is
automatically forwarded to the preconfigured subscriber number, regardless of
the number he has dialed.

• The DITW feature (COP parameter DITW ) with digit prefixing (DGTPR in
AMO TACSU) has the same effect in the case of a tie trunk; both features may
not be used together.
• The feature is only effective in the case of incoming seizure type ATND or
HAUS1.
• The COT parameter DIT must be set in the associated trunk.
• The COP parameters DITW, DTN, DTV may not be set when using the DIT
feature.
• The COP parameters DTN (incoming seizure dial tone) and DTV (dial tone
analysis) have no effect if the DIT feature is activated. Therefore,
synchronous/asynchronous recorded announcement is also not possible.
• The HOTRCL feature in AMO FEASU must be set, and a valid DITIDX
configured in AMO TACSU and a subscriber number configured in AMO
HOTLN.
• In AMO TACSU, the DITIDX must be in the range of 1 to 512; a DITIDX value
of 0 acts as if no DIT feature had been configured.
• If no HOTLN number has been entered or if FEASU HOTRCL has not been
set or the DITIDX in AMO TACSU has not been entered, the DIT feature is
not executed. In this case, the call behaves as if no DIT feature has been
configured (i.e. switching system call).
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
Supplemantary dialing
24.4.4 Generation Example
24.4.4.1 German
• EINR-HOTLN:TYP=HOTZIEL,HTLNIDX=<Nummer>,RZIEL=<key-
Nummer>;
24.4.4.2 English
• ADD-HOTLN:TYPE=HOTDEST,HTLNIDX=<number>DEST=<key-
Nummer>;

Language
FEASU SET HOTROE HOTROE muss freigegeben werden
FEASU SET HOTRLC HOTRLC must set to free

COT COTPAR DIT Parameter DIT muss gesetzt werden.
COT COTPAR DIT Parameter must be set
HOTLN TYP HOTZIEL HTLNIDX ein Wert zwischen 0 und 512
HTLNIDX <x> RZIEL eine gültige Teilnehmernummer
RZIEL <yyy>
HOTLN TYPE HOTDEST HTLNIDX a value between 0 and 512
HTLNIDX <x> DEST a valid Subscriber Number
DEST <yyyy>
TACSU DITIDX <x> Es ist der entsprechende Wert welcher unter
HTLNIDX eingetragen wurde einzusetzen
TACSU DITIDX <x> Take the value what is set in HTLNIDX and set
it in TACSU
24.5 Supplemantary dialing

The feature “Supplementary dialing” is forbidden to use by US-Trunks.
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
Real Dialtone from Central-Office
24.6 Real Dialtone from Central-Office

If the outgoing seized Trunk should hear “Real Dialtone” from the connected CO
and should connected to the Subscriber or the transit-trunk, the following
parameters are to set:
This function is only possible if the outgoing trunk has set the parameters “waiting
for dialtone” or “line with no start dial signal”.
The COP-Parameter “TDED” must administrated to the existing COP-

Parameters.
The CO must send “Dial-Tone”
In AMO-TACSU the Parameter DIALVAR=X-8 is to set, “X” is normally to set to “0”
The AMO-LODR is to administrate only with END (no ECHOFELD) so that the
dial-tone can be heard allready when dialing the access-code.
Also the AMO-LDPLN is only to administrate with the access-code.
Remark: The dial-tone from the CO must be released from the CO after getting
the first dialed digit.
24.7 RealTrunk Group Overflow (Rerouting) for Trunks in the Event of a

Fault
For outgoing seizable circuits or ports (TMC16/T1Loop Ground) which are
triggered on account of a fault (e.g. no incoming circuit seizable or no audible
signal) and enter disabled state, another circuit can be searched in the same
trunk group and seized, or if there is no trunk available in the same trunk
group,searched in a different trunk group and seized via trunk group overflow
(Rerouting) without having to dial again.
To this end, it is necessary to configure another trunk group with circuits, in

addition to the trunk group originally used.
The original and additional trunk group numbers must be specified in AMO
RICHT. Furthermore, the parameter REROUTING must be set to YES, also the
parameter RERINGRP (Rerouting in the same trunk-group) must be set to YES
The AMO LDAT with its original LCR number must be reconfigured with the
additional trunk group number.
Example:
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
RealTrunk Group Overflow (Rerouting) for Trunks in the Event of a Fault
24.7.1 Original Trunk Group

• German
RRGL=0,ACDPMGRP=0;
NR=223,COFIDX=0,SATZNR="TMC16
AS,GER=LPSTR,MFCVAR=0,ANZUNT=0,ANZZIFF=0,PRUEFNR=1,CIRCIDX=2,
GEB=1,SATZINFO=0,WAHLART=IWV-IWV,WAHLVAR=0-0,COEX=0;
EINRICHTEN-RICHT:ART=LRTGNEU,LRTG=223,LDIENST=SPR,NAME="TMC16
500,REROUT=JA,ROUTATT=NEIN,RERINGRP=JA,EMCYRTT=NEIN,PZKNNR=1-
1-0,===RERINGROUP=JA====;
EINRICHTEN-
• English
ADD-BUEND:TGRP=223,NAME=”TMC16-
1LOOP“,NO=2,RSV=N,TRACENO=0,ACDTHRH=*,PRIONO=1,TDDRFLAG=ON,GD
TRRULE=0,ACDPMGRP=0,CHARCON=NEUTRAL;
RP=223,COFIDX=0,CCT=”TMC16 LOOP
“,DESTNO=0,ALARMNO=2,CARRIER=1,ZONE=EMPTY,LIN=0,CIDDGTS=NONE,
CBMATTR=NONE,SRCGRP=1,CLASSMRK=EC&G711,TCCID=”
“,DITIDX=0,TRTBL=GDTR,RULEIDX=0,ATNTYP=COLOW,INS=Y,DEVTYPE=TC
,DEV=LPSTR,MFCVAR=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=3,CD
RINT=1,CCTINFO=0,DIALTYPE=DIP-DIP,DIALVAR=0-0,COEX=0;
ADD-RICHT:MODE=LRTENEW,LRTE=223,LSVC=VCE,NAME=”TMC16 LOOP
“,TGRP=223&224,RERINGRP=YES,REROUT=YES,DNNO=1-1-
400,ROUTATT=YES,EMCYRTT=NO,PDNNO=1-1-
0,CHARCON=NEUTRAL,CONFTONE=NO;
ADD-
ADD-
ADD-LODR:ODR=2,INFO=”QUER A3 OFFEN”;
Overflow Trunk Group
A31003-H3170-S103-6-7620, 02/2019
Analog Trunking USA
RealTrunk Group Overflow (Rerouting) for Trunks in the Event of a Fault
24.7.2 Trunk Group Overflow

• German
/* Ein weiters Bündel einrichten */
EINRICHTEN-BUEND:BUNUM=224,NAME="TMC16-UEBERLAUF
RRGL=0,ACDPMGRP=0;
/* Weietere Sätze oder Satz einrichten */
NR=224,COFIDX=0,SATZNR="TMC16-UEBERLAUF
AS,GER=LPSTR,MFCVAR=0,ANZUNT=0,ANZZIFF=0,PRUEFNR=1,CIRCIDX=2,
GEB=1,SATZINFO=0,WAHLART=IWV-IWV,WAHLVAR=0-0,COEX=0;
/* Die bestehnde Richtung umdas weitere Bündel erweitern
sowie REROUTING auf JA setzen /*
EINRICHTEN-RICHT:ART=LRTGNEU,LRTG=223,LDIENST=SPR,NAME="TMC16
",BUNUM=223&224,ZKNNR=1-1-
500,REROUT=JA,ROUTATT=NEIN,EMCYRTT=NEIN,PZKNNR=1-1-0;
/* LDAT für die bestehden LRTG-Richtung nochmals mit dem
neuem Bündel einrichten */
EINRICHTEN-
• English
/* Spezial Trunk-Group for Rerouting /
ADD-BUEND:TGRP=224,NAME="TMC16 -Rerouting
E=0,ACDPMGRP=0;
/* Genrating one or more Trunks for Rerouting */
RP=223,COFIDX=0,CCT="TMC16 LOOP
L=GDTR,RULEIDX=0,ATNTYP=COLOW,INS=Y,DEVTYPE=TC,DEV=LPSTR,MFCV
0,DIALTYPE=DIP-DIP,DIALVAR=0-0,COEX=0;
/* Change AMO-RICHT for 2 Trunk-Groups and REROUTING=YES */
ADD-RICHT:LRTENEW,223,VCE,"TMC16 LOOP ", 223&224,1-1-
500,,NO, ,,"",,,,,,YES,,NO,"",1-1-0;
/* Add LDAT for the existing LROTE with the Trunk-Group for
Rerouting */
ADD-
A31003-H3170-S103-6-7620, 02/2019
anif_en.fm
Feature Description
25 ANIF Automatic Number Identification

ANIF (automatic number identification forward) is a OpenScape 4000 feature for
the Confederation of Independent States (CIS), which provides the exchange
with calling line number information.
With the ANIF feature, the OpenScape 4000 system supports the following public
network services:
• Toll exchange connections (long-distance)
• Special services
• Chargeable services
• Malicious call tracing
25.2 User Interface

No explicit interface for OpenScape 4000 users.

Used primarily for CIS.
25.4 Generation
• Add board data (DIUC64):
ADD-
BCSU:MTYPE=DIU,LTG=number,LTU=number,SLOT=number,PARTNO="Q218
5-X ";
• Add board data (SIUX):
ADD-
BCSU:MTYPE=SIUP,LTG=number,LTU=number,SLOT=number,PARTNO="Q22
33-X ",MFCTYPE=ANIF,LWVAR=0,FCTID=5;
• Add digit analysis result for device type "BWCISL"
• Add timers for device type "BWCISL"
A31003-H3170-S103-6-7620, 02/2019
anif_en.fm
Generation
COPY-PTIME:INIBLOCK=54,TBLK=3;
CHANGE-PTIME:TYPE=REST,TBLK=3,BTYPE=PARA,P11=1;
• Add classes of service for device type "BWCISL"
ADD-
COSSU:NEWCOS=1,AVCE=TTCR2&TTCR4&CDRATN&CDRC&COSXCD&FWDNWK&MTR
ACE& ATRACE;
CHANGE-
COSSU:TYPE=COS,COS=1,AFAX=TTCR2&FAX&BASIC&INTWOR&OFTFS;
CHANGE-COSSU:TYPE=COS,COS=1,ADTE=TTCR2&BASIC&DSM;
ADD-COSSU:NEWCOS=200,AVCE=TA&TSUID&TNOTCR&CDRC;
ADD-COSSU:NEWCOS=106,AVCE=ANITC;
CHANGE-COSSU:TYPE=COEX,COEX=6,COS=106;
• Add class of parameter for device type "BWCISL"
ADD-
COP:COPNO=201,PAR=SDL&ANS&LSUP&RLSA&BR64&NOAN&TIM1&IDP1&ANIW&
TL7& RF0C&AST1;
• Add class of trunk for device type "BWCISL"
ADD-COT:COTNO=201,PAR=RCL&ANS&TRAI&NTON;
• Assign trunk group for device type "BWCISL"
ADD-BUEND:TGRP=129,NAME="ani-cis ',NO=4;
• Edit MFC table:
COPY-MFCTA:MFCVARI=19,MFCVAR=1;
CHANGE-MFCTA:MFCVAR=1,TYPE=TBLB,OPT=FSIG,PHYSIG=15,SIG=EOD;
CHANGE-MFCTA:MFCVAR=1,TYPE=MFCVAR,OPT=SUPERV,MAXDGTS=8;
• Add analog trunk configuration data:
ADD-TACSU:PEN=GG-UU-BBB-
SS,COTNO=201,COPNO=201,COS=200,LCOSV=1,LCOSD=1,TGRP=129,CCT="
ani-cis
outg",NNO=9,INS=YES,DEVTYPE=TC,DEV=BWCISL,MFCVAR=1,DGTCNT=1,C
IRCIDX=3,CDRINT=1,DIALTYPE=DIP-DIP,DIALVAR=0-0;
• Assign outgoing route data
ADD-RICHT:MODE=LRTENEW,LRTE=229,LSVC=ALL,NAME="mfs-cis
",TGRP=129,DNNO=1;
ADD-LODR:ODR=49,CMD=OUTCOEX,COEX=6;
ADD-LODR:ODR=49,CMD=ECHO,FIELD=2;
ADD-LODR:ODR=49,CMD=END;
ADD-
LDAT:LROUTE=229,LSVC=ALL,TGRP=129,ODR=49,LAUTH=1,LATTR=WCHREG
;
ADD-LDPLN:LDP=429-z,LROUTE=229,LAUTH=1;
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
Feature Description
26 Automatic Node Topology Detection

This feature is used to automatically detect the topology of a OpenScape 4000
network and communicate the topology data to the higher-level tools such as
Remote Service Platform-Smart.
To this end, provided the feature has been activated, a so-called "partner table"
which can be queried with the AMO KNTOP is established automatically in every
OpenScape 4000 node. This table contains information per B-channel group
concerning the partner nodes (adjacent node = nearest transit node) connected
via this B-channel group in the circuit.
By querying all nodes, i.e. calling up the AMO KNTOP in all nodes, the tool
determines the topology of the entire network.
This feature always uses the physical node numbers / node access codes
(defined in the AMO ZAND), not the virtual ones,for example, configured in the
AMO KNDEF.
Automatic detection only functions in a homogenous OpenScape 4000/HiPath

4000 network. CorNet-NQ with Segmentation 8 must be configured as the
networking protocol. Components which convey the CorNet-NQ protocol
transparently are not detected (e.g. ATM networks, multiplexers, ViNet).
However, the OpenScape 4000 nodes networked via such installations do appear
in the topology. Remote IP access points are not detected. Only the OpenScape
4000 host system is detected, as only the host system is assigned a physical
node number.
In heterogonous networks (e.g. with Hicom 300 nodes), you can use the AMO
KNTOP to perform manual entries in the partner table which can no longer be
overwritten by automatic entries. You also have the option of marking manual
entries as overwriteable. These can then be replaced by automatic entries. The
purpose of this is to configure Hicom 300 nodes which you know will be upgraded
to OpenScape 4000 in future with this marker, thus avoiding the need to
subsequently perform changes with the AMO KNTOP.
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
Feature Description
PNNO=10-89-100 PNNO=10-89-400
PNODECD=808901 1-2-25-0 1-2-79-0 PNODECD=808904
1-2-103-0 1-2-103-0
NODE 10-89-100 NODE 10-89-400
1-2-25-1 1-2-79-1
1-2-79-0 1-2-79-1
PNNO=10-89-200 PNNO=10-89-300
PNODECD=808902 PNODECD=808903
NODE 10-89-200 NODE 10-89-300

1-2-103-0 1-2-103-0
1-2-79-1 1-2-79-0
Figure 11 Example: Homogenous OpenScape 4000/HiPath 4000 network
In Figure 11, Example: Homogenous OpenScape 4000/HiPath 4000 network, the

physical nodes are specified with the AMO ZAND designations PNNO and
PNODECD. The tie lines are designated by specifying the port equipment
number (PEN) in the corresponding partner nodes. The tie trunk circuits can be
S0 or S2 circuits (also ATM circuits); CorNet-NQ with Segmentation 8 must be
assigned to all circuits as the networking protocol.
In nodes 10-89-100, the following information is stored in the partner table:
– The line at the tie trunk circuit with PEN 1-2-25-0 leads to the physical
node with the node number 10-89-400 and the node access code 808904
(partner node). In the partner node, this line is connected to PEN 1-2-79-
0.
– The line at circuit 1-2-25-1 leads to partner node 10-89-4200 (node

access code 808902). There, this line is connected to circuit 1-2-79-0.

In node 10-89-400, the following information is stored in the partner table:
– The line at circuit 1-2-79-0 leads to partner node 10-89-100 (node access
code 808901). There, this line is connected to circuit 1-2-25-0.
– The line at circuit 1-2-79-1 leads to partner node 10-89-300 (node access
code 808903). There, this line is connected to circuit 1-2-79-1.
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
User Interface

The same principle applies to the entries in the partner tables of the remaining
nodes.
The user tool (e.g. Remote Service Platform) can detect and graphically display
the connecting lines by assigning the nodes / PEN pairs of all partner tables. For
example, the partner tables of 10-89-100 and 10-89-400 contain the matching
pairs:
10-89-100: Circuit 1-2-025-1 leads to node 10-89-200, where the circuit
is 1-2-079-0
is 1-2-079-0
is 1-2-103-0
This means that a connecting line exists between these points.
26.2 User Interface

Every node can be queried individually by service personnel via AMO. After the
OpenScape 4000/HiPath 4000 network nodes have been booted and assuming
the feature is activated (which it is as standard), establishment of the partner
tables can be commenced automatically in each node following a stabilization
period (approx. 5 min.). As the cross-node exchange of information is handled via
the CorNet-NQ messages SETUP or CONNECT, the network must be carrying
switching loads. The time taken until the complete topology is established
depends on the load situation and the configuration of the ZAND Polling Timer.
The feature is designed in such a way that only long-term changes (of an order
of magnitude of 10 min.) are detected and network performance is not impaired.
In this context, it must be noted that, although the automatic mechanism is started
immediately in the case of newly configured lines / B-channel groups or activated
lines, an entry is only initiated upon the presence of a switching load.
In the event of faults (interrupted/deactivated lines, defective or deactivated

nodes), the entries are not deleted until after an intentional delay. A node is only
deleted from the partner table automatically if it does not respond despite multiple
repetitions, with the repetition interval likewise depending on the ZAND Polling
Timer. A switching load has no effect on the deletion.
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
Service Information
IMPORTANT: When using “Automatic Node Topology Detection” feature to

switches with mixed routes to a partner system i.e. IP trunking and TDM, then the
Automatic Topology will not work unless there is a corresponding overlay network
with Gateway Information in AMO LDAT (GW parameter) to the partner nodes.
Required is therefore to use the configuration of an overlay network via IP
trunking to the corresponding nodes with correct GW LDAT partner entries. If the
configuration is incorrect then no TSC Setup will be sent for the feature.
26.3.1 Feature Activation / Deactivation

The feature is activated as standard.
With the AMO command:

DIS-ZAND:TYPE=ALLDATA3;
you can determine if the feature is activated. If the value of the parameter
NWTOPTIM is anything other than 0, the feature is active. The value designates
the polling intervals, i.e. the intervals at which the poll is switched from one
CorNet-NQ line to the next, or from one B-channel group to the next. The
sequence is determined by the mapping of the physical / fictional lines in the
system (i.e. the "Lines").
With the AMO command:

CHA-ZAND:TYPE=ALLDATA3,NWTOPTIM=0;
the polling is stopped, but not the feature in general. In other words, lines
previously marked for the feature may still lead to new entries in the partner table.
Existing entries are likewise retained. These can be deleted with the AMO
KNTOP, if necessary.
If the feature has never been activated because NWTOPTIM was set to 0 in the
AMO generation batch before the circuits were configured with the AMO TDCSU,
the feature is generally deactivated and no entry is made in the partner table. If
the feature is to be activated, the following AMO command must be entered:
CHA-ZAND:TYPE=ALLDATA3,NWTOPTIM=xx; (xx > 0, corresponds to polling

time in seconds)
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
Service Information
26.3.2 Feature Parameterization

If the feature is activated (see Section 26.3.1, “Feature Activation / Deactivation”),
you can make certain adjustments. However, the basic settings suffice in virtually
all cases.
• Configuring the polling interval (handling of the Polling Timer is described in

Section 26.3.1, “Feature Activation / Deactivation”):
CHA-ZAND:TYPE=ALLDATA3,NWTOPTIM=<time in seconds>;
The default setting is 20 seconds. If the polling interval is shortened, the poll
is performed faster, which results in the partner table being adjusted faster in
the event of changes in the topology. However, this increases the network
load. The opposite happens if a longer polling interval is selected.
• Configuring the Multiplexer Timer of a circuit / B-channel group:

CHA-TDCSU:PEN=ltg-ltu-slot-circuit,NWMUXTIM=<time in
seconds>;
The default setting is 10 seconds. This allows you to specify the time windows
in which further partner node messages are to be awaited once a partner
node has reported to a line / B-channel group. This is only of significance if
several partner nodes are connected to a line / B-channel group via a
multiplexer or another CorNet-NQ transport system (e.g. ViNet).
If, in this instance, an excessively small time windows is selected, partner
nodes might not be detected until after many polling cycles, with this in turn
being dependent on the switching situation (if the partner node is frequently
busy with calls, be it in transit or as a terminating node of a connection, there
is a high probability that the call will fall within a time window and thus be
detected).
If an excessively large time windows is selected, the processor load is
increased, as every call within the time windows is processed by the program.
The load in the D-channel of the networking protocol is likewise increased.
IMPORTANT: The standard setting of the NWMUXTIM in the AMO TDCSU

should only be altered in exceptional cases.
• The number of repetitions of unanswered messages to the partner node

before the node is deleted from the partner table is fixed at a value of 5 and
cannot be administrated via AMO.
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
Service Information
Derived from ZAND / NWTOPTIM: Polling time

related to the specific line / B-channel group
NWMUXTIM Entry into partner table.
Time axis
Further calls
1st Call
Line / B-channel group is marked for the reporting Line is ...

procedure
Figure 12 Timing parameterization
Entry i. Pt table
Polling time Polling time Polling time Polling time

NWM Time axis
UXTIM
Transmit to Transmit to
1st
Line marked No  partner Line marked partner
Call
action
Reset line marking
Figure 13 View across several polling cycles
Figure 12, Timing parameterization shows the effect of the two timers
NWTOPTIM and NWMUXTIM within a polling period. The NWMUXTIM does not
start until after the line or B-channel group has been marked (this takes place
automatically on every 2nd poll) and a call has been established via the marked
line. In this procedure, an entry is made in the partner table (either a new entry is
made, or an old one overwritten).
It must be noted that the polling time does not correspond to the ZAND value
NWTOPTIM, but is instead derived from it: NWTOPTIM is the polling time
between 2 successive lines / B-channel groups. The respective line is not due
again until all lines in the system have been processed (this means that the time,
in relation to the line, is yielded by a multiplication of NWTOPTIM with the number
of CorNet-NQ lines / B-channel groups in the system).
Figure 13, View across several polling cycles illustrates the behavior across
several polling cycles in relation to the line. Let us assume there is, as yet, no
entry in the partner table for this line. You see that a transmission is started to the
partner (provided this is already known in the partner table) with every 2nd polling
cycle. Only via this mechanism are nodes deleted from the partner table
automatically in the event of repeated failure (partner does not answer). In the
case of multiplexers / ViNet, i.e. whenever several partner nodes are "connected"
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
Service Information
to one line, the further Calls for the nodes connected via the line must fall within
the NWMUXTIM time windows (highlighted field in the diagram), in order for them
to be adopted in the partner table.
26.3.3 What Information Does the Feature Provide?

By means of the AMO KNTOP, manual entries can be created in the partner table.
Manual and automatic entries are displayed and can also be deleted. Output can
be realized both in short and long output formats. In short output format, only the
most important information of the partner is displayed, while long output format
also displays additional information concerning the own node. Furthermore, a
third format is available for diagnostic purposes. This is the query format START
(see Section 26.3.4, “Diagnostic options”). The following section briefly explains
the KNTOP outputs of the long output format:
• NNO: This is the physical node number, as configured individually in the

PNNO parameter of the AMO ZAND in every node. In the KNTOP output
mask, the NNO of the own node is displayed in the left column beneath the
heading "OWN NODE" and that of the partner in the right column beneath the
heading "PARTNER NODE" (see Figure 15, Output mask of the AMO KNTOP
with overwritten MANAUT entry)
• NWTOPTIM: Polling Timer configured by AMO ZAND (see Section 26.3.2)
• NODECD: This is the physical node access code as configured individually in

every node in the PNODECD parameter of the AMO ZAND. In the KNTOP
output mask, the NODECD of the own node is displayed in the left column
beneath the heading "OWN NODE" and that of the partner in the right column
beneath the heading "PARTNER NODE" (see Figure 15, Output mask of the
AMO KNTOP with overwritten MANAUT entry). NODECD can also be
designated as a node number, making it a number that is thus interpreted by
the "Least Cost Routing" mechanism.
IMPORTANT: If the feature is activated, an open numbered LCR route and

a dialing pattern with its physical node access code must be configured in
every network node for every partner node (adjacent node). The LCR bundle
(AMO LDAT) need only be specified for formal reasons and is not evaluated.
Please check whether the physical node figures are already configured in the
LCR for the "Route Optimization" feature. If so, no further settings are
necessary.
• PEN: The PEN of the tie trunk circuit leading to the partner node is displayed
under the heading "OWN NODE". Under the heading "PARTNER NODE", the
PEN configured as an own node is displayed in the partner. This is always the
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
Service Information
output in the case of automatic entries (see description of the AUT field); the
output field may be blank in the case of manual entries, as the PTPEN
parameter is freely selectable in the add branch.
• BCGR: The B-channel group of the tie trunk circuit leading to the partner node
is displayed under the heading "OWN NODE".
Although the BCGR field is also available under the heading "PARTNER
NODE", it is only valid in the case of manual entries for digital circuits. In the
case of automatic entries, no value is displayed, regardless of the
configuration in the partner node. This is because the answering mechanism
is handled via the D-channel protocol. However, there is only 1 D-channel for
all B-channel groups, meaning that no assignment can be determined in this
context. The field remains blank in the case of manual entries for analog
circuits and of automatic entries.
• TGRP: The number of the trunk group to which the tie trunk circuit or the B-
channel group belongs in the own node.
• OVRD: 3 possibilities:
1. Display field is blank: This can only involve an automatic entry (see
description of the AUT field) that was never based on a manual entry.
2. MANONLY: The entry marked as such is manual, i.e. is realized with the
AMO KNTOP. It cannot be overwritten automatically.
3. MANAUT: Although the entry marked as such was originally made
manually, it can be overwritten automatically. Whether or not this is the
case can be derived from the AUT display field (if checked, it has been
overwritten).
• AUT: If this display field is checked, it involves an automatically created entry.

All information regarding the partner node has been provided by the node
itself. The partner node is actually connected and "live", i.e. it responds to the
messages sent at the polling intervals. Automatic entries can also be deleted
by the AMO KNTOP.
If the partner node fails to respond repeatedly, it is automatically deleted and
no longer displayed, even if it was originally created with MANAUT.
26.3.4 Diagnostic options

For diagnostic purposes, the option exists of marking a line / B-channel group
with the AMO KNTOP for the automatic reporting procedure. Command example:
STA-KNTOP:PEN=1-2-25-0,BCGR=4;
This only works with CorNet-NQ lines with Segmentation=8, as only these
support the reporting procedure. If the line is marked, an automatic entry is
created for this line in the partner table upon the first successful call via this line
(regardless of whether this involves transit or terminating traffic).
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
The command:
DIS-KNTOP:PEN=1-2-25-1,BCGR=1,FORMAT=START;
Allows you to query whether the line is marked. In this context, it is irrelevant
whether the line was marked manually via AMO or automatically during a polling
procedure.
26.3.5 Regenerate
Only manual entries in the partner table are regenerated with the AMO KNTOP.
If a MANAUT entry has been overwritten by an automatic entry, it is no longer
regenerated. In other words, if you find that the AUT field is checked when
performing a query with KNTOP, it involves an automatic entry that is not
regenerated.
26.3.6 Switching the Tie Trunk Circuits On and Off

When switching off tie trunk circuits (analog or digital), the AMO DSSU
(regardless of the parameter OFFTYPE) leaves the line marking unchanged. In
contrast, when switching on or restarting a tie trunk circuit with the following
properties (regardless of the parameter ONTYPE), the line marking is set for all
configured B-channel groups:
– The tie trunk circuit must be assigned the CorNet-NQ protocol (AMO
TDCSU, parameter PROTVAR))
– The CorNet-NQ protocol must be configured with Segmentation 8 (AMO

TDCSU, parameter SEGMENT)
– The Polling Timer must be configured (AMO ZAND, parameter

NWTOPTIM > 0)
This results in the automatic detection of the partner node being started faster
when the feature is activated.
The AMO TDCSU, which likewise switches circuits off and on, acts in exactly the
same way as described previously for the AMO DSSU.

• Check that sufficient memory is configured for the partner table and adjust it
if necessary. This can be done via the EXEC command, which configures the
standard value on a system-specific basis, or via an ADD command:
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
DIS-DIMSU:TYPE=ALL,PARAM=PARTNODE;
EXEC-DIMSU:FEASET=DEFAULT;
ADD-DIMSU:PARTNODE=100;
• Configure own and partner node access codes in the digit analysis.
Closed numbering scheme:
ADD-WABE:CD=808902,DAR=NETW,CHECK=NO;
ADD-WABE:CD=808903,DAR=NETW,CHECK=NO;
ADD-WABE:CD=808904,DAR=NETW,CHECK=NO;
Or open numbering scheme:
ADD-WABE:CD=808901,DAR=OWNNODE;
ADD-WABE:CD=808902,DAR=TIE,CHECK=NO; 
ADD-WABE:CD=808903,DAR=TIE,CHECK=NO; 
ADD-WABE:CD=808904,DAR=TIE,CHECK=NO;
Configure own physical node number and node access code in the central
system data:
CHA-ZAND:TYPE=ALLDATA,PNNO=10-89-100,PNODECD=808901;
• Check whether the feature is activated and, if necessary, adjust the polling
times:
DIS-ZAND:TYPE=ALLDATA3;
CHA-ZAND:TYPE=ALLDATA3,NWTOPTIM=xx;
(xx > 0, corresponds to polling time in seconds)
• Configuring trunk groups, tie trunk circuits, LCR for open/closed numbering,
etc. To this end, the corresponding FUEs, i.e. "Feature Usage Examples"
(e.g. LCR, number modification...) must be taken into account. Use the
default NWMUXTIM in AMO TDCSU whenever possible. However, in
exceptional cases in which, for example, MUX functionality will never be
required, use the following:
CHA-TDCSU:PEN=1-2-25-1,DEV=S2CONN,BCGR=1,NWMUXTIM=0;
• Configure LCR for the physical node access codes; the important factor here
is that the dial pattern is entered in the LCR for every partner node access
code (check whether it may already have been configured for the path
optimization).
Closed numbering scheme:
ADD-RICHT:MODE=CD,LRTE=400,CD=40,CPS=0,SVC=SPVH,NAME=TO NODE
400, TGRP1=40,DESTNO=40,DNNO=1-89-400,ROUTOPT=YES,PDNNO=10-
89-400;
ADD-LODR:ODR=1,CMD=NPI,NPI=UNKNOWN,TON=UNKNOWN;
ADD-LODR:ODR=1,INFO="CLOSED NUMBERING UNKNOWN";
ADD-
LDAT:LROUTE=400,LSVC=VCE,LVAL=1,TGRP=40,ODR=1,LAUTH=1,CARRIER
=9,ZONE=EMPTY,LATTR=NONE;
Or open numbering scheme:
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
ADD-RICHT:MODE=LRTENEW,LRTE=40O,NAME=TO NODE
400,TGRP=40,DNNO=1-89-400,ROUTOPT=YES,PDNNO=10-89-400;
ADD-LODR:ODR=10,INFO="OPEN NUMBERING";
ADD-
LDAT:LROUTE=400,LSVC=ALL,LVAL=1,TGRP=40,ODR=10,LAUTH=1,CARRIE
R=9, ZONE=EMPTY,LATTR=NONE;
ADD-LDPLN:LDP=808904-T,LROUTE=400,LAUTH=1;
• Initiate manual entries (if necessary) in the partner table:
ADD-KNTOP:PEN=1-2-25-1,BCGR=1,PTNAC=808904,PTNNO=10-89-
400,OVRD=MANONLY;
• Querying the partner table, for example before the MANAUT entry is
overwritten by an automatic entry. For partner node 1-2-200, an automatic
entry has already been realized:
DIS-KNTOP;
Output: (Output mask (long format) of the AMO KNTOP
+-------------------------------------|----------------------------------------+
| OWN NODE | PARTNER NODE |
+-------------------------------------|----------------------------------------+
| NNO: 10- 89-100 NWTOPTIM: 20 SEC | |
| NODECD: 808901 | |
+-------------------------------------|----------------------------------------+
| PEN: 1- 2- 25- 1 BCGR: 1 TGRP: 40 NWMUXTIM: 10 |
| OVRD: AUT : X --> NNO: 10- 89-400 |
| | NODECD: 808904 |
| | PEN: 1- 2- 79- 1 BCGR: |
+-------------------------------------|----------------------------------------+
Figure 14 Output mask (long format) of the AMO KNTOP
• In this example, the original MANAUT entry is overwritten by an automatic

entry after a certain time (e.g. because the partner node was upgraded to
OpenScape 4000). In this case, the output presented in Figure 15, Output
mask of the AMO KNTOP with overwritten MANAUT entry is displayed
(differences are highlighted):
DIS-KNTOP;
Output: (Output mask of the AMO KNTOP with overwritten MANAUT
entry)
+-------------------------------------|----------------------------------------+
| OWN NODE | PARTNER NODE |
+-------------------------------------|----------------------------------------+
| NNO: 10- 89-100 NWTOPTIM: 20 SEC| |
| NODECD: 808901 | |
+-------------------------------------|----------------------------------------+
| PEN: 1- 2- 25- 1 BCGR: 1 TGRP: 40 NWMUXTIM: 10 |
| OVRD: MANONLY AUT : - --> NNO: 10- 89-400 |
| | NODECD: 808904 |
| | PEN: 1- 2- 79- 1 BCGR: |
| OVRD: MANAUT AUT : X --> NNO: 1- 2-300 |
| | NODECD: 7018 |
| | PEN: 1- 2-109-0 BCGR: |
+-------------------------------------|----------------------------------------+
Figure 15 Output mask of the AMO KNTOP with overwritten MANAUT
entry
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
Relevant AMOs
26.5 Relevant AMOs

Language
DIMSU TYP d =NETZ, Zweig für PARTNODE
Konfiguration
TYPE e =NETWORK, branch for PARTNODE
configuration
PARTNODE d max. Anzahl der Partnerknoten
(Nachbarknoten)
PARTNODE e max. number of partner nodes (adjacent
nodes)
DSSU TYP d =LAGE: Aus- und Einschalten bzw. Restart
eines Quersatzes
TYPE e =PEN: Deactivate, Activate or Restart a Tie
Line
LAGE1 d Lage 1 des Quersatzes
PEN1 e Peripheral Equipment Number 1 of a Tie
Line
LAGE2 d Lage 2 des Quersatzes
PEN2 e Peripheral Equipment Number 2 of a Tie
Line
KNTOP LAGE d Lage im eigenen Knoten
PEN e Peripheral Equipment Number in own node
BKGR d B-Kanal-Gruppe im eigenen Knoten
BCGR e B Channel Group in own node
PTKNKZ d Knotenkennzahl des Partnerknotens
PTNAC e Node Access Code of adjacent partner
node
PTKNNR d Knotennummer des Partnerknotens
PTNNO e Node Number (Node Id) of adjacent partner
node
PTLAGE d Lage im Partnerknoten
PTPEN e Peripheral Equipment Number in adjacent
partner node
PTBKGR d B-Kanal-Gruppe im Partnerknoten
PTBCGR e B Channel Group in adjacent partner node
OVRD d Override-Steuerung manuell/automatisch
OVRD e Override control manual / automatic
TYP d Typ des zu löschenden Eintrags
TYPE e Type of entry to be deleted
FORMAT d Ausgabeformat (lang oder kurz)
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
Relevant AMOs

Language
FORMAT e Format of output (long / short)
TDCSU NWMUXTIM d MUX-Timer (Zeitfenster für Partnerknoten,
die über MUX angeschlossen sind)
NWMUXTIM e MUX-Timer (time window for partner nodes
connected via MUX)
PROTVAR d Protokollvariante, z.B. CorNet-NQ
(ECMA1, ECMA1R, ECMAV2, ECMAV2R,
PSS1V2, PSS1V2R)
PROTVAR e Protocol variant , e.g. CorNet-NQ
(ECMA1, ECMA1R, ECMAV2, ECMAV2R,
PSS1V2, PSS1V2R)
SEGMENT d Segmentierung der Layer 3 Meldungen
SEGMENT e Segmentation of Layer 3 messages
WABE RNR d Angabe der Knotenkennzahl
(Knotenrufnummer)
CD e Access Code
KZP d Kennzahlpunkt:
=EIGENKZ: Eigene Knotenkennzahl
einrichten
Diese ist auch mit AMO ZAND, Parameter
PKNOTKZ im eigenen Knoten einzurichten.
= QUER: Querkennzahlen für alle
Partnerknoten
(Nachbarknoten) einrichten.
Dort muss die Knotenkennzahl mit AMO
ZAND,
Parameter PKNOTKZ eingerichtet sein.
DAR e Digit analysis result:
= OWNNODE: Own node acces code
configuration
it has to be configured also by AMO ZAND,
parameter PNODECD
= TIE: Tie line configuration for all adjacent
partner
nodes. At each partner node, the access
code has to be configured by AMO ZAND,
parameter PNODECD
ZAND TYP d Typverweigung:
=DATENALL: Zweig für PKNOTKZ, PKNNR
= DATEN3: Zweig für NWTOPTIM
TYPE e Type branch:
= ALLDATA: Branch for PNODECD, PNNO
= ALLDATA3: Branch for NWTOPTIM
PKNOTKZ d Einstellen der eigenen physikalischen
Knotenkennzahl (Knotenrufnummer)
PNODECD e Configuration of own physical Node Access
Code
A31003-H3170-S103-6-7620, 02/2019
kntop_en.fm
Relevant AMOs

Language
PKNNR d Einstellen der eigenen physikalischen
Knotennummer
PNNO e Configuration of own physical Node
Number (Node Id)
NWTOPTIM d Polling Timer für das Update der
Partnertabelle
NWTOPTIM e Polling Timer for updating the Partner Table
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Cornet NQ Interworking with DPNSS1
Feature Description
27 Cornet NQ Interworking with DPNSS1

With the feature Cornet NQ interworking with DPNSS1 the gateway board is
integrated in OpenScape 4000 Loading, Administration and Dependability
concept.
The peripheral board serves as a protocol gateway between Cornet NQ

(OpenScape 4000 internal protocol) and DPNSS1 protocol (private network
protocol in UK; ISDX; ’Realitis’ migration). It works also in transit networks
between OpenScape 4000 switches with DPNSS1 switches as transit nodes.
The board loadware translates the CornetN/Cornet NQ protocol into DPNSS1

and vice versa or hides the CornetN/Cornet NQ protocol in DPNSS1 frames for
transit function and vice versa (tunneling function). The board also supports
conversion of Cornet N into DASS2 protocol for use as a central office interface
in the UK .
Realitis/DX ISPBX
DPNSS1 with Cornet/NQ protocol

"tunnelled" within DPNSS frames
User to user features of Cornet N/NQ between

OpenScape 4000 users in mixed vendor
networks using
PBXXX and DPNSS1 protocol including
segmented Cornet messages and Cornet NQ
connection transport service.
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Application Field of PBXXX
27.2 Application Field of PBXXX

The PBXXX gateway module is used to link the OpenScape 4000 system to
private systems and networks via DPNSS1 or public exchanges via DASS2. With
PBXXX it is possible to link the OpenScape 4000 system with:
• iSLX, iSDX, EMS 601 or other DPNSS based PBX systems via DPNSS1
protocol or
• public exchanges via DASS2 protocol
• other PABX systems via DPNSS1 protocol if certificated.
DPNSS1 (Digital Private Network Signaling System No. 1) is a British Telecom

(BT) standard private network protocol used on many PBX systems, mostly in the
UK, although it is also supported in many other countries. The DPNSS1
specification is a published standard in the United Kingdom.
IMPORTANT: Most DPNSS1 implementations of the various PBX vendors are a

subset of the global DPNSS specification (BTNR188). Cooperation with other
vendor PBXs must be tested first.
DASS2 (Digital Access Signaling System No 2) describes the standard interfaces

of the British ISDN access.
27.3 PBXXX Board

CorNet -N/NQ-DPNSS1 Gateway allows one of the following functions:
• connection to other PBXs supporting the DPNSS1 protocol
• connection to DPNSS based Voice Mail Systems
• connection to the public network supporting the DASS2 protocol
• transparent transmission supporting the CorNet-NQ/CorNet N protocol/QSIG

protocol (e.g. Tunnelling of signalling messages)
The feature is available in the following configurations:
27.3.1 Partial Integration Ring Generator

• The board board is configured like a Ring Generator (RG) and is plugged in
a peripheral slot of the OpenScape 4000. It only gets power from the
OpenScape 4000 switch. No direct signalling and administration is
supported.
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
PBXXX Board
• The connection to OpenScape 4000 is done via a separate DIUS2 board.
• In this configuration the board is loaded and administrated via V.24 interface
from a separate PC (CDGM-Tool).
• This configuration only uses one circuit of the PBXXX i.e. 30 B channels
external clock signal path
Backplane
circuit 1
Link 1
DIU-S2
OpenScape 4000 CorNet N/NQ
Link 2
Connection made to one of
the available DIU-S2 ports
circuit 2
clock source CorNet N/NQ
PBXXX Cables are connected via

plugs on the backplane
Link 2
clock sync DPNSS / DASS
Link 1
V24 P.C. with CDGM
Figure 16 PBXXX - Partial-integration-RG
27.3.2 Partial Integration DIUS2

• The board is configured like a DIUS2 board and is plugged in a peripheral slot
of the OpenScape 4000.
• The board is connected directly to the OpenScape 4000 backplane and

supports the DIUS2 message interface.
• But the board is still loaded and configured via V.24 interface from a separate
PC (CDGM-Tool).
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
PBXXX Board
OpenScape 4000
DPNSS / DASS Cables
circuit 1
Link 1 connected by
Backplane
CorNet N/NQ DPNSS / DASS plugs on the
Link 2 backplane
circuit 2
clock source
clock sync
PBXXX
P.C. with CDGM
V24
connected to front
of the card
Figure 17 PBXXX - Partial-integration-DIUS2
27.3.3 Full-integration Solution

• The board is configured and is plugged in a peripheral slot of the OpenScape
4000.
• The board is connected directly to the OpenScape 4000 backplane and

supports the DIUS2 message interface. Additionally, interfaces for loading,
administration and debugging are added.
• The loading and administration process is now supported via OpenScape

4000. No separate PC is necessary any longer. The exception to this is in the
initial configuration of the board when software known as the Eprom Extender
has to be loaded into the board .
Also it is possible to connect the PC via V.24 to the board for special
debugging purposes (this is limited to product specialists)
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Feature Characteristics
OpenScape 4000
DPNSS / DASS Cables
circuit 1
Link 1 connected by
Backplane
CorNet N/NQ DPNSS / DASS plugs on the
Link 2 backplane
circuit 2
clock source
clock sync
PBXXX P.C. with CDGM
V24
Figure 18 PBXXX - Full-integration

• Changes in the configuration data made by AMO LWPAR and AMO TDCSU
will become only effective on the board after switching off/on the concerned
unit. This will cause loading the new configuration data to the board:
• Switch off/on circuits with AMO DSSU:

Concerned Parameters in AMO LWPAR are signed as ’C’ (’Circuit’).
• Switch off/on board with AMO BSSU:

Concerned Parameters in AMO LWPAR are signed as ’R’ (’Restart the
board’) or ’B’ (’Board’). Also the parameters which can only be changed by
AMO TDCSU are listed here within the LWPAR block]
• A maximum of 50 loadware parameter blocks (LWPAR blocks) are available

for PBXXX These data can be changed by AMO LWPAR per block.
B-channel negotiation:
• B Channel negotiation is set on the board. The PBXXX will use the channel
requested by the OpenScape 4000 or DPNSS/DASS circuit involved. If this
is not available due to collision or faults then the call setup is rejected with the
appropriate cause .On the DPNSS side the channels are configured as X or
Y. The Y channell will back off in the case of call collision.The distant end must
have the B channel set to the opposite value as is normall for DPNSS. To the
OpenScape 4000 the PBXXX in the case of call collision sends a message
with "required circuit not available", the OpenScape 4000 then can select
another B channel or not.Please pay attention to the COT parameter BCNE
and TDCSU parameter CCHDL for the OpenScape 4000 trunk as these
affect the way OpenScape 4000 handles B channel negotiation.
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
• In this way trunk groups and sub equipped configurations will function
correctly on both sides of the PBXXX.The restriction here is that the same
channels must be configured on either side e.g. if only DPNSS channels 1-10
are configured for use then OpenScape 4000 (Cornet N/NQ ) channels 1-10
only must be configured.
Reference clock:
• ’Partial-integration-RG’ solution:
The OpenScape 4000 switch gets the reference clock over the backplane
from the separate DIUS2 board and not directly from the board. The separate
DIUS2 circuit therefore must not be configured as ’connected with PBXXX’.
• ’Partial-integration-DIUS2’ solution:
directly from the PBXXX board.
• ’Full-integration’solution:
directly from the PBXXX board. In this situation the PBXXX circuit must be
configured (via the CDGM tool) to retrieve the clock from the external
DPNSS/DASS2 circuit.
• Command interface AMO LWCMD:

With the ’Full-integration’ solution the new AMO LWCMD (LoadWare
CoMmanD) is available which supports a command interface between
OpenScape 4000 service terminal and PBXXX board.
With AMO LWCMD service personnel are able to send ASCII-command
strings to the PBXXX board loadware and to receive ASCII-strings on the
service terminal display.
This command interface is developed for PBXXX system specialists (e.g. for
debugging , for detailed fault diagnosis and for statistics).
It is not service relevant.
The AMO LWCMD therefore gets the AMO password class 3 (product
specialist).
• AMO LWPAR has a branch, TYPE=CDG this allows the feature of the
PBXXX to be configured in the fully integrated solution.
• The CDGM tool is to be used for the partialy integrated solutions.It is also
used for upgrading the extender and loadware for partial integration solutions
or just the extender software in the fully integrated solution. In all cases it can
be used to monitor configuration data and other items such as link status.
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Configuration
27.5 Configuration
Configuration and maintenance can be done via the tool OpenScape 4000 Expert
Access and Hicom One Tool (only possible in the fully integrated option) and/or
via the V24 interface.
Additionally “Execute Commands” can be sent from OpenScape 4000 service

terminal (V24 interface) to the board, also when the board is accessible by
OpenScape 4000. By means of execute commands special data can be sent to
board (AMO LWCMD )
27.5.1 Software and Data Base Loading (Flash

Loading Concept)
The software loading is done by the EPROM extender program. The EPROM
extender program is factory-preloaded, but can be reloaded on site by means of
the CDGM program.
When PBXXX is powered-up or restarted, the bootstrap EPROM checks if the

EPROM extender program on the board is still present. When no extender is
available, the PBXXX will wait for the CDGM program to download the extender.
In the PBXXX flash memory, an area is available where some miscellaneous data
can be saved. One item (LW-source) will indicate from where the PBXXX will get
the loadware and database : from OpenScape 4000 AMO or CDGM. If this flash
area is not initialized, OpenScape 4000 will be assumed as default source.
(Therefore the board will default to load from the OpenScape 4000 unless it has
been configured as a partial integration board, in which case it can only be loaded
via the CDGM tool)
• LW-source = OpenScape 4000

PBXXX will first activate the backplane communication and waits for a
message from OpenScape 4000. Software and database are loaded from
OpenScape 4000. On receipt of the configuration data, PBXXX will create all
the necessary software components to handle calls. Configuration data will
be saved in flash.
• LW-source =CDGM
download software and database via V.24 port (using CDGM tool). 
In this case the PBXXX will check whether it has a valid database or loadware
stored in the flash RAM. If so, the PBXXX loads the database/loadware from
flash which results in the creation of all the software components that are
necessary to handle calls. If no database/loadware is available in flash, the
PBXXX will wait for a database/loadware download from the CDGM tool.
Configuration data received from the OpenScape 4000 will be ignored.
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Configuration
The EPROM extender program will first read this ‘LW-source’ parameter from
flash. Via the CDGM tool the PBXXX will allow to change this parameter for a
period of max 10 secs (this waiting period will be skipped in case no terminal or
modem is connected to the PBXXX board in order to speed-up the start-up time).
If nothing is entered, the indication from Flash (or default) is used as LW-source.
A LW-source update received from CDGM will be saved in flash and used
afterwards.
27.5.2 PBXXX Partial Integration RG

The CDGM tool is required for PBXXX configuration and debugging. The CDGM
PC also provides the loadware for the PBXXX and is used to upgrade the
extender. The PBXXX board will receive all the configuration data and
maintenance commands via the V24 port.
27.5.3 PBXXX Partial Integration (DIU-S2-Emulation)

This is a configuration of PBXXX, where the PBXXX takes power from the
backplane. In addition the PBXXX can receive a reference clock from the
OpenScape 4000 backplane, or supply a reference clock to the OpenScape 4000
backplane.
In this case the PBXXX emulates the DIU-S2 functionality: It looks like a DIU-S2
to the OpenScape 4000 and communicates with the OpenScape 4000
backplane’s D-channel signalling highway using layer 3 CorNet-N/NQ messages.
In addition maintenance messages are passed between the PBXXX and the
OpenScape 4000 backplane.
The CDGM tool is required for PBXXX configuration and debugging.The CDGM
PC also provides the loadware for the PBXXX. The PBXXX board will receive all
the configuration data and maintenance commands via the V24 port.
Features:
• PBXXX will always synchronize on the PCM clock from the OpenScape 4000
backplane. Additionally, the PBXXX will be able to provide OpenScape 4000
with the clocksources derived from the incoming data stream from the
DPNSS1 or DASS links. These clocksources can be switched on and off
under OpenScape 4000 control by means of DIU-S2 backplane messages.
• Between B channels on the Network side (DPNSS/DASS) a fixed relationship

exists (see B channel negotiation). Timeslot connections are made on a per
call basis, however no physical connection will be established until
OpenScape 4000 assigns a timeslots on the backplane for the selected B-
channel.
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Configuration
27.5.4 PBXXX Full Integration

This product configuration is characterized by the following:
• The PBXXX takes power from the backplane.
• The PBXXX can receive a reference clock from the OpenScape 4000
backplane, or supply a reference clock to the OpenScape 4000 backplane.
• The PBXXX emulates the DIU-S2.
• The PBXXX loadware resides on the OpenScape 4000 and is loaded on to

the card automatically on startup if loadware in the OpenScape 4000 is found
to be different to that on the board
• Configuration for the PBXXX is done using AMOs on the OpenScape 4000.
PBXXX configuration is stored on the OpenScape 4000 database.
• Limited PBXXX debugging can also be done by AMO.
• The option of using a separate CDGM tool for PBXXX debug/ tracing is still
available.
• Administation and maintenance of the PBXXX can either be done by AMO or

by using the CDGM tool. But can not be done by AMO and the CDGM tool in
parallel or at the same time.
Within the PBXXX loadware it is configurable (via execute commands sent
with AMO or via CDGM) which internal errors are sent to the OpenScape
4000
In the fully integrated option, the PBXXX board will receive the configuration data
from OpenScape 4000 directly on start-up. During start-up, each equipped circuit
on the PBXXX will receive from OpenScape 4000 a message containing a
datablock with configuration parameters. These PBXXX specific parameters are
configured by OpenScape 4000 using different AMO commands (AMO LWPAR/
AMO TDCSU).
Changing configuration data on the PBXXX board via the V.24 interface while the
board is in the ‘full integration configuration’ leads to inconsistent OpenScape
4000 Database for PBXXX.
Therefore this manipulation is not allowed in normal operation but only for
diagnostics purposes (executed by system specialists).
Features:
• PBXXX will always synchronise on the PCM clock from the OpenScape 4000
backplane. Additionally, the PBXXX will be able to provide OpenScape 4000
with the clock sources derived from the incoming data stream from the
DPNSS1 or DASS links. These clock sources can be switched on and off
under OpenScape 4000 control by means of DIU-S2 backplane messages.
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Administration/Maintenance
• Between B channels on the Network side (DPNSS/DASS) a fixed relationship

exists (see B channel negotiation). Timeslot connections are made on a per
call basis, however no physical connection will be established until
OpenScape 4000 assigns a timeslots on the backplane for the selected B-
channel.
• Circuit 0 or 1 appear in the REFTA table as possible clock sources.
27.6 Administration/Maintenance
The administration and maintenance possibilities depend on the PBXXX
configuration mode. For the fully integrated option, administration and
maintenance can be done in the same way as the OpenScape 4000
administration, via the OpenScape 4000 Expert Access and Hicom One Tool.
Additionally the CDGM tool can be used for maintenance functions via the V24
port.
For partial integration modes administration and maintenance can only be done
using the CDGM. Additionally using AMO LWCMD (EXEC-LWCMD) “Execute
Commands” can be sent from OpenScape 4000 service terminal to a fully
integrated board ,these allow:
• Trace activate/deactivate commands (Trace results are received via DH and

AMO TRACS)
• Dump activate commands
• Other commands (e.g. alarm selection)
Results from execute Commands are displayed on OpenScape 4000 service

terminal:
• Dump result data
• Error and alarm information stored in LW buffers
• Aknowledges (e.g. “OK”)

• No transmission of node number from ISDX / Realitis System.
COT Parameter LOKN has to be set to the DIUS2 and a node number has to
be given to the trunk in AMO TDCSU.
• No transmission of LBER from ISDX / Realitis System.
• COT Parameter OLCR/OLCRD has to be set to the DIUS2.
• A COS have to be assigned to the DIUS2.
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
AMO Information
• The CORNV33 protocoll can be used for DPNSS1 and DASS.
• Sychronisation of the OpenScape 4000 is possible via the PBXXX.
27.8 AMO Information

AMO LWPAR
A branch of AMO LWPAR is available to deal with the full integration configuration
of PBXXX, PBXXX.(The partial integration configurations still use the existing
DIUS2 branch of the AMO) On initialistaion of the database data blocks are
created with default values and therefore there is no ADD function for the amo.To
reset a LWPAR block to default a DEL function exists.When changing parameters
two sub branches of the AMO exist under the parameter CDGTYPE, these are
CONF and TIMER. these are displayed together in the display branch of the AMO
as below.
+---------------------------------------------------------------------+
| LOADWARE PARAMETERS CIRCUIT TYPE: CDG SOURCE:DB BLOCK: 0 |
+---------------------------------------------------------------------+
| [R]UNWD = DPACN [R]PATTERN = 213 |
| [C]BCHNEG = Y [C]CRC4C = N [C]CRC4REP = N |
| [C]TEMPSIG= Y [C]NSITR = Y [C]NSIOUT = Y |
| [C]CDGCF = Y [C]CONVBN = N [C]TIDOP = Y |
| [C]C3CONF = Y [C]CONACK = Y [B]LSCF = N |
| [C]NSIMSGS= 150 [C]SADRTM = NSAP [C]MAXTMS = 500 |
| [C]RESTLNK= Y [C]RESTALL = Y |
| [C]AROB = N [C]SCCONF = N [C]ATCPN = 11 |
| [C]ICPN = 12 [C]APCPN = 13 [C]DASSCPN = 14 |
| [C]T301 = 180 SEC [C]T302 = 10 SEC [C]T303 = 4 SEC |
| [C]TBID = 5 SEC [C]TDPNSSC = 500 MSEC [C]TROPTBR = 10 SEC |
| [C]TWEOS = 60 SEC [C]TAMOST = 60 [C]TROPTNR = 30 SEC |
| [C]DEFID = B010 [C]TSABMR = 200 MSEC [C]TAROB = 10 SEC |
| [R]PROT = DPNSS [C]VMSYSTAD = 0 |
| [R]BCHKONF = 16&&30 |
| [R]EQVIRC = 1&&30 |
| [R]VCHCONF = 16&&30 |
| RES3 = 0 RES4 = 0 RES5 = 0 |
| DEV = INDEP TIPL = 10 IPLDS = A |
| LCOSMAP(Y=ENABLED,N=DISABLED) = N DEFPASSW = 9999 |
| INFO = |
+---------------------------------------------------------------------+
| DEFC: CIRCUIT SPECIFIC DATA WITHOUT BOARD LEVEL SWITCHING |
| (CIRCUIT LEVEL SWITCHING BY AMO-DSSU NEVERTHELESS REQUIRED) |
| DEFR: CIRCUIT SPECIFIC DATA WITH BOARD LEVEL SWITCHING |
| (PLUS CIRCUIT LEVEL SWITCHING BY AMO-DSSU REQUIRED) |
| DEFB: BOARD SPECIFIC DATA |
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
AMO Information
| (BOARD LEVEL SWITCHING REQUIRED) |

+---------------------------------------------------------------------+
AMO-LWPAR-218 LOADWARE PARAMETERS FOR NETWORKING MODULES
DISPLAY COMPLETED;
<
The explanations of DEFC DEFR and DEFB refer to the functions which must be
restarted following a change of the parameter.This is indicated by the letter in
parenthisis adjacent to the parameter
The parameters in the block are defined as follows:

TYPE=CDG
Parameter Initialization/default Definition/Options

The following are in the branch CDGTYPE = CONF
Idle code (PATTERN) 213 (D5H) BYTE in decimal
User Network Definition (UNWD)  
DPACN DPNSS A Cornet Network DPACN DPACN 
DPACU DPNSS A Cornet User DPACU
DPBCN DPNSS B Cornet Network DPBCN
DPBCU DPNSS B Cornet User DPBCU
Protocol (PROT) DPNSS DPNSS
DASS
Equipped B channels - BitMap All equiped Bitmap, 1 = equiped.
DPNSS X/Y B-Channels (BCHCONF) 16-30 Channels configured
here are those
channels that are
required to be set as
Y, those not entered
are automatically
configured as X
ie 1-15 X, 16-30 Y
DPNSS virtual channels (EQVIRC) 30 can sub equip
DPNSS X/Y virtual channels (VCHCONF) 16-30 Channels configured

here are those
channels that are
required to be set as
Y, those not entered
are automatically
configured as X
ie 1-15 X, 16-30 Y
Msg size NSI to non NSI (NSIMSGS) 300 RANGE (100:2048)
DASS-CORNET subaddress NPI NSAP (=0) can have user
(SADRTM) specified
DPNSS transit msg size max (MAXTMS) 500 RANGE (0-2048)
CORNET: Restart link at startup YES YES/NO
(RESTLNK)
Table 3 LWPAR block initialization values
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
AMO Information

DPNSS/DASS:Restart LAPs at startup YES YES/NO
(RESTALL)
CORNET-N(Q): B-Channel negotiation YES YES/NO
(BCHNEG)
CORNET-N(Q): CRC4 (CRC4C) NO YES/NO
DPNSS/DASS: CRC4 (CRC4REP) NO YES/NO
Temporary signaling connection YES YES/NO
(TEMPSIG)
NSI CORNET-NQ transit (NSITR) YES YES/NO
Insert NSI DPNSS outgoing (NSIOUT) YES YES/NO
PBXXX transit working on Call Forward YES YES/NO

(CDGCF)
Conversion back Notify from CORNET-N NO This should be yes
(CONVBN) when connected to
Realitis/DX
DPNSS trunk identity option (TIDOP) NO YES/NO
3-party conference (C3CONF) YES YES/NO
Connect Ack sent by Protocol Han YES YES/NO
dler (CONACK)
Loadware saved compressed in  NO YES/NO
Flash (LSCF)
ROP,Default call id length when used with B001 B001=1 digit,
Cornet NQ (DEFID) B010=2 digits,
B011= 3digits and
B100= 4 digits
Dass operator number (DASSOPN) 0 digit string
Kind of device on trunk (DEV) CDGCOD
CDGCONN
Service information (INFO) Max. of 50 positions
COS mapping. (LCOSMAP) NO YES(enabled)/
NO(disabled)
Diversion Activation/Deactivation default 9999 0 to 6 digits.
password (DEFPASSW) ‘Digit values 0 to 9
The following are in the branch CDGTYPE = CONF2
Analogue trunk call priority(ATPCN) 12 1 - 16
Internal call priority (ICPN) 11 1 - 16
Analogue PSTN (APCPN) 14 1 - 16
DASS call priority (DASSCPN) 13 1 - 16
AROB mapping enabled(AROB) NO YES/NO
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
AMO Information

Station controlled conference enabled NO YES/NO
(SCCONF)
Voicemail system address (VMSYSTAD) Empty - digit length = digit string
0
The following are in the branch CDGTYPE = TIMER
Callback interdigit timer (TBID) 5 seconds (= WORD
0x4005)
ROPT release timer both end(TROPTBR) 10 seconds (= WORD
0x400A)
ROPT release timer neither end release 30 seconds (= WORD
(TROPTNR) 0x401E)
DPNSS collision timer (TDPNSSC) 500 msec (= 0x0005) WORD
Timer wait for EOS from CORNET 60 seconds (= WORD
(TWEOS) 0x403C)
DPNSS SABMR retransmission timer 0 seconds (=0x4000) WORD
(TSABMR)
T301 timer 180 seconds WORD
(=0x40B4)
(=0x400A)
T303 timer 4 seconds (=0x4004) WORD
(=0x400F)
(=0x401E)
(=0x405A)
(=0x400A)
(=0x4078)
AMO supervise timer (TAMOST) 60 seconds (= WORD
0x403C)
IPL timer (TIPL) 10 seconds WORD
Intrusion level (IPLDS) A A = Allowed
NA = Not-allowed
AROB timer (TAROB) 10 seconds WORD
Reserved 3 0 WORD
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm

Reserved 4 0 WORD
Reserved 5 0 WORD
The following are in the branch CDGTYPE = MAPPING
Conversion between OpenScape 4000 DXTGPOS (0 - 31)
ITR and Realitis trunk group number (TBL
= DXTGITR)
Conversion between OpenScape 4000 TRG (0 - 15)
ITR and Realitis call barring group (TBL = CBG (0 - 127)
TRGCBG)
Conversion between OpenScape 4000 LCOS (1 - 32)
LCOSD and TAC value in DPNSS1 (TBL RRG (0 - 127)
= LCOSDRRG)
Conversion between OpenScape 4000 LCOS (1 - 32)
LCOSV and TAC value in DPNSS1 (TBL RRG (0 - 127)
= LCOSVRRG)
27.9.1 Configuration of ’Partial-integration-RG’

solution
• Configuration of ’Partial-integration-RG’ solution
• Configuration of DIUS2
The DIUS2 is configured identical to other DIUS2 in system (e.g. for
CORNET-NQ networks). The DIUS2-Loadware need not be informed by
AMO LWPAR, that a PBXXX is connected to it. The OpenScape 4000 switch
gets the reference clock directly from the DIUS2. Therefore if PBXXX is
connected to a DIUS2, the LWPAR-Parameter CDG=NO has to be configured
for the DIUS2.
AMO commands (applicable to an empty Database, important commands are
shown bold):
Please pay attention to the functional id of the PBXXX
• Configuration of the PBXXX board as ’Ring Generator’:

ADD-BCSU:MTYPE=RG,LTG=1,LTU=1,SLOT=67,PARTNO="Q6401-
X",FCTID=1;
• DIMSU configuration for DIUS2 (all dimsu needed for DIUS2)
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
ADD-DIMSU:TYPE=ADMCC,CCIDXS=2000;
ADD-DIMSU:TYPE=BASIC,LODEN=2000,PRI=20,TRK=100,SG=100,
NWBCHL=600,CRCP=50,DPLNCD=800,....; 
ADD-DIMSU:TYPE=SYSTEM,PERMDL=100,..;
• Configuration fo LTG, LTU and DIUS2
ADD-UCSU:UNIT=LTG,LTG=1,SIPARTNO="Q2234-X "; 
ADD-UCSU:UNIT=LTU,LTG=1,LTU=1,LTPARTNO="Q2248-X"; 
ADD-BCSU:MTYPE=DIU,LTG=1,LTU=1,SLOT=61,PARTNO="Q2096-
X200", LWVAR=0;
• Basic configuration of LCR
ADD-WABE:CD=16,DAR=TIE;
CHANGE-ZAND:TYPE=ALLDATA,NNO=100,NODECD=19;
ADD-COP:COPNO=5;
ADD-COT:COTNO=20;
ADD-BUEND:NO=30,TGRP=23,NAME="QV-DPNSS1";
CHANGE-LWPAR:TYPE=DIUS2,BLNO=2,CDG=N; /* CDG MUST BE SET
TO "NO" */
• Configuration of trunk (use a proper LCOSS and LCOSD to get the
necerssary access and a node number )
ADD-TDCSU:OPT=NEW,PEN=1-1-061-00,BCGR=1,CCT="CDG-
DPNSS1",COTNO=20,COPNO=5,LCOSV=1,LCOSD=1,PROTVAR=ECMAV2,DE
V=S2CONN, TGRP=23,LWPAR=2;
CHANGE-REFTA:TYPE=CIRCUIT,PEN=1-1-061-00,PRI=80;
OpenScape 4000 can accept the clock from DPNSS1 (depending on prio
and error counters)
And if the circuit is configured through CDGM to retrieve th clock from
DPNSS/DASS
OR
OpenScape 4000 does not accept clock from DPNSS-Network but
delivers it (PRIO=0) (for details see also Section 47.5.6, “Network Clock
Supply”).
OpenScape 4000 should always accept the clock from a DASS circuit
and never deliver it.
27.9.2 Configuration of ’Partial-integration-DIUS2’

• Configuration of ’Partial-integration-DIUS2’ solution
• Configuration of the PBXXX board as ’DIUS2’ AMO commands (applicable

to an empty Database, important commands are shown bold):
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
ADD-DIMSU:TYPE=SYSTEM,PERMDL=100,..;
• Configuration fo LTG, LTU and DIUS2
ADD-UCSU:UNIT=LTG,LTG=1,SIPARTNO="Q2234-X "; 
ADD-UCSU:UNIT=LTU,LTG=1,LTU=1,LTPARTNO="Q2248-X"; 
ADD-BCSU:MTYPE=PER,LTG=1,LTU=1,SLOT=67,PARTNO="Q6401-
X",FCTID=2;
ADD-COP:COPNO=5;
ADD-BUEND:NO=30,TGRP=23,NAME="CDG-DPNSS1";
• Configuration of trunk (use a proper LCOSS and LCOSD to get the
ADD-TDCSU:OPT=NEW,PEN=1-1-067-00,BCGR=1,CCT="CDG-DPNSS1",
COTNO=20,COPNO=5,LCOSV=1,LCOSD=1,PROTVAR=ECMAV2,DEV=S2CONN
, (or S2COD ),TGRP=23,LWPAR=2;
CHANGE-REFTA:TYPE=CIRCUIT,PEN=1-1-067-00,PRI=80;
and error counters)
And if the circuit is configured through CDGM to retrieve the clock from
DPNSS/DASS
OR
OpenScape 4000 does not accept clock from DPNSS-Network but
delivers it (PRIO=0) (for details see also Section 47.5.6, “Network Clock
Supply”).
27.9.3 Configuration of ’Full-integration’ solution

• Configuration of ’Full-integration’ solution
Configuration Sequence (example for empty Database, important commands
are shown bold)

ADD-DIMSU:TYPE=SYSTEM,PERMDL=100,..;
ADD-UCSU:UNIT=LTG,LTG=1,SIPARTNO="Q2234-X ";
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
ADD-UCSU:UNIT=LTU,LTG=1,LTU=1,LTPARTNO="Q2248-X"; /
ADD-BCSU:MTYPE=PER,LTG=1,LTU=1,SLOT=67,PARTNO="Q6401-
X",FCTID=3;
ADD-COP:COPNO=5;
ADD-BUEND:NO=30,TGRP=23,NAME="QV-DPNSS1";
• Configuration of tie trunk (use a proper LCOSS and LCOSD to get the
COTNO=20,COPNO=5,LCOSV=1,LCOSD=1,PROTVAR=ECMAV2 or CORNV33
(see service information),DEV=CDGCONN,TGRP=23, LWPAR=29;
• Configuration of central office trunk (use a proper LCOSS and LCOSD
to get the necessary access and a node number )
COTNO=20,COPNO=5,LCOSV=1,LCOSD=1,PROTVAR=CORNV33 (see
service information,DEV=CDGCOD,TGRP=23, LWPAR=29;
CHANGE-REFTA:TYPE=CIRCUIT,PEN=1-1-067-00,PRI=80
and error counters)
OR
CHANGE-REFTA:TYPE=CIRCUIT,PEN=1-1-067-00,PRI=0
• OpenScape 4000 does not accept clock from DPNSS-Network but
delivers it (PRIO=0)
(for details see also PN Service Manual, chapter Networking, section
Clock Supply)
• If less than 30 B-Channels have to be configured (Example: B-Channel 1

to 8):
commands see above, replace TDCSU command by :
COTNO=20,BCHAN=1&&8,COPNO=5,LCOSV=1,LCOSD=1,PROTVAR=ECMAV2
or CORNV33 (see service
information),DEV=CDGCONN,TGRP=23,LWPAR=29;
• If Loadware Parameters differ from standard initialization:
CHANGE-
LWPAR:TYPE=CDG,BLNO=29,CDGTYPE=CONF,PROT=DACORN,...;
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
description of all 55 loadware parameters can be found in the AMO

description part of the service manual.
IMPORTANT: The changed LWPAR values are not transferred immediately

to the board. This happens if the board / circuit is switched off / on. The user
is informed by an advisory message.
• Transmit changed LWPAR values to the LW (according to advisory message

of AMO LWPAR):
• If board specific data have been changed:

RESTART-BSSU:LTG=1,LTU=1,SLOT=67;
• If circuit specific data have been changed (according to advisory
message of AMO LWPAR):
• If another loadware block is to be assigned to a TDCSU circuit (e.g.
replace block 29 by block 15). Note that new LWPAR values are
transferred to LW only if a restart is initiated:
CHANGE-TDCSU:PEN=1-1-067-00,DEV=CDGCONN,BCGR=1,LWPAR=15;
• Handling of B-Channel negotiation
CHANGE-TDCSU:PEN=1-1-67-0,DEV=CDGCONN,BCGR=1,BCNEG=Y;
CHANGE-LWPAR:TYPE=CDG,BLNO=29,CDGTYPE=CONF,BCHNEG=Y;
BCHNEG=Y is the default setting. With this configuration the OpenScape
4000 takes over the proposed B channel in case of a collision/fault. This is
the recommended configuration!
However the B channel negotiation will be fixed on the PBXXX so that it is not
possible to perform a B channel negotiation between OpenScape 4000 and
PBXXX. Is a B channel in OpenScape 4000 available the connection will be
established. Is no B channel available the connection will be rejected.
CHANGE-TDCSU:PEN=1-1-67-0,DEV=CDG,BCGR=1,BCNEG=N;
BCHNEG=N cause the OpenScape 4000 to release the call in any case of
call collision independant of LWPAR settings.
CHANGE-TDCSU:PEN=1-1-67-0,DEV=CDGCONN,BCGR=1,BCNEG=Y;
BCHNEG=Y is the default setting. This setting means that the PBXXX does
not select any new B channel in the case of a collision. The PBXXXPBXXX
initiates the call.
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
27.9.4 Usage of AMO LWCMD command interface:

The AMO LWCMD can be used to send so called ’EXECUTE’ commands to the
loadware and display the response data (e.g. dump data) at the OpenScape 4000
service terminal. The ’EXECUTE’ commands are described in a separate
document.
EXEC-LWCMD:LTU=1,SLOT=67,TYPE=CDG,CMD="... here enter EXECUTE
cmd ...",TIMER=30;
The AMO supervise timer is set in this example to 30 seconds.
The EXECUTE command is passed transparently to LW and if it is coupled with
response data, data are displayed in ASCII format.
27.9.5 COP for PBXXX

ADD-COP:COPNO=110,PAR=EOD&SACK&RLSB&RLSA&SPTR&TIM3&ASEG;
27.9.6 Protocol changes for PBXXX to activate the

ASEG COP-parameter
CHA-
PRODE:KIND=PD,PDNAME=PD14,SEC=WELMAND,SETNO=14,B10=40,B30=40;
CHA-
PRODE:KIND=PD,PDNAME=PD14,SEC=WELMAND,SETNO=46,B10=42,B30=42;
CHA-PRODE:KIND=PD,PDNAME=PD14,SEC=WELNAME,CS=00,NO=13,B00=06;
CHA-PRODE:KIND=PD,PDNAME=PD14,SEC=RESTP,PDBLK=WELHEX,NO=12,
B00=0D;
CHA-PRODE:PD,PD14,ORG,,Y;
27.9.7 COT Parameter for full integrated PBXXX

ADD-
COT:COTNO=110,PAR=RCL&XFER&ANS&KNOR&CEBC&TIE&CBBN&CBFN&FNAN&BLOC
&LWNC&ATRS&ITRC&ROPT&NLCR&CECO&TSCS&DFNN&CFOS&CFBU&CFVA&NLRD&PIN
R&CFRM&ASTN&NTON;
27.9.8 Changes of standard LWPAR

For A-side
CHANGE-
LWPAR:TYPE=CDG,BLNO=1,CDGTYPE=CONF,PROT=DPNSS,BCHCONF=1&&15,EQVI
RC=1&&30;
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
For B-side
CHANGE-
LWPAR:TYPE=CDG,BLNO=2,CDGTYPE=CONF,UNWD=DPBCN,PROT=DPNSS,EQVIRC=
1&&30,VCHCONF=1&&15;
27.9.9 Remote registration of diversion

The ‘Default DPNSS Password is configured in the PBXXX using AMO LWPAR.
The default value for this parameter is = 9999 , which is the value usually
configured in Realitis DX systems. To change the value of this parameter use the
following ( for example to set the default = 1234) :
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=CONF,DEFPASSW=1234
27.9.10 Class of Service Configuration

The Class of Service interworking implemented by the Enhanced CDG feature
converts between the following values in OpenScape 4000 and Realitis DX;
OpenScape DPNSS Note

4000
LCOS RRC In OpenScape 4000 LCOS is 2 parameters
LCOSV for Voice calls
LCOSD for Data calls
This is known as TAC in Realitis DX
ITR CBG where the originator or terminator is an extension terminal
(ITR group is also know as VBZGR in OpenScape 4000)
ITR Trunk Group where the originator or terminator is a trunk
The values used by the OpenScape 4000 and Realitis DX for these parameters
do not have the same range, and to facilitate integration of OpenScape 4000 and
Realitis DX switches in mixed networks the Enhanced CDG feature provides
mapping tables for these parameters to convert between the OpenScape 4000
and DPNSS1 values.
Class of Service Parameters:

LCOSMAP: this parameter is used to enable or disable the mapping of all the
parameters in the table following. The default value is ‘enabled’ and is configured
using AMO LWPAR:
To enable Class of Service Mapping

CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=CONF,LCOSMAP=Y
To disable Class of Service Mapping
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=CONF,LCOSMAP=N
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
LCOSVRRG and LCOSDRRG Tables: These tables convert between the LCOSV
and LCOSD in OpenScape 4000 and the RRC (TAC) value in DPNSS1. There
are separate tables for LCOSV and LCOSD and the table format for each is
shown in Table 4. Each table is Indexed using the OpenScape 4000 LCOS value.
The table is setup with default values with the DPNSS1 RRC having the same
value as the OpenScape 4000 LCOS - this is shown in :Table 4 (note that the
OpenScape 4000 LCOS value sent out on CorNet-NQ has the value 1 less than
the value entered in the AMO).
OpenScape 4000 LCOS DPNSS1 RRC

1 0
2 1
3 2
4 3
5 4
6 5
. .
. .
. .
30 29
31 30
32 31
Table 4 LCOS to RRC mapping table
The table can be configured using AMO LWPAR:
To change a single value in the LCOSVRRG table:

CHA-
LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=LCOSVRRG,LCOS=1
,RRG=32;
To change many values in the LCOSVRRG table:
CHA-
LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=LCOSVRRG,LCOS=1
&2&3&4,RRG=32&33&34&35;
To change a single value in the LCOSDRRG table:
CHA-
LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=LCOSDRRG,LCOS=1
,RRG=32;
To change many values in the LCOSDRRG table:
CHA-
LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=LCOSDRRG,LCOS=1
&2&3&4,RRG=32&33&34&35;
To set the LCOSVRRG table back to its default settings:
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=LCOSVRRG;
To set the LCOSDRRG table back to its default settings:
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=LCOSDRRG;
TRGCBG Table: This table converts between the OpenScape 4000 ITR (VBZ)
value and the Realitis DX CBG (Call Barring Group) value when the originator or
destination of a call is a terminal on the PBX. The format of the table is shown in
Table 5. The table is Indexed using the OpenScape 4000 ITR value. The table is
setup with default values with the DPNSS1 CBG having the same value as the
OpenScape 4000 ITR - this is shown in Table 5.
OpenScape 4000 ITR DPNSS CBG

0 0
1 1
2 2
3 3
4 4
. .
. .
. .
13 13
14 14
15 15
Table 5 ITR to CBG Mapping Table
The table can be configured using AMO LWPAR:
To change a single value in the TRGCBG table:

CHA-
LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=TRGCBG,TRG=1,CB
G=32;
To change many values in the TRGCBG table:
CHA-
LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=TRGCBG,TRG=1&2&
3&4,CBG=32&33&34&35;
To set the TRGCBG table back to its default settings:
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=TRGCBG;
DXTGITR Table: This table converts between the OpenScape 4000 ITR (VBZ)
value and the Realitis DX Trunk Group Number ( in the Call Barring Group of the
DPNSS1 COS) value when the originator or destination of a call is a trunk circuit.
This is used for Trunk-to-trunk barring within a mixed OpenScape 4000, Realitis
DX network.
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
The format of the table is shown in below. The table has 32 entries. The table is
initially empty.
Entries are added to the table to map Trunk Groups values in Realitis DX into
Trunk Group values in OpenScape 4000 and vice versa.
The range of the OpenScape 4000 ITR value ( 0 to 15) is much smaller than the
Realitis DX Trunk Group values (0 to 200). This can result in many Realitis DX
Trunk Group values mapping onto a single OpenScape 4000 ITR value. This
situation is shown in the following table. For the direction Realitis to OpenScape
4000 the PBXXX converts the values as configured in the table, searching using
the DXTG value. For the direction OpenScape 4000 to Realitis DX the one of the
DXTG values must be chosen from the list ( e.g. in the table shown, OpenScape
4000 ITR value =0, this could be mapped to DXTG values of 12 or 254 or 127 or
199. The parameter PRIME is then used by PBXXX to choose which mapping to
use; in the example the OpenScape 4000 ITR value = 0 will be mapped into
Realitis DX Trunk Group value 127.
The parameter PRIME must be configured for one of the mappings where there
are many DX Trunk Group values for the same OpenScape 4000 ITR value.
DXTGP DPNSS OpenSca DPNSS OpenSc

OS DXTG pe 4000 PRIME DXTGP DXTG ape PRIME
ITR OS 4000
ITR
0 34 5 * 1 12 0
2 45 5 3 254 0
4 5
6 150 10 7 199 0
8 127 0 * 9 27 9 *
10 11 18 5
12 13
14 23 15 15
16 17
18 19 2 9
20 21 231 9
22 23
24 25
26 27
28 29
30 31
To set a single entry in the DXTGITR table:
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
CHA-
LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=DXTGITR,DXTGPOS
=14,DXTG=23,ITR=15;
To set many DXTG values to a single ITR value in the DXTGITR table :
CHA-
LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=DXTGITR,DXTGPOS
=0&2&11,DXTG=34&45&18,ITR=5,PRIMDXTG=34;
To set a PRIMDXTG value in the DXTGITR table:
CHA-
LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=DXTGITR,PRIMDXT
G=27;
To delete the whole DXGITR table:
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=MAPPING,TBL=DXTGITR;
27.9.11 Trunk Identity Configuration

The Trunk Identity service is enabled or disabled by configuration parameter. This
parameter is TIDOP in AMO LWPAR. This parameter must be configured = YES
to enable the mapping of Trunk Identity between OpenScape 4000 and DPNSS.
To turn trunk identity mapping on:

CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=CONF,TIDOP=Y;
To turn trunk identity mapping off:
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=CONF,TIDOP=N;
27.9.12 Routing DX calls to AC-Win MQ source keys

This feature allows the CLC of ISRM messages from the DX to generate a
particular priority in the classmarks of the Setup message sent to the OpenScape
4000. There are four categories of calls for which priorities are assigned, the
brackets show the parameter used to change the value.
• Internal (ICPN)
• Analogue trunk (ATPCN)
• DASS (DASSPCN)
• Analogue PSTN (APCPN)
There are default values for these parameters which are:
• Internal = 11
• Analogue trunk = 12
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
• DASS = 13
• Analogue PSTN = 14
The priority has a range of 1 to 16.
To change the value of a parameter use the following ( for example to set the call
priority of internal calls to 6) :
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=CONF2,ICPN=6;
Calls to the operator can be routed according to their priority to a particular
ACWIN queue by use of the AMO parameter VFGR.
27.9.13 Automatic redirection to voicemail on busy

This feature allows a OpenScape 4000 user when calling a busy DX voicemail
user to be redirected to a voicemail system. The OpenScape 4000 user on
encountering a busy DX voicemail user will hear ring tone for a configurable time
before being redirected to a voicemail system.
There are three configurable parameters set by LWPAR.
• AROB - this enables/disables the feature
• VMSYSTAD - this sets the voicemail address
• TAROB - this sets the delay before the user is redirected
An example for each is given below.
AROB
This can have a value of y or n. The default is n.
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=CONF2,AROB=Y;
VMSYSTAD
This can store up to 22 digits in the range 0 to 9. The default is empty, no digits
stored.
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=CONF2,VMSYSTAD=7802020;
TAROB
This parameter sets the delay in seconds before the call is redirected to the
voicemail system.
To set 15 seconds,
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=TIMER,TAROB=15;
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Relevante AMOs
27.9.14 Trunking: Private ISDN networking

One parameter SCCONF is used to enable/disable the ability of any station to
control a conference. The parameter can have a value of y or n, the default n.
Setting SCCONF to n means master controlled conference is used.
To turn station controlled conference on:

CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=CONF2,SCCONF=Y;
To turn station controlled conference off:
CHA-LWPAR:TYPE=CDG,BLNO=<number>,CDGTYPE=CONF2,SCCONF=N;
27.10 Relevante AMOs
AMO Parameter Sprache/ Beschreibung/ Discription

Language
LWPAR TYP=CDG d Typ für PBXXX (nur ÄNDERN,
LOESCHEN, ABFRAGEN,
REGENERIEREN, KOPIEREN)
TYPE=CDG e Type for PBXXX (only CHANDE, DELETE,
DISPLAY, REGENERATE, COPY)
CDGTYP d Verzweigung:
= KONF: Konfigurationdaten ändern
= TIMER: Zähler und Reserveparameter
ändern
CDGTYPE e Branch:
= CONF: Change configuration data
= TIMER: Change timer
BLNR d Blocknummer, wurde für PBXXX auf 0-49
erweitert
BLNO e block number has been extended to 0-49 for
PBXXX
BLNRALT d alte Blocknummer, wurde für PBXXX auf 0-
49 erweitert (Aktion KOPIEREN)
BLNOOLD e old block number has been extended to 0-
49 for PBXXX (action COPY)
BLNRNEU d neue Blocknummer, wurde für PBXXX auf
0-49 erweitert (Aktion KOPIEREN)
BLNONEW e new block number has been extended to 0-
49 for PBXXX (Aktion KOPIEREN)
LWPARREF d LWPAR Referenz-Information ausgeben
(Verweis, welchen Sätzen der Block
zugeordnet ist, JA/NEIN)
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Relevante AMOs

Language
e display LWPAR reference information
(circuits which have assigned the block
number, Y/N)
MUSTER d Ruhebitmuster für die B-Kanäle der Strecke
(0-255)
PATTERN e idle bit pattern for the b-channels on the
route (0-255)
BENW d Benutzer/Netzwerk Einstellung:
= DPACB: DPNSS:A / Cornet:Benutzer
= DPACN: DPNSS:A / Cornet:Netzwerk
= DPBCB: DPNSS:B / Cornet:Benutzer
= DPBCN: DPNSS:B / Cornet:Netzwerk
UNWD e user/network definition:
= DPACU: DPNSS:A / Cornet:user
= DPACN: DPNSS:A / Cornet:network
= DPBCU: DPNSS:B / Cornet:user
= DPBCN: DPNSS:B / Cornet:network
PROT d externes Protokoll - nur fuer CORNET-N
Protokoll relevant:
= DASS
= DPNSS
e external protocol - relevant for CORNET-N
protocol only:
= DASS
= DPNSS
BKAKONF d DPNSS B-Kanal x/y Konfiguration (1-30,
gekettet)
BCHCONF e DPNSS b chanel x/y configuration (1-30,
concat.)
VKDPNSS d virtuelle Kanäle mit DPNSS (1-30, gekettet)
EQVIRC e DPNSS equipped virtual channels (1-30,
concat.)
VKKONF d virtuelle Kanäle x/y Konfiguration (1-30,
gekettet)
VCHCONF e virtual chanels x/y configuration (1-30,
concat.)
NSIMLDL d Meldungslänge für NSI / nicht NSI-
Umschaltung (100-2048)
NSIMSGS e message size NSI to non NSI switchover
(100-2048)
SADRUM d DASS-Cornet Subadresse
Übersetzungsmethode:
= NSAP: Network Service Access Point
= USER: vom Benutzer definiert
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Relevante AMOs

Language
SADRTM e DASS-Cornet subaddress translation
method:
= NSAP: Network Service Access Point
= USER: user specified
MAXTNL d DPNSS maximale Übertragungslänge einer
Meldung (0-2048)
MAXTMS e DPNSS maximum transit message size (0-
2048)
RESTLNK d Restart Link bei Cornet-Hochlauf (JA/NEIN)
e restart link at startup (Y/N)
RESTALL d Restart alle LAPs bei DPNSS/DASS-
Hochlauf (JA/NEIN)
e restart all LAPs at DPNSS/DASS-startup (Y/
N)
BCHNEG d B-Kanalverhandlung (JA/NEIN)
e b channel negotiation (Y/N)
CRC4C d CRC4 bei Cornet-N/NQ (JA/NEIN)
e CRC4 for Cornet-N/NQ (Y/N)
CRC4REP d Schicht 2 CRC4 bei DPNSS/DASS (JA/
NEIN)
e layer-2 CRC4 reporting for DPNSS/DASS
(Y/N)
TEMPSIG d temporaere Signalisierungsverbindung (JA/
NEIN)
e temporary signaling connection (Y/N)
NSITR d NSI Cornet-NQ transit (JA/NEIN)
e NSI Cornet-NQ transit (Y/N)
NSIOUT d Einfügen von NSI in DPNSS abgehend
(JA/NEIN)
e insert NSI DPNSS outgoing (Y/N)
CDGCF d PBXXX transit bei Rufweiterschaltung (JA/
NEIN)
e PBXXX transit working on call forward (Y/N)
CONVBN d Notify-Rückumwandlung von Cornet-N (JA/
NEIN)
e conversion back-notify from Cornet-N (Y/N)
TIDOP d DPNSS Trunk Identifizierungsoption (JA/
NEIN)
e DPNSS trunk identity (TID) option (Y/N)
C3CONF d Halten möglich von Konferenz-Master bei
Dreierkonferenz (JA/NEIN)
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Relevante AMOs

Language
e 3-party conference hold allowed from
conference master (Y/N)
CONACK d Verbindungsquittung von Protokol Handler
(JA/NEIN)
e connect acknowledge sent by protocol
handler (Y/N)
LSCF d Loadware im Flash komprimiert gespeichert
(JA/NEIN)
e loadware saved compressed in flash (Y/N)
DEFID d ROP, die benutzte Anruf-
Identifikationslänge in Cornet-NQ:
= B001: 1 Ziffer
= B010: 2 Ziffern
= B011: 3 Ziffern
= B100: 4 Ziffern
e ROP, default call identity lenght used in
Cornet-NQ:
= B001: 1 digit
= B010: 2 digits
= B011: 3 digits
= B100: 4 digits
DASSOPN d DASS Operator Rufnummer (max. 22-
stellig)
e DASS operator number (max. 22-digits)
TBID d Timer: Callback Interdigit (1-20 Sek.)
e timer callback interdigit (1-20 sec)
TROPTBR d Timer: ROPT Release - beide Enden
freigegeben (1-100 Sek)
e timer ROPT release - both end released (1-
100 sec)
TROPTNR d Timer: ROPT Release - kein Ende
freigegeben (1-100 Sek)
e timer ROPT release - neither end released
(1-100 sec)
TDPNSSC d Timer: DPNSS Kollision (0-50*100 ms)
e timer DPNSS collision (0-50*100 ms)
TWEOS d Timer: Warten auf EOS von Cornet (0-100
Sek)
e timer wait for EOS from Cornet (0-100 sec)
TSABMR d Timer DPNSS SABMR Neuübertragung (0-
255 Sek)
e timer DPNSS SABMR retransmission (1-
255 sec)
T301...T305 d Timer 301 ... Timer 305 (0-255 Sek)
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Relevante AMOs

Language
e timer 301 ... timer 305 (0-255 sec)
T308...T310 d Timer 308 ... Timer 310 (0-255 Sek)
e timer 308 ... timer 310 (0-255 sec)
T313-T314 d Timer 313 , Timer 314 (0-255 Sek)
e timer 313 , timer 314 (0-255 sec)
T316, T322 d Timer 316 , Timer 322 (0-255 Sek)
e timer 316 , timer 322 (0-255 sec)
TAMOST d Timer: AMO Überwachung (0-255 Sek)
e timer AMO supervision timeout (0-255 sec)
RES1...RES5 d Reserve 1 ... Reserve 5 (0-65535)
e reserve 1 ... reserve 5 (0-65535)
TDCSU GER=CDGAMT d Gerät: PBXXX für Amtsanschluss
DEV=CDGCOD e Device for PBXXX trunk to CO
GER=CDGVERB d Gerät: PBXXX für Querverbindungen
DEV=CDGCONN e Device for PBXXX tie trunk
LWPAR d Verweis auf den Loadware Parameter
Block, für PBXXX ist die Blocknummer 0-49
erlaubt
e Reference to Loadware Parameter Block,
for PBXXX block number 0-49 is allowed
TRACOUNT d Transit Counter: für PBXXX ist nur 1-25
(Standard 25) erlaubt
e Transit Counter: for PBXXX only 1-25
(Default 25) is allowed
PROTVAR d Protokollvariante: für PBXXX sind nur
Cornet-N und Cornet-NQ (CORNV33,
ECMAV2) erlaubt. Bei Cornet-NQ wird
immer das externe Protokoll DPNSS1 in der
PBXXX eingestellt
e Protocol Variant: for PBXXX: only Cornet-N
and Cornet-NQ (CORNV33, ECMAV2) are
allowed. Cornet-NQ impacts the PBXXX
external protocol DPNSS1
A31003-H3170-S103-6-7620, 02/2019
cornet_nq_en.fm
Relevante AMOs
A31003-H3170-S103-6-7620, 02/2019
cornet_vn_en.fm
Feature Description
28 CorNet-VN (CorNet Virtual Networking)

CorNet Virtual Networking (CorNet-VN) is a patented signaling protocol whereby
the networking capabilities of CorNet-N are supported over a public switched
telephone network (PSTN) connection. This is done by passing the proprietary
signaling elements of CorNet-N through the PSTN using the user-to-user
signaling (UUS) capabilities of the public network carrier.
CorNet-VN is offered to U.S. customers as an alternative to conventional CorNet-

N or CorNet-NQ trunks that require dedicated T1 facilities. CorNet-VN is not
intended to replace CorNet-N or CorNet-NQ trunks, but rather augment them with
a solution that is more cost effective in certain customer environments. The
typical situation where CorNet-VN is more cost effective than CorNet-N/NQ
trunks is for inter-connecting distant locations that have low traffic volume where
dedicated or leased-line facilities would be expensive and under utilized. CorNet-
VN shall be supported across AT&T and Worldcom (formerly MCI) public
telephone networks.
Hicom
300H
V1.0 CorNet-VN
Hicom
HiPath 300E
4000 CorNet-VN AT&T or Worldcom V6.5
CorNet-VN
V2.0 (MCI) Network
HiPath
3000
CorNet-VN CorNet-VN
CorNet-N
(Hicom
HiPath ISDN PRI 150E)
4000 HiPath
V2.0 4000
non-
CorNet-VN V2.0
HiPath PBX Hicom
CorNet-NQ
4000 CorNet-N 300E
V1.0 or V6.5
V2.0
The above figure illustrates a typical CorNet-VN network whereby CorNet-VN is

used for long-haul non-IP connectivity through the PSTN. CorNet-N is used for
lang-haul non-IP connectivity between OpenScape 4000/HiPath 4000 switches.
CorNet-NQ is used for short-haul non-IP connectivity between OpenScape 4000/
HiPath 4000 switches. The figure shows a mix of switch types that are CorNet-
VN capable as well as a non-CorNet-VN-capable switch that is connected to the
PSTN using conventional ISDN-PRI.
A31003-H3170-S103-6-7620, 02/2019
cornet_vn_en.fm
User Interface
28.2 User Interface

CorNet-VN is based on CorNet-N, therefore the user has a limited CorNet-N user
interface available.

The CorNet-VN feature is intended for North American marktplace.

CorNet-VN will run on the TMDNH (Q2192-X, Function ID 3) card or on its
replacement DIUN2U (Q2216-X, Function ID 6).
• How to configures the TMDNH / DIU2U board

configures the TMDNH board:
ADD-BCSU: MTYPE=TMD, LTG=x, LTU=y, SLOT=z, PARTNO="Q2192-X",
FCTID=3, LWVAR="K", HWYBDL=A;
configures the DIU2U board:
ADD-BCSU: MTYPE=TMD, LTG=x, LTU=y, SLOT=z, PARTNO="Q2216-X",
FCTID=6, LWVAR="K", HWYBDL=A;
• How to configures the CorNet-VN AT&T
The following commands are based on COPY-PRODE: TYPE=PVCD,
PVCDNO=16 to load the US protocols into memory (default PVCDNO = 16).
Then the associated PRODE tables for CVN1 and CVN2 are available.
configures the AT&T trunk:
CHANGE-LWPAR: TYPE=TMD, TMDTYPE=TMDMOS, BLNO=3,
OPMODE=FRAMEESF&BISUB8ON&BDETON, CABLETYP=1, OESDISTH=30,
OESREQTH=4, SESDISTH=10, SESREQTH=10, ACKTIM=10, DLVTIM=300,
OCTMAX=260, RETMAX=3, WINDOW=7, CRIDC=0288, NSFIV=1,
NSFTSC=9, TTSC=4;
configures new device S1CVN with AT&T protocol:
ADD-TDCSU: OPT=NEW, PEN=x-y-z-1, COTNO=99, COPNO=95, DPLN=1,
ITR=0, LCOSV=1, LCOSD=1, CCT=" ", DESTNO=5, PROTVAR="CVN1",
SEGMENT=1, DEDSVC=NONE ,TRTBL=GDTR, SIDANI=N, ATNTYP=TIE,
CBMATTR=NONE, TCHARG=N, SUPPRESS=0, TRACOUNT=31,
SATCOUNT=MANY, NNO=1-1-501, ALARMNO=2, FIDX=1, CARRIER=1,
ZONE=EMPTY, COTX=99, FWDX=1, CHIMAP=N, UUSCCX=16, UUSCCY=8,
FNIDX=1, NWMUXTIM=10, CLASSMRK=EC&G711&G729OPT, TGRP=98,
SRCHMODE=DSC, INS=Y, DEV=S1CVN, BCHAN=1&&23, BCNEG=N, BCGR=1,
LWPAR=3;
• How to configures the CorNet-VN MCI trunk
A31003-H3170-S103-6-7620, 02/2019
cornet_vn_en.fm
Relevant AMOs
The following commands are based on COPY-PRODE: TYPE=PVCD,

PVCDNO=16 to load the US protocols into memory (default PVCDNO = 16).
Then the associated PRODE tables for CVN1 and CVN2 are available.
configures the MCI trunk:
CHANGE-LWPAR: TYP=TMD, TMDTYP=TMDMOS, BLNO=4,
OPMODE=FRAMEESF&BISUB8ON&BDETON, CABLETYP=1, OESDISTH=30,
OESREQTH=4, SESDISTH=10, SESREQTH=10, ACKTIM=10, DLVTIM=300,
OCTMAX=260, RETMAX=3, WINDOW=7, CRIDC=0222, NSFIV=1,
NSFTSC=9, TTSC=4
configures new device S1CVN with MCI protocol:
ADD-TDCSU: OPT=NEW, PEN=x-y-z-1, COTNO=99, COPNO=95, DPLN=1,
ITR=0, LCOSV=1, LCOSD=1, CCT=" ", DESTNO=5, PROTVAR="CVN2",
SEGMENT=1, DEDSVC=NONE ,TRTBL=GDTR, SIDANI=N, ATNTYP=TIE,
CBMATTR=NONE, TCHARG=N, SUPPRESS=0, TRACOUNT=31,
SATCOUNT=MANY, NNO=1-1-501, ALARMNO=2, FIDX=1, CARRIER=1,
ZONE=EMPTY, COTX=99, FWDX=1, CHIMAP=N, UUSCCX=16, UUSCCY=8,
FNIDX=1, NWMUXTIM=10, CLASSMRK=EC&G711&G729OPT, TGRP=98,
SRCHMODE=DSC, INS=Y, DEV=S1CVN, BCHAN=1&&23, BCNEG=N, BCGR=1,
LWPAR=4;
• Activation / Deactivation of CorNet-VN
displays the number of contracted, assigned and free CVN trunks:
DISP-CODEW;
28.5 Relevant AMOs
AMO Parameter Sprache Beschreibung

BCSU PARTNO d = "Q2216-X" für DIU2U Board
= "Q2192-X" für TMDNH Board
PARTNO e = "Q2216-X" for DIU2U Board
= "Q2192-X" for TMDNH Board
FCTID d = 6 für DIU2U Board
= 3 für TMDNH Board
FCTID e = 6 for DIU2U Board
= 3 for TMDNH Board
LWPAR CRIDC d Pflichtfeld für CVN
= 0288 for AT&T
= 0222 for MCI
CRIDC e Mandatory when block is used for CVN
= 0288 for AT&T
= 0222 for MCI
NSFIV d Default = 1,
= 1 für AT&T und MCI
NSFIV e Default = 1,
= 1 for AT&T and MCI
A31003-H3170-S103-6-7620, 02/2019
cornet_vn_en.fm
Relevant AMOs
AMO Parameter Sprache Beschreibung

NSFTSC d Default = 9,
NSFTSC e Default = 9,
TTSC d Default = 4,
TTSC e Default = 4,
TDCSU PROTVAR d = CVN1 für AT&T
= CVN2 für MCI
TDCSU PROTVAR e = CVN1 for AT&T
= CVN2 for MCI
TDCSU DEV d = S1CVN für die Konfiguration von CorNet-
VN trunks
TDCSU DEV e = S1CVN for configuring CorNet-VN trunks
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Trunk Connections Versus Tie Connections
29 Country-Specific Connection Techniques With Analog

Trunks
The following sections offer some tips and tricks that you can use with the DH-
Länder (DS120). A different chapter describes the MFC-R2 signaling. As a
general rule, features that have been implemented for a particular country have
been developed in a way that allows the feature to be used for other countries as
well. Of course this idea cannot always be applied to all features (because the
hardware, loadware, and other components must match the system software
(generally DH/CP)).
29.1 Trunk Connections Versus Tie Connections

Regardless of the devices (circuits) and their signaling, you can also use a "trunk
connection" as a tie trunk with the COP and COT parameter "TIE". This is true for
terminating connections (incoming). For generated connections (outgoing), the
combination of digital analysis result (WABE) and route (LCR) is important.
29.2 Dial Tone, Proceed-to-Send Signal on Outgoing Seizure

There are users who wait for a proceed-to-send signal (usually a dial tone) after
the trunk group code. We recommend giving up this type of dialing and continuing
to dial immediately.
Using different parameters and settings, you can have the system request that
the user continue dialing.
• After the user dials the trunk access code, the system applies a tone even
if it has not found a circuit:
AMO ZAND: TYPE=ALLDATA, CODTN=YES.
• Using LDPLN, you can configure the digit pattern so that the dial tone is
applied at any position in the dialing. Here it is also the case that the
system has not yet searched for (let alone seized) the circuit. You can also
administer several dial tones here. Example for applying the dial tone
after the user has dialed the code 528:
ADD-LDPLN:LDP=528-W-X,LROUTE=228,LAUTH=1;
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Dialing Procedures
29.2.1 Real Dial Tone (Time-Dependent) From the

Central Office (CO)
If the remote central office also actually applies a dial tone, you must set the
following parameters for the outgoing seized trunk to apply the real dial tone to
the outgoing user from the central office.
• COP parameter: TDED (line with time-dependent central office dial tone)
• AMO TACSU:DIALVAR=x-8 (where x usually has the value 0)
• AMO ZAND: TYPE=ALLDATA, CODTN=NO
• You must configure the outgoing seized circuit for the proceed-to-send signal
(COP parameter: SDL).
The sound path of the outgoing user is switched to the circuit when the dial tone
from the remote central office has been detected.
If only the parameter TDED is set but not the corresponding type of dialing, the
OpenScape 4000 generates the CO dial tone itself and then applies it when this
tone is detected on the line (time-dependent).
29.3 Dialing Procedures

The DH-Länder handles several dialing procedures. You control these with COP
and the DIALTYPE element in the AMO TACSU. To allow for different procedures
in incoming and outgoing seizures, use DIALTYPE = iii-ooo (1st value for
incoming, 2nd value for outgoing).
The usual dialing procedures are: MOSIG-DTMF, DTMF-DTMF, DIP-DIP, MFC-

MFC. The other procedures DIPA, MFP1, MFP2, MFRP, and MFRS are used in
the CIS countries.
MOSIG-DTMF: Main station interfaces (incoming call, outgoing loop, and DTMF
dialing).
DTMF-DTMF, DIP-DIP: double configured DID (direct inward dialing) line with
DTMF (dual tone multi-frequency signaling) or DIP (dial pulse signaling) in both
directions.
MFC-MFC: double configured DID line with MFC signaling.
If you use outgoing DTMF dialing, you also need the COP DTMF and DTM1 (or
DTM2, etc.) to control the DTMF SIU (signaling unit). In the same way, you need
the COP BR64 and IDP1 (or IDP2, etc.) when you use DIP dialing to control the
pulse and the time between pulse series.
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
End-of-Dial and Answer on Outgoing Seizure
29.4 End-of-Dial and Answer on Outgoing Seizure

On loop start lines (or similar signaling with DTMF or DIP dialing), the remote
exchange does not always announce the end-of-dial on outgoing seized lines
(generated connections). This means that this signal must be artificially
generated so that the user can switch from the dial to the talking state. This is
done using a timer. Two timers are provided in the system, end-of-dial and end-
of-dial with 1A-procedure. (Also refer to Kapitel auf Seite 312). There is a
separate description of the control of the end-of-dial and answer with and without
charges (Section 29.4.4, “End-of-Dial With First Call Charge Pulse”).
IMPORTANT: Call detail recording (CDR) registers the digits dialed during the
’dial state’ but ignores digits dialed later.
29.4.1 End-of-Dial Code With ’#’

Different countries (such as the UK) use the pound sign (#, hash mark, number
sign) as the end-of-dial code. The system interrupts the dialing to the CO as soon
as the character to be sent would have been a ’#’ and switches the connection to
the talking state.
This feature is only used when the COP parameter SFRM is set. If the first digit
that was sent to the CO was an asterisk (*) or pound sign (#), the system assumes
that the so-called ’Value Added Network Services’ are being used. The system
then sends out # and generates end-of-dial via the timer (see above).
If the parameter SFRM is not set, all characters of a 16-entry keypad are sent to
the remote exchange (also applies to DIP).
This procedure also applies to a DTMF AnaTe. The 1A procedure described later
can be interrupted by dialing the pound sign.
You can use the same method when dialing with LCR. In MFC-R2, the "dial
complete" signal is converted to I-15.
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
End-of-Dial and Answer on Outgoing Seizure
29.4.2 End-of-Dial According to the 1A Procedure

The 1A dialing procedure is a method of suppressing the DTMF sig-
nals sent by a DTMF user to a remote exchange that can evaluate
any DTMF signals. This is because otherwise incorrect dialing could
result. The SIU sends DTMF signals to the remote exchange.
IMPORTANT: The 1A procedure is always used when the internal station is a

DTMF device. If the trunk is seized over a CorNet link (circuit and station on
different systems), digital telephones also display this property (default value).
You can switch the end-of-dial procedure 1A with the COP parameter NO1A:
• When the parameter is set, the digits are sent to the CO with no delay (also
applies to DIP dialing to CO) and the speech path is not switched until after
the 1A time expires; the connection switches to the talking state.
• If the parameter is not set, the last digit is sent to the CO but delayed by the
1A time (also applies to DIP dialing to the CO) and then the connection
switches to the talking state.
29.4.3 End-of-Dial by Line Signal

Naturally the OpenScape 4000 (or the combined Länder-DH) also handles an
END-OF-DIAL signal from the line. One of the timers mentioned above is always
used in this case, however. The system ignores an END-OF-DIAL signal that is
delayed and arrives after the timer has expired.
29.4.4 End-of-Dial With First Call Charge Pulse

The combined Länder-DH interprets the first call charge pulse as end-of-dial and
answer. If this is not what you want, you must set the COP parameter NOAN.
This procedure also applies to a DTMF AnaTe, so the procedure 1A is therefore

ended with the 1st call charge pulse and the paths (speech paths) are through-
connected.
29.4.5 Effect of the End-of-Dial, Call Charge Pulse,

and Answer Signals
The COP parameters ANS and NOAN have the following combined meanings:
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Dial Tone on Incoming Seizure
ANS NOAN Remark

NO NO End-of-dial and answer are announced to the CP together after time-
out. Transition to the talking state. 1st call charge pulse or the
ANSWER signal during dialing is interpreted as end-of-dial and
answer.
NO YES End-of-dial and answer are announced to the CP together after time-
out. The 1st call charge pulse is not interpreted as the ANSWER
signal. If the line sends an ANSWER signal in the dial state, this
causes a change to the talking state.
YES NO End-of-dial announced after time-out. An ANSWER signal or a 1st call
charge pulse must be received.
YES YES The line must receive an ANSWER signal to change the connection
to the talking state. After the end-of-dial timer expires, no more digits
are sent.
IMPORTANT: The COP parameter EOD (line with end-of-dial) signals the end-
of-dial on incoming seizures.
29.4.6 Configuring the End-of-Dial Monitoring and

End-of-Dial 1A Timers
Because the end-of-dial detection influences the transition to the talking state but
the dialing behavior of the user must also be taken into consideration, there are
conflicting requirements. Furthermore, you should note that signaling method no.
5 used in international traffic uses a 5 second timer here. The LCR settings also
have an influence (for example, no seizure until all digits have been dialed).
CHANGE-DTIM2:TYPEDH=LNGEN,EOD=5000,EOD1A=5000; (values in ms)
29.5 Dial Tone on Incoming Seizure

As was already mentioned, there are networks (or customers) who do not
continue dialing until they hear a dial tone. The problem can now also occur on
incoming seizures (terminating connections). A dial tone should be applied as
soon as the line is ready for digit input. Different dial tones are possible.
Administer them as follows:
COP parameter: DTN (dial tone on incoming seizure)
COT parameter: DTNI (internal dial tone) or DTNE (incoming dial tone, outgoing
mark as co-conn) or ANNC (local announcement). You must set one of the
parameters NTON (no tone), DTNI, DTNE, or ANNC. You can administer the
actual tones using the AMO ZAND after the normal configuration.
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Test Port
29.6 Test Port

For DID calls, it is possible to dial a test port or a test program. These are
implemented with software only. You control these test programs with a TESTNO
specified with TACSU and by selecting the code TESTLN.
29.6.1 CH (Switzerland) Test Port

You can also control this test program with dial pulsing DID.
B6 R’back tone Test tone Busy tone

(DTV) Idle
75 ms 6.5 sec 10 sec
1 2 3 4 5
1. End of the last MFC-R2 signal, 75 ms timer in accordance with UIT Q.475, or
end-of-dial detection.
2. END-OF-DIAL-FREE message to the line (loadware) and application of the

ringback tone (including 1st ringback tone).
3. Time-out for controlling the ringback tone phase (including 1st RINGBACK
TONE); 2 .. 3 times ringback tone. ANSWER message to line (loadware)
4. Time-out for controlling the test tone phase; RELEASE message to line
(loadware)
5. Wait for release from CO (RESETPOTENTIAL message from the loadware);

READY message to CP, line free for switching.
To control the SWZ test program you must assign the correct TESTNO in the
TACSU and you must configure the timer in compliance with the defaults.
• Set or change the test number in the TACSU as follows:

CHANGE-TACSU: ..., TESTNO = 1
• Set or change the timers as follows:
CHANGE-DTIM1:TYPEDH=MFCDID,TSUPV1=6500,TSUPV2=10000;
29.6.2 BEL Test Port

You can only control this test program with MFC-R2 DID.
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Test Port
A6 A1 Idle
2 sec. 1.5 sec.
1 2 3 4
1. End of the last MFC-R2 signal; END-OF-DIAL-FREE message to line

(loadware)
2. ANSWER message to line (loadware); application of the ringback tone

(including 1st ringback tone)
3. Time-out for controlling the test tone phase. The MFC-R2 forward signal A1
is used as the test tone in Belgium.
4. Wait for RELEASE from CO. READY message to CP, line free for switching
To control the BEL test program you must assign the correct TESTNO in the

29.6.3 RSA Test Port
B6 R’back tone Test tone Idle

(400 Hz)
75 ms 5 sec 5 sec
1 2 3 4 5
1. End of the last MFC-R2 signal, 75 ms timer in accordance with UIT Q.475 or
end-of-dial detection
2. END-OF-DIAL-FREE message to line (loadware); Application of the ringback

tone (including 1st ringback tone)
3. Time-out for controlling the ringback tone phase (including 1st ringback tone).
2 .. 3 times ringback tone; and ANSWER message to PP (loadware).
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Test Port
4. Time-out for controlling the test tone phase; RELEASE message to the line
(loadware)
5. RESETPOTENTIAL message from PP (loadware); READY to CP, line free for

switching
To control the RSA test program you must assign the correct TESTNO in the

29.6.4 CIS Test Port
Test tone Test tone

R’back tone 700 Hz Pause 700 Hz Busy tone Idle
75 ms 8 .. 18 sec 2.5 sec 5 .. 6 sec 0.5 sec
1 2 3 4 5 6 7
1. End-of-dial detection
2. END-OF-DIAL-FREE message to line (loadware)
3. ANSWER message to line (loadware)
4. Time-out for controlling the idle phase
5. Time-out for controlling the 2nd test tone phase
6. RELEASE message to line (loadware)
7. READY message to CP, line free for switching
To control the CIS test program you must assign the correct TESTNO in the

CHANGE-
DTIM1:TYPEDH=MFCDID,TSUPV1=13000,TSUPV2=2500,TSUPV3=5500,TSUP
V4=500;
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Extension of Trace Signaling for Calls to the Attendant Console
29.7 Extension of Trace Signaling for Calls to the Attendant Console

Different sequences and signaling in Finland and the Czech Republic: In Finland,
the attendant console should automatically have trace authorization as soon as
one user in a system has this authorization. In the Czech Republic the attendant
console should also explicitly receive the trace authorization. The new COT
parameter "AC with call tracing" has been introduced for this purpose.
• Set the COT parameter for calls to the attendant console as follows:
CHANGE-COT:COTNO=x,COTTYPE=COTADD,PAR=ACTR;
IMPORTANT: In Finland you must set the COT ACTR as soon as a user is
authorized for tracing.
29.8 Line With Loop Start Signaling and Straightforward Direct Inward
Dialing (DID)
There are customers who have a PTT that cannot provide them with DID because
of a lack of resources. The feature described here for main station interfaces
(loop start signaling) can help (if the general numbering plan allows it).
Naturally you can also use the feature for connecting external systems with the
OpenScape 4000 (see also TC-SL link).
29.8.1 Feature Description (User Interface)

The ’external’ user calls the connection number. When there is a call on the line,
the OpenScape 4000 generates an ANSWER to the CO and applies the dial tone.
The external user can now dial into the system. The codes that are possible are
the same as for ’normal’ DID.
IMPORTANT: In this application, the assessment begins with the answer (appli-
cation of the dial tone).
The feature described functions only with DTMF apparatuses because the DID is
operated with the DTMF signaling method. This means that the external user
must dial with a DTMF device or use an acoustic coupler.
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Connection to External Systems Using TC-SL Link
29.8.2 Operational Configuration

The COP of the main station line must include the parameter DTN (dial tone on
incoming seizure). Determine the dial tone in the AMO COT. It is also possible to
have a synchronous announcement for the proceed to select signal.
You must set the DIALTYPE in the AMO TACSU to DTM-x and you must set the
DIALVAR to 5-0 (line with old loop start loadware BWMSCH) or 4-0 (all other loop
start signaling).
29.8.3 Important Note on the ’Trunks’

Trunks that are operated with the feature described here must be answered or
they will not be able to be released later. This condition does not apply if the trunk
(including the hardware used) can handle forward release by interrupting the
supply voltage. You must coordinate this with the remote exchange during the
system start-up.
If forward release is not possible, you must set all intercept cases (COT) while
keeping in mind that calls to the attendant console or night station must be
answered. (One way to do this is with the help of an answering machine that
also triggers when the system is operated unattended).
29.9 Connection to External Systems Using TC-SL Link

Straightforward networking of the OpenScape 4000 with external products is
possible with a TC-SL link. An analog subscriber line (SL) from the external
system is connected to a trunk circuit (TC) from the OpenScape 4000 (loop start
signaling).
OpenScape 4000
A
External system loop start
B AC
(TM2LP) SLMx A
Subscriber .......
C line
A
(SL)
(TC)
The following chapters contain some specific notes on the following applications:
• Outgoing seizure
• Incoming seizure
• Consultation hold
• Trunk grounding/trunk flash
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
• Consultation hold pick up in straightforward trunk calls
• Suffix dialing
29.9.1 Outgoing Calls (OpenScape 4000 to External

System)
Calls that a OpenScape 4000 user makes to a remote system take place with the
digital analysis result CO (or tie) and the appropriate signaling method. To reach
the talking state, the end-of-dial criteria described above apply.
29.9.2 Incoming Calls (External System to

OpenScape 4000)
Calls from an external user to the OpenScape 4000 (BWMSCH) reach the
attendant console or reach a specific user with the help of the Dedicated
Incoming Trunk (continuous assigned night service) feature. The loop start trunk
with straightforward DID feature (pseudo DDI; see above for more information)
offers another way to selectively reach a OpenScape 4000 user.
29.9.3 Consultation Hold

A consultation hold in the external system is initiated or cancelled with flash or
ground. Because the OpenScape 4000 does not know whether an incoming call
is a consultation hold call, the call can be picked up with either the feature Trunk
grounding/trunk flash or the feature Picking up a consultation hold in
straightforward trunk calls.
If you want to set up a consultation hold in the external system, proceed as

follows:
• Initiate the consultation hold in the talking state (incoming or outgoing) in the
OpenScape 4000 and dial the OPROVR code.
• Wait for the dial tone of the external system (is not evaluated by the
OpenScape 4000)
• Dial the user number in the external system (suffix dialing after grounding).
• Depending on the properties of the external system, either you can transfer
the call by going on hook or you must wait until user C picks up.
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
• Cancel the consultation hold in the external system: initiate the consultation
hold (in the OpenScape 4000) and dial the code OPROVR (connection A-B).
29.9.4 Trunk Grounding/Trunk Flash

The feature described in the following was developed under the name "operator
recall". It should take the place of repeatedly pressing the cradle button, which is
common in different countries and is used to call the operator. There are
(dedicated) circuits that use an adaptor to convert the ground pulse into a call to
get the remote party on the line.
29.9.4.1 Implementation
Depending on the COP parameter DTMP for the line, the system generates a
ground pulse (DTMF not set) or a loop interruption (DTMF set). It is not possible
to replicate an AnaTe with DTMF dialing and ground key.
When the ground pulse or the flash pulse ends, the trunk returns to the talking
state.
You can set the ground pulse or flash for BWMSCH lines with the AMP PTIME,
parameter TBLK for BWMSCH under L3 and L4. L3 contains the time for the
ground pulse (default: 240 ms) and L4 the time for the flash (default: 120 ms).
IMPORTANT: NOTE for BWMSCH lines

The ground is applied only to the ring wire in the ground pulse. You must check
the wiring because the tip and ring wires are no longer polarity-independent.
• DigiTe:
Initiate a consultation hold from the talking state (in the OpenScape 4000) and
dial the OPROVR code: -> ground pulse/flash to trunk.
You can simplify the procedure by programming the ’OPROVR’ code on a
name/destination key. Then you do not have to initiate the consultation hold.
Send the (suffix) dialing to the remote exchange with the signaling method (-
outgoing: DIP or DTMF) that is assigned to the line.
• AnaTe:
Initiate the consultation hold from the call and dial the OPROVR code: ->
ground pulse/flash to trunk.
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Send the (suffix) dialing from a COMTEL 3 (DIP-AnaTe) to the remote

exchange with the signaling method (-outgoing: DIP or DTMF) that is
assigned to the line.
• AC:
Push the aggregate key during the call -> ground pulse / trunk flash; (WABE:
OPROVR for AC is not necessary). Then it is not possible to dial on the line.
29.9.5 Picking Up a Consultation Hold in

Straightforward Trunk Calls
Even the first OpenScape 4000 versions had the feature Picking up a
consultation hold in straightforward trunk calls. This makes it possible to pick up
a consultation hold connection that was set up by the external exchange (see
figure).
29.9.5.1 Implementation
This uses the same procedures as for Initiating a consultation hold or Ground/
flash to CO (see previous sections).
• DigiTe:
Initiate a consultation hold from a call and dial PUEXT code: -> ground pulse/
flash to trunk; cancel consultation hold.
You can simplify the procedure by programming the ’PUEXT’ code on a
name/destination key. Then you do not have to initiate and cancel the
consultation hold.
• AnaTe:
Initiate a consultation hold from a call and dial PUEXT code: -> ground pulse/
flash to trunk; cancel consultation hold.
• AC:
Push the aggregate key during the call -> ground pulse / trunk flash; (WABE:
PUEXT for AC not necessary).
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
29.9.6 Suffix Dialing To Remote System

Because lines with loop start signaling do not have any criteria for end-of-dial
(evaluated or not evaluated), the OpenScape 4000 can be in the ’talking state’
although the remote system is in the busy or ringing state. Now you can use
remote system features with suffix dialing.
IMPORTANT: Send the (suffix) dialing to the remote system with the signaling
method (-outgoing: DIP or DTMF) that is assigned to the line. This is not a cross-
network feature.
If you have configured a line for suffix dialing (COT: OVRA & USD set), then every
dialing is sent to the remote system as suffix dialing. This means that features that
are controlled by suffix dialing are not possible in the OpenScape 4000. This
affects redial, tracing, and DTMF transmission.
29.9.7 Configuration Notes

The following notes apply to all applications (grounding/flash to trunk, suffix
dialing after grounding, and picking up after a consultation hold):
• This setting is valid for BWMSCH lines. The same basically applies to
other lines (see PTIME). In PTIME TBLK (corresponds to CIRCIDX in
TACSU) check that BWMSCH L3 = 240 ms and L4=120 ms; These may
have to be adapted to fit the line that is connected.
• You must set OVRA in the COT of the trunk circuit.
• The application only functions when the trunk circuit for the outgoing
seizure is reached over the CO (WABE) digital analysis result.
For grounding and flash to the line, the following applies:
• Configure the digital analysis result OPROVR in WABE.
To pick up a consultation hold with TC-SL coupling, the following applies:
• Configure the digital analysis result PUEXT in WABE. In the COT of the
trunk circuit, you must set CONS (COT OVRA is not needed for the
feature alone).
The OpenScape 4000 no longer has the COT CONS; a replacement will
follow later.
To allow suffix dialing, the following applies (for example, after OPROVR):
• You must set USD in addition to OVRA in the COT.
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Testing and Measuring the DTMF and MFC Signals
29.10 Testing and Measuring the DTMF and MFC Signals

Different network providers want to be able to measure the DTMF and MFC
signals that the SIUs send on the trunks. This is possible with the help of a DigiTe.
SLMx
SW
TMx Call
CO
Processing
SIU
Type 3
Testing MFC-R2 or
equipment Type 2 OpenScape 4000
or DTMF
Figure 19 Overview of the Principle: Test of the MFC Signal Transmitter with
SIU Type3

Initiate the tests with the DigiTe from the talking state with the circuit. You can
reach the talking state with an incoming call to the DigiTe in the case of MFC or
by dialing the correct trunk group code from the DigiTe if you are conducting a
DTMF test.
In suffix dialing (without previously pressing the consultation key), dial the
FREQTEST code (*xz); the telephone (DigiTe) acknowledges on the display with
"*xz EXECUTED". The DigiTe remains connected to the circuit.
The DigiTe CP evaluates and displays each digit in the range from 00 .. 16
according to Table 1. There is no digit time monitoring. If you dial a number > 16,
the display shows "INCORRECT INPUT" for 5 s. You can start to dial a new string
of digits immediately.
There are no other features possible from the DigiTe, which means that in the
state "MFC/DTMP test" only the digit keys and going on hook have any effect (no
name keys, disconnect, consultation hold, etc.).
After you dial two digits, the system directly notifies the DH-Länder of this. The
system deletes all previously picked up digits. The dialing translation takes place
in DH-Länder according to Table 4.8.1. As soon as the system recognizes the
next digit as valid, it deactivates the applied signal and sends the new one.
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Extension of the Override Features With Intercept
If you dial an invalid signal (signal ’-’ according to Table 4.8.1), for example, signal
16 as MFC-R2 signal, the system deactivates the pending signal but does not
send a new one.
IMPORTANT: The measurement equipment (testing equipment) must

guarantee the feeding conditions (direct current conditions) and the termination
(alternating current conditions) of the line.
Assign the code *xy to the digital analysis result FREQTEST with the AMO
WABE.
Assignment of dialing -> signals:
Dialing/Display Corresponds to Corresponds to Corresponds to

MFC-R2 signals SOCOTEL/ DTMF digit (16-
IBERCOM signals key)
00 - Ctrl freq -
01 1 1 1
02 2 2 2
03 3 3 3
04 4 4 4
05 5 5 5
06 6 6 6
07 7 7 7
08 8 8 8
09 9 9 9
10 10 0 0
11 11 - *
12 12 - #
13 13 - A
14 14 - B
15 15 - C
16 - - D
29.11 Extension of the Override Features With Intercept

If a terminating call reaches a busy user (without intercept, automatic call waiting,
etc.), a remote override can result, depending on the configuration (or signaling).
If it is not possible to override, the system intercepts the call to the attendant
console if COT:IONS is set. This is also basically true for automatic override. You
control the feature with the COT parameter IONS.
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Reversed Charges Calls
• Change the COT as follows:

CHANGE-COT:cotno,COTADD,IONS;
29.12 Reversed Charges Calls

For Brazil, the system uses a special line signal to signal the ANSWER of a user
who is authorized to receive calls with reversed charges to the remote central
office.
It uses the authorization to receive reversed charges calls and the COT
parameter ACRC.
• Set the COT parameter for calls to the attendant console as follows:
CHANGE-COT:COTNO=x,COTTYPE=COTADD,PAR=ACRC;
• Change the COS as follows:
CHANGE-COSSU:TYPE=COS,COS=x,AVCE=REVCHA;
A31003-H3170-S103-6-7620, 02/2019
mfcr2a_en.fm
Reversed Charges Calls
A31003-H3170-S103-6-7620, 02/2019
cugroup_en.fm
30 Customer Groups, Shared Systems CUG

OpenScape 4000 enables several customers to share a common system. The 16
ITR and 16 DPLN groups afford various possibilities of organizing such a system.
The following options exist:
• Assigning stations to any of the 16 ITR groups in such a way that the
terminals of one customer may belong to one or several ITR groups and the
terminals of the other customers cannot be dialled up internally.
• Assigning the trunk circuits to specific customers but allocating common

routing codes to all customers. The DPLN at the terminal causes only those
routes to be seized that are allocated for that user station. The ITR group of
the trunk circuit will establish connections only to those stations to which
traffic is allowed i.e. established via the ITR matrix.
• Trunk circuits may also be required and shared by several customers. In a

different arrangement each customer can use his trunk groups in the outgoing
direction and share them with other customers in the incoming direction.
• Providing the same service/access code numbers for all customers or

entering several code numbers per service. The same applies to the
attendant access code or the code for "trunk answer from any station/
universal night answer".
• Implementing the class-of-service changeover either separately for each

customer or for all customers by assigning the relevant changeover groups
on terminal setup.
• Allocation of NON-VOICE terminals to STN either separately or system-wide

by way of the TGER AMO
Features are always enabled or disabled for the complete system with the
FEASU AMO. Disabling of features for specific customers is possible only by
means of omitting certain access codes for a customer-specific DPLN.
It is not possible to define specific quantities for each customer with the DIMSU
AMO (e.g..: 10 hunting groups for customer A and 20 for customer B). This type
of layout is always defined for the complete system.
The central speed dialling facility, consisting of 16 groups, is so conceived that

groups 1-15 only may be allocated to specific stations. Group 0 is the common
group i.e.shared by all stations.
A31003-H3170-S103-6-7620, 02/2019
cugroup_en.fm
A31003-H3170-S103-6-7620, 02/2019
dtmf_usage_en.fm
DTMF Dialing
Feature Description
31 DTMF Dialing
Welcome
press 1 for sales
press 2 for service
Analog lines
Users with digital telephone sets can convert keypad key preses into DTMF tones
to acess functions e.g. Automatic Atendant feature of Phonemail or other IVR
products

The DTMF dialing is an optional feature that allows the DTMF signaling in
through-connect states.
This case includes anate, analog VoiceMail system, analog IVR, special devices
(e.g. dictation) etc. The device can either be configured to have DTMF dialing
capability or to allow DTMF signaling from its partner while through-connected
(allow to have DTMF suffix dialing in the line ), via the DHPAR=DTMFST.
The following situations are not covered before:
– Digital device in through-connect state with another digital device.
– Through-connect states in a conference.
The DTMF dialing enhancements cover the situations above on an administrable

basis. In the conference, if at least one member (except that one which is sending
digits) requires DTMF signaling, this will be enough to generate DTMF signaling
for all conference members. In addition there is a possibility to spare a local
station member to hear the DTMF tones. Only conferences up to 4 local
conference members will be allowed to receive DTMF signaling.
A31003-H3170-S103-6-7620, 02/2019
dtmf_usage_en.fm
DTMF Dialing
Feature Description
31.1.1 Local DTMF functionality

The flag DHPAR=DTMFST allows to analog devices and DTMFCTRD=YES
allows to digital/functional devices the capability to receive dual tone multi-
frequency signals received from the through-connected partner. In other words,
the digit sender party will be able to compose DTMF signals for the receiving
party, when the receiving party requires the DTMF signaling.
The AMO SCSU, DIAL=DTMF functionality remains the same.
31.1.2 Network DTMF functionality / Trunks that allow

DTMF negotiation.
In an incoming network 2-Party talk state connection and in an outgoing 2-party
connection, the DTMF Negotiation feature will transport the necessary trunk
(route) DTMF requirements (via access code, automatic or without) and the
DTMF station requirements (DTMF flag) after the establishment of the call.
The "Block DTMF in Conference" flag is not transported in the network, since it is
considered only a local optional flag.
After the transportation of the feature indicator fields, the digit sender party will be
able to compose DTMF signals for the receiving party (remote device), when the
receiving party (remote device) requires DTMF signaling.
31.1.3 Outgoing DTMF functionality / Trunks that do

NOT allow DTMF negotiation
For an outgoing connection the DTMF for the originating party is ruled by the
DTMF parameters in AMO RICHT, DTMFCNV parameter.
– WITHOUT = No DTMF conversion for this route,
– FIX = Automatic DTMF conversion,
– SUFDIAL = Activation of conversion by means of suffix dialing (DTMF

access code)
When the route is configured with DTMFCNV=FIX, the originator party will
allocate a MF circuit Sender to convert the pressed digits into DTMF Signals
directly in the voice path.
When the route is configured with DTMFCNV=SUFDIAL, as soon the DTMF

access code is dialed, the originator party will allocate a MF circuit Sender to
convert digits into DTMF Signals directly in the voice path.
For the analog devices configured with DIAL=DTMF, this RICHT parameter does
not apply, since they could be configured to send DTMF signaling by themselves.
A31003-H3170-S103-6-7620, 02/2019
dtmf_usage_en.fm
DTMF Dialing
Feature Description
31.1.4 Incoming DTMF functionality

For incoming network connection, the DTMF activation via SUFDIAL (DTMF
access code) is allowed. As soon the DTMF access code is dialed, the called
party allocates the MF circuit sender to convert pressed digits into DTMF signals.
IMPORTANT: DTMF negotiation may also take place in these scenarios.
31.1.5 DTMF signaling in a conference concept

For conference states, DTMF signaling is allowed if it is requested for at least one
of the conference members (except the member who pressed the key). Both
analog devices, digital devices, and external partners are able to receive DTMF
signaling while in conference. The DTMF signal will be generated by each
member of the conference by itself.
To prevent a local partner from hearing DTMF signals while in conference, the
station basis flag "Block DTMF in Conference" should be configured. With this
flag, the local partner will not hear a local DTMF tone, remaining connected in the
conference during the signaling process. This flag should block the DTMF
signaling only when it is generated internally, by a local conference member.
The internal DTMF conference signaling will be provided in a conference (limited

to 4 conference members).
By default, all external partners of a DTMF conference should be able to hear

DTMF automatically, also when they do not require to hear DTMF tone.
In the DTMF conference, each local analog, digital, and external partner should
be responsible for the DTMF conversion itself. In the same way the flag
DHPAR=DTMFST and DTMFCTRD=YES will set this requirement that the
conference member device that has the DTMF flag.
IMPORTANT: Attendant devices and functional devices will not be able to

hear DTMF digits in a conference because the DTMF in conference feature
shall cover ACD scenarios and neither attendant devices, nor functional
devices can be ACD agents.
The following trunks will support DTMF dialing in conference scenarios:
– Analog trunk with signaling type DP (dial pulse)
– Analog trunk with signaling type DTMF
– Analog trunk with signaling type MFCR2
A31003-H3170-S103-6-7620, 02/2019
dtmf_usage_en.fm
DTMF Dialing
Feature Description
– Digital trunk with signaling type DP - dial pulse
– Digital trunk with signaling type DTMF
– Digital trunk with signaling type MFCR2
– Cornet trunk - ISDN
– PRI trunk
– Ground Start trunk
– E+M trunk
The following device/signaling types will NOT support DTMF dialing in

conference scenarios:
– Functional devices (because it cannot become an agent)
– Attendant (because it cannot become an agent or supervisor).
– other trunks not mentioned above, such as cornet analog trunks, will not
be implemented.
Notes:
• If in the history of a conference at least one member required DTMF
signaling, for the NW party this conference will require DTMF signaling. This
will occur because the NW party is not informed that a local conference
member disconnected (e.g. only this local conference member, which
disconnects, requires DTMF in this conference). However, once the
conference is removed (for example, the conference resources are released
and the connection reduces to two parties), the NW is informed.
• If in the history of a conference (with local, and NW orphan members) no

member had required DTMF signaling, and in this scenario a new local
member which requires DTMF is added to this conference, the NW orphan
member(s) will not be informed that at least one member of this conference
requires DTMF.
• The case where the single remote party connected to the conference via NW
makes a conference in their node, thus having two conferences connected
via NW trunk will be handled like specified in the NW Conference and Station
Conference Features. They state that when two conferences are linked via a
NW connection, the user interface shall operate as two independent
conferences. In this case, Call Processing for the DTMF dialing feature will
transport the DTMF feature indicator when only one side is in a conference
state.
A31003-H3170-S103-6-7620, 02/2019
dtmf_usage_en.fm
DTMF Dialing
Feature Description
31.1.6 Feature Activation when DTMF signaling is

active
Feature activations that use a keypad access code during local through-connect
states shall not work if the DTMF signaling is activated.
In the OpenScape 4000, when the DTMF signaling is activated on the line, any
access code will be considered as keypad dialed numbers and will be converted
into DTMF signaling.
31.1.7 Affected Talk States

As definition, the station DTMF signaling flag will be active only in basic through-
connect talk states, when a station device requires the DTMF signal from it’s local
partner. This flag will be effective while the station is in direct conversation with
another device. For this reason, it will be considered only in the mandatory talk
states, in which DTMF signaling is frequently used.
The DTMF mandatory talk states are:
– Basic A-B talk state.
– Both A or B Pty talk consultation mode.
– Consultation out of a conference.
– Camped-on talk state.
– 3-Pty and 4-Party conference talk state.
IMPORTANT: Toggle after consulting out of conference. Toggle,and or 2nd.

consultation will not be supported in conference scenarios for the DTMF in
conference feature . These states may also represent conference talk states,
but they will not be supported , in addition it does not make sense to toggle a
call which has an IVR involved (this is the typical situation in which DTMF
dialing is required).
For any other states (e.g: ACD Silent Monitoring) the DTMF signaling/dialing
feature is not in effect.
31.1.8 Digit Displays

– in trunk connections => digits will be shown based on the RICHT
configuration.
A31003-H3170-S103-6-7620, 02/2019
dtmf_usage_en.fm
DTMF Dialing
Service Information
– other connections (normal talk, conference talk, consultation talk, etc) =>
digits will NOT be shown.

This feature enhancement is intended for the global marketplace.
31.3 Generation (example)

The configuration of the DTMF dialing feature can be done either in a station
basis or in a trunk (route) basis.
31.3.1 DTMF dialing configuration - Station basis

To set a station to require DTMF signaling, the parameter DTMFCTRD (AMO
SBCSU) must be set to YES or the parameter DHPAR (AMO SCSU) must be set
to DTMFST.
To set a station to block local DTMF signaling while in conference, the parameter
DTMFBLK (AMOs SCSU and SBCSU) must be set to YES.
Both configurations can be done while creating a station, or if the station is

already created it can be done by the AMO action CHANGE. For example:
• To set the station 3257 as requiring DTMF signaling and do not blocking
DTMF signaling while in conference, the following AMO command can be
used:
CHA-SBCSU:STNO=3257,DTMFCTRD=YES,DTMFBLK=NO;
• To set the analog station 2201 as requiring DTMF signaling and blocking local
DTMF signaling while in conference, the following AMO command can be
used:
CHA-SCSU:STNO=2201,SPEC=SUFDIAL(or
SOD),DHPAR=DTMFST,DTMFBLK=YES;
31.3.2 DTMF dialing configuration - Trunk (route)

basis
To set a route to require DTMF signaling, the parameter DTMFCNV (AMO
RICHT) must be set. The DTMFCNV (DTMF conversion) options are:
– FIX activate fixed dtmf conversion;
A31003-H3170-S103-6-7620, 02/2019
dtmf_usage_en.fm
DTMF Dialing
Relevant AMOs
– SUFDIAL dtmfcnv activated through suffix dialing (AMO

WABE:DAR=DTMFCONV);
– WITHOUT dtmfcnv or dtmfdisp not applicable.
The AMO parameters DTMFDISP, DTMFTEXT and DTMFPULS only indicate

how the pressed digits will be shown, what is the text message shown after the
connection and what is the DTMF signaling pulse/pause ration for outgoing trunks
(routes).
31.4 Relevant AMOs
AMO Parameter Language Description/Beschreibung

/Sprache
SBCSU MFVGSTRT d Dieser die Leitungstechnik (DH) betreffende
Parameter ist auf JA zu setzen, wenn die
betreffende Endstelle im Gesprächszustand
von der Gegenstelle MFV-Töne empfangen
soll.
DTMFCTRD e This device handler parameter shall be set to
YES for the station, if this station requires to
receive DTMF tones from the call partner
while in talk.
SBCSU MFVBLK d Dieser Parameter sperrt die akustische
Signalisierung von MFV-Signalen im
Konferenzzustand. Hinweis: Gesperrt
werden können nur lokal erzeugte MFV-
Töne.
DTMFBLK e This parameter is able to block a station to
hear DTMF tones while in conference. Note:
only DTMF tones generated locally can be
blocked.
SCSU DHPAR d Dieser die Leitungstechnik (DH) betreffende
Parameter ist auf MFVTLN zu setzen, wenn
eine Endstelle im Gesprächszustand MFV-
Töne von der Gegenstelle empfangen
können soll.
DHPAR e This device handler parameter shall be set to
DTMFST for the station, if this station
requires to receive DTMF tones from the call
partner while in talk.
SCSU MFVBLK d Dieser Parameter sperrt die akustische
Signalisierung von MFV-Signalen im
Konferenzzustand. Hinweis: Gesperrt
werden können nur lokal erzeugte MFV-
Töne.
A31003-H3170-S103-6-7620, 02/2019
dtmf_usage_en.fm
DTMF Dialing
Relevant AMOs

/Sprache
DTMFBLK e This parameter is able to block a station to
hear DTMF tones while in conference. Note:
only DTMF tones generated locally can be
blocked.
SCSU WAHL d Wird dieser Parameter auf MFV gesetzt, ist
das analoge Gerät in der Lage, MFV-Signale
zu verarbeiten.
DIAL e Set to DTMF allows the analog device the
capability of dual tone multi-frequency
signals.
WABE KZP d Der Kennzahlpunkt MFVUMS (Aktivierung
der MFV-Umsetzung bei der Wahl ins
öffentliche Netz) wird für abgehende
Amtsleitungsverbindungen und für
eingehende Amtsleitungsverbindungen mit
MFV-Umsetzung = Nachwahl gesetzt.
DAR e The digit analysis result DTMFCONV
(activations of dtmf-conversion when dialing
to public network) is used for outgoing trunk
calls and for incoming trunk calls with suffix
dialing dtmf-conversion set.
RICHT MFVUMS d Dieser Parameter legt die Kennzahl für die
MFV-Umsetzung bei abgehenden
Richtungen wie folgt fest.
FIX = fixe MFV-Umsetzung einschalten;
NAWA = MFVUMS wird durch Nachwahl
aktiviert;
OHNE = keine Verwendung von MFVUMS
bzw. MFVANZ.
DTMFCNV e This parameter determines the dtmf
conversion code for outgoing routes. It can
be:
FIX activate fixed dtmf conversion;
SUFDIAL dtmfcnv is activated through suffix
dialing;
WITHOUT dtmfcnv or dtmfdisp not
applicable.
RICHT MFVANZ d Dieser Parameter bestimmt die Anzeigeform
bei der MFV-Umsetzung für abgehende
Richtungen.
DTMFDISP e This parameter determines the display mode
for dtmf conversion for outgoing routes.
RICHT MFVPULS d Dieser Parameter bestimmt das Impuls-/
Pauseverhältnis für Codeumsetzer
abgehender Richtungen.
DTMFPULS e This parameter determines the pulse/pause
ratio of codetransmitter for outgoing routes.
A31003-H3170-S103-6-7620, 02/2019
dtmf_usage_en.fm
DTMF Dialing
Relevant AMOs

/Sprache
RICHT MFVTEXT d Dieser Parameter bestimmt, welcher Text bei
der MFV-Umsetzung für abgehende
Richtungen auf Endgeräte-Displays
angezeigt wird.
DTMFTEXT e This parameter determines which text will be
shown on device display for dtmf conversion
for outgoing routes.
A31003-H3170-S103-6-7620, 02/2019
dtmf_usage_en.fm
DTMF Dialing
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
ecmaqsig_en.fm
ECMA QSIG Protocol
General
32 ECMA QSIG Protocol
32.1 General
The ECMA1 QSIG protocol is based on the European ETSI standard (see Figure
20). A variation of supplementary services supporting the ETSI standard was
implemented and tested (see Table 7).
In the meantime, the European Standardization Committee ETSI has released

edition 2 (following the ISO standard). The coding of the ETSI edition 1
supplementary services implemented is not compatible with ETSI edition 2 (see
Table 6). A new protocol variant ECMAV2 was incorporated with the same feature
range as the predecessor (see Figure 20).
The worldwide accepted standardization committee ISO/IEC (International

Standardization Organization/International Electrotechnical Commission)
included the QSIG standard in the standards catalogue. The coding of the ETSI
edition 1supplementary services is not compatible with ISO/IEC edition 1.
Consequently, a new protocol (PSS1V2) was incorporated with the same features
as the predecessor (see Figure 20).
The QSIG protocol "CorNet NQ V2.1/V2.2/V2.3" describes private signaling

based on the ISO standard on one hand, and signaling based on the ETSI
standard’s Basic Call (edition 3) and Supplementary Services (edition 2) on the
other.
IMPORTANT: The private CorNet N elements are no longer transferred in the

protocol. This means that the CorNet-N-specific features no longer work.
Use the ECMA1 protocol variant to network Hicom 300 E V2.0 with an
OpenScape 4000.
CORNV33 is available for coupling an OpenScape 4000 to CorNet N networks

with Hicom 300 V3.3.
A comparison of the various releases is required for the correct use of the protocol
variants (ECMA1, PSS1V2 and ECMAV2) for networking an OpenScape 4000
with a third-party PINX (see Table 6).
The continuity of the individual features on the reference points S/T and Q over
the various protocols is shown in Table 7.
A31003-H3170-S103-6-7620, 02/2019
ecmaqsig_en.fm
ECMA QSIG Protocol
General
OpenScape 4000
CorNet-NQ/V2.0a
ECMA1
ETSI
ETSI-PINX
Public ISDN
DSS1
ECMAV2
ETSI
CorNet-NQ/V2.1/V2.2/V2.3
Public PRI
ETSI-PINX
PSS1V2
ISO-PINX
CORNUS
ISO
PBXXX iSDX
CorNet-N
existing CorNet networks
PNE PBXXX CSG
PACT Systems
DPNSS1 Standard 3
iSDX
EMS601
OMNI, ...
Figure 20 Range of protocol variants
A31003-H3170-S103-6-7620, 02/2019
ecmaqsig_en.fm
ECMA QSIG Protocol
General
Standards CorNet - NQ V2.0 CorNet - NQ V2.1/V2.2/V2.3

OpenScape 4000 ECMA1 ECMAV2 PSS1V2
Protocol variant
BC Basic Call ETS 300 172 Jan. ETS 300 172 ISO/IEC
SUB 1994 Nov. 1995 11572:1996(E)
Second Edition Third Edition Second Edition
Draft Amendment 1 
to ISO 11572
Draft Amendment 2 
to ISO 11572
Transit Counter
ANF
GF Generic Functions ETS 300 239 ETS 300 239 ISO/IEC
HOLD June. 1993 Nov. 1995 11582:1995(E)
First Edition Second Edition First Edition
Circuit-mode multi- ISO/IEC
rate bearer 11584:1996(E)
services First Edition
CNIP/ Name identification ETS 300 238 June ETS 300 238 ISO/IEC
R supplementary 1993 Nov. 1995 13868:1995(E)
CONP/ services First Edition Second Edition First Edition
R
(E) CT Call transfer ETS 300 261 Nov. ETS 300 261 ISO/IEC
supplementary 1993 Nov. 1995 13869:1995(E)
services First Edition Second Edition First Edition
CCBS Call completion ETS 300 366 Jul. ETS 300 366 ISO/IEC
CCNR supplementary 1994 Nov. 1995 13870:1995(E)
services First Edition Second Edition First Edition
CFB Call diversion ETS 300 257 Nov. ETS 300 257 ISO/IEC
CFNR supplementary 1993 Nov. 1995 13873:1995(E)
CFU services First Edition Second Edition First Edition
CFPR
PR Path replacement ETS 300 259 Nov. ETS 300 259 ISO/IEC 13874:
additional network 1993 Nov. 1995 1995(E)
feature First Edition Second Edition First Edition
CLIP Identification ETS 300 173 Dec. ETS 300 173 ISO/IEC 14136:
CLIR supplementary 1992 Mai 1996 1995(E)
COLP services First Edition Second Edition First Edition
COLR
CO Call offer ETS 300 362 Dec. ISO/IEC ISO/IEC
supplementary 1994 14843:1996(E) 14843:1996(E)
service First Edition
AOC-S Advice of charge ECMA 212, ISO/IEC DIS ISO/IEC DIS 15050
AOC-D supplementary Dec.1994 15050
AOC-E services
Table 6 Assignment of implemented Supplementary Services to the ETSI/

ISO Standards
A31003-H3170-S103-6-7620, 02/2019
ecmaqsig_en.fm
ECMA QSIG Protocol
General
Standards CorNet - NQ V2.0 CorNet - NQ V2.1/V2.2/V2.3

OpenScape 4000 ECMA1 ECMAV2 PSS1V2
Protocol variant
MWI Message waiting ECMA 242, ISO/IEC 15506 ISO/IEC 15506:
indication June 1996
supplementary
service
Table 6 Assignment of implemented Supplementary Services to the ETSI/

ISO Standards
ETSI & Qsig Supplementary Central Office OpenScape 4000

Services (DTAG)
DSS1- DSS1- DSS1- DSS1- DSS1- PSS1-
AnlAs MgAs AL AnlAs MgAs Qsig
Number & Identification Services:
DDI Direct Dialing In + na + + na na
PNP Privat Numbering Plan na na na na na +
MSN Multiple Subscr. Number na + na na + na
CLIP Calling Line Identific. + + + + + +
Pres.
CLIR Calling Line Identific. + + + + + +
Restr.
COLP Connected Line Ident. + + + + + +
Pres.
COLR Conn. Line Ident. Restr. + + + + + +
CNIP/R Calling Name Ident. Pres. na na na na na +1
CONP/ Connected Name Ident. na na na na na +2
R Pres.
MCID Malicious Call + + + - - nq
Identification
SUB Sub- Addressing + + + + + +
Call Offering Services:
(E) CT (Explicit) Call Transfer + + - - +3 +
PR Path Replacement na na na na na +
CFB Call Forwarding Busy + + - - + +
CFNR Call Forwarding No Reply + + - - + +
CFU Call Forwarding + + - - + +
Uncondit.
CFPR Call Forw. Partial + na + - na +
Rerouting
CD Call Deflection + - na + + na
Table 7 Summary of ETSI-DSS1 & PSS1 Supplementary Services with

OpenScape 4000
A31003-H3170-S103-6-7620, 02/2019
ecmaqsig_en.fm
ECMA QSIG Protocol
General

Services (DTAG)
CO Call Offer na na na na na +
Call Completion Services:
CW Call Waiting na + na na + na
HOLD Call Hold +4 + -5 -6 + +
CCBS Compl. Calls Busy + + + + + +
Subscr.
CCNR Compl. of Calls on No + + - - - +
Reply
Multiparty Services:
CONF Add- on Conference + + - - - -
3PTY Three Party Service na + na na + -
MMC Meet- Me Conference - - - - - -
Community of Interest Services:
CUG Closed User Group + + - +7 - nq8
Charging related Services:
AOC- S Advice of Charge at - - +9 - - -
Setup
AOC- D AOC during the Call + + + + + +
AOC- E AOC at the End of the + + + + + +10
Call
Additional Inform. Transfer
Services:
UUS1i User- User Sign. Serv. 1 + + + + + +
implicit
UUS1e User- User Sign. Serv. 1 - - - - - -
explicit
UUS2 User- to- User Sign. - - - - - -
Service 2
UUS3 User- to- User Sign. + + + + + +
Service 3
Other:
TP Terminal Portability na + na na - na
FPH Freephone - - - - - na
MWI Message Waiting - - - - - +
Generic functional protocol:
GF Generic functional + + + + + +
protocol

OpenScape 4000
A31003-H3170-S103-6-7620, 02/2019
ecmaqsig_en.fm
ECMA QSIG Protocol
General

Services (DTAG)
GF- KP Generic keypad protocol - + - - ? na
for the Support of SS

OpenScape 4000
1 Display dependent on the Pres Ind of the assigned number
2 Display dependent on the Pres Ind of the assigned number
3 "implicit request“ only
4 Transmission of the "Notify“ message
7 for the ’FUEV‘ feature only
8 for the ’FUEV‘ feature only
9 not based on "per call“
10 not "unsolicited“ call data
Abbreviations:
DTAG = Deutsche Telecom AG AnlAs = (Sub-) system interface

AL = Trunk MgAs = Point-to-multipoint interface
+ = implemented - = not implemented
na = not applicable nq = supported over CorNet-NQ V2.1
A31003-H3170-S103-6-7620, 02/2019
ecmaqsig_en.fm
ECMA QSIG Protocol
QSIG Protocol Modifications
32.2 QSIG Protocol Modifications
32.2.1 B-channel negotiation
In the CO direction, the

OpenScape 4000 is always the
SLAVE and preferred (ready for
negotiation).
MASTER = NO (exclusive)
BCNEG=YES (preferred)
DEVICE=S0CONN/S2CONN
S0/S2
For Cornet N For Cornet N
BCNEG=NO BCNEG=YES
(exclusive) (preferred)
DEVICE=S0CONN/ DEVICE=S0CONN/
S2CONN S2CONN
For Cornet NQ/ For Cornet NQ/QSIG
QSIG CCHDL= SIDEB
CCHDL= SIDEA (exclusive)
(exclusive) and and COT BKNE must
COT BKNE must be be set
set
The parameter BCNEG is used for controlling B-channel negotiation.

Connections that are set up afterwards with "exclusive" are not ready for
negotiation. In contrast, lines set up with "preferred" are ready for negotiation and
give precedence to exclusive connections.

ETS 300 172 describes how to resolve collisions. To do this, one side of a link
must be declared the A-side and the other side the B-side. A call from the A-side
to the B-side has precedence in this configuration (in the event of an exclusive/
exclusive or preferred/preferred collision). The necessary declaration is set with
the AMO TDCSU.
A31003-H3170-S103-6-7620, 02/2019
ecmaqsig_en.fm
ECMA QSIG Protocol
QSIG Protocol Modifications
32.2.3 AMO Changes

Language
CTIME AOCT1 d UEBERWACHUNG DER ANTWORT AUF
CHARGE REQUEST
AOCT1 e ANSWER SUPERVISION OF CHARGE
REQUEST
AOCT2 d UEBERWACHUNG DER ANTWORT AUF GET
FINAL CHARGE
AOCT2 e ANSWER SUPERVISION OF GET FINAL
CHARGE
COT BKVE d B-Kanalverhandlung
BCNE e B-Channel Negotiation
TDCSU CCHDL d ASEITE
BSEITE
OHNE
CCHDL e SIDEA
SIDEB
DONT
32.2.4 Instructions for generation

Example
CHANGE-TDCSU:DEV=S2CONN,PEN=<ltg-ltu-slot-
cct>,BCGR=b,CCHDL=SIDEA;
Default value: DONT
Notes:
Please note that B-side stations were configured differently by the carrier.
The COT parameter BCNE must be set for lines using the QSIG protocol so
that in the event of a collision, both calls are successfully connected, provided
there are B channels available.
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Feature Description
33 EDSS1 System Interface / Trunk Interface

Remote PBXs can be connected using the EDSS1 trunk interface. In this case,
the OpenScape 4000 functions just like a public EDSS1 interface (Germany),
which has fewer features.
SLAVE
MASTER
Remote PBX
S0/S2 OpenScape 4000 300 E
 EDSS1FRG
Features
EDSS1NET
DDI Direct dialling in

CLIP -> Display of A STNO
CLIR -> No display of ASTNO
COLP ->Display of BSTNO
COLR -> No display of BSTNO
AOC-D -> Call charges during call 
MCID -> Call tracing
UUS -> D channel data transmission
Remote PBX CCBS -> Callback on busy
CFx -> Call forwarding
 EDSS1FRG
S0/S2
EDSS1NET
The EDSS1NET protocol should only be used if the QSIG or Cornet N protocols
cannot, or should not, be used, since the provided network-wide features will be
limited.
During network planning pay special attention to any PBXs connected using the
EDSS1NET protocol: unlike QSIG, the networked partners when using EDSS1
are not equal. The master, for example, can send call information to the slave but
not vice versa.
33.2 User Interface

The EDSS1-T interface handles like a basic (Telekom) access.
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Service Information

• The point-to-multipoint interface is a feature in its own right and not part of the
system interface.
• The EDSS1-T network features support the ETSI protocols.
• Adjustments for other providers or countries have not yet been implemented,
but can be realised at a later date.
• The following features were implemented:
– Direct Dialing In on the S0 or S2 interface.
– Calling Line Identification Presentation (CLIP) / Display of the A station

number.
– Call Screening is supported with regard to E.164 addressing. This allows

the validity check of the CLIP received on this line. Unambiguous Call
Screening using CLIP is highly important, as the customer is assigned the
call charges.
– Calling Line Identification Restriction (CLIR) / Calling stations‘s number

suppression at the called party.
– Connected Line Identification Presentation (COLP) / After CONNECT the

calling party sees the actual station number of the called party.
– Connected Line Identification Restriction (COLR) / Suppression of the

called party‘s line identification at the calling party.
– Malicious Call Identification (MCID) / Identification and registration.

During a trunk call the called PBX station can instigate the storage of
connection-related data in the ISDN CO. 
The facility message is then transparently transmitted with BA or PRA via
the DSS1 gateway system interface to the Telekom AG DSS1 interface.
– The following options can be activated in the ISDN CO for the system
interface:
– Malicious Call identification immediately (MCII) / all incoming and

outgoing calls via the Telekom interface are registered at the ISDN
CO.
– Malicious Call identification on request (MCIR) / calls and call

attempts are only registered, if MCID was specially activated using a
DSS1 gateway. All calls are registered, if MCID was activated in the
gateway system. Since a code must be dialled to activate MCID the
feature can only be used for ‘voice‘ services.
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Service Information
– User to User Signalling 1 implicit (UUS1Ii) / D channel user data

transmission between two users during connection setup (setup
message)and clear down. A maximum of 128 bytes can currently be
transmitted.
– User to User Signalling 3 (USS3) / D channel user information

messages transmission in active state. To prevent network
overloading, every user with UUS3 authorization is assigned a certain
maximum number of user information messages per period
(Congestion Control).
– Advice of Charge During Call (AOC-D) / call charge information is

transmitted from the Telekom DSS1 access to the DSS1 gateway
system. The information is then processed in the OpenScape 4000
module INCDR. The currently valid call charges are then calculated
using tariff tables and Least Cost Routing information. The derived
call charges are then transmitted to the CP for further transmission to
the DSS1 gateway. Call charges are accounted according to the
INCDR regulations.
– AOC-E is included in AOC-D.
– The OpenScape 4000 does not only transmit call charge information
generated by the Telekom. AOC-D is also linked to the internal
OpenScape 4000 INCDR interface and therefore allows accounting
of PBXs connected via the DSS1 interface. 
Advice of Charge End of call / Transmission of call charge information
at the end of the connection.
– The ISDN trunk interface was expanded by the following features:
– Completion of Calls to busy Subscribers (CCBS) / Callback on busy. 

Callback on busy to external systems is supported.
– Call Diversion Partial Rerouting / Call forwarding using rerouting.
– Call Diversion Notification / Call forwarding information is signalled to

the involved stations.
• The features listed below supporting the DSS1 protocol, are either not
useable at the DSS1-T-network interface, or have not been implemented for
a system interface:
– Multiple Subscriber Number (MSN)/ Multiple subscriber number of a

basic access
– Terminal Portability (TP)
– Call Waiting (CW)
– Closed User Group (CUG)
– Three Party Service (3PTY)
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Service Information
– Conference Call Add-on (COF) / Conference call
– Freephone Service / 130 FPH Service
– Call Transfer (CT)
– User User Signalling 1 explicit (UUS1e) / Transmission of user data 1 e
– User User Signalling 2 (UUS2) / Transmission of user data 2
– Call Diversion (CFB, CFU, CFNR) for the entire T reference point
– Call Hold HOLD / Call parking
– Call Deflection (CD) / Call forwarding during call, activated by B station
– Advice of Charge Start (AOC-S) / Call charge information during

connection setup
• Any local features which do not affect the EDSS1-T protocol can be activated
(conference, callback to internal station, etc. ).
• The COT parameters FWDN/FNAN/CFVA/CBFN may not be set at the

system interface, as the connected functions at the T-reference point (on the
network side) are not defined.
• Interworking between different protocols
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Service Information
DSS1 trunk
OpenScape 4000
(TK AG)
DSS1- (system interface) Remote PBX
(DSS1)
(T-Network)
S2M or S0

DSS1 User
"Slave" *)
"Master"
*) The "Slave", like the "Master", can have access to the DSS1
trunk
Interworking:
OpenScape 4000
Remote
CorNet N
DPNSS1
OpenScape 4000
Switch behind OpenSca
PBXXX
4000 via DSS1
EWSD DSS1 trunk EDSS

DSS
EDSS 11 Remote
CorNet NQ
CorNet NQ
QSIG
OpenScape DSS 1 DSS 1 Remote
4000
DSS1 station.
• The OpenScape 4000 supports the following numbering plans for EDSS1-T:
unknown and E.164. PBXs networked using E-DSS1-T should always use
the numbering plan E.164.
• A COP parameter (IMEX) can define, whether or not for incoming calls with
TON=unknown (implicit STNO) the TON is to be modified into an explicit
STNO with a different TON.
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Relevant AMOs
33.4 Relevant AMOs
AMO Parameter Sparche/ Beschreibung/Description

Language
COP IMEX d "Implizit-to-Explizit" Ist der type-of-number in der
Ankommenden called-number gleich unknown
(dies entspricht einer impliziten Rufnummer), so
wird bei gesetztem Parameter versucht, die
Prefixe zu entfernen und die Nummer in eine
Explizite zu verwandeln (mit type-of-number
subscriber, national oder international).
IMEX e "Implizit-to-Explizit": If the type-of-number of an
incoming call = unknown (implicit station
number), the system tries to remove the prefixes
and change the number into an explicit station
number (with type-of-number= subscriber,
national or international), provided this
parameter is set.
RMSG d "Restart-Message-after-Startup" Nach dem
Aufbau der Layer 1 bis 3 wird als erstes eine
Restart Meldung an den Partner gesendet, um zu
Signalisieren, dass alle eingerichteten B-Kanäle
frei sind.
Achtung ! Diese Funktion darf nicht gleichzeitig
beim User und beim Netz aktiv sein, sonst
entstehen Probleme, bedingt durch die Restart-
Kollision.
RMSG e "Restart-Message-after-Startup": After layer 1 to

3 setup, a restart message is sent to the partner
PBX to signal that all configured B channels are
free.
Attention ! To avoid problems caused by the
restart collision, this function may not be active
simultaneously on the user and the network side.
COT BKVE d "B-Kanal Verhandlung für EDSS1" Dieser
Parameter (respektive diese Funktion) muss
sowohl beim User wie auch beim Netz aktiv sein.
Die bereits vorhandene B-Kanal-Kollisions-
Auflösung (preferred<->exclusiv und exclusiv<-
>prefered) wird dann ergänzt um die Fälle
exclusiv<->exclusiv und prefered<->prefered.
Achtung ! Dies funktioniert nur dann, wenn eine
Seite als Netz und die andere als User
eingerichtet ist (Leitungen mit der PROTVAR
EDSS1NET oder EDSS1NETR gelten als Netz-
Seite, alle anderen als User-Seite).
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Relevant AMOs

Language
BCNE e "B channel negotiation for EDSS1": This
parameter (or this function) must be active both
on the user and on the network sides. The
existing B channel collision solution (preferred<-
>exclusive and exclusive<->preferred) is then
enhanced by the cases exclusive<->exclusive
and preferred<->preferred.
Attention! This only works, if one side is
configured as network and the other as user
(lines using PROTVAR EDSS1NET or
EDSS1NETR are the network side, all others are
the user side).
BKDU d "B-Kanal Durchschalten mit Melden" Zur
Partneranlage, wo sich der A-Teilnehmer
befindet, wird immer Frei- oder B-Ton von
OpenScape 4000 gesendet. Erst beim Melden
des B-Teilnehmers werden die Sprech-Wege
End-End geschaltet. Dies verhindert, dass z. B.
der B-Teilnehmer Informationen sendet, ohne
dass der A-Teilnehmer Gebühren bezahlt (weil
die Gebührenzählung erst mit Melden aktiviert
wird).
BCCC e "B channel call completion before answer": The
OpenScape 4000 always sends free or busy
tones to the partner PBX with the A station. Only
when the B station answers the voice paths are
connected through. This way, the B station
cannot send information without any call charges
assigned to the A station (because call charging
is activated with answering).
TR6Q d "Querverkehr zu Anlage ohne Töne" In der Alert-
oder Disconnect-Meldung von der Partneranlage
wird anhand des Progressindicators geprueft, ob
ein Frei- oder B-Ton angelegt ist. Wenn nicht, so
wird in Richtung zum A-Teilnehmer ein eigener
Ton eingespeist. Sendet die Partneranlage eine
Setup-Meldung ohne Ziffern, so reagiert
OpenScape 4000 bei Voice und 3.1kHz-Audio
Verbindungen mit dem Anschalten von Wählton
(dies wird in der Setup-Ack-Meldung mit dem
Progressindicator signalisiert).
TR6T e "Tie lines to system without tones": The progress
indicator checks the Alert or Disconnect
message of the partner system, to see if a free or
busy tone is injected. If not, the system injects its
own tone in the direction of the A station. If the
OpenScape 4000 receives a setup message
without digits from the partner system, it injects
the dial tone for Voice and 3.1 kHz audio
connections (signalled by the progress indicator
in the setup ACK message).
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Relevant AMOs

Language
NCHD d "No-Charge-During-Call" Zur Partner-Anlage
werden nur AOC-E Informationen am Ende des
Gespräches gesendet.
NCHD e "No-Charge-During-Call": AOC-E information is
sent to the partner PBX at the end of the call.
UUS1 d "User-User-1i" Bei den Protokollen EDSS1NET
und EDSS1NETR wird eine UUS1i-Anforderung
nur dann akzeptiert, wenn der Parameter gesetzt
ist.
UUS1 e "User-User-1" The EDSS1NET and
EDSS1NETR protocols only accept a UUS1
query if this parameter is set.
UUS3 d "User-User-3" Bei den Protokollen EDSS1NET
und EDSS1NETR wird eine UUS3-Anforderung
nur dann akzeptiert, wenn der Parameter gesetzt
ist.
UUS3 e "User-User-3" The EDSS1NET and
EDSS1NETR protocols only accept a UUS3
query if this parameter is set. (E V3.0)
ETSC d "ETSI-Conform" Dort wo ETSC gesetzt wir,
werden nur noch UU-Informationen übertragen,
welche entsprechend dem ETSI-Protokoll
angefordert (requested) worden sind.
ETSC e "ETSI-Conform" If ETSC is set, only UU
information is transmitted which were requested
in accordance with ETSI protocol.
USBT d "UUS3 Anforderung vom B-Teilnehmer" Wird der
COT-Parameter USBT gesetzt, so ist dies auch
dem gerufenen Teilnehmer (B-Tln) gestattet
(Network Option).
USBT e "UUS3 Request from B Party" If the COT
parameter USBT is set, the B party can also
request UUS3 (Network Option)
USCC d "UUS3-Congestion-Controll" Ist USCC nicht
gesetzt, wird eine Überprüfung der Datenmenge
verhindert und unbeschränkt viele UU-
Informationen können übertragen werden
(wichtig für proprietäre Leistungsmerkmale wie
CMI, NW CHESE, ...).
USCC e "UUS3-Congestion-Control" If USCC is not set,
the data quantity is not checked. This allows
transmission of unlimited UU information
(important for proprietary features such as CMI,
NW CHESE, etc.)
USCD d "User-User-Call-Diversion" Wenn der COT-
Parameter USCD gesetzt ist, wird eine allfällige
UUS-Anfrage nicht zum Umleitziel weiter
geleitet.
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Relevant AMOs

Language
USCD e "User-User-Call-Diversion" If the COT parameter
USCD is set, the UUS query is not transferred to
the forwarding destination..
CCRO d "Call-Completition-Retention-Option" Wenn
dieser Parameter gesetzt ist, wird die Retention
Option eingeschaltet. Ansonsten wird bei erneut
besetztem B-Teilnehmer wie bis anhin
automatisch ein neuer Rückruf eingetragen.
CCRO wird nur gehend geprüft.
CCRO e "Call-Completion-Retention-Option" This
parameter activates the retention option.
Otherwise, a new callback is entered at the B
station if it becomes busy again. CCRO is only
checked for outgoing connections.
DIMSU DSS1SCRD d Anz. der Screening Datensätze bei E-DSS1
Verbindungen
e Number of Screening data records for EDSS1
connections.
DSS1SCRP d Anz. der Screening Patterns für E-DSS1
Verbindungen
Number of Screening Patterns for E-DSS1
connections
KNFOR TON d Neue Parameterwerte
INTERPRE ->Internationale Rufnummer mit
Prefix
NATIOPRE ->Nationale Rufnummer mit Prefix
e Neue Parameterwerte
INTERPRE ->Internationale Rufnummer mit
Prefix
NATIOPRE ->Nationale Rufnummer mit Prefix
SCRE d Neuer Parameterwert
TRANSP -> Transparent - Screening indic. bleibt
unverändert
e New parameter
transparent - screening indicator remains
SENDCALL d Senden der Calling Number
SENDCALL e send calling number
SENDCONN d Senden der Connected Number
SENDCONN e send connected number
OVRDCAT d Override Category
Anzeige der geheimen calling/connected RNR J
/N
OVRDCAT e override category
display secret calling / connect number Y/N
LODR LWREL d SENDCOMP -> das schicken von Wahlblöcken
ist abgeschlossen
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Relevant AMOs

Language
e SENDCOMP -> sending number blocks
completed
PRODE PROTVAR d Neue bzw. geänderte Parameterwerte:
ECMAV2 -> Protokoll qsig etsi ETS 300 172 3rd.
ECMAV2R -> Protokoll qsig etsi ETS 300 172.
PSS1V2 -> Protokoll qsig iso ISO/IEC 11572
PSS1V2R -> Protokoll qsig iso ISO/IEC 11572
EDSS1NET ->Protokoll EDSS1 net side
EDSS1NETR -> Protokoll EDSS1 net side
Reserve
e Neue bzw. geänderte Parameterwerte:
EDSS1NET ->Protokoll EDSS1 net side
EDSS1NETR -> Protokoll EDSS1 net side
Reserve
SCREN d Neuer AMO
Festlegen von Nummernbereichen und deren
Prüfung
e New AMO
Screening of numbering ranges
TDCSU PROTVAR d Neue Parameterwerte:
EDSS1NET -> EDSS1 net side
EDSS1NETR -> EDSS1 -> net side Reserve
e New parameter values:
ECMAV2 -> protocol QSIG ETSI ETS 300 172
3rd.
ECMAV2R -> protocol QSIG ETSI ETS 300 172.
PSS1V2 -> protocol QSIG iso ISO/IEC 11572
PSS1V2R -> protocol QSIG iso ISO/IEC 11572
EDSS1NET -> EDSS1 net side
EDSS1NETR -> EDSS1 -> net side Reserve
UUSCCX d "User-User-Signalling-Congestion-Controll-
Counter-X" Jedem UUS3 berechtigten
Teilnehmer steht eine bestimmte maximale
Anzahl UU-Informations-Meldungen (Zähler-X)
pro Zeiteinheit (UUS3T2) zur Verfügung.
UUSCCX e "User-User-Signalling-Congestion-Control-
Counter-X"
Every user with UUS3 authorization is assigned
a certain maximum number of UU information
messages (counter-x) per period (UUS3T2).
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
Configuration of the EDSS1 system interface with Screening

Language
UUSCCY d "User-User-Signalling-Congestion-Controll-
Counter-Y" Anzahl UU-Informations-Meldungen
(Zähler-X) pro Zeiteinheit (UUS3-T2) zur
Verfügung. Unabhängig davon, ob er sein
Kontingent genutzt hat oder nicht, wird in einem
regelmässigen Zeitinterwall (UUS3T2) das
verbleibende Kontingent um eine bestimmte
Anzahl (Zähler-Y) aufgestockt bis maximal die
ursprüngliche Menge (Zähler-X) erreicht ist.
UUSCCY e "User-User-Signalling-Congestion-Control-
Counter-Y"
Every user with UUS3 authorization is assigned
a certain maximum number of UU information
messages (counter-x) per period (UUS3T2).
Regardless of whether or not the user has used
his assigned quantity, the remaining number of
messages is increased by a certain number
(counter-y) in periodic intervals (UUS3T2) until
the original maximum number of messages
(counter-x) is reached.
CTIME UUS3T1 d "User-User-Signalling-Timer-1" Der Timer
UUS3-T1 bestimmt, wie lange die Netzwerkseite
auf die Antwort einer ausgesandten UUS-
Anfrage warten soll.
UUS3T1 e "User-User-Signalling-Timer-1" The UUS3-T1
timer defines the time the network side waits for
the response to a transmitted UUS request.
UUS3T2 d "User-User-Signalling-Timer-2" Jedem UUS3
berechtigten Teilnehmer steht eine bestimmte
maximale Anzahl UU-Informations Meldungen
pro Zeiteinheit zur Verfügung, welche durch den
Timer UUS3T2 bestimmt wird.
UUS3T2 e "User-User-Signalling-Timer-2" Every user with
UUS3 authorization is assigned a certain
maximum number of UU information messages .
33.5 Configuration of the EDSS1 system interface with Screening
IMPORTANT: Verification of the calling and the called number is not required by
the system interface, as the station numbers are checked by the network provider
who replaces a wrong station number by a predefined number, if necessary. If
screening is not performed by the carrier the OpenScape 4000 will check the
numbers.
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
33.5.1 Configuration of the system interface
STNO 78072 ISDN/SUBSCR

With SCREENING the OpenScape 4000 with
STNO 78070 CALLING and the CALLED
ISDN/SUBSCR system interface
STNO is verified and
replaced by a default
Satellite PBX or value, if necessary. Protocol: EDSS1NET
server with
EDSS1FRG Clock: Master
interface Device: S0CONN / 
SO / S2 S2CONN
NNO 1-89-410 SMD: y
numbering range: Master y
0000-9999
NNO: 1-89-410
ISDNCC 49
ISDNAC 89
ISDNLC 78062
All COS such as LCOS, COS, NNO etc.

must be specified at the trunk interface,
as these COS are not transmitted from
the sattelite PBX/server via the protocol.
The COT parameters FWDN/FNAN/
CFVA/CBFN may not be set in the COT
of the trunk interface.
The user and the network side must be configured separately using AMO
TDCSU.
Network side User side

Protocol EDSS1NET EDSGER
Connection S0CONN S0COD
ISDN STNO 78072 (ISDN E164 / SUBSCR) 78070 (ISDN E164 / SUBSCR)
• Allocate memory for AMO SCREN

ADD-DIMSU:DSS1SCRD=10,DSS1SCRP=30,TYPE=NET;
• Configure trunk groups and COT/COP parameters
ADD-BUEND:TGRP=140,NAME=EDSS1_TRUNK INTERFACE,NO=2;
ADD-
COT:COTNO=140,PAR=NTON&AEOD&FWDN&CBBN&BLOC&NLCR&TSCS&DFNN&NLR
D&CFTR&VCMN&BCNE;
ADD-COP:COPNO=140,PAR=L3AR;
• Configure circuit
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
EINR-TDCSU:ART=NEU,LAGE=1-02-079-
5,COTNR=140,COPNR=140,WABE=0,
VBZ=0,COS=90,LCOSS=7,LCOSD=7,SATZNR="DSS1 NETSIDE",ZLNR=40,
PROTVAR="EDSS1NET",SEGMENT=1,KNNR=1-89-410,FIDX=1,CARRIER=4, 
ZONE=LEER,COTX=140,AULX=5,GER=S0VERB, ANZ=1,
INBETR=J,BUNR=140,SUCHART=AUF,MASTER=JA,SMD=JA,CNTRNR=0,BKVER
=N;
• Configure the route to the external PBX. Node 1-89-410 NPI ISDN,
TON=Subscriber. For TON=national and international separate routes must
be configured, if required.
ADD-RICHT:MODE=LRTENEW,LRTE=140,LSVC=ALL,NAME=DSS1
NETSIDE,TGRP=140,DNNO=1-89-
410,ROUTOPT=NO,REROUT=NO,DTMFCNV=FIX,DTMFDISP=DIGITS,DTMFTEXT
="MFV_NW",PLB=YES;
• Configure LODR and LDAT AMOs to the node 1-89-410, NPI ISDN,
TON=Subscriber.
ADD-LODR:ODR=140,CMD=NPI,NPI=ISDN,TON=SUBSCR;
ADD-
LDAT:LROUTE=140,LSVC=ALL,TGRP=140,ODR=140,LAUTH=1,CARRIER=4,Z
ONE=EMPTY;
ADD-LDPLN:LDP=0-78070-X,LROUTE=140,LAUTH=1;
33.5.2 A station number verification (screening)

• Station number verification is not required for this function and need only be
configured if necessary.
• Configuration of the number verification for TON=Subscriber

If required, separate SCREEN data must be configured for TON=national and
international.
• A station number from 0000 to 9999 are transmitted in TON=Subscriber.

ADD-SCREN:TYPE=SCRPATT,SCRPPLAN=1,SCRP=78070XXXX;
• The default station number (DNO) is expanded by the ATND code (0) of the
external PBX.
EINR-SCREN:ART=SCRDATEN,UKNNR=1-89-
410,DRNR=780700,DRNRTYP=SUBSCR,
ARNRTYP=SCREEN,ARNRANZ=CLIPSTD,BRNRTYP=KEINSCR,BRNRANZ=COLPST
D, SCRPPLAN=1,SCRPTYP=SUBSCR;
A31003-H3170-S103-6-7620, 02/2019
dss1_en.fm
33.5.3 EDSS1 Use Side

• A OpenScape 4000 at the EDSS1 system interface must be configured as a
OpenScape 4000 to the public CO.
ADD-BUEND:TGRP=140,NAME=EDSS1_CO,NO=2;
ADD-
COT:COTNO=140,PAR=NTON&AEOD&FWDN&CBBN&BLOC&NLCR&TSCS&DFNN&NLR
D&CFTR&VCMN&BCNE;
ADD-COP:COPNO=140,PAR=L3AR;
EINR-TDCSU:ART=NEU,LAGE=1-02-103-
5,COTNR=140,COPNR=140,WABE=0,VBZ=0,
COS=90,LCOSS=7,LCOSD=7,SATZNR="DSS1
NETSIDE",ZLNR=10,PROTVAR="EDSBRD",SEGMENT=1,TCHARG=N,ANZUNT=0
,KNNR=1-89-110,ALARMNR=0,FIDX=1,CARRIER=4, ZONE=LEER,
COTX=140,AULX=5,GER=S0AMT,ANZ=1,INBETR=J,
BUNR=140,SUCHART=AUF;
• Configure the route to the external PBX. Node 1-89-410 NPI ISDN,
TON=Subscriber.
If required, separate routes must be configured for TON=national and
international.
ADD-LODR:ODR=140,CMD=NPI,NPI=ISDN,TON=SUBSCR;
ADD-RICHT:MODE=LRTENEW,LRTE=140,LSVC=ALL,NAME=DSS1
USERSIDE,TGRP=140,DNNO=1-89-
110,REROUT=NO,DTMFCNV=FIX,DTMFDISP=DIGITS,DTMFTEXT="DTMF",DTM
FPULS=PP300,PLB=YES;
ADD-
LDAT:LROUTE=140,LSVC=ALL,TGRP=140,ODR=140,LAUTH=1,CARRIER=4,Z
ONE=EMPTY;
A31003-H3170-S103-6-7620, 02/2019
euint_en.fm
34 EURO-ISDN Exchange Interface

The OpenScape 4000 can be connected as an NT2 unit at the V reference point
(TO basic access and T2 primary rate access) of the European EURO-ISDN
network.
S T
TE1
S0 T0
TE1 NT2 NT1

S2 T2
TE1 = Terminating equipment with ISDN interface

NT1, NT2 = Network terminations
S,T = Reference point
Figure 21 Reference model
The supplementary services supported on the exchange interface onward are as

follows:
• Direct Dialing In (DDI) 

An exchange subscriber can dial straight through to a OpenScape 4000 user.
In this case the OpenScape 4000 user receives a different type of call
signalling (trunk call) from that used for inside calls.
• Calling Line Identification Presentation (CLIP) 

The number of the calling party appears on the display at the called terminal.
The number is displayed during the ringing phase.
• Calling Line Identification Restriction (CLIR) 

The calling party can suppress the call number display by pressing a key at
the start of an outpoing call.
• Connected Line Identification Presentation (COLP) 

The number of the user who has actually been accessed is indicated on the
display of the calling terminal. The number is displayed when the connection
is switched through.
• Connected Line Identification Restriction (COLR) 

Display of the user who has been accessed is suppressed by the called
terminal.
• User-to-User Signaling (UUS) 

Communication between terminals.
A31003-H3170-S103-6-7620, 02/2019
euint_en.fm
Direct Dialing In (DDI)
• Subaddressing (SUB) 
The ISDN subaddress is used for the more precise addressing of
subcomponents within the user equipment selected with the ISDN number.
The following figure illustrates the structure of the ISDN addres:
ISDN-adress
ISDN-Number (without discriminating digit sequences)
Country code
Network identifier/area code
Subscriber number
Local destinatioon code
Station number
ISDN subaddress
Figure 22 Structure of the ISDN address
34.1 Direct Dialing In (DDI)

DDI enables users to call parties in private ISDN networks directly via public ISDN
using the ISDN numbering plan. The ISDN exchange sends the DDI number to
the private ISDN. The DDI number consists either of the complete ISDN number
(country code, area code and subsciber number) or part of it, the minimum being
the subscriber number. Which parts are transmitted varies from one exchange to
another. The discriminating digit sequences for national and international calls
(e.g. 00 and 0 or 16 in France for inter-zone calls) are not part of the DDI number
and are therefore not provided by the exchange. 
The following components of the home ISDN NUMBER must always be specified
in connection with EURO-ISDN trunk circuits:
• Country code (e.g. 49 for Germany)
• Area code (e.g. 89 for Munich)
• Local destination code (e.g. 7007)
The discriminating digit sequences for national and international calls must also
be provided:
• International prefix (e.g. 00)
• National prefix (e.g. 0)
A31003-H3170-S103-6-7620, 02/2019
euint_en.fm
Calling and Connected Number Displays (CLIP/CLIR and COLP/COLR)
The components of the the home ISDN number are required for DDI so that the
DDI number sent by the exchange can be reduced to the simple subscriber
number, which in turn is necessary for correct digit analysis in the OpenScape
4000 system.
Example: Configuration of trunk circuits on the T2 primary rate access.
• Assign module DIU (2 PCM30 routes):

ADD-BCSU:MTYPE=DIU,LTG=gg,LTU=uu,SLOT=bbb,PARTNO=Q2096-X;
• Assign trunk group for 30 B-channels:
ADD-BUEND:TGRP=x,NAME="ISDN-S2AMT",NO=30;
• Assign S2 trunk circuit with 30 b channells in module
ADD-TDCSU:OPT=NEW,PEN=gg-uu-bbb-0/1,COTNO=number,
COPNO=number,LCOSV=number,LCOSD=number,PROTVAR=ETSI, 
ISDNIP=00,ISDNNP=0,ISDNCC=49,ISDNAC=89,
ISDNLC=722,NNO=number,DEV=S2COD,TGRP=x,BCGR=1;
Example: Configuration of trunk ciruits on the T0 basic access.
• Assign module STMD (8 xS0 interfaces)

ADD-BCSU:MTYPE=DIU,LTG=gg,LTU=uu,SLOT=bbb,PARTNO=Q2174-X;
• Assign trunk group for 8 x S0-interfaces (2 B-channels ea.):
ADD-BUEND:TGRP=y,NAME="ISDN-S0AMT",NO=16;
• Assign 8 S0 trunk circuits in module
ADD-TDCSU:OPT=NEW,PEN=gg-uu-bbb-0,COTNO=number,
COPNO=number,LCOSV=number,LCOSD=number,PROTVAR=ETSI, 
IISDNIP=00,ISDNNP=0,ISDNCC=49,ISDNAC=89,ISDNLC=722, 
NNO=number,DEV=S0COD,NO=8,TGRP=y;
34.2 Calling and Connected Number Displays (CLIP/CLIR and COLP/COLR)

Connections via EURO-ISDN exchange lines transport various info-numbers in
as additional connection information, which include the "calling line information"
and the "connected line information" (respectively shortened to "calling number"
and "called number"). These info-numbers not only appear in the telephone
displays of the connection parties; many system features use these info-numbers
as destination numbers at later stages in a call setup, e.g. for recall, callback, etc.
For this reason, an Info-Number Signalling system exists (INS), whose function
is to ensure that any node-specific modification of these numbers for transport is
carried out in such a way that the info number string (including the necessary
route codes etc.) can be reconstructed by any system or node at any stage in the
connection setup path. Networks transport the info-numbers in explicit format
throughout, wherever possible. Explicit info-numbers do not contain the full
dialled number string, but only the root number and additional information
elements indicating the breakout codes, prefix codes, area codes, the numbering
A31003-H3170-S103-6-7620, 02/2019
euint_en.fm
plan identifier (NPI=ISDN for EURO-ISDN) and Type of Number (TON, i.e.
INTERNAT, NATIONAL or LOCAL). Since call number information of this type is
not suitable for display or further processing within a system or node, each node
converts incoming explicit calling number information into an implicit format for
internal purposes. The implicit calling number information will contain all the
appropriate code digits (breakout and prefix codes) and have the type of number
attribute TON = UNKNOWN. In the outgoing direction, the implicit format is
converted back into an explicit format. The conversion is always carried out with
the station number modification function, i.e. depends on AMO settings specific
to each node. The following example shows an ISDN exchange and a destination
node, with the intervening network.
Exchange
Dest Node Transit interface node
Stn Stn
I E I E I
E I E I E
Displa I
E
E I E
I
I Displa
I E E
Key: I/E = Implicit/Explicit, i.e. conversion in outgoing direction

E/I = Explicit/Implicit, i.e. conversion in incoming direction
Figure 23 Format dependant information number signalling
Two parallel methods exist for modifying the calling number information (calling
line number and connected line number): the new format-dependent station
number modification (AMOs KNFOR, KNPRE and TDCSU) and the ’old’ source/
destination-dependent method as administered with the KNMAT AMO. Hicom
300 E V1.0 nodes with the ISDN numbering plan (NPI=ISDN) should always use
the format-dependent method. To this end, the ISDN exchange must be assigned
a virtual node number in order to be able to configure the outgoing trunk groups
for routing (DNNO parameter of RICHT AMO) and incoming trunk groups for
identification (NNO parameter of TDCSU AMO). The own node number must
always be entered in the central PABX data administered with the ZAND AMO
(parameter NNO). The virtual node number must have the same hierarchical level
structure (i.e. single-level, 2-level or 3-level) as the NNO specified in the ZAND
AMO.
A31003-H3170-S103-6-7620, 02/2019
euint_en.fm
34.2.1 Format-dependent INS/STNO Modification in

Incoming Direction
The conversion of the calling number information from an explicit format into an
implicit one is carried out in two steps:
Step 1:
The incoming ISDN number (NPI=ISDN), which may be any type of number
(TON), is set to the lowest possible format (TON=UNKNOWN) with the aid of the
ISDN codes stored in the system (ISDNAC, ISDNCC and ISDNLC parameters of
TDCSU AMO). Since this conversion also takes place in transit nodes, these
codes must also be assigned to tie-lines with the TDCSU AMO, if these are used
to transport numbers of the ISDN numbering plan. If you do not want user
displays to show the converted numbers in the lowest possible format, you can
set an alternative format with the KNFOR AMO.
Step 2:
Depending on the type of number (TON), the modified (shortened) ISDN call
number (see step 1) is then supplemented with the national prefix
(TON=NATIONAL) and international prefix (TON=INTERNAT) as well as the
breakout code (only if TON is not equal to UNKNOWN). The following AMO
settings are necessary for this:
• Define the breakout codes in all network nodes, and prefix codes specific to
the home node, with the KNPRE AMO, as follows:
ADD-KNPRE:DPLN=0,NPI=ISDN,TON=INTERNAT,EXIT=0,PREFIX=00;
ADD-KNPRE:DPLN=0,NPI=ISDN,TON=NATIONAL,EXIT=0,PREFIX=0;
ADD-KNPRE:DPLN=0,NPI=ISDN,TON=SUBSCR,EXIT=0;
Since EURO-ISDN exchanges always transport the calling number information in
the explicit format defined by ETSI-E.164, the prefix settings in the TDCSU AMO
are not required (ISDNIP and ISDNNP).
34.2.2 Format-dependent INS/STNO Modification in

Outgoing Direction
The conversion of the calling number information from an implicit format into an
explicit one is also carried out in two steps:
Step 1:
With the aid of the KNPRE settings, any breakout codes or prefixes contained in
the implicit number are removed.
Step 2:
A31003-H3170-S103-6-7620, 02/2019
euint_en.fm
The modified/shortened number is then set to the highest format

(TON=INTERNAT) on the basis of the ISDN code settings in the TDCSU AMO. If
a destination node in the network, or the ISDN exchange, requires a lower format,
this can be set with the aid of the KNFOR AMO, in cases where this is possible.
34.2.3 COT-Parameters
Since the ISDN exchange cannot recognize node codes, the COT attribute
LWNC (line without node code) must be set for the eschange line.
• Add attribute to class of trunk of ISDN exchange line:

CHANGE-COT:COTNO=NUMBER,COTTYPE=COTADD,COTPPAR=LWNC;
The COT parameter DFNN (use virtual node number assigned to line) does not
need to be specified, since this function is automatically carried out by the system
for exchange lines. The COT parameter LIRU (line with implicit number) is only
significant in heterogeneous networks (see "INS Info-Number Signalling" chapter
of AMO Usage Examples for Networking). This attribute must always be set for
tie-lines to "old" systems and OEM systems, together with the appropriate
KNFOR settings for the ISDN exchange interfaces in these systems.
IMPORTANT: COT parameter LWNC only works in the outgoing direction, and
parameter DFNN only works in the incoming direction. COT parameter LIRU
works in both directions.
34.2.4 Handling of extension numbers unknown to

the exchange
The sending of extension numbers unknown to the ISDN exchange should be
avoided. In such a case a substitute number (e.g. the attentand console number)
is sent to the exchange. Configure the substitute extension number using KNMAT
AMO with the modification condition ERSNST (Substitute extension number).
CHANGE-KNMAT:NPI=ISDN,LEVEL=0,ONNO=<OpenScape 4000
node>,DNNO=<Trunk node>,MODCON=REPEXT,NUMEXT=<substitute
extension number>;
Assign the class of service DIDBLK to all stations unknown to the exchange (e.g.
all extension numbers beginning with 4):
CHANGE-COSSU:TYPE=COS,COS=14,AVCE=DIDBLK;
CHANGE-SCSU:STNO=4000&&4999,COS1=14,COS2=14;
If, for example, the substitute extension number (number of the attendant
console) is 722 1111 the extension number 4711 is substituted by
• the substitute number 722 1111 (COS DIDBLK is set)
A31003-H3170-S103-6-7620, 02/2019
euint_en.fm
while extension number 5711
• is substituted by 722 5711 (COS DIDBLK is not set). The rule to use the
substitute extension number also applies here, however, the last four digits
1111 are overwritten by 5711.
34.2.5 Classes of service OVCAT and SPECAR

There are two classes of service for CLIP and COLP (per service).
• OVCAT : Override category 

The number of the called/calling party is displayed at the 
called/calling party in spite of a "secret number" classmarking 
(this only applies to functional terminals).
• SPECAR: Special arrangement 

When a functional terminal sends its own call number to the 
system, the plausibility of this number is not checked 
(this applies to both directions of seizure).
A31003-H3170-S103-6-7620, 02/2019
euint_en.fm
A31003-H3170-S103-6-7620, 02/2019
featnet_en.fm
Features Available Throughout the Network
Call Forward/Forward No Reply
35 Features Available Throughout the Network
35.1 Call Forward/Forward No Reply

Call forwarding is possible throughout a private network (to other stations, servers
or code-calling systems), and even to public network subscribers. Call forwarding
cannot be enabled for the ISDN main station lines of a PABX. 
Call forwarding to public network subscribers is possible with the following
restrictions: VOICE service only, only for privileged users (special COS), and
number of dialled external digits must not exceed 22
• For call forwarding and forwarding on no answer throughout the network the
AMO COT has two values: FWDN and FNAN respectively.
ADD-COT:COTNO=number,PAR=FWDN&FNAN;
IMPORTANT: Forward no reply only for S0 / S2 circuits.
• Assign call forwarding to public network for voice service

ADD-COSSU:NEWCOS=number,AVCE=FWDNWK;
35.1.1 Call Forward/Forward No Reply with Open

Numbering Scheme
If call forwarding or no answer advance is activated at the called party’s station,
and the call is forwarded back to the caller’s home node, the route code prefix
must be suppressed. 
Enter route code of home node to be suppressed in the DPLN (DESTNO=1)
AD-WABE:CD=90,DAR=OWNNODE;
35.1.2 Call Forward/Forward No Reply after Transfer

If the partner cannot execute network-wide FWD/FNANS after transfer, this
feature must be prevented by setting the COT parameter NCTP in the S0/S2
trunk to this PBX.
CHA-COT:COTNO=number,COTTYPE=COTADD,PAR=NCTP;
Example:
Station A (Node 1) transfers a call to station B (Node 2) which has set FWD/
FNANS to station C (Node 3):
The connection is to station C is therefore established by Node 2 and not Node 1.
A31003-H3170-S103-6-7620, 02/2019
featnet_en.fm
Announcement Unit
Node 1 Node 2 Node 3
trunk PSE trunk trunk- S0/S2 trunk trunk

COT:
N
CO C
T
P
A
B C
35.2 Announcement Unit

Announcement unit for a node without exchange trunks
Seizure from all nodes is possible.
CO
002 RTECD
S0/S2
OpenScape OpenScape
RA
4000 4000
TGRP 33 RCLS
Node 1 Node 2
RA_CD 73
003 RTECD
S0/S2 TGRP 40
OpenScape
4000
Node 3
RA_CD 73
Figure 24 Announcement unit throughout the network, also via CO
For station users who want to access the announcement unit via incoming calls
from the exchange, the announcement code must be additionally assigned for the
"SAT" DAR in the DPLN (of the node with the trunks). 
For external stations, the route to the announcement unit must be formed with the
announcement unit code, the CPS 3&6 and the same group as for internal
announcement.
A31003-H3170-S103-6-7620, 02/2019
featnet_en.fm
Announcement Unit
In the COT of the S2 circuits, with which the node with the announcement unit is
seized via the exchange, the RCLS parameter must be set. Thus, CPS=6
(incoming trunk) is generated for the CO seizure type, which is required for
controlling the TCOM (first greeting text, then announcement text).
• Commands in node 1 (for example in above diagram)
– Assign the code for DAR=NETRTE as follows:

AD-WABE:CO=002,DAR=NETRTE;
– Assign announcement code for external stations
AD-WABE:CD=73,DAR=SAT;
– Assign announcement code for internal stations
AD-WABE:CD=73,CPS=2&4&5&7&8&9&10&11&12,DAR=NETW;
– Assign route for announcement code of internal stations to node 2
AD-RICHT:TYPE=CD,CD=002,CPS=0,SVC=ALL,TGRP1=33;
– Assign route for announcement code of external stations to node 2
AD-
RICHT:TYPE=CD,CD=73,CPS=3&6,SVC=ALL,TGRP1=33,PREFDGT1=73;
• Commands in node 2
– Assign announcement codes for internal and external stations

AD-WABE:CD=73,DAR=ANSCO; 
AD-WABE:CD=73,DAR=ANSINT;
– Assign code for DAR=NETRTE

AB-WABE:CD=003,DAR=NETRTE;
– Assign announcement code for internal stations
AD-WABE:CD=73,DAR=NETW;
– Assign route with DAR=NETRTE to node 2
AD-RICHT:TYPE=CD,CD=003,CPS=0,SVC=ALL,TGRP1=40;
Announcement unit for a node with exchange trunks

If the node with the TCOM also provides trunks, which are to be used by the other
nodes as well, with the same exchange code, proceed as follows since the digit
analysis result CO cannot be allocated CPS=6.
A31003-H3170-S103-6-7620, 02/2019
featnet_en.fm
Override, Camp-On, Transfer
CO CO 8 = CO
73 = SCONSCO
OpenScape S0/S2
OpenScape RA
4000 4000
"73" PREFDGT
Node 1 Node 2
8 = CO
Figure 25 Node with announcement unit and exchange trunks
In node 1, the exchange code of node 2 must lead to DAR CO, for example, and
be linked with the tie-trunk group; conversion to another code, e.g. 73, must be
performed. Conversion is done via digit prefixing with the RICHT AMO.
AD-WABE:CD=8,DAR=CO; 
AD-RICHT:TYPE=CD,CD=8,SVC=ALL,TGRP1=number,PREFDGT1=73;
In node 2 code 73 leads to the SAT digit analysis result and is linked with the trunk
group.
AD-WABE:CD=8,DAR=CO; 
AD-WABE:CD=73,DAR=SAT; 
AD-RICHT:TYPE=CD,CD=8,SVC=ALL,TGRP1=number,CPAR=CO; 
AD-RICHT:TYPE=CD,CD=73,SVC=ALL,TGRP1=number,CPAR=CO;
This generates a second exchange code which is not apparent to the user.
35.3 Override, Camp-On, Transfer

The following parameters must be set in the COT so that the features override/
camp-on, transfer (S0/S2) can be used throughout the network:
KNOR - override/camp on possible at busy station

CEBC - transfer (busy/ring or talk state)
CEOC - transfer (only talk state)
These line parameters must be coordinated with the remote system.

AD-COT:COTNO=number,PAR=param
A31003-H3170-S103-6-7620, 02/2019
featnet_en.fm
35.4 Public Address System

Seizure from all nodes is possible. In the other nodes, the code must lead to
DAR=NETW with the destination number indication. 
Announcement via the CO is not provided.
35.5 Dictation Equipment

The dictation equipment can be used throughout the network, also via incoming
calls from the exchange. Command for all nodes in which DICT is not configured.
AD-WABE:CD=key-num,DAR=NETW,DESTNO=number;
35.6 Door Opener

The entrance call feature can be used throughout the network. The door opener
function can be used by suffix-dialling via the dial plan of the system in which the
door opener circuit is configured. Suffix dialling is only possible via an S0/S2
connection (OpenScape 4000/HiPath 4000 - OpenScape 4000/HiPath 4000) or
via loop signalling with DP devices.
The access code of the entrance telephone in the foreign node may be identical
to the suffix dialling digits, and must be assigned the "NETW" DAR.
35.7 Code Calling - Normal and Multiple Task

The code calling system (CC or CCM) is accessible throughout the network.
Normal network code calling is only possible with closed numbering schemes,
CCM is also possible with open numbering plans. CCM can also be used for
incoming calls from the exchange.
The MEET-ME function (Waiting before answering) can be used throughout the
network by PSE/PSM. Network-wide call forwarding/ring no answer to a PSM
MEET-ME is possible. With direct incoming calls from the exchange the required
station is called in addition to the PSM (parallel call), if CF/RNA is configured and
if the PSM and the forwarding station are located in the same node. Answering
via analog and tie trunks is not possible. The attendant console cannot answer.
Switching to PS in other nodes is possible if the waiting station is in a different
node. Switching is not possible, if the PS and the waiting station share the same
node and consultation hold on the same line was carried out.
A31003-H3170-S103-6-7620, 02/2019
featnet_en.fm
Code Calling - Normal and Multiple Task
For the DISPLAY mode, it is necessary that the A-block number also be
transferred. Therefore, this function is only possible via S0 and S2 in inter-PBX
transit traffic. (For CCM, DISPLAY can also be used for incoming calls from the
exchange with S0 and S2 with CorNet-N or CorNet-NQ protocol.)
Assign the CC in the node in which it is configured, as before.
In all other nodes, from which paging jobs are to be executable, the paging code
CCSN, CCSCD and CCANS or CCMS, CCMSURG and CCMANS is assigned on
DAR=NETW plus destination number.
• Set the system-specific parameters for the CCM in all systems with AMO
ZAND.
CHA-ZAND:TYPE=CCM,STNRNG=param,SRCHTN=param,DEL=param,
POSTDBSY=param,SRCHONCE=param,ANNINTCC=param,
ANNEXTCC=param,AAFTERB=param,ADISPEND=param,
SYNCACCM=param,OPENNO=param;
PSM in networks with open numbering plans

In networks with open or mixed numbering plans all search codes, together with
the node code, are signaled to the CCM, e.g. 
263212 if 26-3212 is searched and
273421 if 3421 is searched
node 26 node 27
3421
3212
CCM
If the CCM is called directly (=prefix), the called number must be terminated by
’#’.1 The own node code is not required for searching for stations within the
system where the CCM is located.
Programming Call forwarding to CCM remains the same: 

forwarding destination = paging code.
• Activate the CCM for open numbering plans:

CHA-ZAND:TYPE=CCM,OPENNO=YES;
• The station numbers must be known to the OpenScape 4000, dialed number
- to pager number conversion is not possible:
CHA-TSCSU:PEN=<ltg-ltu-slot-cct>,DEV=CCM,STNOLEN=0,CONV=NO;
1. If the function "PSM with open numbering plan" is active, then this is always applicable, even with
closed numbering.,
A31003-H3170-S103-6-7620, 02/2019
featnet_en.fm
Callback
• Enter the routing code of the home node (corr. WABE code OWNNODE) in
every PBX:
CHA-ZAND:TYPE=ALLDATA,PNODECD=<ownnode>;
• Program call forwarding to CCM for stations in a network:
ADD-ZIEL:TYPE=FWD,SRCNO=<number>, SI=VOICE, DESTNOF=<key-
num>,
DTYPE=<diversion type>,CFVAR=<call forwarding variant>;
where key-num= paging code+ ownnode+station number
35.8 Callback
Callback if busy between station users of a private network 
Callback if busy from and to public ISDN users 
Callback on no answer between users in a private network (not VFSS)
• The parameter CBK must be declared in the AMO DIMSU

AD-DIMSU:TYPE=USER,CBK=number;
• For callback throughout the network the AMO COT has two parameters:
CBBN for callback if busy, and CCFN for callback on no answer.
AD-COT:COTNO=number,PAR=CBBN; 
AD-COT:COTNO=number,PAR=CBFN;
IMPORTANT: Line circuits must be hard-blocked, since the Call References are
not deleted with a soft block, and the circuit only becomes free when all its
callback jobs have been processed.
IMPORTANT: Der COT parameter TSCS is to be set on all digital circuits (tie/
public).
A31003-H3170-S103-6-7620, 02/2019
featnet_en.fm
Speed Dialling Facility Throughout the Network (S0,S2)
35.9 Speed Dialling Facility Throughout the Network (S0,S2)
83=TIEATND
OpenScape S0/S2 OpenScape CO

4000 4000
DESTNO 1 DESTNO 2
83=NETW, DESTNO=2
S0/S2
OpenScape
4000
DESTNO 3
83=NETW, DESTNO=2
Figure 26 Example for using the speed dialling facility in the EMS
The speed dialling facility can be used throughout the network. 

Within a OpenScape 4000 network linked with S0/S2 the speed dialling facility
code leads to DAR=NETW in all "foreign" nodes.
A31003-H3170-S103-6-7620, 02/2019
euprot_en.fm
ISDN Protocol Variants
Notes on protocol handling
36 ISDN Protocol Variants

The initialization for the PD tables has been transferred from the database to the
HD. The following command is sufficient for initialization of the memories for the
PD tables:
COPY-PRODE:PVCD,1;
The above command writes the initialization data for the PD tables to the
database, initializes the general section and loads all assigned PDs.
The protocol descriptor tables consists of a general section and the PD tables.
This applies both to the database (DB) and the hard disk (HD)
The general section is referred to as the variant table (VARTAB). It defines the
relationships between the protocol descriptors (PD) and the protocol variants.
The hard disk contains up to 40 versions of these variant tables, each for a
particular country. On the HD the tables are termed protocol variant combination
descriptors (PVCD).
The PVCDs and PDs on the hard disk can be displayed with the following
commands:
DISPLAY-PRODE:SRC=HD,KIND=PVCDSHRT;
DISPLAY-PRODE:SRC=HD,KIND=PDSHORT;
Outputs, see AMO description.
The PVCDs/PDs are numbered for HD access and are addressed by means of
PVCDNR or PDNR.
The database protocols activated can be displayed with the following commands:
DISPLAY-PRODE:SRC=DB,KIND=PDSHORT;
DISPLAY-PRODE:SRC=DB,KIND=VARTAB;
Outputs, see AMO description.
36.1 Notes on protocol handling

With the COPY action, a complete protocol variant combination descriptor
(PVCD) or an individual protocol descriptor (PD) can be loaded from the hard
disk.
When a PVCD is copied, the variant table (VARTAB) is initialized in the DB and
all the PDs required for the PVCD are loaded.
A maximum of 14 PDs can be used in a PVCD. The loaded PDs are activated
automatically.
A31003-H3170-S103-6-7620, 02/2019
euprot_en.fm
Notes for upgrading a previous version
When individual PDs are copied, either an already loaded PD can be overwritten
or a free space can be searched or specified for the PD. Once an individual PD
has been loaded, it is deactivated.
After an individual PD has been copied, the CHANGE command for activation of
the PD must be sent in order to ensure that the active bit is set and the call
processing (CP) protocol is available. The command to activate the PD is:
CHANGE-PRODE:SRC=PD,PDNAME=PD08,SEC=ORG,ACTIVE=Y;
With the CHANGE action, the contents of the PD memories can be changed in
both the general section (VARTAB) and the individual protocol descriptors (PD).
A PD can also be activated/deactivated.
Only a PD loaded with COPY can be changed.
To prevent call processing from accessing inconsistent data when a PD (protocol

file) is changed, the PD is disabled automatically with the first CHANGE
command. The PD must be reactivated explicitly with the last CHANGE
command (parameter ACTIVE).
36.2 Notes for upgrading a previous version

The protocol variants 1TR6 or DKZN and SBQ9311 are no longer available.
The protocol variant ECMABC is generally no longer available. Use the protocol
variant ECMA1 instead.
36.3 Example: Copying a protocol from the hard disk to the database
36.3.1 Current PRODE configuration should be

regenerated first.
The result can be reloaded in an emergency to regenerate the previous status.
REG-PRODE;
36.3.2 Displaying the assignment of protocol variants

to the protocols loaded in the database:
PROTVAR Name of protocol variant assigned to trunks or stations

PDNAME Database memory location (PD01 - PD14) containing a protocol
PDSTRING Short description of the protocol
A31003-H3170-S103-6-7620, 02/2019
euprot_en.fm
Example: Copying a protocol from the hard disk to the database
Check which protocol variants (PROTVAR) are not needed and can be deleted.
A memory location (PDNAME) can be assigned to multiple protocol variants
(PROTVAR).
In the following example:
• PD01, PD02 are assigned to the protocol variant (PROTVAR) CORNV33.
• PD07 is assigned to PROTVAR SBDSS1 (with option table 10).

DIS-PRODE:SRC=DB,KIND=VARTAB;
H500: AMO PRODE STARTED
PVCDNR : 1 "DEUTSCHLAND " VERSION: B0-EL0.20.001 
+---------------------+--------+--------+---------------------------+ 
| PROTVAR | | PDNAME | PDSTRING | 
+---------------------+--------+--------+---------------------------+
| CORNV33 | PDNORM | PD01 | CORNET-N 1.3f (IM) | 
| | PDA1 | PD02 | NI-2 PRI MAINTENANCE | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| ECMA1 | PDNORM | PD03 | ECMA QSIG SS | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| EDSBRD | PDNORM | PD04 | EURO-ISDN 1TR67 REF-T | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
+---------------------+--------+--------+---------------------------+ 
+---------------------+--------+--------+---------------------------+
| ETSI | PDNORM | PD05 | EURO-ISDN REF-T USER-SIDE | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| EDSS1NET | PDNORM | PD06 | EURO-ISDN REF-T NET-SIDE | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| SBQ9311 | PDNORM | PD07 | S0-BUS DSS1 ETS 300 403 ) | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
+---------------------+--------+--------+---------------------------+ 
+---------------------+--------+--------+---------------------------+
| SBDSS1 | PDNORM | PD07 | S0-BUS DSS1 ETS 300 403 ) | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| ECMAV2 | PDNORM | PD08 | ETSI QSIG Third ed. SS | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| PSS1V2 | PDNORM | PD09 | ISO QSIG Second ed. SS | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
+---------------------+--------+--------+---------------------------+ 
+---------------------+--------+--------+---------------------------+
| ATT4ESS | PDNORM | PD12 | AT&T 4ESS (TR41459) | 
| | PDA1 | | | 
A31003-H3170-S103-6-7620, 02/2019
euprot_en.fm
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| MCI250 | PDNORM | PD13 | MCI 014-0018-04.3D-ER | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
+---------------------+--------+--------+---------------------------+ 
+---------------------+--------+--------+---------------------------+
| SPRINT | PDNORM | PD13 | MCI 014-0018-04.3D-ER | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| NI2 | PDNORM | PD11 | NI-2 PRI (SR-4619) | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| CORNUS | PDNORM | PD14 | CORNET-N 1.3f (US) | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
AMO-PRODE-124 TABELLEN FUER DEN PROTOKOLL DESCRIPTOR VERWALTEN 
ABFRAGEN DURCHGEFUEHRT;
IMPORTANT: Before loading a new protocol to a memory location (PDNAME),

ensure that this memory location is not assigned to any protocol variant
(PROTVAR).
36.3.3 Deleting unwanted protocol variants
IMPORTANT: The AMO PRODE does not check if a protocol variant is still
assigned to a trunk or a station. It may be necessary to regenerate the AMO
TDCSU or SBCSU and then analyze the regeneration result to check if a protocol
variant is still in use.
In this example, a change command is used to delete the protocol variants

SBDKZ1 and SBDKZ2 from VARTAB (DB). The new protocol is loaded to
memory location PDNAME=10.
Protocol variant MCI250 is deleted:

CHA-PRODE:SRC=VARTAB,PROTVAR=MCI250;
Check query:
DIS-PRODE:SRC=DB,KIND=VARTAB
PROTVAR MCI250 has been deleted, memory location PD10 is no longer
assigned to a PROTVAR.
A31003-H3170-S103-6-7620, 02/2019
euprot_en.fm
36.3.4 Querying the number (PDNO) under which the

required protocol description (PDSTRING) is saved
on the HD
In this example, the MCI 014-0018-04 MAINT protocol is loaded to the database.
DIS-PRODE:SRC=HD,KIND=PDSHORT;
+------+---------------------------+-------+---------------+
| PDNR | PDSTRING | IDENT | VERSION |
+------+---------------------------+-------+---------------+
| 1 | ECMA QSIG BC | H/08 | B0-EJ0.20.002 |
| 2 | SWISSNET 2 BC | H/08 | B0-EG0.10.001 |
| 3 | CORNET HICOM V2.2 / V2.3 | H/08 | B0-EL0.20.001 |
| 4 | CORNET-N 1.3f (IM) | H/08 | B0-EL0.20.004 |
| 5 | 1TR6 N0 REF-T (USER-SIDE) | H/40 | B0-EL0.20.001 |
| 6 | 1TR6 N1 REF-T (USER-SIDE) | H/41 | B0-EL0.20.001 |
| 7 | ANALOG | H/11 | B0-EL0.20.001 |
| 8 | FRANKREICH VN3 NUMERIS | H/08 | B0-EL0.10.001 |
| 9 | S0-BUS DSS1 ETS 300 403 ) | H/08 | B0-EJ0.20.001 |
| 10 | S0-BUS DKZN1 N0 | H/40 | B0-EL0.20.002 |
| 11 | S0-BUS 1TR6 N0 | H/40 | B0-EL0.20.001 |
| 12 | S0-BUS DKZN1 N1 | H/41 | B0-EL0.20.002 |
| 13 | S0-BUS 1TR6 N1 | H/41 | B0-EL0.20.001 |
| 14 | EURO-ISDN REF-T USER-SIDE | H/08 | B0-EJ0.20.004 |
| 15 | EXPO-92 SPANIEN JULIO, 89 | H/08 | B0-EG0.10.002 |
| 16 | PRE-EURO-ISDN FINNLAND | H/08 | B0-EG0.10.001 |
+------+---------------------------+-------+---------------+
+------+---------------------------+-------+---------------+
| 17 | PRE-EURO-ISDN PORTUGAL | H/08 | B0-EG0.10.001 |
| 18 | PRE-EURO-ISDN BELGIEN | H/08 | B0-EG0.10.001 |
| 19 | PRE-EURO-ISDN DAENEMARK | H/08 | B0-EG0.10.001 |
| 20 | 1TR6 N1 REF-Q (NET-SIDE) | H/41 | B0-EL0.20.001 |
| 21 | EURO-ISDN 1TR67 REF-T | H/08 | B0-EJ0.20.004 |
| 22 | EURO-ISDN OESTERREICH | H/08 | B0-EJ0.20.004 |
| 23 | FRANKREICH VN4 NUMERIS | H/08 | B0-EJ0.20.001 |
| 24 | NEDERLAND | H/08 | B0-EG0.10.001 |
| 25 | CHINA CSN-7 REF-T | H/08 | B0-EH0.10.006 |
| 26 | ENGLAND MCL-ISDN | H/08 | B0-EF0.30.004 |
| 27 | BASIC ACCESS T0 AUSTRALIA | H/08 | B0-EF0.30.002 |
| 28 | PRIM. ACCESS T2 AUSTRALIA | H/08 | B0-EF0.30.002 |
| 29 | ECMA QSIG SS | H/08 | B0-EL0.20.001 |
| 31 | ETSI QSIG Third ed. SS | H/08 | B0-EL0.20.001 |
| 32 | ISO QSIG Second ed. SS | H/08 | B0-EL0.20.001 |
+------+---------------------------+-------+---------------+
+------+---------------------------+-------+---------------+
| 33 | EURO-ISDN REF-T NET-SIDE | H/08 | B0-EJ0.20.004 |
| 34 | NI-2 PRI (SR-4619) | H/08 | B0-EN0.10.002 |
| 35 | NI-2 PRI (SR-4619 (NET) | H/08 | B0-EN0.10.002 |
| 36 | NI-2 PRI MAINTENANCE | H/43 | B0-EL0.20.002 |
| 37 | AT&T 4ESS (TR41459) | H/08 | B0-EL0.20.007 |
| 38 | AT&T 4ESS (TR41459) MAINT | H/03 | B0-EL0.20.002 |
| 39 | MCI DMS 250 014-0018-04 | H/08 | B0-EL0.20.009 |
| 40 | CORNET-N 1.3f (US) | H/08 | B0-EL0.20.005 |
| 41 | S0-BUS NI-BRI GR-268-CORE | H/08 | B0-EL0.20.005 |
| 42 | MCI 014-0018-04 MAINT | H/03 | B0-EL0.20.001 |
| 43 | MCI DEX 600 014-0018-04 | H/08 | B0-EL0.20.004 |
+------+---------------------------+-------+---------------+
AMO-PRODE-60 TABELLEN FUER DEN PROTOKOLL DESCRIPTOR VERWALTEN
The required protocol is stored under number 42 on the hard disk.
A31003-H3170-S103-6-7620, 02/2019
euprot_en.fm
36.3.5 Copying the protocol from the hard disk to the

database memory
Protocol no. 42 is copied to memory location PD10 in the database.
COPY-PRODE:TYPE=PD,PDNO=42,PDNAME=PD10;
36.3.6 Assigning a protocol variant to the memory

location in the database
The protocol variant MCI250 should be assigned to memory location PD10.
CHA-PRODE:KIND=VARTAB,PROTVAR=MCI250,PDNORM=PD10;
This procedure must be repeated if the protocol loaded is assigned to more than
one protocol variant.
Check query:
AB-PRODE:ORT=DB,ART=VARTAB;
H500: AMO PRODE GESTARTET
+---------------------+--------+--------+---------------------------+ 
+---------------------+--------+--------+---------------------------+
| CORNV33 | PDNORM | PD01 | CORNET-N 1.3f (IM) | 
| | PDA1 | PD02 | NI-2 PRI MAINTENANCE | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| ECMA1 | PDNORM | PD03 | ECMA QSIG SS | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| EDSBRD | PDNORM | PD04 | EURO-ISDN 1TR67 REF-T | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
+---------------------+--------+--------+---------------------------+ 
+---------------------+--------+--------+---------------------------+
| ETSI | PDNORM | PD05 | EURO-ISDN REF-T USER-SIDE | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| EDSS1NET | PDNORM | PD06 | EURO-ISDN REF-T NET-SIDE | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| SBQ9311 | PDNORM | PD07 | S0-BUS DSS1 ETS 300 403 ) | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
+---------------------+--------+--------+---------------------------+ 
+---------------------+--------+--------+---------------------------+
| SBDSS1 | PDNORM | PD07 | S0-BUS DSS1 ETS 300 403 ) | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
A31003-H3170-S103-6-7620, 02/2019
euprot_en.fm
| ECMAV2 | PDNORM | PD08 | ETSI QSIG Third ed. SS | 

| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| PSS1V2 | PDNORM | PD09 | ISO QSIG Second ed. SS | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| MCI250 | PDNORM | PD10 | MCI 014-0018-04 MAINT |
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+ 
+---------------------+--------+--------+---------------------------+ 
+---------------------+--------+--------+---------------------------+
| ATT4ESS | PDNORM | PD12 | AT&T 4ESS (TR41459) | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
+---------------------+--------+--------+---------------------------+ 
+---------------------+--------+--------+---------------------------+
| SPRINT | PDNORM | PD13 | MCI 014-0018-04.3D-ER | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| NI2 | PDNORM | PD11 | NI-2 PRI (SR-4619) | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
| CORNUS | PDNORM | PD14 | CORNET-N 1.3f (US) | 
| | PDA1 | | | 
| | PDA2 | | | 
+---------------------+--------+--------+---------------------------+
AMO-PRODE-124 TABELLEN FUER DEN PROTOKOLL DESCRIPTOR VERWALTEN 
A31003-H3170-S103-6-7620, 02/2019
euprot_en.fm
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Routing with LCR
37 LCR (Least Cost Routing)

LCR is a collective term for the procedures of routing in a network which allow
optimum control of the line selection for a connection under mutual interaction.
This routing is based on the user LCOS, the costs of a circuit, the time of day, the
node number, the source group, the restriction table (destination) and the service.
The system determines the available routes and checks the authorization of the
user for using the route.
37.1 Routing with LCR

Routing with LCR allows the specification of several alternative routes within a
network to the destination station (see diagram).
In this context, the route may display differing properties, e.g. as regards call
charge recording.

• The digits dialed by the subscriber can be manipulated as a function of the
route selected (LCR dial rules).
• The search for an idle circuit only takes place once during the call setup.
However, a circuit is not seized until after a complete check of the dial plan.
• An additional alternative route can also be added to a route in LCR.
• For the primary path, the route with the shortest/least expensive connection
should be established (direct connection).
• Restriction: LCR is only operable when the end partners of the standard
route are analog/digital stations or analog/digital CO trunk circuits. Functional
terminals and analog interface circuits, special equipment (VMX, VMS,
paging, etc.) and COs (as A or C stations in consultation) are not supported.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Routing with LCR
Public Network
No. dialed.
089-722-39500
Alternative route
93-39500 93-39500
NODECD 92
Primary route
93-39500
STN
NODECD 91 NODECD 93 39500
Figure 27 Alternative Routes to Destination Station
37.1.3 Generation (Example)

Excerpt of the most important commands for closed numbering from Node 91 to
Node 93 with an alternative route via Node 92.
• Prepare route to Node 93 with AMO RICHT:

ADD-RICHT:MODE=CD,LRTE=93,CD=093,SVC=ALL,NAME="TO NODE
93",TGRP1=93&92;
• Enter primary route (direct connection) in AMO LDAT:
ADD-LDAT:LROUTE=93,LSVC=ALL,TGRP=93,ODR=1,LAUTH=1;
• Enter secondary route (alternative route via NODECD 92) by means of AMO
LDAT:

Language
RICHT ART d Art der Adressierung der Richtung
MODE e Address-mode of the route
LRTG d LCR - Richtungsnummer
LRTE e LCR - Route number
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Routing with LCR with Rerouting

Language
KZ d Richtungskennzahl
CD e Routing code
DIENST d Dienst
SVC e Communication service
BUNU1 d Buendelgruppe 1
TGRP1 e Trunk group number 1
LDAT LRTG d LCR-Richtungs Nummer
LROUTE e LCR Route number
LDIENST d LCR Dienst
LSVC e LCR Service indicator
BUNUM d Nummer des Buendels
TGRP e Trunk group number
LWR d LCR - Wahlregel Nummer
ODR e LCR Out dial rule number
37.2 Routing with LCR with Rerouting

In the case of rerouting, call setup, for instance, is not interrupted upon receipt of
a congestion signal from the partner system. Instead, assuming availability, an
additional route to the destination is determined and the call setup continued via
this route.
Route variants already taken into consideration in the specified route within the
LCR or routing search are no longer taken into account.
By default, every route is assigned the "Rerouting" feature upon setup. However,
you can also deactivate this attribute individually for every route via the parameter
REROUT in AMO RICHT.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Public network
No. dialed.
089-722-39500
Primary route Congestion signal

93-39500 93-39500
NODEDC 92
Alternative route
93-39500
NODENCD 91 NODENCD 93 STN

39500
Figure 28 Rerouting

Rerouting is executed, for example, upon detection of the following situations
(Disconnect / Release Causes):
• No dial plan entry" for the number dialed in the partner system
(No route to destination / Cause No. 03)
• B-Channel negotiation incorrect 

(Channel unacceptable / Cause No. 06
Requested circuit / Channel not available / Cause No. 44)
• Circuit fault / Out of operation (circuit out of order / Cause No. 33)
• No valid / Idle circuit available (no circuit / channel available / Cause No. 34)
• Network fault (network out of order / Cause No. 38)
• Insufficient information for call setup in the remote system 

(temporary failure, resource unavailable / Cause No. 41)
• Lack of resources at partner (switching equipment congestion / Cause No.

42)
• No authorization for outgoing calls (outgoing call barred)
• Line is available, but does not correspond to the requirements on the

connection 
(service or option not available / Cause No. 63)
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
• The channel requested does not exist (identified channel does not exist /
Cause No. 82)
• No response within a defined period (recovery on timer expiry / Cause No.

102).
• Number has changed (number changed / Cause No. 22)
IMPORTANT: If the parameter NORR is set in the COT of a circuit, the Rerouting
function is generally deactivated for this circuit.
IMPORTANT: If the parameter TGRE is set in the COT of a circuit, Rerouting is

only performed for this in the case of Cause No. 01/03/22/44.

Excerpt of the most important commands for closed numbering from Node 91 to
Node 93 with the possibility of Rerouting.
• Add route to Node 93 with AMO RICHT with Rerouting:

ADD-RICHT:MODE=CD,LRTE=93,CD=093,SVC=ALL,NAME="TO NODE
93",TGRP1=93&92,REROUT=YES;

Language
CD e Routing code
DIENST d Dienst
REROUT d Reroute Kennzeichen
REROUT E Set rerout-sign
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Routing via LCR with Internal Rerouting
37.3 Routing via LCR with Internal Rerouting
37.3.1 Description of Features

In the case of Internal Rerouting, a route is selected within the routes which does
not lead to a direct circuit seizure. The LCR remains in the own physical nodes
and only transits the dial rule in the route labelled as RERTEINT.
With the resultant number, the digit analysis is restarted and the search for a route
to the (possibly) new destination commenced, where the "called party number" is
internal.
Public network
FAX - dial FAX - Server

089 89100 91 7140
CD 91:
Primary route (e.g S2-circuit to Server)
SNNO 1-89-102
Alternative route (STN)
FAX - STN
7101
Figure 29 Rerouting Internal

• For the Internal Reroute function, the parameter REROUT in AMO RICHT
need not necessarily be set to the value "Yes".
• No circuit is seized in the case of Internal Rerouting, i.e. the LCR remains
within the system.
• The parameter TGRP in AMO LDAT should be completed using a TIE Trunk
if LATTR=RERTEINT is set. The Trunk will not be seized or permissions
checked, but a TIE Trunk instead of CO is important for some DB procedures.
• Routing to the own system no longer functions if the own destination node
number is specified in the route.
• Incoming channel search for IP Trunking is not supported and does not work
when only LDAT entries are available with RERTEINT.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Routing via LCR with Internal Rerouting
Notes on LATTR=RERTEINT
• RERTEINT was developed only to reach an internal destination after dialling
a number e.g. the E.164 ISDN CO code for the local switch.
• RERTEINT should not be used to reach any external destinations (i.e. the
result after RERTEINT should physically belong to the local switch).
• It is coincidental RERTEINT is allowed for basic call (i.e. to reach an external

destination).

Excerpt of the most important commands for open numbering to a FAX Server 
(digit pattern 91-X ) with the possibility of Internal Rerouting (rerouting of the FAX
to a G3-FAX terminal) if the connection to the FAX server fails.
• Prepare Route 33 to Nodes 1-89-102 with AMO RICHT:

ADD-RICHT:MODE=LRTENEW,LRTE=33,LSVC=ALL,
NAME="FAXSERVER",TGRP=33,DNNO=1-89-102,INFO="FAXSERVER",
PDNNO=1-89-102;
• Define Dial Rule No. 33 with AMO LODR:
ADD-LODR:ODR=33,INFO="FAX SERVER";
• Define Dial Rule No. 333 with AMO LODR:
ADD-LODR:ODR=333,CMD=OUTPULSE,DGTS=7101;
ADD-LODR:ODR=333,INFO="FAX MACHINE";
• Prepare direct connection to Nodes 1-89-102 with AMO LDAT:
ADD-LDAT:LROUTE=33,LSVC=ALL,LVAL=2,TGRP=33,
ODR=33,LAUTH=1,CARRIER=9,ZONE=EMPTY,LATTR=NONE;
• Prepare Internal Rerouting with AMO LDAT (use of a different dial rule and,
thus, new entry into route selection):
ADD-LDAT:LROUTE=33,LSVC=ALL,LVAL=2,TGRP=33,
ODR=333,LAUTH=1,CARRIER=9,ZONE=EMPTY,LATTR=RERTEINT;

Language
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Central Office Breakout

Language
CD e Routing code
DIENST d Dienst
REROUT e Set rerout-sign
LATTR d LCR-Attribut
LATTR e LCR attribute
37.4 Central Office Breakout

Trunk calls are routed to the private node closest to the destination. This is only
sensible if the destination is within the local area, or if the short-haul area of a
node lies within the private network. 
Breakout into the public network (CO Breakout) is thus performed at the least
expensive point and the use of resources in the private network minimized.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Indirect Network Access
Requirements:
1. If a subscriber in Berlin dials a 
number in Munich (089-
Private network Carrier 47110815), the connection
Berlin (030) PSTN must be routed in the private
network via Frankfurt to 
Munich.
If the destination in the local
network
0-089-
is Munich, the central office
47110815 outbreak 
takes place in Munich.
Bonn Frankfurt (069)
2. If the route from Frankfurt to
Munich 
is blocked, no central office
breakout 
may occur in Frankfurt. 
In this case, in Berlin, a trunk
circuit must be seized and the
Munich (089) connection 
to Munich setup via the public 
network. Munich (089)
47110815
Figure 30 Central Office Breakout
37.5 Indirect Network Access

Example: Indirect network access to private network
In general, the requirement applies of routing local calls via PTT and long-
distance calls via other Carriers. Access to the Carrier can be realized directly or
indirectly via PTT.
Indirect access:
Analog
OpenScape PTT Private
4000 Network
Digital
Figure 31 Indirect Network Access
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Dialing Plan
Call setup procedure:
Station dials the number: 08972239500. The switch seizes a trunk circuit (digital)
and sends the following digits:
131 CO call to private network. Dialing the D channel

Dial tone System waits for second dial tone
Authorization code Authorization code for network access, if required
08972239500 Number
The authorization code and the nummer are sent via the DTMF signaling in the B
channel.
37.6 Dialing Plan

Not only the access code dialed by the subscriber is required for routing, but also
the subsequent digits defined with AMO LDPLN.
37.7 Closed Numbering NWLCR (without LCR DIALING PLAN)

Switching is realized via the digit analysis (DPLN).
For RICHT MODE=CD and LRTE=x, the principle path selection is realized via
the AMOs 
RICHT-->LDAT--> LSCHD-->LODR (influencing AMO’s KNLCR, LAUTH, LSCHD
...). 
A number of type MODE=NETRTE is assigned to an LRTE (Route) established
by the AMO RICHT. The LRTE number establishes the cross-reference to AMO
LDAT. The trunk group numbers (TGRP) must be identical with the information in
AMO RICHT. The order of the assigned trunk groups is not important, as these
are ordered by AMO LDAT with the parameter LVAL (LCR priority).
The LCR schedules are taken into consideration with the parameter LSCHED
and additional LCR attributes can be stored for a route under LATTR.

• The numbers of a closed numbering network must be unique.
• Closed numbering is used within Areas (so-called OpenScape 4000

Domains).
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Closed Numbering NWLCR (without LCR DIALING PLAN)
• The WABE entries in such a network (Area) must be consistent, i.e. entries
for call numbers must lead to the corresponding destination number.
• Virtual node numbering structure in the case of closed numbering networks is

not sensible in the I.M.
• With the help of the AMO WABE, the physical destination node number can
be displayed.
• NWLCR is the typical OpenScape 4000 numbering with NPI=unknown, which

is primarily used for the internal company area
Dial
AMO WABE AMO WABE
CD CPS DPLN DAR DESTNO CD CPS DPLN DAR DESTNO
... NETRTE STN
AMO RICHT
MODE LRTE CD DPLN CPS SVC TGRP1 DESTNO DNNO PDNNO REROUT
CD ...
AMO LDAT
LROUTE LSVC LVAL TGRP ODR LAUTH LSCHED LATTR DNNO
AMO LODR
ODR CMD CMDPOS INFO
Called Party
(circuit seizure)
Figure 32 Call Setup Procedure via Networking LCR
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm

• Setting up the digit analysis result for a routing code (AMO WABE NETRTE):
ADD-WABE:CD=20,DAR=NETRTE,CHECK=NO;
• Setting up a route with utilizable trunk groups to destination node 1-89-200,
with destination number 20 for voice connections (AMO RICHT):
ADD-RICHT:MODE=CD,LRTE=200,CD=20,CPS=0,SVC=SPVH,
NAME="TO NODE 200",TGRP1=20&30&40,DESTNO=20,DNNO=1-89-200,
PDNNO=2-89-200,ROUTOPT=YES;
• Define dial rule with AMO LODR (repeat digit sequence dialed on line):
ADD-LODR:ODR=1,CMD=NPI,NPI=UNKNOWN,TON=UNKNOWN;
ADD-LODR:ODR=1,INFO="CLOSED NUMBERING UNKNOWN";
• Set up primary route to route 200 with AMO LDAT (direct connection):
ADD-LDAT:LROUTE=200,LSVC=VCE,LVAL=1,TGRP=20,ODR=1,LAUTH=1,
CARRIER=9,ZONE=EMPTY,LATTR=NONE;
• Set up secondary route to route 200 with AMO LDAT (alternative connection
1):
• Set up alternative route to route 200 with AMO LDAT (alternative connection
2):
• Set up station numbers as digit analysis result STN (AMO WABE):
ADD-WABE:CD=7200&&7298,DAR=STN;
• Refer station numbers to the destination number (here: 20, i.e. Node 1-89-
200):
CHANGE-WABE:CD=7200&&7298,DESTNO=20;

Language
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm

Language
CD e Routing code
DIENST d Dienst
WABE d Wahlbewertungsgruppe
DPLN e feature access group
VKS d Verkehrssituation
CPS e call progress state
ZLNR d Zielanlagennummer
ZKNNR d Zielknotennummer
DNNO e destination node number
PZKNNR d Phys. Zielknotennummer
PDNNO e Phys. destination node number
LSCHED d LCR schedule
LSCHED e LCR schedule
LWERT d Wertigkeit des Richtungselements
LVAL e priority of route element
LBER d erforderliche LCR-Berechtigung
LAUTH e required lcr authorization
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Open Numbering LCR (with LCR DIALING PLAN))

Language
KZP d Kennzahlpunkt
WABE d Wabegruppe
DPLN e feature access group / dial plan
ZLNR d Zielnummer
LODR INFO d Service Informationen
INFO e Service Informations
LWREL d LCR-Wahlregel-Element
CMD e Out Dial Rule Command
LWR d LCR-Wahlregelnummer
ODR e out dial rule
LWRELPOS d Position des LCR-Wahlregelelementes
CMDPOS e position of the command in the out dial rule
37.8 Open Numbering LCR (with LCR DIALING PLAN))

Switching access is realized via the digit analysis (WABE).
For RICHT MODE=LTRGENEW and LRTE=x, the principle path selection is
realized via the 
AMOs LDPLN-->LDAT--> LSCHD-->LODR. 
(Influencing AMO´S KNLCR, LPROF, LAUTH, LSCHD, ...)
In AMO LDPLN, those routing codes with the digit pattern (RTECD from WABE)
to be evaluated for LCR must be entered as the LCR digit pattern (LDP). 
With the parameter LAUTH (single value), you specify whether an LDP is allowed
or blocked on a subscriber-specific basis. With the parameter LROUTE Number,
you indicate the further call processing of the respective LDP with AMO LDAT. In
the case of large digit pattern schedules, performance can be improved by means
of OPTIIMIZE-LDPLN. See also AMO description LDPLN.
With the AMO LDAT, the trunk groups are linked with the values ODR, LAUTH
and an LCR priority (LVAL) assigned to LCR route elements and prioritized for the
LCR path selection. With the parameter ODR, you specify which LCR dial rule
stipulated with AMO LODR is to be used with this trunk group. 
With the parameter LAUTH (single value), you specify the permissible access
authorization (e.g. for subscribers). 
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
With the parameter LVAL, you specify the priority of a trunk group within an LRTE
(LVAL=1 means highest priority). The seizure priority of the trunk group is thus
specified. You have the option of assigning a host of trunk groups to the same
LVAL. In this case, the trunk groups are simply searched through sequentially. All
trunk groups are numbered consecutively (parameter LROUTE). The parameter
LROUTE only serves to allow subsequent, selective deletion of an entry, not to
assign an additional priority. 
With the parameter LSCHED, consideration is given to the LCR schedules.
In a network with several areas, a subscriber dials an area code and an extension
in order to reach a subscriber from a different area. In this context, the extensions
need only be unique within an area.
IMPORTANT: All area codes (tie line access code) of a network must be unique
and may not be station numbers.
• Open numbering and LCR are used to realize ISDN (E.164) and PNP (E.189)
or EPNP numbering plans.
• The subscriber numbers of a network need not necessarily be unique in this

context.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Dial
AMO WABE
CD CPS DPLN DAR
... CO / TIE
AMO LDPLN
LDP DPLN LROUTE LAUTH SPC PINWM FDSFIELD SDSFIELD PROFIDX
...-
AMO RICHT
MODE LRTE LSVC TGRP DNNO REROUT ROUTATT
LRTENEW
AMO LDAT
LROUTE LSVC LVAL TGRP ODR LAUTH LSCHED LATTR DNNO LDSRT
AMO LODR
ODR CMD CMD INFO
Called Party
(circuit seizure)
Figure 33 Call Setup Procedure via LCR

Example without additional LCR supplements and with only one route element.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
• Setting up the digital analysis result TIE (AMO WABE):

ADD-WABE:CD=0,CPS=2&3&4&5&8&9&10&12,DAR=TIE,TEST=NO;
• Set up the route with utilizable trunk groups to destination node 1-1-0 (CO)
for connections of all services (AMO RICHT):
ADD-RICHT:MODE=LRTENEW,LRTE=91,LSVC=ALL,NAME="CO LOCAL",
TGRP=90,DNNO=1-1-0,INFO="ICN-CO ISDN LOCAL";
• Define dial rule with AMO LODR (send dialed digit sequence X on line and
use ISDN with type Subscriber for the "calling party"):
ADD-LODR:ODR=91,CMD=NPI,NPI=ISDN,TON=SUBSCR;
ADD-LODR:ODR=91,INFO="ICN-CO ISDN LOCAL";
• Set up primary route to route 91 with AMO LDAT (direct connection to CO):
ADD-LDAT:LROUTE=91,LSVC=ALL,LVAL=1,
TGRP=90,ODR=91,LAUTH=2,CARRIER=1,ZONE=EMPTY,LATTR=WCHREG;
• Set up digit pattern with central office breakout code 0 and dial tone (AMO
LDPLN):
ADD-LDPLN:LDP=0-W-X,LROUTE=91,LAUTH=2

Language
DIENST d Dienst
BUNUM d Buendelgruppe 1
TGRP e Trunk group number 1
ROUTATT d Richtungsattribute
ROUTATT e Route attribute
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm

Language
LSCHED d LCR schedule
LDSRT d Nummer der LCR Digit String Restriction
Tabelle
LDSRT e Number of LCR Digit String Restriction
Table
KZP d Kennzahlpunkt
WABE d Wabegruppe
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Time Based LCR (AMO LSCHD)

Language
ODR e out dial rule
LWRELPOS d Position des LCR-Wahlregelelementes
CMDPOS e position of the command in the out dial rule
LDPLN LWM d LCR Wählmuster
LDP e LCR digit pattern
LBER d LCR Berechtigung
LAUTH e LCR authorization level
LRTG d LCR Richtungsnummer
FDSFIELD d Index des Feldes in dem Anrufplan, das
FDS enthaelt
FDSFIELD e Index of the field in dialplan, which contains
FDS
SDSFIELD d Index des Feldes in dem Anrufplan, das
SDS enhaelt
SDSFIELD e Index of the field in dialplan, which contains
SDS
PINDP d PIN fuer Anrufplan gebraucht
PINDP e PIN for dialing plan requested
PROFIDX d LCR Profile Index
PROFIDX e LCR Profile Index
37.9 Time Based LCR (AMO LSCHD)

With the AMO LSCHD, up to 8 schedules - designated with the letters A, B, C, ..
G, H - can be defined in a table per internal traffic restriction group. These typically
cover the week in schedules which correspond with call charging rates. Every
internal traffic restriction group (ITR) has its own LCR schedule table.
An entry is made for every day/hour combination, with minute and schedule.
Every hour of every day is always assigned to a schedule. The minute determines
the time within the hour at which the specified schedule is switched. If the current
schedule for the expiring hour is unchanged, no switching occurs and the minute
specification has no significance.
The schedules configured in this way can be included during routing in AMO
LDAT (parameter LSCHED), in order to determine a route (time based LCR).
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
37.9.2 Special Feature

In the event that the feature is released (AMO FEASU), a corresponding audio
signal is supplied at the terminals in the case of a more expensive connection and
a warning text displayed on voice terminals (with the exception of attendant
consoles and bus terminal devices). The attribute Expensive is assigned to a
route element as a function of the weekday and the time of day.

• The table is implemented and initialized per ITR group in the database (with
00 A)
• You can only change it. Therefore, the AMO LSCHD has no actions for ADD
and DELETE.
• If schedules are not specified, AMO LDAT enters all schedules.

The following table presents an excerpt of a specimen configuration with two
changes.
Schedule B = Monday to Friday 07.00 - 17.59 hrs

Schedule C= Monday to Friday 18.00 - 22.59 hrs
• Change schedule for Monday to Friday from 07.00 - 17.59 Hrs to B:

CHA-LSCHD:ITR=0&&15,DAY=MON&TUE&WED&THU&FRI,HOUR=7&&17,SCHED,
MINUTE=59;
• Change schedule for Monday to Friday from 18.00 - 22.59 Hrs to C:
CHA-
LSCHD:ITR=0&&15,DAY=MON&TUE&WED&THU&FRI,HOUR=18&&22,SCHED=C,M
INUTE=59;
• Assign schedule of a route with parameter LSCHED:
(In this example, trunk group 200 can only be seized in schedule B)
ADD-
LDAT:LROUTE=3,LSVC=VCE,LVAL=2,TGRP=200,ODR=6,LAUTH=1,LSCHED=B
;
HOUR SUN MON TUE WED THU FRI SAT

00 00 A 00 A 00 A 00 A 00 A 00 A 00 A
01 00 A 00 A 00 A 00 A 00 A 00 A 00 A
02 00 A 00 A 00 A 00 A 00 A 00 A 00 A
03 00 A 00 A 00 A 00 A 00 A 00 A 00 A
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
HOUR SUN MON TUE WED THU FRI SAT

04 00 A 00 A 00 A 00 A 00 A 00 A 00 A
05 00 A 00 A 00 A 00 A 00 A 00 A 00 A
06 00 A 00 A 00 A 00 A 00 A 00 A 00 A
07 00 A 00 B 00 B 00 B 00 B 00 B 00 A
08 00 A 00 B 00 B 00 B 00 B 00 B 00 A
Excerpt
20 00 A 00 C 00 C 00C 00 C 00 C 00 A
21 00 A 00 C 00 C 00 C 00 C 00 C 00 A
22 00 A 00 C 00 C 00 C 00 C 00 C 00 A
23 00 A 00 A 00 A 00 A 00 A 00 A 00 A

Language
LSCHD VBZ d Verkehrsbeziehungsgruppe
ITR e Internal Traffic Restriction Group
TAG d Wochentag
DAY e Weekday
STUNDE d Stunde
HOUR e Hour
SCHED d Zeitband fuer diese Tag-Stunden-
Kombination
SCHED e Schedule for this day/hour combination
MINUTE d Minute des Zeitbandwechsels
MINUTE e Minute of Schedule change
LDAT LRTG d LCR-Richtungsnummer
LROUTE e LCR route number
ODR e LCR Out Dial Rule Number
LSCHED d LCR Schedule
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Restriction Tables (AMO LDSRT)
37.10 LCR Restriction Tables (AMO LDSRT)

A max. of 16 restriction tables (LDSRT) can be administrated with the AMO
LDSRT. Each of these tables allows the blocking of individual digit strings, which
can be broken down into two areas (FDS and SDS). The digit pattern fields to be
included for the check of the FDS/SDS areas are specified in AMO LDPLN. The
applicable table is optionally assigned one or more routes when using the
restriction tables in AMO LDAT with the parameter LDSRT.
If no correlation between the administrated areas (FDS and SDS) is found with
the specified digit pattern fields in the digit pattern dialed, the LCR for this route
is continued.
If the entries in the LDSRT table agree with the specified digit pattern fields, the
connection is not established via this route (trunk group) and the LCR is
continued with the next route. (If no further route is defined, or if the authorization
is inadequate, the LCR is terminated.)
This feature is typically used if a system is connected to several carriers. Certain

digit sequences (digit strings) are not, however, accepted by all carriers.

• If an entry exists in the table for an FDS area, but no entry exists under the
SDS area, all further digit strings are blocked (as of the SDS area).
• Several LDSRT tables can also be assigned to one route.
• A route in which the LDSRT test fails is not suitable to be inserted into a queue
(Chapter on page 432)
• If a large number of entries are needed in the LDSRT table, it may be

necessary to modify the value LCRDSR of the AM DIMSU, i.e. to further
increase it.
• This function can also be combined with other LCR features.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Dialing
Path selection
AMO WABE
Digit pattern LDP: 0 - W - 0 - 190 - X- X

AMO LDPLN Field Index: 1 2 3 4 5
LDP FDSFIELD SDSFIELD
FDSFIELD = 4
... - ... - ... - ...
SDSFIELD = 5
AMO RICHT
AMO LDAT AMO LDSRT

LDSRT LDSRT FDS SDS
AMO LODR Restricted Digits

(no circuit seizure)
(i.e. LCR Route terminated)
Called Party
(circuit seizure)
Figure 34 Call Setup Procedure with Restriction Tables

• Expansion of the DIMSU buffer (here: to the value 100):
ADD-DIMSU:TYPE=NETWORK,LCRDSR=100;
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
• Setting up the restriction table with the AMO LDSRT (Table 1 for Digit String
190 with Sub Digit Strings 5 or 7 and Table 2 for 190 with all possible Sub Digit
Strings):
ADD-LDSRT:LDSRT=1,FDS=190,SDS=5&7;
ADD-LDSRT:LDSRT=2,FDS=190;
• The AMO LDPLN is required in order to specify the field of an LDP to be
prioritized:
ADD-LDPLN:LDP=0-W-0-190-X-
X,LROUTE=1,LAUTH=1,FDSFIELD=4,SDSFIELD=5;
• The AMO LDAT is required in order to refer to the desired LDSRT table
(Table 1 is used in the primary route in this case, and Table 2 for the
secondary route):
ADD-
LDAT:LROUTE=1,LSVC=VCE,LVAL=1,TGRP=200,ODR=1,LAUTH=1,LDSRT=1;
ADD-
LDAT:LROUTE=1,LSVC=VCE,LVAL=2,TGRP=201,ODR=2,LAUTH=1,LDSRT=2;
Digit pattern (Example)
Dialed number Primary route forbidden Secondary route forbidden

001900X
: LDSRT 2
001904X
001905x LDSRT 1 LDSRT 2
001906x LDSRT 2
001907x LDSRT 1 LDSRT 2
001907x
: LDSRT 2
001909x
In this example, all numbers with the access code 0190 are generally forbidden
for the secondary route, with this prohibition only being restricted to numbering
blocks 5 and 7 in the primary route.

Language
LDSRT LDSRT d Nummer der LCR Digit String Restriction
Tabelle
Table
FDS d Nummer des First Digit Strings
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm

Language
FDS e First Digit String Number
SDS d Nummer des Sub Digit Strings
SDS e Sub Digit String Number
FDSFIELD d Index des Feldes in dem Anrufplan, das
FDS enthaelt
FDSFIELD e Index of the field in dialplan, which contains
FDS
SDSFIELD d Index des Feldes in dem Anrufplan, das
SDS enhaelt
SDSFIELD e Index of the field in dialplan, which contains
SDS
LWR d Nummer der LCR-Wahlregel
LDSRT d Nummer der LCR Digit String Restriction
Tabelle
Table
DIMSU LCRDSR d Anzahl der gesperrten Ziffernfolgen fuer
LCR Route Ele.
LCRDSR e Number of blocked digit strings for lcr route
elements
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Autorization PIN (Forced Authorization Code)
37.11 LCR Autorization PIN (Forced Authorization Code)

A PIN code is required for certain voice numbers configured in the LCR dial plan
for public network access or for access to tie trunk circuits for which a consultation
call was selected for the first call or a call forward was selected during execution.
A typical application case is, for example, on a campus, where users have to
identify themselves via PIN on generally accessible phones for the purposes of
call charging.
This PIN code can be dialed after the external number has been dialed (suffix
dialing), or prior to that via the COPIN digit analysis result (preselection). A PIN
is never demanded in transit systems, and a PIN code request is never sent in
the originating system.
A distinction is made between three manifestations in the case of the PINWM

feature (PIN digit pattern):
1. Unchecked (PCODE)
In this case, the PIN code comprises a defined number of digits. In the
existing PIN; this corresponds to the project code PCODE. The behavior
in the case of Unchecked, as well as its administration, is likewise the
same as for the PCODE.
2. Checked (PIN Mobile)
In this case, the PIN code must agree exactly. In the existing PIN, this
corresponds to the PIN Mobile. The behavior in the case of Checked, as
well as its administration, is likewise the same as for PIN Mobile.
3. Restricted (PIN Mobile with IDHome)
Restricted corresponds to Checked, but the "IDHome" feature is
additionally set in the COPIN. This results in the PIN code only being
accepted at the base station.
The PINWM (PIN digit pattern) feature is based on the existing PIN concepts (PIN
mobile, PCODE,...) and likewise uses existing PIN procedures. In order to setup
PINWM, the STN personal identification numbers must first be configured. A new
type of PIN (COPIN) has been added.
Whether or not a number in the network is subject to the PINWM test is
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
administrated in the LCR digit pattern. For this digit pattern, an LDPLN entry then
has to exist with parameter PINWM=YES (Default = No). If an incorrect PIN is
entered when the PIN is requested, the LCR is triggered.
IMPORTANT: During administration, it must be noted that the PINWM is only of

relevance for the first outgoing connection, and that a check of the PINWM in a
transit system no longer takes place. Numbers which are administrated as closed
numbering cannot be subject to the PINWM.

The user interface is essentially influenced by the following factors.
• Dialing the PIN with preselection (PCODE APIN10) or suffix dialing
• Entry of the PIN necessary in the case of PININT or PINNW
• Signaling of the calling party at the called party after identification via PIN
entry.
1. The PIN is dialed in preselection:

Before the number is dialed, the COPIN for PINWM is activated via the own
code (APIN10). This procedure is absolutely identical to identification via
digital analysis result.
2. The PIN is dialed in suffix dialing:

The following procedure applies to the Anate and Digite terminal devices:
• The calling party dials the complete number of the called party
• Calling party hears the Recall-Dial tone
– In the event of:
– PININT activated: Calling party dials the correct PIN code
– PINNW activated: Calling party dials home station number, followed by #

, then the correct PIN code and # again.
• Calling party hears the Confirmation tone

• In the case of digital terminal devices with display, the user prompting is
realized on the TE display with PINWM.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
• If authorization NPINWM (AMO COSSU) is set for a station in its COS, the
PIN test is thus broken through, i.e. the STN need not enter a PIN
(optional authorization), even if a test is envisaged for the digit pattern.
• If a valid PIN has been activated in preselection for PINWM testing (via
PCODE APIN10), the call can be continued without the PIN having to be
suffix dialed.
• A PIN activated by preselection is reset via PCODE (DPIN); the PIN can
likewise be deactivated through the Timeout of a timer (authorization code
timer). This timer is restarted for each call in which the PIN is to be tested.
• In the case of PINWM, it is possible to enter the PIN at the TE in a remote

system. In this context, the PIN test is performed at the TE in the home
station, to which end the station number always has to be dialed before the
PIN for PINWM .
In this case, the station number, the COPINNr and the PIN are sent in the
home station. (Presupposing the PINNW feature is released with AMO
FEASU)
• The PINWM is entered in the call detail record (see CDR and/or CDRe).
• If an incorrect PIN code is entered, this negative case is signaled and the
calling party has to restart the dialing procedure from the beginning.
• PINWM test is only available for voice services.
• In the case of attendant consoles and funct. terminal equipment, it is not

possible to enter a PIN code for PINWM.
• The AMO LDPLN indicates which digit patterns are subject to a PINWM test.
• Other COPIN´s can be declared as valid for the PINWM feature via the
parameter DPTEST. Thus, several COPIN´s can also be used for the PINWM
feature.
37.11.4 Generation (Examples)

Setting up a specimen PINWM for STN
At first, PIN’s must be configured for the STN.
• Increase PIN-Buffer:
ADD-DIMSU:TYPE=USER,PINBUF=80;
• Release the PININT function for the system:
CHANGE-FEASU:TYPE=RELEASE,CM=PININT;
• Release the PINNW function for the switch:
CHANGE-FEASU:TYPE=RELEASE,CM=PINNW;
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
• Set the COT parameter for the circuits in the case of PINNW:
ADD-COT:COTNO=2,PAR=PINR;
• COPIN10 in the event of Unchecked (PCODE)
ADD-PERSI:TYPE=SYS,PIN10LEN=6;
CHANGE-PERSI:TYPE=COPIN,COPIN=10,COTYPE=PCODE,PINTEXT="FAC,
(1CALL)", CDRTEXTS=NO,DISPRSTN=NO,PINTEST=LENGTH,TRKCD=0,
TRKCDTYP=NO,PINDUR=ONE,TRANSFER=NO,IDHOME=NO,
DISPID=PERMDISP,TRACE=NO,PINEXT=YES,DISPPIN=YES,PINNKEY=NO,
DEACKEY=NO,POSCHKN=1,COSHOME=NO,PINLCOS2=NO,DPTEST=NO;
The COPIN10 is setup as standard for Unchecked (PCODE). Of course, the
settings can also be made in a different COPIN (see Service Info).
COPIN10 for the event of Checked (PIN Mobile)
ADD-PERSI:TYPE=SYS,PIN10LEN=6;
CHANGE-PERS:TYPE=COPIN,COPIN=10,COTYPE=MOBILE,
PINTEXT="FAC,(1CALL)",CDRTEXTS=NO,DISPRSTN=NO,
PINTEST=TABLE,TRKCD=0,TRKCDTYP=NO,PINDUR=TIME,
TRANSFER=ALL,IDHOME=NO,DISPID=PERMDISP,TRACE=NO,PINEXT=YES,
DISPPIN=NO,PINNKEY=NO,DEACKEY=NO,POSCHKN=1,COSHOME=NO,
PINLCOS2=NO,DPTEST=NO;
ADD-PERSI:TYPE=STN,STNO=7140,NAME="PINWMCHE",
PIN10="103157",PININDIV=YES;
The COPIN10 is setup as standard for Unchecked (PCODE). Of course, the
settings for Checked can also be made in a different COPIN.
• COPIN10 for the event of Restricted (PIN Mobile with IDHome)

ADD-PERSI:TYPE=SYS PIN10LEN=6;
CHANGE-PERSI:TYPE=COPIN,COPIN=10,COTYPE=MOBILE,
PINTEXT="FAC,(1CALL)",CDRTEXTS=NO,DISPRSTN=NO,
PINTEST=TABLE,TRKCD=0,TRKCDTYP=NO,PINDUR=TIME,
TRANSFER=ALL,IDHOME=YES,DISPID=PERMDISP,TRACE=NO,PINEXT=YES,
DISPPIN=NO,PINNKEY=NO,DEACKEY=NO,POSCHKN=1,COSHOME=NO,
PINLCOS2=NO,DPTEST=NO;
ADD-PERSI:TYPE=STN,STNO=7140,NAME="PINWMRES",
PIN10="103157", PININDIV=YES;
Preselection *51 PIN 90xxxx
Suffix dialing 90 PIN xxxx
Figure 35 Example of a user interface
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
PINWM preparation for preselection

• Setup DAR for PIN (DTMF AND DP):
ADD-WABE:CD=*51,DAR=APIN10,CHECK=NO;
ADD-WABE:CD=*851,DAR=APIN10,CHECK=NO;
• Setup timeout for voice (300 seconds as standard):
CHANGE-CTIME:TYPESWU=CP2,PINVO10=300,PINNV10=1800;
PINNV10 has no relevance to PINWM, as only valid for Voice.
Setup PINWKZ for suffix dialing

• Assign LCOSV the COPIN 10:
CHANGE-COS:TYPE=LCOSV,LCOSV=5,COPIN=10;
In the LCOSV, the type of PIN code to be tested is assigned (Unchecked,
Checked, Restricted).
• Setup "Recall dial tone" and "Confirmation tone":

CHANGE-ZAND:TYPE=ALLDATA2,CONFTONE=YES;
• Break through authorization (STN with COS No. 13 need not suffix dial a
PINWM):
CHANGE-COSSU:TYPE=COS, COS=13,AFAX=NPINDP;
It is never necessary to dial a PIN code with breakthrough authorization.
• Declare COPIN 1 valid for PINWM:

CHANGE-PERSI:TYPE=COPIN,COPIN=1,DPTEST=YES;
If an STN has presented identification through preselection of COPIN1 and
the parameter DPTEST=YES is set in COPIN1, this COPIN1 counts as being
an already activated PINWM COPIN and renewed dialing of the PIN code (in
suffix dialing) is thus rendered superfluous.
Activate PINWM for an LCR digit pattern (with PIN prompt):

ADD-LDPLN:LDP="90"-"XXXX",LROUTE=190,LAUTH=3,SPC=22,PINDP=YES;
The digit pattern must correspond to a block dial. Otherwise, dialing the number
is interrupted by entry of the PIN.
The rest of the number then has to be suffix dialed.

Language
COSSU TYP d Verzweigungsparameter
TYPE e Desired cossu option
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm

Language
LCOSS d LCR-Class-of-Service Nummer fuer
Sprache (FAX)
LCOSV e LCR class of service number for voice (FAX)
COPIN d class of pin for dialing pattern
COPIN e class of pin for dialing pattern
COT COTNU d Class of Trunk (Nummer)
COTNO e Class of Trunk
COTPAR d Parameterwerte für eine Class of Trunk
PAR e Parameter values of a Class of Trunk
CTIME ARTSWU d Verzweigungsparameter
TYPESWU e Desired timer category
PINVO10 d Überwachungszeit fur Gültigkeit der PIN
COPIN 10 SPR
PINVO10 e time for validation of the pin of COPIN 10 for
voice
PINNV10 d Überwachungszeit fur Gültigkeit der PIN
COPIN 10- NV
PINNV10 e time for validation of the pin of COPIN 10 for
non voice
DIMSU PINBUF d anz. der dyn. PIN Speicher bei netzweiter
Identifizierung
PINBUF e no. of dynamic pin buffers for network-wide
identification
FEASU TYP d Typ der Verarbeitung
TYPE e Desired class mark facility options
LM d Leistungsmerkmal
CM e Feature, class mark, facility
PINDP d PIN fuer Anrufplan gebraucht
PINDP e PIN for dialing plan requested
PERSI TYP d Verzweigungsparameter
TYPE e desired personal identification options
COPIN d class of pin
COPIN e class of pin
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Classes of Service LCOS (AMO COSSU)

Language
PINTYP d Typ fuer netzw. transfer der copin im Cornet
Protokoll
PINTYPE e type of pin
PIN10LAE d Laenge der PIN fuer pin-art 10
PIN10LEN e Length of pin for pin type 10
WMPRUEF d PIN art ist gueltig fuer Wahlmusterpruefung
DPTEST e PIN type is valid for dailing pattern check
PINDAUER d Dauer der aktiviertenPIN
PINDUR e duration of the activated pin
PINPRUEF d PIN Pruefung
PINTEST e pin test
CD e Access code / station number
KZP d Kennzahlpunkt
CONFTON d Ein/ausschalten beep Mechanismus im DH
CONFTONE e Act/deact beep mechanism in DH
37.12 LCR Classes of Service LCOS (AMO COSSU)

There are 64 LCR class marks which can be used for controlling the dialing plan
prioritization and for trunk group selection within a route.
All told, 32 LCR classes of service (LCOSV and LCOSD) can be created with the
combination of the 64 class marks (LCOS). In addition to its conventional COS,
every station, circuit and attendant console is also assigned an LCOSV/LCOSD
setup with the AMO COSSU for the authorization test in the case of LCR. 
The LCOS’s of the LCOSV/LCOSV are prioritized in the path selection when
outgoing in the case of the AMO’s LDPLN / LDAT IN. 
In the case of circuits whose signalisation behavior does not allow the
transmission of the LCR class marks, the COT parameter OLCR / OLRD
(signalisation procedure without LCR) must be set. In this case, the LCR class
marks of the circuit (e.g. assigned with AMO TDCSU, parameter LCOSV) are
used for all incoming calls.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Classes of Service LCOS (AMO COSSU)
OpenScape 4000 B OpenScape 4000 A Foreign PABX

AMO S0/S2 Line
AMO E&M line
TDCSU Cornet-NQ TDCSU
LCOSV=2 LCOSV none
=1 Transmission
of the LCOSx
AMO S0/S2 Line COT
TDCSU with
Cornet-N
LCOSV=3 NLCR
5237
STN C: Without LCOSV
47000 39500
STN B: LCOSV=6 STN A: LCOSV=4
Figure 36 LCR Class Mark Transmission

• The LCR class marks of the stations are transmitted network-wide with
Cornet.
• Without the corresponding COT parameters NLCR / NLRD (signalising

without LCR), the LCOSV/LCOSD values in the circuits are of no relevance.
• During path selection, the LCOS’s of an LCOSV/LCOSD can be temporarily

changed by means of the AMO KNLCR.

For STN A, LCOSV=4 (assigned in AMO SCSU/SBCSU) applies in the path
selection in the OpenScape 4000 A and also the OpenScape 4000 B. STN C has
no LCOS attributes and, with COT parameter NLCR set in OpenScape 4000 A,
is assigned the prefixed LCOS value in the circuit, which is then further
transmitted in the network and used for authorization checking (see diagram
"LCR Class Mark Transmission").
• Enter the authorization code in the outpulsing with AMO LODR:

CHANGE-COSSU:TYPE=LCOSV,LCOSV=1,ALCR=2,INFO="LCOS FOREIGN
SYSTEMS";
• Enter the authorization code in the outpulsing with AMO LODR:
ADD-COT:COTNO=100,PAR=DFNN,INFO="COT FOR FOREIGN SYSTEMS";
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Authorization Codes (AMO LAUTH)

Language
Sprache (FAX)
LCOSD d LCR-Class-of-Service Nummer fuer Daten
(DEE)
LCOSD e LCR class of service for data (dte)
ELBER d Einzufuegende LCR-Berechtigung
ALCR e LCR classmarks to be activated
INFO d Service Informationen z.b. fuer welchen
Leitungstyp die LCOS geeignet ist
INFO e Service information e.g. what kind of trunk
matches with LCPOS
INFO d Service Informationen z.B. für welchen
Leitungstyp die COT geeignet ist.
INFO e Service Information e.g. what kind of trunk
matches with COT
37.13 LCR Authorization Codes (AMO LAUTH)

Definition table of the authorization codes for access from a private network to
services of public third-party providers. The codes entered in this table can be
used with the dial rule 
(dial rule element OUTCODE in AMO LODR) for outpulsing purposes.
In this context, the link between the two AMOs is established via the parameter
INDEX.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Authorization Codes (AMO LAUTH)

The authorization codes can be implemented in the database per ITR Group.
IMPORTANT: During administration, the authorization code can be entered both

in encrypted and unencrypted form. However, only the encrypted form is regen-
erated.

The digit pattern 0-W-031-X is to refer to trunk group 12, which leads to a provider
who requires authentication via code "123456789".
• Enter authorization code with parameter CODE in AMO LAUTH:

EINR-LAUTH:ITR=0,INDEX=1,FORMAT=NORMAL,CODE=123456789;
• Define LCR route with AMO RICHT
ADD-RICHT:MODE=LRTENEW,LSVC=VCE,LRTE=12,NAME="VENDOR 2",
TGRP=12;
• Enter authorization code in the outpulsing with AMO LODR:
ADD-LODR:ODR=12,INFO="WITH OUTPULSING 1";
ADD-LODR:ODR=12,CMD=ECHO,INDEX=1; 
ADD-LODR:ODR=12,CMD=ECHO,FIELD=3; 
ADD-LODR:ODR=12,CMD=ECHOALL;
• Use AMO LDAT to assign LCR dial rule (ODR) to a route (LROUTE):
ADD-LDAT:LROUTE=12,LSVC=VCE,LVAL=1,TGRP=12,ODR=12,LAUTH=1;
• Setup LCR digit pattern (LDP) with AMO LDPLN:
ADD-LDPLN:LDP= 0-W-031-X,LROUTE=12,LAUTH=1;

Language
LAUTH VBZ d Nummer der Verkehrsbeziehungsgruppe
ITR e Internal traffic restriction group number
INDEX d Index des Berechtigungscodes
INDEX e Index of Authorization Code
FORMAT d Eingabe des Berechtigungscode normal
oder verschluesselt
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Source Dependant (AMO KNLCR)

Language
FORMAT e Use normal or encrypted format
CODE d eingerichteter Berechtigungscode
CODE e Normal authorization code
LWR d LCR-WahlregelNummer
37.14 LCR Source Dependant (AMO KNLCR)

As a function of the combination of source/destination nodes, different LCR
routes can be selected without rendering a special LCOS assignment necessary.
This source/destination controlled seizure of LCR routes is achieved through
modification of the LCR class marks (LCR-LCOS’s from LCOVS or LCOSD - i.e.
service-independent) upon entry in the path selection) with the AMO KNLCR.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Calling Party
LCOSV
LCOSD SNNO
Path selection
AMO WABE
AMO LDPLN
LAUTH
AMO RICHT AMO KNLCR

DNNO DNNO SNNO ADDSLCOS REDSLCOS
AMO LDAT
LAUTH DNNO
AMO LODR
Calling Party
LCOSV
SNNO LCOSD
Figure 37 Procedure for a Source Independent Call Setup
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
As every connection is specified by a combination of source node and destination

node, an expansion or reduction of individual LCOS’s can be administrated for a
node number pair (SNNO / DNNO). These changes in the authorization
transmitted are taken into account during the test of the access rights in AMO
LDAT, in order to seize a trunk group.
Thus, the option of using or blocking an LCR route can be enabled both for single
and multiple nodes of a network.
(e.g.: to prevent or selectively enable central office breakouts.)

• Source / destination node numbers can also be in other physical nodes.
• Source and destination node numbers must be virtual node numbers of the
same priority.
• Renewed transit through the modification also takes place in the case of
rerouting.
IMPORTANT: Modification of the LCOS’s only serves the path selection

within the routes defined in AMO LDAT and is not permanently changed or
propagated.
• This function can also be combined with other LCR features.
A B C
LCOSV:LAUTH=1&&11 LCOSV:LAUTH=1&&12 LCOSV:LAUTH=1&10&11
KNLCR:
ADDSLOCS=11&12
REDSLCOS=10
1-1-10 1-1-100 1-1-800
LDAT: LAUTH=10 LDAT: LAUTH=10
A B C
LDAT:LBER=12 LDAT:LAUTH=11&12
1-1-888
ISDN CO
Figure 38 Example of a Source Dependent Call Setup
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Source Groups (AMO LPROF)

From Node A (NNO=1-1-10) to Node B (NNO=1-1-100), as well as Node C
(NNO=1-1-800), the connection from Node A is to be possible for all subscribers.
Subscriber A can call B and C, but cannot use the secondary route in Node B to
CO ISDN (NNO=1-1-888) via a tie trunk to Node C (NNO=1-1-800) - for which the
LAUTH 10 is likewise necessary.
• Definition of access modifications with reduction of the LAUTH 10 and

additional expansion of the LAUTH 11&12 for access to the trunk:
ADD-KNLCR:SNNO=1-1-10,DNNO=1-1-
888,ADDSLCOS=11&12,REDSLCOS=10;

Language
KNLCR UKNNR d Ursprungsknotennummer
SNNO e Source node number
DNNO e Destination node number
ERWLBER d Erweiterung der vorgegebenen LCR-
Berechtigung
ADDSLCOS e Add to LCR classmark subset
REDLBER d Reduzieren der vorgegebenen LCR-
Berechtigung
REDSLCOS e Reduce the LCR classmark subset
37.15 LCR Source Groups (AMO LPROF)

Depending on the source group, different LCR routes can be selected without, for
instance, rendering a special LCOSx assignment necessary. This allows not only
the routing to be designed on a node-dependent basis, but also to be broken
down even further (e.g. distinction according to shelf).
The LCR routes belonging to a source group are defined in a table with the AMO
LPROF. In AMO LDPLN, it is then possible to refer to such a table with the
parameter PROFIDX.
If an index entry exists in the digit pattern (in AMO LDPLN), the table
administrated by AMO LPROF is branched too, and concurrence of the specified
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
source group with the table values checked. If a matching entry is found, the
further path selection is realized on the basis of the 
LTRE specified therein, otherwise, the LROUTE originally entered in AMO
LDPLN is further used for path selection.

• A source group can be explicitly assigned to a "Calling Party" (e.g. with AMO
SDAT) or, as standard, derived from the slot (in shelf, AMO UCSU).
• In the table administrated by AMO LPROF, the same LROUTE entry can be
specified as the LROUTE already defined for the digit pattern in AMO LDPLN.
• In AMO LPROF, only valid, i.e. existing, LRTE’s can be entered.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Calling Party
Dial SRCGRP
Select path
AMO WABE
AMO LDPLN AMO LPROF
LROUTE PROFIDX PROFIDX SRCGRP LRTE
AMO RICHT
AMO RICHT
LRTE
LRTE
AMO LDAT AMO LDAT

LROUTE LROUTE
AMO LODR AMO LODR
Called Party Called Party

(no concurrence (LRTG for SRCGRP
of SRCGRP) exists)
Figure 39 Procedure of a Source Group-Dependent Call Setup
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LRTE=100
ISDN
LTU: 17
Berlin
SDAT:DATA1
SRCGRP=2
LTU: 2
LRTE=1
ISDN
Munich LTU: 1
LDP=0-110
Figure 40 Example of a Source Group-Dependent Call Setup

• Setup LTU 17 with Source Group 2:
ADD-
UCSU:UNIT=AP,LTU=17,SRCGRP=2,FRMTYPE=INCH19,CONNTYPE=NBCSIPDL
,LOCATION="TESTLAB";
• or setup STN in LTU 17 with Source Group 2:
CHANGE-SDAT:STNO=7140, TYPE=DATA1,SRCGRP=2;
• Definition of LCR route 100 (route for outbreak "ISDN Berlin") for Source
Group 2 with AMO LPROF:
ADD-LPROF:PROFNAME="EMERGENCY",SRCGRP=2,LRTE=100;
• Reference to a source group table entry (here: Index 1) with AMO LDPLN:
ADD-LDPLN:LDP=0-110,LAUTH=1,LROUTE=1,PROFIDX=1;

Language
UCSU SRCGRP d Source-Gruppen Index
SRCGRP e Sourcegroup index
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Dial Rules (AMO LODR)

Language
INCH19 d 19 zoll - rahmen fuer ap shelfs
INCH19 e 19 inch frame for ap shelves
NBCSIPDL d ap shelf verbunden via ip - direct
link
NBCSIPDL e ap shelf connected via ip - direct
link
NBCSIPNW d ap shelf verbunden via ip netzwerk
NBCSIPNW e ap shelf connected via IP net
LPROF PROFIDX d LCR Profil-Index
PROFIDX e LCR Profil-Index
SRCGRP d Source-Gruppen Index
SRCGRP e Sourcegroup index
PROFNAME d LCR Profillname
PROFNAME e LCR Profile name
LRTG d LCR Richtung
LRTE e LCR Route
PROFIDX d LCR Profile Index
PROFIDX e LCR Profile Index
SDAT TYP d DATEN1
TYPE e data1
SRCGRP d quell gruppen index
SRCGRP e source group index
37.16 LCR Dial Rules (AMO LODR)

In order to control outpulsing, assign each route element a dial rule. A dial rule
(ODR) is a batch comprising one or more dial rule commands. The ODR’s created
with the AMO LODR are needed in the case of AMO LDAT, with the parameter
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Dial Rules (AMO LODR)
ODR representing the link between these in this context. An ODR comprises
consecutive, individual LCR dial rule elements (CMD) and is terminated with the
CMD END.
Dial rule commands:

OUTPULSE <ziffern> Transmission of <digits>
PAUSE <n sec.> Interrupt outpulsing for n sec.
WAITANS <n sec.> Wait for 2nd dial tone
OUTCOEX <coex> Class of external
OUTCSN <index> Transmission of the call serial number
OUTCODE <index> Transmission of an authorization Code
... ...
ECHO <field> Transmission of field <field> of the dialing plan

ECHOALL Transmission of the remaining digits
END End of the command batch.
You thus specify the digits to be transmitted for an LCR route and their order, as
well as the format.

Instead of the dialed digit pattern 0-030-4711, 010330304711 is to be transmitted
on the line.
• Definition of the dial rule with AMO LODR

ADD-LODR:ODR=10,INFO="WITH CALL BY CALL 01033";
ADD-LODR:ODR=10,CMD=OUTPULSE,DGTS=01033; 
ADD-LODR:ODR=10,CMD=ECHOALL; 
• Assignment of the dial rule generated to a route with AMO LDAT parameter
ODR:
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Traffic Dependant (Line Reservation AMO BUEND)

Language
LWR d LCR-WahlregelNummer
37.17 LCR Traffic Dependant (Line Reservation AMO BUEND)

The reservation of circuits for traffic dependent dynamic routing (seizing B-
channels for direct connections) can be activated or deactivated per trunk group
with the AMO BUEND. This results in the threshold value, i.e. the minimum
number of free B-channels as of which the trunk group can be used as an
alternative route in the path selection, being automatically computed and stored
pursuant to the number of configured (n) B-channels in the trunk group according
to  n   2 .
Number of Threshold value Number of Threshold value

configured circuits configured circuits
1 11 529 - 624 12
2-8 1 625 - 728 13
9 - 24 2 729 - 840 14
25 - 48 3 841 - 960 15
49 - 80 4 961 - 1088 16
81 - 120 5 1089 - 1224 17
Table 8 Threshold Value as a Function of the Number of Configured Circuits
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Number of Threshold value Number of Threshold value

configured circuits configured circuits
121 - 168 6 1225 - 1368 18
169 - 224 7 1369 - 1520 19
225 - 288 8 1521 - 1680 20
289 - 360 9 1681 - 1848 21
361 - 440 10 1849 - 20002 22
441 - 528 11
Table 8 Threshold Value as a Function of the Number of Configured Circuits

1 Special case: trunk group with one circuit - no rerouting possible.
2 Max. number of circuits per trunk group
In order to distinguish between direct connection and alternative connections, the

alternative paths of a route must be labelled. This is realized by setting the
attribute ALTTGR ("variable trunk group") in AMO LDAT for the respective LCR
route elements which serve as alternative paths.
This can prevent direct connections no longer being possible via a trunk group
(e.g. Trunk Group No. 30, i.e. Connection AC as depicted in diagram below), as
this connection is seized upon overflow of Route AB. A so-called overflow or a
call setup via an alternative route element can then only take place if more
channels are still free than the reservation threshold value specifies.
TDDRFLAG=ON 1
A TGRP = 20 TGRP = 10 B
1-89-100
1-89-200
TDDRFLAG=ON
LATTR = ALTTGR
BUNUM = 30 TGRP = 40
2
TGRP = 40
TGRP = 30
TDDRFLAG=ON
LATTR = ALTTGR
3
TGRP = 20
TDDRFLAG=OFF
D TGRP = 20 TGRP = 10 C
1-89-400
1-89-300
TDDRFLAG=O
TGRP = 30 TGRP = 40
Figure 41 Traffic Dependent Routing
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm

• The number of channels that remain reserved for direct connections is
stipulated pursuant to ITU-T E.412 and cannot be altered through an explicit
parameter, but only implicitly via the number of configured circuits of a trunk
group.
• The parameter TDDRFLAG is always set to ON as the default value when

setting up a new trunk group.
• This function is service-independent and applies both to analog and digital

channels.
• The number of reserved channels can be queried by means of AMO BUEND.
• For the special case of a single configured circuit, the parameter

TDDRFLAG=OFF should be set.
• If, during path selection, a route is selected in which the attribute ALTTGR is
active, this property is transmitted to the network (e.g. with Cornet Protocol)
and also taken into account in subsequent path selections in the network.

Changing the existing LCR in Network Node A in order to activate the feature.
• Preparation of the existing trunk group (20) for taking traffic dependent routing
into account in Network Node A with AMO BUEND:
CHANGE-BUEND:TGRP=20,TDDRFLAG=ON;
• Labeling the 3rd route (Route 200 to Node B) as a "variable trunk group" with
AMO LDAT:
CHANGE-LDAT:LRTG=200,LRTEL=3,LATTR=ALTTGR;

Language
BUEND BUNUM d Bündelnummer
TDDRFLAG d belastungsabhaengiges Dynamic Routing
Flag
TDDRFLAG e traffic dependent dynamic routing flag
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Inserting/Removing in a Queue (AMO LDAT)

Language
LRTGEL d LCR-Richtungselement nummer
LRTEL e LCR route element number
37.18 Inserting/Removing in a Queue (AMO LDAT)

The term queuing incorporates inserting/removing assignment requests for lines
in a queue (trunk/direction).
The term queuing can be described as follows:
• waiting in the Route Advance Delay queue
• waiting in the OFF-hook queue
• waiting in the ON-hook queue
A call can be inserted/removed from a queue in the following two cases:
1. If the LVAL of all trunk groups is identical and no B channel is found in any of
the trunk groups, OFF-Hook Queuing (B) is executed directly.
2. The trunk groups are prioritized. The call is initially queued via the Route
Advance Delay (A) feature. If, however, no B channel is found in the highest
prioritized trunk group, OFF-Hook Queuing (B) is executed
LROUTE route to CO
1. Situation 2. Situation
LVAL Provider 1,
LVAL
Inexpensive
=1 =1 A
Provider 2,
Expensive
=1 =2 A
Provider 3,
Extortionate
=1 B =3 B
Figure 42 Inserting/removing according to LVAL
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
Removing calls:
If a B channel is free, this is made available to the call already inserted. In this
context, the queue (A,B) in which the call is located is irrelevant; assignment of
the B channel is based on the prioritization of the inserted call.
The following prioritization applies in this context:
Prio Designation
0 Insert station in ON-hook queue
1 Insert station in route ADV queue
2 Station
3 Insert station in OFF-hook queue
4 Attendant console
5 Multy level pre-preemption
6 Emergency
Table 9 (The priority with the highest value is assigned first)
37.18.1 Interrupting B Channel Search with Route

Advance Delay
The Route Advance Delay feature allows the search for an available trunk to be
interrupted for a set time. After this time has elapsed, a more expensive trunk is
searched for. However, if a cheaper trunk (1) becomes available within this time,
the time is stopped and the relevant trunk group is assigned.
If the search for a B channel is interrupted and if the delay timer is greater than
two seconds, this will be signalled to the user by a short tone. It is therefore
possible for the user to search in a cheaper trunk.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LROUTE route to CO AMO-LDAT
Provider 1,
Inexpensive LVAL=1
1.
Provider 2,
Expensive LVAL=2
1.
Provider 3,
Extortionate LVAL=3
Figure 43 Queuing with cn Route Advance Delay
The only signal is the Route Advance Delay tone. This tone is only sounds if the
timer for the delay reads is greater than two seconds.
• If calls have the same priority, the FIFO principle applies.
Restrictions for insertion/removal from the queue:
• As lines can only be switched if they are actually available, the feature (insert
in queue) is not available to the AC.
• Direct Call Park/Call Forwarding No Replay (CFNR) and insertion into the
queue is not possible.
• As regards the DB, Route Advance Delay is assigned to the callbacks.
• The parameters LVAL of the trunk groups in AMO LDAT must have different
priorities. If all LVAL’s have the same priorities, the next trunk group is
switched to directly, as before.
• The Route Advance Delay tone can be separately activated
• The Route Advance Delay feature is only active if the value of the RTAD timer
is set at > 0 seconds in the AMO CTIME.
The default RTAD timer value is 0 seconds. This means that the feature is
deactivated.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
37.18.1.4 Generation (Example)
• Dimensioning the callback buffer:

ADD-DIMSU:TYPE=USER,CBK=40;
• Prioritizing the trunk groups, example for TGRP 51,52,53:
ADD-
LDAT:LROUTE=400,LSVC=ALL,LVAL=1,TGRP=51,ODR=4,LAUTH=1,CARRIER
=1, 
ZONE=EMPTY;
ADD-LDAT:LROUTE=95,LSVC=ALL,LVAL=2,TGRP=52,ODR=4,LAUTH=1,
CARRIER=1, 
ZONE=EMPTY;
CARRIER=1, 
ZONE=EMPTY;
• Activate Route Advance Delay Tone:
CHANGE-COSSU:TYPE=LCOSV,LCOSS=1,ALCROPT=RTADT;
• Administrate length of the Route Advance Delay, 6 seconds:
CHANGE-CTIME:TYPESWU=CP2,RTAD=6;
• Release Route Advance Delay Tone and assign SIU Tone:
CHA-ZAND:TYPE=DATA2,ROUTTONE=YES;
CHANGE-ZAND:TYPE=TONES,CPCALL=RTCHKNTF,SIU="2";

Language
CTIME ARTSWU d Verzweigungsparameter
TYPESWU e desired timer category
RTAD d Überwachungszeit fur Gültigkeit der LCR
Route
RTAD e time for validation of LCR route advanced
Sprache (FAX)
ELCROPT d Einfügen LCR-Optionen
ALCROPT e Add LCR options
DIMSU RR d Dimensionierung der Rückruf Buffer
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm

Language
CBK e no. of dynamically assignable pool elements
for callback
CPTON d Vermittlungstechnischer Ton
CP e Call processing tone
SIUTON d Zugeordneter Ton der SIU
SIU e Assigned siu tones
ROUTTON d Aktivieren des Routing Ton
ROUTTONE e Activate connect routing tone
37.18.2 Off-Hook Queue
A call is queued off-hook if no B channel is free in any of the trunk groups. This
results in a B channel being reserved for the station. An Off-Hook queue can
likewise take place in a transit station (Node 1-89-200). If a B channel becomes
free, this is assigned to the queued call/circuit with the highest priority.
If a direction (AMO LDAT) has been assigned to the parameter LATTR with the
parameter value OHKQ, the call is inserted into the off-hook queue.
In the transit case, the LCOSV of the station must additionally be assigned the
parameter value OHKQT, and the COT of the incoming circuit the parameter
value OHKQ.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
1-89-100 1-89-200
LATTR: OHKQ LATTR: OHKQ

COT: OHKQ
LCOSV: OHKQT
Figure 44 Off-Hook Queuing
The station receives no specific signaling.
• As regards the DB, off-Hook Queuing is assigned to the callbacks.
• In the transit case, the parameter value OHKQT must be set in the COT of
the incoming transit circuit.
• The LCOSV must be assigned OHKQ, with OHKQT also being necessary in
transit cases.
• In AMO LDAT, the parameter value OHKQ must be assigned in LATTR.

• Setup a route (here: to Node 1-89-200) for off-hook queuing:
LATTR=OHKQ;
• Release off-hook queuing with a transit case for LCOSV:
CHANGE-COS:TYPE=LCOSV, LCOS=7,ALCROPT=OHKQ&OHKQT;
• Release the COT Off-Hook Queuing for a transit case:
ADD-COT:COTNO=2,PAR=OHKQ;
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm

Language
Sprache (FAX)
(DEE)
for callback
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
37.18.3 ON-hook Queue
If there is no free B channel in all the trunks, this is signalized to the user by a
second acknowledgment tone, so that he can then insert the call into the ON-
hook queue. This way a B channel is reserved for the user. If a B channel is
available, this is assigned to the highest priority inserted call/unit.
If a direction (AMO LDAT) is assigned the parameter LATTR with the parameter
value ONKQ, the call is inserted into the ON-hook queue.
1-89-100 1-89-200
LATTR: OHKQ LATTR: OHKQ

COT: OHKQ
LCOSV: OHKQT
Figure 45 On-hook Queuing
A second acknowledgment tone signalizes to the user that the function for
inserting a call into the ON-hook queue can be activated.
Activation:
• Opti-Point
By confirming the menu "call back", insertion into the ON-hook queue is
activated.
• Anate
By confirming the "flash key" and suffix dialing of the digit analysis result
ACBK, insertion into the ON-hook queue is activated.
• As regards the DB, the ON-hook queue is assigned to the callbacks.
• The LCOSV must be assigned to ONKQ.
• The parameter value ONKQ in the LATTR must be assigned in the AMO
LDAT.
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm

• Set up a route for the on-hook queue:
ADD-LDAT:LROUTE=200,LSVC=ALL,LVAL=1,TGRP=20,LVAL=1,LAUTH=1,
LATTR=ONKQ;
• Release on-hook queue with a transit case for LCOSV:
CHANGE-COSSU:TYPE=LCOSV, LCOSV=7,ALCROPT=ONKQ;

Language
Sprache (FAX)
(DEE)
for callback
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Generation

Language
37.19 LCR Generation

In order to be able to setup LCR, the generation sequence must be complied with.
DIMSU WABE COSSU LDPLN
LPROF
BUEND TACSU RICHT LDAT
TDCSU
TSCSU
DIMSU
LAUTH LODR
LDSRT
LSCHD
ZAND KNDEF KNLCR
Figure 46 Generierungsablauf LCR
A31003-H3170-S103-6-7620, 02/2019
lcr_en.fm
LCR Generation
A31003-H3170-S103-6-7620, 02/2019
rerouting_en.fm
LCR Rerouting
Internal Rerouting Disabled
38 LCR Rerouting
38.1 Internal Rerouting Disabled

This SIS is used on DX when a network is created such that there are nodes with
only 1 route out to a particular destination.In this situation congestion is
unavoidable, and so in order to stop the situation where the call drops back and
the node tries a different route, which will inevitably lead to the same point of
congestion, IRD is used. This is administered on a network basis.
1 4 5
7626166 7382121
This trunk group is a
“bottleneck” in the
network
Figure 47 Network with Internal routes only
If a point of congestion is encountered in the network then then IRD flag is sent
backwards.
In Figure 47 there is a possible point of congestion between nodes 4 and 5.

Without the Internal rerouting Disable being set a call from Node 1 to Node 5
would route initially to node 4 via Node 2. A Disc message would be sent back
from Node 4 with the cause No Route to Dest.
The LCR in Node 1 would then choose the alternate route via Node 3 but with the
same result a Disc with the same clearing code.
This can lead to a dynamic loading of the network To overcome this the IRD
feature is to be used.In this case the clearing message is accompanied by a
further flag which says no internal rerouting is enabled
This is done in the route element leading to the congested route
A31003-H3170-S103-6-7620, 02/2019
rerouting_en.fm
LCR Rerouting
External Rerouting Disabled
ADD-
LDAT:LROUTE=xx,LSVC=ALL,TGRP=xx,ODR=xx,LAUTH=xx,LATTR=INTBNEC
K;
When a LROUTE ends in a bottleneck of the net, all trunk groups to this LROUTE
have to be marked with the attribut "INTBNECK".
In the followin g figure LCR searches for a new route. In the database it is verified
whether the new route leads to a Foreign network or not.This is marked in the
COT of the trunk
CHANGE-COT:COTNO=xx,COTTYPE=COTADD,PAR=NTBO;
The system administrator knows the network boundary of the private network and
can set the COT parameter "NTBO" where it’s necessary, and if it not then the call
is disconnected.
In the following figure the call would route out to the public network at sys 3 as the
route is marked as a network boundary (this assumes the route is in the LDAT for
this call).
Sys 1 Sys 3 Sys4
SETUP
SETUP SETUP
DISC
CAUSE= No Route to Dest

No_int_Rer=TRUE
PUBLIC Sys 5
SETUP SETUP
SETUP_ACK
SETUP_ACK SETUP_ACK
On receipt of the DISC message Sys 3 would reroute only if the chosen route is
marked as a network boundary i.e COT parameter NTBO is set
38.2 External Rerouting Disabled

External rerouting by to the public or Foreign networks may want to be disabled
througout the network there by giving the originating system control
A31003-H3170-S103-6-7620, 02/2019
rerouting_en.fm
LCR Rerouting
COT :NTBO Public

Sys 2 ISDN or Foreign
Network
Sys 3
All B channels busy

LATTR :
NOEXTRTE
Sys1
COT :NTBO Sys 4
Public
ISDN or
Foreign
Network
Figure 48 External Rerouting Disabled
When a system wants to decide for itself if it is possible to route to a foreign

network the LDAT attribute NOEXTRTE must be set in each specified element of
the used routes.
In the example in Figure 48 a call is setup from system 1 to sys 4 and encounters
congestion between system 3 and 4.The cot parameter NTBO is set in Public/
Private route to the foreign network and normaly the call would reroute to this
route from system3.
However system 1 wishes to use it’s own connection to the external network (and
then only if the route via system 2 is congested)and marks the outgoing setup
message with the attribute No External Rerouting set by:
ADD-
LDAT:LROUTE=xx,LSVC=ALL,TGRP=xx,ODR=xx,LAUTH=xx,LATTR=NOEXTRT
E;
A31003-H3170-S103-6-7620, 02/2019
rerouting_en.fm
LCR Rerouting
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
Introduction to MFC-R2 Signaling
39 MFC-R2 Signaling
After a general introduction, this chapter describes some tips and tricks for using
MFC-R2 signaling. The system uses MFC-R2 signaling when setting up the
connection. Because this was implemented in the DH-Länder (DS120Vx), the
comments given in the main chapter "Country-Specific Connection Techniques
With Analog Trunks" also applies.
39.1 Introduction to MFC-R2 Signaling

This section provides a short introduction to MFC-R2 register signaling according
to CCITT. For detailed information, refer to CCITT Recommendation Q.440 or to
the guidelines published by the individual administrative authorities.
The MFC register signals are exchanged between the registers of the originating
and terminal exchanges (end-to-end) in compelled inband signaling. There is a
distinction made between the two different signal directions: forward (originating
exchange to terminal exchange) and backward signals (terminal exchange to
originating exchange). They are used for exchanging information when setting up
a connection.
The forward signals are the dialing information (digits), type and origin of the
connection, and others. Each signal (1...15) consists of two frequencies (2 of 6).
To differentiate between the directions, there is an upper frequency group
(1380...1980 Hz, at intervals of 120Hz intervals) for the forward signals and a
lower frequency group.
The backward signals are retrieval, status of the user connections, user class of
service, and others. The backward signals use the lower frequency group
(1140...540 Hz, at intervals of 120 Hz).
There are administrative authorities that use only the signals 1...10 for the PBX
connections. This can save on configurations (2 of 5 instead of 2 of 6 code). The
OpenScape 4000 SIU can always handle the entire range of signals (2 of 6). You
can filter out signals 11 ... 15 by choosing the appropriate configurations (MFCTA,
MFC conversion table).
The introduction of MFC-R2 register signaling according to CCITT Q.440 also

included the implementation of signaling according to SOCOTEL (for France) and
IBERCOM (for Spain). These types of signaling are not discussed here.
39.1.1 Compelled Signaling According to MFC-R2

In this type of signaling, Exchange A sends each forward signal to Exchange B
until the remote central office (exchange B) recognizes it and acknowledges it
with a backward signal (from B to A). The exchange of signals always starts with
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
the sending of a forward signal (signal offer). As soon as Exchange A detects the
acknowledge signal, it deactivates the pending forward signal. As soon as
Exchange B detects that the forward signal has been dropped, it deactivates the
backward signal.
Exchange A Exchange B
(originating register, source) (end register, destination)
Transmitter
Forward signal on Receiver
Transmitt
Receiver Backward signal on
Forward signal off
Backward signal off
Response or delay time
39.1.2 Example of a Connection Set-Up
Originating register A End register B
Forward signals Backward signals
Transmit. Receiver Transmit. Receiver

I - 5
(100s) A - 1
Send next digit
I -1
(10s) A - 1
Send next digit
I - 7 A - 3
(1s) Send A-STN category
Transition to B signal
II - 1
(No-priority B - 6
STN) Station free
The arrow diagram illustrated here shows the exchange of signals for a
successful connection set-up to free station 517.
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
39.1.3 The Meaning of the MFC-R2 Signals According

to UIT Q.441
The following table lists the meanings of the forward (Groups I and II) signals and
the backward (Groups A and B) signals. This table is a compilation of the CCITT
tables 6 to 9/Q.441.
Sign Group I Group II Group A Group B

al
1 Digit 1 STN without Send next digit (n+1) Spare for national
priority use
2 Digit 2 Subscriber with Send last but one Station number
priority digit (n-1) modified
3 Digit 3 Maintenance End-of-dial Station busy
equipment Reception of B signal
4 Digit 4 Spare Congestion Congestion
5 Digit 5 Operator Send calling party’s Port not configured
category
6 Digit 6 Data transmission End-of-dial, set-up Station free with
(national) speech condition call charges
(with call charges)
7 Digit 7 STN or AC without Send last but two Station free
forward transfer digit (n-2) without call
capability charges
8 Digit 8 Data transmission Send last but three Station faulty
(international) digit (n-3)
9 Digit 9 Priority STN Spare for national Spare for national
(international) use use
10 Digit 10 Operator with Spare for national Spare for national
forward transfer use use
capability
11 Access to Spare for national Send country code Spare for national
incoming use use
operator (Code
11)
12 a) Access to Spare for national Send language or Spare for national
delay operator use discriminating digit use
(Code 12)
b) Request not
accepted
13 a) Access to test Spare for national Send type of Spare for national
equipment use international R2 use
b) Satellite link register
not included
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
Hardware
Sign Group I Group II Group A Group B

al
14 a) Incoming half- Spare for national Is an incoming half- Spare for national
echo suppressor use echo suppressor use
required necessary?
b) Satellite link
included
15 a) End of pulsing Spare for national Internationally Spare for national
b) End of use congested use
identification
39.1.4 MFC-R2 Signals and MFCTA

The MFC tables control the signal exchange and the meaning of the forward and
backward signals (physical-logical and reverse). Administer these with the AMO
MFCTA.
You can see in the table that signals have been kept free for national use. Each
country or provider uses these as needed. The terminal exchange often requires
the A number (ANI;identification) from the originating exchange.
An SIU-X helps with the exchange of MFC signals.
39.2 Hardware
39.2.1 Circuits
MFC register signaling is possible for all devices (line circuit modules) that work
with the DH-Länder (DS120). These can be both analog and digital circuits with
CAS. Configure the "MFC-R2 Line Signalling digital version" described by CCITT
Q.421 with the device (DEV=DIUCQ421).
Configuration example TACSU:

05,COTNO=222,COPNO=222,COS=220,LCOSV=1,LCOSD=1,TGRP=222,CCT="A-
ANALOG MFC",NNO=1-1-
101,INS=Y,DEVTYPE=TC,DEV=DIUCQ421,MFCVAR=2,CIRCIDX=22,DIALTYPE=M
FC-MFC;
39.2.2 SIU for MFC-R2

Depending on the configuration, you can set up a maximum of 8 MFC-R2 signal
receivers and MFC signal transmitters on this. These always operate in pairs and
the configuration is also always in pairs.
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
General Information on the MFC Tables
Because the signaling described in the preceding is based on the signal offer,
more configurations are needed for outgoing traffic than for incoming traffic (in the
example there are 2 incoming (backward) and 6 outgoing (forward)
configurations):
ADD-BCSU:SIUP,1,2,49,"Q2233-X
",R2B&R2B&R2F&R2F&R2F&R2F&R2F&R2F,"0",3;
A virtual SIUX board provides MFC-R2 functionality for OpenScape 4000
SoftGate/OpenScape Access. The configuration for a virtual SIUX, for example,
is
ADD-BCSU:MTYPE=SIUP,LTG=1,LTU=42,SLOT=10,PARTNO="Q2187-X
",MFCTYPE=R2B&R2B&R2F&R2F&R2F&R2F&R2F&R2F,LWVAR=0,FCTID=3;
For detailed information, refer to the "OpenScape Access” service
documentation.
39.2.3 Trunk - SIU Connection

As the general description clearly indicates, there must be an MFX-R2
transmitter/receiver pair assigned to a trunk during the exchange of signals. The
configuration in TACSU is responsible for the correct connection: MFCVAR=x,
DIALTYPE=MFC-MFC.
MFCVAR in this AMO corresponds to the MFCVAR in the AMO MFCTA

(described later).
39.3 General Information on the MFC Tables

The OpenScape 4000 hard disk meanwhile has MFC tables for many countries
and applications. You must modify these for the individual application. This is
possible at any time. If you make the same modifications over and over, it would
be useful to report this so that the base initialization can be adjusted. Display the
list as follows:
DISPLAY-MFCTA: MFCVAR=1,TYPE=HD;
IMPORTANT: You can use Table 25 (CCITT Standard) as the generally valid
base configuration. Configure SOCOTEL signaling with Table 3 and IBERCOM
signaling with Table 4 or 10.
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
39.3.1 Identification With Master Number (Outgoing

Seizure)
Instead of the station number, the master number is sent to the remote central
office if:
• the station is blocked for direct inward dialing,
• the number is identified as ’Presentation restricted’ (for example, a secret

calling number),
• the A number is not available (for example, because of an analog network

interface),
• the A number is identified as inadmissible (screening indicator: Screened but

failed),
• the attendant console sets up the connection (does not apply to seizure of the
line with the P aggregate).
You must configure the master number in MFCTA. If you have not configured a
calling number, the central office acknowledges the A number request with the ID
contents.
• Configure the master number as follows:

CHANGE-MFCTA:MFCVAR=x,TYPE=TBLF,OPT=FIDENT,BSDIRNO=master-
number;
CHANGE-MFCTA:MFCVAR=x,TYPE=TBLF,OPT=FIDENT,BSDIRCNT=number-
of-digits-in-master-number;
39.3.1.1 A Number Identification Examples (Generated,

Outgoing Seizure)
To guarantee proper identification with MFC-R2 (ANI), you must enter a master
number in the AMO MFCTA. Because the provided country tables apply for a
country in general, you must configure them for each MFC type a system uses.
Here are a few application examples to illustrate the existing ANI capabilities:
• Example 1: ANI with master number for station as described above or

extended with PABXID for the other stations ("normal" application)
Internal calling number: 5017 (4-digit)
• ANI block (station) sent to central office: 0585 585 017F
• ANI block (master number) sent to central office:0585 585 585F

+----------------------------------------------------+
| MFCVAR: 1 MFCVARI: 1 TYPE=TBLF OPT=FIDENT |
+----------------------------------------------------+
| |
| |
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
| ID: F CNT: 1 |
| |
| PABXID : 058558 PCNT: 6 |
| |
| POS1: 0 POS2: 0 POS3: 0 POS4: 0 |
| |
| ANBEG: 0 ANEND: 0 APOS: 0 |
| |
| BSDIRNO: 0585585585 BSDIRCNT: 10 |
| |
+----------------------------------------------------+
• Example 2: ANI with master number for all stations

Internal station number: 5017 (4-digit)
• ANI block (master number) sent to central office: 01 495 3111F

+----------------------------------------------------+
| MFCVAR: 1 MFCVARI: 1 TYPE=TBLF OPT=VIDENT |
+----------------------------------------------------+
| |
| |
| ID: F CNT: 1 |
| |
| PABXID : 014953111 PCNT: 9 |
| |
| POS1: 9 POS2: 0 POS3: 0 POS4: 0 |
| |
| |
| |
+----------------------------------------------------+
• Example 3: ANI with master number (like in example 1) and modification of

the highest-valued digit for other stations
Internal station number: 5017 (4-digit), central office station number: 01 495
9017
• ANI block (master number) sent to central office: 01 495 9111F

+----------------------------------------------------+
| MFCVAR: 1 MFCVARI: 1 TYPE=TBLF OPT=FIDENT |
+----------------------------------------------------+
| |
| |
| ID: F CNT: 1 |
| |
| PABXID : 014959 PCNT: 6 |
| |
| POS1: 0 POS2: 0 POS3: 0 POS4: 0 |
| |
| |
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
| |
+----------------------------------------------------+
39.3.2 Counter When Retrieving the A-Number

(Terminating Seizure)
There are countries that acknowledge each A-5 with the II signal (category). But
it is assumed that the 1st A-5 acknowledges with the station category and that
other A-5s acknowledge with the A number. To prevent endless loops in this
(incorrect) case (identification sent with A-5 to I-15), you should limit the number
of A-5s that are sent.
• Change the MFC table (MFCTA) as follows:

CHANGE-MFCTA:MFCVAR=x,TYPE=MFCVAR,OPT=SUPERV,MAXDGTS=15;
IMPORTANT: If you set MAXDGTS=0, there is no monitoring of the digit signals

during identification. The number of signals is not explicitly monitored during a
generated seizure. Therefore you must configure the table correctly (see above).
39.3.3 Identification With MFC-R2 (General)

The identification sequence according to PTT Basic Requirement 692.97 Issue
VII.D was implemented for Switzerland. The A station retrieved by the central
office is displayed on the digital station device if you have configured the
appropriate classes of service.
Because the identification sequence increases the length of the seizure of the
MFC equipment in the central office and in OpenScape 4000, you should only
equip a few TVAs with the identification feature according to Section 5.4 of the
mentioned PTT basic requirement. Therefore you should arrange the
identification configuration in a system with the PTT.
This statement also basically applies to other countries.
The identification (A number) can be retrieved before and after the B number is
received.
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
39.3.3.1 Generation Notes on A Station Identification (Before

the B Number)
In this application, identification is performed on each incoming call. The

advantage of this method is that the dangerous time between the "preliminary
seizure" of the B station and ringing is short. The disadvantage of this method is
that the SIU MFC devices for both the OpenScape 4000 and in the central office
remain seized (considerably) longer for each seizure.
You should perform the following generations using MFCTA (MFC parameter:
IDBEFBS) and FEASU so that the central office retrieves the A station number:
FEASU: TRACCO = YES
CHANGE-MFCTA:MFCVAR=x,TYPE=MFCVAR,OPT=MISC,PAR=IDBEFBS;
IMPORTANT: In a concrete case, you must repeat and chain all parameters that
have already been set with ’&’. The above example only sets the parameter
IDBEFBS.
39.3.3.2 Generation Notes on A Station Identification (After the

B Number)
In this method, the A number is only retrieved if the reached station is correctly
administered. The advantage is that calls do not use the SIU MFC devices longer
than necessary. The disadvantage is that the time between "preliminary seizure"
and ringing is considerably longer. If the B station picks up during this time, the
call is signaled to the central office with "FREE" but the busy tone is applied.
To make sure that the A station number is retrieved from the central office,
perform the following generations with COT, COSSU, and FEASU:
Identification without allowing the tracing expression:

COSSU: Station COS with TSUID for retrieval of the A number when there is
a call to the station.
COT: ATDI for retrieval of the A number when there is a call to the AC (call
queue).
COT: TIEI for retrieval of the A number when there is a call via DAR TIE.
FEASU: TRACCO = YES
Identification while allowing the tracing expression:

COSSU: Station COS with TSUID and FANGAUT (if there is automatic
tracing)
FEASU: TRACCO = YES
WABE: Digital analysis result TRACE (for manual tracing)
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
39.3.4 Use Identified Calling Number for Redial

The Swiss PTT network does not send the so-called network access digit (0)
during identification (example: 14954444, 17491212, 216318888 or 31650333,
where the remote code is shown in bold).
The feature has been extended so that the identified station number is
supplemented according to the following rule:
- Starting digit sequence <> "xy" supplement calling number with "uw" (31650333
-> 0 031 650 333).
- Starting digit sequence = "xy" remove this digit sequence; supplement with "u"
(14954444 -> 0 4954444)
Configure the remote code (starting digit sequence "xy"), the network access digit
("w"), and the trunk group code (breakout to central office "u") in the AMO
MFCTA.
Example for network group 01 and trunk group code to central office 0: Display
for 14954444: 04954444 / Display for 31650333: 0031650333:
CHANGE-MFCTA:MFCVAR=1,TYPE=MFCVAR,OPT=MISC,EXACFI=0;
CHLCLTR=1, TRDISDI=0;
Example for network group 21 and trunk group code to central office 9: Display
for 216318888: 96318888 / Display for 31650333: 9031650333:
CHANGE-MFCTA: MFCVAR=1, TYPE=MFCVAR, OPT=MISC, EXACFI=9;

CHLCLTR=21, TRDISDI=0;
You can also use the above examples for other countries. You should also keep
in mind the calling number modifications in the OpenScape 4000.
39.3.5 Acknowledged Identification Request

(HUNGARY)
When there is an identification request (Hungary) with MFC-R2, first a signal is
received that indicates whether the identification is valid or possible
(acknowledge). This signal should not be sent on to the CP.
• Load the MFC Table 15 for Hungary (central office) with the following AMO
command on MFC version x. The tables already have the correct basic
initialization, so that the following MFCTA command to assign the parameters
is not necessary.
COPY-MFCTA: 15, x;
• You can control the feature described above with the MFC parameter
CHKIDDGT:
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
CHANGE-MFCTA: MFCVAR=x, TYPE=MFCVAR, OPT=MISC, PAR=CHKIDDGT.
IMPORTANT: In a concrete case, you must repeat and chain all parameters that
have already been set with ’&’. The above example only sets the parameter
CHKIDDGT.
39.3.6 Handling the Signals in Generated

Connections
Use the table (TYPE=TBLF,OPT=DIALOUT) in MFCTA to assign the dialed digits
to any MFC signals that you choose. This table converts the dialed 0 to the MFC
signal 10. This installation of this table is correct for most applications. It assigns
all characters of a 16-key keyboard to an MFC signal.
• Changing the MFC tables to assign the MFC signal I-15 to the digit # (11).
CHANGE-MFCTA: MFCVAR=x, TYPE=TBLF, OPT=DIALOUT, PHYSIG=11,
SIGNAL=15, INFO=END;
39.3.7 Note on Message F5607 MFC-MONITORING

This (error) message contains various information:
Example for message F5607:

F5607 M4 N0203 NO ACT BPA CIRCUIT MFC MONITORING
03-01-16 11:42:58
ALARM CLASS:SWU-PER:013/000/001
P102:LTG1 :LTU2 :037: 38 : 0 Q2196-X DIU-N2/2
BST:01 PLS:-03
FORMAT:22 DEVICE NAME: DIUCQ421
402C0100100000000000010100000000
00000000000000000000000000000000
00000002010101050000000000000000
000000000000000000000000B5050000
15FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF
Interpretation of the message contents:
1st line:
402C0200100000008000010100010000
00000000000000000000000000000000
aabbccddeeeeeeeeeeeeffgghhiiiiii
iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
2nd line
00000001000001000000000000000000
000000000000000000000000B8000000
iiiiiijjkkllmmmmmmmmmmmmmmmmmmmm
mmmmmmmmmmmmmmmmmmmmmmmmnnnnnnnn
3rd line
0EFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
ooxxxxxxxxxxxxxxx
aa Message length H'40 = 64 relevant bytes

bb Message code = DB_QF_E_CIR_MFC_UEBERW = MFC-Monitoring
cc Situation (see below) here: 01 = No first signal
dd Pending frequencies on the SIU (only for SIU developers)
ee MFC attribute (only for DH developers)
ff Forward signal input counter
gg Forward signal output counter
hh Forward signal retrieval pointer (not important)
ii Forward signal
jj Backward signal input counter
kk Backward signal output counter
ll Backward signal retrieval pointer
mm Backward signal
nn Device address of the connected SIU type 3
oo DH status
xx Data that is no longer important
The situation is stored in the 3rd byte (in this case 02). The following values are
possible:
00 no SIU found
01 No first signal
02 No further signal
03 Pending signal does not deactivate
04 No control frequency (SOCOTEL/IBERCOM)
05 Control frequency does not deactivate
06 SIU does not answer message (request for pending frequencies)
07 Signal that is not allowed (NOPO in table
08 Forward signal not acknowledged (generated connection)
09 Forward signal not acknowledged (generated connection)
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
0A COE error. Line has incorrect or missing class of externals assigned.

The F5607 with situation 0A is also used for trunks without MFC-Table
0B Implausible MFC signal start
0C Implausible MFC signal end
0D Implausible timer
0E Test call 1
0F Test call 2
10 Other situation (not assigned)
11 Test call 3
12 No SIU request message (MFRP)
13 Invalid SIU frequency (MFRP)
14 Unexpected 1st frequency (MFRP)
15 Incorrect program progress (MFRP)
16 Congestion signal (MFRP)
17 Long timer responds (terminating connection MFRP)
18 Long timer responds (generated connection MFRP)
19 Error during MFRP generated connection
1A Codogram (not sended by ANIF / no receiver by ANIB)
1B Error during MFRP generated connection
1C Error during MFRP generated connection (not allowed parameter
combination)
1D Error during MFRP generated connection (no attribute set)
1E Error during MFRP generated connection (unlogical parameters, attribute)
1F end to end signalling
20 link-by-link Signalling (see )
39.3.7.1 F5607 MFC-MONITORING for all terminating

connections
You can set the parameter MFCMO in MFCTA. The parameter NOMFCMO must
not be set. With this combination of the parameters, each terminating connections
generates a F5607 MFC-MONITORING.
This is implemented for tesing cases. Here two examples:

03-01-16 08:50:29
P102:LTG1 :LTU2 :037: 37 : 0 Q2196-X DIU-N2/2
BST:01 PLS:-03
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
402C2000C100020000000F0F00000301
050202030205070F0405070100000000
0000000F020101050505050505050505
010101030600000000000000B4050000
FFFFFFFFFF

03-01-16 11:11:35
P102:LTG1 :LTU2 :037: 38 : 0 Q2196-X DIU-N2/2
BST:01 PLS:-03
402C20008100020000000F0F00000301
050202030205070F0406020100000000
0000000F020101050505050505050505
010101030500000000000000B5050000
FFFFFFFFFF
Interpretation of example one:
The decribed rules of the chapter above are valid. The ii-part shows the signals
received from the originating register. The mm-part shows the signals send to the
originating register.
ii: 03 01 05 02 02 03 02 05 07 0F 04 05 07 01
mm: 05 05 05 05 05 05 05 05 05 01 01 01 03 06
You see the signals by using ANI before the tranmission of the B-number. For ANI
is the A-5 used. Fisrt A-5 ask calling partys category.
A-Number: 5223257F; B-Number: 3457; calling partys category: II-1
The called party is free (B-6)
The second example shows nearly the same, but the called party (3462) is out of
service (B-5).
39.3.8 Monitoring the MFC Signal Exchange

You can configure the monitoring timers in the branch TYPE=MFCVAR,
OPT=TIME. To monitor from the signal start of the current digit to the signal start
of the next digit, you must set the timers NXTSIG = 0 and RMVSIG > 0. If you set
both values to 0, there is no monitoring. If you set both timers to a value > 0,
NXTSIG waits for the next signal and RMVSIG waits until the remote exchange
overrides the signal. Use STADIAL for applying the first signal from the remote
central office.
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
If an MFC monitoring timer responds, the system generates an MFC-

MONITORING message and ends the signal exchange with IMP (corresponding
pulse signal from the MFC table TYPE=MFCVAR,OPT=MISC).
39.3.9 Dialing Monitoring Combined With Intercept to

Attendant Console
MFC-R2 signaling allows you to send selected signals as pulses. You can
configure two signals (MFCTA). The IMP signal (usually A-4) is sent as a pulse
when the call encounters busy (no intercept) after the monitoring response (see
above). The signal IMP2 (usually A-6) is sent as a pulse when the call encounters
a free indication after the monitoring response. This case occurs when the call
was intercepted to the attendant console.
• Change the MFC table (MFCTA) as follows:

CHANGE-MFCTA: MFCVAR=x, TYPE=MFCVAR, OPT=MISC, IMP=4;
CHANGE-MFCTA: MFCVAR=x, TYPE=MFCVAR, OPT=SUPERV, IMP2=6;
39.3.10 Tracing End-of-Dial Without Charges

In some countries (such as Brazil), it should be possible to trace an MFC end-of-
dial without charges. (Extension of the possible B signals when calling an
available user.)
If a user has both the trace class of service and the ’without taxation’ class of
service, use MFCTA as follows:
CHANGE-MFCTA: MFCVAR=x, TYPE=TBLB, OPT=BSIGB, EODTYPE=MCIDFC,
BSIG=7;
39.3.11 END TO END Connections

In end-to-end signal transmissions, the transit register and destination register
correspond only to the originating register. Enough information is retrieved from
the origin to allow the through-connection. In particular, the number of the B
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
station is transmitted only once. This means that the connection set-up is faster
than with a link-by-link transmission. The feature is only effective in transit
systems but does not have to be administered throughout the network.
IMPORTANT: If you do not administer the END TO END feature, LINK BY LINK
is set up. As a rule, the following applies: transmission is LINK BY LINK if the
configuration is incorrect.
CorNet links are inserted into the connection transparently and do not interfere
with the END TO END set up.
Identification is possible only after the B station has been reached and depends
on the classes of service there.
Example:
dialed number: 416-761-2100
ETE ETE
ETE1 ETE1 AMO COT
Node A Node B Node C Stn:2100
ETENORSP ETEMIN1 AMO LDAT
DPLN: 416-xxx 761-xx -----

Signal exchange 761-21
until DPLN met in B A2 (n-1) AMO MFCTA
2100
39.3.12 Configuration Notes

The data refers to an existing configuration with MFC or CorNet circuits on DIUC
modules. Digit analysis results for tie or trunk calls are available, as are the
numbering plans for the path selection. Activate the feature with the AMO COT.
An END TO END connection is made when the ETE classes of the incoming and
outgoing circuit are compatible, which means that both belong to the same ETE
class and the signal exchange has been adapted to the existing numbering plan.
CHANGE-COT:210,COTADD,ETE&ETE1
IMPORTANT: If you have not set ETE on the incoming circuit, link by link is set
up, but you can use the circuit for outgoing ETE if you have only set ETE1. You
can assign more than one ETE class.
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
CHANGE-MFCTA:1,TBLB,BSIGA,2,ETEMIN1,END
CHANGE-MFCTA:1,TBLF,BSIGA,2,MIN1
IMPORTANT: MFC version and backward signaling depend on the country.

ETEMIN1 or MIN1 are values for the BSIG and its interpretation for the ETEMIN1
end-of-dial (B station starting with the next to last digit)
CHANGE-LDAT:401,ALL,1,,401,10,1,,1,EMPTY,ETEMIN1,,NONE,1,4
IMPORTANT: You are only allowed to set one end-of-dial attribute. This
depends on the numbering plan that is configured in the network.
ETEMIN1 means that the B-station is requested starting with the next to last digit.
CHANGE-COP:XX,COPADD,STNI
IMPORTANT: Set the COP if you want to use an incoming circuit for identification
for both types of set ups.
39.3.13 New User Categories for Private Networks

(With MFC Signaling)
The new service for private networks from Ibercom allows users of distributed
systems in a private network to communicate with one another under special
conditions (charges) via the Ibercom network. Special MFC signals (group II) are
used for ’private calls’ (local, national, international).
Assign the category (or the II signal) with MFCTA. Define the class of service with
COSSU. Use the LCR outdial rules to assign this COS (or COEX) to the dialed
digits (local, national, or international).
• Load MFC Table 10 for Spain (IBERCOM 2 of 6) with the following AMO
commands on MFC version x. The tables already have the correct basic
initialization, so that the following MFCTA commands to assign the category
are not necessary:
COPY-MFCTA: 10, x;
• Assign the II signal (physical) to the category (logical) as follows:
CHANGE-MFCTA: MFCVAR=x, TYPE=TBLF, OPT=VFGR2, FSIG2=LOCCLPR,
CATEGORY=12, PHYSIG=11, IDX=3;
CHANGE-MFCTA: MFCVAR=x, TYPE=TBLF, OPT=VFGR2, FSIG2=NATCLPR,
CATEGORY=14, PHYSIG=13, IDX=3;
CHANGE-MFCTA: MFCVAR=x, TYPE=TBLF, OPT=VFGR2, FSIG2=INATCLPR,
CATEGORY=15, PHYSIG=6, IDX=0;
• Assign the COS parameter as follows:
A31003-H3170-S103-6-7620, 02/2019
mfcr2b_en.fm
MFC-R2 Signaling
CHANGE-COSSU:TYPE=COS,COS=x,AVCE=LOCC;
CHANGE-COSSU:TYPE=COS,COS=y,AVCE=TOLLPV;
CHANGE-COSSU:TYPE=COS,COS=z,AVCE=INATC;
39.3.14 Using the ITR (Internal Traffic Restriction

Group) With MFC-R2
The MFC table is modified for the special networks of Hungary. This assigns an
ITR to the Group II signal. Using the AMO VBZ, you can configure the appropriate
restrictions. You can use this feature everywhere that you use MFC-R2. Because
the ITR is transmitted in a OpenScape 4000/HiPath 4000 network, this feature is
valid throughout the network.
Use the column "ADINFO" in the table TYPE=TBLB,OPT=FORIA (AMO MFCTA).

This column is initialized to 0 for each pending signal. This guarantees that the
new feature is normally not active. This value is also initialized in the AMO TACSU
to ITR.
Configuration example for assigning ITR 5 to signal II-5 (mediator):

CHANGE-MFCTA: MFCVAR=x, TYPE=TBLB, OPT=FORIA, PHYSIG=5,
ADINFO=5;
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
Feature Description
40 National ISDN Basic Rate Interface (NI BRI)

The customer, as the end user, can access the OpenScape 4000 switching
system with this feature by using the protocol and the procedures defined by
Telcordia Technologies (previously Bellcore) for the NI BRI. Thus end users can
initialize ISDN configurations and set up and release system-internal ISDN
connections and ISDN users can communicate with existing networks.
Usually US customers use the NI BRI connection in the OpenScape 4000 as a

LAN bridge for teleworking and for connecting ISDN equipment that can then be
used for communication along with the devices connected (for example, analog
telephones, fax devices (see list of supported devices in FDB2-3 for NI BRI, V1.0,
Appendix B). Only those NI BRI functions that are needed to support this
customer requirement have been implemented.
40.2 User Interface

You must enter the SPID value (Service Profile Identifier) in the following format
to initialize the station device:
<DN>01
DN ... via the user defined on the current S0 port with the AMO SBCSU.
Example:
• Using DN configured on AMO SBCSU: 3188
• Using the SPID to be entered via the ISDN user interface 318801
40.3.1 Connecting NI BRI Data Devices via the SLMQ3

Card
The SLMQ3 trunk card provides the physical two-wire interface U2B1Q, controls
the connection in the D channel on the data link layer (LAPD), and transports the
Layer 3 signaling information between the NI BRI data device and the
OpenScape 4000 system. One SLMQ3 connection can support a maximum of 8
devices. This includes analog devices that are possibly connected behind the
data devices with U or S interfaces.
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
Service Information
OpenScape 4000 supports NI BRI devices on a SLMQ3 port as follows:
a) Maximum of one data device with U interface that is directly connected

with an SLMQ3 port.
b) Maximum of eight data devices with S interface, which are in turn

connected with one non-company-specific NT1 device that is connected
to an SLMQ3 port.
c) Up to seven data devices with S interface that are connected with a

"passive S interface bus adapter", which in turn is connected to a non-
company-specific data device that has a U interface and that is on an
SLMQ3 port.
It is not possible to connect both NI BRI and DSS1 equipment to a BRI at the
same time.
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
Service Information
SLMQ3
NI
U2B1Q data device
a) with U
interface
U2B1Q Passive S interface bus

NT-1
b)
NI Max. 8 NI
data device 1 devices data device 8
with S with with S
interface S interface interface
U2B1Q NI
c) device
with
U interf.
S bus Passive S interface bus

adapter
NI NI
data device 1 (1-7 data device 7
with S devices) with S
interface interface
40.3.2 Connecting NI BRI Date Devices via the SLMO

Card
OpenScape 4000 supports the connection of NI BRI data devices both via the
ISDN terminal adapter (known as TA S0) in an optiPoint telephone and via the
USB port of an optiPoint telephone.
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
Service Information
The TA S0 is the NT1 reference point; the connected NI BRI data devices can
access the B and D channels of an SLMO port via the TA S0. Included in the NI
BRI data devices supported over this interface are Group 4 fax devices and data
station devices. These have their own power supplies.
The TA S0 module performs the Layer 1 interworking between the NI BRI data
device with S interface and the UP0/E transmission code to the SLMO card. The
Layer 2 and 3 signaling information is transparently transported between the NI
BRI data device and the OpenScape 4000 system.
The TA S0 is supported in optiPoint telephones. With the optiPoint telephones,

OpenScape 4000 also supports a 2B + D interface, which is provided via the
ISDN application on a PC that is connected to the optiPoint telephone USB port.
40.3.2.1 Restrictions With the TA S0 Configuration
You must install at least one TA S0 in the optiset E/optiPoint master telephone. In
this case, you can connect a maximum of two NI BRI data devices with S interface
to the TA. As an exception to the "3-device rule" that applies to the SLMO card,
you can also configure an analog device (for example, a telephone or fax device)
on each of the NI BRI data devices with S interface. If you install a TA t/r (analog
adapter) in addition to the TA S0 in the optiPoint master telephone, you can
connect only one NI BRI data device with S interface to the TA.
IMPORTANT: You cannot install the TA 232 in the optiPoint!
40.3.2.2 General Configuration Restrictions
1. A SLMO port can support a maximum of three devices. This is known as the
"3-device rule".
2. You cannot connect both NI BRI and DSS1 equipment to a BRI port at the
same time.
40.3.2.3 Connecting NI BRI Data Devices via the optiPoint

Telephone
OpenScape 4000 supports the connection of NI BRI applications and data

devices via an OptiPoint telephone as follows:
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
Service Information
a) A 2B + D interface that is provided by an ISDN application in a PC, which

in turn is connected to the USB port of an OptiPoint telephone; see FDBs
for the feature ID 5073 for information on NI BRI support via the USB
interface: API (TAPI / CAPI) for OptiPoint telephone.
b) Maximum of two NI BRI data devices with S interface. As an exception to

the SLMO card "3-device rule", an additional analog device (for example,
a telephone or fax device) on each NI BRI data device that is connected
to the TA S0 terminal adapter in an OptiPoint telephone in which no other
TAs are installed.
c) An NI BRI data device with S interface that is connected to an TA S0

terminal adapter in an OptiPoint telephone in which a TA t/r terminal
adapter is also installed.
SLMO
UP0/E optiPoint USB
a) phone port PC with ISDN
application*
*See feature ID 5073: API (TAPI / CAPI)

for optiPoint telephone
UP0/E optiPoint
b) phone S0 interface
with
TA S0
NI Max. 2 NI
data device1 devices data device 2
with S interf. with with S interf.
S interface
UP0/E
c) optiPoint-
Analog
phone device
with
TA t/r
and NI
TA S0 data device 1
with S interf.
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
Service Information
40.3.3 NI BRI Partner Products Supported by

OpenScape 4000
Device Interface
NT1 network terminators
Motorola NT1D
Adtran NT1ACE
Alpha Telecom UT620
Alpha Telecom UT812 built-in version
TA ISDN terminal adapter
Motorola BitSURFR U interface
Zyxel ISDN modem S/T or U interface
Cardinal - IDC 100i (PC card) U interface
Diamond - Supra Net Commander (PC card) U interface
3Com Impact IQ U interface
US Robotics Courier Modem U interface
LAN Bridge / Router
Cisco 1604U Router U interface
ACC Congo Router U interface
Ascend MAX1800 Router U interface
(supports 8 BRI ports)
Lan Rover E Plus Shiva Router S/T interface
(supports 4 BRI ports)
Ascend Pipeline 400 S/T interface
Ascend Pipeline 50 S/T interface
Gandalf 5242I U interface
Cisco 766 S/T interface
Cisco 201 S/T interface
Cisco 4500 (BRI) S/T interface
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
Device Interface
Video systems
Adtran ISU 512 U interface
PictureTel PCS100 Desktop
PictureTel Venue 2000 Desktop
PictureTel Concord 4500 Group Video
PolyCom ViaVideo View Station Group Video
Proshare Video System Group Video
Modems
US Robotics 56k Sportster
(external with X2 technology)
33.6 Cardinal Modem Model 2460 (external)
40.4.1 First-Time Loading of the NI BRI Protocol Data

The protocol for the NI BRI interface must be on the hard disk before you
configure the system.
• Check whether the NI BRI protocol data has already been loaded from the
hard disk.
DISPLAY-PRODE:SRC=DB,KIND=PDSHORT;
If the NI BRI protocol is already available, the following entry appears in the
column under PDSTRING:
"S0-BUS NI-BRI GR-268-CORE"
If the column is empty, you can supply the protocol with one of the two
following methods:
1. Load only the missing portion of the NI BRI protocol data.

2. Load a collection of all US-specific protocol data at the same time (among
the data is the NI BRI protocol).
For method (1) above, simply load the missing NI BRI protocol data
separately in the above DISPLAY-PRODE output. Determine the first
available index PDxy (column PDNAME) without a PDSTRING description.
This is the index where the NI BRI protocol data can be loaded.
In this example, PDNAME=PD11.
• In the next step, determine the PDNO index used to store the original NI BRI
protocol data.
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
DISPLAY-PRODE:SRC=HD,KIND=PDSHORT;
In this example, PDNO=41
• Now you can load the NI BRI protocol data from the hard disk in DB ... */
COPY-PRODE:KIND=PD,PDNO=41,PDNAME=PD11;
• Release of the protocol for CP */
CHANGE-PRODE:KIND=PD,PDNAME=PD11,SEC=ORG,ACTIVE=Y;
To load all US-specific protocol data simultaneously with method (2),
determine the PVCDNO index used for storing the collection of US protocol
data on the hard disk.
DISPLAY-PRODE:SRC=HD,KIND=PVCDSHRT;
The overview display must contain a line with "UNITED STATES OF
AMERICA" (column DESCRIPTION).
In this example, PVCDNO=16 is the index for this line.
• Now you can load the US protocol collection from the hard disk in DB ... */
COPY-PRODE: KIND=PVCD, PVCDNO=16;
When you use this method, you do not have to release the new protocol data
for CP*/.
40.4.2 Connecting NI BRI Data Devices via the SLMQ3

Card
Example for configuring a subscriber with NI BRI data device
(connected with SLMQ3 port via PNT) in a PBX:
• If no SLMQ3 port is available (module not configured or no free ports)

ADD-BCSU:MTYPE=PER,(LTG=1,)LTU=5,SLOT=67,PARTNO="Q2479-X";
• Configure subscriber 3188 with NI BRI data device that is connected to the
SLMQ3 card via PNT.
ADD-SBCSU:SSTNO=3188,OPT=FBUS, CONN=PNT, PEN=1-5-67-0,
DVCFIG=SET600&DTE,COS1=5, COS2=6,LCOSV1=11, LCOSV2=12,
LCOSD1=21, LCOSD2=22, SPROT=SBNIBRI, DPROT=SBNIBRI,
SOPTIDX=7, DOPTIDX=7, BASICSVC=UDI64;
• Configure MSN 3189 on S0 bus 3188 */
NOTE: The NI BRI protocol set for the S0 bus 3188 is also automatically used
for all accompanying MSNs and can be changed only for the 3188.
ADDSBCSU:SSTNO=3189,OPT=MSN,MAINO=3188,BASICSVC=UDI64&UDI64;
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
40.4.3 Connecting NI BRI Data Devices via the SLMO

Card
Example for configuring a subscriber with an NI BRI data device (directly
connected to the SLMO port) in a PBX system:
• If no SLMO port is available (module not configured or no free ports)

ADD-BCSU:MTYPE=PER,(LTG=1,)LTU=5,SLOT=73,PARTNO="Q2158-X";
• Configure an Opti connection: optiset E-Master 3160 connected directly to
the SLMO */
ADD-SBCSU:SSTNO=3160,OPT=OPTI,CONN=DIR,PEN=1-5-73-
06,DVCFIG=OPTISET,COS1=5,COS2=6,LCOSV1=11,LCOSV2=12,LCOSD1=21
,LCOSD2=22;
• To extend this Opti connection: S0 bus 3168 with NI BRI data device
IMPORTANT: The system automatically configures the TA S0 that you must

install for connecting S0 devices in Optiset E-Master 3168.
ADDSBCSU:SSTNO=3168,OPT=OPTIEXP,MAINO=3160,DVCFIG=SET600&DTE,
COS1=5,COS2=6,LCOSV1=11,LCOSV2=12,LCOSD1=21,LCOSD2=22,SPROT=S
BNIBRI,DPROT=SBNIBRI,SOPTIDX=7,DOPTIDX=7,BASICSVC=UDI64;
• Configure MSN 3169 (with reference to the S0 bus 3168) for the Opti
connection.
IMPORTANT: The NI BRI protocol set for the S0 bus 3168 is also automati-
cally used for all accompanying MSNs and can be changed only for the 3168.
ADDSBCSU:SSTNO=3169,OPT=MSN,MAINO=3168,BASICSVC=UDI64&UDI64;
• Opti connection configuration: OptiPoint-Master 3170 and PC with ISDN
application connected directly to the SLMO.
IMPORTANT: The system automatically configures the USB adapter that is

needed for the PC connection and that is integrated in the OptiPoint-Master
3178.
ADD-SBCSU:SSTNO=3170,OPT=OPTI,CONN=DIR,PEN=1-5-73-07,
DVCFIG=OPTI500&DTE,COS1=5,COS2=6,LCOSV1=11,LCOSV2=12,
LCOSD1=21,LCOSD2=22,DPROT=SBNIBRI,DOPTIDX=7,BASICSVC=UDI64;
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
Relevant AMOs
40.5 Relevant AMOs

Language
BCSU SACHNR d baugruppensachnummer (2. und 3. block) :
= Q2479-X
zum Einrichten einer SLMQ3 Baugruppe
PARTNO e board/module number from part catalog :
= Q2479-X
to set up an SLMQ3 module
CTIME T400 d ueberwachungszeit der nationalen ISDN
bruecke
e timer for national ISDN bridge
DTIM1 TINT1 d ueberwachungszeit fuer die terminal
initialisierung
e control timer for terminal initialization procedure
PRODE PROTVAR d protokollvariante :
= SBNIBRI fuer NI BRI
e protocol variant :
= SBNIBRI for NI BRI
TIMERID d Identifikation des Timers :

= T408
e timer identification :
= T408
SBCSU BASICSVC d basic service voreinstellung fuer geraete
mit NI BRI prot. :
= AUDIO3K1 fuer 3.1khz audio
= SPRACHE
= UDI64 fuer 64kbps unrestricted digital
information
= UDI64RA fuer 64kbps unrestricted digital
information (rate adapted)
e basic service default value for devices
with NI BRI protocol :
= AUDIO3K1 for 3.1khz audio
= SPEECH
= UDI64 for 64kbps unrestricted digital
information
= UDI64RA for 64kbps unrestricted digital
information (rate adapted)
DOPT d index auf optionstabelle (amo zand) :
= 7 fuer NI BRI
DOPTIDX e index into option table for data device (dte) on s0
bus :
= 7 for NI BRI
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
Relevant AMOs

Language
DPROT d protokollvariante des funktionalen dee-
endgeraetes am s0-bus :
e protocol variant for data device (dte) on s0 bus :
FOPT d index auf optionstabelle (amo zand) :
= 7 fuer NI BRI
FOPTIDX e index into option table for facsimile device (fax)
on s0 bus :
= 7 for NI BRI
FPROT d protokollvariante des funktionalen fax-
endgeraetes am s0-bus :
e protocol variant for facsimile device (fax) on s0
bus :
SOPT d index auf optionstabelle (amo zand) :
= 7 fuer NI BRI
SOPTIDX e index into option table for voice/speech device
on s0 bus :
= 7 for NI BRI
SPROT d protokollvariante des funkt. sprach-endgeraetes
am s0-bus :
e protocol variant for voice/speech device on s0
bus :
A31003-H3170-S103-6-7620, 02/2019
ni_bri_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
netloop_en.fm
Network Loops
Feature Description
41 Network Loops

Network loops can occur as a result of faults in the network (e.g. failure of lines
or nodes) or as a result of traffic load congestion (busy trunk groups). They are
liable to occur in networks with both open and closed numbering schemes.
There are four methods by which network loops can be (largely) prevented or at
least limited.
41.2 Methods of Preventing Network Loops

1. Method: Prevention of network loops by checking for prohibited connections
in the node connecting matrix. Potential loops can be avoided right from the
network planning stage. 
For this purpose, specific connections are barred in a node connecting matrix
based on virtual originating/destination node numbers. This matrix, which is
initialized to permit all connections, is administered by AMO KNMAT. 
The check for prohibited connections is carried out in all nodes involved in a
connection. 
When applying this method, note the following carefully:
a) The traffic paths are restricted; this can adversely affect the load
distribution in the network.
b) Not all loops can be prevented.
c) CONN=D is set for all NPIs.
2. Method: Limitation of network loops with TRANSIT-COUNTER 

This counter prevents endless loops in the network. Threshold values are set
for incoming circuits or trunk groups in each node. In each transit node the
currently active counter in the network protocol is incremented and compared
with the threshold value. If the threshold value is reached, the connection is
cleared and an advisory issued. If nodes of variants up to and including Hicom
3000 V3.2 are involved in a connection, the TRANSIT-COUNTER information
is lost. In general, a connection (or several connections) cannot be set up if a
threshold value is set too low.
3. Method: Prevention of network loops by temporarily reducing classes of

service.
LCR classes of service can be reduced or removed using the AMO KNLCR
for combinations of virtual originating and destination nodes. This prevents
occupation of a specific LCR route or generally prevents further routing in this
network node for combinations of virtual originating and destination nodes.
A31003-H3170-S103-6-7620, 02/2019
netloop_en.fm
Network Loops
Service Information

• In each physical network an unambigous node number and an umambigous
code for the Route Optimization feature must be assigned by means of AMO
ZAND, parameters PNNO and PNODECD (Method 1).
• Each route must be assigned a virtual destination node number by means of

AMO RICHT, parameter NODENO (Method 1,3).
• Incoming digital circuits of nodes up to and including Hicom 300 V3.2 and
analog circuits must be assigned a fictitious virtual node number by means of
AMO TDCSU, AMO TACSU, parameter ORNDNO and activated via the COT
parameter DFNN/LWNC (Method 1,2).
• For incoming digital circuits of nodes up to and including Hicom 300 V3.2 a
class of trunk must be created with AMO COT, parameter COTPAR= LWNC,
and assigned to the circuits with AMO TDCSU, parameter COTNO (Method
1, 3).
• Incoming digital circuits must be assigned TRANSIT-COUNTER threshold

values by means of AMO TDCSU, parameter TRACOUT. 
The TRANSIT-COUNTER check must be activated by means of AMO COT,
parameter COTPAR=ATRS. This value is always applicable to all circuits in a
trunk group (Method 2).
• Incoming digital circuits of Hicom 300 V3.3 nodes must be assigned the value
CORNV33 or a an appropriate protocol in new variants such as QSIG, by
means of AMO TDCSU, parameter PROTVAR, in order to ensure
transmission of the node numbers in the network protocol (Method 1, 2, 3).
• If the default value is insufficient, the prevention function can be extended by

means of AMO DIMSU, parameter RSTCON (Method 1).
• The traffic restrictions of the node connecting matrix can be removed for the
attendant console (AC) by means of AMO ZAND, TYPE=ATND, parameter
ACCHECK (Method 1).

The node connecting matrix must be set individually in each network node
(Method 1). The examples show how loops can occur with the different types of
numbering and how they can be prevented by appropriate matrix setting.
A31003-H3170-S103-6-7620, 02/2019
netloop_en.fm
Network Loops
41.4.1 Network with Open Numbering; Alternate

Routing with Complete Set of Prefix Codes
Stn. A (4700) Stn. B
NODENO 1. TGRP NODENO NODENO NODENO

010 020 030 040
CD=91 2. TGRP CD=92 CD=93 CD=94
NODENO
050
CD=95
Stn. C
NODENO NODENO NODENO

100 060 070
CD=99 CD=96 CD=97
Figure 49 Alternate Routing with a set of Prefix Codes
Routes to node 040 are configured in NODENO 010:
• Route with route code 94 with first trunk group and PREFDGT1=9394
• Route with route code 94 with second trunk group and PREFDGT1=9794
(alternate routing trunk group)
Station A dials 944711;in NODENO 010 the dialing of 94 leads to DAR=TIE. 

A loop can be formed if, for example, both trunks to NODENO 040 develop a
malfunction or are overloaded, or if a failure occurs in node 040. An alternate
routing trunk group is then seized in NODENO 030, in this case via NODENO
050, 060 and 070. all number 9697944711 is transmitted on the trunk from
NODENO 030 to NODENO 050, since the alternate routing trunk group (route
code=94) is configured with PREFDGT1=969794. 
If the message is received at NODENO 070 (call number = 944711), it is
established that the direct trunk group for route code 94 is unavailable. The
alternative trunk group with PREFDGT1=9394 is seized on the trunk to NODENO
020. The loop, comprising the 5 nodes NODENO 030, 050, 060, 070 and 020, is
now closed. All available B channels are seized in turn. 
The loop can be prevented by restricting the permissible connections (AMO
KNMAT). In NODENO 050 all connetions from source node NODENO 010 to
A31003-H3170-S103-6-7620, 02/2019
netloop_en.fm
Network Loops
destination node NODENO 040 are prohibited. The configured routes (1st and
2nd trunk groups) can both still be used. Stations connected to other nodes (e.g.
station C, NODENO 100) can also use the transit route via NODENO 050.
• Example Method 1 - command in NODENO 050:

CHA-KNMAT:LEVEL=0,SNNO=10,DNNO=40,CONN=D;
• Example Method 3- command in NODENO 050:
ADD-KNLCR:SNNO=10,DNNO=40,REDSLCOS=1&&64;
41.4.2 Network with Open Numbering; Alternate

Routing with one Prefix Code
Stn. A (4700) Stn. B (4711)
NODENO 1. TGRP NODENO NODENO NODENO

010 020 030 040
CD=91 2. TGRP CD=92 CD=93 CD=94
NODENO
050
CD=95
Stn. C
NODENO NODENO NODENO

100 060 070
CD=99 CD=96 CD=97
Figure 50 Alternate Routing with one Prefix Code
In this case a single fault can produce a loop. The reason is that only the node
code of the destination node is supplied as the prefix code. In each transit node
the path to the next transit node in the direction of the destination is redefined. 
Routes to node 040 are configured in NODENO 010:
• Route with route code 94 with first trunk group and PREFDGT1=94
• Route with route code 94 with second trunk group and PREFDGT1=94
(alternate routing trunk group)
A31003-H3170-S103-6-7620, 02/2019
netloop_en.fm
Network Loops
Relevant AMOs
Station A dials 944711. In NODENO 010 the dialing of 94 again leads to

DAR=TIE. Call number 944711 is sent to NODENO 020, where route code 94 is
also assigned with PREFDGT1=94, with the result that call number 944711 is
transmitted to NODENO 030. Here a direct trunk group is configured for route
code 94 (no prefix). The number forwarded to NODENO 040 is thus 4711. 
With this configuration a loop may occur if, for example, the trunk from NODENO
030 to NODENO 040 has a fault. An alternative trunk group, e.g. via NODENO
050, is then used in NODENO 030. From here a trunk group can then be seized
in the direction of NODENO 030 or an alternative trunk group via NODEO 020. In
either case a loop is formed. This can be prevented by means of a prohibition
criterion in NODENO 050:
• Example Method 1 - command in NODENO 050:

CHA-KNMAT:LEVEL=0,SNNO=10,DNNO=40,CONN=D;
• Example Method 3- command in NODENO 050:
ADD-KNLCR:SNNO=10,DNNO=40,REDSLCOS=1&&64;
41.4.3 Network with Closed Numbering

In a network with closed numbering the node codes have no significance in the
path selection process. In each transit node a path to the destination is defined
with the aid of the digit analysis facilities (the destination is only defined by the
station number). Network loops are formed in the same way as for networks with
open numbering/alternate routing with one prefix code.
41.5 Relevant AMOs

Language
KNLCR UKNNR d Ursprungsknotennummer
SNNO e Source node number
DNNO e Destination node number
ERWLBER d Erweiterung der vorgegebenen LCR-
Berechtigung
ADDSLCOS e Add to LCR classmark subset
REDLBER d Reduzieren der vorgegebenen LCR-
Berechtigung
REDSLCOS e Reduce the LCR classmark subset
KNMAT UKNNR d Ursprungsknotennummer
ONNO e origin node-number
A31003-H3170-S103-6-7620, 02/2019
netloop_en.fm
Network Loops
Relevant AMOs

Language
EBENE d Ebene der Knotennummern
LEVEL e level of the node numbers
VBDG d Verbindung erlaubt / verboten
CONN e connection allowed / denied
PKNNR d ADreistufige Knotennummer zur
eindeutigen Identifikation des Knotens im Netz
PNNO e Node number (until 3 levels) for unambiguous
identification in network
PKNOTKZ d Kennzahl eigener Knoten
PNODECD e Physical node number.
TDCSU LAGE d Anschlusslage des Trunks: ltg-ltu-ebt-satz
PEN e Port Equipment Number: ltg-ltu-slot-cct
TRACOUNT d Transit-Counter. Standardwert: 31
TRACOUNT e Transit Counter. Default value: 31
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
General Description and Rules
42 Number Modification
42.1 General Description and Rules

With the format-dependent number modification the network configurator does
not have to worry about the source and target relationships for the PRIVATE and
ISDN numbering plans when configuring a OpenScape 4000/HiPath 4000
network for the first time, but can limit the configuration to the standard entries
(codes in AMO KNDEF and KNPRE settings).
Multiple levels of node numbers

Due to the multiple levels of the node numbers, modifications now can be made
at each level in a targeted manner. Through the introduction of the logical node
numbers (OWN,ROW=all nodes), the previously complicated AMO KNMAT
settings can be limited to a few, logically simple entries.
Virtual node numbers

Virtual node numbers are used to define the numbering plan data for subscribers
and thus are the basis for number modification. 
The fundamentals for physical and virtual node numbers are described in Chapter
22, “Basic Networking Principles”.
Physical node numbers

Physical node numbers have to differ from virtual ones since only the physical
ones can be used as a unique identifier for a PABX. Virtual nodes can be
distributed over several PABXs and thus not identify an individual PABX.
Nnumbering plans
• Several E.164/PNP numbering plan ranges/codes per physical node
This feature allows for example, a move while keeping the fully qualified
phone number (E.164 with local destination code, national code, international
code), which may make sense in a collocated system with several nodes (and
thus several CO numbers) in one location. Stations, however, must still
remain unique for each PABX. It is also possible to configure the phone
numbers 49 89 722 4711 and 49 89 636 4712 to one PABX, but not 49 89 722
4711 and 49 89 636 4711. This must be taken into consideration in case of
moves. If the subscriber 49 89 722 4711 is moving from node 1 to node 2, the
station number cannot be retained if a subscriber already has extension 4711
(**) e.g.: 49 89 636 4711) on node 2.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
This feature is also of interest for IPDA numbering plans.
IMPORTANT: For format-dependent number modification, only the

assignment of the subscriber to a virtual node = numbering plan range is
relevant! The assignment of the subscriber to a virtual node (AMO SDAT) and
the numbering plan data defined to this node (AMO KNDEF) is also relevant.
• Overlapping phone numbers:

Phone numbers (extensions) can overlap in the node code/local destination
code of the E.164 number/local code of the PNP number. 
This feature is used if the required number of public phone numbers is not
available in a consecutive range for a private network.
Provided that the private network requires 1800 CO numbers, but cannot
obtain any four-digit DID ranges from the public numbering plan (assigned or
too expensive). In this case, two three-digit DID ranges can be used, e.g. the
local destination codes 723 and 724 that result in CO numbers 723 xxx and
724 xxx. Since the internal phone numbers must be unique, however, the
three-digit numbers xxx may not be used as internal numbers. One solution
is a "double use" of the last digit of the local destination code as the first digit
of the internal number, the "overlapping". This results in four-digit internal
numbers ranging from 3000 to 4999, so more than enough.
None up to all of the digits of the local destination code/local code/node code
may overlap. The non-overlapping digits are the skip digits, that is, the digits
that have to be removed to form the internal number. The number of skip
digits must be configured (AMO KNDEF). The default here is "no
overlapping", all digits are skip digits.
In the example above, we have a three-digit local destination code and an
overlapping digit (Digit 3 or 4), the number of skip digits is thus two.
• Modification for external nodes:

If an OpenScape 4000 system networks with systems that do not have
number modification and, for example, that can send only extension numbers
as "calling numbers", the OpenScape 4000 can modify the external nodes.
The administration of the modification with E.164 or PNP codes has been
improved:
External nodes for which the OpenScape 4000 (in its place) should modified
are entered in the AMO KNDEF table under TYPE=EXTERNAL together with
their codes. Phone numbers supplied by these external nodes are thus
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
supplemented by the specified codes so that they appear delivered in the

correct format. After this external modification, they are subject to the
standard modification rules.
IMPORTANT: Standard partner nodes that supply valid numbers must not be
included in AMO KNDEF!
The standard assignment is one physical node = one virtual node. In order for
you to have to make as few changes as possible in the configuration of
partner nodes when upgrading a OpenScape 4000 node within a network, we
recommend using the original node number as the virtual node number and
defining a new node number for the physical node number. Partner nodes
must not change the configuration for routes (RICHT, LDAT) and number
modification (KNMAT, KNFOR).
42.1.1 Summary
Due to the great size of the number modification feature, the description is
preceded by a summary of the principles and rules.
The number modification has the task of modifying a phone number entered as
additional information ("calling number") in such a way that the dialing of this
number can always be interpreted by the system and a connection established to
the "calling number" at any time or place in the network.
There are two parallel methods for modifying the calling number:
Format-dependent number modification (AMO KNDEF, AMO KNPRE, AMO

KNFOR)
For this modification method, you must do the following:
• Set the exit codes and prefixes to your own node (IDSN or PRIVATE) using
AMO KNPRE.
• Set the codes (e.g. country code, area code, etc.) using AMO KNDEF.
• If destination nodes require certain formats, set them using AMO KNFOR
(TONOUT).
• If a special display format is desired at your own node, configure it using AMO
KNFOR (TONIN).
The most important rules:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
a) In each node that can be addressed with numbering plan NPI=ISDN or

NPI=PRIVATE, all prefixes and exit code should be set up for the possible
numbering plans using AMO KNPRE!
b) All required numbering plans should be defined in AMO KNDEF. In case

of CO lines, all E.164 entries are to be made here.
c) The node format table (AMO KNFOR) should always be set up when
external nodes require a certain format of the numbers or if the
subscribers require a certain display format on their own node. If the
KNFOR is not set up, the calling number will be by default displayed in the
highest format (e.g. TON=INTERNAT) when outgoing and to the lowest
possible format (e.g. TON=UNKNOWN) when incoming!
The source/destination-controlled modification (AMO KNMAT)
For this modification method, you must do the following:
• Using AMO KNMAT, set codes for certain source/destination combinations

(virtual nodes). These codes should either be abbreviated from the calling
number or placed before the calling number. If overlapping phone numbers
are used, only the skip digits of the code to be supplemented or abbreviated
should be entered.
The most important rules:
a) By default, only the logical node numbers OWN and ROW should be used
in AMO KNMAT for the UNKNOWN numbering plan. The following rule
applies here: in ONNOL=ROW to DNNOL=OWN, the own node code is
abbreviated when incoming and, in ONNOL=OWN to DNNOL=ROW, the
own node code is supplemented when outgoing. 
For the own node code, a new logical value can be used. Using an
"Supplement/abbreviate OWN with own node code of virtual code" entry
automatically performs an implementation for all virtual nodes and
extracts the code belonging to the virtual node from the AMO KNDEF
table.
b) By default, the AMO KNMAT should be used only for the UNKNOWN
numbering plan (NPI parameter). The NPI=ISDN and NPI=PRIVATE
numbering plans should be handled using format-dependent
modification!
c) When multi-level node numbers are used, the codes in AMO KNMAT
must be entered at the corresponding level; that is, a country code (e.g.
49) is always at Level 2, an area code (e.g. 89) is always at Level 1, and
a local destination code (e.g. 722) is always at Level 0.
d) Modification conditions (the MODCON parameter in AMO KNMAT) must

only be set for multi-level networks in levels 1 and 2.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
• For the ISDN or PRIVATE numbering plans, format-dependent number

modification should always be configured.
• For the UNKNOWN OpenScape 4000 numbering plan (i.e. the selection of tie
line codes), source/destination modification must continue to be configured.
• If configured, the source/destination-controlled modification always has

priority over format-dependent number modification during execution.
General rules, regardless of the selected method of number modification

Regardless of the selected method of number modification, there are a number
of general rules stemming from the introduction of the new ISDN and PRIVATE
numbering plans or from the expansion from the one-level to the three-level node
number.
The most important of the general rules are as follows:
a) If numbering plans not equal to NPI=UNKNOWN are used in a node,

each route element (AMO LDAT) is to be assigned the respective
numbering plan (NPI) and the type belonging to the destination number
(TON) in the corresponding outdial rule (AMO LODR).
b) Each node must be assigned a physical node number with AMO ZAND,
parameter PNNO, and at least one virtual node number with AMO
KNDEF. Each node number may be assigned only once in the network.
Node number 0 is not valid.
c) All OpenScape 4000/HiPath 4000 networks can continue to be operated

with one-level node numbers. If multiple levels are desired, however, the
node number ranges should be adapted to those of the phone numbers!
d) When multi-level node numbers are used, all node numbers must be kept
at the same level within the network! Even virtual and physical node
numbers must have the same level.
Special rules for various connections

To connect multi-level subnets to one-level subnets and to connect OpenScape
4000 systems to external systems, a number of special rules must be observed:
a) If, by way of exception, a multi-level subnet is connected to a subnet that

is not on the same level, the COT parameter LWNC (line without node
number) must be set in the respective set and a corresponding node
number must be entered for this system in RICHT as the destination
node. If the other system already has one-digit node numbers, LWNC
must also be set there.
b) Systems that do not understand node numbers should always be

assigned COT parameter LWNC in the trunks leading to them.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
c) Lines that lead to external systems and that only transfer implicit phone
numbers (for the definition, see Section 42.1.2.2, “Explicit and implicit
phone numbers”) must be provided with the COT parameter LINO. LINO
may not be set for CO lines.
d) The COT parameter DFNN causes the fictive, virtual node number
assigned to the set to be used for modification. It prevents a
reconstruction of the source node number and should thus be set only in
exceptional cases.
This brief overview is intended to provide a general idea. The following chapter,
however, absolutely must be read and understood.
42.1.2 Phone numbers
42.1.2.1 Structure a phone number
The phone numbers transported in an ISDN network have further information in

addition to the actual numbers. It thus provides information as to whether a
number should be displayed (presentation indicator), how and whether a test
takes or has taken place (screening indicator SCRE), to which numbering plan
this number belongs (numbering plan identifier NPI), and which codes it contains
(type of number TON). In an OpenScape 4000/HiPath 4000 network, the
respective node numbers are also transferred together with the numbers ("calling
numbers").
Three different numbering plans are supported:
1. ISDN CO numbering plan according to ETSI-E.164: NPI = ISDN
2. Private numbering plan (PNP) according to ETSI-E.189: NPI = PRIVATE
3. OpenScape 4000-specific numbering plan: NPI = UNKNOWN
Each node in the network can be set up parallel for all three plans. OpenScape
4000 phone numbers in a numbering plan NPI=ISDN or NPI=PRIVATE consist of
the DID number, the various codes, the corresponding prefix and the exit code for
the respective numbering plan:
Phone Exit + Prefix + Code(s) + Direct in dial

number:
CC AC LC
e.g. 0 00 49 89 722 4711 (International STNO)
0 0 89 722 4711 (National STNO)
0 722 4711 (Subscriber STNO)
Abbreviations: CC=country code, AC=area code, LC=local destination code,

STNO=phone number
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
The first zero in the example above signals the numbering plan. Traditionally, it
means that the subscriber would like an exit to the central office. Since
OpenScape 4000/HiPath 4000 networks can also be configured with CO
numbers (NPI=ISDN), however, only LCR decides whether a CO exit really takes
place or whether a tie line is routed. The exit code (here, 0 for NPI=ISDN) is the
only entry in which WABE must be set up (digit analysis result CO or TIE).
IMPORTANT: In corporate networks in which the numbering plan NPI=ISDN is

also set up for network-internal calls, the exit code (e.g. 0) should be set up in
WABE with a digit analysis result of TIE. The CO tone facility is then set up using
the W field in the digit pattern plan (AMO LDPLN).
The prefix signal the level of a number. In Germany "00" must be dialed to reach
international subscribers, for example, in England. The "0" says that a national
subscriber, for example, in Dusseldorf, is required. If no prefix is dialed, the
subscriber is in the caller’s own local network, for example, in Munich. These
levels are reflected in the type of number (TON) information. For NPI=ISDN, the
values INTERNAT for international, NATIONAL for national, SUBSCR for
subscriber-related, and UNKNOWN for DID numbers (e.g. 4711) can be
assumed.
The addressing in the respective level takes place using the codes. For
NPI=ISDN, the county code (CC) is thus used as the address of a country (e.g.
49 for Germany), the area code as the address of a city (e.g. 89 for Munich), and
the local destination code (LC) as the address of the main station (e.g. 7007).
The structure of a phone number in the private numbering plan (NPI=PRIVATE)

has the same structure as a number in the ISDN CO numbering plan. The only
difference is in the naming of the parameters. The TON can thus assume the
values LEVEL2, LEVEL1, and LOCAL and the codes are called Level 2 Code
(L2C), Level 1 Code (L1C), and Local Code (LC). Both numbering plans, ISDN
and PRIVATE, require that every point in the network is uniquely addressed and
can be reached from every other point with precisely this address (e.g. if
Germany can be reached with 49 from every point in the worldwide telephony
network - only the exit and prefix may differ).
The structure of a phone number in the OpenScape 4000-specific numbering

plan (NPI=UNKNOWN) behaves differently. Here, a certain node is addressed
with open numbering with cross codes. Here, multiple addressing of a node may
result, for example, if two networks are merged. The same node of Point A in the
network may have another address - and thus another code - than that of Point
B. This may lead to confusion and thus to errors in the execution of network-wide
features.
Problems may also arise in the merging of existing networks. In such cases, the
solution is to expand the hierarchy by one level so that the node numbers and
assigned codes in the network are unique again. If a node in a subnet with the
code 99 is connected to the node of another subnet that also has a code of 99,
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Level 1 is introduced. One node then receives the code 91-99 and the other the
code 92-99. The only problem is that the area code 91 or 92 was dialed as well,
which means that the numbers change. This has the disadvantage, however, that
the numbers 91 and 92 must be unassigned in WABE. If Code 99 is unique in the
network, however, it is not necessary to adapt the code when introducing a new
level (for example, Node 1-2 would then have a code of 99).
All of these problems are avoided if the ISDN numbering plan is used for these
networks. The following table shows the advantages and disadvantages of the
numbering plans.
Numbering Advantages Disadvantages

plan
ISDN + unique worldwide - somewhat long phone numbers
+ hierarchical structure - not always applicable for subscribers
+ simple generation without CO DID numbers
+ no getting used to internal
numbers for the user
PNP + hierarchical structure - somewhat long phone numbers
+ simple generation - not guaranteed to be unique due to lack
of coordination
OpenScape + short phone numbers - no hierarchical structure
4000 - somewhat high generation expenses
(UNKNOWN) - not unique
Table 10 Advantages/disadvantages of the various numbering plans
42.1.2.2 Explicit and implicit phone numbers
As described in Section , a phone number in ISDN networks has, in addition to

the actual digits, additional information on NPI and TON. If this information is not
included, for example, in the case of analog sets, or if the information has a value
of UNKNOWN, only the digits must be meaningful; i.e., the address must be able
to be reached solely by the dialing of the digits. This case is trivial since it appears
during each dialing of a phone number by the user. Such a number that can be
evaluated at any time by WABE has an implicit format according to the definition.
During the transport of the phone number, however, certain information contained
in the digits can be extracted. Exit codes thus provide information on the selected
numbering plan (NPI) and the prefix of the level of the number (TON). A dialed
implicit phone number 0-0-89-722-4711 can thus also be transferred as 89-722-
4711 with the additional information NPI=ISDN (since 0 is considered to be the
exit in the CO numbering plan in this case) and TON=NATIONAL (since 0 is the
prefix of a national number). These numbers, which contain no exit codes and no
prefixes, but which are labeled by NPI and TON, are called explicit phone
numbers. They cannot be analyzed by WABE and must thus be converted into an
implicit format before evaluation.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
According to definition, an explicit number must have an NPI not equal to

UNKNOWN and a TON not equal to UNKNOWN. It may thus not contain exit
codes or prefixes. The other way round an implicit number must always have
TON = UNKNOWN and all required digits must possibly contain the exit code an
prefixes. Table 1 shows the NPI/TON combinations defined in the ETSI standard.
The designations on the AMO interface are marked with capital letters.
NPI = E164 (ISDN) NPI = PNP (PRIVATE) NPI = UNKNOWN

NPI = LANDMOB
NPI = DATA
NPI = MARITMOB
NPI = NATIONAL
NPI = TELEX
TON = International TON = Level2-Regional TON = UNKNOWN
(INTERNAT) (LEVEL2)
TON = NATIONAL TON = Level1-Regional
(LEVEL1)
TON = Subscriber (SUBSCR) TON = LOCAL
TON = UNKNOWN TON = UNKNOWN
Table 11 ETSI NPI/TON combinations
The advantage of an explicit number lies in its independence from exit codes
or prefixes, which, as previously mentioned, often differ in different networks and
countries and, on the other hand, in the possibility of performing a source-
independent number modification at any time, for example, if a call that was
originally a national call is routed via an international network. In the standard
case for explicit numbers, a source/destination-dependent modification thus
becomes completely unnecessary with AMO KNMAT.
AMO KNPRE regulates the relationship between the explicit and implicit
numbers. This defines which exit code belongs to which prefix for a certain NPI/
TON combination. In the example above, the exit "0" thus belongs to the
combination NPI=ISDN and TON=NATIONAL. The actual codes (e.g. CC, AC,
LC) are saved in AMO KNDEF in the case of explicit numbers.
Since external nodes that understand only implicit numbers possibly supply the
NPI/TON information incorrectly (e.g. station with NPI=ISDN, TON=SUBSCR),
which leads to errors in the number modification, the COT parameter LINO was
introduced.
RULE:
The COT parameter LINO (line with implicit numbers) causes the format of all
numbers to be overwritten with UNKNOWN by default whether incoming or
outgoing. If an explicitly signaled, external node (e.g. central office) can be
reached by means of a set with this number, an entry for this node must exist with
AMO KNFOR.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
42.1.3 US EPNP
One special case of a numbering plan is the plan formerly used in U.S. systems
(R6.6), EPNP (Enhanced Private Numbering Plan). In the process, a PNP
numbering plan that works without an exit code and without prefixes is
configured. The number thus complies with the following scheme:

number:
L2 Code L1 Code Loc Code
e.g. 99 88 777 4711 (Level 2 STNO)
88 777 4711 (Level 1 STNO)
777 4711 (Local STNO)
Abbreviations: STNO=Station, i.e. phone number
In special cases, exit codes may also exist.
A normal PNP for comparison:

number:
L2 Code L1 Code Loc Code
e.g. 9 11 99 88 777 4711 (Level 2 STNO)
9 1 88 777 4711 (Level 1 STNO)
9 777 4711 (Local STNO)
A typical EPNP, however, only consists of a three-digit local code (no L1 and L2
codes) and a six-digit internal number. The signaling takes place in explicit format
with NPI= PRIVATE and TON=LOCAL.
Since the number that can be dialed (i.e. the implicit number) has no exit and no
prefixes, it is thus more similar to a number of the OpenScape 4000-implicit
numbering plan. The consequence is that no unique, explicit number can be
extracted from the implicit number. The configuration is thus a mixed form of the
explicit numbering plan and cross codes (for an example, see below).
42.1.3.1 The (multi-level) node numbers
Dependency of the (multi-level) node numbers on the phone numbers

A general definition of the node numbers can be found in the “Networking Terms”
chapter. Here, the role of the node numbers during number modification is
described.
Since an individual number is not assigned to every node in an OpenScape 4000/

HiPath 4000 network (e.g. several nodes are hidden behind the main station 089
7007), physical node numbers are used in a network as the unique address of a
node. These node numbers are entered in various AMOs (ZAND, RICHT, etc.)
and transported according to the number in the network protocol.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Based on the ISDN or PRIVATE numbering plan, a node number also has a
hierarchical structure. It has Levels 0, 1, and 2. Just like the numbers, the
individual levels of the node number define the respective number ranges. All
nodes of a company in Munich, for example, may differ in Level 0, all cities of the
company in Germany in Level 1, and all company countries in Level 2. It must be
observed here that the node number is uniquely assigned to a node only in Level
0. The other levels describe ranges of subordinate nodes or levels. The ranges
described in this manner must always be coordinated with the number ranges
(e.g. the number area 89 for Munich should be precisely assigned an area
number in Level X).
Rules
RULE:
A physical node number must be assigned to each node with AMO ZAND,
parameter PNNO, which may be assigned only once within the network.
Node number 0 is not valid.
RULE:
All OpenScape 4000/HiPath 4000 networks can continue to be operated with

one-level node numbers. If multiple levels are desired, however, the node number
ranges should be adapted to those of the phone numbers!
RULE:
When multi-level node numbers are used, all node numbers must be kept at the
same level within the network! If this is not possible, for example, since external
nodes do not understand node numbers the COT parameter LWNC (line without
node number) must be set in the respective set and a corresponding multi-level
node number entered as destination node for this system in RICHT. If the other
system already has one-digit node numbers, LWNC must also be set there.
RULE:
Systems that do not understand node numbers should always be assigned COT
parameter LWNC in the trunks leading to them. LWNC always functions in an
outgoing direction.
RULE:
The COT parameter DFNN should be used only in exceptional cases. The effect
of DFNN is that the TDCSU node number is used for the modification when
incoming and the reconstruction of the node number from the number is
prevented. The disadvantage here is that a node-specific modification is
prevented. A certain advantage results from an improvement in performance
through the prevention of the reconstruction. You should use DFNN only for lines
to external systems or if a node number reconstruction is not necessary due to
the simplicity of the network. DFNN must always be used in combination with the
TDCSU parameter NNO.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
42.1.4 Number signaling
42.1.4.1 Destination and information numbers: The general

modification method
The numerous numbers in a network can basically be divided into two categories:
1. The numbers which describe the destination (e.g. the B subscriber of the
“called number”)
2. The numbers provided as additional information (e.g. information on the A

subscriber of the “calling number” or the forwarding subscriber in the
“redirecting number” o. "last rerouting number")
Numbers of the first category are handled by WABE and LCR and modified
accordingly. Here, they should generally be called "destination numbers." By
contrast, numbers of the second category are modified using AMO KNMAT, AMO
KNPRE, AMO KNFOR, and AMO KNDEF. The "information numbers" modified in
this manner are called "calling numbers" in this document. The modification
method itself is designated by the term "INS" (Info Number Signaling). For many
features, the number previously specified as additional information is used as the
destination number in a later procedure (e.g. stored number redial, callback, etc.).
For this reason, it is the objective of the INS to treat the number in such a way the
point it is addressing can be called at any time and place in the network.
RULE:
The information numbers must always be modified in such away that the point
they are addressing can be reached from any transmitting location in the network
and at any time!
42.1.4.2 The influence of LCR on Info Number Signaling (INS)
The NPI and TON parameters in the LCR outdial rules

Both methods of number modification - LCR and INS - are basically different, but
cannot be observed separately from each other. LCR thus ultimately decides on
the route of a call and thus on the numbering plan to be used (AMO LODR with
the NPI command). Since the numbering plan demanded by the destination
number for a certain route also corresponds to that of the information numbers by
default (e.g. in case of a CO exit, all numbers must be from the NPI=ISDN
numbering plan), the numbering plan of the destination numbers from LCR is also
used for the information numbers. The other information such as TON and
screening indicator is either derived from the node format table (set with AMO
KNFOR) or set by default and thus determined independent of LCR.
RULE:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
If numbering plans not equal to NPI=UNKNOWN are used in a node, each route
element (AMO LDAT) is to be assigned the respective numbering plan (NPI) and
the type belonging to the destination number (TON) in the corresponding outdial
rule (AMO LODR).
The destination node number in AMO RICHT

In AMO RICHT, a virtual destination node number and a physical destination
node number must be defined. The virtual destination node number is used for
number modification and, for example, also displayed in charge tickets. The
physical destination node number is mainly used for the closed numbering of the
assignment of subscribers with destination numbers to destination node number.
If a node has a partner node that hides several virtual nodes, a route must be
defined for every virtual node. In the dial plan (AMO LDPLN), entries must be
made in such a way that the right virtual destination node can be addressed. In
extreme cases, complete numbers including the extension must be configured to
guarantee the assignment of subscribers to various virtual nodes (NNO).
Example:
In PABX 1, Subscriber 4711 is administered in VKN 1 and thus available with tie
line code 777. Subscriber 4712 is also in VKN 1, but administered in PABX 2. This
situation may have arisen due to a move of Subscriber 2 from PABX 1 to PABX 2
while keeping the numbers. VKN 1 thus extends to two physical nodes. In the
partner node PABX 3, the dial plan entry must take place as follows: The digit
pattern "777 4711" is assigned to Route 1 with DNNO = VKN1, while the digit
pattern "777 4712" is assigned to Route 2 with DNNO = VKN2.
The destination node number in AMO LDAT

The virtual destination node number entered in AMO RICHT always describes the
remote destination, i.e. the end point of a call. Since no differentiation
dependent on the distance is possible here, however, a destination node number
that is valid for a certain route is entered in AMO LDAT. The LDAT and not the
RICHT destination node number is thus used for the modification. This could be
the case, for example, if rerouting takes place via the central office for an
originally network-internal call. In the rerouting node, the central office or a fictive
node number that deviates from AMO RICHT can be entered as the destination
node - dependent on route - thus resulting in an accordingly different reaction.
IMPORTANT: Normally, you do not have to enter a virtual destination node

number in AM LDAT.
The LATTR=SUPPCPN attribute in AMO LDAT

If a number is to be transferred from one numbering plan to another, this is a case
of “Transit Interworking.” This transfer takes place by placing the codes of the new
numbering plan before the original number (implicit format). An explicit number of
89-722-99-4711 with NPI=ISDN and TON=NATIONAL, for example, thus arises
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
from number 99-4711 with NPI=UNKNOWN and TON=UNKNOWN (OpenScape

4000 specific numbering plan) for a transfer to the ISDN CO numbering plan.
Since various problems can arise with this method (e.g. a central office does not
accept the number since 99-4711 does not come from the assigned group of
numbers), the signaling of the information numbers can be entirely prevented in
such a linkage case by setting LATTR=SUPPCPN (no display of A subscribers)
in LDAT for certain routes. Instead, a permanent, substitute number set by AMO
KNMAT (e.g. attendant console number) can be sent instead.
IMPORTANT: The SUPPCPN parameter may not be used in connection with

confidential numbers or the suppression of A numbers since a suppression takes
place only in case of transit interworking!
42.1.4.3 Info Number Signaling (INS)
The INS has the objective of modifying a number specified as information (“calling
number”) in such a way that this number reaches the point that it addresses again
and again as a destination number from any place in the network and at any time.
For this purpose, the number, which was originally available as a DID number
(e.g. 4711) must be replaced with the corresponding codes.
This modification can basically take place in two ways:
1. On the one hand, it can take place using AMO KNMAT and AMO KNFOR
depending on source and destination.
2. On the other hand, a modification can take place only on the basis of the
actual and set numbering formats with AMO KNPRE, AMO KNFOR, and
AMO KNDEF (format-dependent modification) through the use of explicit
numbers. The second method has the decisive advantage that the network
administration usually does not have to have detailed knowledge of the
network topology.
The selection of one of the two methods depends on the entries in the AMO
KNMAT of the corresponding numbering plan for the current source/destination
relationship. If AMO KNMAT has an entry with a valid modification condition, the
AMO KNMAT modification will always be performed. If no entry exists, the
format-dependent modification is taken into account.
Source/destination-dependent modification with AMO KNMAT

1. When is AMO KNMAT used for modification?
A source/destination-dependent modification with AMO KNMAT and AMO
KNFOR should take place whenever the numbers are implicit and cannot be
converted into an explicit format due to their structure or whenever a
destination node requires an implicit format. Since the OpenScape 4000
specific numbering plan always contains implicit numbers, all modifications
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
regarding tie line codes must be settled using AMO KNMAT. 

For the NPI=ISDN and NPI=PRIVATE numbering plans, modification using
AMO KNMAT makes sense only in exceptional cases.
2. What is the structure of the node connection matrix?

The node connection matrix managed using AMO KNMAT is set up
separately for each node number level and numbering plan. There are nine
(3 levels x 3 numbering plans) KNMAT tables that are independent of each
other. The selection of tables to be processed is oriented on the NPI and node
number levels listed there for incoming numbers. In the case of outgoing
numbers, the numbering plan to be selected depends on the destination
number, i.e. on the LCR (AMO LODR), and the levels to be processed
depend on the levels of the node numbers. Figure 51 shows the principle
structure of the node connection matrices.
ONNO
Modification point 3
DNNO
Level 2
Level 1
Level 0
NPI=PRIVATE NPI=ISDN NPI=UNKNOWN
Figure 51 Modification matrices and modification points in a three-level

network
3. How is the matrix processed?

In regard to the specific numbering plan, the KNMAT tables are always run
through from the highest to lowest level (modification point 3->2->1) and all
minus entries (abbreviation of digits) are processed. The tables are then
processed from the lowest to the highest level (modification point 1->2->3),
whereby all plus entries (supplementing of digits) are processed. Minus
entries are deducted only if the correspond with the first part of the numbers.
Plus entries, on the other hand, are always supplemented unless the number
exceeds the maximum length of 22 digits.
In the case of multi-level KNMAT modification, it is very important to clarify
that the node numbers are assigned to precisely one node only on Level 0
and that Levels 1 and 2 describe larger areas of nodes. A node with a physical
node number of 1-2-5 in ZAND is clear within the network only with a three-
digit node numbers (e.g. "1" for all nodes in Germany, "2" for all nodes in
Munich, and "5" for precisely this node in Munich). In the KNMAT modification
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
of this node for Node 1-2-6, however, the virtual node must always be
observed, which means that Germany is modified to Germany (1 to 1) in Level
2, Munich to Munich (2 to 2) in Level 1, and Node 5 to Node 6 in Level 0.
4. Why were the modification conditions introduced?

To prevent ambiguities in the higher levels, AMO KNMAT has a modification
condition parameter (MODCON). With this parameter, the entered
modification can be executed only under certain conditions. These conditions
can be derived from the desired traffic type. A modification can thus be
performed only in case of outgoing terminating traffic (ABG), incoming
terminating traffic (ANKE), transit under observance of the numbering plan
(TRANSH), transit with a change of the numbering plan (TRANSI), never
(NONE), or always (ALL) or in case of a combination of these conditions. If
the supplementing of digits on Level 2 can thus take place only if the call
comes from the node for which AMO KNMAT has been set up and not in a
transit node on Level 2, the modification condition MODCON=OUT should be
entered.
In combination with the subscriber-individual authorization DIDBLK (direct
inward dialing blocking), the REPEXT special modification condition effects a
complete replacement of the "calling number" by a substitute number.
REPEXT and DIDBLK are always set whenever station numbers are not
known to the central office so that they are replaced by an attendant console
number, for example. In case of REPEXT without DIDBLK, the substitute
number is also used, but the lower digits with the calling number are
overwritten. An example can be found in the Service Manual the "EURO-
ISDN CO Interface" chapter.
5. What are "logical" node numbers?

In addition to the actual area and node numbers of a level, AMO KNMAT has
so-called logical node numbers. They were introduced to simplify
administration, i.e. to minimize the number of entries in the matrix. The
following logical node numbers exist:
– OWN: All own node or area numbers.

After entry, the logical OWN node is directly converted into all really own
node numbers (according to AMO KNDEF) and should act only as a
simplified aid for the administrator.
In connection with the logical entry ##### for NUMEXT/NUMRED, the
corresponding node code is extracted from AMO KNDEF under
consideration of the skip digits for each virtual node number.
– ROW: Stands for all nodes/areas in the respective level (including the
own node).
The logical node ROW represents a new line or column in AMO KNMAT.
If no entry for the precise source/destination relationship exists in the
corresponding level and numbering plan or if the MODCON is incorrect,
the real source/destination node is replaced by the logical node ROW and
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
an entry is sought there. In the process, only one node number not equal
to the own node number is replaced by ROW. Both node numbers are
never replaced by ROW at the same time.
– CDR as special node for call data recording The logical node number
CDR is taken into consideration only as a destination node number
(parameter DNNOL) in the numbering plan UNKNOWN (parameter NPI).
Here, the special modifications for the call data recording can be entered
independently of the source node (MODCON=ALL). How the modification
should take place is described in the “Call Data Recording” chapter and
not dealt with further here.
6. How is the logical node ROW handled?

Example for the handling of ROW:
The connection from Node 100 to Node 200 should be established. No entry
exists for ONNO/DNNO = 100/200. The KNMAT table is as follows:
---------------------------------------------------------------------------
NODE MATRIX FOR NPI = UNKNOWN, LEVEL = 0, OWN NNO = 100
---------------------------------------------------------------------------
ONNO |DNNO |CONN|MODCON| NUMEXT | NUMRED
/ ONNOL|/ DNNOL | | | |
------+------+----+------+------------------------+------------------------
100 |ROW | A |ALL | 99 | - 
------+------+----+------+------------------------+------------------------
ROW | 100 | A |ALL | 55 | - 
Result: "99" is supplemented since there is no entry in 100/200 and the own
NNO 100 is not replaced by ROW.
Remark: A "0" in one of the lower levels of a node number in AMO (e.g. RICHT)
is interpreted as ROW in AMO KNMAT if a clear number is contained in
one of the higher levels.
IMPORTANT: A targeted entry with ONNO/DNNO always has priority before

ROW!
7. How is the OWN logical node handled in connection with the modification
conditions?
A modification can generally take place in an incoming and outgoing manner.
For outgoing terminating traffic (MODCON=OUT), modification only takes
place in an "outgoing" manner and in an "incoming" manner for incoming
terminating traffic (MODCON=IN). In transit traffic, homogeneous transit
(MODCON=TRANSH) and transit interworking (MODCON=TRANSI) must
be differentiated. To keep the number in the node as short as possible, ONNO
will be modified to DNNOL=OWN when incoming in both cases. In TRANSH,
the possibly previously abbreviated number is supplemented by these
numbers again and then modified with ONNO/DNNO when outgoing. In
TRANSI, the possibly previously abbreviated number is kept and modified
with ONNOL=OWN to DNNO when outgoing.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
8. How is a substitute number set?

If the parameter SUPPCPN is set in the LATTR of AMO LDAT (see Section ),
a substitute number can be set using AMO KNMAT. The applies in case of
MODCON=TRANSI and is read from AMO KNMAT with ONNO/DNNO when
outgoing.
9. How can the KNMAT modification be configured for the ISDN and PRIVATE
numbering plans as well in case of exceptions?
If, in special cases, explicit numbers also have to be handled with AMO
KNMAT when incoming, a pretreatment of the calling number is performed
before the KNMAT modification. Every previously explicit number (e.g. 89 722
4711, NPI=ISDN, TON=NATIONAL) is converted into the respectively highest
possible format (TON=INTERNAT) using AMO KNDEF and AMO KNPRE. All
codes, the respective exit codes, and the prefixes are added (e.g. 0 00 49 0
0 89 0 722 4711). Now, an abbreviation of the desired code can take place
using AMO KNMAT (e.g. in the ROW/OWN entry): -00049). Invalid exit codes
and prefixes remaining in the number are removed by the program after
modification (e.g. 0 0 89 722 4711).
In the case of the outgoing modification of numbers from the NPI=ISDN and
NPI=PRIVATE numbering plans, the codes entered in AMO KNMAT must
always be coordinated with AMO KNFOR.
Rules for KNMAT modification

RULE:
By default, the AMO KNMAT should be used only for the UNKNOWN numbering
plan (NPI parameter). The NPI=ISDN and NPI=PRIVATE numbering plans
should be handled using format-dependent modification (see Section )!
RULE (Important !):
By default, only the logical node numbers OWN and ROW should be used in
AMO KNMAT for the UNKNOWN numbering plan. The following rule applies: in
ONNOL=ROW to DNNOL=OWN, the own node code is abbreviated when
incoming and, in ONNOL=OWN to DNNOL=ROW, the own node code is
supplemented when outgoing. The specification of the own node code can also
be shown in logical format (#####).
The numbers in the source node are thus brought to the highest possible format
and those in the destination node to the lowest possible format. This applies both
for closed and open numbering (the area code applies in case of closed
numbering). This requires that each node in the network can be reached with
precisely one node code!
RULE:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
The special rules for areas are suspended. The exceptions are areas in which
the full subscriber number of the other nodes are not set up in WABE. Further, an
entry must be made on the 45 line in AMO KNMAT (ONNO = DNNO) for all nodes
of the area in this case.
RULE:
When multi-level node numbers are used, the entry of the codes in AMO KNMAT
must always take place at the corresponding level; that is, a country code (e.g.
49) is always at Level 2, an area code (e.g. 89) is always at Level 1, and a local
destination code (e.g. 722) is always at Level 0.
RULE:
If an external mode cannot be modified itself and is number openly to the own
node, the missing codes must be set using AMO KNMAT. In the process, the
numbers in AMO KNMAT of the respective numbering plan must be
supplemented from ONNO to DNNOL=OWN (MODCON=IN). If the node also
sends no node number, the set for this node must refer to the COT parameter
LWNC and the node number of the external node (parameter NNO) must be
entered in TDCSU.
Format-dependent modification
1. What is format-dependent modification?
Format-dependent modification offers the opportunity to convert an incoming
number (calling number) in any format automatically using the codes in AMO
KNDEF to a certain destination format (AMO KNFOR).
This modification method is configured with AMO KNPRE, AMO KNFOR, and
AMO KNDEF. It is possible only for the processing of explicit numbers. Since
this is the case by default, however, at least in the NPI=ISDN and
NPI=PRIVATE numbering plans, the use of format-dependent modification
should always be preferred to source/destination-dependent modification in
this case.
2. How is the format-dependent modification configured?

The modification takes place as follows:
– The entry of the corresponding code in AMO KNDEF.
– The setting of the node prefix table using AMO KNPRE. Here, you can set
the prefixes belonging to the NPI/TON combination and the exit code.
This enables a conversation from explicit to implicit numbers and vice
versa.
– The setting of the node format table using AMO KNFOR. The TON entry
in KNFOR decides on the format of the number. Since, in the case of
overlapping nodes for a virtual node number, it is no longer clear whether
the node in question is the part of the overlapping virtual node on the
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
actual physical node or whether it is the part of the overlapping virtual

node on another physical node, two TON parameters are introduced:
TONIN and TONOUT:
TONIN or rather, a KNFOR entry on the own node (DNNO=own node
number), determines the display format of the number for all telephones
on this node (e.g. displays). If no entry exists here, the number is always
converted to the lowest possible format (e.g. only the DID number
TON=UNKNOWN). An entry with TON=NATIONAL, for example, has the
effect that the calling number is always displayed in the national format
(e.g. 0 089 722 4711).
TONOUT or, rather, a KNFOR entry with any number of destination
nodes in the network, determines the number format, i.e. the TON, for
precisely these nodes. If no entry exists, the highest possible format
(e.g. TON=INTERNAT) is taken as the default.
If TON=UNKNOWN is entered in KNFOR, the number for the
corresponding destination node must be implicit. Here, no format-
dependent modification is performed, but rather only the entries in AMO
KNMAT are processed.
Rules for format-dependent modification

RULE:
The format-dependent modification is set up using AMO KNDEF. The entry of

codes to trunks is no longer required.
RULE:
In each node that can be addressed with numbering plan NPI=ISDN or

NPI=PRIVATE, all prefixes and exit code should be set up for the possible
numbering plans using AMO KNPRE!
RULE:
The node format table (AMO KNFOR) should always be set up when external
nodes require a certain format of the numbers or if the subscribers require a
certain display format on their own node. If KNFOR is not set up, the calling
number is brought to the highest format (e.g. TON=INTERNAT) when incoming
and the lowest format (TON=UNKNOWN) when outgoing by default!
RULE:
For lines through which numbers with prefixes but without an exit are transferred
(e.g. 089 722 4711), the ISDNIP and ISDNNP parameters must continue to be
configured in AMO TDSCU.
No prefixes may be set at tie lines through which OpenScape 4000 specific
numbers are transferred as well. 
Prefixes for the conversion of normal, implicit numbers (e.g. 0 089 722 47110)
into normal, explicit numbers are to be set in AMO KNPRE.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Examples for the configuration of the number modification
42.2 Examples for the configuration of the number modification

The following abbreviations are used in the following:
• PNNO: A physical node number
• NNO: A virtual node number
• PNODECD: A physical node code
• NODECD: A virtual node code
• FVNNO: A fictive virtual node number
42.2.1 One-level network (only Level 0)
42.2.1.1 Closed-numbered area with digital ISDN CO

connection
Area 96
NNO 1 NNO 2
FVNNO 3 PNNO 11 PNNO 22
ISDN-CO TC 1
e.g. TT 1 TT 2
DIUS
OpenScape OpenScape
4000 4000
Figure 52 Example: Closed-numbered area with digital ISDN CO connection
A closed-numbered area consisting of Nodes 1 and 2 through which the digital

trunk circuit TC1 is connected to an ISDN-CO is located in Figure 52. The fictive
node number 3 was assigned to the central office. Both OpenScape 4000 nodes
are connected via tie trunks QS1/QS2:
In the example, the format-dependent number modification configured with AMO

TDCSU, AMO KNFOR, AMO KNDEF, and AMO KNPRE should be effective.
IMPORTANT: With AMO KNMAT, no modification should be set in this case.
Configuration in physical node 11

Configure the physical node with PNNO=11 as follows:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
• Set the node table (define the virtual own NNO):

ADD-KNDEF:NNO=1,TYPE=OWN,ISDNCC=49,ISDNAC=89,
ISDNLC=722,ISDNSK=3,ISDNUL=EXT,NODECD=96;
• Set the node prefix table:
• Set the central system data:
CHANGE-ZAND:TYPE=ALLDATA,PNNO=11, PNODECD=888811;
• Set the digital trunk circuit:
ADD-BUEND:NO=30,TGRP:=44;
ADD-
TDCSU:OPT=NEW,DEV=VCCOD,BCGR=1,COTNO=11,COPNO=2,TGRP=44,LCOSV
=1, LCOSD=1,PROTVAR=EDSGER,NNO=3,ISDNIP=00,ISDNNP=0;
• LCR route configuration:
With AMO RICHT, you can set up LCR routes for the central office and tie line
according to the "LCR Description." Enter 3 as the destination node for the
CO route and 2 as the destination node for the tie line route.
ADD-RICHT:MODE=LRTENEW,LRTG=710,LSVC=ALL,TGRP=44,DNNO=3;
With AMO LODR, you can configure the outdial rules for CO connections. In
outdial rule 10 for the CO route, numbering plan NPI=ISDN and the TONs for
the called numbers must be included (UNKNOWN in this example). The NPI
numbering plan, which is always determined from the LCR, is important for
the modification of the calling number.
ADD-LODR:ODR=10,CMD=NPI,NPI=ISDN;
ADD-LODR:ODR=10,CMD=TON,TON=UNKNOWN;
The outdial rule is assigned to the route elements using AMO LDAT.
ADD-LDAT:LROUTE=710,LSVC=ALL,LVAL=1,TGRP=44,ODR=10,LAUTH=1;
With AMO WABE, enter the routing code into the dial pattern plan:
ADD-WABE:CD=0,DAR=TIE;
With AMO LDPLN, enter the route elements into the dial pattern plan:
ADD-LDPLN:LDP=0-X,DPLN=0,LROUTE=710,LAUTH=1;
• Set the node format table:
1. Normally, the node format table must not be set. In this case, the "calling
number" is always sent to the central office in international format. If the
central office wants a national number with the test attribute
SCRE=NOTDEF, enter the following command:
ADD-KNFOR:DNNO=3,NPI=ISDN;,TONOUT=NATIONAL,SCRE=NOTDEF;
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
The NPI parameter in AMO KNFOR is the selection parameter. The NPI
is determined from the LCR outdial rule (AMO LODR).
2. Without setting the node format table with DNNO=1 (own node), the
"shortest" possible number is displayed for the subscribers connected to
Node 1 in case the subscriber is called from the central office. The extent
of the shortening is determined by the codes set by AMO KNDEF (see
above). If the calling number should always be displayed in a certain
format (e.g. international) for the subscriber, enter the following
command:
ADD-KNFOR:DNNO=1,NPI=ISDN;,TONIN=INTERNAT;
Please observe that, for this function, the own node should be entered as
the destination node. In this example of the closed-numbered subsystem
(NNO 2) without the CO connection, this number format also applies in
Node 2.

Configure the physical node with PNNO=22 as follows:
• Set the node table (define the virtual own NNO):

ISDNLC=722,ISDNSK=3,ISDNUL=EXT,NODECD=96;
Since Node 22 has no CO connection and is addressed in a cross-closed-
numbered manner, no number modification must be configured. For this
reason, the specification of NIP in the LCR outdial rule is no longer necessary:
The LCR route, route elements, and dial pattern plan are configured as in
Node 1. The tie trunk group is assigned for CO lines as the trunk group.
• AMO KNPRE and AMO KNFOR are not called in Node 2.
42.2.1.2 Closed-numbered area with analog CO connection
The system configuration corresponds to that shown in Figure 52 with the

exception that no digital or analog CO connection exists. Numbers can be
transferred, e.g. in case of MFC (multi-frequency code) lines (see AMO TACSU,
AMO MFCTA).\
In this case, no format-dependent modification can be configured (reason: NPI/

TON are not transferred) so that you must set all modifications with AMO KNMAT
or AMO MFCTA. In this case, the numbering plan is always UNKNOWN. In this
example, no number modification is set in the MFC table.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification

The node prefix and node format tables are not set.
• Set the analog trunk circuit:

ADD-
TDCSU:DEVTYPE=...,COTNO=11,COPNO=2,TGRP=44,LCOSV=1,LCOSD=1,NN
O=3;
• Configure the LCR route:
LCR is configured as shown in Section . The outdial rule defined using AMO
LODR, however, must be different since NPI is always UNKNOWN.
• Set the node connection matrix:
Incoming from the central office, the calling number is supplemented by the
exit code 0 in Node 1. This happens if the connection for a subscriber is
established at Node 1, but also for connections to subscribers at other nodes.
Toward the central office, the number of the main connection is placed before
the pure station number at exit node 1 of the calling number so that a correct
CO number is provided to the central office.
CHANGE-
KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=OWN&ROW,DNNO=3,NUMEXT=089722;
CHANGE-
KNMAT:NPI=UNKNOWN,LEVEL=0,ONNO=3,DNNOL=OWN&ROW,NUMEXT=0;
The following setting results:
---------------------------------------------------------------------------
---------------------------------------------------------------------------
/ ONNOL|/ DNNOL| | | |
------+------+----+------+------------------------+------------------------
1 | 3 | A |ALL | 089722 | - 
------+------+----+------+------------------------+------------------------
3 | 1 | A |ALL | 0 | - 
3 |ROW | A |ALL | 0 | - 
------+------+----+------+------------------------+------------------------
ROW | 3 | A |ALL | 089722 | - 

In closed-numbered Node 2, no special setting is required for the number
modification.
42.2.1.3 Closed-numbered area with CO connection and

subsystems
There is no difference between Section 42.2.1.1, “Closed-numbered area with

digital ISDN CO connection” and Section 42.2.1.2, “Closed-numbered area with
analog CO connection” for the configuration of the number modification.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
42.2.1.4 Mixed-numbered network with digital ISDN trunk

access points
In this example (Figure 53), the network consists of a closed-numbered area in

Berlin and an open-numbered node in Munich with digital trunk access points.
In the ISDN numbering plan, the format-dependent number modification that can
be configured using AMO KNDEF, AMO KNFOR, and AMO KNPRE is selected.
For the open numbering in the OpenScape 4000 internal numbering plan
UNKNOWN, the number modification must be set with AMO KNMAT.
NODECD: 99
FVNNO 3/ NNO 1
PNNO 3 PNNO 11
ISDN-CO TC 1 TT 1
e.g.
Munich
OpenScape
4000 Munich
Area: NODECD 96 Berlin
FVNNO 5/ NNO 4 NNO 2

PNNO 5 PNNO 44 PNNO 22
ISDN-CO TC 2 TT 4 TT 3 TT 2
e.g.
Berlin
OpenScape OpenScape
4000 4000
Figure 53 Example: Mixed-numbered network with digital ISDN trunk access

points

Trunk calls to Berlin should not already be routed to the central office in Munich,
but rather via the tie line to Berlin.
Since ISDN connections can also come in via the tie trunk during transit, you must
make the ISDN-specific settings here as well.
You can configure the node with PNNO=11 as follows:
• Set the node table:

ISDNLC=722,ISDNSK=3,ISDNUL=EXT,NODECD=99;
CHANGE-KNDEF:NNO=1,DFLT=Y;
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
• Set the own node code in the WABE:

ADD-WABE:CD=99,DAR=OWNNODE;
• Set the digital trunk circuit TC1 (important parameter):
ADD-BUEND:NO=30,TGRP:=44;
ADD-
• Set the digital tie trunk TT1 (important parameter):
The node number does not have to be specified since it is transferred in this
protocol.
ADD-BUEND:NO=30,TGRP=55;
ADD-
TDCSU:OPT=NEW,DEV=S2CONN,BCGR=1,COTNO=11,COPNO=2,TGRP=55,LCOS
V=1, LCOSD=1,PROTVAR=ECMA1;
according to the LCR description.
ADD-RICHT:MODE=LRTENEW,LRTE=700,LSVC=ALL,TGRP=44,DNNO=3; /*
CO */
Central office over tie line */
Central office over tie line */
TIE */
With AMO LODR, you can configure outdial rules for CO and tie line
connections. Outdial rule 10 is applied to international numbers in tie line
traffic, outdial rule 11 to national numbers in tie line traffic, and outdial rule 12
to direct CO traffic. Outdial rule 13 is intended for pure tie line traffic. The NPI
numbering plan, which is always determined from the LCR, is important for
the modification of the calling number. The TON is used only for the called
number.
ADD-LODR:ODR=10,INFO="CO OVER TIE LINE INTERNAT.";
ADD-LODR:ODR=10,CMD=TON,TON=INTERNAT;
ADD-LODR:ODR=11,INFO="CO OVER TIE LINE NAT.";
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
ADD-LODR:ODR=11,CMD=TON,TON=NATIONAL;
ADD-LODR:ODR=12,INFO="CO";
ADD-LODR:ODR=13,INFO="TIE";
The outdial rules are assigned to the route elements with AMO LDAT.
ADD-LDAT:LROUTE=700,LSVC=ALL,LVAL=1,TGRP=44,ODR=12,LAUTH=1;
ADD-LDPLN:LDP=0-X,DPLN=0,LROUTE=700,LAUTH=1;/* Central office
*/
ADD-LDPLN:LDP=0-00-4930-X,DPLN=0,LRTE=701,LAUTH=1;/* Central
office over tie line internat. */
ADD-LDPLN:LDP=0-0-30-X,DPLN=0,LROUTE=702,LAUTH=1; /* Central
office over tie line national */
ADD-LDPLN:LDP=96-X,DPLN=0,LROUTE=711,LAUTH=1; /* TIE */
The node format table can be set as described in Section .

For the ISDN numbering plan, format-dependent number modification was
selected in this example. The node connection matrix can thus not be set for
NPI=ISDN.
For the UNKNOWN numbering plan (i.e. the OpenScape 4000 specific
numbering plan), the modifications must be configured for open numbering.
Using AMO KNMAT, you must thus set the matrix in such a way that the
outgoing calling number is always supplemented with the own node code. In
case of incoming connections that end at Node 1, the number is shortened by
its own node code.
CHANGE-
KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=OWN,DNNOL=ROW,NUMEXT=#####;
CHANGE-
KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=ROW,DNNOL=OWN,NUMRED=#####;
---------------------------------------------------------------------------
---------------------------------------------------------------------------
------+------+----+------+------------------------+------------------------
1 |ROW | A |ALL | 99 | - 
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
------+------+----+------+------------------------+------------------------
ROW | 1 | A |ALL | - | 99 

Trunk calls to Munich should not already be routed to the central office in Berlin,
but rather via the tie line to Munich.
Since ISDN connections can also come in via the tie trunk during transit, you must
make the ISDN-specific settings here as well.
Configure the virtual node with PNNO=2 as follows:

ISDNLC=611,ISDNSK=3,ISDNUL=EXT,NODECD=96;NODECDSK=2;
• Set the own area code in WABE:
• Set the digital tie trunk TT2 (TGRP=55), TT3 (TGRP=66):
The node number does not have to be specified since it is transferred in this
protocol.
ADD-
V=1, LCOSD=1,PROTVAR=ECMA1; /* most important parameter */
ADD-
V=1, LCOSD=1,PROTVAR=ECMA1; /* most important parameter */
according to the LCR description.
ADD-RICHT:MODE=LRTENEW,LRTE=700,LSVC=ALL,TGRP=66,DNNO=5;/* CO
*/
OVER TIE*/
OVER TIE*/
ADD-RICHT:MODE=LRTENEW,LRTE=711,LSVC=ALL,TGRP=55,DNNO=1;/*
TIE */
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
connections. Configure the outdial rules with AMO LODR in the exact same
manner as in Node 1 (outdial rules 10 to 13 in the example). Only the outdial
rule for digit pattern 0-X changes:
ADD-LODR:ODR=12,CMD=ECHO,FIELD=1;/* transfer 0 */
The outdial rule is assigned to the route elements using AMO LDAT.
ADD-LDPLN:LDP=0-X,DPLN=0,LROUTE=700,LAUTH=1; /* CO */
ADD-LDPLN:LDP=0-00-4989-X,DPLN=0,LROUTE=701,LAUTH=1; /*
Central office over tie line internat. */
office over tie line national */

Analogous to virtual node 1, you can configure virtual node 2 for open
numbering in the OpenScape 4000 numbering plan. Instead of the node
code, enter area code 96:
CHANGE-
CHANGE-
---------------------------------------------------------------------------
---------------------------------------------------------------------------
------+------+----+------+------------------------+------------------------
2 |ROW | A |ALL | 96 | - 
------+------+----+------+------------------------+------------------------
ROW | 2 | A |ALL | - | 96 

ADD-
KNDEF:NNO=4,TYPE=OWN,ISDNCC=49,ISDNAC=30,ISDNLC=611,ISDNSK=3,
ISDNUL=EXT,NODECD=96;NODECDSK=2;
• Set the own area code in WABE:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
• Set the digital trunk circuit TC2:
ADD-BUEND:NO=30,TGRP=44;
ADD-
• Set the digital tie trunk TT4:
Since ISDN connections can also come in via the tie trunk during transit, you
must make the ISDN-specific settings here as well. The node number does
not have to be specified since it is transferred in this protocol.
ADD-
With AMO RICHT, you can set the LCR routes according to the LCR
description in the same manner as virtual node 2 for the central office and the
tie line.
connections. Configure the outdial rules with AMO LODR in the exact same
manner as in Node 1 (outdial rules 10 to 13 in the example).
Using AMO LDAT, you can assign the outdial rules to the route elements as
shown in Node 1.
ADD-LDPLN:LDP=0-X,DPLN=0,LROUTE=700,LAUTH=1; /* CO */
ADD-LDPLN:LDP=0-00-4989-X,DPLN=0,LROUTE=701,LAUTH=1; /*
Central office over tie line internat. */
office over tie line national */
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Analogous to Node 1, you can configure Node 2 for open numbering in the
OpenScape 4000 numbering plan. Instead of the node code, enter area code
96:
CHANGE-
KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=OWN,DNNOL=ROW,NUMEXT=96;
CHANGE-
KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=ROW,DNNOL=OWN,NUMRED=96;
---------------------------------------------------------------------------
---------------------------------------------------------------------------
------+------+----+------+------------------------+------------------------
4 |ROW | A |ALL | 96 | - 
------+------+----+------+------------------------+------------------------
ROW | 4 | A |ALL | - | 96 
42.2.1.5 Source/destination-dependent number modification

in the ISDN or PNP numbering plan
Normally, format-dependent number modification is configured for the ETSI-

E.164 (ISDN) and PRIVATE (PNP) numbering plans using AMO KNPRE, AMO
KNFOR, and AMO KNDEF. The reason for this is the simpler configuration,
especially in case of later changes in the network.
In this example, the source/destination-dependent modification configured with

AMO KNMAT should also be set for the ISDN and PNP numbering plans (in the
example above, KNMAT was also used, but only for the UNKNOWN numbering
plan, i.e. the open, OpenScape 4000 specific numbering).
For better understanding, the example refers to the ISDN numbering plan. For
PNP, however, its numbering plan applies accordingly (with other exit codes,
prefixes, and codes in AMO KNDEF and AMO KNPRE).
IMPORTANT: Source/destination number modification with AMO KNMAT should

be applied for ISDN and PNP only in exceptional cases. Settings with KNMAT
prevent format-dependent number modification.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
NNO 3 NNO 1
PNNO 11
ISDN-CO TC 1 TT 1 PBX network
OpenScape
4000
Figure 54 Example: Source/destination-dependent number modification in

ISDN or PNP numbering plan

ISDNLC=611,ISDNSK=3,ISDNUL=EXT,NODECD=96;NODECDSK=2;
Even though only the node connection matrix is used for the modification of
the calling number in this example, you must set the exit codes and prefixes
with AMO KNPRE due to the conversation from explicit to implicit numbers
and vice versa:
CHANGE-ZAND:TYPE=ALLDATA,PNNO=1;
• Set of the digital trunk circuit TC:
ADD-
• Set of the digital tie trunk TT1:
The node number does not have to be specified if it is transferred in this
protocol.
ADD-
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
With AMO RICHT, you can set up LCR routes as shown in the examples
above.
With AMO LODR, you can configure the outdial rule for CO connections:
ADD-LODR:ODR=12,CMD=ECHO,FIELD=2; /* CO */
The outdial rule for tie line connections depends on whether the numbering is
open or closed (see Chapter 37, “LCR (Least Cost Routing)”).
The outdial rules are assigned to the route elements with AMO LDAT.
ADD-LDPLN:LDP=0-X,DPLN=0,LROUTE=...,LAUTH=1; /* CO */
In this example, the central office should always demand a national number
for the calling number. With AMO KNFOR, you thus make the following
settings:
ADD-KNFOR:DNNO=3,NPI=ISDN;,TONOUT=NATIONAL,SCRE=NOTDEF;
To be able to modify ISDN or PNP numbers using KNMAT, you must know
which format the number had before it was subjected to modification when
both incoming and outgoing:
– The number of the incoming calling number contains exit codes and
prefixes of the own node (Munich in the example; also see AMO KNPRE
and AMO TDCSU). It always has an international, implicit format (e.g.
00049008907224711 for connections from Munich, 0004900303864711
for connections from Berlin, and 00041318184711 for connections from
Zurich). With KNMAT, you can shorten the calling number by the
superfluous part so that a dialable number remains (e.g. 07224711,
00303864711, 00041318184711).
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
– The number of the outgoing calling number for connections from the own
node have the format entered in WABE (e.g. 4711). It is converted to an
explicit format via the modification. In this example, the central office in
Munich demands a national number so that the number is supplemented
with 89722.
IMPORTANT: If a certain format for a destination node is set using AMO

KNFOR, you must convert the number to this format using the modification in
AMO KNMAT.
IMPORTANT: In case of multi-level node numbers in a hierarchical network,

enter the modification in the corresponding levels of the KNMAT (e.g. short-
ening of 00049 to Level 2, 0089 to Level 1, 0722 to Level 0).
Commands:
CHANGE-KNMAT:NPI=ISDN,LEVEL=0,ONNOL=OWN,DNNO=3,NUMEXT=89722;
CHANGE-
KNMAT:NPI=ISDN,LEVEL=0,ONNOL=OWN,DNNOL=ROW,NUMEXT=4989722;
CHANGE-
KNMAT:NPI=ISDN,LEVEL=0,ONNO=3,DNNOL=OWN,NUMRED=000490089;
CHANGE-
KNMAT:NPI=ISDN,LEVEL=0,ONNOL=ROW,DNNOL=OWN,NUMRED=00049;
---------------------------------------------------------------------------
NODE MATRIX FOR NPI = ISDN, LEVEL = 0, OWN NNO = 1
---------------------------------------------------------------------------
------+------+----+------+------------------------+------------------------
1 | 3 | A |ALL | 89722 | - 
1 |ROW | A |ALL | 4989722 | - 
------+------+----+------+------------------------+------------------------
3 | 1 | A |ALL | | 000490089 
------+------+----+------+------------------------+------------------------
ROW | 1 | A |ALL | | 00049 
42.2.2 Multi-level network

The homogeneous OpenScape 4000/HiPath 4000 network in this example has a
three-level structure. It consists of four physical nodes (system) and three fictive
virtual nodes (trunk access points). The subscribers of all nodes can be reached
through all three numbering plans; i.e. they have individual numbers for each
numbering plan. This configuration can be preset when the OpenScape 4000/
HiPath 4000 network is to be set up as the central office. Figure 55 shows the
network topology.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
In this example, the setup of three numbering plans is shown parallel. In practice,
ISDN and PRIVATE are usually not configured together. The commands
belonging to the unconfigured numbering plan are simply omitted.
IMPORTANT: In a multi-level network, you must pay attention to the correct

modification conditions (MODCON) in the case of the KNMAT entries in the
ambiguous Levels 1 and 2!
ZAND PNNO should be configured in line with the KNDEF node (i.e. same
domain levels, but a different node ID), this is needed because ZAND PNNO is
used as a reference point for number modification under some circumstances.
For example:
Redirection numbers will be modified with AMO KNMAT for all levels when the
number is equal to the DAR length e.g. PSE/PSM codes - here number
modification assumes the call forward is made to a local service so all levels will
be modified with AMO KNMAT using ZAND PNNO as a reference point, to ensure
the correct full redirection number is returned. Redirection numbers that are un-
equal to a DAR result e.g. TIE+CODE, will only be modified for levels where there
is a KNMAT entry match, here number modification assumes the user has
programmed the call forward to a correct number meaning not all levels need to
be modified.
42.2.2.1 Three-level, open-numbered network/one-level

OpenScape 4000 specific numbering plan
In this example shown in Figure 55, the ISDN and PRIVATE numbers are also
three-level according to the rule following the three-level node numbers. In the
OpenScape 4000 specific numbering plan with tie line codes, however, where the
numbers should be as short as possible, numbering usually continues to be one-
level (e.g. one-level node code) if the numbers are unique within the network.
The local subscriber 4711 in Node 1-1-100, for example, is reached via the
numbers:
• 19-4711 in the UNKNOWN numbering plan, whereby:

19 = node code
• 0-00-49-89-722-4711 in the ISDN numbering plan (E.164), whereby:

0 = exit code in the ISDN numbering plan
00 = international prefix
49 = country code (CC)
89 = area code (AC)
722 = local destination code (LC)
• 15-11-39-719-6051-4711 in the PRIVATE (PNP) numbering plan, whereby:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
15 = exit code in the PRIVATE numbering plan

11 = Level 2 prefix
39 = Level 2 code (L2C)
719 = Level 1 code (L1C)
6051 = local destination code (LC)
UN: 27 -XXXX
PNP: 15-(11)39-(1)719-5116-XXXX
ISDN:0-(00)49-(0)89-636 -XXXX
UN: 37 -XXXX
PNP: 15-(11)39-(1)1573-634-XXXX
ISDN :0-(00)49-(0)211-734 -XXXX
NNO: 1-1-400
Level 2 PNNO: 1-1-444
PNODECD = 920
Level 1
Level 0 NNO:1-2-200
PNNO:1-2-222
PNODECD:921 Central office 
in Munich
NNO: 1-1-8
Central office  84
75 71
in Dusseldorf 1-2-79-1 1-2-103-0
NNO: 1-2-8 1-2-91-0
NNO: 1-1-100
NNO: 2-1-300 Trunk PNNO: 1-1-111
PNNO:2-1-333 groups PNODECD:919
PNODECD:922 74
1-2-79-0
Central office 4711

in Switzerland
NNO: 2-1-8
UN: 19 -XXXX
PNP: 15-(11)39-(1)719-6051-XXXX
ISDN:0-(00)49-(0)89-722 -XXXX
UN: 39 -XXXX
PNP: 15-(11)31-(1)0-536-XXXX
ISDN: 0-(00)41-(0)1-636-XXXX
Figure 55 Example: Three-level network, node numbers, and numbers
Abbreviations: 
UN = UNKNOWN, PNP = PRIVATE (numbering plan), XXXX = Station number 
(1 - 6-digit, up to 8 digits in special configurations)
Prefixes are specified in parentheses.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Configuration in physical node 1-1-111
IMPORTANT: Normally, you must only perform modifications in the UNKNOWN

numbering plan using KNMAT; the other numbers are controlled via format-
dependent modification.
• Set the node table (with virtual node code):

ADD-KNDEF:NNO=1-1-
100,TYPE=OWN,ISDNCC=49,ISDNAC=89,ISDNLC=722,ISDNSK=3,ISDNUL=E
XT,PNPL2C=39,PNPL1C=719,PNPLC=6051,PNPSK=4,
PNPUL=EXT,NODECD=19,NODECDSK=2;
CHANGE-KNDEF:NNO=1-1-100,DFLT=Y;
• Set the node prefix table for both NPIs:
ADD-KNPRE:NPI=PRIVATE,TON=LEVEL2,EXIT=15,PREFIX=11;
ADD-KNPRE:NPI=PRIVATE,TON=LEVEL1,EXIT=15,PREFIX=1;
ADD-KNPRE:NPI=PRIVATE,TON=LOCAL,EXIT=15;
ADD-KNPRE:NPI=ISDN,TON=INTERNAT,EXIT=0,PREFIX=00;
ADD-KNPRE:NPI=ISDN,TON=NATIONAL,EXIT=0,PREFIX=0;
ADD-KNPRE:NPI=ISDN,TON=SUBSCR,EXIT=0;
• Enter the own node number in the ZAND data:
CHA-ZAND:TYPE=ALLDATA,PNNO:=1-1-111;
• Set the own physical code in WABE and in ZAND data:
CHA-ZAND:TYPE=ALLDATA,PNODECD=919;
• Set the CO and PNP exit codes in WABE:
ADD-WABE:CD=0,DAR=TIE; /* CO */
• Set tie line codes for NPI=UNKNOWN in WABE (for other nodes):
• Set trunk groups for direct CO connection:
ADD-BUEND:TGRP=71,NAME="AMT-DIU-S2 ",NO=60,RSV=NO;
• Set COT with LWNC for the central office:
ADD-
COT:COTNO=37,PAR=NLCR&ANS&COTN&NTON&IEVT&ICZL&IIDL&IVAC&INAU&
ITB&IDND&IFR&IDIS&LWNC,INFO="COT FOR CO";
• Set the trunk circuit:
ADD-TDCSU:OPT=NEW,PEN=1-2-103-00,COTNO=37,COPNO=56,COS=1,
LCOSV=1,LCOSD=1,DESTNO=8,PROTVAR=EDSGER,BCNEG=Y,ISDNIP=00,
ISDNNP=0,PNPL2P=11,PNPL1P=1,NNO=1-1-8,DEV=S2COD,TGRP=71,
BCHAN=1&&30,BCGR=1,INS=Y,LWPAR=1;
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
• Set the tie trunks:

ADD-TDCSU:OPT=NEW,PEN=1-2-079-00,COTNO=20,COPNO=0, COS=1,
LCOSV=1,LCOSD=1,
PROTVAR=ECMA1,DEV=S2CONN,TGRP=74,BCHAN=1&&30,BCGR=1,ACT=Y,LWP
AR=2,
SEGMENT=2;
LCOSV=1,LCOSD=1,
AR=2,
SEGMENT=2;
LCOSV=1,LCOSD=1,
AR=2,
SEGMENT=2;
• You must set the node connection matrix only for the UNKNOWN numbering
plan according to the rules in Section 42.2.1.5, “Source/destination-
dependent number modification in the ISDN or PNP numbering plan”.
CHA-
CHA-
---------------------------------------------------------------------------
NODE MATRIX FOR NPI = UNKNOWN, LEVEL = 0, OWN NNO = 1-1-100
---------------------------------------------------------------------------
------+------+----+------+------------------------+------------------------
100 |ROW | A |ALL | 19 | - 
------+------+----+------+------------------------+------------------------
ROW | 100 | A |ALL | - | 19 
• Set the node format table for CO node 1-1-8, which expects the calling
number in international format and the screening indicator NETWPROV
(network provided, i.e. the number is checked by the network):
ADD-KNFOR:DNNO=1-1-8,NPI=ISDN,TONOUT=INTERNAT,SCRE=NETWPROV;
• Set the CO route with LCR:
ADD-
RICHT:MODE=LRTENEW,LRTE=20,LSVC=ALL,NAME="CO_S2",TGRP=71,DNNO
=1-1-8,
• Set the tie line routes, outdial rules, route elements, and dial pattern plan in
LCR for the ISDN numbering plan:
/* To Node 2-1-300 */
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
ADD-
RICHT:MODE=LRTENEW,LRTE=700,LSVC=ALL,NAME=ISDN,TGRP=74,DNNO=2
-0-0;
ADD-LODR:ODR=10,CMD=TON,TON=INTERNAT;
ADD-LDPLN:LDP=0-W-00-41-X,LROUTE=700,LAUTH=1;
/* To Node 1-2-200 */
ADD-
-2-0; 
ADD-
-2-0;
ADD-LODR:ODR=11,CMD=TON,TON=NATIONAL;
ADD-LDPLN:LDP=0-W-00-49211-X,LROUTE=707,LAUTH=1;
/* To Node 1-1-400 */
ADD-
-1-400; 
ADD-
-1-400; 
ADD-
-1-400;
ADD-LODR:ODR=16,CMD=TON,TON=SUBSCR;
ADD-LDPLN:LDP=0-W-636-X,LROUTE=712,LAUTH=1;
/* On the own node, LCR recognizes own node, TGRP ignored */
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
• The configuration for a route on the own node has changed due to the virtual
node concept. As before, one route must be configured, but the recognition
of a (logical) loop no longer takes place using the node number, but rather
using a route attribute RERTEINT = Reroute Internal.
ADD-
RICHT:MODE=LRTENEW,LRTE=706,LSVC=ALL,NAME=OWN,TGRP=84,DNNO=1-
1-100;
LATTR=RERTEINT
ADD-LDPLN:LDP=0-W-004989722-X,LROUTE=706,LAUTH=1; /*
International */
ADD-LDPLN:LDP=0-W-089722-X,LROUTE=706,LAUTH=1; /* National */
ADD-LDPLN:LDP=0-W-722-X,LROUTE=706,LAUTH=1; /* Subscriber */
LCR for the PRIVATE numbering plan:
/* To Node 2-1-300 */
ADD-RICHT:MODE=LRTENEW,LRTE=600,LSVC=ALL,NAME=ISDN,TGRP=74,
DNNO=2-0-0;
ADD-LODR:ODR=20,CMD=NPI,NPI=PRIVATE;
ADD-LODR:ODR=20,CMD=TON,TON=LEVEL2;
ADD-LDPLN:LDP=15-11-31-X,LROUTE=600,LAUTH=1;
/* To Node 1-2-200 */
DNNO=1-2-0;
DNNO=1-2-0;
ADD-LODR:ODR=21,CMD=TON,TON=LEVEL1;
ADD-LDPLN:LDP=15-11-391573-X,LROUTE=607,LAUTH=1;
ADD-LDPLN:LDP=15-1-1573-X,LROUTE=608,LAUTH=1;
/* To Node 1-1-400 */
ADD-
-1-400; 
ADD-
-1-400; 
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
ADD-
-1-400;
ADD-LODR:ODR=26,CMD=TON,TON=LOCAL;
/* On the own node, LCR recognizes own node, TGRP ignored */
ADD-RICHT:MODE=LRTENEW,LRTE=606,LSVC=ALL,NAME=OWN,TGRP=84,
DNNO=1-1-100;
ADD-LDPLN:LDP=15-11397196051-X,LROUTE=606,LAUTH=1;
ADD-LDPLN:LDP=15-17196051-X,LROUTE=606,LAUTH=1;
LCR for the UNKNOWN numbering plan:
/* To Node 2-1-300 */
ADD-
RICHT:MODE=LRTENEW,LRTE=101,LSVC=ALL,NAME=UNKNOWN,TGRP=74,DNN
O=2-0-0;
ADD-LDAT:LROUTE=101,LSVC=ALL,LVAL=1,TGRP=74,ODR=6;
ADD-LDPLN:LDP=39-X,LROUTE=101,LAUTH=1;
/* To Node 1-2-200 */
ADD-
O=1-2-0;
/* To Node 1-1-400 */
ADD-
O=1--1-400;
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Configuration in other nodes

The configuration of the other nodes is performed in the same manner as that for
Node 1-1-100. If (in exceptional cases) you do not want to configure the format-
dependent modification for the ISDN and PRIVATE numbering plans, set the
node connection matrix following Section .
42.2.2.2 Closed numbering of network in OpenScape 4000

specific numbering plan
In the following example, the subscribers on Level 0 in Munich should be closed-

numbered in the OpenScape 4000 specific numbering plan. According to
definition, ISDN and PRIVATE are always open-numbered. For this reason, the
configuration for ISDN and PRIVATE remains unchanged for Section . Again, it
should be based in the network topology shown in Figure 55. The numbers are
shown in the following table:
Node Number Number ISDN Number PRIVATE

UNKNOWN
1-1-100 [30]-XXXX 0-(00)49-(0)89-722-XXXX 15-(11)39-(1)719-6051-XXXX
30=area code
1-1-400 [30]-XXXX 0-(00)49-(0)89-636-XXXX 15-(11)39-(1)719-5116-XXXX
30=area code
1-2-200 37-XXXX 0-(00)49-(0)211-734-XXXX 15-(11)39-(1)1573-634-XXXX
2-1-300 39-XXXX 0-(00)41-(0)1-636-XXXX 15-(11)31-(1)0-536-XXXX

Here, only the differences in comparison with Section 42.2.2.1, “Three-level,
open-numbered network/one-level OpenScape 4000 specific numbering plan”
are listed.

ADD-KNDEF:NNO=1-1-
100,TYPE=OWN,ISDNCC=49,ISDNAC=89,ISDNLC=722,ISDNSK=3,ISDNUL=E
XT,PNPL2C=39,PNPL1C=719,PNPLC=6051,PNPSK=4,PNPUL=EXT,NODECD=3
0,NODECDSK=2;
• Set the own area code for UNKNOWN in WABE:
• Set the tie line code for Switzerland (NPI=UNKNOWN) in WABE:
• Set the tie line for Dusseldorf (NPI=UNKNOWN) in WABE:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
• Set closed-numbered subscribers in WABE:
ADD-WABE:CD=001,DAR=NETRTE,CHECK=NO;
ADD-WABE:CD=2400&&2499,DAR=STN,DESTNO=4,CHECK=NO; /*
Subscriber in 1-1-400 */
ADD-WABE:CD=4000&&4799,DAR=STN,DESTNO=0,CHECK=NO; /*
Subscriber in own node */
IMPORTANT: The number within an area must always be set fully qualified
in AMO WABE (e.g. 43xxx is not valid!).
• The node connection matrix is to be set for the UNKNOWN numbering plan.
You can see that the area code is treated like a normal node code in AMO
KNMAT.
CHA-
KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=OWN,DNNOL=ROW,MODCON=OUT,NUME
XT=#####;
CHA-
KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=ROW,DNNOL=OWN,MODCON=IN&TRANS
I,NUMRED=#####;
/* Open for Node 2-1-300 */
ADD-
O=2-0-0;
/* Open for Node 1-2-200 */

ADD-
O=1-2-0;
/* Closed for Node 1-1-400 */

ADD-
RICHT:MODE=CD,LRTE=103,CD=001,CPS=0,SVC=ALL,NAME=LCR_VERDECKT
,TGRP1=84,DESTNO=4,DNNO=1-1-400;
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification

The setting of the other nodes can be derived from Node 1-1-111.
42.2.2.3 Open-numbered network, three-level, OpenScape

4000 specific numbering plan
This configuration is based on Figure 55. The UNKNOWN numbering plan (i.e.
dialing with tie line codes) has three levels in this example, in contrast to Section
. For ISDN and PRIVATE, as well, not the format-dependent, but the KNMAT
modification should be configured.
IMPORTANT: This example should only be used to show the special cases of
number modification.
In the following example, the network topology correspond with the example in
Section . The UNKNOWN numbers, however, have one level there:
Node Number Number ISDN Number PRIVATE

UNKNOWN
1-1-100 29-36-19-XXXX 0-(00)49-(0)89-722-XXXX 15-(11)39-(1)719-6051-XXXX
1-1-400 29-36-27-XXXX 0-(00)49-(0)89-636-XXXX 15-(11)39-(1)719-5116-XXXX
1-2-200 29-26-37-XXXX 0-(00)49-(0)211-734-XXXX 15-(11)39-(1)1573-634-XXXX
2-1-300 18-37-39-XXXX 0-(00)41-(0)1-636-XXXX 15-(11)31-(1)0-536-XXXX

Here, only the differences in comparison with Section 42.2.2.1, “Three-level,
open-numbered network/one-level OpenScape 4000 specific numbering plan”
are listed.

Please observe that, in the case of a multi-level UNKNOWN numbering plan,
only the lowest level is in AMO KNDEF. The reason for the different AMO
KNDEF administration between explicit numbering plans (all levels must be
described in AMO KNMAT) and the UNKNOWN numbering plan (only the
lowest level must be described) is as follows: For explicit numbering plans,
the codes for the modification are taken from AMO KNDEF, but from AMO
KNMAT for UNKNOWN. The number of skip digits is taken from AMO KNDEF
for both numbering plans. The skip digits, on the other hand, are on the lowest
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
level of every numbering plan. If a called part number is analyzed, the number
of the skip digits is thus determine in which the code is sought in AMO KNDEF
at the lowest level and the respective skip digits are read.
ADD-KNDEF:NNO=1-1-100,TYPE=OWN,
ISDNCC=49,ISDNAC=89,ISDNLC=722,ISDNSK=3,ISDNUL=EXT,
PNPL2C=39,PNPL1C=719,PNPLC=6051,PNPSK=4,PNPUL=EXT,
NODECD=19,NODECDSK=2;
• Set the own node code for UNKNOWN in WABE:
ADD-WABE:CD=19,DAR=OWNNODE; /* Level 0 node code
(Hofmannstraße)*/
ADD-WABE:CD=36,DAR=OWNNODE; /* Level 1 area code (Munich)*/
ADD-WABE:CD=29,DAR=OWNNODE; /* Level 2 area code (Germany)*/
• Set the own physical node code in WABE:
ADD-WABE:CD=919,DAR=OWNNODE; /* Level 0 node code
(Hofmannstraße)*/
• Set tie line codes for UNKNOWN in WABE:
ADD-WABE:CD=18,DAR=TIE; /* To 2-1-300 */
ADD-WABE:CD=26,DAR=TIE; /* to 1-2-200 */
ADD-WABE:CD=27,DAR=TIE; /* to 1-1-400 */
• Configure the node connection matrix for the UNKNOWN, ISDN, and
PRIVATE numbering plans (three levels for UNKNOWN here as well).
In the process, observe that the new logical specification of the digits to be
supplemented/shortened is only possible at Level 0. On higher levels, the
own code must still be determined by hand. You may of course determine the
own code on Level 0 by hand as shown here.
CHA-
XT=19,;
CHA-
I,NUMRED=19;
CHA-
XT=36;
CHA-
I,NUMRED=36;
CHA-
XT=29;
CHA-
I,NUMRED=29;
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
CHA-
KNMAT:NPI=ISDN,LEVEL=0,ONNOL=OWN,DNNOL=ROW,MODCON=OUT,NUMEXT=
722,;
CHA-
KNMAT:NPI=ISDN,LEVEL=0,ONNOL=ROW,DNNOL=OWN,MODCON=IN&TRANSI,N
UMRED=0722;
CHA-
89;
CHA-
UMRED=0089;
CHA-
49;
CHA-
UMRED=00049;
CHA-
KNMAT:NPI=PRIVATE,LEVEL=0,ONNOL=OWN,DNNOL=ROW,MODCON=OUT,NUME
XT=6051,;
CHA-
KNMAT:NPI=PRIVATE,LEVEL=0,ONNOL=ROW,DNNOL=OWN,MODCON=IN&TRANS
I,NUMRED=156051;
CHA-
XT=719;
CHA-
I,NUMRED=151719;
CHA-
XT=39;
CHA-
I,NUMRED=151139;
/* To Node 2-1-300 */
ADD-
O=2--0-0;
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
/* To Node 1-2-200 */
ADD-
O=1--2-0;
ADD-LODR:ODR=7,CMD=OUTPULSE,DGTS=29;
/* To Node 1-1-400 */
ADD-
O=1--1-400;

The setting of the other nodes can be derived from Node 1-1-111.
42.2.3 Open-numbered heterogeneous network

A heterogeneous network is a mixed network made of OpenScape 4000 nodes
and nodes or subnets from earlier versions or nodes of other manufacturers.
42.2.3.1 Heterogeneous network with nodes that know only

one node number
If you network a system which doesn’t differentiate between virtual and physical
NNO with OpenScape 4000, you can use the own node number of the older
partner as both virtual and physical destination nodes for the configuration of the
OpenScape 4000 switch.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
42.2.3.2 Heterogeneous network with nodes that already

modify
In this case, an OpenScape 4000/HiPath 4000 network (surrounded by a dotted

line in Figure 56) is networked with nodes of the older versions Hicom 300 E V2.0
or Hicom 300 V3.4.
For all trunks leading to systems of the versions Hicom 300 V3.4, the COT
parameter LINO (line with implicit numbers, see Section 42.1.2.2, “Explicit and
implicit phone numbers”) must be set. You must set the COT parameter LWNC
(line without node number) for tie trunks TT1/2 only if the Hicom 300 V3.3/Hicom
300 V3.4 network has already used the same node number (in a one-level
network) or always in a multi-level network.
OpenScape NNO 11 (1-11) NNO 2

PNNO 1 H300-V3.4
4000
H300-V3.4
OpenScape TT x TT 1 TT 2 TT y
4000 H300-V3.4
OpenScape H300-V3.4
OpenScape H300 V3.4
4000
4000 H300-V3.4
Figure 56 Example: Heterogeneous one-level or multi-level network with

nodes that already modify
1. Multi-level OpenScape 4000 network or one-level network with ambiguous

node numbers
a) Configuration in physical node PNNO=1 (or 1-1 for in case of two levels):
In OpenScape 4000 node PNNO=1 (1-1 for multi levels), define a COT:
ADD-COT:COTNO=12,PAR=LWNC&LINO&...;
Set up a route to Hicom 300 V3.4, e.g. in the multi-level network in this
case. Node 2 must also be adapted to two levels in the same manner as
Node 1-1, i.e. the fictive node number obtains a value of 2-0 ( 1-2 is also
possible).
ADD-
RICHT:MODE=LRTENEW,LRTE=101,LSVC=ALL,NAME=UNKNOWN,TGRP=74,
DNNO=2-0;
b) Configuration in physical node NNO=2:
In node NNO=2, you define a COT and a route. The fictive destination
node 444 designates e.g. the "real" Node 1 in case, for example, Node 1
already exists in the Hicom 300 V3.4 subnet or, in case of multi levels,
Node 1-1. Node number 444 may not exist in the Hicom 300 V3.4 subnet.
ADD-COT:COTNO=12,PAR=LWNC&...;
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
ADD-
DNNO=444;
2. One-level network with unambiguous node numbers:
a) Configuration in physical node PNNO=1:

In OpenScape 4000 node NNO=11, you define a COT and a route:
ADD-COT:COTNO=12,PAR=LINO&...;
ADD-
DNNO=2;
b) Configuration in physical node NNO=2:
In node NNO=2, no particular COT parameter is required. As usual, you
set up a route to destination node 1 (via LCR here):
ADD-
DNNO=1;
Setting the tie trunks:
The COT (class of trunk) number is to be set in TT1/2. You do not enter a fictive
node number.
ADD-TDCSU:OPT=NEW,DEV=S2CONN,COTNO=12,...;
IMPORTANT: The COT parameter LWNC always functions in an outgoing

direction. If the parameter is set, no node numbers are sent to the partner node.
In this case, the source node number, however, can be reconstructed using the
digit analysis. Reconstruction reduces the performance. For this reason, multi-
level networks should be configured only if absolutely necessary.
42.2.3.3 Heterogeneous network with nodes that do not modify
In this case, an OpenScape 4000/HiPath 4000 network (surrounded by a dotted

line in Figure 57) is networked with nodes of the older versions Hicom 300 V3.4
or systems of other manufacturers.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
OpenScape 4000 NNO 1-100

External node External node
PNNO: 1-1
OpenScape 4000
External node
TT x TT 1
OpenScape 4000
OpenScape 4000
OpenScape External node
4000 Assigned: 1-200
OpenScape 4000
Figure 57 Example: Heterogeneous network with nodes that do not modify
The external network is assigned its own area or node number. In the example
above, the external network is addressed from the OpenScape 4000 subnet with
1-200. Node number 1-200 is used for the configuration of the LCR routes and for
number modification in AMO KNMAT.
Configuration of tie trunk TT1:

Define a COT with parameter LINO (line with implicit number) and LWNC (line
without node number). The parameter DFNN (use preset node number in the
incoming direction) can be set if no reconstruction of the node numbers is desired
using dial analysis. A single node number (that is set in AMO TDCSU, TACSU) is
then assigned to the external network and the numbers can no longer be modified
for each external node.
ADD-COT:COTNO=12,PAR=LINO&LWNC&DFNN&...;
Assign this COT to the tie trunk and set the fictive node number:
ADD-TDCSU:OPT=NEW,DEV=S2CONN,COTNO=12,NNO=1-200,...;
Routes are also set up for this fictive destination node number:
ADD-
RICHT:MODE=LRTENEW,LRTE=103,LSVC=ALL,NAME=UNKNOWN,TGRP=84,DNNO=1
-200;
Configuration of the node connection matrix:

If, for example, the external system reaches Code 77 from the viewpoint of the
virtual node 1-100, set the following additional digits in Node 1-1:
CHANGE-KNMAT:NPI=UNKNOWN,LEVEL=0,ONNO=200,DNNOL=OWN,NUMEXT=77;
Code 77 is thus placed before the numbers coming from the external network at
the entry node. In all other nodes, no modification is set for the external network.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification

OpenScape 4000 specific numbering plan, overlapping virtual
nodes
Munich CO
NNO: 1-1-8
CO connection with CO connection with

49 89 722 49 89 636
PNNO: 1-1-91 PNNO: 1-1-92

PNODECD: 919 PNODECD: 927
NNO: 1-1-2
NODECD: 27
NNO: 1-1-1
NODECD: 19
1715 1716
UN: 19 -XXXX
ISDN:0-(00)49-(0)89-722 -XXXX
2244 2245
UN: 27 -XXXX
ISDN :0-(00)49-(0)89-636 -XXXX
Figure 58 Before the move (non-overlapping virtual nodes)
What is new about this example is the feature of overlapping node. In Figure
Figure 58, the initial state is shown. The normal configuration still exists with a 1:1
assignment from the physical to the virtual node.
In the next Figure 58, Subscriber 1716, which was originally configured in the
system with PNNO 1-1-91, moved within the system with PNNO 1-1-92. The
subscriber wanted to keep his or her fully qualified number (not just the
extension). The same applies for Subscriber 2244, who was originally configured
in 1-1-92 and then moved to 1-1-91.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Munich CO
NNO: 1-1-8

49 89 722 49 89 636
PNNO: 1-1-91 PNNO: 1-1-92

NNO: 1-1-2
NODECD: 27
NNO: 1-1-1
NODECD: 19
UN: 19 -XXXX
ISDN:0-(00)49-(0)89-722 -XXXX
1715 1716
UN: 27 -XXXX
ISDN :0-(00)49-(0)89-636 -XXXX

2244 2245
Figure 59 Overlapping Nodes
Abbreviations: 
UN = UNKNOWN, xxxx = station number (1 - 6 digits, 8 digits in special
configurations). Prefixes are specified in parentheses.
In this example, the ISDN numbers are also three-level according to the rule
following the three-level node numbers. In the OpenScape 4000 specific
numbering plan with tie line codes, however, where the numbers should be as
short as possible, numbering usually continues to be one-level (e.g. one-level
node code).
In this example, physical nodes 1-1-91 and 1-1-92 form an overlapping area since
there are overlapping virtual nodes between them. If the extensions in the
overlapping area are unambiguous, a simplified configuration can be used that
have performance advantages in comparison with the configuration shown in the
next chapter. Such a (sub)net could also be closed-numbered and the
configuration also works with a mixed format of closed and open numbering.
Configuration in physical node 1-1-91 before the move

Before the move, the following configuration was present:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Set the node table:

All subsequently configured subscribers are assigned this virtual node by default
(due to DFLT=Y). Here, however, is the command by means of which you can
explicitly assign a subscriber a virtual NNO. Subscribers 1715 and 1716,
however, are both still in the same virtual nodes:
CHANGE-SDAT:STNO=1715,TYPE=DATA1,NNO=1-1-1;
CHANGE-SDAT:STNO=1716,TYPE=DATA1,NNO=1-1-1;
Both subscribers are normally set up and configured in WABE.
Set the node prefix table for NPI=ISDN:

Enter the own physical node number and code in the ZAND data:
CHANGE-ZAND:TYPE=ALLDATA,PNNO=1-1-91,PNODECD=919;
Set the own codes in WABE:
ADD-WABE:CD=919,DAR=OWNNODE;/*PNODECD*/
ADD-WABE:CD=19,DAR=OWNNODE;/*NODECD*/
Set CO exit codes in WABE:
Set tie line codes for UNKNOWN in WABE:
You can set up the trunk groups for direct CO connection, the trunk circuit, and
the tie trunk as show in the previous examples.
You must set the node connection matrix only for the UNKNOWN numbering plan
according to the rules in Section .
CHA-KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=OWN,DNNOL=ROW,NUMEXT=#####;
CHA-KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=ROW,DNNOL=OWN,NUMRED=#####;
---------------------------------------------------------------------------
---------------------------------------------------------------------------
------+------+----+------+------------------------+------------------------
1 |ROW | A |ALL | 19 | - 
------+------+----+------+------------------------+------------------------
ROW | 1 | A |ALL | - | 19 
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Set the node format table for CO node 1-1-8, which expects the calling number in
international format and the screening indicator NETWPROV (network provided,
i.e. the number is checked by the network):
Setting the CO route with LCR:
ADD-RICHT:MODE=LRTENEW,LRTE=20,LSVC=ALL,NAME="AMT_S2",TGRP=71,
DNNO=1-1-8; 
ADD-LODR:ODR=20,CMD=END; 
ADD-LDAT:LROUTE=20,LSVC=ALL,LVAL=1,TGRP=71,ODR=20; 
Set the tie line routes, outdial rules, route elements, and dial pattern plan in LCR
for the ISDN numbering plan. Here, only the AMOs and parameters important for
this example are shown:
/* To remote Node 1-1-2 with three-level ISDN */
ADD-RICHT:MODE=LRTENEW,LRTE=203,...,DNNO=1-1-2;/* For dialing in
int. format */
nat. format */
sub. format*/
The outdial rule is to be formulated according to the desired format of the called
party. In general, the international format is used in the ISDN numbering plan so
that different outdial rules are required for the three dialing formats.
ADD-LODR:ODR=23,NPI=ISDN,TON=INTERNAT;
ADD-LDAT:LROUTE=203,.., ODR=23;
ADD-LDPLN:LDP=0-W-00-4989636-X,LROUTE=203,LAUTH=1;/* For dialing

in international format*/
ADD-LDPLN:LDP=0-W-0-89636-X,LROUTE=204,LAUTH=1;/* For dialing in
nat. format*/
ADD-LDPLN:LDP=0-W-636-X,LROUTE=205,LAUTH=1;/*For dialing in sub.
format*/
/* To own node 1-1-1 with three-level ISDN */
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Attention: As long as no subscriber has moved, these entries are optional!

They make it possible for subscribers to reach other subscribers in their own
node not just through their own extension, but also using an international,
national, or subscriber number without using the public central office in the
process.
ADD-RICHT:MODE=LRTENEW,LRTE=101,...,DNNO=1-1-1; /* For dialing
in ISDN format*/
With the RERTEINT attribute, you can mark a route element as a route element
that leads to the own node from OpenScape 4000 and higher. No line is occupied
(the trunk group specification is ignored), only the outdial rule is executed and the
dial analysis is restarted. 
The outdial rule must be set up in such a way that only the extension is resent to
the dial analysis.
ADD-LDAT:LROUTE=101,.., ODR=26,LATTR=RERTEINT;

for the UNKNOWN numbering plan:
/* To remote Node 1-1-2 with one-level UNKNOWN */
ADD-RICHT:MODE=LRTENEW,LRTE=206,LSVC=ALL,NAME="UNKNOWN 1-1-
2",TGRP=74,
DNNO=1-1-2;
Configuration in physical node 1-1-92 before the move

Set the node table:
All subsequently configured subscribers are assigned this virtual node by default
(due to DFLT=Y). Here, however, is the command by means of which you can
explicitly assign a subscriber a virtual NNO. Subscribers 2244 and 2245,
however, are both still in the same virtual nodes:
Set the node prefix table:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Enter the own physical node number and code in the ZAND data:
AE-ZAND:TYPE=ALLDATA,PNNO=1-1-92,PNODECD=927;
Set the own codes in WABE:
ADD-WABE:CD=927,DAR=OWNNODE;/*PNODECD*/
ADD-WABE:CD=27,DAR=OWNNODE; /*NODECD*/
Set tie line codes for UNKNOWN in WABE:
according to the rules in Section 42.2.1.5, “Source/destination-dependent
number modification in the ISDN or PNP numbering plan”.
---------------------------------------------------------------------------
---------------------------------------------------------------------------
------+------+----+------+------------------------+------------------------
1 |ROW | A |ALL | 27 | - 
------+------+----+------+------------------------+------------------------
ROW | 1 | A |ALL | - | 27 
Set the node format table for CO node 1-1-8, which expects the calling number in
international format and the screening indicator NETWPROV (network provided,
d.h. the number is checked by the network):
Setting the CO route with LCR:
ADD-RICHT:MODE=LRTENEW,LRTE=20,LSVC=ALL,NAME="AMT_S2",TGRP=71,
DNNO=1-1-8;
for the ISDN numbering plan. Here, only the AMOs and parameters important for
this example are shown:
/* To remote Node 1-1-1 with three-level ISDN */
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
ADD-RICHT:MODE=LRTENEW,LRTE=103,...,DNNO=1-1-1;/*für Wahl im
int. Format*/
nat. format*/
ADD-RICHT:MODE=LRTENEW,LRTE=105,...,DNNO=1-1-1;/*For dialing in
sub. format*/


ADD-LDPLN:LDP=0-W-00-4989722-X,LROUTE=103,LAUTH=1;/* For dialing
in int. format*/
ADD-LDPLN:LDP=0-W-0-89722-X,LROUTE=104,LAUTH=1;/* For dialing in
nat. format*/
ADD-LDPLN:LDP=0-W-722-X,LROUTE=105,LAUTH=1;/*For dialing in sub.
format*/
/* To own Node 1-1-2 with three-level ISDN */
Attention: As long as no subscriber has moved, these entries are optional!
You thus make it possible for subscribers to reach other subscribers in their own
node not just through their own extension, but also using an international,
national, or subscriber number without using the public central office in the
process.
ADD-RICHT:MODE=LRTENEW,LRTE=201,...NAME="REROUTE 1-1-1",DNNO=1-
1-2;
With the RERTEINT attribute, you can mark a route element as a route element
that leads to the own node from OpenScape 4000 and higher. No line is occupied
(the trunk group specification is ignored), only the outdial rule is executed and the
dial analysis is restarted:
ADD-LDAT:LROUTE=201,.., ODR=26,LATTR=RERTEINT;
for the UNKNOWN numbering plan:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
/* To remote Node 1-1-1 with one-level UNKNOWN */

ADD-RICHT:MODE=LRTENEW,LRTE=106,LSVC=ALL,NAME=UNKNOWN,TGRP=74,
DNNO=1-1-1,PDNNO=1-1-92;
Changes in the Configuration after the Move

For the move from 1716 to physical node 1-1-92, you must make the following
changes:
• In physical node 1-1-91:

The WABE entry for 1716 as a subscriber in the own system must be
changed on the external system after the subscriber configuration was
deleted. The setup takes place using destination numbers as in the case of
closed numbering.
Routes that have a destination node number of 1-1-1 must be redefined,
whereby the newly arising node portion on physical node 1-1-92 is meant.
These routes must be assigned to route elements that occupy the tie line
route.
– If you would like to give internal subscribers the choice of ISDN numbers
in international, national, or subscriber format, the existing dial plan must
be expanded for the own ISDN codes. Subscriber 1716 should be
removed from the reroute internal configuration and a subscriber-specific
entry that leads to the partner node should be made for 1716. Without this
entry, a reroute internal run with renewed dial analysis would also lead to
this result, but this loop can be prevented and thus a higher performance
can be achieved.
ADD-RICHT:MODE=LRTENEW,LRTE=103,...,DNNO=1-1-1;PDNNO=1-1-
92;
ADD-LDPLN:LDP=0-W-00-4989722-1716,LROUTE=103,LAUTH=1;
ADD-LDPLN:LDP=0-W-722-1716,LROUTE=103,LAUTH=1;
The specification of the fields of the dial pattern is oriented on the
requirements of the outdial rule and thus on the desired format of the
called party.
In the following, a closed numbering is set up in the physical node 1-1-91
for the stations that moved (all subscribers within the virtual node 1-1-1
can thus reach each other by dialing the number).
ADD-RICHT:MODE=CD,LRTE=207,CD=0101,SVC=ALL,
NAME="NODE 1-1-1",DESTNO=1,DNNO=1-1-1,PDNNO=1-1-92;
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
CHANGE-WABE:CD=1716,DESTNO=1;
• In physical node 1-1-92:
– The virtual node 1-1-1 extends to this physical node and must be made
known. The same configuration of NNO 1-1-1 as in physical node 1-1-91
is to be used.
This node is added to 1-1-2, but remains 1-1-2.
NODECD=19,NODECDSK=2;
– Subscriber 1716 must be set up with a subscriber AMO as usual, but the
node to which he or she belongs must then be changed so that the
modification can be properly performed for this subscriber:
– If Subscriber 1716 should also be reached with his or her ISDN number
in international, national, or subscriber format without a CO connection
being established, reroute internal should be used:
ADD-LDAT:LROUTE=101,.., ODR=26,LATTR=RERTEINT;/* already
set up */
ADD-LDPLN:LDP=0-W-7-22-1716,LROUTE=101,LAUTH=1;
– The same applies to the one-level OpenScape 4000 numbering plan:
ADD-RICHT:MODE=LRTENEW,LRTE=102,LSVC=ALL,NAME="REROUTE 1-
1-1",TGRP=74,
DNNO=1-1-1,PDNNO=1-1-92;
ADD-
LDAT:LROUTE=102,LSVC=ALL,LVAL=1,TGRP=74,ODR=10,LATTR=RERTE
INT;
ADD-LDPLN:LDP=19-1716,LROUTE=102,LAUTH=1;
Adapting the outdial rule for the existing digit pattern
19-X:
CHANGE-LDAT:LROUTE=106,LSVC=ALL,LRTEL=1,ODR=10;
You can configure the move of Subscriber 2244 to the other system
analogously.
You must now set the node connection matrix for the UNKNOWN numbering plan
again according to the rules in Section 42.2.1.5, “Source/destination-dependent
number modification in the ISDN or PNP numbering plan” as follows:
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
IMPORTANT: The moved subscriber now uses the LCR and, usually, the CO
route located in the new system.
(For the carrier/central office, it is possible to request the ""No Screening Options"
feature to specify the appropriate "calling party number" in the outgoing direction
as well.)

OpenScape 4000 specific numbering plan, overlapping virtual
nodes with ambiguous extensions
This example should show that a network with overlapping nodes can also only
be configured with open numbering. This has the advantage that the extensions
do not have to be unique3 throughout the network.
IMPORTANT: Rule: Extensions, however, have to be unique for each physical

node and each virtual node!
• The following configuration is thus valid (with Station: 4711):
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Munich CO
NNO: 1-1-8

+ 49 89 722 xxxx + 49 89 636 xxxx
PNNO: 1-1-91 PNNO: 1-1-92

NNO: 1-1-2
4711
NODECD: 27
NNO: 1-1-1
NODECD: 19
4711
NNO: 1-1-1
UN: 19 -XXXX
ISDN:0-(00)49-(0)89-722 -XXXX
1715 1716
NNO: 1-1-2
UN: 27 -XXXX
ISDN :0-(00)49-(0)89-636 -XXXX
2244 2245
Figure 60 Non-unique extensions in the network
• The configuration of 4711 to VNNO 1-1-2 and PNNO: 1-1-91 or of 4711 to

VNNO 1-1-1 and PNNO 1-1-92, on the other hand, is not valid.
Both subscribers 4711 (in NNO 1-1-1 and PNNO 1-1-91 and in NNO 1-1-2 and
PNNO 1-1-92) are permissible, but not unique throughout the network!
Uniqueness is achieved only with their ISDN L0 codes. This leads us to the
concept of the lowest unique level. The lowest unique level of the ISDN number
is the subscriber level. This effects calls from other networks, for example. Let’s
assume that there is a further network, e.g. with nodes in other areas, only via
Node 1-1-91 (1-1-92 can only be reached as a transit node via 1-1-91). The called
party may not be shortened below the lowest unique level. The called party 49 89
636 4711 would otherwise be incorrectly identified, namely as a subscriber of the
transit node.
The configuration is based on the basic principle that the digit analysis can
provide no general statement as to whether a number that consists of more than
one extension refers to an internal or external destination. For this reason, the
first digit analysis procedure always refers to TIE to evaluate the dial plan. TIE
can analyze the entire number and process the number and transfer a second
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
digit analysis procedure in case of the recognition of an internal destination or

determine an external destination. 
Losses in performance, however, occur due to this loop.

Due to non-unique extensions, a change must be made in AMO KNDEF. The
ISDN unique level must be raised from the station to the subscriber. From the
point of view of the software, you thus prevent the called party from being
shortened in the device handler under the subscriber level. At the same time,
however, you must then set up the dial plan in such a way that called parties can
be analyzed in subscriber format.
NODECD=27,NODECDSK=2;
The subscribers are assigned to the virtual node, whereby only the ones that are
not in the default node must be explicitly configured.
CHANGE-SDAT:STNO=2244,TYPE=DATA1,NNO=1-1-2;/* Expl. conf.
reqd.*/
The subscribers are usually set up as a subscriber in WABE .
As usual, set the node prefix table using AMO KNPRE, and enter the own
physical node number and code in the ZAND data and the own physical code in
AMO WABE 
Enter DAR=OWNNODE.
Virtual codes 19 and 27 may not be entered as OWNNODE, but rather as TIE so
that the dial plan analysis can be transferred. The reason for this is the same as
for the determination of the lowest unique level for ISDN numbers: OWNNODE is
used to shorten the called party. Since 4711 is only unambiguous due to his or
her tie line code, however, it may not fit in a transit node. Of the entire called party,
the dial plan can recognize whether a certain call is internal or external.
ADD-WABE:CD=19,DAR=TIE;/*NODECD*/
ADD-WABE:CD=27,DAR=TIE;/*NODECD*/
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Set up tie routes, outdial rules, and route elements for the ISDN numbering plan
in the normal manner. Routes are required for each virtual destination node,
however, as shown above. The dial plan is shown here. The specified entries are
absolutely necessary. Entries for a selection of the internal or external
subscribers in national or international format may continue to be necessary.
ADD-LDPLN:LDP=0-722-X,LROUTE=route to own node 1-1-1;
This route aims at the own "normal" subscriber of the default node. It may receive
only one route element for which the RERTEINT attribute is set. The outdial rule
may contain only the extension.
ADD-LDPLN:LDP=0-722-1716,LROUTE=route to partner node 1-1-1;
These routes really lead to the outside and aim at the "exception subscriber,"
Subscriber 1716 who moved.
ADD-LDPLN:LDP=0-636-X,LROUTE=route to partner node 1-1-2
These routes are the configuration for the "normal" subscriber on the partner
node and really lead to the outside.
ADD-LDPLN:LDP=0-636-2244,LROUTE=route to own node 1-1-2
This route only applies for the "exception subscriber" 2244, who has moved here.
The route may receive only one route element for which the RERTEINT attribute
is set. The outdial rule may contain only the extension.
Set the tie route, outdial rules, route elements for the UNKNOWN numbering plan
as usual. Routes are required for each destination node, however, as shown
above. The dial plan is shown here. The specified entries are absolutely required.
Entries for a selection of the internal or external subscribers in national or
international format may continue to be necessary.
ADD-LDPLN:LDP=19-X,LROUTE=route to own node 1-1-1;
This route aims at the own "normal" subscriber of the default node. It may receive
only one route element for which the RERTEINT attribute is set. The outdial rule
may contain only the extension.
ADD-LDPLN:LDP=19-1716,LROUTE=route to partner node 1-1-1;
These routes really lead to the outside and aim at the "exception subscriber,"
Subscriber 1716 who moved.
ADD-LDPLN:LDP=27-X,LROUTE=route to partner node 1-1-2
These routes are configuration for the "normal" subscriber on the partner node
and really lead to the outside.
ADD-LDPLN:LDP=27-2244,LROUTE=route to own node 1-1-2
This route only applies for the "exception subscriber" 2244, who has moved here.
The route may receive only one route element for which the RERTEINT attribute
is set. The outdial rule may contain only the extension.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
according to the rules in Section 42.2.1.5, “Source/destination-dependent
number modification in the ISDN or PNP numbering plan”. The use of ##### for
the specification of the digits to be supplemented or abbreviated in combination
with the logical NNO OWN extracts all virtual nodes and their codes from AMO
KNDEF:
CHA-KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=OWN,DNNOL=ROW,NUMEXT=#####;
---------------------------------------------------------------------------
NODE MATRIX FOR NPI = UNKNOWN, LEVEL = 0
---------------------------------------------------------------------------
------+------+----+------+------------------------+------------------------
1 |ROW | A |ALL | 19 | - 
2 |ROW | A |ALL | 27 | - 
------+------+----+------+------------------------+------------------------
ROW | 1 | A |ALL | - | 19 
ROW | 2 | A |ALL | - | 27

Analogously to 1-1-92
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
42.2.3.6 US EPNP network with overlapping L0 codes for

extension, without exit or prefixes
Munich CO
NNO: 1-1-8

49 89 722 and 723 49 89 636 and 637
PNNO: 1-1-91 PNNO: 1-1-92

NNO: 1-1-192 NNO: 1-1-276
NNO: 1-1-193
NNO: 1-1-277
21715 31715
PNP: 192 -XXXX

193 -XXXX
ISDN :0-(00)49-(0)89-722 -XXXX
0-(00)49-(0)89-723 -XXXX
62244 72244
PNP: 276 -XXXX
277 -XXXX
ISDN :0-(0)49-(0)89-636 -XXXX
ISDN :0-(0)49-(0)89-637 -XXXX
Figure 61 US EPNP with overlapping L0 code/extension
Here, a one-level PNP is used for internal network, as usual in the U.S. networks.
No exit or prefixes are used for PNP. It looks like a OpenScape 4000 numbering
plan and the configuration is a mixed form of open numbering and PNP. Signaling
takes place in PNP and both the called party and information numbers should be
transferred in LOCAL format.
In addition, the overlapping feature is shown between extensions and L0 code.

For PNNO 1-1-91, the customer has purchased two CO numbers with extension
0 to 9999, 722 and 723. To cover the customer’s extension requirements of about
19,000, the customer has created an extension range of 20000 to 29999 and
30000 to 39999 through the overlapping of the last digit. 
The overlapping must thus also be transferred to the PNP.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification

PNPLC=192,PNPSK=2,PNPUL=EXT;
PNPLC=193,PNPSK=2,PNPUL=EXT;
The subscribers are assigned to the virtual node, whereby only the ones that are
not in the default node must be explicitly configured.
The subscribers are normally set up as subscribers in WABE, whereby the
overlapping digit belongs to the extension, i.e. 21716 and 31715.
Set the node prefix table:

For PNP, no entry may be made since no exit or prefixes are used for processing.
You can set the format of the outgoing information number in KNFOR.
ADD-KNFOR:DNNO=1-1-276,NPI=PRIVATE,TONOUT=LOCAL;
ADD-KNFOR:DNNO=1-1-277,NPI=PRIVATE,TONOUT=LOCAL;
If information numbers should also be displayed with L0 code in the own node,
use this command: This only effects the number transferred in the network,
however, not for internal calls:
ADD-KNFOR:DNNO=1-1-192,NPI=ISDN,TONIN= LOCAL;
ADD-KNFOR:DNNO=1-1-193,NPI=ISDN,TONIN= LOCAL;
In the digit analysis, forward the local code of the partner to the TIE digit analysis
result. Normally, the PNP exit is referred to TIE here, but since there is no exit,
the local code is configured like a tie line code of the OpenScape 4000
UNKNOWN numbering plan.
When needed, you can set up the own local codes as OWNNODE. In contrast to
open numbering, this entry is not required in the UNKNOWN station for incoming
calls through the network since the called party is shortened via the AMO KNDEF
table in case of network-wide calls. They cannot enable dialing with codes for
subscribers, however, which is recommended for a constellation with two virtual
nodes. Subscriber 21715 can thus reach Subscriber 31715 by dialing 31715 or
1931715. The skip digits are not specified in WABE; they are automatically
determined from the entries in the AMO KNDEF table.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
ADD-LDPLN:LDP=276-X,LROUTE=1408,...;
ADD-LDPLN:LDP=277-X,LROUTE=1308,...;
For the transfer of the called party (and thus the information numbers) in PNP, you
need a relevant outdial rule.
ADD-LODR:ODR=60,CMD=NPI,NPI=PRIVATE,TON=LOCAL;
ADD-LODR:ODR=60,CMD=ECHOALL;
Define routes with the virtual node of the partner as the target node and assign
the outdial rule.
ADD-RICHT:MODE=LRTENEW,LRTE=1408,...,DNNO=1-1-276;
ADD-RICHT:MODE=LRTENEW,LRTE=1308,...,DNNO=1-1-277;
ADD-LDAT:LROUTE=1308,.., ODR=60;
Comment:
If you do not want to transfer the called party in local format, but rather as an
extension in subsystem and if you also want to use the overlapping of the local
code for an extension, observe the following:
The outdial rule must divide the dial pattern into fields in such a way that the
specification of a field for the extension is possible in the outdial rule. For this
purpose, the check in AMO LDPLN was changed so that a splitting of the local
code into skip digits and overlapping portion is now possible as well.
ADD-LDPLN:LDP=27-X,LROUTE=1408,...;
/* The 6 of local code 276 is a part of Field 2 */
The corresponding outdial rule would be:
ADD-LODR:ODR=60,CMD=NPI,NPI=PRIVATE,TON=UNKNOWN;
The number modification takes place with data from AMO KNDEF.
Service information
• No settings for KNMAT are required.
• In this example, the overlapping digits between NPI ISDN and PRIVATE must
be identical.
• The digit pattern for the connection between the systems in PNP must
possible be set up individually for the overlapping digits.

The physical node 1-1-92 is configured analogously to 1-1-91.
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Relevant AMOs
42.2.3.7 US EPNP network with overlapping L0 codes for

extension, with exit, without prefixes
It is also possible to configure PNP without prefixes, but with exit.

For this purpose, an entry must be made in KNPRE:
ADD-KNPRE:NPI=PRIVATE,TON=LOCAL,EXIT=9;
ADD-KNPRE:NPI=PRIVATE,TON=LEVEL1,EXIT=9;
ADD-KNPRE:NPI=PRIVATE,TON=LEVEL2,EXIT=9;
The dial plan must be adapted accordingly.
Such a configuration may be required if ambiguities appear between extensions

and local codes during the merging of networks. In Figure 61, for example,
Subscriber 636 could exit in physical node 1-1-91. The dialing of 636 by a
subscriber in 1-1-91 should then lead to internal subscriber 636, while the dialing
of 9-636-xxxx should lead to the partner node.
The last configuration examples have shown different types of analysis for the
dial pattern. Principally, the analysis of the dial pattern consists of the digit
analysis (AMO WABE) and LCR dial plan (AMO LDPLN) steps. If required, a loop
back to the digit analysis (AMO WABE) can be configured using the RERTEINT
LDAT attribute.
IMPORTANT: Configure the analysis of the dial pattern in as few steps as

possible.
42.3 Relevant AMOs

Language
KNDEF KNNR d virtuelle Knotennummer (0-0-0 = Rest
der Welt)
NNO e virtual node number (0-0-0 = rest of world)
TYP d Typ des virtuellen Knotens (eigen
oder fremd).
TYPE e type of virtual node (own or foreign).
ISDNCC d ISDN Landeskennzahl (country code).
Standardwert: * (keine Landeskennzahl)
ISDNCC e ISDN country code. Default value: * (no
country code)
ISDNAC d ISDN Ortskennzahl (area code).
Standardwert:* (keine Ortskennzahl)
ISDNAC e ISDN area code. Default value: * (no area
code)
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Relevant AMOs

Language
ISDNLC d ISDN Hauptanschlussnummer (local
destination code). Standardwert: * (keine
Hauptanschlussnummer)
ISDNLC e ISDN local destination code.
Default value: * (no local destination code)
ISDNSK d ISDN Skip Digits.
ISDNSK e ISDN skip digits.
ISDNUL d ISDN lowest unique level
ISDNUL e ISDN lowest unique level
PNPL2C d PNP Level 2 Code. Standardwert: * (kein
Level 2 Code)
PNPL2C e PNP level 2 code. Default value: * (no level
2 code)
PNPL1C d PNP Level 1 Code. Standardwert: * (kein
Level 1 Code)
PNPL1C e PNP level 1 code. Default value: * (no level
1 code)
PNPLC d PNP Local Code (Level 0 Code).
Standardwert: * (kein Local Code)
PNPLC e PNP local code (level 0 code). Default
value: * (no local code)
PNPSK d PNP Skip Digits.
PNPSK e PNP skip digits
PNPUL d PNP lowest unique level
PNPUL e PNP lowest unique level
KNOTENKZ d Knotenkennzahl für Rufnummernplan
unknown.
Standardwert: ****** (keine
Knotenkennzahl)
NODECD e Node access code for numberingplan
unknown. Default value: ****** (no node
access code)
KNOTKZSK d Skip Digits für Knotenkennzahl (Param.
KNOTENKZ).
NODECDSK e Skip digits for node access code (parameter
NODECD).
CACP d CAC-Präfix. Standardwert: * (keine
CAC-Präfix)
CACP e CAC prefix. Default value: * (no CAC prefix)
KNFOR ZKNNR d Zielknotennummer
NPI d numbering plan identifier
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Relevant AMOs

Language
NPI e numbering plan identifier
TONIN d Type of number für ankommenden
Endverkehr
TONIN e Type of number for incoming traffic
TONOUT d Type of number für abgehenden Verkehr
TONOUT e Type of number for outgoing traffic
SCRE d screening indicator
SCRE e screening indicator
FEHLOPT d Fehleroptionen für TONOUT Option
ERROPT e error option for TONOUT handling
KNPRE TON d Typ der Rufnummer
TON e type of number
NPI d numbering plan identifier, rufnummernplan
AUSSTIEG d Ausstiegskennzahl
EXIT e exit code
KNMAT EBENE d ebene der Knotennummern
LEVEL e level of nodenumbPKNOTKZPKNOTKZers
NPI d numbering plan identifier, rufnummernplan
UKNNR d Ursprungsknotennummer
ONNR e origin node-number
ZERG d Ziffernergänzung,loe=*****,eigen=#####
NUMEXT e number extension,delete=*****,own=#####
ZKUE d Ziffernkuerzung,loe=*****,eigen=#####
NUMRED e number reduction,delete=*****,own=#####
WABE RNR d Rufnummer
KZP d Kennzahlpunkt
WABE d Wabegruppe
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Relevant AMOs

Language
PKNNR d Dreistufige Knotennummer zur eindeutigen
Identifikation des Knotens im Netz.
PNNO e Node number (until 3 levels) for
unambiguous
identifaction in network
PKNOTKZ d Kennzahl eigener Knoten.
PNODECD e Physical node number
(AMOs for LCR, see Chapter 37, “LCR (Least Cost Routing)”)
A31003-H3170-S103-6-7620, 02/2019
stnomod_en.fm
Number Modification
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
Feature Description
43 PIN and Follow-Me Network-Wide

Users in local OpenScape 4000/HiPath 4000 networks (i.e. confined to one
company building/location) are to be able to use the "network-wide PIN" feature
similarly to the previous system-wide PIN function, for manual PINs and chip
cards. In corporate networks distributed over different sites/locations, some
limitations must be expected.
IMPORTANT: : Setup of network-wide PIN and network-wide follow-me is

described in the Chapter 132, “PIN (Personal Identification Number)”.
The following data and functions of a user’s "home" station are available and
usable at "foreign" stations in a network:
1. Authorizations
• Individual authorizations for external calls (COS1 / LCRCOS)
• Internal traffic restrictions group no. (ITRGR)
• Dial plan group no. (DPLNGR)
2. Display data
If a user sets up a call after activating his/her PIN at a foreign station, called
users will see the calling user’s own display name and number instead of that
of the "foreign user’s" station. If the calling user has a secret station number,
this will be taken into account accordingly. Depending on the COPIN assigned
to the user (class-of-PIN), called users may alternatively still see the "foreign"
station data instead of the calling user’s home station data.
3. CDR data
For call data recording purposes, either the station number of the home
station or the number of the foreign station is entered in the CDR data record,
depending on the COPIN.
4. Mailbox LED (MB)

When a user activates his/her PIN at a foreign station, the MB-LED of the
foreign station will indicate new messages in the VMS or TCS mailbox of the
user’s home station.
5. Follow-me
Call forwarding to a foreign station can be activated at the foreign station as
follows (follow-me feature):
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
Functions / Restrictions when using a PIN network-wide / external
a) if PIN is activated: by pressing the FWD key for fixed call forwarding, or
dialling the appropriate variable call forwarding code procedure.
b) if PIN is not activated: via the Service Menu
6. SMART
If the user’s home station is configured as a virtual station (a.k.a. "fictitious
user"), the call forwarding mode can be switched over from variable FWD
(follow-me) to fixed FWD (e.g. to the user’s voice mailbox) at the "foreign"
station. This function can also be configured for "real" stations/users.
7. Project code (PCODE) verification

The "PCODE" feature is intended to allow project-specific call charges and
feature authorizations to be assigned to a project code. The PCODE number
is not assigned to a specific user or home station. This means that it is not
possible to determine ad hoc which node the PCODE is administered in. In
order to be able to use PCODES throughout a network, it is necessary to
install an administrable network-wide algorithm for PCODES, according to
which the PCODE can be verified and identified ("modulo" verification). This
means that the PCODES are no longer stored in individual nodes of the
network.
8. Restart protection
The active PIN identifications and existing follow-me activations are not lost
after soft or hard restarts, or after duplex switchover.
43.2 Functions / Restrictions when using a PIN network-wide / external
Feature Network-wide / external PIN

Transfer authorizations For outgoing calls only, not for incoming calls.
Authorizations for trunk and tie traffic only.
PIN for call detail recording Yes
Follow me / FWD transfer. Yes
Caution: Note the
restrictions for FWD and
FNA
Speed dialing facility The speed dialing facility is not transferred. The speed
dialing facility index from the physical station and numbers
from the local system list are used.
Individual speed dialing No. Individual speed dialing cannot be used.
WABE Only numbers from the WABE group are transferred. The
corresponding WABE group of the external system is then
valid. In other words, WABE groups or the generation of
systems in the network should be consistent.
IBM SMART, CF switch Yes (for virtual and physical stations).
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
Terminals
Feature Network-wide / external PIN

ITR group Only numbers from the ITR group are transferred. The
corresponding ITR group of the external system is then
valid.
Repertory dialing keys Repertory dialing keys are not transferred. The repertory
dialing keys on the physical station are used.
DSS keys DSS keys are not transferred. The DSS keys on the
physical station are used.
Redial Not transferred. The redial key on the physical station is
used.
Enter timed reminder No. The timed reminder is valid for the physical station.
Mailbox Signaling via LED only, no scroll function available. In
other words, you must use the corresponding VMS code
to dial into the VMS.
Although the physical station’s callbacks are signaled, it is
not possible to scroll through or perform callbacks when
the PIN is active.
43.3 Terminals
Functional terminals (e.g. set 600) cannot be used as "foreign" stations in the
sense described above. A user’s home station can be any standard voice
terminal. PIN entry at non-voice terminals is not supported.
43.3.1 Activating and Deactivating a Network-Wide

PIN
Users with network-wide PINs only enjoy a subset of the current features
available with the standard, system-specific PIN feature. For example, "name"
keys (programmable keys) and individual speed dialling destinations
programmed at the home station cannot be accessed.
PINs can be enabled for network-wide use or limited to system-specific (node-

specific) use by setting the appropriate bit flag in the system’s feature bit string. It
is not possible to activate both types of PIN usage for PINs within the same PABX.
Users have two possible options for identifying themselves via PIN within a
OpenScape 4000/HiPath 4000 network:
• By entering the appropriate "APIN" code, i.e. entering the home station
number followed by the assigned PIN (manual PIN)
• By inserting their chip card and entering their home station number
• from V2.0 by inserting the Smart Card
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
Terminals
The code for deactivating the PIN (if necessary) is the same for all PIN types.
Users simply enter the "DPIN" code or pull out the card.
43.3.2 Identification via "APIN" Code (Manual PIN)

The "APIN" code, i.e. the home station number followed by the assigned PIN,
must be entered as follows:
CDAPIN + STNOhome stno + # + PIN + #
(Note: STNOhome stno = CDnode number + STNOhome station/extension number)
The delimiter between the station number and the actual PIN is the "#" character.
In networks with open numbering schemes, users must enter the node number
assigned to their "home" node in front of their home station number. If entering a
PIN identification procedure within their own node, users can omit the node
number.
As a positive acknowledgement, the display will show "Identifikation STNOhome

stno" ("Identification: STNOhome stno").
For wrong PIN or wrong home station number entries, "nicht erlaubt" ("not
allowed") will be displayed as a negative acknowledgement.
For other wrong entries, "nicht moeglich" ("not possible") will be displayed as a
negative acknowledgement. 
For Digites without display units, the appropriate positive or negative
acknowledgement tone or announcement will be heard instead.
Users receive the following display outputs when identifying themselves:

1. Input: CD APIN
123456789012345678901234
Rufnummer eingeben:
2. Input: 1st digit of STNO home stno
n
neu waehlen?
3. Input: remaining digits of STNO home stno + #
Code-Nr. eingeben:
4. Input: 1st digit of PIN
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
Identification via Chip Card
n
Code neu eingeben?
5. Input: remaining digits of PIN + #
Identifikation rnr
IMPORTANT: stno is normally the user’s home station number, but may also be
the number of the "foreign" station used, depending on the user’s COPIN.
Users have the option of correcting their entries at each stage of the procedure,
i.e. the home station number or PIN entry can be repeated if mistakes are made
during input.
43.4 Identification via Chip Card

When the chip card is inserted, the telephone display will show "RUFNUMMER
EINGEBEN:" ("PLEASE ENTER NUMBER") to prompt the user to enter his/her
home station number. The delimiter (end character) between the station number
and the actual PIN is the "#" character.
In networks with open numbering schemes, users must enter the node number
assigned to their "home" node in front of their home station number. If entering a
PIN identification procedure within their own node, users can omit the node
number.
As a positive acknowledgement, the display will show "Ausweis STNOhome stno"

("ID card STNOhome stno").
For wrong PIN or wrong home station number entries, "nicht berechtigt" ("not
authorized") will be displayed as a negative acknowledgement.
For other wrong entries, "nicht moeglich" ("not possible") will be displayed as a
Users receive the following display outputs when identifying themselves:

1. Input: Insert chip card
123456789012345678901234
Rufnummer eingeben:
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
Input Procedure for Network-Wide Follow-Me
n
neu waehlen?
Ausweis rnr
IMPORTANT: stno is normally the user’s home station number, but may also be
the number of the "foreign" station used, depending on the user’s COPIN.
Users have the option of correcting their entries at each stage of the procedure,
i.e. the home station number entry can be repeated if mistakes are made during
input.’
From V2.0, you no longer need to use the ’SCAA’ application for activation of the
mobile station with chip card or smart card.
43.5 Input Procedure for Network-Wide Follow-Me

The "Follow-Me" feature allows variable call forwarding of calls to the user’s home
station to the foreign station currently in use (i.e. programming and activation).
The network-wide follow-me feature is a subset of the feature "Remote CF by
Station". 
The activation and deactivation of the follow-me feature via the FWD key, for the
voice service, can only be carried out at foreign stations in idle state. If the foreign
station is in any state not equal to "idle", the display will show "NICHT
MOEGLICH" ("NOT POSSIBLE") as a negative acknowledgement.
The activation or deactivation of the follow-me feature via the CHECK function is
also possible during an ongoing call.
The following options are available for activating/deactivating the follow-me
feature:
• if PIN active or chip-card inserted: by pressing the FWD (call forwarding) key.
• if PIN active or chip-card inserted: by dialling the appropriate code for

"Variable FWD on/off"
• if PIN active or chip-card inserted: via the idle telephone menu
• with or without active PIN: via Service Menu
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
Follow-Me Activation/Deactivation via Service Menu:
The follow-me option is displayed on the foreign terminal if the home station
user’s PIN is active. If the user’s PIN is not active, the display shows "Umleitung
eingeschaltet" ("Call forwarding activated").
For wrong entries, "nicht moeglich" ("not possible") will be displayed as a
The call forwarding option is shown on the telephone displays of the home station
and foreign station concerned, and indicated with the FWD LED, in the same way
as for the "internal" follow-me feature. The active call forward status at the user’s
home station is additionally indicated at the foreign station with a special dial tone.
43.5.1 Follow-Me Activation/Deactivation with the

FWD key (PIN/Chip Card Active)
If the home station user’s PIN is active, simply pressing the FWD key on the
foreign station will switch over the call forwarding function at the user’s home
station. This means: if call forwarding is already activated at the user’s home
station, it will be deactivated. If no call forwarding is activated at the user’s home
station, variable call forwarding to the foreign station in use will be activated
(follow-me).
If the user’s home station is a virtual station ("fictitious user"), an existing call
forwarding activation is not only deactivated, but immediately re-activated to the
fixed call forwarding destination programmed for the user’s home station (if
programmed). This function can also be used by users with "real" home stations
(depends on COPIN).
43.5.2 Follow-Me Activation/Deactivation by Dialling

the Codes for "Variable Call Forwarding On/Off" (PIN/
Chip Card Active)
Provided the home station user’s PIN is active, dialling the code for "Variable call
forwarding on" will automatically program and activate the follow-me function.
Dialling the code for "Variable call forwarding off" deactivates any call forwarding
activated at the user’s home station. The codes can be dialled at any digital
terminal.
43.6 Follow-Me Activation/Deactivation via Service Menu:

The follow-me function can be activated via the Service Menu function regardless
of whether the home user’s PIN is active or not.
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
43.6.1 Activating Follow-Me via the Service Menu

In the "Destinations" menu, a sub-menu option will be installed for activating the
"Remote-CFU" feature.
Menu text for activating follow-me in the "Destinations" menu:
1. Input: press Service Menu key, browse to "Destinations" - press "Yes" key
123456789012345678901234
Ziele:
Umleitung f. Ruf-Nr.? >
2. Input: "Yes" key
Umleitung f. Ruf-Nr.:
variable Umleitung? >
3. Input: "Yes" key
Rufnummer eingeben:
zurueck?
n
neu waehlen? >
(scroll with "Next"/"Back" keys until: zurueck? >)
Code-Nr. eingeben:
zurueck?
n
Code neu eingeben? >
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
Zielruf-Nr. eingeben:
speichern? >
8. Input: (1st digit of STNO destination stno )
n
speichern? >
(scroll with "Next"/"Back" keys until: neu waehlen? >)

9. Input: (remaining digits of STNO destination stno + ) (#)
10. Input: "Yes" key
Umleitung
eingeschaltet
IMPORTANT: Input in brackets ( ) = optional

For activating follow-me, it is not necessary to enter the destination number.
If the home station user’s PIN is active, users do not need to repeat the PIN and
home station number entries, but must enter the delimiter "#".
With "zurueck" ("back"), users are returned to the next highest menu level, e.g.
back to the "Umleitung f. Ruf-Nr.? >" option of the "Destinations" menu.
43.6.2 Deactivating Follow-Me via the Service Menu

In the "Switches" menu, a sub-menu option will be installed for deactivating the
"Remote-CFU" feature.
Menu text for deactivating follow-me in the "Switches" menu:
1. Input: press Service Menu key, browse to "Switches" - press "Yes" key
123456789012345678901234
Schalter:
Umleitung f. Ruf-Nr.? >
2. Input: "Yes" key
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
Rufnummer eingeben:
zurueck?
n
neu waehlen? >
Code-Nr. eingeben:
zurueck?
n
Code neu eingeben? >
Umleitung ist ein

ausschalten? >
(scroll with "Next"/"Back" keys until: Ziel anzeigen? >)

(scroll with "Next"/"Back" keys until: naechster Schalter? >)
7. Input: "Yes" key
Umleitung
ausgeschaltet
IMPORTANT: If the home station user’s PIN is active, users do not need to
repeat the PIN and home station number entries, but must enter the delimiter "#".
With "zurueck" ("back"), users are returned to the next highest menu level, e.g.
back to the "Umleitung f. Ruf-Nr.? >" option of the "Switches" menu.
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
PIN Deactivation
43.7 PIN Deactivation

The PIN can be deactivated as follows:
• with the PIN code
• in the service menu
• by removing the chip card/smart card (V2.0 and higher)
Message exchange for PIN deactivation
a) PIN deactivation at the third-party station

When you deactivate the PIN at the third-party station, the foreign node
sends a PIN deactivation messages to the home node. This informs the
home node that the PIN was deactivated and deletes the station number
of the foreign station in your memory.
b) PIN deactivation from the home station to the foreign station

The mobile user should not be identified at multiple stations
simultaneously because the status of the home station can only be
updated at one foreign station. If the mobile user is identified at a second
foreign station, an identification existing at another station should be
automatically deleted. To do this, the home station sends a PIN-
deactivation message to the first foreign station where PIN deactivation is
performed. If the connection between the home and foreign system
breaks down, the first identification remains intact because the
deactivation message to the foreign station is not repeated. The PIN
remains active at the foreign station. Consequently, the mobile user
cannot be sure that the first identification was automatically deactivated
when entering the PIN at another station. The home data can only be
updated at the station where the mobile user was last identified because
only this station is known to the home station.
43.8 Network-Wide PIN and Follow-Me in 1 Step

When you activate a long PIN, the follow-me function can be automatically
activated. This feature is automatically deactivated when you deactivate a PIN.
For information on configuring this function, see the PIN chapter.
A31003-H3170-S103-6-7620, 02/2019
pinfol_en.fm
Network-Wide PIN and Follow-Me in 1 Step
A31003-H3170-S103-6-7620, 02/2019
prevcon_en.fm
Preventing Connections
Single Level Network
44 Preventing Connections
44.1 Single Level Network

The node connection matrix can be set so that connections between certain
network nodes are inhibited. AMO KNMAT is used for this.
NNO NN NN NNO
Public. Public
EXCH 1 =100 O O =200 EXCH 2
STNO 4711 STNO 4711
Figure 62 Preventing Connections
The two exchanges are assigned different node numbers. These are allocated
with AMO TDCSU or TACSU, parameter NNO.
1. Calls from a public exchange are to be prevented from being switched via the
PABX network to another public exchange. At the same time, the forwarding
of stations in the PABX network to the public exchange at any point is not to
be prevented, e.g. in order to utilize the cost benefits involved. 
NNO 010: CHANGE-
KNMAT:LEVEL=0,ONNO=200,DNNO=100,CONN=D; 
NNO 020: CHANGE-
KNMAT:LEVEL=0,ONNO=100,DNNO=200,CONN=D;
2. If, for example, it is not to be possible for subscribers in Exchange 1 to access

subscriber 924711 by way of the tie trunk (e.g. because expensive private-
network leased lines are used for such connections), the following must be
configured: 
NNO 010: CHANGE-KNMAT:LEVEL=0,ONNO=100,DNNO=20,CONN=D;
3. If subscribers in Exchange 2 are likewise not to be permitted to use the tie

trunk, the following must be configured: 
NNO 020: CHANGE-KNMAT:LEVEL=0,ONNO=200,DNNO=10,CONN=D;
IMPORTANT: Since the node numbers in the network are unambiguous, the
commands can be entered in all network nodes.
Since all other connections are permissible, the default setting is retained for
them.
A31003-H3170-S103-6-7620, 02/2019
prevcon_en.fm
Preventing Connections
Multi Level Network
44.2 Multi Level Network

It is possible to configure multi level networks. In all network nodes however, the
node numbers must have the same graduation. You are able to deny connections
level individual.
Level 0 Level 1 sub-domain = 10

Node number = 5
Level 1 sub-domain = 20
Level 2 domain = 1 Level 2 domain. = 2
Figure 63 3-Level Network
Example 1
You can configure in one or in all network nodes, that e.g. connections between
Level 2 domain 1 and 2 are to be denied:
CHANGE-KNMAT:LEVEL=2,ONNO=1,DNNO=2,CONN=D;
IMPORTANT: Note that Node numbers / Sub-domains (Level 0 / 1) are not

unique within the network. if the network numbering scheme comprises higher
levels than the specified one.
Example 2
CHANGE-KNMAT:LEVEL=1,ONNO=10,DNNO=20,CONN=D;
Since the levels are handled seperately, this command prevents all connections
between 1-10-xxx and 1-20-xxx, but also between 1-10-xxx and 2-20-xxx (xxx
means any Level 0 node number).
The anolog handling will occur if you use level 0 node numbers in KNMAT which
are defined within several sub-domains / domains, i.e. which are not unique.
For denying connections between node numbers in level 0, see Single Level
Network.
A31003-H3170-S103-6-7620, 02/2019
public_pri_networking_en.fm
Feature description
45 Public PRI Networking
45.1 Feature description

This feature provides the capability for a OpenScape 4000 customer the ability to
access a wide range of U.S. public network calling services and supplementary
services via a PRI access interface. The US PRI protocols supported are:
• for LEC-access (Local Exchange Carrier): ATT4ESS and NI2
• for IEC-access (Inter Exchange Carrier): ATT4ESS, MCI-DMS250, MCI-

DEX600, SPRINT-DMS250
45.1.1 Supplementary Services

The following table shows a list of supported Supplementary Services. (X =
supported)
Supplementary Service ATT4ESS MCI- MCI- SPIRNT- NI2

DMS250 DEX600 DMS250
Call-by-Call Service Selection X X X X X
Dedicated Service Selection X X X X X
Equal Access X - - - X
Operator Access (using functional X - - - X
Signalling)
DNIS (Dialed Nr ID Service) X X X X X
CLID (Calling Line ID)) X X X X X
COLI (Connected Line ID) X X X X -
Redirecting Number X X X X X
Network Name Display - - - - -
Call Redirection X X X
Network Call Transfer - X X - X
- Network Call Transfer (MCI)
- Two B-Channel Transfer (NI2)
User-to-User Signalling X X X - -
B-Channel Management X X X X X
PRI Span Initialization Restart X X X X X
Procedures
Additional Calling Part Number X X X X X
CND (Calling Name Delivery) X
Table 12 Supplementary Services
A31003-H3170-S103-6-7620, 02/2019
Feature description
Supplementary Service ATT4ESS MCI- MCI- SPIRNT- NI2

DMS250 DEX600 DMS250
ISDN-PRI (RN) Redirecting X X X X X
Number
Table 12 Supplementary Services
45.1.1.1 ACPN (Additional Calling Party Number)
The ACPN is configured in SDAT. This is the public number to be sent out to the
public network.
When the call is originated on the private NQ network, the LDAT LCR-Attribute
PUBNUM must be set on the gateway switch to the public network. If LDAT LCR-
Attribute PUBNUM is set the calling number is only replaced with a provided
PUBNUM if the NPI (Numbering Plan Identifier) matches that of the called
number. The received ACPN will replace the the calling number when the LDAT
Attribute is set and is not subject to any modification from the usual KN-AMOs i.e.
KNFOR, KNMAT.
If the LCR-Attribute PUBNUM is not set, then the subscriber extension number
(modified by KN-AMOs) is sent out.
45.1.1.2 Network Call Transfer
This Supplementary Service is called Network Call Transfer for MCI and Two B-
Channel Transfer by Bellcore (NI2). This service is invoked whenever a trombone
connection on the same trunk to the public network exists (e.g. Transfer,
Conference, ACD- off-sire routing,...). The COT NCT and the FEASU NCT must
be set to enable this SS. The user has not indication of when the NCT takes
place. CDR and Trafic Metering record successfull NCTs.
45.1.1.3 Calling Services
There are incoming, outgoing Calling Services which can be requested on Call-
by-Call or Pre-Provisioned. Outgoing Call-by-Call Calling Services are configured
in LDAT, Pre-Provisioned (Dedicated) Calling Services are configured in TDCSU.
Outgoing Call-by-Call Calling Services shall only be configured on the Gateway

switch to the public network. Incoming Calling Services will be sent over the
private NQ network for CDR purposes.
A31003-H3170-S103-6-7620, 02/2019
Feature description
Calling AT&T MCI SPRINT NI2

Service
NONE POTS POTS POTS POTS
INWATS Toll-Free MCI 800/888/ Ultra 800/888/ In-WATS
Megacom 877 877
INTLWATS International - - -
Toll-Free
PPC900 MultiQuest MCI 900 - -
LDS Long Distance - - -
Service
OUTWATS Megacom Prism Ultra WATS Out-WATS
WB0-WB9 - - - Multiband Out-
WATS
VPN SDN Vnet VPN -
FX - - - Foreign
Exchange
TTa - - - Tie Trunk
Access
SDS Accunet - - -
Table 13 Calling Service
45.1.1.4 Equal Access
Equal Access can be requested by LCR (AMO-LDAT) or by the user dialing a CIC
(e.g. 9-101-0288-1-561-923-1446). This is an outgoing only feature and can be
requested from the private CorNet-N/NQ network. Equal Access s only available
for LECs where the DEDSCC parameter of AMO-TDCSU is set to NONE.
45.1.1.5 CND (Calling Name Delivery)
If a name server is connected to a switch the calling name information can be

received in a delayed FACILITY message instead of the SETUP message. The
delayed information is then shown on the user display.
The calling name delivery feature can be disabled by adding the COT BKNA to
the trunk.
Traffic meetering is expanded with three system wide peg counters:
• Calling name informations in SETUP message.
• Calling name informations in delayed FACILTY message.
• Calling name informations not available.
A31003-H3170-S103-6-7620, 02/2019
User Interface
This feature is only supported with NI-2 or CorNet-NQ.
45.1.1.6 ISDN-PRI RN (ISDN-PRI Redirecting Number)
ISDN-PRI Redirecting Number provides support for sending of the ISDN-PRI

Redirecting Number (RN) of the originally called party for e.g 0# transfers out of
PhoneMail to PRI Software Defined Network (SDN).
This feature affects only calls that are transferred out of applications (e.g
PhoneMail, Xpressions, or the new Multimedia Messaging Server (codenamed
"Saturn") using the official transfer CorNet-NQ procedure SS-SSCT to ISDN-PRI
trunk.
45.2 User Interface
45.2.1 CND (Calling Name Delivery)

When a calling name information is received the new name information is shown
on the user display.
45.2.2 ISDN-PRI RN (ISDN-PRI Redirecting Number)

The only user interface impacted by this feature is that of the destination of the
transfer out of SSCT. This user will receive indication of a redirecting number of
the party that the caller who invoked SSCT originally attempted to call. The way
the redirecting number is presented to that destination is outside the scope of this
specification.

The Public PRI Networking feature is intended for the North American
marketplace.
The following features are also available:
• CND
• ISDN-PRI RN
A31003-H3170-S103-6-7620, 02/2019
Generation
45.4 Generation
• How to add the T1 board:
COPY-PRODE:TYPE=PVCD,PVCDNO=16; /*loads the US protocols into
memory
",FCTID=2,LWVAR="K", HWYBDL=A; /*configures T1 board
CHANGE-
LWPAR:TYPE=TMD,TMDTYPE=TMDMOS,BLNO=2,OPMODE=FRAMEESF&BISUB8ON
&BDETON,CABLETYP=1,OESDISTH=30,OESREQTH=4,SESDISTH=10,SESREQT
H=10,ACKTIM=10,DLVTIM=600,OCTMAX=260,RETMAX=3,WINDOW=7; /
*loadware parameters for T1 board
• How to setup the trunk for NI2 without a dedicated calling service
ADD-
COT:COTNO=100,PAR=IIDL&IVAC&INAU&ITB&IDND&IFR&ANS&CEOC&CEBC&C
OTN&IEVT&IDIS&LWNC&NLCR&ICZL&NCT&NTON;
ADD-COP:COPNO=100,PAR=SDL&BR64&RMSG&RRST&TIM1&IDP4;
ADD-TDCSU:OPT=NEW,PEN=1-01-043-
0,COTNO=100,COPNO=100,COS=1,LCOSV=9,LCOSD=9,CCT="PRI",DESTNO=
0,PROTVAR=NI2,SEGMENT=1,DGTPR=1,ISDNIP=561,ISDNNP=923,PNPL2P=
011,PNPL1P=1,NNO=1-1-
99,TGRP=104,SRCHMODE=ASC,DEV=S1COD,BCHAN=1&&23,BCNEG=N,BCGR=1
,IGN=1,IID=1,LWPAR=6,LWPP=2;
45.4.1 Calling Services

• How to setup the routing with the call-by-call service ‘banded outwats - band
2’
ADD-RICHT:MODE=LRTENEW,LRTE=304,LSVC=ALL,NAME="E.164
NAT.",TGRP=104,DNNO=1-1-99,ROUTATT=YES,PDNNO=1-1-99;
ADD-LODR:ODR=304,CMD=SENDCIC;
ADD-LODR:ODR=304,CMD=SENDOSA;
ADD-LODR:ODR=304,CMD=NPI,NPI=ISDN,TON=NATIONAL;
ADD-LDAT:LROUTE=309,LSVC=ALL,LVAL=1,TGRP=104,ODR=304,LAUTH=1,
CARRIER=1, ZONE=INTERN01,LATTR=PUBNUM&WCHREG,SCCID=0288, 
FACILITY=2, SVCVCE=OUTWATS;
ADD-LDPLN:LDP="9"-"1"-"561"-"923"-"XXXX",LROUTE=304,LAUTH=1;
45.4.2 B-Channel Management

• How to deactivate and activate B-Channels 1through 6:
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
DEA-DSSU:OFFTYPE=DI,TYPE=BCHAN,PEN1=1-1-43-0,BCHL=1&&6;
ACT-DSSU:ONTYPE=AUL,TYPE=BCHAN,PEN1=1-1-43-0,BCHL=1&&6;
45.4.3 ACPN (Additional Calling Party Number)

• How to configure the ACPN of the originating station:
CHANGE-
SDAT:STNO=3342,TYPE=DATA1,PUBNUM=915619233342,TON=NATIONAL,NP
I=ISDN;
45.4.4 CND (Calling Name Delivery)

• How to enable CND by COT (default)
CHANGE-COT:COTNO=120,COTTYPE=COTDEL,PAR=BKNA;
• How to disable CND by COT
CHANGE-COT:COTNO=120,COTTYPE=COTADD,PAR=BKNA;
• How to activate and reset the system counters
DISPLAY-ZAUSL:PROCID=BP,DEL=Y;
• How to inquire the values of the system counters
DISPLAY-ZAUSL:PROCID=BP;
45.4.5 ISDN-PRI RN (ISDN-PRI Redirecting Number)

• How to enable ISDN-PRI RN by COT (default)
CHANGE-COT:COTNO=120,COTTYPE=COTDEL,PAR=ORRN;
45.5 Relevant AMOs
AMO Parameter Language Description

PRODE - d US PRI-spezifische Protokoll-Tabellen für
die Länder USA & Kanada sind über die
PVCD 16 verfügbar.
- e US PRI protocols have been added. PVCD
16 is the new protocol variant for the
counties US/Canada.
FEASU - d NCT (Network Call Transfer) kann aktiviert/
deaktiviert werden
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

- e NCT (Network Call Transfer) can be
activated/deactivated
BCSU MTYP d MTYP=TMD für die T1-Board Konfiguration.
(sehe T1 Adaption Leistungsmerkmal für
mehr Details)
MTYPE e MTYPE=TMD for configuration of T1
boards. (see T1 Adaption feature for more
details)
COP RRST/RMSG d RRST und RMSG müssen US PRI
Protokolle gesetzt sein
RRST/RMSG e RRST and RMSG must be set for US PRI
protocols.
COT BKNA d Verhindert CND für den Trunk wenn
gesetzt.
BKNA e Disable CND for specific trunk if set.
NCT d Erlaubt SS-NCT für angegebenen trunk
NCT e Enable SS-NCT for specific trunk.
ORRN d Aktivierung des Leistungsmerkmals ISDN-
PRI RN für spezifische NW-Sätze.
ORRN e Enable ISDN-PRI RN for specific trunk if
set.
DSSU TYP d TYP=BKANAL um einzelne B-Kanäle zu
aktivieren/deaktivieren
TYPE e TYPE=BCHAN to activate/deactivate single
B-Channels
KNDEF CACP d CAC Prefix (e.g. 101 for US)
CACP e CAC Prefix (e.g. 101 for US)
LDAT PUBNUM d Erlaubt ACPN (Additional Calling Party
Number)
PUBNUM e Enable ACPN (Additional Calling Party
Number)
SOCC d Equal Access bei LCR
SCCID e Equal Access using LCR
DIENSTSP d Ruf-für-Ruf Calling Service für Sprache
SVCVCE e Call-By-Call Calling Service for Voice
DIENSTDT d Ruf-für-Ruf Calling Service für Nicht-
Sprache
SVCNVCE e Call-By-Call Calling Service for Non-Voice
FACILITY d Ruf-für-Ruf Calling Service Parameter
FACILITY e Call-By-Call Calling Service Parameter
PUBNUM d Erlaubt ACPN (Additional Calling Party
Number)
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

PUBNUM e Enable ACPN (Additional Calling Party
Number)
LDPLN LDP d Platzhalter ‘J’ zur Kennzeichnung von CIC
digits
LDP e Wildcard marker ‘Y’ to indicate CIC digits
LODR SENDCIC d Das öffentlich Netz unterstützt Equal
Access
SENDCIC e Indicates Public Network supports Equal
Access
SENDOSA d Das öffentliche Netz unterstützt kommende
Operator System Access über Fuctional
Signalling
SENDOSA e Indicates Public Network supports receiving
Operator System Access using fuctional
signalling
LWPAR TYP/ d TYP=TMD und TMDTYP=MOS Zweige
TMDTYP sind für T1-Board zugeführt. (sehe T1
Adaption Leistungsmerkmal für mehr
Details)
TYPE/ e TYPE=TMD and TMDTYPE=MOS branch
TMDTYPE is added for T1 board. (see T1 Adaption
feature for more details)
SDAT PUBNUM, NPI, d Darstellung einer dem Teilnehmer
TON zugeordneten öffentliche Number für US
Provider
PUBNUM, NPI, e Additional Calling Party Number (ACPN) to
TON be sent to US Public Network
TDCSU GER d Neuer Geräte Typ S1COD für US PRI
Protokolle
DEV e Device Type S1COD for US PRI protocols
PROTVAR d Erweitert mit den 5 neuen US PRI Protokol
Varianten
PROTVAR e Enhanced with the 5 new US PRI protocol
variants
DEDSCC d Festgelegter Carrier Identification Code für
“IEC connected to” Anzeige(z.B. 0288 für
AT&T)
DEDSCC e Dedicated Carrier Identification Code
indicating the IEC connected to (e.g. 0288
for AT&T).
DEDSVC d Festgelegter (Voreingestelter) Calling
Service
DEDSVC e Dedicated (Pre-Provisioned) Calling
Service
FACILITY d Festgelegte Calling Service Parameter
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

FACILITY e Dedicated Calling Service Parameter
DITIDX d DIT Hotline Index zugewiesen in AMO-
HOTLN
DITIDX e DIT Hotline Index assigned in AMO-HOTLN
TCCID d Telephone Company Circuit Indetification
TCCID e Telephone Company Circuit Indetification
IGN d Interface Group Number
IGN e Interface Group Number
IID d Interface Identifier
IID e Interface Identifier
WABE KZP d KZP=PRITEST für PRI Loopback Test
Anrufem
DAR e DAR=PRITEST for PRI Loopback Test calls
ZAUSL NCT d Verkehrsmessung for erfolgreiche/nicht
erfolgreich NCT
NCT e Traffic Metering for successfull/
unsuccessfull NCT
N0056 d Anzahl sofortiger CNAM deliveries (in
Setup-Meldung)
N0056 e Number of immediate cnam deliveries (in
Setup message)
N0057 d Anzahl verspaeteter. CNAM deliveries (in
Facility-Medlung)
N0057 e Number of delayed cnsm deliveries (in
facility message)
N0058 d Anzahl erfolgloser call name deliveries (in
Setup-Meldung)
N0058 e Number of failed call name deliveries
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
publnet_en.fm
46 Public Network Exchange Signalling DTMF (Suffix

Dialling)
This feature enables special functions which require DTMF suffix dialling, e.g.
public services such as CITYCALL as well as Code-Calling with DISPLAY
OPERATION, Voice Mail systems and dictation equipment in private telephone
systems, to be used by all OpenScape 4000 voice terminals (ANATEs and
DIGITEs) via the public network exchanges. This means converting suffix-dialled
digits to DTMF signals on the exchange line, which is achieved by means of dial-
up converters for lines without DTMF signalling, or simply by seizing a specific
line with the necessary DTMF converter parameters by dialling the appropriate
route code when setting up a connection. Callers switched via these routes by the
attendant will not be able to use the converter functions. 
If a DTMF conversion route code is dialled, or a dial-up DTMF converter is called
up during an established call (suffix-dialling), DIGITEs can receive a notification
text on their displays. This text must be entered by means of an AMO. 
One SIU Type 2 module must be assigned for each LTG for receiving and
transmitting the DTMF signals.
• Assign a SIU Type 2 (Q2031-X1) to each LTG:

AD-BCSU:MTYPE=SIUP,LTU=number,SLOT=number,PARTNO=string;
Please also refer to the BCSU AMO description "Assigning a SIU".
In networked systems, the DTMF conversion is always carried out in the home
node of the station.
• Assign the code for the dial-up DTMF converter in the DPLN:
AD-WABE:CD=key-num,DAR=DTMFCONV;
• Assign the route code for the dial-up DTMF converter:
AD-RICHT:TYPE=CD,CD=key-num,SVC=param,DTMFCNV=SUFDIAL
or
CHA-RICHT:TYPE=CD,CD=key-
num,SVC=param,TYPE=DTMF,DTMFCNV=SUFDIAL;
• Assign the route code for the direct DTMF conversion route:
AD-RICHT:TYPE=CD,CD=key-num,SVC=param,DTMFCNV=FIX;
• Enter display notification for DIGITEs with AMO RICHT and the following
parameters:
– DTMFDISP = Parameter for defining display output options, with the

values:
WITHOUT no display output

FTEXT Displays text entered with RICHT AMO under parameter DTMFTEXT
A31003-H3170-S103-6-7620, 02/2019
publnet_en.fm
DIGIT Displays text entered with RICHT AMO under parameter DTMFTEXT
plus last dialled digit
DIGIT Displays text entered with RICHT AMO under parameter DTMFTEXT
plus last six dialled digits
– DTMFTEXT = Text for DIGITE display output, if parameter DTMFDISP

has been declared with FTEXT, DIGIT or DIGITS. Possible values:
alphanumeric string, up to 16 characters.
DTMF conversion is also possible for LCR routes. 

The appropriate commands can be found in the AMO RICHT description.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
REFTA Synchronization
47 REFTA Synchronization
The synchronization of TDM telecommunication networks has become very
important with their digitalization. Voice, fax and modem signals are digitalized
and transferred in real time. If the clock frequencies for digital coding of the A-side
and for decoding on the B-side are not synchronous a bit slip occurs after a
certain time, causing the loss or doubling of data. The resulting deterioration in
quality varies on the basis of the service. Depending on the difference in
frequency, the bit slip occurs after a certain time, i.e. at a certain bit slip rate and
leads to total loss of service. Frequency synchronization can be achieved in
various ways. The most cost-effective is master/slave synchronization, a
procedure employed worldwide.
As transmission is asynchronous in Voice over Internet Protocol (VoIP), there is

no need for synchronization plans here. However, the techniques specified here
still apply to the remaining TDM connections with the result that multiple island
networks often have to be considered. Each individual IPDA can have its own
REFTA.
The following two tables are provided to aid understanding. The first shows the
effect of a bit slip on the quality of the required service. The second shows the
space of time with regard to the frequency difference.
Service Effect
Encrypted data Without subsequent ARQ procedure no data can be decoded
after the bit slip
Video The picture is frozen for a few seconds, the sound produces a
loud "crack"
Digital data Data is lost or doubled,
the frame must be repeated,
data throughput reduced
Fax 4 to 8 scan lines lost (strips)
sometimes loss of connection
Modem Transmission errors for a duration of 10 msec to 2 sec,
data transfer within sometimes loss of connection depending on the transfer rate
voice band
Speech compressed Speech distorted, cracking sounds
Voice Sometimes a "crack"
Table 14 Effect of an individual bit slip
These tables show how quickly one small deviation in frequency can lead to
considerable loss in quality and to the breakdown of the connection. It is possible
to deduct the frequency difference and the most probable error cause from the
interval between bit slips. Frequency differences of 10 to the power of minus nine
and 10 to the power of minus eight are caused by free-running local exchanges
or tracking oscillators. Frequency differences of 1 ppm have been noticed with
smaller ISPBXs in hold over/free-run mode. Frequency differences greater than
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
Network Synchronization Plan
5 ppm are caused by free-running transmission devices, i.e. it is likely that a

synchronization chain is not thoroughly closed. Considerable frequency
differences occur if regulation loops are caused. However, it can take several
days for a regulation loop to result in an excessive frequency difference.
In the following table, E1 connections have a 125-µs buffer and 30 B channels.
T0 connections have a 24-µs buffer and 2 B channels here.
Frequency departure Interval between

delta f/f two bit slips
absolute in Hz (at 2 MHz) for E1 for T0
50 ppm 100 2.4 sec 0.48 sec
10 ppm 20 12.5 sec 2.4 sec
5 ppm 10 25 sec 4.8 sec
1 ppm 2 2 min 24 sec
1 x 10-7 0.2 20 min 4 min
1 x 10-8 3 1/2 h 40 min
1 x 10-9 1 day 7h
1 x 10-10 2 weeks 3 days
1 x 10-11 4 months 1 month
As long as the interface is synchronous and "jitter" and "drift" are within the standard
range, no bit slip occurs.
Table 15 Interval between two bit slips
As VoIP transmissions are digital but asynchronous, every connection must

incorporate a buffer to make up for minor clock deviations and larger delay
fluctuations, known as jitter. The buffer size is no longer in the µsec range but the
msec range.
47.1 Network Synchronization Plan

A network synchronization plan is required for the synchronization of
telecommunication and data networks. The master/slave principle is generally
used for network synchronization. Plesiochronous operation of systems or
network elements is also possible. In digital island networks with analog
environment or analog connection to other networks the network frequency does
not have to be absolutely accurate. It is sufficient for all the systems
interconnected in a network to operate synchronously in relation to one another.
However, if networks are digitally connected, absolute accuracy is essential if the
connection is to be operated in plesiochronous mode, since the bit slip rate must
be limited. Networks can be operated here in pseudosynchronous mode,
meaning that each has free-run accuracy of 1 x 10 exp – 11.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
Definition of Hierarchy Levels
47.1.1 Clock Hierarchy Plan

The specific requirements of the network provider and the customers result in the
best synchronization strategy which can, in turn, lead to certain decisions
regarding the network synchronization plan.
Example
1. All systems are to be operated synchronously at the Telecom network =
simple private network;
2. Private network with connection to one point and backup by GPS
3. = Larger network with large amounts of internal traffic;
4. Network with connections to various carriers and/or Telecom;
5. Network is to become a carrier network.
First, create a topological network plan. The clock hierarchy plan is derived from
the network topology plan, which must contain all route information, e.g.
distances, line types, transmission equipment. Then the network synchronization
plan can be created.
Transmission equipment and multiplexers must be included into the network

synchronization plan.
When creating a network synchronization plan the number of clock hierarchy

levels is important since they must be limited for the network to remain
synchronous in all operating and error situations.
47.2 Definition of Hierarchy Levels

The definition of hierarchy levels specifically refers to OpenScape 4000 in this
case. However, it can also be used for other transmission networks (with
necessary modifications). Division into levels is necessary so that a network can
function with good enough quality in the event of errors.
The connections between systems are clock transparent. The number of

repeaters is only limited by the jitter and drift values provided by the route and
which must comply with the input requirements.
( --> Connections)
The route clocking source should be investigated or determined in the case of

non-clock-transparent routes. For leased lines, this can be the master for both
systems at the connection’s endpoint. However, make sure that the connection
always has an external clocking source. Avoid a return to clock-transparent
operation during a failure without informing the network management centers
involved, since this procedure results in a forbidden clock loop.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
( --> Connections, AMO REFTA)
47.2.1 Synchronous Private Networks

(see Figure 64)
Metering begins in the local exchange (level=0) and commences at level=1 since
most private networks are connected to the public switched network and receive
their synchronous clock from it. All systems with a digital connection to the local
exchange that they use for synchronization are assigned level = 1.
All systems which are connected to level = 1 systems that they used for
synchronization are assigned to hierarchy level = 2.
All systems which are connected to level = 2 systems that they use for
synchronization are in hierarchy level = 3.
All systems which are connected to level = 3 systems that they use for
synchronization are in hierarchy level = 4.
This can continue up to level 4 if systems on the same level are to be

interconnected. The number of levels can exceed four in systems that are
simply "cascaded". The OpenScape 4000 standard clock generators allow about
seven or eight levels without any loss of synchronism under the usual boundary
conditions e.g. jitter, drift and phase hits. The configuration of more than five
levels is not recommended, however, as propagation times in the network are
excessive for connections to public switched networks.
Once all systems have been assigned to a level, the resulting number of levels
must be determined: If there are more than two levels with tie trunks, networking
clock generators should be used on the first level. If there are more than three
levels with tie trunks, the network clock generators should be used on the first and
second level. If the systems are only cascaded without tie trunks, a network clock
generator should be used from the fifth level in the first level and on the sixth level
in the first and second level.
( --> Selection of clock generators)
47.2.2 Plesiochronous or Pseudosynchronous

Private Networks
(see Figure 64)
Independent private networks which start with an internal clock master (an
OpenScape 4000 system is designated as the network clock master) or private
networks with their own standard clock (the OpenScape 4000 system with an
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
external clocking source from a standard clock is designated master) are

plesiochronous or pseudosynchronous with an exactness of 1 x 10 to the power
of minus 11 with regard to other networks to which they are digitally connected.
( --> Special cases, SDH)
The system designated as clock master in the network or which is provided by the
standard clock is referred to as level = 0. Then the same procedure used for
synchronous networks is applied for the clock hierarchy levels. If the network
comprises more than four systems, the master system should have a networking
clock generator. This also applies to private networks synchronizing onto the
public network using an SASE but change to an autonomous clocking state in the
case of trunk errors (the SASE changes to hold over or free-run mode or
synchronizes onto a backup clock normal).
( --> Selection of clock generators)
47.2.3 Limiting Level Numbers

The limit of four levels has been introduced so that double faults on the
synchronization path can be sustained with no loss of synchronism. This
limitation is justified by the fact that the drift must not become too great; the drift
is not attenuated in the different stages, but can in fact even be increased.
There are other important (quality) criteria independent of network

synchronization, which can lead to a limitation of levels.
The "round trip delay", for instance, must be taken into account without any
special measures for echo suppression. Then a maximum of five levels is
reasonable.
47.2.4 Reducing Level Numbers

It is easy to reduce the number of levels by wider networking. However, this is
sometimes not possible for topological and/or economic reasons.
If necessary, the number of levels can be reduced by synchronizing the

transmission equipment (the transmission network) from the system on level = 1
or = 0. In this way, all systems directly synchronized by the transmission
equipment are assigned to level = 2 or = 1. Due to the fact that a connection can
go from one system to a third bypassing the second, the actual route can become
longer. This is only possible since the route length of the transmission can,
theoretically, be up to 27,000 km according to the standards. However, this shifts
responsibility for network synchronism to the transmission system. It should also
be noted that in the case of intelligent transmission networks - where automatic
changeover includes synchronization - the transmission network must be
included into the network synchronization plan and into network
management. Therefore, the network must be treated as a separate hierarchical
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
level as known from the OpenScape 4000 system. This treatment reduces the
number of possible OpenScape 4000 levels; for the transmission equipment
networking clock generators may become necessary.
( --> SDH, Special cases)
Ortsamt Ortsamt Ta ktnormal für HiPath

pseudosynchronen Ta ktmaster
Ebene 0 Ebene 0 Betrieb Ebene 0
89.. 89.. 85.. 85..

79.. 75..
HiPath HiPath HiPath HiPath
0 0
Ebene 1 Ebene 1 Ebene 1 Ebene 1
69.. 69.. 65.. 65..

59.. 55..
HiPath HiPath HiPath HiPath
0 0
49.. 49.. 45.. 45..

39.. 35..
HiPath Hicom Hicom HiPath
0 0
29.. 29.. 25.. 25..

19.. 15..
HiPath Hicom HiPath Hicom
0 0
9.. 5..
HiPath HiPath
Ebene 5 Ebene 5
9 5
HiPath Hicom
Ebene 6 Ebene 6
Figure 64 Hierarchy levels with OpenScape 4000/HiPath 4000 networks
Annotation 1: Networking clock generator in level 1 or 1 and 2 necessary
Annotation 2: Connecting lines _______ represent clock-transparent digital

connections between the systems. Analog and VoIP connections must not be
displayed as connecting lines in the clocking plan.
Annotation 3: The numbers at the connections between the systems are a

suggestion for priority assignment in the reference clock table (REFTA)
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
Connections
47.3 Connections
The term "connections" refers to all digital connections between the systems, e.g.
trunk connections and tie trunks, regardless of the transmission equipment.
Although VoIP connections are digital, they do not transmit any clocking signals
(asynchronous transmission). Time information that can later be used for
synchronization (NTP, PTP) can only be transmitted with specific protocols - even
over IP connections.
47.3.1 Synchronization Interfaces

All digital connections can be used for synchronization. The following interface
types exist:
ATM: STM1 or OC3 (bit rate 155,52 Mbps);
PMA: E1 (S2M, S2M FV, PCM30) (bit rate 2,048 Mbps), T1, T1.5 Accunet (bit rate
1,544 Mbps);
BA: T0, S0, U-2B1Q (bit rate 160 Kbps) and data interfaces in accordance with
ITU X.21 with bit rates between 1,200 bps and 64,000 bps.
Depending on the network topology not all interfaces on the different levels are
allowed as tie trunk connections because the elastic buffers have different sizes:
Level Admissible tie trunk connections

1 S1, T1, S2, PCM30, STM1, S0, X.21
2 S1, T1 *, S2, PCM30, STM1, S0
3 S1, T1 *, S2, PCM30, STM1
4 S1, T1 *, S2, PCM30, STM1
* : In the case of network connections routed exclusively via AT&T’s T 1.5

Accunet service only one level with T1 tie trunk connections is allowed
because the network jitter/drift may be up to 90 µsec high, but the T1 interface
components have only +/- 125 µsec buffers.
In the OpenScape 4000 system, all available digital interfaces for synchronization
can be set if the reference clock table size is matching. This makes it possible to
deal with not only simple failures but also double and quadruple errors in a
predefined manner. Always make sure that automatic changeover of reference
clock routes in a network do not cause clock loops. Experience with many
networks shows that leased lines used for tie trunks often cause problems
because it is necessary to determine whether or not they are clocked. Also clock
quality and availability of local exchange trunks is normally better than the quality
and availability of leased lines.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
AMO REFTA
47.3.2 Clock-Transparent Connections

All wire connections, repeater chains or radio relay connections with which the
clock can be transmitted via the interface together with the data stream are
referred to as clock-transparent connections. Clock-transparency must be valid in
both directions. PCM2 connections, for instance, are clock-transparent in one
direction only. The number of repeaters is only limited by the jitter and drift values
provided by the route and which must comply with the input requirements. This
must always be researched and checked for leased lines. Unstructured leased
lines (i.e. without frame) are normally transparent if PDH technology is used. The
procedure in figure is based on the assumption that transparent connections are
used for the assignment of the priority values.
47.3.3 Connections with External Clock

The route clocking source should be investigated or determined in the case of
non-clock-transparent routes. For leased lines, this can be the master for both
systems at the connection’s endpoint. However, make sure that the connection
always has an external clocking source. Avoid a return to clock-transparent
operation during a failure without informing the network management centers
involved, since this procedure results in a forbidden clock loop that goes
unnoticed at first. Structured leased lines always have an external clocking
source. Check the clocking source and routes to which the clock is distributed for
every multiplexer in the network.
External clocking can generally be assumed when using SDH technology. The
network synchronization plan is then drawn up in compliance with the switching
and the transmission equipment. Check for SDH multiplexers if the interfaces are
set to "retiming" and if the "retiming" is to be accepted by the OpenScape 4000
system. This function requires the connection of the SDH multiplexer’s clocking
port (T4) to the OpenScape 4000’s front reference port using a special cable. For
information on the advantages of transferring the "retiming" function to the PBX,
see Section 47.5.7, “SDH”.
47.4 AMO REFTA

The AMO REFTA is used to edit the reference clock table (REFTA). The system
references this table which contains the interfaces used for synchronization with
the corresponding priorities. The priorities define which interface and priority must
be used for synchronization for every system. It also defines the sequence in the
case of possible failures. Also the interfaces are defined which are never used or
only for special error cases occurring in the network during a synchronization
process.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
AMO REFTA
The safety equipment processes the error counter according to a patented

procedure. The error counters generally provide the network provider with
important information about the layer-1 quality of the network connections. The
reference clock table provides a complete overview of the synchronization state
of the system. Comparing different reference clock tables with the network
synchronization plan provides a quick overview of the network situation with
regard to synchronization and layer-1 errors.
The points are weighted in the error counters according to their importance for the
synchronization quality and increased for transmission if the errors occurred in
layer 1. The error counters are reduced by 5% at hourly intervals as long as the
system is synchronous. The error counters therefore always show quality
differences for the interface and thus for the connected equipment and routes in
relation to the last hours. Serious errors remain visible over a longer period of
time (1 to 2 days). As soon as the error counter for an interface is no longer 0, the
"History error messages" file containing error messages for the relevant
interfaces should be consulted. The OpenScape 4000 error messages can be
used to find network errors - even in the transmission network and transmission
equipment.
A bit slip, for example, is penalized with 150 points, a short interrupt < 1 sec with
1,500 points, a longer interrupt with 1,500 points x seconds, an excessive
frequency departure during regulation start or an excessive jitter with 32,000
points. A record contains 16,000 points at startup. A record is not accepted - even
if it has the highest priority - once the error counter exceeds 42,000 points. A
record of this kind is accepted after a minimum of 30 minutes and "paroled" with
error points below 42,000 if it has the highest priority.
If no records can be referenced (during tests) because of error counters, all error
counters are halved.
In special cases, the barring column (= YES or = NO) provides a means of direct
access for quick intervention in network synchronization. It is mainly used in rare
network errors to turn the synchronization direction without the need to switch off
the remaining interfaces. Setting the disable function to "YES" for a record with a
certain priority has the same effect as setting the priority to 0. As priority changes
from and to zero are possible by simply switching the record on and off, turning
the synchronization direction in these rare network errors by switching on and off
the interfaces would be unreasonable.
Clock supplier: The selected interface used for synchronization is marked "X"
in the REFTA.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
AMO REFTA
Only one clock supplier can be active for LTUs 1-15. As LTUs 17-99 (IPDAs) are
connected asynchronously via LAN, synchronization is not possible with the
system’s central clock generator. Consequently, a separate IPDA can be selected
in each interface and used for synchronization. This is also marked "X" in the
REFTA.
IMPORTANT: If digital trunk or tie trunk circuits are operated in an access point,
the AP’s local clock generator must be synchronized with the network clock ("CO
clock").
47.4.1 Value Range of Priorities

The value range for the priority is between 1 and 90, the higher value also means
the higher priority. A priority of 0 prevents this interface from being used for
synchronization. In the case of special errors, interfaces which may be used
temporarily for synchronization must be assigned an appropriate priority and the
barring must be set to YES. Thus the synchronization direction can be turned
without the necessity to switch the route on and off as is the case with the change
of priority =0. Before changing barring from YES to NO, make sure that it has
been changed from NO to YES on the other side. This priority assignment is to
prevent the fatal error of a synchronization loop with regard to all route failures.
47.4.2 Priority Assignment

It is advisable to start priority assignment with priority = 89 at the routes to the
local exchange level (=0). To differentiate between local exchange routes and
internal connections to the clock master start here with the value = 85
(see Figure 64). Interfaces of the same value must be assigned the same priority.
Steps of 1 or 2 are recommended for interfaces with different values. Connections
with the same priority are selected automatically according to their quality
(REFTA error counter). In case of a failure the next connection is selected, but
never the last one. If you want to return to a certain interface after it has been
proven OK it must be assigned a priority value which is 1 higher than all others.
A return to the interface is possible after a minimum of 45 minutes and if the error
counter is lower than 42,000 points. Figure 1 shows the graduation of priorities as
a suggestion for a network structure. The graduation of the values in the
reference clock table according to the hierarchy levels simplifies the assignment
of the individual REFTA printouts and therefore are processed for the Network
Management Center. It is also helpful to enter the individual interface layers of the
REFTA in the network synchronization plan for easier assignment.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
AMO REFTA
With the same interface type priorities should be assigned in the order alternate
routing, wire and radio and then, if necessary, graduated by distance and number
of repeaters. Interfaces with different bit rates provide different quality. This fact
should be taken into consideration when assigning priorities. The order is:
in ROW: STM1, E1, PCM30, BA (U-k0, S0, U-2B1Q), X.21;
in USA: OC3, T1, T1.5 Accunet, BA (U-2B1Q)
For the assignment of priorities for tie lines the systems of one clock hierarchy
level are sorted. The system with the most paths to the higher level is designated
System 1. For this system the disable function is set to YES at the tie trunk
interfaces to System 2 and the system is assigned a lower priority than provided
for in System 2 for this connection. The system with the lower values corresponds
to the zero. This allows turning the synchronization direction for this important
system in the network. For all other tie trunk connections the priority is set to 0.
The procedure is the same for System 2 and all other systems.
However, all possible network errors must be considered. Particular attention

should be paid to the fact that clock loops do not occur in the event of errors or
automatic changes - not even in scenarios with three or four systems.
47.4.3 Networks with Several Masters

If a system is connected to different masters (of the same level) the quality of this
system should be taken into consideration when allocating priorities. This can
mean that higher priority is assigned for the exchange (system/carrier) with the
most frequent or most important (data) traffic. Several masters may not always
be synchronous or pseudosynchronous in relation to one another. There is, for
instance, no error message reporting via the trunk that the local exchange
switched to hold over mode. Up to now there is no carrier-wide network
management. The effects in the private network only show as bit slips. It is helpful
to mark the existing and possible plesiochronous interfaces in the network
synchronization plan as such. This procedure helps quick and precise error
diagnostics if bit slip frequently occurs on these lines. In important networks or
network elements these problems can only be solved using an SASE.
( --> Clock generator selection)
47.4.4 AMOs LWPAR & SYSPAR

The AMOs LWPAR and SYSPAR are used to set parameters effecting
synchronization. The "Master" parameter, however, is not used for
synchronization but for master/slave assignment for layer 2.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
AMO REFTA
The "SMD" parameter, on the other hand, effects synchronization. If SMD = YES
this record will never supply the reference clock, even though it has a certain
priority in the REFTA and would have been selected by the safety equipment.
The "Qual" parameter switches the CRC safety for the 2 Mbps frame on. This
enables monitoring of the bit error rate and allows switch-off after 10 SESs, for
instance.
47.4.5 Clock Generator and Front Reference

The CLOCK BOX (see Section 47.5, “Selection of Clock Generators”) and the
"front reference" or "frontref" (external clocking source directly on the clock
generator) are independent of each other and fully integrated into the security
equipment.
The CLOCK BOX must be configured as AECB (also applies for AICB, SASE,
etc.) with the AMO REFTA, i.e. the required clock generator class can be
selected. The clock generator of the simple MTSCG is in standard class 38 by
default. If a working AECB is connected, class 68 can be selected for the
networking clock generator (like NCG-X). If a CLOCK BOX with high free-run
exactness (better than 1 x 10 to the power of minus eight) over a longer period of
time is used, class 78 can be set. This class always narrows the trimming range
to 0,1 ppm absolute. Setting the class does not effect or require a reset of the
MTSCG board. Therefore, no duplex switch is necessary. Changeover of the
class during operation results in a brief switch-off of a configured (line) reference.
If a CLOCK BOX is used, the state of the clock cable to the CLOCK BOX and the
status of the background reference (OCXO) are also monitored. All changes are
reported to the security equipment and are available for the NMS.
The "frontref" is part of the reference clock table. Its priority can therefore be
freely selected. The frontref status of a system is continuously monitored,
regardless of whether it is used for synchronization. This applies for the A and B
controllers independently of each other.
47.4.6 Changes with cPCI Control

The situation illustrated in Section 47.4.5, “Clock Generator and Front Reference”
also applies to the OpenScape 4000 based on the cPCI controller with the
following changes: The clock generators are now located on the RTM modules
and can be reached externally via the MCM module. Consequently, there is now
only one connector for the "external clock box", which can also be used to
connect the "frontref". The input clocks are distributed from here to both clock
generators or the output clock originates in the active (master) clock generator.
The "external clock box" interface on the MCM is mechanically and electrically
identical to that of the MTSCG.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
Selection of Clock Generators
47.5 Selection of Clock Generators

Various different clock generators are available in different price categories. The
two most important criteria when choosing a clock generator for OpenScape 4000
systems are:
1. Exactness of free-run mode
2. Performance for network operation
47.5.1 Exactness of Free-Run Mode

The accuracy of free-run mode in clock generators for normal ISDN PABX
networks is important for systems which are to operate as the master of a digital
island, i.e. for plesiochronous or pseudosynchronous private networks. As free-
run accuracy does not have to be very high in the first case, the small clock
generator with +/- 32 ppm is sufficient. The standard clock generator (class 38)
offers +/- 10 ppm and the networking clock generator (class 68, 78: +/- 5 ppm with
AICB or with an external clock box: 1 x 10 to the power of minus nine to 10 to the
power of minus eleven). This accuracy is guaranteed for fifteen years under all
operation conditions. Note the exact definition of free-run accuracy when
comparing models.
47.5.2 Performance for Network Operation/Normal

Clock Generators
Hierarchical levels are important when choosing clock generators because
systems with multiple successive layers encounter a large amount of transit
traffic. Therefore greater clock stability must be ensured to counteract the
increased probability of malfunctions, see ISO standard 11 573 or ETSI or TIA
standards. Clock generators for transit systems (e.g. MTSCG+RTM type + clock
box in class 68 or 78), moreover, have a longer time constant than standard clock
generators (e.g. MTSCG/RTM type in class 38) which in turn have a longer time
constant than clock generators for smaller systems.
IPDA (HG3550) uses class-38 clock generators which can no longer have an
external clock box but which can be configured with a "frontref" as of OpenScape
4000 V4 (R1). This is important in connection with Cordless and ISS (i.e.
seamless handover) because the time information for ISS can also only be used
in the case of precise clocking from the GPS.
For reasons of stability, the time constants in a network should be progressively

shorter.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
The "Networking clock generator" feature (class 68 or 78) provides a system

with a more accurate frequency in free-run mode, a more stable hold over mode
for a longer period of time, a longer time constant for the PI regulator, a more
thorough check of the reference frequencies, faster recognition of reference
frequency changes and a trimming range smaller than with the standard clock
generator (class 38). For the "Networking clock generator" feature to work, an
AECB, an AICB or an SASE must be connected to the front panel of the MTSCG
board or the MCM module in the cPCI controller. The clock generator can then be
set to the corresponding class using the AMO REFTA. Class 38 corresponds to
the standard clock generator. Classes 68 and 78 are networking clock
generator classes, the class 68 corresponding to the previous NCG-X and class
78 providing a further limitation of the trimming range, thus making the system
resemble an SASE, even replacing an SASE in some cases.
Values Standard clock Networking clock

generator generator
Free-run, 10 x 10 -6 4,6 x 10 -6 .. 1 x 10 -10 1)
(delta f/f) for 15 years
hold over mode 4 x 10 -9 2 x 10 -9
(initial offset)
(3 days)
(10 days)
Time constant approx. 15 minutes approx. 1 hour
(l-part)
Trimming range (absolute) min. +/- 32 ppm min. +/- 10 ppm
Trimming range for ATM min. +/- 20 ppm min. +/- 5 ppm
Trimming range for class 78 -- min. +/- 0.1 ppm
Table 16 Quality differences for clock generators
1) depending on the external clock box used
47.5.3 Hold Over Mode

In hold over mode the clock generator remembers the frequency onto which it
synchronized. In the event of a failure of all possible reference sources the clock
generator can then operate with the last set frequency in synchronous mode.
The standards do not require this function for simple clock generators. In the
event of failure of all reference sources, the clock generator can switch to its own
average value which can be several ppm off.
A real hold over mode has been implemented for even the simplest, smallest
OpenScape 4000 clock generators. With increasing quality this function works
even more accurately with standard and networking clock generators. Not only
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
the frequency at the moment of failure is considered (which can be off) but an
average value of the last 30 minutes and the last 24 hours is calculated which is
then slowly passed by the system in a smooth changeover. With networking clock
generators this hold over frequency is stored in a non-volatile memory to prevent
its loss during power failure or change of boards. Also, the frequency accuracy
during hold over mode relies especially on the temperature dependency of the
quartz oscillator used. For standard clock generators, temperature compensated
oscillators (TCVCXO) are used with a frequency deviation of only +/- 1 ppb over
the entire temperature range. For the background reference of the networking
clock generators, at least one temperature stabilized oscillator (OCXO) is used
which a frequency deviation of only +/- 1 ppb over the entire temperature range.
47.5.4 ATM
The free-run accuracy must be considered in the case of ATM because the
interface function is not higher (as is the case with PMA with +/- 50 ppm and BA
with +/- 100 ppm) than the free-run accuracy standard of the clock generators
with +/- 32 ppm for stratum 4 or +/- 50 ppm for ISO 11 573 class III.
The STM1 or OC3 interface has been designed for frequency deviations of +/- 15
or 20 ppm.
The OpenScape 4000 standard clock generators meet these requirements in

free-run mode. The trimming range is also affected in that it is automatically
limited by an ATM interface board. Synchronization on a (drifting) local exchange
could be stopped with the error message "BAD CLOCK" to prevent a private ATM
interface from failure.
47.5.5 External Clock Box (AECB, AICB, etc.) for

OpenScape 4000
The MCM module on the cPCI controller features a port for an external clock box
where an AICB, AECB or SASE can be connected. It should be noted that this
interface corresponds mechanically and electrically to that of the MTSCG.
The external clock box must be configured as "AECB" using the AMO REFTA
for inclusion in network management.
47.5.6 Network Clock Supply

The standard clock generator suffices for clock supply of a small private network
in an analog environment. The default clock generator is sufficiently precise even
for the clock requirements of cordless DECT. If better clock quality is required for
the network, a networking clock generator must be installed in the master system.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
It already has the Stratum 3 clock quality, i.e. the quality of a USA CO, and the
frequency stability and hold over function of an ITU local exchange, but not the
same free-run accuracy. If free-run accuracy is important for the network or if
independence from Telecom/the carriers is desired, an SASE must be installed in
the master system and, in larger networks, also on the first level in front of the
OpenScape 4000 clock generators. This provides clock quality of a local
exchange or means Stratum 2 level.
As PDH networks are hardly ever used anymore and even SDH networks are
slowly being replaced by MPLS networks and thus by VoIP technology, the
demand for networking clock generators in OpenScape 4000 systems is
decreasing. Clock distribution has been shifted to the transmission network in
SDH networks. Responding to these changes is simply done in OpenScape 4000
by using the external clock box less and the frontref more. It is easy to connect to
each T4 output with the special cables for the cPCI or IPDA shelves. From the
clock perspective, this means there is no longer an OpenScape 4000 master
system in the network.61.6 SDH, Cordless - CMI (DECT) and ATM
47.5.7 SDH
For the combination of an OpenScape 4000 with SDH transmission equipment
the following must be considered other than with PDH equipment:
Transmission within the SDH (Synchronous Digital Hierarchy) is synchronous

with the SDH network clock on the levels STM - n. Data rates below 155.52 Mbps
are mended but differently than with PDH (Plesiochronous Digital Hierarchy).
Data streams from the SDH< 155.52 Mbps can or could be supplied with the SDH
network clock. This is called "retiming". "Retiming" can be performed both in the
SDH multiplexer or in the OpenScape 4000 system. For retiming in the
OpenScape 4000 system, a clock connection from the SDH multiplexer (port T4)
to the OpenScape 4000 front reference port must be established (special cable).
The front reference is then set using the AMO REFTA and its priority adjusted
correspondingly for the OpenScape 4000 system to synchronize onto this front
reference. "Retiming" is then automatically executed in the OpenScape system.
The advantage only exists as long as an overflow of the "retiming" buffer leads to
a bit slip and not to a total loss of frame synchronization with a complete
disconnection of all B channels as the SDH multiplexer has only 40 µsec buffer
depth for retiming, while the OpenScape 4000 PMA interfaces have a buffer of +/
- 125 µsec.
SDH equipment without "retiming" behave identically to PDH equipment in the

case of 2-Mbps interfaces, i.e. the connections must be treated as clock-
transparent (PDH). Priorities for the OpenScape 4000 reference clock table
remain the same.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
The fact that the SDH network should be operated synchronously to the
Telecom/carrier clock at this point should be considered when planning the
network. If an SASE (tracking oscillator) is connected, further T4 ports with 2.048
MHz for the T3 clock ports of the PABX equipment are used in addition to the
clock for the front reference.
As soon as "retiming" is used, clock distribution in the network must be

redesigned since the SDH network is important for clock distribution.
In case of "retiming", the SDH network must be able to receive the master clock
(PTT or SASE) from two independent ports. Thus the SDH network has the same
clock supply as an OpenScape 4000/HiPath 4000 network with clock-transparent
(PDH) connections and minimum meshing. The clock is then distributed in the
SDH with the STM-n level. Reconfigurations during interruptions etc. are
automatically performed in the SDH network (comparable to the OpenScape
4000/HiPath 4000 network planning with the AMO REFTA). The 2-Mbps
connections between the OpenScape 4000 systems in the network cease to be
clock-transparent. All OpenScape 4000 systems connected to the SDH network
are operated as clock slaves on the SDH network. OpenScape 4000 tie trunks on
the same clock hierarchy level can no longer be used as substitute routes but are
allocated a priority unequal zero on both sides. This puts these ports on the
OpenScape 4000 systems on one level with the direct clock paths.
Normal transmission jitter is not greater with SDH than with PDH. During
reconfigurations in the network or with plesiochronous connections between
various SDH islands the so-called "pointer adjustment" jitter with an amplitude
of up to 5 µsec can appear in addition to the normal jitter. Both the OpenScape
4000 interfaces and the clock generator can handle and accept this additional
jitter and drift caused by SDH.
Network synchronization and SDH equipment planning should be performed in

conjunction with personnel representing the relevant transmission systems.
47.5.8 HiPath Cordless (CMI)

Free-run accuracy with Cordless DECT must be considered because the
transmission equipment (DECT) requires an absolute accuracy of +/- 10 ppm for
the entire temperature range and +/- 5 ppm for the limited temperature range. The
small clock generator suffices as long as Telecom or any equivalent carrier
supplies the system via digital interface. The standard clock generator should be
used for "island" operation over a longer period of time. This is provided therefore
for all OpenScape 4000 systems and the IPDAs.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
47.5.9 Network-Wide Synchronization for Cordless

(ISS)
The "network-wide seamless handover" function requires an exact phase
relationship between the basic stations, especially in connection with data
applications. The deviation of the DECT frame at the air interface must not be
more than +/- 2 µsec between the basic stations for "seamless handover".
Frequency economics also require this in-phase condition. Due to their
synchronization over TDM connections, OpenScape 4000 systems are
frequency- and phase-synchronous in relation to one another. However, every
system has its own frame clock phase relationship because the different
propagation times of the digital interfaces are compensated by frame adjustments
on the receiver side. The PCM frame clock (8 kHz) of various OpenScape 4000
systems can therefore have any phase relationship of module 125 µsec in
relation to one another and cannot be used for network-wide synchronization of
the DECT basic stations. Instead, GPS receivers are used which deliver a 12-
sec pulse from 1 or 2 measuring boards to the master SLMC board of each
system. The pulse phase relationship must be absolutely exact with a deviation
of +/- 500 ns. This exact phase time information is then evaluated and measured
in relation to the system clock. The CMI basic stations receive setting information
from the derived value so that they can keep their frame clock at the air interface
in relation to one another with a deviation of +/- 2 µsec. This procedure provides
the hardware for network-wide "seamless handover".
In the case of VoIP, please note that TDM connections are no longer needed to
connect the systems, but that IP trunking can be used exclusively. It has been
demonstrated that in the case of Cordless with ISS, direct external system
clocking via the 2.048 MHz clock from the GPS receiver increases stability more
than synchronization over tie trunks. It is therefore strongly recommended to
always use the "frontref" supplied by the GPS receiver.
A Datum GPS receiver has been certified for ISS V1.0 for this. The GPS receiver
also has a V.24 output to which a cable to a OpenScape 4000 input can be
connected (thus making the OpenScape 4000 UTC compliant).
If a receiver of this kind or an SLCSM fails in 2008 or later and cannot be repaired
or replaced, the relevant system will have to be upgraded to ISS V2.0. The
network supports combinations of V1.0 and V2.0. When replacing a GPS
receiver, the aerials must also be replaced but the aerial cable can continue to be
used. When exchanging SLCSM for SLCSS, both master and standby have to be
replaced. The cables can still be used.
A Meinberg GPS receiver (available from Unverdross-Technik) has been certified

for ISS V2.0. The time output here is suitable for SLCSS measurement modules,
the clock output is suitable for "frontref" (special cable). A suitable NTP time
normal for this receiver can also be ordered so that time is supplied to the
systems, servers and terminals via the LAN.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
47.5.10 ATM Interface (STMA Board)

The STMA board provides the first ATM interface in a system. If an STMA board
is configured, the security equipment narrows the trimming range of the clock
generator during startup to approx. +/- 15 to 20 ppm. The clock generator ensures
that any private ATM interface behind a PABX system always works. The
OpenScape 4000 clock generator can therefore cancel synchronization onto the
master (e.g. the local exchange) and issue the message "Trimming range
exceeded" although the frequency departure is still within the ISDN standards. As
with a lot of error messages from the OpenScape 4000 clock generator, the error
does not lie within the OpenScape 4000 system but outside it.
Together with the ATM, many new systems currently enter the market which
originated from the data world and do therefore disregard "clocking" as it is
required by the ISDN/PCM world. In future there will be more and more ATM
systems also suitable for the CBO. The present ATM systems must be checked
to see if they can transmit clocking for a CBO or not. If the result is positive, the
next question arises: whether the ATM systems have a priority list for various
ports, i.e. can be regarded as an own hierarchy level like a OpenScape 4000
system. If the result is negative, connections via the ATM system must be treated
like analog connections, i.e. they are not mentioned in the network
synchronization plan. This must lead to appropriate conclusions since there are
fewer substitute routes, for instance, for synchronization. In future, however, there
will be no differences between transmissions via PDH, SDH and/or ATM.
47.5.11 Special Cases

For larger synchronous networks with one master system (with SASE) and
peripheral systems connected to local exchanges by BA, check if the small buffer
of the BA suffices for the jitter and drift of all possible networking situations. If in
doubt, system synchronization from the local exchange is preferable. In this case,
the connection, which in the event of error can show bit slip, drifts from the
perimeter into the private network. The BA, however, remains slip-free in normal
operation because the buffers of the internal PMA interfaces are sufficient in size.
47.5.12 Front Reference

In the case of OpenScape 4000 with a cPCI controller, the front reference can
continue to be connected to the MCM module and the "external clock box"
connector with the special frontref cable (S30267 – Z319 – A150). It is distributed
to both clock generators on the RTM module. Configuration with the AMO REFTA
remains unchanged.
The front reference in every IPDA can also be used. If the cordless coverage
areas of several nodes overlap, (e.g. of several IPDAs), these nodes must be
synchronized with ISS in order to avoid dropped call in the overlapping area and
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
to enable switching nodes during a call. All base stations in a continuous

coverage area of a cordless system must be synchronized according to the DECT
requirements to enable a seamless handover, regardless of whether they are
connected to a IP access point (AP 3300 IP, AP 3700 IP) or a host system frame
(AP 3300, AP 3700). To do this the IP access points must receive synchronization
signals from a GPS receiver. The AP3x00 IP IP access points with the NCUI4
control board enable the handover between base stations connected to two IP
access points.
To date the ISPA requires a TDM line as a base clock and the GPS clock for
advanced settings for ISS. By using the front reference, the TDM line does not
need to be used as a clock supplier. The clock is now provided solely from the
GPS receiver. The GPS receiver clocks once via the NCUI front reference input
and SLC24 clocks via the SLCSS board.
A cluster of several IPDAs at one site can be supplied to by the clock distributor
via a GPS receiver.
The GPS signal ensures the GPS receivers are synchronized and therefore also
that the IPDAs or the IPDA clusters are synchronized. If an IPDA cluster has no
overlapping area to a cluster clocked by another GPS receiver or separate IPDA,
this cluster can operate without a GPS signal. This means that the receiver
generates a dummy signal to syschronize in a cluster but does not require a GPS
antenne.
The AMO REFTA can be used to configure and prioritize the frontref separately
for every IPDA.
The frontref that can be used to operate OpenScape 4000 satisfies the UTI G.703
§ 13 recommendation with wave resistance of 120 ohms.
Administration
ADD-REFTA:TYPE=FRONT,PRI=89,LTU=17;
CHANGE-REFTA:TYPE=FRONT,PRI=90,LTU=17;
DELETE-REFTA:TYPE=FRONT,LTU=17;
( --> Section 47.4.5, “Clock Generator and Front Reference”)
47.5.13 S0 Interface not Permanently Active

Layer 1 of a trunk connection must be permanently active for continuous
synchronization of a PBX. With OpenScape 4000 systems, interfaces to the clock
master are only started after the clock generator reports sufficient synchronism.
For instance, in France the S0 interface cannot be set to permanent activity. The
timers on the trunk side, on the other hand, are set for insufficient intervals for the
OpenScape 4000 system to respond in order to synchronize.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
There may be cases in other networks where it is necessary for interfaces to the
clock master to be immediately operable although synchronism is still insufficient.
Therefore the AMO REFTA was prepared to assign the parameter "Ready
despite asynchronous mode" to any interface if necessary. This parameter is not
set by default. If it is set for an interface, this interface enters the "Ready" mode
immediately, even after an HRST, without waiting for the "Synchronous" message
from the clock generator.
If OpenScape 4000 systems are networked with S0 connections, the parameter

SMD must be set to "NO" (despite priority = 0) in the AMO SYSPAR. This sets the
layer 1 of this BA to permanent activity. Both sides of the connection must be set
to "Trunk".
47.5.14 Setting the REFTA Error Counter to 16 000

An interface is only selected as reference clock source if
• it is set to TMD and is Ready,
• it has the highest priority and an error counter < 42 000,
• it has the lowest error counter for the same priority level.
During integration tests, startup and switchovers for error diagnostics the error
counter can quickly rise to 65 535. Since it is only reduced by 5%/h in
synchronous systems, the established procedure was to remove and re-install
the peripheral board. This resets the error counter to the starting value of 16 000.
A REFTA command has been implemented to set the error counter to 16 000
without affecting the peripheral board or having to handle it.
47.5.15 T4 Clock Output/Previously T3ab, APT3

Adapter
In the past, a T4 clock output based on TU G.703 § 13 with wave resistance of
120 ohms was frequently required for clocking transmission equipment. An
adapter for a shelf used to exist for this and was followed by the AECB or AICB.
The demand for this clock is very rare these days. This is why it no longer exists
in the OpenScape 4000 with cPCI controller.
An SASE/SSU is often required for the networking clock generator function. The
SASE then provides all T4 clocks for transmission equipment and for the
OpenScape 4000 front reference. This output is therefore no longer required.
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
Notes/Experience
47.6 Notes/Experience
There are many ways in which a route providing the reference clock can fail. In
the simplest case it is only interrupted and the clock immediately switched off.
The clock generator then switches to hold over mode. Regulation commences
automatically in the case of interruptions of under 1 sec. An appropriate message
is entered in the REFTA error column. If the interruption is longer than 1 sec., the
security equipment is switched on. A waiting period of 1 minute is observed for
the line to return and then regulation is restarted. If the interruption is longer than
1 minute, the next line with a suitable priority and error counter is selected from
the REFTA and switched on.
Error cases with uninterrupted lines and deteriorating quality are more difficult.
These could be caused by a repeater that is about to fail but is still delivering its
own - internal inexact - clock or by external interruptions that result in higher jitter.
A certain period of time can elapse before the clock generator detects the quality
deterioration or the frequency departure. The "BAD CLOCK" error message
provides valuable information.
If S2 or S0 lines are to supply the reference clock, SMD must be set to "NO" in
the AMO SYSPAR. This sets the interface to TMD = Trunk Mode Digital.
If OpenScape 4000 systems are networked with S0 connections, the parameter

SMD must be set to "NO" (despite priority = 0) in the AMO SYSPAR. This sets the
layer 1 of this BA to permanent activity. Both sides of the connection must be set
to "Trunk".
ATM interfaces will require that the interface is operated as a trunk with regard to
the clock, although the board only addresses subscribers.
If a system has trunk connections to various carriers (Telecom, CMI, Viag,

Telalliance, ...) it is more favorable to use different DIUS2, DIUN2 or DIUT2
records (or similar) than to put all (and different) carriers onto a single board. This
not only provides better availability but also better synchronization: the reference
clock to the clock generator has less jitter (cross-talk on a board) because the
clocks of the different carriers can be only pseudosynchronous in the best case.
47.7 Abbreviations
AECB = Atlantic External Clock Box

AICB = Atlantic Internal Clock Box
AMO = Administration & Maintenance Order
APT3 = Adaptor Plug T3 clock output (now T4)
ATM = Asynchronous Transfer Mode
Table 17 Abbreviations
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
Abbreviations
BALUN = Balancing Unit/conversion from 120 ohms symm. to 50 ohms

asymm.
CBO = Continuous Bitstream Operation, = voice, fax, multimedia
CGM, CGMC = Clock Generator Module (Q9606) corresponds to SCG
CMI = Cordless Multicell Integration
DECT = Digital Enhanced Cordless Telephony
DSC80 = Dataprocessor Stream Control 80 CMX
DSCX = Dataprocessor Stream Control 80 ECX
DSCXL = Dataprocessor Stream Control
ETSI = European Telecommunication Standardization Institute
GPS = Global Positioning System
HG3575 = Gateway HG 3575, IPDA controller, HW = NCUI4
HRST = Hard Restart
HW ID = Hardware code in H = hexadecimal representation
IP = Internet Protocol
IPDA = IP Distributed Architecture, H4k access point
ISS = Inter System Synchronization, cordless seamless handover network-
wide
ITU = International Telecommunication Union
MTSCG = Memory Time Switch Clock Generator (Q2224)
MCM = Management and Control Module
NMS = Network Management System
NTP = Network Time Protocol
OCXO = Oven Controlled Xtal Oscillator, i.e. temperature stabilized
PDH = Plesiochronous Digital Hierarchy
PI = Proportional Integral (regulator)
PLL = Phase locked loop
REFTA = Referenz Takt (reference clock) Priority list, AMO REFTA
RTM = Real Time Module, part of the cCPI controller
SASE = Stand-Alone Synchronization Element (ETSI)
SCG = Small Clock Generator (on SCC board)
SDH = Synchronous Digital Hierarchy
SES = Severely Errored Second
SLCSS = Subscriber Line Cordless Synchronization Support (plug-in module)
SMD = Subscriber Module Digital (opposite of TMD = Trunk Module D).
SSU = Synchronization Supply Unit (synonym for SASE9
TCVCXO = Temperature-Compensated Voltage Controlled Xtal Oscillator
T3 = 2.048 MHz input clock according to ITU G.703/10, previously T3-an
A31003-H3170-S103-6-7620, 02/2019
refclock_en.fm
Abbreviations
T4 = 2.048 MHz output clock according to ITU G.703/10, previously T3-ab

VCXO = Voltage-Controlled Xtal Oscillator
VoIP = Voice transmission over the Internet protocol
Xtal = am. for quartz oscillator
A31003-H3170-S103-6-7620, 02/2019
call_duration_transit_call_en.fm
Feature Description
48 Restricted Call Duration for Transit Calls

The duration of a transit call can be limited.

With the feature Restricted Call Duration for Transit Calls it is possible to limit
the duration of a transit call.
The parties in the call will be warned by Override tone shortly before the
maximum call duration is reached. The call will be automatically released after the
warning period.
The activation of the feature is controlled by the AMO COT parameter CDSV (Call
Duration Supervision).
The call duration time and the duration of the warning period are administrable on
a per trunk basis. AMO TDCSU will be enhanced to configure the call duration
timer and the warning period timer.The call duration timer range is 1 to 60 minutes
in minute intervals. Default value is 60 minutes.

The feature Restricted Call Duration for Transit Calls supports ISDN and IP
trunks.

Feature Activation with Call Duration Supervision in AMO COT
ADD-COT:COTNO=<cot number>,PAR=CDSV;
Call duration timer and warning period timer

ADD-TDCSU:OPT=NEW,...,CALLTIM=<call duration timer in
minutes>,WARNTIM=<warning period timer in seconds>,...;
NOTE: The default values for CALLTIM and WARNTIM is 60.
A31003-H3170-S103-6-7620, 02/2019
call_duration_transit_call_en.fm
Relevant AMOs
48.4 Relevant AMOs

Language
COT CDSV d Überwachung der Gesprächsdauer für
kommende Transitverbindungen
CDSV e Call duration supervision for incoming
transit connections
TDCSU CALLTIM d Timer für die Zeitdauer des Rufes (in
Minuten)
Default: 60
0: Verbindungsdauer auf 0 Minuten
begrenzt. Die Transitverbindung wird sofort
ausgelöst.
CALLTIM e Call duration timer (in minutes)
Default: 60
0: The call duration time is set to 0 minutes.
The transit call is released immediately.
WARNTIM d Timer für die Warnungsdauer
Bereich: 0 bis 60 Sekunden
Default: 60
0: Sofortiges auslösen sobald der Timer für
die Zeitdauer des Rufes abgelaufen ist
(ohne Aufschalteton).
WARNTIM e Warning period timer
Range: 0 to 60 seconds.
Default: 0
0: Immediate release when the call duration
timer expires.(without override tone).
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
Feature Description
49 Route Optimization

The purpose of this function is to prevent the unnecessary use of alternative
routes and the unnecessary seizure of lines. To this end, a "more favorable"
alternative path is hunted as a replacement for the standard route which has been
selected for a particular call processing situation; the system performs
changeover to this new route.
This feature applies to the voice service for both open and closed numbering
schemes in homogeneous OpenScape 4000/HiPath 4000 networks. The feature
is effective in heterogeneous networks provided that the standard route and the
alternative route pass through Hicom 300 V3.3 nodes only. CORNV33 (at least)
must be used as the networking protocol on both the standard and the alternative
routes.
From Hicom 300 V3.5 the QSIG protocol can be used (ECMA1, from Hicom 300
V3.6 also ECMAV2 or PSS1V2).
The optimization process is initiated automatically by the call processing software

in the following cases:
1. If the software is programmed to permit Route Optimization.
2. If the call processing situation "transfer" is in effect:
a) Normal transfer/pickup from a consultation call.
b) Extension by the attendant console (AC) from the call state.
c) Normal transfer from the consultation ringing or busy situation after the
called party has answered.
d) Extension by the AC from the ringing or busy situation after the called
party has answered.
e) Extension of a dialed/non-dialed line by the AC after the called party has

answered.
f) also after a three-party conference is reduced to a two-party call
IMPORTANT: The station user cannot influence the Route Optimization

function.
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
Service Information

Administration Rules
1. Setting the home physical node number:
An network-wide unambiguous physical node number must be set in each
network node by means of the AMO ZAND, parameter PNNO. 
(The node number of the virtual node is configured in the AMO KNDEF.)
2. Setting the home physical node code:

The Route Optimization feature is based on the physical node codes. These
must be unambiguous throughout the network. This also applies to networks
with closed numbering schemes.
The home physical node codes must be assigned by means of AMO ZAND,
parameter PNODECD, and applied to digit analysis result OWNNODE by
means of the AMO WABE. 
(The node code of the virtual node is configured in the AMO KNDEF.)
IMPORTANT: If route optimization is performed, the node code contained in

the route optimization messages is subject to the station number modification
which must be correctly configured.
3. Configuring routes to remote network nodes:

The remote node codes must be configured by means of AMO WABE (DAR
"TIE") for both open and closed numbering schemes and assigned to the
trunk groups as route codes with AMO RICHT.
IMPORTANT: Please note that in spite of the closed numbering scheme the
node codes for route optimization must have open numbering.
4. Identification of routes suitable for route optimization:

The routes must be marked as being suitable for route optimization by means
of AMO RICHT, parameter ROUTOPT=Y. The lines of all routes with
ROUTOPT=Y must lead to nodes which also support route optimization (see
5). 
This cross reference is not verified in the AMOs!
5. Identification of lines leading to adjoining nodes that support route

optimization:
A class of trunk must be defined by means of AMO COT, parameter
PAR=ROPT. This class of trunk must be assigned, by means of the AMO
TDCSU, to those circuits which lead to an adjoining node that support route
optimization. This ensures that the standard route and the alternative route
only pass via nodes that support route optimization.
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
Restrictions
6. Setting protocol variant:

The AMO TDSCU, parameter PROTVAR should be used in variant Hicom
300 V3.3 or higher to set the value CORNV33 (or the value ECMA1 in Hicom
300 V3.5 or higher) in all digital tie trunk circuits to nodes to ensure
transmission of the ROPT-specific messages in the network protocol.
Cross checks: 
AMO RICHT checks whether a route to be set up with ROPT capability contains
at least one trunk group of the type S0/S2 and whether the "voice" service has
been configured.
IMPORTANT: Standards and alternative routes are not restart-safe during the
optimization process. In addition, all station services are disabled for the duration
of the optimization process. An attempt to activate features in this phase is
acknowledged on the display with "PLEASE REPEAT" or "NOT POSSIBLE".
Attempts to activate a feature are ignored in the case of analog stations.
49.3 Restrictions
• Route optimization only works when the end partners of the standard route
are analog/digital stations or analog/digital CO trunk circuits. Functional
terminals and analog interface circuits, special equipment (VMX, VMS,
paging, etc.), and COs (as A or C stations in consultation) are not supported.
• Optimize only a part of the standard route only: This feature is not
implemented because it is not available in CorNet-NQ.
• Route optimization initiated by random transit node in standard route: This

feature is not implemented because it is not available in CorNet-NQ.
• An option for repeated ROPT feature requests from a random timer not
provided for in the case of insufficient resources, a collision or when busy.
Route optimization is not performed in this case and the standard route is
maintained.
• An ROPT request can be rejected for a number of other reasons.
49.4.1 Heterogeneous Network

The heterogeneous network consists of a total of four closed-number nodes (that
is, an area) with a node that does not support route optimization (1-89-400)
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
Route a: Standard route after call transfer 

Route b: Alternative route after call transfer
Stn-A Area-CD=89
PNNO = 2-89-100 PNNO = 2-89-200

PNODECD = 828901 PNODECD = 828902
Stn-B
Route a
CO/Carrier
1-89-100 1-89-100 1-89-200
SNNO=1-89-190
Route b
Stn-C
1-89-300
SNNO=1-89-400 PNNO = 2-89-300

CD = 828904 PNODECD = 828903
Figure 65 Heterogeneous network with Route Optimization
Subscriber A in the public exchange calls user B in the ROPT-compliant network.

The later makes a consultation call to user C and transfers the call to C.
If the prerequisites for route optimization are satisfied (that is, route permitted for
route optimization and circuit with parameter ROPT), the standard route (route a)
is switched to the alternative route (route b) at the moment of call transfer.
To ensure smooth switchover of the call, so-called "broadcasting" is performed in

the transition phases: the "old" and "new" circuits receive the user’s call data at
the same time.
IMPORTANT: Only commands important for the Route Optimization feature are
listed. Information on adding boards, trunk groups and CO accesses is not shown
here because no ROPT-specific settings are necessary. Only the ROPT-specific
parameters should be specified as a change in the AMO TDCSU.
Commands for PNNO 2-89-100:

• Assign a home physical node code and area code in the AMO WABE as
follows:
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
ADD-WABE:CD=828901&89,DAR=OWNNODE;
• Assign remote node codes on the TIE DAR in the AMO WABE as follows:
ADD-WABE:CD=828902&828903,DAR=TIE;
• Set a home physical node number and node code for route optimization as
follows:
• Only configure first path for route optimization, (ROUTOPTP=NO is default):
CHANGE-ZAND:TYPE=ALLDATA,ROUTOPTP=YES;
• Allow a route optimization request for all physical nodes:
CHANGE-ZAND:TYPE=ALLDATA,ROUTOPTD=NO;
• Define class of trunk for lines to adjoining nodes with route optimization
capability:
ADD-COT:COTNO=0,PAR=ROPT;
• Define class of trunk for line:
ADD-COT:COTNO=20,PAR=LWNC;
• You can define the class of trunk for the line to the CO without the COT
parameter ROPT.
• Assign circuits to adjoining nodes with route optimization capability as

follows:
CHANGE-TDCSU:PEN=1-2-25-0,COTNO=0,PROTVAR=ECMA1,
SEGMENT=8,DEV=S2CONN;
Assign circuit to node (without NODENO transmission):
CHANGE-TDCSU:PEN=1-2-25-1,COTNO=20,PROTVAR=CORNV33,
SEGMENT=1,DEV=S2CONN,SNNO=1-89-400;
• Assign LCR routes for route optimization with closed numbering as follows:
From physical node 2-89-100 to physical node 2-89-200:
ADD-RICHT:MODE=LRTENEW,LRTE=902,NAME="ROUTEOPT",
TGRP=20,DNNO=1-89-200,ROUTOPT=YES,INFO="ROUTEOPT TO 200",
PDNNO=2-89-200;
Define an outdial rule with the AMO LODR:
ADD-LODR:ODR=1,INFO="CLOSED NUMBERING ROPT";
Define a routing element with the AMO LDAT:
ADD-LDAT:LROUTE=902,LVAL=1,TGRP=20,ODR=1,LAUTH=1;
Add a digit pattern with the AMO LDPLN:
• From physical node 2-89-100 to physical node 2-89-300:
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
PDNNO=2-89-300;
• Add a digit pattern with the AMO LDPLN:
• Assign routes for closed numbering, ROUTOPT=NO is default:
ADD-RICHT:MODE=CD,LRTE=400,CD=40,CPS=0,SVC=ALL,
NAME="TO NODE 400 ",TGRP1=40,DESTNO=40,DNNO=1-89-400,
ROUTOPT=NO,PDNNO=1-89-400;

• Assign own node code and area code in the AMO WABE:
• Assign remote node codes in DPLN (DAR TIE):
• Assign user B locally in dial plan:
ADD-WABE:CD=7200,DAR=STN,DESTNO=0;
follows:
• Define class of trunk for lines to adjoining nodes with ROPT capability:
• Assign circuits to adjoining nodes with ROPT capability as follows:
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
PDNNO=2-89-100;
PDNNO=2-89-300;

• Assign own node code and area code in the AMO WABE:
• Assign remote node codes in DPLN (DAR TIE):
• Assign user C locally in dial plan:
ADD-WABE:CD=7300,DAR=STN,DESTNO=0;
follows:
• Define class of trunk for lines to adjoining nodes with ROPT capability:
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
• Assign circuits to adjoining nodes with ROPT capability as follows:
From node 300 to node 100:
PDNNO=2-89-100;
PDNNO=2-89-200;
• Assign a route for closed numbering, ROUTOPT=NO is default:
ADD-RICHT:MODE=CD,LRTE=400,CD=40,CPS=0,SVC=ALL,
NAME="TO NODE 400 ",TGRP1=40,DESTNO=40,DNNO=1-89-400,
ROUTOPT=NO,PDNNO=1-89-400;
IMPORTANT: Since the Hicom 300 V3.2 node does not recognize route optimi-
zation, it is not specifically configured for this function. All lines to this node must
be marked as non-ROPT-capable (AMO COT, AMO TDCSU and AMO RICHT) to
ensure that no attempt is made to send ROPT-specific messages to the node.
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
49.4.2 Network with Several Areas

The network consists of three areas with area codes 69, 89, 79. Each area
contains three physical nodes which all support route optimization.
Within an area, routes must be configured between all nodes (see Section 49.4,
“Generation (Example)”).
Routes must also be configured from all nodes in an area to all remote areas and
the parameter ROUTOPT=Y must be set so that the Route Optimization feature
works everywhere. 
It is not necessary to assign routes to the individual nodes in a remote area.
Example:
• From physical node 2-89-200 to physical node 2-69-100:

ADD-RICHT:MODE=LRTENEW,LRTE=969,NAME="AREA 69",
TGRP=100,DNNO=1-69-100,ROUTOPT=YES,INFO="TO AREA 69 with
ROPT",
PDNNO=2-69-100;
ADD-LODR:ODR=100,INFO="AREA NUMBERING ROPT";
The route optimization request message on the standard route is modified by the
node of subscriber A by means of the node connecting matrix. In compliance with
KNMAT (see Chapter 42, “Number Modification”), the code for the home AREA
(here 89) is added so that the node code for route optimization is now 89828901.
In the node of user C the connection setup request for the alternative route is sent
to call number 89828901. A route code is only assigned for area 89; no route
code 828901 is configured. If the message is received in the entry node in area
89 (in this case node with node code 828902), node code 828901 is known there.
The home area code 89 is removed (in LCR using an outdial rule, not provided)
and the route to 828901 is seized.
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
CO/Carrier Stn-A Stn-C
SNNO=1-89-190
Area-CD=89 Area-CD=69
PNNO = 2-89-100 PNNO = 2-89-200 PNNO = 2-69-100 PNNO = 2-69-200

PNODECD = 828901 PNODECD = 828902 PNODECD = 826901 PNODECD = 826902
Route b Route b Route b
PNNO = 2-89-300 PNNO = 2-69-400

Area-CD=79
PNNO = 2-79-100 PNNO = 2-79-200

Route a Route a
Route a
Stn-B
PNNO = 2-79-300
PNODECD = 827903
Figure 66 Network with several areas
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
Relevant AMOs
49.5 Relevant AMOs

Language
LAUTH e LCR authorisation level
CD e Routing code
DIENST d Dienst
ROUTOPT d Routoptimisation möglich
ROUTOPT e route optimisation possible
ZLNR d Zielanlagennummer
PZKNNR d phys. Zielknotennummer
PDNNO e phys. destination node number
TDCSU LAGE d Anschlußlage
PEN e
PROTVAR d Protokollvariante
A31003-H3170-S103-6-7620, 02/2019
wegopt_en.fm
Route Optimization
Relevant AMOs

Language
PROTVAR e protocol variant
SEGMENT d Segmentierung
SEGMENT e segmentation
KZP d Kennzahlpunkt
WABE d Wabegruppe
PKNNR d physikalische Knotennummer
PNNO e Node number (until 3 levels) for unambiguous
identifaction in network.
PKNOTKZ d physikalische Knotenkennzahl
PNODECD e Physical node code
ROUTOPTE d Route Optimierung nur unter Verwendung des
Erstweges erlaubt
ROUTOPTP e Route optimization only be used of primary route
ROUTOPTS d Route Optimierung sperren. Wirkt dahingehend,
daß von diesem Knoten keine Wegeoptimierung-
Anforderung gestellt wird.
ROUTOPTD e Route optimization disable. No RO-request will
be send of this node.
(AMOs for LCR can be found in the Chapter 37, “LCR (Least Cost Routing)”)
A31003-H3170-S103-6-7620, 02/2019
s0s2_en.fm
50 S0/S2 Trunk Parameterization
S0/S2 path
OpenScape 4000 SMD TMD OpenScape 4000

MASTER SLAVE
PRIO=0 PRIO>0
CG CG
TMD
SLAVE
PRIO>0
CG = Clock Generator
= Route for reference clock
EXCH
Figure 67 Example of parameterization for reference clock supply
IMPORTANT: The MASTER/SLAVE allocation is for layer 2 signalling (D-

channel), has nothing to do with the clock distribution and can also be set in the
reverse direction.
S0/S2 PCM2/PCM30 S0/S2

public network
TMD clock TMD
MASTER SLAVE
PRIO>0 PRIO>0
PCM30
S2 S2
private network
SMD clock TMD
MASTER SLAVE
PRIO=0 PRIO=0
Figure 68 Example of parameterization for range extension
Three sets of associated parameters must be observed for parameterization for

the reference clock supply:
SMD - TMD 
MASTER - SLAVE (NETWORK-SIDE - USER-SIDE) 
PRI 0 - PRI > 0
The following rules must be adhered to (Figure 67)
• Exchange trunks (S0/S2) are always
– TMD
A31003-H3170-S103-6-7620, 02/2019
s0s2_en.fm
– SLAVE
– PRI > 0
• The following applies to tie trunks
– SMD should have priority=0, MASTER should normally apply.
– Normally, TMD has priority > 0, and SLAVE is set.
– Normally, the three parameters have the opposite values in the remote
system.
– if SMD is set, the circuit will not be regarded as reference clock supplier
even if priority = 0. 
Exception (see Figure 68): if PCM2/30 lines are installed for range
extension, the OpenScape 4000 circuits are marked as TMD. 
AMOs concerned
• Exchange trunks - S0
AD-TDCSU:OPT=NEW,COTNO=number,PROTVAR=param,DEV=S0COD;
The parameters SLAVE and TMD are set by the AMO. They do not appear in
the user interface.
• Exchange trunks - S2
CHA-
LWPAR:TYPE=DIUS2,BLNO=number,MASTER=N(Standard),SMD=N(Standar
d); 
AD-
TDCSU:OPT=NEW,COTNO=number,PROTVAR=number,DEV=S2COD,TGRP=numb
er, BCGR=0,LWPAR=number;
• Tie trunks - S0
AD-
TDCSU:OPT=NEW,COTNO=number,PROTVAR=param,DEV=S0CONN,MASTER=Y,
SMD=Y; 
AD-REFTA:PEN=ltg-ltu-slot-cct,PRI=0;
• Tie trunks - S2
CHA-
LWPAR:TYPE=DIUS2,BLNO=number,MASTER=N(Standard),SMD=N(Standar
d); 
AD-
TDCSU:OPT=NEW,COTNO=number,PROTVAR=number,DEV=S2CONN,TGRP=num
ber, BCGR=0,LWPAR=number;
• Priority setting
AD-REFTA:PEN=x,PRI=nn;
A31003-H3170-S103-6-7620, 02/2019
satpath_en.fm
51 Satellite Paths Limiting

With this feature, it is possible to limit the number of satellite paths involved in a
connection. The feature was introduced in order to ensure speech quality through
adherence to the runtime requirements. 
The SATELLITE COUNTER introduced for this feature counts the number of
satellite paths passed through. In those nodes in which a trunk group to a satellite
is to be seized (in the o/g direction) a check is carried out to establish whether the
threshold value has already been reached for this connection. The currently
active counter, referred to in the connection setup message, is compared with the
threshold value for the o/g trunk group. The connection is cleared down and an
advisory issued if the counter reading, incremented by one, is higher than the
threshold value; in all other cases the incremented counter reading is indicated in
the message.
NOTE: Unlike the TRANSIT COUNTER check, the SATELLITE COUNTER

check is performed on the o/g side before the path is seized.
The following AMOs affect this feature:
AMO COT: Parameter PAR=SATV: COT with check of the number of satellite
paths passed through.
PAR=/SATV (default): no SATELLITE COUNTER check.
AMO PRODE: Parameter PVCD: Copying the country-specific protocol tables to the
database. The CORNV33 protocol must be supported.
AMO TDCSU: Parameter PROTVAR: Assigning the CORNV33 protocol to the digital
tie trunk circuit.
Parameter COTNO: Assigning the COT with SATELLITE COUNTER
check to the digital tie trunk circuit. The COT must first be
defined by means of AMO COT (with Parameter
SATCOUNT COTPAR=SATV). Not until then is the
parameter SATCOUNT analyzed.
Parameter SATCOUNT=NONE: No satellite connection permitted.
SATCOUNT=NONE: One satellite connection permitted
SATCOUNT=TWO: Two satellite connections permitted
SATCOUNT=MANY (default): Any number of satellite
connections permitted.
Configuration of satellite path limitation

The normal configuration is no limitation. The restriction can be activated with the
aid of the following commands:
• Define COT for SATELLITE COUNTER check

AD-COT:COTNO=10,PAR=SATC;
A31003-H3170-S103-6-7620, 02/2019
satpath_en.fm
• Load country-specific protocol for Germany

COPY-PRODE:TYPE=PVCD,PVCDNR=1;
• Parameterize digital circuit so that two satellite paths are admissible
AD-TDCSU:OPT=NEW,....,COTNO=10,PROTVAR=CORNV33,SATCOUNT=TWO;
A31003-H3170-S103-6-7620, 02/2019
dss1scr_en.fm
Feature Description
52 Screening on the EDSS1 Trunk Interface

The Screening function checks E.164 numbers (calling party number or
connected party number) according to a predefined pattern. AMO SCREN
defines the screening pattern. In case of a wrong or missing number, a default
number is transmitted to the network, if required. 
Screening modifies only the calling and the called numbers (display) and not the
dialed station numbers. 
Screening can be assigned to any node using the NPI (numbering plan identifer)
E.164. 
If used as a trunk interface in a Carrier network, the OpenScape 4000 must
carried out the screening procedure, as is required of an EWSD trunk interface.
The network depicted in Figure 69, which contains a OpenScape 4000 and an
ISDN PBX, shows the relation between the network side (N) and the user side (U)
for DSS1 and trunk interface networking.
The interface from the OpenScape 4000 (in the example: node 1-1-100) to
another PBX (in the example: node 1-1-400) serves as a gateway either to an
individual PBX or to an "external" network.
A31003-H3170-S103-6-7620, 02/2019
dss1scr_en.fm
Overview
Screening Point
normally, the Carrier
performs the screening to
ISDN the public network
Network
2100
2411 Network side

.164 +49 89 382
User side STNO

E.164 +49 89 381 range
OpenScape
STNO 49 89 381 4000 node 1-1-
range External 100
ISDN international
node 1-1- system 382 21XX
node 1-1-400 node 1-1-100
400 382 31XX
381 24XX 382 41XX
381 34XX Screening can be
381 44XX configured for all
connections using
Screening Point
E164 signaling.
Here, the correctness of the
calling and the called station
number from the external
PBX is checked. If required,
a default number is
transmitted. The node
number of the external PBX
must be entered in AMO
TDCSU.
Figure 69 Network with DSS-1 protocol and E.164 numbering plan
52.2 Overview
Screening Clip/Clir Presentation

function checks E.164 numbers according to a Setting of Define
predefined pattern (screening pattern) the station settings to
number external
Allocate Specify Configure
display at nodes.
memory pattern the user and
the called
network side
party.
used AMOS DIMSU SCREN TDSCU SCREN KNFOR
A31003-H3170-S103-6-7620, 02/2019
dss1scr_en.fm
Screening
Screening Clip/Clir Presentation

procedure configure configure Specify
DSS1SCRD SCRPATT parameters
and and PRESCAL
DSS1SCRP SCRDATA and 
PRESCOL
52.3 Screening
52.3.1 Allocate memory

ADD-DIMSU:TYPE=NETWORK,DSS1SCRD=10,DSS1SCRP=10;
Parameter Function
DSS1SCRD Quantity of screening data. 
This number corresponds to the number of used nodes where screening
is performed.
DSS1SCRP Quantity of the screening patterns
This number corresponds to the number of E.164 numbers checked
during the number screening.
The number of entries for DSS1SCRD and DSS1SCRP must exactly meet the
requirements of the memory management.
52.3.2 Configure screening patterns

The AMO SCREN consists of the two elements SCRPATT and SCRDATA. It is
recommended, to configure SCRPATT first and then SCRDATA.
Define screening pattern Typ of Number (TON) International

ADD-SCREN:TYPE=SCRPATT,SCRPPLAN=1,SCRP=498938124xx#&498938134xx#
&498938144xx#;
This numbering pattern meets the LCR rules with character strings following the
digits. Every E.164 numbering pattern is allocated to a group (SCRPPLAN).
The number of screening patterns is defined in the chapter "Allocate memory"

using AMO DIMSU.
The screening pattern must correspond to the TON (Type of Number) of the
SCRPTYP parameter in AMO SCREN, described in chapter Configure screening
patterns. This TON should not be set to unknown as this could result in
ambiguous numbering.
A31003-H3170-S103-6-7620, 02/2019
dss1scr_en.fm
Screening
In the example three patterns are defined. Each screening pattern corresponds
to an E.164 number with TON=INTERNAT. The sequence ‚xx#‘ indicates that two
digits are to follow.
All these patterns are allocated to the SCRPPLAN number 1.
If the remote side transmitts TON INTERNATIONAL further screening patterns

and data must be configured for these TON.
Configure screening data

ADD-SCREN:TYPE=SCRDATA,SNNO=1-1-
400,DNO=893814402,DNOTON=NATIONAL,TOSCAL=SCREEN,PRESCAL=CLIRDEF,
TOSCOL=SCREEN,PRESCOL=COLRDEF,SCRPPLAN=1,SCRPTON=INTERNAT,LOCDES
T=381;
The following data for screening is stored in SCRDATA:
• the operator number,
• which numbers are to be screened and how,
• the assigned numbering pattern and
• the original local destination code (LOCDEST).
The PRESCAL and PRESCOL data is available for the CLIP/CLIR COLP/COLR
services.
SCRDATA is used to define the following parameters:
Parameter Function
SNNO The screening is linked with this node number. All incoming connections
on this node are assigned to the screening. Originating node=1-1-400
DNO Number for a certain station which can be reached internally or
externally (e.g. operator, service personnel, users, etc.) if the screening
delivered a negative result.
The numbering format must correspond to the DNOTON. The screening
indicator (SI) of the DNO is programmed to Network provided. (See also
chapter Presentation, parameter SCRE).
The DNO (e.g. 13814402) is used with activated screening, if the
parameters TOSCAL and TOSCOL are set to:
• SCREEN and the screening delivered negative results.
• SPECARR and the numbers to be screened do not

correspond to the E.164 notation.
With the SPECARR function, the DNO can be transmitted as second
number (e.g. operator, service personnel, etc.).
DNOTON defines the numbering format of the DNO.
Note that TON=unknown could result in ambiguity as unknown can
either be a partial number (e.g. 4402), a national number (e.g.
013814402) or an international number (e.g. 004113814402) with prefix.
In the example TON = NATIONAL and the DNO=13814402.
A31003-H3170-S103-6-7620, 02/2019
dss1scr_en.fm
Screening
Parameter Function
TOSCAL defines, whether or not (and how) the A number (Calling Party Number
in Setup) is to be screened.
NOSCR: screening is not executed.
The Calling Party Number and the second number are saved
unmodified.
SCREEN: the Calling Party Number is checked and the second number
is deleted.
If the number lies within the predefined pattern, it is accepted and
marked as checked (user verified and passed). The number is then
saved in the format TON using the SCRPTON parameter. If this
parameter is set to TON=unknown the number is modified to subscriber.
In the example SCREEN is set.
SPECARR: Special arrangement checks only the E.164 format and the
length for the Calling Party Number.
If the result is negative the DNO is used and the second number is
deleted.
If the result is positive the DNO is stored as second number.
PRESCAL Display type of the Calling Party Number (A channel station number)
(For secret numbers see also Override Category in AMO KNFOR
parameter OVRDCAT.)
CLIPPERM: CLIP is set to permanent.
The Calling Party Number is always marked with "presentation allowed"
(Presentation Indicator), provided a number is available.
CLIPSTD: a Calling Party Number can be secret for one called party.
Normally, the number is transmitted with "presentation allowed". In
special cases it is transmitted with "presentation restricted".
(The setting CLIPSTD also means CLIR per call or CLIR temporary
mode.)
CLIRPERM: CLIR is set to permanent.
The Calling Party Number is always marked with "presentation
restricted", provided a number is available.
CLIRSTD: a Calling Party Number cannot be secret for a called party.
normally, the number is transmitted with "presentation restricted". In
special cases it is transmitted with "presentation allowed".
(The setting CLIPSTD also means CLIP per call or CLIP temporary
mode.)
TOSCOL defines whether or not (and how) the B number (connected number in
the connection) is to be screened.
NOSCR: screening is not performed.
The Connected Number and the second number are saved unmodified.
SCREEN: the Connected Number is checked and the second number is
deleted.
If the number lies within the predefined pattern, it is accepted and
marked as checked (user verified and passed). The number is then
saved in the format TON using the SCRPTON parameter. If this
parameter is set to TON=unknown the number is modified to subscriber.
In the example SCREEN is set.
SPECARR: Special arrangement checks only the E.164 format and the
length for the Connected Number.
If the result is negative, the DNO is used and the second number
deleted.
If the result is positive, the DNO is stored as second number.
A31003-H3170-S103-6-7620, 02/2019
dss1scr_en.fm
CLIP/CLIR, COLP/COLR
Parameter Function
PRESCOL Display type of the Connected Number (B channel station number)
(For secret numbers see also Override Category in AMO KNFOR
parameter OVRDCAT.)
CLIPPERM: CLIP is set to permanent.
The Connected Number is always marked with "presentation allowed"
(Presentation Indicator), provided a number is available.
CLIPSTD: a Connected Number can be secret for one called party.
Normally, the number is transmitted with "presentation allowed". In
special cases it is transmitted with "presentation restricted".
(The setting CLIPSTD also means CLIR per call or CLIR temporary
mode.)
CLIRPERM: CLIR is set to permanent.
The Connected Number is always marked with "presentation
restricted", provided a number is available.
CLIRSTD: a Connected Number cannot be secret for a called party.
normally, the number is transmitted with "presentation restricted". In
special cases it is transmitted with "presentation allowed".
(The setting CLIPSTD also means CLIP per call or CLIP temporary
mode.)
SCRPPLAN The Screening Plan defines the numbering patterns used to check the
Calling Party Number or the Connected Number.
All used Screening plans must be of the same SCRPTON.
SCRPTON The Screening Pattern Type defines the TON (Type of Number) of the
SCRPPLAN.
The number with TON=unknown can be ambiguous as unknown can
either be a partial number (e.g.. 4402), a national number (e.g.
013814402) or an international number (e.g. 004113814402) with prefix.
LOCDEST The Originating Local Destination Code defines the digit sequence used
to supplement a partial number (e.g. a speed dialing number) to a
subscriber number.
The LOCDEST corresponds to the local area code assigned to the
partner node. LOCDEST can also be the local area code of the own
node.
52.4 CLIP/CLIR, COLP/COLR

These functions are implemented using AMO SCREN parameters PRESCAL
and PRESCOL.
Presentation Calling line identification

Indicator for
Default = CLIR Default = CLIP
the A side
(Calling Party CLIR CLIP CLIR CLIP
Number) permanent per call per call permanent
allowed restricted allowed allowed allowed
restricted restricted restricted restricted allowed
1
No. not avail. No. not avail. No. not avail. No. not avail. No. not avail.
A31003-H3170-S103-6-7620, 02/2019
dss1scr_en.fm
Presentation
1 The unused number is saved on the network side, SI = Network provided, PI = default
The table also applies for Connected Line Identification but with COLR and
COLP.
52.5 Presentation
ADD-KNFOR:1-1-400,ISDN,NATIONAL,USERNSCR,SEND2,SEND1,YES;
AMO KNFOR is used to perform certain settings to external node.
When configuring KNFOR make sure that
• NPI=ISDN
• the protocol for this connection is set to EDSS1NET or EDSBRD.
Parameter Function
NPI=ISDN DSS1 ISDN exchange numbering plan according to ETSI-E.164
TON defines the modification of a number to fit a certain format before it is
transmitted to a destination node.
INTERPRE international station number with prefix
NATIOPRE national station number with prefix
ISDNCC country code
ISDNIP international prefix
ISDNLC local destination code
ISDNNP national prefix
The relevant prefixes and codes are set using AMO TDCSU.
SCRE the Screening Indicator (SI) of a station number can be defined by its
settings.
Example: the station numbers transmitted from the home node (user) to
the external node (net) must have the SI=USERNSCR
NETWPROV: sets the Screening Indicator of the station number to
Network provided. The station number is not checked for validity.
(Network provided means that the station number is generated by the
network and is therefore valid).
TRANSP: the Screening Indicator is transparently transmitted to the
external node, e.g. with transit calls.
USERNSCR: the network does not check the station number. The
number is also not partially checked according E.164 in case of Special
Arrangement.
USERVF: the station number check by the network delivered a negative
result. The Network provided Nummer (DNO) was missing.
(Configure a DNO, see Configure screening patterns.)
USERVP: the station number check by the network delivered a positive
result.
A31003-H3170-S103-6-7620, 02/2019
dss1scr_en.fm
Presentation
Parameter Function
SENDCALL SEND0: no station number is transmitted to the external node.
The Information Element (IE) is deleted from the DSS-1 message and
no numbers are transmitted to the external node. The Subaddress
information is not transmitted.
SEND1: if a station number exists, only the first number is transmitted.
SEND2: if two station numbers exist the second number is transmitted
if SI=Network provided. Otherwise, the second number is deleted.
SENDCONN SEND0: no station number is transmitted to the external node.
The Information Element (IE) is deleted from the DSS-1 message and
no numbers are transmitted to the external node. The Subaddress
information is not transmitted.
SEND1: if a station number exists, only the first number is transmitted.
SEND2: is not possible.
OVRDCAT The override category is used to transmit secret numbers to an external
node.
YES: the secret number (Presentation Indicator (PI) = restricted) is
transmitted and can be read in the external node.
NO: the first and/or second number (PI,SI,TON und Digits) is completely
deleted if it is a secret number (PI=rescricted or PI=Number not
available).
The empty Information Element, however, is transmitted in the DSS-1
message.
If a secret number is deleted, the subaddress is also deleted.
A31003-H3170-S103-6-7620, 02/2019
spoa_en.fm
Description of the product
53 Single Point of Access (SPoA)
53.1 Description of the product
53.1.1 SPoA
The SPoA concept offers, in accordance with the customer the remote access to
the customer netpoints (OpenScape 4000, applications). The access is realized
via a ISDN respectively a DSL connection between the RCC and the SPoA router
(Huawei and Cisco) on customer side.
53.1.2 Option SESAP

The Secured Enterprise Service and Administration Platform (SESAP) is a
Service Platform and supports the Remote Service engineer to carry out
administration and Maintenance of Enterprise cutomers solutions in the area of
IP voice and Data communications. The service platform consists of a HW
platform as well as a SW suite combined with service and administration
applications/tools
The SESAP SW-Suite contains Applications for
• An optimized installation and administration of IP terminals
• SW-Update and SW-distribution to IP-terminals and other applications
• IP-Network Analysis and IP Traffic measurement
• The recording and management of QoS-Data from IP-terminals and IP-

Gateways
• License Management Components for Licencing of OpenScape 4000

Products
A31003-H3170-S103-6-7620, 02/2019
spoa_en.fm
SPoA Router
The SESAP SW-Suite is provided on a separate server and provides exclusive

access for service to the customer’s solutions for both local and remote access.
The remote access is via a central network access (SPoA-Solution).
53.1.3 SIRA
Secured Infratsurcture for Remote Access (SIRA) is the solution for the central
maintenance and administration of the entire Communications product range.
SIRA supports the new end-to-end service process and integrates the existing
Remote Service Platform system for OpenScape 4000 switches and applications.
SIRA enables the Com service to offer its customers fast remote fault clearance
for all products with the help of RCC (Remote Clearing Center) or BLS (Back
Level Support). Both the service organizations and the customers profit from
central, globally uniform maintenance and administration for all customer
systems, the travel time and costs saved through remote access, and from so-
called SpoAs (Single Points of Access) to key accounts running their own local
networks.
53.2 SPoA Router

Possible SPoA- Scenarios for the Remote-connection with SIRA in the RCC:
1. Central own customer Partner-Access:

This is used when a central Internet-VPN access from the customer or other
SPoA access with NAT-functionality exists,
2. Own SPoA:
Own SPoA-Router with OpenScape 4000: When no SPoA exists in a
customer network, the SPoA must be ordered as an extra.
In this case the Huawei AR 18-35 Router respectively Cisco 836 is released
and delivered.
For IM countries who have no ISDN availability, an analog capable router can
be used in the future (approximately 03.06).
A31003-H3170-S103-6-7620, 02/2019
spoa_en.fm
Possible SPoA scenarios and network access on customer site
53.3 Possible SPoA scenarios and network access on customer site
53.3.1 Remote Connectivity via Customer own SPoA

(ISDN / DSL and VPN)
IMPORTANT: The service provides for the customer the required IP information
for the configuration of the own router. Therefore a check list has to be used.
Figure 70 Remote connectivity via customer own SPoA (ISDN and VPN)
53.3.2 Remote Connectivity via supported SPoA

Router
53.3.2.1 SPoA Router in the Customer LAN
IMPORTANT: Therefore the check list for commissioning through the company-
own service has to be used.
A31003-H3170-S103-6-7620, 02/2019
spoa_en.fm
Configuration of the Huawei - Routers
Figure 71 SPoA router in teh customer LAN
53.3.2.2 Direct Access SPoA Router with netpoints
IMPORTANT: Therefore the check list for commissioning through the company-
own service has to be used.
Figure 72 SPoA router with netpoints
53.4 Configuration of the Huawei - Routers

The router will be configured from the service personnel at the customer (remote
not possible).
A31003-H3170-S103-6-7620, 02/2019
spoa_en.fm
53.4.1 Display and Connectors
Figure 73 Front of the Huawei router
Figure 74 Back of the Huawei router
53.4.2 Configuration
1. Connect the Router (connector: COM) with the COM1 Port on the PC
2. Establish a connection to the ISDN (connector: ISDN BRI) and if neccessary

connect DSL connection (connector: ADSL over ISDN).
3. Call up the Router Configuration tool program SPoAConfig.exe
4. Enter configuration parameters
A31003-H3170-S103-6-7620, 02/2019
spoa_en.fm
a) Configuration parameters for the SPoA connection including the first

device for scenario Section 53.3.2.1, “SPoA Router in the Customer
LAN”:
Figure 75 Configuration parameters for the SPoA connection
Entry Field Explanation

VPN IP Address of the Router VPN Address of the Router.
In coordination with the RCC.
Netsize Reachable endpoints with IP addresses in the
network.
The entry here is 8. Higher values (16, 32 etc)
neccessary if the number of netpoints are
accordingly high (therefor always add 4
endpoints). Additionaly take four more netpoints
into account for reserve. Is the number for the
reserve not available the next netsize has to be
used. Because the endpoints can be reached via
HiSPA, use this setting only for access via the
router.
Routertyp Chose between HUAWEI and Cisco Router
Telephone Number of the RCC The RCC call back number.
CHAP Name Target This parameter is entered automatically and is
later used by SIRA (provided by the RCC).
Chap Password Here 16 times “1” is entered (1111111111111111)
by default.
Customer LAN IP Address of IP address of the Router in the customer network.
the Router In coordination with the RCC.
Customer LAN Subnetmask Subnet Mask
A31003-H3170-S103-6-7620, 02/2019
spoa_en.fm

Customer LAN IP Address of IP address e.g. of the first device (e.g. SESAP
the Device sever, OpenScape 4000) for connectivity test
through the RCC.
VPN IP Address of the Device VPN address e.g. of the first device (e.g. SESAP
sever, OpenScape 4000).
b) Configuration parameter for the SPoA connection including the first

device for scenario Section 53.3.2.2, “Direct Access SPoA Router with
netpoints”:

VPN IP address of the VPN Address of the Router.
Router In coordination with the RCC.
Netsize Reachable endpoints with IP addresses in the
network. The entry here is 8. Higher values
(16,32 etc) are neccessary if the number of
netpoints are accordingly high (therefor always
add 4 netpoints). Additionaly take four more
netnodes into account for reserve. Is the number
for the reserve not available the next netsize has
to be used. Because the endpoints can be
reached via HiSPA, use this setting only for
access via the router.
Routeryp Chose between HUAWEI and Cisco Router
Telephone Number of the The RCC call back number.
RCC In coordination with the RCC.
CHAP Name Target This parameter is entered automatically and is
later used by SIRA (provided by the RCC).
Chap Password Here 16 times 1 is entered (1111111111111111) by
default.
A31003-H3170-S103-6-7620, 02/2019
spoa_en.fm

Customer LAN IP address of IP address of the router, if possible 192.168.1.1,
the Router otherwise in coordination with the customer.
Customer LAN Subnet mask Subnet Mask 255.255.255.0, otherwise in
coordination with the customer.
Customer LAN IP address of IP address of the first device, if possible
the Device 192.168.1.2, otherwise in coordination with the
customer.
VPN IP address of the VPN address e.g. of the first device (e.g. SESAP
device sever, OpenScape 4000)
5. Gateway for the way back of the netpoints in the OpenScape 4000 Assistant
respectively of the particular application.
Example OpenScape 4000 for the scenario Section 53.3.2.1, “SPoA Router
in the Customer LAN”:
Example OpenScape 4000 for the scenario Section 53.3.2.2, “Direct Access
SPoA Router with netpoints”:
A31003-H3170-S103-6-7620, 02/2019
spoa_en.fm
6. Switch on the router
7. Start the Router configuration with the button Generate Config:

It opens the window "Tera Term Com1 VT"
IMPORTANT: Do not switch off the router as the configuration is not yet
saved. This can be done after a connection test from the RCC.
A31003-H3170-S103-6-7620, 02/2019
spoa_en.fm
Figure 76 Huawei router configuration process
8. All further settings of the SPoA router will be done in the RCC.
A31003-H3170-S103-6-7620, 02/2019
tref_en.fm
Overview
54 Transmission and Loss Plan
54.1 Overview
In order to provide telephone users with the most pleasing audio quality, proper
control of echo and noise is necessary while maintaining the correct receiving
volume.
The feature “T - Reference point “ forms the basis for the Transmission and Loss
Plan integration for the I.M. and U.S. markets. The Loss Plan is implemented on
a country specific basis and is administered by AMO TREF
The ’T-reference point’ is a defined interface between a PABX and the public
ISDN network, at which pre-defined voice signal levels must be adhered to. In
order to achieve a constant voice signal transmission quality, regardless of the
connection type and network size, the T-reference point conditions also apply to
analog interfaces, as well as to tones heard by subscribers. The attenuation
values for the voice signal and tone levels are stored in the TREF table on the
hard disk, and are loaded into the database with the TREF AMO

The ’T-Reference point’ feature is for all systems equipped with LTUCC/LTUCE/
SCC boards. All other systems will respond to any attempt to load the TREF
matrix with the error message F03.
Within the system various subsytems are resonsible for enabling the Loss Plan
A.M. is responsible for configuration and definition of the Loss Plan and to specify
in which country the sytem is operating. Administration is also responsible for
defining the loss pair values for initialisation of boards
D.B. is resonsible for DBARs to access the defined loss plans
C.P has the resonsibility of deciding when an attenuation value has to be sent to
the LTUCE/LTUCX for a given timeslot duriong a call (The LTUC/LTUCX applies
the attenuation to the timeslot
Dependability (PIT) is resonsible for downloading data to the boards (existing

function of parameter COFIDX in AMO’s SBCSU and TACSU )
The T Reference Point Feature is the basis for the loss plan implementation for
the U.S market the U.S. values being integrated into the existing feature.
A31003-H3170-S103-6-7620, 02/2019
tref_en.fm

The administration of the loss plan data is via AMO TREF
The ACTIVATE command loads a country-specific TREF matrix into the

database. If no matrix exists on the hard disk for the specified country, the error
message F04 will be output.
• Activate T-reference point matrix for the U.S. Default voice and tone
attenuation values are loaded.
ACT-TREF:K;
(K is defined as the code for the U.S.A.)
• Activate T-reference point matrix for Germany. Default voice attenuation

values are loaded. By default, tone attenuation values are 0dB.
ACT-TREF:0;
The DEACTIVATE command resets the attenuation values of the LTUCC/LTUCE/
SCC board to 0dB. If no T-reference matrix was active, the advisory F05 is output.
• Deactivate T-reference point matrix

DEA-TREF;
The DISPLAY TREFTAB command shows the currently assigned voice
attenuation values. If no T-reference matrix was active, the advisory H01 is
output.
• Display current values of T-reference point matrix

DIS-TREF:TREFTAB;
The CHANGE TREFTAB command for attenuation between two devices only
works if a T-reference matrix has already been loaded with the ACTIVATE
command. If this is not the case, the error message F02 is output.
• Change attenuation value for connections from ANATE to OPTISET in the T-

reference point matrix to 0dB
CHA-TREF:TREFTAB,ANATE,OPTISET,0DB;
The DISPLAY TONETAB command shows the currently assigned tone
attenuation values. If no T-reference matrix was active, the advisory H01 is
output.
• Display current values of T-reference tone matrix

DIS-TREF:TONETAB;
The CHANGE TONETAB command for attenuation applied to devices connected
to tones only works if a T-reference matrix has already been loaded with the
ACTIVATE command. If this is not the case, the error message F02 is output.
• Change attenuation value for Group 1 tones to OPTISET in the T-reference

point matrix to 0dB
A31003-H3170-S103-6-7620, 02/2019
tref_en.fm
CHA-TREF:TONETAB,TONGRP1,OPTISET,0DB;
TONE TONE TONE TONE TONE TONE TONE

Group 1 Group 2 Group 3 Group 4 Group 5 Group 6 Group 7
Dial Reorder Call Maintena DTMF SIU Voice SIU Music
Waiting nce (test tones announce
tone) ments
Recall Busy Busy
Dial Override
Special Audible Executive
Dial Ringing Override
Message Special LCR
Waiting Audible Warning
Dial Ringing (expensiv
e route)
Confirmati Intercept
on
LCR On-Hook
Route Queue
Advance
Called
Party
Table 18 Tone Groups
IMPORTANT: Tone Group assignments may be affected if AMO ZAND

(TONES) is used to change a tone’s timeslot in the SIU.
U.S. trunks can be assigned different attenuation values depending upon

characteristics such as loop length and partner switch type. This is specified by
the ATNTYP parameter of the trunk AMOs TDCSU and TACSU. In Europe,
trunks get a default attenuation type.
• Change attenuation type for digital trunk 1-2-85-1 to TIE

CHA-TDCSU:PEN=1-2-85-1,ATNTYP=TIE;
• Change attenuation type for analog trunk 1-2-109-1 to CO
CHA-TACSU:PEN=1-2-109-1,ATNTYP=CO;
Optisets can be assigned different accoustic filter IDs when connected to analog
trunks in Europe. This is specified by the ACOUSTID parameter of the AMO
ZAND. In the U.S., Hong Kong, and Japan, a default accoustic filter ID is used;
it will not change when connected to analog trunks.
• Change to the acoustic filter ID settings for the U.S. (or Hong Kong or Japan)
CHA-ZAND:OPTISET,,USA; (or HONGKONG or JAPAN)
• Change to the acoustic filter ID settings for Europe
CHA-ZAND:OPTISET,,EUROPE;
A31003-H3170-S103-6-7620, 02/2019
tref_en.fm
A31003-H3170-S103-6-7620, 02/2019
amt_stma_en.fm
Feature Description
55 Trunk Access with the STMA When Using the ATM

Networking V2.0 Feature

S2-trunk access with the STMA is possible via an ATM switch. To make this
possible, there is a new device type, TYPE=ATMPVCCO in the AMO TDCSU in
the ATM Networking V2.0 (ID=5) feature.

The following rules apply to trunk connection via STMA:
• Configure the STMA with BCSU and BDAT in the same way. The innovation
only affects the AMO TDCSU.
• The new device type ATMPVCCO in the AMO TDCSU is similar to the old
device type ATMPVC30, which means that you can configure a maximum of
4 S2 trunk circuits for each STMA.
• The clock production can only be implemented for each STM-1 interface.
• You can add the ATMPVCCO circuits to existing ATMPVC and ATMSVC
circuits if there are still enough free time slots or ports. In this regard, an
ATMPVCCO circuit behaves like an ATMPVC30 circuit. All other rules that
apply to ATMPVC circuits also apply in this case (for example, you cannot
switch on the ATMPVCCO circuit until you have switched off all ATMSVCs
that are configured on the STMA.
• For STMA trunk access, only device type ATMPVCCO with a maximum of 30
B channels is possible.
• The ATM-specific parameters in the AMO TDCSU of the ATMPVCCO circuit

(VPI, VCI, PORT, etc.) correspond exactly to those of the ATMPVC30.
– Always set the filling level parameter to the default value FILLLEV=47.
– You can select all other TDCSU parameters (COP, COT, COS, etc.) in
exactly the same way as for the previously known S0/S2 trunk access via
DIU-S2 or STMD.
– The exception is the COP parameter RRST, which you must also set on
all ATMPVC circuits (but there is an appropriate message if this
parameter is missing and you cannot configure the circuit without it).
A31003-H3170-S103-6-7620, 02/2019
amt_stma_en.fm
Example Configuration
– The circuit seizure order (TDCSU parameter SRCHMODE) should - if

possible - be set to the opposite of that of the central office system. That
is, if the central office system is set to linear-increasing, the ATMPVCCO
should be set to linear-decreasing and vice versa.
• The STMA is connected to the STM-1 interface of the ATM switch. You must
connect the S2 trunk with a CES-E1 interface of the ATM switch. 
Configure a PVC with a bandwidth of 2244 Kbps (when filling level = 47 on
the STMA) in the ATM switch between the STM-1 and CES-E1 port.
55.3 Example Configuration

• Configure ATM circuit
2,COTNO=2,COPNO=2,DPLN=0,ITR=0,COS=155,LCOSV=1,LCOSD=1,CCT="S
TMA-
CO",DESTNO=4,PROTVAR=EDSGER,SEGMENT=1,TCHARG=N,SATCOUNT=MANY,
NNO=1-10-
155,CARRIER=1,ZONE=EMPTY,COTX=201,DEV=ATMPVCCO,TGRP=155,SRCHM
ODE=ASC,BCHAN=1&&30,BCNEG=N,BCGR=1,INS=Y,PERMACT1=Y,PERMACT2=
Y,MASTER=N,TEIVERIF=N,FIXEDTEI=0,CNTRNR=255,PGRP=3,ERRTIM=50,
FILLLEV=47,DCHAN=16,VPI=0,VCI=84;
A31003-H3170-S103-6-7620, 02/2019
supervise_trunk_to_trunk_connections_en.fm
Overview
56 Trunk to Trunk Supervised Connection
56.1 Overview
The Trunk to Trunk Supervised connection (TTS) offers the possibility for trunks
that do not provide disconnect supervision to be connected together in a
“supervised connection”.
Network Scenario
Transfering party
I/C or O/G I/C or O/G
C.O.
Cornet or analog Tie Analog C.O. trunk without

C.O.
disconnect supervision
Analog trunks W/O

Disconect supervision Transfering party
Stand alone System

If the TTS connection’ conditions are met, then the connection may be allowed,
with the use of the automatic trunk-to-trunk recall timer, as described below. Upon
expiration of the timer , the call is recalled to an attendant console so that an
operator can manually supervise the connection. If the attendant group is in night
mode, then the night -recall timer starts and the connection will be automatically
released when it expires.
A31003-H3170-S103-6-7620, 02/2019
User Interface
56.3 User Interface

• Certain rules must be met when establishing a TTS connection:
a) a) The station user ia allowed to transfer trunks (TTT attribute in COS) or

it is an attendant:
b) b)Both transferred trunks are trunks with no disconnect supervision:
c) c)Other AMOs which allow the transfer must be set
• Features that may connect trunks and create TTS connection:

Transfer from Consultation
Transfer from Conference
Transfer Before Answer
Transfer from Join ( Attendant)
Single Step Transfer
ACD - Route Off Destination
• If a supervised connection is created, then, when the trktotrk timer expires,

the ITR group set in VFGR ITDEST will intercept the recall
• When the operator answers the recall, a conference between the trunks and
attendant is created. The operator may release this call pressing the
RELEASE key or may re-extend the trunks connection by pressing the
EXTEND key ( in this case creating a new supervised connection).

The TTS connection feature is intended for the global marketplace.

How to add the TTS connection feature into the system:
General Settings:
• Allow CO to CO transfer
CHA-ZAND:ALLDATA,EXCOCO=YES;
• Change transfer type to extend
CHA-ZAND:ALLDATA,TRANSFER=EXTEND;
• Trunks participating to the transfer:
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
CHA-COT:cotno,COTADD,CEBC&CEOC;
• Setting the trunks timer duration:
CHANGE-CTIME:TYPESWU=CP2,NIRECALL=900,TRKTOTRK=120;
( values are in the range 60 - 1800 seconds for both parameters)
Transferring Device’ Settings:
• Transferring Device being station or trunk must have TTT in its COS (not
necessary for attendant)e.g. for cos 1:
CHANGE-COSSU:TYPE=COS,COS=1,AVCE=TTT;
Transferred Trunks’ Settings:
• Incoming Trunks with no disconnect supervision (e.g COT 1)

CHANGE-COT:COTNO=1,COTTYPE=COTDEL,PAR=DSIT;
• Outgoing Trunks with no disconnect supervision (e.g. COT 1)
CHANGE-COT:COTNO=1,COTTYPE=COTADD,PAR=NRAA&NRBA&TWDS;
56.6 Relevant AMOs

Language
COT TWDS d Umlegen zulässig bei überwachter Verbindung
e Transfer allowed in a supervised connection
DSIT d Auslöseüberwachung in kommender Richtung
e Disconnect Supervision in the Incoming Direction
KRVM d Kein Auslösen vor Melden
NRBA e No Release Before Answer
MVLT d Meldeüberwachung
ANS e Answer Supervision
COSSU VAA d Gerät zum Umlegen von Amtsleitungen
berechtigt
TTT e Device allowed to transfer trunks
CTIME NIRECALL d Dauer bei überwachten Verbindungen
e Duration in a Supervised Connection
TRKTOTRK d Dauer bei überwachten Verbindungen
e Duration in a Supervised Connection
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Introduction
57 Virtual Numbering (VNR)
57.1 Introduction
The Virtual Numbering – VNR feature in OpenScape 4000 supports :
• the multiple assignment of station numbers,
• the configuration of overlapping station numbers with different lengths

(dependent on DPLN groups).
Multiple virtual nodes must be created for this in the OpenScape 4000 (the
physical node). These are defined with node number and node code.
The station ports configured are each assigned to one of the virtual nodes. The
station number of a station port is now only unique within the virtual node.
The unique identification of a station within the physical node is only possible with
the combination of the node code and station number.
57.1.1 Prerequisites
Activation/deactivation of the VNR feature is only possible in combination with
regeneration.
The same requirements as for earlier OpenScape 4000 system versions apply to
other communication systems in a network with a VNR system. Detailed
information is provided in the Release Notes. Administrative changes are also
required in the network for network-wide station availability.
57.1.2 Scenarios
The requirements for this feature are based on the following customer scenarios:
• Branch network optimization - a company with a branch network with a single

physical system,
• Shared Use of a OpenScape 4000 by Different Companies.
57.1.2.1 Branch network optimization - a company with a

branch network with a single physical system
Initial scenario
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Introduction
OpenScape 100 Branch office 1

S2 4000 ISDN country code 49
Physical ISDN area code 30
node number 200 ISDN local code 38645
10-1-6
Main office OpenScape OpenScape Branch office 2

1008 4000 4000 100
ISDN country code 49 Physical IP ISDN country code 49
Physical
ISDN area code 89 node number ISDN area code 631
node number
ISDN local code 7221 10-1-5 10-1-7 200 ISDN local code 7974
1007
OpenScape
Branch office 3
4000 10
S0 Physical ISDN country code 49
node number ISDN area code 89
10-1-8 ISDN local code 636123
20
Figure 77 Corporate network with multiple OpenScape 4000s and non-unique

station numbers
Target scenario:
Identical station structure but with only one OpenScape 4000, two access points
and HFA terminals The Virtual Numbering feature supports the use of multiple
identical or overlapping numbering plans within a OpenScape 4000.
AP 17 Branch office 1
100 Virtual node 1-1-6
IP Node code 96
ISDN country code 49
200 ISDN area code 30
ISDN local code 38645
OpenScape
4000
1008
AP 26 Branch office 2
100
IP Virtual node 1-1-7
Node code 97
200 ISDN country code 49
ISDN area code 631
1007
Main office HFA

IP Branch office 3
node 10-1-5: 10 Virtual node 1-1-8
Virtual node 1-1-5 Node code 98
Node code 95 HFA
IP ISDN country code 49
ISDN country code 49 20 ISDN area code 89
ISDN area code 89 ISDN local code 636123
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Introduction
Figure 78 Corporate network with one OpenScape 4000, two access points
and HFA terminals
57.1.2.2 Shared Use of a OpenScape 4000 by Different

Companies
Initial scenario
Company 1
OpenScape 1000
4000
ISDN country code 49
Physical ISDN area code 89
node number 2000 ISDN local code 723
20-2-6
OpenScape
Company 2 1000
4000
ISDN country code 49 Physical
ISDN area code 89 node number
11-3-5
ISDN local code 797 2000
OpenScape Company 3
4000 100
Physical ISDN country code 49
node number ISDN area code 89
51-1-1 200 ISDN local code
79456
Figure 79 Three companies with independent communication systems
Target scenario:
Three independent companies are assigned a virtual node in a shared

OpenScape 4000. These virtual nodes are not restricted to APs or the
OpenScape 4000 host system.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Properties
AP 1 Company 1
1000
(Virtual) node 1-1-6
IP
Node code 96
OpenScape ISDN area code 89
4000 ISDN local code 723
Node 10-1-5
3038
AP 2 Company 2
100
1000
IP (Virtual) node 1-1-7
Node code 89
2000
ISDN area code 89
ISDN local code 797
3037
System operator AP 3
100 Company 3
node 10-1-5:
IP (Virtual) node 1-1-8
Virtual node 1-1-5
Node code 89
Node code 95
ISDN country code
ISDN area code 89
49
ISDN local code
ISDN area code 89
79456
ISDN local code 721
Figure 80 Three independent companies are assigned a virtual node in a

shared OpenScape 4000
57.2 Properties
57.2.1 Station Availability

The activation of this feature changes how stations are reached via their station
number. This must be taken into consideration when analyzing requirements. The
following is an example of availability with regard to Figure 77:
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Properties
Call from
Stn 1008 in the main office Stn 10 in branch office 3
Virtual node 1-1-5 Virtual node 1-1-8
Node code 95 Node code 98
ISDN country code 49 ISDN country code 49
ISDN area code 89 ISDN area code 89
ISDN local code 7221 ISDN local code 636123
to
can dial the following: can dial the following:
100 in branch office 1 0 0049 30 38645 100 for 0 0049 30 38645 100 for
Virtual node 1-1-6 INTERNAT INTERNAT
Node code 96 0 030 38645 100 for NATIONAL 0 030 38645 100 for
ISDN country code 49 96 100 for UNKNOWN NATIONAL
ISDN area code 30 96 100 for UNKNOWN
Stn 1007 in the main 0 0049 89 7221 1007 for 0 0049 89 7221 1007 for
office INTERNAT INTERNAT
node 10-1-5: 0 089 7221 1007 for NATIONAL 0 089 7221 1007 for
Virtual node 1-1-5 0 7221 1007 for LOCAL NATIONAL
Node code 95 1007 for UNKNOWN (95 1007 0 7221 1007 for LOCAL
ISDN country code 49 optional) 95 1007 for UNKNOWN
ISDN area code 89
Stn 20 in branch office 3 0 0049 89 636123 20 for 0 0049 89 636123 20 for

Virtual node 1-1-8 INTERNAT INTERNAT
Node code 98 0 089 636123 20 for NATIONAL 0 089 636123 20 for
ISDN country code 49 0 636123 20 for LOCAL NATIONAL
ISDN area code 89 98 20 for UNKNOWN 0 636123 20 for LOCAL
ISDN local code 636123 20 for UNKNOWN (98 20
optional)
Table 19 Station availability in multiple virtual nodes
57.2.2 Feature Principles

1. When you activate this feature, a station number is only unique if combined
with a node code. Station numbers for multiple assignment continue to be
configured in the AMO WABE with the digit analysis result STN .
2. Stations can be reached in a virtual node with their station number, even
without a node code.
3. Idle terminals display the station number without the node code.
Exception: SIP end points. These show the node code in the idle status.
4. The display format for the station number in ringing or call status can be set
individually for each customer (ISDN, PNP and unknown). This setting then
applies to all stations in the entire physical node.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Properties
5. Overlapping station numbers (10, 100, 1000) should be configured on the

basis of DPLN groups.
6. The node code and station number may not exceed 6 characters in length.
This yields a maximum station number length of 12 digits.
57.2.3 Special Features and Restrictions

Special Features
The following special features arise due to the use of VNR:
• Station numbers should be configured as DPLN-dependent with VNR

The stations can only be assigned to the DPLN groups specified in the
KNDEF parameter ADPLN. For the example in Figure 78, the stations are
assigned to the DPLN groups as follows:
Station number WABE

95,96,97,98 All
10,20 1
100,200 2
1007,1008 3
Examples:
– If station 96200 dials extension 100, it reaches STN 96100.
– If station 951007 dials extension 1008, it reaches STN 951008.
• Features, such as PU group, hunt group, CHESE, direct station selection,

and COM group, can be configured for stations in different virtual nodes.
• The network-wide Team CHESE feature becomes redundant if the CHESE

stations are located in a single system after the startup of a VNR node. In this
case, use of the standard CHESE function can be resumed.
• The node code is required for unique identification with the Autoset Relocate
and Mobile HFA features.
• Closed numbering within one system between VNR nodes.

Feature Description
Any station number (including personal attendant console) is reachable via its
extension number (short number, without VNAC in front).
Different VNR nodes can be grouped under one VNR group via AMO KNDEF
(parameter VNRGRP). Inside this VNR group closed numbering is possible,
considering also the right display and ACL interface.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Properties
Please be aware that one station number can be configured in more than one
virtual node. If the same number is configured in more virtual nodes inside of
a VNR group, only the first found one in the data base will be used!
Service Information
• Only stand alone system with VNR is considered. Only the stations
belonging to one physical system can use closed numbering.
• The feature is released for any kind of device (anate, digite and functional
devices). HFA and SIP subscribers are considered too, but note that no
changes have been done in the login phase / HFA mobility.
• The VNR closed numbering applies to internal and external calls to

stations (only for service VOICE, not for DTE or FAX).
• This feature considers only basic call and the following basic features
related to this:
– consultation,
– conference,
– transfer,
– centralized AC-features (blind transfer / single step transfer from AC,

recall from Hold),
– call completion (call back) on busy / free,
– Call forwarding execution,
– integrated OpenScape 4000 Call log and CLIR.
• The display presents only the short number inside one VNR group (on
calling and called side).
• Only DISPMOD = UNKNOWN & ISDN are considered.
• CCBS from CO is only working with its own ISDN number.
IMPORTANT: The service technicians should be aware at configuration to

assure that VNR Closed Numbering makes sense for the VNR nodes that are
part of a certain VNR group (considering DPLN, ITR restrictions, number
overlapping).
Generation (Example):
CHANGE-ZANDE:TYPE=ALLDATA,DISPMOD=UNKNOWN;
CHANGE-ZANDE:TYPE=ALLDATA,DISPMOD=ISDN;
Activation of the feature in the system:
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Properties
Group different VNR nodes under one VNR group:

CHANGE-KNDEF:NNO=<number>,VNRGRP=<number>;
The AMO KNDEF parameter VNRGRP allows to group different VNR nodes
under one VNR group. Within this group closed numbering is possible
between stations belonging to different VNR nodes.
Changing the value for VNRGRP is only allowed when “VNR Closed
Numbering'” is activated in the system (with AMO ZANDE).
Default: VNRGRP=0. This means no membership to a certain VNR group;
any other value means that the VNR node is part of the specified VNR group.
Restrictions
The following restrictions must be observed:
• Keysets with lines via different virtual nodes are not supported. This
restriction also applies for the network-wide Team CHESE function.
• The members of the one number service must be located within a virtual
node. Otherwise false information is displayed.
• A code hunt group cannot be assigned to a virtual node. It should always be

considered for the entire physical node. A workaround is possible with floating
stations as a master hunt group.
57.2.4 Limiting Values

The following limiting values must be specifically observed in connection with
VNR:
• No more than 16 DPLN groups (AMO WABE, parameter DPLN),
• No more than 16 attendant console groups (AMO VFGR, parameter

ATNDGR),
• No more than 254 destination numbers (AMO WABE, parameter DESTNO),

(AMO DIMSU, parameter NWNUNSUB)
57.2.5 Converting to VNR

When converting from a non VNR OpenScape 4000/HiPath 4000 network to a
VNR OpenScape 4000/HiPath 4000 network the following items have to be
considered:
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Properties
Keyword Brief Description

Autoset Relocate / The node code is needed for unique identification.
Mobile HFA
CMI All stations and the extension connections associated with an SLC
board must be assigned to the same virtual node.
The CMI instructions on upgrading to VNR must be followed.
DTENO/FAXNO & DAR=DTENO/FAXNO can no longer be used in CPS 6, 10, 11, and
STN 12 to prevent interception for stations (faxes and modems)
because, in contrast to stations, the node code is not appended to
the DAR DTENO & FAXNO. This is why it is not possible to assign
a node to them.
As a workaround, we recommend configuring all station numbers
as DAR=STN and setting up system forwarding to the DAR= DTE
+ own station number or FAX + own station number.
DNIT DNIT station numbers are not modified on the basis of the node
code. It is thus impossible to uniquely assign them to a virtual node
or even to use individual numbers repeatedly. Moreover, a number
can only be configured as a DNIT number if it is configured for
DPLN=0 or ALL DPLN groups.
We therefore recommend configuring six-digit DNIT numbers in a
free number range. Known station numbers are configured as a
floating station and routed to the associated DNIT station number
via system forwarding.
Call data recording The node code + extension are always sent by default to call data
recording. Changes are possible with the AMO GEFE.
Internal E.164 An appropriate LCR configuration is needed for this.
dialing
KNDEF ISDN and node codes must be unique.
DPLN is used for the DIAL operation in this node. If multiple DPLN
groups are needed for the station, then the "allowed DPLN groups"
should be entered under ADPLN, otherwise we recommend
setting the ADPLN as equal to the DPLN to avoid configuration
errors.
KNMAT As station numbers are automatically modified with ITR, KNMAT
should not be used in a VNR system.
Call data modification should be performed with the AMO GEFE.
PUBNUM in AMO SDAT should be used instead of the
replacement extension (REPEXT).
KNMAT / ITR Connections cannot be restricted in a physical system with
KNMAT. Restrictions are only possible with ITR.
Cross node PU, HT, CHESE, DSS, COM group.
features The relevant stations can be distributed across multiple nodes.
LCR / two-stage We recommend using two-stage LCR for a better overview of the
LCR LCR process, especially in the event of breakout in different
locations or countries and to simplify expansion. Please note that
a number of functions cannot be performed with RERTEINT, such
as REMAC in AUN and ONS. These should be entered as
international numbers in this case.
Table 20 Converting to VNR
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Properties

Features within a Keysets => network-wide Team/Chese - The relevant station
virtual node numbers must be located within a virtual node.
ONS The members of an ONS group must belong to the same virtual
node.
RCG / ACD RCG station numbers can only be configured as DPLN-
independent. This means they conflict with the VNR numbering
plan. We therefore recommend configuring six-digit RCG numbers
in a free number range. Old RCG numbers should then be
replaced in applications by the new RCG station numbers.
RUFNUM We strongly recommend against using the AMO RUFUM in the
VNR system. A station number that is converted with the AMO
RUFNUM cannot be assigned to a virtual node because the node
code is not appended to it. We recommend replacing the RUFUM
with a floating station with system forwarding.
Call numbers Every virtual node must be assigned a unique node code and ISDN
station number. The node code is part of the station code, the
attendant console code, and the attendant code. These codes are
needed to activate features (AMO ACTDA, AMO ZIEL, etc.)
Closed calling is no longer possible between stations with different
E.164 station numbers.
HT (code) Node codes are not appended to the station number of a hunt
group code. This number is therefore valid system-wide. You
cannot assign a virtual node to it.
Workaround: Change the hunt group code into a master hunt
group using a floating station. PC-DACON supports this change.
HT (master) The node code is part of the master hunt group's station number. It
is therefore assigned a virtual node.
SIP /HFA The node code is part of the station number. This station number
should be signaled to the SIP and HFA terminals for logon at the
gateway.
TDCSU / VNNO A trunk connection can be assigned to a virtual node using the
(CO) parameter VNNO in the AMO TDCSU if the carrier does not send
a unique called party number, for example, only the DID number
(extension).
Network with Please note the following if using a OpenScape 4000 numbering
closed numbering plan and closed numbering:
The relevant KNMAT entries that are needed to integrate an openly
numbered node into an openly numbered network should be made
network-wide.
It is important to ensure that the node code is part of the called
party in the directly connected systems.
VFGKZ The ATNDID and ATND codes should be assigned node codes in
the AMO VFGKZ.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation

DPLN To avoid restrictions in expansions, these station numbers should
be configured as DPLN-dependent. As this significantly increases
the number of DPLNCD and DPLNGR memory blocks used in the
AMO DIMSU, attention should be paid to block formation in the
DPLN configuration (always 0-9, 00-99, 000-999, etc.).
Example: 10&&19, 100&&159, 100&&199, 1000&&1199,
1000&&1999, 10000&&12999 etc.
DPLN / KNDEF A DPLN group can be used for multiple virtual nodes.
DPLN - DAR The following digit analysis results cannot be configured as DPLN-
dependent:
RCG, SIGNON, SIGNOFF, DSNR, PRTY, IMMED, FLASHOV,
FLASH, OWNNODE, INCALTRT, FRCALTRT
It is important to ensure that these codes do not conflict with the
numbering scheme.
XPRESSION, In future, all connected applications that were previously switched
DAKS etc. with closed numbering must use a unique station number (E.164
or a prefixed node code).
Sole exception: The application only dials stations within a virtual
node. In this case, the target node code can, where applicable, be
preceded by DGTPR/VNNO.
ZANDE You can use the AMO ZANDE to set the number format for internal
number display. The same number format should be used for
networking.
57.3 Generation
57.3.1 Tasks Involved in Switching to VNR

• The system must be regenerated before changeover to VNR. 
A detailed customer network analysis with DPLN planning for the stations of
the VNR system is strongly recommended.
• Each virtual node must be assigned a unique node code. This cannot be
changed. All node codes must feature DAR =OWNNODE in the AMO WABE.
• The station terminals are generated with node codes in the relevant AMOs
(SBCSU, SCSU, etc.).
• After activating the VNR feature, SIP and HFA terminals must log back on
(LOGON) with node code and station number. The terminals should be
provided with the new LOGIN data for this purpose.
• Each virtual node must be assigned a unique E.164 station number.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
• LCR routes must be set up with reroute internal to ensure internal availability
via the E.164 station number. If all virtual nodes are located in one LAN, this
can be implemented using three basic "reroute internal“ LCR routes
(subscriber, national and international) for which the complete E.164 station
number is mirrored. However, if a breakout to another location is expected in
the future, we advise changing over to a two-level LCR. The associated
depends on the ISDN station numbers in the VNR system.
• All station numbers assigned before feature activation in OpenScape 4000

must be expanded to include the virtual node code for all features (for
example, AMO ACTDA, AMO ZIEL). (Impact on the use of DLS, PCDACON,
OpenScape 4000 Manager, etc.)
• If the internal E.164 station number display (AMO ZANDE, parameter

DISPMOD=ISDN) is used, the shortest ISDN station number possible is
displayed for connections across virtual nodes such as in networking. Using
the AMO KNFOR, the shortest station number display can be restricted to
National or International. Within the local virtual node, only the station number
without the node code is shown as usual.
• If a shared trunk connection is used to reach multiple virtual nodes, an explicit

E.164 station number must always be sent by the CO. In this case, the
parameter DFNN must not be set in the AMO TDCSU.
• Connections between virtual nodes can only be restricted with ITR. Existing
KNMAT restrictions must be converted to ITR restrictions.
• The virtual node code is a component of the CHRGEE in call data recording.
57.3.2 Network Integration

• An openly numbered network is basically a network with at least one VNR
node (OpenScape 4000 with the feature "Virtual Numbering" active).
• The following measures are necessary for closed numbering:
– The usual KNMAT entries that are needed for open numbering in an
OpenScape 4000/HiPath 4000 network are required in all OpenScape
4000 systems in the network
– In addition to the KNMAT modification in the systems directly connected

to the VNR system, an OUTPULSE must be configured in the AMO LODR
with the node code for the VNR system.
– Evaluations should be performed to check the effect of open numbering

on existing applications and if any adjustments are necessary.
– Adjustments may be necessary in call data recording.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
– In VNR systems, all virtual nodes that have the same E.164 station
number must be assigned the same node number network-wide. It is not
necessary to adapt the existing standard OpenScape 4000/HiPath 4000
network. In the case of network expansions and significant modifications,
this concept should be adopted with a view to achieving a clear network
structure.
57.3.3 Description of the AMO Application
IMPORTANT: This section assumes general configuration skills, such as the

ability to configure trunks, stations and features. Information on these topics is
provided in the corresponding chapters of the service manual.
IMPORTANT: The configuration steps described in the following are based on

Figure 78.
57.3.3.1 Feature Activation
As already mentioned, regeneration is necessary if the use of non-unique station

numbers is enabled in OpenScape 4000. The VNR parameter is set to YES in the
AMO ZANDE for definition on a VNR system:
CHANGE-ZANDE:TYPE=ALLDATA,…,VNR=YES;
57.3.3.2 Digit Analysis and Node Definitions
Before we come to the configuration of digit analysis and node definitions, a few
explanations are needed on the relationships between the AMOs WABE and
KNDEF:
Outgoing dialing is performed with the station’s DPLN (AMO SBCSU).
When DAR OWNNODE is reached, dialing with the DPLN of the destination node
(AMO KNDEF) continues from this point.
Here is an example as an aid to understanding:

Let’s consider station (95)1007 from virtual node 1-1-5 and station (98)10
from virtual node 1-1-8.
Virtual node 1-1-5 uses four-digit numbering, such as 1007.
Virtual node 1-1-8 uses two-digit numbering, such as 10.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
If station (95)1007 wants to call station (98)10, then the dial plan must be
adjusted to the destination node after the node code is dialed.
Station number "10" does not produce a result in the DPLN of the station
(95)1007.
The outcome is identical if station (98)10 calls station (95)1007.
Station number "10" produces a result in the DPLN associated with station
(98)10, but dialing is incomplete in virtual node 1-1-5.
For this reason, subsequent dialing is evaluated with the DPLN of the destination
node when DAR OWNNODE is reached.
The parameter ADPLN (permitted DPLN) defines which DPLN groups may be
assigned to the members of a virtual node.
If the parameter ADPLN associated with a virtual node is assigned multiple DPLN
groups, ensure that the node-dependent station numbers (such as STN,
ATNDDID, ATNDIND, ATND, etc.) are identically configured.
The DPLN is now configured following the generation sequence. The following
should be noted here:
• The DAR OWNNODE should always be configured independently of the

DPLN.
• In contrast to earlier versions, the DAR STN can now be configured

dependent on the DPLN. In the case of a VNR system, we recommend
generating the DAR=STN dependent on the DPLN to avoid problems with
future expansions.
First the physical node code that is entered in the AMO ZAND as PNODECD is
configured as DAR=OWNNODE.
The physical node code must be unique network-wide, and should not
correspond to any virtual node code as virtual nodes can be distributed over
several physical nodes.
As the user does not select the physical node code, station numbers are
frequently entered with * to avoid limiting the numbering scheme:
ADD-WABE:CD=95,DAR=OWNNODE,CHECK=N;
DAR=OWNNODE should also be configured for all account codes in the virtual
nodes:
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
The station numbers are now configured on the basis of DPLN groups. To avoid
running out of memory in the AMO DIMSU, parameters DPLNGR/DPLNCD,
entire station number blocks are prepared where possible:
ADD-WABE:CD=10&&29,DPLN=0,DAR=STN;
Next, the physical node number and node code are entered in the AMO ZAND:
CHANGE-ZAND:TYPE=ALLDATA,…,PNNO=10-1-5,PNODECD=**95;
The virtual nodes are now configured with the AMO KNDEF. This involves
assigning the unique ISDN station number (E.164 station number) and the unique
node code:
ADD-KNDEF:NNO=1-1-5,TYPE=OWN,
ISDNCC=49,ISDNAC=89,ISDNLC=7221,ISDNSK=4,
NODECD=95,NODECDSK=2,DPLN=2,ADPLN=2;
57.3.3.3 Station Configuration
The stations are now configured. Note that the node code is part of the station
number with which the station is configured.
Add the station for virtual node 1-1-5:

ADD-SBCSU:STNO=951007,OPT=OPTI,CONN=DIR,
PEN=1-1-3-0,DVCFIG=OPTIIP,COS1=1,COS2=1,LCOSV1=1,
LCOSV2=1,LCOSD1=1,LCOSD2=1,DPLN=2;
ADD-SBCSU:STNO=951008,OPT=OPTIIP,CONN=DIR,
PEN=1-1-3-0,DVCFIG=OPTIIP,COS1=1,COS2=1,LCOSV1=1,
ADD-SBCSU:STNO=96200,OPT=OPTIIP,CONN=DIR, 
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
LCOSV2=1,LCOSD1=1,LCOSD2=,DPLN=0;
As the stations of the virtual node are routed in different ways, source-dependent
routing is required here.
The stations of the different virtual nodes are assigned to different source groups
for this purpose, unless this assignment is not already fixed by a unique position
within their own APs.
We will assign source group 1 to the stations in node 1-1-5.

CHANGE-SDAT:STNO=951000&&951999,TYPE=DATA1,SRCGRP=1;
We will assign source group 2 to the stations in node 1-1-8.
We will assign source group 17 to the stations in node 1-1-6 based on the AP
number.
Accordingly, we will assign source group 26 to the stations in node 1-1-7.
Our example assumes that each virtual node also has its own central office
access.
57.3.3.4 Trunk Configuration
First the trunk groups are prepared:

ADD-BUEND:TGRP=5,NAME="TRUNK GROUP ND 1-1-5",NO=30;
• We will configure the S2 trunk for node 1-1-5 at PEN 1-1-1-0:
0,COTNO=20,COPNO=20,DPLN=0,ITR=0,COS=1,LCOSV=1,LCOSD=1,CCT="C
O Munich
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
195",DESTNO=99,PROTVAR=EDSGER,SEGMENT=1,ATNTYP=CO,ISDNIP=00,I
SDNNP=0,TRACOUNT=8,NNO=1-1-
195,TGRP=5,SRCHMODE=ASC,INS=Y,DEV=S2COD,BCHAN=1&&30,BCNEG=Y,B
CGR=1,LWPAR=1, SRCGRP=1;
O Berlin
SDNNP=0,TRACOUNT=8,NNO=1-1-
ADD-TDCSU:OPT=NEW,PEN=1-26-1-0,COTNO=20,COPNO=20,
DPLN=0,ITR=0,COS=1,LCOSV=1,LCOSD=1,CCT="CO Wiesbaden 197"
,DESTNO=99,PROTVAR=EDSGER,SEGMENT=1,ATNTYP=CO,ISDNIP=00,
ISDNNP=0,TRACOUNT=8,NNO=1-1-
197,TGRP=7,SRCHMODE=ASC,INS=Y,DEV=S2COD,BCHAN=1&&30,BCNEG=J,B
O Munich
SDNNP=0,TRACOUNT=8,NNO=1-1-198,TGRP=8,INS=Y,
DEV=S0COD,BCNEG=Y,SRCGRP=2;
57.3.3.5 LCR Configuration
Before performing LCR configuration, you should consider the expansions to the
network that may be required in the future.
Our example has just one system in Germany with trunk access distributed
across three cities.
To facilitate additional breakouts in Germany or other countries at a later stage,

the LCR should be structured from the outset so that breakouts to several
countries can be configured without difficulty. One option here is the "two-level
LCR" concept:
First let’s consider a possible constellation of breakouts in different countries.
The following graphic shows the possible connections in such a network:
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
If, for example, a local station number is dialed, then the required destination
depends on the source. A different destination is dialed for every location. This is
why only one reroute internal is permitted within the same location for internal
destinations with local station numbers. Likewise, routing should be carried out
on an individual basis for each location.
If a national number is dialed, then the required destination is different in each

country. Reroute internal is only permitted for national internal destinations within
a country. Routing differs from country to country.
If an international number is dialed, then the destination is unique worldwide.
This is why we have divided the LCR into 2 levels.
57.3.3.6 Brief Description of 2-Level LCR
LCR level 1 - internationalization

Location-dependent modification:
The station number dialed is transformed into a unique international station

number using source groups based on reroute internal.
Dialed station number -> international station number transformation
The station number dialed is converted to an international station number in

accordance with the entries in the AMO KNPRE and the AMO KNDEF:
Format definition:
• Exit code (no prefix (PF)) = local area
• Exit code + national prefix (no international prefix) = national
• Exit code + international prefix = international
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
The station number dialed is extended to an international ISDN station number

by prefixing it with the exit code, the international prefix, the relevant country
code, and, in the case of local calls, with the relevant area code. Dialed prefixes
are left out.
Example:
Exit code =0
National prefix =0
International prefix = 00
Country code = 49
Area code = 30
Digit Pattern -> Modification

0-W-0-X -> 0 00 49 + X
0-W-X -> 0 00 49 30 + X
Definition for this example:
Local station number -> LODR /LRTE 1xx, LPROF 1
The LRTE and LODR values 1xx (100 to 199) are used to extend local station
numbers. They are summarized in LPROF 1.
National number -> LODR /LRTE 2xx, LPROF 2
The LRTE and LODR values 2xx (200 to 299) are used to internationalize
national numbers. They are summarized in LPROF 2.
LCR level 2 - routing

Source-based routing:
The international station number is routed to the destination, depending on the

source group.
Routing international numbers
Internal station numbers are routed back to the local node based on reroute
internal. The other station numbers are routed individually dependent on the
source group.
Internal routing:
• Standard with LRTE 300
• Reserved for special cases: LRTE 3xx (301 - 399)
External routing (dependent on the source group):
General outdial rules:
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
• 400 - for international destinations (4xx reserved for special cases)
• 500 - for national destinations (5xx reserved for special cases)
LCR routes:
• International destinations with LRTE 4xx (401 – 499)
• National destinations with LRTE 5xx (501 – 599)
LCR profile for international destinations:
LPROF 3 - contains only LRTG 4xx - for international destinations. No local

breakout.
LCR profiles per country with CO breakout for national destinations:
Depending on the breakout country, LPROF 4 and those that follow contain a
combination of LRTE 4xx for international destinations and 5xx for destinations
within the local country.
Example
LCR level 1:
An LCR route is required for each local area network so as to convert the dialing
of local area codes into a unique international station number.
Since this station number is immediately to pass through LCR again if it originates
from LCR, it is not modified by the AMO KNPRE. This is why the destination
number must be entered implicitly in the outdial rule, in other words, with an exit
code and international prefix.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
The following figure shows the digits to be expanded per location or country. 
The small boxes containing numbers represent the source groups.
Local numbers use the 100 outdial rules and LCR routings, national number use
the 200 outdial rules.
The diagram shows which source group belongs to which local area and which
digits are to be added when dialing the local or national network.
For the remaining configuration, we will only consider "our own network" to begin
with.
Let’s begin with the configuration of the outdial rules for reroute internal:
(With exit code and international prefix)
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
Outdial rules 1xx (100 -199) are provided for modifying local station numbers:
• Outdial rule 100 for Berlin:

ADD-LODR:ODR=100,CMD=NPI,NPI=ISDN,TON=UNKNOWN;
ADD-LODR:ODR=100,INFO="LODR for Berlin";
• Outdial rule 101 for Munich
ADD-LODR:ODR=101,CMD=ECHO,FIELD=3
ADD-LODR:ODR=101,INFO="LODR for Munich";
• Outdial rule 102 for Wiesbaden
ADD-LODR:ODR=102,INFO="LODR for Wiesbaden";
We use the 2xx (200 – 299) outdial rules to modify national station numbers:
• Outdial rule 200 for Germany:

ADD-LODR:ODR=200,INFO="LODR FOR Germany";
LCR route configuration:

One LCR route is required per city. We use the numbers of the outdial rule as an
index for the LRTE. (1xx = 100 – 199)
ADD-RICHT:MODE=LRTENEW,LRTE=100,LSVC=ALL,NAME="City
Berlin",TGRP=6,DNNO=1-1-199;
Munich",TGRP=5,DNNO=1-1-199;
Wiesbaden",TGRP=7,DNNO=1-1-199;
ADD-LDAT:LROUTE=100,TGRP= 6,ODR=100,LAUTH=1,LATTR=RERTEINT;
ADD-LDAT:LROUTE=101,TGRP= 5,ODR=101,LAUTH=1,LATTR=RERTEINT;
ADD-LDAT:LROUTE=102,TGRP= 7,ODR=102,LAUTH=1,LATTR=RERTEINT;
An LCR route is also required for all countries (LRTE 2xx = 200 – 299):
ADD-RICHT:MODE=LRTENEW,LRTE= 200,LSVC=ALL,
NAME="Germany",TGRP=5,DNNO=1-1-299;
ADD-LDAT:LROUTE=200,TGRP= 5,ODR=200,LAUTH=1,LATTR=RERTEINT
We now come to the source-dependent LCR:
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
The LCR routes are summarized in LCR profiles. Each source group is assigned
an LCR route.
Reminder:
We have already made the following assignments:
Node Source group Local area Local area  LRTE

1-1-5 1 Munich 101
1-1-6 17 Berlin 100
1-1-7 26 Wiesbaden 102
1-1-8 2 Munich 101
We use LCR profile 1 to modify local station numbers:

ADD-LPROF:PROFNAME="SUBSCR TO INTERNAT",
SRCGRP=1,LRTE= 101,PROFIDX=1;
CHANGE-LPROF:PROFIDX=1,SRCGRP=2,LRTE=101;
CHANGE-LPROF:PROFIDX=1,SRCGRP=26,LRTE=102;
We use LCR profile 2 to modify national station numbers:
ADD-LPROF:PROFNAME="NATIONAL TO INTERNAT",
LCR level 1 will be complete as soon as the selected station numbers are
assigned to the LCR profiles. The LCR required for this purpose can be derived
from the AMO KNPRE:
• The exit code is "0".
• The national prefix is "0“.
• The international prefix is "00“.
If the ISDN exit code is now dialed and neither of the prefixes, then a local
station number is dialed. The associated digit pattern is assigned to LCR profile
1:
ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP=0-W-
X,PROFIDX=1,LAUTH=1;
If the ISDN exit code is dialed, followed by the national prefix, but not by the
international prefix, then a national station number is dialed. LCR profile 2 is
used for the dialing process in this case:
ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP=0-W-0-
X,PROFIDX=2,LAUTH=1;
LCR level 1 is now fully generated. The international station number is evaluated
in LCR level 2.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
LCR level 2:
Only station numbers in international format are evaluated in level 2. They have
the same destination worldwide.
The following routing rules are defined for configuring LCR level 2:
• If the destination is an internal virtual node, the station number is routed back
to the local node based on reroute internal.
• External breakout is always performed via the local trunk. A separate LCR is
required for each source group in this case.
As some carriers do not permit national dialing with international station numbers,
an additional LCR configuration is required here.
The following routes should be covered by LCR level 2:
1. Internal destinations:
A single LRTE route is initially sufficient for all source groups (see also
Configuring "1. Internal destinations")
2. External international destinations:
This requires a separate LRTE for each source group, combined in a shared LCR
profile.
3. External national destinations:
As certain carriers or countries do not permit connections to national destinations

using the international number format, a separate LCR configuration per source
group is also required for national destinations. A separate LCR profile is then
created for each country, in which the LCR routes for national and international
destinations are used accordingly.
In order to prevent confusion between LCR level 1 and level 2, we will define in
our example that the LRTE routes 300 – 399 should be used for reroute internal.
For international destinations we will use LCR routes 400-499, and for national
destinations LCR routes 500-599.
Configuring "1. Internal destinations"

• Configuring an outdial rule
Here we can use the general outdial rule for international destinations. To
ensure uniform numbering, we will configure the outdial rule 300 for general
reroute internal:
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
ADD-LODR:ODR=300,CMD=NPI,NPI=ISDN,TON=INTERNAT;
ADD-LODR:ODR=300,INFO="LODR FOR REROUTE INTERNAL";
• Configuring LRTE 300 for general reroute internal:
ADD-RICHT:MODE=LRTENEW,LRTE=300,LSVC=ALL,NAME="SRC01 RERT
INT",DNNO=1-1-195;
ADD-LDAT:LROUTE=501,ODR=300,LAUTH=1,LATTR=RERTEINT;
• Configuring LDPLN entries for the internal E.164 station numbers:
ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LAUTH=1,LDP=0-W-00-49-89-
7221-X,LROUTE=300,LAUTH=1;
ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LAUTH=1,LDP=0-W-00-49-
631-7974-X,LROUTE=300,LAUTH=1;
Internal availability via ISDN station numbers is now ensured.
• Configuring outdial rules

As every source group uses different trunks for CO breakout, each source
group requires separate LCR routes. As the outdial rules are usually the same
for all LROUTES, it makes sense to share their usage.
We have defined that we want to use LCR routes 400-499 for international
destinations and routes 500-599 for national destinations.
In the description that follows, we will use the numbers 400 and 500 for the
general outdial rules and the LROUTES 4xx and 5xx for the LCR routes (xx
represents the source group. This results in the LROUTE numbers 401 to
599).
Defining the required outdial rules:
– Outdial rule 400 will be the general outdial rule for sending an explicit
international E.164 station number.
– Outdial rule 500 will be the general outdial rule for sending an explicit
national station number, which is necessary for destinations within the
local country.
Additional information on assigning outdial rules:
If other provisions apply for particular carriers or countries, the corresponding
outdial rules 3xx and 4xx are kept free to enable the relevant outdial rules to
be used for national and international station numbers.
– Configuring an outdial rule for international dialing:
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
ADD-LODR:ODR=400,CMD=NPI,NPI=ISDN,TON=INTERNAT;
ADD-LODR:ODR=400,INFO="LODR INTERNATIONAL";
– Configuring the outdial rule for national dialing:
ADD-LODR:ODR=500,INFO="LODR NATIONAL for INTERNATIONAL
NUMBERS";
• Configuring LCR routes:
– LRTE numbers 4xx (401 to 499) are used for connections to external
international destinations.
ADD-RICHT:MODE=LRTENEW,LRTE=401,LSVC=ALL,,NAME="SRC01
INTERNAT",TGRP=5,DNNO=1-1-195;
– The subscriber’s own trunk group is seized directly and the international
station number (LODR 400) is transmitted.
ADD-LDAT:LROUTE=401,TGRP=5,ODR=400,LAUTH=1;
– The 5xx LRTE numbers (501 to 599) are used for connections to external
national destinations.
ADD-RICHT:MODE=LRTENEW,LRTE=501,LSVC=ALL,NAME="SRC01
INLAND",TGRP=5,DNNO=1-1-195;
– The subscriber’s own trunk group is seized directly and the national
station number (LODR 500) is transmitted.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
Once the LCR routes have been configured, these are assigned to the LCR
profiles.
• Configuring the LCR profile

The simplest LCR profile is for connections to countries in which there is no
separate CO breakout, but rather just general international breakout.
As LCR profiles 1 and 2 have already been used for general modification in
LCR level 1, we will use LCR profile 3 for the general international breakout,
and assign this profile the corresponding 4xx LRTE numbers:
ADD-LPROF:PROFNAME="INTERNAT
DIRECT",SRCGRP=1,LRTE=401,PROFIDX=3;
For every country where CO breakout is available, an additional LCR profile
is required for national destinations. As we have defined that CO breakout
should always be performed from the local CO, a separate LCR profile is
required for every destination country for this purpose, comprising an
individual combination of national and international LCR routes.
Our example only includes breakouts in Germany. As a result, we require an
LCR profile with uniform national destinations:
LCR profile 4 is for external destinations in Germany (LRTE 5xx for direct
breakout to the national network):
ADD-LPROF:PROFNAME="CO GERMANY",SRCGRP=1,LRTE=501,PROFIDX=4;
57.3.3.7 Future Expansions
1. If another virtual node were to be added in Germany, the following additional

measures would be required:
• Configure the virtual node number as OWNNODE.
• If the station numbers do not correspond to an existing DPLN group, you

may need to configure a new DPLN group.
• The new virtual node must be configured with the AMO KNDEF.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
• The new subscribers must be configured.
• The subscribers must then be assigned the LCR profile if this is not
already specified by the hardware configuration.
• Configure the trunk group with the trunks for this node.
• Expansion of LCR level 1:
– For every new city, a new outdial rule must be configured with the
number 1xx for Hamburg.
– This outdial rule must be configured for the LCR route with the
number of the outdial rule as the LRTE number.
– The new LRTE must be assigned LCR profile 1.
– In addition, LCR profile 2 (Germany) must be expanded to include

new source groups.
– A new LTRE must be configured for this source group for all LCR
routes from LTRE 3xx onwards (in our example LTRE 3xx to 6xx).
– Existing LCR profiles greater than or equal to 3 (3 to 5 in our example)

must be expanded to include the new source group.
– The new station number must be assigned LCR profile 4 for internal
destinations in Germany.
Example:
The system is expanded to include an IPDA shelf in the Reperbahn district.
The AP is assigned the LTU number 40. Accordingly, it is assigned source
group 40. The virtual node number is 1-1-4 with the node code 94. The ISDN
station number is +49 40 2889 – X.
LCOSV2=1,LCOSD1=1,LCOSD2=1;
(CHANGE-SDAT:STNO=941000&&941999,TYPE=DATA1,SRCGRP=40;)
0,COTNO=20,COPNO=20,DPLN=0,ITR=0,COS=1,LCOSV=1,LCOSD=1,CCT
="CO Hamburg 194",
DESTNO=99,PROTVAR=EDSGER,SEGMENT=1,ATNTYP=CO,ISDNIP=00,ISD
NNP=0,TRACOUNT=8,NNO=1-1-
194,TGRP=4,SRCHMODE=ASC,INS=Y,DEV=S2COD,BCHAN=1&&30,BCNEG=
Y,BCGR=1,LWPAR=1, SRCGRP=40;
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
ADD-LODR:ODR=103,CMD=NPI,NPI=ISDN,TON=INTERNAT;
ADD-LODR:ODR=103,INFO="LODR FOR Hamburg";
ADD-RICHT:MODE=LRTENEW,LRTE= 103,LSVC=ALL,NAME="SRC
Hamburg",TGRP=4,DNNO=1-1-194;
ADD-LDAT:LROUTE=103,TGRP=
4,ODR=103,LAUTH=1,LATTR=RERTEINT;
INT",TGRP=4,DNNO=1-1-194;
4,ODR=300,LAUTH=1,LATTR=RERTEINT;
NAT",TGRP=4,DNNO=1-1-194;
ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LAUTH=1,
LDP=0-W-00-49-40-2889-X,PROFIDX=4;
2. If another virtual node were to be added in a new country, for example Austria,
then the following measures are required:
• Configure the virtual node number as OWNNODE.
• If the station numbers do not correspond to an existing DPLN group, you

may need to configure a new DPLN group. (In our example we expand
the DPLN to include five-digit station numbers.)
• The new virtual node must be configured with the AMO KNDEF.
• The new subscribers must be configured.
• The subscribers must then be assigned the LCR profile if this is not
already specified by the hardware configuration. (In our example, two
source groups are required because the location is large and is
distributed over 2 APs.)
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
• Configure the trunk group with the trunks for this node.
– For every new city, a new outdial rule must be configured with the
number 1xx for the company in Austria.
– This outdial rule must be assigned to the LCR route with the LRTE
number of the outdial rule.
– The new LRTE must be assigned to LCR profile 1 for both source
groups.
– A new outdial rule with the number 2xx must be configured for the
new country, Austria.
– This outdial rule should be assigned to the LCR route with the LRTE
number of the outdial rule.
– The new LRTE is to be assigned to LCR profile 2 with both source

groups.
– A new LTRE must be configured for this source group for all LCR
routes from LTRE 3xx onwards (in our example LTRE 3xx to 6xx).
– Existing LCR profiles greater than or equal to 3 (3 to 5 in our example)

must be expanded to include the new source group.
– Two new LCR profiles must be configured for the destination Austria,
Profile 6 for reroute internal and Profile 7 for direct breakout to the
central office.
– The new station number must be assigned LCR profile 6 for internal
destinations in Germany.
– External station numbers in Austria must be assigned LCR profile 7.

Example:
The system is expanded to include two IPDA shelves at the Prater site. The
APs are assigned the LTU numbers 42 and 43. This is why they are assigned
source groups 42 and 43. The virtual node number is 1-1-3 with the node
code 93. 
The ISDN station number is +43 5 1707 – X.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
CHANGE SDAT is omitted because in this case the source group is
already assigned to the PEN via the AMO UCSU. Luckily, neither of the
APs contains an additional virtual node :-)
ADD-BUEND:TGRP=2,NAME="BDL AP42 KN1-1-3",NO=30;
ADD-BUEND:TGRP=3,NAME="BDL AP43 KN1-1-3",NO=30;
="CO Vienna
192",DESTNO=92,PROTVAR=EDSAUT,SEGMENT=1,ATNTYP=CO,ISDNIP=0
0,ISDNNP=0,TRACOUNT=8,NNO=1-1-
="CO Vienna
193",DESTNO=93,PROTVAR=EDSAUT,SEGMENT=1,ATNTYP=CO,ISDNIP=0
0,ISDNNP=0,TRACOUNT=8,NNO=1-1-
ADD-LODR:ODR=104,INFO="LODR for Company in Austria";
NAME="SRC Company in Austria",TGRP=3,DNNO=1-1-193;
ADD-LODR:ODR=201,INFO="LODR FOR Austria";
NAME="Austria",TGRP=3,DNNO=1-1-193;
INTERNAT",TGRP=2,DNNO=1-1-192;
ADD-LDAT:LROUTE=342,TGRP=2,ODR=300,LAUTH=1;
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Generation
ADD-RICHT:MODE=LRTENEW,LRTE=442,LSVC=ALL, ,NAME="SRC42
INLAND",TGRP=2,DNNO=1-1-192;
INT",TGRP=2,DNNO=1-1-192; ADD-
RICHT:MODE=LRTENEW,LRTE=543,LSVC=ALL,NAME="SRC43 RERT
INT",TGRP=3,DNNO=1-1-193;
NAT",TGRP= 2,DNNO=1-1-192;
NAT",TGRP=3,DNNO=1-1-193;
ADD-LPROF:PROFNAME="RERT AUSTRIA",
ADD-LPROF:PROFNAME="CO AUSTRIA",
LDP=0-W-00-43-5-1707-X,PROFIDX=6;
LDP=0-W-00-43-X,PROFIDX=7;
A separate description will be created for the topic of networking.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
OpenScape 4000 Manager
57.3.4 Connecting External Systems

If an external system or carrier is unable to send the called party number as a
subscriber, national or international station number, then the corresponding trunk
must be assigned to a virtual node with the AMO TDCSU parameter VNNO. The
stations in this node will then be reached by this trunk with the station number.
Stations in other virtual nodes can be reached by this trunk by dialing the node
code + station.
1,COTNO=20,COPNO=20,DPLN=0,ITR=0,COS=1,LCOSV=1,LCOSD=1,CCT="S
2
CO",DESTNO=99,PROTVAR=EDSGER,SEGMENT=1,ATNTYP=CO,ISDNIP=00,IS
DNNP=0,TRACOUNT=8,NNO=1-1-
CGR=1,LWPAR=1,VNNO=1-1-95;
57.4 OpenScape 4000 Manager
VNR cannot be activated from CM. The feature can only be activated using the
parameter VNR in the AMO ZANDE (see Command for feature activation). The
value of the corresponding flag is shown in CM. However, this cannot be
administrated from CM.
VNR mode not activated

If VNR is not activated only unique station numbers with a maximum of 6 digits
are accepted. The numbers must be independent of the DPLN; similar numbers
will not be accepted. Virtual nodes are also independent of the DPLN.
VNR mode activated

If you wish to switch to the mode "VNR activated", you must execute the AMO
ZANDE and set the VNR flag to YES. In CM, the display of station numbers is
taken from the AMO.
If the user activates the global flag in a particular OpenScape 4000, the display
of the relevant station numbers in the OpenScape 4000 Manager database is no
longer applicable. The display in the Manager/Assistant depends strongly on the
display in the AMO. If the display in the system changes, an upload with the new
displayed numbers must be performed without delay in OpenScape 4000
Manager/Assistant. Following modification to the VNR flag, Upload All must be
implemented. With Upload All, all station numbers are returned as 12-digit
numbers including the access code of the virtual node (VNAC). In CM, the display
of all station numbers loaded by the relevant system is adapted. DPLN-
dependent virtual nodes can be configured; identical and similar numbers are
permitted.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
With the current implementation, routing cannot be correctly performed when

systems with and without VNR are operated in one domain. However, there are
current scenarios that support this option.
As the current Manager implementation only supports routing in domains where

VNR is either globally activated or globally deactivated, new V4 systems where
VNR is activated should be assigned to a separate domain.
Customers can continue to enter abbreviated numbers when configuring station

numbers. During saving, the numbers are then automatically extended. Once
saving has been successfully completed, the numbers are shown in full.
57.4.2 Modifying the User Interface
57.4.2.1 "System" Window
Call up via Configuration Management > Network > System
Changes in this dialog:
• New flag VNR Active
As it is not possible to administrate the global flag from the AMO ZANDE via CM,
the user cannot modify the status of the checkbox.
57.4.2.2 "Station" Window
Call up via Configuration Management > Station > Station
There are four changes in this dialog.
• Station No. has been extended so that station numbers with 12 digits can
now be displayed.
• The flag VNR Active was added. This flag cannot be edited and is displayed
for information purposes only.
• The access code for the virtual node (VNAC) is displayed directly next to the
field Virtual Node ID.
• The field DPLN Group (tab page Base 1) was added.
Configuring a new station in a system with VNR

• Using the virtual node assigned as standard
When configuring a new station, the user does not need to specify a Virtual
Node ID. This is an optional input parameter. If the user does not input any
information, the virtual node assigned as standard is used for the station in
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
question. The standard node for the relevant system is the virtual node for
which the Default Entry checkbox is selected in the "Virtual Nodes (KNDEF)"
Window.
The Virtual node ID is in fact a mandatory parameter that is automatically
filled when the user does not input specific information.
• Using the standard DPLN group of a virtual node

Standard DPLN group usage is similar to that of the virtual node assigned as
standard. A DPLN group must be declared as standard for every virtual node.
If the user leaves the field for the DPLN group entry empty, this is
automatically filled with the value of the standard DPLN group for the selected
virtual node.
57.4.2.3 "Virtual Nodes (KNDEF)" Window
Call up via Configuration Management > Network > Virtual Nodes (KNDEF)
Configuring a new virtual node

Situation up until now: Virtual nodes are not DPLN-dependent.
With the VNR feature it is now possible to configure DPLN groups in virtual nodes.
The user can configure a new virtual node as DPLN-dependent by deactivating

the corresponding checkboxes for particular DPLN groups. A standard DPLN
group must then be selected. In the selection list for the standard DPLN group, all
authorized DPLN groups are offered.
Forwarding information to virtual nodes

In the Virtual Nodes (KNDEF) dialog, data regarding the selected virtual node
can be forwarded to other systems in the same domain or to all systems in the
network. With this new function, users can correctly configure virtual nodes.
When correctly configured, a virtual node will have the same access code
(VNAC) in all systems.
As the access code for virtual nodes (VNAC) cannot be modified for systems
where VNR is activated, the forwarding function can only be used when
configuring new virtual nodes.
57.4.2.4 Station Relocation
IMPORTANT: Stations can only be relocated to another system at the same

virtual node.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
AMO Interrelationships
Relocation is not permitted if the same virtual node as in the source system is not
configured in the destination system. OpenScape 4000 Manager CM does not
configure virtual nodes in the background during relocation. As a result, users
cannot modify the virtual Node Access Code when relocating to another system.
Modification of the virtual Node Access Code must be performed in a separate

step or after relocation has been completed.
57.5 AMO Interrelationships
57.5.1 Attendant Console Groups
Even if the VNR feature is activated, all attendant consoles/attendant console

groups for each node should be available under the same number.
The access code for incoming trunk calls (ATND) and attendant code (MEL) for
internal calls are configured on a node-dependent basis, as are the personal
station numbers of the attendant consoles. In the same way as with VNR stations,
the same codes can therefore also be used in multiple virtual nodes.
If, for example, attendant console groups distributed across several physical
nodes (OpenScape 4000 systems) are moved to one physical and several virtual
nodes, the attendant console groups can retain their codes, but will be addressed
uniquely via the node code of the virtual node and the existing codes of the
attendant console group.
IMPORTANT: If VNR is activated, attendant console groups and attendant

consoles can only be uniquely reached with the node code of the virtual node
where the codes are configured.
57.5.1.2 Example
OpenScape 4000 is located in Munich and AP in Hamburg. One attendant

console group each is configured at both locations with the same codes (access
code 0 for calls from the central office and attendant code 900 for internal calls).
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Figure 81 Attendant console groups with VNR
Availability of attendant consoles/attendant console groups

• From the CO with the relevant E.164 station number in accordance with the
virtual node and access code (Example: As shown in the diagram, 089 722 0
to the Munich AC group or 040 555 0 to the AC group in Hamburg).
• Stations at the OpenScape 4000 or the AP reach the AC group belonging to

the local virtual node via the attendant code without the node code (900).
They reach the AC group belonging to another virtual node by dialing the
node code and attendant code (from Munich to Hamburg e.g. 96 900)
• Stations at the OpenScape 4000 or the AP reach the attendant console

belonging to the local virtual node via their own station number without the
node code (4480). They reach an attendant console belonging to another
virtual node by dialing the node code and their own station number (from
Munich to Hamburg e.g. 96 4410)
Administration for the application example

• Configuring the station numbers in the DPLN
DAR = ATND (900)
DAR = ATND (0)
DAR = VPI (4410,4411,4480)
(DAR = GENANS)
• Configuring the attendant consoles in the AMO ACSU
ADD-ACSU:ATNDNO=954480,...;
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
• Configuring the night options

ADD-NAVAR:NOPTNO=1,TYPE=STN,STNO=952100;
ADD-NAVAR:NOPTNO=3,TYPE=CASINT,ATNDGR=2;
ADD-NAVAR:NOPTNO=4,TYPE=CASINT,ATNDGR=1;
• Configuring the attendant console groups
ADD-VFGR:ATNDGR=1,QUEMODE=DW,ATNDNO=954480,....;
ADD-VFGR:ATNDGR=2,QUEMODE=DW,ATNDNO=964410&964411,....;
• Configuring the code - group assignments
ADD-VFGKZ:TYPE=ATNDGR,CD=950,CPS=6,ATNDGR=1;
57.5.2 VNR with Code Calling/Multiple Code Calling

(CC/MCC)
In a OpenScape 4000 that is divided into several virtual nodes, there is one
central MCC configuration and thus just one central MCC search table.
Consequently, the station number entries must be unique, which means they
must be entered with the node code.
The same applies for the administration of the station number/code-calling

number evaluation table in the AMO PERSI for station number entry. The original
limitation of the station number length to six characters was extended to twelve.
A user can basically select either an MCC paging job or an MCC callback job with
or without node code. The relevant virtual node code is automatically added for
the selected station number depending on the PEN of the user (virtual node or
HHS).
If the paging party is in the same virtual node as the paged party, node codes are
not displayed; the node code is displayed if the parties are in different virtual
nodes.
Call forwarding to MCC can only be programmed over the menu by entering the
MCC code. The associated station number is automatically generated (always
with the node code).
If MEETME is set as the operating mode, the paging job can also be extended to
include the A BLOCK (paging party’s station number). This is done by assigning
a length to the MABLK parameter in TSCSU. The station number is generated
following VNR rules within this length specification.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
If the paging and paged parties are in the same virtual node, then generation
takes place without a node code. If the paging and paged parties are in different
virtual nodes, then generation takes place with the node code.
Another parameter specifies at which end the station number generated should
be truncated if it exceeds the preset length setting.
In DISPLAY mode, the paging job consists of the paged party’s station number.
Here again, the station number is generated with or without the node code
depending on the PENs of the paging and paged parties.
If you set "Long code-calling number > 0", the MCC operates without digit
analysis for the code-calling number which means VNR interaction is not
performed for it.
The same rules apply for CC.
GUI impact
• The station number/code-calling number table is always administered with
station number + node code. In contrast to the station number, the code-
calling number remains restricted to a maximum of six digits.
• Paging and callback jobs within a virtual node continue to omit the node code.
• The node code must always be entered for paging and callback jobs across
virtual nodes.
• The format of the paging job issued and the paging display always depends
on virtual node assignment for the paging and paged parties.
Scenario:
STN 4711 from virtual node 722 is paged and appears in the search table with
node code 722.
STN 4711 from virtual node 723 is paged and appears in the search table with
node code 723.
• STN 4700 can register on STN 7224711 without dialing the node code
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
• STN 4700 can only register on STN 7234711 when the node code is
dialed
• STN 4701 can only register on STN 7224711 when the node code is
dialed
• STN 4701 can register on STN 7234711 without dialing the node code
57.5.3 VNR with Alternate Routing on Error (ARoE)

The parts of ARoE that have relevance for VNR include scenarios for AP
Emergency or HFA Alternate Logon.
In these cases, there is usually an entire group of stations from specific areas
(APs) in a OpenScape 4000 that cannot be reached.
To avoid having to configure alternative station numbers for each individual

station (storage space), you can use the AMO APRT to configure a partially
qualified alternative station number for an entire source group and then append
this number with the station number you want to use.
This number appended always includes the node code.
When performing administration with the AMO APRT, ensure that the parameter
that defines the maximum length of the station number you want to expand is
sufficiently large so as to accommodate the length of station numbers and virtual
node numbers in the case of different station number lengths.
OpenScape 4000 supports length specifications that exceed the actual station
number generated. If the station number generated exceeds the length specified,
this number is truncated from the left.
You can use this mechanism when an HFA telephone tries by mistake to log on
to a non-NUN node in which its station number is configured without node code.
GUI impact
• Consider VNR relevance when configuring the alternate routing number with
APRT or SDAT.
• If the alternate routing number is configured as partially qualified (only

possible with the AMO APRT), you should specify a length that will
accommodate the station number to be generated.
• If the alternate routing number is completely configured, check whether it

must be administered with the node code.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
57.5.4 Applications
The following applications and tools are available with this feature in the versions
listed:
OpenScape 4000
Application/Tool Version Status
CMI/CATool ? ?
Gateways (CGW) + Admin LW line 11 or 21 Tests conducted in system test.
IPDA access points (AP) LW line 11 or 21 Tests conducted in system test.
QDC ? Tests†with V4 without VNR OK
QCU ? Tests†with V4 without VNR OK
HOT => (PCDACON ?) V4.0 (PCDACON No test in system test
open)
Applications
CAP (Common V3.0 SMR 5 6.0 Tests with VNR OK
Application Platform)
BLF (Busy Lamp Field V3.0 Tests with VNR scheduled for E03/
application) 07
AC-WIN (Attendant V5.0/MQ v3.0 Tests with VNR OK
Console)
DS-WIN V3.0 Tests with VNR scheduled for E03/
07
DTB (Display Telephone --- Does not support VNR!!!
Book)
ASC (Attendant V5.0 Tests with VNR scheduled for E03/
Supervisor Console) 07
Com Assistant V2.0 Operates in FT with V4.0 without
VNR
Simply Phone V4.0 Simply Phone for Web V3.1 does
not work with CAP V3.0 and
consequently was not tested.
Simply Phone for Outlook/Lotus
Notes tested without VNR.
Xpressions 470 V4.0/V5 Tests without VNR with V4 OK
Pro Center V7.0 Request sent to Trango, no answer
yet
Teleworking (HiPath V2.6 does not run with No test because status is M5
Corporate Connect) VNR
Hospitality V2.0/V2.1 Tests with VNR scheduled for E04/
07
OpenScape Agile V2.0 No test required according to Mr.
Paschdeka
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
DAKS Not available in the system test,

operates in int. FT without VNR
OpenScape 4000 Management Applications (Manager & Assistant)
CM (Configuration ? ?
Management)
COL V2.0 Tests with VNR scheduled
PM (Performance V2.0 Tests with VNR scheduled
Management)
SNMP ? ?
TSKA ? ?
RDS ? ?
ACL Tracer ? ?
OpenScape Management Applications
UM (User Management) V2.0 Tests with VNR scheduled for E03/
07
AM (Accounting V2.0 Tests with VNR scheduled for E03/
Management) 07
FM (Fault Management) V3.0 Tests with VNR scheduled for E03/
07
QM (Quality of Service V1.0 Tests with VNR scheduled for E03/
Management) 07
DLS (Deployment ? No tests yet, tests with SPE
Service)
Endpoints
Analog phones ? Tests with VNR OK
TDM phones ? Tests with VNR OK
IP phones HFA V5.1 Tests with VNR OK
IP phones SIP V6.0 Tests with VNR OK
CMI phones V3.0 Tests with VNR OK
WLAN IP phones V1.0 Tests with V4.0 OK (without active
VNR)
optiClients V5.1 HFA/V4.0 SIP Tests with VNR OK
57.5.5 Modified Display for E.164

The following display format options are available for virtual station numbers:
• Node code + station number (AMO ZANDE, parameter

DISPMOD=UNKNOWN),
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Relevant AMOs
• PNP data + station number (AMO ZANDE, parameter DISPMOD=PRIVATE),
• E.164 data + station number (ZANDE, parameter DISPMOD=ISDN)
Data in AMOs KNDEF, KNFOR, and KNPRE is accessed.
This modified display only applies to incoming/outgoing station numbers.
Station numbers saved for key functions or administered using AMOs are always
stored in the format node code + station number.
57.6 Relevant AMOs

The following AMOs and parameters specified must be considered when
activating the feature:
AMO Parameter Sprache/ Beschriebung/Description

Language
ACDGP SUPERRNR d Knotenkennzahl + Teilnehmerrufnummer
SUPEXT e node number + extension number
ACDRT TLNNU d Knotenkennzahl + Teilnehmerrufnummer
STNO e node number + extension number
ACDSD RCGADR d Knotenkennzahl + Teilnehmerrufnummer
CAFDN e node number + extension number
ACSU VFNU d Knotenkennzahl + persönliche Rufnummer
des VF
ATNDNO e node number + individual attendant number
ACTDA ZIELRNR d Knotenkennzahl + Teilnehmerrufnummer
RNR
DESTNO e node number + extension number
STNO
AGENT AUTORNR d Knotenkennzahl + Teilnehmerrufnummer
AUTOEXT e node number + extension number
AUN TLNNU d Knotenkennzahl + Teilnehmerrufnummer
BERUM TLNNU d Knotenkennzahl + Teilnehmerrufnummer
CHESE CHEF d Knotenkennzahl + Teilnehmerrufnummer
SEK
VTR
EXEC e node number + extension number
SECR
REP
ALTCHEF d Knotenkennzahl + Teilnehmerrufnummer
NEUCHEF
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Relevant AMOs

Language
OLDEXEC e node number + extension number
NEWEXEC
ALTSEK d Knotenkennzahl + Teilnehmerrufnummer
NEUSEK
OLDSECR e node number + extension number
NEWSECR
COMGR TLNNU d Knotenkennzahl + Teilnehmerrufnummer
DCIC TLNNR d Knotenkennzahl + Teilnehmerrufnummer
DIDCR REGEL d Knotenkennzahl + Teilnehmerrufnummer
DIGITS e node number + extension number
DIMSU ZANLNUNT d Anzahl der Netzwerk-Teilnehmer mit
mehrdeutigen Nummern.
NWNUNSUB e number of network subscribers with
ambiguous numbers
DSSU TLNNU d Knotenkennzahl + Teilnehmerrufnummer
HISTA TLNNU d Knotenkennzahl + Teilnehmerrufnummer
HOTLN ZIEL d Knotenkennzahl + Teilnehmerrufnummer
DEST e node number + extension number
KCSU TLNNU d Knotenkennzahl + Teilnehmerrufnummer
TLNNUSEK d Knotenkennzahl + Teilnehmerrufnummer
=> muss gleiche Knotenkennzahl wie
TLNNU haben, d.h. im gleichen Virtuellen
Knoten sein
STNOSEC e node number + extension number
=> must be the same node number as in
STNO, they must be in the same virtual
node
KNDEF DFLT d Default Knoten (nur bei TYP=EIGEN)
DFLT e default node (only with TYPE=OWN)
KNNR d Virtuellle Knotennummer.
Führende Nullen können eingegeben
werden, werden aber unterdrückt.
Nachfolgende Nullen sind nur bei Knoten
vom TYP=FREMD erlaubt.
Knotennummer 0-0-0 bedeutet Rest der
Welt.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Relevant AMOs

Language
NND e virtual node number
Leading zeros can be entered; however,
these will be suppressed.
Trailing zeros are only permitted with
TYPE=EXTERNAL nodes.
node number 0-0-0 means rest of world
ISDNSK d ISDN Skip Digits. Anzahl der Stellen von
Parameter ISDNLC die übersprungen
werden müssen um die Teilnehmernummer
zu extrahieren, wenn die
Teilnehmernummer und die
Hauptanschlussummer sich überlappen
ISDNSK e ISDN skip digits. Number of digits of
parameter ISDNLC which are to skip to
extract the extension number when
extension number and office code overlap
ISDNCC d ISDN Landeskennzahl (country code).
Standardwert: * (keine Landeskennzahl)
ISDNCC e ISDN country code. Default value: * (no
country code)
ISDNAC d ISDN Ortskennzahl (area code).
Standardwert: * (keine Ortskennzahl)
ISDNAC e ISDN area code. Default value: * (no area
code)
ISDNLC d ISDN Hauptanschlussnummer.
Standardwert: ********** (keine
Hauptanschlussnummer)
ISDNLC e ISDN local destination code. Default value:
********** (no local destination code)
KNOTENKZ d Knotenkennzahl fuer Rufnummernplan
unknown
NODECD e Node access code for numbering plan
unknown
WABE d WABE Gruppe, die zur Bewertung der
Zielrufnummer verwendet werden soll
DPLN e dialplan group, that should be used for
evaluating the destination number
EWABE d In diesem Virtuellen Knoten erlaubte WABE
Gruppen für die darin eingerichteten
Teilnehmer. Dieser Parameter wird nur für
AMO Konsistenzchecks benötigt.
ADPLN e DPLN groups permitted in this virtual node
for the stations configured in this node. This
parameter is only required for AMO
consistency checks.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Relevant AMOs

Language
KNOTKZSK d Skip Digits fuer Knotenkennzahl (Parameter
KNOTENKZ). Anzahl der Stellen von
Parameter KNOTENKZ die übersprungen
werden müssen um die Teilnehmernummer
zu extrahieren, wenn die
Teilnehmernummer und die
Knotenkennzahl sich überlappen
NODECDSK e Skip digits for node access code (parameter
NODECD). Number of digits of parameter
NODECD which are to skip to extract the
extension number when extension number
and node access code overlap
LEMAN TLNNU d Knotenkennzahl + Teilnehmerrufnummer
DUWA2
DID2
LIN TLNNU d Knotenkennzahl + Teilnehmerrufnummer
NAVAR TLNNU d Knotenkennzahl + Teilnehmerrufnummer
einer Nachtnebenstelle
STNO e node number + extension number of night
service station
RNR d Knotenkennzahl + Platzkennzahl der
externen ZVFGR
CD e node number + extension number for
ecternal centralized ATND service
PERSI RUFNU d Knotenkennzahl + Teilnehmerrufnummer
RUFUM DUWA1,DUWA2,F d Knotenkennzahl + Teilnehmerrufnummer
AX2
DEEZ
DID/DID2 e node number + extension number
FAX2
DTEZ
SA RNR d Master-Sammelanschluss:
Knotenkennzahl + Teilnehmerrufnummer
CD e master hunting group:
node number + extension number
SBCSU TLNNU d Knotenzahl + Teilnnehmernummer
WABE d Muss eine der erlaubten WABE Gruppen
des Parameters EWABE im AMO KNDEF
sein.
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Relevant AMOs

Language
DPLN e One of the permitted DPLN groups of the
parameter ADPLN must be included in the
AMO KNDEF.
SCSU TLNNU d Siehe SBSCU
STNO e see SBCSU
WABE d Siehe SBSCU
DPLN e see SBCSU
SDAT KNNR d virtuelle Knotennummer
Umkonfigurieren eines Teilnehmers in einen
anderen Virtuellen Knoten.
NNO e virtual node number
Station reconfiguration in another virtual
node.
SSC ARUFNU d Knotenkennzahl + Teilnehmerrufnummer
des ABF-Anschlusses für AMO NAVAR
UNANO e node numbe r+ extension number of night
answer station
SSCSU TLNNU d Siehe SBSCU
STNO e see SBCSU
WABE d Siehe SBSCU
DPLN e see SBCSU
SXSU TLNNU d Knotenkennzahl + Teilnehmerrufnummer
HAUPTNU
TLNNUX
MAINO
STNOX
TACSU ENACHT d Knotenkennzahl + Teilnehmerrufnummer
INIGHT e node number + extension number
TDCSU ENACHT d Knotenkennzahl + Teilnehmerrufnummer
INIGHT e node number + extension number
TGER TLNNU, d Knotenkennzahl + Teilnehmerrufnummer
FAXRU,
DEERU
GERRU
FAXNO
DTENO
NUSTNNO
TSU RNR d Knotenkennzahl + Teilnehmerrufnummer
VBZGR TLNNU d Knotenkennzahl + Teilnehmerrufnummer
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Relevant AMOs

Language
VFGKZ RNR d Knotenkennzahl + Meldekennzahl bei KZP
MEL
Knotenkennzahl + Platzkennzahl bei KZP
VPL
Knotenkennzahl + Abfragekennzahl bei
KZP ABF
CD e node number + internal call code.for DAR
ATND
node number + indial call code for DAR
ATNDDID
node number + answering station number
for DAR=GENAN
VFGR VFNU d Knotenkennzahl + Persönliche Rufnummer
eines zugeordneten Tag-VF der VF-Gruppe
ATNDNO e node number + individual Attendant number
WABE KZP d KZP=TLN kann jetzt WABE Gruppen
abhängig eingerichtet werden
KZP=EIGENKZ für die Knotenkennzahl des
Virtuellen Knotens – ist WABE Gruppen
unabhängig
DAR e Using DAR=STN, DPLN groups can now be
configured independently
DAR=OWNNODE for the node code of the
virtual node – is independent of the DPLN
group
RNR d Rufnummer
CD e extension number
ZLNR d Zielnummer
Wird benötigt wenn Teilnehmer eines
virtuellen Knotens sich in verschiedenen
physikalischen Knoten befinden.
Required when virtual node stations are
located in different physical nodes.
WABE d WABE-Gruppe
ermöglicht die Eingabe einer neuen
Teilnehmer - WABE Gruppen Zuordnung
DPLN e dial plan
enables a new station - DPLN group
assignment to be entered
ZANDE VNR d Leistunsgmerkmal “Virtueller
Rufnummernplan”
VNR e Feature “Virtual Node Number”
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Relevant AMOs

Language
DISPMOD d Mögliche Werte:
UNBEK=Nicht-VNR: Bei deaktiviertem
virtuellen Rufnummernplan (Feature VNR)
wird die Teilnehmer Nummer im kuerzest
moeglichen Format angezeigt. VNR: Bei
aktiviertem virtuellen Rufnummernplan
(Feature VNR) wird die Teilnehmer Nummer
im Format KNOTENKZ +
Teilnehmernummer angezeigt, z.B. 100 or
20 100
PRIVAT=Die Anzeige erfolgt im Format
Privater Nummerierungs - Plan , z.B.. 9 44
777 100
ISDN=Die Anzeige erfolgt im E.164-
Rufnummern-Format, z.B. 0 089 722 100
DISPMOD e Possible values:
UNKNOWN=Non VNR: For deactivated
vitual numbering (feature VNR) the display
of shortest possible subscriber numbers is
done VNR: For activated vitual numbering
(feature VNR) the display is done in format
NODECD + subscriber number, e.g. 100 or
20 100
PRIVATE=display of subscriber number in
privat numbering plan format, e.g. 9 44 777
100
ISDN=display of subscriber number in
E.164 format, e.g. 0 089 722 100
ZIEL QLRUFNU d Quellrufnummer AUL
SRCNO e station number of source FWD
TYP=NA d Namenstaste DR
TYPE=NAME e name key DSS
TZLRUFNU d Ziel-Rufnummer für Namenstasten
DESTNON e destination number for name keys
BUZRUFNU d Knotenkennzahl + Teilnehmerrufnummer
DZLRUFNU
RUFNU
ZLRUFNU
BZLRUFNU
KZLRUFNU
DESTNOBZ e node number + extension number
DESTNOD
EVMCD
DESTNOF
DESTNOM
DESTNOR
A31003-H3170-S103-6-7620, 02/2019
vnr_en.fm
Relevant AMOs

Language
ZIELN TLNNU d Knotenkennzahl + Teilnehmerrufnummer
RNRRU
RNRBK
RNR1
RNR2
DZLRUFNU
VTRSEK
RNRCH1
RNRCH1V
RNRCH2
RNRCH2V
RNRCH3
RNRCH3V
RNRCH4
RNRCH3V
STNORXFR
STNOMB
STNO1
STNO2
DESTNOD
STNOREP
STNOEX1
STNOEX1R
STNOEX2
STNOEX2R
STNOEX3
STNOEX3R
STNOEX4
STNOEX4R
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
General
58 Voice Compression
58.1 General
58.1.1 Task of the Feature

The feature Voice Compression (VC) increases the capacity of speech channels
on S0/S2 trunks.
B-channels speech channels

without VC with VC
per S0 trunk 2 up to 7
per S2 trunk 30 up to 112
If a S0/S2 B-channel is configured for VC, it can only be used for voice
communication. Therefore it is possible to use only some and not all B-channels
of a S0/S2 circuit by VC.
From ATM level 3 an STMA circuit can be a partner circuit, provided the STMA
board is configured as "STMA networking 1.0 (=backboning, ATMPBB)’’ or as
STMA networking 2.0 (=Networking 2.0, ATMNW20). With operating mode
"ATMNW20" only ATMPVCxx circuits should be configured, as ATMSVC circuits
do not support the required functions.
Other STMA functions for this feature have not yet been released . An STMA
circuit handles like an S2 circuit and will not be described in detail.
58.1.2 The Voice Compression Board

Voice Compression needs a new board called VCM (Voice Compression Module)
which is available in two versions:
Name Item number description

VCM-B15 Q2235-X This is the standard VCM with 15 B-channels.
It occupies 4 B-channels of a S0/S2 board.
In case of a S0 board the 4 B-channels 
(2 S0 trunks) have to be in the same trunk group.
VCM-B7 Q2235-X100 This variant of VCM with 7 B-channels occupies 2 B-
channels of the S0/S2 board.
It should be prevential used if on a S0/S2 board not
more than 2 B-channels can be occupied.
• The G.728 Standard is used for compression.
• The VCM supports a transit mode where the voice data will stay compressed.
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
General
• The VCM can be used only with the new Atlantik architecture.
58.1.3 Description of Synonyms which are Used
VCSU: The compressed B-channels of a VCM are merged to a Voice Compression

SubUnit.
The assignment of VCM B-channels to a VCSU is always fix.
VCSU VCM Channels

1 D-channels
B-channels 1-3
2 B-channels 4-7
3 B-channels 8-11
4 B-channels 12-15
Partner board: S0/S2 STMA board, which will be used to transmit the
compressed speech channels.
Partner B-channel: B-channel of a S0/S2 STMA board, which is connected via
a Nailed Connection with a VCSU of a VCM.
Nailed Connection (NC): Expression for a permanent Switching Network connection.
In case of Voice Compression it’s the connection between a
VCSU and a Partner B-channel.
58.1.4 Functional Overview

The VCM compress the 64KBit/s B-channels to the 16KBit/s sub-channels. One
S0/S2 B-channel (64KBit/s) will be used to transmit 4 sub-channels to the other
OpenScape 4000 node.
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
General
Legende:
OpenScape 4000 64 kbit/s time slot
with one 
subscriber DIU
board uncompressed
Data S2
connection
64 kbit/s time slot

with a D channel
D
and 
Voice D
3 compressed
connections
D Kanal 1 2 3 64 kbit/s time slot
D
4 5 6 7 with 4 compressed
connections
8 9 10 11 Stand-
leitung
64 kbit/s time slot
12 13 14 15 with 1 compressed
1 connection
VCM Switching Network
DIU-S2 emulation
...
with 15 connections
15
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
General
58.1.4.1 Figures of Symmetric Voice Compression

Configuration
S2 Link
Node A Node B
VCM (Master) DIU-S2 (Master) DIU-S2 (Slave) VCM (Slave)

D-Kanal D-Kanal
B-Kanäle
1 1
1 NC NC
B-Kanäle
2
1 1 1
2
3 3
2 2
4 4
NC NC
5 5
2 3 3 2
6 6
7 7
VCSU
VCSU
4
S2-Verbindung
8 4 8
9 NC NC 9
10 10
Partner B-Kanäle
11 3 3
Partner B-Kanäle
11
12 NC NC 12
13 13
14 14
15 4 4 15
VCM (Master) 5 5 VCM (Slave)

NC NC
D-Kanal D-Kanal
B-Kanäle
1 6 1
1 6 1
B-Kanäle
2 2
3 7 3
7
4 4
NC NC
5 5
2 2
6 6
7 7
VCSU
VCSU
8 NC NC 8
9 9
10 10
11 3 3 11
12 12
13 13
14 14
15 4 4 15
Master
There are no restrictions to choose the Partner B-Channels.
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
General
S0 Link
Node A Node B
VCM STMD STMD VCM

D-Kanal CIRCUIT 6 CIRCUIT 6 D-Kanal
B-Kanäle
1 1
1 NC NC 1
B-Kanäle
2
1 1 2
S0-Verbindung
3 3
Partner B-Kanäle
4
Partner B-Kanäle
4
5 5
2 2
6 6
7 2 7
VCSU
VCSU
8 NC 2 NC 8
9 9
10 10
11 3 11
3
12 12
13 CIRCUIT 7 CIRCUIT 7 13
NC NC
14 14
15 1 1 15
Partner B-Kanäle
4 4
Partner B-Kanäle
S0-Verbindung
NC
Master NC Slave
2 2
Master Slave
There are no restrictions to choose the Partner B-Channels.
58.1.5 VCM Transit Overview

If the VCM transit function is activated the voice connection will stay compressed.
Each Signal Processor of a VCM B-Channel can be set seperatly to the transit
mode.
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
General
No TRANSIT
comp/decomp comp/decomp comp/decomp comp/decomp
VCM/S2 S2/VCM VCM/S2 S2/VCM

16KBit 64KBit 16KBit
Node A Node B Node C
Signal Processors synchron Signal Processors synchron
TRANSIT activated by Call Processing

comp/decomp Transit Transit comp/decomp

Signal Processors asynchron Signal Processors asynchron

new synchronisation
TRANSIT ok
comp/decomp Transit Transit comp/decomp

Signal Processors synchron again
58.1.6 Administration Overview

The following administration steps are needed for the feature Voice Compression:
• Memory Configuration
(AMO DIMSU)
• Costumer Feature List Configuration

(AMO FEASU)
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
Basic Administration
• VCM Boards Configuration

(AMO BCSU)
• Class of Trunk Configuration

(AMO COT)
• Trunk Group Configuration

(AMO BUEND)
• Trunk Configuration
(AMO TDCSU)
• Activation/Deactivation of Boards
(AMO BSSU)
• Activation/Deactivation of Circuits
(AMO DSSU)
• LCR Configuration
(AMO COSSU, AMO LDAT, AMO RICHT)
• Subscriber Configuration
(AMO SCSU, AMO SBCSU)
• Voice Compression Configuration

(AMO VOICO)
58.2 Basic Administration
58.2.1 Allocation of Needed Memory

The VCM trunks will be added to the system like S2 trunks. 
Therefore the value of PRI has to be calculated by the number of S2 trunks +
number of VCM trunks.
ADD-DIMSU:TYPE=BASIC,PRI=<?>;
For each occupied S0/S2 Partner B-channel a memory element has to be
allocated.
One VCM-B7 occupies up to 2 and one VCM-B15 occupies up to 4 Partner B-
channels.
ADD-DIMSU:TYPE=NETWORK,VOICO=<?>;
number of available speech value of parameter VOICO

Boards channels (occupied Partner B-channels)
1 * VCM-B7 7 2
1 * VCM-B15 15 4
7 * VCM-B15 105 28
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
58.2.2 Costumer Feature List

Call Processing only uses VC trunks if the feature is activated.
CHANGE-FEASU:TYPE=A,CM=VOICO;
58.2.3 VCM Board Configuration

VCM-B15
ADD-BCSU:MTYPE=PER,LTU=<?>,EBT=<?>,PARTNO="Q2235-X ";
VCM-B7
ADD-BCSU:MTYPE=PER,LTU=<?>,EBT=<?>,PARTNO="Q2235-X100";
58.2.4 Class of Trunk Configuration

• The following COT parameters have to be added to a COT for VC trunks:
– SPCM = compressed speech channel
– NLHT = no local hold tone, hold tone from remote system

When VCM transit is activated, there is a noise based on connection
setup / connection release during the toggling function.
If the COT parameter NLHT is set the connection will not be released.
CHANGE-COT:COTNO=<?>,COTREF=COTADD,COTPAR=SPCM&NLHT;
• It’s only possible to compress voice connections. Therefore all trunks where
the type of the connection (voice or data) is unknown or connected with an
multiplexer have to be marked with the following COT parameter:
– VCMN = voice compression not allowed

CHANGE-COT:COTNO=<?>,COTREF=COTADD,COTPAR=VCMN;
See also Section 58.3.2, “No Voice Compression for Particular Subscribers”,
on page 715
58.2.5 Trunk Group Configuration

The VCM trunks have to be combined in separate trunk groups.
ADD-BUEND:TGRP=<?>,NAME=<?>,NO=<?>,RSV=<?>,TRACENO=<?>;
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
58.2.6 Trunk Configuration

In normal circumstances, the parameters of the VC trunks are based on the
parameters of the partner trunk.
However there are some parameters which have to be different:
• COTNO: The VCM trunk requires a COT which contains the parameter SPCM.
All other trunks should not have this COT parameter.
• DEV: The VC trunk has to be added with the device type VCCONN (digital
tie trunk circuit with voice compression).
• TGRP: The VC trunks should be in own trunk groups.
• BCHAN: The VCM has, depending from board type, 7 or 15 B-channels.
• PROTVAR: The protocol variants CORNV33 or ECMA1 should be used prevered
because they support the new protocol element "Allowed
Compression/Decompression Cycles".
The two corresponding VCM trunks (Node A / Node B) have to be configured with
a MASTER/SLAVE relation (like S0/S2 trunks). This has to be controlled by the
loadware parameter.
Example of a S2/VCM Configuration:

The different/important parameter values are marked bold.
S2 Trunk:
ADD-TDCSU:OPT=NEW,PEN=1-2-49-0,COTNO=20,COPNO=0,DPLN=0,
ITR=0,COS=1,LCOSV=1,LCOSD=1,CCT=" ",DESTNO=0,
PROTVAR=CORNV33,SEGMENT=1,TCHARG=N,SUPPRESS=0,TRACOUNT=31,
SATCOUNT=MANY,NNO=604,ALARMNO=0,FIDX=1,CARRIER=1,
ZONE=EMPTY,FWDX=1,DEV=S2CONN,TGRP=98,SRCHMODE=ASC,
BCHAN=1&&30,BCNEG=Y,BCGR=1,INS=N,LWPAR=8;
VCM Trunk:
ZONE=EMPTY,FWDX=1,DEV=VCCONN,TGRP=99,SRCHMODE=ASC,
Example of a S0/VCM Configuration:

The different/important parameter values are marked bold.
S0-Trunk:
ZONE=EMPTY,FWDX=1,DEV=S0CONN,INS=Y,TGRP=100,SRCHMODE=ASC,
MASTER=Y,SMD=Y,CNTRNR=0,BCNEG=N;
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
VCM-Trunk:
ZONE=EMPTY,FWDX=1,DEV=VCCONN,TGRP=101,SRCHMODE=ASC,
58.2.7 Activation/Deactivation of Boards and Circuits

VCM board and circuit:
The VCM board and circuit can be switched like all other boards and circuits with
the AMOs BSSU and DSSU.
Partner board and circuit:

In case of pre-blocking of a S0/S2 board or S0/S2 circuit the AMOs BSSU and
DSSU check if B-channels are occupied by VC and if so the affected VCM boards
or circuits will be pre-blocked too.
During activation the occupation by VC will be also checked. If the determined
VCM boards or circuits are in a pre-blocked status, they will be activated too.
NOTE: After deactivation of a LTU the status “pre-blocked” of boards and circuits
is lost.
In this case the automatically pre-blocked VCM boards or circuits have to be
activated manually.
58.2.8 LCR Configuration

All VC trunks to a specific route are combined in one trunk group.
This VC trunk group will be used in a new route element which has been added
to the route.
In the following example all relevant parameters are marked bold:

ADD-LDAT:LROUTE=<?>,LSVC=VCE,LVAL=1,TGRP=<?>,
ODR=<?>,LAUTH=64,CARRIER=<?>,ZONE=<?>,LATTR=VOICO,MSO=<?>,VCC
YC=6;
• LSVC: A compressed route element has to be created with the LCR service
voice.
• LAUTH: With a particular LCR authorization it’s possible to exclude some
subscribers from VC.
(i.e. necessary in case of analog fax devices)
• LATTR: The LCR route element should be marked by the LCR attribute VOICO to
have the option for a selected query.
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
• VCCYC: The value of this parameter limits the number of compression/

decompression cycles, because too much compression/decompression
cycles decrease the quality of speech. The deterioration of voice quality
is marginal with up to 8 cycles of compression/decompression.
Multiple compression/decompression cycles are the result of not available
VOICO routes in a network during the connection setup.
58.2.9 Voice Compression Configuration

The Nailed Connection between a VCM and a Partner board will be added with:
ADD-VOICO:PEN1=<vcm-pen>,VCSU=<?>,
PEN2=<partner line>,BCHAN=<partner bchan>,INS=Y/N;
Meaning of the parameter INS:
• INS=Y:
After adding a NC it will be activated immediately. Therefore the circuits of
VCM and Partner board have to be already locked.
• INS=N:
In this case the NC will not be activated and the VCM B-channels remains
locked. The Partner B-channel will not be occupied and stays as a normal S0/
S2 B-channel.
The VCM B-channels have be activated later with ACTIVATE-VOICO.

See detailed description in Section 58.2.10, “Deactivation/Activation of Voice
Compression”, on page 711.
NOTE: A symmetric configuration of the NCs at both nodes is necessary.

See figure in Section 58.1.4.1, “Figures of Symmetric Voice Compression Config-
uration”, on page 704.
58.2.10 Deactivation/Activation of Voice

Compression
In case of VC activated, one VCM-B15 offers 15 B-channels (only voice) and
occupies 4 B-channels (data & voice).
Therefore the capacity of B-channels for data transfer will decrease.
With the function “deactivation/activation of VC” the relation of

voice channels to data/voice channels can be adapted when required.
It’s possible to switch each VCSU seperatly.
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
Activated VCSUs S2 VCM required VCMs

(occupied B-channels B-channels
Partner (data & voice) (only voice)
B-channels)
30 0 112 7 VCM-B15, 1 VCM-B7
29 1 108 7 VCM-B15, 1 VCM-B7
28 2 105 7 VCM-B15
27 3 101 7 VCM-B15
26 4 97 7 VCM-B15
25 5 93 7 VCM-B15
24 6 90 6 VCM-B15
20 10 75 5 VCM-B15
16 14 60 4 VCM-B15
12 18 45 3 VCM-B15
8 22 30 2 VCM-B15
4 26 15 1 VCM-B15
3 27 11 1 VCM-B15
2 28 7 1 VCM-B15
1 29 3 1 VCM-B15
0 30 0 none
The deactivation/activation of VC requires deactivated circuits of VCM- and its

Partner board.
See detailed description in Section 58.2.7, “Activation/Deactivation of Boards and
Circuits”, on page 710.
Deactivate Voice Compression:

DEACTIVATE-DSSU:OFFTYPE=DC,TYPE=PEN,PEN1=<partner line>;
DEACTIVATE-VOICO:PEN1=<vcm line>[,VCSU=<?>];
ACTIVATE-DSSU:ONTYPE=ANL,TYPE=PEN,PEN1=<partner line>;
The NCs to all or oneVCSU of a VCM will be deactivated.
Afterwards the Partner B-channels are available again as normal S0/S2 B-
channel (data&voice); the VCM B-channels (only for voice) remain blocked.
Activate Voice Compression:

DEACTIVATE-DSSU:OFFTYPE=DC,TYPE=PEN,PEN1=<partner-circuit>;
ACTIVATE-VOICO:PEN1=<vcm-circuit>[,VCSU=<?>];
ACTIVATE-DSSU:ONTYPE=ANL,TYPE=PEN,PEN1=<partner-circuit>;
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
Extended Administration
The NCs to all or oneVCSU of a VCM will be activated.

Afterwards the affected Partner B-channels (data & voice) remain blocked; the
VCM B-channels (only for voice) are ready again.
NOTE: The NCs at both nodes have to be switched symmetric.

See figure in Section 58.1.4.1, “Figures of Symmetric Voice Compression Config-
uration”, on page 704.
58.3 Extended Administration
58.3.1 Mixed Routes (compressed/not compressed)

The following example shows a OpenScape 4000 network with 3 nodes,
connected with a S2 link.
The S2 B-channels are partial used by Voice Compression for voice connections
only. The other S2 B-channels will be used for data and analog FAX/MODEM
connections. If no more compressed B-channels are available, the
uncompressed B-channels can be used for voice too.
Node 100 200 100 Node 200

VC/S2 11
21
202 102
22 12
S2
31 32 32 31
302 S2 S2 302 300

300
102 202 VC/S2

VC/S2 Node 300
12 22
100 200
11 21
EXTERNAL
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
From Node 100 to 200:

ADD-
RICHT:MODE=CD,CD=00200,LRTE=200,SVC=VCE,TGRP1=21&22,CPS=0,DES
TNO=21;
ADD-RICHT:MODE=CD,CD=00200,SVC=DTE,TGRP1=22,CPS=0;
ADD-
LDAT:LROUTE=200,LSVC=VCE,LVAL=1,ODR=1,LAUTH=8,TGRP=21,LATTR=V
OICO;
ADD-LDAT:LROUTE=200,LSVC=VCE,LVAL=2,ODR=1,LAUTH=1,TGRP=22;
ADD-LDAT:LROUTE=200,LSVC=DTE,LVAL=1,ODR=1,LAUTH=1,TGRP=22;

ADD-
TNO=31;
ADD-
OICO;

ADD-
TNO=21;
ADD-
OICO;

ADD-
TNO=31;
ADD-
OICO;

ADD-
TNO=11;
ADD-
OICO;
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression

ADD-
TNO=21;
ADD-
OICO;
58.3.2 No Voice Compression for Particular

Subscribers
For certain connections (i.e. analog fax, modem, phones with voice decrypting
(privacy module)) call processing cannot identify them as data connections where
Voice Compression isn’t possible.
Therefore these connections have to be excluded from Voice Compression by
administration.
For connections established by an internal station, Voice Compression is

prevented by LCR control mechanisms.
Incoming external connections to these stations can be prevented by an entry in

the digit analysis.
58.3.2.1 Connections from Intern to Intern/External
In the following examples the LCR authorization 8 will be used to include/exclude

a particular subscriber from Voice Compression.
1. LCR Class of Service (LCOSS):

The LCOSV 1 with the LCR authorization 8 will be used for all subscribers
allowed to use Voice Compression.
CHANGE-COSSU:TYPE=LCOSV,LCOSV=1,ALCR=1&&8,DLCR=9&&64;
The LCOSV2 without the LCR authorization 8 will be used for all subscribers
which have to be excluded from Voice Compression.
CHANGE-COSSU:TYPE=LCOSV,LCOSV=2,ALCR=1&&7,DLCR=8&&64;
2. LCR Route Elements:
For that example there are two trunk groups for LCR route 200.
The Voice Compression trunk group 21 requires the LCR authorization
(LAUTH) 8. Therefore it can be used only from subscribers with LCOSV 1.
In case of trunk group overflow these subscribers can use the trunk group 22
with S2 B channels, too, as LCOSV1 contains the LAUTH8.
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
The subscribers with the LCOSV 2 can only be routed via trunk group 98 due
to the missing LCR authorization 8.
LATTR=VOICO;
3. Subscriber Configuration:
The subscriber 2220 should use VC and therefore gets the LCOSV1.
ADD-SCSU:STNO=2220,PEN=1-2-109-0,DVCFIG=ANATE,DPLN=0,ITR=7,
COS1=2,COS2=4,LCOSV1=1,LCOSV2=1,LCOSD1=1,LCOSD2=1,COSX=0,SPDI
=10,
COFIDX=0,DIAL=DTMF,INS=YES,ACKST=CHR,SSTNO=NO;
The subscriber 2221 has to be excluded from VC and therefore gets the
LCOSV 2.
ADD-SCSU:STNO=2221,PEN=1-2-109-1,DVCFIG=ANATE,DPLN=0,ITR=7,
COS1=2,COS2=4,LCOSV1=2,LCOSV2=2,LCOSD1=1,LCOSD2=1,COSX=0,SPDI
=10,
COFIDX=0,DIAL=DP,INS=YES,ACKST=CHR,SSTNO=NO;
58.3.2.2 Connections from External to Intern
An external incoming analog FAX or MODEM connection has to be routed without

VC. Therefore, all internal fax and modem numbers must be listed in the WABE
with a destination number which leads to a route without VC.
Based on the example of a route configuration in Section 58.3.1, “Mixed Routes

(compressed/not compressed)”, on page 713, additional new routes must be
defined.

ADD-
RICHT:MODE=CD,CD=00202,LRTE=202,SVC=ALL,TGRP1=22,CPS=0,DESTNO
=22;
ADD-LDAT:LROUTE=202,LSVC=ALL,LVAL=1,ODR=1,LAUTH=1,TGRP=22;

ADD-
=32;

ADD-
=12;
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression

ADD-
=32;

ADD-
=12;

ADD-
=22;
In the dialing plan of each node the new destination numbers have to be set for
all FAX and MODEM subscriber numbers.
Node Destination number for FAX/ Destination number for the other
MODEM subscriber numbers
100 12 11
200 22 21
300 32 31
Example:
The FAX subscriber 10123 of node 100 requires the following changes of the
dialing plan in nodes 200 and 300:
CHANGE-WABE:CD=10123,DESTNO=12;
There is also the possibility to exclude all incoming connections of an external
bundle from voice compression using a special COT parameter. See also Section
58.2.4, “Class of Trunk Configuration”, on page 708.
In this case WABE modification is not necessary.
58.3.3 More Data Channels or More Speech Channels

If there is the necessity for an increase of data channels, i.e. during the night, the
number of B channels to be additionally used for data connections can be
increased by directed deactivation of Voice Compression subunits.
If more B-channels for voice are needed, the deactivated Voice Compression
NCs have to be switched on again.
For a detailed description see Section 58.2.10, “Deactivation/Activation of Voice

Compression”, on page 711.
At present, there is no external application which supports this functionality.
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
Error Messages
58.3.4 Route Optimization

There is the possibility to prevent Route Optimization in case of Voice
Compression.
Till today there are no reasons to use it.
CHANGE-ZAND:TYPE=ALLDATA2,ROLCKVCM=YES;
58.4 Error Messages

The feature Voice Compression has requested 3 new error messages.
• F5993 CIRCIUT L2 ERROR VC

D-channel of Voice Compression not active. (Level-2-error)
• F5994 CIRCUIT B CHANNEL VC DEF

B-channel of Voice Compression not active.
• F5995 CIRCUIT B CHANNEL VC OK

B-channel of Voice Compression active again.
How to interpret the auxiliary data:
Byte 0 = 10 Error type (DB_M_QF_CIR_L2_ERR_SET)

D-channel error or B-channel changes
Byte 1, 2 = 0001 Number of reported errors = 01
Byte 3 = 02 Length of following data: 2 Bytes
Byte 4 = 1. Status byte: Bit 0 = D-channel
Bit 1-7 = B-channel 1-7
Byte 5 = 2. Status byte: Bit 8-15 = B-channel 8-15
If the channel is active the corresponding bit is set to 1. If the channel is defect or
not configured the corresponding bit is set to 0.
In case of the VCM-B7 (without B-channel 8-15) the second status byte is set
always to 00.
All error messages are described in the documentation OpenScape 4000/HiPath

4000, Troubleshooting (AlFe).
Examples of error messages:

The error messages are based on following configuration:
Both switches are connected with 2 S0 trunks which are linked to one VCM-B15.
The VCM D-channel and the VCM B-channels 1-7 (VCSU 1 + 2) occupies the
STMD trunk 0 and the VCM B-channels 8-15 (VCSU 3 + 4) occupies the STMD
trunk 1.
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
Error Messages
1. At the remote system the STMD trunk 0 has been switched off.
(VCM D-channel and B-channels 1-7 are affected)
F5414 M4 N5381 OUT SERV BPA CIRCUIT L2 ERROR
97-02-10 07:33:36
ALARM CLASS:SWU-PER:001
** :LTG1 :LTU2 :115: 0 : 0 Q2174-X STMD
BST:01 FW: C360-L
REASON:01H DEACTIVATED BY PEER
FORMAT:36

97-02-10 07:33:36
** :LTG1 :LTU2 :115: 0 : 0 Q2174-X STMD
BST:01 FW: C360-L
REASON:0BH TEI REMOVED
FORMAT:36
F5994 M4 N5383 OUT SERV BPA CIRCUIT B CHANNEL VC DEF

97-02-10 07:33:38
** :LTG1 :LTU1 :055: 0 : 0 Q2235-X VCM-B15
BST:01 PLS:-B3
FORMAT:22
1000010201FFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF

97-02-10 07:33:49
** :LTG1 :LTU1 :055: 0 : 0 Q2235-X VCM-B15
BST:01 PLS:-B3
REASON:05H PEER OUT OF ORDER
FORMAT:36
F5993 M4 N5385 OUT SERV BPA CIRCUIT L2 ERROR VC

97-02-10 07:33:49
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
Error Messages
** :LTG1 :LTU1 :055: 0 : 0 Q2235-X VCM-B15

BST:01 PLS:-B3
FORMAT:22
1000010200FFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF
2. At the remote system the STMD trunk 0 has been activated again.
F5418 M4 N5389 IN SERV BPA CIRCUIT LX ACTIVE
97-02-10 07:35:16
** :LTG1 :LTU2 :115: 0 : 2 Q2174-X STMD
BST:01 FW: C360-L
REASON:09H LAYER 3 ACTIVE
FORMAT:36

97-02-10 07:35:16
** :LTG1 :LTU1 :055: 0 :15 Q2235-X VCM-B15
BST:01 PLS:-B3
FORMAT:36
3. At the remote system the STMD trunk 1 has been deactivated.

(VCM B-channels 8-15 are affected)
97-02-10 07:38:31
** :LTG1 :LTU2 :115: 1 : 0 Q2174-X STMD
BST:01 FW: C360-L
REASON:01H DEACTIVATED BY PEER
FORMAT:36

97-02-10 07:38:31
** :LTG1 :LTU2 :115: 1 : 0 Q2174-X STMD
BST:01 FW: C360-L
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
Error Messages

FORMAT:36

97-02-10 07:38:31
** :LTG1 :LTU2 :115: 1 : 0 Q2174-X STMD
BST:01 FW: C360-L
FORMAT:36

97-02-10 07:38:33
** :LTG1 :LTU2 :115: 1 : 0 Q2174-X STMD
BST:01 FW: C360-L
REASON:04H NO SIGNAL (LOCAL ALARM)
FORMAT:36

97-02-10 07:38:33
** :LTG1 :LTU1 :055: 0 : 0 Q2235-X VCM-B15
BST:01 PLS:-B3
FORMAT:22
10000102FF00FFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF
4. At the remote system the STMD trunk 1 has been switched on again.
97-02-10 07:40:13
** :LTG1 :LTU2 :115: 1 : 2 Q2174-X STMD
BST:01 FW: C360-L
FORMAT:36
A31003-H3170-S103-6-7620, 02/2019
vcmanw_en.fm
Voice Compression
Error Messages
F5995 M4 N5400 IN SERV BPA CIRCUIT B CHANNEL VC OK

97-02-10 07:40:13
** :LTG1 :LTU1 :055: 0 : 0 Q2235-X VCM-B15
BST:01 PLS:-B3
FORMAT:22
10000102FFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF
5. The VCM board at the remote system has been activated,

but STMD trunk 1 (VCM B-channels 8-15) is out of service.
97-02-10 07:46:19
** :LTG1 :LTU1 :055: 0 :15 Q2235-X VCM-B15
BST:01 PLS:-B3
FORMAT:36

97-02-10 07:46:19
** :LTG1 :LTU1 :055: 0 : 0 Q2235-X VCM-B15
BST:01 PLS:-B3
FORMAT:22
10000102FF00FFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF
A31003-H3170-S103-6-7620, 02/2019
cdr_basics_grundlg1.fm
INCDR (Internal and network-wide call detail recording) - Basic Information
INCDR (Internal and network-wide call detail recording) -

Basic Information
59 Call Detail Recording

Call detail recording (INCDR = internal and network-wide call detail
recording) is responsible for recording, outputting, and processing charge and
call data for the purpose of determining costs and billing them for certain
communication services. This refers to outgoing (trunk, tie) and incoming external
connections as well as to internal connections. CDR (Call Data Recording)
performs charge calculation for external connections without charging
information from the line or for internal connections. This charge calculation uses
a cost parameter (CARRIER and ZONE). The costs here are determined by
amount or time unit. This parameter is determined by call processing; it is always
passed when CDR is started (ZONE=EMPTY means there are no charges).
IMPORTANT: Call detail recording functions are only possible via LCR (Least
Cost Routing), which means that all routes must be set up over the LCR AMOs
(AMO WABE, AMO RICHT, AMO LODR, AMO LDAT, and AMO LDPLN).
The call processing determines the cost parameter in the following cases:
– for outgoing traffic by using LCR route information
– for incoming traffic by reading the cost parameter from the

static station line memory
– for internal traffic, depending on the ITR group.
With each initial start of the CDR, a call ID (node number + consecutive number),
which is determined by the call processing, is assigned. This call ID is used for
the internal or network-wide identification of call detail records.
The CDR information that the CDR function uses when computing the costs can
be displayed on terminal devices with display. This display is updated in the
following cases:
– each time call detail information arrives from a line
– on expiration of a central timer in CP (Call Processing) during charge

computing.
A31003-H3170-S103-6-7620, 02/2019
General Information
There is a feature function block "Cost UNIT Identification" (COSTI), which can
be started from all equipment (voice and non-voice terminal devices, trunks) over
a program interface, so the new requirements do not have to be implemented on
all OpenScape 4000 equipment. This function block handles the interface
between the CDR function and the display of the charges (see the following figure
"Interface Call Processing - Call Detail Recording").
Tasks of the function block:
• Uniform program interface for all calling equipment
• Storage of call processing data for call detail recording
• Handling of the interfaces to the CDR
• Reporting the charges for display on terminal devices (non-device-specific)
– Creating the totals for displays for multiple call charge records
– Timer-controlled when computing costs
– When call detail information arrives from the lines
• The size of the memory in COSTI is the same as the size of the memory in
the CP buffer. Therefore there should be no blocking.
• After a soft restart, no more data is displayed for existing internal connections.
A31003-H3170-S103-6-7620, 02/2019
General Information
SWU
Call Processing DPS for call detail recording
Configuraton
requesting
call detail
recording
Cost Unit Identification
DATCOL
COSTI
Program
interface
Program
interface
Message *
interface CDRD
(display of call
details on the Charge calculation
telephone
station)
Saving and forwarding the

*for linking two chargeable call details: CDBMAN
Cost connections such as
unit
conference or consultation hold
Terminal device
Output call details:

Call detail recording
DATSEL, OUTPUT
ISP on the server side
e.g., call charge computer,

Call detail recording
Figure 82 Interface between Call Processing and Call Detail Recording
A31003-H3170-S103-6-7620, 02/2019
Call Detail Recording Features
59.2 Call Detail Recording Features

• Individual display on terminal device (AOC)
– Display on a voice terminal device of the total of the current call charges
for the call charge amounts of each connection. The counting starts with
the 1st counting pulse; the display is switched off after a configurable time
(default is 5 s).
– CDRD for voice, fax, data.
• Charge display for each connection on attendant console (CDRA)
– Display of the call charges and call data on the attendant console screen.
– Call charge display on console is done only when there is CDRA class of
service.
– When the call ends, the charge data or call data of the station that has the
GEP class of service is logged on the attendant console. When there are
queries, the internal or external station number, the units or the amount is
displayed.
– Plain-text output to a printer is possible.
– CDRA is possible for voice, fax, and data.
• Call charge display at the night answering position
– CDRD at the night station and connection of a printer are possible.
• Immediate output of call charges to external data medium (CDRC)
– The output device can be a printer, the hard disk, the operating terminal,
the data channel (DPS), or a call charge computer (CCU/GC3001A, see
separate service handbook).
– A selected and formatted call detail unit record is output.
• Call charge output by call-up on auxiliary devices (CDRC)
– Output of the call detail data without analysis on auxiliary devices and
DPS (CDRC with call-up). Call detail data analysis on the call charge
computer (CCU/GC3001A).
• Call charge output to FT file
• Call detail recording and calculation for internal traffic
• Call detail recording and charge calculation for incoming trunk calls and inter-
PBX traffic
• Call detail recording and charge calculation for outgoing inter-PBX traffic
(networking)
A31003-H3170-S103-6-7620, 02/2019
Call Detail Recording Overload Behavior
• Call detail recording and charge calculation for Euro-ISDN trunk
• Charge calculation of the call charges on Digite display
• LCR expensive warning
59.3 Call Detail Recording Overload Behavior

The call detail data is temporarily stored in a call detail data pool on the SWU so
that there is no loss of call detail data if there is an ISp outage or outage of an
output device. The size of the memory depends on the system type. The ECX is
designed for the temporary storage of a maximum of 3800 CDR records. Every
other type of system is designed for the temporary storage of a maximum of 2200
CDR records.
When the limits of this memory capacity are reached, no more call detail data can
be temporarily stored and call detail data is lost. Therefore, to minimize the loss
of call detail data for outgoing trunk calls (expensive connections), the internal
connections are no longer recorded once the call detail data pool has been filled
to 75% of its capacity. Before this point is reached, appropriate error messages
(alarm messages) are sent.
59.4 Relevant AMOs for Call Detail Recording
AMO Parameter Lang Description

.
COSSU Classes of service
CDPRINT E Internal call detail recording
CDRA E Call detail recording, attendant (ATND)
CDRSTN E Immediate display of call charges on telephone
CDRS E Individual call detail recording for the station
CDRC E Central call detail recording for the station
PUPHON *) E Public telephone
SCRNCA *) E Station A without charges (creates a data record
without charges)
SCRNCB *) E Station B without charges (creates a data record
without charges)
SCRSPC *) E Station with special call detail recording (used in
special cases)
MTEQ *) E Maintenance device (used in special cases)
Table 21 AMOS for Call Detail Recording - Description of the Parameters
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs for Call Detail Recording

.
COT Class of trunk
CDBO E Call detail recording for breakout to carrier
network
IICB E Ignore incoming charges
The cost unit and the TRANSWB bit (AMO
LDAT) received from the billing element are not
used.
CDRI E Call detail recording for incoming connections
SNBE E Do not send billing elements (cost unit is the
station number plus node number)
CATR E Transmit call charges transit
AOCC E Call charge data transmission by connection;
must always be set for CORNET-NQ and QSIG.
CDRD E If this parameter is set, the transmitted class of
service for the line is not used for the call charge
data transmission; instead the permanently set
class of service in the circuit’s COS is used. With
carriers, this controls whether the service AOC
(Advice of Charge) is released for the customer.
The parameter has nothing to do with the call
detail recording for the terminal device.
IGID E Ignore the call ID (for example, for call detail
recording) for incoming connections. The
received call ID is ignored and a new one is
assigned (for example, to the carrier’s network
boundary).
ICZL E Incoming call detail recording over zone or line.
For call detail recording in incoming traffic, the
calculation of the call charges is performed
according to zone tables (tariff tables) or
according to incoming charge information
(messages) from the line.
The ICZL and ICZO parameters are mutually
exclusive.
ICZO E Activate incoming call detail recording by circuit.
The ICZL and ICZO parameters are mutually
exclusive.
NCDR E Suppress signaling of CDR-E-specific
messages.
NCHD E No call charge messages during the call.
NCHG E ATND without charges.
The subscriber is not charged for a call to the
ATND (MFC). AMO FEASU parameter
NOCHRG feature must be set.
A31003-H3170-S103-6-7620, 02/2019

.
DPRE E If the parameter is set, the dialing that was
actually sent out (for example, including prefix
digits, AMO LODR, OUTPULSE) is passed
along to the call detail recording function.
CTIME Call processing timers

DISPCH E Time interval for updating the call charge display
with CDRD (INCRD feature). The timer for the
periodic call charge display. Update of the call
charge display at stations at selected time
interval. The selected value is only a guideline
that can also be exceeded when the SWU is fully
occupied because of high priority processes.
Note: If the parameter is too low, the processor
load will be very high. If the parameter is too
high, there will be jumps in the call charges.
CDRDISDE E Clear call charge display for CDRD (call charge
display on the display of the digital voice
terminal). The time controls the continuation of
the display after the idle state occurs on the
Digite.
PREEMT E Preemption: higher-level switching time for
clearing outgoing connections if no one answers
during a recall (because of call charge pulses)
DAGR Administration of CDR file parameters
DAVF Display properties when outputting call charges

to the attendant console
DEFPP Define paying party (cost unit)

DEFTM Define traffic measurement
DIMSU Feature quantities

COSTI E Size of dynamically allocated connection
memory for connections with call detail
recording. 
Note on dimensioning: COSTI = CPB. Then the
charges can be recorded on all outgoing trunk
calls and tie trunks. If you want to record
incoming connections and internal calls as well,
you must increase the value.
CPDBUF E Size of the dynamically allocated CP data
buffers.
A31003-H3170-S103-6-7620, 02/2019

.
FBTN Administration of the flag byte table and the line

number table
FEACG Call detail recording features (bit string)
FEASU Central features

CDRE E Call data recording
enhancements
This allows for detailed output of the CDR
records.
NOCHRG E Free of charges (applies to incoming MFC-R21,
for example, feature Switzerland for free fault
services)
CDROGTR E Record call charges for outgoing trunk calls.
Call detail recording for outbound connections
(trunk calls and tie trunk traffic) is always set
using Least Cost Routing (LCR) parameters.
The VOICE/FAX/ DATA services are normally
treated in the same way as far as the call
charges are concerned. Because LCR is
configured according to service, each service
can be allocated a different cost parameter.
CDROGNW E Record call charges for outgoing network-wide
traffic (tie trunk traffic); see also parameter
CDROGTR.
CDRINH E Record call charges for internal traffic.
For internal connections in nodes, you allocate
the cost parameters to the internal traffic
restriction groups (ITR groups). Use AMO
VBZGR to allocate the cost parameter ZONE
(INT01 to INT09, EMPTY) to the ITR groups,
using the chargeable station’s cost parameter of
the ITR group for the call detail recording. Use
AMO TTBL to configure the ZONE itself.
CDRIC E Record call charges for incoming network and
trunk calls.
CDRA E Call detail recording at the station (not analyzed)
DISCHTR E Display call charges for incoming and outgoing
trunk calls on the station display
DISCHINH E Display call charges for internal traffic on the
station display
DISCHNW E Display call charges for incoming and outgoing
network-wide traffic on the station display
A31003-H3170-S103-6-7620, 02/2019

.
CPS E Transmission and measurement of call charge
pulses (on the SLMAR card) 
The SLMAR card provides 8 analog ports for all
basic features that are offered on analog lines,
as well as three features (loop extension, CDR
pulse transmission, and line test) for a few
special countries.
FETA Administration of tables of public and national

holidays
FTBL Administration of output format tables
GEFE Administration of CDR parameters
GETAB Retrieval of the CDRS file on auxiliary devices
GETPD CM deletion of CDRS files
GEZAB Call charge data display on auxiliary devices
GEZU Administration of device allocation tables
GRZW Administration of the connection limits table
KNMAT Administer node data for networking
KNPRE Administer node prefix table
LDAT Administration of LCR destinations

CARRIER E Carrier; must always be entered together with
the ZONE parameter
LATTR E LCR attributes
ZONE E LCR zone; must always be entered together
with the NETZBETR parameter
RCUT Administration of the route code conversion

table
A31003-H3170-S103-6-7620, 02/2019

.
SELG Administration of selection groups and selection
tables
SELL Administer the station and destination number

lists
SELS Switching the selection groups

TABT Administration of rate period tables
TACSU Configure analog trunk circuits

CARRIER E Carrier (for cost computation)
When calculating costs for incoming
connections, the trunk circuits can be allocated
cost parameters that are made up of CARRIER
and ZONE. CARRIER and ZONE, which always
work in combination, must be parameterized
with AMO TTBL.
COS E Class of service
COTNO E Class of trunk
CDRINT E Limiting value for call charge pulse integration.
This value indicates the number of call charge
pulses that are picked up in the device handler
before they are passed to the call detail
recording function.
NNO E Node number (fictitious node number or node
number of the destination system).
The node number identifies the partner node.
You can omit leading zeros. Zeros at the end
indicate any node in an area.
MFCVAR E Type of MFC
This parameter allocates the MFC type to the
circuit.
ITR E Internal traffic restriction group
ZONE E Distance zone for call charges based on time.
When calculating costs for incoming
connections, the line circuits can be allocated
cost parameters that are made up of CARRIER
and ZONE. You must use AMO TTBL to
parameterize CARRIER and ZONE, which
always work in combination. The empty zone,
for which no charges are incurred according to
time, is assigned by default.
TDCSU Configure digital trunk circuits

A31003-H3170-S103-6-7620, 02/2019

.
CARRIER E Carrier (for cost computation)
See above for a detailed description (AMO
TACSU parameter CARRIER).
COS E Class of service
COTNO E Class of Trunk
NNO E Node number (fictitious node number or node
number of the partner system).
TACSU parameter NNO).
ITR E Internal traffic restriction group
ZONE E Distance zone for call charges based on time.
TACSU parameter ZONE).
TEXT Administration of CDR text output tables
TLZO Administration of the station allocation table
TTBL Administration of the tariff tables
VBZGR Allocation of the respective destinations (zones

for call detail recording) to the internal traffic
restriction groups
TYPE E Branch parameters: CHRGINT (call detail
recording for internal calls) and CHRGINC (call
detail recording for incoming calls)
ZONE E Zone allocation for call detail recording for
internal and incoming calls
ZAND Administration of central system data

TYPE=CCD Log Settings for call charge display on the terminal
dialo device and attendant console
g
fields

Classes of service marked with *) are only to be released for specific countries for
the feature public exchange telephone with call charge pulses.
A31003-H3170-S103-6-7620, 02/2019
Cross-References between AMOs and the AMO SELG
59.5 Cross-References between AMOs and the AMO SELG
LCSM FETA
Line settings Public and national
holiday tables
ATCSM TABT
Interface parameters Rate period tables
and allocation
GEZU DAGR TTBL PERSI

Device allocation File size of the  Tariff tables with call Personal data
for the output CDRC and FT charge information
and zones 
files
SELG LDAT
FTBL LCR guidelines
Selection groups
Format tables 
BASDEV TAR LATTR=INTCHARG
RESDEV ZONE
ZAND COPIN LATTR=WCHREG
Central system FORMBAS LATTR=TRANORG
data FORMRES LATTR=NOCHDIS
CARRIER
 P
TYPE=ALLDATA, CARRIER
LEVEL0 .. 2
TYPE=CCD STNTAB1, 
STNTAB2
RTECD
DNOTBL1,
RCUT ATNDGR DNOTBL2 TDCSU
Trunk group  TACSU
codes Trunk circuits
SELS
Deactivate or  SELL
ATNDGR
activate the Station number
ATND groups
selection and destination
number tables
Figure 83 AMOs for Call Detail Recording - cross-references to AMO SELG
A31003-H3170-S103-6-7620, 02/2019
Types of Call Detail Recording
59.6 Types of Call Detail Recording
59.6.1 Internal Traffic

For internal traffic, call detail recording and charge calculation are possible for the
following features: base call, consultation hold, transfer/pickup, three party
conference, toggle, call pick-up, forwarding/call forwarding - no answer, executive
intrusion, and callback.
59.6.1.1 Voice
Connections to special equipment (such as dictation equipment, paging

equipment, etc.) are also recorded. Feature activations are not recorded if no
voice transfer results (such as call waiting).
Connections with the attendant console (ATND) are only registered if the ATND
is on the called side.
Voice: Call detail recording

according to time and zones
A-party B-party
OpenScape
4000
A-party: B-party:
all anate, all anate,
all Digite, including Euro-ISDN all Digite, including Euro-ISDN
phones, phones,
transmission of VMS/PM attendant console,
VMS/PM, special facility.
Figure 84 Configuration for internal traffic
Configuring system features

AMO FEASU
• CDRINH Record call charges for internal traffic.

• DISCHINH Display call charges for internal traffic on the station display
• CDRA Call detail recording at station (ATND)
Configure station-specific features

AMO COSSU
• CDPRINT Recording for the station with the COS no. ...
A31003-H3170-S103-6-7620, 02/2019
• CDRSTN Immediate display of call charges on the terminal device

• CDRA Call detail recording at attendant (ATND)
Configuring zone values

AMO VBZGR
• TYPE Branch parameter for call detail recording for incoming calls (CHRGINT)
• ZONE Zone allocation for call detail recording for internal calls (INT01-INT09)
Configure tariff tables

AMO TTBL
• Configure tariff group table

TAB=GRP: GROUPNO, CARRIER (=0), CATPTY, SERVICE, TARTBLNO
• Configure tariff table without call charge information

TAB=WOCU: TARTBLNO, ZONE (=INT01-INT09), INTDAY, TARDAY,
INTNT1-INTNT4, NTAR1-NTAR4, TARBAS, TARMIN, SEGTBLNO, CHPER
Configure timers
AMO CTIME
• DISPCH Update period of the station call charge display, in seconds

• CDRDISDE Duration of the call charge display after end of call (in seconds)
59.6.1.2 Non-Voice
Fax connections are recorded in the call detail recording for internal traffic under
the "Fax" service and data connections are recorded under the "Data" service.
The type of the service ("fax" or "data") is registered in the call detail record.
Under the "data" service, no subdivision is done according to data transmission

speed or according to special data service type, such as X.21 or synchronous/
asynchronous.
Internal calls of the following device types are recorded for non-voice calls:
• Euro-ISDN (S0 and S2)
• DCI and DCI-compatible devices
• Modem at an SLMA interface and on the a- and b-interfaces of an S0 terminal

adapter (Euro-ISDN).
A31003-H3170-S103-6-7620, 02/2019
59.6.2 Incoming Trunk Calls and Tie Trunk Traffic

You can configure the call detail recording for all types of analog and digital lines.
For the charge calculation, a cost parameter is used that you can configure for
each trunk using the administration. The system specifies the clock.
During an incoming Euro-ISDN call, any charges announced with AOC-S (Advice
of Charge (Setup) = charge notification at the start of the connection), AOC-D
(charge notification during the connection), or AOC-E (charge notification at the
end of the connection) are used for charge calculation in the call detail recording.
During an incoming analog call with call charge units, a CDR record can be
recorded if needed. However, this does not result in any cost billing (collect call).
Information may be missing in the CDR records if this information is not
transmitted by the remote analog station.
A-party:
incoming circuit
group B-party:
OpenScape
Voice
4000
Fax
Data
CDR
(Call Detail Recording)
Call detail recording according to time and zones and
by the transmission of call charge information
Figure 85 Configuration for incoming tie trunk traffic
Configuring System Features

AMO FEASU
• CDRIC Record call charges for incoming network and trunk calls.
• GESPAM Display call charges for incoming trunk calls on the station display
• DISCHNW Display call charges for incoming network-wide traffic on the station
display
AMO COT
• ICZL Incoming CDR over zone or line

• ICZO Activate incoming call detail recording by circuit
• TRSC The line sends charge amounts to the originating node (valid for INCDR.
If TRSC is not set, units are reported to the originating node so that the value
UNIT is set there as the system date with AMO ZAND, TYPE=CCD,
parameter CDDISPEX.
A31003-H3170-S103-6-7620, 02/2019
AMO TACSU / AMO TDCSU
• CARRIER Carrier (for cost computation) (1 - 9)

When calculating costs for incoming connections, the trunk circuits can
be allocated cost parameters that are made up of CARRIER and
ZONE. CARRIER and ZONE, which always work in combination, must
be parameterized with AMO TTBL.
• ZONE Distance zone for call charges based on time (EMPTY, INC01 - INC09)
When calculating costs for incoming connections, the line circuits can
be allocated cost parameters that are made up of CARRIER and
ZONE. CARRIER and ZONE, which always work in combination, must
be parameterized with AMO TTBL. The empty zone, for which no
charges are incurred according to time, is assigned by default.
AMO TTBL
• WOCU
Tariff tables 1 - 25 without charge information (ZONE=INC01 - INC09)
• WCU
Tariff tables 1 - 25 with charge information (pulse tariff 0, 23 ....)
59.6.3 Outgoing Tie Trunk Traffic (Networking)

Call detail recording is possible for all analog and digital line types in the services
"voice", "fax" and "data". It is performed on the basis of routing-dependent cost
parameters (LCR = Least Cost Routing).
You can configure the LCR cost parameter for each LCR route element. This LCR
cost parameter is used for OpenScape 4000 internal and external call charge
calculation as well as for the control of the Digite display.
The networking call detail recording is always started, regardless of the

connection type and regardless of the features used to make the connection. This
means that not only the standard features are taken into consideration, but also
all country-specific features.
A31003-H3170-S103-6-7620, 02/2019
B-party:
outgoing circuit
group
A-party: (networking)
Voice OpenScape
4000
Fax
Data
CDR
Call detail recording for networking including
all network features according to time and
zones
Figure 86 Configuration for outgoing tie trunk traffic
59.6.3.1 Configuring System Features for Outgoing Tie Trunks
AMO FEASU
• CDROGNW Record call charges for outgoing network-wide traffic (tie trunk traffic:
also see CDROGTR)
• DISCHNW Display call charges for outgoing network-wide traffic on the station
display
AMO LDAT
• see Section 59.6.3.2, “Configuring System Features for Outgoing CO”
AMO COT
• see Section 59.6.3.2, “Configuring System Features for Outgoing CO”
59.6.3.2 Configuring System Features for Outgoing CO
AMO FEASU
• CDROGTR Record call charges for outgoing trunk calls

Call detail recording for outgoing connections (trunk calls and tie trunk
traffic) is always set using Least Cost Routing (LCR) parameters. The
voice/fax/data services are normally treated in the same way as far as
the call charges are concerned. Because LCR is configured according
to service, each service can be allocated a different cost parameter.
• DISCHTR Display call charges for outgoing trunk calls on station display
AMO LDAT
A31003-H3170-S103-6-7620, 02/2019
CARRIER Carrier; must always be entered together with the ZONE parameter (1 - 9)
ZONE Values:
EMPTY, SHORT, LOCAL, LONG01 - LONG49, ABROAD01 - ABROAD99,
TIE01 - TIE09, INTERN01 - INTERN09
LATTR LCR attributes
Possible values:
WCHREG Activate call detail recording
EODSTCDR Call detail recording starting at the end of dialing
INTCHARG External charges like internal
NOTRANS Transit node without charges
NOCHDISP Suppress display in the case of expensive warning
AMO COT
• DPRE If the parameter is set, the dialing information that was actually transmitted
(including, for example, prefix digits, AMO LODR, OUTPULSE) is passed to
the call detail recording function (destination number with prefix digit to
DATCOL).
59.6.4 Call Detail Recording for Networking
LCR route selection
Acknowledgement of the
display information to the Call detail recording with the call
originating node charge information from the
LCR table
Figure 87 Call detail recording for networking
The following points have been implemented in call detail recording in

networking:
• Call detail recording with the help of route-dependent and routine-dependent

cost parameters (least cost routing parameters)
• You can configure the LCR cost parameter for each LCR route element.
A31003-H3170-S103-6-7620, 02/2019
• This LCR cost parameter is used for OpenScape 4000 internal and external
call charge calculation as well as for the control of the Digite display. The cost
parameter is not available for old routing.
• Transmission of the call charge information for a Digite display network-wide

to the A-party’s originating node
• The LCR AMOs determine when and where a call is recorded.
• Call detail recording and charging of networking connections are always done
in the node in which the lines or trunk to be recorded are allocated.
59.6.5 Network-Wide Call Detail Recording With Call

ID
Network-wide connections can be identified with the help of a call ID, which can
be stored in the call data records. This makes it possible to link together call data
records that stem from a connection’s different recording locations (measurement
at different path sections of a network-wide connection) at a later time for offline
analysis of the call data records and for computing the costs.
The call ID has two levels and has a thread ID and a global ID: the thread and
global IDs contain a three-level node number and a counter (sequence number).
The call ID is assigned during the first call processing operation.
The thread ID does not change throughout the entire connection (even network-
wide) and can therefore be consulted for a summary of all CDR records that
belong to a connection.
The global ID changes with each call step such as transfer, call forwarding, etc.
0-0-100-123456
Thread ID
OpenScape
OpenScape 4000 OpenScape
4000 4000
OpenScape
PNNO 0-0- 4000
PNNO 0- 200 PNNO 0-0-
0-100 400
PNNO 0-0-
300
CDR CDR
CDR record with thread ID 0- CDR record with thread ID
0-100-123456 Call detail recording 0-0-100-123456
Figure 88 Network-wide call detail recording with thread ID
A31003-H3170-S103-6-7620, 02/2019
Call Charge Display on the Digite
59.6.6 Euro ISDN Trunk

With the feature ’Euro-ISDN’, the charge message from the trunk at the beginning
of the connection (AOC Setup) is not only taken into account for the Digite display
but is also processed in the call detail recording for the OpenScape 4000 internal
charge calculation and in the external accounting management (call charge
computer).
Voice
Euro-ISDN
Fax
Public network
Data
Call detail information when setting up the connection

of a public network: "AOC-S (setup)"
Figure 89 Euro-ISDN trunk
The following types of recording have been implemented for the network-wide
transmission of a Euro-ISDN trunk’s charge information to the originating node of
the A-party for a Digite display
• AOC-S
Call detail information while setting up the connection or during the
connection
(for example, 20 s =1 unit or 30 s =0.20 EUR)
• AOC-D
Call detail information during the call (units or amount).
• AOC-E
Call detail information when the call ends (units or amount).
59.7 Call Charge Display on the Digite

The CDRSTN class of service (call charge display at the telephone station) is
needed to display the call charges at the station.
The call charge display is updated periodically. You can adjust the time interval
between updates throughout the system with the help of a configurable timer. The
call charges are displayed during the call and at the end of the call.
A31003-H3170-S103-6-7620, 02/2019
Call Charge Display on the Digite
The charge notification from OpenScape 4000 to the Euro-ISDN telephone

connection occurs during the call and at the end of the call, but not at the
beginning of the connection when it is being switched. The charge notification
occurs if the connection is made under the "Voice" service and if the Euro-ISDN
telephone connection’s station has been assigned the CDRSTN class of service.
If a Digite station has two chargeable connections (for example, during a

consultation hold), the display shows the total of the charges that apply,
regardless of the different types of costs (trunk call, inter-PBX traffic, or tie trunk
traffic).
Primary and secondary calls on Digites are handled as separate connections.

The respective charges are displayed separately. They are not added together.
This type of call occurs when one call is taken over from another call with the help
of call pickup, for example, after call waiting.
• Call charges for internal calls

The costs that result from the length of the call and the cost parameter are
shown on the Digite display during an internal call. This is configured for
internal connections for each ITR group of a system.
• Call charges for "incoming trunk and tie trunk"

The costs that result from the cost parameter are displayed. This cost
parameter is configured for each trunk by Administration (accounting of call
charges based on time).
IMPORTANT: However, this does not mean a general release of the Digite
call charge display for incoming connections for any given country-specific
analog lines.
• Call charges (CDRD) during a networking connection on the basis of

route-dependent cost parameters
– The costs that result from the length of the call and the cost parameter are
shown on the Digite display. This is configured for each selected routing
trunk group for LCR connections (cost parameter depending on LCR
route element).
– LCR expensive warning signaling helps prevent a false call charge

display on the Digite caused by an expensive route selection. This means
that the "normal" call charges are displayed for a "normal" route and that
the expensive warning signaling prevents the wrong call charge display
when an expensive route is selected to remote nodes (for example,
during break-out).
• Call charges (CDRD) during a connection over the Euro-ISDN trunk
A31003-H3170-S103-6-7620, 02/2019
Types of Charge Calculation
– The charge notification from the Euro-ISDN trunk to OpenScape 4000 to

the Euro-ISDN telephone connection occurs at the end of the call and
possibly during the call.
59.8 Types of Charge Calculation

The charge calculation has been adjusted to meet the new Euro-ISDN
requirements and the requirement for a calculation done without call charge units.
The following types of charge calculation are used:
• Charge calculation for internal traffic over internal zones (maximum of 9); the
zones can be allocated by ITR group. The cost parameter of the ITR group in
which the chargeable station is located always applies.
• Charge calculation with call charge units (price/call charge unit)
• Charge calculation with amounts (factor)
• Charge calculation for Euro-ISDN with cost parameters that are reported by
the trunk (AOC-S, AOC-D, and AOC-E).
• Charge calculation without charge information based on cost parameters

(CARRIER and ZONE) and length of the connection.
You can assign different prices for variable clocks (for example, for n sec.
connection duration) for each cost parameter and time of day (which can also
vary for each cost parameter). Different rate period tables and minimum and basic
charges can be taken into account for each cost parameter.
If the network signals charge information, this information is included when

calculating the charges.
The charge calculation is done centrally in the call detail recording. The
calculated charges are passed on to the call processing and shown on the
telephone station’s Digite display (CDRD).
59.9 Data Recording

To perform call detail recording, all of a connection’s relevant data must be
known. Sometimes this data is obtained in phases of a connection that are widely
spread out over time. Therefore, it must be collected step by step for each
connection.
A "connection block" is available for collecting this data. A connection block is

allocated to each connection. The identification is based on the trunk number and
the communication service. This allocation does not change for the duration of
the connection.
A31003-H3170-S103-6-7620, 02/2019
Data Selection
Two exceptions must be noted however:
• If a new paying party appears during a call, a new connection block must be
opened for this party. The old party is handled as if there is an end-of-
connection.
• The procedure is the same if a limiting value (charges or time) is reached.
Creating a standard data record:

Information is collected in the connection block (CB) during a connection.
• Calculation of the connection duration.
• If necessary, conversion of the cost unit using a table (only for ATND or
MTLC).
• Change of the communication service from "voice" to "fax" when the fax class
of service is set.
• Transmission of all necessary data in the standard data record.
Then the standard data record is transferred to the data selection function for
further processing.
59.10 Data Selection

The data selection programs offer the operators of systems with call detail
recording the capability of adjusting the data output of certain connections
according to internal company requirements concerning the existing output
capabilities (devices).
These then continue the processing of data records that were recorded by the
data recording function and that were entered into memory especially reserved
for this purpose at the end of the connection or section.
Selection sequence:
The selection processes each connection block or the standard data record that
results from it. This is also true for standard data records that result from
connection attempts (for example, station is busy in the trunk).
The basis of the selection process is the selection field, which is divided into 4 so-
called selection groups (see AMO SELG).
Each selection group corresponds to an independent output unit with definable

device allocation, where the outputs for "Display at attendant console" (or several
attendant consoles) or each HD file are considered as one device.
Selection field
A31003-H3170-S103-6-7620, 02/2019
Data Selection
GROUP 1 GROUP 2 GROUP 3 GROUP 4
Table 22 Selection field
Selection group
POOL_PART RES_OUT_WO_QUE
DEV_BAS DEV_RES
BLOC_BAS BLOC_RES
SEL_GR_STATE SEL_TAB
Table 23 Selection group
The following parameters are allocated to each of these selection groups.
• POOL_PART
Number of reserved elements (queue entries) in the CDB pool
• RES_OUT_WO_QUE
Mode of operation for the reserve output
• DEV_BAS
Device indicator for basic operation
• BLOC_BAS
Number of data records per output procedure (basic)
• DEV_RES
Device indicator for reserve operation
• BLOC_RES
Number of data records per output procedure (reserve)
• SEL_GR_STATE
Operating state of a selection group
• SEL_TAB
Field of 8 selection tables
Each selection group (1-4) taken into service compares the connection
characteristics of the standard data record with the customer-specific
characteristics given in its 8 selection tables.
If a connection characteristic within a selection group applies, the standard data
record is processed by the next selection group, regardless of the decision
(output/no output). Multiple outputs (to the same device) are thereby eliminated
even if overlapping characteristics are entered.
A31003-H3170-S103-6-7620, 02/2019
Data Selection
It is possible to make multiple outputs (parallel outputs) of a standard data record

to different devices if there are additional selection groups with the same
characteristic combination in the selection tables.
Selection table
A selection table contains 13 fields.
FORM_BAS FORM_RES CALC_LIST

DEST_LIMIT LIMIT_CHARGES LIMIT_TIME
MEMB_ROUT_CODE MEMB_SERV_IND MEMB_ATT_GR
POP1 POP2 NODE_TBL
COPIN CARRIER
Table 24 Selection table
Elements:
• OUT_IND: output indications. Consists of the fields FORM_BAS,

FORM_RES, CALC_LIST, DEST_LIMIT. 
The CALC_LIST field contains the new tariff group number, which is used
during the charge calculation.
Mode: DA_M_CGS_TA_OUT_IND_STR
• LIMIT_CHARGES: limiting value for call charge units; output occurs if this
value is exceeded.
Mode: DA_M_CONN_CHRG_UNIT_RNG
• LIMIT_TIME: limiting value for the duration of the connection; output occurs
if this value is exceeded.
Mode: DA_M_CG_TIME_STR
• MEMB_ROUT_CODE: routing code

Mode: DA_M_CGS_MEMB_ROUT_ARY
• MEMB_SERV_IND: service with which output occurs (network type,

transmission speed)
Mode: DA_M_CGS_SERV_IND_PST
• MEMB_ATT_GR: statement for selecting a maximum of 16 ATND groups.

Mode: DA_M_CGS_MENGE_ATT_GR_PST
• POP1: connection and class of service codes

Mode: DA_M_CG_MARK1_PST
• POP2: limiting values

Mode: DA_M_CGS_TA_MARK2_PST
A31003-H3170-S103-6-7620, 02/2019
Selection Group Operating States
• NODE_TBL: node number table (the node numbers are expanded to 4

places)
Mode: DA_M_CGS_NODE_NO_ARY
• COPIN: Class of Pin

Mode: POWERSET( DB_M_COPIN_RNG )
• CARRIER
Mode: POWERSET( DB_M_CP_CARRIER_RNG )
59.11 Selection Group Operating States

One condition considered when deciding whether the selection table of a
selection group checks a CDR record that is entered in memory is the current
operating state of the respective selection group, among other conditions.
This is why the corresponding state parameters are allocated to each selection
group. They can be changed by administration and maintenance orders (AMO
SELS).
This makes it possible to activate and deactivate call charge recording and CDR
displays indirectly by means of the output of a selection group without device
intervention (at times).
Operating states of selection groups (see also AMO SELS):
• State ’ON’
The selection group is activated.
Output should be performed with the allocated selection tables of the
selection group. If a processed CDR record is to be output, it is linked into the
output queue of the selection group and thereby released for output.
• State ’OFF WITH QUE’

The selection group is conditionally activated. The CDR record is processed
and linked in the output queue as in the state "ON". However, the output is
blocked until the selection group is reset to the operating state "ON" or "OFF
WITHOUT QUE".
All CDR records that, in case of output, are already linked to the output queue
at this time or that will be entered in this operating state in the future, are put
in safekeeping for output for as long as the memory capacity of the overflow
memory or the group’s individual memory is not reached. If the memory
capacity is reached, output starts on the reserve device.
In this operating state, maintenance work can be done on the allocated basic
output device without any loss of the output data of this selection group.
• State "OFF WITHOUT QUE"
A31003-H3170-S103-6-7620, 02/2019
Validity Check of the Selection Entries
The selection group is conditionally deactivated.

In this operating state, no processing is done to a CDR record in the selection
tables of this selection group, so there is no output.
However, all CDR records that are already linked in the output queue at the
time of the removal from service are still output. For block output, this can
result in the formation of a partial block.
• State ’OFF’
The selection group is deactivated.
In this operating state, there is no processing of CDR records in the selection
tables of this selection group. All CDR records that are linked in the queue at
the time of the removal from service are deleted.
59.12 Validity Check of the Selection Entries

To guarantee smooth sequencing of both the selection processing and the output,
AMO SELG – which processes and updates the selection tables – carries out a
validity check on the changed selection entries, especially the output indication.
A selection group is only released for operation if the result of the validity check
is positive or, in certain cases, if it can be corrected. Wrong, incomplete, or invalid
entries always lead to an error message, even when corrected.
59.13 Data Output

The output is divided into the following two functional units.
• Immediate Output
In immediate output, outputs to a device (such as printers, AM-WIN) or
outputs to long-term memory (hard disk) are executed as soon as the
connection is ended. In immediate output, the CDR records are copied to the
output format or, when storing on the hard disk, the CDR record is stored with
some supplementary data.
• Data Output on Demand

The call charge data, which is temporarily stored on the hard disk, is output
at a time defined by the customer.
This output can take place one time or periodically. The prerequisite is that an
AMO has been used to configure a dialog field for this job.
59.13.1 Immediate Output

Immediate output is divided into the following components:
A31003-H3170-S103-6-7620, 02/2019
Data Output
• Data preprocessing
• Formatting
• Output control
• Charge calculation
Selection Selection Selection Selection

group 1 group 2 group 3 group 4
Output preprocessing Output formatting Charge calculation
to the ATND
Format lists Tariff lists

Output Output
control control
PT 80 HD, FD,
DPS
CDRC
AM-Win
Figure 90 Overview of the selection
• Data preprocessing
The job of the data preprocessing is to configure the data records or formatted
data blocks in an output block according to the parameters entered in the
selection group.
The relevant output control takes over the output of this output block to the
requested output medium, depending on the selection group entries.
The following restrictions have been made for treating the attendant console
as an output device:
– An attendant group can have n-1 ATNDs.
– The maximum number of attendant groups is 16

If the base device is the same as the attendant console (ATND), no reserve
device is permitted. If the base device is another output device, the reserve
device can be an attendant console (ATND).
• Formatting
A31003-H3170-S103-6-7620, 02/2019
Data Output
The formatted (EBCDIC or ASCII code) CDR records can be transferred at

any time via fast file transfer (FT SINX and other file transfer programs that
are released for OpenScape 4000) to DMS or other applications. 
The OpenScape 4000 call detail recording files that the CDR records are filed
in the requested customer format in an FT file (file transfer file). You can
configure the format of the data records in the file with the help of AMOs. At
a time specified by the customer or when the file has reached its maximum
size, the file is closed and copied under a name specified by the customer.
This file is then availablefor file transfer. After this file has been transferred
with file transfer, it must be deleted, but not by call detail recording function.
If the file is still present at the time of the copy operation, an alarm message
is issued. The new file is then attached to the old file. If the file is not picked
up, attachments are made until the memory capacity limits are reached. After
this, data is lost.
When there is a restart or reload during the copy operation, the appropriate
data must be saved in a scratch file to prevent any duplicate or incomplete
data records when attaching. This data is used so that the file does not
contain any mutilated data records.
The storage in the "FT file" is done either by the selection (for immediate
output) or by output of the call charge data from the CDRC file to the "FT file".
The output records resulting from the formatting can be transferred to any
device controller and any transfer procedure (including DPS channel), even
if there is no device-specific data.
The outputs that run to the ATND contain data that is converted in the
switching unit to code appropriate for output.
The processing and compilation of the variable output format data is laid out
in format lists. These format lists consist of individual elements (see AMO
FTBL).
• Output control
Each output control uses programs, which vary according to the device to be
connected, for configuring and processing different types of files. The files are
output in any computer units or programs to the following:
– TTY (asynchronous terminals)
– DPS (connection of a data processing system)
• Charge calculation
The task of charge calculation is to calculate the charges for each connection
on the basis of the call data recorded in the CDR record using the tariff from
the selection table.
The type of charge calculation differs for the different communication services
and is therefore handled in several subcomponents (see AMO TTBL).
• Notes on the output devices
A31003-H3170-S103-6-7620, 02/2019
Data Output
The zone parameter of the CDR record has 54 domestic and 99 foreign zones
and 9 zones for internal, incoming, and tie trunk traffic.
Because of the large amount of data when recording the internal connections,
it may be necessary to output the call charge data quickly to a fast output
device. To do this, use an AMO to enter the appropriate notice ("output to fast
output device") in the call data recording bit string. If this bit is set, the call
charge data selection is done only with the first selection group. The
remaining selection groups are deactivated. In this case, temporary storage
in a CDRC file (as reserve device) is also not possible. This limitation to one
output device and one selection group makes it possible to achieve a
considerably higher output speed.
You can configure one basic and one reserve device for this one output.
Possible or useful combinations:
– DPS and magnetic tape (MT)
– DPS and FT file (file transfer)
– Magnetic tape (MT) and FT file
– FT file and MT
Storage for later retrieval (CDRC file) is not possible.
59.13.2 Data Output on Demand

Output on demand includes carrying out the dialog for the creation of the output
orders, the selection of the stored CDR records, and the provision of the selected
CDR records for output. There are 8 dialog fields provided for the output; these
can be used for both CDRS/CDRC and the call charge computer.
Unlike immediate output, output on demand allows the user to define the time of
the call data output.
The user creates the output order by dialog. The following types or orders are
possible:
• One-time orders (simple/multiple single order)
– With a simple single order, there is exactly one output at the time the user
defines.
– With multiple single orders, the user can specify a maximum of 3 different
output times.
• Periodic orders (simple/multiple standing orders)
– With a simple standing order, the user issues dialog commands to specify
the time of the first output and the period for the repeated outputs.
A31003-H3170-S103-6-7620, 02/2019
Data Output
– For multiple standing orders, the user specifies a maximum of three

different output times and exactly one period. Each of the maximum of 3
orders is then repeated periodically. Hours, days, or months are allowed
as periods (minimum value of the period is 1 hour, maximum value is 12
months).
Additional parameters when creating an output order - along with the output time
and period - are as follows:
– CDR file
– File beginning and end
– Output device
– Format table (AMO FTBL)
– Tariff table (AMO TTBL)
– Identifier indicating whether the data records should be deleted after

successful output.
– Identifier indicating whether a forced output of the CDR file is required. If

there is a file overflow, a forced output can be arranged. However, the file
is only printed if the "forced order" code was set in one of the dialog fields
during configuration. If no "forced order" code was set, the forced order is
ignored (AMO GEZAB).
The parameters of the completely created dialog commands are saved in a dialog
field and transmitted to the scheduled batch job processing function.
In addition to creating an output order, the CDRC dialog offers the following
functions:
– Cancel output order (scheduled batch job)
– Cancel outputs
– Output (log) dialog fields
A31003-H3170-S103-6-7620, 02/2019
Data Output
A31003-H3170-S103-6-7620, 02/2019
Requirements for Call Detail Transmission to the DPA
60 Call Detail Transmission
60.1 Requirements for Call Detail Transmission to the DPA

Depending on the administration in the OpenScape 4000 system, data can be
recorded in the OpenScape 4000 system over all outgoing and incoming trunk
and tie trunk connections and over internal connections and then prepared for call
detail tracing. This makes it possible to output connection and call detail data.
Either a printer, magnetic tape equipment, or a DPA coupled over the data
channel is available as the output device.
This section describes all messages and message sequences that are provided
for the transmission of data concerning the individual connections (individual call
data) over the data channel to the DPA.
The following general possibilities for transmitting this data to the DPA exist:
• Immediately after each connection ends (immediate output) initiated by

OpenScape 4000,
• After temporary storage of the data in OpenScape 4000
– On demand, initiated by the DPA,
– Upon the expiration of a (periodic) scheduled batch job in OpenScape

4000 initiated by OpenScape 4000,
– Upon overflow of the call detail file in OpenScape 4000 (forced output)
initiated by OpenScape 4000.
You can configure the required OpenScape 4000 behavior with the help of
administration and maintenance (AMOs).
Section 60.2, “Transmission of Individual Call Data” contains a more detailed

explanation of the individual call data.
60.2 Transmission of Individual Call Data

The transmission of individual call data is a part of the OpenScape 4000 system
feature ”Call detail recording, central (CDRC)”.
You must use AMO GEZU (device allocation) to configure the name of the DP
application that is to receive the data. You may configure only one DP application
name.
The transmission of the data to the DPA can occur either immediately after a
connection ends (immediate output) or after temporary storage in OpenScape
4000 (output on demand). You must configure the required OpenScape 4000
A31003-H3170-S103-6-7620, 02/2019
Transmission of Individual Call Data
behavior with AMOs GEZAB (configuration of the central call detail data
extraction).
It is also important that you suitably coordinate the DP application and the
OpenScape 4000 behavior with one another.
The two hard disk files CDR1 and CDR2 are available for the temporary storage
of the data in OpenScape 4000. Together they can currently accept a maximum
of 130,000 data records. Each separate CDR file can store a maximum of 65,000
data records. The standard value of the file size for the CDR files (AMO DAGR:
administration of the CDR file parameters) is between 30,000 and 40,000 CDR
records. Taking these boundary conditions into account, you can define the size
of the CDR files with AMO DAGR as needed.
If a CDR file overflows and a forced output to the DPA (see Section 60.3.2, “Data
Retrieval Initiated by OpenScape 4000 for Scheduled Batch Job or Forced
Output”) is not possible, you can specify that any other data that arises should be
output to a OpenScape 4000 printer.
You can configure the CDR files to meet different requirements. There are several
possibilities:
• The CDR2 file can be used as the overflow area for the CDR1 file.
• Certain connections, selected according to different criteria, can be recorded

in a particular CDR file.
For example, the criteria could be:
– the connection type (local or long-distance connection),
– the entry of a user in a user list,
– overstepping a limiting value for the time or cost.
Several such criteria can be integrated in a selection group and allocated to a

CDR file with AMO SELG (selection group administration).
Then all connections that meet all set criteria of the selection group are recorded
in the CDR file.
The message sequences are described in Section 60.3, “Message Sequences

for Transmitting Individual Call Data” and the different messages for the
transmission of individual call data are described in Section 60.4, “Messages
When Transmitting Individual Call Data”.
The individual components that form the messages (the so-called data elements)
are summarized in Section 60.5, “Types of Elements When Transmitting Call
Detail Data”.
The message contents are represented in EBCDIC. Numerical message

elements are to be interpreted as decimals in EBCDIC strings.
The message sequences and the message structure are defined. However, you
can use AMO FTBL (format table administration) to configure and change the
format and the contents of the actual connection and call detail data within the
A31003-H3170-S103-6-7620, 02/2019
Message Sequences for Transmitting Individual Call Data
data blocks so that it is customer-specific. This means that you can put together
the configurable part of the affected data record format in any way, using the data
elements specified in Section 60.5.2, “Configurable Elements”. Furthermore, you
can configure the length, justification, fill character, and, if needed, decimal
separation character (decimal point or comma) of these data elements.
60.3 Message Sequences for Transmitting Individual Call Data

There are four different message sequences for transmitting data over the data
channel:
1. Data retrieval initiated by the DPA
– The DP application retrieves OpenScape 4000 data.
2. Data retrieval initiated by OpenScape 4000
– upon the expiration of a scheduled batch job,
– when there is forced output because the CDR file overflows. 

(OpenScape 4000 requests that the DP application retrieves data.)
3. Immediate output after the end of a connection initiated by OpenScape 4000
– Data records that arise are transmitted to the DPA immediately.
4. Data output initiated by OpenScape 4000
– when there is forced output because the CDR file overflows.
A separate logical connection must be set up between OpenScape 4000 and the
DP application for each message sequence that should be handled (see S0 link
or V.24 link description concerning the connection setup and cleardown). The
connection setup and cleardown is always done by whichever of the two
applications is initiating the process (see above).
It is not possible to handle several message sequences simultaneously.
In any case, the DP application must always be ready to accept a connection

setup from OpenScape 4000 (if there is not already a connection). Even if you
plan that the DPA will initiate all data transmission (see point 1 above, Data
retrieval initiated by the DPA), it may still happen that OpenScape 4000 sets up
the connection for a forced output (see point 2 above, Data retrieval initiated by
OpenScape 4000).
SNA mainframes also have the capability of transmitting the connection and call
detail data in RJE operation (Remote Job Entry). In this case, only the message
sequences ”Data Retrieval Initiated by the DPA” and ”Data Output Initiated by
OpenScape 4000 for a Scheduled Batch Job or Forced Output” can be handled.
A31003-H3170-S103-6-7620, 02/2019
60.3.1 Data Retrieval Initiated by the DPA

The DP application sets up and clears down the connection to the OpenScape
4000 application (see S0 link or V.24 link description). During the connection, the
following messages are exchanged:
1. The DP application sends the message ”Send CDR information” to the

OpenScape 4000 application.
The reference field (REF) of this message indicates the source of the
requested data – the CDR1 or CDR2 file. In addition, the reference field
indicates whether or not OpenScape 4000 should delete the data after the
transmission or whether or not the data should not be transmitted at all and
just deleted in OpenScape 4000 immediately (see Section 60.5.1, “Elements
with a Fixed Specification”).
Two other fields (”Start of time frame” and ”End of time frame”) allow you to
request data that arises during a specific time frame.
2. The OpenScape 4000 application responds
– with a data block containing CDR records,
– with the message ”Good CDR information end”, if no data has been
saved,
– with the message ”Bad CDR information end” if it is not possible to

transmit at this time, for example, because the CDR file is currently being
administered.
3. In any case, the DP application acknowledges with the message ”CDR

information processed”.
Depending on whether this message was sent off with a new retrieval request or
with a terminate code,
– the message sequence starts again at point 2 (this means the

OpenScape 4000 application sends the next block of CDR records or the
message ”Good CDR information end” or ”Bad CDR information end”),
– the OpenScape 4000 application waits for the DP application to clear

down the connection.
To check the connection between the DP application and the OpenScape 4000
application, the DPA can send the message ”Connection verification (heartbeat)”
after the connection has been successfully set up. If the connection is active,
OpenScape 4000 acknowledges immediately (”AD00”).
IMPORTANT: The parameter ”CALLUP” (retrieval by DPA) in AMO GEZAB must

be responded to with ”Y” (Yes).
A31003-H3170-S103-6-7620, 02/2019
The size of the blocks to be transmitted is limited by the underlying transport

system. This means that the maximum number of data records per block –
adjustable with AMO GEZAB (call detail data extraction, central) – must be
coordinated with the size of the configured data records and the maximum block
size (max. 1020 bytes). 
To make sure that all data records currently stored in OpenScape 4000 have
been transmitted, the DP application should continue to answer with a new
retrieval request until the OpenScape 4000 application responds with ”Good CDR
information end” (especially as long as the DP application receives data blocks
that contain the maximum number of data records).
The message sequence is shown schematically in Figure 91.
If a message sequence that has been started is then interrupted, that is,
messages fail to appear, the OpenScape 4000 application waits 10 minutes and
then clears down the connection to the DP application.
If the "SEND CDR information" message sent by the DP application contains the
order to delete the data in OpenScape 4000 after it has been transmitted, the data
is not deleted until the internal block has been completely output and the last
"CDR information processed" message concerning this block has arrived in
OpenScape 4000.
DP application OpenScape 4000 application
”Send CDR information”
(Record ID = ”A0”)
”CDR information block on demand”

(Record ID = ”AA”, ”AB”, ... ”AB”)
or
”Good CDR information end” or
"Bad CDR information end"
"CDR information processed" (Record ID = ”AC” or ”AD”)
(with new retrieval request
or termination) *)
for new retrieval request
*)This acknowledgement must occur within 10 minutes or OpenScape 4000 breaks off
the call detail transmission.
Figure 91 Message sequence for data retrieval initiated by the DPA.
A31003-H3170-S103-6-7620, 02/2019
The DP application handles the preceding setup and following cleardown of the
connection.
60.3.2 Data Retrieval Initiated by OpenScape 4000 for

Scheduled Batch Job or Forced Output
The OpenScape 4000 application sets up and clears down the connection to the
DP application (see S0 link or V.24 link description). During the connection, the
following messages are exchanged:
1. OpenScape 4000  DPA

The OpenScape 4000 application sends the message ”CDR data retrieval
request” to the DP application.
In this message, the value of the reference (REF) indicates whether the data
should be retrieved from the CDR1 file or from the CDR2 file.
An additional field indicates the reason for the request:
a) Expiration of a scheduled batch job in OpenScape 4000,
b) Forced output because of CDR file overflow.
Depending on the reason for the request, the DP application proceeds
according to 2.a or 2.b.
2. DPA  OpenScape 4000 

The DP application responds with the message ”Send CDR information”. The
reference indicated in the request determines the reference field in this
response.
a) Scheduled batch job
The reference must only agree with the reference of the preceding ”CDR
data retrieval request” message as far as the information concerning the
CDR1 or CDR2 file is concerned. However, the DP application can
specify whether the data in OpenScape 4000 should be deleted after the
transmission or not (see the description of the reference field in Section
60.5.2, “Configurable Elements”).
b) Forced output
The reference must completely agree with the reference of the preceding
”CDR data retrieval request” message; this already contains the order to
delete the data in OpenScape 4000 after the transmission.
A31003-H3170-S103-6-7620, 02/2019
From this point on, the message exchange proceeds exactly like for ”Data
retrieval initiated by the DPA" (see Section 60.3.1, “Data Retrieval Initiated by
the DPA”, starting with Point 1). However, unlike there, the OpenScape 4000
application handles the connection cleardown.
IMPORTANT: The parameter ”CALLUP” (retrieval by the DPA) in AMO GEZAB

must be responded to with ”N” (No).
"CDR data retrieval

request”
(Record ID = ”AF”)
”Send CDR information”

or
(Record ID = ”AC” or ”AD”)
"CDR information processed"
(with new retrieval request
or termination)*)
*)This acknowledgement must occur within 10 minutes or OpenScape 4000

breaks off the call detail transmission.
Figure 92 Message sequence for data retrieval initiated by OpenScape 4000.
The OpenScape 4000 application handles the preceding setup and following
cleardown of the connection.
Starting with the message ”Send CDR information”, the message sequence
corresponds to the CDR data retrieval initiated by the DPA (cf. Figure 91).
60.3.3 Immediate Output at the End of a Connection

If you have configured immediate output, once a connection is made, it is kept –
unlike data transmission on demand. The connection is not cleared down until it
has remained inactive over a longer time and it is set up again as soon as the next
data record is ready.
A31003-H3170-S103-6-7620, 02/2019
DPA (see S0 link or V.24 link description). During the connection, the following
messages are exchanged:
1. OpenScape 4000  DPA

OpenScape 4000 sends a data block with call data records to the DPA. The
only real differences between this data block and a data block sent when the
DPA initiates the transmission are the record identifier and the reference field.
2. DPA OpenScape 4000
a) The DPA acknowledges with the message ”CDR information processed”

together with a new retrieval request
b) The DPA sends the message ”Repeat the same call data record”, and
after approximately 30 seconds, the last transmitted data block is sent
again (OpenScape 4000 DPA), then back to Point 2.

Then OpenScape 4000
– sends the next data block,
– clears down the logical connection after longer inactivity.
Usually the question concerning the storage in OpenScape 4000 is not necessary
when the connection data is output immediately to the DPA. If there is a
disturbance, that is, if transmission to the DPA is not possible, a CDR file can be
specified as the (reserve) output device. This entry is made with AMO SELG
(selection group administration) when configuring the immediate output.
When the connection between OpenScape 4000 and the DPA resumes, any
temporarily stored call charge records that may have arisen can be retrieved by
the DP application (see Section 60.3.1, “Data Retrieval Initiated by the DPA”).
OpenScape 4000 simultaneously attempts to send such CDR information to the
DPA for immediate output.
There are two different ways of doing this:
• Case 1: OpenScape 4000 does not become active until after the connection
returns:
The immediate output of the call detail data is initiated. The DPA can retrieve
the temporarily stored call detail data at a later time (see Section 60.3.1, “Data
Retrieval Initiated by the DPA”).
• Case 2: When the connection resumes, the DP application becomes active

first (before OpenScape 4000 starts with the immediate output):
A31003-H3170-S103-6-7620, 02/2019
The DP application retrieves the temporarily stored data from the CDR file. If
new call charge records for immediate output arise while the DPA is retrieving
the CDR data, these are simultaneously written into the CDR file. Only the
data stored as of the start of the retrieval is transmitted. All data stored after
the start of the retrieval must be retrieved with a new request later. After this
sequence has finished, OpenScape 4000 automatically switches to the
immediate output of the call charge records to the DPA.
”CDR information block with

"CDR information processed" immediate output"
(with new retrieval request) (Record ID = ”AH”, ”AI”, ... ”AI”)
or
”Repeat the same
call data record”
(Record ID = ”A1”, ”W1”)
after longer inactivity

the logical connection is cleared down
Figure 93 Message Sequence for Immediate Output by OpenScape 4000.
cleardown of the connection.
60.3.4 Data Output Initiated by OpenScape 4000 for a

Scheduled Batch Job or Forced Output
computer application (see S0 link or V.24 link description). During the connection,
the following messages are exchanged:
1. OpenScape 4000 DPA

The OpenScape 4000 application sends a data block with call data records to
the DP application.
Reasons for the output:
A31003-H3170-S103-6-7620, 02/2019
a) Expiration of the scheduled batch job in OpenScape 4000,
b) Forced output because of CDR file overflow.
2. DPA  OpenScape 4000

The DPA acknowledges with the message ”CDR information processed” with
a new retrieval request.

Then OpenScape 4000
– sends the next data block,
– clears down the logical connection after longer inactivity.
IMPORTANT: The parameter ”CALLUP” (retrieval by DPA) in AMO GEZAB must

be responded to with ”Y” (Yes).

output initiated by OpenScape 4000"
or
"CDR information processed" (Record ID = ”AC” or ”AD”)
(with or without
new retrieval request)
Figure 94 Message Sequence for Data Retrieval Initiated by OpenScape 4000.
cleardown of the connection.
60.3.5 Data Transmission in RJE Operation (RJE =

Remote Job Entry)
The connection and call detail data can also be transmitted to SNA mainframes
in RJE operation (Remote Job Entry). This capability is in addition to the four
message sequences that are described in Section 60.3.1, “Data Retrieval
Initiated by the DPA” to Section 60.3.4, “Data Output Initiated by OpenScape
4000 for a Scheduled Batch Job or Forced Output”.
A31003-H3170-S103-6-7620, 02/2019
There are two different message sequences for transmitting data in RJE
operation:
1. Data Retrieval Initiated by the DPA (SNA RJE)
– The DP application retrieves OpenScape 4000 data.
2. Data Output Initiated by OpenScape 4000 for Scheduled Batch Job or Forced
Output (SNA-RJE)
– When there is forced output because the CDR file overflows.
It is not possible to handle several message sequences simultaneously.
In any case, the DP application must constantly be ready to accept a connection

setup from OpenScape 4000 (if there is not already a connection).
60.3.5.1 Data Retrieval Initiated by the DPA (SNA RJE)
The DP application handles setting up and clearing down the connection to the
OpenScape 4000 application (see CallBridge/ACL description "V.24 LINK/SNA
connection").
In RJE operation, no logical connection is set up between the DP and OpenScape

4000 applications. Instead, the DP application hands over the message ”Send
CDR information” in the form of a control card file to OpenScape 4000 and also
receives the CDR information in the form of a control card file. This file contains
the currently stored data records and has the same structure as a CDR
information block (see Figure 96).
The DPA does not acknowledge the receipt of the data and does not send the
message ”CDR information processed”. A new retrieval request is not necessary
because all existing data has been transmitted.
It must be ensured that the transmitted data is deleted in OpenScape 4000 (if this
was requested in the control card file) before the end job card is sent.
During the connection, the following messages are exchanged:
1. The DP application sends the message ”Send CDR information” to the

OpenScape 4000 application. The source of the requested data - CDR1 file
or CDR2 file - is indicated in the reference field (REF) of this message. The
reference field also contains a command that indicates whether or not
OpenScape 4000 should delete the data after the transmission and whether
or not OpenScape 4000 should send an acknowledge after the ”Delete
without output”.
Two other fields (”Start of time frame” and ”End of time frame”) allow you to
request data that arises during a specific time frame.
2. The OpenScape 4000 application responds
A31003-H3170-S103-6-7620, 02/2019
– with a data block containing CDR records,
– with the message ”Good CDR information end”, if no data has been
saved,
– with the message ”Bad CDR information end” if it is not possible to

transmit at this time, for example, because the CDR file is currently being
administered.
IMPORTANT: The size of the blocks to be transmitted is limited by the underlying

transport system. This means that the maximum number of data records per
block – adjustable with AMO GEZAB (call detail data extraction, central) – must
be coordinated with the size of the configured data records and the maximum
block size. 
If the "SEND CDR information" message sent by the DP application contains the
order to delete the data in OpenScape 4000 after it has been transmitted,
OpenScape 4000 deletes the data after internal blocking is done. This internal
blocking can be three to ten times larger than the blocking set up in AMO GEZAB.
(Example: a blocking of 10 is entered in AMO GEZAB, but the data is not deleted
from the hard disk until 100 data records have been transmitted.)
The internal blocking is determined as follows:
no yes
CDRCDIS blocking
>=40
no yes
CDRCDIS blocking
>10
Internal blocking Internal blocking Internal blocking

= 3 times = 10 times = 40 times
CDRCDIS blocking CDRCDIS blocking CDRCDIS blocking
Figure 95 Determination of the Internal Blocking Value (SNA - RJE)
A31003-H3170-S103-6-7620, 02/2019
Messages When Transmitting Individual Call Data
Control card data has contents

similar to ”Send CDR information”
Data file
has contents similar to
or

(Record ID = ”AC” or ”AD”)
Figure 96 Message Sequence for Data Retrieval Initiated by the DPA (SNA -
RJE )
60.3.5.2 Data Output Initiated by OpenScape 4000 for

Scheduled Batch Job or Forced Output (SNA-RJE)
DP application (see V.24 link/SNA connection description).
The OpenScape 4000 application sends the DPA the call detail data in the form
of a job with start job card, call detail data, and end job card. The trigger is the
expiration of a OpenScape 4000 scheduled batch job.

output initiated by OpenScape 4000"
Figure 97 Message Sequence for Data Retrieval Initiated by OpenScape 4000

(SNA - RJE )
60.4 Messages When Transmitting Individual Call Data

The following describes the different messages for the transmission of individual
call data:
A31003-H3170-S103-6-7620, 02/2019
• Send CDR information,
• CDR information block on demand or with immediate output,
• Bad or good CDR information end,
• CDR information processed,
• CDR data retrieval request
• Repeat the same call data record (immediate output),
• Verification of connection (”heartbeat”).
The record identifier unambiguously identifies each message.
The message contents are represented in EBCDIC. Numerical message

elements are to be interpreted as decimals in EBCDIC strings.
The setup of the messages is defined. However, you can use AMO FTBL (format
table administration) to configure and change the format and the content of the
actual connection and call detail data within the data blocks (data records with
record identifiers ”AA”, ”AB”, ”AH” and ”AI”) so that it is customer-specific.
The separate data elements of the messages are summarized and explained in
Section 60.5, “Types of Elements When Transmitting Call Detail Data”.
60.4.1 Message ”Send CDR Information”

Direction:
DPA OpenScape 4000
Format:
Fixed format
RID REF Start of time End of time

frame frame
2 2 10 10
Table 25 Data Record ”Send CDR information”, Direction: DPA -> OpenScape
4000
A31003-H3170-S103-6-7620, 02/2019
Description
Position Name Value Description

(byte)
1–2 RID ”A0” Record identifier (see Section 60.5.1, “Elements
with a Fixed Specification”)
3–4 REF Reference (see Section 60.5.1, “Elements with a
Fixed Specification”)
5 – 14 Start of the time frame in format yymmddhhmm *);
if dd = 00, the time frame starts with the start of the
file
15 – 24 End of the time frame in format yymmddhhmm *);
if dd = 00, the time frame ends with the end of the
file
Table 26 Description of Data Elements for “Send CDR information”, Direction:

DPA -> OpenScape 4000
*) All components of the data should be right justified with leading zeros.
If the entire contents of the file should be sent, the information concerning the start
and end of the time frame can be left out completely.
If the year yy entered is  80, it is considered to be in the 21st century and if yy >
80 it is considered to be in the 20th century (for example, yy = 00 corresponds to
2000; yy = 99 corresponds to 1999).
60.4.2 Message "CDR information block on demand"

or "CDR information block with immediate output"
Direction
OpenScape 4000  DPA
Format:
Only the record identifier (Record ID) and, for the first record, the reference (REF)
have a fixed definition.
You can put the rest together in any way from the data elements defined in
Section 60.5.2, “Configurable Elements”. Furthermore, you can configure the
length, justification, fill character, and, if needed, decimal separation character
(decimal point or comma) of these elements. Examples of possible formats are
given in the following.
A31003-H3170-S103-6-7620, 02/2019
Setup of the first data record in a block (Example)
RID REF BLENBYT Output-Time BLENREC

2 2 4 10 3
Table 27 Setup of the First Data Record in a Block (Example), Direction:

OpenScape 4000 -> DVA
Description:

(byte)
1–2 RID Record identifier (see Section 60.5.1, “Elements with a
”AA” Fixed Specification”)
”AH” on demand
For immediate output
3–4 REF Source of the data to be transmitted
”00” for immediate output
”01” CDR1 file
”02” CDR2 file
5–8 BLENBYT Length of the entire block in bytes
right justified, with leading zeros *)
9 –10 OUTYEAR Date of the output: year (right justified, with leading
zeros*))
11 – 12 OUTMONN Date of the output: month (right justified, with leading
zeros*))
13 – 14 OUTDAYN Date of the output: day (right justified, with leading
zeros*))
15 – 16 OUTHOUR Date of the output: hour (right justified, with leading
zeros*))
17 – 18 OUTMIN Date of the output: minute (right justified, with leading
zeros*))
19 – 21 BLENREC Number of the data records following in the block;
(right justified, with leading zeros *)
Table 28 Description of Data Elements for "CDR information block on demand

or for immediate output”, Direction: OpenScape 4000  DPA
*) The coding information (length, justification, and fill character) applies to the present
example.
Setup of the data records following in the block (example):
Format
RID L SWP STNID CHRGEE PIN TKNOLIST

2 4 2 1 6 12 6
Table 29 Setup of the following data records in the block (example)
A31003-H3170-S103-6-7620, 02/2019
ROUTCN DESTPTY NETTYPE SERVICE SPEED CHRGUNIT

2 22 1 1 1 4
End-of-connection Call duration MSGNO SIGDATA

13 7 5 1
Description

(byte)
1–2 RID Record identifier (see Section 60.5.1, “Elements with
a Fixed Specification”)
“AB” On demand
“AI” For immediate output
3–6 L ”0084” Length of the following data in bytes ***)
7–8 SWP ” 1”... Partial switching procedure **)
”11”
9 STNID ”1”... User ID **)
”5”
10 – 15 CHRGEE Party charged for the connection 
left justified, filled with blanks *)
16 – 27 PIN Personal id
28 – 33 TKNOLIST Fictitious circuit number (trunk no. list)
right justified, with leading blanks *)
34 – 35 ROUTCN Trunk group code
right justified, with leading blanks *)
36 – 57 DESTPTY Newly selected or through connected destination for
a connection.
58 NETTYPE ”1”... Output of the network description **)
”3”
59 SERVICE ”1”... Output of the service **)
”6”
60 SPEED ”1”... Output of the transmission speed **)
”6”
61 – 64 CHRGUNIT Call charge units
Table 32 Description of the Data Elements for "CDR information block on

demand or for immediate output”, Direction: OpenScape 4000 
DPA
A31003-H3170-S103-6-7620, 02/2019

(byte)
65 – 66 ENDYEAR End-of-connection: year (right justified, with leading
zeros*))
67 – 68 ENDMONTH End-of-connection: month (right justified, with
leading zeros*))
69 – 70 ENDDAY End-of-connection: day (right justified, with leading
zeros*))
71 – 72 ENDHOUR End-of-connection: hour (right justified, with leading
zeros*))
73 – 74 ENDMIN End-of-connection: minute (right justified, with
leading zeros*))
75 – 76 ENDSEC End-of-connection: seconds (right justified, with
leading zeros*))
77 END10 End-of-connection: 1/10 seconds (right justified, with
leading zeros*))
78 – 79 CONHOUR Call duration: hours (right justified, with leading
zeros*))
80 – 81 CONMIN Call duration: minutes (right justified, with leading
zeros*))
82 – 83 CONSEC Call duration: seconds (right justified, with leading
zeros*))
84 CON10 Call duration: 1/10 seconds (right justified, with
leading zeros*))
85 – 89 MSGNO Message’s consecutive number
90 SIGDATA ”1”... Identification whether the data record is correct,
”2” incorrect, or duplicate **)
Table 32 Description of the Data Elements for "CDR information block on

demand or for immediate output”, Direction: OpenScape 4000 
DPA
*) The coding information (length, justification, and fill character) applies to the
present example.
**) The coding given for the values applies to the present example.
The appropriate code for the possible values of the element must be set with AMO
TEXT.
***) This length is not one of the configurable data elements. It is set up as field with
constant contents.
60.4.3 Message ”Good/Bad CDR information end”

Direction:
OpenScape 4000 DPA
A31003-H3170-S103-6-7620, 02/2019
Format:
Fixed format
RID REF
2 2
Table 33 Data record for "Good/Bad CDR information end”, direction:

Description

(byte)
1–2 RID Record identifier (see Section 60.5.1, “Elements with a
“AC” Good
“AD” *) Bad
3–4 REF Source of the transmitted data
”00” **) only possible for record identifier = ”AD” 
”02” CDR2 file
Table 34 Description of the Data Elements for "Good/Bad CDR information

end", Direction: OpenScape 4000  DPA
*) e.g.: Incorrect block length, file not available, FTBL not generated, DPA retrieval
is not set to ”Yes”, CGD: Area does not exist, etc.
**) e.g.: No reference to CDR file in message ”Send CDR information” or block
length greater than 1020 bytes
60.4.4 Message ”CDR information processed”

Direction:
DPA  OpenScape 4000
Format:
Fixed format
RID REF NRR

2 2 1
Table 35 Data Record for "CDR information processed", Direction: DPA ->
OpenScape 4000
A31003-H3170-S103-6-7620, 02/2019
Description

(byte)
1–2 RID ”A1” Record identifier (see Section 60.5.1, “Elements with
3–4 REF Reference (see Section 60.5.1, “Elements with a
5 NRR New retrieval request
”0” Interrupt transmission
”1” Request for next block or acknowledgement of ”AC..”
/ ”AD..”
Table 36 Description of the Data Elements for “CDR information processed”,

Direction: DPA  OpenScape 4000
60.4.5 Message "CDR data retrieval request"

Direction:
OpenScape 4000 DPA
Format:
Fixed format
RID REF RRR

2 2 1
Table 37 Data Record for "CDR data retrieval request", Direction: OpenScape
4000  DPA
Description

(byte)
1–2 RID ”AF” Record identifier (see Section 60.5.1, “Elements with
3–4 REF Notification of where to find the data to be transmitted
”02” CDR2 file
5 RRR Reason for the retrieval request
”1” Scheduled batch job in OpenScape 4000
”2” Forced output
Table 38 Description of the Data Elements for “CDR data retrieval request”,
Direction: OpenScape 4000  DPA
A31003-H3170-S103-6-7620, 02/2019
60.4.6 Message ”Repeat the same call data record (for

immediate output only)”
Direction:
DPA OpenScape 4000
Format:
Fixed format
RID REF RR
2 2 1
Table 39 Data Record for "Repeat the same call data record (for immediate
output only)", Direction: DPA  OpenScape 4000
Description

(byte)
1–2 RID ”W1” Record identifier (see Section 60.5.1, “Elements with
3–4 REF ”00” Immediate output
5 RR Request for repetition
”1” Request the same block
Table 40 Description of the Data Elements for “Repeat the same call data
record (for immediate output only)”, Direction: DPA  OpenScape
4000
60.4.7 Verification of Connection (”Heartbeat”).

The DPA can send this job to determine whether there is a logical connection. In
the ”good case”, OpenScape 4000 acknowledges immediately, in the "bad case"
OpenScape 4000 cannot react.
Job:
Direction:
Format:
Fixed format
A31003-H3170-S103-6-7620, 02/2019
RID REF
2 2
Table 41 Data Record for "Verification of connection (“Heartbeat”)", Direction:

Description

(byte)
1–2 RID ”A0” Record identifier (see Section 60.5.1, “Elements with
3–4 REF ”00” No file
Table 42 Description of the Data Elements for “Verification of connection

(“Heartbeat”)”, Direction: DPA  OpenScape 4000
Acknowledge:
Direction:
Format:
Fixed format
RID REF
2 2
Table 43 Data Record for "Verification of connection (“Heartbeat”)", Direction:

Description
Positio Name Value Description

n (byte)
1–2 RID ”AD” Record identifier (see Section 60.5.1, “Elements with a
3–4 REF ”00” No file
Table 44 Description of the Data Elements for “Verification of connection

(“Heartbeat”)”, Direction: OpenScape 4000  DPA
A31003-H3170-S103-6-7620, 02/2019
Types of Elements When Transmitting Call Detail Data
60.5 Types of Elements When Transmitting Call Detail Data

Each data record exchanged between OpenScape 4000 and the DPA in the
framework of call detail recording consists of particular individual components,
so-called data elements.
All elements are coded in EBCDIC. Numerical message elements are interpreted
as decimals in EBCDIC strings.
You should distinguish between
• elements with a fixed specification

such as record identifier, reference, and others,
• configurable elements.
You can put together the configurable part of the data block format (see
Section 60.4.2, “Message "CDR information block on demand" or "CDR
information block with immediate output"”) from these elements with AMO
FTBL or AMO TEXT. You can set the length, justification, fill character, and
decimal separation character (decimal point or comma), if any, for each
element.
The elements with a fixed specification and those that are configurable are listed
in detail in Section 60.5.1, “Elements with a Fixed Specification” and Section
60.5.2, “Configurable Elements”.
A31003-H3170-S103-6-7620, 02/2019
60.5.1 Elements with a Fixed Specification
Name Value Description

RID Record identifier
A particular record identifier is unambiguously allocated to each
message in connection with the transmission of connection and call
detail data:
”A0” Send CDR information or Verification of connection
”A1” CDR information processed
”AA” Block start for output on demand
”AB” Call data record for output on demand
”AC” Good CDR information end
”AD” Bad CDR information end or Verification of connection
”AF” CDR data retrieval request
”AH” Block start for immediate output
”AI” Call data record for immediate output
”W1” Repeat the same call data record (for immediate output)
Byte 1 of the record identifier contains the service identifier (for
example, call detail recording), byte 2 contains the meaning and also
the direction of the data record in question: data records going from
OpenScape 4000 to the DPA are identified by letters, data records
going from the DPA to OpenScape 4000 are identified by numbers.
REF Reference
The reference indicates the source of the data that is being transmitted
or that is to be transmitted. Unless otherwise stated (see Section
60.5.1, “Elements with a Fixed Specification”), all reference entries
within a message sequence must agree.
The reference has the following meanings for the transmission of
individual call data:
Transmission of the data from
”00” No file (immediate output)
”01” CDR1 file without deleting
”02” CDR2 file without deleting
”03” CDR1 file with deleting
”04” CDR2 file with deleting
Deletion of the data without transmission from
”05” CDR1 file (for SNA-RJE without end message) *)
”06” CDR2 file (for SNA-RJE without end message) *)
”07” CDR1 file (for SNA-RJE with end message) *)
”08” CDR2 file (for SNA-RJE with end message) *)
Table 45 Elements with a Fixed Specification
A31003-H3170-S103-6-7620, 02/2019

NRR New retrieval request
”0” Interrupt transmission
”1” Request for next block or acknowledge ”AC”, ”AD”
RRR Reason for the retrieval request
”0” Scheduled batch job in OpenScape 4000
”1” Forced output
RR Request for repetition
”1” Request for the same immediate output record or block
Table 45 Elements with a Fixed Specification
IMPORTANT: To delete the data without transmitting it, use the values ”05” and
”06” in dialog operation (an end message is always implied in dialog operation).
These two values indicate no end message only in the SNA-RJE operations, so
the values ”07” and ”08” are still available. These two values allow the data to be
deleted without transmission with end message, even in SNA-RJE operation.
60.5.2 Configurable Elements
IMPORTANT: The indication ”(n-digit)” in an element refers to the possible infor-

mation content (digits or characters) of the element in question. A shorter or
longer length can be configured for the elements unless the entry in the table
reads ”max. n-digit”.
Example 1:
The element CHRGEE (party responsible for connection costs) with the
statement ”(6-digit)” can, for example, be configured to be four digits. This is
useful if the party responsible for connection costs (paying party) has only four
digits. On the other hand, the field can also be configured as eight digits if, for
example, the DP application is expecting an 8-digit field. In this case, 6 digits
contain the actual value and the remaining digits contain the fill character.
For certain elements, you must use AMO TEXT to set up text strings for all
possible values (while taking the number of possible digits into consideration).
Example 2:
For the element OUTDAYC (date of the output: name of the day of the week),
"MONDAY ", "TUESDAY ", "WEDNESDAY ", "THURSDAY " and so on (each
10 characters long)
or "MO", "TU", "WE", "TH", and so on
or the short form "1", "2", "3", "4", and so on
A31003-H3170-S103-6-7620, 02/2019
can be set up as values.
Configurable Elements
Name Description
ACCTCODE The call’s account code. The user enters the account code either before
or during the call (12-digit)
ACDAGTID ACD Agent ID (6 characters). ID of an ACD Agent for an incoming or
outgoing answered call
ACDGRPID ACD Group ID (3 Zeichen). Group ID for an ACD call
ADPLOAD Processor load of the ADP in 1/10 percent. This is the average load over
10 seconds (4-digit). The time stamp, showing when the load was
determined, is in the field "end of connection"->ENDDAY (2-digit),
ENDMONTH (2-digit), ENDHOUR (2-digit), ENDMIN (2-digit), ENDSEC
(2-digit), END10 (1-digit).
AOCTYPE Type of the call charge accounting message (10-digit)
You can use AMO TEXT to set up text strings for this element, which can
have the following values:
Call detail information during the call (D_AOC)
Call detail information when the call ends (E-AOC)
Call detail information when setting up the connection (S_AOC)
ATNDGRNO Attendant Group (2-digit) (see In the fields for incoming calls are:)
ATTCALLP Attendant Call Priority - priority of a call in an attendant queue. Only
available for ACWinMQ (2 characters)
ATTCALLR Attendant Intercept Reason - only available for ACWinMQ (2 characters)
ATTCALLT Attendant Call Type- only available for ACWinMQ (2 characters)
ATTQUEID Attendant Queue ID - queue ID assigned to a call. Only available for
ACWinMQ (2 characters)
BCHLCNT Number of B channels (max. 2-digit). No longer maintained
BLENBYT Block length in bytes (5-digit)
BLENREC Number of records per block (5-digit)
(The number of data records in the block with record ID = ”AB” or ”AI” )
CALCTYPE Type of billing used (10-digit)
Pay phone (RURAL) (CLOCK)
Pulse or amounts from CO (PULSES)
Accounting of call charges based on time (WOUT)
CALLEPTY Called party: number that was dialed by the calling station. (22-digit)
CALLIID Station ID of the calling party (text parameter STNID is defined in AMO
TEXT) (10-digit)
CALLILV0 Node number of calling party (3-digit max.)
CALLILV1 Subdomain number of the calling party (max. 3-digit)
CALLILV2 Domain number of the calling party (max. 2-digit)
Table 46 Configurable Elements
A31003-H3170-S103-6-7620, 02/2019
Name Description
CALLIPTY Calling party: party that initiated the existing connection/segment. (22-
digit)
CALLIONI Originating network ID of calling party
CARRIER Identifier for the communication network as text string (10-digit, see In the
fields for incoming calls are: and In the fields for internal calls are:)
CARRIER_0 (internal)
CARRIER_1
CARRIER_n
CARRIER_9
CAUSE Output of the cause of the clearing of a connection (3-digit, see table
Meaning of the Values for the Element CAUSE in AMO FTBL)
CHOFCON Output of the type of connection (10-digit, see In the fields for incoming
calls are: and In the fields for internal calls are:)
Local connection
Long-distance connection
Local connection with exceeded limiting value
Long-distance connection with exceeded limiting value
No entry
Rerouting / Routopt
You can set up the limiting value for the number of the call charge pulses
or the connection duration with AMO GRZW.
CHRGUNIT Call charge units: The units in this field are recalculated from the
calculated costs. (5-digit, see In the fields for internal calls are:)
CON10 Call duration: 1/10 seconds (1-digit)
CONCHRG Output of the costs including sales tax.
For calculation in 1/100th (max. 8-digit)
For calculation in 1/100000th (max. 12 digits)
OpenScape 4000 calculates this value according to the price per pulse
set up with AMO TTBL (tariff table administration)
CONCHRN Output of the net costs without sales tax.
For calculation in 1/100th (max. 8 digits)
For calculation in 1/100000th (max. 12 digits)
CONHOUR Call duration: hours (2-digit)
CONMIN Call duration: minutes (2-digit)
CONNSTEP All of a connections’s CDB records are numbered in order (starting with
contents 1), (3-digit).
A31003-H3170-S103-6-7620, 02/2019
Name Description
CONNTYPE Output of the connection type as text string (10 characters, see In the
fields for incoming calls are:).
Outgoing connections (OUTGO)
Internal connections (INTERN)
Incoming connections (INCO)
Attendant activity (ACACT)
Processor load (LOAD)
CONSEC Connection duration: seconds (2-digit)
CONSECT Connection duration, total in tenths of seconds (6-digit)
COPIN Output of the PIN class (see AMO PERSI) as text string (10 characters)
No PIN available
PIN Class_1
PIN Class_n
PIN Class_8
CTRDIFF CDRS difference counter, only CDRS functionality (5-digit)
CTRTOT CDRS summation counter, only CDRS functionality (5-digit)
DESTLV0 Node number of the new or connected party, (3-digit)
DESTLV1 Subdomain number of the new or connected party, (3-digit)
DESTLV2 Domain number of the new or connected party, (2-digit)
DESTPID Station ID of the new or connected party. It is not possible to determine
the ID for dialed numbers. In this case, "unknown" is output. The text
parameter STNID is defined in AMO TEXT (10 digits)
DESTPTY connected party: Newly selected or through connected destination for a
connection (22 digits).
DISPCHRG Connection charges, including sales tax, shown on display. Calculated
during the connection.
For calculation in 1/100000th (max. 12-digit)
DISPCHRN Connection charges, not including sales tax, shown on display. 
Calculated during the connection.
For calculation in 1/100000th (max. 12-digit)
DNIS Text string regarding the called party. Output of the Identification Service
Number belonging to the dialed number. The DNIS number is provided
by the BREAKIN trunk and refers to the called party (11-digit)
END10 End-of-connection: tenths of seconds (1-digit)
ENDDAY End-of-connection: day (2-digit)
ENDHOUR End-of-connection: hour (2-digit)
ENDMIN End-of-connection: minute (2-digit)
ENDMONTH End-of-connection: month (2-digit)
A31003-H3170-S103-6-7620, 02/2019
Name Description
ENDSEC End-of-connection: second (2-digit)
ENDYDAY End-of-connection: day of year (1...366, 3-digit)
ENDYEAR End-of-connection: year (4-digit)
EXPENS Output of the identifier ’Expensive connection’ as text string (10-digit)
Cheap
Expensive
Free A-station
Free B-station
FACA Values for FX or TTA trunk access on BREAKIN trunk as part of the NI2
PRI service (5-digit)
FACB Values for FX or TTA trunk access on BREAKOUT trunk as part of the NI2
PRI service (5-digit)
FLAG1 No longer maintained
FLAG2 No longer maintained
GLOBLLV0 Node number of the global leg ID (3-digit), identical to LEGLV0
GLOBLLV1 Subdomain number of the global leg ID (3-digit), identical to LEGLV1
GLOBLLV2 Domain number of the global leg ID (2-digit), identical to LEGLV2
GLOBLSEQ Sequence number of the global leg ID. A new global call ID is provided
only when there is a new connection (8-digit), identical to LEGSEQ
GLOBLV0 Node number of the global call id, (3-digit)
GLOBLV1 Subdomain number of the global call id, (3-digit)
GLOBLV2 Domain number of the global call id, (2-digit)
GLOBSEQ Global call ID: a number global call ID may only be created when a new
connection is set up (8-digit).
HOLDDUR Total hold time in 1/10 seconds (5-digit)
IDPP Output of the CDRS station number as text string (10 characters)
Trunk circuit (TC)
Main PBX tie trunk (MTLC)
Station (STN)
Attendant console (ATND)
INFOTYPE Type of information (10-digit),
If accounting call charges from CO, then units or amounts.
Amounts from CO (AMO UNT)
Units from CO (UNITS)
INTNBCHA B channel of the real trunk number of the location that is not recording
INTNLIST Fictitious trunk number converted from INTNREAL (max. 6-digit, see
AMO FBTN)
A31003-H3170-S103-6-7620, 02/2019
Name Description
INTNREAL Real trunk number of the location that is not recording (see TKNOREAL,
5-digit)
Outgoing connection: A-station PEN or incoming circuit
Incoming connection: B-station PEN or outgoing circuit
Internal connection: same as private automatic branch exchange: B-
station PEN
Network-wide: A-station PEN or incoming circuit
INTNTRGR Trunk number group of INTNREAL (real trunk number of the location that
is not recording). If the location that is not recording is a telephone
instead of a trunk, this has the value 0 (5-digit)
KEYLV0 Node number of the key line used party, (3-digit)
KEYLV1 Subdomain number of the key line used party, (3-digit)
KEYLV2 Domain number of the key line used party, (2-digit)
KEYPTY Key line used party: the selected trunk (number) of a multi-trunk equipped
with a key phone (22-digit).
LCALLENO Length of the called number (called party), (2-digit)
LDESTNO Length of the destination number (2-digit). 
The dialed selection number can be transmitted to the DPA either in its
complete form or – for reasons of data protection – partly deleted; the
partial deletion can be done in two ways:
only the first n digits of the destination number are transmitted to the DPA
the last n (of the actually dialed) digits are deleted
You can use AMO SELG to select the method that you want to use.
LEGLV0 Node number of the leg id, (3-digit)
LEGLV1 Subdomain number of the leg ID, (3-digit)
LEGLV2 Domain number of the leg ID, (2-digit)
LEGSEQ Leg ID: If the destination station is changed in an existing connection, a
new leg ID is generated but the global call ID itself is not changed (8-
digit).
PINLEN Length of the personal ID (2-digit)
LISTTYPE Output of the type of the CDRS output format as text string, only CDRS
functionality (16 characters)
Individual call charge calculation (IND)
Partial call charge calculation (PART)
Total call charge calculation (TOTAL)
MOBUCLV0 Node number of mobile user calling party, (3-digit)
MOBUCLV1 Subdomain number of mobile user calling party, (3-digit)
MOBUCLV2 Domain number of mobile user calling party (2-digit)
MOBUCPTY Mobile user calling party: the user identifies himself/herself at the called
station with a PIN (22-digit)
MSGNO Message’s consecutive number of the S&F (Store & Forward) connection
(5-digit)
A31003-H3170-S103-6-7620, 02/2019
Name Description
NCT Flag that shows that a network call transfer (NCT) was successfully
performed. The transfer is done in the public network and all connections
over the OpenScape 4000 are released. Because of this, it is no longer
possible to record the accounting of call charges of the remaining call (1-
char)
NETCARA The trunk-related access code of the network carrier (related to the
BREAKIN trunk) (4-digit)
NETCARB The trunk-related access code of the network carrier (related to the
BREAKOUT trunk) (4-digit)
NETPULS Pulse: call detail information from the network (5-digit)
NETSVCA Service for a long-distance call carrier that supplies the PRI rate call (call
ends in the PBX); this service is used or requested for an incoming PRI
rate call (2-digit)
NETSVCB Service for a long-distance call carrier that supplies the PRI rate call (call
ends in the PBX); this service is used or requested for an outgoing PRI
rate call (2-digit)
NETTYPE Output of the network description as text string (10 characters)
- Analog network (ANA)
- Integrated Data Network (IDN)
- Integrated Service Data Network (ISDN)
ORIGIPA Originating IP Address of the call (15-digits)
OSAA Operator system access for incoming trunk connections (area 0-2) (1-
digit)
OSAB Operator system access for outgoing trunk connections (area 0-2) (1-
digit)
OUTDAY Date of the output: day of the year (1...366, 3-digit)
OUTDAYC Date of the output: name of the day (10-digit)
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
See also Example 2: before the start of the table.
OUTDAYN Date of the output: day (2-digit)
OUTHOUR Date of the output: hour (2-digit)
OUTMIN Date of the output: minute (2-digit)
OUTMONN Date of the output: month (2-digit)
A31003-H3170-S103-6-7620, 02/2019
Name Description
OUTMONC Date of the output: name of the month (10-digit)
January
February
March
April
May
June
July
August
September
October
November
December
OUTSEC Date of the output: second (2-digit)
OUTYEAR Date of the output: year (4-digit)
CHRGEE Paying party: connection’s party responsible for connection costs (22-
digit) (see In the fields for incoming calls are:).
Information on the right or left justified output field Section 60.5.2,
“CALLEPTY”.
PPLV0 Node number of the paying party, (3-digit)
PPLV1 Subdomain number of the paying party, (3-digit)
PPLV2 Domain number of the paying party, (2-digit)
PRECLEV Precedence level of the calling party, (2-digit)
QUEUEDUR Queuing duration: total delay time in the queue in 1/10 seconds (5-digit).
RECNO Consecutive number of the record to be output (1...9999, 4-digit) by
selection group.
The consecutive number is initialized to 1 for each dialog field
for ”Data transmission on demand”
or
for ”Restart” (also for ”RELOAD” or ”Power on”) and
is continually incremented for ”immediate output” (even after soft restart).
RECPT Record point (max. 1 digit)
Possible values:
0 = transit
1 = exit to trunk
2 = record directly at origin
3 = record directly at origin and exit to trunk
4 = incoming
RECTYPE Type of recording, either relating to the accounting of call charges or
traffic measurement or both (1-digit)
RING10 1/10 seconds part of the ring duration in the format minutes:seconds;1/
10 seconds (1-digit)
RINGDUR Total ring duration in format 1/10 seconds (5-digit) (see In the fields for
internal calls are:)
A31003-H3170-S103-6-7620, 02/2019
Name Description
RINGMIN Minute portion of the ring duration in format minutes:seconds;1/10
seconds (2-digit)
RINGSEC Second portion of the ring duration in the format minutes:seconds:1/10
seconds (2-digit)
ROUTCC Trunk group code as text string (10-digit), (see In the fields for incoming
calls are: and In the fields for internal calls are:)
You can use AMO TEXT to set up text strings for the different trunk group
codes, for example, ”BUSINESS ”, ”PRIVATE ” (each 10 characters
long).
ROUTCN Trunk group code (6-digit), (see In the fields for incoming calls are: and
In the fields for internal calls are:)
Instead of the actual trunk group code that is used for seizing the trunk or
tie trunk when setting up the connect (for external calls, the prefix "0"),
the customer can specify 2-digit numbers (see AMO RNKR). For
example, this allows you to use different codes to distinguish between
external calls for business or private purposes so that they can be billed
separately.
RTINGLV0 Node number of the redirecting party, (3-digit)
RTINGLV1 Subdomain number of the redirecting party, (3-digit)
RTINGLV2 Domain number of the redirecting party, (2-digit)
RTINGPTY Redirecting party: party that forwards a call (22-digit).
RTIONLV0 Node number of the redirection party, (3-digit)
RTIONLV1 Subdomain number of the redirection party, (3-digit)
RTIONLV2 Domain number of the redirection party, (2-digit)
RTIONPTY Redirection party: where a call is redirected to (22-digit).
RURAL Flag for pay phone call, (1-digit)
Possible values:
0 = pay phone
1 = other telephone
SELGRUNO Number of the selection group that created the CDR record (1-digit).
You can use AMO SELG (selection group administration) to put the
selection group together with different criteria
For example, the criteria could be:
the connection type (local and long-distance),
the entry of a user in a user list,
or
exceeding a limiting value for the time or cost.
By indicating the selection group number, all connections that meet all set
criteria of the chosen selection group are recorded.
SERVICE Output of the service as a text string (10-digit)
Voice connection (VOICE)
Facsimile (FAX)
Data terminal (DTE)
A31003-H3170-S103-6-7620, 02/2019
Name Description
SIDANI Text string referring to the calling party. The BREAKIN trunk provides the
SIDANI number, which refers to the calling party (24-digit)
SIGDATA Code indicating whether the output data record is correct, incorrect, or a
duplicate (10-digit).
imprecise or duplicated data record
correct data record
A data record is identified as imprecise if discrepancies are found while
processing the call detail data. For example, this could happen if the
connection was automatically restored after a OpenScape 4000 soft
restart and the number of call charge pulses and the call duration can not
be exactly determined.
SPEED Output of the transmission speed as a text string (10-digit)
No speed information
2400 baud
4800 baud
9600 baud
48000 baud (only for S0 link)
64000 baud (only for S0 link)
See the table Meaning of the Values for the Element SPEED in AMO
FTBL.
ST10 Connection start: 1/10 second (1-digit)
STDAY Connection start: day (2-digit)
STHOUR Connection start: hour (2-digit)
STMIN Connection start: minute (2-digit)
STMONTH Connection start: month (2-digit)
STSEC Connection start: second (2-digit)
STYDAY Connection start: day of the year (1...366, 3-digit)
STYEAR Connection start: year (4-digit)
STNID Output of the station identification as text string (10-digit), (see Note 1)
Attendant console
Main PBX tie trunk
Night server
Station
Service module (TCS)
Special call charge accounting
Maintenance equipment
Public telephone
Mobile user
External trunk number (keyset)
A31003-H3170-S103-6-7620, 02/2019
Name Description
SUPLSERV Output of the supplement service as a text string (10-digit)
Not defined
Normal call
Consultation call
Call transfer
Callback
Forwarding on busy station
Call forwarding
Call forwarding, no answer
Call pick-up
Conference call
Override
Hunt group
Mailbox
Radio paging (scroll)
Dictation
Credit card charge
Acceptance of reverse charges
Call redirection
Door opener
Ringing state
Hang up on hold
Hang up on hold in the attendant queue
Busy 
Removal from the attendant queue
Entry into the attendant queue
Transfer of a conference by the master
Automatic recall when transferring
Interruption by the attendant
Call forwarding to central attendant console
No CDR with eos 
CDR lost buffer 
Attendant (ATND) activating night service 
Attendant (ATND) deactivating night service 
Attendant (ATND) pulls out the plug (log off) 
Attendant (ATND) inserts plug (log on) 
Attendant (ATND) deactivated 
Attendant (ATND) restart 
Hang up on hold in the hunt group queue
A31003-H3170-S103-6-7620, 02/2019
Name Description
- Hunt group busy 
- Data record with SWU and ADP load 
- Passing the call through (transit)
- Call rerouting 
- Incoming call barred 
- Destination station deactivated 
- Resource unavailable 
- Call rejected 
- Non-allocated number 
- Account code 
- The chargeable convener is integrated in the conference
- The chargeable convener has left the conference
- A-station on hold 
- B-station on hold 
- A-station back from hold 
- B-station back from hold 
- A-station cradled on hold 
- B-station cradled on hold 
- Ringing after connected
SVCDOM Service Domain of the calling party, (19-digit),
SWP Partial switching procedures (10-digit)
- No switching procedure (EMPTY)
- Section after section (SECASEC)
- Section after account code (SECACC) 
- Section after seizure (SECS)
- Section after limit value (SECL)
- End of call after section (ENDSEC)
- End of call after seizure (ENDS)
- End of call after limiting value (ENDL)
- Limit after section (LASEC)
- Limit after seizure (LAS)
- Limit after first limit (LAL)
Explanation:
The values two to ten arise as possible combinations of the events at the
beginning and end of the time frame to which the CDR record refers. The
following events are considered:
Seizure of a line
Beginning a data record
Section, change of the party responsible for connection costs
(for example, transferring the connection)
Closing up the old data record and starting a new one
Limiting value exceeded for call charge pulses or time
Closing up the old data record and starting a new one
End-of-connection
Closing up the data record
The last of the values given above identifies a section for chained fax
messages.
A31003-H3170-S103-6-7620, 02/2019
Name Description
SWULOAD SWU processor load in 1/10 percent. This is an average value over 10
seconds (4-digit). The time stamp indicating when the load was
measured is in the field "Start of the connection"->STDAY(2-digit),
STMONTH(2-digit), STHOUR(2-digit), STMIN(2-digit), STSEC(2-
digit),ST10(1-digit)
TERMIPA Terminating IP Address of the call (15-digit)
THRELV0 Node number of the global thread ID (3-digit), identical to GLOBLV0
THRELV1 Subdomain number of the global thread ID (3-digit), identical to
GLOBLV1
THRELV2 Domain number of the global thread ID (2-digit), identical to GLOBLV2
THRESEQ Sequence number of the global thread ID (8-digit), identical to GLOBSEQ
TKNOBCHA B channel of the real trunk number of the recording point.
TKNOTRGR Trunk number group of TKNOREAL (real trunk number of the recording
point). If the recording point is a telephone, 0 (zero) is output instead of a
trunk (2-digit)
TKNOLIST Fictitious circuit number, converted from TKNOREAL (Trunk no. list, 6-
digit)
The real circuit number (board number) is depicted on a fictitious circuit
number specifically for this customer with the help of a table. You can
customize this table with AMO FBTN (administration of the flat byte and
trunk number table).
TKNOREAL Real trunk number of the recording point (trunk no. real, 5-digit):
Outgoing connection: outgoing circuit
Incoming connection: incoming circuit
Internal connection: same private automatic branch exchange: A-station
PEN
Internal connection: network-wide: outgoing circuit
TRNSFLV0 Node number of transferring party, (3-digit)
TRNSFLV1 Subdomain number of the transferring party, (3-digit)
TRNSFLV2 Domain number of the transferring party, (2-digit)
TRNSFPTY Transferring party: party that transfers a call (22-digit).
Information on the right or left justified output field (see Section 60.5.2,
“CALLEPTY”).
TRANSCNT Number of transit nodes passed through (2-digit max.)
UNANS through connect/ no through connect (10-digit)
Through connection (THRCONN)
Non-through connection (NTHRCONN)
UNITERAS Output whether CDRS call charge totals are deleted after being output as
text string, only CDRS functionality (22-digit).
Difference counter deleted or through-connected
Difference counter not deleted or not through-connected
A31003-H3170-S103-6-7620, 02/2019
Name Description
PIN Personal ID (max. 12-digits)
ZONE Output of the distance zone as a text string (10-digit, see In the fields for
incoming calls are: and In the fields for internal calls are:)
1st incoming zone (INC01)
n-th incoming zone (INCnn)
9th incoming zone (INC09)
1st abroad (ABROAD01)
n-th abroad (ABROADnn)
99th abroad (ABROAD99)
1st distance (LONG01)
n-th distance (LONGnn)
50th distance (LONG50)
No charge (NOCHRG)
Call detail information from carrier (CHRGINFO)
1st internal zone (INT01)
n-th internal zone (INTnn)
9th internal zone (INT09)
Empty entry (EMPTY)
Short zone (SHORT)
Local Zone (LOCAL)
1st zone for tie trunks (TIE01)
n-th zone for tie trunks (TIEnn)
9th zone for tie trunks (TIE09)
Remarks:
1. In the fields for incoming calls are:
ATNDGRNO = Group number of the attendant console that answered and

forwarded this call
CARRIER = a carrier that can be allocated to an incoming trunk group (AMO
TACSU / TDCSU)
CHOFCON = always "LONG"
CONNTYPE = "INCOMING"
ROUTCC = empty (fill character)
ROUTCN = empty (fill character)
STNID = station identification of the called station
ZONE = a zone INC01 - INC09 that can be allocated to an incoming trunk
group (AMO TACSU / TDCSU)
2. In the fields for internal calls are:
CARRIER = always "0"

CHRGUNIT = empty (fill character)
CONNTYPE = "INTERN"
CHOFCON = always "LOCAL"
A31003-H3170-S103-6-7620, 02/2019
List of the Record Identifiers
ROUTCN = empty (fill character)

ROUTCC = empty (fill character)
RINGDUR = "0" for ZAND parameter CDRRINGB = NO (AMO ZAND)
ZONE = zone INT01 - INT09 determined from the ITR group (AMO
VBZGR)
60.6 List of the Record Identifiers

Key:
ALL llBridge/ACL description „General“

ECCS CallBridge/ACL description „DVA-Controlled Connection setup ECCS“
GÜ CallBridge/ACL description „Call detail Transmission GÜ“
TDS CallBridge/ACL description „Telephone Data Service TDS“
RID Vol. Chap. Description

A0 GÜ 3.3.1 Send CDR information
3.3.7 Heartbeat
A1 GÜ 3.3.4 Receive CDR information
AA GÜ 3.3.2 Start of the transfer block by job
AB GÜ 3.3.2 Retrieve call charge records after query
AC GÜ 3.3.3 Transfer OK
AD GÜ 3.3.3 Transfer failed
3.3.7 Verification of connection
AF GÜ 3.3.5 Block start for immediate transmission
AH GÜ 3.3.2 Request for pickup of call charge records
AI GÜ 3.3.2 Retrieve call charge records for immediate transmission
B0 ALL 4.1.2.5 Format of the blocked ACL message
B1 ALL 4.1.2.4 Format of the blocked ACL message
BA ALL 4.1.2.5 Acknowledge B0
C0 ECCS 3.1.3.1 Monitoring, control feature
C1 ECCS 3.1.3.1 Telephone detection
C2 ALL 4.1 Activate or deactivate block mode
ECCS 3.1.3.1 Load measurement
C3 ECCS 3.1.3.1 Bit string
C4 ECCS 3.1.3.1 Query application number
C4 DGV 3.1.3.1 Applikationsnummer abfragen
Table 47 List of the record identifiers (RID)
A31003-H3170-S103-6-7620, 02/2019

CA ECCS *) Acknowledge C0
CB ALL *) Acknowledge C1
CC ECCS *) Acknowledge C2
CD ECCS *) Acknowledge C3
CE ECCS *) Acknowledge C4
CE DGV *) Quittung auf C4
E0 TDS 3.2.3 Data output format for DIGITEfür DIGITE
3.2.7 Acoustic signaling format for ANATE
3.2.7 Format der akustischen Signalisierung bei ANATE
E1 TDS 3.2.4 Verification of connection format
EA TDS 3.2.3 Acknowledge E0
3.2.5 TDS status message
3.2.6 Format of data input with function keys
3.2.8 Data message from OpenScape 4000 to application
EB TDS 3.2.4 Acknowledge E1
F0 ALL 5.2.1 Application gateway
FA ALL 5.2.2 Acknowledge F0
F0 ALL 5.2.1 Applikationsgateway
FA ALL 5.2.2 Quittung auf F0
G0 ECCS 3.1.3.1 Call processing functions
G1 ECCS 3.1.3.1 Key string functions, simulation of call charge pulses,
Gebührenimpulssimulation
GA ECCS *) Acknowledge G0
GB ECCS *) Acknowledge G1
P0 ECCS 3.1.3.1 Snapshot monitoring
P1 ECCS 3.1.3.1 Query of the call queue status
PR ECCS *) Acknowledge P0
PQ ECCS *) Acknowledge P1
PA ECCS 5.1 Connection Event Message (CEM)
PB ECCS 5.1.5.2 PB message, continuation of the CEM
PE ECCS 5.1.6.2 PE message
PL ECCS 5.1.7.2 Process load status
PB DGV 5.1.5.2 PB-Meldung, Fortsetzen der VEM
PE DGV 5.1.6.2 PE-Meldung
PL DGV 5.1.7.2 Zustand der Prozessorlast
R0 ECCS 3.1.3.1 Sample station status
RJ ECCS *) Acknowledge R0
A31003-H3170-S103-6-7620, 02/2019

T0 ALL 6.2.3.1 Message transfer prompt
T1 ALL 6.2.1.1 Connection setup
6.2.2.1 Connection setup
TA ALL 6.2.4 Transfer message received
TB ALL *) Acknowledge for T1
TX ALL 6.2.3.2 Message transfer prompt
T0 ALL 6.2.3.1 Meldungstransferaufforderung
T1 ALL 6.2.1.1 Verbindungsaufbau
6.2.2.1 Verbindungsabbau
TA ALL 6.2.4 Transfermeldung empfangen
TB ALL *) Quittung auf T1
TX ALL 6.2.3.2 Meldungstransferaufforderung
XA ALL 4.2 Overload
ECCS 3.3 Syntax error
XB ALL 4.1.2.5 Error in block format
XC ECCS 3.3 Invalid message length
W1 GÜ 3.3.6 Request for immediate pickup of call charge records

*) See the section for the corresponding order code
A31003-H3170-S103-6-7620, 02/2019
A31003-H3170-S103-6-7620, 02/2019
cdr_basics_gesp.fm
Call Charge Display Parameters in AMO COT and AMO COSSU
61 Call Detail Information for Heterogeneous Networks
61.1 Call Charge Display Parameters in AMO COT and AMO COSSU
You can activate and deactivate the Advice of Charge (AOC) messages sent over
the tie trunk with the CDRSTN/CDRD parameter in the AMOs COS and COT.
• If the CDRD parameter is set in the tie trunk’s AMO COT, the system checks
if the CDRSTN parameter is also set in the tie trunk’s AMO COS.
• If the CDRD/CDRSTN parameter is set in the tie trunk’s AMOs COT and
COS, AOC messages are sent over the tie trunk.
• If the CDRD parameter is set in AMO COT but CDRSTN is not set in the AMO
COS, no AOC messages are sent over the tie trunk, even if the call charge
display class of service is set in the AMO COS for the terminal device.
• If the CDRD parameter is not set in the tie trunk’s AMO COT, the CDRSTN
parameter in the tie trunk’s AMO COS is not checked. AOC messages are
only sent over the tie trunk for terminal devices that have the CDRSTN
parameter set in the AMO COS.
• If the CDRD parameter is set in the tie trunk’s AMO COT, the tie trunk’s AMO
COS is checked to see if the CDRSTN parameter is also set there.
CDRD in CDRSTN in
AMO COT AMO
COSSU
No Not relevant The CDRSTN parameter in the tie trunk’s AMO COS is not
checked. AOC messages are only sent over the tie trunk for
terminal devices that have the CDRSTN parameter set in
their COS.
Yes No Do not send any AOC messages over the tie trunk, even if
the CDRSTN parameter is set in the AMO COS for the
terminal device.
Yes Yes Send AOC messages over the tie trunk.
Table 48 CDRD/CDRSTN in AMOs COT and COSSU
A31003-H3170-S103-6-7620, 02/2019
cdr_basics_gesp.fm
Charge-Related COT Parameters
61.2 Charge-Related COT Parameters
61.2.1 AOCC
The AOCC parameter must always be set for CORNET-NQ tie trunks. Otherwise
no Advice of Charge (AOC) messages are sent over the tie trunk.
The COT parameter AOCC must also be set for QSIG and ETSI connections to
external systems, but only if the trunk also understands the Advice of
Charge request. Clarify this beforehand with the external manufacturer.
If the COT parameter AOCC is set but the trunk does not understand the AOC
request, the AOC class of service is suppressed. All AOC messages that are
received will be discarded.
More information you can find in section “INCDR - Feature Usage Examples and
COT Parameters, Chapter 262, “AOCC - Request charges per line for remote
station”.
61.2.2 IICB
If the parameter IICB is set, billing elements that are received are discarded.
COT Parameters, Chapter 272, “IICB - Ignore incoming billing information
element”.
61.2.3 SNBE
If the parameter SNBE is set, no billing elements are sent.
COT Parameters, Chapter 276, “SNBE - Send no billing element to the partner
system”.
61.2.4 IGID
If the parameter IGID is set, incoming call IDs are discarded. This is optional and
should be used in carrier networks.
Note: This is a mandatory parameter for carriers.
A31003-H3170-S103-6-7620, 02/2019
cdr_basics_gesp.fm
Charge-Related COT Parameters
61.2.5 TRSC
The line sends charge amounts to the originating node (valid for INCDR).
If the parameter TRSC is not set, units are reported to the originating node.
COT Parameters, Chapter 277, “TRSC - Trunk sends call charges to source
node”.
61.2.6 DPRE
If the parameter DPRE is set, the dialing information that was actually transmitted
(including, for example, prefix digits, AMO LODR, OUTPULSE) is passed along
to the call detail recording function.
COT Parameters, Chapter 268, “DPRE - Send dial information actually sent to
partner system as destination number with prefix digits to call data recording”.
61.2.7 ICZO and ICZL

You can use the parameter ICZO to activate incoming call detail recording per
trunk.
You can use the parameter ICZL to activate incoming call detail recording by zone
and line.
The parameters ICZL and ICZO are mutually exclusive.
When transferring the connection of a call from the ATND to the station and from
the secretary to the executive station, a separate CDR record is created for each
call section.
IMPORTANT: The AMO GEFE indicates whether the ATND or the secretary
must pay for their call section themselves.
The GEFE parameter ATTNDINC defines whether the ATND or the secretary
is chargeable for incoming connections.
The GEFE parameter ATTNDOUT defines whether the ATND or the secretary
is chargeable for outgoing connections.
COT Parameters, Chapter 271, “ICZO - Incoming call data recording by zone
only” and Chapter 270, “ICZL - Incoming call data recording by zone or from line”.
A31003-H3170-S103-6-7620, 02/2019
cdr_basics_gesp.fm
Charge-Related TDCSU Parameters
61.2.8 CCTN
The parameter CCTN in the AMO COT of an analog circuit causes the telephone
number that is entered as the calling party in the circuit number field (CCT) to be
reported to the call detail recording function.
COT Parameters, Chapter 264, “CCTN - Apply trunk number as A number”.
61.2.9 DFNN and LWNC on Tie Trunks to an

Expression 450
Neither the COT parameter DFNN nor LWNC may be set for the circuit to the XPR
because otherwise the paying party would be provided with the wrong account
number (with the number of the tie trunk to the XPR).
A dialing analysis is made in the OpenScape 4000 with the calling party that the
OpenScape 4000 receives from the XPR. Then the node number from the RICHT
entry is established and, along with the calling party, is reported to the call detail
recording function. In this way, the paying party (the calling party) is clearly
identified.
COT Parameters, Chapter 273, “LWNC - Line protocol without node number” and
Chapter 267, “DFNN - Use default node number for trunk as a dummy source
node number”.
61.3 Charge-Related TDCSU Parameters
61.3.1 ZONE
The parameter ZONE is read out of the AMO VBZGR branch CHRGINC. The ITR
group of the incoming circuit determines the zone, depending on the ITR group
of the destination.
The ZONE parameter includes the distance zone for charges based on time.
For the purpose of calculating costs for incoming connections, the line circuits can
be allocated cost parameters that are made up of CARRIER and ZONE. You must
use AMO TTBL to parameterize CARRIER and ZONE, which always work in
combination. The empty zone, for which no charges are incurred according to
time, is assigned by default.
A31003-H3170-S103-6-7620, 02/2019
cdr_basics_gesp.fm
Charge-Related FEASU Parameters
61.4 Charge-Related FEASU Parameters
61.4.1 DISCHNW and CDROGNW

The AMO FEASU also automatically sets the parameter CDROGNW when the
parameter DISCHNW is set.
61.5 Charge-Related LDAT Parameters
61.5.1 LATTR Parameter NOCHDISP

Setting the LATTR parameter NOCHDISP causes the charge display for the
terminal device to be suppressed.
However, this does not cause the connection to be marked as expensive in the
CDR record EXPENS field of AMO FTBL.
A connection is recorded in the CDR record in the EXPENS field only if it is

identified as expensive by the parameter LSCHED in AMO LDAT.
A31003-H3170-S103-6-7620, 02/2019
cdr_basics_gesp.fm
Charge-Related LDAT Parameters
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
CDRe - Call Detail Recording enhanced
Internal and network-wide call detail recording (INCDR) - Usage Examples
Internal and network-wide call detail recording (INCDR) -

Usage Examples
62 CDRe - Call Detail Recording enhanced
62.1 Specification
The "CDRe" feature broadens the scope of call data recording and generates not
only call detail records but also, and more importantly, call data records. These
call data records are transferred for further processing.
The goal of this feature is to cover as many CDRe changes as possible on the
basis of the extended variety of requirements in OpenScape 4000. Because of
their complexity, however, CDRe Traffic , CDR Account Code, and Elapsed Time
Display are handled separately.
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
Description
external
internal
• Introduction of a variable cost unit concept (not for

internal connections) The data evaluation
for call traffic
• Introduction of fields in the CDR record for call detail measurement and call
recording data recording is
performed on an
• Recording of all activities at the terminal using CDRe
external processor.
• Call tracing by implementation of the call sequence
number
• Without CDRe call charge recording remains basically

unchanged
62.2 Description
Originally, CDR (Call Detail Recording) was used to assign call charges to a
station. For this purpose, various call details are output in a flexible format. These
CDR records can then be transferred for further processing.
This principle had been enhanced. Call charge recording is enhanced by the
feature "CDRe". This means, that not just call charges are recorded but also all
call details. These records are then transferred for further processing. They are
also used to measure the effectiveness of call handling and performance They
are also used to measure the effectiveness of call handling and performance.
For a Call Management System (CMS) to be able to generate useful information,

each destination change must generate a separate call data record. CDRe can
be deactivated if these records are not required.
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
Modified Cost Unit Assignment Concept
To facilitate the evaluation of the call data records with regard to effectiveness and
performance, additional information fields are recorded in the OpenScape 4000;
these are available for output in the data record.
In addition to the various numbers associated with the connection, the time a
connection waits in the queue is now recorded for attendant consoles.
62.3 Modified Cost Unit Assignment Concept

Cost unit assignment can be administered for a connection.
In addition to the internal rules, situations can now be defined where a different
cost unit is assigned to a connection which deviates from the internal rules. The
user-defined rules override the internal rules. If in a call-processing situation both
the internal and the user-defined rules could be applied, the cost unit is assigned
according to the user-defined rule. This also allows the complete re-definition of
internal rules.
The internal rules can also be displayed to make the entire set of rules easier to
understand.
62.4 Special Features

• Data is always entered in the Paying_Party, Calling_Party, and
Destination_Party fields in the charge detail record. In contrast, the
Called_Party field is not always supplied with data. Data is entered in the
Transferring-Party field in the event of call transfer. The Mobile_User_Calling
and Key_Line_Used CM (PIN /KEY system) fields are feature-dependent.
• If CDRE is active, the entries for cost distribution on the AC and for 
CHESEs in the AMO GEFE are ignored. A separate CDB is generated for
each call segment.
• When CDRE is active, the off-hook signal starts the call detail recording
irrespective of the entry in ZAND (answer or end of dial).
• The AMO DEFPP is only applicable to an incoming and outgoing connection.

The entries are ignored for an internal connection.
• A customer-specific calling number should be entered for each trunk or

attendant in the AMO TLZO. If you do not enter this number, a default calling
number (999999) is entered in the record.
• In the AMO KNMAT, MODCON parameter entries are ignored for the virtual
node number CDR.
• The COT parameter AOCC:
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
User Interface
• should always be set in systems with V2.0 or later with Cornet NQ,
ECMA, and QSIG.
• in external systems with ECMA/QSIG should be checked to ensure that

the parameter is interpreted correctly in the remote system. Display
information is lost in the event of incorrect interpretation.
• should be set if you want charge information to be sent to the connected

system.
• must not be set for other protocols, such as, DSS1, DPNSS, and DASS
because the remote system cannot work with the protocol messages that
this would generate, which could result in the OpenScape 4000
incorrectly turning off the display information.
• The COT parameter ICZO only activates the incoming call detail recording on
the trunk.
• The ICZL has no function at this time because no carrier currently sends
charge information for incoming calls.
• In the AMO PERSI, COPIN specifies which calling number is sent to the call
detail recording module during identification (station or mobile).
62.5 User Interface

Most changes to the user interface result from the consolidation of the US call
detail recording and IM CDRe.

No special requirements.
62.7 AMOs
62.7.1 Enabling and Disabling Call Data Recording

Enhancements
• CDR-e is enabled as follows:
CHANGE-FEASU:TYPE=A,CM=CDRE;
• CDR-e is disabled as follows:
CHANGE-FEASU:TYPE=D,CM=CDRE;
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
62.7.2 Important Fields in the Call Detail Record

• Output the connection’s cost unit with node and number:
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,
FORMAT="COST UNIT: #@-#@-#@@@ #@@@@@@@@"; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=CTRL,NO=2,END=N,CTLCHARS=CR;
ADD-FTBL:FORMNO=4,TYPE=B,TBL=CTRL,NO=3,END=N,CTLCHARS=LF;
ADD-FTBL:FORMNO=4,TYPE=B,TBL=CTRL,NO=5,END=Y,CTLCHARS=LF;
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=PPLV0
,FILLTYPE=CHAR,FILLER=" ",FLDALIGN=L; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=CHRGEE
,FILLTYPE=CHAR,FILLER=" ",FLDALIGN=L;
• Output the calling party with node and number
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N
,FORMAT="CALLER: #@-#@-#@@@ #@@@@@@@@";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=CTRL,NO=2,END=N,CTLCHARS=CR; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=CTRL,NO=3,END=N,CTLCHARS=LF; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=CTRL,NO=5,END=Y,CTLCHARS=LF; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=CALLILV0
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=CALLIPTY
• Output the dialed number and length of the number
,FORMAT="DIALED: #@@@@@@@@ NO. LENGTH: #@@"; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=CALLEPTY
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=LCALLENO
,FILLTYPE=CHAR,FILLER=" ",FLDALIGN=R;
• Output the connection’s current destination with node and number and its
length:
,FORMAT="DESTINATION: #@-#@-#@@@ #@@@@@@@@ NO.
LENGTH: #@@"; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=DESTLV0
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=DESTPTY
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=5,FLDNAME=LDESTNO
• Output the forwarding party of a forwarded connection with node and number:
,FORMAT="FORWARDER: #@-#@-#@@@#@@@@@@@@"; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=RTINGLV0
,FILLTYPE=CHAR,FILLER=" ",FLDALIGN=L;
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=RTINGPTY
• Output the forwarding destination of a forwarded connection with node and
number:
,FORMAT="FORWARDING DESTINATION: #@-#@-#@@@
#@@@@@@@@";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=RTIONLV0
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=RTIONPTY
• Output the connected user of a transferred connection with node and number:
,FORMAT="TRANSFERRING PARTY: #@-#@-#@@@ #@@@@@@@@"; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=TRNSFLV0
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=TRNSFPTY
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
• Output a home station of a number identified with a PIN, with node and
number
,FORMAT="TRANSFERRED: #@-#@-#@@@ #@@@@@@@@";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=MOBUCLV0
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=MOBUCPTY
• Output the number assigned to the keyline used, with node and number
,FORMAT="KEYLINE: #@-#@-#@@@ #@@@@@@@@";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=KEYLV0
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=KEYPTY
• Output the call ID and the number of the CDB record:
,FORMAT="CALL ID: #@-#@-#@@@/#@@@@@@@@, #@-#@-#@@@/
#@@@@@@@@";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=2,END=N,FORMAT="COUNTER:
#@@@";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=GLOBLV0
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=GLOBSEQ
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=5,FLDNAME=LEGLV0
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=8,FLDNAME=LEGSEQ
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=9,FLDNAME=CONNSTEP
• Output the wait time (1/10 seconds) in an AC’s queue:
,FORMAT="WAIT TIME: #@@@@@"; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=QUEUEDUR
• Output the account code (ACCTCODE):
,FORMAT="ACCTCODE: #@@@@@@@@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=ACCTCODE,FILL
TYPE=CHAR
,FILLER=" ",FLDALIGN=L;
• Output the ADP processor load (ADPLOAD):
,FORMAT="ADP-TIME: #@:#@,#@'#@ #@-#@-#@@@ ADP-
LOAD: #@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=ENDHOUR,FILLT
YPE=CHAR
,FILLER=" ",FLDALIGN=L; 
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=ENDMIN,FILLTY
PE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=3,FLDNAME=ENDSEC,FILLTY
PE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=END10,FILLTYP
E=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=ENDDAY,FILLTY
PE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=ENDMONTH,FILL
TYPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=3,FLDNAME=ENDYEAR,FILLT
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
YPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=ADPLOAD,FILLT
YPE=CHAR
• Output the SWU processor load (SWULOAD):
,FORMAT="SWU-TIME: #@:#@,#@'#@ #@-#@-#@@@ SWU-
LOAD: #@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=STHOUR,FILLTY
PE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=STMIN,FILLTYP
E=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=3,FLDNAME=STSEC,FILLTYP
E=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=ST10,FILLTYPE
=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=STDAY,FILLTYP
E=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=STMONTH,FILLT
YPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=3,FLDNAME=STYEAR,FILLTY
PE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=SWULOAD,FILLT
YPE=CHAR
• Output the calling party ID (CALLIID):
,FORMAT="CALLIID: #@@@@@@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=CALLIID,FILLT
YPE=CHAR
• Output the destination party ID (DESTPID):
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
,FORMAT="DEST-ID: #@@@@@@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=DESTPID,FILLT
YPE=CHAR
• Output the connection type (CONNTYPE):
,FORMAT="CONNTYPE: #@@@@@@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=CONNTYPE,FILL
TYPE=CHAR
• Output the text string relating to the dialed number (DNIS):
,FORMAT="DNIS: #@@@@@@@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=DNIS,FILLTYPE
=CHAR
• Output the text string relating to the calling number (SIDANI):
,FORMAT="SIDANI: #@@@@@@@@@@@@@@@@@@@@@@@";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=SIDANI
• Output the values for FX trunk access on the A side (FACA):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="FACA:
#@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=FACA,FILLTYPE
=CHAR
• Output the values for FX trunk access on the B side (FACB):
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="FACB:
#@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=FACB,FILLTYPE
=CHAR
• Output the global leg ID node number (GLOBLLV0):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="GLOBAL
LV0: #@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=GLOBLLV0,FILL
TYPE=CHAR
• Output the global leg ID subdomain number (GLOBLLV1):
LV1: #@";
ADD-
TYPE=CHAR
• Output the global leg ID domain number (GLOBLLV2):
LV2: #@";
ADD-
TYPE=CHAR
• Output the global leg ID sequence number (GLOBLSEQ):
,FORMAT="GLOB SEQ: #@@@@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=GLOBLSEQ,FILL
TYPE=CHAR
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
• Output the global thread ID node number (THRELV0):

ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="THREAD
LV0: #@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=THRELV0,FILLT
YPE=CHAR
• Output the global thread ID subdomain number (THRELV1):
LV1: #@";
ADD-
YPE=CHAR
• Output the global thread ID domain number (THRELV2):
LV2: #@";
ADD-
YPE=CHAR
• Output the global thread ID sequence number (THRESEQ):
,FORMAT="THREAD SEQ: #@@@@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=THRESEQ,FILLT
YPE=CHAR
• Output the entire hold duration (HOLDDUR):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="HOLDDUR:
#@@@";
ADD-
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=HOLDDUR,FILLT
YPE=CHAR
• Output the trunk number group of the non-recording point (INTNTRGR):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="PTRK-
GRP: #@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=INTNTRGR,FILL
TYPE=CHAR
• Output the trunk number group of the recording point (TKNOTRGR):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="TRK-GRP:
#@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=TKNOTRGR,FILL
TYPE=CHAR
• Output network call transfer (NCT):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="NCT: #";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=NCT,FILLTYPE=
CHAR
• Output the A party network carrier (NETCARA):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="NETCARA:
#@@@@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=NETCARA,FILLT
YPE=CHAR
• Output the B party network carrier (NETCARB):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="NETCARB:
#@@@@";
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=NETCARB,FILLT
YPE=CHAR
• Output the A party network service (NETSVCA):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="NETSVCA:
#@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=NETSVCA,FILLT
YPE=CHAR
• Output the B party network service (NETSVCB):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="NETSVCB:
#@";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=NETSVCB,FILLT
YPE=CHAR
• Output operator system access A (OSAA):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="OSAA:
#";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=OSAA,FILLTYPE
=CHAR
• Output operator system access B (OSAB):
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END=N,FORMAT="OSAB:
#";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=OSAB,FILLTYPE
=CHAR
• Output the record type (RECTYPE):
,FORMAT="RECTYPE: #@@@@@@@@@";
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=RECTYPE,FILLT
YPE=CHAR
• Filters in the AMO SELG
RECTYPE indicates relevance for PM and/or CDRE.
CONNTYP can be used to filter according to ACACT/LOAD/ALL, depending
on the requirements.
SERVICE now only supports VOICE, FAX, and DTE.
• Conversion of numerical values into texts with the AMO TEXT

SERVICE, SWP, CONNTYP, and SUPLSERV have been changed.
62.7.3 Modified Cost Unit Assignment Concept

Standard behavior, that is, the system should behave as usual with regard to
cost unit assignment:
Normal system behavior. No configuration data is necessary.
Reset all entries and restore the standard behavior with regard to cost unit
assignment:
DELETE-DEFPP:ALL;
62.7.4 Processing Sequence for Entries in DEFPP
Changes possible by system administrator
User-defined entries
no entry
System-wide special entries

Changes only possible by Development
System-wide standard entries

No change possible
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
Configuring special rules for callback

If a callback is entered in the requested called party’s mailbox and the mailbox
owner activates the callback, the charges are normally assigned to the mailbox
owner as the cost unit. For connections over tie trunks, the originator of the
connection can be defined as the cost unit:
ADD-DEFPP:CONNTYPE=OUTGO,SUPLSERV=CALLBACK,CHRGEE1=CONNECT;
NOTE: Attention! For normal callback connections over tie trunks without a
mailbox, cost unit assignment is reversed with the result that the called party
becomes the cost unit.
Configuring special rules for conditional and unconditional call forwarding

If the central office forwards a call several times, the charges are normally
assigned to the original called party who initiated the first call forwarding action.
In the case of connections that are forwarded several times and then finally to the
central office, the charges are assigned to the station that initiated forwarding to
central office. The following settings are necessary either if the charges for
connections from the central office are to be assigned to the actual party reached
or if the charges for connections to the central office are to be assigned to the
initiator of the connection:
ADD-DEFPP:CONNTYPE=OUTGO,SUPLSERV=CALLFOR,CHRGEE1=CALLING;
ADD-DEFPP:CONNTYPE=INCO,SUPLSERV=CALLFOR,CHRGEE1=CONNECT;
Configuring special rules for a hunt group

A hunting group is normally reached via the hunting group station number. The
charges are assigned to the hunting group member who answers the call. The
following setting is necessary, if the charges are to be assigned to the hunting
group station number:
ADD-DEFPP:CONNTYPE=INCO,SUPLSERV=HUNTGRP,CHRGEE1=CALLED;
Configuring special rules for override

An override connection is always an internal connection. Administration of charge
assignment is not possible for internal connections.
Configuring special rules for call pickup

Normally, the charges are assigned to the station that picks up a trunk call. It is,
however, possible to define the originally called party as the cost unit:
ADD-DEFPP:CONNTYPE=INCO,SUPLSERV=PICKUP,CHRGEE1=CALLED;
Configuring special rules for call transfer

Normally, the charges accrued during call transfer are assigned to the internal
station (or the held party, if all stations are internal). The following settings are
necessary if the charges for an extended connection are to be assigned to the
extending party:
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
ADD-DEFPP:CONNTYPE=OUTGO,SUPLSERV=TRANSFER,CHRGEE1=TRANSPTY;
ADD-DEFPP:CONNTYPE=INCO,SUPLSERV=TRANSFER,CHRGEE1=TRANSPTY;
62.7.5 Changes in the AMO GEFE

This is where you specify whether the attendant or secretary are assigned their
own charges or if the charges are passed on to the other party. This can be set
independently for incoming and outgoing connections.
COSTDUTY OF ATTENDANT / SECRETARY INCOMING : NO

OUTCOMING : NO
If two outgoing calls are connected to each other, this parameter allows or blocks
a possible change to the connection direction of one of these two calls (in this
case, from "outgoing" to "incoming").
CHANGE OF CALL DIRECTION IN TICKET SEQUENZ : YES
The parameter shows renewed ringing for a call that was already put through. In
this case, SupplService is changed to Ring_after_connect.
NEW RINGING, THROUGH CONN. CALL IN RINGDUR : NO
The parameter allows the queuing duration to be output without enabling the
CDRE feature.
OUTPUT OF QUEUE_DUR WITHOUT ACTIVATION OF CDRE : YES
A user identified as "confidential" is suppressed in the CALLIPTY output field

(AMO FTBL). This user is usually also the paying party (as Calling). This
parameter can be used to allow or block the output of this confidential user in the
PayingParty field.
SHOW RESTRICTED SUBSCRIBER IN PAYINGPARTY : NO
You can also specify whether the destination number should be shortened by two
digits.
DESTINATION NUMBER SHORTENED BY 2 DIGITS : NO
Should a new ticket and therefore a new call detail record be generated if the
other party involved in the call with the paying party (PP) changes because of
forwarding or similar.
TICKET BY SAME PP : YES
Call charge units received by the carrier are entered in the field Field CHUNIT. If
YES is set, the call charge information from the CO is entered in NETPULS while
internally calculated call charge data is entered in CHUNIT.
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
OFFICIAL UNITS ARE SAVED IN CDB : YES
With incoming call detail recording, the called party is entered as the paying party.
This is not always correct. This parameter changes the calling party into the called
party.
INCOMING CALLING IN THE FIELD OF CALLING : NO
Information for AOCs

AOC-S COST CALCULATION CONFIGURATION 
THROUGH CONNECTED 
BASIC COMM : YES
CALL ATTEMPT : NO
CALL SETUP : YES
UUI : NO
OP. OF. SS. : NO (Basic charge for special
services)
NON THROUGH CONNECTED 
BASIC COMM : YES
CALL ATTEMPT : YES
CALL SETUP : NO
UUI : NO
OP. OF. SS. : NO (Basic charge for special
services)
• Use KNMAT to make changes

NODE ID HANDLING
INTERNAL : NO
INCOMING : NO
OUTGOING : NO
• In an E164 numbering plan, the prefix is added to the station number

PREFIX HANDLING OF STATION
INTERNAL : NO
INCOMING : NO
OUTGOING : NO
CARRIER TYPE OF CALL DETAIL REC. AT

METHODS FOR 
CALL DETAIL REC. CONNECTION END NORM SPEC
PUBL OPER
0 MIX NO 0 0
0 0
1 MIX NO 0 0
0 0
2 MIX NO 0 0
0 0
3 MIX NO 0 0
0 0
4 MIX NO 0 0
0 0
5 MIX NO 0 0
0 0
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
6 MIX NO 0 0
0 0
7 MIX NO 0 0
0 0
8 MIX NO 0 0
0 0
9 MIX NO 0 0
0 0
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_en.fm
AMOs
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdre_traffic_en.fm
Feature Description
63 Call Detail Recording enhanced Traffic

The goal of this performance feature is to generate additional CDR records in
order to allow a call traffic management application to create certain statistics.
These additional records are based on CDRe.
63.2 User Interface

Starting and stopping measurement:
The measurement is started/stopped via the AMO DEFTM.
Additional records for the call traffic measurement are only created when the
measurement has been started, i.e. when the tag is set. In all other cases, only
normal "charging relevant" tickets are created.
Filter function on the basis of the call traffic measurement table:

A list of the objects to be measured can be defined ("ALL" is likewise possible,
and results in the entire traffic being recorded).
When call traffic measurement is started, only records with a relationship to

objects in the call traffic measurement table are generated. In this check, the
fields for calling party (i.e. FTBL-field CALLIPTY), connected party (or called party
if connected party is not available) (DESTPTY field in FTBL), TRUNK number and
PARTNER TRUNK number are compared with the entries in the call traffic
measurement table. If at least one of these objects exists in the call traffic
measurement table, the record is labelled as "relevant for call traffic
measurement" (in the "Record Type" field).
A distinction is made between the following cases:
• Normal stations (likewise secretary and executive) are checked against the
station list.
• Attendant console and night service are checked against the AC list.
Furthermore, the attendant console group is checked against the entries in
the attendant console group table.
• Trunk and partner trunk are compared with the trunk object list. Furthermore,
the trunk group and partner trunk group are compared with the entries in the
trunk group list.
• If a connection to a hunt group is involved, the DESTPTY is also compared

with the hunt group object list. Furthermore, the head number is determined
and likewise compared.
A31003-H3170-S103-6-7620, 02/2019
Service Information
Record type:
Every ticket contains a field with information on whether this record is relevant for
charging and / or for traffic measurement.
SWU / ADP load:

If the SWU / ADP load (average processor load of at least 10 seconds) is to be
measured, a load ticket is generated every 10 seconds. In this case, the record
type is likewise set to "traffic measurement relevant".
Activities of the attendant console:

If
• the attendant activates / deactivates night service,
• the attendant removes / inserts the jack,
• AC-WIN stops / starts operation - with the following cases covered in this
context:
– the AC-WIN program is started / stopped,
– the AC-WIN PC is activated / deactivated,
– the attendant console is blocked / deblocked through an AMO command,
An activity ticket is generated. In this case, the RECORD TYPE is likewise set to
ASC "traffic measurement relevant".
Queuing time for hunting groups:

The time a connection waits - in the queue of a hunting group - is measured.

No special requirements. This performance feature must be regarded in
connection with the feature CDR enhanced.
A normal record is generated in this context. Most of the non-relevant fields are
filled with fillers. The activity of the attendant console can be seen in the
SUPPLSERV field and CALLIPTY provides the AC number. The CONNTYPE
field contains the label for this function: ACACT
In the RECTYPE field, "2" documents that this record is only relevant for PM.
A31003-H3170-S103-6-7620, 02/2019
Generation
63.4 Generation
1. Activate performance feature CDRe Traffic (or PM, Performance
Management)
CHA-DEFTM:PMON=Y;
2. Activate all measuring objects
CHA-DEFTM:ALLON=Y;
3. Generate special load tickets
CHA-DEFTM:LOADON=Y
4. Activate special activity tickets of the attendant console
CHA-DEFTM:ACACTON=Y;
5. Adding the field RECORD TYPE (RECTYPE) in the charge data record
output
ADD-FTBL:FORMNO=4,TYP=B,TBL=FORM,NO=1,END=N,
FORMAT="RECTYPE:#@@@@@@@@@";
ADD-FTBL:FORMNO=4,TYP=B,TBL=CTRL,NO=2,END=N,CTLCHARS=CR; 
ADD-FTBL:FORMNO=4,TYP=B,TBL=CTRL,NO=3,END=N,CTLCHARS=LF; 
ADD-FTBL:FORMNO=4,TYP=B,TBL=CTRL,NO=5,END=Y,CTLCHARS=LF; 
ADD-
FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=1,FLDNAME=RECTYPE,
FILLTYPE=CHAR,FILLER=" ",FLDALIGN=L;
6. Adding the field Processor Load ADP (ADPLOAD) in the charge data
record output
ADD-FTBL:FORMNO=4,TYP=B,TBL=FORM,NO=1,END=N,
FORMAT="ADP-TIME: #@:#@,#@'#@ #@-#@-#@@@ ADP-LOAD:
#@@@@";
ADD-
FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=1,FLDNAME=ENDHOUR,
FILLTYPE=CHAR ,FILLER=" ",FLDALIGN=L; 
ADD-FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=2,FLDNAME=ENDMIN,
ADD-FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=3,FLDNAME=ENDSEC,
ADD-FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=4,FLDNAME=END10,
ADD-FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=1,FLDNAME=ENDDAY,
ADD-
FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=2,FLDNAME=ENDMONTH,
FILLTYPE=CHAR,FILLER=" ",FLDALIGN=L; 
ADD-
FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=3,FLDNAME=ENDYEAR,
ADD-
FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=4,FLDNAME=ADPLOAD,
FILLTYPE=CHAR ,FILLER=" ",FLDALIGN=L;
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
7. Adding the field Processor Load SWU (SWULOAD) in the charge data
record output
ADD-FTBL:FORMNO=4,TYP=B,TBL=FORM,NO=1,END=N,
FORMAT="SWU-TIME: #@:#@,#@'#@ #@-#@-#@@@ SWU-LOAD:
#@@@@";
ADD-FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=1,FLDNAME=STHOUR,
ADD-FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=2,FLDNAME=STMIN,
ADD-FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=3,FLDNAME=STSEC,
ADD-FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=4,FLDNAME=ST10,
ADD-FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=1,FLDNAME=STDAY,
ADD-
FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=2,FLDNAME=STMONTH,
FILLTYPE=CHAR ,FILLTYPE=" ",FLDALIGN=L; 
ADD-FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=3,FLDNAME=STYEAR,
ADD-
FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=4,FLDNAME=SWULOAD,
8. Adding the field Hold Time(HOLDDUR) in the charge data record output
ADD-
FTBL:FORMNO=4,TYP=B,TBL=FORM,NO=1,END=N,FORMAT="HOLDDUR:
#@@@";
ADD-
FTBL:FORMNO=4,TYP=B,TBL=FIELD,NOFELD=1,FLDNAME=HOLDDUR,
9. Filter in AMO SELG
The RECTYPE indicates relevance for PM and / or CDRE.
With CONNTYP, filtering according to ACACT / LOAD / ALL can be
performed if required.
10. Please refer also to the Service Manual and the ID10114 CDRE
Adaptions feature description for configuring and activating call charge
recording.
63.5 Relevant AMOs

• New AMOs
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

Language
DEFTM ACACTON D Erfassen der Ereignisse des
Vermittlungsplatzfernsprechers
ACACTON E Monitoring of the events of attendant console
ALLON D Alle Objekte, ausser der Prozessorlast und der
Aktivität des Vermittlungsplatzfernsprechers
werden erfasst.
ALLON E Monitoring of all objects except processor load
and attendant console activity.
ATNDGRNU D Vermittlungsplatzgruppennummer
ATNDGRNO E Attendant group number
EBT D Einbauteilung in der LTU
CCT E Circuit number
LOADON D spezielles PM-Ticket mit der Prozessorlast
LOADON E special PM-Ticket containing processor load
LTU D Leitungsverbindungseinheit
LTU E Line Trunk Unit
NUMMER D Teilnehmernummer
NUMBER E Station number
OBJECT D Messobjekttypen
OBJECT E Measurement object types
PMON D Zentralschalter für das Performance
Management
PMON E Central switch for performance measurement
SATZ D Nummer des Baugruppensatzes
SLOT E Specification of the mounting pitch in the LTU
TRKGRNU D Bündelnummer
TRKGRNO E Trunk group number
FTBL ELNAM D Identification of the variable fields
ADPLOAD: Prozessorlast des ADP,
HOLDDUR: gesamte Haltezeit,
RECTYPE: Art der Aufzeichnung,
SWULOAD: Prozessorlast der SWU
FLDNAME E Identification of the variable fields
ADPLOAD: processor load of the ADP,
HOLDDUR: total hold duration,
RECTYPE: for which application areas the
record is relevant,
SWULOAD: processor load of the SWU,
SELG RECTYPE D Aufz. relevant fuer: CDR/PM/CDR&PM
E Record is relevant for: CDR/PM/CDR&PM
• Changed AMOs
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

Language
SELG CONNTYPE D Art der Verbindung erweitert
E Connection type enhanced
TEXT SUPLSERV D Supplementary services erweitert
E Supplementary services enhanced
SUBSID D Teilnehmertyp erweitert
E Subscriber ID enhanced
CONNTYPE D Art der Verbindung erweitert
E Connection type enhanced
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_cdr_acc_en.fm
Feature Description
64 Call Detail Recording - Account Code
ACC List
Company= 111111
BMW=222222
Bosch = 333333
Rover = 444444
Entry of an account code

automatic or manual
ACC Code for output in call detail record for Call charge output
subsequent billing. STN ext. STNO ACC code
Entry prior to or during the call
PIN check pursuant to entry in COPIN

With the "Account Code" feature, incoming and outgoing calls can be provided
with an account number or, consecutively, with several account numbers which
are displayed in the call charge data output.
64.2 User Interface

Two types of account code can be configured in the system:
• automatic account code
• manual account code
The automatic account code is assigned automatically to every station for every
outgoing call. It is configured system-wide and can also be changed individually
by station.
The user can overwrite an automatic account code with a manual account code
per call.
A31003-H3170-S103-6-7620, 02/2019
Service Information
The manual account code can be entered as follows both prior to and during a
call:
• with the digit analysis result for account code
• using the service menu
• using the main menu
• using the account code key
• using the ACD transaction code key
• using the ACD transaction code
The following check types can be configured for the manual account code:
• no check
• check of the code length
• modulo check (= configurable algorithm)

The account code feature must be released in the system with the AMO FEASU.
The automatic account code can be configured system-wide with the AMO ZAND
and also edited individually by station with the AMO SDAT.
For the manual account code, the station requires a COS parameter configured
with the AMO COSSU. This authorization only applies to its physical connection
and cannot be transferred with the PIN-Mobile User feature.
The access codes for the manual account code and the ACD transaction code
are configured with the AMO WABE.
The manual account code and the check type are configured with the AMO
PERSI in COPIN 9. The string length of the account code can likewise be
administrated in PERSI.
The account code key and the ACD code key are configured with the AMO
TAPRO.
In AMO ZAND, it can be specified whether the manual transaction code can also
be activated with the code or key for ACD transaction code. The user interface
differs when using the ACD function and when entering the account code via
CDRACC code or key. In the case of the ACD function, the code entry must
always be ended with the ‚”#’ character, for example, and every code entered is
accepted without being checked.
A31003-H3170-S103-6-7620, 02/2019

Account Code Setup - Examples
• Activate account code feature in system:

CHA-FEASU:TYPE=A,CM=CDRACC;
• Add digit analysis result *86 (8086) for account code:

ADD-WABE:CD=*86,DPLN=0,DAR=CDRACC,CDDP=8086;
• Add COS for manual account code:

CHA-COSSU:TYPE=COS,COS=23,AVCE=ACTMAN;
• Add code ‚4711’ for account code:

ADD-PERSI:TYPE=CDRAC,CDRAC=4711;
• Display COPIN 9 settings for the account code:

DIS-PERSI:TYPE=COPIN,COPIN=9;
H500: AMO PERS STARTED
+-------+-------------------------------------------------+
| COPIN | COPIN PARAMETER |
+-------+-------------------------------------------------+
| 9 | COTYPE = PCODE |
| | PINTEXT = 'ACCOUNT CODE ' |
| | CDRACLEN = 5 |
| | CDRTEXTS = NO |
| | CDRTEXT = ' ' |
| | DISPRSTN = NO IDHOME = NO |
| | PINTEST = LENGTH DISPID = PERMDISP |
| | TRKCD = 0 TRACE = NO |
| | TRKCDTYP = NO PINEXT = YES |
| | PINDUR = ONE DISPPIN = YES |
| | TRANSFER = NO PINNKEY = NO |
| | DEACKEY = NO POSCHKN = 1 |
| | COSHOME = NO PINLCOS2 = NO |
| | DPTEST = NO |
+-------+-------------------------------------------------+
AMO-PERS-111 PERSONAL IDENTIFICATION
• Add account code key:

CHA-TAPRO:STNO=3156,STD=19,DIGTYP=OPTISET,KY11=CDRACC;
• Add ACD transaction code key:
CHA-TAPRO:STNO=3156,STD=19,DIGTYP=OPTISET,KY12=ACC;
• Add automatic account code in system:(default account code)
CHA-ZAND:TYPE=ACC,DCDRACC=1234;
• Display of the data configured in the system (automatic account code=1234,
activation via ACD function=no) for the account code:
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
DIS-ZAND:TYPE=ACC;
H500: AMO ZAND STARTED 
ACCOUNT CODE 
===================== 
DCDRACC = 1234 , ACCONEKY = NO; 
AMO ZAND -111 CENTRAL SYSTEM DATA
• Configure account code via ACD Transaction Code:

CHA-ZAND:TYPE=ACC,ACCONEKY= YES;
• Add automatic CDRACC for station 3156:
CHA-SDAT:STNO=3156,TYPE=DATA1,CDRACC=6789;
• Add account code in the call charge data output:
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=1,END
,FORMAT="ACCTCODE: #@@@@@@@@@@@";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=CTRL,NO=5,END=J,CTLCHARS=LF; 
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=ACCTCODE
Please refer to the Service Manual and the CDRE Adaptions feature description
for configuring and activating call charge recording.
64.5 Relevant AMOs

Language
FEASU CDRACC d Gebuehrenerfassung Account Code
Leistungsmerkmal Abrechnungs Code im
System einschalten
CDRACC e Call Detail Recording Account Code
switch feature Account Code
WABE CDRACC d CDR Account Code
Kennzahl für Abrechnungs Code einrichten
CDRACC e CDR Account Code
digit analysis result Account Code
COSSU ACTMAN d Manueller CDR Code Moeglich
COS für manuellen Abrechnungs Code
einrichten
ACTMAN e Allow Manual Cdr Account Code
Cos for manuel cdr account code
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

Language
PERSI CDRAC d CDR Account Code
Code für Abrechnungs Code einrichten
CDRAC e Cdr Account Code
CDRACLAE d Länge des CDR account codes
CDRACLEN e Length Of Cdr Account Code
TAPRO CDRACC d CDR Account Code Key
Taste für Abrechnungs Code einrichten
CDRACC e CDR Account Code Key
ZAND ACC d Einstellungen Fuer Account Code
ACC e settings for CDR Account Code
DCDRACC d Default CDR Account Code
automatischen Abrechnungs Code im System
einrichten oder löschen (Eingabe: „F“)
DCDRACC e Default CDR Account Code
set or delete (input: „F“) default CDR Account
Code in system
ACCMEINT d Account Code Mit Einer Taste Aktivieren
Nein= Abrechnungs Code ist nicht mittels ACD-
Transaktions Code möglich
Ja= Abrechnungs Code ist mittels ACD-Transak-
tions Code möglich
ACCONEKY e Account Code With One Key Only
No= CDR key triggers CDR, ACD key triggers
ACD-G (DB-Initialization)
Yes= ACD triggers ACD-G and CDR
SDAT CDRACC d CDR Account Code
automatischen CDRACC für einen Teilnehmer
ändern
CDRACC e CDR Account Code
automatic CDRACC for subscriber
FTBL ELNAM d Bezeichnung des variablen Feldes
ACCTCODE: Account-Code des Rufes
FLDNAME e Identification of the variable fields (new:
ACCTCODE: account code of call
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_gdata_en.fm
Call Charge Data Display from the CDRS File
65 Call Charge Data Display
65.1 Call Charge Data Display from the CDRS File

• Create a scheduled job for output once, more than once, or periodically with:
ADD-GETAB:TYPE=L,DIAFNO=<number>,DEV=<string>,TAR=<string>
,STAT=<string>,[STADAY2=<string>],[STADAY3=<string>]
,[STAHR2=<number>],[STAHR3=<number>],[PERIOD=<string>]
,STNO=<string>,DEL=<string>;
• Set up a short dialog to start immediate output for a current station number, a
station list ,or a line list with:
ADD-GETAB:TYPE=S,DIAFNO=<number>,STNO=<string>,DEL=<string>;
• Immediate output of a dialog field with:
OUTPUT-GETAB:DIAFNO=<number>;
• Cancel the output with:
STOP-GETAB:DIAFNO=<number>;
• Display the dialog fields with:
DIS-GETAB:[DIAFNO=<number>];
• Delete one dialog field with:
DEL-GETAB:DIAFNO=<number>;
65.2 Call Charge Data Display on Supplementary Device

• Create a long dialog to delete the data without output with:
ADD-
GEZAB:TYPE=L,DIAFNO=<number>,FILE=<character>,FILESTA=<string
> 
,FILEND=<string>,DEV=NODEV,DEL=<Y\N>,FOUT=<Y/N>;
• Create a scheduled job for output once, more than once, or periodically with:
ADD-
> 
,FILEND=<string>,DEV=<DEV1\DEV2\DEV3\DEV4\TAPE\FT>
,DEL=<
Y\N>,FORM=<string>,BLKSIZE=<number>,FOUT=Y\N>
,STAT=<string>,MULTOUT=Y{(min1)STADAY2=<string>
,STADAY3=<string>,STAHR2=<string>,STAHR3=<string>}
,PERIOD=<string>,SELSTOP=<Y\N>;
• Create a scheduled job to output to the DPS with:
A31003-H3170-S103-6-7620, 02/2019
Call Charge Data Display on Supplementary Device
ADD-
> 
,FILEND=<string>,DEV=DP,CALLUP=<Y\N>,DEL=<Y\N>
,FORM=<string>,BLKSIZE=<number>,FOUT=<Y\N>,STAT=<string>
,MULTOUT=Y{(min1)STADAY2=<string>,STADAY3=<string>
,STAHR2=<string>,STAHR3=<string>},PERIOD=<string>
,SELSTOP=<Y\N>;
• Create a scheduled job using a short dialog with:
If the ADD-GEZAB action is started with "S" (short dialog), all parameters are
changed except for CALLUP and PERIOD.
– A long dialog must have already been added for the dialog field in
question.
– Stop the TIMEORDER ACTIVE status for the dialog field in question.
– Change certain values in the dialog field in question using a short dialog.
ADD-
GEZAB:TYPE=S,DIAFNO=<number>,[FILE=<character>],[FILESTA=<str
ing>]
,[FILEND=<string>],[DEV=<string>],[DEL=<Y\N>]
,[FORM=<string>],[BLKSIZE=<number>],[FOUT=<Y\N>]
,STAT=<string>,[MULTOUT=Y],{(min1)STADAY2=<string>
,STADAY3=<string>,STAHR2=<string>,STAHR3=<string>}
,[SELSTOP=<Y\N>];
• Change certain parameters in a scheduled job using a short dialog with:
If a scheduled job is activated for a dialog field, you can only rewrite the dialog
field by stopping the scheduled job that is running (STOP-GEZAB). This
changes the status of the dialog field from TIMEORDER ACTIVE to BUSY.
With the CHA-GEZAB action, you can rewrite all parameters except PERIOD.
CHA-
GEZAB:DIAFNO=<number>,{(min1)FILE=<character>,FILESTA=<string
>
,FILEND=<string>,DEV=<string>,CALLUP=<Y\N>,DEL=<Y\N>
,FORM=<string>,BLKSIZE=<number>,FOUT=<Y\N>,STAT=<string>
,MULTOUT=Y},{(min1)STADAY2=<string>,STADAY3=<string>
,STAHR2=<string>,STAHR3=<string>},[SELSTOP=<Y\N>];
• Cancel an active data output with:
STOP-GEZAB:DIAFNO=<number>;
• Display the dialog fields with:
DIS-GEZAB:[DIAFNO=<number>];
• Start immediate output with:
Requirement: The dialog field in question must be configured.
OUTPUT-GEZAB:DIAFNO=<number>;
• Delete a configured dialog field with:
A31003-H3170-S103-6-7620, 02/2019
DEL-GEZAB:DIAFNO=<number>;
A31003-H3170-S103-6-7620, 02/2019
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_gsoft_en.fm
Call Charge Data - Immediate Output
Immediate Output to GC 3001 A
66 Call Charge Data - Immediate Output
66.1 Immediate Output to GC 3001 A

• Enter line allocation for connecting GC 3001A to line 17
AD-ATCSM:UNIT=A1,TYPE=CFIG,CFIG=DEV,TYPENO=8,TERMDESC=ARCVCO,
CNTRLNA=F8,T=30,ANSLNT=04,ANSLN=00,CNTRLND=02; 
AD-LCSM:UNIT=A1,MLNTYPE=ASYNC,TYPENO=8,BAUD=2400,LEN=7,
STOPLEN=SL2_,TRNSCLK=INT,RCLK=INT; 
AD-ATCSM:UNIT=A1,TYPE=ADD,ALSEL=LN,TYPENO=8,LN=17; 
AC-BSSM:UNIT=A1,TYPE=BC,SLOT=13,KIND=ANT; 
AC-LSSM:UNIT=A1,LN=17;
• Configure CDR with immediate output to options
AD-FEACG:CM=CDRCDUMP;
• Add CDR code to route code table
AD-RCUT:RTECD=0,CDRCODE=0;
• Add device allocation
AD-GEZU:TBL=TTY,NAMEOUT=DEV2,PHDEV=TTY,DEVCL=GC3001A;
• Create GC3001A format
AD-FTBL:FORMNO=3,TYPE=B,TBL=FORM,NO=1,END=N, 
FORMAT=""*#@@+#@@@@+#+#@@+#@@@@@@@@@@@@@+0+#@@@@@@@@@@@+#@#@#
@+#@#@#@#@+""; 
AD-FTBL:FORMNO=3,TYPE=B,TBL=CTRL,NO=2,END=N,CTLCHARS=CR; 
AD-FTBL:FORMNO=3,TYPE=B,TBL=CTRL,NO=3,END=Y,CTLCHARS=LF; 
AD-FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=TKNOREAL,
FATTR=NONE,DATTR=NONE,FILLTYPE=CHAR,FILLER=0,FLDALIGN=R; 
AD-
FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=CHRGEE,FATTR=
NONE, 
DATTR=NONE,FILLTYPE=CHAR,FILLER=0,FLDALIGN=R; 
AD-
FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=3,FLDNAME=RECPT,FATTR=N
ONE, 
AD-FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=CHRGUNIT,
AD-FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=5,FLDNAME=VDESTNO,
FATTR=NONE,DATTR=NONE,FILLTYPE=CHAR,FILLER= ,FLDALIGN=L; 
AD-
FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=6,FLDNAME=PIN,FATTR=NON
E, 
DATTR=NONE,FILLTYPE=CHAR,FILLER= ,FLDALIGN=L; 
AD-FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=7,FLDNAME=CONHOUR,
AD-
FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=8,FLDNAME=CONMIN,FATTR=
NONE, 
AD-
A31003-H3170-S103-6-7620, 02/2019
Immediate Output to CDRC1 File on HD
FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=9,FLDNAME=CONSEC,FATTR=
NONE, 
AD-FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=10,FLDNAME=ENDMONTH,
AD-
FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=11,FLDNAME=ENDDAY,FATTR
=NONE, 
AD-FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=12,FLDNAME=ENDHOUR,
AD-FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=13,FLDNAME=ENDMINR,
AD-FTBL:FORMNO=3,TYPE=B,TBL=FIELD,NOFELD=14,FLDNAME=ENDSEC,
FATTR=NONE,DATTR=NONE,FILLTYPE=CHAR,FILLER=0,FLDALIGN=R;
• Add selection group
AD-SELG:TBL=SELG,SELGNO=4,RESOP=Y,BASDEV=DEV2,RESDEV=DEV1,
BLBAS=1,BLRES=1; 
AD-SELG:TBL=SELT,SELGNO=4,SELTABNO=1,FORMBAS=FORM03,
FORMRES=FORM03,TARIF=NOCALC,DESTCNT=A22,CDRCD=0&&999999,
SERVICE=VOICE,ATNDGR=0&&15,CTYPE=ALL,PAYPARTY=ALL,CDRC=N,
CDRSTA=N,THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,CDRAC=N,
SFSETUP=N,CDBAD=N,CDRULTE=N,CONNT=N,PCODE=N,PPCF=N,
STATAB1=N,
STATAB2=N,DNOTBL1=N,DNOTBL2=N,CDRULT=0,CONNTL=000000,
LEVEL0=0&&999,LEVEL1=0&&254,LEVEL2=0&&30,TIELINE=N,EXPENS=N,
CONNTYP=ALL,COPIN=0&&8,CARRIER=0&&9;
• Activate immediate output of call charge data to options
AC-SELS:SELGRNO=4;
66.2 Immediate Output to CDRC1 File on HD

The output format is defined as FORM01 when setting up the CDR data output
request to options with the GEZAB AMO (Format 1, for output to TTY).
• Create a selection
AD-FEACG:CM=CDRCDUMP&CDRCDIS;
• Assign "Segmentation Tables" (DTAR=standard/daytime rates, NTAR1
cheap/night rate 1, NTAR2 cheap/night rate 2)
AD-TABT:LT=06-
00,TARTYPMO=NTAR2,TARTYPTU=NTAR2,TARTYPWE=NTAR2,
TARTYPTH=NTAR2,TARTYPFR=NTAR2,TARTYPSA=NTAR2,TARTYPSU=NTAR2,
TBLNO=1; 
AD-TABT:LT=08-
TARTYPTH=NTAR1,TARTYPFR=NTAR1,TARTYPSA=NTAR1,TARTYPSU=NTAR2; 
AD-TABT:LT=14-
00,TARTYPMO=DTAR,TARTYPTU=DTAR,TARTYPWE=DTAR,TARTYPTH=DTAR,TA
RTYPFR=DTAR,TARTYPSA=T,TARTYPSU=NTAR2; 
AD-TABT:LT=18-
RTYPFR=DTAR,TARTYPSA=N2,TARTYPSU=NTAR2; 
A31003-H3170-S103-6-7620, 02/2019
Immediate Output to File Transfer File on HD
AD-TABT:LT=22-
AD-TABT:LT=24-
TARTYPTH=NTAR2,TARTYPFR=NTAR2,TARTYPSA=NTAR2,TARTYPSU=NTAR2;
• Assign the tariff and tariff group tables
– Assign the tariff table for connections with call charge information
AD-
TTBL:TBL=WCU,TARTBLNO=1,TARMIN=0,METHOD=FACTOR,FACTOR=100,
LT1=0,TAR1=500;
– Assign the tariff table for connections without call charge information
AD-
TTBL:TBL=WOCU,TARTBLNO=1,ZONE=DIST01,INTDAY=10,TARDAY=10,
INTNT1=10,NTAR1=10,INTNT2=10,NTAR2=10,INTNT3=10,NTAR3=10,
INTNT4=10,NTAR4=10,TARBAS=100,TARMIN=0,SEGTBLNO=1,CHPER=Y;
– Assign tariff group
ADD-
TTBL:TBL=GRP,GRNO=1,CARRIER=0,SERVICE=VOICE,TARTBLNO=1,CAT
PTY=NORM;
• Add selection group for CDR with immediate output to options (HD)
AD-SELG:TBL=SELG,SELGNO=1,RESOP=Y,BASDEV=CDRC1,RESDEV=NODEV,
BLBAS=1, BLRES=0; 
AD-SELG:TBL=SELT,SELGNO=1,SELTABNO=1,FORMBAS=HDFORM,
FORMRES=NOFORM,TARIF=TARGR01,DESTCNT=A22,CDRCD=0&&999999,
SERVICE=VOICE&TTC,ATNDGR=0&&15,CTYPE=ALL,PAYPARTY=ALL,
CDRC=N,CDRSTA=N,THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,
CDRAC=N,SFSETUP=N,CDBAD=N,CDRULTE=N,CONNT=N,
PCODE=N,PPCF=N,STATAB1=N,STATAB2=N,DNOTBL1=N,DNOTBL2=N,
CDRULT=0,CONNTL=000000,LEVEL0=0&&999,LEVEL1=0&&254,LEVEL2=0&&
30,
TIELINE=N,EXPENS=N,CONNTYP=ALL,COPIN=0&&8,CARRIER=0&&9;
• Activate CDR with immediate output to options (TTY)
AC-SELS:SELGRNO=1;
66.3 Immediate Output to File Transfer File on HD

The output format is defined as FORM01 (Format 1, for output to TTY).
• Create a selection
A31003-H3170-S103-6-7620, 02/2019
Immediate Output to File Transfer File on HD
AD-TABT:LT=06-
TBLNO=1; 
AD-TABT:LT=08-
AD-TABT:LT=14-
AD-TABT:LT=18-
AD-TABT:LT=22-
AD-TABT:LT=24-
AD-
LT1=0,TAR1=500;
AD-
ADD-
PTY=NORM;
• Add selection group for CDR with immediate output to options (HD)
AD-SELG:TBL=SELG,SELGNO=1,RESOP=Y,BASDEV=FT,RESDEV=NODEV,
BLBAS=1, BLRES=0; 
AD-SELG:TBL=SELT,SELGNO=1,SELTABNO=1,FORMBAS=HDFORM,
FORMRES=NOFORM,TARIF=TARGR01,DESTCNT=A22,CDRCD=0&&999999,
CDRAC=N,SFSETUP=N,CDBAD=N,CDRULTE=N,CONNT=N,
PCODE=N,PPCF=N,STATAB1=N,STATAB2=N,DNOTBL1=N,DNOTBL2=N,
CDRULT=0,CONNTL=000000,LEVEL0=0&&999,LEVEL1=0&&254,LEVEL2=0&&
30,
TIELINE=N,EXPENS=N,CONNTYP=ALL,COPIN=0&&8,CARRIER=0&&9;
AC-SELS:SELGRNO=1;
A31003-H3170-S103-6-7620, 02/2019
Immediate Output to Magnetic Tape Device
66.4 Immediate Output to Magnetic Tape Device

AD-GEZU:TBL=TTY,NAMEOUT=DEV1,PHDEV=TTY,DEVCL=TERM1;
• Configure CDR with immediate output to options
AD-TABT:LT=06-
TBLNO=1; 
AD-TABT:LT=08-
AD-TABT:LT=14-
AD-TABT:LT=18-
AD-TABT:LT=22-
AD-TABT:LT=24-
AD-
LT1=0,TAR1=500;
AD-
ADD-
PTY=NORM;
• Add selection group for CDR with immediate output to options (tape)
AD-SELG:TBL=SELG,SELGNO=3,RESOP=Y,BASDEV=TAPE,RESDEV=DEV1,
A31003-H3170-S103-6-7620, 02/2019
Immediate Output to PT80i (Optional Device)
FORMRES=FORM01,TARIF=TAR01,DESTCNT=A22,CDRCD=0&&999999,
CDRAC=N,SFSETUP=N,CDBAD=N,CDRULTE=N,CONNT=N,PCODE=N,
PPCF=N,STATAB1=N,STATAB2=N,DNOTBL1=N,DNOTBL2=N,CDRULT=0,
CONNTL=000000,LEVEL0=0&&999,LEVEL1=0&&254,LEVEL2=0&&30,TIELIN
E=N,
EXPENS=N,CONNTYP=ALL,COPIN=0&&8,CARRIER=0&&9;
• Activate immediate output of call charge data to options (magnetic tape)
AC-SELS:SELGRNO=1;
66.5 Immediate Output to PT80i (Optional Device)

The output format is defined as FORM01 in the GEZAB AMO (Format 1 for output
to TTY).
• Configure CDR for immediate output to options

AD-GEZU:TBL=TTY,NAMEOUT=DEV1,PHDEV=TTY,DEVCL=TERM1; 
AD-GEZU:TBL=TTY,NAMEOUT=DEV2,PHDEV=TTY,DEVCL=TERM2;
AD-TABT:LT=06-
TARTYPTH=NTAR2,TARTYPFR=NTAR2,TARTYPSA=NTAR2,
TARTYPSU=NTAR2,TBLNO=1; 
AD-TABT:LT=08-
AD-TABT:LT=14-
AD-TABT:LT=18-00,TARTYPMO=DTAR,TARTYPTU=DTAR,TARTYPWE=DTAR,
TARTYPTH=DTAR,TARTYPFR=DTAR,TARTYPSA=N2,TARTYPSU=NTAR2; 
AD-TABT:LT=22-
AD-TABT:LT=24-
00,TARTYPMO=NTAR2,TARTYPTU=NTAR2,TARTYPWE=NTAR2,TARTYPTH=NTAR
2,TARTYPFR=NTAR2,TARTYPSA=NTAR2,
TARTYPSU=NTAR2;
AD-TTBL:TBL=WCU,TARTBLNO=1,TARMIN=0,METHOD=FACTOR,
FACTOR=100,LT1=0,TAR1=500;
A31003-H3170-S103-6-7620, 02/2019
AD-
ADD-
PTY=NORM;
• Add selection group for immediate output to options (printer)
AD-SELG:TBL=SELG,SELGNO=1,RESOP=Y,BASDEV=DEV1,RESDEV=DEV2,
FORMRES=FORM01,TARIF=TARGR01,DESTCNT=A22,CDRCD=0&&999999,
CDRAC=N,SFSETUP=N,CDBAD=N,CDRULTE=N,CONNT=N,PCODE=N,
PPCF=N,STATAB1=N,STATAB2=N,DNOTBL1=N,DNOTBL2=N,CDRULT=0,
CONNTL=000000,LEVEL0=0&&999,LEVEL1=0&&254,LEVEL2=0&&30,TIELIN
E=N;
EXPENS=N,CONNTYP=ALL,COPIN=0&&8,CARRIER=0&&9;
AC-SELS:SELGRNO=1;
A31003-H3170-S103-6-7620, 02/2019
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_gebau_en.fm
Call Charge Output
Output Format 1
67 Call Charge Output
67.1 Output Format 1

Format 1 is an output format for call data recording.
Formats 1 to 16: Standard formats

These are formats that can be selectively chosen with the parameters
FORMBAS (output format for the base device) and FORMRES (output format
for the reserve device) in the AMO SELG and AMO GEZAB. All variable fields
can appear in these formats.
Formats 17 to 24: Formats for block start (base device)

You can use the parameters BLBAS (block size for the base device) and
BLRES (block size for the reserve device) in the AMO SELZ to define block
sizes for the output. The block size specifies how many call data records are
blocked in a contiguous output. Formats 17-24 are entered in selection
groups 1-4 (format 17 in selection group 1, format 18 in selection group 2,
etc.) each time a block of this kind is started.
Formats 25 to 32: Formats for block start (reserve device)

See formats 17-24; but only for reserve device.
Formats 33 to 40: Formats for block end (base device)

See formats 17-24; but only for block end and base device.
Formats 41 to 48: Formats for block end (reserve device)

See formats 17-24; but only for block end and reserve device.
The formats (17 - 48) for the selection groups contain gaps because the number
of selection groups was reduced to 4.
Formats 49 to 56: Formats for block start (dialog/output on callup)

In the AMO GEZAB, you can use the parameter BLKSIZE (block size,
number of records per output block) to define block sizes for output in a
dialog. Formats 49 - 56 are output in dialog fields 1 - 8 (format 49 in dialog
field 1, etc.) each time a block of this kind is started.
Formats 57 to 64: Formats for block end (dialog/output on callup)

See formats 49-56; but only for block end.
Formats 65 to 72: Formats for data end in a file (dialog/output on callup)

These formats are output when the actual call data output has ended.
Formats 73 to 80: Formats for "empty files" (dialog/output on callup)
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
Output Format 1
These formats are output if the selected file is empty.
Formats 81 to 88: Formats for "deleted files" (dialog/output on callup)

These formats are output if a file is deleted after a delete job.
Formats 89 to 96: Formats for cancelling the output

These formats are output if the system calls for the data output to be
cancelled.
Formats 97 to 109: Formats for CDRS output

These formats are needed for CDRS output.
In formats 17 to 96, only the variable data elements output time, block length, and
number of records per block are allowed.
Configure output format 1:

,FORMAT="DEST. NO:#@@@@@@@@@@@@@@@@@@@@ STN.
NO:#@@@@@@ COSTS:"; 
ADD-FTBL:FORMNO=1,TYPE=B,TBL=FORM,NO=2,END=N, 
,FORMAT="#@@@@@@@ EUR CHRG. UNIT:#@@@ CALL DUR:
#@:#@:#@"; 
ADD-FTBL:FORMNO=1,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=DESTPTY 
ADD-FTBL:FORMNO=1,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=CHRGEE 
ADD-FTBL:FORMNO=1,TYPE=B,TBL=FIELD,NOFELD=3,FLDNAME=CONCHRG,
,FILLTYPE=CHAR,FILLER=" ",FLDALIGN=RC,COMPOS=6; 
ADD-FTBL:FORMNO=1,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=CHRGUNIT 
ADD-FTBL:FORMNO=1,TYPE=B,TBL=FIELD,NOFELD=5,FLDNAME=CONHOUR 
,FILLTYPE=CHAR,FILLER="0",FLDALIGN=R; 
ADD-FTBL:FORMNO=1,TYPE=B,TBL=FIELD,NOFELD=6,FLDNAME=CONMIN 
ADD-FTBL:FORMNO=1,TYPE=B,TBL=FIELD,NOFELD=7,FLDNAME=CONSEC 
,FILLTYPE=CHAR,FILLER="0",FLDALIGN=R;
The format now looks as follows:
Output example:
Four data records with the destination number 04511, station number 3101,
call charge units 1, call duration 3 seconds and the tariff of 23 cent/call charge
unit.
DEST. NO:04511 STN. NO:3101 COSTS:00000.23 EUR CHRG.
UNIT:1 CALL DUR: 00:00:03
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
Charge Output at the ATND (CDRATND)
67.2 Charge Output at the ATND (CDRATND)

• Enable the required CDRATND feature (attendant console)
ADD-FEACG:CM=CDRATND;
NOTE: If the parameter TARIF=NOCALC was set in the AMO SELG and the
parameter TYPE=WITHOUT was set in the AMO GEFE, only the call duration
is shown on the attendant console display.
• Segmentation table (T=day tariff, N1=night tariff 1, N2=night tariff 2):

ADD-TABT:LT=06-
00,TARTYPMO=NTAR2,TARTYPTU=NTAR2,TARTYPWE=NTAR2
,TARTYPTH=NTAR2,TARTYPFR=NTAR2,TARTYPSA=NTAR2,TARTYPSU=NTAR2,
SEGTBLNO=1; 
ADD-TABT:LT=08-
,TARTYPTH=NTAR1,TARTYPFR=NTAR1,TARTYPSA=NTAR1,TARTYPSU=NTAR2;
ADD-TABT:LT=14-00,TARTYPMO=DTAR,TARTYPTU=DTAR,TARTYPWE=DTAR
,TARTYPTH=DTAR,TARTYPFR=DTAR,TARTYPSA=DTAR,TARTYPSU=NTAR2; 
,TARTYPTH=DTAR,TARTYPFR=DTAR,TARTYPSA=NTAR2,TARTYPSU=NTAR2; 
ADD-TABT:LT=22-
ADD-TABT:LT=24-
,TARTYPTH=NTAR2,TARTYPFR=NTAR2,TARTYPSA=NTAR2,TARTYPSU=NTAR2;
• Add tariff group:
– Add the tariff table with call charge information:

ADD-TTBL:TBL=WCU,TARTBLNO=1,TARMIN=0,METHOD=FACTOR
,FACTOR=100,LT1=0,TARIF1=500;
– Add the tariff table without call charge information:
ADD-
TTBL:TBL=WOCU,TARTBLNO=1,ZONE=DIST01,INTDAY=10,TARDAY=10
,INTNT1=10,NTAR1=10,INTNT2=10,NTAR2=10,
INTNT3=10, NTAR3=10
,INTNT4=10,NTAR4=10,TARBAS=100,TARMIN=0,SEGTBLNO=1,CHPER=Y
;
– Add tariff group table 1:
ADD-
TTBL:TBL=GRP,GROUPNO=1,CARRIER=0,SERVICE=VOICE,TARTBLNO=1
,METHOD=FACTOR;
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
Charge Output at the ATND (CDRATND)
• Add currency identifier:

CHA-DAVF:COMPOS=+2,NAME="EUR";
• Add routing code table (tie trunk connection yes/no):
ADD-RCUT:RTECD=0,CDRCODE=0;
• Selection group for attendant console
– Delete selection group 3:

DEL-SELG:SELGNO=3;
– Add selection group 3:
ADD-SELG:TBL=SELG,SELGNO=3,RESOP=N,BASDEV=ATTEND
,RESDEV=NODEV,BLBAS=1,BLRES=0;
– Add selection group 3 with selection table 1 (voice connection VOICE):
ADD-SELG:TBL=SELT,SELGNO=3,SELTABNO=1,FORMBAS=ATTEND
,FORMRES=NOFORM,TARIF=TARGR01,DESTCNT=A22,CDRCD=0&&999999
,SERVICE=VOICE,ATNDGR=0&&15,CTYPE=ALL,PAYPARTY=ALL,CDRC=N
,CDRSTA=N,THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,CDRAC=STN
,SFSETUP=N,CDBAD=N,CDRULTE=N,CONNT=N,PCODE=N,PPCF=N,STATAB
1=N
,STATAB2=N,DNOTBL1=N,DNOTBL2=N,CDRULT=0,CONNTL=000000
,LEVEL0=0&&999,LEVEL1=0&&254,LEVEL2=0&&30,TIELINE=N
,EXPENS,CONNTYP=ALL,COPIN=0&&15,CARRIER=0&&9,RECTYP=ALL;
– Add selection group 3 with selection table 2 (communication service
FAX):
ADD-SELG:TBL=SELT,SELGNO=3,SELTABNO=2,FORMBAS=ATTEND
,SERVICE=FAX,ATNDGR=0&&15,CTYPE=ALL,PAYPARTY=ALL,CDRC=N,CD
RSTA=N
,THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,CDRAC=STN,SFSETUP=N,C
DBAD=N,
,CDRULTE=N,CONNT=N,PCODE=N,PPCF=N,STATAB1=N,STATAB2=N
,DNOTBL1=N,DNOTBL2=N,CDRULT=0,CONNTL=000000, LEVEL0=0&&999
,LEVEL1=0&&254,LEVEL2=0&&30,TIELINE=N,EXPENS=N,CONNTYP=ALL
,COPIN=0&&15,CARRIER=0&&9,RECTYP=ALL;
• Activate selection group 3:
ACT-SELS:SELGRNO=3;
Display call charge data at the attendant console

• Change the decimal point position or currency unit:
CHA-DAVF:COMPOS=<number>,NAME=<string>;
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
Charge Output with PT80i
• Call up the display (decimal point position and currency unit) on the attendant
console:
DIS-DAVF;
67.3 Charge Output with PT80i

• Enable call data recording on the immediate output supplementary device
ADD-FEACG:CM=CDRCDUMP;
• Device assignment for the output:
ADD-GEZU:TBL=TTY,NAMEOUT=DEV1,PHDEV=TTY,DEVCL=TERM1;
• Segmentation table (T=day tariff, N1=night tariff 1, N2=night tariff 2)
ADD-TABT:LT=06-
,TARTYPTH=NTAR2,TARTYPFR=NTAR2,TARTYPSA=NTAR2,TARTYPSU=NTAR2,
SEGTBLNO=1; 
ADD-TABT:LT=08-
ADD-TABT:LT=22-
ADD-TABT:LT=24-
• Add tariff group

ADD-
INTNT3=10,NTAR3=10
;
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
ADD-
,METHOD=FACTOR;
• Add output format 15
,FORMAT="NO: #@@@@@ DEST. NO: #@@@@@@@@@@@@@@@@"; 
,FORMAT="AMOUNT: #@@@@@@@@@"; 
ADD-FTBL:FORMNO=15,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=CHRGEE 
,FILLTYPE=CHAR,FILLER=" ",FLDALIGN=R; 
ADD-FTBL:FORMNO=15,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=DESTPTY
,FILLTYPE=CHAR,FILLER=" ",FLDALIGN=R; 
ADD-FTBL:FORMNO=15,TYPE=B,TBL=FIELD,NOFELD=3,FLDNAME=CONCHRG
,FILLTYPE=CHAR,FILLER=0,FLDALIGN=RC,COMPOS=7;
• Add selection group 4 with selection table 1 (voice connection VOICE):
ADD-SELG:TBL=SELG,SELGNO=4,RESOP=N,BASDEV=DEV1,RESDEV=NODEV
,BLBAS=1,BLRES=0;
ADD-SELG:TBL=SELT,SELGNO=4,SELTABNO=1,FORMBAS=FORM15
,CDRSTA=N,THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,CDRAC=N,SFSETUP
=N
,CDBAD=N,CDRULTE=N,CONNT=N,PCODE=N,PPCF=N,STATAB1=N,
STATAB2=N
,DNOTBL1=DNOTBL2=N,CDRULT=0,CONNTL=000000,
LEVEL0=0&&999
ACT-SELS:SELGRNO=4;
67.3.1 Charge Output per Line with PT80i

The output format used for the reserve device is FORM01 (format 1 output to TTY
device).
• Unblock the feature array for call data recording per line
ADD-FEACG:CM=CDRCDUMP&CDRSPR;
• Add device assignment:
ADD-GEZU:TBL=TTY,NAMEOUT=DEV1,PHDEV=TTY,DEVCL=TERM1; 
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
ADD-TABT:LT=06-
,TARTYPTH=NTAR2,TARTYPFR=NTAR2,TARTYPSA=NTAR2
,TARTYPSU=NTAR2,SEGTBLNO=;
ADD-TABT:LT=08-
ADD-TABT:LT=22-
ADD-TABT:LT=24-

ADD-TTBL:TBL=WCU,TARTBLNO=1,TARMIN=0,FACTOR=100,LT1=0
,TAR1=500;
ADD-
;
ADD-
,CATPTY=NORM;
• Add routing code table:
• Add selection group 2 with selection table 1 for call data recording per line:
ADD-SELG:TBL=SELG,SELGNO=2,RESOP=Y,BASDEV=CDRS,RESDEV=DEV1
,BLBAS=1,BLRES=1; 
ADD-SELG:TBL=SELT,SELGNO=2,SELTABNO=1,FORMBAS=CDRSFORM
,FORMRES=FORM01,TARIF=TARGR01,DESTCNT=A22,CDRCD=0&&999999
,SERVICE=VOICE,ATNDGR=0&&15,CTYPE=ALL,PAYPARTY=ALL,CDRC=N,CDR
STA=N
,THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,CDRAC=N,SFSETUP=N,CDBAD=
N
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
,CDRULTE=N,CONNT=N,PCODE=N,PPCF=N,STATAB1=N,STATAB2=N,DNOTBL1
=N
,DNOTBL2=N,CDRULT=0,CONNTL=000000,LEVEL0=0&&999
• Activate call data recording per line on TTY:
ACT-SELS:SELGRNO=2;
• Add dialog field with periodic jobs (with 3 retrieval times):
ADD-
GETAB:TYPE=L,DIAFNO=3,DEV=DEV1,TARIF=TARIF01,STAT=0101010000
,STADAY2=15,STADAY3=1U,STAHR2=0,STAHR3=0,PERIOD=1M
,STNO=CO,DEL=N;
• Add the dialog field without specifying the retrieval time:
The first output takes place immediately after the add and the following
outputs are interactively controlled (second selection by short dialog).
ADD-GETAB:TYPE=L,DIAFNO=4,DEV=DEV1,TARIF=TARIF01,STAT=0
,STNO=CO,DEL=N;
67.3.2 Charge Output per Station with PT90i (CDRS)

The output format used for the reserve device is FORM01 (format 1 for output to
TTY device).
• Change the date and time of day of scheduled jobs:

CHANGE-
DATE:YEAR=2000,MONTH=12,DAY=31,HOUR=00,MINUTE=00,SECOND=00,
SYNC=MAC;
• Unblock the feature array for call data recording per station:
ADD-FEACG:CM=CDRCDUMP&CDRSPR;
• Add device assignment:
DEL-GEZU:TBL=TTY,NAMEOUT=DEV1; 
DEL-GEZU:TBL=TTY,NAMEOUT=DEV2; 
ADD-GEZU:TBL=TTY,NAMEOUT=DEV1,PHDEV=TTY,DEVCL=TERM1; 
ADD-TABT:LT=06-
,TARTYPTH=NTAR2,TARTYPFR=NTAR2,TARTYPSA=NTAR2,TARTYPSU=NTAR2
SEGTBLNO=1; 
ADD-TABT:LT=08-
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
ADD-TABT:LT=22-
ADD-TABT:LT=24-

ADD-
;
ADD-
,CATPTY=NORM;
• Add routing code table:
• Add selection group 1 with selection table 1 for call data recording per station:
ADD-SELG:TBL=SELG,SELGNO=1,RESOP=N,BASDEV=CDRS,RESDEV=DEV1
,BLBAS=1,BLRES=1;
ADD-SELG:TBL=SELT,SELGNO=1,SELTABNO=1,FORMBAS=CDRSFORM
,FORMRES=FORM01,TARIF=TARGR01,DESTCNT=A22,CDRCD=0&&999999
,CDRSTA=N,THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,CDRAC=N,SFSETUP
=N
,CDBAD=N,CDRULTE=N,CONNT=N,PCODE=N,PPCF=N,STATAB1=N,
STATAB2=N
,DNOTBL1=N,DNOTBL2=N,CDRULT=0,CONNTL=000000,
LEVEL0=0&&999
• Activate call data recording per station on TTY:
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
Charge Output to DPS via WAML Board
ACT-SELS:SELGRNO=1;
• Add dialog field with periodic jobs (with 3 retrieval times):
ADD-
GETAB:TYPE=L,DIAFNO=1,DEV=DEV1,TARIF=TARIF01,STAT=0101010000
,STADAY2=15,STADAY3=1U,STAHR2=0,STAHR3=0,PERIOD=1M
,STNO=STN,DEL=N;
• Add the dialog field without specifying the retrieval time: 
The first output takes place immediately after the add and the following
outputs are interactively controlled (second selection by short dialog).
ADD-GETAB:TYPE=L,DIAFNO=2,DEV=DEV1,TARIF=TARIF01,STAT=0
,STNO=STN,DEL=N;
67.4 Charge Output to DPS via WAML Board

The OpenScape 4000 is connected to an external Ethernet via a WAML board.
The computer PCD127 (ACom PC) which should be connected to the
OpenScape 4000 via this network is located in this LAN.
The following assumptions apply to this example:
• Computer PCD127 and the OpenScape 4000 are in the same network.
• This network’s subnet mask: 255.255.255.0
• IP address of the computer PCD127: 158.226.13.21
• IP address of the OpenScape 4000: 158.226.13.242
• ISDN calling number of the WAML: 55005
67.4.1 Adding the WAML Board
67.4.1.1 AMO DIMSU
Allocate Flexama memory for WAML configuration data:

ADD-DIMSU:TYPE=SYSTEM,WAML1=1;
67.4.1.2 AMO BCSU
Add the configuration of the WAML board (slot: 1-2-49)

ADD-BCSU:TYPE=PER,LTG=1,LTU=2,SLOT=49,PARTNO=Q2205-
X,FCTID=1,LWVAR=0;
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
If the board does not start operating as soon as it is added, you must pull it out
and then re-insert it.
67.4.1.3 AMO DIMSU
Add and change the database layout:

ADD-DIMSU:TYPE=APPLICAT,ACDMONID=1000;
67.4.2 Configuration for TCP/IP
67.4.2.1 AMO WABE
Add ISDN calling number of the WAML:

67.4.2.2 AMO LANC
• Add the global parameter table:

ADD-
LANC:LTG=1,LTU=2,SLOT=49,TABTYPE=GLOBAL,STNO=55005,LANHW=WEST
ERN
,ACTNETIF=ATLLAN&EXTLAN1,FIREWALL=NONE,ADPISDN=PROXY
,ADPELAN=PROXY;
• Add the external LAN interface:
ADD-LANC:LTG=1,LTU=2,SLOT=49,TABTYPE=NETWORK,NETNAME=EXTLAN1
,IPADR=158.226.13.242,IPNMASK=255.255.255.0;
• Load the WAML configuration data:
EXEC-LANC:LTG=1,LTU=2,SLOT=49;
67.4.2.3 AMO CPTP
• Add the DPS connection to the PCD127:

ADD-CPTP:TYPE=DPCON,NO=1,DPPROC=PCD127,IPNO="158.226.13.21";
• Assign the TCP/IP ports to the DPS applications (DPS-controlled connection
setup)
ADD-
CPTP:TYPE=APPL,NO=1,EMSAPPL=LANDGV,DPPROC=PCD127,DPAPPL=LANDG
V
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
,MSGBASED=YES,LOCPORT=102,FARPORT=811,LOCTSAP=DGV811
,FARTSAP=FDGV811;
ADD-
CPTP:TYPE=APPL,NO=2,EMSAPPL=LANGUE,DPPROC=PCD127,DPAPPL=LANGU
E
,MSGBASED=YES,LOCPORT=102,FARPORT=812,LOCTSAP=GUE812,
,FARTSAP=FGUE812;FAMOS ADD-
CPTP:TYPE=APPL,NO=3,EMSAPPL=FAMOS,DPPROC=PCD127,DPAPPL=LANFAM
ADD-
CPTP:TYPE=APPL,NO=3,EMSAPPL=FAMOS,DPPROC=PCD127,DPAPPL=LANFAM
,MSGBASED=YES,LOCPORT=102,FARPORT=813,LOCTSAP=FAM813
,FARTSAP=FFAM813;
ADD-CPTP:TYPE=APPL,NO=99,EMSAPPL=FAMOS,DPPROC=PCD127
,DPAPPL=COMFAM,MSGBASED=YES,LOCPORT=102,FARPORT=5000
,LOCTSAP=SRC,FARTSAP=DST;
67.4.2.4 AMO FAMOS
Activate FAMOS (remote AMO activation). Use $fam to activate FAMOS on line
2 (ACom) and $famend to deactivate it.
ACT-FAMOS:TYPE=FAMOS;
67.4.3 Direct Call Data Exchange Between

OpenScape 4000 and ACom PC
• Allow ACom G0 commands (ACL-specific environment):
CHA-ZAND:TYPE=CIT,FECCSDEV=50;
• Enable the feature: call data recording for internal traffic
CHA-FEASU:TYPE=A,CM=CDRINH;
• Set the call data recording features (feature array):
ADD-FEACG:CM=CDRATND&CDRCDUMP&CDRCDIS;
• Add the call data recording file CDRC1:
ADD-DAGR:FILE=CDRC1,NO=35000;
• Add the device allocation table (DPS to ACom):
ADD-GEZU:TBL=DP,NAMEOUT=DP,PHDEV=V24HDLC,DEVCL=HDLC
,EMSAPPL=LANGUE,DPNAME=PCD127,DPAPPL=LANGUE;
• Add selection group 3 with selection table 1:
ADD-SELG:TBL=SELG,SELGNO=3,RESOP=N,BASDEV=DPS,RESDEV=NODEV
,BLBAS=1,BLRES=0;
ADD-
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
SELG:TBL=SELT,SELGNO=3,SELTABNO=1,FORMBAS=FORM04,FORMRES=NOFO
RM
,TARIF=TARGR01,DESTCNT=A22,CDRCD=0&&15,SERVICE=VOICE
,ATNDGR=0&&999999,CTYPE=ALL,PAYPARTY=ALL,CDRC=N,CDRSTA=N
,THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,CDRAC=N,SFSETUP=N,CDBAD=
N
,CDRULTE=N,CONNT=N,PCODE=N,PPCF=N,STATAB1=N,STATAB2=N
,DNOTBL1=N,DNOTBL2=N,CDRULT=0,CONNTL=000000,
LEVEL0=0&&999
ACT-SELS:SELGRNO=3;
• Add output format table 4:
,FORMAT="~~~#@@@*#@@@@@@@*#@*#@@@@@@@@@@@@@@@@@@@@@*#@:#@:#";
,FORMAT="@*#@@@-#@-#@*#@:#@:#@*#@@@-#@-
#@*#@:#@:#@*#@@@@@*#";
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=3,END=N,FORMAT="@@@@@@@*#";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=RECNO
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=CHRGEE,FILLTY
PE=CHAR
,FILLER=" ",FLDALIGN=R;
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=3,FLDNAME=ROUTCN,FILLTY
PE=CHAR
,FILLER="0",FLDALIGN=R;
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=DESTPTY,FILLT
YPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=5,FLDNAME=CONHOUR,FILLT
YPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=6,FLDNAME=CONMIN,FILLTY
PE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=7,FLDNAME=CONSEC,FILLTY
PE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=8,FLDNAME=STYEAR,FILLTY
PE=CHAR
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=9,FLDNAME=STMONTH,FILLT
YPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=10,FLDNAME=STDAY,FILLTY
PE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=11,FLDNAME=STHOUR,FILLT
YPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=12,FLDNAME=STMIN,FILLTY
PE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=13,FLDNAME=STSEC,FILLTY
PE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=14,FLDNAME=ENDYEAR,FILL
TYPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=15,FLDNAME=ENDMONTH,FIL
LTYPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=16,FLDNAME=ENDDAY,FILLT
YPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=17,FLDNAME=ENDHOUR,FILL
TYPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=18,FLDNAME=ENDMIN,FILLT
YPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=19,FLDNAME=ENDSEC,FILLT
YPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=20,FLDNAME=TKNOLIST,FIL
LTYPE=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=21,FLDNAME=PIN,FILLTYPE
=CHAR
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=22,FLDNAME=SELGRUNO,FIL
LTYPE=CHAR
,FILLER=" ",FLDALIGN=R;
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
67.4.4 ACom ACL Communication

ACom is a program for using the OpenScape 4000 ACL feature.
The following features are used:
• ECCS External DPS-controlled call setups
• FAMOS Remote AMO activation
• FT File transfer
• CCT Call charge data transfer
• TDS Telephone data service
The program is implemented as a 32-bit application and released for the

Microsoft Windows NT 4.0 operating system.
67.4.4.1 ACom Configuration
ACom is controlled via the configuration file acom32.ini which is provided by

default in the Windows NT 4.0 system directory. This file is only read when the
program starts. As a result, changes to the configuration are not effective until
after a restart.
• ACom configuration file acom32.ini

The following links are set up:
• Link 0: ECCS link
• Link 1: Charges link
• Link 2: FAMOS link

The most important entries in the sections ACOM, TCP_PBX.DLL, WFAM,
and LEX are:
[ACOM]
;Path to the PBX driver
pbx=e:\ACom32cp_pbx32.dll

;FAMOS remote AMO activation
objekt1=e:\ACom32\wfam32.dll
;Charge test via ApplicationsConnectivityLink
objekt2=e:\ACom32\gacl.dll
;File transfer between ACom PC and OpenScape 4000
;objekt3=e:\ACom32\fta32.dll
;OpenScape 4000 version inquiry
;objekt4=e:\ACom32\vers32.dll

[TCP_PBX.DLL]
;Interval between connection test, in seconds
PINGINTERVALL=5
;Length of connection test, in milliseconds
A31003-H3170-S103-6-7620, 02/2019
Call Charge Output
PINGTIMEOUT=500

;SYSTEM 80X03

;First link on connection 0, local port 811
C0_LINK0=158.226.13.242:811
C0_LINK0_S=DGV811
C0_LINK0_D=FDGV811

;Second link also on connection 0, local port 812
C0_LINK1=158.226.13.242:812
C0_LINK1_S=GUE812
C0_LINK1_D=FGUE812

Third link also on connection 0, local port 813
C0_LINK2=158.226.13.242:813
C0_LINK2_S=FAM813
C0_LINK2_D=FFAM813

[WFAM]
LINK02=FAM:OpenScape 4000
AUTO_LOGIN

[LEX]
Link2=FAM

[Connection Description]

0=80X03

[OpenScape 4000Version]
Password=OpenScape 4000
67.4.4.2 Ticket Output in the Output Window of the ACom User

Interface
Operating information:
• You must set the link with <Alt>+<2> (charge link (ACL-L1)).
• You must set up the FTBL output format (in this case: FORM04).
• The first data record from the CDRC2 file is transmitted to the ACom PC
with the string A003.
• The PC (ACom) must acknowledge each call data record that is received
with A1011. Only then will the next call data record be sent from the
CDRC1 file.
• The string AC01 is sent if there are no more data records in the CDRC1
file; this must also be acknowledged with the string A1011.
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_etd_en.fm
Overview
68 Call Charge Recording-Elapsed Time Display
68.1 Overview
01:03:22
The ETD feature takes priority

over the CDRSTN feature.

Display of elapsed time at station terminal during incoming or outgoing trunk calls.
68.3 User Interface

It is possible to display the time elapsed (parameter ETD in AMSO SDAT) instead
of the call charges (parameter CDRSTN in AMO COSSU) at the station terminal
during incoming or outgoing trunk calls. While CDRSTN is set up through the
COS, ETD is set up on a per-subscriber basis with ETD taking priority over
CDRSTN. This means that if both parameters are configured, the display shows
the time elapsed and not the call charges recorded.

No special requirements.
Time is displayed in the format 00:00:00, i.e. hh:mm:ss.

Activation:
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_etd_en.fm
Relevant AMOs
CHANGE-SDAT:STNO=<number>, TYPE=ATTRIBUT, AATTR=ETD;

Deactivation:
CHANGE-SDAT:STNO=<number>, TYPE=ATTRIBUT, DATTR=ETD;
68.6 Relevant AMOs

Language
SDAT AMERK d Teilnehmermerkmal ausfügen / deaktivieren
ETD: Anzeige der vergangenen Zeit
DATTR e delete subscriber attribute
ETD: elapsed time display
EMERK d Teilnehmermerkmal einfügen / aktivieren
ETD: Anzeige der vergangenen Zeit
ATTRIB e activate individual subscriber attribute
ETD: elapsed time display
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_geban_en.fm
Flexible Memory Management
69 Central Configuration
Call data recording is activated when charges are shown on the display. The call
data recording tariff tables must be configured to ensure the correct charges
appear on the Digite display. Likewise, you must configure central and line-
dependent data in the SWU using AMOs. The following chapter will show how to
configure the nodes in single and networked communication systems in order to
set a certain charge feature. This chapter uses examples to examine the following
features:
– Activate/deactivate call data recording
– Charge display on the device
The other features (charge output, DPS, etc.) are described in separate AMO
application cases.
IMPORTANT: Charges are only displayed if the data is consistent which means
that the currency is correct and the charge type (amounts/units) corresponds to
what is to be displayed.
69.1 Flexible Memory Management

Buffer memory, the so-called COSTI buffer, is needed in the SWU to save the call
charge data for chargeable connections. The number of COSTI buffers that are
set up after initial startup is dimensioned in such a way that all outgoing trunks
and tie trunks can be recorded with charges.
You must expand the memory if you want incoming connections and/or internal
connections to also have the charges recorded. The same applies if CDR-e is
used:
COMMAND
ADD-DIMSU:TYPE=BASIC,COSTI=<number>;
A31003-H3170-S103-6-7620, 02/2019
Central System Data
69.2 Central System Data
69.2.1 Affected AMOs
69.2.1.1 AMO ZAND
Use the remaining data to define the form of the charge display on the device in
the type branch CCD.
CCUC: Conversion factor = amount per unit; used to calculate units from
amounts (for example, for stations with call charge pulse display)
CDDISPEX: = AMOUNT system with call charge amounts
= UNIT: system with call charge units
CDDISPAT: = 1: 1-line call charge display on attendant console
= 2: 2-line call charge display on attendant console
CDRRINGB: = YES: Call data recording active with end of dialing
= NO: not active
NETPROV: = YES: Save network-provided number for incoming CDR .
= NO: do not save
69.2.1.2 AMO FEASU
Call-charge-specific parameters:
NOCHRG: No charge (valid for MFC-R2 incoming (for example, Switzerland

feature for no-charge troubleshooting services))
DISCHTR, Central activation/deactivation of the call charge display for
DISCHNW, different traffic types (outgoing/incoming CO, outgoing/incoming
DISCHINH: networking, internal). The meaning is described in the following
sections.
CDRIC, CDROGTR, Central activation/deactivation of the call charge display for
CDROGNW, different traffic types (incoming CO/networking, outgoing CO,
CDRINH: outgoing networking, internal). The meaning is described in the
following sections.
CPS: Central activation/deactivation of the call charge pulse
transmission and measurement (RURAL). The meaning is
described in the following sections.
CDRE: Central activation/deactivation of call data recording
enhancements).
A31003-H3170-S103-6-7620, 02/2019
Central System Data
69.2.1.3 AMO FEACG
ADD-FEACG:CM=<param>;
IMPORTANT: If call data recording was not activated with the AMO FEACG, then
only the display is active.
69.2.1.4 AMO CTIME
Call-charge-specific parameters:
DISPCH: Time intervals at which the call charge display is updated.

CDRDISDE: Period of time post-cleardown after which the charge display will be
deleted.
69.2.1.5 AMO KNMAT
You must select the node connection matrix with open numbering. In addition to
the general configuration rules (described in the Networking/Station modification
chapter), you must set up the matrix so that a modification between the own node
and the logical destination node CDR must be entered on those nodes on which
call data recording is active. Enter extensions with the corresponding node ID.
The reason is that a unique station number for the chargeable station is always
provided to the call data recording. In exceptional cases, a shortcut for the logical
destination node CDR can also be selected (if the station numbers get to be too
long, for example).
In addition, you must use the AMO GEFE to inform the call data recording which
of the recorded station numbers should be modified with the networking matrix.
This can be done separately for internal (KNMATINT), incoming (KNMATINC),
and outgoing (KNMATOUT), depending on the type of connection.
For example, the CALLING Party and the KEY LINE USED should be modified
for outgoing connections:
CHANGE-GEFE:TYPPARAM=KNMATOUT,PARTY=CALLIPTY&KEYPTY;
69.2.1.6 AMO KNPRE
With the AMO KNPRE, a national or international (dialing) prefix can be

configured in the "Private" or "ISDN" numbering plan, depending on the DPLN.
A31003-H3170-S103-6-7620, 02/2019
Central System Data
With the AMO GEFE, call data recording can be arranged so that the recorded
station numbers are supplemented by the corresponding prefix, depending on the
DPLN and numbering plan. This can be done separately for internal (PREINT),
incoming (PREINC), and outgoing (PREOUT), depending on the connection
type.
For example: DPLN 0, ISDN numbering plan, national prefix, access code 6, dial
009
ADD-KNPRE:DPLN=0,NPI=ISDN,TON=NATIONAL,EXIT=6,PREFIX=009;
69.2.2 Configuration Commands for Central System

Data
1. Set the node connection matrix with the following AMOs:
In the example in Figure 98, the following is set on physical node 20 (physical
node ID 99):
CHA-ZAND:TYPE=ALLDATA,PNNO=20, PNODECD=99;
CHA-KNMAT:NPI=UNKNOWN,LEVEL=0,ONNOL=OWN,DNNOL=CDR,NUMEXT=99;
CHANGE-GEFE:TYPPARAM=KNMATOUT,PARTY=PAYPTY;
PNNO 200 CO(999) PNNO 400
PNODECD = PNODECD =
92 94
PNNO 20
PNODECD =
99
PNNO 300 PNNO 500
PNODECD = PNODECD =
93 Call data recording 95
Figure 98 Example of network configuration with open numbering
2. The settings (supplements) in the node connection matrix, separated into

connection type internal (KNMATINT), incoming (KNMATINC), or outgoing
(KNMATOUT), do not affect call data recording until, for example, you set the
CALLING party for outgoing connections:
CHA-GEFE:TYPPARAM=KNMATOUT,PARTY=CALLIPTY;
If you want to configure station number cutoff instead of add-on (only
PARTY=CALLEPTY and PARTY=CONNPTY) and the node IDs contain two digits, you
can also do this without KNMAT with the AMO GEFE:
A31003-H3170-S103-6-7620, 02/2019
Tariff Group Tables
CHA-GEFE:TYPPARAM=DN,DNSHORT=Y;
3. Configure the units or amounts with:
Amounts on device:
CHA-ZAND:TYPE=CCD,CDDISPEX=AMOUNT;
or
Units on device:
CHA-ZAND:TYPE=CCD,CDDISPEX=UNIT,CCUC=50; (units on device)
If you want to show units on the display, these are calculated with CCUC from
the amounts used in call data recording and shown rounded off to whole
numbers.
4. Configure the attendant console display with:

two-line call charge display format (more than six digits for station and node
numbers)
CHA-ZAND:TYPE=CCD,CDDISPAT=2;
or
One-line call charge display format (six digits for station number)
CHA-ZAND:TYPE=CCD,CDDISPAT=1;
5. Configure the timer for updating the call charge display on the device with:
CHA-CTIME:TYPESWU=CP1,DISPCH=30,CDRDISDE=10;
In this case, the charges are updated on the display every 30 seconds. The
display is deleted 10 seconds after the call has ended.
IMPORTANT: Section 69.2, “Central System Data”: These settings are valid
for all of a network node’s devices.
69.3 Tariff Group Tables

The tariff group tables contain the tariff table numbers per carrier, per station
category, and per service. This applies to connections with and without call
charge information.
IMPORTANT: Only tarif group table 0 is used for call charge display during a call.
A31003-H3170-S103-6-7620, 02/2019
Tarif Tables
Carrier CATPTY Service

Voice Fax DTE
NORM
SCRSPC
0
PUPHON
MTEQ
...
NORM
SCRSPC
9
PUPHON
MTEQ
When adding tariff group tables, enter the number of the tariff table per carrier,
category, and service.
69.4 Tarif Tables
IMPORTANT: The examples use the old European currencies ATS, DEM, and
LIRE.
Tariff tables with call charge information

The tariffs for connections with call charge information are divided into graduated
tariff ranges, with each graduated tariff range representing a call charge unit limit
up to which the relevant tariff is valid. Each of these tariff tables contains four
graduated tariff ranges, a minimum charge, and a multiplication factor for
amounts (expressed as a per-mill value). The prices should be expressed in 1/
100ths or 1/1000ths of the currency units1The information is expressed in 1/
1000ths of the currency unit if 2T or 3T is set up in the COMPOS (decimal point
position) parameter in the AMO DAVF; otherwise, it is expressed in 1/100ths.
LIMIT_1 PRICE_1
LIMIT_2 PRICE_2
LIMIT_3 PRICE_3
LIMIT_4 PRICE_4
MIN_CHRG
CHRG_FACTOR
1. For an explanation of currency units, see the display characteristics.
A31003-H3170-S103-6-7620, 02/2019
Tarif Tables
If the parameter METHOD = FACTOR is set in a tariff table with call charge
information (WCU) and if call charge information is supplied by the network in the
form of (finished) amounts, the amounts are multiplied by the FACTOR value. The
minimum charge is taken into consideration, but there is no basic charge.
If the calculation is made based on time, the calculated amount is likewise

modified by the multiplication factor (FACTOR) from the WCU table with the same
tariff table number as the WOCU table that is being used.
The costs calculated in this way are taken as the connection costs.
IMPORTANT: The minimum charge is always expressed in 1/100ths of the

currency units, regardless of the DAVF setting.
Tariff tables without call charge information

For connections without call charge information, the tariffs are entered depending
on the time of day and distance.
Zones/Set Day Nigh Nigh Nigh Nigh TAB Chan Min. B-

Value t1 t2 t3 t4 T ge Char Basic CHL
No. ge Char Facto
Perio ge r
d
NO_ENTRY/0
INT 01-09/01- x y x y x y x y x y tt cc bb ff
09 x y x y x y x y x y mm
INC 01-09/11-
19
LOCAL/21
FREE/29
CHINFO/30
NEAR/31
TOLL 01-50/
51-100
ABROAD 01-
99/101-199
TIE 01-09/
201-209
xx: Clock in 1/100ths of seconds

yy: Price for this clock in 1/100ths, 1/1000ths, or 1/100000ths of the currency
units1 (e.g., pennies, tenths of a penny or thousandths of a penny. It depends
on the GEN (COMPOS) setting).
1. For an explanation of currency units, see the display characteristics.
A31003-H3170-S103-6-7620, 02/2019
Tarif Tables
tt: Number of segmentation table (1-25)

cc: Boolean value
(FALSE): The time-of-day segment for the start of the call applies during
the entire connection, which means that if the segment changes, the
change is ignored.
(TRUE): If the time-of-day segment changes, the call duration is split up,
which means that the costs are evaluated according to the each
applicable time-of-day segment.
mm: The minimum charge for a call, in hundredths of currency units.
bb: The basic charge of a connection, always in hundredths of currency units.
ff : Multiplication factor per B channel used (in percent, 100% means multiply 
by 1).
Five tariff ranges can be assigned to the various distance zones. The costs are
calculated according to the particular applicable segment. A basic charge and a
minimum charge can be specified.
In the tariff tables without charge information, you can specify the distance zone
and the day, night1, night2, night3, and night4 tariffs (yy) per clock (xx) that apply
to this zone. Specify the clock in 1/100 seconds, the day and night tariffs in 1/
100ths, 1/1000ths or 1/100000ths of the currency units, depending on the
settings in the GEN branch and the COMPOS parameter.
The basic charge (bb) can be either positive or negative. The negative charge
facilitates calculating the first n seconds of the call duration at no charge
(exemption). As long as the costs that accrue are negative, the display shows
costs = 0.
The division of the call duration into time of day segments is done in the time of
day segmentation tables. You must specify the number of the segmentation table
(tt) that is to be used (see AMO TABT). The value for the segment change (cc)
indicates whether or not a segment change during a call is taken into
consideration.
When calculating costs, the call duration is divided into clocks based on the
segment that applies at the beginning of the call and the current zone. The
number of clocks in each segment determined in this way is multiplied by the
current tariff (price), and then these values are added together. If there has been
a change in the segment during the call, this is taken into account, depending on
the value assigned for the segment change. After this, the basic charge is added
on or deducted. If the calculated costs are greater than zero and less than the
minimum charge, the minimum charge is taken as the cost of the connection.
Output format:
The calculated costs are output according to the selectable display
characteristics in the AMO TBBL/branch GEN (associated with the respective
tariff table).
A31003-H3170-S103-6-7620, 02/2019
Tarif Tables
The display characteristics are:
1. Decimal point position: indicates the position of the decimal point (-3 to 3, 2T,
3T 2HT and 3HT
Examples:
Decimal point position: 3 Value: 30558 Output: 305.580

Decimal point position: 0 Value: 30558 Output: 306
Decimal point position: -1 Value: 30558 Output: 3056
Decimal point position: 2T (rounding) Value: 30558 Output: 30.56
Decimal point position: 3T Value: 30558 Output: 30,558
Decimal point position: 2HT (rounding) Value: 30558 Output: 0.31
Decimal point position: 3HT (rounding) Value: 30558 Output: 0,306
2. Currency identifier: Character string, for example, DEM, ATS, USD, etc.
Table with clock information

There are nine tariff tables with pulse time clocks available for setting the call
charge pulses for analog stations that transmit call charge pulses or coin-
operated phones.
Zone DAY NIGHT1 NIGHT2

Fix First Perio Fix First Perio Fix First Perio
d d d
LOCAL xx yy zz xx yy zz xx yy zz
NEAR
TOLL01-50
ABROAD1-99
...
TIE01-09
ZONE NIGHT3 NIGHT4 SEGTB CHPE

LNO R
Fix First Perio Fix First Perio
d d
LOCAL xx yy zz xx yy zz tt cc
NEAR
TOLL01-50
ABROAD1-99
...
A31003-H3170-S103-6-7620, 02/2019
Tarif Tables
ZONE NIGHT3 NIGHT4 SEGTB CHPE

LNO R
Fix First Perio Fix First Perio
d d
TIE01-09
xx: Basic charge: No or one or more call charge pulses are created as the
basic charge and sent immediately. Pulses are not sent periodically (0-15).
yy: Time after which the first pulse is sent (in 10 ms):
• (0): No first call charge pulse is sent.
• (>0): A first charge pulse is sent after n * 10 ms (1-999999)
• (KA) Karlsson added method: The basic charge (xx) is automatically set
to 1. A pulse is sent immediately. The next pulse is sent after a random
period of time that lies within the configured time period (zz). The pulses
are then sent periodically according to the set time period (zz).
• (KM) Karlsson modified method: The basic charge (xx) is automatically

set to 1. A pulse is sent immediately. The next pulse occurs after a
random time, which lies between the configured time period (zz) and this
value doubled (2*zz). The pulses are then sent periodically according to
the set time period (zz).
• (K) Karlsson method: The basic charge (xx) is automatically set to 0. The
first pulse is sent after a random period of time which lies within the
configured time period (zz). The pulses are then sent periodically
according to the set time period (zz).
zz: Length of period for periodic pulses (in 10 ms).
tt: Number of the segmentation table.
cc: Identifier for time-of-day segment change for connections without call
charge information
Boolean value:
(FALSE): The time-of-day segment for the start of the call applies during the
entire connection, which means that if the segment changes, the change is
ignored.
(TRUE): If the segment changes, the call duration is split up, which means
that the costs are evaluated according to the segment that applies in each
case.
Calculation of costs
The calculation of the costs (with call charge information) is made in 1/100ths of
currency units if the parameter COMPOS in the AMO DAVF is neither 2T nor 3T.
The currency unit is the currency with the specified currency identifier. This
setting corresponds to a decimal point position 2. For example, a calculated
amount of 30558 corresponds to costs of 305.58 currency units.
A31003-H3170-S103-6-7620, 02/2019
Tarif Tables
If the decimal point position in the AMO DAVF is either 2T or 3T, the calculation
is expressed in 1/1000ths of currency units. If the calculated costs total 30558,
the display will show the amount 30.56 if COMPOS =2HT and 30.559 if
COMPOS=3HT. This only applies if the calculation is made according to the WCU
branch of the AMO TTBL.
Positive decimal point positions only influence the number of positions after the
decimal point that are to be displayed, but not the value or amount. As a result,
all tariff entries must be specified in 1/100ths of currency units if COMPOS is 0 to
+3. If COMPOS is 2T or 3T, then entries must be expressed in 1/1000ths.
You can enter values in the range 0000 - 9999 for tariff information (TARMIN,
TARIF1, etc.).
Negative decimal point positions indicate output without a decimal point and a
shifting of the decimal point by 1 to 3 places to the right (this corresponds to
division by 
10 decimal point position). This means that if the decimal point position is -1, the value
30558 corresponds to the amount 
305.58/10-1 = 3056, if the decimal point position is -2, to the amount 305.58/10-2
= 30558, etc.
When calculating by zone, the decimal point position is configured individually for
the tariff table. the decimal point position is administered in the GEN branch in the
same way as when using the AMO DAVF. If the decimal point position equals -3,
-2, -1, 0, +1, +2 or +3, costs are calculated in 1/100ths of currency units. If the
decimal point position is 2T or 3T, costs are calculated in 1/1000th of currency
units, and if the decimal point position is 2HT or 3HT, costs are calculated in 
1/100000ths of currency units.
The minimum charge (TARMIN) and the basic charge (TARBAS) continue to be
expressed as 1/100ths of currency units.
IMPORTANT: The value of the decimal point position applies only to the
assigned tariff table. If different tariff table numbers are specified for the display
output (tariff group 1) and the data record (tariff group from the selection group),
you must set the decimal point position for both tariff tables.
Example 1:
One call charge unit costs 12.1 pennies. 
Input: TARIF = 0121 (00.121 DEM), decimal point position 3, currency
identifier = ’DEM’. The COMPOS parameter in the AMO DAVF is 2T or 3T.
Example 2:
90 seconds’ call duration at the day tariff costs 3.6 ATS. 
Input: TARDAY = 0360 (03.60 ATS), INTDAY = 9000 (in 1/100ths of seconds),
decimal point position 1 or 2, currency identifier = ’ATS’. The COMPOS
parameter in AMO TTBL is +2.
A31003-H3170-S103-6-7620, 02/2019
Tarif Tables
Example 3:
One call charge unit costs 812 Lire. You must enter the parameter TARIF =
81200 (812.00 Lire). This is not possible because only four-digit values are
allowed.
Solution: Decimal point position -1 is configured, then TARIF = 8120. This is
81.20 Lire, but the output is multiplied by 10 because of the negative decimal
point position.
Example 4:
One call charge unit costs 1350 Lire. You must enter the parameter TARIF =
135000 (1350.00 Lire). 
Solution: Decimal point position -2 is configured, then TARIF = 1350. This is
13.50 Lire, but the output is multiplied by 100 because of the negative decimal
point position.
• Add a tariff group as follows:

ADD-TTBL:TBL=GRP,GROUPNO=0,CARRIER=0,SERVICE=VOICE
,TARTBLNO=1,CATPTY=NORM;
ADD-TTBL:TBL=GRP,GROUPNO=0,CARRIER=1,SERVICE=VOICE
,TARTBLNO=1,CATPTY=NORM;
• Create the tariff table with call charge information as follows:
(no minimum charge, cost factor 100%, 1 charge unit should cost 50/
100ths of the currency units).
• Add the tariff table without call charge information as follows:
ADD-TTBL:TBL=WOCU,TARTBLNO=1,ZONE=INT01,INTDAY=10
,TARDAY=100,INTNT1=10,NTAR1=100,INTNT2=10,NTAR2=100
,INTNT3=10,NTAR3=100,INTNT4=10,NTAR4=100,TARBAS=0
,TARMIN=0,SEGTBLNO=1,CHPER=Y;
ADD-TTBL:TBL=WOCU,TARTBLNO=1,ZONE=DIST01,INTDAY=10
,TARMIN=0,SEGTBLNO=1,CHPER=Y;
ADD-TTBL:TBL=WOCU,TARTBLNO=1,ZONE=INC01,INTDAY=10
,TARMIN=0,SEGTBLNO=1,CHPER=Y;
• Add the segmentation table (T=day tariff, N1 = night tariff 1, N2 = night
tariff 2) as follows:
ADD-TABT:LT=06-00,TARTYPMO=NTAR2,TARTYPTU=NTAR2
,TARTYPWE=NTAR2,TARTYPTH=NTAR2,TARTYPFR=NTAR2,TARTYPSA=NTA
R2
A31003-H3170-S103-6-7620, 02/2019
Call Data Recording for Outgoing Connections
,TARTYPSU=NTAR2,SEGTBLNO=1; 
R1
,TARTYPSU=NTAR2; 
ADD-TABT:LT=14-
00,TARTYPMO=DTAR,TARTYPTU=DTAR,TARTYPWE=DTAR
,TARTYPTH=DTAR,TARTYPFR=DTAR,TARTYPSA=DTAR,TARTYPSU=NTAR2;
ADD-TABT:LT=18-
00,TARTYPMO=DTAR,TARTYPTU=DTAR,TARTYPWE=DTAR
,TARTYPTH=DTAR,TARTYPFR=DTAR,TARTYPSA=NTAR2,TARTYPSU=NTAR2
; 
R2
,TARTYPSU=NTAR2; 
R2
,TARTYPSU=NTAR2;
• Add the display characteristics for on the display and on the ATND as
follows:
with call charge information:
CHANGE-DAVF:COMPOS=+2,NAME="DM";
without call charge information:
CHA-TTBL:TBL=GEN,ELEMENT=COMPOS,TARTBLNO=1,COMPOS=3HT;
69.5 Call Data Recording for Outgoing Connections

Call data recording for outgoing connections (trunk and tie traffic) is always
configured using Least Cost Routing (LCR) parameters. The VOICE/FAX and
DATA services are normally handled in the same way as far as charges are
concerned. Because you can configure LCR separately depending on the
service, you can also assign another cost parameter to each service.
Configuration commands:
1. Activate the feature for outgoing trunk calls (including charge display) as
follows:
CHANGE-FEASU:TYPE=A,CM=CDROGTR&DISCHTR;
2. Activate the feature for outgoing tie traffic (including charge display) as
follows:
CHANGE-FEASU:TYPE=A,CM=CDROGNW&DISCHNW;
3. Assign the LCR charge parameters as follows:
A31003-H3170-S103-6-7620, 02/2019
CHA-LDAT:LROUTE=<number>[,LSVC=VCE],LRTEL=<number>,CARRIER=1
,ZONE=LONG01,LATTR=WCHREG;
Explanation of important parameters:
CARRIER: Network operator

ZONE: Distance zone (EMPTY=no charges); you must configure the ZONE
with the AMO TTBL
LATTR: WCHREG activates call data recording for this routing element (see
examples in Section 69.10, “Examples”).
NOTRANS deactivates call data recording in all transit nodes in the
route; only the charges reported by the CO are sent back to the source
node (see example in Section 69.10.1, “Internal Call Data Recording in
the Network”).
EODSTCDR starts call data recording right after the end of dialing.
INTCHARG treats outgoing tie connections as internal connections
(see example in Section 69.10.1, “Internal Call Data Recording in the
Network”)
NOCHDISP suppresses the call display in the source node if an
"expensive" route is used on the way to the destination node (e.g.,
overflow into the CO) (see example in "Section 69.10.2, “Tie Traffic with
Incoming Charges and Trunk Traffic in Transit”").
4. Define COT with the DPRE class of service and assign it to the trunk and tie
circuits. DPRE causes the prefix digits to be added to the destination number
that is sent to call data recording. This setting takes effect when an overflow
trunk group is seized via a toll line.
If the network nodes have different ZAND settings for CDDISPEX (unit/
charge), you must assign a COT with/without TRSC parameter to the trunk in
the transit node (see example in Section 69.10.2, “Tie Traffic with Incoming
Charges and Trunk Traffic in Transit”).
If TRSC is set, charges are sent on this line in the direction of the source
node; these can be displayed there, e.g. without ongoing call data recording.
If TRSC is not set, then units are sent. This parameter works only in a
connection’s transit node.
CHA-COT:COTNO=15,COTTYPE=COTADD,PAR=DPRE;
CHA-COT:COTNO=15,COTTYPE=COTADD,PAR=TRSC; (only in transit node)
CHA-TDCSU: PEN=<g-uu-bbb-sss>,COTNO=15;
5. Define the class of service (COS) with CDRSTN authorization and assign it
to the stations at which the charges should be displayed. Assign the COS to
the station with the AMOs ACSU, SCSU, SBCSU; you must also use the
AMOs TACSU, TSCSU, TDCSU to assign it to a circuit whose protocol cannot
transmit the classmarks.
CHA-COSSU:TYPE=COS,COS=5,AVCE=CDRSTN,AFAX=CDRSTN,ADTE=CDRSTN;
CHA-SCSU:STNO=<number>,COS1=5,COS2=5;
A31003-H3170-S103-6-7620, 02/2019
Explanation of the following tables.

Table 49: In addition to the charges calculated in the separate node, it is also
possible to receive call charge information from the line. Table 49 shows what
affect the LCR parameters (AMO LDAT) have in this regard.
Table 50: If charges are received from the line, they are displayed according to
this table. The charges were calculated in foreign nodes or they originate with the
CO. The influence of activated call data recording is limited to a possible
conversion of units into amounts or vice versa.
Table 51: If call data recording is activated and no charges are received from the
line, the charges are calculated and displayed according to Table 51.
IMPORTANT: Calculated charges are not added to charges that were received
from the line. Charges from the line are always dominant.
Combination of LRTEL parameters Effect

ZONE LATTR LATTR
=WCHREG =NOTRANS
EMPTY yes No calculation of costs using cost
parameters, costs are calculated based on
call charge information over the line (trunk
traffic). Conversion of pulses <-> charges is
possible.
Charges from the line:
no All types (trunk, tie) are possible.
yes Only trunk traffic from remote systems is
possible.
not EMPTY yes Calculation of costs using cost parameters,
calculation of costs based on charges via the
line are dominant.
possible.
any no No call data recording is activated, charges
from the line can be displayed but not
converted. 
Important: Note TRSC in the transit nodes.
possible.
Table 49 Combination of LRTEL parameters and their effect (outgoing

connections)
A31003-H3170-S103-6-7620, 02/2019
AMO FEASU AMO Meaning

COSSU
(Axxx=authorization for specific service)
CM= CM= Axxx =
DISCHN DISCHTR DIDB
W
yes any yes Charges displayed on the station display
any yes
any any no No charges whatsoever displayed on the
station display
no no any
Table 50 AMO FEASU and AMO COSSU parameter (outgoing connections)
A31003-H3170-S103-6-7620, 02/2019

COSS
U (Axxx=authorization for
specific service)
CM = CM= CM= CM= Axxx =
CDROGN CDROGT DISCHN DISCHTR DIDB
W R W
yes yes yes yes yes Trunk and networking call data
is recorded for the station and
all charges are displayed.
yes no yes any yes Networking call data is
recorded for the station and
charges are displayed.
No trunk charges.
no yes any yes yes Trunk call data is recorded for
the station and charges are
displayed.
No networking charges.
yes yes no yes yes Trunk and networking call data
is recorded for the station, only
trunk charges are displayed.
yes yes yes no yes Trunk and networking call data
is recorded for the station, only
networking charges are
displayed.
yes yes any any no Trunk and networking charge
data is recorded for the
station, but no charges are
displayed.
yes no any any no Networking call data is
recorded for the station, but
not trunk call data; no charges
are displayed.
no yes any any no Trunk call data is recorded for
the station but networking call
data is not, and no charges are
displayed.
no no any any any Call data is not recorded for
any station and no charges are
displayed.
Table 51 AMO FEASU and AMO COSSU parameter (outgoing connections)
IMPORTANT: CDRSTN=no has the same effect as 

DISCHNW=no and DISCHTR=no and CDRSTN=any.
A31003-H3170-S103-6-7620, 02/2019
Call Data Recording for Incoming Connections
69.6 Call Data Recording for Incoming Connections

Cost parameters for incoming connections are assigned to the circuit (trunk)
using the parameters CARRIER and ZONE in the AMOs TACSU, TDCSU, and
TSCSU.
• CARRIER: Network operator
• ZONE: distance zone (INC01 to INC09, EMPTY); you must configure the
ZONE with the AMO TTBL 
Expand the circuit parameters (AMO COT) for incoming connections by four
values relating to charges:
• ICZL: Incoming call data recording via the zone or the line
• ICZO: Incoming call data recording exclusively via the zone
• CATR: Transfer charges in the transit node. CATR works in the transit node if
the incoming and outgoing circuits are analog circuits and charges should be
passed on in transit. CATR is not a part of the INCDR feature; it was
introduced for the China feature. With INCDR, charges are always transferred
in transit for digital lines.
• TRSC: Line with amounts (instead of units). TRSC works when there are
digital lines in transit. Because charges for incoming connections are not
transferred in transit, TRSC is explained in Section 69.5, “Call Data
Recording for Outgoing Connections”.
IMPORTANT: Because of outgoing connection handover with call data recording

in the remote system, the table for outgoing connections applies, in spite of the
incoming seizure (see Table 52, Figure 99).
AMO FEASU AMO COSSU Meaning

CM=DISCHNW Axxx = CDRSTN
(Axxx=authorization for specific service)
yes yes Charges displayed on the station display
no yes No charges whatsoever displayed on the station
display
any no
Table 52 AMO FEASU and AMO COSSU parameters (incoming connections)
An incoming, transferred connection is shown in Figure 99: The original

chargeable connection from node 1 to node 2 (e.g., CO) is transferred to a station
in node 3, where it is an incoming connection. Nevertheless, the charge-related
A31003-H3170-S103-6-7620, 02/2019
memory areas (COSTI buffers) must be created as with an outgoing connection.

For this reason, you must set up DISCHNW (for the call detail memory) and
CDRSTN (for the station) in node 3.
Connect.transferred 3
1st connection
Figure 99 Example of an incoming transferred connection
1. Activate the feature for incoming trunk and tie traffic (including call charge
display) as follows:
CHA-FEASU:TYPE=A,CM=CDRIC&DISCHTR&DISCHNW;
2. Set the COT parameter as follows:
CHA-COT:COTNO=15,COTTYPE=COTADD,PAR=ICZO;
3. Change the trunk configuration as follows:
CHA-TDCSU:PEN=<g-uu-bbb-sss>,COTNO=15,CARRIER=1,ZONE=INC01;
Table 53 shows the effect of the COT parameters ICZL and ICZO in
combination with the trunk AMO parameters CARRIER and ZONE.
4. Define the class of service (COS) with CDRSTN authorization and assign it
to the stations at which the charges should be displayed. Assign the COS to
the station with the AMOs ACSU, SCSU, SBCSU, but you must also assign
it to a circuit whose protocol cannot transfer the classmarks with the AMOs
TACSU, TSCSU, TDCSU.
A31003-H3170-S103-6-7620, 02/2019
AMO AMO COT Effect

TxCSU
ZONE ICZL ICZO
not yes no Calculation of costs using cost parameters,
EMPTY calculation of costs based on call charge
information via the line are dominant.
no yes Calculation of costs using cost parameters
(ZONE).
EMPTY yes no No calculation of costs using cost parameters, but
instead calculation of costs based on call charge
information via the line.
no yes Call detail recording without calculation of costs.
any no no No call data recording.
Table 53 AMO TxCSU ans AMO COT parameters (incoming

connections)
Table 54 shows how the AMO FEASU settings and the CDRSTN station
authorization affect the call data recording.

COSSU
(Axxx=authorization for specific
CM=CD CM= CM= Axxx
service)
RIC DISCHN DISCHTR =CDRST
W N
yes yes yes yes Trunk and networking call data is
recorded for this station and all
yes no yes yes Trunk and networking call data is
recorded for this station and the trunk
yes yes no yes Trunk and networking call data is
recorded for this station and
networking charges are displayed.
yes any any no Trunk and networking call data is
recorded for this station but no
yes no no any
no any any any Call data is not recorded for any
station and no charges are displayed.
Table 54 AMO FEASU and AMO COT parameters (incoming

connections)
A31003-H3170-S103-6-7620, 02/2019
Call Data Recording for Internal Node Connections
69.7 Call Data Recording for Internal Node Connections

Cost parameters are allocated to traffic restriction groups (ITR groups) for internal
connections within the node. The AMO TRG is used to assign the cost parameter
ZONE (INT01 to INT09) to the ITR groups and the cost parameter of the ITR
group of the chargeable station (A station) is used for call detail recording. You
must have added the ZONE with the AMO TTBL.
1. Activate the feature for internal traffic (including display of the charges) with:
CHANGE-FEASU:TYPE=A,CM=CDRINH&DISCHINH;
2. Define the class of service (COS) with CDRING and CDRSTN authorizations
and allocate them to the stations with the station AMOs ACSU, SCSU,
SBCSU.
CHA-
COSSU:TYPE=COS,COS=5,AVCE=CDRINT&CDRSTN,AFAX=CDRINT&CDRSTN
,ADTE=CDRINT&CDRSTN;
CHA-SBCSU:STNO=<number>,COS1=5, COS2=5;
3. Assign the ZONE to the ITR groups as follows:
ADD-VBZGR:GROUP=0,TYPE=CHRGINT,ITRGRB=0,ZONE=INT01;
4. Activate internal call data recording from the end-of-dialing as follows:
CHA-ZAND:TYPE=CCD,CDRRINGB=YES;
5. A dummy trunk group code (DDDDDD) is generated for the internal call data
recording data record. This data record is output only if the parameter
CDRCD in the AMO SELG is set to 0&&999999.
CHA-
SELG:TBL=SELT,SELGNO=<number>,SELTABNO=<number>,CDRCD=0&&9999
99;
6. To suppress call data recording advisories (F4066), set up a dummy LTG 99
in the AMO FBTN.
ADD-FBTN:TBL=TRKNO,LTG=99,LTU=1,SLOT=25,CCT=0,BCHAN=<number>
,VTRKNO=999999;
Costs are calculated depending on the FEASU settings and the CDRSTN
authorizations. Table 55 shows the effect of the corresponding settings.
A31003-H3170-S103-6-7620, 02/2019
Call Charge Display at the Attendant Console
AMO FEASU AMO COSSU AMO Meaning

VBZG
R (Axxx=authorization for specific
service)
CM= CM= Axxx= Axxx = ZONE
CDRIN DISCHIN CDRIN CDRS
T H T TN
yes yes yes yes not Call data is recorded for this station,
EMPT charges are recorded and displayed.
Y
yes yes yes no not Call data is recorded for this station,
EMPT charges are recorded but not
Y displayed at this station.
yes no yes any not Call data is recorded for this station,
EMPT charges are recorded but not
Y displayed at any station in the node.
yes any yes any EMPT Call data is recorded for this station, no
Y charges are recorded or displayed.
yes yes no any any No call data is recorded for this station,
no charges are displayed.
no any any any any Call data is not recorded for any
station in the node, no charges are
displayed.
Table 55 AMO FEASU and AMO COT parameters (internal node

connections)
69.8 Call Charge Display at the Attendant Console

After a call has ended, you can have the charges for the call displayed at the
attendant console (ATND) for any station, with or without display (no in-progress
charges).
To do this, you must have activated the feature centrally and the station must
have CDRATN authorization.
This applies to all types of charges. The station can also have CDRSTN
authorization, in which case the in-progress charges are displayed as described
in the previous chapters.
1. The CDRATN feature (AMO FEASU) is always activated.
2. Define the class of service (COS) with CDRATN authorization and assign it to
the stations for which the charges should be displayed at the attendant
console as follows:
CHA-COSSU:TYPE=COS, COS=5,AVCE=CDRATN:
A31003-H3170-S103-6-7620, 02/2019
CDR Records, Central and per Station
69.9 CDR Records, Central and per Station

Charges that have accumulated for a station can be reported to the charge output
either centrally for each system or on a station-specific basis. This applies to all
accumulated charges (incoming/outgoing, trunk/networking/internal).
1. Charges reported per station to charge output:
CHA-COSSU: TYPE=COS, COS=5,AVCE=CDRS;
2. Charge output receives charges centrally for the system instead of on a
station-specific basis:
CHA-COSSU:TYPE=COS,COS=6, AVCE=CDRC;
3. Assign COS to station numbers with one of the station AMOs:
CHA-SCSU:STNO=<number1>,COS1=5; (per station)
CHA-SBCSU:STNO=<number2>,COS1=6; (centrally)
69.10 Examples
69.10.1 Internal Call Data Recording in the Network

You can configure charges for internal traffic not only within a node, but also in a
private network. The following example shows an entire network, which consists
of 2 sub-networks (shown inside the dashed lines) for charging purposes. Internal
charges are calculated inside these sub-networks. Networking charges for
outgoing calls are calculated between the sub-networks, because, for example,
the network connections (node 100 <-> node 400 and node 100 <-> node 300)
are leased from a network operator.
A31003-H3170-S103-6-7620, 02/2019
Examples
Node 100 Node 300

1 2 3
4 5 6
+ 7 8 9 1 2 3
- * 0 # 4 5 6
Q W E R T Z U I O P Ü + 7 8 9
A S D F G H J K L Ö Ä LÖS
A Y X C V B N M - * 0 #
KAR ED IT ALT MEN END WA
Q W E R T Z U I O P Ü
A Y X C V B N M
31000
51000
1 2 3
4 5 6
+ 7 8 9
- * 0 #
1 2 3 A S D F G H J K L Ö Ä LÖS
A Y X C V B N M
4 5 6
+ 7 8 9
Node 200
- * 0 #
41001
A Y X C V B N M
31001
Node 400 1 2 3
4 5 6
+ 7 8 9
- * 0 #
A Y X C V B N M
41002
CO
Dummy node 999
Figure 100 Charges for internal traffic and outgoing networking
Scenario 1: Station 41001 calls station 41002. 41001 is in an ITR group that is
assigned the charge group INT01 (for example, EUR 0.30/MIN during the day,
EUR 0.20 at night). 41001 sees the in-progress charges updated periodically on
its display. After hanging up, the total charges for the call are displayed after a set
time.
Scenario 2: Station 41002 calls station 51000. The outgoing trunk group is
determined with LCR. Zone INT01 is again assigned to the LCR routing element.
The INTCHARG identification is also set so that external charges are treated as
internal ones. From the station’s perspective, scenario 2 is the same as scenario
1.
Scenario 3: Station 41001 calls 31000. Because 31000 is not in the same sub-
network and is reached via chargeable tie trunks, a networking zone (such as
TIE01) is assigned to the corresponding LCR routing element. The charges differ
from those in scenarios 1 and 2.
Scenario 4: Station 31000 dials a CO number. If, for example, the tie trunk group
nodes 100 - 200 and the first overflow trunk group nodes 100 - 400 are seized, a
route node 100-300-400 is seized. No networking charges should be calculated
in transit node 300 and source node 100. In this case, the corresponding route
element in source node 100 is given the attribute NOTRANS and the message so
A31003-H3170-S103-6-7620, 02/2019
Examples
that no call data recording is activated in transit node 300. Call data recording is
always active in trunk breakout node 400. In the example, trunk access is only
allowed for the LCR service VCE (voice + fax).
IMPORTANT: All commands that are shown in boldface are specifically for call
data recording.
Configuration commands in node 100:

• Add a separate node number with:
CHA-ZAND:TYPE=ALLDATA,PNNO=100;
• If necessary, increase the buffer for cost calculation with:
ADD-DIMSU:TYPE=BASIC,COSTI=1000;
• Define amounts instead of units on the device with:
• Configure the charge display timer with:
• Add the station numbers for closed numbering in the DPLN as follows:
ADD-WABE:CD=0,DPLN=0,DAR=CO;
ADD-WABE:CD=31000,DAR=STN;
ADD-WABE:CD=41001&41002,DAR=NETW,DESTNO=4;
ADD-WABE:CD=31001,DAR=NETW,DESTNO=2;
ADD-WABE:CD=001&002&003, DAR=NETRTE;
• Assign the zone for ITR 0 internal traffic as follows:
• Create the COS with the charge authorizations as follows:
CHA-
COSSU:TYPE=COS,COS=2,AVCE=CDRINT&CDRSTN&CDRS,AFAX=CDRINT&CDRS
TN
• Add the LCR routes as follows:
CHA-COSSU:TYPE=LCOSV,LCOSV=15,ALAUTH=1&2; (for example, LCOS
authorization PBX-NETWORK + CO)
CHANGE-COSSU:TYPE=LCOSD,LCOSD=5,ALAUTH=1; (for example, data
only in PBX network)
ADD-BUEND:TGRP=20,NAME=K100TO200,NO=30;
ADD-
TDCSU:OPT=NEW,COTNO=11,LCOSV=1,LCOSD=1,DEV=S2CONN,PROTVAR=ECM
A1
,TGRP=20,BCGR=2;
ADD-
A31003-H3170-S103-6-7620, 02/2019
Examples
A1
,TGRP=30,BCGR=2;
ADD-
A1
,TGRP=40,BCGR=2;
ADD-
RICHT:MODE=CD,CD=001,LRTE=55,CPS=0,SVC=ALL,TGRP1=20,DESTNO=2
,DNNO=200;
ADD-
RICHT:MODE=CD,CD=002,LRTE=66,CPS=0,SVC=ALL,TGRP1=30&40,DESTNO
=3
,DNNO=300;
ADD-
=4
,DNNO=400;
ADD-
RICHT:MODE=LRTENEW,LRTE=88,LSVC=VCE,TGRP=20&30&40,DNNO=999;
ADD-KNDEF:NNO=<level2>-<level1>-<level0>,ISDNCC=49,ISDNAC=89
,ISDNLC=722;
• Configure the outdial rule for the CO (open numbering) as follows:
ADD-LODR:ODR=1,CMD=ECHO,FIELD=1; (send the dialed 0)
ADD-LODR:ODR=1,CMD=ECHO,FIELD=2; (send the rest of the station number)
• Assign the outdial rule for networking (closed numbering) as follows:
ADD-LODR:ODR=2,CMD=ECHO,FIELD=1; (send the entire station number)
• Define the LCR elements with trunk group seizure order as follows:
ADD-LDAT:LROUTE=55,LSVC=ALL,LVAL=1,TGRP=20,LAUTH=1,ODR=2;
ADD-LDAT:LROUTE=88,LSVC=VCE,LVAL=1,TGRP=20,LAUTH=2,ODR=1;
ADD-LDAT:LROUTE=88,LSVC=VCE,LVAL=3,TGRP=30,LAUTH=2,ODR=1;
• Add the dialing plan for the CO:
ADD-LDPLN:LDP=0-Z,LROUTE=88,LAUTH=2;
• Give the LCR elements charge attributes as follows:
CHA-LDAT:LROUTE=55,LSVC=ALL,LRTEL=1,CARRIER=1,ZONE=INTERN01
,LATTR=WCHREG&INTCHARG;
CHA-LDAT:LROUTE=66&77,LSVC=ALL,LRTEL=1&2,CARRIER=1
,ZONE=TIE01,LATTR=WCHREG;
CHA-LDAT:LROUTE=88,LSVC=VCE,LRTEL=1&2&3,LATTR=WCHREG&NOTRANS;
• Parameterize the stations as follows:
CHA-
SBCSU:STNO=31000,COS1=2,COS2=2,LCOSV1=15,LCOSV2=15,LCOSD1=5
,LCOSD2=5,ITR=0;
• Activate the features (charges for the trunk, tie, and internal) centrally as
follows:
A31003-H3170-S103-6-7620, 02/2019
Examples
CHANGE-FEASU:TYPE=A,
CM=CDROGTR&DISCHTR&CDROGNW&DISCHNW&CDRINH&DISCHINH;

• Add a separate node number as follows:
• If necessary, increase the buffer for cost calculation with:
• Amounts instead of units at the device with:
• Configure the charge display timer as follows:
• Add the station numbers in WABE as follows:
ADD-WABE:CD=41001&41002,DAR=STN;
ADD-WABE:CD=001&002&003, DAR=NETRTE;
• Assign the zone for internal traffic in ITR 0 as follows:
CHA-
COSSU:TYPE=COS,COS=2,AVCE=CDRINT&CDRSTN&CDRS,AFAX=CDRINT&CDRS
TN
• Configure the COT with DPRE (for trunk circuits) as follows:
CHA-COT:COTNO=12,COTTYPE=COTADD,PAR=DPRE&LWNC&NLCR;
• Add the LCR routes as follows:
CHA-COSSU:TYPE=LCOSV,LCOSV=15,ALAUTH=1&2; (for example, LCOS
authorization PBX-Network + CO)
CHANGE-COSSU:TYPE=LCOSD,LCOSD=5,ALAUTH=1; (for example, data
only in PBX network)
ADD-BUEND:TGRP=44,NAME=K400TOAMT,NO=30;
ADD-
A1
,TGRP=11,BCGR=2;
ADD-
A1
,TGRP=31,BCGR=2;
ADD-
TDCSU:OPT=NEW,COTNO=12,LCOSV=1,LCOSD=1,GER=S2COD,PROTVAR=ETSI
,TGRP=44,BCGR=2,NNO=999,ISDNIP=00,ISDNNP=0;
A31003-H3170-S103-6-7620, 02/2019
Examples
ADD-
=1
,DNNO=100;
ADD-
=2
,DNNO=200;
ADD-
=3
,DNNO=300;
ADD-
RICHT:MODE=LRTENEW,LRTE=88,LSVC=VCE,TGRP=11&31&44,DNNO=999;
ADD-KNDEF:NNO=<level2>-<level1>-<level0>,ISDNCC=49,ISDNAC=89
,ISDNLC=722;
• Configure the outdial rule for the CO (via a tie trunk) as follows:
ADD-LODR:ODR=1,CMD=ECHO,FIELD=1; (send the dialed 0)
ADD-LODR:ODR=1,CMD=ECHO,FIELD=2; (send the rest of the station number)
• Configure the outdial rule for the CO (direct connection) as follows:
ADD-LODR:ODR=3,CMD=ECHO,FIELD=2; (send the station number without "0")
• Define the LCR elements with trunk group seizure order as follows:
ADD-LDAT:LROUTE=88,LSVC=VCE,LVAL=3,TGRP=31,LAUTH=2,ODR=1;
• Add the dialing plan for the CO:
• Give the LCR elements charge attributes as follows:
CHA-LDAT:LROUTE=77,LSVC=ALL,LRTEL=1,CARRIER=1,ZONE=INTERN01
,LATTR=WCHREG&INTCHARG;
CHA-LDAT:LROUTE=77,LSVC=ALL,LRTEL=2,CARRIER=1,ZONE=TIE02
,LATTR=WCHREG&NOTRANS; (transit node 100 without
charge)
CHA-LDAT:LROUTE=55&66,LSVC=ALL,LRTEL=1&2,CARRIER=1
,ZONE=TIE01,LATTR=WCHREG;
CHA-LDAT:LROUTE=88,LSVC=VCE,LRTEL=1,LATTR=WCHREG;
CHA-LDAT:LROUTE=88,LSVC=VCE,LRTEL=2&3,LATTR=WCHREGT&NOTRANS;
A31003-H3170-S103-6-7620, 02/2019
Examples
CHA-
SBCSU:STNO=41001&&41002,COS1=2,COS2=2,LCOSV1=15,LCOSV2=15,
LCOSD1=5,LCOSD2=5,ITR=0;
• Proceed as follows to activate the feature centrally:
CHA-FEASU: TYPE=A
,CM=CDROGTR&DISCHTR&CDROGNW&DISCHNW&CDRINT&DISCHINH;
Configuration commands in nodes 200 and 300:

Configure node 200 (with trunk connection) in the same way as node 100, in
principle, like nodes 400 and 300.
69.10.2 Tie Traffic with Incoming Charges and Trunk

Traffic in Transit
+
1
4
*
2
5
8
3
6
9 +
1
4
*
2
5
8
3
6
9
Incoming
networking
- 0 # - 0 #
Q W E R T Z U I O P Ü Q W E R T Z U I O P Ü
A S D F G H J K L Ö Ä LÖS A S D F G H J K L Ö Ä LÖS
A Y X C V B N M A Y X C V B N M
KAR EDIT ALT MEN END WA KAR EDIT ALT MEN END WA
31000 31001 charges
Sub-network,
reachable via TIE
Outgoing
networking
charges CO
Dummy node 999
Node 100 Node 200
Call data recording

active
Figure 101 Tie Traffic with Incoming Charges and Trunk Traffic in Transit
Incoming charges should be recorded between the sub-network that is connected

via tie trunks and node 200. In addition, call data recording for outgoing trunk
traffic is activated in node 200.
Scenario 1: A station from the sub-network calls 31001. In node 200, call data
recording is activated for incoming tie trunks and a zone is assigned to the
incoming trunk so that charges are calculated by time; these charges should be
displayed at the chargeable station 31001.
Scenario 2: Charges should be recorded for outgoing network connections from

node 200 to node 100. A subscriber calls 722-31000. In node 200, a dummy
station number is assigned to the trunk for call data recording; this is used as the
"paying party" for the chargeable link 200-100.
A31003-H3170-S103-6-7620, 02/2019
Examples

• Assign a separate node identifier and separate node number as follows:
• Amounts instead of units on the device with:
• If necessary, increase the buffer for calculation for costs with:
• Configure the charge display timer as follows:
• Add the station numbers in WABE as follows:
ADD-WABE:CD=31001,DAR=STN;
ADD-WABE:CD=001,DAR=NETRTE;
• Add the LCR authorizations as follows:
CHA-COSSU:TYPE=LCOSV,LCOSV=9,ALAUTH=1;
CHA-COSSU:TYPE=LCOSD, LCOSD=5,ALAUTH=1;
• Add the outgoing trunk groups TIE and CO as follows:
ADD-BUEND:TGRP=20,NAME=K200TONET,NO=30;
ADD-BUEND:TGRP=40,NAME=K200TOAMT,NO=30;
• Configure COT for incoming call data recording via ZONE as follows:
CHA-COT:COTNO=15,COTTYPE=COTADD,PAR=ICZO;
• Configure COT for incoming call data recording via ZONE as follows:
CHA-COT:COTNO=12,COTTYPE=COTADD,PAR=DPRE&LWNC&NLCR;
• Assign the charge parameters to the incoming circuit as follows:
ADD-TDCSU:OPT=NEW,COTNO=15,LCOSV=1,LCOSD=1,DEV=S2CONN
,PROTVAR=ECMA1,TGRP=20,BCGR=2,CARRIER=2,ZONE=INC01;
• Add the trunk to node 100 as follows:
ADD-
A1
,TGRP=30,BCGR=2;
• Add the trunk to the CO as follows:
A31003-H3170-S103-6-7620, 02/2019
Examples
ADD-
TDCSU:OPT=NEW,COTNO=12,LCOSV=1,LCOSD=1,GER=S2COD,PROTVAR=ETSI
,TGRP=40,BCGR=2,NNO=999,ISDNIP=00,ISDNNP=0,PEN=1113-0;
• Assign a "dummy" station number to the trunk circuit as follows:
ADD-
TLZO:TBL=MTLC,LTG=1,LTU=1,SLOT=113,CCR=0,BCHAN=0&&30,STNO=555
55;
• Configure the LCR routes for closed numbering as follows:
ADD-
RICHT:MODE=CD,CD=001,LRTE=55,CPS=0,SVC=ALL,TGRP1=30,DESTNO=3
,DNNO=100;
ADD-RICHT:MODE=LRTENEW,LRTG=88,LSVC=ALL,TGRP=40,DNNO=999;
• Configure the outdial rule for direct trunk connection as follows:
ADD-LODR:ODR=1,CMD=ECHO,FIELD=2; (send the station number without "0")
• Define the LCR element with trunk group seizure order as follows:
ADD-LDAT:LROUTE=88,LSVC=ALL,LVAL=1,TGRP=40,LAUTH=1,ODR=1;
• Configure the dialing plan for the CO as follows:
• Give the LCR element charge attributes (outgoing to node 100) as follows:
CHA-LDAT:LROUTE=55,LSVC=ALL,LRTEL=1,CARRIER=2,ZONE=TIE02
,LATTR=WCHREG;
• Configure the LCR element for the CO with outgoing call data recording as
follows:
CHA-LDAT:LROUTE=88,LSVC=ALL,LRTEL=1,LATTR=WCHREG;
CHA-SBCSU:STNO=31001,COS1=2,COS2=2,LCOSV1=9,LCOSV2=9,LCOSD1=9
,LCOSD2=9;
• Activate the feature centrally as follows (TIE incoming, TIE outgoing, CO
outgoing):
CHA-FEASU:TYPE=A,CM=CDROGTR&DISCHTR&CDROGNW&DISCHNW&CDRIC;
A31003-H3170-S103-6-7620, 02/2019
Examples
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_gebana_en.fm
Feature description
70 Charge Pulse Metering & Sending to Analog Stations

12 or 16 kHz metering pulses are sent to analog stations with the classes of
service "GET" and "Call charge metering pulse sending" or to coin boxes (new
COS). The frequency of the metering pulses (depending on the time of day, type
of day, zone, etc.) is either calculated by the OpenScape 4000 system (charge
pulse metering) or received by a higher-ranking CO.
The OpenScape 4000 system supports the charge pulse types 16 kHz, 12 kHz,
and line reversal.
A new SLMA board (SLMAR) was developed for sending the 12 kHz and 16 kHz
pulses. The charge pulse types (16 KHz, 12 KHz, etc.) can be configured per port.
A special charge pulse is configured in the OpenScape 4000.
The pulse sending procedures listed below can be configured (see AMO GEFE /
TTBL):
Fixed metering pulse One or more metering pulses are sent immediately as
sending at connection basic charges. Pulses are not sent periodically (interval
setup set to 0).
Periodical metering pulse One or more metering pulses are sent immediately. The
pulses are then sent periodically according to the set
intervals.
Periodical "Karlsson" (K) The first metering pulse is sent after a random period of
metering pulse time which lies within the configured interval range. The
intervals. (Method 0)
Periodical "Karlsson The first metering pulse is sent immediately. The next
added" (KA) metering metering pulse is sent after a random period of time which
pulse lies within the configured interval range. The pulses are
then sent periodically according to the set intervals.
(Method 1)
Periodical "Karlsson The first metering pulse is sent immediately. The next
modified" (KM) metering metering pulse is sent after a random period of time which
pulse lies within a range of 2 times the configured interval. The
intervals. (Method 2)
70.1.1 Operating limitations

Only the following stations are allowed to use this feature:
• Analog stations with metering or
A31003-H3170-S103-6-7620, 02/2019
Service Information
• ELASA coin boxes with the appropriate configuration (OpenScape 4000-

specific EPROM specified for the country intended for use)
Simultaneous use of the features "Charge Pulse Metering" and "Extended

Subscriber Loop" is not possible.
70.1.2 Areas of application

This feature is intended for "rural" markets (e.g. South America).
70.1.3 Activating the feature

This is not a default feature. Metering pulse sending is activated using the FEASU
AMO’s feature bit.
The start of CDR for internal connections at end-of-dialing can be configured

using the AMO ZAND. In this case both pulse sending and CDR for all internal
connections starts from the ringing state.
CDR from end-of-dialing (for internal calls) is independent from the configuration
of metering pulse sending.
70.2.1 Charges for analog stations

The features "extended loop" and "Send metering pulse" are mutually exclusive.
The level is set with the AMO SCSU and is dependent on the station and line
length.
The maximum line length is currently 300 m (approx.).
Metering pulses from the CO are converted on a one-to-one basis by the SLMAR.
Call charge information generated by the remote system is split by the CCUC
parameter in the AMO ZAND and then forwarded as pulses by the SLMAR.
Separate clock tables must be configured with the AMO TTBL for internal and
network-wide CDR by carrier and zone. Only the clock tables of the TTBL group
are used for timer pulse generation. Clock tables in other groups are not analyzed
by the software.
A31003-H3170-S103-6-7620, 02/2019
Generation Notes
70.2.2 Increasing the line length

Stations with a loop resistor of up to 3000 ohms (including station) can be
connected to the SLMAR.
Up to two analog stations are permitted per port.
An extended station (extended loop) in talk state requires roughly the same
amount of power as two normal analog stations.
The ringing ac current for the station is generated on the board. The ring current
from the ring generator is not used.
The limit for the extended stations is the power supply of the system.
During configuration of the station the board checks if the increased power supply
is necessary. If it is not required, a message indicating that a standard SLMA
should be used is output.
When equipping the system, the configurator must ensure that there are no hot
spots.
70.3 Generation Notes
70.3.1 AMOs for charges on analog stations
AMO Parameter Sprache Beschreibung/ Discription

FEASU LM=GIS d Gebührenimpulsaussendung und -messung
(Baugruppe SLMAR)
CM=CPS e Charge pulse sending and metering (SLMAR)
SCSU GERKON= d Analoges Sprachendgerät mit Gebührenzähler
ANATEGEB
DVCFIG= e Analog voice terminal with charge metering
ANATECM
PULSTYP d Typ der Gebührenimpulse (nur Baugruppe
SLMAR)
PULSTYPE e Type of charge metering pulses (only for SLMAR
board)
PULSPGL d Pegel der Gebührenimpulse (nur Baugruppe
SLMAR)
PULSLEV e Level of charge metering pulses (only for SLMAR
board)
TTBL TAB=TKT d Tabelle mit Taktinformation
TBL=CLK e Table with clock information
A31003-H3170-S103-6-7620, 02/2019
Generation Notes
70.3.2 FEASU - Enabling metering pulse sending

CHA-FEASU:TYPE=A,CM=CPS;
70.3.3 BCSU - Configuring an SLMAR board

ADD-BCSU:TYPE=PER,LTG=1,LTU=2,SLOT=67,PARTNO=Q2480-X;
70.3.4 XAPX - Managing classes of service

ADD-
COSSU:NEWCOS=24,AVCE=TA&PUPHON&TNOTCR&CDRATN&CDRINT&CDRS&CDRC;
• PUPHON ... Public telephone
Different clock intervals can be sent for each station type according to the
assigned class of service. If a station does not have a special class of service, it
is treated as a “normal station“.
70.3.5 SCSU - Configuring an SLMAR station

ADD-SCSU:STNO=2250,PEN=1-2-67-
0,DVCFIG=ANATECM,DPLN=0,ITR=0,COS1=24,COS2=24,LCOSV1=7,LCOSV2=6,
LCOSD1=5,LCOSD2=4,CIRCDIX=1,DIAL=VAR,PULSTYPE=KHZ12,PULSLEV=VEFF
5;
• DVCFIG ... Device configuration
– ANATECM ... Analog station with metering
– ANATE ... Analog telephone
• CIRCIDX ... Index for timer block table
• PULSTYPE ... Type of metering pulse
– FORM ... Change pulse form
– KHZ12 ... 12 kHz pulses
– KHZ16 ... 16 kHz pulses
– POL ... Polarity reversal
– POL12 ... Polarity reversal + 12 KHz
– POL16 ... Polarity reversal + 16 KHz
• PULSLEV ... Level of metering pulses
– VEFF5 ... 5 volts effective voltage
A31003-H3170-S103-6-7620, 02/2019
Generation Notes
Given that each station has a different line length and a different frequency
separating filter, the setting for the pulse level and the pulse silent period in
PTIME must be chosen carefully.
When setting the metering level and the pulse length and duration, it is
recommended that you have a measuring device for measuring the metering
pulses as well as a data sheet for the frequency separating filter.
70.3.6 TTBL- Configuring the tariff table for pulse

sending
ADD-
TTBL:TBL=CLK,TARTBLNO=1,ZONE=DIST01,FIXDAY=1,FPLSDAY=100,PPLSDAY
=100,FIXN1=1,FPLSN1=100,PPLSN1=100,FIXN2=1,FPLSN2=100,PPLSN2=100
,FIXN3=1,FPLSN3=100,PPLSN43=100,PPLSN3=100,FIXN4=1,FPLSN3=100,PP
LSN4=100,SEGTBLNO=1,CHPER=Y;
The clock branch is only required if the value MIX or TIME is set in the AMO
GEFE. If PULSE is set in GEFE, the pulse is normally sent from the CO to the
SLMAR, which in turn generates the 16 KHz pulse for the station and sends it to
the station.
• TBL ... New tariff table branch
– CLK ... Table with clock information
• TARTBLNO ... Tariff table number
• ZONE ... Zone for connections without CDR information (parameter

Zone)
The table contains three parameters (FIX..., FPLS..., PPLS...), for each rate
period. These parameters define the metering pulse sending (e.g 1,100,100).
These parameters are interpreted as follows:
• FIX ... Number of pulses to be sent as basic charges
• FPLS ... Time until the first pulse after the basic pulses are sent in
milliseconds
This parameter can also contain one of the following values:
K ...... for Karlsson metering pulse sending
KA ... for Karlsson added metering pulse sending
KM ... for Karlsson modified metering pulse sending
• PPLS ... Silent period for periodical metering pulse sending in

milliseconds
If the selected metering pulse interval is too short ( < 1 sec.), this can
cause problems in some stations with regard to analysis of the 16 KHz
signal.
A31003-H3170-S103-6-7620, 02/2019
Generation Notes
• SEGTBLNO... Number of rate period table
• CHPER... Identifier for rate period change for connections without CDR
information
– Y... The costs are calculated according to the current rate period
70.3.7 TTBL - Managing the tariff group table

ADD-
TTBL:TBL=GRP,GROUPNO=0,CARRIER=0,CATPTY=PUPHON,SERVICE=ALL,TARTB
LNO=1;
70.3.8 VBZGR - Managing the internal traffic

restriction group zone matrix
VBZGR is only required for internal and incoming CDR.
• CHRGINT... Matrix for internal connections
• CHRGINC... Matrix for incoming connections
• ITRGRB... Internal traffic restriction group
70.3.9 GEFE - Managing the CDR parameter

The METHOD branch is only used for the Rural feature.
There are three methods for this accounting of call charges procedure:
• Method 0 ... No modification of the CDR information from the CO
• Method 1 ... First received pulse is suppressed
• Method 2 ... Second received pulse is suppressed
In the CAR branch the type of call detail recording is set per carrier. The following
values are permitted:
• TIME ... The CO (carrier) does not transmit any CDR information;
metering pulses are determined independently in the OpenScape 4000.
• PULSE ... The pulses received from the CO (carrier) are emitted by the
OpenScape 4000 via the SLMAR board.
• MIX ... Pulses are calculated and emitted independently by the

OpenScape 4000 at connection setup; if, however, pulses are received
from the CO, these are sent via the SLMAR board.
A31003-H3170-S103-6-7620, 02/2019
Forwarding charges from the CO
70.3.10 ZAND - Managing central system data

CHA-ZAND:TYPE=CCD,CDRRINGB=YES;
• CDRRINGB ... Flag for active CDR with end-of-dialing
This option was developed with the Charge Pulse Metering and Sending feature,
but is not a requirement for activation of metering pulse sending.
By activating internal CDR after end-of-dialing, recording for internal connections

(and therefore also the start of metering pulse sending) is set to start at end-of-
dialing (ringing state).
70.3.11 PTIME - Managing timers for peripherals

Changing the pulse duration or minimum pause duration between the metering
pulses
CHA-PTIME:TYPE=SLMA1,TBLK=0,PULSED=<number>,PAUSED=<number>;
• TBLK ... Timer block
• PULSED ... Pulse duration
• PAUSED ... Pause duration
The values for PULSED and PAUSED must be entered in 10 msec increments
(i.e. for 80 msec the value is 8)
The timer block (TBLK) configured with the AMO PTIME must be assigned with
the AMO SCSU in the CIRCIDX parameter (index for the timer block table for
SLMAR):
CHA-SCSU:STNO=<number>,CIRCIDX=0;
If the original behavior for a station is to be restored, the value 16 must be
specified for the CIRCIDX parameter when changing SCSU.
A change in the pulse or pause duration does not take effect until the SLMAR
board is loaded.
70.4 Forwarding charges from the CO
70.4.1 Configuring the board

ADD-BCSU:MTYPE=PER,LTG=1,LTU=2,SLOT=31,PARTNO=Q2480-X;
• Configure the station on an SLMAR (the level depends on the line length and
telephone type used)
A31003-H3170-S103-6-7620, 02/2019
Forwarding charges from the CO
• The station must be assigned a suitable PTIME table with CIRCIDX if

required.
CHA-PTIME:TYPE=SLMA1,TBLK=0,PULSED=80, PAUSED=80;
H500: AMO PTIME STARTED
H01: WARNING! THE MODIFIED TIME PARAMETERS WERE NOT 
LOADED IN THE TRUNK MODULES. 
PLEASE REMOVE AND INSERT AFFECTED BOARDS.
ADD-
SCSU:STNO=7104,DVCFIG=ANATECM,DPLN=0,ITR=0,COS1=4,COS2=4,LCOS
V1=4,LCOSV2=4,LCOSD1=4,LCOSD2=4,CIRCIDX=1,DIAL=VAR,INS=YES,PU
LSTYPE=KHZ16,PULSLEV=VEFF3;
70.4.2 Feature enabled

The feature must be enabled in FEASU.
CHA-FEASU:TYPE=A,CM=CPS;
ACT-BSSU:ONTYPE=AUL,LTG=1,LTU=2,SLOT=31;
70.4.3 Output loadware version of SLMAR

The loadware version of the SLMAR can be output with STA-LIST.
STA-LIST:FILENAM=":PDS:APSP/LTG/LG80/PZESLAR0",FORMAT=B;
70.4.4 Activating call detail recording

Activating call detail recording for the carrier used:
CHA-GEFE:TYPPARAM=CAR,CARRIER=1,TYPE=MIX,CHRGPLS=N;
70.4.5 PUPHON tariff table

Assigning tariff table for PUPHON:
ADD-
LNO=1;
70.4.6 Station entries

All stations entered in your COS PUPHON are thus referred to
TARTBLNO=1.
A31003-H3170-S103-6-7620, 02/2019
Configuring internal call detail recording
70.5 Configuring internal call detail recording
70.5.1 Configuring internal zones for call detail

recording
ADD-VBZGR:GROUP=0&&15,TYPE=CHRGINT,ITRGRB=0&&15,ZONE=INT01;
70.5.2 Assigning type public telephone

ADD-COS:COPYCOS=3,NEWCOS=25,AVCE=PUPHON;
70.5.3 Enabling internal call detail recording

CHA-FEASU:TYPE=A,CM=CHRGINT;
70.5.4 Tariff table for metering pulse sending

Configuring the tariff table for metering pulse sending
ADD-
TTBL:TBL=CLK,TARTBLNO=1,ZONE=INT01,FIXDAY=2,FPLSDAY=100,PPLSDAY=
100,FIXN1=2,FPLSN1=100,PPLSN1=200,FIXN2=2,FPLSN2=100,PPLSN2=200,
FIXN3=2,FPLSN3=100,PPLSN3=300,FIXN4=2,FPLSN4=100,PPLSN4=500,SEGT
BLNO=1,CHPER=Y;
70.5.5 Tariff tables for public telephone

Configuring tariff tables for public telephone:
ADD-
LNO=1;
A31003-H3170-S103-6-7620, 02/2019
Configuring internal call detail recording
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_gesta_en.fm
Default Values
Country-Specific Parameters
71 Default Values
The customer can change these values, but they are preset to a particular value.
71.1 Country-Specific Parameters

• Change the parameter values
DN branch Destination number shortened:
CHA-GEFE:TYPPARAM=DN,DNSHORT=<param>;
ATTNDINC branch Incoming attendant/secretary must pay own costs:
CHA-GEFE:TYPPARAM=ATTNDINC,ATTNDINC=<param>;
ATTNDOUT branch Outgoing attendant/secretary must pay own costs:
CHA-GEFE:TYPPARAM=ATTNDOUT,ATTNDOUT=<param>;
INCOLD branch Incoming caller in the field of the called:
CHA-GEFE:TYPPARAM=INCOLD,INCOLD=<param>;
CONFAOCS branch Configuration of the call charging over AOC_S message
(call charge information at connection setup):
CHA-
GEFE:TYPPARAM=CONFAOCS,CONFAOCS=THRCONN,THRCONN=<param>;
and
CHA-
GEFE:TYPPARAM=CONFAOCS,CONFAOCS=NTHRCONN,NTHRCONN=<param>;
KNMATINT branch Node ID for internal traffic:
CHA-GEFE:TYPPARAM=KNMATINT,PARTY=<param>;
KNMATINC branch Node ID for incoming traffic:
CHA-GEFE:TYPPARAM=KNMATINC,PARTY=<param>;
KNMATOUT branch Node ID for outgoing traffic:
CHA-GEFE:TYPPARAM=KNMATOUT,PARTY=<param>;
PREINT branch Prefix handling for internal traffic:
CHA-GEFE:TYPPARAM=PREINT,PARTY=<param>;
PREINC branch Prefix handling for incoming traffic:
CHA-GEFE:TYPPARAM=PREINC,PARTY=<param>;
PREOUT branch Prefix handling for outgoing traffic:
CHA-GEFE:TYPPARAM=PREOUT,PARTY=<param>;
CAR branch Carrier:
CHA-GEFE:TYPPARAM=CAR,CARRIER=<number>,{(min1)TYPE=<param>
,CHRGPLS=<param>};
A31003-H3170-S103-6-7620, 02/2019
Default Values
Connection Limits Table
METHOD branch Method (Rural):

CHA-
GEFE:TYPPARAM=METHOD,CARRIER=<number>,{(min1)MNORM=<param>
,MSCRSPC=<param>,MPUPHON=<param>,MMTEQ=<param>};
REALUNIT branch Units from CO are saved in CDB:
CHA-GEFE:TYPPARAM=REALUNIT,REALUNIT=<param>;
SAMEPP branch Section by same paying party:
CHA-GEFE:TYPPARAM=SAMEPP,TICKET=<param>;
CCALLDIR branch Allow change of call direction in ticket sequence:
CHA-GEFE:TYPPARAM=CCALLDIR,CCALLDIR=<param>;
RNGDT branch New ringing, through connected call in RING_DUR:
CHA-GEFE:TYPPARAM=RNGDT,RNGDT=<param>;
QUEUEDUR branch Output of QUEUE_DUR without CDRE feature switched
on:
CHA-GEFE:TYPPARAM=QUEUEDUR,QUEUEDUR=<param>;
• Display the parameter values
DIS-GEFE;
71.2 Connection Limits Table

• Change a connection limit or a connection time limit or an amount limit or a
fixed time of day
RCD branch Routing code:
CHA-
GRZW:TBL=RCD,[CDRCODE=<number>],[LTTYPE=CHRG],[CDRULT=<num
ber>];
CHA-
GRZW:TBL=RCD,[CDRCODE=<number>],[LTTYPE=AMOUNT],[AMOUNTLT=
<number>];
CHA-
GRZW:TBL=RCD,[CDRCODE=<number>],[LTTYPE=TIME],[CALLT=<numb
er>];
CAR branch Carrier:
CHA-
GRZW:TBL=CAR,CARRIER=<number>,[LTTYPE=CHRG],[CDRULT=<numbe
r>]; 
CHA-
GRZW:TBL=CAR,CARRIER=<number>,[LTTYPE=AMOUNT],[AMOUNTLT=<n
umber>]; 
CHA-
GRZW:TBL=CAR,CARRIER=<number>,[LTTYPE=TIME],[CALLT=<number
>];
HOUR branch Hour limit:
A31003-H3170-S103-6-7620, 02/2019
Default Values
Output Text Tables
CHA-GRZW:TBL=HOUR,[HOURLIM=<number>];
• Display the limits in list format:
DIS-GRZW:[TBL=<param>];
71.3 Output Text Tables

• Add the output tables:
ADD-TEXT:TBL=OUTDAYC,ENTRY=<number>,NAME=<string>; 
ADD-TEXT:TBL=OUTMONC,ENTRY=<number>,NAME=<string>; 
ADD-TEXT:TBL=SERVICE,ENTRY=<param>,NAME=<string>; 
ADD-TEXT:TBL=SPEED,ENTRY=<number>,NAME=<string>; 
ADD-TEXT:TBL=NETTYPE,ENTRY=<param>,NAME=<string>; 
ADD-TEXT:TBL=SWP,ENTRY=<param>,NAME=<string>; 
ADD-TEXT:TBL=CHOFCON,ENTRY=<number>,NAME=<string>; 
ADD-TEXT:TBL=SUBSID,ENTRY=<number>,NAME=<string>; 
ADD-TEXT:TBL=SIGDATA,ENTRY=<number>,NAME=<string>; 
ADD-TEXT:TBL=ROUTCC,ENTRY=<number>,NAME=<string>; 
ADD-TEXT:TBL=IDPP,ENTRY=<param>,NAME=<string>; 
ADD-TEXT:TBL=UNITERAS,ENTRY=<param>,NAME=<string>; 
ADD-TEXT:TBL=LISTTYPE,ENTRY=<param>,NAME=<string>; 
ADD-TEXT:TBL=EXPENS,ENTRY=<param>,NAME=<string>; 
ADD-TEXT:TBL=CONNTYPE,ENTRY=<param>,NAME=<string>;
ADD-TEXT:TBL=SUPPLSERV,ENTRY=<param>,NAME=<string>;
ADD-TEXT:TBL=ZONE,ENTRY=<param>,NAME=<string>;
ADD-TEXT:TBL=CARRIER,ENTRY=<param>,NAME=<string>;
ADD-TEXT:TBL=COPIN,ENTRY=<param>,NAME=<string>;
ADD-TEXT:TBL=UNANS,ENTRY=<param>,NAME=<string>;
ADD-TEXT:TBL=RURAL,ENTRY=<param>,NAME=<string>; 
ADD-TEXT:TBL=AOCTYPE,ENTRY=<param>,NAME=<string>; 
ADD-TEXT:TBL=CALCTYPE,ENTRY=<param>,NAME=<string>; 
ADD-TEXT:TBL=INFOTYPE,ENTRY=<param>,NAME=<string>;
• Delete an entire table or table entries:
DEL-TEXT:TBL=OUTDAYC,[ENTRY=<number>];
DEL-TEXT:TBL=OUTMONC,[ENTRY=<number>]; 
DEL-TEXT:TBL=SERVICE,[ENTRY=<param>]; 
DEL-TEXT:TBL=SPEED,[ENTRY=<number>]; 
DEL-TEXT:TBL=NETTYPE,[ENTRY=<param>]; 
DEL-TEXT:TBL=SWP,[ENTRY=<param>]; 
DEL-TEXT:TBL=CHOFCON,[ENTRY=<number>]; 
DEL-TEXT:TBL=SUBSID,[ENTRY=<number>]; 
DEL-TEXT:TBL=SIGDATA,[ENTRY=<number>]; 
DEL-TEXT:TBL=ROUTCC,[ENTRY=<number>]; 
DEL-TEXT:TBL=IDPP,[ENTRY=<param>]; 
DEL-TEXT:TBL=UNITERAS,[ENTRY=<param>]; 
DEL-TEXT:TBL=LISTTYPE,[ENTRY=<param>]; 
DEL-TEXT:TBL=EXPENS,[ENTRY=<param>]; 
DEL-TEXT:TBL=CONNTYPE,[ENTRY=<param>];
DEL-TEXT:TBL=SUPPLSERV,[ENTRY=<param>];
DEL-TEXT:TBL=ZONE,[ENTRY=<param>];
DEL-TEXT:TBL=CARRIER,[ENTRY=<param>];
DEL-TEXT:TBL=COPIN,[ENTRY=<param>];
DEL-TEXT:TBL=UNANS,[ENTRY=<param>];
DEL-TEXT:TBL=RURAL,[ENTRY=<param>]; 
A31003-H3170-S103-6-7620, 02/2019
Default Values
File Sizes
DEL-TEXT:TBL=AOCTYPE,[ENTRY=<param>]; 
DEL-TEXT:TBL=CALCTYPE,[ENTRY=<param>]; 
DEL-TEXT:TBL=INFOTYPE,[ENTRY=<param>];
• Display one table or all tables:
DIS-TEXT:[TBL=<param>];
71.4 File Sizes

• Add the file sizes for the CDRC files:
ADD-DAGR:FILE=CDRC1,NO=<number>;
ADD-DAGR:FILE=CDRC2,NO=<number>;
• Add the file parameters for the FT file:
ADD-DAGR:FILE=FT,NO=<number>,CODE=<string>,TIME=<number>
,PERIOD=<number>,NAME=<string>;
• Display the file sizes:
DIS-DAGR;
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_gd_dv_en.fm
DPS Interface Data
72 DPS Interface Data

The call data recording software complex offers the OpenScape 4000 system
operator a feature for retrieving call charge data or transmitting call charge data
to a DPS application using a partner computer (DPS) application.
The message traffic and output of the call charge data to the DPS are processed
via the Communication Management System (CMS).
• Connection process for retrieving data from the DPS: 

For this connection process, the DPS must send a job that specifies how
much data should be transmitted.
The DPS only sends the "Send call charge data" job at the beginning. Call
data recording then responds with "Call charge data block on request" and
waits for the answer "Call charge data processed" from the DPS. If this
acknowledgement is not sent within a specified time, the logical connection is
cleared down and the charge transmission is cancelled. If the DPS sends the
acknowledge message, the next block of data is transmitted with "Call charge
data processed" and a new call request. A "End of call charge data" message
is sent when there is no more call charge data available.
Requirement for processing the call charge data call:
• The AMO GEZAB’s "ADD" action must be used to define a dialog field for the
DPS retrieval of the CDRC1 or CDRC2 file.
Example for multiple output = NO:
ADD-
GEZAB:TYPE=L,DIAFNO=<number>,FILE=CDRC1|CDRC2,FILESTA=<string
>
,FILEND=<string>,DEV=DP,CALLUP=Y,DEL=<Y\N>,FORM=<string>
,FORM=<string>,BLKSIZE=<number>,FOUT=<Y\N>,MULTOUT=N
,PERIOD=<string>,SELSTOP=<Y\N>;
• For each dialog field that is assigned to the DPS call, a "short dialog" must be
defined for the AMO GEZAB. In the "short dialog", it must be possible to
change the two parameters FILESTA (start of file) and FILEND (end of file). 
If a scheduled job is activated for the dialog field that is assigned to the DPS
call, the dialog field can only be rewritten by stopping the active scheduled job
(STOP-GEZAB). This changes the status of the dialog field from
TIMEORDER ACTIVE to BUSY.
With the CHANGE-GEZAB action, the two parameters FILESTA and FILEND
can be rewritten in the "short dialog".
A plausibility check is run on the data sent by the DPS application (file name, file
start, file end), which means only the value CDRC1 or CDRC2 is allowed.
Call data recording for CDRC output on call must be configured:

ADD-FEACG:CM=CDRCDIS;
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_gd_dv_en.fm
DPS Interface Data
Furthermore, each of the eight dialog fields is searched to see if it contains

the following parameters.
DEV = DPS
FILE = CDRC1 or CDRC
ORDER_ID = CALL
If a dialog field contains the above parameters, the dialog field on the
database (DB) is blocked.
• Connection process for output from the OpenScape 4000: 

In the event of a file overflow (mandatory output) or output by scheduled jobs,
the call charge detail output is initiated by the OpenScape 4000 when the
output device is specified (DPS in this case). This is done by sending the
message "Call charge data blockon request". If the "Call charge data
processed" acknowledge is sent, the process is continued in the same way
as for DPS-based file retrieval.
If there is no acknowledgement from the DPS within a specific time, the call
charge detail output is cancelled.
In contrast to call charge detail retrieval via DPS, the initiative for call charge detail
output to the DPS lies with the OpenScape 4000.
All eight dialog fields are searched for the following parameters.
DEV = DPS
FILE = CDRC1 or CDRC
ORDER_ID = TO or FORCE
File processing starts if there is a dialog that contains these parameters. 

If no such dialog field is found (for example, if the job was cancelled with the AMO
GEZAB before the DPS connection was set up), a report is sent to the exception
handler and the system waits for the next job.
Meaning of the ORDER_ID variables:
• ORDER_ID = CALL
There is a call from the DPS.
• ORDER_ID = TO 
Output to the DPS.
• ORDER_ID = FORCE 
Mandatory output to the DPS (for example, in the event of file overflow)
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_geout_en.fm
INFO 2000 Outcalls
73 INFO 2000 Outcalls

• Set central parameters for call data recording
AD-FEACG:CM=<param>;
Possible Values: CDRATND Charge registration on attendant console

CDRCDUMP Central call charge registration immediate
CDRDIS Central call charge registration on call-up
CDRSPR Station CDR with output on printer
CDRFAST Fast CDR output
• Assign selection groups and tables for output on attendant console

AD-
SELG:TBL=SELT,SELGNO=<number>,RESOP=N,BASDEV=ATTEND,RESDEV=NO
DEV,BLBAS=1,BLRES=0;
AD-
SELG:TBL=SELT,SELGNO=<number>,SELTABNO=<number>,FORMBAS=ATTEN
D,FORMRES=NOFORM,TARIF=<string>,DESTCNT=<string>,CDRCD=<numbe
r>,
SERVICE=VOICE,ATNDGR=<number>,CTYPE=<string>,PAYPARTY=ALL,CDR
C=N,
CDRSTA=N,CHUAUTH=N,NSTAT=N,ABSCH=N,CDCHU=Y,CDRAC=STN,SFSETUP=
N,CDBAD=N,CDRULTE=N,CONNT=N,PCODE=Y,PPCF=N,TLNTAB=Y,STATAB2=N
,
DNOTBL1=N,DNOTBL2=N,CDRULT=0000,CONNTL=000000,CONNTL=000000,N
NO=0&&999,TIELINE=N;
The parameter TAR (tariff) defines the call charge unit output; possible values are
NOCALC, TARGR00...TARGR05.
• Assign tariff group

AD-TTBL:TBL=GRP,GRNO=<number>,CARRIER=<0-9>,SERVICE=<param>,
TARTBLNO=<1-9>;
• Assign tariff
AD-TTBL:TBL=WCU,TARTBLNO=<1-9>,TARMIN=<number>,METHOD=FACTOR,
FACTOR=100,LT1=0,TAR1=<number>;
<number> = call charge units in lowest-denomination currency unit
• Set comma (decimal point) and currency denomination for ATND display
CHA-DAVF:COMPOS=<number>,NAME=<number>
• Assign the route code
AD-RCUT:RTECD=<number>,CDRCODE=<number>;
NOTE: CDRCD parameter in SELG AMO is CDRCODE parameter in RCUT

AMO.
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_geout_en.fm
INFO 2000 Outcalls
If the SELG parameters STATAB1, STATAB2, DNOTBL1 and DNOTBL2 are

specified with "Y", the STN or destination concerned must be entered in the
appropriate table with the SELL AMO (please note that the "station table"
acronym in this AMO is "STNTBLx").
• Make entries in station or destination number lists

AD-SELL:TBL=STNTBL1/2,STNO=<number>;
or
AD-SELL:TBL=DNOTBL1/2,STNO=<string>;
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_gsecab_en.fm
74 Per-Second Invoicing with Prices in 1/100000 Currency

Units
Up until now, call charge unit prices have been specified in tariff tables with and
without charge information in 1/100th or 1/1000th currency units.
This means cents or tenths of cents, for example, in the European Union.
These values were used to calculate prices per time unit. However, as these
values did not support further subdivision, the full price had to be paid for each
time unit that was started.
The charging method has now been updated to bill on the basis of 1/100000th
currency units when calculating costs using tariff tables without charge
information for the displays, attendant console display, and cost elements in the
call detail record.
The output can now be rounded down to two and three places after the decimal
point in whole currency units (EU: EUR), for example, for city calls (assumed
price: 0.127 cent/s):
Call duration [seconds]: 1 25 60

2-digit display: 0.00 EUR 0.03 EUR 0.08 EUR
3-digit display: 0.001 EUR 0.032 EUR 0.076 EUR
The method for calculating costs on the basis of tariff tables with call charge units
has not been changed.
The method for calculating costs on the basis of tariff tables with charge
information in the form of costs has not been changed (the costs are received
from the carrier "ready calculated").
• Administration:
AMO-TTBL: In the GEN branch, a new parameter COMPOS is added for
each tariff table without charge information with the values: -3 to 3, 2T, 3T,
2HT, 3HT. If the decimal place is not 2T, 3T, 2HT, or 3HT, the cost is calculated
in 1/100th currency units. If the decimal place 
equals 2T or 3T, the cost is calculated in 1/1000th currency units, and if the
decimal point equals 2HT or 3HT, the cost is calculated in 1/100000th
currency units. Like the previous COMPOS parameter in the AMO DAVF, this
COMPOS parameter indicates the value of the price information in this tariff
table.
Attention: The settings in the AMO-DAVF now only apply when the
calculation uses the WCU tables. The settings in TTBL apply to a calculation
using WOCU.
• Example 1 (CITY CALL) = basic setting:
A31003-H3170-S103-6-7620, 02/2019
For carrier 0, zone INT01 is configured for per-second invoicing for the
VOICE service and user category NORM. 
Tariff table 1 should be used for the display and tariff table 2 for
CONN_CHARGE. In addition, time-of-day section table 1 should be used.
The output should be rounded down to two places after the decimal point on
the display, the attendant console, and in the data record.
• Assign tariff group 0 to carrier 0 and enter tariff table 1

ADD-
TTBL:TBL=GRP,GROUPNO=0,CARRIER=0,CATPTY=NORM,SVC=VOICE,TAR
TBLNO=1;
• Use tariff group 1 for calculating in the ADS and enter in tariff table 2
ADD-
TTBL:TBL=GRP,GROUPNO=1,CARRIER=0,CATPTY=NORM,SVC=VOICE,TAR
TBLNO=2;
• Set the decimal point for tariff tables 1 and 2 to hundred-thousandths of
the currency units and two-digit output
CHANGE-
TTBL:TBL=GEN,ELEMENT=COMPOS,TARTBLNO=1,COMPOS="2HT";
CHANGE-
TTBL:TBL=GEN,ELEMENT=COMPOS,TARTBLNO=2,COMPOS="2HT";
• Tariff tables 1 and 2
ADD-
TTBL:TBL=WOCU,TARTBLNO=1,ZONE=INT01,INTDAY=100,TARDAY=127,
INTNT1=100
,NTAR1=127,INTNT2=100,NTAR2=127,INTNT3=100,NTAR3=127,INTNT
4=100
,NTAR4=127,
TARBAS=+0,TARMIN=0,SEGTBLNO=1,CHPER,BCHLFACT=0;
ADD-
TTBL:TBL=WOCU,TARTBLNO=2,ZONE=INT01,INTDAY=100,TARDAY=127,
INTNT1=100
,NTAR1=127,INTNT2=100,NTAR2=127,INTNT3=100,NTAR3=127,INTNT
4=100
,NTAR4=127,
TARBAS=+0,TARMIN=0,SEGTBLNO=1,CHPER,BCHLFACT=0;
• Use the AMO GEFE to set the carrier to charging by time.
CHANGE-GEFE:TYPPARAM=CAR,CARRIER=0,TYPE=TIME,CHRGPLS=N;
• To calculate the units, you still need to configure a WCU table number 1
(in tariff group 0) with the price per unit of 0.94 EUR.
A31003-H3170-S103-6-7620, 02/2019
ADD-
TTBL:TBL=WCU,TARTBLNO=1,TARMIN=0,METHOD=FACTOR,FACTOR=1000
,LT1=0,TAR1=94;
NOTE: You should not configure WCU tariff table 2 with the UNITS method
as otherwise the units calculated in the SWU can be calculated back into
costs. This can result in considerable differences between DISPL_CHARGE
and CONN_CHARGE.
• Data records:
RECNO:0022 STARTED AT 01-03-04/17:07
PAYPART : 3351 DESTINATION: 3352
CALL_ID : 00000022 CONN_TYP : INT
CALLEV0 : 300 LEVEL0 : 300
CARRIER : CARRIER_0 ROUTE : 
DISC_CAUSE: 0 SUPL_SERV : NORMAL
PIN_TYP : 0 PIN_NO : 
CONN_DUR : 07:02.2 UNIT : 00001
CHARGE_ISP: 0.54 DISP_CHARG : 0.54
EXPENSIVE : B RING_DUR : 0000
ZONE : INTERN01 SWITCH_PR : ENDE N
START_TIME: 17:07:01.5 END_TIME : 17:14:03.7
ATTNR : REC_PT : 2
TRANSIT_CNT: 0
***RECORD-END***
RECNO:0025 STARTED AT 01-03-04/17:23

CONN_DUR : 11:27.2 UNIT : 00001
TRANSIT_CNT: 0
***RECORD-END***
• Example 2:
If you want the display to show outputs with three places after the decimal
point, enter the following command and perform the configuration outlined in
Example 1.
CHANGE-
A31003-H3170-S103-6-7620, 02/2019
The output is still shown with two places after the decimal point on the
attendant console and in the data record. The final sum appears as 0.124 on
the display and as 0.12 on the AC, and the following is output as a data
record:
RECNO:0026 STARTED AT 01-03-04/17:38
CALLEV0 : 300 LEVEL0 : 300 
CONN_DUR : 01:37.2 UNIT : 00001
TRANSIT_CNT: 0
***RECORD-END***
• Example 3:
If you want two places after the decimal point to be shown on the display, but
three on the attendant console, you only need the following command after
the basic configuration outlined in Example 1:
CHANGE-
The output would then be 0.42 on the display and 0.415 on the attendant
console; the data record would be:
RECNO:0027 STARTED AT 01-03-04/17:49
CONN_DUR : 05:26.9 UNIT : 00001
ATTNR :
REC_PT : 2
TRANSIT_CNT: 0
***RECORD-END***
• Example 4:
If the customer would like to set a basic charge of 0.50 EUR, then the
following commands must be entered after the basic configuration outlined in
Example 1.
A31003-H3170-S103-6-7620, 02/2019
CHANGE-TTBL:TBL=WOCU,TARTBLNO=1,ZONE=INT01,TARBAS="50";
CHANGE-TTBL:TBL=WOCU,TARTBLNO=2,ZONE=INT01,TARBAS="50";
The display and the attendant console show 1.51 EUR, and the data record
is:
RECNO:0028 STARTED AT 01-03-04/18:02
CONN_DUR : 13:16.5 UNIT : 00002
ATTNR : REC_PT: 2
TRANSIT_CNT: 0
***RECORD-END***
Explanation: The connection time was 13 minutes and 16.5 seconds, so a
total of 797 seconds was charged. 797 * 0.127 cents equals 1.0122 EUR, 0.5
EUR is added as the basic charge, and then the total is rounded down to two
places after the decimal point.
• Example 5:
The customer would like to set an exemption of 0.20 cents. In addition to the
basic configuration shown in Example 1, you need the following commands:
CHANGE-TTBL:TBL=WOCU,TARTBLNO=1,ZONE=INT01,TARBAS="-20";
CHANGE-TTBL:TBL=WOCU,TARTBLNO=2,ZONE=INT01,TARBAS="-20";
First data record: The credit of 0.20 cents is not used. Nothing is shown on
the display, the attendant console shows 0.00, and the data record is:
RECNO:0029 STARTED AT 01-03-04/18:22
CONN_DUR : 00:42.4 UNIT : 00000
TRANSIT_CNT: 0
***RECORD-END***
Explanation: After 42.4 seconds, 0.0546 EUR are charged, which is below
the free limit of 0.20 EUR.
A31003-H3170-S103-6-7620, 02/2019
Second data record: Credit is used up. The display and attendant console
both show 1.47 and the data record appears as follows:
RECNO:0031 STARTED AT 01-03-04/18:51
CONN_DUR : 21:57.2 UNIT : 00002
ATTNR :
REC_PT : 2
TRANSIT_CNT: 0
***RECORD-END***
Explanation: 1318 seconds costs 1.6739 EUR minus 0.20 EUR (free), so
the result is 1.47 EUR.
• Example 6:
The customer would like to set a minimum charge of 0.30 EUR. In addition to
the basic configuration shown in Example 1, you need the following
commands:
CHANGE-
TTBL:TBL=WOCU,TARTBLNO=1,ZONE=INT01,TARBAS="0",TARMIN=30;
CHANGE-
TTBL:TBL=WOCU,TARTBLNO=2,ZONE=INT01,TARBAS="0",TARMIN=30;
First data record (very short connection ):
The display and attendant console show 0.30, and the following call detail
record (CDR) is output:
RECNO:0032 STARTED AT 01-03-04/19:19
CONN_DUR : 00:03.0 UNIT : 00001
ATTNR :
REC_PT : 2
TRANSIT_CNT: 0
Explanation: Only the minimum charge of 0.30 EUR is displayed.
Second data record (longer connection):
A31003-H3170-S103-6-7620, 02/2019
The display and attendant console show 0.37 EUR and the following call
detail record (CDR) appears:
RECNO:0033 STARTED AT 01-03-04/19:21
CONN_DUR : 04:49.3 UNIT : 00001
ZONE : INTERN01 SWITCH_PR : ENDE
N
ATTNR :
REC_PT : 2
TRANSIT_CNT: 0
***RECORD-END***
Explanation: 290 seconds cost 0.3683 EUR which is rounded down to 0.37
(two places after the decimal point).
Output in the data record with more (maximum of five) places after the
decimal point
Example: Per-second billing should be performed for carrier 0. Selection group
1 is active. Calls that are billed with charge information from the outside (carriers
1 to 9) should be output with two places after the decimal point, and calls that use
per-second billing (carrier 0) should have five places after the decimal point.
Solution: Selection group 1 contains two selection tables. In the AMO DAVF, the
decimal point is set to +2, and in the AMO TTBL, COMPOS is set to 2HT.
In the example, output is to DEV1, number 4 is assigned two-place format and

number 8 is assigned five-place format.
ADD-
SELG:TBL=SELG,SELGNO=1,RESOP=Y,BASDEV=DEV1,RESDEV=DEV3,BLBAS=
1,BLRES=1;
CHANGE-
SELG:TBL=SELT,SELGNO=1,SELTABNO=1,FORMBAS=FORM04,FORMRES=FORM
04,TARIF=TARGR01,
DESTCNT=A22;
CHANGE-SELG:TBL=SELT,SELGNO=1,SELTABNO=1,CDRCD=0&&999999;
CHANGE-SELG:TBL=SELT,SELGNO=1,SELTABNO=1,SERVICE=VOICE;
CHANGE-SELG:TBL=SELT,SELGNO=1,SELTABNO=1,ATNDGR=0&&15;
CHANGE-
SELG:TBL=SELT,SELGNO=1,SELTABNO=1,CTYPE=ALL,PAYPARTY=ALL,CDRC
=N,CDRSTA=N,THRGCON=N,
NSTAT=N,SECTION=N,CDCHU=N,CDRAC=N,SFSETUP=N,CDBAD=N,CDRULTE=N
,CONNT=N,PCODE=N,PPCF=N,STATAB1=N,STATAB2=N,DNOTBL1=N,DNOTBL2
=N; 
CHANGE-
SELG:TBL=SELT,SELGNO=1,SELTABNO=1,CDRULT=0,CONNTL=000000;
CHANGE-
SELG:TBL=SELT,SELGNO=1,SELTABNO=1,LEVEL0=0&&999,LEVEL1=0&&254
A31003-H3170-S103-6-7620, 02/2019
,LEVEL2=0&&30;
CHANGE-
SELG:TBL=SELT,SELGNO=1,SELTABNO=1,TIELINE=N,EXPENS=N,CONNTYP=
INTERN&INCO&OUTG,
COPIN=0&&7,CARRIER=1&&9;
CHANGE-
SELG:TBL=SELT,SELGNO=1,SELTABNO=2,FORMBAS=FORM08,FORMRES=FORM
08,TARIF=TARGR01,
DESTCNT=A22; 
CHANGE-SELG:TBL=SELT,SELGNO=1,SELTABNO=2,CDRCD=0&&999999;
CHANGE-SELG:TBL=SELT,SELGNO=1,SELTABNO=2,SERVICE=VOICE;
CHANGE-SELG:TBL=SELT,SELGNO=1,SELTABNO=2,ATNDGR=0&&15;
CHANGE-
SELG:TBL=SELT,SELGNO=1,SELTABNO=2,CTYPE=ALL,PAYPARTY=ALL,CDRC
=N,CDRSTA=N,
THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,CDRAC=N,SFSETUP=N,CDBAD=N
,CDRULTE=N,CONNT=N,PCODE=N,PPCF=N,STATAB1=N,STATAB2=N,DNOTBL1
=N,DNOTBL2=N;
CHANGE-
SELG:TBL=SELT,SELGNO=1,SELTABNO=2,CDRULT=0,CONNTL=000000;
CHANGE-
SELG:TBL=SELT,SELGNO=1,SELTABNO=2,LEVEL0=0&&999,LEVEL1=0&&254
,LEVEL2=0&&30;
CHANGE-
SELG:TBL=SELT,SELGNO=1,SELTABNO=2,TIELINE=N,EXPENS=N,CONNTYP=
INTERN&INCO&OUTG,
COPIN=0&&7,CARRIER=0;
Configuration data for format 4:

,FORMAT="RECNO:#@@@ STARTED AT #@-#@-#@/#@:#@";
,FORMAT="PAYPART : #@@@@@@@@ DESTINATION:
#@@@@@@@@@@@";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=5,END=N,FORMAT="@@";
,FORMAT="CALL_ID : #@@@@@@@ CONN_TYP :
#@@";
,FORMAT="CALLEV0 : #@@@ LEVEL0 :
#@@@";
#@@@"; 
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FORM,NO=17
,END=N,FORMAT="CALLEV2 : #@@@ LEVEL2
: #@@@";
,FORMAT="CARRIER : #@@@@@@@@ ROUTE :
A31003-H3170-S103-6-7620, 02/2019
#@@@@@";
,FORMAT="DISC_CAUSE: #@@ SUPL_SERV :
#@@@@@@@@@";
,FORMAT="PIN_TYP : # PIN_NO :
#@@@@@@@@@@@";
,FORMAT="CONN_DUR : #@:#@.# UNIT :
#@@@@";
,FORMAT="CHARGE_ISP: #@@@@@@@ DISP_CHARG :
#@@@@@@@";
,FORMAT="EXPENSIVE : # RING_DUR :
#@@@";
,FORMAT="ZONE : #@@@@@@@@@ SWITCH_PR :
#@@@@@";
,FORMAT="START_TIME: #@:#@:#@.# END_TIME :
#@:#@:#@.# ";
,FORMAT="ATTNR : #@@@@@@@@@@@@@@@ REC_PT:
#@@@@@@@";
,FORMAT="TRANSIT_CNT: #@@@@@@@@@@";
,FORMAT="***RECORD-END***";
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=RECNO,
FILLTYPE=CHAR,FILLER="0",FLDALIGN=R;
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=STYEAR,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=3,FLDNAME=STMONTH,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=STDAY,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=5,FLDNAME=STHOUR,
A31003-H3170-S103-6-7620, 02/2019
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=6,FLDNAME=STMIN,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=7,FLDNAME=CHRGEE,
FILLTYPE=CHAR,FILLER=" ",FLDALIGN=L;
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=8,FLDNAME=DESTPTY,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=9,FLDNAME=GLOBSEQ,
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=10,FLDNAME=CONNTYPE,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=11,FLDNAME=GLOBLV0,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=12,FLDNAME=PPLV0,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=17,FLDNAME=CARRIER,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=18,FLDNAME=ROUTCN,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=19,FLDNAME=CAUSE,
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=20,FLDNAME=SUPLSERV,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=21,FLDNAME=COPIN,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=22,FLDNAME=PIN,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=23,FLDNAME=CONMIN,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=24,FLDNAME=CONSEC,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=25,FLDNAME=CON10,
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=26,FLDNAME=CHRGUNIT,
FILLTYPE=CHAR,FILLER=" ",FLDALIGN=RC,COMPOS=6;
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=28,FLDNAME=DISPCHRG,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=29,FLDNAME=EXPENS,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=30,FLDNAME=RINGDUR,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=31,FLDNAME=ZONE,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=32,FLDNAME=SWP,
FILLTYPE=CHAR,FILLER="0",FLDALIGN=R; 
A31003-H3170-S103-6-7620, 02/2019
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=35,FLDNAME=STSEC,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=36,FLDNAME=ST10,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=37,FLDNAME=ENDHOUR,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=38,FLDNAME=ENDMIN,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=39,FLDNAME=ENDSEC,
ADD-FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=40,FLDNAME=END10,
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=41,FLDNAME=TRNSFPTY,
ADD-
FTBL:FORMNO=4,TYPE=B,TBL=FIELD,NOFELD=43,FLDNAME=TRANSCNT,
FILLTYPE=CHAR,FILLER=" ",FLDALIGN=R;
Configuration data for format 8:

,FORMAT="RECNO:#@@@ STARTED AT #@-#@-#@/#@:#@";
,FORMAT="PAYPART : #@@@@@@@@ DESTINATION:
#@@@@@@@@@@@";
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FORM,NO=5,END=N,FORMAT="@@";
,FORMAT="CALL_ID : #@@@@@@@ CONN_TYP :
#@@";
,END=N,FORMAT="CALLEV0 : #@@@ LEVEL0
: #@@@";
#@@@";
#@@@";
,END=N,FORMAT="CARRIER : #@@@@@@@@ ROUTE
: #@@@@@";
,FORMAT="DISC_CAUSE: #@@ SUPL_SERV :
#@@@@@@@@@";
A31003-H3170-S103-6-7620, 02/2019
,FORMAT="PIN_TYP : # PIN_NO :
#@@@@@@@@@@@";
,FORMAT="CONN_DUR : #@:#@.# UNIT :
#@@@@";
,FORMAT="CHARGE_ISP: #@@@@@@@@@@@ DISP_CHARG :
#@@@@@@@";
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FORM,NO=33,END=N,FORMAT="@@@@";
,FORMAT="EXPENSIVE : # RING_DUR :
#@@@"; 
,FORMAT="ZONE : #@@@@@@@@@ SWITCH_PR :
#@@@@@";
,FORMAT="START_TIME: #@:#@:#@.# END_TIME :
#@:#@:#@.# ";
,FORMAT="ATTNR : #@@@@@@@@@@@@@@@ REC_PT:
#@@@@@@@";
,FORMAT="TRANSIT_CNT: #@@@@@@@@@@";
,FORMAT="***RECORD-END***";
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=1,FLDNAME=RECNO,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=2,FLDNAME=STYEAR,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=3,FLDNAME=STMONTH,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=4,FLDNAME=STDAY,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=7,FLDNAME=CHRGEE,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=8,FLDNAME=DESTPTY,
A31003-H3170-S103-6-7620, 02/2019
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=9,FLDNAME=GLOBSEQ,
ADD-
FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=10,FLDNAME=CONNTYPE,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=17,FLDNAME=CARRIER,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=18,FLDNAME=ROUTCN,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=19,FLDNAME=CAUSE,
ADD-
FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=20,FLDNAME=SUPLSERV,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=21,FLDNAME=COPIN,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=22,FLDNAME=PIN,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=23,FLDNAME=CONMIN,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=24,FLDNAME=CONSEC,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=25,FLDNAME=CON10,
ADD-
FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=26,FLDNAME=CHRGUNIT,
ADD-
FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=28,FLDNAME=DISPCHRG,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=29,FLDNAME=EXPENS,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=30,FLDNAME=RINGDUR,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=31,FLDNAME=ZONE,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=32,FLDNAME=SWP,
FILLTYPE=CHAR,FILLER="0",FLDALIGN=R; 
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=35,FLDNAME=STSEC,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=36,FLDNAME=ST10,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=37,FLDNAME=ENDHOUR,
FILLTYPE=CHAR,FILLER="0",FLDALIGN=R;R;
A31003-H3170-S103-6-7620, 02/2019
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=38,FLDNAME=ENDMIN,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=39,FLDNAME=ENDSEC,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=40,FLDNAME=END10,
ADD-
FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=41,FLDNAME=TRNSFPTY,
ADD-FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=42,FLDNAME=RECPT,
FILLTYPE=CHAR,FILLER=" ",FLDALIGN=R;
ADD-
FTBL:FORMNO=8,TYPE=B,TBL=FIELD,NOFELD=43,FLDNAME=TRANSCNT,
FILLTYPE=CHAR,FILLER=" ",FLDALIGN=R;
The configuration data listed at the beginning is used for the following
examples.
RECNO:0005 STARTED AT 01-03-11/09:57
CALL_ID : 00000006 CONN_TYP : OUTG
CARRIER : CARRIER_1 ROUTE : 01
CONN_DUR : 00:03.5 UNIT : 00001
ZONE : LONG01/DIST01 SWITCH_PR : ENDE
N
ATTNR :
REC_PT : 2
TRANSIT_CNT: 0
***RECORD-END***
Explanation: Trunk call, costs are sent from the central office; 0.93 appears
on the display and on the attendant console.
RECNO:0006 STARTED AT 01-03-11/09:56
CONN_DUR : 02:56.3 UNIT : 00001
ZONE : INTERN01 SWITCH_PR :
ENDE N
ATTNR :
REC_PT : 2
TRANSIT_CNT: 0
***RECORD-END***
A31003-H3170-S103-6-7620, 02/2019
Explanation: Connection calculated to the second, 0.22 appears on the

display and on the attendant console.
Example for output with four places after the decimal point:
RECNO:0007 STARTED AT 01-03-11/10:03
CONN_DUR : 03:58.7 UNIT : 00001
ZONE : INTERN01 SWITCH_PR :
ENDE N
ATTNR :
REC_PT : 2
TRANSIT_CNT: 0
***RECORD-END***
Explanation: Display and attendant console show 0.30.
NOTE: A maximum of three places after the decimal point can be output on
the display and attendant console but internal billing is more precise. The
decimal point position in the AMO TTBL has no effect on billing with external
charge information. As in the past, the AMO DAVF should be used to change
this.
A31003-H3170-S103-6-7620, 02/2019
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_rnr_mod_en.fm
Feature Description
75 Station Number Modification

Many customers need the station numbers that appear on the charge tickets in a
particular format. They consequently need an option for cutting off parts from or
adding parts to the station numbers (for example, ISDN codes, tie line access
digits, etc.).
These modifications are necessary for making efficient analyses. A suitable

modification is critical for further ticket processing using applications.
Station number modification in call data recording affects only the number output
in the charge tickets and so has absolutely no side-effects on the CP functionality.
An editable modification table can be used to configure digit patterns that can be
cut off or added.
Multiple cutoff patterns and one add-on pattern can be defined for each node
number. You can also configure the numbers to which these patterns should be
applied. In addition, you can define the minimum number of remaining digits.
The cutoff algorithm attempts to apply the longest pattern to each node number.
Each number is cut a maximum of one time. The station number is then added.
Should the resulting number be longer than 22 characters, the final digits are cut
off.

Remarks
An ADP soft restart is absolutely necessary after the patch is activated.
Restrictions
A maximum of 300 entries are possible in the CDR number modification table.

Configure the modification table with the AMO GEFE.
Configuration Examples:
1. Cut off the digits 201 for the CALLING party with node number 1-1-99; seven
digits must remain
CHANGE-GEFE:NMOD,1-1-99,,201,7,CALLING;
A31003-H3170-S103-6-7620, 02/2019
cdr_fues_rnr_mod_en.fm
2. Cut off the digits 201 for all three parties with node number 1-1-601; five digits
must remain.
Add the digits 4711 at the front for all three parties with node number 1-1-601.
CHANGE-GEFE:NMOD,1-1-601,4711,201,5,PAYING&CALLING&CONNECTED;
3. Add the digits 333 at the front for the connected party with node number 1-1-
401.
CHANGE-GEFE:NMOD,1-1-401,333,,5,CONNECTED;
4. Delete the add-on pattern 444 for node number 1-401.
DEL-GEFE:NMOD,1-1-401,333;
5. Delete the cutoff pattern 333 for node number 1-401.
DEL-GEFE:NMOD,1-1-401,333;
6. Delete the add-on pattern 4711 and the cutoff pattern 201 for node number 1-
401.
DEL-GEFE:NMOD,1-1-601,4711,201;
Messages
• Error messages from the modification part (patch):
CDR-NM: NO MEMORY!
No memory for storing the configuration that was read in.
CDR-NM: FILE :CGD:NUMBER-MOD-TAB NOT FOUND
No modification table (file) found.
CDR-NM: GENERAL ERROR!
General error
• Error messages from AMO GEFE:

F02: NODE NUMBER MAY NOT BE 0
F03: LEVEL@ THE NODE NUMBER MAY NOT EXCEED THE VALUE @@@
F04: LEVEL1 OF NODE NUMBER MAY NOT BE 0
F05: ???Problems accessing hard disk (e.g., A1H1F or A1H6F)
F06: The desired entry already exists.
F07: It is not possible to add more entries because the table
is full.
F08: ONLY ONE DADD IS POSSIBLE FOR SAME NODE NUMBER.
F09: DREM PATTERN ALREADY DEFINED FOR THIS NODE.
F10: THE ENTRY CANNOT BE DELETED.
F11: NO ENTRY FOUND.
H03: ENRTY HAS DELETED SUCCESFULLY.
A31003-H3170-S103-6-7620, 02/2019
rollring_en.fm
Groups
Groups
76 Audible Ringing on Rollover Lines
Audible Ringing
at Rollover volume
Call
Alert Ringing
at Rollover volume
Call
Audible Ringing
not set
Call
Figure 102 Audible ringing on rollover lines
The “Audible Ringing on Rollover Lines” feature, also known as “Rollover

Ringing” provides to customers with keyset telephones, the ability to hear ringing
lines signaled at their multi-line telephones, while active on a call. This is
especially helpful in high noise environments. The ringing is provided at a user
selected Rollover Ringing volume, which may be at a reduced level compared
with their ringer volume.
A31003-H3170-S103-6-7620, 02/2019
rollring_en.fm
User Interface
76.2 User Interface

The audible signaling of line appearances while the user is busy on a call is
provided automatically by the OpenScape 4000 switch, according to
administered options, at a volume which may also be individually set and
changed by the user, via the phone settings menu.

Audible Ringing on Rollover Lines is available on keysets having multiple line
appearances. It is configured on a per keyset basis.
The “signal when user is busy” option is provided via Administration (AMO KCSU)
to allow one of three rollover ring options, which is assigned to each individual
keyset to provide either -
1. No Ring when active on the telephone,

2. Alert Ring at the user selected rollover ring volume when active on the
telephone, or
3. Standard Ring at the user selected rollover ring volume when active on
the telephone.
Only line appearances which are assigned to audibly ring on the telephone will
be signaled when the user is active on the telephone.
An “Alert Ring” is a single short burst of ringing, sometimes also called a “Splash
Ring.”
Phone setting default values (including Rollover Ring volume) are administered
via AMO ZAND, and individual phone settings (including Rollover Ring volume)
are administered via AMO ACTDA and via the user’s phone settings menu.

• Set the default Rollover Ring volume for all Keysets -
CHA-ZAND:TYPE=OPTISET,ROLLVOL=3;
• Set an individual station to have a Rollover Volume of 3 -
ADD-ACTDA:TYPE=STN,STNO=3353,FEATCD=OPTISET,ROLLVOL=3;
• Create a Keyset, giving it the Standard Ring option for Rollover Ringing -
(Note: a station 3259 has already been created with a key standard
containing a LINE key at key position 1).
A31003-H3170-S103-6-7620, 02/2019
rollring_en.fm
Relevant AMOs
ADD-
KCSU:STNO=3259,TYPE=PRIM,PRIMKEY=1,RIOP=YES,ORLNPF=PRIME,TMLN
PF=ALER,SGLBMOD=YES,BUSYRING=STAND,OFFTYPE=DI;
76.5 Relevant AMOs
AMO Parameter New Sub Sprache/ Beschreibung / Description

Path Parameter Language
<value>
ZAND TYP= ROLLLAUT Deutsch Standard-Rollover-Tonlautstärke
OPTISET =<0-7> für alle Keysets, Wert 0-7
ZAND TYPE= ROLLVOL English Default Rollover Ring Volume for
OPTISET =<0-7> all Keysets, value 0-7.
ACTDA TYP=TLN, ROLLLAUT Deutsch Individuell für eine Sprechstelle
RNR=XXXX, =<0-7> eingestellte Rollover-
LMACT= Tonlautstärke, Wert 0-7.
OPTISET,
ACTDA TYPE=STN, ROLLVOL English Individual Rollover Ring Volume
STNO=XXXX, =<0-7> setting for one station, value 0-7.
FEATCD=
OPTISET
KCSU TLNNU=XXXX, RUFBES Deutsch Stellt für eine Sprechstelle die
TYP=PRIM =STDTON; Standard-Rufoption ein (Ruf bei
besetztem Telefon), d. h. der
Rollover-Ruf wird aktiviert.
KCSU STNO=XXXX, BUSYRING English Sets Standard Ring option for one
TYPE=PRIM, =STAND; station (Standard Ring means
Ring while busy) -
i.e. provide Rollover Ringing.
76.6 Interrelationship with other Features

The Audible Ringing on Rollover Lines feature has an effect on the description of
the signalling in "Key system functionality: Multi line access" (see Chapter 86,
“Integrated Key Functionality / Multi Line Access”)..
A31003-H3170-S103-6-7620, 02/2019
rollring_en.fm
Interrelationship with other Features
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
Directed Call Pickup
77 Call Pickup
77.1 Directed Call Pickup

The feature is available both locally and throughout the network. You will find a
description in Section 77.3.5.2, “Directed Call Pickup”.
77.2 Local Call Pickup Groups
*7
*7 *7
*7
*7

Users in a node are combined into a local pickup group so that they can take over
incoming calls for one another. Users do this by pressing a key or by choosing a
pickup code that is uniform throughout the system.
One way to configure call pickup groups is with the AMO AUN. A call pickup group
is comprised of users from this node (analog or digital devices). It is possible to
connect such a group to a call pickup group of an external OpenScape 4000 node
in the framework of a network-wide call pickup (over so-called "remote links", see
Section 77.3, “Network-wide Call Pickup”).
• System-wide attributes:
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
Local Call Pickup Groups
You can use parameters (such as AMO ZAND, OPTISET branch, PICKOPT
parameter) to select whether you must press the call pickup key on a Digite
once (PICKOPT=NO) or twice (PICKOPT=YES) to pick up a call from a call
pickup group. This is valid for the entire system. If the switch is YES, the first
time you press the call pickup key in the digit input you go to the directed call
pickup. You can then enter the destination number from which you want to
pick up a call. In this mode, the second time you press the key the call is
picked up from the call pickup group.
• Group-specific attributes:
For each call pickup group, you can set up the display of the calling user
(DISTNO) and the delayed notification ring (NOTRNG). 
To be able to pick up second calls, you must specify PUSECOND=YES. You
can use the parameter SIGNAL to define the type of signaling for incoming
calls at the station devices of a group.
• User-specific attributes:
The subscriber class of service GRPCAL (for example, AMO COSSU)
controls whether a user takes part in a group call (see Section 77.2.3, “Pickup
Group Call”), that is, whether an arriving call is acoustically signaled (instead
of via LED or display). This feature is also referred to as parallel call and is
possible locally and network-wide in the framework of a call pickup group.
• Moving users from one call pickup group to another

You can move users or remote links from one call pickup group to another
specific call pickup group with the AMO. You do not have to specify the
original group number to do this; the AMO AUN determines it. You only need
to specify the user(s) (or 1 remote link) and possibly the group to which you
want to move the user(s) (destination group). It is also possible to move an
area of users; the AMO AUN looks for the users from the respective groups
and gathers them in the destination group. If you do not specify the
destination group, the AMO AUN creates the next free group.
• Selecting call pickup groups during configuration or expansion

It is possible to identify a call pickup group by specifying the station number
of a user who is a member of this group. (The parameter GRSTNO was
introduced for this purpose.)
– Do not specify either parameter GRNO or GRSTNO in the ADD

command: This creates the next, in increasing order, free call pickup
group (for example, if groups 1, 2, 3, and 10 exist: group 4 is added).
– Specify only the parameter GRNO, not the parameter GRSTNO in the
ADD command: This creates or expands the call pickup group identified
by GRNO.
– Specify only the parameter GRSTNO, not the parameter GRNO in the
ADD command: This creates or expands the call pickup group that
already includes the user identified by GRSTNO.
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
– Specify both parameters (GRNO and GRSTNO) in the ADD command:

Not allowed, commanded is rejected with an error.
• Deleting users from different call pickup groups

It is possible to leave out the group number (GRNO) in the DELETE
command. In this case, the system determines the group in which a user is a
member. You can also delete several users who are not members of the same
call pickup group. They are removed from the respective groups.
• Type branch with display or regenerate in the AMO AUN.

The call pickup key is programmable by the user himself to any feature key. The
key-function „call pickup“ is offered via servicemenu.
Restrictions:
• A call pickup group may not have more than 255 members (users + remote
links).
• A group may have up to 255 Digites, but you should note that we do not
recommend full signaling (SIGNAL=ALL) if there are more than 25 Digites.
The default in this case is SIGNAL=LED and the default when there are more
than 75 Digites is SIGNAL=NONE. You can correct this setting for the
particular case.
• You cannot configure more than 1000 call pickup groups. Select and query
the current value in the dimensioning (parameter PUGR). If you enter a group
number during the configuration, it must be smaller than the PUGR value.
• A user may belong to only one call pickup group.
• The users in a call pickup group may not be silent monitors.
• You may not enter special users in a call pickup group.
• Users in a secretary system may not be in a call pickup group.
• A call pickup group must have at least 1 user. Therefore a group with only a
remote link is not allowed.
• The alerting call (NOTRNG) only applies to digital station devices.
• If there are more than 75 stations configured in a pick up group with

parameter GRPCAL in AMO COSSU, then the calls will not be signalled (no
ringing and no display).
• Pickup Group and Hunt Group with parallel ringing
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
Only private calls to the hunt group members are signalled on all pickup group
members. Calls to the master of a hunt group with parallel ringing are not
signalled on other pickup group members
77.2.3 Pickup Group Call
When there is a call to a station device (Anate or Digite), it is possible to

acoustically call other station devices that belong to the same group if they are
programmable (parallel call). All station devices called in parallel receive the
same type of call (normal, CO, or special call) and, in the case of Digite, the same
display information.
The call goes to the first user in the group to pick up or to take over the call by
using the call pickup button or dialing the pickup call code.
• All station devices that you want to be called in parallel must belong to the
same call pickup group and be specially identified for administration
purposes (in the Class of Service COS).
• All Digites that are not marked for parallel calling in the call pickup group
receive the normal call pickup group signal (display, LED, and alerting
call).
• If the code for parallel call is not set in the alternative COS, the user can
switch off or on his or her property as member of the group from "station
called in parallel" to "station only active for call pickup signaling" by
performing a class of service switch.
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
• During parallel signaling, the system does not check if there is

authorization to pickup up or answer the call. Therefore when you
configure the group, you should make sure that all users in the group
have the necessary authorization (class of service). If not, the user
receives a negative acknowledge when answering a parallel call.
• Group call is not implemented for functional terminals. Group call is also
allowed for Anates that are connected to optiPoints via terminal T/R
adapter.
• The maximum number of groups for group call corresponds to the

maximum number of call pickup groups: 1000.
• The maximum number of station devices called in parallel in a group is

(as for call pickup groups) 255. However when doing the configuration,
note that there is not more than 1 ringing current generator per shelf, so
that if more than 10 Anates are simultaneously supplied by the same
ringing current generator, the ringing may be not as loud.
• The parallel call to the group is only set up at the end of the initial call.
After a user becomes free, there is not a check for additional calls.

• Releasing the feature:
You can only release the feature in expert mode.

Expert mode --> ComWin --> Open ...< IP> using AMO (see AMO
command).
To use the AMO ZAND to release AUN:

CHANGE-FEASU:TYPE=A,CM=PU;
• Setting the mode for the call pickup key:
You can only set the mode in expert mode.

command).
If you want the press to call pickup key only once to pick up the call, you
must set the PICKOPT parameter as follows:
CHANGE-ZAND:TYPE=OPTISET,PICKOPT=NO;
If the parameter is YES, the first press of the call pickup key initiates the
directed call pickup. The second time you press the key the call is picked up
from the call pickup group.
• Configure the code for call pickup as follows:
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
You can only configure a code (with * or #) for call pickup in expert mode.
command).
To configure a code for call pickup using the AMO WABE:

ADD-WABE:CD=key_num,DAR=PU;
• You can configure the number of possible call pickup groups; this number
also corresponds to the largest possible group number.
You can only change the dimensioning data in expert mode.

command).
Set the number of possible call pickup groups with the AMO DIMSU,
parameter PUGR. 
ADD-DIMSU:PUGR=<number>;
• Configure a new call pickup group with default values as follows:
Configuration Management --> Groups --> Call Pickup, Extension tab,

click New and then enter the number. To add more numbers, click Add
(symbol at the right) and enter the other numbers in the new field. (You
must repeat this step for each station number.)
Using default values with the AMO AUN:
ADD-AUN:STNO=<number>;
• You can configure a new call pickup group with other group-specific
parameters as follows:

must repeat this step for each station number.) You can specify and
save the separate parameters (such as alerting call) under the Suppl.
Data tab.
Do not use the AMO AUN default values:
ADD-
AUN:STNO=number[,DISTNO=YES][,NOTRNG=PERIOD1][,PUSEC
OND=YES][,SIGNAL=LED];
• The user determines the call pickup group number during the reconfiguration.

must repeat this step for each station number.) You can enter and then
save the required group number (GRNO) for the call pickup group.
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
By entering the number with the AMO AUN:

ADD-AUN:GRNO=21,STNO=<number>;
• Move users from different call pickup groups into a new call pickup group
(number1, number2, number3 are already members of different call pickup
groups):
You can only administer the move of station numbers from one pickup
group to a new group in expert mode.
command).
Using the AMO AUN to move them is the same as a normal
configuration:
ADD-AUN:STNO=<number1&number2&number3>;
• Extend the call pickup group as follows:

enter the station number of a member of the call pickup group and click
Search. Click Add Entry (symbol at the right) and enter the new station
number in the new field.
(You must repeat this step for each station number.)
Determine existing call pickup group by the group number and expand
the group:
ADD-AUN:GRNO=1,STNO=<number>;
Or determine existing call pickup group by a user in the group:
ADD-AUN:GRSTNO=<number>,STNO=<number>;
• Change the group-specific parameters of an existing call pickup group as

follows:

enter the station number of a member of the call pickup group and click
Search. You can change and save the separate parameters (such as
alerting call) under the Suppl. Data tab.
Change with the AMO AUN:
CHANGE-
AUN:TYPE=GR,GRNO=1,{[,DISTNO=YES][,NOTRNG=ONIDLE1][,
PUSECOND=YES][,SIGNAL=NONE]};
The parameter NOTRNG determines whether or not the alerting call is sent:
(default: ON3 = multiple alerting call in all states).
• You can set up the time until the alerting call sounds for the AMOs AUN and
CHESE (default 15 sec.).
You can only administer the time until the alerting call sounds in expert
mode.
command).
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
Change the parameter BURST using the AMO DTIM1:

CHANGE-DTIM1:TYPEDH=DIGITE,BURST=<sec>;
• You can set the time interval for the periodic alerting call
(NOTRNG=PERIOD1,PERIOD3) (default = 5 sec.).
You can only administer the time for the alerting call in expert mode.
command).
Change the parameter NOTRNG using the AMO CTIME:

CHANGE-CTIME:TYPESWU=CPTIME1,NOTRNG=<sec>; 
(5 to 30 seconds)
• You can determine the parallel call for the call pickup member
(set the class of service in the user’s COS).
Configuration Management --> Tables --> Class of Service, tab Voice 1,

click parameter GRPCAL (checkmark appears) and save.
With AMO COSSU (class of service GRPCAL):

CHANGE-COSSU:TYPE=COS,COS=<number>,AVCE=GRPCAL;
• A floating station registers with PIN on a physical device that is assigned to a

call pickup group and additionally activates call forwarding. An incoming call
for the floating station is now signaled to the call pickup group members with
the name and number of the floating station (instead of the name and number
of the physical device on which it has registered).
IMPORTANT: The floating station won’t become a member of the call pickup
group.
With AMO ZAND (reserve parameter 195):

CHANGE-ZAND:TYPE=RESEVE,ELNUM=195,ACTIV=YES;
77.2.5 Other Remarks
IMPORTANT: When you CHANGE and DELETE call pickup groups, the call
pickup feature is no longer blocked. This eliminates any waiting times.
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
Network-wide Call Pickup
77.3 Network-wide Call Pickup

The network-wide call pickup feature is divided into two features:
1. Network-wide call pickup groups
2. Directed network-wide call pickup regardless of the affiliation with a call

pickup group.
FEASU
DIMSU
AUN
COT
WABE
255 max. groups
25 "LED display only"
75 "no display"
FEASU
WABE
COSSU
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
77.3.1 Network-wide Call Pickup Groups
This feature allows you to expand existing local call pickup groups to network-
wide call pickup groups ("network-wide call pickup and call parking").
group 1 group 10
7140 7141
808901,1 7240
808902,10
OpenScape Cornet-N
Q
4000 OpenScape
1-89-100 4000
1-89-200
Each call pickup group has a remote connection to other groups; this is identified
by an access code (open numbering plan, node code) and the group number.
The network-wide call pickup group acts as if it were in a PBX. Calls to one
extension are signaled to all others. During a call query, if the called user is in a
different PBX than the calling and querying user (that is, the user is "alone"), path
optimization is performed.
Call parking functions in a similar way. Each network-wide call pickup group has
its own "parking location".
Each local call pickup group can maintain up to 255 devices or remote
connections (at least one device), regardless of the device type (exception:
attendant console). If there are more than 25 local Digites, we recommend "LED
display only" and if there are more than 75 Digites, "no display". If full signaling is
not configured, the group call is deactivated.
Full visual signaling of the information is a new feature (display on demand); you
can configure it for the call. Visual signaling always depends on the local group
settings. Acoustic call signaling is the same for all network-wide groups.
77.3.2 Supported Features

Memory dimensioning (DIMSU) receives the new parameter REMPUGR (sum of
remote connections).
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
All requirements for route optimization must be met in the LCR before network-
wide call pickup can function. This means that the outdial rule for the station
number that you entered as the remote code must lead to the digit analysis result
OWNNODE in the remote system.
All 64 LCOS authorizations are automatically used in the network.
Example: CD Configuration in Closed Numbering NPI Unknown/TON

Unknown
Closed numbering
Source node Destination node
AUN WABE LODR WABE ZAND
REMAC 808902 ECHO 1 OWNNODE PNODECD
=808902 DAR NETW =808902 =808902
DESTNO 220
Example: CD Configuration in Open Numbering NPI Unknown/TON

Unknown
Open numbering NPI unknown

AUN WABE LDPLN/LODR WABE ZAND
REMAC=92 92 92-t OWNNODE PNODECD
DAR TIE ECHO 1 =92 =92
NPI unknown
TON unknown
Example: CD Configuration NPI ISDN / TON LOCAL
Open numbering NPI E164 (ISDN)

AUN/REMAC WABE LDPLN/LODR KNDEF WABE ZAND
REMAC= 0 TIE 0-89100-808902- CD after OWNNODE=80 PNODE
08910080890 T cutting own 8902 CD
2 ECHO 2 ISDN CD 808902
ECHO 3 808902
NPI ISDN ISDN
TON LOCAL Unknown
Circuits to and from PBXs before H V 1.0 need the circuit parameter NQPI
(between calling and called user, can also be Cornet-N) and NQNP (between
querying and called user, cannot be used for call pickup). This is not the case for
a dedicated transit system that supports Cornet-NQ.
Remote connections can also lead to PBXs that do not support broadcast
signaling (for example, Realitis). If the queue of the local call pickup group is
empty, the system blindly attempts the call pickup at this PBX until it is successful.
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
There are three more parameters for administering each remote connection -
whether pickup signaling is transmitted, whether signaling is received, and
whether park signaling is supported.
Broadcast signaling is executed over "Temporary Signaling Connections" (TSCs)

(one per group to each remote connection that is picked up for signaling or used
for the parked call). These TSCs are active until the queue of the call pickup group
is empty and the local "parking location" is empty. A timer starts as soon as this
situation occurs. When the timer expires, the TSCs are triggered. The default time
is 1800 seconds. You can modify it with the parameter GPUNST (for example,
AMO CTIME, branch CPTIME). 
If calls are signaled while the timer is running, the timer stops.
77.3.3 Directed Call Pickup
7140 7141
7143
**717143
7240
**717240
OpenScape Cornet-NQ
4000 OpenScape
DPNSS
1-89-100 4000
1-89-200
Starting with Version H V 1.0, directed call pickup, regardless of any call pickup
group affiliation, is possible. This feature allows waiting, switched off, or manually
held calls at any user to be queried network-wide.
In directed call pickup, you select the feature code (PUDIR) or select the menu
option at the terminal and specify the number of the dialed apparatus. This
feature applies both locally and network-wide, but is not connected to the
classically configured call pickup groups. This mean users can use this function
even if they are not in a call pickup group. With the COS authorization (BDCP), a
user can protect himself or herself from a directed call pickup. With the COT
parameter NQNP, you can block a line for a network wide call pickup (for
example, for systems that do not support the feature).
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
77.3.3.2 Special Aspects of the Feature
You can block directed call pickup either in the PBX of the location making the
pickup or in the PBX of the called location. To do this, block DIRCPCKP in the
feature bit string. To block it at the called party, set the COS parameter BDCP.
77.3.4 Service Remarks

Note the following remarks for both features.
• The systems must be connected using one of the following protocols:
• Cornet_NQ
• and DPNSS1
• You may not assign the following station devices in a call pickup group:
• Attendant console
• The feature is not checked via the dongle.
• You must provide for the digit analysis result "OWNNODE" in the digit
analysis and you must enter the parameter PNODECD in the central system
data.
• If you use an open numbering plan with NPI unknown, the "OWNNODE" of
the remote system is configured to the digit analysis result TIE.
• If you use an open numbering plan with NPI E164 or PNP, the OWNNODE of
the remote system does not appear in the digit analysis because the node
code of the system is completed to international format or Level 2 format.
• If you use a closed numbering plan, the "OWNNODE" of the remote system
is configured to NETW with appropriate destination number.
• After a call is picked up, the system performs path optimization if needed.
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
77.3.5 Generation Notes
77.3.5.1 Network-wide Call Pickup
Group 1 Group 10
7140 7141
7240
1-89-100 1-89-200
DESTNO 10
808901 808902 DESTNO 20
• In closed and open numbering plans
WABE 808902 NETW DESTNO ------> WABE 808902 OWNNODE

20
ZAND 808902 PNODECD
WABE 808901 OWNNODE <----- WABE 808901 NETW DESTNO

10
ZAND 808901 PNODECD
• For open calling plan
WABE 808902 TIE ------> WABE 808902 OWNNODE

ZAND 808902 PNODECD
WABE 808901 OWNNODE <----- WABE 808901 TIE

ZAND 808901 PNODECD
KNMAT 808901 UNKNOWN/ KNMAT 808902 UNKNOWN/

OWN OWN
LODR (e.g. LWR 1), ECHO 1

LDAT (e.g.: LWR 1), ......
LDPLN 808902-T
• Administer the remote connection in Group 1 as follows:
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
You can only administer the number of possible remote call pickup
groups in expert mode.
command).
Use AMO DIMSU to change the parameter REMPUGR: when needed:
ADD-DIMSU:REMPUGR=1;
Configuration Management --> Tables --> Dialing Plan --> Dial Codes,
click New. Enter dial code and select and save TIE as the dial code type.
Configuring a TIE digit analysis result using the AMO WABE:

You can only administer remote call pickup in expert mode.

command).
Configure the group using the AMO AUN:

ADD-
AUN:GRNO=1,STNO=7140&7141,REMAC=808902,REMGRNO=10;
• If the two PBXs do not exchange broadcast signaling (LED/display),

administer them as follows:
Configuration Management --> Groups --> Call Pickup, click New. On

the Station number tab, enter the station numbers of the members of the
call pickup group. Now change to the Remote Links tab and specify the
group number of the remote group (partner system) and select the node
code and required signaling parameters and save.
Configure call pickup group across the network with the AMO AUN:
ADD-
AUN:GRNO=1,STNO=7140&7141,REMAC=808902,REMGRNO=10,RE
MSIGO=NO,REMSIGI=NO,REMSIGPK=NO;
• You should deactivate local signaling at the group:
Configuration Management --> Groups --> Call Pickup, enter the group
number that you want to edit under "PU Group" and search. Now
change to the Suppl. Data tab and change the setting for signaling to
"none" and save.
Deactivate call pickup group signaling with the AMO AUN:
CHANGE-AUN:TYPE=GR,GRNO=1,SIGNAL=NONE;
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
77.3.5.2 Directed Call Pickup
• Release directed call pickup with the code **71:
You can only administer the release of DIRCPCKP in expert mode.

command).
Release DIRCPCKP with the AMO FEASU:

CHANGE-FEASU:TYPE=A,CM=DIRCPCKP;
You can only administer the digit analysis result PUDIR (with * or #) in
expert mode. 
command).
Configure the digit analysis result PUDIR with the AMO WABE:
ADD-WABE:CD=**71,DAR=PU;
77.3.5.3 Display on Request
• Configure the feature "Display on request" with the code **72:
You can only administer the digit analysis result PUGDIS (with * or #) in
expert mode.
command).
Configure the digit analysis result PUGDIS with the AMO WABE:
ADD-WABE:CD=**72,DAR=PUGDIS;
77.3.5.4 Configure call pickup throughout the network on

PBXXX
• If a circuit leads to the PBXXX, you must use "Extended Facilities" instead of
segmentation for the EConfiguration ManagementA-V2 protocol. The circuit
needs the COP parameter ASEG and you must configure the following in the
AMO PRODE:
You can only administer a protocol change in expert mode.

command).
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup
Make the changes in the protocol with the AMO PRODE:

CHANGE-
PRODE:KIND=PD,PDNAME=PD14,SEC=WELMAND,SETNO=14,B10=4
0,B30=40;
CHANGE-
PRODE:KIND=PD,PDNAME=PD14,SEC=WELMAND,SETNO=46,B10=4
2,B30=42;
CHANGE-
PRODE:KIND=PD,PDNAME=PD14,SEC=WELNAME,CS=00,NO=13,B0
0=06;
CHANGE-
PRODE:KIND=PD,PDNAME=PD14,SEC=RESTP,PDBLK=WELHEX,NO=
12,B00=0D;
CHANGE-PRODE:KIND=PD,PDNAME=PD14,SEC=ORG,ACTIVE=Y;
77.3.6 AMO Changes

Language
AUN GRUTLNNU d Teilnehmerrufnummer, die eine AUN-
Gruppe bezeichnet
GRSTNO e station number depicting a pickup group
REMKZ d Remote Knotenkennzahl
REMAC e remote access code
REMGRUNU d Remote Gruppennummer
REMGRNO e remote group number
SIGNAL d Signalisierungsmodus (ALLE, KEINE, LED)
SIGNAL e signaling mode (ALL, NONE, LED)
REMSIGAB d Remote Signalisierung abgehend
REMSIGO e remote signaling outgoing
REMSIGAN d Remote Signalisierung ankommend
REMSIGI e remote signaling incoming
REMSIGPK d Remote Signalisierung fuer Parken
REMSIGPK e remote signaling for parking
COSSU SGAUN d Sperren der gezielten Anrufuebernahme
BDCP e blocking of directed call pickup
UUS1IM d Nutzung des Dienstes uus1 implizit
UUS1IM e use of user - user signaling 1 implicit
DIMSU REMAUNGR d Anzahl der AUN-Gruppen in fremden
Knoten
REMPUGR e number of pickup groups in remote nodes
COP ASEG d CorNet-NQ Facility Segmentierung
ausschalten
A31003-H3170-S103-6-7620, 02/2019
aun_cm_en.fm
Call Pickup

Language
ASEG e switch off CorNet-NQ facility segmentation
COT ETSC d Nur ETSI USS3 protokollkonforme
Meldungen werden zugelassen
ETSC e UUS ETSI conform
NQPI d CorNet-NQ Pickup-Info nicht unterstützt
NQPI e CorNet-NQ Pickup-Info not supported.
NQNP d CorNet-NQ Netzweite Übernahme nicht
unterstützt.
NQNP e CorNet-NQ Network-wide Pick-up not
supported.
UUS1 d User to user implizit (kommend)
UUS1 e UUS Service Class 1 (Connection Setup
Basic Call)
UUSC d UUS3 Begrenzung der Datenmenge
UUSC e Congestion Control for User-User Service
CTIME GPUNST d Netzweiter AUN TSC-Abbruch Timer
GPUNST e network-wide group pick-up tsc teardown
timer
UUS3T1 d Maximale Wartezeit auf eine
Antwort(Netzwerkseite)
UUS3T1 e uus3 request started on called network
UUS3T2 d Zeiteinheit für maximale Meldungen pro
Zeiteinheit
UUS3T2 e uus3 info message started on net side
FEASU DIRAUN d Direkte Anrufübernahme
DIRCPCKP e directed call pick up
TDCSU UUSCCY d Anzahl von Meldungen die pro Zeiteinheit
(UU3T2) bis zum Maximum (UUSCCX)
aufgestockt wird.
UUSCCY e UUS congestion control Y
WABE AUNGANZ d Anzeige der Gruppen AUN Information
anfordern
PUGDIS e display group pickup information on request
AUNGEZ d Gezielte Anrufuebernahme
PUDIR e directed call pickup
ZAND UUS d DIVUUSUmlenkung erlaubt
NODIVUmlenkung verboten
DIVSUPUmlenkung abhängig von der
Berechtigung
UUS e User-User Signalling for DSS1 Devices
A31003-H3170-S103-6-7620, 02/2019
chese_en.fm
78 CHESE - Integrated Executive/Secretary System

Integrated executive/secretary systems are created with the AMO CHESE. The
AMO is used to assign users to executive/secretary groups, and to define their
status (executive, secretary or substitute secretary).
A mailbox can be defined as the forwarding destination for call forwarding if busy
and forwarding on no answer for calls to an executive member of a CHESE.
The following points must be borne in mind:
• Only digital telephones can be assigned to an executive/secretary system.

Digital telephones without a display (parameter DIGNODIS in SBCSU)
cannot be assigned as executive or secretary telephones in a CHESE
system. Keysets can not be assigned as executive or secretary. CMI mobile
phones, however, can be configured in a CHESE as executive.
• When configuring the telephones, before they are assigned to the executive/
secretary system, the appropriate key layout standard must be downloaded
from the database (SBCSU, parameter STD). Secretary terminals must be
defined by declaring SECR=Y. If a subscriber has been configured with
SECR=NO, it can be changed later on to SECR=YES (AMO SBCSU).
• Executive stations and secretary stations require special function keys for the
CHESE features:
1. Executive telephone
a) one RNGXFER key (transfer of ringing to secretary telephone)
b) one DSS key (direct station select) for DSS to secretary (also to
second secretary telephone if required)
2. Secretary telephone
a) one PUS key (call pick-up) for each executive telephone in the
configuration
b) one RNGXFER key for each executive telephone in the configuration

(transfer of ringing)
c) one DSS key per executive telephone (direct station select)
d) one REP key for activating/deactivating call forwarding to secretary’s

representative.
• The function of the four PUS and RNGXFER keys of the secretary telephone
can be changed via the TAPRO AMO, but not at the telephone itself.
• An executive/secretary configuration can comprise up to 4 executive, 2

secretary and 2 substitute secretary terminals (representatives).
A31003-H3170-S103-6-7620, 02/2019
chese_en.fm
• Neither an executive nor a secretary representative terminal may be assigned

a hunt group master call number. Secretary terminals, however, are allowed
as hunt group masters.
• The executive features FNANS (call forwarding on no answer) and FWDBSY

(call forwarding if busy) can be assigned a voice mailbox as a forwarding
destination. The following voice mailbox options can be set:
NONE: Calls to the executive will not be forwarded to a voice mailbox with the
FNANS or FWDBSY features (default setting)
EXEC: The FNANS and FWDBSY features will forward calls to the executive’s
voice mailbox
SECR: The FNANS and FWDBSY features will forward calls to the secretary’s
voice mailbox
The chosen setting is terminal-specific, and only works if
– The RNGXFER key on the executive telephone is not activated (i.e. no

transfer of ringing to secretary)
– the voice mail server (VMS) is entered as the FNANS/FWDBSY

destination for the executive terminal
If a secretary has activated the representative (REP) function, this will not
affect the feature. However, if the executive has activated the standard call
forwarding feature for all calls (FWD), this will take priority.
• Each executive and secretary station can only belong to one group. Secretary
representatives can belong to more than one group. Secretary telephones
can also be assigned as secretary representatives. Secretary telephones can
also be entered in a group without being assigned an executive (second
secretary).
• The activation and deactivation of the substitute secretary is initiated at the

secretary terminal.
• The REP (substitute secretary) destination can also be assigned with the
CHECK key of the secretary terminal. When the REP function is deactivated,
the old destination is automatically restored.
• If an executive has entered his or her secretary as a direct station selection

destination, this function is automatically transferred to the substitute station
if activated, even for substitutes of more than one secretary. When the
substitutes are deactivated at the secretary terminal, the DSS destination is
changed back.
• Each executive/secretary system is assigned a number for administration

purposes. If this number is not explicitly specified when the system is initially
added, the AMO automatically assigns the first free number.
A31003-H3170-S103-6-7620, 02/2019
chese_en.fm
Assign a Secretary Telephone
• The maximum number of integrated executive/secretary systems is defined

with the ES parameter of the DIMSU AMO (max. 1000), and the maximum
number of stations in all CHESE systems is limited with the ESSTN
parameter.
• Members of an executive/secretary system can also program a

MESSENGER key on their terminal. The messenger code leads to an analog
port to which a bell or a telephone can be connected. The connection is
assigned with the AMO SSC and is allocated an access code for
administration purposes rather than a dialling number.
• The timer for the notification ring delay has to be set with parameter BURST
of the DTIM1 AMO.
• CHESE calls for the executive which are picked-up by the secretary, are
logged in the executive’s call log.
2 or more executives are assigned to one secretary: When one caller calls all
executives one after the other, every executive gets an entry in its call-log of
not-answered calls.
The secretary gets all calls but only the last call is stored in its call-log (update
of time of call of the older entry in case of calls from the same caller).
After answering/deleting the last call, the call-logs of the other executives is
not updated.
• Secretary has enabled the representative function (REP key). If there is an

incoming CHESE call for the executive, this is signaled for the representative
and now also on the executive's display. An alerting tone is generated for the
executive after a time (AMO DTIM1, Parameter BURST). This otherwise only
happens if the secretary has not activated the representative function.
CHANGE-ZAND:TYPE=RESERVE,ELNUM=194,ACTIV=YES;
CHANGE-DTIM1:TYPEDH=DIGITE,BURST=<time in seconds>;
78.1 Assign a Secretary Telephone

• Assign the station
The parameter SECR=Y must be declared in the SBCSU command.
When adding the terminal with the AMO SBCSU, the appropriate key layout
standard must be assigned to the secretary terminal with the parameter
STDNO.
• Display service information field of key layouts

DIS-TAPRO:TYPE=STD,STD=34&&37,FORMAT=S;
• Assign an executive user to an executive/secretary system
CHA-CHESE:GRNO=number,TYPE=ADDSTN,EXEC=number,SECR=number;
A31003-H3170-S103-6-7620, 02/2019
chese_en.fm
Assignment of the Messenger Facility
• Assign a secretary user to an executive/secretary system

CHA-CHESE:GRNO=number,TYPE=ADDSTN,SECR=number;
• Assign the executive mailbox as FNANS/FWDBSY destination
CHA-CHESE:GRNO=number, TYPE=EXEC,EXEC=number,MB=EXEC;
78.2 Assignment of the Messenger Facility

The messenger facility can be assigned to one or more terminals in an executive/
secretary system with the AMO ZIEL or a procedure at the terminal. 
Allocating a messenger to several executive/secretary systems is only feasible if
the secretary terminals are in the same office, since it is not possible to establish
who has rung. The messenger call is initiated with the messenger button. 
Prior to deletion the facility must be released from its allocation to executives and
secretaries. These allocations are interrogated with the AMO ZIEL. 
The messenger code must always be 3 digits long so it can be recognized as
messenger number by the OpenScape 4000 set.
• Add the "messenger key" DAR in the DPLN

AD-WABE:CD=key-num,DAR=MSGRKY;
• Assign messenger to free SLMA
AD-SSC:TYPE=MSGR,MSGRNO=number;
The messenger number MSGRNO is purely an administration number, and is
therefore not entered in the DPLN.
• Assign the messenger key at the executive terminal

CHA-TAPRO:STNO=number,KYxx=MSGR;
• Assign the messenger to the executive telephone
AD-ZIEL:TYPE=MSGR,SRCNO=number,DESTNOM=number;
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
CHESE/ Team Functions Network-wide
Feature Description
79 CHESE/ Team Functions Network-wide

Use this feature to implement network-wide team functions such as Chese, key
set, and network-wide direct station selection.
Each station device is

integrated in a key system.
Use the AUN groups to
connect the key systems.
virtual network-wide call pickup group over all systems
Networked
system via Cornet
NQ.
NETTEAM in the
AMO ZAND is set
to YES.
You must connect all

systems via Temporary
Switched Connections
(TSC).
allow the TSC connection with card subscribers
Max. 4 executive and 4

secretary telephones.
Distributed among any
OpenScape 4000 systems

The "network-wide team" is not a separate feature like the CHESE, but is instead
a useful combination of existing independent features with several very special
changes, for example, to fit the user interface to the CHESE. The basic features
used here are:
• Keyset 300 E
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description
• Network-wide call pickup
• Different versions of call forwarding
All network-wide signaling relationships are produced with the feature "network-
wide pickup groups".
79.1.2 Team Functions

Secretary systems that are formed as a "network-wide team" have the following
features:
• Executive line
• Private line
• Secretary line
• Network-wide direct station selection
• Network-wide signaling of station status
• Voice calling and auto answer
• Ring transfer
• Secretarial function transfer
• Conference corner telephone
• Ringer cutoff
Each member of a team can also use all other features such as callback, do-not-
disturb, number redial, call waiting, voice server (with the possibility of saving
messages in the mailbox of the executive or the secretary), etc.
All members of a "network-wide team" can be in different network nodes. All

features described above are available without restrictions to the team members.
Executive line
Each call to an executive arrives at the executive line (executive station number)
either directly or after the secretary forwards it. This is usually the line where he
or she makes outgoing calls.
The secretary or secondary secretary is also connected to the executive line of

all executives assigned to him or her. The secretaries receive a visual signal
(quickly blinking LED) and an acoustic signal (alerting call tone) on these lines for
calls to the executive (executive calls). On the other hand, only a quickly blinking
LED notifies the executive of a call. The LED lights up as soon as the executive
or the secretary takes the incoming call.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description
The secretary can handle incoming or outgoing calls at any time by changing to
any line. This automatically puts the current call on hold. The LED blinks slowly
for the held line.
Private line
You can configure a private line (private number) for each executive. The
executive can make or accept calls on the private line independently of the
executive line. The secretary is not signaled for incoming or outgoing calls on the
private line.
The private line can be forwarded independently of the executive line. The
forwarding is not signaled on either the display or with an LED.
Secretary line
Each secretary has a separate line (station number) for his or her "personal" calls.
The executive normally receives no notification of "personal" secretary calls
(secretary’s personal line).
Network-wide direct station selection

An executive has a DSS key configured for each secretary to allow him or her to
reach the secretary. Of course a secretary can also have a DSS key configured
to each of his or her executives. Like the CHESE, the direct station selection does
not follow call forwarding. If call forwarding is active at a direct station selection
destination, it does not take place.
Network-wide signaling of station status

The DSS key LED signals free or busy network-wide for the partner in question.
The DSS key LED displays the following states:
LED off Partner is free

LED is lit Partner is busy
LED is blinking Incoming call to partner You can accept the call by pressing the DSS
key for the partner.
Voice calling and auto answer

For security reasons, you can use the administration to configure voice calling
and auto answer (one-way hands free intercom system) only for specially
identified direct station selection or name keys. Voice calling and auto answer are
also possible across nodes.
Ring transfer
By pressing the intercept key of an executive, each secretary can forward
incoming executive calls to the secretary apparatus. This secretary then becomes
the active secretary. Incoming executive calls are signaled at the secretary
acoustically and visually in the display and at the executive by a blinking LED. All
other secretaries receive an alerting call tone and a display on their terminals.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description
If a different secretary presses the intercept key for this executive on his or her
telephone, he or she become the active secretary. Executive calls are then
forwarded to this secretary (remote call forwarding). In the idle display, the
executive always see the name or phone number of the secretary who is currently
his or her active secretary.
Each executive can also forward all calls to the secretary by pressing the
intercept key.
Intercept key off Ring transfer to primary secretary is not active; the primary secretary
does not receive executive calls
Intercept key on Ring transfer to primary secretary is active; the primary secretary
receives executive calls
Attention: This is a major difference to CHESE!
Secretarial function transfer

• Activating the secretarial function transfer
• The active secretary can forward all executive calls to a different

preselected (using administration software) secretary of the same team
by pressing the secretarial function transfer key. The intercept key LEDs
at the forwarding secretary go out. Now the intercept key LEDs at the
delegate secretary, the new active secretary, light. The secretarial
function transfer key LED does not light there. - Secretary calls are also
forwarded to the delegate.
Important: The secretary is not allowed to program the delegate
destination; configure this with administration software. Only a user
within the same team can be a delegate.
• Deactivating the secretarial function transfer
• Only the secretary who previously activated the secretarial function

transfer can turn it off again by pressing the intercept key (not the
delegate key). The secretary only deactivates the secretarial function
transfer for the executive in question; the secretary becomes the active
secretary for his or her executive again.
Ring transfer for secretary calls ("personal" calls for the secretary) are still
delegated; this can be cancelled either by pressing the FWD key or by
using the service menu.
Conference corner telephone

Executive and secretary are always put together in a pickup group. You can also
configure a telephone assigned to the executive as a conference corner
telephone in the pickup group.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description
Ringer cutoff
You can configure a ringer cutoff key at the executive to switch off the acoustic
signal.
There is then only a visual signal on the display and via LED for incoming calls.
79.1.3 Network-wide Team in Combination With

Additional Features
Although you can use the network-wide team as a secretary system like the
CHESE, some features are treated differently than with the CHESE. The
following sections describe the most important features.
Recorded announcement server

If an executive call forwarded to the secretary is not answered within a particular
time, it is forwarded to a call forward - no answer destination, if this is configured.
Like with the CHESE, with network-wide team you can select whether a call
intended for the executive should be directed to the executive mailbox or the
secretary (department) mailbox.
If configured, the same also applies for forwarded executive calls to a busy
secretary.
• Callback
• When executive line is busy

If executive calls are forwarded to the secretary (normal operation), the
system always carries out a callback when the secretary is free again.
The callback occurs regardless of whether the executive is free or busy.
• When executive line is free

A callback to a free executive that is signaled at the secretary is not
entered in the mailbox. The system always performs callback on free the
next time the executive line or the secretary is free.
79.1.4 Comparison of Current Chese With Network-

wide Team Function
Network-wide team function Local Chese

Max. 4 secretaries and max. 4 executives. Max. 2 secretaries and max. 4 executives.
Each executive has an active secretary. Secretary is defined as primary or
secondary secretary.
Each user can be in a different system All in the same system (except with
extended connection)
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description

Executive has one line key each for team Executive has one call pickup key for
line and private line. Directed call take picking up calls forwarded to the secretary
over is possible with each key and outgoing and to pick up second calls.
calls can be set up on each line. A call
pickup key can also be added to takeover
second calls.
Private number configured as phantom Private numbers configurable only via code
line. Can be forwarded. Can be directly hunt group. No special forwarding of the
queried. private number possible.
Executive has intercept key. It lights when Executive has intercept key. It lights when
calls to the executive are forwarded to the calls come directly to the executive; this
secretary. means without forwarding.
Major difference.
Executive has one DSS key to the Executive has one DSS key per
secretary. It lights when the secretary is secretary.. It lights when the secretary is
busy on one of the lines. The LED blinks busy and it blinks when there is an acoustic
when there is a call to the secretary. call at the secretary.
Call pickup possible by pressing the Call pickup possible by pressing the
blinking DSS key. blinking DSS key.
Secretary has one line key for calls to the No special key. No difference between
secretary number. It blinks when there is a secretary line and executive line
call and lights when the line is busy.
Secretary has line key for calls to the Secretary has call pickup key for each
executive that were forwarded to him or executive. LED blinks if secretary is busy
her. Key blinks when there is incoming call and call does not ring. LED does NOT light
(in addition to ringing) and lights during a during call.
call.
Whichever call is oldest rings at the active Whichever call is oldest rings at the
secretary, which means there is a queue secretary, which means there is a queue
for waiting calls. for waiting calls.
Secretary has an intercept key for each Secretary has an intercept key for each
executive. It lights when calls for the executive. It does NOT light when calls for
executive are forwarded to this secretary. the executive are forwarded to this
secretary.
In addition, ring transfer status signaled In addition, ring transfer status also
only at executive (no secondary secretary signaled at executive and secondary
defined). secretary.
If another secretary presses the non- If the secondary secretary presses the ring
lighting intercept key, the forwarding is transfer key, exactly the same thing
reprogrammed at the executive to this happens as when the executive or
secretary. Display at executive in idle primary secretary presses the key: the
display. The LED at the previously active status is changed (activating or
secretary goes out. deactivating).
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description

Secretary has secretarial function Secretary has secretarial function
transfer key. When the secretary presses transfer key. When the secretary activates
this key, forwarding for all executives for this by pressing the key, executive calls are
which this secretary is active is forwarded to the delegate destination.
reprogrammed to the delegate destination. Secretarial function transfer key LED
The secretary number is also forwarded to lights.
the delegate destination if it has not been
forwarded anywhere else. Secretarial
function transfer key LED does NOT light.
No team overlap possible. Team overlap possible. Delegate can
delegate for several teams.
Secretary cannot program delegate. Only Secretary can program delegate. Any
via AMO. Delegate must be in team. delegate.
No reprogramming of DSS key when DSS key at executive is reprogrammed
activating the delegate. to the delegate destination during
delegation.
No cancellation of the delegation via Cancellation of the delegation via
secretarial function transfer key; only via secretarial function transfer key. LED goes
intercept key at secretary. When the active out. Ring transfer status determines who
secretary presses the lit key, ring transfer receives the executive calls.
switches off and calls come to the
executive. If another secretary presses the
unlit key, executive calls come to him or
her.
Switch off ring transfer at executive so that Switch off ring transfer so that calls come to
calls come to the executive. Ring transfer the executive. This takes priority over an
LEDs go out at executive and secretary. If active delegation. If executive switches
executive switches ring transfer on again, ring transfer on again, calls go to delegate
calls go to last active secretary. destination again.
Executive can program fixed or variable Executive can program fixed or variable
forwarding for executive and private forwarding. Calls go to forwarding
number separately. Calls go to forwarding destination regardless of ring transfer or
destination. Ring transfer is also a variable delegate status. After forwarding is
forwarding. deactivated, the selected ring transfer or
delegation is in effect again.
If ring transfer is activated at a secretary, If ring transfer is activated at a secretary,
this changes the forwarding destination of this does NOT change the forwarding
the executive calls. This also writes over a destination of the executive calls. A
forwarding programmed by the executive forwarding programmed by the executive
himself of herself (for example, external). himself of herself does not change.
Forwarded executive calls must be No call forwarding - no answer for
forwarded to the CFNR destination after forwarded executive calls at secretary.
some time.
Forwarded executive calls must be No call forwarding on busy for forwarded
forwarded to the call forwarding busy executive calls at secretary.
destination when the executive line is
busy.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description

Call back to busy executive line (if Call back to busy executive line (if
forwarded to secretary). Call back is forwarded to secretary). Call back should
performed when the executive line at the be performed only when executive and
secretary becomes free. Call back occurs secretary are free.
regardless of whether the executive
apparatus is free.
Call back to free executive line (if Call back to free executive (in call state)
forwarded to secretary) cannot be entered is entered in the executive mailbox even if
in a mailbox because a phantom line never the call was forwarded to the secretary.
has a mailbox. Therefore it is a callback on
free.
Forwarding, forwarding on busy, or call Forwarding to voice mail.For each
forwarding - no answer to voice mail. For system, you can decide whether the voice
each executive, you can decide whether mail entry should be made in the executive
the voice mail entry should be made in the or secretary mailbox.
executive or secretary mailbox.

• You must follow the generating order given. In particular, before you configure
the keys with the AMO TAPRO you must set TEAMBIT with the AMO SDAT
because otherwise there is not enough memory for the RNGXFER keys.
• Give all nodes in a network in which the "network-wide team" is configured a

new central code with the AMO ZAND that cannot be reset via AMO (only with
patch). Various AMOs, which implement the new functions, query this code.
This allows mixed operation and the configuration of network-wide teams or
"internal teams" of the new kind and internal teams with AMO CHESE.
However this should be the exception!
• You can assign a secretary to one or more executives; unlike the "old"
CHESE, this assignment is not fixed because it wanders through the delegate
function.
• You essentially implement the network-wide team with the feature "network-
wide call pickup".
• Delegate function: Each secretary has a REP key to transfer his or her
function to a delegate or representative. The delegation can only be to
another secretary in this team and is a fixed assignment. You can only change
the assignment by disbanding and reconfiguring the team, but this is not
critical because the "care" of one or more executives can also be actively
transferred by pressing the appropriate RNGXFER key(s). The RNGXFER
key at the affected executive is reprogrammed when the delegation is
activated.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description
• Use the AMO AUN to assign a three-digit team number to each station
number in a network-wide team, the prime line of the executive, and all
phantom lines at the secretaries assigned to this executive. DMS uses this
number, which must be unambiguous throughout the network, only for
administration purposes. The AMO does not check that the number is
unambiguous.
The "private line" of the executive (phantom) and the prime line of the
secretary telephone do not receive a team number.
• The station devices of network-wide team members are configured as key

sets.
• If necessary, the executive is given a "phantom line" as a private line.
• Each secretary receives one "phantom line" for each executive assigned to
him or her.
These must have the code for group call in their COS so that calls to the
executive can also be signaled at the secretary.
• The executive’s prime lines and the secretary’s phantom lines are identified
in the line memory as "executive" or "secr" (AMO SDAT).
The executive’s "private line" does not receive an executive code.
• Ring transfer: Each executive receives one RNGXFER key that he or she
can use to transfer calls (or take them back) on his or her prime line to the
secretary. The station number of the currently assigned secretary’s phantom
line for this executive is entered on the RNGXFER key. If this secretary
activates a delegate, then the RNGXFER key is updated with the station
number of the corresponding phantom of the current secretary. If several
RNGXFER keys were activated at the secretary, the RNGXFER key
destinations for all affected executives are rewritten when the delegation is
activated. 
Each secretary receives a RNGXFER key for each assigned executive; he or
she can also activate or deactivate the ring transfer for each executive with
the key. Thus the secretary can actively take over the delegation for each
executive of this team by pressing the corresponding RNGXFER key. In this
case, the destinations are also reprogrammed on the RNGXFER keys of the
affected executive.
• PUS keys are not configured.
• Direct station selection network-wide
• Direct station selection (DSS) destinations (both internal and external) for
"network-wide teams" are configured only by AMO (AMO ZIELN); the
DSS key is marked as "network-wide" if the destination is external. Use
the pickup group to implement the network-wide relationship. The
destination must be a member of a call pickup group that is on the source
device. Use the new AMO ZIELN to edit all DSS destinations that are
involved with the "network-wide team". You cannot change the
destinations from a station device.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description
To prevent a flood of messages concerning the signaling of the free and

busy status of members of network-wide call pickup groups, station
numbers that are entered somewhere as a network-wide DSS destination
receive a special "direct station selection destination network-wide"
identifier (AMO SDAT).
• Stations that have network-wide destinations on their DSS keys also

receive a code in the line feature "source for network-wide DSS
destination". The AMOs ZIEL and ZIELN evaluate this as regards
regeneration.
• Each executive receives one DSS key for each secretary in the team. The
contents are not reprogrammed when ring transfer is activated. Each
secretary receives one DSS key for each executive in the team.
• Call pickup groups for network-wide team:
1 executive/1 secretary
Call pickup group prime line (Pri) executive + phantom (Pha) of the
secretary for executive
call pickup group 1: Prime line executive1 + phantom of the secretary for
executive 1
Call pickup group 2: Prime line executive2 + phantom of the secretary for
executive 2
Call pickup group 1: prime line C1 + phantom S1 for executive 1 + phantom S2
for executive 1;
for executive 2;
for executive 3;
Call pickup group 4: prime line C4 + Phantom S1 for executive + phantom S2
for executive 4
Call pickup group 1: Pri_C1 + Pha_S1_ C1 + Pha_S2_ C1+Pha_S3_C1 +
Pha_S2_C1;
Pha_S2_C2;
Pha_S2_C3
Call pickup group 4: Pri_C4 + Pha_S1_ C4 + Pha_S2_ C4 + Pha_S3_C4 +
Pha_S2_C4;
• If there is more than one secretary, you must configure a call pickup between
the prime lines of the secretary telephones so that they can accept calls for
one another.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description
• Destination entries (station numbers)

RNGXFER key at executive
prime line executive + phantom secretary for the executive
RNGXFER keys at secretary per executive
RNGXFER1: prime line executive 1 + phantom for executive 1
RNGXFER2: prime line executive 2 + phantom for executive 2, etc.
Secretarial function transfer keys at the secretary telephone
You must save the following for each REP key to activate the function
transfer: Station number of the secretary (prime line), station number of the
delegate (prime line), and station number of each assigned executive
Prime line executive 1 + phantom of the delegate for this executive
Prime line executive 2 + phantom of the delegate for this executive, etc.
• Team DSS key at executive:

Prime line for each secretary
• Team DSS key at secretary

Prime line for each executive
• Voice calling groups.

Voice calling goes only to station numbers that are on NAME or DSS
keys. These keys must have the code for "voice calling" and "write
protection" (AMO ZIELN) and can only be administered via AMO.
Therefore you must use the AMO ZAND to set the code "voice calling only
in configured user groups" (VCOCUG=YES). 
This feature has nothing to do with "network-wide teams" and is also not
limited to certain types of station devices.
• You can also add station devices without the "executive" or "secretary"
code in the network-wide pickup groups for "network-wide teams". In this
way you can implement network-wide direct station selection destinations
that are not directly involved in the executive/secretary relationship.
• General tips concerning the difference between DSS and NAME keys
besides the LED, for the DSS key:
- FWD is ignored
- Do-not-disturb is ignored
- With a master HT, the master is called (not the next free station)
- Automatic camp-on when destination is busy
• Network-wide team also functions with the APS exchange if the current data
is regenerated and then again regenerated, and this is only in individual
network nodes.
• It is possible to have mixed operation, or network-wide teams or "internal

teams (key systems)" and internal CHESEs, in a system. However this should
be the exception!
• No station in a network-wide team is allowed to be in a local Chese.
• The secretary phantom lines must have the group call feature.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Feature Description
• The executive and secretary prime lines must have the FWDFAS and
FWDBAS classes of service for the RNGXFER function.
• The prime line of the secretary telephone is the private line as well.
• You must use a terminal with at least 12 function keys for the feature.
• The Remote FWD feature must be released network-wide.
• You can add team members to call pickup groups with teams or remove them
only by removing the entire team. Then you must reconfigure the team. The
same also applies to moving team members from one node to another.
You can, however, supplement or reduce "team call pickup groups" by station
numbers that do not have the executive or secretary code (AMO SDAT), for
example, because of DSS destination links. (Exception: primary secretary
line has secretary code but does not belong to the team.)
Network requirements
• Fictitious network-wide call pickup groups for signaling network-wide
direct station selection
For signaling the states (ringing, free, busy) of all network-wide direct station
selection destinations, configure a "fictitious network-wide call pickup group"
to optimize the flood of TSC messages. This signaling is handled over this
group. This call pickup group must be in each node that has a direct station
selection key configured with a network-wide destination or a network-wide
direct station selection destination. This group must be configured ahead of
time. In each node in this call pickup group, you must enter remote links to all
other nodes that you want to signal. Enter the REMAC to the correct node as
the "remote link". Always use the first remote group number as the
REMGRNO, although this entry is not evaluated.
• To avoid having to constantly expand this call pickup group, you should enter
all nodes that could be considered for the network-wide team in this group as
a user during the initial configuration.
• You must configure this call pickup group with a fictitious STN (card
subscriber). Use any call pickup group number or the next free one as the
"fictitious" group number.
• The parameter NWRES in the AMO AUN identifies the fictitious call pickup
during configuration.
• The COT parameters CFVA, TSCS, and BLOC must be included in the COT
for the circuits with the network-wide team.
Special features of the network-wide call pickup

• Separate delete branch for the fictitious call pickup group.
• You cannot add to this call pickup group with STN and you cannot delete the
fictitious device.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Relevant AMOs
• When you display "All" or areas, they are specially marked in the output.
New error messages come with each AMO editing attempt that is denied.
• You can configure only one fictitious call pickup group in a node.
• You are not allowed to simultaneously mark the fictitious group as a "team
group". You should check this on both sides.
• You must set all remote signaling parameters (REMSIGxx) to "yes".
• You can regenerate the fictitious call pickup group and you can do this in any
order.
• The solution also functions if the group number of the fictitious call pickup
group in a node should change for any reason.
79.2 Relevant AMOs
79.2.1 Overview

Language
AUN NWRES d ja = AUN für Teamsignlisierung
NWRES e yes = for networking reserved fictive pu group
TEAMNR d Teamnummer Verwaltungsziffer für DMS
TEAMNO e team number
SDAT EMERK d Teilnehmermerkmal =
TEAMSEKR: Teamsekretärfernsprecher
TEAMCHEF: Teamcheffernsprecher
DRZIEL: Direktrufziel netzweit
DIRANS: Direktansprechziel
AATTR e subscriber attribute =
TEAMSCR: secretary for netteam
TEAMEXEC: executiv for netteam
DSSDEST: netwide dss-destination
VCvoice call
ZAND NETZTEAM d ja = Anlage mit netzweiten Teams
Achtung lässt sich nur per Patch löschen!
NETTEAM e yes = Node with network-wide teams
CAUTION: Switch off only possible via patch.
ATONNULL d ja = Die Lautstärke des Aufmerksamkeitston
kann auf Null gesetzt werden
ATONZERO e yes = Alerttone volume can be set to zero.
DAINTGR d ja =Direktansprechen nur in
Interressensgruppen
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Relevant AMOs

Language
VCOCUG e yes = Voice calling only in configured usergroups
ZIELN d Neuer AMO zum Einrichten der
Direktrufnummern, Rufumleitungsziele,
Direktansprechen und Vertretertasten (netzweit)
e New AMO to activate DSS feature,
79.2.2 Detail
ZAND Set feature for "administration of network wide team" in each node:
NETTEAM=YES.
The user can set the volume of the alerting tone to zero: ATONZERO=YES.
COSSU Set COS for phantom lines of the secretary telephones and the parameters
for group call.
SDAT Define the station number for the "executive" or "secretary" as a team station
number (check against ZAND bit). Do this for both the prime lines of the
executive and secretary telephones and any executive phantom lines. (Not
for the phantom that is configured as the private executive line.)
TAPRO Assign keys for "executive".
For the prime line only, executive receives:
– One RNGXFER key.
– One DSS key for each possible secretary.
– One line key for each station number (prime line of the
phantom(s)).
For the prime line only, assign keys for "secretary":
– One RNGXFER key for each executive in the team.
– One REP key.
– One DSS key for each executive in the team.
– One line key for each station number (prime line of the
phantom).
(No PUS keys.)
(Possibly separate type of key status for executive and secretary.)
Keys for executive and secretary for logged-off stations
(phantoms)
– --> one line key each.
– --> remaining keys are irrelevant.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Relevant AMOs
ZIELN Enter destination, plan for all station numbers in "network-wide

format" (max. 22 digits).
Executive, only for PRI:
• DSS keys for each secretary telephone

Enter station number of the prime line for each secretary
telephone, 
including exit code for network-wide destination station numbers.
• RNGXFER key
Station number of the primary executive line (1st element).
Station number of the secretary phantom assigned to this
executive (2nd element).
ZIELN Secretary,only for prime lines:
• RNGXFER key for each executive in the team:
– Prime line of the assigned executive (1st element).
– Secretary phantom for this executive (2nd element).
– Identify RNGXFER key for network-wide team operation.
• REP key
Station number of the secretary prime line (1st element).
– Station number of the delegate prime line (2nd element).

And for each assigned executive
• PRI executive 1 (3rd element)

Delegate phantom for this executive (4th element).
• PRI executive 2 (5th element)

Delegate phantom for this executive (6th element),
etc.
• Identify REP for network-wide team operation.
• One DSS key for each executive in the team
• PRI station number of executive1.
• PRI station number of executive2, etc.
• Set write protection.
• Set code for network-wide for network-wide destinations.

SDAT Mark stations that are network-wide DSS destinations as such to avoid
unnecessary messages at all other call pickup group members when the
status changes.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Relevant AMOs
KCSU Convert terminal to key set and assign station numbers to the line keys
(configure PRI and phantoms).
Configure logged-off stations (phantoms) as key sets.
Executive receives a phantom line as private line.
Secretary receives one phantom line for each assigned executive.
Parameterize key set.
Device-specific for executive and secretary:
ORLNPF=PRIME (prime line is automatically seized when the phone is
lifted).
TMLNPF=RINGP (when there are incoming calls on several lines including
the prime line, the prime line is automatically given priority when the phone is
lifted).
SGLBMOD=YES (use one line key to select and seize).
KCSU BUSYRING=NORING (if someone is speaking on a line and more calls come
on other lines, they are signaled only visually, not acoustically).
APRIVAT=NO (not used for team configurations).
Prime line for executive and secretary:
RIOP= YES (acoustic ring for primary line).
AICS=YES (only for station devices with headsets, call is automatically
signaled at the headset, no button must be pushed).
Phantoms for each executive at the secretary

RIOP=YES (when it rings on the phantom and ring transfer is activated, it
should also be acoustically signaled. When ring transfer is deactivated,
executive calls on the phantom are not acoustically signaled at the secretary
- only visual signaling).
AICS=YES (see above).
AUN Form call pickup groups

One "fictitious network-wide call pickup group" per node, see Chapter 1, if
there are network-wide DSS destinations.
For each executive/secretary relationship of a call pickup group, possibly
network-wide.
1 executive, 1 secretary
PRI executive 1 + phantom secretary 1/executive 1
2 executives, 1 secretary
Call pickup group 1: PRI executive 1 + phantom secretary 1/executive 1
Call pickup group 2: PRI executive 2 + phantom secretary 1/executive 2
etc.
AUN Enter team number (also delete and regenerate)
For each executive, enter the team number for the key sets with the code
"executive" or "secretary" in the line memory for the PRI of the executive and
phantoms of the secretary. This is a 3-digit number that must be
unambiguous network-wide.
This team number is entered for the corresponding station numbers when the
call pickup group is formed. For network-wide call pickup, for all
corresponding station numbers of the network-wide group pickup in the
different nodes.
When such a call pickup group is deleted, the team number is also taken
away.
DMS administers the team number in its own database.
DSSU Switch on team devices,
ACTDA as a precaution, first use ACTDA to deactivate the primary executive line
FWD because it is not allowed to be activated.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Relevant AMOs
79.2.3 Flowchart for Chese 1/1 over 2 Systems
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Relevant AMOs
ZAND
Feature release
ALLDATA3 NETTEAM
ALLDATA NODECD
OPTISET ATONZERO
WABE
DAR NETW DESTN You must following this
O procedure in all systems.
The TSC signaling is built
OWNNODE
up network-wide via these
call pickup groups.
Then you can start to
configure the network-wide
teams and DSS keys.
DIMSU
USER PUGR
KEYSYS
NETWORK REMPUGR
SCSU
Virtual card subscribers
INS FLOAT
AUN
GRNO Network call pickup for virtual
stations
REMAC
REMGRNO
NWRES=YES
1 2
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Relevant AMOs
System with executive 1 System with secretary 1

1 2
SDAT COSSU
Feature TEAMEXEC AVCE GRPCAL
DSSDEST
SBCU One for each executive phantom

TAPRO INS SIGNOFF line
KY..... DSS
RNGXFER
SDAT
RCUTOFF
Feature TEAMSECR
LINE
DSSDEST
ZIELN
TAPRO
TYPE DSS
KY..... DSS
VC
RNGXFER
RNGXFER
RCUTOFF
LINE
AUN
GRNO ZIELN
REMAC TYPE DSS
REMGRNO VC KCSU
RNGXFER SEC KEYNO
REP * STNOSEC
ZAND RIOP
* Optional
ALLDATA2 INDNADIS
KCSU
PRIM PRIMKEY AUN
RIOP GRNO
ORLNPF REMAC
TMLNPF REMGRNO
SGLBMOD
BUSYRING
ZAND
APRIVAT
ALLDATA2 INDNADIS
AICS
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
Generation (Examples)
79.3 Generation (Examples)
79.3.1 Two Executives, One Secretary, Spread Over 3

Systems
System 2 SECR 1
You cannot assign a
7360 RU für C1 REP
7261 delegate because only
Before actually 7460 one secretary telephone
7262 RNGXFER is configured.
configuring the team, for C2
you must configure the 7360 RU für C1
virtual pickup (Pickup 1)
network-wide for the 7461 DSS to C2
network-wide signaling.
Pickup
7260 separate line (prime)
7261 RU für C1
7262 C2 phantom line
<--- Pickup Pickup 3 ---
System 3 EXECUTIVE1 System 4 EXECUTIVE2

7360 7460
7261
RNGXFER to SECR 1 RNGXFER to SECR 1
7262
7260 DSS to SECR 1 7260 DSS to SECR 1
Pickup Pickup
7360 RU für C1 7460 separate line (prime)
7361
private station number private station number
7465
phantom line phantom line
79.3.1.1 Configure Network-wide Call Pickup for TSC Signaling

in Nodes 89-200
• Activate feature.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
CHANGE-ZAND:TYPE=ALLDATA3,NETTEAM=YES;
• Configure virtual card subscribers and network call pickup (Pickup 1).
ADD-
SCSU:STNO=7290,DVCFIG=ANATE,DPLN=0,ITR=0,COS1=3,COS2=3,LCOSV1
=5,LCOSV2=1,LCOSD1=5,LCOSD2=1,INS=FLOAT;
ADD-
AUN:GRNO=1,STNO=7290,REMAC=808903,REMGRNO=1,DISTNO=YES,NOTRNG
=ON3,PUSECOND=YES,SIGNAL=ALL,REMSIGO=YES,REMSIGI=YES,REMSIGPK
=YES,NWRES=YES;
ADD-
AUN:GRNO=1,REMAC=808904,REMGRNO=1,REMSIGO=YES,REMSIGI=YES,REM
SIGPK=YES;

in Nodes 89-300
ADD-
ADD-
=YES,NWRES=YES; 
ADD-
SIGPK=YES;

in Nodes 89-400
ADD-
ADD-
=YES,NWRES=YES; 
ADD-
SIGPK=YES;
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
79.3.1.4 Configure Executive 1 in System 89-399
• Configure executive telephone with add-on device.
• You must keep the COS for parameters FWDFAS and FWDBAS for the
RNGXFER function.
ADD-
SBCSU:STNO=7360,OPT=OPTI,CONN=DIR,DVCFIG=OPTIIP,COS1=13,COS2=
13,LCOSV1=5,LCOSV2=1,LCOSD1=5,LCOSD2=1,DPLN=0,ITR=0,REP=1,STD
=4;
• Configure private line for executive with key default for key lines, for example,
25 (optional).
ADD-
=25,,INS=SIGNOFF;
• Mark executive 1 with team function.
CHANGE-SDAT:STNO=7360,TYPE=ATTRIBUT,AATTR=TEAMEXEC&DSSDEST;
• Key assignments for executive 1.
CHANGE-
TAPRO:STNO=7360,DIGTYP=OPTIA1,KY01=LINE,KY02=LINE,KY03=DSS,KY
04=RNGXFER,KY05=RNGXFER;
• Define key functions.
• Direct station selection to secretary.

ADD-ZIELN:STNO=7360,TYPE=DSS,KYNO=22,DESTNOD=7260;
• Configure voice calling to secretary.
ADD-ZIELN:STNO=7360,TYPE=VC,KYNO=22;
• Configure ring transfer destination to secretary.
ADD-
ZIELN:STNO=7360,TYPE=RNGXFER,KYNO=23,STNO1=7360,STNO2=7261;
• Configure executive key system with private line.
ADD-
KCSU:STNO=7360,TYPE=PRIM,PRIMKEY=20,RIOP=YES,ORLNPF=PRIME,TML
NPF=RING,SGLBMOD=YES,BUSYRING=NORING,APRIVAT=NO;
• Configure private line as key.
ADD-KCSU:STNO=7361,TYPE=PRIM,PRIMKEY=8;
• Private line (assign phantom as secondary).
ADD-KCSU:STNO=7360,TYPE=SEC,KYNO=21,STNOSEC=7361,RIOP=YES;
• Configure a new call pickup network-wide for executive 1.
• Call pickup 2 of the partner is in node 200, remote group 2.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
ADD-
AUN:GRNO=2,STNO=7360,REMAC=808902,REMGRNO=2,DISTNO=NO,NOTRNG=
ON3,PUSECOND=NO,SIGNAL=ALL,TEAMNO=1;
• Save data.
EXEC-UPDAT:BP,ALL;
79.3.1.5 Configure Executive 2 in System 89-400
• Configure executive telephone with add-on device.
RNGXFER function.
ADD-
=4;
• Configure private line for executive with key default for key lines, for example,
25 (optional).
ADD-
=25,INS=SIGNOFF;
• Mark executive 2 with team function.
CHANGE-SDAT:STNO=7460,TYPE=ATTRIBUT,AATTR=TEAMEXEC&DSSDEST;
• Key assignments for executive 2.
CHANGE-
04=RNGXFER,KY05=RCUTOFF;
• Direct station selection to secretary.

• Configure ring transfer destination to secretary.
ADD-
• Configure executive key system with private line.
ADD-
NPF=RING,SGLBMOD=YES,BUSYRING=NORING,APRIVAT=NO;
• Configure private line as key.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
• Private line (assign phantom as secondary).

• Configure a new call pickup network-wide for executive 2.

ADD-
• Save data.
EXEC-UPDAT:BP,ALL;
79.3.1.6 Configure Secretary in System 89-200
• Configure with secretary telephone with add-on device.
RNGXFER function.
ADD-
=4;
• Configure COS with group call.
ADD-COSSU:COPYCOS=12,NEWCOS=15,AVCE=GRPCAL;
• Configure phantom line for executive 1 at secretary (logged off).
ADD-
=25,IINS=SIGNOFF;
• Configure phantom line for executive 2 at secretary (logged off).
ADD-
=25,INS=SIGNOFF;
• Mark secretary with team function.
CHANGE-SDAT:STNO=7260,TYPE=ATTRIBUT,AATTR=TEAMSECR&DSSDEST;
• Mark executive 1 and executive 2 lines as team secretary.
CHANGE-SDAT:STNO=7261,TYPE=ATTRIBUT,AATTR=TEAMSECR;
CHANGE-SDAT:STNO=7262,TYPE=ATTRIBUT,AATTR=TEAMSECR;
• Key assignments for secretary.
CHANGE-
04=RNGXFER,
KY08=RCUTOFF,KY09=REP,KY10=LINE,KY11=DSS,KY12=RNGXFER;
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
• Direct station selection to executive 1.

• Direct station selection to executive 2.
• Configure intercept key to executive1 (STN01 = primary line executive 1,
STN02 = phantom line 1 secretary).
ADD-
• Configure intercept key to executive2 (STN01 = primary line executive 2,
STN02 = phantom line 2 secretary).
ADD-
• Configure key system, secretary with 2 executives.
ADD-
NPF=RING,SGLBMOD=YES,BUSYRING=NORING,APRIVAT=NO; 
ADD-KCSU:STNO=7261,TYPE=PRIM,PRIMKEY=8;
• Assign executive 1 and executive 2 phantom lines as secondary.
ADD-KCSU:STNO=7260,TYPE=SEC,KYNO=21,STNOSEC=7261,RIOP=YES;
• Connect phantom line1 secretary with primary line of executive 1.
• Pickup 2 of the partner is in node 300, remote group 2.

ADD-
• Connect phantom line 2 of secretary with primary line of executive 2.

ADD-
• Save data.
EXEC-UPDAT:BP,ALL;
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
79.3.2 Two Executives and Two Secretaries, Spread

Over 3 Systems
Node Node
SECR 1 SECR 2
300 7362 400 7462
7261
7390
RNGXFER REP 7462 7261
7490 RNGXFER REP 7362
7261 7461
for C1 for C1
7461 7490 7461 7391
7391 RNGXFER 7491
RNGXFER 7261
7461
for C2 7491 for C2 7390
7261 DSS to 41 C1 7261 DSS to 41 C1
7461 DSS to 51 C2 7461 DSS to 51 C2
Pickup Pickup
pickup 3 -> 7362 21 separate line (prime) 7462 31 separate line (prime)
7390 22 C1 phantom line 7490 32 C1 phantom line
7391 23 C2 phantom line 7491 33 C2 phantom line
<--- Pickup 1 Pickup 2 --->

Node EXECUTIVE1 Node EXECUTIVE2
200 400
7261 7461
RNGXFER to SECR 1 RNGXFER to SECR 2
7390 7491
7362 DSS to 21 SECR 1 7362 DSS to 21 SECR 1
7462 DSS to 31 SECR 2 7462 DSS to 31 SECR 2
Pikkup Pickup
7261 41 separate line (prime) 7461 51 separate line (prime)
7264
42 private station number 52 private station number
7465
phantom line phantom line
79.3.2.1 General Section in System 3 (Node 300)
• Display the closed numbering among the 3 systems.
DISPLAY-WABE:TYPE=GEN,DAR=NETW&OWNNODE;
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
• Configure virtual call pickup groups with card subscribers.

ADD-
• Check if enough memory is available.
DISPLAY-DIMSU:TYPE=ALL,PARAM=PUGR;
DISPLAY-DIMSU:TYPE=NETWORK,PARAM=REMPUGR;
• Configure the network pickup. Set NWRES=YES.
ADD-
AUN:GRNO=555,STNO=7395,REMGRNO=555,DISTNO=YES,NOTRNG=ON3,PUSE
COND=YES,REMSIGO=YES,REMSIGI=YES,REMSIGPK=YES,NWRES=YES; 
ADD-
AUN:GRNO=555,REMAC=808904,REMGRNO=555,REMSIGO=YES,REMSIGI=YES
,REMSIGPK=YES;
ADD-
ADD-
AUN:GRNO=555,STNO=7295,REMAC=808903,REMGRNO=555,DISTNO=YES,NO
TRNG=ON3,PUSECOND=YES,REMSIGI=YES,REMSIGPK=YES,NWRES=YES; 
ADD-
AUN:GRNO=555,REMAC=808904,REMGRNO=555,DISTNO=YES,NOTRNG=ON3,P
USECOND=YES,REMSIGO=YES,REMSIGI=YES,REMSIGPK=YES;
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm

ADD-
SCSU:STNO=7495,DVCFIG=ANATE,DPLN=0,ITR=0,COS1=40,COS2=40,LCOS
V1=16,LCOSV2=16,LCOSD1=32,LCOSD2=32,INS=FLOAT;
ADD-
AUN:GRNO=555,STNO=7495,REMAC=808902,REMGRNO=555,DISTNO=YES,NO
TRNG=ON3,PUSECOND=YES,REMSIGO=YES,REMSIGI=YES,REMSIGPK=YES,NW
RES=YES; 
ADD-
AUN:GRNO=555,REMAC=808903,REMGRNO=500,REMSIGO=YES,REMSIGI=YES
,REMSIGPK=YES;
79.3.2.4 Configure Executive 1 in Node 300
Identify the configured standard station 7261 Stn as the executive and set the
direct station selection (DSS) feature. This establishes that this station device
is a network-wide direct station selection destination. You do not have to do
this for internal direct station selection destinations.
CHANGE-SDAT:STNO=7261,TYPE=ATTRIBUT,AATTR=DSSDEST&TEAMEXEC;
• Add-on device for executive 1.
CHANGE-SBCSU:STNO=7261,OPT=OPTI,REP=1;
• Define key assignments for executive function.
CHANGE-
TAPRO:STNO=7261,DIGTYP=OPTIA1,KY01=DSS,KY02=RNGXFER,KY03=DSS,
KY06=RCUTOFF,KY07=LINE,KY08=LINE;
• Direct station selection for executive 1 to secretary 1 and secretary 2.
ADD-ZIELN:STNO=7261,TYPE=DSS,KYNO=20,DESTNOD=7362;
• Configure ring transfer destination to secretary 1.
ADD-
• Configure phantom line for private station number, executive 1.
ADD-
COSSU:NEWCOS=50,AVCE=FWDBAS&FWDECA&FWDEXT&FWDNWK&FWDFAS&FWDDI
R&MB&COSXCD&TA&CDRSTN&CDRC&GRPCAL&TNOTCR;
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
ADD-
50,LCOSV1=5,LCOSV2=5,LCOSD1=5,LCOSD2=5,DPLN=0,ITR=0,COSX=0,RE
P=1,STD=26,INS=SIGNOFF,ALARMNO=0,CBKBMAX=5,TEXTSEL=GERMAN,HMU
SIC=0,CALLOG=TRIES,SERVID=0;
• Configure executive 1 as key set.

DISPLAY-DIMSU:TYPE=CC,CCTLOPT=KEYSYS;
ADD-
NPF=RING,SGLBMOD=YES,BUSYRING=NORING;
• Configure private line for executive 1 (optional).
ADD-
NPF=RING,SGLBMOD=YES,BUSYRING=NORING;
• Configure call pickup group between Pri_executive + Pha_executive at
secretary 1 and secretary 2 (call pickup 1).
ADD-
AUN:GRNO=1,STNO=7261,REMAC=80893,REMGRNO=1,DISTNO=YES,NOTRNG=
ON3,PUSECOND=NO,SIGNAL=ALL;
ADD-
SIGPK=YES;
• Assign team number for DMS, unambiguous in the network.
CHANGE-AUN:TYPE=GR,GRNO=1,TEAMNO=1;
• To have only the name of the executive phantom line and not the station
number displayed when there is RNGXFER, you can change the ZAND as
follows:
CHANGE-ZAND:TYPE=ALLDATA2,INDNADIS=YES;
79.3.2.5 Configure Executive 2 in Node 400
Identify the configured standard station 7461 Stn as the executive and set the
direct station selection (DSS) feature. This establishes that this station device is
a network-wide direct station selection destination. You do not have to do this for
internal direct station selection destinations.
CHANGE-SDAT:STNO=7461,TYPE=ATTRIBUT,AATTR=DSSDEST&TEAMEXEC;
• Add-on device for executive.
• Define key assignments for executive function.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
CHANGE-
TAPRO:STNO=7461,DIGTYP=OPTIA1,KY01=DSS,KY02=RNGXFER,KY03=DSS,
KY06=RNGXFER,KY07=LINE,KY08=LINE;
• Direct station selection for executive 1 to secretary 1 and secretary 2.
• Ring transfer destination is secretary 2.
ADD-
• Configure COS with GRPCAL for phantom user.
ADD-
R&
MB&COSXCD&TA&CDRSTN&CDRC&GRPCAL&TNOTCR;
• Configure phantom line for private station number, executive 2 (optional).
ADD-
P=1,STD=26,INS=SIGNOFF,ALARMNO=0,CBKBMAX=5,TEXTSEL=GERMAN,HMU
SIC=0,CALLOG=TRIES,SERVID=0;
• Configure executive 2 as key set.

DISPLAY-DIMSU:TYPE=CC,CCTLOPT=KEYSYS;
ADD-
NPF=RING,SGLBMOD=YES,BUSYRING=NORING;
• Configure private line for executive 2.
ADD-
• Configure key assignments for conference corner telephone.
CHANGE-TAPRO:STNO=7465,DIGTYP=OPTIIP,KY04=LINE,KY10=LINE;
• Conference corner telephone is configured as key set (optional).
ADD-
PF=RING,SGLBMOD=YES,BUSYRING=NORING,AICS=YES;
• Executive prime line is configured as secondary line.
79.3.2.6 Configure Secretary 1 in Node 300
Station 7362 is already configured as a normal station.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
• Configure COS with GRPCAL for phantom user.

ADD-
R&MB&COSXCD&TA&CDRSTN&CDRC&GRPCAL&TNOTCR;
• Phantom line for executive 1 at secretary 1.
ADD-
50,LCOSV1=50,LCOSV2=1,LCOSD1=1,LCOSD2=1,DPLN=0,ITR=0,COSX=0,R
EP=1,STD=26,SECR=N,INS=SIGNOFF,ALARMNO=0,CBKBMAX=5,TEXTSEL=GE
RMAN,,HMUSIC=0,SERVID=0;
• Configure phantom line for executive 2 at secretary 1.
ADD-
P=1,STD=26,SECR=N,INS=SIGNOFF,ALARMNO=0,CBKBMAX=5,TEXTSEL=GER
MAN,HMUSIC=0,SERVID=0;
• Mark prime line and phantom line at secretary 1 as team secretary.
CHANGE-SDAT:STNO=7362,TYPE=ATTRIBUT,AATTR=DSSDEST&TEAMSECR;
• Configure add-on device for secretary 1.
• Define key assignments for secretary function.
CHANGE-
TAPRO:STNO=7362,DIGTYP=OPTIA1,KY01=DSS,KY02=RNGXFER,KY03=LINE
,
KY04=DSS,KY05=RNGXFER,KY06=LINE,KY07=RCUTOFF,KY08=LINE,KY09=R
EP;
• Configure direct station selection for secretary 1 to executive 1 and executive
2.
• Define ring transfer destinations for secretary 1 to executive 1 and executive
2.
ADD-
ZIELN:STNO=7362,TYPE=RNGXFER,KYNO=21,STNO1=7261,STNO2=23851;
ADD-
• Define delegate for secretary 1 is secretary 2.
ADD-
ZIELN:STNO=7362,TYPE=REP,STNOREP=7462,STNOEX1=7261,STNOEX1R=7
490,STNOEX2=7461,STNOEX2R=7491;
• Configure secretary 1 as key set with phantom line for executive 1 and
executive 2.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
ADD-
ADD-
ADD-
NPF=RING,SGLBMOD=YES,BUSYRING=NORING; 
• Connect prime line from executive 1 (node 200) with phantom line of
secretary 1 and secretary 2 via the network-wide call pickup 1.
ADD-
ADD-
AUN:GRNO=1,REMAC=808904,REMGRNO=1,DISTNO=NO,NOTRNG=ON3,PUSECO
ND=NO,SIGNAL=ALL;
• Connect prime line from executive 2 with phantom line of secretary 2 and
secretary 2 with help of the network-wide call pickup 2.
ADD-
=ON3,PUSECOND=NO,SIGNAL=ALL;
• Connect prime line of secretary 1 with prime line of secretary 2 via call pickup
3.
ADD-
CHANGE-AUN:TYPE=GR,GRNO=1,TEAMNO=1;
• Give secretary 1 a name.
ADD-PERSI:TYPE=STN,STNO=7362,NAME="SECR 1";
• Give phantom line a name that appears during ring transfer.
ADD-PERSI:TYPE=STN,STNO=7390,NAME="SECR 1*";
ADD-PERSI:TYPE=STN,STNO=7391,NAME="SECR 1*";
• You must configure executive phantom lines that are at the secretary as
secret users so that the caller does not see the station number of the phantom
line during ring transfer.
CHANGE-SBCSU:STNO=7390,SSTNO=Y;
CHANGE-SBCSU:STNO=7391,SSTNO=Y;
CHANGE-ZAND:TYPE=ALLDATA2,DISPTGNA=YES;
• Only the name of the executive phantom line is displayed during ring transfer.
The name is displayed independently of the station number display. This
parameter applies system wide for all station devices.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
79.3.2.7 Configure Secretary 2 in Node 400
Station 7462 is already configured as a normal station.
• Configure COS with GRPCAL for phantom station.

ADD-
R&MB&
COSXCD&TA&CDRSTN&CDRC&GRPCAL&TNOTCR;
ADD-
P=1,STD=26,SECR=N,IINS=SIGNOFF,ALARMNO=0,CBKBMAX=5,TEXTSEL=GE
RMAN,HMUSIC=0,SERVID=0;
ADD-
P=1,STD=26,SECR=N,INS=SIGNOFF,ALARMNO=0,CBKBMAX=5,TEXTSEL=GER
MAN,HMUSIC=0,SERVID=0;
• Mark prime line and phantom line at secretary 2 as team secretary.
CHANGE-SDAT:STNO=7462,TYPE=ATTRIBUT,AATTR=DSSDEST&TEAMSECR;
• Secretary 2 CD 7462 is voice calling destination
CHANGE-SDAT:STNO=7462,TYPE=ATTRIBUT,AATTR=VC;
• Configure add-on device for secretary 2
• Define key assignments for secretary function.
CHANGE-
TAPRO:STNO=7462,DIGTYP=OPTIA1,KY01=DSS,KY02=RNGXFER,KY03=LINE
,KY04=DSS,KY05=RNGXFER,KY06=LINE,KY07=RCUTOFF,KY08=LINE,KY09=
REP;
• Configure direct station selection destinations for secretary 2 to executive 1
and executive 2.
• Configure ring transfer destinations for secretary 1 to executive 1 and
executive 2.
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
ADD-
ZIELN:STNO=7462,TYPE=RNGXFER,KYNO=21,STNO1=7261,STNO2=7490;
ADD-
• Define delegate for secretary 2 is secretary 1.
ADD-
ZIELN:STNO=7462,TYPE=REP,STNOREP=7362,STNOEX1=7461,STNOEX1R=7
391,STNOEX2=7261,STNOEX2R=7390;
• Configure secretary 2 as key set with phantom line for executive 1 and
executive 2.
ADD-
ADD-
NPF=RING,SGLBMOD=YES,BUSYRING=NORING; 
ADD-
• Connect prime line of executive 1 (node 200) with phantom line of secretary
2 and secretary 1 (node 300) via the network-wide call pickup.
ADD-
ADD-
SIGPK=YES;
• Connect prime line of executive 2 (node 400) with phantom line of secretary
2 and secretary 1 (node 300) via the network-wide call pickup.
ADD-
AUN:GRNO=2,STNO=7461&7491,REMAC=808903,REMGRNO=2,DISTNO=NO,NO
TRNG=ON3,PUSECOND=NO,SIGNAL=ALL;
• Connect prime line of secretary 2 with prime line of secretary 1 via call pickup
3.
ADD-
CHANGE-AUN:TYPE=GR,GRNO=1,TEAMNO=1;
• Give secretary 2 a name.
ADD-PERSI:TYPE=STN,STNO=7462,NAME="SECR 2";
• Give phantom line a name that appears during ring transfer.
ADD-PERSI:TYPE=STN,STNO=7490,NAME="SECR 2*";
ADD-PERSI:TYPE=STN,STNO=7491,NAME="SECR 2*";
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
• Only the name of the executive phantom line is displayed during ring transfer.
The name is displayed independently of the station number display. This
parameter applies system wide for all station devices.
• Save data.
EXEC-UPDAT:BP,ALL;
A31003-H3170-S103-6-7620, 02/2019
chesenet_en.fm
A31003-H3170-S103-6-7620, 02/2019
berum_en.fm
Class of Service Switch-Over COSX
80 Class of Service Switch-Over COSX

Each terminal port is assigned two classes of service (COS): one COS
comprising basic classmarks (COS1), and one comprising alternative classmarks
(COS2). When a terminal is placed in service, the COS pointer always points to
COS1; these should be the higher-level classmarks. On switch-over to the
alternative classmarks the user receives a special dial tone when he picks up the
handset.
LCOSV (Least Cost Routing Voice) and LCOSD (Least Cost Routing Data) follow
this same logic with LCOSV1/LCOSV2 and LCOSD1/LCOSD2.
A COS contains all classmarks for all services. These are entered with the AMO
COSSU. The COS is assigned to the port and hence to all connected devices.
This includes service-specific classmarks for FAX and DTE. Attendant terminals
are assigned only one COS (AMO ACSU), therefore, no class of service switch-
over is provided. The same is true for trunk circuits.
Class of service switch-over can be activated:
• at the terminal
– by inserting the ID card in the card reader. Inserting the ID card, however,
will not change the position of the COS pointer, but result in the automatic
assertion of COS1. When the ID card is inserted in a foreign device, and
provided traffic (ITR) to the reader is allowed, COS1 of the user’s home
port will apply.
– with a dialling procedure, provided both COSs of the user include code
switch-over. The code number is assigned with the AMO PERSI. One port
may be allocated several COSXCDs. 
The class-of-service switch-over code (COSXCD) to COS2 can be
enabled for any user by setting the PERSI parameter COSXCOS2.
• from the attendant terminal
• from the service terminal with AMO BERUM
– separately for each port
– for a group of ports. This includes each port of a class-of-service-switch-

over group (COSX group). There are 16 such groups. They are allocated
with AMO SCSU / AMO SBCSU when the ports are set up. If the
parameter is not provided, the port invariably belongs to COSX group 0. 
The AMO BERUM can be used for a selective switch-over to COS1,
COS2 or to the currently inactive (alternative) COS.
• time-of-day-dependent; this always applies to entire COSX groups:

The switch-over times are specified for each COSX group and week day by
way of the AMO BERUZ. Each day of the week one time entry can be made
for switch-over to COS1 and one for switch-over to COS2. An additional code
A31003-H3170-S103-6-7620, 02/2019
berum_en.fm
Class of Service Switch-Over COSX
character indicates for each COSX group and day of the week whether or not
switch-over should take place. This way time switch-over can be deactivated
and reactivated temporarily without entering new time periods.
Key switch equipment is exempted from group switch-over. For equipment using
several switch-over variants (code switch-over, group switch-over from the
service terminal or from the attendant terminal, or time-dependent switch-over)
the most recent switch-over is applicable.
Exception:
If individual COS switch-over is to be allowed for COSX group members, the
parameter COSIND=Y must be declared in the ALLDATA2 branch of AMO
ZAND. This will ensure that an individual switch-over will not be accidentally
"reset" by a group or time-dependent switch-over. Individual COS switch-overs
will then have to be revoked individually in each case.
A31003-H3170-S103-6-7620, 02/2019
com_groups_en.fm
COM Group Call
Feature Overview
81 COM Group Call
81.1 Feature Overview

The feature Com Group Calling allows internal short code and special ring
cadences for users who are members of the same COM group.
Access Code in Wabe Communication

*52= Comgrp Group number 1
Line with Special ring

RIOP =yes
7440
7446
7445 Member 2
Member 1
Member 6
*5 23 7441
User dials
Member 3
Station number 7445 has 7443 7442

access to Com group 1 as Member 5
Member 4
configured by AMO SBCSU

A COM (community) Group Call allows Digital Feature Telephone (DFT) or
Keyset users within a work group or same department to dial each other by using
fewer digits than the full extension number, to establish a normal A to B
connection. Call origination is based on the device that initiated the call, not the
line used.
The COM Group Call feature will make it easy for a user to access a group (10 or
100 members) of stations in an abbreviated fashion. The user can, press a key
(e.g., DDS w/access code), or dial an access code,or press a programmed
key(AMO TAPRO ,COMGRP) followed by a member number, to reach another
station.
A31003-H3170-S103-6-7620, 02/2019
com_groups_en.fm
COM Group Call
User Interface
81.3 User Interface

The COM Group Call feature is involved with the initial establishment of a call. It
allows 2 or 3 digit dialing to reach a destination party. The destination will then
ring with special ringing which can be administered via AMO.
Additional user interface items:
• The user must answer the call via Hands-Free or by lifting the handset.
• Each station (device) (e.g., prime line, and phantom line) may be a member
of one or more Groups and can appear once in each Group.
• A station (Keyset or DFT) has “access to” only one COM Group, but does not
have to be a member of that COM Group.
• A COM Group station can be located in a remote node. This requires that
each node have a duplicate database of the COM Group members to allow
all members to call each other.
• NOTE: When the destination COM Group member resides in a different node
than the calling party, the call is processed as a standard A <-> B call.
• Small COM Groups consist of up to 10 members (allows for two digit dialing
(e.g., one digit access code followed by one digit member number[0-9])).
• Large COM Groups consist of up to 100 members (allows for three digit
dialing (e.g., one digit access code followed by a two digit member
number[00-99]).
• System can be configured for up to 1,024 COM Groups.
81.4 Service information

The COM Group Call feature is intended for the global marketplace.

How to add the COM Group feature into the system:
• Dimension the system for the number of COM Groups:

ADD-DIMSU:TYPE=USER,COMGR=100;
• How to add stations into the COM Group:
ADD-COMGR:STNO=7446,MBNO=1,GRNO=1,SIZE=S,INFO=TEST GROUP;
• How to change the special ringing at the destination device:
CHA-ZAND:TYPE=RNGTYPE,COMGROUP=SGLR2;
A31003-H3170-S103-6-7620, 02/2019
com_groups_en.fm
COM Group Call
Relevant AMOs
• How to configure the originating station to have access to the COM Group:
CHA-SBCSU:STNO=7445,COMGRP=1;
• Add the digits for dial access to the feature:
ADD-WABE:CD=*52,DAR=COMGRP;
• Add the feature key to a phone:
CHA-TAPRO:STNO=7445,KY05=COMGRP;
81.6 Relevant AMOs

DIMSU COMGR d anzahl der com gruppen
e Dimension the system for the number of COM
Groups
COMG TLNNU d teilnehmer nummer
R
STNO e station number
MNU d mitgliedsnummer eines teilnehmer in einer com
gruppe
MBNO e member number of the station in the com group
GRUNU d nummer der com gruppe
GRNO e number of the com group
GROESSE d groesse einer gruppe
SIZE e size of the com group
INFO d jede gruppe kann mit service informationen
ergaenzt werden
e a service information may be added to each
group
SBCSU COMGRP d com group auf die der teilnehmer zugreifen kann
e com group the device is allowed to access
TAPRO BROADCST rundspruch
BROADCST e speaker call - one way broadcast
WABE BROADCST d rundspruch
ZAND RUFTYP= d Rufsignal fuer Comgruppe
COMGRUP DOPPELRUF2, EINFACHRUF1,
EINFACHRUF2
RNGTYPE= e Used to supply special ring to the destination
COMGROUP party
A31003-H3170-S103-6-7620, 02/2019
com_groups_en.fm
COM Group Call
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
intercom_groups_en.fm
Overview
82 COM Group Speaker Call -Two-Way
82.1 Overview
This feature combines the existing voice call feature with the short code intercom
feature to enable a fast easy to access intercom function.
Communication
Access Code in Wabe
Group number 1
*17= Comspk
Station switches to
7440 handsfree mode
7446
7445 Member 2
Member 1 Microphone is turned on
Member 6 all
tercom c if available
d sets up in
ls *533 an
User Dia 7441
Member 3
Station number 7445 has 7443 7442

access to Com group 1 as Member 5
Member 4
configured by AMO SBCSU

The Digital Feature Telephone (DFT) or Keyset user is able to call and
automatically activate and speak through the speaker of another DFT or Keyset
in the same COM Group (a.k.a., an Intercom call). To make an Intercom call, the
user depresses the Intercom key or dials an access code, and then dials the COM
Group member number of the destination phone. The destination’s speaker and
microphone, if so equipped, are automatically activated.
82.3 User Interface

• Certain rules must be met when establishing a COM Group Speaker Call:
A31003-H3170-S103-6-7620, 02/2019
a) The station user is not busy, not off-hook, not in hands-free operation, is
not in program mode.
b) The telephone is not marked for voice call protection.
c) c) The station is not restricted from terminating to that destination (e.g.

ITR Internal Traffic Restriction).
• The destination cannot be an analog telephone or attendant.
• If the destination telephone does not have a microphone, the handset must
be lifted to establish the two-way conversation.
• The destination extension must appear in only one node. A destination

extension can be a destination in a remote node. If so, the attempted call shall
be converted to a standard two party call (A-B call).
• See COM Group Call for further information.

How to add the COM Group feature into the system:
• Dimension the system for the number of COM Groups:

ADD-DIMSU:TYPE=USER,COMGR=100;
• How to add stations into the COM Group:
ADD-COMGR:STNO=7441,MBNO=3,GRNO=1,SIZE=S,INFO=TEST GROUP;
• How to configure the originating station to have access to the COM
Group:
CHA-SBCSU:STNO=7445,COMGRP=1;
ADD-WABE:CD=*53,DAR=COMSPK;
CHA-TAPRO:STNO=7445,KY05=COMSPK;
• How to configure the originating station to have access to the feature:
CHA-SDAT:STNO=7445,TYPE=ATTRIBUT,AATTR=COMSPK;
• Change the length of time between periodic alert tone (warning beeps at
the destination) during the speaker call:
CHA-DTIM1:TYPE=DIGITE, VCHAPAU=20;
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
82.5 Relevant AMOs

DIMSU COMGR d anzahl der com gruppen
e Dimension the system for the number of COM
Groups
COMG TLNNU d teilnehmer nummer
R
STNO e station number
MNU d mitgliedsnummer eines teilnehmer in einer com
gruppe
MBNO e member number of the station in the com group
GRUNU d nummer der com gruppe
GRNO e number of the com group
GROESSE d groesse einer gruppe
SIZE e size of the com group
INFO d jede gruppe kann mit service informationen
ergaenzt werden
e a service information may be added to each
group
SBCSU COMGRP d com group auf die der teilnehmer zugreifen kann
e com group the device is allowed to access
TAPRO COMSPK gruppenteilnehmer ansprechen
e com group speaker call - two way
WABE COMSPK d gruppenteilnehmer ansprechen
e com group speaker call - two way
DTIM1 DAPAUSE d pausenlaenge fuer aufmerksamkeitston bei
direktansprechen
VCHAPAU e pause length for alerting tone during voice calling
SDAT COMSPK d direktansprechen/direktantworten
COMSPK e com group speaker call - two
way
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
hunt_en.fm
Hunt Group
Feature Description
83 Hunt Group

A hunt group incorporates several terminals which need to be reached under a
common number. This number may be a code or the number of the first station of
the hunt group. This first station is referred to as the master station.
The following seizure types are possible:
• cyclic
The first available member rings. The search starts where the previous
search ended.
• linear
The first available member rings. The search starts with the first member.
• with parallel ringing

Voice calls ring at all available members of the hunt group.

Hunt groups can be formed for all service types, the hunt group code or master
station number being service-neutral. The services are selected using a separate
code number.
The call with the highest priority in the queue is assigned to the first group
member who becomes available. The priority order within the queue is
emergency call, CO call, tie call, internal call.
The previously queued call is presented to the next member who becomes
available if it is still in ringing state, for example there is only one call ringing the
group and not one call ringing member A and another call ringing member B.
A terminal can belong to several hunt groups. However, it cannot be master of

more than one and cannot appear more than once in one and the same hunt
group. For a voice hunt group, an overflow to a call queue can be established or
a mailbox be added to the voice mail server in case all of a hunt group’s stations
are busy.
A functional terminal (ISDN terminal) requires the COS parameter MULTRA to

ensure that all features work properly. However, when a functional terminal is
configured in a hunt group, the COS parameter MULTRA may not be set.
Otherwise the hunt group will not work properly and a CP Advisory message with
A31003-H3170-S103-6-7620, 02/2019
hunt_en.fm
Hunt Group
Feature Interactions for Hunt Group with Parallel Ringing
UA:AD0:49DE (CC:15295 / EC:2015) will be sent.

Solution: Delete the MULTRA parameter for the affected terminal, then delete the
hunt group, and set it up again.
A hunt group member station can be reached separately under its number or
more or less randomly under the huntigroup code. The master station can only be
reached as a hunt group member. It must always be the first station of a hunt
group.
Attendant terminals cannot be integrated in a hunt group. They have to be

accessed via the ATND group by dialing the ATNDDID or ATND group codes.
All group members can LOG ON to and LOG OFF from the group. An option can
be configured to allow the last active member of the group to LOG OFF. The
LOGON/LOGOFF operation is effective for all groups of which the phone is a
member. The operation can be invoked by means of an access code or key or via
the service menu.
Names can be assigned to all groups. The group name is presented to the calling
party's display while the call is in the ringing state. An option can be configured to
show the group name or the name of the group member who accepted the call in
the connected state.
By specifying the CPS in AMO SA, availability of the hunt group can be restricted,
for example, not available for DID or consultation hold. The DPLN group must be
specified if the hunt group code has been added in the DPLN with a DPLN group
branch.
Basically, a hunt group can be reached under several code numbers, for
example, *80, and by replacing *, 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. Changes made to such hunt groups apply to
all code numbers.
The hunt group type "parallel" is only supported for voice (STYPE=PRL is
rejected for SVC=DTE/FAX).
A hunt group with parallel ringing can have up to 20 members.
83.3 Feature Interactions for Hunt Group with Parallel Ringing

• Call Forwarding
All group members can activate CFU (Call Forwarding Unconditional).
Incoming group calls routed to the group member follow the CFU. If the CFU
destination is recognized as being a server, for example OpenScape
Xpressions, then CFU is not followed and the member will not be rung for the
group call.
A31003-H3170-S103-6-7620, 02/2019
hunt_en.fm
Hunt Group
Feature Interactions for Hunt Group with Parallel Ringing
An option can be configured to consider any member with CFU active as

being available, for example if the group option "busy if at least one member
is busy" is chosen, then the group is not considered busy.
The party forwarded to the device cannot LOG ON to or LOG OFF from the
group on behalf of the forwarding member.
The CFU settings of the master of a master hunt group control the CFU for
the entire group, for example if the master has activated CFU, then all
incoming group calls are routed to the CFU destination of the master. This
also applies in case the master has activated CFU to a server, for example
OpenScape Xpressions. This does not apply for a non master hunt group.
CFNR (Call Forwarding on no Reply) and CFB (Call Forwarding Busy)
settings for all group members are ignored for incoming group calls.
Regular Call Forwarding processing applies for non group calls, for example
if the extension number of the group member has been dialed by the call
originator.
Overview: FOLFWBSY and BUSYCOND if CQMAX=0:
FOLFWBSY BUSYCOND CFU Caller gets Ringing

Destination Station
NO ONE free free HGM and CFU-
DEST
NO ONE busy free HGM
NO ALL free free HGM and CFU-
DEST
NO ALL busy free HGM
YES ONE free free HGM and CFU-
DEST
YES ONE busy busy
YES ALL free free HGM and CFU-
DEST
YES ALL busy free HGM
Table 56 Call forwarding and hunt group with parallel ringing

• Do not Disturb
All group members can activate do not disturb.
Regular do not disturb processing applies for incoming group calls, for
example calls are not routed to members with do not disturb active, etc.
• Outgoing Calls
All group members can initiate outgoing calls while being rung for an
incoming group call via either keypad dialing or use of a feature key (name
key etc.).
A31003-H3170-S103-6-7620, 02/2019
hunt_en.fm
Hunt Group
If the last ringing group member places an outgoing call, then the incoming
group call is queued.
• Call Waiting
Busy group members with call waiting active are alerted to an incoming group
call by an audible and visible (if applicable) indication.
Call waiting is not invoked if the group member decided to initiate an
outbound call while the incoming call was ringing.
• Call Log
Only answered calls are logged for the member who answered the call. There
is no log for missed calls.
• Pickup Group
Only private calls to the hunt group members are signalled on all pickup group
members. Calls to the master of a hunt group with parallel ringing are not
signalled on other pickup group members
• Applications
All members offer an incoming call to applications that have registered for the
offered event. The call forwarding rules apply if the application deflects the
call.
• Intercept to attendant
If a DID call to a parallel group is intercepted, only the attendant station will
ring regardless if the parallel intercept is set on the system.

• Proceed as follows to enable the feature:
CHA-FEASU:TYPE=A,CM=HTVCE;
HTVCE = voice service

HTFAX = fax service
HTDTE = DTE service
• Assign a hunt group DAR in the DPLN:

ADD-WABE:CD=key-num,DAR=HUNT;
• Assign DAR for deactivation of hunt group member (voice service):
ADD-WABE:CD=key-num,DAR=DHTVCE;
• Assign DAR for reactivation of hunt group member (voice service):
ADD-WABE:CD=key-num,DAR=AHTVCE;
• Assign a hunt group with linear device search (voice service):
A31003-H3170-S103-6-7620, 02/2019
hunt_en.fm
Hunt Group
ADD-SA:TYPE=VCE,CD=number,STYPE=LIN,CQMAX=number;
• Assign a hunt group with cyclic device search:
ADD-SA:TYPE=VCE,CD=number,STYPE=CYC,CQMAX=number;
• Assign a hunt group with parallel ringing (voice service):
ADD-SA:TYPE=VCE,CD=number,STYPE=PRL,CQMAX=number;
• Create a master hunt group with the STNO 2103, service = voice, stations
2100-2101, STYPE=LIN with call queue capacity of 20 stations.
ADD-
SA:TYPE=VCE,CD=2103,DPLN=0,STNO=2100&2101,STYPE=LIN,CQMAX=20;
IMPORTANT: A maximum of 10 users can be added with one command. If

a larger hunt group is required, the command ADD-SA:TYPE=STN; can be
used to expand the hunt group by an additional 10 users: This applies to all
services. 
In addition, the parameter POS can be used to specify the position in the hunt
group at which the station is to be included.
• Duplicate the hunt group having STNO *21 at *3.

ADD-SA:TYPE=DUPL,CDOLD=*21,CDNEW=*3;
• To ensure that every station in a hunt group can receive a new call as soon
as it becomes available, use the following command to create a pool:
ADD-DIMSU:HGMEMB=<minimum number of local hunt group
stations>;
• Call forwarding in a hunt group
– LVAFTEXT=N, EXECCFW - no effect

If a hunt group is to be set up with external (non-local) stations, set the
parameter LVAFTEXT=NO. Only then can all stations in the hunt group
be reached (even when external stations have been set up in the hunt
group). The hunt group will not be exited. If call forwarding has been set
up by subscribers, it will not be carried out.
ADD-SA:TYPE=VCE,CD=number,STYPE=<CYC or LIN>,LVAFTEXT=N;
– LVAFTEXT=Y, EXECCFW=Y
If external stations have been set up in the hunt group, they can be
reached, but that results in them leaving the hunt group. Call forwarding
set up by subscribers in the hunt group will be carried out, but will also
result in them leaving the hunt group.
ADD-SA:TYPE=VCE,CD=number,STYPE=<CYC or
LIN>,LVAFTEXT=Y,EXECCFW=Y;
– LVAFTEXT=Y, EXECCFW=N
A31003-H3170-S103-6-7620, 02/2019
hunt_en.fm
Hunt Group
Relevant AMOs
External stations may not be configured for the hunt group. With this
setting, external stations cannot be reached. The hunt group will not be
exited. If call forwarding has been set up by subscribers in the hunt group,
it will not be carried out.
ADD-SA:TYPE=VCE,CD=number,STYPE=<CYC or
LIN>,LVAFTEXT=N,EXECCFW=Y;
IMPORTANT: The parameters EXECCFW and LVAFTEXT are only relevant

for members of a hunt group. 
For the master station of a hunt group with call forwarding configured,
signaling always occurs regardless of the settings of the two parameters.
EXECCFW and LVAFTEXT do not have any effect for hunt groups with
parallel ringing.
• Allow last hunt group member to leave the group

This feature can be activated in two steps.
1. The feature can be activated globally (in the whole system) with AMO
ZAND, parameter DISCLHNT.
CHANGE-ZAND:TYPE=ALLDATA2,DISCLHNT=YES;
2. The feature can be activated for one hunt group only with AMO SA,
parameter LSTMBOFF.
CHANGE-
SA:TYPE=TYPE,CD=<hunting_group_access_code>,SVC=<device
service>,LSTMBOFF=YES;
If a member is configured in more than one hunt group, the member is
allowed to log off last only if the parameter LSTMBOFF is set in all affected
hunt groups.
83.5 Relevant AMOs

Language
DIMSU SATLN d Anzahl der Endgeräte, die Mitglieder eines
Sammelanschlusses (auch netzweiter
Sammelanschlüsse) sind
HGMEMB e Number of stations that are members of a
hunt group (also network-wide hunt groups)
FEASU LM d SAS = Dienst Sprache
SAF = Dienst FAX
SAD = Dienst DEE
A31003-H3170-S103-6-7620, 02/2019
hunt_en.fm
Hunt Group
Relevant AMOs

Language
CM e HTVCE = voice service
HTFAX = fax service
HTDTE = DTE service
SA TYP d Sammelanschlussoption
TYPE e Hunt group option
ART d Suchart
STYPE e Search type
ANOKAP d Anrufsortierungs-/Warteschlangenkapazität
Wenn der Parameter VARAO auf JA
gesetzt ist, wird die Anzahl der
Anrufwarteschlangen automatisch
bestimmt und der Parameter ANOKAP
ignoriert.
CQMAX e Call ordering/queuing capacity
If the parameter VARCQ is set to Y, the
number of call queues will be determined
automatically and the parameter CQMAX
will be ignored.
VERLNEXT d Sammelanschluss nach Netzwerkmitglied
verlassen
LVAFTEXT e Leave hunt group after networking member
AUSFAUL d Anrufumleitung von Sammelanschlüssen
ausführen
EXECCFW e Execute call forwarding from hunt groups
ABMLDLZT d JA: Das letzte Mitglied einer
Sammelanschlussgruppe kann sich beim
Sammelanschluss abmelden (gilt für einen
einzelnen Sammelanschluss).
LSTMBOFF e YES: Last member of a hunt group is
allowed to leave the hunt group (only valid
for one hunt group).
BUSYCOND d Besetzt Bedingung des Parallel Ringing
Sammelanschlusses. Werden bei
ART=ZYK/LIN ignoriert.
BUSYCOND e Busy condition of the parallel ringing hunt
group. Will be ignored for STYPE=CYC/LIN.
FOLFWBSY d Umgeleiteten Ruf folgen um besetz Status
zu bestimmen. Werden bei STYPE=CYC/
LIN ignoriert.
FOLFWBSY e Follow forwarded to determine busy status.
Will be ignored for STYPE=CYC/LIN.
ANZART d Art der Nebenstellennummernanzeige an
einer Nebenstelle. Wird bei ART=ZYK/LIN
ignoriert.
A31003-H3170-S103-6-7620, 02/2019
hunt_en.fm
Hunt Group
Relevant AMOs

Language
DISPTYPE e Type of station number display at a station.
Will be ignored for STYPE=CYC/LIN.
WABE KZP d SAMMEL = Sammelanschluss
DHTVCE = Zuweisung des Endgeräts zum
Sammelanschluss Sprache aufheben
AHTVCE = Endgerät zum
Sammelanschluss Sprache hinzufügen
DAR e HUNT = Hunt group
DHTVCE = Disassociate station from hunt
group voice
AHTVCE = Add station to hunt group voice
ZAND AUSLSA d JA: Das letzte Mitglied einer
Sammelanschlussgruppe kann sich beim
Sammelanschluss abmelden (gilt für das
gesamte System).
DISCLHNT e YES: Last member of a hunt group is
allowed to leave the hunt group (valid for the
whole system).
A31003-H3170-S103-6-7620, 02/2019
hgnw_en.fm
Hunt Group Network-wide
84 Hunt Group Network-wide

Hunting group destinations which can be reached internally, externally, or
network wide are treated as call forwarding destinations, provided the hunt group
parameter "Call forwarding for hunting group stations" (AMO SA) has been
activated.
Call forwarding can be performed several times in sequence, for example,

renewed call forwarding, call forwarding - no answer after a timeout or call
forwarding busy, etc., under the same conditions as those for "normal" station
multiple call forwarding.
For even load distribution within a network, you can configure a hunting group
with network-wide stations. 
To achieve even load distribution in a cyclical hunting group allow every second
hunting group station to activate call forwarding to another hunting group within
the network.
LVAFTEXT Parameter
The parameter LVAFTEXT (leave hunt group after netw. member) makes it
possible to maintain control in the hunting group when calls are distributed to
external numbers (in other words, whether the hunting group should be left or
not).
• LVAFTEXT=Y
When a call to a hunting group arrives at an external number or forwarded
number, the call leaves the hunting group. The hunting group then no longer
controls this call.
• LVAFTEXT=N
When a call is distributed within a hunting group, the system also checks for
external numbers. The network-wide station is handled in the same way as
an internal station. The hunting group maintains control in this case. Call
forwarding (any type) is not performed when LVAFTEXT=N.
The following hunting group sequence is possible for example: internal station ->
network-wide station -> internal station.
External subscribers can also be configured as hunting group stations. If the

station does not answer, the call is redirected within the hunting group.
If no pool has been configured in AMO DIMSU (see below) for systems including
hunting group stations, there may be delays in recognizing when hunting group
stations are free.
This is especially true for external stations.
A31003-H3170-S103-6-7620, 02/2019
hgnw_en.fm
Expansion of the Call Queue Overflow Function
84.1 Expansion of the Call Queue Overflow Function

AMO SA permit input of a station number with up to 22 digits as an overflow
destination. This means that all internal, external, and network-wide stations can
be configured as overflow destinations. An overflow to a PhoneMail via S2
connection functions like an overflow to a network-wide VMS. The mailbox
number is limited to 7 digits.
• Possible overflow destinations
– none
– station number
– network-wide VMS
– PhoneMail
• Station number for overflow destinations
– station number (1 - 22 digits for station numbers)
– station number (1 - 7 digits for VMS/PhoneMail destinations)
If a network-wide VMS or PhoneMail number is entered, the entry in the VMX

table (for network-wide VMS) or the SAN table (for PhoneMail) is the server
station number. Mailbox station number output is similar to that of the internal
VMS.
Any calls to a hunting group during call queue overflow are treated as call
forwarding to a hunting group station: after call forwarding by overflow a ‘ring no
answer or when busy‘ cannot be performed. Several call forwardings can only be
performed if multiple call forwarding has been activated in the destination node
(currently up to 10 levels).
The only exception is when another hunting group is specified as the overflow
destination. In this case, FNA (Forward If No Answer) is performed within the
hunting group. The system will consider this hunting group‘s overflow destination,
which can be an internal or network-wide station number, provided multiple call
forwarding was activated in this node. The overflow destination can again be a
hunting group. As call processing cannot check the number of network-wide
hunting group links, the provider is responsible for their limitation. If the second
hunting group’s overflow destination is a VMS or PhoneMail number, call
forwarding is always performed, even if multiple call forwarding has not been
activated. This occurs regardless of whether the VMS or PhoneMail number is a
network-wide or internal number.
To distribute the traffic load evenly in the network, configure another hunting
group in a second PABX as the overflow destination. This distributes the busy
hour loads caused by call queue overflow.
A31003-H3170-S103-6-7620, 02/2019
hgnw_en.fm
Expansion of the Call Queue Overflow Function
A hunting group station can configure a FWD destination. The usual tests to
check the validity of the FWD destination are performed. No further checks for the
validity of the FWD destinations are required.
The overflow destination is configured using an AMO (=FWD destination). The

AMO first checks whether the specified station number leads to a valid DAR. In
other words, this eliminates incomplete (INCO) or impossible (NOPO) station
numbers (only limited use for network-wide or external station numbers).
If a call to a hunting group is forwarded to an external or network destination, then

the call will not be forwarded within the originally called hunting group if the
overflow destination does not answer or is busy. Optical camp-on by the call
queue and the overflow destination is not used, as stations with active call
forwarding to network or external station numbers are treated as free.
Call forwarding destinations can only be checked if the destination is an internal

station number. Forwarding to other station numbers cannot be checked.
After call forwarding or if the station is located in another PABX, callers may only
hear the busy tone if the destination is busy or the required resources (lines,
paths) are currently unavailable.
Stations in different PABXs can be configured as hunting group members.
All station numbers which can be dialed internally, externally, and network wide
and all internal and network-wide VMS and PhoneMail numbers can now be
configured as overflow destinations.
A31003-H3170-S103-6-7620, 02/2019
hgnw_en.fm
Generation
Caller Hunting group
Overflow
internal network-wide external (CO)
VMS VMS
Station Station
Hunting group Hunting group
etc. etc.
Figure 103 HG Overflow Destinations
84.2 Generation
The FWD COUNTER in AMO ZAND is used to configure the maximum number
of call forwardings.
• Activate the feature

CHA-FEASU:TYPE=A,CM=HTNW;
• Configure a hunting group with call forwarding
ADD-SA:TYPE=VCE,CD=<hunting group station
number>,STNO=<station numbers of hunting group
station>,STYPE=<(LIN or CYC)>,LVAFTEXT=Y,EXECCFW=Y;
A31003-H3170-S103-6-7620, 02/2019
hgnw_en.fm
Generation
• Configure a hunting group in which call diversion is not allowed, but in which
network-wide stations in the hunting group can be reached
stations>,STYPE=<(LIN or CYC)>,EXECCFW=Y;LVAFTEXT=N,
• Configure the maximum number of call forwardings
CHA-ZAND:TYPE=ALLDATA2,FWDMAX=<number of call forwardings>;
• Configure call forwarding
ADD-ZIEL:TYPE=FWD,SRCNO=<forwarding
party>,SI=VOICE,DESTNOF=forwarding destination;
• Activate call forwarding
ADD-ACTDA:TYPE=STN,STNO=<forwarding
party>,FEATCD=FWD,SIFWD=VOICE;
The number of a hunting group‘s overflow destinations has been increased. Now
an internal VMS (in the local PABX), a network-wide VMS, a PhoneMail server,
and a station number (optionally in the local PABX, in a network PABX, or in the
CO) is allowed. Overflow to the servers is performed whether or not the FWD
COUNTER in AMO ZAND is reached. The FWD COUNTER limits the overflow to
the station number.
• Configure a hunting group with overflow

stations>,STYPE=<(LIN or CYC)>,OVFLDEST=<(PHONMAIL,VMSNW,
DESTEXT,NONE)>,NUMBER=<station number>;
The overflow destination can be reached after a call has spent a cycle in the
hunting group. The OVFLCYCL parameter is set to Y for this.
• Configure a hunting group with overflow and overflow after one cycle
stations>,STYPE=<(LIN or
CYC)>,OVFLCYCL=Y,OVFLDEST=<(PHONMAIL,VMSNW,VMSINT,DESTEXT,NON
E)>,NUMBER=<station number>;
Configure a pool for detecting free or busy stations
ADD-DIMSU:TYPE=USER,HGMEMB=<number of configured hunting group
stations>;
If the LVAFTEXT parameter in the AMO SA is set to N, you must also configure
a pool in all systems that feature a network-wide hunting group station.
A31003-H3170-S103-6-7620, 02/2019
hgnw_en.fm
Example
84.3 Example
Node 3
Node 1
HG C11
201 201
HG 222
200
201
202 Node 2
203
HG C11
202 202
200 203
Figure 104 Hunting group, network wide: Example
Generating node 1:
The actual hunting group with internal and external stations is configured in this
node.
ADD-
SA:TYPE=VCE,CD=222,STNO=200&201&202&203,STYPE=LIN,CQMAX=0,LVAFTE
XT=N;
CHANGE-TAPRO:STNO=200,KY12=HT;
Generating nodes 2 and 3:

An additional fictitious hunting group is configured in nodes 2 and 3 (in this case,
it has the number "C11", which cannot be dialed). It has a floating (FLOAT) station
as the head station for the following reasons:
• in order for the HG button to function. The station can leave the hunting group
using the HG button.
• With this configuration, the external stations (201, 202) are merely members
and not masters of the hunting group. As a result, there are no restrictions on
these stations when they are called directly (for example, callback).
Set the DISCLHNT parameter to YES so that the external stations can leave the
hunting group.
Generating node 2:
ADD-WABE:CD=C11,DAR=HUNT,CHECK=N;
ADD-SA:TYPE=VCE,CD=C11,STNO=201,STYPE=CYC,CQMAX=0;
A31003-H3170-S103-6-7620, 02/2019
hgnw_en.fm
Example
Generating node 3:
ADD-WABE:CD=C11,DAR=HUNT,CHECK=N;
ADD-SA:TYPE=VCE,CD=C11,STNO=202,STYPE=CYC,CQMAX=0;
A31003-H3170-S103-6-7620, 02/2019
hgnw_en.fm
Example
A31003-H3170-S103-6-7620, 02/2019
preview_usage_en.fm
Keyset Preview Key
Overview
85 Keyset Preview Key
85.1 Overview
The Preview feature allows the users of multi-line keysets to view caller i.d.
information about certain lines.
7446 KN 89 400
PREVIEW
Pressing the Preview Key and any line allows the caller I.D of that line to be displayed

The Preview key is typically used on a keyset with multiple lines. By depressing
the Preview key, the keyset user can see display information associated with
certain lines on the keyset, without requiring the user to answer the call or to take
the line off of hold.This "previewing" can be done while the user is active on a call
or while the keyset is idle, as follows:
• A keyset user can preview ringing (audible) lines, for those lines that are
configured to ring.
• A keyset user can preview lines on Manual Hold.
• A keyset user can preview lines that he/she has placed on Exclusive Hold.
• A keyset user can preview the currently active keyset line, (s)he is using, to
show the identity of the other user and, when a call is camped-on, to show the
identity of the camped-on caller.
• A keyset user can preview ringing (audible) lines which are recalling, i.e., from
hold, park, system hold, and transfer.
An attempt to preview any lines not meeting the above criteria will give a timed
"CURRENTLY NOT AVAILABLE" display.
A31003-H3170-S103-6-7620, 02/2019
preview_usage_en.fm
Keyset Preview Key
User Interface
85.3 User Interface

Activation Sequences
1. Previewing a ringing line
a) If IDLE or TALK or CONFERENCE -
1. Press PREVIEW Key and the PREVIEW LED comes on
2. Press a ringing line and calling information is displayed for a

programmed amount of time (Preview-Display timer = 8 seconds
default).
3. To preview another line, press the LINE key of the line to be

previewed.
4. To answer a line which is being previewed (preview display

information is active), press the line key again or go off-hook if
previewing from idle state.
2. Previewing a line on hold
a) If IDLE or TALK or CONFERENCE -
2. Press a manually held line and held party information is displayed for
a programmed amount of time (Preview-Display timer = 8 seconds
default).

previewed.
4. To answer a line which is being previewed (preview display

information is active), press the line key again or go off-hook if
previewing from idle state.
3. Previewing a line you are active on
a) While in TALK
2. Press the line you are active on and connected party information is
displayed for a programmed amount of time (Preview-Display timer =
8 seconds default).

previewed.
4. To answer a different line which is being previewed (preview display

information is active), press the line key again.
A31003-H3170-S103-6-7620, 02/2019
preview_usage_en.fm
Keyset Preview Key
User Interface
4. Previewing a non-ringing (alerting) or non-manual held line other than the line
you are active on.
a) While in TALK or CONFERENCE
2. Press the non-ringing/alerting line and Preview of line, Currently not

possible is displayed for a programmed amount of time (Preview-
Display timer = 8 seconds default).

previewed.
5. Previewing an idle line.
a) While in TALK or CONFERENCE
2. Press an idle line and PRESELECTED is displayed for a programmed

amount of time (Preview-Display timer = 8 seconds default).
3. To select the idle line, press the same LINE key while preview display
is active. Note: If the user is active on another line, disconnect and
automatic hold rules for line keys shall be honored.

previewed.
Deactivation Sequences
a) A keyset user must deactivate preview mode prior to answering a call
(line).
b) Time-out: There is no time-out for preview "mode".
c) Pressing any key other than a line key after pressing the Preview key.
d) User going off hook while the keyset is idle (with or without any line
appearances on hold) will deactivate preview mode and, if preview
display information is present for a line, will select that line.
e) User going on hook, e.g., to terminate existing call or to go to hands-free

operation.
Feature Interactions
a) Upon deactivation, the preview function ceases and the Preview key LED
is deactivated.
b) Upon deactivation or after time-out of the display of the previewed

information, the following shall be displayed, dependent upon priority:
A31003-H3170-S103-6-7620, 02/2019
preview_usage_en.fm
Keyset Preview Key
Service Information
a) Elapsed Time display will be displayed.
b) Dialog options (e.g., feature prompts) for Optiset E telephones will be

displayed.
c) Pending call information will be displayed.
d) Displays during idle state, e.g., Optiset E time and date.
c) A user selection of another feature or function other than a line key for
preview, shall overwrite active line preview information display, in
response to the user.
d) Upon initialization or re-initialization of the telephone.

The Preview feature is intended for the global marketplace.

To add the preview key to an Optipoint telephone
CHANGE-TAPRO:STNO=7446,DIGTYP=OPTIT19,KY19=PREVIEW;
To increace the timer for the preview function
CHANGE-DTIM1:TYPEDH=DIGITE,CTPRESEL=20;
85.6 Relevant AMOs

TAPRO TDnn d Die neue Taste (nn) heißt PREVIEW
TAPRO KYnn e The new key (nn) is called PREVIEW
DTIM1 DIGITE d Über den Parameter KPDRESEL wird die Dauer
der PREVIEW-Anzeige festgelegt.
DTIM1 DIGITE e Parameter CTPRESEL is used to set the
PREVIEW display duration
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Integrated Key Functionality / Multi Line Access
86 Integrated Key Functionality / Multi Line Access

The feature functions are similar to team systems or multi-line key telephone
systems.
Primary
Line 1
Line 2
Line 3
Line 4
Keyset
Line 5
Line 6
Line 7
Keyset
Primary
Keyset
Line 1
Line 2
Line 3
Line 4
Line 5
Keyset
Line 6
Line 7
• Max. 28 lines per terminal.
• Max. 40 terminals per line.
• Functional on all optiPoint 410 and optiPoint IP.
• Line status display by LED.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Feature Description
• Not allowed with the executive/secretary feature.

Multi-line access can only be activated by terminals which have been specially
configured using AMO KCSU. Terminals configured for this purpose will be
referred to as Keysets in this document.
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 terminals. 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.
86.1.1 Brief Description of Keyset Features

• Every Keyset has an initial or primary line which is reached via the main
station number. 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 flashes. 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
configured, 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,

ORLNPF=PRIME), the last used line (KCSU, ORLNPF=LAST), any
free line (KCSU; ORLNPF=IDLE) or no line (KCSU; ORLNPF=NONE
-- > manual selection required) is seized for outgoing connections.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Feature Description
– Depending on the configured option, either a calling line (KCSU;

TMLNPF=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; 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 subsequent 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 preselection 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
preselection time expires. After preselection the incoming call can be
received on the preselected line by going off-hook.
– Subsequent line selection. The user lifts the handset and presses a line
key to subsequently 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 assigned 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.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Feature Description
– 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).
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 Keysets where the line is assigned.
• Multiple consultation. A user with several assigned lines can initiate a three-
party conference 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 consultation 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 (configured using AMO KCSU,
APRIVAT=YES) is activated as soon as a call is initiated. Keysets without the
automatic private call feature are protected for one connection by activating
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 service menu.
• Ringer cut off. 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.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Feature Description
86.1.2 Display of incoming calls on secondary lines

of a keysystem
If a station is a keysystem and it has several secondary lines configured on it, then
all the incoming calls to any of those keysets who have appearances on the
device must be signaled by the line led blinking (actual behaviour) and also on
the display, indicating who the caller is and which the line number called is.
86.1.2.2 Generation
CHANGE-ZAND:TYPE=KEYSYS,DSAALINC=YES;
Configuration example:
Station A no. 1000 - keyset
Station B no. 1001 - keyset
Station C no 1002 - optiPoint 410, Anate, …..
Station A has on the key no.5 a secondary line of B configured.
When C dials the number of B, this call should by signaled on A, by the blinking
led (no.5) and by displaying "1002 C -> 1001 B ". (Name and number of the
parties, if available)
The display of A must remain active for 10 seconds and return to the previous
display after time-out, if the call is not answered nor dropped during this time.
If B answers the call before the 10 seconds timer expires, then the display of A
must be refreshed and changed back to the display before.
If C goes on-hook (drops the call) before B answers, then the display of A must
be switched back to the previous display. (the one before the call to B occurred).
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Feature Description
86.1.3 Keysystem Flowchart
CODEW OpenScape DIMSU

4000 CC2 KEYSYS
COUNTS KEYSYS
ZAND
CTIME ALLDATA DISPMODE;
CP CTHLDREC
KEYSYSTEM COSLNBAS
DISLNBAS
DTIM1 ACTDA HOLDACKY
DIGITE CTPRESEL STN RCUTOFF HDNOACKY
WABE
DAR HOLDKY
EXHOLDKY
PRIVKY
IUSEKEY
RCTOFFKY
TRNSKY
RLSKY
TOGGLEKE
Y
CONSKY
TAPRO CBKKY
STD XX APRIV
DPRIV
Phantom station
SBCSU SBCSU
STD STD
SECR NO SECR NO
INS YES INS SIGNOFF
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Trading-Executive in a Keysystem
KCSU
PRIM PRIMKEY
RIOP
ORLNPF KCSU
TMLNPF SEC KYNO
SGLBMOD STNOSEC
BUSYRING RIOP
APRIVAT OFFTYPE
AICS
OFFTYPE
Partner Line
Own Line
or
Phantom Line
86.2 Trading-Executive in a Keysystem
86.2.1 Description
The Keysystem feature is expanded with some new functions from the Trading
Executive feature. With this it is now possible to create local wide teams with the
functionality of the Trading Executive. Except for the “Direct Station Selection
Line”, the new features can only be used local.
The following new functions are available:
• Direct station selection line
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
• Mailbox line
• Silent monitoring
• Ringer transfer line
• Repeat dial line
IMPORTANT: In this example, the installing steps for a local Keysystem with the
new features are described. After the local example, you will find a network wide
example with the DSS function!
86.2.2 Installing a local Keysystem with the new

features
86.2.2.1 Local Keysystem
– The subscribers 7210, 7211 and 7212 are added in node 10-30-200.
– These three subscribers form a Team.
05 Line 7210 (prim) 05 Line 7211 (prim) 05 Line 7212 (prim)

07 Line 7235 (sec) private 07 Line 7236 (sec) private 08 Line 7210 (sec)
13 Line 7211 (sec)
C1 C2 S1
7210 7211 7212
KN 200
Add a key layout

CHANGE-
TAPRO:STD=126,DIGTYP=OPTIT19,KY01=CH,KY02=SNR,KY03=FREE,KY04=
SPKR,KY05=LINE,KY07=LINE,KY19=RLS,INFO="KEY-EXECUTIVE TI_E";
CHANGE-
SPKR,KY05=LINE,KY08=LINE,KY13=LINE,KY19=RLS,INFO="KEY-
EXECUTIVE TI_S";
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Subscribers
ADD-SBCSU:STNO=7210,OPT=OPTI,CONN=DIR,PEN=1-2-4-
6,DVCFIG=OPTIP500,COS1=33,COS2=33,LCOSV1=9,LCOSV2=9,LCOSD1=9,
LCOSD2=9,DPLN=0,ITR=0,REP=1,STD=126,TEXTSEL=ENGLISH,CALLOG=TR
IES;
IES;
IES;
Phantom subscriber
ADD-
SBCSU:STNO=7235&7236,OPT=OPTI,CONN=DIR,DVCFIG=OPTIP500,C
OS1=33,COS2=33,LCOSV1=9,LCOSV2=9,LCOSD1=9,LCOSD2=9,STD=1
27,INS=SIGNOFF;
Add the KEYSYSTEM
• primary
ADD-
PF=RING,BUSYRING=ALERT,APRIVAT=NO,AICS=NO;
ADD-
ADD-
ADD-
ADD-
• secondary
ADD-
KCSU:STNO=7210,TYPE=SEC,KYNO=07,STNOSEC=7235,RIOP=YES,AICS=NO
;
ADD-
;
ADD-
KCSU:STNO=7212,TYPE=SEC,KYNO=08,STNOSEC=7210,RIOP=NO,AICS=NO;
ADD-
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Key layout after generating this step
7210 7211 7212

05 05
06 06
07 07
08 08
09 09
10 10
11 11
12 12
13 13
14 14
15 15
16 16
17 17
18 18
19 19
86.2.2.2 Direct station selection line
– The direct call line buttons are phantom lines which have a special
feature.The direct call destinations are assigned to these lines as hotline
destinations The hotline feature program must be activated for this in the
system.If the direct call button is pressed, then the accompanying hotline
destination is called.
– The phantom lines are always configured in pairs and always show the
hotline destinations to each other.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
– The number of direct call line buttons is dependent on the number of

configured lines at the Keysystem telephone. There can be maximum 29
line buttons on a Keyset i.e: the possible number of direct call buttons is
29 minus the existing Prime and Secondary lines.
– If the direct call line button is configured at several keysets, then it shall
be signaled only at a single device (boss). This function corresponds to a
status signalling.The LED of the direct call destination shall show only the
condition of the configured terminal but not of the others (secretary). The
remaining functionality of the direct call is independent of the terminal
type (e.g. flash call, the Name display).
• Expansion of the Keysystem group with the new Features:

13 Line 7211 (sec)
12 DSS to 7211 (7221) 12 DSS to 7210 (7222)
13 DSS for 7211 (7223) 13 DSS to 7212 (7223) 14 DSS to 7211 (7224)
08 DSS to 7212 (7225) 08 DSS for 7210 (7225) 09 DSS to 7210 (7226)
C1 C2 S1
7210 7211 7212
KN 200
Changing key layout (extend STD 126 and 127)

CHANGE-
TAPRO:STD=126,DIGTYP=OPTIT19,KY08=LINE,KY12=LINE,KY13=LINE;
CHANGE-TAPRO:STNO=7210&7211,STD=126;
CHANGE-TAPRO:STD=127,DIGTYP=OPTIT19,KY09=LINE,KY14=LINE;
CHANGE-TAPRO:STNO=7212,STD=127;
Phantom subscriber
ADD-
SBCSU:STNO=7221&&7226,OPT=OPTI,CONN=DIR,DVCFIG=OPTIP500,
COS1=33,COS2=33,LCOSV1=9,LCOSV2=9,LCOSD1=9,LCOSD2=9,STD=
127,INS=SIGNOFF;
Extend the KEYSYSTEM
• primary
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
ADD-
ADD-
ADD-
ADD-
ADD-
ADD-
• secondary
ADD-
,DSSLINE=YES;
ADD-
,DSSLINE=YES;
ADD-
KCSU:STNO=7210,TYPE=SEC,KYNO=13,STNOSEC=7223,RIOP=NO,AICS=NO,
DSSLINE=NO;
ADD-
,DSSLINE=YES;
ADD-
,DSSLINE=NO;
ADD-
DSSLINE=YES;
ADD-
,DSSLINE=YES;
ADD-
,DSSLINE=YES;
If a DSS line (e.g. Phantom 7223) configured on several terminals as a secondary
line, the parameter DSSLINE could be set to “YES” only for one terminal.
Therefor the “owner” of the line is marked. 
If a subscriber is defined as the owner, the DSS peer is informed by the LED at
the DSS key, if the owner is in a “busy-state”.
Description:
The subscriber 7210 has a DSS-key (key 08) to subscriber 7212 and is defined
as the “owner” for this line (DSSLINE=YES). This line is also added for subscriber
7211 (08). But 7211 is not the “owner” of this line (DSSLINE=NO), but could get
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
a call via this key from 7212 to 7210. This possibility is signalized to 7211 by the
blinking LED of key 08. Furthermore 7211 could activate a three-party connection
during an active call between 7210 and 7212. The LED of key 08 will light
constant, if 7210 calls 7212. Thus only the busy state is signalized.
LED signalizing for the DSS peer in case of a “Busy” state
CHANGE-ZANDE:TYPE=ALLDATA,DSSLINE=YES;
Define own name for DSS keys
CHANGE-ZAND:TYPE=KEYSYS,DISLNBAS=YES
e.g.
ADD-PERSI:TYPE=STN,STNO=7221,NAME="DSS FROM 7210";
ADD-PERSI:TYPE=STN,STNO=7226,NAME="DSS FROM 7212";
Activate Hotline
CHANGE-FEASU:TYPE=A,CM=HOTRCL;
Add Hotline destinations
ADD-HOTLN:TYPE=HOTDEST,HTLNIDX=1,DEST=7221;
ADD-HOTLN:TYPE=HOTDEST,HTLNIDX=6,DEST=7226;
Add the authorization for Hotline
CHANGE-COSSU:TYPE=COS,COS=33,AVCE=HOT; or
CHANGE-SDAT:STNO=7221&&7226,TYPE=ATTRIBUT,AATTR=HOT;
Add the Hotline index to the subscribers
CHANGE-SDAT:STNO=7221,TYPE=DATA1,HOTIDX=2;
CHANGE-SDAT:STNO=7226,TYPE=DATA1,HOTIDX=5;
Add additional authorization
CHANGE-SDAT:STNO=7221,TYPE=ATTRIBUT,AATTR=DSSLINE;
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
CHANGE-SDAT:STNO=7226,TYPE=ATTRIBUT,AATTR=DSSLINE;
7210 7211 7212

05 05
06 06
07 07
08 08
09 09
10 10
11 11
12 12
13 13
14 14
15 15
16 16
17 17
18 18
19 19
86.2.2.3 Mailbox per Line
– The mail box buttons shall be line related (per line an assigned mail box).
– All users who own such a mail box button for a certain line can read,
delete and distribute the entries of the mail box.
– Only 1 user can scroll through the same mail box at the same time.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
– Per station up to 29 Mail box keys can be configured.
Remark:
– For the phantom lines the Voice/phone-mail features are not reached by
call forwarding, because the call forwarding belongs to the terminal and
not the line.
– No network wide function

13 Line 7211 (sec)
12 DSS to 7211 (7221) 12 DSS to 7210 (7222)
06 MB.. 7210 06 MB.. 7211 06 MB...7212

10 MBL 7210
15 MBL 7211
C1 C2 S1
7210 7211 7212
KN 200

CHANGE-TAPRO:STD=126,DIGTYP=OPTIT19,KY06=MB;
CHANGE-
TAPRO:STD=127,DIGTYP=OPTIT19,KY06=MB,KY10=MBLINE,KY15=MBLINE;
Add mailbox for line
ADD-ZIELN:STNO=7212,TYPE=MBLINE,KYNO=10,STNOMB=7210;
ADD-ZIELN:STNO=7212,TYPE=MBLINE,KYNO=15,STNOMB=7211;
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
7210 7211 7212

05 05
06 06
07 07
08 08
09 09
10 10
11 11
12 12
13 13
14 14
15 15
16 16
17 17
18 18
19 19
86.2.2.4 Silent monitoring
• The key MONSLNTL uses the BUZZ destination and request the witness
(destination) to enter. The witness enters the conversation, after the entry
request, by pressing the line button or lifting the handset. The third party does
not get any signaling about this and the witness can only listened in. For using
the Buzz-function, only one witness can be defined per subscriber.
• The “witness” must be in the same OpenScape 4000 and must be a member
of a keyset.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
• The solution for the add-on witness connection is a combination of the

already existing Buzz and bridge features.
• No network wide function.

13 Line 7211 (sec)
12 DSS to 7211 (7221) 12 DSS to 7210 (7222)
06 MB.. 7210 06 MB.. 7211 06 MB...7212

10 MBL 7210
15 MBL 7211
18 MONSLNTL 18 MONSLNTL
C1 C2 S1
7210 7211 7212
KN 200

CHANGE-TAPRO:STD=126,DIGTYP=OPTIT19,KY18=MONSLNTL;
Add BUZZ destinations
ADD-ZIEL:TYPE=BUZZ,SRCNO=7210,DESTNOBZ=7211;
ADD-ZIEL:TYPE=BUZZ,SRCNO=7211,DESTNOBZ=7210;
The audible line must exist at both QLRUFNU and BUZRUFNU. Both must
also belong to one keyset and be configured on one system.Add additional
authorization.
CHANGE-SDAT:STNO=7210,TYPE=ATTRIBUT,AATTR=MONSLNTL;
CHANGE-SDAT:STNO=7211,TYPE=ATTRIBUT,AATTR=MONSLNTL;
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
7210 7211 7212

05 05
06 06
07 07
08 08
09 09
10 10
11 11
12 12
13 13
14 14
15 15
16 16
17 17
18 18
19 19
86.2.2.5 Ring Transfer
– At a device several Ring Transfer keys to several destinations can be

configured.
– The switchover deactivates the acoustic signaling and the incoming calls
are signaled by line LED.
– The Ring Transfer changes the RIOP parameter of the affected line at the
source and destination terminal.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
– A ring transfer button lights if the ring transfer to the destination is

activated.
– An incoming call is signaled acoustically, if the participant doesn't have

any activated ring transfer and "RIOP =YES" is configured for the called
line.
– The RIOP parameter has an initial value which is configured by the AMO
KCSU (yes or no).
– Only such lines can be transferred, which would be ringing before the
transfer, and are existing on the destination.
Remarks:
– A ring transfer will activate, when no ring transfer chain is created. In
chained cases "Not Possible” is seen on the display.
– For further activated Ring Transfer incoming calls can be accepted.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm

13 Line 7211 (sec)
12 DSS to 7211 (7221) 12 DSS to 7210 (7222)
06 MB.. 7210 06 MB.. 7211 06 MB...7212

10 MBL 7210
15 MBL 7211
18 MONSLNTL 18 MONSLNTL
09 RNGXFERL to 7212 14 RNGXFERL to 7212 11 RNGXFERL from 7210

16 RNGXFERL from 7211
C1 C2 S1
7210 7211 7212
KN 200

CHANGE-
TAPRO:STD=126,DIGTYP=OPTIT19,KY09=RNGXFERL,KY14=RNGXFERL;
CHANGE-TAPRO:STNO=7210&7211,STD=126;
CHANGE-
TAPRO:STD=127,DIGTYP=OPTIT19,KY11=RNGXFERL,KY16=RNGXFERL;
CHANGE-SDAT:STNO=7210,TYPE=ATTRIBUT,AATTR=RNGXFERL;
CHANGE-SDAT:STNO=7211,TYPE=ATTRIBUT,AATTR=RNGXFERL;
CHANGE-SDAT:STNO=7212,TYPE=ATTRIBUT,AATTR=RNGXFERL;
Add Ringer transfer for the subscriber
ADD-
ZIELN:STNO=7210,TYPE=RNGXFERL,KYNO=05,STNORXFR=7212,RXFRFCT=S
RC;
ADD-
ZIELN:STNO=7212,TYPE=RNGXFERL,KYNO=09,STNORXFR=7210,RXFRFCT=D
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
EST;
ADD-
ZIELN:STNO=7211,TYPE=RNGXFERL,KYNO=05,STNORXFR=7212,RXFRFCT=S
RC;
ADD-
ZIELN:STNO=7212,TYPE=RNGXFERL,KYNO=09,STNORXFR=7211,RXFRFCT=D
EST;
7210 7211 7212

05 05
06 06
07 07
08 08
09 09
10 10
11 11
12 12
13 13
14 14
15 15
16 16
17 17
18 18
19 19
86.2.2.6 Repeat dial function for the used line
– The “redial” key can store destinations of all line keys.
– The last dialed number can be stored line specific.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
– Therefore the subscriber gets an additional authorization in AMO SDAT.

Changing key layout (extend STD 127)
CHANGE-TAPRO:STD=126,DIGTYP=OPTIT19,KY02=LNR/SNR;
CHANGE-TAPRO:STD=127,DIGTYP=OPTIT19,KY02=LNR/SNR;
CHANGE-SDAT:STNO=7210,TYPE=ATTRIBUT,AATTR=SNRLINE;
CHANGE-SDAT:STNO=7211,TYPE=ATTRIBUT,AATTR=SNRLINE;
CHANGE-SDAT:STNO=7212,TYPE=ATTRIBUT,AATTR=SNRLINE;
Activation of the function in AMO ZAND if key LNR is used
CHANGE-ZAND:TYPE=ALLDATA2,LNR=YES;
The LNR of 7212 (own line) will be over written, when the line 7210 is used
and 7210 has no SNRLINE-authorization.
86.2.3 Direct Station Selection network wide
86.2.3.1 Installation of the keysystem network wide via two

nodes
– The subscribers 7210 and 7211 are added in node 10-30-200.
– The subscriber 7110 is added in node 10-30-100.
– These three subscribers form a Team.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
07 Line 7210 07 Line 7211 07 Line 7110

12 Line 7211 12 Line 7210 12 Line 7210 (7126)
17 Line 7110 (7220) 17 Line 7110 (7220) 16 Line 7211 (7127)
7210 7211 7110
KN 200 KN 100
• Node 200 (SYS 1)

Add a key layout
CHANGE-
SPKR,KY07=LINE,KY12=LINE,KY17=LINE,KY19=RLS,INFO="KEY-
EXECUTIVE TI";
New COS with Goupcall (GRPCAL)
ADD-
COSSU:NEWCOS=333,AVCE=TA&TNOTCR&CDRSTN&COSXCD&MB&CFNR&FWDNWK&
TTT&FWDECA&GRPCAL,AFAX=TA&TNOTCR&BASIC&MSN&MULTRA,ADTE=TA&TNO
TCR&BASIC&MSN&MULTRA,INFO="FOR KEYSYSTEM TI";
Subscribers
6,DVCFIG=OPTIP500,COS1=333,COS2=333,LCOSV1=9,LCOSV2=9,LCOSD1=
9,LCOSD2=9,DPLN=0,ITR=0,REP=1,STD=127,TEXTSEL=ENGLISH,CALLOG=
TRIES;
TRIES;
Phantom subscriber
ADD-
SBCSU:STNO=7220,OPT=OPTI,CONN=DIR,DVCFIG=OPTIP500,COS1=3
33,COS2=333,LCOSV1=9,LCOSV2=9,LCOSD1=9,LCOSD2=9,STD=127,
INS=SIGNOFF;
Add the KEYSYSTEM
• primary
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
ADD-
ADD-
ADD-
• secondary
ADD-
KCSU:STNO=7210,TYPE=SEC,KYNO=12,STNOSEC=7211,RIOP=NO,AICS=NO;
ADD-
ADD-
KCSU:STNO=7211,TYPE=SEC,KYNO=12,STNOSEC=7210,RIOP=NO,AICS=NO;
ADD-
Add network wide pickup group for TSC-Signaling
ADD-
=ON3,PUSECOND=YES,SIGNAL=ALL,REMSIGO=YES;
ADD-
ADD-
• Node 100 (SYS 2)
Add a key layout
CHANGE-
TAPRO:STD=127,DIGTYP=OPTIT19,KY01=CH,KY02=SNR,KY03=FREE,
KY04=SPKR,KY07=LINE,KY12=LINE,KY16=LINE,KY19=RLS,INFO="K
EY-EXECUTIVE TI";
New COS with Goupcall (GRPCAL))
ADD-
COSSU:NEWCOS=333,AVCE=TA&TNOTCR&CDRSTN&COSXCD&MB&CFNR&FW
DNWK&TTT&FWDECA&GRPCAL,AFAX=TA&TNOTCR&BASIC&MSN&MULTRA,A
DTE=TA&TNOTCR&BASIC&MSN&MULTRA,INFO="FOR KEYSYSTEM TI";
Subscriber
TRIES;
Phantom subscriber
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
ADD-
SBCSU:STNO=7126&7127,OPT=OPTI,CONN=DIR,DVCFIG=OPTIP500,COS1=3
33,COS2=333,LCOSV1=9,LCOSV2=9,LCOSD1=9,LCOSD2=9,STD=127,INS=S
IGNOFF;
Add the KEYSYSTEM
• primary
ADD-
ADD-
ADD-
• secondary
ADD-
;
ADD-
;
Add network wide pickup group for TSC-Signaling
ADD-
ADD-
ADD-
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
7220 7211 7110

05 05
06 06
07 07
08 08
09 09
10 10
11 11
12 12
13 13
14 14
15 15
16 16
17 17
18 18
19 19
Node 200 Node 100
86.2.3.2 Direct station selection line
– The direct call buttons or direct call line buttons are phantom lines which
have a special feature.The direct call destinations are assigned to these
lines as hotline destinations The hotline feature program must be
activated for this in the system.If the direct call button is pressed, then the
accompanying hotline destination is called.
– The phantom lines are always configured in pairs and always show the
hotline destinations to each other.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
– The number of direct call buttons is dependent on the number of

configured lines at the Keysystem telephone. There can be maximum 29
line buttons on a Keyset i.e: the possible number of direct call buttons is
29 minus the existing Prime and Secondary lines.
– If the direct call line button is configured at several keysets, then it shall
be signaled only at a single device (boss). This function corresponds to a
status signalling.The LED of the direct call destination shall show only the
condition of the configured terminal but not of the others (secretary). The
remaining functionality of the direct call is independent of the terminal
type (e.g. flash call, the Name display).
• Expansion of the Keysystem group with the new Features:
– Subscribers 7210 and 7211 are configured in node 30-200.
– Subscriber 7110 is configured in node 30-100.
– This three subscribers form one team.
07 Line 7210 07 Line 7211 07 Line 7110

12 Line 7211 12 Line 7210 12 Line 7210 (7126)
17 Line 7110 (7220) 17 Line 7110 (7220) 16 Line 7211 (7127)
11 DSS 7211 (7221) 11 DSS 7210 (7222) 11 DSS 7210 (7128)

15 DSS 7110 (7223) 15 DSS 7110 (7223) 15 DSS 7211 (7129)
16 DSS 7110 (7224) 16 DSS 7110 (7224)
7210 7211 7110
KN 200 KN 100
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
• Node 200 (SYS 1)

CHANGE-
TAPRO:STD=127,DIGTYP=OPTIT19,KY11=LINE,KY15=LINE,KY16=LINE;
Phantom subscriber
ADD-
COS1=333,COS2=333,LCOSV1=9,LCOSV2=9,LCOSD1=9,LCOSD2=9,ST
D=127,INS=SIGNOFF;
• primary
ADD-
ADD-
ADD-
ADD-
• secondary
ADD-
,DSSLINE=YES;
ADD-
KCSUSTNO=7210,TYPE=SEC,KYNO=15,STNOSEC=7223,RIOP=YES,AICS=NO,
DSSLINE=YES;
ADD-
DSSLINE=NO;
ADD-
,DSSLINE=YES;
ADD-
DSSLINE=NO;
ADD-
,DSSLINE=YES;
If a DSS line (e.g. Phantom 7223) configured on several terminals as a secondary
line, the parameter DSSLINE could be set to “YES” only for one terminal.
Therefor the “owner” of the line is marked. 
If a subscriber is defined as the owner, the DSS peer is informed by the LED at
the DSS key, if the owner is in a “busy-state”.
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Description:
e.g.
ADD-PERSI:TYPE=STN,STNO=7224,NAME="DSS FROM 7211";
Activate Hotline
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Activate LED signaling in the network

CHANGE-ZAND:TYPE=VMI,MWIOPEN=YES; (for Xpression)
CHANGE-COT:COTNO=xx,COTTYPE=COTADD,PAR=TSCS;
• Node 100 (SYS 2)
CHANGE-TAPRO:STD=127,DIGTYP=OPTIT19,KY11=LINE,KY15=LINE;
CHANGE-TAPRO:STNO=7110&7126&7127,STD=127;
Phantom subscriber
ADD-
SBCSU:STNO=7228&7229,OPT=OPTI,CONN=DIR,DVCFIG=OPTIP500,C
OS1=333,COS2=333,LCOSV1=9,LCOSV2=9,LCOSD1=9,LCOSD2=9,STD
=127,INS=SIGNOFF;
• primary
ADD-
ADD-
• secondary
ADD-
,DSSLINE=YES;
ADD-
,DSSLINE=YES;
e.g.
ADD-PERSI:TYPE=STN,STNO=7228,NAME="DSS TO 7110";
ADD-PERSI:TYPE=STN,STNO=7229,NAME="DSS TO 7110";
Unblock Hotline
A31003-H3170-S103-6-7620, 02/2019
key_en.fm

LED signaling in the network
CHANGE-ZAND:TYPE=VMI,MWIOPEN=YES; (for Xpression)
CHANGE-COT:COTNO=xx,COTTYPE=COTADD,PAR=TSCS;
7210 7211 7110

05 05
06 06
07 07
08 08
09 09
10 10
11 11
12 12
13 13
14 14
15 15
16 16
17 17
18 18
19 19
Node 200 Node 100
A31003-H3170-S103-6-7620, 02/2019
key_en.fm
Relevant AMOs
86.3 Relevant AMOs

Language
KCSU DRLEITNG d Direktrufleitung mit Taste beim Direktrufleitungs-
partner
DSSLINE e dss line with key on dss line partner
SDAT DRLEITNG d Direktrufleitung
DSSLINE e dss line
RULEITNG d Rufumschaltung der Leitung erwünscht
RNGXFERL e ring transfer for line desired
WWLEITNG d WW-Ziel der benutzten Leitung benutzen
SNRLINE e use redail number of used line
MITHOERL d Mithören/Eintreten ohne Ton in Leitung
MONSLNTL e silent monitoring/bridge of line
TAPRO BKLEITNG d Briefkasten für Leitung
MBLINE e mailbox key for line
RULEITNG d Rufabschaltung der Leitungstasten
RNGXFERL e ring transfer (for executive/ secretary) key
MITHOERL d Mithören/eintreten ohne Ton in die Leitung
MONSLNTL e silent monitoring / bridge of line
ZIELN BKLEITNG d Briefkasten für Leitung
ZANDE DRLEITNG d LED Statusanzeige bei Direktrufleitung
DSSLINE e deactivate LED status display at DSS lines
ANZKOMRF d Ist der Parameter gesetzt,so werden auch
kommende Rufe auf der Secondary Line von
Key-Systemen angezeigt.
DSAALINC e If this parameter is set,also incoming calls on
secondary lines of keysystems will be displayed.
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
General Information
87 Parallel Ringing - One Number Service (ONS)

The feature Parallel Ringing – One Number Service (ONS) is used for one
person using different phones. Incoming calls are signalled at more than one
destination in parallel (simultaneously).
Also a typical scenario is also the use of One Number Service for service
deliveries. Depending on who is on duty, the responsible service technician is
reachable over one fixed number. If the responsible engineer needs to recall the
customer via the SIP device, the server number of the help desk is shown in the
customer's display. His own mobile phone number cannot be seen. This ensures
that the customer always reaches an employee when calling this number.
Figure 105 Parallel Ringing with one number
An incoming call is blocked by busy, if one station of the parallel ringing station
group is busy.
All internal ONS members have the same idle display showing the ONS master
number.
Exception: If a CMI mobile was configured as ONS slave, the idle display does
not show the ONS master number. The CMI phones keep in idle state their own
numbers on display.
For a basic incoming call to the ONS group the call is signalled at all ONS
members. All ONS members see the calling party information. After answering
the call by one ONS member all other group members are disconnected from the
call. The whole ONS group is called no matter whether the ONS master number
or a secondary ONS number has been dialed.
If the ONS master is out of service any incoming call to the ONS group is blocked.
If one of the secondary ONS phones is out of service the other phones shall work
as usual.
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Service Information
For the ONS call to the external number no CFNR is honored; in this case the
external call is released but the internal ONS members are still ringing. The
purpose of this processing is to avoid that the ONS call only reaches the mailbox
of the GSM network although the ONS person is near one of the internal ONS
phones. Trunks who cannot receive reliable answer and disconnect signalling
must not be used for the ONS call to the external member. The information from
the GSM via the CO is not as detailed as within the PBX network (especially in
negative cases when the mobile phone cannot be alerted) and therefore it is
recommended that the mobile phone is always turned on.
87.2.1 General Notes

• Up to 2000 parallel ring groups (ONS group or a call pickup group) are
supported within one OpenScape 4000 node.
• The maximum number of ONS members is 3 (master and two slaves).
• Anates, digites, HFA subscribers, SIP subscribers and virtual secondary

devices are considered as ONS members (master and/or slave). A virtual
ONS master or a REMAC number doesn’t count as ONS member in this
respect.
If the master/slave of an ONS group is a SIP subscriber please refer to
Section 87.2.5, “ONS Groups with SIP Subscriber as Master/Slave”.
• As slave (instead of B2 or B3) one GSM mobile phone or another external

terminal may be in an external GSM network with the special ringing function
"search mobile phone first" (SMPF).
• There is no busy signalization of the ONS master number, if the external

subscriber has taken a call.
• One ONS member can call another ONS member of the same group (ONS
internal call).
• Last number redial, saved number redial, speed dialing, namekeys, direct
station select keys and reminders are available for each ONS device
separately.
• For incoming calls the ONS master extension number B is equal B1.
The features call waiting, call forwarding (CFW), do not disturb (DND),
message waiting indication (MWI), callback and call logs are ONS group
features.
• Outgoing calls are always initiated with the number, COS and LCOS of the
master extension.
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Service Information
Same COS, same ITR group, same WABE group and same COSX group.
This is ensured by using the Permanent PIN feature. The pin of the master
device is automatically activated on all slave devices by starting up the phone
or by configuring a new ONS group.
The permanent PIN cannot be modified by the ONS device; only a short PIN,
valid for only one call can be activated.
IMPORTANT: PIN for SIP phones is not implemented yet, therefore

activation of master PIN is not possible on SIP phone slaves.
87.2.2 Interactions with other Features

Call Forwarding
When an ONS group is created the callf orwarding activation status of the ONS
master is relevant for the incoming ONS calls. The idle display is updated at the
internal ONS members if necessary. Any change of this status by one of the
internal ONS members leads to the ONS group callforwarding status change.
Changes via AMO or via ACL service are also effective for the whole ONS group.
Call deflect from an ONS member alerted by an incoming call to the static CFW
destination of the ONS group is possible.
Notes for SIP subscribers:
Activation/Deactivation of Call Forwarding types using AMO ACTDA for one SIP
ONS member is propagated to all SIP ONS members.
Setting of Call Forwarding using AMO ZIEL is not possible for SIP devices.
Therefore it does not apply for SIP ONS groups.
Call Forward Busy set with AMO ACTDA is executed only if COS MULTRA is not
set.
Do not disturb
Do not disturb is also an ONS group feature. The ONS master status for DND
determines the DND group status. Any internal ONS member can change this
DND status for the whole ONS group. Changes via AMO or via ACL service are
also effective for the whole ONS group.
Call Waiting
If call waiting as ONS group feature is activated then a second call to the ONS
group is alerting the group even if one ONS member is busy. Call waiting can be
(de)activated by a key at the device of the ONS member.
Exception: If all internal ONS devices are anates then the call waiting feature is
(de)activated by the AMO AUN parameter PUSECOND.
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Service Information
Message waiting indication (MWI)

Message waiting indication (MWI) is an ONS group feature. MWIs to the ONS
group are stored at the ONS master; the status of the MWI led is shown at all
internal ONS members.
Call Logs
Call Logs of the ONS group are stored in the call log of the ONS master and can
be accessed by any internal digite ONS member. Simultaneous menu access to
the call log is prevented. Call log is only supported if the ONS master is a digite.
Callback
Callback activated by an ONS member to another station is not an ONS group
feature. Callback execution only alerts the ONS member who has activated
callback.
Callback activation to the ONS group, however, is an ONS feature. All members
are alerted after callback execution.
Message waiting callback to the ONS group is also an ONS group feature.
IMPORTANT: For SIP subscribers

If a slave has COS MULTRA set and is busy then Callback Busy cannot be set.
IMPORTANT: If Callback Busy is set when a slave is busy, it is not executed

when the slave goes idle. The master should go idle to invoke callback.
Recalls
Recalls to an ONS member are not ONS group calls; they are only alerting the
ONS member who has previously transferred the call.
Campon/Override
Campon or override to a busy ONS group is possible.
Keyset
ONS master and ONS secondary extension numbers must not appear at any
other keyset. ONS devices may have secondary lines from any other non ONS
keysets.
Conference
One ONS member can call another ONS member of the same group (ONS
internal call). This call is not alerting any other ONS group members. Therefore
it is possible to establish a conference with outside partners and with members of
the same ONS group.
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Service Information
Handover
Handover of ONS connections from one internal ONS member to another internal
ONS member is possible.
• Handover by active extension: A digite ONS member presses the parkkey

in talk state. Then the call is parked and the parkkey led of all digite ONS
group members starts flashing. The former active ONS subscriber goes
onhook and the call can be retrieved by the parkkey.
• Handover by passive extension: If there is one basic ONS connection

active then another ONS member can retrieve the call by pressing the
parkkey. Anates and digites without a parkkey can use the associated
accesscode for parking and retrieving a call.
Hunt Group
Only master devices of an ONS group are allowed to be members of a hunt group
(but not master). Wird eine ONS-Gruppe über einen Sammelanschluss belegt,
wird der AMO AUN Parameter SMPF grundsätzlich ignoriert.
The secondary member of an ONS group is able to log on/log off the master of
the ONS group (which is also a member of a hunt group) to/from the hunt group.
IMPORTANT: For SIP subscribers:

If the ONS master is a SIP phone, then the following hunt group and SIP phone
restriction applies: A functional device (or SIP device) configured in a hunt group
must never have the parameter MULTRA set in AMO COSSU!
DSS key
Calls via DSS key with an ONS number are alerting the whole ONS group.
Service Information
The LED of the DSS key for an ONS master number indicates the state of the
ONS group:
• If the ONS group is idle then the LED is off.
• If the ONS group is busy then the LED is on.
• If the ONS group is ringing then the LED is flashing.
For an ONS secondary number the LED of the DSS key indicates the state of the
ONS secondary member.
Generation
For a station the ONS master or secondary number is configured as destination

for a DSS key. This can be done via AMO ZIEL as well as via programming by
the user at the phone.
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Service Information
87.2.3 Notes on Configuration

• Subscribers can not be added to OSN groups after they are configured. In this
case regenerate,delete and re-add the ONS group with the new subscriber
information.
• All members of an ONS group (master and slave - subscribers B1, B2 and
B3) are to be configured in the same node.
• Subscribers of an ONS-group must be in the same ITR-group.
• The parallel ringing station group is configured via AMO AUN with parameter
TYPE=ONS.
• Internal ONS members are assigned by the AMO AUN as group members.
The ONS group consists of exactly one ONS master (who has the AMO SDAT
parameter PARARNGM) and secondary members (who have the AMO SDAT
parameter PARARNGS).
• The external ONS member number is assigned by the parameter REMAC.

For this external member a virtual secondary device has to be added as ONS
member. This virtual secondary device is configured via AMO SCSU with
DVCFIG=AUXDIGI and INS=ACLSTN and via AMO SDAT parameter
PARARNGS.
• The ONS master must have a PIN activated with the following AMO PERSI
COPIN values: PINDUR=PERM (permanent), PARARNGM=YES (pararing
master), TRANSFER=ALL (tranfer all key contents and cos),
COSHOME=YES, DISPRSTN=NO (no display of remote station) and
IDHOME=NO. Outgoing trunks to the central office or to the expression
server must have the COT parameter VNCO so that the permanent PIN is
considered for outgoing calls from an ONS member.
• The AMO AUN parameter SMPF (search mobile phone first) indicates for a
basic call to an ONS group the following:
SMPF=YES: The mobile phone is called first before the internal ONS
members are called (waiting a time period specified by the AMO CTIME
parameter SMPFTIME). If an external station (REMAC) is used in an ONS
group, the parameter SMPF is fixed to YES and cannot be changed.
SMPF=NO: The internal ONS members are also called immediately.
IMPORTANT: SMPF is not considered e.g. for a consultation call to the ONS
group or if call waiting is active for this call.
• The AMO AUN parameter ONSSNS indicates if the number of an ONS

secondary member should be suppressed or not.
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Service Information
• The AMO AUN parameter PUSECOND indicates if the pickup of a second call
to the ONS group is enabled or not. This AMO parameter is relevant for an
ONS group where the internal members are only anates. For an ONS group
call waiting can be (de)activated via key at the device.
In addition to the PUSECOND parameter: If there is an ONS group with only
anate members (and maybe a virtual secondary member and a REMAC) and
the feature call waiting should be active for this ONS group then it is
recommended to add a virtual ONS master to this ONS group. Only then the
call waiting feature is supported. This virtual ONS master must not have the
AMO COSSU COS parameter MB (mailbox) assigned and must not have a
MB key assigned via AMO TAPRO. This is necessary to ensure that a
callback to this anate ONS group is handled according to CCNR (call
completion no reply) and not according to the mailbox function (where the
mailbox key doesn’t exist).
87.2.4 Restrictions
• This feature is only active for voice calls.
• The feature is not supported for DSS1 phones (S0), attendant consoles or
analog voice terminals connected to a T/R adapter!
• ONS group for CHESE (chief secretary group) members is not supported.
• ONS group members cannot be members of call pickup groups.
• ONS group members must not be configured as night stations.
• ONS group members must not be configured as ACD agents.
• If the master of an ONS group is a SIP subscriber, the secondary members

cannot be HFA subscribers.
• MLPP, Emergency Override and emergency disconnect is not supported from

and to ONS group members.
87.2.5 ONS Groups with SIP Subscriber as Master/

Slave
Requirements
• The ONS group must not contain any Anate, TDM or HFA subscriber, if the
master is a SIP subscriber. The slaves must also be SIP subscribers.
If the SIP subscriber is a slave in the ONS group then the master can be a
TDM or HFA subscriber (SIP slave is added via AUXDIGI and SIP number in
REMAC of ONS Group).
The following combinations are possible for HFA, TDM and SIP subscribers:
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Service Information
Slave: SIP Slave: HFA Slave TDM

Master: SIP x --- ---
Master: HFA x x x
Master: TDM x x x
Table 57 Combinations of an ONS group with HFA, TDM and SIP

subscribers
• The ONS group must not contain an external mobile phone.
• Parallel ringing must be initiated by the SIP subscriber (=MASTER).
Service Information
• ONS group features are limited. Only the currently supported SIP phone
features are supported.
• Activation of local features on the SIP phone is not signaled to the system and
therefore these features cannot be controlled by the system.
• Some system features are not released for SIP phones and some features
exist only for SIP phones. Therefore there are cases when ONS SIP groups
behave differently than ONS classic groups.
• COS MULTRA (multiple transactions - the station can be seized multiple

times) is a parameter which might be set for SIP devices, because it is
needed for some features to work correctly. When MULTRA is set, the busy
state of the SIP device is ignored by the system and a SIP phone is seized.
• Members display
ONS SIP members keep their own idle display, showing their number rather
than the master's number.
The parameter DISPRSTN AMO PERSI:COPIN does not apply for SIP ONS
groups. The master number will be always shown for internal SIP ONS calls.
• ACL
– Call forwarding:
ACL reports call forwarding situations differently depending of call
forward activation (local or system), the COS MULTRA parameter and
which SIP ONS member is called.
Remark: Call Forward Unconditional/Busy activated locally on a slave
SIP phone is executed and reported as CF No Answer in ACL messages.
– Incoming Calls:
ACL reports incoming calls differently to ONS scenarios depending on the
COS MULTRA and Local Call Waiting settings.
• Local feature interaction
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Service Information
– Local Do not Disturb (only for SIP subscribers)

If a member has DND (Do not Disturb) activated locally, all the other ONS
members are alerted shortly and then cleared when the member with
DND disconnects.
When DND is set for the ONS member, the behavior differs depending on
whether the member is a master or slave. If the member is a master, the
calling party gets the disconnect message in dialing state. If the member
is a slave, the calling party gets the disconnect message in ringback state,
because the master acknowledged the call just beforehand. In this
second case, the DND set for the slave is processed for the calling party
as a call reject.
Remark: DND for SIP cannot be set using AMO ACTDA.
– Local Call Forward

A SIP phone can activate internal Call Forward (SIP-specific feature). The
system is not informed of this action. Therefore call forward will be only
executed when the SIP phone is reached.
When a member has activated a local Call Forward, a call to the SIP ONS
group will ring for all members and then it will be forwarded to the call
forward destination.
Remarks:
If both Call Forwards No Reply are set (local on the phone and with AMO
ACTDA) the one with the shorter no answer timer will be executed.
If master and slave have the same type of local Call Forward activated,
the master call forward will be executed.
– Deflect call
Deflect is a local feature that can be used by a SIP phone to transfer the
call in a ringing state. When one ONS SIP member invokes this feature,
the call will be transferred to the new destination.
– Refuse call
Refuse is a local feature that can be used by a SIP phone to reject a call.
When one ONS SIP member invokes this feature, the call will be
disconnected.
– Local Do not Disturb

If a member has DND (Do not Disturb) activated locally, all the other ONS
members are alerted shortly and then cleared when the member with
DND disconnects.
When DND is set for the ONS member, the behavior differs depending on
whether the member is a master or slave. If the member is a master, the
calling party gets the disconnect message in dialing state. If the member
is a slave, the calling party gets the disconnect message in ringback state,
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Service Information
because the master acknowledged the call just beforehand. In this

second case, the DND set for the slave is processed for the calling party
as a call reject.
Remark: DND for SIP cannot be set using AMO ACTDA.
– Local Call Log

Any call to the SIP ONS group will be saved in the alerted member's call
log.
– Second call
Call Waiting is a local SIP phone feature that can only be used if COS
MULTRA is set. The list below contains an overview of ONS group
behavior. Call Waiting for SIP phones is possible when the SIP phone is
in talk state. Call Waiting for SIP phones is not possible when the SIP
phone is in ringing state.
ONS group action result when result when

state busy SIP has busy SIP has
CW on CW off
COS ONS is busy in call master call cleared, call cleared,
MULTRA set ring state busy busy
call slave call cleared, call cleared,
busy busy
ONS is busy, call master ONS ONS
master is in members ring members ring
talk state shortly and
then call
cleared, busy
call slave ONS ONS
members ring members ring
shortly and
then call
cleared, busy
ONS is busy, call master ONS ONS
slave is in talk members ring members ring
state shortly and
then call
cleared, busy
call slave ONS ONS
members ring members ring
shortly and
then call
cleared, busy
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
ONS group action result when result when

state busy SIP has busy SIP has
CW on CW off
COS ONS is busy in call master call cleared, call cleared,
MULTRA not ring state busy busy
set
busy busy
ONS is busy, call master call cleared, call cleared,
master is in busy busy
talk state
busy busy
ONS is busy, call master call cleared, call cleared,
slave is in talk busy busy
state
busy busy
Remark: For the situation when COS MULTRA is set and busy SIP
phone has Call Waiting off:
• ONS is busy, master is in talk state: the call is disconnected before the
request is accepted.
• ONS is busy, slave is in talk state: the call is disconnected after

request is accepted.
– Out of Service
If the master SIP device is out of service any incoming call to the ONS
group is blocked.
If one of the slave SIP devices is out of service the other members work
as usual.
Remark: If the SIP phone is unplugged, it is not signaled as "Out of
Service" to the system.
Restriction
• Handover will not be supported
• PIN is not supported for SIP devices; therefore the “PIN permanent" feature
isn't used.
87.3.1 Configuration steps

• Configuring the real ONS group members
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
• Configuring the virtual ONS group members
• Setting subscriber authorizations
• Defining the COPIN class used for the master PIN
• Assigning the master PIN to the ONS master
• Adding an ONS group
• Additional control mechanisms
87.3.2 Example with Auxiliary Device
IMPORTANT: The example below shows the steps to be followed for AMO
configuration. CMI station configuration is not taken into consideration here.
ONS group 8
COPIN 15 for
7150 (HFA/TDM)
master PIN
ONS master
6100 (CMI)
ONS members
7151 virtual SUB (ACLSTN)

ONS member
ISDN
Calls: 7150
01751234567
1. System-wide AMOs
ADD-DIMSU:TYPE=BASIC,AUXDIGI=xx;
xx=number of virtual stations, if GSM devices or other external stations are
being used in an ONS group.
2. Checking the FWDMAX counter.

Parallel ringing of ONS members is achieved with the FWD functions:
DISPLAY-ZAND:TYPE=ALLDATA2;
CHANGE-ZAND:TYPE=ALLDATA2,FWDMAX=xx;
3. Configuring station 7150 (ONS master)
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
ADD-SBCSU:STNO=7150,OPT=OPTI,CONN=IP2,PEN=1-1-37-
0,DVCFIG=OPTIIP,COS1=33,COS2=30,LCOSV1=9,LCOSV2=1,LCOSD1=5,LC
OSD2=1,DPLN=0,ITR=0,SSTNO=NO,COSX=1,SPDI=0,SPDC2=1,IDCR=NO,RE
P=0,STD=104,SECR=NO,INS=YES,ALARMNO=0,RCBKB=NO,RCBKNA=NO,CBKB
MAX=5,CBKNAMB=YES,TEXTSEL=GERMAN,IPCODEC=G711PREF;
4. CMI station (6100) already configured
5. Configuring the virtual station 7151 (ACLSTN)

ADD-
SCSU:STNO=7151,DVCFIG=AUXDIGI,DPLN=0,ITR=0,COS1=10,COS2=10,LC
OSV1=1,LCOSV2=1,LCOSD1=1,LCOSD2=1,INS=ACLSTN;
6. Assigning station authorization
Master: CHANGE-SDAT:STNO=7150,TYPE=ATTRIBUT,AATTR=PARARNGM;
Slave: CHANGE-SDAT:STNO=6100,TYPE=ATTRIBUT,AATTR=PARARNGS;
CHANGE-SDAT:STNO=7151,TYPE=ATTRIBUT,AATTR=PARARNGS;
7. Defining COPIN class 15 for the master PIN

CHANGE-PERSI:TYPE=SYS,PIN15LEN=4;
CHANGE-PERSI:TYPE=COPIN,COPIN=15,COTYPE=NONE,PINTEXT="ONS
MASTER",DISPRSTN=NO,PINDUR=PERM,IDHOME=NO,PARARNGM=YES,COSHOM
E=YES;
8. Assigning the master PIN to the ONS master
ADD-PERSI:TYPE=STN,STNO=7150,NAME=”ONS
MASTER”,PIN15=7150,PININDIV=YES;
9. Configuring ONS group 8
ADD-AUN:GRNO=8,TYPE=ONS,STNO=7150&7151&6100;
ADD-AUN:GRNO=8,TYPE=ONS,REMAC=001751234567;
10. Displaying the ONS group
DISPLAY-AUN:TYPE=ONS;
+-----------------------------------------------------------+
| GROUP NO.: 8 |
| PU SECOND CALL: NO |
| ONS : YES SMPF : YES ONSSNS : NO |
| |
| SUBSCRIBER: 7150 (MASTER) |
| 7151 |
| 6100 |
| REMAC: 001751234567 |
+-----------------------------------------------------------+
11. Description of the additional control mechanisms
• AMO PERSI: COPIN

DISPRSTN = YES:
The original number is displayed on the B station for an outgoing call from
an ONS slave station.
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
DISPRSTN = NO:
The ONS master number is displayed on the B station for an outgoing call
from an ONS slave station (default).
• AMO CTIME: CP2, SMPFTIME (default 8 sec.)

This preset time period is the maximum that the system will wait for a
response from the external station (REMAC call number). If there is no
response after this time has elapsed, the internal ONS stations will ring.
If there is a response before this time has elapsed, all free ONS stations
ring simultaneously.
87.3.3 Example with SIP Subscriber (Master and

Slave)
1. Checking the FWDMAX counter.
DISPLAY-ZAND:TYPE=ALLDATA2;
2. Configuring ONS master
The master SIP phone must have PARARNGM set by AMO SDAT.
SIP phone 3432 - Master of ONS group:
ADD-SBCSU:STNO=3432,OPT=FPP,CONN=SIP,PEN=1-1-6-
35,DVCFIG=S0PP,COS1=33,COS2=33,LCOSV1=5,LCOSV2=5,LCOSD1=5,LCO
SD2=5,DPLN=0,ITR=0,SSTNO=N,COSX=0,SPDI=0,PROT=SBDSS1,PERMACT=
Y,INS=Y,ALARMNO=0,OPTIDX=10,RCBKB=N,RCBKNA=N,CBKBMAX=5,HMUSIC
=0,PMIDX=1,IPCODEC=G7 11,PASSWD="",USERID="",SECZONE="";
CHANGE-SDAT:STNO=3433,TYPE=ATTRIBUT,AATTR=PARARNGM;
3. Configuring ONS member
The slave SIP phone must have PARARNGS set by AMO SDAT.
SIP phone 3433 - member of the ONS group:
SIP phone 3434 - member of the ONS group:
4. Configuring ONS group:
/* SIP subscriber as master and member of an ONS group
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Relevant AMOs
ADD-AUN:GRNO=1,TYPE=ONS,STNO=3432&3433&3434;
IMPORTANT: DIS-AUN for ONS presents the SIP member twice: once in the
member's area and once in the REMAC area.
87.4 Relevant AMOs

Language
AUN TYP=ONS d One-Number-Service
TYPE=ONS e One Number Service
TLNNU d Teilnehmerrufnummer: Alle internen ONS-
Apparate, auch das virtuelle Gerät (wenn
benutzt), sind Teilnehmerrufnummern einer
Anrufübernahmegruppe.
STNO e Station number: All internal ONS extensions
including the virtual device (if needed) are
station numbers of a pickup group.
REMKZ d Remote-Knotenkennzahl: Muss benutzt
werden um das externe ONS-
Gruppenmitglied (GSM-Telefon)
zuzuweisen.
REMAC e Remote access code: Has to be used to
assign the external ONS group member
(GSM phone).
AUNZWEIT d Anrufübernahme des Zweitanrufs möglich:
Anrufübernahme des Zweitanrufs muss
benutzt werden, wenn alle ONS-Mitglieder
analoge Telefone sind.
PUSECOND e Pick up of second call enabled: Pickup
second call has to be used if all ONS
members are analog phones.
SMPF d Zuerst Mobiltelefon suchen: Die SMPF-
Option ist nur gültig, wenn die
Anrufübernahmegruppe die Rolle einer
ONS-Gruppe hat.
SMPF e Search mobile phone first: The SMPF option
is only valid if the pickup group is in role of
an ONS Group.
ONSSNS d ONS-Slave-Nummer unterdrücken
ONSSNS e Suppress ONS Slave Number
SDAT PARARUFM d Master einer Parallelrufgruppe: Muss allen
ONS-Master-Apparaten zugewiesen
werden.
A31003-H3170-S103-6-7620, 02/2019
ons_en.fm
Relevant AMOs

Language
PARARNGM e Master of a parallel ringing group: Has to be
assigned to all ONS master extensions.
PARARUFT d Teilnehmer einer Parallelrufgruppe: Muss
allen ONS-Sekundär-Apparaten
zugewiesen werden.
PARARNGS e Subscriber of a parallel ringing group: Has to
be assigned to all ONS secondary
extensions.
PERSI PARARUFM d PIN für Master einer Parallelrufgruppe:
Muss der COPIN des ONS-Master-Telefons
zugewiesen werden, um das permanente
Merkmal PIN zu aktivieren.
PARARNGM e PIN for master of a parallel ringing group:
Has to be assigned to the COPIN of the
ONS master phone in order to enable the
PIN permanent feature.
ANZFREMD d Zweig COPIN
ANZFREMD = JA: ONS-Slave-Nummer
wird als CLIP gesendet.
ANZFREMD = NEIN: ONS-Master-Nummer
wird als CLIP gesendet..
Das wird durch den Parameter ONSSNS im
AMO AUN bewirkt.
DISPRSTN e Branch COPIN
DISPRSTN = YES: ONS slave number is
sent as CLIP.
DISPRSTN = NO: ONS master number is
sent as CLIP.
This is effected by the ONSSNS parameter
in AMO AUN.
CTIME SMPFTIME d Wartezeit für Rückmeldung des
Mobiltelefons
SMPFTIME e Waiting time for Mobile Phone Response
A31003-H3170-S103-6-7620, 02/2019
personal_device_group_en.fm
Feature Description
88 Personal Device Group

The feature „Personal Device Group“ is a personal group of multiple phones
which can be reached under one unique number.

Personal Device Group supports the usage of two devices for one extension
number in a OpenScape 4000 system. These are usually one desktop phone and
one cordless phone (CMI).
The Personal Device Group concept is based on keyset functionality to allow

multiple devices using the same number. Keyset configuration is also allowed for
CMI and also a special Personal Device Group flag for the Keysets is introduced.
The CMI device has the Personal Device Group number as prime line (Personal
Device Group master) and the desktop phone has the Personal Device Group
number as secondary line (Personal Device Group slave). The Prime Line of the
Desktop Phone is not used.
Outgoing calls from the cordless or the desktop phone transmit always the same
number (Personal Device Group number) to the destination.
Incoming calls are signaled on both devices and the user decides where to
answer the call.
At the same time only one of the devices can initiate a call with Personal Device
Group number. If the CMI is talking the desktop phone can not initiate a call with
Personal Device Group number.

The feature „Personal Device Group“ will be released in several steps:
• Personal Device Group Step 1

Support of one desktop phone (optiPoint or openStage, either TDM or IP-
HFA) and one CMI
88.2.1 Supported Devices

• Personal Device Group master: CMI Cordless (S2, SL2)
• Personal Device Group slave: TDM or HFA device
A31003-H3170-S103-6-7620, 02/2019
Service Information
88.2.2 Restrictions
• When parameter TWINNING is changed from YES to NO in AMO KCSU, the
extension number on the phone displays are updated only when the phone
idle display is shown / updated.
• The master device (CMI) has exactly 1 line (its own prime line) configured.
• The slave device has exactly 2 lines configured (its own prime line and the
prime line of the CMI as a secondary line).
• Allthough the CMI is used as a keyset there are no line keys supported for
that device. The CMI devices which are being used are S2-SL2 and S3-SL3.
There is only one CMI allowed for a Personal Device Group group.
• Attendant is not supported by the Personal Device Group feature.
• All members of the Personal Device Group configuration must be assigned to

the same WABE group.
• All members must be in the same switch. It is not possible to combine a

desktop phone of one switch with a CMI configured in a different switch.
• Some menu items are handled different on desktop phone and CMI.
• One device can only be in one Personal Device Group group.
• No other keysets may be combined with the Personal Device Group group.
88.2.3 Supported Features
IMPORTANT: For features with restrictions the restriction is described in the

section of the feature.
The features that are not listed in this section are not supported for Personal
Device Group!
Basic Call
Incoming call:
In case of an incoming call (intern or extern) to Personal Device Group both
devices the desktop phone and the cordless device ring simultaneously. If one of
these devices answers the call the other device stops ringing.
A31003-H3170-S103-6-7620, 02/2019
Service Information
Outgoing call:
In case of outgoing call (intern or extern) from Personal Device Group the
Personal Device Group number will be displayed on the called device as the
calling number no matter if the call was initiated from the cordless or from the
desktop phone.
This behavior is also the same in case of call forwarding:
• Call forward unconditional
• Call forward busy
• Call forward no answer
User interface:
On both devices of the Personal Device Group group the Personal Device Group
number is displayed as the extension number belonging to the device.
In general the display structure is different in case of cordless and desktop (e.g.
optiPoint) phones. This is also the case for the members of a Personal Device
Group.
Call back
This feature can be used from and to the devices of a Personal Device Group.
Callback busy / no answer

Callback is supported for a Personal Device Group for internal endpoints only.
The callback will be signaled and can be executed on both endpoints of the
Personal Device Group.
External devices will not be supported for callback. Therefore no callback busy is
possible on external devices.
Configuration:
• Callback without mailbox:
/* RRFBK=N: Callback on no answer is not stored in the mailbox
CHANGE-
SBCSU:STNO=twincmi,RCBKB=NO,RCBKNA=NO,OPT=OPTI,CBKNAMB=NO;
CHANGE-
SBCSU:STNO=twinopti,RCBKB=NO,RCBKNA=NO,OPT=OPTI,CBKNAMB=NO;
• Callback with mailbox
/* BRK MAIL BOX (AUTHORIZATION TO RECEIVE MAIL)
/* set it for the COS of twincmi and twinopti */
CHANGE-COSSU:TYPE=COS,COS=23,AVCE=MB;
A31003-H3170-S103-6-7620, 02/2019
Service Information
/* RRFBK=J : Callback on no answer is stored in the mailbox

CHANGE-
SBCSU:STNO=twincmi,RCBKB=NO,RCBKNA=NO,OPT=OPTI,CBKNAMB=YES;
CHANGE-
SBCSU:STNO=twinopti,RCBKB=NO,RCBKNA=NO,OPT=OPTI,CBKNAMB=YES;
Call Forwarding
Call forwarding can be configured on any device of the Personal Device Group.
The feature is activated for both devices and the signaling (Display, LED) is done
on both devices.
Call Forwarding can be activated for the Personal Device Group number using
the following ways:
• Cordless / desktop device menu
• AMO ACTDA / AMO ZIEL for the Personal Device Group number
• ACL Feature ACT Deact Service on CTI interface
Call Forwarding will be activated for the Personal Device Group number: If a
device calls the Personal Device Group number the call will be forwarded to the
forwarding destination and none of the Personal Device Group devices (desktop
or cordless) will ring.
If the Personal Device Group device has a Call Forward busy activated then the
call is forwarded to the CFW destination, e.g. digite device, Attendant, Voice Mail
in case of the Personal Device Group number is busy. Therefore either the
cordless device is busy or the desktop phone is busy using the Personal Device
Group number.
Call Forwarding can be activated/deactivated on any of the Personal Device

Group devices.
Please refer also to Basic Call.
Camp On
Automatic camp on can be activated /deactivated on any of the Personal Device

Group devices. Manual Camp On (caller activates camp on) is not supported.
Automatic Camp On has to be activated on both devices (Personal Device Group

master and slave). This is automatically done synchronously if one of the devices
activates or deactivates the feature.
If an incoming second call is calling the Personal Device Group it will camp on the
active device only (the one using actually the Personal Device Group line). Camp
on is not signaled on the second device of the Personal Device Group.
A31003-H3170-S103-6-7620, 02/2019
Service Information
Call Log / Call Journal
The local Call Log functionality does not support Personal Device Group. It must
not be used. To offer call log and phonebook only DTB is allowed. This application
supports the same call log and phone book entries on both devices.
In the next step of the „Personal Device Group“ feature a solution without DTB
will be implemented!
Call Pickup
The Personal Device Group number can be configured to be a member of a call

pickup group.
The incoming calls to another device in the call pickup group can be picked up by
any member of the Personal Device Group (cordless and desktop phone).
The incoming calls to the Personal Device Group number can be picked up by
any other member of the call pickup group.
Configuration:
Add twincmi and twinopti to the pick up group as any usual extension number.
Call features during an active call
The following call features are supported by the cordless device during an active
call:
• Consultation
• Transfer
• Toggle
• Conference
Park / Hold
An active call (that is in call state) can be put on hold the following ways:
• by selecting Halten/Hold in the phone menu (cordless phone, desktop

phone).
• by pressing the line key (desktop phone).
A31003-H3170-S103-6-7620, 02/2019
Service Information
This call can be retrieved by the desktop phone by pressing the blinking line key
belonging to the phone.
Restriction:
The cordless phone cannot retrieve a call that has been put on hold this way.
Configuration:
The park timer can be set with the following AMO configuration:
CHANGE-CTIME:TYPESWU=CP1,CTHLDREC=<timer to control the duration
of a manual hold of a call>;
If the timer has expired the Personal Device Group will be ring back and both
member of Personal Device Group can accept the call.
Hunt groups
Personal Device Group can be a member of the hunt group. The twincmi must be
added to the hunt group by using AMO SA.
When the hunt group routes an incoming call to the Personal Device Group
number, both Personal Device Group devices start ringing and any of the
Personal Device Group devices can answer the call.
Do not disturb
Do not disturb can be activated/deactivated on any device of the Personal Device

Group. The signaling (based on device possibilities) is done on both devices of
the Personal Device Group.
CHESE
Chese functionality is not supported.
Timed Reminder
Timed Reminder is supported with Personal Device Group.
Speed Dial List (SPDI)
Speed dial list can be used on both devices of the Personal Device Group. Both
devices use the same short calling list, i.e. changing the short challing list on one
of the devices will be visible also on the other device.
A31003-H3170-S103-6-7620, 02/2019
Service Information
When configuring the short calling list using AMO ZIEL, parameter SPDI, the
same configuration has to be done for both twincmi and twinopti.
Ringer Cut Off
For ringer cutoff two keys can be configured on the desktop phone of the Personal
Device Group:
• ringer cutoff for desktop phone
• ringer cutoff for CMI phone
Desktop phone
When ringer cutoff is activated for the desktop phone, incoming calls to the
Personal Device Group number are indicated in the following way:
• On the cordless phone the call is indicated as if ringer cutoff was not active
• On the desktop phone there is no ringing / display update. Only the blinking
line key indicates the call.
Cordless phone
When ringer cutoff is activated for the cordless phone, incoming calls to the
Personal Device Group number are indicated in the following way:
• On the cordless phone the call is absolutely not indicated. Note that during
such a call attempt the cordless phone seems “idle” however it is not possible
to initiate outgoing calls using this device.
• On the desktop phone the call is indicated as if ringer cutoff was not active.
Configuration:
CHANGE-TAPRO:STNO=twincmi,KY08=RNGXFERL; /*CMI*/
CHANGE-TAPRO:STNO=twincmi,KY12=RNGXFERL; /*CMI*/
CHANGE-TAPRO:STNO=twinopti,KYx=RNGXFERL; 
CHANGE-TAPRO:STNO=twinopti,KYx=RNGXFERL;
CHANGE-SDAT:STNO=twincmi,TYPE=ATTRIBUT,AATTR=RNGXFERL;
CHANGE-SDAT:STNO=twinopti,TYPE=ATTRIBUT,AATTR=RNGXFERL;
ADD-
ZIELN:STNO=twincmi,TYPE=RNGXFERL,KYNO=8,STNORXFR=twincmi,RXFRFC
T=SRC;
ADD-
ZIELN:STNO=twincmi,TYPE=RNGXFERL,KYNO=12,STNORXFR=twinopti,RXF
RFCT=DEST;
ADD-
ZIELN:STNO=twinopti,TYPE=RNGXFERL,KYNO=x,STNORXFR=twincmi,RXFR
FCT=DEST;
ADD-
ZIELN:STNO=twinopti,TYPE=RNGXFERL,KYNO=x,STNORXFR=twinopti,RXF
RFCT=SRC;
A31003-H3170-S103-6-7620, 02/2019
Service Information
Direct Station Selection (DSS) Key
If one of the devices has a configured DSS Key with configured destination of the
Personal Device Group on the DSS key the busy condition of the Personal Device
Group is displayed via a LED.
If the Personal Device Group is called despite being busy, call waiting is
automatically activated.
By pressing the flashing DSS key while the Personal Device Group is being
called, it is possible to take the call if the calling party and the Personal Device
Group are in the same pickup group.
Restriction:
A DSS key can only be configured on the desktop phone of a Personal Device
Group.
Class of Service (COS) Switchover (AMO BERUM)
The class of service switchover feature can be activated and deactivated either
on the desktop or on the cordless phone.
The Class of Service will be changed for Personal Device Group number and can
be queried using AMO BERUM.
The desktop and the cordless phone must be in the same COS group. When
doing AMO configuration both twincmi and twinopti has to be configured the same
way.
Keyset
A Personal Device Group must not be combined with other Keysets. The CMI is
only allowed to have one line configured and for the desktop phone exactly two
lines are required (own prime line and Personal Device Group number as
secondary line).
CDRE
CDRE is supported for devices of the Personal Device Group. In the accounting
tickets the Personal Device Group number (twincmi) will be reported as paying
party.
A31003-H3170-S103-6-7620, 02/2019
Service Information
SPE
SPE is supported for devices of a Personal Device Group. Both twincmi and
twinopti must be configured for the same security level.
CTI / ACL functionalities:
ACL Monitoring
In monitor events always the Personal Device Group extension number (twincmi)
is reported.
ACL Services
ACL services which support the Personal Device Group number:
• Service Comment
• Alternate-Call-Request
• Clear-Connection-Request
• Callback-Request
• Cancel-Callback-Request
• Conference-Call-Request
• Consult-Call-Request
• Deflect-Call-Request
• Dial-Digits-Request
• Divert-Call-Request
• Feature-act/deact-Request
• Feature-Status-Request
• Generate-Digits-Request
• Generate-Telephony-Tone-Request
• Make-Call-Request
Restriction: Not working for a Personal Device Group.
• Make-Predictive-Call-Request
• Reconnect-Call-Request
• Single-Step-Transfer-Call-Request
• Transfer-Call-Request
• Device Type Check CMI is reported for the Personal Device Group number.
A31003-H3170-S103-6-7620, 02/2019
Service Information
• Get-Switching-Funct-Devices
New device type „Personal Device Group“ is reported for twinning number.
• Monitor Set/Cancel
• Snapshot-monitor
• Snapshot-call
• I/O services
The Personal Device Group number is to be used to access the CMI. Primary
line extension number of desktop phone is to be used to access the desktop
phone.
• Set-Lamp-Mode
The Personal Device Group number is to be used to access the CMI. Primary
line extension number of desktop phone is to be used to access the desktop
phone.
• Answer-call-Request It is working only for the desktop phone.
• Hold-Call-Request Service is disabled.
• Retrieve-Call-Request Service is disabled.
• Invoke-Feature Service is disabled.
• Button-Press-Request Service is disabled.
• Escape services Service is disabled.
The other ACL services that are not present in the list above are not directly
affected by Personal Device Group.
Restrictions:
• The service disabling is working, if the configuration is not correct e.g:
A desktop phone is configured with AMO KCSU as Personal Device Group
device, but there is not any CMI (configured as Personal Device Group
master) to assign to this desktop phone. In this case the service will be
disabled for desktop phone.
• ACL Make Call Service is not working for a Personal Device Group.
Corresponding applications
CA4000 standalone version

Version CA4000 standalone Version 7.1.4.2
A31003-H3170-S103-6-7620, 02/2019
If an older version of the CA4000 standalone is installed on the PC, then it must
be removed and replaced with this version!
IMPORTANT: If the configuration of the „Personal Device Group“ feature is

changed then the CA4000 must be restarted to provide the needed functionality
regarding this feature.
DTB
The following version of DTB supports the Personal Device Group:
DTB V9.0 R19.0.2
This application supports the same call log and phone book entries on both
devices of the Personal Device Group.
BLF
The BLF-Win application supports the Personal Device Group number.
In case of Personal Device Group only the „master number“ should be entered at
the BLF-Win grid, because the informations for the „slave number“ may be wrong.

The configuration example shows how to configure a Personal Device Group.
The CMI (master) member of the group will be represented by the symbolic
extension number “twincmi”. The optiPoint (slave) member of the group will be
represented by the symbolic extension number “twinopti”.
While doing the actual configuration both “twincmi” and “twinopti” must be
replaced by the actual extension number.
IMPORTANT: On the Personal Device Group master (CMI) device the key layout
is important! The Check key should not be overwritten by any line-key, otherwise
the callback entries of the callback list and the entries in the mailbox list of the
CMI and are no more visible.
CHANGE-
TAPRO:STNO=twincmi,DIGTYP=OPENST10,KY01=CH,KY02=CBK,KY03=C
ONS,KY04=SPKR,KY05=RLS,KY06=PU,KY07=MB,KY08=RNGXFERL,KY09=
NAME,KY10=CL,KY11=LINE,KY12=RNGXFERL; /*CMI*/
ADD-KCSU:STNO=twincmi,TYPE=PRIM,PRIMKEY=11,TWINNING=YES; /
*CMI*/
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
CHANGE-
TAPRO:STNO=twinopti,DIGTYP=OPENST10,KY01=LINE,KY02=LINE; /
*DIGITE*/
ADD-
KCSU:STNO=twinopti,TYPE=PRIM,PRIMKEY=1,ORLNPF=LAST,TWINNIN
G=YES; /*DIGITE*/
ADD-
KCSU:STNO=twinopti,TYPE=SEK,KYNO=2,STNOSEC=twincmi,RIOP=YE
S; /*DIGITE*/
CHANGE-ZAND:TYPE=KEYSYS,DISLNBAS=YES;
88.4 Relevant AMOs

Language
COSSU ESBER=BRK d Sprachberechtigung: Briefkasten (Ausle-
seberechtigung)
AVCE=MB e Voice Classmark: mail box (authorization
to receive mail)
CTIME KDHLDREC d Timer für die Dauer des manuellen
haltens des Gesprächs
CTHLDREC e Timer to control the duration of a manual
hold of a call
KCSU TWINNING d Personal Device Group fuer CMI Geraete
aktivieren
TWINNING e Activate Personal Device Group for CMI
devices
SBCSU TLNNU d Teilnehmernummer des CMI / Desktop-
Endgerätes
STNO e Station number of the CMI / desktop
phone
RRFBK d Rückruf im Freifall wird im Briefkasten
abgelegt/nicht abgelegt
CBKNAMB e Call back on no answer is stored / not
stored in the mailbox
SDAT EMERK=RULEITNG d Rufumschaltung der Leitung erwünscht
AATTR=RNGXFERL e Ring transfer for line desired
TAPRO TLNNU d Teilnehmernummer des CMI / Desktop-
Endgerätes
STNO e Station number of the CMI / desktop
phone
TD*=RULEITNG d Rufumschaltung für Leitung
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

Language
KY*=RNGXFERL e ring transfer (for executive/secretary) key
ZAND ANZLNBAS d Rufnummer und Name der aktiven Line
anzeigen anstatt die des zugeordneten
Gerätes.
DISLNBAS e Display station number and subcriber
name belonging to the line appearance
instead of those belonging to the device
hosting the line appearance
ZIELN TYP=RULEITNG d Rufumschaltetaste für Leitungen
TYPE=RNGXFERL e Ring transfer key for lines
RNRRU d Rufumschaltungsziel / -quelle für
Leitungen: Teilnehmernummer des CMI /
Desktop-Endgerätes
STNORXFR e Ring transfer destination / source for lines
RUFUNKT d Ziel/Quelle der Rufumschaltetaste für
Leitungen
RXFRFCT e Function of ring transfer key for lines
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
broadcast_en.fm
Overview
89 Speaker Call - One-Way - Broadcast
89.1 Overview
With the speaker call Broadcast function it is possible to allow the broadcast to
multiple loudspeakers.
Log Off the network

Please
Broadcast call to a
specified line
Log Off the network

Please
Line apperance not set to ring
I.S.Department
Voice Call Protection is set
The Loudspeakers are turned on at all

stations where the called line is set to Log Off the network
ring Please
MAX 40 Keysets

This feature provides the capability to allow an Analog telephone, Digital Feature
Telephone (DFT) or Keyset user to initiate a speaker call with a one-way
connection to multiple (maximum 40 keysets) keyset destinations,
simultaneously.
Upon one of the destinations answering the Broadcast (by lifting the handset),
that user can privately converse with the originator of the Broadcast.
A31003-H3170-S103-6-7620, 02/2019
broadcast_en.fm
User Interface
89.3 User Interface

• The user may either depress a key (BROADCST) or dial an access code
(BROADCST), followed by dialing a destination extension number, to initiate
a Broadcast call. A one-way connection shall immediately be established
between the user and up to 40 keysets which have a line appearance of the
dialed destination and meet the following criteria:
• The line appearance on the telephone is configured to ring.
• The station user is not busy, not off-hook, not in hands-free operation, or
is not in program mode.
• The destination is not marked for voice call protection.In default this is on.
• The station is not restricted from terminating to that destination (e.g. ITR
Internal Traffic Restriction).
• An external dial tone shall alert the originator that the one-way connections
have been established, and that the one-way Broadcast can begin.
• The Broadcast connection shall be converted to a single two-way connection

upon any active Broadcast destination’s going off hook, via the handset only.
The two-way connection shall be established between the party that initiated
the call and the first party that went off hook. All other parties will be released
from the call.
• A Speaker Call -- One-way - Broadcast call can be initiated by an analog or

digital telephone.
• When a destination party presses the speaker key, the party will be
disconnected from the Broadcast (speaker turned off). If the last party
presses the speaker key, the call will be disconnected.
• When a destination party presses a line key (either the one on which the
Broadcast is pending, or any other line key), the party will be disconnected
from the Broadcast (speaker turned off). If the last party presses a line key,
the call will be disconnected.
• The number of simultaneous Speaker Call -- One-way - Broadcasts is 10 with

40 members each.
• The destination parties receive a momentary burst of ringing and the calling
party remains on the display of the destination parties.

The Speaker Call - One-Way - Broadcast call feature is intended for the global
marketplace.
A31003-H3170-S103-6-7620, 02/2019
broadcast_en.fm

• How to configure the originating station to have access to the Broadcast
feature:
CHA-SDAT:STNO=7445,TYPE=ATTRIBUT,AATTR=BROADCST;
• Add the digits for dial access to the Broadcast feature:
ADD-WABE:CD=*51,DAR=BROADCST;
• Add the Broadcast key to a phone:
CHA-TAPRO:STNO=7445,KY08=BROADCST;
89.6 Relevant AMOs

WABE BROADCST d rundspruch
TAPRO BROADCST rundspruch
SDAT BROADCST d rundspruch
A31003-H3170-S103-6-7620, 02/2019
broadcast_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
fax_en.fm
Fax Machine
Non Voice
Non Voice
90 Fax Machine

A fax machine can be configured either as an analog terminal linked to an SLMA
module or via an analog adapter at the UP0/E connection, or as a digital terminal
linked to an S0 bus. Assign the fax machine a combination call number under
which it is generally accessible. The connection is thus a fax connection (FAX
service).

At the UP0/E connection, a fax machine can be configured via an analog adapter.
IMPORTANT: The fax machine can be accessed internally or externally by

means of combination call number (4444) or by the fax code and station number
(4321). Since the latter of these alternatives usually results in an unduly long digit
sequence for external callers, the combination number must be used. 
In the case of calls from an ISDN fax machine, the called station must be
configured as a fax terminal.

• Create digit analysis result:
ADD-WABE:CD=key-num,DAR=FAX;
• Create digit analysis result for the combination call number:
ADD-WABE:CD=4444,DAR=FAXNO;
• Create a fax machine linked to the SLMA module as follows:
ADD-
SCSU:STNO=4321,DVCFIG=ANATE&FAX,DPLN=number,ITR=number,
COS1=number,COS2=number,LCOSV1=number,LCOSV2=number,LCOSD1
=number, LCOSD2=number;
• Create digit translation:
A31003-H3170-S103-6-7620, 02/2019
fax_en.fm
Fax Machine
Relevant AMOs
The combination call number (FAXNO) is linked to the internal call number of
the fax machine.
ADD-RUFUM:TYPE=COMB,FAX1=4444,FAX2=4321;
90.4 Relevant AMOs

Language
RUFUM TYP d Verzweigungsparameter
TYPE e desired conversion table
FAX1 d externe FAX-Rufnummer
FAX1 e externally dialled facsimile access code
FAX2 d interne Rufnummer mit FAX-Anschluss
FAX2 e facsimile internal access code
KZP d Kennzahlpunkt
WABE d Wabegruppe
A31003-H3170-S103-6-7620, 02/2019
rufum_en.fm
Number Conversion
Feature Description
91 Number Conversion
Analog exch. ISDN

digital exch.
Combi. code
A B
Stn.
Fax
(5711)
A = Direct inward dialing (DID)
B = Direct dialing-in (DDI/DID) with service indicator
Figure 106 Number conversion
Indialed digit sequences are converted in the following cases:
• Station numbers between 1 and 6 digits (AMO WABE, DAR=STN). 

The dialed number must always be converted to an assigned station number.
• Conversion of call numbers from the IDN network (1 to 4 digits) (AMO WABE,
DAR=STN) 
???Conversion is necessary if the internal numbering of the relevant TTX or
DTE devices contains more digits than the station number dialed by the IDN
network.
• Combination codes for FAX, DTE (AMO WABE, DAR=FAXNO/DTENO). 

These must be configured in the digit analysis if the service code plus station
number in the system contains more than six digits and the service should be
accessible from an external location over the exchange, because only six-
digit (max.) station numbers are supported for external access. Conversion is
always necessary in this case.
A31003-H3170-S103-6-7620, 02/2019
rufum_en.fm
Number Conversion
Example of Station Number Conversion
The prerequisite is that the access code to which the conversion is to occur is
already assigned and is compatible with the code to be converted (service, etc.).
There must be no STN configured for the station number to be converted but it
must be applied to the DAR STN in the AMO WABE.
IMPORTANT: ADD and CHANGE are performed in the same manner because
the AMO RUFUM simply overwrites configured entries in the case of a new add
command. 
Station number:- conversion
91.2 Example of Station Number Conversion

• Configure the code(s) with:
ADD-WABE:CD=7144,DAR=STN; 
ADD-WABE:CD=7145,DAR=STN; /* STN still to be added */
IMPORTANT: The code can only be assigned for the CPS 6 and 7
(exchange indial). This means it can be assigned to other DARs in different
CPSs. If TYPE= DID is set, the AMO RUFUM only checks for the STN DAR
and will accept any CPS.
• Configure number conversion as follows:

ADD-RUFUM:TYPE=DID,DID1=7144, DID2=7145;
DID1 = direct inward dialing number 
DID2 = station number to be converted to (station must be assigned under
this number)
91.3 Combination Code (FAX, DTE)

• Configure the DAR in the DPLN as follows:
Combination code for FAX
ADD-WABE:CD=key-num,DAR=FAXNO;
or
Combination code for DTE
ADD-WABE:CD=key-num,DAR=DTENO;
• Configure number conversion as follows:
ADD-RUFUM:TYPE=COMB,FAX1=number,FAX2=number; or 
ADD-RUFUM:TYPE=COMB,DTE1=number,DTE2=number;
A31003-H3170-S103-6-7620, 02/2019
rufum_en.fm
Number Conversion
Relevant AMOs
FAX1, DTE1 correspond to the combination codes (FAXNO, DTENO) in digit

analysis. 
FAX2, DTE2 correspond to the station numbers of the devices in OpenScape
4000
IMPORTANT: Conversion is not possible if the station numbers are identical

in the AMO RUFUM, for example, for the parameters FAX1 and FAX2. It is
not necessary either because dialing the combination code always sets up a
connection to the device with the same station number. 
All you have to do is set the station number 4711 to DAR=FAXNO under CPS
6 in WABE and set 4711 to DAR=STN for the other CPSs. If the fax device is
configured under 4711, it is reached (even if number conversion is not
performed) by dialing 4711 in CPS 6 (exchange indial) under DAR=FAXNO.
91.4 Relevant AMOs

Language
TYPE e desired conversion table
DUWA1 d externe Durchwahlrufnummer
DID1 e direct digit indial number
DUWA2 d interne Rufnummer (fuer Durchwahl)
DID2 e internal destination number (for indial)
DEE1 d externe DEE-Rufnummer
DTE1 e externally dialled data terminal equipment
access code
DEE2 d interne Rufnummer mit DEE-Anschluss
DTE2 e data terminal equipment internal access code
FAX1 d externe FAX-Rufnummer
FAX1 e externally dialled facsimile access code
FAX2 d interne Rufnummer mit FAX-Anschluss
FAX2 e facsimile internal access code
KZP d Kennzahlpunkt
WABE d Wabegruppe
A31003-H3170-S103-6-7620, 02/2019
rufum_en.fm
Number Conversion
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
ani_en.fm
Terminals
Terminals
92 Automatic Number Identification (ANI)

Up to now the phone number of the caller wasn't shown at the called party, after
remote transfer out of PhoneMail. In case of remote transfer (CorNet-N) and if
COT-Parameter ANDY is set, then the redirectin number (REDIRECTING_NUM)
is exchanged to the called number (CALLED_NUM).
Scenario
PRI Trunks come into System A with ANI from phone company.
Call rings an extension in System A. Phone is ring no answer forwarded into

PhoneMail (Which is in System B). Caller does 0# to transfer out of PhoneMail
and ring another extension in System A. Person Answers phone. Caller is now
connected. The person answering the phone gets the ANI of the caller.

Prerequisites
The feature is only available with CorNet-N / CorNet-US protocol variant.
92.3 Generation
CHANGE-COT:<cot-no>,COTTYPE=COTADD,PAR=ANDY;
92.4 Relevant AMOs

Language
COT ANDY d ANI delivery in gemischten Netzen
ANDY e ANI delivery in mixed networks
A31003-H3170-S103-6-7620, 02/2019
ani_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
autosetr_en.fm
Autoset Relocate
General Information
93 Autoset Relocate

The Autoset Relocate feature allows users to move their telephones to different
locations within the same PABX (i.e. same node in network systems), as required.
Anates and UP0 terminals are supported
Users can "sign off" their telephones by dialling an appropriate code followed by
their PIN number (only at their own telephone), and can, similarly, "sign on" at any
suitable free location (PEN) in the system. The users class of service, group
memberships and activated telephone features remain unchanged.
Service engineers can relocate any telephone in a system as follows:
Signing off
• Via dial-up procedure at any suitable telephone in the system (sign off code
followed by station number of telephone to be relocated) or
• via dial-up procedure at any suitable telephone in the system (service code
followed by station number of telephone to be relocated) or
• via the service terminal (with the device switch et-relocate DSSU).
Signing on
• Via dial-up procedure at the relocated telephone (sign on code followed by
station number of relocated telephone) or
• via dial-up procedure at the relocated telephone (service code followed by

station number of relocated telephone) or
• via the service terminal with AMO DSSU.
IMPORTANT: The signing on procedure cannot be entered at at remote

telephone.
Service Terminal
In addition, the following operations can also be carried out at the service
terminal:
• Users/stations can be configured with AMO SCSU / AMO SBCSU in signed

off status
• Configured, free (i.e. not occupied) PENs can be signed offf with AMO BCSU
• PENs which are signed off can be re-enabled (signed on) with AMO BCSU
A31003-H3170-S103-6-7620, 02/2019
autosetr_en.fm
Autoset Relocate
General Information
• Users/stations which are signed off can be displayed with AMO SCSU or
AMO SBCSU, depending on the device type. All users can be displayed
regardless of device type with AMO SDSU.
• PENs which are signed off can be displayed with AMO BCSU and AMO
SDSU
The sign off and sign on procedures are functionally seperate procedures, i.e. a
service engineer can sign off a telephone via AMO and the user can sign on via
the telephone dial-up procedure or vice-versa, as required.
service code
The service code is a special user-independent service PIN, which is

administered with AMO PERSI.
93.1.1 Terms Used

• Signed off user:
A signed off station is a station to which no pen (module) is assigned. From
a security point of view the status is SIGNED_OFF. In this status the station
cannot be reached and cannot execute any action itself with the exception of
the following functions:
– It can sign in on a suitable terminal on a signed signed off pen.
– It can make an emergency call by entering a specified emergency

number.
Its class of service, group membership etc. remain unchanged. A previously
activated FWD remains active.
• Signed on user:
A signed on user is a user configuration properly assigned to an enabled
PEN. The dependability status SIGNED_OFF is not set.
• ID card user:
An ID card user (anates) is a user without a specific telephone. These users
identify themselves by means of their ID card and their PIN at any suitable
stations/telephones in the system. Depending on the type of telephone used,
such users may not always be able to access the entire range of features for
which they are authorized. The device at which an ID card user identifies
himself or herself remains configured under its original station number, and is
administered with this number.
• Identified ID card user:
A31003-H3170-S103-6-7620, 02/2019
autosetr_en.fm
Autoset Relocate
General Information
An identified ID card user is an ID card user who has identified himself/herself

at a suitable telephone assigned to an enabled PEN. Such a user is regarded
by the system as a standard, signed on telephone user in all respects, except
that no group memberships (e.g. PU-group or CHESE group) are possible.
These users sign off by removing the ID card from the card reader. However,
ID card users are not placed in SIGNED_OFF status.
• Signed off PEN:

PENs with the CONNECTION_TYPE "SIGNED_OFF". For multiple device
PENs, the dependability status of a circuit will be MULTIPLE_LINE, and only
the CONNECTION_TYPE of the individual TSIs will be SIGNED_OFF (c.f.
DISPLAY-SDSU, DISPLAY-BCSU).
• Enabled PEN:
PENs with a CONNECTION_TYPE other than "SIGNED_OFF". For boards
with multiple-device PENs, the CONNECTION_TYPE of the circuit will
always be MULTIPLE_LINE, whereas the TSIs can be free, signed off or
assigned.
93.1.2 Prerequisites for Signing Off and On

1. Requirements for signing off:
• The device type and configuration (e.g. bus) must support the autoset
relocate function (see Section 93.2.1, “Anate” and Section 93.2.2, “Digital
System Telephone (without second Telephone)”).
• The telephone to be relocated must be configured and in operation (if sign off
procedure is entered at the same telephone). If the sign off procedure is
entered at a different telephone or via the service terminal, the telephone to
be relocated does not need to be in operation.
2. Requirements for signing on:
• The relocated telephone, and the PEN at which it is to be signed on, must
be signed off (ID card users cannot sign on at two different telephones/
PENs anyway, see Section 93.1.1, “Terms Used”).
• The type of PEN must be suitable for the user configuration to be signed
on.
The sign off procedure not only signs off a user configuration, but also the PEN
to which it is assigned.
IMPORTANT: Users can only sign on a relocated telephone at a suitable PEN

for the user configuration concerned.
A31003-H3170-S103-6-7620, 02/2019
autosetr_en.fm
Autoset Relocate
Devices and Configurations which support Autoset Relocate
93.2 Devices and Configurations which support Autoset Relocate
93.2.1 Anate
Anates can be signed off and signed on , provided they are configured as follows:
1. Anates as individual telephones (i.e. not associated with other devices);
2. Anates with card readers (ID card user can only sign on);
3. Anates with associated FAX/DTEANA;
IMPORTANT: Anates can only be signed off if configured with the parameter
DIAL = VAR (variable). Anates which are configured for pulse dialling or DTMF
dialling must be appropriately reconfigured with AMO SCSU, if the board
supports the dialling type.
93.2.2 Digital System Telephone (without second

Telephone)
• If two terminals are connected to the same line, a strict relocate sequence
must be adhered to first, the terminator must be relocated and then the
repeater can be relocated
• If a functional terminal or CorNet terminal is connected to the Digital system-

or IP-telephone via an S0 adapter, the digital phone must be relocated last.
93.3 Devices which do not support Autoset Relocate

• HiPath Tradeboard
• HiPath Executive
• Terminals associated with other terminals
• Terminals configured under the main number of an S0 bus, if other terminals

are connected under the same number.
• Functional terminals in an S0 bus configuration.
• IP terminals and IP softclients
A31003-H3170-S103-6-7620, 02/2019
autosetr_en.fm
Autoset Relocate
AMOs Usage Examples for Autoset Relocate
93.4 AMOs Usage Examples for Autoset Relocate
93.4.1 Preparations
In order to be able to activate the feature from a suitable terminal, the following
conditions must be created first:
• The feature must be enabled.

DISPLAY-FEASU;
RELOCATE must be listed among the activated features.
If not, enable the feature with AMO FEASU:
CHA-FEASU:TYPE=A,CM=RELOCATE;
• Sign off and sign on code must be assigned.
DISPLAY-WABE:TYPE=GEN,DAR=SIGNOFF&SIGNON;
Assign sign off and sign on codes with AMO WABE:
ADD-
WABE:CD=<kkkkkk>,DAR=SIGNOFF,CDDP=<kkkkkk>,CD2=<nnnnnn>,CDDP2
=<nnnnnn>;
CDDP is the code for pulse dialling, i.e. without “*“ and “#“ keys,
CD2 is the code for the partner DAR ( = SIGNON)
CDDP2 is the code for pulse dialling for the partner DAR.
• PIN1 and PIN8 (service code) must be assigned.

DISPLAY-PERSI:TYPE=STN,STNO=<nnnnnn>; (PIN1 is used for Autoset
Relocate)
DISPLAY-PERSI:TYPE=PIN,PINTYPE=8; ( PIN8 = service code)
Assign PIN1 with AMO PERSI:
ADD-PERSI:TYPE=STN,STNO=<nnnnnn>,PIN1=<nnnnnnnn>;
Assign service code with AMO PERSI:
ADD-PERSI:TYPE=SI,SI=<nnnnnnnn>;
These conditions are not necessary for signing off and signing on via AMO.
93.4.2 Signing Off and On via AMO
93.4.2.1 Signing off with DSSU AMO
CHA-DSSU:TYPE=SIGNOFF,STNO=<nnnnnn>;
A31003-H3170-S103-6-7620, 02/2019
autosetr_en.fm
Autoset Relocate
93.4.2.2 Signing on with AMO DSSU
CHA-DSSU:TYPE=SIGNON,STNO=<nnnnnn>,PEN=<nn-nn-nnn-nn>
[,TSI=<nn>];
IMPORTANT: The TSI (Terminal Selection Identifier) parameter only applies for
optiPoint configurations. In optiPoint configurations, the first optiPoint telephone
is automatically assigned the TSI 1, and the second is assigned on the remaining
TSI, which is intend for optiPoint .
The specified PEN must be located on the correct board type for the telephone
concerned. The following table shows which boards are suitable for the individual
device types:
Device Board(s)
optiPoint SLMO, SLMQ
OpenStage TDM SLMO24/SLMOP
The AMO BCSUprovides information on PENs or board types, as follows:
Boards:
DISPLAY-BCSU:TYPE=TBL,LTG=<nn>,LTU=<nn>,SLOT=<nnn>;
Column 2 of the display output shows whether the PEN is free, assigned or
signed off. Signed off users can only be signed on at signed off PENs (or signed
off TSIs). If a signed off user needs to be signed on at a free PEN, the free PEN
must first be signed off with AMO BCSU (see Section 93.4.3.1, “Signing Off a
Free PEN (or TSI) with AMO BCSU”).
The AMO SDSU provides more detailed information on the status of the individual
PENs (see Section 93.4.5.3, “Display Signed Off Users and PENs with AMO
SDSU”).
93.4.3 Signing Off and Enabling PENs

For SLMA and SLMB boards, the entire circuit is signed off or enabled, i.e. is
ignored. For board types with multiple lines assigned to each circuit (SLMO,
SLMQ), the TSI parameter is required in order to identify the precise user
configuration to be signed off or signed on.
93.4.3.1 Signing Off a Free PEN (or TSI) with AMO BCSU
CHANGE-
BCSU:TYPE=SIGNOFF,[LTG=<nn>],LTU=<nn>,[SLOT=<nnn>,][TSI=<nn>];
A31003-H3170-S103-6-7620, 02/2019
autosetr_en.fm
Autoset Relocate
93.4.3.2 Enabling a Signed Off PEN (or TSI) with AMO BCSU
CHANGE-
BCSU:TYPE=RELEASE,[LTG=<nn>],LTU=<nn>,[SLOT=<nnn>],[TSI=<nn>];
93.4.4 Configuring Users/Stations with SIGNED_OFF

Status (without PEN)
Anate
AMO SCSU
optiPoint 500, OpenStage TDM

AMO SBCSU
ADD command, with parameter INS=SIGNOFF

Examples:
1. Configure an Anate with the station number 2224 with SIGNED_OFF status
via SCSU:
ADD-
SCSU:STNO=2224,DVCFIG=ANATE,...,DIAL=VAR,...,INS=SIGNOFF,...;
2. Configure an OpenStage TDM with the station number 3720 as first optiset E
with SIGNED_OFF status via SBCSU:
ADD-
SBCSU:STNO=3720,OPT=OPTI,CONN=DIR,DVCFIG=OPTISET,...,INS=SIGN
OFF,...;
93.4.5 Display Signed Off Users and PENs
93.4.5.1 Display Signed Off Users with AMO SCSU / AMO

SBCSU
• Anate telephones:
DISPLAY-SCSU:[STNO=<nnnnnn&&nnnnnn>,]TYPE=ATTR,ATTR=SIGNOFF;
• digital telephones:
DISPLAY-SBCSU:[STNO=<nnnnnn&&nnnnnn>,]TYPE=SIGNOFF;
93.4.5.2 Display Signed Off PENs with AMO BCSU
DISPLAY-BCSU:TYPE=PEN,[LTG=<nn>],[LTU=<nn>].[SLOT=<nnn>];
A31003-H3170-S103-6-7620, 02/2019
autosetr_en.fm
Autoset Relocate
All the PENs and TSIs (for multiple line circuits) are displayed, together with the
appropriate status information (FREE, ASSIGNED, SIGNED OFF)
93.4.5.3 Display Signed Off Users and PENs with AMO SDSU
• Users/telephones:
DISPLAY-
SDSU:[STATUS=SIGNOFF],TYPE=STNO,LEVEL=PER3,[STNO=<nnnnnn>],
[SVC=<si>];
• PENs:
DISPLAY-
SDSU:[STATUS=SIGNOFF],TYPE=PEN,LEVEL=PER3,[LTG=<nn>],[LTU=<nn
>],[SLOT=<nnn>];
If the STATUS parameter is not specified, the stations or PENs which are out of
service are displayed.
93.4.6 Emergency calls

If a user wants to make an emergency call from a signed off station ("signed off"
appears on the screen), when he lifts the receiver he is assigned a number for
this one emergency call from a number pool previously set up for this purpose.
The station makes the emergency call and hangs up again. The phone then
returns to its original state (automatic sign-off) without requiring any action by the
user.
Limitations
An emergency call cannot be made on signed-off analog terminals.
Prerequesites:
• The number pool must be configured (preferably using numbers not already
in use).
• The optional patch which determines the emergency number must be

activated.
Administration Number Pool

Configuration of maximum 25 stations in the "Signed off" state. This means a
maximum of 25 emergency calls can be made simultaneously from signed off
stations.
This stations cannot be keysets or ACD agents and cannot be member of a group
(e.g. pickup group, CHESE, hunt group, etc.).
ADD-WABE:CD=number,…..,DAR=STN;
EINR-WABE:RNR=nummer,…..,KZP=TLN;
A31003-H3170-S103-6-7620, 02/2019
autosetr_en.fm
Autoset Relocate
ADD-SBCSU:STNO=number,OPT=OPTI,…..,INS=SIGNOFF…..;
EINR-SBCSU:TLNNU=nummer,OPT=OPTI,…..,INBETR=ABGEM…;
CHANGE-SDAT:STNO=number,TYPE=ATTRIBUT,AATTR=EMERGPLN;
AEND-SDAT:TYP=MERKMAL,EMERK=NOTRFPLN;
New advisory message from AMO SDAT

F63: Only signed off subscribers can be configured to the pool of Emergency Call
numbers
F63: Es koennen nur abgemeldete Teilnehmer in den Notruf-Nummern-Pool

konfiguriert werden
F64: Only a maximum of 25 signed off subscribers can be configured to the pool
of Emergency Call numbers
F64: Es koennen nur max. 25 abgemeldete Teilnehmer in den Notruf-Nummern-

Pool konfiguriert werden
A31003-H3170-S103-6-7620, 02/2019
autosetr_en.fm
Autoset Relocate
A31003-H3170-S103-6-7620, 02/2019
baby_cm_en.fm
Babyphone
Feature Description
94 Babyphone

As soon as this feature is activated a room can be monitored from any telephone
configured in the same PBX. The feature is activated from the telephone in the
room that is to be monitored. For activation a code with a maximum of 21 digits
must be entered which may only be known to the activating person. Monitoring
remains active until the handset of the telephone in the monitored room is placed
on-hook or the loudspeaker is switched off. To activate the actual monitoring
process the telephone in the monitored room is called, then the feature code and
the secret code number can be entered. Only the receive channel is switched
through for monitoring purposes.

• This feature is not available network-wide.
• This feature cannot be centrally disabled or enabled.
94.3 User Interface and Operation
94.3.1 Activation
Take off the handset > dial the feature code > dial the code number ending with # .
94.3.2 Deactivation
Place the handset on-hook or switch off the loudspeaker.
94.3.3 Monitoring the room

From any telephone configured in the same PBX:
Call the station where the feature is activated.

After the busy tone dial BABYUEBW and enter the code number ending with #.
The receive channel is switched through after the positive acknowledgement
tone.
A31003-H3170-S103-6-7620, 02/2019
baby_cm_en.fm
Babyphone

You can configure a code for babyphone feature as follows:
You can only administer the digit analysis result BABYLSNG (with * or #) in
expert mode.
Expert mode > ComWin > Open ...< IP> using AMO (see AMO command).
Use the AMO WABE to configure the digit analysis result:

ADD-WABE:CD=**99,DAR=BABYLSNG;
94.5 Relevant AMOs

Language
WABE RNR d RUFNUMMER
CD e ACCESS CODE / STATION NUMBER
KZP d KENNZAHLPUNKT
DAR e DIGIT ANALYSIS RESULT
A31003-H3170-S103-6-7620, 02/2019
block_dial_en.fm
Block Dialing
Feature Description
95 Block Dialing

It is possible to enter call numbers and to modify them before dialing. The digits
are collected firstly but not yet evaluated by the system.
It is possible
• to delete digits in the selected string,
• to insert digits or
• to complete the string.
Start of the dialing:
• LCR-we timer is started with any entered digit and with timeout the call is
processed.
• With Ok key the call is started immediateately.

• Block-Dialing is possible in onhook and offhook state.
• During predialing now "DIAL ?" is shown in the display. The cursor is not
shown.
• +/- key are not relevant anymore.
• With the left key digits are deleted.
95.3 Generation
AMO LDPLN
The AMO LDPLN should be configured with call complete. That means the LCR
digit pattern has to be configured as 0-w-123-Z instead of 0-w-123-X.
This is important in case of using ANATE or Fax.
Activation:
CHANGE-ZANDE:TYPE=OPTISET,EDITDIAL=YES;
CHANGE-ZANDE:TYPE=DATENALL,SIPDIAL=YES;
A31003-H3170-S103-6-7620, 02/2019
block_dial_en.fm
Block Dialing
Relevant AMOs
95.4 Relevant AMOs

Language
LDPLN LWM d LCR-Wählmuster
(Z: für eine beliebige Ziffernfolge, gefolgt
von Timeout oder # (= Wahlendezeichen) )
(Z: for any digit sequence followed by
timeout or # (=end-of-dial character))
REMKZ d Remote Knotenkennzahl
REMAC e remote access code
REMGRUNU d Remote Gruppennummer
REMGRNO e remote group number
SIGNAL d Signalisierungsmodus (ALLE, KEINE, LED)
SIGNAL e signaling mode (ALL, NONE, LED)
REMSIGAB d Remote Signalisierung abgehend
REMSIGO e remote signaling outgoing
REMSIGAN d Remote Signalisierung ankommend
REMSIGI e remote signaling incoming
REMSIGPK d Remote Signalisierung fuer Parken
REMSIGPK e remote signaling for parking
COSSU SGAUN d Sperren der gezielten Anrufuebernahme
BDCP e blocking of directed call pickup
UUS1IM d Nutzung des Dienstes uus1 implizit
UUS1IM e use of user - user signaling 1 implicit
DIMSU REMAUNGR d Anzahl der AUN-Gruppen in fremden
Knoten
REMPUGR e number of pickup groups in remote nodes
COP ASEG d CorNet-NQ Facility Segmentierung
ausschalten
ASEG e switch off CorNet-NQ facility segmentation
COT ETSC d Nur ETSI USS3 protokollkonforme
Meldungen werden zugelassen
ETSC e UUS ETSI conform
NQPI d CorNet-NQ Pickup-Info nicht unterstützt
NQPI e CorNet-NQ Pickup-Info not supported.
NQNP d CorNet-NQ Netzweite Übernahme nicht
unterstützt.
NQNP e CorNet-NQ Network-wide Pick-up not
supported.
A31003-H3170-S103-6-7620, 02/2019
block_dial_en.fm
Block Dialing
Relevant AMOs

Language
UUS1 d User to user implizit (kommend)
UUS1 e UUS Service Class 1 (Connection Setup
Basic Call)
UUSC e Congestion Control for User-User Service
CTIME GPUNST d Netzweiter AUN TSC-Abbruch Timer
GPUNST e network-wide group pick-up tsc teardown
timer
UUS3T1 d Maximale Wartezeit auf eine
UUS3T1 e uus3 request started on called network
Zeiteinheit
UUS3T2 e uus3 info message started on net side
FEASU DIRAUN d Direkte Anrufübernahme
DIRCPCKP e directed call pick up
TDCSU UUSCCY d Anzahl von Meldungen die pro Zeiteinheit
aufgestockt wird.
UUSCCY e UUS congestion control Y
WABE AUNGANZ d Anzeige der Gruppen AUN Information
anfordern
PUGDIS e display group pickup information on request
AUNGEZ d Gezielte Anrufuebernahme
PUDIR e directed call pickup
ZAND UUS d DIVUUSUmlenkung erlaubt
NODIVUmlenkung verboten
DIVSUPUmlenkung abhängig von der
Berechtigung
UUS e User-User Signalling for DSS1 Devices
A31003-H3170-S103-6-7620, 02/2019
block_dial_en.fm
Block Dialing
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
buzz_en.fm
Buzz
Feature Description
96 Buzz
23455
23456
is called
BUZZ
23455
calling
23456
The Buzz feature makes it possible to alert a party without a speech connection.
The buzzed party gets an audible signal and the display shows the number and
name of the buzzing party. The originator's display shows number and name of
the buzzed party.
96.2 User Interface

The Buzz can be initiated by pressing the buzz key or by dialing an access code.
If the Buzz key is pressed the Buzz ring acknowledges the successfully signalling
of the buzzed party.
When the access code is dialed, the initiator gets a positive acknowledge tone.
In each case if the Buzz is not carried out, e.g. because there is no destination
administered or the target's status does not allow a Buzz, the initiating party gets
the display 'Buzz not possible'. If the Buzz was initiated by the access code, the
buzzing party gets the display and a negative acknowledge tone. The Buzz key
can be used nearly independant from the device status, e.g. while a call ist
established or while the telephone is ringing and further more situations. The
target device can be buzzed in almost the same manner. Multiple Buzz in a short
time can be initiated, especially if the Buzz key is used.
A31003-H3170-S103-6-7620, 02/2019
buzz_en.fm
Buzz
Service Information

• The Buzz can be performed on devices of the Optipoint and OptiSet E family
only. For other device types the Buzz request will rejected.
• The Buzz can be performed in the own node only.
• Only one Buzz destination is allowed for each party, but the same Buzz
destination for different parties is possible.

• Administer a Access Code for Buzz:
ADD-WABE:CD=< >,DAR=BUZZ;
• Administer the Buzz Key :
CHA-TAPRO:STNO=< >,DIGTYP=OPTIT12,KY12=BUZZ;
• Administer the Buzz Destinaion:
ADD-ZIEL:TYPE=BUZZ,SRCNO=< >,DESTNOBZ=< >;
96.5 Relevant AMOs

WABE BUZZ d rufen (warnton) einer bestimmten rufnummer
e alert (buzz) a target station
TAPRO BUZZ d buzz einer bestimmten rufnummer
e buzz a predetermined number
ZIEL BUZZ d buzz-ziel
e buzz destination
QLRUFNU d quellen-rn
SRCNO e station number of source
BUZRUFNU d ziel-rufnummer fuer buzz
DESTNOBZ e dest. no. for buzz
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
Feature Description
97 Call Forwarding

For each service (DTE, FAX, VOICE), you can assign a forwarding destination to
a phone number. You cannot assign a forwarding destination to attendant
consoles and special stations. The different criteria for call forwarding are
explained in the following.
There are three different types of forwarding:
• Variable Call Forwarding
• Fixed Call Forwarding
• System Call Forwarding
There are also the following types of call forwarding which are assigned to the
above-mentioned FWD types according to Table 58 on page 97, Forwarding
types. You can program destinations for these.
• Unconditional call forwarding (FWD/CFU)
• Call forwarding if busy (CFB)
• Call forwarding if no response after timeout (CFNR)
• Call forwarding if do not disturb (CFDND)
IMPORTANT: Call forwarding type CFDND:

Do-not-disturb is a separate feature that you activate with the do-not-disturb
button on the station device. If you want all calls to be forwarded in this state,
configure and activate a forwarding destination for SYSTEM in CFDND. This
forwarding runs only when do-not-disturb is activated.
Furthermore, there are two types of forwarding that do not have separate
destinations defined:
• Call deflection, forced forwarding (CD), always uses the CFNR destination.
(This type of forwarding allows you to activate the FWD action during the call
by pressing the FWD key or disconnect key on the telephone.)
• Delayed Call Forward Busy (DelCFB) always uses the CFB destination.
(This type of forwarding has only been implemented for optiPoint telephones
and requires the parameter DCFWBUSY. If this is set, camp-on automatically
occurs at busy stations that are called and, after some time has expired, call
forwarding on busy (CFB) occurs.)
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
Feature Description
Another possibility for some types of forwarding is to make a distinction based on

the type of incoming connection. For example, an external connection is
forwarded to a different destination than an internal incoming connection.
The following table illustrates the forwarding assignments
CFU CFB CFNR CFBNR CFDND

Variable INT -----
(IM and EXT GEN GEN GEN
US) GEN
Fixed ----- ----- ----- -----
(not US) GEN
System INT INT INT ------ INT

(IM and EXT EXT EXT EXT
US) GEN GEN GEN GEN
Table 58 Forwarding types
CFBNR defines only a common destination for CFB and CFNR but is not a
separate type of forwarding. "GEN" means the same destination for internal and
external calls.
IMPORTANT: For functional terminals according to DSS1 protocol, forwarded

calls that are programmed according to the protocol are shown under variable
forwarding. For this reason, it is also not restricted to only one variable forwarding
destination at a given time the way other station devices are (see Section 97.2.1,
“Variable Call Forwarding”)
Important Information for USA

In the USA, only the variable and system FWD types are used. To keep the fixed
FWD out of the station device interface, you must set the parameter for the user
interface without fixed forwarding in the central system data.
As a result:
• The system does not offer fixed FWD in the optiPoint menu
• No FWD information is displayed when in the idle state
• FWD-LED signaling also occurs for the variable CFB and CFNR
When the system is delivered, the parameter CFUI is set to "YES".
Destinations can be:

• Configured subscribers and MASTER HT for each service
• Hunt group code for each service
• Personal station number of attendant console on voice
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
User Interface
• Attendant console call queue (M key) only for voice
• Attendant group access code of attendant group
• Multiple code calling/paging with "meet me" (that is, you must configure
search code and attendant code)
• Announcement via TCOM (adapter set for special equipment)
• Server for the particular service
• External destinations
There must be an allowed connection from the subscriber or MASTER HT to the

call forwarding destination. With the parameter ITRFWD, you can centrally define
whether there should be a check of the connection from the caller to the
forwarding destination when there is a call.
In principle, all call forwarding actions can be chained. You can configure this
centrally with parameters.
You must provide enough memory for the forwarding destinations.
97.2 User Interface
IMPORTANT: The forwarding destination number must be terminated with "#"

when dialling in the voice function. If “#” is not dialed then the validation of the
number starts only after time-out.
In the service function there is no time-out. Destination number can be terminated
by “#” or by selecting the menu option "save?"
97.2.1 Variable Call Forwarding

You can enter destinations for variable forwarding from the station device.
Entering a destination automatically activates it. Deleting a destination
automatically deactivates it. You can configure variable call forwarding
a) from the station device
or
b) with AMO ACTDA or Configuration Management
You can configure variable call forwarding for optiPoint via the service menu and
for Anate and functional terminals via code. Configure the digit analysis results in
digit analysis.
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
User Interface
With two exceptions, you can always program only one variable forwarding
destination. The exceptions are:
1. CFU can simultaneously have an internal and an external destination
2. You can enter a destination for each type of forwarding for functional
terminals with DSS1 protocol
97.2.2 Fixed Call Forwarding

You can enter, activate, deactivate, or delete one fixed forwarding destination
from the station device. When you enter and save the destination from the station
device, the forwarding is activated. When you enter the destination with the AMO
ZIEL, it is not automatically activated. Disabling a destination does not
automatically delete the destination entry. Activate it separately.
Program and delete fixed call forwarding
or
b) with AMO ZIEL or Configuration Management
Activate or deactivate fixed call forwarding
or
b) with AMO ACTDA or Configuration Management
You can configure fixed call forwarding for optiPoint via the service menu or with
codes; you must use codes for Anate and functional terminals. Configure the digit
analysis results with the AMO WABE or Configuration Management.
97.2.3 System Call Forwarding

You cannot enter any forwarding destinations for this type of forwarding from the
station device. You must use AMO ZIEL or Configuration Management. You can
only activate or deactivate it by code from the station device or by using AMO
ACTDA or Configuration Management.
A special feature is that you cannot activate the type of forwarding (CFU or CFB,
for example) for each separately, but must do all at once. If you later add a
destination for a type of forwarding, it is automatically activated if this type of
forwarding was activated for the previously entered destination.
Example:
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
User Interface
You have entered and activated a CFNR destination for CFVAR=SYSTEM. If you
later enter a CFB destination, it is automatically activated.
97.2.4 Call Forwarding/Call Forwarding Busy

If ZAND reserve parameter 124 is not acrtivated the fixed forwarding destination
is not used for executing the CFNR or CFB. If system call forwarding is defined,
it is used.
If ZAND reserve parameter 124 is activated, the fixed forwarding destination is

used on an individual subscriber basis like in earlier versions, depending on the
COS parameters CFNR and CFB.
97.2.5 Call Forwarding Unconditional

B has se call forwarding unconditional to C. C has call forwarding unconditional
to B.
When A calls B , C will ring even C has set CFU to B.
If B should ring you must set reserve switch 124 in AMO ZAND.
97.2.6 Chaining FWD Types

The diversion sequence table (DIST) defines how often a type of forwarding can
be performed in one connection. The table also defines which types of forwarding
can be chained together. The table is centrally administered.
There are ten such entries that are permanently assigned to the different types of
station devices. You can see the assignment in the information field of the
individual entries. (for example: DISPLAY-ZAND: TYPE=DIST).
IDX Device type

1 Analog telephones
2 Functional terminals
3 Digital station devices
4 Hunt group
5 Attendant console
6 Analog trunks
7 Digital trunks (protocol /= ECMA-QSIG)
8 Digital trunks (protocol = ECMA-QSIG or ECMAV2)
Table 59 Diversion Sequence Table Device Types
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
IDX Device type

9 Digital trunks to central office
10 Free (no assignment)
Table 59 Diversion Sequence Table Device Types

For one of the ten possible entries in the DIST, the following table shows. In this
case, the following would be possible:
• 10 x CFU
• 1 x CFB, CFNR, or CD
• Chaining is only allowed for CFU to CFU
CFU CFB CFNR CD

10 CFU X
1 CFB
1 CFNR
1 CD
Table 60 DIST
The DIST treats the new type of forwarding, CFDND, the same as CFB.
The DIST treats DelCFB, the other new type of forwarding, like CFNR.
The parameter FWDMAX still defines the total number of forwarding entries,
regardless of the type.
If the last forwarding is to the VMS, you can use the parameter FWDVMS1 to
define whether the forwarding should be done to the mailbox of the first called or
to the last forwarded.
When you program a variable FWD, an activated fixed FWD is deactivated, but a
FWD System not. The variable FWD is executed. If you deactivate this, the
system executes a previously activated FWD System.
If a variable FWD is activated and you program and activate a fixed FWD, the
variable FWD is deleted.

The following contains lists of sample commands for the different AMOs in
question:
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
97.3.1 AMO ACTDA

• Activating the FWD for FWD type SYSTEM for voice:
Configuration Management --> Line --> Station, enter station number

and click Search. In the Call Forwarding tab, select the forwarding type
and variant. Then select and save.
Activate call forwarding with the AMO ACTDA:

ADD-
ACTDA:TYPE=STN,STNO=3240,FEATCD=FWD,CFVAR=SYSTEM,SI=
VCE;
• Configuring a variable FWD for CFU with a common destination for internal
and external calls:

and variant. Then select and save.
Activate call forwarding for CFU with the AMO ACTDA:

ADD-
ACTDA:TYPE=STN,STNO=3280,FEATCD=FWD,CFVAR=STATIONV,D
TYPE=CFU,ITYPE=GEN,SI=VCE,DESTNO=4711;
97.3.2 AMO COSSU

Relevant authorizations:
• FWDBAS Release the FWD for programming by other subscribers
• FWDFAS Programming a FWD for other subscribers
• FWDDIR Activate or deactivate and query FWD for incoming
• CFNR Call forwarding when there is no answer (SMR09 and later or PRB for
SMR08)
• CFB Call forwarding when busy (SMR09 and later or PRB for SMR08)
Configuration Management --> Tables --> Class of Service, enter COS

and click Search. In the Voice 1 tab, select the parameter FWDDIR, for
example, and save.
Add authorizations with the AMO COSSU:

CHANGE-COSSU:TYPE=COS,COS=<cos number>,AVCE=<e.g.
FWDDIR>;
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
97.3.3 AMO COT

Relevant parameters, new:
• CDN Call forwarding during the ringing phase throughout the network
• CFBN Call forwarding when busy throughout the network
Configuration Management --> System Data --> Trunk --> Class of

Trunk (COT), enter COT and click Search. In the Parameter 2 tab, select
the parameter CDN, for example, and save.
Add values using the AMO COT:

CHANGE-COT:COTNO=<cot
number>,COTTYPE=COTADD,PAR=<CDN>;
Relevant parameters, old:
• CFOS Call forwarding possible network-wide
• CFBU Call forwarding on busy with new setup of the connection to the
forwarding destination throughout the network
• FWDN Release rerouting for network-wide call forwarding to source node

(cannot be used at the same time as CFBU)
• FWDR Call forwarding is done using rerouting in the public network

(application for France)
• FAX1 Call forwarding of incoming FAX trunk calls to phonemail
• FAX2 Call forwarding of incoming FAX trunk calls to phonemail
• NCTP The partner node can execute network-wide call forwarding after
transfer
• CFVA Activate connectivity validation for call forwarding destinations in

network
• FNAN Activate rerouting for network-wide call forwarding to source node
• XFER Forwarding trunk call
97.3.4 AMO DIMSU

Define size of the memory for FWD destinations and for forwarding follow-me
You can only administer the memory values in expert mode.

command).
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
To change the memory using the AMO DIMSU:

ADD-DIMSU:TYPE=USER,CFWDEST=<e.g. 100>,CFWHIST=<e.g.
100>;
Guidance value for dimensioning: One pool element per STN and forwarding
type. Additional pool elements for separate destinations for internal and external.
Example: If all possibilities are used for a STN according to Table 1, you need 9
pool elements if you enter common destinations for internal and external calls.
97.3.5 AMO TDCSU

Parameter FWDX Maximum number of call forwarding entries (FWDMAX) in the
partner system.
You only need this parameter for ECMA-QSIG or EURO-ISDN protocol (see
PROTVAR parameter). For ECMA-QSIG protocol, you should not set this value
to more than 5.
Configuration Management --> System Data --> Trunk --> Trunk, click
Search and select the circuit. In the Digital Extensions tab, change and save
the value for the call forwarding entries.
To change the call forwarding entries using the AMO TDCSU:

CHANGE-TDCSU:PEN=<LTG-LTU-SLOT-
PORT>,FWDX=<number>,DEV=<device>,BCGR=<B channel group
number>;
97.3.6 AMO WABE

Administering digit analysis results for call forwarding:
97.3.6.1 FWD Fixed
• DAR for programming and activating for voice:
click New. Enter dial code and select and save AFFWDVCE as the dial
code type.
Configuring a digit analysis result using the AMO WABE:

ADD-WABE:CD=*51,DAR=AFFWDVCE,CHECK=NO;
• DAR to deactivate and delete for voice:
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
click New. Enter dial code and select and save DFFWDVCE as the dial
code type.

ADD-WABE:CD=#51,DAR=DFFWDVCE,CHECK=NO;
(or configure both with one command)
ADD-WABE:CD=*51,DAR=AFFWDVCE,CD2=#51;
• DAR to activate for voice:
click New. Enter dial code and select and save AFWDVCE as the dial
code type.

ADD-WABE:CD=*41,DAR=AFWDVCE,CHECK=NO;
• DAR to deactivate for voice:
click New. Enter dial code and select and save DFWDVCE as the dial
code type.

ADD-WABE:CD=#41,DAR=DFWDVCE,CHECK=NO;
ADD-WABE:CD=*41,DAR=AFWDVCE,CD2=#41;
• Digit analysis results for non-voice DFFWDFAX/DFFWDDTE (deactivate

FAX/DTE)
click New. Enter dial code and select and save DFFWDFAX or
DFFWDDTE as the dial code type.

ADD-WABE:CD=*61,DAR=DFFWDFAX,CHECK=N
ADD-WABE:CD=*71,DAR=DFFWDDTE,CHECK=NO;
• Digit analysis results for non-voice AFFWDFAX/AFFWDDTE (program

and activate FAX/DTE)
click New. Enter dial code and select and save AFFWDFAX or
AFFWDDTE as the dial code type.

ADD-WABE:CD=*81,DAR=AFFWDFAX,CHECK=N;
ADD-WABE:CD=*91,DAR=AFFWDDTE,CHECK=N;
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
97.3.6.2 FWD Variable
• DAR for programming and activating internal or external
click New. Enter dial code and select and save AULFEXIN as the dial
code type.

ADD-WABE:CD=*42,DAR=AULFEXIN;
• DAR to activate CFU, external
click New. Enter dial code and select and save AFWDEXT as the dial
code type.

ADD-WABE:CD=*43,DAR=AFWDEXT,CHECK=N;
• DAR to deactivate CFU, external
click New. Enter dial code and select and save DFWDEXT as the dial
code type.

ADD-WABE:CD=#43,DAR=DFWDEXT,CHECK=N;
ADD-WABE:CD=*43,DAR=AFWDEXT,CD2=#43;
• DAR to activate CFU, internal
click New. Enter dial code and select and save AFWDINT as the dial
code type.

ADD-WABE:CD=*44,DAR=AFWDINT,CHECK=N;
• DAR to deactivate CFU, internal
click New. Enter dial code and select and save DFWDINT as the dial
code type.
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding

ADD-WABE:CD=#44,DAR=DFWDINT,CHECK=N;
ADD-WABE:CD=*44,DAR=DFWDINT,CD2=#44;
• DAR to activate CFBNR
click New. Enter dial code and select and save AFWDBNA as the dial
code type.

ADD-WABE:CD=*45,DAR=AFWDBNA;
• DAR to activate CFB
click New. Enter dial code and select and save AFWDB as the dial code
type.

ADD-WABE:CD=*46,DAR=AFWDB;
• DAR to activate CFNR
click New. Enter dial code and select and save AFWDNA as the dial
code type.

ADD-WABE:CD=*47,DAR=AFWDNA;
• DAR to deactivate CFB, CFNR, CFBNR, CFU

Use the same DAR to simultaneously deactivate all FWD types as for FWD
fixed.
• Digit analysis results for non-voice AFWDFAX/AFWDDTE (activate FAX/

DTE)
click New. Enter dial code and select and save AFWDFAX as the dial
code type.

ADD-WABE:CD=*48,DAR=AFWDFAX;
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
• Digit analysis results for non-voice DFWDFAX/DFWDDTE (deactivate

FAX/DTE)
click New. Enter dial code and select and save DFWDFAX as the dial
code type.

ADD-WABE:CD=*49,DAR=DFWDFAX;
97.3.6.3 FWD System
• DAR to activate
click New. Enter dial code and select and save ASYSFWD as the dial
code type.

ADD-WABE:CD=*60,DAR=ASYSFWD,CHECK=N;
• DAR to deactivate
click New. Enter dial code and select and save DSYSFWD as the dial
code type.

ADD-WABE:CD=#60,DAR=DSYSFWD,CHECK=N;
(or with a command)
ADD-WABE:CD=*60,DAR=ASYSFWD,CD2=#60;
97.3.6.4 Special Digit Analysis Results
• AFWDREM/DFWDREM (activate or deactivate for remote/follow me)
• FWDTERM (terminal call forwarding)
• AFWDDWD (FWD activate for digits without display)
• FFWDREMK (saving a FWD fixed remotely via key)
• FWDREM (display of the FWD remote/follow me)
• FWDIGNOR (ignore call forwarding)
• FWDKY (program key function FWD key)
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
click New. Enter dial code and select and save a digit analysis result as
the dial code type.

ADD-WABE:CD=<keyed_num>,DAR=<special digit analysis
point>;
97.3.7 AMO ZAND

• Fixed forwarding destination is CFNR destination (SMR09 and later)
You can only configure the identifier "Fixed forwarding destination is

CFNR destination" in expert mode.
command).
Using the AMO ZAND, configure the identifier "Fixed forwarding
destination is CFNR destination":
• Set number of chained call forwarding instructions to a maximum of 10
You can only configure the number of chained call forwarding

instructions in expert mode.
command).
Use the AMO ZAND to configure the number of chained call forwarding
instructions:
CHANGE-ZAND:TYPE=ALLDATA2,FWDMAX=10;
• Set up user interface without fixed forwarding for USA
You can only administer setting the menus for call forwarding in expert
mode.
command).
Using the AMO ZAND, set the menus for call forwarding:
CHANGE-ZAND:TYPE=ALLDATA3,CFUI=NO;
• A maximum of 5 CFU call forwarding instructions should be possible for

optiPoint after no answer:
You can only configure the number of maximum call forwarding

instructions in expert mode.
command).
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
Use the AMO ZAND to configure the number of call forwarding

instructions:
CHANGE-
ZAND:TYPE=DIST,DIVSQIDX=3,DIVTYPE=CFU,MAXDIVNO=5,ALL
DIVTY=CFNR;
CFU CFB CFNR CD

5 CFNR X
Table 61 Result of the Entry in the DIST Table
DIVSQIDX=3 is intended for the optiPoint devices.
97.3.8 AMO ZIEL

• Enter a destination for internal calls for FWD variable system, forwarding type
CFU.

and variant and save with destination number.
Use the AMO ZIEL to configure call forwarding:

ADD-
ZIEL:TYPE=FWD,SRCNO=3240,SI=VCE,DESTNOF=3241,DTYPE=C
FU,ITYPE=INT,
CFVAR=SYSTEM;
• Configure and activate a call forwarding destination for internal and external
calls


ADD-
ZIEL:TYPE=FWD,SRCNO=4711,SI=VCE,DESTNOF=2100,DTYPE=C
FNR,ITYPE=GEN,CFVAR=SYSTEM;
ADD-ACTDA:FEATCD=FWD,CFVAR=SYSTEM,SI=VOICE;
• Configure destination for fixed FWD


ADD-
ZIEL:TYPE=FWD,SRCNO=5700,DESTNOF=3333,DTYPE=CFU,ITYP
E=GEN,CFVAR=STATION;
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
Relevant AMOs
97.4 Relevant AMOs

Language
ACTDA AULVAR d Umleitungsvariante (variable, ...)
CFVAR e call forwarding variant (variable, ...)
UART d Umleitungsart (CFU, ...)
DTYPE e Diversion type (CFU, ...)
KART d Art der kommenden Verbindung
ITYPE e incoming seizure
SI d Service
SU e service indicator
ZLRUFNU d Rufnummer des Umleitungsziels
DESTNO e forwarding destination number
DIMSU AULZIEL d Anzahl der Poolelemente zum Speichern von
Umleitungszielen
CFWDEST e number of call forwarding destinations
AULHIST d Anzahl der Poolelemente zum speichern von
Einträgen der Umleitungshistory. Ist dieses
Pool nicht eingerichtet, funktioniert zwar die
Umleitung, aber die Maximalwerte der
einzelnen Umleitungstypen aus der
Umleitungs Folge Tabelle können nicht
überprüft werden.
CFWHIST e number of elements for call forwarding history
TDCSU AULX d Legt fest, wie oft eine Verbindung maximal
umgeleitet werden darf um über diese
Leitung verbunden zu werden
FWDX e
ZAND AULMAX d Legt die Gesamtzahl der erlaubten
Umleitungen, unabhängig vom Typ, fest.
FWDMAX e
AULVMS1 d Legt fest, ob die Umleitung ins Postfach der
Erstgerufenen oder des zuletzt Umleitenden
erfolgen soll wenn die Umleitung zum VMS
führt.
FWDVMS1 e
UMLENIDX d Gerätespezifischer Index
DIVSQIDX e Diversion Sequence Table Index
UMART d Umleitungsart
DIVTYPE e Diversion type that a diversion can follow.
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
Relevant AMOs

Language
MAXANZUM d Anzahl, wie oft der durch UMART definierte
Typ in einer Verbindung maximal
durchgeführt werden darf
MAXDIVNO e
ERLUMART d Umleitungsart, die der durch UMART
definierte Typ in einer Verbindung folgen darf
ALLDIVTY e Allowed diversion types to follow a specific
diversion, defined with DIVTYPE
CFUI d Anrufumlenkung Benutzeroberfläche mit/
ohne feste Umleitung vom Endgeraet
CFUI e Call forward user interface with/without
station fix forwarding.
ZIEL QLRUFNU d Rufnummer des Teilnehmers, für den eine
’Umleitung programmiert wird
SRCNO e
SI d Service
SI e service indicator
ZLRUFNU d Rufnummer des Umleitungsziels
DESTNOF e destination number for forwarding
NAME d Name des Umleitungsziels. Nur relevant für
netzweite oder externe Teilnehmer
NAME e
UART d Umleitungsart (CFU, ...)
DTYPE e
KART d Art der kommenden Verbindung
ITYPE e incoming seizure of fwd feature
AULVAR d Umleitungsvariante (variable, ...)
CFVAR e call forwarding variant
WABE AULEEXIN d Anrufumleitung einschalten ext und int
AFWDEXIN e activate call forwarrding external and internal
AULEEXT d Anrufumleitung einschalten extern
AFWDEXT e activate call forwarding external
AULEINT d Anrufumleitung einschalten intern
AFWDINT e activate call forwarding intern
AULEBKA d Anrufumleitung einsch. besetzt oder keine
antwort
AFWDBNA e activate call forwarding busy or no answer
AULEKA d Anrufumleitung einschalten keine antwort
AFWDNA e activate call forwarding no answer
AULSYSE d Anrufumleitung system einschalten
A31003-H3170-S103-6-7620, 02/2019
aul_cm_en.fm
Call Forwarding
Relevant AMOs

Language
ASYSFWD e activate system call forwarding
A31003-H3170-S103-6-7620, 02/2019
call_forward_no_reply_en.fm
Call Forward no Reply (CFNR)
Call Forward no Reply after Transfer
98 Call Forward no Reply (CFNR)
98.1 Call Forward no Reply after Transfer
Incoming
external/internal
call
CorNet NQ S0/S2
A Transferring pty B Call forwarding no reply C Call forwarded to pty
An incoming call for A (station or AC) is transferred to party B . Party B has

configured call forwarding no reply to party C. Upon expiration of the call
forwarding no reply timer, the call is forwarded to party C. If necessary, a recall to
A is carried out.

The feature is available to all users in a PBX.
98.1.3 Interaction with other Features

• In the case of CFNR during a recall to the AC or during an attendant intercept
(parallel call), the call to the AC is terminated and CFNR is carried out.
• CFNR for interworking with DPNSS1 (redirecting service).
• Multiple hop interactions with CFNR, call forwarding unconditional and call
forwarding busy.
• CFNR after transfer from a second consultation call.
A31003-H3170-S103-6-7620, 02/2019
call_forward_no_reply_en.fm
Call Forward no Reply (CFNR)
Call Forward No Reply and Rerouting
98.2 Call Forward No Reply and Rerouting

With this change request it is now possible to reroute calls after call forward no
reply. This means that if after CFNR execution the destination is not reachable
then the call is rerouted to the redirection party.
A31003-H3170-S103-6-7620, 02/2019
hard_hold_analog_e_en.fm
Call Hold analog
Overview
99 Call Hold analog
99.1 Overview
The Hold function previously available via keyset functions and the Call Park
feature is also available for analog telephones.
Party is on hold
Analog user
dials hold code
Second call made while

If analog user dials code again first is on hold
Toggle is possible

An Analog station user can place a call on hold and hang up without losing the
call. After holding the call, the user may originate or receive other calls on the
same line and alternate between the two calls, holding one call while speaking to
the other.
The Call Hold analog feature is only possible during a stable two party talk state.
This feature allows only an Anate (including Off Premise Station) to place one of
the following connections on hold freeing up the line for other calls :
• Partner device is an Anate.
• Partner device is a Digite (CMI / Keyset / DFT).
• Partner device is a Functional Device.
• Partner device is an analog CO/TIE trunk.
• Partner device is a digital CO/TIE trunk.
If the held party releases, the hold position becomes available for new calls.
Once a party is placed on hold, the call can only be retrieved by the same Anate
that placed the call on hold.
A31003-H3170-S103-6-7620, 02/2019
Call Hold analog
User Interface
Only one party can be held in the call hold location at a time. If a station attempts
to put a second call on hold while another is on hold, the second call is placed on
hold. The first call is removed from hold and reconnected to the station user
activating hold.(in effect the user hastoggled the calls
99.3 User Interface

Only one feature access code is provided for Call Hold and retrieval.
Only an Anate can put a call into a hold position via the Call Hold analog access
code. The following acknowledgements are given to the Anate for placing a call
on hold :
• Confirmation tone, when holding was sucessfull.
• Immediate talk, when an existing call was already on hold.
• Busy tone, when call hold is not allowed for partner device type.
• Reorder tone for all other cases, where holding is not possible.
The held subscriber is given announcement or music or silence, while on hold.
The same Call Hold analog access code will be used to retrieve the call again
from the hold position. The following acknowledgements are given to the Anate:
• Immediate talk, for retrieving a Call Held party.
• Reorder tone, when attempting to retrieve a party and the hold location is
empty.
A party left on hold (single held) recalls the Anate that placed the call on “Call Hold
analog” after the timeout of the Hold Recall timer, or is intercepted to the
Attendant/ACWin, dependent upon the system parameter (COT parameter
SPAH) and the state (idle, busy or out of service) of the party that held the call.

• The Call Hold Analog feature is only a local feature and not available network-
wide.
• Only Anates have access to the Call Hold analog feature.

Assign Call Hold analog access code :
A31003-H3170-S103-6-7620, 02/2019
Call Hold analog
Relevant AMOs
ADD-WABE:CD=<XYZ>,DAR=HOLD;
Change timer value for Call Hold analog recall timer:

CHA-CTIME:TYPESWU=CP1,CTHLDREC=<X>;
Caution: This timer is also used for feature “System Manual Hold”.
Optionaly, assign COT parameter SPAH to COT <N> of an used digital or analog
trunk:
CHANGE-COT:COTNO=<N>,COTTYPE=COTADD,PAR=SPAH;;
99.6 Relevant AMOs

Language
WABE HOLD d Gespräche halten/wiederholen auf/von Halte
Position
WABE HOLD e call hold and retrieve to/from hold location
CTIME KDHLDREC d Call Hold analog Wiederanrufzeitglied
CTIME CTHLDREC e call hold analog recall timer
COT SPAH d nach Wiederanrufzeitgliedablauf wird ein
geparkter oder gehaltener Teilnehmer zum
Vermittlungsplatz weitergeleitet
COT SPAH e on recall timer expiry, a parked or held party is
routed to the attendant
A31003-H3170-S103-6-7620, 02/2019
Call Hold analog
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
analog_port_call_id_en.fm
Feature Description
100 Call ID (Name and Number) on Analog Port with PRI

NI2 Calls

In OpenScape 4000 the caller ID number is sent via PRI NI2 from Telco central
office to an analog port between the first and second ring cycle. The Calling Party
Name Facility message is a separate message that is sent after the OpenScape
4000 (PBX or CPE) sends the Alert message to the Telco central office.
OpenScape 4000 only sends caller ID information during the long silent interval
between the first and second power ringing patterns.
Telco sends caller party name information typically after silent interval between
the first and second power ringing patterns.
Activating this feature the caller ID number and caller party name is sent between
first and second power ringing pattern.

CHANGE-FEASU:TYPE=A,CM=CLIP;
CHANGE-ZAND:TYPE=ALLDATA3,CLIPSTD=ETSIFSK;
100.3 Relevant AMOs

Language
FEASU CLIP d Calling Line Identification Presentation
CLIP für analoge Teilnehmer
CLIP e Calling Line Identification Presentation
CLIP for analog subscribers
ZAND CLIPSTD=ETSIFSK d CLIP Protokoll Standard für analoge
Teilnehmer
ETSI mit FSK(Frequency Shift Key)
CLIPSTD=ETSIFSK e CLIP Protocol Standart for analog
subscribers
ETSI with FSK(Frequency Shift Key)
EINGVA d Im Nachtschaltungsfall zu aktivierende
Variante
A31003-H3170-S103-6-7620, 02/2019
analog_port_call_id_en.fm
Relevant AMOs

Language
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
A31003-H3170-S103-6-7620, 02/2019
cli_enhancements_en.fm
Calling Line Identification (CLI) Enhancements
Feature Description
101 Calling Line Identification (CLI) Enhancements

Requirements from the customers for special handling of incoming calls in
OpenScape 4000:
• In the case the incoming number matches a predefined number/pattern, it has

to be changed to an internal number - as if the call came from an internal
number.
• In the case the incoming number matches a predefined number/pattern, the

incoming party name has to be changed - so the calling party can be
recognized.
• Alpha tagging: In the case the incoming number matches a predefined

number/pattern, the incoming party name has to be changed - so the
incoming number can be recognized.
• Call barring: In case the incoming number matches a predefined number/

pattern, one of the following has to be done:
– The call has to be rejected.
– The call has to be routed to a predefined number (hotline destination).
– The call has to be accepted (routed to the original called party).
– The call barring processing described above should also depend on the
called destination number (not only on the calling party number).
• No intercept to attendant console if the CLI number is unknown.
101.2 Realization
There are two kinds of tables:
• DDI table: table for checking the called (DDI) number (1 table)
• CLI tables: tables for checking the calling (CLI) number (19 tables)
For both kind of tables number patterns can be specified:
• the digits 0-9,
• the letter "X" indicating any digit 0-9,
A31003-H3170-S103-6-7620, 02/2019
Prerequisites
• the letter "Z" indicating any number of any digits 0-9.
IMPORTANT: The maximum number of entries over all of these tables is 64000.
101.3 Prerequisites
1. LCR Dialing Plan Configuration
Only for DDI table type of CLIMA records.
In order to add a DDI type of clima record , user must add a dial plan having
the following values.
• LCR Dialing Plan Numbers:

DPLNUM=770 is reserved for DDI table
DPLNUM=771-789 for CLI tables 1-19
• LCR Pool Number : 8

LWMPOOL=8
• LCR Dialing Plan :0

DIALPLAN=0 for DDI
DIALPLAN=1-19 for CLI. 1 -19
Create the DDI/CLI tables with AMO CLIMA (770 for the DDI table,771-789
for the CLI tables).
2. To add a clima record having dial plan number “x”, user should previously add
a dial plan having dial plan number “770 + x” and LCR Pool Number 8 in
OpenScape 4000 Assistant “LCR Dialing Plan Administration” dialog.
For example if an user want to create a clima record having dial number 1,
771 dial plan having poll number 8 should be added first.
For all table types(DDI & CLI) is the following
Figure 107 LCR Dialing plan configuration
A31003-H3170-S103-6-7620, 02/2019
Service Information
3. Assign the COT parameters:
• CLNA (for CLI name translation)
• CLNO (for CLI number modification)
• CLAC (for CLI action/ call barring)
• DDIC (for DDI control)
• CLNI (CLI number unknown - no intercept to attendant console)

How calls are processed:
1. An incoming call is received with a called number (e.g. WABE access code
STN/TLN)
2. If COT parameter DDIC is set, the called number is checked against the DDI
table (only when the digit analysis result is station or a hunt group). This table
will determine which CLI table to use for checking the CLI number.
3. If COT parameter DDIC is not set or if the DDI table is empty or if the called
number is not found in the DDI table, the first CLI table will be used. Otherwise
the table specified in the DDI table will be used.
4. Then the CLI number will be checked against the CLI table (from step 1).
5. If the calling number is found in the CLI table the following will happen:
• If COT parameter CLNA is set, the calling party name will be overwritten
by the name from the CLI table.
• If COT parameter CLNO is set, the calling party number will be

overwritten by the number from the CLI table.
• If COT parameter CLAC is set, the CLI action from the CLI table will be
executed:
– For REJECT the calling party will be disconnected.
– For RESTRICT the call will be routed to the hotline destination

specified in the CLI table.
– For ACCEPT the call will be accepted (to the called destination).
6. If the CLI number is not found in the CLI table, the following will happen:
• If at least one of the COT parameter CLNA or CLNO or CLAC is set :
– the call will be accepted (sent to called party) if COT DDIC is not set.
A31003-H3170-S103-6-7620, 02/2019
Service Information
– the call will be intercepted to Attendant if COT DDIC is set and COT
CLNI is not set.
– the call will be accepted if COT DDIC and COT CLNI are set and
calling number has PresInd Restricted.
• If none of the COT parameters CLNA or CLNO or CLAC is set, then the
call will be accepted (sent to called party).
Scenarios
• Incoming call is rejected
If an incoming call is rejected by this feature the call is cleared with cause
"incompatible destination" in order to disable a callback attempt from the
calling party.
• Incoming call to a station that is restricted

For an incoming call to a station that is restricted, the hotline destination is
called. If this hotline destination is busy the call is cleared with cause
"incompatible destination" in order to disable a callback attempt from the
calling party.
• Call back
There is an incoming call to a station where the calling party name/number is
modified according to this feature and the calling party activates a callback.
Then during callback execution the original name/number of the calling party
will appear and not the modified name/number.
Restriction
This feature will only work for incoming digital trunks (including IP trunks). The
new COT parameters can only be set for digital trunks.
“CLI Call Baring and Alpha Tagging (CLIMA)” in OpenScape 4000 Assistant/
Manager
The “CLI Call Baring and Alpha Tagging (CLIMA)” is available in CM Assistant
and CM Manager. There is a close relationship between “CLIMA” (Start Page >
Configuration Management > Tables > Dial Plan) and “LCR Dialing Plan
Administration” (Start Page > Configuration Management > Least Cost
Routing) dilalogs. To use all functionality in CLIMA dialog, user should first
configure LCR Dialing Plans by using “LCR Dialing Plan Administration” .
Rules for CLIMA

To add/modify a clima record you should obey the rules mentioned below. If you
do not obey the rules, an error message appears.
1. For all clima table types, the user must specify the switch name, table type
dial plan and pattern.
2. If the user tries to add a CLI type of clima record, Action must be specified.
A31003-H3170-S103-6-7620, 02/2019
Generation
3. If the user specified restrict value in action field, “Index of destination table”
must be also specified. This value must be between 1 and 2512.
4. During adding/modifying DDI type of clima record, it is not allowed to enter

values for “Action”, “Index of Destination Table”, “Name Representing the CLI
Digit Pattern” and “Alternate Number for the CLI Digit Pattern”.
5. Pattern should be unique among the all clima records and change operation
on pattern field is not allowed like table type.
6. Pattern could be a combination of 0..9xXzZ.
7. Dial plan number must be in the range between 1-19.
8. Dial plan number choice list shows the list of predefined LCR dial plan
number – 770 in the range between 770 and 790.
Figure 108 CLI call barring and alpha tagging (CLIMA)
101.5 Generation
• Reserve dialplans 770 for DDI table and 771-789 for CLI tables
ADD-
LDPLN:LCRCONF=LCRADM,DPLNUM=770,LWMPOOL=8,DIALPLAN=0,INFO="DD
I TABLE";
ADD-
LDPLN:LCRCONF=LCRADM,DPLNUM=771,LWMPOOL=8,DIALPLAN=1,INFO="CL
I TABLE1";
ADD-
LDPLN:LCRCONF=LCRADM,DPLNUM=772,LWMPOOL=8,DIALPLAN=2,INFO="CL
I TABLE2";
• Reserve special LCR dialingplan entries
ADD-DIMSU:LDPLN8=1000;
• Create DDI table entries
ADD-CLIMA:TABLE=DDI,DDIDP="12001",PLAN=1;
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
• Create CLI table entries

ADD-CLIMA:TABLE=CLI,PLAN=1,CLIDP="4930640014001",
NAME="ANL91-1",NUMBER=28814001,ACTION=ACCEPT;
NAME="ANL91-2",NUMBER=8814002,DESTIDX=1,ACTION=RESTRICT;
NAME="ANL91-3",NUMBER=8814000,ACTION=ACCEPT;
NAME="ANL91-4",NUMBER=8814003,ACTION=REJECT;
ADD-CLIMA:TABLE=CLI,PLAN=1,CLIDP="49307100X",NAME="ANLX46
ACCEPT",ACTION=ACCEPT;
• Assign e.g. several COTs for incoming CO trunk
CHANGE-
COT:COTNO=60,COTTYPE=COTADD,PAR=CLNA&CLNO&CLAC&DDIC&CLNI;
101.6 Relevant AMOs

Language
CLIMA AKTION d ACCEPT: Der Anruf wird akzeptiert.
REJECT: Der Anruf wird abgelehnt.
RESTRICT: Der Anruf wird an eine
vordefinierte Rufnummer, basierend auf
dem DESTIDX Feld weitergeleitet.
ACTION e ACCEPT: The call will be accepted.
REJECT: The call will be refused.
RESTRICT: The call will be routed to a
predefined extension based on the
Destination Index field.
CLIDP d Falls die Nummer des kommenden Anrufers
zu dieser/diesem Nummer/ Muster passt,
wird die entsprechende Aktion
ausgeführt.CLIDP kann aus den Ziffern 0-9
und den Buchstaben X und Z bestehen.
CLIDP e In case the incoming number matches this
number/pattern, the corresponding action
will be taken. CLIDP can contain digits 0-9
and literals X and Z.
DDIWM d die gerufene Nummer wird gegen diese
Nummer/dieses Muster geprüft. DDIWM
erlaubt die Ziffern 0-9 und die Zeichen X und
Z.
DDIDP e The called number is checked against this
number/pattern. DDIDP can contain digits 0-
9 and literals X and Z.
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

Language
DESTIDX d Wenn AKTION=RESTRICT ist und die
externe Nummer passt, wird der DESTIDX
in der (mit HOTLN: HOTDEST
konfigurierten) Zieltabelle gesucht und der
Anruf wird an den entsprechende
Rufnummer weitergeleitet.
DESTIDX e If ACTION is RESTRICT and the external
number matches, the destination number
will be changed to the value looked up in the
Destination Table (configured with
HOTLN:HOTDEST) based on this index
value.
NAME d Wenn die externe Nummer passt, wird der
Name der externen Party in diesen Wert
geändert.
NAME e If the external number matches, the name of
the external party will be changed to this
value.
NUMMER d Wenn die externe Nummer passt, wird die
Nummer der externen Party in diesen Wert
geändert.
NUMBER e If the external number matches, the number
of the external party will be changed to this
value.
PLAN d Dieser Parameter bestimmt, welche CLI-
Tabelle verwendet wird, um CLIDP zu
prüfen.
PLAN e This parameter determines which CLI Table
to use for checking the CLIDP.
COT COTPAR=CLNA d CLI Name / Namensaustausch
PAR=CLNA e CLI name / alpha tagging
COTPAR=CLNO d CLI Nummernmodifikation
PAR=CLNO e CLI number modification
COTPAR=CLAC d CLI Aktion / Anruf zurückweisen
PAR=CLAC e CLI action / call barring
COTPAR=DDIC d DDI-Kontrolle
PAR=DDIC e DDI control
COTPAR=CLNI d Kein Abwurf zum AC für unbekannte CLI
PAR=CLNI e CLI number unknown - no intercept to AC
DIMSU LWM8 d Anzahl der Einträge im Wählmusterplan 8
für Least Cost Routing
LDPLN8 e number of dial plan entries for lcr in dial plan
8
LDPLN WAPLNUM d LCR Wählplannummer
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

Language
DPLNUM e LCR dial plan number
LWMPOOL d LCR Poolnummer
LWMPOOL e LCR pool number
WAEHLPLN d LCR Wählplan
DIALPLAN e LCR dial plan
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
Calling Line Identification (CLI) Restriction
Feature Description
102 Calling Line Identification (CLI) Restriction
7440 Johnson
7440
7441
*XXX*
7440
7441
Presentation Restricted
The calling party’s name and station number are displayed at the called party’s
station or attendant console either directly or indirectly in the following cases:
• Internal / external call (external in the case of ISDN),
• Switching traffic,
• Callback (particularly callback-on-no-answer in mailbox),
• Call pickup (call waiting, call pickup group), CF / CFNA, server traffic and
connection to paging equipment.
• Attendant console - hold menu
IMPORTANT: The calling and called parties in the description below can be
extensions or attendant consoles.
It is possible to suppress the display of the calling party’s name and station
number at the called party’s station for individual calls and for specific systems,
circuits, and users.
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
Service Information
With display suppression you must decide whether the line is a "normal line" or a
"confidential line".
"Normal line": The station number is passed on and displayed at the called party’s
station or attendant console.
"Confidential line": Station Number display at the called party’s station is always
suppressed.
In this case, the text string to appear on the display of the called
party’s station can be established using a central parameter
(applies to all called parties in the system).
You can administer the confidential line for users.

and Search. Select the required value in the Basic 1 tab under Display
and save. 
Display=NO/YES/External Alternative Number/not extern
With the AMO SBCSU, AMO SCSU, AMO SSCSU, or AMO-SDAT via
the parameter
SSTNO=YES/NO/ONLYEXT/ONLYEX0;
YES= This user’s station number (name) is not displayed at the called
party’s station (internally and externally);
NO = This user’s station number is displayed at the called party’s
station internally and externally);
ONLYEXT = Only a replacement number (as configured with AMO
KNMAT) is displayed at an external station instead of this user’s station
number;
ONLYEX0 = Neither this user’s station number nor a replacement
number is displayed at an external station.

• To ensure that the external calling line identification restriction and the
external display of a replacement number (ONLYEX0 and ONLYEXT)
function correctly, you must make an entry to modify the station number with
a special modification condition.
• The protocol must be able to transmit this information to the destination (e.g.
QSIG).
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
• To suppress the display, the carrier must support a case-by-case suppression

to allow the function.
IMPORTANT: You can administer the confidential line for the attendant console’s
number (ATNDIND) only in the AMO ACSU with the parameter
STATNDNO=YES/NO/ONLYEXT.
(However only in expert mode in the management interface).

Configure the calling party as "secret" and configure a text string, such as
"SUBSCRIBER UNKNOWN" for display at the called party’s station.
• Set up confidential line at calling party (7140) for outgoing calls:

and Search. Select NO in the Basic 1 tab under Display and save.
(Display No means this is a confidential subscriber)
Use the AMO SDAT to set confidential subscriber:

CHANGE-SDAT:STNO=7140,TYPE=DATA,SSTNO=YES;
• Set up confidential line at attendant console for outgoing calls:
You must be in expert mode to administer the confidential line for

attendant consoles.
command).
Use the AMO ACSU to set confidential subscriber:
CHANGE-ACSU:ATNDNO=7777,SATNDNO=YES;
• Configure display text *XXX* at called party for confidential line calls:
You must be in expert mode to administer the display text.

command).
Set the display text XXX with the AMO ZAND as follows:
CHANGE-ZAND:TYPE=ALLDATA2,DISPNUUN=*XXX*;
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
Relevant AMOs
102.4 Relevant AMOs

Language
SDAT GETLNNU d geheime Teilnehmer-Rufnummer
SSTNO e Secret station number
ZAND ANZNUUN d Anzeigetext im Display von Teilnehmer B
DISPNUUN e Text on display of extension B
SBCSU GETLNNU d geheime Teilnehmer-Rufnummer
SCSU GETLNNU d geheime Teilnehmer-Rufnummer
SSCSU GETLNNU d geheime Teilnehmer-Rufnummer
ACSU GEVFNU d geheime Vermittlungsplatz-Rufnummer
SATNDNO e Secret ac number
102.5 Further Features in Connection with CLIR
102.5.1 Display Control for a Single Call
Suppression of the display of names and numbers on the called party’s station is
controlled by the selection of access codes (in the case of an Optiset with a
display this can also be controlled using the menu item "Display Suppression" in
the service menu "Additional Functions").
The access codes function differently depending on whether the line is normal or
confidential.
Display suppression for a "normal line":

In the case of a "normal line", the code for display suppression on (DISUON)
causes the display to be suppressed at the called party’s station for the next
call only.
Station Number display in the case of a "confidential line":

In the case of a "confidential line" the code for display suppression off
(DISUOFF) causes the station number to be passed on for display at the
called party’s station for the next call.
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
Further Features in Connection with CLIR
• The display suppression access codes can be assigned to the name keys,
together with the destination station numbers of the parties for whom the
modified display functions are to apply.
• Set up access codes as follows: (**80 Display Suppression ON and ##80

Display Suppression OFF)
click New. Enter dial code, select it as dial code type DISUON, and
save.
To configure a code for DISUON with the AMO WABE:

ADD-WABE:CD=**80,DAR=DISUON;
click New. Enter dial code, select it as dial code type DISUOFF, and
save.
To configure a code for DISUOFF with the AMO WABE:

ADD-WABE:CD=##80,DAR=DISUOFF;

Language
CD e Access code
KZP d ANZUEIN Anzeigenunterdrückung einschalten
ANZUAUS Anzeigenunterdrückung ausschalten
DISUON Display Suppression ON
DISUOFF Display Suppression OFF
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
102.5.2 Display Control for a Replacement Number

for Calls to an External Station
For confidential lines with SSTNO=ONLYEXT a replacement number can be

configured for display at the called party's station.
The modification in the AMO KNMAT must be entered in the relevant NPI for the
calling station number. The customer station number must be specified under
NUMEXT without any prefixes according to the TONE - as administered in the
AMO KNFOR or in the case of no entries TONE=INTERNATIONAL - up to the
destination node. The * is used in this case as a delimiter between the customer
station number and the extension to be replaced (or the number sequence).
The extension number in the "calling party" will be substituted for outgoing calls
by the replacement number (number sequence after delimiter *) if in addition
REPEXT is defined under MODCON.
IMPORTANT: The display of the ACD group number instead of the agent station
number can be administered in the TYPE=ACD branch of AMO ZAND with the
parameter SUPAGTNU=YES/NOr.
(However only in expert mode in the management interface)
IMPORTANT: There must be an entry for "replace extension number" when you
set display suppression at external stations. In this case no replacement number
is sent and the setup is identified as PRESENTATION RESTRICTED.
• The replacement number should be a meaningful number taken from the

customer's number block 
(i.e. Callbacks to this number should also be able to reach an STN/ATND.)
• Depending upon the numbering plan, digit modification can also be set up for
logical nodes (see description of AMO KNMAT).
• Possible alternative paths to other destination nodes have to be taken into

account if the replacement number is to be displayed in all cases (see LCR).
• Digit modification is based on the virtual origin and destination node numbers,
i.e. not on each individual station!
• Display suppression at external stations (SSTNO=ONLYEXT0) is effective

only with a valid replacement number.
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
Display of a replacement number 0 for the calling party (node 1-89-100) to the CO
with destination node number 1-89-190 for ISDN numbering plan (here:
international format as administered). The extension number - here 7141 - in the
"calling party" will be substituted by the replacement number (here: 0 for e.g. the
DAR ATND).
• Set up confidential line to an external station for calling station with

replacement number:

and Search. Select External Alternative Number in the Basic 1 tab
under Display and save.
Use AMO SDAT to set confidential subscriber:

CHANGE-SDAT:STNO=7141,TYPE=DATA,SSTNO=ONLYEXT;
• Display node format table:
Configuration Management --> Tables --> Dialing Plan --> Node Format
Tables (KNFOR), click SEARCH. Browse to the required destination
node number and read off the format data.
Use the AMO KNFOR to display data:

DISPLAY-KNFOR:DNNO=<destination node number>;
(Destination node number format data)
• Example for digit modification. The level where modification takes place
depends on the virtual destination node number. The format of the number
determines the entry in the node format table. If there is no entry there, ISDN
always uses the international format.
Configuration Management --> Tables --> Dialing Plan --> Network

Node Data (KNMAT), click NEW. Select the modification condition in
the Node Number Modification tab, enter the data, and save.
Use the AMO KNMAT for set digit modification:

CHANGE-
KNMAT:NPI=ISDN,LEVEL=0,ONNO=100,DNNO=190,MODCON=OU
T&REPEXT,NUMEXT=498978062*0;

Language
SDAT GETLNNU d geheime Teilnehmer-Rufnummer
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm

Language
KNMAT NPI d Numbering plan identifier, Rufnummernplan
MODBED d ERSNST=Ersetzten Nebenstellennummer
MODCON e REPEXT= Replace station number
ZAND UNAGTNU d Anzeige Rufnummer der ACD-Gruppe
SUPAGTNU e Display the number of the ACD group
102.5.3 Display Control (using parameters

DISPTGNA/INDNADIS)
From EV 3.0, QSIG-compliant behavior was implemented for independent

display of numbers and names, i.e. now number and name can be independently
checked for "presentation allowed". In the PABX, the number and the respective
name of a confidential line (SSTNO=YES) are always designated as
"presentation restricted". For this reason, so far only the number was checked for
"presentation allowed". If the presentation of the number was permitted, the name
was also displayed and vice versa.
If a station number is not transmitted, either the defined string or the trunk group
name is displayed depending on the AMO ZAND setting.
1. If the calling party and the called party are in the same system, the string that
has been set with the parameter DISPNUUN=< string > is displayed
regardless of how the parameter DISPTGNA was set with the AMO ZAND.
2. If the calling party and the called party are in different systems, a distinction
must be made between an OpenScape4000/HiPath 4000 to
OpenScape4000/HiPath 4000 or a an OpenScape4000/HiPath 4000 to Non
OpenScape4000/HiPath 4000 connection.
The parameter DISPTGNA activates the display of the trunk group name in
the event of incoming seizures if no name (e.g. no PERSI name in the case
of a network-wide call) is provided in the protocol.
• OpenScape4000/HiPath 4000 to OpenScape4000/HiPath 4000

connection:
Case a: Parameter in the AMO ZAND: DISPTGNA= YES
A check is made in the protocol for existing names. If the name field is
blank (Length=0) and the display allowed ("presentation allowed"), the
trunk group name is entered with "presentation allowed" (presentation
permission), regardless of the parameter INDNADIS, and can no longer
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
be subsequently overwritten in the network/system.

If a name is provided, but is labelled as "presentation restricted", the
name is not overwritten and remains declared as "presentation
restricted".
Case b:Parameter in the AMO ZAND: DISPTGNA=NO
No check is made in the protocol for existing names.
The string defined with the parameter DISPNUUN appears on the display
of the called party’s station.
• Connection with a third-party system (e.g. QSIG Protocol):

The parameter INDNADIS in the AMO ZAND serves to specify the check
mechanisms regarding the presentation permission ("presentation
allowed or restricted")
More recent protocols recognize several variations of "confidential line":
Via the parameter INDNADIS in the AMO ZAND, the name can be
displayed on the display of the called party, regardless of caller ID
suppression.
Case a: Parameter in the AMO ZAND: INDNADIS=YES
Numbers and names are checked for "presentation restricted" separately
and can thus be displayed independently of one another.
Furthermore, this setting also contains a check that compares the called
numbers and returned numbers with one another:
If the numbers are the same, the target number is also displayed, even if
the display is not permitted (confidential).
Case b: Parameter in AMO ZAND: INDNADIS=NEIN
Only the calling number is checked for "presentation restricted" and the
behavior for the name adopted, i.e. either the calling number and name
are displayed in the case of "presentation allowed", or both are
suppressed in the case of "presentation restricted". In this case, the string
that is entered with the parameter DISPNUUN and/or the outgoing trunk
group name in the case of DISPTGNA = YES for the called party can be
displayed.
• In the case of outgoing traffic, the route name is generally completed and/or
presented on the display, unless a name with "presentation allowed" is
returned from the destination. If no name is administrated in the AMO RICHT,
the trunk group name of the outgoing trunk group used is displayed if
DISPTGNA is set.
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
• The first system with DISPTGNA set completes the trunk group name and
this trunk group name may then be displayed if DISPTGNA= YES. Other
systems on the network which are transited no longer overwrite the trunk
group name.
• The parameters INDNADIS and DISPTGNA should be set identically in all

systems of a network group.
• The parameters INDNADIS and DISPTGNA should generally be set to "YES"
NOTE: Caller ID suppression can be achieved for all external EDSS1

connections per trunk - regardless of the subscriber configuration - with the
COT parameter LPRN (see description of COT parameter).
NOTE: The attribute LATTR=SUPPCPN (AMO LDAT) may not be used in

connection with confidential numbers and/or the suppression of the calling
party number, as suppression only takes place in the case of Transit Inter-
working (switching of the numbering plan)!
102.5.3.3 Generation (example)
• Configuring system-wide display of the trunk group name:
You must be in expert mode to administer the display of the trunk group
name.
command).
Use the AMO ZAND to set the display of the trunk group name:
CHANGE-ZAND:TYPE=ALLDATA2,DISPTGNA=YES;

Language
ZAND DISPTGNA d Bündelname im Display von Teilnehmer B
anzeigen
DISPTGNA e Display name of trunk group of extension
INDNADIS d Steuerung der Namensanzeige am Display des
B-TLN
INDNADIS e Control of display name at the display of
extension B
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm

Language
LDAT LATTR d KANZATLN
LATTR e LCR Attribute
102.5.4 Exceptions to Honoring Presentation

Restriction Indication
1. Parameter CIDBON (AMO ZAND)

If CIDBON=NO all attendant consoles on this system will only honor restricted
presentation indication for off-net calls. On-net calling parties that are marked
"presentation restricted" (display suppression is invoked) will have their name
and number displayed on the attendant console, if provided for in the
protocol.
2. Parameter in AMO-SBCSU TRACE=Y (e.g.: AMO SBCSU for called party);

the display of the number and the name of the calling party - regardless of
whether this involves a confidential subscriber or not - is generally permitted
in the case of incoming calls (the calling party set "presentation allowed" at
the called party for the "calling party".).
IMPORTANT: Setting the TRACE parameter to "Y" may violate privacy regula-
tions in some countries (e.g. United States).
• The parameter CIDBON refers to all VPLs of a physical node.
• 1. Configuring the function for attendant consoles:
You must be in expert mode to administer the function for attendant

consoles.
command).
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
Configure with AMO ZAND as follows:

CHANGE-ZAND:TYPE=ALLDATA3,CIDBON=NO;
• 2. Configuring the function for STN 7141:
Configuration Management --> Lines --> Station, enter station number

and Search. Select “Malicious call tracing” in the Basic 3 tab and save.
Set function using AMO SDAT as follows:

CHANGE-SDAT:STNO=7144,TYPE=DATA,TRACE=YES;

Language
SBCSU AMTFANG d Fangen eines Amtsgespräches erlaubt
TRACE e Malicious call trace allowed
ZAND ANHRIDNR d Auswertung der Anzeigeunterdrückung
CIDBON e Caller ID blocking for on net calls
102.5.5 Display Suppression for Analog and T1

Trunks (only US)
Analog and T1 trunks are incapable of delivering caller ID information to the

public network. However the serving Central Office (CO) has the capability to
generate a calling party number that has been assigned to the trunk group on
which the call originates. The calling party number generated by the public
network is known as Automatic Number Identification (ANI).
In order to block or unblock the generation of an ANI number by the CO, the Caller
ID Block/Unblock feature can optionally send - based on a new trunk attribute and
based on the existing trunk dialing method - the standard caller ID blocking or
unblocking access codes as a prefix to the destination address digits.
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
The COP parameter NAAT must be set in the case of outgoing analog circuits, so
that the CO prefixes can be sent as they are configured in the following example.
102.5.5.3 Generation (Examples for US)
The standard dial codes as understood by CO in US (according to North

American Number Plan) are:
For caller ID blocking: *67 (Usage with DTMF trunks)

1167 (Usage with DP trunks)
For caller ID unblocking: *82 (Usage with DTMF trunks)
1182 (Usage with DP trunks)
• Supplement COP with NAAT (for analog circuits):
Configuration Management --> System Data --> Trunk --> Class of

Parameter, enter COP number and Search. Select NAAT in the
parameter tab and save.
Set parameter NAAT using AMO COP as follows:

CHANGE-COP:COPNO=<copnumber>,PAR=NAAT;
• Change circuit at 1-1-55-0, so that none of the above-mentioned standard

access codes are sent:
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
Configuration Management --> System Data --> Trunk --> Trunk, enter
PEN and Search. Select the value NONE in the Analog Extensions tab
in the Caller ID Blocking/Unblocking Digits selection window and save.
Set parameter CIDDGTS using AMO TACSU as follows:

CHANGE-TACSU:PEN=1-1-55-0,CIDDGTS=NONE;
• Change circuit at 1-1-55-0, so that a called party number is prefixed by this

standard code for display suppression off in the case of non-confidential
subscribers:
PEN and Search. Select the value SEND82 in the Analog Extensions
tab in the Caller ID Blocking/Unblocking Digits selection window and
save.
CHANGE-TACSU:PEN=1-1-55-0,CIDDGTS=SEND82;
• Change circuit at 1-1-55-0, so that a called party number is prefixed by this

standard access code for display suppression on in the case of confidential
subscribers:
PEN and Search. Select the value SEND67 in the Analog Extensions
tab in the Caller ID Blocking/Unblocking Digits selection window and
save.
CHANGE-TACSU:PEN=1-1-55-0,CIDDGTS=SEND67;
• Change circuit at 1-1-55-0, so that the above-mentioned standard access

codes are sent, depending on request:
PEN and save. Select the value BOTH in the Analog Extension tab in
the Caller ID Blocking/Unblocking Digits selection window and save.

CHANGE-TACSU:PEN=1-1-55-0,CIDDGTS=BOTH;
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
CLIR on an Individual Subscriber Basis

Language
TACSU CIDDGTS d Unterdrückung der Anruferidentification
CIDDGTS e Caller ID blocking / unblocking
COP COPPAR d NAAT =Nordamerikanische analoge
Übertragung
COPPAR e NAAT = North american analog trunk
102.6 CLIR on an Individual Subscriber Basis

When the subscriber specific SDAT attribute SECRAGNT is set, for calls initiated
by this device the following scenarios apply:
• In case of local calls the calling party number is treated as hidden / secret
• In case of external calls, the calling party number is treated as hidden / secret,
unless PUBNUM is set for the calling party and the outgoing trunk, in which
case the PUBNUM is transported as calling party number.
• If the device is marked as SECRET or has dialed "secret call access code",
its number will not be transported at all.
• The parameter can also be used to suppress the display of calling party
number in Call Center.
A31003-H3170-S103-6-7620, 02/2019
anzun_cm_en.fm
CLIR on an Individual Subscriber Basis
A31003-H3170-S103-6-7620, 02/2019
cli_en.fm
Calling Line Identification (CLI) Translation
Feature description
103 Calling Line Identification (CLI) Translation

Certain features (e.g. call diversion and callback) do not work in mixed
OpenScape 4000/DX-networks because of existing problems with the backwards
translation of numbers (e.g. redirection party numbers) from DX-> OpenScape
4000.
The problem can be made worse by numbering schemes that are adopted. For
example where 2 companies merge.
702 DPNSS1 connections via PBXXX
OpenSca
pe 4000
node 001
B sets up a call
70 diversion to C
DX
700 702 B
A
OpenScape
4000 node
002
OpenScape 4000 DX
area code 7
C
703
DX area code 8
Figure 109 Mixed OpenScape 4000 - DX network
Figure 109 shows an example of a network where all the node ID’s (i.e. routing
codes) are of equal length. The DX network is represented as fictive OpenScape
4000 node 3 (for CLI purposes).
The customer requirement is that they can successfully CF to any extension

anywhere in the network. In addition callback to diverted to extensions will also
be successfully supported.
The problem with this arrangement, is that the Redirection number is returned to
node 1 as 703 #C, i.e. the DX network area code is missing. The OpenScape
4000 does not have the correct routing information if it needs to re-establish the
A31003-H3170-S103-6-7620, 02/2019
cli_en.fm
Calling Line Identification (CLI) Translation
call. In this instance even if the diversion had been performed by the DX,
OpenScape 4000 would have incorrect routing information if it needed to perform
a callback or circuit optimisation.

Solution as in the scenario depicted by Figure 109:
User A calls user B by dialling 8 702 #B.
KNMAT (which is active for all call set-ups) adds the routing digits of the calling
node (i.e. 700 for level 0 and 7 for level1) and 7700 #A is sent to node 702 and is
displayed at B.
Node 702 returns the digits 702 #B to node 1, where DGTPR in TDCSU adds 8
(i.e. the DX network area code) to the front of the string. This is displayed at user
A. This is required because the DX does not send a node code OpenScape 4000
can use and so KNMAT cannot prefix the incoming CLI.
If user B has CF to user C, then the diversion may take place, if it is performed by
the DX. However, the divert destination that is returned to node 1 is 703 #C.
Even if the diversion has successfully taken place, a problem arises in this
situation if the OpenScape 4000 attempts a callback or circuit optimization as it
does not have the correct routing information of the diverted to party and
therefore callback requests and optimization will fail.
Fig. 1 Example: The calling party dials 8-702-4711. Ext.4711 is forwarded to 8-

703-4712
The ISDX 702 send‘s the redirection party number as 7034712, without the
private network ac-cess code. OpenScape 4000 701 can not evaluate the digits
correctly and the call attempt fails,or even worse end‘s at a wrong destination.
Since the ISDX software can not be changed the OpenScape 4000 has to prefix
the redirection party num-ber with the private access code before presenting it to
digit analysis.
The private network access code is customer specific. In order to allow for
enough flexibilty it was decided to administer the access code on a B-channel
group basis.
Only ISDN trunks are affected by the feature.
A31003-H3170-S103-6-7620, 02/2019
optilog_en.fm
Call Log for optiPoint 410/420, OpenStage
Feature Description
104 Call Log for optiPoint 410/420, OpenStage
IMPORTANT: In case of OpenStage phones the following description is not valid

for OpenStage 60/80.
OpenStage 60/80 have their own internal call log with 30 entries. This call log is
always available and doesn’t have to be configured!
This feature is also known as call journal.
0089722333 Huber 
Busy 31.12.1999 17:19
0567478 Allgaier 
free 31.12.1999 18:19
For each entry, the following data Anrufliste

are stored: Rufjournal
Anrufjournal
• station number max. 22
digits 60%
• name (if available) max. 30

characters 80%
• date / time
• Info: free / busy / call state 100%

The last incoming and outgoing calls are logged for 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 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 characters
• date / time
A31003-H3170-S103-6-7620, 02/2019
optilog_en.fm
• Info: free / busy / call state

• The feature can only be used with optiPoint 410/420 and OpenStage 10/15/
20/30/40 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.
• 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
– A call is only logged in a CHESE caller list if it not answered by a member

of the CHESE, in other words calls for the executive, which are picked up
by the secretary, are not logged in the executive’s caller list. And vice
versa.
– If one CHESE member deletes an entry in the caller list (by calling the
original party back or manually deleting this entry), the entry is also
deleted for the other CHESE member.
– 2 or more executives are assigned to one secretary: When one caller calls
all executives one after the other, every executive gets an entry in its call-
log of not-answered calls.
The secretary gets all calls but only the last call is stored in its call-log
(update of time of call of the older entry in case of calls from the same
caller).
After answering/deleting the last call, the call-logs of the other executives
is not updated.
• A key can be assigned to query the call log. The LED is on when there are
new incoming calls.
• A "delete entire log" function (separate menu option) can be set up.
A31003-H3170-S103-6-7620, 02/2019
optilog_en.fm
Service Information
• A function can be set up so that the called party instead of the transferring
party is stored in the call log (originating number).
• 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.
• The call log is protected against unauthorized readout by the Chapter 108,
“Data Security at the Terminal” feature.
• The call log contents are retained after hard and soft restarts.
• Call log has only been implemented for voice services.

• For each terminal with display, space in memory must be generated in
DIMSU. For each memory space, approximately 1.1 KB is reserved.
• For each optiPoint 410/420 with 4-line display, memory for CALLOGS must
be allocated in DIMSU.
• 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 OpenScape 4000 call log should not be configured.
• This feature is not available for Cordless Multicell Integration and Hicom
Trading E.
• Die data are not stored on the hard disk (not RELOAD-proof).
104.4 Generation
104.4.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. Specify the number of stations with call log and 4-line display.
A31003-H3170-S103-6-7620, 02/2019
optilog_en.fm
Relevant AMOs
ADD-DIMSU:TYPE=USER,CALLOGS=n;
4. Assign the feature to a 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;
104.4.2 Set up menu option: delete call log

AMO ZAND Action OPTISET Parameter CALLOG = Yes;
104.4.3 Setup: save originating number on transfer

AMO ZANDE: TYPE=ALLDATA, SCALLOG = YES;
104.4.4 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 only protected if the COS is set to COSACT=2.
Note: See also Chapter 108, “Data Security at the Terminal”
104.5 Relevant AMOs

Language
DIMSU CALLOG d Anzahl der optiPoint Endgeraete mit Anrufliste
(Zweig User)
CALLOG e Number of optiPoint devices with call log
CALLOGS d Anzahl der optipoint-Endgeraete mit Scrolling
Mode für Anruferliste
CALLOGS e Number of optipoint devices with scrolling mode for
call log
FEASU ANRLSOPT d Anrufliste für optiPoint
CALOGOPT e Call log for optiPoint
A31003-H3170-S103-6-7620, 02/2019
optilog_en.fm
Relevant AMOs

Language
SBCSU RJOURNAL d Endgeraet mit Rufjournal:
VERSUCH: Nur erfolglose, ankommende
Verbindungen
ALLE: Alle ankommenden Verbindungen
CALLOG e Device with callog:
TRIES: only incoming calls that haven’t been
successful
ALL: all incoming calls
A31003-H3170-S103-6-7620, 02/2019
optilog_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
System Park
105 Call Parking

In previous versions the feature call park was linked to the feature call pickup,
when a pickup group was created the members can park a call within their own
pick up group. The system park feature is available with the directed call park
feature in addition to the original park function.
105.1 System Park
Call parked to

one of system
ISDN park slots
Station dials 0 Station dials park

Park code+slot 0-9 1 code+slot 0-9 to
2 reconnect to parked call
3
4
5
6
7
8
Attendant dials
9
Park code+slot 0-9

The System Park feature allows a station user or an attendant to place a trunk or
station connection into a system park slot. Once parked, the call can be retrieved
by the same station/attendant or another station/attendant.
The System Park feature is possible only during a stable two-party talk state.
The following devices have access to the System Park feature:
• Analog telephone
• Digital telephone (Keyset or DFT including CMI)
• Attendant
• ACWin (2Q or MQ)
The following devices can be parked:
• Analog telephone
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
System Park
• Digital telephone (Keyset or DFT including CMI)
• Functional devices
• CO trunk (analog and digital)
• TIE trunk (analog and digital

There are different variants to park or retrieve a call:
• One access code (park code + park slot number (0-9)) is provided for park
and retrieval to/from each system park slot.
• The subscriber dials the park code followed by the system park slot
number (0-9).
• If the call has been parked successfully,
• the parking subscriber receives confirmation tone,
• the used system park slot number is displayed, if the parking

subscriber has a display option.
• If the requested system park slot is currently in use,
• the parking subscriber receives dial tone again,
• the parking subscriber dials the park code followed by another system
park slot number (0-9) without going on-hook.
• If the call cannot be parked (e.g. all system park slots are in use), the
parking subscriber receives reorder tone.
• This variant can be used by analog telephones, Keyset and DFT with/
without display option.
• Optional for Keyset and DFT with display:
• To park a call to system, the subscriber uses a System Park key and the
next available system park slot is selected automatically by the system
and displayed.
• If the call has been parked successfully, the parking subscriber receives
confirmation tone.
• If all system park slots are in use, the parking subscriber receives reorder
tone.
• When idle to retrieve a parked call, the subscriber uses the System Park
key and enters the system park slot number (0-9) manually.
• Optional for Keyset and DFT without display:
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
System Park
• To park a call to system, the subscriber uses a System Park key and
enters the system park slot number (0-9) manually.
• If the call has been parked successfully, the parking subscriber receives
confirmation tone.
• If the requested system park slot is currently in use,
• the parking subscriber receives dial tone again,
• the parking subscriber uses the System Park key and enters another
system park slot number (0-9) without going on-hook.
• If the call cannot be parked (e.g. all system park slots are in use), the
parking subscriber receives reorder tone.
• When idle to retrieve a parked call, the subscriber uses the System Park
key and enters the system park slot number (0-9) manually.
• For Attendant/ACWin:
• To park a call to system, the attendant/ACWin dials the park code

followed by the system park slot number (0-9). Additionally, it can use the
Direct Destination Selection (DDS) key which has been programmed with
the system park access code plus the system park slot number (0-9).
• If the call has been parked successfully,
• the attendant/ACWin receives confirmation tone,
• the used system park slot number is displayed.
• If the requested system park slot is currently in use but another system
park slot is available, the system will place the call in the alternate system
park slot and the system park slot number is displayed where the call has
been parked.
• A call left on park is recalled to the parking party after a time-out of a System
Park recall timer or to the Attendant/ACWin dependent upon the system
parameter (COT parameter SPAH) and the state of the parking party at time-
out (idle, busy or out of service).
105.1.3 Service information

• The System Park feature is a local feature and not available network-wide.
• The system contains 10 System Park slots (0-9), which cannot be configured
via AMO-DIMSU.
• 100% of the telephones have access to the System Park feature except
functional devices.
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
Directed Call Parking
105.2 Directed Call Parking

The feature direct call parking permits a user to park a two-party connection
directly with another terminal (directing device).
Parked Extension
Parking Extension Parked to

Extension
The user (any terminal type) is able to use Directed Call Park to park a call at
another extension whether local or network wide. The call can be parked onto a
free or busy extension.

The user with a call that they wish to park on another extension, dials a feature
code followed by the extension number of the user on whom the call is to be
parked:-
If the called party is idle, the call is held at the called party. It does not ring the
terminal. The called user dials reconnect to connect to the held call. If the
called user does not pick-up the call within a configured period of time, the
held call will ring the extension.
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
If the called party is busy, they will receive audible and visible (if possible)
notification of the call and the call will be held. The called user will dial
reconnect to connect to the held call. If the called user fails to answer the call
within a configured period of time, the call will be treated as a call that has
been held too long and may be re-directed to the parking party.
105.2.3 Feature Operation by User Terminal

The Directed Call Park feature can be used to park a call to a designated
extension anywhere within the network,whether the extension is idle or busy, but
providing that the park position is idle and the call is able to be parked e.g. the
caller to be parked is not barred from being held.
The parked call can be picked up at the parked to terminal by dialling ’reconnect’,
or from any other extension within the network by invoking Directed Call Pick-up
and then keying the directory number of the parked to extension.
Note. It will not be possible to park a call to the pilot number of a hunt group.
The following exceptions apply:-
It is a requirement that a user will not be able to park a call from the Attendant; or
park a call to an Attendant position.
It will not be possible to invoke park from a functional terminal.
The following detailed feature invocation descriptions include the parking (A

party), parked (B party) and parked to (C party).
105.2.3.1 Directed Call Park Feature Invocation from Anates
A) Parking user
From an active call i.e. talk state, the user enters consultation state, receives
dial tone and keys the feature access code. User then dials the directory
number of the desired location to which the call will be parked;
OR
From an active call i.e. talk state, the user enters consultation state, receives
dial tone and keys the feature code for self-park. The call is parked and the
user hears positive acknowledgement tone and is free to make further calls;
OR
User hears negative acknowledgement tone and the user can now return to
the calling party or can re-try the feature (e.g. attempt to park to a different
extension); or the user can use another feature.
B) Parked user
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
Once parked, user receives ’holding’ tone as appropriate to the system. User
can now only wait for re-connection or hang up.
C) Parked to user
If the parked to user is idle when the call is parked, then the user will be given
no indication (the requirement is that the call is parked without ringing the
terminal). However, whilst the park-timer is running the user will be given
special dial tone if they go off-hook. After the park-timer expires then the
terminal will be alerted if idle, or when they becomes idle.
The parked to user cannot receive further incoming calls, but can make
outgoing calls.
If the parked to user is busy when the call is parked, then the user will be given
audible notification in the form of camp-on tone.
In the case of parking to a busy user, the call is transferred into camp-on and
is then treated as a normal camp-on call.
Pick-up of parked calls

There are 2 ways that a user can connect to a parked call;
1. Reconnect; and
2. Directed Call Pickup.
From the station at which the call is parked, the user can connect to the
parked call by dialling the feature code for ’reconnect’.
A user can connect to the call from any other eligible station in the network by
invoking the feature Directed Call Pickup, and then keying the directory
number of the parked to extension.
105.2.3.2 Directed Call Park Feature Invocation from Terminals

(with display)
For users with terminals without display refer to invocation from Anates
There are 2 ways that an user (with display) can invoke the feature:
• From talking state (Dialogue menu); this is only for a first call. Feature
invocation is not possible from a consultation call (i.e. secondcall);
• With feature access code (for a first call only).
From Dialogue menu
A) Parking user
From an active call i.e. talk state (first call only),the user scrolls to the feature
with the right arrow key until the display shows the new selection directed call
park
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
This is accepted by ok (tick button)the user is then prompted to dial a park

location (parked to station
The user then keys the station number of the parked to extension.
OR
The user dials the code for their own station to self park to park the call on
their own station The call is parked and the user is free to carry on making
normal calls
The user is provided with advice that a call is parked
B)Parked user
the display of the parked terminal shows “please wait” and the parked call gets no
indication of whether the call is parked at the parking station or not
C) Parked to user
If the parked to user is idle when the call is parked,then the user will be given no
indication (audible or visual). However, whilst the park-timer is running the user
will be given special dial tone if they go off-hook. After the park-timer expires then
the terminal will be alerted if idle, or when becomes idle.
If the parked to user is busy when the call is parked, and the parked to user has
Call waiting set to on then the call is transferred into camp-on and is then treat as
a normal camp-on call.
The displays are the same if the user invokes the direct call park feature by
feature access code
Pick up of parked calls
Connecting to a parked call is possible in the following ways:-

From any eligible end device by invoking the feature Directed Call Pickup,and
then keying the directory number of the parked to extension.
From the station at which the call is parked by keying the ’reconnect’ code.
From the station at which the call is parked by invoking ’reconnect’ from the
Idle menu, or from the dialling state (Dialogue menu).Note the option
“Reconnect “ is only offered if a call is parked on the terminal
105.2.3.3 Directed Call Park Feature Invocation from AC
The following description is applicable to AC4 on Upoe interface
The Attendant needs to be connected to the call in order to invoke the feature.
The Attendant then enters consultation state by pressing the consultation key and
dialing the feature code.
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
The Attendant keys the directory number of the terminal to which the call is to be
parked and if sucessful the call is released from the attendant console.
Call Pickup
The attendant can reconnect to the parked call by using the direct call pickup
feature code
Recall
If the parked call is recalled to the Attendant then it is queued as for a normal
recall
105.2.3.4 Directed Call Park Feature Invocation from ACWin

(MQ)
The Attendant needs to be connected to the call in order to invoke the feature.
The Attendant then enters the consultation state by pressing the consultation key
and dials the feature code. Note. Only invocation from feature code is possible.
The Attendant keys the directory number of the terminal to which the call is to be
parked.
The display information presented to the Attendant is <FC><DN> in the status

field.
If the call is successfully parked, then the attendant will receive the message
’PARKED’, the call is released from the Attendant and the loop key becomes free.
If the call is not successfully parked, then the attendant will receive the message
’NOT POSSIBLE’, and the call will remain on hold.
in the OpenScape 4000 it is not possible for the Attendant to Retrieve the parked
call, since the OpenScape 4000 Retrieve solution is not based upon Pickup. The
attendant will be able to ’reconnect’ to parked calls by invoking the feature
Directed Call Pickup.
Parked Calls Recalled to Attendant
When a parked call is recalled to the attendant, for whatever reason, then it will
be presented to the source button assigned for recall and queued if necessary.
To connect to the recalled party, the Attendant clicks on the recall source button
or presses the recall source key on the P.C. keyboard

Connections from conference calls and calls in consultation state cannot be
parked.
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
Call Park Within a Pickup Group
The Parked to extension at the time of being parked to can be either free or busy.
This feature is only available for the service Voice.
For network-wide use of the feature Cornet NQ at issue 2.2 is required
105.2.5 Interworking between devices
Terminal/Set Parked Parking Parked to

All digital devices X X X
CMI X X X
AC/Centralised AC - X -
Float Anate - - X
Hunt groups or ACD numbers - - -
DSS1 Terminals X - -
DPNSS1 Gateway (PBXXX) X X X
All remaining ISDN devices (Voice X
service only)
105.3 Call Park Within a Pickup Group

This is the original call park feature with which a call park slot is created per pick
up group

Digital telephones require a Park key with an led.
A call in talk state can be parked by pressing the Park key. All members of the
same pickup group as the parking terminal recieve a visual indication via the park
key led flashing.
A call can be retrieved from Park by any member pressing the park key
After a congfigurable time-out the Parked call recalls back to the parking station
and signals as a group pickup call ,depending on the pickup group settings,on
other members of the pickup group.
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
105.4.1 System Park

Assign System Park access codes (park code + system park slot number):
ADD-WABE:CD=<XYZ0>,DAR=PARK;
Note: This command assigns all 10 System Park access codes XYZ0-XYZ9 in
one single step.
• The standard key layout 7 contains the System Park key. A digital telephone
(Keyset or DFT) with access to the System Park feature via System Park key
could be configured with standard key layout 7. However this, as standard ,is
for a 3 button digital telephone
Assign System Park key to digital telephone (Keyset or DFT) which is
configured with standard key layout different to7:
CHA-TAPRO:STNO=4711,STD=n,DIGTYP=OPTIT19,KYm=SPARK;
• Change timer value for System Park recall timer:
CHA-CTIME:TYPESWU=CP2,SYSRCPAR=x;
• Optional, assign COT parameter SPAH to COT class n of an used digital or
analog trunk:
CHA-COT:COTNO=n,COTTYPE=COTADD,PAR=SPAH;
105.4.2 Directed Call Park

• Releasing the feature for the system
CHANGE-FEASU:TYPE=A,CM=DCPA;
• Enable the direct call pickup feature ( to connect to a call parked on another
station)
CHANGE-FEASU:TYPE=A,CM=DIRCPCKP;
To allow the user to use the feature direct call park feature access codes are
required
• Adding code for direct call parking

ADD-WABE:CD=<cd>,DPLN=<no>,DAR=DCPA
• Adding the code to allow users to self park a call
ADD-WABE:CD=<cd>,DPLN=<no>,DAR=SELFPA;
• Adding the code so that the parked call can be accepted i.e. reconnected
ADD-WABE:CD=<cd>,DPLN=<no>,DAR=RECONNPA;
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
There are three timers that need to be configured for recalls for direct call parked
calls
• The park timer T1 which is started with parking on a free station changed as
follows
CHANGE-CTIME:TYPESWU=CP2,DCPA1=20 */20 seconds*/
• The recalling timer T2 for the feature direct parking is added as follows
CHANGE-CTIME:TYPESWU=CP2,DCPA2=30 */30 seconds*/;
The timer T3 which is started when a call is parked to a busy station is as
follows
CHANGE-CTIME:TYPESWU=CP2,DCPA3=5 */5 seconds*/
Timers DCPA1/DCPA2 are consecutive ie DCPA2 begins when DCPA1 expires.
DCPA2 also begins on the expiry of DCPA3.
Note regarding user indication and timer interreaction.
During DCPA1 a call is parked to an idle station, the parked to station recieves no
indication the call is parked, the Parked station recieveds hold tone.
Upon the expiry of DCPA,1 DCPA2 begins. The Parked To station recieves
ringing and the Parked station Ringback tone. When DCPA2 expires the call
recalls to the Parking station.
DCPA3 begins when the call is parked to a busy station. During this time the
Parked To station recieves no indication of the parked call the Parked call
recieves hold tone. Upon expiry of DCPA3, DCPA2 begins as before. The user
indication depends upon the Parked to ststion having Camp on enabled. If camp
on is enabled then the Parked call will indicate with a beep tone on the Parked To
station as any camped on call would do.The Parked station would at this time
hear ring back tone. If camp on is not enabled at the Parked To station then the
call remains in the same state as it was during the DCPA3 timer until the expiry
of DCPA2 after which it recalls to the Parking station.
For Network wide use of the feature the following changes needed to be made in
the class of trunk
• To enable the feature network wide

CHANGE-COT:COTNO=<no>,COTTYPE=COTDEL,PAR=DCPA;
Note: DCPA is for barring the feature to a system that cannot support directed
call park
• To enable the feature to work with Attendants

CHANGE-COT:COTNO=120,COTTYPE=COTADD,PAR=RCL;
/* Recall to AC if user hangs up in Consultation call
CHANGE-COT:COTNO=120,COTTYPE=COTDEL,PAR=RCLS;
/*suppression of Recall to AC/*
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
Relevant AMOs
105.4.3 Park within a Pickup group

• Configure a pickup group
• Enable a Park key on the telephone

CHA-TAPRO:STNO=4711,STD=n,DIGTYP=OPTIT19,KYn=PARK
105.5 Relevant AMOs

Language
WABE PARKEN d Gespräche parken/wiederholen auf/von
System Parkplatz
PARK e call park and retrieve to/from system park slot
DCPA d parken eines tln bei einem bestimmten tln
DCPA e Code to park a call on another user
SELFPA d parken eines teilnehmers bei sich
e Code to park a call at ones own station
RECONNPA d wiederverbinden mit dem geparkten
teilnehmer
RECONNPA e Code to reconnect to a parked call on own
station
AUNGEZ d gezielte anrufuebernahme
PUDIR e Direct call pickup code to reconnect to call
parked on a different station
TAPRO SPARK d System Park Taste
e system call park key
PA d Park taste
PARK e Park key
CTIME SYSRCPAR d System Park Wiederanrufzeitglied
e system park recall timer
DCPA1 d gezieltes parken - zielteilnehmer ist frei
e Directed call park park destination is idle
DCPA2 d gezieltes parken - wiederanruf beim
parkenden
e Recall timer of the parked party
DCPA3 d gezieltes parken - zielteilnehmer ist besetzt
e Directed call park park destination is busy
COT SPAH d nach Wiederanrufzeitgliedablauf wird ein
geparkter oder gehaltener Teilnehmer zum
Vermittlungsplatz weitergeleitet
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
Relevant AMOs

Language
SPAH e on recall timer expiry, a parked or held party
is routed to the attendant
A31003-H3170-S103-6-7620, 02/2019
system_park_en.fm
Call Parking
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
connect_key_en.fm
Connect Key
Feature Description
106 Connect Key

A digital feature telephone or Keyset has limited function keys. To make access
to multiple functions from one key possible the Connect Key is introduced.
CONNECT KEY combines the following functions
• Toggle in consultation and between foreground / background
• Pick up a camp-on call
• Pick up a call from a pick up group
Where toggle and pick up are possible at the same time the toggle function
supersedes pick up.
106.2 User Interface

No access code is required for the feature Connect Key. The feature is
implemented by a new Key in AMO TAPRO.
When presented with a group call the user can pick up the call by pressing the
connect key. (pick up function)
When in consultation with a third party the user can toggle between the held party
and the consulted party by pressing the connect Key (Toggle Function)
Whilst in talk state the user can connect to a waiting call (if camp on at that station
is set) by depressing the Connect Key. (Camp -On pickup)
From the service menu function the user can display the key function but
reprogramming of the key from the service menu will not be possible.

The feature Connect Key is a pure Software feature and requires no hardware
changes.
Only one appearance of the Connect Key is possible per terminal
A31003-H3170-S103-6-7620, 02/2019
connect_key_en.fm
Connect Key

The Connect key function is valid for optiPoint telephones .
• Add a Connect Key on key 19:

CHANGE-TAPRO:STNO=7445,DIGTYP=OPTIT19,KY19=CNCT;
106.5 Relevant AMOs
AMO Parameter Spache/ Beschreibung/Description

Language
TAPRO TDxx d Neuer taste CNCT
TAPRO KYxx e New key CNCT
IMPORTANT: The AMO description of the Connect Key defines it as Connect to

call on hold.
A31003-H3170-S103-6-7620, 02/2019
ctls_en.fm
Feature Description
107 Controlled Trunk and Line Selection

See also Chapter 196, “CTLS - Controlled trunk and line selection network-wide”
and Chapter 195, “CTLN - Prevent controlled line and trunk selection in an
external system”.
With the feature Controlled Trunk and Line Selection (CTLS) you can seize and
check trunk circuits and subscriber line circuits selectively by directly entering the
appropriate PEN.
CTLS is available for trunk and tie lines as well as SLMA and TMOM connections.
CD + Pen
• Direct checking with one COS only (CTLS).
• Direct checking of ports and individual B

channels.
• Network-wide feature.

With CTLS, authorized users can seize analog and CAS trunk circuits, digital B
channels and also SLMA and TMOM connections (only announcement devices)
by entering (dialing) the PEN and, if necessary, the B channels. VMX connections
on SLMA and digital trunk circuits belonging to nailed connections cannot be
selectively seized. 
By analyzing the reception of predefined tones the authorized user can recognize
the state of the PEN or the terminal to be tested.
A31003-H3170-S103-6-7620, 02/2019
ctls_en.fm
Effects on other Features
Analog trunk circuits, CAS trunk circuits and digital circuits can be trunk and tie
lines.
CTLS can be used in OpenScape4000/HiPath 4000 networks. The seizure of

trunks or subscriber line circuits by entering the PEN is only possible within
CorNet-NQ networks.
If in transit connections an outgoing analog, CAS or trunk circuit is seized by

entering the PEN, the dialing of the PEN cannot be continued in the next PBX.
Regardless of the following PBX type, the connection can be established by

dialing a station number. The signaling method configured for the seized circuit is
used.
If in transit connections within a Cornet-NQ network the outgoing circuit is seized

by dialing a station number and not by entering the PEN, the dialing of the PEN
cannot be resumed in the next PBX.
IMPORTANT: This feature only applies for the VOICE service.
107.2 Effects on other Features

Connection establishment using CTLS has the following restrictions (in contrast
to LCR):
• If SLMA stations are seized, any active transfers of ringing, call forwarding no
answer, call pickup groups and intercept cases are disregarded, provided the
SLMA station is configured in the same PBX as the station used for CTLS or
if the PBX where the SLMA station is configured is reached via CorNet-NQ.
• Hunting group number: Any attempt to reach a station by dialing the hunting
group number is rejected if the station is configured in the same PBX as the
station used for CTLS or if this PBX was reached via CorNet-NQ. 
Master hunting group: The master is seized if the hunting group number is
dialed. The hunting group function is ignored, if the station is configured in the
same PBX as the station used for CTLS or if this PBX was reached via
CorNet-NQ.
• If an interim destination reached using CTLS is busy, the connection can only
be reestablished, after the caller goes on-hook. Rerouting is not performed.
• A CTLS entry cannot be saved for number redial. Strings, and parts thereof,
with a maximum length of 22 characters can be saved under destination and
repertory keys.
• Callback on busy and free is not possible.
A31003-H3170-S103-6-7620, 02/2019
ctls_en.fm
User Interface
• During an active CTLS connection all third-party features such as

consultation hold, transfer, broker’s call, conference, etc.) are blocked for the
dialing station.
• It is not possible to establish a CTLS connection from a third-party

connection.
• The destination reached using CTLS cannot activate any third-party features
during the connection if the destination is configured in the same PBX as the
station using CTLS or if this PBX was reached via CorNet-NQ.
107.3.1 Data editing for CorNet-NQ

• The A station (checking party) first enters:
<Code CTLS>
After this code is identified and the CTLS classmark was successfully checked, a
digit counter is initialized. If the user has no authorization any further inputs are
rejected (’NOT AUTHORIZED’ and a corresponding tone).
• With proper authorization the user enters

#<PEN># or #<PEN>*
A ’CTLS’ flag, as well as a ’PEN’ flag, are set and the digit counter is incremented
depending on the length of the PEN. These values together with the entered PEN
are stored in the CPB and transmitted to CorNet-NQ, depending on the interface
to be defined.
• The successful seizure of the previously entered PEN initiates the following
procedure: 
The test is terminated, if another 
’#’ is recognized (not after an *, see below). If
<PEN># or # <PEN>*
is entered again, the PEN is saved in the CPB and then transmitted to CorNet-
NQ, together with the updated digit counter and the ’PEN’ flag, depending on the
interface to be defined.
• If the last character entered was a ’*’ then a station number must now be
entered:
<Station number>#
A31003-H3170-S103-6-7620, 02/2019
ctls_en.fm
User Interface
This station number is saved in the CPB and then transmitted to Cornet-NQ,
together with the updated digit counter and the ’Station number’ flag, depending
on the interface to be defined.
The actual node checks for the following:
• If the DAR of this station number established in WABE leads to a trunk, then
the trunk is only seized and the station number transmitted, if the parameter
CTLS is set in COT for the corresponding trunk group.
• If the DAR established in WABE leads to a station (’STN’), the following is

checked:
– If the station number is a hunting group number, the number is not

transmitted and the test is terminated.
– If the destination number is configured in the same PBX as the A station

or if the destination switch was reached via CorNet-NQ, the destination is
dialed as usual. Call forwarding, call forwardings on no answer, call
pickup groups and intercepts, however, are disregarded.
– The ’Station number’ flag is set. The station number is saved in the CPB,
together with the updated digit counter and the flag. After the station
number is transmitted, the test is terminated.
If the last entered character was a

’#’
then the procedure is continued as described under A), provided a PEN was
specified.
Notes:
1. General notes:
– If the end criterion ’##’ of the CTLS test is entered, all trunks concerned
remain seized. The tone injected after the entry of the first ’#’ remains
audible. A ringing status can change to call status and a call status
reached before the input of the second ’#’ also remains established.
– If a station number is entered with a destination other than in the current

PBX, then LCR is no longer avoided. Call charges are accrued, if this
station number leads to a CO trunk!
– The terminals used for the CTLS test are protected agains camp-on for
the test duration.Emergency override / disconnect during CTLS Test is
possible
2. Notes on terminal key behaviour
A31003-H3170-S103-6-7620, 02/2019
ctls_en.fm
User Interface
– CTLS is used for line testing. Therefore, only digit and repertory keys are
supported. One station number or, alternatively, one PEN can be stored
per repertory key. The use of other keys will be rejected, in particular an
attempt to establish a 3-party connection.
– AC: If the AC is called during start-of-dialing for the CTLS test and the
operator presses either the Personal key or the OPR key to accept this
call, the CTLS test is terminated. If, however, the AC is called during a
CTLS call, the call can be accepted by pressing the Personal or OPR key.
The CTLS call remains in the background and can be resumed by
pressing the DIAL key.
– During the CTLS test, the CLEAR key on the AC has the same effect as
the RELEASE key, i.e. the CTLS test is terminated.
– With the exception of the repertory keys and the other keys mentioned
above, all other AC keys are rejected.
– DIGITE: If the DIGITE is called during start-of-dialing for the CTLS test
and the user presses the "Call waiting" key to accept this call the CTLS
test is terminated. If, however, the DIGITE is called during a CTLS call,
the waiting call can be accepted by pressing the "Call waiting" key. The
CTLS call remains in the background and can be resumed by pressing
the TOGGLE key. Conference and call transfer are not possible.
– With the exception of the repertory keys and the other keys mentioned
above, all other DIGITE keys are rejected.
– With ANATE, the callback key for establishing a 3-party connection is

rejected. All keys, with the exception of the digit keys, are not supported.
3. Notes on networking:
– In a network, CTLS connections are signaled as such, if possible. If, e.g.

the last entry for a CTLS test is a station number which leads to the digital
network via a DAR and the trunks seized using LCR are "CTLS capable",
then the CTLS test task is transmitted via these trunks. A log printout is
generated in every transit node.
– If a breakout to an analog network is achieved by entering the PEN, the

test is terminated. In this state, in the best case (i.e. the trunks could be
seized by CP), the information signalled inband depends on the type of
CO trunk. With signalling without dialing tone from CO (e.g. MFC-R2)
there are no audible tones. In this case, dialing to CO should be allowed
(COT CTLS set on the trunk), e.g. to reach a test tone transmitter.
However, this should only be a temporary solution and not become
the rule as this procedure allows abuse as call charges can no longer be
assigned to the originating party. The charges can only be assigned at a
later date by a comparison of the test log printouts.
A31003-H3170-S103-6-7620, 02/2019
ctls_en.fm
User Interface
– The test possibilities are also restricted for trunk circuits which need
complex information from the LCR in order to be seized (e.g. CIS
signalling with ANI). This information is normally not available for CTLS
seizures.
107.3.2 Provision of path selection

In the incoming seized PEN the digit counter is reset and the protocol delivered
by CorNet-NQ is evaluated by converting the digit string into a PEN, if the ’PEN’
flag is set.
The test is terminated in the following cases:
– if the end criterion ’##’ is recognized. There is no system reaction.
– after the station number entered under <Station number># is transmitted;

the system reaction configured for end-of-dialing is carried out;
– if the entered station number is a hunting group number (will not be

transmitted); the NU tone is injected;
– if the station number exceeds 22 digits; the configured system reaction is

carried out;
– if the syntax of the entered PEN is incorrect; the NU tone is injected;
– for the defined error cases (PEN busy, not existent or invalid for CTLS,
PEN is defective) the configured tones are injected (busy tone, NU tone,
negative acknowledgement tone);
– if the outgoing seized trunk was an analog trunk, a CAS or a trunk circuit
and further PENs were dialed; the NU tone is injected;
– if a station number which leads to a circuit is transmitted and the CTLS

parameter is set in the COT for the outgoing trunk group; the system
reaction configured for end-of-dialing is carried out;
– after the evaluation of the station number and before the circuit is seized,
if the CTLS parameter is not set in the COT of the outgoing trunk group;
the connection is backwards released to the originating node;
– if an SLMA terminal (exception:VMX) is administrated on a selected PEN.

The corresponding tones are injected, depending on the station status.
IMPORTANT: If analog, CAS or trunk circuits are seized without station number,
the reception of the dialing tone cannot be guaranteed, e.g. with MFC/R2 dialing
or analog tie lines. These cases require specialist knowledge of the paths to be
tested.
A31003-H3170-S103-6-7620, 02/2019
ctls_en.fm
Service Information
107.3.3 System Reactions

For user guidance, a tone is injected after every PEN that is selected. The
following cases are discriminated:
• PEN x seizes CorNet-NQ circuit: First ring tone from the reached PBX
(FRNGBK);
• PEN x seizes analog or CAS tie trunk: Dialing tone from the reached PBX, if
dialing tone injection is configured for this tie trunk;
• PEN x seizes trunk circuit: The proper CO dial tone is injected;
• PEN x seizes SLMA circuit: Connection of the corresponding terminal

(exception: VMX). With anate the ring tone is injected and the ring tone is
injected at the calling party (RNGBK);
• PEN x seizes line circuit. The then dialed station number is not transmitted
because the CTLS parameter is not set in COT (NU)
• PEN x or destination of station number is busy: busy tone (BUSY);
• PEN x is non-existent, invalid for CTLS or overdefined: NU tone is injected

(NU);
• PEN x is defective/out of order: Negative acknowledgement tone (NACK);
If a station number is entered and the connection is established via transit PBXs,
these PBXs do not transmit any tones.

• The user interface is uniform for the selection of lines and SLMA circuits. For
the necessary dialing information the AMOs TACSU, SCSU, TSCSU and
TDCSU are displayed.
• Any CTLS input must start with the specification of a PEN.
• Within a CTLS input it is possible to change once from the input of PENs to
station number dialing.
• The system reactions after every input of a PEN inform the user of the status
of the dialing destination or any operating errors.
• In addition to authorization assignments, CTLS is classed as a service case

and therefore every call of the application is logged. A protocol message is
output for every application (maintenance message F4624 in text form).
A31003-H3170-S103-6-7620, 02/2019
ctls_en.fm
Service Information
• In the originating node, this protocol message contains the station number of
the user and the selected PEN. In every transit node, which was reached via
CorNet-NQ, this message contains the incoming seized PEN, and the PEN
or station number used to reach the outgoing seized trunk.
• All messages have a code which identifies them as being generated by

CTLS.
• The user’s station number is not the administrated station number of the used
terminal, if the user has identified himself on this terminal using PIN network
wide.
• The authorization assignment for CTLS using DMS/CM-Win is prevented.
• CTLS is provided for use on digital terminals. This includes also the AC.
• CTLS is also possible on Anate, provided it can handle DTMF or an external

DTMF transmitter is used. i.e. a hand held tone sender.
• Functional terminals (e.g. set600), DSS1 termnals and CMI terminals are
excluded.
• An authorized user can activate this authorization by network-wide

identification on other terminals. Transmission of the CTLS authorization
using PIN network-wide via CorNet-NQ is supported.
• CTLS is used to seize trunks avoiding LCR. This means
– CDR is not possible,
– the blocking of destination numbers is circumvented and
– ITR and Closed User Groups are ignored.
• After outgoing seizure of a trunk using CTLS the station number transmission
is prevented by default. Transmission is only possible, if the newly introduced
COT parameter ’CTLS’ is set in the corresponding trunk group. This also
applies for CorNet-NQ circuits, as a breakout to CO via PBXXX and DPNSS
is possible here.
• A "normal" dialing-in via trunk or tie lines and subsequent use of CTLS as
DISA feature is prevented.
• An entered station number is only transmitted after the entry of a # (en-bloc

dialing). If the selected PEN has previously seized a cutdial circuit, a correct
connection establishment cannot be guaranteed.
A31003-H3170-S103-6-7620, 02/2019
ctls_en.fm
1-1-25-00 1-1-49-23
F4624
 F4624
**88 # 1 01 025 00 #  1 01 049 23 # 

or
**88 # 1 01 025 00 *  7241 # 
7140 7241
: Waiting for system reaction (tones).
The testing circuit 7140 can establish the following test connection:
a) via tie line and PEN of station 7241
b) via tie line and station number of station 7241
After the connection to the second PBX is established, a continuous tone is

injected. Then the remaining digits can be entered.
This selection can be made via several nodes.
• Configure Wabe:
ADD-WABE:CD=**88,DAR=CTLS;
• Set the authorization:
ADD-COSSU:NEWCOX=xx,AVCE=CTLS;
A31003-H3170-S103-6-7620, 02/2019
ctls_en.fm
• Set COT for the trunks:

ADD-COT:COTNEW=xx,PAR=CTLS,INFO=”Selective line seizure”;
• Set "TESTLN" in WABE:
If a test station is to be tested in the CTLS test, the DAR TESTLN with the
CPS 10&11 must be set for this station. For the outgoing trunk the COT CTLS
must also be set.
ADD-WABE:CD=**89,CPS=10&11,DAR=TESTLN;
• Set the test tone length
With CTLS the test tone injection is timer controlled. The duration of the test
tone can be set using the CP timer CTLS1 (AMO CTIME, TYPESWU=CP).
CHA-CTIME:TYPESWU=CP,CTLS1=20; /*inject test tone for 20
seconds
AMO Parameter Sprache/ Beschreibung/ Discription

Language
COSSU GLTA d gezielte Leitungs- und Teilnehmerwahl
CTLS e controlled trunk and line selection
CTIME GLTA1 d gezielte Leitungs- und Teilnehmeranwahl timer 1
CTLS1 e controlled trunk and line selection timer 1
GLTA2 d gezielte Leitungs- und Teilnehmeranwahl timer 2
CTLS2 e controlled trunk and line selection timer 2
COT GLTA d gezielte Leitungs- und Teilnehmerwahl
WABE GLTA d gezielte Leitungs- und Teilnehmerwahl
A31003-H3170-S103-6-7620, 02/2019
disp_mailbox_callback_en.fm
Feature Description
108 Desktop Callback Idle Display Option

It is possible to display the mailbox (callback messages) when the phone is in idle
state. This feature is only for digital phones. The phone will display the mailbox
instead of the idle display, but only if there are callback messages stored.

While the phone displays the mailbox, it can perform the following actions:
• If the phone goes off hook, the mailbox is canceled and the phone can start
to dial (instead of the dial tone the announcement "You have a message" is
offered). When the phone goes on hook, the mailbox display is offered.
• The phone can start to dial. The mailbox is canceled and the dialed digits are
displayed. After ending the call, the mailbox display is offered.
• A phone which is configured as a keyset can select a line, by pressing the

corresponding line key. The mailbox is canceled and the phone can start to
dial (instead of the dial tone the announcement "You have a message" is
offered). After ending the call, the mailbox display is offered.
• In this state, the phone can receive calls. The mailbox is canceled and the
number/name of the caller appears on the display. If the call isn't answered
and the caller ends the call, the phone returns to idle and the mailbox display
is offered. The phone can also answer this call by going off hook (or by
pressing the line key for keysets). After the call is finished and the phone
returns to idle, the mailbox display is offered.
• In this state, the user can scroll through the messages ("Next entry?" option
), can execute the callbacks ("Call originator?" option), can delete the
messages ("Delete?" option) or can leave the mailbox ("Cancel?" option).
The following configurable feature keys (with AMO TAPRO) are supported during
the phone displays the mailbox:
• Name key (NAME)
• Speed dial key (SPDI)
• Call-log key (CALLOG). If the call log key is pressed, then the call log will
appear on the display. After the call log is canceled, the mailbox display will
be offered again.
A31003-H3170-S103-6-7620, 02/2019
disp_mailbox_callback_en.fm
• Call pickup key (PU). If the phone is configured in a pickup group, then it can
pickup the call for a member of the pickup group. The display of the phone
will not show for which member of the group the call is (mailbox display will
remain on).

This feature is activated with a AMO SDAT attribute for each phone in the system.
Only the phones marked with this attribute will display the mailbox in idle display.
• Activation:
CHA-SDAT:STNO=XXXX,TYPE=ATTRIBUT,AATTR=MBXDSPID;
• Deactivation:
CHA-SDAT:STNO=XXXX,TYPE=ATTRIBUT,DATTR=MBXDSPID;
XXXX - is the number of the digital phone.
108.4 Relevant AMOs

Language
SDAT MBXANZRU d Mailbox-Anzeige im Ruhezustand
MBXDSPID e Mailbox display in idle state
A31003-H3170-S103-6-7620, 02/2019
dict_en.fm
109 Dictation Equipment DICT

• Assign TMOM module
• Assign code for dictation equipment
AD-WABE:CD=key-num,DAR=DICT;
• Add class of trunk
AD-COT:PAR=NTON;
• Add class of parameter
AD-COP:PAR=SACK&BR64&LSUP&IDP1;
• Add trunk group
AD-BUEND:NO=number;
• Add trunk circuit
AD-TSCSU:COTNO=number,TGRP=number,DEV=DICT,COPNO=number,
SUPV=SUPV2,ACKT=SZACK2,DTYPE=2;
• Assign a route to the dictation equipment
AD-RICHT:TYPE=CD,CD=key-num,SVC=VCE,TGRP1=number;
A31003-H3170-S103-6-7620, 02/2019
dict_en.fm
A31003-H3170-S103-6-7620, 02/2019
tlns0_en.fm
Functional Bus
110 Digital Station with S0 Interface

Bus configurations can be set up with various devices at the S0 interface (STMD
or STHC and STMD2) with PNT-E (SLMO24, SLMOP, STHC, etc.).
Device types
• Functional terminals are operated with the protocols SBDSS1 or SBNIBRI.
You can connect up to three devices with different services and protocols but a
single call number to the S0 bus. Only one protocol is permitted per service.
The introduction of MSN call numbers lets you extend the number of call numbers
at the S0 bus beyond the above limits (only applies to functional terminals and
therefore not to all other types of configuration described below - see also chapter
"EURO ISDN Terminals", Section 120.2.1, “Multiple Subscriber Numbers (MSN)
on the S0 Bus”.
You can configure the following connection options:
• direct
• over PNT E (Private Network Terminator) at the Up0/E or ANSI-U NTBA
• as an "external" extension only at STMD (over public paths)
Configuration types
• Functional Bus (FBUS)
• S0 interface at the UP0/E port (see Chapter 133, “PNT E for Connecting
Standardized S0 Telephones”).
110.1 Functional Bus

You can connect terminals to the functional bus with the SBDSS1 or NIBRI
protocol. You can only connect non-voice dial-in devices. You can only configure
one call number per bus and one terminal per service (see also the following Note
on MSN call numbers).
A31003-H3170-S103-6-7620, 02/2019
tlns0_en.fm
Bus Extenders
E-DSS1 S0-Bus S
set 600 T
M
D
E-DSS1
FAX
E-DSS1
DEE
Figure 110 Functional bus (configuration example)
IMPORTANT: The introduction of MSN call numbers lets you reach functional
terminals at the main number or at a new call number. 
You can also connect additional functional terminals for the same services as
already configured at the main number to the bus and reach them at a new call
number (see also "EURO ISDN Terminals", Section 120.2.1, “Multiple Subscriber
Numbers (MSN) on the S0 Bus”.
Configure the terminals for this example as follows:

ADD-
SBCSU:STNO=number,OPT=FBUS,CONN=DIR,DVCFIG=SET600&FAX&DTE,COS1=n
umber,COS2=number,LCOSV1=number,LCOSV2=number,LCOSD1=number,LCOS
D2=number,SPROT=SBDSS1,FPROT=SBDSS1,DPROT=SBDSS1;
110.2 Bus Extenders
110.2.1 Adding NV Services to the Functional Bus

The services can only be assigned to a particular call number that already exists
for example, functional services with OPT=SVC (the result remains an FBUS).
A31003-H3170-S103-6-7620, 02/2019
tlns0_en.fm
Bus Extenders
DSS1 S0-Bus S
set 600 T
300 M
D
DSS1
300 FAX
DSS1
300 DEE
Figure 111 Functional bus (expansion example)
ADD-SBCSU:STNO=300,OPT=SVC,DVCFIG=DTE,DPROT=SBDSS1;
IMPORTANT: If there are MSN call number configured at the FBUS, the new
service is automatically added to their scope of service (see "EURO ISDN
Terminals", Section 120.2.1, “Multiple Subscriber Numbers (MSN) on the S0
Bus”.
110.2.2 Adding MSN Call Numbers to the Functional

Bus
The introduction of MSN call numbers lets you reach functional terminals at the
main number or at a new call number. 
You can also connect additional functional terminals for the same services as
already configured at the main number to the bus and reach them at the bus’s
new call number (see also "EURO ISDN Terminals", "Section 120.2.1, “Multiple
Subscriber Numbers (MSN) on the S0 Bus”).
A31003-H3170-S103-6-7620, 02/2019
tlns0_en.fm
Bus Extenders
set 600 S0-Bus

DSS1
300
301
DSS1
300 S
FAX
301 T
M
D
301
DSS1
301 FAX
Figure 112 Functional bus with MSN call numbers (expansion example)
Add an MSN call number to the existing functional bus with:

ADD-SBCSU:STNO=301,OPT=MSN,MAINO=300;
110.2.3 Deleting Devices at the S0

You may only delete the main number of a device last.
• You need one delete job for every call number.
• You can delete individual services for a call number. 

If there are MSN (extension) numbers configured, the deleted service is
automatically removed from their scope of service. If you delete the last
functional service at the main number, all MSN (extension) numbers
belonging to the bus are automatically deleted.
• To delete the entire bus, create a delete job containing all configured call
numbers with SVC=ALL. 
If there are MSN (extension) numbers configured, you must delete these first
with SVC=MSN.
A31003-H3170-S103-6-7620, 02/2019
tlns0_en.fm
Bus Extenders
• In general, the conditions that apply to the AMO SCSU also apply to group
assignments (for example, call pickup groups, executive/secretary systems,
hunt groups, etc.). You must first remove the call numbers to be deleted from
the group assignments.
• Existing station/device assignments (created with the AMO TGER) are

automatically deleted.
• The device to be deleted can first be deactivated with the AMO DSSU or
controlled with the parameter OFFTYPE so that deactivation is performed by
the AMO SBCSU.
A31003-H3170-S103-6-7620, 02/2019
tlns0_en.fm
Bus Extenders
A31003-H3170-S103-6-7620, 02/2019
dr_en.fm
Feature Description
111 Direct Station Selection (DSS)

Devices with Direct Station Selection (DSS) are automatically assigned a memory
when configured with the AMO SBCSU. The proportion of name keys to DSS
keys may be freely selected per telephone. The difference between DSS and
name keys is that on DSS keys, the busy condition of the destination is displayed
via a LED. If the destination is called despite being busy, call waiting is
automatically activated and the destination is called when no longer busy.
By pressing the flashing DSS key (while the destination is being called), it is
possible to take the call.
The DSS key must be assigned to one of the freely programmable keys to be able
to make a destination entry. 
This may be achieved with the AMO TAPRO, either by assigning a standard key
layout or by assigning the key function individually.

• DSS destinations must be internal stations. Stations within the network are
also possible (see Chapter 79, “CHESE/ Team Functions Network-wide”).

• DSS keys are configured as follows, either with a standard or an individual
key layout:
CHA-TAPRO:STD=number,KY01=DSS,...; (standard key layout with
DSS keys) 
CHA-TAPRO:STNO=number,STD=number,KY01=DSS,...; (individual
key layout)
• A DSS destination is configured as follows:

ADD-ZIEL:TYPE=DSS,SRCNO=number,KYNO=number,DESTNOD=number,
DEV=param;
A special feature is implemented in conjunction with the integrated secretary
system. If an executive has his secretary as the destination on a DSS key and the
secretary activates the substitute secretary, the destination entry on the
executive’s phone is automatically assigned to the substitute and is re-assigned
to the secretary again when deactivated.
A31003-H3170-S103-6-7620, 02/2019
dr_en.fm
Relevant AMOs
111.4 Relevant AMOs

Language
TAPRO SNU d Standardnummer
STD e Map standard
TD0x d Tastenfunktion Taste x
(x = Nummer der Taste am EG z.B. 1-19)
KY0x e Key function for button x
( x=number of button e.g. 1-19)
TLNNU d Teilnehmer-Rufnummer
STNO e Station number
ZIEL TYP d Verzweigungsparameter
DR = Direktruftaste
TYPE e Desired destination option
DSS = Direct station selection key
QLRUFNU d Quellen Rufnummer
SRCNO e Station number of source
TASNU d Tastennummer
KYNO e Key number
DZLRUFNU d Zielrufnummer für Direktruf
DESTNOD e Destination number for DSS
A31003-H3170-S103-6-7620, 02/2019
disable_flash_en.fm
Overview
112 Disable Flash on Analog Phones
112.1 Overview
This feature allows the disabling of the hookflash function.
With this feature the user is

prevented from feature access
using a flash key or switchook
hookflash
Hotel Lobby
The feature is already available in the U.S.and allows for the administration of
“featureless” analog telephones for selected users by ignoring any hookflash
signal. Station users in various enviroments such as hospitals, elderly care
facilities and some hotels often do not require features to be used, in these cases
telephone sets without hookflash keys can be provided,and by administration any
hookflash signal from the telephone switchooks can be ignored.

The disable flash on Analog phones feature provides via administration the
capability to disable the flash capability from an analog device. This feature
includes a new classmark to disable the detection of a hookswitch flash by an
analog telephone. When this classmark is assigned via a parameter used for
such analog telephones, any attempt by a station user with that authorization to
activate a hookswitch flash shall result in one of two states:
– An attempted hookswitch flash of short duration (less than disconnect

time) is ignored
– An attempted hookswitch flash of longer duration (greater than

disconnect time) results in an on-hook condition

The only difference for an Analog phone is the removal of the hookflash capability,
therefore all functions that first require a hookflash are disabled (e.g. consultation,
transfer).
A31003-H3170-S103-6-7620, 02/2019
disable_flash_en.fm
Service Information

The disable flash on Analog phones feature is intended for the global
marketplace.

• How to disable the Hookflash on an Analog line
CHA-SCSU:STNO=2300,FLASH=NO;
112.6 Relevant AMOs

Language
SCSU FLASH d Bei Einstellung NEIN steht die Hookflash-
Funktion auf analogen Telefonen nicht zur
Verfügung
FLASH e Set to NO will not allow the Analog device to
hookflash
A31003-H3170-S103-6-7620, 02/2019
analog_ops_en.fm
Disable Message Waiting Lamps on OPS
Overview
113 Disable Message Waiting Lamps on OPS
113.1 Overview
OPS Off Premises Station is an application for where there are requirements for
an analog telephone to be located an extended distance from the telephone
system. Analog telephones can be utilized in exposed areas where the
instrument may be open to abuse.
e.g. A large campus environment with guard stations located around the perimiter
could utilise OPS analog telephones.
1
SLMA Board
Analog phone
. T1 mux
.
.
.
. TMDN
24 Board
Analog phone

The external interfaces to the Off Premises Station (OPS) shall be T1 interface
(TMDN-H) and a line interface (SLMA). Message Waiting Indication via lamp shall
not be supported on an OPS line (port), due to what is deemed to be hazardous
voltage requirements.
The introduction of the TMDN board is not covered in this document as it is a

separate feature .

The user interface for this feature remains the same as the existing Analog
devices with the excepion of the MW Lamp.
A31003-H3170-S103-6-7620, 02/2019
analog_ops_en.fm
Disable Message Waiting Lamps on OPS
Service Information

The disable MW Lamps on an OPS feature is intended for the global marketplace.
113.5 Generarion (Example)

• How to configure an Anate as an SLMA Off Premise Station (OPS)
NOTE: Ensure that the DHPAR is NOT set to MWLED
CHA-SCSU:STNO=2300,CONN=OPSSLMA;
• How to configure an Anate as an T1 Off Premise Station (OPS)
NOTE: Ensure that the DHPAR is NOT set to MWLED
CHA-SCSU:STNO=2300,CONN=OPST1;
113.6 Relevant AMOs

Language
SCSU ANSCHL d EXTSLMA
CONN e OPSSLMA - The OPS is connected to an
SLMA card
SCSU ANSCHL d EXTT1
CONN e OPST1 - The OPS is connected to an T1
(TMDNH) card
SCSU DHPAR d
DHPAR e This should NOT be set to MWLED
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Overview
114 DNIS (Directory Number Identification Services)
IMPORTANT: This document describes only the administration of Directory

Number Identification Services (DNIS) services for different configurations.
114.1 Overview
The ability to route calls depending on the called party or calling party has been
up to now a feature of flexrouting (ACD) with the I.M switch. The feature is made
available based on both source (SID/ANI in the U.S.) routing and destination
(DNIS in the U.S.) routing without the need to configure ACD routing in the
system.
7744 Call routed by DNIS/

ANI or combination
Central office
converts
number
(DNIS)
Munich
User dials 1-800-333 3653
Service call
89-722-32177
This is sent as SID (CLIP)
If required an identifier for this Display depending on
number settings and SID/CLIP
appears in top line of display presentation
114.2.1 Definition of Tables
Table Usage
DNI Directory Number Information table: stores routing and display information
concerning source (SID/ANI) and called party (DNIS) digit strings.
GDTR General Digit Translation table: stores the translation information
concerning SID/ANI and non-sequential DNIS numbers.
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Service Information
Table Usage
GDTRSR General Digit Translation Service Rule table: stores the information
concerning the DNIS GDTRRULE for Primary Rate Interface trunks.
DIDCR Direct Inward Dialing (DID) Digit conversion table (AMO DIDCR).
114.2.2 Definition of Terms
Term Definition
DNIS(Dialed Number Identification Service) This feature allows special call routing and
special call displays based on the original
called (dialed) number.
SID/ANI: (Station Identification / Automatic This Feature allows special call routing
Number Identification) and special call displays based on the
calling number.
ANI The Automatic Number Identification is a
public network customer billing number
stored at the public network central office
serving the originator of the call. The ANI
may be delivered when the SID number is
not available.
SID The Station Identification is the calling
party number of the station originating the
call.
DIDBLK Incoming Direct Inward Dialing (DID)
blocking.
114.2.3 AMO Relationships

DNIS digit conversion features requires interaction with the following AMOs:
• AMO TDCSU & AMO TACSU, for Trunks
• AMO BUEND, for Trunk Groups
• AMO DNIT, Directory Numbering Internal Translations
• AMO DIDCR,Direct Inward Dialing Conversion
• AMO WABE, Dialing Plan.

This feature is released for the US and international market.
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
114.4 Generation
114.4.1 AMO WABE

Define a set of numbers to be in the numbering plan (WABE) and should be
reserved for Station Terminations (STN(s)) for the DNIS services
ADD-WABE:CD=645000&&645009&&,DAR=STN;
114.4.2 AMO TDCSU (Digital), AMO TACSU (Analog )

Trunk Configuration
With AMo’s TDCSU and TACSU it is possible to define whether the incoming
trunk information is routed via a DIDCR table , a GDTR table or no table selection,
based on trunk and trunk group configuration parameters.
When configuring a digital trunk with AMO-TDCSU for ISDN-PRI or Cornet-NQ

trunks the new parameter TRTBL is used to select DIDCR or GDTR digit
conversion tables.
SIDANI= YES forces SID/ANI additional signalling to obtain the Called Party
(ANI) or Billing Party Information (SID/BN) if not presented in original Call Setup
message. If SID/ANI is required and not send by incoming side the call will be
released.
TGRP field is indirectly related for this feature to determine GDTR Table rule
index in the later stages of DNIS processing.
Digital Trunk configuration using AMO-TDCSU:

0,COTNO=20,COPNO=20,DPLN=0,ITR=0,COS=1,LCOSV=1,LCOSD=1,CCT="NQ
TEST",PROTVAR=ECMAV2,SEGMENT=8,TRTBL=GDTR,SIDANI=N,ATNTYP=TIE,DE
V=S2CONN,BCHAN=1&&30,BCGR=1,TGRP=96;
This configuration forces GDTR conversion with no SID/ANI requirement with
using TGRP=96 for a Cornet-NQ trunk.
Analog trunk configuration using AMO-TACSU with TRTBL,RULEIDX, TGRP

(Example only)
ADD-TACSU:PEN=1- 1-121-
0,COTNO=240,COPNO=240,DPLN=0,ITR=0,COS=220,LCOSV=1,LCOSD=1,TGRP=
240,TRTBL=DID,RULEIDX=6,DEVTYPE=TT,DEV=TSEMCON;
This configuration uses DIDCR conversion table 6. AMO-BUEND GDTRRULE
has no effect.
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
114.4.3 AMO BUEND

Example to show GDTR rule
Create Trunk Group (AMO BUEND):
ADD-BUEND:TGRP=96,NAME="DNIS 1",NO=30,RSV=N,TRACENO=0,
ACDTHRH=*,PRIONO=2,TDDRFLAG=ON, GDTRRULE=220,ACDPMGRP=0;
This trunk group will use GDTR table 220.
114.4.4 GDTR Conversion for only Called Party

Number
Create DNIS Routing with DRTD (with/without ACD) for GDTRRULE 220. This
would create a digit conversion based on Called Party Number only. SID/ANI
information would have NO effect of termination point selection
7340 AMO DNIT TBL =GDTR,GDTRULE=220....
Central office AMO DNIT TBL =DNI,ITRTDN=645001...

converts number
(DNIS)
TG 96
Points call <caller id><buend
to GDTR
SERVICE
rule 220
7345
User dials 1-800-333 3653 Display depending on settings from AMO DNIT
Example
Callers who route into the system via Trunk Group 96 with digits 7340 are routed
to internal number 7345 with the second line of the display showing “Service”.
• Add the routing and display parameters for internal rerouting number 645001
ADD-
DNIT:TBL=DNI,INTRTDN=645001,ROUTING=DRTD,DISPLAY="SERVICE",
ACD=N,TARGET=7345;
• Add Digit patterns which will be routed to Internal Director Number (INTDN)
645001
ADD-
DNIT:TBL=GDTR,GDTRRULE=220,DGTSTR=7340,INTRDN=645001,SVCDATA=
NOREQU;
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
This provides a digit conversion based on GDTR tables with Called Party
number of 7340 to terminate to STNO=7345 for any incoming call from trunk
group attached to GDTR rule 220. Also DNIS display defined with DISPLAY field
to be presented to termination on display line 2
• To allow for all other digit patterns to terminate on station 7344 additional
entries are made in the GDTRRULE 220 and a DNI entry in AMO DNIT
ADD-DNIT:TBL=DNI,INTRTDN=645002,ROUTING=DRTD,DISPLAY="NORMAL
SERVICE", ACD=N,TARGET=7344;
645002
ADD-
DNIT:TBL=GDTR,GDTRRULE=220,DGTSTR=#,INTRDN=645002,SVCDATA=NOR
EQU;
This provides a digit conversion based on GDTR tables with digit pattern of any
number( # means any number presented as called party number )to terminate to
STNO=7344 for any incoming call from trunk group attached to GDTR rule 220.
Also DNIS display defined with DISPLAY field to be presented to termination on
display line 2
Any SID/ANI/Clip information proivided would be presented in line 1 of the

display together withthe trunk group name if set to do so. (AMO ZAND,ALLDATA2
parameter DISPTGNA )
Note this is not using ACD to route the call as specified by ACD= N in AMO DNIT.
To enable the display parameter text to appear on the display of the telephone the
following parameter is required in AMO SBCSU
CHANGE-SBCSU:STNO=7340,OPT=OPTI,DNIDSP=YES;
IMPORTANT: There is a fixed relationship between the GDTR rule and the type
of routing.
GDTR rules 129 and above are used for DNIS routing. Here the DGTSTR
parameter is the CALLED party number and the wildcard # represents any
CALLED party number.
With GDTR rules used for SID /ANI routing (1-128) the parameter DGTSTR
represents the CALLING party number. The wild card * can be used to represent
any calling party digit and the # character represents any calling party
number.
The use of the wild card # in the DNIT table for called party number (GDTR rule
129 and above) can lead to the complete DDI range being routed by GDTR rules.
If this is not required and only specific numbers within a DDI range are to be
routed by GDTR then omit the wildcard # entry in the DGTSTR parameter. With
this setting only those numbers matching entries in DGTSTR will be further
processed all other DDI numbers will route as normal.
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
114.4.5 GDTR Conversion for Called Part Number and

SID/ANI info
Here the incoming call is routed by the dialled number (DNIS) but with additional
routing and display information depending on the calling party number.
This example defines Called party Number conversion then possibly additional
conversion for SID/ANI
7340 AMO DNIT TBL

Central office =GDTR,GDTRULE=220....
SVCDATA=SID,DGTSTR= 7340,
converts
INTRDN=645001
number
(DNIS)
TG 96
AMO DNIT TBL
User dials 1- gdtrule=220 =DNI,ITRTDN=645001..
800-333 3653 ROUTING=DRTSA,SARULE=110
TARGET=7345,ACD=N,
49 89 89400 DISPLAY=”HELPDESK”
7445
AMO DNIT TBL=GDTR,GDTRULE=110

DGTSTR=498989300****,INTRTDN=6
45003
AMO DNIT
TBL=DNI,INTRTDN=645003
ROUTING=SA,DISPLAY=”NODE 400”
ACD=N,TARGET=7345
Display depending on settings NODE 400

from AMO DNIT HELPDESK
7345
In the example above any caller with the caller ID of 498989400xxxx will be
routed to station 7345 and will present 2 lines in the display ,line 1 being the
display of a known caller
• Set rule number in BUEND to connect Rule to Trunk and Trunk Group
CHA-BUEND:GDTRRULE=220,TGRP=96;
• Add the routing and display information for a known caller
ADD-DNIT:TBL=DNI,INTRTDN=645003,ROUTING=SA,DISPLAY="NODE
400",ACD=N,TARGET=7345;
• Add the rule to verify any caller from 498989400
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
ADD-
DNIT:TBL=GDTR,GDTRRULE=110,DGTSTR=498989400****,INTRTDN=64500
3,SVCDATA=NOREQU;
ADD-
DNIT:TBL=DNI,INTRTDN=645002,ROUTING=DRTSA,DISPLAY="HELPDESK
",ACD=N,TARGET=7345,SARULE=110;
ADD-
DNIT:TBL=GDTR,GDTRRULE=220,DGTSTR=7340,INTRDN=645002,SVCDATA=SID
;
This should provide a digit conversion based on GDTR tables with digit pattern
7340 to terminate to STNO=7345 and if SID/ANI /CLIP information matches 110
the station will receive the display:
NODE 400
HELPDESK
or if SID/ ANI/ CLIP information DOES NOT match rule 110 the display is:
<caller id><buend name>
HELPDESK
In this example there is a digit conversion for the called party number.
It is possible to only alter the routing dependent on the SID /ANI / CLIP
information i.e the Calling Party Number
This requires an entry of a GDTR rule for DNIS routing (129 and above) as a trunk
group cannot be pointed to a GDTR table used for SID/ANI routing (1-128) in this
case a Wild card could be required for the DNIS entry (#) to allow for any dialled
digits.
IMPORTANT: The use of digit stings with wild card entries e.g # can be
considered. As calls are pointed to the DNIT table from the trunk group there is a
possibility several different digit strings are recieved as Called Party Number. If
normal DDI is required then the # should be omited and a separate entry in DNIT
is required for specific called party numbers.
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
114.4.6 DNIT table GDTRSR

In the previous examples the GDTR rule has been selected by the GDTRRULE
parameter in AMO BUEND. In practice this restricts the changes to the routing as
this parameter can only be changed if the trunk group is empty. The normal
practice is to define in AMO DNIT a GDTRRULE depending on the trunk group
and the type of service used.
There exists in AMO DNIT a table, the GDTRSR table, here it is defined per
service and per trunk group which GDTRRULE is to be used.
Example
Callers who route into the system via Trunk Group 96 (ISDN) with digits 7340 are
routed to internal number 7345 with the second line of the display showing
“Service”.
• Add the trunk group for the ISDN trunk

ADD-BUEND:TGRP=96,NAME="DNIS
1",NO=30,RSV=N,TRACENO=0,ACDTHRH=*, PRIONO=2,TDDRFLAG=ON,
GDTRRULE=0,ACDPMGRP=0;
• Change the GDTRSR table entry for trunk group 96 and service NONE
(ISDN)
CHANGE-DNIT:TBL=GDTRSR,TGRP=96,DNISRULE=220,NETSVC=NONE;
• Add the routing and display parameters for internal rerouting number 645001
ADD-
DNIT:TBL=DNI,INTRTDN=645001,ROUTING=DRTD,DISPLAY="SERVICE",
ACD=N,TARGET=7345;
645001
ADD-
NOREQU;
This provides a digit conversion based on GDTR tables with Called Party
number of 7340 to terminate to STNO=7345 for any incoming call from trunk
group attached to GDTR rule 220. Also DNIS display defined with DISPLAY field
to be presented to termination on display line 2
• To allow for all other digit patterns to terminate on station 7344 additional
entries are made in the GDTRRULE 220 and a DNI entry in AMO DNIT
ADD-DNIT:TBL=DNI,INTRTDN=645002,ROUTING=DRTD,DISPLAY="NORMAL
SERVICE", ACD=N,TARGET=7344;
645002
ADD-
DNIT:TBL=GDTR,GDTRRULE=220,DGTSTR=#,INTRDN=645002,SVCDATA=NOR
EQU;
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
114.4.7 GDTR Digit Conversion (DNIS) without SID/

ANI signalling without PRI services
Add TMDN-H card as PRI trunk for USA, trunk group (BUEND) 96 with
GDTRRULE =0
• PRI TMDN-H Card configuration:

ADD-BCSU:PER,1,1,67,"Q2196-X ",1,"0",,,,,,A;
• Trunk Group Configuration:
ADD-BUEND:96,"PRI BOCA RATON
DNIS",60,N,0,*,2,ON,GDTRRULE=0,0;
• Set trunk group 96 to route to GDTRRULE 220 for service NONE
CHANGE-DNIT:TBL=GDTRSR,TGRP=96,DNISRULE=220,NETSVC=NONE;
• Trunk Configuration:(Example only)
Functional Fields to note: PROTVAR, TRTBL, SIDANI
0,COT=99,COP=99,COS=1,LCOSV=9,LCOSD=9,CCT="PRI-
DNIS",PROTVAR=ATT4ESS ,SEGMENT=1,TRTBL=GDTR,SIDANI=N ,NNO=1-
1-
99,TGRP=96,SRCHMODE=CIR,DEV=S2COD,BCHAN=1&&10,BCNEG=N,BCGR=1,
LWPAR=2;
• Create DNIS Routing with DRTD without ACD for GDTRRULE 220
ADD-DNIT:TBL=DNI,INTRTDN=645003,ROUTING=DRTD,DISPLAY="MC
DONALD’S",ACD=N,TARGET=7345;
ADD-DNIT:TBL=DNI,INTRTDN=645002,ROUTING=DRTD,DISPLAY="BIG
MACS",ACD=N,TARGET=7344;
645002&645003
ADD-
NOREQU;
ADD-
DNIT:TBL=GDTR,GDTRRULE=220,DGTSTR=771*,645003,SVCDATA=SID;
This can provide a digit conversion based on GDTR tables with digit pattern 7340
to terminate to STNO=7345 and digit patterns “7711-7719” to terminate STNO
7344 for any incoming call from trunk group attached to GDTR rule 220. Also
DNIS display defined with DISPLAY field to be presented to terminating side.
114.4.8 GDTR Digit Conversion (DNIS) with SID/ANI

signalling without PRI-Services for USA-PRI Trunks.
Configuration of trunk and trunk group parameters are as above
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
Configure DNIT routing and display for known caller

ADD-DNIT:TBL=DNI,INTRTDN=645005,ROUTING=SA,DISPLAY="MAJOR
CUSTOMER",ACD=N,TARGET=7345;
Configure SA rule to verify a known caller
ADD-
DNIT:TBL=GDTR,GDTRRULE=110,DGTSTR=5619231687,INTRTDN=645005,SVCD
ATA=NOREQU;
• Configure the DNI table entry and link to sa rule 110
ADD-DNIT:TBL=DNI,INTRTDN=645002,ROUTING=DRTSA,DISPLAY="SALES
ORDER",ACD=N,TARGET=7345,SARULE=110;
• Configure the GDTR rule 220 to allow any dialled digits
ADD-
DNIT:TBL=GDTR,GDTRRULE=220,DGTSTR=#,INTRDN=645002,SVCDATA=SID
114.4.9 GDTR Digit Conversion (DNIS) with SID/ANI

signalling with PRI Services for USA-PRI Trunks for
ACD call.
The ACD Configuration is not shown here. the decision to route to an ACD group
is made with the parameter ACD = Y/ N . The AMO DNIT branch changes
depending on the selection
• Create DNIS routing with SID/ANI as DNIT entry for known customer display
information on line 1 of the display to route to routing control group 100
ADD-DNIT:TBL=DNI,INTRDN=645004, ROUTING=SA, DISPLAY="LINE 1",
ACD=Y, RCG=100, PRI=10, OVRPRI=1, AUDSRCID=3, THRSHLD=20;
• Create GDTR SID/ANI Rule 112 to veryfy caller from 5619231687
ADD-
DNIT:TBL=GDTR,GDTRRULE=112,DGTSTR=5619231687,INTRTDN=645004;
ADD-DNIT:TBL=DNI, INTRTDN=645003, ROUTING=DRTSA, SARULE=112,
DISPLAY="LINE 2", ACD=Y, RCG=100;
• Create GDTR Rule 212 For USA PRI Megacom-800 Services () 
using trunk group # 96
ADD-
DNIT:TBL=GDTR,GDTRRULE=212,DGTSTR=561800000,INTRTDN=645003,SV
CDATA=SIDPREF;
CHA-DNIT:TBL=GDTRSR,TGRP=85,DNISRULE=212,NETSVC=INWATS;
This configuration will do digit conversion for INWATSVirtual Connections when
digit string 561800000 as called party information is received with calling party
number 5619231687 the call will route to RCG 100
If calls are not INWATS then they will follow the CALLED Party routing
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
114.4.10 GDTR Digit Conversion for Cornet-NQ PRI

Trunks.
There is no special configuration in TDCSU except always set SIDANI=NO.
Cornet-NQ always provides calling party information in call setup message. US
PRI configuration is applicable as defined in previous sections.
Note: Although there is no SID/ANI signalling necessary for Cornet-NQ and SID/
ANI information exists in call setup message, SID/ANI conversion is applicable.
to Cornet-NQ too
114.4.11 Without DNIS feature configuration

If no digit conversion to be configured (neither DID nor GDTR)
1. For digital trunks analog trunks

For digital trunks - AMO-TDCSU - TRTBL=GDTR,SIDANI=NO;
For analog trunks - AMO-TACSU - TRTBL=GDTR,RULEIDX=0
• Trunk Group (BUEND) - For analog and digital trunks

AMO-BUEND GDTRRULE=0;
• Set GDTRSR table entry for all services to 0
CHANGE-DNIT:TBL=GDTRSR,TGRP=96,DNISRULE=0;
114.4.12 DIDCR Digit Conversion without services for

analog trunks.
Note: No SID/ANI signalling required for analog trunks.
• Create the DIDCR Table - 1 with total digits 5 delete digits 3. This provides
last two digits to be used to determine the final destination.
ADD-DIDCR:1,5,3;
• Add conversions based on last 2 digits to DIDCR Table-1
CHA-DIDCR:DID,1,87,61097;
This provides a numbering conversion of ddd87 -> 61097, .. , ddd99->71099 etc.
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
• Assign Analog Trunk for DID conversion Table - 1.

CHA-TACSU:PEN=1-1-121-0,TRTBL=DID,RULEIDX=1;
This provides all calls with 5 digits to be truncated to the last two digits from the
look up table-1, Last Two Digit indexes 87,88,89,97,98,99 will be routed to
destinations defined above and rest of the calls will keep original dialed numbers
to route the call.
114.4.13 DIDCR Digit Conversion with SID/ANI

signalling with Trunking Services for USA-T1 Trunks.
• Create 1st DIDCR conversion table
Table-1 Total Digits=6 Delete Digits=4
ADD-DIDCR:1,6,4;
• Add digit conversion based on last 2 digits
• Set 2nd DIDCR Table Total Digits=6 Delete Digits=4
ADD-DIDCR:2,6,4;
• Add conversions based on last 2 digits
• Attach DID Table 1,2 to service types FX (foreign exchange),VPN (Virtual
Private Numbering)
CHA-DIDCR:SRT,1,FX,1
CHA-DIDCR:SRT,1,VPN,2;
• Assign T1 Trunk for DID conversion service rule Table - 1.
ADD-TDCSU: PEN=x-x-x-x,TRTBL=DIDCR, SRTIDX=1,SIDANI= Y,
DEDSVC=FX,
ADD-TDCSU: PEN=y-y-y-y,TRTBL=DIDCR, SRTIDX=1,SIDANI= Y,
DEDSVC=VPN,
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Generation
After this configuration PEN=x-x-x-x will use DIDCR Table -1 for all Foreign
Exchange Services and PEN=y-y-y-y trunk will use DIDCR Table-2 for all VPN
services.
114.4.14 DID call blocking DIDBLK

This feature will disable incoming calls to the stations if the station DID blocking
feature is active.
• Change station Class of services (COS) with Add Voice Feature of DIDBLK
CHA-COSSU:COS,23,,,,,,AVCE=DIDBLK;
This will activate DID Blocking on this station.
114.4.15 Call Routing when no CLI present

Feature Description
Routing of an incoming call depending on the calling party number requires an
entry of a GDTR rule for DNIS routing.
With GDTR rules used for SID /ANI routing (rules 1-128) the parameter DGTSTR
represents the CALLING party number. The wild card * can be used to represent
any calling party digit and the # character represents any calling party number.
Generation
For the following configuration, an incoming call to 8887 with caller ID of
498989400xxxx will be routed to RCG 103.
ADD-DNIT:TBL=DNI,INTRTDN=8884,ROUTING=SA,SARULE=0,DISPLAY="NODE
400",ACD=YES,RCG=103,PRI=64,OVRPRI=0,AUDSRCID=0,THRSHLD=*,REVCHA
=FORB;
ADD-
DNIT:TBL=GDTR,GDTRRULE=110,DGTSTR=498989400****,INTRTDN=8884,SVC
DATA=NOREQ;
ADD-
DNIT:TBL=DNI,INTRTDN=8887,ROUTING=DRTSA,SARULE=110,DISPLAY="SERV
ICE",ACD=YES,RCG=23,PRI=64,OVRPRI=0,AUDSRCID=0,THRSHLD=*,REVCHA=
FORB;
Additionally it is possible to configure a GDTR entry in order to route incoming
calls without caller ID to a group of extensions defined by the customer. 000000
is defined now as the "no CLI" string for DGTSTR parameter in ADD-
DNIT:TBL=GDTR....
ADD-DNIT:TBL=DNI,INTRTDN=8884,ROUTING=SA,SARULE=0,DISPLAY="NO
CLI",ACD=YES,RCG=103,PRI=64,OVRPRI=0,AUDSRCID=0,THRSHLD=*,REVCHA
=FORB;
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Relevant AMOs
ADD-
DNIT:TBL=GDTR,GDTRRULE=110,DGTSTR=000000,INTRTDN=8884,SVCDATA=NO
REQ;
ADD-
DNIT:TBL=DNI,INTRTDN=8887,ROUTING=DRTSA,SARULE=110,DISPLAY="SERV
ICE",ACD=YES,RCG=23,PRI=64,OVRPRI=0,AUDSRCID=0,THRSHLD=*,REVCHA=
FORB;
For the above configuration, any incoming call to 8887 with no caller ID will be
routed to RCG 103.
114.5 Relevant AMOs

Language
COSSU ESBER d DUWAV-Durchwahlverhinderung
AVCE e DIDBLK -Voice Feature DID Blocking
DNIT ACD d ACD (Automatische Anrufverteilung)
verwenden
ACD e ACD line selection Yes or No...
TAB= d
DNI DNI Tabelle fuer Internes Routing
GDTR GDTR Tabelle fuer Allgemeine
GDTRSR Zeichenumsetzung
GDTRS Allgemeine Zeichenumsetzung
Dienstregel
TAB= e DNI Table Type:
DNI Directory number information table
GDTR General digit translation table
GDTRSR General digit translation service ruleTable
type
REGEL d DNIS- bzw. SID/ANI-Zeichenkette, die mit
den Ziffern der gerufenen bzw. rufenden
Nummer zu vergleichen ist
(Musterabgleich)
DGTSTR e DNIS or SID/ANI digit string to compare
(pattern match)(for dialed or calling party
digits.
ANZEIGE d Anzeigetext (gerufenes endgeraet )
DISPLAY e DNIS or SID/ANI Pre defined text string to
be presented to Called or Calling party for
the call
DNISRGL d Nummer des Regeltabelleneintrags
DNISRULE e DNIS Rule index
0 - Not assigned
129-255 DNIS Applicable Rule
INTRTADR d Interne Routing Adresse
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Relevant AMOs

Language
INTRTDN e Internal routing directory number
ROUTING= d Routingtyp:
DRTD DNIS-Eintrag, DNIS-abhängiges Routing /
DRTSA Zielnummer
SA DNIS-Eintrag, SIDANI-abhängiges Routing
+ Zielnummer
Ursprungsabhängiges Routing (SID/ANI-
Eintrag)
ROUTING= e Routing Type:
DRTD DNIS entry routing on dnis - Dialed Party
DRTSA Number
SA DNIS entry routing on sidani + With Dialed
Number
Source Number routing (SID/ANI entry)
SARGL d Nummer der SID/ANI Regel
SARULE e SID/ANI Conversion Rule 1-128...
NETSVC=: d Netzdienst
FX Fremdvermittlungszugang
INTLWATS Internationale Langstrecke
INWATS Megacom/mci 800, WATS eingehend
LDS Langstreckendienst
NONE Kein Dienst ausgewählt
PPC900 Multiquest, mci 900
SDS Sds Accu-net
TTA Zugang Querverbindungsleitung,
VPN SDN, Mci Vnet, Private NW-Dienste.
NETSVC=: e Network Service
FX Foreign Exchange Access Service
INTLWATS International Long Distance
INWATS Megacom/mci 800,incoming Wats
LDS Long Distance Service
NONE No Service Selected
PPC900 Multiquest, Mci 900
SDS Sds Accu-net
TTA Tie Trunk Access
VPN Sdn, Mci Vnet, Private Nw Services.
SVCDATA:= d SID/ANI-Voreinstellung
ANI Nur ANI
ANIPREF ANI voreingestellt
NOREQU SID/ANI nicht angefordert
SID Nur SID
SIDPREF SID voreingestellt
SVCDATA:= e SID/ANI Preference
ANI ANI service only
ANIPREF ANI service preferred
NOREQU No service request for sid/ani
SID SID service only
SIDPREF SID service is preferredservice only
TDCSU SIDANI d SID/ANI Service erlaubt
A31003-H3170-S103-6-7620, 02/2019
dnis_en.fm
Relevant AMOs

Language
SIDANII e SID/ANI Signalling requested per device...
TDCSU TRTBL= d Typ der Zeichenumsetzungstabelle:
GDTR Tabelle für allgemeine Zeichenumsetzung
DIDCR Tabelle für Umwandlung bei Durchwahl
TRTBL=: e Digit Conversion Table Type:
GDTR General Digit Translation Table
DIDCR Direct Inward Dialing Conversion Table
TACSU RULEIDX d DID Regelindex
RULEIDX e DNIS Rule index
TRTBL= d Typ der Zeichenumsetzungstabelle:
GDTR Tabelle für allgemeine Zeichenumsetzung
DID Tabelle für Umwandlung bei Durchwahl
TRTBL=: e Digit Conversion Table Type:

GDTR General Digit Translation Table
DID Direct Invard Dialing Conversion Table
BUEND GDTRRGL d Regelnummer für Zeichenumsetzung
GDTRRULE e Rule Number for Digit Conversion
SBCSU DNIDSP d Anzeige DNIS info fuer ankommende
Gespraeche
DNIDSP Display DNIS information for incomming
calls
WABE RNR= Rufnummer z.B. 45999&&45600
KZP= TLN-Teilnehmer
CD e Called Digits i.e. 45600&&45999,
DAR STN- Station
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
Feature Description
115 DSS 1 Terminals

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
OpenScape
4000 S0 Bus
PNTQ
TA S0
S0 Point to Point
SBQ9312
S2 Point to Point
SBQ9312
The features are activated via the Supplementary Services 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.
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
Feature Description
Supported Features
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
COLP to 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
SUBMS SUB using subaddressing, the MSN is signalled at the
N 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
,CDRINT released.
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 (station controlled)
CFU "Immediate call forwarding of all incoming calls"
switches all incoming calls to a station defined by the
CFNR user.
"Call forwarding on no response" switches an incoming
CFB
call to a station defined by the user, if the user does not
answer 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 HiPatn 4000.
ECT "Call transfer" allows a user with a held and an active
connection 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
functional callback; IMPORTANT: Bit 5 of byte 3 must
be set in the option table.
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
User Interface

TRACE MCID this COS must be set together with MCIDM to allow
the automatic registration of all incoming calls.
Additional manual registration is not possible.
MCIDA
automatic registration of nuisance callers; they are
calling users who release the line before the
connection is established.
TP TP set a user in active talk state can park a call for a maximum
of 2 minutes.
In order to be able to use the above Supplementary Services, the DSS1 terminal
must be configured in such a way that it can handle more than one signaling
connection simultaneously (Class of service parameter:
"MULTRA"=Multitransaction).

The features are activated independent from the HiPatn 4000 codes by standard
protocol elements which are transmitted from the station to the HiPatn 4000. This
results on varying user interfaces depending on the station used.
115.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 HiPatn 4000 concept (FWD, FWDBSY and
FNAN) if FWD is programmed via keypad. The forwarding (FWD or BUL) is
then carried out on the A side, which corresponds to the procedure known
from HiPatn 4000 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 HiPatn 4000

concept and the DSS1 concept, then, due to data inconsistencies, the HiPatn
4000 concept dominates.
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
User Interface
115.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!).
• 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 transmitted 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.
115.2.1.2 Call Forward Unconditional (CFU)
Differences to the previous FWD with HiPatn 4000
• Execution at station B. For the calling party, B has not activated FWD and is
seized.
115.2.1.3 Call Forward Busy (CFB)
Differences to the previous FWDBSY with HiPatn 4000
• 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.
115.2.1.4 Call Forward No Reply (CFNR)
Differences to the previous FNAN with HiPatn 4000.
• 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.
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
User Interface
115.2.2 Call on Hold

• A station can put a call on hold, without initiating consultation call, with the
following consequences:
• 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 prefix)
• A consultation call on a DSS1 terminal cannot be picked up, only transferred

using ECT.
• 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).
115.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.
115.2.4 Three-Party Conference

• The three-party conference is not initiated from a normal consultation hold.
The required memory concatenation is therefore not available.
115.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.
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
User Interface
• CFB is performed with UDUB if all stations acknowledged the CW call

negatively (the reason for release is stored in the DH. USER_BUSY
overwrites all other release reasons but is not overwritten).
115.2.6 Callback (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).
• 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).
115.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 behavior 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).
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
User Interface
• 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 station 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 parameter must not be assigned.
115.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.
115.2.9 Malicious Call Identification
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 connection the called party can instigate registration in the
destination PBX by either pressing the appropriate key or by dialling the
corresponding code.
115.2.9.2 Feature Characteristics
In addition to the station numbers of the calling parties, the station numbers of
forwarded parties are also registered.
115.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
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
User Interface
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.
115.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 registration 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 registration 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;
115.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.
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
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.
• 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: no
• 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)

• Configure COS for the DSS1 terminal
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
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",VPRO
T="SBDSS1",FPROT="SBDSS1",DPROT="SBDSS1",PERMACT=Y,INS=Y,ALAR
MNO=0,SOPTIDX=10,TOPTIDX=10,VOPTIDX=10,FOPTIDX=10,DOPTIDX=10,
EXTBUS=Y,CBKBMAX=5;
• ADD-SBCSU:
ADD-SBCSU:STNO=7186,OPT=MSN,MAINO=7185, COS1=22,COS2=5, 
LCOSV1=1, LCOSV2=1,LCOSD1=1,LCOSD2=1, INS=Y;
• 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,LCO
SD2=1,DPLN=0,SPROT="SBDSS1",TPROT="SBDSS1",BPROT="SBDSS1",FPR
OT= "SBDSS1",DPROT="SBDSS1",INS=Y,
SOPTIDX=10,TOPTIDX=10,VOPTIDX=10,
FOPTIDX=10, DOPT=10,CBKBMAX=5;
Option table
The option table consists of a series of hexadecimal numbers which partly have
switch functions 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 conform functioning.
The following table contains the option table assigned to the corresponding
station:
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
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
Station Protocol variant Option table

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 corresponding option in the database:
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>;
IMPORTANT: 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 number 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="..
."];
IMPORTANT: 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 therefore overwritten and any previous individual adjust-
ments are lost.
A31003-H3170-S103-6-7620, 02/2019
dss1term_en.fm
DSS 1 Terminals
Relevant AMOs
115.5 Relevant AMOs

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
115.6 Glossary
NDUB network-determined user busy
UDUB user-determined user busy
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
Feature Description
116 E911 Emergency Call
CPE
OpenScape 4000 node 1

ISDN Public Network
ISDN OpenScape 4000 node 2
PSAP
Calling CorNet-NQ ISDN Central 911

NQ NQ ISDN Office Tandem
User Office
Analog Analog
Analog PSAP
ALI DB
Analog Tie CAMA
Analog Tie
Telident
Figure 113 E911 Network Configurations
An E911 emergency number is dialled out from a user who chooses the
E911number e.g. "9 "" 1 "" 1" to get a connection to the PUBLIC Safty Answering
Point (PSAP). The E911 phone number can also have another numeric string
which is provided by administration.
The emergency call number E911 is connected with high priority via ISDN direct
to the Central Office. The emergency number has also injected into the setup data
about the geographical location of the physical apparatus from where the call was
made. This is acheived by means of a code (LIN) with the Calling party's number
. This transmitted data are identified by a data base (Ali) (PSAP) and further
information given to an operator such as floor or room location.
E911 connection can also be made via a Transit systems (also OpenScape 4000)
with CorNet-NQ, CorNet-N and Analog connections All information cannot be
transmitted by CorNet N or analog connection. The missing information of CPN,
LIN is completed in the next OpenScape 4000 system with the data of its own.
The LIN is read from the Circuit and the CPN comes from the system.
In Network connections from the subscriber to the PSAP including transit

connections ,EMCYRTT=Y must be set on all E911 Routes. Also on circuits used
for E911 a LIN must be administered and in every system a System wide
emergency callback number in AMO ZAND configured, this is required to transmit
the information about CPN and LIN for E911 calls to the relevant correctly
registered PSAP.
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
Central Office (CO) Requirements
116.2 Central Office (CO) Requirements

As a prerequisite for using ISDN PRI trunks for E911 calls, the serving CO must
support this function. Specifically, the CO must be capable of receiving and
processing LIN information that is in a Codeset 5 Generic IE contained in a
SETUP message.
116.3.1 Subscriber
Dialling an E911 telephone number is seen and is carried out by the subscriber in
the same way as a normal telephone number.
116.3.2 Administrator
116.3.2.1 Central System configuration
The administrator must assign memory with AMO DIMSU to be able to manage
the LIN data. This is about 10% to 20% of the maximum available system ports.
A system-wide phone number must be registered in the AMO ZAND, This phone
number is used in the case of a missing subscriber number. This is to enable the
PSAP operator to call back in the case of a disconnection.
116.3.2.2 Port and Subscriber Data
Every Port in the system must have a LIN configured, This is configured with
AMO LIN. Several ports can have the same LIN configured provided they are
located in the same office, factory section, laboratory or room.
NOTE: The LIN used in this document is for example only!
Every subcscriber must be assigned a second phone number with the AMO
SDAT which is obtainable from the external CO. This second phone number is
used together with the E911 emergency call and is transmitted with the call.
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
Service Information
116.3.2.3 Call Handling and Networking
A E911 Emergency number must be configured in AMO WABE .
In LCR the routes over which an E911 emergency call are to be routed are
specially marked as emergency routes. Special outdial rules for the E911
switching have to be configured to take into account both ISDN and Analog
connections
In AMO BUEND it is possible to mark lines or B channels as reserved for the E911
connections.
Connections via Analog or Digital require COT Parameters to Filter or release

Information which are transmited over the analog line or digital Protocoll.
Special care has to be taken when networking that both partners "understand"
each other regarding the transmission of information. The parameters must be
co-ordinated on both sides for outgoing and incoming connections (e.g. analog to
analog)..

This feature is based on The U.S protocol variants. A set of protocols is created
for different U.S. phone network operators and can be copied and loaded into the
DB and the Hard Disk by means of AMO Prode..
With DISPLAY-PRODE:SRC=HD,KIND=PVCDSHRT; the PVCDNR for the

"UNITED STATES OF AMERICA" can be found.
For MOBHFA functionally to work correctly with E911, LIN must be configured
directly in the GUI of the phone device. Further configuration hints are available
under KM209494 (https://gsikm-productive.unify.com/rkm/
viewdoc.jsp?doc=209494).
116.5 AMO Usage
116.5.1 Basic AMOs
116.5.1.1 PRODE
• Create the U.S.A protocol variants in the Database

COPY-PRODE:PVCD,16;
DIS-PRODE:DB,VARTAB;
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
AMO Usage
PVCD,16 selects the "UNITED STATES OF AMERICA" Protocol variant which is

described in the table VARTAB.
116.5.1.2 DIMSU
Add the memory requirements for the number of entries in the LIN table
ADD-DIMSU:TYP=USER,LIN=1000;
116.5.1.3 ZAND
Configure central system data to support the E911 feature requirements

CHA-ZAND:TYPE=ALLDATA2,OOSTONE=YES,ECN=004114953111;
OOSTONE:- For the signed off subscriber no E911 dialling is possible with this
parameter a tone can be configured so that the subscriber can notice that this
Apparatus is not usable.
ECN-This is the System wide Callback Number for Emergency Calls. This
number must be configured in the International Number format with Prefix digits.
This Number works internally with the TON=unknown and NPI=ISDN. Care has
to be taken when sending out this number over analog lines that a limit of the
length is configured. See section " LODR”
116.5.1.4 SDAT
• Configure a public number for the subscriber

CHA-
SDAT:STNO=3560,TYPE=DATA1,PUBUM=3863560,NPI=ISDN,TON=SUBSCR;
PUBNUM Is the phone number which from an external source would lead to this
subscriber.
116.5.1.5 BUEND
• Reserve B channels of a trunk group for E911

ADD-BUEND:TGRP=91,NAME="E911 TO PSAP",NO=2,RSV=YES;
RSV :-This B-Channel group is reserved for E911.
116.5.1.6 REFTA
ADD-REFTA:TYPE=CIRCUIT,PEN=1-2-121-6,PRI=80,BLOCK=N,READYASY=Y;
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
AMO Usage
READASY in the case of no synchronisation a connection setup is still

possible.Otherwise it would be waiting on the complete synchronisation
116.5.1.7 WABE
• Add entries in the Dial Plan

ADD-WABE:CD=911,DAR=CO;
CD is the E911 Emergency number
DAR Is for the connection to the Central office. Set up with the entry CO
116.5.1.8 RICHT
• Create a route to be used for E911

ADD- RICHT:MODE= LRTENEW ,LRTE=91,
ROUTOPT=N,REROUT=N,EMCYRTT=YES;
EMCYRTT is the identification for the E911 emergency number route. The
connection set-up is carried out with a high priority.
116.5.1.9 LIN
• Add Location identification numbers to a station and a PEN

CHA-LIN:TYPE=STNO,STNO=3560,LIN1=9110003560;
CHA-LIN:TYPE=PEN,LTG=1,LTU=2,SLOT=79,CCT=0,LIN1=191112790;
STNO the LIN is assigned to the subscriber.
PEN The LIN is assigned to a position e.g. a circuit.
116.5.1.10 COT
The following COT parameters need to be configured to support the E911 feature.
• SECO Causes the LIN to be sent in the Generic information for LIN code set
5 format
• RLIN informs the system that on this connection LIN data will be received. If
the parameter is no set then the recieved LIN digits are interpreted as CPN.
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
AMO Usage
116.5.2 ISDN Connection to the C.O.

Public Network
ISDN
ISDN
SETUP
3560 CLD=911,NPI=ISDN,TON= PSAP
Calling NATIONAL; Central 911

CPN=3863560,NPI=ISDN, Office Tandem
User Office
TON=SUBSCR;
GI:LIN=9110003560;
PSAP
ALI DB
116.5.2.1 TDCSU
6,COTNO=91,COPNO=91,LCOSV=1,LCOSD=1,CCT="E911
ECS",DESTNO=91,PROTVAR=NI2,SEGMENT=1,ISDNIP=00,ISDNNP=0,NNO=9-1-
1,DEV=S0COD,TGRP=91,BCNEG=Y;
All these parameters must be coordinated withthe Central Office.
116.5.2.2 COT
CHA-COT:COTNO=91,COTTYPE=COTADD,PAR=...IEVT&BLOC&NLCR&PRI&SECO;
Parameter Description:
• NLCR No LCR data will transfer over this line
• SECO activates the sending of the GI:LIN
• PRIO configures the connection with high prioriy.
116.5.2.3 LODR
ADD-LODR:ODR=31,CMD=SENDCOMP;
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
AMO Usage
Parameter description:
• FIELD Causes that only the E911 phone number (911) is sent out.(FIELD =1 )
• SENDCOMP configures that the dialling is complete.
• NATIONAL sets the E911 number in the National Format .
116.5.2.4 LDPLN
ADD-LDPLN:LDP=911,LROUTE=91,LAUTH=1,SPC=22,PINDP=N;
• PINDP No pin is required to reach the C.O for this dial pattern.
• LDP Configures the E911 call number „9“„1“„1“
116.5.3 Analog Connection to the C.O.

Public Network
PSAP
Calling Central 911

Office Tandem
User Office
Analog
PSAP
ALI DB
CAMA
Analog Tie
Telident
Only the LIN is sent.out here
116.5.3.1 LODR
ADD-LODR:ODR=32,CMD=CPNLIN,DGTS=9;
• SENDCOMP configures that the dialling is complete.
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
AMO Usage
• CPNLIN Causes the LIN(9110003560 From AMO LIN)to be sent out
• DGTS Configures how many numbers are sent for the LIN. If the LIN is
shorter than this value then 0’s are added. If the LIN is longer than this setting
then it is shortened to this value
116.5.3.2 LDPLN
ADD-LDPLN:LDP=911,LROUTE=91,LAUTH=1,SPC=22,PINDP=N;;
116.5.4 Digital Networking OpenScape 4000

Public Network

PSAP
Calling CorNet-NQ ISDN

Central 911
NQ NQ ISDN Office Tandem
User Office
PSAP
ALI DB
SETUP
CLD=911,NPI=ISDN,TON=NATIONAL;
CPN=3863560,NPI=ISDN,TON=SUBSCR;
LIN=9110003560;
The element LIN is a private element and when networking with private protocols
such as CorNet-NQ and segment length =1 the private elements are not
transferred. Segmentation should be set to 8.
In the OpenScape 4000 node 2 a LIN must be configured on the port which leads
to OpenScape 4000 node 1. The OpenScape 4000 node 2 won't transmit any LIN
data of the OpenScape 4000 node 1, uses the LIN of this port for the E911
connection. In all systems EMCYRTT=YES must be set.
116.5.4.1 TDCSU node 1
CHANGE-TDCSU:PEN=1-2-121-6,PROTVAR=PSS1V2,SEGMENT=8,DEV=S0CONN;
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
AMO Usage
116.5.4.2 TDCSU node 2
CHANGE-TDCSU:PEN=1-2-121-6,PROTVAR=PSS1V2,SEGMENT=8,DEV=S0CONN;
116.5.4.3 LIN node 2
CHANGE-LIN:TYPE=PEN,LTG=1,LTU=1,SLOT=121,CCT=6,LIN1=....
The Circuit is assigned the LIN1 on the CorNetNQ. circuit
116.5.5 Digital Networking V6.6
V6.6
Public Network
PSAP
Calling CorNet-N ISDN

Central 911
NQ N ISDN Office Tandem
User Office
PSAP
ALI DB
SETUP
CLD=911,NPI=ISDN,TON=NATIONAL;
CPN=3863560,NPI=ISDN,TON=SUBSCR;
The CPN from a V6.6 system has to be NPI=ISDN, otherwise the CPN in the
Setup will be replaced by the systemwide CPN of the OpenScape 4000 node 2.
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
AMO Usage
116.5.6 Analog Networking

Public Network
PSAP
Calling ISDN Central 911

ISDN Office Tandem
User Office
Analog
Analog
Analog PSAP
ALI DB
The E911 number and the LIN is sent
out here..
116.5.6.1 LODR node 1
ADD-LODR:ODR=31,CMD=CPNLIN,DGTS=9;
116.5.6.2 LDPLN node 1
ADD-LDPLN:LDP="911",LROUTE=91,LAUTH=1,SPC=22,PINDP=N;
116.5.6.3 COT node 2
CHANGE-COT:COTNO=221,COTTYPE=COTADD,PAR=RLIN;
• RLIN sets on this connection LIN data will be received. If the parameter is not
set the reccieved LIN is interpreted as CPN.
116.5.6.4 LIN node 2
CHA-LIN:PEN=...,LIN1=....
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
AMO Usage
116.5.6.5 TACSU node 2
CHA-TACSU:PEN=1-2-37-36,LIN=9;
• LIN Defines how many LIN digits are to be expected . When LIN numbers
collected have reached this length the rest of the digits will be ignored.

Language
DIMSU LIN d Anzahl von standortinformationen fuer notruf
DIMSU LIN e Number of location identifiers for emergency
calls
PRODE PVCD d Die US-PVCD Nummer ist 16
PRODE PVCD e The U.S. PVCD number is 16
ZAND AUSBETON d Auser betrieb ton fuer abgemeldet teilnehmer
RRNONOTR d Rueckrufnummer fuer notruf
ZAND OOSTONE e Out of servicre tone for signed off devices
ECN e System wide emergency callback number
LIN LIN1/LIN2 d Standort Identifizierungs nummer 1/2
LIN LIN1/LIN2 e Location Identification number
RICHT EMCYRTT d Notfallsroute
RICHT EMCYRTT e Emergency route
COT SECO d
RLIN d
COT SECO e Send emergency number in genric I.E.
RLIN e Recieve LIN digits
LODR CPNLIN d
LODR CPNLIN e Send LIN or CPN (max 22 digits)
TACSU LIN d Laenge der LIN fuer notruf
TACSU LIN e Length of LIN for E911
REFTA READYAS d READYAS = JA
REFTA READYAS e READYAS =Y
BUEND RESERV d RESERV=JA
BUEND RESERV e RSV =Y trunk group reserved for E911
A31003-H3170-S103-6-7620, 02/2019
e911_en.fm
E911 Emergency Call
AMO Usage
A31003-H3170-S103-6-7620, 02/2019
emergency_call_en.fm
Emergency Call
Feature Description
117 Emergency Call
OpenScape 4000 OpenScape 4000

Node 1 Node 2
Calling
User ISDN Central
IP trunk
Office
The Richtlinie Notrufverbindungen (TR Notruf) of the Bundesnetzagentur

requires to send address information within call signalling of an emergency call.
This requirement is for TDM phones and DSS1 trunks in Germany only but also
works for HFA phones.
The address information is added to the LIN table entries. Call Processing reads
the address information in case of an emergency call, packs it into an ISDN User
Info Element and sends it in the ISDN SETUP message to the Central Office.
Trunks to a Central office which do not support TR Notruf are marked with a Class
of trunk parameter (NOEA) and address information is not sent. The latter
functionality is needed in multinational OpenScape 4000 deployments.
Normal treatment is given to User Info elements received from the Central Office,
e.g the element is passed on to devices and/or applications.

• For MOBHFA functionally to work correctly, LIN must be configured directly in
the GUI of the phone device.
• It is not required to recognize and act upon received address information from
the CO.
A31003-H3170-S103-6-7620, 02/2019
Emergency Call

AMO LIN
CHANGE-LIN:TYPE=STNO,STNO=4711,ZIPCODE=81379,STRNAME=Sesam
Street,STRNUM=123;
It is possible to delete the fields with OPT=ADDR in DELETE branch:
DELETE-LIN:TYPE=STNO,STNO=4711,OPT=ADDR;
AMO ZANDE
Parameters for system-wide address
CHANGE-ZANDE:TYPE=ADDR,ZIPCODE=81379,STRNAME=SESAM
STREET,STRNUM=123;
IMPORTANT: The entry in AMO LIN has a higher priority than the entry in AMO
ZANDE. This means that the entry in AMO ZANDE is only used, if the subscriber/
trunk doesn’t has an entry in AMO LIN.
AMO COT
Parameter PAR=NOEA (No Emergency Address)
117.4 Relevant AMOs

Language
LIN ZIPCODE d Postleitzahl
ZIPCODE e Zip Code
STRNAME d Straßenname
STRNAME e Street name
STRNUM d Hausnummer
STRNUM e Street number
OPT=ADDR d Entfernen der Adressfelder (ZIPCODE,
STRNAME, STRNUM)
OPT=ADDR e Delete address fields (ZIPCODE, STRNAME,
STRNUM)
ZANDE ZIPCODE d Postleitzahl
ZIPCODE e Zip Code
STRNAME d Straßenname
STRNAME e Street name
STRNUM d Hausnummer
A31003-H3170-S103-6-7620, 02/2019
Emergency Call
Relevant AMOs

Language
STRNUM e Street number
COT NOEA d Keine Notfalladresse
NOEA d No emergency address
A31003-H3170-S103-6-7620, 02/2019
Emergency Call
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
emerove_en.fm
Feature Description
118 Emergency Override/Disconnect

Network-wide "emergency override/disconnect" is used primarily in special-
purpose networks, e.g. power supply or police networks, for authorized users in
emergency situations. "Destination-dependent disconnect" takes place on
connection setup to a specific destination by means of code dialing.
The "emergency override/disconnect" feature enables the caller to intrude on or

disconnect busy digital (S0/S2 B-channels) or analog lines (with/without DIUC,
not TMOM circuits) within a private network configuration. In addition,
"emergency override/disconnect" is also possible for analog or digital tie-trunks
or CO (exchange) trunks within a private network (for breakout to other networks).
Emergency override can be activated by authorized users by means of suffix

dialing as soon as the busy or ATB state occurs.
Disconnect can be activated by authorized users by means of prefix dialing as a

precautionary measure prior to entering the destination number or alternatively
by means of suffix dialing as soon as the busy or ATB state arises.
Users without special classmarks can initiate destination-dependent disconnect

to specific internal or external emergency destinations by dialing a special code,
e.g. an emergency call number. This code implicitly contains both the disconnect
request and the destination address. The connection to this destination is then set
up with a precautionary disconnect request. If the code for destination-dependent
disconnect refers to an internal destination, translation to a station number with
PEN takes place. The code is assigned to the station number by means of an
AMO.
The "emergency override/disconnect" function can be activated by DIGITEs, ACs

and ANATEs.

• Limitation: suffix paging cannot be activated from ANATE.
• "Emergency override/disconnect" can be performed on busy DIGITE and

ANATE, as long as there is no emergency override/disconnection protection
activated.
• The DAR must be added on a NAME key to allow the feature to work from a
Digite.
A31003-H3170-S103-6-7620, 02/2019
emerove_en.fm

Configuring the "emergency override/disconnect" features
The procedure for configuring the features is described in the following.
Assigning digit analysis results (DAR) in the digit analysis

• Assigning the DAR "emergency override"
AD-WABE:CD=<number>,DAR=EOVR;
• Assigning the DAR "disconnect"
AD-WABE:CD=<number>,DAR=RELEASE;
• Assigning the DAR "destination-dependent disconnect" to an internal station
AD-WABE:CD=<number>,DAR=STNREL,DESTNO=0;
• Assigning the DAR "destination-dependent disconnect" to an external
subscriber in the system with destination system number <number>
AD-WABE:CD=<number>,DAR=STNREL,DESTNO=<number>
Translating "destination-dependent disconnect" code to an internal

number
With this conversion function the "destination-dependent disconnect" code, e.g.
the emergency call number, is assigned a real station. Translation must be
performed in the system of the station to which connections are set up with
"destination-dependent disconnect". The station number must have a PEN
configured.
AD-RUFUM:TYPE=DID=<n>,DID1,DID2=<m>;
DID1 code for "destination-dependent disconnect"
DID2 call number of an internal station with PEN (applies to internal/external
in the system to which the station belongs).
Enabling "emergency override" or "disconnect" feature

The two features can be released independently of each other. For the
"destination-dependent disconnect" feature the "disconnect" feature must be
released with AMO FEASU.
CHA-FEASU:TYPE=A,CM=EMOVR; 
CHA-FEASU:TYPE=A,CM=EMRLS;
Assigning COS "emergency override/disconnect"

SDAT AMO is used to set the COS for "emergency override/disconnect" for
ANATE/DIGITE and AMO ACSU to set this COS for the AC.
CHA-SDAT:STNO=number,TYPE=ATTRIB,AATTR=EOVR;
or
CHA-ACSU:ATNDNO=number,EOVR=Y;
A31003-H3170-S103-6-7620, 02/2019
emerove_en.fm
Relevant AMOs
Assigning the "emergency override/disconnect protection" class of service

The emergency override/disconnect protection authorization can be assigned to
DIGITEs with the SBCSU AMO, to ATNDs with the ACSU AMO and to ANATEs
with the SCSU AMO.
CHA-COSSU:TYPE=COS,COS=<number>,AVCE=REOVR;
Enabling "emergency override/disconnect" on inter-PBX trunks

"Emergency override/disconnect" is possible on analog and digital inter-PBX
trunks. The parameter class can be assigned with the AMOs TACSU and
TDCSU. The COT parameter must be assigned to the connection in all systems
involved.
CHA-COT:COTNO=<number>,COTTYPE=COTADD,PAR=PROV;
Enabling "emergency override/disconnect" breakout

"Emergency override/disconnect" is possible for analog or digital tie-trunks or CO
(exchange) trunks within a private network, for breakout to other networks (e.g.
PSTN). The network breakout point is the last possible emergency override/
disconnect point in the connection path, since the emergency override/
disconnect criterion is not transmitted beyond this point. 
The CO trunks or tie-trunks in question must be enabled by setting the following
COT parameter:
CHA-COT:COTNO=<number>,COTTYPE=COTADD,PAR=EODL;
Administering external tone source for disconnect tone

The disconnect tone is signalled to the destination station after disconnection has
taken place. The standard tone in Germany is NU tone. 
An external acoustic source connected via a SLMA can also be used for the
disconnect tone.
E.g.:
ADD-SSC:PEN=<ltg-ltu-ebt-port>,TYPE=EXTANN,CPCALL=DISCTONE;
118.4 Relevant AMOs

Language
ACSU VFNU d RUFNUMMER DES VF
ATNDNO e ATTENDANT CALLING NUMBER
NATR d Notaufschalten/Trennen
JA=aktivieren
EOVR e EMERGENCY OVERRIDE/FORCED HOLD
YES=activate
A31003-H3170-S103-6-7620, 02/2019
emerove_en.fm
Relevant AMOs

Language
COS=ZU BEARBEITENDE COS
COS=CLASS OF SERVICE
ESBER d Einfuegen Sprachberechtigungen
NATRS=SCHUTZ VOR NOTAUFSCHALTEN/
TRENNEN
AVCE e Add voice authorization
REOVR = REJECTION OF EMERGENCY
OVERRIDE
COT COTNU d Class of Trunk Nummer
NATR=Notaufschalten/Trennen
NATL=NOTAUFSCHALTEN BZW. TRENNEN
NUR LOKAL
PROV=EMERGENCY OVERRIDE
EODL=EMERGENCY OVERRIDE/
DISCONNECT ONLY LOCAL
FREI=FREIGEBEN VON
LEISTUNGSMERKMALEN
TYPE e desired class mark facility options
A=ACTIVATED FEATURES
NOTAUF=NETZWEITES NOTAUFSCHALTEN
NOTTR=NETZWEITES TRENNEN IM
NOTFALL
CM e feature, class mark, facility
EMOVR=NETWORK-WIDE EMERGENCY
OVERRIDE
EMRLS=NETWOK-WIDE EMERGENCY
CONNECTION RELEASE
KZP d Kennzahlpunkt
NOTAUF=NOTAUFSCHALTEN
TRENNEN=TRENNEN EINES TEILNEHMERS
EOVR=EMERGENCY OVERRIDE
RELEASE=EMERGENCY RELEASE OF A
STATION
DUWA=Durchwahlrufnummern
TYPE e DID=DIRECT IN DIAL
A31003-H3170-S103-6-7620, 02/2019
emerove_en.fm
Relevant AMOs

Language
DUWA1 d externe Durchwahlrufnummer
DID1 e DIRECT DIGIT INDIAL NUMBER
DUWA2 d interne Rufnummer (fuer Durchwahl)
DID2 e INTERNAL DESTINATION NUMBER (FOR
INDIAL)
A31003-H3170-S103-6-7620, 02/2019
emerove_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
entrance_en.fm
119 Entrance Telephone with Door Opener

• Add the configuration of the TMOM module
• Assign codes for the entrance telephone and door opener in the DPLN
AD-WABE:CD=key-num,DAR=DOORCL&TORAUF;
• Assign a class of trunk
AD-COT:PAR=NTON;
• Assign a class of parameter
AD-COP:PAR=LSUP;
• Add trunk group
AD-BUEND:NO=number;
AD-TSCSU:COTNO=number,DEV=DOOR,COPNO=number;
• Assign a route to the entrance telephone for DOORCL and DOOROPEN
AD-RICHT:TYPE=CD,CD=key-
num,CPS=5&8&9&10&11&12,SVC=VCE,TGRP1=number;
A31003-H3170-S103-6-7620, 02/2019
entrance_en.fm
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Configuration
120 EURO ISDN Terminals
120.1 Configuration
A functional terminal can be configured on the OpenScape 4000 via the
interfaces shown in the diagram:
S0-DSS1 S0-DSS1
Bus SLMS STMD
Point-Point
STMD2 STMD2
S0-DSS1 STHC2
Bus NTBA
SLMQ
S0-DSS1 UP0/E S2-DSS1
Bus PNT E DIUS2
Point-Point
SLMO DIUN2
S0-DSS1 UP0/E
Bus TA S0 STHC2 DIUN4
The terminal is configured with the following AMOs:
• AMO SBCSU: Configuration of terminal data for phone numbers and multiple
subscriber numbers (MSN).
• AMO PRODE: Configuration of protocol tables that are assigned to a

terminal.
• AMO ZAND: Modification of option tables which provide an important means

of configuring a terminal.
Note that DSS1 terminals in the bus configuration always have to be configured
for all services. The service protocols should generally be assigned to option
table 10.
120.1.1 Configuration Examples

• Bus configuration of RNR 3270 with MSN 3271 on S0 bus (SLMS 1-1-25-2)
ADD-SBCSU:STNO=3270,OPT=FBUS,CONN=DIR,PEN=1-1-25-
2,DVCFIG=SET600&DEE&FAX,COS1=24,COS2=5,LCOSS1=1,LCOSS2=1,LCOS
D1=1,LCOSD2=1,SPROT="SBDSS1",FPROT="SBDSS1",DPROT="SBDSS1",SO
PTIDX=10,FOPTIDX=10,DOPTIDX=10,EXTBUS=YES;
ADD-SBCSU:STNO=3271,OPT=MSN,MAINO=3270,
COS1=24,COS2=5,LCOSS1=1,LCOSS2=1,LCOSD1=1,LCOSD2=1;
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Configuration
• Point-to-point configuration on SLMS/STMD with RNR 3177

In contrast to the bus configuration, all possible services are configured the
same.
ADD-SBCSU:STNO=3177,OPT=FPP,CONN=DIR,PEN=1-2-31-
0,DVCFIG=S0PP,COS1=24,COS2=5,LCOSS1=1,LCOSS2=1,LCOSD1=1,LCOSD
2=1,COSX=0,PROT="SBDSS1",OPTIDX=10;
• Configuration of STNO via PNT E on SLMO
ADD-
SBCSU:STNO=3100,OPT=OPTI,CONN=DIR,PEN=<number>,DVCFIG=OPTISET
,COS1=<number>,COS2=<number>,LCOSS1=<number>,LCOSS2=<number>,
LCOSD1=<number>,LCOSD2=<number>;
ADD-
SBCSU:STNO=3232,OPT=OPTIEXP,MAINO=3100,DVCFIG=SET600&DEE&FAX,
COS1=<number>,COS2=<number>,LCOSS1=<number>,LCOSS2=<number>,L
COSD1=<number>,LCOSD2=<number>,SPROT="SBDSS1",FPROT="SBDSS
1",DPROT="SBDSS1",SOPTIDX=2,FOPTIDX=4,DOPTIDX=4;
120.1.2 Option Table

The option table comprises a sequence of hexadecimal numbers, which are used
in part as a switch function and partly for configuring parameters for features such
as CCBS and UUS.
Byte/ 7 6 5 4 3 2 1 0 Comment
Bit
1 1 0 0 1 0 1 1 1 Must not be modified
2 0 1 1 0 0 0 0 1 Must not be modified
Bit 2: Use of UUS3 without explicit
activation (CMI extension line only)
Bit 5: Allow suffix dialing
Bit 6: Allow override stimulus
3 0 1 1 0 0 0 0 0 Bit 4 set: Only AOC-E with activated
call data recording
Bit 5 set: CCBS is possible
Bit 6 set: TP exclusively with basic
rate access
Bit 7 set: Network-wide signaling that
the subscriber is using a functional
terminal
4 0 0 0 0 0 0 0 0 Reserve
...
7 $0A-$83 Maximum length of a UUS
information element
42 $10-$FF UUS burst parameter (default = $10)
43 $08-$FF UUS incrementation parameter
(default = $08)
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Configuration
All other fields in the option table must not be changed as otherwise functionality
can no longer be guaranteed to be protocol compliant.
The next table contains the option table assigned accordingly to the respective
terminals:
Terminal Protocol Option

variants table
EURO-ISDN terminal from KRONE SBDSS1 10
Integrated terminal adapter SBDSS1 10
ISDN S0PP-PNT (PC cards with layer 2 structure - UDAT SBDSS1 10
REQ)
CMI SBDSS1 10
NI - BRI terminals SBNIBRI 7
DSS1 terminal (EURO-ISDN terminals) SBDSS1 10
DSS1 terminal (functional voice terminals) SBDSS1 10
• Assigning an option index to the terminal

A specific option index (1-10) is assigned to the functional terminals on the
bus for each service represented, using AMO SBCSU (see table); the index
refers to the corresponding option in the database
AD-SBCSU:STNO=4711,OPTIDX=<FBUS/MBUS,OPTI/OPTIEXP>,...
,SOPTIDX=<opt-speech>,TOPTIDX=<opt-ttx>,VOPTIDX=<opt-
vtx>,FOPTIDX=<opt-fax>,DOPTIDX=<opt-dte>;
or in the case of point-to-point connections:
AD-SBCSU:STNO=4711,OPT=<FPP/MSN>,OPTIDX=<opt>;
IMPORTANT: If no xOPTIDX (x=S/T/V/F/D) or OPTIDX value is specified

when a functional terminal is configured, the AMO enters xOPTIDX=1 or
OPTIDX=1 automatically.
• Subsequent modification of an option

If the option table is definitely loaded (CHA-ZAND:TYPE=OPTTBL) and there
are still problems with EURO-ISDN features, it may be necessary to modify a
particular option in the database.
Each option consists of 100 bytes and can be modified in the database on a
byte basis using AMO ZAND. For this purpose the option must be addressed
by way of the table index 1-10 and the number of the byte to be modified (1-
100). The new value assigned to the byte must be in hexadecimal form. Each
option also has a name; this too can be modified:
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Configuration
CHA-
ZAND:TYPE=OPTTBL,IDX=number,BYTE=number,VALUEOPT=FF[,NAME="..
."];
IMPORTANT: Since the meanings of the individual bytes are known only to
CP, modification of an option must be carried out by specialists (apart fom the
change of name). It is therefore advisable to consult with CP Munich
beforehand. 
If a new HD option table is incorporated (e.g. change of APS), it must be
loaded into the database again by means of AMO ZAND. Since the AMO
requires this to be done in its entirety (the selective reloading of specific
options is not possible), all options are overwritten in the database and any
previous modifications are lost.
IMPORTANT: If the SBDSS1 protocol is required for FPP with layer 2

structure, option table 10 must be used with the following change 
( CH-ZAND:TYPE=OPTTBL,IDX=10,BYTE=2,VALUEOPT=E1;). It must be
ensured however that only the S0PP connections (PNT) then use this option
table.
120.1.3 Station class of service

The possible classes of service are shown in the next table:

CCBS CCBS set The calling subscriber can activate a functional callback
if the line is busy; n.b.: Bit 5 of byte 3 must be set in the
option table
COLR COLR set The called subscriber line can temporarily suppress the
display of its own phone number to the calling party
(controlled by terminal)
CW CW set The called subscriber has call waiting class of service
FGAUT MCID This class of service must be set together with the
MCIDM class of service so that all incoming calls can be
registered automatically. Additional manual registration
is not possible.
GEP, AOC Call charge information is output on the terminal
GESP,
GEBIN
T
MCIDA MCID Automatic registration of ringing malfunctions; the
calling subscribers disconnect before the call is
connected
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Additional Services

MCIDM MCID Manually activated registration of call data during the
call or following disconnection
MSN MSN set Multiple Subscriber Number;only for functional
terminals
MULTR - set Only for functional terminals
A
OVCAT COLR The phone number of the called subscriber is also
output on the terminal for a secret number
SPECA CLIP/ Only activate if the phone number configured on the
R COLP terminal is not to be checked
SUBCA SUB Called subscriber is informed of the phone number of
L the calling subscriber by means of subaddressing
SUBDB SUB The called subscriber is notified of own phone number
by means of subaddressing
SUBMS SUB The called subscriber is notified of MSN number by
N means of subaddressing
TP TP set The subscriber can park a call for the maximum duration
of two minutes in an active call state
UUS1I UUS set Class of service for using the UUS1 service is implicit
M
UUS3 UUS Class of service for using the UUS3 service
120.2 Additional Services
120.2.1 Multiple Subscriber Numbers (MSN) on the S0

Bus
With the Multiple Subscriber Numbers (MSN) feature a terminal interface can be
assigned several (not necessarily consecutive) subscriber numbers. It is thus
possible to select a specific terminal from several belonging to the same service
and linked to the same S0 bus.
The bus terminology introduced with AMO SBCSU is used in the following:
• Main Subscriber Number

The main subscriber number in a bus configuration is the number assigned
to the physical LINE of the bus. The bus is configured with this subscriber
number.
• Secondary Subscriber Number

The secondary subscriber numbers in a bus configuration are additional
numbers, under which CorNet terminals can be configured.
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Additional Services
The bus constellation, functional bus (FBUS) as well as an UP0/E connection

with functional terminal can be extended such that an existing functional
terminal on the main subscriber number or the secondary subscriber number
can be reached via several phone numbers. In contrast to the number
conversion with AMO TGER, the phone number dialed by the A station is
displayed to the B station. 
Furthermore, additional functional terminals for a service already configured
on this port can be connected and reached under a separate phone number.
The previously used bus terminology has to be extended in this case by the
term secondary MSN number and MSN phone number.
• Secondary MSN Numbers

The effective range of an existing secondary subscriber number is extended
to the existing functional non-voice terminal for the main subscriber number
or secondary subscriber number. In other words, the NV-FUNCT terminals for
the main/secondary subscriber number can now also be reached via the
secondary MSN number if it is configured accordingly. Other FUNCT
terminals for the same service that are connected to the bus can be reached
selectively with the secondary MSN number. Secondary MSN numbers can
occur at the UP0/E port. Secondary MSN numbers can occur at the UP0/E
port. 
Since the first "MSN device" on a secondary MSN number occupies a TSI,
the number of secondary MSN numbers on the bus is restricted.
IMPORTANT: In UP0/E- configurations, functional terminals can also be

assigned to secondary subscriber numbers. The main subscriber number can
then be assigned MSN functionality, and thus becomes a "secondary MSN
number".
• MSN Numbers
These are further numbers for functional terminals. All the services for which
a functional terminal is configured under the main subscriber number can be
accessed under an MSN number. Accordingly, MSN numbers are used in
MBUS, FBUS, and UP0/E- configurations.
There are no restrictions regarding the number of MSN numbers on the bus.
120.2.1.1 Configuration
• MSN on UP0/E port

Precondition: UP0/E port with secondary subscriber number and at least one
functional terminal linked to the main subscriber number, e.g.
Main subscr. no. 4711: CORNET-TS (Voice FUNCT- FUNCT-DEE

terminal), FAX,
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Additional Services
Secondary sub. no 4712: CORNET-TS (Voice

terminal),
Assigning secondary MSN number 4712:
AD-SBCSU:STNO=4712,OPTIDX=MSN,MAINO=4711;
Result:
Main subscr. no. 4711: CORNET-TS (Voice FUNKT-FAX, FUNKT-DEE

terminal),
MSN Secondary sub. no 4712: CORNET-TS (Voice MSN-FAX, MSN-DEE
terminal),
The secondary MSN number 4712 occupies 1 TSI for the CorNet-TS terminal
and one for all "MSN devices", regardless of how many services can actually
be reached. Other secondary MSN numbers can no longer be configured.
However, additional MSN subscriber numbers can be configured.
IMPORTANT: Secondary MSN numbers are always READY and cannot be

configured by dependability (DEP) or by AMO DSSU. 
The scope of MSN services is always the same as the services provided by
the functional terminals linked to the main subcriber number (in this case fax
and videotex) and cannot be limited to specific services (e.g. fax only). 
The scope of MSN services is expanded automatically (with each secondary
MSN number on the bus) when new functional terminals are added to the
main subscriber number (AD-SBCSU: OPTIDX=SVC,..;) ! 
The scope of MSN services is reduced automatically (with each secondary
MSN number on the bus) when functional terminals are deleted at the main
subscriber number (DEL-SBCSU:SVC=<VTX/DTE/FAX/TTX, ...;) !
• Assigning an MSN Number (MBUS)

Precondition: Free subscriber number (defined as DAR=STN in AMO WABE)
and MBUS with at least one functional terminal linked to the main subscriber
number, e.g.
Main subscr. no. 4711 CORNET-TS (Voice FUNCT- FUNCT-

terminal), FAX, DEE
MSN Secondary sub. no. CORNET-TS (Voice MSN-FAX, MSN-DEE
4712 terminal),
Secondary sub. no. MSN-FAX MSN-DEE
4713
Assigning MSN number 4999:
Result:
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Additional Services
Main subscr. no. 4711 CORNET-TS (Voice FUNKT-FAX, FUNKT-DEE

terminal),
MSN Secondary sub. no. CORNET-TS (Voice MSN-FAX, MSN-DEE
4712 terminal),
MSN Secondary sub. no. MSN-FAX MSN-DEE
4713
IMPORTANT: MSN numbers are alway READY and cannot be configured by

dependability (DEP) or by AMO DSSU. 
The scope of MSN services is always the same as the services provided by
the terminals linked to the main subscriber number (in this case fax and
videotex) and cannot be limited to specific services (e.g. fax only). 
The scope of services is expanded automatically (with each MSN number on
the bus) when functional terminals are deleted at the main subscriber number
(AD-SBCSU:OPTIDX=SVC, ...;) ! 
The scope of MSN services is reduced automatically (with each MSN number
on the bus) when functional terminals are deleted at the main subscriber
number (DEL-SBCSU:SVC=<VTX/DTE/FAX/TTX>, ...;) !
• Assigning an MSN Number (FBUS)

Precondition: Free subscriber number (defined as DAR=STN in AMO WABE)
and FBUS with at least one functional terminal linked to the main subscriber
number, e.g.
Main subscr. FUNCT- FUNCT- FUNCT-DEE

no. 5711: Voice, FAX,
Assigning MSN number 5999:
Result:
Main subscr. no. FUNCT-Voice, FUNCT-FAX, FUNCT-DEE

5711:
MSN MSN no. 5999: MSN-Voice, MSN-FAX, MSN-DEE
IMPORTANT: The informamtion contained in the section "Assigning an MSN

number (MBUS)" applies accordingly.
• Setting MSN Authorization

The MSN authorization must be set in the associated COS for the main
subscriber number on the bus, depending on the services involved.
CHA-COSSU:TYPE=COS,COS=<number>,AVCE=MSN,AFAX=MSN,AVTX=MSN,
ADTE=MSN;
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Additional Services
or in the MBUS examples

CHA-COSSU:TYPE=COS,COS=<number>,AFAX=MSN,AVTX=MSN;
This class of service has two major effects:
• A CP bit which has been set according to the service (this normally
preven two funcional bus terminals of the same service being in the
call state simultaneously) is disregarded, so that the main subscriber
number and the MSN number can be accessed parallel to each other
(even without the MSN number on the bus it is possible to ensure, by
means of a set MSN class of service, that of two functional voice
devices, both set to the main subscriber number, the second can be
accessed with the main subscriber number if the first is busy).
• On an incoming call, the (MSN) number is sent as "Called Party No"

to the bus, where each functional terminal itself checks, on the basis
of the programmed number(s), whether it has to answer (in the 1TR6
protocol this is the equivalent of the TSI).
IMPORTANT: It is advisable to set the MSN authorization for all services and
not just for those which are actually available - this saves repeated adaptation
if the main subscriber number is subsequently expanded with the addition of
other (functional) services and has no negative effects (apart from those
referred to above) if there is in fact no "MSN device" for a particular service.
• Programming terminal to MSN number

Functional terminals already connected to the bus can also be programmed
to the MSN number. 
In addition, further terminals belonging to the same service can be connected
to the bus and programmed to the new MSN number.
IMPORTANT: In the case of terminals connected to the bus with the 1TR6
protocol only a single-digit terminal selection identifier (TSI) can be
programmed, with the result that MSN numbers can only be differentiated on
the basis of the final digit. It is therefore important for all MSN numbers used
on the bus to have different final digits.
120.2.2 Deleting of an Configuration

• Secondary MSN number (FBUS, UP0/E port)
Main subscr. no. CORNET-TS (Voice FUNCT-FAX, FUNCT-DEE

4711 terminal),
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Additional Services
MSN Secondary no. CORNET-TS (Voice MSN-FAX, MSN-DEE

4712 terminal),
MSN MSN no. 4999: MSN-FAX MSN-DEE
Delection of secondary MSN number 4712:
DEL-SBCSU:STNO=4712,SVC=MSN;
Result:
Main subscr. no. CORNET-TS (Voice FUNCT-FAX, FUNCT-DEE

4711 terminal),
Secondary no. CORNET-TS (Voice
4712 terminal),
MSN MSN no. 4999: MSN-FAX MSN-DEE
IMPORTANT: Secondary MSN numbers are always "READY" and cannot be

activated either by dependability (DEP) or the AMO DSSU so that the usual
disconnect before deletion is obsolete. 
A secondary MSN number cannot be deleted if it is still contained in a hunt
group for a service from the MSN services range (i.e. FAX or DEE in the
example). 
All secondary MSN numbers on the bus are deleted automatically by the
AMO if you delete the last functional terminal (DEL-
SBCSU:SERVICE=<DEE/FAX>, ...;) ! 
If you cannot delete a secondary MSN number for whatever reason, you also
cannot delete the last functional terminal!
• Deleting an MSN subscriber number (FBUS, UP0/E port)
Main subscr. no. CORNET-TS (Voice FUNKT-FAX, FUNKT-DEE

4711: terminal),
Secondary subscr. CORNET-TS (Voice
no. 4712: terminal),
MSN MSN no. 4999: MSN-FAX
Deletion of MSN number 4999:
DEL-SBCSU:STNO=4999,SVC=MSN;
Result:
Main subscr. no. CORNET-TS (Voice FUNKT-FAX, FUNKT-DEE

4711: terminal),
Secondary susbcr. CORNET-TS (Voice
no. 4712: terminal),
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Subaddressing (SUB)
120.2.2.1 Displaying an MSN Number of an S0 Bus
MSN numbers/secondary MSN numbers can only be interrogated in one of the

following two ways:
CHA-SBCSU:TYPE=BUS, ...;
also displays "MSN" devices"
CHA-SBCSU:TYPE=DEV,DEV=MSN, ...;
displays all MSN numbers/secondary MSN numbers assigned by AMO SBCSU
120.3 Subaddressing (SUB)

Subaddressing enables users to extend the addressing capacity beyond the
ISDN number. The subaddress can be used, for example, for:
• the additional selection of terminals
• the activation of special processes in the called terminal.
The subaddress (if outdialed by the A subscriber) is transmitted transparently to

the called party. The maximum length of a subaddress is 23 octets. This length
can be changed to any value between 0 and 23 (default=23) on the terminal side
by means of AMO ZAND (see below). At the NW interface this value is
permanently assigned to a protocol variant.
Classes of service SUBCAL, SUBDB and SUBMSN

There are 3 alternative authorizations per service for EURO-ISDN terminals. By
means of these authorizations, the provision of the ISDN subaddress is controlled
for those cases in which the B subscriber definitely expects an ISDN subaddress
but this address is not supplied by the A subscriber.
• SUBCAL: B is provided with the A number as the subaddress
• SUBMSN: B is provided with the MSN (Multiple Subscriber Number) as the

subaddress (either the number dialed by A or a call forwarding number)
• SUBDB : B is provided with the default B number (main subscriber number)

as the subaddress
One of these authorizations must be set in the COS assigned to the EURO-ISDN
terminal on a service-specific basis:
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Subaddressing (SUB)
CHA-
COSSU:TYPE=COS,COS=<number>,AVCE=SUBCAL,AFAX=SUBCAL,ATTX=SUBCAL,
AVTX=SUBCAL,ADTE=SUBCAL;
IMPORTANT: Since the SUB authorizations are mutually exclusive, only one of
these values may be set per COS and service. If several are specified, the first
authorization set in the order indicated above is authomatically given prece-
dence.
120.3.1 Malicious Call Identification

see Chapter 115, “Malicious Call Identification”
120.3.2 User-to-User Signalling (UUS)

see Chapter 150, “User-to-User Service”
120.3.3 Terminal Portability

The "Terminal Portability" feature allows a call to be parked temporarily. The call
is parked in the node by specifying a two-position identification number. As long
as the call is not unparked again, the subscriber can continue to replace or
decouple terminals or resume the call from another terminal on the bus by
specifying the identification number.
A call can only be parked for a duration of two minutes.
• Configuration
The TP parameter for the voice service has to be activated in the COS and
bit 6 in byte 3 of the assigned option table must be set.
• Restriction
If the subscriber is a member of a call pickup group, the call can no longer be
parked in the pickup group. However, a parked call can be transferred from
the pickup group.
120.3.4 Call Waiting

If the called subscriber is busy or if all B channels are busy, the subscriber can be
informed of the new call if the CW class of service is defined.
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Subaddressing (SUB)
120.3.5 Call Completion Busy Subscriber

A calling subscriber can activate a functional callback if the line is busy. The
CCBS class of service must be set in the COS for this purpose. Bit 5 of byte 3
must be set additionally in the option table.
120.3.6 COLR
If the COS class of service COLR of the called subscriber is defined, the call
number suppression set in the terminal is evaluated and forwarded to the calling
station.
120.3.7 Advice of Charge

If call charge recording is activated, the option table can be used to define
whether AOC-D and AOC-E or only AOC-E is activated.
If bit 4 of byte 3 is active in the option table, AOC-D is blocked.
A31003-H3170-S103-6-7620, 02/2019
euterm_en.fm
EURO ISDN Terminals
Subaddressing (SUB)
A31003-H3170-S103-6-7620, 02/2019
key_executive_en.fm
Executive Features
Features
121 Executive Features

The key function is enhanced by several new trading executive functions. This
means that the network-wide teams can now be set up with the same functions
as for local teams. Features that are familiar from the CHESE can now be used
over the entire network.
121.1 Features
121.1.1 DSS lines

• The number of DSS destinations that can be programmed is increased to 65
in the ZAND.
• The new function is available network-wide and should be set up with a

separate name.
• Calls using DSS keys can always be signaled, even when the called station
is busy.
121.1.2 Mailboxes per line

• Up to 29 mailbox lines can be configured for each station.
• Each mailbox line has a trunk key assigned to it in the ZIELN.
121.1.3 Entry without tone

• The BUZZ key can be pressed to invite a person listening to the call to join in.
• A special authorization (SDAT) prevents the conference tone from being

played.
121.1.4 Ring transfer

• Call ringing can now be transferred while still displaying the visual signal on
the telephone (function as in CHESE).
• Up to 16 ring transfer keys can be configured on each telephone.
A31003-H3170-S103-6-7620, 02/2019
key_executive_en.fm
Executive Features
Example: Configuration over two Nodes
121.1.5 Redial destinations for trunks used

• The redial key can now store a destination for each trunk key. The station is
given a special authorization in AMO SDAT.
121.2 Example: Configuration over two Nodes

• Stations 7210 and 7211 are configured in node 30-200
• Station 7110 is configured in node 30-100.
• These three stations form a team.
A31003-H3170-S103-6-7620, 02/2019
key_executive_en.fm
Executive Features
7125 DSS to stn 1 (sys 1) 7210 RNGXFER to stn. 1 (sys 1)

7210
Stn3: 7110 7127 DSS to stn 2 (sys 1) 7210 RNGXFER to stn. 2 (sys 1)
7211
7110 MBOX own line
7210 MBOX of stn 1
7211 MBOX of stn 2
7126 Partner line (Phant.)
7127 Partner line (Phant.)
7110 own line (Primary)

SYS 2
Stn1: 7210 Stn2: 7211
SYS 1
7211 RNGXFER to stn 2 (sys 1) 7210 RNGXFER to stn 1 (sys 1)
7110 RU to stn 3 (sys 2) 7110 RNGXFER to stn 3 (sys 2)
7220 DSS to stn 2 7221 DSS to stn 1

7211 7210
7223 DSS to stn 3 (sys 2) 7223 DSS to stn 3 (sys 2)

7110 7110
7210 MBOX own line 7211 MBOX own line
7211 MBOX of stn 2 7210 MBOX of stn 1
7110 MBOX of stn 3 (sys 2) 7110 MBOX of stn 3 (sys 2)
7211 Partner line (Phant.) 7211 won line (Primary)
7210 own line (Primary) 7210 Partner line (Phant.)
7224 Partner line (Phant.) 7224 Partner line (Phant.)
A31003-H3170-S103-6-7620, 02/2019
key_executive_en.fm
Executive Features
• Node 200
Configure KYPROG
CHANGE-
TAPRO:STD=127,DIGTYP=OPTIT19,KY01=MENU,KY02=SNR,KY03=CALLOG,K
Y04=SPKR,KY05=RNGXFERL,KY06=MBLINE,KY07=LINE,KY08=BUZZ,KY09=R
NGXFERL,KY10=MBLINE,KY11=LINE,KY12=LINE,KY13=RNGXFERL,KY14=MB
LINE,KY15=LINE,KY16=LINE,KY17=RCUTOFF,KY18=MONSNLTL,KY19=RLS,
INFO="KEY - EXECUTIVE TI";
Station
6,DVCFIG=OPTIP500,COS1=13,COS2=1,LCOSV1=5,LCOSV2=1,LCOSD1=5,L
COSD2=1,DPLN=0,ITR=0,REP=0,STD=127,TEXTSEL=GERMAN,CALLOG=ALL;
7,DVCFIG=OPTIP500,COS1=13,COS2=1,LCOSV1=5,LCOSV2=1,LCOSD1=5,L
COSD2=1,DPLN=0,ITR=0,REP=0,STD=127,TEXTSEL=GERMAN,CALLOG=ALL;
Phantom station
ADD-
SBCSU:STNO=7220&&7224,OPT=OPTI,CONN=DIR,DVCFIG=OPTIP500,
COS1=13,COS2=1,LCOSV1=5,LCOSV2=1,LCOSD1=5,LCOSD2=1,STD=1
27,
INS=SIGNOFF;
Configure KEY
• primary
ADD-
KCSU:STNO=7210,TYPE=PRIM,PRIMKEY=5,RIOP=YES,ORLNPF=PRIME
,TMLNPF=ALER,BUSYRING=ALERT,APRIVAT=NO,AICS=NO;
ADD-
ADD-
ADD-
ADD-
ADD-
ADD-
• secondary
A31003-H3170-S103-6-7620, 02/2019
key_executive_en.fm
Executive Features
EINR-
KCSU:TLNNU=7210,TYP=SEK,TASNU=11,TLNNUSEK=7211,RUFOP=JA,AUTOA
NT=NEIN,DRLEITNG=XX;
EINR-
EINR-
EINR-
EINR-
EINR-
EINR-
EINR-
Release hotline
Set up HOT destination
Set up HOT authorization
CHANGE-COSSU:TYPE=COS,COS=1&13,AVCE=HOT;
Set up hot index on station
Set up mailbox for trunk
EINR-ZIELN:TLNNU=7210,TYP=BKLEITNG,TASNU=06,RNRBK=7210;
Assign additional rights (RNGXFER, DSS, SNR and monitoring)
A31003-H3170-S103-6-7620, 02/2019
key_executive_en.fm
Executive Features
CHANGE-
SDAT:STNO=7210,TYPE=ATTRIBUT,AATTR=SNRLINE&DSSLINE&RNGXF
ERL&MONSNLTL;
CHANGE-
ERL&MONSNLTL;
CHANGE-
SDAT:STNO=7220,TYPE=ATTRIBUT,AATTR=DSSLINE&RNGXFERL&MONS
NLTL;
CHANGE-
SDAT:STNO=7221,TYPE=ATTRIBUT,AATTR=DSSLINE&RNGXFERL&MITH
OERL;
CHANGE-
NLTL;
CHANGE-
NLTL;
CHANGE-
ERL&MONSNLTL;
Set up RNGXFER on station
EINR-
ZIELN:TLNNU=7210,TYP=RULEITNG,TASNU=5,RNRRU=7210,RUFUNKT=XXX;
EINR-
EINR-
EINR-
• Node 100
Configure KYPROG
CHANGE-
TAPRO:STD=127,DIGTYP=OPTIT19,KY01=MENU,KY02=SNR,KY03=CALLOG,K
Y04=SPKR,KY05=RNGXFERL,KY06=MBLINE,KY07=LINE,KY08=BUZZ,KY09=R
NGXFERL,KY10=MBLINE,KY11=LINE,KY12=LINE,KY13=RNGXFERL,KY14=MB
LINE,KY15=LINE,KY16=LINE,KY17=RCUTOFF,KY18=MONSLNTL,KY19=RLS,
INFO="KEY - EXECUTIVE TI";
Configure station
6,DVCFIG=OPTIP500,COS1=13,COS2=1,LCOSV1=5,LCOSV2=1,LCOSD
1=5,LCOSD2=1,DPLN=0,ITR=0,REP=0,STD=127,TEXTSEL=GERMAN,C
ALLOG=ALL;
Phantom station
ADD-
COS1=13,COS2=1,LCOSV1=5,LCOSV2=1,LCOSD1=5,LCOSD2=1,STD=1
27,INS=SIGNOFF;
Configure KEY
A31003-H3170-S103-6-7620, 02/2019
key_executive_en.fm
Executive Features
• primary
ADD-
ADD-
ADD-
ADD-
ADD-
• secondary
EINR-
EINR-
EINR-
EINR-
Release hotline
Set up HOT destination
Set up HOT authorization
CHANGE-COSSU:TYPE=COS,COS=1&13,AVCE=HOT;
Set up hot index on station
Set up mailbox for trunk
Assign additional rights (RNGXFER, DSS, SNR and monitoring)
CHANGE-
ERL&MONSLNTL;
A31003-H3170-S103-6-7620, 02/2019
key_executive_en.fm
Executive Features
Relevant AMOs
CHANGE-
LNTL;
CHANGE-
ERL&MONSLNTL;
CHANGE-
ERL&MONSLNTL;
CHANGE-
LNTL;
Set up RNGXFER on station
EINR-
EINR-
EINR-
121.3 Relevant AMOs

Language
KCSU DRLEITNG d Direktrufleitung mit Taste beim
Direktrufleitungspartner
DSSLINE e dss line with key on dss line partner
SDAT DRLEITUNG d Direkrufleitung
DSSLINE e dss line
RULEITUNG d Rufumschaltung der Leitung erwünscht
RNGXFERL e ring transfer for line desired
WWLEITUNG d WW-Ziel der benutzten Leitung benutzen
SNRLINE e use redail number of used line
MITHOERL d Mithören/Eintreten ohne Ton in Leitung
MONSLNTL e silent monitoring/bridge of line
TAPRO BKLEITNG d Briefkasten für Leitung
MITHOERL d Mithören/eintreten ohne Ton in die Leitung
MONSLNTL e silent monitoring / bridge of line
ZIELN BKLEITNG d Briefkasten für Leitung
A31003-H3170-S103-6-7620, 02/2019
key_executive_en.fm
Executive Features
Relevant AMOs

Language
ZAND DRLEITNG d LED Statusanzeige bei Direktrufleitung
DSSLINE e deactivate LED status display at DSS lines
A31003-H3170-S103-6-7620, 02/2019
key_executive_en.fm
Executive Features
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
digidis_en.fm
Feature Description
122 Flexible optiPoint Display

optiPoint terminals have a one- or two-row display, with 24 characters per row.
With the "flexible Digite display" feature it is possible to change the structure of
the station display and also the system’s response to an "over-long" station
display.
The space between the extension and the name has been reduced from two
positions to one and there is no longer a space between the name and the call
forwarding signal.

• The * is used to indicate the length of the last name.
• The NAME="LAUTSCHNEUZER-STARNBERGER*SABIN" (max. 31

characters) is stored without the asterisk (*).
• This feature has no effect when the display is idle.
122.3 User Interface/Display Formats

• MODE1: Display extension and name
CHANGE-ZAND:TYPE=ALLDATA,DISPMODE=MODE1;
if over-long: name display is truncated
4711 LAUTSCHNEUTZER-STARN
not over-long: full name display
4711 SCHNARCHENDORFER M.
A31003-H3170-S103-6-7620, 02/2019
digidis_en.fm
User Interface/Display Formats
• MODE2: Display extension only - no name display (excessive length not

possible)
4711
• MODE3: No extension display - display name only

if over-long: name display is truncated
LAUTSCHNEUTZER-STARNBERGE
SCHNARCHENDORFER MICHAEL
• MODE4: Display extension and second name

if over-long: no name display
4711
4711 SCHNARCHENDORFER
A31003-H3170-S103-6-7620, 02/2019
digidis_en.fm
Relevant AMOs
• MODE5: Display extension and second name

If over-long: the call number is replaced by the "#" (pound) sign; a shortened
name display is also possible
if over-long: # output instead of call number
# LAUTSCHNEUTZER-STARNBER
not over-long: full name and number display
4711 SCHNARCHENDORFER
122.4 Relevant AMOs

Language
ZAND TYP d AUSWAHL DES DATENTYPS
TYPE=DATENALL
TYPE e DESIRED SYSTEM OPTION
TYPE=ALLDATA
DISPMODE d DISPLAYMODE FUER FLEXIBLE
DISPLAYANZEIGE
MODE1=AUSGABE RUFNUMMER UND
NAME, FALLS DISPLAYTEXT ZU LANG: NA...
MODE2=AUSGABE NUR RUFNUMMER
MODE3=AUSGABE NUR NAME
NAME, FALLS DISPLAYTEXT ZU LANG: NU...
NAME, FALLS DISPLAYTEXT ZU LANG: ST...
DISPMODE e DIGITE DISPLAY MODE
MODE1=DISPLAY EXTENSION AND NAME
MODE2=DISPLAY EXTENSION ONLY
MODE3=DISPLAY NAME ONLY
MODE4=DISPLAY EXTENSION AND
OPTIMIZED NAME
MODE5=DISPLAY OPTIMIZED EXTENSION
AND NAME
A31003-H3170-S103-6-7620, 02/2019
digidis_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
hotrec_en.fm
Hotline/Off-Hook Recall
123 Hotline/Off-Hook Recall

The hotline feature automatically sets up VOICE and DTE connections
immediately via initial seizure to a preset destination assigned in the HOTLN
AMO.
• Assign memory
ADD-DIMSU:TYPE=USER,HOTDEST=<number>;
• Assign a hotline destination
ADD-HOTLN:TYPE=HOTDEST,HTLNIDX=<number>,DEST=<number>;
• Activate the feature:
CHA-FEASU:TYPE=A,CM=HOTRCL;
• Assign the hotline destination to a station
CHA-SDAT:STNO=<number>,TYPE=DATA1,HOTIDX=<number>;
• Assign the attribute HOT for service voice to a station by either assigning it
switchable to a COS of the station (toggling between a COS with attribute
HOT and one without HOT is possible - COS1/COS2 of the station):
CHA-COSSU:TYPE=COS,COS=<number>,AVCE=HOT; (for VOICE)
or assigning it fixed (COS with AVCE=HOT is not necessary in that case):
CHA-SDAT:STNO=<number>,TYPE=ATTRIBUT,AATTR=HOT;
• Assign the attribute HOT for service DTE to a COS of the station 
(toggling between a COS with attribute OFHKRC and one without OFHKRC):
CHA-COSSU:TYPE=COS,COS=<number>,ADTE=HOT;
The off-hook recall feature automatically sets up a connection to a preset
destination assigned in the HOTLN AMO if either no digits are dialled, or only an
incomplete digit sequence is dialled within a preset time. For AnaTe stations, the
connection is also set up after time-out of busy tone from A-B disconnection of
one party or after time-out of busy tone after dialing an Out of Service destination.
This feature is provided for the VOICE service only.
• Assign memory
ADD-DIMSU:TYPE=USER,HOTDEST=<number>;
• Assign an off-hook recall destination
ADD-HOTLN:TYPE=OFRCDEST,HTLNIDX=<number>,DEST=<number>;
• Activate the feature:
CHA-FEASU:TYPE=A,CM=HOTRCL;
• Change the time for automatic connection setup in AMO DTIM2:
Digital phones:
CHA-DTIM2:TYPEDH=GEN,ANATN1=10; 10 seconds is default value.
A31003-H3170-S103-6-7620, 02/2019
hotrec_en.fm
Relevante AMOs
Analog phones:
CHA-DTIM2:TYPEDH=GEN,DTNT1=10; 10 seconds is default value
IMPORTANT: The parameter ANATN1 or DTNT1 is also used to configure

the dial supervision time (i.e. the maximum time allowed between lifting the
handset and dialing a number). If the maximum time allowed is exceeded,
"Timeout" appears on the display.
• Assign the off-hook recall destination to a station

CHA-SDAT:STNO=<number>,TYPE=DATA1,HOTIDX=<number>;
• Assign the attribute OFHKRC to a station by either assigning it switchable to
a COS of the station (toggling between a COS with attribute OFHKRC and
one without OFHKRC is possible - COS1/COS2 of the station):
CHA-COSSU:TYPE=COS,COS=<number>,AVCE=OFHKRC;
or assigning it fixed (COS with AVCE=OFHKRC is not necessary in that
case):
CHA-SDAT:STNO=<number>,TYPE=ATTRIBUT,AATTR=OFHKRC;
123.1 Relevante AMOs

Language
DIMSU HOTZIEL d Speicher für Hotline-, Röchelziel
HOTZIEL e Memory for hotline/offhook destinations
HOTLN TYP d ROEZIEL, HOTZIEL, DATZIEL
TYPE e OFRCDEST, HOTDEST, HOTDEST,
HTLNIDX d gewuenschter hotline index fuer hotline/offhook
ziele
HTLNIDX e desired hotline index for hotline/offhook
destinations
ZIEL d roechelziel
DEST e offhook intercept destination
SDAT TYP d DATEN1
TYPE e DATA1
HOTIDX d hotline index
HOTIDX e hotline index
COSSU HOT d (ESBER/EDBER) hotline
HOT e (AVCE/ADTE) hotline
A31003-H3170-S103-6-7620, 02/2019
hotrec_en.fm
Relevante AMOs

Language
ROE d (ESBER)
OFHKRC e (AVCE) code blue
A31003-H3170-S103-6-7620, 02/2019
hotrec_en.fm
Relevante AMOs
A31003-H3170-S103-6-7620, 02/2019
fwdignor_en.fm
Ignore Call Forwarding
Feature Description
124 Ignore Call Forwarding

Even subscriber B has activated a call forwarding subscriber A is able to call him.

Subscriber B has activated a call forwarding to subscriber C. If subscriber A dials
the access code FWDIGNOR and the extension of subscriber B the call
forwarding of subscriber B will be ignored. If subsriber B is idle he will be called
from subscriber A.

This feature is available for subscribers and the attendant console.
This feature is available for a straight outgoing call as well as for a consultation
call.

AMO WABE, Parameter FWDIGNOR
The following steps have to be performed to activate the feature.
1. DEL-WABE for accesscode FWDIGNOR
2. CREATE-WABE for accesscode FWDIGNOR
3. EX-UPDAT:BP,ALL; to save accesscode on harddisc
Now the feature „Ignore Call Forwarding“ is activated.
124.4 Relevant AMOs

WABE AULIGNOR d Anrufumleitung ignorieren
FWDIGNOR e Ifnore call forwarding
A31003-H3170-S103-6-7620, 02/2019
fwdignor_en.fm
Ignore Call Forwarding
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
tracing_en.fm
Feature Description
125 Malicious Call Identification/Tracing

The "Malicious Call Identification" feature can be used to trace or identify the A-
station’s call number in a OpenScape 4000/HiPath 4000 network, even if the
number is marked as private.
If tracing is performed, the A-station’s call number is output as a system message

at the operating terminal, for example, and not on the B-station’s display.
You can also use this function to identify external callers if MCID evaluation is
activated by the carrier and protocol element transfer is guaranteed for MCID.

When tracing calls on MFC-R2 trunks, a report is printed out and the line is
cleared down once the caller has been traced.
Restrictions
When both COT parameter AMFC and TRACE=YES is set in AMO SBCSU, the
user must activate there TRACE or DTMF features via the corresponding code
WABE.

Initiating a trace:
Tracing is started from the standard attendant console by pressing the unmarked
key above the night switch key (moon symbol). The COS of the AC must include
the MTRACE or ATRACE parameters.
If you want to trace the A-station from the enhanced attendant console, click the
"TOOLS" menu item while a call is in progress and then click "MCID".
You must select the tracing code to activate the MCID feature in a Digite.
Anates differ from Digites in that you must initiate a consultation call in the Anate
before you can select the tracing code.
A31003-H3170-S103-6-7620, 02/2019
tracing_en.fm

General parameters for malicious call identification:
• You must apply to the carrier for the MCID feature before you can trace the
A-station in the public network.
• To add a code:
ADD-WABE:CD=<code for trace>,DAR=TRACE;
• Proceed as follows to enable the feature:
CHA-FEASU:TYPE=A,CM=TRACE&TRACCO;
• To configure a trace code as follows:
CHA-ZAND:TYPE=ALLDATA,TRCD=<code for trace>;
• Timer for tracing jobs (multiple timer, default value 50 seconds)
CHA-DTIM1:TYPEDH=CO,TRACCO=number;
Parameters for the trunk (also required for tie trucks):
• Create a class of parameter for lines to be traced as follows:

ADD-COT:PAR=TRAI;
• Create a class of parameter for lines with initial tracing as follows:
(Finland NO2 signaling):
ADD-COP:PAR=TRAC;
• Define the maximum number of simultaneous tracing jobs per trunk group: 
The TRACENO parameter must be >0.
CHA-BUEND:TGRP=<number>,TRACENO=<number>;
Parameters for stations:
• Assign trace authorization to the station as follows:

CHA-SCSU:STNO=number,COTRACE=YES;
or
CHA-SBCSU:STNO=number,TRACE=Yes;
Parameters for the station or attendant console, for example:
CHANGE-COSSU:TYPE=COS,COS=<COS of attendant console>,
AVCE=MTRACE;
Enhanced attendant console settings

• Deactivate the enhanced attendant console and start the configuration tool.
• Set MCIDEnabled to 1, that is, activate it (or enter in the registry database:
"MCIDEnabled"=DWORD:00000001).
A31003-H3170-S103-6-7620, 02/2019
tracing_en.fm
Relevant AMOs
• Save and exit the configuration tool, then restart the enhanced attendant
console
or see the relevant manual.
125.5 Relevant AMOs

Language
BUEND BUNUM d Bündelnummer
ANZFANG d Anzahl der Leitungen für Fangen im Bündel
( >1 )
TRACENO e NUMBER OF LINES IN A TRUNK GROUP
USED BY TRAPS ( >1 )
COS d Class-of-Service Nummer fuer Sprache
COS e Class of service number for voice
ESBER d Einfügen Sprachberechtigung
MRNRID oder ARNRID
AVCE e Add voice authorization
MTRACE or ATRACE
LTGF (Leitung mit Fangen)
TRAI (Malicious call trace)
TYPE e desired class mark facility options
LM=FANGEN bzw. AMTFANG
CM=TRACE or TRACCO
SBCSU TLNNU d Teilnehmer-Rufnummer
SCSU
STNO e Station number
AMTFANG d Fangen eines Amtsgespräches erlaubt
( JA )
TRACE e Malicious call trace allowed
( YES )
A31003-H3170-S103-6-7620, 02/2019
tracing_en.fm
Relevant AMOs

Language
CD e Access code
KZP d Kennzahlpunkt (FANGEN)
FANGKZ d Fangen Kennzahl
TRCD e Call Trace Code
A31003-H3170-S103-6-7620, 02/2019
man_hold_cons_en.fm
Overview
126 Manual Hold of Consultation
126.1 Overview
This feature will allow a consulted to party to place a call on manual hold. The
feature works for both first and second consultation provided the consulted to
party does not have a background call at the same time.
Party on
consultation
hold
Manual Hold Consulted to party

State that invoked
manual hold
Party is then idle
2nd consulting party

1st consulting party

The consulted to party my invoke manual hold via
– Hold Key
– Dialog Menu
The first Consulting party may
– Toggle
– Transfer
– Release the conection to the party on manual hold
– Release the conection to the party on Consultation hold
– If a second consultation has taken place the first consulting party can
release the call to the second consulting party
The second Consulting party may also
A31003-H3170-S103-6-7620, 02/2019
man_hold_cons_en.fm
Service Information
– Release the call to the first consulting party
The held party in the first consultation may
– Release the call to the first consulting party

The feature “Manual Hold of Consultation” is a pure software feature.
A31003-H3170-S103-6-7620, 02/2019
mula_en.fm
Feature Description
127 Multilingual User Interface

Different languages can be configured for display texts per switch.
One of these languages can be defined as priority language for every subscriber.
Additionally, a language selection key can be configured which allows the user to
select one of the available language in the switch. By pressing this key the next
language configured in the switch is selected. After the language change the
selected language is displayed in the new language (e.g. "Sprache: Deutsch",
"Language: English").
There are two modes (COS) for the duration of the language change:
• Temporary (dynamic) selection:

The language selection is valid until the end of the next call.
Applications: stations frequented by many different users, e.g. , conference
rooms, hotel lobbies.
• Static selection:
The language selection remains valid until changed by the user or the
administrator.
Application: stations used by different users for a longer period of time, e.g.
hotel rooms, working places for guests or consultants

Note the following relations to other features:
• Team/Chese network wide:

The available languages must be configured identically in both switches.
• Announcements:
The user receives the standard announcements independent from the
language selected for the displays.
• Autoset Relocate
If an Up0E moves to a non-multilingual board, the default language becomes
the priority language.
• Programming the key layout:
A31003-H3170-S103-6-7620, 02/2019
mula_en.fm
The user cannot define the language selection key.
• PIN:
Whether station data of the various PIN types is transferred or not, is defined
in the Class of PIN (COPIN). This parameter also defines the transfer of the
priority language. If the PIN type is PIN network wide, the priority language is
only transmitted between nodes connected via CorNet-NQ.
• Cordless 300E (CMI):

On cordless stations the default language of the switch is always the priority
language. On these stations the language cannot be changed.
• Trading / SKY:
The default language of the switch is always the priority language for stations
configured with Trading and SKY. On these stations the language cannot be
changed.

This is a default feature and need not be released using CODEW, FEASU AMO.
• Install the list of languages available in the switch (the first language in the list
is the default language, in the example German. All stations where no other
language was explicitly defined as priority language will use German):
CHA-
ZAND:TYPE=ALLDATA2,TEXTSEL=GERMAN&ENGLISH&PORTUG&FINNISCH;
• Enter a list of languages for the control of the phone inherent special
character tables and for the phone inherent telephone book menu. Make sure
that the languages on positions 1 to 5 in both lists match (LANGID parameter
and TEXTSEL). For the above example enter the following:
CHA-ZAND:TYPE=OPTISET,LANGID=GERMAN&ENGLISH&PORTUG&FINNISCH;
• To activate the new list containing the available languages save the new data
and restart the system:
EXEC-UPDAT:UNIT=BP,SUSY=ALL;
EXEC-REST:TYPE=SYSTEM,RSLEVEL=RELOAD;
• Change the priority language of a terminal:
CHA-SBCSU:STNO=3258,OPT=OPTI,TEXTSEL=GERMAN;
• Switch off all other stations before changing the priority language. Change the
priority language of a Set 400:
DEA-DSSU:OFFTYPE=DI,TYPE=STNO,STNO=3212; /* Deactivate
station 
CHA-SCSU:STNO=3212,TEXTSEL=GERMAN; /* Change priority
A31003-H3170-S103-6-7620, 02/2019
mula_en.fm
Relevant AMOs
language
AC-DSSU:ONTYPE=AUL,TYPE=STNO,STNO=3212; /* Activate
station
• Define the language selection key for a terminal (key 12 in the following
example):
CHA-TAPRO:STNO=3256,DIGTYP=OPTISET,KY12=TEXTSEL;
• Configure the COS for static or dynamic language selection for the user:
CHA-SDAT:STNO=3256,TYPE=ATTRIB,AATTR=TEXTDYN; /* dynamic
selection
or
CHA-SDAT:STNO=3256,TYPE=ATTRIB,AATTR=TEXTSTAT; /* static
selection
127.4 Relevant AMOs

Language
SBCSU TEXTSEL D Textselektion (Sprache für die Displayanzeige)
TEXTSEL E Testselection of display language
SDAT SPRDYN D Dynamische Auswahl der Sprache
LNGDYN E Dynamic language select
SPRSTAT D Statische Auswahl der Sprache
LNGSTAT E Static language select
TAPRO SPRWA D Sprachauswahltaste für Displaytexte
LANSEL E Languageselection for Display texts
ZAND TEXTSEL D Textselektoren im System
TEXTSEL E General settings for individual language setting
of display texts
ZAND SPRACHID D Nationale Zeichensätze für das Display
LANGID E National character set for display
A31003-H3170-S103-6-7620, 02/2019
mula_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
nameorg_en.fm
128 Name and Organization to a Number (ORG Assigning)

Each station number can be assigned several names. 
A name consists of the surname and possibly the first name, which is separated
from the surname by a (*).
The name which appears on the display is always the first name assigned to the
STNO.
The organization unit (department) must always be entered together with a name.
• Enter the name and the organization unit:

AD-PERSI:TYPE=STN,STNO=number,NAME=string,ORG=string;
• Change the display name:
CHA-PERSI:TYPE=NAME,STNO=number,NEWNAME=string;
• Change the name:
CHA-
PERSI:TYPE=NAME,STNO=number,[OLDNAME=string],NEWNAME=string;
• Change the ORGNAME as follows:
CHA-PERSI:TYPE=ORGNAME,STNO=number,NAME=string,NEWORG=string;
Call number display for calling parties

• Change the type of call number display for calling parties:
CHA-ZAND,TYPE=ALLDATA,DISPMODE=<MODE1 .. MODE5>,
• Example: Enter a name with a first name (* divides the two names):
ADD-PERSI:TYPE=STN,STNO=32857, NAME="DR. V. RITTER*MARTIN";
Depending on the mode installed, the following is displayed on the device
display:
MODE1:-> 32857 DR. V. RITTER M.

MODE2:-> 32857
MODE3:-> DR. V. RITTER MARTIN
MODE4:-> 32857 DR. V. RITTER
MODE5:-> # DR. V. RITTER
A31003-H3170-S103-6-7620, 02/2019
nameorg_en.fm
A31003-H3170-S103-6-7620, 02/2019
calipr_en.fm
129 Number Identification

Identification (S0/S2 central office)
For manuel and automatic identifications of numbers to CO two COS-
parametervalues (only for speech) are used:
• Manual number identification

ADD-COSSU:AVCE=MCIDM;
• Automatic number identification
ADD-COSSU:AVCE=MCIDA;
Identification (MFC-R2)
During indentification the number of partner will be displayed. Since that feature
is based on "Identification CO" the AMO-FEASU is applied.
CHA-FEASU:TYPE=A,CM=TRACCO;
• Class of trunk with identification for calls to the attendant
ADD-COT:COTPAR=ATDI;
• Class of trunk with identification for calls over TIE trunks
ADD-COT:COTPAR=TIEI;
• Class of service with indentification for calls to normal subscriber
ADD-COSSU:AVCE=TSUID;
A31003-H3170-S103-6-7620, 02/2019
calipr_en.fm
A31003-H3170-S103-6-7620, 02/2019
on_hook_transfer_subscriber_en.fm
Feature Description
130 On Hook Transfer per User or a Group of Users

The feature „On hook transfer“ should be able to be activated per user or a group
of users.

With the parameter ONHKTRNS in AMO FEASU it is possible to activate the
function that a call transfer is allowed before the consulted party has answered
the call in the whole system. This systemwide parameter is valid for every
consulting party.
The parameter NOONHKTR (no on hook transfer) in AMO SDAT deactivates the
on hook on transfer function per user or a group of users. This disables or enables
for this station a call transfer to a ringing or busy destination.
When a call transfer to a ringing or busy destination is done it is determined if this

call transfer is allowed considering the AMO FEASU and AMO SDAT parameters.
If this is allowed the call is transferred. Otherwise the consulting party gets an
immediate recall from the held party.

The feature „on hook transfer per user or a group of users“ will only be allowed if
in AMO FEASU the parameter ONHKTRNS and in AMO SDAT paramter
NOONHKTRNS are set. If the AMO FEASU parameter ONHKTRNS is not set
then on hook transfer will not be allowed for any station.
It is also possible to use a range of station numbers with the AMO-SDAT in order
to assign the NOONHKTR parameter for a group of stations.
For customers who want to keep the previous situation where every station is
allowed to do on hook transfer only in AMO FEASU parameter ONHKTRNS must
be set.

CHANGE-FEAUS:TYPE=A,CM=ONHKTRNS;
With the AMO SDAT the following command disables on hook transfer for station
2901:
CHANGE-SDAT: STNO=2901,TYPE=ATTRIBUTE,AATTR=NOONHKTR;
The following command enables on hook transfer for station 2901:
A31003-H3170-S103-6-7620, 02/2019
on_hook_transfer_subscriber_en.fm
Relevant AMOs
CHANGE-SDAT: STNO=2901,TYPE=ATTRIBUTE,DATTR=NOONHKTR;
130.4 Relevant AMOs

Language
FEASU UML d Übergabe vor Melden
ONHKTRNS e On hook transfer (transfer before answer)
SDAT NUEBVMEL Uebergeben vor Melden fuer Uebergebenden
erlaubt.
NOONHKTR e On hook transfer (transfer before answer) for
NS consulting party not allowed
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
Boards
131 OpenStage TDM
131.1 Boards
OpenStage devices can be connected to the following boards:
• SLMO24 (Q2158-X)
• SLMOP (Q2169-X100)
IMPORTANT: It is not possible to connect an OpenStage terminal to a SLMQ

board!
131.2 OpenStage terminal types

The following OpenStage TDM terminals are supported:
• OpenStage 10 T
• OpenStage 15 T
• OpenStage 20 T
• OpenStage 30 T
• OpenStage 40 T
• OpenStage 60 T
• OpenStage 80 T
131.3 Transmission Range
Phone Transmission Feeding range for 0,6 mm cable

range
U (OpenScape U (OpenScape
[dB]
Pmax 4000) = 42V 4000) = 48V
[W]
Rcab range Rcab range
[Ohm] [m] [Ohm] [m]
OpenStage 10 T 16 1,5 234 1800 312 2400
OpenStage 20 T 16 1,5 234 1800 312 2400
OpenStage 40 T 16 2,3 130 1000 195 1500
Table 62 Transmission range OpenStage T (0,6 mm cable)
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
Transmission Range

range
[dB]
Pmax 4000) = 42V 4000) = 48V
[W]
[Ohm] [m] [Ohm] [m]
OpenStage 60/80 T 16 2,2 143 1100 221 1700
Table 62 Transmission range OpenStage T (0,6 mm cable)

range
[dB]
Pmax 4000) = 42V 4000) = 48V
[W]
[Ohm] [m] [Ohm] [m]
OpenStage 10 T 16 1,5 234 3100 312 4200
OpenStage 20 T 16 1,5 234 3100 312 4200
OpenStage 40 T 16 2,3 130 1700 195 2600
OpenStage 60/80 T 16 2,2 143 1900 221 3000
Table 63 Transmission range OpenStage T (0,8 mmm cable)
Notes:
1. The actual range depends on the characteristics of the used cable (loss,
diameter).
2. The maximum range is the minimum value of transmission range and feeding
range.
3. If a local power supply is used, the feeding range is not relevant.
4. For transmisson ranges of different cable types please refer to Table 64,
“Transmission range - cable types and their characteristics” (column 16dB).
Cable type Cable values maximum range [m]

Delay Loss RLoop Delay Loss
[s/km] [dB/km] [Ohm/km] 20,8 s 16 dB 14,5 dB
J-2Y(ST)Y4x2x0,51 6,3 9,1 185 3300 1700 1500
LG ICCS Data5
J-2YY ...x2x0,6/1,4 6,3 9,1 130 3300 1700 1500
VIMF FR ICCS
J-02YSCY4x2x0,5 5,5 9,4 190 3800 1700 1500
PIMF ICCS300S
J- 5,5 8,8 164 3800 1800 1600
02YS(ST)CY4x2x0,5
5 PIMF ICCS Data6
Table 64 Transmission range - cable types and their characteristics
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
Transmission Range
Cable type Cable values maximum range [m]

Delay Loss RLoop Delay Loss
[s/km] [dB/km] [Ohm/km] 20,8 s 16 dB 14,5 dB
J-2Y(ST)Y < 6,3 10,8 130 3300 1400 1300
10x2x0,6 STIIIBD
J-2Y(ST)Y > = 6,3 8,8 130 3300 2100 1900
10x2x0,6 STIIIBD
J-2Y(ST)Y < 6,3 n.v.1 73,2 3300 n.v. n.v.
10x2x0,8 STIIIBD
J-2Y(ST)Y >= 6,3 n.v. 73,2 3300 n.v. n.v.
10x2x0,8 STIIIBD
Installation cable < 8 15,6 130 2600 1000 900
10x2x0,6 2
Installation cable >= 8 11 130 2600 1400 1300
10x2x0,6 1
Installation cable < 8 14 73,2 2600 1100 1000
10x2x0,8 1
Installation cable >= 8 8 73,2 2600 2000 1800
10x2x0,8 1
Outdoor cable < 6,3 9,6 130 3300 1600 1400
10x2x0,6 STIIIBD 1
Outdoor cable >= 6,3 7,4 130 3300 2100 1900
10x2x0,6 STIIIBD 1
Outdoor cable < 6,3 n.v. 73,2 3300 n.v. n.v.
10x2x0,8 STIIIBD 1
Outdoor cable >= 6,3 6,1 73,2 3300 n.v. n.v.
10x2x0,8 STIIIBD 1
Outdoor cable 6,3 10,5 300 3300 1500 1300
...x2x0,4 3
A-PM ...x2x0,6 5,5 6 130 3800 2600 2400
STIIILG or BD 3
A-PM ...x2x0,8 5,5 4,5 73,2 3800 3500 3200
STIIILG 3
Table 64 Transmission range - cable types and their characteristics

1 n.v. = no values available
2 see examples below
3 do not use for new installations
Examples for installation cables:
• J-Y(ST)Y Nx2x0,6/0,8 LG
• J-YY Nx2x0,6/0,8 BD
• J-H(ST) H Nx2x0,6/0,8 BD FR NC
• JE-H(ST) H Nx2x0,8 BD FRNCX
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
Accessories
Examples for outdoor cables:
• A-2Y(L) 2Y Nx2x0,4/0,6/0,8 ST III BD 1PPERF
• A-2YF(L) 2Y Nx2x0,4/0,6/0,8 ST III BD
• A-2Y0F(L)2Y Nx2x0,6/0,8 ST III BD
• A-02YS0F(L)2Y Nx2x0,6/0,8 ST III BD
131.4 Accessories
IMPORTANT: Both key modules, the application modules, the display modules,
the busy lamp field and the adapters in the optiPoint series of telephones
cannot be deployed or operated together with OpenStage. The only exception is
the external power supply (L30250-F600-A190-A191-A192) for the telephones.
Device type Function

OpenStage key module Key module with 12 programmable function keys. The user
40, 60, 80 can program one of these keys as a SHIFT key to switch
between two levels.
For OpenStage 40 T, 60 T, 80 T.
Up to 2 units can be connected.
OpenStage15 key Key module with 18 programmable function keys (no 2nd
module level available and therefore no programmable Shift key).
For OpenStage 15 T, 30 T, 40 T.
Only 1 unit can be connected.
OpenStage BLF (Busy 90 additional freely programmable
Lamp Field) keys with LEDs; function, speed dial
or line keys.
External power supply necessary.
For OpenStage 30 T, 40 T.
Only 1 unit can be connected.
OpenStage Phone Optional connection:
Adapter Second OpenStage/optiPoint phone
with UP0/E or, an analog device (phone or fax).
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
Configuration
131.5 Configuration
131.5.1 Terminal Configuration
IMPORTANT: OpenStage 60/80 related settings, like volume or ring type, are not
controlled by the system. So values set via AMO ACTDA/AMO KCSU are not
used.
OpenStage terminals are configured in the same way as optiset terminals:

ADD-
SBCSU:STNO=3100,OPT=OPTI,CONN=DIR,PEN=number,DVCFIG=OPTISET,COS1
=number,COS2=number,LCOSV1=number,LCOSV2=number,LCOSD1=number,LC
OSD2=number,HEADESET=WITHIND;
IMPORTANT: HEADSET=WITHIND must be configured to get the correct

display message in case the headset key is pressed and no headset is
connected.
131.5.2 Key assignment

OpenStage telephones have fixed keys. For this reason, the correct standard key
layouts must be assigned. The keys 1-8 must correspond to the illustrated
examples. The variable keys start from key 9 onwards. Therefore, the appropriate
key layout for every OpenStage terminal is available in AMO TAPRO (parameter
DIGTYP).
SHIFT key
A SHIFT key can also be configured on OpenStage terminals (previously this was
only possible on key modules). This is achieved with the AMO TAPRO or via the
Service menu on the terminal.
CHANGE-TAPRO:STNO=<station number>,KYxx=SHIFT;
IMPORTANT: xx must be greater than 08 since the first 8 keys are fixed.
Only key 9 and onwards can be freely assigned.
When the SHIFT key is pressed on an optiPoint key module, the same action is
performed on all other key modules. In other words, the SHIFT level is also
activated on the second and fourth key modules.
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
Configuration
This is not the case on OpenStage telephones and key modules. In this case, the
SHIFT level is only activated on the telephone/key module on which the SHIFT
key was pressed.
131.5.3 Master/Slave Configuration Downstream

from Up0 Extender (Phone Adapter)
Figure 114 Phone adapter (Up0 extender)
Possible use
The following terminals can be connected to the phone adapter:
• Up0 system telephone:
– OpenStage 20 T
– OpenStage 40 T
– OpenStage 60 T and 80 T (require their own power supply unit)
– optiPoint 500 (must be connected to Up0 Slave output socket)
– optiset E (must be connected to Up0 Slave output socket)
• Analog device:
– Phone with MFV tone dialing (e. g. Euroset 5020 or a cordless phone
such as Gigaset A160),
– a Group 3 fax or
– a modem.
IMPORTANT: Analog telephones at the phone adapter act as DSS1 phones.

Therefore the same call processing features available to S0/S2 terminals with
the E-DSS1 protocol are also available to the analog terminals at the
telephone adapter. This means that some of the normally available ANATE
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
Configuration
features are not supported.

For example:
PIN-specific features, such as class-of-service changeover, follow me/FWD
transfer,
Autoset relocate,
Night station
The Phone Adapter can be used in the following configurations only:
• One Up0 system telephone (Up0 Master)
• Two Up0 system telephones (Up0 Master, Up0 Slave)
• One Up0 system telephone and one analog terminal (Up0 Master, a/b)
IMPORTANT: It is not possible to operate two Up0 system telephones and one
analog device.
Installation
OpenScape 4000
Phone
Terminal Adapter
Terminal
Ports on the Phone adapter

There are five sockets (from right to left):
• Power
• Up0-IN (from the OpenScape 4000)
• Up0-Out1 (to the master phone) = Up0 Master output socket
• Up0-Out2 (to the slave phone) = Up0 slave output socket
• a/b = analog output socket
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
Configuration
A small slide switch is located between the Up0-Out2 and the a/b. When the slide
switch is moved, the output closest to it is enabled:
• if the switch is moved to the left towards the a/b socket -> the a/b (analog)
output is enabled, you can connect an analog device
• If the switch is moved to the right: the Up0 slave is enabled, you can
connect a further Up0 phone
The switch is read during power-up, and then enables the appropriate output.
Reconfiguration during live operation is therefore not possible.
You must connect an OpenStage phone to the “Up0 Master output socket” in order to be
able to operate devices on the “Up0 Slave” and “Analog” output sockets..
Example
Up0 master:
ADD-
SBCSU:STNO=3100,OPT=OPTI,CONN=DIR,PEN=number,DVCFIG=OPTISET&VIR
TDTE,COS1=number,COS2=number,LCOSV1=number,LCOSV2=number,LCOSD1=
number,LCOSD2=number,DPROT=SBDSS1,DOPTIDX=1;
Up0 slave:
ADD-
SBCSU:STNO=3101,OPT=OPTIEXP,MAINO=3100,DVCFIG=OPTISET&VIRTDTE,D
PROT=SBDSS1,DOPTIDX=1;
The terminal must now still be activated:
RESTART-DSSU:TYPE=STNO,STNO=3100&3101;
or
Analog device:
The analog device can be configured with the same call number as ANAFAX:
ADD-
SBCSU:STNO=3100,OPT=OPTI,CONN=DIR,PEN=number,DVCFIG=OPTISET&VIRT
DEE&ANAFAX,COS1=number,COS2=number,LCOSV1=number,LCOSV2=number,L
COSD1=number,LCOSD2=number,DPROT=SBDSS1,DOPTIDX=1;
or as an analog device with another call number:
Up0 master:
ADD-
SBCSU:STNO=3100,OPT=OPTI,CONN=DIR,PEN=number,DVCFIG=OPTISET&VIRT
DEE,COS1=number,COS2=number,LCOSV1=number,LCOSV2=number,LCOSD1=n
umber,LCOSD2=number,DPROT=SBDSS1,DOPTIDX=1;
Up0 slave:
ADD-SBCSU:STNO=3101,OPT=OPTIEXP,MAINO=3100,DVCFIG=ANADEV;
For further details on the Phone adapter please refer to the installation guide.
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
Configuration
131.5.4 OpenStage Busy Lamp Field

In AMO TAPRO the appropriate key layout for the terminal must be chosen.
The OpenStage busy lamp field is also supported for optiPoint 500.
Hint:
Adding each BLF module uses 5 counts of DIMSU parameter OPTEXP.
OpenStage BLF for OpenStage
CHANGE-SBCSU:STNO=3100,OPT=OPTI,REP=0,BLF=Y;
CHANGE-TAPRO:STD=55,DIGTYP=OST40BLF;
OpenStage BLF for optiPoint 500
The key configuration is similar as for an OpenStage device with busy lamp field.
Not 90 keys are configured on one add-on device but 5 add-on devices each with
18 keys. So each column with 18 keys on the busy lamp field can be thought as
one add-on device.
For OpenStage BLF for optiPoint 500 the DIGTYP value OPTIBLF has been
introduced for the busy lamp field in AMO TAPRO. A layout with this type has to
be used for the key layout configuration of an optiPoint device with BLF.
A number for the key layout (STD=127) for the DIGTYP=OPTIBLF must be
configured.
Example:
CHANGE-SBCSU:STNO=3110,OPT=OPTI,REP=0,BLF=Y;
CHANGE-TAPRO:STD=127,DIGTYP=OPTBLF,KY01=CH;
REGEN-TAPRO:TYPE=STD,STD=127;
CHANGE-TAPRO:,127,OPTIBLF ,CH ,FREE ,FREE ,FREE ,FREE ,
FREE ,FREE ,FREE ,FREE ,FREE ,
FREE ,FREE ,FREE ,FREE ,
" ";
CHANGE-TAPRO:,127,OPTIB1 ,FREE ,FREE ,FREE ,FREE ,FREE ,
FREE ,FREE ,FREE ;
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
Configuration
FREE ,FREE ,FREE ;

FREE ,FREE ,FREE ;
FREE ,FREE ,FREE ;
FREE ,FREE ,FREE ;
AMO-TAPRO-111 PROGRAMMABLE KEY DEFINITION FOR DIGITAL

TERMINALS
REGENERATE COMPLETED;

Language
SBCSU BEIGER d Anzahl der vorhandenen Beistellgeräte
REP e Number of add-on devices
BLF d Belegtlampenfeld
BLF e Busy Lamp Field
TAPRO DIGTYP d Art des Sprachterminals (OPTIBLF,
OST40BLF, ...)
DIGTYP e Type of voice terminal (OPTIBLF,
OST40BLF, ...)
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
TDM Software Download
131.6 TDM Software Download
IMPORTANT: The TDM Software Download is only supported for OpenStage

endpoints connected to a SLMOP (issue 9 or higher) or to a SLMO24.
The TDM Software Download is not supported for OpenStage endpoints
connected to a STHC/SLMQ.
New software for the TDM OpenStage telephones and the Phone adapter can be
downloaded via the TDM software download. The download is started via the
TDM Software Deployment Manager (Software Management - TSDM) in
OpenScape 4000 Assistant. The application first transfers the telephone software
to one OpenStage TDM telephone via the D channel. This terminal establishes a
B channel connection to another OpenStage TDM telephone via the virtual S0
adapter (AMO SBCSU: parameter VIRTDTEE (for VIRTDEE no licenses are
required)) and transfers the telephone software via the B channel. These two
telephones establish B channel connections to other OpenStage telephones,
ensuring that the telephone software is transferred to all TDM OpenStage
telephones during this "snowball" TDM download. So that the TDM software
download can function correctly, the parameter ADTE=GRUBE must also be set
in the AMO COSSU.
Refer to the online help for further information about „TDM Software Deployment
Manager“.
TDM download times:
• Via D channel to TDM OpenStage 20T/40T: Approximately 5 minutes
• Via B channel to TDM OpenStage 20T/40T: Approximately 1,5 minutes
• Via D channel to TDM OpenStage 60T/80T: Approximately 4,5 hours
• Via B channel to TDM OpenStage 60T/80T: Approximately 1,5 hours
131.6.2 Restriction
The "fast" (via B channel) TDM software download (snowball system) does not
work if the OpenStage TDM is also configured for 1st Party CTI (AMO SBCSU,
DVCFIG=API). This is because the terminal must be configured for B channel
download in the AMO SBCSU using DVCFIG=VIRTDTE. However, for 1st Party
CTI, DVCFIG=API must be configured in the AMO SBCSU. Both are not possible
at the same time.
A31003-H3170-S103-6-7620, 02/2019
openstage_tdm_en.fm
OpenStage TDM
TDM Software Download
The only alternative for customers that use 1st party CTI on OpenStage TDM
telephones is the "slow" software download via the D channel, which must be
activated separately for each telephone in OpenScape 4000 Assistant.
1. As described before, the telephones on which the software is to be loaded
must be configured with the new value VIRTDTE instead of DTE.
ADD-
SBCSU:STNO=3100,TYPE=OPTI,CONN=DIR,PEN=number,DVCFIG=OPTISET&
VIRTDTE,COS1=number,COS2=number,LCOSV1=number,LCOSV2=number,L
COSD1=number,LCOSD2=number,DPROT=SBDSS1,DOPTIDX=1;
2. In addition to VIRTDEE, the GRUBE COS parameter must be set under DEE
in the AMO SBCSU:
DIS-COSSU:TYPE=COS,COS=<cos_number>;
H500: AMO COSSU STARTED
+------+-----------------+---------------+-----------------+
| COS | SPEECH | FAX | DTE |
+------+-----------------+---------------+-----------------+
| 13 |> |
| | TA | TA | TA |
| | TNOTCR | TNOTCR | TNOTCR |
| | CDRSTN | BASIC | BASIC |
| | COSXCD | | |
| | MB | | |
| | CFNR | | |
| | FWDNWK | | |
| | TTT | | |
| | FWDECA | | |
+------+-----------------+---------------+-----------------+
AMO COSSU-111 - Classes of service

If GRUBE is not entered in the DEE column, this must be configured:
CHA-COSSU:TYPE=COS,COS=<cos number>,ADTE=TA&TNOTCR&BASIC;;
3. The terminal must now still be activated:
RESTART-DSSU:TYPE=STNO,STNO=3100;
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Types
132 PIN (Personal Identification Number)

The personal identification number (PIN) is used for identification of a call number
by the system. Each call number can be assigned any number of PINs. There are
15 different types of PINs, each of which (exception: PINC) can be activated by
means of its own code (AMO WABE). A PIN application is initialized for each type
of PIN. The predefined PIN applications can be altered or redefined by specifying
additional PIN/PCODE attributes.
132.1 PIN Types

The following PIN types are defined in the system:
PIN1 (Mobile Users)

PIN1 is used for identification by manual dialing (mobile users).
Use:
Users can "identify" themselves to the system at a "foreign" station by dialing
a secret PIN, which does not appear on the display when dialed. This enables
them to use the class-of-service (COS1) and key functions of their "home"
station. The PIN is active for a specific, configurable time. The PIN and the
call number of the user’s home station are entered in the call data recording
records as the chargee for any calls made.
Users can deactivate their PIN1 before the timer runs out via a corresponding
delete procedure.
PIN2 (Business, Long-Term)

PIN2 is used for the identification of business calls, and remains active until
deleted manually.
Use:
Following input, the PIN is permanently activated.
The PIN can be deactivated via a delete procedure.
PIN3 (Business, Per-Call)

PIN3 is used for the identification of a single business call.
Use:
The PIN is only active for the duration of the call. At the end of this period the
station reverts automatically to its operating state prior to input of the PIN3. If,
for example, a PIN2 was active before the PIN3 was input, then the former
becomes active again as soon as the PIN3 call has been terminated!
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Types
PIN4 (Private, Per-Call)

PIN4 is used for the identification of a single private call.
Use:
The PIN is only active for the duration of a call. At the end of this period the
station reverts automatically to its operating state prior to input of the PIN4.
This is an effective means of distinguishing business calls from private calls
in the call data recording records.
PIN5 (PCODE)
PIN5 is used for the identification of a project-specific call (project code=PCODE).
Use:
The project code is a digit sequence which is assigned to a project, object,
etc. It is used for allocating costs, e.g. telephone charges, to a specific project.
Unlike the personal identification number (PIN), the project code (PCODE) is
not assigned to a specific user. The classes of service (COS1) and features
of the station at which the PCODE was entered are available to the caller. The
PCODE can be checked for validity (see also Section 132.14.10, “Verifying
the PIN/PCODE”). It is not secret and concealed input is not necessary. Input
errors are indicated on terminals with displays.
PIN6: PINC (PIN CARD)

PINC is used for identification by means of a magnetic card or chip card which is
inserted in the identity card reader at the terminal.
Use:
Users identify themselves by inserting/removing a chip card. The identity card
has priority over PIN1.
V2.0 and higher supports the application-based use of smart cards (see Chapter
138, “Smart Card Application”).
PIN7: COSXCD (Class of Service Changeover Code)

COSXCD is used for identification purposes in connection with the activation of
class of service changeover from the terminal.
Use:
Class of service changeover from COS 1 to COS 2 and vice versa can be
performed with the aid of the PIN. It is possible to configure whether
changeover to COS 2 is to take place with or without prior input of the PIN.
PIN8: Service Identification PIN (Service Identifier)

The service identifier (SI) is used by service personnel as a top-priority PIN for
"registering" or canceling a user at a terminal (see also Section 132.11, “Service
Identifier” on "Autoset Relocate" feature).
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
Functions / Restrictions when using a PIN
PIN9: CDRAC (Account Code)

The "Account Code" feature allows individual incoming and outgoing calls to be
assigned an account number or, consecutively, with several account codes which
are displayed in the call data recording records (see also the chapter on call data
recording).
PIN10 (Forced-Authorization-Code)
A PIN code is demanded for certain voice numbers configured in the LCR
Dialplan for calls to the public network or on tie line circuits dialed during an initial
call, a consultation call or when performing call forwarding. A typical application
case is, for example, on a campus, where users have to identify themselves via
PIN on generally accessible phones for the purposes of call charging.
For further information, please refer the Feature Usage Example LCR (Least Cost
Routing, Section 37.11, “LCR Autorization PIN (Forced Authorization Code)”.
PIN11 to PIN15 (Mobile Users)

PIN11 to PIN15 are predefined as per PIN1 and can be configured and used like
PIN1.
132.2 Functions / Restrictions when using a PIN
Feature Internal PIN

Transfer authorizations For outgoing calls only, not for incoming calls.
PIN for call detail recording Yes
Follow me / FWD transfer. Yes
Caution: Note the restrictions for
FWD and FNA
Speed dialing facility Yes
Individual speed dialing Yes
WABE The WABE group of the originating station is valid.
IBM SMART, CF switch Yes (for virtual and physical stations).
ITR group The ITR group for the originating station is valid.
Repertory dialing keys Repertory dialing keys are transferred provided they
are configured on the device. Both devices should
be the same type (although it is theoretically
possible, modifying the layout is too complicated).
DSS keys See repertory dialing keys.
Redial Transferred.
Enter timed reminder Yes. A timed reminder is entered on the originating
station and is later diverted via the call forwarding
(follow-me) function. This means it can also be used
for virtual stations.
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN / PCODE Activation
Feature Internal PIN

Mailbox Yes. Standard access and scroll functions for
mailbox. In the case of VMS, a connection to the
server is established by pressing the start key. View,
perform and delete callbacks.
132.3 PIN / PCODE Activation

The PIN / PCODE is activated prior to the call being placed. This can take place
in idle state or in dialing state by using the appropriate code or via the service
menu.
When you enter the PIN, you can choose to display ’*‘ instead of the actual PIN.
CHA-PERSI:TYPE=COPIN,COPIN=number,DISPPIN=NO;
Internal PIN also allows the PIN to be entered in consultation state. A short PIN
is only valid for the consultation call and is automatically deleted at the end of the
call. A long PIN entered in consultation state is valid for the consultation call and
the following calls, as long as the PIN is activated.
A PIN cannot be activated in consultation state with "network-wide PIN".
In the case of activated COS2 at terminals in use, PIN entry can be prevented
with:
CHA-PERSI:TYPE=COPIN,COPIN=number,PINLCOS2=YES;
132.4 Length of PIN

The length of the particular type of PIN is defined centrally; it is possible to define
the same length for all PIN types, or different lengths for different PIN types. Each
PIN number (except for COSXCODE) must be unique in the system.
For the network-wide PIN feature, the same PIN numbers may be assigned in
different nodes. The length of a particular PIN type may also vary from node to
node.
The manually entered PIN/PCODE consists of a maximum of 12 characters,

either digits or the character *. The PIN for a card also comprises 12 characters
(digits, letters, special characters) from the ASCII character set. The hash
character ’#’ is no longer permissible as a PIN/PCODE/SI character, since this
character is used as an end-of-string character for the network-wide PIN feature.
Before the length of a PIN number can be changed, all PINs of this type must be
deleted.
Change length of PINC (ID-card PIN):
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
Manual PIN Types (PIN1 to PIN4 and PIN10-15)
CHA-PERSI:TYPE=SYS,PINCLEN=number;
132.5 Manual PIN Types (PIN1 to PIN4 and PIN10-15)

• Assign digit analysis results for PIN1 to PIN4 and PIN10 to PIN15 activation
code:
ADD-WABE:CD=key-num,DAR=APIN1; 
ADD-WABE:CD=key-num,DAR=APIN15;
• Assign digit analysis results for PIN1 to PIN4 and PIN10 to PIN15
deactivation code:
ADD-WABE:CD=key-num,DAR=DPIN;
IMPORTANT: Please note that there is only one digit analysis result for PIN
deactivation. It applies to PIN types PIN1 to PIN4 and PIN10 to PIN15
• Assign length of PIN number

ADD-
PERSI:TYPE=SYS,PIN1LEN=number,PIN2LEN=number,PIN3LEN=number,
PIN4LEN=number,PIN10LEN=number,PIN11LEN=number,PIN12LEN=numbe
r, PIN13LEN=number, PIN14LEN=number, PIN15LEN=number;
• Assign PIN to a station number
ADD-
PERSI:TYPE=STN,STNO=number,PIN1=string,PIN2=string,PIN3=strin
g, PIN4=string,PIN10=string,PIN11=string,PIN12=string,
PIN13=string, PIN14=string, PIN15=string;
• Changing PIN (OLDPIN and NEWPIN must be of equal length)
CHA-PERSI:TYPE=PIN,OLDPIN=string,NEWPIN=string;
132.6 PIN Card (Chip Card)

• Assigning length and pointer of chip card PIN
ADD-PERSI:TYPE=SYS,PINCLEN=number,PINPOINT=number;
• Assigning personal identification number to a station number
ADD-PERSI:TYPE=STN,STNO=number,PINC=string;
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
Class of Service Changeover Code (COSXCD)
• Changing pointer of chip card PIN

CHA-PERSI:TYPE=PINPOINT,PINPOINT=number;
• Changing PINC number (OLDPIN and NEWPIN must be of equal length):
132.7 Class of Service Changeover Code (COSXCD)

• Assigning codes for class of service changeover
ADD-WABE:CD=key-num,DAR=ACOSX; (activate) 
ADD-WABE:CD=key-num,DAR=DCOSX; (deactivate)
• Assigning length of class of service changeover code

ADD-PERSI:TYPE=SYS,COSLEN=number;
• Assigning COS changeover code as personal identification number
ADD-PERSI:TYPE=STN,STNO=number,COSXCD=string;
• Change class-of-service switchover code (OLDPIN and NEWPIN must be of
equal length):
132.8 Class of Service Changeover to COS2 without COSXCD

It is also possible to switch over to COS2 without entering the COSXCD, by
dialing the DCOSX code instead.
ADD-PERSI:TYPE=SYS,COSXCOS2=N;
132.9 PIN Display on DIGITE Display

Setting PIN display for PIN types
ADD-PERSI:TYPE=SYS,PINDISP=number;
132.10 Project Code

• Assign digit analysis results
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
Service Identifier
ADD-WABE:CD=number,DAR=APIN5;
ADD-WABE:CD=number,DAR=DPIN;
IMPORTANT: Please note that there is only one digit analysis result for PIN
deactivation. It applies to PIN types PIN1 to PIN5 and PIN11 to PIN15.
• Assign length of PCODE

ADD-PERSI:TYPE=SYS,PIN5LEN=number;
• Assign project code
ADD-PERSI:TYPE=PCODE,PCODE=string,PINTYPE=5;
132.11 Service Identifier

• Assign DAR pair for service indicator for feature "Autoset Relocate"
(SIGNON/SIGNOFF)
ADD-WABE:CD=key-num,DAR=SIGNON,CD2=key-num;
IMPORTANT: CD = code for signing on, CD2 = code for signing off.
• Assign length of service identifier

ADD-PERSI:TYPE=SYS,SILEN=number;
• Assign service identifier
ADD-PERSI:TYPE=SI,SI=string;
132.12 Account Code

• Assign DAR pair for service indicator for feature "Account Code"(SIGNON/
SIGNOFF):
ADD-WABE:CD=key-num,DAR=CDRACC;
IMPORTANT: CD = code for signing on. Signing off is performed automati-

cally at the end of the call.
• Assign length of Account Code:

ADD-PERSI:TYPE=SYS,CDRACLEN=number;
• Assign Account Code (only numerical entries permitted):
ADD-PERSI:TYPE=CDRAC,CDRAC=number;
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
Forced Authorization Code
132.13 Forced Authorization Code

• Assign length of Forced Authorization Code:
ADD-PERSI:TYPE=SYS,PIN10LEN=number;
• Assigning Forced Authorization Code to a station number:
ADD-PERSI:TYPE=STN, STNO=number,PIN10=string;
132.14 PIN Attributes

All 15 PIN types can be used in a system concurrently. Each PIN type can be
assigned with similar and/or different attributes. These attributes are contained in
PIN classes called COPIN (class of PIN). The COPINs 1 - 7 and 9 - 15 can be
changed with the AMO PERSI; COPIN 8 is an SI PIN type, the initialized values
of which may not be changed.
The following PIN attributes can be defined in a COPIN:
132.14.1 PIN Type

COPINs 1 to 5 and 10 to 15 can be assigned to any of the following PIN types:
• mobile user (MOBILE)
• Project code (PCODE)
• Business calls, long-term activation (BUSLONG)
• Business calls, activation per call (BUSSHRT)
• Private calls, activation per call (PRIVSHRT)
This is not possible for the following COPINs, as these are of a fixed defined type:
• COPIN 6: PIN CARD
• COPIN 7: COSXCD
• COPIN 8: SI
• COPIN 9: CDRAC
You can also assign a PINTEXT or description of the COPIN in order to identify it
more easily.
Change PIN type (e.g. in PCODE)

CHA-PERSI:TYPE=COPIN,COPIN=<number>,COTYPE=PCODE,PINTEXT="PCODE
2";
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Attributes
132.14.2 Duration of PIN Activation

The PIN can be activated for 1 call only, permanently or for a pre-defined time.
The timer required for the latter option is administered with the CTIME AMO.
• Duration of PIN activation

Set PIN duration for 1 call only
CHA-PERSI:TYPE=COPIN,COPIN=number,PINDUR=ONE;
Set PIN duration to ’permanent’
CHA-PERSI:TYPE=COPIN,COPIN=number,PINDUR=PERM;
Set PIN duration to ’timed’
CHA-PERSI:TYPE=COPIN,COPIN=number,PINDUR=TIME;
• Set timer for timed PIN for PIN types PIN1 - 5 and 10 to 15 for Voice and Non
Voice
CHA-CTIME:TYPESWU=CP1,PINV01=number,PINNV1=number; 
CHA-CTIME:TYPESWU=CP1,PINV05=number,PINNV5=number;
CHA-CTIME:TYPESWU=CP2,PINV015=number,PINNV15=number;
Important note on the PIN timer:

For this timer, values between 1 second and 18 hours can be entered. Setting the
timer value in minutes (default: 5 min.) is recommended, as the timer is restarted
after end of call and the active time of the PIN is extended. Setting the timer value
in hours and a high number of PIN activations could lead to lack of resources, i.e.
timer elements which, in turn, leads to system restarts.
132.14.3 User Identification Display on Digite

When a PIN user activates his/her PIN at a foreign station, the telephone display
shows ’IDENTIFICATION stno’ as a positive acknowledgement. The ’stno’ output
is a variable, defined by the user’s home station number. The length of this
display can be set to ’permanent’ or ’timed’ (default value 5 seconds).
• Timed identification display

CHA-PERSI:TYPE=COPIN,COPIN=number,DISPID=TIMEDISP;
• Permanent identification display
CHA-PERSI:TYPE=COPIN,COPIN=number,DISPID=PERMDISP;
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Attributes
132.14.4 PIN-Identification at Home Station Only

PIN codes can be further restricted for use at the user’s home station only.
• PIN-identification at home station only:

CHA-PERSI:TYPE=COPIN,COPIN=number,IDHOME=Y;
132.14.5 Transferring classes of service

You can ’transfer’ the COS1 classes of service from the home station to the
foreign station and operate them from the foreign station.
CHA-PERSI:TYPE=COPIN,COPIN=number,TRANSFER=ALL;
To use the home station’s current COS for identification at the foreign station:
CHA-PERSI:TYPE=COPIN,COPIN=number,COSHOME=YES;
132.14.6 COS and Key Function Transfer from Home

Station (internal PIN only)
With the internal PIN feature, certain key functions and LED functions can be
transferred from the user’s home station, and used at the foreign station for the
duration of the PIN activation. This function is not possible with the network-wide
PIN feature.
The following key functions and LED functions can be transferred from the user’s
home station:
Repertory keys (REP) and Direct Station Select (DSS) keys are transferred to the
same position on the foreign station
• Mailbox LED (MB)
• Call forwarding key (FWD)
• Saved number redial key (SNR)
• Timed reminder (REMIND) keys. The keys can be programmed at a foreign

station (timed reminder call follows call forwarding).
• Enable function transfer for key functions and COS (incl. ITR and DPLN
groups) (internal PIN feature only):
CHA-PERSI:TYPE=COPIN,COPIN=number,TRANSFER=ALL;
• No function transfer
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Attributes
CHA-PERSI:TYPE=COPIN,COPIN=number,TRANSFER=NO;
IMPORTANT: The function transfer is only possible for the internal PIN
feature, i.e. not possible for the network-wide PIN feature.
132.14.7 PIN-Entry in Repertory Keys and Speed

Dialing List (internal PIN only)
• Allow PIN entry in repertory keys and individual speed dialing list.
CHA-PERSI:TYPE=COPIN,COPIN=number,PINKEY=Y;
132.14.8 Automatic Exchange Seizure

Automatic exchange line seizure after PIN/PCODE entry. The PIN user can
immediately begin dialing the public network subscriber’s number. The Digite
display shows the exchange line access code.
• Add exchange code

ADD-WABE:CD=key-num,DAR=CO;
• Define code for automatic exchange line seizure with universal exchange
access code
CHA-PERSI:TYPE=COPIN,COPIN=number,TRKCD=key-
num,TRKCDTYPE=UNICD;
In a different variant of this feature, you can disable the universal exchange
access code for the user, i.e. the user cannot seize an exchange line without
dialing the PIN. Assign with WABE AMO (CPS=4 for ATND) and AMO RICHT.
• Assign exchange access code

ADD-WABE:CD=key-num,CPS=4,DAR=AMT;
• Define code for automatic exchange line seizure via PIN only.
CHA-PERSI:TYPE=COPIN,COPIN=number,TRKCD=key-
num,TRKCDTYPE=PINCD;
• It is also possible to prevent automatic exchange seizure.
CHA-PERSI:TYPE=COPIN,COPIN=number,TRKCDTYPE=NO;
After the automatic exchange seizure, the PIN text "Identification
CD" appears on the Digite display. The exchange access code is
shown on the display instead with the following setting:
CHA-PERSI:TYPE=COPIN,COPIN=number,ANZAMTKZ=YES;
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Attributes
132.14.9 Additional Text for Call Data Recording

(internal PIN only)
Users can choose between a PIN type by dialing a code. An additional text entry
in the call data record allows users to discriminate between calls made with
different PIN types and assign call charges accordingly. The additional text is an
ASCII character string between 1 and 11 characters. The length of the PIN also
defines the maximum length of the additional text. The PIN and CDRTEXT
together must not exceed 12 characters.
• Assign additional text for CDR (internal PIN feature only)

CHA-PERSI:TYPE=COPIN,COPIN=number,CDRTEXTS=Y,CDRTEXT=text;
Note:
Additional CDR texts with the AMO PERSI are not permitted for the network-wide
PIN feature. Workaround: configure additional CDR texts with the CDR AMOs.
IMPORTANT: The configuration of additional CDR texts via the AMO PERSI are
only permitted for the internal PIN feature, i.e. not for the network-wide PIN
feature.
132.14.10 Verifying the PIN/PCODE

The PIN/PCODE can undergo several tests, in order to prevent unauthorized use,
as far as possible. The following test settings can be defined:
• The PIN/PCODE is not tested (for PIN9-CDRAC only)

CHA-PERSI:TYPE=COPIN,COPIN=number,PINTEST=NO;
• Only the length of the PIN is checked
CHA-PERSI:TYPE=COPIN,COPIN=number,PINTEST=LENGTH;
• The PIN/PCODE is checked against the PIN/PCODE table. This is only
possible for the internal PIN feature:
CHA-PERSI:TYPE=COPIN,COPIN=number,PINTEST=TABLE;
• The PIN/PCODE is checked algorithmically (modulo test). You can choose
between 3 different test algorithms, MODULO1, MODULO2 or MODULO3:
CHA-PERSI:TYPE=COPIN,COPIN=number,PINTEST=MODULO1 or
MODULO2 or MODULO3;
IMPORTANT: PIN/PCODE table verification is not possible for the network-

wide PIN feature.
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Attributes
132.14.10.1 Algorithmic "MODULO-N" Verification of PIN/

PCODE
Test algorithm
Customers can set the verification algorithm required for the MODULO-N
verification function.
The expected PIN entry consists of the administered PIN code plus a verification
code, i.e. PIN length = PIN+verification code. The verification code is 1-2 digits
long and must be included in the PIN, as follows:
Formula for MODULO-N verification
PIN: k P1 k P2 k P3 k P4 k
x x x x k alternative, possible positions for
verification code
Weighting: G1 G2 G3 G4
--------------------------------------------------------------
Product: pPG1+ pPG2+ pPG3 + pPG4 = check sum
(or: qpPG1+qpPG2+qpPG3+qpPG4 )
Modulo-N: Check sum + = x, remainder y
modules
The verification code can either be defined as:

code = remainder y
or
code = modulus minus remainder y (complement)
Key to abbreviations in above equations:
P = PIN code digit

G = Weighting value
pPG = Product of (P x G)
qpPG = Sum of digits of products of (P x G)
The verification code is calculated as follows:

1. Each individual digit of the PIN code is multiplied with the appropriate
weighting value. When assigning the weighting values (parameter
VALENCE), a value must be specified for each entered digit of the PIN, i.e.
PIN code plus verification code. This is especially important if the verification
code position is not at the end of the actual PIN code.
2. The check sum is achieved by
a) adding each product of (PxG), see example

or
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Attributes
b) adding the sum of the digits of each product of (PxG)
3. The modulo-N operation is then performed, i.e. the check sum is divided by
the modulus. The verification code can either be defined as
a) the remainder left over from this division (see example)

or
b) the difference between the remainder and the modulus (complement).
Note:
• Single-digit verification code
If the verification code is defined as a single-digit code, and the calculated
verification code is a two-digit number, the first digit is dropped and only the
second digit is used (i.e. ’19’ becomes ’9’)
• Two-digit verification code:

If the verification code is defined as a two-digit code, and the calculated
verification code is a single-digit number, a zero is prefixed as the first digit
(i.e. ’9’ becomes ’09’).
PIN length = PIN code plus verification code (if assigned).
PERSI settings for the MODULO-N verification:

You can define up to 3 modulo-N algorithms with the AMO PERSI. These are
assigned to PIN types via the class-of-PIN COPIN.
Algorithm settings:
• Weighting value (VALENCE).
Single-digit value, from 1 - 9. Must be specified for all 12 possible digits of a
PIN number.
[Default: 2-1-2-1-2-1-2-1-2-1-2-1]
• Modulus (MODULUS).
Up to two digits, from 2 - 99
[Default: 10]
• Length of verification code (CHKNLEN)

Single-digit or two-digit code (1 or 2)
[Default: 1] = single digit
• Calculation of verification code (TYPECHKN)

- remainder of modulo-N operation (division)
or
- complement of remainder to modulus
[Default: complement of remainder to modulus]
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Attributes
• Check sum type (TYPESUM)

- sum of products of (PxG)
or
- sum of all digits of products of (PxG)
[Default: sum of products]
PIN type-specific settings

• Position of the verification code within the PIN code (1st pos. - 12th pos.)
The position of the verification code is entered in the COPIN, which is
assigned per PIN type. The PIN length of the PIN type(s) using the COPIN
must be observed.
[Default: 1st position]
Example:
Set up modulo-N algorithmic verification for PIN type PIN2.
Relevant parameters:
• Length of PIN 5 digits

• Weighting value per digit 5432
• Modulus 11
• Position of verif. code 5th position
• Length of verif. code 1 digit
• Calculation of verif. code remainder of modulo-n division
• Check sum type sum of products of (PxG)
The PIN to be checked is: 47119
verification code
PIN: 4 7 1 1 9
x x x x
Weighting: 5 4 3 2 1
----------------------------------------------------------------------------------------
Product: 20+ 28+ 3+ 2 = 53
Modulo-N: 53 : 11 = 4 Rest 9 =9
Verif. digit type = remainder = 9 PIN 47119 is valid
(in the above example, if the modulo-N remainder were 10, i.e. 2 digits, the first
digit would be dropped)
PERSI command examples

• Configure modulo-N algorithmic verification:
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Attributes
CHANGE-PERSI:TYPE=MODULO,MODULO=1,VALENCE=5-4-3-2-1-1-1-1-1-
1-1-1,TYPESUM=SUMPRO,MODULUS=11,CHKNLEN=1,TYPECHKN=RESTDIV;
• Assign modulo-N algorithm and verification code position to COPIN:
CHANGE-PERSI:TYPE=COPIN,COPIN=5,PINTEST=MODULO1,POSCHKN=5;
• Set length of PIN type PIN2:
CHANGE-PERSI:TYPE=SYS,PIN2LEN=5;
132.14.11 Station Number of Home/Foreign Station

for CDR
You can define whether calls are to be charged to the home station number or the
foreign station.
• Charge calls to foreign station number

CHA-PERSI:TYPE=COPIN,COPIN=number,CDRRMSTN=Y;
The chargee (station number of the home or remote node) is defined using the
CDR AMOs. When the CDRRMSTN parameter is changed to DISPRMSTN, the
display of the other party shows the station number of the remote station instead
of the home node.
132.14.12 PIN/PCODE and Call Transfer (Extension)

A call set up via PIN or PCODE can be transferred to another user. There are two
variants of this feature:
• PIN/PCODE of call initiator is replaced with PIN/PCODE of party to whom the

call is transferred:
CHA-PERSI:TYPE=COPIN,COPIN=number,PINEXT=N;
– The party to whom the call is transferred does identify himself or herself
via PIN. In this case, the call charges for the second stage of the call are
assigned to this party.
– The party to whom the call is transferred does not identify himself or
herself via PIN. In this case, the initiator of the call is assigned the call
charges for the outgoing exchange call. The PIN/PCODE of the initiator
also appears in the call charge record for the second stage of the call,
together with the station number of the party to whom the call was
transferred.
• PIN/PCODE of call initiator is not replaced with PIN/PCODE of party to whom

the call is transferred:
CHA-PERSI:TYPE=COPIN,COPIN=number,PINEXT=Y;
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN Attributes
In this second case, e.g. for PCODEs, the call charges are always assigned
to the call initiator, regardless of whether or not the party to whom the call is
transferred has activated his/her PIN.
132.14.13 Detecting PIN/PCODE Hackers

In order to detect unauthorized users of PINs, the OpenScape 4000 system has
a trace mechanism. The OpenScape 4000 system always assumes unauthorized
use if a user attempts to enter a PIN several times over (hacking). The maximum
number of permitted consecutive mistakes/retries applies to all PIN types. The
station number of the hacker station at which the PIN was attempted is output on
the OpenScape 4000 service terminal, together with the date and time. If a PIN
is already active, the station number of the home station is output. In addition, the
last unauthorized PIN is printed out. This allows you to cancel a PIN if you detect
or suspect unauthorized use within your system or domain. The station at which
the hacker attempted to ’break’ the PIN is not blocked.
• Trace PIN hacker

CHA-PERSI:TYPE=COPIN,COPIN=number,TRACE=Y;
• Define number of mistakes/retries
CHA-PERSI:TYPE=SYS,ATTEMPTS=number;
132.14.14 Deactivation of PIN by pressing Release or

Delete Key
A PIN can be configured to be active for one call only, with deactivation by
pressing the release key or delete key.
• Enable deactivation of PIN via release or delete key

CHA-PERSI:TYPE=COPIN,COPIN=number,DEACKEY=Y;
132.14.15 PIN Valid for Digit Pattern Test

If a user is identified by predialing a PIN, it is not necessary to redial
the code for the digit pattern test.
• PIN type valid for digit pattern test
CHA-PERSI:TYPE=COPIN,COPIN=number,DPTEST=YES;
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
Company Code
132.15 Company Code

In addition to the personal identification number (PINA), the magnetic or chip card
can contain a company code of up to 4 digits. This must be entered in multi-tenant
systems on a company-specific basis. The company code is specific to the ITR
group but can be identical for several ITR groups. 
With AMO PERSI it is possible to individually assign each ITR group a company
code and the pointer (position on the chip card).
• Assigning company code

ADD-PERSI:TYPE=COCO,ITR=number,COCO=string,CPOINT=number;
Remark: In V2.0 and higher, the company code is no longer necessary for smart
cards and is ignored for this card type.
132.16 SMART Transfer Facility between Mailbox and Remote Station

Fixed call forwarding (FWD), e.g. to the voice mail service, can be configured for
a mobile or "floating" (virtual) user (no advance hardware provisioning).
Whenever floating users identify themselves at a "foreign" station (remote
station), they can have incoming calls routed to the station by pressing the call
forwarding (FWD) key. At the same time, any messages already stored in the
user’s mailbox are indicated by the mailbox LED. When the user deactivates the
FWD, the foreign station reverts to its former operating state and the floating
user’s fixed call forwarding to the voice mail service is active again.
This function is possible for "floating" users and for "normal" users (COSSU value
CFSWF must be assigned to user’s COS).
132.17 PIN/PCODE for Voice and Non-Voice

The PIN/PCODE can only be entered on a voice device (Digite/Anate). It is also
active for a non-voice terminal associated with the voice terminal.
132.18 PIN/PCODE in the Network

For call data recording purposes, the PIN is transported within the network from
the station at which it was entered to the node containing the exchange/CO trunk
circuit. For this purpose a buffer element must be available for each DIU B-
channel (AMO DIMSU: CPDBUF).
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN/PCODE in the Network
132.18.1 Network-Wide PIN Usage

Users in local OpenScape 4000/HiPath 4000 networks (i.e. confined to one
company building/location) are able to use the "network-wide PIN" feature (AMO
FEASU) similarly to the previous system-wide PIN function, for manual PINs and
chip cards. The following data and functions of a user’s "home" station are
available and usable at "foreign" stations in such a network:
• Individual classes-of-service for voice(COS1 / LCRCOS1)
• Internal traffic restrictions group no. (ITRGR)
• Dial plan group no. (DPLNGR)
• Mailbox LED display for voice/fax messages
The range of functions available for the network-wide PIN feature is somewhat
restricted, compared to the standard, internal PIN feature. The following
restrictions apply to PIN usage within the home node and in remote nodes of a
network with network-wide PIN functionality:
• Follow-me function not available for all authorizations of a user’s home station
• DPLN and ITR groups: the group numbers of the user’s home station are
used to access the appropriate lists in the remote node
• No follow-me function for repertory keys and DSS keys of a user’s home
station
• No follow-me function for SNR (redial) destination stored in user’s home

station
• No follow-me function for callback in user’s home station
• No follow-me function for individual speed dialing list in user’s home station
• No follow-me function for central speed dialing list in user’s home station
• No follow-me function for programmed timed reminder calls
• PIN/PCODE verification against PIN/PCODE tables not possible
In cases where the follow-me function is not possible for home station data and
home station memory, the data of the remote station will be used.
The "network-wide PIN" feature is intended for use in local networks (i.e. confined
to one company building/location). In corporate networks distributed over
different sites/locations, some limitations must be expected. The PIN types
(COPIN settings) must be identically defined in all nodes of the network.
In networks with open numbering schemes, users must use the node number of
their home node when identifying themselves in foreign nodes.
The ITR, DPLN, SPD2 and SPDC groups must be set up analogously in all nodes
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
PIN/PCODE in the Network
of the network.
If the LCRCOS groups are not set up identically in all nodes of a network,
outgoing connections may cause blocking of incoming calls to other nodes.
The network-wide PIN feature is intended to save having to set up separate PINs
for the same users in the different nodes of a corporate network.
132.18.1.1 Mobile Users
In the case of mobile users (AMO-PERSI:PINTYPE=MOBILE), the home station

(or virtual home station) stores the number of the foreign station at which the
mobile user last logged in. This information is used to signal incoming calls or
messages to the user’s mailbox at the "foreign" station as well. This parameter
also enables the follow-me functionality for call forwarding from the user’s home
station to the foreign station.
If a mobile user logs in at a new foreign station without deactivating his PIN at the
previous station, the first activation is deleted, i.e. it is only possible for a user’s
PIN to be active at one station at a time.
• Assign a PIN type for mobile users:

CHA-PERSI:TYPE=COPIN,COPIN=number,COTYPE=MOBILE;
132.18.1.2 Configuration Commands for Network-Wide PIN
The following commands are necessary for the network-wide PIN feature.
• Enable feature
CHANGE-FEASU:TYPE=A,CM=PINNW;
• Define number of buffer elements required for network-wide PIN:
Formula: number of PINBUFs = max. no. users times 2
ADD-DIMSU:TYPE=USER,PINBUF=number;
• Assign COT for network-wide PIN usage:
CHANGE-COT:COTNO=number,COTTYPE=COTADD,PAR=PINR;
• When the user number (virtual station) should be sent as E164, then the COT
parameter NPIS must be set:
CHA-COT:COTNO=number,COTTYPE=COTADD,PAR=NPIS;
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
Restart Security of PIN/PCODE
132.18.1.3 Configuration Commands for Follow-Me Function

(with Netw-Wide PIN)
The follow-me function allows calls to be forwarded from the home station to the
remote station at which they have logged on. The following commands are
necessary
• Assign COT for network-wide call forwarding:

CHANGE-COT:COTNO=number,COTTYPE=COTADD,PAR=FWDN;
132.18.2 PIN and Follow-Me in 1 Step

Activating PIN-lang may automatically activate the follow-me function. This
function is automatically deactivated when you deactivate the PIN.
PIN and follow-me 1 step should be configured in the home station’s COS.
CHA-COSSU:TYPE=COS,COS=number,AVCE=CFSWF&PINAFM;
Remark: PIN and follow-me 1 step only work in Digites and for network-wide
PINs. Internal PINs and Anates are not supported.
132.19 Restart Security of PIN/PCODE

Identification by means of a PIN/PCODE is not affected by soft or hard restart or
by a processor changeover (in duplex systems); this does not apply to reloading.
This security function is only required for a PIN/PCODE if the PIN/PCODE is
active for longer than the duration of a call, i.e. for the card as well.
Any class of service changeover between the two COS is also saved.
A31003-H3170-S103-6-7620, 02/2019
pin_en.fm
Restart Security of PIN/PCODE
A31003-H3170-S103-6-7620, 02/2019
pnteanw_en.fm
Feature Description
133 PNT E for Connecting Standardized S0 Telephones

To connect standardized S0 telephones to the UP0E interface of the SLMO, use
the "UP0E to S0" adapter box PNT E. This allows you to operate S0 telephones
on the UP0E interface of the SLMO.
The OpenScape 4000 Administration does not recognize the PNT E. Configure it
like an optiset E telephone, making sure that there is enough DTISO DIMEN
memory.
When you make an OPTIDAT request using AMO SBCSU, you will not find an
PNT E; the PNT E reports as an "optiset E basic".
IMPORTANT: You can connect a maximum of two reporting sources

(Telephones with S0 interfaces that conform to the ITU Recommendation I.430 or
Q920/921).
IMPORTANT: In place of an optiset E telephone as representative for PNT E,

you can also configure an optiPoint 500 (DVCFIG=OPTIP500), which the system
then automatically changes into an optiset E.
IMPORTANT: To supply the S0 telephones without a separate power supply, you

need an additional power supply unit.
A31003-H3170-S103-6-7620, 02/2019
pnteanw_en.fm
PNT E for Connecting Functional Station Devices
133.2 PNT E for Connecting Functional Station Devices
functional
telephone
No 3101
DEE
No 3101 S0 UP0/E S
PNT E L
see * M
Fax
PS O
* You can configure another NV service of your choice under the calling number 3101.
To do this, you must specify the service (DTE, FAX) in the DVCFIG parameter, a type of
protocol in the parameter F/DPROT, and an option index in the parameter F/DOPTIDX.
• Configure optiset E telephone as a representative for PNT E:

ADD-
SBCSU:SSTNO=3100,OPT=OPTI,CONN=DIR,PEN=number,DVCFIG=OPTISET,
COS1=number,COS2=number,LCOSV1=number,LCOSV2=number,LCOSD1=nu
mber,LCOSD2=number;
IMPORTANT: Physically, there is no system telephone with the number

3100.
• Configure functional station devices:

ADD-
SBCSU:SSTNO=3101,OPT=OPTIEXP,MAINO=3100,DVCFIG=SET600[&DTE/
FAX],SPROT=param,SOPTIDX=number[,FPROT=param][,FOPTIDX=number
][,DPROT=param][,DOPTIDX=number];
A31003-H3170-S103-6-7620, 02/2019
pnteanw_en.fm
PNT E for Connecting Functional NV Station Devices
133.3 PNT E for Connecting Functional NV Station Devices
Fax
RNR 3100 S
S0 UP0/E
PNT E
L
ee * M
DEE O
You can configure two functional NV station devices under the calling number 3100 with
any service that you want. To do this, you must specify the service (DTE, FAX) in the
DVCFIG parameter, a type of protocol in XPROT, and an option index with the parameter
xOPTIDX (see parameter specifications in the optional brackets).
• Configure optiset E telephone (as representative for PNT E) and functional

NV services:
ADD-
SBCSU:SSTNO=3100,OPT=OPTI,CONN=DIR,PEN=number,DVCFIG=OPTISET[
&DTE]&[FAX],COS1=number,COS2=number,LCOSV1=number,LCOSV2=numb
er,LCOSD1=number,LCOSD2=number[,DPROT=param][,FPROT=param][,D
OPTIDX=number][,FOPTIDX=number];
IMPORTANT: You cannot configure a functional voice device on this port

(not even with MSN).
A31003-H3170-S103-6-7620, 02/2019
pnteanw_en.fm
PNT E for Connecting Video Conference Equipment With Two Calling Numbers
133.4 PNT E for Connecting Video Conference Equipment With Two Calling
Numbers
S0
S
UP0/E L
PNT E M
O
No. 3100
No. 3101
IMPORTANT: Configure the two B channels for the video conference equipment
as functional DTEs under the calling numbers 3100 and 3101. You must
configure the second calling number with MSN.
• Configure an optiset E telephone (as a representative for PNT E) with

functional DTE as follows:
ADD-
SBCSU:SSTNO=3100,OPT=OPTI,CONN=DIR,PEN=number,DVCFIG=OPTISET&
DTE,COS1=number,COS2=number,LCOSV1=number,LCOSV2=number,LCOSD
1=number,LCOSD2=number,DPROT=param,DOPTIDX=number;
• Configure the second calling number for the video conference using MSN as
follows:
ADD-SBCSU:SSTNO=3101,OPT=MSN,MAINO=3100;
A31003-H3170-S103-6-7620, 02/2019
pnteanw_en.fm
PNT E With Channel Bundling for NV Station Device
133.5 PNT E With Channel Bundling for NV Station Device
No. 3100 S
UP0/E L
PNT E
M
O
S0
No. 3101
IMPORTANT: To avoid reserving a B channel for voice, you must configure the
PNT E with OPTISET and another calling number with OPTIEXP (No. 3100 is
thus a service number for PNT E configuration).
• Configure an optiset E telephone (as the representative for PNT E) as follows:

ADD-
SBCSU:SSTNO=3100,OPT=OPTI,CONN=DIR,PEN=number,DVCFIG=OPTISET,
COS1=number,COS2=number,LCOSV1=number,LCOSV2=number,LCOSD1=nu
mber,LCOSD2=number;
• Configure the calling number 3101 for channel bundling as follows (for
example, for all services):
(Set MULTRA in the COS to be able to use both B channels under one calling
number)
ADD-
SBCSU:SSTNO=3101,OPT=OPTIEXP,MAINO=3100,DVCFIG=SET600&DTE&FAX
,COS1=number,COS2=number,LCOSV1=number,LCOSV2=number,LCOSD1=n
umber,LCOSD2=number,SPROT=SBDSS1,FPROT=SBDSS1,DPROT=SBDSS1,RC
BKB=NO,RCBKNA=NO,SOPTIDX=10,FOPTIDX=10,DOPTIDX=10;
A31003-H3170-S103-6-7620, 02/2019
pnteanw_en.fm
PNT E With Channel Bundling for NV Station Device
A31003-H3170-S103-6-7620, 02/2019
pubaddr_en.fm
Feature Description
134 Public Address System

This feature (also called Voice Paging) allows the customer to have dialing
access to a public address system. The customer provides the loudspeaker voice
paging equipment, which can be connected to the OpenScape 4000 several
ways:
• Analog circuits on a SLMA
• Analog circuits on a TMOM (not available for customers in the United States)
• Analog circuits on TIE or CO trunk
134.2 User interface
134.2.1 SLMA Access

The customer dials the access number for the voice paging circuit and is
automatically connected.
The voice paging circuit can be dialed from basic call or consultation dial states.
However, depending on the method of configuration (refer to Section 134.4.1 on

page 134-1360), most features may not be permitted when connected to voice
paging equipment. For example, the following features may NOT be permitted.
This is new for OpenScape 4000.
• conference
• transfer
• call forward to voice page destination
• toggle
• park
• any type of hold
• callback
• message waiting
• override
• camp-on
A31003-H3170-S103-6-7620, 02/2019
pubaddr_en.fm
Service information
134.2.2 TMOM Access

• Interface for the connection of a public address system with amplifier with one
or more loudspeakers.
• An announcement over the public address system can be activated using the
standard procedure.
– It can also be seized in consultation status.
– The announcement over the public address system can be ended by

releasing the connection to the calling station.
• A maximum of 100% of users can be authorized to make announcements

over the public address system. Users are given the appropriate class-of-
service with the aid of administration and maintenance.
• The voice paging system can be seized by
– internal station users,
– the attendant console if the public address system is not connected via
TMOM
– station users of the remote PABX via a station line.
134.2.3 TIE or CO trunk Access

It is possible to connect voice paging equipment to the OpenScape 4000 via TIE
or CO trunk boards (e.g. TMC16 or TMEMUS). The trunks are configured in the
normal way (independent of voice paging). However, the OpenScape 4000 in this
case will be unaware that the trunks are connected to special equipment, and will
therefore be unable to block the activation of features.

Voice Paging via the TMOM board is not possible for customers in the United
States, since this board is not available in the United States.
134.4.1 SLMA Access

• Configure the SLMA2 board:
A31003-H3170-S103-6-7620, 02/2019
pubaddr_en.fm
ADD-BCSU:MTYPE=PER,LTG=ltg,LTU=ltu,SLOT=slot,PARTNO=partno;
If features are to be blocked (new for OpenScape 4000):

• Assign the voice paging device (only significant parameters for voice paging
are shown - other parameters such as COS1, etc. must also be given a
value):
ADD-
SCSU:STNO=number,DVCFIG=ANATE,SPEC=VCEPAGE&SUFDIAL,DIAL=DTMF;
If features are not to be blocked:

• Assign the voice paging device (only significant parameters for voice paging
are shown - other parameters such as COS1, etc. must also be given a
value):
ADD-
SCSU:STNO=number,DVCFIG=ANATE,SPEC=SSTN&SUFDIAL,DIAL=DTMF;
134.4.2 TMOM Access

One circuit is configured on the TMOM module per public address system.

• Assign code for public address system
AD-WABE:CD=key-num,DAR=RA;
AD-COT:PAR=NTON;
• Assign the class of parameter
AD-COP:PAR=SACK&LSUP;
• Add trunk group
AD-BUEND:NO=number;
AD-
TSCSU:COTNO=number,TGRP=number,DEV=SPKR,COPNO=number,SUPV=SUP
V2,ACKT=SZACK2;
• Assign a route to the public address system
134.4.3 TIE or CO Trunk Access

No special configuration other than the usual trunk and routing assignments.
A31003-H3170-S103-6-7620, 02/2019
pubaddr_en.fm
Relevant AMOs
134.5 Relevant AMOs

The below AMO parameter is new for OpenScape 4000.

Language
SCSU SOND d The values LPSE and NAWA ARE needed for
voice paging
SCSU SPEC e The values VCEPAGE and SUFDIAL are needed
for voice paging
A31003-H3170-S103-6-7620, 02/2019
redial_en.fm
Redial
Saved Number Recall
135 Redial
135.1 Saved Number Recall

Each user (STN) as well as each attendant terminal (ATND) can store a dialled
number of up to 22 digits for redialling at a later time. 
This function also includes a ’notebook function’, i.e. a number can be entered
and stored during a call. When the database is regenerated the stored redial
number is saved. For analog stations a code digit must be defined for the ’*’ and
’#’ keys.
135.1.1 Generation
• Release feature
CHA-FEASU:TYPE=A,CM=SNR;
• Assign the key for saved number redial to a subscriber:
CHANGE-TAPRO:STNO=number,KYxx=SNR
• Assign the code for saved number redial
AD-WABE:CD=key-num,DAR=SNR;
135.2 Last Number Redialing

Another kind of number redial is that of redialling the last dialled station number.
This station number is automatically stored and cannot be changed by the user.
To redial the last dialled number requires a special key or a code.
135.2.1 Generation
• Release feature for Last number Redialing:
This feature is activated either by a LAST-NUMBER-REDIAL key on DIGITE
or by dialling the LNR code with ANATE.
CHA-ZAND:TYPE=ALLDATA2,LNR=YES;
• Assign the key for last number redial:
CHANGE-TAPRO:STNO=number,KYxx=LNR;
• Configure the code for number redial of the last dialled number:
ADD-WABE:CD=key-num,DAR=LNR;
A31003-H3170-S103-6-7620, 02/2019
redial_en.fm
Redial
Last Number Redialing
A31003-H3170-S103-6-7620, 02/2019
repeat_id_key_en.fm
Repeat ID Key
Feature Description
136 Repeat ID Key

The repeat ID feature allows the user to see the calling/called party information
presented again to the display after it has timed out.
000441159433266
Repeat ID

The Repeat ID key is an optional feature key that can be assigned to any Keyset
or Digite with a display. The station user can depress this key while in talk state
to display calling and/or called party information.

Activation Sequences
Repeat ID of a connection the user is active on
• If TALK or CONFERENCE -
Press REPEAT ID Key:
– In case of keyset on the first line of display the partner ID is shown (called/
connected/calling party) and on the second line of display the used line
ID is shown.
– In case of non keyset, on the first line of display the partner ID is shown
(called/connected/calling party) and on the second line the own number
is shown.
A31003-H3170-S103-6-7620, 02/2019
repeat_id_key_en.fm
Repeat ID Key
Service Information
Deactivation Sequences
• Time-out: There is a 8 second display timeout (administrable) for Repeat ID
• The display given upon initiation of Repeat ID may be overwritten by other

user requested or features at the user’s telephone.
• Upon initialization or re-initialization of the telephone.

The Repeat ID feature is intended for the global marketplace.

• To add a Repeat I.D. Key to a station
CHANGE-TAPRO:STNO=7445,DIGTYP=OPTIT19,KY18=RPTID;
• To vary the timer for the display of the I.D.
CHANGE-DTIM1:TYPEDH=DIGITE,CTPRESEL=20;
Note: This timer also has the function of determining the preselection time for
manual line selection with Keysets
136.5 Relevant AMOs

TAPRO TDnn d
KYnn e The new key (nn) is called RPTID
DTIM1 KDPRESEL d
CTPRESEL e Parameter is used to set the RPTID display
duration
A31003-H3170-S103-6-7620, 02/2019
s2tln_en.fm
S2 Station Configuration
Feature Description
137 S2 Station Configuration

Servers, routers, MCU and similar equipment can be connected to OpenScape
4000 as a tie line or station. From the point of view of the protocol it is better to
install these stations with SBCSU because in this case OpenScape 4000 offers
the network part of the protocol and the terminal provides the user part. With tie
line signaling differences frequently occur in the protocol if the terminal has not
actually implemented the protocol for it. 
If more than one extension number is needed for the connection these are
provided with MSN.

• There is no permanent allocation of extension numbers to B channels.
• The CRC4 test is activated and deactivated with the parameter QUAL (AMO
LWPAR).
• In a configuration with another device, the OpenScape 4000 should be set as

master for clocking and layer 2 (AMO LWPAR).
• This is a point-to-point connection, in other words there is only one terminal

connected to the port.
• If you do not use MSNs but still want to be able to reach the connected device
several times using the primary station number, set the parameter MULTRA
in the associated COS for the relevant primary station number service.

To be able to configure an S2 station, a corresponding board must be configured
and free in the system (with S2 port). In addition, the appropriate number of
station numbers must be entered in the DPLN.
Below is an example of a connection in the form of a station with 30 MSN
numbers.
• Set up an S2 primary station number (3581):

ADD-SBCSU:STNO=3581,OPT=FPP,CONN=DIR,PEN=1-5-37-0,
DVCFIG=S2PP,COS1=23,COS2=23,LCOSV1=1,LCOSV2=1,LCOSD1=1,LCOSD2
=1,
PROT=SBDSS1,PERMACT=Y,OPTIDX=10;
A31003-H3170-S103-6-7620, 02/2019
s2tln_en.fm
S2 Station Configuration
Relevant AMOs
• Set an MSN as the primary station number (if multiple numbers are needed
for S2):
ADD-SBCSU:STNO=3600&&3629,OPT=MSN,MAINO=3581,COS1=23,COS2=23,
LCOSV1=1,LCOSV2=1,LCOSD1=1,LCOSD2=1;
137.4 Relevant AMOs

Language
SBCSU ART d ANGABE DES BUSTYPS ODER DER ZU
ERWEITERNDEN EINHEIT
(ART=FPP HAUPTRUFNUMMER DES S0-
/S2-PUNKT-PUNKT-ANSCHLUSS
ART=MSN MSN-RUFNUMMER )
OPT e SPECIFICATION OF BUS TYPE OR UNIT
TO BE
EXPANDED
(OPT=FPP FUNCTIONAL POINT-TO-
POINT
CONNECTION
OPT=MSN MSN STATION NUMBER)
ANSCHL d ANSCHLUSS-ART DER GERAETE
(ANSCHL=DIR DIREKTER ANSCHLUSS)
CONN e DEVICE CONNECTION TYPE
(CONN=DIR DIRECT CONNECTION)
GERKON d GERAETE-KONSTELLATION EINES
TEILNEHMERS
(GERKON=S2PP S2-PUNKT-PUNKT-
ANSCHLUSS,
30 B-KANAELE)
DVCFIG e DEVICE CONFIGURATION
(DVCFIG=S2PP S2 POINT-TO-POINT)
OPT d INDEX AUF OPTIONSTABELLE
(OPT=9 Optionsindex S2 Endgeräte, für alle
funktionalen Protokolle)
OPTIDX e INDEX INTO OPTION TABLE
(OPT=9 Optionindex S2 TE)
PROT d PROTOKOLLVARIANTE
PROT e PROTOCOL VARIANT
TLNNU d TEILNEHMER-RUFNUMMER
STNO e STATION NUMBER
HAUPTNU d HAUPT-RUFNUMMER
MAINO e PRIMARY STATION NUMBER
A31003-H3170-S103-6-7620, 02/2019
smartcard_appl_en.fm
Feature Description
138 Smart Card Application

You can connect a signature module (Smart Card Reader) to an optiPoint 500/
600 telephone (Up0E interface) as well as to an optiPoint 410/600 HFA IP phone.
S erver
optiP oint 500 (C A P /C A 4000)
S m art O ther
C ard S ignature optiP oint 400 H F A S m artC ard Access
M odule optiP oint 600 H F A H iP ath 4000 A p p licatio n S C A A A pplications
(S C )
A C L-C link
IS O
7816-4 C orN et-T S C orN et-T S A C L-C LA N
A smart card can be inserted into a signature module and is authenticated by the
SmartCard Access Application (SCAA) that runs on a server connected to the
OpenScape 4000 over the CAP/CA4000. Once authenticated by the SmartCard
Access Application (SCAA), you can access any applications that communicate
with the SCAA application on the server.
The Smart Card Application:
• supports smart cards that comply with the standard ISO 7816, parts 1-4.
• supports the Local Security Check Procedure which requires users to

enter an ID over the telephone’s keypad and display to prove their identity
as card owner.
• provides a connection over OpenScape 4000 between the signature

module and the SmartCard Access Application (SCAA) on the server to
record smart card insertion and removal, control the Local Security Check
Procedure (LSCP), perform authentication and provide user guidance for
using the smart card with the SmartCard Access Application (SCAA).
• supports the AMU - Mobile Station application for activating the

OpenScape 4000 PIN.
A31003-H3170-S103-6-7620, 02/2019
User Interface

The smart card can be inserted or removed in any telephone state (free, busy,
etc.).
You can manipulate the user interface to identify a user on the basis of a smart
card (Local Security Check Procedure) and card ID with the help of the
SmartCard Access Application (SCAA).
The SmartCard Access Application (SCAA) switches the telephone to non-voice

state (the non-voice LED lights up) to let you manipulate the display.
The smart card ID digits entered are not shown on the display. The end-of-dialing
criterion (end-of-dialing code, such as, "#" or number of ID digits) can be set in
the SmartCard Access Application (SCAA).
Following successful authentication, the SmartCard Access Application (SCAA)

starts up an application on the server that in turn activates the "mobile station"
feature for the user that used the smart card for identification and authentication.
In contrast to Optiset E chip cards, you no longer need to enter a station number
for smart cards.
Once a smart card is inserted and the "mobile station" feature is successfully
activated, the privileges and properties (membership of DPLN groups, ITR
groups, etc.) associated with the smart card user can be used for the next call or
station activities. This also applies if you insert a smart card during a connection
that was established with another smart card or "Manual PIN".

Remark:
This feature description does not include a description of the Smart Card Access
Application (SCAA).

Enabling the SmartCard Feature in the System
CHA-FEASU:TYPE=A,CM=SMARTCRD;
If the DP Application SCAA (here applno=61) Already Exists:

To add a SmartCard Access Application link, enter:
CHA-XAPPL:CTYPE=APPL,APPLNO=61,SECAPPL=111;
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
If the DP Application SCAA Does Not Yet Exist

To configure a DP application and SmartCard Access Application link, enter (in
the case of 
dpappl, you must specify the application name used in the AMO CPTP - here,
for example, "SCAA"):
ADD-
XAPPL:APPLNO=61,DPAPPL="SCAA",NAME="APPLICATION22",SECAPPL=11
1;
NOTE: You can use the parameter secappl to configure up to 20 SmartCard

Access Application links.
If the Station Already Exists:

• To configure the signature module (SmartCard Reader)
afterwards at the station, enter:
CHA-SBCSU:STNO=3456,IDCR=Y;
• To assign a SmartCard Access Application link to the station, enter:
CHA-SBCSU:STNO=3456,SECAPPL=111;
• To set "Mobile User Activation over SCAA/AMU" at the station, enter:
CHA-SBCSU:STNO=3456,APMOBUSR=Y;
• or to combine all steps:
CHA-SBCSU:STNO=3456,IDCR=Y,APMOBUSR=Y,SECAPPL=111;
If a Station Does Not Yet Exist:

ADD-
SBCSU:STNO=3456,OPT=OPTI,...,IDCR=Y,APMOBUSR=Y,SECAPPL=111;
138.5 Relevant AMOs

Language
FEASU smartcrd d Leistungsmerkmal SmartCard im System
freischalten
FEASU smartcrd e Activate SmartCard feature usage system wide
SBCSU secappl d SmartCard Access Application Link zuweisen
SBCSU secappl e Assign SmartCard Access Application Link
SBCSU apmobusr d Aktivierung Mobile User über SCAA/AMU
SBCSU apmobusr e Mobile User Activation via SCAA/AMU
XAPPL secappl d SmartCard Access Application Link einrichten
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

Language
XAPPL secappl e Create SmartCard Access Application Link
A31003-H3170-S103-6-7620, 02/2019
speaker_call_one_way_en.fm
Overview
139 Speaker Call - One-Way
139.1 Overview
The feature „Speaker Call - One Way“ is the migration from the U.S. speaker
function and the I.M. voice call function.
Speaker call to a
specified station
Taxi in reception for

your guest
The Loudspeakers is turned on at a specific

Reception station.
Stn 7445 If handset is lifted a 2 way conversation is entered
into

The feature „Speaker Call - One Way“ provides the capability to allow an analog
telephone, digital feature telephone (DFT), or Keyset user to initiate a speaker
call which provides a one-way connection to a single destination (prime line) of
their choice.
Upon the destination lifting the handset, the call is converted to a normal two-way
call.

• The user may either depress a key (SPKRCALL) or dial an access code
(SPKRCALL), followed by dialing a destination extension number, to initiate
a „Speaker Call - One-Way“ call. A one-way connection shall immediately be
established between the user and the dialed destination, if the following
criteria are met:
• The destination is not busy, not off-hook, not in hands-free operation, and
is not in program mode.
A31003-H3170-S103-6-7620, 02/2019
Service Information
• The destination is not marked for voice call protection.
• The station is not restricted from terminating to that destination (e.g. ITR
Internal Traffic Restriction).
• An external dial tone shall alert the originator that the one-way connection has
been established, and that the one-way call can begin.
• The one-way connection shall be converted to a single two-way connection

upon the destination’s going off hook, via the handset only.
• A „Speaker Call - One way“ call can be initiated by an analog or digital

telephone.
• When the destination party presses the speaker key, the call will be
disconnected.
• When the destination party presses a line key (either the one on which the
call is pending, or any other line key), the call will be disconnected.

The „Speaker Call - One Way“ feature is intended for the global marketplace.

How to add the „Speaker Call - One Way“ feature into the system:
• How to configure the originating station to have access to the feature:

CHA-SDAT:STNO=7445,TYPE=ATTRIBUT,AATTR=SPKRCALL;
ADD-WABE:CD=*54,DAR=SPKRCALL;
CHA-TAPRO:STNO=7445,KY04=SPKRCALL;
139.6 Relevant AMOs

SDAT SPKRCALL d direktansprechen simplex
SPKRCALL e speaker call - one way
TAPRO SPKRCALL d direktansprechen simplex
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

WABE SPKRCALL d direktansprechen simplex
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
special_ring_tone_en.fm
140 Special Ring Tone depending on Caller

For certain types of call, a special ring can be signalled at the called terminal
(triple cadence). This is possible for internal calls and consultation calls within the
same node.
• The calling party must be assigned either an off-hook recall classmark in the
COS
CHA-COSSU:TYPE=COS,COS=number,AVCE=OFHKRC;
or an off-hook recall attribute in SDAT
CHA-SDAT: STNO=number,TYPE=ATTRIBUTE,AATTR=OFHKRC;
• The calling party must also not have any HOTIDX assigned. Check as
follows:
DIS-SDAT:STNO=number,TYPE=SUBDATA;
• The special ring type is set with the AMO ZAND.
CHA-ZAND:TYPE=RNGTYPE,PRI=TRPR;
Instead of TRPR, a different special ring may be assigned (see parameter
values for PRI in AMO description of AMO ZAND).
A31003-H3170-S103-6-7620, 02/2019
special_ring_tone_en.fm
A31003-H3170-S103-6-7620, 02/2019
spedial_en.fm
Speed Dialling
Speed dialing, individual
141 Speed Dialling
141.1 Speed dialing, individual
141.1.1 Overview
This feature permits individual storing of a maximum of 10, 20, or 30 arbitrary digit
sequences, each comprising up to 22 digits, at any ANATE or DIGITE, but not at
the attendant terminal.
Destinations are stored in a memory which is set up with the AMOs SCSU/
SBCSU/SSCSU, by declaring parameter SPDI=0, 10, 20, or 30 when the port is
assigned (action ADD) or the number of SPDI is increased/decreased for an
existing port (action CHANGE).
Destinations are entered either at the service terminal with the ZIEL AMO or at
the user’s telephone by means of a dialing procedure.
141.1.2 Generation
• Add an SPDI destination
AD-ZIEL:TYPE=SPDI,SRCNO=number,SPDNO=number,DESTNOR=number;
• Add an SPDI key
CHA-TAPRO:STNO=number, KYxx=SPDI;
141.2 Speed Dialing, Central (SPDC)

The SPDC is conceived for up to 10000 destinations that can be distributed as
desired among a maximum of 16 speed dialing lists. Each list can continue a
maximum of 1000 destinations. Each terminal/port can be allocated up to 2 lists
with the AMO SCSU, SBCSU, or SSCSU. These are lists 0 to 15.
If only one speed dialing access code is assigned in the dial plan (only
DAR=SPDC1 is assigned by AMO WABE), the speed dialing indexes assigned in
the first list of any terminal/port should not overlap the indexes assigned in the
second list of the same terminal/port. The lowest index in the second list should
be a higher number than the highest index assigned in the first list. The number
of digits of the indexes of the first and second list have to be the same. These
prerequisites (no overlapping, correct order of indices of the first and second list)
are not checked by any AMO, but have to be assured by the service personnel.
Users can access up to 1000 speed-dialing numbers. If there are overlapping
indexes, the indexes of the first list cover the indexes of the second list. Despite
A31003-H3170-S103-6-7620, 02/2019
spedial_en.fm
Speed Dialling
Extended functions for central speed dialing
the fact that the covered indexes of the second list cannot be accessed via
access code (DAR=SPDC1) they can be accessed via speed dialing keys,
however.
If two speed dialing codes are assigned in the dial plan (DAR=SPDC1 and
DAR=SPDC2 are assigned by AMO WABE), the speed dialing indexes can be
assigned more than once. Users can access up to 2000 speed dialing numbers.
Speed dialing destinations can have up to 22 digits; any digit sequence can be
entered. Special characters, i.e. asterisk and hash, are also allowed as part of the
destination number. For automatic suffix dialing it is possible to specify the
number of digits that have to be transmitted with a delay, e.g.: unabbreviated call
number 0897220 SUPDIAL=1 will dial 089722 immediately and the last 0 only if
no suffix dialing followed the SPDI dialing.
• Create a central speed dialing list

AD-LRNGZ:LST=number,SPDMIN=number,SPDMAX=number;
• Assign a destination to an SPDC list (existing destination is overwritten)
AD-ZRNGZ:LST=number,SPDNO=number,DESTNO=number;
• Assign central speed dialing keys
CHA-TAPRO:STNO=number,KYxx=SYSSP1,KYxx=SYSSP2;
141.3 Extended functions for central speed dialing

Two alternative, customer-specific features for central speed dialing can be
activated: namely 4-digit or 5-digit central speed dialing. The only change
involves activation with the AMO ZAND.
The 5-digit version allows the first two dialed digits to be converted to an index to
one of the 16 central speed dialing lists with the aid of a conversion table. This
permits a speed dialing facility to be set up, for example, in which a 5-digit
customer number is used to represent the customer’s unabbreviated call number.
The conversion table must be patched on a customer-specific basis (refer to

section “Entering the customer-specific data for the 5-digit speed dialing facility”).
141.3.1 4-digit speed dialing facility

The abbreviated call number which is dialed must have 4 digits, of which the first
determines the central speed dialing list. This must be reflected by the
organization of these lists.
Example: The code for seizing the central speed dialing facility (*1) must be
dialed, followed by the abbreviated call number (2357).
A31003-H3170-S103-6-7620, 02/2019
spedial_en.fm
Speed Dialling
*1 2 357
Code no. SPDC group 0 (SPDC1)
CSD list 2
Abb. call no. 357 in list 2
Figure 115 Example for the 4-digit speed dialing facility
1. Enable system with 4-digit speed dialing facility:

CHANGE-ZAND:TYPE=ALLDATA2,CSDZTYPE=4DIG;
2. All stations wishing to use the 4-digit speed dialing facility must have entered
group 0 under SPDC1 (e.g. AMO SCSU).
3. Digit analysis results SPDC1 and SPDC2 must have been created in the digit
analysis (AMO WABE).
4. Central speed dialing lists 0 to 9 must have been created with the AMO
LRNGZ. The first abbreviated call number in each list is 000, max. 1000
entries.
IMPORTANT: Lists 0 to 9 must still be created if fewer than 10 lists are used,
as otherwise the system will fail if the station dials a wrong number. The
reason for this is that when a speed dialing list is dialed, the system always
assumes that it actually exists. Any lists which are not required can remain
empty, however.
5. Lists 1 - 16 can be assigned to speed dialing groups 1 - 16 if necessary. The

lists are allowed to overlap, i.e. even if they are already being used for the 4-
digit central speed dialing facility, lists 1 - 9 can still be used for speed dialing
groups 1 - 9. Only a 3-digit number is dialed by these groups, however!
6. Activating/deactivating the 4-digit speed dialing facility

The various features of the central speed dialing facility are switched on or off
with the AMO ZAND. The normal speed dialing facility is activated in the initial
state.
In the branch TYPE = ALLDATA2 of the action ’CHANGE’ the parameter
CSDTYPE=4DIG must be set to activate the 4-digit CSD. The standard CSD
is available with CSDTYPE=STANDARD.
A31003-H3170-S103-6-7620, 02/2019
spedial_en.fm
Speed Dialling
141.3.2 5-digit speed dialing facility

The abbreviated call number which is dialed must have 5 digits, of which the first
two are converted to a valid speed dialing list number with the aid of a conversion
table. This table contains 100 entries, which means that the range of converted
index numbers extends from 00 to 99. The basic initialization includes a NULL
value, so that any digits which are dialed incorrectly by the station do not result in
an addressing error. The basic initialization is activated with a DB routine during
the generation procedure.
Example: The code for seizing the central speed dialing facility (*1) must be
dialed, followed by the abbreviated call number (19357).
*1 19 357
Abb. call no. 357 in speed dialing list
Index no. in conversion table
Code no. CSD group 0 (SPDC1)
DB_S_AM_CSD_TRANSL_TBL
00 List 0
01 Null
CSD list 0 CSD list 5
.. ... ... ...
19 Liste 5 ... ...
20 Liste n ... 357 0897220
.. ... ...
99 Null ...
Figure 116 Example for the 5-digit speed dialing facility
1. All stations wishing to use the 5-digit speed dialing facility must have entered
group 0 under SPDC1 (e.g. AMO SCSU).
2. Digit analysis results SPDC1 and SPDC2 must have been created in the digit
analysis (AMO WABE).
A31003-H3170-S103-6-7620, 02/2019
spedial_en.fm
Speed Dialling
3. The central speed dialing lists to which the conversion table refers must have
been created with the AMO LRNGZ. If no such lists exist, an addressing error
will occur. The first abbreviated call number in each list is 000, in other words
3 digits. The assignment of the speed dialing lists is completely flexible, for
example a list can be referred to by several different index numbers or by all
index numbers.
4. Lists 1 - 16 can be assigned to speed dialing groups 1 - 16 if necessary. The

lists are allowed to overlap, i.e. even if they are already being used for the 5-
digit central speed dialing facility, the lists can still be used for the speed
dialing groups. Only a 3-digit number is dialed by these groups, however!
5. Activating/deactivating the 5-digit speed dialing facility

The various features of the central speed dialing facility are switched on or off
with the AMO ZAND. The normal speed dialing facility is activated in the initial
state.
In the branch TYPE = ALLDATA2 of the action ’CHANGE’ the parameter
CSDTYPE=5DIG must be set to activate the 5-digit CSD. The standard CSD
is available with CSDTYPE=STANDARD.
Entering the customer-specific data for the 5-digit speed dialing facility
The customer-specific data, i.e. the assignment of the 2-digit index to a reference
to one of the speed dialing lists which has been created, is defined after (!) the
system has been generated in the DB_S_AM_CSD_TRANSL_TBL. This table
was initialized with NULL values during the generation procedure, so that there
are no indices which refer to a speed dialing list.
With the AMO DEBUG the SD list for the TABLE INDEX can then be entered at
a certain address (see following Table 65).
Address Speed dial list Table index

(derived from
DB_S_AM_CSD_TRANSL_TBL)
HiPath 4000 V6 OpenScape 4000 V7
4F20:36AE 4F20:7876 0...15, 32 00
4F20:36AF 4F20:7877 0...15, 32 01
4F20:36B0 4F20:7878 0...15, 32 02
4F20:36B1 4F20:7879 0...15, 32 03
4F20:36B2 4F20:787A 0...15, 32 04
4F20:36E7 4F20:78AF 0...15, 32 57

4F20:36E8 4F20:78B0 0...15, 32 58
4F20:36E9 4F20:78B1 0...15, 32 59
4F20:36EA 4F20:78B2 0...15, 32 60
Table 65 5-digit speed dialing facitlity - Debug address for index table
A31003-H3170-S103-6-7620, 02/2019
spedial_en.fm
Speed Dialling
Relevant AMOs
Address Speed dial list Table index

(derived from
DB_S_AM_CSD_TRANSL_TBL)
HiPath 4000 V6 OpenScape 4000 V7
4F20:36EB 4F20:78B3 0...15, 32 61
4F20:370D 4F20:78D5 0...15, 32 95

4F20:370E 4F20:78D6 0...15, 32 96
4F20:370F 4F20:78D7 0...15, 32 97
4F20:3710 4F20:78D8 0...15, 32 98
4F20:3711 4F20:78D9 0...15, 32 99
Table 65 5-digit speed dialing facitlity - Debug address for index table
Example:
The abbreviated call number 58123 must be created. The unabbreviated call
number has been created as SPDNO=123 in speed dialing list 2 using the AMO
ZRNGZ. The value 2 must now be entered at index 58 with AMO DEBUG.
"SET 4EF0:BB7C(1)=T’02!";
If an entry needs to be deleted again, the value 32 must be entered at the

appropriate address.
IMPORTANT: A reference in the conversion table to a non-existent speed dialing

list will cause the system to crash!
The addresses of DB_S_AM_CSD_TRANSL_TBL are different in the
OpenScape 4000/HiPath 4000 variants. Using a wrong address may cause the
system to crash!
141.4 Relevant AMOs

Language
SBCSU/ RNGI d rufnummerngeber individuell (0, 10 ,20 ,30)
SCSU/
SSCSU
SPDI e station with speed calling individual (0, 10 ,20 ,30)
TAPRO SYSSP1 d kurzwahl zentral 1
SYSSP1 e system speed key # 1
SYSSP2 d kurzwahl zentral 2
SYSSP2 e system speed key # 2
A31003-H3170-S103-6-7620, 02/2019
spedial_en.fm
Speed Dialling
Relevant AMOs

Language
SPDI d kurzwahl individuell
SPDI e speed dial (station speed) key
ZAND RNGZTYP d 5ZIFF= Kundenindiv.RNGZ mit
Umwandlungstabelle
CSDTYPE e 5DIG= Customer individual CSD with translation
table
A31003-H3170-S103-6-7620, 02/2019
spedial_en.fm
Speed Dialling
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
142 Stations
Use the following AMOs to enter data for stations:
AMO SCSU
• Add ports for ANATEs, ANATECM, as well as, ANATE/FAX, ANATE/
DTEANA.
• Add the auxiliary Digite AUXDIGI for "Trading Classic" and "ViNet" (DIGI260
was used for this before OpenScape 4000 was released)
• You can add users without terminals, known as dummy users/stations or ID-
card users. These are configured in the same way as normal terminals
connected to a line module but are not assigned a PEN. The SCSU
parameter INS=FLOAT must be set for these users.
ID-card users can telephone from any station that has a card reader, using
the class-of-service and the station number assigned to the ID card.
• The ACL support station is a special type of dummy station (INS=ACLSTN)

that is configured in the system like an ID-card user. If this ACL support
station is configured as a Digite (AUXDIGI), it goes into operation as soon as
it is added (DC state ’Ready’), even if there is no terminal connected. These
support stations are often also referred to as ’phantoms’ (particularly in the
U.S.). A ’phantom’ can only be deleted if is not processing any calls.
When the data is interrogated, group assignments are also displayed, such
as, hunt groups, call pickup groups and night switch systems in which the
terminal is incorporated.
A terminal is normally put into operation immediately when the data is added.
This is done by setting the parameter INS=NO.
Device configuration data cannot be changed with the AMO SCSU
(parameter DEVCFIG). In order to change configuration data, you must
delete the old configuration and add a complete, new configuration. The
circuit can be disabled beforehand and enabled again afterwards with the
AMO DSSU. You can also use the AMO SCSU’s delete command to disable
circuits (OFFTYPE=DC=default value, that is, with camp-on (soft lock) or
OFFTYPE=DI, without camp-on (hard lock)).
You can also add station data in "signed off" status (ANATE only). To do this,
you must specify the SCSU parameter INS=SIGNOFF and assign no PEN
(the PEN parameter is otherwise ignored), see "Autoset Relocate
Applications" chapter.
Stations for users who do not wish their number to be displayed at a called
DIGITE must be configured with the parameter SSTNO (secret station
number). Two versions of call number suppression can also be set
specifically for external calls: The parameter SSTNO=ONLYEXT suppresses
external call number display and replaces the call number with a substitute
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
number set with the AMO KNMAT. The parameter SSTNO=ONLYEX0

suppresses external call number display.
For more information, see the "Display Suppression" chapter.
AMO SBCSU
• Assign terminals for the S0 bus, S0/S2 interface or the UP0/E interface. You
can configure set 600 terminals (Euro ISDN) at the functional bus for VOICE.
For non-voice devices, you can configure the devices for DTE, FAX and S0/
S2 connections to DP, LAN and servers. For more information, see the
"Digital Stations with S0 Interface" chapter.
• Add OPTIIP terminals (IP phones) on the STMI-HFA boards. These are
configured with CONN=IP on the STMI-HFA board and with CONN=IP2 on
the STMI2-HFA board.
AMO SSCSU
• Special configurations, such as "Trading" devices and telecommuting server
connections and extension connections can be configured with the AMO
SSCSU, see the relevant chapter.
AMOs for configuring additional station data

• AMO TAPRO
For each device type key layout standards are stored in the database. The
key standard allocated to the device (SBCSU/ SSCSU, parameter STD) can
be changed with the AMO TAPRO. Individual key layout standards can also
be created.
• AMO TGER
Each voice terminal can be assigned one NON-VOICE device per service
(FAX, DTE) in the incoming direction.
• AMO PERSI
Allocation of names, organizational units and personal identification number
for card reader (PINC), personal identification - manual (PIN1 to PIN15) and
class of service changeover code (COSXCD) for a station number. Several
PINs and several names may be assigned to one station. Service identifiers
(SI) can be configured independently of call numbers. For further information,
please refer to the section "Personal Identification Numbers".
• AMO ZIEL
Assignment of a call forwarding destination, name keys and DSS keys as well
as redial destinations to a station number.
• AMO SDAT
You can administer station-specific attributes and features for the voice
service. General, device-independent data can also be administered.
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
Adding a Station (Example)
142.1 Adding a Station (Example)

• Add a station number as follows:
ADD-WABE:CD=<key-num>,DAR=STN;
• Add a class of service as follows:
ADD-COSSU:AVCE=<param>;
• Add a station as follows:
– ANATE, AUXDIGI with the AMO SCSU:

ADD-
SCSU:STNO=<number>,DVCFIG=<param>,COS1=<number>,COS2...,LC
OSV1=...,LCOSV2=...,LCOSD1=...,LCOSD2=...;
– Add a station at the UP0E port as follows:
ADD-
SBCSU:STNO=<number>,OPT=OPTI,DVCFIG=<param>,COS1=<number>,
COS2=<number>,LCOSV1=...,LCOSV2=...,LCOSD1=...,LCOSD2=...;
– The AMO SSCSU is used for adding special stations
(see AMO description or special applications).
You can select a key layout standard with the parameter STD when adding a
station with the AMO SBCSU/SSCSU (key layout). 
You can modify this key layout later with the AMO TAPRO. You can modify the
key layout separately for each individual station.
• Change the key layout for a special station:

CHA-TAPRO:STNO=number,[KY01=param]...[KY19];
• Each station number can be assigned a name, PIN and organization name,
for example, with:
ADD-PERSI:TYPE=STN,STNO=<number>,NAME=<string>,ORG=<string>,
PIN1=<number>;
142.2 Displaying Station Class of Services

• Display station classes of service (class-of-service numbers for COS1 and
COS2) with:
DIS-SCSU:STNO=<number>;
or
DIS-SBCSU:STNO=<number>;
or
DIS-SSCSU:STNO=<number>;
The classes of service for COS1 and COS2 can then be found in the output.
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
Displaying a Station from a Specific Class of Service
• You can also use the AMO SDAT to display the class of service for random
stations, regardless of the AMO used to configure the station.
DIS-SDAT:STNO=<number>;
• You can display the classes of service (which privileges are configured, for
example, in the classes of service) with:
DIS-COSSU:TYPE=COS,COS=<cos_from_display>;
142.3 Displaying a Station from a Specific Class of Service

When displaying the COS with the AMO SBCSU, you also see the stations that
were assigned this COS with the AMO SCSU. However, the DISPLAY-SCSU
command will only display stations with the specified COS which were actually
configured with this AMO. Use the AMO COSSU to display all stations (including
SSCSU stations) and trunks with a specific class of service.
(Example)
DIS-SCSU:TYPE=COS,COSNO=<number>;
or
DIS-SBCSU:TYPE=SEARCH,COSNO=<number>;
or
DIS-COSSU:TYPE=COS,COS=<number>,FORMAT=REF;
142.4 Displaying Station Features

Display station data:
DIS-SCSU:STNO=<number>;
or
DIS-SBCSU:STNO=<number>;
or
DIS-SSCSU:STNO=<number>;
The output table shows the active features under the heading "Activation
Identifiers for Features".
142.5 Changing a Station’s COS

• Display a station’s COS (1st and/or 2nd COS), and subsequently display all
stations with the same COS.
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
Station Number Changes
DIS-SCSU:STNO=number;
or
DIS-SBCSU:STNO=number;
or
DIS-SSCSU:STNO=number;
or
DIS-COSSU:TYPE=COS,COS=number,FORMAT=REF;
• Station is the only one with this COS -> change COS:
CHA-COSSU:TYPE=COS,COS=number,AVCE=param;
• Several stations have this COS -> station receives new COS:
ADD-COSSU:COPYCOS=number,AVCE=param;
• Assign the new COS to the station:
CHA-SCSU:STNO=number,COS1=number,COS2=number;
or
CHA-SBCSU:STNO=number,COS1=number,COS2=number;
or
CHA-SSCSU:STNO=number,COS1=number,COS2=number;
142.6 Station Number Changes

Once a station has been configured in the system, you can change its call number
without first deleting and reentering it.

• The number under the parameter NEWNO must be applies locally to the STN
DAR in the AMO WABE and must be predefined (free).
• The original number is redefined in the AMO WABE after the call number has
been changed.

Change the station number:
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
Swapping Station Numbers
CHA-SCSU:STNO=<number>,NEWNO=<number>;
or
CHA-SBCSU:STNO=<number>,NEWNO=<number>;
or
CHA-SSCSU:STNO=<number>,NEWNO=<number>;
or
CHA-SDAT:STNO=<number>,TYPE=DATA,NEWNO=<number>;
142.7 Swapping Station Numbers

Station numbers of voice terminal configurations (=telephones) can be swapped
with the aid of the AMO SXSU. 
The parameter STNOX defines the station number which is to be exchanged for
the station number defined by the parameter STNO.
4711 now 4711

now 2233 2233

• Both devices must be supported by the AMO SXSU.
– The station must not be an AGENT, SUPER, CAF or AUTOLOG.
– The station must not be a TEAMSECR or TEAMEXEC, either.
• This DSS destination is deleted at all stations where the STN to be modified
is set as a DSS destination.
• No jumpering changes are necessary.
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
Changing the Station Port Assignment

Exchange station numbers:
CHA-SXSU:STNO=<number_a>,TYPE=STNO,STNOX=<number_b>;
142.8 Changing the Station Port Assignment

ANATEs and an S0 bus or optiset E/optiPoint 500 telephone can be assigned to
a different port with the AMO SXSU (feature and group assignments are not lost).
All other terminal types, such as, individual devices on the S0 bus or optiset E port
must be deleted and then re-assigned (see also following section).
OpenScape 4000
4711 PEN: x
2233 PEN: y
IMPORTANT: The PEN can only be modified with the AMO SXSU within a
physical node.
• After changing the port equipment number assignment, replug the station line
on the MDF.

Change the port equipment number:
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
Exchanging Terminals
CHA-SXSU:STNO=<number>,TYPE=PEN,PEN=<ltg-ltu-slot-port>;
142.9 Exchanging Terminals

You can use AMO SXSU to replace ANATE voice terminals with optiset E or
optiPoint 500. (Not applicable to: dummy terminals and SET600.)
Anate
OpenScape 4000
4711
PEN: x
PEN: y
Digite
4711

• You must connect the new device type to the new PEN following changes to
the configuration.
IMPORTANT: A device changeover from optiset E to optiPoint 500 is not

supported by AMO SXSU because this changeover is automatically detected
by the system.
• All other terminal types must be deleted and then re-assigned!
IMPORTANT: Existing group assignments are not lost.
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
Exchanging Terminals

• Exchange a voice terminal:
CHA-SXSU:STNO=number,TYPE=DEV,OPT=param,DVCFIG=param,...;
All terminals that are not supported by the AMO SXSU can be modified by
deleting the old device and configuring a new port with the appropriate data. 
In these cases, if the parameters and features of the old device configuration are
to be taken over, you must display and/or save the appropriate data before you
delete the configuration data, so that you can re-assign them to the new device
configuration as required.
• Display station data:

DIS-SCSU:STNO=number; or
• Save device configuration data and features with REGENERATE commands.
REG-SCSU:STNO=number;
or
REG-SBCSU:STNO=number;
or
REG-SSCSU:STNO=number;
REG-AUN:TYPE=STN,STNO=number;
REG-SA:CD=number;
REG-NAVAR;
REG-SDAT:STNO=number;
REG-COMGR:TYPE=STN,STNO=number;
REG-PERSI:TYPE=STN,STNO=number;
REG-ZIEL:TYPE=FWD,SRCNO=number;
REG-ZIEL:TYPE=NAME,SRCNO=number;
REG-ZIEL:TYPE=SPDI,SRCNO=number;
REG-ZIEL:TYPE=SNR,SRCNO=number;
REG-TGER:STNO=number;
Additionally, for messenger, DSS and executive/secretary destinations:
REG-ZIEL:TYPE=MSGR,SRCNO=number; 
REG-ZIEL:TYPE=DSS,SRCNO=number; 
REG-CHESE:TYPE=STN,STNO=number;
• Delete the device configuration data:
DEL-SCSU:STNO=number,CMIND=ALL,OFFTYPE=DI;
or
DEL-SBCSU:STNO=number,SVC=ALL,OFFTYPE=DI;
or
DEL-SSCSU:STNO=number,OFFTYPE=DI;
• Re-assign station (see Section 142.1, “Adding a Station (Example)”)
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
Station Port Deletion
In the ADD command which results from the REG-SCSU/SBCSU/SSCSU

command, you must change the parameter DVCFIG to the new terminal type
and, where applicable, replace the AMO names and adapt the parameter tree
(for example, if you want to replace an ANATE for an optiset E). Re-assign
station data and features with the remaining ADD commands.
142.10 Station Port Deletion

• Display station data:
DIS-SCSU:STNO=number;
or
or
DIS-SSCSU:STNO=number;
The display table shows which groups the station belongs to.
• Deactivate port:
DEACTIVATE-DSSU:OFFTYPE=DI,TYPE=STNO,STNO=number;
Station is a member of one or more hunt group(s) (HT):
•
DIS-SA:STNO=number;
• Station is a master of a hunt group; enter another station as master:
CHA-SA:TYPE=SA,CDOLD=number,CDNEW=number;
• Station user is an owner of a mailbox which is assigned as overflow for a hunt
group. Enter another station as mailbox owner:
CHA-SA:TYPE=OVFLDEST,OVFLDEST=VMSINT,NUMBER=number;
• Remove the station from the hunt group(s).
The command must be repeated for each hunt group displayed!
DEL-SA:TYPE=STN,CD=number,SVC=param,STNO=number;
• Station is a member of a night option. Display night options:
DIS-NAVAR;
• Remove the station from the night option or delete the night option, if the
station is the only one assigned.
CHA-NAVAR:FUNCT=DIS,TYPE=STN,STNO=number;
or
DEL-NAVAR:NOPTNO=number;
• Station is a member of a pickup (PU) group:
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
DEL-AUN:TYPE=STN,STNO=number;
• Station is an executive in an executive-secretary (CHESE) group:
DEL-CHESE:TYPE=GR,GRNO=number,EXEC=number;
If the station is a secretary, the corresponding executive station must also be
entered.
• Delete the station with:

DEL-SCSU:STNO=number,CMIND=ALL,[OFFTYPE=DI];
or
DEL-SBCSU:STNO=number,BERLM=ALL,[OFFTYPE=DI];
or
DEL-SSCSU:STNO=number,[OFFTYPE=DI];
A31003-H3170-S103-6-7620, 02/2019
tln_en.fm
Stations
A31003-H3170-S103-6-7620, 02/2019
station_controlled_conf_en.fm
Feature Description
143 Station Controlled Conference

For OpenScape 4000 there will continue to be “Three-way conference” created
by functional devices only. The new Station Controlled Conference applies for
all other devices.
“Eight Party Conference”, which has the conference “master” (also known as the
conference chairperson) does not exist in OpenScape 4000.
public network
• Maximum 8 stations per conference
• Connections between confences in different

systems are possible
• No conference master
• Analoge and digital devices can establish a

conference
• Functional devices can only be passive

members
• No feature restrictions for conference

members

Station Controlled Conference (3-8 party) provides the capability for a non-
functional device (e.g., analog or digital) to create a three to eight party
conference. All parties within the conference (except functional devices) have the
A31003-H3170-S103-6-7620, 02/2019
Feature Description
capability to consult out of the conference and bring parties into the conference
as long as the maximum number of parties in the conference does not exceed
eight parties. Functional devices are considered passive parties in a station
controlled conference and therefore can not consult or initiate features or
functions.
Overview:
• Allow a conference of 3-8 parties to be established from analog and digital

devices (except functional devices).
• In a Station Controlled Conference, functional devices as conference

members are passive and therefore do not have access to features and
functions.
• Allow one or more users within a conference to consult to a party outside

the conference.
• Allow one or more users within a conference to toggle between a party

outside the conference and the conference.
• Allow one or more users within a conference to consult to a party outside

the conference and bring that party into conference.
• Allow one or more users within a conference to view the conference

members.
• Allow independent conferences to be created when one or more of the

conference parties are located across a CorNet network. A party located
in a remote node from the conference can also create a conference within
their node. From the user point of view, the connection between nodes
shall be treated like two independent conferences.
• One or more members shall be allowed to initiate the above mentioned

functions simultaneously.
143.1.1 Hold a Conference

An analog telephone user can use the consultation hold feature to place a
conference on hold. They can not use the Group Park (hard hold) or Call Hold
feature to place a conference on hold.
A Keyset user can use the Manual/exclusive Hold feature or the consultation hold
feature to place the conference on hard hold or soft hold.
A Digital Feature Telephone (DFT) can use the consultation hold feature to place
a conference on hold (soft hold). They can not use the Group Park (hard hold)
feature to place a conference on hold.
Executive/Secretary (CHeSe) telephone arrangements can use the features

associated with the physical device and configuration the user is active on.
A31003-H3170-S103-6-7620, 02/2019
Feature Description
A functional device (e.g., Profiset) is a passive conference member and therefore

can not activate features and functions while in a conference.
143.1.2 Pick a Call and add to Conference, or Create

a Conference
Allows one or more users within a conference to simultaneously initiate
• directed call pick up
• group call pick up
• pickup of a camped-on call
and add the call to conference.
Allow a user while active in a basic call connection to pickup a call (e.g., camped
on call, directed call pickup, group call pickup) and create a conference.
143.1.3 Station Controlled Conference in the Private

Network
It is possible to create large conferences in the network by adding a remote party
located in another node, and then that party create a conference in their own
node. There is no restriction in the total number of conference participants in a
network wide conference other than the availability of the conference resources
themselves and the local restriction of eight parties per conference circuit.
Knoten A Knoten V
ISDN
2101 Konferenz1 Konferenz2 3100
2102 Knoten S
3105
4104
Figure 117 Conference using two conference modules
A31003-H3170-S103-6-7620, 02/2019
Feature Description
A remote conference member without its own conference (station 4104 in the
above diagram) located in another PINX(Privat Integrated Netwok Exchange)has
some limitations including
• Not being allowed to delete conference members,
• Local member can consult with a remote member but not with other local
members whereas remote members are not restricted,
• Not receiving notification of members added/leaving/holding the

conference, and
• Not being able to scroll through the conference member list.
When a station is a remote conference member i.e without it’s own conference,
signalling of supplementary services shall occur to the conference (e.g., user
suspended).
Whereas, when a chained conference exists (i.e., two or more conference circuits
connected together as is Conference 1 and Conference 2 in the figure above),
signalling of supplementary services which the remote members invoke shall not
be signalled to the remote conference.
Backward compatibility to the US and IM installed bases is provided.
143.1.4 Prevention of consultation, transfering and

hold by networked conference party
Switch A has a Conference and Switch B has Station 1. A member of the
Conference adds Station 1. If station 1 goes into consultation the Conference
then does not listen to Music On Hold or Ringback because Station 1 has placed
the Conference on Hold. The conference continues as normal, stattion 1 can then
bring in the consulted party into a conference on its local switch which is chained
to the original conference
See Section 143.5, “Relevant AMOs” for information about the AMO-COT
parameter NOHO and interaction with switches which do not signal hold.
143.1.5 Starting a Conference using Keyset Lines

With this function you can create and enhance a conference if a keyset device
holds an other device in linehold. This feature can be used only for keysystem
device.
Service Information
• The conference master has to have the right (AMO COSSU) to create or to
enhance a conference.
A31003-H3170-S103-6-7620, 02/2019
User Interface
• Conference master have to hold a device (anate, digite, trunks, ISDN

devices) in linehold.
If there is more than one device in linehold by conference master keyset, then
the device found at first will be joined to the conference.
• The conference master has to be in basic talk connection.
• The active connection of the joined device has to be the linehold connection:
if the joined device makes consultation then creating or enhancing
conference is not possible.
Restrictions
• If a keyset is in a conference and it is possible to enhance the conference by
this way the VIEW MEMBERS conference menu item is missing.
• To create or enhance the conference is only possible using conference key or

ACL conference service.
Generation
• A new parameter was introduced in AMO COSSU for creating or enhancing
conference: CFKL.
e.g.: CHANGE-COSSU:TYPE=COS,COS=23,AVCE=CFKL;
• Physical station A with secondary line B and C
Station A presses line key for station B and calls D --> D answers,
Station A presses line key for station C and calls E --> E answers.
In order to work the conference properly station C also needs to have a
secondary line for station B.
CHANGE-KCSU:STNO=<C>,TYPE=SEC,KYNO=<Linekey
number>,STNOSEC=<B>;
143.2.1 Create and add

AnaTe
After hookflash station A

consults station C
B A C
A31003-H3170-S103-6-7620, 02/2019
User Interface
• Party A is in conversation with Party B
IMPORTANT: Operation is different from the U.S V6.6. User must dial
access code to bring party into conference. V6.6 uses hookflash to bring party
into conference.
Stn A is in talk state to Stn B. A initiates consultation hold and dial the code
for stn C . When C answers A initaites again consultation hold and dials the
conference access code. All partys hear conference tone and the conference
is established
• PartyA is in a conference with Party B and Party C (prior to dialing party D)
Conference
B A C
Consultation to station D
Stns A,B and C are in conference. Stn A initiates consultation and dials stn D
. At this point although the conference is on “hold” no MOH is heard and the
conference carries on as normal i.e. B and C are in conference. Stn A can
bring Stn D into the conference.
DigiTe or DFT
The conference feature with digital telephones is similar to the Anate in function
but is made easier due to the extra functionality with these sets. Access to a
conference is via CONF key, or the Conference switch from the Optiguide menu
reached by pressing > after consulting with a party. Also with digital telephone
sets there is the possibilty for a display function
With Station controlled conference the display is different from previous versions.
A31003-H3170-S103-6-7620, 02/2019
User Interface
Conference. 1-2-3->
Your position is 2
7446 7445 7440
Note: Pressing the "<" or ">" shall remove display line 2 and display the Optiguide
Feature Prompt (dialog). The position number does not stay in the display all the time
It is also possible to view members of the conference.
7446
next member?
Note: Pressing the "<" or ">" shall remove display line 2 and display the Optiguide
Feature Prompt (dialog). Pressing the tick presents the next member of the
conference
Network conference members can see members of their own conference and the
“partner” station i.e. the member they invited ,or were invited by, into the conference,
but not the conference members in a foreign node.
143.2.2 Hold of a Conference

• A member can place the conference on consultation hold by consulting to a
station outside the conference in the usual way.
• A member (DigiTe only) can place the conference on background hold by

performing any type of pickup.
• A member (DigiTe only) can place the conference on manual or exclusive

hold by performing manual or exclusive hold in the usual way.
In both cases the conference does not hear any hold tone and is in effect still
functional.
143.2.3 Pick a Call and Create a Conference

Any station who is in conference can:
• pick-up a waiting call by pickup group or direct call pick-up.
The picking party leaves the conference functioning as before.
A31003-H3170-S103-6-7620, 02/2019
User Interface
143.2.4 Pick a Call and add to the Conference

Upon picking up a call:
The conferee can press
• the CONFERENCE key, or
• CONSULT key plus access Code for conference
to add the caller to the conference.
143.2.5 Removal of a Conference Member

AnaTe
• Hookflash followed by access Codes for release of each party (1-8) or
release last party. There are separate access codes to be added in the
dial plan to allow these functoions
DigiTe
• Access Codes for release of each party (1-8) or release last party during
consultation out of conference
• CLEAR or CANCEL key to remove last party (only if conference member

is not being viewed)
• Upon viewing a conference member (while display is active) press

CLEAR OR CANCEL key to remove that party
• Deactivation via Optiguide Feature Prompts (dialog).
143.2.6 Optiguide
Viewing Conference Members
To view conference members, while active in conference:
The user displays are the same for all methods of viewing conference members
(uses Optiguide sub-menus)
• Press CONF key (multiple times) to scroll through conference members

(note: positions not occupied shall be skipped)
or
A31003-H3170-S103-6-7620, 02/2019
User Interface
• Optiguide Feature Prompts (dialog) "<View members? >"
IMPORTANT: Pressing the associated keypad digit to view a conference

member is not possible.
Other Optiguide Information

The following feature prompts shall be displayed on line 2 when the user is active
in a station controlled conference with no held party (e.g., toggled party).
"Consultation? >"
"Add to conference? >"
"View members? >"
"Release last party? >" (if applicable)
143.2.7 Station Controlled Conference in the Private

Network
When the local and remote nodes have a linked conference connection
established:
• The user interface can operate as two independent conferences.

Therefore, members in each independent conference can be able to
scroll through their respective conference members (local to their node)
and see the party they are linked to in the remote switch
When a conference is established in one node with a "single station" across

CorNet:
• From the "single station’s" point of view the following happens:
• The CONFERENCE key LED of the single station doesn’t light unless
a local conference is established in the single station node, which
includes that station.
• When brought into the remote conference the single station gets a
display "CONFERENCE" as indication that they are connected to a
remote conference.
• The single party station node shall not inject music into the remote
conference when placing the remote conference on soft or hard hold.
See AMO-COT information in Section 143.5, “Relevant AMOs” for
additional information in situations where the single party’s node does
not signal hold.
A31003-H3170-S103-6-7620, 02/2019
Service Information
• The single station shall be able to initiate all local features they could
initiate when active in a two party connection in their node, with
some exceptions:
The single station cannot do transfer by pull when consulted across the NW by
a conference member
The single station cannot do transfer ringing or transfer busy when consulting
away from the conference connection.
The single station cannot park the conference connection, since pickup of a
conference connection is not allowed.
• From the remote conference point of view the following shall happen:
• The remote conference members shall have access to all conference

features local to their node.
• The remote conference members display shall display the single

station’s name and private number information.
• The remote conference members’ display shall not be updated if the

single station creates a conference or is brought into a conference
local to the single party node.
• The remote conference members display shall be updated if the

CorNet link between the single station and remote conference is
disconnected or if the conference established at the single station
node is disconnected.

There are no patches or country specific implementations.
• Paying-Party for Conference Calls

There is no conference master for the station controlled conference of
OpenScape 4000 the Paying-Party for each part call of the conference will be
the corresponding conference convener. The convener will remain as Paying-
Party for his branch also when he has left the conference already.
• Charge Display for Station controlled Conference

A Charge Display will be sent to the convener only when he drops out of the
conference. A convener will get no further Charge Displays after he has left
the conference, even though he may continue to be the paying party for some
remaining conference legs.
Because of the fact that for each part call of the conference the corresponding
convener will be the Paying-Party INCDR can not summarize all the costs of
all COSTI buffers administrated in one COSTI buffer administration table and
send the resulting cost amount to the display of the conference master.
A31003-H3170-S103-6-7620, 02/2019
Generation
For station controlled conference INCDR must identify all COSTI buffers with the
same Paying-Party summarize the costs and send the resulting cost amount to
the display of the responsible conference convener.
143.4 Generation
• Activate variable conference in the system:
The activation of VARKONF is only possible in expert mode.

Expert Mode > OpenScape 4000 > Expert Access > Open ...<IP> with
AMO (see AMO command)
CHANGE-FEASU:TYPE=A,CM=VARKONF;
• ADD DAR for conference:
Configuration Management --> Tables --> Dial PLan --> Dial Codes,
Click New. Enter Dial Code and select CONF as Code Type. Click
Save.
ADD-WABE:CCD=91,DAR=CONF;
• Change display time of conference information (if wanted):
The time how long the conference information is displayed on a digital

phone can be performed in expert mode.
Expert Mode > OpenScape 4000 > Expert Access > Open ...<IP> with
AMO (see AMO command)
CHANGE-DTIM1:TYPEDH=DIGITE,VWKONFMB=<sec>;
143.5 Relevant AMOs

Language
COSSU CFKL e Conference from keyset lines
KVKL d Konferenz von Keyset-Lines
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

Language
FEASU CM e The value VARCONF allows Station Controlled
Conference in the system
LM d Über den Wert VARKONF können
Teilnehmergesteuerte Konferenzen in der
Anlage zugelassen werden
DTIM1 VWKONFMB e This timer shall control the length of time the
conference information is displayed at the digital
telephone
VWKONFMB d Dieser Timer bestimmt, wie lange die
Konferenzinformationen an digitalen Telefonen
angezeigt werden
WABE DAR e The following values are relevant for conference:
CONF
CONFKY
RMCONFP1
RMCONFP2
RMCONFP3
RMCONFP4
RMCONFP5
RMCONFP6
RMCONFP7
RMCONFP8
RMCONFLP
KZP d Folgende Werte sind für die Konferenz relevant:
CONF
KONFTA
RMCONFP1
RMCONFP2
RMCONFP3
RMCONFP4
RMCONFP5
RMCONFP6
RMCONFP7
RMCONFP8
RMCONFLP
COT NOHO e Prevention of consultation, transfering and hold
by networked conference party
This is to be set when connecting to a system of
HV1.0 or earlier. These systems do not send the
facility messages for conference hold in the
same way a OpenScape 4000 system does.
Because of this there is the danger the
conference would be forced to listen to hold tone
which is not desired. Setting this parameter
prevents a station in the remote node from going
into consultation. This means however the
remote station can not inintiate a local
conference of its own.
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

Language
NOHO d Rückfrage, Übergabe und Halten durch
vernetzten Konferenzteilnehmer verhindern.
Diese Anlagen senden die Dienstmerkmal-
Nachricht für "Konferenz Halten" anders als die
OpenScape 4000-Anlage. Deshalb besteht die
Gefahr, dass die Konferenz den unerwünschten
Halteton hört. Dieser Parameter verhindert, dass
eine Endstelle im abgesetzten Knoten in
Rückfrage geht. Dies bedeutet allerdings, dass
diese Endstelle nicht in der Lage ist, eine eigene
lokale Konferenz einzuleiten.
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
tlnumz_en.fm
Station Relocation
Feature Description
144 Station Relocation

The station relocates from one physical network node to another and retains its
call number. 
First, regenerate and delete the station configuration data in the old node (with
AMO SCSU or SBCSU) and enter the destination number of the new node in the
AMO WABE.
Then re-configure the station configuration data in the new node (using the
regenerated data) after the DESTNO has been set to "0" in the AMO WABE. 
The destination number of the new node must be entered in the AMO WABE 
for all other nodes in the network (with closed numbering).

• A station can also be relocated within a physical node using the AMO SXSU
(PEN exchange).
• Use the AMO SDAT parameter NNO to relocate a station within a physical
node from one virtual node to another (no PEN exchange).
• If the station is a member of a call pickup group, executive/secretary system,

night switch system, ACD group, COM group, keyset or hunt group, it must
first be removed before it can be relocated to another physical node.
• Before deletion, all relevant station data must be regenerated 

(AMOs SDAT, ZIEL, ACTDA, PERSI, TAPRO, LIN, HOTLN, etc.) so that it can
be reentered in the destination system.

Station 7140 moves from node 1-89-100 to node 1-89-300. 
(Prerequisites: network with closed numbering, standard classes of service and
key layouts, LCR configured and no deviating settings in the AMOs SDAT, ZIEL,
ACTDA, PERSI, TAPRO, LIN, HOTLN, etc.)
• Commands for node 1-89-100 (part 1)

REGEN-SBCSU:STNO=7140;
(regenerate further station data if necessary)
• Commands for node 1-89-300

Change the station from external to internal with:
A31003-H3170-S103-6-7620, 02/2019
tlnumz_en.fm
Station Relocation
Relevant AMOs
CHA-WABE:CD=7140,DESTNO=0;
Re-configure the station in node 1-89-300 with (the REGEN command from
node 1-89-100), for example:
ADD-
SBCSU:STNO=number,OPT=OPTI,DVCFIG=param,COS1=number,COS2=numb
er,LCOSS1=number,LCOSS2=number,LCOSD1=number,LCOSD2=number;
• Commands for node 1-89-100 (part 2)
Delete the station with:
DEL-SBCSU:STNO=7140,SVC=ALL;
Assign the destination number for node 3 with:
• Commands for all other nodes in the network
144.4 Relevant AMOs

Language
SBCSU d alle
e all
ZLNR d Zielnummer
A31003-H3170-S103-6-7620, 02/2019
stafwa_en.fm
Description
145 Step by Step Dialing
145.1 Description
Step by step (cut-through) dialing means that when the transition to the next node
has been reached, the subscriber hears an announcement, dials more digits,
hears another announcement, dials again etc., until the required destination has
been reached. The subscriber can only hear the announcement/tones if these
have been configured. Dialing must be carried out via dialed digits only and not
via touchtone dialing. The dialing procedure described is possible when dialing
into a OpenScape 4000 system via an ISDN connection and in the case of transit
traffic to a step by step dialing connection. The ISDN B-channel (audio path) is
not activated in the current call situation, meaning that the subscriber cannot hear
the announcements. With step by step dialing, this B-channel through-connection
becomes effective without any change of status.
Switch 1 Switch 2 (Transit)
OpenScape 4000 OpenScape 4000
ISDN
647 Switch 3
Setup calledPN="" OpenScape 4000
Announcement* ISDN
Analog 648
542
Setup CalledPN=""
Analog Announcement*
544
* if administrated ECMA V2
5xx and 6xx are trunk access codes for step by step dialing Setup
649
Subscriber CalledPN=""
Subscriber in switch 1 dials 542 or 647. Then he hears the announcement from
switch 2 and can continue step dialing to switch 3 with 544, 648 or dial a 547
subscriber number in switch 2. CalledPN information element in the setup is Analog
present but empty.
Figure 118 Step by step dialing
A31003-H3170-S103-6-7620, 02/2019
stafwa_en.fm
Supported Hardware, Lines, Protocols
145.2 Supported Hardware, Lines, Protocols

Step by step dialing operates via CAS, E&M with DP and DTMF, and with the
ISDN protocols DSS1, ECMA and CorNet.
145.3 Restrictions
• In the case of MFC lines, no provision is made for step by step dialing. The
system can be configured to prevent transit DID traffic from MFC lines from
occuring on a step by step dialing route.
• A maximum of 22 digits can be transmitted.
• ANATE with DTMF is not supported
• Step by step dialing from functional S0 terminals is not supported.
• Step by step dialing is only possible for the Voice service.
• Step by step dialing is only supported by special ISDN exchanges due to

premature B-channel through-connections. The LM44573 must be active in
the EWSD exchange.
• The ECMA protocol cannot transfer any SETUP without Called Party Number
(see Section 145.4.3, “Outdial Rule”).
• Step by step dialing is not applicable for the US market.
145.4 Basic Configuration Notes
145.4.1 No Answer
• If one of the circuits used in the step by step dialing connection is capable of
transmitting a NO answer signal, only dial pulsing or ISDN circuits are
permitted for the entire step by step dialing link (problem of digit repetition in
DTMF circuits). This is only necessary if a DTMF circuit is available in the link
that is not capable of transmitting an ANSWER signal.
• In the digit range, the digit "# "cannot be used as the access code, since this
digit is required for speedy through-connection once the last digit has been
dialed (through-connection of the call only after step by step dialing timeout
is thereby no longer valid -> immediate through-connection of the call). Once
"#" has been dialed, it is not possible to dial further digits.
A31003-H3170-S103-6-7620, 02/2019
stafwa_en.fm
Basic Configuration Notes
145.4.2 Routing
In the AMO RICHT (for the outgoing analog step by step circuit), both
REROUTING and ROUTOPTIMATION must be set to NO.
145.4.3 Outdial Rule

• Dialing must lead to the digit analysis result CTDL.
• The AMO LODR can only contain the value "END".
• If an ECMAV2 link starts with a step by step dialing digit analysis result, then
parameter "OUTPULSE" must be configured before the "END" in the AMO
LODR and it must be assigned the value of the node number of the next
allocated node (exception: where the ECMAV2 protocol has been altered
using a customer-specific patch and PRODE commands so that the
parameter "OUTPULSE" is not needed).
145.4.4 COT/COP
• If a local announcement is to be supplied from an incoming allocated circuit,
the COT parameter "ANNC" is to be set. The SIU tone is then applied. This
tone was configured by assigning the value LOCANN in the AMO
ZAND:TONES (incoming allocated circuit). With the COP DTN, the analog
trunk sends a tone to the remote office. You can configure which tone is sent
with the COT parameter (NTON, ONAS, DTNI, DTNE)
• For analog trunk line circuits reserved for reverse dialing in incoming traffic,
the COT parameter "USD" must be set for unrestricted suffix-dialing. This is
not necessary for outgoing step by step dialing in tie trunk traffic.
• For further dialing after ANSWER, the COP parameter "SEDL" must be set
145.4.5 Timer
• The timers in the ECMA, DSS1 and CorNet circuits must be set to "0" (T302,
T303, T304)
• If no "ANSWER" is transmitted, the audio path of the step by step dialing

connection becomes active only after the timer has run out (DTIM2-
>TYPEDH=GEN-> CTDL). If the timer had not run out, the subscriber can dial
further digits for step by step dialing. The audio path has already been
connected but the speech path has not.
A31003-H3170-S103-6-7620, 02/2019
stafwa_en.fm
Configuration Examples
145.5 Configuration Examples
145.5.1 ECMA Protocol with Announcement

CHA-FUNCT:SLANG=GER;
/* Back to english with: CHA-FUNCT:SLANG=ENG; */
/* announcement for call by call dialing, not CALLED_NUMBER
ECMAV2,DSS1 */
/* Change setting for called Num IE from MAND to OPT */
/* PVCD table 1 Germany, PD14 = ECMAV2 */
DEACTIVATE-DSSU:DI,PEN,x;
CHANGE-TDCSU:DEV=S2CONN,BCGR=1,PEN=x,PROTVAR=ECMAV2,SEGMENT=1;
ACT-DSSU:UL,PEN,x;
COPY-PRODE:PVCD,1;
/* PRODE change (example)*/
CHANGE-PRODE:KIND=PD,PDNAME=PD14,SEC=WELMAND,SETNO=46,B02=00;
CHANGE-PRODE:KIND=PD,PDNAME=PD14,SEC=WELMAND,SETNO=46,B12=E0;
CHANGE-PRODE:PD,PD14,ORG,,Y;
/* Timers */
CHANGE-PRODE:PD,PD14,TIMER,T304,0,0;
CHANGE-PRODE:PD,PD14,ORG,,Y;
/* Route */
CHANGE-COT:20,COTDEL,COTN&BCCC&BLOC&ROPT;
CHANGE-COT:20,COTADD,LWNC&NORR&ANNC;/* ANNC,DTNI or DTNE*/
CHANGE-COSSU:LCOSV,1,,,NONE;
ADD-WABE:CD=647,DAR=CTDL;
CHANGE-RICHT:LRTE=647,ROUTOPT=NO,REROUT=NO,MODE=LRTE;
CHANGE-RICHT:LRTE,647,ISDN-Step_by_Step,x;
CHANGE-LDAT:LROUTE=6,LSVC=ALL,LRTEL=1,ODR=6;
/* System */
CHANGE-FEASU:D,VOICO;/* Problem with voice compression */
CHANGE-ZAND:TYPE=TONES,CP=LOCANN,SIU=XX;
CHANGE-ZAND:TYPE=ALLDATA,COANN=YES;
END
A31003-H3170-S103-6-7620, 02/2019
stafwa_en.fm
145.5.2 Dial Pulsing Circuits (DIUC64) with ANSWER

from the Trunk
ADD-WABE:CD=542,DAR=CTDL,CHECK=N;
ADD-BUEND:TGRP=242,NAME="Step_by_Step-DP-1",NO=1,
RSV=N,TRACENO=0,ACDTHRH=*,PRIONO=1,CHARCON=NEUTRAL;
ADD-COP:COPNO=242,PAR=ANS&LSUP&RLSA&DTN&BR64&NO1A&TIE&IDP1,
TRK=TA,TOLL=TA;
ADD-COT:COTNO=242,PAR=RCL&ANS&TIE&IEVT&ANNC;
CHANGE-
COT:COTNO=242,COTTYPE=COTADD,DEV=INDEP,INFO="Step_by_Step-
analog-DP";
ADD-COSSU:NEWCOS=220,AVCE=TA&TNOTCR&CDRSTN&CDRINT&CDRC;
22,COTNO=242,COPNO=242,DPLN=0,ITR=0,COS=220,LCOSV=1,LCOSD=1,TGRP
=242,COFIDX=0,CTT="Step_by_Step-DP
",DESTNO=0,ALARMNO=0,CARRIER=1,ZONE=EMPTY,INS=Y,DEVTYPE=TC,DEV=B
WCISL,MFCVAR=0,SUPPRESS=0,
DGTCNT=0,TESTNO=1,CIRCIDX=11,CDRINT=1,CCTINFO=0,DIALTYPE=DIP-
DIP,DIALVAR=0-0,COEX=0
ADD-RICHT:MODE=LRTENEW,LRTE=242,LSVC=ALL,TGRP=242,DNNO=1-1-
100,REROUT=NO,ROUTATT=NO,INFO="Step_by_Step-DP";
ADD- -
LDAT:LROUTE=242,LSVC=ALL,LVAL=1,TGRP=242,ODR=7,LAUTH=1,CARRIER=1
,ZONE=EMPTYLATTR=NONE,DNNO=1-1-100,MSO=NONE,BANDW=1,VCCYC=4;
ADD-LDPLN:LDP="542",LROUTE=242,LAUTH=1;
145.5.3 DTMF Circuits (DIUC64) with ANSWER from

the Trunk
ADD-BUEND:TGRP=244,NAME="Step_by_Step-DTMF-
1",NO=1,RSV=N,TRACENO=0,ACDTHRH=*,PRIONO=1,CHARCON=NEUTRAL;
ADD-COP:COPNO=244,PAR=ANS&LSUP&RLSA&DTN&DTMF&DTM1&NO1A&TIE&IDP1,
TRK=TA,TOLL=TA;
CHANGE-
analog-DP";ADD-
COSSU:NEWCOS=220,AVCE=TA&TNOTCR&CDRSTN&CDRINT&CDRC;
=244,COFIDX=0,CCT="Step_by_Step-DP
WCISL,MFCVAR=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=11,CDRINT=1,
CCTINFO=0,DIALTYPE=DTMF-DTMF,DIALVAR=0-0,COEX=0;
A31003-H3170-S103-6-7620, 02/2019
stafwa_en.fm
ADD-
,ZONE=EMPTY,LATTR=NONE,DNNO=1-1-100,MSO=NONE,BANDW=1,VCCYC=4;
145.5.4 Dial Pulsing Circuits (TMEMW) with ANSWER

from the Trunk
ADD-WABE:547,DAR=CTDL,TEST=NO;
ADD-BUEND:TGRP=247,NAME="Step_by_Step-DP-
Tie_Trunk",NO=1,RSV=N,TRACENO=0,ACDTHRH=*,PRIONO=1,CHARCON=NEUTR
AL;ADD-
COP:COPNO=247,PAR=ANS&LSUP&RLSA&DTN&BR64&NO1A&TIE&IDP1,TRK=TA,TO
LL=TA;
CHANGE-
analog-DP";
=247,COFIDX=0,CCT="Step_by_Step-DP-Tie_Trunk
",DESTNO=0,ALARMNO=0,CARRIER=1,ZONE=EMPTY,INS=Y,DEVTYPE=TT,DEV=T
SEMU;
100,REROUT=NO,ROUTATT=NO,INFO="Step_by_Step-DP-Tie_Trunk";
ADD-
,ZONE=EMPTY,LATTR=NONE,DNNO=1-1-100,MSO=NONE,BANDBR=1,VCCYC=4;
Circuits as DTMF (TMEMW) without ANSWER from the trunk
ADD-BUEND:TGRP=249,NAME="Step_by_Step-Tie-Trunk
",NO=1,RSV=N,TRACENO=0,ACDTHRH=*,PRIONO=1,CHARCON=NEUTRAL;
ADD-
COP:COPNO=249,PAR=ANS&LSUP&RLSA&DTN&DTMF&DTM1&NO1A&TIE&IDP1,TRK=
TA,TOLL=TA;
CHANGE-
analog-DP";
A31003-H3170-S103-6-7620, 02/2019
stafwa_en.fm
=249,COFIDX=0,CCT="Step_by_Step-DTMF-Tie_Trunk
SEMU;
100,REROUT=NO,ROUTATT=NO,INFO="Step_by_Step-DTMF-Tie_Trunk";
ADD-
145.5.5 Dial Pulsing Circuits (DIUC64) without

ANSWER from the Trunk
ADD-BUEND:TGRP=242,NAME="Step_by_Step-DP-1
ADD-
COP:COPNO=242,PAR=LSUP&RLSA&DTN&BR64&NO1A&TIE&IDP1,TRK=TA,TOLL=T
A;
ADD-COT:COTNO=242,PAR=RCL&TIE&IEVT&ANNC;
CHANGE-
analog-DP";
=242,COFIDX=0,CCT="Step_by_Step-DP
WCISL,MFCVAR=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=11,CDRINT=1,
CCTINFO=0,DIALTYPE=DIP-DIP,DIALVAR=0-0,COEX=0;
ADD-
145.5.6 DTMF Circuits (DIUC64) without ANSWER

from the Trunk
A31003-H3170-S103-6-7620, 02/2019
stafwa_en.fm
ADD-BUEND:TGRP=244,NAME="Step_by_Step-DMTF-1
",NO=1,RSV=N,TRACENO=0,ACDTHRH=*,PRIONO=1,CHARCON=NEUTRAL;ADD-
COP:COPNO=244,PAR=LSUP&RLSA&DTN&DTMF&DTM1&NO1A&TIE&IDP1,TRK=TA,T
OLL=TA;
CHANGE-
analog-DP";
=244,COFIDX=0,CCT="Step_by_Step-
DTMF",DESTNO=0,ALARMNO=0,CARRIER=1,ZONE=EMPTY,INS=Y,DEVTYPE=TC,D
EV=BWCISL,MFCVAR=0,SUPPRESS=0,DGTCNT=0,TESTNO=1,CIRCIDX=11,CDRIN
T=1,CCTINFO=0,DIALTYPE=DTMF-DTMF,DIALVAR=0-0,COEX=0;
100,REROUT=NO,ROUTATT=NO,INFO="Step_by_Step-DTMF";
ADD-
145.5.7 Dial Pulsing Circuits (TMEMW) without

ANSWER from the Trunk
ADD-BUEND:TGRP=247,NAME="Step_by_Step-DP-tie_trunk
ADD-
COP:COPNO=247,PAR=LSUP&RLSA&DTN&BR64&NO1A&TIE&IDP1,TRK=TA,TOLL=T
A;
CHANGE-
analog-DP"";
=247,COFIDX=0,CCT="tep_by_step-DP-tie_trunk
SEMU;
100,REROUT=NO,ROUTATT=NO,INFO="Step_by_Step-DP-tie_trunk";
ADD-
A31003-H3170-S103-6-7620, 02/2019
stafwa_en.fm
145.5.8 DTMF Circuits (TMEMW) without ANSWER

from the Trunk
ADD-BUEND:TGRP=249,NAME="Step_by_Step-DMTF-Tie_Trunk
ADD-
COP:COPNO=249,PAR=LSUP&RLSA&DTN&DTMF&DTM1&NO1A&TIE&IDP1,TRK=TA,T
OLL=TA;
ADD-COT:COTNO=249,PAR=RCL&TIE&AEOD&IEVT&ANNC;
CHANGE-
analog_DTMF";
=249,COFIDX=0,CCT="Step_by_Step-DTMF-Tie_trunk
SEMU;
100,REROUT=NO,ROUTATT=NO,INFO="Step_by_Step-DMTF-Tie_Trunk";
ADD-
145.5.9 Configuration Data for Step by Step Dialing

via ECMAV2 (Analog Dial Pulsing Circuit)
Prerequisite: ECMAV2 link for trunk group 72 (open numbering) is available on
the system.
ADD-RICHT:MODE=LRTENEW,LRTE=246,LSVC=ALL,NAME="TRANSIT-S2-
SATFF",TGRP=72,DNNO=1-1-
100,REROUT=NO,ROUTATT=NO,CHARCON=NEUTRAL;
ADD-
LDAT:LROUTE=246,LSVC=ALL,LVAL=1,TGRP=72,ODR=246,LAUTH=1,CARRIER=
1,
ZONE=EMPTY,LATTR=NONE,DNNO=1-1-100,MSO=NONE,BANDW=1,VCCYC=4;
A31003-H3170-S103-6-7620, 02/2019
stafwa_en.fm
145.5.10 Configuration Data for Step by Step Dialing

via ECMAV2 (DTMF analog)
Prerequisite: ECMAV2 link for trunk group 72 (open numbering) is available on
the system.
ADD-RICHT:ART=LRTENEW,LRTE=251,LSVC=ALL,NAME="TRANSIT-S2-
Step_by_Step",
TGRP=72,DNNO=1-1-100,REROUT=NO,ROUTATT=NO,CHARCON=NEUTRAL;
ADD-
LDAT:LROUTE=251,LSVC=ALL,LVAL=1,TGRP=72,ODR=251,LAUTH=1,CARRIER=
1,ZONE=EMPTY,LATTR=NONE,DNNO=1-1-100,MSO=NONE,BANDW=1,VCCYC=4;
A31003-H3170-S103-6-7620, 02/2019
nachwahl_en.fm
Suffix Dialing
Feature Description
146 Suffix Dialing

The following deals with implementing OpenScape 4000 in the analog telephone
networks of traffic enterprises: Bundes-Autobahnen (AB, German federal
motorways), Deutsche Bundesbahn (DB, German Federal Railways), Deutsche
Reichsbahn (DR, German Reichsbahn) und Wasserstraßen- und Schiffahrts-
Direktion (WSD, Waterways and Shipping Authority), Energie Versorgungs
Unternehmen (EVU, Power and Utilities) and for the following countries: CIS,
Poland and Italy. Here the subscriber can continue to dial in to the analog network
(suffix-dialing) even after the OpenScape 4000 has received an "answer" signal.
Suffix-dialing is possible from analog (dial pulsing) and digital terminals and from
ACs.
A maximum of 22 digits can be transmitted.
The parameter DPSTN must be maintained in the COS of all trunks in all
OpenScape 4000s. The parameter must always be set for S0/S2 circuits.
Access to the analog telephone network is achieved via digital tie trunks with CAS
(TFZ or EB5/NAL signaling), or indirectly via one or more transit nodes. These
transit nodes must be networked via digital tie trunks with S2 (CorNet-N protocol).
The analog trunks are connected to the digital CAS interface via primary
multiplexers (PMUX) in the case of TFZ signaling and via signal converters in the
case of EB5/NAL signaling. Incoming trunk calls via EB5 systems can be returned
to the EB5 attendant console by the called OpenScape 4000 subscriber by dialing
the flashing code. EB5 subscribers can intrude on OpenScape 4000 subscriber
calls if the subscriber dialed is busy. OpenScape 4000 subscribers, however,
cannot intrude on EB5 subscriber calls. Another application is the connection of
adapters for analog networks (AAN) to OpenScape 4000 via the TFZ interface.
A31003-H3170-S103-6-7620, 02/2019
nachwahl_en.fm
Suffix Dialing
Feature Description
Analog telephone network
S2 Transit Gateway
S2 CAS/EB5 Trunk
DIU DIU DIU DIU DIU D Trunk
S2 S2 S2 S2 S2
A Tie trunk
Tie trunk
OpenS OpenSca Signal converter
OpenScape AC
cape pe 4000 (KZU)
4000 EB5/34
4000 DIU
CAS CAS/TFZ
D
analog - AAN
A - channel converter
Tie trunk - analog transmission
PMUX
S2 OpenScape
DIU-S2 DIU-S2
S0 4000
STMD STMD
E&M/CF E&M/CF
TMEMW TMEMW TMEMW
TMSFP TMSFP TMSFP
TM3WO TM3WI TM3WO
CAS CAS
DIU-CAS DIU-CAS DIU-CAS
Analog tie trunk

to the EVU network
Figure 119 Example of connection and networking
Line circuit parameter USD

Analog trunk line circuits reserved for reverse dialing in incoming traffic must be
prepared in the class of trunk (COT) with the USD circuit parameter for
unrestricted suffix-dialing. This is not necessary for outgoing step by step dialing
in tie trunk traffic.
• You can expand the class of trunk for unrestricted suffix-dialing as follows:
CHA-COT:COTNO=x,COTTYPE=COTADD,PAR=USD;
RICHT parameters
The RICHT parameters ROUTOPT=NO and REROUT=NO must be set.
LODR parameters
The configured LODR should begin with COXSEND.
A31003-H3170-S103-6-7620, 02/2019
nachwahl_en.fm
Suffix Dialing
Flashing Signal at AC
Digit input timer

The digit input timer T302 for digital trunks (S0/S2) must be extended to 30
seconds.
146.2 Flashing Signal at AC

Digit analysis result OUTPULSE
The digit analysis result OUTPULSE is designed to send digits, in this case for
"flashing signal at AC" on the EB5 system. The only call progress state permitted
is consultation hold (CPS 9).
• You can configure the code for flashing in the AMO WABE as follows:
ADD-WABE:STNO=x,CPS=9,DAR=OUTPULSE;
Line circuit parameter FLAC

EB5/NAL line circuits reserved for external transit traffic must be released for
flashing in the class of trunk (COT) with the line circuit parameter FLAC. The line
circuit parameter FLAC may not be set for tie trunk traffic.
• You can expand the class of trunk for flashing as follows:

CHA-COT:COTNO=x,COTTYPE=COTADD,PAR=FLAC;
146.3 Busy Override

Line circuit parameter OVR
EB5/NAL line circuits must be released for busy override in the class of trunk
(COT) with the line circuit parameter OVR. The line circuit parameter OVR should
not be set for TFZ line circuits.
• You can expand the class of trunk for busy override as follows:
CHA-COT:COTNO=x,COTTYPE=COTADD,PAR=OVR;
146.4 TFZ Signaling

TFZ signaling has been developed for the digital interface between OpenScape
4000 and the special telephone networks of the traffic enterprises.
Loadware variant 5
The loadware with TFZ signaling for the DIUC boards must be available on the
OpenScape 4000 system hard disk:
:PDS:APSP/LTG/LG57/PZFDCAS5 (for DIUC Q2185)
A31003-H3170-S103-6-7620, 02/2019
nachwahl_en.fm
Suffix Dialing
TFZ Signaling
• You can configure the DIUC board with loadware variant 5 as follows:
DIUC64:
ADD-BCSU:TYPE=DIU,LTG=gg,LTU=uu,SLOT=bbb,PARTNO="Q2185-
X",LWVAR=5;
• The loadware variant can be subsequently assigned as follows:
DIUC64 (Q2185):
CHA-ZAND:TYPE=LOADWARE,LWTYPE=DCAS,LWVAR=5; (for DIUC Q2185)
IMPORTANT: To load the LWVAR, the board with the AMO BSSU must be
switched off and on again.
Device TSTFZ
The following example shows the configuration of TFZ tie trunk circuits with suffix-
dialing.
• You can configure the class of trunk for TFZ tie trunk circuits as follows:
ADD-COT:COTNO=x,PAR=AND&USD;
• You can configure the trunk parameter circuits for TFZ tie trunk circuits as
follows:
ADD-
COP:COPNO=x,PAR=SDL&BR64&NO1A&IDP3&MSG&RLSA&RLSB&LSUP&TIE;
• You can configure the TFZ trunk group for tie trunk traffic (for example 30
circuits) as follows:
ADD-BUEND:TGRP=x,NAME="TFZ-TIE",NO=30;
• You can configure 30 tie trunk circuits with TFZ signaling as follows:
ADD-TACSU:NO=30,PEN=gg-uu-bbb-
1,COTNO=x,COPNO=x,TGRP=x,DEVTYPE=AS,DEV=QSTFZ;
PTIME init block for device TSTFZ

The initialization data for the device TSTFZ are saved on the hard disk in init block
40 (see AMO PTIME). The data are loaded automatically from the AMO TACSU.
To change a fixed default value (for example two-way, incoming), the following
steps must be taken:
• Load init timer block 40 from the hard disk into the DB (into TBLK 11, for
example) with:
• You can change the value for parameter 3 with:
CHA-PTIME:TYPE=REST,TBLK=11,BTYPE=PARA,P3=2;
• You can assign the new timer block 11 to all trunk groups as follows:
A31003-H3170-S103-6-7620, 02/2019
nachwahl_en.fm
Suffix Dialing
EB5/NAL signaling
CHA-TACSU:PEN=gg-uu-bbb-ss,DEVTYPE=AS,DEV=TSTFZ,CIRCIDX=11;
IMPORTANT: To load the new parameters, all relevant circuits with the AMO
DSSU must be switched off and on again. Alternatively, you can also selectively
assign the modified timer block when configuring the circuits.
146.5 EB5/NAL signaling

EB5/NAL signaling is designed for the digital interface between OpenScape 4000
and the two-motion selector system EB5/34 from Deutsche Reichsbahn (DR).
Loadware variant 5
The loadware with EB5/NAL signaling for the DIUC boards must be configured
on the OpenScape 4000 system hard disk as follows:
:PDS:APSP/LTG/LG57/PZFDCAS5 (for DIUC Q2185)
• You can configure the DIUC boards with loadware variant 5 as follows:
DIUC64:
ADD-BCSU:TYPE=DIU,LTG=gg,LTU=uu,SLOT=bbb,PARTNO="Q2185-
X",LWVAR=5;
• The loadware variant can be subsequently assigned as follows:
DIUC64 (Q2185):
CHA-ZAND:TYPE=LOADWARE,LWTYPE=DCAS,LWVAR=5; (for DIUC Q2185)
IMPORTANT: To load the LWVAR, the board with the AMO BSSU must be
switched off and on again.
Device EB5NAL
For incoming traffic, the OpenScape 4000 needs to distinguish between external
transit traffic and tie trunk traffic so that a flashing signal is only sent in the case
of incoming external traffic. In the case of OpenScape 4000 incoming seizure,
EB5 signal generation offers no criteria for distinguishing between the various
types of traffic. Therefore, the traffic must be channeled according to its origin into
2 separate trunk groups in the EB5 and must also be implemented in this form in
the OpenScape 4000. Both trunks can be on the same DIUC. 
The following example shows the configuration of EB5/NAL trunk circuits with
busy override and flashing.
• You can configure the class of trunk for EB5/NAL trunk circuits as follows:
ADD-COT:COTNO=x,PAR=ANS&USD&OVR&FLAC;
A31003-H3170-S103-6-7620, 02/2019
nachwahl_en.fm
Suffix Dialing
EB5/NAL signaling
• You can configure the line parameter class for EB5/NAL trunk circuits as
follows:
ADD-COP:COPNO=x,PAR=SDL&BR64&NO1A&IDP3&MSG&RLSA&LSUP;
• You can configure the EB5/NAL trunk group for tie trunk traffic (for example
30 circuits) as follows:
ADD-BUEND:TGRP=x,NAME="EB5-CO",NO=30;
• You can configure 30 trunk circuits with EB5/NAL signaling as follows:
1,COTNO=x,COPNO=x,TGRP=x,DEVTYPE=AS,DEV=EB5NAL;
The following example shows the configuration of EB5/NAL tie trunk circuits with
busy override and suffix-dialing (the difference between trunk traffic and tie trunk
traffic is determined via the trunk parameter "TIE").
• You can configure the class of trunk for EB5/NAL tie trunk circuits as follows:
ADD-COT:COTNO=x,PAR=ANS&USD&OVR;
• You can configure the line parameter class for EB5/NAL tie trunk circuits as
follows:
ADD-COP:COPNO=x,PAR=SDL&BR64&NO1A&IDP3&MSG&RLSA&LSUP&TIE;
• You can configure the EB5/NAL trunk group for tie trunk traffic (for example
30 circuits) as follows:
ADD-BUEND:TGRP=x,NAME="EB5--TIE",NO=30;
• You can configure 30 tie trunk circuits with EB5/NAL signaling as follows:
33,COTNO=x,COPNO=x,TGRP=x,DEVTYPE=AS,DEV=EB5NAL;
PTIME init block for device EB5NAL

The initialization data for the device EB5NAL are saved on the hard disk in init
block 41 (see AMO PTIME). The data are loaded automatically by the AMO
TACSU. To change a fixed default value (for example two-way, incoming), the
following steps must be taken:
• Load init timer block 41 from the hard disk into the DB (into TBLK 12, for
example) with:
• You can change the value for the parameter P3 as follows:
CHA-PTIME:TYPE=REST,TBLK=12,BTYPE=PARA,P3=2;
• You can assign the new timer block 12 to all circuits of the trunk group with:
A31003-H3170-S103-6-7620, 02/2019
nachwahl_en.fm
Suffix Dialing
EB5/NAL signaling
CHA-TACSU:PEN=gg-uu-bbb-ss,DEVTYPE=AS,DEV=EB5NAL,CIRCIDX=12;
IMPORTANT: To load the new parameters, all relevant circuits with AMO DSSU
must be switched off and on again. You can also selectively assign the changed
timer block when configuring the circuits.
A31003-H3170-S103-6-7620, 02/2019
nachwahl_en.fm
Suffix Dialing
EB5/NAL signaling
A31003-H3170-S103-6-7620, 02/2019
aulzunt_cm_en.fm
Suppression of the FWD Destination at the Caller’s Display
Feature Description
147 Suppression of the FWD Destination at the Caller’s

Display

The station dialed is still displayed on the caller’s terminal even though call
forwarding, forwarding on busy, or call forwarding - no answer has been activated
at the destination.

• Refer to station number suppression as explained in the chapter on display
suppression.

• Activate display suppression as follows:
Configuration Management --> Tables --> Traffic Restrictions Group,

click New. Enter group, then select "Suppress Display on Call Forward"
in the Basic Data tab and save.
Set display suppression with the AMO VBZGR, parameter value CFW. 
ADD-VBZGR:GROUP=<ITR_group>,TYPE=CFW;
This command accomplishes the following: When there are calls to a user in this
internal traffic restriction (ITR) group with call forwarding (FWD), call forwarding
on busy (CFB), or call forwarding - no answer (CFNR) to another destination, the
caller still sees the dialed number on the display, regardless of where the call is
forwarded.
• Deactivate display suppression as follows:
Configuration Management --> Tables --> Traffic Restrictions Group,

click New. Enter group, then deselect "Suppress Display on Call
Forward" in the Basic Data tab and save.
Delete with the AMO VBZGR, parameter value CFW. 

DEL-VBZGR:GROUP=<ITR_group>,TYPE=CFW;
A31003-H3170-S103-6-7620, 02/2019
aulzunt_cm_en.fm
Suppression of the FWD Destination at the Caller’s Display
Relevant AMOs
Once this command has been executed, the actual destination number is
displayed on the caller’s terminal when he or she calls a member of this ITR group
with activated FWD, CFB, or CFNR.
147.4 Relevant AMOs

Language
VBZGR GROUP d VERKEHRSBEZIEHUNGS/WABE-
GRUPPENNUMMER
GROUP e INTERNAL TRAFFIC RESTRICTION OR DIAL
PLAN GROUP
TYP d EINTRAGSTYP,
VERZWEIGUNGSPARAMETER
CFW = CALL-FORWARDING
TYPE e DESIRED HOTLINE/OFFHOOK RECALL
OPTION
CFW = CALL-FORWARDING
A31003-H3170-S103-6-7620, 02/2019
trans_en.fm
Feature Description
148 Transfer before Answer ex Call State

Station A dials the number of an external station B (1st Call). If station A has a
special authorization he can enter consultation state before end of dialing and
e.g. call station C in the network or station D internally. Station A can transfer the
calls after one of the dialed parties has answered.
OpenScape 4000. OpenScape 4000........

outgoing/
outgoing/
external
external
ISDN call
ISDN
call CorNet NQ S0/S2
CorNet NQ S0/S2
CorNet NQ S0/S2 CorNet NQ S0/S2
B Pty B Pty
D Pty
A Transfering Pty C Pty

Figure 120 Transfer before Answer ex Call State

The parameter XFBADIAL in AMO FEASU activates this feature centrally in a
system. It allows consultation hold before end of dialing for the first connection.
Alternatively, this feature can be activated using the parameter XFBACALL in

AMO FEASU. This feature allows consultation call either after end of dialing (free
or non-evaluated) for the first connection or from the time when the call was
routed into the analog network.
Only one of the two parameters may be set.
The second alternative must be used, if features such as returning FWD/BUSY,

LCR rerouting or LCR expensive routing are to be used on the S0/S2 trunk group
of the first connection.
To prevent unauthorized use of this feature the parameter SUTVA in AMO

COSSU can be configured.
In order to be able to use “Transfer before Answer ex Call State” for outgoing
trunk and tie traffic, the COT parameter TRBA must be set locally in the S0/S2 B
channel trunk group of the first connection in the originating node. It is of no
importance whether the first connection is routed in the own or an external
network (e.g. PTT) or whether the called party is located in the own or an external
network.
A31003-H3170-S103-6-7620, 02/2019
trans_en.fm
Service Information
Consultation call for an outgoing connection via S0/S2 activated by an authorized

station for a voice service can be initiated only after the system received the
acknowledgment of the first connection and the FEASU parameter “Extension
Transfer Before Answer ex Dial State” is set. An ANATE can initiate consultation
call without consultation key only after it received the end of dialing (free or non-
evaluated) acknowledgment, as the consultation function is derived from the
dialing information.
Otherwise, consultation call for an outgoing connection via S0/S2 activated by an

authorized station for a voice service can be initiated only after the system
received the end of dialing (free or non-evaluated) acknowledgment of the first
connection, or from the time when the call was routed into the analog network and
the parameter XFBACALL in AMO FEASU is set.
IMPORTANT: Up to now consultation call could only be initiated from the station
after the first call entered talk state.
If the outgoing S0/S2 first connection (preferably a trunk call) is in call state or
digit-sequence transmission, the A station can transfer the first connection to
station C who is on consultation hold and has answered. Station C can be located
internally in the system or in a network which is connected via S0/S2.
The first call (via S0/S2) can only be transferred, if one of the two connections is
in talk state.

This feature does not support networking trunks with extension loop signalling
and all analog tie and trunk signalling on the first connection (without voice
connection).
This feature is not supported to Functional Devices (including SIP phones).
This feature is not supported if rerouting is active (AMO RICHT,

REREOUT=YES). Use of AMO COSSU parameter LCRET=ALCROPT also
behaves as if rerouting is active.
This feature is also not supported on networking trunks with extension loop
signalling and all analog tie and trunk signalling on the consultation connection
(with voice connection) and on the first connection via S0/S2 (without voice
connection).
If an outgoing unanswered S0/S2 first connection (trunk call) enters busy state or
the connection was released backwards, initiation of consultation call or call
transfer is not possible.
A31003-H3170-S103-6-7620, 02/2019
trans_en.fm
Service Information
If both connections (first connection via S0/S2 and the consultation connection)
are in call state and the call is transferred by going on hook, the consultation
connection is released forward and the call is signalled at the transferring station.
If transfer was activated by key “NOT POSSIBLE” is displayed.
As the user interface shows “NOT POSSIBLE” in negative call transfer cases, call
transfer should be activated by key instead of going on hook.
If call transfer is initiated by going on hook the user should make certain, that one
of the connections is in talk state to avoid negative cases.
If the first connection is in talk state, consultation call and call transfer from the
station as well as other services are handled as previously.
If the first call has not yet answered and the DIGITE activates the CLEAR/
CANCEL or TOGGLE key, the consulted party is released and the station enters
the current state of the first connection.
If the consulted party dials before the first connection answers, the following DAR
are set to “NOT POSSIBLE”:
WABE OUTPULSE Outpulse specific digits during call

OPROVR Demand to override by co-operator
EXTANS Interception by AC in partner system
VMOWN Operation of the VM for the user
VMFOR Access to other (’foreign’) users’ voice mailbox
DOORCL Answering a door call
ANSINT Answering device, internal
RA Recorded announcement for a certain area
PU Call pickup
DNIT DNI Directory number information table
If the feature “Direct trunk select” is active on the first connection, “Transfer before
Answer ex Call State” cannot be activated.
Should the first connection lead to a text/fax server or to a VMS or PMS, which is
known to the originating PBX, “Transfer before Answer ex Call State” cannot be
activated.
If consultation was initiated before the first connection answers, the following
reactions are carried out:
• any FWD or FNA is suppressed at the consulting party
• if an executive/secretary system is called, the executive is called and not the

secretary
• a master hunting group is suppressed, i.e. only the master station is called.
The call is not transferred to another station in the master hunting group.
A31003-H3170-S103-6-7620, 02/2019
trans_en.fm
Effects on other features
Consultation call via the same line is not possible. Instead, consultation call is
established via a different B channel.
The feature “Transfer before Answer ex Call State” doesn’t support DSS1 phones
neither in their active (transferring party) nor in their passive (consulted party)
function.
148.3 Effects on other features

• If the parameter XFBACALL in AMO FEASU is set, the following features are
either deactivated or are no longer possible on the first connection (via S0/
S2) if consultation is initiated before end-of-dialing on the first connection:
– LCR rerouting
– returning call forwarding
– returning deflection of busy calls
• If the parameter XFBADIAL in AMO FEASU is set alternatively, the following

features are either deactivated or are no longer possible on the first
connection ( via S0/S2):
– returning call forwarding no answer
A second B channel is used for consultation.
This feature cannot be used with first connection with Release Control.
If the feature “Emergency disconnect after internal dialing” is active on the first
connection, Transfer before Answer ex Call State cannot be activated.
If consultation before answer was activated on the outgoing first connection the
features e.g. Call Park, Override/Camp-on, Callback cannot be activated on the
first connection. These features can be used again, as soon as the station returns
to the first connection. Only answered calls can be parked. On the consulting
party‘s side the DAR “NOT POSSIBLE” are displayed, i.e. the feature is not
supported.
If consultation before answer was activated on the outgoing first connection, the
consultation connection is override protected. This protection applies after call
transfer. It is released, when the initial connection answers.
After transfer the consulting partner cannot finish incomplete dialing to the first
destination.
If consultation before answer was initiated on the outgoing first connection, a

conference before answer on the outgoing first connection is not possible.
Fixed DTMF dialing on the first connection must not be configured (AMO Richt).
A31003-H3170-S103-6-7620, 02/2019
trans_en.fm
Service Information

• An operational PABX is required, i.e. an S0/S2 trunk and tie line (CorNet-NQ)
must be configured and 1operational. Basic internal traffic capabilities,
including consultation and external consultation calls via S0/S2, must be
configured and likewise operational.
• S0/S2 B channel transfer (first connection is talk state) must be configured

and operational.
• Only XFBADIAL or XFBACALL may be set in the AMO FEASU.
• For subscriber-specific release please refer to Chapter 130, “On Hook

Transfer per User or a Group of Users”.
148.5 Generation
• Consultation can be activated either after end of dialing (free or unevaluated)
on the first connection or from the time the call was routed to the analog
network.
CHA-ZAND:TYPE=ALLDATA,TRANSFER=EXTEND;
CHA-FEASU:TYPE=A,CM=XFBACALL;
CHA-COSSU:TYPE=COS,COS=xx,AVCE=SUTVA;
CHA-COT:COTNO=xx,COTTYPE=COTADD,PAR=TRBA;
• Alternatively, consultation can be activated before end of dialing on the first
connection.
CHA-ZAND:TYPE=ALLDATA,TRANSFER=EXTEND;
CHA-FEASU:TYPE=A,CM=XFBADIAL;
CHA-COSSU:TYPE=COS,COS=xx,AVCE=SUTVA;
CHA-COT:COTNO=xx,COTTYPE=COTADD,PAR=TRBA;
148.6 Relevant AMOs

Language
COSSU TUEVM d Berechtigten Teilnehmern ist es erlaubt,
eine gehende Erstverbindung via S0/S2
Sätzen im Wahl-oder Rufzustand, der
gehenden Rückfrageverbindung (im
Gesprächszustand) zu übergeben.
A31003-H3170-S103-6-7620, 02/2019
trans_en.fm
Relevant AMOs

Language
SUTVA e Authorized stations can transfer an
outgoing first connection in dialing or call
state to the outgoing consultation
connection (in talk state) via S0/S2 trunks.
COT UEVM d Dieser Satz bzw. Sätze erlaubt es
berechtigten Teilnehmern eine gehende
Erstverbindung via S0/S2 Sätzen im Wahl-
oder Rufzustand, der gehenden
Rückfrageverbindung (im
TRBA e Using this/these trunk(s) authorized stations
can transfer an outgoing first connection in
dialing or call state to the outgoing
consultation connection (in talk state) via
S0/S2 trunks.
FEASU TRVARUF d In der Anlage ist es Teilnehmern erlaubt,
Sätzen im Rufzustand der gehenden
XFBACALL e Stations in this PBX can transfer an
outgoing first connection in call state to the
outgoing consultation connection (in talk
state) via S0/S2 trunks.
TRVAWAHL In der Anlage ist es Teilnehmern erlaubt,
Sätzen im Wahlzustand (Zielrufnummer
muss komplett sein) der gehenden
XFBADIAL e Stations in this PBX can transfer an
outgoing first connection in dialing state
(destination number must be dialed
completely) to the outgoing consultation
connection (in talk state) via S0/S2 trunks
ZAND UEBERG In der Anlage können alle Teilnehmer
übergeben.
EXTEND e All stations in this PBX can transfer calls.
A31003-H3170-S103-6-7620, 02/2019
user_signaling_us_en.fm
Feature Description
149 User Signaling for the U.S. Market

The system is able to support the special ring, LED and tone cadences that are
familiar in the U.S. systems.
For the U.S. Market special LED flash rates ,

Ring cadences and Tone settings have to be
made to match existing preferences.
The intent of this document is to provide the administration required to implement

the U.S. type LED cadences, ringing and tones.

There is no specific user interface for this feature. All features will work the same
except for the LED, ringing and tones required for the U.S. market.

• This feature is intended for the global marketplace.
• The emphasis for this feature relates primarily to the U.S. marketplace.
However ther may be occasions where this feature is required in other
countries e.g. U.S companies in the I.M.
149.4.1 LED Handling

• The following settings are required in order to receive the correct LED
cadences for US installations.
A31003-H3170-S103-6-7620, 02/2019
CHANGE-ZAND:TYPE=LEDTYPE,RINGING=MEDIUM;
CHANGE-ZAND:TYPE=LEDTYPE,HELD=WINK;
CHANGE-ZAND:TYPE=LEDTYPE,CALLFWD=VERYFAST;
CHANGE-ZAND:TYPE=LEDTYPE,FEATURE=MEDIUM;
CHANGE-ZAND:TYPE=LEDTYPE,PRIORITY=VERYFAST;
The following tables show the relationship between the database, the amo
parameters, and the actual cadences.
LED Function RATE LED CADENCE

ON(ms) OFF(ms)
Feature SLOW 750 750
DB_LED_OP_BLINKEN_LANGSAM)
Priority FAST 250 250

DB_LED_OP_BLINKEN_SCHNELL )
Ringing DB_LED_OP_RING FAST 250 250

Held DB_LED_OP_RING SLOW 750 750
Callfwd DB_LED_OP_CALL_FORWARD OFF 0 100
Table 66 Default Initialisation of LEDs for I.M
LED Function RATE LED CADENCE

ON(ms) OFF(ms)
Feature MEDIUM 500 500
DB_LED_OP_BLINKEN_LANGSAM)
Priority VERYFAST 50 50
DB_LED_OP_BLINKEN_SCHNELL )
Ringing DB_LED_OP_RING MEDIUM 500 500

Held DB_LED_OP_HELD WINK 450 50
Callfwd DB_LED_OP_CALL_FORWARD VERYFAST 50 50
Table 67 Settings required for U.S. Market
149.4.2 Ring Cadences

In order to receive the US ring cadences the following must be done.
• For digital devices the following command allows usage of hard coded ring
cadences for usage in the US.
CHANGE-ZAND:TYPE=ALLDATA2,USRINGTY=K;
• For anate stations the ring cadences are hard coded in the loadware. In order
to access this branch of the loadware the following ZAND command is used.
A31003-H3170-S103-6-7620, 02/2019
CHANGE-ZAND:TYPE=ALLDATA,CNTRYCD=K;
IMPORTANT: The programming of the ring cadences by PTIME will have no

affect when these parameter are set to K.
• In order for the appropriate rings to be given for the US features the following
ZAND command is used.
CHANGE-ZAND:TYPE=RNGTYPE,DSS=TRPR,FWD=TRPR,EXTCO=DBLR1,
NORM=SGLR1,RMDCALL=SGLR2,NVCE=SGLR2,MSGRCALL=PRR,MT=MTR,
CBK=TRPR,RECALL=TRPR,COMGROUP=SGLR2;
IMPORTANT: Even though the parameters above suggest single, double

and triple rings this is not true for the hardcoded US ringtypes. For example
DBLR2, SGLR2 are actually triple rings.
Ringtype Ring Cadence Pattern

on off
SGLR1 100 ms 3000 ms Repeat
SGLR2 250 ms 250 ms
250 ms 250 ms
1000 ms 2000 ms Repeat
DBLR1 250 ms 500 ms
DBLR2 250 ms 250 ms
250 ms 250 ms
250 ms Stop
TRPR 250 ms 250 ms
250 ms 250 ms
Table 68 U.S Ring Cadences
149.4.3 Tones on Display Phones:

• In order to receive tones on display phones the following ZAND parameter
must be set.
CHANGE-ZAND:TYPE=ALLDATA2,DISPTONE=YES;
A31003-H3170-S103-6-7620, 02/2019
149.4.3.1 Campon
• In order to receive the US campon beeps the following ZAND parameter must
be set.
CHANGE-ZAND:TYPE=ALLDATA2,CAMPON=YES;
• Additionally to control the interval between campon beeps the following
DTIM2 command is used.
CHANGE-DTIM2:TYPEDH=GEN,CMPOBEEP=60; /*60 = seconds between
beeps*/
149.4.3.2 Trunk Dial Tone
In the US there is no specific external dial tone. Instead a pause in the internal
dial tone after a trunk access code has been dialed.
• To control the duration of this pause the following DTIM2 command is used.
CHANGE-DTIM2:TYPEDH=GEN,PAUSDIAL=400; /* 400 = milliseconds
between beeps*/
• In order to have the tone set to the correct timeslot use the following
commands.
CHANGE-ZAND:TYPE=TONES,CP=SECDIALT,SIU=0; /* To give silence
during the pause */
149.4.3.3 Confirmation Tone
• In order to receive the US confirmation tone the following ZAND parameter

must be set.
CHANGE-ZAND:TYPE=ALLDATA2,CONFTONE=YES;
commands.
CHANGE-ZAND:TYPE=TONES,CP=REQDIALT,SIU=1;
CHANGE-ZAND:TYPE=TONES,CP=RECDIALT,SIU=1;
149.4.3.4 Announcements
In order to receive the announcements, “Please holds the line” , “ You have a
message” the following parameters must be set.
• This command insures that the correct loadware in included.

CHANGE-ZAND:TYPE=ALLDATA, SIUANN=D;
• These commands activate the announcements inside the system.
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
CHANGE-ZAND:TYPE=ALLDATA, ANATESIG=RA;
CHANGE-ZAND:TYPE=ALLDATA, HOLDTN=RA;
commands.
CHANGE-ZAND:TYPE=TONES,CP=HOLDLINE,SIU=16; /* For “Please
hold the line” */CHANGE-ZAND:TYPE=TONES,CP=HOLDLINE,SIU=21; /
* For “You have a message” */
149.4.3.5 Other loadware
• In order to get the correct loadware for the SIU, DTR, CONFC the following
command is needed.
CHANGE-ZAND:TYPE=TN,SIUC=K,DTR=K,RDS=0,CONFC=K;
• In order to get the correct operation of the U.S. conference feature the
following command is needed.
CHANGE-ZAND:TYPE=CONFC,CODE=ULAW;
149.5 Relevant AMOs

Language
ZAND KLINGELN d LED-Anzeige bei kommendem Ruf
RINGING e Led situation when a phone is ringing
BESASS d LED-Anzeige bei gehaltener Leitung
HELD e Led situation when a line is held
ANRUFUML d Auf der Leitungstaste, wenn Call Forward
aktiviert hat
CALLFWD e On line key when line has call forward active
PRIO d LED-Anzeige bei Dringlichkeitsanzeige
PRIORITY e Led situation when urgency is indicated
AUSGBTON d Ein/ausschalten von Tonen fuer Telefon mit
Ausgabe
DISPTONE e Act/deact Tones for display phones
CAMPON d Ein/ausschalten Campon beep
CAMPON e Act/deact Camp-on beeps
CPTON d Vermittlungstechnischer Ton
CP e Call processing tone
SIUTON d Zugeordneter Ton der SIU
SIU e Assigned siu tones
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

Language
KENNL d Linearisierungs- und Kompandierungskennlinien
bei der PCM-Kodierung/Dekodierung
CODE e Speech coding
CONFTONE d Ein/ausschalten beep Mechanism in DH
CONFTONE e Act/deact beep mechanism in DH
SIUSPKZ d Sprachkennzeichen für SIU-Texte und SWU-
Displaytexte (kein VPL) einstellen
SIUANN e Set options for SIU announcement texts
HALTETON d Ton im Haltezustand (intern und extern)
HOLDTN e Tone in hold state (internal and external)
ANATESIG d Quittungssignalisierung am ANATE
ANATESIG e Analog telephone user acknowledgement mode
SIU d Auswahl der länderspezifischen SIU-Tontabelle
SIUC e Selection of country-specific SIU tone table
HZE d Auswahl der länderspezifischen HZE-Tabelle
DTR e Selection of country-specific dial tone receiver
table
RDS d RDS Funktionalitaet
RDS e RDS Functionality
DTIM2 ARTDH d Verzweigungs-parameter
TYPEDH e Desired timer category
CMPOBEEP d Cycle time of the beep cycle
CMPOBEEP e Cycle time of the beep cycle
PAUSDIAL d Pause time between internal and second dial
tone
PAUSDIAL e Pause time between internal and second dial
tone
A31003-H3170-S103-6-7620, 02/2019
dss1user_en.fm
Feature Description
150 User-to-User Service

With this service a limited data quantity can be transparently transmitted to the
call partner. For this transmission the signaling channel (D channel) is used not
the B channel.
DSS1 terminal with

UUS1M classmark
and corresponding
Am on holiday
option table
UUS to an external station
UUS to external COT parameters for

station UUS1i/e and UUS3 must
be set at both PBXs;
UUS1 / US1E / UUS3 /
USBT / UUSC (optional)/
USCD (optional)
ECMA1/ECMA2/
PSS1V2
the COT parameter ETSC
E
should be set for

D
SS
transmission to external networks

1
ISDN
Am on holiday
The entire range of the UUS1 and

UUS3 services are only available for
DSS1 terminals (voice and data).

The "User-to-User Service 1 Implicit" and "User-to-User Service 3" services are
available for basic S0 access. Both conform to protocol requirements.
Applications for the UUS3 service are as yet unavailable. The UUS1 Implicit
service, however, is supported by most ISDN terminals. It is used to transmit brief
texts, e.g. "Am on holiday".
A31003-H3170-S103-6-7620, 02/2019
dss1user_en.fm
Service Information
Which type of User-to-User service (UUS) is used depends on the program or

terminal currently in use.
The following UUS are supported:
Service supported Effect on the connection Effect on the

application
UUS1i yes Although the remote system does not Loss of comfort,
support this service the connection is depending on the
established. application.
UUS1e no If this service is not supported by the No function
remote system the connection is not
established.
UUS2 no The OpenScape 4000 rejects this Connection is not
service. established
UUS3 yes Although the remote system does not Loss of comfort,
prefered support this service the connection is depending on the
established. application.
UUS3 yes If this service is not supported by the Connection is not
required remote system the connection is not established
established.
The UUS differentiates between ’preferred’ and ’required’. Connections requiring

’UUS preferred’ are usually established even though the service might not be
supported. 
On the other hand, connections requiring ’UUS required’ are not established if the
service is not available.
explicit
implicit
preferred required
UUS1 not implemented not implemented

UUS2 not applicable not implemented not implemented
UUS3

• The entire range of this service is only available for DSS1 terminals.
• As an option, the service can be redirected (only possible with DSS1

terminals).
• The service cannot be transferred (Call Transfer)
• For the UUS to function flawlessly, the parameters UUS1 / US1E / UUS3 /
USBT must be set in both PBXs.
A31003-H3170-S103-6-7620, 02/2019
dss1user_en.fm
• These parameters do not affect existing UUS services as used by CMI and
network-wide CHESE.
• The ETSC parameter should be set for transmission to those networks where
only messages in compliance with the ETSI protocol are sent.
• The following protocols allow the transmission of the entire User-to-USer

signaling:
Netside: EDSS1NET
User side: EDSGER / EDSSUI / ETSI
Tie: ECMA1 / ECMAV2 / PSS1V2.
• DPNSS1 does not support this feature.
• UUS should be allowed in the standard COT parameter sets.
150.3.1 AMO batch for DSS1 terminals

Configuration of UUS1 Implicit:
The calling party must have the classmark for UUS1 Implicit (UUS1IM). Only the
calling party can activate this service. The called party does not require the
classmark for UUS1 Implicit:
Provided, the COS number 6 is set for a DSS1 station:

CHA-COSSU:TYPE=COS,COS=6,AVCE=UUS1IM;
Configuration of UUS3 for DSS1:

The calling party must have the classmark for UUS3.
CHA-COSSU:TYPE=COS,COS=6,AVCE=UUS3;
Changes in the option table
IMPORTANT: Changes in the option table affect all terminals assigned to this
particular index number (IDX).
The data rate can also be administrated in option table 10:
• the burst parameter: maximum number of data blocks which can be

transmitted within 10 seconds
CHA-ZAND:TYPE=OPTTBL,IDX=10, BYTE=42, VALUEOPT=10;
A31003-H3170-S103-6-7620, 02/2019
dss1user_en.fm
• the incrementation parameter: every 10 seconds an internal counter

which controls the data rate is increased by the value assigned to this
parameter, until the counter is equal to the burst parameter.
CHA-ZAND:TYPE=OPTTBL,IDX=10, BYTE=43, VALUEOPT=08;
Bit 2 of byte 2 in option table 10 may not be set in the option table for DSS1
terminals. Bit 2 specifies whether the service will be activated protocol compliant
or proprietary for CMI and network-wide CHESE.
CHA-ZAND:TYPE=OPTTBL,IDX=10, BYTE=2, VALUEOPT=E1;
If a call is redirect, the User-to-User service request:
• can always be redirected (only DSS1 terminals)

CHA-ZAND:TYPE=ALLDATA2, UUS=DIV;
• can not be redirected
CHA-ZAND:TYPE=ALLDATA2, UUS=NODIV;
• can only be redirected if the redirecting party has the required UUS
classmark.
CHA-ZAND:TYPE=ALLDATA2, UUS=DIVSUB;
150.3.2 AMO batch for CMI and network-wide CHESE

CMI and network-wide CHESE may only use option table 6. Bit 2 in byte 2 must
be activated in this table.
CHA-ZAND:TYPE=OPTTBL,IDX=6, BYTE=2, VALUEOPT=E5;
Functional terminals used for the expansion connection must have COS
UUS1IM:
CHA-COSSU:TYPE=COS, COS=x, AVCE=UUS1IM;
The default data rate is 64 messages/10sec. maximum. In load cases, this
parameter can be administrated using optional table 6, bytes 42, 43.
150.3.3 AMO batch for networks
150.3.3.1 Configuration of UUS1 Implicit:
If the EDSS1NET and EDSS1NETR protocols are used, a UUS1 request is only
accepted if the COT parameter UUS1 is set.
Provided, the COT number 37 is configured for the corresponding trunk:

CHA-COT:37,COTADD,UUS1;
A31003-H3170-S103-6-7620, 02/2019
dss1user_en.fm
150.3.3.2 Configuration of UUS1 Explicit:
To transparently transmit an UUS1e request through the network the COT

parameter US1E must be set. If not, the request is rejected according to the
protocol.
Provided, the COT number 37 is set for the corresponding trunk:

CHA-COT:37,COTADD,US1E;
150.3.3.3 Configuration of UUS3:
AMO-COT:
A UUS3 request is only accepted if the COT parameter UUS3 is set. If not, the
request is rejected according to protocol.
Provided, the COT number 37 is set for the corresponding trunk:

CHA-COT:37,COTADD,UUS3;
The COT parameter ETSC can be used to define a virtual network limitation for
proprietary UU messages (e.g. CMI, NW-CHESE, ...). Where the COT parameter
ETSC is set, only UU information requested according to the ETSI protocol is
transmitted .
CHA-COT:37,COTADD,ETSC;
The service UUS3 can only be activated by the calling party ( A station). If the
COT parameter USBT is set, UUS3 can also be activated (network option) by the
called party (B station).
CHA-COT:37,COTADD,USBT;
With UUS3, a station can transmit a limited data quantity transparently to the call
partner. If the predefined data quantity is exceeded by one of the two parties and
if the COT parameter USCC is set, the transmitting party receives a Congestion
Control message. It informs the sending party that no further UU information will
be accepted or transmitted. After a timeout (network option) the limited
transmission of UU information is allowed again. This information is also signalled
with a Congestion Control message.
If the COT parameter USCC is not set, the check of the data quantity as described
above is prevented and an unlimited quantity of UU information can be
transmitted (important for proprietary features such as CMI, NW CHESE, ...).
CHA-COT:37,COTADD,USCC;
If the COT parameter USCD is set, a UUS request is not forwarded to the
forwarding destination.
CHA-COT:37,COTADD,USCD;
A31003-H3170-S103-6-7620, 02/2019
dss1user_en.fm
Relevant AMOs
AMO TDCSU:
A defined maximum number of UU information messages (UUSCCX ) per time
unit (UUS3T2) is available for each station with the UUS3 classmark. Regardless
of whether or not the stock was used, the remaining stock is increased by a
defined quantity (UUSCCY) after a certain time interval (UUS3T2), until the
original maximum number (UUSCCX) is reached. In this way, the user is provided
with a clearly defined bandwidth..
Provided, the corresponding trunk is a digital trunk with S2 interface (S2COD) in

slot 1-2-115-1 and B channel group 1 has been configured (default value
UUSCCX=16, UUSCCY=8):
CHA-TDCSU: DEV=S2COD, PEN=1-2-115-1, BCGR=1, UUSCCX=10;
CHA-TDCSU: DEV=S2COD, PEN=1-2-115-1, BCGR=1, UUSCCY= 5;
AMO CTIME:
The timer UUS3T1 defines the maximum waiting time of the network side for an
answer to a sent UUS request. If the timer expires before an answer is received,
the service is released according to protocol.
CHA-CTIME:TYPESWU=CPTIME,UUS3T1=10;
The timer UUS3T3 defines the maximum waiting time of the user side for an
answer to a sent UUS request. If the timer expires before an answer is received,
the service is released according to protocol.
Every station with UUS3 classmark is assigned a certain maximum number of UU
information messages per time unit which is defined by the timer UUS3T2.
150.4 Relevant AMOs

Language
COSSU UUS1IM d User-to-user 1 implizit
UUS1IM e User-to-user 1 implicit
COT ETSC d Nur ETSI UUS3 protokollkonforme Meldungen
werden zugelassen
ETSC e Only messages in compliance with ETSI UUS3
protocol are allowed
UUS1 d User-to-user implizit (kommend)
UUS1 e User-to-user implicit (incoming)
USBT d B-TLN kann bei Bedarf auch UUS3 Service
anfordern.
A31003-H3170-S103-6-7620, 02/2019
dss1user_en.fm
Relevant AMOs

Language
USBT e If necessary, the B station can request UUS3
service
US1E d User-to-user explizit (kommend)
US1E e User-to-user explicit (incoming)
UUS3 d User-to-user 3 (kommend)
UUS3 e User-to-user 3 (incoming)
UUSC e UUS3 limitation of the data quantity
USCD d Bei AUL wird die UUS3 nicht umgeleitet
(kommend)
USCD e With FWD, UUS3 is not forwarded (incoming)
CTIME UUS3T1 d Maximale Wartezeit auf eine
UUS3T1 e Maximum waiting time for an answer (network
side)
Zeiteinheit
UUS3T2 e Time unit for maximum messages per time unit
UUS3T3 d Maximale Wartezeit auf eine Antwort(Userseite)
UUS3T3 e Maximum waiting time for an answer (user side)
TDCSU UUSCCX d Max. Anzahl Meldungen pro Zeiteinheit (UU3T2)
UUSCCX e Maximum number of messages per time unit
(UUS3T2)
TDCSU UUSCCY d Anzahl von Meldungen, die pro Zeiteinheit
aufgestockt wird.
UUSCCY e Number of messages which is increased per time
unit (UU3T2) up to the maximum (UUSCCX)
ZAND UUS d DIV UUS Umlenkung erlaubt
NODIV Umlenkung verboten
DIVSUP Umlenkung abhängig von der
Berechtigung
UUS e DIV UUS forwarding allowed
NODIV forwarding not allowed
DIVSUP forwarding dependent on the COS
A31003-H3170-S103-6-7620, 02/2019
dss1user_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
ring_variable_en.fm
Feature Description
151 Variable Call Forwarding No Reply

Up to now it was only possible to define the ring time system wide. Now it is
possible to set the ring time station-specific.

This feature is supported with the following devices:
• optiPoint
• OpenStage
• Anates

ADD-ACTDA:TYPE=STN,STNO=37278,FEATCD=VARRING,RNGTIME=10;
The ring time in seconds can also set via the service menu (not valid fro Anate)
at the device itself:
Service Menue > Destinations > Call Forwarding > FWD-VAR-RNA-
BOTH > Ringing duration until forwarding
Enter the number of seconds and safe your new settings.
151.4 Relevant AMOs

Language
ACTDA LMACT=VARRING d Aktiviert das Leistzungsmerkmal für ein
bestimmtes Endgerät
FEATCD=VARRIN e Activates the feature for a specific device
G
RNGTIME d Rufdauer in Sekunden
mögliche Werte: 1-60
RNGTIME e Ring time in seconds
possible values: 1-60
A31003-H3170-S103-6-7620, 02/2019
ring_variable_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
witness_en.fm
Witness Facility
Feature Description
152 Witness Facility

Digital telephones offer the possibility of setting up a network-wide "witness"
connection during internal or external calls. The prerequisite for activating a
witness connection is that the user activating the facility is called directly. This
means it is not possible to activate the witness facility for a consultation call. 
The witness is connected without a notification tone. The ITR group’s witness
(analog telephone) can be dialed automatically by pressing the witness key. ITR
groups should be used to ensure that users have set a permitted ITR as the
witness facility. One witness station can be added per ITR group.
OpenScape 4000
ITR = X
Witness station
ITR = Z
ITR = X E.g. recording
device
other STN
ITR = Y
ITR Matrix
STN with witness
key X Y Z
X A A A A = allowed
Y A A A N= not allowed
Z A A A
Figure 121 Traffic relations for witness facility

• One witness station can be added per ITR group.
• The witness facility key can only be assigned with the AMO TAPRO.
A31003-H3170-S103-6-7620, 02/2019
witness_en.fm
Witness Facility
• The "witness" can only be an analog telephone.
IMPORTANT: The witness station must at least have restricted trunk access.
The call forwarding on no answer feature must not be activated for the
witness facility.

• Set up the ITR matrix (if not yet available) with:
CHA-VBZ:ITRSRC=<number>,ITRGR=<TYPE>,ITRDEST=<number_itr>;
• Set up a digital station if not yet available:
ADD-
SBCSU:STNO=<number_addon>,OPT=OPTI,CONN=DIR,DVCFIG=OPTISET,CO
S1=<number>,COS2=<number>,LCOSV1=<number>,LCOSV2=<number>,LCO
SD1=<number>,LCOSD2=<number>,ITR=<number_itr>;
• Assign the witness facility key (for example, key 12) for a station with:
CHANGE-TAPRO:STNO=<number_addon>,KY12=ADDON;
• Restrict the witness station to the CPS "consultation call" with:
ADD-WABE:CD=<number_witns>,CPS=8&9,DAR=STN;
• Configure an analog witness station with:
ADD-
SCSU:STNO=<number_witns>,DVCFIG=ANATE,ITR=<number_itr>,COS1=<
number>,COS2=<number>,LCOSV1=<number>,LCOSV2=<number>,LCOSD1=
<number>,LCOSD2=<number>,SPEC=WITNS;
• Assign a witness station to an ITRGR as follows:
ADD-VBZGR:GROUP=<number_itr>,TYPE=LSTNR,STNO=<number_lstnr>;
152.4 Relevant AMOs

Language
SCSU TLNNU d TEILNEHMER-RUFNUMMER
GERKON d GERAETE-KONSTELLATION EINES
TEILNEHMERS
ANATE = ANALOGES SPRACHGERAET
DVCFIG e DEVICE CONFIGURATION
ANATE = ANALOG VOICE TERMINAL
A31003-H3170-S103-6-7620, 02/2019
witness_en.fm
Witness Facility
Relevant AMOs

Language
SOND d SONDEREINRICHTUNGEN BEIM
TEILNEHMER
ZEUGE = TEILNEHMER MIT
ZEUGENANSCHLUSS
SPEC e SPECIAL FACILITY AT STATION
WITNS = STN/PORT FOR CONNECT. OF
TAPEREC. ETC. AS WITNESS
VBZ d VERKEHRSBEZIEHUNGSGRUPPE
ITR e INTERNAL TRAFFIC RESTRICTION
GROUP
TAPRO TLNNU d TEILNEHMERRUFNUMMER
TDxx d TASTENFUNKTION TASTE xx
z.B. xx = 12
KYxx e KEY FUNCTION FOR BUTTON xx
e.g. xx = 12
VKS d VERKEHRSSITUATION
CPS e CALL PROGRESS STATE
KZP d KENNZAHLPUNKT
TLN = Teilnehmer
STN = STATION
VBZ VBZUR d VERKEHRSBEZIEHUNGS-GRUPPE
URSPRUNG
ITRSCR e INTERNAL TRAFFIC RESTRICTION
GROUP,
SOURCE
VBZG d VERKEHRSBEZIEHUNG
ITRGR e INTERNAL TRAFFIC RESTRICTION
GROUP
VBZZL d VERKEHRSBEZIEHUNGS-GRUPPE ZIEL
ITRDEST e INTERNAL TRAFFIC RESTRICTION
GROUP,
DESTINATION
VBZGR GROUP d VERKEHRSBEZIEHUNGS/WABE-
GRUPPENNUMMER
GROUP e INTERNAL TRAFFIC RESTRICTION OR
DIAL PLAN GROUP
TLNNU d RUFNIUMMER
A31003-H3170-S103-6-7620, 02/2019
witness_en.fm
Witness Facility
Relevant AMOs

Language
TYP d EINTRAGSTYP,
VERZWEIGUNGSPARAMETER
ZEUGE = ZEUGE
TYPE e DESIRED HOTLINE/OFFHOOK RECALL
OPTION
LSTNR = LISTENER / WITNESS
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Attendant Console
Attendant Console
153 Attendant Console
153.1 Overview
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
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 QUEMODE=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 attendants.
The night options are given a neutral number created in the NAVAR AMO and
allocated in the ATNDGR as night option 1, 2 etc.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Feature Description
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 VFGKZ 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 software 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.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Comfort Attendant Console
The overflow position option, (required when all positions of an ATNDGR are
busy), is described 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.
IMPORTANT: Attendant consoles cannot be configured in hunting groups. 

In the case of systems without attendant console an ATND group must still be
configured, 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.
IMPORTANT: The central parameters for the attendant consoles can be found in
the TYPE=ATND branch of the ZAND AMO.
153.3 Comfort Attendant Console

The features are worldwide released to multiple queue (MQ) and parallel display
in addition to the double queue (DQ) for the windows attendant console.
153.3.1 Overview AC-WIN (DQ)

The feature "double queue" is the standard for the queue mode of arrangement
groups. This mode supports 2 spring queues, which submits incoming calls and
is taken to disconnected mode there as administered. All calls incoming with such
a AC group are shown to the attendant console according to the configuration.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Comfort Attendant Console
Calls waiting
in the queues
Active
Calls
Status
153.3.2 Overview AC-Win MQ

The feature Multiple Queues and Parallel Presentation provides a 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 alternative to the DQ
(Double Queue) mode.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Nodes without an Attendant Console
Calls waiting
in the queues
Active calls
Calls in
progress
Status
Valid Attendant types in these groups can be:
Attendant Group Queue Attendant type

Mode
DQ (Double Queue) AC4, AC-Win 4.x
MQ (Multiple Queue) AC-Win MQ 2.x
The feature can be used network-wide in a homogeneous OpenScape 4000 and

mixed OpenScape 4000/HiPath 4000/DX networks.
There are no changes to hardware required for this new feature the Multiple
Queue version of the AC-Win utilises the same hardware as the previous ACWin-
xx. The feature requires a different software package to be loaded on the PC.
153.4 Nodes without an Attendant Console

Ensure that an attendant group with a "STN" (station) or an empty variant night
switch option is assigned in nodes without ATNDs.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Nodes without an Attendant Console

• This requires no HW (AC)!

• 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;

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
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Usage - Examples
153.5 Usage - Examples
153.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 number 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 =<Attendant
Console type parameter : ACWIN / AC4>;
IMPORTANT: 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.
153.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>,....;
• Assign the attendant group in AMO VFGR
For each Attendant group it must be decided in which Queue mode the group
shall be operated.
Attendant groups with Double Queue mode (DQ) can consist of AC4 and
AC-Win 4.x Attendant types.
ADD-
VFGR:ATNDGR=<Atnd.Grp.number>,QUEMODE=DQ,ATNDNO=<number>,NOPT
1=<Night option number>,OPT=<Selected Night Option parameter
NOPTx on activation of Night mode :1...8 >;
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Usage - Examples
Attendant groups with Multiple Queues mode (MQ) can consist of AC-Win
MQ 2.x Attendant type only.
ADD-
VFGR:ATNDGR=<Atnd.Grp.number>,QUEMODE=MQ,ATNDNO=<number>,NOPT
1=<Night option number>,OPT=<Selected Night Option parameter
NOPTx on activation of Night mode :1...8 >;
IMPORTANT: 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>;
153.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 console.
• 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 allocated to the ITR group with the VBZGR AMO.
• Assign the same name for attendant intercept

AD-VBZGR:GROUP=<number>,TYPE=CUSNAME,NAME=<string>;
IMPORTANT: The stations assigned to the ITR groups can be interrogated with
the AMO 
SCSU/SBCSU.
153.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;
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Usage - Examples
• Delete attendant telephone number from the DPLN (if necessary)

DEL-WABE:TYPE=CD,CD=<key-num>,DAR=ATNDIND;
153.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;
153.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>;
153.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;
153.5.8 Internal Centralized Attendant Services

The internal centralized Attendant servcices group (CASINT) is assigned in the
home node. This function enables the entire range of attendant functions of an
ATNDGR to be transferred to another ATNDGR. If an attendant group takes on
the attendant terminal traffic of another ATNDGR 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 Centralized
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
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Usage - Examples
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>;
IMPORTANT: More than one night option can be assigned to a CASINT as

a destination.
• Assign an attendant group to a CASINT night option

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

Group
An external centralized attendant services group (CASEXT) is located in a
’foreign’ node. Several 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.
IMPORTANT: CASEXT configuration and functionality was only supported in

OpenScape 4000/HiPath 4000 homogenous networks, however it is also
possible to use the configuration to a none OpenScape 4000/HiPath 4000 desti-
nation. If the required classmarks are not present in the Connect message from
the partner, the centralized attendant feature modules will be left and the call
treated as a normal one. Any CASEXT configuration prior to these versions is not
supported as negative side effects will be experienced.
• Assign night options for the CASEXT

ADD-NAVAR:NOPTNO=number,TYPE=CASEXT,CD=number;
IMPORTANT: 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
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Function-Enhancements for the Attendant Queues
ATND access code of the attendant group in the destination system must be
entered. This code must lead to a "NETW" digit analysis result (DAR) in the
dial plan.
• Assign a night option to an ATNDGR

CHANGE-
VFGR:ATNDGR=number,{NOPT1...NTVA8},OPT=number,CQMAXF=number;
Relevant AMOs

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 zielteilnehmer
COD e control of diversion when calling target
station
ENACHTPR d prioritaet der einzelnachtschaltung
INIGHTPR e priority of individual night service
153.6 Function-Enhancements for the Attendant Queues

The priority assignment to calls in call queues of an AC group is improved.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
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.
153.6.1 Priority Calculation and Queue Assignment
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.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
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 OpenScape 4000
Answer Key Priority Level
priority number
Emergency call PNo1 PNo 1 L2 or L1 / S01..S12 1
PNo 2 L2 or L1 / S01..S12 7
Trunk PRI Local First call PNo 40
PNo 3 L2 or L1 / S01..S12 5
group number
1 1-48
2 1-48
3 1-48
4 1-48 PNo 47
PNo 48
L2 or L1 / S01..S12
L2 or L1 / S01..S12
3
4
5 1-48 CO-recall PNo16 ANSKEY PROLEV

• • Overflow CO-call PNo16
Combination of call Assignment of

• • priority numbers
types to one priority
• • number (AMO VFGR) with one priority
• • Any number of call and one answer
• • types can be assigned key,
510 1-48 to one priority number. (AMO VFGR).
Several priority
511 1-48
numbers can be
512 1-48 assigned to one
Combination of trunk groups
priority level.
to one priority number 1-48
(AMO BUEND). Any number
of trunk groups can be
PNo n = Priority number n = 1......48
assigned to the same L1 n = O-call with prio n = 1.........8
priority number. L2 n = AT-call with prio n = 1........8
S01.12 = Source keys on AC-Win MQ
CorNet-NQ
e.g.PNo16
If the COT parameter (PRIO) is set, the priority number

transmitted by CorNet is used. Up to 16 priority classes can
be transmitted. If the COT parameter is not set, the priority
number of the trunk group is used.
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 number of the originating node can be transmitted (can be administrated
in the destination node using COT parameter PRI).
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
With transmission via CorNet NQ, they also apply within a system network.
Transmitted via CorNet 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 OpenScape 4000/HiPath 4000 network. In transit nodes the
priority number is switched transparently through, subject to the COT parameter
PRI being 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.
The COT parameter PRI is an old parameter (transmission of the priority number
via CorNet-NQ in homogeneous OpenScape 4000/HiPath 4000 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 Attendants according to the FIFO principle. The longest waiting call is the
first transferred to a free station (AC Win or Night station).
• 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 an

OpenScape 4000. With transmission via CorNet-NQ, they also apply within a
system network.
• The priority number transmission via CorNet-NQ is only supported within a

homogeneous OpenScape 4000/HiPath 4000 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.
• 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

OpenScape 4000/HiPath 4000 networks.
– Original meaning: Priority establishment for prioritized trunk groups for

calls to the call queue. This meaning is no longer relevant
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
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 -- 47
TRANSFER
The following tables show the standard initialisation values for the various call
types and their priority levels
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
Table 69 Table 1-1 Basic initialisation DQ
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console

6-8 L2 8
11-48 L2 8
Table 69 Table 1-1 Basic initialisation DQ
Multiple Queues (MQ)

1 SQ01 3
2 SQ02 3
3-8 SQ012 8
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
46 SQ10 5
47 SQ11 3
48 SQ11 8
Table 70 Table 1-2 Basic Initialsation MQ
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;
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
• 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:
CHA-
2. for local first calls, assign the priority level 8 on answer key L1 for ATNDGR 0
and the priority 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:
CHA-
• 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;
ATNDGR 0:
CHA-
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 OpenScape 4000/HiPath 4000 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;
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
ATNDGR 1.
CHA-
5. For internal calls in an originating node assign the priority level 7 on answer
key L2 for ATNDGR 1 in the destination node (only possible in homogeneous
OpenScape 4000/HiPath 4000 networks via CorNet-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.
• Activate the overflow by entering an overflow ATNDGR using AMO VFGR

CHA-VFGR:ATNDGR=0,TYPE=GENERAL,OFLGR=1;
IMPORTANT: The parameter "OFLGR=*" deactivates the overflow for

this ATNDGR.
• Change the overflow timer

CHA-CTIME:TYPESWU=ATNDTIME,CQOFL=40;

Language
BUEND PRIONUM d Prioritätsnummer 1-16
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console

Language
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
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
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console

Language
UELGR d Überlaufgruppe
OFLGR e overflow attendant group
153.6.2 Priority Upgrade
Calls waiting longer are diverted after time to another Attendant group. This
behavior is administerable. 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.
• 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 priorized
stations, the priority numbers of the configured 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.
• 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>;
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Automatic Night Service
• Overflow to another Attendant group after timeout.

Calls waiting for a longer period of time in the call queue are transferred to
another Attendantgroup after timeout. This feature can be administrated
using AMO VFGR :
CHANGE-VFGR:ATNDGR=<number>,TYPE=GENERAL,OFLGR=<assigned
overflow attendant group>,
• The overflow timer can be set using AMO CTIME.
CHANGE-CTIME:TYPESWU=ATND,CQOFL=<5...240>;

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
153.7 Automatic Night Service

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.

• This feature works in different ways, dependant on the used group Queue
mode :
Attendant Group with Double Queue mode (DQ):
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Automatic Night Service
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
pre-sented 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.
• 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:

• 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;

Language
CTIME ATNDCALL d Zeitglied für den Attendant Call
ATNDCALL e Timer for Attendant Call
ZAND AUNA d Automatische Nachtschaltung
AUTNS e Automatic night switch
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Attendant Intercept

Language
VFGR AUNA d Automatische Nachtschaltung
AUTNS e Automatic night switch
153.8 Attendant Intercept

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.

• 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 console group to which the call is forwarded.
– If ITRN ist not set, the calling line’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 non-networked remote

system, the calling line’s ITR group is always used for selecting the attendant
console group to which the call is forwarded.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Attendant Intercept
Hint:
Before an ATNDGR can be deleted, and unless it is the only one in the system,
another ATNDGR 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;

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)
/* 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 */
0,DVCFIG=ANATE,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) */
/* 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 Typ: Ring Start with Loop Current Check . Dipfix-Switch:
• S1 = on \
• S2 = on > Message 1 on all lines
• S3 = on /
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Attendant Intercept
• S4 = off \
• S5 = on \
• S6 = off > Ring Start Mode on all lines
• S7 = on /
• S8 = on > separate ansage

Language
NOPTNO e NUMBER OF NIGHT SWITCHING
OPTION
RNR d PLATZKENNZAHL DER EXTERNEN
ZVFGR
CD e CODE FOR EXT. CENTRALIZED ATND
SERVICE
VFGRU d VF-GRUPPENNUMMER
ATNDGR e ATND GROUP NO.
FEASU LM d Leistungsmerkmal
VFGR VFGRU d NUMMER DER VPL - GRUPPE
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
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Extend Call to Paged User

Language
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
153.9 Extend Call to Paged User
153.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
A will be Held
Attendant can proceed with normal 

call handling
while A is
After the activation of
held
the join key the waiting
party B
“
is B calls attendant
connected to the paged Personal number
user
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console

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.

The Extend Call to Paged User feature can be used by the attendant to join a call
that is either held at theT,O or R (recall)sub-units or parked, with a paged user
who calls into the attendant P sub-unit.(Personal Key) The 2 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 utilised by the attendant for the following
scenarios
After a transfered 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).
153.9.3.1 Extend Call to Paged User feature invocation from

AC
The following description is applicable to:

AC4 on Upoe interface
There are 2 states that the incoming call can be in while the Attendant waits for
the response to the paged call, these being held at theT,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 interchangable.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
The attendant pages the desired extension and carries on with normal call
handling
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 wating call against the P in the display, in additiion 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 theT key. The two parties are now joined together and
released from the Attendant.The Attendant 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 keyand 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 2 partys are connected together and the calls are
released from the attendant ,where the display returns to normal.
153.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 AC.
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
theT, 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 keyboard, 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.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Remote Activation of Call Forwarding for Users at the Attendant Console
For parked calls, the attendant clicks the JOIN key in the AC-Win Buttons window
and then either 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.

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.
153.10 Remote Activation of Call Forwarding for Users at the Attendant

Console
153.10.1 Overview
Variable call forwarding (FWD) can be activated or deactivated for any station
(forwarding object) 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
(AFWDREM) and remote deactivation (DFWDREM) of call forwarding at the
attendant console with the AMO WABE.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Remote Activation of Call Forwarding for Users at the Attendant Console
In order to enable the remote activation and deactivation feature, you must
specify the COT parameter 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 between ATND and forwarding
object must be set up with LCR.

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.

• 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;

Language
COT COTPAR d PARAMETERWERTE FUER EINE COT
AUAT = PROGRAMMIERUNG DER
ANRUFUMLEITUNG 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
AFWDREM = ACT CALL FORWARDING
REMOTE/FOLLOW ME
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Attendant Control of Diversion
153.11 Attendant Control of Diversion
153.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 refered to as call forwarding immediate CFI)
Ring
AC-Win M Q Call Forward

Unconditional
A pplikatio n
Statistische Daten
Siemen s Bellavist a Telefon buch V1.0
Nam en:Liste
Name: OK
Vo rnam e: Ab brech en
A bteilung :
Ruf num mer:
Fax:
C:\
Prog ramm anag er
( immediate )
Step

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 overide 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 proir to calling a
station with call forward immediate set i.e. the STEP and RING keys do not
appear automatically and the attendant has know that the station has CFI set.
The feature works on different types of extensions, analog ,digital and functioal
devices are supported

The feature ’Control of Diversion’ controls CFB and CFU only, not CFNR (Call
ForwardingNo Reply).
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Attendant Control of Diversion
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 possible.
The feature works network wide with Realitis/DX over CorNet NQ orCorNet NQ/
DPNSS1.
The feature works for transit traffic with CorNet NQ .
For other digital or analogue trunks a control of diversion is not possible. The call
follows the diversion.

• 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 without 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 dialed 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.
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Displaying of the Source Dialling Number instead of Number of the Attendant Console

Language
ZAND AULSTEU d Kontrollierte Anruflenkung in der Anlage
aktiviert
COD e Control of diversion enabled for the system
VFGR AULSTEU d Kontrollierte Anrufumlenkung automatisch
setzen J/N
COD e Control of diversion set automaticaly Y/N
153.12 Displaying of the Source Dialling Number instead of Number of the

Attendant Console

An incomming call from a public ISDN network that is transfered by the attendant
in switch A to an busy extension in switch B provides the source dailing number
and not the number of the attendant for the called subscriber and in the call log
list.
153.12.2 Generation
CHA-ZANDE:TYPE=ALLDATA,SCALLOG=YES;

Language
ZANDE QNRRFLST d Quellenrufnummer in Anrufliste
SCALLOG e Source number in call log
A31003-H3170-S103-6-7620, 02/2019
ach4_en.fm
Attendant Console
Displaying of the Source Dialling Number instead of Number of the Attendant Console
A31003-H3170-S103-6-7620, 02/2019
attendant_light_en.fm
Attendant Light
Service Information
154 Attendant Light

Attendant Light offers customers (e.g. serving small offices) without central call
acceptance for incoming calls the option to receive and speed extend incoming
calls using a standard OpenStage 40 HFA or OpenStage 40 TDM phone. This
phone also has to support certain attendant features.
Figure 122 Attendant Light scenario

• Released with OpenScape 4000 V7 R1.
• Attendant Light is supported only for OpenStage 40 HFA and OpenStage 40

TDM.
• The Attendant Light device must support the following attendant features:
• Multiple incoming call handling: The existing OpenScape 4000 hunt

group solution for queuing and answering calls is used. The Attendant
Light device must be single user within a master or code hunt group.
Therefore, call distribution options of hunt groups have no impact to
Attendant Light because it is a single device in group.
The Attendant Light can be called via a special Attendant access code
which is configured over DAR=HUNT/DAR=STN in AMO WABE.
If the Attendant Light is already busy with a call, all next incoming calls
are queued. The call with the highest priority in the queue is assigned to
the Attendant Light when it becomes available again. The priority order
within the queue is emergency call, CO call, tie call, internal call.
The call queue capacity can be set variable.
Feature Interactions will be the same as for hunt group (AMO SA).
A31003-H3170-S103-6-7620, 02/2019
Attendant Light
Service Information
• BLF key module support with a maximum of 90 direct call keys to

observe the status of the programmed subscribers.
IMPORTANT: Using the BLF module on the Attendant Light excludes the
usage of any other key module.
Using the Direct station selection keys on the busy lamp field the busy
condition of the destination is displayed via a LED. If the destination is
called despite being busy, call waiting is activated and the destination is
called when no longer busy (only if call waiting is activated. If call waiting
is not activated “Not Possible” will be displayed).
IMPORTANT: Direct call keys cannot represent network wide parties.
• Speed Extend with dialing a destination number or pressing a direct call

key on the busy lamp field module while being in talk state.
Speed Extending uses the operator if he does not want to announce the
call prior to extending it to the destination station.
In connection state with the partner (caller or called party) the operator
dials the destination number of extension B or press DSS key without
manually invocation of the consultation function.
After end of dial, the A party is automatically transferred to the free
destination and the Attendant Light device is released.
Transfer busy is used when extension B is busy (only if call waiting is
activated. If call waiting is not activated “Not Possible” will be displayed).
IMPORTANT: Speed extending and dialling DTMF digits excludes each

other.
IMPORTANT: Other specific Attendant Console / AC-Win and Attendant

Group features as night services, call retrieval, control of diversion, call inter-
ception etc. are not supported by Attendant Light.
154.1.2 Interworking with other features

• Attendant Light device cannot act as ACD agent (attribute AGENT) and/or
ACD supervisor (attribute SUPER) (blocked by AMO SDAT).
• Chief/Secretary
A31003-H3170-S103-6-7620, 02/2019
Attendant Light
The Attendant Light device cannot be a TEAM/CHESE member (attributes

TEAMSECR and TEAMEXEC) (blocked by AMO SDAT).
• Recall
Works as recall after Single Step Transfer.
• Hunt group
Hunt group search type linear (LIN) and cyclic (ZYK) are supported.
• Using the extension code number 0

In the case of customers for whom a further extension code number 0 is to
route from the CO to the Attendant Light, in addition to the hunt group number
for the Attendant Light, the Attendant Light can be configured as a "none"
night service destination of the attendant console group (VFGR) 0.
ADD-WABE:CD=0,CPS=6,DAR=ATNDDID;
ADD-VFGKZ:TYPE=ATNDGR,CD=0,ATNDGR=0;
ADD-NAVAR:NOPTNO=8,TYPE=STN,STNO=<No. of attendant light>;
• Trunk night service destination
The ACLight can be configured as the trunk night service destination for
ACLight in branch networks at the respective trunk access of the branches
(see also Chapter 160, “Trunk Night Service”.
154.1.3 Restrictions
• The Attendant Light is implemented with the hunt group feature. AMO VFGR,
AMO VFGKZ and AMO NAVAR are not used.
Exception: Use of the Attendant Light as a night service destination (see
Section 154.1.2, “Interworking with other features” > Using the extension
code number 0).
• The feature to be configured in AMO SDAT

(TYPE=ATTRIBUTE,AATTR=ACLIGHT) cannot be displayed in OpenScape
4000 V7 R1 in AMO SBCSU (DISPLAY-SBCSU).
This is possible as of OpenScape 4000 V7 R2.
154.2.1 Master Hunt Group

Subscriber number and hunt group number are the same. Subscriber can only be
called as Attendant Light with 900.
A31003-H3170-S103-6-7620, 02/2019
Attendant Light
• Configure OpenStage device with busy lamp filed

0,DVCFIG=OPTIP500,TSI=1,COS1=23,COS2=9,LCOSV1=1,LCOSV2=1,LCOS
D1=2,LCOSD2=2,DPLN=0,ITR=0,SSTNO=N,COSX=0,SPDI=10,SPDC1=0,IDC
R=N,REP=0,STD=56,SECR=N,INS=Y,ALARMNO=0,RCBKB=N,RCBKNA=N,DSST
NA=N,DSSTNB=Y,DIGNODIS=N,CBKBMAX=5,HEADSET=N,HSKEY=NORMAL,CBK
NAMB=Y,TEXTSEL=GERMAN,HMUSIC=0,COMGRP=0,BLF=Y;
• Configure key layout for OpenStage device
• DSS key administration:
ADD-ZIEL:TYPE=DSS,SRCNO=900,KYNO=1,DESTNOD=25501,DEV=AD1;
• Configure Attendant Light device as a master in hunt group for getting a call
queue:
ADD-WABE:CD=900,DAR=STN;
ADD-
SA:TYP=TLN,RNR=900,VBZ=0,ART=LIN,ANOKAP=20,NAME="ATTENDANT
LIGHT",VERLNEXT=NEIN,ANZART=SA;
• Configure device as Attendant Light device
CHANGE-SDAT:STNO=900,TYPE=ATTRIBUT,AATTR=ACLIGHT;
154.2.2 Code Hunt Group

Subscriber number and hunt group number are different. Subscriber can be
called as Attendant Light with 900 and as subscriber with 25502 (without
attendant queue).
• Configure OpenStage device with busy lamp filed

0,DVCFIG=OPTIP500,TSI=1,COS1=23,COS2=9,LCOSV1=1,LCOSV2=1,LCOS
D1=2,LCOSD2=2,DPLN=0,ITR=0,SSTNO=N,COSX=0,SPDI=10,SPDC1=0,IDC
R=N,REP=0,STD=56,SECR=N,INS=Y,ALARMNO=0,RCBKB=N,RCBKNA=N,DSST
NA=N,DSSTNB=Y,DIGNODIS=N,CBKBMAX=5,HEADSET=N,HSKEY=NORMAL,CBK
NAMB=Y,TEXTSEL=GERMAN,HMUSIC=0,COMGRP=0,BLF=Y;
• Configure key layout for OpenStage device
• DSS key administration:
ADD-ZIEL:TYPE=DSS,SRCNO=22502,KYNO=1,DESTNOD=25501,DEV=AD1;
• Configure Attendant Light device as a master in hunt group for getting a call
queue:
ADD-WABE:CD=900,DAR=HUNT;
A31003-H3170-S103-6-7620, 02/2019
Attendant Light
Relevant AMOs
ADD-
SA:TYPE=VCE,CD=900,ITR=0,STNO=25502,STYPE=LIN,CQMAX=20,NAME="
ACLIGHT",LVAFTEXT=N,LSTMBOFF=Y,DISPTYPE=HT;
• Configure device as Attendant Light device
CHANGE-SDAT:STNO=25502,TYPE=ATTRIBUT,AATTR=ACLIGHT;
154.2.3 Configure key layout for busy lamp field

CHANGE-
TAPRO:STD=65,DIGTYP=OST40BLF,KY09=VACANT,KY10=VACANT,KY11=VACANT
,KY12=VACANT,KY13=VACANT,KY14=DSS,INFO="DR";
CHANGE-
TAPRO:STD=65,DIGTYP=OPTIA1,KY01=DSS,KY02=DSS,KY03=DSS,KY04=DSS,K
Y05=DSS,KY06=DSS,KY07=DSS,KY08=DSS,KY09=DSS,KY10=DSS,KY11=DSS,KY
12=DSS,KY13=DSS,KY14=DSS,KY15=DSS,KY16=DSS,KY17=DSS,KY18=DSS;
CHANGE-
CHANGE-
CHANGE-
CHANGE-
154.3 Relevant AMOs

Language
SDAT EMERK=ACLIGHT de Gerät als Attendant Light konfigurieren
AATTR=ACLIGHT e Configure device as Attendant Light
SA TYP=SPR d Sammelanschluss des Typs “Sprache”
TYPE=VCE e Hunt group type “Voice”
RNR d Rufnummer des Sammelanschlusses
CD Hunt group access code
ART d Suchart des Sammelanschlusses (linear
oder zyklisch)
STYPE e Search type of hunt group (linear or cyclic)
A31003-H3170-S103-6-7620, 02/2019
Attendant Light
Relevant AMOs

Language
ANOKAP d Anrufordnerkapzität
CQMAX e Call ordering/queuing capacity
SBCSU TLNNU de Rufnummer des Attendant Light
Teilnehmers
STNO e Number of the Attendant Light subscriber
ART=OPTI de Hauptrufnummer des OpenStage-
Endgerätes
OPT=OPTI e Configure main number of OpenStage
BLF=JA d Belegtlampenfeld (optional)
BLF=YES e Busy lamp field (optional)
TAPRO SNU=65 d Tasten-Layout 65
STD=65 e Key layout 65
TDxx=DR d Direktruftaste konfigurieren
KYxx=DSS e Configure direct station selection key
ZIEL QLRUFNU d Quellenrufnummer
SRCNO e Source number
TASNU d Tastennummer
KYNO Key number
DZLRUFNU d Zielrufnummer für Direktruf
DESTNOD e Destination number for direct station
selection
A31003-H3170-S103-6-7620, 02/2019
cr_en.fm
Call Retrieval
Feature Description
155 Call Retrieval

The Call Retrieval feature can be used on an Attendant Console to recover the
last call, that the operator has transferred to an extension on behalf of an
incoming call (local or remote)
Quick handling of caller or

consultation
call AC-Win M Q
Applikation
Statistische Daten
Siemens Bellavista Telefonbuch V1.0
Namen:Liste
Name: OK
Vorname: Abbrechen
Abteilung:
Rufnummer:
Fax:
C:\
Programmanager
Wrong destination
The attendant
has only to activate the
call retrieval key AC-Win M Q
Applikation
Statistische Daten
Namen:Liste
Name: OK
Vorname: Abbrechen
Abteilung:
Rufnummer:
Fax:
C:\
Programmanager
Wrong destination
call
AC-Win M Q The attendant gets the call

call Applikation
Statistische Daten
Name: OK
Namen:Liste
back and can proceed in
order to direct it to the
Vorname: Abbrechen
Abteilung:
Rufnummer:
Fax:
C:\
Programmanager
correct destination

This feature is released for operators using an ACWin (MQ) console. It can be
used network wide in an homogeneous OpenScape 4000/HiPath 4000 and
mixed OpenScape 4000/HiPath 4000 /DX networks. Only the last transfered call
can be retreieved

An internal or external extension A (any device type), who was requesting a call
service from the operator, can be retrieved by the operator, if the operator has
prior transferred the extension A to
A31003-H3170-S103-6-7620, 02/2019
cr_en.fm
Call Retrieval
• An alerting internal or external extension B and extension B has not answered

yet
• An alerting internal or external extension B with activated CFNR feature and

the call was forwarded to extension C and extension C has not answered yet
• A hunt/distribution group and no group member has answered yet
• A paging device and the paged user has not answered yet
• An ACD group and no agent or supervisor has answered yet
• An undialed CO trunk line and the remote CO extension has not answered yet
• A busy internal or external extension B (w/o camp-on)
• An alerting or busy internal or external extension B and the operator has

provided incoming call service to another extension C but has not transferred
extension C to somewhere else
An internal or external extension A (any device type), who was requesting a call
service from the operator, can not be retrieved by the operator, if the operator has
prior transferred the extension A to
• An internal or external extension B in talk state
• An alerting internal or external extension B and extension B has answered the

call after the transfer
• An alerting or busy internal or external extension B and the call was already
released
• An alerting or busy internal or external extension B and a recall is queued to

the operator from extension B due to timer expiration
• An internal or external extension B and extension B has parked the call to

another internal or external extension C
• an alerting or busy internal or external extension B and all loop keys on the
ACWin (MQ) console are busy
• Voicemail server

• The Call Retrieval feature can be activated by the following command:
CHANGE-ZAND:TYPE=ATND,CALLRETR=YES;
• The Call Retrieval feature can be deactivated by the following command:
CHANGE-ZAND:TYPE=ATND,CALLRETR=NO;
A31003-H3170-S103-6-7620, 02/2019
cr_en.fm
Call Retrieval
Relevant AMOs
155.4 Relevant AMOs

Language
ZAND RUFRUECK d Gesprächsrückholung in der Anlage aktiviert
CALLRETR e Call retrieval set for the system
A31003-H3170-S103-6-7620, 02/2019
cr_en.fm
Call Retrieval
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
codeca_en.fm
156 Code Calling System Basic

The CC (code calling/paging system) is connected to the system via the TMOM
module. For the paging input, several circuits can be assigned (except for MEET-
ME mode).
Depending on the code calling/paging equipment, the following operating modes

are possible:
1. DISPLAY: station number of the paging party is displayed
2. VOICE ANNOUNCEMENT: talking facility to the paged party
3. MEET-ME: the paged party answers with an individual answering code and is
switched to the paging party by the code calling equipment. 
For this operating mode, a special answering circuit (station line) must be
configured for the code calling equipment with the AMO SSC. It is assigned
a special administration code (CCNO), which is not entered in the DPLN. If
several paging systems are installed, each one must be assigned a special
answering circuit for MEET-ME operation.
4. MIXED MODE WITH CODE DIGIT: the operating mode (DISPLAY, VOICE,
MEET-ME) or the type of code call (URGENT or NORMAL) is determined by
the user, who dials a specific code ditit after the paged party’s number.
5. TRANSPARENT MODE: the paged party’s number need not be entered in

the DPLN as a station number; it is transparently dialled through to the code
calling system as a B-block. This mode is possible in conjunction with all
operating modes mentioned above.
A31003-H3170-S103-6-7620, 02/2019
codeca_en.fm
CC in DISPLAY OPERATION
OpenScape
4000
S
PSE
TLN
S = Paging input
M = Answering input (special
answering circuit on SLMA)
Figure 123 PSE configuration with Meet-me conference
156.1 CC in DISPLAY OPERATION

• Add the paging codes in the DPLN
AD-WABE:CD=key-num,DAR=CCSN;
• Configure the TMOM module
• Add trunk group
AD-BUEND:NO=number;
AD-COT:PAR=NTON;
• Assign a class of parameter
AD-COP:PAR=DTMF&SACK&LSUP&PDP2&IDP1&DTM1;
Parameter CCR depends on the type of code calling system! 
Value EOD can only be assigned with ESPA interface!
• Add a line circuit

AD-TSCSU:COTNO=number,TGRP=number,DEV=CC,COPNO=number, *)
*) for AMO TSCSU, the parameters must be declared as follows:
A31003-H3170-S103-6-7620, 02/2019
codeca_en.fm
CC in VOICE ANNOUNCEMENT Operation
WIRES = depending on the system, 2, 3 or 4 wires

SUPV = SUPV1
ACKT = SZACK2
STADIAL = STADIAL1
ABLK = Y (paging party’s station number is transmitted)
STNOLEN = 0 (station number = paging number)
Assign a route for the code calling system
AD-RICHT:TYPE=CD,CD=key-num,CPS=1&2&3&4&5&6&7&8&9,SVC=VCE,
TGRP1=number;
IMPORTANT: CPS 6 (incoming CO trunk) is not assigned as paging via the

public network is not provided. The CPSs 10&11&12 are only required for inter-
PABX traffic.
156.2 CC in VOICE ANNOUNCEMENT Operation

Same as for DISPLAY OPERATION, except that parameter ABLK=N (NO) must
be declared in AMO TSCSU.
156.3 CC in MEET-ME Operation

• Assign paging and answer codes
AD-WABE:CD=key-num,DAR=CCSN; 
AD-WABE:CD=key-num,DAR=CCANS;
• Assign trunk group, class of trunk, class of parameter and trunk as for
DISPLAY OPERATION, with the following differences:
AMO COP: value CCM must be added to values for PAR 
AMO TSCSU: ABLK = N
IMPORTANT: CPS 6 (incoming CO trunk) is not assigned as paging via the

public network is not provided. The CPSs 10&11&12 are only required for inter-
PABX traffic.
• Assign answering line circuit on SLMA

AD-SSC:TYPE=CC,CCNO=number,ITR=number;
• Assign a route for the code calling equipment
A31003-H3170-S103-6-7620, 02/2019
codeca_en.fm
Code Calling in MIXED MODE Operation with CODE DIGIT
AD-RICHT:TYPE=CD,CD=key-num,RTECD=number,CPS=1&2&3&4&5&8&9,
SVC=VCE,CCNO= number;
The CPSs 10&11&12 are only required for inter-PABX traffic.
CD = Code calling (paging) code

RTECD = Answer code
CCNO = Administration number for special answering circuit
156.4 Code Calling in MIXED MODE Operation with CODE DIGIT

• The code digits are assigned in the DPLN according to the operating modes
and paging modes of the code calling system.
CCDIS Code digit for DISPLAY OPERATION

CCMEETME " " MEET-ME
CCITN " " DISPLAY (overwrite)
CCVCE " " VOICE ANNOUNCEMENT
CCSURG " " URGENT PAGING
CCS " " NORMAL PAGING
In addition, the digit analysis result CCSCD (code calling with code digit) must
be assigned in the DPLN instead of CCSN. 
If MEET-ME operation is possible, a code must also be assigned for the digit
analysis result CCANS.
• Configure the trunk module and trunk group, assign the class of trunk and
class of parameter and configure the trunk circuit as for DISPLAY
OPERATION.
– In the case of MEET-ME operation with code digit, the value CCM must
be specified for the parameter PAR in the COP command.
– In the case of DISPLAY OPERATION (CCDIS and CCITN), the parameter

ABLK=Y must be declared in the TSCSU command.
• In addition, for MEET-ME operation with code digit, the special answering
circuit must also be configured (AMO SSC), as well as the routes for the code
calling and answering codes (see Section 156.3, “CC in MEET-ME
Operation”).
156.5 Code Calling in TRANSPARENT MODE Operation

The transparent mode is possible for all types of operation, and is set by declaring
the parameter STNOLEN in the TSCSU command.
A31003-H3170-S103-6-7620, 02/2019
codeca_en.fm
Code Calling in TRANSPARENT MODE Operation
STNOLEN =0 means no transparent mode; the recipient’s address must be

assigned in the DPLN.
STNOLEN = 1-20 means transparent mode will be used, and defines the length of
the code to be transmitted to the CC (B-blocks).
The code length can either be fixed or variable, depending on
the ENDRAUT parameter (in AMO ZAND:TYPE=CCM):
ENDRAUT = NO: fixed length
ENDRAUT = YES: variable length
STNOLEN defines the maximum length. Terminate shorter
codes with ‘#’. 
En-bloc dialing (number redial, destination keys, key module,
etc.) is not possible, if mixed mode with code digit Section 156.4,
“Code Calling in MIXED MODE Operation with CODE DIGIT” is
used.
A31003-H3170-S103-6-7620, 02/2019
codeca_en.fm
Code Calling in TRANSPARENT MODE Operation
A31003-H3170-S103-6-7620, 02/2019
navar_en_cm_en.fm
Feature Description
157 General Night Switching Options

The system renders a range of night switching options available, which can be
administrated in the system and are identifiable through their option number. Is is
possible to assign one attendant group (ATNDGR) to as many as eight of these
night switching options (NOPTNOs) respectively. Which of these night switching
options handles the representation of the ATNDGR in the night service can then
be specified on an individual basis at an attendant console (ATND) of the
ATNDGR.
In night service, the attendant group (ATNDGR) can be represented by a night
switching option (NOPT). All calls to the attendant group (ATNDGR) are signalled
at a free station assigned to this night switching option. The assignment of the
stations (STN) to the night switching options can be administrated in the system
(AMO NAVAR).
• Universal Answering
Options of this nature comprise precisely one station, which is configured
especially for "Universal Answering".
• Station Option
Options of this nature comprise up to 10 configured extensions.
(Seizure takes place in cyclic form.)
• Internal Centralized ATNDGR Option

An option of this nature comprises a centralized ATNDGR within the switch
and is 
identified via its ATND group number. An internal centralized ATNDGR can
only be assigned to one night switching option. However, this centralized
ATNDGR need not yet be configured in an attendant group, i.e. the existence
of the ATNDGR is not checked.
• External Centralized ATNDGR Option

An option of this nature comprises a ATND group within the network
and is identified via the code for the centralized ATND service and the
destination number of the switch.
An external centralized ATND service can only be assigned to one night
option. However, neither the station access code nor the destination number
need be configured.
A31003-H3170-S103-6-7620, 02/2019
navar_en_cm_en.fm
Service Information

• Normally, a recall remains at the night service option which originally
connected the call, and does not follow a call forwarding on no answer which
may have taken place.
NOTE: Call forwarding on no answer (CFNA) to the night switching option takes
place if the RECALL FROM HOLD NIGHT STATION is activated in the central
system data and if a call forwarding destination is defined.
Via AMOs or ComWin:
Enter the parameter RENSFWD= yes of AMO ZAND’s DATEN3 branch and
configure a call forwarding destination by entering parameter UAERT=CFNR of
AMO ZIEL’s FWD branch.
• Call forwarding on busy (CFB) is not supported for night switching options.
• Recall to a night switching option which is a master hunting group does not
follow the hunting group.

• Assign the stations for possible night switching option(s) as follows:
Configuration Management > Port > Station Port.

A port for universal night answer however in the menu branch:
Configuration Management --> Port -->Special Station Port.
Depending on the desired night station:

ADD-SBCSU: Assign night station or
ADD-SCSU: Assign night station
ADD-SSC: Assign port for universal answering
• Assign the possible night switching option as follows:
A dummy option can only be administrated via the expert mode.

Expert Mode > ComWin > Open ... <IP> via AMO (see AMO command).
Further options, such as night stations and universal night answer can
be configured via Configuration Management > Groups > Night
Switching options.
A31003-H3170-S103-6-7620, 02/2019
navar_en_cm_en.fm
Expand a Night Option
Depending on relevant night switching option types:

ADD-NAVAR:NOPTNO=number,TYPE=L; (dummy option) 
ADD-NAVAR:NOPTNO=number,TYPE=STN,STNO=number;
(station) 
ADD-NAVAR:NOPTNO=number,TYPE=GENANS,GENANSNO=num;
(universal answering) 
ADD-
NAVAR:NOPTNO=number,TYPE=CASINT,ATNDGR=num;(interna
l centralized ATND service) 
ADD-
NAVAR:NOPTNO=number,TYPE=CASEXT,CD=number;(external
centralized ATND service)
157.4 Expand a Night Option

Only possible for night stations (STN). All other options cannot be expanded.
• A night station is added as follows:
Configuration Management --> Groups --> Night Switching Options,

Night Stations tab. Enter the number of night switching options to be
expanded and click the Search button. Click Add entry (right icon) and
enter the new call number in the new field. 
(This procedure must be repeated for each call number).
CHA-
NAVAR:NOPTNO=<navarnu>,FUNCT=ADD,TYPE=STN,STNO=<nu
mber>;
157.5 Reduce a Night Option

Only possible for night stations (STN). All other options must be completely
removed.
• A night station is deleted as follows:

Night Stations tab. Enter the call number of the extension to be deleted
and click the Search button. Now highlight the extension to be deleted
(right icon) and save.
Via SNTN number specification:
CHA-
NAVAR:NOPTNO=<number>,FUNCT=DEL,TYPE=STN,STNO=<tln_
number>;
A31003-H3170-S103-6-7620, 02/2019
navar_en_cm_en.fm
Delete a Night Option
157.6 Delete a Night Option

• The assignment to an ATND group is deleted as follows
Deletion can only be administrated via the expert mode.

Expert mode --> ComWin --> Open ...< IP> via AMO (see AMO
command).
Depending on the required option number:

CHA-VFGR:ATNDGR=<number>,{NOPT1=0,....,NOPT8=0};
• An existing night switching option in the system is deleted as follows:

Night Stations tab. Enter the number of the night switching options to be
deleted, click the Search button and then the Delete button.
Via night switching option number:

DEL-NAVAR:NOPTNO=<number>;
157.7 Relevant AMOs

Language
NOPTNO e NUMBER OF NIGHT SWITCHING OPTION
RNR d PLATZKENNZAHL DER EXTERNEN ZVFGR
CD e CODE FOR EXT. CENTRALIZED ATND
SERVICE
VFGRU d VF-GRUPPENNUMMER
ATNDGR e ATND GROUP NO.
VFGR VFGRU d NUMMER DER
VERMITTLUNGSFERNSPRECHER - GRUPPE
NTVAx d DER NACHTVARIANTE x ZUGEORDNETE
VARIANTE
(x=1-8)
A31003-H3170-S103-6-7620, 02/2019
navar_en_cm_en.fm
Relevant AMOs

Language
NOPTx e DEVICE(S) ASSIGNED TO NIGHT OPTION x
(x=1-8)
ZAND RUNSUML d Ein/ausschalten
'Wiederanruf des gehaltenen Teilnehmers'
RENSFWD e Act/deact system option 'recall from hold/night
station'
A31003-H3170-S103-6-7620, 02/2019
navar_en_cm_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
158 Multiple Code Calling System CCM

The multiple code calling equipment (CCM) is connected to the system via the
TMOM module. One circuit on the TMOM must be configured per code pair
(normal and urgent code calling). Up to 15 code calling jobs can be entered via
this circuit.
In the Meet-Me mode, the connection to the paging party is set up by the
OpenScape 4000; unlike single-call paging, multiple paging does not have a
special answering circuit.
If the 15 paging jobs are not sufficient, another TMOM circuit must be assigned
to the CCM for a further code pair. In this case, the paged parties are assigned to
one of the two code calling codes!
One code for normal code calling (CCMS) and one code for urgent code calling
(CCMSURG) should always be set up. In the Meet-Me mode, the answering code
(CCMANS) must be added.
Unlike single-call code calling, multiple code calling equipment also uses CO
trunks for paging.
Multiple code calling can be set up in the following modes:
1. DISPLAY operation (call number of calling party is shown on receiver display)
2. Meet-Me
In addition, the following features can be configured for the multiple code-calling
system:
1. Meet-Me operation with display
2. Display sequence of meet-me number and calling party number can be

reversed
3. Calling party’s number can be displayed left-justified or right-justified; display

is filled or truncated accordingly
4. Block separator characters and end-of-block characters can be defined
5. CCM with code conversion
6. Parallel ringing of exchange calls when FWD/FNANS activated to CCM in

Meet-Me operation
7. Priority signalling of urgent exchange calls for CCM in Meet-Me operation
8. Recorded announcements for CCM in Meet-Me operation
9. Multiple code calling of the same paging number
10. Suffix dialling to CCM when busy
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
CCM in Display Operation
11. Paging with on-hook handset internally and throughout network
158.1 CCM in Display Operation

In this mode it is possible to answer a paging Digite or Anate which pages when
in consultation hold. To answer the station must dial the displayed station number.
• Add the code calling codes in the DPLN

AD-WABE:CD=key-num,DAR=CCMS; 
AD-WABE:CD=key-num,DAR=CCMSURG;
• Add the configuration data for the TMOM
• Assign the trunk group
AD-BUEND:NO=1;
AD-COT:PAR=NTON;
• Add the class of parameter
AD-COP:PAR=DTMF&SACK&BR64&LSUP&PVWZ&IDP1&DTM3;
Parameter CCR, if code calling release after every call is required (no
queuing). 
Parameter EOD only with code-calling systems with "Call accpeted" /
"Absence" signalling.
• Add the trunk circuit parameters

AD-TSCSU:COTNO=number,TGRP=number,DEV=CCM, *)
*) in the TSCSU command, the parameters must be declared as follows:
WIRES = 2,3,4 or 6 wires, depending on code calling system

SUPV = SUPV1
ACKT = SZACK2
STADIAL = STADIAL1
STNOLEN = 0
TBT = CCMEOD1
EOD = CCMEOD2
SRCHORD = 15
SRCHATT = 1
OPTYPE = DIS&BLKSEP&BLKEND&NOICPTRA 
(or other parameters, refer to AMO description)
WAIT = NOTRDY1
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
CCM in Meet-me Operation
SRCHCANT = only if DELANS has been specified with parameter OPTYPE

(see CTIME timers for CCM)
WAITT = Default value (see CTIME timers for CCM)
CDGT = Code digits from 0 to 9, with 
1st digit for normal code calling and
2nd digit for urgent code calling.
The digits must be specified as required by the code calling
system.
CONV = Conversion of dialled number to CC code
For CCM in DISPLAY operation, the TSCSU parameter MABLK must be set
to the number of digits of the calling party’s number which are to be
displayed, i.e. the parameter must be set to a value greater than ’0’ (see also
CCM in Meet-Me operation with Display).
• Assign route to multiple code calling system

AD-RICHT:TYPE=CD,CD=key-num,RTECD=key-
num,SVC=VCE,TGRP1=number;
• Delete code calling job after going on-hook
CHA-ZAND:TYPE=CCM,DEL=YES;
• Suffix dialling if busy
CHA-ZAND:TYPE=CCM,POSTDBSY=YES;
NOTE: The node number assigned to the CCM (NNO parameter of TACSU
AMO) is evaluated by the KNMAT AMO for display number modification for
DISPLAY operation or Meet-Me operation with display. This number must be a
unique number (see also Display Number Modification with AMO KNMAT).
158.2 CCM in Meet-me Operation

• Assign codes for normal code calling, urgent code calling and answering in
the DPLN
AD-WABE:CD=key-num,DAR=CCMS; 
AD-WABE:CD=key-num,DAR=CCMSURG; 
AD-WABE:CD=key-num,DAR=CCMANS;
• Add configuration data for the TMOM module
• Assign a trunk group
AD-BUEND:NO=number;
• The COT and COP parameters are entered as for DISPLAY operation, except
that the COP parameter CCM for Meet-Me operation must also be specified.
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
CCM in Meet-me Operation with Display
• The trunk circuit is assigned as for DISPLAY OPERATION except:

SRCHATT = 5, default value (max. 99 possible) and 
OPTYPE=Meet-Me instead of DISPLAY.
• Configure the circuit with the TSCSU AMO as for DISPLAY operation. The
only parameters which are different are SRCHATT=5 (standard value, max.
99 possible) and OPTYPE=MEETME.
For CCM in Meet-Me operation, the TSCSU parameter MABLK must be set
to ’0’, i.e. calling party’s number is not displayed (see also CCM in Meet-Me
operation with Display).
• Assign route to multiple code calling system

AD-RICHT:TYPE=CD,CD=key-num,RTECD=key-
num,SVC=VCE,TGRP1=number;
158.3 CCM in Meet-me Operation with Display

• Configure the circuit with the TSCSU AMO as for Meet-Me operation
(OPTYPE=MEETME).
DIFFERENCE:
MABLK This parameter defines the length of the number to be displayed

on the code calling receiver (calling party’s number/A-block).
Type of Input: Single value, optional
Possible Values: 0
1 - 16
Default Value: 0 (no number is displayed; standard Meet-Me operation)
NOTE: The node number assigned to the CCM (NNO parameter of TACSU
AMO) is evaluated by the KNMAT AMO for display number modification for
DISPLAY operation or Meet-Me operation with display. This number must be a
unique number (see also Display Number Modification with AMO KNMAT)
158.4 Reversing the Number Display Sequence

For CCM in DISPLAY operation, you can reverse the display sequence of the
number blocks on the CCM receiver devices by setting the ZAND parameter
AAFTERB. This means that the A-block will be displayed after the B-block, i.e.
the display sequence will be "answering number - calling party’s number -
answering code" (B-block/A-block/C-block).
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
Left-Justified/Right-Justified A-Number Display
• Set new display sequence "answering number - calling party’s number -

answering code"
CHA-ZAND:TYPE=CCM,AAFTERB;
Default Value: AAFTERB i s n o t set (i.e. standard sequence A-block/B-
block/C-block,
i.e. "calling party’s number - answering number - answering code")
An answering code will only be displayed if assigned with the TSCSU AMO.
158.5 Left-Justified/Right-Justified A-Number Display

The standard display mode is right-justified. This means that if the calling party’s
number (A-block number) is longer than the number of digits specified in the
MABLK parameter, the beginning of the number will run off the left side of the
display block. If the A-block number is shorter than the number of digits specified
in the MABLK parameter, the left side of the display block will be filled in with
zeroes.
If the display mode is set to left-justified, the end of the calling party’s number
will run off the right side of the display block, if too long. If shorter, the right side
of the display block will be filled in with zeroes. You can change the display mode
as follows:
• Set left-justified display mode

CHA-ZAND:TYPE=CCM,ADISPEND;
Default Value: ADISPEND i s n o t set (right-justified display mode)
The total length of A-block + B-block + C-block, including separators and end-of-
block characters, must not exceed 22 characters, otherwise the A-block will be
truncated.
158.6 CCM with Block Separators and End-of-Block Characters

The length of the calling line information element varies according to where a
caller is calling from (e.g. 12 digits for calls from digital ISDN exchanges, 0 digits
for calls from analog exchanges, or 5 digits for internal calls). To compensate for
this, some multiple code-calling systems can interpret block separator characters
(*) and an end-of-block character (#). These special characters allow you to set
a variable A-block length
The block separator characters separate the A-block, the B-block, and the C-
block of a code-calling block. If an answering code is defined, the end-of-block
character follows the C-block. If no answering code is defined, the end-of-block
character follows the B-block.
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
CCM with Code Conversion
• Configure the circuit with the TSCSU AMO as for CCM in DISPLAY operation
or CCM in Meet-Me operation with display;
DIFFERENCE:
OPTYPE=DIS&BLKSEP&BLKEND,
or
OPTYPE=MEETME&BLKTSEP&BLKEND,
and
MABLK=16 (maximum length);
In this case, for incoming calls from analog exchanges (calling line identification
information element is 0), a single zero is transmitted in the A-block.
If the code-calling system requires fixed lengths for the A block and the B-block,
you should specify a fixed length for the A-block, and omit the block separators.
In this case, if the answering number differs from the number of the calling party,
the left or right side of the answering number display block (B-block) will either be
filled in with zeroes (if the number is shorter) or the number will run off the left or
right side of the block (if longer).
• Configure the circuit with the TSCSU AMO as for CCM in DISPLAY operation
or CCM in Meet-Me operation with display;
DIFFERENCE:
OPTYPE=DIS&NOBSEP&NOBEND,
or
OPTYPE=MEETME&NOBSEP&NOBEND,
and
MABLK= betewen 1 and 16;
158.7 CCM with Code Conversion

If the station numbers used for code-calling responses in the OpenScape 4000
system (answering number in the B-block) are not the same as the search codes
of the CCM, you must assign a code conversion table for these numbers. More
than one search code can be assigned to the same station number (answering
number), if required.
• Enable answering number/search code conversion for CCM

AD-TSCSU:,,DEV=PSM,,CONV=Y;
• Assign a conversion table for the CCM
AD-PERSI:TYPE=CCM,CCMSCD=key-num,STNO=number,CCNO=key-num;
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
Parallel Ringing of Exchange Calls if FWD/FNANS Activated to CCM in Meet-me Operation
158.8 Parallel Ringing of Exchange Calls if FWD/FNANS Activated to CCM

in Meet-me Operation
Direct-dialled calls from digital and analog exchanges to users who have
activated call forwarding or forwarding on no answer to the CCM system can be
rung in parallel. This means that the user’s telephone will continue ringing while
he or she is being paged.
• Enable parallel rining for CCM in Meet-Me operation

CHA-ZAND:TYPE=CCM,STNRNG=Y;
158.9 Priority Signalling of Urgent Exchange Calls for CCM in Meet-me

Operation
Incoming exchange calls which are direct-dialled to the CCM system, or
forwarded to the CCM system from a user’s telephone, are signalled with the
"urgent" CCM priority code (CCMSURG).
• Configure circuit with the TSCSU AMO as for CCM in Meet-Me operation.
DIFFERENCE:
CDGT=x y; x = normal call, y = urgent call
158.10 Announcements for CCM in Meet-Me Operation

Looped Announcements via Musiphon
For CCM systems in Meet-Me operation, a looped announcement can be played
back to the calling party via Musiphon connected to an SLMA, instead of the code
calling or paging tone
(CHA-ZAND:TYPE=CCM,SRCHTN=KNTNINT/MUSIC/RNGTNINT).
• Enable announcement playback for internal and external calls to CCM in

Meet-Me operation
CHA-ZAND:TYPE=CCM,ANNINTCC=Y,ANNEXTCC=Y;
• Assign CCM tone (HOLDCCS) to SIU tone TSL or PEN TSL
CHA-ZAND:TYPE=TONES,CP=HOLDCCS,SIU=1 to n;
or
AD-SSC:PEN=a-b-c-d,TYPE=EXTANN,CPCALL=HOLDCC;
Callers from digital exchanges will always hear the r i n g b a c k tone;
if parallel ringing is enabled for CCM in Meet-Me operation, callers from both
digital and analog exchanges will hear the r i n g b a c k tone.
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
Announcements for CCM in Meet-Me Operation
For CCM systems in Meet-Me operation, a synchronized announcement can be
played back to the calling party via an external announcement unit connected to
a TMOM, instead of the code calling or paging tone
(CHA-ZAND:TYPE=CCM,SRCHTN=RNGBK/ACTION/MUSIC).
COP parameter CCR must be set for the calling line. If the calling line is a digital
exchange the COP parameter ABPD (initial answering) must also be set. In
addition, the synchronized announcement for call to CCM must be enabled
centrally (ZAND:TYPE=CCM,SYNCACCM=YES)
Synchronized announcements are used for providing callers with a specific

sequence of information prompts, depending on the call progress/traffic situation
of the incoming call, in order to achieve specific reactions.
The prompts/announcements are achieved by connecting external

announcement units to TMOM boards. Each prompt or announcement is heard
from the beginning. Up to 50 callers can listen to an announcement at any one
time. The announcement is not LTG-dependent.
The attributes of an announcement are defined in a specific announcement type

(= announcement name). Between 1 and 64 announcement units or tone sources
can be combined to form a single announcement type. This is done by configuring
the TMOM boards for synchronized announcements (RAS), and assigning them
to the same announcement type.
For more details, and instructions on how to configure a TMOM board for
synchronized announcements, please refer to the AMO Usage Examples’ section
"Announcerment Unit, Synchronized Announcements".
Example:
Callers to the multiple code-calling system CCM should hear a synchronized

announcement. The announcement is not to be repeated. After the
announcement, the CCM hold tone is to be fed in for as long as possible. The call
waiting tone (knocking/camp-on tone) is to be defined as the entry tone, and the
ringback tone is to be defined as the exit tone. The required operating mode is
"Start/Stop", and an announcement start delay timer of 2 seconds is to be set.
• Enable announcement for CCM in Meet-Me mode

CHA-ZAND:TYPE=CCM,SYNCACCM=YES
• Assign announcement type 4:
AD-SYNCA:
ANTT,4,Mueller_Inc,ON,,,HOLDCCS,255,ON,,,,,,,STA_STO,2;
• Assign entry tone/exit tone for ANNCCM announcement reason
AD-SYNCA: ANNTONE,ANCCM,CAMP,RNGBK;
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
Display Number Modification with AMO KNMAT
• Assign announcement reason / announcement type table:

Depending on the ITR code number of the incoming call, the announcement
type 4 must be assigned to the announcement reason ANNCCM. The ITR
numbers used depend on the types of call situation for which the
announcement is required.
• If the CCM is reached by direct dialling, and the code-calling number dialled
belongs to an internal user, the called user’s ITR (5) is used.
AD-SYNCA: ANNMITR, ANCCM, 5, 4;
• If the code-calling number dialled belongs to an external user, the calling
user’s ITR (7) is used.
• If the CCM is reached via call forwarding/forwarding on no answer after
dialling an internal user’s number, the ITR of the internal (forwarding) user (8)
is used.
• If the CCM is reached via call forwarding/forwarding on no answer after
dialling an external user’s number, the caller’s ITR (7) is used.
If the CCM system is operated without initial answering, callers from digital
exchanges will always hear the r i n g b a c k tone;
if parallel ringing is enabled for CCM in Meet-Me operation, callers from both
digital a n d analog exchanges will hear the r i n g b a c k tone.
158.11 Display Number Modification with AMO KNMAT

The displayed number (calling number, i.e. number of code-calling party) can be
shortened and/or supplemented with the aid of the KNMAT AMO.
This is possible for internal and external code-calls alike; however, the number
modification is only possible for numbers in the OpenScape 4000 numbering plan
(NPI=UNKNOWN), and not for the PRIVATE or ISDN numbering plans.
NOTE: For DISPLAY operation, or Meet-Me operation with display, the node
number assigned to the CCM (NNO parameter of TACSU AMO) must be a unique
number, since it is evaluated by the KNMAT AMO for display number modifi-
cation.
• Configure the circuit with the TSCSU AMO as for DISPLAY operation, or
Meet-Me operation with display.
DIFFERENCE:
NNO = Virtual node number.
Type of Input: Single value or up to 3 linked single values, optional
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
Display Number Modification with AMO KNMAT
Possible Values: kkk, jjj-kkk or ii-jjj-kkk, where
kkk = 1-999 (level 0 node code)

jjj = 0-253 (level 1of multi-level node address)
ii = 0-29 (level 2 of multi-level node address)
See also ZAND AMO description, branch: ALLDATA, parameter: NNO
Default Value: 0-15
• Add modification table data:

CHA-KNMAT:
NPI = UNKNOWN, i.e. OpenScape 4000-specific numbering plan

LEVEL = 0, single value, mandatory
ONNO = 1-999, i.e. explicit source node number or
ONNOL = OWN/ROW, i.e. own node or all nodes
DNNO = node number assigned to CCM
MODCO = OUT, i.e. for outgoing traffic to CCM
N
NUMEXT = "number extension", i.e. digits prefixed to displayed number
NUMRED = "number reduction", i.e. digits removed from beginning of displayed
number
If no display number modification is to be carried out, and if the logical node

number ROW is entered in the KNMAT matrix, you must enter the following:
• Add modification table data:

CHA-KNMAT:
NPI = UNKNOWN, i.e. OpenScape 4000-specific numbering plan

LEVEL = 0, single value, mandatory
ONNO = 1-999, i.e. explicit source node number.
Logical node type ONNOL=ROWonly applies to those nodes for which no other
modification type is assigned
DNNO = node number assigned to CCM
MODCON = NONE
NUMEXT = "number extension", i.e. digits prefixed to displayed number1
NUMRED = "number reduction", i.e. digits removed from beginning of displayed
number<Hochgestellt>
1 i.e. digit prefixes which are not to be added or removed
Example
The system has the node number 1-1-100; the calling numbers of all outgoing
connections are prefixed with ’19’ (CHA-
KNMAT:UNKNOWN,0,100,,,ROW,,OUT,19;).
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
Multiple code calling of the same paging number
The CCM is assigned the node number 1-1-37, the length of the display number
is set to ’6’:
CHA-TSCSU:PEN=<pen>,DEV=CCM,NNO=1-1-37,MABLK=6;
Provided no other value is entered in the node connection matrix for node number
37, the display number of an internal call is modified by prefixing the digits ’19’
=>display number: 19 3100.
1. No modification:
CHA-KNMAT:UNKNOWN,0,OWN,37,,,NONE,19;
=> display number: 00 3100
2. Display numbers of calls from node 1-1-200 are to be prefixed with ’17’:
CHA-KNMAT:UNKNOWN,0,200,,37,,,OUT,17;
=> display number: 17 3100
158.12 Multiple code calling of the same paging number

Simultaneous code calling of the same paging number can be set. When
answering, the calling party who is longest in the search queue and can be
reached is selected.
• Set, if multiple code calling of the same paging number is allowed

CHA-ZAND:TYPE=CCM,SRCHONCE=YES/NO;
158.13 Suffix dialing to CCM with busy

Suffix dialing to CCM from Digite or Anate can be executed for a call to busy.
• Set, if suffix dialing to CCM is allowed for a call to busy.

CHA-ZAND:TYPE=CCM,POSTDBSY;
158.14 Paging with on-hook handset internally and throughout network

It is possible to replace the handset after the call without releasing the job. Paging
with an on-hook handset can be used both internally and externally throughout
the net.
The CCM key lights up during netwide paging with on-hook handset. When the
CCM key is pressed, the job is released in the node with the CCM connection.
• Set, if the paging job continues after handset replacement

CHA-ZAND:TYPE=CCM,DEL=YES/NO;
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
CTIME Timers for CCM
(entries must be made in the node of the paging party).
158.15 CTIME Timers for CCM

If a multiple code calling system has less search jobs than the number specified
in the TSCSU AMO, the system starts a corresponding number of dummy tasks.
For each dummy task in the search queue, a timer is started which takes the
same amount of time to run down as a normal search job.
The next search job in the queue is not transmitted until the dummy task timer
(WAIT1/2) has timed out. This allows the system to achieve near-constant time
cycles for each repeat beeping.
With the CTIME AMO, you can configure the system to delete unanswered
search jobs after a specific number of attempts, or to keep unanswered search
jobs in the search queue for a specific length of time (to allow users more time to
answer).
Search jobs are deleted when the timer runs out (CLRANS1/2/3/4).
For administration purposes, the two timers WAIT1 and WAIT2 are sufficient,
since the OpenScape 4000 system permits a maximum of two multiple code-
calling systems to be configured. These timers can be set between 0.5 and 5
seconds (in steps of 100 ms) .
• Change timers for first and second dummy task:

CHA-CTIME:TYPESWU=CCM,WAIT1=1000,WAIT2=2000;
• Display timers for first and second dummy task:
DIS-CTIME:TYPESWU=CCM;
""
" TIMERS FOR MULTIPLE CODE-CALLING SYSTEMS:"
" ========================================="
" +-----------------------+-----------------------+-----------------------
+"
" | NOTRDY1 = @@@@ SEC. | NOTRDY2 = @@@@ SEC. | WAIT1 = 1000 MS.
|"
" | WAIT2 = 2000 MS. | CLRANS1 = @@@@ SEC. | CLRANS2 = @@@@ SEC.
|"
" | CLRANS3 = @@@@ SEC. | CLRANS4 = @@@@ SEC. |
|"
" +-----------------------+-----------------------+-----------------------
+"
""
• Regenerate the call processing timers:

REGENERATE-CTIME;
"CHA-
CTIME:CP,@,@@,@,@@@,@@@,@@@,@@,@@@,@@@,@@@,@,@,@@@,@@@,@,@@,@
@,@@@,"
"
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
@@@,@@@,@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,"
"
@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,"
" @@@,@@@,@@,@@@,@@@,@@;"
"CHA-CTIME:TRK,@@@,@@@,@@@,@@@,@@,@@@;"
"CHA-CTIME:ATND,@@,@@,@@,@@;"
"CHA-CTIME:CCM,@@,@@,1000,2000,@@@,@@@,@@@,@@@;"
"CHA-
CTIME:RES,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@@@,@@@
@@,"
" @@@@@,@@@@@,@@@@@;"
A31003-H3170-S103-6-7620, 02/2019
mucoca_en.fm
A31003-H3170-S103-6-7620, 02/2019
remote_en.fm
Feature Description
159 Remote Night Station Changeover

Previously, night stations (nightoptions/night variants) could be changed at an
active attendant console or via AMO (See Chapter 153, “Attendant Console”).
Also night stations can be changed at standard terminals as well as from an
attendant console. The authorization will be assigned as a classmark in a COS
for a specific group.
It will be possible for authorized users (regardless of whether the stations are
defined as night stations or not) and authorized attendants in any attendant
console group to change specific night stations within a system or other
OpenScape 4000 systems that are connected via CorNet-N/Cornet-NQ.
Sequence of changeover
1. Dial the authorization code for activating the night station (*88).
2. Dial the ATNDGR access code for the attendant group whose night station
you wish to change. This access code must be unambiguous throughout the
network.
3. Dial the NOPT number of the night station you wish to change (1 to 8).
4. Terminate the action by entering ’#’.
You can link several changes within the same system, e.g. you can change the
night options for up to three attendant groups at the same time. Use the flash key
(*) as a separator.

• Only one attendant console group can be switched simultaneously in any
other OpenScape 4000 system.
• The attendant code must be unique in the network.
• A maximum of 22 digits is possible.
• The DAR cannot be used for incoming trunks.

• Configure the digital analysis result as follows:
A31003-H3170-S103-6-7620, 02/2019
remote_en.fm
Relevant AMOs
ADD-WABE:CD=*88,DAR=NOPT;
• Configure authorization for switching as follows:
CHA-COSSU:TYPE=COS,COS=number,AVCE=NOPTCD;
• The station must have appropriate authorization to use this feature.
159.4 Relevant AMOs

Language
CD e access code/station number
KZP d Kennzahlpunkt
COS d Class-of-Service Nummer fuer Sprache
(FAX)
COS e class of service number for voice (FAX)
ESBER d Einfügen COS-Optionen fuer Sprache
AVCE e Add cos options for voice
A31003-H3170-S103-6-7620, 02/2019
tns_en.fm
Trunk Night Service
Feature Description
160 Trunk Night Service

With the release of HPath 4000 V1.0 the night service function of the system is
further enhanced.
Local TNS position

(trunk B) Local TNS position
(trunk C)
Attendant Group in

night service Remote
GNS position
PSTN trunk
PSTN trunk (C)
(B)
Call Call
Figure 124 Trunk night service

The feature is based on the existing night service. In order to improve the facilities
of network wide night service configuration, the following enhancements has
been implemented:
(Remark: The night service feature does not depend on the type of the used
attendant groups. The following descriptions are valid for Multiple Queue-MQ
groups and Double Queue-DQ groups as well.).
The attendant console activates night mode by clicking the night button in the
Buttons window or by pressing the Night key on the keyboard. The DAY/NIGHT
Service indication in the call control window shows NIGHT.
This can also be achieved by unplugging the handset.
160.1.1 Console night service

When an attendant activates night mode in an attendant group with a least one
other attendant in day mode, then the attendant is in Console Night Service.
When the Attendant enters CNS then all dedicated calls to the console
A31003-H3170-S103-6-7620, 02/2019
tns_en.fm
Trunk Night Service
Feature Description
(e.g.Recalls Serial Calls etc) are changed to general calls and these are
represented to the group. Personal calls to the Attendant are however
disconnected and the caller recieves a notification of this.
The source button in the call control window will be disabled and appear grey to
the user.Indication of calls in the source queue will still be presented to the
console and will increment.
Outgoing calls can still be made as normal.
160.1.2 Group night service

When all attendants of an attendant group have activated night mode, the Group
Night Service is active. The displays and keys are as CNS above.
This feature can be split into different requirements and their solutions.
Local Extension calls to an AC Group
When an AC group is night service (GNS) local extension calls shall
always follow the GNS destination.
Incoming CO trunk calls
Group night service for trunk calls (GNS). Trunks follow the GNS
destination where no individual night answer point is defined for the trunk
as in the case for extension calls.
Trunk night service (TNS see below) If set for the system will overide
GNS.
Centralised attendant functionality
Incoming CO calls in a break-in node automatically routed to a remote AC
group use the centralised attendant functionality (CAC). On encountering
the remote attendant group in night service the break -in node is informed
of the night status of the CAC and the GNS answer point. The decison as
to which night answer point to route to is made in the break-in node i.e
follow the GNS of the CAC or route to the TNS destination of the incoming
trunk.
If trunk night service is active (ZAND:ATND- INIGHT=YES) in the centralized

attendant switch, centralized attendant has night mode activated and rerouting is
permitted, all calls will be diverted to the assigned night destination by rerouting
to the originating switch.
The counter for CAS-diversions (ZAND: CACFWMAX) will be checked and

incremented also for night diversions to internal centralized attendant.
A31003-H3170-S103-6-7620, 02/2019
tns_en.fm
Trunk Night Service
Restrictions
160.1.3 Trunk night service

For each incoming networking trunk a local or netwide night service destination
can be defined (TDCSU / TACSU parameter INIGHT), which is used for trunk
night service instead of the group night service destination.
TNS is active if a TNS destination is configured for the trunk and the feature is
enabled within the system (AMO ZAND:ALDATA,INIGHT=YES).The TNS is
active independent of the active night option and the user cannot decide as to
whether a call is routed to the GNS or TNS target. The decision is made on a per
attendant group basis by a new parameter in VFGR :- INIGHTPR.
The most important trunk night service configurations are described in Section
160.4, “Generation (Examples)”. The feature must be enabled / disabled
generally with the system wide parameter INIGHT (ZAND:ATND). If disabled,
group night service GNS is active for trunk calls. If enabled, the processing of
trunk calls depends on the parameter INGHTACT (ZAND:ATND). This system
wide parameter defines an AC group within the network (from the originating
node point of view) on which the trunk night service destination instead of the
group night service destination should be used. I.e., assuming there is a
sequence of CAS-diversions how many diversions are allowed before switching
to the TNS destination.
160.2 Restrictions
The feature has the following restrictions:
• GNS destinations (Analog or Digital) within OpenScape 4000 can only be

local.
• If the TNS destination is a single device (analog or digital)there is no call

waiting terminating feature (camp on) .Therefore a master hunt group
should be configured to allow camp on of more than 1 night service call
• If the TNS destination is busy the system will try after a time out a new
attempt to connect i.e, it will be polled. This could cause additional traffic
on a network
• Cot parameters FWDN and FNAN must be set in all transit and
centralised attendant nodes to enable the feature to work
A31003-H3170-S103-6-7620, 02/2019
tns_en.fm
Trunk Night Service
AMO Usage Examples
160.3 AMO Usage Examples
Public/Private
Network
OP OP
1
CO call to operator
eg 01159430300
OP
PBX (B)
OP
CO party calls operator
PBX (C)
in PBX (A)
OP
PBX (D)
OP PBX (A)
means : Operator in night

mode to destination 4711
TNS-destination
Figure 125 Call flow (routing) for INGHTACT = 4 in PBX(A)
Figure 125 illustrates the call flow (routing) for INGHTACT = 4 in PBX(A).
Operator (OP1) in PBX(A) has activated night mode to external centralized

attendant OP2 in PBX(B). This attendant group in PBX(B) is in night mode to
internal centralized attendant OP3, which is in night to another centralized
attendant (OP4) in PBX(C). This attendant group in PBX(C) has also activated
night mode to another external centraized attendant OP5 in PBX(D).
Assuming, there’s only a trunk night service destination on the CO-trunk

configured(not on tie lines), INGHTACT in PBX(A) marks an attendant group,
whichs night mode causes the diversion to the trunk night service destination in
the originating switch.
INGHTACT = 0: trunk night destination 4711 is always called (independent of
night / day mode of OP1)
INGHTACT = 1: trunk night destination 4711 is called, if called attendant
group OP1 is in night mode.
A31003-H3170-S103-6-7620, 02/2019
tns_en.fm
Trunk Night Service
INGHTACT = 2: trunk night destination 4711 is called, if the centralized

attendant OP2 is in night mode.
INGHTACT = 3: trunk night destination 4711 is called, if 2nd centralized
INGHTACT = 4: trunk night destination 4711 is called, if 3rd centralized
IMPORTANT: A device will not change its authorization level (COS), if used as
trunk night destination. Furthermore, no parallel call situation will be supported at
the trunk night destination.
The parameter INIGHTPR (AMO VFGR) controls, whether the trunk night service
activation should depend on the activated night variant number 7 or not:
INIGHTPR = NO :trunk night service is only active, if the activated night
variant number equals #7 (this can give the attendant some measure of
control)
INIGHTPR = YES: trunk night service is always active.TNS is independent of
the active NAVAR number and always has priority over the GNS.
If a trunk call is night-diverted to a busy trunk night destination, the call will be
queued into the call queue of the final diversion initiating attendant / centralized
attendant. By timer expiration a next diversion request will be started to the busy
TNS destination.
160.4 Generation (Examples)
160.4.1 Trunk Night Service

Incoming CO calls to the operator (attendant group) should come to a local trunk
night destination 4711, only if operator has activated night option 7 (in the
example, night option 7 is night mode to external centralized attendant)
A31003-H3170-S103-6-7620, 02/2019
tns_en.fm
Trunk Night Service
Local TNS B: local station 3200

destination 4711 calls operator
B
A: CO call
to operator #7
Public/Private
Network OP OP
B
A
PBX (A) PBX (B)
OP Attendant group in night mode
OP Attendant group in day mode
Parameter settings in PBX(A):

AMO ZAND:ATND
INIGHT = YES
INGHTACT = 1
CACFWMAX >= 1
AMO VFGR
INIGHTPR = NO
CASMFC = YES
AMO VFGKZ
ATND+ATNDDID entries required
AMO TDCSU / TACSU
INIGHT = 4711 (trunk night service destination number)
Parameters have to be set in all affected break-in-nodes / trunks of the network.
160.4.2 Centralized Attendant Configuration

In this scenario Trunk calls from CO should come to the trunk night service
destination
994711, if the centralized attendant has activated night mode, but independent of
the activated
A31003-H3170-S103-6-7620, 02/2019
tns_en.fm
Trunk Night Service
night variant number. Local operator calls should terminate at the group night
service destination.
B: Local station
3200 calls operator GNS destination
5211
B
B
B
OP OP
Public/Private
Network
PBX (A) A PBX (B) PBX (C)
A: CO call to operator A
A
PBX (D)
TNS
OP Attendant group in night
destination
mode
994711
160.4.2.1 Parameter settings
AMO Parameter PBX(A) PBX(B) PBX(C)

ZAND:ATND INIGHT YES n/a YES
ZAND:ATND INGHTACT 2 n/a 2
ZAND:ALLDATA CACFWMAX >=2 n/a >=2
VFGR INIGHTPR n/a n/a YES
VFGR CASMCF YES n/a YES
VFGKZ ATND AND ATNDID Entries reqd n/a Entries reqd
COT FNAN n/a set for i/c set for i/c
FWDN trunk trunk
TACSU/TDCSU INIGHT External n/a n/a
number
994711 set
for i/c CO
trunk
A31003-H3170-S103-6-7620, 02/2019
tns_en.fm
Trunk Night Service
Relevant AMOs
160.5 Relevant AMOs
AMO Parameter Sprache/ Description

Language
ZAND VF=ENACHT d NEIN : Leitungsnachtschaltung ist deaktiviert.
Lokale Anrufe bei einer VF-Gruppe im Nacht-
betrieb werden immer an das aktive GNS-Ziel
weitergeleitet
JA: Leitungsnachtschaltung ist aktiviert.
Amtsgespräche zu einer VF-Gruppe werden
abhängig von der effektiven
Betriebseinstellung des Vermittlungsplatzes
und der ZVFs sowie von der effektiven
Netzkonfiguration an TNS-Sonderziele
weitergeleitet.
ATND=INIGHT e NO : Trunk night service is deactivated.i.e
local calls to an attendant group in night
mode will always be forwarded to the
activated group night service
YES: Trunk night service is activated i.e trunk
calls to an attendant group will be forwarded
to special trunk night service destinations
dependent on the actual mode of the
attendant, the centralised attendants and on
the actual network configuration.
ENCHTAKT d 0.....9 Legt fest, wie viele GNS-Umleitungen
zulässig sind, bevor ein TNS-Ziel angesteuert
wird. Der Wert von ENCHTAKT wird nur
dann berücksichtigt, wenn die
Leitungsnachtschaltung generell mit
ENCHTAKT=JA/NEIN aktiviert wurde.
INGHTACT e 0.....9 Defines the number of group night
service diversions to be allowed before a
trunk night service destination is called. The
value of INGHTACT takes affect only if trunk
night service is generaly activated with
INIGHT= YES/NO.
ZVFUMMAX d 0,,,,,9 Der Grenzwert für die zulässige Anzahl
Umleitungen an ZVFs sollte zumindest
identisch mit dem ENCHTAKT-Wert sein.
CACFWMAX e 0,,,,,9 The limit for the permited number of
centralized attendant diversions should be at
least equal to the INGHTACT value.
VFGR ENACHTPR d NEIN: Amtsgespräche werden nur dann an
das TNS-Ziel weitergeleitet, wenn die
Nachtoption 7 aktiviert ist.
JA: Die Leitungsnachtschaltung wird
unabhängig von der aktiven Nachtoption
aktiviert.
A31003-H3170-S103-6-7620, 02/2019
tns_en.fm
Trunk Night Service
Relevant AMOs

Language
INIGHTPR e NO: Trunk calls will be routed to the trunk
night service destination only if the number of
the activated night variant is 7.
YES: Trunk night service is invoked
independently of the activated night variant
number
ZVFMFAUL d zvf extern mit mehrfacher aul
CASMCF e YES : The feature “multiple centralised
attendant” feature is enabled
NO: The feature is deactivated
VFGKZ RNR d Kennzahl einer Vermittlungsfernsprecher-
gruppe
CD e Attendant console group access code
COT AULN d Anrufumleitung ohne Bedingungen per
Rerouting netzweit. Gültig für alle Satztypen.
Ist der Parameter gesetzt, wird im
Umleitungsfall die Umleitungsrufnummer an
den Ursprungsknoten zurückgegeben, der
daraufhin zu dieser Rufnummer eine neue
Verbindung aufbaut. Die erste Verbindung
wird ausgelöst. Gilt für alle digitalen
Verbindungssätze und muß im gesamten
Netz gesetzt werden. Ab EV1.0 wird AULN
durch den COT Parameter PRZL ergänzt, der
beim Programmieren einer netzweiten AUL
die Zielprüfung veranlaßt. Parameter AULB
und AULN schließen sich aus !!
FWDN e ICall forwarding without conditions via
rerouting network-wide. Valid for all kind of
trunks. If parameter is set, the call forwarded
number is send back to origination node
which will create a new connection to this
station number. The first connection will be
released. Valid for all digital trunks and has to
be set in whole network! Since EV1.0 FWDN
is enhanced by parameter CFVA which
activates a check for destination number
when programming a network-wide CFWD.
Either parameter FWDN or CFBN may be
set.
RWSN d Einschalten der Rerouting Funktion bei
Rufweiterschaltung. Gültig für alle Satztypen
und netzweit.
FNAN e Call forwarding no-answer via rerouting. Valid
for all kind of trunks.
TACSU/ ENACHT d einzelnachtstelle
TDCSU
INIGHT e individual night station i.e. per incoming line
A31003-H3170-S103-6-7620, 02/2019
tns_en.fm
Trunk Night Service
Relevant AMOs

Language
CTIME ATNDTNSR d setup-meldungsfrequenz (leitungs-
nachtservice besetzt)
ATNDTNSR e ATNDTNSR=3,....100 seconds : When a call
is routed by night service to a trunk night
destination which is busy ,the call is queued
in a suitable attendant call queue and this
timer is started. After the timer expires the call
is routed again to the trunk night destination.
If the destination is still busy ,ATNDTNSR will
be started again
A31003-H3170-S103-6-7620, 02/2019
uniansw_cm_en.fm
Feature Description
161 Universal Night Answer

Universal night answer or trunk answer from any station is a night option.
Incoming calls are routed to an analog port (e.g. for universal ringing). The trunk
call can then be taken at any telephone by dialling a code.
Each port for "trunk answer from any station" is assigned a neutral night variant
of the type "GENANS" by means of its administration number and the NAVAR
AMO. Only one port of this kind is permissible for each night option. This neutral
night option is then assigned to the ATND group as one of the night options 1-8.

• Prior to deletion of the port, the night option belonging to it must be deleted
(interrogation and deletion of the appropriate night option with the NAVAR
AMO). 
Before this, however, the night option must be released from the allocation to
the ATND group (VFGR AMO).
• If this night variant was the only one, or was provided for automatic night
service (AUTNS), this must be replaced by a substitute variant by means of
CHANGE-VFGR.Service Information

• Configure the module (SLMA)
Click Configuration Management --> System Data --> Module -->

Module, New. Enter the port equipment number with LTG, LTU, EBT,
select SLMA part number and save.
The module is configured via AMO BCSU:

ADD-
BCSU:TYPE=PER,LTU=<number>,SLOT=<number>,PARTNO=<st
ring>;
• Configure a universal night answer code:
Click Configuration Management --> Tables --> Dial Plan --> Dial Code,
New. Enter the dial code and select GENANS as the dial code type and
save.
A31003-H3170-S103-6-7620, 02/2019
uniansw_cm_en.fm
A digit analysis result GENANS is configured via AMO WABE:

ADD-WABE:CD=<key-num>,DAR=GENANS;
• Configure a universal night answer port (privileged station):
Click Configuration Management --> Port --> Privileged Station Port,

New. Enter station number, select as "universal night answer" and save.
The privileged station is configured via AMO SSC:

ADD-SSC:TYPE=GENANS,UNANO=<anumber>;
• Configure a night option (for GENANS):
Click Configuration Management --> Groups --> Night Options, New.

Enter night bell number, select as "universal night answer" type and
save.
The night option is configured via AMO NAVAR:

ADD-
NAVAR:NOPTNO=<nnumber>,TYPE=GENANS,GENANSNO=<anumbe
r>;
• Assign a code for universal night answer:
Assignment can only be administrated via expert mode.

Expert Mode --> ComWin --> Open ...< IP> via AMO. (See AMO
command).
The code is configured via AMO VFGKZ:

ADD-VFGKZ:TYPE=ATNDGR,CD=<key-num>,ATNDGR=<number>;
• Extend ATNDGR with night option:
ATND group configuration can only be administrated via expert mode.

Expert mode --> ComWin --> Open ...< IP> via AMO. (See AMO
command).
The ATND group is configured via AMO VFGR:

CHA-
VFGR:ATNDGR=number,{NOPT1,...,NOPT8},OPT=<number>;
A31003-H3170-S103-6-7620, 02/2019
uniansw_cm_en.fm
Relevant AMOs
161.4 Relevant AMOs

Language
NOPTNO e NUMBER OF NIGHT SWITCHING OPTION
ABFNU d NUMMER EINES FUER ALLG.-ABFRAGEN
EINGERICHTETEN GERAETES
GENANSNO e DEVICE NUMBER OF PREASSIGNED
UNIVERSAL NIGHT ANSWER STATION
SSC TYP d TYP DER AUSGABE
TYPE e SPECIAL STATION TYPE
ARUFNU d RUFNUMMER DES ABF-ANSCHLUSSES
UNANO e DEVICE NUMBER OF NIGHT ANSWER
STATION / BELL
KZP d Kennzahlpunkt
VFGKZ TYP d VERZWEIGUNG: KENNZAHL - VF-GRUPPE
TYPE e TYPE OF FUNCTION
RNR d KENNZAHL EINER
VERMITTLUNGSFERNSPRECHER-GRUPPE
CD e ATTENDANT CONSOLE GROUP ACCESS
CODE
VFGRU d VERMITTLUNGSFERNSPRECHER-GRUPPE
VFGR VFGRU d NUMMER DER
VERMITTLUNGSFERNSPRECHER - GRUPPE
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
A31003-H3170-S103-6-7620, 02/2019
uniansw_cm_en.fm
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
ACD (Automatic Call Distriution)
ACD
ACD
162 ACD (Automatic Call Distriution)
162.1 Enhanced Agent Feature Operation after Soft Restart
ACD
Examples of features maintained include but are not limited to:
• Agent to Supervisor Messages
• Call Forwarding
• Manual Hold
• callback
• conference
• repeat id
• dds/dss
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Phantom Lines as Agents
• message waiting
• recall
• park to station/group park
• consult,transfer and toggle

This feature enhancement only applies to logged on ACD Agents that are
connected to an ACD call from an external (outside the private network) source.
The intent is to allow the Agent to have access to activation of all features
following a soft restart just as it did before any restart.

There is no special user interface for this feature enhancement. The feature
applies to all ACD routed calls from an external source connected/talking to an
(non-PhoneMail) ACD Agent.

No special configuration is necessary for this feature enhancement. And no AMO
usage is required.
162.2 Phantom Lines as Agents

A phantom line is synonymous with a signed-off keyset line. Essentially, this is a
line that is currently not attached to a PEN number. Phantom/Signed-off keyset
line appearances remain in service even though they do not have a physical line
assigned. This feature enhancement allows a properly classmarked phantom
line to operate as an ACD Agent.
e.g. An Agents Keyset is configured with one prime line. In addition to the prime
line the keyset may also have one or more phantom lines configured in addition
to additional secondary lines. The Agent can log on to the prime line and all the
secondary lines provided there are different logon I.D.’s are used for each line.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Keysets can be
configured with
a mixture of
phantom lines
and secondary
lines. These
can be used as
ACD Agents in
phant addition to the
phant Prime line
phant
phant
phant
phant
second
prime
An Agent can never transition between a phantom Agent and a non-phantom

Agent. That is, a phantom Agent is not permitted to sign-on and be assigned to
a physical line. Similarly, a prime line Agent cannot sign-off and have its
remaining line appearances become phantom Agent appearances.

A phantom line can log on as an ACD Agent only if it is classmarked as an Agent
(AGENT) and it is restricted from both signing on and signing off (NORELOC).
CHANGE-SDAT:STNO=2222,TYPE=ATTRIBUT,AATTR=NORELOC;
IMPORTANT: The NORELOC attribute blocks the line it is assigned to from

performing autoset relocation (sign-on/sign-off). A phantom Agent must be
logged off from the line appearance where the phantom was initially logged on.
Operation of the phantom Agent line is the same as for other keyset lines which
are Agents. The phantom line must be selected either manually or via the
keyset’s originating line preference setting for the phantom Agent line to be in
use.
Some ACD features only operate on ACD keysets -- keysets whose prime line is
an Agent. Also note that the ACD LEDs that indicate Agent modes and call queue
status only apply to the device’s prime line and not any secondary or phantom line
appearance.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Phantom lines can be classmarked as ACD Supervisors (SUPER) and as

autologon extensions (AUTOLOG). However, phantom lines are blocked from
acting as ACD group Supervisors and from being automatically logged on.
162.2.3 AMO Usage

Two methods exist for creating a phantom Agent. This is because there are two
ways in which the line can be signed-off.
162.2.3.1 Create a Phantom Agent Via Feature Access Code for

Sign-Off
In order to sign-off a line via feature access code, the line must have a PIN
assigned.
• Create secondary line appearance(s) of some keyset line (3340).
• Create a PIN1 for the line (3340) via AMO PERSI.
• Sign-off the keyset line (3340) by selecting the prime line and entering the
sign-off access code followed by the line’s PIN1. Normal sign-off
restrictions apply here including the restriction that the line does not
possess the NORELOC attribute.
Now 3340 is a phantom line (it PEN has been removed). The remaining line
appearances of 3340 are still in service. However, an Agent cannot logon the
phantom line without first being blocked from performing autoset relocation or
sign-on/sign-off (NORELOC).
• Mark the phantom line so that it cannot be signed-on/off.

CHA-SDAT:3340,ATTRIBUT,NORELOC;
If 3340 is not classmarked as an Agent, this also must be done via AMO SDAT.
• Log an Agent onto line 3340. One way of doing this is by selecting the
line, entering the logon access code and entering a valid, free Agent ID.
Now 3340 is a phantom ACD Agent.
162.2.3.2 Create a Phantom Agent Via AMOs Only
• Create secondary line appearance(s) of some keyset line (3340).
• Sign-off the keyset line (3340) via AMO DSSU. Normal sign-off
restrictions apply here including the restriction that the line does not
possess the NORELOC attribute.
CHA-DSSU:TYPE=SIGNOFF,STNO=3340;
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
PhoneMail Ports as Agents
• Mark the phantom line so that it cannot be signed-on/off.

CHA-SDAT:STNO=3340,TYPE=ATTRIBUT,AATTR=NORELOC;
If 3340 is not classmarked as an Agent, this also must be done via AMO SDAT.
• Log an Agent onto line 3340 by selecting the line, entering the logon
access code or pressing the AVAIL key, and entering a valid, free Agent
ID.
Now 3340 is a phantom ACD Agent.
IMPORTANT: A phantom/signed-off keyset line can also be created directly with

AMO SBCSU by not assigning a PEN and setting INS=SIGNOFF.

Language
PERSI PIN1 e Create PIN for use when signing off keyset
line manually
PIN1 d PIN für manuelles Abmelden der Keyset-
Leitung erzeugen
SDAT ATTRIBUT e Mark line as AGENT and NORELOC
(prevents sign-on/sign-off)
MERKMAL d Leitung als AGENT und KRELOC
markieren (verhindert automatisches
Anmelden/Abmelden)
DSSU TYPE e Sign-off/Sign-on existing keyset line
TYP d Vorhandene Keyset-Leitung abmelden/
anmelden
SBCSU INS e Create keyset (without PEN) as initially
signed-off
INBETR d Keyset (ohne LAGE) als abgemeldet
erzeugen
162.3 PhoneMail Ports as Agents

This feature provides the ability to route ACD calls to PhoneMail Agent groups.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Properly configured PhoneMail trunk ports are treated as Agents and calls can be
queued to their PhoneMail Agent group awaiting a free Agent/trunk. PhoneMail
Agents are always logged on and in available mode when their corresponding
trunk port is in service i.e. the phonemail agents are automatically given the
attribute auto logon without AMO configuration and are logged on after
restart,reload when the trunk comes back into service.
ACD Agents
Group 1
ISDN
Phonemail Trunks configured

as ACD AGENTS in group 4

ACD calls can be routed to PhoneMail via a Route-to-Group ART step. The
Agents in the ACD PhoneMail group are associated with a specific trunk port in
an ACD PhoneMail trunk group. Routing and queuing to an ACD PhoneMail
group is the same as for normal ACD groups. The only difference is that specific
Agent selection is performed based on the ACD PhoneMail trunk selection
algorithm rather than the ACD group’s Agent selection algorithm.
The PhoneMail service access number used to route calls to the PhoneMail
Agent group is configured with the ACD group. This number must first be defined
in AMO RICHT. Upon successful completion of a route to a PhoneMail Agent, the
calling party display will be updated to show the DNI number followed by the
NAME configured in RICHT associated with the PhoneMail group’s service
access number.
IMPORTANT: If the PhoneMail service access number assigned to the Agent

group is invalid, all attempts to route ACD calls to this PhoneMail Agent group will
cause an error to be logged. Such failures cause ART processing to abandon
further attempts to reach the PhoneMail Agent group for this call (i.e. no queuing
to the group).
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
162.3.3 AMO Usage

Assume that an STMD2 board is already properly configured in slot 1-1-49 to
connect to an Xpressions server. (Note that the S0 interface to PhoneMail is the
only interface supported for ACD’s "PhoneMail Ports as Agents" enhancement.)
Also assume a valid COT (111) and COP (112) are already defined and the
numbering plan used is open.
• If a PhoneMail service access number is not yet defined for routing calls to
PhoneMail/Xpressions, one must be created. Create PhoneMail service
access number 27441.
ADD-RICHT:MODE=PM,IDX=1,SAN=27441,NAME="ACD PHONEMAIL
ACCESS",STYPE=XPRESION;
• Create an ACD PhoneMail Agent group. Group 4 will be a PhoneMail ACD
group with service access number 27441.
ADD-ACDGP:ACDGRP=4,TYPE=PM,PMSAN=27441;
• Create an ACD PhoneMail trunk group. Trunk group 444 will contain only
Agents/trunks for ACD group 4.
ADD-BUEND:TGRP=444,NAME="ACD PM TRUNK
GROUP",NO=30,RSV=N,TDDRFLAG=ON,GDTRRULE=0,ACDPMGRP=4;
• Create the ACD PhoneMail trunks and populate the ACD PhoneMail trunk
group. (There is nothing special for ACD PhoneMail Agent trunks in this
case; just the usual construction of digital trunks.) Each trunk must eventually
become an Agent before being brought into service. PEN 1-1-49-0 will be
added to ACD PhoneMail trunk group 444.
0,COTNO=111,COPNO=112,DPLN=0,LCOSV=1,CCT="PM
AGENT",PROTVAR=PSS1V2,SEGMENT=8,DEDSVC=NONE,TRTBL=GDTR,ATNTYP
=TIE,TCHARG=N,SUPPRESS=0,TGRP=444,DEV=S0CONN;
Repeat for each trunk circuit that will be an ACD PhoneMail Agent.
• Create a trunk route for ACD PhoneMail. (No special configuration for ACD
PhoneMail.) LRoute 98 will route calls to ACD PhoneMail trunk group 444.
ADD-RICHT:MODE=LRTENEW,LRTE=98,TGRP=444,NAME="ACD PM",DNNO=1-
1-200,PDNNO=1-1-200;
• Create access code for reaching ACD PhoneMail. 27 will be the access code
for ACD PhoneMail.
• Make ACD PhoneMail access code lead to route pointing to ACD PhoneMail
trunk group. Trunk access code 27 will take calls to route 98 and ACD
PhoneMail trunk group 444.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
• Create the ACD PhoneMail Agents and populate the ACD PhoneMail group.
Agent 41 will be an Agent in ACD PhoneMail group 4.
ADD-AGENT:AGTID=41,AGTTYPE=PM,ACDGRP=4,AGTPOS=1,PEN=1-1-49-
0,BCHAN=1;
Repeat for each PhoneMail Agent/trunk to be added to the ACD PhoneMail
group.
• Activate the ACD PhoneMail Agents/trunks. This can only be done once they
are assigned a PEN in an ACD PhoneMail group.
ACT-DSSU:ONTYPE=AUL,TYPE=PEN,PEN1=1-1-49-0,PEN2=1-1-49-7;

Language
RICHT MODE e Define an Lroute for the phonemail trunk
group
ART d LRTG für die PhoneMail-Bündelgruppe
definieren
WABE CD e Define PhoneMail service access number
KZP d PhoneMail-Dienstkennzahl definieren
ACDGP TYPE and PMSAN e Create ACD PhoneMail Agent group with
service access number assigned
TYP und PMSAN d ACD PhoneMail-Agentengruppe mit
Dienstkennzahl anlegen
BUEND ACDPMGRP e Link trunk group to ACD PhoneMail Agent
group
ACDPMGRP d Bündelgruppe mit ACD PhoneMail-
Agentengrupppe verknüpfen
AGENT PEN and BCHAN e PhoneMail Agents must be given the PEN
and B-channel of the ACD PhoneMail trunk
that they are associated with
LAGE und BKANAL d Den PhoneMail-Agenten müssen die LAGE
und der B-Kanal der ACD PhoneMail-
Amtsleitung zugeordnet werden, zu der sie
gehören
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Special Outpulsing Devices (SODs) as Agents
162.4 Special Outpulsing Devices (SODs) as Agents

A Special Outpulsing Device (SOD) is a specially configured analog device which
is expected to receive DNIS digit information via inband digit signalling upon
through-connection of an ACD call. The exact DNIS digit information outpulsed
to an SOD is configurable on a system basis.
ACD Agents
Group 1
ISDN
SOD eg phonemail with Analog

connections configured as ACD
AGENTS in group 4
Route to GROUP or Route to AGENT
SODs can be configured as Agents. Because they are typically not normal Agent
positions, they can activate indefinite work mode via a simple offhook-onhook
sequence when configured as autologon Agents.

An analog station, analog OPS, or T1 OPS is configured as an SOD in AMO
SCSU. When an SOD answers an ACD call via a Route-to-Agent, Route-to-
Group, or Route-to-Extension ART step, the internal and/or external DNIS
number associated with the call is outpulsed to the SOD. The exact DNIS
number(s) to outpulse is determined by system flag TYPEDNIS in AMO ZAND.
Outpulsing of DNIS digits after the SOD answers begins after the time period
(OHDELAY1) defined in AMO DTIM2.
SODs can be configured as autologon Agents. Such Agents enter indefinite work
mode automatically when they go offhook and then onhook without dialing any
digits. They must go offhook and enter the available mode access code to be
routed to as an Agent again. This is required to prevent the ACD from routing calls
to the SOD when it is unavailable e.g. when back-up operations are in place.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Special Outpulsing Devices (SODs) as Agents
162.4.3 AMO Usage
162.4.3.1 Creation of SOD and Outpulsing Characteristics
Assume the analog station, analog OPS, or T1 OPS device that will become the
SOD is already created as extension 2200. Configure 2200 as an SOD that will
be outpulsed external DNIS information only beginning 1 second after through-
connection of an ACD call.
• Assign 2200 as an SOD.

CHA-SCSU:STNO=2200,SPEC=SOD;
• Set system flag to the type of DNIS information to be outpulsed after through-
connection of an ACD call to an SOD. Set up so that only external DNIS digits
(as received from external party) are outpulsed.
CHA-ZAND:TYPE=ALLDATA2,TYPEDNIS=EXTDNIS;
• Set system timer for offhook delay to control interval after answer before
outpulsing of DNIS begins. Set timer to 1000 milliseconds.
CHA-DTIM2:TYPEDH=GEN,OHDELAY1=1000;
162.4.3.2 Creation of SOD as Autologon Agent for Special

Work Mode Activation
There is no new, special configuration for this aspect of the feature enhancement.
This is done automatically because the SOD simply must be an autologon
Agent.Therefore when an agent is configured and it is a SOD then it will
automaticaly log on.
The code for deactivating work mode must be configured in the device

Language
SCSU SPEC e Designate analog device as a Special
Outpulsing Device
SOND d Analoges Gerät als SOD bestimmen
ZAND ALLDATA2 e Configure the type of DNIS information
(internal and/or external) to outpulse
(TYPEDNIS)
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Silent/Tone Monitoring of Non-Agent Targets

Language
DATEN2 d Art der DNIS-Informationen (intern und/oder
extern) konfigurieren, die auszusenden sind
(TYPDNIS)
DTIM2 GEN e Configure timer to delay outpulsing for an
interval following connection to SOD
(OHDELAY1)
ALLG d Zeitüberwachung konfigurieren, um die
Aussendung der DNIS nach Anschaltung
einer Leitung an ein SOD um eine
bestimmte Zeit zu verzögern (OHDELAY1)
162.5 Silent/Tone Monitoring of Non-Agent Targets

Silent/tone monitoring targets must not be classmarked as an Agent. Monitoring
targets must only be classmarked as "Can Be Silent Monitored".

There is no change to the user interface. The restriction that a monitoring target
must be first classmarked as AGENT before being classmarked as CBSTMON
has been removed. Only the CBSTMON classmark is necessary for monitoring.
No special configuration is necessary for this feature enhancement.

Language
SDAT ATTRIBUT e AGENT attribute is no longer a prerequisite
for assigning the CBSTMON attribute
MERKMAL d Das Attribut AGENT ist keine
Voraussetzung mehr, um das CBSTMON-
Attribut zuordnen zu können
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Consultation Calls from Conference into ACD
162.6 Consultation Calls from Conference into ACD

Any station that can consult away from a conference is allowed to consult away
from a conference to an ACD number/destination.

There is no special user interface for this feature enhancement.
No special configuration is necessary for this feature enhancement and no Amos

are required.
162.7 Honoring of Call Forwarding for ACD Routes Offsite

ACD routes to offsite (outside the ACD node) destinations will be forwarded
according to the forwarding rules of the destination station.
There is no special user interface for this feature enhancement and no

configuration or AMO.
162.8 Automatic Call Acceptance (ACD Zip Tone)

This feature allows you to configure a toggle button on the ACD agent telephone
that allows the agent to set their telephone to automatically answer inbound
telephone calls.
When the button is pressed, the lamp comes on indicating that the feature is
enabled. When the button is pressed again, the lamp turns off.
If the feature is engaged and the lamp is on, and a call is delivered to the agent
by ACD call processing, a short burst of tone, or "zip" tone, is heard in the headset
the agent is using, and the caller is automatically answered and connected to the
agent. The call is terminated when the caller hangs up or the agent presses the
line key or the release key.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Personal Call Notification (AICS for ACD calls only)
When the feature is not engaged and the lamp is off, the telephone call must be
answered by the agent manually by pressing the line key.

Language
TAPRO AUTOM e Automatic Call Acceptance
AUTOM d Automatische Gesprächsannahme
162.9 Personal Call Notification (AICS for ACD calls only)

Automatic Call Pickup will be available for telephones configured with ACD
functionality.
There are 2 scenarios:
Agent is logged on and available
• AICS is activated
– The agent receives ACD calls. In this case nothing is changed: the agent
automatically hears the AICS zip tone and then gets connected to the
caller, or the agent automatically hears the AUDSRCID if activated, then
the zip tone and then gets connected to the caller.
– The agent receives personal calls. In this case the agent hears a personal
announcement if activated (see below ¡V user interface), similar to
AUDSRCID, then the zip tone and then gets connected to the caller.
• AICS is not activated
– The agent receives ACD calls. In this case nothing is changed: the agent
station rings. When the agent answers it gets connected to the caller or it
hears the AUDSRCID if activated and then gets connected to the caller.
– The agent receives personal calls. The agent station rings. When the
agent answers it hears a personal announcement if activated (see below
¡V user interface), similar to AUDSRCID, then it gets connected to the
caller.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Display the A Number at the Agent
Agent is logged off, or not available
AICS activated/not activated:
• The agent cannot receive ACD calls.
• The agent receives calls on his private line. In this case AICS has no effect,
the station rings and the agent uses the handset to answer the call. No
announcement starts.

• It is important to note that RECNUM 206 should be used in the future for this
feature only! Therefore RECNUM=206 cannot be used for other
announcements any more.
• In case of a keyset station the activation and deactivation of the AICS must
be made with the HS button instead of the AICS parameter from AMO KCSU.

Language
KCSU AICS e Automatic incoming call signalling on
headset
AICS=YES: Incoming call automatically
collected.
AICS=NO: Incoming call must be manually
collected.
AUTOANT d Automatisches Antworten bei
Kopfsprechgarnitur
AUTOANT=JA: Gespräch wird automatisch
entgegengenommen.
AUTOANT=NEIN: Gespräch muss manuell
entgegengenommen werden.
162.10 Display the A Number at the Agent

The displays for calling and called parties in an ACD scenario follows the
following implementation rules:
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Display the A Number at the Agent
Once an internal DNIS number was identified by the system, it is retained

throughout the life of the call unless it is overwritten.
During the life of a call, the DNIS information may be overwritten one or more
times by new DNIS information. This can occur each time a call is transferred,
extended or ACD routed to a number which is identified as a DNIS number.
The initial DNIS information for a call is not the first DNIS information produced
when DNIS information is produced more than once, e.g. due to multiple ACD
routings. The displays will be updated using the actual DNIS information which is
saved as redirecting data in call buffer.
In the described scenario, the calling party will be updated accordingly with the
actual DNIS number.
When agents' numbers are not suppressed (SUPAGTNU=NO in AMO ZAND),

the calling party display will be updated with agent's informations (number and/or
name).
The functionality of the CR:
With the implementation of this CR the displays for calling and calles parties in an
ACD scenario follows the following rules:
In case of an ACD call on the display of the calling party only the called ACD
number (DNIT number) can be seen.
This feature prevents to show the numbers of the agents and also other routed or
diverted devices on the calling party display.
If this feature is activated the already existing ACD display feature „suppress
agent number“ has no influence for the calling party display.
In the following Section 162.10.2, “Scenarios” the scenarios where this feature is
working are described.
162.10.2 Scenarios
1. The calling party is diverted from the ACD's queue:
2. The ringing call is deflected from the agent
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Ringback Tone for Diverted Call to analog CallDirector
3. The calling party is routed to a second DNI number (DNI 1 will be displayed
on the calling)
4. The Calling party is transferred to an ACD by an extension
At the call connection the display of the calling party shows the (first) DNI number.
162.10.3 Activation
The above described feature can be activated with the following AMO command:
CHANGE-ZANDE:TYPE=ACD, ORIGDNI =YES;
AENDERN-ZANDE:TYP=ACD,ORIGDNI=JA;
162.11 Ringback Tone for Diverted Call to analog CallDirector

It is possible to eliminate the ringback tone for a calling party if the application
divert a call from ACD queue to an anlaog CallDirector port and the calling party
was routed in the ACD to a music or an announcement.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Ringback Tone for Diverted Call to analog CallDirector

Prerequisites
• AMO ZAND RESERVE parameter 186 is activated.
• Calling party is in ACD queue and hears music or announcement.
• Application activated a CSTA deflect (ACL Diver Call) request for calling
party CallDirector port.
• The destination of CSTA Deflect (ACL Diver Call) Request is an analog

CallDirector port.
• Destination CallDirector has an activated AGENT flag in AMO SDAT.
User interface:
Calling party will not hear ringback tone when the application divert the call from
ACD music or announcement to the Call Director port.
calling party
Possible calling party devices:
• internal digital phone
• internal analog phone
• internal functional device
• external call via digital trunk (CO or TIE trk.)

• Activation of the feature
• Analog CallDirector
0,DVCFIG=ANATE,DPLN=0,ITR=0,COS1=50,COS2=50,LCOSV1=1,LCOSV2=1
,LCOSD1=1,LCOSD2=1,COSX=0,SPDI=0,COFIDX=0,SPEC=SUFDIAL,DIAL=V
AR,DHPAR=DTMFST,INS=YES,SSTNO=NO,HMUSIC=0,CONN=DIR,FLASH=YES,
DTMFBLK=NO,PMIDX=0;
• AGENT flag for CallDirector
CHANGE-SDAT:STNO=5300,TYPE=ATTRIBUT,AATTR=AGENT;
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Divert Call Request Support of Reroute Internal

Language
SCSU GERKON=ANATE d CallDirector muss als Anate konfiguriert
sein.
DVCFIG=ANATE e CallDirector must be configured as Anate.
SDAT EMERK=AGENT d CallDirector muss ein aktiviertes AGENT-
Flag haben.
AATTR=AGENT e CallDirector must have an activated AGENT
flag.
ZAND ELNUM=186 d Aktivierung des Leistungsmerkmals mit
Reserve-Parameter 186.
ELNUM=186 e Activation of the feature with reserve
parameter 186.
162.12 Divert Call Request Support of Reroute Internal
162.12.1 Divert Call Requests if the Destination is a

Trunk with Reroute Internal
ACD routes queued calls internally (to internal stations called agents) or
externally (destinations are trunks). There are cases when a trunk is configured
with RERTEINT (Reroute Internal) attribute in AMO LDAT. ACD is able to execute
routings to RERTEINT destinations.
Use Cases
Use Cases for ACD with route to a destination on a trunk with RERTEINT.
The feature takes care of two cases:
1. ACD has configured a RTOFF step to a destination on a trunk with

RERTEINT.
2. An application which monitors ACD queues, diverts the call to a destination

on a trunk with RERTEINT.
For a configuration with
• 200 as trunk access code,
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
• 200-x the LDPLN entry,
• RERTEINT in corresponding AMO LDAT,
• 3400 internal station,
• 3500 external station (configured with closed numbering),
• 9663500 trunk access code for open numbering and external station 3500
the following scenarios are implemented:
1. A call to ACD is queued

ACD has configured a step RTOFF 2003400
ACD executes this step
Call is routed internally to stn 3400

Call is routed externally to 3500


Application invokes DIVERT to destination 2003400
Call is routed internally to stn 3400


A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
The solution applies also for routings to agents which are forwarded to
RERTEINT destinations (to enable execution of forward for agents, set AMO
ACDSD, AGTFWD=YES).
No AMO configuration is necessary to activate this feature.
162.12.2 ACL Set Forward Command Support for

Reroute Internal
ACL set FWD has been enhanced to apply LCR reroute internal functionality to
determine the redirection number and to determine the redirection name from the
redirection number after LCR logic has been applied. The redirection name is
presented on forwarded station display instead of trunk name.
This means that in case of ACL set forward to extern destinations, the trunk name
is determined and presented on forwarded station display next to redirection
number.
Use Cases
Use Cases for ACL set forward command for reroute internal:
For a configuration with
• 200 as trunk access code
• 200-x the LDPLN entry
• RERTEINT in corresponding LDAT
• trunk name ¿NETWORK¿ in corresponding RICHT
• 3400 internal station with name “JOE SMITH”
• 3480 internal DNIT number, with DNI display “ACD ROUTING”
• 3500 external station (configured with closed numbering)
• 9663500 trunk access code for open numbering and external station 3500
the following scenarios are implemented:
1. ACL set FWD for 3412 to 2003480

display of 3412 shows: “Forwarding to 2003400 ACD ROUTING”
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
display of 3412 shows: ¿Forwarding to 2003400 JOE SMITH¿

display of 3412 shows: “Forwarding to 2003500 NETWORK”
4. ACL set FWD for 3412 to 2009663500

display of 3412 shows: “Forwarding to 2009663500 NETWORK2
• The redirection number determined after LCR reroute internal processing is

not validated by ACL (parameters CFVA in AMO COT or AMO ZAND
parameter NOCFW are ignored).
• The name of the redirection number after RERTEINT processing is

determined identically in ACL as in not-RERTEINT scenarios, when internal
redirection number is used in ACL set FWD command.
• If no name is configured for redirection number, then the name misses on

forwarded station display.
• ACL is not clever enough to determine hunt group names, therefore:
– if redirection number is pilot hunt group, trunk name is used
– if redirection number is master hunt group, name of master station is used
• If RERTEINT processing fails or redirection number is not valid, trunk name

is used
• No AMO configuration necessary to activate this feature.
Restricions:
For this CR to work, there’s a limit of maximum 4 accepted trunk access codes
used simultaneously for a destination number.
In other words it means the following:
For a configuration:
• 3400 internal station with name “JOE SMITH”
• 51-x the AMO LDPLN entry
• RERTEINT in corresponding AMO LDAT
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Application Populated Caller ID (APCID)
• 54-x the LDPLN entry
• trunk name “NETWORK” in corresponding AMO RICHT
the expected results are the following:
1. ACL set FWD for 3412 to 515253543400

display of 3412 shows: “Forwarding to 515253543400 JOE SMITH2
2. ACL set FWD for 3412 to 51525354553400

display of 3412 shows: “Forwarding to 515253543400 NETWORK”
3. DIVERT or RTOFF of ACD queued call to 515253543400

call is routed internally to 3400
4. DIVERT or RTOFF of ACD queued call to 51525354553400

routing is rejected, the call remains in ACD queue
162.13 Application Populated Caller ID (APCID)

The caller identification set by applications using ACL Make Call Request is
called Application Populated Caller ID (APCID) and has two parts - number
and name.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Call Center customers want to send out (internally and externally) the agent's
CLIP (e.g. Service Number) according to the task he is involved in. For example,
a Call Center handles calls for different customers (brands) and the agents have
to callback to the clients. They want to show the customers (brands) service
number.

The implementation is based on the two information elements NumberToDisplay
and NameToDisplay that are part of the ACL MakeCallRequest.
NumberToDisplay and NameToDisplay overrides the existing number and

name configured or active (e.g. via PIN) on the physical device used to initiate the
call.
The feature has been implemented from the calling party perspective for:
• analog phones
• digital phones,
• Keysets,
• HFA IP phones.

Rules
1. Application provides only NumberToDisplay (no NameToDisplay). In this
case NameToDisplay can be determined in 3 possible ways:
• If NumberToDisplay is configured as station in the system then its

PERSI name will be provided as NameToDisplay. If this station has no
PERSI, then NameToDisplay is empty.
• If PIN is entered on physical device, then PIN name will be provided as

NameToDisplay. If PIN data contains no name, then NameToDisplay is
empty.
• Otherwise PERSI name of physical device will be provided. If physical

device has no PERSI, then NameToDisplay is empty.
2. Application provides only NameToDisplay (no NumberToDisplay). In this

case the number can be determined in 2 possible ways:
• If PIN is entered on physical device, then PIN number is provided.
• Otherwise physical device number is provided.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
3. If physical device has PIN entered, it is preserved and restored after the call
is terminated.
4. In the called party's Call Log, NumberToDisplay and NameToDisplay are

saved. If this number is called back, it might happen that the call fails. The call
will be established only if NumberToDisplay is configured in the system. The
same happens in case of call back scenarios.
5. If the physical station has restricted number and/or name (i.e. it is secret
station, SSTNO=YES in AMO SBCSU), the presentation of
NumberToDisplay and NameToDisplay will not be restricted. The
presentation will be kept as configured if one of the two parameters misses
and is determined as described above (see 1 and 2).
6. To enable APCID feature for outgoing CO calls, the CO trunks must be

configured with VNCO (send Virtual Subscriber Number to CO) in AMO COT.
If VNCO is not set, the identity of the physical station will be sent to the CO
partner.
7. If physical station has PUBNUM set, it is ignored. NumberToDisplay and

NameToDisplay will be sent to CO partner.
8. To enable APCID feature for call forward scenarios over network, parameters
FWDN and/or FNAN have to be set in AMO COT of the involved trunks.
9. It is the application's responsibilty to use this feature as law enacted. Sending

out a legal number and name than the real calling party's identity to a public
network is always the responsibility of the initiator of the call.
10. If a call is initiated for a station with NumberToDisplay and NameToDisplay,

they will be presented as long as the station is not idle. It means that the
application populated caller id information will not change if the station
invokes any of the following features:
• HOLD - if the agent puts its partner on hold and consults, Application
Populated Caller ID information is used for the consultation call.
• RETRIEVE - Application Populated Caller ID information is presented to

the partners, since MakeCall call has not terminated and agent didn't go
to idle.
• CONSULT - same as HOLD
• RECONNECT - Application Populated Caller ID information is presented

to the partners, since MakeCall call has not terminated and agent didn't
go to idle.
• TRANSFER - there are three cases for TRANSFER
– agent is transferred to a new partner - the new partner will see

Application Populated Caller ID since MakeCall call has not
terminated and agent didn't go to idle.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
Displaying the ACD Pilot Number and Name for Outgoing System-Internal Calls
– agent transfers a CO call to agent 2 - the CO partner is connected to

agent 2 and sees the the original Application Populated Caller ID,
even if MakeCall call has terminated and agent went to idle (the CO
trunks must be configured with VNCO in COT).
– agent transfers a TIE or internal call to agent 2 - agent 2 identity is

presented to the TIE or internal partner. Application Populated Caller
ID is deleted because MakeCall call has terminated and agent went
to idle.
• CONFERENCE - Application Populated Caller ID is still presented to the

partners, since MakeCall call has not terminated and agent didn't go to
idle.
• SINGLE STEP TRANSFER - same as TRANSFER (see TRANSFER -

there are three cases for TRANSFER)
• ALTERNATE - agent toggles from active to held call and always

Application Populated Caller ID is presented

The feature does not need any configuration to activate, due to working with
additional optional parameters in an existing ACL Make Call service.
162.14 Displaying the ACD Pilot Number and Name for Outgoing System-
Internal Calls
ACD pilot number and name of an logged on agent who initiates an internal call
can be configured and displayed.

If an agent is part of a group for which a configuration with pilot number and name
exists (GRPPN and GRPNAME in AMO ACDGP), and the agent makes a call
towards another subscriber, the pilot number and name will be displayed at the
called side. These data will remain valid until the agent becomes idle, regardless
if the agent has logged off in the mean time or gets involved in various scenarios.
The ACD Group Pilot Number (GRPPN) is a number per ACD group which fully
replace the agent's number when an agent places a call. It must be a configured
number in AMO ACDGP which can be called back.
The ACD group pilot number can be assigned to one or more groups of agents.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
The ACD Group Name (GRPNAME) is a text per ACD group which fully replaces
the agent's name when an agent places an internal call (configurable in AMO
ACDGP).
If the name and number of the ACD group should not be presented, then the
corresponding fields in AMO ACDGP must be empty.

• If the agent's station is secret, the new caller ID will not be secret.
• If the agent's call is initiated by an application which sets calling name and
number (see Section 162.13, “Application Populated Caller ID (APCID)”),
then ACD group pilot number and ACD group name will be ignored.
• The ACD Pilot Group Number will be a configured directory number with AMO
DNIT. It must be a number which can be called directly. An ACD Pilot Group
Number can be assigned to one or more groups of agents. A group of agents
can have a Pilot Number if desired. A group of agents can have a Group
Name if desired.
In the called party's Call Log, the caller ID is saved. When the directory
number is called back, the DNI processing will be executed, as configured by
AMO DNIT.
Caller ID is made of two parts, number and name. The number is in this case
the Pilot Number. The name is a configured name per ACD group.
• Pilot Number will be used for all types of calls (internal or external). If
parameter PUBNUM is set in AMO SDAT, it will be set for external calls and
will overwrite ACD Group Pilot Number.
• If an ACD group is configured im AMO ACDGP only with the Pilot Number (no
Group Name), then the Group Name will be taken from AMO DNIT.
If the Pilot Number has DISPLAY parameter set, then it will be used as Group
Name.
If the Pilot Number has no DISPLAY set, then the Group Name will be empty.
• If an ACD group is configured only with the Group Name (no Pilot Number),
then the Pilot Number will be determined in two possible ways:
– If PIN is entered on agent's station, then PIN user number is provided.
– Otherwise agent's physical station number is provided.
• If a call is initiated by an agent with Pilot Number (GRPPN) and Group Name
(GRPNAME) as agent's ID, they will be displayed as long as the station is not
idle. It means that the agent's ID will not change if the station invokes any of
the following features:
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
– Hold - if the agent puts its partner on hold and consults, GRPPN and
GRPNAME are used for the consultation call.
– Retrieve - GRPPN and GRPNAME are presented to the partners, since

agent's call has not terminated and agent didn't go to idle.
– Consult - same as hold
– Reconnect - GRPPN and GRPNAME are presented to the partners,

since agent's call has not terminated and agent didn't go to idle.
– Transfer - there are three cases for TRANSFER:
– Agent is transferred to a new partner - the new partner will see

GRPPN and GRPNAME since agent's call has not terminated and
agent didn't go to idle.
– Agent transfers a CO call to agent 2 - the CO partner is connected

to agent 2 and sees the the original GRPPN and GRPNAME, even if
agent's call has terminated and agent went to idle (the CO trunks
must be configured with VNCO in AMO COT).
– Agent transfers a TIE or internal call to agent 2 - agent 2 identity

is presented to the TIE or internal partner. GRPPN and GRPNAME
are deleted because agent's call has terminated and agent went to
idle.
– Conference - GRPPN and GRPNAME are still presented to the partners,

since agent's call has not terminated and agent didn't go to idle.
– Single Step Transfer - same as TRANSFER
– Alternate - agent toggles from active to held call and always GRPPN and
GRPNAME are presented

ACD Group Pilot Number and Group Name must be configured in AMO ACDGP
with the parameters GRPPN and GRPNAME.
Directory Number set as ACD Group Pilot number must be configured in AMO
DNIT with ROUTING=DRTD or ROUTING=DRTDSA.

Language
ACDGP GRPPN d GRUPPE PILOT NUMMER
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
DNIT Number Presentation

Language
GRPPN e GROUP PILOT NUMBER
GRPNAME d GRUPPENNAME
GRPNAME e GROUP NAME
DNIT ANZEIGE d ANZEIGETEXT
ANZEIGETEXT wird nur ausgewertet, wenn
der Parameter GRPNAME im AMO ACDGP
nicht gesetzt ist.
ANZEIGETEXT gesetzt:
Der Inhalt von ANZEIGETEXT wird als
Gruppenname verwendet.
ANZEIGETEXT nicht gesetzt:
Gruppenname ist leer.
DISPLAY e DISPLAY only will be evaluated if parameter
GRPNAME in AMO ACDGP is not sett!
DISPLAY set:
Content of DIPLAY is used as Group Name,
DISPLAY not set:
Group Name is empty.
162.15 DNIT Number Presentation

If a call that was routed by ACD has reached a Call Director and this call is
transferred by the Call Director to an agent which is logged on and available, then
the original caller sees on the display the DNIT number which was originally
dialed, instead of seeing the agent’s number.
The transfer can be either made by ACL commands SingleStepTransfer or

Consultation and Transfer, or it can be executed as Transfer ringing or Transfer
talking.
The calling station can be any station, and the Call Director can also be an analog
port.
Scenario
A station dials a DNIT number, which is routed via ACD to a group of agents.
If none of the agents are free, then the call is routed to a Call Director.
The caller sees on the display the DNIT number.
The call is held for as long as there is no free agent.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
As soon as an agent becomes free (still logged on and available), the Call
Director transfers the held call to a free agent.
After the transfer is executed and the agent’s station is ringing, the caller will still
see the DNIT number, even after the agent has answered.

• If the agent is forwarded CFU to another destination, then the same
behaviour as in case of an ACD call will be kept: If AGTFWD is set to YES,
then the forwarding will be executed when the CallDirector calls this agent,
otherwise the agent will ring. If the type of forwarding is not unconditional, but
Call Forward No Reply or Call Forward busy, then the call from the Call
Director will be redirected.
• If the agent is a Hunt Group master or member in a Pick-up group, then the
functionality is the same: after the call is transferred and answered, the calling
station will have the DNIT number on the display.

Prerequisite
The agent must be logged on and available.
Configuration:
• Parameter SUPAGTNU is set to YES in AMO ZAND branch ACD.
CHANGE-ZAND:TYPE=ACD,SUPAGTNU=YES;
• The Call Director has to be flagged as CALLDIR in AMO SDAT.
• The behaviour in case of a forwarding set for the agent’s station is controlled
by the AGTFWD parameter from AMO ACDSD.
A31003-H3170-S103-6-7620, 02/2019
acd_homol_en.fm
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Feature Description
163 Flexrouting
163.1.1 The fundamental routing functions of the ACD

package are:
– Incoming call processing.
– Flexible ACD routing.
– Queuing unanswered calls if no agent is free.
– Queuing free agents to answer the next incoming ACD calls.
– Playing music or announcements in an ACD connection while searching

for a free agent.
– Assigning to agent groups on recognition of agent logon.
– Special features for operating terminals to support the agent’s work with
specific ACD function keys and ACD displays (for example, LEDs for
queued calls, ACD status display).
– Additional functions to support the operator console when monitoring

ACD groups and various control tasks (for example, controlling the agent
features).
– Generating a complete ACD event stream (ACL messages) to support

CCMS functions (new: ACDAPP).
163.1.2 Server Functions

– The ACDAPP can operate as an application server with functions for
generating reports and statistics.
– The ACDAP supports various management functions with a range of

reports and statistics which can be implemented by the ACD
administrator and ACD operator console to monitor ACD agent and ACD
system performance.
– An ALAN is used for the connection to the OpenScape 4000. The new
ACL-C link developed is used as a data interface.
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Feature Description
163.1.3 The following is a short description of the

features
ACD features for flexible routing and queuing:
• ACD flexible routing
• ACD look-ahead routing
• ACD day and night service
• Queuing available agents
• Queuing incoming calls
• End-of-shift routing (work schedule table)
• Calendar routing (day and year table)
Features for ACD agents:

• Logon/logoff code
• Mandatory ACD logon
• Automatic logon
• ACD agent mode and status
• Agent autowork
• LED display for agent modes
• LED display for queued ACD calls
• ACD folder status display
• Billing code entry
• Call duration display
Features for the ACD operator console:

• Control of AGT Features (CAF)
• ACD group status display
• Monitoring/silent monitoring
Features for ACD call processing:

• Shared DID lines (threshold value control) --> AMO BUEND
• Automatic incoming call signaling (AICS)
Announcement texts:
• ACD announcement texts
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
User Interface
• ACD music
• Acoustic caller identification
ACD messaging services:

• Short message service
• Emergency message service
Features for source/destination-based routing:

• Destination-based routing
• ACD call destination display
• Source-based routing
• ACD call source display (visual source recognition)
ACDCQ features:
• ACL protocol implementations

A call can be held in up to sixteen call waiting queues. If more than sixteen
destinations are specified for this call, these are only connected when a
destination becomes free. If a call is routed to a free agent who does not reply,
the agent’s status is set to UNAVAILABLE (call distribution disabled) as soon as
the FNA timer expires (after 20 s). The call is then lost.

• Flexrouting can also be operated without a server.
• Flexrouting is assigned a DPLN group with the AMO ZAND. This means that
callers can also reach the destinations they require by calling the appropriate
DPLN.
• The LCR classes of service that are forwarded by the flexrouting feature
when setting up a call belong to the A-station. The LCOSs associated with
trunks are used for stations that do not forward an LCOS.
• Terminals with key module should be used in preference.
• A SUPERVISOR/AGENT must not be a member of a CHESE (SECR) as this

would nullify its flexrouting functions.
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Service Information
• ART 1 (ACD routing table) cannot be modified in the AMO ACDRT. ARTs 2-
15 can only be modified with the master password. Standards should be
defined in these ARTs for emergency operation. They can only be modified in
the SET branch at the operating terminal. The other ARTs can be modified
with a level-2 password at the operating terminal and the agents.
• The Silent Monitoring parameter in the AMO ZAND allows authorized users
to override calls at authorized extensions. The send route is deactivated here.
• An external VMS must be entered as a destination with the following syntax:

VMOWN ACD mailbox
• The attendant console operator can dial ACD numbers directly.
• The attendant console operator can initiate consultation calls with ACD
numbers.
• The CASTMON function in the AMO SDAT can now be configured for analog
terminals.
• There are now only four possible slots for the DMP5L Q2271-X board.
• GDTR rules for routing based on outgoing numbers is now available for up to
22 digits (formerly only sixteen).
• SMTIMER: Timer for delayed activation of silent/tone monitoring can be

configured.
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Service Information
DIMSU Standard OpenScape4500 value ZAND
TYPE APPLICAT GENBUF 0256 TYPE ACD
ACDAGT 0256 ACDCQ 1500 ACDALLOW YES
ACDGRP 0128 ACDLOGON 0256
ACDPRIM 0128 ACDRCG 0512
ACDSHIFT 0300 ACDRT 0300

Threshold
ACDRTX 0900 ACDCALEN 3200
BUEND
ACDMONID 0256 GDTR 2000
ACDTHRH
DNI 2000 DPNI 2000
for max. ACD call
WABE
DAR ACC DAR ACDPGS DAR CAFAFWD DAR RCG

SCSU/SBCSU (I.M.)
ACDWORK ACDPQS CAFDFWD STN (ACD)
STD 17 - 20
ACDSHMSG ACDSGS CAFGRNAV STN (RCG) SECR N
ACDLOGOF ACDSQS CAFGROFF
ACDLOGON CAFGRAV
ACDEMMSG CAFLOGOF
SDAT
ACDNAV CAFNAV
STNO
ACDAV CAFAV
TYPE ATTRIBUT
MONSLNT
AATTR SUPER
AGENT
CD for Tapro subst. for basic query via basic query AGENT&SUPER
Terminal AGENT&AUTOLOG
TAPRO 17 (AGENT 1/12 keys) TAPRO 18 (SUPERVISOR 1/12 keys) AGENT&SUPER&AUTOLOG
TAST01 CH TAST07 ACDNAV TAST01 CH TAST07 ACDNAV DATTR
TAST02 SNR TAST08 ACDWORK TAST02 SNR TAST08 ACDWORK
TAST03 MB TAST09 NAME TAST03 MB TAST09 ADDON
TAST04 SPKR TAST10 NAME TAST04 SPKR TAST10 MONSLNT
TAST05 ACDLOG TAST11 NAME TAST05 ACDLOG TAST11 ACDPGS ACDGRP
TAST06 ACDAV TAST12 CL TAST06 ACDAV TAST12 CL ACDGRP *)

SEARCH FIFO
SUOERRNR
Announcement dev.(opt.) System data PRIMÄR YES
RCSU ACDSD LED YES
ON
ACT YES YES TYPE MSG
*)
OPMODE DEMAND CONT MESSAGE FLASH
OPTYPE FIXED RANDOM MSGCAT AGT SPV EMER WINK
RECAPL ACDR ACDMUS MSGNUM
RECNUM ACDSD
LENGTH TYPE SYS AGENT
AGTIDLEN AGTID *)
max.206x announcements ACDGRP
QFACTOR
max. 32x music AGTPOS
AGTTARGT
DELAYRBT AUTOWK
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Service Information
Figure 126 Generation information, part 1
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Service Information
ACDRT
ART *)
TYPE MAXSTEP TYPE ARTSTEP
STEP
ACT RTGRP ACT WTSEC ACT RTMUS ACT RTREC
ACDGRP SEC MUSNUM RECNUM
WABE
DAR RCG
ACDRS
TYPE DS TYPE RS TYPE CR *)

DSNUM RCG RCG
ENSCH SUN STARTYR

ACDSD
ART MON STARTMON
TYPE CAFRCG
EOS TUE STARTDAY
RCG
ARTDEF WED ENDYR
CAFDN
THU TYPE
FRI RCG
SAT STARTYR
Destination
number Destination and
only source number
Secondary table
DNIT DNIT
TBL DNI TBL DNI
INTRTDN INTRTDN
ROUTING DRTD ROUTING SIAN

Rules Planning direction
DISPLAY DISPLAY
DNIT
RCG RCG
TBL GDTR
PRI 10 PRI 10
GDTRRULE
OVRPRI 5
Primary table
OVRPRI 5
DGTSTR
DNIT
INTRTDN
TBL DNI
INTRTDN
ROUTING DRTSA
GDTRRULE
DISPLAY
RCG
PRI 10
OVRPRI 5
THRSHLD
*) The marked AMOs can be administered from the server
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Figure 127 Generation information, part 2
163.4.1 Defining ACD call numbers, groups and users

The following ACD call numbers are defined:
7351 (hotline 1), 7352 (hotline 2) and 7353 (hotline 3)
Terminals 7361 through 7369 should be assigned AGENT properties. Terminals

7361, 7364, and 7367 should be assigned the SUPERVISOR property.
ACD group 1 should consist of the agent IDs 1637, 2637, and 3637.
ACD group 2 should consist of the agent IDs 4637, 5637, and 6637.
ACD group 3 should consist of the agent IDs 7637, 8637, and 9637.
An agent should be able to log on to random agent telephones using the agent ID.
• Enable ACD in the AMO ZAND and set the silent monitoring variant
CHA-ZAND:TYPE=ACD,ACDALLOW=YES,MONTONE=YES;
If you want silent monitoring to be performed without tones:
SET-ZAND:MONSLNT=YES;
• Configure the codes in the DPLN
ADD-WABE:CD=**10,DAR=ACDLOGON,CHECK=N;
ADD-WABE:CD=##10,DAR=ACDLOGOF,CHECK=N;
ADD-WABE:CD=**11,DAR=ACDAV,CHECK=N;
ADD-WABE:CD=##11,DAR=ACDNAV,CHECK=N;
ADD-WABE:CD=**12,DAR=ACDWORK,CHECK=N;
ADD-WABE:CD=**13,DAR=ACC,CHECK=N;
ADD-WABE:CD=**14,DAR=MONSLNT,CHECK=N;
ADD-WABE:CD=**15,DAR=MONTONE,CHECK=N;
ADD-WABE:CD=**20,DAR=ACDPGS,CHECK=N;
ADD-WABE:CD=##20,DAR=ACDSGS,CHECK=N;
ADD-WABE:CD=**21,DAR=ACDPQS,CHECK=N;
ADD-WABE:CD=##21,DAR=ACDSQS,CHECK=N;
ADD-WABE:CD=**22,DAR=ACDEMMSG,CHECK=N;
ADD-WABE:CD=**23,DAR=ACDSHMSG,CHECK=N;
ADD-WABE:CD=##30,DAR=CAFLOGOF,CHECK=N;
ADD-WABE:CD=**31,DAR=CAFAV,CHECK=N;
ADD-WABE:CD=##31,DAR=CAFNAV,CHECK=N;
ADD-WABE:CD=**32,DAR=CAFGRAV,CHECK=N;
ADD-WABE:CD=##32,DAR=CAFGRNAV,CHECK=N;
ADD-WABE:CD=##33,DAR=CAFGROFF,CHECK=N;
ADD-WABE:CD=**34,DAR=CAFAFWD,CHECK=N;
ADD-WABE:CD=##34,DAR=CAFDFWD,CHECK=N;
• Display the call numbers that are required for flexrouting (agent, supervisor
call number and hotline 1-3)
DIS-WABE:TYPE=GEN,CD=7350&&7369,DAR=STN;
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
• Configure terminals 7361 && 7369

ADD-
SBCSU:STNO=7361&&7369,OPT=OPTI,CONN=DIR,DVCFIG=OPTISET,COS1=1
3,COS2=11,LCOSV1=5,LCOSV2=1,LCOSD1=5,LCOSD2=1,DPLN=0,REP=1,ST
D=17;
CHA-TAPRO:STNO=7361&7364&7367,STD=18;
ADD-PERSI:TYPE=STN,STNO=7361,NAME=SUPERVISOR,PIN1=1637;
ADD-PERSI:TYPE=STN,STNO=7362,NAME=AGENT,PIN1=2637;
ADD-PERSI:TYPE=STN,STNO=7369,NAME=AGENT,PIN1=9637;
• Assign agent/supervisor skills for the terminals
– Activate stations 7361, 7364, and 7367 as SUPERVISOR with the

attributes:
agent and supervisor, automatic logon and monitoring authorization
CHANGE-
SDAT:STNO=7361,TYPE=ATTRIBUT,AATTR=AGENT&SUPER&AUTOLOG&CAS
TMON&CAF;
CHANGE-
TMON&CAF;
CHANGE-
TMON&CAF;
– Activate stations 7362, 7363, 7365, 7366, 7368, and 7369 as AGENT with
the attribute:
agent can be monitored
CHA-
SDAT:STNO=7362&&7363,TYPE=ATTRIBUT,AATTR=AGENT&CBSTMON;
CHA-
SDAT:STNO=7365&&7366,TYPE=ATTRIBUT,AATTR=AGENT&CBSTMON;
CHA-
SDAT:STNO=7368&&7369,TYPE=ATTRIBUT,AATTR=AGENT&CBSTMON;
• Set the ACD system data
– ID= 4-digit, priority increased after 20 s, ID-based identification, ringback

tone delay of 3 s.
– When setting AGTIDTYP=ID, the ID number is used to create the link to

the ACD group when logging the agent on.
CHA-
ACDSD:TYPE=SYS,AGTIDLEN=4,QFACTOR=20,AGTTARGT,DELAYRBT=3;
– Check if the ROUTREQ timer is less than the DELAYRBT
DISPLAY-CTIME:TYPESWU=CP1;
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
– The DELAYRBT should not exceed five seconds. The maximum length in
the OpenScape 4000 is approximately 30 seconds (protocol timer T310).
The exact value depends on the partner system, for example, Telekom
• Configure ACD group 1

The LED threshold values are based on the number of waiting calls.
This is the primary group of supervisor 7361.
ADD-ACDGP:ACDGRP=1,TYPE=NORMAL,SEARCH=FIFO,
SUPEXT=7361,PRIMARY=YES,LED=YES,ON=1,FLASH=2,WINK=3;
Assign agents to group 1 (AUTOEXT is only required if the call number is
needed for identification. No other agents can then log on to this device with
their own call number).
ADD-AGENT:AGTID=1637,ACDGRP=1,AGTTYPE=NORMAL,AUTOWK=5;
ADD-AGENT:AGTID=3637,ACDGRP=1,AGTTYPE=NORMAL,AUTOWK=5;
Assign agents to group 2 (AUTOEXT, see group 1).
Assign agents to group 3 (AUTOEXT, see group 1).
• Create short messages
– Create messages to the supervisor.

CHA-ACDSD:TYPE=MSG,MESSAGE=PLEASE
REMOVE,MSGCAT=SPV,MSGNUM=1;
CHA-ACDSD:TYPE=MSG,MESSAGE=ASSISTANCE
REQUESTED,MSGCAT=SPV,MSGNUM=2;
– Create messages to the agent.
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
CHA-ACDSD:TYPE=MSG,MESSAGE=PREPARE
REMOVAL,MSGCAT=AGT,MSGNUM=1;
CHA-ACDSD:TYPE=MSG,MESSAGE=POOR
PERFORMANCE,MSGCAT=AGT,MSGNUM=2;
– Configure an emergency message.
CHA-ACDSD:TYPE=MSG,MESSAGE=HEART ATTACK,MSGCAT=EMER;
163.4.2 Defining routes
ART 16 ART 17 ART 18
Rngbk tn del. Rngbk tn del. Rngbk tn del.
Group 1 Group 2 Group 3
Group 2 Group 3 Group 1
old. calls > 20 s. old. calls>20s. old. calls > 20 s.
Wait for 40 s. Wait for 40 s. Wait for 40 s.
Disconnect Disconnect Disconnect
Overflow pos. 7340 Overflow pos. 7341 Overflow pos. 7342
ART 19
7300 Destination after end of shift and

on particular days
Figure 128 Overview of route configuration
ACD routes 2-15 can only be modified with SET.

SET-ACDRT:ART=2,TYPE=MAX,MAXSTEP=5;
• Configure the ACD routing tables
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
• Configure ACD routing table 16

ADD-ACDRT:ART=16,MAXSTEP=8;
Configure ACD route 16:
Go to ACD group 1 with overflow to ACD group 2 and subsequent
breakout to station 7340 if a user has been waiting in the queue for more
than 20 s.
CHA-ACDRT:ART=16,TYPE=ARTSTEP,STEP=1,ACT=DELAYRB;
CHA-ACDRT:ART=16,TYPE=ARTSTEP,STEP=2,ACT=RTGRP,ACDGRP=1;
CHA-ACDRT:ART=16,TYPE=ARTSTEP,STEP=4,ACT=COND,CACDGRP=1,
CGSTEP=7,TEST=OLDINQGT,VALOLD=00-20;
CHA-ACDRT:ART=16,TYPE=ARTSTEP,STEP=5,ACT=WTSEC,SEC=40;
CHA-ACDRT:ART=16,TYPE=ARTSTEP,STEP=6,ACT=DISCON;
CHA-
ACDRT:ART=16,TYPE=ARTSTEP,STEP=7,ACT=RTEXT,EXTNUM=7340;
CHA-ACDRT:ART=16,TYPE=ARTSTEP,STEP=8,ACT=DISCON;
COPY-ACDRT:ART=16,NEWART=17;
than 20 s.
CHA-
ACDRT:ART=17,TYPE=ARTSTEP,STEP=7,ACT=RTEXT,EXTNUM=7341;
COPY-ACDRT:ART=17,NEWART=18;
than 20 s.
CHA-
ACDRT:ART=18,TYPE=ARTSTEP,STEP=7,ACT=RTEXT,EXTNUM=7342;
• Configure ACD routing table 19 for end-of-shift, Sundays, and holidays
ADD-ACDRT:ART=19, MAXSTEP=3;
CHA-
ACDRT:ART=19,TYPE=ARTSTEP,STEP=2,ACT=RTEXT,EXTNUM=7300;
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
• Configure and assign route control group (RCG) call numbers
– Configure RCG call numbers (call numbers only used by flexrouting)

Only digits 0-9 are permitted. You can use the asterisk (*) to delete the
AMO ACDSD 
entry.
ADD-WABE:CD=70001&&70003,DAR=RCG;
– Assign RCG call numbers to the RCGs.
CHA-ACDSD:TYPE=CAFRCG,RCG=1,CAFDN=70001;
CHA-ACDSD:TYPE=CAFRCG,RCG=2,CAFDN=70002;
CHA-ACDSD:TYPE=CAFRCG,RCG=3,CAFDN=70003;
• Create shift schedules
– Extend shift schedules with CHANGE only.

ADD-ACDRS:TYPE=DS,DSNUM=1,SHIFT=17-
00,ART=16,EOS=YES,ARTDEF=19;
ADD-ACDRT:TYPE=DS,DSNUM=2,SHIFT=18-
00,ART=17,EOS=NO,ARTDEF=19;
00,ART=18,EOS=NO,ARTDEF=19;
59,ART=19,EOS=NO,ARTDEF=19;
– Configure day routing tables.
ADD-
ACDRT:TYPE=RS,RCG=1,SUN=4,MON=1,TUE=1,WED=1,THU=1,FRI=1,SA
T=4;
ADD-
T=4;
ADD-
T=4;
– Configure calendar days with special routing (holidays).
ADD-
ACDRT:TYPE=CR,RCG=1,STARTMON=12,STARTDAY=24,ENDMON=12,ENDD
AY=26,DSNUM=4;
ADD-
AY=26,DSNUM=4;
ADD-
AY=26,DSNUM=4;
ADD-
ACDRT:TYPE=CR,RCG=3,STARTMON=11,STARTDAY=1,ENDMON=11,ENDDA
Y=1,DSNUM=4;
ADD-
ACDRT:TYPE=CR,RCG=2,STARTMON=11,STARTDAY=1,ENDMON=11,ENDDA
Y=1,DSNUM=4;
ADD-ACDRT:TYPE=CR,RCG=1,STARTMON=11,STARTDAY=1,ENDMON=11,
ENDDAY=1,DSNUM=4;
ADD-ACDRT:TYPE=CR,RCG=1,STARTMON=1,STARTDAY=1,ENDMON=1,
ENDDAY=1,DSNUM=4;
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
ADD-
ACDRT:TYPE=CR,RCG=2,STARTMON=3,STARTDAY=1,ENDMON=1,ENDDAY=
1,DSNUM=4;
ADD-
1,DSNUM=4;
ADD-
5,DSNUM=4;
ADD-
5,DSNUM=4;
ADD-
5,DSNUM=4;
• Configure destination-dependent routing
AMO DNI (Directory number information translation)
For normal users
– Destination selection based on the number dialed (7351)

ADD-DNIT:TBL=DNI,INTRTDN=7351,ROUTING=DRTD,
DISPLAY="CALLS VIA 7351", ACD=YES,RCG=1,PRI=30,OVRPRI=20;
• Configure destination- and source-based routing
STN: 7141 7354

7241 >
CALLED number evaluation CALLING number evaluation

71* #
71**
71***
RCG 1 RCG 4
Figure 129 Overview of route configuration
AMO DNI (Directory number information translation)
For preferred users
Destination selection based on the number dialed (7354) and the calling number
(calling party’s call number).
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Relevant AMOs
• Route for source- and destination-based routing

ADD-WABE:CD=70004,DAR=RCG;
• Call number for internal flexrouting addressing (call number is not dialed)
• Define flexrouting route 4
CHA-ACDSD:TYPE=CAFRCG,RCG=4,CAFDN=70004;
• Route for special stations with disconnection if extension is busy
ADD-ACDRT:ART=20,MAXSTEP=3;
CHA-ACDRT:ART=20,TYPE=ARTSTEP,STEP=2,ACT=RTEXT,EXTNUM=7367;
• Day shift number for special customers
00,ART=20,EOS=NO,ARTDEF=19;
ADD-
ACDRT:TYPE=RS,RCG=4,SUN=4,MON=5,TUE=5,WED=5,THU=5,FRI=5,SAT=4
;
• Route for special stations
ADD-DNIT:TBL=DNI , INTRTDN=70100 ,
GDTRRULE=0,DISPLAY="Customer King
7354",ACD=YES,RCG=4,PRI=30,OVRPRI=20,AUDSRCID=0,THRSHLD=*;
• Definition of special stations (all that begin with 71)
ADD-DNIT:TBL=GDTR , GDTRRULE=1 , DGTSTR=71** , INTRTDN=70100
;
• Miscellaneous stations
ADD-DNIT:TBL=DNI,INTRTDN=7354,GDTRRULE=1,DISPLAY="CUSTOMER
Normal
7354",ACD=YES,RCG=1,PRI=30,OVRPRI=20,AUDSRCID=0,THRSHLD=*;
163.5 Relevant AMOs

Language
ACDGP ACDGRP d ACD Gruppen Nummer
e acd group number
SUCHE d Suchverfahren nach freien Agenten in dieser
ACD Gruppe
SEARCH e search method for acd group
SUPERNR d Supervisor Rufnummer für diese ACD Gruppe
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Relevant AMOs

Language
e primary option for acd group
PRIMAER d Hauptgruppen Funktion für diese ACD Gruppe
PRIMARY e primary option for acd group
LED d Led Funktion für diese ACD Gruppe
e led options for acd group
LEDEIN d Schwellwert für >Led leuchtet
ON e led on option
LEDLANG d Schwellwert für >Led, blinkt mit langer Pause
FLASH flash led option
LEDKURZ d Schwellwert für >Led, blinkt mit kurzer Pause
WINK e wink led option
ACDRS ANFJAHR d Anfangsdatum: Jahr
STARTYR e start year of range entity
ANFMON d Anfangsdatum: Monat
STARTMON e start month of range entity
ANFTAG d Anfangsdatum: Tag
STARTDAY e start day of range entity
ART d ACD Routing Tabelle der Arbeitsschicht
e acd routing table
ARTDEF d Voreingestellte Art
e acd routing table default
ASPLAN d Arbeitsschichtplan
DSNUM e day shift number
ASPLNDI d Arbeitsschichtplan für Dienstag
TUE e tuesday day shift number
ASPLNDO d Arbeitsschichtplan für Donnerstag
THU e thursday day shift number
ASPLANFR d Arbeitsschichtplan für Freitag
FRI e friday day shift number
ASPLANMI d Arbeitsschichtplan für Mittwoch
WED e wednesday day shift number
ASPLANMO d Arbeitsschichtplan für Montag
MON e monday day shift number
ASPLANSA d Arbeitsschichtplan für Samstag
SAT e saturday day shift number
ASPLANSO d Arbeitsschichtplan für Sonntag
SUN e sunday day shift number
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Relevant AMOs

Language
ENDJAHR d Endedatum: Jahr
ENDYR e end year of range entity
ENDMON d Endedatum: Monat
ENDMON e end month of range entity
ENDTAG d Endedatum: Tag
ENDDAY e end day of range entity
ENDSCH d Ende der Arbeitsschicht
SHIFT e shift end time
RCG d Route Controll Gruppe
e route control group
SEF d Schichtendefunktion
EOS e end of shift option
TYP d Tabellentyp
TYPE e type of table
ACDRT ACDGRP d Nummer der ACD Gruppe
e acd group number
AGENTEN d Anzahl der Agenten für Vergleich
VALAGT e condition compare value for agents
AGTID d Identifikationsnummer des Agenten
e agent id
AKTION d Welche Aktion wird beim Step ausgeführt
TEST e type of conditional test
ANRUFE d Anzahl der wartenden Anrufe für Vergleich
VALCAL e condition compare value for calls queued
ANSAGENR d Nummer der Sprachansage
RECNUM e recorded announcement number
ART d Nummer der ACD Routing Tabelle
e acd routing table number
EXTTLNNU d Externe Teilnehmerrufnummer
EXTNUM e extension number
MAXSTEP d Anzahl der möglichen Steps
e maximum step of art
MUSIKNR d Nummer der Wartemusik
MUSNUM e music number
NEUART d Nummer der neuen ACD Routing Tabelle
NEWART e acd routing table number for copied art
PACDGRP d Diese ACD Gruppe wird überprüft
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Relevant AMOs

Language
CACDGRP e acd group for conditional checks
PRUEFBED d Typ der Prüfbedingung
TEST e type of conditional test
SEK d Wartezeit in Sekunden
SEC e seconds
STEP d Step-Nummer
e step number
TLNNU d Interne Tln-Rufnummer
e
TYP d Was soll administriert werden
TYPE e function mode
ZEIT d Wartezeit für Vergleich
VALOLD e condition compare value for oldest call in queue
ZIEL d Sprungziel ( Fortsetzung mit diesem Step )
GSTEP e step goto number
ZIELBED d Sprungziel ( wenn Bedingung erfüllt )
CGSTEP e step goto number for conditional step
ACDSD AGTIDLAE d Länge der Identifikationsnummer der ACD
Agenten
AGTIDLEN e acd agent's id length
AGTIDTYP d Wie werden die ACD Agenten identifiziert
AGTTARGT e acd agent target
FTONVERZ d Freiton - Verzögerung in Sekunden
DELAYRBT e delay ringback timer
NACHRNUM d Nachrichtennummer
MSGNUM e message number
NACHRTXT d Nachrichtentext
MESSAGE e message text
NACHRTYP d Nachrichtentyp
MSGCAT e message category
PRIOZEIT d Zeit in Sek. bis ein wart. Anruf eine höhere Prio.
bekommt
QFACTOR e queue factor timer
RCG d Route Control Group
e route control group
RCGADR d REG Adressennummer ( für CAF )
CAFDN e control agent facility directory number for rcg
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Relevant AMOs

Language
TYP d Tabellentyp
TYPE e type of table
AGENT ACDGRP d ACD Gruppen-Nummer
e acd group number
AGTID d Identifikations-Nummer des Agenten
e agent's identification number
AGTPOS d Position des Agenten in der ACD Gruppe
e agent's position in a group
AUTOARB d Zeit in Sekunden zur Nachbearbeitung eines
Anrufs
AUTOWK e auto work time
AUTORNR d Rufnummer für automatisches anmelden
AUTOEXT e auto logon extension number
NEUID d Neue Identifikations-Nummer des Agenten
NEWID e agent's new identification number
TYP d Was soll gelöscht werden.
TYPE e type of deletion
DIMSU ACDAGT d Anzahl der ACD Agenten
e number of acd (automatic call distribution)
agents
ACDCQ d Anzahl der Einträge im ACD Anrufordner
e number of acd call-queuing pool elements
ACDGRP d Anzahl der ACD Gruppen
e number of acd groups
ACDKALEN d Anzahl der Einträge für ACD Kalender-Routing
ACDCALEN e number of calendar routing entries
ACDLOGON d Anzahl der Agenten, die zur gleichen Zeit
angemeldet sind
e number of acd agents logged on at once
ACDMONID d Anzahl der ACD Monitorpunkte ( nur ACD - G )
e no. of monitored id sets (e.g. acd agents, trunk
groups ...)
ACDPRIM d Anzahl der ACD Primär - Agenten
e number of primary acd agent positions
ACDRCG d Anzahl der ACD Routing - Control Gruppen
e number of acd route-control groups
ACDRT d Anzahl der ACD Routing Tabellen
e number of acd routing step tables
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Relevant AMOs

Language
ACDRTX d Anzahl der ACD Routing Zusatztabellen
e number of auxiliary acd routing step tables
ACDSCH d Anzahl der ACD Schichtzeiten
ACDSHIFT e number of acd shifts
DNI d Anzahl der Einträge für die Umwertung der B-
Rufnr.
e number of directory number information table
indices
DPDNI d Anzahl der Datenpoolelemente für den Dimsu
Parameter DNI
e number of datapool elements reserved for dimsu
parameter dni
GDTR d Anzahl der Einträge für die Umwertung der A-
Rufnr.
e number of general digit translation table entries
DNIT ANSAGENR d Nummer der Sprachansage
AUDSRCID e audible source identification
ANZEIGE d Anzeigetext für das gerufene Endgerät
DISPLAY e called device display
GDTRRGL d Nummer einer GDTR-Regel zur SID/ANI
Umsetzung
e
INTRTADR d Interne Routing Adressnummer
INTRTDN e internal routing directory number
MAXANRUF d Anzahl gleichzeitiger ACD Anrufe bei dieser Reg.
THRSHLD e number of incoming trunk acd calls
NGDTRRGL d Neue Nummer einer GDR-Regel zur SID/ANI
Umsetzung
NEWRULE e new gdtr element with sid/ani rule
NREGEL d Neue Regel zur allg. Zeichenumsetzung
NEWDGTS e new digit string
PRIO d Priotät des ACD Anrufs in Anrufordner
PRI e priority for acd call queued to acd group
RCG d Route Control Group
e route control gruppe
REGEL d Regel zur allg. Zeichenumsetzung
DGTSTR e digit string for dnis or sid/ani
ROUTING d Verwendetes Verfahren für das Routing
e type of routing to take place
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Relevant AMOs

Language
TAB d Auswahl der betreffenden Tabelle
TBL e used table for directory number information and
translation
UEBLPRIO d Priorität des ACD Anrufs nach Überlauf
OVRPRI e overflow priority for acd call
RCSU ANSLAE Länge der Ansage in Sekunden
LENGTH e length of recorded announcement in seconds
ANSNR d Nummer der Sprachansage
RECNUM e number of recorded announcement
ANWENDNG d Anwendung des Ansagegerätes
RECAPL e application of the selected recorder
ANZ d Anzahl der einzuricht. Ansagegeräte
NO e number of recorders to be created
BETRART d Betriebsart des Ansagegerätes
OPMODE e operation mode for recorders
CIRCIDX d Index zur Timerblocktabelle für SLMA
e index into timer block table for slma1 circuit
MUSNR Nummer der Musik
MUSNUM e number of music recording
WIEDART Wiedergabeart des Ansagegerätes
OPTYPE e operation type for recorder
SDAT AMERK d Teilnehmermerkmale ausfügen
DATTR e delete subscriber attribute
EMERK d Teilnehmermerkmale einfügen
AATTR e add subscriber attribute
TYP d Typ der Administration
TYPE e type of administration
TAPRO ACC d Account Code ( Gespräch makieren )
e account code
ACDAGTN d Nachrichten zum Agenten schicken
ACDAGTM e send message to agent
ACDARB d Agent arbeitet
ACDWORK e agent work
ACDLOG d Agent logon/logoff
e agent logon/logoff
ACDNOTN d Notfallnachricht
ACDEMMSG e emergency message
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Relevant AMOs

Language
ACDNVB d Agent nicht verfügbar
ACDNAV e agent not available
ACDPGS d Primärer Gruppenstatus
e primary group status
ACDPQS d Primärer Queue Status
e primary queue status
ACDSGS d Sekundärer Gruppenstatus
e secondary group status
ACDSPVN d Nachricht zum Supervisor senden
e send message to supervisor
ACDSQS d Sekundärer queue Status
e secondary queue status
ACDVB d Agent verfügbar
ACDAV e agent available
ACK d Nachricht Quittieren
e message acknowledgment
MITHOERT d Mithören mit Ton
MONTONE e tone monitoring
WABE ACC d Account Code
e account code
ACDARB d Agent arbeitet
ACDWORK e agent work
ACDKURZN d Kurznachrichten
ACDSHMSG e short message
ACDLOGOF d Agent logogg
e agent logoff
ACDLOGON d Agent logon
e agent logon
ACDNOTN d Notfallnachricht
ACDEMMSG e emergency message
ACDNVB d Agent nicht verfügbar
ACDNAV e agent not available
ACDPGS d Primär Grupen Status
e primary group status
ACDPQS d Primär Queue SStatus
e primary queue status
ACDSGS d Sekundär Gruppen Status
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Relevant AMOs

Language
e secondary group status
ACDSQS d Sekundär Queue Status
e secondary queue status
ACDVB d Agent Verfügbar
ACDAV e agent available
CAFAULA d CAF ausschalten der Umleitung der RCG
CAFDFWD e caf deactivate forwarding of rcg
CAFAULE d CAF einschalten der Umleitung der RCG
CAFAFWD e caf activate forward of rcg
CAFGRNVB d CAF Gruppe nicht verfügbar
CAFGRNAV e caf group not available
CAFGROFF d CAF Gruppe logoff
CAFGROFF e caf group logoff
CAFGRVB d CAF Gruppe verfügbar
CAFGRAV e caf group available
CAFLOGOF d CAF Agent lofoff
CAFLOGOF e caf agent logoff
CAFNVB d CAF Agent nicht verfügbar
CAFNAV e caf agent not available
CAFVB d CAF Agent verfügbar
CAFAV e caf agent available
RCG d Route Control Group Nummer
e route control group number
ZAND ACDERL d FlexRouting Schalten
ACDALLOW e FlexRouting allowed
MITHOERT d FlexRouting Mithören mit Ton
MONTONE e FlexRouting tone monitoring
MITHOER d FlexRouting Mithören ohne Ton ( nur über
SETZEN )
MONSLNT e FlexRouting Silent monitoring
A31003-H3170-S103-6-7620, 02/2019
flexrout_en.fm
Flexrouting
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
sil_tone_monit_pin_en.fm
Overview
164 Flexrouting Silent/Tone Monitoring PIN
164.1 Overview
In certain countries it is permissable for calls to be monitored either silently or with
the injection of a tone. Two features “Silent Monitoring” and “Tone Monitoring” are
available for certain class marked stations to enable them to carry out this
function. Also stations who are to be Silent/Tone monitored have also to be
classmarked. As an additional security feature the monitoring stations can be
forced to input a PIN prior to executing Silent/Tone monitoring.
Authorised User presses Tone/Silent Monitor

key/code and Inputs Pin number
Silent/Tone monitoring
access is allowed for Pin
duration Conversation
Tone or Silently
Monitored

The Silent/Tone Monitoring PIN feature is built upon the the ACD Silent/Tone
Monitoring feature and the PIN (Personal Identification Number) feature.
It is an optional security enhancement for the ACD Silent/Tone Monitoring feature

which requires the user to enter a valid password before activating Silent/Tone
Monitoring. The password used will be a local or network PIN number. COPINs
1-4 and the ID card PIN are valid as long as the home station of the PIN
possesses the “can activate silent/tone monitoring” attribute. If the PIN’s
associated home station number is not configured with this monitoring
authorization, the monitoring activation request is denied.
When the switch is configured for the network PIN mode of operation, the
connection between the local switch and the remote switch where the home
station of the PIN may be located, must be CorNet-NQ end to end.
If the PIN was required for monitoring activation, it will be deactivated when
monitoring ends (the only exception is the ID card PIN which will remain active
even after monitoring ends.) If, however, the PIN was not required for monitoring
activation, PIN deactivation occurs only for short PIN.
A31003-H3170-S103-6-7620, 02/2019
User Interface
It is also possible to silent monitor all agents using an application which will record
all calls. When an agent is not on the phone but is monitored, the supervisor
normally hears "please hold the line" every 4 seconds. This means that a record
of 8 hours will contain a lot useless information. Using a parameter in AMO
ZANDE it is possible to suppress this message and the application stops
recording when there is no line activity for 6 seconds.
It is also possible to monitor a consultation call. This feature is called “Extended

Silent Monitoring/Tone Monitoring”.
164.3.1 Feature Activation with Positive

Acknowledgement
If the system flag for the Monitoring with PIN is enabled, PIN activation must
precede activation of Silent/Tone Monitoring.
The user can activate a PIN by using the service menu, by inserting the ID PIN
chip card into the telephone device, or by employing the PIN Manual feature
dialing procedure. If the entered PIN is valid, it will remain active for the time
configured in its COPIN. If the system flag for the Monitoring Pin is not enabled,
the Silent/Tone Monitoring feature is activated using the previous unsecure
activation procedure.
Tone monitoring may be activated by pressing the MONTONE key configured on

the digite device or by dialing the access code for Tone Monitoring.
Silent monitoring may be activated by pressing the ADDON key configured on the
digite device or by dialing the access code for Silent Monitoring.
After a PIN has been entered, Silent/Tone Monitoring can be activated during the
time the PIN is active. When a PIN is activated, the user hears dial tone and can
then start the activation of Silent/Tone monitoring without first going on hook. In
the case of “long” PIN or the ID card PIN, the user may go on hook and then
activate monitoring at a later point in time as long the PIN is active.
164.3.2 Feature Activation with Negative

Acknowledgement
An user attempting to activate the Silent/Tone Monitoring feature without an
active PIN when a PIN is required, will receive the message “Not authorized” after
the Silent/Tone Monitoring access code has been entered or after the Silent/Tone
Monitoring key has been depressed.
A31003-H3170-S103-6-7620, 02/2019
Service Information
164.3.3 Feature Deactivation

When the Silent/Tone Monitoring party goes on hook, monitoring is deactivated.
If the Monitoring PIN was a requirement for the activation of Monitoring, the active
“short” or “long” PIN is also deactivated and the message “Identification deleted”
is displayed for digites with display. The ID card PIN is not deactivated.
If, however, the Monitoring PIN system parameter was not a requirement for
Monitoring, the “long” PIN or the ID card PIN is not deactivated. The short PIN is
deactivated as is usually done after one call.

A station or a recording device, which has the proper authorizations can listen the
calls made by a another station to a third party. Only the basic calls can be
listened and when the monitored station leaves the actual call and goes ino
consultation with another subscriber or trunk, the monitoring is interrupted and
the monitor hears the “Please hold” announcement. It is also possible to monitor
a consultation call.
The monitoring will be extended with the same type of monitoring as the
initial call! For example, if the monitor has activated the Tone Monitoring, for the
consultation call the tone will also be present, given the condition that the
extended tone monitoring is enabled.
The monitoring of the consultation call is started only if the Extended Monitoring
is enabled for the whole system by means of AMO ZANDE through the
parameters EXTMNTON or EXTSLTMN.
The monitoring can be either silent or with tone and can only be activated from
a Digite or an Anate phone.
Only Digites and Anates can be monitored as targets.
The supported partners of the monitored station are:
• Digital phones
• Analog phones
• SIP devices
• Functional devices
• Trunks (digital/analog)
silent
The silent monitoring implies that the listened parties are not notified about the
fact that they are being monitored.
A31003-H3170-S103-6-7620, 02/2019
Feature Interactions
tone
The tone monitoring means that the monitored and its partner are hearing a tone
which lets them know that their call is monitored by another station.
164.5 Feature Interactions

Call Forwarding:
If the montiored party attempts to initiate a consultation call towards a forwarded
station, when the forward destination picks up the call, the conversation will be
monitored, regardless of the forwarding type ( CF unconditional, CF busy, CF no
reply).
Pickup Groups:
If the montiored party attempts to initiate a consultation call towards a station
which is member in a PickUp Group and the call is picked-up by another member,
the call will be monitored.
Hunting Groups:
If the montiored party attempts to initiate a consultation call towards a station
which is a Hunt Group Master, and the call is answerded by another member, the
call will be monitored.
If the monitored party dials the number of a HuntGroup and the call advances to
a member which answers is, the call will be monitored.
Direct Call Pickup:

If the montiored party attempts to initiate a consultation call towards a station and
another station answers the call using the Direct Call Pickup feature, the call will
be monitored.
Enhanced Silent Monitoring:

If Enhanced Silent Monitoring is active in the system (SILMON is active in AMO
FEASU) it cannot be invoked and will have no effect during Extended Silent
Monitoring scenarios.

• Set the system parameter that enables the Monitoring PIN (Default value is
NO):
A31003-H3170-S103-6-7620, 02/2019
CHA-ACDSD:TYPE=SYS,MONPIN=YES;
IMPORTANT: If the MONPIN parameter is set to NO but all other conditions

are valid the Silent/Tone monitoring function works but is not reliant on secure
access. It is only required that the station is classmarked. ANY user at that
station can Silent/Tone monitor.
• Allow Silent Monitoring in the system:

SET-ZAND:MONSLNT=YES;
• Allow the ACD feature and Tone Monitoring in the system:
CHA-ZAND:TYPE=ACD,ACDALLOW=YES,MONTONE=YES;
• Add the digits for dial access to the Silent Monitoring feature:
ADD-WABE:CD=728,DAR=MONSLNT;
• Add the digits for dial access to the Tone Monitoring feature:
ADD-WABE:CD=729,DAR=MONTONE;
• Add the Silent Monitoring key to a phone:
CHA-TAPRO:STNO=3356,KY04=ADDON;
• Add the Tone Monitoring key to a phone:
CHA-TAPRO:STNO=3356,KY05=MONTONE;
• Enable monitoring authorization for a particular station:
CHA-SDAT:STNO=3358,TYPE=ATTRIBUT,AATTR=CASTMON;
• Enable the target station to be silent/tone monitored:
CHA-SDAT:STNO=3357,TYPE=ATTRIBUT,AATTR=CBSTMON;
• Don’t activate SILMON in AMO FEASU.
CHANGE-FEASU:TYPE=D,CM=SILMON;
IMPORTANT: The SILMON parameter in AMO FEASU is used for activating

a feature which allows the monitor to initiate a conference with the monitored
parties, which is not possible in a Silent/Tone Monitoring scenario. 
By enabling this feature, the 'normal' Silent/Tone Monitoring will be widely
affected, with the displays and the behaviour of the subscribers being
modified (tones, keys pressed, states, etc.).
• Suppress „Please hold the line“ when an silent monitored agent is not on the
phone
CHANGE-ZANDE:TYPE=ACD,NODHOLDT=YES;
• Activation of the feature “Extended Silent/Tone Monitoring”
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
CHANGE-ZANDE:TYPE=ACD,EXMNTONE=YES; /*Tone monitoring

CHANGE-ZANDE:TYPE=ACD,EXTSLTMN=YES; /* Silent monitoring
164.7 Relevant AMOs

ACDSD MONPIN e New parameter to signify whether the PIN
password is required to activate Silent/Tone
Monitoring
MONPIN d Neuer Parameter, der definiert, ob für die
Aktivierung des Mithörens ohne/mit Ton das
PIN-Passwort benötigt wird.
FEASU SILMON e Enhanced Silent/Tone Monitoring
SILMON d Verbessertes Mithören ohne/mit Ton
SDAT ATTRIBUT e Set CASTMON for the home station of the
PIN used, and CBSTMON for the monitored
target station
MERKMAL CASTMON für die Heimatstation der
benutzten PIN und CBSTMON für die
Sprechstelle setzen, die mitgehört werden
kann.
TAPRO KYnn e Configure MONTONE (key for activating
Tone Monitoring) & ADDON (key for
activating Silent Monitoring) on a digite
device
TDnn d Auf einem Digite MITHOERT (Taste für
Aktivierung Mithören mit Ton) und ZZU
(Taste für Aktivierung Mithören ohne Ton)
konfigurieren.
WABE CD e Configure the access code for MONSLNT
and MONTONE
KZP d Kennzahl für MITHOER und MITHOERT
konfigurieren.
ZAND ACD e ACDALLOW must be set to yes.
ACD d ACDERL muss auf JA gesetzt sein.
MONTONE=YES e Tone Monitoiring
MITHOERT=YES d Mithören mit Ton
MONSLNT=YES e Silent Monitoring
MITHOER=JA d Mithören ohne Ton (Silent Monitoring)
ZANDE EXMNTONE e Extended tone monitoring
EXTMNTON d Erweitertes Ton Monitoring
EXTSLTMN e Extended silent monitoring
EXTSLTMN d Erweitertes Silent Monitoring
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs

SILMON e If this parameter is set, the 'normal' Silent/
Tone Monitoring will be widely affected, with
the displays and the behaviour of the
subscribers being modified.
SILMON d Ist dieser Parameter gesetzt, wirkt sich das
auf das "normale" Mithören ohne/mit Ton
aus, insbesondere auf die Anzeigen und
das Verhalten der Teilnehmer (Töne,
Tasten, Status usw.)
NOHOLDT e When this parameter is set to YES the silent
monitoring party (supervisor) hears silence
(instead of „Please hold the line“) if the
monitored party (agent) is not talking on the
phone.
KHTON d Wenn der Parameter gesetzt ist, hört der
Silent Monitoring Teilnehmer (Supervisor)
Stille (anstatt Halteton / -musik), wenn der
abgehörte Agent sich nicht im Rufzustand
befindet.
A31003-H3170-S103-6-7620, 02/2019
Relevant AMOs
A31003-H3170-S103-6-7620, 02/2019
whisper_announcement_en.fm
Whisper Annoucement
Feature Description
165 Whisper Annoucement

To create a feature which allows supervisors in call centers to join a call and
discreetly coaching an agent. It can also be used in boss/secretary arrangements
for a discreet call announce. The new feature is called "Whisper Announcement"
or "Discreet Coaching".
165.2 Realization
The Whisper Announcement feature is to be an expanded version of Silent
Monitoring. Silent Monitoring feature allows a supervisor to monitor agent calls
which are currently in progress. The supervisor microphone is switched off when
Silent Monitoring feature is in use; agents and callers don’t hear the supervisor.
In case of Whisper Announcement activation, the supervisor will be heard by the
agent and will be able to discreetly make an announcement for the agent. The
agent partner will not hear supervisor's actions. He will hear only the agent. 

To fulfill the new requirements, the existing Silent Monitoring implementation is
enhanced to switch on the supervisor microphone in order to be heard only by the
agent. 
Whisper Announecement is a monitoring feature.
165.3.1 ACD WHISPER ANNOUNCEMENT Feature

Activation
The ACD Whisper Announcement feature can be activated from any properly
classmarked supervisor set from the initial dial state only (see Section 165.4,
“Administration” for AMO commands).
The ACD Whisper Announcement feature can be activated by pressing a feature

key or by dialing a feature access code (see Section 165.4, “Administration” for
AMO commands). If a feature key is used, then CP will receive
DB_CP_E_SC_WHISPER_ANN_KEY event. If a feature access code was
dialed, then digit analysis shall return DB_KZP_WHISPER_ANN.
The supervisor's class of service is checked to determine if the ACD Whisper

Announcement feature can be activated from this line.
A31003-H3170-S103-6-7620, 02/2019
Whisper Annoucement
User Interface
If not authorized, negative acknowledgement tone is connected and a NOT

AUTHORIZED display is provided.
If authorized to activate ACD Whisper Announcement, a system flag is checked

to determine whether the target party is to be specified by extension number or
by agent logon id (see Section 165.4, “Administration” for AMO commands).
The appropriate display (ENTER LOGON ID or ENTER STATION NO.) will be

provided along with Recall dial tone.
If the addressing is to be done by extension number, the directory number of the

target party is collected and digit analysis is called to verify that a valid extension
number has been dialed. A valid extension number is indicated by the return
'DB_KZP_TLN'. The loden of the target party is retrieved.
If the addressing is by agent logon-id, then the logon-id digits are collected. After
the agent's logon-id number is collected, the loden of the device using that logon-
id is determined.
A check is made to determine if the target agent has the proper classmark to be
monitored. Otherwise negative acknowledgement tone is connected and a NOT
AUTHORIZED display is sent to the supervisor's set.
If the agent is properly classmarked, the 'ACD_MONITOR_ACT' attribute is set

on in the dev_attribute field and the loden of the monitoring party is stored in the
'MONITOR_LODEN' field of the DYNAMIC_DEVICE table of the target party.
DB_GEN_ATTR_WHISANN_ACTIVE attribute is set on in the monitor CPB.
The loden of the target party is stored in the 'MONITORED_LODEN' field of the
CP_DYNAMIC_DEVICE table of the monitoring party.
The call status of the target party is now evaluated to determine whether a
monitor call can be immediately established.
If the current call status of the target party does not permit a monitor call to be
immediately established, the monitoring device enters into a special call state -
'MONITORING_PTY_WAIT', DB_CP_CDSA640 (or DB_CP_CLS640 if anate).
If the current call status of the target party allows the monitor call to be established
(call is a 'MONITORABLE CALL'), a monitoring conference call is established
between the monitoring party, the target party, and the non target party.
A 'MONITORABLE CALL' is defined as follows:
1. The call is in a stable two party talk call condition. This precludes all non talk
conditions such as ringing, ringback, dialing, etc. This also precludes all
multiparty call conditions such as consultation and all forms of conferencing.
2. The attendant is not a member of the two party call.
3. The call is not any type of DATA call.
4. The DB_GEN_ATTR_GEST_ZUST attribute is set in the

GENERAL_ATTRIBUTES field of the CPB.
A31003-H3170-S103-6-7620, 02/2019
Whisper Annoucement
User Interface
5. The parties in the call must be in one of the call processing call states as
indicated in the following table.
DEVICE MONITORABLE STATE TARGET STATE NON TARGET

TYPE WHILE STATE WHILE
MONITORED MONITORED
(WHISPERED) (WHISPERED)
ANATE DB_CP_CLS500DB_CP_ DB_CP_CLS541D DB_CP_CLS542D
CLS520 B_CP_CLS543 B_CP_CLS544
DIGITE / DB_CP_CDSA500T DB_CP_CDSA541 DB_CP_CDSA542
Phan / KS / T T
SEKR
Funct device DB_CP_CSF500 Not Allowed DB_CP_CSF542
ANALOG DB_CP_CTS500 Not Allowed DB_CP_CTS542_
trunks NM
CORNET DB_CP_CNW500 Not Allowed DB_CP_CNW542_
NM
The monitoring party is responsible for allocating the needed resources

(conference cells, common cpb, and all paths) to establish the monitor
conference call. When all of the resources have been allocated, the monitoring
party sends a 'MONITOR_BEG' event to the target party.
When the target party receives the 'MONITOR_BEG' event, the target party
sends a 'PARTN_MON_BEG' event to the non-targeted member in the call.
The processing to set up the whisper monitor call is essentially similar as that for
establishing a silent monitor call using an override conference call with three
parties: monitoring party, target and non target. No override tone is connected to
the conference cell.
Feature activation:
1. The monitoring party's speech connection is a full path connection to the
monitoring conference. The monitoring party enters a 'MONITOR TALK'
DB_CP_CDSA540T (or DB_CP_CLS540 if anate) call state.
2. The target speech connection is a full patch connection to the monitoring

conference. The target enters a 'MONITORED PARTY TALK' call state.
3. The non target’s speech connection is a half path connection (LISTEN ONLY)
to its partner (target). Non target enters a 'NON MONITORED TALK' call
state.
165.3.2 Breakdown of Whisper monitor Connection -

Monitoring Party
The system ignores certain actions initiated by the monitoring party, i.e., digit
events.
A31003-H3170-S103-6-7620, 02/2019
Whisper Annoucement
User Interface
The system responds by displaying the NOT POSSIBLE message for five
seconds when the monitoring party presses a key which signals a flash (either the
FLASH_KEY or a feature key that produces the same result) in an attempt to
activate a feature. The call state remains intact.
An 'ON HOOK' by the MONITORING PARTY when in the 'MONITORING_TALK'

call state causes an immediate breakdown of the whisper monitor connection and
deactivation of the Whisper Announcement feature. The target and its partner are
returned to the call states that existed prior to the whisper monitor connection.
The MONITORING PARTY is not able to receive incoming calls or to answer any
call. The MONITORING PARTY is not in an "IDLE" call state.
165.3.3 Breakdown of Whisper Monitor Connection -

Monitored Party / Non-Monitored Party
Any action initiated by or event received by the MONITORED PARTY or NON
MONITORED PARTY results in the immediate dismantling of the monitor call
connection. The MONITORING PARTY enters into the ’MONITOR PARTY WAIT’
state. The MONITORED PARTY and NON MONITORED PARTY returns to the
call state that existed prior to entering the monitor call state before the action or
event is processed.
165.3.4 Breakdown of Whisper monitor Connection -

Monitor Party Wait State
The system shall ignore certain actions initiated by the monitoring party (i.e., digit
events) when in the ’MONITOR PARTY WAIT’ state.
The system responds by displaying the NOT POSSIBLE message for five
seconds when the monitoring party presses a key which signals a flash (either the
FLASH_KEY or a feature key that produces the same result) in an attempt to
activate a feature when in the 'MONITOR PARTY WAIT' state. The call state
remains intact.
An 'ON HOOK' by the MONITORING PARTY when in 'MONITOR PARTY WAIT'

state results in the immediate deactivation of the whisper monitor feature.
A31003-H3170-S103-6-7620, 02/2019
Whisper Annoucement
Administration
165.3.5 Reestablishing the Whisper Monitor

Connection.
Whenever the MONITORED PARTY enters into a MONITORABLE call
connection, it sends a 'MONITOR_RESUME' event to the MONITORING PARTY.
This event causes the MONITORING PARTY to reestablish the whisper monitor
connection.
165.3.6 Whisper Announcement Feature and Whisper

Monitor Connections over a CC Soft Restart
The Whisper Monitor Connection shall not be saved over a CC soft restart. The
Whisper Announcement feature shall not be saved over a CC soft restart.
165.4 Administration
Activate Whisper Announcement in the system
CHA-ZANDE:TYPE=ACD,WHISANN=YES;
Configure digit analysis results

This allows Whisper Announcement to be activated using a speed dial code.
ADD-WABE:CD=xxx,DAR=WHISANN;
CD --> Number used to activate the feature on the supervisor telephone

DAR=WHISANN --> Whisper Announcement
Only extensions with the corresponding authorization can be used for monitoring
purposes.
Authorize the supervisor to monitor and whisper agent calls.

Call monitoring must be activated individually for each agent.
CHA-SDAT:STNO=AgentNr,TYPE=ATTRIBUT,AATTR=CBSTMON;
STNO --> Number of member for which monitoring is authorized

AATTR=CBSTMON --> Configures an attribute: The agent's calls may be monitored
Authorize the supervisor for monitoring

Monitoring authorization must be defined individually for each supervisor.
CHA-SDAT:STNO=SupervisorNr,TYPE=ATTRIBUT,AATTR=CASTMON;
STNO --> Supervisor member number

AATTR=CASTMON --> The station is authorized to monitor agent calls
A31003-H3170-S103-6-7620, 02/2019
Whisper Annoucement
Restrictions
Define a Whisper Announcement key for the supervisor station.

CHA-TAPRO: STNO=SupervisorNr, KYxy=WHISANN;
Define whether the agent's ID or number must be entered in order to

activate monitoring.
CHA-ACDSD: TYPE=SYS, AGTTARGT=EXT and ID
AGTTARGT=EXT --> to monitor agent calls, the EXTENSION is entered

AGTTARGT=ID --> to monitor agent calls, the AGENT ID is entered
Monitor a call
1. Do one of the following actions on a telephone authorized for monitoring:
a) Ppress the Whisper Announcement key

or
b) Enter the code for Whisper Announcement.
2. Enter the processor number of the agent whose calls you wish to monitor:
a) If AMO ACDSD, TYPE=SYS, AGTTARGT=ID was used to define that the

agent ID is to be used:
ENTER LOGON ID
b) If AMO ACDSD, TYPE=SYS, AGTTARGT=EXT was used to define that

the agent number is to be used:
ENTER STATION NO.
3. When a correct processor number is entered but
a) monitoring is not authorized for this agent, the function is aborted and the
message NOT AUTHORIZED is output.
a) this agent is already being monitored by another supervisor, the function

is also aborted and the message ‘NOT POSSIBLE’ is output.
165.5 Restrictions
The feature can be used in boss/secretary arrangements for a discreet call
announce. In this case the feature must be activated by entering extension of
target, therefore ACTTARGET=EXT must be set in AMO ACDSD, TYPE=SYS.
It is recommended that the target shouldn’t be an ANATE, because in this case

there is a noticeable hardware echo which allows the partner to softly hear the
supervisor whispering.
A31003-H3170-S103-6-7620, 02/2019
annuni_en.fm
Announcement Unit
Applications
Applications
166 Announcement Unit

The announcement unit is assigned on the TMOM module. Any number of lines
circuits may be configured for one device, which are combined on the
announcement unit.
166.1 Assignment of Announcement Unit for General Text (internal)

• Assign code for announcement unit (internal)
AD-WABE:CD=key-num,DAR=ANSINT;
AD-COT:PAR=NTON;
• Add trunk group
AD-BUEND:NO=number;
AD-TSCSU:COTNO=number,TGRP=number,DEV=RA,COPNO=number,
SUPV=SUPV2,ACKT=SZACK2;
• Assign a route to the announcement unit
• Set timers (seconds)
CHA-DTIM1:TYPEDH=TCOM,RATX= *.;
*) The time must be set so that it is twice as long as the announcement text.
If several announcement units are used, the longest text must be used as a
reference.
A31003-H3170-S103-6-7620, 02/2019
annuni_en.fm
Announcement Unit
Announcement Unit for Greeting Text and General Text
166.2 Announcement Unit for Greeting Text and General Text

If announcements are required for incoming CO trunk calls as well, 2
announcement units must be connected: one unit for the company greeting, and
the second one for the announcement. 
To make sure that a line to the unit with the announcement text is free after the
greeting, 2 trunk groups are assigned for the announcement unit: one group
which is seized only internally and one group which is seized externally after the
greeting text. 
The code for external and internal seizure is the same, but it leads to different digit
analysis results in the dial plan for different CPSs.
Assign an announcement unit for greeting text

• Assign a TMOM module
• Assign identical code for greeting and announcement text
AD-WABE:CD=key-num,DAR=ANSCO; 
AD-WABE:CD=key-num,DAR=ANSINT;
AD-COT:PAR=NTON;
• Add trunk group
AD-BUEND:NO=number;
AD-TSCSU:COTNO=number,DEV=ANS,COPNO=number; 
EINR-TSCSU:COTNR=number,BUNR=number,GER=ANSEA,COPNR=number,
• Assign a route for the greeting text unit. The CPSs must be specified, since
the code leads to different digit analysis results in the DPLN.
AD-RICHT:TYPE=CD,CD=key-
num,CPS=6,SVC=VCE,TGRP1=number,CPAR=ANN;
CHA-DTIM1:TYPEDH=TCOM,RASTA= *1),RECAMDLY= *2.;
*1. Set time for text length in seconds (must be longer than the greeting text).
*2. Time for waiting for start of greeting text in seconds (must be
approximately as long as the greeting text). 
A ringing tone is sent until the text begins. If the timer expires before zero
passage, i.e. the set time is too short, the connection is released.
A31003-H3170-S103-6-7620, 02/2019
annuni_en.fm
Announcement Unit
Assign an announcement unit for announcement text (after greeting text)

• The configuration data, class of trunk and class of line parameters are
assigned as for the greeting text unit.
• Assign two trunk groups

AD-BUEND:TGRP=zz,NO=number; 
AD-BUEND:TGRP=yy,NO=number;
• Assign the trunk circuits (as many as required)
AD-
TSCSU:NO=number,COTNO=number,TGRP=number,DEV=RA,COPNO=number,
• Assign a route to the announcement unit
The trunks are assigned to the two trunk groups. 
The CPS values must be specified as follows.
AD-RICHT:TYPE=CD,CD=key-num,CPS=5&8&9,SVC=VCE,
TGRP1=zz,CPAR=RATGRP,TGRP2=yy ,CPAR=NONE; 
(CPS 10&11&12 are only for tie-traffic.)
CHA-DTIM1:TYPEDH=TCOM,RATX= *.;
*) The time must be set so that it is twice as long as the announcement text.
If several announcement units are used, the longest text must be used as a
reference.
A31003-H3170-S103-6-7620, 02/2019
annuni_en.fm
Announcement Unit
A31003-H3170-S103-6-7620, 02/2019
musicex_en.fm
Feature Description
167 Music Source External

This feature is used to replace standard announcements or SIU signaling tones
injected for stations on hold by individual announcement injections from external
announcement devices. Configure one announcement device on a SLMA/
SLMA1 board per LTG. You can assign between one and sixteen CP tones to this
device.
The connection is configured using AMO SSC, TYPE=EXTANN. You must

specify a PEN both when assigning the CP tones and per line. You can also
assign further CP tones (max. 16)

Configure connections for local announcement and attendant intercept:
ADD-SSC:TYPE=EXTANN,CPCALL=LOCANN&ANNICPT;
Expand the CP tone assignment (per LTG) by the internal dialing tone:
ADD-SSC:TYPE=EXTANN,CPCALL=INTDTN;
Delete the CP tone assignment (e.g. internal dialing tone):
DEL-SSC:TYPE=EXTANN,CPCALL=INTDTN;

• Deletion is performed automatically in every LTG. Deleting the last tone
assigned also deletes the configured connection.
• If a tone assignment (CPCALL in the TONTBL) is activated in the AMO ZAND

- after a EXTANN has already been assigned via AMO SCC, a soft restart is
required in the BP to reactivate the SSC configuration.
167.4 Relevant AMOs

Language
SSC TYP d Typ der Ausgabe
(EXTANS für externes Ansagegerät)
A31003-H3170-S103-6-7620, 02/2019
musicex_en.fm
Relevant AMOs

Language
TYPE e Special Station Type
(EXTANN for external announcement)
CPTON d Anlagenton
(z.B: interner Wählton: WTONINT)
CPCALL e Signal
(e.g. internal dial tone: INTDTN)
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
General
168 Synchronized Announcements
168.1 General
Synchronized announcements are used for providing callers with a specific
sequence of information prompts in order to achieve specific reactions. This is
dependent on the call progress/traffic situation of the incoming call.
The prompts/announcements are achieved by connecting external

announcement units to TMOM2 boards. Each prompt or announcement is heard
from the beginning. Up to 50 callers can listen to an announcement at any one
time. If more than 50 callers are to be able to listen to the same announcement
or, if the time callers spend waiting for an announcement to begin is to be
minimized, then the appropriate number of additional announcement units of the
required announcement type must be configured.
The attributes of an announcement are defined in a specific announcement type

(= announcement name). Between 1 and 64 announcement units or tone sources
can be combined to form a single announcement type. This is done by configuring
the TMOM2 Q2214-X boards for synchronized announcement units (RAS), and
assigning them to the same announcement type. Up to 64 announcement types
can be configured, provided each announcement type is only assigned 1
announcement unit or tone source.
Synchronized announcements can only be connected in certain call processing

situations. The situations are defined by the reasons for the announcements.
Presently, the following announcements are configured:
• hold-the-line announcement for call to an AC:
• announcement for calls to multiple paging equipment:
• announcement for calls to a hunting group call queue:
• announcement for calls to busy station for suffix dialing:
• announcement for calls to busy station with attendant intercept:
• announcement for calls to free station for suffix dialing:
• announcement for calls to free station with or without attendant intercept:
• announcement for calls to busy station with automatic camp on:
• announcement for DDI with incoming call from analog CO:
Synchronized announcements are cross-LTG.
The attributes of an announcement type consist of:
• Name:
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
General
– can be freely assigned
– up to 20 characters
• Status:
– on or off.
• Repeats:
– number of times the announcement cycle is to be repeated.
• Linked announcements:
– announcement type to continue after completion of current

announcement cycle.
• Operating mode:
– Continuous or Start/Stop
• Announcement delay timer:
– only applies if operating mode is Start/Stop. This value defines the delay
time before the announcement is started, following seizure by the first
caller.
• Idle release limit:
– only applies if operating mode is Continuous. This value defines the

number of times an announcement cycle is to be repeated under no-load
conditions before the announcement unit is switched off.
• Type of first internal tone:
– This tone type defines the tone which is to be applied at the end of the
announcement text.
• Duration of first internal tone:
– can be set as required
• Status of first internal tone:
– on or off.
• Type of second internal tone:
– This tone type defines the tone which is to be applied after the first internal
tone, or, if no first internal tone is applied, at the end of the announcement
text.
• Duration of second internal tone:
• Status of second internal tone:
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
General
– on or off.
• Type of third internal tone:
– This tone type defines the tone which is to be applied after the first or
second internal tone. If a first or second internal tone is not applied, it
defines the tone to be applied at the end of the announcement text.
• Duration of third internal tone:
• Status of third internal tone:
– on or off.
A synchronized announcement will run until interrupted by an external action (call

release or answer etc.), or until it terminates itself, depending on the
announcement type attributes defined. In the latter case, a return tone (exit tone)
is applied. This tone must be defined for each announcement reason.
The selection of a particular announcement type depending on the call progress

situation/internal traffic restriction matrix is configured via AMO SYNCA, by
means of an Announcement Reason / Announcement Type table.
Short announcements can be run in CONTINUOUS operating mode (i.e. looped).

The waiting time for callers before the start of an announcement text can be
bridged with the entry tone, which must be defined for each announcement type.
Longer announcements (from approx. 10 seconds onward) should be run in

START/STOP mode, since callers would otherwise have to wait too long before
hearing the start of an announcement text. However, this can only be done if the
announcement unit has a start/stop input. In this mode, the system searches for
an idle announcement unit assigned to the announcement type and starts
playback.
Wait times may differ from case to case in the CONTINUOUS operating mode,
and may even be as long as the announcement. However, you can minimize wait
times in the START/STOP operating mode by connecting several announcement
units and by selecting the correct announcement delay time in relation to the text
length.
Use the following example to calculate the optimum size of the synchronized
announcement with regard for the shortest wait time for text start by optimizing
the announcement length.
The text length of the first active announcement unit must be covered by the
result of the start delay time and the number of additional announcement units.
Ergo: Text length = start delay time multiplied by the number of announcement
units.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
General
Example:
Text length :: 40 sec

Start delay time :: 5 sec/10 sec/20 sec
Number of announcement units :: 8/4/2
In figures:
40 sec = 5 sec multiplied by 8 or

10 sec multiplied by 4 or
20 sec multiplied by 2 or ...
The number of necessary announcement units in relation to the set delay time
results from the following formula:
number of announcement units = text length / start delay time + 1
In figures:
Number of announcement units = 40 sec /5 sec + 1 = 8 + 1 = 9 or

= 40 sec / 10 sec + 1 = 4 + 1 = 5 or
= 40 sec / 20 sec + 1 = 2 + 1 = 3 or ...
If this procedure is used
• the maximum possible wait time for text start is always equal to the set start
delay time.
• the average wait time for text start is equal to half the maximum possible wait
time.
The value combination you use depends on the number of announcement units
you require (matter of costs) to reduce the wait times for text start to a justifiable
value.
The delay timer is necessary in order to avoid having to start a separate

announcement unit for each caller. This allows up to 50 callers to be connected
to the same announcement unit, provided they all call within the start delay time.
In this operating mode, if an idle announcement unit cannot be found for an
announcement type, the system switches to CONTINUOUS mode until an
announcement unit becomes idle again. This means that any caller(s) will have
to wait for the beginning of the announcement text, i.e. despite START/STOP
operation the wait times are irregular in length.
In this case, the system can output diagnosis advisory messages, in order to
allow system owners to react to the problem by expanding the system if
necessary. For this, bit 11 of the diagnosis bit string must be set with the aid of
the DIAGS AMO. This information will enable you to reconfigure your system and
to avoid the bottle neck.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
General
If you wish to operate an announcement unit in asynchronous mode, you must

set the new parameter ANOD in the COT of the TMOM board to which the
announcement unit is connected. In this case, callers will be switched to an
announcement unit without delay. This is useful if the announcement to be
switched is a looped announcement, e.g. please hold the line with background
music, where a start of text signal is not required.
For this type of operation (without start-of-text recognition), announcement units

can also be connected to TMOM via the a/b wires only. The c- and d-wires must
be bridged in order to avoid a line alarm. In addition, the new parameter AANT
must be set in the COP of the TMOM lines.
• COT parameter value = ANOD (asynchronous operation)
• COP parameter value = AANT (connection via a/b wires only)
You must set the operating mode to START/STOP for this type of connection,
since the TMOM circuit will otherwise not be released when required. (If you set
the operating mode to CONTINUOUS, the TMOM circuit would normally be
released when the release limit is reached. However, since no text repetitions can
be defined, this is not possible).
For start and stop control via the TMOM board, the p-wire and j-wire can be
additionally connected.
You can also install and operate the synchronized announcement for the
application "wait announcement on the AC" in the CAC node. Installation in all
originating nodes is therefore no longer necessary. Prerequisites are:
Set the COT parameters WAAN and ABPD for the tie line to the CAC node, even
if the calling party in the originating switch is an analog trunk. The digit in last
position in the CAC’s attendant code (satellite PBX: AMO-NAVAR, last digit CD-
CASEXT) is entered in the branch ANNMCI in the AMO-SYNCA. In addition, you
must set the COT parameter ABNA, if the synchronized announcement in the
CAC node is only to be started, when the attendant console is in night service.
You can operate a new announcement, if a digital trunk with external traffic
performs automatic camp-on on a Digite, Anate or functional station. For this,
configure and assign an announcement type for the new announcement reason
"Announcement with automatic camp on".
You can operate a synchronized announcement for analog trunks with automatic
camp-on on a Digite or Anate. The announcement is also activated for a transfer
during camp on.
You can have different wait announcements at the AC for day and night operation.
For this purpose, the additional announcement reason "Wait announcement on
AC no answer with night service" (WANNDNS) was implemented for both local
ACs and the CAC. With a CAC the TMOM connection and the CAC can be
located in different nodes.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
General
If no special administrative settings are made for night service, the day service
settings also apply for night service.
You can also use the ITR of the night station to determine the announcement type
for wait announcements at the AC during night operation if these were configured
in the same node as the announcement unit.
Synchronized announcement can also be used for three applications, provided

the calling device has the COS for synchronized announcement (COS=ANSYN)
and is not an AC. Each of these three application cases must be released using
AMO ZAND. If you want third-party systems to hear the synchronized
announcement, set the COT parameter SANH in the incoming tie lie. The three
possible application cases are:
• no answer on AC (day and night service)

CHA-ZAND:TYPE=ATND,ISYNCAC=YES;
• call to CSM (CSM with MEETME)
CHA-ZAND:TYPE=CCM,ISYNCCCM=YES;
• call to a hunting group call queue.
CHA-ZAND:TYPE=ALLDATA2,ISYNCHG=YES;
Synchronized announcement can be remotely operated for
• call to CSM (CSM with MEETME) and
• call to a hunting group call queue
The announcement need therefore not be configured in the same node as the
hunting group or the CSM. Instead, the announcement can be configured in the
originating node for these application cases.
Any discrepancies within the network when setting the remote operation of the
synchronized announcement can be avoided by setting the COT parameter
TNDV (tone is injected from the station) for the outgoing digital tie trunk.
Remote operation of the synchronized announcement are generally prohibited for

other applications (Announcement with station no answer), if this COT parameter
is not set.
It is also possible to administrate up to 999 different station numbers between 1

and 6 digits as an alternative to the administration of the company index. Use the
corresponding switch setting in AMO ZAND to select one of the two variants.
AMO ZAND: TYPE = ATND, COMP1000 = YES
IMPORTANT: When you switch to 1000 company announcements for the first
time, you must regenerate the existing data for the AC DAR.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
Connecting Announcement Units
You can also use the announcement for transfer purposes for the applications
"Announcement with PSM" and "Announcement with camp-on". This option is
also available for the application "Announcements for Hunting Group Call
Queue". The position of the hunt group, the announcement unit or the transferring
party in the network is not important.
You can also use the synchronized announcement for the individual night service
(AMO ZAND: TYPE = ATND, INIGHT = YES) if you set a subscriber call number
for the trunk as an individual night station (AMO TDCSU: INIGHT = nnnnn).
The announcement type determined in the originating node can be transported

via the CAC traffic to the CAC node and used there for connection. Up until now,
if the announcement unit was configured in the CAC node, the announcement
type was also determined in this node. In certain applications, the relevant
information was not available to determine the correct announcement type.
You cannot set a different entry tone or exit tone, however, with this procedure.
The tone settings made in the CAC node for the announcement reason
WANNAOHK or WANNDNS apply here.
If you want to use this procedure, follow the rules listed here:
• Ensure that the announcement type information unit is consistent

throughout the entire OpenScape4000/HiPath 4000 network.
• Configure the synchronous announcement in all OpenScape 4000 nodes

as if you wanted to operate the announcement locally. However, you only
have to configure the TMOM2 board in the CAC node and assign the
announcement type to the board (AMO TSCSU).
• Set the COT parameter SATR for all trunks used to reach the CAC node
from the originating node.
168.2 Connecting Announcement Units

Possible announcement units are the Musifone multimax from Bayer and the
Genius ST from Speech Design. All these devices can be run in CONTINUOUS
or START/STOP mode. The predecessor of Musiphone multimax was Musiphone
5000 S. The following section describes how to connect these devices to the
TMOM2 board.
• Musifone 5000 S:
This device has a text memory for announcements between 32 and 320 secs.
If you are using the Bayer Musifone 5000 S, you should use the following
settings:
- CONTINUOUS operating mode: Functional setting = 4, Operating mode
setting = 8.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
- START/STOP operating mode: Functional setting = 4, Operating mode

setting = 9.
The following diagram shows the announcement unit connected to circuit 0 of the
TMOM board in START/STOP mode.
a/b JP CD
1 2 3 4 5 6 7 8
TMOM
1
2
3 Announcement
unit
4 connection
5
43 OHM
6
Figure 130 TMOM Connection Musiphone 5000 S
If the announcement unit is to be run in CONTINUOUS mode, the TMOM input

JP does not need to be wired (bold lines). In order for the announcement unit to
repeat automatically, pins 4 and 5 of the announcement unit interface must be
bridged.
• Musiphone multimax
This device is a further development of the Musifone 5000 S. It has 8
independent text memories.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
a/b JP CD
1 2 3 4 5 6 7 8 TMOM
1
O Announcement
2 unit
O
connection
3
O
4
O
5
O
6
O
TMOM connection to Musiphone multimax
• Genius ST:
This device has 2-4 independent text memories. Text 1 can be up to 3 minutes
in length; all other texts can be max. 32 seconds long.
No changes to the DIP switch settings are necessary.
- CONTINUOUS operating mode:
Activate the used text memories manually with the appropriate buttons.
The announcements are then played back continuously in looped mode.
- START/STOP operating mode:
Do not activate the text memories manually.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
a/b JP CD
1 2 3 4 5 6 7 8
TMOM
1
2
3 Announcement
unit
4 connection
5
6
7
8
Figure 131 TMOM Connection Genius ST
If the announcement unit is to be run in CONTINUOUS mode, the TMOM input

JP does not need to be wired (bold lines).
168.2.1 Prerequisites, Interrelationships
AMO - ZAND Required for enabling the synchronized announcements feature; also
for enabling the feature synchronized announcements for CCM calls.
Also required for enabling the synchronized announcements feature
for "No answer on AC", for "Call to CSM" and for "Call to hunting
group".
AMO - VFGR Required for marking all ATND groups with a synchronized
announcement service for callers.
AMO - SA Required for marking all hunt groups with a synchronized
announcement service for callers waiting in the call queue.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
AMO - DIMSU Required for defining the number of available announcement buffers.
This value also defines the total number of lines in a particular node
which can be switched to an announcement unit at the same time.
AMO - CTIME Required for defining the start time of an announcement if calls rung at
the attendant console are not answered.
Required for defining the timeout after seizure of a station to either
start the announcement for suffix dialing or "Station no answer".
AMO - DTIM1 Required for defining the maximum delay time before the beginning of
the announcement is heard after the announcement unit is activated,
and for defining the maximum delay time before the beginning of the
next announcement in the chain is heard.
Attention: With Genius ST in the text memory from 1 to 3 minutes!
AMO - COT Required for defining the additional COT parameters necessary for
allowing callers to be switched to synchronized announcements.
for asynchronous operation: ANOD (for TMOM circuit)
for announcements at the WAAN (for calling circuit)
attendant console:
for announcements at an SA ANHT&BSHT (for calling circuit)
AO
for announcements with busy ABNA&IBSY (for calling circuit)
station:
for announcements for camp on ABNA&KNDI (for calling circuit)
for announcements for station ABNA &(IFR) (for calling circuit)
no answer:
for announcements suffix PDOB (for calling circuit)
dialing station busy:
for announcements suffix PDOT (for calling circuit)
dialing station no answer:
for announcements for DDI: RDDI (for calling circuit)
for announcements for third- SANH (for calling circuit)
party systems:
for announcements with PSM: APSM (for calling circuit)
for answering before suffix- ABPD (for calling circuit)
dialing or announcement:
for transporting the SATR (for calling circuit)
announcement type to the CAC
node
AMO - COP The COP parameter set in TSCSU for the TMOM board must contain
the parameters SACK and LSUP.
If an announcement is operated in asynchronized mode (with a/b wires
only) the COP parameter AANT must be set.
AMO-COSSU Set the COS ANSYN for the terminal which is to hear the synchronized
announcement.
AMO - TSCSU Once the announcement types have been defined, the TSCSU AMO
must be used to configure the TMOM board as a RAS and assign the
appropriate announcement type.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
AMO - SYNCA Configure the announcement type. Assign an entry tone and exit tone
to an announcement reason. Define, whether you reach the
announcement either by ITR or the last dialed number (for hold-the-
line announcement at AC).
Example 1: Hold-the-line Announcement at the AC

The Meier company can be reached via ATND group 2. If calls are not answered
within a defined time, callers are to hear the first in a series of announcements.
This announcement is to be repeated once. If the call has still not been answered
at the end of the second repeat, the caller is to be switched to a further
announcement, which will then be continuously repeated (looped), until the call is
finally answered (or the caller hangs up). The text announcements should be
interrupted by 10 seconds of music and 20 seconds of
PLEASE_HOLD_THE_LINE. The first announcement is to be configured in
START/STOP mode, with a start delay time of 3 seconds. The second
announcement is to be set up in CONTINUOUS mode, with a no-load release
value of 5 repeats.
ATNDGR 2 is marked as ’with synchronized announcements’. (VFGR AMO).
The last announcement type in a chain of linked announcements must always be

defined first
Assign announcement type 2:

AD-SYNCA:
ANTT,2,Meier_Inc,ON,255,,MUSIC,10,ON,HOLDLINE,20,ON,,,, CONT,5;
AD-SYNCA: ANTT,1,Meier_Inc,ON,1,2,MUSIC,10,ON,HOLDLINE,20,ON,,,,
STA_STO,3;
Assign entry tone/exit tone for WANNAOHK announcement reason
AD-SYNCA: ANNTONE,WANNAOHK,CAMP,RNGBK;
Create the Announcement Reason/Announcement Type table entries:
You must assign the announcement type 1 to the announcement reason

WANNAOHK, depending on the ITR number or last dialed digit with which the
ATND group is reached.
If an ATNDGR is reached by direct dialing, the last dialed digit (e.g. 2) is relevant.
The last digit in the attendant code is relevant for CAC (satellite PBX AMO-
NAVAR,CD-CASEXT)
AD-SYNCA: ANNMCI,WANNOHK, <ldigit-stno-atnd-cd>, 1;
AD-SYNCA: ANNMCI,WANNAOHK, <ldigit-stno-casext>,1;
Up to EV2.0 it was only possible to assign an announcement type to the last
dialed digit (company index). From HV 3.0 you can assign 999 different digit
sequences with up to 6 digits to one announcement type. These digits are the last
dialed digits. The switch in AMO ZAND must be set to this alternative.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
CHA-ZAND: RESERVE,102, YES;

Then enter the digit sequence (e.g. 471199).
AD-SYNCA: ANNMCI,WANNOHK, 471199, 1;
If the attendant group is reached via an internal FWD, FWDBSY or FNANS, the
ITR number of the forwarding station is used (ITR=4). If the group is reached via
an external FWD, FWDBSY or FNANS, the ITR number of the caller is used
(ITR=0), since the ITR groups are not unambiguous throughout a network.
If the attendant group is reached via “attendant intercept”, the ITR number is
relevant. If no destination number can be determined, e.g. in the case of
attendant intercept due to misdialing or because the station is not authorized for
direct inward dialing, the ITR number of the caller is used (ITR-A-STN).
AD-SYNCA: ANNMITR,WANNAOHK, <ITR_A_STN>, 1;
and
AD-SYNCA: ANNMITR,WANNAOHK, <ITR-FWD-STN>, 1;
If an internal destination (internal user or internal hunting group) can be
determined, the ITR number of the internal user or hunting group master is used
(ITR = 3). If the destination number is an external number, the ITR number of the
caller is used.
AD-SYNCA: ANNMITR,WANNAOHK,<ITR-DEST>, 1;
If you want to activate a synchronized announcement for terminals you must
enable the internal application using AMO ZAND
CHA-ZAND: TYPE = ATND,ISYNCAC=YES;
When you assign a COS, you select the user who should hear the synchronous
announcement.
CHA-COSSU: TYPE = COS, COS = <ITR-A-STN>, AVCE = ANSYN;
Example 2: Announcement with PSM

Callers to the multiple code-calling system CCM are to hear an announcement.
The announcement is not to be repeated. After the announcement, the CCM hold
tone is to be fed in for as long as possible. The call waiting tone (knocking/camp-
on tone) is to be defined as the entry tone, and the ringback tone is to be defined
as the exit tone. The required operating mode is START/STOP, and an
announcement start delay timer of 2 seconds is to be set.
Synchronized announcements for CCM callers are currently only possible if the
announcement unit and the CCM are in the same node. Remote applications are
also supported in EV 3.0 and higher.
Use the ZAND AMO to enable synchronized announcements for CCM callers.
Parallel ringing and synchronous announcement are possible at the same time.
You must disable parallel ringing before you can activate the synchronous
announcement for call forwarding on no reply or call forwarding.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
CHA-ZAND: TYPE = CCM, SYNCACCM = YES, STNRNG = NO;

Set the APSM parameter in the calling circuit’s COT.
CHA-COT: COTNO = <number>, COTTYPE = COTADD, PAR = APSM
AD-SYNCA: ANTT,2,Meier_Inc,ON,,,HOLDCCS,255,ON,,,,,,,STA_STO,2;
Assign entry tone/exit tone for ANNCCM announcement reason
AD-SYNCA: ANNTONE,ANCCM,CAMP,RNGBK;
Assign announcement reason/announcement type table:
Depending on the ITR code number of the incoming call, the announcement type
4 must be assigned to the announcement reason ANNCCM 4. The ITR numbers
used depend on the types of call situation for which the announcement is
required.
If the CCM is reached by direct dialing, and the code-calling number dialed
belongs to an internal user, the called user’s ITR (5) is used.
AD-SYNCA: ANNMITR,ANCCM, <ITR-SEARCHNO-STN>,4;
If the code-calling number dialed belongs to an external user, the calling user’s
ITR (7) is used.
AD-SYNCA: ANNMITR,ANCCM,7,4;
If the CCM is reached via call forwarding/forwarding on no answer after dialing an
internal user’s number, the ITR of the internal (forwarding) user (8) is used.
AD-SYNCA: ANNMITR,ANCCM,8,4;
If the CCM is reached via call forwarding/forwarding on no answer after dialing an
external user’s number, the caller’s ITR (7) is used.

enable the internal application using AMO ZAND.
CHA-ZAND: TYPE = CCM,ISYNCCCM=YES;
announcement.
CHA-COSSU: TYPE = COS, COS = <ITR-A-SEARCHER>, AVCE = ANSYN;
Example 3: Announcement with Hunting Group Call Queue

Callers to a certain hunt group are to hear a synchronized announcement, if put
on hold in the call queue. This announcement is to be repeated 3 times. A 15-
second hunting group wait tone is to be fed in between each repeat. The ringback
tone is to be used as the entry tone and exit tone. The announcement is to be
operated in START/STOP mode, with an announcement start delay of 3 seconds.
Use the SA AMO to mark the hunting group as ’with synchronized

announcements’ .
Set up announcement type 5:
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
AD-SYNCA: ANTT,5,Meier_Inc,,ON,3,,HOLDHT,15,ON,,,,,,,STA_STO,3;
Assign entry tone/exit tone for WANNHG announcement reason
AD-SYNCA: ANNTONE,WANNHG,RNGBK,RNGBK;
Assign announcement reason / announcement type table:
5 must be assigned to the announcement reason WANNHG. The ITR numbers
required.
If the hunting group is reached by direct dialing, the ITR number of the hunting
group master or the first hunting group member is used (ITR-HT-MASTER).
AD-SYNCA: ANNMITR,WANNHG,7,5;
If the hunting group is reached via call forwarding/forwarding on no answer after
dialing an internal user’s number, the ITR of the internal (forwarding) user (8) is
used.
AD-SYNCA: ANNMITR,WANNHG,8,5;
If the hunting group is reached via call forwarding/forwarding on no answer after
dialing an external user’s number, the ITR of the destination number is used (i.e.
of the hunting group).

CHA-ZAND: TYPE = ALLDATA2,ISYNCHG=YES;
announcement.
Example 4: General Announcement "Station busy"

Callers who reach busy internal stations are to hear a one-off announcement
(announcement type =3). The announcement can only be set up if COT
parameters with subsequent attendant intercept are set. If an announcement with
subsequent attendant intercept is used, and the call is not answered by the
attendant within a specific time limit, callers are to be switched to a second
announcement (announcement type =5). The delay time until the call is answered
by the attendant, or until the second announcement is started, is to be filled in with
music. The second announcement is to start after approx. 15 seconds. After the
second announcement, more music is to be fed in for another 30 seconds,
followed by 10 seconds of “please hold the line”. This cycle is to be repeated 3
times. Since the text of the first announcement is very short, the operating mode
is to be set to CONTINUOUS, with a no-load release limit of 5 repeats. The
operating mode of the second announcement is to be set to START/STOP, with
a start delay time of 3 seconds. The call waiting tone (camp-on) is to be used as
the entry tone, and the ringback tone as the exit tone
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
In this example, the second announcement (if call is not answered within a
specific time after attendant intercept) cannot be reached except through the first
announcement. The reason for this is that the announcements would otherwise
interrupt each other. This means that the wait time for the second announcement
can be influenced by the settings for the first announcement. For example, if the
first announcement has a length of 4 seconds, the subsequent music feed-in
must be set for 9 seconds. The actual start delay of the second announcement
thus lies between 13 seconds and 17 seconds. If precise delay times are
required, this can only be achieved by running the first announcement in START/
STOP mode as well.
Whereas the first announcement, with subsequent attendant intercept, will

always be played back in the specified situation, the second announcement will
only be played if the attendant intercept destination (ATND group) is marked as
“with synchronized announcements”.
The synchronous announcement must be configured in the node in which it is

required. For example, if an exchange call reaches an internal user via an S0/
S2 transit connection, and the call is to be cleared down back to the originating
node, the announcement will have to be configured in this node.
Assign announcement type 5 (second announcement):

AD-SYNCA:ANNTT,5,Meier_Inc,ON,3,,MUSIC,30,ON,HOLDLINE,10,ON,,,
STA_STO,3;
Assign announcement type 3 (first announcement):
AD-SYNCA: ANNTT,3,Müller_Inc,ON,,5,MUSIC,9,ON,,,,,,,CONT,5;
Assign entry tone/exit tone for ANNBUSY announcement reason
AD-SYNCA:ANNTONE,ANNBUSY,CAMP,RNGBK;
3 must be assigned to the announcement reason ANNBUSY. The ITR numbers
required.
If the busy station is reached by direct dialing the ITR of the called station (5) is
used.
AD-SYNCA: ANNMITR,ANNBUSY,5,3;
If the busy station is reached via call forwarding/forwarding on no answer after
dialing an internal user’s number, the ITR of the internal (forwarding) user (8) is
used.
AD-SYNCA: ANNMITR,ANNBUSY,8,3;
If the busy station is reached via call forwarding/forwarding on no answer after

dialing an external user’s number, the ITR of the destination number is used (i.e.
of the busy station).
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
If a call is switched to the attendant (attendant intercept) in the originating node

after dialing a network number in another node, the ITR of the destination station
number is also used (i.e. ATND).
This announcement cannot be used for a terminal.
Example 5: General Announcement "Station no Answer"

This is the same as example 4, except that the announcement reason is to be “no
answer” as opposed to “busy”. Substitute the announcement reason parameter
for this example ANNBUSY by ANNOHK. Other than with the "General
announcement "Station busy" this announcement is not combined with an
attendant intercept. You need not set the COT parameter IFR (Intercept when no
answer) in order to connect a synchronized announcement.
If the COT parameter IFR is set for the calling trunk, the announcement is
interrupted for the attendant intercept. To avoid this, the size of the intercept timer
must be in relation with the announcement length and to the configured value of
the announcement start timer (minimum value = 5).
Example 6: General Announcement with Automatic Camp on

Calls to a station in a two-party call are to hear a synchronized announcement
during automatic camp on. Set the COT parameter KNDI for automatic camp-on
on a busy station. The announcement is also activated during transfer.
Assign announcement type 7 as required, e.g.:

AD-SYNCA: Anntt,7,Camp,On,,5,Camp,10,On,,,,,,,Stasto,2;
Assign the entry/exit tone for the "Anknock" announcement reason :
AD-SYNCA:Anntone,Anncamp,Camp,Camp;
Set announcement type 7 for the ANKNOCK announcement reason, depending
on the ITR number of the camped-on party. For DDI to a busy station the ITR (ITR
=5) of the busy station is valid.
AD-SYNCA: Annmitr, Anncamp, 5, 7;
Example 7: Announcement "Station Busy with Suffix Dialing"

Callers via analog trunks who reach a busy user, but can re-route via DTMF
suffix-dialing, are to hear an appropriate announcement (announcement type 11).
In this case, the COT parameter IBSY must not be set. The announcement is not
to be repeated, and is to be followed by 10 seconds of music. The operating mode
is to be Start/Stop, with a start delay time of 3 seconds. The busy tone is to be
defined as the entry tone and exit tone.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
AD-SYNCA:,ANTT,11,Meier_Inc,ON,,,MUSIC,10,ON,,,,,,,STA_STO,3;
Assign entry tone/exit tone for SDBUSY announcement reason
AD-SYNCA:,ANNTONE,SDBUSY,BUSY,BUSY;
Assign announcement reason / announcement type table:
The same rules apply as for example 4, except that the announcement reason
ANNBUSY must be replaced with SDBUSY instead.
Example 8: Announcement "Station no Answer with Suffix Dialing"

Callers via analog trunks with DTMF suffix dialing, who reach a station user who
does not answer within a set time, are to hear an appropriate announcement. The
same rules apply as for example 5, except that the announcement reason
ANOHK must be replaced with SDOHK instead.
Example 9:
Calls via analog trunks without direct dialing authorization but with DDI
functionality are to receive an announcement immediately after incoming trunk
seizure (announcement type 12). This announcement is not to be repeated, and
no further internal tones are to follow. The ringback tone is to be defined as the
entry tone, and a special dialing tone as the exit tone. The operating mode is to
be Start/Stop, with a start delay time of 1 second.

AD-SYNCA:ANTT,12,Meier_Inc,ON,,,,,,,,,,,,STA_STO,1;
Assign entry tone/exit tone
AD-SYNCA:ANNTONE,RNGBK,SPEC;
Assign announcement reason/announcement type table:
For this announcement reason, there are no destination number ITRs to be used.
The announcement reason must therefore be entered as dependent on the ITR
number of the caller (ITR=2).
AD-SYNCA:ANNMITR,DIDSD,2,12;
Example 10: Wait announcement on AC with night service

The Meier company can be reached via ATND group 2. If the calls are not
answered within a configurable time and the AC is switched to night service, an
announcement of type 19 is to be injected. This announcement is to be repeated
once. The text announcements should be interrupted by 10 seconds of music and
20 seconds of PLEASE_HOLD_THE_LINE. The first announcement is to be
configured in START/STOP mode, with a start delay time of 3 seconds. For day
time operation the settings in example 1 apply.
ATNDGR 2 is marked as ’with synchronized announcements’. (VFGR AMO).
Set up announcement type 19:
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
AD-SYNCA:
ANNTT,19,Meier_Inc,ON,1,,,MUSIC,10,ON,HOLDLINE,20,ON,,,,
Stasto,3;
Assign entry tone/exit tone for WANNADNS announcement reason
AD-SYNCA: ANNTONE,WANNDNS,RNGBK,FRNGBK;
Create the Announcement Reason/Announcement Type table entries:
You must assign the announcement type 19 to the announcement reason

WANNDNS, depending on the ITR number or last dialed digit with which the
ATND group is reached.
If an ATNDGR is reached by direct dialing, the last dialed digit (e.g. 2) is relevant.
AD-SYNCA: ANNMCI,WANNDNS,2,19;
When night service is active at the night station, the night station’s ITR is relevant
(ITR_NIGHT) if the night station is in the same node as the announcement unit.
AD-SYNCA: ANNMITR, WANNDNS, <ITR-NIGHT>, 19
If the attendant group is reached via an internal FWD, FWDBSY or FNANS, the
ITR number of the forwarding station is used (ITR=4). If the group is reached via
an external FWD, FWDBSY or FNANS, the ITR number of the caller is used
(ITR=0), since the ITR groups are not unambiguous throughout a network.
If the attendant group is reached via “attendant intercept”, the ITR number is
relevant. If no destination number can be determined, e.g. in the case of
attendant intercept due to misdialing or because the station is not authorized for
direct inward dialing, the ITR number of the caller is used (0).
AD-SYNCA: ANNMITR,WANNDNS, <ITR-A-STN>, and
AD-SYNCA: ANNMITR,WANNDNS, <ITR-DEST>, 19;
If an internal destination (internal user or internal hunting group) can be
determined, the ITR number of the internal user or hunting group master is used
(ITR = 3). If the destination number is an external number, the ITR number of the
caller is used.
AD-SYNCA: ANNMITR,WANNDNS, <ITR-DEST>, 19;
CHA-ZAND: TYPE = ATND, ISYNCAC=YES;
announcement.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
Help for Setting Synchronized Announcements
168.3 Help for Setting Synchronized Announcements

General
When using synchronized announcements wait times for the beginning of
announcements should be as brief as possible for economic reasons. After all,
charges are usually applied from the moment the request is entered - even before
the announcement has been activated. The examples and diagrams in this
document should provide some help for optimizing synchronized announcement
settings.
The wait time for announcement begin depends on various events, their time
sequence and also on parameter settings in SYNCA AMO.
The most influence have:
• traffic.
• length of the announcement text.
• number of announcement units allocated to an announcement type.
• set operating mode (Start/Stop or Continuous)
• set announcement delay time with Start/Stop operating mode
If the operating mode is CONTINUOUS then the wait time cannot be shortened
by administrative interventions or by jumpering. Even additional announcement
units will have no effect on the wait times.
Additional announcement units will only increase the number of callers for a
specific announcement (50 callers more per additional announcement unit).
The CONTINUOUS operating mode results in the following unchangeable wait

times:
– maximum possible wait time in individual case: length of text

announcement
– average wait time: half of text length
Depending on the traffic situation, wait times can only be optimized in the START/
STOP operating mode by setting a start delay time and the number of
announcement units per announcement type.
If the synchronized announcement is operated in START/STOP mode and traffic

shows too few announcement units per announcement, the operating mode is
automatically switched to temporary CONTINUOUS mode, if no idle
announcement unit can be found.
If bit 11 of the diagnosis bit string is set the system always outputs diagnosis
advisory messages at the point of switch-over. These messages contain
information about the capacity of individual announcement units in order to allow
system owners to react to the problem.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
The following diagrams show the changes of wait times for certain suppositions
depending on the number of announcement units (for a certain announcement
type) and the selected delay time.
Suppositions:
• traffic: number of calls per sec = 1
• text length: 10 sec.
• set operating mode: Start/Stop
Actions:
• modification of start delay time: (0 - 1 - 2 - 3 - 4 - 5) sec
• connection of announcement units for an announcement type: (1 - 2 - 3

- 4 ) units
Wait time for text start
sec
o (maximum possible delay)
13
11
9 0
7 o (average)
o o
o
o
5
o
4
delay time
0 1 2 3 4 5 sec
Example: Number of announcement units = 1

Comment: A synchronized announcement with start delay for only one
announcement unit is unreasonable. With an increasing start delay, both the
average wait time and the maximum wait time show near linear increase.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
sec
13
11
9
o o (maximum possible delay)
7
4 (average)
o o o o
o o
2
delay time
0 1 2 3 4 5 sec

Comment: In this case the maximum possible delay time is constant at 8
seconds. The shortest wait time (2.7 seconds) is achieved with a start delay time
of 2 seconds.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
sec
13
11
7 o
o
5 o o (maximum possible wait time)
o o
4
o o (average)
o
2 o
o o
delay time
0 1 2 3 4 5 sec

Comment: In this case the maximum possible wait time can obviously be
influenced by the start delay time. With a start delay time of 2 seconds the
average wait time for text start (1.5 seconds) reaches its minimum. The optimum
is a start delay time of 3 seconds.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
sec
13
11
7
o
5 o (maximum possible wait time)
4 o o
o o (average)
o
2 o o
o
o o
delay time
0 1 2 3 4 5 sec

Comment: In this case the maximum possible wait time reaches its minimum of 2
seconds with a start delay time of 2 seconds. The average wait time reaches its
minimum of 1.5 seconds also with a start delay time of 2 seconds.
Rule of thumb:
Calculation of the optimum timing for synchronized announcements, in order to

achieve briefer wait times for text start using different text lengths, is facilitated by
the following consideration.
The text length of the first active announcement unit must be covered by the
result of the start delay time and the number of additional announcement units.
Ergo: Text length = start delay time multiplied by the number of announcement
units.
Example:
• Text length: 40 sec
• Start delay time: 5 sec / 10 sec / 20 sec
• Number of announcement units: 8/4/2
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
In figures: 40 sec = 5 sec multiplied by 8 or

10 sec multiplied by 4 or
20 sec multiplied by 2 or ...
The number of necessary announcement units in relation to the set delay time
results from the following formula:
Number of announcement units = text length/begin delay time + 1
In figures: number of announcement units = 40 sec /5 sec + 1 = 8 + 1 = 9 or

= 40 sec /10 sec + 1 = 4 + 1 = 5 or
= 40 sec /20 sec + 1 = 2 + 1 = 3 or ...
If this procedure is used
• the maximum possible wait time for text start is always equal to the set start
delay time.
• the average wait time for text start is equal to half the maximum possible wait
time.
Which value combination is used depends on how many announcement units

should be used (matter of costs) to reduce the wait times for text start to which
justifiable value.
The following tables show possible combinations for different text lengths and the
resulting wait times for text start.
No. of Start delay time Max. possible wait Average wait time
announcement time
units
1+1 = 2 40 sec 40 sec 20 sec
2+1 = 3 20 sec 20 sec 10 sec
4+1 = 5 10 sec 10 sec 5 sec
5+1 = 6 8 sec 8 sec 4 sec
8+1 = 9 5 sec 5 sec 2.5 sec
10+1 = 11 4 sec 4 sec 2 sec
20+1 = 21 2 sec 2 sec 1 sec
Example: Text length = 40 sec.
announcement time
units
1+1 = 2 30 sec 30 sec 15 sec
2+1 = 3 15 sec 15 sec 7.5 sec
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
announcement time
units
5+1 = 6 6 sec 6 sec 3 sec
6+1 = 7 5 sec 5 sec 2,5 sec
10+1 = 11 3 sec 3 sec 1.5 sec
announcement time
units
1+1 = 2 20 sec 20 sec 10 sec
2+1 = 3 10 sec 10 sec 5 sec
4+1 = 5 5 sec 5 sec 2,5 sec
5+1 = 6 4 sec 4 sec 2 sec
10+1 = 11 2 sec 2 sec 1 sec
announcement time
units
1+1 = 2 10 sec 10 sec 5 sec
2+1 = 3 5 sec 5 sec 2,5 sec
5+1 = 6 2 sec 2 sec 1 sec
10+1 = 11 1 sec 1 sec 0,5 sec
Example: Text length = 10 sec
Comment:
It is possible to allocated several announcement units to the same
announcement type by assigning the same announcement type when
configuring the TMOM announcement board (TSCSU).
A maximum of 64 announcement units can be configured in the PBX. They
can be combined to any announcement types.
Extreme cases using 64 different announcement types with one
announcement unit each or only 1 announcement type with 64 assigned
announcement units are possible.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
Possible Reasons why Announcements may not Work
168.4 Possible Reasons why Announcements may not Work
168.4.1 General Requirements:

• Is the system feature "Synchronous Announcements" enabled (FEASU:
SYNCANN)?
• Is the "Synchronous Announcements" feature activated in the central system

data (ZAND: ALLDATA2, RAS=Y)?
• Has the internal application for "No answer on AC", for "Call to CSM" and for
"Call to hunting group call queue" been enabled using AMO ZAND?
• Is a sufficient number of announcement buffers assigned (DIMSU: SYNAN)?

50 announcement buffers must be assigned per announcement unit (max. 64
announcement units).
• Have the necessary announcement types been defined, and assigned to the
appropriate TMOM2 boards (TSCSU)
• Have the announcement types been activated, i.e. set to "ON" status?
(SYNCA)
• Are you sure that the appropriate incoming direct exchange traffic or tie-traffic
is being received?
• Are the TMOM2 connections compatible with the device type used?
Genius ST and MUSIFONE 5000 S have different interfaces.
• If you are running the announcements in START/STOP mode, have you set
the start delay timer value appropriately? (SYNCA)
• Have you defined an entry tone and a return tone for the appropriate
announcement reasons? (SYNCA)
• Announcement reason/announcement type table (ANNMITR/ANNMCI)

If the announcement type is to be used independently of an ITR value or the
last dialed digit, the announcement type must be explicitly entered into the
table for all ITR values and all last digits.
• Has the COT parameter ABPD (answering before suffix-dialing or

announcement) for the digital exchange trunks been set?
This COT parameter is mandatory for digital exchange lines, since the
exchange will otherwise not receive the necessary criterion for switching
through the call, i.e. the caller will not be able to hear the announcement.
For analog exchange lines, this parameter is not checked. However, it must
still be assigned if the exchange requires an answering criterion before
switching through the connection.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
The same applies for incoming exchange traffic via transit lines, i.e. the COT
parameter is not checked for the transit line. The parameter must be set if the
calling exchange in the originating node requires an answering criterion
before switching through the connection.
If the parameter is set, call charge pulses are signaled immediately the
announcement is started.
Have the 2 timers WFIRST and WNEXT of the device handler of the TMOM2
been set to the appropriate values? (DTIM1)
WFIRST defines the wait time for the first start of the announcement after
connecting to the announcement unit. In START/STOP operation, this value
can be kept small (1 - 4 sec.). If the announcement is run in CONTINUOUS
mode, the value must be greater than the length of the announcement. If this
timer runs down, a line alarm is set for the TMOM board. In this case, you
must check the JP interface cables.
WNEXT defines the wait time for the next start of the announcement following
the first start. This value must always be set to a longer value than the
announcement length. If timer runs down a line alarm is also set.
• If the diagnosis bit is set, call processing errors while attempting to access the
announcement unit are output by means of advisory messages
• (DIAGS: CC, CP, S06=Y).
• If a fault occurs, the error message F4066 CP ADVISORY is output for

diagnostic purposes.
• With remote parties: Has the COT parameter TNDV (tone injected from
terminal) been set for the digital tie trunk (EV 3.0 and higher)?
• With internal parties (calling party is terminal): Has the COS (ANSYN) been
set for the terminal (from EV3.0)?
• No synchronized announcement is injected after a call transfer (e.g. to CCM),

although the transferring party heard the announcement before transfer.
This can happened under the following circumstances:
– The announcement type of the synchronized announcement is in START/

STOP operating mode.
– Only one announcement unit is assigned to this announcement type
– The transferring terminal was the only device connected with the
synchronized announcement.
In this constellation the announcement unit is released during the transfer
procedure and needs several seconds to become operable again. Therefore,
for the transferred station there is no seizable announcement unit available at
the time of transfer (from EV 3.0).
Solution: Assign a second announcement unit to this announcement type.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
Set the operating mode of the announcement type to CONT.
168.4.2 Announcements for Attendant Call Queue

• Is the attendant group configured "with synchronous announcements"?
(VFGR: ANSYN=Y)?
• Is the COT parameter WAAN set for the route concerned?
• Has the caller dialed the attendant direct or has the call been extended to the
attendant via the attendant intercept feature?
• Is the announcement reason (WANNAOHK) entered in the ANNTONE

branch in the AMO-SYNCA?
For rerings, linked callback requests etc., no announcements will be
heard.
• Has the start delay timer been set to an appropriate value? (CTIME: CP1,
ATDLYANN)
• Have the correct entries been made in the announcement reason/

announcement type tables for ANNMCI and ANNMITR? (SYNCA)
– For direct dialing to the attendant group, the appropriate announcement

types must be entered for the WANNAOHK announcement reason in the
ANNMCI table for each possible last dialed digit.
– For attendant intercept of incoming exchange calls on lines without direct

inward dialing, the appropriate announcement types must be entered for
the WANNAOHK announcement reason in the ANNMITR table for the
ITR number of the exchange line.
– For callers who reach the attendant group via FWD/FNANS/FBSY, the
appropriate announcement types must be entered for the WANNAOHK
announcement reason in the ANNMITR table for the ITR number of the
forwarding station. However, this only works for forwarding stations in the
same node as the announcement unit. Otherwise, the ITR number of the
connecting line applies.
• If the synchronized announcement is installed in the CAC node, have the

COT parameters ABPD and WAAN been set for the tie trunk?
• Is the last digit in the attendant code entered for the ANNMCI branch in the
AMO-SYNCA (satellite PBX AMO-NAVAR, CD-CASEXT)?
• If the synchronized announcement is installed in the CAC node and is only to

be started, if the attendant console is in night service: has the COT parameter
ABNA been set for the tie trunk?
This parameter must not be set if you want the announcement to be enabled
at the CAC even during the day.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
• If the incoming trunk is an MSI trunk, has the COT parameter ABPD
(answering before suffix-dialing or announcement) been set?
• If the incoming trunk is an MSI trunk without DDI and digit prefixing, has the
appropriate announcement type been set using the administration in
ANNMITR for the ITR of the MSI trunk?
• Has the internal application (calling party is terminal) been enabled for
internal traffic using AMO ZAND (from EV 3.0)?
AMO-ZAND BRANCH ATND, parameter ISYNCAC = YES
• Is the parameter ANSYN set in the internal terminal’s COS?
168.4.3 Announcements for Calls to Multiple CCM

• Is the "Synchronous Announcements for CCM calls" feature activated in the
central system data (ZAND: CCM, SYNCACCM=Y)?
• Has the COP parameter CCR been set for the route concerned?
• Is parallel ringing configured? (ZAND: CCM, STNRNG=NO)

Parallel ringing is configured if the STNRNG parameter is set to Y, i.e. if the
forwarding station and the CCM are rung in parallel. In this case, callers will
hear the ringback tone.
• Is the announcement reason (ANNCCM) entered in the ANNTONE branch in

the AMO-SYNCA?
• Is the CCM set to MEET ME operation? (TSCSU)
• Is the COT parameter CHRT set for the connecting line, i.e. can the call be
transferred to the CCM?

announcement type table, ANNMITR? (SYNCA)
– For direct dialing to the CCM, the appropriate announcement types must
be entered for the ANNCCM announcement reason in the ANNMITR
table for the ITR number of the called party (for internal CCM users) or for
the ITR number of the CCM (for external CCM users.
– For callers who reach the code-calling system via FWD/FNANS/FBSY,

the appropriate announcement types must be entered for the ANNCCM
CCM applies.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
AMO-ZAND BRANCH CCM, parameter ISYNCCCM = YES
168.4.4 Announcements for Hunting Group Call

Queue
• Is the call queue capacity of the hunt group large enough? (SA: CQMAX > 0)?
• Is the hunting group configured "with synchronized announcements"? (SA:

CSANS=Y)?
• Are the COT parameters ANHT and BSHT set for the connecting lines?
• Is the announcement reason (WANNHG) entered in the ANNTONE branch in

the AMO-SYNCA?

– For direct dialing to the hunting group, the appropriate announcement

types must be entered for the WANNHG announcement reason in the
ANNMITR table for the ITR number of the first station in the hunting
group.
– For callers who reach the hunting group via FWD/FNANS/FBSY, the
appropriate announcement type must be entered for the WANNHG
first station in the hunting group applies.
AMO-ZAND BRANCH ALLDATA2, parameter ISYNCHG = YES
168.4.5 General Announcements if Called Station is

Busy
• Have the COT parameters ABNA&IBSY been set for the connecting line?
• Are you sure that the COT parameter KNDI has NOT been set for the
connecting line?
• Is the announcement reason (ANNBUSY) entered in the ANNTONE branch

in the AMO-SYNCA?
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm

• For direct lines:
– For direct dialing to the a station user, the appropriate announcement

types must be entered for the ANNBUSY announcement reason in
the ANNMITR table for the ITR number of the called station user.
– For callers who reach the station user via FWD/FNANS/FBSY, the
appropriate announcement types must be entered for the ANNBUSY
announcement reason in the ANNMITR table for the ITR number of
the forwarding station. However, this only works for forwarding
stations in the same node as the announcement unit. Otherwise, the
ITR number of the called, busy station user applies.
• For transit lines:

In this case, the connection is cleared back to the node with the exchange
line interface (originating node).
– Is the synchronized announcement configured in the originating

node?

types must be entered for the ANNBUSY announcement reason in
the ANNMITR table for the ITR number of the calling exchange line.
ITR number of the exchange line applies.
168.4.6 Announcement for Automatic Camp-on on

Busy Station
Synchronized announcements are only possible for incoming digital trunks.
Synchronized announcements are also possible for analog trunks, if the busy
station is an Anate or Digite.
• Has the COT parameter ABNA been set for the connecting line?
• Are you sure that the COT parameter IFR is NOT set for the connecting line?
• Has the COT parameter KNDI been set for the connecting line?
• Does any other station camp-on this busy station?
• Has "Call forwarding when busy" not been activated for the busy station?
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
• Can the busy station be camped on?
• If the busy station is a functional terminal, has the COS parameter MULTRA
not been set?
• Is the announcement reason (ANKNOCK) entered in the ANNTONE branch

in the AMO-SYNCA?

– For direct dialing to the busy station, the appropriate announcement type
must be entered for the ANNBUSY announcement reason in the
ANNMITR table for the ITR number of the busy station.
– For direct dialing to the busy station via internal FWD/FBSY, the
appropriate announcement type must be entered for the announcement
reason ANCAMPON in the ANNMITR table for the ITR number of the
forwarding party. However, this only works for forwarding stations in the
called, busy station user applies.
168.4.7 General Announcements with call to station

and no answer
• Has the COT parameter ABNA been set for the connecting line? (COT
parameter IFR is optional)
• Are you sure that the COT parameter KNDI has NOT been set for the
connecting line?
• Has the timer for "announcement with station no answer" been assigned an
appropriate value? (CTIME: CP1, ANNDIAL)
• Is the announcement reason (ANNOHK) entered in the ANNTONE branch in

the AMO-SYNCA?


types must be entered for the ANNOHK announcement reason in the
ANNMITR table for the ITR number of the called station user.
appropriate announcement types must be entered for the ANNOHK
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm


In this case, the timer runs in the node with the exchange line interface
(originating node).

node?

types must be entered for the ANNOHK announcement reason in the
ANNMITR table for the ITR number of the calling exchange line.
– For callers who reach the station user via FWD/FNANS, the
appropriate announcement type must be entered for the ANNOHK
stations in the same node as the announcement unit (e.g. originating
node). Otherwise, the ITR number of the exchange line applies.
168.4.8 Announcements for Suffix Dialing if Called

Station is Busy
• Is the feature "Suffix dialing if busy" enabled? (FEASU: POSTBUSY)
• Is the connecting line an analog exchange line?

The function is currently only implemented for analog exchange lines.
• Is the COT parameter PDOB set for the connecting line?
• Has the station user enabled automatic override?
• Is the announcement reason (SDBUSY) entered in the ANNTONE branch in

the AMO-SYNCA?


types must be entered for the SDBUSY announcement reason in the
ANNMITR table for the ITR number of the called, busy station user.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm

In this case, the connection is cleared back to the node with the exchange
line interface (originating node).

node?

types must be entered for the SDBUSY announcement reason in the
ANNMITR table for the ITR number of the calling exchange line.
ITR number of the exchange line applies.
168.4.9 Announcements for Suffix Dialing if Station

User does not Answer
• Is the feature "suffix dialing on no answer" enabled? (FEASU: POSTFREE)
• Is the connecting line an analog exchange line?

The function is currently only implemented for analog exchange lines.
• Is the COT parameter PDOT set for the connecting line?
• Is the announcement reason (SDOHK) entered in the ANNTONE branch in

the AMO-SYNCA?
• Has the timer for "announcement with station no answer" been assigned an
appropriate value? (CTIME: CP1, ANNDIAL)

types must be entered for the SDOHK announcement reason in the
ANNMITR table for the ITR number of the called, busy station user.
A31003-H3170-S103-6-7620, 02/2019
anse1_en.fm
appropriate announcement types must be entered for the ANNOHK

OpenScape 4000 V7, Volume 3 - Feature Usage Examples, Service Documentation, Issue 6.

Uploaded by

Copyright:

Available Formats

OpenScape 4000 V7, Volume 3 - Feature Usage Examples, Service Documentation, Issue 6.

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

OpenScape 4000 V7, Volume 3 - Feature Usage Examples, Service Documentation, Issue 6.

Uploaded by

Copyright:

Available Formats

OpenScape 4000 V7 

Feature Usage Examples

Our Quality and Environmental Management Systems are

1 Feature Usage Examples - Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

8.1.7 Configuring Preliminary Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

16.6 Generation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

23.1.4 Philosophy of supplementation (parameter EXTNO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

24.2.2.7 Configuration Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

27.2 Application Field of PBXXX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

29.6.2 BEL Test Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

33.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

37.3.1 Description of Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

37.15.3 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

39.3.3.2 Generation Notes on A Station Identification (After the B Number) . . . . . . . . . . . . . . . . . . . . . 455

42.2.1 One-level network (only Level 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503

45.2.1 CND (Calling Name Delivery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

48.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

56.5 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648

58.1.6 Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706

63 Call Detail Recording enhanced Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823

69 Central Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865

70.5.3 Enabling internal call detail recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905

79 CHESE/ Team Functions Network-wide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959

84.3 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018

89 Speaker Call - One-Way - Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087

94.3.3 Monitoring the room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109

99.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139

104.3 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1171

109 Dictation Equipment DICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1203

114.4.15 Call Routing when no CLI present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229

116.5.2.2 COT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1250

121.1.2 Mailboxes per line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283

131.5.2 Key assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323

133.2 PNT E for Connecting Functional Station Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354

141.1.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1379

144.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1413

149.4.3.1 Campon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444

153.6.1.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1472

155 Call Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1501

160.4.2.1 Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539

162.11 Ringback Tone for Diverted Call to analog CallDirector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1562

165.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609

172.6.2 General Administration of T1 BOS (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1683

173.11.3 Generation (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1708

182 ADIU - Attenuation of DIUC trunk circuits (CIS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1787

1 Feature Usage Examples - Overview

ACD (Automatic Call Distribution)

Subject Attendant Console

General Night Switching Options

Subject Call Detail Recording - Basic Information

Call Detail Recording

Subject Call Detail Recording - Usage Examples

CDRE - Call Detail Recording enhanced

INFO 2000 Outcalls

Subject Call Detail Recording - COT Parameter

AOCC - Request charges per line for remote station

COP and COT Parameter

Parameter Generation and Signaling for International Markets

COP and COT Parameter