Alcatel-Lucent Network

Alcatel-Lucent OmniPCX Enterprise
Communication Server
System Services
Release 12.1 - September 2017

8AL91000USAH Ed. 01
Legal notice
The information presented is subject to change without notice.
ALE International assumes no responsibility for inaccuracies contained herein.
Copyright © ALE International, 2017
Disclaimer
While efforts were made to verify the completeness and accuracy of the information contained in this
documentation, this document is provided “as is”. To get more accurate content concerning Cross
Compatibilities, Product Limits, Software Policy and Feature Lists, please refer to the accurate
documents published on the Business Partner Web Site.
In the interest of continued product development, ALE International reserves the right to make
improvements to this documentation and the products it describes at any time, without notice or
obligation.
The CE mark indicates that this product conforms to the following Council Directives:
• 2014/53/EU for radio equipment
• 2014/35/EU and 2014/30/EU for non radio equipment (including wired Telecom Terminal
Equipment)
• 2014/34/EU for ATEX equipment
• 2011/65/EU (RoHS)
Table of
contents System Services
Chapter 1
Reference documents
Chapter 2
Alcatel-Lucent OmniPCX Enterprise Communication Server overview
2.1 Overview.............................................................................................................................................27
2.1.1 Overview..................................................................................................................................................27
2.1.2 Operating Principle.............................................................................................................................28
2.1.3 Example of Implementation........................................................................................................... 29
2.1.4 Overview of the Different Components.................................................................................... 30
2.1.5 The ALE International offer............................................................................................................ 33
2.1.6 Software Overview............................................................................................................................. 35
2.1.7 Security.................................................................................................................................................... 35
Chapter 3
Compliance with standards
3.1 Overview.............................................................................................................................................36
Chapter 4
Communication Server duplication
4.1 Overview.............................................................................................................................................43
4.1.1 Overview..................................................................................................................................................43
4.2 Basic description.......................................................................................................................43
4.2.1 Principle................................................................................................................................................... 43
8AL91000USAH - Ed. 01 - September 2017 - System Services 3/458

Table of
4.2.2 Duplication on Common Hardware and Appliance Server............................................. 43

4.2.3 Duplication on Crystal Hardware.................................................................................................44
4.2.4 Restrictions............................................................................................................................................ 45
4.3 Detailed description................................................................................................................ 45
4.3.1 Start up.....................................................................................................................................................45
4.3.2 Data duplication................................................................................................................................... 46
4.3.3 Database consistency.......................................................................................................................46
4.3.4 "Double Main" Special Case (Common Hardware and Appliance Server only).. 47
4.3.5 Role Addressing.................................................................................................................................. 49
4.4 Switchover........................................................................................................................................49
4.4.1 Communications on hybrid logical links...................................................................................50
4.5 Installation procedure........................................................................................................... 55
4.5.1 Common Hardware and Appliance Server.............................................................................55
4.5.2 Crystal Hardware................................................................................................................................ 55
4.6 Configuration procedure....................................................................................................57
4.6.1 Checking Software Lock..................................................................................................................57
4.6.2 Configuring IP Addresses on Com Servers........................................................................... 58
4.6.3 Configuration Parameters...............................................................................................................59
4.6.4 Selecting Link Type for Duplication Data Transfer............................................................. 61
4.6.5 Configuring the Reference Media Gateway...........................................................................61
4.6.6 Forcing Configuration........................................................................................................................61
4.6.7 Ensuring Com Server Database Consistency...................................................................... 62
4.6.8 Installing a Pair of Duplicated Com Servers.......................................................................... 63
4.6.9 Adding a Standby Com Server.....................................................................................................63
4.6.10 Upgrading with a Static or Dynamic Patch without Interrupting Service..................63
4.6.11 Configuring hybrid link communication at switchover....................................................... 64
4.7 Maintenance....................................................................................................................................65
4.7.1 bascul Command................................................................................................................................65
4.7.2 twin Command.................................................................................................................................... 65
4.7.3 role Command.................................................................................................................................... 66
4.7.4 Incidents on the Standby Com Server......................................................................................66
4.7.5 Log File Relating to the Storage of MAO Commands.......................................................67
4.7.6 Incidents Relating to the Storage of MAO Commands.................................................... 67

Table of
Chapter 5
Passive Communication Server (PCS)
5.1 Overview.............................................................................................................................................68
5.2 Basic description.......................................................................................................................68
5.2.1 Topology.................................................................................................................................................. 68
5.2.2 Passive Communication Server Capacities and Configuration....................................69
5.2.3 Passive Communication Server Services...............................................................................69
5.2.4 Passive Communication Server Restrictions........................................................................ 70
5.3 Detailed description................................................................................................................ 70
5.3.1 Start-up.................................................................................................................................................... 70
5.3.2 Loss of signaling link between Passive Communication Servers and
Communication Servers.................................................................................................................. 72
5.3.3 Equipment Rescue............................................................................................................................. 73
5.3.4 Reestablishment of the signaling link........................................................................................78
5.3.5 Passive Communication Server modes...................................................................................79
5.3.6 Access to a SIP carrier.....................................................................................................................80
5.3.7 Services................................................................................................................................................... 83
5.4 Configuration procedure....................................................................................................84
5.4.1 Prerequisites..........................................................................................................................................84
5.4.2 IP ports..................................................................................................................................................... 84
5.4.3 Configuring a Passive Communication Server on the Communication Server.... 85
5.4.4 Declaring the Passive Communication Server addresses on the Communication
Server....................................................................................................................................................... 86
5.4.5 Configuring SIP external gateway for Communication Server and PCS.................87
5.4.6 Declaring the IP domain on the Communication Server..................................................87
5.4.7 Configuring the address of the Passive Communication Server in a GD............... 87
5.4.8 Configuring the address of the Passive Communication Server in the INTIP
boards.......................................................................................................................................................88
5.4.9 Configuring the address of the Passive Communication Server on SIP
equipment............................................................................................................................................... 88
5.4.10 PCS commissioning...........................................................................................................................88
5.4.11 Recommendations for an operating PCS............................................................................... 89
5.5 Maintenance....................................................................................................................................89

Table of
5.5.1 Traces....................................................................................................................................................... 89
5.5.2 Maintenance Tools..............................................................................................................................91
5.5.3 Alarms.......................................................................................................................................................92
Chapter 6
Topology
6.1 Introduction.....................................................................................................................................96
6.2 Main area based on an OmniPCX Media Gateway.................................... 96
6.2.1 Architecture............................................................................................................................................96
6.2.2 ACT in the main area........................................................................................................................ 97
6.3 Main area based on an ACT Media Gateway.................................................. 98
6.3.1 Communication Server on a CPU board................................................................................. 98
6.3.2 Communication Server on Appliance Server........................................................................ 99
6.4 Commissioning Media Gateways............................................................................ 100
Chapter 7
Resource allocation in an IP distributed architecture
7.1 Detailed description.............................................................................................................. 102

7.1.1 Introduction.......................................................................................................................................... 102
7.1.2 Example of IP Distributed Architecture.................................................................................. 102
7.1.3 Resource Allocation Description................................................................................................103

Table of
Chapter 8
Common Hardware media gateway
8.1 Overview...........................................................................................................................................106
8.1.1 Overview................................................................................................................................................106
8.2 Commissioning..........................................................................................................................106
8.2.1 Commissioning a Media Gateway............................................................................................ 106
8.2.2 Managing Rack Number................................................................................................................ 116
8.3 Maintenance..................................................................................................................................116
8.3.1 Connecting a Media Gateway.....................................................................................................116
8.3.2 Replacing a GD or GD-3 Board................................................................................................. 120
8.3.3 Communication between the GD or GD-3 Board and the Communication Server
....................................................................................................................................................................120
8.4 Cabling instructions............................................................................................................. 120

8.4.1 Classic Configurations....................................................................................................................121
8.4.2 IP Configurations...............................................................................................................................126
8.5 GD/GA or GD3/GA3 board reloading.................................................................... 128
8.5.1 Overview................................................................................................................................................128
8.5.2 GD or GA board reloading............................................................................................................129
8.5.3 Erasing and reloading a GD-3 board or GA-3 board.......................................................130
8.6 STP protocol.................................................................................................................................132
8.6.1 Overview of the problem................................................................................................................132
8.6.2 Spanning Tree Protocol................................................................................................................. 132
Chapter 9
Crystal Hardware media gateway
9.1 Overview...........................................................................................................................................135
9.1.1 Overview................................................................................................................................................135
9.2 Architecture...................................................................................................................................135

Table of
9.2.1 Configuration 1................................................................................................................................... 135

9.2.2 Configuration 2................................................................................................................................... 136
9.2.3 Configuration 3................................................................................................................................... 137
9.2.4 Restriction.............................................................................................................................................139
9.3 Commissioning..........................................................................................................................139
9.3.1 Overview................................................................................................................................................139
9.3.2 Principle................................................................................................................................................. 139
9.3.3 Declaring the INT-IP A Board......................................................................................................139
9.3.4 Declaring the ACT Media Gateway..........................................................................................139
9.3.5 Installing and Connecting INT-IP B (or IOIP) Board to the ACT Media Gateway
....................................................................................................................................................................141
9.3.6 Installing and Connecting INT-IP3 Board to the ACT Media Gateway................... 142
9.3.7 Starting the ACT Media Gateway............................................................................................. 142
9.3.8 Configuring the Address of the Passive Communication Server in the INTIP
board....................................................................................................................................................... 145
9.4 Maintenance..................................................................................................................................145
9.4.1 Connecting to a Media Gateway............................................................................................... 145
9.4.2 Error Codes..........................................................................................................................................146
9.4.3 Board Boot Traces............................................................................................................................146
9.5 INT-IP3 or IOIP3 board reloading..............................................................................147
9.5.1 Overview................................................................................................................................................147
9.5.2 Erasing and reloading a INT-IP3 board or a IOIP3 board.............................................148
Chapter 10
INTOF connections
10.1 Overview...........................................................................................................................................152
10.2.1 Connecting a Peripheral ACT by INTOF2 Boards............................................................152
10.2.2 Commissioning...................................................................................................................................153
10.2.3 Duplicating the Inter-ACT Link....................................................................................................154
10.2.4 Reserving B Channels....................................................................................................................154
10.2.5 Synchronization of INTOF2 Board............................................................................................154

Table of
10.2.6 Tones, Voice Guides, and On-hold Music.............................................................................155

10.2.7 Trunks..................................................................................................................................................... 155
10.2.8 Attendant............................................................................................................................................... 155
10.2.9 Voice mail..............................................................................................................................................155
10.2.10 Callbacks...............................................................................................................................................155
10.3 Installation procedure......................................................................................................... 155
10.3.1 Installation Procedure..................................................................................................................... 155
10.4 Configuration procedure..................................................................................................155
10.4.1 Principle................................................................................................................................................. 155
10.4.2 Reserving B Channels....................................................................................................................156
10.4.3 Declaring the Peripheral ACT on INTOF...............................................................................156
10.4.4 Declaring an INTOF Board on a Main ACT......................................................................... 156
10.4.5 Declaring an INTOF2 Board on a Peripheral ACT........................................................... 157
10.4.6 Declaring Duplicate Links............................................................................................................. 157
10.4.7 Consulting Board Status................................................................................................................157
10.5 Maintenance..................................................................................................................................158
10.5.1 Flashing and Downloading Procedure....................................................................................158
10.5.2 Maintenance Commands.............................................................................................................. 158
Chapter 11
INTOF signaling link (IOIP INT-IP)

11.1.1 Detailed description......................................................................................................................... 159
11.1.2 Duplication / switchover................................................................................................................. 161
11.1.3 Additional features............................................................................................................................162
11.2 Restrictions................................................................................................................................... 163
11.2.1 Restrictions.......................................................................................................................................... 163
11.3.1 Configuration procedure................................................................................................................ 163
11.3.2 Flash memory reloading................................................................................................................ 165

Table of
Chapter 12
Signaling link backup
12.1 Overview...........................................................................................................................................166
12.1.1 Overview................................................................................................................................................166
12.2 Basic description.....................................................................................................................166
12.2.1 Basic Description.............................................................................................................................. 166
12.3.1 Preliminary Configuration..............................................................................................................167
12.3.2 Switchover to the Backup Link................................................................................................... 168
12.3.3 Restrictions in Rescued (Backup) Mode............................................................................... 168
12.3.4 Return to Normal............................................................................................................................... 169
12.3.5 Rescuable and Rescuer Media Gateway..............................................................................169
12.3.6 Interaction with the RMA Service.............................................................................................. 169
12.3.7 Interaction with Call Server Duplication................................................................................. 169
12.3.8 Interaction with IP-Phones............................................................................................................170
12.3.9 Interaction with the DHCP Server.............................................................................................170
12.3.10 Recommendations for Installation of a Secure Link........................................................ 170
12.4.1 Declaring the Rescuer Media Gateways............................................................................... 171
12.4.2 Declaring the Rescuable Media Gateways.......................................................................... 171
12.4.3 Synchronizing Access.....................................................................................................................173
12.4.4 IP Domain............................................................................................................................................. 173
12.4.5 Timers..................................................................................................................................................... 173
12.5 Maintenance..................................................................................................................................173
12.5.1 The "bckdebug" Command.......................................................................................................... 173
12.5.2 The “trkstat” <ACT_nbr> <Cpl_nbr> Command................................................................ 175
12.5.3 Incidents (Error messages).......................................................................................................... 176

Table of
Chapter 13
Private to public overflow between IP media gateways
13.1 Overview...........................................................................................................................................177
13.1.1 Overview .............................................................................................................................................. 177
13.2.1 Steps of an Overflow....................................................................................................................... 178
13.2.2 Interaction with the Routing Service Intelligence.............................................................. 179
13.2.3 Accounting............................................................................................................................................180
13.2.4 Former Releases Compatibility.................................................................................................. 181
13.2.5 Restrictions.......................................................................................................................................... 181
13.3.1 Principle................................................................................................................................................. 181
13.3.2 User Right to Overflow................................................................................................................... 181
13.3.3 Node Access Prefix..........................................................................................................................182
13.3.4 Node DID Translation Tables...................................................................................................... 182
13.3.5 Authorizing Overflow on an Out of Service Set Rescued by the Passive
Communication Server...................................................................................................................183
13.4 Configuration examples....................................................................................................184
13.4.1 Example Overview............................................................................................................................184
13.4.2 User Overflow Right.........................................................................................................................185
13.4.3 Node Access Prefix..........................................................................................................................185
13.4.4 Translation Tables.............................................................................................................................185
13.4.5 ARS Configuration............................................................................................................................187
Chapter 14
IP services and port numbers
14.1 Overview...........................................................................................................................................191
14.1.1 Dynamic Port Range....................................................................................................................... 191
14.1.2 Types of Port....................................................................................................................................... 191
14.1.3 TFTP Connection..............................................................................................................................191

Table of
14.1.4 Passive FTP Connection...............................................................................................................192

14.1.5 IP services and Port Numbers....................................................................................................193
14.2 Configuring dynamic port range.............................................................................. 193
14.2.1 Configuring Dynamic Port Range............................................................................................. 193
14.2.2 Incidents................................................................................................................................................ 195
Chapter 15
Tones
15.1 Overview...........................................................................................................................................196
15.1.1 Overview................................................................................................................................................196
15.1.2 Related modules................................................................................................................................196
15.2.1 Principle................................................................................................................................................. 196
15.2.2 Tones for R2 signaling.................................................................................................................... 198
15.2.3 Tones specific to the USA.............................................................................................................198
15.3 Tone table........................................................................................................................................ 198
15.3.1 Tone table............................................................................................................................................. 198
15.4 Basic tones country by country................................................................................204
15.4.1 Overview................................................................................................................................................204
15.4.2 Argentina............................................................................................................................................... 204
15.4.3 Australia.................................................................................................................................................204
15.4.4 Austria.....................................................................................................................................................205
15.4.5 Bahrein................................................................................................................................................... 207
15.4.6 Belgium.................................................................................................................................................. 208
15.4.7 Brazil........................................................................................................................................................209
15.4.8 Cambodia..............................................................................................................................................211
15.4.9 Chile.........................................................................................................................................................211
15.4.10 China (People's Republic of)....................................................................................................... 211
15.4.11 Colombia............................................................................................................................................... 212
15.4.12 Costa Rica............................................................................................................................................ 212
15.4.13 Czech Republic..................................................................................................................................212
15.4.14 Denmark................................................................................................................................................ 212

Table of
15.4.15 Ecuador..................................................................................................................................................214
15.4.16 Egypt....................................................................................................................................................... 214
15.4.17 El Salvador........................................................................................................................................... 215
15.4.18 Finland....................................................................................................................................................215
15.4.19 France.....................................................................................................................................................216
15.4.20 Germany................................................................................................................................................218
15.4.21 Greece....................................................................................................................................................219
15.4.22 Hong Kong............................................................................................................................................221
15.4.23 Hungary................................................................................................................................................. 222
15.4.24 India......................................................................................................................................................... 223
15.4.25 Indonesia...............................................................................................................................................225
15.4.26 Ireland (Eire)........................................................................................................................................225
15.4.27 Israel........................................................................................................................................................226
15.4.28 Italy...........................................................................................................................................................227
15.4.29 Japan...................................................................................................................................................... 229
15.4.30 Korea (Republic of).......................................................................................................................... 230
15.4.31 Latin America...................................................................................................................................... 231
15.4.32 Laos......................................................................................................................................................... 233
15.4.33 Luxembourg.........................................................................................................................................233
15.4.34 Malaysia.................................................................................................................................................233
15.4.35 Malta........................................................................................................................................................234
15.4.36 Mexico.................................................................................................................................................... 236
15.4.37 Myanmar (Burma).............................................................................................................................236
15.4.38 Netherlands..........................................................................................................................................236
15.4.39 New Zealand....................................................................................................................................... 237
15.4.40 Norway................................................................................................................................................... 237
15.4.41 Oman...................................................................................................................................................... 239
15.4.42 Peru......................................................................................................................................................... 240
15.4.43 Philippines............................................................................................................................................ 241
15.4.44 Poland.....................................................................................................................................................241
15.4.45 Portugal..................................................................................................................................................243
15.4.46 Russia and the CIS.......................................................................................................................... 244
15.4.47 Singapore..............................................................................................................................................246
15.4.48 Slovakia................................................................................................................................................. 247
15.4.49 Spain....................................................................................................................................................... 248
15.4.50 South Africa......................................................................................................................................... 250
15.4.51 Sweden.................................................................................................................................................. 251
15.4.52 Switzerland...........................................................................................................................................253

Table of
15.4.53 United Kingdom (UK)...................................................................................................................... 254

15.4.54 Taiwan.....................................................................................................................................................255
15.4.55 Thailand................................................................................................................................................. 257
15.4.56 United Arab Emirates......................................................................................................................257
15.4.57 United States (USA)........................................................................................................................ 258
15.4.58 Uruguay................................................................................................................................................. 259
15.4.59 Venezuela............................................................................................................................................. 259
15.4.60 Viet Nam................................................................................................................................................259
15.4.61 Yugoslavia............................................................................................................................................ 260
15.5 R1 and R2 frequencies....................................................................................................... 261
15.5.1 R1 frequencies................................................................................................................................... 261
15.5.2 R2 frequencies................................................................................................................................... 262
15.6.1 Introduction.......................................................................................................................................... 265
15.6.2 Tone......................................................................................................................................................... 265
15.6.3 Prefix for tone playback................................................................................................................. 266
15.6.4 Playback timer.................................................................................................................................... 266
15.6.5 R1 and R2 signaling........................................................................................................................ 266
15.6.6 Reinitialising the tones plan......................................................................................................... 267
Chapter 16
Voice guides and music-on-hold
16.1 Overview...........................................................................................................................................268
16.1.1 Types of voice messages..............................................................................................................268
16.1.2 Types of voice guides..................................................................................................................... 268
16.1.3 Reserved numbers and number of times a voice message can be called........... 271
16.1.4 Related modules................................................................................................................................271
16.2.1 Static voice messages....................................................................................................................271
16.2.2 Dynamic voice messages............................................................................................................. 275
16.2.3 External music.................................................................................................................................... 276
16.2.4 Physical interfaces............................................................................................................................276
16.2.5 Organization on a Media Gateway........................................................................................... 279

Table of
16.2.6 Recognizing and selecting voice guides................................................................................282

16.2.7 Type of playback................................................................................................................................282
16.2.8 Backup tone.........................................................................................................................................283
16.2.9 Listening class.................................................................................................................................... 283
16.3 Voice guide message content..................................................................................... 283
16.3.1 Overview................................................................................................................................................283
16.3.2 Descriptive table of voice guides...............................................................................................283
16.4 Voice guide indices by language............................................................................. 290
16.4.1 Language correspondence table...............................................................................................290
16.5 Voice guide transfer.............................................................................................................. 295
16.5.1 Purpose..................................................................................................................................................295
16.5.2 Hardware and software required............................................................................................... 295
16.5.3 Using the AAS software.................................................................................................................295
16.5.4 Transferring dynamic voice guides via FTP.........................................................................300
16.6 External music............................................................................................................................303
16.6.1 Connecting an external device to a GD (AFU) or SLI board....................................... 303
16.6.2 Connecting an external device to a CPU7-2/CPU8 or Z20VG board..................... 304
16.6.3 Management and verifications....................................................................................................305
16.7.1 Overview................................................................................................................................................305
16.7.2 Downloading files..............................................................................................................................306
16.7.3 Declaring GPA board DSPs......................................................................................................... 307
16.7.4 Managing languages....................................................................................................................... 308
16.7.5 Managing voice guides.................................................................................................................. 310
16.7.6 Managing voice guides for music-on-hold............................................................................ 313
16.7.7 Managing music and voice guides on external equipment.......................................... 313
16.7.8 Managing dynamic voice messages........................................................................................314
16.8 Configuration examples....................................................................................................316
16.8.1 Overview................................................................................................................................................316
16.8.2 Loading voice messages...............................................................................................................317
16.8.3 Managing system languages...................................................................................................... 317
16.8.4 Managing the languages associated with the index........................................................ 318
16.8.5 Defining internal music................................................................................................................... 319
16.8.6 Using external music-on-hold..................................................................................................... 320
16.8.7 Connecting a CD player to the AFU daughterboard........................................................320
16.8.8 Creating a greeting message for routing to a set.............................................................. 320

Table of
16.8.9 Adding a language............................................................................................................................321

16.8.10 Declaring music-on-hold with specific files...........................................................................321
16.9 Recording dynamic messages from a set.......................................................322
16.9.1 Overview................................................................................................................................................322
16.9.2 Recording from a set....................................................................................................................... 322
16.10 Maintenance..................................................................................................................................326
16.10.1 Useful commands............................................................................................................................. 326
16.10.2 Music-On-Hold commands...........................................................................................................331
16.10.3 Checking the version of voice guides..................................................................................... 332
16.10.4 Dynamic voice messages............................................................................................................. 333
Chapter 17
Date and time management
17.1 Overview...........................................................................................................................................334
17.1.1 Overview................................................................................................................................................334
17.2.1 Text Messages....................................................................................................................................335
17.2.2 Appointment and Wake Up Time...............................................................................................335
17.2.3 DECT or PWT Sets.......................................................................................................................... 335
17.2.4 Unanswered Calls.............................................................................................................................335
17.2.5 Accounting Tickets........................................................................................................................... 335
17.2.6 Incidents................................................................................................................................................ 335
17.2.7 Passive Communication Server.................................................................................................335
17.2.8 Time Update by ISDN..................................................................................................................... 336
17.2.9 Restrictions.......................................................................................................................................... 336
17.3.1 System Date and Time...................................................................................................................336
17.3.2 System Time Zone........................................................................................................................... 337
17.3.3 IP Domain Time Zone..................................................................................................................... 337

Table of
Chapter 18
Multi-country configuration
18.1 Overview...........................................................................................................................................339
18.2.1 Device Behavior.................................................................................................................................339
18.2.2 Tone Setup........................................................................................................................................... 341
18.2.3 Numbering Plan................................................................................................................................. 342
18.2.4 Restrictions.......................................................................................................................................... 342
18.3.1 System Country................................................................................................................................. 342
18.3.2 Multi-Country....................................................................................................................................... 342
18.3.3 Enhanced Multi-country................................................................................................................. 343
18.3.4 IP Domain Country........................................................................................................................... 343
18.3.5 Board Country.....................................................................................................................................344
Chapter 19
Timer management
19.1 Overview...........................................................................................................................................345
19.1.1 General.................................................................................................................................................. 345
19.1.2 Reference to related modules.....................................................................................................346
19.2 List of timers................................................................................................................................ 346
19.3 Timer management................................................................................................................ 367
19.4 Maintenance..................................................................................................................................368

Table of
Chapter 20
Licenses
20.1 Overview...........................................................................................................................................369
20.2 Basic description.....................................................................................................................369
20.3.1 Licenses.................................................................................................................................................369
20.3.2 Locks....................................................................................................................................................... 370
20.3.3 Purchasing process......................................................................................................................... 370
20.3.4 OPS files................................................................................................................................................371
20.3.5 Risk in case of fraudulent use.....................................................................................................371
20.3.6 Changing the CS board for maintenance..............................................................................372
20.3.7 License move (from R5.1)............................................................................................................ 373
20.3.8 Test sets (from R5.1.1)................................................................................................................... 373
20.3.9 Licensing using FlexLM server...................................................................................................374
20.3.10 Licensing using Cloud Connect................................................................................................. 377
20.4.1 Principle................................................................................................................................................. 382
20.4.2 Managing OPS files with swinst................................................................................................382
20.4.3 Consulting locks via the configuration tool........................................................................... 387
20.4.4 Processing the OPS files for OmniVista 8770.................................................................... 387
20.4.5 Incidents/errors.................................................................................................................................. 388
20.4.6 Configuring CSTA/TSAPI parameters (UCaaS configuration)....................................388
20.4.7 Configuring a FlexLM server....................................................................................................... 390
20.4.8 Configuring licensing via Cloud Connect.............................................................................. 391
20.5 License move...............................................................................................................................395
20.5.1 Overview................................................................................................................................................395
20.5.2 License: “10 Phonebook users” (lock 2)................................................................................ 395
20.5.3 License: “CCD 5 agents pack” (lock 76)................................................................................396
20.5.4 License: “Roaming DECT” (lock 90)........................................................................................396
20.5.5 License: “ECC 4980 option 10 ext pack” (lock 117).........................................................396
20.5.6 License: “DECT encryption” (lock 127).................................................................................. 396
20.5.7 License: “ECC My softphone 10 ext pack” (lock 129).....................................................397
20.5.8 Set Licenses (locks 173, 174, 176 and 177)....................................................................... 397

Table of
20.5.9 License: “10 Mobile users” (lock 175).....................................................................................398

20.5.10 License: “G729A Client” (lock 197).......................................................................................... 398
20.5.11 License: “OmniCellular client for 10 users” (lock 308)....................................................398
20.5.12 License: “Class service (CLIP) for 10 analog users” (lock 310).................................398
20.6 List of software locks.......................................................................................................... 399
20.6.1 List of OmniPCX Enterprise Locks........................................................................................... 399
Chapter 21
List of user profiles
21.1 Overview...........................................................................................................................................421
21.2.1 User profiles description................................................................................................................ 421
21.2.2 Types of user profiles......................................................................................................................422
21.3 List of user profiles................................................................................................................426
21.3.1 ALE International list of user profiles.......................................................................................426
Chapter 22
PCX synchronization
22.1 Overview...........................................................................................................................................433
22.1.1 Overview................................................................................................................................................433
22.2.1 Outline of the Problem....................................................................................................................433
22.2.2 Solution Adopted for Synchronous Transmission............................................................. 433
22.2.3 External Synchronization Sources............................................................................................434
22.2.4 Internal Synchronization Sources............................................................................................. 434
22.2.5 Transporting the Synchronization on Links between Shelves.................................... 434
22.2.6 Synchronization Domains............................................................................................................. 435
22.2.7 Synchronization Priority................................................................................................................. 436

Table of
22.2.8 Interaction between DECT/PWT and Synchronization.................................................. 436

22.3 Engineering rules.................................................................................................................... 436
22.3.1 Synchronization within a Private Network.............................................................................436
22.3.2 Synchronization within a Node................................................................................................... 438
22.3.3 Migration of an OmniPCX 4400 to OmniPCX Enterprise with Appliance Server
....................................................................................................................................................................447

22.4.1 Overview................................................................................................................................................451
22.4.2 Synchronization Priority on a Digital Access....................................................................... 451
22.4.3 Synchronization Priority on a PCM Board............................................................................ 452
Chapter 23
Rainbow
23.1 Overview...........................................................................................................................................453
23.2 Description.....................................................................................................................................453
23.3 Configuration...............................................................................................................................455
23.3.1 Configuring network parameters............................................................................................... 455
23.3.2 Configuring the Rainbow parameters..................................................................................... 455

Chapter
1 Reference documents
The OmniPCX Enterprise documentation includes the documents listed in the following table:
table 1.1: OmniPCX Enterprise Documentation
Documentation title Part number
[1] System Services 8AL91000xxyy

Summary: this document provides an overview of system architecture,
topologies, as well as server duplication. It describes how to implement
synchronization and specific connections, as well as licenses, timers,
voice guides (and music-on-hold), languages and date and time.
[2] Management Tools 8AL91002xxyy

Summary: this document describes how to configure access rights to
the system by the management application, how to implement a config-
uration by domains and how to translate the strings displayed on tele-
phone sets and specific OmniPCX Enterprise applications.
[3] User Services 8AL91003xxyy

Summary: this document describes how to implement basic telephone
features such as broker call and transfer, as well as more advanced
collaboration features such as call pick-up, conferences and twin sets.
Each feature is presented in a separated chapter providing a descrip-
tion, the necessary configuration and, if need be, how to operate it.
[4] Attendant Services 8AL91004xxyy

Summary: this document describes how to implement attendant con-
soles. It also details the integrated automated attendant feature and
specific configurations for attendant consoles.
[5] Public Networks 8AL91005xxyy

Summary: this document describes the available features to configure
and implement accesses to public networks
[6] Private Networks 8AL91006xxyy

and implement networks of OmniPCX Enterprises, including QSIG and
PCX synchronization.
[7] IP-PCX Networks 8AL91007xxyy

and implement IP networks. It covers IP redundancy, quality supervi-
sion, SNMP, security and authentications.

Chapter 1 Reference documents
[8] Voice Mail 8AL91008xxyy

Summary: this document describes how to implement and configure the
native 4645 voice mail service in IMAP or VPIM. It also describes how
to centralize voice mail for several nodes and how to implement an ex-
ternal voice mail system.
[9] Mobility 8AL91009xxyy

Summary: this document describes the available features for DECT
sets and how to implement and configure every service. This document
also covers the various ways for GSM sets to rely on OmniPCX Enter-
prise services and the implementation of paging for authorized users.
[10] General Applications 8AL91010xxyy

Summary: this document describes how users can access external ap-
plications via a Presentation server. It also details how call distribution
can be precisely controlled or temporarily restricted for external calls or
within a specific group of users. The configuration to filtering of incom-
ing calls is also presented. Finally, this document covers how to share
an OmniPCX Enterprise between distinct companies and how to imple-
ment metering features, in order to monitor and control call costs.
[11] Hotel/Hospital 8AL91016xxyy

Summary: this document describes the operations and configuration of
the hospitality feature integrated to the OmniPCX Enterprise. It details
the different configurations, by room or by guest and how to connect
the system to an external hospitality application.
[13] Maintenance 8AL91011xxyy

Summary: this document details the syntax and result of the most com-
mon maintenance commands. It also details the management of inci-
dents and alarms, as well as SNMP. It covers remote maintenance fea-
tures and the operations of sets dedicated to alarms.
[14] Security 8AL91012xxyy

Summary: this document includes a detailed description on the neces-
sary measures to ensure the highest system security. Guidelines and
configuration details are provided to cover every level of this highly sen-
sitive issue.
[15] PWT 8AL91019xxyy

Summary: this document describes the implementation and configura-
tion of mobile sets relying on the PWT protocol in an OmniPCX Enter-
prise environment.

[16] Crystal Hardware System Boards 8AL91020xxyy

Summary: this document provides a detailed description of the different
system boards available in the Crystal hardware package. A visual
guidance of the default and specific positions of straps, as well as con-
nections are included.
[17] Crystal Hardware Interface Boards 8AL91021xxyy

interface boards available in the Crystal hardware package. These
boards allow the implementation of T0/S0 interfaces, DECT, analog ter-
minals, accesses to the public network, the implementation of different
OmniPCX Enterprise nodes and IP communications. A visual guidance
of the default and specific positions of straps, as well as connections
are included.
[18] Common Hardware Boards 8AL91022xxyy

boards available in the Common hardware package. Each board is de-
scribed individually. A visual guidance of connections is included for
each board.
[19] Cables 8AL91023xxyy

cables available for Crystal hardware interface boards. Maximum length
are indicated for each type of cables.
[20] Dedicated sets 8AL91024xxyy

Summary: this document provides a detailed description of the propriet-
ary sets and generic sets (including heavy-duty sets), available for the
OmniPCX Enterprise. These telephones sets can be TDM, IP or mo-
bile. Ergonomics, environmental constraints, power supply, initialization
and configuration are explained for each set.
[21] TA and TSC Adapters 8AL91025xxyy

Summary: this document provides a detailed description of the availa-
ble adapters for V24, CTI, S0 and analog peripheral. A visual guidance
of the default and specific positions of straps, as well as connections
are included.
[22] Complementary Equipment 8AL91026xxyy

Summary: this document describes the available connecting devices for
external devices, as well as V24 interfaces, tie line filter box and IBS
base stations for DECT roaming.

[23] Common Hardware Installation Manual 8AL91027xxyy

Summary: this document details what is necessary to install a Common
hardware system. Recommendations on the best environmental situa-
tions are included along with system specificities. The installation pro-
cedure details assembling, internal connections, external connections,
power supplies and first level maintenance operations.
[24] Crystal Hardware Installation Manual 8AL91028xxyy

Summary: this document provides separate chapters for each available
Crystal hardware rack. Recommendations on the best environmental
situations are included along with system specificities and cabling dia-
grams, with visual guidance to implement connections.
[25] Appliance Server Installation Manual 8AL91029xxyy

Summary: this document provides all the necessary information to com-
mission an appliance server, with or without uninterruptible power sup-
ply. Technical specifications and software version compatibilities are
provided for each available piece of hardware.
[26] Blade Center Installation Manual 8AL91030xxyy

mission a blade center, replacing up to fourteen separate servers, in an
OmniPCX Enterprise network, offering maintenance and redundancy
facilities. A precise installation procedure is included. It details how to
download a system software and how to update firmware.
[27] PCX on Standard Racks Installation Manual 8AL91031xxyy

mission a Crystal hardware OmniPCX Enterprise on industry-standard
racks. It details wiring, power supply and fixing kit recommendations
[28] Software Installation Manual 8AL91032xxyy

Summary: this document details the partitions and directories, along
with their contents necessary for system operations. It describes the dif-
ferent procedures available to deploy the software, on site or from a re-
mote location, on a physical or virtual environment.
[29] ALEDS 8AL90508xxyy

Summary: this document describes the implementation of this deploy-
ment tool in the various compatible topologies. This documents in-
cludes requirements and procedures to install each software, among
which the OmniPCX Enterprise. Software deployments and updates are
explained for physical and virtual machines.

[30] Customer Management via mgr 3EU19871xxyy

Summary: this administration manual describes how to connect, set
menus and navigate with this text interface management tools. It pro-
vides information on basic configurations, such as creating users,
speed dialing numbers, directory, telephone class of service or modify-
ing metering costs.
[31] Customer Management via 8770 8AL90615xxyy

Summary: this administration manual describes how to connect to the
OmniVista 8770 client and navigate in this GUI application. It lists the
available configurations for the OmniPCX Enterprise and provides infor-
mation on basic configurations, such as creating users, speed dialing
numbers, telephone services, alarm sets and phone book.
[32] Alcatel-Lucent 4645 - Administrator Manual 3EU19873xxyy

Summary: this administration manual describes how to configure and
implement the voice mail system embedded in the OmniPCX Enter-
prise. It also details the procedure to rely on distribution lists, how to
create mail boxes (including temporary mail boxes in hotel/hospital en-
vironments), set up an automated attendant for incoming calls, as well
as record and implement customized announcements.
[33] Internal Accounting - Administrator Manual 3EU19833xxyy

Summary: this administration manual describes how to configure and
implement the cost metering system embedded in the OmniPCX Enter-
prise. Procedures explain how to set up the different communication
types (normal, business and personal) and process the records. This
document also details how to monitor call costs from a telephone set.
[36] Alcatel-Lucent 4059 IP Attendant Console 3EU19877xxyy

Summary: this user manual describes the various features available for
attendants using a 4059 IP set. Configuration procedures are also de-
tailed.
[37] Alcatel-Lucent IP Touch 4068 Attendant Set 8AL90607xxyy

attendants using a 4068 IP set configured for this particular usage. Ba-
sic configuration procedures are also detailed.
[38] Alcatel-Lucent 4645 VMS - User Manual 3EU19583xxyy

system users wishing to make the most of this voice mail and custom-
ize their announcements.

[39] Hotel - Hospital - User Manual 3EU19837xxyy

hotel/hospital staff to configure and modify and retrieve metering re-
cords for the guests on their facility. Room service management and
basic configuration procedures are also detailed.
[40] Dongle IP / Raspberry for OpenTouch Suite 8AL90617xxyy

Summary: this document covers the deployment of USB over an IP
dongle with OmniPCX Enterprise systems to support FlexLM server de-
ployments. Procedures explain how to install the dongle, obtain the
firmware and boot the system.
[41] NFC Extended OXE Mobility Administration Manual 8AL90614xxyy

Summary: this administration manual describes the implementation of
transparent call shifts from a device to the other via NFC tags. NFC tag
generation is detailed with screenshots from the application.
[42] NFC Extended OXE Mobility User Manual 8AL90613xxyy

Summary: this user manual describes the implementation of transpar-
ent call shifts from a device to the other via NFC tags. Procedures to
read NFC tags and shift calls are provided, and the necessary mobile
phone settings are detailed.
[43] OmniVista 8770 Administrator Manual 8AL90703xxyy

[44] SP0123 Cabinet user manual and technical specifications 8AL90637xxyy
In the present document, cross-references are identified by the number in the first column of the above
table.
Part numbers are given in the last column, where xx corresponds to the language code of the
document, and yy to the incremented edition of the document.

Chapter
2 Alcatel-Lucent OmniPCX Enterprise

Communication Server overview
2.1 Overview
2.1.1 Overview
The OmniPCX Enterprise (Linux version) is a private telephone switch based on an IP data network
infrastructure.
The main components of the OmniPCX Enterprise are:
• The Call Server, which is the system control center
• One or more (possibly none) Media Gateways supporting standard telephone equipment:
• Wired digital or analog sets
• Lines to the standard public or private telephone networks
• DECT or PWT mobile phone base stations
• Voice guides
• Compressors to ensure the link between standard and IP phones
• IP terminals (SIP terminals, multi-media PCs or H.323 terminals)
• DECT or PWT mobile sets
• Mobile IP Touch WLAN sets: these sets are linked to the OmniPCX Enterprise through a wireless
LAN
• External applications such as voice mail and the OmniVista 8770 management console

Chapter 2 Alcatel-Lucent OmniPCX Enterprise Communication
Server overview
OmniVista
8770
Voice Mail &
Console
Automated
Call Server Attendant 4645
IP
IP Phones
Voice over Wireless LAN

IP-FAX IP
SVP Server
IP Network * OmniAccess
V24 / IP
Wireless Switch
Adapt.
Asynchronous VT100
Terminal
OmniPCX
AccessPoint MIPT Set
Media Gateway
Router ACT
Media
Gateway
To other IP Networks
Wired Equipment
Public Network
RBS - IBS Base Stations

Wired TDM Sets Analog Sets and Fax Machines
(DECT or PWT)
and Mobile Sets
Figure 2.1: The OmniPCX Enterprise Telephone System
(*) : Local client network (LAN) or OmniPCX Enterprise-specific network.

Other Characteristics:
• An OmniPCX Enterprise can belong to an ABC-F network - in such a network OmniPCX Enterprises
can be interconnected
• An OmniPCX Enterprise can use direct RTP to optimize IP resources. In case of a full-IP network
(nodes connected by ABC-F IP logical links and subnetworks connected by ABC-F IP trunk groups),
RTP flow is direct throughout the network.
• An OmniPCX Enterprise can connect to the following public networks:
• Digital: ISDN T0/T1/T2
• Digital: T1 CAS
• Analog: NDDI
• Analog: Loop start
• Analog: Ground start
• SIP
2.1.2 Operating Principle

The Call Server is a software program that runs with LINUX. It centralizes the configuration of each
system element. It also stores the current status of each element in its memory (set, trunk, trunk group,
etc.). To give a (simplified) example, a set may be: idle, ringing or in conversation. When an event

Server overview
occurs (set unhooked for example), this event is notified to the Call Server by the Media Gateway. The
Call Server, according to set configuration and status, carries on the operations to be performed. In the
case of an idle set being picked up, it can send the dialing prompt tone. The order is transmitted to the
Media Gateway via the IP network. The Media Gateway interprets the order from the Call Server and
connects the required tone to the designated set.
This scenario is identical for all system elements.
Protocols Used:
• Voice calls transit on IP segments using one of the following protocols: H.323, SIP or a proprietary
protocol (used by IP phones provided by ALE International) and one of the following coding
algorithms: G711, G722, G723 or G729
• Data calls transit on IP segments by encapsulation in IP datagrams
• FAX calls transit on IP segments using T.38 protocol or, possibly, a proprietary protocol (for
equipment provided by ALE International)
2.1.3 Example of Implementation

An IP network may cover one or more local area networks (LANs) or local networks linked via public
networks to make Wide Area Networks (WANs).
Main Site
Call Server
Media Gateway
Local Network
Router
Secondary Site
Public
Router Local Network
WAN Network
Media Gateway
Router
Secondary Site
Local Network
Media Gateway
Figure 2.2: Example of Multi-Site Implementation of a Node

Server overview
To counterbalance possible IP network breakdowns between headquarters and branch offices, the
OmniPCX Enterprise provides several defence mechanisms such as: Passive Communication Server,
IP backup signaling link, IP phone survivability.
The OmniPCX Enterprise allows to build a node encompassing several branch offices in various
countries. Users are provided with a time display corresponding to their actual geographical time zone
and text display in their own language, including languages written in non-Latin characters such as
Chinese, Japanese, Korean or languages using the Cyrillic alphabet.
2.1.4 Overview of the Different Components

2.1.4.1 Call Server
The Call Server is a program that can run on the following hardware:
• Appliance Server. The Appliance Server is a Personal Computer. This machine is configured and
delivered by ALE International.
• CS board. This board is installed in an S or L rack (Common Hardware). All connections with other
components are via IP link.
• CPU board (CPU8, CPU7-2) in an ACT cabinet (Crystal Hardware).
The Call Server can be duplicated for reliability. Duplication is only possible when the backup Call
Server is of the same type as the main Call Server.
In order to improve reliability, the 2 Call Servers can be located in two different IP subnetworks.
Signaling between a Call Server and an OmniPCX Media Gateway can be backed up by the public
switched telephone network.
2.1.4.2 Passive Communication Server

Passive Communication Servers provide continuity of telephony services in case of:
• Loss of two duplicated Call Servers
• Loss of a non-duplicated Call Server
• Breakdown of IP links between remote sites and Call Servers
2.1.4.3 OmniPCX Media Gateway

The OmniPCX Media Gateway is supported on S and L racks (Common Hardware). These racks have
3 or 9 board slots. If 9 slots are not sufficient, two extension racks (maximum) can be connected for
increased capacity.
The OmniPCX Media Gateway has:
• A 220V (or 110V) AC/48V DC power supply
• Batteries ensuring limited autonomy (several minutes). Their purpose is to ensure that the system
can shut down correctly. For increased autonomy, external battery cabinets or a UPS are required
• A GD board, ensuring:
• The IP link with the Call Server
• Support of the compressors/decompressors enabling voice calls with the other Media Gateways,
the IP-Phones and standard telephone resources (not IP)
• Support of the voice guides, tones and 3-party conference circuits
• The link with the rack interface boards
• The link with the extension racks
• Interface boards, that are used to connect:
• Digital or analog sets
• DECT – IBS (or PWT) mobile phone base stations

Server overview
• Links with the public or private analog or digital networks

• Possibly, one or two extension racks, connected to the main rack via an extension board
Call Server IP Network
IP Link
OmniPCX
Media Gateway
1 HSL Link
3
Main Rack
Extension Rack 1 Extension Rack 2
2
HSL Link
UA Link
Figure 2.3: OmniPCX Media Gateway with Extensions
In the above figure, rack (1) is directly connected to the IP network. Racks (2) and (3) are extension
racks; they are connected by HSLs (High Speed Links).
2.1.4.4 ACT shelf

An ACT shelf is based on Crystal Hardware. It can be implemented in several ways.
2.1.4.4.1 Main ACT shelf
A main ACT shelf houses a Call Server supported by a CPU board. In addition, the main ACT allows
the following devices to be connected:
• TDM or analog sets
• T0, T1 or T2 digital networks
• Analog networks
• DECT/PWT – base stations
• IP network
• Peripheral INTOF/RT2 shelf
• ... .
2.1.4.4.2 Peripheral ACT shelf
This shelf is connected to the main ACT through an INTOF or RT2 link. This shelf is under the control
of the Call Server located in the main ACT. The peripheral ACT shelf can support the same equipment
as the main ACT shelf.
2.1.4.4.3 Auxiliary ACT Media Gateway
An auxiliary ACT Media Gateway is used to support equipment (devices) not supported on Common
Hardware.
It includes:
• One or more public or private network interface boards (for example LDTL, etc.)

Server overview
• One or more auxiliary boards (for example GPA)

• One or more DECT – RBS connection boards
2.1.4.4.4 Standard ACT Media Gateway
A standard ACT Media Gateway is a remote ACT (connected via the IP network). It is connected to the
Call Server via an INT-IP board.
2.1.4.5 Sets
The following sets can operate with the OmniPCX Enterprise:
• Analog sets: these sets are connected to the OmniPCX Enterprise through traditional analog lines.
• SO sets: these sets are connected to the OmniPCX Enterprise through SO digital lines.
• Mobile DECT/PWT sets: these mobile sets allow roaming and seamless mobility. They are
connected to the OmniPCX Enterprise through radio base stations (RBS or IBS).
• Mobile IP Touch WLAN sets: these mobile sets allow roaming and seamless mobility. They can
share the same wireless LAN with data terminals. They are connected to the OmniPCX Enterprise
through Access Points (radio base station), OmniAccess Wireless switches and SVP Server
(gatekeeper). The IP network allows communications between these devices.
• H.323: compliant H.323 terminals can be connected to the OmniPCX Enterprise through the IP
network.
• SIP terminals: SIP terminals benefit from a wide range of the PCX features, with access to almost
as many services as those available on dedicated sets.
2.1.4.6 Adapters
Adapters are interfaces allowing the following equipment to be connected to the OmniPCX Enterprise:
• Asynchronous terminals
• Synchronous terminals
• SO terminals
• Analog terminals (fax and modem)
2.1.4.7 External Applications

An external application is an application that works closely with the Call Server. Not all external
applications are available in all the configurations described: The ALE International offer on page 33.
2.1.4.7.1 Voice Mail
The 4645 voice mail system is available on the OmniPCX Enterprise. These voice mail systems also
offer the automated attendant and ubiquity features.
The 4645 voice mail system can be installed on the same processor as the Call Server, or run on a
dedicated machine.
Voice mail systems from other manufacturers can be used. In this case, connection with the OmniPCX
Enterprise is via analog lines and the VPS protocol.
2.1.4.7.2 OmniPCX Enterprise Management Tools
The OmniPCX Enterprise can be managed using:
• A generic tool such as mgr: based on character-mode screens that allow basic system
management to be performed
• The OmniVista 8770: running on a dedicated PC, this application is particularly useful when a PCX
network must be managed
With both methods, access to management can be protected against malicious intrusions. Several
mechanisms (notably SSH and HTTPS protocols) are used to ensure protection.

Server overview
2.1.4.7.3 OmniTouch Unified Communication

OmniTouch Unified Communication is a unified communication applications suite that groups, in its full
version:
• My Phone
• My Messaging
• My Assistant
• My Teamwork
2.1.4.7.4 LDAP Directory Server
This server is used by the Dial by name feature as an external database.
2.1.5 The ALE International offer

ALE International offers the following configurations:
2.1.5.1 Based on Common Hardware (OmniPCX Media Gateway)

The following figure presents an example of such a configuration.
Call Server on a
CS board or
Appliance Server
IP Network IP Network
WAN
OmniPCX OmniPCX
Media Gateway
OmniPCX Media Gateway
Media Gateway
OmniPCX
Media Gateway
OmniPCX
Media
OmniPCXGateway ACT
Media Gateway Auxiliary ACT Media Gateway
Media Gateway
2.1.5.2 Based on Crystal Hardware and CPU Board


Server overview
WAN
Main ACT
OmniPCX
+ CPU - ACT
Media Gateway
(Call Server)
Remote ACT ACT

Media Gateway
Remote ACT
Public Remote ACT

Network
Remote ACT
2.1.5.3 Based on Crystal Hardware and Appliance Server

Call Server on
Appliance Server
WAN
ACT Media
Gateway OmniPCX
Media Gateway
Remote ACT
Remote ACT
ACT
Public Network Media Gateway
Remote ACT
ALE International offers a large capacity feature for Appliance Servers. Call Server equipment capacity
is measured in terms of equipment number. The system configuration module automatically assigns at
least one equipment number to each device when configuring it on the Call Server. The large capacity
feature increases the maximum number of equipment numbers from 32,000 to 100,000. The
equipment capacity maximum value includes all types of equipment. For more information on the
maximum capacity for specific types of equipment, see the OmniPCX Enterprise Provisioning Levels.
Notes on compatibility of large capacity nodes:
If one node in a network is configured in large capacity, all nodes in the network must be at Release 8.0
or above.

Server overview
A network configured in large capacity can be connected, via ABC–F trunk groups, to other networks,
even if these networks are at a release prior to 8.0 or not configured in large capacity.
For installations using the application Open Telephony Server or Genesys T-Server, if one node is
configured in large capacity, all applications connecting to this node must be upgraded to versions
which recognize the large capacity feature. Software for other customer-specific applications may need
to be upgraded when moving to large capacity.
2.1.6 Software Overview

2.1.6.1 Call Server
The Call Server software is loaded on the hard drive at system installation. This software is unique for
all configurations. Licenses and locks allow certain features to be allowed or barred according to the
options purchased. The main functions handled by the Call Server are:
• Call handling, telephone call processing
• Internal applications, Accounting, Hotel-Hospital, Call Center, etc.
• DHCP server, download server, gatekeeper
2.1.6.2 Media Gateway

The Media Gateway software is downloaded from the Call Server at initial installation. This software is
stored in flash memories. At subsequent startups, there is no download, unless upgrade is required.
The IP address of the Media Gateway can be manually or automatically assigned using a DHCP
server. The Call Server may be used as DHCP server.
2.1.6.3 Digital Sets

The software of some digital sets is downloaded from the Call Server at initial installation. This software
is stored in flash memories. At subsequent startups, there is no download unless upgrade is required.
2.1.7 Security
2.1.7.1 Security against Intruders
At initial installation, the installer is required to define the security policy and to modify the default
passwords.
The PCX accesses are protected by:
• Passwords: a 8 characters minimum password is required at login. As of R6.2, the passwords have
a limited live time.
• Accesses to PCX web applications are encrypted using the https (secured http) protocol.
• Remote shell can be protected and encrypted using the SSH (secured shell) protocol
• Remote access to the PCX can be limited to the declared trusted hosts
2.1.7.2 Security against Eavesdropper

IP communications with IP Touch sets and Media Gateways can be encrypted and authenticated.
Signaling links and voice links can be secured according to conditions.
The IP Touch set binary allows this security feature. Media Gateways can be secured with an external
module called the IP Touch Security module (with such a module, both signaling and voice flows are
encrypted) or with a secured binary (in this case, only signaling flows are encrypted).

Chapter
3 Compliance with standards
3.1 Overview
Essential Requirements
Directive
Directive 2014/53/EU Standard/Directive Title
2014/53/EU
Harmonized Standards
Product standard to demonstrate

the compliance of mobile phones
with the basic restrictions related
CENELEC-EN 50360
to human exposure to electro-
magnetic fields (300 MHz - 3
Radiation exposure (SAR)
GHz)
for DECT, Bluetooth,
VoWLAN Terminals
Council Recommendation of 12
July 1999 on the limitation of ex-
Directive 1999/19/EC posure of the general public to
electromagnetic fields (0 Hz to
300 GHz)
Product standard to demonstrate

the compliance of radio base
stations and fixed terminal sta-
tions for wireless telecommuni-
CENELEC-EN 50385
cation systems with the basic re-
strictions related to human expo-
Radiation exposure (SAR)
3.1 (a) Safe- sure to electromagnetic fields
for DECT, Bluetooth &
ty (300 MHz - 3 GHz)
WLAN Bases
Council Recommendation of 12
July 1999 on the limitation of ex-
Directive 1999/19/EC posure of the general public to
electromagnetic fields (0 Hz to
300 GHz)
IEC-60950 CENELEC- Safety of information technology

EN 60950 equipment
Directive 2014/35/EU of the Eu-

ropean Parliament and of the
Council of 26 February 2014 on
Electrical Safety
the harmonization of the laws of
Low Voltage Directive
the Member States relating to
2014/35/EU
the making available on the
market of electrical equipment
designed for use within certain
voltage limits

Chapter 3 Compliance with standards
Directive
2014/53/EU
IEC-CISPR 22 CENE- Information Technology Equip-

LEC-EN55022 Class B ment- Radio disturbance charac-
Radio Disturbance
teristics Limits and methods of
CISPR 32 - EN 55032 measurement (class B)
Information Technology Equip-

IEC-CISPR 24 CENE- ment- Immunity characteristics
Immunity
LEC-EN55024 Limits and methods of measure-
ment
Directive 2014/30/EU of the Eu-

ropean Parliament and of the
Council of 26 February 2014 on
EMC 2014/30/EU
the harmonization of the laws of
the Member States relating to
electromagnetic compatibility
Electromagnetic compatibility
Harmonic current IEC-EN 61000-3-2 (EMC) Part 3.2: Limits for har-
monic current emissions
Limits – Limitation of voltage

changes, voltage fluctuations
and flicker in public low-voltage
Flicker IEC-EN 61000-3-3
supply systems, for equipment
with rated current ≤16 A per
phase and
and Radio Spectrum Matters
EMC for DECT ETSI-EN 301 489-06 (ERM): EMC for Radio Equip-
ment: Part 6 Specific conditions
for DECT Equipment
(ERM): EMC for Radio Equip-
EMC for 2.4 GHz (Blue-
ETSI-EN 301 489-17 ment: Part 17 Specific conditions
tooth)
for 2.4 GHz wideband transmis-
sion systems and 5 GHz high
performance RLAN equipment
(ERM): EMC for Radio Equip-
EMC for 2.4 GHz & 5 GHz
ETSI-EN 301 489-17 ment: Part 17 Specific conditions
(WLAN)
for 2.4 GHz wideband transmis-
sion systems and 5 GHz high
performance RLAN equipment

Directive
2014/53/EU
(ERM): Wideband Transmission
systems: Data transmission
equipment operating in the 2.4
2.4 GHz ISM (Bluetooth) ETSI-EN 300 328-2
GHz ISM band and using spread
spectrum modulation techniques;
Part 2: Harmonized EN covering
essential requirements under ar-
ticle 3.2 of the R&TTE Directive
(ERM): Wideband Transmission
systems: Data transmission
3.2 Spec- equipment operating in the 2.4
2.4 GHz ISM (VoWLAN) ETSI-EN 300 328-2
trum GHz ISM band and using spread
spectrum modulation techniques;
Part 2: Harmonized EN covering
essential requirements under ar-
ticle 3.2 of the R&TTE Directive
5 GHz (WLAN) ETSI-EN 301 893 (ERM):Broadband Radio Access
Networks (BRAN); 5 GHz high
performance RLAN
DECT: Harmonized EN for DECT

covering essential requirements
DECT ETSI-EN 301 406
under article 3.2 of the R&TTE
Directive: Generic radio
Essential Require-
ments Directive Directive
Standard Title
94/9/EC Harmonized 94/9/EC
Standards
Electrical apparatus for explo-

sive gas atmospheres — Part 0:
EN 60079-0
General requirements (IEC
60079-0:2004 (Modified))
"Ex" DECT Handset
Explosive atmospheres — Part
11: Equipment protection by in-
EN 60079-11
trinsic safety ""i"" (IEC
60079-11:2006)

DIRECTIVE 2003/10/EC OF
THE EUROPEAN PARLIA-
MENT AND OF THE COUNCIL
Essential Require- of 6 February 2003 on the min-
Directive
ments Directive imum health and safety re-
2003/10/EC
2003/10/EC quirements regarding the ex-
posure of workers to the risks
arising from physical agents
(noise)
DIRECTIVE 2011/65/EU OF
Essential Require- Directive MENT AND OF THE COUNCIL
ments Directive 2011/65/EU of 8 June 2011 on the restric-
2011/65/EU (ROHS) tion of the use of certain haz-
ardous substances in electri-
cal and electronic equipment
DIRECTIVE 2012/19/EU OF
Essential Require- Directive
MENT AND OF THE COUNCIL
ments Directive 2012/19/EU
of 4 July 2012 on waste elec-
2012/19/EU (WEEE)
trical and electronic equip-
ment (WEEE)
Environmental Speci- Environmental Stand-

Product State Title
fications ard
Environmental conditions and

environmental tests for Telecom-
munications equipment Part 1-1:
ETSI
Classification of environmental
Storage ETS 300 019 Part 1-1 Conditions: Storage
class 1.2
Class 1.2: Weather protected,
not temperature- controlled stor-
age locations

ETSI environmental tests for Telecom-
Transportation ETS 300 019 Part 1-2 Classification of environmental
class 2.3 Conditions: Transportation Class
2.3: Public Transportation

Environmental Speci- Environmental Stand-

Product State Title
fications ard

environmental tests for Telecom-
ETSI Classification of environmental
Conditions:
Usage ETS 300 019 Part 1-3
class 3.2 Stationary use at weather pro-
tected locations
Class 3.2: Partly temperature-
controlled locations
ETSI Equipment Engineering (EE);

Noise gener-
Acoustic noise emitted by tele-
ated ETS 300 753 communications equipment
EN 60529
IP 20 for basic racks
without specific cabinet
protection
IP 20 for 8 & 9 series
sets
IP Classifica- Degrees of Protection provided
tion IP 44 for 300 & 400 by enclosures (IP Code)
DECT sets
IP 53 for 310 & 610
WLAN sets
IP 44 for Alcatel-Lucent
OmniTouch 8118/8128
WLAN Handsets
Interface Specifica-
Interface Standard Title
tions ETSI Standards
A Guide to the Application of

ETSI-EG 201 121
TBR21
Attachment Requirements for

ETSI-TBR21 Connection to the Analogue
PSTN (Analog) PSTN
ETSI Standards Harmonized basic attachment

requirements for Terminals for
ETSI ES 203 021
connection to analogue interfa-
ces of the Telephone Networks
DECT: General Terminal Attach-

DECT ETSI-TBR10 ment Requirements: Telephony
Applications

tions ETSI Standards
DECT: Generic Access Profile

ETSI-TBR22
(GAP) applications
ISDN: Attachment Requirements

ETSI-TBR3 for Connection to an ISDN Basic
Access

ETSI-TBR33 packet mode TE to connect to a
Basic Access
PSTN (ISDN)
ETSI-TBR34 packet mode TE to connect to a
Primary Access

ETSI-TBR4 for Connection to an ISDN Pri-
mary Access
ISDN: Telephony 3.1 KHz tele-

service; attachment require-
ETSI-TBR8 ments for Handset
Terminals
Public Switched Telephone Net-

Digital Sets work (PSTN); Attachment re-
quirements for a terminal equip-
ment incorporating an analogue
ETSI-TBR38
handset function capable of sup-
porting the justified case service
when connected to the analogue
interface of the PSTN in Europe
tions Operator stand- Interface Standard Title
ards
PSTN (Analog, Interface Standards e.g: STI (Spécifications Techni-

Network Operator ISDN) ques d'Interfaces for France Tel-
published by the EC
standards ecom); Belgacom Specifica-
IP Interface Network Operators
tions...

VoIP Interface Specifi-

cations
Packet-Based Multimedia Com-

VoIP LAN (H323) LAN ITU-T H323
munications Systems
VoIP LAN (SIP) LAN IETF-SIP Session Initiation Protocol
Operator Interfaces Interface Standard Title
Resistibility of telecommunica-
Protection against Inter- tion equipment installed in cus-
Telecom ITU-T K21
ference tomer premises to over- voltages
and overcurrents

Chapter
4 Communication Server duplication
4.1 Overview
4.1.1 Overview
The Com Server Duplication service is used to improve system operating reliability. This service is
based on the use of two Com Servers. One Com Server is active: it plays the "main" role. The other is
in standby. When the main Com Server fails, the standby Com Server takes over and becomes the
main Com Server.
The standby Com Server is continuously updated. It is ready to take over the "main" role at any time.
This service is available for Com Servers located on CPU boards (Crystal Hardware), CS boards
(Common Hardware) or Appliance Servers.
4.2 Basic description

4.2.1 Principle
Whatever the platform used (Appliance Server, CS board, or CPU board), the services provided by the
Com Server duplication are the same:
• Duplication data update on standby Com Server
• Detection of main Com Server loss and switchover
Using a duplicated Com Server also allows maintenance of one Com Server to be performed. Static or
dynamic software upgrade patches can be installed without interrupting the telephone service.
4.2.2 Duplication on Common Hardware and Appliance Server

On both platforms, the Com Servers are connected via the IP network. The two Com Servers can be
either on the same IP subnetwork or on different IP subnetworks (as of R6.1).
On Common Hardware, the two Com Servers are hosted on CS boards and must be placed in different
racks.
Com Server A Com Server B
(Appliance Server) (Appliance Server)
Main Stby
IP Subnetwork A IP Subnetwork B
Router A Router B
IP Network
Figure 4.1: Com Servers Hosted on Appliance Server and Placed on Different IP Subnetworks
During normal operation :

• When the main Com Server data is updated, data is transmitted to the standby Com Server via the
Ethernet link.

Chapter 4 Communication Server duplication
• A "keep alive" dialog (see note) is established between the main and standby Com Server. The
interruption of this dialog informs the standby Com Server that the main Com Server is down. The
standby Com Server then becomes main.
Note:
A “keep alive” dialog is used to ensure mutual monitoring between two Com Servers. Messages are constantly
being sent back and forth between the two machines. Each exchange is monitored by a timer. A Com Server
detects the interruption of its "twin" when the monitoring time-outs elapse. The surviving Com Server thereby
determines the actions to be implemented. It should be noted that this method does not allow a problem on a
Com Server to be distinguished from a problem with the network.

(Appliance Server) (Appliance Server)
Main Stby
IP Subnetwork A IP Subnetwork B
Updating and
«Keep alive» Dialog
Router A Router B
IP Network
Figure 4.2: Updating and “keep alive” Dialog between both Com Servers
4.2.3 Duplication on Crystal Hardware

On Crystal Hardware, the two Com Servers are hosted on CPU boards and must be placed in the
same Crystal shelf.
Main Com Server Standby Com Server
14-Slot Crystal Shelf
IP Subnetwork
Router IP Network
Figure 4.3: Com Servers Hosted on CPU boards, Placed in a 14–Slot Crystal Shelf
During normal operation :

• When the main Com Server data is updated, data is transmitted to the standby Com Server via the
C1 link (on the back panel). Duplication data (and signaling) can be transmitted via Ethernet to limit
traffic on the C1 link, only with a CPU7-2 board (as of R6.2) and a CPU8 board (as of R12.1). A new
option in the Com Server configuration tool allows to select the transmission link for duplication data
exchange (Ethernet or C1 link). See: Selecting Link Type for Duplication Data Transfer on page 61.

Note:
The standby Com Server resets when the Ethernet link is interrupted between both Com Servers. When it
restarts and the Ethernet link is out, the standby Com Server resets again after it has checked its role.
• The standby Com Server monitors the clock signals from the main Com Server. A loss of clock
signals indicates that the main has shut down. The standby Com Server then becomes main.
First case :
Monitoring and Updating
On C1 Link
IP Subnetwork
Second case :
Monitoring
on C1 Link
IP Subnetwork Updating
on Ethernet Link
Figure 4.4: Monitoring and Updating between both Com Servers
4.2.4 Restrictions
e-reflexes sets do not operate in a duplicated Com Server configuration where the two Com Servers
are on different IP subnetworks.
As of R6.1, a hybrid logical link with signaling over IP cannot be set up between an R6.0 node (or
lower) and a node operating in a duplicated Com Server configuration with the two Com Servers on
different IP subnetworks.
4.3 Detailed description

4.3.1 Start up
At start up, a Com Server runs a test to check that its twin is present. On Common Hardware and
Appliance Server, it sends a message via IP. On Crystal Hardware, it runs a test to check that the
clocks are present. There are several possible cases:
• No twin Com Server is present: the Com Server is alone, and takes the main role.

Caution:
If the Com Server is not able to reach the reference Media Gateway (rack not connected or reference
Media Gateway not declared), the Com Server will suspect there is a "double main" (see "Double Main"
Special Case (Common Hardware and Appliance Server only) on page 47 for definition of "double
main").
Since the reference Media Gateway cannot be reached, management is blocked. In this case, the
manager can force management (see Forcing Configuration on page 61). This forcing command
should only be performed after checking that the second Com Server is indeed shut down.
• A twin Com Server is present, it has the "main" role: the Com Server becomes the standby Com
Server.
• The twin Com Server is also searching for its twin: both Com Servers appear simultaneously on the
network and each Com Server selects its role:
• On Common Hardware and Appliance Server, the Com Server declared in the Preferred CS
@IP (redundancy) parameter takes the main role (see Configuring the Preferred Main Com
Server on page 60). If this parameter is not filled in, the Com Server with the highest IP address
takes the main role.
• On Crystal Hardware, the Com Server that started first takes the main role and provides the
clock.
4.3.2 Data duplication

The main Com Server establishes an IP link with the standby Com Server, all Media Gateways, and all
IP phones on the IP network.
Redundancy messages are exchanged between the main and standby Com Servers, so that when a
standby Com Server is in service, its database is updated in real time. The following data is duplicated
on the standby Com Server:
• MAO (telephonic database)
• Traffic observation
• Accounting records
• CCD data
• LINUX data managed by swinst
Note:
LINUX data managed by netadmin are not duplicated (manual update is required).
• Mini message system (MMS) messages
• Information from neighboring nodes (via the broadcast mechanism)
• ACTIS files
4.3.3 Database consistency

The standby Com Server database is updated in real time, any modification made to the main Com
Server database is immediately replicated on the standby Com Server. The standby Com Server can
take control of the system at any time.
4.3.3.1 Database consistency ensured by a cloning operation

Up to R9.0, when the standby Com Server is unreachable, any configuration management done on the
main Com Server is lost on the standby Com Server. When the IP link is reestablished between the two
Com Servers, the Com Server that was isolated reboots and becomes the standby. Duplication
becomes operational again.
Before restarting the telephone application on the standby Com Server, the two databases must be
made consistent with a database cloning operation (see: Ensuring Database Consistency by a Cloning
Operation on page 62).

4.3.3.2 Database consistency automatically ensured for a limited period of time

As of R9.1, when the standby Com Server is unreachable, the main Com Server can store the history
of MAO commands (used to update its database). MAO is the process for the configuration of the
database of a Com Server.
The main Com Server stores MAO commands for a limited period of time (120 minutes maximum).
This storage duration can be configured (see: Configuring the Storage Duration Limit on page 62). If
the storage duration is set to 0, MAO commands are not stored when the standby Com Server is
unreachable.
When the standby Com Server is unreachable, two situations can occur according to storage duration:
• If the standby Com Server becomes operational before the expiration of the storage duration, the
main Com Server sends MAO commands to the standby Com Server. The standby Com Server
updates its database and the main Com Server stops storing MAO commands. As a result, the two
databases become consistent.
MAO commands are sent to the standby Com Server before telephony updates (in service, out of
service, in communication, etc.). When data are updated on the standby Com Server, the database
of the main Com Server can be modified.
Note:
As the main Com Server starts the telephone update after it has sent MAO commands to the standby Com
Server, updating the standby Com Server takes some time.
• If the standby Com Server is still unreachable after the expiration of the storage duration, the main
Com Server stops storing MAO commands. MAO commands already stored are deleted and an
incident (440) is triggered.
When the standby Com Server becomes reachable, the two databases must be made consistent
via a database cloning operation (see: Ensuring Database Consistency by a Cloning Operation on
page 62).
Information handled by MAO commands is:
• Agent login/logout (Alcatel-Lucent OmniTouch Contact Center - Standard Edition)
• Configuration of set parameters (secret code, language, user name, keys, etc.). This applies to
digital and cordless sets
• Set status (in or out of service)
• Interphony service
• Hotel/Hospital application
• Configuration of attendant parameters (and attendant groups)
• Configuration of entity parameters
• Configuration of Call Distribution Tables (CDT)
Notes:
• Information on the storage of MAO commands is saved in a log file iplink.log (see: Command on page
67).
• The main Com Server does not store MAO commands in standalone mode.
• This feature is only available for Com Servers located on CS-2/CS-3 boards (Common Hardware), Appliance
Servers and Blade Centers.
4.3.4 "Double Main" Special Case (Common Hardware and Appliance Server only)
The "keep alive" dialog may be interrupted because of a network problem, as shown in the figure
below:

Main Main
IP Network
Router 1 Router 2
Reference Media Gateway 2 Media Gateway 3

Media Gateway 1
Figure 4.5: IP Network Failure
The Call Severs can no longer dialog, however each one of them can access certain Media Gateways.
Each Com Server assumes it is alone and they both take the main role.
Calls can be made from each of the Media Gateways (according to the capabilities of the failed IP
network).
A Media Gateway called “reference Media Gateway” can be configured (see: Configuring the
Reference Media Gateway on page 61). This machine has no specific features except that it can be
used to resolve conflicts generated by this particular setup.
Management commands can only be performed on the Com Server that can reach the reference
Media Gateway. This restriction avoids update conflicts on return to a normal situation. Forcing can be
performed to escape blocked situations. Accounting records are lost on the Com Server that cannot
reach the reference Media Gateway.
On return to normal (the “keep alive” dialog is re-established) a negotiation takes place between the
Com Servers to define the role of each Com Server.
The selection of the main Com Server follows the process:
1. If a reference Media Gateway is configured, the Com Server that has reached the reference Media
Gateway remains main.
2. If no reference Media Gateway is configured, the polling of the main Com Server applies to the
preferred Com Server's IP address (see: Configuring the Preferred Main Com Server on page 60).
The Com Server declared as preferred Com Server remains main.
3. If no reference Media Gateway and preferred Com Server's IP address are configured, the Com
Server with the highest number of links to the GD (or INTIP-B) board remains main.
4. When both Com Servers have the same number of links, the Com Server with the highest IP
address is main.
The other Com Server and its related devices (boards, IP phones, etc.) reset. The calls managed by
this Com Server are interrupted. After reset, the duplication feature is on. As of R9.1, two situations can
occur when this Com Server resets:
• If any MAO command is not sent to this Com Server before its reset, the MAO commands stored in
the main Com Server are not deleted. After reset, the Com Server takes the standby role and

updates its database with the MAO commands sent by the main Com Server. For more information,
see: Database consistency automatically ensured for a limited period of time on page 47
• If MAO commands are sent to this Com Server before its reset, MAO commands stored on the two
Com Servers are deleted and an alarm (439) is triggered. After reset, a manual update of the two
Com Server is requested (see: Ensuring Database Consistency by a Cloning Operation on page
62)
4.3.5 Role Addressing

The role addressing is used when connection requests are sent to the system by applications (ex:
OmniVista 4760), IP phones or for link set up (ex: hybrid logical link with signaling over IP). The
connection requests are sent to the main IP addresses of the main and standby Com Server. Only the
main Com Server responds to its main IP address.
Each Com Server has two IP addresses:
• A local IP address: this is the physical address of the Com Server
• A main IP address: the Com Server only responds to this address when it plays the "main" role
When the two Com Servers are on the same IP subnetwork, a same main IP address can be used for
the two Com Servers. As of R6.1, when the two Com Servers are on different IP subnetworks, each
one is identified by its own main IP address.
4.4 Switchover
A switchover will occur when:
• On Common Hardware and Appliance Server, when the main Com Server activity is interrupted, for
example due to a power failure or network problem, and the main Com Server shuts down. The
"keep alive" dialog between Com Servers is interrupted and the standby Com Server stops
receiving messages from the main Com Server. After a delay, the standby Com Server switches to
main.
Note:
The delay can be checked in system administration but its value must not be modified.
Note:
When the "keep alive" dialog is interrupted because of a network problem, there may be a "double main"
situation.
• On Crystal Hardware when there is an interruption in the clock signal transmitted by the main Com
Server. This interruption informs the standby Com Server that it must switch to main.
• A Com Server that is deliberately shut down for maintenance (shutdown or bascul command)
sends a “Release” message to the standby Com Server. The standby Com Server immediately
takes over the role of main.
Note:
A shutdown on the standby Com Server does not generate a switchover.
During a switchover, the former standby Com Server becomes the main Com Server without restarting.
It must establish an IP link with all IP devices.
In releases previous to Release 8.0, the telephone application sends a message to the switchover
application for every IP device configured on the Com Server. Starting with Release 8.0, the switchover
application continuously maintains the IP addresses of all IP devices. When a switchover occurs, the
telephone application sends only one message to the switchover application to start the
reestablishment of the IP links.
System behaviors during a switchover:

• Internal Calls established are maintained.

• Calls set up on standard logical links (T2 type links) are maintained
• As of R10.1, calls set up on hybrid logical links can be maintained, depending on the type of hybrid
link and configuration: see Communications on hybrid logical links on page 50
• External calls in progress (all types of signaling: analog, T0, T2, ABC, PCM, etc.) are maintained.
• Calls currently being set up are released.
• Calls established with attendants, automated attendant, IVR, voice mail, nomadic are released. If
external calls are involved, the calls are redistributed.
• A three-party conference becomes a simple communication between the conference initiator and
the party who was not in conversation before the conference. The third party is released
• External calls that are on-hold are transferred to the attendants.
• Internal and network calls on-hold are released.
• No accounting records are lost
• On Crystal Hardware, direct links on V24 ports are maintained ("wired or''). On Common Hardware
and Appliance Server with Moxa boxes, V24 connections are lost and reestablished after a timeout
period
• New calls cannot be set up until the X25 routes have been recalculated. This operation takes about
30 seconds
4.4.1 Communications on hybrid logical links

As of R10.1, in certain conditions (see Conditions on page 50), communications on hybrid logical links
can be maintained after a Com Server switchover.
However, while the hybrid link is down for the users involved in communications on this hybrid link,
actions are "frozen". In other words the voice communication is maintained, but most telephone
features and actions are unavailable: see Frozen state on page 53.
When the hybrid link is reestablished, users come back to a standard state where all telephone
features and actions are available again.
4.4.1.1 Conditions
A communication on a hybrid logical link is maintained after Com Server switchover, provided that the
following conditions are met:
• The node on which the Com Server switchover occurs must be R10.1 or higher and the Hybrid
Link Switchover system option must be enabled on this node
• The node linked by a hybrid link to the node on which the switchover occurs must be R10.1 or
higher and the Hybrid Link Switchover system option must be enabled on this node
• End nodes (nodes where the users or trunks involved in the communication are) must be R10.1 or
higher and the Hybrid Link Switchover system option must be enabled on these node
• The Phone Features COS of the concerned users must allow Hybrid link comm. saved if
switchover
• The communication is not in QSIG-GF
• The hybrid logical link complies to the conditions detailed: Hybrid logical links for which
communications are maintained on page 51
• Terminals involved in communications are of any of the following types:
• TDM, IP, DECT, analog sets
• Remote extensions
• SIP extensions
• DECT sets operating with IP DECT base stations
• Hotel sets
• Public trunks

4.4.1.2 Hybrid logical links for which communications are maintained

The hybrid logical link for which communications can be maintained after a switchover are:
• Hybrid logical links with one of the following signaling types (on main and/or on standby access):
• IP signaling
• B channel signaling
• D channel signaling
• Hybrid logical links without signaling and pointing on an access with one of the following signaling
types:
• IP signaling
• B channel signaling
• D channel signaling
• Hybrid logical links In permanent establishment mode (leased but not switched)
Note:
Communications are maintained in the same way:
• Whether established on main access or standby access at the time of switchover
• When a VPN overflow (H.323, ISDN or analog) is used
The following tables show examples of hybrid logical links for which communications are maintained
during a switchover:
• The first two tables show a hybrid logical link with several accesses
• The third table shows three hybrid logical links towards three different nodes, each one containing
only one access
table 4.1: First example of hybrid logical link with several accesses
Hybrid link with several accesses

Signal establishment: permanent
Access number 1 2 3
Signaling type IP Without signaling Without signaling
Sig provider access no. for main 1 1

access
Has standby signaling No No No
table 4.2: Second example of hybrid logical link with several accesses

Signal establishment: permanent
Access number 1 2 3
Signaling type IP D channel IP
1 for more information on standby signaling channel, see Document [6] Private Networks, section Backup
Signaling in Hybrid Logical links - Detailed description

Has standby signaling Yes Yes No
Standby signaling type B channel IP
table 4.3: Example of three hybrid logical links with only one access
Hybrid link First hybrid link Second hybrid link Third hybrid link
Signal establishment:
permanent
Access number 1 1 1
Signaling type IP B channel D channel
Has standby signaling No No Yes
Standby signaling type IP
4.4.1.3 Hybrid logical links for which communications are released

The hybrid logical link for which communications cannot be maintained after a switchover include:
• Hybrid logical links with one of the following signaling types on one of the accesses (main or
standby)
• QSIG-GF
• X25
• Hybrid local links
The following tables show examples of hybrid logical links for which communications are released after
a switchover:
table 4.4: Example of hybrid logical link with several accesses, where X25 and QSIG-GF signaling
types are used

Signal establishment: on demand
Access number 1 2 3 4
Signaling type IP B channel QSIG-GF B channel
Has standby sig- No No No Yes

naling
Standby signaling X25

type

table 4.5: Example of hybrid logical link with several accesses, where X25 signaling type is used

Signal establishment: on demand
Access number 1 2 3
Signaling type IP B channel X25
Has standby signaling No Yes Yes
Standby signaling type IP Without signaling
Sig provider access no. 1

for standby access
4.4.1.4 Frozen state

While the hybrid logical link is down, communications which were using this hybrid logical link enter a
"frozen" state: voice communications are maintained and users can release communications, but the
range of available actions is very limited.
The situation comes back to normal when the hybrid logical link is back in operation on the new Main
Com Server (approximately between 40 s and 60 s).
If the hybrid logical link is not reestablished before the end of the "frozen state" timer (3 minutes by
default), the concerned communications are automatically released.
The following table shows:
• The list of handsets and trunk groups which can enter into the "frozen state"
• The available and unavailable actions on handsets
• The actions of remote parties which are accepted and refused

Terminal type Available actions Unavailable actions Actions accep- Actions not ac-
on handsets on handsets ted from remote cepted from re-
party mote party
Sets Hanging up Consultation call, Call release Evolution of the

DTMF transmission, call
Audio operations:
transfer, conference,
• Switching record, holding the
between call, retrieving it from
handsfree and hold, malicious call
handset trace…
• Activating/ On the end node, call
deactivating waiting consultation
mute call , retrieving a call
• Adjusting the on hold, supervised
level of call consultation
loudspeaker
Pressing the re-
lease key
SIP extension Hanging up Evolution of the call BYE Evolution of the

call3
Pressing the re-
lease key
SIP device BYE Evolution of the

call3
SIP trunk (ABC or BYE Evolution of the

ISDN) call3
ISDN trunk Call release

H323 trunk Advice of charge
DASS2 trunk
DPNSS trunk Call release

Advice of
charge4
Analog trunk Call release

Advice of
charge4
A "frozen" set cannot be reached and is seen out of service. When supervised, it is seen busy.
A set trying to reach a "frozen" set displays out of service.
2 All the keys appear available as they would in a normal situation. When pressing one key, an Alcatel
Reflexes or Alcatel-Lucent 8/9 serieshandset indicates that the service is not available.
3 RE-INVITE, REFER, UPDATE, INFO are rejected with 403 Forbidden.
4 Advice of charge is taken into account for accounting but is not displayed on the set.

When a user tries to do an action which is not available on a "frozen" set, this "frozen" set displays non
available service.
4.5 Installation procedure

4.5.1 Common Hardware and Appliance Server
The two Com Servers must:
• Be able to reach each Media Gateway and each IP-Phone via IP.
• Be implemented on identical platforms (Appliance Server or CS Board).
• Have the same software version.
To ensure maximum reliability, the installation technician must take care:
• Not to install the two CS boards in the same cabinet, or even in the same cabinet as a Media
gateway (reliability in relation to the power supply).
• Not to install a CS board in an expansion cabinet (reliability in relation to the power supply).
• When the two Com Servers are on the same IP subnetwork: do not separate the two Com Servers
by a non-secured inter-switch link (1) (reliability in relation to the network).
• When the two Com Servers are on the same IP subnetwork: use configuration (2) (as shown in the
following figure) whenever possible. This configuration allows "Double Main" cases to be avoided.
Com Server Com Server Com Server Com Server

LAN
Switch Switch LAN Switch
1 Mandatory Back-up Link 2
Figure 4.6: Com Servers Location
4.5.2 Crystal Hardware

4.5.2.1 Overview
The two Com Servers must:
• Be implemented on identical CPU boards.
• Have the same software version.
Com Servers duplication is possible in:
• M2, M3, and MI cabinets.
• In a 14-slot Crystal shelf, the master CPU is in position 6, the slave CPU is in position 10.
• In a 28-slot Crystal shelf, the master CPU is in position 20, the slave CPU is in position 6.
Note:
For information on connecting CPU boards, see M2 cabinet - Internal connections.
• WM1 cabinets. The master CPU is in position 1, the slave CPU is in position 7. Connection of the
CPU boards is identical to connection in M2/M3 cabinets. CBRMA or BRMA connection boxes are
used.
The VH cabinet is not compatible with CPU duplication.

4.5.2.2 Inter–Com Servers Communication

The clock signal monitoring between both Com Servers is performed on the internal C1 link.
According to Com Server configuration, the exchange of duplication data can be performed either on
the internal C1 link or on an Ethernet link. The Ethernet link may be set up as:
• The embedded Ethernet link.
In this configuration, one, and only one Com Server (main or standby) must be connected to an
external switch. The embedded Ethernet link connects the second Com Server.
Switch
Embedded Ethernet Link

between both Com Servers
Ethernet Link
to Com Server
(Main or Standby)
Note:
It is recommended to use the embedded link to perform exchange of duplication data (more secured).
• An external Ethernet link.
In this configuration, both Com Servers are connected to the same external switch. The embedded
Ethernet link must be deactivated between both Com Servers (to avoid loop of frames).
Switch
Embedded Ethernet Link

Deactivated
Ethernet Link
to Com Server Standby
Ethernet Link
to Com Server Main
The deactivation of the embedded Ethernet function is obtained by jumpers setting on the CPU
boards as shown below:

CPU Board Jumper Position for For more information

deactivation
CPU5 step 3 XB01
(adding a
jumper)
CPU6 X900
CPU7-2 XF03 See section CPU7-2, Hardware configuration in

Document [16] Crystal Hardware System Boards
4.5.2.3 Communication with Applications via V24

Connection to a V24 port is by "wired or" to the “C” or “D” CPU ports. The peripheral is simultaneously
connected to the V24 ports of both CPUs. Only the link with the active CPU is effectively used. On
switchover from the active CPU to the second CPU, the other V24 link becomes effective.
Bus B Bus B
CPU IO2 CPU IO2

Main Main Standby Standby
2 V24 (COM A and B) 2 V24 (COM A and B)

2 V24
COM C and D
Hard-wired OR
Figure 4.7: V24 Access in "Wired or" Mode in a Duplicated Configuration
Ports A and B are not in "wired or" mode. They are usually reserved for remote maintenance via
modem or for the system console.
4.6 Configuration procedure

4.6.1 Checking Software Lock
The 186 E–CS redundancy software lock (set to 1) is required to use Com Server duplication. If this
lock is not installed, the standby Com Server remains in “UNDEFINED” state and data cannot be
duplicated.
Viewing the lock set with the spadmin tool:

186 E-CS redundancy = True (1)
4.6.2 Configuring IP Addresses on Com Servers

4.6.2.1 Configuring the Twin Com Server
1. Run netadmin -m command
2. Select 4. 'CPU redundancy'
The following options are displayed:
• Option 1. 'View': to display the parameters of the twin Com Server with:
• On the first line: the name, IP address, and the subnetwork mask
• On the second line: the name and IP address used when the Com Server plays the "main"
role
Example:
Netmask : 255.255.255.0
===============================================================
| Machine type | Local interface | Name | Address |
===============================================================
| twin | Ethernet | xb000000 | 197.158.4.21 |
| local main | Ethernet | xmb000000 | 10.253.8.2 |
===============================================================
• Option 2. 'Add': to add a twin Com Server. The name, IP address and subnetwork mask are
requested.
When the twin Com Server and the local Com Server are on different IP subnetworks, a
message invites you to update default router(s), static routes, and trusted hosts. This message is
displayed after subnetwork mask address is entered.
• Option 3. 'Update': to modify the name and/or IP address of the twin Com Server. The new
name and address are requested.
When the twin Com Server and the local Com Server are on different IP subnetworks, a
message invites you to update default router(s), static routes, and trusted hosts. This message is
displayed after subnetwork mask address is entered.
• Option 4. 'Delete': to delete the twin Com Server. Confirmation is requested.
3. After twin Com Server configuration, select 0. 'Previous menu'
Note:
For more information about theses options, see: netadmin - Operation - CPU Redundancy.
4.6.2.2 Configuring Role IP Addresses

1. Run the netadmin -m command
2. Select '5. Role addressing'
The following options are displayed:
• Option 1. 'View': to display the main IP addresses of the local and twin Com Servers.
Example:
===============================================================
| Machine type | Local interface | Name | Address |
===============================================================
| local main | Ethernet | xma000000 | 197.158.4.22 |
| twin main | Ethernet | xmb000000 | 197.253.8.2 |
===============================================================
• Option 2. 'Add': to add the main IP addresses of the local and twin Com Servers. The names
and role IP addresses are requested.

• Option 3. 'Update': to modify the main IP addresses of the local and twin Com Servers.
• Option 4. 'Delete': to delete the main IP addresses of the local and twin Com Servers.
Confirmation is requested.
3. After Role Addressing configuration, select 0. 'Previous menu'
Caution:
After configuring role IP addresses for local and twin Com Servers, a full reboot must be performed to
apply changes.
Note:
For more information about theses options, see: netadmin - Operation - Role Addressing.
4.6.2.3 Configuring Routers IP Addresses

When the two Com Servers are on different IP subnetworks, you must define routers IP addresses for
the local and twin Com Servers. For more information, see: netadmin - Operation - Routing.
4.6.3 Configuration Parameters

4.6.3.1 Checking Duplication Parameters
4.6.3.1.1 Checking Window Size
1. Select IP > Duplication Parameters
2. Review/modify the following attribute:
System Option Select: Window Size.
Window Size Value of the acknowledgment window for inter-Com Server exchang-
es.
Check that the value is: 1 (default value).
Caution:
This value must not be modified.
3. Confirm your entry

4.6.3.1.2 Checking UDP Keep-alive
System Option Select: UDP Keep-alive.
UDP Keep-alive Duration of the "Keep Alive" frame monitoring timeout.

Check that the value is: 1s (default value).
Caution:

4.6.3.1.3 Checking UDP Lost

System Option Select: UDP Lost.
UDP Lost Delay for detection of link loss in reception (absence of traffic or
"keep Alive" dialog) in transmission (frame not acknowledged after
several attempts).
Caution:

4.6.3.1.4 Checking UDP Lost Reinit
System Option Select: UDP Lost Reinit.
UDP Lost Reinit Delay before the inter-Com Server dialog is declared interrupted.
Caution:

4.6.3.1.5 Checking MTU
System Option Select: MTU.
MTU Size of the frames for duplication information.

Check that the value is: 1024 (default value).E
Caution:
4.6.3.2 Configuring the Preferred Main Com Server

The preferred Com Server's IP address is used to define the main Com Server in the following cases:
• When the keep-alive dialog is reestablished between two main Com Servers ("double main" case)
and no reference Media Gateway is specified (see: Configuring the Reference Media Gateway on
page 61)
• When both Com Servers appear simultaneously on the network, the Com Server specified here
becomes main. If this parameter is not configured, the Com Server with the highest IP address
becomes main.
1. Select IP
Preferred CS @IP (redun- Enter the preferred Com Server's IP address

dancy)

4.6.4 Selecting Link Type for Duplication Data Transfer

This operation allows to select the link type (C1 or Ethernet) for duplication data transfer towards the
standby Com Server.
1. Select Shelf
2. Select Shelf N°0 with the Review/Modify menu
Signaling Mode Select:

• Ethernet if the Ethernet link is used.
Caution:
If IP redundancy is also implemented, do not forget to configure the
IP redundancy timers accordingly. The IP redundancy timers and
Com Server duplication timers must be configured so that if there is
an inter-Com Server dialog interruption, switchover is performed by
IP redundancy. For IP redundancy timer, see: IP redundancy -
Configuration procedure - Timer Management.
• N64 (or another value) if the C1 link must be used.
N64: default value.
5. If configuration changes, reboot the standby Com Server
6. Run the swinst tool or the mastercopy command on the standby Com Server for data cloning
(see Ensuring Database Consistency by a Cloning Operation on page 62).
4.6.5 Configuring the Reference Media Gateway

In each PCX, one (and only one) reference Media Gateway must be specified to resolve "double main"
cases.
1. Select Media Gateway
Main Shelf Address Enter the number of the reference Media Gateway.
Reference Select: Yes

4.6.6 Forcing Configuration

1. Select IP

Redundancy State Displays duplication status:

• On: Com Server duplication is operational and management can
be performed from this Com Server. The broadcast messages
received are duplicated.
• Off: Duplication is not operational and management cannot be
performed from this Com Server.
The manager can force state to On and thus authorize management.
Before forcing configuration, the system administrator must ensure
that his Com Server is unique. Different configurations on the two
Com Servers would generate inconsistencies that would be difficult to
resolve.
4.6.7 Ensuring Com Server Database Consistency

4.6.7.1 Configuring the Storage Duration Limit
System Option Select: Updates storage time limit.
Updates storage time Limited period of time (in minutes) during which the main Com Server
limit stores MAO commands (used to update its database) when the
standby Com Server is unreachable. If the storage duration is set to
0, MAO commands are not stored when the standby Com Server is
unreachable.
Default value: 120. This value is also the maximum value
4.6.7.2 Ensuring Database Consistency by a Cloning Operation

The swinst tool is used to render the Com Servers consistent. The menu is used to copy data from
the twin Com Server to the local Com Server (the Com Server from which the command is run). The
telephone must be stopped on the Com Server from which the cloning command is run.
Cloning can also be performed by running the mastercopy command.
Path: Swinst > 2 Expert menu > 3 Cloning & duplication operations > 1 CPU cloning
4.6.7.2.1 Cloning Linux Data
Duplication of Linux data to the standby Com Server.
The relevant data is:
• Data entered via the netadmin tool.
• Date and time information.
4.6.7.2.2 Cloning Databases
Duplication of the database, the relevant data is:
• Management data (data entered by mgr tool or OmniVista 4760).
• Accounting records.

• CCD data.
• Linux data (information entered by netadmin command).
• Traffic analysis data.
• Actis files.
• Voice guides.
Caution:
When a cloning operation is required, it must be performed with the telephone stopped on the Com Server
concerned.
4.6.7.2.3 Postponed Database Cloning
Delayed duplication of the database. Duplication operations may take some time and prevent
management. The Postponed cloning databases command is used to postpone the duplication
operation (to be performed at night, for example).
4.6.8 Installing a Pair of Duplicated Com Servers

1. Install the hardware for the two Com Servers in compliance with the recommendations given:
Installation procedure on page 55.
2. Install the appropriate software version (release) on both Com Servers.
3. Configure the IP addresses on both machines (netadmin command).
4. As a safety precaution, perform a Cloning databases operation to ensure the two databases are
consistent.
5. Start the telephone on both machines.
6. Perform management operations on the main Com Server. Data duplication is performed
automatically.
4.6.9 Adding a Standby Com Server

1. Install the duplicated Com Server hardware in compliance with the recommendations given:
Installation procedure on page 55.
The software version installed on this Com Server must be the same as that installed on the existing
Com Server.
2. Configure the IP addresses, if necessary (netadmin command and/or swinst: Cloning Linux
data).
3. Update the database (swinst tool: Cloning databases).
4. Start the telephone on the standby machine.
4.6.10 Upgrading with a Static or Dynamic Patch without Interrupting Service

The standby Com Server can be used to upgrade the software program. Proceed as follows:
1. Stop the telephone application on the standby Com Server.
2. Load the new software version onto this Com Server. A message informs the manager if the
software versions on the two Com Servers are different.
3. Restart this Com Server.
4. Update the databases (swinst tool: Cloning databases).
5. Restart the telephone on this Com Server.
6. Switch over the Com Server (bascul command).
7. Stop the phone on the second Com Server.
8. Load the new software version onto the second Com Server.
9. Restart this Com Server.
10.Update the databases (swinst tool: Cloning databases).

11.Restart the telephone on this Com Server.

Note:
Do not attempt to set a Com Server with a software version that is different to that of the main Com Server to
standby.
For example:
Com Server main 5.1.1 and Com Server Standby 5.1.1: OK
Com Server main 5.1.2 and Com Server Standby 5.1.1: NOK
4.6.11 Configuring hybrid link communication at switchover

Enabling the feature consist in:
• Enabling the feature for a node on page 64
• Enabling the feature for a user on page 64
4.6.11.1 Enabling the feature for a node

A system option allows to enable/disable the hybrid link communication saving when Com Server
switches over.
1. Select System > Other system Param.> System Parameters
Hybrid Link Switchover • True (default value): communications established on hybrid link
can be maintained after a Com Server switchover.
• false: communications established on hybrid link are released
after a Com Server switchover.
Note:
This system option must be configured in the same way on all nodes of the
network.
3. Confirm your entries
4.6.11.2 Enabling the feature for a user

1. Select Classes of Service > Phone Features COS
2. Review/modify the following attributes
Set features
Hybrid link comm. saved 1 (default value): a hybrid link communication in which the user is in-
if switchover volved can be maintained in case of switchover.
0: a hybrid link communication in which the user is involved is re-
leased in case of switchover.
4.6.11.3 Timers
1. Select System > Timers

Timer No. 374
Timer units Maximal duration of the freeze state. After this timer, if the hybrid log-
ical link has not been reestablished, communications in freeze state
are released.
Default value: 1800 (180 seconds).
Reserved for technical support
Timer No. 376
Timer units Delay after which messages are sent (freeze state/normal state) to
ensure both sides of the link are ready to send/receive messages.
Default value: 30 (3 seconds).
4.7 Maintenance
4.7.1 bascul Command
This command is used to force a change of status: main to standby or vice-versa. The main Com
Server reboots; the standby Com Server takes the main role.
Note:
Switchover is only possible if duplication is active.
4.7.2 twin Command

> twin
Usage : twin [Redundancy Cpu Enable (y/n)]
Role and CPU positions:
Role of the CPU : MAIN
CPU position : 06 (1)

CPU address : 132.169.4.52
Twin CPU position : 10
Twin CPU address : 132.169.5.54
Redundancy State:
Duplicated configuration : YES (2)
Wished sig. transfer mode : C1 signalling channel (3)
Used sig. transfer mode : C1 signalling channel
Transmission CPU-CPU : READY (4)
Telephony redundancy : READY (5)
monitel redundancy : READY (6)
memloader redundancy : READY (7)
All applications redundancy : READY (8)
The twin command displays the following information:

1. Status of the local Com Server: main or standby.

CPU position: position of the Com Server in the shelf. On Common Hardware, CPU positions are
virtual.
CPU address: Com Server IP address.
2. Configuration status reminder.
3. Irrelevant.
4. status of the inter-Com Server link: READY or KO.
5. Status of the telephone application: READY or not ready (KO) for switchover.
6. Information reserved for Technical Support.
4.7.3 role Command

This command is used to obtain the status (main/standby) of the Com Server on which the command is
run.
The command “role -b” is used to know whether the standby Com Server is standby. The twin
command gives a more accurate summary of duplication status.
4.7.4 Incidents on the Standby Com Server

When a fault is detected on a standby Com Server, it sends a main Com Server incident message that
is displayed with the letter “S'', this enables the user to differentiate such incidents from those
originating on the main Com Server "M''.
When a standby Com Server cannot process the MAO requests transmitted by a main Com Server
(this is the case when the databases are inconsistent), it signals this situation by transmitting an
incident to the main Com Server.
Incident messages are displayed as follows:
dd/mm/yy hh/mn/ss N M/S/I pc/ t/ eqt| =s: nini= name
Information text
Number of system message
Severity level
MG number/board number/-/equipment number

M: incident originating from Main Call Server
S: incident originating from Stand-by Call Server
i: incident originating from a Call Server
whose role is not yet established
N : nbr of the node generating the incident (six digits)
Hour of the system message (hh=hour, mn=minute, ss=second)
Date of system message (dd=day, mm=month, yy=year)
Figure 4.8: Com Server Incident Messages
When Com Server role is “UNDEFINED”, the incidents transmitted are stored on this Com Server.
When it switches to standby status, the incidents are sent to the main Com Server.

4.7.5 Log File Relating to the Storage of MAO Commands

A log file (iplink.log) provides information on the storage of MAO commands. The access path to
retrieve this log file is: /var/log/iplink.log.
Relevant information is:
Message Location Definition
Save MAO msg because Main Com Server The IP link between the two Com Servers is
Sdby CPU is not avail- broken. The database of the main Com Server
able has been modified. MAO messages are stor-
ed by the main Com Server, and sent to the
standby Com Server when it becomes availa-
ble again.
MAO is ON on the re- Main Com Server The main Com Server has received the
mote CPU MAO_IS_ON message from the standby Com
Server. As a result, the standby Com Server is
ready to process MAO messages stored by
the main Com Server
MAO is ON on the local Standby Com Server The standby Com Server has received the
CPU MAO_IS_ON_ACK message from the main
Com Server. As a result, the main Com Server
acknowledges that the standby Com Server is
ready to process MAO messages. The main
Com Server starts sending stored MAO mes-
sages.
Stop saving MAO msg Main Com Server The main Com Server has stopped storing
after X minutes MAO messages after X minutes, while the
standby Com Server was unreachable. All
stored MAO messages are deleted. A manual
update of the standby Com Server must be
performed
4.7.6 Incidents Relating to the Storage of MAO Commands

• Incident 439: This incident is triggered when the main Com Server deletes the history of MAO
commands, or when storage duration has expired, or in a "double main" case when the two Com
Servers have stored MAO commands. When incident 440 is triggered, a manual update of the
standby Com Server is necessary.
• Incident 440: on return to normal after a "double main" situation, a negotiation is started between
the two Com Servers. One of them remains main and the other one resets (standby Com Server). If
the standby Com Server resets before having stored MAO messages, incident 439 is triggered and
a manual update of the standby Com Server is necessary.

Chapter
5 Passive Communication Server

(PCS)
5.1 Overview
As of OmniPCX Enterprise Release 7.1, Passive Communication Servers provide continuity of
telephony services in case of:
• Loss of two duplicated Call Servers
• Loss of a non-duplicated Call Server
• Breakdown of IP links between remote sites and Call Servers

5.2.1 Topology
Passive Communication Servers are associated with IP domains. In a multi-IP domain configuration:
• One IP domain can be rescued by only one Passive Communication Server
• One Passive Communication Server can rescue several IP domains, including IP domains without a
Media Gateway
Main Call Stand-by

Server Call Server
2
IP 1
PCS1
IP
IP
PCS2
Media Gateway 1
Media Gateway 2
SIP External
Domain 3
Gateway
Domain 1
Domain 2
Figure 5.1: Example of a Passive Communication Server configuration

Chapter 5 Passive Communication Server (PCS)
In Figure 1, when IP link 1 is lost, Passive Communication Server 1 rescues domains 1 and 2. When IP
link 2 is lost, Passive Communication Server 2 rescues domain 3. When both Main and Stand-by Call
Servers fail, each Passive Communication Server rescues the associated domains.
Note:
Each Passive Communication Server must be configured to rescue at least one Media Gateway.
5.2.2 Passive Communication Server Capacities and Configuration

Passive Communication Servers have the following capacities and configuration options:
• Passive Communication Servers must be configured on nodes where the Call Server is either a
Common Hardware or an Appliance Server.
• Passive Communication Servers can be either a Common Hardware CS board, an Appliance
Server or a Blade Server.
A PCS must have a memory configuration (RAM) equal to or greater than a CS: If the CPUs of the
central site are Appliance Servers, all the PCS of Common Hardware type must have 256 Mo of
memory.
Note:
An Appliance Server can act as a PCS without restriction.
The Common Hardware CS-2 board can act as a PCS without restriction. This board is available as of R9.0.
The Common Hardware CS board can act as a PCS with restrictions. This board can rescue 1000 users and
20 Media Gateways maximum.
• If IP Touch security is used, the PCS needs an MSM box if it rescues more than 500 users.
• Passive Communication Servers can handle 1000 IP domains.
• Passive Communication Servers cannot be duplicated.
• Passive Communication Servers can operate in active mode for a maximum of 30 consecutive
days.
• Domains cannot be rescued by both backup signaling and a Passive Communication Server.
However, private to public overflow is possible transparently.
• There are no network metering tickets on a PCS
5.2.3 Passive Communication Server Services

Passive Communication Servers provide the following services:
• Rescue of Media Gateways, INTIPB, IOIP and IP Touch terminals (see Equipment Rescue on page
73)
Note:
As of R9.1, Passive Communication Servers can rescue Alcatel-Lucent IP Touch 310/610 WLAN Handsets and
Alcatel-Lucent OmniTouch 8118/8128 WLAN Handsets. The rescue process is similar to that of IP Touch sets.
• As of R9.1, rescue of SIP phones and SIP external gateways, provided they can handle two proxies
(primary and secondary). The PCS rescues a SIP external gateway, provided the PCS IP address is
configured on the PCX in SIP external gateway parameters (see SIP Trunking - Configuration
procedure - Configuring an External Gateway)
• Possible rescue of several domains, including domains with no Media Gateway. In that case, at
least one of the domains must include a Media Gateway
Note:
SIP phones and SIP external gateways situated in a domain with no Media Gateway cannot be rescued.
• Support for calls to domains with public access using private to public overflow (see Private to
public overflow between IP Media Gateways on a same node on page 75)
• Support for encrypted calls (see Encryption on page 83)

• Support for H.323 sets (if their Gateway address is the GD address connected to the Passive
Communication Server)
• Generation of accounting tickets (see Accounting on page 84)
5.2.4 Passive Communication Server Restrictions

An active Passive Communication Server offers the same functions as a Call Server with some
restrictions. Equipment rescued by an active PCS also works with some limitations:
• Terminals cannot access a 4645 voice mail system when they are rescued by an active PCS
• While database configuration is possible on active Passive Communication Servers, updates are
lost after the resynchronization with the Call Server which follows the signaling link reestablishment
• Alcatel-Lucent 8 series and Alcatel-Lucent 9 series sets, WLAN handsets, GD, GA, INT-IP boards
rescued by an active PCS cannot download binary from the PCS (no TFTP server on a PCS)
• Some configuration files relative to several functions are not copied on the PCS (see Data
consistency on page 71)
The following equipments and services are not supported:
• SIP fax servers
• SIP voice mails
• DHCP server
• e-RMA service
• IP link backup for the Media Gateway
• IP equipment backup before the udp-lost-reinit if the link with the PCS has been lost
• ABC-F network services

5.3.1 Start-up
5.3.1.1 Creating a signaling link between the PCS and the main Communication Server
A list of declared PCS addresses is created in the Communication Server. When a CPU starts:
• If the address of the CPU is in this list, the CPU starts as a Passive Communication Server
• If the address of the CPU is not in this list, the CPU starts as a Communication Server
When the PCS starts up, it establishes an IP signaling link with the main CPU of the Communication
Server.
For this signaling link, use a UDP protocol identical to the one used between the Communication
Server and the sets.
5.3.1.2 Operation
When a Passive Communication Server starts up, it establishes an IP signaling with the main CPU of
the Communication Server. This signaling link is used for communication between the Communication
Server and the Passive Communication Server:
• The Communication Server sends orders to the Passive Communication Server
• The Passive Communication Server informs the Communication Server about its status
The Passive Communication Server stores the physical IP addresses of the main Communication
Server and the stand-by Communication Server in its hosts file.

Communication Server Passive Communication Server

(Appliance server) (Appliance server)
IP subnetwork A Updating and IP subnetwork B

keep alive dialog
Router A Router B
IP network
Figure 5.2: Updating and “keep alive” dialog between Passive Communication Server and
A “keep alive” dialog is used to ensure mutual monitoring between Communication Servers and
Passive Communication Servers. Passive Communication Servers continuously send “keep alive”
messages to their associated Communication Servers. The Communication Servers reply to these
messages. Each exchange is monitored by a timer. A Communication Server or a Passive
Communication Server detects the interruption of the other server when the time-out for the monitoring
timers is exceeded. As a result, the Passive Communication Server determines the action to be taken.
The Passive Communication Server then becomes active.
Note:
This method does not enable Passive Communication Servers to distinguish between Communication Server and
network problems.
5.3.1.3 Data consistency

The PCS operates with:
• Data copied from the main Communication Server
• Local data entered manually by the manager
The pcscopy tool is used to copy data from the main CPU to PCS(s). This tool can be configured to
update automatically (weekly, daily) or manually.
This tool operates with a "not secured copy protocol" (rcp) or a "secured copy protocol" (scp).
For more information on manual updating with the pcscopy command, see pcscopy on page 91.
5.3.1.3.1 Data Copied by the pcscopy tool
The pcscopy tool copies the following information from the CPU:
• All database objects configured with the mgr tool:
The Passive Communication Server database is the exact copy of the associated database objects
of the Communication Server.
• Password files (/etc/passwd, /etc/shadow and /etc/login.defs)
• Radius server files (/etc/raddb/server, /etc/raddb/export, /etc/pam.d/system-
auth.NORADIUS, /etc/pam.d/system-auth.RADIUS and /etc/pam.d/system-auth)
• CCD statistics: when system option PCSCOPY without CCD statistics is set to False (select
System > Other system parameters > System parameters)
Note:
By default, the value of the system option is False

5.3.1.3.2 Data Not Copied by the pcscopy tool

Most data configured via swinst or netadmin are not copied by the pcscopy tool.
The hosts file is not copied on the PCS.
The configuration files relative to the following functions are not copied on the PCS:
• SSH configuration
• SSL configuration
• Apache server configuration
• Syslog server configuration
• SNMP configuration
• NTP configuration
• Radius users
• Date, time and time zone
• CCD statistics: when system option PCSCOPY without CCD statistics is set to True (select
System > Other system parameters > System parameters)
Note:
By default, the value of the system option is False
This data must be configured manually on each PCS using netadmin or swinst.
5.3.2 Loss of signaling link between Passive Communication Servers and

Communication Servers
5.3.2.1 Operation
When the signaling link between a Communication Server and a Passive Communication Server is
lost, the Passive Communication Server switches to active mode:
• An alarm is generated in the Communication Server and in the Passive Communication Server,
which indicates that the signaling link has been lost
• Another alarm is generated in the Passive Communication Server, specifying how much longer it
can remain in active mode
For detailed information on possible alarms, see Alarms on page 92.
5.3.2.2 Database
When a Passive Communication Server is in active mode, there is no update of the database from the
Communication Server to the Passive Communication Server.
Caution:
The Passive Communication Server database can be changed. However, when the signaling link between
the Communication Server and the Passive Communication Server is reestablished, these changes are not
copied to the Communication Server database and are lost.
5.3.2.3 Communication Server duplication

In a duplicated configuration, if a switching occurs while a PCS is in ACTIVE mode, this PCS will be
seen in undefined state (UNDEF) by the Communication Server which has switched to main role. The
PCS will be seen in INACTIVE state after IP connection between the PCS and the Communication
Server is established.

5.3.3 Equipment Rescue

5.3.3.1 Rescue process
If an IP link with a Communication Server is lost, the Passive Communication Server rescue process
varies according to the type of equipment to be rescued. Possible types of equipment include:
• GD
• INTIPB/IOIP boards
• IP Touch sets
• Alcatel-Lucent IP Touch 310/610 WLAN Handsets and Alcatel-Lucent OmniTouch 8118/8128 WLAN
Handsets
• SIP phones
• SIP external gateways
5.3.3.1.1 Rescue process for GD, INTIPB/IOIP boards, IP Touch sets and WLAN handsets
Equipment rescue proceeds as follows:
1. The device is in service (connected to the Main Communication Server)
2. The link between the device and the Main Communication Server is lost
3. After 7 seconds (the UDP Lost timer default value) the device realizes that the link is lost
Note:
the UDP Lost timer value can be configured in the IP Parameter Menu.
4. The device waits for 7 seconds (the UDP Lost Reinit timer default value) to ensure that the link is
down and that it is not a switch-over from the Main Communication Server to the Stand-by
Note:
the UDP Lost Reinit timer value can be configured in the IP Parameter Menu.
5. After 7 seconds, if the Communication Server is still not reachable:
In the case of… then…
a GD / GD-3 board the board launches software reset and uses the rescue IP address to
connect to the PCS. This address is entered statically in the GD / GD-3
(see Configuring the address of the Passive Communication Server in a
GD on page 87).
an INTIPB/IOIP board the board resets twice before using the rescue IP address to initialize.
This address is entered statically in the INTIPB/IOIP board (see Configur-
ing the address of the Passive Communication Server in the INTIP
boards on page 88).
an INT-IP3 board the board launches software reset and uses the rescue IP address to ini-
tialize. This address is entered statically in the INT-IP3 board (see Con-
(B type)
figuring the address of the Passive Communication Server in the INTIP
boards on page 88).

In the case of… then…
an IP Touch handset the IP Touch restarts, switches to survivability mode, and connects to the
Passive Communication Server using the rescue IP address sent by the
Communication Server at initialization.
Note:
As of R10.1, if the Keep RTP flow option is enabled, the set does not reset as
long as a communication is active: the set resets at the end of the
communication. See 8/9 Series (Common Features) - Additional configuration
operations - Phone COS for more information.
a WLAN handset theIP Touch WLAN handset restarts, switches to survivability mode, and
connects to the Passive Communication Server using the rescue IP ad-
dress sent by the Communication Server at initialization.
6. The Passive Communication Server receives the EVT_START message
7. The Passive Communication Server initializes the links with the device directly
Note:
The Passive Communication Server can rescue IP Touch sets belonging to a domain without a Media Gateway.
Note:
CCD agents are logged out at Communication Server switchover to PCS.
5.3.3.1.2 Rescue process for SIP phones
SIP phone rescue is as follows:
1. The SIP phone is in service (connected to the main Communication Server).
2. The PCS becomes active.
3. When the SIP phone sends a REGISTER or INVITE request to the main Communication Server,
two situations can occur:
a. The Main Communication Server receives the request (this case can occur when the IP Link
between the main Communication Server and PCS is down whereas the Main Communication
Server is still in service):
For a REGISTER request, the Main Communication Server sends error response 503 without
Retry-after header. This error response leads the SIP phone to send the REGISTER request to
the PCS (the SIP phone uses the Backup Server IP address).
For an INVITE request, the Main Communication Server sends error response 503 with Retry-
after header. The time in this Retry-after header is the expiry time of the SIP phone. After this
expiry time is over, the SIP phone restarts the registration process on the PCS.
b. Both main and stand-by Communication Servers are down or the Main Communication Server
does not receive the request due to loss of IP link: the SIP phone gets no response:
In this case, after registration has expired, the SIP phone sends the REGISTER request to the
PCS.
For the INVITE request, the SIP phone sends the INVITE request to the PCS once registered on
the PCS.
4. The Passive Communication Server receives and accepts the REGISTER or INVITE request, as
well as the following requests from the SIP phone.
5.3.3.1.3 Rescue process for SIP external gateways
SIP external gateway rescue is as follows:
1. The SIP external gateway is in service (connected to the main Communication Server)

2. Two situations can occur:

a. The IP Link between the main Communication Server and the PCS is down
The PCS is identified as ACTIVE by the Communication Server. The main Communication
Server does not send the REGISTER/OPTIONS request after the expiry time and the external
gateway is identified as out of service by the main Communication Server. From this moment on,
the main Communication Server does not allow any outgoing call to the external gateway.
The ACTIVE PCS which rescues the external gateway sends it the REGISTER/OPTIONS
request and puts the external gateway in service, as well as the associated trunk group. From
this moment on, all communications with the external gateway are handled by the PCS. On any
incoming call from the external gateway to the main Communication Server, the main
Communication Server replies with error response 503 with a retry-after header. The time in this
header is the Registration/Supervision expiry timer. For external gateways which are not
managed with a refresh timer, the main Communication Server replies with error response 503
without a retry-after header.
b. Both main and stand-by Communication Servers are down
The PCS becomes ACTIVE and sends the REGISTER/OPTIONS request for its own external
gateways. Incoming and outgoing calls are possible as usual from PCS.
5.3.3.2 Private to public overflow between IP Media Gateways on a same node

Private to public overflow can be used between Communication Servers and Passive Communication
Servers, or between two Passive Communication Servers.
When an IP Touch is in survivability mode, it can still reach an IP Touch belonging to another domain
through the PSTN network. This is only possible if these IP Touch domains belong to distinct Passive
Communication Servers (or Communication Servers).
Note:
A domain cannot be rescued by both backup signaling link and a Passive Communication Server.
Overflow table for N2

4202 => 155664202 Local # = 4202
Public # = 155664202
PSTN
PCS DDI TG
DDI TG
Bob
WAN N2
Marie
domain x
Figure 5.3: Private to Public Overflow
5.3.3.3 Examples
5.3.3.3.1 Single Backup Configuration
This configuration includes:
• A duplicated Communication Server in a central site
• A Passive Communication Server in a backup site

The three servers (Main Communication Server, Stand-by Communication Server and Passive
Communication Server) have the same role. The active server manages all of the network domains.
If both the Main Communication Server and the Stand-by Communication Server are down, or if the IP
link from the central site fails, the Passive Communication Server switches to active mode.
The Passive Communication Server acts as a backup Communication Server.
Central site
Backup site
Communication Communication
Server Server
main stand-by PCS
WAN
Domain 3
domain 1 domain 2
Figure 5.4: Single backup configuration
5.3.3.3.2 Multi-backup configuration

• A Passive Communication Server in each remote site
The role of the Main and Stand-by Communication Servers is to manage all of the network domains.
If both the Main Communication Server and the Stand-by Communication Server are down, or if the IP
links from the central site to the remote sites fail, each Passive Communication Server from each
domain switches to active mode and rescues its associated domain.

Central site
Server Server
main stand-by
WAN
PCS
PCS PCS
Domain 1
Domain 2 Domain 3
Figure 5.5: Multi-backup configuration
5.3.3.3.3 Multi-domain backup configuration

• A Passive Communication Server in domain 1
• A Passive Communication Server for domains 2 and 3
• No Media Gateway in domain 3
If both the main Communication Server and the stand-by Communication Server are down, each
Passive Communication Server switches to the active mode and rescues its associated domains,
including domain 3, which has no Media Gateway. In this example:
• Passive Communication Server 1 rescues domain 1
• Passive Communication Server 2 rescues domains 2 and 3

Central site
Server Server
main stand-by
WAN PCS2
PCS1
Domain 1 Domain 2 Domain 3
Figure 5.6: Multi-Domain backup configuration
5.3.4 Reestablishment of the signaling link

5.3.4.1 Reset of rescued devices
When the signaling link between a Passive Communication Server and the Communication Server is
reestablished, the Passive Communication Server stays active until it resets (this intermediate state is
called inactive *). During this time, all devices (IP phone and IP boards) belonging to the IP
telephony domains rescued by the PCS remain attached to this PCS.
After a delay, or at a configured time (see Configuring a Passive Communication Server on the
Communication Server on page 85), the Passive Communication Server resets and becomes passive
again. Resetting the Passive Communication Server resets all related devices (even if they are in
communication), these devices attach themselves back to the Communication Server.
When a Passive Communication Server is in the inactive * state, devices which start up or reset,
connect to the Passive Communication Server, even if the Communication Server is available. If, for
some reason, some devices belonging to IP telephony domains rescued by the PCS are attached to
the Communication Server, these devices can reset according to PCS expected reset time:
• The PCS is programmed to reset in less than two minutes (non-modifiable period of time), they do
not reset and remain attached to the Communication Server
• The PCS is programmed to reset in more than two minutes, they reset to attach themselves back to
the PCS
5.3.4.2 Process for each type of equipment

The following table shows how Passive Communication Servers behave for each type of rescued
equipment when the signaling link with the Communication Server is reestablished.

In the case of … The Passive Communication Server…
an IP Touch 1. Sends a RELEASE message to all the IP Touch sets

2. The IP Touch sets reset and connect to the Communication Server
Note:
As of R10.1, if the Keep RTP flow option is enabled, an IP Touch set does not reset
as long as a communication is active: the set resets at the end of the
communication. See 8/9 Series (Common Features) - Additional configuration
operations - Phone COS for more information.
a GD board 1. Sends a PCS_CPL_RESET_CPL message to the GD

2. The GD replies with a RELEASE message to the Passive Communication
Server
3. The GD connects to the Communication Server without resetting (software
reset only)
a GD-3 board 1. Sends a PCS_CPL_RESET_CPL message to the GD-3 board

2. The GD-3 board restarts (hard reset) and connects to the Communication
Server
an INTIPB/IOIP 1. Sends a PCS_CPL_RESET_CPL message to the INTIPB/IOIP stand-by

board and to the INTIPB/IOIP main
2. The INTIPB/IOIP main sends a RELEASE message to the Passive
3. The two boards (main and standby) reset (hard reset) and the first
operational board connects to the Communication Server
an INT-IP3 board 1. Sends a PCS_CPL_RESET_CPL message to the INT-IP3 stand-by and to

the INT-IP3 main
(B type)
2. The main INT-IP3 board sends a RELEASE message to the Passive
3. The two boards (main and standby) reset (hard reset) and the first
operational board connects to the Communication Server
Note:
There is no TFTP server on a PCS. That is why rescued IP equipment do not download binary files from the PCS.
When a rescued IP equipment resets and connects again to the Communication Server, the binary version is
checked and new binary is downloaded if necessary.
5.3.5 Passive Communication Server modes

The Passive Communication Server is in:
• Software protection violation mode, at first installation or when the 30 day countdown has been
reached
• Passive mode, when the Passive Communication Server and the Communication Server can
communicate
• Active mode, when the Passive Communication Server and the Communication Server cannot
communicate
• Inactive *mode, when in an intermediate state after the Active mode, when the PCS is back in
communication with the Communication Server (testing signaling link reestablishment stability),
before the timer (reset type) has expired (see Reset of rescued devices on page 78)
The Passive Communication Server is in one of these modes according to the following process:

1. Installation of the Passive Communication Server:

• The Passive Communication Server starts in software protection violation mode
2. The signaling link between the Passive Communication Server and the Communication Server is
established:
• The Passive Communication Server changes to passive mode
3. When the Passive Communication Server and the Communication Server cannot communicate
(see Loss of signaling link between Passive Communication Servers and Communication Servers
on page 72 and Equipment Rescue on page 73):
• The Passive Communication Server changes to active mode
• The 30 day countdown starts
4. The Passive Communication Server rescues its associated equipment within 30 days. Beyond 30
days this is no longer possible:
• If the signaling link between the Passive Communication Server and the Communication Server
is reestablished (see Reestablishment of the signaling link on page 78) before 30 days, the
countdown stops and the Passive Communication Server changes to passive mode
• If the 30 day countdown has been reached the Passive Communication Server changes to
software protection violation mode
5.3.6 Access to a SIP carrier

Incoming and outgoing calls to (or from) a SIP carrier are routed by the Communication Server or the
local PCS.
A trunk group leading to the SIP carrier and its associated SIP external gateway must be configured for
the Communication Server and each PCS.

Domain 0
Communication
server
Domain 1 Domain 2
PCS 1 PCS 2
IP local
TG1 TG0 TG2
Ext
Ext Gateway Ext
Gateway 0 Gateway
1 2
SIP Carrier 1
Figure 5.7: Configuration of SIP accesses for Communication Server and PCS
Before R11.1, each trunk group and each external gateway must be configured manually for the PCS.
As of R11.1, only the trunk group between the Communication Server and the SIP carrier must be
configured. The associated SIP external gateway's PCS IP Address must be configured using the
Global address option. When the .Global address option is used a trunk group and a SIP gateway
are automatically associated to each PCS as well as the Communication Server. This simplifies the
configuration procedure when many PCS are used.
5.3.6.1 Nominal (normal) mode

Links between the Communication Server and the PCS are in-service .The PCSs are in the inactive
state.
An incoming call is handled by the Communication Server, then directly routed to the called set
belonging to the domain, the local domain, or a remote domain.

Domain 0
Communication
server
CS-PCS1 Link
in-service
Domain 1
Domain 2
PCS 1 PCS 2
IP local
Called set
SIP Carrier 1
Calling set
Figure 5.8: Incoming call in normal mode
For outgoing calls, the Communication Server routes calls to the local trunk group.
5.3.6.2 Rescue mode

The links between the Communication Server and one or several PCS are out of service. These PCSs
are in the active state.

Domain 0
Communication
CS-PCS1 Link server
out-of-service
Domain 1
1 Domain 2
PCS 1 3
PCS 2
IP local
2
Called set
SIP Carrier 1
Calling set
Figure 5.9: Incoming call in rescue mode
Incoming calls are processed as follow:

1. The SIP carrier routes the incoming call to the Communication Server
2. The Communication Server rejects incoming calls with the response: 503 Service Unavailable
3. The SIP carrier reroutes calls to the appropriate PCS. The PCS routes the call to the called set.
Outgoing calls from sets associated to a PCS in service, are routed to the SIP carrier via the local trunk
group.
5.3.7 Services
5.3.7.1 Inhibiting connection of equipment
When a domain is attached to a Passive Communication Server in active mode, Communication
Servers block the connection of equipment from this domain.
5.3.7.2 Encryption
When encryption is used by the Communication Server, Passive Communication Servers can use
encryption, but it is not mandatory.
To provide encryption, Passive Communication Servers must be equipped with an MSM box.
If a Communication Server is equipped with a Server Security Module (SSM) box, the SSM box must
know the associated Passive Communication Server addresses.

At initialization, the encryption process is as follows:

1. Create the Passive Communication Server address as an address to be protected
2. Assign a Media Security Module (MSM) box to this address
If a Passive Communication Server is in active mode, its MSM box mode changes to safe mode. This
enables the IP Touch sets to start at negotiation phase 2 (and not phase 1, which would take more
time) when the system switches back to normal mode.
The links between boxes to encrypt signaling between Passive Communication Servers and Media
Gateways are automatically generated at configuration file emission from the Communication Server to
the SSM.
The SSM mode is in… when …
“Degraded active” mode there is a Passive Communication Server in active mode in the system.
This mode allows the SSM box to keep the inactive security links in
memory.
“active” mode there is no Passive Communication Server in active mode in the sys-
tem.
The BTlink process is deactivated for Passive Communication Servers (the SSM acts as master for the
MSMs). This process sends the BT_config file to the SSM box.
5.3.7.3 Accounting
Passive Communication Servers have the following accounting characteristics.
• The accounting tickets of Communication Servers are not copied to Passive Communication
Servers
• The tickets generated in Passive Communication Servers in active mode are not erased after
database update
• After the switchover from a Passive Communication Server to a Communication Server, the
accounting tickets and the traffic observation files generated on the Passive Communication Server
when it was in active mode are not copied to the Communication Server

5.4.1 Prerequisites
Before configuring a Passive Communication Server, check that:
• Lock 332 is greater than 0 in the license file in the Communication Server
• The software version of the Passive Communication Server is the same, or more recent than the
associated Communication Server
5.4.2 IP ports
Firewall configuration must abide by the following information:
1. The Communication Server connects to the PCS on TCP port 514
2. The PCS connects to the Communication Server on TCP ports 113, 1022 and 1020
3. Port 113 must be opened on the firewall
4. ICMP "ping" and "port unreachable" must be allowed in both directions

5. UDP port 32640 must be opened

6. TCP 1018 is used for connection from PCS to CS
5.4.3 Configuring a Passive Communication Server on the Communication Server

Whenever a copy of the database is made on the Communication Server, the installer can determine
the duration (in hours, default 4) of the validity of the database, to avoid interrupting the MAO and the
metering application. Each time a copy of the Communication Server database is programmed or
manually configured on the Passive Communication Server, the following occurs:
If… Then the Communication Server…
There is no MAO database in the /DHS3dyn/ 1. Interrupts the MAO and the metering
BACKUP/IMMED directory or if the validity duration application while it transfers the database into
has expired the /DHS3dyn/BACKUP/IMMED directory
2. Transfers the /DHS3dyn/BACKUP/IMMED
database into the specified Passive
The MAO database of /DHS3dyn/BACKUP/ Copies this database into the Passive Communi-
IMMED is valid. cation Server without interrupting the MAO and
the metering application
To configure a Passive Communication Server on a Communication Server:

1. Select Passive Com. Server
2. Review/modify the following attributes:
Automatic update type Defines when the Communication Server database is up-
dated in the Passive Communication Server.
Valid values:
• None (no update is required)
• Weekly
• Daily
Update day The day of the week, if the automatic update type is set to
Weekly.
Update time (hh:mm) The time of day (hh:mm), if the automatic update type is
set to Weekly or Daily.
Database validity (in h) Defines the duration validity (expressed in hours) of the
database copied on the PCS.
Default value: 4h

Reset type Select the reset type after a reestablishment of the signal-
ing link:
• Reset by default: the PCS and its related devices
reset 30 second after reestablishment of the signaling
link
• Time: the PCS and its related devices reset at a
specified time
• Timeout: the PCS and its related devices reset after a
specified delay
Reset time (hh:mm) This parameter is available when the Reset type parame-
ter is set to Time.
Enter the reset time using the hh:mm format.
Reset timeout (in s) This parameter is available when the Reset type parame-
ter is set to Timeout.
Enter the delay (in seconds) before reset (from 1 to
65535).
Note:
The 0 value means the Passive Communication Server does not
reset. The reset must be activated manually.

Note:
If you use pcscopy to manually synchronize again a Passive Communication Server, the database archive is
automatically rebuilt on the Communication Server (the MAO and the metering application are therefore
interrupted while the database archive is being rebuilt.)
5.4.4 Declaring the Passive Communication Server addresses on the

To declare the Passive Communication Server addresses associated with a Communication Server:
1. Select: Passive Com. Server > PCS Addresses
IP Address IP address of the Passive Communication Server
IP Netmask Netmask of the Passive Communication Server
Name Name of the Passive Communication Server
Update type Can be applied if the parameters of the Passive Communi-

cation Server are customized.
Update day
Update time
Reset type Can be applied if the parameters of the Passive Communi-

cation Server are customized.
Reset time (hh:mm)
Reset timeout (in s)

5.4.5 Configuring SIP external gateway for Communication Server and PCS
Only parameters associated to PCSs are presented in this section. For a complete configuration of SIP
accesses, see the IP-PCX documentation.
1. Select: SIP > SIP Ext Gateway
SIP External Gateway Enter gateway number
Gateway Name Enter a name for the gateway
PCS IP Address Enter the IP address of the PCS associated to this

SIP Ext Gateway:
• When a valid IP address is entered, the PCS with
this address is associated.
• When this parameter is empty, no PCS is
associated. This value is used when the external
gateway is associated with the communication
server.
• As of R11.1, when 255.255.225.255 is entered for
this parameter, all the PCS and CS are
associated to this gateway.
The value 255.255.255.255 is called the Global
address.
In addition, when the Global address is used, a
SIP trunk group and a SIP external gateway is
created automatically for each configured PCS.
5.4.6 Declaring the IP domain on the Communication Server

To declare the Passive Communication Server address used to rescue the IP domain:
1. Select IP > IP domain
Backup IP address IP address of the Passive Communication Server

5.4.7 Configuring the address of the Passive Communication Server in a GD

To configure the address of a Passive Communication Server in a GD:
1. Connect to the GD
2. Open the e-MGD IP configuration tool using the mgconfig command
3. In the e-MGD IP configuration menu:
• Select item 1, Startup mode, and set it to Static
• Select item 2, IP address, and enter the IP address of the GD
• Select item 5, CS role address, and enter the Communication Server role address
• Select item 12, Passive CS address, and enter the IP address of the Passive Communication
Server

4. Exit
5.4.8 Configuring the address of the Passive Communication Server in the INTIP
boards
To configure the address of the Passive Communication Server in the INTIP board, connect to the
INTIP board using V24 or the cpl_online tool:
1. To use the cpl_online tool, at the CS> prompt, type the command cpl_online followed by the
crystal number and the position of the coupler
Example:
CS> cpl_online 7 6
2. At the Config> prompt, type pcs to display the INTIP configuration menu
Example:
config>:pcs
3. At the Config PCS> prompt, type address to display the IP address
Example:
config PCS>:address
4. Enter the IP address of the Passive Communication Server
Example:
Config:192.40.56.11
5. To exit, type “q” until you reach the root menu, then type ctrl+D
5.4.9 Configuring the address of the Passive Communication Server on SIP

equipment
To configure the address of the Passive Communication Server in SIP phones, see SIP End Point
Level Of Service - Configuration procedure - Operations to Perform on SIP Sets.
To configure the address of the Passive Communication Server for SIP external gateway, see SIP
Trunking - Configuration procedure - Configuring an External Gateway.
5.4.10 PCS commissioning

5.4.10.1 Configuring private public overflow between IP Media Gateways
The Communication Server sees users who belong to an IP field rescued by a PCS as Out of
Service.
The rescuing PCS sees the users who belong to IP fields not rescued by the PCS as Out of
Service.
If you want users who belong to isolated IP fields to be able to communicate:
• Configure the private public overflow between IP Media Gateways.
• In the system parameters, enable overflow on Out of Service extension.
Select Installation / Autres param. Install. / Paramètres Système (FR)
Select System / Other System Param. / System Parameters (GEA)
And answer as follows:
Débordement sur poste Hors Service (FR) oui
Overflow on Oos extension (GEA) yes

5.4.10.2 PCS software download

• The software download procedure for a PCS is identical to that of a Communication Server.
• The software version of the Passive Communication Server must always be the same or more
recent than that of the Communication Server.
5.4.10.3 PCS system configuration

With the netadmin tool, configure IP data:
1. Declare the physical IP address of the PCS, the netmask, the default router.
2. Declare the physical and role addresses of the Communication Server in the hosts file of the
Passive Communication Server.
3. If needed configure other functions for which configuration files are not transfered from the CS at
resynchronization, see Data consistency on page 71.
With the swinst tool:
1. Create an empty database.
2. Enable the autostart mode.
3. Set date and time.
5.4.10.4 PCS database resynchronization

The PCS database must be identical to that of the Communication Server.
After creating an empty database and starting the telephone applications on the PCS, use the
pcscopy tool on the Communication Server to manually launch the synchronization of the PCS
database. At the end of the copy, the PCS starts automatically.
5.4.11 Recommendations for an operating PCS

• When updating the software, always update the Passive Communication Server software before the
• When installing a patch on the PCS, check that the update of the software version of the Passive
Communication Server does not take place during the resynchronization period of the databases. It
is essential to check this to prevent the Communication Server from rebooting the Passive
Communication Server once it has transfered the database, while it is still updating the software
version of the Passive Communication Server.
• The manual database copy must necessarily be done by the pcscopy tool (see pcscopy on page
91). The manual database copy must not be done by creating a Communication Server database
archive using swinst, then sending it and decompressing on the PCS. This is essential for the copy
to be complete.
Note:
Avoid programming daily backups using swinst on the Passive Communication Server while re-synchronization is
taking place on the Communication Server.
There is a risk of clash between the re-synchronization and any running backup. The re-synchronization might fail.
5.5 Maintenance
5.5.1 Traces
5.5.1.1 IPLINK
To display traces of the PCS link:

1. Activate the pcs field of the ipltrace tool by typing:

>ipltrace pcs=on
2. Use the traced tool to display traces
5.5.1.2 Call Handling

To activate TEL traces for the PCS:
1. Activate the sec_cpu field of the actdbg tool is used, with the filter in the neqt of the activated
fictitious INTIPA.
2. Launch the mtracer tool to display the traces
5.5.1.2.1 GD trace
Follow these 4 steps to get the appropriate trace in the GD:
1. Log on the GD.
From Call Server or Passive Communication Server do: telnet "GD_IP_Address", login : admin,
password : admin
2. Appropriate root rights
Type command: "su -"
3. Retrieve the log files from memory. This concerns the logs since the last reboot.
Type: "ll" command to read the files last modification date.
Type: "cd /var/log" to go in /var/log directory.
Retrieve the files in /var/log directory via FTP or read them and copy what you read in a backup file :
"messages", "mglog", "*monitor*".
Note:
"*monitor*" means all files which have "monitor" in their names. E. g.: "monitor.log" or "monitor2.log"
4. Retrieve the log files from flash. This concerns the logs before the last reboot.
Type: "ll" command to read the files last modification date.
Type: "cd /mnt/flash/info" to go in /mnt/flash/info directory.
Retrieve the files in /mnt/flash directory via FTP or read them and copy what you read in a backup
file : "messages_tail.log", "messages_head.log", "*monitor*".
Note:
"*monitor*" means all files which have "monitor" in their names. E. g.: "monitor.log" or "monitor2.log"
5.5.1.3 MAO
To display mao traces:
1. Activate the obj and the swk traces by typing
>mao trace +obj +swk
2. Use the traced tool to display the traces
5.5.1.4 pcscopy
To display pcscopy traces:
1. Activate the pcscopy traces by typing:
>pcscopy +tr
2. Use the traced tool to display the traces

5.5.2 Maintenance Tools

Use … to…
domstat display the domains that are secured by Passive Communication Servers:
• The IP address and the state of each Passive Communication Server are displayed.
For more information see domstat - Operation.
pcsview display information on the Passive Communication Server(s):

• name
• IP address
• state
• reset type
• attached domains
• secured domains
pcscopy manually update the Passive Communication Server database with the Call Server da-
tabase.
This tool also enables you to consult the log of the copy operations.
Note:
With the Config 0 command, the following Passive Communication Server information are also displayed:
• name
• IP address
• state
5.5.2.1 pcsview
+------------------------+------------------+-------------------+---------------
PCS Name | Address | State | Reset Type
|------------------------|------------------|-------------------|---------------
| PcsNancy | 10.3.16.1 | INACTIVE | Default (30s)
| PcsMetz | 10.4.16.1 | ACTIVE | Default (30s)
| PcsSiltzheim | 10.5.16.1 | UNDEF | Default (30s)
+------------------------+------------------+-------------------+---------------
Possible states of a PCS are:

• INACTIVE: the signaling link between the PCS and the Call Server is up and the PCS is in inactive
state.
• ACTIVE: the signaling link between the PCS and the Call Server is down and the PCS should be in
active state.
• INACTIVE *: the signaling link between the PCS and the Call Server is reestablished but the PCS is
still in active state (the PCS will reboot at expiration time).
• UNDEF: the signaling link between the PCS and the Call Server has never been established. The
PCS is not in the capacity to switch to active state.
5.5.2.2 pcscopy
The pcscopy command offers two options:
Pcscopy

1 - PCS update
2 - PCS log file
0 - Exit
Choice [0 - 2] :
• PCS update : this option is used to synchronize a PCS. Enter the IP address of the PCS to
synchronize. pcscopy checks that the PCS is reachable and that its software release is consistent
with the Call Server release, then sends an archive of the Call Server database to the PCS. If the
transfer fails, the reason for failure is displayed.
• PCS log file: this option is used to view the log.pcs file content. The log.pcs file contains the
result of the last synchronizations (up to 1000 synchronizations/ 2000 lines).
Note:
The result of the previous synchronizations is contained in the oldlog.pcs file. The log.pcs and
oldlog.pcs files are located in the /usr4/mao directory (also accessible via /DHS3dyn/mao).
Only log.pcs can be viewed by pcscopy.
Example:
2006/03/23 13:43:52 - PCS 192.40.64.27 Update => Start
2006/03/23 13:47:09 - PCS 192.40.64.27 Update => End OK
2006/03/23 14:05:51 - PCS 192.40.64.27 Update => Start
2006/03/23 14:05:52 - PCS 192.40.64.27 Update => End NOK: Bad PCS soft. release
Note:
If you use pcscopy to manually synchronize again a Passive Communication Server, the database archive is
automatically rebuilt on the Communication Server (the MAO and the metering application are therefore
interrupted while the database archive is being rebuilt.)
5.5.3 Alarms
The alarms that are diffused on the Call Server are mapped to an object on the Passive
Communication Server within the 4760 topology.

Alarm Gravity Alarm descrip- Event Type Cause Object

number tion
Alarm 402 Alarm 402 is is-

sued on the PCS
when the GD/
INTIPB of a do-
main not secured
by the PCS tries
to connect to this
PCS.
Alarms 427 Warning These alarms in- ProcessingErrorAlarm Unknown PCS

and 428 dicate loss or es- (427)/
tablishment of Node
contact between (428)
the Passive Com-
munication Server
and Call Server.
Alarm 427 is re-
ported on the
Passive Commu-
nication Server
and alarm 428 is
reported on the
Call Server.
Alarm 429 Major Alarm 429 is re- ProcessingErrorAlarm TransmitFailure PCS

ported on the Call
Server when the
signaling link is
lost and the Pas-
sive Communica-
tion Server re-
mains active.
Alarm 430 Clear Alarm 430 is re- ProcessingErrorAlarm TransmitFailure PCS

ported on the Call
Server when the
signaling link is
reestablished and
the Passive Com-
munication Server
is inactive.


number tion
Alarm 431 Warning Alarm 431 is re- ProcessingErrorAlarm Unknown Node

ported on the
Passive Commu-
nication Server to
indicate the
amount of time
left in which the
Passive Commu-
nication Server
can operate in ac-
tive mode. This
alarm is reported
when the link is
lost between the
Passive Commu-
nication Server
and the Call Serv-
er. It is then repor-
ted at regular in-
tervals to the Pas-
sive Call Server.
Alarm 432 Major Alarm 432 is re- ProcessingErrorAlarm Unknown Node

ported on the
Passive Commu-
nication Server to
indicate that the
Passive Commu-
nication Server
has expired and
switched to soft-
ware protection vi-
olation mode.


number tion
Alarm 433 Minor Alarm 433 is re- ProcessingErrorAlarm Unknown PCS

ported on the Call
Server to indicate
that the copying of
the database on
the Passive Com-
munication Server
has failed. This
alarm contains the
IP address of the
Passive Commu-
nication Server
and the cause of
the failure. For ex-
ample, the failure
may be because
the version of the
software is earlier
than that of the
Call Server, be-
cause the Passive
Communication
Server cannot be
reached, or be-
cause of some
other reason.
Alarm 434 Minor Alarm 434 is re- ProcessingErrorAlarm Unknown Node

ported on the
PCS to indicate
that a device that
does not belong
to a domain res-
cued by the PCS
is trying to con-
nect to the PCS
Note:
If a MOXA box is declared on the Call Server, the following alarm is reported on the PCS at PCS startup:
2:1462=V24:48: chanel configuration, operation 1, error 5
Ignore this alarm.
Note:
Incidents 429 and 430 are correlated.

Chapter
6 Topology
6.1 Introduction
This module describes the different possible topologies on an OmniPCX Enterprise node as from R5.1.
A node is composed of a Communication Server controlling one or more Media Gateways. The Media
Gateways provide interfaces with sets and external networks.
Each node is structured between a main area and remote areas. The main area contains a Media
Gateway "close to" the Communication Server. This supports links to other network nodes.
Remote areas may be connected to the main area via the WAN (remote IP area with an ACT or
OmniPCX Media Gateway) or via the public network (RT2 connection).
There are three possible supports for the Communication Server:
• A Crystal Hardware CPU board in an M2, M3, WM1 or VH cabinet : the Communication Server is
then called IPCS (IP Crystal Server). The CPU8 board is not supported on WM1 or VH cabinet
• A Common Hardware CPU board in an S or L rack : the Communication Server is then called IPRS
(IP Rack Server).
• An Appliance Server (external PC) : the Communication Server is then called IPAS (IP Appliance
Server).
There are two types of Media Gateway hardware:
• S and L racks for OmniPCX Media Gateways.
• M2, M3, WM1 or VH cabinets for ACT Media Gateways.
Whatever the hardware used, the services offered are the same. However, e-RMA and A4645 voice
mail are not available on CPU boards. Some features are only available on ACT format boards (see
below).
The topologies possible depend on the hardware used in the main area and are described in the
following paragraphs:
1. The hardware in the main area is based on S and L racks: The Communication Server can then be
on a CS board installed in an S or L rack, or on an Appliance Server,
2. The hardware in the main area is based on an ACT: The Communication Server can be on a CPU
installed in an ACT, or on an Appliance Server.
6.2 Main area based on an OmniPCX Media Gateway

6.2.1 Architecture
The Communication Server is on an Appliance Server or on a CS board in an S or L rack.
Architecture is as follows:
• Main area: OmniPCX Media Gateway (1 to 3 S or L racks) + (possibly) an ACT Media Gateway with
a limited selection of boards.
• Remote areas:
• OmniPCX Media Gateway on IP.
• ACT Media Gateway on IP.

Chapter 6 Topology
Remote IP area with Remote IP area with

ACT Media Gateway OmniPCX Media Gateway
INT-
IP B
MEX MEX
GD
WAN
LAN
INT-
GD IP B
Call Server
ACT
MEX
Appliance Server or
MEX
CS board
Main area
Figure 6.1: Example configuration with an OmniPCX Media Gateway in the main area
6.2.2 ACT in the main area

The role of the ACT installed in the main area is to host boards that are not available in S or L rack
format:
• Public network access: DDI-D, AT-Q23, AT-R2, DID-USA.
• Analog boards: PCM2, ACEM, EMTL, BLTL-D, LDTL4, LDTL8, E&M-4TL-USA.
• DECT / applications / data: DECT8, GPA, VPM35, SPA3, VPU5 (4635H), CMP.
It also allows supplementary services to the services available on an OmniPCX Media Gateway to be
provided:
• DECT (PWT) capacity to be increased by adding DECT8 boards.
• A voice mail service with a large number of mail boxes (4635H).

Chapter 6 Topology
6.3 Main area based on an ACT Media Gateway

Architecture differs depending on the Communication Server support:
• The Communication Server is on an CPU7-2 or CPU8 board: there may be 3 ACT levels, i.e. a
peripheral ACT can be connected to another peripheral ACT, in turn, connected to the main ACT
(hosting the CPU).
• The Communication Server is on an Appliance Server: There can only be 2 ACT levels.
6.3.1 Communication Server on a CPU board

• Main area: Main ACT (hosting the CPU) + peripheral ACT connected via INTOF link, on 3 levels
maximum.
• Remote areas:
• Remote wired area: Peripheral ACT on RT2 (this ACT can be directly connected to the main
ACT or to a peripheral ACT with INTOF.

Chapter 6 Topology

INT-
IP B
MEX MEX
Remote wired area
GD RT2 Lvl. 3
B
RT2 link
WAN
Public network
LAN
Lvl. 1 INTOF
CPU B
INTOF Lvl. 2
B
INTOF Lvl. 2
B INTOF
B
Lvl. 3
Lvl. 2
Main area
Figure 6.2: Example configuration with CPU board on ACT
Note:
• Only controller boards are shown in the figure.
• The main ACT must also contain an INT-IP A board to ensure the links with the remote IP areas.
• For each INTOF B (or RT2 B) board, there is a matching INTOF A (or RT2 A) board on the upper level ACT.
6.3.2 Communication Server on Appliance Server

• Main area: Main ACT + peripheral ACT on INTOF.
• Remote areas:
• Remote wired area: Peripheral ACT on RT2 directly connected to the main ACT.

Chapter 6 Topology

INT-
IP B
MEX MEX
Remote wired area
GD
RT2
B
Lvl.2
RT2 link
WAN
Public network
IOIP
Lvl.1
INT-
Internet Server platform IP A
INTOF
B
Appliance Server
INTOF
B
Lvl.2
INTOF Lvl.2 INTOF links

B
Main area
Figure 6.3: Example configuration with Appliance Server and ACT main area
Note:
• In this configuration, the level 3 ACT is prohibited.
• The main ACT is controlled by an IOIP board (4x64 kbps signaling function). As this board has no
compressors, an INT-IP A board is required to ensure IP communication with the other remote areas.
• For each INTOF B (or RT2 B) board, there is a matching INTOF A (or RT2 A) board on the main ACT.
6.4 Commissioning Media Gateways

Main ACT (with Crystal Hardware : Operational as soon as the CPU is put into service.
CPU)
ACT Media Gateway on IP : See the Commissioning on page 139.

Chapter 6 Topology
OmniPCX Media Gateway on IP : See the Commissioning on page 106.
Peripheral ACT on INTOF or RT2 : See Overview on page 152.
Remote ACT on LIO :

Chapter
7 Resource allocation in an IP
distributed architecture

7.1.1 Introduction
This document outlines how resources (voice guides, compressors, Music on Hold, etc.) are allocated
in an IP distributed architecture including remote sites with an IP Media Gateway and remote sites
without an IP Media Gateway (only equipped with IP Touch sets).
7.1.2 Example of IP Distributed Architecture

The explanation on resource allocation below is based on the following IP distributed architecture:
E F
North of Com Server
the (main) 4645 VMS
Country
IP Domain 2
Public
Network
G Main Site
H IPMG 1 B
A
IPMG 3
IP Domain 3 WAN IP Domain 0
I J IP Domain 1
C
IP Domain 4 IPMG 2 D
K L South of
the
Country Secondary Site
IP Domain 5
Com Server
(Standby)
Figure 7.1: Example of IP Distributed Architecture
Figure 1 represents an OmniPCX Enterprise configuration spread out on several geographical sites,
with the following main characteristics:
• Com Server duplication, with one Com Server located in the main site and the other Com. Server in
the secondary site
• Intra-site communications are not compressed (G.711 is used).

Chapter 7 Resource allocation in an IP distributed architecture
• Inter-site communications are compressed using G.729. Each site is configured with a different IP
domain (all the extra IP domain communications are compressed).
• The sites are distributed across the whole country. The main site is located in the north of the
country and the secondary site in the south. It will be explained later why this geographical detail is
mentioned.
7.1.3 Resource Allocation Description

7.1.3.1 Voice Guide Resource Allocation
The general principle of resource allocation is the same whatever the resources: compressors, voice
guides, music on hold...
When the Call Handling application needs a resource, for instance a voice guide resource, a list is
dynamically created. This list details, at the very moment when the request is made, all the IP Media
Gateway having available resources. IP Media Gateways are always listed in the same order.
If, at the moment of the request, all the IP Media Gateways (IPMGs) can provide voice guides, the list
is IPMG1, IPMG2, and IPMG3 but if, for example, all the voice guides supported by IPMG2 are used,
the list is reduced to IPMG1 IPMG3.
When a set needs a voice guide, the OmniPCX Enterprise selects in priority the voice guides:
• In the same IP Media Gateway if the set is a TDM set: see: Example 1 below
• In the same IP domain if the set is an IP Touch set: see: Example 3 below
Examples:
Based on the configuration described: Figure 1
• Example 1: Set C needs to be connected to a voice guide
Set C is a TDM set connected to IPMG 2. A voice guide is searched in priority in IPMG2. If no voice guide is
found, the search continues in the order provided by the resource list. A free voice guide is searched in priority
in IPMG1 because IMPG1 is the first choice in the list. If no voice guide is found, the search continues in the
next IPMG of the list (IPMG3).
• Example 2: Set D needs to be connected to a voice guide
Set D is an IP Touch set belonging to the same IP domain as IPMG2. The search process is exactly the same
as for set C in Example 1 above
• Example 3: Set E or Set I need to be connected to a voice guide
Set E is an IP Touch belonging to an IP domain without IP Media Gateway able to provide voice guides.
Search starts directly by using the list: in priority in IPMG1, then IPMG2, .…
Note:
The list used for voice guides search, or any other type of resource, is unique, so the search process is the same
whatever the location of the set. Set I is located in the south of the country but a voice guide is selected in priority
in IPMG1 and not in IPMG2 despite the fact that IPMG2 is geographically nearer than IPMG1
7.1.3.2 Compressor Allocation

Compressor allocation is identical to voice guide allocation. A specific list is created at the moment of
the request for compressor resources.
Example: Set D (see Figure 1) makes an outgoing communication
Accesses to the public network are centralized on IPMG1. When an IP Touch set makes an outgoing
call, the device needing a compressor is not the set but the trunk, so the compressor is selected in the
same IP domain as the trunk, in this case: IPMG1
Note:
If the TDM trunk group is replaced by a SIP trunk group, an outgoing call made by an IP Touch set does not need
the use of a compressor, because the set uses direct RTP.

7.1.3.3 Music on Hold Selection

The allocation process is the same as with voice guides, with the difference that it is possible to use the
Music On Hold (MOH) per entity feature.
For instance, in the system configuration all the sites located in the north belong to entity 1 and all the
sites located in the south belong to entity 2.
The MOH located in IPMG1 and IPMG3 are associated by configuration to entity 1 and the MOH
located in the IPMG 2 is associated to entity 2.
With this feature, it is possible for user J (see Figure 1), who belongs to entity 2, to listen to the MOH of
IPMG2, when put on hold.
7.1.3.4 Three Party Conference Circuit Allocation

A three party conference with participants using IP Touch sets requires compressors. Therefore
available compressors and conference circuit are allocated in priority in the IPMGs belonging to the
same IP domain.
7.1.3.5 Resource Allocation for Alcatel-Lucent 4645 Voice Mail System Access
Alcatel-Lucent 4645 Voice Mail System (VMS) uses the IP network to carry the voice flows. Voice flow
coding is only performed with G.711. Therefore, if an IP device uses a voice compression algorithm,
compression resources are mandatory for conversion (in GD, GA or INTIPB boards).
As the communication between the VoIP board providing the compressors and the 4645 VMS is
established in G.711, the VoIP board and the 4645 VMS must belong to the same IP domain. In our
example, the compressors will be selected in the main site (IPMG1), i.e. where the 4645 VMS is
located regardless of the location of the user accessing the 4645 VMS
GD, GA or INT-IP
COMP COMP
2 compressors are
used per conversion
G.711
4645 VMS
G.723
IP Network Signaling: ABC-A
protocol via IP or
internal mechanism
(integrated 4645 VMS)
IP Touch set
Com Server
7.1.3.6 Summary
As explained in this document, for the sites without IPMG (only equipped of IP Touch sets), the notion
of preferred IPMG does not exist except for MOH selection (when the MOH per entity feature is used).

The allocation process does not take into account geographical physical considerations. For example,
it is not possible for IP Touch set K (see Figure 1) to select a voice guide in IPMG2 just because IPMG2
is geographically nearer to set. According to configuration, IPMG1 will provide the requested voice
guide to set K.

Chapter
8 Common Hardware media gateway
8.1 Overview
8.1.1 Overview
The term "OmniPCX Media Gateway" refers to a main shelf, alone or associated with one or two
secondary shelves.
Physically, the OmniPCX Media Gateway is composed of ”common hardware” racks (also used by the
OXO Connect).
There are two types of racks:
• S (Small) racks: with three slots (board positions).
• L (Large) racks: with nine slots (board positions).
A rack includes:
• A GD board which drives the OmniPCX Media Gateway
• Interface boards which connect legacy sets and networks
• A GA board (optional) which provides additional resources to process calls
In addition to the main shelf, a Media Gateway can include one or two secondary shelves (extension
modules). On a secondary shelf, the link with the main shelf is via an HSL board, set in rack controller
position and connected to the GD board by an HSL cable.
As of R9.1, OmniPCX Media Gateways support GD-3, GA-3 and PowerMEX boards. These boards
cannot be mixed with the former generation boards (GD, GA or Mex) in the same OmniPCX Media
Gateway (main rack and extension rack).
Note:
In the rest of this document, the OmniPCX Media Gateway is referred to as the "Media Gateway".
8.2 Commissioning
8.2.1 Commissioning a Media Gateway
To put a Media Gateway into service:
1. Install the racks and boards.
2. Declare the Media Gateway on the Communication Server using the PCX configuration tool.
3. Start-up the Media Gateway.
8.2.1.1 Installing the Racks and Boards

1. Install the racks (see the Installation procedure of the document [23]).
2. Install and connect the boards (see the Installation procedure of the document [23]).
8.2.1.2 Declaring the Media Gateway on the Communication Server

Declare the following:
1. The main rack of the Media Gateway.
2. The secondary racks (if necessary).
3. The Ethernet (MAC) address of the GD board.

Chapter 8 Common Hardware media gateway
4. The boards in the main rack and in the secondary racks.

8.2.1.2.1 Declaring the Main Rack of the Media Gateway
1. Select Shelf
Shelf Address Enter main rack number.

Note:
Addresses 0, 18, and 19 are reserved.
Shelf Type Select rack type from the menu: Media Gateway Small or Media
Gateway Large.
Name of rack Enter a name for the rack.
Shelf role Select Main (Master).
Main Shelf Address Enter the address assigned to the rack or leave at -1.
Law Select from the menu between: Default, A Law or MU Law
Reference Used exclusively for duplication.

This attribute is used to specify the Communication Server which
authorizes management when the IP link between Communication
Servers is lost. Thus:
• When there is a loss of the IP link between the two
Communication Servers, the main Communication Server
connected to the reference Media Gateway continues to
authorize management (and broadcasting).
• When the IP link is re-established between the two
Communication Servers, the Communication Server which is not
connected to the Media Gateway is re-initialized (reboots).
See the Overview on page 43.
8.2.1.2.2 Declaring Secondary Racks
1. Select Shelf
Shelf Address Enter secondary rack number.

Note:
Addresses 0, 18, and 19 are reserved.
Shelf Type Select rack type from the menu: Media Gateway Small or Media
Gateway Large.
Name of rack Enter a name for the rack.
Shelf role Select Expansion 1 or Expansion 2.

Main Shelf Address Enter the number of the main rack which has just been created.
Law Select from the menu between: Default, A Law or MU Law
Reference Enter the same Reference as the one used for the main rack.
8.2.1.2.3 Modifying the GD or GD-3 Board
Creating a main rack results in the automatic creation of a GD-3 board in the controller position
(position 0). If the board type does not match, you must modify it manually.
1. Select Shelf > Board
Shelf Address Enter the main rack number
Board Address Enter the board address
Board Type Select the board type:

• GD
• GD-3
When you change the board type, see Modifying the Board Type on page 110
for more information.
GD/GA Daugh- This parameter is available for the GD board only.

terboard
Select: None, MCV24, MCV8, MADA1 or MADA3.
Daughter Board This parameter is available for the GD-3 board only.
Select: None or ARMADA
No. of Com- This parameter is available for the GD board only.

pressors for
Enter the number of compressors allowed for the gateway application When
Gateway
RTP direct is enabled, there is no longer a specific pool of compressors for
gateway application. There is a common pool of compressors for the two appli-
cations: gateway and IP devices. Only the sum of the two parameters No. of
Compressors for Gateway and No. of Compressors for IP Devices is taken
into account.
No. of Com- For the GD board:

pressors for IP
Enter the number of compressors allowed for IP devices.
Devices
When RTP direct is enabled, there is no longer a specific pool of compressors
for IP devices. There is a common pool of compressors for the two applications:
gateway and IP devices. Only the sum of the two parameters No. of Compres-
sors for Gateway and No. of Compressors for IP Devices is taken into ac-
count.
For the GD-3 board:
Enter the number of compressors allowed for IP devices and the gateway func-
tion. For more information, see: Table 1.

Number of N This parameter is available for the GD board only.

part conferen-
Enter the number of N-party conferences allowed on the Media Gateway. For
ces on MG
more information, refer to the document [3] (section Casual conference, meet-
me conference or mastered conference), according to the type of conference
used.
N part confer- This parameter is available for the GD-3 board only.
ences configu-
For more information, see: Table 1
ration
N part confer- This parameter is available for the GD-3 board only.
ence Type
Select the conference type:
• Meet-me: meet-me conferences can be initialized on this board
• Add-on: mastered or casual conferences can be initialized on this board
Note:
For all GD boards, this is determined by a system parameter. For more information, refer
to the document [3] (section Casual conference, meet-me conference or mastered
conference)

According to the hardware configuration and usage profile, the table below details the available VOIP
channels (compressors), n party conference, voice guides and 3 party conferences:
table 8.1: Board Configuration versus Usage Profile
Profile Additional VOIP N Party Confer- Voice Guides 3 Party Confer-

ARMADA Channels ence ence
(1)
GD-3 No 15 All 16 24
Mixed Profile Configurations
No 30 0 16 24
Yes 45 All 16 24
Configurations
Yes 60 0 16 24
GA-3 Yes 0 4x7, 2x15 16 3

Legacy Profile 1x30
GA-3 No 15 1x7, 2x17, 3x7 16 3

Mixed Profile 1x15
No 30 0 16 3

Yes 30 3x7, 4x7 0 0

2x15, 1x30
Yes 45 1x7, 2x17 0 0

1x15
GA-3 Yes 60 0 0 0
VOIP Profile
GA3CONF No 0 0 0 21
Conf Profile
PowerMEX N/A N/A N/A 0 24
(1): n party conference: the valid configurations are: 1x7,2x7, 3x7, 4x7, 1x15, 2x15 and 1x30 (number
of circuits versus number of participants)
For more information on compressors/conferences configuration, refer to the conference sections of
the document [3].
8.2.1.2.4 Modifying the Board Type
When the board type is modified from GD to GD-3, existing GA boards must be modified to GA-3
boards and existing MEX boards must be modified to PowerMEX boards. This process allows to keep
board consistency (GD/GA/MEX and GD-3/GA-3/PowerMEX).
You must set manually:
• The daughter board configuration
• The number of compressors
• The conference settings (if needed)
• Voice framing (if needed)
When the board type is modified from GD-3 to GD, the board type of the existing GA-3 and PowerMEX
boards are modified to GD and MEX boards in order to keep board consistency. The parameters above
must be set manually.
8.2.1.2.5 Entering the Ethernet (MAC) Address of the GD or GD-3 Board
Creating a main rack results in automatic creation of a GD-3 board in the controller position (position
0). If the board type does not match, you must modify it manually.
Note:
In releases prior to R9.1, a GD board is automatically created.
The Ethernet (MAC) address of the GD-3 board must be entered in its Ethernet parameters. The IP
parameters (IP Coupler Address, IP Netmask, Default Gateway IP Address) must not be entered at
this stage, they will be entered when the board is initialized.
1. Select Shelf > Board > Ethernet Parameters
Shelf Address Enter main rack number.
Board Address 0

Board Ethernet Address Enter the Ethernet (MAC) address of the GD or GD-3 board.
Note:
In some cases, it is not necessary to enter the Ethernet address of the GD boards. Identification is based on rack
number, see Managing Rack Number on page 116.
8.2.1.2.6 Declaring Boards
Shelf Address Enter rack number.
Board Address [0..8]
Interface Type Select a board from the menu.

8.2.1.3 Starting the Media Gateway

The Media Gateway startup corresponds to GD or GD-3 board initialization. There are two possible
initialization processes:
• Static initialization: IP parameters are manually configured on the GD or GD-3 board. Static
initialization must be used if there is no DHCP server. It is also recommended for reasons of
reliability so that Media Gateway operation is not dependent on DHCP server availability. See GD or
GD-3 Board Static Initialization Process on page 111.
• Dynamic initialization (default process): IP parameters are automatically sent by a DHCP server to
the GD board. See GD Board Dynamic Initialization Process on page 115.
Important:
Due to security reason, dynamic initialization is not allowed for GD-3 board.
8.2.1.3.1 GD or GD-3 Board Static Initialization Process
8.2.1.3.1.1 Overview
1. The administrator configures the GD board IP parameters either:
• From a terminal using the mgconfig command, or
• From one UA 4035 connected to the Media Gateway (not supported on GD-3 boards)
The IP parameters to enter are:
• The GD board IP address
• The IP subnetwork mask
• The router address
• The CS role address
• The CS redundancy role address
Note:
In a duplicated Communication Server configuration:
• When the two Communication Servers are in the same IP subnetwork, the same main IP address can
be used for the two Communication Servers. This address must only be entered once in the CS role
address field.
• When the two Communication Servers are on different IP subnetworks, the duplicated Communication
Server main IP address must be entered in the CS redundancy role address field.

2. The GD board sends a TFTP request towards the main IP addresses of the two Communication
Servers configured previously.
3. The GD board downloads the binaries from the main Communication Server.
4. The GD board sends a new TFTP request towards the main IP addresses of the two
Communication Servers configured previously.
5. The GD board downloads the startemg file from the main Communication Server.
8.2.1.3.1.2 Starting the GD Board Static Initialization Process with mgconfig Command
1. Connect to the GD board via the console port (Config connector). For more information, see:
Connecting via the Console Port on page 116.
2. Power up the GD board.
3. Open a session under the root account.
Note:
To interrupt the board initialization when you want to modify the configuration, unplug the IP cable and access
configuration from the console port or UA set.
4. Run the mgconfig command.
eMGD login: admin
Password:
[admin@eMGD admin]$ su
[root@eMGD admin]# mgconfig
Welcome to the GD IP configuration tool
---------------------------------------
MAC address 00809F2E1672
1. Startup mode Dynamic
2. IP address 192.168.4.53
3. Netmask 255.255.255.0
4. Gateway address 192.168.4.254
5. CS role address 192.168.4.52
6. CS redundancy role address 192.168.7.48
7. Crystal number 3 (Dynamic allocation-Refer
mgr)
8. IP QoS menu
9. BACKUP menu
10. Duplex and speed mode menu
11. Download binaries timeout 1200
12. Passive CS address 0.0.0.0
13 Security function
14 Encryption
15 Telnet Service
0. Exit
5. Select the menu 1. Startup mode to change the initialization process in Static.
6. Enter the following parameters:
• The GD board IP address (menu 2. IP address)
• The IP network mask (menu 3. Netmask)
• The router IP address (menu 4. Gateway address)
• The local Communication Server main IP address (menu 5. CS role address)
• The duplicated Communication Server main IP address in a duplicated Communication Server
configuration where the two Communication Servers are on different IP subnetworks (menu 6.
CS redundancy role address)
Note:
The default value is 0.0.0.0 when this parameter is not managed.
• The rack address of the Media Gateway (menu 7. Crystal number)
Note:
The default value is 3 when this parameter is not managed.
• the VLAN number (menu 8. IP QoS menu)

•If the Media Gateway is rescued by a Passive Communication Server, the Passive
Communication Server IP address (menu 12. Passive CS address)
• The VLAN number (menu 8. IP QoS menu)
• If the Media Gateway is rescued by a Passive Communication Server, the Passive
• If security options must be set, use the 13. Security function menu. For more information,
refer to the IP Touch Security section of the document [7]
• If encryption must be set, use the 14. Encryption menu. For more information, refer to the IP
Touch Security section of the document [7]
7. Press 0. to exit the tool.
The system displays:
Configuration not saved – Do you want to save now ? (y/n)
8. Enter y.
Do you want to reboot now ? (y/n)
9. Enter y to reset the GD board.
8.2.1.3.1.3 Starting the GD Board Static Initialization Process from a UA 4035 set
Requirements:
• The GD board must not be connected to the LAN network. If it is, unplug the IP cable.
• At least one UA 4035 set must be declared and connected to a Media Gateway rack.
Note:
The static initialization process configuration is not available on a 9 Series set.
Note:
The static initialization configuration from a UA set is not supported on GD-3 boards.

2. On a UA 4035 set connected to the Media Gateway, when the set displays "Phase 1", successively
press the [i] and # keys.
The UA set displays:
1. MAC Address 3. Backup 5. IP QoS

2. IP Parameters 4. Others 0. Restart
3. Select the menu 2. IP Parameters and configure the IP parameters (see above).
In the menu 5. DHCP, check the DHCP server is not activated (off selected). This parameter is
used for Dynamic initialization.
4. Select the menu 4. Other to configure the rack number (sub-menu 2. Crystal number)
5. Select the menu 5. IP QoS to configure the VLAN number
6. Connect the IP cable to the GD board.
7. Press 0. Restart to reset the GD board.

8.2.1.3.1.4 Starting the GD-3 Board Static Initialization Process with mgconfig Command
1. Connect to the GD-3 board via the console port (Config connector). For more information, see:
Connecting via the Console Port on page 116.
2. Power up the GD-3 board.
3. Open a session under the root account (no password entry).
Note:
To interrupt the board initialization when you want to modify the configuration, unplug the IP cable and access
configuration from the console port.
4. Run the mgconfig command.
-bash-3.2# mgconfig
Tue Jul 12 16:36:48 UTC 2016
[Script /etc/rc.d/init.d/verify_ipmg (PID=29193) started by "mgconfig"]
The ipmg.cfg is in good shape in RAM
backup config file not available...
Welcome to the GD configuration tool
---------------------------------------
FW version
mg3_07.59_01Apr16_17h40
---------------------------------------
Board role GD
1. IP N/W Mode IPV4only
2. View/Modify IP Addresses
3. Crystal number 3 (Manual allocation)
4. IP QoS menu VLAN
disabled
5. BACKUP menu (Not
Available)
6. Duplex and speed mode menu auto
7. Download binaries timeout 1200[ms]
8. Security and Encryption PROTECT, SoftMSM enabled, PSKg2
9. Telnet server open
10. Archive log files
11. Allow shell commands usage allowed
12. IPV4 Forwarding
0. Exit
5. Select the 2. View/Modify IP Addresses option and enter the following parameters:
• The GD-3 board IP address (menu 1. IPv4 address)
• The IP network mask (menu 2. IPv4 subnetmask)
• The router IP address (menu 3. IPv4 gateway)
• The local Communication Server main IP address (menu 4. CPU role address)
• The duplicated Communication Server main IP address in a duplicated Communication Server
configuration where the two Communication Servers are on different IP subnetworks (menu 5.
CPU redundancy role address)
Note:
The default value is 0.0.0.0 when this parameter is not managed.
• If the Media Gateway is rescued by a Passive Communication Server, the Passive
6. Press 0 to exit the submenu
7. If necessary, enter the VLAN number (menu 4 . IP QoS menu)
8. If security options must be set, use the 8. Security and Encryption menu. For more
information, refer to the IP Touch Security section of the document [7]
9. Press 0. to exit the tool.
Configuration not saved – Do you want to save now ? (y/n)

10.Enter y.
Do you want to reboot now ? (y/n)
11.Enter y to reset the GD board.
8.2.1.3.2 GD Board Dynamic Initialization Process
Important:
The dynamic initialization is not supported on GD-3 board.
8.2.1.3.2.1 Overview
1. At board startup, the GD board sends a request to the DHCP server which returns the following IP
parameters:
• The GD board IP address
• The TFTP server address
2. The GD board downloads the lanpbx.cfg file from the TFTP server. This file contains the list of
Communication Server IP addresses in the PCX network. For information on lanpbx.cfg generation,
refer to the lanpbxbuild section of the document [13] (if the file does not exist on the PCX, it is
created automatically).
Note:
A lanpbx.cfg file created automatically doesn't contain a list of Communication Server IP addresses in the PCX
network. It contains local Communication Server IP addresses.
3. The GD board sends a TFTP request towards the Communication Servers IP addresses declared in
the lanpbx.cfg file.
4. The GD board downloads the binaries from the main Communication Server.
5. The GD board sends a new TFTP request towards the two Communication Servers main IP
addresses.
6. The GD board downloads the startemg file from the main Communication Server.
8.2.1.3.2.2 Starting the Dynamic Initialization Process
Requirements:
• Before starting initialization, you must program on the DHCP server a static address (Ethernet
(MAC) address - IP address correspondence) for the GD board. The advantage of static
addressing is that the DHCP server always assigns the same IP address to the GD board at
subsequent start-ups. For more information, refer to the DHCP Server section of the document
[7].
• If the DHCP server is internal to the Communication Server, no address of TFTP server must be
entered in DHCP server configuration. The DHCP server provides the appropriate IP address of
the Communication Server. In a duplicated Communication Server configuration where the two
Communication Servers are on different IP subnetworks, a DHCP relay must be activated on the
IP subnetwork where the GD board is located.
• If the DHCP server is external, the TFTP server address must be entered in DHCP server
configuration. In a duplicated Communication Server configuration where the two Communication
Servers are on different IP subnetworks, the TFTP server must be external.

2. Check the board initialization process is set to Dynamic. If board initialization process has been
changed previously and the board is set to static, it must be switched back to dynamic using the
mgconfig command.

8.2.2 Managing Rack Number

In some cases for example, if you have only one Communication Server, the rack number is sufficient
to identify a Media gateway and the Ethernet address of the GD board does not need to be checked.
If you choose identification via rack number, you must disable the Ethernet address check performed
by the Communication Server.
1. Select IP > INTIP/IP Parameters
Ethernet Address Select False.

Checked By TFTP.
Default value: True.
Note:
• Check that the rack number is configured on the GD board using mgconfig or via a UA set interface.
• For GD-3 board, Ethernet address is always checked.
8.3 Maintenance
8.3.1 Connecting a Media Gateway
8.3.1.1 Connecting via the Console Port
Connect a VT100 console (or a PC with a VT100 emulation Hyper Terminal) to the console port of the
GD or GA board.
Media Gateway
GD-3
. . .
VT100 Console
3EH 75003AAAA
RJ45/SubD9 Cable
Figure 8.1: Connecting a Console to a Media Gateway
Account to use:

• root: by default the password is empty

On GD-3 and GA-3 boards, there is no password
• admin: by default the password is admin
8.3.1.2 Connecting via Telnet

The Telnet service is available on all GA/GD boards. Telnet sessions can be opened from the main
Communication Server only.
Telnet sessions to the GA/GD boards can be secured (IP Touch Security service).
To open a Telnet session in a duplicated Communication Server configuration, the telnet_al
command must be used (the telnet command does not work). In a single Communication Server
configuration, the telnet command can also be used to open Telnet sessions.
8.3.1.2.1 Activating the Telnet Session
The activation duration is either permanent or limited by a timeout, configured in days. When the
timeout expires, the Telnet server is closed and it is impossible to open a new Telnet session. Opened
Telnet sessions are not closed.
Note:
The Telnet server is limited to launching sessions. If this server is down, current Telnet sessions keep running.
Activation and deactivation of the Telnet server are performed with:
• The ippstat tool for GA or GD boards.
Note:
The Communication Server generates incident 5870 each time the ippstat command (option 21) is used.
The incident parameter indicates the number of allowed Telnet sessions (4 maximum). 0 indicates that the
Telnet server is closed.
• The mgconfig tool for GA-3 or GD-3 boards (available as of R9.1).
For GA2 and GD2 boards, ippstat and mgconfig tools can be used to activate or deactivate the
Telnet server.
To activate the Telnet server:

If the Media Gateway includes: Use the following procedure:
one of GA, GD, GA-2 or GD-2 1. On the main Communication Server, enter the ippstat
boards command
2. Select option 21: Enable telnet service for GD/GA
3. Enter the shelf number of the Media Gateway when the
prompt displays Cristal Number:
4. Enter the board number of the GD/GA board when the
prompt displays Coupler Number:
5. Press 1 to increment the number of allowed Telnet sessions
when the prompt displays Press 1 to increment max
telnet sessions allowed, 0 to disable the
service:
one of GA-2, GD-2, GA-3 or GD-3 1. Connect to the corresponding board via the V24 port (or
boards cpl_online from the Communication Server)
2. Open a session with the root account and run the
mgconfig command
The Telnet server activation mode (open or close) is
determined by option 9. Telnet server (option 15.
Telnet Service for GA-2/GD-2 boards)
3. If the activation mode is set to close, select the option 9.
Telnet server
4. Select either 1: open or 2: open with timeout
5. Select option 0. to exit the menu
6. Reboot the board
Note:
For more information on the ippstat tool, refer to the ippstat section of the document [13].
To deactivate the Telnet server:

If the Media Gateway includes: Use the following procedure:
one of GA, GD, GA-2 or GD-2 1. On the Communication Server, enter the ippstat
boards command
2. Select option 21: Enable telnet service for GD/GA
3. Enter the shelf number of the Media Gateway when the
prompt displays Cristal Number:
4. Enter the board number of the GD/GA board when the
prompt displays Coupler Number:
5. Press 0 to disable the Telnet service when the prompt
displays Press 1 to increment max telnet
sessions allowed, 0 to disable the service:
one of GA-2, GD-2, GA-3 or GD-3 1. Connect to the corresponding board via the V24 port (or
boards cpl_online from the Communication Server)
2. Open a session with the root account and run the
mgconfig command
The Telnet server activation mode (open or close) is
determined by option 9. Telnet server (option 15.
Telnet Service for GA-2/GD-2 boards)
3. If the activation mode is set to open, select option 9.
Telnet server
4. Select 0: close
6. Reboot the board
8.3.1.2.2 Opening a Telnet Session

To access a Media Gateway via Telnet:
1. Open a session on the main Communication Server
2. Enter the Telnet command and IP address of the Media Gateway
When the Telnet session is opened, enter your login and password.
Note:
Use the admin account (default password: admin), not the root account. On GA-3/GD-3 boards, Use the
root account without password.
8.3.1.2.3 Until R8.0.1
1. Open a session on the main Communication Server
2. Enter the Telnet command and IP address of the Media Gateway
When the Telnet session is opened, enter your login and your password.
Note:
Use the admin account (default password: admin), not the root account.
8.3.1.2.4 As of R9.0
On Media Gateways, the Telnet server must be activated manually before opening a Telnet session.

8.3.2 Replacing a GD or GD-3 Board

First, you must declare the new board's Ethernet (MAC) address on the Communication Server.
Shelf Address Enter main shelf number.
Board Address 0
Board Ethernet Address Enter the Ethernet (MAC) address of the new GD or GD-3 board.
1. Connect to the GD or GD-3 board
2. Run the mgconfig command
3. Switch initialization process to static, then Enter the IP parameters.
Caution:
For more information on GD or GD-3 connection, see: Connecting a Media Gateway on page 116.
By default, when the board is delivered from the factory, it is configured for Dynamic initialization.
Depending on the chosen board initialization mode, you must either:
• In Static initialization:
1. Connect to the GD or GD-3 board
2. Run the mgconfig command
3. Switch initialization process to static, then enter the IP parameters.
Caution:
• In Dynamic initialization: on the DHCP server, reprogram manually the address of the GD board
with the new Ethernet (MAC) address.
8.3.3 Communication between the GD or GD-3 Board and the Communication Server
A communication problem can occur between the GD or GD-3 board and the Communication Server.
This problem is often due to incorrect network configuration.
Depending on the board initialization process, you must either:
• In Static initialization: check the main IP address(es) of the Call Server(s) using the mgconfig tool
on the GD or GD-3 board.
Caution:
• Or in Dynamic initialization:
1. Check the address of the TFTP server used for lanpbx.cfg file download.
2. If the dialog is still not established, the lanpbx.cfg file may be incorrect. You can update this file
by running the lanpbxbuild command on the Call Server.
8.4 Cabling instructions

This document describes recommended cabling instructions for several simple configurations with
Communication Server on the CS-2/CS-3 board (first configuration in Topology on page 96).

There are two types of cases:

• classic configurations: phone devices (Communication Server, GD-3, GA-3, IP-Phones) are
connected internally to LANX 16 boards (possibly, to the 4 port LAN switch of CS-3, or CS-2 board
SLANX4),
• IP configurations: phone devices are connected to an external switch (for example: Alcatel-Lucent
6124 switch).
8.4.1 Classic Configurations

The following examples offer cabling recommendations for "classic" configurations, where phone
devices are connected internally to the PCX switches. These configurations apply to systems with
many Reflexes sets and few IP-Phones.
Remark:
The examples presented here use the (S)LANX boards of the PCX, but other customer switches can be used.
8.4.1.1 Stand-alone Configuration without Duplication, with 1 or 2 Media Gateways

In a stand-alone configuration, with no Communication Server duplication (redundancy), but one or two
Media Gateways, all the necessary connections can be provided by the CS-3 board (which natively
provides a four port LAN switch), or by a CS-2 board equipped with a SLANX4 daughterboard.
Whether using the CS-3 LAN switch, or a CS-2 board equipped with a SLANX4 daughterboard, the
LAN port of the CS board must be connected to a port of the switch (green link in the figure below).
CALL SERVER PROCESSING UNIT

CS-2
LAN1 LAN2 . .
GD-3
CS-2 LAN1 LAN2 .

HD FAN POWER
UNIT 1 UNIT 2 UNIT 3 UP-LINK USB

UNIT 1 UNIT 2 UNIT 3 UP-LNK CPU
GD-3
To LAN switch
Figure 8.2: Stand-alone Configuration without Duplication, with 1 or 2 Media Gateways
In a configuration with one Media Gateway including a GA-3 board, the GA-3 board can also connect
to the four port LAN switch of CS-3 (or to the SLANX4 daughterboard of the CS-2 board).
8.4.1.2 Duplicated Communication Server with a Single Media Gateway

In this case, the two Communication Servers are connected to the same LANX board.

To LAN switch
CS-2
ETHERNET LANSWITCH LANX 16

9 10 11 12 13 14 15 UP-LINK
GD-3
LANX
CS-2
1 2 3 4 5 6 7 8
Figure 8.3: Duplicated Communication Server with a single Media Gateway
8.4.1.3 Duplicated Communication Server with two Media Gateways

Cabling is executed as follows:
• the two Media Gateways are connected to a (S)LANX board and the two Communication Servers
are connected to a different (S)LANX board.
• if there is no GA-3 board on the Media Gateway, the Communication Server SLAN board may
suffice; however, a LAN16 board is recommended, to facilitate initialization.
• the two LANX boards are interconnected and both are connected to the LAN switch.
Note:
This topology creates a loop in the network. It is possible if one of the switches in the loop supports STP
protocol. LANX boards do not support this protocol, so the external switch must support STP protocol (see STP
protocol on page 132).
This configuration offers the following characteristics:
• the unavailability of a LANX board does not block the system. A Communication Server and a
Media Gateway are still operational and connected to the LAN,
• the unavailability of the LAN connection switch has no impact on the phone system, since the two
LAN boards are directly interconnected.

GD-3
GD-3
ETHERNET LANSWITCH
9 10 11 12 13 14 15
LANX 16
UP-LINK
LANX
GA-3 CS-2 1 2 3 4 5 6 7 8
Reference Media Gateway

LAN switch
(with STP support) LAN
GD-3 ETHERNET LANSWITCH

9 10 11 12 13 14 15
LANX 16
UP-LINK
LANX
1 2 3 4 5 6 7 8
CS-2
Figure 8.4: Duplicated Communication Server with 2 Media Gateways
Note:
In a duplicated (redundant) system, according to ACTIS, the typical configuration includes the main
Communication Server in the Media Gateway rack and the stand-by Communication Server in a dedicated 1U
rack.
8.4.1.4 Duplicated Communication Server with 1 OmniPCX Media Gateway and 1 ACT Media
Gateway
• a LANX board is installed on the OmniPCX Media Gateway,
• the two Communication Servers are connected to the LANX board,
• the INT-IP board of the ACT Media Gateway is connected to the LANX board.
In the case, a failure of the LANX board results in a total unavailability of the system.

To LAN switch
CS
CS-3

9 10 11 12 13 14 15 UP-LINK
GD-3
LANX
CS-3
1 2 3 4 5 6 7 8
CS
INT-IP
Figure 8.5: Duplicated Communication Server with 1 OmniPCX Media Gateway and 1 ACT Media
Gateway
8.4.1.5 Duplicated Communication Server with 2 OmniPCX Media Gateways and 1 ACT Media
Gateway
• a LANX board is installed on each one of the two Media Gateways,
• each one of the two LANX boards receives a Communication Server,
• each one of the two LANX boards receives one of the two INT-IP boards of the ACT Media
Gateway,
• a loop is created to eliminate the point of failure: the two LANX boards are connected to the LAN
switch as well as between each other.
Note:
this configuration implies that the external switch supports the STP protocol (see STP protocol on page 132).
• If a LANX board fails, a Communication Server, a Media Gateway and an ACT Media Gateway
remain operational and linked to the LAN,
• if the connection switch to the LAN fails, the phone service remains operational.


9 10 11 12 13 14 15
LANX 16
UP-LINK
LANX
GA-3 CS-2 1 2 3 4 5 6 7 8
INT-IP 1
INT-IP 2 LAN switch


9 10 11 12 13 14 15
LANX 16
UP-LINK
LANX
1 2 3 4 5 6 7 8
CS-2
Figure 8.6: Duplicated Communication Server with 2 OmniPCX Media Gateways and 1 ACT Media
Gateway
8.4.1.6 Configuration with a 4645 Voice Mail System

The system may prove to be more reliable when the 4645 voice mail is located on a dedicated rack. In
case of failure or maintenance of one Communication Server, the 4645 voice mail remains operational.
This is represented in the example below.

4645

9 10 11 12 13 14 15
LANX 16
UP-LINK
LANX
GA-3 CS-2 1 2 3 4 5 6 7 8

LAN switch

9 10 11 12 13 14 15
LANX 16
UP-LINK
LANX
1 2 3 4 5 6 7 8
CS-2
Figure 8.7: Configuration with a 4645 Voice Mail on a Dedicated Rack
8.4.2 IP Configurations
The two examples below describe the cabling recommendations for "IP" configurations where phone
equipments are connected via external switches. These configurations are appropriate for systems with
many IP-Phones.
8.4.2.1 "Extended" IP Architecture

This section describes an example of extended architecture (for example, a building with several
floors), where all the phone devices do not belong to the same IP network and are separated by
routers. In this case, the system's reliability depends on the routers between IP networks.
The recommended solution is to:
• connect the two Communication Servers and the reference Media Gateway to 3 different external
switches,
• duplicate the LAN connection router,
• connect the 3 switches to the two routers.
Note:
this solution requires:
• switches which support QoS, VLAN and STP protocols,
• routers which support HSRP (Hot Stand-by Routing Protocol) and VRRP (Virtual Router Redundancy Protocol)
protocols to provide a Main router and a Standby router that share the same virtual IP address.
• if one of the two Communication Server connection switches fails, the Communication Server
Standby switches to Main, and the system remains operational.

• if the Main router fails, the Standby router takes over: thus, the remote Media Gateway remains
accessible and operational.
Switches
Switches / Route
CS-2
HSRP
CS-2 LAN
VRRP
GD-3

GD-3
Figure 8.8: Distributed IP Architecture
8.4.2.2 "Local" IP Architecture

This section describes an example of a configuration localized to an IP network. Phone devices are
connected via "stackable" external switches which create a loop.
In the figure, cabling is executed as follows:
• the two Communication Servers and the Media Gateway are all connected to a different switch,
• the 3 switches are interconnected through a loop.
Note:
this configuration requires switches which support QoS, VLAN and STP protocols.
If one of the two Communication Server connection switches fails, the Communication Server Standby
switches to Main, and the system remains operational.

OmniStack 6124 or 6148

(supports QoS, VLAN,
STP)
CS-2
GD-3 LAN
CS-2
Figure 8.9: "Local" IP Architecture
8.5 GD/GA or GD3/GA3 board reloading

8.5.1 Overview
When the binary of the GD/GA board or GD-3/GA-3 board is corrupted, their flash memory must be
reloaded.
The OmniPCX Enterprise PC installer software application (called PC installer in this document) is
used to reload board flash memory.
GD3/GA3 board
in controller position
Common hardware rack
Ethernet VT100
cross cable cable
PC Installer Console VT100

Figure 8.10: Flash memory reloading configuration
For more information on PC installer, refer to the document [28].

For more information on board connections and configuration switches, refer to the document [28].
The deliveries are retrieved from the patches installed in the dhs3mgr directory of the machine hosting
the PC installer. At least one static patch must be available in this directory so that all types of binaries
are available for download.

8.5.2 GD or GA board reloading

To reload GD or GA board flash memories:
1. Erase and format flash memories
2. Download binary files
8.5.2.1 Erasing and formatting flash memories

1. Start the PC Installer application (V2.26 or higher)
2. Configure the PC installer:
a. In the Installation type field, select the GD/GA/… binary option
b. In the Type of Media Gateway board field, select the GD/GA option
c. Click Apply
3. Copy (or verify the presence of) binary files on the machine hosting the PC installer application in
the /dhs3mgr/"version"/pcmao/boot_res/DHS3bin/downbin/emg directory.
Note:
The GD board and the GA board use the same binary files.
4. Set the GD/GA board to a reformatting configuration (also called LOLA mode):
a. Set configuration switches: switches 1, 2 and 4 to ON and switch 3 to OFF
b. Insert the board in the controller position (position 0 of the rack)
5. Connect the GD/GA board to the PC installer via an Ethernet crossed cable
6. Connect the VT100 console to the Config port of the board
7. Start the GD/GA board with the On/Off switch
The CPU LED indicates progress:
CPU LED Meaning
2 x ON/OFF (250ms)/ 1 OFF ( 2 s) BIOS in progress
4 x ON/OFF(250ms)/ 1 OFF ( 2 s) Linux.RAM loading
Fixed ON Flash memory erasing and formatting
Fast flashing (50 ms/ 50 ms) End of formatting
When formatting the flash memory is completed, the following message is displayed on the console:
Welcome to PeeWeeLinux
(none) login:
8. Stop GD/GA board with the On/Off switch and wait until the Power LED is switched to fixed red
9. Stop the PC Installer
8.5.2.2 Downloading the GD/GA binaries

1. Start the PC Installer (V2.26 or higher)
2. Configure the PC installer
a. In the Installation type field, select the GD/GA/… binary option
b. Click Apply in the Installation parameters window
3. Set the board:
• For the GD board, set the configuration switch 2 to ON and switches 1, 3 and 4 to OFF
• For the GA board, set the configuration switches 1 and 2 to ON, switches 3 and 4 to OFF

4. Insert the board in the controller position (slot 0)

5. Start the GD/GA board with the On/Off switch
The Client parameters window displays the list of transferred files.
When download is completed, you are prompted to open an session on the configuration console.
6. Open an admin session
7. Enter the mgconfig command and set the IP configuration
8. Stop GD/GA board with the On/Off switch and wait until the Power LED is switched to fixed red
8.5.3 Erasing and reloading a GD-3 board or GA-3 board

To proceed:
1. Insert the board in the controller position (slot 0)
2. Connect the board to the PC installer with an Ethernet crossed cable
3. Copy (or verify the presence of) binary files on the on the machine hosting the PC installer
application:
The GD-3 binary files (depending on the version) must be present in the /dhs3mgr/"version"/
pcmao/boot_res/DHS3bin/downbin/mg3 directory
Note:
The GD-3 and GA-3 boards use the same binary files.
4. Start the PC Installer (V2.26 or higher)
a. In the Installation type field, select the GD/GA/GD3/GA3/INTIP3/IOIP3 binary option
Figure 8.11: PC installer interface example

b. In the Media Gateway board designation field, select the GD3/GA3 option

c. Click Apply
The PC installer is waiting for board request.
6. Connect a terminal to the CONFIG port of the board
7. Switch on the board and enter the BIOS menu:
Two seconds after power on, as soon as the prompt Press ^B^I to enter into the Bios
menu is displayed, quickly press CTRL + B and CTRL + I command.
Figure 8.12: Terminal traces after power on
Note:
On new generation board, you can skip this operation. The board automatically requires binary fields from the
PC installer.
8. In the BIOS menu select the 3 : Load from Ethernet option
The board erases its flash memory, requests binary files from the PC installer, and loads it.
When download is completed, the board restarts.
When the board is restarted, the mgconfig menu is displayed:
Example:
Welcome to the GD configuration tool
---------------------------------------
FW version
mg3_07.59_01Apr16_17h40
---------------------------------------
Board role GD
1. IP N/W Mode IPV4only
2. View/Modify IP Addresses
3. Crystal number 3 (Manual allocation)
4. IP QoS menu VLAN
disabled
5. BACKUP menu (Not
Available)
6. Duplex and speed mode menu auto
7. Download binaries timeout 1200[ms]
8. Security and Encryption PROTECT, SoftMSM enabled, PSKg2

9. Telnet server open

10. Archive log files
11. Allow shell commands usage allowed
12. IPV4 Forwarding
0. Exit
9. Select the 2. View/Modify IP Addresses option and configure IP parameters
8.6 STP protocol

8.6.1 Overview of the problem
The phone system's reliability is not only based on the Communication Server and phone devices, but
also on the IP network architecture and on the type of switches used (basic, medium, high-end).
In a classic IP network, the architecture has the a tree structure (or a star structure), there are no loops.
Loops are a problem for multicast frames and broadcast frames, which continue to circulate and can
multiply needlessly. On the other hand, the problem with tree-structured architecture is that each node
constitutes a possible point of failure. In the event of a node failure, the entire branch connected to it is
cut from other network elements.
Example:
in the example described below, the LAN connection switch constitutes a point of failure. Its failure causes a
degraded operation mode of the phone system since the two LANX boards are no longer interlinked. A direct
connection between these two boards should solve this difficulty.
GD-3 9 10 11 12 13 14 15 UP-LINK
LANX
CS-2 1 2 3 4 5 6 7 8

LAN
switch LAN
GD-3 9 10 11 12 13 14 15 UP-LINK
LANX
1 2 3 4 5 6 7 8
LAN switch is a
point of failure
CS-2
8.6.2 Spanning Tree Protocol

STP is a protocol used to create redundant paths in a network while barring routing loops.
To eliminate loops in a network, STP sets certain switch segments and ports to a blocked state. To do
this, STP first chooses a root switch (one for each VLAN). By default, the root switch is the switch with
the smallest MAC address. Strategically, it is preferable to configure a switch with a central position in
the network as the root switch.

Once the root switch has been chosen, a tree is built to link all the network devices. The path to link the
root switch to another switch in the network is the minimum cost path. By default, it is the most direct
path but it is possible to configure the costs of the different ports manually in order to give precedence
to certain links whose bandwidth is higher.
This configuration results from port switch specialization:
• root port: port used to reach the root switch,
• specified port: routing port to a LAN segment,
• alternative port: blocked port providing an alternative path to the root switch,
• backup port: blocked port that can be used in the event of a failure of certain network elements.
The initial tree construction is executed by BPDU broadcast frames transmitted by the network
elements. Once the initial building is completed, the BPDU frames are periodically transmitted in order
to check that all network links operate properly. When a failure is acknowledged in the network, a new
tree is constructed. Ports which were initially in blocked state can become active, and vice-versa.
Example: in the meshed network below, A is chosen as root because of its central position. E is the
specified switch to access F and G. In this diagram, only the root ports (RPs) are indicated. The dotted
lines, which represent the blocked segments, lead to the blocked ports. The other ports are routing
ports.
Terminal equipments
switch root
D F
RP RP
RP RP
C RP A E G
RP
Figure 8.13: Example of tree construction
If switch E fails, a new tree is constructed to solve the problem. Switch D is specified to reach F and G;
port assignments are modified accordingly.

Terminal equipments
switch root RP
D F
RP
RP
C RP A E G
RP
Figure 8.14: Modifying the tree after a node failure

Chapter
9 Crystal Hardware media gateway
9.1 Overview
9.1.1 Overview
This document describes how to commission an ACT Media Gateway connected via IP. Connection via
IP is specific in that the link between the ACT Media Gateway and Call Server cannot be set up
immediately. A preliminary phase, involving acquisition of IP parameters by the ACT Media Gateway
controller board and a binary download from the Call Server, must be performed.
An ACT Media Gateway on IP is controlled by an INT-IP B or IOIP board installed in a CPU slot. This
board may be duplicated. The INT-IP B or IOIP board only provides a link with the Call Server or main
Crystal shelf. It does not act as an H.323 gateway and does not handle IP-Phone signaling.
9.2 Architecture
On the basis of the three standard topologies described in the Topology on page 96, this section
describes three basic types of configuration.
9.2.1 Configuration 1
The main area is composed of an OmniPCX Media Gateway (S and L racks): there may be an auxiliary
ACT Media Gateway in the main area and remote ACT Media Gateways over IP. Connection to the
Call Server is via IP.
5 Main Call Server in a duplicated Call Server configuration

Chapter 9 Crystal Hardware media gateway
INT-
IP B
Remote ACT Media

Gateway over IP
WAN
LAN
OmniPCX
INT-
Media Gateway
GD IP B
Call Server
Auxiliary ACT
Media
Gateway
Appliance Server
MEX MEX
or CS Board
Main Area
Figure 9.1: Configuration 1
Main area with a main Crystal shelf hosting the Call Server on a CPU board: there may be remote ACT
Media Gateways over IP. The inter ACT link is established between the CPU and the INT-IPB board.
The INT-IPA board provides resource for VOIP communication.

INT- Remote ACT Media

IP B Gateway over IP
WAN
LAN
Main Crystal
INT- Shelf with Call
CPU
IP A Server
Main area
Main area with an ACT Media Gateway and Call Server on Appliance Server. In this case, the main
Crystal shelf is connected to the Call Server via the IP network. There may also be remote ACT Media
Gateways over IP.

INT-
IP B
Remote ACT Media

Gateway over IP
WAN
LAN
INT-
IP B
Internet Server platform
Main ACT
Appliance Server Media Gateway
Main Area
Note:
With this latter configuration, an INTOF or RT2 connection behind the main ACT Media Gateway may be used.
If there is a peripheral Crystal shelf on INTOF, 2 signaling modes can be used: TS16 mode or N64 mode.
IP Network
INT-IP B or
IOIP Board
Level 1
INT- INTOF
IP A A
INTOF
B
INTOF
B
Level 2
Level 2 INTOF Links

Appliance Server
Main Area
Note:
The INT-IP3 board cannot be used as an IOIP board.

9.2.4 Restriction
On an ACT Media Gateway, the INT-IPB main and the INT-IPB standby must be of the same board
generation: two INT-IP3 boards or two INT-IP from older generation.
9.3 Commissioning
9.3.1 Overview
The commissioning procedure is almost identical, irrespective of system architecture. The only
difference is with configuration 3 (see the Configuration 3 on page 137): if an INTOF connection with
4*64 kbps signaling is used, you must declare an IOIP board instead of the INT-IP B board.
Note:
The INT-IP3 board cannot be used as an IOIP board.
9.3.2 Principle
To put an ACT Media Gateway into service:
1. If required (see configuration 2 above), declare an INT-IP A board in the main Crystal shelf.
2. Declare the ACT Media Gateway on the Call Server using the PCX configuration tool.
3. Install and connect INT-IP B (or IOIP) board in the ACT Media Gateway.
4. Start-up the ACT Media Gateway.
9.3.3 Declaring the INT-IP A Board

In configuration 2, at least one INT-IP A board must be declared in the main Crystal shelf. This board
provides compression resources.
9.3.4 Declaring the ACT Media Gateway

Declare the following:
1. The Crystal shelf of the ACT Media Gateway (this is always declared as a peripheral shelf).
2. An INT-IP B (or IOIP) board in CPU position.
3. The Ethernet (MAC) address of the INT-IP B (or IOIP) board.
4. At least another board in the Crystal shelf (required for commissioning).
9.3.4.1 Declaring the Crystal Shelf of the ACT Media Gateway

1. Select Shelf
Shelf Address Enter Crystal shelf number.

Note:
Numbers 0, 18 and 19 are reserved.
Shelf Type Select Crystal shelf type from the menu: ACT-14 Interfaces or
ACT-28 Interfaces.
Name of rack Enter a name for the Crystal shelf.

ACT Type Select Peripheral ACT Shelf.

Remark:
In configuration 3, the Crystal shelf in the main area is also declared as a
peripheral ACT shelf. In management, the Call Server is considered to be
the main Crystal shelf (No. 0).
9.3.4.2 Declaring the INT-IP B (or IOIP) Board

Board Address Enter the slot number of the board in the Crystal shelf.
This board must be in a CPU slot. The options are:
• Slot 1 in a 4-slot Crystal shelf (Voice Hub) or in a 9-slot
Crystal shelf (WM1)
• Slot 6 in a 14-slot Crystal shelf
Interface Type Select INTIPB, INTIP3B or IOIP (if the signaling mode
used is IO2).
INTIP Daughterboard Specify the type and number of daughterboards installed

on the board, the options are:
• None: no daughterboard.
• GIP6x1: one GIP6 daughterboard.
• GIP6x2: two GIP6 daughterboards.
• 1 GIP4-4: one GIP4-4 daughterboard (as of R6.0).
• 2 GIP4-4: two GIP4-4 daughterboards (as of R6.0).
• 1 GIP6A: one GIP6A daughterboard.
• 1 GIP4-1: one GIP4-1 daughterboard (as of R6.0).
• 2 GIP6A: two GIP6A daughterboards.
• 2 GIP4-1: two GIP4-1 daughterboards (as of R6.0).
• ARMADA: if the mother board is an INT-IP3 board (as
of R9.1)
If an IOIP board is used, a daughterboard cannot be instal-
led (no compressor on IOIP boards).
Board IP Version IP Default

Note:
When the board has been created, an additional attribute is displayed in view/modify:

No. of Compressors for IP Devices Enter the number of compressors that can be used. The val-
ue entered is used to calculate the maximum number of PCX
compressors for the "G729A Server" and "469 G723.1 Serv-
er" 135 locks.
According to hardware configuration, the table below details the number of available VOIP channels.
Profile Additional ARMADA VOIP Channels
INT-IP3B 0 30
Main/Standby
1 60 (30+30)
9.3.4.3 Entering the Ethernet (MAC) Address of the INT-IP B (or IOIP) Board
Once the INT-IP B board has been declared, its MAC address must be entered in its Ethernet
parameters. IP parameters are not completed at this stage, they are completed at board initialization.
Interface Type INTIPB or IOIP (if 4*64 kbps signaling on INTOF is

used).
Board Ethernet Address Enter the board Ethernet MAC address. This informa-
tion is included in the label attached to the board.
9.3.4.4 Declaring another Board

Interface Type Select a board from the menu list.

9.3.5 Installing and Connecting INT-IP B (or IOIP) Board to the ACT Media Gateway
Note:
This section is not relevant for INT-IP3 boards.
The following procedure is applicable for both the INT-IP B and IOIP boards. The IOIP board is (physically) an INT-
IP2 board with no compressors (declaring the INT-IP2 board as an IOIP board in management gives it this
functionality).
1. On the INT-IP B board, specify Crystal shelf number with the "crystal number" switches. There are 8
switches each corresponding to a bit (pay attention to LSB and MSB).

Example Example
configuration: Shelf configuration: Shelf
No. = 10 No. =16
OFF ON OFF ON OFF ON
4 MSB 4 MSB 4 MSB
3 3 3
2 2 2
Shelf number configuration 1 1 1
OFF=0, ON=1 (binary coding) 4 4 4
3 3 3
2 2 2
1 LSB 1 LSB 1 LSB
2. In the Crystal shelf, install the INT-IP B board in the CPU slot as follows:
• Slot 1 in a 4-slot Crystal shelf (Voice Hub) or in a 9-slot Crystal shelf (WM1)
3. Connect the adapter to the INT-IP B board as follows:
• For 9-slot (WM1), 14-slot or 28-slot Crystal shelf: connect the 10/100 base T connector (ref 3BA
23243 AA) to the back panel of the INT-IP B board.
• For 4-slot Crystal shelf (Voice Hub): connect the 9-port module (VH PATCH PANEL INT-IP
MODULE/ref 3BA 23244 AA) to the patch panel.
4. Connect the adapter to the LAN with a straight RJ45 cable.
5. Install another board in the shelf (there must be at least one other board declared and in service in
the shelf for the INT-IP B board to initialize).
9.3.6 Installing and Connecting INT-IP3 Board to the ACT Media Gateway
1. Install the INT-IP3 board in the CPU main slot or standby.
Note:
The Voice Hub is not supported with INT-IP3.
2. Connect the 10/100/1000 base T (3BA23278AA) connector as shown in INT-IP3 - External
connections
3. Connect the adapter to the LAN with a straight RJ45 cable.
9.3.7 Starting the ACT Media Gateway

The Media Gateway start-up corresponds to INT-IP B board initialization. There are two possible
initialization processes:
• Static initialization: IP parameters are manually configured on the INT-IP B board. Static initialization
must be used if there is no DHCP server. It is also recommended for reasons of reliability so that
ACT Media Gateway operation is not dependent on DHCP server availability. See INT-IP B (or IOIP)
Board Static Initialization Process on page 142.
• Dynamic initialization (factory-fitted default process): IP parameters are automatically sent by a
DHCP server to the INT-IP B board. See INT-IP B (or IOIP) Board Dynamic Initialization Process on
page 144.
Notes:
• The two board initialization processes are common to the INT-IP B and IOIP boards.
• For INT-IP3 boards, only static initialization is allowed due to security constraints.
9.3.7.1 INT-IP B (or IOIP) Board Static Initialization Process

Note:
For INT-IP3 static initialization, see: INT-IP3 B Board Static Initialization Process on page 145.

9.3.7.1.1 Overview
1. The administrator configures the board IP parameters from a console connected directly to the front
panel of the INT-IP B board. The IP parameters to configure are:
• The INT-IP B board IP address
• The TFTP server 1 IP address
• The TFTP server 2 IP address
Note:
In a duplicated Call Server configuration, the addresses to enter in the TFTP server 1 and 2 fields are the
main IP addresses of the Call Servers as follows:
• When the two Call Servers are on the same IP subnetwork, the same main IP address can be used for
the two Call Servers. This one must only be entered on the TFTP server 1 field.
• When the two Call Servers are on different IP subnetworks, the two Call Servers main IP addresses
must be entered on the TFTP server 1 and TFTP server 2 fields.
2. The INT-IP B board downloads the lanpbx.cfg file from the TFTP server, this file contains the list
of Call Server IP addresses in the PCX network. For information on lanpbx.cfg generation, see
the lanpbxbuild - Operation (if the file does not exist on the PCX, it is created automatically).
3. The INT-IP B board sends a TFTP request towards the Call Servers IP addresses declared in the
lanpbx.cfg file.
4. The INT-IP B board downloads the binaries from the main Call Server.
5. The INT-IP B board sends a new TFTP request towards the two Call Servers main IP addresses.
6. The INT-IP B board downloads the startintip file from the main Call Server.
9.3.7.1.2 Starting the Static Initialization Process
To configure the board in static, access the board's main menu by connecting a console to the front
panel of the board:
1. Connect the V24 cable to the board:
• For INT-IP board, the cable reference is 3BA 28112.
• For INT-IP 2 board, the cable reference is 3EH 75003 AA.
• For INT-IP3 board, the cable reference is 3EH 75003 AA. For more information, see: INT-IP3 -
External connections - Connecting a Console for Static Configuration
2. Configure the console as follows:
• 9600 bps
• 8 N1
• Flow control XON/XOFF
3. When the message Hit ENTER key to suspend coupler boot processis displayed, press
Enter to display the main menu:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––
IP configuration Menu
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Available commands :
– view : display current IP configuration
– chmode : change IP Configuration Mode (Static/dynamic)
– chip : change Static IP Parameters
- chqual : Change default quality Parameters
– save : saved modified configuration
– reset : reset coupler
Use? or ? <cmd> to get help on Command

Config:
4. Enter chmode, then 1 to change the initialization mode to Static mode.
5. Enter chip and configure the following IP parameters:
• The INT-IP B board IP address,
• The IP subnetwork mask,
• The router IP address,
• The TFTP server 1 IP address,
• The TFTP server 2 IP address.
6. Enter save to save the parameters.
7. Enter reset to re-initialize the board.
8. To check initialization status, enter the command: Config <Shelf No.>
9.3.7.2 INT-IP B (or IOIP) Board Dynamic Initialization Process

Note:
The dynamic initialization process is not allowed for INT-IP3 boards (no DHCP server use). Only static initialization
is allowed due to security constraints.
9.3.7.2.1 Overview
1. At board start-up, the INT-IP B board sends a request to the DHCP server which returns the
following IP parameters:
• The INT-IP B board IP address,
• The IP subnetwork mask,
• The router address,
• The TFTP server address.
2. The INT-IP B board downloads the lanpbx.cfg file from the TFTP server, this file contains the list of
Call Server IP addresses in the PCX network. For information on lanpbx.cfg generation, see the
lanpbxbuild - Operation (if the file does not exist on the PCX, it is created automatically).
3. The INT-IP B board sends a TFTP request towards the Call Servers IP addresses declared in the
lanpbx.cfg file.
4. The INT-IP B board downloads the binaries from the main Call Server.
5. The INT-IP B board sends a new TFTP request towards the two Call Servers main IP addresses.
6. The INT-IP B board downloads the startintip file from the main Call Server.
9.3.7.2.2 Starting the Dynamic Initialization Process
Requirements:
• Before starting initialization, you must program on the DHCP server a static address (Ethernet
(MAC) address - IP address correspondence) for the INT-IP B board. The advantage of static
addressing is that the DHCP server always assigns the same IP address to the INT-IP B board at
subsequent start-ups. For more information: see DHCP server - Configuration procedure.
• If the DHCP server is internal to the Call Server, no address of TFTP server must be entered in
DHCP server configuration. The DHCP server provides the appropriate IP address of the Call
Server. In a duplicated Call Server configuration where the two Call Servers are on different IP
subnetworks, a DHCP relay must be activated on the IP subnetwork where the INT-IP B board is
located.
• If the DHCP server is external, the TFTP server address must be entered in DHCP server
configuration. In a duplicated Call Server configuration where the two Call Servers are on different
IP subnetworks, the TFTP server must also be external.
The INT-IP B board initialization starts as soon as the board is installed in the ACT Media Gateway.

Note:
If board initialization process has been changed previously and the board is set to static, it must be switched back
to dynamic using the IP configuration menu. This menu is accessible by connecting a console to the front
panel of the INT-IP B board. For more information: see Starting the Static Initialization Process on page 143.
9.3.7.3 INT-IP3 B Board Static Initialization Process

The administrator configures the INT-IP3 B board IP parameters from a console using the mgconfig
command.
1. Connect a console as shown in: INT-IP3 - External connections - Connecting a Console for Static
Configuration
2. Open a root session (by default the password is empty)
3. Enter the mgconfig command
The IP parameters to enter are:
• The INT-IP3 B board IP address
• The CS role address
• The CS redundancy role address
Note:
In a duplicated Call Server configuration:
• When the two Call Servers are in the same IP subnetwork, the same main IP address can be used for
the two Call Servers. This address must only be entered once in the CS role address field.
• When the two Call Servers are on different IP subnetworks, the duplicated Call Server main IP address
must be entered in the CS redundancy role address field.
4. Exit the mgconfig tool and exit the session
After configuration, the INT-IP3 B:
1. Sends a TFTP request towards the main IP addresses of the two Call Servers configured previously
2. Downloads the binaries from the main Call Server
3. Sends a new TFTP request towards the main IP addresses of the two Call Servers configured
previously
4. Downloads the startemg file from the main Call Server
9.3.8 Configuring the Address of the Passive Communication Server in the INTIP
board
If the ACT Media Gateway is rescued by a Passive Communication Server, the Passive
Communication Server address must be configured in the INT-IP board. To configure the address of
the Passive Communication Server in the INT-IP board, see Configuring the address of the Passive
Communication Server in the INTIP boards on page 88.
Note:
Do not use the role addressing (main IP address) to configure the IP address of the Passive Communication
Server in the INT-IP board.
9.4 Maintenance
9.4.1 Connecting to a Media Gateway
Telnet sessions are available on all INT-IP boards.

The Telnet server must be activated manually before opening a Telnet session. Activation and
deactivation of the Telnet server are performed with the mgconfig tool on INT-IP3 board. On INT-IP/
INT-IP2 boards, Telnet server activation is not performed via mgconfig, but via a command accessible
from the IP Configuration menu of the board.
The activation duration is either permanent or limited by a timeout configured in days.
In a duplicated Com Server configuration, Telnet sessions can be opened from the main Com Server
only, via the telnet_al command. In a single Com Server configuration, the telnet command can
also be used to open Telnet sessions. When the timeout expires, the Telnet server is closed and it is
impossible to open a new Telnet session. Opened Telnet sessions are not closed.
1. Activate the Telnet server on the corresponding board:
• On INT-IP/INT-IP2 boards, perform the following operations:
1. Connect to the board via the V24 port
2. When the message Hit ENTER key to suspend coupler boot process is
displayed, press Enter to display the main menu
3. Configure the Telnet server activation mode
4. Enter save to save modifications
5. Enter reset to reboot the board
• On INT-IP3 boards, perform the following operations:
1. Connect to the board via the V24 port (or cpl_online from the Com Server)
2. Open a session with the root account and run the mgconfig command
The Telnet server activation mode (open or close) is displayed in front of the option 13.
Telnet server
3. If the activation mode is set to close, select option 13. Telnet server
4. Select either 1: open or 2: open with timeout
6. Reboot the board
2. Open a session on the main Com Server
3. On the Com Server prompt, enter the telnet_al command
4. When the Telnet session is opened, enter your login and password
Note:
Use the admin account (default password: admin). On INT-IP3 boards, use the root account without password.
Note:
The Telnet server is limited to launching sessions. If this server is down, current Telnet sessions keep running.
9.4.2 Error Codes

In case of error, LEDs located on the front panel are lit up. For more information, see INT-IP3: INT-IP3 -
Hardware configuration
9.4.3 Board Boot Traces

Board boot can be traced on a console connected to the board front panel with a cable as described in
INT-IP B (or IOIP) Board Static Initialization Process on page 142. The trace gives information on
binary download, binary version, IP parameters, Call Server address, etc.
Example:
In this example, the address assigned by the DHCP server is 172.231.47.19.

------------------------------------------------------------------------------
Logical Board : INTIP B Main - Crystal 2 (Dynamic IP Configuration
using DHCP)
Physical Board : Revision 1 = AB (MPC8260 40MHz)
MuP : Version 0081 Revision 0101
Boot/download version : intip _04.03.0_03Dec01_11h29
Application version : intip _04.07.1_09Jan02_08h56
------------------------------------------------------------------------------
---> Hit ENTER key to suspend coupler boot process <---
INTIP:
5 sec left before starting coupler
Starting Coupler
00000004-000007E4: ConfigIP : Discovering our IP Parameters using DHCP
request
00000005-000007E4: DHCP : My Ethernet Address is 00:80:9F:04:9C:0E
00000006-000007E4: DHCP : Send DHCP_DISCOVER (Broadcast)
00000007-00000BCD: DHCP : Switch to state INIT_STATE
00000008-00000F6D: DHCP : Send DHCP_DISCOVER (Broadcast)
00000009-00000F6E: DHCP : Receive DHCP_OFFER from 172.231. 47. 1
0000000A-00000F6E: DHCP : This DHCP_OFFER comes from Alcatel 4400 DHCP
Server
0000000B-00000F6E: DHCP : DHCP_OFFER contain @IP 172.231. 47. 19 @TFTP
172.231. 47. 3
0000000C-00000F6E: DHCP : Switch to state REQUESTING_STATE
0000000D-00000F6E: DHCP : Send DHCP_REQUEST[0] [ServerId 172.231. 47.
3 ReqIP 172.231. 47. 19] (Broadcasts)
0000000E-00000F89: DHCP : Receive DHCP_ACK from 172.231. 47. 1
0000000F-00000F89: DHCP : Switch to state BOUND_STATE
00000010-00000F89: DHCP : Board IP Addr : 172.231. 47. 19
00000011-00000F89: DHCP : Subnet Mask : 255.255.255. 0
00000012-00000F89: DHCP : Router IP Addr: 172.231. 47.254
00000013-00000F89: DHCP : DHCP IP Addr : 172.231. 47. 3
00000014-00000F89: DHCP : TFTP IP Addr : 172.231. 47. 3
00000015-00000F89: DHCP : LEASE TIME : 86400 seconds
00000016-00000F89: DHCP : Start Timer [43200 , 75600 , 86400]
00000017-00000F89: ConfigIP : IP Parameters comes from DHCP server
172.231. 47. 3
00000018-00000F89: ConfigIP : IP Address : 172.231. 47. 19
00000019-00000F89: ConfigIP : IP Subnet Mask : 255.255.255. 0
0000001A-00000F89: ConfigIP : IP Default Router : 172.231. 47.254 ping
fd = 2
0000001B-00000F8C: Reset of Released Call Counters
0000001C-00000F8C: LANPBX : Download of the file 'lanpbx.cfg' from
server 172.231.47.3
9.5 INT-IP3 or IOIP3 board reloading

9.5.1 Overview
Flash memory reloading is required when:
• Flash memory is corrupted
• The board type is changed (switch between INT-IP3 and IOIP3).
Before being delivered, a flash memory is factory loaded for INT-IP3. Before installing an IOIP3
board, you must reload the flash memory.
The Alcatel-Lucent OmniPCX Enterprise Communication Server PC installer software application
(called PC installer in this document) is used to reload board flash memory.

Crystal hardware rack INT-IP3 or IOIP3 board

in CPU position
VT100
cable
Ethernet
cross cable
VT100 console
PC Installer
Figure 9.4: Flash memory reloading configuration
For more information on PC installer, see: Enterprise PC Installer - Commissioning - Overview.

For more information on board connexions, see: INT-IP3 - External connections - Ethernet Network
Connection
The deliveries are retrieved from the patches installed in the dhs3mgr directory of the machine hosting
the PC installer. At least one static patch must be available in this directory so that all types of binaries
are available for download.
9.5.2 Erasing and reloading a INT-IP3 board or a IOIP3 board

To proceed:
1. Insert the board in a CPU position (slot 6,10 or 20)
2. Connect the board to the PC installer with a Ethernet crossed cable
3. Copy (or verify the presence of) binary files on the machine hosting the PC installer application:
The INT-IP3 binary files (depending on the version) must be present in the /
dhs3mgr/"version"/pcmao/boot_res/DHS3bin/downbin/intip3 directory.
The IOIP3 binary files (depending on the version) must be present in the /dhs3mgr/"version"/
pcmao/boot_res/DHS3bin/downbin/ioip3 directory.
4. Start the PC Installer:
• For the INT-IP3 board, the PC Installer V2.26 or higher is required
• For the IOIP3 board, the PC Installer V3.3 or higher is required
a. In the Installation type field, select the GD/GA/GD3/GA3/INTIP3/IOIP3 binary option

Figure 9.5: PC installer interface example

b. In the Media Gateway board designation field, select the INTIP3 or IOIP3 option
c. Click Apply in the Installation parameters window.
The PC installer is waiting for board requests.
6. Connect a console to the Config. port of the board
7. Switch on the board and enter the BIOS menu:
Two seconds after power on, as soon as the prompt Press ^B^I to enter into the Bios menu is
displayed , quickly press CTRL + B and CTRL + I command.

Figure 9.6: Terminal traces after power on
Note:
On new generation board, you can skip this operation. The board automatically requires binary fields
automatically to the PC installer.
8. In the BIOS menu, select the 3 : Load from Ethernet option
The board erases flash memories, requests binary files from the PC installer, and loads it.
When the download is completed, the board restarts.
When the board is restarted, the mgconfig menu is displayed:

Figure 9.7: mgconfig menu

9. Configure IP parameters

Chapter
10 INTOF connections
10.1 Overview
The INTOF connection is used to connect a main ACT to a peripheral ACT. It has a capacity of four
PCMs (eight Mbps), and its length is limited (depending on the physical support used).

10.2.1 Connecting a Peripheral ACT by INTOF2 Boards
The INTOF2 board enables a main ACT to be connected to a peripheral ACT. The inter-ACT link is
composed of four PCMs (eight Mbps). The length of a link is limited, depending on the physical support
used:
• Copper line: maximum = 600m
• Multimode optic fiber: maximum = 5km
• Monomode optic fiber: maximum = 40km.
The INTOF link is possible behind:
• The main ACT with CPU
• Any other ACT on the INTOF2 board, as long as it is behind the main ACT with CPU.
Lev. 1
CPU
Main ACT
INTOF
A
INTOF
B
INTOF
A
Level 3 INTOF
Level 2
Peripheral B INTOF Peripheral
B
ACT ACT
Lev. 3
Main Zone
INTOF = INTOF or INTOF2 Board
Figure 10.1: Peripheral ACTs on INTOF Behind the Main ACT with CPU
• The figure below displays an ACT Media Gateway in the main zone, with an IOIP board behind
Appliance Server. Refer to Detailed description on page 159.

Chapter 10 INTOF connections
IP Network
IOIP
Lev. 1
INT- INTOF
IP A A
INTOF
B
INTOF
B
Lev. 2
Lev. 2 INTOF Links

Appliance Server
Main zone
Figure 10.2: Peripheral ACT on INTOF Behind an ACT Media Gateway and Appliance Server
10.2.2 Commissioning
The inter-ACT link is created using two boards. One is installed in the main shelf and acts as a coupler
(feature A). The other is installed in the peripheral shelf and acts as a CPU (feature B). The board
which has feature A is called INTOF2-A and the board which has feature B is called INTOF2-B.
The remote ACT is sometimes called URAD.
CPU
Main ACT
INTOF A
Inter-ACT Link
INTOF B
Peripheral ACT
Figure 10.3: Main ACT and Peripheral ACT Linked by INTOF

10.2.3 Duplicating the Inter-ACT Link

CPU
Main ACT
INTOF A
INTOF A
INTOF B
INTOF B
Peripheral ACT
Figure 10.4: Principle of the Duplicated Inter-ACT link
For security reasons, the inter-ACT link can be duplicated. Four INTOF2 boards are necessary for this.
In the peripheral ACT, the boards are situated in the same place as for the main CPU and the backup
CPU.
When both links are valid, the system uses the resources of both connections (the communication
capacity is doubled).
If the link with the board which provides the master CPU feature fails, the other link takes over and the
CPU feature switches over from one link to the other.
The capacity of the INTOF type link can be further increased by adding INTOF pairs declared as
INTOF A on both ACTs.
10.2.4 Reserving B Channels

The inter-ACT link has two operating modes, either with or without B channel reservation.
• Without B channel reservation:
Signaling is operational even when all B channels are busy.
• With B channel reservation:
Signaling is not operational unless there are free B channels.
The operating mode is defined in configuration.
10.2.5 Synchronization of INTOF2 Board

An INTOF link transports the synchronization signal, either from the main ACT to the peripheral ACT, or
vice versa.
This synchronization is compatible with the DECT/PWT handover. In a DECT/PWT multi-ACT
configuration, the INTOF/INTOF2 board allows DECT/PWT mobiles to benefit from the handover when
they move from one ACT to another (see the Multi-ACT DECT - Overview). In this case, the length of
the link is limited to 12km.

10.2.6 Tones, Voice Guides, and On-hold Music

The INTOF2 board does not have a tone generator. The tones are transmitted by the main ACT via the
inter-ACT link.
To use the voice guides for the peripheral ACT , a GPA2 board is required. If there is no such board,
the guides are replaced by tones.
External music can only be connected to the peripheral ACT via an analog link.
10.2.7 Trunks
The peripheral ACT can support trunk groups. In this case, subscribers of this ACT use the ACT's local
trunk groups as a priority.
When dealing with a multi-level architecture, only the level one and two trunks can be synchronizing
(not permitted for level three trunks).
10.2.8 Attendant
The attendant can be connected either on the main ACT or the peripheral ACT.
Incoming calls to the attendant (in transit on the inter-ACT link) do not reserve channels in call phase.
However, four channels are reserved for incoming calls to the attendant.
10.2.9 Voice mail

The voice mail can only be in the main ACT, but peripheral ACT subscribers can access it. A time slot
is seized on the inter-ACT link when a peripheral ACT subscriber connects.
If no channels are available to contact the voice mail it is declared “Unavailable”.
10.2.10 Callbacks
Automatic callback is only offered if the call fails because the inter-ACT link is saturated.
For groups: callback or camp-on is offered if no group members are available, either because they are
all busy or the inter-ACT link is saturated.
Before making a callback, the system reserves the B channels required. The callback is deferred if the
reservation fails.
10.3 Installation procedure

10.3.1 Installation Procedure
To install the boards, refer to [16].
Optic fiber connection is carried out using the COST board, which is placed on the backpanel behind
the INTOF2 board. Refer to [16].

10.4.1 Principle
To perform an inter-ACT link, it is necessary to:
• Declare the operation mode of the inter-ACT links of the node (concerning B channel reservation)

• Declare a peripheral ACT

• Declare an INTOF2 board in coupler position in the main ACT
• Declare an INTOF2 board in CPU position in the peripheral ACT.
10.4.2 Reserving B Channels

1. Select: System > Other System Param
B channel reservation Determines, for all the inter-ACT links of the node, whether or not B
channels need to be reserved in call phase.
10.4.3 Declaring the Peripheral ACT on INTOF

1. Select: Shelf
Shelf Address Enter the ACT number.
Shelf Type Select the type of shelf. All shelf types are suitable.
ACT Type Select Peripheral ACT Shelf.
Stand By CPU No
Signaling Mode Select the signaling mode used on the inter-ACT link:
• N64: signaling is transferred on N channels (speed N*64 kbps)
• TS16 (default position): signaling is transferred on TS16.
• IO2: signaling is transferred on 4*64kbps.
Note:
An IO2N board is recommended (for a CPU on ACT).
Signaling Channel N64 If the Signaling Mode is N64, enter the number of channels used
Size for signaling.
10.4.4 Declaring an INTOF Board on a Main ACT

1. Select: Shelf > Board
Shelf Address Enter the main ACT number.
Board Address Enter the position of the board (the board must be in coupler po-
sition).
Interface Type Select: INTOF2A
Country Protocol Type Not significant

Remote Shelf Address Enter the no. of the ACT at the other end of the inter-ACT link.
Remote Board Address Enter the no. of the board at the other end of the inter-ACT link.
Synchronization Priority Not significant
Voice-->Data TS Not used.

10.4.5 Declaring an INTOF2 Board on a Peripheral ACT

Shelf Address Enter the peripheral ACT number.
Board Address Enter the position of the board (the board must be in CPU posi-
tion).
Interface Type Select: INTOF2B
Country Protocol Type Not significant
Remote Shelf Address Enter the no. of the ACT at the other end of the inter-ACT link.
Remote Board Address Enter the position of the board at the other end of the inter-ACT
link.
Synchronization Priority Not used.
Voice-->Data TS Not used.

10.4.6 Declaring Duplicate Links

The two boards on the main ACT as well as on the peripheral ACT must be defined without making any
specific declaration. The system understands whether a main link or a backup link is used.
10.4.7 Consulting Board Status

This function allows the System Administrator to determine the status of the boards.
Shelf Address Enter the ACT no.
Board Address Enter the board position.
Interface Type INTOF2Aor INTOF2B depending on the case.
Usage State Not significant

Operational State Enabled or Disabled depending on the case.
Main/Standby State Main (Master) or Standby (Slave) depending on the case.

Caution:
On duplicated links:
• In the main ACT, both boards are always seen as Main (Master)
boards.
• In the peripheral ACT, only the board which acts as the main
CPU is seen as the Main (Master) board. The other board is
seen as a Standby (Slave).
10.5 Maintenance
10.5.1 Flashing and Downloading Procedure
The INTOF boards use “binintof” software which is installed in the flash memory. When the version is
upgraded or in case of accidental destruction, new software is downloaded from the CPU (whatever
the position of the board).
The download is performed automatically.
To perform a download, the board has a boot in the flash memory. This is deleted when the flash
memory is reset to zero (it is impossible to perform a partial reset of the flash memory). It is restored by
the download. However, if a reset occurs during this short period in time, the boot is lost. It must
therefore be restored.
Boot Recovery Procedure
When the boot is lost, it may be recovered by inserting the specific EPROM in the dedicated
motherboard connector.
It is also necessary to position the jumpers in "boot on EPROM" position:
• Jumper X17 on the INTOF board (see [16] )
Afterwards, insert the board into the shelf and the boot will automatically duplicate itself.
10.5.2 Maintenance Commands

The standard maintenance commands are available on the INTOF2.

Chapter
11 INTOF signaling link (IOIP INT-IP)

11.1.1 Detailed description
A Call Server can support peripheral ACTs linked via IP. These peripheral ACTs can support one or
several peripheral ACTs linked via INTOF.
Peripheral ACTs, directly connected to the Call Server, linked via IP, are called primary peripheral
ACTs. Peripheral ACTs, connected to the Call Server, via an ACT directly connected to the Call Server,
linked via INTOF, are called secondary peripheral ACTs.
Between primary and secondary peripheral ACTs a signaling link is established to transmit signaling
messages.

Chapter 11 INTOF signaling link (IOIP INT-IP)
Call Server
IP network
IP link
IOIP or
IOIP
INT-IP
Primary
peripheral INTOF-A INTOF link
ACT
(copper or optical fiber line)
INTOF-A
INTOF-A
INTOF
A
INTOF-B
INTOF
B INTOF-B
INTOF
B INTOF-B
INTOF
B
Secondary peripheral ACTs
Figure 11.1: Example of configuration with primary and secondary peripheral ACTs
The signaling link between the primary ACT and the secondary ACT can be:
• A mode 1 link. An INT-IP board controls this link (also called an n64 link).
With mode 1 link, signaling messages are sent from the INT-IP board to the INTOF-A board and
from the INTOF-A to the INTOF-B board.
In addition, the INT-IP board supports VoIP channels.
According to the hardware version, the INT-IP board can be an INT-IP2 board or an INT-IP3 board.
• A mode 2 link. An IOIP board controls this link which is also called an IO2 link.
With mode 2 link, signaling messages are sent directly from the IOIP board to the INTOF-B board.
Signaling traffic goes through the INTOF-A board, without being processed.
The IOIP board is an INT-IP board loaded with a specific firmware. This firmware is loaded in the
flash memory of the board.

An IOIP board cannot support voice communication. VoIP channels require an additional INT-IP
board.
According to the hardware version, the IOIP board is:
• An IOIP2 board when the INT-IP2 hardware is used.
• An IOIP3 board when an INT-IP3 hardware is used.
For more information on INT-IP3 board, see: INT-IP3 - Hardware description - Overview.
Signaling link Signaling link

mode 1 or n64 mode 2 or IO2
Call Server Call Server
IP network IP network
IP link IP link
INT-IP
INT-IP
B IOIP
IOIP
4x64 kbps signaling 4x64 kbps signaling

link link
Primary Primary
peripheral peripheral
ACT ACT
INTOF-A
INTOF
A
8Mbps multiplex
INTOF-A
INTOF
A
link
INTOF-B
INTOF
B INTOF-B
INTOF
B
Secondary Secondary
peripheral peripheral
ACT ACT
Figure 11.2: Secondary signaling link configurations
11.1.2 Duplication / switchover

The Call Server, IOIP board, and INTOF boards may be duplicated.

Call Server
Call Server
(stand-by)
LAN
IOIP
IOIP
IOIP
IOIP
main
main
INTOF
Peripheral ACT stand-
Stand-by
INTOF
A
A
by
(main)
INTOF
INTOF INTOF
INTOF
A A A
A
INTOF
INTOF INTOF
INTOF
A A
A A
INTOF
INTOF
A
A
INTOF
INTOF
INTOF
INTOF
INTOF
INTOF
B
B B
B B
B
INTOF
INTOF
INTOF
INTOF
INTOF
INTOF
B B B B B B
Peripheral ACT Peripheral ACT Peripheral ACT

(secondary) (secondary) (secondary)
Figure 11.3: Redundant configuration
In the event of a switchover, the process is as follows:

• Call Server switchover: the signaling link is maintained
• IOIP board switchover: the signaling link is reset (all peripheral ACTs located "behind" the board are
affected)
• INTOF board switchover:
When the INTOF link is secured with an INTOF backup link, the signaling link is transmitted via the
main link and voice channels are shared between main and standby links.
When the main INTOF link fails, the signaling link is reset and calls established via the main INTOF
link are broken.
The IOIP3 board is compatible with the PCS (Passive Communication Server). In case of Call Server
link failure, a PCS can rescue an IOIP3 board.
11.1.3 Additional features

The IOIP3 board can provide synchronization for a DECT infrastructure.

The IOIP3 board supports encryption of the signaling link.

For more information on IOIP3 board encryption, IP Touch Security - Installation procedure - Securing
a Media Gateway without MSM (MGSec or SoftMSM).
11.2 Restrictions
11.2.1 Restrictions
To configure mode 2 signaling:
• The Call Server must be an Appliance Server
• Between the main ACT and its peripheral ACTs on INTOF: only one ACT in the entire node can host
the IOIP board
• An IOIP board can support up to 12 secondary peripheral ACTs
• An IOIP3 board can support up to 8 secondary peripheral ACTs
Restrictions on the IOIP board:
• The board declared as IOIP must be an INT-IP2 board (INT-IP and INT-IP3 hardware cannot be
used)
• The board declared as IOIP3 must be an INT-IP3 board (INT-IP and INT-IP2 hardware cannot be
used)
When an INT-IP3 board is declared as IOIP3, the first initialization of the board must be done by
reloading IOIP3 firmware with PC installer (see: Flash memory reloading on page 165)
• The board has no compressors
• It does not provide an H323 gateway
• It cannot be used to connect IP-Phones
• It is not possible to mix IOIP boards and IOIP3 boards on the same system

11.3.1 Configuration procedure
11.3.1.1 Configuring a peripheral ACT (primary)
1. Select: Shelf
Shelf Address Enter the primary peripheral ACT number.
Shelf Type Select the shelf type according to your hardware:

• ACT-14 Interface
ACT Type Select Peripheral ACT Shelf
Signaling Mode Select N64


11.3.1.2 Configuring the controller board

Shelf Address Enter the ACT number (as declared: Configuring a peripheral
ACT (primary) on page 163)
Board Address Enter the slot number

This slot must be a CPU slot (also called controller position)
Interface Type Select:

• IOIP when an INT-IP2 hardware is used
• IOIP3 when an INT-IP3 hardware is used
Note:
When the board type is modified, the board flash memory must be
reloaded. For more information, refer: Flash memory reloading on page
165.
Board IP Version IP Default

11.3.1.3 Configuring a peripheral ACT (secondary)

1. Select: Shelf
Shelf Type Select the shelf type according to your hardware:

ACT Type Select Peripheral ACT Shelf
Signaling Mode Select:

• IO2 when the signaling link is controlled by an IOIP board.
• n64 when the signaling link is controlled by an INT-IP board.
11.3.1.4 Signaling link control

The signaling link becomes operational once the INTOF B board of the peripheral ACT (secondary) has
been initialized.
You can check the signaling link with:
• The infocs command to check the synchronization
• Use the ioipdisplay command to display links between the call server and remote INTOF B

11.3.2 Flash memory reloading

INT-IP3 and IOIP3 boards share the same hardware but their flash memory are loaded with a specific
firmware.
The PC installer application is used to reload board flash memory.
Flash memory reloading is required when:
• Flash memory is corrupted
• The board type is changed (switch between INT-IP3 and IOIP3)
Before being delivered, a flash memory is factory loaded for INT-IP3. Before installing an IOIP3
board, you must reload the flash memory.
For more information on flash memory reloading, see: Overview on page 147.

Chapter
12 Signaling link backup
12.1 Overview
12.1.1 Overview
The “Signaling link backup” feature (also called "survivability") is used to back up signaling between a
Call Server and Media Gateway. This service is designed to ensure limited phone operations on a
remote Media Gateway (connected by a WAN) in case of a failure of the IP network connecting the
sites.
The service only allows OmniPCX Media Gateways to be backed up ("rescued") via the public
telephone network.
The service does not provide IP link backup.

12.2.1 Basic Description
This service is used to back up the signaling between the Call Server and Media Gateway on a remote
site. The Media Gateways on the local site are not concerned by this service: the local network is
considered to be sufficiently reliable.
Site 1
Rescuer MG
Call Server
Signaling backup
Router PSTN
WAN
Router
Rescued MG
Site 2
Figure 12.1: Signaling Link Backup Setup
The Call Server monitors the links with each Media Gateway via a "keep alive" dialog. Interruption of
this dialog informs the Call Server that a failure has occurred. The Call Server then attempts to reach
the isolated Media Gateway, using modems on the public telephone network.

Chapter 12 Signaling link backup
Note:
A “keep alive” dialog is used to ensure mutual monitoring between two machines. Messages are constantly being
sent back and forth between the two machines. Each exchange is monitored by a timer. A machine detects the
interruption of its "twin" when the monitoring timeouts elapse.
The backup link is not an IP flow backup. This link only ensures phone signaling backup of sets
assigned to this media Gateway. The service provided on this rescued Media gateway is limited.
For the "Signaling link backup" feature, there are the following types of Media Gateways:
• Rescuer Media Gateway: This Media Gateway is able to set up a call to an isolated Media
Gateway. The rescuer Media Gateways are located on the Call Server site (connected by an LAN)
A rescuer Media Gateway can only back up a single Media Gateway at a time (since it has only one
modem).
• Rescuable Media Gateway: Media Gateway operating on its nominal IP link, but configured to be
back upped in the event of a network failure.
• Rescued Media Gateway: Media Gateway effectively back upped after a failure of its nominal IP
link.
Useable devices (equipment):
Call Server: The Call Server may be supported by a CS board, an Appliance server, or an ACT CPU.
The OmniPCX Media Gateways may be rescuer or rescuable type.
ACT Media Gateways are neither rescuer nor rescuable type.
Caution:
Any problem that breaks the IP link between an OmniPCX Media Gateway and Call Server results in
switchover to the backup link. For example, disconnection of the GD board cable results in switchover.

12.3.1 Preliminary Configuration
On the Call Server site, the manager declares one or more rescuer Media Gateways. The Call Server
can use these machines to set up a backup link. These Media Gateways have an internal modem and
direct access to the public telephone network.
Remote Media Gateways, which can be backed up, are declared rescuable. For each one of them, you
must specify in management the call number via the public telephone network. The signaling of this link
to the telephone network must be one of the types listed (see the Configuration procedure on page
171).
The “Signaling link backup” feature is only supported by T0, T1 and E1 digital interfaces. The MG must
be connected to the public network by one of the following boards:
• PRA-T2
• PRA-T1 (CCS)
• T1-CAS
• BRAx
• MIX-xxx
Note:
Signaling backup is presented in this document as using a switched public telephone network. However, nothing
prohibits the use of an equivalent private network.

12.3.2 Switchover to the Backup Link

When the Call Server observes the interruption of a "keep alive" dialog with a Media Gateway, it waits
for a certain time (specified in management). When this time has elapsed, it declares the nominal link
failed and initiates the backup link activation procedure.
This procedure is performed as follows:
• On the Call Server side:
• Search for a free rescuer Media Gateway.
• The internal modem of the rescuer Media Gateway calls the isolated Media Gateway at the
number defined in management.
• On the Rescued Media Gateway side:
• The isolated Media Gateway, having observed the failure of the nominal link, performs a reset.
All calls in progress are then lost.
• The isolated Media Gateway is rebooted in "backup link" mode; it activates exclusively the
backup access (specified in management) and waits in reception mode on this access. "Backup
link" mode is a simplified operational mode that processes signaling on the backup access.
Incoming calls on the backup access are systematically directed to the internal modem of the Media
Gateway. The dialog with the Call Server is re-established and calls are accepted again.
12.3.3 Restrictions in Rescued (Backup) Mode

Call restrictions:
Each rescuable Media Gateway must have its own IP domain. This domain includes:
• The rescuable Media Gateway itself.
• The IP-Phones connected to it.
Note:
If a remote site has two rescuable Media Gateways, two backup links and two IP domains must be planned.
Outgoing calls from the rescued Media Gateway are limited to the IP domain of this Media Gateway.
That is to say:
• Calls cannot be made with other sites.
• Calls cannot be made with other Media Gateways (including the Media Gateways on the same site).
• Calls cannot be made with IP-Phones that do not belong to the same IP domain.
The only operations that remain possible are:
• Calls with other sets of the same Media Gateway (static sets, connected IP-Phones, DECT or PWT
mobiles).
• External telephone networks (public or private).
Note:
It is possible to bypass these restrictions by making calls via the public network.
Caution:
Restriction on the duration of rescued (backup) mode
Some public operators release calls after a certain lapse of time. This is the case, for example, in France
on the T0 ISDN support after 18 hours of calls.
Restriction on voice mail:
The voice mail service can no longer be reached for rescued Media Gateway subscribers.
Restriction on internal applications:

Internal applications (accounting, hotel, call center, etc.) operate from the rescued Media gateway, if
these applications do not require an IP link between the rescued Media Gateway and the Call Server.
12.3.4 Return to Normal

In "Backup link" mode, the Media gateway periodically consults the IP network. When the IP network is
re-established, the Media Gateway waits for a certain time to ensure that this re-establishment is
stable. After this time, the Media gateway switches Call Server signaling over to the nominal link. The
restrictions related to the backup link no longer apply. The backup link, which is now no longer
required, is cut off. Calls in progress are not interrupted.
12.3.5 Rescuable and Rescuer Media Gateway

A Media Gateway may be both rescuable (as it is located on a remote site that can be rescued) and
rescuer (as it can also be used for backup).
Public telephone
network
Backup link
Site 1
Call Server
Router
Site 2 Router
Site 3
Router
WAN
Figure 12.2: Rescuable and Rescuer Media Gateway
In the above example, no rescuer GD is available on the main site. The system can search for a
rescuer GD on another site.
12.3.6 Interaction with the RMA Service

As the "e-RMA" and the "Signaling link backup" services use the same internal modem, an access
conflict may occur (rescuer Media Gateway and rescued Media Gateway). If you want to avoid
conflicts, you must prohibit (in management) the e-RMA service on this Media Gateway.
12.3.7 Interaction with Call Server Duplication

The backup link is maintained during a Call Server switchover.
Special case of a "double main" (see the Overview on page 43)
In a "double main" situation, each Call Server will attempt to reach, via signaling backup, the rescuable
Media Gateways that cannot be reached on IP. These attempts are rejected. The Media Gateway is
already controlled by a main Call Server.

Main IP links Main

cut off
Call Server Call Server

IP Network
Media
Gateway
Media
Gateway New
IP links
Media
Gateway
Media
Media Gateway
Gateway Public Network
MG rejected
Attempt to set up signaling

link backup
Figure 12.3: Signaling Backup and "Double Main"
12.3.8 Interaction with IP-Phones

The switchover to the backup link of a Media Gateway triggers the reset of the IP-Phones that are
connected to it. A detailed description of IP-Phone behavior is presented in the IP-Phones - Overview.
The “lanpbx.cfg” file, required for loading, must only refer to the host Call Server (and possibly the
backup Call Server). For more information on the “lanpbx.cfg” file, see lanpbxbuild - Operation.
12.3.9 Interaction with the DHCP Server

When the WAN IP network is out of service, the OmniPCX Media Gateway switches to backup
signaling mode. This mode does not back up the IP link. The GD board and IP-Phones cannot reach
the DHCP server located on the Call Server. Their DHCP requests remain unanswered and restart is
blocked. There are two solutions:
• Declare IP-Phones and the GD board in static mode.
• Use a local DHCP server. This must specify, for IP-Phones, that the OmniPCX Media Gateway is
the TFTP server to be used.
12.3.10 Recommendations for Installation of a Secure Link

On a strictly functional level:
• The Call Server must be able to reach the rescuer Media Gateway via IP.
• The Call Server must be able to reach the rescuable Media Gateway via IP.
• The rescuer and rescuable Media Gateways must be able to reach each other via the public
telephone network.
However, to ensure maximum security, the installation technician must be careful to:
• Make sure that there are reliable links between Call Server and rescuer Media Gateways.

• Create an IP domain for each rescuable Media Gateway.

• Make the backup link on the rescued Media Gateway synchronizing. This configuration allows better
data transfer on the backup link.

12.4.1 Declaring the Rescuer Media Gateways
For a Media Gateway to be "rescuing" (or "rescuer"), its GD board must be declared "rescuing".
Shelf Address Enter the rescuer Media Gateway number.
Board Address Enter 0 (address of the GD board in the shelf).
Interface Type Reminder of the type of interface: GD or GD3.
eMG rescue Select whether (Yes or No) the Media Gateway is rescuer.
e-RMA feature Select whether (Yes or No) the Media Gateway accepts remote
maintenance on the e-RMA.
Caution:
Beware of a possible access conflict with the "Signaling link
backup" feature.
12.4.2 Declaring the Rescuable Media Gateways

For a Media Gateway to be rescuable, you must declare a backup signaling channel.
1. Select: Shelf > Board > Signaling Link Backup
Shelf Address Enter the rescuer Media Gateway number.
Board Address Enter 0 (address of the GD board in the shelf).

Backup Call Number Enter the rescuable Media Gateway call number.
This number results from the concatenation of:
• The seize prefix for the trunk group to the external network.
This prefix must be a "Professional trunk group seize" prefix.
• The call number of the rescuable Media Gateway in the
external telephone network.
Note:
It is precisely the existence of this number which indicates that the
Media Gateway is rescuable.
Note:
To delete this number enter "".
Caution:
The trunk group for access to the external network must be located
in the main rack of the Media Gateway.
Caution:
In this case, the ARS prefix cannot be used.
Backup Address In the three following parameters, the manager defines the ac-
cess on which the Media Gateway must wait for reception.
Shelf Enter shelf number
Board Enter board number
Terminal Enter the number of the access.
Signaling Link Type Select the type of signaling of the backup link at the level of the
Media Gateway. The following types of signaling are possible:
• T0
• T2
• T1 CCS
• T1 CAS
Call Attempts Enter the number of attempts to connect before abort. Default
value: 3.
Delay Between Calls Enter the delay between two attempts (unit: seconds). Default
value: 120s.
Delay Between TFTP Re- Enter the delay between two TFTP requests (unit: seconds). De-
quests fault value: 60s.
Delay for Recovery/Restoral Enter the correct operating time of the IP link before declaring the
final re-establishment of the nominal link (unit: seconds). Default
value: 60s.
Delay for First Retransmis- Reserved for Technical Support.

sion
Delay For Retransmission Reserved for Technical Support.

Delay For Keeping Alive Reserved for Technical Support.
Delay for UDP Lost Reserved for Technical Support.
Delay for UDP Lost Enter the expected number of digits in the called party address
received with the call setup message.
This information allows filtering to be performed and undesirable
calls to be eliminated.
12.4.3 Synchronizing Access

On the rescuable Media Gateway, if you use a potentially synchronizing digital access, this access
must be synchronizing while other accesses must not be synchronizing. For more details on this
command, refer to the PCX Synchronization section of the document [6].
12.4.4 IP Domain
Each rescuable Media Gateway must have a specific IP domain. The IP-Phones connected to this
Media Gateway must belong to the same IP domain. For more details on IP domains, refer to the IP
Telephony Domains section of the document [7].
12.4.5 Timers
Timers No. 302 and 305 are used for signaling link backup. For more information on these timers, see
the List of timers on page 346.
12.5 Maintenance
12.5.1 The "bckdebug" Command
This command provides information on signaling link backup.
12.5.1.1 Main Menu

xxxxx> bckdebug
----------------------------------------------------
CALL SERVER : Config tool for back up signaling link
----------------------------------------------------
Display the signaling link back-up information : 1
Display the information about neqt x : 2
List all used fictious Z : 3
List timers for back-up DL : 4
Modify timers for back-up DL : 5
Check management consistency : 6
Activate back up calls : 7
----------------------------------------------------
Quit this tool : 0
Enter your choice :
12.5.1.2 Displaying Signaling Link Backup Information

Enter your choice : 1
Enter the crystal number : 3
INFORMATION FOR BACK UP LINK ON eMGD (3 0)
neqt_phant_cpl = 4575 (1)
********************************************
current status :SIG_BACKUP_ENABLE (2)
this MG can be rescued :SIG_BACKUP_ENABLE (3)

==> 0 attempt(s) of 5 (4)

********************************************
neqt of the calling fictitious z : -1 (5)
PROBLEM : can not access to information about neqt -1 (6)
********************************************
associated modem nulog : 3840 (7)
calls_attempts : 5 (8)
delay_between_calls : 60 (9)
delay_between_TFTP_req : 5 (10)
delay_for_resurrection : 20 (11)
Back up call number : [1..30] = 0 1 1 4 3 1 3 0 0 (12)
Back up access on CPL_PRA : (3, 3, 0, 255) (13)
********************************************
********************************************
=> Management consistency OK (14)
********************************************
Itemized list of the various fields:

1. Phant equipment number (reserved for Technical Support).
2. Current status of the backup link. Possible statuses are:
• SIG_BACKUP_DISABLED: the backup link is not configured.
• SIG_BACKUP_ENABLE: the backup link is configured but not enabled.
• SIG_BACKUP_STARTING: the backup link is being set up.
• SIG_BACKUP_ACTIVATED: The MG is rescued and the backup link is active.
• SIG_BACKUP_RESCUING: The MG is rescuer and the link is active.
3. Signaling link configuration. This configuration can be:
• SIG_BACKUP_DISABLED: on this MG the backup link is not configured, which implies that this
MG cannot be back upped (rescued).
• SIG_BACKUP_ENABLE: the backup link is configured.
4. Number of attempts to reach this MG.
5. Modem device (equipment) number.
6. The message "PROBLEM: can not access to information about neqt -1”, means that no rescuer MG
backs up (rescues) this MG.
The message "RESCUER: Board (4,0)”, means that the designated MG is back upped by MG (4,0).
7. Logical number of the associated modem (reserved for maintenance).
8. Reminder of the value configured for the number of attempts to establish backup.
9. Reminder of the value configured for the time between attempts.
10.Reminder of the value configured for the time between TFTP requests.
11.Reminder of the value configured for the "return to normal" time.
12.Reminder of the value configured for the call number of the backup link.
13.Reminder of the value configured for the backup access. The type of coupler (board) is indicated.
The value 225 means that, at the time of the command, there is no busy trunk in the backup
context.
14.The message "Management consistency OK", indicates that the configured parameters are
compatible.
• The trunk group seize prefix is correct.
• The trunk group used for backup exists.
• Signaling is compatible.
The message “NO BACK UP SIGNALING LINK MANAGED FOR THIS MEDIA GATEWAY”,
indicates that the MG cannot be back upped.
12.5.1.3 Display the Information about neqt x

Displays information on a device (equipment). This submenu is used for the internal modem.

Enter your choice : 2

Enter the equipement number : 3
INFORMATION ABOUT Z_MG NEQT 983 IN POSITION (2, 3, 1) :
********************************************
associated_cr : 4
associated_cpl : 0
associated_pos : 254
associated_ts : 126
emgd_neqt : 4575
modem_state : MODEM_OUT_DIALING (3)
ip_mode : 0
********************************************
Modem state: status of the modem. This can be:

• MODEM_AVAILABLE: idle state
• MODEM_OUT_DIALING: dialing
• MODEM_WAITING _FOR _INCOMING_CALL: in reception mode
• MODEM_CONNECTED: connected
• MODEM_DISABLE: out of service
12.5.1.4 List all Used Fictious Z

List of modems in use.
12.5.1.5 List Timers for Backup DL and Modify Timers for Backup DL
To display and modify timers. Reserved for maintenance.
12.5.1.6 Check Management Consistency

To check management is consistent. Checks that:
• The trunk group seize prefix is correct.
• The trunk group used for up exists.
• Signaling is compatible.
12.5.1.7 Activate Backup Calls

Reactivates calls. This command is used to reactivate calls to set up the backup link.
12.5.2 The “trkstat” <ACT_nbr> <Cpl_nbr> Command

This command allows the use of the TSs of a trunk group to be viewed. This command must be run on
the rescued Media Gateway.
(1)OXE0> trkstat 4 3
+----------------------------------------------------------------–––--+
+----------------------------------------------------------------–––--+
| T R U N K S T A T E PRA T Coupler Crystal Nbr = 4
|
| IN SERVICE Coupler Nbr = 3
|
+-----------------------------------------------------------------––––+
| Type : T1 CCS Access 0 : ENABLE level2 : INIT_T2
|
| B channel rate : 64K
|
|
|
| Trunk Grp 50 50 50 50 50 50 50 50 50 50 50 50
|
| Channel 1 2 3 4 5 6 7 8 9 10 11 12
|
| State Cr F F F F F F F F F F F
|
|
|

| Trunk Grp 50 50 50 50 50 50 50 50 50 50 50
|
| Channel 13 14 15 16 17 18 19 20 21 22 23
|
| State F F F F F F F F F F F
|
|---------------------------------------------------------------------|
| F : Free | B : Busy | Ct : busyComptrunk | Cl : busy Comp link |
| | Cr : busy Comp trunk for RLIO inter-ACT link |
|---------------------------------------------------------------------|
| ALARMS COUNTERS |
|---------------------------------------------------------------------|
| LMFA | RAI | LFA | AIS | LOS | MIC_LOOP |
| 0 | 0 | 0 | 0 | 0 | 0 |
|---------------------------------------------------------------------|
| LMFA : Loss of Multi Frame Alignement| RAI : Remote Alarm Indication|
| LFA : Loss of Frame Alignement | AIS : Alarm Indication signal|
| LOS : Loss Of Signal | |
|---------------------------------------------------------------------|
State = “Cr”: means busy with an inter-Media Gateway backup link.
12.5.3 Incidents (Error messages)

The "Backup signaling link" feature may generate the following incidents:
• Incident 417: this incident is transmitted as soon as the backup link is activated.
• Incident 418: this incident is transmitted on return to the nominal IP link.
• Incident 419: this incident is transmitted during the first attempt to set up the backup link.
• Incident 420: this incident is transmitted during the first or the last failure to set up the backup link.
The "error" field indicates the cause of this failure:
• error 1: no trunk group available to send a call to the MG (trunk group busy, out of service, not
authorized).
• error 2: the system does not recognize the trunk group seize prefix.
• error 3: no trunk group corresponding to the prefix.
• error 4: trunk group signaling is not authorized.
• error 5: modem unavailable on the rescuer MG.
• error 6: no response from the MG to be rescued.
• error 7: communication problem with the MG during its re-initialization.
• error 8: the maximum number of connection attempts has been reached.
• error 9: modem connection failure or unacceptable connection characteristics.
• error 10: Call Server switchover interrupted the backup signaling connection attempt.
• error 11: unexpected event.
• Incident 421: this incident is transmitted when the system refuses connection of modems as these
are running in a mode other than “V42 with error control”.
• Incident 423: for a Call Server on an ACT CPU, this incident is transmitted when no INTIPA board is
available to host the CPU – rescuer Media Gateway link. The link is then set up on the CPU's local
access.
• Incident 2091: this incident is transmitted when the backup link does not synchronize the Media
Gateway.
• Incident 5857: this incident is transmitted when a Media Gateway restarts. “Reason” code 20
indicates “Backup configured but invalid (DHCP mode is configured)”.

Chapter
13 Private to public overflow between

IP media gateways
13.1 Overview
13.1.1 Overview
In case of failure or congestion of the IP network between two sites of a same node, the feature Local
private to public overflow between Media Gateway allows the use of the public network to establish
a communication.
Call Server
Normal Route
IP Network
IP Domain 1
IP
Failure IP Domain 2
MG1
MG2
Overflow Route
61001
62001
A dials 62001 Public

Network B
Figure 13.1: Example of Overflow
In this example, A calls B. The IP network is not available. The call is automatically routed through the
public network. The level of service provided is the ISDN level of service.
An overflow can be required for the following reasons:
• IP link failure
• Inter domain call saturation
• No compressor is available
In case of IP link failure, for the overflow to operate, the Media Gateway must be rescued in one of the
two following ways:
• By a backup signaling link between the Call Server and the Media Gateway
• By a Passive Communication Server
This feature needs the following architecture:
• The node consists in several remote sites linked by an IP network
• Each site consists in one or more Media Gateway
• Each site consists in one IP domain
• Each media gateway has its own signaling link backup, when the IP network is down.
• Each site has is own public network access

Chapter 13 Private to public overflow between IP media gateways
• Overflow to DID user is automatic. Overflow to non DID user is possible but not automatic. In case
of overflow to non DID user, the overflow is done to a third party located in the destination domain.
The service Local private to public overflow uses the following features:
• The IP domain, see: IP telephony domains - Overview
• The DID (Direct Inward Dialing), see: Numbering conversion - Overview
• The ISDN trunk group, see: ISDN T0/T2 (CCS on E1 boards) - Overview
• The ARS feature used to find out the right trunk group to use. For more details on ARS, see: ARS -
Overview
• The signaling link backup, see:Overview on page 166
• Passive Communication Server, see: Overview on page 68

13.2.1 Steps of an Overflow
3 4 5 Call
Server
IP Failure
IP Network
2
Domain Domain Domain

D1 D2 D3
Trunk Group 1 Trunk Group 2 Trunk Group 3

1 01 23 45 1x xx 01 23 45 2x xx 01 23 45 3x xx
Public
61001 ISDN Overflow Route 63001
Network
Figure 13.2: Example of Overflow
13.2.1.1 Overflow to a DID Set

1. The calling party (61001) dials the destination number: 63001, located in domain 3
2. There is no resource available to reach domain 3. An overflow is required
3. The system checks the right to overflow of the calling party (61001).
Note:
If this parameter is set to No, then the call is rejected.
4. The system builds the called party public number with the following configuration data:
• The prefix to add. For this example node: 0
• The node DID translation table. In this table, the internal number 63001 (DID number) is
associated to the public number 01 23 45 30 01

For DID numbers, the translator assigns one public number to one DID number. All DID internal
numbers are translated into an external number.
The number built is 0 01 23 45 30 01.
5. 0 must be the ARS prefix. The ARS process is invoked
6. The ARS process is configured as follow:
For the public number 01 23 45 30 01 there are two possible routes:
• The first route uses trunk group 1
• The second route uses trunk group 2
In this example, the calling party is located in domain 1, trunk group 1 is available. Trunk group 1 is
used.
13.2.1.2 Overflow to DID Set from Domain 2

For a call from set 62001 belonging to domain 2, steps 1 to 5 are the same.
In step 6, the first route through trunk group 1 is not available. The ARS tries route 2 through trunk
group 2. In domain 2, trunk group 2 is available. Trunk group 2 is used.
13.2.1.3 Overflow to a Non DID Set

When the calling party 61001 calls a non DID set (63555) located in domain 3, steps 1 to 3 are the
same.
In step 4, all non DID numbers are translated to a unique number. This unique number is the set
number (DID) of the domain attendant.
Steps 5 and 6 are the same.
All non DID internal numbers are translated into the same external number.
13.2.1.4 Overflow to a Set Rescued by a Passive Communication Server

The Communication Server sees any set that belongs to an IP field rescued by a Passive
Communication Server as Out of Order.
The system must check whether overflowing on a set which is out of order is authorized or not.
13.2.2 Interaction with the Routing Service Intelligence

As of R8.0.1, the private to public overflow feature can be used by the Routing Service Intelligence
(RSI) interface for call processing in the event of IP link congestion or failure.
The right to private to public overflow is defined in the RSI feature class of service and not in the set's
phone feature class of service of the calling party.
Incoming Call routing in the RSI can be interrupted, when the IP link with the called party fails or is
satured. When this situation occurs and the RSI enables private to public overflow, call can be
redirected to the called party using the public network. The called party can be a business set, a
hunting group, an attendant, or an attendant group.

Com
Server
Messages
RSI exchange
Normal route Call in the RSI CTI Application
IP Network
IP Failure
Domain Domain
D1 D2
User B
Public
Network
User A Overflow route
Figure 13.3: Example of Call Overflow to the Public Network
In this example, a user A from IP domain 1 calls a local RSI. A route request is sent to the CTI
application, which returns a route select message to RSI. RSI, in turn, routes the call to a user B
belonging to IP domain 2. In the mean time, a failure or saturation is detected between IP domains 1
and 2.
Two scenarios can occur:
• The RSI does not authorize private to public overflow. In this case, the call is not distributed to user
B.
According to the call routing strategy applied within the RSI, a reroute request or an end of
service notification is sent to the CTI application with the following reason: resource not
available
• The RSI authorizes private to public overflow. In this case, the call is routed from the RSI to user B
through the public network, using the same overflow mechanisms as described in: Steps of an
Overflow on page 178.
If the local private to public overflow succeeds, an end of service notification is sent to the CTI
application. If this is not the case, according to the call routing strategy applied within the RSI, a
reroute request or an end of service notification is sent to the CTI application with the reason for
call failure
Note:
For more information on the RSI routing mechanisms and messages exchanged, see the Routing Service
Intelligence - Standard Edition documentation.
13.2.3 Accounting
One accounting ticket is created per overflow call. In this ticket, the Obtaining mode field is set to
overflow. For more details on Accounting, see: [10].

13.2.4 Former Releases Compatibility

As of R6.1, the maximum number of node DID translation tables is increased from 32 to 200.
These tables are broadcast to the other nodes of the same ABC network. When more than 32 tables
are sent to a node in a former release, a number of tables are lost.
When there are less than 32 node DID translation tables, it is possible to have nodes in former
releases.
When there are more than 32 node DID translation tables, all network nodes must be in release R6.1
or higher.
13.2.5 Restrictions
The service provided by the Local Private to Public Overflow between IP Media Gateway is not a
virtual private network as carried out by the feature VPN Overflow (see: [6]). The service provided is
similar to that of Overflow on public network (see: [6]).
The service provided by the overflow is limited to the services of the public network (e.g. ISDN
services). In case of overflow, ABC-F2 services are no longer provided. For example, a forward on
voice mail is displayed for an internal call and not for an overflow call.

13.3.1 Principle
To configure local private to public overflow:
• Configure IP domains, see: IP telephony domains - Overview
• Configure one trunk group per domain to access the ISDN network, see: ISDN T0/T2 (CCS on E1
boards) - Overview
• Grant users the right to overflow
• Define the node access prefix
• Define DID translation tables
• Configure the ARS feature. The use of ARS is mandatory to determine which trunk group to use.
For more details on ARS, see: ARS - Overview
13.3.2 User Right to Overflow

The user right to overflow is defined in the set's phone feature class of service. For Routing Service
Intelligence (RSI), the right to overflow is defined in the RSI's phone feature class of service.
1. Select: Classes of Service > Phone feature COS
2. Review/Modify the following attributes:
Phone feature COS Enter the phone features COS

number for the set
Rights

Busy priv.to public 1: Local Private to Public Overflow

overfl. is allowed when the private route
is busy.
0: No overflow when the private
route is busy.
O/S private to public 1: Local Private to Public Overflow

overflow is allowed when the private route
is out of service.
0: No overflow when the private
route is out of service.
13.3.3 Node Access Prefix

1. Select Translator > External Numbering Plan > Node Access Prefix
Destination Node No. Enter the local node number
Number to Add Enter the ARS prefix

Reminder: this prefix must be iden-
tical to the ARS prefix
DID Translator Mode Default DID mode

13.3.4 Node DID Translation Tables

One table must be defined per range of user numbers. These tables are used as follows:
• For DID users, the Thin Sector parameter is set to No. Each internal numbers is translated to a
specific external number.
Internal numbers ISDN numbers

Translation First external
First internal 63000 01 23 45 30 00
number number
63001 01 23 45 30 01
…... Range
…... size
63999 01 23 45 39 99
Figure 13.4: Example of DID Translation

• For non DID users, the Thin Sector parameter is set to Yes. All internal numbers are translated to
the same external number: i.e. the domain attendant number.

Internal numbers ISDN numbers
First internal Translation First external

number 65000 01 23 45 34 00
number
65001
Range
size …...
65999
1. Select: Translator > External Numbering Plan > Node Access Prefix > Node DID Translator
Destination Node No. Enter the local node number
First External Number Enter the first ISDN number of in

the range
First Internal Number Enter the first internal number of in

the range
Range size Enter the number of DID numbers

making up this range
Thin Sector No: for DID users

Yes: for non DID users
see example below
Example:
Configuration:
First Internal Number | Range size | First External Number | Thin sector
63000 | 1000 | 01 23 45 30 00 | No
65000 | 1000 | 01 23 45 34 00 | Yes
Translation result:
Translation of 63123 is 01 23 45 31 23
Translation of 65678 is 01 23 45 34 00
13.3.5 Authorizing Overflow on an Out of Service Set Rescued by the Passive

The Communication Server sees the users who belong to an IP field rescued by a Passive
Communication Server as Out of Service.
The rescuing Passive Communication Server sees the users who belong to IP fields non rescued by
the Passive Communication Server as Out of Service.
For users who belong to isolated IP fields to be able to communicate, you must authorize, in the
system parameters, overflow on Out of Service sets.
Select Installation / Autres param. Install. / Paramètres Système (FR)

Select System / Other System Param. / System Parameters (GEA)

Answer as follows:
Débordement sur poste Hors Service (FR) oui
Overflow on Oos extension (GEA) yes
13.4 Configuration examples

13.4.1 Example Overview
In this example, the node includes three sites. Each site corresponds to one IP domain, namely D1, D2
and D3.
Each domain has its own ISDN access.
The three domains and the Call Server are linked through an IP network. In normal use, the IP network
carries signaling and communications.
When the IP network fails, the signaling is backed up with a signaling link backup (not shown). The
local private to public overflow feature reroutes calls to the public ISDN network.
Call
Server
IP Network
Domain Domain Domain

D1 D2 D3
Trunk Group 1 Trunk Group 2 Trunk Group 3

01 23 45 1x xx 01 23 45 2x xx 01 23 45 3x xx
Public
ISDN
Network
Figure 13.5: Node Configuration Example
Domain numbering:
Domain DID number Non DID number Domain Attendant
1 61000 to 61499 61500 to 61599 61400
2 62000 to 62499 62500 to 62999 62400
3 63000 to 63499 63500 to 63999 63400

Node prefix number: 0

ARS prefix number: 0
Phone Feature COS (with overflow right set to 1): 0
13.4.2 User Overflow Right

Each user must belong to a phone feature COS in which overflow is enabled.
1. Select: Users
Directory number Enter the user directory number
Phone Features COS Enter the phone feature COS num-

ber. For this example: 0
Entity Enter the Entity number. For this

example: 1
Reminder:
Entities must be configured for ARS implementation.
4. Select: Classes of Service > Phone Feature COS
Phone feature COS Enter the Phone features COS

number. For this example: 0.
Rights
O/S private to public 1: Overflow is allowed

overflow
13.4.3 Node Access Prefix

1. Select: Translator > External Numbering Plan > Node Access Prefix
Destination Node No. Enter the local node number. For

this example: 1
Number to Add Enter the ARS prefix. For this ex-

ample: 0
13.4.4 Translation Tables

Two tables must be defined per domain: one for DID numbers and one for non DID numbers.
1. Select: Translator > External Numbering Plan > Node Access Prefix > Node DID Translator
2. For Domain 1:

DID Numbers Non DID Numbers
Destination Node 1 1
No.
First External Num- 01 23 45 10 00 01 23 45 14 00

ber
First Internal Num- 61000 61500

ber
Range Size 500 500
Thin Sector No Yes
For Domain 2:
DID numbers non DID numbers
No.

ber

ber
Range Size 500 500
Thin Sector No Yes
For Domain 3:
DID numbers non DID numbers
No.

ber

ber
Range Size 500 500
Thin Sector No Yes


13.4.5 ARS Configuration

Note:
Unlike overflow between nodes, Media Gateway overflow takes place within the same node. This means that there
is only one configuration for all the Media Gateways.
13.4.5.1 ARS Data Organization

The following diagram shows the relevant parameters of ARS data for this example.
Caller ARS Prefix:

Number: 0
User: 61500 Prefix Meaning : ARS TG seize
Entity: 1 Discriminator No: 0
Entity:
Discriminator 00: 0
Discriminator 01:
(logical) (real)
Numbering Discriminator: 0
Discriminator Rule: Discriminator Rule: Discriminator Rule:

Call Number: 01 23 45 1 Call Number: 01 23 45 2 Call Number: 01 23 45 3
ARS Route List Number: 1 ARS Route List Number: 2 ARS Route List Number: 3
Route List: 1 Route List: 2 Route List: 3

Name : to Domain 1 Name: to Domain 2 Name: to Domain 3
Route : 1 Route : 1 Route : 1

Trunk Group : 2 Trunk Group : 1 Trunk Group : 1
Name : From D2 Name : From D1 Name : From D1
Route : 2 Route : 2 Route : 1

Trunk Group : 3 Trunk Group : 3 Trunk Group : 2
Name : From D3 Name : From D3 Name : From D2
Figure 13.6: ARS Data Organization for Local Private to Public Overflow
13.4.5.2 ARS Prefix

1. Select: Translator > Prefix Plan
Number Enter the ARS prefix number.

For this example 0
Prefix Meaning Select: ARS Prof.Trg Grp Seizure

Discriminator No. Enter the Discriminator number.

For this example: 0
13.4.5.3 Entity Configuration

1. Select: Entities > Discriminator Selector
Entity Number Enter the ARS prefix number.

For this example 1
Discriminator 00 Enter the discriminator number.

For this example 0
.........
Discriminator 07 Not used

13.4.5.4 Discriminator Configuration

The discriminator must have one rule per domain.
1. Select: Translator > External Numbering Plan > Numbering Discriminator
2. Complete the following attributes:
Discriminator Num- Enter the discriminator number.

ber
For this example 0
Name Enter the discriminator name. For

this example: Overflow Discrimina-
tor
4. Select: Translator > External Numbering Plan > Numbering Discriminator > Discriminator
Rule
To Reach To Reach To Reach

Domain 1 Domain 2 Domain 3
Discrimina- 0 0 0
tor No.
Call Number Enter : Enter : Enter :

01 23 45 10 01 23 45 20 01 23 45 30
00 00 00
ARS Route 1 2 3
List Number

13.4.5.5 Route Configuration

There is one route list per domain. Each route list contains n routes (n = domain number - 1).
In this example, there are 3 route lists with 2 routes each.
13.4.5.5.1 Two Routes to Reach Domain 1
1. Select: Translator > Automatic Route Selection > ARS Route List
2. Complete the following attributes:
ARS Route List Enter the discriminator number.

For this example 0
Name Enter the Route List name. For this

example: D1 route list
4. Select: Translator > Automatic Route Selection > ARS Route List > ARS Route
From D2 From D3
ARS Route List 1 1
Route 1 2
Name D1 from D2 D1 from D3
Trunk Group 2 3

For this example 2

example: To Domain 2
From D2 From D3
ARS Route List 2 2
Route 1 2

Trunk Group 1 3

For this example 3

example: To Domain 3
From D1 From D2
ARS Route List 3 3
Route 1 2
Trunk Group 1 2

Chapter
14 IP services and port numbers
14.1 Overview
14.1.1 Dynamic Port Range
In R5.1.2 and lower, dynamic port range cannot be configured. The range covered is 10000-20000.
As of R6.0, dynamic port range can be set. The default range is reduced to 10000-10499.
Dynamic port range can be used by all applications that allow the core to select a port for them. This
includes TFTP and FTP when the Call Server is client.
In addition, to facilitate configuration, free port range uses the same limits as dynamic port range. This
may give the impression that the range is a common range, although this is not the case.
For more information on the different types of ports, refer to Types of Port on page 191.
Range limits are configured using Netadmin, see Configuring dynamic port range on page 193.
14.1.2 Types of Port

There are different types of ports:
• "Well known" ports (1 - 511)
This range includes all "well known" ports between 1 and 511. These ports are identified (in /etc/
services) and only the ports associated with the desired services (DHCP, FTP (partially), RSH, etc.)
are opened on the firewalls. The DHCP ports (67, 68) and TFTP ports (69), for example, are located
in this area.
• Supervisor dynamic port range (512 - 1023)
These are dynamic ports used for certain special services. RSH and TELNET open sockets using a
port from this range. This range has fixed limits and cannot be expanded or reduced.
Given its size, this range cannot be used for TFTP.
• Low dynamic port range
These ports have the same function as the previous ports, but are used for other services. The
ports in this range are generally used by proprietary applications. Currently, the TFTP port is taken
from this range (see TFTP Connection on page 191).
From R6.0, this range can be configured.
• Free port range
In fact, this is more than a range as it is a list of all free TCP ports. It is therefore difficult to make
this range configurable. The ports in this range are for example, used by the FTP server CSs for the
FTP server data channel ports used for passive connections.
14.1.3 TFTP Connection

Figure 1 shows how standard TFTP connection exchanges are performed.
The client sends a file request from a port C (selected by the client), to port 69 on the TFTP server. If a
server is "listening", it determines which port (port S) to use to respond to the request. It then sends a
first block via port S to port C on the client. The client returns an “ACK” message via ports C to S and
so on, until the file has been completely transferred.

Chapter 14 IP services and port numbers
TFTP server TFTP client

(Call Server) (IP phone)
Asking for file Port C

Port 69
Port S Sending block 1
Port C
Ack block 1 Port C
Port S
Port S Sending block 2
Port C
Ack block 2 Port C
Port S
Figure 14.1: TFTP Connection
Selection of ports C and S varies depending on the operating system installed on the machines. On a
CS, port S is arbitrarily selected in the range of dynamic ports by the core. The IP-Phone selects port P
from its own specific range. If the client were to be a CS (highly unlikely with TFTP), port P would also
be selected from dynamic port range.
14.1.4 Passive FTP Connection

Figure 2 shows how standard passive FTP connection exchanges are performed. Acknowledgement
exchanges at TCP level are not shown in the figure.
The client sets up the command channel (setup is not shown in the figure) between port Cc on the
client and port 21 on the server. When a transfer request is made, the client requests passive
connection to the server via the command channel. The server responds by assigning a port number,
Ds, to which the client must connect for the DATA connection.
The client then determines a new local port (port Dc) for the DATA connection, and opens the socket
between this port and port Ds, assigned by the server in the previous step. Once open, this channel is
used for A SINGLE data transfer between the client and the server (irrespective of direction). An FTP
'get' is shown in the figure, but the mechanism is the same for a 'put' or 'dir'.

FTP Server FTP Client

(Call Server) Control (IP phone)
Channel
Passive Connection Port Cc

Port 21 Request
Port 21 Number of Port Ds Us
ed for Data Socket
Sent Port Cc
Control
Channel
Data Channel Opened Port Dc

Port Ds
Port Ds Data Sent to Client
Port Ds Port Dc
Port Ds Port Dc
Port Ds Port Dc
Port Dc
Data Channel Closed
Figure 14.2: Passive FTP Connections
In the same way as for TFTP, port selection policy varies depending on the operating system used:
• If the server is a CS, port Ds is selected by the FTP server (not by the core) from the list of free
ports. The configuration mechanism for the range of usable ports is therefore different from that
used for TFTP.
• If the client is a CS, then ports Cc and Dc are determined in the range of dynamic ports.
• For other types of machines, refer to the documentation for the machine concerned.
14.1.5 IP services and Port Numbers

It is important to know these numbers if the PCX is to be integrated in a secure network with a firewall.
To obtain a list of the ports that a server is "listening" to at a specific time in order to compare it with the
list in the table and thus detect any unusual service, enter the command netstat -l.
14.2 Configuring dynamic port range

14.2.1 Configuring Dynamic Port Range
Important:
Range limits must only be modified with the agreement of the client network administrator. The range
configured for the Call Server must be included in the range configured for firewalls.

14.2.1.1 Determine the Thresholds to Be Configured

1. Make an inventory of all applications using one (or more) dynamic ports on the site. This includes
the FTP and TFTP services, but there are others.
The server using the highest number of ports is the FTP server. Like TFTP, this server uses a port
per file transfer during a session but, unlike TFTP, a released port can only be reused when the
TIME_WAIT for the socket elapses (usually 60s). A port is therefore unavailable for a full minute
after use. This may affect the applications using FTP for data transfer, in particular, retrieval of
accounting records.
An IP-Phone uses three dynamic ports.
2. Among the applications inventoried, assess how many applications may be used simultaneously
and calculate the number of dynamic ports used.
3. Add a safety margin of around 20%.
4. Calculate the size of the range to be configured.
5. Calculate the thresholds: in most cases, only the upper limit of the range needs to be modified, the
lower limit remains at 10 000.
Example:
• The site includes 100 IP-Phones that are likely to be started up (almost) simultaneously. TFTP may therefore
(potentially) use 300 ports (for the IP-Phones only).
• The safety margin is 300 x 0.2 = 60.
• Range is thus 300 + 60 = 360.
• The range to configure is thus 10 000 to (at least) 10359.
14.2.1.2 Configuring Thresholds

1. Connect to the system with the "root" account.
2. Run the command netadmin -m.
3. Select 11. 'Security'
4. Select 6. 'Low dynamic port range configuration'
5. Select 2. 'Update configuration'
The following screen is displayed:
Low dynamic ports range configuration.
======================================
Enter lowest allowed port (3000 <= port < 32639, default is 10000):
6. Enter the lower limit of the range (in general, this threshold can be left at its default value, 10000)
The following screen is displayed:
Enter highest allowed port (10128 < port <= 32767, default is
10499):
7. Enter the upper limit of the range according to estimated needs.
Note:
Port range must include at least 128 ports.
8. Enter 0 to return to the main menu, then select 16. 'Apply modifications'
9. Enter 0 to exit netadmin.
14.2.1.3 Configuring the Firewall

A typical environment is a Call Server and one or more IP-Phones separated by an IP network and a
firewall.
Another typical environment is a Call Server and one or more FTP clients using passive FTP
connections (OmniVista 4760 for example) separated by an IP network and a firewall.

Figure 1 shows an example of a Call Server with IP-Phones. In this example, the firewall must be
configured to allow passage of DHCP traffic (UDP port 67) and TFTP traffic (UDP port 69), as well as
the entire range of dynamic ports configured on the Call Server.
IP
Call Server
IP Network Firewall
Figure 14.3: Example Topology with IP Phones
Figure 2 shows an example with a Call Server and 4760. In this example, the FTP client (4760)
connects to the Call Server via passive FTP connections. If the firewall is unable to determine the port
used for the data channel by "listening" to the command channel, the entire range of usable ports has
to be opened. The advantages gained by use of a firewall are severely reduced. For firewalls of this
type, FTP port range is also reduced.
A4760
Call Server
IP Network Firewall
Figure 14.4: Example Topology with a 4760
14.2.2 Incidents
When no ports in the range remain available, incident 1529 is sent, in the limit of one incident per
minute:
• 1529 No dynamic ports, proto 6
For a port request for a TCP socket,
• 1529 No dynamic ports, proto 17
For a port request for a UDP socket.
Caution:
No incident is sent when the FTP server does not have enough ports. However, the client sends an explicit
message stating that the server does not have enough resources.

Chapter
15 Tones
15.1 Overview
15.1.1 Overview
Tones, still referred to as true tones, are part of tone auxiliaries in the same way as voice guides. Each
tone has a specific tonality and is used in a certain number of applications.
Tones are used in telephone facilities (phone features). They guide the user in the operation of his set
and are notably used to:
1. Inform the user that he can dial: the user unhooks and waits for the dial tone before dialing the
directory number to be called.
2. Inform the user of the state of the set he wishes to call (free or busy). If the set is busy, the tone
heard is the "wait on busy" tone (depending on calling set rights). If "call back on busy" is allowed,
the caller does not get the busy tone but a voice guide when a busy set is called.
3. Ensure continuity of operation. This is the case with a consultation call, allowing a second party to
be called in the course of a call. To do this, the user puts the call on hold, then calls the desired
party.
Tones are also used to:
1. Define set ringing cadence. They are configured and ready to be used by the system.
Example:
The ringing cadence of an alarm set is set by tone N°64.
2. Assign different cadences according to call origin (internal, external, etc...). The melody can be
customized.
Example:
Tone N°29 is used for internal calls and tone N°30 for external calls.
3. Assign a backup tone for voice guides when they cannot be played.
15.1.2 Related modules

Tones are described in the following modules:
• Functional description (see the Detailed description on page 196).
• Management (see the Configuration procedure on page 265).
• A description of existing tones is given in the Tone table on page 198.
• The basic tones for each country are described in the Basic tones country by country on page 204.
• R1 and R2 tones are described in the R1 and R2 frequencies on page 261.

15.2.1 Principle
Tones are constructed from the basic tones delivered with the system. They form a "sequence". For
the tone table: see the Tone table on page 198. For the basic tone table country by country: see the
Basic tones country by country on page 204.

Chapter 15 Tones
Each basic tone has a corresponding duration (given in ms). A specific cadence can thus be specified
for each tone by modifying the durations of the basic tones it is composed of. A duration of 0 ms
corresponds to continuous (infinite) duration.
Note:
Basic tone N°0 always corresponds to silence.
The following examples show the different possible cases that may be encountered with respect to
tones (combinations of basic tones with their respective durations).
Example:
Tone 19, "Dialing tone" (prompt to dial), only uses basic tone 21 (440Hz in France - continuous tone).
No. 21
Duration (ms) 0 (infinite)
Figure 15.1: Example 1
Example:
Tone 22, the "Busy tone", is a combination of basic tones 21 and 0 with a cadence of 500 ms/500 ms.
No. 21 0 21 0
Duration (ms) 500 500 500 500
Example:
Tone 23, "Beep indicating wait", is a combination of basic tones 21 and 0 with a cadence of 500 ms/0 ms.
No. 21 0
Duration (ms) 500 0 (infinite)
Example:
Tone 61, "Congestion tone", is a combination of basic tones 25 and 26 with a cadence of 740 ms/740 ms.

Chapter 15 Tones
No. 26 0
25
Duration (ms) 740 740 0 (infinite)
By varying the combinations of basic tones and their cadence, the manager can modify existing tones.
He can also create new tones. The identifier number of these tones can be an unused number (see the
Tone table on page 198) or the number of a voice guide (the voice guide must first be deleted). In the
same way, the manager can replace a tone with a voice guide.
All tones present on the PBX can be played from a set in the installation (see the Voice guide and tone
check - Overview).
Note:
Some tones must follow a precise sequence for the application in which they are used and cannot therefore be
modified. This is the case for tone N°28.
15.2.2 Tones for R2 signaling

The tone table is for tone generators and also R1 and R2 DTMF generators.
Tones for R2 signaling cannot be modified by the manager. R2 tone files are provided by the GD board
and are downloaded when the coupler is initialized.
For the R2 signaling tone table and the frequencies used, see the R1 and R2 frequencies on page 261.
15.2.3 Tones specific to the USA

Tone 66 (Feedback Tone) - emitted when a key is pressed on a dedicated digital set, is constructed
from the following basic tones:
Tone N° Basic tone Duration (units of 10 ms)
0 4
66 21 10
0 0 (infinite)
15.3 Tone table

15.3.1 Tone table
Tone Nº Name Meaning
Tone 1 AUXTEACH Routing tone
Tone 2 AUXMUSICATT Wait (Camp on) tone

Chapter 15 Tones
Tone 3 to Tone 18 Voice guides
Tone 19 AUXTE Dial tone
Tone 20 AUXPTT1 Simulated external tone
Tone 21 AUXPTT2 Simulated international tone
Tone 22 AUXTO Busy tone
Tone 23 AUXATT Tone indicating a waiting call
Tone 24 AUXBIP Barge-in (intrusion) tone
Tone 25 AUXSONBA Basic ringing tone
Tone 26 AX26 Dialing tone to indicate presence in DISA mode
Tone 27 AUXRA Ringing tone
Tone 28 AUXSIL Silence
Tone 29 AUXSONLO Ringing for internal calls
Tone 30 AUXSONR Ringing for external calls
Tone 31 AUXSONRV Set forwarded ringing
Tone 32 AUXSORAP Automatic callback ringing
Tone 33 AUXSONOP Attendant ringing
Tone 34 AUXSONRDV Appointment (Meet me) reminder ringing
Tone 35 MF1 DTMF digit 1 generator

Chapter 15 Tones
Tone 45 MFET DTMF digit * generator
Tone 46 MFCAR DTMF digit # generator
Tone 47 MFA DTMF digit A generator
Tone 48 MFB DTMF digit B generator
Tone 49 MFC DTMF digit C generator
Tone 50 MFD DTMF digit D generator
Tone 51 B1 SOCOTEL DTMF generator
Tone 52 A2B3 SOCOTEL DTMF generator
Tone 53 A3B3 SOCOTEL DTMF generator
Tone 54 FC SOCOTEL DTMF generator (test frequency)
Tone 55 REMPGP1 Hold music replacement tone
Tone 56 REMPGP2 Backup tone N°2 (action accepted)
Tone 57 REMPGP3 Backup tone N°3 (prompt to dial after prefix)
Tone 58 Voice guide
Tone 59 AUXIA2F 2 wire ATL frequency
Tone 60 TONSURSON Over-ringing on busy multiline set
Tone 61 AUXTOCONG Congestion tone
Tone 62 AUXTODIS Dissuasion tone
Tone 63 Voice guide
Tone 64 TONALAPO Alarm set ringing
Tone 65 Voice guide
Tone 66 AUXFBT Feedback tone (tone emitted when a key is

pressed on a dedicated digital set - specific to
the USA)

Chapter 15 Tones
Tone 67 AUXMULOC Ring tone on busy but accessible multiline set
Tone 68 Voice guide
Tone 69 AUXSOMES Message lamp activation tone on Z sets in US

shelves
Tone 70 AUXSOPRIO Priority call ringing on free analog sets
Tone 71 to Tone 108 Voice guides
Tone 109 GPHURLANT Tone to indicate a set in line lockout mode
Tone 110 Voice guide
Tone 111 to R2AR_F1 to 10 Non-modifiable R2 tones - (see the R1 and R2

Tone 120 frequencies on page 261).
R2AV_F1 to 15
and Tone 121 to Non-modifiable R2 tones.
Tone 135
Tone 136 AUXCONGES Congestion tone
Tone 137 AUXTONBASE Basic Italian tone
Tone 138 AUXBIPCONF Conference tone
Tone 139 Voice guide
Tone 140 to R2AR_F1_IMP to Non-modifiable R2 tones - (see the R1 and R2

Tone 149 R2AR_F10_IMP frequencies on page 261).
and R2AV_F1_IMP to Non-modifiable R2 tones.
R2AV_F15_IMP
Tone 150 to
Tone 165
Tone 166 TONARV Backup tone N°4 (dial tone for forwarded set)
Tone 167 TONACH_RE Routing transit tone
Tone 168 TON_PBX_ABS Backup tone N°5

Set absent from (PBX) hunt group
Tone 169 R2 backwards frequency on IO1

Combination N°1 (specific to Belgium)
Tone 170 R2 backwards frequency on IO1

Combination N°6 (specific to Belgium)

Chapter 15 Tones
Tone 171 to Reserved for hold music on analog interfaces

Tone 180 (non-modifiable)
Tone 181 AUXSONMESZ Message lamp activation tone on Z sets in ACT

shelves
Tone 182 On a Z alarm set, tone showing that an alarm

has been activated
Tone 183 AUXRA2 Ring tone sent on trunks after a pre-offhook

voice guide. Tone identical to tone 27, but can
be changed when specified by the public carri-
er.
Tone 184 Priority ringing (MLPP service)
Tone 185 Continuous auxiliary for cyclic incoming pre-

emption beep (MLPP service)
Tone 186 AUXTEACHLOC Basic routing tone for local facilities
Tone 187 to R2AV_F11 to 15 Non-modifiable R2 tones - (see the R1 and R2

Tone 191 frequencies on page 261).
Non-modifiable R2 tones.
Tone 192 BIPEXT Beep on set with outgoing external conversa-

tion.
Tone 193 DIGITAL_RINGING_TONE Ring tone for digital set cadencing. In fact, to
distinguish call types, there is a choice of 6 pre-
determined cadences and a 7th that can be
customized.
Tone 194 to CGCT DTMF tones 1 to 10

Tone 204
Tone 205 PRIO_BIP1 Priority call tone N°1
Tone 206 PRIO_BIP2 Priority call tone N°2
Tone 207 REMPGP4 Backup tone N°6 (action not allowed)
Tone 208 BIPSECRETARY Tone for break-in (intrusion) on assistant (sec-

retary) set when the manager activates discreet
listening.
Tone 209 AUXPATRIO Priority call ringing on a Z set behind UA
Tone 210 AUXWRONGNB Wrong number tone

Chapter 15 Tones
Tone 211 REORDER_TONE Specific tone for the USA
Tone 212 AUXSONMESZ_MG Message lamp activation tone on Z sets in a

Media Gateway
Tone 213 Free tone
Tone 214 to Voice guides

Tone 255
Tone 256 to R1 tones

Tone 270

Tone 543
Tone 544 AUXBIPRECORD Beep when a conversation is recorded

Tone 560
Tone 561 AUXBIP_RA Tone for automatic reconfiguration service
Tone 562 to Free tones

Tone 599

Tone 679

Tone 699

Tone 849
Tone 850 to R1 tones

Tone 864
Tone 865 ANIREQ

Tone 910

Tone 1023

Chapter 15 Tones
15.4 Basic tones country by country

15.4.1 Overview
For any country not listed below (classified in alphabetical order), the tones installed are the same as
those installed for Poland (see Poland on page 241).
15.4.2 Argentina
Specific tones for Latin America (see Latin America on page 231).
15.4.3 Australia
Basic tone N° Function LEVEL (in dBm0)
0 Silence
1 1209+697Hz
2 1336+697Hz High frequency
3 1477+697Hz -12
4 1209+770Hz
5 1336+770Hz Low frequency
6 1477+770Hz -11
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3

Chapter 15 Tones
19 50Hz line seize / ALE -1.66
20 Reserved for DECT
21 425Hz -12
22 450 + 400 Hz -14.5
23 1400Hz -14.5
24 425Hz -22
25 425Hz -12
26 Not used
27 25Hz ringing 3
28 400+425Hz -14.5
29 425Hz -4
30 50Hz (Hotel voicemail) -15
31 25Hz ringing (for ALE) -1.66
15.4.4 Austria
0 Silence
1 1209+697Hz
3 1477+697Hz -6
4 1209+770Hz
6 1477+770Hz -8
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz

Chapter 15 Tones
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing -1.5
21 425Hz -3.5
22 1800Hz -6.5
23 1400Hz -6.5
24 425Hz -15
25 425Hz -3.5
26 2100Hz -9
27 25Hz ringing 3
28 950Hz -6.5
29 425+350Hz -14/-14
31 25Hz -1.66

Chapter 15 Tones
15.4.5 Bahrein
0 Silence
1 1209+697Hz
3 1477+697Hz -9
4 1209+770Hz +/-2 dB
5 1336+770Hz
7 1209+852Hz -11
8 1336+852Hz +/-2 dB
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 350+440Hz -12
22 1800Hz -12
23 425Hz -12
24 1400Hz -12

Chapter 15 Tones
25 425Hz -12
26 Not used
27 25Hz ringing 3
28 950Hz -12
29 Not used
15.4.6 Belgium
0 Silence
1 1209+697Hz
3 1477+697Hz -4
4 1209+770Hz
6 1477+770Hz -6
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz

Chapter 15 Tones
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -4.5
22 425Hz -6
23 425Hz 3
24 1400Hz -6
25 425Hz -4.5
26 (R2/MF2)900+780Hz -8/-8
27 25Hz ringing 3
28 Not used
29 (R2/MF1)1140+1020Hz -8/-8
15.4.7 Brazil
0 Silence
1 1209+697Hz
3 1477+697Hz -7
4 1209+770Hz
6 1477+770Hz -9

Chapter 15 Tones
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 Not used
22 330Hz -10
23 425Hz -5
24 425Hz -7
25 425Hz -7
26 Not used
27 25Hz ringing 3
28 Not used
29 425+24Hz -10
31 25Hz -1.66

Chapter 15 Tones
15.4.8 Cambodia
Tones common with tones for Singapore (see Singapore on page 246).
15.4.9 Chile
15.4.10 China (People's Republic of)

0 Silence
1 1209+697Hz
3 1477+697Hz -5.5
4 1209+770Hz
6 1477+770Hz -7.5
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz -5.5/-7.5
18 50Hz ringing 3

Chapter 15 Tones
21 450Hz -10
22 450Hz -15
23 450Hz -20
24 Not used
25 450Hz -10
26 2700Hz 3
27 25Hz ringing) 3
28 Not used
29 Not used
15.4.11 Colombia
15.4.12 Costa Rica

Tones common to other Latin American countries (see Latin America on page 231).
15.4.13 Czech Republic

Tones common with tones for Slovakia (see Slovakia on page 247).
15.4.14 Denmark
0 Silence
1 1209+697Hz
3 1477+697Hz -8.8
4 1209+770Hz
6 1477+770Hz -10

Chapter 15 Tones
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -8
22 1800Hz -8
23 1400Hz -8
24 425Hz -13.5
25 425Hz -8
26 425Hz -8
27 25Hz ringing 3
28 950Hz -8
29 425+375Hz -7.5/-9.5
31 25Hz -1.66

Chapter 15 Tones
15.4.15 Ecuador
15.4.16 Egypt
0 Silence
1 1209+697Hz
3 1477+697Hz -5.5
4 1209+770Hz +/-2 dB
5 1336+770Hz
7 1209+852Hz -7.5
8 1336+852Hz +/-2 dB
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 450x50Hz -5
22 1800Hz -5

Chapter 15 Tones
23 450Hz -5
24 1400Hz -5
25 450x50Hz -5
26 440+350Hz -5
27 25Hz ringing 3
28 950Hz -5
29 440+350Hz -9
15.4.17 El Salvador
Tones common to other Latin American countries (see Latin America on page 231).
15.4.18 Finland
0 Silence
1 1209+697Hz
3 1477+697Hz -8
4 1209+770Hz
6 1477+770Hz -10
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz

Chapter 15 Tones
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -8
22 950Hz -8
23 1400Hz -8
24 1800Hz -8
25 425Hz -8
26 425Hz -18
27 25Hz ringing 3
28 950Hz -18
29 1400Hz -18
30 25Hz Hotel -15
15.4.19 France
0 Silence
1 1209+697Hz

Chapter 15 Tones
3 1477+697Hz -6
4 1209+770Hz
6 1477+770Hz -8
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 440Hz -10
22 330Hz -9
23 440+330Hz -10/-7
24 440Hz -12
25 440Hz -10
26 330Hz -12
27 25 Hz ringing 3

Chapter 15 Tones
28 Not used
29 Not used
30 25 Hz (Hotel voicemail) -15
15.4.20 Germany
0 Silence
1 1209+697Hz
3 1477+697Hz -6
4 1209+770Hz
6 1477+770Hz -8
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3

Chapter 15 Tones
19 50Hz line seize 0
21 425Hz -5
22 425Hz -16
23 425+400Hz -8/-8
24 425Hz -22
25 425Hz -5
26 1000Hz 0
27 25Hz ringing 3
28 Not used
29 Not used
31 Not used
15.4.21 Greece
0 Silence
1 1209+697Hz
3 1477+697Hz -3.5
4 1209+770Hz
6 1477+770Hz -5.5
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz

Chapter 15 Tones
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -10
22 1800Hz -10
23 450Hz -10
24 1450Hz -10
25 425Hz -6.5
26 900Hz -10
27 25Hz ringing 3
28 950Hz -10
29 400Hz -10
30 25Hz Hotel -15

Chapter 15 Tones
15.4.22 Hong Kong

0 Silence
1 1209+697Hz
3 1477+697Hz -3
4 1209+770Hz
6 1477+770Hz -5
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -14
22 400Hz -14
23 440Hz -14
24 350+440Hz -11

Chapter 15 Tones
25 425Hz -14
26 440+480Hz -11
27 25Hz ringing 3
28 480+620Hz -11
29 Not used
15.4.23 Hungary
0 Silence
1 1209+697Hz
3 1477+697Hz -8
4 1209+770Hz
6 1477+770Hz -5
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz

Chapter 15 Tones
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -10
22 1800Hz -10
23 1400Hz -10
24 425 Hz -10
25 425Hz -10
26 425+450Hz
27 25Hz ringing 3
28 950Hz -10
29 425+300Hz -20
31 900 Hz -5
15.4.24 India
0 Silence
1 1209+697Hz
3 1477+697Hz -5.5
4 1209+770Hz +/-2 dB
5 1336+770Hz

Chapter 15 Tones
7 1209+852Hz -7.5
8 1336+852Hz +/-2 dB
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 330+440Hz -3
22 300+400Hz -3
23 400x25Hz -3
24 400 Hz -3
25 400Hz -3
26 800Hz -3
27 25Hz ringing 3
28 1300Hz -9
29 2100Hz -9

Chapter 15 Tones
15.4.25 Indonesia
15.4.26 Ireland (Eire)

0 Silence
1 1209+697Hz
3 1477+697Hz -11
4 1209+770Hz
6 1477+770Hz -13
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 440Hz -10
22 1800Hz -10

Chapter 15 Tones
23 425Hz -10
24 1400Hz -10
25 425Hz -6.5
26 400+450Hz -12/-12
27 25Hz ringing 3
28 950Hz -10
29 400Hz -10
30 25Hz Hotel -15
15.4.27 Israel
0 Silence
1 1209+697Hz
3 1477+697Hz -5
4 1209+770Hz
6 1477+770Hz -7
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz

Chapter 15 Tones
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 440Hz -6
22 1800Hz -3
23 1400Hz -3
24 440Hz -3
25 440Hz -10
26 440Hz -10
27 20Hz ringing 3
28 950Hz -3
29 350+440Hz -6
15.4.28 Italy
0 Silence
1 1209+697Hz
3 1477+697Hz -6
4 1209+770Hz

Chapter 15 Tones
6 1477+770Hz -8
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -6
22 350Hz -6
23 425+350Hz -6/-6
24 425Hz -11
25 425Hz -6
26 350Hz -11
27 25Hz ringing 3
28 Not used
29 Not used

Chapter 15 Tones
15.4.29 Japan
0 Silence
1 1209+697Hz
2 1336+697Hz
3 1477+697Hz
4 1209+770Hz
5 1336+770Hz
6 1477+770Hz
7 1209+852Hz
8 1336+852Hz -5/-7
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz -5/-7
18 20Hz ringing 3
19 50Hz line seize -1.66

Chapter 15 Tones
21 400Hz busy -13
22 440Hz wait -13
23 400x20Hz ringback -13 / -13
24 Not used
25 Not used
26 440+350Hz ringback -13/-13
27 Not used
28 Not used
29 50 Hz not used 3
30 50 Hz (Hotel voicemail) -15
31 20Hz ringing (ALE), not used -1.66
15.4.30 Korea (Republic of)

Basic tone N° Function LEVEL (en dBm0)
0 Silence
1 1209+697Hz -6/-8
2 1336+697Hz -6/-8
3 1477+697Hz -6/-8
4 1209+770Hz -6/-8
5 1336+770Hz -6/-8
6 1477+770Hz -6/-8
7 1209+852Hz -6/-8
8 1336+852Hz -6/-8
9 1477+852Hz -6/-8
10 1209+941Hz -6/-8
11 1336+941Hz -6/-8

Chapter 15 Tones
Basic tone N° Function LEVEL (en dBm0)
12 1477+941Hz -6/-8
13 1633+697Hz -6/-8
14 1633+770Hz -6/-8
15 1633+852Hz -6/-8
16 Not used
17 1633+941Hz -6/-8
18 20Hz ringing 3
19 50Hz tie line -1.66
21 440+350Hz ringing (internal) -15/-15
22 620+480Hz busy -15/-15
23 480+440Hz ringback -15/-15
24 330Hz -6
25 425Hz -15
26 440Hz -23
27 Not used
28 620+480Hz -10/-10
29 440+350Hz -10/-10
31 50Hz ringing (pour ALE) -1.66
15.4.31 Latin America

Tones common to the following countries:
• Argentina,
• Chile,
• Colombia,
• Costa Rica,
• Ecuador,
• El Salvador,
• Mexico,

Chapter 15 Tones
• Uruguay,
• Venezuela.
Caution:
Peru and Brazil have their own specific tones.
0 Silence
1 1209+697Hz
3 1477+697Hz -7
4 1209+770Hz
6 1477+770Hz -5
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 20Hz ringing 3
21 425Hz -15
22 1800Hz -15

Chapter 15 Tones
23 1400Hz -18/-18
24 950Hz -15
25 425Hz -18/-18
26 1400Hz -12
27 25Hz ringing 3
28 1440Hz -15
29 400Hz -15
30 25Hz Hotel -15
15.4.32 Laos
15.4.33 Luxembourg
Tones common with Germany (see the Germany on page 218)
15.4.34 Malaysia
0 Silence
1 1209+697Hz
3 1477+697Hz -4
4 1209+770Hz
6 1477+770Hz -6
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz

Chapter 15 Tones
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 Not used
22 425Hz -2
23 Not used
24 425Hz -5
25 425Hz -10
26 Not used
27 25Hz ringing 3
28 Not used
29 Not used
15.4.35 Malta
0 Silence
1 1209+697Hz

Chapter 15 Tones
3 1477+697Hz -9
4 1209+770Hz
6 1477+770Hz -10
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -11
22 1800Hz -11
23 425Hz -20
24 1400Hz -20
25 425Hz -11
26 1400Hz -11

Chapter 15 Tones
27 25Hz ringing 3
28 950Hz -11
29 425Hz -11
15.4.36 Mexico
15.4.37 Myanmar (Burma)

15.4.38 Netherlands
0 Silence
1 1209+697Hz
3 1477+697Hz -9
4 1209+770Hz
6 1477+770Hz -11
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz

Chapter 15 Tones
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 440Hz -9
22 1800Hz -19
23 440Hz -12.5
24 1400Hz -19
25 440Hz -9
26 2100Hz -12
27 25Hz ringing 3
28 950Hz -19
29 480Hz -18
15.4.39 New Zealand

Tones common with tones for Australia (see Australia on page 204).
15.4.40 Norway
0 Silence
1 1209+697Hz
3 1477+697Hz -10

Chapter 15 Tones
4 1209+770Hz
5 1336+770Hz +/-2dBm0
6 1477+770Hz
8 1336+852Hz -11.2
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -10.2
22 1800Hz -12.2
23 1400Hz -11.6
24 425Hz -14.2
25 425Hz -6.2
26 1400Hz -22.6
27 25Hz ringing 3
28 950Hz -11.2

Chapter 15 Tones
29 425Hz -26.2
15.4.41 Oman
0 Silence
1 1209+697Hz
3 1477+697Hz -6
4 1209+770Hz +/-1 dB
5 1336+770Hz
7 1209+852Hz -9
8 1336+852Hz +/-1 dB
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3

Chapter 15 Tones
21 425Hz -5
22 1800Hz -10
23 425Hz -10
24 1400Hz -10
25 425Hz -5
26 440Hz -10
27 25Hz ringing 3
28 950Hz -10
29 400Hz -5
15.4.42 Peru
0 Silence
1 1209+697Hz
3 1477+697Hz -7
4 1209+770Hz
6 1477+770Hz -5
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz

Chapter 15 Tones
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 20Hz ringing 3
21 425Hz -10
22 1800Hz -10
23 1400Hz -10
24 950Hz -10
25 425Hz -10
26 330+440Hz -6
27 25Hz ringing 3
28 480+620Hz -6
29 440+480Hz -6
15.4.43 Philippines
15.4.44 Poland
Tones installed by default for any country that does not have specific tones.

Chapter 15 Tones
0 Silence
1 1209+697Hz
3 1477+697Hz -6
4 1209+770Hz
6 1477+770Hz -8
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -6
22 1800Hz -6
23 1400Hz -6
24 425Hz -10

Chapter 15 Tones
25 425Hz -6
26 Not used
27 25Hz ringing 3
28 950Hz -6
29 Not used
15.4.45 Portugal
0 Silence
1 1209+697Hz
3 1477+697Hz -7
4 1209+770Hz
6 1477+770Hz -9
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz

Chapter 15 Tones
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 440Hz -12
22 330Hz -10
23 Not used
24 425Hz -12
25 425Hz -12
26 2100Hz -9
27 25Hz ringing 3
28 Not used
29 1300Hz -9
30 25Hz (Hotel -15
15.4.46 Russia and the CIS

These tones are common to all countries in the CIS (Armenia, Azerbaijan, Byelorussia, Kazakhstan,
Kirghizistan, Georgia, Moldavia, Russia, Tadjikistan, Turkmenistan, Uzbekistan, Ukraine).
0 Silence
1 1209+697Hz
3 1477+697Hz -6
4 1209+770Hz

Chapter 15 Tones
6 1477+770Hz -8
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -10
22 1800Hz -10
23 425Hz -15
24 1400Hz -17
25 425Hz -6.5
26 25Hz ringing (ALE) -1.66
27 25Hz ringing 3
28 950Hz -10
29 2600Hz -9

Chapter 15 Tones
31 500Hz -4.3
15.4.47 Singapore
0 Silence
1 1209+697Hz
3 1477+697Hz -5
4 1209+770Hz
6 1477+770Hz -7
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -8

Chapter 15 Tones
22 1800Hz -3
23 1400Hz -3
24 425Hz -3
25 425Hz -13
26 425Hz -10
27 25Hz ringing 3
28 950Hz -3
29 425x24Hz -3
15.4.48 Slovakia
Tones common to the Czech Republic.
0 Silence
1 1209+697Hz
3 1477+697Hz -9
4 1209+770Hz
6 1477+770Hz -11
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz

Chapter 15 Tones
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -5
22 1800Hz -5
23 1400Hz -5
24 425Hz -11
25 425Hz -5
26 1400Hz -11
27 25Hz ringing 3
28 950Hz -5
29 425Hz -5
15.4.49 Spain
0 Silence
1 1209+697Hz

Chapter 15 Tones
3 1477+697Hz -5
4 1209+770Hz
6 1477+770Hz -4
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -12
22 330 Hz -10
23 Not used
24 1400Hz -20
25 425Hz -12
26 1700Hz -8
27 25Hz ringing 3

Chapter 15 Tones
28 Not used
29 Not used
15.4.50 South Africa

0 Silence
1 1209+697Hz
3 1477+697Hz -9
4 1209+770Hz +/-2 dB
5 1336+770Hz
7 1209+852Hz -11
8 1336+852Hz +/-2 dB
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3

Chapter 15 Tones
21 400x33Hz -8
22 1800Hz -8
23 400Hz -8
24 1400Hz -8
25 400Hz -8
26 1209+697Hz -8
27 25Hz ringing 3
28 950Hz -8
29 Not used
15.4.51 Sweden
0 Silence
1 1209+697Hz
3 1477+697Hz -7.5
4 1209+770Hz
6 1477+770Hz -9.5
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz

Chapter 15 Tones
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -8.5
22 1800Hz -8.5
23 1400Hz -8.5
24 1400Hz -28.5
25 425Hz -8.5
26 Not used
27 25Hz ringing 3
28 950Hz -8.5
29 Not used

Chapter 15 Tones
15.4.52 Switzerland
0 Silence
1 1209+697Hz
3 1477+697Hz -6
4 1209+770Hz
6 1477+770Hz -8
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -1.5
22 425Hz -14
23 340+425Hz -1.5/-6.5
24 1400Hz -17

Chapter 15 Tones
25 425Hz -6.5
26 425Hz -6.5
27 25Hz ringing 3
28
29 850Hz -6.5
15.4.53 United Kingdom (UK)

0 Silence
1 1209+697Hz
3 1477+697Hz -13
4 1209+770Hz
6 1477+770Hz -15
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz

Chapter 15 Tones
16 Not used
17 1633+941Hz
18 50Hz ringing 3
19 50Hz line seize -1.66
21 400Hz -15
22 330Hz -15
23 420+335Hz -18/-18
24 440Hz -15
25 420+335Hz -18/-18
26 1400Hz -12
27 25Hz ringing 3
28 1300Hz -15
29 2100Hz -15
31 25 Hz ringing (for ALE) -1.66
15.4.54 Taiwan
0 Silence
1 1209+697Hz
3 1477+697Hz -6
4 1209+770Hz
6 1477+770Hz -8

Chapter 15 Tones
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 480+620Hz -24
22 480Hz -0
23 Not used
24 440+480Hz -19
25 425Hz -13
26 425Hz -13
27 20Hz (Hotel voicemail) 3
28 440+480Hz -13
29 350+440Hz -13

Chapter 15 Tones
15.4.55 Thailand
15.4.56 United Arab Emirates

0 Silence
1 1209+697Hz
3 1477+697Hz -9
4 1209+770Hz +/-1 dB
5 1336+770Hz
7 1209+852Hz -11
8 1336+852Hz +/-1 dB
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 350+450Hz -13
22 1800Hz -13

Chapter 15 Tones
23 425Hz -13
24 1400Hz -13
25 425Hz -13
26 425Hz -10
27 25Hz ringing 3
28 950Hz -13
29 450Hz -10
31 25 Hz ringing (for ALE) -1.66
15.4.57 United States (USA)

0 Silence
1 1209+697Hz
3 1477+697Hz -8
4 1209+770Hz
6 1477+770Hz -10
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz

Chapter 15 Tones
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz -8/-10
18 50Hz ringing 3
20 Reserved for PWT
21 480+620Hz -18.5
22 425Hz -16
23 Not used
24 440+620Hz -18.5
25 440Hz -16
26 Not used
27 25Hz ringing 3
28 440+480Hz -18.5
29 350+440Hz -18.5
15.4.58 Uruguay
15.4.59 Venezuela
15.4.60 Viet Nam


Chapter 15 Tones
15.4.61 Yugoslavia
0 Silence
1 1209+697Hz
3 1477+697Hz -6
4 1209+770Hz
6 1477+770Hz -8
7 1209+852Hz
8 1336+852Hz
9 1477+852Hz
10 1209+941Hz
11 1336+941Hz
12 1477+941Hz
13 1633+697Hz
14 1633+770Hz
15 1633+852Hz
16 Not used
17 1633+941Hz
18 50Hz ringing 3
21 425Hz -3
22 1800Hz -6
23 1400Hz -6
24 425Hz -10

Chapter 15 Tones
25 425Hz -6
26 Not used
27 25Hz ringing 3
28 950Hz -6
29 Not used
15.5 R1 and R2 frequencies

15.5.1 R1 frequencies
Tone Combined basic tone no. Tone dBm0 level
N°
Tone 256 1 700Hz+900Hz -7.3 / -7.3
Tone 257 2 700Hz+1100Hz -7.3 / -7.3
Tone 258 3 900Hz+1100Hz -7.3 / -7.3
Tone 259 4 700Hz+1300Hz -7.3 / -7.3
Tone 260 5 900Hz+1300Hz -7.3 / -7.3
Tone 261 6 1100Hz+1300Hz -7.3 / -7.3
Tone 262 7 700Hz+1500Hz -7.3 / -7.3
Tone 263 8 900Hz+1500Hz -7.3 / -7.3
Tone 264 9 1100Hz+1500Hz -7.3 / -7.3
Tone 265 10 1300Hz+1500Hz -7.3 / -7.3
Tone 266 11 700Hz+1700Hz -7.3 / -7.3
Tone 267 12 900Hz+1700Hz -7.3 / -7.3
Tone 268 13 1100Hz+1700Hz -7.3 / -7.3
Tone 269 14 1300Hz+1700Hz -7.3 / -7.3

Chapter 15 Tones
Tone Combined basic tone no. Tone dBm0 level

N°
Tone 270 15 1500Hz+1700Hz -7.3 / -7.3
Tone 850 1 700Hz+900Hz -3 / -3
Tone 851 2 700Hz+1100Hz -3 / -3
Tone 852 3 900Hz+1100Hz -3 / -3
Tone 853 4 700Hz+1300Hz -3 / -3
Tone 854 5 900Hz+1300Hz -3 / -3
Tone 855 6 1100Hz+1300Hz -3 / -3
Tone 856 7 700Hz+1500Hz -3 / -3
Tone 857 8 9002Hz+1500Hz -3 / -3
Tone 858 9 1100Hz+1500Hz -3 / -3
Tone 859 10 1300Hz+1500Hz -3 / -3
Tone 860 11 700Hz+1700Hz -3 / -3
Tone 861 12 900Hz+1700Hz -3 / -3
Tone 862 13 1100Hz+1700Hz -3 / -3
Tone 863 14 1300Hz+1700Hz -3 / -3
Tone 864 15 1500Hz+1700Hz -3 / -3
15.5.2 R2 frequencies
Tone Nº Combined basic tone no. Tone dBm0 level
Tone 111 R2 backward frequency (DDI) 1140Hz+1020Hz -8 / -8

-
1

-
2

-
3

Chapter 15 Tones

-
4

-
5

-
6

-
7

-
8

-
9

-
10
Tone 121 R2 forward frequency - 1380Hz+1500Hz -8 / -8

1

2

3

4

5

Chapter 15 Tones

6

7

8

9

10

11

12

13

14

15
Tone 187 R2 backward frequency- 1140Hz+540Hz -8 / -8

11

12

13

14

Chapter 15 Tones

15

15.6.1 Introduction
This section details how to parameter the different tones used in the telephone facilities.
The administrator can:
• create or modify a tone defined by its number,
• define a prefix for tone playback (all the tones can be consulted) with modification of the duration via
a timer,
• reinitialise the tone plan with the factory default values.
15.6.2 Tone
This parametering should be carried out when a tone is to be created or modified. The combined basic
tone that it comprises is obtained by juggling with the "Tone No." and "Duration" parameters.
Object name : System > Tone
Attributes:
Tone No. : Enter the number of the tone.
Combined basic tone :
Tone No. : Enter the number of the first basic tone making up the se-
quence.
Duration : Enter the duration of the basic tone (10 ms units).
Repeat entry of the "Tone No." and "Duration" parameters for each basic tone making up the combined
basic tone sequence. Use the following commands:
• [Add] or [Delete] are used to insert new basic tones or remove tones from the sequence,
• [Next] and [Previous] are used to scroll through all the basic tones presented in the combined
tone sequence.
Example with tone 22 "busy tone"described in a previous chapter:
Object name : System > Tone
Attributes:
Tone No. : 22 .
Tone No. : 21.

Chapter 15 Tones
Duration : 50.
Pressing the [Next] command results in:

Attributes:
Tone No. : 22 .
Tone No. : 0.
Duration : 50.
15.6.3 Prefix for tone playback

This prefix allows the administrator to control all system tones and, in particular, tones that have
recently been altered or created.
Object name : Translator > Prefix Plan
Attributes:
Prefix Meaning : Local Features.
Local Features : Tone test.
After entering this prefix, enter on the set the number of the tone to playback. Enter 4 digits since the
tone auxiliary numbers (true tone or voice guide) can go up to 2,000.
Example:
For tone 19, enter 0019 on the set after entering the prefix.
Note:
to scroll through all the tones before or after the one played back, use the [+] and [-] keys on the set.
15.6.4 Playback timer

This timer provides the administrator with the possibility of modifying the playback time for the tone to
be listened to after entering the "Tone test" prefix and the tone number.
If necessary, change its duration.
Object name : System > Timers
Attributes:
Timer No. : 108 : wait timer before moving onto the playback of the next
tone.
Timer Units : 60 (6s).
15.6.5 R1 and R2 signaling

The type of tone downloaded on GPA2 and EMTL boards is defined in the board data.
Object name : Shelf> Board

Chapter 15 Tones
Attributes:
Interface Type : GPA2 or EMTL board.
Tone on board : Select the tone type:

• R1 tone,
• R1_5 tone,
• R2 tone.
15.6.6 Reinitialising the tones plan

This allows the administrator wants to return to the default configuration per country after having
modified the tones. For this, the administrator must:
• logon under "mtcl",
• move to directory /DHS3data/mao,
• run the "intro_tones" command followed by the country code on two characters (the list of country
codes can be viewed on screen).
Example:
"intro_tones FR".
Once the process has terminated, the system indicates this by: "Table initialisation OK".
Note:
carry out a shutdown on the PABX to take into account the new tones.

Chapter
16 Voice guides and music-on-hold
16.1 Overview
A voice guide consists of one or more voice messages.
The purpose of the voice messages is to assist users with phone operation and/or provide users with
information.
The CCD (Contact Center Distribution), integrated Automated Attendant and many other phone
features use voice messages.
Each voice message is a recording of a given text.
The messages corresponding to voice guide No. 3, for example, differ according to the language used:
• “Votre manoeuvre est enregistrée, vous pouvez raccrocher” in French.
• "Your request has been recorded, you may now hang up" in English.
• “La seva maniobra ha quedat registrada, ja pot penjar” in Catalan.
16.1.1 Types of voice messages

Voice messages may be:
1. Static: cannot be modified by the user:
• Generic: compatible with generic numbering plans and offered in at least 6 different languages
for all countries.
• Standard: adapted to a country with special requirements and/or a numbering plan differing from
the generic numbering plan.
• Specific: to an area or company.
Note:
A static message file contains one or more messages.
2. Dynamic: modifiable, recorded by users and/or managers via a set or the AAS application.
Note:
A dynamic message file only contains one message.
3. External: music-on-hold (in most cases) played by a device external to the OmniPCX Enterprise.
16.1.2 Types of voice guides

Voice guides are either:
• System voice guides on page 268
• CCD agent presentation guides on page 269
• Variable chained voice guides on page 269
16.1.2.1 System voice guides

There are three types of system voice guides:
• Voice guides consisting of one single voice message
They provide audio information in a maximum of eight different languages.
Each voice guide is mapped to one voice message number per language
• Static chained voice guides

Chapter 16 Voice guides and music-on-hold
They provide a sequence of audio information in a unique language.

Each voice guide is mapped to several voice message numbers: one per audio information.
• Multi-language voice guides
They providing an audio information in different languages.
Each voice guide is mapped to one voice message number per language.
As of R11.1, the maximum number of different languages is 57
16.1.2.2 CCD agent presentation guides

CCD agent presentation guides are played to the customer and/or CCD agent at the beginning of a
CCD communication.
Each voice guide is mapped to several voice message numbers: one per CCD agent.
Voice guide no. 538 is dedicated to the feature CCD Agent Presentation Guide
16.1.2.3 Variable chained voice guides

Some voice guides are made of several messages played one after the other. They are referred to as
"chained" voice guides.
1. Variable composite chained voice guides: composed of an internal message (static or dynamic)
followed by an external voice message.
Example:
The message: "Welcome to ALE International, please hold the line we're trying to connect you" is played before
real-time broadcast of a radio station.
2. Variable chained voice guides: composed of several messages (8 maximum), of which at least one
varies.
Example:
When programming an appointment reminder, the user programs the time at which he wants to be called on
his set. The set then confirms "Your request for an appointment at XX hour(s) YY minute(s) has been recorded
(where "XX" and "YY" are variables).
Before R11.1, some variable chained voice guide numbers were reserved for a specific usage:
• Voice guide no. 520: dedicated to RSI digit announcement. This entails that it should not be used
for another feature
It is mapped to the different variable voice messages, according to the language in use
Language no. First variable message no. Last variable message no.
1 3066 3075
2 3076 3085
3 3086 3095
4 3096 3105
5 3106 3115
6 3116 3125
7 3126 3135

Language no. First variable message no. Last variable message no.
8 3136 3145
9 3146 3155
10 3156 3165
11 3166 3175
12 3176 3185
13 3186 3195
14 3196 3205
15 3206 3215
16 3216 3225
• Voice guide no. 518 dedicated to CCD waiting queue position announcement. This entails that it
should not be used for another feature
It is mapped to the different variable voice messages, according to the language in use
Language no. First fix message Second fix First variable Last variable mes-
no. message no. message no. sage no.
1 3226 3227 3258 3317
2 3228 3229 3318 3377
3 3230 3231 3378 3437
4 3232 3233 3438 3497
5 3234 3235 3498 3557
6 3236 3237 3558 3617
7 3238 3239 3618 3677
8 3240 3241 3678 3737
9 3242 3243 3738 3797
10 3244 3245 3798 3857
11 3246 3247 3858 3917
12 3248 3249 3918 3977
13 3250 3251 3978 4037

14 3252 3253 4038 4097
15 3254 3255 4098 4157
16 3256 3257 4158 4217
16.1.3 Reserved numbers and number of times a voice message can be called
As of R11.1, no reservation of voice message number applies.
Any voice message number from 0 to 5999 can be associated to one and only one of the following
voice guide types:
• System voice guides
• CCD agent presentation guides
• Variable chained voice guides
A given voice message number can be used in only one of the above three groups of voice guides.
However, this message number can be used several times in system voice guides or CCD agent
presentation guides.
In other words, the same voice message number can be assigned to several system voice guide
numbers or to different entry points of a given system voice guide, with a maximum number of uses set
to 100.
The same voice message number can be assigned to several CCD agents as presentation guide, with
a maximum number of uses set to 100.
In variable chained voice guides, a voice message number can be used once only.
These rules cannot be breached and any attempt to breach them results in a warning messages.
16.1.4 Related modules

Voice guide configuration and operations are described in::
• Detailed description (see Detailed description on page 271).
• Configuration procedure (see Configuration procedure on page 305).
• Configuration examples (see Configuration examples on page 316).
• Voice guide transfer (see Voice guide transfer on page 295)
• Descriptive table of voice guides (see Voice guide message content on page 283).
• Language correspondence table (see Voice guide indices by language on page 290).
• Maintenance (see Maintenance on page 326).

16.2.1 Static voice messages
16.2.1.1 Overview
The OmniPCX Enterprise is delivered with a CD-ROM containing:
• All available system (static) voice messages,
• Music-on-hold,
• A tool that enables selected files to be transferred to the Communication Server hard drive.
The voice messages are played from:

• OXE Media Services

• GD boards
• GA boards
• GPA2 boards
• Z20VG boards
• CPU6 boards
Two different voice message file formats are offered, depending on the board used to play them:
• G711 to play messages from GPA2, Z20VG, or CPU6 boards.
• ADPCM 32 to play messages from OXE Media Services, GD or GA boards with a virtual GPA
board.
16.2.1.2 Loading static voice messages

Various types of messages may be selected by the installer.
Note:
For installation of the transfer tool and the transfer operations to perform, see Voice guide transfer on page 295.
16.2.1.2.1 Reference to the numbering plan
Some voice guides refer to the numbering plan. At installation, a numbering plan is automatically
created according to PBX country code.
The voice messages selected must be compatible with this numbering plan.
Generic voice messages, for example, integrate the three following numbering plans:
• 4x
• 7x
• *x
Example:
Depending on the numbering plan selected, voice message No. 7 will be:
• 4x: “Your calls are forwarded, you can still make a call. To cancel forwarding please dial 41”.
• 7x: “Your calls are forwarded, you can still make a call. To cancel forwarding please dial 71”.
• *x: “Your calls are forwarded, you can still make a call. To cancel forwarding please dial *1”.
Caution:
Once the numbering plan has been established, modifying phone feature prefixes/suffixes may result in a
voice message providing users with incorrect information.
16.2.1.2.2 Selecting generic messages
Generic files (one per language) are transferred to the Communication Server hard drive:
• To the directory /DHS3ext/vgadpcm/flash/std for ADPCM files
• To the directory /DHS3ext/vg/flash/std for G711 files

CD-ROM
1. Generic voice guides
EN0
FR0 Call
DE0
IT0
Server
PT0
ES0
The downloaded files are for the following languages:
Language G711 file ADPCM file
English flashz2vg.EN0 vgadpcm.EN0
French flashz2vg.FR0 vgadpcm.FR0
German flashz2vg.DE0 vgadpcm.DE0
Greek flashz2vg.GR0 vgadpcm.GR0
Hungarian flashz2vg.HU0 vgadpcm.HU0
Italian flashz2vg.IT0 vgadpcm.IT0
Japanese flashz2vg.JP0 vgadpcm.JP0
Korean flashz2vg.KR0 vgadpcm.KR0
Portuguese flashz2vg.PT0 vgadpcm.PT0
Russian flashz2vg.RU0 vgadpcm.RU0
Spanish flashz2vg.ES0 vgadpcm.ES0
The music-on-hold is downloaded with these files.

16.2.1.2.3 Selecting standard messages
Standard files are transferred to the Communication Server hard drive:
• To the directory /DHS3ext/vgadpcm/flash/std for ADPCM files
• To the directory /DHS3ext/vg/flash/std for G711 files
The transfer tool reads the country code configured on the OmniPCX Enterprise, then transfers the
corresponding files for this country. The number of files available varies depending on country.
Example:
For an installation in Argentina, the transfer tool reads the OmniPCX Enterprise country code, then downloads the
three standard voice guide files for this country (with the on-hold-music).

Language G711 file ADPCM file File
Spanish (America) flashz2vg.ES2 vgadpcm.ES2 Standard (reference

3BA50188ALAA-01)
English flashz2vg.EN0 vgadpcm.EN0 Generic (the same as that in-

stalled when selecting generic
voice guides)
French flashz2vg.FR0 vgadpcm.FR0 Generic (the same as that in-

stalled when selecting generic
voice guides)
16.2.1.2.4 Selecting custom messages

Specific files are transferred to the Communication Server hard drive:
• To the directory /DHS3ext/vgadpcm/flash/custom for ADPCM files
• To the directory /DHS3ext/vg/flash/custom for G711 files
These messages correspond to a specific requirement and/or numbering plan specific to an area or
client company.
For a site on which both formats (ADPCM and G711) are used, the two files must have the same name
(mandatory).
16.2.1.2.5 Combined selection comprising custom messages
The installer works in successive steps:
• either to load generic voice messages, then the desired custom message(s),
• or to load standard voice messages, then the desired custom message(s).
16.2.1.3 Music-on-hold
The music-on-hold delivered on the voice message CD-ROM is transferred along with generic and
standard voice guides.
Caution:
For internal music to be played (broadcast), the following management operation must be performed:
• Delete tone 2 (the default waiting tone).
• Create voice guide 2 by assigning message No. 2 for each language.
You can replace this music by a specific (custom) music-on-hold file.
Important:
Up to R.8, the above is the only available music-on-hold management. As of R.8, music-on-hold is
enhanced with new static voice guide indexes (9 to 200). For more information, see Music-on-hold number
increase on page 275.
16.2.1.3.1 On OXE Media Services, GD and GA boards
The music-on-hold is stored in a file named adpcmmoh:
• Music-on-hold provided by ALE International: /DHS3ext/vgadpcm/flash/std/adpcmmoh
• Custom music-on-hold: /DHS3ext/vgadpcm/flash/custom/adpcmmoh
Note:
To replace the music-on-hold provided by ALE International, place a custom on hold music file (with the same
name) in the custom directory.

16.2.1.3.2 On Z20VG and GPA2 boards

The music-on-hold is stored in a file named flashmoh:
• Music-on-hold provided by ALE International: /DHS3ext/vg/flash/std/flashmoh
• Custom music-on-hold: /DHS3ext/vg/flash/custom/flashmoh
Note:
To replace the music-on-hold provided by ALE International, place a custom on hold music file (with the same
name) in the custom directory.
16.2.1.3.3 A specific case: the CPU6 board

When the flashmoh file is loaded to a CPU6 (8 MB of dedicated space), it is merged with the static
voice message file.
.custom/vgfilename or .std/flashz2vg.LNG
According to index management in board data
.custom/flashmoh or .std/flashmoh
Depending whether or not there is a file in the custom
directory
.custom/flashCPU6
16.2.1.4 Music-on-hold number increase

As of R8.0, you can use static voice guide files to increase the number of music-on hold. The number
of static voice guide indexes increases from 8 to 200. These new static voice guide indexes complete
the 8 already existing ones used for the 8 possible languages. Static voice guide files are referred to as
"specific files".
Each of these 200 specific files contains N number of different music-on-hold messages. N depends on
music duration and board type.
For more information, see Configuration procedure on page 305.
Note:
You must create specific files in G711 for the GPA2 board and in G723 for GD and GA boards.
16.2.2 Dynamic voice messages

16.2.2.1 Overview
• Dynamic voice messages are recorded (or modified) by the user:
• On a 4035x, 4037x, or Alcatel-Lucent 8/9 series set (see Recording dynamic messages from a
set on page 322).
• Via the AAS application (see Document [10] General Applications, Overview section in Alcatel-
Lucent Audio Station (AAS) chapter).
• As of R11.2, on a PC, using any compatible sound processing tool, such as, for example,
Audacity (open source software)

• A dynamic message (if there is one) replaces a static message with the same index number.
• Whatever the board used, all dynamic messages are stored in the directory /DHS3ext/vg/dhs.
• There is only one file for each dynamic message.
• Dynamic message file name format is x_y (mandatory): where x is message number (1 to 4 digits)
and y is message name (1 to 8 alphanumeric characters).
• As of R11.0.1 (K1.5), a dynamic message can be played on an OXE-MS
• The command vgfile all lists the dynamic messages selected in the system
16.2.2.2 Operation
Each message must first be assigned to one or more boards (GD, GA, CPU7-2, CPU8, Z20VG, GPA2).
During recording on a set, the last broadcast channel of one of these boards is used.
When a message has been assigned and recorded, it is available on the Communication Server in the
directory /DHS3ext/vg/dhs.
The message must be validated (enabled) to be played.
Several dynamic messages can have the same number (but different names). Only one message is
enabled at a given time (T).
Example:
Depending on the day of the week, one of the four following messages is enabled:
• File 2_Monday contains the message: “Hello, today, Monday, departments A and B are open to the public...”
• File 2_Tuesday contains the message: “Hello, today, Tuesday, departments B and C are open to the public...”
• File 2_day3456 contains the message : “Hello, today all departments are open to the public...”
• File 2_Sunday contains the message: “Hello, we are open Monday through Saturday...”
Active files are identified by the character ^ displayed after the file name.
Example:
Checking which dynamic voice messages are active on a board:
(1)pabx56> cd /DHS3ext/vg/dhs
(1)pabx56> ll
total 477
-rw-rw-rw- 1 mtcl tel 54650 Aug 30 2001 002_Monday
-rw-rw-rw- 1 mtcl tel 25942 Aug 31 2001 002_Tuesday
-rw-rw-rw- 1 mtcl tel 79012 Aug 31 2001 002_day3456
-rw-rw-rw- 1 mtcl tel 77364 Aug 31 2001 002_Sunday
16.2.3 External music

To use music-on-hold or voice messages played on equipment external to theOmniPCX Enterprise(CD
player, radio, etc.), no loading is required. However, the equipment must be certified by ALE
International and connected in accordance with the instructions provided.
These external recordings are continuously played by the Communication Server on a dedicated Time
Slot (TS). No file is associated to them. They operate independently.
An external music may be used as music on-hold or background music (the user calls a given number
to listen to the radio or any other external equipment connected to the OmniPCX Enterprise): see
Document [3] Overview section in Internal music channel.
16.2.4 Physical interfaces

16.2.4.1 On GD and GA boards
Voice message implementation requires a DSP component on the GD and GA boards.

To allow access to this DSP component, the Communication Server creates a virtual GPA board (used
for voice guides and conference) for each GD and GA board.
Note:
This virtual board is not seen in management.
An SLI board or AFU board (GD daughterboard) is used for external music: see External music on
page 303).
If external music is played via an AFU board, an AFU board must be installed on each GD board of the
Communication Server using this service.
16.2.4.2 On Z, CPUx, and GPA2 boards

A CPUx board also acts as a Communication Server.
The GPA2 board requires additional management for DSPs to be used.
External music can be connected to any Z board or to a CPU7-2 or CPU8 board.
16.2.4.3 On OXE-MS
The OXE-MS is an application running on an appliance server.
The application allows to play:
• Static voice guide (as of R11.0)
• Dynamic voice guide (as of R11.0.1 - K1.5)
As of R12.0, the OXE-MS can be used to record dynamic messages.

16.2.4.4 Summary
ACT Media
Gateway
INT IP INT-IP
IP network
INTOF Call
GPA2
Server
CPU6 Internal
voice messages
Internal
voice messages
DSP GA Internal
voice messages
INTOF DSP GD
AFU
Internal
Z20VG
voice messages
Internal External
voice messages voice messages
External
voice messages
Figure 16.1: Example configuration
In this example, the Communication Server is installed on a CPU6 board. An OmniPCX 4400 sys-
tem has been transformed into an OmniPCX Enterprise.
The CPU6 board (Communication Server) allows internal voice messages to be played (static and
dynamic). This board controls:
1. A remote ACT (via INTOF), on which a Z20VG board plays internal voice messages and music-
on-hold (from an external device).
2. An ACT Media Gateway, on which a GPA2 board plays internal voice messages.
3. A Media Gateway on an Alizé rack. The Media Gateway has a GD and a GA board.
An external device is connected to the AFU board (GD daughterboard) to play music-on-hold.
table 16.1: Summary of methods for playing voice guides
Type of voice guide Played by File type
Internal (static and dynamic) GA or GD board ADPCM32
CPU7-2, CPU8 boards G711
Z20VG board G711

Type of voice guide Played by File type
GPA2 board G711
OXE-MS
External music (or external voice SLI or MIX board, or AFU board on a GD None
guides) board
Z20VG, CPU7-2/CPU8 boards None
Variable and static chained voice GA or GD board ADPCM32

guides
CPU7-2/CPU8 board G711
Note:
The messages making up a chained
guide must all be on the same board. Z20VG board G711
GPA2 board G711
Chained voice guides: internal+exter- For the internal part (depending on the con- G711 or ADPCM32,
nal voice message figuration), all boards allow internal mes- depending on the
sages to be played. board used
Note:
The internal voice messages and external
music must be located in the same shelf. For the external part, all boards allow exter- No corresponding file
nal messages to be played.
16.2.5 Organization on a Media Gateway

16.2.5.1 Internal voice messages
The files are downloaded from the Communication Server to the boards used to play messages. They
are placed in different partitions on: .
• each GD or GA boards
• CPU7-2/CPU8, Z20VG or GPA2 board
• OXE-MS
16.2.5.1.1 File distribution on GD boards, GA boards and OXE-MS
Parti- Use Size Example files

tion
No.
1 Static messages 2 MB / 8 mn Standard Spanish voice messages (for Latin Ameri-

ca):
/DHS3ext/vgadpcm/flash/std/vgadpcm.ES2
2 Static messages 2 MB / 8 mn Generic or standard French voice messages:

/DHS3ext/vgadpcm/flash/std/vgadpcm.FR0
3 Static messages 2 MB / 8 mn New specific voice guides for music-on-hold:

/DHS3ext/vgadpcm/flash/custom

Parti- Use Size Example files

tion
No.
4 Static messages 2 MB / 8 mn Music-on-hold provided by ALE International:

/DHS3ext/vgadpcm/flash/std/adpcmmoh
5 Dynamic messages 2 MB / 8 mn As many files as desired, up to 8 mn total
16.2.5.1.2 File distribution on a GPA2 board

Files are coded in G711.
Partition Use Size Example files

No.
1 Static messages 6 MB / 12 mn Standard Spanish voice messages (for Latin

America):
/DHS3ext/vg/flash/std/
flashz2vg.ES2
2 Static messages 6 MB / 12 mn Generic or standard French voice messages:

flashz2vg.FR0
3 Static messages 6 MB / 12 mn New specific voice guides for music-on-hold:

/DHS3ext/vg/flash/custom
4 Static messages 6 MB / 12 mn Music-on-hold provided by ALE International:

/DHS3ext/vg/flash/std/flashmoh
16.2.5.1.3 File distribution on a Z20VG board


No.

America):
flashz2vg.ES2
16.2.5.1.4 File distribution on a CPU7-2/CPU8 board



No.

America):
flashz2vg.ES2
Reminder:
This file is concatenated with the music-on-hold file,
the result (concatenated), named flashCPU6, is
located in the directory /DHS3/vg/flash/
custom
2 Dynamic messages 1 MB / 2mn As many files as desired, up to 2 mn total
16.2.5.1.5 Number of simultaneous accesses per support

The maximum number of different internal voice messages played simultaneously by the same support
is given below.
Support Type Simultaneous messages
GD and GA Up to 16
CPU7-2/CPU8 Up to 15
GPA2 Up to 60
Z20VG Up to 13
OXE-MS Up to 120
(manageable)
16.2.5.2 External music

Music and external voice messages can be used as music-on-hold or waiting music on a set, and for
internal applications such as the Automated Attendant, routing to a guide, or the CCD.
The index numbers generally used are:
• Tone No. 2 (for an entry on an AFU, CPU7-2, or CPU8 board).
• Voice guides No. 171 to 180 (for an entry on an SLI or Z board).
16.2.5.2.1 Hardware required
• A device approved by ALE International.
• A two-pair cable to connect the power supply and low frequency (LF).
• An access point on the AFU board of a GD board, or on an SLI, Z, or CPU7-2/CPU8 board.
16.2.5.2.2 Connection
On an AFU or SLI board, the external device is connected to the front panel by an RJ45 cable (see the
External music on page 303).
For the other boards, see the External music on page 303.

Correct playback operation may be checked by performing a tone test (see Document [3], Basic
description in Voice guide and tone check) or making a consultation call from another set in the
installation. Volume may be adjusted on the external device or, when recording on an Alcatel-Lucent
Audio Station, adjusted during recording.
16.2.6 Recognizing and selecting voice guides

16.2.6.1 Voice guide indexes
Each voice guide is identified by an index number (see the Voice guide message content on page 283).
8 different messages (i.e. one for each language available to the manager) are associated with each
index number.
Example:
To play guide No. 3 (“Your request has been recorded, you may now hang-up ”) in language 2, message No. 271
will be played.
Index LG1 LG2 LG3 LG4 LG5 LG6 LG7 LG8
3 3 351 431 1024 1025 1026 1027

271
(For the correspondence between index numbers and the language number assigned by the manager, see the
Voice guide indices by language on page 290).
Note:
As there is no language distinction for music-on-hold, you create a voice guide number and assign a message to
this guide number instead of assigning a message to each language. For more information, see Managing voice
guides for music-on-hold on page 313.
Example:
The music-on-hold message (message number 1501) will be played with all languages.
Index LG1 LG2 LG3 LG4 LG5 LG6 LG7 LG8
1501 1501 -1 -1 -1 -1 -1 -1 -1
Value -1 indicates no message selected.
16.2.6.2 Selecting a guide according to system configuration

The Communication Server selects voice guides as follows.
If the voice message:

• Is only available on one board: it is played from this board.
• Exists in dynamic and static versions: the dynamic message is played.
• Is available on several boards in the same Media Gateway: the message on the board with the
greatest number of free channels is played.
• Is available on several boards in several Media Gateways: the message on the board of the same
Media Gateway as the requesting device is played.
16.2.7 Type of playback

Depending on the type of playback selected by the manager, the user will hear the voice message from
the start or while it is being played.

• If playback is set from the start, each time a user requests this guide and a broadcast channel is
free, the message is played from the start.
Remark:
If all broadcast channels are busy and the user requests a guide that is already playing, the user will hear the
message while it is being played and not from the start.
• If playback is not set from voice guide start, each time a user requests the guide and it is already
playing, the user hears the message while it is being played and not from the start.
If the user requests a guide that is not playing and all message broadcast channels are busy, the user
hears the backup tone for the guide requested.
16.2.8 Backup tone

For each voice guide, there is a corresponding backup tone that replaces it when it cannot be played.
Examples of backup tone use:
• Static or dynamic voice guide: no broadcast channel free for this guide, no message in the desired
language available, etc.
• External voice guide: equipment disconnected, interface board out of service, cassette deck
disconnected, etc.
16.2.9 Listening class

Users can choose not to hear voice guides during normal use and the administrator can verify one or
several tones or voice messages to test them (see the chapter on Voice guide and tone check in
document [3]).
16.3 Voice guide message content

16.3.1 Overview
An OmniPCX Enterprise comprises up to 2000 tone auxiliaries (tones + voice guides + specific voice
guides for music-on-hold). Each of these auxiliaries can be configured as a tone or voice guide or
music-on-hold. The manager can decide to replace any of these auxiliaries by the other.
The table below gives voice guide message content according to their index number. The prefix and
suffix numbers given in the table correspond to the generic numbering plans (see the Reference to the
numbering plan on page 272).
A second table gives the message numbers for each of the eight languages available to the manager
(see the Voice guide indices by language on page 290).
Reminder:
Exercise precaution when modifying phone feature prefixes and suffixes as these do not modify voice guides
referring to them. Cases where the user is prompted to enter a number which is no longer correct must be
avoided.
16.3.2 Descriptive table of voice guides

Index Name Content
2 MUSICATT “music”
3 GPMERAC Your request has been recorded, you may now

hang up.

Index Name Content
4 GPNUMCOD Please dial your personal code
5 GPMANAUT The number dialled is not authorized, please make

inquiries
6 GPCONUDE Please dial the extension number you require
7 GPRV_A Your calls are forwarded, you can still make a call.
To cancel forwarding please dial 41 (Forward can-
cellation Prefix, numbering plan 4x, see the De-
tailed description on page 271).
7 GPRV_B Your calls are forwarded, you can still make a call.
To cancel forwarding please dial 71 (Forward can-
cellation Prefix, numbering plan 7x)
7 GPRV_C Your calls are forwarded, you can still make a call.
To cancel forwarding please dial *1 (Forward can-
cellation Prefix, numbering plan *x)
8 GPRAPPEL You may request automatic call back by dialling 5

(Booking On Free Or Busy Set suffix).
9 GPVONUM Please dial your own extension number.
10 GPRAPEET You may request intrusion by dialling 4 (Intrusion

suffix) or automatic call back by dialling 5 (Booking
On Free Or Busy Set suffix).
11 GPRAPATT You may request automatic call back by dialling 5

(Booking On Free Or Busy Set suffix) or camp on
by dialling 6 (Busy Camp On suffix).
12 GPATTRAPEET You may request intrusion by dialling 4 (Intrusion

suffix), automatic call back by dialling 5 (Booking
On Free Or Busy Set suffix) or camp on by dialling
6 (Busy Camp On suffix).
13 GPEET You may request intrusion by dialling 4 (Intrusion

suffix).
14 GPNUMAF Please dial the project account code.
15 GPHEURDV Please enter the time required.
16 GPATT You may camp on by dialling 6 (Busy Camp On suf-

fix).
17 GPINACMOMEN The person you have called is unavailable, please

call back later.

Index Name Content
18 GPDONDIST_A Your extension is in do not disturb, you can still

make a call. To cancel do not disturb, please dial 42
(numbering plan 4x, Do not disturb prefix).
18 GPDONDIST_B Your extension is in do not disturb, you can still

make a call. To cancel do not disturb, please dial 72
(numbering plan 7x, Do not disturb prefix).
18 GPDONDIST_C Your extension is in do not disturb, you can still

make a call. To cancel do not disturb, please dial *2
(numbering plan *x, Do not disturb prefix).
58 FILM_EXT There is no extension corresponding to the number

dialled.
63 PBX_ABS You have left the group.
65 TONREVEIL This is the time you wished to be call back.
68 FILM_EET The extension you have called is protected against

intrusion.
71 GUIDAR1 “Greeting message n°1 (music-on-hold level 1)”.
72 GUIDAR2 “Greeting message n°2 (general forward guide)”.
73 GUIDAR3 “Greeting message n°3 (deterring guide)”.
74 to GUIDAR 4 à 30 “Greeting message n°N (from 4 to 30)”.

100
101 GPATTEET You may request intrusion by dialling 4 (Intrusion

suffix) or camp on by dialling 6 (Busy Camp On pre-
fix).
102 GPMESSYMP_A You have voice messages waiting, to consult your

mailbox please dial 43 (numbering plan 4x, Voice
mail consultation Prefix).
102 GPMESSYMP_B You have voice messages waiting, to consult your

mailbox please dial 73 (numbering plan 7x, Voice
102 GPMESSYMP_C You have voice messages waiting, to consult your

mailbox please dial *3 (numbering plan *x, Voice
103 GPATTRECH Please do not hang up, we are paging your corre-
spondent.

Index Name Content
104 GPSUFRECH You may page the person you have called by dial-
ling 7 (Paging Request suffix).
105 GPRACRECH We are paging your correspondent, you may hang-

up.
106 GPDISA Welcome to the DISA service, please enter your

DISA code number.
107 GPANNURAP_A You may cancel the automatic call back by dialling
44 (numbering plan 4x, Cancel auto call back on
busy prefix).
107 GPANNURAP_B You may cancel the automatic call back by dialling
74 (numbering plan 7x, Cancel auto call back on
busy prefix).
107 GPANNURAP_C You may cancel the automatic call back by dialling
*4 (numbering plan *x, Cancel auto call back on
busy prefix).
108 GUIDE_HOTEL You have used all of your prepaid deposit, please
extend your credit.
110 GUID_ATT Please hold, the operator will be with you shortly
139 GPSUFSYMP You may leave a message in the voice mail box of
your correspondent by dialling 8 (Voice Mail Mes-
sage Deposit suffix).
214 GPENVINF You are connected to the paging system, please

enter your message.
215 GPMAINT “DTMF Q23 'A' digit for voice guides maintenance
purpose”
216 GPFAX You have a fax message awaiting collection.
217 GPUA_GUIDE You are in Guide mode. To see the main call prefix-
es, press the CONSULT key and then the CALL
key.
218 GPUA_KEYCONS To identify a key's content, please press the selec-

ted key.
219 GPUA_KEYPROG To program a key on your extension, please press

the selected key.
252 TONLEN37_A This extension is locked, to cancel please dial 45

(numbering plan 4x, lock prefix).

Index Name Content
252 TONLEN37_B This extension is locked, to cancel please dial 75

(numbering plan 7x, lock prefix).
252 TONLEN37_C This extension is locked, to cancel please dial *5

(numbering plan *x, lock prefix).
253 TONLEN38_A You have a call back request, you can still make a
call. To cancel please dial 46 (numbering plan 4x,
Consult call back list prefix).
253 TONLEN38_B You have a call back request, you can still make a
call. To cancel please dial 76 (numbering plan 7x,
253 TONLEN38_C You have a call back request, you can still make a
call. To cancel please dial *6 (numbering plan *x,
254 VG_PWD_EXPIRE Your password is or will be shortly outdated. To

change it please dial XXX
255 TONLEN40 To identify a key's content, please press the selec-

ted key ; to list the main codes, please press 1.
512 MULT_WAKE_UP_PROG To change the time press 1, to cancel it press 2, for

next programming press 3, otherwise hang-up
513 MULT_WAKE_UP_END To change the time press 1, to cancel it press 2,

otherwise hang-up.
514 VG_LNK_SAT The network link is busy, please try again later.
515 GP_ARS_WAIT_TONE The call you are trying to make will not be routed
via the cheapest network, either try again later or
wait to establish a connection.
516 VG_ACDV2_EMAIL_PROCESS You are in “E-mail” processing, you may hang up.
CCD application.
517 VG_ACDV2_CHAT_PROCESS You are in “chat” processing, you may hang up
518 VG_ACDV2_QUEU-ING_POSITION ACD V2 Dynamic chained VG giving CCD call

queuing position.
519 VG_ACDV2_CALLBACK_PROC You are in callback processing, you may hang-up.

CCD application only.
524 ACD2_PILNUM Please enter the pilot number.


Index Name Content
525 ACD2_PGNUM Please enter the processing group number.

526 ACD2_AGNUM Please enter your agent number.

527 ACD2_WITHDRAW You re withdrawn from the processing group.

528 ACD2_TRANS_ALLOW You may hang-up to transfer the call

529 ACD2_TRANS_FORBID This transfer is not allowed.

530 ACD2_WITHDR_TYPE Please enter the withdrawal type.

531 GPMMC_SUFF You may cancel the enquiry by dialling 2 (Consulta-

tion Call suffix), introduce your correspondent into
the conference by dialling 3 (Three-party Confer-
ence suffix) or hang-up to transfer the call.
532 GPMMC_ATT_TR You are being entered into a conference, thank you
for holding.
533 GPMMC_ATT_CV You are in a conference, thank you for holding.
534 VG_ACD2_WAIT_TIME ACD V2 predictive waiting time announcement.

The range of reserved messages used is: 4218 to
4499 and 5500 to 5999
Note:
As of R11.1, this range of messages is no longer
reserved and can be used for other purposes.
535 VG_ALARM_TIME_PROG Alarm time programming time confirmation.

4499 and 5500 to 5999
Note:

Index Name Content
536 VG_ALARM_TIME_EXPIR Alarm time programming time expiration.

4499 and 5500 to 5999
Note:
537 VG_ACD2_HD_PHONE Do you wish to validate the headphone mode?
538 VG_ACD2_AG_WELCOME_GUIDE ACD V2 agent welcome guide: This dynamic voice

guide is used to give the agent's welcome to an ex-
ternal caller in a CCD environment.
5499
Note:
539 GPBADCODE Incorrect code, please re-enter your personal code.
540 GPNEWPIN Your personal code is wrong or outdated, please

enter your new personal code.
541 GPCONFPIN Please confirm your new personal code.
542 GPNEXTCODE Please dial your next personal code.
543 GPSERVINAC The service is momentarily unavailable, please call

back later.
557 DIFF_LIST_NUMBER Please dial a list number.
558 DIFF_EMPTY_LIST Empty list, please redial.
559 DIFF_ANNOUNCE_NUMBER Please select a message or press #.
560 DIFF_ANNOUNCE_NUM_ERR Please select another message or press #.
562 VG_ACDV2_LOGON_STATE You are available to handle ACD calls

563 VG_ACDV2_WRAPUP_STATE You are in wrap-up state
564 VG_ACDV2_PAUSE_STATE You are in pause state
638 MTBAVG38 For the time being, you are not authorized to dial
this number.

16.4 Voice guide indices by language

16.4.1 Language correspondence table
Up to 2000 auxiliaries (tones + voice guides + new specific voice guides for music-on-hold) may be
defined in a given system. Up to 6000 messages (total) can be handled.
Voice guide content is given in the Voice guide message content on page 283.
Index Lg 1 Lg 2 Lg 3 Lg 4 Lg 5 Lg 6 Lg 7 Lg 8
2 2 2 2 2 2 2 2 2
3 3 271 351 431 1024 1025 1026 1027
4 4 272 352 432 1028 1029 1030 1031
5 5 273 353 433 1032 1033 1034 1035
6 6 274 354 434 1036 1037 1038 1039
7 7 275 355 435 1040 1041 1042 1043
7 PL1 (*) 1013 1012 1011 1010 1009 1008 1007 1006
7 PL2 (*) 965 964 963 962 961 960 959 958
8 8 276 356 436 1044 1045 1046 1047
9 9 277 357 437 1048 1049 1050 1051
10 10 278 358 438 1052 1053 1054 1055
11 11 279 359 439 1056 1057 1058 1059
12 12 280 360 440 1060 1061 1062 1063
13 13 281 361 441 1064 1065 1066 1067
14 14 282 362 442 1068 1069 1070 1071
15 15 283 363 443 1072 1073 1074 1075
16 16 284 364 444 1076 1077 1078 1079
17 17 285 365 445 1080 1081 1082 1083
18 18 286 366 446 1084 1085 1086 1087
18 PL1 (*) 1005 1004 1003 1002 1001 1000 999 998
18 PL2 (*) 957 956 955 954 953 952 951 950

58 58 917 916 915 914 913 912 911
63 63 287 367 447 1088 1089 1090 1091
65 65 288 368 448 1092 1093 1094 1095
68 68 289 369 449 1096 1097 1098 1099
101 101 290 370 450 1100 1101 1102 1103
102 102 291 371 451 1104 1105 1106 1107
102 PL1 997 996 995 994 993 992 991 990
(*)
102 PL2 949 948 947 946 945 944 943 942
(*)
103 103 292 372 452 1108 1109 1110 1111
104 104 293 373 453 1112 1113 1114 1115
105 105 294 374 454 1116 1117 1118 1119
106 106 295 375 455 1120 1121 1122 1123
107 107 296 376 456 1124 1125 1126 1127
107 PL1 989 988 987 986 985 984 983 982
(*)
107 PL2 941 940 939 938 937 936 935 934
(*)
108 108 297 377 457 1128 1129 1130 1131
110 110 298 378 458 1132 1133 1134 1135
139 139 299 379 459 1136 1137 1138 1139
214 214 340 420 500 1140 1141 1142 1143
215 215 215 215 215 215 215 215 215
216 216 300 380 460 1144 1145 1146 1147
217 217 301 381 461 1148 1149 1150 1151
218 218 302 382 462 1152 1153 1154 1155

219 219 303 383 463 1156 1157 1158 1159
220 220 304 384 464 1160 1161 1162 1163
221 221 305 385 465 1164 1165 1166 1167
222 222 306 386 466 1168 1169 1170 1171
223 223 307 387 467 1172 1173 1174 1175
224 224 308 388 468 1176 1177 1178 1179
225 225 309 389 469 1180 1181 1182 1183
226 226 310 390 470 1184 1185 1186 1187
227 227 311 391 471 1188 1189 1190 1191
228 228 312 392 472 1192 1193 1194 1195
229 229 313 393 473 1196 1197 1198 1199
230 230 314 394 474 1200 1201 1202 1203
231 231 315 395 475 1204 1205 1206 1207
232 232 316 396 476 1208 1209 1210 1211
233 233 317 397 477 1212 1213 1214 1215
234 234 318 398 478 1216 1217 1218 1219
235 235 319 399 479 1220 1221 1222 1223
236 236 320 400 480 1224 1225 1226 1227
237 237 321 401 481 1228 1229 1230 1231
238 238 322 402 482 1232 1233 1234 1235
239 239 323 403 483 1236 1237 1238 1239
240 240 324 404 484 1240 1241 1242 1243
241 241 325 405 485 1244 1245 1246 1247
242 242 326 406 486 1248 1249 1250 1251
243 243 327 407 487 1252 1253 1254 1255

244 244 328 408 488 1256 1257 1258 1259
245 245 329 409 489 1260 1261 1262 1263
246 246 330 410 490 1264 1265 1266 1267
247 247 331 411 491 1268 1269 1270 1271
248 248 332 412 492 1272 1273 1274 1275
249 249 333 413 493 1276 1277 1278 1279
250 250 334 414 494 1280 1281 1282 1283
251 251 335 415 495 1284 1285 1286 1287
252 252 336 416 496 1288 1289 1290 1291
252 PL1 981 980 979 978 977 976 975 974
(*)
252 PL2 933 932 931 930 929 928 927 926
(*)
253 253 337 417 497 1292 1293 1294 1295
253 PL1 973 972 971 970 969 968 967 966
(*)
253 PL2 925 924 923 922 921 920 919 918
(*)
254 254 338 418 498 1296 1297 1298 1299
255 255 339 419 499 1300 1301 1302 1303
512 512 875 874 873 872 871 870 869
513 513 868 867 866 865 864 863 862
514 514 341 421 501 1304 1305 1306 1307
515 515 342 422 502 1308 1309 1310 1311
516 516 861 860 859 858 857 856 855
517 517 854 853 852 851 850 849 848
519 519 814 813 812 811 810 809 808

521 521 807 806 805 804 803 802 801
524 641 642 643 644 1312 1313 1314 1315
525 645 646 647 648 1316 1317 1318 1319
526 649 650 651 652 1320 1321 1322 1323
527 653 654 655 656 1324 1325 1326 1327
528 657 658 659 660 1328 1329 1330 1331
529 661 662 663 664 1332 1333 1334 1335
530 665 666 667 668 1336 1337 1338 1339
531 669 670 671 672 1340 1341 1342 1343
532 673 674 675 676 1344 1345 1346 1347
533 677 678 679 1023 1348 1349 1350 1351
537 1019 1020 1021 1022 1352 1353 1354 1355
539 1018 910 909 908 907 906 905 904
540 1017 903 902 901 900 899 898 897
541 1016 896 895 894 893 892 891 890
542 1015 889 888 887 886 885 884 883
543 1014 882 881 880 879 878 877 876
557 557 847 846 845 844 843 842 841
558 558 840 839 838 837 836 835 834
559 559 833 832 831 830 829 828 827
560 560 826 825 824 823 822 821 820
562 562 800 799 798 797 796 795 794

563 563 793 792 791 790 789 788 787
564 564 786 785 784 783 782 781 780
638 638 738 778 818 819 817 816 815
(*) : PL1 or PL2 means alternate numbering plan 1 (7x) or 2 (*x) (see the Loading static voice
messages on page 272).

Note:
As there is no language distinction for music-on-hold, you only assign a message to the new value On Hold Music
voice guide instead of assigning a message by language. For more information, see Managing voice guides for
music-on-hold on page 313.
16.5 Voice guide transfer

16.5.1 Purpose
The following procedures describe:
• How to transfer static voice guides to the OmniPCX Enterprise hard drive from a CD-ROM or
Alcatel-Lucent Audio Station (AAS); see: Using the AAS software on page 295
• How to record and transfer dynamic voice guides via standard tools and FTP, see: Transferring
dynamic voice guides via FTP on page 300
Note:
This feature is available as of R11.2
The same software can be used to transfer both static voice guides and 4645 (e-VA voice mail) voice
guides to one or more OmniPCXs.
16.5.2 Hardware and software required

• The OmniPCX Enterprise Communication Server
• The installation CD-ROM
• A PC with a minimum configuration of:
• 17" screen (this makes installation easier)
• 10 Mb of free drive space
• Operating system: Windows
• Internet Explorer version 5 (or higher)
• An IP link between the PC (Ethernet connector) and the Communication Server (LAN connector).
16.5.3 Using the AAS software

16.5.3.1 Installing the transfer software
Note:
This software is part of the Alcatel-Lucent Audio Station (AAS) suite that enables creating customized voice guides
(see the Alcatel-Lucent Audio Station (AAS) - Overview).
1. Check that the version of Internet Explorer installed on the PC is version 5 (or higher).
Note:
If this is not the case, browse to the IE5 directory on the CD-ROM and double-click:
• ie5upd_en.EXE: to install this version in English
• Or ie5upd_fr.EXE: to install it in French
• Follow the instructions displayed on screen to complete the upgrade process
2. In the install directory on the CD-ROM, double-click the setup.exe file.
3. Confirm the selected installation directory by clicking Next.
4. In the last InstallShield Wizard window, click Finish.

16.5.3.2 Transferring voice guides

Reminder:
Voice guide file format varies depending on type of OmniPCX. It is G711 for the OmniPCX4400 and ADPCM32 for
the OmniPCX Enterprise. In other words, voice guide files are not interchangeable for the different types of
OmniPCX.
Double-click the desktop icon (or, via the Windows explorer, VoiceGuidesTFR.exe, in the
directory in which installation was performed).
Click Help to access the on-line help for use of the software.
16.5.3.2.1 Connecting to the OmniPCX Enterprise
1. Enter the IP address of the OmniPCX Enterprise.
Note:
If the remote node is declared in the host file of the PC, simply enter the node name.
2. Click Add host to add it to the list.
Note:
If the information entered is incorrect, select the address of the OmniPCX Enterprise to be modified and click
Remove.

3. In the newly created list, select the OmniPCX Enterprise to which the voice guides are to be
transferred.
4. Click Connection.
5. Enter the mtcl account password.
6. Click OK to confirm.
7. In the frame reserved for the OmniPCX Enterprise, the OmniPCX Enterprise country code is
identified by the software (this field cannot be modified).
16.5.3.2.2 Selecting the type of voice guides to download

A selection of standard voice guides (specific to a particular country) is available. If there is no file
corresponding to the country concerned on the CD-ROM, select generic voice guides.
16.5.3.2.2.1 Generic guides
1. In the section reserved to the OmniPCX Enterprise, select the type of file to be downloaded
(ADPCM for a Communication Server and G711 for an ACT Media Gateway).
Note:
In a system using boards requiring G711 and ADPCM files, two seperate downloads must be performed.
2. The hard drive directory in which generic guides will be stored is displayed automatically (/
DHS3ext/vgadpcm/flash/std or /DHS3ext/vg/flash/std according to the requested file
format)
If there are already files in the directory concerned, they will be shown in the Files field.
3. Click Transfer to OmniPCX.
Note:
The Communication Server hard drive will be purged automatically before transfer starts.
A specific language cannot be selected. All generic languages (and the music-on-hold provided by ALE
International) are downloaded automatically.
Language File extension
English EN0
French FR0

Language File extension
German DE0
Italian IT0
Portuguese PT0
Spanish ES0
Other language ...
According to board format requirements, these files are named vgadpcm.LNG or flashz2vg.LNG
(where LNG is the language used).
16.5.3.2.2.2 Standard guides
Note:
The OmniPCX Enterprise country code detected by the software determines which guides can be loaded. For
example, standard Turkish guides cannot be downloaded if the OmniPCX Enterprise country code is fr (France).
1. In the section reserved to the OmniPCX, select file type (ADPCM for a Communication Server and
G711 for CPU7-2/CPU8, GPA2 and Z20VG boards).
2. The hard drive directory in which standard guides will be stored is displayed automatically (/
DHS3ext/vgadpcm/flash/std or /DHS3ext/vg/flash/std according to the requested file
format))
If there are already files in the directory concerned, they will be shown in the Files field.
3. Check that the standard guides for the OmniPCX Enterprise reference country are present on the
CD-ROM.
Note:
16.5.3.2.2.3 Custom guides
Customized guides can be factory prepared on request and delivered on CD-ROM.
1. In the section reserved to the OmniPCX, select the target (Custom ADPCM Business System).
2. The hard drive directory in which standard guides will be stored is displayed automatically (/
DHS3ext/vgadpcm/flash/custom or /DHS3ext/vg/flash/custom according to the
requested file format).
If there are already files in the directory concerned, they are shown in the Files field.
3. In the standard Windows window, select the file to be transferred before clicking Open.
16.5.3.2.2.4 Audio station guides
Guides recorded by the client on the Alcatel-Lucent Audio Station (AAS) are loaded by selecting the
corresponding option. This type of transfer is described in the Audio Station documentation (see
Alcatel-Lucent Audio Station (AAS) - Overview).
16.5.3.2.2.5 Guides for the Hotel/Hospital application
A file contains Hotel/Hospital messages in two languages (language selection is configured in system
management).
1. In the section reserved to the OmniPCX, select the target:

• Generic (ADPCM or G711)

• or Standard (ADPCM or G711 if the country concerned requires a standard guide to be loaded
2. The hard drive directory in which standard (or generic) guides will be stored is displayed
automatically (/DHS3ext/vgadpcm/flash/std or /DHS3ext/vg/flash/std for CPU7-2/
CPU8, GPA2 and Z20VG boards).
If there are already files in the directory concerned, they will be shown Files field.
16.5.3.2.2.6 Guides for 4645 (e-VA voice mail)
These guides are specific to 4645 (e-VA) voice mail (OmniPCX Enterprise).
1. In the section reserved to the OmniPCX, select file type.
2. The (Communication Server) hard drive directory in which standard guides will be stored is
displayed automatically (/DHS3ext/vgeva)
If there are already files in the directory concerned, they will be shown Files field.
Note:
16.5.3.3 Deleting a file from the OmniPCX

For standard and generic files, any new loading operation overwrites existing files in the directory to
which these files are saved.
However, custom files are left in the OmniPCX Custom directory when a new loading operation is
performed.
To delete a given file from the OmniPCX, from the AAS select the file in the list and click Delete.
Figure 16.2: Example, selecting a file
If a file is deleted accidentally, simply repeat the loading procedure.

Reminder:
Generic files are not loaded individually, see Generic guides on page 297.
16.5.3.4 Saving files

Whatever the type of voice guide files loaded on the OmniPCX, they can be saved (file by file) on a PC
hard drive.
1. Select the file to be saved.
2. Click Copy to PC.
3. Select the directory to which the file is to be saved in the standard Windows window.

4. Click Save.
16.5.3.5 Renaming a file on the Communication Server

1. Select the file to be renamed.
2. Click Rename file.
3. Enter the new file name.
4. Click OK.
16.5.4 Transferring dynamic voice guides via FTP

As of R11.2, dynamic voice guides can be transferred, to the OmniPCX Enterprise, with standard FTP
tools.
Before you start, bear in mind that:
• This applies to dynamic voice guides only (one message per file).
• Only .wav files can be transferred to the OmniPCX Enterprise.
They must abide by certain rules: they are verified by the system during import operation and, in
main cases, the import is cancelled if the file is not compatible. You may use a GNU program, such
as Audacity or any software of your choice to obtain the correct .wav format.
Note about dynamic messages duration and files length:
• There is a hardware limitation depending on the coupler type (GD, GPA2,…): this limitation is based
on the whole capacity of the dynamic partition of the coupler. For example, one dynamic message
could take all the capacity, so that only one dynamic message would be supported on the coupler in
this case.
• As of R11.2, a limitation is added to prevent the treatment of too big dynamic messages. This
limitation forbids the import of dynamic files bigger than about 6 minutes (3072 kBytes). In this case,
import is rejected and an error is generated. The message "file too long error" is displayed.
To transfer voice guides to the OmniPCX Enterprise:
1. Save the voice guides on your PC
The requested format of the sound file is 8 kHz, 8 bits, mono, G711, A or µ law
The requested format of the file name is the same as for AAS: x_y (no extension)
where x corresponds to the message number (up to four digits) and y corresponds to the message
name (up to eight alphanumeric lowercase characters)
Note:
Special characters: * , $ are not allowed in the file name.
2. A hexadecimal editor can be used to verify the format of your input file
3. Ensure your input file contains:
• A header, with three fields:
Field name Size (in bytes) Description
General file type 4 “RIFF”
Length file 4 Length of file excluding the fields: General file type
and Length file
Application file 4 “WAVE”

type

• An FMT chunk, with three fields:
Fmt 4 “fmt”
Length 4
Application file 12 hexa (18 deci- WAVEFORMATEX (compressed)

type mal)
The structure of the Application file type field is as follows for dynamic voice guides:
1 for PCM
Wformat Tag 2 6 for G711 A
7 for G711 µ
Nchannels 2 1 for mono, 2 for stereo
NsamplesperSec 4 8000 for 8 kHz
NavgBytesPersec 4 Average data rate
NblockAlign 2
Wbits Persample 2
CbSize 2 Number of bytes of extra following

• A DATA chunk, with three fields
Chunk type 4 “data”
Length 4 Length of the voice stream
Application file X Binary samples of the voice stream

type
4. CRC chunk and MEMO chunk should be present in the final file:
The CRC chunk and the MEMO chunk (added when the files are processed by the AAS) are
automatically added by the OmniPCX Enterprise when the file is imported to the system.

table 16.2: CRC chunk
Chunk type 4 "crc"
length of crc 4 Length of crc
crc 4 crc calculation of data part
table 16.3: MEMO chunk
Chunk type 4 "memo"
length of MEMO 4 Number of bytes of the following string
string xxxxxxxxx This string can be read/written with mgr

5. Using any FTP transfer tool, transfer in bin mode your file(s) to the OmniPCX Enterprise, in the
directory: DHS3ext/vg/pc
6. Import the files, as explained: Managing dynamic voice messages on page 314
After their transfer in OmniPCX Enterprise, the dynamic voice messages can be verified using the
following tools:
• vg file command (for more information, see: Useful commands on page 326)
• ll command to launch in the directory: /DHS3ext/vg/pc
Example:
(205)frcolswoxe5a> ll
-rw-rw-r-- 1 mtcl tel 60645 Feb 19 2009 7_queen113^
60645 = 4 bytes (RIFF) + 4 bytes (length of Length) + length written in header (60637)
• vgstat command (for more information, see: Useful commands on page 326)
• Voice Guides system parameter (for more information, see: Managing voice guides on page 310)

Message numbers Voice guide number
Figure 16.3: Voice Guides system parameter example

• Tone test prefix dialed on a set followed by the voice guide number. For example, to verify the
message 275, the set must be in language 2 (see: Figure 2).
16.6 External music

16.6.1 Connecting an external device to a GD (AFU) or SLI board
16.6.1.1 Prerequisites
• An AFU board (GD board daughterboard).
• Or, an SLI board (or MIX board).
• An external audio device with its own power supply that can be connected to the OmniPCX by an
RJ45 cable. This can be a standard device (CD player, for example) or professional equipment for
this type of application.
Note:
It is preferable to use an output with adjustable volume.
16.6.1.2 Connectors
Caution:
Management (configuration operations) must be performed before any external music device is put into
service
• On an OmniPCX Media Gateway
Connection is to the front face of the SLI board or GD board (connection to the AFU
daughterboard).
On a GD board, connection is via the AUDCTRL output (normally-open control contact) and the
AUDIN input of the AUDIO-IN connector.
The recommended output impedance is 600 Ohms for the AFU board and the analog equipment.
For analog equipment (SLI board) connection is the same as for an analog set (pins 4 and 5).

Call
Server
SLI
54
On an AFU board, pins 1 and 2 of the RJ45 cable are used.
Call Server
AFU
2
1
16.6.2 Connecting an external device to a CPU7-2/CPU8 or Z20VG board

• One of the following boards: Z20VG, CPU7-2, or CPU8.
• A external audio device with its own power supply that can be connected to either a distribution
frame or directly to the OmniPCX. This can be a standard device (CD player, for example) or
professional equipment for this type of application.
Note:
It is preferable to use an output with adjustable volume.
16.6.2.2 Connection
16.6.2.2.1 CPU7-2/CPU8
Depending on the type of OmniPCX cabinet, connection is either:
• To the front panel (VH cabinet) via the connector provided:
RL AL MUSIC
CPU
1
SLOT 1
• Or, to the back panel (M2, M3, MI, and WM1 cabinets):
mainframe
CPU
CBRMA

Note:
On the WM1, connection is made directly from the unit (incorporated in the cabinet) to the splitter.
16.6.2.2.2 Z20VG
Depending on the type of OmniPCX cabinet, connection is either:
• To the front panel (VH cabinet) via a Patch Panel (for more information, see section VH rack - Patch
Panels in Document [24] Crystal Hardware Installation Manual)
Z
PATCH PANEL
• Or, to the back panel (M2, M3, MI, and WM1 cabinets).
mainframe
16.6.3 Management and verifications

See the Configuration examples on page 316 and the Configuration procedure on page 305.

16.7.1 Overview
To put voice messages into service:
• Download one or more generic, standard or custom voice messages.
• To play (broadcast) messages via a GPA2 board, declare the DSPs.
Note:
This operation is reserved to physical boards, it is not required for a virtual GPA board associated with a GD or
GA board.
• To configure available languages:
• Assign language index numbers to the available languages (or modify them).
• If required, configure correspondence between set display language and voice message
language.
• Assign a user language (association of a set display language and voice message language) to
system users and attendants.
• If specifically required, manage and create individual voice guides.
• If required, create new voice guide indexes and manage voice guides for music-on-hold.
• If required, manage assignment of a voice guide (or music-on-hold) to a device external to the
OmniPCX Enterprise.
• If required, manage voice message listening rights.

Note:
This specific point is described in the Voice guide and tone check - Configuration procedure,
• To configure dynamic voice messages:

• Create a prefix allowing messages to be recorded from a telephone set.
• Grant sets the right to record messages.
• Assign messages to the system boards used to play them.
• If required, adjust set recording level from the management tool.
• If required, manage dynamic messages .
16.7.2 Downloading files

For a generic, standard or custom voice message file to be played by the application (after installation,
see the Voice guide transfer on page 295), a voice guide index must be managed. A language index is
associated with this voice guide index. In turn, this language index is associated with a language in
management.
16.7.2.1 On OXE Media Services and GD/GA boards

1. Select: Shelf > Board > Voice Guide Index MG.
2. Review/modify the following attributes.
Shelf Address Enter shelf number.
Board Address Enter board number of the Media Gateway GD (or GA)
board.
Voice Guide Language Index Either enter the index number of the voice guide to be man-
aged:
• 1 to 8
• 2&3
• 4&5
• 6&7
Or, select one of the following:
• Music-on-hold
• Specific Voice Guide
Specific Voice Guide index Enter any value between 9 and 200 to use the new static
voice guide files.
Note:
This attribute is displayed only if you
select Specific Voice Guide.
3. Confirm your entries.
16.7.2.2 On a CPU/Z20VG board

1. Select: Shelf > Board .
Board Address Enter board number.

Voice guide language index Either enter the index number of the voice guide to be man-
aged:
• 1 to 8
• 2&3
• 4&5
• 6&7
Or, select Music-on-hold
16.7.2.3 On a GPA2 board

1. Select: Shelf > Board .
Board Address Enter board number.
Voice guide language index Either enter the index number of the voice guide to be man-
aged:
• 1 to 8
• 2&3
• 4&5
• 6&7
Or select one of the following:
• Music-on-hold
• Specific Voice Guide
Specific voice guide index Enter any value between 9 and 200 to use the new static
voice guide files.
Note:
This attribute is activated only if you
select Specific Voice Guide.
16.7.3 Declaring GPA board DSPs

Note:
This management is also valid for GPA boards, except virtual GPA boards (associated with a GD or GA board).
1. Select: Shelf > Board > GPA DSP program.
Board Address Enter the position of the GPA2 board in this ACT

Configuration Select (as desired):

• VG+4 Detections+Tones
• VG+4 VAD+Tones
• VG+2 Detections+2 VAD+Tones
• VG+Conf.+3 Detections+Tones
• VG+Conference+3 VAD+Tones
• VG+Conf.+2 Detections+1 VAD+Ton.
• VG+Conf.+2 Detections+1 VAD+Ton.
• VG+2 Conferences+2 Detections
• VG+2 Conferences+2 VAD
• VG+2 Conferences+Detection+VAD
• 3 Conferences+Detection+Tone
• 3 Conferences+VAD+Tone
16.7.4 Managing languages

This series of operations allows the following to be configured:
• Languages displayed on user sets
• The association between static voice guide index and a given language
• Voice message languages
• “User language”, i.e. combination of display language and voice message language
16.7.4.1 Selecting languages

1. Select: System
Display Languages
Display Language 0 Select a language from those available on the system. This
language refers to the language configured in Managing the
associated language on page 309.
.......... .........
Display Language 7 Idem.
User Languages
1- User language Select a user language from those offered.
1- Display Language Enter language number (0 to 7).
1- Voice Guide Language Enter language number (1 to 8).
.......... .........
9- User language Select a user language from those offered.

9- Display Language Enter language number (0 to 7).
9- Voice Guide Language Enter language number (1 to 8).
Language For Screen/Printout Enter language number (1 to 16).
X121 Area Enter a value between 0 to 12..

Note:
For terminals which automatically transmit dialing
16.7.4.2 Managing the associated language

1. Select: System > Flash Voice Guide Configuration
Flash VG Number Enter the index number of the language concerned (1 to 8).
Language Choice Select the desired language for this language number.
Reminder:
Up to 8 different languages can be configured on the same
system.
Note:
To download a custom (specific) file, select Specific file, for
music-on-hold, select Music-on-hold.
Flash File Enter the name of the file to be downloaded. If the file is not
in directory /DHS3ext/vgadpcm/flash/custom (or /
Note:
This attribute is only displayed for DHS3ext/vg/flash/custom for an ACT Media Gate-
download of a custom file or music-on- way), management will not be allowed.
hold, if the "Specific (Custom) File"
attribute is selected for the display
language and voice message language
combination.
16.7.4.3 Managing static voice guides for music-on-hold

For music-on-hold, you can:
• Create new static voice guide indexes (9 to 200)
• Consult/modify all voice guide indexes (1 to 200)
1. Select: System > Flash Voice Guide Configuration > Create
Flash VG Number Enter a voice guide identification number (9 to 200).

4. Select once again: System > Flash Voice Guide Configuration

Flash VG Number Enter the static voice guide index number (1 to 200).
Language Choice Select Specific file.
Flash File Enter the name of the file to be downloaded. If the file is not
in directory /DHS3ext/vgadpcm/flash/custom (or /
DHS3ext/vg/flash/custom for an ACT Media Gate-
way), management will not be allowed.
16.7.4.4 Assigning a user language to a set

Reminder:
User language is the combination of set display language and voice guide playback language.
1. Select: Users
2. Review/modify the following attribute
Language ID Enter a "user language" number defined above (from 1 to 9).

16.7.4.5 Assigning a user language to an attendant set

Assigning a "user language" (display language + voice guide playback language) to an attendant set.
1. Select: Attendant > Attendant sets
Language ID Enter a user language number defined above (from 1 to 9).

16.7.5 Managing voice guides

1. Select: System > Voice Guides.

Voice Guide No. Enter voice guide identification number. To select a new
guide number, refer to the list of voice guides (Voice guide
message content on page 283).
Note:
Dynamic voice guides reserved for CCD and Appointment reminder
are:
• n°518: CCD waiting queue position
• n°535: Program Appointment Reminder
• n°536: Appointment reminder: expiration
• n°538: CCD agent welcome guide
As of R11.1, this restriction no longer applies.
Function Select (as desired):

• Single-message Voice Guide for a static message
• Z Voice Guide (analog equipment) for an external voice
guide (SLI board or other analog board)
• Dynamic chained Voice Guide
• Static chained Voice Guide
• Intern+extern chained voice guide for a chained
message comprising a static message and an external
guide
• Multi-language message (in version prior to R11.1
reserved for CCD)
• Music On Hold Voice Guide
Voice Guide Start YES: the voice message is played from the start of the mes-
sage.
NO: the voice message can start to play anywhere in the
message.
Backup tone Enter the number of the tone to be used when the voice
message fails to play.
Flash message for language 1 Note:

Static guides (not chained) only.
..........
Enter a message number (value between -1 and 5999), see
Flash message for language 8 the Voice guide indices by language on page 290. Value -1
indicates no message selected.

Dynamic function Note:

Variable (dynamic) chained guides only.
Select:
• Program Appointment Reminder, to confirm to the user
that he has entered appointment time correctly
• Appointment reminder: expiration, to inform the user of
appointment reminder expiration time
• CCD waiting time announcement: informs the caller of
waiting time.
• CCD agent welcome guide: enables the agent that the
call reaches to be identified.
• CCD waiting queue position: informs the external caller
of his position in the waiting queue.
• RSI Digit Announcement
Number of connections Note:

Variable chained guides only
This message will be played to the caller n times
Listening class 0 Note:

Static guides (chained or not) only.
..........
Select "Forbidden" or "Allowed with no control" to forbid
Listening class 7 users from hearing or allow users to listen to the guide de-
pending on their listening class. ALE International recom-
mends that:
• Class 0 be set to "Forbidden"
• Class 7 be set to "Allowed with no control"
Flash message number Note:

Internal-external chained guides only
Z VG External message number
Enter the number of the static message and external voice
guide to be chained.
Language Set Note:

Multi-language guides only, reserved for CCD.
Language Number
Use the [ Add ], [ Delete ], [ Next ], [ Previ-
Message Number ous ] options to add other languages and/or other messag-
es to each guide.
Equipment Address Note:

External guides on analog equipment only
Shelf Enter:
Board • The number of the Media Gateway in which the board is
Terminal installed.
• The analog interface slot in the shelf (between 0 and 13
or 0 and 27 depending on shelf capacity)
• The equipment slot in the interface (between 0 and 23)

For more information on configuring variable chained guides and multi-language guides, see the
documentation relating to CCD configuration.
16.7.6 Managing voice guides for music-on-hold

1. Select: System > Voice Guide > Create
Voice Guide Number Enter voice guide identification number. To select a new
guide number, see Music-On-Hold commands on page 331.
Function Select Music On Hold Voice Guide .
Music On Hold Voice Guide Enter message identification number.

Note:
Message identification number could be the same or different from
voice guide number.
16.7.7 Managing music and voice guides on external equipment

16.7.7.1 Connection to a CPU7-2/CPU8 board or an AFU board
The external piece of equipment is directly connected to the CPU7-2/CPU8 board or AFU board (GD
daughterboard), for more information, see the External music on page 303.
ALE International recommends using tone No. 2 (see the Principle on page 196).
Caution:
If the music-on-hold to be used is not the system background music (see the Internal music channel -
Overview), the background music is associated with a voice guide and not tone 2.
Reminder:
An AFU board (and external device) must be connected to all Communication Server GD boards using this
service.
1. Select: System > Tones
Tone No. 2
Combined basic tone Use [ Add ], [ Delete ], [ Next ], [ Previous ] to

check and confirm options as follows.
Tone No. Enter 31.
Duration This attribute does not affect the playback of music-on-hold.

16.7.7.2 Connecting equipment to an SLI board

To avoid any malfunction, equipment management must be configured before connecting it to the
OmniPCX Enterprise and powering it up.
ALE International recommends that guides No. 171 to 180 be used (preferably).

Note:
Music-on-hold played from an SLI board may be common to all GD boards in the same system.
See Managing voice guides on page 310.
Note:
For this music-on-hold to be played on the trunk group and when waiting for attendant, you must:
1. Configure the object: Entities.
Voice Guide
Waiting Guide Enter the number of the message (music-on-hold) to be

played.
Attendant Waiting Guide Enter the number of the message (music-on-hold) to be

played.
16.7.8 Managing dynamic voice messages

16.7.8.1 Creating the recording prefix
1. Select: Translator > Prefix Plan.
Number Enter a prefix number compatible with the dialing plan.
Prefix Meaning Select Local features.
Local Features Select

Recordable Voice Guides
16.7.8.2 Granting set rights

1. Select: Classes of service > Phone Features COS.
Phone Features COS Enter the COS ID of the set on which dynamic voice mes-
sages are to be recorded.
PCX Services
Recordable Voice Guides Enter 1 to grant sets with this COS the right to record and
download dynamic voice guides. Enter 0 to block this fea-
ture.
16.7.8.3 Assigning a message to a board

Before recording, each message must first be assigned to one or more boards (OXE-MS,GD, GA,
CPU7-2/CPU8, GPA2, Z20V ).

If you experience problems doing this, use the option System > Dynamic voice guides > Failure
reason (see the Dynamic voice messages on page 333).
1. Select: System > Dynamic Voice Guides > Assignment.
VG Sub-message No. Enter the number of the message to be created.
ACT-Board Use the [ Add ], [ Delete ], [ Next ], [ Previ-

ous ] options
to specify the address of each board to be used to play the
guide.
Note:
To play dynamic voice guides using compressors of an OXE Media
Services system (OXE-MS), it is recommended to create the OXE-
MS on the lowest shelf (position 2) and the controller board (INTIP3
or GD3) on the next shelf (respectively position 3 or 4).

Caution:
For the manager to have maximum flexibility, any message number (0 to 5999) can be used to name a file.
Make sure that dynamic voice guides that are not intended to replace static voice guides have a different
number.
16.7.8.4 Adjusting set volume

1. Select: System > Other System Param.
VG Recording Gain from a UA set Enter a value between 0 and 4 (see list below).
Level Gain in dB
0 -5
1 -2,5
2 0
3 2,5
4 5
3. Confirm your entry.
16.7.8.5 Managing dynamic voice guide files

The following applies to voice guides transferred via the Audio Station application or FTP (see Voice
guide transfer on page 295):
16.7.8.5.1 Importing files
Files are first transferred using the AAS transfer tool. They are stored on the Communication Server in
the directory DHS3ext/vg/pc. The following operation allows files to be transferred to the directory
DHS3ext/vg/dhs to make them available for use.

1. Select: System > Dynamic Voice Guides.

2. Review/modify the following attribute.
Import new files in database Select this option.

If the file(s) was transferred via FTP (and not the AAS), the Header chunk is modified, a CRC chunk
is inserted and a default date and hour memo chunk is added to the file. After further controls by the
system, the dynamic voice guide files is saved in /DHS3ext/vg/pc
A copy of the original file is automatically made in /DHS3ext/vg/tmp, useful in case
troubleshooting is needed (analysis of faulty files with an external hexa editor).
16.7.8.5.2 Cleaning the transfer directory
It is possible to clean up directories DHS3ext/vg/pc and /DHS3ext/vg/tmp, for example after a
successful transfer, or after analysis of faulty files.
1. Select: System > Dynamic voice guides > Clear import directory.
2. Review/modify the following attribute.
Clear Import directory Select this option.

This operation deletes files in /DHS3ext/vg/pc and /DHS3ext/vg/tmp
If transfer is incorrectly or only partially performed, only the faulty files can be deleted.
1. Select: System > Dynamic voice guides > Remove invalid files from database
Remove invalid files from data- Select this option.

base
16.8 Configuration examples

16.8.1 Overview
This example is for loading of guides to an OmniPCX Enterprise delivered to a French company
subsidiary in Turkey.
The Communication Server (CS board) is declared as shelf No. 0.

The main CPU of the Communication Server is in slot 6.
The OmniPCX Media Gateway is declared as shelf 4.
The GD board of the Media Gateway is in slot 0.
The following operations are performed prior to voice guide installation on this system:
1. Standard Turkish voice message file downloaded to the Communication Server, using the transfer
tool included on the CD-ROM (mandatory).
2. Custom voice message file downloaded (to French play voice guides corresponding to the Turkish
numbering plan). This file was previously ordered from ALE International.
3. Management of languages associated with the voice guide indices.

4. Management of display and voice message languages (user language) according to types of sets
(user and attendant).
5. Declaration of two voice guide indices on the Media Gateway.
6. Declaration of internal music-on-hold.
7. Management of tone 2 for connection of external music-on-hold to the OmniPCX Enterprise.
8. Connection of a CD player to the AFU board (GD daughterboard)
9. Creation of a chained voice guide: static + external and declaration of routing to guide for a given
set in the system.
10.Language added.
11.Declaration of music-on-hold with specific files.
16.8.2 Loading voice messages

• Load standard voice messages for Turkey (see the Voice guide transfer on page 295).
• Check available drive space (in directory usr7), using the command df-v
Example:
df -v
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda5 149126 54425 87001 38% /
/dev/hda6 396623 214761 161381 57% /usr2
/dev/hda7 198313 80912 107150 43% /usr3
/dev/hda8 1923520 55856 1769956 3% /usr4
/dev/hda13 297851 82377 200096 29% /usr7
• Load specific files (custom guides), see the Voice guide transfer on page 295.
16.8.3 Managing system languages

Note:
The following management is given for information. Language management (depending on country of installation)
is automatically performed with the creation of the PCX database.
16.8.3.1 Selecting languages

1. Select: System
Display Languages
Display Language 0 Turkish
Display Language 1 French
User Languages
1- User language Turkish
1- Display Language 0
1- Voice Guide Language 1
2- User language French
2- Display Language 1

2- Voice Guide Language 2

4. End
16.8.3.2 Assigning a user language to a user set

As the OmniPCX Enterprise is Turkish, by default all sets in the system have a display in Turkish and
voice messages are in Turkish. The following management is required for a French-speaking
manager's set only.
1. Select: Users
Language ID 2
16.8.4 Managing the languages associated with the index

Note:
The following management is given for information. Language management (depending on country of installation)
is automatically performed with the creation of the PCX database.
16.8.4.1 Loading files

1. Select: System > Static Voice Guide.
Static voice guides index 1
Language Turkish
Caution:
The file must be in the directory /
DHS3/vgadpcm/flash/std.
4. Select once again: System > Static Voice Guide.
Language Specific file
File name Name of the file to be downloaded.

Caution:
The file must be in the directory /
DHS3ext/vgadpcm/flash/
custom.
16.8.4.2 Declaring voice guide indices

Two indices are created.

Shelf Address 4
Board Address 0
Instance VG 1

4. Select once again: Shelf > Board > Voice Guide Index MG.
Shelf Address 4
Board Address 0
Instance VG 2

16.8.5 Defining internal music

The standard ALE International music-on-hold is to be used before an external device is connected to
the AFU daughterboard of the GD.
Reminder:
For ACT Media Gateway boards, the same management is performed at Shelf > Board level.
Shelf Address 4
Board Address 0
Instance VG 3
Static voice guides index Music-on-hold

Note:
To check that the file has been transferred correctly to the
Communication Server, use the command ls -l (or ll) in the
directory /DHS3ext/vgadpcm/flash/std.

Any voice guide index can be used to play this. However, it is easiest to use tone 2 (intended for this).
Note:
The simplest method of playing the music-on-hold is, therefore to:
1. Delete tone 2.
2. Create voice guide No. 2 (single message guide) with No. 2 as message number for all languages to be
managed on the system.

16.8.6 Using external music-on-hold

As tone 2 is generally used for external music, manage the tone as follows.
1. Delete voice guide No. 2 (see previous paragraph).
2. Create tone No. 2.
a. Select: System > Tones
b. Review/modify the following attributes
Tone No. 2
Combined basic tone
Tone No. 31
Note:
Tone number must be 31
Duration This attribute does not affect music-

on-hold playback.
c. Confirm your entries
16.8.7 Connecting a CD player to the AFU daughterboard

After the above management operations have been performed, connect the external CD player as
described in the External music on page 303. This music replaces the standard ALE International
music-on-hold.
16.8.8 Creating a greeting message for routing to a set

When a caller tries to reach the set concerned, he will get a greeting message followed by a brief
musical extract.
16.8.8.1 Creating a chained voice guide: internal + external

1. Select: System > Voice Guides.
2. Review/modify the following parameters
Voice Guide Number 561
Function Select:
• Intern+extern chained voice guide for a
chained message comprising an internal
message and external guide.
Voice Guide Start No: the voice guide can start to play anywhere in the
message.
Backup Tone 56
Internal-external chained
voice guide
Internal message number 20

External message number 2

16.8.8.2 Defining a greeting guide for incoming calls

Up to 254 different greeting guides can be created.
1. Select: System > Incoming Greeting Guides
2. Review/modify the following parameters
Voice guide number 1
Voice guides 561
Guide Timer 30
Routing Directory Number Directory number to which the call is directed after
playback of the voice guide.
4. Return to the start menu
5. Select: Translator > Prefix Plan
Number Enter the relevant DID number.
Prefix Meaning Select Incoming Call Greeting

Guide
Prefix Information Enter the number of the greeting

guide configured above.
16.8.9 Adding a language

To meet the needs of some English-speaking users and to be able to offer them voice guides in English
that comply with the numbering plan specific to Turkey, two solutions can be envisaged:
• Acquire the AAS application that enables the static guides delivered by default to be adapted to the
numbering plan and allows for custom static guides to be added to existing guides.
• Order an additional specific file from ALE International.
The files created will then be downloaded to the Communication Server as described in the Voice
guide transfer on page 295.
Note:
The standard Turkish file offers messages No. 7, No. 1013 and No. 965 (notification of set forwarding and the
option to cancel such forwarding by dialing a prefix) for the index for voice guide No. 7. These messages mention
3 prefixes that are different from the prefixes offered by the generic English file on the CD-ROM. In other words,
the generic English file is not compatible with the Turkish standard.
16.8.10 Declaring music-on-hold with specific files


Shelf Address 4
Board Address 0
Instance VG 4
Static voice guides index Specific Voice Guide
Specific Voice Guide index 9

16.9 Recording dynamic messages from a set

16.9.1 Overview
Dynamic voice messages are recorded by the user via a 4035x, 4037x or Alcatel-Lucent 8/9 series set,
or via the AAS application (see the Alcatel-Lucent Audio Station (AAS) - Overview).
Reminder:
Voice messages may be:
• Static: loaded to the Communication Server hard drive in a single operation, cannot be modified by system
users (see the Voice guide transfer on page 295).
• Dynamic: can be modified, recorded by users and/or managers via a set or the AAS application.
16.9.2 Recording from a set

The following paragraphs describe the series of set displays obtained during creation of a dynamic
voice message.
A dynamic voice message is created in three steps:
• The audio sequence is recorded from the set (after a message number has been created in
management).
• The file is created (the audio sequence is assigned the message number).
• The file is downloaded to the Communication Server.
Note:
A set linked to an OXE-MS cannot be used to record dynamic messages.
16.9.2.1 Recording the audio sequence

On the set, enter the dynamic voice message management prefix.
Note:
A message cannot be recorded if a number for it has not been previously assigned to at least one board.

VG Message Management : Main Menu

Record Downld
To download an existing file
Enter the number of the message Recording of VG message number: 500

to record (e.g. 500) Apply Cancel
Maximum recording duration : 914 sec

Apply Cancel
Recording of VG message number: 500

Start Cancel
Speak to record this message Recording of VG message number: 500

Stop Cancel
Recording of VG message number: 500 3s

Listen Rstart Apply Cancel
The information on maximum recording time is for the shortest time available on the different boards to
which the message is assigned.
When the audio recording has been confirmed, the set offers either to create a new file or to replace an
existing file (when appropriate).
16.9.2.2 Creating a new file

The first screen shown below is displayed when the audio recording is confirmed.

File name for VG message number : 500

NewFil List Apply Back
NewFil List To replace an existing file
Enter the file name :

Apply List Delete Erase Back
Enter the name of the file (e.g. "greeting1")
Enter the info :

Apply Delete Erase Back
Enter "info" on the message (e.g. "re-routing to

attendant"). Apply to record the file on the Call
Server
"greeting1" created for Message No.: 500

Apply
Note:
“Info” is a brief description of the message. This is not mandatory but helps the user to identify message content.

16.9.2.3 Replacing an existing file
File name for VG message number : 500

NewFil List Apply Back
greeting2
Apply NewFil Prev. Next Back
greeting1
Apply NewFil Prev. Next Back
Confirm the replacement of greeting1?

Yes No
Enter the info:

Apply Delete Erase Back
Enter "info" for this file (e.g. "re-routing to attendant)

Apply
The new recording will overwrite the old recording in Communication Server memory.
16.9.2.4 Downloading to the board(s) used to play the guide

Download can be performed immediately after the new file has been created (or an existing file
replaced). It can also be performed directly from the main menu.
It allows a dynamic voice message to be enabled (on all boards configured in management), the
message can have the same number as another dynamic voice guide.
Downloading immediately after recording the audio sequence


Apply
Do you want to select this VG file?

Yes No
Back to file selection (see

next figure)
"greeting1" selected for msg nbr : 500

Menu
Back to main menu
Downloading from the main menu
VG Message Management : Main Menu

Record Downld
indicates file rank in the list

Enter file name (e.g. "greetingl2") and total number of files with
the same number
greeting2 [Selected] 02/03

Dselct Delete Prev. Next Back
Show desired file (ex. "greeting3")
greeting3 03/03
Select Delete Prev. Next Back
greeting3 selected for msg nbr : 500

Menu
This allows several guides to be downloaded simultaneously.
16.10 Maintenance
16.10.1 Useful commands
Several voice guide-specific maintenance commands can be run on the OmniPCX system terminal
(under the mtcl account).
• cplstat <cristal (0–19)> <cpl (0–28)>: returns board state.
Example:
cplstat 1 0

Logic coupler type : INTMGD (77);

MAO coupler type : GD ;
Coupler state : IN SERVICE ;
Protocol country : FRA ( 5);
Ghost equipment number : 10521 ;
First terminal number : 0 ;
Last terminal number : 0 ;
Specific data of the INT boards

Opposite crystal : 19
Opposite coupler : 1
Role part : 0
State of the link : 1
Signalling transmission mode : 0
Used TS : 0
Specific data of the IP boards

Board IP address (IPv4) : 192.168.65.172
Netmask IP : 255.255.255.0
Default Gateway IP address : 192.168.65.1
Board Ethernet Address : 00:80:9f:2e:2d:ee
IP quality of service : 0
Current base UDP port : 0
Base UDP port for next initialization : 32000
Compression available for Gateway : 6
associated cpl : 27
Information about virtual Gpa :
Logic coupler type : CPL_GPA ;

MAO coupler type : GPA FICTIF ;
Protocol country : FRA ( 5);

Ghost coupler neqt : 10522 ;
Detection equipements on this coupler :
- first dsp 0 terminal number : 0 ;
- last dsp 0 terminal number : 15 ;
- dsp 0 program : VG_PRG ;
- dsp 1 program :
CONFERENCE_PRG ;
- dsp 2 program : DTO_R2_PRG ;
Voice guide equipements on this coupler :
- voice guide state : VG_STABLE ;
- first vg terminal number : 0 ;
- last vg terminal number : 15 ;
More information about voice guide may be displayed by vgstat 1 27
Type of tone emitter registered on this coupler : TONE_R2;
Tone emitter state on this coupler : EM_R2;
• downstat <cristal (0–19)> <cpl (0–28)>: displays which binary files (including voice messages) are
being downloaded to the system.
• dspstat: displays DSP use for GPA boards (virtual and GPA2)
Example:
Logic coupler type : CPL_GPA ;
MAO coupler type : GPA FICTIF ;
Dsp number : 0;
Enable types of detection :
- VOCAL GUIDANCE
+----------------------------------------------------------------+
| dsp neqt | dsp term | dsp state |calling neqt|calling dir nb|
|----------------------------------------------------------------|
| 444 | 0 | | | |
| 445 | 1 | | | |
| 446 | 2 | | | |

| 447 | 3 | | | |
| 448 | 4 | | | |
| 449 | 5 | | | |
| 450 | 6 | | | |
| 451 | 7 | | | |
| 452 | 8 | | | |
| 453 | 9 | | | |
| 454 | 10 | | | |
| 455 | 11 | | | |
| 456 | 12 | | | |
| 457 | 13 | | | |
| 458 | 14 | | | |
| 459 | 15 | | | |
+----------------------------------------------------------------+
As the remainder of this example describes use of board DSPs for conferences and tones, it is not
presented here.
• tabag to display CCD agent presentation guides. As of R11.1, this command also displays the
presentation message number
Example:
tabag
+------------------------------------------------------------------+
| Ag nb | Lognum | Dir nb | Neqt| Type | Name | Msg nb
|
|------------------------------------------------------------------|
| 1 | 20 | 2501 | -1 | SU | FOUR SuMu01 | -1 |
| 2 | 21 | 2502 | -1 | AG | FOUR AgMo02 | 4502 |
| 3 | 22 | 2503 | -1 | AG | FOUR AgMu03 | 4503 * |
| 4 | 23 | 2504 | -1 | AG | FOUR AGMp04 | 4503 |
+------------------------------------------------------------------+
A star displayed after the message number indicates that the message is activated
• vgton (alone or followed by several message numbers): gives voice guide or tone name and type.
Example:
vgton 1 7 534
+-------------------+-------------------------+---------------------+
| tonality number | tonality label | tonality type |
+-------------------+-------------------------+---------------------+
| 1 | AUXTEACH |TONE |
| 7 | GPRV |multi-lng flash VG |
| 534 | VG_ACD2_WAIT_TIME |dynamic flash VG |
|-------------------+-------------------------+---------------------|
• vgstat <cristal (0–19)> <cpl (0–28)>: shows which dynamic and static voice guides are present on
a given board.
Example:
vgstat 0 2
+------------+------+------+------+------+------+------+------+------+------+
Guide Name Guide MsgLg1 MsgLg2 MsgLg3 MsgLg4 MsgLg5 MsgLg6 MsgLg7
MsgLg8
+------------+------+------+------+------+------+------+------+------+------+
GPMERAC 3 3 271
GPNUMCOD 4 4 272
GPCONUDE 6 6 274
GPRV 7 7-D 275
The latest line displays information on a dynamic voice guide:

• Message 7-D is played on a set for the voice guide 7 in language 1 (D for dynamic)
• Message 275 is played on a set for the voice guide 7 in language 2
• If the wave is for a user in language 2, about the voice guide 7, file name has the format:
275_yyyyyyyy

• vgemis (followed (or not) by voice guide number): shows the number of voice guides played at the
time the command is confirmed, with:
• Guide name and number.
• The address of the shelf, interface board, termination and equipment concerned.
• Guide language.
• The numbers of user equipment concerned by this playback of this guide.
Example:
vgemis 7
+------+-----------------+----+----+-----+------+---+-------------------------+
| guid | guide name | cr | cpl| term| neqt |lng| listeners neqt |
+------+-----------------+----+----+-----+------+---+-------------------------+
| 217| GPUA_GUIDE | 3 | 27 | 0 | 580 | 1 | 660 |
+------+-----------------+----+----+-----+------+---+-------------------------+
| 5 | GPMERAC | 3 | 27 | 0 | 580 | 1 | 661 |
+------+-----------------+----+----+-----+------+---+-------------------------+
| 3 | GPMANAUT | 3 | 27 | 0 | 580 | 1 | 684 |
+------+-----------------+----+----+-----+------+---+-------------------------+
• vgclass (followed (or not) by voice guide number): shows state of available voice guides: their
number, name, type of playback (at start of guide or while guide is being played) and their listening
class.
Example:
vgclass 7
------------------------------------------------------------------------------
| message | class number |
|------------------------------------------------------------------------------|
| number | label | start| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
|------------------------------------------------------------------------------|
| 7 | GPRV | no | no | no | no | no | no | no | yes | yes |
|------------------------------------------------------------------------------
• vgmsg (as of R11.1, this command replaces the vgmulti and vgmultilang commands
Usage:
• vgmsg aux to display all tones and guides
• vgmsg aux <aux-1> [<aux-2>] ... to display selected tones and guides
• vgmsg mono to display single-message voice guides
• vgmsg stat to display static chained voice guides
• vgmsg multi to display multi-language messages
• vgmsg msg to display all used MESSAGES
Examples:
vgmsg aux 1 13 1500 1600

------------------------------------+----+----+----+----+----+----+----+----+
|Aux | Name | Type |Lng1|Lng2|Lng3|Lng4|Lng5|Lng6|Lng7|Lng8|
|---------------------------------------------------------------------------|
| 1 | AUXTEACH| TONE | | | | | | | | |
| 13 | GPEET|Mono-message vo| 13| 281| 361| 441|1064|1065|1066|1067|
| 1500 | UNKNOWN|Static chained | To get more info, use option "stat" |
| 1600 | UNKNOWN|Multi-language | To get more info, use option "multi" |
----------------------------------------------------------------------------+
vgmsg mono
------------------------------------+----+----+----+----+----+----+----+----+
|Aux | Name | Type |Lng1|Lng2|Lng3|Lng4|Lng5|Lng6|Lng7|Lng8|
|---------------------------------------------------------------------------|
| 2 | MUSICATT|Mono-message vo| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
| 3 | GPMERAC|Mono-message vo| 3 | 271| 351| 431|1024|1025|1026|1027|
| 4 | GPNUMCOD|Mono-message vo| 4 | 272| 352| 432|1028|1029|1030|1031|
| 5 | GPMANAUT|Mono-message vo| 5 | 273| 353| 433|1032|1033|1034|1035|
----------------------------------------------------------------------------+

vgmsg multi
+------------------------------------------------------------+
|Aux :1600 | Name : UNKNOWN | Type : Multi-language|
+------------------------------------------------------------+
| Language Number | Message number |
|------------------------------------------------------------|
| 29 | 1609 |
| 18 | 1608 |
| 11 | 1607 |
| 47 | 1610 |
| 8 | 1606 |
| 5 | 1605 |
| 4 | 1604 |
| 3 | 1603 |
| 2 | 1602 |
| 1 | 1601 |
-------------------------------------------------------------+
vgmsg msg 271 282 1512 1603 3226 3317 4502 4503
-----------------------------------------------------------------------
| Msg | Status | Type | Guide | Agent
nb |
|---------------------------------------------------------------------|
| 271 | 0x0001 | Mono-message voice guide | 3 | |
| 281 | 0x0002 | To get more info, use command "vgmsg aux" |
| 1512 | 0x0001 | Static chained voice guide | 1510 | |
| 1603 | 0x0001 | Multi-language message | 1600 | |
| 3226 | 0x8000 |Dynamic chained voice guide | | |
| 3317 | 0x8001 | Error: should be used only as Dynamic chained |
| 4502 | 0x0100 | Agent presentation guide | | 2502 |
| 4503 | 0x0200 | To get more info, use command "tabag" |
-----------------------------------------------------------------------
• vgstart (followed (or not) by voice guide number): shows playback type of one or all voice guides.
Example:
vgstart 7
--------------------------------------------------------------------
| VG message number | VG message label |starting at the beginning|
|--------------------------------------------------------------------|
| 7 | no |
|--------------------------------------------------------------------|
• vgfile (followed by voice guide number or the mention all): only concerns dynamic voice guides (in
other words, those selected for playback), shows their CRC, size, number of pages and duration in
seconds.
Example:
vgfile 545
------------------------------------------------------------------------
| VG msg No | file name | crc | size (bytes) | pages | time (sec)|
|------------------------------------------------------------------------|
| 545 | cafe | 8288678 | 54566 | 14 | 7.2 |
|------------------------------------------------------------------------|
Where:
file name: this corresponds to the Y part of the X_Y file name of the corresponding dynamic
voice guide (same as for AAS - no extension)
CRC: value written in CRC chunck. This value is not only red but it is calculated on data stream and
coherency is verified during import
size (bytes): value written in DATA chunck
• wherevg (followed by voice guide number): shows their type and location in the system.
Example:
wherevg 7
voice guide number : 7 (GPRV)

+-------+-----+------+------+-----+-----+
| Cryst | Cpl | Slot | Msg | Typ | Lng |
+-------+-----+------+------+-----+-----+
| 0 | 8 | 2 | 7 | FLA | 1 |
+-------+-----+------+------+-----+-----+
Note:
wherevg -m (followed by message number) shows message type and location.
16.10.2 Music-On-Hold commands

Use the following tab__aux commands to find respectively "free" voice guide numbers and message
numbers when you want to manage new static voice guides for music-on-hold:
• tab__aux freeguide,
• tab__aux freemsg.
Note:
Use tab__aux/Help to have all possible options of this command:
• tona : displays only the tonality(ies),
• suvg : displays only the multi-lng flash(s) VG,
• zvg : displays only the z message(s),
• dynvg : displays only the dynamic flash(s) VG,
• multivg : displays only the multi-msg flash(s) VG,
• flashz : displays only the flash(s)-Z chained,
• freemsg : displays the free messages,
• freeguide : displays the free guides.
Example:
tab__aux freeguide
|---------------------------------------------------------|
| LIST OF FREE GUI DE(S) |
|---------------------------------------------------------|
|(*) => Could be used depending on the system management |
|---------------------------------------------------------|
|A1_R2AR (0169) *
|---------------------------------------------------------|
|A6_R2AR (0170) *
|---------------------------------------------------------|
|GPMGTZ1 (0171) to GPMGTZ10 (0180) *
|---------------------------------------------------------|
|REORDER_TONE (0211) *
|---------------------------------------------------------|
|TONA_213 (0213) *
|---------------------------------------------------------|
...
|---------------------------------------------------------|
|VG_MULT_701 (0701) to VG_MULT_849 (0849) *
|---------------------------------------------------------|
|R1_F1_L2 (0850) *
|---------------------------------------------------------|
|ANIREQ (0865) *
|---------------------------------------------------------|
|FREE_AUX_866 (0866) to FREE_AUX_910 (0910) *
|---------------------------------------------------------|
|VG_MULT_911 (0911) to VG_MULT_1023 (1023) *
|---------------------------------------------------------|
|UNKNOWN (1024) to UNKNOWN (2000)
|---------------------------------------------------------|
| TOTAL FREE GUIDE(S) = 1708 |
|---------------------------------------------------------|
Example:
tab__aux freemsg
|-------------------------------------------------------|
| LIST OF FREE MESSAGE(S) |

|-------------------------------------------------------|
|(0001) |
|-------------------------------------------------------|
|(0002) |
|-------------------------------------------------------|
|(0019) to (0057) |
|-------------------------------------------------------|
|(0059) to (0062) |
|-------------------------------------------------------|
|(0064) |
|-------------------------------------------------------|
|(0066) |
|-------------------------------------------------------|
...
|-------------------------------------------------------|
|(0918) to (1013) |
|-------------------------------------------------------|
|(1356) to (3065) |
|-------------------------------------------------------|
| TOTAL FREE MESSAGE(S) = 2221 |
|-------------------------------------------------------|
|-------------------------------------------------------|
|(3066) to (5999) reserved for ACD, Alarm or RSI |
|-------------------------------------------------------|
16.10.3 Checking the version of voice guides

To check the (installed) version of system voice guides and 4645 (e-VA) voice guides on a system, use
the readhead command.
16.10.3.1 System voice messages

1. Go to the voice guide directory:
cd /usr7/vgadpcm/flash/std
or
cd /usr7/vg/flash/std
2. Enter the readhead command, followed by the name of the file to check.
Example:
readhead vgadpcm.EN0
16 first bytes >>>

magic : 51e0c
start adress : 0
length : 165ada
crc : cbe95f2
240 next bytes >>>

Firmware : @
Format_number : 91 [
ab_binary_name : VGU_EGUI
separator : _
version_number : 04
separator : _
date : 20FEB02_11h59
end_string : 30
country_name : generic
site_name : BREST
release_env_name : R1.0
binary_name : vgadpcm.EN0
board_type_name : ADPCM e-Mediate
component_name : vgadpcm.EN0
downloaded_by : A4400tfr
PCMS_code : 3ba50162enaa
misc_flag : 41 H
Compression_type : 44 H
Compression_param : 50 H
comment : Generic English

16.10.3.2 4645 (e-VA) voice messages

1. Go to the 4645 (e-VA) voice guide directory:
cd /usr7/vgeva
2. Enter the readhead command, followed by the name of the file to check.
Example:
readhead evavg.EN0
16 first bytes >>>

magic : 1e0c
start adress : 0
length : 6f44ac
crc : 33869131
240 next bytes >>>

Firmware : @
Format_number : 91
[ ab_binary_name : EVA_GUID
separator : _
version_number : 02
separator : _
date : 08JAN03_16h35
end_string : 30
country_name : en
site_name : BREST
release_env_name : R1.0
binary_name : evavg.EN0
board_type_name : G.711 A EVA
component_name : evavg.EN0
downloaded_by : a4400tfr
PCMS_code :
misc_flag : 41 H
Compression_type : 4c H
Compression_param : 41 H
comment : English
16.10.4 Dynamic voice messages

Failure reasons
If dynamic message assignment, selection or download fails, check to see if the message is present in
System > Dynamic Voice Guides─> Failure reason.
Messages and solutions
• More than one current file: Use the option Remove invalid file from database.
• Cannot read file: Check read rights for the file loaded into the directory /DHS3ext/vg/pc by AAS.
• Invalid file content: Use the Clear import directory option or the Remove invalid files from
database option before downloading again.
• Not enough designated memory : contact Technical Support (please give details of the context in
which the error occurred).
• VG Recording by UA set in progress: wait for the set to finish recording.

Chapter
17 Date and time management
17.1 Overview
17.1.1 Overview
Date and time of OmniPCX Enterprise is provided by the internal clock. The internal clock is set by:
• The system manager: in this case, the manager sets the system date and the system time manually
with the swinst tool (see: Swinst - Detailed description)
• ISDN access: in this case, the system date and system time are received from the ISDN network at
each connection (see: ISDN T0/T2 (CCS on E1 boards) - Overview). Only interfaces belonging to
domains with the same time zone as the system can be used to update the system clock.
• Network Time Protocol (NTP): in this case, the system date and the system time are received from
an external reference clock, via IP (see: Network Time Protocol (NTP) - Overview)
The time zone parameter allows to compute local time.
Until R8.0, the system time is unique for the entire system (one Com. Server, one or several Media
Gateways and IP sets).
As of R9.0, the local time can be specific to each IP domain. For each IP domain, a specific time zone
parameter is made available in system administration.
Domain 0
Call
Server Paris
GMT +01:00
IP network
Domain 3
Domain 1 Domain 2
London Tokyo Shangai

GMT 00:00 GMT +09:00 GMT +08:00
Figure 17.1: Example of Network with Different Time Zones
In each domain, the time is set with the formula:

Domain Time = A + (C-B)
• A = Time of the system (domain 0)
• B = Time zone of the system (domain 0)
• C = Time zone of the domain

Chapter 17 Date and time management
Example:
In the example above, the system is set to the local time 15:00, the system is located in Paris GMT+01:00 . A set,
located in Shangai GMT+08:00, displays : 23:00 (15+(8-1))
The system automatically changes the clock at dates set by local authorities (Daylight Saving Time -
DST).

17.2.1 Text Messages
Received text messages are displayed with the local date and time of the receiving set.
For more information on text message see: Text message - Overview
17.2.2 Appointment and Wake Up Time

Appointment and wake up facilities can be configured from any set in the system (including sets in
different time zones). This configuration must correspond to the local time of the destination set.
Caution:
1. When the time zone of the IP domain of the set is modified, the appointment/wake up time is not
updated.
For example: A user plans a wake up call at 08:00 when the time zone of the domain is GMT + 01. The
manager changes the time zone to GMT + 02. The wake up time is not updated and the user set rings at
09:00 (new local time).
2. During DST transitions, an offset of one hour (plus or minus) could affect the appointment/wake up
time, depending on the offset between user time and system time.
For more information on appointments and wake up see: Appointment reminder - Overview
17.2.3 DECT or PWT Sets

When a Dect (or PWT) set is on roaming between time zones, it is updated with the local date and time
each time it enters a different IP domain.
17.2.4 Unanswered Calls

Unanswered calls are stored with the local date and time of the receiving set.
For more information on unanswered calls see: Unanswered calls - Overview
17.2.5 Accounting Tickets

External call accounting tickets contain a field with the time zone of the used trunk.
17.2.6 Incidents
Incidents are always stored with the system date and time.
17.2.7 Passive Communication Server

Passive Communication Servers must be configured with the system date, time and time zone
whatever the domain they belong to.
Note:
When the system date and time are modified, the date and time of each PCS must be modified.

17.2.8 Time Update by ISDN

Only interfaces belonging to domains with the same time zone as the system can be used to update
the system clock. The Update hour on ABC systematically parameter of these interfaces can be set
to Yes. For other interfaces, the parameter must be set to No.
17.2.9 Restrictions
• Entity: the entity calendar must be configured with the system time zone. Caution: the DST is not
taken into account for entities
• ARS: the ARS calendar must be configured with the system time zone. Caution: the DST is not
taken into account for ARS
• Voice mail: Voice mail servers record messages with the system date and time
• INTOF ACT: non IP sets of ACTs connected to the call server via an INTOF or RT2 link use the
system date and time whatever the time zone they belong to
Domain 1
RT2 IP Link
Link
Public
Time zone 1
IP network
Network
Time zone 0
Domain 0
Call Server
INTOF
Link
Figure 17.2: Example of Not Recommended Configuration

• CSTA: for this service only the system date and time are used
• OTCC (Statistic): for this service only the system date and time are used
• SIP Set: Date and time are managed directly on the set or the set gets date and time form an
external server

17.3.1 System Date and Time
The system date and time are configured via the swinst tool.
Path: Expert menu > System management > Date & time update > Set date & time

Enter the local date and time of the system. The new date and time are immediately updated on all
sets of all IP domains.
For more information on the swinst tool see: Swinst - Detailed description.
17.3.2 System Time Zone

The system time zone is configured via the swinst tool.
Path: Expert menu > System management > Date & time update > Set timezone
Figure 17.3: Time Zone Setting Page
1. Use the Tab key to navigate to time zone selection

2. Select the system time zone using the up and down arrows
3. Navigate to OK using the Tab key and press Enter to validate
4. Exit the swinst tool
5. Restart the system, with the command: shutdown -r now
Notes:
The selection of a time zone defines both the time offset and the DST rules.
Notes:
The default value is automatically set according to the country configuration defined during installation.
17.3.3 IP Domain Time Zone

The time zone of an IP domain (different than domain 0) is configured via mgr or OmniVista 4760.
1. Select: IP > IP Domain
IP Domain Number Enter the number of the IP domain
Time Zone Name Select the time zone of the IP domain

Note:
The available values are the same as for swinst (but with a
different order).
The default value is set to the system time zone name.

Note:
When a time zone of an IP domain is modified, all sets of this domain are updated immediately.

Chapter
18 Multi-country configuration
18.1 Overview
Until R8.0, the OmniPCX Enterprise only supports configurations where all the sites of a node are in
the same country.
A country parameter is defined for the entire system and applies to all the sets of the installation.
As of R9.0, the Multi-Country feature allows an OmniPCX Enterprise to support configurations where
the sites of a node are in different countries.
For each IP domain, a specific country parameter is made available in system administration. This
country parameter applies to Common Hardware boards and devices linked to these boards.
Call
Server Domain 0
Country 0
IP network
Domain 1 Domain 3
Country 1 Country 3
Domain 2
Country 2
Figure 18.1: Example of Network with Different Country Zones
The country parameter is used for:

• Tones
• Common hardware boards initialization and other pieces of equipment initialization (IP devices and
devices linked to a common hardware board)

18.2.1 Device Behavior
18.2.1.1 Multi-Country Feature Disabled
When the multi-country feature is disabled, the country is configured at system level. A country can
also be configured at board level.

Chapter 18 Multi-country configuration
Device behavior with the Multi-Country feature disabled is described in Figure 1.
Board Parameters
Equipment linked to a
board Country:
(sets, trunks, boards)
- Default
System Parameters
- Selected country
Country
DECT, GAP, IP
phones, SEPLOS,
remote extensions and
nomadic sets
Figure 18.2: Device Behavior with Multi-Country Disabled
Note:
For devices not mentioned in the above figure, the system country is used.
18.2.1.2 Multi-Country Feature Enabled

When the multi-country feature is enabled, in addition to the system country, a country can be specified
for each IP domain. A country can also be configured at board level.
Device behavior with the Multi-Country feature enabled is described in Figure 2.

UAI Board
Parameters
Equipment linked to an
IBS base station linked Country:
to a UAI board IP phones,
- Default SEPLOS, Voice
Mail 4645
- Selected country
GD Board
Common Hardware Parameters
Board Parameters IP Domain
Country:
Equipment linked to a Parameters
Country:
Common Hardware
- Default Country:
board
(sets, trunks, boards) - Default
- Selected country - Default
- Selected country
Remote extension - Selected country
linked to a trunk linked
to a Common
Hardware board SIP devices
- In an IP domain
- Otherwise System Parameters
Country
Nomadic sets
Figure 18.3: Device Behavior with the Multi-Country Feature Enabled
Note:
For devices not mentioned in the above figure, the system country is used.
Note:
For Voice Mail 4645, the used country is the country of IP domain 0.
18.2.2 Tone Setup

With the Multi-Country feature, users hear the tones they are used to, corresponding to their own
country.
A tone is defined by:
• Tone generation definition (frequency, level, sequence)
• Tone parameters (sequence durations and silent durations)
18.2.2.1 Tone Generation Definition

The tone generation definition of the corresponding country is sent by the Com Server to the Media
Gateway at Media Gateway initialization. For IP Phones, the Communication Server sends the tone
generation definition of the corresponding country to the set.
18.2.2.2 Tone Parameters

When a tone is sent to a device, the PCX checks the country declaration of this piece of equipment and
sends the corresponding tone parameters in a specific tone message:

• For digital sets, analog sets, trunks and compressors, the tone message is sent to the Media
Gateway of this piece of equipment.
• For IP Phones (Alcatel-Lucent 8 series and e-Reflexes), the tone message is sent to the set.
• For Seplos, SIP and H.323 devices, the tone depends on the country of the compressor used by the
IP device.
18.2.3 Numbering Plan

Until R10.0, the numbering plan is the same for all items of the OmniPCX Enterprise.
As of R10.1, the callback translator includes country specificities. For more information, see: [5].
18.2.4 Restrictions
In a multi-country configuration:
• All countries must share the same compression law (e.g. the USA and Hong-Kong are compatible
because they share the same law, i.e. law µ).
• The hardware of the main country of the system (i.e. the country of the Communication Server) may
be either Crystal and/or Common Hardware.
• The system hardware in all the other countries must be: Common Hardware.
• The same DECT frequency must be used in all countries of the system.
• When QSIG is required, the same protocol (ECMA or ISO) must be used in all countries.
• When the IP Touch Security service is required, all the countries of the system must legally allow
the use of this service.
• The hold key on multiline set for USA feature is available only if the system country is USA (this
feature allows to put on hold any conversation on a multiline set by pressing the hold key instead of
pressing the multiline key corresponding to the conversation to put on hold).
• Only tones corresponding to the system country can be configured. For other country, default values
are used.
Note:
To display the default value for tones specific to a country, use the visu_tona command.

18.3.1 System Country
To configure the country of the system:
1. Select System.
Country Select a country

4. Restart the system, with the command: shutdown -r now.
18.3.2 Multi-Country
To enable the Multi-Country feature:
1. Select System > Other System Param. > System Parameters.

System Option Select Multi country
Multi country • True: Multi-Country enabled

• False (default value): Multi-Country disabled
4. Restart the system, with the command: shutdown -r now.
18.3.3 Enhanced Multi-country

As of R12.0, in case of external call forwarding, the display of the destination set shows the country of
origin of the call.
1. Select System> Other System Param. > External Signalling Parameters
System Option Enhanced-Multi-Country
Enhanced-Multi-Country Select the appropriate value:

• True: the country code of the calling party is compared
to the country code of the call forwarding destination.
When these country codes are identical, the number
sent to the destination set is national. When they are
different, the number sent to the destination set is
international.
The country code added to the calling number is the
country code defined in the external call back
translation table including the G rule, and associated
to the entity of the calling party. For more information,
refer to the External callback translator section of
the document [5].
If it is not configured, the country code is taken from
the Country Code system option (access path:
System > Other System Param. > Signalling String)
• False: country codes are not taken into account to
build the calling number used to reach the destination
number. Operation is identical to that of previous
releases.
18.3.4 IP Domain Country

To configure the country of an IP domain:
1. Select IP > IP Domain.
IP Domain Number Enter the number of the IP domain.
Country Select a country or Default (in this case, the system

country applies).

4. Reset the controller board manually.
18.3.5 Board Country

To configure the country of a board:
1. Select Shelf > Board.
Board Address Enter the address of the board
Country Select a country or Default

4. Reset manually the board.

Chapter
19 Timer management
19.1 Overview
19.1.1 General
The timers used in the OmniPCX Enterprise have two functions:
• either to delay an operation,
• or to monitor the arrival of an event and to control the resulting actions.
The length of the timers is set in the factory but may be modified by the administrator.
Note:
any unchecked modifications of the timers may cause the system to malfunction seriously. The timers must only be
modified with the help of an expert.
Example of an event delay timer: Set Ringing
Active
process
Time
Timer duration
Ringing start command Ringing stop command

Figure 19.1: Event delay timer example
The process, which allows the ringing to be stopped, is delayed for the length of the timer.
Event monitoring example
There are two possibilities in this case:
• the timer expires before the expected event occurs,
Message send Non response

processing processing
Time
Timer duration
Timer setting Timer expiry

Figure 19.2: Message exchange monitoring (1st case)

Chapter 19 Timer management
When the timer expires, the system processes the non response of the expected event.
• the event occurs at the end of the timer.
Response
Message send
Response
processing
processing
Time
Timer duration
Timer setting Timer stopping
Figure 19.3: Message exchange monitoring (2nd case)
The system stops the timer and processes the response.
19.1.2 Reference to related modules

The timers are documented in the following modules:
• Functional description (see List of timers on page 346 ),
• Management (see Timer management on page 367 ).
19.2 List of timers

Remark:
The default values given below correspond to a PBX configured for "France". They are expressed in units of
100 ms.
On the PBX, the "DefaultInit command, available under the mtcl account, gives the default value
for each timer. This command requires the manager to first select the required country, then select the
option 3 Timers.
Timer
TIMERS
No.
1 second timer
Timer 1
cannot be modified
Off-hook routing timer
Timer 2 For sets with routing on off hooking (enabled in management), routing is per-
formed when the timer elapses, if the user has not dialed a number in the mean-
time.

Timer
TIMERS
No.
Local inter-digit timer

Timer 3 If this timer expires between the dialing of two digits the busy tone is sent to the
set (local only).
Ringing before overflow on no answer timer.

Timer 4
In the case of overflow with delayed forward on no answer enabled.
Check for ringing timer for callback on busy set or trunk group.
Timer 5
The user is rung while this timer is active
Timer for paging dialing presumed completed.
Timer 6 When a call party is directed to paging, this timer is triggered after each digit. If,
when the timer elapses, no digit has been transmitted, the system considers dial-
ing to be complete.
Timer for callback on hold.

Timer 7
Maximum hold time of a transferred trunk before return to attendant.
Park and paging wait.

Timer 8
Maximum parking and paging wait time.
Ring tone timer: if the person called does not answer before this timer elapses,
Timer 9 the caller gets the busy tone.
Timer for ringing before overflow on internal call (as of R4.2).
Timer for ringing in the intercom position.

Timer 10 Only used for internal calls (the set continues to ring for an external incoming
call).
Timer for trunks that have waited for more than "n" seconds.
Timer for time before call or wait status is changed to urgent.
Tex = external overflow timer (welcome/greeting management).
Timer 11
T0 = welcome/greeting call received.
Tn = call status changes to "urgent".
Td = call overflow to external, to the welcome team.
Timer for change to line lockout.

Timer 12
When the timer elapses the set switches to line lockout.
Timer 13 Wait timer for external tone detection.

Timer
TIMERS
No.
Wait timer for an action performed.

Timer 14
Do not modify.
Intercom ringing cadence timer.

Timer 15
Ringer cadence in the intercom position (digital sets).
Timer for release of combined networks.

Timer 16
Time after which the trunk is again available.
Timer 17 Timer for confirmation of PSTN tone (external or presumption).
Timer for dialing to the outside to be presumed complete (with DTMF).
Timer 18 When this timer elapses, the routing tone is transmitted - on the TRUNK SIDE:
this timer can be shortened by the equivalent keypad end. With open dialing, the
bi-directional connection is not established until this timer elapses.
Timer for busy tone in the intercom position.

Timer 19 Time during which the busy tone is transmitted before automatic on-hooking (in-
tercom position).
Timer for call to a set after a forwarding operation.

• A forwarding operation is performed on the set, the user then waits for this
Timer 20 timer to elapse without hanging up and is routed to the forwarding destination
set.
• Timer for set callback if a message is left.
Wait timer for external intermediate tone detection.

Timer 21
Same principle as for timer 13, but for intermediate tone.
Non modifiable timer.

Timer 22 Timer 22 is constantly modified by the system and cannot be modified by the
user.
Translation timer.
Timer 23
Used for set numbers in 4T form.
Timer for idle between calls with automatic attendant answer.

Timer 24
Time before the next call is presented (automatic answer).
Alarm set ringing timer.

Timer 25
Maximum time that alarm sets ring.

Timer
TIMERS
No.
MF digit transmission timer.

Timer 26
Do not modify.
6 second timer.
Timer 27
Do not modify.
Timer for ringing on call to attendant.

Timer 28 When calling an attendant, the attendant station is rung during this timer if so
configured.
Timer before "beep" / incoming on set (Satellite).

Timer 29 Satellite feature only: when an incoming call reaches a set, a beep (indicating that
a call is waiting) is only transmitted to the set once this timer has elapsed
Wait for off-hooking timer on satellite center.

Timer 30 Time that a subscriber can remain in off-hook wait on a satellite center trunk
group.
Timer for idle (rest) between two calls to a set in a PBX group.
Timer 31 This timer is triggered after on-hooking. The set will not receive a call to the PBX
group (but may receive a personal call) until this timer has elapsed.
Timer for attendant unplugging with a call on hold (camping).

Timer 32
During this timer, the attendant is informed of camping calls on the station.
Timer for authorization of attendant withdrawal.

Timer 33
Attendant withdrawal is authorized once this timer has elapsed
Timer for DATA routing to attendant set.

Function key on attendant set:
Timer 34
If the operator dials before the timer has elapsed, routing to server (Nº dialed),
otherwise routing to the server configured in management.
Inter-digit timer in pulses (dialing).

Timer 35
Do not modify.
Timer before overflow to another set in a PBX group.

Timer 36
In the event of no answer from a free station in a station group.
Timer for paging guide proposal.

Timer 37
Timer before the suffix triggering paging is offered.

Timer
TIMERS
No.
Timer for self-release of a DTMF receiver and out of service trunk cyclic tests.
Timer 38 Watchdog timer for DTMF receiver release.
Time between two tests of an out of service trunk.
Timer for release of a trunk in callback on night forwarding.

Timer 39
If there is no answer, the trunk is released when the timer elapses.
Timer 40 Timer for continuous transmission of a DTMF code (used for DTMF code testing)
Timer for detection of ring or busy tone for TRANSCOM
Timer 41 Time during which the system attempts to detect the ring or busy tone, if either of
these tones is detected the system infers that the link set up is not a TRANSCOM
link, and breaks it.
Timer for authorization of a consultation call following direct seize.

Used when a trunk is seized for an outgoing call, this timer starts to run when
Timer 42 conversation begins
(polarity inversion, charge unit reception or when timer 41 elapses) and must
have completely elapsed before a consultation call can be made.
Time for switch to idle while in service.

Timer 43
When the attendant presses the service key but performs no further action.
Timer for routing to data associate.

Timer 44
After this timer elapses, the set is routed to its data associate.
Max. timer for exchange of the controlled sequence (DID)

Timer 45
(FRANCE only)
Inter-digit timer (DID)

Timer 46
(FRANCE only)
Timer before sending FC on forward signal reception (DID)

Timer 47
(FRANCE only)
Timer for switch to B code (DID)

Timer 48
(FRANCE only)
Timer to maintain back signal after detection of FC (DID)

Timer 49
(FRANCE only)

Timer
TIMERS
No.
Timer before transmission of ring or busy tone (DID)

Timer 50
(FRANCE only)
Timer before transmission of UNHOOK of the called party (DID).

Timer 51
See special features of ITALY type DID and R2.
Timer for camping of a call with level 1 precedence.

If there is a call in progress on a set (call with no precedence) and another call
(with precedence) arrives, a "beep" is emitted:
Timer 52
• rank 1 beep during timer 52,
• rank 2 beep during timer 55,
Rank 1 beep = short beep. Rank 2 beep = long beep
Wait timer for release at the other end.

Timer 53
See special features of ITALY type DID.
New answer timer.

Timer 54 The user hangs up while making an external call, if he unhooks during this timer,
he is again connected to the network. Can be reduced to 1 sec.
Timer for hold (camping) of a call with level 2 precedence.

If a set receives a call with precedence and another call with precedence arrives,
Timer 55 a "beep" is emitted (rank 1 (short) beep) during timer 52 + 55, then the call over-
flows.
Rank 1 beep = short beep
Timer for US board state stabilization camping.

Timer 56
Do not modify.
Timer for waiting for US board reply.

Timer 57
Do not modify.
Duration of Forward sequence (DID)

Timer 58
(FRANCE only)
Timer for acknowledgement of DATA set-up modification.

Timer 59 When a set-up is changed from the set, this timer is used to validate the new val-
ues.
Timer for temporary tie-line unavailability.

Timer 60
See special tie-line features.

Timer
TIMERS
No.
Timer for listening silence (DID)

Timer 61
(FRANCE only)
Timer for simultaneous tie-line seize.

Timer 62
See special tie-line features.
Timer for maintaining A2 after receiving FC (DID)

Timer 63
(FRANCE only)
Timer before sending seize of COLISÉE IA (tie-line).

Timer 64
See special COLISÉE tie-line features. (FRANCE only)
Timer before transmission of dial tone (DID)

Timer 65
(FRANCE only)
Timer before beginning to detect FC (DID)

Timer 66
(FRANCE only)
Timer assumption of -48V (DID)

Timer 67
(FRANCE only)
Timer for waiting for a delayed call in the case of an incoming call on an NDDI
Timer 68 trunk (delay in going off-hook on non polarized lines in order not to hear ringing)
See specific country features.
Timer for inter-standard line release.

Timer 69
See special inter-standard features.
Variable timer.
Timer 70
Cannot be modified.
Appointment reminder ringing timer.

Timer 71
Maximum time appointment reminder rings.
Timer 72 Not used.
Timer 73 Timer for digital set ringing cadence.
Timer 74 PSTN PCM No 1 timer to generate 10 to 60 sec message
Timer 75 PSTN PCM No 2 timer to generate 10 to 60 sec message

Timer
TIMERS
No.
Timer before switching to attendant absent

Timer started as soon as the attendant receives a call, if, when the timer elapses,
Timer 76 the attendant has not answered,
the station switches to “ATTENDANT ABSENT" (the call goes to the night for-
warding set).
Timer for wait to enter a programmed conference.

Timer 77
Timer before being put into programmed conference (conference reminder).
Timer for single trunks in programmed conference.

Timer 78
Maximal duration for which a trunk can stay alone in a programmed conference.
Call announcement response timer (Loudspeaker call).

Timer 79
Time during which the caller requesting a call announcement is in conversation.
Timer for release of PCM trunk with call in progress when there is an alarm.
If the PCM alarm occurs at the time of an "incoming" call, and the corespondent
Timer 80 has not unhooked, this timer is triggered (signaling cannot be exchanged during
the alarm). If, at the end of the timer, the alarm has disappeared, the exchange
continues normally, otherwise the trunk is released.
Timer 81 Observation wait timer 108 (V24)
Timer 82 Observation wait timer 105 (V24)
Timer for ring tone before connection of welcome or camp-on message.

Timer 83
Time before connecting the welcome guide or the waiting guide.
Timer 84 Timer for overflow of incoming calls with precedence to attendants.
This timer has two roles:

• Timer for keeping the DISA call rerouted:
Maximum timer for conversation between a DISA incoming trunk and an
outgoing external trunk.
Timer 85 After this timer has elapsed, a beep is transmitted to the external user who
must perform an action (press a key) to continue the conversation, otherwise,
the trunks are released.
• Timer used to indicate that the call is on an ISDN line:
After this timer has elapsed, a beep is transmitted to the user to indicate that
he is using ISDN (expensive call).
Timer for answering incoming DISA.

Timer 86
Time before connection of trunk for an incoming DISA call.

Timer
TIMERS
No.
Timer 87 Timer for presumption of on hooking on Inter-standard line.
Over-ringing timer (indicating a call camped on multi-line).

Timer 88
Duration of beep.
Timer for confirmation of not going on-hook (for analog sets).

Timer 89
To avoid the problems of ill-timed flashing.
End to end signaling timer.
Timer 90 When switching to end to end signaling, users have the duration of this timer to
transmit their first digit, otherwise this state is exited. This timer delay is rearmed
at transmission of each digit.
Timer for acknowledgment of call entering X21.

Timer 91
Timer T14A complies with the X21 recommendations of the CCITT.
Timer for X21 inter-digit.

Timer 92
Timer T13 complies with the X21 recommendations of the CCITT.
Timer for X21 dialing cover.

Timer 93
X21 timer.
Timer 94
Timer for displaying total cost T2.

Duration of display, after an external outgoing call and according to set manage-
ment, i.e. of:
Timer 95 • either the number of charge units of the last call, plus the total number of units
since the last RESET of counters,
• or the cost of the last call, plus the total cost since the last RESET of counters.
The set is considered as busy during this timer.
Timer for Voice service cyclic supervision.
Timer 96 Timer between two tests for the presence of voice mail. If there is a break in voice
mail (converter cut off, V24 cable unplugged, etc.), current voice mail calls are re-
leased after a delay of 40 seconds.

Timer
TIMERS
No.
Timer for ringing on VESTAL call request.

Timer for the TELEMARKETING application. The server may request the teleac-
Timer 97 tor to call a number. The server transmits the call to the PBX via the V24 channel
and the PABX rings the teleactor's set. If the teleactor does not answer before
this timer elapses, the call is cancelled; if he answers, the call is made automati-
cally.
Timer for TS 16 Level 2 Coupler T2 connection.

Timer 98 Timer for LAPD coupler response.
If the coupler does not respond before this timer elapses, an error is returned.
Timer for simultaneous center / satellite seize.

Timer 99
Specific to center / satellite! Do not modify.
Timer for pre-payment tone connection (hotel).

Timer 100
Time during which the prepayment tone (108) is sent to the set.
Timer in case of non-detection of digit at beginning of message.

Timer 101 Timer in case of non-detection of digit D on the film. The film is tested a second
time with another DTMF receiver before it is declared out of service.
Timer of ringing tone on attendant set before guide connection.

Timer 102 When a trunk arrives at the attendant, the user hears the ringing tone during this
timer, then the voice wait guide after this timer if the attendant has not answered.
Timer for confirmation of external intermediary tone.

Timer 103
Same principle as for timer 17, but for intermediary tone.
Timer for reception of ring tone while waiting for unhook.

Used in the TELEMARKETING application.
Timer 104
For an outgoing call, when there is no reply from the called party, the call is re-
moved when the timer elapses.
Timer 105 Timer of PCM forced release.
Timer 106 Timer for connection of tone in DID transit.
Timer for listening to voice guide 17.

Timer 107 When trunks are joined, this limits the listening time of the guide informing the
caller that the called party is temporarily unavailable.

Timer
TIMERS
No.
Timer for listening to a tone.

Timer 108 During tone testing, this timer makes it possible to remain listening to one tone
before moving to the next one.
Timer 109 Timer for trunk release by attendant. (ITALY).
Timer 110 Timer for wait before authorization code on MCL
Timer 111 Timer for S0 bus release.
Timer 112 Timer for establishment of T0 levels 1 and 2.
Timer 113 Level 2 deactivation timer.
Timer for initializing Driver IO1 (CPU)

Timer 114
Special feature of the system, do not modify
Timer for IO1 identification

Timer 115
Download timer
Timer 116
Timer for determining role

Timer 117
Clock synchronization activation response

Timer 118
Synchronizing coupler stop response

Timer 119
Synchronization of secondary ACT shelf

Timer 120
Synchronization stop in secondary ACT shelf

Timer 121
Coupler response after CPU switchover

Timer 122
Max. duration of coupler reset

Timer 123

Timer
TIMERS
No.
Coupler cyclical test interval

Timer 124
Coupler response to cyclical tests

Timer 125
Auxiliary cyclical test interval

Timer 126
Timer before notification of availability for call setup is sent

Timer 127
DPNSS special feature for Great-Britain
Timer for retry due to trunk congestion

Timer 128
DPNSS special feature for Great-Britain
Timer used in guide mode

Timer 129
Wait timer for call by name or Directory answer

Timer 130
Timer 131 Wait timer before sending DTMF to VPS
Timer for initialization of UA sets located in the main shelf

(Timer between board and the first UA set initialization, then between each UA
Timer 133
set)
Timer for initialization of UA sets located in the secondary shelves

(Timer between board and the first UA set initialization, then between each UA
Timer 134
set)
Timer 135 ARS warning tone timer (in seconds)
Timer 136 ARS wait point timer (in seconds)
Timer 137 Wait timer used to display the total cost at the end of a T2 call
Timer 138 CSTA - set ringing timer
Timer 139 CSTA - timer for beep before unhooking

Timer
TIMERS
No.
Timer used if the attendant set ringing mode is Delayed ringing (refer to the sec-
Timer 140 tion Attendants of the document [4]: Ringing attribute).
This timer defines the delay between call presentation and ringing.
Timer before return to attendant after transfer of an external call to a set that does
Timer 141
not answer
If the attendant set ringing is Delayed ringing, this timer defines the ringing dura-
tion before the call switches to urgent degree.
Timer 142
If the attendant set ringing is not delayed, the sum of timers 140 and 142 defines
the ringing duration before the call switches to urgent degree.
Timer 143 Absent beep timer
Timer 144 Timer for distributed call
Timer 145 DECT - Link release timer
DECT - Wait timer for the "LCE REQUEST PAGING" message (search for set lo-
Timer 146
cation)
Timer 147 DECT - Wait timer for the first "LCE PAGE RESPONSE " message
DECT - Timer for handover synchronization (switching to another, more powerful,

Timer 148
channel)
Timer 149 Destination Idle Guard Time for Network Automatic CallBack
Originating PBX Service Duration timer

Timer 150 This timer is also used to limit service for a Call Completion on Busy Set (CCBS)
on an ABC network.
Wait timer for starting of the CZ wake-up IO process (real-time UNIX printout
Timer 151 process used to print wake-up requests, infocenter, hotel check-in check-out,
etc.)
Timer 152 Initialization timer for UA and Z sets
Timer 153 DECT NETWORK TMR - DECT timer used to release blocked links
Timer 154 DECT TMP_07 - DECT network timer
Timer 155 DECT TMP_08 - DECT network timer
Timer 156 DECT - Timer for base station restart initialization tracking
Timer 157 DECT - Inactivity timer for DECT set installation

Timer
TIMERS
No.
MLPP - Timer between arrival of a message with precedence and effective pre-
Timer 158
emption (of the called party)
MLPP - Time for security of the preempting party (party requesting preemption).
This timer avoids the preempting party being blocked in certain "no answer" situa-
Timer 159
tions. Forced release of a set after preemption, if a call with precedence cannot
be presented (for example, analog set that has not hung up after preemption)
MLPP - Duration of the tone providing the incoming preemption "beep" (CAU-
Timer 160
TION not 1/100 sec)
MLPP - duration of conversation times between preemption beeps (CAUTION:

Timer 161
not 1/100 sec)
Reserved for A234 - Timer for the management of line switch-over (main ->
Timer 162 standby) of a CNA set.
Not to be modified in any circumstances
Reserved for A234 - time the system waits for user action after an AID guide with
Timer 163
multiple choice
Reserved for A234 - time the system waits for the answer of a Sinar to an AID
Timer 164
request
For the attendant, timer for the display of the name of an inaccessible caller or in
Timer 165
line lockout.
Timer 166 Reserved for future use
Timer for validation of IO1 clock data

Timer 170
Timer for validation of IO1 synchronization change

Timer 171
Timer for cyclical search for DTMF receiver - When an analog set is picked up, a
DTMF receiver is searched for; if this search fails, the system performs succes-
Timer 172 sive search attempts (every 2 seconds); - when this timer elapses, the search is
interrupted and the busy tone is heard on the set.
(Example: cyclical search every 2 seconds during the timer = 10 sec)

Timer
TIMERS
No.
Wait timer for the CSP (DECT board Cell Site Processor) parameter for base initi-
Timer 173
alization
Timer 174 Timer for repeated paging
Timer 175 Delay between retries for DPNSS routing optimization
Timer 176 Duration of display of error messages on the attendant set
Timer for remote supervisor update - Used in network to regulate supervision traf-
Timer 177
fic when a link between two nodes restarts.
V1 ACD timer before overflow on directory number (in order to enable the display
of dissuasion on the wall-mounted display and permanent edition of the dissua-
Timer 178 sion supervisor).
Do not modify
Timer for consultation call during which the user can choose between transferring
Timer 179
from hold to voice mail or going to voice mail whilst remaining on hold.
Timer 180 AC15 - Unannounced transfer
Timer 181 Timer for locate-accept MMI (user interface) transaction
Timer 182 Timer for Cipher-Request MMI (user interface) transaction
Timer 183 Timer for sending of overlap used for external ring tone after transfer.
Timer 184 CC release timer
Timer 185 CC setup timer
Timer 186 CC automatic callback timer
Timer 187 CC connection timer
Timer 188 Timer for release of set reserved by attendant
Timer 189 CCD (Call Center Distribution) trunk group supervision timer
Timer 190 Transparency anticipation, timer for sending 1st digit
Timer 191 Congestion timer
Timer 192 Timer for memory cleaning
Timer 193 Registration beep duration
Timer 194 DEC flash timer

Timer
TIMERS
No.
Timer 195 CNA overflow timer
Timer 196 Over-ringing timer for 3G multiline set
Timer 197 Timer for forced release in the event of bilateral release
Timer 198 Wake-up/Appointment Timer
Timer 199 VPN sync. timer
Timer 200 Reserved for blocked Z trap
Timer 201 Reserved for blocked Z trap, used to trigger backtrace
Timer 202 Reserved for blocked Z trap, new wait with the trap
Waiting suffix timer, allows the complete guide to be listened to, before dialing the
Timer 203
suffix selected with an analog UA Z set
Timer for repetitive beep on the loudspeaker instead of over-ringing on the hand-
Timer 204
set
Timer 205 Wait timer for 1st digit dialed by incoming DISA caller
Timer 206 Timer for MMI (user interface) identity request transaction: MM_ident.2
Timer 207 Timer for MMI (user interface) authentication request transaction: MM_auth.1
Timer 208 Timer for MMI (user interface) key allocate transaction : MM_key.1
Timer 209 ATM VB: Wait for answer to SNMP request
Timer 210 ATM VB: Wait for answer to BBC request
Timer 211 Wait for release to complete
Timer 212 Wait for complete end of connection after SSCOP disconnection
Timer 213 Wait for connection acknowledge (user)
Timer 214 Wait for Q93B restart acknowledgement
Timer 215 Wait for connection clearing end after a Q93B restart (received)
Timer 216 Wait for setup response
Timer 217 Wait for connection or release in incoming call processing state
Timer 218 Wait for drop party response

Timer
TIMERS
No.
Timer 219 Wait for add party response
Timer 220 Wait for Bbc response
Timer 221 Wait for status message
Timer 222 SSCOP release oversight (ATM frame field)
Timer 223 Marking for ack msg timer
Timer 224 Marking for ack msg timer
Timer 225 Time sharing during search procedure
Timer 226 to Tim- Reserved

er 232
Wait timer associated with the GPMMC_SUFF guide for dialing a suffix for trans-
Timer 233
fer to meet-me conference
Wait timer associated with the GPMMC_ATT_TR guide for placing in automatic
Timer 234
conference after transfer from hold to meet-me conference
Timer 235 Timer held to check malicious call
Timer 236 Max duration of the conversation during a trunk group-trunk group connection
Timer 237 Specific timer to delay the current digit
Timer 238 Specific timer to play back the guide (CCD)
Timer 239 Specific timer to play back the busy tone (CCD)
Timer 240 Timer for application not answering after a connection REQUEST
Timer 241 Timer for virtual CCD not answering
Timer 242 Wait timer before validation of the Unanswered Call service
Timer 243 Wait timer between two HYBRIDEV supervisions
Timer 244 Timer for break-in (intrude) suffix dialing
Timer 245 Response delay timer
Timer 246 MMI (user interface) access right transaction timer
Timer 247 Wait timer for secureIDproxy server response

Timer
TIMERS
No.
Wait timer for PRN (Pseudo-Random Number given by the TokenCard) change
Timer 248
on TokenCard
Timer 249 Wait timer for wake up of AINT unit options (A234)
Timer 250 Attendant release wait timer
Timer 251 Wait timer before 4635 transfer on direct call
Timer 252 Timer between repetitive beeps for emulpaging for non urgent alarm
Timer 253 Timer stopping repetitive beeps for emulpaging for non urgent alarm
Timer 254 Timer between repetitive beeps for emulpaging for urgent alarm
Timer 255 Timer stopping repetitive beeps for emulpaging for urgent alarm
Timer 256 DISA break-in (intrusion) presumption phase duration timer
Timer 257 DISA temporary blocking phase min duration timer
Timer 258 DISA temporary blocking phase max duration timer
Timer 259 Rover trunk release timer
Before R11.2, at the end of this timer, outgoing external calls, using TDM or IP
protocols, are released.
As of R11.2, according to configuration, this timer determines the maximum dura-
Timer 260
tion of (private and public network) outgoing and incoming calls.
For more information on this timer, refer to the section Call duration control of
the document [3]..
Timer 261 Agent reservation on CCD call
Timer 262 Unauthorized discrimination guide timer
Timer 263 LIS (manual tie–line) surveillance period timer
Timer 264 Timer to delay the detection of DTMF frequencies
Timer 265 Allocation of universal DSP in conversation max duration timer
Timer 266 Display duration for specific LVMH client supervision
Timer 267 Max wait during activation of the DTO_Universal
Timer 268 Max wait during activation of the DTO_VAD

Timer
TIMERS
No.
Timer 269 DECT paging clock (8 multi-frames, 1280 ms)
Timer 270 Call renewal for IS authorization timer
IP telephone recording started after TFTP request. The application waits for an
Timer 271 EVT_CPL_CPU_TSCIP_INIT initialization event to start the identification of the
set or the idle state.
IP telephone recording. User identification failed. Wait and display of the cause
Timer 272
before any new attempt.
Timer 273 Participant ringing in broadcast context timer
Timer 274 Conference waiting hold timer
Timer 275 Operations in conference programming context timer
Announcement message on loudspeaker timer. Charging ticket (call detail record)

Timer 276
forwarded to subscriber node
Timer 277 Timer before new attempt (retry)
Timer 278 Release timer
Timer 279
Timer 280
Radio intercom feature: time between two successive attempts at reconnection

Timer 289
by the intercom server to the EMTL or CMP board
Radio intercom feature: time the activity icon is displayed after activity on a chan-
Timer 290
nel has ended
Radio intercom feature:

• in multi-channel mode, time without speaking (without pressing the PTT
Timer 291 button) resulting in automatic release of traffic mode and switchover to
monitoring mode
• time a menu continues to be displayed after selecting a channel. If the user
performs no action within this time, the main menu is displayed again
Multi-translator (barring): Wait timer for end of discriminated number containing

Timer 292 the W character. If no other digit is dialed before this timer elapses, the number
alone is transmitted.
MLA feature: An external call party on supervised hold will cause the set to ring
Timer 296
when this timer elapses.

Timer
TIMERS
No.
MLA feature: Time between primary set ringing and secondary sets ringing when
Timer 297
the "delayed" option has been selected
MLA feature: An internal call party (or ABC network) on supervised hold will
Timer 298
cause the set to ring when this timer elapses
Used when a call including a DTMF message transits on an INTIP board.

Timer 299
Default value: 40ms.
This timer limits "Search by name" time in remote directories of LDAP type.
Timer 301
Default value: 38s
Time before a "Signaling link backup" to a stand-alone Media Gateway is set up.
Value 0: no backup link is set up.
Value 1: a backup link is set up immediately.
Timer 302 Other values: delay before link set up.
Default value: 20s.
Note:
a timer with a value of less than 90 sec before the backup link is set up may result in
connection failures (the Media Gateway is lost because it has not finished initializing).
Maximum reset time for a stand-alone Media Gateway. If, when this timer elap-
ses, neither the backup up nor the nominal link has been established, the Media
Gateway is reset.
Timer 305
Default value: 20mn.
Note:
for Alcatel-Lucent support only.
Timer for ringing before no answer for an e-RMA call. This call concerns incident
Timer 308 reporting or callback from the remote manager.
Default value: 20s.
Timer before callback by the remote manager. This timer gives the remote mo-
Timer 309 dem sufficient time to on hook.
Default value: 20s.
Timer after ringing (CLIP on Z32)

Timer 319
Default value: 7s
Timer after message (CLIP on Z32)

Timer 320
Default value: 2.5s

Timer
TIMERS
No.
Callback on busy trunk group: timer between release of a trunk and callback on
Timer 328
busy trunk group
Alcatel-Lucent 8/9 series sets: timer for the display of audio and internal applica-
Timer 325
tion confirmation popup.
Callback on busy trunk group: maximum duration of a recording. After this timer,
Timer 329
the recording is lost. Default value: 45mn
Alcatel-Lucent 8/9 series sets: timer for the display of the popup window indicat-
Timer 331
ing an incoming call
Timer 332 Alcatel-Lucent 8/9 series sets: timer for the display of the confirmation popup
Alcatel-Lucent 8/9 series sets: Timer used by the Input Method Editor (IME) for
input of non-Latin characters in Dial by name. Closes IME due to inactivity and
saves previous input.
Timer 356
Default value is 20 seconds.
Note:
The value of this timer should be less than the value of timer 357.
Alcatel-Lucent 8/9 series sets: Timer used by the Input Method Editor (IME) for
input of non-Latin characters in Dial by name. Closes IME due to inactivity and
clears previous input.
Timer 357
Default value is 60 seconds.
Note:
The value of this timer should be greater than the value of timer 356.
Timer 361 Max duration for call handling response on call control stimulus (internal timer)
Timer 362 Max duration for 180 Ringing response from SIP set
Timer 363 Max duration for 200 Ok response from SIP set
Timer 364 Max duration for 202 Accepted response from SIP set
Timer 365 Max duration for 487 Request Terminated response from SIP set
Timer 366 Max duration for Ack request from SIP set
Timer 367 Max duration for Bye request from SIP set
Timer 368 Max duration for Invite request from SIP set
Timer 369 Max duration for Notify request from SIP set
Timer 370 Com Server polling timer

Timer
TIMERS
No.
Alcatel-Lucent 8/9 series sets: timer for the Main page auto display
Note:
Timer 371
Minimum value is 10, maximum value is 255.
Timer expressed in units of 1s
OmniPCX Integrated Cellular Client service - Timer used when the Cellular Client
belongs to a twin set association.
When timer no. 373 is activated, it bypasses the Cellular Client forwarded to
Timer 373
voice mail. The main set rings when a call is presented to the twin set association
and the user can take the call.
One timer unit is equal to 100 ms
Timer for calls set up on hybrid logical links and maintained in case of switchover
(duplicated call servers).
Maximum time during which the end user's communications are frozen. At expiry
Timer 374 of the timer, the communication is released. The timer is stopped when the hybrid
logical link comes up again.
Default value: 1800 (180 seconds)
Timer for calls set up on hybrid logical links and maintained in case of switchover
(duplicated call servers).
Delay used by the software to differ sending messages (frozen state/normal
Timer 376 state), so that the two ends of the link are in a state compatible with sending/
receiving messages. At expiry of the timer, the message is sent.
This timer starts when the DTMF mode is activated on trunk group, upon receipt
Timer 377 of the send_dtmf_tones CSTA service. When this timer elapses, the
communication switches from DTMF to normal mode.
Timer for an ACD remote agent going to out of service state when his/her
Timer 383 external phone set is unreachable
Timer for a remote ACD agent connected to the Dissuasion tone . When the timer
Timer 384 elapses, the remote ACD agent switches to line lockout
19.3 Timer management

The Timers object is used to consult/modify the timers.

1. Select: System > Timers

Timer No Enter the number of the timer.
Timer units Enter the number of timer units (standard unit:100ms).

Caution:
Reserved values :
• “0” : means that the designated timeout is not used ,
• “1” : means that the designated timeout will be reset to
its original value at the next “shutdown”.
Caution:
Any unchecked modifications of the timers may cause the system to malfunction seriously. The timers
must only be modified with the help of an expert.
19.4 Maintenance
The tabtemp maintenance command displays the current value of timers.
When used without a specifying parameter tabtemp lists all available timers. When followed by one
or several timer numbers, it details the timers requested only.
Example:
(1)CPU_CS> tabtemp 7 12 26
+--------------+---------------------------------+----------------------------+
| | | values |
| delay number | delay label +--------------+-------------+
| | | number | step in ms |
+--------------+---------------------------------+--------------+-------------+
| 7 | TRAPGAR | 300 | 100 |
| 12 | TFAPPEL | 150 | 100 |
| 26 | EMISCMF | 2 | 100 |
+--------------+---------------------------------+--------------+-------------+

Chapter
20 Licenses
20.1 Overview
The system of licenses and locks allows the customer to purchase only the features that he needs. The
Call Server software is sold as a single package with a full OmniPCX Enterprise feature set. Under
these conditions, it would be unfair to charge customers for features they do not use.

The customer purchases one (or more) licenses for each feature required. Licenses are marketing
packages or sales "units". Licenses have matching locks that are functional units. The locks, installed
on the Communication Server, allow the features purchased to be used.
Purchase of licenses results in delivery of OPS (Order Preparation System) files. These lock files, also
called "OPS files", are installed on the OmniPCX Enterprise. They contain:
• A list of the locks purchased.
• The number of the system supporting the Communication Server. This number is referred to as the
"CPU identifier" or CPU ID". System number (CPU ID) is a unique number stored in PROM. It can
be read by the BIOS. For a duplicated Communication Server, there are two identifiers (one for
each Communication Server).
• A software key. The software key is an encrypted data item that depends on the locks purchased
and system numbers (CPU IDs). The software key guarantees that the OPS files are of ALE
International origin in order to prevent illegal use.
With R5.1, ALE International introduced the concept of "license move" (transfer). This feature allows
licenses to be moved from one machine to another, provided that both machines belong to the same
customer.

20.3.1 Licenses
There are several types of licenses:
• “Service Authorization License”. Purchase of this type of license authorizes the customer to use
this service. For example, ”E-CS REDUNDANCY” authorizes use of a duplicated Communication
Server.
• “License by steps”. Purchase of this type of license allows a certain number of users to access a
service. For example, “PHONEBOOK 10 EXT” authorizes" 10 sets to use the "Dial by Name
service. If you want 30 sets to have access to this service, you must purchase 3 licenses.
• “License by stage”. Purchase of this type of license allows a certain number of users to access a
service. For example, “HOTEL UP TO 150 EXT” authorizes the creation of a maximum of 150
customer sets in a hotel. Another license authorizes the creation of a hotel with over 500 sets. A
higher release (stage) can only be purchased if a lower release has already been purchased.
ALE International Marketing Services can provide a complete list of licenses.
Special case of the OmniVista 8770

Chapter 20 Licenses
The OmniVista 8770 has its own license system, similar to that of the Communication Server. In
addition, for an OmniVista 8770 to supervise an OmniPCX Enterprise, the latter must have a license
which allows such supervision.
There are several supervision licenses:
• Configuration
• Alarms
• Accounting (charging)
• Directory
• Traffic Analysis
20.3.2 Locks
Each lock has:
• A maximum value that depends on the licenses acquired. The maximum value of a lock can be:
• 0 or 1 when it corresponds to a "service authorization" license. 0: service prohibited, 1: service
authorized.
• 0 to 9999 (or 0 to 099999 as of R8.0) when it corresponds to "number of users" licenses. The
value of the lock is then equal to the maximum number of authorized users. For example, the
“PHONEBOOK EXT” lock sets the number of users authorized to use the "Dial by Name"
service.
• The value 9999/099999 indicates that the feature is authorized for unlimited use.
• A current value that represents the actual number of users on this service.
Some locks are referred to as "open" when they no longer correspond to a marketing offer. These locks
are systematically positioned at the maximum value.
Some locks are referred to as "not used" when the Communication Server software no longer uses
them.
20.3.3 Purchasing process

20.3.3.1 Tools
ALE International has developed the following tools:
• eCom: the ALE International Internet server dedicated to taking purchase orders for licenses and
also hardware.
• Actis: a software tool providing assistance in drawing up a sales proposal. Actis runs off-line on the
marketing representative's PC (laptop for example).
• eLP: a software tool providing and associating a new CPU ID in the OPS files.
There may be other tools for specific needs.
20.3.3.2 First sale/initial purchase

The marketing representative draws up a proposal tailored to the customer's needs. He uses Actis to
do this. The main features of Actis are:
• Integrated hardware and feature catalogs.
• Existing proposals can be copied/modified.
• Consistency of selected options is checked.
When the proposal is approved, the offer becomes an order which is transmitted to the eCom server.
The eCom server performs the following operations:
• Stores all customer configurations.

Chapter 20 Licenses
• Forwards the hardware order to the production department.

• Produces and sends the OPS files.
Orders can also be directly placed on eCom (without using Actis). However, the eCom interface offers
fewer features and requires Internet access.
20.3.3.3 Add-ons
There are two procedures:
• Via Actis: The marketing representative imports the old customer configuration stored on the eCom
server. He then modifies this jointly with the customer and exports it back to eCom. As at initial
purchase, eCom saves the new configuration, transmits the hardware order to the production
department if necessary, and produces and sends the new OPS files. This is the recommended
procedure.
It is also possible to recover the OPS files from the Communication Server work files using
"photoconfig". This procedure is used if the OPS files are not available on Actis or eCom. This
situation arises when commissioning does not comply with standard procedure.
• Directly on eCom: After connecting to the eCom server, the marketing representative can modify the
saved configuration. If necessary, a hardware order is sent to the production department and new
OPS files are sent.
20.3.4 OPS files

The OPS files are the following:
1. <offerld>.swk
2. <offerld>.hw
3. <offerld>.sw8770 (only if a OmniVista 8770 is ordered)
4. hardware.mao
5. <offerld>.zip
<offerld> is a string of characters specific to the site.
Files 1 and 3 are installed whatever the command mode. Files 2, 4 and 5 are installed with commands
performed via ACTIS.
When an add-on is installed, the OmniPCX Enterprise may have to be rebooted for installation of the
new OPS files. Reboot may or may not be necessary, depending on the locks modified. For information
on which locks require the OmniPCX Enterprise to be rebooted, see the List of software locks on page
399.
Caution:
The <offerId>.swk file is only produced by eCom. It is only accepted by the system if the software key is
consistent with the licenses.
20.3.5 Risk in case of fraudulent use

20.3.5.1 Legal risks
It is illegal to duplicate software programs or to unlock a feature without authorization. Offenders are
liable to be prosecuted by law.
20.3.5.2 Functional risks

When the system detects an inconsistency in the OPS files, it suspects illegal use, the Panic flag is set
up and the system runs in degraded mode. The phases of this degraded mode are:
• Action 1 (as soon as illegal use is detected)

Chapter 20 Licenses
• Displays a message on the attendant set as soon as it enters idle mode, with a mandatory order
for the attendant to acknowledge this message.
• Deletes the screen of the terminal system, and displays the incident message.
Acknowledgement is mandatory.
• Stores the incident in the incidents file.
• Continuous ringing on an alarm set.
• Some management commands can then no longer be performed and result in the following
error: "Software protection error".
• Action 2 (4 hours later):
• Displays a predefined string on all sets with a display.
• Action 3 (8 hours later):
• Loopback on actions 1 and 2.
The system checks its OPS files every four hours (up to R11.2) or five days (as of R11.2). If an
inconsistency is detected, it initiates the degraded mode procedure.
Note:
If the OPS files do not contain a Communication Server Identification (CPU_Id), the system suspects a
maintenance operation and postpones the degraded mode procedure for 30 days.
20.3.6 Changing the CS board for maintenance

The CS board (Communication Server support) may have to be changed. In this case, the identifier of
the new board no longer corresponds to the identifier declared in the OPS files. The installer has 30
days (before degraded mode is triggered) to provide notification of this change of situation.
ALE International
3
4
Technician
5
2
1
customer site
Figure 20.1: Block diagram of OPS file update operations following CS board replacement
1. Diagnosis and replacement of the CS board (replacement includes hardware operations, software
loading and configuration).
2. Retrieval of site information:
• The number of the new CS board.
• The number of the old CS board.
3. Site information sent to the eCom server.
4. Retrieval of new OPS files.
5. Installation of the new OPS files on the site.

Chapter 20 Licenses
20.3.7 License move (from R5.1)

20.3.7.1 Overview
A license is acquired for a specified PCX. If you want to transfer a license for a feature from a source
PCX to a target PCX, you must carry out a "license move".
When moving licenses, the licenses not used on the source PCX are recovered for use on the target
PCX. Licenses are moved using the eCom server.
Not all licenses can be moved. The transfer of some licenses is not recommended due to the
complexity of their implementation. See the list of transferable licenses in the List of software locks on
page 399.
Note:
License transfer/move can only be performed between two PCXs belonging to the same customer.
20.3.7.2 Transfer principle

To carry out a license move the installation technician performs the following operations:
• Creates new OPS files on the eCom server (fewer on the source PCX and more on the target PCX).
• Installs the OPS files on the PCXs.
• Increases services on the "destination" PCX and decreases services on the "source" PCX.
• Recovers the acknowledgement code from the source PCX. This acknowledgement proves that the
OPS files have been installed correctly and avoids any illegal use.
• Enters the acknowledgement code on eCom.
The acknowledgement code must be entered on eCom at the latest 30 days after creation of the OPS
files. If this deadline is not respected, ALE International will take legal action against the organization
performing the license move.
A specific procedure is required to move a lock, see License move on page 395.
20.3.7.3 Protection
Each OPS file contains a version number. To prevent illegal use, the system considers installation of
OPS files with a version number lower than that of the active files as constituting an inconsistency. The
installation technician has 5 days to rectify this.
Caution:
This protective mechanism complicates the installation technician's task. If the newly installed OPS files
present a problem, returning to the previous OPS files will result in inconsistency. The installation
technician will have to react promptly in order to rectify the inconsistency.
20.3.8 Test sets (from R5.1.1)

Various types of sets must be used to test the quality of voice calls on an OmniPCX Enterprise.
However, some customer configurations do not include all types of sets.
For such specific cases, ALE International authorizes (without it being necessary to have the
corresponding license) creation of the following sets (one of each type):
• One IP Phone
• One analog set
• One UA set

Chapter 20 Licenses
20.3.9 Licensing using FlexLM server

20.3.9.1 Overview
The FlexLM server is a license server used when:
• RSI (Routing Service Intelligence) licenses with FlexLM are required
For an RSI license presentation, see the RSI documentation.
• The OmniPCX Enterprise server is hosted on a virtual machine (for example with an OpenTouch
solution)
In this configuration, the OmniPCX Enterprise cannot read the CPU_ID. This entails that the
standard license process which consists in comparing the CPU_ID read on the hardware and the
Product-Id included in the license file cannot be used.
Reminder: a CPU_ID is a number which identifies a CPU. This identifier is hardware written and
cannot be modified.
Note:
• A FlexLM server can be requested by several OmniPCX Enterprise
• The FlexLM server is a license server which can be also used by non ALE International products
20.3.9.2 Single FlexLM server

This section describes operations when there is only one installed FlexLM server.
20.3.9.2.1 Configuration
On the OmniPCX Enterprise, a standard license file software.mao (or <offer>.swk) is installed.
This installation is described: OPS files on page 371.
The standard OmniPCX Enterprise license file has no FlexLM specificity. It includes the list of
authorized features and the Product-Id of the OmniPCX Enterprise authorized to use this license file.
In addition, the FlexLM server IP address is configured on the OmniPCX Enterprise.
The FlexLM server includes license files. These files include:
• The MAC address of the FlexLM server
• The list of supported licenses
For the FlexLM server RSI licenses and Product-Ids are licenses:
• RSI license is a number which limits the number of RSI users
• Product-Id is a license which can be used (check out) or unused (released) when the associated
OmniPCX Enterprise is in operation or stopped.
Note:
The Product-Id is used in a BiCS and OpenTouch context (OmniPCX Enterprise in a virtual machine).
• A signature to prove the ALE International origin of the license file and avoid frauds

Chapter 20 Licenses
software.mao file
Product-Id = 00011315
OmniPCX 1 ………..
FlexLM server
software.mao file
Product-Id = 0001717C
License file
software.mao file
Supported licenses:
00011315 0
0001717C 1 Product-Id= 0002D81A
0002D81A 0
………..
License status:
0 = used
1 = unused
Figure 20.2: Configuration of license files when a FlexLM server is used
20.3.9.2.2 Operations
When an OmniPCX Enterprise, with the FlexLM feature enabled is started, the license process of the
OmniPCX Enterprise sends a checkout message to the FlexLM server. This message includes the
Product-Id read in the OmniPCX Enterprise software.mao file.
On the FlexLM server, there are several cases to consider:
• The FlexLM server replies with a positive answer and the OmniPCX Enterprise is authorized to use
the features defined in the software.mao license file.
The transmitted license belongs to the list of supported licenses and the associated status is
unused:
• The license status switches from unused to used (checked out)
• A heartbeat dialog is started to maintain the license as "used". Every two minutes a heartbeat
message is exchanged between the OmniPCX Enterprise and the FlexLM server.
This dialog is supervised as follows:
•On the FlexLM server, the lost of the heartbeat dialog is considered as an OmniPCX
Enterprise shutdown and the associated license status switches to unused
• On the OmniPCX Enterprise, the lost of the heartbeat dialog causes retry messages every
two minutes. After four hours without answer, the Panic flag is set up and services are
restricted as defined:Functional risks on page 371.
• The OmniPCX Enterprise receives a negative answer or no answer:
• The transmitted license does not belong to the list of supported licenses
• The associated license status is already used
• The network or the FlexLM server is down

Chapter 20 Licenses
The OmniPCX Enterprise repeats the checkout message every three minutes until a positive
answer is received. As of R11.2, after five days without a positive answer, the Panic flag is set up
and services are restricted as defined: Functional risks on page 371.
When the Panic flag is up, the OmniPCX Enterprise sends a checkout message every five minutes until
a positive answer is received. When a positive answer is received, the Panic flag is reset and services
are recovered.
When a checkout message or a heartbeat message fails, a warning message is displayed on the
OmniPCX Enterprise console.
20.3.9.3 CPU duplication

In a duplicated CPU configuration, the main and standby CPUs are installed with the same
software.mao license file (same Product-Id) and the same database (same number of RSI license).
Only the main CPU requests the FlexLM server with checkout messages as described: Operations on
page 375. The standby CPU remains silent.
When the main CPU stops or crashes, the heartbeat dialog is stopped. After three minutes without
heartbeat dialog, the FlexLM server considers the main CPU is down and releases the associated
license. In other words, the associated license status is set to unused.
When the standby CPU switches to main, it requests the FlexLM server with a checkout message as
described: Operations on page 375. The associated license status is unused and the answer is a
positive answer. The new main CPU can operate normally.
In some configurations, when the stand-by CPU becomes main, first requests to the FlexLM server can
fail because the associated license has not yet been released. After a delay the associated license is
released and can be reused by the new main CPU.
Note:
In a duplicated CPU configuration, two CPU-Ids are included in the software.mao license file (one for each
physical machine). In a configuration with Product-Id discovery, only the first Cpu-Id is transmitted to the FlexLM
server as Product-Id, whatever the CPU which has the main role.
20.3.9.4 FlexLM server duplication

When the FlexLM server or the network crashes, the main CPU cannot get authorization to use its
software.mao license file. As of R11.2, after five days , services are restricted.
To improve functional security, the FlexLM server can be duplicated.
Two FlexLM servers with the same configuration file can be installed.
At startup, the OmniPCX Enterprise sends a checkout message to the first FlexLM server. If no positive
answer is received, the OmniPCX Enterprise tries alternatively the first and the second FlexLM server.
As of R11.2, these retries are sent for five days before the Panic flag is raised and service is restricted
as described: Functional risks on page 371.
After a positive answer, a heartbeat dialog is set with the FlexLM, which responds positively. This
dialog is supervised a described: Operations on page 375.
In case of FlexLM server duplication and OmniPCX Enterprise duplication on different subnetworks, it
is recommended to install a CPU and a FlexLM server in one subnetwork and the duplicated CPU with
the duplicated FlexLM server in another subnetwork.

Chapter 20 Licenses
20.3.10 Licensing using Cloud Connect

20.3.10.1 Overview
As of R12, Communication Servers can connect to a centralized infrastructure called Cloud Connect
Infrastructure (CCI) and benefit from services such as Right-To-Run (RTR). The RTR service offers
license control and runs at both CCI and Communication Server level.
If the Communication Server includes a CC-SUITE-ID and its internal RTR service is activated, it can
register to the CCI (see: Connection to the CCI (First Time Registration) on page 378 ) and establish a
dialog with the RTR service of the CCI (CCI/RTR service). Periodically, products ask the CCI/RTR
service if they can run, by sending requests (see: License control by the CCI/RTR service on page
380). The CCI/RTR service detects when the same license is used simultaneously by several products.
It does not require any hardware identifier or physical dongle to ensure that a given product with its
license runs only once. If fraudulent usage is detected, the CCI/RTR service can restrict product usage.
The RTR service applies to Communication Server running either on a physical server or virtual
machine. In virtualized environment, the RTR service allows the Communication Server to run without
a dongle. The RTR service cannot run on Passive Communication Servers (PCS).
FTR service
RTR service
CCI (XMPP server)
WAN
1. Registration (FTR)
2. License control (RTR)
DNS server
Proxy (Firewall/NAT)
FTR service
RTR service
(OmniPCX Enterprise)
Figure 20.3: CCI architecture
The CCI/RTR service does not replace existing licensing mechanisms at product level. A valid license
file is still required (*.swk file for the OmniPCX Enterprise). CPU-ID and CC-SUITE-ID can coexist in
the same *.swk license file.
The RTR service, running on the Communication Server can be activated or disabled in PCX
configuration. Communication Servers that are not configured to use the RTR service continue relying
on existing licensing mechanisms, based on hardware identifier, or physical dongle for virtualized
deployments (see: Licensing switchover between FlexLM server and CCI/RTR service on page 381).

Chapter 20 Licenses
20.3.10.2 Connection to the CCI (First Time Registration)

To perform a First Time Registration (FTR) with the CCI, the Communication Server requires the
following parameters:
• CC-Suite-ID
• DNS server IP address(es)
• Optionally, HTTP proxy parameters if required on site
These parameters must be entered in the Communication Server via the netadmin command (see:
Configuring the FTR parameters on page 392). The CC-Suite-ID may be present in the license file
associated to the Communication Server (*.swk). When it is present, the Communication Server uses
the CC-Suite-ID provided in the *.swk file to connect to the CCI. You can verify if a CC-Suite-ID
is present in the license file via the netadmin or spadmin command.
Connection to the CCI (FTR) is started manually from the netadmin command (see: Performing FTR
on page 393). With the parameters entered previously in the Communication Server, the FTR tool tries
to register to the CCI using its activation account. If the registration fails, the FTR tool returns an error
to netadmin. The error can be local (invalid address, wrong CC-Product-ID, DNS server not
reachable) or from the CCI (authentication problem, service unavailable).
When FTR is successful, the Communication Server receives back some credentials parameters from
the CCI. These credentials are used to establish a permanent secure connection with the CCI. All
further communication with the CCI is done over this secure connection.
This permanent connection with the CCI is automatically established by the system. There is no
manual activation required. It is established only on the Main CPU. In case of switchover, the link is
restored as soon as the Standby CPU becomes Main.

Chapter 20 Licenses
FTR service
CCI (XMPP server)
WAN
XMPP over websockets + TLS
Proxy (Firewall/NAT)
DNS server
FTR service
(OmniPCX Enterprise)
Initial parameters: Final parameters:

Netadmin configuration: - Jabber ID
- CC-SUITE-ID (if it not present in SWK file) - Password
- Proxy Parameters with: - Final CCI hostname and port
. IP
. Port (optional)
. Login/password (optional)
- DNS Server IP address (optional)
Figure 20.4: FTR architecture
20.3.10.3 FTR in a Communication Server duplication

FTR parameters are encrypted and stored in a Netadmin file, which simplifies duplicated
Communication Server update procedures. In a Communication Server duplication, FTR parameters
must be manually copied from the local Communication Server to the duplicated Communication
Server (see: Updating the standby Communication Server with the FTR parameters on page 395). In
case of failure of the local Communication Server, the duplicated Communication Server can connect
to the CCI with the FTR parameters copied previously in its database.
Important:
The activation account used to perform FTR operation remains, for convenient reasons (need to resume
installation …) available a few days after the first successful FTR. It is possible to renew the FTR operation
during this delay, but the FTR service in infrastructure generates a new password each time it is
successfully requested.
If a second request is performed by the standby Communication Server, it retrieves a different
password. Only the latest password is valid for permanent connection to the CCI. This leads to an
important risk while synchronizing Communication Server. If synchronization is executed from the

Chapter 20 Licenses
Communication Server hosting an invalid password, the system is not able to reconnect to the CCI, if
the permanent link is disconnected.
To avoid these synchronization problems, FTR operations must only be performed on the main
Communication Server. Any successful FTR must be followed by a manual synchronization from the
CPU on which the FTR has been performed to the redundant CPU.
20.3.10.4 FTR with PIN code

Following a fraud detection, an administrator change, or in case of Panic mode, it may be necessary to
reset RTR parameters and reinitialize the system credentials for permanent connection to CCI. In this
case, you must request a temporary activation account to your helpdesk, which returns a PIN code,
composed of 6 digits (0-9). To reset the parameters, a specific FTR operation (FTR with PIN code)
must be performed. It can be performed from the netadmin dedicated menu (see: Performing FTR
with a PIN code on page 393). A new set of credentials is retrieved and all connections related to
system’s CC-Product-ID are released. Then system reconnects using these new obtained
credentials. In addition, RTR parameters are reset.
20.3.10.5 License control by the CCI/RTR service

Once connected to the CCI (after successful FTR), the Communication Server starts a dialog with the
centralized CCI/RTR service, provided that the RTR service present on communication Server is
activated (see: Activating the RTR service on page 394).
The Communication Server periodically connects to the CCI/RTR service to verify if it has the right to
run: it automatically decrements its qualifying period every day if it cannot reach the CCI, or if it
receives an error message. If it receives a response, the Communication Server increments this
qualifying period, in the limit of 30 days.
The Communication Server can be in one of the following states:
• Normal: The Communication Server communicates periodically with the centralized CCI/RTR
service. Its qualifying period is positive (in the limit of 30 days).
• Panic: when the qualifying period has been decremented to zero, the Communication Server
switches into panic and runs in degraded mode. The only way to exit from panic is to execute an
FTR with PIN code (see: Performing FTR with a PIN code on page 393).
The information provided in the responses from the CCI/RTR service are encrypted and stored on the
Communication Server. In a Communication server duplication, this information is backed up on the
standby Communication Server without any user intervention.

Chapter 20 Licenses
(OmniPCX enterprise)
Successful FTR
Qualifying period = 30 days
Normal state
Qualifying period > 0 from CCI/RTR service
Or no CCI/RTR answer
Or no CCI login
Qualifying period = 0 days FTR
Panic state
Qualifying period decremented by one everyday if the CCI/RTR service response is NOK
Or by the product (if no CCI/RTR answer or no CCI login)
Note:
If the Communication Server includes a CC-SUITE-ID and its internal RTR service is activated (Cloud
Connect RTR Enabled is set to YES), then the RTR service is started in product level. In such cases, If FTR
is not performed, or not successful, or final connection to CCI is not established, then the Communication
Server automatically decrements its qualifying period every day. The Product may run into degraded
mode when the qualifying period reaches 0.
Figure 20.5: Communication Server states
20.3.10.6 Licensing switchover between FlexLM server and CCI/RTR service

A reboot of the Communication Server is required after a licensing switchover between FlexLM and
CCI/RTR service. After reboot, the RTR service on the Communication Server is started if it has been
activated in PCX configuration, and if the CC-SUITE-ID is present on the Communication Server.
When this is not the case, licensing via FlexLM is used, provided that it has also been activated on
PCX configuration. When this is not the case, the CPU-ID is used for licensing.
table 20.1: Licensing selection
FlexLM enabled RTR enabled Licensing mode used

(and CC-SUITE-ID present)
Yes Yes Not allowed
Yes No Flex-LM licensing
No Yes CCI/RTR licensing
No No CPU-ID verification

Chapter 20 Licenses

20.4.1 Principle
To configure locks:
• Install the OPS files to apply the licenses acquired: Restoring OPS files from the Communication
Server hard drive on page 382
• Back up the OPS files in order to perform an add-on: Saving OPS files on the Communication
Server hard drive on page 382
• Manage OPS files: Managing OPS files on page 383
• Restart after detecting an inconsistency: Restart after detecting an inconsistency on page 386
For these operations, the manager can use the following tools:
• swinst: procedure described below.
• OmniVista 8770: procedure described in the OmniVista 8770 documentation.
• Wizard: procedure described in the Wizard documentation.
20.4.2 Managing OPS files with swinst

OPS configuration access: swinst > Expert menu > OPS configuration
OPS configuration general menu:
OPS management menu Installation FACILITIES 2.70
1 Backup OPS files on cpu disk

2 Restore OPS from cpu disk
3 OPS administration
4 Software protection recover
5 Backup OPS files on USB key
6 Restore OPS from USB key
7 Clean OPS files on USB key
Q Go back to previous menu
Your choise [1..11, Q] ?
The swinst tool has a number of functions. Only functions related to OPS files are described here.
For a full description of the "swinst" tool, refer to the document [13].
20.4.2.1 Saving OPS files on the Communication Server hard drive

Access: swinst > Expert menu > OPS configuration > Backup OPS files on cpu disk
This command is used to recreate OPS files from work files. The files created with this command are
available in either the directory /usr4/BACKUP/OPS or DHS3dyn/BACKUP/OPS. This operation is
implemented in the case of an add-on, it is sometimes called “photoconfig”. A file transfer operation
(using ftp, for example) must be performed to retrieve these files from the Communication Server.
20.4.2.2 Restoring OPS files from the Communication Server hard drive
Access: swinst > Expert menu > OPS configuration > Restore OPS from cpu disk
This command is used to install the OPS files previously copied (via ftp, for example) in the directory /
usr4/BACKUP/OPS. In some cases, swinst will ask for the Communication Server to be rebooted to
apply these changes.

Chapter 20 Licenses
Caution:
Using the swinst tool is the only correct method for installing the OPS files. Any other method (for
example, direct copy) would cause the system to switch to fraudulent (illegal) use status with the
corresponding consequences (operation in degraded mode).
For an add-on which affects only the licenses, the only file provided is <offerId>.swk.
For an add-on which affects the licenses and a hardware item, the <offerld>.swk, <offerld>.hw,
hardware.mao, offerld.zip and <offerld>.sw8770 (optional) files are provided.
If the files to be installed have a version (release) number lower than that of the files currently installed,
the installation takes place. However, the system switches to fraudulent (illegal) use status. The
manager is informed of this by a warning message and has five days to rectify the situation. This check
is linked to the "license move" procedure.
Caution:
When you install OPS files for the large equipment capacity feature on a Communication Server in small
equipment capacity, swinst will ask you to reboot the system to take into account the large capacity. You
must then re-install the OPS files. You can use the command siteid to see the equipment capacity level of
the Communication Server.
20.4.2.3 Managing OPS files

Access: swinst > Expert menu > OPS configuration > OPS administration
20.4.2.3.1 Main menu
Display current counters ........................... 1
Display active file ................................ 2
Check active file coherency ........................ 3
Install a new file ................................. 4
Read the system CPUID ................................ 5
CPU-Ids management ................................. 6
Display active and new file ........................ 7
Display OPS limits ................................. 8
Display ACK code ................................... 9
Exit ............................................... 0
choice :
Note:
This swinst menu is identical to the spadmin maintenance command.
20.4.2.3.2 Display current counters/locks (1)

Result of the command:
(SP) Software Protection counters :

PANIC Flag : 0 (1)
Group Telephony Counter : 0 (2)
Call By Name Counter : 9
....................
1. “PANIC Flag” status. The “Panic Flag” indicates that an inconsistency has been detected in the OPS
files and that the degraded mode procedures of the system are activated:
• PANIC Flag = 0 normal operation.
• PANIC Flag = 1 operation in degraded mode.
2. List of counters corresponding to each lock. For example, if the manager has authorized "Call By
Name" for 9 users, the “Call By Names Counter” is equal to 9.
20.4.2.3.3 Display active file (2)
20.4.2.3.3.1 General case
DLL version = 0110 (1)
File version = 0 (2)

Chapter 20 Licenses
OXE version = 0110 (3)
Soft Key = a3661ef81e72228d5edb (4)
Cpu Id0 = 000011ce (5)

Cpu Id1 = 0000dd71
Your System CPU_Id: 000011ce (6)
System CPU_Id found (7)
CC-SUITE-ID = 1496-6942-3024-2885-3978 (8)
Handle 4760 = 0000c1e1 (9)
Timestamp :
Fri Feb 8 10:16:30 2016 (10)
SP_OPS_Version = 17B01 (11)

1 GroupTelephony = 9999 (12)
2 Phonebook users = 20
...............
301 Hard Key 1 = 085B (13)
301 Hard Key 2 = 08F3
1. Reserved for Technical Support.

2. Displays OPS file version.
3. Reserved for Technical Support.
4. Displays the software key or checksum.
5. Displays authorized CPU-Ids. If the Communication Server is duplicated, there are two CPU-Ids.
6. Displays the business reference for eCom. This reference is either the CPU-Id or, if the hard key is
used, an arbitrary reference provided by eCom. This arbitrary reference is sometimes called a
virtual "CPU-Id".
7. Indicates that local system CPU-Id has been found in the list of authorized CPU-Ids.
8. Displays the CC-SUITE-ID used by the Communication Server to connect to the Cloud Connect
Infrastructure (CCI) (see: Configuring licensing via Cloud Connect on page 391).
9. Displays the authorized OmniVista 8770 CPU-Id.
10.File creation date.
11.Displays the OPS version from which this file was created.
12.List of locks with the maximum value authorized (depending on purchase options). For moveable
locks, the system adds the current value in brackets.
13.Displays hard keys if present or 0000 if there are no hard keys present.
20.4.2.3.3.2 Errors
DLL version = 0110
File version = 0
OXE version = 0110
Soft Key = a3661ef81e72228d5edb
Cpu Id0 = 000011ce

Cpu Id1 = 0000dd71
Your System CPU_Id: 000011ce (1)
System CPU_Id not found! (2)
***************************************** (3)
* 30 remaining day(s) to fix this issue *
*****************************************
CC-SUITE-ID = 1496-6942-3024-2885-3978
Handle 4760 = 0000c1e1
Timestamp :
Fri Feb 8 10:16:30 2016

Chapter 20 Licenses
SP_OPS_Version = 17B01
1 GroupTelephony = 9999
2 Phonebook users = 20
...............
.................
1. Displays the business reference for eCom.
2. Displays that CPU-Id is incorrect.
3. Displays the number of days remaining before the procedure for switchover to degraded operating
mode is launched.
20.4.2.3.4 Check active file consistency (3)
The tool checks whether the checksum is compatible with the locks and Communication Server
number.
Result of the command when the check is correct:
> Checking active file /DHS3data/mao/software.mao
File OK
Result of the command when the check is incorrect:

> Checking active file /DHS3data/mao/software.mao
Error : Illegal hardware key
20.4.2.3.5 Install a new file (4)
This command is identical to Restoring OPS files from the Communication Server hard drive on page
382.
20.4.2.3.6 Read the Communication Server CPU-Id (5)
The tool displays Communication Server number. For example:
If the identifier is a CPU-Id:
System CPU-Id: 00006ff9
If the identifier is a hard key:

Your Hard Key: 8AB5
20.4.2.3.7 CPU-Ids (Communication Server number) management (6)
This command allows an installation technician to carry out an on-site Communication Server add-on
or Communication Server replacement. For sites which do not have access to eCom, the information
may be sent by telephone or fax.
Sub-menu:
Spadmin: CPU_Ids management
----------------------------
Add CPU-Ids .................................... 1
Remove CPU-Ids ................................. 2
Update CPU-Ids ................................. 3
Back to previous ............................... 4
choice :
The tool asks the operator to enter Communication Server number(s) and the new software key. The
operation is only performed if the new software key is consistent.
20.4.2.3.8 Display active and new file (7)
This command displays the contents of the current file and of the file to be installed in two columns.
The file to be installed should be called “software.new” and should be located in the directory /
DHS3data/mao. Display format is the same as that shown in section Display active file (2) on page
383.
20.4.2.3.9 Display OPS limits (8)
OPS limits

Chapter 20 Licenses
Remanent size (Kb) = 15162

Number of stations = 1977
Number of trunks = 384
Number of half-contexts = 695
Stand-alone = 0
Number of BLF = 0
Phone-book (x 2000) = 3
SBC = 0
BLF = 0
4635 = 0
Hotel accesses = 16
ACD supervisor accesses = 0
Multi-site CCS accesses = 0
Nb of set display languages = 4
Nb S0 Buses = 100
Nb fictive clients = 500
Nb ACT = 3
Param 20 = 0
Number of Nice Monitoring = 0
Number of Casual Conferences = 0
This command displays the maximum values that can be configured on this site. These maximum
values depend on the software used and on the hardware configuration of the site. Consequently, there
is no reason to purchase locks for higher values as they cannot be used.
20.4.2.3.10 Display ACK code (9)
This command displays the acknowledgement code. The acknowledgement code is used when a
license is transferred (moved).
20.4.2.4 Restart after detecting an inconsistency

Access: swinst > Expert menu > OPS configuration > Software protection recover
This command is used when an inconsistency has been detected. This command is used to restart
station display for a duration of four hours, which gives the technician time to intervene. This command
can be repeated ten times. A reset must then be performed to re-validate the features. This operation
was formerly performed using the sprecover command.
20.4.2.5 Saving OPS files on USB key

This option allows to save local or remote OPS files on an USB key. This function is only available on
CPU7-2, Appliance Server and Blade Server.
Access:
swinst > Expert menu > OPS configuration > Backup OPS files on USB key
The user is prompted to select the OmniPCX Enterprise.
Name of host (default localname) ->
By default, the local OPS files are saved.

After confirmation, the OPS files of the selected OmniPCX Enterprise are saved on the USB key.
Note:
The USB key must be previously enabled (refer to the document [13]).
20.4.2.6 Restore OPS from USB key

This option allows to restore OPS files from an USB key. This function is only available on CPU7-2,
Appliance Server and Blade Server.
Access:
swinst > Expert menu > OPS configuration > Restore OPS from USB key
Select the OmniPCX Enterprise.

Chapter 20 Licenses
The available folders are:

localname
hostname1
hostname2
hostname3
...
Name of folder (default localname) ->
Name of host (default localname) ->
After confirmation, the selected files are installed on the local or on the remote OmniPCX Enterprise.
Note:
The USB key must be previously enabled (refer to the document [13]).
20.4.2.7 Cleaning OPS files on USB key

Access:
swinst > Expert menu > OPS configuration > Clean OPS files on USB key
Select the OmniPCX Enterprise.
The available folders are:
localname
hostname1
hostname2
hostname3
...
Name of folder (default localname) ->
The list of the OPS files is displayed and after confirmation, the selected files are deleted. This function
is only available on CPU7-2, Appliance Server and Blade Server.
20.4.3 Consulting locks via the configuration tool

Lock values can be viewed using the configuration tool (mgr or OmniVista 8770).
1. Select: System > Software Package
Package Number Select the name of the lock to be consulted.
Authorized Limit Displays the maximum value authorized for this lock.
Current Value Displays the current value of the lock.
Private Route type • True: the trunk group to be used is a private trunk group
(trunk group private NPD used).
• False: the trunk group to be used is a public trunk group
(trunk group public NPD used).
20.4.4 Processing the OPS files for OmniVista 8770

The OmniVista 8770 OPS file (<offerld>.sw8770) is not functional on the OmniPCX Enterprise.
However, this file is used by the ACTIS software for add-ons when eCom is not used. The ACTIS
procedure first requires the OPS files to be retrieved (“photoconfig” operation). If the
<offerld>.sw8770 file is not present on the PCX, it is easy to forget it. To avoid this problem, it is
highly advisable to copy this file to the PCX at installation.
To do this, proceed as follows:

Chapter 20 Licenses
• Transfer, via ftp, the file “<offerld>.sw8770” to the directory “/usr4/BACKUP/OPS”.

• Activate the OPS files (access path: swinst > Expert menu > OPS configuration > Restore OPS
from cpu disk). The “<offerld>.sw4760” file is then saved, with the other OPS files, to the
directory /usr3/mao.
During the “photoconfig” operation (swinst > Expert menu > OPS configuration > Save OPS files on
cpu disk) the file “<offerld>.sw8770” is copied to the directory /usr4/BACKUP/OPS with all the other
OPS files.
When the add-on operation is complete, do not forget to place the new file on the PCX.
20.4.5 Incidents/errors
If the system detects an inconsistency, it outputs fault "5906" on a daily basis:
"xxx day(s) remaining before changing to fraudulent state"
The installation technician is thus informed of the time remaining to rectify the problem.
When a FlexLM server is used, the following incidents can be displayed:
• 0640: FLEX_ERROR_SERVER
Example: 0640=: FlexLM (135.117.164.18-27000) No checkout can be realized 3 4 (No checkout
because invalid license name, server busy, invalid license file …)
• 0641: FLEX_CONSISTENCY
Example: 0641=: FlexLM (135.117.164.18-27000) Checkout request exceed the limits 5 (Request
for more licenses than available on the FlexLM server)
• 0642: FLEX_SERVER_LINK
Example: 0642=: FlexLM (135.117.164.18-27000) Connection with the FlexLM server lost 1 15
• 0645: FLEX_PANIC_SET
Example: 0645=FlexLM (172.19.111.147-27000): OXE license checkout failure. 0 days remaining
before going to panic
The incident 0645 indicates the connection to the FlexLM server is lost. This incident is triggered
every 4 hours until the connection to the FlexLM server is reestablished. It also displays the days
remaining before the system goes in panic mode.
• 0646: FLEX_PANIC_CLEAR
Example: 0646=FlexLM (172.19.111.147-27000): successful checkout of OXE licence
The incident 0646 indicates the connection to the FlexLM server is reestablished. This incident is
triggered only once.
When a Cloud Connect RTR server is used, the following incidents can be displayed:
• 648: RTR OK/NOK with Remaining Qualifying Period and Cause
• 649: RTR Panic Mode Raised due to RTR continous failure
• 650: RTR Panic Mode Released. This incident is triggered when the Cloud Connect process does
not run properly. The Communication Server switches to panic
• 651: Clearance of incident 650. It is generated when the Cloud Connect process runs or responds
again
20.4.6 Configuring CSTA/TSAPI parameters (UCaaS configuration)

The OmniPCX Enterprise can operate in common or Unified Communication as a Service (UCaaS)
configuration. The OmniPCX Enterprise configuration is defined by the lock 386 UC as a Service:

Chapter 20 Licenses
UCaaS configuration is enabled when the lock is set to 1. This lock cannot be moved. It requires a
reboot to be updated.
Up to R11.1, monitoring/recording operations via CSTA or TSAPI are controlled by software locks,
which contain the number of licenses:
• If there are enough licenses, the monitoring/recording operation is enabled.
• If there are not enough licenses, the OmniPCX Enterprise returns an error.
This applies to the OmniPCX Enterprise whatever its configuration (UCaaS or common). As of R11.2,
when the OmniPCX Enterprise operates in UCaaS configuration, monitoring/recording operations
performed by CSTA or TSAPI are controlled by system parameters, and no longer by software locks.
This applies to the following operations:
• CSTA monitoring requests: The licenses are incremented/decremented for the devices monitored
by CSTA, based on the value defined in the CSTA Requests monitored parameter, and no longer
on the value of software lock 101 CSTA monitoring requests.
• TSAPI monitoring: The licenses are incremented/decremented for the devices monitored by
TSAPI, based on the value defined in the TSAPI max Authorized parameter, and no longer on the
value of software lock 114 TSAPI server.
• Local/remote recording through CSTA: The licenses are incremented/decremented for call
recording by the CSTA recording server (also identified as CSTA_TDM_LINK), based on the value
defined in the CSTA recording B Channel parameter, and no longer on the value of software lock
145 CSTA Recording B channel. Similarly, for remote recording by CSTA, the value of
Remote recording TS parameter is used instead of software lock 164 CSTA Record
Networked.
• IP recording through CSTA: The licenses are incremented/decremented for VoIP communication
recording by the CSTA recording server (also identified as IP_DR_LINK), based on the value
defined in the CSTA record B Channel Over IP parameter, and no longer on the value of software
lock 334 Max. IP recording.
To modify these CSTA/TSAPI system parameters:
1. Select: System > Other System Param. > RTU Parameters
2. Select a system parameter corresponding to a CSTA or TSAPI operation, and configure its value
The value can be:
Parameter Minimum value Maximum value Default value
CSTA recording B channel 0 600 0
Remote recording TS 0 600 0
CSTA record B channel over 0 8000 0

IP
CSTA Requests monitored 0 20000 (*) 0
TSAPI max Authorized 0 5000 0
(*): 20000 is the maximum number for CSTA monitoring of Business sets, CCD/RSI agents, CCD
pilots, PBX groups, RSI points, IVR access, SOSM devices and numbers, standard CSTA clients,
TSAPI, NICE/DR_Link recorder, AFE, A4980, TAPI.

Chapter 20 Licenses
Note:
A system parameter modification does not affect a current CSTA/TSAPI monitoring or recording.
OmniVista 8770 collects data from these CSTA/TSAPI system parameters. For OmniPCX Enterprise
operating in common configuration (non UCaaS), monitoring/recording operations performed by CSTA
or TSAPI are still controlled by software locks.
When the OmniPCX Enterprise operates in UCaaS configuration, you can display the values defined
for the CSTA/TSAPI system parameters via the cstainfo command.
Example:
Result of the cstainfo command when the CSTA/TSAPI system parameters are configured as follows:
• CSTA recording B channel parameter is set to 100
• Remote recording TS parameter is set to 100
• CSTA record B channel over IP parameter is set to 100
• CSTA Requests monitored parameter is set to 20000
• TSAPI max Authorized parameter is set to 100
20.4.7 Configuring a FlexLM server

To configure a FlexLM server:
1. Select: System > Licenses

Chapter 20 Licenses
FlexLM Licensing Enabled • No: no request to a FlexLM server. Licenses are processed
on the OmniPCX Enterprise only
• Yes: a FlexLM server is used in the process
This option is mandatory when the OmniPCX Enterprise runs
on a virtual machine or when RSI licenses are used.
Caution:
Verify that licensing via CCI/RTR is not activated (see:
Activating the RTR service on page 394). The two licensing
modes (FlexLM server and CCI/RTR) cannot run at the same
time.
Flex Server IP Address Enter the IP address of the main FlexLM server
Flex Server Port Enter the port number used on the main FlexLM server
Typically port number 27000 is used.
Flex Server 2 IP Address Enter the IP address of the duplicated FlexLM server
This parameter enables the FlexLM duplication function.
Flex Server Port Enter the number to use on the duplicated FlexLM server
Typically port number 27000 is used.
Product ID discovery • No: the CPU_ID of the CPU is checked with the
sofware.mao file
• Yes: the Product-Id of the sofware.mao file is checked with
the FlexLM server
Use Flex License • No: For the RSI feature, the system uses the license located
in the software.mao file.
• Yes: For the RSI feature, the system uses the license file
located on the FlexLM server.
Note:
Any modification of the FlexLM parameters requires rebooting.
20.4.8 Configuring licensing via Cloud Connect

20.4.8.1 Overview
Licensing via Cloud Connect consists in:
• Configuring the FTR parameters on page 392 in the Communication Server
• Performing FTR on page 393 to register product to the CCI
• Retrieving FTR status on page 394
• Activating the RTR service on page 394 allowing the Communication Server to communicate with
the RTR service of CCI for license control
• In a Communication Server duplication, Updating the standby Communication Server with the FTR
parameters on page 395

Chapter 20 Licenses
20.4.8.2 Configuring the FTR parameters

20.4.8.2.1 Opening the netadmin command
FTR parameter configuration is performed using the netadmin command:
1. Connect to the Communication Server with the root account
2. Run the command netadmin -m
A netadmin menu is displayed
20.4.8.2.2 Configuring the CC-Suite-ID
1. From the netadmin menu, select 19. 'Cloud Connect'
2. Select 1. 'CC-suite-ID'
If the license file (*.swk) includes a CC-suite-ID, its value is displayed on screen. if not, enter
the corresponding CC-suite-ID (for example: 1496B-6F423-302A3-28C85)
Note:
When it is available in the license file, the CC-suite-ID can also be displayed from the following tools :
• The spadmin command (see: Display active file (2) on page 383).
• The OmniPCX Enterprise configuration application of the OmniVista 8770: A Suite Id field is available
under the Configuration tab
Example:
19.Cloud Connect Menu
============================
1. 'CC-suite-ID'
2. 'Perform FTR'
3. 'View FTR Status'
4. 'PIN Code'
0. 'Previous menu'
What is your choice ? 1
CC-suite-ID is provided in license file.
The SUITE ID present in SWK file is 1496B-6F423-302A3-28C85
20.4.8.2.3 Configuring the DNS server IP address

1. From the netadmin menu, select 14. 'DNS configuration'
2. Select 2. 'Create/Update DNS setup' and enter the DNS server IP address
Example:
14.DNS Setup
============================
1. 'View DNS configuration'
2. 'Create/Update DNS setup'
3. 'Delete DNS Details'
0. 'Previous menu'
Primary DNS address (default is 127.0.0.1)?
135.250.161.173
Secondary DNS address (default is 127.0.0.1)?
Note:
14. 'DNS configuration' also allows to consult or delete the current DNS server IP address.
20.4.8.2.4 Configuring the proxy parameters
1. From the netadmin menu, select 15. 'Proxy configuration'
2. Select 2. 'Create/Update Configuration' and enter successively:
• The IP address of the proxy
• The credentials (login/password) to access the proxy

Chapter 20 Licenses
• The port used to access the proxy (default is 443)

Example:
15. HTTP Proxy Menu
============================
1. 'View HTTP Proxy Configuration'
2. 'Create/Update Configuration'
3. 'Delete HTTP Configuration'
0. 'Previous menu'
Host address? 135.250.161.173
Proxy Login? mylogin
Proxy password? xxxxxx
Proxy port (default is 443)? 8080
Note:
15. 'Proxy configuration' also allows to consult or delete current proxy parameters.
20.4.8.3 Performing FTR

2. Select 2. 'Perform FTR'
Example:
============================
1. 'CC-suite-ID'
2. 'Perform FTR'
4. 'PIN Code'
0. 'Previous menu'
================== TERMS AND CONDITIONS ==================
I do accept ALE Cloud Connect Terms & Conditions
"(www.enterprise.alcatel-lucent.com/Terms&Conditions) and
commit to inform my customer (y/n).y
Launching FTR ...
FTR Done Successfully
WARNING: Credentials to connect to CCI are not synchronized automatically with TWIN CPU.
Manual Synchronization is mandatory for proper functioning of system when CPU is changed
ftrtool has been exited
FTR Details
=============
FTR Status:Registered
Last FTR operation: Success
The ALE Cloud Connect Terms and Conditions are displayed until you accept it. If you refuse them,
the FTR operation is cancelled and the previous menu is displayed.
20.4.8.4 Performing FTR with a PIN code

Launching a FTR with a PIN code completely resets Cloud Connect configuration and parameters
while the system is still running. This operation can only be performed if the RTR and FTR services are
running on the Communication Server.
2. Select 2. 'Perform FTR'
3. Enter the PIN code composed of six digits (0-9), and press Enter
Example:

Chapter 20 Licenses

============================
1. 'CC-suite-ID'
2. 'Perform FTR'
4. 'PIN Code'
0. 'Previous menu'
Please enter the 6-digit pincode to perform FTR or press 'q' to exit 123456
Launching FTR ...
FTR Done Successfully
WARNING: Credentials to connect to CCI are not synchronized automatically with TWIN CPU.
Maunal Synchronization is mandatory for proper functioning of system when CPU Role is
changed
ftrtool has been exited.
FTR Details
===========
20.4.8.5 Retrieving FTR status

You can verify the current FTR status:
2. Select 3. 'View FTR Status'
The result presents the registration status of the system and the result of the last FTR operation
(and the error cause in case this operation failed). Note that the last operation status can be failed
even if the system is successfully registered, for instance if the FTR operation has been renewed on
a closed activation account.
Example:
============================
1. 'CC-suite-ID'
2. 'Perform FTR'
4. 'PIN Code'
0. 'Previous menu'
FTR Details
=============
20.4.8.6 Activating the RTR service

To activate/deactivate the RTR service on the Communication Server:
1. Select: System > Licenses
Cloud Connect RTR Ena- • No (default value): the RTR service on Communication Server is
bled disabled. Licensing via the CCI/RTR service is not available.
• Yes: the RTR service on Communication Server is activated. If a
CC-SUITE-ID is present on the Communication Server, licensing
via the CCI/RTR is started.
Caution:
For Communication Servers running on virtual machines, verify that
licensing via FlexLM server is not activated (see: Configuring a
FlexLM server on page 390). The two licensing modes (FlexLM
server and CCI/RTR) cannot run at the same time.

Chapter 20 Licenses

Note:
Any modification of the RTR parameter requires rebooting.
20.4.8.7 Updating the standby Communication Server with the FTR parameters
The FTR parameters (inputs and final parameters obtained from FTR) can be stored on the standby
Communication Server using any of the following commands:
• netadmin -m:
1. Connect to the Communication Server with the root account
2. Run netadmin -m
3. Select 10. 'Copy setup'
4. Select 2. 'Copy to twin CPU (all)'
This operation updates configuration on the duplicated Communication Server with the
configuration of the Communication Server in service.
Caution:
Before making a copy, verify that:
• Duplication and role addressing are managed in the same way on the two Communication
Servers.
• netadmin is not running on the duplicated Communication Server at the time of the copy.
• mastercopy:
1. Connect to the Communication Server with the mtcl account
2. Enter swinst and its password
3. Go to 2 Expert menu > 3 Cloning & duplication operations > 1 CPU cloning
Note:
For more information on the cloning operation, refer to: Ensuring Database Consistency by a Cloning
Operation on page 62.
20.5 License move

20.5.1 Overview
The procedures described below are for one license. However, it is possible to move several licenses
simultaneously (licenses of the same type or of different types).
The eCom server accepts deferred acknowledgement, which allows the OPS files for the source and
destination PCXs to be created simultaneously.
In general, the following rule must be respected: On a PCX, you must always have locks for the
services declared. Therefore, before "reducing" (the scope of) a lock, you must "reduce" the
corresponding service and before "increasing" a service you must increase the corresponding lock.
20.5.2 License: “10 Phonebook users” (lock 2)

• On eCom: create new OPS files for the source and destination PCXs.
• On the source PCX:
• Delete rights for the "Dial by name" feature on the selected sets.
• Install the reduced OPS files.
• Read the acknowledgement code.

Chapter 20 Licenses
• On the destination PCX:

• Install the increased OPS files.
• Assign "Dial by name" rights to the selected sets.
• On eCom: Enter the acknowledgement code read on the source PCX.
20.5.3 License: “CCD 5 agents pack” (lock 76)

Check that lock 13 (E-CS Engine) is "sufficient" on the destination node.
• Log off the agents to be moved.
• Reboot the cabinet.
• Log on the agents that have been moved.
20.5.4 License: “Roaming DECT” (lock 90)

Check that locks 175 (Mobile users) and 82 (Mobile terminal) are sufficient on the destination node.
Proceed in similar manner as for moving the license for “10 Phonebook users” (lock 2).
20.5.5 License: “ECC 4980 option 10 ext pack” (lock 117)

In order to transfer a number (n) of licenses, you must also transfer:
• "n" 116 locks (4980 standard).
• "n" 129 locks (4980 groupware).
• "n" 197 locks (G729 client) or 198 locks (G723 client) if the 4980s are linked to multimedia 2 PCs.
Proceed in similar manner as for lock 2 "Phonebook users", but delete rights to the "4980 professional"
feature (using the softphone administration tool) instead of deleting rights to the "Dial by name" feature.
20.5.6 License: “DECT encryption” (lock 127)

Check that locks 175 (Mobile users) and 82 (Mobile terminal) are sufficient on the destination node.
• Delete the right to encryption (only if the lock changes to 0).
• Add the encryption right (if this has not already been done).

Chapter 20 Licenses
20.5.7 License: “ECC My softphone 10 ext pack” (lock 129)

In order to transfer a number (n) of licenses, you must also transfer:
• "n" 116 locks (4980 standard).
• "n" 197 locks (G729 client) or 198 locks (G723 client) if the 4980s are linked to multimedia 2 PCs.
Proceed in similar manner as for lock 2 "Phonebook users", but delete rights to the "4980 groupware"
feature (using the softphone administration tool) instead of deleting rights to the "Dial by name" feature.
20.5.8 Set Licenses (locks 173, 174, 176 and 177)

Licenses concerned:
• Licenses: “10 UA fixed users” (lock 173).
• Licenses: “10 analog users” (lock 174).
• Licenses: “10 IP users” (lock 176).
• Licenses: “10 SIP users” (lock 177).
On the destination node, check that lock 13: “E-CS engine” is sufficient. In addition:
• If an IP set transfer is performed, check that lock 138 "IP equipments" is equal to lock 176.
• If a SIP set transfer is performed, check that lock 185 "SIP gateway" is set.
20.5.8.1 On an ABC-F Network

• Wireline (static) sets (UA and analog): delete physical equipment from the sets which are to be
transferred.
• IP sets: Change set type from "IP" to "non IP" for the sets to be transferred.
• SIP sets: Change set type from "SIP" to "Analog" for the sets to be transferred.
• Move the sets to be transferred.
• Wireline (static) sets (UA and analog): Assign new physical equipment.
• IP sets: Change set type from "non IP" to "IP".
• SIP sets: Change set type to "SIP".
20.5.8.2 On a Network other than an ABC-F Network

• Export data from the sets to be moved to the OmniVista 4760 or 4760i.
• Check the compatibility of the data with the capabilities of the destination PCX (and make any
modifications required).
• Delete the sets transferred.

Chapter 20 Licenses
• Import set data from the OmniVista 4760 or 4760i.

20.5.9 License: “10 Mobile users” (lock 175)

On the destination node, check that lock 13: "E-CS engine is sufficient and that locks 175 and 82 have
the same values.
• Export data from the sets to be moved to the OmniVista 4760 or 4760i.
• Delete the mobile sets to be moved.
• Reboot the cabinet if the license is greater than 250,
• Import set data from the OmniVista 4760 or 4760i.
20.5.10 License: “G729A Client” (lock 197)

On the destination node, check that lock 13 (E-CS Engine) is sufficient. In addition, ensure that locks
138 (IP equipments) and 176 (10 IP users) have the same value as lock 197.
Proceed in similar manner as when moving the license for “10 UA fixed users” (lock 173).
20.5.11 License: “OmniCellular client for 10 users” (lock 308)

On the destination node, check that lock 13 (E-CS Engine) is sufficient.
• Export data from “Cellular Client” sets to be moved to the OmniVista 4760 or 4760i.
• Delete the “Cellular Client” sets.
• Import the “Cellular Client” sets from the OmniVista 4760 or 4760i.
20.5.12 License: “Class service (CLIP) for 10 analog users” (lock 310)
On the destination node, check that lock 13 (E-CS Engine) is sufficient. In addition, if the sets are
assigned to eZ32 boards, check that lock 174 (analog users) is sufficient.
Proceed in similar manner as for lock 2 "Phonebook users".

Chapter 20 Licenses
20.6 List of software locks

20.6.1 List of OmniPCX Enterprise Locks
A lock is "Open" when it corresponds to a free license. It is then set to 9999 or to 099999 as of R8.0.
An "unused" lock is set to 0. It is not displayed by the “swinst” or “spadmin” commands.
For some locks, the value "0" cannot be used because the first corresponding licenses are free.
The "Moveable" column indicates whether the lock can be moved or not.
The “Reboot required” column indicates whether or not it is necessary to restart the system to apply
any changes made to the relevant lock.
Num- Name Possible values Moveable Reboot re-

ber quired
001 Group Telephony “Open” lock — —
002 Phonebook users 0/10/20/.../9999 (15000 as of Yes No

R8.0)
003 – Not used — —
004 Hotel guest sets 0/ 50/ 80/ 150/ 350/ 500/ No According to
1000/ 1500/ .../ 9500/ 9999 conditions,
(15000 as of R8.0) see:Note 1 on
page 420
(> or = lock 213 if different
from 0)
005 Multilingual voice prompts 0/1 No No
006 Hotel: AHL on V24 0/1 (= lock 126) No Yes
007 – Not used — —
008 – Not used — —
009 PSTN B channel “Open” lock — —
010 Voice guide 0/1 No No
011 – Not used — —
012 DISA 0/1 No No
013 E-CS engine 0/ 50/ 80/ 150/ 250/ 500/ No Yes

1000/ 1500/ .../ 9500/ 9999
(099999 as of R8.0)
= 9999 (099999 as of R8.0)
if lock 213 different from 0

Chapter 20 Licenses

ber quired
014 Integrated metering re- 0/1 No No

port
015 – Not used — —
016 – Not used — —
017 – Not used — —
018 – Not used — —
019 Corporate networking 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
> or = lock 213 if different
from 0
020 Automated attendant 0/ 6/ 9999 (099999 as of No No

R8.0)
021 No. of VPS ports 0/ 2/ 4/.../ 240 No No
022 – Not used — —
023 – Not used — —
024 – Not used — —
025 – Not used — —
026 – Not used — —
027 – Not used — —
028 – Not used — —
029 DECT/PWT Engine 0/1 No Yes
030 – Not used — —
031 – Not used — —
032 eLP: Move Agents CCD 0 / 5 / 10 / ... / 50 — —

eLP
033 eLP: OTTCC-PE present 0/1 — —

(not used anymore with
eLP
eLP V6.3

Chapter 20 Licenses

ber quired
034 eLP: PPU MCS system 0/1 — —

eLP
035 Free “Open” lock — —
038 Infocenter link 0/1 No According to

conditions, see:
Note 1 on page
420
039 Performance 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)
040 Real Time Incidents 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
(= lock 047)
041 DECT register 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(099999 as of R8.0)
(= lock 050)
042 Accounting users 0/ 50/ 80/ 150/ 2350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)
043 – Not used — —
044 4059 SBC 0/ 1/ 2/.../ 50 No According to

conditions, see:
Note 2 on page
420
045 4059 BLF 0/ 1/ 2/.../ 30 No According to

conditions, see:
Note 2 on page
420

Chapter 20 Licenses

ber quired
046 Fax server ABC-A link 0/ 1/ 2/.../ 28 No According to

conditions,
see:Note 3 on
page 420
047 Alarms 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)
048 – Not used — —
049 Directory 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)
050 Configuration 0/ 50/ 80/ 150/ 350/ 500/ No Yes

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)
051 Real Time Metering on 0/ 50/ 80/ 150/ 350/ 500/ No No

V24 1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
(= lock 042)
052 4635: Basic package 0 = none No According to

conditions, see:
1 = 4635J
Note 3 on page
2 = 4635H 420
053 – Not used — -
054 – Not used — —
055 – Not used — —
056 4635: Networking Octel- 0/ 2/ 4/.../ 64 No According to

Net conditions, see:
(= lock 057)
Note 3 on page
420

Chapter 20 Licenses

ber quired
057 4635: Fax manager 0/ 2/ 4/.../ 64 No According to

conditions, see:
Note 3 on page
420
058 4635: Call manager 0/ 2/ 4/.../ 64 No According to

conditions, see:
(= lock 057)
Note 3 on page
420
059 4635: Hotel manager 0/ 2/ 4/.../ 64 No According to

conditions, see:
(= lock 057)
Note 3 on page
420
060 4635: No of ports 0/ 2/ 4/.../ 64 No According to

conditions, see:
Note 3 on page
420
061 4635: No of hours 0/ 5/ 10/.../ 40 No According to

conditions, see:
Note 3 on page
420
062 4635: No of languages 0/ 1/ 2/.../ 8 No According to

conditions, see:
Note 3 on page
420
063 4635: Attendant manager 0/ 2/ 4/.../ 64 No According to

conditions, see:
(= lock 057)
Note 3 on page
420
064 – Not used — —
065 4635: Recording manag- 0/ 2/ 4/.../ 64 No According to

er conditions, see:
(= lock 057)
Note 3 on page
420
066 4635: Networking AMIS 0/ 2/ 4/.../ 64 No According to

conditions, see:
(= lock 057)
Note 3 on page
420
067 – Not used — —
068 – Not used — —

Chapter 20 Licenses

ber quired
069 – Not used — —
070 – Not used — —
071 – Not used — —
072 – Not used — —
073 – Not used — —
074 – Not used — —
075 Network Hospital (specific “Open” lock — —

to France)
076 CCD agents 0/ 5/ 10/.../ 2000 Yes No
077 CCS mono-site 0/ 1/ 2/.../ 60 No No
078 CRI call record interface 0/1 No No
079 ISVPN 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
(= lock 019)
080 VPN 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
(= lock 019)
081 Meet me conference (29 0/ 1/ 2/.../ 30 No No

parties)
082 No of DECT/PWT termi- 0/ 10/ 20/ ..../ 5000 No No

nals
(= lock 175)
083 Flow Metering on Ether- 0/ 50/ 80/ 150/ 350/ 500/ No According to
net 1000/ 1500/ .../ 9500/ 9999 conditions, see:
(15000 as of R8.0) Note 4 on page
420
(= lock 042)
084 4635 users 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)

Chapter 20 Licenses

ber quired
085 – Not used — —
086 Automatic directory pop 0/ 1/ 2/.../ 50 No According to

up conditions, see:
Note 2 on page
420
087 Beta test release 0 = OmniPCX Enterprise No No

version released
8 = Beta test OXE R5.0LX
9 = Beta test OXE R5.1
088 – Not used — —
089 Notification server 0 / 50 / 300 / 800 / 9999 — —
090 Mobility: Roaming 0/ 10/ 20/ .../ 5000 Yes No

DECT/PWT
091 Voice guide recording 0/ 1 No No

from Reflexes sets
092 – Not used — —
093 4635J IDENTIFICATION 0/ 1 No —

Chapter 20 Licenses

ber quired
094 WMI Workforce manage- 0/ 1 No No

ment interface
095 – Not used — —
096 – Not used — —
097 VPS users 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(099999 as of R8.0)
from 0)
098 Accounting for local calls 0/ 50/ 80/ 150/ 350/ 500/ No Yes
1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)
099 Accounting for ABC calls 0/ 50/ 80/ 150/ 350/ 500/ No Yes
1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)
100 CSTA profile 0 = None No Yes

2 = Call center
101 CSTA monitoring re- 0/ 5/ 10/.../ 9995/ 9999 No Yes

quests (099999 as of R8.0)
the Maximum depends on
OXE release.
102 CCS multi-site 0/ 1/ 2/.../ 60 No No
103 Real Time Interface 0/ 1/ 2/.../ 60 No No
104 – Not used — —
105 Compressed calls 0/ 1/ 2/.../ 9999 (099999 as No No

of R8.0)
106 Transfix Access X24/V36 “Open” lock - -
108 - Not used - —

Chapter 20 Licenses

ber quired
109 4635 : IP Octel Network- 0/ 2/ 4/.../ 64 No According to

ing conditions, see:
(= lock 057)
Note 3 on page
420
110 4635 : Global message 0/1 No According to

redundancy conditions, see:
Note 3 on page
420
111 Ubiquity 0/ 10/ 20/.../ 15000 No No
112 CCS LIGHT 0 / 1 / 2 / ... / 60 No No
113 CSTA pilots monitoring 0/ 1 No Yes
114 TSAPI server 0/ 5/ 10/.../ 2000 No Yes
115 CCA softphone 0/ 5/ 10/.../ 1000 No No

(< or = lock 076 if different
from 0)
116 OTUC Local My Phone 5/ 10/ 20/.../ 3000 No Yes

(4980 standard)
(= lock 129)
117 OTUC Local 4980 Option 5/ 10/ 20/.../ 3000 No Yes

(4980 advanced)
from 0)
118 – Not used — —
119 4980 nomadic logged 5/ 10/ 20/.../ 600 No Yes

(= lock 129 + lock 309)
120 – Not used — —
121 CLIP on VPS 0/ 2/ 4/.../ 240 No No

(= lock 021)
122 ACAPI via CMIP 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(099999 as of R8.0)
(= lock 050)
123 CSTA IVR ports moni- 0/ 5/ 10/.../ 5000 No Yes

tored

Chapter 20 Licenses

ber quired
124 – Not used — —
125 CCWeb Agents 0/ 5/ 10/.../ 1000 No No

from 0)
126 Hotel AHL link 0/ 1 No Yes
127 Encryption DECT/PWT 0/ 10/ 20/.../ 5000 Yes No

users
128 4615 No. of Access 0/ 2/ 4 No No
129 ECC My softphone (4980 5/ 10/ 20/.../ 3000 No Yes

Grp)
130 CSTA: Voice Recording 0/ 1/ 2/ 3/ 4 No Yes

Type
0 = none
1 = Nice
2 = DR-Link
3 = multi Nice (from M2.300)
4 = multi DR-Link (from
M2.300)
131 Remote LIO 0/ 16/ 32/ 48/ .../ 16xN No No
132 IP-Trunk 0/ 10000 No No

(= lock 187)
133 Mastered conference 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)
134 Multi-tenant 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
( > or = lock 213 if different
from 0)
135 G729A Server 0/ .../ 9999 (099999 as of No No

R8.0)

Chapter 20 Licenses

ber quired
136 Priority 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)
137 Call restriction 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)
138 IP Clients 0/ 10/ .../ 9990 (15000 as of No Yes

R8.0)
(= lock 176 + lock 317+ lock
330)
139 – Not used — —
140 – Not used — —
141 – Not used — —
142 – Not used — —
143 TAPI premium server 0/ 5/ 10/.../ 5000 No Yes
144 – Not used — —
145 CSTA Recording B Chan- 0/ 5/ 10/.../ 600 No Yes

nel
146 PWT MOBILITY (UTAM) 0: non US market No No

1: US market
(according to lock 029)
phased out
147 – Not used — —
148 IP Call Server “Open” lock - -
149 – Not used — —
150 – Not used — —

Chapter 20 Licenses

ber quired
151 4635 : VPIM 0/2/4/.../64 No According to

conditions, see:
(= lock 057)
Note 3 on page
420
152 Radio link 0/1 No No
153 SNMP TRAP 0/1 No Yes
154 Additional S0 features 0/1 No No
155 Additional safety features 0/1 No No
156 Interphony features 0/1 No No
157 CCA nomadic 0/1 No No
158 CSTA By-pass 500/ 1000/ 1500/ .../ 9500/ No Yes

9999 (099999 as of R8.0)
the maximum depends on
the OXE release.
159 – Not used — —
160 CCemail Agents 0/5/10/.../1000 No No
161 CCoutbound Agents 0/5/10/.../1000 No No
162 CCoutpredial Agents 0/5/10/.../1000 No No
163 – Not used — —
164 CSTA Record networked 0/5/10/.../600 No Yes

Chapter 20 Licenses

ber quired
165 OmniPCX Enterprise re- 30 = R5.0 LX No No

lease
31 = R5.1
32 = R6.0
33 = R6.1
34 = R6.2
35 = R7.0
36 = R7.1
37 = R8.0
38 = R9.0
39 = R9.1
40 = R10.0
41 = R10.1
42 = R11.0
43 = R11.1
44 = R11.2
45 = R12.0
166 4980 multi device 5/10/20/.../3000 No Yes

(= lock 129)
167 ACR data base read 0/ 1 No No
168 No. of HPOV node 0/ 1/ 2/.../ 100 No No
169 Voice detection channels 0/ 1/ 2/.../ 600 No No
170 – Not used — —
171 – Not used — —
172 – Not used — —
173 Business Users 0 / 1 / 2 / ... / 15000 Yes No
174 Analog Users 0 / 1 / 2 / ... / 5000 Yes No
175 Mobile Users 0 / 1 / 2 / ... / 5000 Yes No
176 Business IP Users 0/ 10/ 20/.../ 5000 (15000 as Yes No

of R8.0)
177 SIP Registered Users 0/ 10/ 20/.../ 5000 Yes Yes

Chapter 20 Licenses

ber quired
178 4645 : Voice mail engine 0/ 1/ 2/ 3 No According to

conditions, see:
Note 2 on page
420
179 4645 users 0/ 50/ 80/ 150/ 350/ 500/ Yes According to
1000 (15000 as of R8.0) conditions, see:
Note 3 on page
420
180 – Not used — —
181 OmniPCX Enterprise 1 = OmniPCX Enterprise No No
182 4645 : networking 0/ 1 No According to

conditions, see:
Note 3 on page
420
183 4645 : additional lan- 0/ 1/ 2/.../ 7 No According to

guage conditions, see:
Note 3 on page
420
184 Integrated Gatekeeper 0/ 1 No Yes
185 SIP Gateway 0/ 1 No Yes
186 E-CS redundancy 0/ 1 No Yes
187 H.323 (G711) network link 0/ 1/ 2/.../ 1000 No According to

conditions, see:
Note 5 on page
420
188 SIP networking links 0 / 1 / 2 / ... / Max1 No According to

conditions, see:
OXE > or equal to R7.1 :
Note 5 on page
Max1= 2500
420
OXE = R7.0 : Max1= 900
Other releases: Max1= 360
189 CCTI agents 0/ 5/ 10/.../ 1000 No No
190 RSI call center agents 0/ 5/ 10/.../ 2000 No Yes
191 Campus DECT 0/ 1 No No
192 T2 D_REX protocol 0/ 1 No No

Chapter 20 Licenses

ber quired
193 Embedded voice guides 0/ 1 No Yes
194 4645 My Messaging 0/ 10/ 20/.../ 1000 No According to

users conditions, see:
Note 3 on page
420
195 CCD profile 0 = None No Yes

1 = Starter
2 = Server
(according to lock 076)
196 RSI Business agents 0/ 5/ 10/.../ 5000 No Yes
197 G729A Client 0/ 10/ 20/.../ 4000 Yes No
198 — Not Used — —
199 Version 4400–R5.0 Ux 0/ 1 No No
200 4400 Mobiles migration 0/ 1/ 2/... /5000 No No
201 4400 Reflexes migration 0/ 1/ 2/... / 5000 No No
202 4400 Analogs migration 0/ 1/ 2/... / 5000 No No
203 Upgrade CCS ligth to 0/ 1/ 2/ .../ 60 NO No

CCS monosite
< or = lock 112
204 - - Not used — -

212
213 E–CS engine physical 0 / 50 / 80 / 150 / 350 / 500 / No No-

users 1000 / 1500 / ... / 9500 /
9999 (099999 as of R8.0)
214 - - Not used — -

299
300 swk file edition 0 No No
301 4400 hard key 1 0 No No
302 4400 hard key 2 0 No No
303 ACK 1 0 No No
304 ACK 2 0 No No

Chapter 20 Licenses

ber quired
305 ACK 3 0 No No
306 ACK 4 0 No No
307 ACK 5 0 No No
308 Remote extension (GSM 0/ 5/ 10/ 15/ 20/.../ 5000 No Yes

interworking)
309 XML telephony 0/ 10/ 20/.../ 3000 No Yes
310 CLIP Z 0/ 10/ 20/.../ 5000 Yes No
311 ACR networking 0/ 1 No No
312 Scripting agents 0/ 5/ 10/.../ 1000 No No
313 ECC platform 0/1/ 2/ 3 No No
314 4635 : My Messaging 0/ 10/ 20/.../ 5000 No According to

users conditions, see:
Note 3 on page
420
315 Hard 0223 Key migration 0/ 1 No Yes
316 Standard UP 4019(with 0/ 10/ 20/30.../ 5000 Yes No

services restriction)
317 Standard IP 4008/4018 0/ 10/ 20/.../ 5000 (15000 as Yes According to

(with services restriction) of R8.0) conditions, see:
Note 5 on page
420
318 Max number of connec- 0/ 1/ 2/... No No

tions to applications serv-
er (PRS)
319 EasyContact 0 = None No No

1 = EasyContact
320 – Not used — —
321 Mobile IP-Touch 0/ 10/ 20/ .../ 100 (OXE No No

R6.1)
0/ 10/ 20/ .../ 500 (OXE
R6.2)

Chapter 20 Licenses

ber quired
322 CSTA Beyond 9999 in- 0/1 No No

stances (099999 instan-
ces as of R8.0)
323 Executive UA Users (Al- 0/ 10/ 20/ .../ 5000 No No

catel Reflexes and Alca-
tel-Lucent 9 series sets)
324 Executive IP Users (Alca- 0/ 10/ 20/ .../ 5000 (15000 as No No

tel-Lucent 8 series and e- of R8.0)
Reflexes sets)
325 IP-Touch Security Engine 0/ 1 No No
326 Secured IP-Touch 0/ 10/ 20/ .../ 5000 Yes No

Phones (Alcatel-Lucent 8
series sets)
327 IP-Touch Security MCM 0/ 1/ 2/ .../ 120 Yes No
328 IP-SoftPhone Attendant 0/ 1/ 2/ .../ 50 Yes No
329 IP-SoftPhone Agent 0/ 10/ 20/ .../ 5000 Yes No
330 Advanced Mobile IP- 0/ 1/ 2 .../ 5000 (15000 as of Yes No

Touch R8.0)
331 MyPhone IP Desktop 0 / 1 / 2 /... / 5000 Yes No
332 PCS Max Numbers 1/2/ …/240 Yes No
333 CPU-ID (25 characters) 0/1 — —
334 CSTA Recording B chan- 0/5/10/15 ...(max = 2400 (up No No

nel over IP (DR-LINK) to R11.2) or 8000 (as of
R11.2))
335 Number of Greeting As- 0/ 1/ 2/ 3 (max = 3) Yes Yes

sistant
336 Number of stations with 0/ 1/ 2/ 3/ 4../ 15000 No No

IME
337 SIP External Voice Mail 0/ 1 Yes No
338 Migration ELA users to 0 / 1 / 2 / ... / Max = 5 000 — —

eZ32 users
339 Migration ELN users to 0 / 1 / 2 / ... / Max = 5 000 — —

eUA32 users

Chapter 20 Licenses

ber quired
340 Encryption server IP 0 / 500 / 1000 / ... / Max = 15 — —

users 000
341 BiCS release 0 = None — —

1 = BiCS-R1.0
2 = BiCS-R1.1
3 = BiCS-R2.0
4 = BiCS-R2.1
5 = BiCS-R2.2
6 = BiCS-R2.3
342 Number of ABC-IP trunk 0..240 Yes No

group accesses
343 Number of secured media 0..240 Yes No

gateway
344 – Not used — —
345 SIP integrated users 0..5000 Yes No
346 Max voice agents that 0 / 1 / 2 / ... / Max = 150 — —

can be migrated–
347 Max e-mail agents that 0 / 1 / 2 / ... / Max = 150 — —

can be migrated–
348 Soft MSM 0..240 Yes No
349 FUSION: IP CENTRALI- 0/1 — —

zATION
350 OTCC-PE/ GCE: RSI 0 / 155 — —

CALL CENTER
351 eLP Stand Alone Sys- 0/1 — —

tems
352 CCIVR RELEASE 0/1/2/3/4 — —
353 ROYALTIES CCIVR NMS 0 / 1 / 2 / ... / 256 — —

SIP
354 Number of merged OXO 0 / 1 / 2 / ... / n — —

Connect lines
355 Full/Essential Pg offer 0/1/2 — —

Chapter 20 Licenses

ber quired
356 Migration from OmniPCX 0/1 — —

Enterprise to BiCS
357 Users 8622 My Cellular 0 / 1 / 2 / ... / 5000 — —

Extension
358 SIP encryption users 0 / 1 / 2 / ... / 5000 — —
359 SIP encryption trunks 0 / 1 / 2 / ... / 5000 — —
360 Migration 4400 to BiCS 0/1 — —
361 RED-HAT 0 / 1 / 2 / … / 200 — —
362 RED-HAT-CLUSTER 0 / 1 / 2 / … / 200 — —
363 NOE/SIP encryption 0 / 1 / 2 / … / 2000 — —

users
364 4059EE 0 / 1 / 2 / ... / 50 — —
365 SIP BYPASS ICS ICM 0 / 1 / 2 / ... / 1500 — —
366 RELEASE OpenTouch 0 = None — —

Business Edition
1 = OTBE-R1.0
2 = OTBE-R1.1
3 = OTBE-R1.2
5 = OTBE-R1.3
367 RELEASE OpenTouch 0 = None — —

Multimedia Services
1 = OTMS-R1.0
2 = OTMS-R1.1
3 = OTMS-R1.2
5 = OTMS-R1.3
368 Migration from OmniPCX 0/1 — —

Enterprise to OpenTouch
Business Edition
369 Migration from BiCS to 0/1 — —

OpenTouch Business Edi-
tion
370 INTERACTIVE WHITE- 0 / 1 / 2 / ... / 2000 — —

BOARD

Chapter 20 Licenses

ber quired
371 MOBILE IPDECT USERS 0 / 1 / 2 / 1500 — —
372 OpenTouch Business Edi- 0 / 1 / … / 1500 — —

tion number of migrated
standard users
373 OpenTouch Business Edi- 0 / 1 / … / 1500 — —

tion number of standard
users
374 OTBE / OTMS Desktop 0 /1/……/1500 — —
375 OTBE / OTMS Mobiles 0 /1/……/1500 — —
376 Packages OmniTouch 0 /1/……/150 — —

SBC
377 OpenTouch users 0 /1/……/1500 — —
378 Free Licenses Converter: 0 /1/……/1500 — —

no. of abandoned UA li-
censes

no. of abandoned Z licen-
ses

no. of abandoned IP li-
censes

no. of retrieved IP licen-
ses

no. of retrieved Open-
Touch user licenses
383 – Not used — —
384 No. of OXE Media Serv- 0/1/…/240 No

ers
385 VoIP channels on OMS 0/1/…/28800 (240 x120) No

Chapter 20 Licenses

ber quired
386 UCaaSconfiguration 0/1 No Yes

0 = common configuration
1 = UCaaS configuration
See: Configuring CSTA/
TSAPI parameters (UCaaS
configuration) on page 388
387 Migration from BiCS to 0 or 1 — —

virtualized OmniPCX En-
terprise
388 Free Licenses Converter : 0 /1/……/1500 — —

retrieved OpenTouch
Desktop Users
389 OTBE : STD User Cellu- 0 /1/……/1500 — —

lar
390 Migr. BiCS -> OpenTouch 0 or 1 — —

Suite for MLE
391 to Not used — —

395
396 IP-V6 0 or 1 — —

405
406 OT gateways allowed 0 or 1

463
464 SOSM Feature 0 — —

1 = Russia
2884 = United Arab Emi-
rates
465 to – Not used — —

466
467 ARS 0/ 50/ 80/ 150/ 350/ 500/ No No

1000/ 1500/ .../ 9500/ 9999
(15000 as of R8.0)
from 0)

Chapter 20 Licenses

ber quired
468 – Not used — —
469 G723.1 Server 0/n No No
470 - Reserved “Open” lock — —

866
20.6.1.1 Note 1
The Hotel option is validated if the value of one of the following locks is different from 0:
• Lock 004: Hotel Guest set
• Lock 038: Infocenter link
When new OPS files (containing these locks) are installed and these files validate the Hotel option, a
reboot is required.
When the Hotel option has already been validated, a reboot is not required when new OPS files
increase these locks.
20.6.1.2 Note 2
The ABCA option is validated if the value of one of the following locks is different from 0:
• Lock 044: 4059 SBC
• Lock 045: 4059 BLF
• Lock 086: Automatic directory pop up
• Lock 178: 4645 Voice mail engine
The ABCA option is also validated if the value of one of the following parameters of the hardware.mao
file is different from 0:
• Nb of BLF
• SBC
• 4635x
• 4630
• 4855
When new OPS files (containing these locks) are installed and these files validate the ABCA option, a
reboot is required.
When the ABCA option has already been validated, a reboot is not required when new OPS files
increase these locks.
20.6.1.3 Note 3
Locks 46, 52, 56, 57, 58, 59, 60, 61, 62, 63, 65, 66, 107, 108, 109, 110, 151, 179, 182, 183, 194, 314:
These parameters can be increased without reboot, provided the ABCA option is enabled.
20.6.1.4 Note 4
Lock 83: this parameter can be increased without reboot only when accounting is started.
20.6.1.5 Note 5
Lock 187, 188, 317: These parameters can be increased without reboot provided compression was
used before the new SWK file installation.

Chapter
21 List of user profiles
21.1 Overview
User profiles allow a customer to purchase the communication services appropriate to a category of
users, as opposed to trying to adjust features across departments, business units or individual users.
For more information about user profiles, see module Detailed description.

21.2.1 User profiles description
As of R8.0, user profiles provide a new method to define the right communication needs for different
classes of users. This new method is based on the requirements of the job, not on title, department or
business unit. User profiles categorize enterprise users, define their communication needs and match
corresponding services and handsets with each user category.
This new method is integrated into ACTIS configuration tool and it should ease setting the right quantity
of licenses according to each class of users. On the OmniPCX Enterprise side, you keep the standard
way of configuration.
Categorizing enterprise users results in 5 user profiles:
• office workers: working mostly at their desks
• team workers: characterized by strong collaboration needs
• on-site roamers: mainly mobile on-site
• mobile professionals: mainly mobile off-site
• executives
Each of the above user profiles is based on bundles of services combining:
• telephony services
• mobile communication solutions, on-sit and off-site
• applications
• collaboration options (audio or data conferencing, video)
• messaging (voice mail, integrated or Unified Messaging)
User profiles are further classified into three subcategories based on the usage intensity of
communication services:
• low usage: Essential
• moderate usage: Premium
• intensive usage: Privilege
For more information on user profiles, see Types of user profiles on page 422
The following table presents the communication requirement matrix of user profiles:

Chapter 21 List of user profiles
Time at Time away Time away Team work-

User profiles Usage
desk from desk from office ing
> 90% < 10% — — low
Office worker > 90% < 10% — — moderate
> 90% < 10% — — intensive
> 70% < 30% — Yes low
Team worker > 70% < 30% — Yes moderate
> 70% < 30% — Yes intensive
< 20% > 80% — — low
On-site roamer = 50% = 50% — — moderate
= 50% = 50% — — intensive
< 40% — > 60% Yes low
Mobile professional < 40% — > 60% Yes moderate
< 40% — > 60% Yes intensive
Executive = 40% = 30% = 30% Yes intensive
21.2.2 Types of user profiles

21.2.2.1 Office worker
Office workers spend 90% of their working time at their desks in their offices. Examples of this user
profile are: administrative assistants, office managers, legal managers, accountants, Web site
administrators, market research managers, sale operation professionals, Web content editors and
purchasing professionals.
Office workers are classified into three subcategories.
21.2.2.1.1 Office worker essential
This user profile is characterized by a moderate telephony usage. Users in this subcategory basically
need a standard license together with an entry phone and voice mail. The phone choice depends on
the number of Ethernet ports needed on the phone.
Phone handsets associated with this user profile are:
• Alcatel-Lucent IP Touch 4008 Phone
• Alcatel-Lucent IP Touch 4018 Phone
• Alcatel-Lucent 4019 Digital Phone
For more information about services and phone handsets associated with this user profile, see List of
user profiles on page 426.

21.2.2.1.2 Office worker premium

This user profile is characterized by an intensive telephony usage. Users in this subcategory are
provided with a higher level of services:
• call by name
• hands free
• multi-line features
• boss/secretary features
• voice mail
Graphical display and navigator keys offer an intuitive access to advanced telephony features such as
call log.
• 8028/8038/8068, 8028s/8058s/8068s/8078s
• 8029/8039
21.2.2.1.3 Office worker privilege
This user profile is characterized by the most intensive telephony usage. Users in this subcategory
benefit from:
• SIP services
• multimedia interaction based on multiple sessions such as voice, IM or video
My Instant Communicator extends the scope of multimedia communication to real-time multimedia
communication. It transforms telephony into real time multimedia/multi-session collaboration.
• 8028/8038/8068, 8028s/8058s/8068s/8078s
• 8029/8039
21.2.2.2 Team worker

Team workers spend roughly 70% of their time at their desks and 30% away from their desks. They
have growing need to coordinate with cross functional teams. Examples of this user Profile are: project
managers, team workers, legal advisors, project financial analysts, information system managers,
strategic marketing managers and sale administration managers.
Team workers are classified into three subcategories.
21.2.2.2.1 Team worker essential
This user profile gets the essential telephony and conferencing capabilities:
• access to OmniPCX Enterprise telephony feature
• voice mail
• audio conferencing
• Alcatel-Lucent IP Touch 4018 phone Extended Edition
21.2.2.2.2 Team worker premium
This user profile gets advanced telephony and conference capabilities:
• Call by name
• Hands free
• Boss/secretary features

• Voice mail
• Audio conferencing for wide range of business activities across multiple departments
Users in this subcategory have access to conferencing capabilities through a variety of devices
including PCs, TDM and IP phones and mobile devices such as cell phones and PDAs.
• 8028 Premium DeskPhone/8028s Premium DeskPhone
• 8038 Premium DeskPhone
• 8029/8039
21.2.2.2.3 Team Worker privilege
This user profile is characterized by having the most intensive collaboration usage. Users in this
subcategory need more than telephony/audio collaboration. Their collaboration capabilities must
include data conferencing.
My Instant Communicator extends the scope of multimedia communication to real-time multimedia
communication. It transforms telephony into real-time multimedia/multi-session collaboration.
• 8028/8038/8068, 8028s/8058s/8068s/8078s
• 8029/8039
21.2.2.3 On-site roamer

On-site roamers are users mainly mobile on site. They may be away from their desks inside the
campus 50% of their working time, spending the rest in a shared office. Examples of this user profile
are: service and security agents, nurses and facilities managers.
New professional campus mobile handsets are introduced:
• Alcatel-Lucent OmniTouch 8118 WLAN Handset
On-site roamers are classified into three subcategories.
21.2.2.3.1 On-site roamer essential
This user profile is adapted to the most mobile on-site roamers. Users in this subcategory have the
following services:
• Call by name
• Multi-line features
• Voice mail
The multi-line capability is an important security feature. For example, a security guard or a nurse can
receive several emergency calls while in conversation on another line.
• Alcatel-Lucent OmniTouch 8118/8128 WLAN Handsets
21.2.2.3.2 On-site roamer premium
This user profile integrates the multi-line capability adapted to mobile users with a very high traffic. It is
also adapted to assistants that may continue to filter calls on the move.
The multi-line capability is an important security feature. For example, a security guard or a nurse can
receive several emergency calls while in conversation on another line.


21.2.2.3.3 On-site roamer privilege
This user profile includes the richest features of on-site mobile handsets (DECT or WLAN).
For communication between intensive users such as assistants, an advanced desk phone is bundled
together with a PC access to real-time communication and voice mail.
• 8028/8038/8068, 8028s/8058s/8068s/8078s
• 8029/8039
21.2.2.4 Mobile professional

Mobile professionals spend 40 to 60% of their working time away from their offices. Their main
communication device is their off-site mobile phone. Examples of this user profile are: sale managers,
consultants and channel marketing managers.
Advanced Cellular Extension (ACE) is the core building block of this user profile. ACE improves
personal productivity with a mobile access to IP PBX features such as one number, one touch access
to voice mail, transfer, conference and call back.
Mobile professionals are classified into three subcategories.
21.2.2.4.1 Mobile professional essential
This user profile is characterized by an access to OmniPCX Enterprise telephony and voice mail
features from both fixed and cell phone handsets. An example is the access from a cell phone to
features such as automatic call back that gives the possibility to a remote user to be called back by the
person she/he needs to reach.
Interesting features included in this user profile are:
• three party conference
• one number (tandem feature)
• Alcatel-Lucent IP Touch 4018 phone Extended Edition
• Advanced Cellular Extension
21.2.2.4.2 Mobile professional premium
Users in this subcategory may spend slightly more time at their offices and therefore require more
advanced phone handsets. Even though they are not regular conferencing users, they may access
conference bridges if the service is available.
• 8029/8039
21.2.2.4.3 Mobile professional privilege
This user profile is characterized by:
• an access to the OmniPCX Enterprise telephony features
• an access to real-time Collaboration

My Instant Communicator provides users in this subcategory with:

• a Web based access to telephony, UDA, call log, and IM
• PC voice mail access
• extended PC or cell phone access to the enterprise network
• PC, cell phone or fixed phone access to voice mail access to the filtering capabilities of Unified
Communication My Assistant
• 8028/8038/8068, 8028s/8058s/8068s/8078s
• 8029/8039
21.2.2.5 Executives
Executives spend roughly 40% of their working time at their desks, 30% inside their enterprise and
30% outside.
They need immediate access to any type of collaboration with their teams and they have intensive
communication needs.
This user profile provides the richest combination of telephony, messaging, collaboration and mobility.
Users in this subcategory benefit from end-to-end multimedia, multi-session collaboration.
• 8028/8038/8068, 8028s/8058s/8068s/8078s
• 8029/8039
21.3 List of user profiles

21.3.1 ALE International list of user profiles
The following two tables define the right communication services for different classes of users based on
job requirements.
User profiles
Communication services Office Office Office Team Team Team

worker worker worker worker worker worker
essential premium privilege essential premium privilege
OXE user licenses
IP standard license Yes Yes
IP multi-line license (Busi-

Yes Yes Yes Yes
ness)
UA standard license Yes Yes
UA multi-line license (Busi-

Yes Yes Yes Yes
ness)

User profiles

Alcatel-Lucent 4980 Soft-

phone
DECT license
WLAN handsets license
Voice mail service
Voice mail 4635J/H Yes Yes Yes Yes Yes Yes
Integrated Mes. or Unified

Yes Yes
Mes.
OXE telephony features
Boss/Secretary Yes Yes Yes Yes
Multi-line Appearence Yes Yes Yes Yes
Call-by-Name OXE Yes Yes Yes Yes
OTUC services
Web soft phone Yes Yes
Universal Directory Yes Yes
Call Log Yes Yes
Tel./IM Presence Yes Yes
Instant Messaging Yes Yes
My Assistant Yes Yes
Mobility services
Remote extention (ACE)
Dual Mode
Video communication
Video Peer-to-Peer Yes

User profiles

Conferencing
Audio Multi-party Conferenc-

Yes Yes Yes
ing (My TW)
Data Multi-party Conferenc-

Yes
ing (My TW)
User profiles
Communication On-site On-site On-site

Mobile Mobile Mobile
services roamer roamer roamer
prof. es- prof. pre- prof. Executive
essen- premi- privi-
sential mium privilege
tial um lege
OXE user licenses
IP standard license Yes
IP multi-line license
Yes Yes Yes Yes
(Business)
UA standard license Yes
UA multi-line license
Yes Yes Yes Yes
(Business)
Alcatel-Lucent 4980
Yes
Softphone
DECT license Yes Yes Yes
WLAN handsets li-

Yes Yes Yes
cense
Voice mail service
Voice mail 4635J/H Yes Yes Yes Yes Yes Yes Yes
Integrated Mes. or
Yes Yes Yes
Unified Mes.
OXE telephony features
Boss/Secretary Yes Yes Yes Yes

User profiles
Communication On-site On-site On-site

Mobile Mobile Mobile
services roamer roamer roamer
prof. es- prof. pre- prof. Executive
essen- premi- privi-
sential mium privilege
tial um lege
Multi-line Appear-
Yes Yes Yes Yes
ence
Call-by-Name OXE Yes Yes Yes Yes Yes Yes
OTUC services
Web soft phone Yes Yes Yes Yes
Universal Directory Yes Yes Yes Yes
Call Log Yes Yes Yes Yes
Tel./IM Presence Yes Yes Yes Yes
Instant Messaging Yes Yes Yes Yes
My Assistant Yes Yes Yes Yes
Mobility services
Remote extention
Yes Yes Yes Yes
(ACE)
Dual Mode Yes Yes
Video communication
Video Peer-to-Peer Yes
Conferencing
Audio Multi-party
Conferencing (My Yes
TW)
Data Multi-party Con-

Yes
ferencing (My TW)
The following two tables list phone handsets appropriate for different classes of users based on job
requirements.

User profiles
Office
Phone handsets Office Office Team Team Team
worker
worker worker worker worker worker
essen-
premium privilege essential premium privilege
tial
IP Touch Serie 8
Alcatel-Lucent IP Touch
Yes Yes
4008 Phone
Yes Yes
4018 Phone
Yes Yes Yes Yes
4028 Phone
Yes Yes Yes Yes
4038 Phone
Yes Yes
4068 Phone
Bluetooth handset for Alcatel-

Lucent IP Touch 4068 Phone
IP Touch Serie 9
Alcatel-Lucent 4019 Digi-

Yes Yes
tal Phone

Yes Yes Yes Yes
tal Phone

Yes Yes Yes Yes
tal Phone
DECT set
Alcatel-Lucent 300 DECT

Handset set
Alcatel-Lucent 400 DECT

Handset set
WLAN handset
Alcatel-Lucent IP Touch 310

WLAN Handset
Alcatel-Lucent IP Touch 610

WLAN Handset

User profiles
Office
Phone handsets Office Office Team Team Team
worker
worker worker worker worker worker
essen-
premium privilege essential premium privilege
tial
Alcatel-Lucent OmniTouch
8118 WLAN Handset
Alcatel-Lucent OmniTouch
8128 WLAN Handset
User profiles
On-site On-site
Phone handsets On-site Mobile Mobile Mobile
roamer roamer Execu-
roamer prof. es- prof. prof.
essen- premi- tive
privilege sential premium privilege
tial um
IP Touch Serie 8
Alcatel-Lucent IP
Yes
Touch 4008 Phone
Alcatel-Lucent IP
Yes
Touch 4018 Phone
Alcatel-Lucent IP
Yes Yes Yes
Touch 4028 Phone
Alcatel-Lucent IP
Yes Yes Yes Yes
Touch 4038 Phone
Alcatel-Lucent IP
Yes Yes Yes
Touch 4068 Phone
Bluetooth handset for

Alcatel-Lucent IP Yes
Touch 4068 Phone
IP Touch Serie 9
Alcatel-Lucent 4019
Yes
Digital Phone
Alcatel-Lucent 4029
Yes Yes Yes
Digital Phone
Alcatel-Lucent 4039
Yes Yes Yes Yes
Digital Phone

User profiles
On-site On-site
Phone handsets On-site Mobile Mobile Mobile
roamer roamer Execu-
roamer prof. es- prof. prof.
essen- premi- tive
privilege sential premium privilege
tial um
DECT set
Alcatel-Lucent 300
Yes
DECT Handset set
Alcatel-Lucent 400
Yes Yes Yes
DECT Handset set
WLAN handset
Alcatel-Lucent IP
Touch 310 WLAN Yes
Handset
Alcatel-Lucent IP
Touch 610 WLAN Yes Yes Yes
Handset
Alcatel-Lucent Omni-
Touch 8118 WLAN Yes
Handset
Alcatel-Lucent Omni-
Touch 8128 WLAN Yes Yes Yes
Handset

Chapter
22 PCX synchronization
22.1 Overview
22.1.1 Overview
Synchronization is the mechanism which allows a PCX to adjust itself to a clock shared by all the public
or private PCXs to which it is connected.
The aim of synchronization is to avoid problems which may result from time differences between the
internal clocks of the different shelves of a node or the different nodes of a network: loss of information,
audible "crackle", incorrect transmission of fax or data, possible cut-off of calls, etc.

22.2.1 Outline of the Problem
Data transmission on B channels between two machines results in an uninterrupted flow of bits on the
link connecting them. The transmitting machine sends these bits at the speed determined by its internal
clock. The receiving machine extracts these bits at the speed set by its own clock.
If the clocks of the two machines are not exactly identical, one of the following occurs:
• If the reception clock is slower than the transmission clock, information is lost due to saturation at
reception.
• If the reception clock is faster than the transmission clock, there are sampling errors, because
sampling occurs before the expected bit arrives.
Receiving PCX
Transmitting PCX
Transmission
Line to the Recipient
Signals
Transmission Reception &

Sampling
Figure 22.1: Principle of Data Transmission on a B Channel
If the clocks are different, there is:

• Audible "crackle" if the message transmitted is voice
• A degraded image if the message transmitted is a fax
• A lower useful rate if the message transmitted is a data transmission
• Possible call cut-off.
The error rate depends on the difference between the clocks.
22.2.2 Solution Adopted for Synchronous Transmission

For the transmission clock to be exactly the same as the reception clock, one machine is declared as
clock master and the other machines must align themselves with it. The slave machine extracts the

Chapter 22 PCX synchronization
clock link and its clock is slaved to this external source. There is then no transmission loss due to clock
differences.
This is referred to as PCX synchronization with an external source. Note that this synchronization is
only a frequency synchronization. Because of transmission delay due to cable length, phase
synchronization is not performed.
The public network is the best clock and should be used whenever possible. It can be either used
directly when connected to the public network, or used indirectly when connected to a network that is
itself synchronized with the public network.
22.2.3 External Synchronization Sources

The external synchronization sources can be the trunk groups (public or private) and the links. The
types of interface that can transport the synchronization are given in the following table.
table 22.1: Types of Interface which Transport the Synchronization
Interface Restriction
T2, T1, T0 Do not use a T0 as a main synchronization source if it is not permanent.
ATM The ATM access must itself be synchronized with the public network.
PCM
Restriction:
The GD/GD2 or GD-3 board must be synchronized with one (or several) T0, T2 or T1 interface located
in the main rack.
22.2.4 Internal Synchronization Sources

The boards which can provide an internal synchronization source are given in the following table.
Board type Comment
SYNC Provides a clock with a precision of 1PPM.
GD, INT-IP B, CPU These boards generate an internal free running clock, used when the exter-
nal sources or the other internal sources are missing or faulty.
RT2, LIOB These boards generate an internal free running clock, local to the remote
ACT (synchronization by domains), used when the inter-ACT link does not
transport the clock and when the external sources or the other internal sour-
ces are missing or faulty.
22.2.5 Transporting the Synchronization on Links between Shelves

The inter-shelf links that transport the synchronization are given in the following table.
6 "Part Per Million", or a precision of 10 to the power of -6

Type of Link Direction Restriction
HSL links From the main rack to the extension racks The synchronizing coupler must
be in the main rack.
(between main and
secondary rack)
INTOF type inter- Either from the main ACT to the peripheral
ACT links ACT, or vice versa.
RT2 type inter-ACT Either from the main ACT to the remote The link must be set up perma-
links ACT, or vice versa. nently, and not just during the
calls.
Remote LIO type in- Either from the main ACT to the remote The link must be an S0/FV type
ter-ACT links ACT, or vice versa. link.
The inter-shelf links that do not transport the synchronization are given in the following table.
Type of Link Comment
IP link Synchronization is never transported through IP links.
RT2 type inter-ACT For transit through a network for which the quality is not certain. This occurs,
links for example, if the RT2 link uses a multiplexer that only transmits the clock
during a call.
Remote LIO type in- Transfix and Frame Relay type link.
ter-ACT links
22.2.6 Synchronization Domains

A synchronization domain is a set of shelves (ACT or S or L racks) which synchronize on the same
source (external or internal). Conventionally, a synchronization domain is identified by the number of
the ACT or the main rack in the domain.
Inside a synchronization domain, the synchronization is transported by the inter-shelf links. Once an
inter-shelf link is unable to transport the synchronization, a separate synchronization domain must be
created. Each domain has its own synchronization (either from an external trunk group, or through the
internal clock of a board) and this synchronization remains local to the domain.
By default (before any configuration), there is just one domain, called the global synchronization
domain (or default synchronization domain).
The global synchronization domain always contains the Com Server (and the ACT 0 if there is one). It
is also called domain 0.
The global synchronization domain must contain:
• The main ACT and the peripheral ACTs on INTOF (if necessary RT2) in a configuration with IP
Crystal Server
• The Com Server in the configurations with IP Rack Server or IP Appliance Server
• The Media Gateways which do not have synchronizing access: these are free running, and it is the
INT-IP B and GD boards which provide the synchronization.

An OmniPCX Media Gateway with a synchronizing access must belong to a separate synchronization
domain. The extension racks, connected by HSL link to the main rack, must belong to the same
domain as the main rack.
An ACT Media Gateway with a synchronizing access must belong to a separate synchronization
domain.
Note:
In a synchronizing domain, you can create a maximum of six accesses per Media Gateway.
22.2.7 Synchronization Priority

Each potentially synchronizing access (or board) is assigned a synchronization priority (between 0 and
255).
The system synchronizes itself with the highest priority access (which is the smallest priority number,
for example 200 has a higher priority than 201). If this access is not available, the system falls back on
an access with the same priority or the next highest priority level.
If no external access is available, the system switches to free running mode, that is, uses the internal
clock of a potentially synchronizing board (GD, CPU, SYNC, etc.).
The synchronization priorities are also used to create the synchronization domains. The
synchronization domains are not configured as such on the PCX. It is the creation of an access with a
synchronization priority of between 200 and 254 which leads to the creation of a domain. The domain
created in this way contains the shelf on which the access is found as well as the shelves which
depend on it (extension racks or peripheral ACTs).
In summary, the priority values are assigned as follows:
• Between 0 and 199 for the global synchronization domain. Level 0 is the highest priority.
• Between 200 and 254 for the other synchronization domains
• 255 for a non-synchronizing access or board.
22.2.8 Interaction between DECT/PWT and Synchronization

The DECT/PWT (mobile telephony) requires a clock accurate to at least 5 PPM. For more information,
refer to the the document [9] for DECT and document [15] for PWT.
Note:
The HSL link does not comply with DECT/PWT synchronization.
22.3 Engineering rules

22.3.1 Synchronization within a Private Network
22.3.1.1 Constraints
In a network with several PCXs, the private trunk groups and links can be used to send the
synchronization.
Whenever possible, the network driver clock should be the public network clock. Using synchronization
priorities, the system administrator configures the clock transmission route on each node. The system
administrator also configures fallback solutions to be used in the event of a fault.

Public Network
T2-1 T2-2 T2-3
Sy=0 Sy=0 Sy=0

Art1-2
Node 1 Node 2
Sy=255
Sy=1
Sy=255 Sy=255
Art1-3 Art2-3
Sy=1 Sy=2
Node 3
Sy=255
Art3-4
Sy=3
Node 4 Sy=255 Non Synchronizing Link
Figure 22.2: Example of Private Network Synchronization
As shown in the above figure, the system administrator will favor:

• Public network accesses
• Links to PCXs with the greatest number of public network accesses.
Note:
If a PCX connects to several carriers, this is not a problem as carriers are synchronized with each other.
22.3.1.2 Malfunctions
The system administrator must imperatively avoid synchronization loops.
In the figure below, PCX1 is synchronized on PCX2, which is synchronized on PCX3. PCX3 then is
synchronized on PCX1.
Sy=0
Node 1 Node 2
Sy=0
Sy=0
Node 3
Figure 22.3: Synchronization Loop
A situation such as that shown in the figure above (or an equivalent situation) causes not only
malfunction of inter-PCX links, but also internal malfunctions on each machine.
The system administrator must avoid this type of situation, not only for nominal operation, but also for
fallback solutions.
22.3.1.3 Priority Definition Method

This method offers the following advantages:
• It distributes synchronization to all the nodes of the network.

• It avoids synchronization loops.

However, not all fallback possibilities can be used with this method.
The general principles of this method are:
• Public network accesses take priority, and all have the priority 0.
• The inter-PCX links are only used (for synchronization) in one direction.
• On inter-PCX links, the synchronization priority depends on the number of the source node.
Public Network
T2-1 T2-2 T2-3
Sy=0 Sy=0 Sy=0

Sy=10
PCX 1 PCX 2
Sy=255 Sy=255 Sy=255
Sy=255
Sy=20
Sy=10
Sy=20
Sy=40
PCX 3 PCX 4 PCX 6
Sy=255 Sy=30 Sy=255
Sy=255
Sy=30
PCX 5
Figure 22.4: Example of Synchronization
In the example above, a synchronization priority of 10 times the node number has been selected.
22.3.2 Synchronization within a Node

22.3.2.1 General Rules
• In a multi-ACT configuration, the external synchronization links can be located on the level 1 ACT
(main ACT) or on a level 2 ACT, but not on a level 3 ACT.

E1 Synchronization Possible
Main ACT ACT0 (recommended)
INTOF Inter ACT Link
E1 Synchronization Possible
ACT1
Peripheral ACT Level 2
INTOF Inter ACT Link
E1 Synchronization Impossible
Peripheral ACT Level 3 ACT2
Figure 22.5: Example of Synchronization with Three ACT Levels

• In an OmniPCX Media Gateway, the synchronizing coupler must be in the main rack.
• Synchronization on a T2/T1 link must have priority over T0 links.
• Synchronization on a public link must have priority over private links (with other nodes).
• When an inter-shelf link does not transport the synchronization, a synchronization domain must be
created: for example, for RT2 type ACTs behind a MUX.
• An OmniPCX Media Gateway without a synchronizing board belongs to the global synchronization
domain 0. It is free running, without operating restrictions.
22.3.2.2 Configuration with IP Crystal Server

22.3.2.2.1 Example One
Using the following system:
• One CPU board in ACT 0
• Two peripheral ACTs (ACT 1 and ACT 2) connected to ACT 0 using INTOF links
• A digital access to the public network on ACT 0
• A private digital access on both ACTs 1 and 2.
The INTOF links transport the synchronization. All ACTs should therefore belong to the global
synchronization domain. The priority levels are configured so as to synchronize the system on the
public access, then on the private accesses.
Do the following:
1. Configure the public access of ACT 0 with the priority 0.
2. Configure the private accesses on ACTs 1 and 2 with the priorities 1 and 2.

Domain 0
CPU
Public Access
ACT 0 Priority=0
ACT 2
Private Access
Priority=2
ACT 1
Private Access
Priority=1
Figure 22.6: Example of Multi-ACT Configuration with INTOF Links
22.3.2.2.2 Example Two

• One peripheral ACT (ACT 1) connected to ACT 0 using INTOF links
• One remote ACT (ACT 2) connected to ACT 0 using RT2 links behind MUX
• A digital access on ACT 0
• A digital access on ACT 2.
The INTOF links transport the synchronization. ACTs 0 and 1 should therefore belong to the global
synchronization domain. The RT2 link behind MUX does not transport the synchronization. ACT 2
should therefore belong to a different domain.
Do the following:
1. Configure the digital access of ACT 0 with the priority 0.
2. Configure the digital access of ACT 2 with the priority 200. This leads to the creation of domain 2, to
which this single ACT 2 belongs.

Domain 0
CPU
Digital
Access Main ACT 0
Priority=0
Leased RT2
INTOF Lines
External Network
Peripheral
ACT 1 Digital
Access
Priority=200
Domain 2
Remote ACT 2
Figure 22.7: Example of Multi-ACT Configuration with INTOF and RT2 Links
22.3.2.3 Configuration with IP Crystal Server + OmniPCX Media Gateway

• One OmniPCX Media Gateway consisting of two racks (6 and 7)
• A private digital access on both ACTs 1 and 2
• A digital access on rack 6.
The INTOF links transport the synchronization, therefore ACTs 0, 1, and 2 should belong to the global
synchronization domain. The IP network does not transport the synchronization, therefore the
OmniPCX Media Gateway (racks 6 and 7) should belong to a separate domain.
Do the following:
1. Configure the public access of ACT 0 with the priority 0.
2. Configure the private accesses on ACTs 1 and 2 with priorities 1 and 2.
3. Configure the digital access of the OmniPCX Media Gateway with the priority 200. This leads to the
creation of domain 6, to which racks 6 and 7 belong.

IP
CPU
Public Access GD Main Rack 6
Main ACT 0
Priority=0 Digital Access HSL
Priority 200
MEX
INTOF
INTOF Secondary Rack 7
Private Access Domain 6
Priority=1
Peripheral ACT 1 Private Access

Priority=2
Peripheral ACT 2
Domain 0
Figure 22.8: Example with IP Crystal Server + OmniPCX Media Gateway
22.3.2.4 Configuration with IP Rack Server or IP Appliance Server + OmniPCX Media Gateway
• IP Appliance Server or IP Rack Server
• One OmniPCX Media Gateway consisting of two racks, 1 and 2, with a digital access on rack 1
• One OmniPCX Media Gateway consisting of two racks, 3 and 4, with a digital access on rack 3
• One OmniPCX Media Gateway consisting of two racks, 5 and 6, with no digital access.
Do the following:
1. Configure the digital access of rack 1 with the priority 200. This leads to the creation of domain 1, to
which racks 1 and 2 belong.
2. Configure the digital access of rack 3 with the priority 200. This leads to the creation of domain 3, to
which racks 3 and 4 belong.
3. Do not configure the synchronization priority on rack 5. There is no synchronizing access in rack 5,
so racks 5 and 6 belong to the global domain 0 and are free running, with no operating restrictions.

Domain 0
Com Server
GD Main Rack 5
IP HSL
MEX
Main
GD
Rack 1 Secondary Rack 6
Digital Access Main
HSL GD
Rack 3
Priority=200
Digital Access HSL
MEX
Priority=200
Secondary Rack 2
MEX
Domain 1
Secondary Rack 4
Domain 3
Figure 22.9: Example with IP Rack Server or IP Appliance Server + OmniPCX Media Gateway
22.3.2.5 Configuration with IP Rack Server or IP Appliance Server + OmniPCX Media Gateway +
ACT Media Gateway
• IP Appliance Server or IP Rack Server
• One OmniPCX Media Gateway consisting of two racks, 6 and 7
• A digital access on rack 6
• One ACT Media Gateway (3) with two digital accesses
• An ACT (4) connected to ACT 3 using an INTOF link, with a digital access
• An ACT (5) connected to ACT 3 using an RT2 link, with a digital access.
Initially, all ACTs and racks are in the global synchronization domain (domain 0).

Domain 0
Com Server
IP
Main Rack 6
GD
ACT 3
HSL
INTOF Leased RT2 MEX
Lines Secondary Rack 7
External Network
ACT 4
ACT 5
Figure 22.10: Initial Configuration
Taking into account the type of link between shelves, the domain configuration will be as follows:
• The INTOF link transports the clock: ACTs 3 and 4 are therefore reunited in the same domain
(domain 3).
• The RT2 link does not transport the clock: ACT 5 is therefore placed in a separate domain (domain
5).
• The HSL link transports the clock: racks 6 and 7 are therefore placed in the same domain (domain
6). This is a new domain as rack 6 contains a synchronizing access and the IP link between ACT 3
and rack 6 does not transport the clock.
Note:
If the Media Gateway does not contain a synchronizing access, it remains in the global synchronization domain
and operates in free running mode.
Do the following:
1. Assign racks 6 and 7 to a first synchronization domain (domain 6).
2. Assign ACTs 3 and 4 to a second synchronization domain (domain 3).
3. Assign ACT 5 to a third synchronization domain (domain 5).
1. Assign Racks 6 and 7 to a First Synchronization Domain (Domain 6)

• On rack 6, configure the digital access with the priority level 200
Creating a potentially synchronizing coupler E with the priority level 200 on rack 6 leads to the
creation of domain 6. Racks 6 and 7 are assigned to this domain.

Com Server
Domain 0 IP
GD Rack 6
ACT 3
E (200) HSL
INTOF Leased MEX
RT2 Rack 7
Lines
Domain 6
External Network
ACT 4
ACT 5
2. Assign ACTs 3, 4, and 5 to a Second Synchronization Domain (Domain 3)
• On ACT 3, configure the digital access with the priority level 200
As long as the user does not declare a synchronizing coupler on a peripheral ACT, the whole of
the installation belongs to the global synchronization domain (domain 0).
The declaration on ACT 3 of a first potentially synchronizing coupler (A) with the priority 200
leads to the creation of domain 3 containing ACT 3 and the ACTs connected to ACT 3.
Domain 0
Com Server
IP
A (200)
GD Rack 6
ACT 3
E (200) HSL
INTOF Leased MEX
RT2 Lines Rack 7
Domain 6
External Network
ACT 4
Domain 3
ACT 5

• On ACT 3, configure the digital access with the priority level 201
The declaration on ACT 3 of a second coupler (B) with the priority 201 does not lead to any
change in terms of the distribution of the domains.
Domain 0
Com Server
IP
A (200)
GD Rack 6
ACT 3
B (201) E (200) HSL
INTOF Leased MEX
RT2 Lines Rack 7
Domain 6
External Network
ACT 4
Domain 3
ACT 5
• On ACT 4, configure the digital access with the priority 203

If a coupler (C) with the priority 203 is declared on ACT 4, since the existing minimum priority for
domain 3 is lower than the priority entered for coupler C, ACT 4 remains in domain 3.
Domain 0
Com Server
IP
A (200)
GD Rack 6
ACT 3
B (201) E (200) HSL
INTOF Leased MEX
C (203) RT2 lines Rack 7
Domain 6
External network
ACT 4
Domain 3
ACT 5

3. Assign ACT 5 to a Third Synchronization Domain (Domain 5)

• On ACT 5, configure the digital access with the priority 200
If a coupler (D) with the priority 200 is declared on ACT 5, a new domain (domain 5) is created.
Domain 0
Com Server
IP
A (200)
GD Rack 6
ACT 3 HSL
B (201) E (200)
INTOF Leased MEX
C (203) RT2 Rack 7

Lines
Domain 6
ACT 4 External Network
Domain 3
ACT 5
D (200)
Domain 5
22.3.3 Migration of an OmniPCX 4400 to OmniPCX Enterprise with Appliance Server

22.3.3.1 Preliminary Remarks
During migration from an OmniPCX 4400 to an OmniPCX Enterprise with Appliance Server, the latter
takes the place of ACT 0 in the new database. The old ACT 0 is then moved to the first available ACT
position, called “ACT X” in this example.
The Appliance Server (ACT 0) sees ACT X (and if applicable, the ACTs which are connected to it) as
an ACT IP.
The ACT X which has become ACT IP is therefore subject to the rules of synchronization by domain.
The accesses synchronizing this ACT should have a synchronization priority of between 200 and 254
in order to create a new synchronization domain.
The MAO operations need to be carried out manually after the migration in order to modify the priorities
and return to correct operation.
The examples below allow, in most cases, the new synchronization rules to be applied.
22.3.3.2 Example One

Using the following system, before migration:
• A digital access in each ACT (0, 1, and 2)
• A synchronization priority set to 0 on the three accesses.

The operation is as follows:

• One of the three accesses synchronizes the three ACTs. The other two are potentially
synchronizing.
• If the synchronizing access fails, one of the other two accesses becomes synchronizing for the
three ACTs. If the access is restored, it becomes potentially synchronizing.
After migration with Appliance Server:
• CPU is replaced by an Appliance Server. An INT-IP2 is put in the place of the CPU.
• ACT 0 is moved to ACT 3 (first available ACT).
• ACT 3 is then an ACT IP. It must belong to a synchronization domain.
Do the following:
1. Configure the access for ACT 3 with the priority 200. This leads to the creation of the
synchronization domain 3, to which the three ACTs belong. The Appliance Server remains in the
global synchronization domain, which is domain 0.
3. After modification, use the command infocs to check the synchronization plan.
Caution:
The accesses on ACTs 1 and 2 should be set with the priorities 201 and 202, so that they stay in the same
synchronization domain (see Figure 10). They should not be set with the priority 200, as this case would
create two other synchronization domains (see Figure 11).
Domain 0
Com Server
Domain 0
Domain 3
CPU INT-IP B
Digital Access Digital Access
ACT 0
Priority=0 Priority=200
Migration
ACT 2 ACT 3
ACT 2
Digital
Access Digital Access
ACT 1
ACT 1
Figure 22.11: Example One: Three ACTs with Three Accesses with the Same Priority
Note:
This configuration after migration allows part of the initial configuration to be recovered. The ACT 3 access is
synchronizing and the other two accesses are potentially synchronizing. If the ACT 3 access fails, the ACT 1
access becomes synchronizing, but if the ACT 3 access is restored, it becomes synchronizing again, unlike in the
configuration before migration.

Domain 0
Com Server
Domain 0
CPU Domain 3
INT-IP B
Digital Access
ACT 0 Digital Access
Priority=0
ACT 3 Priority=200
ACT 2
Domain 2
Digital Migration
Access ACT 2 Digital Access
ACT 1

Priority=0 ACT 1 Priority=200
Domain 1
Figure 22.12: Incorrect Configuration of the Priorities
Note:
This configuration after migration does not allow the initial configuration to be recovered. Configuring the three
accesses with the priority 200 creates three separate synchronization domains. If one of the accesses fails, the
ACT that it was synchronizing is not backed up by the other accesses. The ACT is then free running.
22.3.3.3 Example Two

• A private digital access on both ACTs 1 and 2
• Priority is set to 0 on the access of ACT 0 (public), to 1 (private 1) on the access of ACT 1 and to 2
(private 2) on the access of ACT 2.
Do the following:
1. Configure the public access for ACT 3 with the priority 200. This leads to the creation of the
synchronization domain 3, to which the three ACTs belong. The Appliance Server remains in the
global synchronization domain, which is domain 0.
2. Configure the private accesses on ACTs 1 and 2 with the priorities 201 and 202, or configure both
as 201 if they are from the same synchronization source.

Domain 0
Com Server
Domain 0
Domain 3
CPU INT-IP B
Public Access Public Access
ACT 0
Migration
ACT 2 ACT 3 ACT 2
Private
Private Access
Access
Priority=202
Priority=2
ACT 1 ACT 1
Private Access Private Access

Figure 22.13: Example Two: Three ACTs with Three Accesses with Different Priorities
Note:
The configuration of the synchronization after migration respects the pre-migration configuration.
22.3.3.4 Example Three: the Highest Level ACT does not Have a Synchronizing Access
This example shows the specific situation where the highest level ACT does not have a synchronizing
access (see Figure 13).
• A digital access on both ACTs 1 and 2
• A synchronization priority set to 0 on the access of ACT 1 and set to 1 on the access of ACT 2.
Do the following:
1. On ACT 3, create a virtual board (one which is not physically present).
2. Create an access on this board with the priority 200.

Domain 0
Com Server
CPU Domain 0 INT-IP B

Virtual T2
ACT 0 Priority=200
Domain 3
ACT 2 ACT 3 ACT 2
Digital Migration
Digital Access
Access
Priority=202
Priority=1
ACT 1
ACT 1
Digital Digital Access
Access Priority=201
Priority=0
Figure 22.14: Example Three: Main ACT without Synchronizing Access
Note:
In this example, after migration, since ACT 3 does not have a synchronizing access, it is necessary to create an
access on a virtual synchronizing coupler with the priority 200. This brings us back to the previous topology.
Without this configuration, ACT 3 would belong to the synchronization domain 0, and would be free running.

22.4.1 Overview
On each PCX, configure:
• The synchronization priority of ISDN type digital accesses
• If necessary, the synchronization priority of the PCM boards.
22.4.2 Synchronization Priority on a Digital Access

Link priority is configured in the Digital Access object for the link.
1. Select: Shelf > Board > Digital Access
Shelf Address Depends on the site.
Board Address Depends on the site.
T0/T2 Access No. Depends on the site.
Access Type Select access type.

Synchronization Priority Enter the synchronization priority for this access:

• 0: Access with highest order of priority.
• 255: The access is never synchronizing.
• 200 to 254: Local synchronization (synchronization
domains are used).
Object name:
Attributes:
The other attributes are not relevant to synchronization.
Note:
Several accesses can have the same synchronization priority. In this case, the system chooses between accesses
with the same priority.
Note:
In a synchronizing domain, you can create a maximum of six accesses per Media Gateway.
22.4.3 Synchronization Priority on a PCM Board

The synchronization priority for a PCM type link is configured in the PCM board parameters.
Shelf Address According to site.
Board Address According to site.
Interface Type Select board type.
Synchronization Priority Enter the synchronization priority for this access:

• 0: Access with highest order of priority.
• 255: The access is never synchronizing.
• 200 to 254: Local synchronization (synchronization
domains are used).
The other attributes are not relevant to synchronization.

Chapter
23 Rainbow
23.1 Overview
As of R12.0, a Cloud Connect Control Agent component (also called Rainbow agent) is embedded on
the OmniPCX Enterprise. This Rainbow agent allows the OmniPCX Enterprise to establish a
permanent secure connection with the Rainbow Cloud infrastructure, using WebSocket Secure (WSS).
On Rainbow side, the access point is a PBX Cloud Gateway (PCG).
Upon request of the PCG, the Rainbow agent makes available OmniPCX Enterprise services and
sends notifications when the user configuration on OmniPCX Enterprise changes (user creation,
modification, or deletion). Notifications on entities and phone book are not sent to the PCG.
PCG Rainbow Cloud
PCX service interfaces embedded in

WSS logical channels
Rainbow
agent
Config Call OmniPCX Enterprise

Control
Figure 23.1: Rainbow agent overview
The scope of the following section is only limited to the necessary Rainbow agent configuration on the
OmniPCX Enterprise.
23.2 Description
The Rainbow agent provides:
• A permanent secure connection with the PCG. This connection is performed through a unique
multiplexed WebSocket Secure (HTTP/TLS) opened by the Rainbow agent. This multiplexed WSS
handles four logical channels such as:
Identifier Feature
0 WS Multiplex control
1 XMPP

Chapter 23 Rainbow
Identifier Feature
cfg Configuration
csta CSTA
• An XMPP client in charge of the OmniPCX Enterprise authentication.
• A configuration gateway used to connect the OmniPCX Enterprise internal configuration API
(CMISE over TCP/IP) to the cfg channel established with the PCG. The configuration gateway can
handle the following requests of the PCG:
• Get users via their directory number
• Get all users configured on the OmniPCX Enterprise
• Get all modified users since a given date
• Get all instances of the OmniPCX Enterprise phone book
• Enable/disable notifications on user creation, modification or deletion
• Rainbow activation code update on OmniPCX Enterprise
The configuration gateway also notifies the PCG when user configuration changes on the OmniPCX
Enterprise (user creation, modification, or deletion.)
• A CSTA transport gateway used to connect the TCP/IP socket opened on OmniPCX Enterprise
CSTA port to the csta channel established with the PCG. Connection to CSTA server is distributed
between the Rainbow agent (1. CPU role detection) and PCG (2. Application identification).
At startup, the Rainbow agent performs the following operations:
1. It retrieves its configuration from the OmniPCX Enterprise. It consists of:
• DNS and proxy parameters (see: Configuring network parameters on page 455)
• Rainbow parameters (see: Configuring the Rainbow parameters on page 455)
2. It opens a multiplexed WebSocket Secure with the Rainbow Cloud Infrastructure.
Channel 0 and 1 are implicitly created. OmniPCX Enterprise authentication via XMPP is performed
on the channel 1.
3. It establishes a TCP/IP connection with the CSTA port of the OmniPCX Enterprise and a csta
channel with the PCG.
4. It establishes both a TCP/IP connection with the configuration port of the OmniPCX Enterprise, and
a cfg channel with the PCG.

Chapter 23 Rainbow
PCG Rainbow Cloud
WSS channels WAN
DNS Proxy (+ Firewall/NAT)
Rainbow agent
CMISE CSTA
Call
Config OmniPCX Enterprise
Control
Figure 23.2: General architecture overview
23.3 Configuration
23.3.1 Configuring network parameters
The DNS server IP address and the proxy parameters (IP address and credentials) must be configured
on the OmniPCX Enterprise via the netadmin command. These parameters are used when the
Rainbow agent connects to the Rainbow Cloud infrastructure.
These data must be common to the Rainbow agent and Rainbow Cloud infrastructure.
To configure the DNS server IP address and the proxy parameters, refer to the document [13].
23.3.2 Configuring the Rainbow parameters

The Rainbow configuration is stored in a configuration file read by the Rainbow agent at startup (/
DHS3data/mao/ccca.cfg).
23.3.2.1 Activating Rainbow

To activate Rainbow, open the OmniPCX Enterprise configuration tool and perform the following
operations:
1. Select Rainbow

Chapter 23 Rainbow
Enable Rainbow Agent Select: YES

By default, this parameter is set to NO.
Note:
Enabling/disabling the Rainbow agent does not require any
license.
Rainbow ID Enter the unique identifier of your OmniPCX Enterprise in

the Rainbow Cloud infrastructure.
This field is mandatory when the Rainbow agent is ena-
bled.
Activation code Enter the activation code used to authenticate the Rain-
bow agent on the Rainbow Cloud infrastructure during the
initial login phase (XMPP initialization).
This activation code must be asked to ALE Internation-
alALE.
This field is mandatory when the Rainbow agent is ena-
bled.
Confirm Enter the activation code again

All parameter change results in a restart of the Rainbow agent, except in one case: the activation
code is updated in PCX configuration or following a Rainbow request, while the previous activation
code was not empty.
23.3.2.2 Configuring CSTA parameters

1. Select Applications > CSTA
Set Callback On Calling Device Select: YES

23.3.2.3 Configuring other Rainbow parameters

To configure other Rainbow parameters, perform the following operations:
1. Select Rainbow

Chapter 23 Rainbow
Rainbow domain This field displays the domain name of the Rainbow
Cloud infrastructure. The Rainbow domain name is initial-
ized to openrainbow.com. It is the default value.
To access the Rainbow infrastructure, this default value
must be kept.
Phone-book sent to Rainbow Select:

• YES (default option): The OmniPCX Enterprise phone
book is sent to the Rainbow Cloud infrastructure.
• NO: The OmniPCX Enterprise phone book is not sent
to the Rainbow Cloud infrastructure.
Keep this parameter to YES
Password status This field displays the status of the connection with the
Rainbow Cloud infrastructure. It is only available in read-
only mode.
Possible values are:
• Temporary: It indicates that a valid connection
between the Rainbow agent and the Rainbow Cloud
Infrastructure has never been established, for instance
because the temporary password has not yet been
entered by the system administrator (initial case) or
the entered password is incorrect.
• Confirmed: A connection is established with the
Rainbow Cloud infrastructure, with a valid password.
• Replacing: It indicates that the Rainbow agent has
received a password change request from the
Rainbow Cloud infrastructure. This status is displayed
until the Rainbow agent has validated the change
password operation.
Password hash This parameter contains the last 8 digits of the encrypted
password, currently used in the connection between the
OmniPCX Enterprise and the Rainbow Cloud infrastruc-
ture.
This parameter is also displayed in the Rainbow configu-
ration portal.
They must be identical in OmniPCX Enterprise and Rain-
bow.
This allows the administrator to detect if there is a prob-
lem of password between the OmniPCX Enterprise and
Rainbow
23.3.2.4 Resetting the password

When the connection between the OmniPCX Enterprise and the Rainbow Cloud infrastructure fails, it
may be helpful to reset the current password and to reconnect to the Rainbow Cloud infrastructure with
a new password.

Chapter 23 Rainbow
In this case, you must ask the Rainbow team to reset the current password and provide you a new
activation code. On the OmniPCX Enterprise, you must perform the following operations:
• Reinitialize the password:
1. Select Rainbow
2. Select Password reinitialization
• Enter the new activation code (see: Configuring the Rainbow parameters on page 455)
23.3.2.5 Disabling Rainbow

You can disable Rainbow by configuring the Enable Rainbow Agent to NO in the PCX configuration.
After deactivating this option, all parameters are reset.
If you enter again the Rainbow ID corresponding to your OmniPCX Enterprise, the connection is
established again.

Alcatel-Lucent OXO Connect
Expert Documentation: Hardware: Platform, Interfaces and

Devices
Release 2.1 - April 2017
8AL91201USAE Ed. 01
Legal notice
The information presented is subject to change without notice.
ALE International assumes no responsibility for inaccuracies contained herein.
Copyright © ALE International, 2017
Disclaimer
While efforts were made to verify the completeness and accuracy of the information contained in this
documentation, this document is provided “as is”. To get more accurate content concerning Cross
Compatibilities, Product Limits, Software Policy and Feature Lists, please refer to the accurate
documents published on the Business Partner Web Site.
In the interest of continued product development, ALE International reserves the right to make
improvements to this documentation and the products it describes at any time, without notice or
obligation.
The CE mark indicates that this product conforms to the following Council Directives:
• 2014/53/EU for radio equipment
• 2014/35/EU and 2014/30/EU for non radio equipment (including wired Telecom Terminal
Equipment)
• 2014/34/EU for ATEX equipment
• 2011/65/EU (RoHS)
Table of
contents Expert Documentation: Hardware:
Platform, Interfaces and Devices
Chapter 1
Expert Documentation structure
Chapter 2
C, S, M, L Racks
2.1 Hardware description............................................................................................................ 10

2.1.1 OXO Connect Compact................................................................................................................... 10
2.1.2 OXO Connect S................................................................................................................................... 10
2.1.3 OXO Connect M and OXO Connect L...................................................................................... 11
Chapter 3
Boards
3.1 PowerCPU EE................................................................................................................................13

3.1.1 Hardware description........................................................................................................................ 13
3.1.2 Hardware configuration....................................................................................................................14
3.1.3 External connections......................................................................................................................... 16
3.2 PowerMEX.........................................................................................................................................20
3.3 BRA......................................................................................................................................................... 21
3.4 PRA..........................................................................................................................................................24
8AL91201USAE - Ed. 01 - April 2017 - Expert Documentation: Hardware: Platform, Interfaces 3/152
and Devices
Table of
3.5 MIX-2.......................................................................................................................................................27
3.6 Mini-MIX...............................................................................................................................................29
3.7 AMIX-1...................................................................................................................................................31
3.8 UAI............................................................................................................................................................33
3.9 SLI-2........................................................................................................................................................37
3.10 LanX-2...................................................................................................................................................39
3.10.2 Configuration examples................................................................................................................... 41
3.11 APA.......................................................................................................................................................... 43
3.12 Power Supplies............................................................................................................................46
Chapter 4
Dedicated Sets
4.1 8001/8001G Deskphones....................................................................................................52

4.1.1 8001/8001G Deskphone description......................................................................................... 52
4.1.2 8001/8001G Deskphone Commissioning............................................................................... 54
4.2 8018 DeskPhone......................................................................................................................... 56
4.2.1 Detailed description........................................................................................................................... 56
and Devices
Table of
4.2.2 Commissioning.....................................................................................................................................59
4.3 80x8 and 80x8s Premium DeskPhones................................................................60
4.3.1 Detailed description........................................................................................................................... 60
4.3.2 Commissioning.....................................................................................................................................68
4.3.3 Maintenance.......................................................................................................................................... 72
4.4 8082 My IC Phone...................................................................................................................... 73
4.4.1 Basic description................................................................................................................................. 73
4.4.3 Commissioning.....................................................................................................................................80
4.4.4 Reset to factory....................................................................................................................................90
4.5 4135 IP Conference Phone............................................................................................... 92
4.5.1 Basic description................................................................................................................................. 92
4.5.3 Commissioning.....................................................................................................................................94
4.6 Generic SIP Phones................................................................................................................ 99
4.6.1 Commissioning.....................................................................................................................................99
4.7 4018 Phone Extended Edition..................................................................................... 102
4.7.1 Basic description............................................................................................................................... 102
4.7.2 Hardware description...................................................................................................................... 103
4.7.3 Commissioning...................................................................................................................................106
4.7.4 Maintenance.........................................................................................................................................111
4.8 8029/8039 Premium Deskphones............................................................................. 114
4.8.1 Detailed description..........................................................................................................................114
4.8.2 Commissioning................................................................................................................................... 119
4.9 4019 Digital Phone..................................................................................................................120
4.9.1 Basic description............................................................................................................................... 120
4.9.3 Commissioning...................................................................................................................................124
4.10 Input Method Editor...............................................................................................................125
4.10.1 Operation.............................................................................................................................................. 125
4.11 Terminal downloading.........................................................................................................130
4.11.1 Operation.............................................................................................................................................. 130
4.12 Add-on Module...........................................................................................................................132
4.12.1 LEDs and icons on AOM modules............................................................................................132
and Devices
Table of
4.13 V24/CTI Interface Module................................................................................................. 133

4.14 AP Interface Module..............................................................................................................135
4.15 S0 Interface Module...............................................................................................................136
4.16 500 DECT Handset..................................................................................................................137
4.17 8212/8232/8242/8262 DECT............................................................................................ 143
4.17.1 Overview................................................................................................................................................143
4.17.2 Key benefits......................................................................................................................................... 145
4.17.3 Key features.........................................................................................................................................146
4.17.4 Location ................................................................................................................................................ 146
4.17.5 Technical specifications................................................................................................................. 146
4.17.6 Accessories..........................................................................................................................................151
4.18 PIMphony Reflexes................................................................................................................ 152
4.18.1 Detailed description......................................................................................................................... 152
and Devices
Chapter
1 Expert Documentation structure
The OXO Connect Expert Documentation is split into fifteen separated documents. Each document
only describes the features supported by OXO Connect RC2.0* (for example: MMC station is not
described since it is not supported). Please refer to the OXO Connect Documentation Note, for
historical information. In addition, the Cross Compatibility document is the reference for detailed status
about supported and unsupported devices and applications.
* RC2.0 stands for any release starting from 2016 introducing Connect capabilities.
It appears on:
• Product stickers with release format: RC020/xx.yy
• In any documentation (including this one) as: R2.0
These documents are:
table 1.1: Expert Documentation structure
[1] OXO Connect Expert Documentation: General Presentation 8AL91200xxxx

Summary: this document contains general information on the OXO
Connect, such as a brief description of services provided, platform
hardware, handsets and user applications available, limits, compatibility
with standards, environmental constraints.
[2] OXO Connect Expert Documentation: Hardware: Platform, interfaces 8AL91201xxxx

and devices
Summary: this document covers all hardware aspects related to the
OXO Connect: this includes description of platforms (racks), boards,
sets and complementary equipment such as additional modules or in-
terface modules. This document also contains commissioning proce-
dures for sets.
[3] OXO Connect Expert Documentation: User services 8AL91202xxxx

Summary: this document gives the presentation and configuration pro-
cedure of features available for end-users. The final chapter of the
document synthesizes features availability according to the type of de-
vice or application.
[4] OXO Connect Expert Documentation: Voice mail 8AL91203xxxx

Summary: this document details the integrated voice mail system and
automated attendant (general description, management, services avail-
able for end-users), as well as configuration procedure to connect an
external voice mail unit.
and Devices
Chapter 1 Expert Documentation structure
[5] OXO Connect Expert Documentation: Mobility 8AL91204xxxx

Summary: this document contains a detailed description of mobility
services available on the OXO Connect. This includes useful informa-
tion to deploy a DECT, PWT or IP-DECT infrastructure, the description
of associated base stations and handsets, and necessary information to
implement OpenTouch Conversation clients.
Note:
This document does not cover VoWLAN.
[6] OXO Connect Expert Documentation: VoIP services 8AL91205xxxx

Summary: this document describes VoIP protocols supported by the
OXO Connect (such as H.323, SIP), configuration procedure of private
or public access through IP links, as well as dimensioning and mainte-
nance basic information.
[7] OXO Connect Expert Documentation: Private networks 8AL91206xxxx

Summary: this documentation gives a description of architectures and
protocols (such as SVPN, QSIG) supported for a private network, a de-
scription of ARS, metering, clock synchronization, and the configuration
procedure of accesses.
[8] OXO Connect Expert Documentation: General applications 8AL91207xxxx

This document gives a description of various applications available on
the OXO Connect, such as Hotel, Call metering, CTI, doorphones, Net-
work management center, point-to-point/point to multipoint T0, perma-
nent logical link, multiple automated attendant, multiple entities, My IC
Plugin for Outlook®, My IC Web, PIMphony Touch.
[9] OXO Connect Expert Documentation: Web-based tool 8AL91208xxxx

Summary: this document describes the web-based tool, which is the in-
tegrated monitoring tool of the OXO Connect.
[10] OXO Connect Expert Documentation: OmniTouch Call Center Office 8AL91209xxxx
Summary: this document provides the description and installation pro-
cedure of OmniTouch Call Center Office. The document also includes
presentation and operation of Announcement, Traceability, and a short
description of Agent, Statistics and Supervisor applications.
[11] OXO Connect Expert Documentation: Management tools 8AL91210xxxx

Summary: this document describes the management tool available for
OXO Connect(OMC). The document describes the OMC installation
procedure, the different types of access between OMC and OXO Con-
nect (local, remote, with or without proxy), the OXO Connect software
installation procedure via OMC and the list of services that can be man-
aged by OMC.
and Devices
Chapter 1 Expert Documentation structure
[12] OXO Connect Expert Documentation: Maintenance services 8AL91211xxxx

Summary: this document contains basic information concerning the
maintenance of your OXO Connect. This includes a diagnosis method-
ology in case of system of terminal(s) failure, the list of system messag-
es, procedure to save/restore data, procedure to stop/restart your sys-
tem, to replace CPU, boards and sets.
[13] OXO Connect Expert Documentation: Security 8AL91212xxxx

Summary: this document gives essential information to secure your
OXO Connect. This includes deployment guide for certificate, manage-
ment of passwords, management of accesses to services from
LAN/WAN and network configuration for remote accesses,
[14] OXO Connect Expert Documentation: System services 8AL91213xxxx

Summary: this document gives information about software keys, includ-
ing their complete list. The document also describes operation of the
OXO Connect with NTP (as client or server) and the configuration of
the embedded DHCP server.
[15] OXO Connect Glossary 8AL91214xxxx

Summary: this document contains a glossary of general telecommuni-
cations terms as well as specific terms related to OXO Connect.
In the present document, cross-references are identified by the number in the first column of the above
table.
Part numbers are given in the last column, where xx corresponds to the language code of the
document.
Outlook is either a registered trademark, or a trademark of Microsoft Corporation in the United States
and/or other countries.
and Devices
Chapter
2 C, S, M, L Racks
2.1 Hardware description

2.1.1 OXO Connect Compact
The OXO Connect Compact platform is a wall-mounted version. It provides 2 slots (1xCPU slot+1xMIX
slot).
The OXO Connect Compact platform is not expandable and cannot be used as satellite.
The Mini-MIX daughter board which is plugged into the PowerCPU EE board provides two Z (Analog
Extension) ports and two T0 (ISDN Basic Rate) accesses.
2.1.2 OXO Connect S

The OXO Connect S mainly consists of a plastic frame.
The plastic frame receives all the parts for attaching the power supply board, the fans, the battery and
the mains power connector, and everything needed to facilitate the routing of the cables.
There is no backplane board: the metric connectors are on the power supply module.
The enclosure consists of 3 parts: metal cover and base, plastic front face.
Access to the fans, the power supply module and the battery is gained by disconnecting the mains
cable and removing the top metal cover (it is vital to remove all the boards before opening the cover).
and Devices
Chapter 2 C, S, M, L Racks
Metal cover
Power supply (+Backpanel)
Boards (CPU + Battery retaining clip

interfaces)
Battery
Fan
Mains power cable
Plastic frame
Mains power connector
mounting plate
Grounding clips
Plastic front face

Metal base
2.1.3 OXO Connect M and OXO Connect L

The frame consists of a "U"-shaped sheath closed on the top by a riveted plate. The boards are guided
by 2 rails for OXO Connect M, or 3 rails for OXO Connect L, riveted vertically to the frame.
The enclosure consists of a metal top part, two metal side parts and a plastic front face.
Access to the fans, the power supply module and the batteries is gained by disconnecting the power
cable and unscrewing the backplane.
and Devices
Chapter 2 C, S, M, L Racks
Power supply
Cooling zone
(fans) Mains power
connector
Board
installation Batteries
areas
and Devices
Chapter
3 Boards
3.1 PowerCPU EE
3.1.1 Hardware description
3.1.1.1 Overview
The PowerCPU EE board, based on processor PowerQuicc II Pro MPC8377 from Freescale, has the
following characteristics: 800 MHz processor, 512 MB DDR2 SDRAM, MSDB (Mass Storage Daughter
Board) 8 GB equipped with eMMC (embedded Multi-Media Card), VoIP DSP C6421/4 (16 VoIP
channels).
The PowerCPU EE board is built around 2 main blocks interconnected via PCI:
• CPU part with MPC8377 processor and following interfaces:
• DDR 2 memory
• BOOT (NOR Flash)
• Dual UART
• PCI
• LAN interfaces
• I2C
• Telecom part with INOX ASIC and with connections to:
• Telecom DSP0 TMS320C5507
• Modem DSP1 TMS320C5402
• VoIP DSP TMS320C6421 (16 VoIP channels)
• Legacy Telecom architecture (PCM buses, ASL, HSL)
3.1.1.2 Daughter Boards

The PowerCPU EE board can be equipped with the following daughter boards:
• AFU-1 (Auxiliary Function Unit): supporting auxiliary functions such as general bell, doorphone,
audio In, audio Out, etc. The AFU-1 board is required for the connection of the ISDN-EFM box
(T0/S0 forwarding)
• HSL (High Speed Link): module interconnections. This daughter board is not compatible with the
Mini-Mix daughter board.
• MSDB (Mass Storage Daughter Board) 8 GB equipped with eMMC (embedded Multi-Media Card):
memory extension.
• ARMADA VoIP32: supporting two additional VoIP DSPs TMS320C6421 (2x16 VoIP channels)
• ARMADA VoIP64: supporting two additional VoIP DSPs TMS320C6424 (44/60 VoIP channels)
• Mini-MIX (only for OXO Connect Compact): this daughter board provides two Z (analog) ports and
two T0 accesses. This daughter board is not compatible with an HSL board.
and Devices
Chapter 3 Boards
Mass Storage Daughter Board

(MSDB) 8 GB equipped with eMMC
(embedded Multi-Media Card)
HSL1/HSL2
(optional)
DDR2 Module
(underneath)
Mini-MIX
(optional)
ARMADA VoIP32 or
ARMADA VoIP64
(optional)
HSL and Mini-MIX
daughter boards
AFU are not compatible
(optional)
Figure 3.1: Example of Daughter Boards on PowerCPU EE
3.1.2 Hardware configuration

3.1.2.1 Meaning of the LED Indications
Figure 3.2: PowerCPU EE Front Panel
Name Color Function
CPU Green CPU functioning LED (flashing)
POWER Red/Green • Mains operation: steady green LED

• Battery operation: steady yellow LED
• Idle: flashing red LED
• System shut down: steady red LED
FAN Red/Green • Both fans functioning: steady green LED

• 1 or both fans down: steady red LED
LAN Green LAN functioning LED (flashes when there is traffic)
and Devices
Chapter 3 Boards
Name Color Function
Mini-MIX Green (only on OXO Green only when accepted by the license 2B channels for
Connect Compact plat- MIX-2 boards. Detection of Mini-MIX board in OXO Connect
form) Compact platform.
MODULE Green Presence of HSL board
3.1.2.2 General Connection Diagram
LanX-2 board External LAN Switch
ETHERNET LANSWITCH LanX8-2
General bell
12V serviceable voltage

PowerCPU EE board
Power CPU EE
PROCESSING UNIT
PC (OMC, NMC)
Doorphone
Power MEX board (extension unit) 1

Power MEX
MODULE EXPANSION "Please wait" message
Background music
Loudspeaker
Alarm
Power MEX board (extension unit 2)

Power MEX
MODULE EXPANSION
and Devices
Chapter 3 Boards
3.1.3 External connections

3.1.3.1 Output Ports
Figure 3.3: PowerCPU EE
Available functions:
• LAN: 10/100/1000 base T Ethernet port (MDI-II/straight).
• SLI1/SLI2: Analog Z accesses from Mini-MIX board, General ringer; 12V output
• AUX: General ringer; 12V output
• CONFIG: RS232 for OMC.
• MODULE1: HSL1 link of HSL board for connection to module expansion 1
• ISDN T01: ISDN T01 port of Mini-MIX board
• MODULE2: HSL2 link of HSL board for connection to module expansion 2
• ISDN T02: ISDN T02 port of Mini-MIX board
• AUDIO: Interfaces Please wait message, Background music, Loudspeaker, Alarm
• DOORPHONE: Interfaces doorphone
table 3.1: Socket Connections
RJ45 pin 1 2 3 4 5 6 7 8
LAN TX+ TX- RX+ RX-
CenRg CenRG
SLI1/SLI2 Ground +12 V ZA1 ZB1 ZA2 ZB2
A B
CenRg CenRG
AUX Ground +12 V
A B
RMTRE
CONFIG CTS RX Ground TX DTR RTS
S
MODULE1 TX+ TX- RX+ RX-
ISDN T01 TX+ RX+ RX- TX-
MODULE2 TX+ TX- RX+ RX-
ISDN T02 TX+ RX+ RX- TX-
and Devices
Chapter 3 Boards
Audio In Audio In Audio Audio Audio Audio

AUDIO Alarm A Alarm B
A B Ctrl A Out A Out B Ctrl B
DoorPh Door- Door- DoorPh

DOORPHONE
B1 PhA1 PhA2 B2
3.1.3.2 Connecting a Please-Wait Message Player

This is connected via the AUDCTRL output (control contact open when idle) and the AUDIN input of
the AUDIO connector.
Distribution panel
AudCrtl A
Control AudCrtl B
circuit
Audio In A
Audio
Circuit
Audio In B
Power supply
Audio Input Characteristics:

Input impedance : 600 Ohms
Fuse Characteristics:
• Max. power : 10 W
• Max. voltage : 60 V
• Max. current : 500 mA
The contacts of the alarm and doorphone controls have the same electrical characteristics as
those indicated above.
3.1.3.3 Connecting a Background Music Tuner

This is connected via the AUDIN input of the AUDIO connector.
Distribution panel
Audio In A
TUNER
Audio In B
Power supply
Audio Input Characteristics:

• Input impedance : 600 Ohms
and Devices
Chapter 3 Boards
• Input level: access + 4.7 dBr or + 15 dBr
3.1.3.4 Connecting an Alarm

The alarm is activated in the event of a false stopping of the system.
It is connected via the ALARM output (control contact closed when idle) of the AUDIO connector.
Distribution panel
Alarm A
Alarm
system
Alarm B
Power supply
3.1.3.5 Connecting a Broadcast Loudspeaker

Broadcast loudspeakers are connected via the AUDOUT output of the AUDIO connector.
Distribution panel
Aud Out A
Amplifier
Aud Out B
Power supply
Audio Output Characteristics:

• Output impedance: < 500 Ohms
• Output level: access + 3 dBr
3.1.3.6 Connecting a General Ringer

The general ringer is connected via the CENRG output of the AUX connector.
Distribution panel
CenRg A
General
call ringer
CenRg B
Power supply
and Devices
Chapter 3 Boards
3.1.3.7 Connecting a Doorphone

2 doorphone types are available, depending on the operating mode used:
• Type A: relay-controlled doorphones (e.g. NPTT)
• Type B: doorphones controlled by MF Q23 signals requiring an SLI interface (e.g. TELEMINI and
UNIVERSAL DOORPHONE)
The doorphone interface comprises an intercom and an optional latch powered by the mains supply
through a SELV (Safety Extra Low Voltage) transformer.
It is connected via the DOORPHA and DOORPHB outputs (control contacts open when idle) of the
DOORPHONE connector.
3.1.3.7.1 Connecting a NPTT Doorphone
Distribution panel
DoorPhA1
DoorPhA2
DOORPHONE
DoorPhB1
To door
lock keeper
DoorPhB2
220V
ANALOG INTERFACES SLI16-2

9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
• A single doorphone with doorstrike may be connected to the system.

• The system also allows for the connection of 2 doorphones without latch.
3.1.3.7.2 Connecting a Telemini and Universal Doorphone
These doorphones require the use of a Z station interface.
• Several of these doorphones can be connected to the system; the limit is determined by the
maximum number of analog stations the system can support.
• A system cannot have Telemini and Universal doorphones at the same time.
and Devices
Chapter 3 Boards
3.1.3.8 Using the 12V Output

The GROUND and + 12V outputs on the AUX connector allow for the connection of an external 12V
device with a maximum energy consumption of 150 mA (OXO Connect S and OXO Connect M) or 300
mA (OXO Connect L).
3.2 PowerMEX
3.2.1.1 Overview
The PowerMEX board is a controller board for extension or module expansion.
The PowerMEX board (POWER Module EXpansion) performs the controller functions in the expansion
platforms.
3.2.1.2 Daughter Board

The PowerMEX board is equipped with an HSL1 (High Speed Link) board for interconnecting with the
basic platform.
HSL1
Figure 3.4: HSL1 Daughter Board on PowerMEX Board

3.2.2.1 Meaning of the LED Indications
MODULE EXPANSION POWER MEX
FAN POWER
MAIN
and pilot-ck
Figure 3.5: PowerMEX
and Devices
Chapter 3 Boards
Name Color Function
POWER Red/Green • Mains operation: steady green LED

• Battery operation: steady yellow LED
• Idle: flashing red LED
FAN Red/Green • Both fans functioning: steady green LED

• 1 or both fans down: steady red LED

3.2.3.1 Output Ports
MODULE EXPANSION POWER MEX
FAN POWER
MAIN
Figure 3.6: PowerMEX
Available functions:
• MAIN: HSL to basic module (cable max. length: 5 meters).
RJ45 pin 1 2 3 4 5 6 7 8
MAIN outputs TX+ TX- RX+ RX-
3.2.3.2 Connection
The PowerMEX board is connected to the MODULE 1 or MODULE 2 connector on the PowerCPU EE
board: see General Connection Diagram on page 15.
3.3 BRA
The BRA (Basic Rate Access) board provides the basic access points (2 x 64-Kbps B-channels + 1 x
16-Kbps D-channel per access) for connecting the system to the ISDN digital public network (point-to-
point or multipoint T0 link) and, starting with version R2.0, to a private network (point-to-point DLT0
link); Several versions are offered:
• BRA2-2: 2 T0 accesses
• BRA4-2: 4 T0 accesses
• BRA8: 8 T0 accesses
With OMC it is possible to define the operating mode access by access: T0 (ISDN) or DLT0 (QSIG). If
the choice is DLT0 (QSIG), the following operating mode may be defined: master = Network (NT),
slave = User(TE)
and Devices
Chapter 3 Boards
Note:
Configuration in T0/DLT0 is done by access pairs; if an access (04-001-01 for example) is configured in DLT0, the
2nd one (04-002-01) must also be configured in DLT0.
Plug-in to BACKX board
OBC
FICA FICA FICA FICA

2 4 6 8
FICA FICA FICA FICA

1 3 5 7

3.3.2.1 Output ports (faceplate)
ISDN ACESS - T0 BRA4-2
1 2 3 4
and Devices
Chapter 3 Boards
8 7 6 5 4 3 2 1
Female RJ45, front
RJ45 pin 1 2 3 4 5 6 7 8
Outputs TX+ RX+ RX- TX-
3.3.2.2 Connecting a T0 access

The OXO Connect system can be installed near the digital network termination or at a certain distance
(up to 350 m), as required.
3.3.2.2.1 Connection without T0/S0 forwarding
Distribution panel ISDN ACCESS - T0 BRA4-2
Transmission
TX
DNT
RX
Reception
3.3.2.2.2 Connection with T0/S0 forwarding

In the event of a loss of tension or CPU malfunction, the ISDN-EFM box allows a T0 access to be
forwarded directly to an S0 station.
Note:
The AFU-1 board (daughter board of the CPU board) must be equipped so as to detect a loss of tension.
Description of the ISDN-EFM box
X5
X4
X3
X2
X1
Not Used
BRA NT S0 CPU AUX
and Devices
Chapter 3 Boards
Connections
The ISDN-EFM box must be installed as close as possible to the system (3 m maximum). All the box
connections are made with straight RJ45-RJ45 cables.
Output connectors functions:
• BRA: connection of T0 access to be forwarded.
• NT: connection of ISDN network termination.
• S0: connection of forwarding S0 station.
• CPU: connection to the CPU board's AUDOUT connector.
• AUX: connection of Audio out, Alarm, General bell and 12 V use auxiliaries; since AUX is a copy of
the CPU board's AUDOUTde connector, check the sheet of the CPU board in use for connection
recommendations.
12V, GND, Alarm

ISDN-EFM module
General call ringer
Not Used
Audio Out
ISDN
S0 Terminal
Network Termination
3.4 PRA
The PRA board (Primary Rate Access) board provides 1 primary access for connecting the OXO
Connect system to the ISDN digital public network or to private networks:
and Devices
Chapter 3 Boards
• PRA -T2, DLT2: 30 x 64-Kpbs B-channels + 1 x 64-Kbps D-channel; 2048 Kbps.

• PRA-T1: 23 x 64-Kbps B-channels + 1 x 64-Kbps D-channel; 1544 Kbps
• PCM R2: 30 x 64 Kbps B-channels + 1 x 4 Kbps signaling channel; 2048 Kbps.
There are several connection options: T2 120-ohm symmetrical pairs and T1 100-ohm symmetrical
pairs. A coaxial 75-ohm connection is available using an external adapter kit.
OBC
4
Citroen straps
(definition of
FALC board type)

3.4.2.1 Board type definition (Citroën straps)
The board type is defined by the Citroën strap solder:
• T2 (ex-factory): no solders
• T1: solder on strap 1
• DLT2: solder on strap 2
• PCM R2: solder on strap 4
and Devices
Chapter 3 Boards
3.4.2.2 Connection (120- ohm symmetrical pairs)
ISDN ACCESS - E1 PRA-T2

Distribution panel
Transmission
TX
DLT
RX
Reception
The PRA board is connected to a digital line termination (DLT) by 2 reinforced symmetrical pairs.
Cable impedance: 120 Ohms +/- 20% between 200 kHz and 1 MHz; 120 Ohms +/- 10% at 1 MHz.
We recommend using an L120-series cable (or the L204 equivalent).
The distance T2-DLT is limited by the amount of loss between the DLT and T2, which must not exceed
6 dB at 1024 kHz.

3.4.3.1 Output ports (faceplate)
T2 board example
ISDN ACCESS - E1 PRA-T2
BUSY RAI AIS
NOS CRC LOS

NETW II PBX X
8 7 6 5 4 3 2 1
Female RJ45, front
RJ45 pin 1 2 3 4 5 6 7 8
NETW outputs RX+ RX- TX+ TX-
PBX outputs TX+ TX- RX+ RX-
NETW: connection to public network DLT.

PBX: network operation (QSIG).
and Devices
Chapter 3 Boards
3.4.3.2 Alarm LEDs

BUSY RAI AIS
NOS CRC LOS
T2 Name T1 Name Feature
BUSY BUSY B-channels busy (red LED lights up if at least 1 B-channel is busy)
RAI (ATD) RAI Remote frame alarm (red LED lights up on alarm)
AIS (SIA2M) AIS Too many "1's in the 2-Mbit binary train (red LED lights up on alarm)
NOS (MS) NSIG Absence of 2-Mbit signal (red LED lights up on alarm)
CRC (TE) CRC CRC error (red LED lights up on alarm)
LOS (PVT) NSYN Loss of frame alignment (red LED lights up on alarm)
In brackets: French abbreviations
3.5 MIX-2
The MIX-2 (Mixed Lines) board serves to connect ISDN basic accesses (T0), digital stations (UA) and
2-wire analog terminals (Z). 3 board versions are available:
• MIX244-2: 2 T0 accesses, 4 UA interfaces and 4 Z interfaces
Note:
Contrary to the BRA-2 board, the MIX-2 board's T0 accesses cannot be configured as DLT0 Network. Only DLTO
User is allowed in QSIG mode.
Example: MIX484-2 board
and Devices
Chapter 3 Boards
QCIALA (Z1 to Z4 (for X/8/4) or Z5 to Z8 (for X/4/8)

OBC
UA
1 to 4
QCIALA Z1 to Z4 (for X/4/8)

T0
1 to 4
UA
5 to 8

3.5.2.1 OUTPUT PORTS (FACEPLATE)
and Devices
Chapter 3 Boards
8 7 6 5 4 3 2 1
Female RJ45, front
RJ45 pin 1 2 3 4 5 6 7 8
Z outputs ZA ZB
UA outputs L1 L2
T0 outputs TX+ RX+ RX- TX-
3.5.2.2 CONNECTING AN ANALOG STATION (Z)

Follow the rules in the "SLI-2 board" section.
3.5.2.3 CONNECTING A DIGITAL STATION

Follow the rules in the "UAI board" section.
3.5.2.4 CONNECTING A T0 BASIC ACCESS

Follow the rules in the "BRA-2 board" section.
3.6 Mini-MIX
The Mini–MIX daughter board is an optional daughter board plugged on the PowerCPU EE board.
Note:
The Mini-MIX daughter board requires BACKXS-N back panel and PSXS-N power supply module. The Mini-MIX
daughter board can be used only in an OXO Connect Compact.
The Mini–MIX daughter board has the following features:
Two T0 (ISDN Basic Rate Access) interfaces
Two Z (SLI Analog Extension Access) interfaces
One local OBC to handle initialization and low level signaling
and Devices
Chapter 3 Boards
PowerCPU
or EE board
CPU-4
T01
T02
SLI
1/2
ABUSY
ADRIVF
ASCAN
HTR8
Figure 3.7: Mini-MIX daughter board
The Mini–MIX is detected via ASL (just like a peripheral board).

The Mini–MIX is located on position “6” (fixed) of ASL0 .
The Mini–MIX drives the Mini–MIX led ( previously WAN led ) on the front stiffener.
LED “ON” indicates that :
• the Mini–MIX daughter board is present and accepted by the mixed board license,
• the Backpanel supports 100V distribution (PSTYPE=”0”).
and Devices
Chapter 3 Boards
PowerCPU EE Front Stiffener
2x Z connections of Mini-MIX board
2x T0 connections of Mini-MIX board
Zoom on SL1/2 & AUX and ISDN T0 RJ45 Connectors / PowerCPU EE
SLI1/2 &
AUX
SLI1/2 & AUX RJ45 pin-out
1 2 3 4 5 6 7 8
CenRg CenRg
Ground +12V ZA1 ZB1 ZA2 ZB2
8765 432 1 A B
MODULE
ISDN T0
12 345678 ISDN T0 1 & 2 RJ45 pin-out
1 2 3 4 5 6 7 8
TX+ RX+ RX- TX-
Figure 3.8: Mini-MIX connections on PowerCPU EE Board
Inter–connections between the Mini–MIX and the PowerCPU EE are made through 2BergStak
connectors (already used for daughter boards AFU-1, HSL, etc.)
3.7 AMIX-1
The AMIX-1 (Analog Mixed Line) board is used to connect the analog public network (PSTN) to the
PBX. It has the following characteristics:
• 4 analog line accesses
• a maximum of 8 UA interfaces
• a maximum of 8 Z interfaces
• an OBC system interface supporting AT, Z and UA signaling
and Devices
Chapter 3 Boards
• protection features
• the PFCT (Power Failure Cut Through) feature which allows a local analog set to connect directly to
a network line in the event of a power cut or a software failure
Note:
The AMIX-1 board is required to connect the OXO Connect Compact platform to the analog public network
(PSTN). It can be used for OXO Connect Small, Medium, Large platforms.
The AMIX-1 board can take the following 2 daughter boards:
• GSCLI
• CLIDSP

MIXED AMIX 4/4/4-1

ANALOG INTERFACES
ANALOG TRUNKS DIGITAL INTERFACES
: indicates the assignment ports for the PFCT (Power Failure Cut Through) feature: the Z2 plug is
connected to a Z set, the AT1 plug to the PSTN.
MIXED AMIX4/8/4-1
ANALOG INTERFACES DIGITAL INTERFACES
MIXED AMIX4/4/8- 1
ANALOG INTERFACES
and Devices
Chapter 3 Boards
8 7 6 5 4 3 2 1
Female RJ45, front
RJ45 pin 1 2 3 4 5 6 7 8
AT outputs AT_B_RING AT_A_TIP
UA outputs UA_a UA_b
Z outputs Z_a Z_b
3.7.2.2 CONNECTING AN ANALOG STATION (Z)

For more information, refer to the SLI-2 board document.

For more information, refer to the UAI document.
3.8 UAI
The UAI board allows the connection of digital stations (UA). Two board versions are available:
• boards without external power supply capability:
• UAI4: 4 UA interfaces
• boards with external power supply capability:
• UAI16-1: 16 UA interfaces
3.8.1.1 Differences between the two boards

The UAI16-1 board is equipped with 2 ASICs OSIRIS while the UAI4/8/16 boards are equipped with
ASICs CATS (one ASIC OSIRIS replaces 2 ASICs CATS).
The system software detects whether the board is equipped with CATS or OSIRIS; if the ASIC OSIRIS
is detected, the software can also detect whether the board is connected to an external power supply.
The UAI-16 board allows to remotely supply the terminals connected to the 16 interfaces from a EPS48
external power supply connected to interface 1 using an external adaptation power cable (splitter).
and Devices
Chapter 3 Boards
3.8.1.2 BOARDS UAI4, UAI8 and UAI16

OBC
Interfaces UA 9 Interfaces UA 13
CATS CATS
CATS CATS
Interfaces UA 1 Interfaces UA 5
3.8.1.2.1 Output ports (Faceplate)
DIGITAL INTERFACES UAI16

9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
8 7 6 5 4 3 2 1
Female RJ45, front
and Devices
Chapter 3 Boards
RJ45 pin 1 2 3 4 5 6 7 8
Outputs L1 L2
3.8.1.3 UAI16-1 board

Plugging on BACKX board
OBC
UA interfaces 1 to 8 UA interfaces 9 to 16
OSIRIS OSIRIS
3.8.1.3.1 Output ports (Faceplate)
DIGITAL INTERFACES UAI16-1
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
(DC-In)
and Devices
Chapter 3 Boards
8 7 6 5 4 3 2 1
Female RJ45, front
RJ45 pin 1 2 3 4 5 6 7 8
Outputs 1 L1 L2 0V +48 V
Outputs 2 to 16 L1 L2

3.8.2.1.1 Connection without external power supply
The terminals are equipped with a cable and a self-acting switch that plugs into the wall socket. Each
terminal is connected up by a pair of 0.5 or 0.6 mm diameter wires.
System - Digital station distances:
• 0.5 mm SYT type cable: 800 m (station without option) or 600 m (station with S0 or Z option)
• 0.6 mm 278 type cable: 1,200m (station without option) or 850m (station with S0 or Z option)
DIGITAL INTERFACES UAI16

Distribution panel
L1 (4) 9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
L2 (5)
3.8.2.1.2 Connection with external power supply

A splitter allows the separation of the UA peripheral connection and the EPS48 external power supply.
and Devices
Chapter 3 Boards
DIGITAL INTERFACES UAI16-1

Distribution table
9 10 11 12 13 14 15 16
L1 (4)
1 2 3 4 5 6 7 8
L2 (5)
Splitter
1 1
EPS48
3.9 SLI-2
The SLI-2 board (Single Line) allows the connection of 2-wire analog terminals (Z). 3 board versions
are available:
• SLI4-2: 4 Z interfaces
and Devices
Chapter 3 Boards
OBC
QCIALA (Z13
QCIALA (Z5
QCIALA (Z1
QCIALA (Z9


9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
876 5 4 32 1
Female RJ45, front
and Devices
Chapter 3 Boards
RJ45 pin 1 2 3 4 5 6 7 8
Outputs ZA ZB
3.9.2.2 CONNECTING AN ANALOG Z STATION

The terminals are equipped with a cable and a self-acting switch that plugs into the wall socket. Each
set is connected up with a pair of 0.5 or 0.6-mm wires (the maximum distance with 0.5-mm cabling is
1.3 km).

Distribution panel
ZA
2
1
4
3
5 6
ZB
3.10 LanX-2
The LanX-2 board (Ethernet LAN Switch) serves to connect Ethernet terminals (IEEE 802.3
compatible). 2 board versions are available:
• LanX8-2
8 10/100 BT Ethernet ports (ports 1 to 7: MDI-X/crossover; Uplink: MDI-II/straight link)
• LanX16-2
16 10/100 BT Ethernet ports (ports 1 to 15: MDI-X/crossover; Uplink: MDI-II/straight link)
and Devices
Chapter 3 Boards
OBC
Converter
KS8998 KS8998
The LanX8-2 and LanX16-2 integrate respectively 1 or 2 Ethernet Gigabit ports for a Lanswitch/Layer 2
configuration. Any port can be used as an Uplink, as all the ports are auto MDI/MDIX.
and Devices
Chapter 3 Boards
3.10.2 Configuration examples

3.10.2.1 Configuration Example
Alcatel Server 1
Ethernet 10/100 Mbits
SWITCH
Up-Link Server 2
LANX8
ETHERNET LANSWITCH
PowerCPU EE
PROCESSING UNIT
Port 4
Port 3
Port 2
Host 1
Port 1
Host 2
Host 3

3.10.3.1.1 LANX-2 board
ETHERNET LANSWITCH LANX8-2

GE1 6 4 2
Port B
Port A
7 5 3 1
manages ports Ge1, 6, 4 and 2
manages ports 7, 5, 3 and 1
and Devices
Chapter 3 Boards
ETHERNET LANSWITCH LANX16-2

GE1 6 4 2 GE2 13 11 9
Port B
Port A
7 5 3 1 14 12 10 8
manages ports GE1, 6, 4, 2, GE2, 13, 11 and 9
manages ports 7, 5, 3, 1, 14, 12, 10 and 8
The LEDs of the A and B ports are both located at the top of the board. The LED display is as follows:
• Green LED (left) = link status and activity:
• LED off: link disconnected
• LED steady: link connected
• LED flashing: link active
• Yellow LED (right) = speed:
• off: low speed (10 or 100 Mb for Gigabit port, 10 Mb for the other ports)
• on: high speed (1 Gb for Gigabit port, 100 Mb for the other ports)
RJ45 pin 1 2 3 4 5 6 7 8
Ports 1 to 14 RX+ RX- TX+ TX-
GE1, GE2 TR0+ TR0- TR1+ TR2+ TR2- TR1- TR3+ TR3-
• Ports 1 to 14: 10/100 BT ports.

• GE1, GE2: 10/100/1000 BT ports.
3.10.3.2 CONNECTION PRINCIPLES

3.10.3.2.1 Basic 10/100 BT connection
MDI-X MDI-II
1 1
2
RX 2
TX
Straight link (twisted

pairs cable)
3 3
TX 6 6 RX
Hub, Switch Station, PC, IPPhone, or Uplink connector
and Devices
Chapter 3 Boards
3.10.3.2.2 MDI-X to MDI-X connection

MDI-X MDI-X
1 1
2 2
RX RX
3 3
6 6
TX TX
Crossover (twisted
pairs cable)
3.11 APA
The APA boards can only be used on systems running a software version posterior to R2.0.
The APA board (Analog Public Access) allows the connection of analog trunk lines (TL). Two board
versions are available:
• APA-4: 4 TL interfaces
• APA-8: 8 TL interfaces
and Devices
Chapter 3 Boards
Plugging on BACKX board
OBC OBC
X5
DSLAC DSLAC
X60 X61 X62 X70 X71 X72
X5: CLIDSP daughterboard plugging connector (detection of CLIP signal).

X60, X61, X62, X70, X71, and X72: GSCLI daughterboards plugging connectors (Ground Start
signaling).
3.11.1.1 CLIDSP BOARD EQUIPMENT

The signal needed to manage the CLIP (Calling Line Identification Presentation) is generated at the
CPU board level except in the following cases, which require a CLIDSP board (to be installed on
connector X5 of the board): US, UK and all countries using only Dual Tone (DT-AS) as alert signal.
The CLIDSP board will also be necessary to detect the CLIP in the on-hook state (later phase).
and Devices
Chapter 3 Boards

ANALOG PUBLIC ACCESS APA8
1 2 3 4 5 6 7 8
8765 432 1
Front panel female RJ45
RJ45 pin 1 2 3 4 5 6 7 8
Output1 ZSETB ZSETA LB-Ring LA-Tip ZB ZA
Outputs 2 to 8 LB-Ring LA-Tip
Note:
Z set B1 and Z set A1: connection to Z set for cut-through functionality. ZB1 and ZA1: connection to a Z access for
cut-through functionality.
3.11.2.2 CONNECTING A TL
3.11.2.2.1 Without TL forwarding

Distribution table
LA-Tip
Network
Public
Analog LB-Ring
3.11.2.2.2 With LR forwarding

In the event of power failure or CPU malfunction, this solution allows connection of the analog line
(connected to the APA board's equipment 1) to an analog station.
and Devices
Chapter 3 Boards
Distribution table
LA-Tip
Analog
Public LB-Ring
Network
ZSETA
Analog
Station
ZSETB
ANALOG INTERFACES SLI16
ZA, ZB
Note:
US connection features
• APA board equipped with Ground Start signaling: Ring is connected to the network's + polarity
while Tip is connected to the - (ground if using conventional battery).
• APA board equipped with Loop Start signaling: In case of conventional battery, Tip is normally
connected to the network equipment's ground and Ring to the network's - polarity. Nevertheless,
maintenance operations may temporarily or permanently inverse these polarities: the connection of
each of the battery's terminals to the earth cannot be ensured. In the case of va riable battery, no
terminal is connected to ground: the Tip and Ring outputs are variable.
3.12 Power Supplies

3.12.1.1 Power Supply PS1/PS1N
Power supply PS1/PS1N provides the different voltages required to operate an OXO Connect S
platform and also acts as a backplane board (slots 1, 2 and CPU).
and Devices
Chapter 3 Boards
Power supply connectors

for fans
SLOT 1
12V CPU fuse

(1A fast-acting)
F6.3AL/250V battery fuse

SLOT 2 (6.3A fast-acting, low breaking
capacity)
Battery connection
+BAT (red)
NEUTRAL
-BAT (black)
EARTH
Mains filter
connection
SLOT CPU
LIVE

Power supply PS2/PS2N, which provides the different voltages required to operate an OXO Connect M
platform, consists of 2 boards:
• PCH2: charger board
• PCO2: converter board
and Devices
Chapter 3 Boards
NEUTRAL
Fan power supply connectors
Mains power connexion
LIVE
12V fuse for CPU
(1A fast-acting)
110V/230V selection: 3
-jumpers in 1-2: 110 V
Plug-in connectors -jumpers in 2-3: 230 V
1
on BACK2*
SWT
PCO2 Board
GND
Connection with
PCO2 board
PO WER-V12DC
Battery fuse F10AL/250V
(10 A fast-acting,
low breaking capacity)
-BAT (black)
SWT
GND
PCH2 Board
+BAT (red)
POWER-V12DC
Connection with Battery

PCH2 board connexion

Power supply PS3/PS3N, which provides the different voltages required to operate an OXO Connect L
platform, consists of 2 boards:
• PCH3: charger board
• PCO3: converter board
and Devices
Chapter 3 Boards
NEUTRAL
Fan power supply connectors
Mains power connexion
LIVE
12V fuse for CPU
(1A fast-acting)
1
110V/230V selection:
Plug-in connectors -2 jumpers in 1-2: 230 V 3
-2 jumpers in 2-3: 110 V
on BACK3 1
SWT
PCO3 board
GND
Connection with
POWER-V40DCN
PCH3 board
Battery fuse F6.3AL/250V

(6.3 A fast-acting,
low breaking capacity)
SWT
GND -BAT (black) PCH3 board
POWER-V40DCN +BAT (red)
Connection with Battery

PCO3 board connexion
3.12.1.4 Batteries
Equipment:
• OXO Connect S: 1 battery
• OXO Connect M: 2 batteries mounted in parallel
• OXO Connect L: 3 batteries mounted in series
Battery characteristics:
• sealed lead battery
• 1,2 Ah / 12 V
and Devices
Chapter 3 Boards
• fire resistance better than or equal to UL94-V2

Maintenance:
To guarantee system shutdown without data loss in the event of a mains power failure, or if the mains
plug is unplugged at the wall socket, replace the batteries every two years. This maintenance operation
is vital to guarantee sufficient power autonomy to allow the files to be saved before the system shuts
down.
In the case of only a voice module (without Hard Disk), the standalone time is approximately 20
minutes.
3.12.1.5 UPS
A UPS (Uninterruptible Power Supply) is recommended because it increases the backup time provided
by the system’s batteries. A maximum of 2 OXO Connect platforms can be connected to a UPS.
Cable provided with UPS
Mains power cable provided with

system (country-specific)
To mains
UPS power
and Devices
Chapter 3 Boards
3.12.1.5.1 Equipment
The following table indicates compatible UPS models to use with each OXO Connect system for a
power autonomy of about 1 hour (40 minutes for the OXO Connect L + extension OXO Connect L used
with a standard configuration):
System UPS 220 V UPS 110 V
OXO Connect S Pulsar ellipse 300 Pulsar ellipse 300 USB
OXO Connect M Pulsar ellipse 650S Pulsar ellipse 650 RS232
OXO Connect L Pulsar ellipse 1200S Pulsar ellipse 1200 RS232
OXO Connect L + extension OXO Pulsar ellipse 1200S Pulsar ellipse 1200 RS232
Connect L
3.12.1.5.2 Choice of UPS

The following table indicates for each OXO Connect system (in extreme configurations) the
consumption that is used to choose a UPS from the various models offered by UPS manufacturers:
System Configuration Primary consumption
OXO Connect S 24 terminals 50 W
OXO Connect M 48 terminals 70 W
OXO Connect L 96 terminals 105 W
OXO Connect L + extension OXO 192 terminals 210 W

Connect L
3.12.1.6 EPS48 External Power Supply

The EPS48 external power supply (48V - 1A) is designed to power the UAI16-1 boards, thus enabling
the connection of power-hungry peripherals without a need for another module or a bigger module.
Plugged into the electrical power supply, a 2 m power cable with an 8-pin RJ45 connector powers the
splitter used with the UAI16-1 board.
A green lamp indicates tension.
The EPS48 external power supply's connection into the main power supply must be located as close
as possible to the system and be easily accessible.
table 3.2: Output Points
RJ45 pin 1 2 3 4 5 6 7 8
Outputs 0V 48 V
and Devices
Chapter
4 Dedicated Sets
4.1 8001/8001G Deskphones

4.1.1 8001/8001G Deskphone description
4.1.1.1 About this chapter
The following paragraphs are intended for administrators in charge of installing and commissioning
8001/8001G Deskphone sets for users declared on OXO Connect nodes.
8001/8001G Deskphone sets are SIP sets, based on IETF standards (RFCs).
Note:
For readability purposes, throughout this chapter the term "set" is used to refer to 8001/8001G Deskphone sets.
The following paragraphs provide:
• A description of the sets (see: Set ergonomics and technical specifications on page 53)
• The procedure to commission the set (8001/8001G Deskphone Commissioning on page 54)
• The procedure to upgrade set binaries (Upgrading set binaries on page 55)
• The procedure to replace a 8001/8001G Deskphone by another 8001/8001G Deskphone (see:
Changing the set by another 8001 DeskPhone set on page 55)
• The procedure to configure the user and password on a 8001/8001G Deskphone (see: 8001
DeskPhone Password management on page 56)
• The process to start a 8001/8001G Deskphone as 8001 SIP Phone in replacement of a same
8001/8001G Deskphone initially installed as Open SIP Phone (see: Replacing the set by another
8001 DeskPhone set on page 55)
User operations are described in a dedicated user guide.
and Devices
Chapter 4 Dedicated Sets
4.1.1.2 Set ergonomics and technical specifications
LCD screen (5 lines)
Call status LED

Volume keys
Line keys
Soft keys
Message and
headset keys Navigation keys
Application keys
Loudspeaker key
Keypad
Figure 4.1: Set layout
Physical characteristics:
• Corded handset (or headset). In its standard version, the set comes with a corded comfort handset.
• Two-level adjustable foot stand: 40° or 60°
• Wall-mountable
• Operating temperature: 0°C to 45°C
• Operating humidity: 10% to 90%
Audio characteristics:
• Audio codec: G711 (A-law and μ-law), G723.1, G.729AB
Power characteristics:
• Power over Ethernet (IEE 802.3af)
• Power adapter (DC 5V/1A output)
Connectivity:
• 8001 DeskPhone: LAN: 2 x RJ45 10/100M Ethernet ports
• 8001G Deskphone: LAN: 2 x RJ45 10/100/1000M Ethernet ports
• 1 x 3.5 mm Jack port (headset connection)
• 1 x RJ9 port (handset connection)
• 1 x RJ9 port (headset connection 4-Pin (CTIA, stereo))
• 1 x power supply port (AC/DC power adapter connection)
This supply port is reserved for future use (no power adapter available with the current version).
Note:
For a complete view of the set technical specifications, refer to the 8001/8001G Deskphone data sheet available
on the business portal (BPWS).
and Devices
4.1.2 8001/8001G Deskphone Commissioning

4.1.2.1 Overview
The 8001/8001G Deskphone sets are plug&phone, which means they are automatically created in the
OXO Connect, when connected to the network. A default certificate in the system allows plug&phone.
The 8001/8001G Deskphone software must be in version 3.6.0.5. If a previous software version is
installed on the set, the set starts as an "Open SIP Phone" and is not recognized as 8001/8001G
Deskphone SIP Phone".
The software is downloaded according to the initial 8001/8001G Deskphone software version of the
set:
1. Sets having a software version prior to 3.5.0.8 must be upgraded to the intermediate version 3.5.0.8
2. Sets are upgraded to version R120-v3.6.0.5
• The OXO Connect must be operational
• A free IP address must be available for the set
• A port with PoE must be available on a switch
• If the set is configured to start in dynamic mode (default configuration, a DHCP server must be
configured:
• If using the OXO Connect DHCP server: a range of available IP addresses must be configured
(in OMC, go to ALU IP Phones: DHCP IP Range).
• If using another DHCP server: the URL for the configuration files must be provided. This URL is
indicated using two proprietary options of DHCP server:
• Option 66 must specify the DM IP address, the value of this option must contain <OXO
Connect_IP_address:10443>
• Sub option 67 of option 43 (DHCP Vendor Specific information) must contain a string value
set to « /dmcfg/ »
The URL to download the configuration files is https://<OXO Connect_IP_address>:10443/
dmcfg.
The CGI script included in the URL is executed on the OXO Connect to create the device (if
necessary) and generate the configuration file.
4.1.2.3 Connecting the set to the LAN

Once the IP configuration is done, the set can be connected to the LAN:
1. Turn the set over so that you can see its base.
2. Plug the RJ45 cable into the set's LAN connector.
3. Connect the RJ45 cable to the LAN.
The set starts and connects to the system
4.1.2.4 Connection to the system

At first appearance of the set, the system creates the configuration file associated to this set and
automatically declares the set in the system subscribers' list.
The set sends an HTTPS request to retrieve its configuration files.
Note:
The SIP parameter configuration file is named <MAC address>.xml
and Devices
Example: 00809f5607ae.xml (for a set whose MAC address is 00:80:9F:56:07:AE)
The set being plug&phone, it starts automatically and can be used straight away.
The set can be further configured in OMC. It is visible in the subscribers list as SIP Phone (8001) or
SIP Phone (8001G).
4.1.2.5 Manual (static) configuration

The set IP parameters can be modified after first initialization.
On the set itself, connected to the system:
1. Press the OK button, or the Menu softkey
2. Go to System settings > Advanced settings > Advanced
3. Select Network > LAN Port
4. Select the Static mode
5. Configure the set IP address, ensuring first that it is a free address
6. Configure other IP parameters: IP subnetwork mask, and gateway (that is router)
7. Configure DNS settings
8. Configure port management settings
9. Go to System settings > Advanced settings > Advanced > Auto Provision
Enter the URL: https://<OXO Connect_IP_address>:10443/dmcfg and select HTTPS as
protocol
10.Press the Save softkey
Important:
If the OXO Connect is installed and configured in a VLAN topology, the VLAN must be manually enabled in
the advanced settings of the set. The corresponding OXO Connect VLAN Value must be entered manually
in set configuration.
4.1.2.6 Upgrading set binaries

If requested:
1. In OMC, select Import/Export > File Management For third Party Devices
2. Import the binary files and firmware configuration files in the directory named: Binary
3. Reboot the set manually
When the set connects to the OXO Connect, it upgrades its software, provided the binaries
imported in the system and the binaries present in the set are of a different version.
Note:
Set binaries can be imported or deleted, but not exported
4.1.2.7 Replacing the set by another 8001/8001G Deskphone set

In case of a replacement by another 8001/8001G Deskphone set, modify the MAC address of the set in
OMC.
There is no backup of terminal data, which means that the local call log and saved contacts are lost.
To replace a set initially installed as Open SIP phone by a same set and have it recognized properly by
the system:
1. Disconnect the phone from the network
2. In OMC, delete the registration Open SIP Phone
3. Reconnect the 8001/8001G Deskphone
It initializes normally and the OXO Connect license-bypass mechanism makes it appear as a SIP
8001/8001G Deskphone.
and Devices
It is preferable to disconnect 8001/8001G Deskphone set from the network during this operation. Once
reconnected, the set initializes normally and the OXO Connect license-bypass mechanism makes it
appear as a SIP phone 8001/8001G Deskphone.
4.1.2.8 8001/8001G Deskphone password management

After a 8001/8001G Deskphone SIP Phone starts with the OXO Connect, the user password for the set
web interface is changed from the default values: root / root to admin / admin.
To configure the set, if no new administrator password has been manually entered:
• On the 8001/8001G Deskphone set : when the password is requested, do not enter anything and
select OK (or try as 000000 password)
• From the web Admin interface, enter: admin / admin
If there is a specified password, different from the default password, for a 8001/8001G Deskphone SIP
phone configured in the OXO Connect, after the set is connected to the system, the login changes to
admin with the password specified in OMC System Misc/SIP Phone Admin password/SIP phone for
the phone.
If a manual 8001/8001G Deskphone SIP phone reset to factory settings is requested (for instance if the
administrator password is lost), on the set:
1. Go Menu > Functions Settings > Dial to find:
Set the option to "off" (no dial by name)
2. With the phone idle, dial *3*3*3"
This reboots the set to factory settings
4.2 8018 DeskPhone

4.2.1.1 Environmental requirements
• Storage temperature: -25°C to 55°C (ETSI EN 300 019-1-1 Class 1.2)
• Transportation temperature: -40°C to 70°C (ETSI EN 300 019-1-2 Class 2.3)
• Temperature controlled enclosed location: -5°C to 45°C (ETSI EN 300 019-1-3 Class 3.2)
• Relative humidity: 5% to 95% (ETSI EN 300 019-1-3 Class 3.2)
and Devices
4.2.1.2 Hardware description

4.2.1.2.1 Phone layout
Set screen Soft keys
Fixed keys
Dialing keypad Programmable

keys
Piano sensitive keys

Headset port
Figure 4.2: 8018 DeskPhone set layout
4.2.1.2.2 Embedded hardware

A BCM1103 CPU is included .
32 Mb RAM (DDR1), 32 Mb Flash (NOR).
4.2.1.2.3 Audio, handsets, hands free and headset
The 8018 DeskPhone is equipped with a USB connector instead of a standard microphone connector.
It comes in standard version with a comfortable corded handset.
It works in hands free mode at the user request.
4.2.1.2.4 Screen
The set screen is a black and white graphical display of 50 by 128 pixels with white backlight.
4.2.1.2.5 Keys
4.2.1.2.5.1 Dialing keypad
The dialing keypad is also used as alphabetical keyboard. Press the "alpha" fixed key, whose label
displays 123 < > abc. By default, the set is in numeric mode and the key is unlit. Press the alpha key to
switch to alphabetic mode.
On the dialing keypad, the selected character is changed with a short press on the key:
Press To input any of (in this order):
1 space | - 1
2 abcABC2
3 defDEF3
and Devices
Press To input any of (in this order):
4 ghIGHI4
5 jklJKL5
6 mnoMNO6
7 pqrsPQRS7
8 tuvTUV8
9 wxyzWXYZ9
0 .,;:“?!0
* *+%$/~&()[]=
# #@
4.2.1.2.5.2 Fixed keys

On all sets:
• Two fixed keys below the keypad (start call key: and stop call key: ) allow
to perform several actions
• A four-direction set of navigation keys (left, right, up, down) allows to select the different options
available on the screen. The OK button in the center of the navigation validates the selection.
• The c key to the left of the navigation allows to cancel the current action.
• Sensitive (piano) keys are located above the black grid of the lower part of the set.
Starting from the left to the right, they provide access to the following features:
• mute sound
• decrease sound volume
• increase sound volume
• put loudspeaker in service
• messaging services
and Devices
4.2.1.2.5.3 Integrated additional programmable keys

On 8018 DeskPhone sets, seven add-on keys are available with a digital label next to each one. The
first key triggers switching between numeric and alphabetical characters. The second key is labeled F1
(Hold in the US), and the third key is labeled F2 (Transfer in the US). By default, pressing the F1 key
puts the current call on hold and pressing the F2 key transfers the current call.
4.2.1.3 USB connector

The 8018 DeskPhone can be charged with boosted current via USB.
To configure USB boost charging:
1. In OMC (expert mode), go to Users/Base stations List -> Users/Base stations List -> Details ->
Misc.
2. Double-click the user in the list to open the User dialog box
3. In the User dialog box, click Misc.
USB Boost charging • Disabled (default value): boosted current is disabled

• Enabled: boosted current is enabled
4.2.2 Commissioning
4.2.2.1 Connecting the set
To connect the set to the PBX:
1. Plug the RJ45 cable into the set LAN connector
2. Connect the RJ45 cable to the LAN itself
3. If your set is not powered by PoE, plug the AC/DC external adapter to the set power supply
connector and connect the plug to the power supply
Once the set is connected and powered up, it automatically starts initializing.
4.2.2.2 Set initialization

By default, 8018 DeskPhone sets initialize dynamically and retrieve IP information automatically.
You can change this initialization mode. Static initialization is mandatory when the system does not use
a DHCP server.
To switch from dynamic initialization to static initialization and modify IP parameters:
1. Wait for the set to initialize and reach the end of the Network setup process, displayed on screen
2. Press simultaneously the star and pound keys
This displays IP settings
3. Use the soft key next to an option to modify the selection
4. Validate your modifications with the soft key next to the tick symbol
4.2.2.2.1 Requested IP parameters
The following information must be provided for static initialization:
• IP address (set's address)
• Subnetwork mask
• Router address
• TFTP1 server address: OXO Connect IP address
• Use VLAN: this box must be checked to enter a VLAN number
and Devices
• VLAN number if necessary

• TFTP port
The TFTP address(es) to enter may differ according to system configuration.
Please contact your system administrator for details on the configuration of your system.
With dynamic initialization, IP parameters are automatically sent by a DHCP server to the phone.
4.2.2.2.2 Deny of download
If the downloaded version is different from the version installed on the set and if the downloaded binary
is incompatible with the hardware/software, the terminal denies it and signals the problem to the
Communication Server.
The terminal requests binary files at each reset until a compatible binary is found.
Deny of download also applies to SIP binary.
4.2.2.3 Binary file download

On 8018 DeskPhone sets, binary upgrade is silent and takes place in the background, once the OXO
Connect has detected that an upgrade is required. Once the file is downloaded by the set and when
the terminal is idle, it resets and implements the new software.
While downloading the new firmware, the set runs with the current firmware.
4.3 80x8 and 80x8s Premium DeskPhones

4.3.1.1 Overview
There are two types of IP Premium DeskPhone sets: 80x8 Premium DeskPhone and 80x8s Premium
DeskPhone.
The available IP Premium DeskPhones are:
• 8078s Premium DeskPhone (delivered with a Bluetooth handset)
• 8068s Premium DeskPhone (delivered with a Bluetooth handset)
• 8068 Premium DeskPhone (delivered with a Bluetooth or corded handset)
• 8058s Premium DeskPhone
80x8s Premium DeskPhone sets come with VPN support.
80x8s Premium DeskPhone provide enhanced services compared to 80x8 Premium DeskPhone.
8028 Premium DeskPhone and 8028s Premium DeskPhone sets are very similar in their features and
capabilities.
8068 Premium DeskPhone and 8068s Premium DeskPhone sets are very similar in their features and
capabilities.
In the following paragraphs, all mentions to 8028s Premium DeskPhone and 8068s Premium
DeskPhone sets apply respectively to 8028 Premium DeskPhone and 8068 Premium DeskPhone sets
unless specified otherwise.

and Devices


4.3.1.3.1 Phone layouts
Although there are differences in the aspect and operation of these sets, their layout is identical, but for
the screen and number of available soft keys.
Alarm LED
Touch screen
Dialing keypad
Bluetooth handset
Headset jack
Adjustable foot stand
Alt key
Space bar
Magnetic alphabetic keyboard
Figure 4.3: 8078s Premium DeskPhone set layout (capacitive Touch Panel)
and Devices
Alarm LED
Soft keys
Set screen
Dialing keypad
Bluetooth handset
Fixed keys
Headset jack
Alt key
Space bar
Figure 4.4: 8068s Premium DeskPhone set layout
Alarm LED
Dialing keypad
Handset (Bluetooth
or corded)
Fixed keys
Headset jack Piano sensitive keys
Adjustable foot
stand (0° to 60°)
Alphabetic keyboard
Alt key
Space bar
Figure 4.5: 8068 Premium DeskPhone set layout
and Devices
Alarm LED
Dialing keypad
Handset (corded)
Add-on modules
Fixed keys
Headset jack
Alt key
Space bar
Alarm LED
Dialing keypad
Corded handset
Fixed keys
Adjustable foot
stand (0° to 60°)
Alphabetic keyboard
Alt key
Space bar
and Devices
Alarm LED Add-on keys Soft keys

Set screen
Dialing keypad
Corded handset
Fixed keys
Headset jack
Adjustable foot stand (0° to 60°)
Alarm LED
Add-on keys
Dialing keypad
Corded handset
Fixed keys
Adjustable foot
stand (0° to 60°)
Magnetic alphabetic
keyboard
Alt key
Space bar
4.3.1.3.2 Foot stand

All sets come with a 0° to 60° adjustable foot stand.
All sets come with a standard 3.5mm jack (4 poles for 80x8s Premium DeskPhone) to plug a headset.
80x8 Premium DeskPhone sets offer wide band audio qualities
Note:
The wide band capability is not available with the Bluetooth handset. It is available for sets with corded handsets.
80x8s Premium DeskPhone with corded handsets offer super wide band audio qualities (except for 8028s
Premium DeskPhone).
and Devices
G722 codec is set as the default codec for 80x8 Premium DeskPhone and 80x8s Premium DeskPhone
sets.
All sets come in their standard version with a comfortable corded handset.
They all work in hands free mode at the user's request.
Note:
The Bluetooth handset with reference BTHS-2 is compatible with the 8068 Premium DeskPhone with Bluetooth
set.
4.3.1.3.4 Screens
Characteristics of set displays are:
• 8078s Premium DeskPhone: capacitive Touch Panel, 480x800 Touch color graphical display
• 8068s Premium DeskPhone: 240x320 color graphical display of 240320 dots, in 16,7 M colors, with
Liquid Crystal Displays (LCD) Modules (LCM)
• 8058s Premium DeskPhone: 320x240 color graphical display
• 8038 Premium DeskPhone: 160x100 black and white graphical display, with white backlight
• 8028s Premium DeskPhone: 64x128 black and white graphical display, with white backlight
8058s Premium DeskPhone, 8068s Premium DeskPhone and 8078s Premium DeskPhone sets come
with Customized Skin.
4.3.1.3.5 Keys
All sets come with a standard 12-key dialing keypad.
On all sets:
• Two fixed keys below the keypad (start call key: and stop call key: ) allow
to perform several actions
The stop call key allows to end a call and ignore an incoming call
• Piano keys are located above the grid of the lower part of the set.
• mute sound
and Devices
• hold call. This is the default feature for F1 keys (but can be programmed with
another feature)
• transfer call. This is the default feature for F2 keys (but can be programmed with
another feature)
redial information
• information page (displayed on screen)
On 8028s Premium DeskPhone sets, four add-on keys, each with a LED, allow to customize each set
according to the user's needs. A paper label at the right of these keys allows to write down a brief
description of the feature programmed on the key.
On 8058s Premium DeskPhone sets, four add-on keys are available on the two lower lines of the
screen.
4.3.1.3.5.4 Alphabetic keyboard
A standard (hot pluggable) keyboard is available for all sets, in the following layouts:
• Azerty (FR)
• Qwertz (DE)
• Qwerty (international)
• Qwerty (Nordic)
A magnetic external alphabetic keyboard is available on 80x8s Premium DeskPhone sets.
If you change keyboard type, ensure it is plugged in before restarting the set.
4.3.1.4 Connecting optional equipment

4.3.1.4.1 External interfaces
On all sets, a 3.5mm jack connector allows to plug a headset to the phone.
and Devices
RJ9 connector RJ45 10/100/1000BASE-

(alphabetic T (PC access or
RJ11 connector keyboard) cascaded IP phone)
(external ringing
and audio active
envelope indicator)
SATA connector
(for add-on modules 10, 40
keys or Smart module)
RJ9 connector
RJ45 connector (10/100/ (corded handset)
1000Base-T) for LAN
access (IEEE802.3af)
2.0mm jack
(external main
power adapter)
Figure 4.10: External interfaces on the back of 80x8 sets
RJ45 10/100/1000BASE- 3.5mm jack

T (PC access or (external main
cascaded IP phone) power adapter)
RJ11 connector
(external ringing
and audio active
envelope indicator)
SATA connector (for add-on modules, RJ9 connector (corded

10, 40 keys ir Smart module) handset)
USB RJ45 connector (10/100/
1000Base-T) for LAN
Figure 4.11: External interfaces on the back of 8028s Premium DeskPhone sets
3.5mm jack
RJ45 10/100/1000BASE- (external main
T (PC access or power adapter)
RJ11 connector cascaded IP phone)
(external ringing
and audio active
envelope indicator)
Microphone connector
SATA connector (for add-on modules,

10, 40 keys ir Smart module)
RJ45 connector (10/100/ RJ9 connector (corded
USB
1000Base-T) for LAN handset)
Figure 4.12: External interfaces on the back of 80x8s Premium DeskPhone (except for 8028s Premium
DeskPhone)
4.3.1.4.2 Additional key modules

On all sets, several add-on modules, connected via SATA (see: External interfaces on page 66), can
complete the standard number of programmed keys.
and Devices
Note:
• These add-on modules are not compatible with 40x8 and 40x9 phone sets.
• Add-on key modules designed for 40x8 and 40x9 phone sets are not compatible with IP DeskPhones sets.
The available modules are:
• 10-key module (can be fastened to the set):
• 40-key module (on its own foot stand, placed next to the set)
• Smart-key module (on its own foot stand, placed next to the set)
4.3.2 Commissioning
To connect the set to the PBX:
1. Plug the RJ45 cable into the set LAN connector
2. Connect the RJ45 cable to the LAN itself
3. If your set is not powered by PoE, plug the AC/DC external adapter to the set power supply
connector and connect the plug to the power supply
Once the set is connected and powered up, it automatically starts initializing.
and Devices
4.3.2.2 Commissioning a Bluetooth® handset

The use of the 8068 Premium DeskPhone with Bluetooth or without Bluetooth can be detected (in
OMC, Expert View): Subscribers/Basestations list > Device details > Susbscriber tab) as follows:
• For a 8068 Premium DeskPhone with Bluetooth set: the Terminal option “8068 Premium
DeskPhone” is displayed in Original Type field.
In this deskphone type, bluetooth option is available in the phone menu (Settings > My Phone)
• For a 8068 Premium DeskPhone without Bluetooth set: the Terminal option ”8068 Premium
DeskPhone – no BT” is displayed in Original Type field.
In this deskphone type, bluetooth option is not available in the phone menu.
Caution:
Bluetooth handsets are available for 8068 Premium DeskPhone with Bluetooth sets only. The handset with
reference BTHS-2 is compatible with 8068 Premium DeskPhone with Bluetooth sets.
Audio Key
On/Off Hook
Battery Compartment
Handset LED
Figure 4.13: Bluetooth handset ergonomics
4.3.2.2.1 Connecting the battery

The battery pack is housed in the battery compartment located in the handset.
The battery pack is reloaded when the handset is placed on its socket. A complete battery load
requires 16 hours.
The autonomy of the battery is of 10 hours in conversation and 33 hours in standby.
The handset Led indicates the battery load state (when the handset is on its socket):
• Led off: the battery is loaded
• Led green steady: the battery is loading
4.3.2.2.2 Binding the handset
Before a Bluetooth® handset can be used, it must be bound correctly to the set:
1. On the 8068 Premium DeskPhone with Bluetooth set, select the Menu page and navigate to:
Settings -> My phone -> Bluetooth -> Add device
2. On the Bluetooth® handset make a simultaneous long press on the On/Off Hook key and the Audio
key
A sound made of three different tones is audible and the led flashes alternatively green and orange.
The Bluetooth® handset enters in pairing mode for about one minute and then goes off. The set
and Devices
searches for Bluetooth® equipment, waits until the type of equipment is detected and displays its
address.
3. On the set, select the relevant equipment and press the Add key.
A sound made of three different tones confirms the correct installation of the handset. The handset
led flashes green or orange depending on the battery charge.
4.3.2.2.3 Adjusting audio level
There are two ways to adjust the audio level:
• On the set with the keys
• On the Bluetooth® handset with the key

Consecutive presses adjust the handset volume (3 levels).
4.3.2.2.4 Activating the mute feature
When the mute feature is enabled your correspondent can no longer hear you.
There are two ways to activate the mute feature:
• On the set with the mute key
• On the Bluetooth® handset with a long press on the key
4.3.2.3 Connecting an add-on module to the sets

Add-On Modules (AOMs) can be connected to sets. They are added to the right side of the set.
Three types of Add-On Module exist and provide keys associated with icons:
• AOM10 provides 10 keys
• Smart Display Module provides 14 keys with programmable LCD labels
4.3.2.3.1 Rules and restrictions
The following rules apply to the use of Add-On Modules:
• A maximum of three Add-On Modules of the types AOM10 and AOM40 can be connected to each
set, providing up to 120 additional keys.
• A maximum of three Smart Display Modules can be connected to each set, providing up to 42
additional keys.
• Add-On Modules of types AOM10 and AOM40 can be used on the same set, but a Smart Display
Module cannot be used in conjunction with an AOM10 or AOM40.
• If an AOM10 is used with other Add-On Modules, it must be connected as the last module on the far
right of the set.
4.3.2.3.2 Connecting add-on modules
To connect an Add-On Module:
1. Remove the tab located on the right side of the set.
2. Plug the Add-On Module's SATA connector into the set's SATA connector.
3. Insert the Add-On Module attachments into the appropriate holes located on the right side of the
set. (AOM10 only)
4. Screw the Add-On Module to the set. (AOM10 only)
and Devices
Note:
If the set is on when you plug in an Add-On Module, you must restart the set after connection.
4.3.2.4 Set initialization

By default, 80x8 sets initialize dynamically and retrieve IP information automatically.
If you want to change initialization mode or configure IP settings:
1. Press the i key and the # key simultaneously when the set is powered up
2. Enter your password (if needed) and validate
The configuration menu is displayed
3. Get to IP parameters
4. Click on the icon on the left to validate (or on the icon on the right to cancel)
5. Reset the phone to validate your modifications
Static initialization is mandatory when the system does not use a DHCP server.
If the sets must initialize dynamically, the auto provisioning must be activated: see Security - Auto
provisioning
4.3.2.4.1 Requested IP parameters
The following information must be provided for static initialization:
• IP address (set's address)
• Subnetwork mask
• Router address
• TFTP1 server address (parameter not used)
• TFTP2 server address (parameter not used)
• Use VLAN: this box must be checked to enter a VLAN number
• VLAN number if necessary
• Strict VLAN if necessary
• TFTP port
With dynamic initialization, IP parameters are automatically sent by a DHCP server to the phone.
The following information must be provided for initial startup:
1. From the Registration window, enter:
a. The set directory number
b. The set Password
If the set has already been initialized in the same configuration, there is no need to enter the directory
number and password again.
4.3.2.4.2 Deny of download
If the downloaded version is different from the version installed on the set and if the downloaded binary
is incompatible with the hardware/software, the terminal denies it and signals the problem to the Call
Server.
The terminal requests binary files at each reset until a compatible binary is found.
Deny of download also applies to SIP binary.
4.3.2.5 Binary file download

To operate correctly, 80x8 sets require binary files, automatically downloaded at set initialization. These
files must comply with the PBX version and configuration. After system upgrade and each time a set
and Devices
initializes, version numbers of binary files are verified to determine whether an update of these files is
necessary.
When a file is downloaded to the set, it overwrites any previously existing file.
Each time the IP phone is initialized, its binary version is checked to see whether more recent binaries
need downloading.
When a set has initialized at least once with the PBX, on subsequent startup, it does not request a
binary header and switches to fast initialization.
The version of binary files for Premium DeskPhone sets. starts with 4.50.YY
4.3.3 Maintenance
4.3.3.1 Error and Information messages
The table below lists the error and information messages. It has the following format:
Short text = text displayed on the screen, in case of real error or for information.
Description = status/error description
table 4.1: Starting phase error messages
Short text Description
END Starting phase is terminated (successful or un-

successful)
STARTED Step started
SUCCESS Step successful
FAIL Step failed
RETRYING Retrying step
NO MAC ADDRESS No Ethernet MAC address stored in flash
DHCP NOT RESPONDING DHCP Server is not responding
BAD IP ADDRESS IP address is incorrect
BAD ROUTER ADDRESS Router address is incorrect
ROUTER PING FAILED Router not responding to ping
BAD TFTP ADDRESS TFTP server address is incorrect
ADDRESSES MISMATCH Address, mask and router do not match
TFTP NOT RESPONDING TFTP server is not responding
TFTP SERVER ERROR TFTP server error
BAD FILE CONTENT Error found in downloaded file
and Devices
FILE TOO LARGE File is too large (cannot be downloaded)
SAME VERSION FOUND The version retrieved is the same as the version
running
NEW VERSION FOUND New IP Touch software version found (download)
FLASHING Flashing in progress
FLASHING FAILED Failed to flash downloaded binary
TRYING ANOTHER CPU Trying next address from configuration file
NO ETHERNET LINK Ethernet link not connected (LAN port only)
initializing First text message after hardware reset and

copyright information
1/5 network start Phase 1 is running: the set is starting its network
interface
2/5 network setup Phase 2 is running: the set is looking for IP ad-
dresses
3/5 config download Phase 3 is running: the set is trying to get a

lanpbx file
4/5 binary download Phase 4 is running: the set is downloading a new

binary
5/5 connecting Phase 5 is running: the set is trying to talk to the

system
4.4 8082 My IC Phone

4.4.1 Basic description
4.4.1.1 Overview
The 8082 My IC Phone set is a full-featured SIP device which constitutes a new step in the
implementation of user needs and comfort.
and Devices
Its screen is a 7 inch capacitive LED backlit touch screen, which provides a context sensitive feedback,
easing the tasks of users.
Access to the most common features is facilitated by a quick access pad, where a sensitive home key
brings you to the homepage. The other sensitive similar keys pilot your audio volume and provide
access to your main applications.
Its audio quality is outstanding and welcomes:
• Corded comfort handset or Bluetooth® handset (or headset)
• High quality loudspeaker
• Handsfree feature with high fidelity audio quality
An open connectivity supports easy expansion with a 10/100/1000 Ethernet switch for LAN and PC
connectivity, an embedded Bluetooth® chipset, a 3.5 mm headset port, two USB connectors, as well as
connectors for keyboard and handset.
4.4.1.2 Video architecture

The 8082 My IC Phone sets includes features that support video capabilities for:
• Video calls
• Door management
A Logitech webcam can be added to the 8082 My IC Phone set as part of the interactive hardware for
the video feature.
and Devices
Video calls can be configured for:

• 8082 My IC Phone over a SIP trunk
• Other SIP phones with video capabilities
Door management with the 8082 My IC Phone and a door camera is available with the Link Slim IP
Door Phone
and Devices

4.4.2.1 Set Equipment
The 8082 My IC Phone set includes the following items:
• Bluetooth® Handset with a front LED or Corded comfort handset
• Hands-free station speaker
• A quick access pad (which includes LEDs)
• A set screen, which is adjustable from the typical angle of 60° relative to the table surface, to a near
horizontal position
4.4.2.2 Quick Access Pad LEDs

LEDs are lit for each active feature displayed, regardless of the status (idle, busy) of the set.
Touching a LED activates/deactivates the corresponding feature.
The table below indicates the default meaning of LEDs. Note that this meaning can depend on the
application active on the set.
LED Corresponding Feature
Mute
Volume down
Volume up
Hands-free
User information, presence and call routing configuration (including Do

not Disturb)
and Devices
LED Corresponding Feature
Communications
Dial/Search
Events
Home
4.4.2.3 Set Screen

The LCD set screen is touch sensitive.
When buttons are displayed, touch any button to activate a feature (or display the corresponding
window).
Figure 4.14: 8082 My IC Phone Screen Example
and Devices
Figure 4.15: Example of Home Page
When a list is displayed, either horizontally or vertically, touch the screen and move your finger in the
desired direction. The display reacts according to the direction of your finger movement.
Figure 4.16: 8082 My IC Phone Screen List Example
4.4.2.4 Video accessories

Note:
Video compatibility is only available for the 8082 My IC Phone HW2 and later. HW1 sets are not video compatible.
The 8082 My IC Phone can be used in conjunction with a video hardware to provide capabilities for:
• Video calls
• Door management support
The Logitech C920 can be connected directly to the 8082 My IC Phone via the USB connection.
and Devices
Figure 4.17: Logitech C920 webcam
Features for the Logitech C920 include:

• Wide view field
• Omni-directional microphones
• High quality Zeiss lens
• Plug-and-play with most video conferencing and UC applications
The Link Slim IP Door Phone can provide the exterior camera and bell push for the door phone
application used with the 8082 My IC Phone. It is an IP based phone that is linked to the OXO Connect
and can be used to manage entry access.
Figure 4.18: Link Slim IP Door Phone
The Link Slim IP Door Phone uses a single cable to use the PoE capabilities to control door entry from
a computer or IP telephone. Features include:
• Voice & Image based on Full SIP protocol
• Autofocus IP Camera
• White LED for automatic lighting for camera
• PoE technology or Power supply 12 V AC/DC, 500 mA max
• Ethernet - 10/100 MB SIP connection P2P or PBX network system
• Day/night switching feature
and Devices
4.4.3 Commissioning
4.4.3.1 Overview
This module presents all the actions required for commissioning the 8082 My IC Phone sets.
Contextual Sensitive
Touch Screen
Bluetooth
Handset Quick Loudspeaker
Access Pad
Microphones
Figure 4.19: 8082 My IC Phone set layout
The following figure illustrates the connectors on the base of each set.
and Devices
Alphabetic keyboard connector

Power connector
PC connector
Handset connector
USB connectors
LAN
connector
Additional key module
connector
Headset jack
Figure 4.20: 8082 My IC Phone set connectors
4.4.3.2 Commissioning the set

This section describes how to commission the set in the two available initialization options:
• Static initialization: commissioning is manual on the set and through OMC
• Dynamic initialization (DHCP): no commissioning is needed, 8082 My IC Phone sets are fully plug &
phone
Depending on the selected mode, the set commissioning is different.
For static initialization, the operation order is as follows:
1. Connect the set, refer to Connecting the set on page 82
2. Configure network parameters on the set, refer to Configuring network parameters for static
initialization on page 84
For dynamic initialization, the operation order is as follows:
1. Configure OXO Connect DHCP server, refer to Configuring OXO Connect DHCP server on page
83, or configure an external DHCP server, refer to Configuring an external DHCP server for
dynamic initialization on page 83
2. Connect the set, refer to Connecting the set on page 82
3. If necessary, configure the user name and password in OMC, refer to Configuring the user name
and password in OMC on page 84
4.4.3.2.1 Prerequisites
and Devices
• For network configuration, any of the following must be implemented:

• In dynamic mode, a DHCP server must be configured
• In static mode, a free IP address must be available for the set
• A port with PoE must be available on a switch. If not available, a PoE injector must be used
4.4.3.2.2 Connecting the set
This section describes how to:
• Connect an 8082 My IC Phone set to the LAN (Local Area Network)
• Connect the external power adapter, if necessary
Note:
The external power adaptor is compatible with 8082 My IC Phone HW2, it is not compatible with version HW1.
4.4.3.2.2.1 Connecting an 8082 My IC Phone set to the LAN
To connect the set to the LAN:
• If you are using the 8082 Power Over Ethernet Injector Kit:
1. Plug an RJ45 cable between the data in port of the kit and the LAN
2. Plug an RJ45 cable between the data and power out port of the kit and the set LAN connector
3. Plug the kit to the mains
• If you are not using the 8082 Power Over Ethernet Injector Kit, plug an RJ45 cable between the set
LAN connector and a port of the switch
4.4.3.2.2.2 Connecting power supply
Note:
Only available for 8082 My IC Phone HW2
If you are not using a PoE switch or the 8082 Power Over Ethernet Injector Kit, connect the AC/DC
external adapter:
1. Plug the appropriate cable from the adapter into the set's power supply connector.
2. Connect the plug from the adapter to the mains power supply.
4.4.3.2.3 Initializing the sets
The following sections describe how to:
• Select the initialization type
• Initialize the 8082 My IC Phone set
4.4.3.2.3.1 Selecting the initialization type
The default initialization is Dynamic Alcatel.
To select the initialization type, refer to the following table.
table 4.2: Initialization type selection
If Then the required initiali- Further information

zation type is
You use OXO Connect Dynamic or Proprietary • Refer to Configuring OXO Connect DHCP
DHCP server Dynamic server on page 83
You use another Dynamic • Refer to Configuring an external DHCP

DHCP server server for dynamic initialization on page 83
and Devices
You do not use a Static • Refer to Configuring network parameters for

DHCP server static initialization on page 84
• Obtain from your network administrator:
• An IP address for the 8082 My IC Phone
set
• The subnetwork mask
• The DNS addresses (primary and
secondary)
• The VLAN ID (if VLAN is used)
• The IP address of the OXO Connect for
set configuration file download
Note:
You need to know the set directory number.
4.4.3.2.3.2 Configuring OXO Connect DHCP server

The OXO Connect DHCP server is enabled by default during startup wizard installation. If enabled,
8082 My IC Phone sets automatically initialize in dynamic mode, when plugged to the OXO Connect. In
other words, 8082 My IC Phone sets automatically get their IP configuration from the OXO Connect
DHCP server
If the OXO Connect DHCP server is disabled, you can enable it as follows:
• In OMC, go to Hardware and Limits > LAN/IP Configuration > DNS/DHCP.
• In the ALU IP Phones: DHCP IP Range area, select the Enable check box.
• Modify the range of IP addresses if needed.
• Click the OK button to confirm your entries.
4.4.3.2.3.3 Configuring an external DHCP server for dynamic initialization
Two types of dynamic initialization are available:
• Dynamic (default value): the set selects in priority DHCP offers, with a Vendor Specific option
corresponding to an ALE International server.
• Proprietary Dynamic: the set accepts only DHCP offers with a Vendor Specific option
corresponding to an ALE International server (alcatel.int-ip.0, alcatel.a4400.0,
alcatel.a4200.0).
When initializing in dynamic mode, the set provides the following information in the DHCP Discover
message
• Option 60: (vendor class identifier): alcatel.ictouch.0
• Option 55: list of requested options: subnet mask, router option, broadcast address, option 43
vendor specific info, server ID, renewal time, rebinding time and vendor class ID
Option 43 is vendor specific information, meaning that this option is defined for a specific client vendor
ID. In the DHCP offer, the data within Option 43 corresponds to the client vendor ID specified in the
request.
In the case of 8082 My IC Phone sets, suboption 67 of option 43 provides the path of configuration files
on the OXO Connect.
The DHCP offer provides the following parameters:
• IP address
• Router IP address
and Devices
• Subnet mask
• Option 66: IP address:10443 or name of the OXO Connect:10443, for example
192.168.12.34:10443
• Suboption 67 of option 43: the value of this sub-option corresponds to the DM Url.It must contain a
string value set to /dmcfg/
• Option 58: VLAN ID: this is sent as a suboption of option 43
Optionally, the DHCP offer can include the following parameters, which can also be configured locally
on the terminal or on the OXO Connect:
• Option 6: Domain Name Server (DNS primary and secondary)
• Option 15: Domain name
• Option 12: Host name (eg, ICTouch<MAC>)
• Option 42: SNTP server
• Option 120: SIP server (outbound proxy server address or name)
4.4.3.2.3.4 Configuring network parameters for static initialization
MMI allows to access and configure the following parameters (you must have administration rights to
modify static configuration):
• In the Network menu:
• DM (OXO Connect) URL: https://OXO Connect IP address:10443/dmcfg/
• DNS addresses
• Ethernet parameters: the LAN and PC Ethernet interfaces are by default configured in auto-
negotiation mode
• IP parameters
• Log parameters, allowing to define a syslog server for log reception
• Network parameters, allowing to:
• Enable and configure a DHCP User Class: this makes the set send the standard DHCP
option 77 (User Class, RFC2132) within the DISCOVER and REQUEST DHCP messages.
Using this option allows to define groups of terminals, and to attach these groups to different
and independent Com Servers.
• Define an SNTP Server address and refresh period
• Proxy host and port
• SIP parameters (read only)
• In Security menu:
• 802.1x parameters
• Certificates: not used
4.4.3.2.4 Configuring the user name and password in OMC
The user default password for a new user is defined at first installation. If need be, the administrator
can reset the user default password via the OMC
To modify the name and reset the password:
• In OMC, go to Users/Base stations List.
• To modify the user name: click the user in the list, modify the user name in the corresponding field
and click Modify
• To reset the user password:
• Click the user in the list and click Details to open the User window
• Click Password to open the Password window
• Click Reset to reset the password
and Devices
Note:
At reset, the password is set to the user default password value defined at first intallation.
4.4.3.2.5 Voice mail access
Using the IcsMessaging Web Service, a voice communication is automatically established between the
8082 My IC Phone set and the VMU to:
• Manage the messages (play, pause, stop)
• Delete one or all messages
• Record, send or cancel a new message
A VMU password can be required to access the voice mailbox from the local voice mail application.
The IcsUserProfile Web Service is used for password verification.
Note:
Password authentication is only requested when the parameter is validated
To validate password requirement:
In OMC:
1. Select Voice Processing
2. Select General Parameters
3. Verify Password required for mailbox consultation
4.4.3.2.6 Connecting optional equipment
4.4.3.2.6.1 Headsets
A headset can be used with 8082 My IC Phone sets.
By default the set is configured to detect headset connection. When the headset is plugged in, the
audio is sent to the headset. The hands-free key allows you to switch from handset, headset and
hands-free.
A Bluetooth® headset may be used.
If your headset is wired, plug it to the associated set connector (see: Figure 2), which can be any of the
following:
• The jack plug
• The set USB port
4.4.3.2.6.2 External station speakers
Any connector used for a headset can be used for external speakers.
Customize your set to take the external station speaker into account:
1. Touch the Settings button
Note:
According to system administration, this button may not appear. The availability of this option is determined by
the set configuration files. Contact your telephony and/or system administrator.
2. Select Devices > Audio
3. Select the connection of your choice (from Accessory device to Bluetooth® device)
4. Touch the field to access available values
5. Select Loudspeaker
6. If your device is not Bluetooth®, plug it to the corresponding connector
4.4.3.2.6.3 Traffic priority on the internal switch
The 8082 My IC Phone set includes an internal LAN switch.
This switch allows to connect a PC.
and Devices
The internal switch has three ports:

• A LAN port
• An internal port
• A PC port, to connect a PC to the LAN.
The internal switch privileges VoIP traffic over PC port traffic.
This switch has two waiting queues:
• The HPQ (High Priority Queue) to proceed all packets from the terminal
• The LPQ (Low Priority Queue) to proceed packets from the PC port
The switch proceeds seven HPQ packets for an LPQ packet.
Exception: packets from the PC port use the HPQ when they are tagged with a DSCP or 802.1p priority
and when the priority value is superior or equal to 4.
4.4.3.2.7 Resetting user data
To reset user data:
1. In OMC, go to Users/Base stations List > Details.
2. Click Reset.
The Reset window opens.
3. Select Reset User Data and click OK.
4. In the confirmation window, click Yes.
4.4.3.2.8 Rebooting an 8082 My IC Phone set
To reboot a set:
2. Click Reset button.
3. Select Reboot and click OK.
4.4.3.2.9 Displaying SIP connection current status
This feature allows the display of SIP connection status.
To display SIP connection status:
2. Read the SIP connection status (under the terminal's physical status).
The following table lists the different displayed status.
table 4.3: SIP connection status display
Displayed Status Meaning
Set not connected SIP phone disconnected from network / No SIP

registration request from the phone
SIP registration KO SIP registration request from SIP Phone rejec-

ted by OXO Connect
Set unregistered SIP phone unregistered from OXO Connect
and Devices
SIP registration OK SIP phone connected and successfully regis-

tered to OXO Connect
4.4.3.2.10 Terminal conference

8082 My IC Phone sets can handle their own local conference, involving up to 2 external members. In
this case, conference is not handled at call server level and the Conference parameter configured in
System Miscellaneous > Feature Design > Part 3 does not apply.
4.4.3.3 Ringing parameters

The set user can select different ringing tones for the different types of call or event.
To configure ringing tones:
1. Touch the Settings button
Note:
According to system administration, this button may not appear. The availability of this option is determined by
the set configuration files. Contact your telephony and/or system administrator.
2. Select Devices > Audio
3. Review/modify the following parameters:
On-site ringing Select the ringing for external calls
Off-site ringing Select the ringing for internal calls
Event ringing Select the ringing for calendar events
Special ringing Select the ringing indicating that the Bluetooth® handset is out of range
4.4.3.4 Video call parameters

The OmniPCX Management Console (OMC) is used to enable the video call support for the 8082 My
IC Phone sets. Once configured it is possible to make:
• Basic P2P video calls between 8082 My IC Phone (VHE-2) and any SIP phone with video support.
• Basic video calls from 8082 My IC Phone (VHE-2) over a SIP trunk
The configuration for video is carried out in two steps:
1. Generic SIP phone parameters for video calls are verified and modified if necessary, see Generic
video parameters on page 87
2. Each set is enabled, see Enabling video support for a 8082 My IC Phone set on page 89
4.4.3.4.1 Generic video parameters
The parameters in the table are generic (common) to all 8082 My IC Phone sets. They are accessed
from:
OMC -> Subscribers Misc -> Generic Parameters for SIP Phones -> Video Call parameters
Video Camera Country Frequency: defines the vertical scan frequency which is needed to avoid
flickering of video. This is same as the mains power frequency of the country. Default value for this
parameter is kept based on the target type (country) of the OXO Connect.
and Devices
Country Type Video Camera Country Fre-

quency (Default value in OMC)
Brazil Costa-Rica Guatemala Haiti Honduras Mexico Panama 60 Hz

Philippines Saudi Arabia Taiwan USA Venezuela Verizon
All others 50 Hz
Video Camera Refresh Cycle: defines the time interval between two full pictures refresh in seconds.
This parameter impacts the network bandwidth usage.If the value of this parameter is 0, it indicates no
refresh.
Video Differential Services: indicates the value of ‘Differential Services’ field in the IP header.
Video 802.1p: indicates the value of ‘802.1p’ field in the IP header.
Video Call Profile Level ID: indicates the value of ‘SDP’ field in IP header. This parameter encodes in
it, the information on profile, level and ID for video call encoding.
Video Call Encoding Profile: defines the profile that 8082 My IC Phone must use for video stream
encoding. This impacts the quality of the video.
Video Encoding Profile Low/Medium/High: defines the bandwidth used for low/Medium/High level
video encoding profile in kbps.
Video Call Packetization Mode: defines packetization mode (PM) among 3 values:
PM1 provides best quality video with reduced bandwidth. If the distant set does not support PM1, PM0
is used. PM0 should be avoided since it is not well supported on 8082 My IC Phone. NS is for
exclusive use of PM1. If NS is not supported by the distant, negotiation fails (no video)
All the video configuration parameters and their possible values are described in Table 3
table 4.4: Video parameters
OMC Parameter Common/Specific Default Value Possible Values

to 8082 My IC
phones
Video Support Specific to Terminal Enabled Enabled/Disabled
Video Camera Country Frequency Common Based on target 50 Hz / 60 Hz

country
Video Camera Refresh Cycle Common 2 [0 .. 2160]
Video Differential Services Common 5 [ 0 .. 63 ]
Video 802.1p Common 5 [0 .. 7]
Video Call Profile Level ID Common 0x42801E [0...0xFFFFFF]
Video Call Encoding Profile Common Medium Low/Medium/High
Video Encoding Profile Low Common 256 kbps 0 .. 65535]
and Devices
OMC Parameter Common/Specific Default Value Possible Values

to 8082 My IC
phones
Video Encoding Profile Medium Common 1000 kbps [0 .. 65535]
Video Encoding Profile High Common 2500 kbps [0 .. 65535]
Video Call Packetization Mode Common PM0 PM0 / PM1 / NS
4.4.3.4.2 Enabling video support for a 8082 My IC Phone set

The Video Support feature right is specific to each 8082 My IC Phone set. Video telephony is enabled
or disabled specifically for each set.
Note:
Enabling is mandatory to support Video calls (incoming or outgoing) for 8082 My IC Phone sets.
To enable/disable “Video Support”
OMC -> User/Base stations List -> 8082 MY IC Phone-> Details-> Features -> Feature Rights ->
Part 1
Video support: select the check box to allow video support on the 8082 My IC Phone.
4.4.3.5 SIP door phone parameters

Note:
If SIP door phone management is to be done with video support, refer to Video call parameters on page 87 to
enable video.
The generic parameters for SIP door phone management with 8082 My IC Phone can be modified at
OMC -> Subscribers Misc -> Generic Parameters for SIP Phones -> Door Phone Parameters
OMC Parameter Common/Specific to Default Value Possible Values

8082 My IC phones
Door Phone Name Common Doorcam STRING
Door Open Signal Common 55 STRING
Door Phone Name: defines the name that must be given for all SIP door phone terminals. Default
value for this parameter is 'Doorcam'.
The unique name defined with ‘Door Phone Name’ parameter is used by 8082 My IC Phone to identify
calls from SIP door phones.
Note:
The 'Door Phone Name’ parameter is case sensitive. SIP door phone names must be unique and not the same as
the ‘Door Phone Name’ parameter.
Door Open Signal: defines the DTMF code that is sent from 8082 My IC Phone to SIP door phone to
open the door latch. The default value for this parameter is 55.
4.4.3.6 Upgrading the software

The Alcatel-Lucent OmniTouch™ 8082 My IC Phone set software is upgraded during OXO Connect
software upgrade. Ensure the 8082 My IC Phone option is validated in the OMC-Software Download
window: refer to the section Downloading the Software in document [11].
and Devices
4.4.4 Reset to factory

4.4.4.1 Overview
The reset to factory is intended to cope with situations in which the administrator can no longer access
the set configuration because the set administrator password has been lost, and the set is configured
in static mode or uses a specific VLAN on the previous installation. Reset to factory is not needed
when a set is configured in dynamic mode: in this case, the set administrator password can be
changed through the device management tool.
The reset to factory enables to restore the set to the “Out of the box” initial status, except that the
software version remains unchanged on the set. It works during the set initialization. If initialization is
done, there is no other solution to reset sets to their factory settings.
The reset to factory performs the following actions:
• Restore the set administrator password to its default value
• Clean all user data and webapps
• Restore the configuration and settings to their default values
• Remove certificate data such as customer certificates and CTL, except ALE International default
certificate stored during manufacturing
• Store a message into Defense log to indicate a reset-to-factory has been done
• Reboot
Note:
Although the feature is not intended for end-users, it is available in user mode, as this feature is used when the set
administrator password has been lost, and therefore the administrator mode cannot be reached.
It is not possible to limit the availability of the feature for users and/or administrators by setting the appropriate
display-rights to the setting EnableResetFactory in the third configuration files, generated by the
Customizer.
4.4.4.2 Procedure
To perform the reset to factory on a set:
1. Restart the set
2. During set initialization (step 2 or 3), press Settings
3. Select Device > Reset
4. Set the Reset to factory option to Yes

Your are prompted to enter the administrator password required for the reset to factory.
The default administrator password is *tx8000#.
and Devices
5. Enter the administrator password, then press OK to confirm the reset to factory, or press Cancel to
cancel the reset.
• If the password is WRONG or Cancel is pressed; the set displays again the reset screen, the
choice selector is set to NO: without further action, the set will go on with normal startup.
• If the password is VALID, you are prompted to confirm the action:
6. Press Yes to confirm the reset to factory: reset to factory is performed and the set restarts
immediately.
Press No to cancel: the set displays again the reset screen, the choice selector is set to NO: without
further action, the set will go on with normal startup.
and Devices
4.5 4135 IP Conference Phone

4.5.1.1 Overview
The 4135 IP Conference Phone is a conference phone for IP telephony offering a host of innovative
features:
• OmniSound® 2.0 audio technology
• IP telephony for flexible and affordable telephony
• Management of lines during a call (calling new parties, creating a multi-party call, splitting a multi-
party call)
• Recording capability (requires an optional SD Card)
• Web interface for simple management of contacts, conference groups and settings (only available in
English language)
• Extra microphone connection for wider reception (option)
• Connection for wireless headset or PA system (option)
• Future-proof, can be upgraded with smart functions
and Devices

4.5.2.1 Keypad
Figure 4.21: 4135 IP Conference Phone Keypad
Each button provides access to letters and characters - including characters not shown on the button.
Press the same button repeatedly to use another character. To enter several letters accessible from the
same button one after the other, pause before entering the second letter. Press C to delete the last
character you have entered.
4.5.2.2 Display Screen
Line free (Before account name – telephone not registered)
Line connected (Before account name – telephone registered)
Line on hold (“HOLD” displayed on the screen – all calls on hold)
and Devices
Line (called party) busy
Own line put on hold by other party
Recording call
Secure connection
4.5.3 Commissioning
4.5.3.1 Overview
This module presents all the actions required for commissioning 4135 IP Conference Phone sets.
Figure 4.22: 4135 IP Conference Phone set layout
The following figure illustrates the connectors on the base of each set.
and Devices
Figure 4.23: 4135 IP Conference Phone set connectors
The 4135 IP Conference Phone is a SIP device which has no handset; it is dedicated to be used as
central for conferences.
Conferences are not managed by the system, but by the device itself. Up to four 4135 IP Conference
Phones can be connected to the OXO Connect.

This section describes how to commission the set in the two available commissioning types:
• Static: commissioning is manual on the set and on OMC
• Dynamic (DHCP): the set automatically retrieves its IP address and other parameters from a DHCP
server (OXO Connect DHCP server or an external DHCP server) . Complementary operations are
necessary on the set and on OMC
For static commissioning, operations are:
1. Configure the user in OMC, refer to Configuring the user by OMC on page 96
2. Connect the set to the LAN, refer to Connecting the set to the LAN on page 96
3. Configure the network parameters on the set, refer to Configuring network parameters for static
initialization on page 98
4. Export the server certificate from the OXO Connect: refer to Exporting the server certificate from the
OXO Connect on page 98
5. Upload the certificate on the 4135 IP Conference Phone
For dynamic commissioning, operations are:
1. Configure OXO Connect DHCP server, refer to Configuring OXO Connect DHCP server on page
97, or configure an external DHCP server, refer to Configuring an external DHCP server on page
97
2. Connect the set to the LAN, refer to Connecting the set to the LAN on page 96
and Devices
3. Configure the user name and password and consult the SIP password in OMC, refer to Configuring
the user name and password in OMC on page 98
4. Export the server certificate from the OXO Connect: refer to Exporting the server certificate from the
OXO Connect on page 98
5. Enter the SIP password through MMI, refer to Entering the SIP password through local MMI on
page 99
6. Upload the certificate on the 4135 IP Conference Phone
• For network configuration, any of the following must be implemented:
• In dynamic mode, a DHCP server must be configured
• In static mode, a free IP address must be available for the set
4.5.3.2.2 Configuring the user by OMC
This paragraph applies to OMC configuration of sets initializing in static mode. In dynamic (DHCP)
mode, the following operation is not mandatory but the server certificate must be exported from the
OXO Connect to the PC and can then be uploaded to the 4135 IP Conference Phone.
To create a 4135 IP Conference Phone:
1. In OMC, go to Users/Base stations List.
2. Select a No., IP access, enter a name and click the Add button.
3. Select IP terminal and click OK.
4. Select the newly created user in the list and select 4135 IP Conference Phone in the combo box
type.
5. Click the Modify button.
6. Click the newly created user to open the User dialog box.
7. Click the IP/SIP button and enter the MAC adress of the set in the IP Parameters tab.
8. If needed, in the SIP Parameters, click the SIP password reset button to get a new password.
4.5.3.2.3 Connecting the set to the LAN
Note:
the set is supplied via Ethernet, so make sure using a 802.3af standard-compatible switch.
3. Connect the RJ45 cable to the LAN.
• Select the initialization mode
• Initialize the 4135 IP Conference Phone set
4.5.3.2.4.1 Selecting the initialization type
The default initialization is Dynamic Alcatel.
To select the initialization type, refer to the table below.
and Devices
table 4.5: Initialization type selection
If Then the required initiali- Further information

zation mode is
You use OXO Connect Dynamic or Proprietary • Refer to Configuring OXO Connect DHCP
DHCP server Dynamic server on page 97
You use another Dynamic • Refer to Configuring an external DHCP

DHCP server server on page 97
You do not use a Static • Refer to Configuring network parameters for

DHCP server static initialization on page 98
• Obtain from your network administrator:
• An IP address for the 4135 IP Conference
Phone set
• The DNS addresses (primary ans
secondary)
• The VLAN ID (if VLAN is used)
• The IP address of the OXO Connect for
configuration files download
Note:
You need to know the set directory number.
4.5.3.2.4.2 Configuring OXO Connect DHCP server

The OXO Connect DHCP server is enabled by default during startup wizard installation. If enabled,
4135 IP Conference Phone sets automatically initialize in dynamic mode, when plugged to the OXO
Connect. In other words, 4135 IP Conference Phone automatically get their IP configuration from the
OXO Connect DHCP server.
If the OXO Connect DHCP server disabled, you can enable it as follows:
• In OMC, go to Hardware and Limits > LAN/IP Configuration > DNS/DHCP.
• In the ALU IP Phones: DHCP IP Range area, select the Enable check box.
• Modify the range of IP addresses if needed.
• Click the OK button to confirm your entries.
4.5.3.2.4.3 Configuring an external DHCP server
In Dynamic initialization (default value), the set selects the first DHCP offer, with a Vendor Specific
option corresponding to an Alcatel-Lucent server.
When initializing in dynamic mode, the set provides the following information in the DHCP Discover
message:
• Option 60: (vendor class identifier): alcatel.sip.0
• Option 55: list of requested options: subnet mask, router option, broadcast address, option 43
vendor specific info, server ID, renewal time, rebinding time and vendor class ID
Option 43 is vendor specific information, meaning that this option is defined for a specific client vendor
ID. In the DHCP offer, the data within Option 43 corresponds to the client vendor ID specified in the
request.
and Devices
In the case of 4135 IP Conference Phone sets, suboption 67 of option 43 provides the path of
configuration files on the ALE International.
The DHCP offer provides the following parameters:
• IP address
• Router IP address
• Subnet mask
• Option 66: IP address or name of the OXO Connect:10443, for example 192.168.12.34:10443
• Suboption 67 of option 43: the value of this sub-option must contain a string value set to https://
alize/dmcfg/
• Option 58: VLAN ID: this is sent as a suboption of option 43
Optionally, the DHCP offer can include the following parameters, which can also be configured locally
on the terminal or on the OXO Connect:
• Option 6: Domain Name Server (DNS primary and secondary)
• Option 15: Domain name
• Option 12: Host name (eg, ICTouch<MAC>)
• Option 42: SNTP server
• Option 120: SIP server (outbound proxy server address or name)
4.5.3.2.4.4 Exporting the server certificate from the OXO Connect
1. Go to OMC->Import/Export->Export Server Certificate.
The Export Server Certificate window is displayed
2. Click Browse button.
The Exportfile window is displayed:
• The File name field indicates server.crt. The file name can be modified as needed
• The Files of type field indicates Certificate Files
3. Specify the destination path for the export and click OK: The selected path and the certificate file
name are displayed in the Export Server Certificate window
4. Click the Export button: The certificate file is exported from the OXO Connect to the specified file
path in PC
5. Click the Return button
4.5.3.2.4.5 Configuring network parameters for static initialization
The following parameters must be entered through the MMI:
• IP address
• Subnet mask
• Gateway address
• DNS addresses
• VLAN use
• VLAN ID (if VLAN use is set)
• URL: provides the URL on the OXO Connect to download configuration file. The path on the OXO
Connect is /dmcfg/
• SIP password
4.5.3.2.5 Configuring the user name and password in OMC
To modify the name and password:
• In OMC, go to Users/Base stations List.
• Click the user in the list.
and Devices
• Modify the user name in the corresponding field and click Modify.
• Double-click the user in the list to open the User dialog box.
• Click on IP/SIP, go to SIP parameters tab to consult the SIP password.
4.5.3.2.6 Displaying SIP Connection Current Status


ted by OXO Connect

4.5.3.2.7 Entering the SIP password through local MMI

For static and dynamic initialization, enter the SIP password through MMI.
4.5.3.3 Upgrading the software

The 4135 IP Conference Phone set software is automatically upgraded during OXO Connect software
upgrade (there is no specific option to select in the OMC-Software Download window: refer to the
section Downloading the Software in document [11]).
The 4135 IP Conference Phone set software can also be upgraded manually through the MMI.
4.6 Generic SIP Phones

4.6.1 Commissioning
4.6.1.1 Overview
This module presents all the actions required for commissioning generic SIP sets.
The List of supported SIP Phones is available on the Alcatel-Lucent Applications Partner Program
(AAPP) web site.
4.6.1.2 Commissioning Generic SIP Sets

This section describes how to commission a generic SIP Set.
The following operations must be performed:
1. Configure the user in OMC, refer to Configuring the User in OMC on page 100
2. Connect the set, refer to Connecting the Set on page 100 and switch it on
and Devices
3. Configure the generic SIP set, refer to Configuring the generic SIP set on page 101, or configure the
OXO Connect DHCP server, refer to Configuring OXO Connect DHCP server on page 101.
• A free IP address must be available for the set
4.6.1.2.2 Configuring the User in OMC
To create a generic SIP set:
1. In OMC, go to Users/Base stations List.
2. Select a No., IP access and click on the Add button.
3. Select IP terminal and enter a Name.
4. Select the newly created user in the list and select Basic SIP Phone or Open SIP Phone in the
combo box.
See the different features relating to basic or open SIP modes: section Services offered on SIP
and DECT (IP-DECT) sets in document [3].
5. Click the Modify button.
6. Click the Details button. The User window is opened.
7. Click the IP/SIP button. The IP/SIP parameters window is opened.
8. In the SIP parameters tab, click the SIP password reset button. A new password is generated in
the SIP password field.
9. A virtual MAC Address is automatically generated but it can be replaced by the real MAC Address
of the SIP device.
Note:
The MAC Address must be unique and is used to identify the subscriber in the OXO Connect call handling (SIP
password is used for authentication).
10.Note this new password safely. It will be requested during the generic SIP set configuration
(Configuring the generic SIP set on page 101).
4.6.1.2.3 Connecting the Set
• Connect a generic SIP set to the LAN (Local Area Network)
• Connect the power supply
4.6.1.2.3.1 Prerequisites
None
4.6.1.2.3.2 Connecting a SIP set to the LAN
Note:
If the set is supplied via Ethernet, ensure you are using a 802.3af standard-compatible switch.
• Plug the RJ45 cable into the set's LAN connector.
• Connect the RJ45 cable to the LAN.
4.6.1.2.3.3 Connecting Power Supply (Optional)
To supply power via an AC/DC external adapter:
• Plug the appropriate cable from the adapter into the set's power supply connector.
• Connect the plug from the adapter to the mains power supply.
and Devices
4.6.1.2.4 Configuring the generic SIP set

The following parameters must be entered through the MMI or web interface when available:
• IP address (if no DHCP server is configured)
• Subnet mask (if no DHCP server is configured)
• Gateway adress (if no DHCP server is configured)
• DNS adresses (if no DHCP server is configured)
• VLAN use (if no DHCP server is configured)
• VLAN ID if VLAN use is set (if no DHCP server is configured)
• SIP username
• SIP password: this is different from the user password. It is randomly generated for each SIP
phone by the system and must be provided to the user in a secured way. It is used both for SIP
registration and for SIP authentication, since every SIP message must be authenticated.
Note:
The random password must be entered manually in MMI. It must be made of with letters and numbers only and
can be viewed/reset in OMC.
This password has been previously generated in: Configuring the User in OMC on page 100.
• SIP Phone Signal Source Port: default value is 5059. This value can be modified to any valid free
port.
• Registrar and proxy IP addresses: the OXO Connect IP address and the SIP port must be set to
value 5059
• Authentication Realm: OXO Connect IP address by default
• Registration interval: value greater than 120 seconds
• Transport protocol: the UDP protocol is preferred, TCP is used if the SIP packet length is greater
than the MTU value or if the remote SIP endpoint requests the TCP protocol
• Domain name: OXO Connect IP address by default
4.6.1.2.5 Configuring OXO Connect DHCP server
Generic SIP phones can use the OXO Connect DHCP server.
By default the OXO Connect DHCP server is not activated for generic SIP phones.
To activate the OXO Connect DHCP server:
1. In OMC, go to Hardware and Limits > LAN/IP Configuration > DNS/DHCP
2. In the Advanced DHCP IP range area, select the Enable check box.
3. Define the range of IP addresses ( Start IP address and End IP Address).
4. Click the OK button to confirm your entries.
For DHCP advanced configuration, refer to the section DHCP configuration in document [14].
4.6.1.2.6 Displaying SIP Connection Current Status
and Devices


ted by OXO Connect

4.7 4018 Phone Extended Edition

4.7.1.1 Overview
As part of the Proprietary professional range, IP phones are fully-featured with integrated IP
connectivity and telephony, bringing you the converged power of data and voice over IP (VoIP). In
addition to their optimized design, these terminals offer a gray display, wide band audio, superior
quality ring tones and hands-free communication.
The sets offer the following advantages:
• Instant Business Communications
• Optimized Ergonomics
• Superlative sound quality
• Unbeatable range of telephony features
4.7.1.2 Instant Business Communications

The Alcatel-Lucent IP Touch 4018 phone Extended Edition sets are always ready to provide the best
communication service whenever you need it, and to connect to other devices and applications in real-
time. You'll find them fast and easy to use, with feature buttons and interactive soft keys.
4.7.1.3 Optimized Ergonomics

Attractive, innovative and intuitively designed, these terminals operate on the same simple, user-
friendly ergonomics found in the best mobile phones and PDAs, so that you won't waste any time
accessing their powerful features and services. These phones come complete with:
• Display in different shades of gray
• Programmable feature buttons
• Up/down navigator
• Context-sensitive keys
4.7.1.4 Superlative sound quality

These phones provide the very best sound quality thanks to the following new enhancements:
• Compatibility with wide band audio, taking listening comfort to higher levels
• Full duplex hands-free speakerphone, including acoustic echo cancellation
• A comprehensive choice of standard ringtones and polyphonic melodies
and Devices
4.7.1.5 Unbeatable range of telephony features

These sets offer the full range of telephony services found in the OXO Connect PBXs, unbeatable in
terms of functionality, features, reliability and Quality of Service. These sets are available in all
countries where the associated IP-enabled OXO Connect system releases are launched.

4.7.2.1 Alcatel-Lucent IP Touch 4018 phone Extended Edition set description
This section describes the:
• Set features
• Set keyboard
• Set display
The following figure illustrates the Alcatel-Lucent IP Touch 4018 phone Extended Edition set.
Dialing
keypad OK
Exit/Home
2-way
navigator
Personal
key
Help
Message
Soft keys
End Redial Hands-free Volume

up/mute/down
Figure 4.24: Alcatel-Lucent IP Touch 4018 phone Extended Edition set
4.7.2.1.1 Set features

The features of the Alcatel-Lucent IP Touch 4018 phone Extended Edition set are as follows:
• Corded comfort handset
• Full duplex hands-free
• Wide band audio
• Standard ring tones and polyphonic melodies
• Display in shades of gray
and Devices
• Dialing keypad
• Fixed function keys
• Up/down navigator and OK key
• Programmable keys
• Ethernet LAN and PC connections
• Optical connectivity with external adapter
• Wall mounted kit [optional]
• Foot-stand 60° (“Big Foot”) [optional]
4.7.2.1.2 Set keyboard
The keyboard of the Alcatel-Lucent IP Touch 4018 phone Extended Edition set includes:
• A dialing keypad
• Function keys
• A navigator
Dialing keypad
The dialing keypad comprises 12 keys.
Function keys
The fixed function keys are described in the table below.
table 4.6: Fixed keys
Key Action
End Can be used to:

• terminate the current communication
• stop ringing for an incoming call
• end the current application (and return the
display to its default)
Hands–free (with green LED) Enables or disables the hands–free feature.

Short press activates the hands-free feature.
Long press on the hands-free key activates the
Group Listening feature.
The hands-free function is a full duplex function
with echo cancellation and attenuation.
Volume In OXO Connect, they adjust:

+ • the handset/headset volume in
communication mode
—
• the built-in loudspeaker volume
• the ringing level when the set rings
and Devices
Key Action
Redial • Short press: Automatically redials the last

number dialled.
• Long press: Displays a list of recently dialled
numbers. Use the up/down arrow keys to
scroll between numbers, and press the OK
key to redial the number currently displayed.
Message (with orange LED) Provides access to:

• voice-mail services
• mini-message services
Mute (with green LED) • When the set is in communication, this key
switches the set to mute mode (disabling the
set's microphone).
• When the set is not in communication, this
key allows an incoming internal call to be
answered in hands-free mode.
Personal/Dial by name • Short press: Provides access to the

personal address book.
• Long press: Provides access to the Dial by
name feature.
Exit/Home • Short press: Steps back one level in the

application.
• Long press: Exits the current application and
returns to the default display.
Help/Menu Menu
• Press once to access the set's menu. This
consists of 7 elements - use the up/down
arrow keys to move between menu elements.
• Press once followed by one of the keys 1 to 7
to access the corresponding element of the
menu.
• Press once followed by the OK key to access
the first element of the menu (Who Am I?).
Help
Press once followed by another key to obtain in-
formation on the function of that key. The possi-
bilities are:
• i + programmable key
• i + Message key
• i + Redial key
• i + End key
• i + Personal/Dial by name key
Programmable keys
and Devices
The programmable keys allow your preferred functions to be programmed (by an administrator), such
as call forwarding or a specific call number. These keys then provide quick and easy access to these
functions.
The programmable keys include:
• One personal key
• A set of 6 other programmable keys
Navigator
The navigator includes:
• A 2-direction navigation key
• A validation key (OK)
• An Exit/Home key (|<)
The Exit/Home key is used to exit the current application, or a long press will switch the display back to
its default. In edit mode, it can be used to delete characters.
4.7.2.1.3 Set display
The table below lists the characteristics of the display of the Alcatel-Lucent IP Touch 4018 phone
Extended Edition set.
table 4.7: Display of the Alcatel-Lucent IP Touch 4018 phone Extended Edition set
Characteristics Alcatel-Lucent IP Touch 4018 phone Extended Edi-

tion
Display Yes
Screen resolution 20 characters
Size of visible area 79 x 13 mm (3.11 x 0.51 inches)
Color Gray background
4.7.3 Commissioning
4.7.3.1 Overview
This module presents all the actions required for commissioning the Alcatel-Lucent IP Touch 4018
phone Extended Edition set.
The following figure illustrates the connectors on the base of the Alcatel-Lucent IP Touch 4018 phone
Extended Edition sets.
and Devices
PC connector LAN connector Power

connector
External ringer
connector
Handset connector
Figure 4.25: Alcatel-Lucent IP Touch 4018 phone Extended Edition connectors

• Connect the set
• Initialize the set
• Program keys
None.
4.7.3.2.2 Connecting the sets
• Connect an IP Touch set to the LAN (Local Area Network)
• Connect the power supply
None.
4.7.3.2.2.2 Connecting an IP Touch set to the LAN
3. Connect the RJ45 cable to the LAN itself.
4.7.3.2.2.3 Connecting power supply
The set can be supplied from two possible power sources:
• An AC/DC external adapter which is a 42V power supply
A female jack is used to connect the power adapter. .
and Devices
• Power over Ethernet (PoE)

The supply via Ethernet can be implemented using a 802.3af standard-compatible switch.
To supply power via an AC/DC external adapter:
1. Plug the appropriate cable from the adapter into the set's power supply connector.
2. Connect the plug from the adapter to the mains power supply.
Initialization starts.
• Choose the initialization mode
• Initialize the IP Touch set
The IP Touch set must be connected to the:
• LAN
• Power supply
4.7.3.2.3.2 Choosing the initialization mode
The default mode is Dynamic Alcatel mode.
To choose the initialization mode, refer to the table below.
table 4.8: Initialization modes
If Then the required initializa- And

tion mode is
You use OXO Connect DHCP Dynamic or Proprietary Dynamic • Refer to Table 2
server
You use another DHCP server Dynamic mode Refer to Table 2
You do not use a DHCP server Static mode • Refer to Table 2

• Obtain from your network
administrator:
• An IP address for the IP
Touch set
• The TFTP server address,
which is the IP address of
the PowerCPU EE board
embedding the VoIP
board
4.7.3.2.3.3 Initializing the IP Touch set

To initialize the IP Touch set, refer to the table below.
and Devices
Note:
In each of the three cases below, you can view the IP Touch set's software version after Step 2 by selecting
Version in the Main menu.
table 4.9: Initialization procedure
For an initiali- Procedure

zation that is
Dynamic Alcatel 1. If necessary, enable the OXO Connect DHCP server (in OMC, Hardware and
Limits > LAN/IP Configuration > DNS/DHCP)
2. Connect the power supply.
3. After initialization phase 2 is completed and before phase 5 starts, press i, then
the # key.
The Main menu appears.
4. If the set was previously in static mode, select IP Parameters from the Main
menu.
The IP Parameters menu appears.
5. Select Dynamic and press the OK key.
6. Save by pressing the # key.
7. Exit the Main menu by pressing the * key.
Dynamic mode 1. Connect the power supply.

2. After initialization phase 2 is completed and before phase 5 starts, press i, then
the # key.
3. If the set was previously in static mode, choose IP Parameters from the Main
menu.
4. Choose Dynamic and press the OK key.
5. Save by pressing the # key.
and Devices
Static 1. Connect the power supply.

2. Before initialization phase 5 starts, press i, then the # key.
3. From the Main menu, choose IP Parameters.
4. Choose Static and press the OK key.
5. Enter the following:
a. IP address
b. Subnetwork mask
c. Router address
d. TFTP server address
e. TFTP port (69)
f. CPU address
6. Enter the required VLAN details, as follows:
a. If required, select Use VLAN and then enter the VLAN ID number.
b. Ensure that Strict VLAN is set as required. It is selected by default; de-
selecting it allows you to use a DHCP server in another VLAN.
7. Save the above parameter values by pressing the # key.
The set restarts from phase 1 with the new parameters.
Note:
If an error message appears during initialization, disconnect the power adapter, then plug it in
again, so that the system restarts initialization.
4.7.3.2.3.4 Restarting initialization

If you want to change a parameter value, restart initialization, as detailed below.
To restart initialization:
1. Disconnect the IP Touch set from the power supply.
2. Reconnect the power supply.
3. Execute the initialization procedure as detailed in Table 2
4.7.3.2.4 Programming keys
This section describes how to program the programmable keys.
In fact, only the direct call key can be programmed (with a telephone number), which by default is the
sixth programmable key. However, the Personal/Dial by name key can be programmed in a similar way.
To program a key:
1. Press the i key followed by the required programmable key.
2. Press one key of the 2-way navigator (up or down).
3. Enter the telephone number to be associated with this programmable key.
4. Press OK. The set then goes back to its default display.
4.7.3.2.5 Relocating and retaining IP Touch sets
This section describes how to relocate and retain the same set.
In the procedure below, it is assumed that:
• there is one DHCP server
and Devices
• no VLAN has to be configured.

None.
4.7.3.2.5.2 Relocating and retaining the same set
To relocate and retain the same set:
1. Unplug the set.
2. Plug the set into a connector at its new location.
4.7.3.3 Rebooting the set

To reboot a set:
2. Click Reset button.
3. Select Reboot and click OK.
4.7.4 Maintenance
4.7.4.1 Overview
This module describes:
• The error and information messages that appear during the starting phase.
• The Ethernet link table.
4.7.4.2 Error and Information messages

The table below lists the error and information messages. It has the following format:
Short text = text displayed on the screen, in case of real error or for information.
Description = status/error description
table 4.10: Starting phase error messages
END Starting phase is terminated (successful or un-

successful)
STARTED Step started
SUCCESS Step successful
FAIL Step failed
RETRYING Retrying step
NO MAC ADDRESS No Ethernet MAC address stored in flash
DHCP NOT RESPONDING DHCP Server is not responding
and Devices
BAD IP ADDRESS IP address is incorrect
BAD ROUTER ADDRESS Router address is incorrect
ROUTER PING FAILED Router not responding to ping
BAD TFTP ADDRESS TFTP server address is incorrect
ADDRESSES MISMATCH Address, mask and router do not match
TFTP NOT RESPONDING TFTP server is not responding
TFTP SERVER ERROR TFTP server error
BAD FILE CONTENT Error found in downloaded file
FILE TOO LARGE File is too large (cannot be downloaded)
SAME VERSION FOUND The version retrieved is the same as the version
running
NEW VERSION FOUND New IP Touch software version found (download)
FLASHING Flashing in progress
FLASHING FAILED Failed to flash downloaded binary
TRYING ANOTHER CPU Trying next address from configuration file
NO ETHERNET LINK Ethernet link not connected (LAN port only)
initializing First text message after hardware reset and

copyright information
1/5 network start Phase 1 is running: the set is starting its network
interface
2/5 network setup Phase 2 is running: the set is looking for IP ad-
dresses
3/5 config download Phase 3 is running: the set is trying to get a

lanpbx file
4/5 binary download Phase 4 is running: the set is downloading a new

binary
5/5 connecting Phase 5 is running: the set is trying to talk to the

system
and Devices
4.7.4.3 Ethernet Link

By default, Alcatel-Lucent 8 series sets are configured to perform auto-negotiation on both ports (LAN
and PC). Provided that the PC and the LAN switch are also configured to perform auto-negotiation, this
is the best configuration for QoS improvement.
However, depending on the network configuration, it may not always be possible to leave the terminal
in auto-negotiation: link speed and duplex of both ports can be forced to determined values using the
supervisor menu:
• Plug in the set, as described: Commissioning the set on page 107.
• Once the set displays initialization, press i, then #.
• Use the navigation key to select Ethernet Links
• Modify data as requested
A configuration mismatch between the terminal and PC/LAN switch can lead to negative effects on the
voice quality:
• No link (or speed mismatch): 8, 9, 11 and 12
• Packet loss (or duplex mismatch): 2, 4, 7 and 14
Note:
Collisions are not detected by the device operating in full-duplex mode: packets from this device are never re-
transmitted if a collision occurs on them.
The following table lists all possible Ethernet port configuration combinations when connecting an IP
Touch set to an external device (switch on LAN side, PC on PC side). For each combination, the table
shows the link status: valid or invalid (duplex or speed mismatch), as described above.
table 4.11: Ethernet Link Combinations
Terminal Port External Device Port Link Status
1 auto-negotiation auto-negotiation Valid
2 auto-negotiation 100-FULL Invalid (packet loss)
3 auto-negotiation 100-HALF Valid
4 auto-negotiation 10-FULL Invalid (packet loss)
5 auto-negotiation 10-HALF Valid
6 100-FULL 100-FULL Valid
7 100-FULL 100-HALF Invalid (packet loss)
8 100-FULL 10-FULL Invalid (no link)
9 100-FULL 10-HALF Invalid (no link)
10 100-HALF 100-HALF Valid
11 100-HALF 10-FULL Invalid (no link)
12 100-HALF 10-HALF Invalid (no link)
and Devices
Terminal Port External Device Port Link Status
13 10-FULL 10-FULL Valid
14 10-FULL 10-HALF Invalid (packet loss)
15 10-HALF 10-HALF Valid
Note:
When the two ports of an Alcatel-Lucent IP Touch 4018 Phone or Alcatel-Lucent IP Touch 4018 phone Extended
Edition set are configured in auto-negotiation mode, if the negotiation has led to a 10 Mbps rate on the PC port and
a 100 Mbps rate on the LAN port, the Alcatel-Lucent 8 series set automatically tries to renegotiate a 10 Mbps rate
on the LAN port. This prevents congestion problems on the PC.
4.8 8029/8039 Premium Deskphones

4.8.1.1 Basic description
The available Digital Premium DeskPhones are:


4.8.1.3.1 Phone layouts
Although there are differences in the aspect and operation of these sets, their layout is identical, but for
the screen and number of available soft keys.
and Devices
Alarm LED
Dialing keypad
Corded handset
Fixed keys
Adjustable foot
stand (0° to 60°)
Alphabetic keyboard
Alt key
Space bar
Alarm LED
Add-on keys
Dialing keypad
Corded handset
Fixed keys
Adjustable foot
stand (0° to 60°)
Alphabetic keyboard
Alt key
Space bar
and Devices
4.8.1.3.2 Embedded hardware

An IVANOE2 Chip with ARM7TDMI RISC processor is included in 80x9 sets, associated with external
SRAM (256Kx16) and NOR Flash (512Kx16) memories.
4.8.1.3.3 Foot stand
All sets come with a 0° to 60° adjustable foot stand.
All sets come with a standard 3.5mm jack to plug a headset. They offer narrowband audio qualities.
All sets come in their standard version with a comfortable corded handset.
They all work in hands free mode at the user's request.
4.8.1.3.5 Screens
Characteristics of set displays are:
• 8039 Premium DeskPhone: black and white graphical display of 160 by 100 dots, with white
backlight
• 8029 Premium DeskPhone: black and white graphical display of 64 by 128 pixels with white
backlight
4.8.1.3.6 Keys
All sets come with a standard 12-key dialing keypad.
On all sets:
• Two fixed keys below the keypad:
• : the Start call key puts the set in hands free mode
• : the Stop call key allows to end a call and ignore an incoming call
• Sensitive (piano) keys are located above the black grid of the lower part of the set.
• mute sound
and Devices
• hold call. This is the default feature for F1 keys (but can be programmed with
another feature)
• transfer call. This is the default feature for F2 keys (but can be programmed with
another feature)
redial information
• information page (displayed on screen)
On 8029 Premium DeskPhone sets, four add-on keys, each with a LED, allow to customize each set
according to the user's needs. A paper label at the right of these keys allows to write down a brief
description of the feature programmed on the key.
4.8.1.4 Connecting optional equipment

4.8.1.4.1 Alphabetic keyboard
A standard (hot pluggable) optional keyboard is available for all sets in the following layouts:
• Azerty (FR)
• Qwertz (DE)
• Qwerty (international)
• Qwerty (Nordic)
If you change keyboard types, ensure it is plugged in before restarting the set.
4.8.1.4.2 External interfaces
On all sets, a 3.5mm jack connector allows to plug a headset to the phone.
and Devices
RJ9 connector
RJ11 connector for UA (alphabetic
link (to the PCX) keyboard)
SATA connector RJ9 connector

(for add-on modules 10, 40-keys or (corded handset)
Smart module)
Figure 4.28: External interfaces on the back of 80x9 sets
4.8.1.4.3 Additional key modules

On all sets, several add-on modules, connected via SATA (see: External interfaces on page 117), can
complete the standard number of programmed keys.
The available modules are:
• 10-key module (can be fastened to the set):
• 40-key module (on its own foot stand, placed next to the set)
• Smart-key module (on its own foot stand, placed next to the set)
and Devices
4.8.2 Commissioning
4.8.2.1.1 Physical connection
To connect the set to the OXO Connect:
1. Plug the RJ11 cable in the corresponding set connector on the back of the set
2. Plug the other end of the cable onto the UA board on which the set has been declared
The set starts initializing automatically.
If this is the first set initialization, or when there has been an upgrade of the PBX software version,
the set downloads binary and data files.
4.8.2.1.2 Connecting an Add-On module to the sets
Add-On Modules (AOMs) can be connected to sets. They are added to the right side of the set.
Three types of Add-On Module exist and provide keys associated with icons:
• Smart Display Module provides 14 keys with programmable LCD labels
4.8.2.1.2.1 Rules and restrictions
The following rules apply to the use of Add-On Modules:
• A maximum of three Add-On Modules of the types AOM10 and AOM40 can be connected to each
set, providing up to 120 additional keys.
• A maximum of three Smart Display Modules can be connected to each set, providing up to 42
additional keys.
• Add-On Modules of types AOM10 and AOM40 can be used on the same set, but a Smart Display
Module cannot be used in conjunction with an AOM10 or AOM40.
• If an AOM10 is used with other Add-On Modules, it must be connected as the last module on the far
right of the set.
4.8.2.1.2.2 Connecting Add-On Modules
To connect an Add-On Module:
1. Remove the tab located on the right side of the set.
2. Plug the Add-On Module's SATA connector into the set's SATA connector.
3. Insert the Add-On Module attachments into the appropriate holes located on the right side of the
set. (AOM10 only)
4. Screw the Add-On Module to the set. (AOM10 only)
and Devices
Note:
If the set is on when you plug in an Add-On Module, you must restart the set after connection.
4.8.2.1.3 Binary file download
To operate correctly, Digital Premium DeskPhones sets require binary files which must comply with the
PBX version and configuration. After system upgrade and each time a set initializes, version numbers
of binary files are verified to determine whether an update of these files is necessary.
When a file is downloaded to set, it overwrites any previously existing file.
Application download to a terminal can be heavy in terms of bandwidth and CPU resources. It is not
possible to upgrade all the terminals during initialization of the system.
4.9 4019 Digital Phone

4.9.1.1 Overview
This phone is part of the ALE International professional range. In addition to its optimized design, this
terminal offers a gray display, wide band audio, a choice of ring tones, and group listening.
The Alcatel-Lucent 4019 Digital Phone set offers the following advantages:
• Instant Business Communications
• Optimized Ergonomics
• Superlative sound quality
• Wide range of telephony features
4.9.1.2 Instant Business Communications

The Alcatel-Lucent 4019 Digital Phone is always ready to provide the best communication service
whenever you need it, and to connect to other devices and applications in real-time. You'll find it fast
and easy to use, with feature buttons and interactive soft keys.
4.9.1.3 Optimized Ergonomics

Attractive, innovative and intuitively designed, this terminal operates on the same simple, user-friendly
ergonomics found in the best mobile phones and PDAs, so that you won't waste any time accessing its
features and services. The phone comes complete with:
• Gray display
• Programmable feature buttons
• Up/down navigator
• Context-sensitive keys
4.9.1.4 Superlative sound quality

This phone provides the very best sound quality thanks to the following new enhancements:
• A group listening capability from its built-in speaker
• A comprehensive choice of standard ringtones and polyphonic melodies
4.9.1.5 Unbeatable range of telephony features

This set offers the full range of telephony services found in the OXO Connect PBXs from ALE
International, unbeatable in terms of functionality, features, reliability and Quality of Service. The set is
available in all countries where the associated OXO Connect system releases are launched. It is
compatible with OXO Connect release 4.0.
and Devices

4.9.2.1 Alcatel-Lucent 4019 Digital Phone set description
This section describes the:
• Set features
• Set keyboard
• Set display
The following figure illustrates the Alcatel-Lucent 4019 Digital Phone set.
Dialing
keypad OK
Exit/Home
2-way
navigator
Personal
key
Help
Message
Soft keys
End Redial Loudspeaker Volume

up/mute/down
Figure 4.29: Alcatel-Lucent 4019 Digital Phone set
4.9.2.1.1 Set features

The features of the Alcatel-Lucent 4019 Digital Phone set are as follows.
• Corded comfort handset
• Group listening through built-in loudspeaker
• Standard ring tones and polyphonic melodies
• Gray display
• Dialing keypad
• Fixed function keys
• Up/down navigator and OK key
• Wall mounted kit [optional]
and Devices
• Foot-stand 60° (“Big Foot”) [optional]

4.9.2.1.2 Set keyboard
The keyboard of the Alcatel-Lucent 4019 Digital Phone set includes:
• A dialing keypad
• Function keys
• A navigator
Dialing keypad
The dialing keypad comprises 12 keys.
Function keys
The fixed function keys are described in the table below.
table 4.12: Fixed keys of the Alcatel-Lucent 4019 Digital Phone set
Key Action
End Can be used to:

• terminate the current communication
• stop ringing for an incoming call
• end the current application (and return the
display to its default)
Loudspeaker (with green LED) Enables or disables the built-in loudspeaker.

This key activates the group listening feature.
Volume In OXO Connect, they adjust:

• + • the handset/headset volume in
• — communication mode
• the built-in loudspeaker volume
• the ringing level when the set rings
Redial • Short press: Automatically redials the last

number dialled.
• Long press: Displays a list of recently dialled
numbers. Use the up/down arrow keys to
scroll between numbers, and press the OK
key to redial the number currently displayed.
Message (with orange LED) Provides access to:

• voice-mail services
• mini-message services
Mute (with green LED) When the set is in communication, this key
switches the set to mute mode (disabling the
set's microphone).
and Devices
Key Action
Personal/Dial by name • Short press: Provides access to the

personal address book.
• Long press: Provides access to the Dial by
name feature.
Exit/Home • Short press: Steps back one level in the

application.
• Long press: Exits the current application and
returns to the default display.
Help/Menu Menu
• Press once to access the set's menu. This
consists of 7 elements - use the up/down
arrow keys to move between menu elements.
• Press once followed by one of the keys 1 to 7
to access the corresponding element of the
menu.
• Press once followed by the OK key to access
the first element of the menu (Who Am I?).
Help
Press once followed by another key to obtain in-
formation on the function of that key. The possi-
bilities are:
• i + programmable key
• i + Message key
• i + Redial key
• i + End key
• i + Personal/Dial by name key
Programmable keys
The programmable keys allow your preferred functions to be programmed (by an administrator), such
as call forwarding or a specific call number. These keys then provide quick and easy access to these
functions.
The programmable keys include:
• One personal key
• A set of 6 other programmable keys
Navigator
The navigator includes:
• A 2-direction navigation key
• A validation key (OK)
• An Exit/Home key (|<)
The Exit/Home key is used to exit the current application, or a long press will switch the display back to
its default. In edit mode, it can be used to delete characters.
and Devices
4.9.2.1.3 Set display

The table below lists the characteristics of the display of the Alcatel-Lucent 4019 Digital Phone set.
table 4.13: Display of the Alcatel-Lucent 4019 Digital Phone set
Characteristics Alcatel-Lucent 4019 Digital Phone
Display Yes
Screen resolution 20 characters
Size of visible area 79 x 13 mm (3.11 x 0.51 inches)
Color Gray background
4.9.3 Commissioning
4.9.3.1 Overview
This module presents all the actions required for commissioning the Alcatel-Lucent 4019 Digital Phone
set.
The following figure illustrates the connectors on the base of the set.
Phone line
connector
Handset connector
Figure 4.30: Alcatel-Lucent 4019 Digital Phone connectors

• Connect the set
• Program keys
None.
and Devices
4.9.3.2.2 Connecting the set

This section describes how to connect the set to the telephone system.
None.
4.9.3.2.2.2 Connecting the set to the telephone system
To connect the set to the telephone system:
2. Plug the RJ11 cable into the set's UA port/phone line connector.
3. Connect the RJ11 cable to a UA port in the telephone system.
4.9.3.2.3 Programming keys
This section describes how to program the programmable keys.
In fact, only the direct call key can be programmed (with a telephone number), which by default is the
sixth programmable key. However, the Personal/Dial by name key can be programmed in a similar way.
To program a key:
1. Press the i key followed by the required programmable key.
2. Press one key of the 2-way navigator (up or down).
3. Enter the telephone number to be associated with this programmable key.
4. Press OK. The set then goes back to its default display.
4.10 Input Method Editor

4.10.1 Operation
The Input Method Editor (IME) allows a user to input non-Latin characters on sets with a standard Latin
keyboard (with or without special markings on the keyboard).
This input method is used for dial by name, customizing programmed key names and editing text
messages and configuring the phone names on the Operator set.
The IME supports Latin, Cyrillic, Hebrew and Chinese characters. For input of Chinese characters, the
IME opens an input session. The type of character is associated with an input method:
Characters Input Method
Chinese - mainland China Pinyin, Latin
Chinese - Hong Kong Stroke, Latin
Chinese - Taiwan Zhuyin, Latin
Russian Cyrillic, Latin
Hebrew Hebrew, Latin
Note:
For the input methods of Pinyin, Stroke and Zhuyin, when the target country is Chinese, or Cantonese, or
Taiwanese, these 3 input methods should be used. If not, these 3 input methods are not used.
and Devices
For the input method of Cyrillic, there are no restrictions. When the current language is Russian, it can be used.
Opening an IME input session:
When one of the Chinese input methods is used, an input session starts when the user presses an
alpha key.
The following figure shows the schema of the IME input session. It appears on the bottom softkey line
of the set's screen display.
Figure 4.31: Open the IME input session
The softkeys and areas operate in IME as follows:

• The input area displays characters as the user enters them.
Note:
For Pinyin input method, Latin characters are displayed in the input area.
• The result area displays the list of candidate characters in the same character type as the input
method.
• The input method indicator shows the input method in use.
• The left softkey is used to toggle between input methods.
• The right softkey is not used.
The following screens show an example of the basic operation of an IME input session. In the example
the input method is Pinyin.
The following figure shows the IME after the user has entered the letters "yu".
and Devices
Figure 4.32: Opened IME session with entered letters
The letters “yu” is displayed in Latin character type in the input area of the IME. The input method
indicator shows the current input method is Pinyin. The result area lists candidate Chinese characters
for the input letters “yu”.
The way input characters are processed, the resulting candidate characters displayed, and the function
of special keys varies according to input method.
Closing an IME input session:
The IME input session closes automatically when no activity is detected from the user. Two timers
control this function. When the first timer, T1, expires, it closes the input session without clearing the
input and result areas. The second timer, T2, should be greater than T1. When T2 expires, it closes the
input session and clears the input and result areas. Both timers are reloaded every time the user
presses an alpha key. If the user presses an alpha key after T1 has expired, but T2 has not yet expired,
the input session is re-opened with the previous contents of the input and result areas.
The input session also closes when the user presses:
• OK (confirms character choice)
• RELEASE
• Back/Exit
Changing input methods:
The user can change the current input method to any which is configured on the set by pressing
+ ([alt] + [space]). An input method selector dialog box pops up, displaying the possible
input methods, as shown in the following figure.
and Devices
Figure 4.33: Change input method
In the pop-up dialog box, the user scrolls with [space] (while keeping [alt] pressed), and selects by
releasing [alt]. If the Latin or Cyrillic input method is selected, the IME input session closes because it is
not used by these input methods.
Note:
If the language is Russian, there are no input sessions for Cyrillic, after changing the input method to Cyrillic, it can
input Russian character directly on the alphabetic keyboard.
Alternately, when the current Input Method is Pinyin, the user can use the left softkey to toggle between
two input methods. In this example, if the user presses the left softkey, the current input method toggles
from Pinyin to Latin and the IME input session remains open, as shown in the following figure.
Figure 4.34: Toggle input method; example screen 1
Now the user can input Latin characters directly without closing the input session. The input method
indicator shows that the current input method is Latin. After one Latin character is entered ("U"), the
input session closes, although Pinyin is still available as the default input method.
To toggle back to Pinyin, the user presses the left softkey and the input session re-opens, as shown in
the following figure.
and Devices
Figure 4.35: Toggle input method; example screen 2
Input Method for programming a key name:

Each user can program the key name on the phone. In this case, the input session does not, however,
close automatically after the user presses OK to confirm a Unicode character. It is kept until the user
presses the Back/Exit key, followed by OK to save the key name.
Figure 4.36: Program a key name
Input Method for programming names on the Operator set:

Note:
It is possible to use Unicode - Chinese, Hebrew and Cyrillic -characters.
The administrator of OXO Connect can modify all the phone names via the operator set. This case is
the same as the one presented above - "Programming a key name". The input session will not close
automatically after pressed OK to confirm a Unicode character. It is kept until the user presses the
Back/Exit key followed by OK to save the phone name.
and Devices
Figure 4.37: Configure a phone name
4.11 Terminal downloading

4.11.1 Operation
4.11.1.1 Overview
The Digital Premium DeskPhones telephone sets contain software and data files that are pre-installed
in the factory
Data files include components such as fonts and ring tones, which may be country specific.
OXO Connect provides the facility for the software and/or data files embedded in the terminals to be
updated by the call server if the versions of the embedded files are different from the versions of the
equivalent files available in the OXO Connect system. In this case, the relevant files are normally
downloaded from the system to the terminal when the terminal is restarted.
Note:
New terminal software versions may become available in the system when the system is updated with new OXO
Connect software. Updates of the files embedded in the terminals may then be required.
4.11.1.2 Timing
The terminal download mechanism is activated when a terminal is restarted. During the restart phase,
the versions of the files embedded in the terminal are compared with the versions of the same files
available for download from the system. If the two versions of the same file are different, a download
request is sent to the call server. When the call server detects a download request from a terminal, the
terminal is entered into a queue of terminals waiting for downloads.
Note:
A terminal may also request a download during the restart phase if the files inside the terminal have been
corrupted, or if the previous download failed or was interrupted.
The user can delay a terminal download so that it is performed at a specified time (date and hour). This
allows terminal downloading to be performed at a convenient time, such as during business closing
hours or at weekends.
Other deviations from the normal download procedure are also possible:
• The user can specify that the next terminal download will be performed following the next software
swap (when the system switches to running the new software).
• The user can force a download, even if the versions of the embedded files are the same as the
versions of the equivalent files in the system.
and Devices
• The user can choose to forbid downloads, even if the versions of the embedded files are different
from the versions of the equivalent files in the system.
The timing of terminal updates is configured in the OMC tool, which presents the following options:
• No Downloading: There will be no updates to the files embedded in the terminals.
• Download after swap: New files will be downloaded to the terminals following the next software
swap.
• Delay Downloading at: New files will be downloaded to the terminals at the specified date and
time.
• Download immediately: New files will be downloaded to the terminals immediately (a forced
download).
4.11.1.3 Customization for 80x8s Premium DeskPhoneDeskPhones

The set customization is configured in the OMC tool and enables to customize set skin and melodies
for the latest proprietary DeskPhones. The customization feature requires a binary file to import
customized skins and melodies.
1. By OMC, go to Import/Export > File Management for Third Party Devices
2. From the File Management for Third Party Devices window, download the binary file
3. Go to Data Saving and Swapping > Terminal Downloading
4. Check the Customization field to enable set customization
For more information on Customization option, refer to OMC online help (Save / Backup Customer
Configuration > Terminal Downloading > Customization for DeskPhones)
4.11.1.4 Operation
During a terminal download, the following conditions apply:
• The terminal cannot be used (the call server puts the terminal out of service).
• The terminal must not be re-configured (with the configuration tools).
• If a problem occurs during a download, the download is attempted a second time. If the problem
persists, the terminal is put out of service.
• If a terminal download is not performed within a certain timeout period from the time of the
download request, the terminal is reset. See the note below.
• If two terminals share the same telephone resources, they cannot be updated simultaneously - the
downloads to the two terminals are performed sequentially.
Note:
If a timeout occurs during a download, you are advised to disconnect and then reconnect the terminal to the
system, so that the download procedure restarts.
4.11.1.5 Duration
The time taken to complete a terminal download depends on the number of terminals that are being
updated at the same time, as well as how and where the terminal is connected to the system, as
follows:
• The more terminals there are to be updated, the longer the expected wait for an individual terminal
to be updated.
• Downloads to terminals connected to extension cabinets take longer than to terminals connected to
the main cabinet.
• Downloads to terminals with shared system connections take longer than to terminals with
dedicated system connections.
and Devices
4.12 Add-on Module

4.12.1 LEDs and icons on AOM modules
4.12.1.1 Overview
Extension units, also called Add-on Modules (AOM), can be fitted to the phone sets. They provide
additional keys which can be configured as call keys, feature keys, and resource keys.
Some keys have their status indicated by icons or LEDs. For example, a blinking icon indicates that a
user action is required.
For feature keys, an active feature is indicated by a LED ON and if a user action is requested (for
example, message not read), the LED blinks slowly.
For resource keys, icons and LEDs provide information such as:
• indicates that the contact hears music (hold state)
• indicates that the communication concerns the user
• indicates an incoming call

• LED ON (fixed) indicates a busy state not activated by the user
• Slow blinking LED indicates a resource used by the user
• Fast blinking LED indicates that a user action is requested (incoming call or call hold)
4.12.1.2 LEDs and icons description

The table below displays the different icon and LED states that can be applied to the feature and
resource keys:
Logical states LED states Icon states
Feature keys:
Inactive feature OFF OFF
Active feature ON
Priority feature SLOW BLINKING
Resource keys:
Free OFF OFF
Own call FAST BLINKING
In use SLOW BLINKING
Exclusive hold FAST BLINKING
and Devices
Logical states LED states Icon states
Exclusive hold forgotten FAST BLINKING
Own recall (supervised call) FAST BLINKING
In call FAST BLINKING
Busy ON
Common hold FAST BLINKING
Common hold forgotten FAST BLINKING
4.13 V24/CTI Interface Module

4.13.1.1 Overview
The V24/CTI Interface Module allows a Data Terminal Equipment (DTE) to be connected to the OXO
Connect, via a UA link, by means of an RS232 serial link (CTI port) or a V24 link.
The V24/CTI Interface Module can be used alone or combined with Digital Premium DeskPhones.
CTI port
The RS232 serial link carries signalling (up to 9600 bit/s) and allows telephone operations such as call
management and call monitoring. The audio part is carried out by the associated dedicated set.
V24 port
The V24 port is considered as a DCE and provides a capacity of 19200 bit/s (ECMA 102) for an
asynchronous V24 transmission. The electrical interface complies with the V28 recommendation of the
CCITT.
and Devices
V24: up to 19200 bit/s

CTI: up to 9600 bit/s
or
DTE
PCX DCE
CTI V24
UA link UA link
UA UA
V24/CTI 9 Series Set

Interface Module
UAI Board
(or MIX board)
Figure 4.38: V24/CTI Interface Module Configuration Example
4.13.1.2 Compliant Standards

4.13.1.2.1 Safety Requirements
• EN60950: European requirements
• UL 1950: US requirements
• CAN/CSA-C22.2 No 950-95: Canada
4.13.1.2.2 ECM
• EN55022: Limits and methods of measurement of radio interference characteristics of information
technology equipment
• EN55024: Limits and methods of measurement of immunity characteristics of information
• FCC part15: US requirements
4.13.1.2.3 V24 & CTI
• CCITT Rec.: V24,V28, V25bis, V54, V110
• Hayes protocols
• ECMA 102: Attachment requirements for pan-European approval for connection to PSTN of TE
(excluding TE supporting the voice telephony service) in which network addressing, if provided, is
by means of DTMF signalling
4.13.1.2.4 Environment Classes
• ETS 300 019: Environmental conditions and tests for telecommunication equipment:
• Part 1-1: Storage
• Part 1-2: Transportation
• Part 1-3: Environmental conditions
4.13.1.2.5 Eco Design
• ISO 14040: Environmental management – Life cycle assessment – Principles and framework (1997)
• RoHS
and Devices
4.14 AP Interface Module

4.14.1.1 Overview
The AP Interface Module (Analog Peripheral) allows an analog device such as fax, modem, minitel,
answering machine to be connected to the OXO Connect via a UA link.
Digital Set
to Mains
Fax
PCX
Digital Link
UAI Board
(or MIX Board)
AP Interface Module
Digital Link
Figure 4.39: Example of Configuration with an AP Interface Module
AP Interface Module can be used alone or combined with Digital Premium DeskPhones.
AP Interface Module powers the analog device (DTMF signalling, ringer) and, to do this, requires an
external power supply (230V AC/30V AC adapter). In this document, this set is called Z set.

4.14.1.2.2 ECM
4.14.1.2.3 Analog Transmission
• ETS 300 439: Business TeleCommunications (BTC); Transmission characteristics of digital Private
Branch eXchanges (PBXs)
• TBR21: Attachment requirements for pan-European approval for connection to PSTN of TE
(excluding TE supporting the voice telephony service) in which network addressing, if provided, is
by means of DTMF signalling
and Devices

ISO 14040: Environmental management – Life cycle assessment – Principles and framework (1997)
4.15 S0 Interface Module

4.15.1.1 Overview
The S0 Interface Module allows an S0 bus (2 B + 1 D channels) to be connected to the OXO Connect
via a UA link. This bus allows S0 terminals (S0 sets, PCs equipped with an S0 interface, Fax G4,
modem, etc.) to be connected.
The S0 Interface Module can be used alone or combined with Digital Premium DeskPhones.
S0 set S0 Terminal
Digital set
S0 Bus
to Mains
(Option)
PCX
digital Link
UAI Board S0 Interface Module

(or MIX Board)
digital Link
Figure 4.40: Example of Configuration with an S0 Interface Module
The S0 module provides an S0 bus supplying power. An external power supply (230V AC/48V DC
adapter) is required.
There are two possible operating modes on the S0 bus:
• Non permanent layer: layer 1 must be set up by the calling end (PCX or terminal) at the start of
each call; layer 1 is shut down at the end of the call
and Devices
• Permanent layer: operation of the S0 bus depends on the direction in which the initial call was set
up:
• If the call was set up from the PCX to the terminal, layer 1 is kept when the call ends.
• If the call was set up from the terminal to the PCX, layer 1 is shut down at the end of the call. It
must be set up again for the following call. If operation is incompatible with the terminal used,
there are two possible solutions: Either layer 2 is kept, this prevents layer 1 being shut down, or,
layer 1 is set up from the PCX by making a call to the terminal. The call does not need to get
through.

4.15.1.2.2 ECM
4.15.1.2.3 ISDN
• ETS 300 012: Basic user-network interface layer 1 specification and test principles
• TBR3: Attachment requirements for terminal equipment to connect to an ISDN using ISDN basic
access
• ETS 300 047: Basic access-safety and protection
• I.430: Basic user-network interfaces layer 1 specification
ISO 14040: Environmental management – Life cycle assessment – Principles and framework (1997)
4.16 500 DECT Handset

4.16.1.1 Overview
The 500 DECT just as the other DECT handsets, is particularly useful for users moving within the
workplace.
The 500 DECT offers:
• Access to most of the added value OXO Connect telephone features.
• Enhanced usability with:
and Devices
• Robust design with inductive charging

• IP 54 compliance (water and dust resistant)
• DECT handset for PWI (alarm button, man down alarm, no movement detector, shock detector)
• Improved ergonomics
• Integrated bi-antenna
• Backlight display
• Improved quality of audio reception
• Vibrating feature
• MWI (Message Waiting Indication)
• Good autonomy (Li-Ion technology)
• Belt clip
The 500 DECT operates with Advanced GAP (AGAP)
The 500 DECT offers:
• A large clear screen accepting images, icons and text
• A simplified functional organization that allows the user to quickly access each of the mobile's
functions
All main operations can be performed on the mobile by use of a single key for navigation (four
directions) and confirmation.
You can take advantage of special DECT features, such as:
• "Roaming", which allows the user to receive or make a call no matter where he/she is relating to the
base station radio coverage zone
• Change of the transmission channel on the base station to portable link during a conversation due
to a change in propagation conditions
• "No-break transfer" from one base station to another when moving during a conversation. This shift
is completely transparent for the user
The set implements specific DECT features, such as:
• Continuous evaluation of different base station levels in order to select the most appropriate base
station for call setup
• Selection of radio transmission channel during call setup
• Continuous listening for paging messages, transmitted by all base stations, when an incoming call
arrives. The set establishes a radio communication with the most appropriate base station (as it
does for an outgoing call)
• Support of the alarm feature, allowing isolated workers to be located with specific alarm server
Note:
Date/Time infomation is received from OXO Connect whenever 500 DECT registers with OXO Connect.
4.16.1.2 Physical Characteristics
Features 500 DECT
Loudspeaker Yes
Multiline management Yes
Dial-by-name Yes (local and central directory)
and Devices
Features 500 DECT
Headset connection Yes

(standard wiring)
Backlight display Yes
Backlight Keypad Yes
Vibrator Yes
Navigation/confirm dual-function key Yes
Battery pack Yes
Color Black
Explosion proof No
Belt clip Yes
Talk time Up to 8 hours
Standby time Up to 100 hours
Charging time Around 9 hours
4.16.1.2.1 Environmental Constraints

Storage, transportation and 500 DECT environment comply with the following standards:
• ETS 300 019 1.1, Storage, Class 1.2: Weather protected, Not temperature controlled locations
• ETS 300 019 1.2, Transportation, Class 2.3: Public transportation
• ETS 300 019 1.3, In Use, Class 7.2: Portable use, Partly Temperature controlled locations
4.16.1.2.1.1 Operation
• Temperature: to achieve optimum reliability, the ambient temperature must be between -10°C and
+45°C.
• Relative humidity: relative humidity must be between 5% and 95% (without condensation)
4.16.1.2.1.2 Storage
• Temperature: temperature must be between -25°C and +55°C
• Relative humidity: relative humidity must be between 10% and 100% (without condensation)
and Devices
4.16.1.3 Description of a Set
Figure 4.41: 500 DECT Presentation
This set provides:

1. A colored LED indicator:
• This LED indicator can be customized by the user and can indicate any of the following:
• Missed call
• Man down
• Low battery
• Alarms, etc...
• The available colors are:
• Red
• Green
• Orange
2. Display screen with status and call icon
3. Volume adjustment keys
4. Red lateral key: triggers an Alarm Call when the emergency call feature is enabled
and Devices
5. Call management Key (softkey)

6. Answer the call
7. Headset socket
8. Back light screen: the screen switches automatically after a few seconds of inactivity
9. Navigation/confirm dual-function key
10.Call management key (softkey)
11.Call management key
12.Silent mode key
13.Microphone
4.16.1.4 Keypad
4.16.1.4.1 Main keys
KEY USE
Allows to
• Activate/deactivate the loudspeaker
• Redial from the call log
• Lock/unlock the keypad
Allows to select a function in the Menu and provides access to all available
functions:
• Personal directory
• Company Directory
• Call log
• Handset settings menu
Erase a character
Allows to:
• Validate an action
• Access to shortcuts for navigation
• Activate/deactivate the loudspeaker
• Access the personal directory
• Switch the screen back on
Note:
the four navigator keys are programmable.
Allows to:
• Answer an incoming call
• Start a call
• Switch between two calls (broker call)
Allows to:
• Switch the set on/off
• Hang up
• Return to first screen/to previous menu
• Switch off ringer
and Devices
KEY USE
Silent mode (long pressing)
4.16.1.4.2 Call Icon Display
ICON USE ICON STATUS
Incoming call Icon displayed: Indicates an incoming call.
Outgoing call Icon displayed: Indicates an outgoing call.
Loudspeaker ac- Icon displayed: Indicates the loudspeaker activation.

tivated
Silent mode acti- Icon displayed: Indicates the silent mode activation (loudspeaker off)
vated
Silent micro- Icon displayed: Indicates that the microphone is muted.

phone activated
4.16.1.4.3 Status Icon
ICON USE ICON STATUS
Battery fully charged (75% - 100%)

Battery Battery half charged (33% - 75%)
Status Indi-
cator Low battery (0% - 33%)
Battery completely discharged (0%)
Icon displayed: Indicates the presence of unread text messages.

New text
Message Note:
Text messages are not supported on IBS
and Devices
New fil- Icon displayed: Indicates the presence of filtered calls.

tered mes-
sage
Icon displayed: Indicates the silent mode activation.

Silent
mode acti-
vated
Radio re- Indicates the received radio signal level.

ception in-
dicator
Icon displayed: Indicates that an appointments reminder is programmed.

Appointe-
ment re-
minder
icon displayed: Indicates the keypad is locked.

Keylock ac-
tivation
icon displayed: Indicates a missed incoming call.

Missed call
4.17 8212/8232/8242/8262 DECT

4.17.1 Overview
The 8212 DECT, 8232 DECT, 8242 DECT, and 8262 DECT handsets offer easy-to-use, cost effective
and reliable voice communication solutions that address the mobility needs of evolving business
environments.
They can offer simple and efficient voice communications, enhanced usability and compatibility with the
existing base station portfolio. They also offer all of the OXO Connect value-added voice services (such
as dial-by-name and multi-line management) that are supported by fixed desk phones.
and Devices
8212 8232
DECT DECT
Figure 4.42: 8212 DECT/8232 DECT handset
The 8212 DECT is available in GAP mode for IBS-DECT or IP-DECT sub-systems.
8242 DECT and 8262 DECT sets are very much alike in their appearance, but 8262 DECT sets offer
more advanced features.
and Devices
8242 DECT 8262 DECT
Figure 4.43: 8242 DECT/8262 DECT handsets
The 8262 DECT is available in A-GAP mode for IBS-DECT sub-systems only.
4.17.2 Key benefits

The key benefits of these handsets include:
• Infrastructure investment protection (compatibility with deployed base stations)
• Excellent voice quality and business telephony features throughout the workplace contributing to
improved user responsiveness and productivity
• One Worldwide product
• Automatic band switching for cruise ship application
• Green friendly:
• Economy mode with automatic low radio emission power (25 mW)
• Energy Star™ compliant
• Low power mode (50 mW) for environments such as nuclear facilities
• Long battery life
• Antenna diversity
• Direct micro USB charging
• Notification & Location based services:
• Location alarm signal when alarm triggered to help locate user ¬ r ¬
Personal protection features & Location requires an external server.
• up to 4 notification call types from server
• Alarm button (8242 DECT/8262 DECT)
• Task monitoring can be signaled by handset to central server (Hospitality, healthcare,
Warehousing…)
and Devices
4.17.3 Key features

The key features for the 8212 DECT/8232 DECT/8242 DECT/8262 DECT sets include:
• Advanced GAP (AGAP) protocol
• CAT-iq
• Lightweight, ergonomic design and intuitive operation
• Color display, backlight, vibrator
• Speakerphone and mute
• Headset connection
• Bluetooth 3.0 support (8242 DECT/8262 DECT)
• Loudspeaker/mute during call
• Status led (missed calls, Battery status)
• Received messages audio notification
• Headset jack (3.5 mm)
4.17.4 Location
Designed as a high-end business terminal, the 8242 DECT/8262 DECT terminals provide notification
and location capabilities in addition to a one-button alarm function. With these features, the 8242
DECT/8262 DECT meet the needs of hospitality, healthcare and any other professional environments:
• Triangulation with up to 4 DECT base stations
• Data transmitted with Notification messages
• External server required
• Location Audio signal
4.17.5 Technical specifications

4.17.5.1 Mechanical Characteristics
8212 DECT 8232 DECT 8242 DECT 8262 DECT
Dimensions height x width x depth 5,31 x 1,61 x 5,19 x 2.00 x 5.59 x 2.00 x 5,31 x 1,61 x
0.98 in 0.90 in (132 x 0.90 in. (142 x 0.98 in
51 x 23 mm) 52 x 23 mm)
(135.3 x 41.9 x (135.3 x 41.9
25 mm) x 25 mm)
Weight 6.06 oz (172g) 3.88 oz, 110 4.76 oz, 135 6.06 oz (172g)
grams grams
Color Black black black Black
Graphic display 1,44 in (36.5 1,4 in, 65k col- 2.4 in.; 65k 2.4 in. (60,95
mm) ors, 128 x 128 colors; 320 x mm)
pixels 240 pixels
resolution 128 resolution:
x 128 pixels 320 x 240 pix-
els
64k colors
65k colors
Display backlight White White White White
and Devices
8212 DECT 8232 DECT 8242 DECT 8262 DECT
Keypad backlight Blue Blue Blue Blue
Hands-free, mute Yes Yes Yes Yes
Vibrator No Yes Yes Yes
Headset: Jack 3.5 mm, TRSS com- Yes Yes Yes Yes
plian
LED status indication 3 colors; Red/ 3 colors; Red/ 4 colors: Red/ 4 colors: Red/
Orange/Green Orange/Green Yellow/Blue/ Yellow/Blue/
Green Green
Ring tones: 6 user selectable poly- Yes Yes Yes Yes

phonic with 4 steps volume control,
meeting mode
Belt clip standard clip standard clip standard clip standard clip
swivel (option) swivel (option)
Charger Charging on Charging on Charging on Charging on

desktop charg- desktop charg- desktop desktop
er or Micro er or Micro charger or Mi- charger or Mi-
USB type B USB type B cro USB type cro USB type
plug plug B plug B plug
• Handset MMI languages: English, French, German, Spanish, Italian, Dutch, Portuguese, Danish,
Swedish, Norwegian, Finnish
• System languages: Communication server dependant, 11 languages in GAP/CAT-iq mode
4.17.5.2 Power
Charging on desktop charger or Micro USB type B plug.
Battery pack:
• Li-Ion, easily replaceable, 1100 mAh
• Talk time: up to 11 hours for the 8212 DECT set, up to 20 hours on all other sets
• Standby time:
• 8212 DECT: up to 113 hours
• Charging time: less than 9 hours for the 8212 DECT set, less than 3 hours for all other sets
4.17.5.3 Radio specifications

• DECT
• Frequency range:
• DECT Europe – 1880-1900 MHz
• DECT 6.0 (NA) – 1920-1930 MHz
• DECT Latam – 1910-1930 MHz
and Devices
except Brazil 1910-1920 Mhz

• DECT Asia - 1900 MHz – 1906 MHz
• Hand-over: Bearer, Connection HO
• Out of coverage signaling
• Antenna diversity
• Automatic band switching for cruise ship applications (requires IP-DECT)
4.17.5.4 Registration
• Up to four systems
• Manual selection
• Automatic selection
• Automatic band switching
4.17.5.5 Audio codecs
8212 DECT 8232 DECT 8242 DECT/

8262 DECT
G726 X X X
G722 Wide Band Ready X
4.17.5.6 Features
• Call by name:
• Local & system directory
• Call log (GAP/CAT-iq mode):
• All, Answered, Dialed, Missed
• Up to 50 call logs
• Contacts (GAP/CAT-iq mode):
• Name, up to four numbers per contact
• Up to 50 contacts without SD card
• Hands-free
• Microphone mute
4.17.5.7 Environmental
For all sets:
• Operation: ETS 300 019 part 1-7 class 7.2
Operating temperature: -10°C to +45°C, (14 to 113°F) ETS 300 019 part 1-7 class 7.2
• Storage: ETS 300 019 part 1-1 class 1.2
Storage temperature: - 25°C to +55°C (-13 to +131°F) ETS 300 019 part 1-1 class 1.2
• Transportation: ETS 300 019 part 1-2 class 2.3
• IP Class: IP40 (EN 60529)
4.17.5.8 Serviceability
For all sets:
• Site survey tool
• Diagnostic mode
and Devices
• Syslog mode
• Download tool
4.17.5.9 Software management tool

• Download tool
• Flash loader (PC application) - 8232 DECT only
• Parallel FW Update (PFWU tool) - 8242 DECT/8262 DECT only
4.17.5.10 Regulatory
Requirements or norms 8212 DECT 8232 DECT 8242 DECT 8262 DECT
EU Directive
99/5/EEC (R&TTE) X X X X
2006/95/EC (LVD) X X X X
2004/108/EC X X X X
2006/32/EC (Eco Design) X
2009/125/EC (Eco design) X X
RoHS 2011/65/EU X X X X
Safety
IEC 60950-1 X X X X
EN 60950-1 X X X X
UL 60950-1 X X X X
CAN/CSA-22.2 No 60950-1 X X X X
EMC & Radio
EN 301 489-1 X X X X
EN 301 489-6 X X X X
IEC/EN61000-4-2 X X X
Level3 criteria B
IEC/EN61000-4-3 X X X X
Level3 criteria A
FCC 47CFR part 15 subpart D X X X X
IC RSS-213 X X X X
and Devices
DECT
EN 301 406 (TBR6) X X X X
EN 300 176-2 (TBR10) X X
EN 300 175-8 (DECT audio) X X
TBR22 X X
ETSI TS 102 841 (security) X X
DECT security certification program ste- X X

pA
DECT security certification program X X

stepB
Bluetooth : (Q4 2014) Headset profile

V3.0
EN 301 489-17 X X
EN 300 328 Radio X X
RF AS/NZS4268 X X
FCC part15-C X X
RSS-210 X X
SAR
EN 50360 X X X
EN 50361 X
FCC OET Bulletin 65 X X
SAR value: 0,102W/kg X
IEE 1528 X X X X
RSS-102 X X X
Audio, Hearing Aid
47CFR Part 68 X X X X
Canada CS-03 X X X X
ANSI/TIA/EIA-504 X X
and Devices
Australia: ACIF S040 X X
Telecom
EN 301 406 (TBR6) X X X
FCC 47CFR part 15 subpart D X X
IC RSS-213 X X
EN 300 176-2 (TBR10) X X
EN 300 175-8 (DECT audio) X X
ETS 300 245-2 X X
TBR22 X X
ETSI TS 102 841 (security) X X
ES 202 738 (Group listening) X X
Local regulations
Australia: ACIF S004 X X X X
USA/Canada: FCC 47 part 68 X X X X
New Zealand: PTC200 X X X
Acoustic shocks
UL 1950, ETS 300 245-2 X X
UL 60950-1 Annex NAD X X
EG 202 518 X X
4.17.6 Accessories
The available accessories include:
• Desktop charger: Charges one handset (with USB cable)
• Power supply: Europe, AR, US, UK, Australia plugs
• Spare battery
• Spare belt clip
• Swivel clip
• Vertical pouch
• Horizontal pouch
• Download tool
• Wired headset
• Bluetooth headset (up to four connected audio devices) - 8242 DECT/8262 DECT sets
and Devices
4.18 PIMphony Reflexes

For more information, you can also consult the PIMphony documentation supplied with the CD
ROM.
The standard OXO Connect offering includes an integrated CTI server (TAPI 2.0) that opens up a
broad range of third party CTI applications.
PIMphony Reflexes is a PC-based workstation equipped with the following PIMphony applications:
• PIMphony Basic (free of charge)
• PIMphony Pro (requires a software key)
• PIMphony Team (requires a software key)
PIMphony Basic PIMphony Pro PIMphony Team
Complete set of telephony fea- YES YES YES

tures
Centralized call log YES YES YES
Integration of Contact Handlers YES YES
"Visual Mailbox" interface YES YES
Unified messaging YES YES
Supervision features YES
Assistant Feature YES
For more information about the "Visual Mailbox", interface, consult " Visual Mailbox Interface" in the
"Integrated Voice Server" section.
They are installed from the CD-ROM provided in each system.
PIMphony Pro and PIMphony Team are supplied on a Try and Buy basis. The user can test both
applications free of charge for 2 months.
If PIMphony is emulating an IP workstation, it can be used via a USB or Bluetooth® handset.
and Devices

Alcatel-Lucent Network

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

Alcatel-Lucent Network

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent OmniPCX Enterprise

Release 12.1 - September 2017

8AL91000USAH - Ed. 01 - September 2017 - System Services 3/458

4.2.2 Duplication on Common Hardware and Appliance Server............................................. 43

8AL91000USAH - Ed. 01 - September 2017 - System Services 4/458

8AL91000USAH - Ed. 01 - September 2017 - System Services 5/458

7.1 Detailed description.............................................................................................................. 102

8AL91000USAH - Ed. 01 - September 2017 - System Services 6/458

8.4 Cabling instructions............................................................................................................. 120

8AL91000USAH - Ed. 01 - September 2017 - System Services 7/458

9.2.1 Configuration 1................................................................................................................................... 135

8AL91000USAH - Ed. 01 - September 2017 - System Services 8/458

10.2.6 Tones, Voice Guides, and On-hold Music.............................................................................155

11.1 Detailed description.............................................................................................................. 159

8AL91000USAH - Ed. 01 - September 2017 - System Services 9/458

8AL91000USAH - Ed. 01 - September 2017 - System Services 10/458

8AL91000USAH - Ed. 01 - September 2017 - System Services 11/458

14.1.4 Passive FTP Connection...............................................................................................................192

8AL91000USAH - Ed. 01 - September 2017 - System Services 12/458

8AL91000USAH - Ed. 01 - September 2017 - System Services 13/458

15.4.53 United Kingdom (UK)...................................................................................................................... 254

8AL91000USAH - Ed. 01 - September 2017 - System Services 14/458

16.2.6 Recognizing and selecting voice guides................................................................................282

8AL91000USAH - Ed. 01 - September 2017 - System Services 15/458

16.8.9 Adding a language............................................................................................................................321

8AL91000USAH - Ed. 01 - September 2017 - System Services 16/458

8AL91000USAH - Ed. 01 - September 2017 - System Services 17/458

8AL91000USAH - Ed. 01 - September 2017 - System Services 18/458

20.5.9 License: “10 Mobile users” (lock 175).....................................................................................398

8AL91000USAH - Ed. 01 - September 2017 - System Services 19/458

22.2.8 Interaction between DECT/PWT and Synchronization.................................................. 436

22.4 Configuration procedure..................................................................................................451

8AL91000USAH - Ed. 01 - September 2017 - System Services 20/458

table 1.1: OmniPCX Enterprise Documentation

Documentation title Part number

[1] System Services 8AL91000xxyy

[2] Management Tools 8AL91002xxyy

[3] User Services 8AL91003xxyy

[4] Attendant Services 8AL91004xxyy

[5] Public Networks 8AL91005xxyy

[6] Private Networks 8AL91006xxyy

[7] IP-PCX Networks 8AL91007xxyy

8AL91000USAH - Ed. 01 - September 2017 - System Services 21/458

Documentation title Part number

[8] Voice Mail 8AL91008xxyy

[9] Mobility 8AL91009xxyy

[10] General Applications 8AL91010xxyy

[11] Hotel/Hospital 8AL91016xxyy

[13] Maintenance 8AL91011xxyy

[14] Security 8AL91012xxyy

[15] PWT 8AL91019xxyy

8AL91000USAH - Ed. 01 - September 2017 - System Services 22/458

Documentation title Part number

[16] Crystal Hardware System Boards 8AL91020xxyy

[17] Crystal Hardware Interface Boards 8AL91021xxyy

[18] Common Hardware Boards 8AL91022xxyy

[19] Cables 8AL91023xxyy

[20] Dedicated sets 8AL91024xxyy

[21] TA and TSC Adapters 8AL91025xxyy

[22] Complementary Equipment 8AL91026xxyy

8AL91000USAH - Ed. 01 - September 2017 - System Services 23/458

Documentation title Part number

[23] Common Hardware Installation Manual 8AL91027xxyy