(Cmsa-A0-El-ma-cya-0010) O&m Manual For Communication System - Telephone System

Power Cogeneration Plant Company
SAUDI ARAMCO THIRD PARTY COGENERATION PROJECTS

Owner Power Cogeneration Plant Company
Contractor Samsung Engineering Company Ltd.
Plant Location ABQ
Contract No. 6600032961 Document No. CMSA-A0-EL-MA-CYA-0010
Installation, Operation and Maintenance Manual

For Communication System - TELEPHONE SYSTEM
SECL DISTRIBUTION
PROJECT
CIVIL
ARCH.
ELEC. O
INST.&CONT.
FIRE FIGHTING
HVAC
MECH.
PIPING
PROCESS
VIBRATION
NOISE
MATERIAL
PERPORMANCE
GROUP
PROCURE. V
CONST.
QA/QC
HSE
PRECOMM.-
COMM.
A 20-MAY-2015 Issued for Information J. H. Shin S. J. Kwon S.Choi S.Choi

Rev. Date Description Prepared by Checked by Approved by PD
DOCUMENT TITLE : Installation, Operation and Maintenance Manuals
DOCUMENT NO : CMSA-A0-EL-MA-CYA-0010
REQUISITION NO : SECL-A0-EL-RQ-CY-0001
PURCHASE ORDER NO : 4500176824
ITEM NO : ALL
ITEM DESCRIPTION : TELEPHONE SYSTEM
PLANT LOCATION : ABQAIQ PLANT, SAUDI ARABIA
FOR CONSTRUCTION
APPROVED WITH COMMENT
REVIEWED RESUBMIT
ISSUED
This approval or review does not relieve the vendor / May 15, 2015
subcontractor of his responsibilities to meet all VECTOR
requirements of the purchase order INFOTECH
PREPARED CHECKED APPROVED
SIGN
DATE
SAMSUNG ENGINEERING CO., LTD
0 15-May-2015 Issued for Construction Ryan Salgado Roberto Bautista Jawn Ng

A 29-Apr-2015 Issued For Approval Ryan Salgado Roberto Bautista Jawn Ng
REV. DATE DESCRIPTION PREPARED BY CHECKED BY APPROVED BY
POWER COGENERATION PLANT COMPANY
SAMSUNG ENGINEERING CO., LTD.

SEOUL KOREA
SECL PROJECT NO. : SP2673
VECTOR INFOTECH PTE LTD
1 of 459
RECORDS OF REVISION
Rev. Issue Date Description
A 29.APR.2015 ISSUED FOR APPROVAL
0 15.MAY.2015 NO CHANGES
2 of 459
INDEX PAGE
S/N Brand Description Page No.
1 Alcatel-Lucent / Omni PCX OXE System: Common Hardware Installation Manual 4

2 Alcatel-Lucent / Omni PCX OXE System: Software Installation Manual 122
3 Alcatel-Lucent / 4059IP Attendant Console 326
4 Allied Telesis / AT-GS900/5E 5 Port Unmanaged Gigabit Ethernet Switch 400
5 Emerson / GXT-3000MTPLUS230 Liebert Online Tower UPS 441
3 of 459
Alcatel-Lucent OmniPCX Enterprise
Communication Server
OXE System: Common Hardware Installation Manual
4 of 459
Legal notice:
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of

Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2014 Alcatel-Lucent. All rights reserved.
The CE mark indicates that this product conforms to the following Council
Directives:
- 2004/108/EC (concerning electro-magnetic compatibility)
- 2006/95/EC (concerning electrical safety)
- 1999/5/EC (R&TTE)
5 of 459

Chapter 1
Hardware description
Description of Racks ............................................................................. 1.1

S (SMALL) Rack ............................................................................................ 1.1
L (LARGE) Rack ............................................................................................ 1.1
Boards Description ................................................................................ 1.2
CS Board ....................................................................................................... 1.5
CS-2 Board .................................................................................................... 1.6
GD Board ....................................................................................................... 1.8
GD-3 Board ................................................................................................... 1.9
GA Board ......................................................................................................1.13

GA-3 Board ...................................................................................................1.14
MEX Board ...................................................................................................1.16
PowerMEX Board .........................................................................................1.17
UAI-X and UAIX-1 Boards ............................................................................1.18
SLI-X and SLIX-1 Boards .............................................................................1.18
BRA-X Boards ..............................................................................................1.18
PRA-T2, PRA-T1, T1 CAS, PRA DASS2 and PCM R2 Boards ...................1.19
APA-X Boards ..............................................................................................1.20
MIX X/Y/Z Boards .........................................................................................1.21
LANX Boards ................................................................................................1.22

Installing Daughterboards/SDRAM on CPU Boards .....................................1.23
Board Position in the Racks ..............................................................1.24
SMALL Rack .................................................................................................1.24
LARGE Rack ................................................................................................1.25
!"# $ % $ &'( ! ) $

0-1
6 of 459

Chapter 2
Specific Technical Data
Safety Standards .................................................................................... 2.1

Declaration of Conformity .............................................................................. 2.1
Declaration of Conformity with Directives ...................................................... 2.1
Classification of Interfaces ............................................................................. 2.2
Environment ............................................................................................. 2.2
Chapter 3
Installation Recommendations
Environmental Conditions .................................................................. 3.1

Operation ....................................................................................................... 3.1
Storage .......................................................................................................... 3.1
Transportation ............................................................................................... 3.1
Vibration ........................................................................................................ 3.1
Site ............................................................................................................... 3.1
Suggested Equipment .......................................................................... 3.2
Fire Detection ................................................................................................ 3.2
Protection Against Fire .................................................................................. 3.2
Temperature Alarm ........................................................................................ 3.2
General Recommendations ................................................................ 3.2
Chapter 4
Protection against Interferences
0-2 !"# $ % $ &'( ! ) $

7 of 459

Chapter 5
Installation procedure
Overview .................................................................................................... 5.1

List of Steps for Complete Installation ........................................... 5.1
Chapter 6
Assembling
Equipment Reception ........................................................................... 6.1

Installation of S and L Racks ............................................................. 6.1
Overview ........................................................................................................ 6.1
Installation Procedure in a Standard 19" Cabinet .......................................... 6.1
Chapter 7
Internal connections
Overview .................................................................................................... 7.1

Output Connector Pinout .................................................................... 7.1
GD Board ....................................................................................................... 7.1
GD-3 Board ................................................................................................... 7.2
CS and GA Boards ........................................................................................ 7.2
GA-3 Board .................................................................................................... 7.3
MEX Board .................................................................................................... 7.3

PowerMEX Board .......................................................................................... 7.3
Types of Cable to Be Used ................................................................. 7.4
Example Connection ............................................................................. 7.4
!"# $ % $ &'( ! ) $

0-3
8 of 459

Chapter 8
External connections
General ....................................................................................................... 8.1

Output Connector Pinout .................................................................... 8.1
SLI board ....................................................................................................... 8.1
UAI Board ...................................................................................................... 8.1
BRA Board ..................................................................................................... 8.1
PRA-T1, T1 CAS, PRA-T2, PRA DASS2 and PCM R2 Board ...................... 8.2
LAN X Board .................................................................................................. 8.2

APA 2, 4 and 8 Boards .................................................................................. 8.2
Types of Cable to Use .......................................................................... 8.2
Connecting a PC ..................................................................................... 8.3
System Management ..................................................................................... 8.3
Configuring the GD Board ............................................................................. 8.3
Connecting Terminals .......................................................................... 8.3
Connecting Alcatel Reflexes Terminals ......................................................... 8.3
Connecting Analog Terminals ....................................................................... 8.4
Connecting DECT or PWT Base Stations ...................................... 8.5
Connecting to the Public Network ................................................... 8.6
Digital Public Network via T0 Access (or S0-FV for Germany) ..................... 8.6
Digital Public Network via T1 or T2 Access ................................................... 8.7
Analog Public Network .................................................................................. 8.8
Connecting the LAN .............................................................................. 8.8
Connecting Auxiliary Equipment (on a GD or GD-3 Board) .... 8.9
Connecting an On-Hold Message Device ..................................................... 8.9
Connecting a Background Music Tuner ........................................................ 8.9
Connecting an Alarm ....................................................................................8.10
Connecting an External Loudspeaker ..........................................................8.11
Connecting a General Ringer .......................................................................8.12

Use of the 12 V Output of the AUDIO-OUT Connector ................................8.12
Connections for Remote Maintenance .........................................................8.12
0-4 !"# $ % $ &'( ! ) $

9 of 459

Chapter 9
Power connections
Connecting the Protective Ground .................................................. 9.1

Using Internal Batteries ....................................................................... 9.2
Battery Switch ................................................................................................ 9.2
Battery Fuse .................................................................................................. 9.3
Replacing the Batteries ................................................................................. 9.3
Connecting a UPS (Uninterruptible Power Supply) - Optional ..
9.3
Overview ........................................................................................................ 9.3
Connecting a Pulsar ellipse Type UPS .......................................................... 9.3
Connecting a Pulsar EXtreme C Type UPS .................................................9.10
Optional External Battery Rack ........................................................9.16
Presentation .................................................................................................9.16
Characteristics ..............................................................................................9.18
Storage .........................................................................................................9.20
Installation Procedure ...................................................................................9.20
Assembling the Battery Rack .......................................................................9.28

Connection to the System Rack ...................................................................9.28
48V Battery and Charger Racks .......................................................9.30
Presentation .................................................................................................9.30
Characteristics ..............................................................................................9.33
Storage .........................................................................................................9.36
Charger Rack Installation Procedure ............................................................9.36
Installing an External 48V Supply .................................................................9.43
Chapter 10
Maintenance
!"# $ % $ &'( ! ) $

0-5
10 of 459

Replacing the Internal Batteries ......................................................10.1

Replacing External Batteries ............................................................10.1
Battery Maintenance ............................................................................10.2
Ventilation System, maintenance ....................................................10.2
Replacing a Board ................................................................................10.2
Recommendations ........................................................................................10.2
Replacing the CS Board ...............................................................................10.3
0-6 !"# $ % $ &'( ! ) $

11 of 459

1.1 Description of Racks

The OmniPCX Enterprise uses the same racks as the OmniPCX Office.
There are four rack models in 19" format (two 1U type racks and two 3U type racks), all
designed to be mounted in a computer cabinet or placed on a shelf. The rack footprint is
identical, allowing easy stacking of racks.
The only functional difference between 1U and 3U type racks is the number of boards they can
contain.
The difference between the two types of 1U rack and the two types of 3U racks is the
presence of internal batteries.
One of the 1U racks and one of the 3U racks have internal batteries.The other 1U and 3U rack
have external batteries.
All types of racks can coexist.
An Common Hardware Media Gateway comprises a main rack and one or two extension racks
if necessary.
1.1.1 S (SMALL) Rack
Figure 1.1: Small Rack Front Panel

- 28 ports maximum
- One controller slot + two all-purpose slots
- Dimensions: H = 66 mm (2.6")/ W=442 mm (17")/ D = 400 mm (15.7")
- Weight: 6 kg (13.2 lb)
1.1.2 L (LARGE) Rack
!"# $ % $ &'( ! ) $

1-1
12 of 459
Chapter 1 *+

Figure 1.2: Large Rack Front Panel

- 96 ports maximum
- One controller slot + one all-purpose slot + seven specific slots
- Dimensions: H = 154 mm (6")/ W=442 mm (17")/ D = 400 mm (15.7")
- Weight: 13 kg (28.6 lb)
1.2 Boards Description

BOARDS FUNCTIONS DAUGHTERBOARDS CONNECTION
CS Call server XMEM: IDE hard drive inter- Hub, Lanswitch, V24 terminal,
(See note be- Voice mail (4645) face Ethernet
low) SLANX: LAN Switch
CS-2 Call server SLANX4: LAN Switch Hub, Lanswitch, V24 terminal, 2
Voice mail (4645) (optional) Ethernet interfaces
GD Media Gateway controller HSL1, HSL2: interconnection Hub, Lanswitch, V24 terminal,
Switching with extension modules Ethernet
(optional) On-hold message device
Voice over IP
MCV24/8 or MADA3/1: com-
Tone generator Background music tuner
pression / decompression of
Voice guides voice channels for VoIP applic- External loudspeaker, General
ations (optional) ringing
Three party conference
n party conference See note below.
AFU: Auxiliary Function Unit:
DTMF (touchtone) gener-
audio input/output (optional)
ator and detector
Modem
1-2 !"# $ % $ &'( ! ) $

13 of 459
*+


GD-3 Media Gateway controller HSL1, HSL2: interconnection Hub, Lanswitch, V24 terminal,
Switching with extension modules Ethernet
(optional) On-hold message device
Voice over IP
ARMADA: compression / de-
Tone generator Background music tuner
compression of voice channels
Voice guides for VoIP applications (optional) External loudspeaker, General
ringing
Three party conference See note below.
n party conference AFU: Auxiliary Function Unit:
audio input/output (optional)
DTMF (touchtone) gener-
ator and detector
Modem
GA Auxiliary board (extends SLANX: LAN Switch (optional) Hub, Lanswitch, V24 terminal,
GD resources) MCV24/8 or MADA3/1 Ethernet
(optional). See note below.
GA-3 Auxiliary board (extends SLANX: LAN Switch (optional) Hub, Lanswitch, V24 terminal,
(See note be- GD resources) ARMADA (optional). See note Ethernet
low.) below.
MEX / Extension module control- HSL1: interconnection with the
ler main rack
PowerMEX Extension module control- HSL1: interconnection with the
ler main rack
UAI4 / UAI41 Four, eight or 16 UA Alcatel Reflexes sets, DECT
UAI8 / UAI81 devices base stations
UAI16 /
UAI161
SLI4 / SLI41 Four, eight or 16 Z devices Z analog terminals
SLI8 / SLI81
SLI16 /
SLI161
BRA2 BRA4 Two, four or eight T0 pub- ISDN network
BRA8 lic network basic rate ac-
cesses or
S0-FV (Germany)
!"# $ % $ &'( ! ) $

1-3
14 of 459
Chapter 1 *+


PRA-T1 (CCS PRA-T1 and T1 CAS: 23 B PRA-T1 and T1 CAS: Public net-
mode) channels + one D channel work
T1 CAS (CAS PRA-T2: T2 public network PRA-T2: ISDN network, ABC or
mode) access QSIG network
PRA-T2
PRA DASS2: DASS2 pub- PRA DASS2: DASS2 ISDN net-
PRA DASS2
lic network access work
PCM R2
PCM R2: 30 B channels PCM R2: public network
(64 Kbits/s) + one signal-
ing channel (4 Kbits/s);
2048 Kbits/s
APA4 APA8 Four or eight analog Trunk METCLI: charge unit receiver Analog Trunk Line (TL) and TL-
Line (TL) devices (optional) SUBS diversion
GSCLI: "ground start" board
enables "ground start signal-
ing", mainly used in the USA
(optional)
CLIDSP: enables CLIP
(Calling Line Identification Pro-
tocol) (optional)
As from R5.1.2 the CLIP fea-
ture is available for the USA
MIX2/4/4 Zero, two or four T0 base ISDN network, Z analog termin-
MIX4/8/4 accesses + four or eight als and Alcatel Reflexes sets
MIX4/4/8 UA devices + four or eight
MIX0/4/4 Z devices
MIX0/8/4
MIX0/4/8
LANX16 / 16 Ethernet 10/100 BT IP phones, Lanswitch, Hub, etc.
LANX161 ports
LANX8-2 7 10/100BaseT ports and IP phones, Lanswitch, Hub, etc.
one 10/100/1000BaseT
port
LANX16-2 14 10/100BaseT ports and IP phones, Lanswitch, Hub, etc.
two 10/100/1000BaseT
ports
RMA Remote maintenance See the RMA documents
MODB Modem support Modem See the RMA documents
Note 1:
MADA1 and MADA3 boards replace respectively MCV8 and MCV24 boards. They offer an echo depth of
128 ms instead of 32 ms (system option to be configured in MAO).
Note 2:
ARMADA daughterboard: due to a power supply limitation, only one ARMADA daughterboard is allowed
in a rack.
Note 3:
GA-3 board: due to a power supply limitation:
1-4 !"# $ % $ &'( ! ) $

15 of 459
*+

- The GA-3 board cannot be hosted in a small rack

- Only one GA-3 board can be hosted in the large main rack
- Two GA-3 boards can be hosted in the large extension rack
1.2.1 CS Board
Figure 1.3: CS Board Front Panel

The CS board offers the following features:
- Call server
- 4645 Voice mail (optional)
1.2.1.1 LED Meanings
Name Function
CPU Flashing green: CPU operating correctly
LAN Green: LAN operating correctly (flashes to indicate traffic)
WAN Green: WAN operating correctly (flashes to indicate traffic)
UNIT 1-3 UPLINK Green: LAN switch 1 interface operating correctly (flashes to
indicate traffic)
1.2.1.2 CS Board Micro Switches Setting

The CS board setting of micro switches depends on board position in the rack:
CS board position Micro switches value Micro switches setting
Controller position 0x09
!"# $ % $ &'( ! ) $

1-5
16 of 459
Chapter 1 *+

CS board position Micro switches value Micro switches setting
Other positions 0x01
Caution:
In controller position, if the CS board setting of micro switches does not correspond to the 0x09
value, the CS board cannot monitor the activity of an optional external batteries rack.
1.2.2 CS-2 Board
Figure 1.4: CS-2 Board Front Panel

The CS-2 board offers the following features:
- Call server
- 4645 Voice mail (optional)
In addition, this board can act as a PCS (Passive Call Server) without restriction.
1.2.2.1 External Interfaces
- LAN1: 10/100/1000 BaseT Ethernet access
- LAN2: redundant 10/100/1000 BaseT Ethernet access
- . (top right): V24 access to system configuration and remote reset signal coming from an
RMA box
- UNIT1, UNIT 2, UNIT 3, UP-LINK: 4 ports 10/100BT LAN switch (if the SLANX4
daughterboard is present)
- USB: not used
1-6 !"# $ % $ &'( ! ) $

17 of 459
*+

Name Function
LAN1 - Green: LAN port 1 operating correctly
- Flashing green: Ethernet traffic detected, flash speed increases
with traffic
LAN2 - Green: LAN port 2 operating correctly (the dual Ethernet feature
is configured)
- Flashing green: Ethernet traffic detected, flash speed increases
with traffic
HD Green: hard disk activity
FAN - Green: fans operating correctly
- Red: 1 or 2 fan(s) out of service
Power - Green: operating on mains
- Yellow: operating on battery
- Flashing red: shutdown in progress
- Red: shutdown complete
- Off: power off
UNIT 1-3 UPLINK Green: LAN switch 1 interface operating correctly (flashes to indicate
traffic)
1.2.2.3 Daughterboards
The CS-2 board supports the SLANX4 daughterboards (optional). This daughterboard
provides a 4 ports 10/100BT LAN switch. This switch cannot be configured.
Figure 1.5: CS-2 Daughterboards Installation
1.2.2.4 Dual Ethernet

Two dual Ethernet modes are available:
- Ethernet Redundancy
- Ethernet Load Balancing
1.2.2.4.1 Ethernet Redundancy
!"# $ % $ &'( ! ) $

1-7
18 of 459
Chapter 1 *+

The CS-2 board supports the Ethernet redundancy feature (also called hot standby or dual
Ethernet).
Two Ethernet interfaces allow two Ethernet accesses. The two Ethernet interfaces have the
same MAC address and IP address. One interface is active, the other one is standby. When
the active interface fails, the standby interface switches to active automatically.
For complete redundancy, each interface must be connected to a different switch unit. These
switches must be parts of a redundancy network supporting the Fast Spanning Tree standard.
As in no redundancy mode, only one IP address is used.
Ethernet Redundancy must be activated via the netadmin tool (see: netadmin - Operation -
Ethernet Redundancy).
Note:
The SLANX4 board does not support Ethernet redundancy.
1.2.2.4.2 Ethernet Load Balancing

The CS-2 board supports the Ethernet load balancing feature.
The two Ethernet interfaces are active simultaneously, the traffic is shared between the two
interfaces. When an interface fails, the other one proceeds the whole traffic.
The two Ethernet interfaces must be connected to two interfaces of the same switch unit. This
switch unit requires a special configuration. This switch unit must support the load balancing
feature.
Ethernet load balancing must be activated via the netadmin tool (see: netadmin - Operation -
Ethernet Redundancy).
Note:
The SLANX4 board does not support load balancing.
1.2.3 GD Board
Figure 1.6: GD Board Front Panel

The GD board offers the following features:
- Media Gateway controller
- Switching
- Voice over IP
1-8 !"# $ % $ &'( ! ) $

19 of 459
*+

- Tone generator
- Voice guides
- Three party conference
- n party conference
- DTMF (touchtone) generator and detector
- Modem
This board is not compatible with the GA-3 and PowerMEX boards.
Name Function
POWER - Green: operating on mains
CPU - Flashing green: CPU operating correctly
- Red flashing: shutdown in progress
FAN - Green: fans working
- Red: one or two fans out of service
LAN Flashing green: LAN operating correctly
MODULE Green: HSL board installed
1.2.3.2 GD Board Micro Switches Setting

The GD board micro switches must be set as indicated in the figure below. Do not change the
position of these switches (reserved for Alcatel-Lucent support).
Figure 1.7: Switch Settings
1.2.4 GD-3 Board

The GD-3 board drives the Media Gateway and interfaces the Media Gateway with the Call
Server.
!"# $ % $ &'( ! ) $

1-9
20 of 459
Chapter 1 *+

Figure 1.8: GD-3 Board Front Panel

This board is not compatible with the GA and MEX boards.
1.2.4.1 Functions
The GD-3 board offers the following features:
- Media Gateway controller
- Switching
- Voice over IP
- Tone generator
- Voice guides
- Conferencing
- DTMF (touchtone) generator and detector
- Modem
- Interface to the extension racks
- Two Ethernet interfaces (LAN and LAN-2) are available:
As of R11.1, these two interfaces can be connected simultaneously for Ethernet
redundancy purposes. For more information, see: Ethernet redundancy connection .
Before R11.1, only one interface can be connected at the same time (no redundancy)
For board reflashing (advanced maintenance operation), only the LAN interface can be
used as bootp/tftp LAN interface.
Note:
The GD-3 board supports the following daughterboards:
- HSL1, HSL2: These optional daughterboards allow to connect extension modules:
HSL1: allows to connect 1 extension module via Module1 connector
HSL2: allows to connect 2 extension modules via Module2 connectors
- ARMADA: this optional daughterboard supports additional DSPs (Digital Signal Processor)
used for compression/decompression of voice channels for VoIP applications
- AFU: Auxiliary Function Unit: audio input/output (optional)
1-10 !"# $ % $ &'( ! ) $

21 of 459
*+

Figure 1.9: GD-3 Daughterboards Installation
Name Function
CPU - Fixed green: BIOS startup in progress
- Fast blinking green: binary download in progress
- Irregular blinking green (4 fast blinks + 1 normal blink):
flash memory formatting in progress
Caution:
DO NOT UNPLUG THE BOARD DURING THIS PHASE.
- Blinking green: application startup in progress or board in
service
- Blinking red: shutdown in progress
- Fixed red: shutdown completed
- Led off: power off
FAN - Green: fans working
- Red: one or two fans out of service
LAN Flashing green: indicates traffic activity
LAN2 Flashing green: indicates traffic activity
MODULE Green: HSL daughterboard installed
Off: HSL not installed
1.2.4.4 Board Micro Switch Setting

The GD-3 board micro switches must be set as indicated in the figure below. Do not change
the position of these switches (reserved for Alcatel-Lucent support).
!"# $ % $ &'( ! ) $

1-11
22 of 459
Chapter 1 *+

1.2.4.5 Ethernet redundancy connection

As of R11.1, the two ethernet interfaces of a GD-3, GA-3 and INT-IP3 boards (also called NGP
boards) can be connected simultaneously for Ethernet redundancy purposes. One interface is
active, the other one is standby. When the active interface fails, the standby interface switches
to active. These two interfaces share the same MAC address and the same IP address.
The Linux kernel include a bonding driver which provides a method for aggregating multiple
network interfaces into a single logical "bonded" interface.
Bonded interfaces provide only hot standby service (active-backup policy).
Only one network interface (a slave) in the bond is active. The other network interface
becomes active when the active slave fails. The bond's MAC address is externally visible on
only one network adapter to avoid confusing the switch.
The network interface eth0 is used as the default active slave if both network interfaces are
connected to a LAN. When a failover occurs in active backup mode, bonding will issue one or
more gratuitous ARP requests on the newly active slave.
One gratuitous ARP request is issued for the bonding master interface and each VLAN
interfaces configured above it, provided that the interface has at least one IP address
configured.
Gratuitous ARP requests issued for VLAN interfaces are tagged with the appropriate VLAN id.
Ethernet redundancy is applicable under Linux kernel driver control but not applicable at
bootstrap time.
___change-begin___
1-12 !"# $ % $ &'( ! ) $

23 of 459
*+

___change-end___
Figure 1.11: Ethernet redundancy connections

For complete Ethernet redundancy, each interface must be connected to a different switch
unit. These units must comply with the Fast Spanning Tree protocol and be configured to allow
a fast IP frames forwarding when the port interface is up.
1.2.5 GA Board
Auxiliary board enabling GD resources to be extended.
Figure 1.12: GA Board Front Panel

This board is not compatible with the GD-3, GA-3 and PowerMEX boards.
!"# $ % $ &'( ! ) $

1-13
24 of 459
Chapter 1 *+

Name Function
LAN Green: LAN operating correctly (flashes to indicate traffic)
UNIT 1-3 UPLINK Green: LAN switch 1 interface operating correctly (flashes to
indicate traffic)
1.2.5.2 Micro Switches Setting

The GA board micro switches must be set as indicated in the figure below. Do not change the
position of these switches (reserved for Alcatel-Lucent support).
1.2.6 GA-3 Board

The GA-3 board is an applicative board which provides additional processing resources to the
Media Gateway.
___change-begin___
___change-end___
Figure 1.14: GA-3 Board Front Panel

This board is not compatible with the GD, GA and MEX boards.
1.2.6.1 Functions
This board provides additional resources to the Media Gateway.
Two Ethernet interfaces (LAN and LAN-2) are available:
- As of R11.1, these two interfaces can be connected simultaneously for Ethernet
redundancy purposes. For more information, see: Ethernet redundancy connection .
1-14 !"# $ % $ &'( ! ) $

25 of 459
*+

- Before R11.1, only one interface can be connected at the same time (no redundancy)
For board reflashing (advanced maintenance operation), only the LAN interface can be used
as bootp/tftp LAN interface.
Note:
The GA-3 board supports the following daughterboards:
- ARMADA: this optional daughterboard supports additional DSP (Digital Signal Processor)
used for compression/decompression of voice channels for VoIP applications
- SLANX: this optional daughterboard provides a 4 ports 10/100BT LAN switch. This switch
cannot be configured.
Figure 1.15: GA-3 Daughterboards Installation
1.2.6.3 LEDs Meanings
Name Function
CPU - Fixed green: BIOS startup in progress
- Fast blinking green: binary download in progress
- Irregular blinking green (4 fast blinks + 1 normal blink):
flash memory formatting in progress
Caution:
DO NOT UNPLUG THE BOARD DURING THIS PHASE.
- Blinking green: application startup in progress or board in
service
- Blinking red: shutdown in progress
- Fixed red: shutdown completed
- Led off: power off
!"# $ % $ &'( ! ) $

1-15
26 of 459
Chapter 1 *+

Name Function
LAN Flashing green: indicates traffic activity
LAN-2 Flashing green: indicates traffic activity
UNIT1 to UNIT3 Flashing green: indicates traffic activity
UP-LINK
1.2.6.4 GA-3 Board Micro Switch Setting

The GA-3 board micro switches must be set as indicated in the figure below. Do not change
the position of these switches (reserved for Alcatel-Lucent support).
1.2.7 MEX Board

The MEX board drives the extension rack and interfaces the GD board located in the main
rack.
Figure 1.17: MEX Board Front Panel

This board is not compatible with the GD-3 and GA-3 boards.
LED meanings :
Name Function
- Flashing red: standby
- Red: one or both fans failed
1-16 !"# $ % $ &'( ! ) $

27 of 459
*+

This board is not compatible with the GD-3 and GA-3board.
1.2.8 PowerMEX Board

The PowerMEX board drives the extension rack and interfaces the GD-3 board located in the
main rack.
Figure 1.18: PowerMEX Board Front Panel

This board is not compatible with the GD, GA and MEX boards.
1.2.8.1 PowerMEX Daughterboards
The PowerMEX board supports the HSL1 daughterboard. This board allows the connection to
the main rack.
Figure 1.19: PowerMEX Daughterboard Installation
1.2.8.2 LEDs Meanings
!"# $ % $ &'( ! ) $

1-17
28 of 459
Chapter 1 *+

Name Meaning
- Flashing red: standby
- Red: one or both fans failed
Note:
This board is not compatible with the GD board.
1.2.9 UAI-X and UAIX-1 Boards

These boards allow four, eight or 16 dedicated Alcatel-Lucent Reflexes sets or DECT or PWT
base stations to be connected.
Figure 1.20: UAI-X Board Front Panel
1.2.10 SLI-X and SLIX-1 Boards

These boards allow four, eight or 16 analog sets to be connected.
Figure 1.21: SLI-X Board Front Panel
1.2.11 BRA-X Boards
1-18 !"# $ % $ &'( ! ) $

29 of 459
*+

These boards allow two, four or eight T0 basic accesses (two B channels + one D channel) to
be connected.
Figure 1.22: BRA-X Board Front Panel
1.2.12 PRA-T2, PRA-T1, T1 CAS, PRA DASS2 and PCM R2 Boards

These boards, which are used to connect a primary access, are the following:
- T2 access via the PRA-T2 board (30 B channels + one D channel)
- T1 access by boards:
PRA-T1 (CCS mode, 23 B channels + one D channel)
T1 CAS (CAS mode, 23 B channels + one D channel)
- DASS2 access: 30 B channels (64 Kbits/s) + two service channels
- PCM R2 access: 30 B channels (64 Kbits/s) + one signaling channel
Example on front panel:
Figure 1.23: PRA-T2 Board Front Panel

LED meanings:
Name Function
BUSY B channels busy (red LED on if at least one B channel is busy)
RAI Remote frame alarm (red LED on if there is an alarm)
!"# $ % $ &'( ! ) $

1-19
30 of 459
Chapter 1 *+

Name Function
AIS Excessive number of "1"s in the 2 Mbits bit stream (red LED on if
there is an alarm)
NOS 2 Mbits signal missing (red LED on if there is an alarm)
CRC CRC error (red LED on if there is an alarm)
LOS Loss of frame alignment (red LED on if there is an alarm)
1.2.13 APA-X Boards

These boards allow connection to the analog public network (two, four or eight accesses).
These boards are also used to forward calls when a system failure occurs (power cutoff or
computer problem).
1-20 !"# $ % $ &'( ! ) $

31 of 459
*+

Figure 1.24: APA2 APA4 APA8 Boards Front Panel

Note:
In Australia and New Zealand, APA boards do not support decimal dialing.
1.2.14 MIX X/Y/Z Boards

These boards allow two or four T0 basic accesses, four or eight analog sets and four or eight
dedicated Alcatel-Lucent Reflexes sets to be connected.
!"# $ % $ &'( ! ) $

1-21
32 of 459
Chapter 1 *+

Figure 1.25: MIX Board Front Panel
1.2.15 LANX Boards

These boards allow a LAN to be created by connecting client PCs, IP-Phones, external
Lanswitch and server.
1.2.15.1 LANX16 and LANX16-1 Boards
Figure 1.26: LANX19 Board Front Panel

Each RJ45 connector (category 5) has two green LEDs:
off: on: flashing:
Left LED link disconnected link connected link active
Right LED half duplex full duplex collision
1.2.15.2 LANX-2 Boards

The LANX8-2 and LANX16-2 boards are second generation boards integrating respectively
one or two 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.
The LANX8-2 board offers 7 10/100BaseT ports and one 10/100/1000BaseT port.
The LANX16-2 board offers 14 10/100BaseT ports and two 10/100/1000BaseT ports.
1-22 !"# $ % $ &'( ! ) $

33 of 459
*+

Figure 1.27: LANX122 Board Front Panel

LEDs for all ports are located on the top of the board.
- : indicates the status of ports GE1,6, 4,2, GE2, 13, 11, 9 on the top half of the board.
- : indicates the status of ports 7, 5, 3, 1, 14, 12, 10, 8 on the bottom half of the board.
Each RJ45 connector (category 5) has two LEDs:

off: on: flashing:
Left LED (green) link disconnected link connected link active
Right LED (yellow) for 10 MHz 100 MHz
10/100BaseT ports
Right LED (yellow) for 10 MHz or 100 MHz 1 GHz
10/100/1000BaseT
ports
1.2.16 Installing Daughterboards/SDRAM on CPU Boards

The following table shows the different daughterboards that can be installed on the various
CPU boards.
Daughter boards CS CS-2 GD GD-3 GA GA-3
SDRAM64 No No Yes No Yes No
SDRAM128 Yes No No No No No
DDR256 No Yes No Yes No Yes
MCV8 No No Yes No Yes No
MCV24 No No Yes No Yes No
MADA1 No No Yes No Yes No
MADA3 No No Yes No Yes No
ARMADA No No No Yes No Yes
HSL1 No No Yes Yes No No
HSL2 No No Yes Yes No No
!"# $ % $ &'( ! ) $

1-23
34 of 459
Chapter 1 *+

Daughter boards CS CS-2 GD GD-3 GA GA-3

AFU No No Yes Yes No No
SLANX Yes Yes No No Yes Yes
XMEM + Hard disk Yes No No No No No
Figure 1.28: Example of Equipment with Daughterboards
1.3 Board Position in the Racks

Board positions given in this section are for information only. Actual positions of boards in the
racks are given by Actis which applies configuration rules not presented here and subject to
regular updates.
1.3.1 SMALL Rack
Figure 1.29: Small Rack Front Panel
1-24 !"# $ % $ &'( ! ) $

35 of 459
*+

Board Slot 1 Slot 2 Controller Slot

CS / CS-2 No Yes Yes
GD / GD-3, No No Yes
MEX / PowerMEX
(see restrictions below)
GA / GA-3 Yes No No
(see restrictions below)
UAI4, UAI41, UAI8, Yes Yes No
UAI81
UAI16, UAI161 Yes Yes No
SLI4, SLI41, SLI8, Yes Yes No
SLI81
BRA2, BRA4, BRA8 Yes Yes No
PRA-T2, PRA-T1, T1 Yes Yes No
CAS, PRA DASS2 and
PCM R2
APA2, APA4, APA8 Yes Yes No
MIX2/4/4, MIX4/8/4, Yes Yes No
MIX4/4/8, MIX0/4/4,
MIX0/8/4, MIX0/4/8
LANX16, LANX161, Yes Yes No
LANX8-2, LANX16-2
Empty slot blanking cov- Yes Yes No
er
1.3.2 LARGE Rack
!"# $ % $ &'( ! ) $

1-25
36 of 459
Chapter 1 *+

Figure 1.30: Large Rack Front Panel
Board\ Slot Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 Ctrl.
Slot
CS / CS-2 Yes Yes Yes Yes Yes Yes Yes Yes No
GD / GD-3 No No No No No No No No Yes
MEX /
PowerMEX
(see restric-
tions below)
GA / GA-3 Yes No N/Y* No No No No No No
(see restric-
tions below)
UAI4, Yes Yes Yes Yes Yes yes Yes N/Y* No
UAI41,
UAI8,
UAI81
UAI16, Yes Yes Yes Yes No No No No No
UAI161
SLI4, Yes Yes Yes Yes Yes Yes Yes N/Y* No
SLI41,
SLI8,
SLI81,
SLI16,
SLI161
1-26 !"# $ % $ &'( ! ) $

37 of 459
*+

Board\ Slot Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 Ctrl.
Slot
BRA2, Yes Yes Yes Yes Yes Yes Yes N/Y* No
BRA4,
BRA8
PRA-T2, Yes Yes Yes Yes Yes Yes Yes N/Y* No
PRA-T1, T1
CAS, PRA
DASS2,
PCM R2
APA2, Yes Yes Yes Yes Yes Yes Yes N/Y* No
APA4
APA 8 No No No No Yes Yes Yes N/Y* No
MIX2/4/4, Yes Yes Yes Yes No No No No No
MIX4/8/4,
MIX4/4/8,
MIX0/4/4,
MIX0/8/4,
MIX0/4/8
LANX16, Yes Yes Yes Yes Yes Yes Yes Yes No
LANX161,
LANX8-2,
LANX16-2
Empty slot Yes Yes Yes Yes Yes Yes Yes Yes No
blanking
cover
Y/N*: In the main rack "Yes ", in extension racks "No".

N/Y*: In the main rack "No", in extension racks "Yes".
!"# $ % $ &'( ! ) $

1-27
38 of 459
Chapter 1 *+

1-28 !"# $ % $ &'( ! ) $

39 of 459

2.1 Safety Standards

This cabinet is compliant with Technical Regulations for Law Voltage Electrical Equipment
and Technical Regulations in Electro Magnetic Compatibility in force in Ukraine.
2.1.1 Declaration of Conformity

We,
Alcatel-Lucent Enterprise,
32 avenue Klber
92707 Colombes Cedex - France
Declare that the following products are deemed to comply with the requirements of Directive
1999/CE/5 of the European Parliament and the Council.
Any unauthorized modification of the products renders this declaration of conformity null and
void.
Pursuant to the directive, as published in the Official Journal of the European Community of
April 7 1999, these appliances can be used in all countries of the European Community,
Switzerland, Norway and Iceland.
Copyright Alcatel-Lucent 2001. All rights reserved. Alcatel-Lucent Enterprise, in keeping with
its policy of constant product improvement for the customer, reserves the right to modify
product specifications without prior notice.
Alcatel-Lucent Enterprise - 32, avenue Klber F-92707 Colombes Cedex RCS Paris 602 033
185.
2.1.2 Declaration of Conformity with Directives

This appliance is designed to be connected to the public telephone network through
appropriate interfaces.
The CE mark indicates that this product conforms to the following Council Directives:
!"# $ % $ &'( ! ) $

2-1
40 of 459
Chapter 2 +*,* -*.* /


- 1999/5/EC (R&TTE)
2.1.3 Classification of Interfaces

SELV: Safety Extra Low Voltage
TNV-3: Telecommunications Network Voltage
2.2 Environment
Storage, transportation and rack 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
2-2 !"# $ % $ &'( ! ) $

41 of 459
+*,* -*.* /

- ETS 300 019 1.3, In Use, Class 3.1: Stationary use, Temperature controlled locations
!"# $ % $ &'( ! ) $

2-3
42 of 459
Chapter 2 +*,* -*.* /

2-4 !"# $ % $ &'( ! ) $

43 of 459

3.1 Environmental Conditions
3.1.1 Operation
- Temperature: to achieve optimum reliability, the ambient temperature must be between
+5C (-5C exceptionally) and +40C (45C exceptionally) with a maximum variation of
30C (86F) per hour. In degree Fahrenheit, the ambient temperature must be between
41F (23F exceptionally) and 104F (113F exceptionally)
- Relative humidity: relative humidity must be between 5% and 85% (90% exceptionally)
without condensation.
3.1.2 Storage
- Temperature: temperature must be between -25C (-13F) and +55C (131F).
- Relative humidity: relative humidity must be between 10% and 100% (without
condensation).
3.1.3 Transportation
- Temperature: temperature must be between -40C (-40F) and +70C (158F).
- Relative humidity: relative humidity does not exceed 95% (without condensation).
3.1.4 Vibration
The hard disk drive is the most sensitive to these two phenomena. The vibrations must not
exceed 0.01G with displacement amplitude less than 0.3mm. The shocks must be less than
4G during 22ms.
3.2 Site
- Select a dry, clean, well-ventilated location.
- Maintain ambient air flow to ensure normal ventilation. If airflow is restricted, blocked or the
incoming air too warm, there is a risk of overheating.
- When the equipment is installed in a closed 19" cabinet, make sure the cabinet is
equipped with a ventilation system capable of dissipating the heat generated by the
equipment installed. Leave a clear space of at least 3 cm (1.2") around the side ventilation
!"# $ % $ &'( ! ) $

3-1
44 of 459
Chapter 3

0*

slots (left and right panels), and at least 10 cm (4") around the rear ventilation slots. Make
sure the airflow is not blocked at the sides of the cabinet.
- When the system is mounted directly on a wall with the wall-mounting kit (Rack 1 only),
leave a free space of at least 15 cm (6") around the entire system. Make sure that no
objects are placed on top of the system or prevent evacuation of hot air. For a multi-rack
installation, a horizontal rack alignment is preferred. If stacked vertically, leave a space of
at least 10 cm (4") between racks.
- Make sure the connecting cables of the Alcatel-Lucent OmniPCX Enterprise
Communication Server rack or other equipment or the uprights of the housing (19" cabinet
for example) do not obstruct airflow through the rack.
- Install a 230V or 110V mains power outlet (depending on country) - 50 Hz or 60 Hz (2P+G)
at a distance of no more than one meter from the rack if it is not installed in a cabinet
(otherwise the cabinet cutoff switch is used).
- The room must be well lit.
3.3 Suggested Equipment

The following specifications are strongly recommended given that the PBX and its peripherals
are both costly and safety equipment.
It is advised to have locked premises, with the key given to a single person.
3.3.1 Fire Detection

It is advisable to have fire detection equipment installed in the room (ionic smoke detection).
3.3.2 Protection Against Fire

It is advised to have inert gas injection protection installed in the room (water and foam
projection mechanical systems are to be banned).
3.3.3 Temperature Alarm

A device that can warn of an abnormal temperature rise inside the room will make it possible
to promptly remedy an air conditioning failure or any other failure.
3.4 General Recommendations

Caution:
It is vitally important to connect this product to a permanent ground connection installed in
accordance with the rules of the art.
Owing to the presence of hazardous voltages, the metal back plate may only be removed by
suitably qualified personnel.
In the event of a poor earth connection, it is IMPERATIVE to disconnect the telecommunications
ports before reconnecting the earth. A check must then be made to ensure that all connections
have been made correctly.
If it is necessary to intervene in the power supply unit, disconnect the mains cable before
3-2 !"# $ % $ &'( ! ) $

45 of 459

0*

removing the metal panel on the power supply unit and disconnect the batteries.
!"# $ % $ &'( ! ) $

3-3
46 of 459
Chapter 3

0*

3-4 !"# $ % $ &'( ! ) $

47 of 459

Notice to the attention of the users and installer:

USA - FCC (Federal Communication Commission)
This equipment has been tested and found to comply with the limits for a Class B digital
device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference in a residential installation. This equipment generates,
uses and can radiate radio frequency energy and, if not installed and used in accordance with
the instructions, may cause harmful interference to radio communications. However, there is
no guarantee that interference will not occur in a particular installation. If this equipment does
cause harmful interference to radio or television reception, which can be determined by turning
the equipment off and on, the user is encouraged to consult the installer or service person.
Changes or modifications to this equipment, not expressly approved by ALCATEL-LUCENT,
may cause harmful interference and void the users authority to operate this equipment.
Japan - VCCI (Voluntary Control Council for Interference)
Translation :
This is a Class B product based on the standard of the Voluntary Control Council for
Interference from Information Technology Equipment (VCCI). If this is used near a radio or
television receiver in a domestic environment, it may cause radio interference. Install and use
the equipment according to the instruction manual.
!"# $ % $ &'( ! ) $

4-1
48 of 459
Chapter 4 1
*
2

,*
4-2 !"# $ % $ &'( ! ) $

49 of 459

5.1 Overview
The purpose of this module is to guide you through assembly operations.
It describes all steps required for complete installation.
To facilitate subsequent maintenance and management operations, the different installation
methods described in the following section must be carefully followed in the order given.
There are 3 types of racks:
- internal batteries rack
- external batteries rack
- 48V supply racks
5.2 List of Steps for Complete Installation

The different steps to be observed for complete installation are:
- Install the Alcatel-Lucent OmniPCX Enterprise CS rack (see Small & Large racks -
Assembling )
- Make internal connections (see Small & Large racks - Internal connections )
- Make external connections (see Small & Large racks - External connections )
- Connect power supplies (see Small & Large racks - Power connections )
- First level maintenance operations are described in the Maintenance module (see Small &
Large racks - Maintenance )
!"# $ % $ &'( ! ) $

5-1
50 of 459
Chapter 5

+*
5-2 !"# $ % $ &'( ! ) $

51 of 459

6.1 Equipment Reception

The Alcatel-Lucent OmniPCX Enterprise CS rack is delivered:
- equipped with all sub-assemblies required for the customer's configuration.
- configured with the software key corresponding to the desired levels of service.
Terminals are packed separately.
Note:
Board OBCs must have release 3.0 or higher (see Small & Large racks - Maintenance )
6.2 Installation of S and L Racks
6.2.1 Overview
S and L racks can be installed in three ways:
- Placed on a table: a maximum of three racks can be stacked on top of each other.
- Mounted directly on a wall: a kit, available as an option, enables S racks to be
wall-mounted.
- Mounted in a standard 19" cabinet: the rack is mounted in the cabinet by means of
guide rails (provided by the cabinet supplier), or using an optional 19" mounting kit (there is
a kit for each type of rack).
6.2.2 Installation Procedure in a Standard 19" Cabinet
Installation Recommendations:
Before installating a rack in the cabinet, check that:
1. The max. static load capacity (given by the supplier) of the cabinet is greater than the total
weight of the equipment mounted or to be mounted in the cabinet,
2. The weight of the racks is evenly distributed over the height of the uprights,
3. If installing the rack would result in excessive load on the front uprights (this usually cor-
responds to total cabinet weight capacity divided by two) the rack must be placed on a
shelf attached to all four uprights.
Rack Installation Procedure:

- In order to simplify the mounting procedure, the standard cabinet is represen-
ted only by the two front uprights of the rack.
- Check beforehand that the mounting kit is complete. Each rack requires two
guide rails with its fastening elements and two locking pins.
Step 1: attaching the locking pins on the guiding rails.

- Place the slots of the fastening pin at the level of the screw heads of the guide rail (in 1),
then seat it against the stop (in 2).
!"# $ % $ &'( ! ) $

6-1
52 of 459
Chapter 6 (2
- Fasten the two screws of the guide rail until the fastening pin is locked.
- Repeat these operations with the second fastening pin.

Step 2: Identifying the mounting positions of the rack in the cabinet.
In order to optimize distribution of the rack(s) in the cabinet, place them in the cabinet, then
mark on the uprights the mounting positions of the guide rails (in 3).
6-2 !"# $ % $ &'( ! ) $

53 of 459
(2
Step 3: attaching the guide rails on the front uprights of the cabinet.
- Clip the nuts at the marked positions (step 2) on the rear face of the two uprights.
- Place the guiding rail against the upright (in 4) with the openings of the rail in front of the
nuts. Then, fit these screws in the openings and tighten them (in 5).
!"# $ % $ &'( ! ) $

6-3
54 of 459
Chapter 6 (2
- Repeat these operations with the second guiding rail.

Step 4: Installing the rack in the cabinet.
Align the rack in front of the guide rails (in 6) then slide it into the cabinet until it is locked by
the fastening pins (in 7).
6-4 !"# $ % $ &'( ! ) $

55 of 459
(2
!"# $ % $ &'( ! ) $

6-5
56 of 459
Chapter 6 (2
6-6 !"# $ % $ &'( ! ) $

57 of 459

7.1 Overview
After describing the pinout of the RJ45 output connectors for each board and reviewing the
cables to be used, this module goes on to describe the different rack connections to be made
to interconnect main rack boards (if 1 or 2 extension racks are used).
7.2 Output Connector Pinout

All outputs are made using female RJ45 connectors.
7.2.1 GD Board
RJ45 pin 1 2 3 4 5 6 7 8
LAN TX+ TX- RX+ RX-
Audio Out Audio
AUDIO-OUT Alarm A CenRg A CenRg B Alarm B Ground +12 V
A Out B
CONFIG CTS DSR RX Ground Ground TX DTR RTS
MODULE1 TX+ TX- RX+ RX-
MODULE2 TX+ TX- RX+ RX-
Audio In Audio Audio
AUDIO-IN Audio In A
B Ctrl A Ctrl B
- LAN: Ethernet 10/100 Base T (MDI-II/straight cable), for interconnection with CPU-GA or
LAN.
- AUDIO-OUT: External loudspeaker, alarm, general ringing interfaces; 12V output
- AUDIO-IN: On-hold message and background music interfaces.
- DOORPHONE: not used.
- CONFIG: RS232 for terminal (to configure the GD board: static and dynamic addressing).
!"# $ % $ &'( ! ) $

7-1
58 of 459
Chapter 7
**

- MODULE1: HSL link for interconnection with extension rack 1.

- MODULE2: HSL link for interconnection with extension rack 2.
7.2.2 GD-3 Board

- LAN: this port is used to connect to an Ethernet network. Use a straight RJ45 cable to
connect to a LAN switch (or a hub).
- LAN2: As of R11.1, this port is used to connect to an Ethernet network. Use a straight
RJ45 cable to connect to a LAN switch (or a hub).
LAN and LAN2 interfaces can be connected simultaneously for redundancy purposes.
Before R11.1, this LAN2 interface is not used.
- AUX: this port is used to connect an external ringing device.
table 7.2: Audio Port Connections
1 2 3 4 5 6 7 8 Shield
GND V12DC CENRG CENR- GND
CPU A GB
- Config: this port is used for GD-3 board local configuration. Use the 3EH75003AA cable
(RJ45/SUBD9) to connect to a VT100 (or emulation) configuration console.
- Module1: this port is used to connect to the first extension rack. Use a straight RJ45 cable
to connect the extension rack. This cable supports the HSL protocol and must not be
connected to the Ethernet network.
Note 1:
This port requires an installed HSL daughterboard .
- Module2: this port is used to connect to the second extension rack. Use a straight RJ45
cable to connect the extension rack. This cable supports the HSL protocol and must not be
connected to the Ethernet network.
Note 2:
This port requires an installed HSL daughterboard .
- Audio: this port is used to connect to an external an music-on-hold device
table 7.3: Audio Port Connections
1 2 3 4 5 6 7 8 Shield
Audio In Audio In Audio Audio Audio Audio Alarm A Alarm B GND
A B Ctrl A Out A Out B Ctrl B
Audio_Out: External loudspeaker, alarm, general ringing interfaces; 12V output

Audio_In: On-hold message and background music interfaces
Note 3:
This port requires the AFU daughterboard installed
- Misc: Doorphone feature not used
- USB: not used
7.2.3 CS and GA Boards
7-2 !"# $ % $ &'( ! ) $

59 of 459

**

RJ45 pin 1 2 3 4 5 6 7 8
LAN/WAN TX+ TX- RX+ RX-
CONFIG CTS DSR RX Ground Ground TX DTR RTS
Up-link TX+ TX- RX+ RX-
Unit 1 to 3 RX+ RX- TX+ TX-
- LAN: Ethernet 10/100 Base T (MDI-II/straight cable).

- WAN: Ethernet 10/100 Base T (MDI-II/straight cable), connection to an ADSL modem
- UNIT1, UNIT2, UNIT3: Integrated LAN Switch ports (MDI-X/crossed cable).
- UPLINK: Integrated LAN Switch up-link (MDI-II/straight cable).
- CONFIG: for system console.
7.2.4 GA-3 Board

- LAN: this port is used to connect to an Ethernet network. Use a straight RJ45 cable to
connect to a LAN switch (or an hub).
- LAN2: As of R11.1, this port is used to connect to an Ethernet network. Use a straight
RJ45 cable to connect to a LAN switch (or a hub).
LAN and LAN2 interfaces can be connected simultaneously for redundancy purposes.
Before R11.1, this LAN2 interface is not used.
- Config: this port is used for GA-3 board local configuration. Use the 3EH75003AA cable
(RJ45/SUBD9) to connect to a VT100 (or emulation) configuration console.
- UNIT 1: this port is the first LAN switch port. This port requires the SLANX optional
daughterboard.
- UNIT 2: idem UNIT 1
- UNIT 3: idem UNIT 1
- UP-LINK: this port is used to connect to a LAN network. This port requires the SLANX
optional daughterboard.
- USB connector: not used
7.2.5 MEX Board

Main: this port is used to connect to the main rack via a straight RJ45 cable. This cable
supports the HSL protocol and must not be connected to the Ethernet network.
7.2.6 PowerMEX Board

- Main: this port is used to connect to the main rack via a straight RJ45 cable. This cable
supports the HSL protocol and must not be connected to the Ethernet network.
- Pilot-CK: used to synchronize system with an external clock (512KHz)
table 7.5: Pilot-CK Connections
!"# $ % $ &'( ! ) $

7-3
60 of 459
Chapter 7
**

1 2 3 4 5 6 7 8 Shield
LS1Y1 LS1Y2
7.3 Types of Cable to Be Used

Access Type Impedance
Ethernet UTP, FTP or STP, Category 5 100 Ohms
HSL STP provided with the product, Category 5 100 Ohms
Cable length : 5m (16.4')
- UTP: Unshielded Twisted Pairs

- FTP: Foiled Twisted Pairs
- STP: Shielded Twisted Pairs
7.4 Example Connection

This example shows the Ethernet connection of two CSs (duplicated configuration), one GA
and two local GDs to a LANX16.
The entire assembly is connected to the data network via an external LAN switch.
A third, remote GD is connected to the assembly via the LAN.
Remark:
the signalisation between GA and GD boards is made through the IP network.
7-4 !"# $ % $ &'( ! ) $

61 of 459

**

!"# $ % $ &'( ! ) $

7-5
62 of 459
Chapter 7
**

7-6 !"# $ % $ &'( ! ) $

63 of 459

8.1 General
After describing the pinout of board RJ45 output connectors and reviewing the cables to be
used for external connection, this module goes on to describe the different connections to be
made between the system and the outside world (management PC, terminals, DECT or PWT
base stations, public network and also to the customer LAN and optional devices).
8.2 Output Connector Pinout

All outputs are made using female RJ45 connectors.
8.2.1 SLI board
RJ45 pin 1 2 3 4 5 6 7 8
1 to 16 ZA ZB
1 to 16: Connection of Z analog terminals.
8.2.2 UAI Board
RJ45 pin 1 2 3 4 5 6 7 8
1 to 16 L1 L2
1 to 16: Connection of Alcatel Reflexes terminals or DECT or PWT base stations.
8.2.3 BRA Board
RJ45 pin 1 2 3 4 5 6 7 8
1 to 8 TX+ RX+ RX- TX-
!"# $ % $ &'( ! ) $

8-1
64 of 459
Chapter 8 3
**

1 to 8: connection of T0 basic access.
8.2.4 PRA-T1, T1 CAS, PRA-T2, PRA DASS2 and PCM R2 Board
RJ45 pin 1 2 3 4 5 6 7 8
NETW II RX+ RX- TX+ TX-
PBX X TX+ TX- RX+ RX-
NETW II: Connection to the public network (TNL).

PBX X: use on a private network with crossed TX and RX pairs.
8.2.5 LAN X Board
RJ45 pin 1 2 3 4 5 6 7 8
Ports 1 to 15I RX+ RX- TX+ TX-
Up-link TX+ TX- RX+ RX-
Port 1 to 15: internal ports.

Up-link: LAN connection
8.2.6 APA 2, 4 and 8 Boards
RJ45 pin 1 2 3 4 5 6 7 8
1 Z set Z set RING_B1 Tip_A1 ZB1 ZA1
B1 A1
2 to 8 RING_B Tip_A
Connector 1:
- Z set B1 and Z set A1 : connection to a Z set for LR line call forward function (*).
- ZB1 and ZA1: connection to an SLI board device for LR line call forward function (*).
- Ring_B and Tip_A: connection to an analog trunk line.
Connectors 2 to 8: connection of analog trunk lines.
(*) : for further details concerning the LR line call forward function, consult Analog Public
Network .
8.3 Types of Cable to Use

Access Type Impedance
Alcatel Reflexes, Z, T0, UTP, FTP or STP, category 3 or 5 100 or 120 Ohms
analog trunk line
T1, T2 UTP, FTP or STP, category 3 or 5 120 Ohms
Ethernet UTP, FTP or STP, Category 5 100 Ohms
8-2 !"# $ % $ &'( ! ) $

65 of 459
3
**

UTP: Unshielded Twisted Pairs

FTP: Foiled Twisted Pairs
STP: Shielded Twisted Pairs
8.4 Connecting a PC
8.4.1 System Management
8.4.2 Configuring the GD Board
8.5 Connecting Terminals
8.5.1 Connecting Alcatel Reflexes Terminals

Terminals are equipped with a cable and telephone jack for a wall-mounted socket. Each
terminal is connected with a pair of 0.5 or 0.6 mm diameter wires.
Distance between the system and Alcatel Reflexes terminal:
- SYT 0.5 mm cable: 800 m (terminal with no options) or 600 m (terminal with S0 or Z
option)
- 278 0.6 mm cable: 1200 m (terminal with no options) or 850 m (terminal with S0 or Z
option)
!"# $ % $ &'( ! ) $

8-3
66 of 459
Chapter 8 3
**

For more information on the connection and wall mounting of each Reflexes terminal, see
Small & Large racks - External connections.
8.5.2 Connecting Analog Terminals

Terminals are equipped with a cable and telephone jack for a wall-mounted socket. Each
terminal is connected with a pair of 0.5 or 0.6 mm diameter wires (1.3 Km max. with 0.5 mm
cable).
8-4 !"# $ % $ &'( ! ) $

67 of 459
3
**

8.6 Connecting DECT or PWT Base Stations

The Alcatel 4070 IO base station is designed to be installed inside the building (indoors),
whereas the Alcatel 4070 EO base station is designed for outdoor installation.
A base station can be connected to 1 or 2 UA links (UAI boards) and allows 3 or 6
simultaneous calls with DECT/PWT or GAP terminals.
The requirement for three or six communication channels depends on the number of wireless
terminals and the traffic to be handled.
If connection is with two cables:
- use two adjacent UAI board interfaces
- use the even interface for the master link and the other for the slave link.
The two cables must be of the same length. The first interface of the system UAI16 board must
not be used as the attendant console uses these points.
!"# $ % $ &'( ! ) $

8-5
68 of 459
Chapter 8 3
**

Note:
A preliminary survey must be performed using coverage tools. Base stations are then installed according
to survey results.
8.7 Connecting to the Public Network
8.7.1 Digital Public Network via T0 Access (or S0-FV for Germany)
The Alcatel system can be installed near the DNT (Digital Network Termination) or, according
to requirements, remote at a distance (350 m maximum).
8-6 !"# $ % $ &'( ! ) $

69 of 459
3
**

8.7.2 Digital Public Network via T1 or T2 Access
The PRA board is connected to a Digital Line Termination (DLT) via 2 symmetrical twisted
pairs.
!"# $ % $ &'( ! ) $

8-7
70 of 459
Chapter 8 3
**

Cable impedance:120 Ohms +/- 20 % between 200 KHz and 1 MHz; 120 Ohms +/- 10 % at 1
MHz.
Use L120 series cable (or equivalent L204).
The T1/T2-DLT distance is limited by attenuation between DLT and T1/T2 that must not
exceed 6 dB at 1024 kHz.
8.7.3 Analog Public Network

The APA board is used to connect theAlcatel-Lucent OmniPCX Enterprise CS to the public
network via analog lines. Two types of connection are offered:
- Connection without LR line forwarding, available on all APA board devices.
- Connection with LR line forwarding, available on the first APA board device. In the event of
a power supply failure or computer fault, this solution allows the line connected to the first
equipment of the APA board to be diverted to one of the system's analog terminals.
These two types are listed in APA board - Connection.
8.8 Connecting the LAN

The LANX16 board can be used to connect servers, PCs, Fast IP Reflexes (IP phones)
terminals and external switches.
8-8 !"# $ % $ &'( ! ) $

71 of 459
3
**

8.9 Connecting Auxiliary Equipment (on a GD or GD-3 Board)

All auxiliary equipment must be connected to the AUDIO-IN and AUDIO-OUT connectors of
the GD board.
8.9.1 Connecting an On-Hold Message Device

Connection is via the AUDCTRL output (normally-open control contact) and the AUDIO-IN
input of the AUDIO-IN connector.
8.9.1.1 Audio Input Characteristics

- Input impedance: 600 Ohms
8.9.1.2 Contact Characteristics
- Max. power : 10 W
- Max. voltage : 60 V
- Max. current : 500 mA
The contacts of the alarm control have the same electrical characteristics as those given
above.
8.9.2 Connecting a Background Music Tuner

Connection is via the AUDIO-IN input of the AUDIO-IN connector.
!"# $ % $ &'( ! ) $

8-9
72 of 459
Chapter 8 3
**

Audio input Characteristics:

- Input impedance: 600 Ohms
- Input level: access +10 dBr
8.9.3 Connecting an Alarm

The alarm is activated in the event of a system failure.
Connection is via the ALARM output (normally-closed control contact) of the AUDIO-OUT
connector.
8-10 !"# $ % $ &'( ! ) $

73 of 459
3
**

8.9.4 Connecting an External Loudspeaker

Connection is via the AUDIO-OUT output of the AUDIO-OUT connector.
Audio output characteristics:

- Output impedance: < 500 Ohms
- Output level: access +3 dBr
!"# $ % $ &'( ! ) $

8-11
74 of 459
Chapter 8 3
**

8.9.5 Connecting a General Ringer

Connection is via the CENRG output of the AUDIO-OUT connector.
8.9.6 Use of the 12 V Output of the AUDIO-OUT Connector

The GROUND and + 12V outputs of the AUDIO-OUT connector can be used to connect an
external device supplied with 12 V when consumption does not exceed 150 mA (S Rack) or
300 mA (L Rack).
8.9.7 Connections for Remote Maintenance

Detailed description of RMA and MOBD board connections can be found in RMA - Installation
procedure.
8-12 !"# $ % $ &'( ! ) $

75 of 459

9.1 Connecting the Protective Ground

Connection can be made to electrical installations of any of the following types:
- TT (EE) (local ground for each unit)
- TN (common ground for all units)
- IT with 230V mesh voltage (only in Norway)
Mains socket fuse: T2.5 AH / 250V (time-delayed, high breaking capacity).
The system is delivered with a 3 m (9.8') three-wire cable to be connected to the mains power
socket.
Permanent ground
The system must be permanently grounded due to leakage currents in excess of 3.5 mA on all
line accesses (safety restriction CEI60950 ed.03). To achieve this, use a ground wire with a
cross-sectional area of 4 mm2 minimum (8AWG), connected to the stud at the rear of the rack
(left hand side).
Summary:
!"# $ % $ &'( ! ) $

9-1
76 of 459
Chapter 9 1 **

9.2 Using Internal Batteries

All racks have their own Power Supply Unit to be connected to the mains. If there is a mains
cutoff, batteries allow correct system shutdown.
Batteries are attached to a support fixed with a collar fitted to the back panel.
These internal batteries can be replaced by an external battery rack (see the Optional External
Battery Rack ).
9.2.1 Battery Switch
9-2 !"# $ % $ &'( ! ) $

77 of 459
1 **

Batteries are insulated during transport by a switch soldered to the power supply board.
Plugging the mains cable into the socket closes this switch by means of a lever integrated in
the mains socket.
9.2.2 Battery Fuse

The battery fuse is located on the board, the back panel must be removed for access. Fuse
characteristics:
- S Rack: 6.3 A quick-acting, low breaking capacity (F 6.3 AL/250 V).
- L Rack: 10 A quick-acting, low breaking capacity (F 10 AL/250 V).
9.2.3 Replacing the Batteries

See the Small & Large racks - Maintenance .
9.3 Connecting a UPS (Uninterruptible Power Supply) - Optional
9.3.1 Overview
To extend the autonomy of the Alcatel-Lucent OmniPCX Enterprise CS in the event of a
prolonged mains power failure, a UPS can be used with it.
The different models of UPS are:
- the MGE UPS Systems Pulsar ellipse which comes in three variants: 300, ASR 375, 650S,
ASR 1000, 1200S and ASR 1500. It ensures one hour minimum additional autonomy
depending on the configuration.
Each of these models is serially equipped with a battery and delivered with two IEC-type
mains cords. A serial cord, as well as an error control and security software program, are
also delivered with models 650S and 1200S.
- the MGE UPS Systems Pulsar EXtreme C which comes in two variants: 1000 and 1500.
With one to three Pulsar EXB battery extension modules, it provides a minimum of four
hours of additional autonomy depending on the configuration.
Each Pulsar EXtreme C is serially equipped with a battery and delivered with:
two IEC-type mains cords
an EXB extension module with its specific connection cord to the Pulsar EXtreme C
Each additional EXB extension module is delivered with its specific cord.
- The MGE Evolution S, which comes in two variants:
3EH76210AA: POWER BACK-UP 1250 (100W/1h30)
3EH76211AA: BATTERY PACK 1250 (+100W:4h)
9.3.2 Connecting a Pulsar ellipse Type UPS

9.3.2.1 Characteristics
This paragraph is not complete, it only provides basic data required to install a Pulsar ellipse in
an Alcatel-Lucent OmniPCX Enterprise CS environment. For further information on the Pulsar
ellipse, connect to the site www.mgeups.fr or www.mgeups.com .
!"# $ % $ &'( ! ) $

9-3
78 of 459
Chapter 9 1 **

9.3.2.1.1 Connectors
The Pulsar ellipse 300, ASR 375, 650S, ASR 1000, 1200S and ASR 1500 are shown below:
Remarks:
- Pulsar ellipse 1200S connectors are identical to those of the 650S.
- Non referenced connectors must not be used to connect Alcatel-Lucent OmniPCX Enterprise CS
racks.
9.3.2.1.2 System Configuration/Pulsar ellipse
The choice of a Pulsar ellipse depends on the Alcatel-Lucent OmniPCX Enterprise CS
environment. The following table shows the possible System - Pulsar ellipse associations:
Basic configuration Add-ons
System Pulsar ellipse System Pulsar ellipse
+ one S rack + 300/ASR 375 (*)
One S rack 300/ASR 375
+ one L rack + 1200S/ASR 1500
+ one S rack + 300/ASR 375
Two S racks 650S/ASR 1000
One S rack
1200S/ASR 1500 + one L rack + 1200S/ASR 1500
+ one L rack
(**)
One L rack 1200S/ASR 1500
9-4 !"# $ % $ &'( ! ) $

79 of 459
1 **


Two L racks 1200S/ASR 1500
(*): in order to ensure that there are two Pulsar ellipses for installation.
(**): it is necessary to review system configuration, i.e. redistribution of racks on the Pulsar
ellipses.
Remark:
If a Pulsar ellipse 300 is listed in the table, an ASR 375, a 650S, an ASR 1000, a 1200S or an ASR 1500
can be used instead.
9.3.2.1.3 System Capacities/Pulsar ellipse

This table shows the system's autonomy (in minutes) according to the total power of the
Alcatel-Lucent OmniPCX Enterprise CS (Wdc) and of the selected UPS model. All the values
indicated in Watts are measured at the secondary winding (on the charger).
(*): Wdc = Power used (boards + sets) + 7.2 W dc (S Rack)

(on the charger) (as calculated by ACTIS or in manual tables) 19.6 W dc (L Rack)
The graphic form of this table is shown below:
!"# $ % $ &'( ! ) $

9-5
80 of 459
Chapter 9 1 **

9.3.2.2 Installation
Safety recommendations:
Before installation, read the safety instructions in the installation and operation guide
provided with the Pulsar ellipse.
Operating temperature below 35 C (with relative humidity lower than 95%).
Sequence with the Pulsar ellipse connection procedure to various system devices. The
9-6 !"# $ % $ &'( ! ) $

81 of 459
1 **

procedure is also described in the Pulsar ellipse installation and operation guide.
In order to simplify this document, only the Pulsar ellipse connection procedure to the
Alcatel-Lucent OmniPCX Enterprise CS is described. It includes three phases:
1. Choice of the Pulsar ellipse according to the system configuration. To do this, refer to
System Configuration/Pulsar ellipse and System Capacities/Pulsar ellipse .
2. Connecting the rack(s) of the Alcatel-Lucent OmniPCX Enterprise CS to the Pulsar ellipse.
Several configurations are possible:
a. Connect the Pulsar ellipse to a rack of the Alcatel-Lucent OmniPCX Enterprise CS (S
or L rack).
Example 1:
Configuration with an L rack
Procedure:
Connect the Pulsar ellipse to the wall-mounted socket (mains). To do this use the
mains cord provided with the L rack.
Connect the Pulsar ellipse to the mains socket on the rear face of the L rack. To do
this, use one of the two mains cords provided with the Pulsar ellipse.
Reminder 1:
For connectors on the rear face of the Pulsar ellipse, refer to Connectors .
b. Connect the Pulsar ellipse to two racks of the Alcatel-Lucent OmniPCX Enterprise CS
(S and/or L racks).
Example 2:
Configuration with two L racks
!"# $ % $ &'( ! ) $

9-7
82 of 459
Chapter 9 1 **

Procedure:
Connect the Pulsar ellipse to the wall-mounted socket (mains). To do this use the
mains cord provided with one of the two L racks.
Connect the Pulsar ellipse to each of the mains sockets on the rear face of the L
racks. To do this, use the two mains cords provided with the Pulsar ellipse.
Reminder 2:
c. Connect the Pulsar ellipse to three racks of the Alcatel-Lucent OmniPCX Enterprise
CS (S and/or L racks).
It is prohibited to connect more than two racks to a Pulsar ellipse. When there are more
than two racks, it is necessary to use two Pulsar ellipses.
It is also prohibited to install two cascaded Pulsar ellipses.
Example 3:
Configuration with two L racks and an S rack
9-8 !"# $ % $ &'( ! ) $

83 of 459
1 **

Procedure:
Connect each Pulsar ellipse to a wall-mounted socket (mains). To do this use the
mains cords provided with the L and S racks.
Connect the first Pulsar ellipse to the mains sockets on the rear face of the L racks.
To do this, use the two mains cords provided with this Pulsar ellipse.
Connect the second Pulsar ellipse to the mains socket on the rear face of the S
rack. To do this, use one of the mains cords provided with the Pulsar ellipse.
!"# $ % $ &'( ! ) $

9-9
84 of 459
Chapter 9 1 **

Reminder 3:
9.3.2.3 Use
Once the connections have been made, refer again to the Pulsar ellipse installation and
operation guide. It provides all data and specifications needed to operate the Pulsar ellipse.
9.3.2.4 Maintenance
A standard exchange of Pulsar ellipse batteries can be performed. In this case, follow the
instructions provided in the Pulsar ellipse installation and operation guide.
This operation must be performed by a qualified person (electric shock hazard).
Cut off the power supply of the Pulsar ellipse before exchanging batteries.
Replace batteries exclusively by batteries recommended by MGE UPS Systems.
9.3.3 Connecting a Pulsar EXtreme C Type UPS

9.3.3.1 Characteristics
This paragraph is not complete, it only provides basic data required to install a Pulsar EXtreme
C in an Alcatel-Lucent OmniPCX Enterprise CS environment. For further information on the
Pulsar EXtreme C, connect to the site www.mgeups.fr or www.mgeups.com .
9.3.3.1.1 Connectors
The Pulsar EXtreme C 1000 or 1500 is shown below:
9.3.3.1.2 System Capacities/Pulsar EXtreme C

This table shows the system's autonomy (in minutes) according to the total power of the
Alcatel-Lucent OmniPCX Enterprise CS (Wdc) and of the selected UPS model (with one, two
or three EXB extension modules). All the values indicated in Watts are measured at the
secondary winding (on the charger).
9-10 !"# $ % $ &'( ! ) $

85 of 459
1 **

(*): Wdc = Power used (boards + sets) + 7.2 W dc (S Rack)

(on the charger) (as calculated by ACTIS or in manual tables) 19.6 W dc (L Rack)
The graphic form of this table is shown below:
!"# $ % $ &'( ! ) $

9-11
86 of 459
Chapter 9 1 **

Safety recommendations:
Before installation, read the safety instructions in the installation and operation guide
provided with the Pulsar EXtreme C.
Sequence with the Pulsar EXtreme C connection procedure to the various system devices.
The procedure is also described in the Pulsar EXtreme C installation and operation guide.
In order to simplify this document, only the Pulsar EXtreme C connection procedure to the
Alcatel-Lucent OmniPCX Enterprise CS is described below. It includes three phases:
1. Choice of the Pulsar EXtreme C and of its EXB extension modules according to system
configuration. To do this, refer to System Capacities/Pulsar EXtreme C .
2. Connecting EXB extension module(s) to the Pulsar Extreme. Three configurations are
possible:
a. Pulsar EXtreme C + one EXB extension module:
Use the cable supplied with the EXB extension module.

b. Pulsar Extreme C + two EXB extension modules:
9-12 !"# $ % $ &'( ! ) $

87 of 459
1 **

Use the cables supplied with the EXB extension modules.

c. Pulsar EXtreme C + three EXB extension modules:
Use the cables supplied with the EXB extension modules.

3. Connecting the Alcatel-Lucent OmniPCX Enterprise CS rack(s) to the Pulsar EXtreme C.
Several configurations are possible:
a. Connecting the Pulsar EXtreme C to a rack of the Alcatel-Lucent OmniPCX Enterprise
CS (S or L rack).
Example 1:
Configuration with an L rack
!"# $ % $ &'( ! ) $

9-13
88 of 459
Chapter 9 1 **

Procedure:
Connect the Pulsar EXtreme C to the wall-mounted socket (mains). To do this, use
the mains cord provided with the L rack.
Connect the Pulsar EXtreme C to the mains socket on the rear face of the L rack.
To do this, use one of the two mains cords provided with the Pulsar EXtreme C.
Reminder 1:
For connectors on the rear face of the Pulsar EXtreme C, refer to Connectors .
b. Connect the Pulsar EXtreme C to two or three racks of the Alcatel-Lucent OmniPCX
Enterprise CS (S and/or L racks).
Example 2:
Configuration with two L racks
9-14 !"# $ % $ &'( ! ) $

89 of 459
1 **

Procedure:
Connect the Pulsar EXtreme C to the wall-mounted socket (mains). To do this use
the mains cord provided with one of the two L racks.
Connect the Pulsar EXtreme C to each of the mains sockets on the rear face of the
L racks. To do this, use the two mains cords provided with the Pulsar EXtreme C.
(If necessary) also connect the Pulsar EXtreme C to the mains socket on the rear
face of the third S or L rack. An additional mains cord is required.
Reminder 2:
For connectors on the rear face of the Pulsar EXtreme C, refer to Connectors .
9.3.3.3 Use
Once the connections have been made, refer again to the Pulsar EXtreme C installation and
operation guide. It provides all data and details required to operate the Pulsar EXtreme C.
9.3.3.4 Maintenance
A standard exchange of the Pulsar EXtreme C battery can be performed. In this case, follow
the instructions provided in the Pulsar EXtreme C installation and operation guide.
!"# $ % $ &'( ! ) $

9-15
90 of 459
Chapter 9 1 **

This operation must be performed by a qualified person (electric shock hazard).

Replace the battery exclusively with a battery recommended by MGE UPS Systems.
9.4 Optional External Battery Rack
9.4.1 Presentation
9.4.1.1 Overview
The external battery rack is used to increase the operating autonomy on S or L type rack
batteries. Although the internal battery only ensures a few minutes of autonomy, the external
battery rack ensures between one and eight hours of operation, depending on configuration.
The use of an external battery rack requires:
- Specific S and L racks (see References ). These racks do not have internal batteries, but
instead have a connector to connect an external battery rack. The external battery rack is
intended to operate with software version R5.1.2 or above.
- Specific CS board micro switches setting, when the CS board is in controller position in the
S or L rack. The micro switches setting must correspond to the 0x09 value (see Small &
Large racks - Hardware description - CS Board ). If this value is different from 0x09, the CS
board cannot monitor the activity of an external battery rack (e.g. to detect the end of
battery autonomy).
There are two types of external battery racks:
- The 12V battery rack which is used to back up an S type rack. This rack can contain two or
three batteries.
- The 36V battery rack which is used to back up an L type rack. This rack can contain three
or six batteries.
Figure 9.21: System Rack and its Battery Rack

An external battery rack can only back up a system rack. The system rack can be used to host
the Call Server, either as Media Gateway or as extension rack.
9-16 !"# $ % $ &'( ! ) $

91 of 459
1 **

Battery racks are fitted with 12V / 7Ah type batteries in series or in parallel. A battery rack does
not have a charger. The system rack power supply recharges the batteries.
The batteries are usually provided by Alcatel-Lucent. It is possible, however, to use compatible
batteries. The installer should ensure that all the batteries in a rack are provided by the same
manufacturer and, if possible, are of identical release. If this is not the case, the life time of the
unit may be affected.
As of R6.2, there are two packages for the batteries:
- 2U/12V Battery Rack and 2U/36V Battery Rack,
- 12V Battery Box and 36V Battery Box
The 2U Battery Racks and Battery Boxes use the same battery element (12V/3Ah). In the two
cases, the PCX autonomy is identical.
Caution:
The 2U/12V Battery Rack or 12V Battery Box should only be connected to a 1U rack. The 2U/36V
Battery Rack or 36V Battery Box should only be connected to a 3U rack. If this is not the case,
there is a risk of damaging racks.
9.4.1.2 Operation
When the mains power is cut off, the system automatically switches to batteries. The power
supply of the system rack sets the electric Batmode signal to battery.
The board in the controller position (GD or CS) monitors this Batmode signal.
- When switching to batteries, this board generates an incident (incident no. 1544 if the CS
is in the controller position; incident 5856 if the GD is in the controller position).
- If the mains power returns, an incident is generated (incident no. 1545 if the CS is in the
controller position; incident 5858 if the GD is in the controller position).
- If battery autonomy expires (battery low), incident 1521 is generated if the CS is in the
controller position. Boards GD, GA and CS in the rack stop (shutdown).
Compatibility between software and hardware versions
New hardware and software prior to R5.1.2: it is necessary to place the strap (delivered with
the rack) on the power supply board (see details for placing the strap: Small & Large racks -
Maintenance - Replacing a Board). No incident is generated when changing to battery mode.
The shutdown is carried out after a time predefined by the swinst tool (1 mn by default).
Old hardware and software R5.1.2 or above: the system rack operates with the internal
batteries (low autonomy). The loss of the mains power causes the Call Server to shut down
after a time specified in the configuration. No incident is sent to the administrator.
9.4.1.3 Autonomy
The following table gives examples of autonomy according to the configuration.
!"# $ % $ &'( ! ) $

9-17
92 of 459
Chapter 9 1 **

Autonomy 12V Batteries 12V Batteries 36V Batteries 36V Batteries

Rack Rack Rack Rack
or 12V Battery or 12V Battery or 36V Battery or 36V Battery
Box Box Box Box
Two elements Three elements Three elements Six elements
Small rack with 8h 16 h not applicable not applicable
dedicated Call
Server
(17W)
Small rack 2h 3h not applicable not applicable
(53 W) (4 h if < 46W)
Large rack not applicable not applicable 1h 3h
(110 W) (4 h if < 92W)
9.4.2 Characteristics
9.4.2.1 2U Battery Rack
Weight:
Weight when empty: 5 kg (11 lb)
Weight of a 12V / 7Ah battery: 2.64 kg (5.8 lb)
Maximum weight (36V configuration with six batteries): 20.84 kg (45.9 lb)
Maximum weight (12V configuration with three batteries): 12.92 kg (28.4 lb)
Operating temperature: +5C to + 40C (41F 104F)
Humidity: +5% to 85% without condensation.
Dimensions:
The battery rack is compatible with standard IEC/UL 60950.
9-18 !"# $ % $ &'( ! ) $

93 of 459
1 **

Environment:
Storage: Class 1.1
Transportation: Class 2.3, shocks ETS300019 requires 0.8 fall test (with packaging)
Operation: Class 3.1
9.4.2.2 Battery Box
Weight:
Weight when empty: 0.90kg (1.98 lb)
Maximum weight (configuration with three batteries): 8.85kg (19.5 lb)
Operating temperature: +0C to + 40C (32F 104F)
Humidity: +5% to 90% without condensation.
Dimensions:
Battery Protection:fuse (5x20mm) 10A slow in negative line.

9.4.2.3 Batteries
Alcatel-Lucent recommends batteries with the following characteristics:
- Dimensions: 151 mm x 65 mm x 97.5 mm (5.9 x 2.5 x 3.8)
- Type: 12V / 7Ah sealed lead battery
- Flammability: UL94V-2 minimum
- Compatible with the following standards:
IEC60950ed03 or EN 60950
CAN/CSA C22.2 no.95095 or UL 60950ed03 (USA and Canada)
Storage: Class 1.1
If the characteristics above are not respected, Alcatel-Lucent accepts no liability.
9.4.2.4 References
!"# $ % $ &'( ! ) $

9-19
94 of 459
Chapter 9 1 **

References Description
3EH76027AD Large 230V rack with internal batteries
3EH76027AE Large 230V rack adapted for external batteries
3EH76027BD Large 110V rack with internal batteries
3EH76027BE Large 110V rack adapted for external batteries
3EH76020AD Small 110/230V rack with internal batteries
3EH76020AE Small 110/230V rack adapted for external batteries
3EH76155AB 2U/36V rack for three/six 12V batteries
3EH76155AA 2U/+12V rack for two/three 12V batteries
3EH76177AB 12V Battery Box for three 12V batteries
3EH76177AC 36V Battery Box for three 12V batteries
3EH76156AA 12V 7Ah battery
3EH76152AA Cord for external batteries
9.4.3 Storage
Prolonged storage harms the battery quality and performance. For prolonged storage, consult
the battery manufacturer's instructions.
9.4.4 Installation Procedure

9.4.4.1 Precautions
The batteries should be installed on the site. They should not be transported in the rack.
Read the instructions placed on the rack:
9-20 !"# $ % $ &'( ! ) $

95 of 459
1 **

Figure 9.24: Safety Label

Safety instructions
Before use, read the instructions given by the battery manufacturer.
Risks when using batteries
Electrical risk:
Each battery element must have a protection adapted to the power supply and to the link
cables.
An adapted circuit breaker or fuse must be provided to insulate the batteries in the event of a
short circuit. The short circuit current is given by the battery manufacturer.
The 12V Battery Rack or Battery Box should only be connected to a 1U rack. The 36V Battery
Rack or Battery Box should only be connected to a 3U rack. If this is not the case, there is a
risk of damaging racks.
Risk of injury:
The metallic parts of the batteries are live. There is a risk of an electric shock or a short circuit.
Only come in contact with the insulated parts of the batteries. In particular, non-insulated tools
should not be used and bracelets and rings should not be worn.
Risk of explosion:
Regardless of the conditions for use, hydrogen may escape from the batteries through the
pressure relief valves. As a result, under no circumstances should you use the Batteries Rack
or Battery Box in an unventilated area.
9.4.4.2 Preliminary Operations
!"# $ % $ &'( ! ) $

9-21
96 of 459
Chapter 9 1 **

It is recommended to carry out two battery charge/discharge cycles before installation. This
operation is used to obtain the optimum battery characteristics. This operation is not necessary
if the batteries have been stored for less than nine months at a temperature of between 20
25C (max 30C).
Before installation, the batteries must be fully charged.
9.4.4.3 Installing Batteries in a 2U/12V Rack
1. Open the rack (remove the attachment screws from the cover).
2. Place the batteries in the vertical position.
3. Depending on whether the rack has two or three batteries, wire it as shown in the following
figure:
Figure 9.25: Wiring the 2U/12V Rack

If there are two batteries, do not remove the insulating material from the free connectors.
4. Place the batteries as shown in the following figure:
9-22 !"# $ % $ &'( ! ) $

97 of 459
1 **

Figure 9.26: Position of the Batteries in a 2U/12V Rack

Note 1:
Pay particular attention to the running of the cables (do not trap them in the metallic parts).
5. Close the rack (put the attachment screws back in place).
6. Close the switch and check the 12V battery voltage on the rear connector.
Note 2:
For a 12V rack, the terminal of the batteries is linked to the ground by the system rack.
9.4.4.4 Installing Batteries in a 2U/36V Rack

1. Open the rack (remove the attachment screws from the cover).
2. Place the batteries in the vertical position.
3. Depending on whether the rack has three or six batteries, wire it as shown in the following
figure:
Figure 9.27: Wiring the 2U/36V Rack

If there are three batteries, do not remove the insulating material from the free connectors.
The free connection cables should not be stored inside the battery rack.
!"# $ % $ &'( ! ) $

9-23
98 of 459
Chapter 9 1 **

Figure 9.28: Position of the Battery in a 2U/36V Rack

Note 1:
Pay particular attention to the running of the cables (do not trap them in the metallic parts).
5. Close the rack (put the attachment screws back in place).
6. Close the switch and check the 36V battery voltage on the rear connector.
Note 2:
For a 36V rack, the + terminal of the batteries is linked to the ground by the system rack.
9.4.4.5 Installing Batteries in a 12V Battery Box

The 12V battery box can be used with S systems. It uses 12V - 7Ah batteries. Up to three
batteries can be installed in the unit.
1. Ensure that the ON/OFF switch on the external battery unit is set to the OFF position (0 or
black) and that there is no cable connected to the J1 connector (see the figure below).
2. Open the unit by removing the four screws (ST3.5x32) with a screwdriver (Phillips PH2).
3. Insert the batteries in the open unit as follows (also see the figure below):
9-24 !"# $ % $ &'( ! ) $

99 of 459
1 **

a. If 2 batteries are to be used, the slots B1 and B3 are used.

b. If three batteries are to be used, the slots B1, B2 and B3 are used.
4. Connect the negative (black) terminals of the batteries as described below (and shown in
the figure below).
5. Connect the positive (red) terminals of the batteries as described below (and shown in the
figure below).
!"# $ % $ &'( ! ) $

9-25
100 of 459
Chapter 9 1 **

6. Close the unit and secure it with the four screws.

7. Stick a label on the unit stating the date of the installation and the number of batteries
installed.
9.4.4.6 Installing Batteries in a 36V Battery Box
The 36V battery box can be used with L systems. It uses three 12V - 7Ah batteries. Two
external battery units can be connected in parallel to obtain the autonomy achieved with six
batteries.
1. Ensure that the ON/OFF switch on the external battery unit is set to the OFF position (0 or
black) and that there is no cable connected to the unit (see the figure below).
2. Open the unit by removing the four screws (ST3.5x32) with a screwdriver (Phillips PH2).
3. Insert the three batteries in the open unit, into the positions B1, B2 and B3 (see the figure
below).
9-26 !"# $ % $ &'( ! ) $

101 of 459
1 **

4. Connect the terminals of the batteries strictly in the order detailed below (also see the
figure below).
a. Connect the black wire to the negative (black) terminal of battery B1.
b. Connect a yellow wire between the positive (red) terminal of battery B1 and the
negative (black) terminal of battery B2.
c. Connect a yellow wire between the positive (red) terminal of battery B2 and the
negative (black) terminal of battery B3.
d. Connect the red wire to the positive (red) terminal of battery B3.
5. Close the unit and secure it with the four screws.

6. Stick a label on the unit stating the date of the installation and the number of batteries
installed.
7. If you wish to use two external battery units in parallel, continue as follows (also see figure
below):
a. Insert the batteries in the extension unit and connect it (see step 3 to 6).
b. Place the two units side by side, or one on top of the other.
c. Connect the two units using the extension cable between the J2 connectors on the
units; the cable's Mate-N-Lok 3-terminal connector must be connected to the principal
unit and its Mate-N-Lok 2-terminal connector must be connected to the extension unit.
!"# $ % $ &'( ! ) $

9-27
102 of 459
Chapter 9 1 **

9.4.5 Assembling the Battery Rack

Place the Battery Rack in a 19" cabinet no more than 2m (6.5') from its system rack. Supports
are required due to the weight, which may be as much as 21Kg (46lb). Leave a 15 mm (0.59)
space above the rack for ventilation. Do not obstruct the vent holes.
Figure 9.37: Mounting the External Battery Rack
9.4.6 Connection to the System Rack

1. Open the battery rack switch.
2. Connect the battery rack to its system rack using the link cord (ref: 3EH76152AA):
9-28 !"# $ % $ &'( ! ) $

103 of 459
1 **

Figure 9.38: Connecting the 2U Battery Rack to its System Rack
!"# $ % $ &'( ! ) $

9-29
104 of 459
Chapter 9 1 **

Figure 9.39: Connecting the Battery Box to its System Rack

If several racks coexist in the same cabinet, label the cables to avoid any connection
errors.
3. Close the battery rack switch.
Note:
Every 36V battery box is delivered with an extension cord.
Caution:
The 12V Battery Rack or 12V Battery Box should only be connected to a 1U rack. The 36V Battery
Rack or 36V Battery Box should only be connected to a 3U rack. If this is not the case, there is a
risk of damaging racks.
9.5 48V Battery and Charger Racks
9.5.1 Presentation
9.5.1.1 Overview
As of R6.0 and R5.1.2, the MR1/MR3 racks (also called S & L racks) can be powered with 48V
9-30 !"# $ % $ &'( ! ) $

105 of 459
1 **

DC. Using of 48V DC requires a special rack called MR148V or MR348V.

For 48V DC power supply:
- Alcatel-Lucent offers a 500 W charger rack (recommended). This charger rack can power
up to 3 MR148V/MR348V racks.
The charger rack includes a rectifier and backup batteries. An optional battery rack
provides extended autonomy. According to the autonomy required, there can be up to 8
batteries in the charger rack and up to 8 batteries in battery rack.
Figure 9.40: MR1/MR3 with their Charger and Batteries Racks

- Use an existing 48V DC power supply available on the customer site. The customer power
supply must comply with the table: table: Operation Mode vs Input Voltage . When a 48V
DC customer power supply is used a specific power supply cable is required.
!"# $ % $ &'( ! ) $

9-31
106 of 459
Chapter 9 1 **

Figure 9.41: Example of MR1/MR3 with a Customer 48V DC Power Supply
9.5.1.2 Operation
When the main power cuts off, the charger rack automatically switches to batteries. The
MR148V/MR348V rack detects the switchover by measuring the input voltage level. The
electric "Batmode" signal is set to "Batteries".
The board in the controller position (GD or CS) monitors this Batmode signal.
- When switching to batteries, the GD or CS board generates an incident (incident no. 1544
if the CS is in the controller position; incident 5856 if the GD is in the controller position).
- If the mains power returns, an incident is generated (incident no. 1545 if the CS is in the
controller position; incident 5858 if the GD is in the controller position).
- If the batteries are low, incident 1521 is generated if the CS is in the controller position.
Boards GD, GA and CS in the rack shutdown. 20 minutes after boards are not supplied
anymore.
- When batteries are very low, the charger rack switches off.
Charger rack failure can be notified to the telecom manager through RMA.
The table below summarizes MR148V / MR348V rack behaviors:
table 9.11: Operation Mode vs Input Voltage
9-32 !"# $ % $ &'( ! ) $

107 of 459
1 **

Charger Rack Input External 48V Power Operation Mode CPU Led Status
Voltage (1) supply Input on CS or GD
Voltage(1)
56V 51V 56V 47V normal mode green
51V 45V (2) 47V 45V(2) battery mode orange
<45V (2) <45V(2) shutdown running red flashing
<43V (3) <43V(3) CPU off red
<41.5V (4) <41.5V(4) no supply off
(1): input voltage on MR348V / MR148V rack

(2): 45.2V for MR348V and 44.2V for MR148V
(3): 43.6V for MR348V and 43.2V for MR148V
(4): charger rack disconnection
9.5.1.3 Autonomy with a Charger Rack and a Battery Rack
The table below provides an example of battery configuration according to the configuration
and autonomy required (calculation done on average configuration).
table 9.12: Autonomy Table for Charger Rack and Battery Rack
Autonom 1h 2h 3h 4h 5h 6h 7h 8h
y
Dedic- 4x 4x 4x 4x 4x 4x 4x 4x
ated (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v
rack ) ) ) ) ) ) ) )
server
1x RM1 4x 4x 4x 4x 4x 4x 4x 4x
(7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v
) ) ) ) ) ) ) )
1x RM3 4x 4x 4x 4x 4x 8x 8x 8x
) ) ) ) ) ) ) )
2x RM3 4x 4x 8x 8x 12 x 12 x 12 x 16 x
) ) ) ) ) ) ) )
3x RM3 4x 8x 8x 12 x 12 x 16 x 16 x Out of
(7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v (7Ah/12v range
) ) ) ) ) ) )
Note:
If an external supply is used, refer the manufacturer documentation.
9.5.2 Characteristics
9.5.2.1 Charger Rack
!"# $ % $ &'( ! ) $

9-33
108 of 459
Chapter 9 1 **

Weight:
- Weight when empty: 5.85 kg (12.8 lb)
- Weight of a 12V / 7Ah battery: 2.64 kg (5.8 lb)
- Maximum weight (configuration with four batteries): 16.4 kg (36 lb)
- Maximum weight (configuration with eight batteries): 27 kg (59.5 lb)
Operating temperature: +5C to + 40C (41F . 104F)
Humidity: +5% to 85% without condensation
Dimensions:
Figure 9.42: Charger Rack

The charger rack is compatible with standard IEC/UL 60950.
Electric:
Input voltage: 110V - 230V, 47 - 63 Hz
Output voltage :
- Nominal : 54V
- Operating : 42V - 58V
- Overvoltage protection: 59.5V + or - 0.5V
- Low voltage disconnect threshold: 41.5V + or - 0.5V
- Fuse : each output is protected by a 4A fuse
Environment:
Storage: Class 1.1
9.5.2.2 Extension Battery Rack
9-34 !"# $ % $ &'( ! ) $

109 of 459
1 **

Weight:
Weight when empty: 5 kg (11 lb)
Maximum weight (configuration with four batteries): 15.56kg (34.3 lb)
Maximum weight (configuration with eight batteries): 26.12 kg (57.6 lb)
Operating temperature: +5C to + 40C (41F . 104F)
Humidity: +5% to 85% without condensation
Dimensions:
Figure 9.43: Battery Rack

The battery rack is compatible with standard IEC/UL 60950.
Environment:
Storage: Class 1.1
9.5.2.3 Battery Unit
Alcatel-Lucent recommends batteries with the following characteristics:
- Dimensions: 151 mm x 65 mm x 97.5 mm (5.9. x 2.5. x 3.8.)
- Type: 12V / 7Ah sealed lead battery
- Flammability: UL94V-2 minimum
- Compatible with the following standards:
IEC60950ed03 or EN 60950
CAN/CSA C22.2 no.950.95 or UL 60950ed03 (USA and Canada)
Storage: Class 1.1
!"# $ % $ &'( ! ) $

9-35
110 of 459
Chapter 9 1 **

If the characteristics above are not respected, Alcatel-Lucent accepts no liability.
9.5.2.4 References
References Description
3AB00404AV (*) MR1 RACK MODULE (48V)
3BA00406AV (*) MR3 RACK MODULE (48V)
3EH76181 RACK CHARGER 48V/14AH WITHOUT REC-
TIFIER
3EH79185 RECTIFIER 500W FOR CHARGER RACK
3EH79187 EXTENSION BATTERY RACK
3EH79156 BATTERY 12V/7AH
(*) : according Alcatel-Lucent offers, the suffix "AV" may be changed.
9.5.3 Storage
Prolonged storage harms the battery quality and performance. For prolonged storage, consult
the battery manufacturer's instructions.
9.5.4 Charger Rack Installation Procedure

This part describes the connection of a charger rack (with his optional battery rack) to
MR148V / MR348V racks.
9.5.4.1 1.1.4.1 Caution
9-36 !"# $ % $ &'( ! ) $

111 of 459
1 **

Figure 9.44:
Safety instructions
Before use, read the instructions given by the battery manufacturer
Risks when using the batteries
Electrical risk:
Each battery element must have protection adapted to the power supply and to the link cables.
An adapted circuit breaker or fuse must be able to insulate the batteries in the event of a short
circuit.
Risk of injury:
The metallic parts of the batteries are live. There is a risk of an electric shock or a short circuit.
Only touch the insulated parts of the batteries. In particular, non-insulated tools should not be
used and bracelets and rings should not be worn.
Risk of explosion:
Regardless of the conditions for use, hydrogen may escape from the batteries through the
pressure relief valves. As a result, under no circumstances should you use the charger rack
and the battery rack in an unventilated area.
9.5.4.2 Preliminary Operation
It is recommended to carry out two battery charge/discharge cycles before installation. This
operation is used to obtain the optimum battery characteristics. This operation is not necessary
if the batteries have been stored for less than nine months at a temperature of between 20 . 25
C (max 30 C).
Before installation, the batteries must be fully charged.
!"# $ % $ &'( ! ) $

9-37
112 of 459
Chapter 9 1 **

9.5.4.3 Installation Batteries in a Rack

Wiring of the batteries in a charger rack and in an extension battery rack is identical
1. Open the rack (remove the attachment screws from the cover)
2. Place the batteries in the vertical position
3. Depending on whether the rack has four or eight batteries, wire it as shown in the following
figure:
Figure 9.45: Wiring Batteries in a Rack

Note 1:
Pay particular attention to the running of the cables (do not trap them in the metallic parts)
9-38 !"# $ % $ &'( ! ) $

113 of 459
1 **

Figure 9.46: Batteries Positioning

Note 2:
Pay particular attention to the running of the cables (do not trap them in the metallic parts)
5. Close the rack (put the attachment screws back in place)
6. Close the switch and check the 48V battery voltage on the rear connector (pin1: 48V,
pin3: 0V)
7. Open the switch to prevent electric shock during assembly.
9.5.4.4 Assembly
Place the charger rack and the battery rack in a 19" cabinet no more than 1m (3.2') from its
system rack. Supports are required due to the weight, which may be as much as 21Kg (46lb).
Leave a 15 mm (0.59') space above the rack for ventilation. Do not obstruct the vent holes.
Figure 9.47:
9.5.4.5 Connecting the Protective Ground

The charger rack and the battery rack must be connected to the protective ground as shown
!"# $ % $ &'( ! ) $

9-39
114 of 459
Chapter 9 1 **

below:
Figure 9.48: Charger Rack and Battery Rack Rear Panel

The MR148V and MR348V must be connected to the protective ground as shown below:
9-40 !"# $ % $ &'( ! ) $

115 of 459
1 **

Figure 9.49: MR148V and MR348V Rear Panel
9.5.4.6 Connection to the System

1. Unplug the mains from the charger rack
2. Open the batteries switch on the charger rack and on the battery rack (if present)
3. Connect (if present) the battery rack to the charger rack using the link cord
4. Connect the MR148V / MR348V racks to the charger rack using the link cords as shown
below:
!"# $ % $ &'( ! ) $

9-41
116 of 459
Chapter 9 1 **

Figure 9.50: 48V Connections

Details of the charger rack rear panel connections:
Figure 9.51: Charger Rack Rear Panel

Note 1:
there are four 48V output sockets : 3 for feeding MR1-48V/MR3-48V racks, 1 for reserved
Note 2:
the fuse 1 on front panel protects the 48V output 1, the fuse 2 for output 2 and so on.
9-42 !"# $ % $ &'( ! ) $

117 of 459
1 **

5. Connect the main to the charger rack

6. Switch on the battery on the charger rack and on the battery rack (if present)
9.5.4.7 Connection to the RMA Alarm
In order to transmit charger rack alarm, the charger rack must be connected to the RMA board
as below:
Figure 9.52: Connecting RMA
9.5.5 Installing an External 48V Supply

When a 48V power supply compatible (with the requirements detailed : table: Operation Mode
vs Input Voltage ) is available, it can be connected in place of the charger rack.
The protective ground must be connected as with charger rack.
The MR1-48V / MR3-48V rack is permanently connected to the customer 48VDC power
supply. A customer 48VDC panel must be installed nearby.
This panel must have for each rack:
- A screw-down terminal block
- An isolating switch to power down
- A fuse or a breaker (10 A) for protection
The 3EH 76194 cable, called Extenal Cable MR1/MR3 48V must be used to connect the 48V
power supply.
!"# $ % $ &'( ! ) $

9-43
118 of 459
Chapter 9 1 **

Figure 9.53: MR348V Power Connection Example
9-44 !"# $ % $ &'( ! ) $

119 of 459

!
10.1 Replacing the Internal Batteries

Internal batteries are replaced with the system powered down and after removing the mains
connector, unscrewing the back panel and undoing the battery rack.
To ensure correct balance, replace all batteries at the same time with batteries of the same
type, same supplier and same batch.
To ensure system shutdown does not result in data loss if mains power is cut off or the
wall-mounted plug disconnected, replace the batteries every two years. This maintenance
operation is essential to make sure that there is sufficient backup power to enable files to be
saved before the system shuts down.
When delivered, batteries are not charged. File save in the event of a mains power loss can
only be guaranteed once the batteries have been charged, that is approximately 12 hours after
the system is powered on (GD switch set to ON).
Battery characteristics
- Number: one (S rack) or three serial (L rack)
- Sealed lead battery
- 1.2 Ah / 12V
- Fire resistance better than or equal to UL94-V2
- Check connection polarity
Important:
Replace only with a battery of the same type or equivalent recommended by the manufacturer.
Discard used batteries following the manufacturer's instructions.
10.2 Replacing External Batteries

Batteries in the external batteries rack can be replaced "hot". The associated system rack does
not have to be stopped.
As with the initial installation, batteries can be provided by Alcatel-Lucent. Compatible batteries
may also be used. See the Small & Large racks - Power connections - Storage for installation
instructions and precautions.
!"# $ % $ &'( ! ) $

10-1
120 of 459
Chapter 10
*
For maximum operating security, you are advised to change the external batteries every two
years.
10.3 Battery Maintenance

It is recommended that CS and GA board batteries be replaced with batteries of the same type
every two years. Used batteries should be disposed of in accordance with the manufacturer's
instructions.
10.4 Ventilation System, maintenance

Take advantage of the periodic battery replacement operations to clean the system ventilation
louvers with a brush or cloth.
When the system operates with no fan (S rack) or one fan (L rack) in working order, only the
external digital T0/T2 accesses and the first two interfaces of Alcatel-Lucent Reflexes
terminals remain operational.
10.5 Replacing a Board
10.5.1 Recommendations
All boards have an OBC component. This component allows boards to exchange data with the
GD board.
For the Alcatel-Lucent OmniPCX Enterprise CS, release 3.0 or higher of this component is
required.
A label affixed on the component shows the release. The OBC is located in a socket, allowing
it to be removed without desoldering.
Component location is shown below (for a MIX board).
10-2 !"# $ % $ &'( ! ) $

121 of 459
OXE System: Software Installation Manual
122 of 459
Legal notice:

owners.
Directives:
- 1999/5/EC (R&TTE)
123 of 459

Chapter 1
Call Server Installation
Software Installation ............................................................................. 1.1

Overview ........................................................................................................ 1.1
Enterprise PC Installer Tool ............................................................... 1.8
Commissioning .............................................................................................. 1.8
Standard Call Server Software Installation .................................. 1.10
Commissioning .............................................................................................1.10
Call Server Installation on a Virtual Machine .............................. 1.27
Overview .......................................................................................................1.27
Installing the VMware ESXi ..........................................................................1.29
Installing the vSphere Client .........................................................................1.40
Installing the OmniPCX Enterprise on Virtual Machine ................................1.50
Installing the FlexLM server ..........................................................................1.69

Appendix .......................................................................................................1.98
Using the Multi-Partition ................................................................... 1.106
Commissioning ........................................................................................... 1.106

Remote Download/Installation ....................................................... 1.111

Detailed description .................................................................................... 1.111

Operation .................................................................................................... 1.118

Maintenance ............................................................................................... 1.126
Swinst ...................................................................................................... 1.127
Detailed description .................................................................................... 1.127
Operation .................................................................................................... 1.128
! " #$ " %&' ( "

0-1
124 of 459

Chapter 2
OXE Media Services Installation
Overview .................................................................................................... 2.1

Overview ........................................................................................................ 2.1
Features provided .......................................................................................... 2.2
G.722 conference .......................................................................................... 2.2
Com Server duplication ................................................................................. 2.3
Security .......................................................................................................... 2.3
Installation process overview ............................................................ 2.4
Manual installation ......................................................................................... 2.4
Automatic installation via the ALEDS ............................................................ 2.5
Installing the VMware ESXi ................................................................. 2.5
Overview ........................................................................................................ 2.5
Requirements ................................................................................................ 2.6
Installation Procedure .................................................................................... 2.6
Configuration Procedure ...............................................................................2.10
Installing the vSphere Client .............................................................2.17
Overview .......................................................................................................2.17
Installation Procedure ...................................................................................2.17
Creating a Virtual Machine for the OXE-MS ................................. 2.27
Overview .......................................................................................................2.27
Requirements ...............................................................................................2.27
Creating the Virtual Machine for the OXE-MS ..............................................2.28

Configuring the OXE-MS on the OmniPCX Enterprise ............ 2.36

Process overview .........................................................................................2.36

Verifying the software locks dedicated to the OXE-MS ................................2.36

Declaring the OXE-MS .................................................................................2.37

Configuring the OXE-MS parameters ...........................................................2.37

Entering the Ethernet (MAC) address of the OXE-MS .................................2.39

G722 conference ..........................................................................................2.40
Installing the OXE-MS on a Virtual Machine ................................ 2.41
0-2 ! " #$ " %&' ( "

125 of 459

Overview .......................................................................................................2.41
Requirements ...............................................................................................2.41
Process overview .........................................................................................2.42
Preparing the OXE-MS installation ...............................................................2.42
Installing the OXE-MS on the Virtual Machine .............................................2.45

Maintenance .................................................................................................2.49
! " #$ " %&' ( "

0-3
126 of 459

0-4 ! " #$ " %&' ( "

127 of 459

1.1 Software Installation
1.1.1 Overview
1.1.1.1 Organization of the Call Server hard drive
At installation, the hard drive is divided into two different parts. The active version of the
application is installed on the first part and the second part has enough space to contain an
inactive version of the telephone application.
This allows a version of the application to be installed on the inactive part of the drive without
disturbing telephone operation.
The hard drive is partitioned.

Each partition may be considered as a virtual drive - an independent drive space containing
files, directories and data.
These partitions are said to be "mounted" (accessible with the mount command) when they
can be accessed and modified by the user.
table 1.1: Call Server partitions
! " #$ " %&' ( "

1-1
128 of 459
Chapter 1 ) &

Partitions Accessible with Function

mount
grub No Bootloader of the Linux core.
/ Yes Root directory (active version) of the Operat-
ing System (OS).
/proc Yes Special Linux feature, allowing direct access
to memory.
/usr2 Yes Contains, amongst other things, the swinst
/DHS3bin
tool and the binary files (telephone applica-
tion) of the active version.
/usr3 Yes Contains the ACTIS files and database of the
/DHS3data
active version.
/usr4 Yes Contains dynamic data (tickets and account-
/DHS3dyn
ing records, traffic analysis, system incidents,
etc.) for both versions
swap No Allows memory use to be optimized. Pro-
grams in swap mode remain in memory only if
they are currently being used or if there is
enough memory to install new programs. Oth-
erwise, they are stored on the swap partition
and loaded into memory when used.
root2_d No Root directory of the inactive version.
/usr5 No Contains, amongst other things, the swinst
/DHS3bin2
tool and the binary files (telephone applica-
tion) of the inactive version (becomes /usr2
when versions are switched).
/usr6 No Contains the ACTIS files and database of the
/DHS3data2
inactive version (becomes /usr3 when ver-
sions are switched).
/usr7 Yes Contains voice guide data and some 4645
/DHS3ext
data.
vmu No Used by 4645 voice mail.
crashdump No Allows data to be recovered if the system
crashes. Copies the entire content of Call
Server memory.
1.1.1.2 Software organization

1.1.1.2.1 Overview
The Alcatel-Lucent OmniPCX Enterprise Communication Server software is distributed and
delivered by Alcatel-Lucent on a CD-ROM. The directories are always organized in the same
way:
<CD-ROM root>\dhs3mgr\<release (version) name, or static or dynamic
patch name>\...
A readme.txt file is included with patches, this is located in <CD-ROM
root>\dhs3mgr\<patch or dynamic patch name>. This file gives a summary of
corrections, with name (usually in English) and error numbers and reports. The file also
1-2 ! " #$ " %&' ( "

129 of 459
) &

describes any modified binaries (a new field indicates each such binary). All former patches for
the complete standard version are listed: all previous Readme files are therefore not needed.
The most recent file summarizes all previous files.
The Enterprise PC Installer software is provided in full release editions; it may be included with
certain patches. The access path is: <CD-ROM root>\dhs3mgr\<release (version)
name, or static or dynamic patch name>\pcmao\boot_res\pcinstall. A
specific readme.txt file gives version number and a description of any corrections.
1.1.1.2.2 Organization
There are two main parts:
- The Operating System: Linux.
- The telephone application.
These two parts are subdivided as follows (for installation):
For Linux:
- Linux full version.
- Linux upgrades.
For the telephone application:
- Telephone application full version.
- Static patch telephone version.
- Dynamic patch telephone version.
1.1.1.2.3 Patches
Telephone patches are delivered as a cpiofile file (Unix compressed file) located in the
directory \dhs3mgr\<version>\dhs3linux
(example: \dhs3mgr\e1604\dhs3linux\comm\cpiofile).
Most binaries are located in the comm directory. For country-specific binaries, the cpiofile
file is at the same level of the tree structure but in a directory named according to the
international standard (example: es for Spain, ch for Switzerland, etc.).
Linux and swinst patches are delivered as "RPM" packages ("Red hat Package Manager":
standard for Mandrake, Suse, and Red Hat editions). These installable files contain binaries
and installation scripts for various Operating System related features (example: package
dhcp_a4400-2.1.17-1oxe.i386.rpm for the dhcp ).
Linux patches
Linux patches are Operating System modifications provided with telephone application
versions. They consist of RPM packages. The machine must be rebooted after installing
such packages. They can only be installed with the phone shut down or when installation is on
the inactive partition.
This type of patch is not installed on its own (except in exceptional circumstances) as it is
always part of a telephone patch(es) delivery and is thus installed simultaneously with this.
Static telephone patches
These patches are new telephone application files containing corrections or upgrades. They
can only be installed with the phone shut down or when installation is on the inactive partition.
! " #$ " %&' ( "

1-3
130 of 459
Chapter 1 ) &

They are installed after a full version has been installed. They cannot run if the standard
telephone version is not installed.
A static patch can easily be distinguished from a full version by the presence of two text files in
the CD-ROM tree structure: <CD-ROM root>\dhs3mgr\<patch
name>\<installlinux\for_comp and <CD-ROM root>\dhs3mgr\<patch
name>\<installlinux\patch>.
The first file is used when installing a full version in standard mode (see the Standard Call
Server installation - Commissioning ): for a static patch, it gives the name of the full version
associated with the patch. The second file gives patch version: this is a number starting with
"1".
- Static patch name is usually the name of the full version followed by patch number.
- Each new static patch includes all corrections made in previous patches.
- To identify the version installed on the hard drive, use the siteid command.
- Some patches require a complete reboot: this is the case when a new version of Linux is
installed for example. When installation (via swinst) is complete, a system message is
displayed requesting the user to reboot the machine.
Dynamic telephone patches
These patches are new telephone application files containing corrections or upgrades. They
can be installed on the active or inactive partition with the phone running without disturbing
phone operation. 1
After this type of patch has been installed, it is immediately installed in CPU memory. The
customer then has the corrected version available without having to reboot the machine
(except in a specific case, described below). This installation is performed using the
memloader tool. For each process patched in memory, a 2176 incident indicating the
operation is emitted.
Dynamic patches are installed after static patch installation. They cannot run if the standard
telephone version and corresponding static patch are not installed.
Dynamic patch name always ends with one or two letters. The first dynamic patch for a version
ends with the letter a, the next with the letter b and so on till the end of the alphabet. If
further patches are necessary after the letter z, they are named aa, etc.
Special cases
When the patch provides new coupler board firmware, the boards must be reset for
modifications to be applied. For IO2N boards, the machine must be rebooted for modifications
to be applied. Use the downstat d command to ascertain which boards must be downloaded
again.
Also read the readme file included on the CD-ROM in \dhs3mgr\<version>: this contains
information on certain operations to be performed after patch installation, for example, the
processes to be restarted (dhs3_init R <process name> command) or on rebooting the
machine. If these operations are not performed, the patch will not implement all the desired
corrections.
To identify the version installed on the hard drive, use the siteid command.
1
They can also be installed with the phone shut down.
1-4 ! " #$ " %&' ( "

131 of 459
) &

The file: <CD-ROM root>\dhs3mgr\<dyn patch name>\<installlinux\Nostopte

(no size) is present to inform swinst that this patch can be installed with the phone running.
The file: <CD-ROM root>\dhs3mgr\<dyn patch name>\<installlinux\patchdyn
gives the name of the static patch supporting this dynamic patch. This file is read during
installation in standard mode: for this type of installation, the installer names this patch and
patch name and full version name are retrieved recursively (via the for_comp file of the
patch).
Delta telephone patches
These patches (available from R5.1.2) contain all modifications made (via several static and
dynamic patches) between two versions released by Alcatel-Lucent.
Example: several patches have been generated for version f1.600.
- Version f1.600.1 has been released by Alcatel-Lucent.
- Versions f1.600.1a and f1.600.2 include corrections, but these versions (not released)
have not been made available to customers.
- Version f1.600.3 has been released by Alcatel-Lucent.
The delta includes all modifications made between version f1.600.1 and version f1.600.3
A delta can only be produced for the same standard version. It is therefore not possible to
obtain a delta between version f1.600 and version f1.700.
The main advantage of a delta patch is its small size in relation to the patches it contains. Call
Server loading and installation are thus faster.
The name of a delta patch includes that of the original (source) version released and that of
the latest (target) version released. A delta between version f1.500.3 and version f1.500.5
! " #$ " %&' ( "

1-5
132 of 459
Chapter 1 ) &

would be named f15003_f15005.

1.1.1.2.4 Swinst
Swinst is a package delivered with the full version of Linux. It can also be delivered as an
upgrade with full versions of the telephone application or for static (or even dynamic) patches.
It can be installed with the phone running or shut down. It is not installed on its own (except in
exceptional circumstances) as it is always part of a Linux or telephone patch(es) delivery and
is thus installed simultaneously with this.
It is always located in the directory \dhs3mgr\<version>\pkglinux\facil.
Version number is given in the name (e.g. swinst-2.14.0-4alc.i386.rpm for version
2.14.0).
To identify the version installed on the hard drive, log on with the swinst account: version
number is displayed in menu headers.
For more information on swinst menu features, see the Swinst - Detailed description .
1.1.1.2.5 Linux
Full versions of Linux are located in:
\dhs3mgr\<version>\pcmao\boot_res\bootp\linux\ followed by version number.
A full version is named as follows:
- A number followed by a period for the major version.
- Another number indicating upgrade version.
- For example: 14.1 for Linux major version 14 with upgrade 1.
To obtain version number, use the command sysload version.
Upgrades are located in: \dhs3mgr\<version>\pkglinux\linux" and
"\dhs3mgr\<version>\pkglinux\RPMS.
To identify the upgrade version, see the file lx_version-[version].
1.1.1.3 Procedures for installation on the hard drive
From R5.0 Lx releases, Alcatel-Lucent OmniPCX Enterprise CS software installation is always
performed from a Windows server PC running the Enterprise PC Installer software. However,
a Call Server can be used as server. In this case, it will only be used as server for "remote
download" type installation operations or software upload to inactive partitions. The following
table lists all version and patch installation procedures that can be used.
For more information, refer to the Standard Call Server installation - Commissioning , Swinst -
Detailed description , Using the multi-partition - Commissioning or the Remote download /
installation - Detailed description .
1-6 ! " #$ " %&' ( "

133 of 459
) &

Module to be in- Active partition Inactive partition Installation tools

stalled
Full version to be in- See the Standard Call This is impossible, but Bios + Enterprise
stalled (standard in- Server installation - the inactive partition is PC Installer
stall) Commissioning still created (blank)
Note 1:
Standard installation
comprises a full version
of Linux + Linux up-
grade (optional) +
swinst + telephone +
patch (optional) + dy-
namic patch (optional).
swinst Installed during stand- Installed when a parti- Swinst + Enter-
ard installation or in- tion is duplicated, during prise PC Installer
stallation of a patch remote installation, in-
(static or dynamic) stallation of a static or
dynamic patch, or in-
stallation of a full version
of Linux
Full version of Linux Installed during stand- Installed during remote Swinst + Enter-
ard installation load. Installed during a prise PC Installer
Duplicate Linux op-
eration in the swinst Note 2:
menu Duplicate If the master/dis-
partitions. Installed tributor call server
with the swinst Install already contains the
package menu
patch, the Enter-
prise PC Installer is
not required for in-
stallation in remote
download mode
Linux patch "Manually" installed us- "Manually" installed us- Swinst + Enter-
ing swinst at static ing swinst at static patch prise PC Installer
patch installation installation or by remote
load. Copied with the full
version of Linux via the
Duplicate parti-
tion menus
! " #$ " %&' ( "

1-7
134 of 459
Chapter 1 ) &

Module to be in- Active partition Inactive partition Installation tools

stalled
Telephone static "Manually" installed us- "Manually" installed us- Swinst + Enter-
patch ing swinst ing swinst or by remote prise PC Installer
load.
Note 4:
Note 3: If the master/dis-
"Manual" installation is per- tributor call server
formed with swinst via the already contains the
menu Deliveries in- patch, the Enter-
stallation/ Get bin- prise PC Installer is
aries delivery from not required for in-
PC. stallation in remote
download mode
Telephone dynamic "Manually" installed us- "Manually" installed us- Swinst + Enter-
patch ing swinst or by remote ing swinst or by remote prise PC Installer
load load.
Note 6:
Note 5: If the master/dis-
"Manual" installation is per- tributor call server
formed with swinst via the already contains the
menu Deliveries in- patch, the Enter-
stallation/ Get bin- prise PC Installer is
aries delivery from not required for in-
PC. stallation in remote
download mode
Delta N/A Installed by remote Swinst
download
1.2 Enterprise PC Installer Tool
1.2.1 Commissioning
1.2.1.1 Overview
The Alcatel-Lucent OmniPCX Enterprise CS PC Installer software allows to install versions,
patches, Linux on the Call Server hard drive inactive partition and GD/GA binary on an
Alcatel-Lucent OmniPCX Enterprise CS.
Note:
The screens shown in the rest of this document are given for information only and may be modified in
future software releases.
1.2.1.2 Recommendations before the installation

1.2.1.2.1 PC configuration
- Windows 2000, Windows XP and Windows 7.
1-8 ! " #$ " %&' ( "

135 of 459
) &

- 19 Mb free space on the hard drive.

- IP network configured.
1.2.1.2.2 Before beginning the installation
- Log on as local administrator to have the required rights.
- Shutdown all programs that are currently running before starting software installation.
The installation of the OmniPCX Enterprise PC Installer software is performed with
InstallShield with the help of setup.exe.
Procedure:
1. Select the OmniPCX Enterprise PC Installer software CD-ROM, or select the drive on
which the version is available (directory: /dhs3mgr/version or
patch/pcmao/boot_res/pcinstall).
2. Run setup.exe.
This displays a language selection window.
3. Select the installation language and click on OK.

This displays a Setup then a Welcome windows.
4. Click on Next.
This displays the folder selection window.
5. Default folder is c:\Program Files\Alcatel-Lucent\OmniPCX Enterprise PC Installer. If you

choose to change, click on "Browse" and select another folder.
6. Click on Next.
This displays a window showing the installation progress.
7. During installation, a warning window can appear. Click on OK and validate the automatic
start of the "Computer Browser" windows service at the end of software installation.
This displays a window informing of the end of installation.
8. Click on Finish.
An icon "OmniPCX Enterprise PC Installer" has been created on the desktop and an
"Enterprise PC Installer" option is available from the Start menu (Start/Program/OmniPCX
Enterprise PC Installer/OmniPCX Enterprise PC Installer).
1.2.1.4 Interactions with the Firewall
Firewall settings of the PC in which the PC installer is running should not be controlled by any
antivirus software or the other external applications.
When a Security alert window is displayed for access to ftpd, dhcpd, tftpd or Perl Command
Line Interpreter, accept private and public accesses.
! " #$ " %&' ( "

1-9
136 of 459
Chapter 1 ) &

1.2.1.5 Operation
The different types of installation (and uninstalling the software) are detailed: Standard Call
Server installation - Commissioning
1.3 Standard Call Server Software Installation
1.3.1 Commissioning
1.3.1.1 Overview
Composition of a software release:
A software release consists of:
- An Operating System: Linux (for the Alcatel-Lucent OmniPCX Enterprise CS).
- A "swinst" package (see the Swinst - Detailed description ).
- Binaries for the telephone part.
- Any Linux, swinst and telephone upgrades.
- Upgrades are contained in "patches". A patch may contain one or more upgrades.
- Some upgrades are referred to as "dynamic patches". These patches include telephone
binaries and a method that, in addition to installing files on the hard drive, also installs
them in memory, which avoids having to reboot the system. This is useful for installing a
patch on a site in operation.
Software releases supplied to installers on CD-ROM have the following tree structure:
- Under the root, a directory "dhs3mgr".
- One or more sub-directories containing release (version) names.
Caution:
This document does not cover manual installation of telephone binaries (an operation performed
without formatting the drive and during which Operating System and client data are conserved).
This type of installation is performed using "swinst" (see the Swinst - Detailed description ), and
is particularly useful when you want to upgrade a release or add a patch (static or dynamic).
1.3.1.2 Operating Procedure

Standard installation of a CPU board, a CS board or an Appliance Server type Call Server
consists in automatically loading a full version (complete release) or full version + static patch
or full version + static patch + dynamic patch to the Call Server hard drive.
Standard installation is performed in several steps:
1. The Call Server must perform a network boot on the installation server PC on which the
Alcatel-Lucent OmniPCX Enterprise CS PC INSTALLER application is running.
2. The installation server PC provides the Call Server with an IP address via DHCP.
3. The installation server PC provides the linux.ram or the pxeloader for an Appliance
Server via TFTP.
4. The installation server PC provides the Linux OS, swinst packages, and telephone
1-10 ! " #$ " %&' ( "

137 of 459
) &

application binaries via FTP.

5. The Call Server restarts automatically when installation is complete.
The network boot procedure:
To perform a network boot, the technician may use two methods:
1. At Call Server boot: automatic, if the hard drive is blank.
2. Manual, if the hard drive is not blank. In this case, there are two possible solutions:
A "manual" boot at BIOS startup (for the Appliance Server, CPU board and CS board),
A command will be run from the active Call Server (with, at minimum, the Linux OS
running). This command deletes the hard drive MBR (Master Boot Record). At the next
reboot, the BIOS considers the hard drive to be blank and will thus automatically
perform a network boot.
These methods are described below.
1.3.1.3 Installation Configuration
For any type of Call Server (CPU board, CS board or Appliance Server):
The default configuration of the V24 port is:
- Speed, 9600 bds.
- 8 bits.
- No parity.
- 1 stop bit.
- XON/XOFF
Connect a terminal with VT100 emulation ("Win3.11 terminal", "Hyper-terminal", etc.).
Connect the Call Server to the installation server PC using a crossed Ethernet cable or a hub
or switch. For an Appliance Server, use Ethernet connector "1".
CS boards must have Bios version 8.3 or higher. If this is not the case, return the board to the
after-sales department.
Caution:
As the Alcatel-Lucent OmniPCX Enterprise CS PC INSTALLER application runs the TFTP, FTP,
and DHCP servers, standard installation of a Call Server is performed outside the client LAN and
therefore requires a direct Ethernet connection between the Call Server and the installation server
PC.
1.3.1.4 Alcatel-Lucent OmniPCX Enterprise CS PC INSTALLER Application

See also: Enterprise PC Installer - Commissioning .
1. Place the CD-ROM containing the Call Server release (version) to be installed in the drive.
1.3.1.4.1 Operation
Installation of a Patch
The installation of a patch is done with the software Alcatel-Lucent OmniPCX Enterprise CS
PC Installer and with swinst on the Alcatel-Lucent OmniPCX Enterprise CS.
! " #$ " %&' ( "

1-11
138 of 459
Chapter 1 ) &

Procedure:
1. Double click on the icon of the desktop " Alcatel-Lucent OmniPCX Enterprise CS PC
Installer". The following window is displayed:
2. In the menu "Preferences", select the driver that contains the patch.
3. In the field "Installation type", select the type of installation to Call handling or patch.
Note:
a TFTP server and a FTP server are running through the installation of the patch and are stopped only
when the window " Alcatel-Lucent OmniPCX Enterprise CS PC Installer" is closed.
Installation of Linux on Inactive Partition

The installation of Linux on the inactive partition of the Alcatel-Lucent OmniPCX Enterprise CS
is achieved with the Alcatel-Lucent OmniPCX Enterprise CS PC Installer software and with
swinst.
Procedure:
1. Open the Alcatel-Lucent OmniPCX Enterprise CS PC Installer application
2. In the menu "Preferences", select the driver that contains the version.
3. In the field "Installation type", select the type of installation (Linux on inactive partition).
1-12 ! " #$ " %&' ( "

139 of 459
) &

Note:
an FTP server is running through the installation of the patch and is stopped only when the window
"Alcatel-Lucent OmniPCX Enterprise CS PC Installer" is closed.
Standard Installation of a Complete Version

The standard installation of a complete version is done with the Alcatel-Lucent OmniPCX
Enterprise CS PC Installer and the bios standard installation menu of a CPU board, a CS
board or an Appliance Server for the Alcatel-Lucent OmniPCX Enterprise CS.
Note 1:
the Linux version for a Call Server must be preceded by a % (for example %14.0).
Procedure:
2. In the menu "Preferences", select the driver that contains the version
3. In the field "Installation type", select the type of installation Linux + Call_handling.
! " #$ " %&' ( "

1-13
140 of 459
Chapter 1 ) &

4. After selecting the field Linux + Call Handling, the window Parameters Installation is
displayed:
1-14 ! " #$ " %&' ( "

141 of 459
) &

5. In the field "Call handling version", select the complete version or the complete
version + patch.
6. In the field "Country", select the country.
7. In the field "Installation type", select Standard installation.
8. In the field "Network type", select the type of installation to Direct cable.
9. In the field "Network Interface", select the network board interface used.
10. In the field "IP Address", the IP address reserved for the Call Server is displayed.
11. In the field "Call Server Type", select the type of the CPU to install (Alize (for CS board),
4400 (for CPU board) or Appliance_server).
12. In the field "ethernet address" do not write the MAC address (not needed) of the Call
Server.
13. Validate by clicking on Apply and the following window is displayed (with the button Apply
disabled):
! " #$ " %&' ( "

1-15
142 of 459
Chapter 1 ) &

Note 2:
in addition to the TFTP and FTP servers, a DHCP server is activated during standard installation and
stops only when the window Parameters Installation is closed.
Closing the Alcatel-Lucent OmniPCX Enterprise CS PC Installer application stops the three
servers: TFTP, FTP and DHCP.
Installation of a GD/GA Binary
Installation of a GD/GA binary is achieved with the software Alcatel-Lucent OmniPCX
Enterprise CS PC Installer and a GD/GA which operates a network boot on the PC server.
Procedure:
2. In the menu "Preferences", select the driver that contains the version.
Note 1:
the version must contain a directory /dhs3mgr/"version"/pcmao/boot_res/DHS3bin/downbin/emg
which includes GD/GA binaries.
3. In the field "Installation type", select the type of installation GD/GA binary.
1-16 ! " #$ " %&' ( "

143 of 459
) &

After selecting the field GD/GA binary, the window Installation parameters is displayed:
! " #$ " %&' ( "

1-17
144 of 459
Chapter 1 ) &

4. In the field "Media Gateway binary versions", select the version.

5. In the field "Network type", select the type of installation to Direct cable.
6. In the field "Network Interface", select the network board interface used.
7. In the field "IP Address", the IP address reserved for the GD/GA is displayed.
8. In the field "ethernet address", don't write the MAC address (_not needed_) of the
GD/GA.
9. Validate by clicking on Apply and the following window is displayed (with the button Apply
disabled):
Note 2:
in addition to the TFTP server, a DHCP server is activated during installation of a GD/GA binary and
stops only when the window "Installation parameters" is closed.
Closing the Alcatel-Lucent OmniPCX Enterprise CS PC Installer application stops the two
servers: TFTP and DHCP.
1.3.1.4.2 Uninstallation
To uninstall the software on the PC, follow the following steps:
- Close all applications running currently.
- In the taskbar, go in to the menu Start/Programs/Enterprise PC Installer to execute
Uninstall Alcatel-Lucent OmniPCX Enterprise CS PC Installer program. The following
window is displayed:
1-18 ! " #$ " %&' ( "

145 of 459
) &

- Click on Yes.
- At the end of the uninstallation, a message indicates that uninstallation is complete, but
that some elements could not be removed: A program deletes automatically these
elements when clicking on OK.
- Restart the PC to achieve complete uninstallation.
1.3.1.5 Call Server Installation Operating Procedure
To install a Call Server, the Call Server must perform a network boot on the server PC.
There are two cases:
1. The Call Server hard drive is blank (for example, new board, drive replaced, etc.):
The Call Server (CPU board, CS board or Appliance Server) network boot on the
installation server PC is then performed automatically.
2. A release (version) is already installed on the Call Server hard drive (this is usually the
case):
The network boot must be performed manually.
CPU board and CS board type Call Server: There are two methods of forcing the Call Server
to perform a network boot:
- From the CPU BIOS menu.
- By running the command "grubboot ETHER" under the Linux root account, a confirmation
is required then the Call Server reboots.
Caution 1:
Following this command, the Call Server hard drive is invalid and requires reformatting.
Appliance Server type Call Server: There are also two methods of forcing the Call Server to
perform a network boot:
- By running the command "grubboot ETHER" under the Linux root account, a confirmation
is required and the Call Server reboots.
Caution 2:
Following this command, the Call Server hard drive is invalid and requires reformatting).
- With a PC monitor and keyboard connected to the Call Server, press the F12 key ("PXE"
type boot). In this case, the hard drive is not invalidated and the network boot is performed.
Caution 3:
Do not modify server configuration in the BIOS menu (accessed via the F1 key) unless
specifically requested to do so by Alcatel-Lucent support. The ex-factory configuration has
been tested to operate correctly with these values.
1.3.1.6 Implementing the Call Server Installation
! " #$ " %&' ( "

1-19
146 of 459
Chapter 1 ) &

1.3.1.6.1 CS Board Type Call Server: Network Boot from the BIOS Menu
In the console window, wait for the following message:
Alize BIOS Monitor
*** BIOS Version 3EH30227EIAA bios100/008.033 ***
*** Generated on Nov/04/2004 at 14:51 ***
memory test started lng=133169152 with 0
running flash(soldered=1
socket=0)=1,BIOScase:4,BIOSv24:0,verrou=1,algoNOR=1,size=1,base=3ff80000
DIMM characteristics->: JEDEC Manu ID:h,
Memory type(EDO,FPM..):0x04
# of row address:12
# of col address 10
# of module row 1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI:scan_bus for bus 0
PCI:bus=00h,devfn=00h ,[vendor:device]=[1022h/3000h]
PCI:bus=00h,devfn=60h ,[vendor:device]=[100bh/0020h]
PCI:bus=00h,devfn=98h ,[vendor:device]=[1064h/2101h]
PCI:scan_buses with 00h secondary buses
PCI:command =000003ffH for device 00:00
PCI: Assigning I/O space fc00-fcff for 00:60 BAR=00000010
PCI:Assign memory space bffff000H to bfffffffH for device 00:60
PCI:Assign memory space bfffd000H to bfffdfffH for device 00:98
PCI: Assigning I/O space fd00-fd1f for 00:98 BAR=00000014
PCI: Unable to handle I/O allocation for 00:98 (ff04) BAR=00000018
assigning irq10 to xchange
B0 = 17
DRCTMCTL = 1e
DRCCTL = 18
DBCTL = 11
Set external RTC
Set Internal RTC
No external RTC detected
gpbus sig timing : 0-2-1-2-1-2!
CMOS is available
Xchange PCI mem base OK: 00000000
Xchange PCI IO base OK: 00000000
Xchange irq OK: 0a
PCI command read for natsemi : 00000347
PCI Master Bit Setting...
pci_command set to:0357
0000 0080 009f 002f 00db 0058 , IRQ 12.
eth0: Transceiver status 0x00007869 advertising 000005e1
Hard Disk #0 : FUJITSU MHK2060AT 5729 Mo
Parameters :
Type 00000
Extended Type 00255
Sectors / track 00063
Landing Zone 00000
Control Byte 00000
Write Precomp 00000
Heads 00015
Nb of Cylinders 12416
HD size(cyl*sec by track*head*sector size) 06007 MO(decimal)
init nand set interupt
Flashfx version:520.001.001
Cannot mount flash drive No 0. Flash NAND may not be formatted !
Cannot mount flash drive No 0. Flash NAND may not be formatted !
NAND Flash Comfiguration:
CPU size : 32 MBytes
free spare blocks: 38
XMEM size : 0 MBytes
NAND Flash Details:
chip #0 : Type=TC58256 Id=9875H Size=32(MBytes) Unit size=16384 Page
Size=512
time :sec=31,min=32,hour=15,DoW=06,date=06,Month=07,year=05
time :sec=35,min=32,hour=15,DoW=06,date=06,Month=07,year=05
1-20 ! " #$ " %&' ( "

147 of 459
) &

ALIZE informations :
Memory Detected : 131072 Ko
Flash Detected
DaughterBoard Not Detected
XCHANGE Detected
XCHANGE Chip Initialization OK
Ethernet Found : 1
Ethernet Chip Initialization OK
Hard Disk Detected
Hard Disk Found : 1
DMA enabled
PCM11 selected
No HD trace
CPU at 133 mhz
check lock RTC
value of DIL switch 01
YOU CAN strike Ctrl B to enter in BIOS monitor during several seconds from NOW !
Caution: When this message is displayed, a timer is triggered (several seconds): Enter
the sequence Ctrl + B
hit [Ctrl I] for BIOS monitor!
Enter the sequence Ctrl + i
Password?:
Type return (no password)
Watchdog disabled
Alize BIOS Monitor
*** BIOS Version 3EH30227EIAA bios100/008.033 ***
*** Generated on Nov/04/2004 at 14:51 ***
Monitor Light Menu
01 - Load From Hdisk #0
02 - Load From Ethernet
03 - Load From Flash NAND program
04 - Load From Flash NAND program and Bootp
05 - Load From Hdisk #0 and Bootp
06 - Display MAC address
07 - Display PCMS id
08 - Display System informations
09 - Full Options menu
10 - Reset System
? 2
1.3.1.6.2 CPU Board, CS Board or Appliance Server Type Call Server: Network Boot
with the "grubboot ETHER" Command
Caution:
The "grubboot ETHER" command invalidates the Call Server hard drive and thus forces a network
boot at restart.
This operation cannot be undone and reformats the Call Server hard drive (as is the case for
standard installation).
For login, log in as root:
localhost login:
Linux Mandrake for eMediate release 7.2 (Odyssey) for i486
Kernel 2.4.1-ll-dhs3 on an i486 / ttyS0
localhost login: root
Password:
e-Mediate/Linux installation performed: 16-Jul-2002 12:08:20
Enter the command "grubboot ETHER":
[root@localhost /root]#grubboot ETHER
A confirmation is required, then the Call Server reboots.
1.3.1.6.3 Network Boot on a CS Board with a Blank Drive
! " #$ " %&' ( "

1-21
148 of 459
Chapter 1 ) &

This is the same as rebooting after running the "grubboot ETHER" command. A confirmation is
required.
1.3.1.6.4 Network Boot on an Appliance Server with a Drive that is not Blank (Monitor
and Keyboard Connected)
Wait until the following message is displayed on the screen: "PRESS F1 FOR
CONFIGURATION/SETUP", at the bottom left of the monitor screen (before the message:
"Verifying DMI pool data .").
Press F12. The network boot starts. If there is an error:
- No address supplied by the DHCP server:
- No boot PXE loader file supplied: The server boots on the hard drive.
Various messages are displayed on the screen: these messages give information such as the
IP address assigned, the DHCP server, and the cause of any boot problems.
When this phase is complete, the system reports all installation information on the screen
connected to the V24 connector. The monitor no longer displays anything.
1.3.1.7 Standard Installation Progress
When the Call Server is started by network boot, standard installation is performed in several
stages.
1.3.1.7.1 Bootp Request and Loading of linux.ram
The Call Server makes a bootp request to the server installation PC to obtain an IP
address via the DHCP server (Alcatel-Lucent OmniPCX Enterprise CS PC INSTALLER):
IP address determination
======================
BOOTP request in progress -> 0:80:9f:2e:4b:64
Bootp resp IP addr src :10.20.21.10
bootp server and TFTP server are the same
TFTP server IP addr (siaddr) : 10.20.21.10
eth source address=0:8:c7:5a:46:3d
bootfile = /bootp/linux/5.0/alize/startup.txt
Netmask : 255.255.255.0
Our Hostname : OXE_1 (10.20.21.11)
My IP address
10.20.21.11
My SUBNET mask
255.255.255.0
The server installation PC transfers the linux.ram to the Call Server via TFTP
(Alcatel-Lucent OmniPCX Enterprise CS PC INSTALLER):
1-22 ! " #$ " %&' ( "

149 of 459
) &

TFTPLOAD STARTED using ip=10.20.21.10 - Bootp Server NT1 - File Name

/bootp/linux/5.0/alize/startup.txt
*RcvTO,TOIPRcv,TFTP_Time_out on No:0001
size of last packet: 216
TFTPLOAD COMPLETE - file size 216
cmd received :
/bootp/linux/5.0/alize/vmlinux.bin;1251184;BIN;1048576;1048576
/bootp/linux/5.0/alize/initrd.img;3769939;RAMDISK;4194304;0
ramdisk_size=3769939,root=/dev/ramdisk,console=ttyS0,panic=5;60;CL;0;0
boot;0;BOOT;0;1048576
size of file loaded : 000000d8H at 00006658H
j= 0 file-fct type= 7 ,file name= /bootp/linux/5.0/alize/vmlinux.bin
,length= 1251184 ,address=1048576 start=1048576
j= 1 file-fct type= 1 ,file name= /bootp/linux/5.0/alize/initrd.img
,length= 3769939 ,address=4194304 start=0
j= 2 file-fct type= 6 ,file name=
ramdisk_size=3769939,root=/dev/ramdisk,console=ttyS0,panic=5 ,length= 60
,address=0
start=0
j= 3 file-fct type= 5 ,file name= boot ,length= 0 ,address=0 start=1048576
j= 4 file-fct type= 0 ,file name= ,length= 0 ,address=0 start=0
config action number=4
Boot continues:
/bootp/linux/5.0/alize/vmlinux.bin
...........................................
.......................................size of last packet: 368
/bootp/linux/5.0/alize/initrd.img
...........................................
.........................................size of last packet: 83
9815=total packets received
9817=total packets transmitted
5473225=total bytes received
628876=total bytes transmitted
0=bad packets received
0=packet transmit problems
0=no space in linux buffers
0=no space available in linux
0=multicast packets received
0=collisions
0=length_errors
0=receiver ring buff overflow
0=receiver ring buff overflow
0=recv'd frame alignment error
0=recv'r fifo overrun
0=receiver missed packet
0=tx_aborted_errors
0=tx_carrier_errors
0=tx_fifo_errors
0=tx_heartbeat_errors
0=tx_window_errors
0=rx_compressed
0=tx_compressed
start kernel at 00100000
Shutdown of the interface 0 =00000000
init Ethernet interface 1 not done
Watch dog started
Bootinfo src = 0x0 Bootinfo dst = 0xc0107000
Linux version 2.4.1-ll-dhs3 (dhs3linx@colebu02) (gcc version 2.95.2
19991024 (release)) #1 Wed Mar 27 14:34:26 MET 2002
1.3.1.7.2 Loading Linux Packages

The server installation PC transfers the Linux packages to the Call Server via FTP
! " #$ " %&' ( "

1-23
150 of 459
Chapter 1 ) &

(c) Alcatel-Lucent e-Mediate / Linux (c) 1999 Red Hat Software Install system
+---+ Install Status ++
| Package: Id.so-1.9.114mdk_2alc |
| Size : 237k |
| Summary: The Linux dynamic linker, library and |
| utilities |
| ########################################### |
| |...........|...........|...........|...........| |
| Packages Bytes Time |
| Total : 124 54M 0:02:29 |
| Completed: .3 0M 0:00:01 |
| Remaining: 121 54M 0:02:28 |
| |
| |...........|...........|...........|...........| |
+-------------------------------------------------------+
<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
1.3.1.7.3 Loading the swinst Package
The server installation PC transfers the swinst package to the Call Server via FTP
*** Creation of user mtch
*** Creation of user mtcl
*** Creation of user adfexc
*** Creation of user client
*** Creation of the missing main directories
*** Creation of the missing swinst directories
A daily backup will be executed on CPU disk
at 5 hour 45 min
WARNING : no delivery has been installed
The path of the delivery is E:/dhs3mgr/e1601
The previous version will be erased before the new installation
to avoid for some old files to remain on your CPU.
end of remove procedure
Transfert for pkg part in preparation
facil/swinst-2.1.0-3alc.i386.rpm
End of remote copy for pkg part files
1.3.1.7.4 Loading Telephone Binaries

The server installation PC transfers the telephone binaries to the Call Server via FTP
1-24 ! " #$ " %&' ( "

151 of 459
) &

*** Creation of the missing main directories

*** Creation of the missing swinst directories
Transfert for comm part in preparation
Remote copy for comm part files is in progress ...
DHS3bin/downbin/bindspemtl
DHS3bin/downbin/bindspnddi2
DHS3bin/downbin/bindspdpt1
DHS3bin/downbin/bindspboot
DHS3bin/downbin/bindspgpa
DHS3bin/downbin/bnvdsp1CPU6
DHS3bin/downbin/bnvdsp0CPU6
DHS3bin/downbin/bindspgpaconf
DHS3bin/downbin/bindspacem
DHS3bin/downbin/bindspatl8_r1
DHS3bin/downbin/bindsppcm2
DHS3bin/downbin/bindsppcm2_r1
DHS3bin/downbin/bindsppcm2_x1
DHS3bin/downbin/bindspgpavg
DHS3bin/downbin/bindspvgu
DHS3bin/downbin/bindspz2c
DHS3bin/downbin/bindspz2f
DHS3bin/downbin/bindspdtmdect8
DHS3bin/downbin/bindspz2cx
DHS3bin/downbin/bindspz2fx
DHS3bin/downbin/bindspcompdect8
DHS3bin/downbin/bnvdsp0z32
DHS3bin/downbin/binbbc2
...etc
1.3.1.7.5 Call Server Restart

When telephone binary loading is complete, the Call Server reboots, restarts, and shuts down
in Linux.
Standard installation is finished and should be completed by configuring the IP network (using
the "netadmin" tool), creating a blank database for a new site ("swinst" tool), and by
configuring automatic telephone startup ("swinst" tool).
Caution:
If the version is named after a dynamic patch, installation will be performed but the dynamic
patch will be incorrectly installed: it must be re-installed AFTER rebooting. To do this, refer to the
Swinst - Operation - Binary Files (Telephone).
1.3.1.7.6 Security Setting

As of R6.2, at the end of the Call Server reboot, the security menu is displayed on the system
console. The security menu requests to define security level before the Call Server is in use.
When the security dialog is displayed, no IP interface is configured. This implies that no
external IP connection can be achieved. In other words, nobody, apart from the console user,
can access the Call Server.
Security setting dialog:
Do you want to activate server security high level (Y/N) ?
- N: when the answer is No the following menu is displayed:

Select server security level:
R) Configuration to be restored
0) Level_0 = no security feature activated
1) Level_1 = password/aging
2) Level_2 = password/aging + trusted hosts/TCP wrapper
3) Level_3 = password/aging + trusted hosts/TCP wrapper + SSH
R): no security function is activated. The installer must later restore the security
configuration from a backup.
0): no security function is activated. This configuration applies when a trusted IP
network is used.
! " #$ " %&' ( "

1-25
152 of 459
Chapter 1 ) &

1): in this case the system requests a new password for the accounts root, swinst, mtcl
and adfexc. The new passwords must comply with the password check rules. For more
information on password check rules, see: Security - Detailed description - Password
composition check rules. Note that the account name and the password cannot be
identical. For example: root is not a valid password for the account root.
In addition, the system request the maximum duration of use for the password of each
account. Set to zero, the aging password option indicates that this option is deactivated
for the corresponding account.
2): in this case the system requests new passwords (as done for 1). In addition, the
Call Server is isolated from the IP network. Only trusted hosts can connect to it. The
installer must declare trusted hosts later, using the netadmin tool.
3): in this case new passwords are requested (as done for 1), the Call Server is
isolated (as done for 2). In addition the SSH function is activated. The SSH function
performs encryption of the calls between machines. For more information on SSH
function, see: Security - Detailed description - Securing exchanges via SSH.
- Y: when the answer is Yes new passwords/password maximum duration are requested (as
for 1), the Call Server is isolated (as for 2) and the SSH function is activated (as for 3).
When the security level selection is performed, the final security configuration is displayed.
For example:
Security configuration:
[+] Default password changed.
[+] Aging password configured.
[+] Isolation from ethernet (trusted host TO BE configured).
[-] The SSH security is currently NOT set.
You are strongly advised to modify the passwords for all Call Server user accounts and also
the passwords recorded on the 4760 at system installation. These modifications should be
performed on the passwords for the root, swinst, mtcl, adfexc, and client (if there is one)
accounts. The modifications should be carried out on all network nodes.
For more information on Alcatel-Lucent recommendations for password management, see:
Security - Detailed description - Recommended password policy.
1.3.1.8 Log Files
Log files can be viewed in the directory /install-log. These files store Call Server installation
and the settings sent to the Installer PC for the boot.
These files may be required by technical support in the event of a problem.
1.3.1.9 Operations Performed by the Technician
Summary of the standard installation method:
- Various V24, Ethernet, etc. connections
- Enter the various parameters/settings on the Installer PC.
- If the drive is not blank:
Run grubboot ETHER command, confirm, the Call Server reboots or:
Reboot the Call Server and run the boot from the BIOS (for the CPU board, Appliance
Server and CS board ); installation starts.
- If the drive is blank, boot the Call Server, and leave installation to be performed
automatically.
1-26 ! " #$ " %&' ( "

153 of 459
) &

1.4 Call Server Installation on a Virtual Machine
1.4.1 Overview
1.4.1.1 Overview
Virtualization dramatically improves the efficiency and availability of resources and
applications. Virtual Machine (VM) software can be used for a number of purposes. Server
consolidation (running multiple logical servers on a single physical machine) is a popular way
to save money on hardware costs and also makes backup and administration easier.
The following topologies are supported by this feature:
- Stand alone OmniPCX Enterprise with a single FlexLM server
- Stand alone OmniPCX Enterprise with FlexLM server duplication
- OmniPCX Enterprise duplication with a single FlexLM server
- OmniPCX Enterprise duplication with FlexLM server duplication
! " #$ " %&' ( "

1-27
154 of 459
Chapter 1 ) &

Figure 1.12: Exemple of OmniPCX Enterprise Duplication with FlexLM server duplication
The FlexLM server is provided in a VM for VMware ESX (ovf format) and this VM can be
installed on the same server as the OmniPCX Enterprise VM or on another server.
- Before R10.1.1, only one OmniPCX Enterprise VM is allowed on a server but other VMs
for applications can be used on the same server. For example, an embedded 4645 voice
mail (16 port) is allowed.
- As of R10.1.1, up to eight virtual machines hosting an OmniPCX Enterprise can run on one
physical machine but embedded 4645 voice mail is not available
- As of R11.0, up to eight virtual machines hosting an OmniPCX Enterprise can run on one
physical machine and embedded 4645 voice mail is available
Prerequisites for the OmniPCX Enterprise VM are:
- 1GB of RAM
- 40 GB for HD
- CPU frequency at 2 GHz/ 2,5 GHz
- Availability for hard disk access: 10 Mbit/s (+2 Mbit/s to be added if 4645 embedded)
- One core dedicated for the OmniPCX Enterprise VM (see: Call Server in Virtual Machine -
Installation procedure - Assign a Virtual Machine to a specific processor/core)
The installation of more than one virtual machine hosting an OmniPCX Enterprise on the same
physical server requires:
- VMware ESXi 5.0
- Hardware, recent enough to provide sufficient capacity.
The following processors, for example, can be used:
Xeon Westmere-EP (35xx, 55xx, or later version)
Nehalem -EX (65xx, 75xx, or later version)
AMD 4000 Valencia and 6000 Interlagos series (or later version)
The OmniPCX Enterprise VM supports RAID - Redundant Array of Independent Disks,
however UPS is not supported.
As of R10.1.1, an OmniPCX Enterprise hosted on a virtual machine, can rely on a SAN
(Storage Area Network) rather than a virtual disk.
The SAN allows the VMotion feature: a virtual machine, hosting an OmniPCX Enterprise, can
be moved from a physical ESX server to another without interruption of service.
The VMotion feature is available:
- For main OmniPCX Enterprise with a very light traffic
- For standby OmniPCX Enterprise
1.4.1.2 Software version
The following software version can been used:
- VMware ESXi Server:
For one Call Server in a physical machine, the VMware ESXi Server: version 4.1.0 and
5.0 are certified
For up to eight server in a physical machine without the 4645 voice mail, the VMware
1-28 ! " #$ " %&' ( "

155 of 459
) &

ESXi Server: 5.0 is certified

For up to eight server in a physical machine with the 4645 voice mail the VMware ESXi
Server: 5.1 is certified
- vSphere Client version 4.1.0, 5.0 or 5.1 according to the VMware ESXi server version
- FlexLM Sever 9.50
1.4.2 Installing the VMware ESXi

1.4.2.1 Overview
OmniPCX Enterprise installation:

Call Server in Virtual Machine - Over-
view Call Server in Virtual Machine - In-
OXE-MS installation: stalling the vSphere Client
OXE Media Services Installation - In-
stallation process overview
The installation described in the following paragraphs applies to OmniPCX Enterprise and
OXE-MS installation on Virtual Machine. It is provided as a guideline only.
The VMWare ESXi Infrastructure is not the responsibility of Alcatel-Lucent. Correct
deployment of virtual machines demands that the ESXi infrastructure has been properly
installed and configured.
See the latest vSphere documentation for more information:
http://www.vmware.com/support/pubs/vs_pubs.html
1.4.2.2 Requirements
The installation of VMware ESXi infrastructure requires:
- A VMware ESXi 5.1 (or higher) for OXE-MS installation on Virtual Machine
- Hardware, recent enough to provide sufficient capacity:
Processors:
Memory: 4Go of physical memory is required for VMware ESXi 5.5
1.4.2.3 Installation Procedure
Before installation
Set the boot order of your server so that it boots from the CD-ROM:
1. Power on the server, insert the VMware ESXi CD, and boot from the CD
The initial boot screen is displayed
! " #$ " %&' ( "

1-29
156 of 459
Chapter 1 ) &

Figure 1.13: Initial boot page example

Ensure ESXi Installer is selected and press Enter .
Note 1:
If you need to change the boot order of the BIOS on the server, change the bios boot order and
reboot the machine, while booting from the CD/DVD ROM drive.
2. The installation routine proceeds.
Press Enter to install the ESXi hypervisor.
Note 2:
This may take a few minutes.
Figure 1.14: Installation welcome page example
1-30 ! " #$ " %&' ( "

157 of 459
) &

3. Press F11 to accept the End User License Agreement.
Figure 1.15: End user license agreement page

4. Select the hard disk drive where you wish to install VMware ESXi to and press Enter to
continue.
Figure 1.16: Disk selection page example

Note 3:
Due to differences in hardware, and hardware configuration, the screens displayed can be different.
The example screenshots provided here were taken from a VMware ESXi instance of VMware ESXi
(ESXi installed virtually on an ESXi hypervisor).
! " #$ " %&' ( "

1-31
158 of 459
Chapter 1 ) &

5. Press F11 to install the ESXi hypervisor.

Note 4:
This erases the data that may be present on the drive you have selected for installation.
Figure 1.17: Installation confirmation page

ESXi installation starts on the physical hardware of the machine.
6. Remove the installation media (CD-ROM, DVD-ROM) and press Enter to reboot the server
and boot into ESXi for the first time.
1-32 ! " #$ " %&' ( "

159 of 459
) &

Figure 1.19: Installation complete page example

When installation is successfully completed, the initial console screen is displayed.
This screen indicates that the VMware ESXI server 5.1.0 is installed. You can proceed with the
configuration of the VMware ESXI server 5.1.0.
1.4.2.4 Configuration Procedure
1. From the summary screen, Press F2 to set up the ESXi hypervisor
! " #$ " %&' ( "

1-33
160 of 459
Chapter 1 ) &

Figure 1.21: Summary screen example

2. Enter your Login Name and Password. The initial default login credentials are root,
without password.
Press Enter when finished.
3. Select Configure Keyboard using the arrow keys, and press Enter.
1-34 ! " #$ " %&' ( "

161 of 459
) &

Select the type of keyboard from the keyboard list.

4. Select Configure Password using the arrow keys, and press Enter.
Figure 1.24: System customization page example

5. Enter your password in the New Password field and Confirm the Password field; press
Enter when finished.
! " #$ " %&' ( "

1-35
162 of 459
Chapter 1 ) &

6. Select Configure Management Network, and press Enter.
7. Select IP Configuration, and press Enter.
1-36 ! " #$ " %&' ( "

163 of 459
) &

8. Use the arrow keys to select Set static IP address and network configuration: and
press the space bar to confirm your choice. Press the down arrow to set the IP address,
Subnet Mask, and Default Gateway fields. Press Enter when you have entered the correct
values.
Figure 1.28: IP configuration page example
! " #$ " %&' ( "

1-37
164 of 459
Chapter 1 ) &

Important:
Changing this address does not affect virtual machine behavior.
However, this address must.
NOT be changed without a good reason
NOT be on the same IP subnet as virtual machine traffic
9. Select DNS Configuration, and press Enter.
10. Enter your network primary DNS server, alternate DNS server, and a hostname.
Note 1:
Do not try to use the option Obtain DNS server addresses and a hostname automatically
1-38 ! " #$ " %&' ( "

165 of 459
) &

Note 2:
You are not required to set a hostname, but if you already have an existing DNS infrastructure,
setting a hostname may be beneficial for future connectivity to the ESXi hypervisor.
11. The Configure Management Network screen is displayed. Press Escape to exit.
A request to Apply changes and restart the management network is displayed, press
'Y' to continue.
When you have validated the changes with Y, the VMware ESXI server 5.1.0 is configured for
your network and the server is restarted . The next step is to create a virtual machine on this
! " #$ " %&' ( "

1-39
166 of 459
Chapter 1 ) &

host with a vSphere client.
1.4.3 Installing the vSphere Client

1.4.3.1 Overview

Call Server in Virtual Machine - In-
stalling the OmniPCX Enterprise on Vir-
tual Machine
stalling the VMware ESXi
OXE-MS installation:
OXE Media Services Installation - Cre-
ating a Virtual Machine for the OXE-MS
installed and configured
For more information, see the vSphere documentation:
In the following example
- The IP address of the ESXi server is 172.19.32.22
- The browser is Microsoft Explorer
Note:
An internet connection is required to download the software.
1.4.3.2 Installation Procedure

1. Open a web browser and navigate to the IP address of your ESXi server.
Enter the IP address in the address bar.
2. If a security warning appears, click Continue to this website (not recommended).

Note:
The display may be different according to the web browser.
1-40 ! " #$ " %&' ( "

167 of 459
) &

The welcome page is displayed.

3. Click Download vSphere Client and save the vSphere client to an appropriate location on
the hard drive.
! " #$ " %&' ( "

1-41
168 of 459
Chapter 1 ) &

Figure 1.35: VMware ESXi welcome page example

4. After downloading the appropriate vSphere client, browse to the directory where the
executable is saved. Double click the file name to run the installation program.
1-42 ! " #$ " %&' ( "

169 of 459
) &

5. Double click the setup file
6. Select the language for your installation from the drop-down list and click OK.
! " #$ " %&' ( "

1-43
170 of 459
Chapter 1 ) &

7. Click Next.
The installation wizard welcome page is displayed.
8. Click Next.
The end-user patent agreement page is displayed.
1-44 ! " #$ " %&' ( "

171 of 459
) &

9. Click Next.
The end-user license agreement page is displayed.
! " #$ " %&' ( "

1-45
172 of 459
Chapter 1 ) &

10. Select the radio button: I agree to the terms in the license agreement, and click Next.
The customer information page is displayed.
1-46 ! " #$ " %&' ( "

173 of 459
) &

11. Enter a User Name and Organization and click Next.

The destination folder page is displayed.
! " #$ " %&' ( "

1-47
174 of 459
Chapter 1 ) &

12. Accept the default installation location and click Next.

A confirmation page is displayed.
1-48 ! " #$ " %&' ( "

175 of 459
) &

13. Click Install.

The installation completed page is displayed.
! " #$ " %&' ( "

1-49
176 of 459
Chapter 1 ) &

14. Click Finish.
1.4.4 Installing the OmniPCX Enterprise on Virtual Machine

1.4.4.1 Overview
Alcatel-Lucent recommends one of the following installation methods to install the OmniPCX
Enterprise on a Virtual Machine.
- Installation of the OmniPCX Enterprise VM through the OmniPCX Enterprise installer
- Installation of the OmniPCX Enterprise VM through the Alcatel-Lucent OmniVista 8770
Network Management System (used to install the OmniPCX Enterprise on an inactive
partition)
For a first installation, follow the instructions detailed: Installation of the OmniPCX Enterprise
VM through the OmniPCX Enterprise installer
1.4.4.2 Installation of the OmniPCX Enterprise VM through the OmniPCX Enterprise
installer
1. Double click the VMware vSphere icon to start the vSphere client.
You can also start the vSphere management console via Start Menu -> All Programs ->
VMware -> vSphere Client
1-50 ! " #$ " %&' ( "

177 of 459
) &

2. Open the vSphere client and login with your user credentials:
IP address: <Your VMware ESXi hypervisor server>
Username: root
Password: <Assigned at installation>
Note 1:
This password has been defined: Call Server in Virtual Machine - Installing the VMware ESXi -
Installation Procedure
Figure 1.47: VMware vSphere client connection page example

Click Login
In some cases, a security warning is displayed
! " #$ " %&' ( "

1-51
178 of 459
Chapter 1 ) &

Figure 1.48: Security warning page example

If you receive a Certificate Warning, select Install this certificate and do not display any
security warnings for "10.1.1.1", and click Ignore.
Note 2:
Certificate Warnings are generated automatically, unless you are working within an internal PKI
infrastructure.
3. When the VMware vSphere Client inventory screen is first displayed initially, it contains no
virtual machines.
1-52 ! " #$ " %&' ( "

179 of 459
) &

Figure 1.49: VSphere client inventory page example

4. Right click the IP address of the ESXi hypervisor to open the contextual menu and select
New Virtual Machine.
Figure 1.50: New virtual machine creation example

5. Select the Typical radio button and click Next
! " #$ " %&' ( "

1-53
180 of 459
Chapter 1 ) &

6. Enter a Name for the virtual machine and click Next.
Figure 1.52: Name and location configuration page example

7. Select your Guest Operating System and Version. Click Next.
For Virtual OmniPCX Enterprise, select Others ->Other (32-bit)
1-54 ! " #$ " %&' ( "

181 of 459
) &

Figure 1.53: Guest operating system page example

8. Select a disk size. Click Next.
! " #$ " %&' ( "

1-55
182 of 459
Chapter 1 ) &

Figure 1.54: Virtual disk configuration page

Note 3:
Alcatel-Lucent recommends a minimum hard disk size of 40 GB for Virtual OmniPCX Enterprise
installation.
9. Select the check box: Edit the virtual machine settings before completion, and click
Continue.
1-56 ! " #$ " %&' ( "

183 of 459
) &

Figure 1.55: Ready to Complete page

10. Select the memory size for your virtual machine and click Finish.
! " #$ " %&' ( "

1-57
184 of 459
Chapter 1 ) &

Figure 1.56: Virtual machine properties page example

Note 4:
You must allocate at least 1 GB
11. The virtual machine is displayed with the new parameters
1-58 ! " #$ " %&' ( "

185 of 459
) &

Figure 1.57: vSphere client inventory with a new virtual machine example
1. Select the Console tab to view the console of the Virtual Machine.
Figure 1.58: Virtual machine console selection example
! " #$ " %&' ( "

1-59
186 of 459
Chapter 1 ) &

2. Launch the OmniPCX Enterprise Installer on a Windows PC to install OmniPCX Enterprise

on the virtual machine
Select the Installation parameters according to your network.
Call Server Type Blade Server
Call Handling version J2501
Country Any (eg:fr)
Installation Type Standard
Network Interface Company network /Direct cable
Network interface - <default>
IP Address - <default>
Ethernet Address - <Virtual Machine Ethernet/Mac Address>
Click Apply
Note 5:
There are no specific constraints for the Virtual OmniPCX Enterprise except for the Call Server type.
Blade Server is used for both Appliance and Blade Server platforms
3. Power on the Virtual Machine OXE_1.
Right click the Virtual Machine and select Power->Power On.
1-60 ! " #$ " %&' ( "

187 of 459
) &

Figure 1.60: Starting a virtual machine example
! " #$ " %&' ( "

1-61
188 of 459
Chapter 1 ) &

4. The OmniPCX Enterprise software starts loading on the Virtual Machine
1-62 ! " #$ " %&' ( "

189 of 459
) &

! " #$ " %&' ( "

1-63
190 of 459
Chapter 1 ) &

1-64 ! " #$ " %&' ( "

191 of 459
) &

5. Select Yes to reboot the OmniPCX Enterprise after the successful installation
! " #$ " %&' ( "

1-65
192 of 459
Chapter 1 ) &

Note 6:
To select the Yes option, make a single mouse click on the console window and use the arrow keys
to navigate to Yes. Press Enter
6. Customization the system according to your needs
1-66 ! " #$ " %&' ( "

193 of 459
) &

Note 7:
The parameters shown in these figures were used for testing
7. Enter the user name and password
! " #$ " %&' ( "

1-67
194 of 459
Chapter 1 ) &

8. Perform Netadmin configuration
1-68 ! " #$ " %&' ( "

195 of 459
) &

Note 8:
When netadmin configuration is completed, you can access the VM- OXE from the network.
VM- OXE configuration is similar to standard OmniPCX Enterprise configuration, except for the
license file. The license used for the VM-OXE must be the license associated to the FlexLM
server licence file, or a specific license request is necessary (.swk file).
Before you configure the FlexLM server on the VM-OXE , ensure that the role of the VM-OXE is
main
1.4.5 Installing the FlexLM server

1.4.5.1 Overview
Licensing with a FlexLM server is used by the OmniPCX Enterprise in the following cases:
- RSI licenses
- In a virtualized CS (e.g. BiCS or OpenTouch), instead of checking the CPU-ID against
the content of the software.mao file, a product-ID is acquired by the FlexLM server. There
is only one product-ID per OmniPCX Enterprise
A FlexLM server can be used by several OmniPCX Enterprise servers.
In earlier OmniPCX Enterpriseversions, each OmniPCX Enterprise could only address one
FlexLM server. If the FlexLM server shuts down (crash, disconnection, or any other reason),
the OmniPCX Enterprise can continue to work for several hours, before raising a panic flag.
! " #$ " %&' ( "

1-69
196 of 459
Chapter 1 ) &

When a panic flag is raised on the OmniPCX Enterprise, the configuration and services
become highly restricted.
To fulfill high availability requirements, current OmniPCX Enterprise versions can rely on a
second FlexLM server .
1.4.5.2 Basic description
In a configuration with one FlexLM server, when the OmniPCX Enterprise requests checkout
of licenses, it sends checkout requests to the FlexLM server. Once the checkout is done, the
OmniPCX Enterprise checks the connection with the FlexLM server by sending heartbeats.
However, the OmniPCX Enterprise can lose the connection with the FlexLM server (for
example, FlexLM server crash) during checkout attempt or heartbeats. In this case, a panic
flag can be raised:
- immediately after checkout failure
- Six hours after the heartbeat connection is lost
In a configuration with FlexLM server redundancy, if the connection is lost, the OmniPCX
Enterprise switches between the two FlexLM servers for four hours until it a reaches a FlexLM
server. If no checkout is performed after four hours, the panic flag is raised.
1.4.5.3 Services provided
In a high availability configuration, the OmniPCX Enterprise provides the following services:
- FlexLM server redundancy: to rely on a second FlexLM server when the first FlexLM
server is unavailable. FlexLM servers are independent. They each provide the same
product-ID
- OmniPCX Enterprise redundancy: when the main OmniPCX Enterprise shuts down, the
stand-by OmniPCX Enterprise (which becomes new main) ensures the licensing service
with the FlexLM server (checkouts, heartbeats)
- Defense: to prevent fraud attempts
1.4.5.4 Prerequisites
Before installation you must have:
- A physical dongle from Aladin Knowledge Systems (type Hasp 4MI USB memory key
Part:#FLEXid-ALA-7200): this dongle defines the FLEX-ID used to authenticate the
OmniPCX Enterprise license file.
- The FlexLM Server DVD: this DVD contains the pre-installed license server in ISO format,
including the OVF FlexLM VM (OVF file to extract from ISO)
- The FlexLM server licence file (extension .ice): license for the FlexLM server for the dongle
- The OmniPCX Enterprise license file (extension .swk). This license file is for the OmniPCX
Enterprise which is virtualized
Note:
All these are required for the installation. If any one of the items is not available, stop the procedure.
1.4.5.5 Installation of OVF FlexLM server on the VMware ESXi server
Ensure that the OVF template contains the following files:
- <VM Name>.mf
1-70 ! " #$ " %&' ( "

197 of 459
) &

- <VM Name>.ovf
- <VM Name>.vmdk
1.4.5.5.1 Deployment of the OVF template
1. From the vSphere client select File > Deploy OVF Template
2. Click Browse to navigate and select the location of the OVF file
! " #$ " %&' ( "

1-71
198 of 459
Chapter 1 ) &

Figure 1.70: Source selection page example
1-72 ! " #$ " %&' ( "

199 of 459
) &

3. Click Next
! " #$ " %&' ( "

1-73
200 of 459
Chapter 1 ) &

Figure 1.72: VMFlexServer detail page example
1-74 ! " #$ " %&' ( "

201 of 459
) &

Figure 1.73: Name and location page example
! " #$ " %&' ( "

1-75
202 of 459
Chapter 1 ) &

Figure 1.74: Disk format page example

4. Click Finish to proceed
1-76 ! " #$ " %&' ( "

203 of 459
) &

Figure 1.75: Summary page example

The FlexLM Server window is displayed to show that deployment is in progress
! " #$ " %&' ( "

1-77
204 of 459
Chapter 1 ) &

Figure 1.77: Installation successful dialog box example

When the virtual machine has been successfully created it is displayed to the left of the
vSphere client
1-78 ! " #$ " %&' ( "

205 of 459
) &

Figure 1.78: Virtual machine list example
1.4.5.5.2 USB dongle installation

Power on the OVF FlexLM Server. Right Click the FlexLM server to display the contextual
menu and select Power>Power On
! " #$ " %&' ( "

1-79
206 of 459
Chapter 1 ) &

The FlexLM server starts booting.
1-80 ! " #$ " %&' ( "

207 of 459
) &

Figure 1.80: FlexLM start example

Select the keyboard type (US English in this example)
! " #$ " %&' ( "

1-81
208 of 459
Chapter 1 ) &

Figure 1.81: Keyboard selection page example

Enter login credentials
- The default username is root
- The default password is letacla
1-82 ! " #$ " %&' ( "

209 of 459
) &

Note:
Ensure you change the password after login
Plug the USB dongle on the USB port and right click the VM. Select Edit Settings from the
contextual menu
! " #$ " %&' ( "

1-83
210 of 459
Chapter 1 ) &

From the Hardware tab, Cclick Add
1-84 ! " #$ " %&' ( "

211 of 459
) &

Figure 1.84: Virtual Machine properties page example

Select the USB Device and click Next
! " #$ " %&' ( "

1-85
212 of 459
Chapter 1 ) &

Figure 1.85: Add hardware page example

The USB dongle is detected and is displayed
1-86 ! " #$ " %&' ( "

213 of 459
) &

Figure 1.86: USB device selection page example

Click Finish
! " #$ " %&' ( "

1-87
214 of 459
Chapter 1 ) &

Figure 1.87: Ready to complete page example

When the USB dongle is detected, it is displayed in the Properties window
1-88 ! " #$ " %&' ( "

215 of 459
) &

Figure 1.88: Virtual Machine properties with USB dongle selected
1.4.5.5.3 Network configuration

Select System > Administration > Network from Inside of the OVF FlexLM server
! " #$ " %&' ( "

1-89
216 of 459
Chapter 1 ) &

Figure 1.89: Network configuration access example

From the Devices tab, select eth0. Click Edit
1-90 ! " #$ " %&' ( "

217 of 459
) &

Figure 1.90: Network configuration page example

From the General tab, select Statically set IP Address. Enter IP parameters. Click OK
! " #$ " %&' ( "

1-91
218 of 459
Chapter 1 ) &

Figure 1.91: Eth0 device properties example

From the DNS tab, enter the hostname for the FlexLM Server
1-92 ! " #$ " %&' ( "

219 of 459
) &

Figure 1.92: DNS configuration page example

From the Hosts tab, click New and enter the IP address and hostname
! " #$ " %&' ( "

1-93
220 of 459
Chapter 1 ) &

Figure 1.93: Hosts configuration tab example
1-94 ! " #$ " %&' ( "

221 of 459
) &

Figure 1.94: Hosts configuration

When configuration of network parameters has been performed, a confirmation request is
displayed. Click Yes to continue.
! " #$ " %&' ( "

1-95
222 of 459
Chapter 1 ) &

Figure 1.95: Network activation

Activate the network: click Activate
1.4.5.5.4 License installation
When network configuration is completed, the license server must be configured.
Copy the license file corresponding to the server (the file with extension .ice). This license to
use must match the license file provided with the dongle, ensure you obtain it.
Note 1:
By default, FTP does not operate on this server. You can copy this file using secure FTP or SCP or from
any media source
- Copy this file to /opt/Alcatel-Lucent/data/licenses
- Restart the FlexLM services: service flexlmd restart
Note 2:
If the hostname configuration is faulty or the license file is not generated for the attached dongle or the
dongle is not attached, the FlexLM Server does not start.
Logs are available in /opt/Alcatel-Lucent/logs/flexlm/.
Verify the FlexLM logs to ensure that the flexlmd service has been started
1-96 ! " #$ " %&' ( "

223 of 459
) &

Details on the VM-OXE license checkout from the FlexLM server are logged in:
/opt/Alcatel-Lucent/logs/flexlm/flexlm_lmlog.log
You have successfully installed and configured the OVF FlexLM server.
1.4.5.6 Installing one FLexLM server for several virtualized OmniPCX Enterprise
servers
- This architecture does not require any specific configuration on the OmniPCX Enterprise
servers or on the FlexLM Server.
- One single dongle is used
- Several license files (.ice extension) must be installed in the FlexLM server
- Several license files (.swk extension) must be installed on each OmniPCX Enterprise
server
Once license files have been installed on all servers, restart the FlexLM service or restart the
virtual machine so that licenses are taken into account. Each OmniPCX Enterprise server can
then register on the same FlexLM server.
In case the FlexLM server is duplicated (which implies that two addresses are declared on
each OmniPCX Enterprise server), two dongles are necessary and twice as many .ice
licenses must be installed on the FlexLM servers.
1.4.5.7 FlexLM Server management on the OmniPCX Enterprise
Configure the FlexLM server on the VM-OXE
Navigate to Mgr#system#Licenses#Review/Modify and configure the following parameters
Figure 1.96: Review/Modify Licenses
Note 1:
Once you have configured the FlexLM server, you need to reboot the VM-OXE to apply modifications
Note 2:
If no FlexLM server responds after four hours, the panic flag is raised on the OmniPCX Enterprise before
displaying Call Installer on Alcatel-Lucent sets.
! " #$ " %&' ( "

1-97
224 of 459
Chapter 1 ) &

1.4.6 Appendix
1.4.6.1 Virtual Machine power on and off
1. Right click the Virtual Machine and select Power > Power On
2. Right click the Virtual Machine and select Power>Power Off
1-98 ! " #$ " %&' ( "

225 of 459
) &

Note:
Ensure that the virtual machine is properly shut down before power off
1.4.6.1.1 Automatic power on and off
1. Fromthe VM Host, select the Configuration tab
Select Virtual Machine StartUp/ShutDown from the Software list
Click Properties to display the System settings window
! " #$ " %&' ( "

1-99
226 of 459
Chapter 1 ) &

2. In the System settings pane, select Allow virtual machines to start and stop
1-100 ! " #$ " %&' ( "

227 of 459
) &

automatically with the system and enter the values in seconds (five seconds
arerecommended) for both Startup and Shutdown delays.
Select the order for Startup by selecting the servers and using the Move up and Move
downbuttons
Click OK
3. In this example, automatic power on and off are enabled for virtual machines
! " #$ " %&' ( "

1-101
228 of 459
Chapter 1 ) &

1.4.6.2 Assign a Virtual Machine to a specific processor/core

1. Before assigning a specific processor to the Virtual Machine, ensure that:
The host machine is equipped with a multiprocessor
The Virtual Machine is powered off
2. In the vSphere client inventory panel, select a virtual machine and select Edit Settings
1-102 ! " #$ " %&' ( "

229 of 459
) &

3. From the Virtual Machine Properties window, select the Resources tab.
Select Advanced CPU.
! " #$ " %&' ( "

1-103
230 of 459
Chapter 1 ) &

In the Scheduling Affinity area, enter the processor that you want to assign to the virtual
machine
1.4.6.3 Export OVF image/template from the VMware ESXi server
You must power off the Virtual Machine to export OVF Template, otherwise the export option
will be disabled.
1. Select the virtual machine to export
2. Power off the selected VM
3. Go to File>Export>Export OVF Template
1-104 ! " #$ " %&' ( "

231 of 459
) &

Figure 1.106: Export OVF template window example
Figure 1.107: Export file example

The virtual machine has been successfully exported via OVF Image/Template
1.4.6.4 Install VM OXE (OVF image) from one ESX towards another ESX
! " #$ " %&' ( "

1-105
232 of 459
Chapter 1 ) &

If you have an OVF image/template of a Virtual Machine OmniPCX Enterprise, see: Call
Server in Virtual Machine - Installing the FlexLM server - Deployment of the OVF template to
install.
Otherwise refer the following sections:
- Export OVF image/template from the VMware ESXi server
- Call Server in Virtual Machine - Installing the FlexLM server - Deployment of the OVF
template
1.5 Using the Multi-Partition
1.5.1 Commissioning
1.5.1.1 Overview
When a hard drive is formatted, partitions are created to host a second Call Server release.
This enables an upgraded release to be installed while conserving the current release, phone
unavailability time to be reduced and hard drive handling operations to be avoided.
This operation can be performed with the phone running or shut down. This is of no advantage
if the phone is shut down. There is no impact on users if the phone is running: the file
operations performed on the file-systems do not affect call-handling in any way.
Multi-partitioning can only be used if all partitions are kept at the same size. That is, if the new
Linux release, in the case of a standard installation, formats all partitions to the same size as
that of the release to be upgraded. Otherwise, a standard installation must be performed (with
reformatting. The old release is not kept).
The term "second partition" will generally be used, although, there are, in fact, several
duplicated partitions. The new release to be installed may contain a new Linux release
(upgrade or major release) or only telephone binaries (that is, be a full release or just patches).
The current release is said to be on the "active" partition. The new release is said to be
installed on the "inactive" partition.
The database is duplicated on one of the inactive partitions. It may be translated with swinst
either before or after the new release takes effect. Translation is also performed automatically
when the phone is started if it was not done previously.
After installation on the inactive partition, the operation for changeover to the new release is
referred to as a "switch". This must be manually triggered. Various operations are then
performed on the different file-systems and a reboot is performed. The new release then
switches to the new active partition.
Not all partitions are duplicated. Some remain common whatever the state before or after a
switch (see Structure ).
"Second" partitions cannot be seen by the user. Once the switch to a new release has been
performed, the user does not need to concern himself about file paths or paths for other
operations: the syntax remains identical. All such details remain hidden to the user as a Unix
link mechanism is used for this feature.
The multi-partition method is also used by the "Remote downloading" application (available as
from R5.1). This application can also be used to install a Call Server (remotely or even locally).
1-106 ! " #$ " %&' ( "

233 of 459
) &

Important:
The Linux and Chorus operating systems are not compatible, it is therefore not necessary to
upgrade an OmniPCX 4400 from an OmniPCX Enterprise (or vice-versa).
1.5.1.2 Structure
The main common file-systems are:

/dev/hda9 on /usr4 type ext2 (rw) Contains accounting, traffic analysis and various
trace files, etc.
/dev/hda15 on /usr7 type ext2 (rw) Contains voice guides.
Eva partition Contains the 4645 voice mail service.
Duplicated file-systems:
/ Root (hosts the Linux OS)
/usr2 Contains the telephone release.
/usr3 Contains the database.
/var Contains system information used by Linux.
The partition containing the crashdump is not duplicated.

1.5.1.3 Methods
All operations are performed using the "swinst" tool and the Enterprise PC Installer software.
The Installer PC must be run in "Telephone or Patch" mode (the dhcp server is not used). For
more information about this application, see the Enterprise PC Installer - Commissioning .
The different examples given below describe the methods to be applied. The "swinst" paths
shown are paths starting from the general expert menu.
To reduce the time required for some operations, "swinst" (in addition to performing installation
procedures) also has menus for duplicating partitions or Linux/database data:
- Duplication of Linux.
- Duplication of Linux data (IP configuration, crontabs, timezone, etc.).
- Duplication of telephone binaries.
- Duplication of the "mao" database.
Linux and telephone releases on second partitions can be identified with "swinst": "8 Software
identity Display/ 1 system release identity" for Linux. The result shows Linux release for both
partitions.
"8 Software identity Display/ 1 Application software identity" gives telephone release. You are
then asked to select the active or inactive partition.
1.5.1.3.1 Installing a full new release (major Linux release, Linux upgrade, telephone
binaries, patches)
The different phases are:
- Installation of Linux on the inactive partition.
- Installation of the full telephone release on the inactive partition.
! " #$ " %&' ( "

1-107
234 of 459
Chapter 1 ) &

- Installation of static/dynamic patches on the inactive partition.

- Copying of Linux/database data to the inactive partition.
Caution 1:
Installing Linux on the second partition overwrites ALL DATA on the second partition (Linux,
telephone, database, Linux data). This was not the case in releases supporting the Chorus O.S.
"1 package installation/
4 install linux on unactive version from server"
Then, answer the questions:
- IP address or name of the server (the Installer PC)
- directory of the new Linux release:
"<drive>/dhs3mgr/<version>/pcmao/boot_res/bootp/linux"
Example 1:
"c:/dhs3mgr/e1604/pcmao/boot_res/bootp/linux"
- Name of the new Linux release (e.g. 8.0) 8.0)
- Then, to the question "clean the second Linux version", answer "y"
- Answer "y" to the question on the boot server, then "y" to the following question as to
whether the current "/bootp/linux" is to be cleaned (only asked if a previous release is
already installed).
Installation of Linux starts.
Caution 2:
See Known problems with e1.604 (Linux 8.x) .
"2 deliveries installation/
1 install delivery from server"
Answer "1" to the question on the active or inactive partition.
Give the IP address of the Installer PC.
Give the name of the release/path of the release to be installed.
Example 2:
"c:/dhs3mgr/e1604". Currently, the drive that can be selected in the Installer PC is not taken into account:
this is why it is given in "swinst". In future Call Server/PC Installer releases, this will not need to be
entered.
Confirm with "y". Installation of the telephone binaries starts. Repeat the last operation for the patches.
1.5.1.3.2 Installing a full release without a major new release of Linux, with or without a
Linux upgrade and with no telephone patches
In this case, installation of a Linux upgrade is automatic and is performed in the same way as
installation of new facilities.
- Linux/ Linux data is copied to the inactive partition (if Linux is not installed on the second
partition or another release of Linux is installed on the second partition).
1-108 ! " #$ " %&' ( "

235 of 459
) &

- Installation of the full release on the inactive partition.

- Copying of the "mao" database to the inactive partition.
"3 cloning and duplicate operation/
2 partition duplication/
5 duplicate all"
"Duplicate all" can be replaced by "1 duplicate linux, packages and linux data", which is faster.
"2 deliveries installation/
1 install delivery from server"
Answer "1" to the question on the active or inactive partition.
Give the IP address of the Installer PC.
Give the name of the release/path of the release to be installed.
Confirm with "y". Installation starts.
Finish with "duplicate database" if this has not been done or to be sure that the modifications
made by call-handling during installation are applied.
Database translation (if any) will be automatically performed at reboot or can be triggered
manually:
"7 database tools/
1 database translation"
Then select "1" for the inactive partition. A new menu is displayed. Select "3 running", then "4
running".
1.5.1.3.3 Installing a full release without a major new release of Linux, with or without a
Linux upgrade and with dynamic and/or static patches
- Installation of the major telephone release (see above, Installing a full release without a
major new release of Linux, with or without a Linux upgrade and with no telephone patches
).
- Installation of the static patch (see above, Installing a full release without a major new
release of Linux, with or without a Linux upgrade and with no telephone patches ).
- Installation of the dynamic patch (see above, Installing a full release without a major new
release of Linux, with or without a Linux upgrade and with no telephone patches ).
1 duplicate linux, packages and linux data".
Continue with installation of the full release, then the patch(es).
Finish by copying the database and translation.
1.5.1.3.4 Installing a new static or dynamic patch
If only a dynamic patch is to be installed, use of the multi-partition is not the best method.
! " #$ " %&' ( "

1-109
236 of 459
Chapter 1 ) &

Simply install the dynamic patch with the phone running, the telephone is then always
available. However, the multi-partition method can be used.
- Copying of telephone binaries to the inactive partition (if the release on the second partition
is not the same).
- The previous two phases can be replaced by "duplicate all", which is simpler.
- Installation of the static patch (see above, Installing a new static or dynamic patch ) and/or:
- Installation of the dynamic patch (see above, Installing a new static or dynamic patch ).
5 duplicate all":
This is if the second partition is empty or not the same level as the full release. Otherwise, this
part can be left out.
The Call Server knows that it must not delete the telephone release already installed. "swinst"
and "Linux" (if present) are automatically installed.
If you are sure that the telephone release on the inactive partition is identical to that on the
active partition, then only installation of the patch and copying of the database need to be
performed.
There is no translation between different static or dynamic patches.
1.5.1.3.5 Installing a delta
A delta is always installed by remote downloading.
- Copy (automatic) of the active version on the inactive partition.
- Installation on the inactive partition.
- Switch (manual, deferred, or automatic when installation is complete).
For more information, see the Remote download / installation - Detailed description - Installing
a Delta.
1.5.1.3.6 Exact copy of the current release
5 duplicate all"
1.5.1.4 Switch
In "swinst":
"Cloning & duplicate operation/
3 Switch on unactive partition".
The switch may be deferred (scheduled in advance for the same day) to avoid disturbing
traffic.
1-110 ! " #$ " %&' ( "

237 of 459
) &

After loading the delta, the system also offers switchback, allowing the old version to be used
in the event of a system reboot (accidental or deliberate), for more information, see the
Remote download / installation - Detailed description ).
Confirmation will be requested and whether telephone auto-start is to be kept.
Caution:
Do not shut down the CPU from this time and up to the time of BIOS startup: this may result in
the Linux OS being unable to start.
1.5.1.5 Releases
Use of the multi-partition is operational as from release R3.0 Ux and R5.0Lx (e1.604.8
minimum).
1.5.1.6 Known problems with e1.604 (Linux 8.x)
Just after installation of a major new Linux release, Linux data must be copied. This is because
an error, just before the end of installation, results in this data not being fully duplicated.
Error:
"shell-init: could not get current directory : getcwd : cannot access parent directories : No such
file or directory
This problem will be addressed in the next software release (major new Linux release).
However, for this correction to be operational, the current release must be switched to active
release to benefit from the correction. As from the new release, installation of a major Linux
release will result in Linux data being correctly copied automatically.
1.6 Remote Download/Installation
1.6.1 Detailed description

1.6.1.1 Overview
This function allows software updates to be performed for one or more networked Com
Servers from a single geographical site.
It offers the advantage of using only one swinst menu to perform two different remote actions
(transfer and installation) on several machines (see the Swinst - Detailed description ).
In R5.1, remote transfer and installation can be performed over IP and on ABC network (but
not via the public network).
A Com Server comprises two partitions (for more information, see the Standard Call Server
installation - Overview ). The first partition contains the active version, that allows the
telephone to operate. The second partition contains the inactive version, that will be installed
remotely.
Software updates are transferred to the part common to both partitions.
Installations are performed on the second partition and do not affect updated Alcatel-Lucent
OmniPCX Enterprise CS telephone operation.
Any installation can be performed locally (see the Using the multi-partition - Commissioning )
or via the Remote Download swinst menu.
Two types of updates can be performed:
! " #$ " %&' ( "

1-111
238 of 459
Chapter 1 ) &

- Full update (the entire telephone version).

- Partial update (of a static or dynamic patch).
Note:
A dynamic patch can be updated on the active partition of the remote Com Server, without affecting
installation operation.
Important:
- Delta update must not be used anymore.
- The Linux and Chorus operating systems are not compatible, an OmniPCX 4400 cannot be
upgraded from an OmniPCX Enterprise (or vice-versa).
1.6.1.2 Terminology
Archive: This is the compact structure of the uninstalled software update, to be transferred or
installed on a Com Server (see the Standard Call Server installation - Overview ).
An archive may be:
- A version: full update of the Com Server software part, see the Standard Call Server
installation - Overview .
- A static patch: partial software upgrade (binaries), see the Standard Call Server
installation - Overview .
- A dynamic patch: partial software upgrade, see the Standard Call Server installation -
Overview .
The archive can be transferred or installed on another Com Server. This target Com Server is
called Com Server Client.
The Com Server from which the archive is transferred is either a Com Server Master or a Com
Server Distributor. During archive transfer, the Com Server Client becomes a Master or
Distributor.
According to system configuration, a Com Server Client may become Com Server Master. In
this case, it transfers (or installs) only one version, one patch, and one dynamic patch on a
Com Server Client. If transfer is performed from a Com Server Master to the Com Server
Client, the new archive overwrites previous versions of the same type of archive on the Com
Server Client.
According to system configuration, a Com Server Client may also become Com Server
Distributor. In this case; it transfers (or installs) one or more versions and/or one or more
patches (static and/or dynamic). If transfer is performed from a Com Server Distributor to the
Com Server Client, the new archive does not overwrite previous versions of the same type of
archive.
Example:
Transfer of version e2.401 to a Com Server Client containing version e1.604. If the Com Server by which
the transfer transits is Master, the new version, e2.401, overwrites the previous version, e1.604. If the
Com Server by which the transfer transits is Distributor, both versions e2.401 and e1.604 are available in
the part common to both partitions of the Com Server Client.
A download consists in transferring an archive. It is performed either from a PC (equipped
with the PC Installer software - see Enterprise PC Installer - Commissioning ) or from a Com
Server (to which the archive has already been transferred from a PC). Downloading from a
Com Server allows several simultaneous installation operations to be performed from one (or
more) Com Servers.
1-112 ! " #$ " %&' ( "

239 of 459
) &

An installation must be performed by a Com Server. The archive is installed either on another
Com Server or on the Com Server initiating installation.
1.6.1.3 Requirements
Depending on site configuration and the updates to be performed, the resources required may
be different.
Good knowledge of the client network topology is essential. In all circumstances, the following
items are required.
1.6.1.3.1 Hardware
- A PC equipped with an Ethernet board to load the Com Server Master/Distributor.
- A Com Server (version higher than e1.604) with a capacity of 8 GB or higher used as
Master/Distributor,
- On OmniPCX 4400 rack: an external hub connected to the CPUx board ensuring the Com
Server functions.
1.6.1.3.2 Software
- The PC Installer tool: this is required to perform the first archive transfer, from the PC to a
Com Server (see the Enterprise PC Installer - Commissioning ),
Note:
For software loading on CHORUS operating system (OmniPCX 4400), the loading software is not PC
Installer but bootnet.
- One or mores archives (as delivered by Alcatel-Lucent).
1.6.1.3.3 Connection
The names or IP addresses of the transfer or installation target Com Servers (Com Server
Clients) and of the Com Servers (Master or Distributor) and/or the PC.
1.6.1.4 Operation
To be able to perform remote download, all hosts must be declared (in a secure configuration).
Remote sites are configured via netadmin (see the netadmin - Operation - Routing).
1.6.1.4.1 Transfer
Archive transfer (or download) is the very first operation to perform.
Using the Enterprise PC Installer software, the archive is transferred to the part common to
both versions of a Com Server.
! " #$ " %&' ( "

1-113
240 of 459
Chapter 1 ) &

Figure 1.108: Software Transfer to Com Server

The Remote download menu is then used to transfer the archive from this Com Server
(which becomes the source: Com Server Master/Distributor) to another, target, Com Server
(Com Server Client) on the network. The Remote load submenu allows an archive to be
transferred to a Com Server Client without installing it.
Figure 1.109: Software Transfer from Master CS to Client CS
1.6.1.4.2 Installation
After transfer, the archive is installed on the inactive version (second partition) of the Com
Server.
Note:
For a full version, at the end of installation, do not forget to copy the database from the active partition to
the second partition loaded with the new version (see the Swinst - Operation - Duplicating inactive
version partition).
1-114 ! " #$ " %&' ( "

241 of 459
) &

A patch can only be installed on the corresponding basic version. For example, patch f1.500.4
may be installed if the basic version on the second (inactive) partition is f1.500. If the inactive
version is f1.400, patch f1.500.4 cannot be installed.
Figure 1.110: Software Installation on the Inactive Partition

The Remote install menu allows an archive present on the common part of another Com
Server to be installed on the inactive version of a second Com Server.
Figure 1.111: Remote Installation
1.6.1.4.3 Switch
To implement the full version update or the patch installed on the inactive version, the versions
must be switched. Version switch is a separate menu (see the Swinst - Operation - Switching
versions (active - inactive)).
! " #$ " %&' ( "

1-115
242 of 459
Chapter 1 ) &

Figure 1.112: Partition Switch

After switching the versions, return to the swinst menu to complete installation (and answer the
questions from the application about the type of installation).
Caution:
Do not confuse this switch between active and inactive versions and that of a duplicated Com
Server (from the Com Server Main and the Com Server Stand-by), for more information, see the
Call Server duplication - Overview.
As this operation restarts the system, switches should preferably by performed outside busy
(high traffic) periods to avoid disturbing the telephone. The swinst menu allows a switch to be
scheduled in advance for the same day.
1.6.1.4.4 A Special Case: Duplicated Com Server via ABC
Whether it is a transfer or an installation, the procedure operates on an IP/X25 tunnel
(declared under netadmin).
1-116 ! " #$ " %&' ( "

243 of 459
) &

Figure 1.113: Remote Installation via ABC Network

When the Com Server Client tunnel IP address is used, the archive is transferred (or installed)
to the Com Server Main.
To transfer/install the archive to the Com Server Stand-by, use the machine physical IP
address (by configuring the route via the netadmin menu).
Caution:
This case must not be used via a non IP ABC-F logical link.
1.6.1.4.5 Archive Location in a Com Server

Depending on their types, archives are transferred in the following Com Server
Master/Distributor directories:
- /usr4/ftp/tftpboot/Rload/version for full versions.
- /usr4/ftp/tftpboot/Rload/patch for static patches.
- /usr4/ftp/tftpboot/Rload/dynpatch for dynamic patches.
1.6.1.5 Compatibility
Operating environments (Operating Systems) Linux and Chorus are not compatible. In other
words, an Alcatel-Lucent OmniPCX Enterprise CS archive cannot be downloaded (or
installed) on an OmniPCX 4400 CPUx and vice versa. The PC software for download is PC
Installer under Linux (Alcatel-Lucent OmniPCX Enterprise CS) and Bootnet under Chorus
(OmniPCX 4400).
The rload tool is available from R5.1.
In R5.1, download (or installation) via the public network is not available. Future development
will allow use of the PPP protocol via IO2.
Remote download/installation swinst menus sometimes propose to use a gateway machine
to access a Com Server. Systematically answer no each time the use of a gateway is
proposed.
1.6.1.6 Remote Download Operation Using OmniVista 4760
! " #$ " %&' ( "

1-117
244 of 459
Chapter 1 ) &

The OmniVista 4760 allows to perform the software update (immediate or scheduled) of many
remote Com Servers and/or Passive Communication Servers.
For more information on software update using OmniVista 4760, see section 9 - Maintenance
of the OmniVista 4760 Administrator Manual.
1.6.2 Operation
1.6.2.1 Accessing the Menu
- Open a session under the swinst account (see the Swinst - Detailed description ).
- Select option 9 Remote download.
ALCATEL BUSINESS SYSTEMS
Remote Download menu Installation FACILITIES 2.20.0
1 Remote install of a client CPU
2 Retry the last remote install operation (if justified)
3 About last remote install (if trace exists)
4 Remote load a CPU as master or distributor
5 Retry the last remote load operation (if justified)
6 About last remote load operation (if trace exists)
7 Cleaning operation on master/distributor CPU
8 Programmed operations
9 Fast Delta programmed operations
Q Go back to previous menu Your choice [1..9, Q]
1.6.2.2 Transfer from a Call Server Master or a Call Server Distributor

Select option 4 Remote load a CPU as master or distributor for any new transfer.
Enter the name or IP address of server (return for this CPU, q to quit) ->
Enter the name or IP address of the server, the default server being the Call Server on which
the remote download process is started.
Example:
Enter the name or IP address of the server
(return for this CPU, q to quit) -> 192.168.4.29
Enter the type of the server
1 Windows server
2 Unix server
3 Call server
q to quit => 1
Enter the name or IP address of the CLIENT CPU
(return for this CPU, q to quit) ->
The Windows server source is : 192.168.4.29
The CLIENT CPU is : oxe
Checking connections
**
The system immediately proposes to download the deltas, a new version or a patch to the Call
Server that will be a Master or Distributor.
Remote load of delta ? (y/n q to quit): n
Delta update must not be used anymore.
Remote load of version ? (y/n q to quit) y
With a Windows server, the system asks for the exact version name, before proposing any
patch download.
Enter the name of version (q to quit) =>e2.400
Remote load of patch ? (y/n q to quit) n
Remote load of dynamic patch ? (y/n q to quit) n
The system asks for the installation countries of the machines to be loaded.
1-118 ! " #$ " %&' ( "

245 of 459
) &

Enter the countries

To choose all, press return.
To display the possible choice, enter ?
To end a selection, enter a null line (just enter).
To quit, enter q
=> fr
=>
Then select whether the Call Server Client is Master or Distributor
1 for a distributor CPU (default)
2 for a master CPU
q to quit
=> 2
Confirm download.
Confirm the remote load of e2.400 (y/n, default y): y
Select the type of checking you want to be performed after download.
Client checking after remote installation
1 for no check (default)
2 for size of files
3 for size and checksum of files
q to quit
=> 3
Installing client CPU ...
1.6.2.2.1 In Case of Failure (Connection Lost)

As download concerns several modules, in the event that the link is lost between the server
and its client, the number of uninstalled modules is registered and installation can resume from
the point at which it was interrupted.
Select option 5 Retry the last remote load operation (if justified)
If no information has been registered on the Call Server client, the tool displays:
No retry information is available
Press return
If installation has been successfully completed, the tool displays:
All modules are already installed on 192.168.4.56
1.6.2.2.2 Checking Previous Transfer

Select option 6 About last remote load operation (if trace exists).
When connection is possible, the tool details the inputs and errors noted during the previous
operation. Checking is made on the Call Server Client.
1.6.2.3 Remote Installation
Select option 1 Remote install of a client CPU for any new installation. Installation
(of the version, of a patch (static or dynamic) is performed on the Call Server Client inactive
version. The server must be a Call Server previously declared as Master or Distributor.
Note:
A dynamic patch (alone) can be installed on the Call Server active version.
Example:
Enter the name or IP address of the MASTER/DISTRIBUTOR CPU
(return for this CPU, q to quit) -> 192.168.4.56
The MASTER/DISTRIBUTOR CPU is : oxe
The CLIENT CPU is : 192.168.4.56
Please confirm this choice (y/n, default y):y
**
Enter the version to be installed.
! " #$ " %&' ( "

1-119
246 of 459
Chapter 1 ) &

Please enter the version (enter for none)

The versions available are the following:
E2.350
E2.400
>E2.400
Confirm installation of the selected version
Confirm the remote install of E2.400
(y/n, default y):
1.6.2.3.1 In Case of Failure (Connection Lost)

As installation concerns several modules, in the event that the link is lost between the Call
Server Master/Distributor and its client, the number of uninstalled modules is registered and
installation can resume from the point at which it was interrupted.
Select option 2 Retry the last remote install operation (if justified)
If no information has been registered on the Call Server client, the tool displays:
No retry information is available
Press return
If installation has been successfully completed, the tool displays:
All modules are already installed on 192.168.4.56
Note:
Installation of a dynamic patch on the active partition must be resumed via option 1 Remote install
of a client CPU.
1.6.2.3.2 Checking the Last Installation Performed

Select option 3 About last remote install (if trace exists). Checking is made
on the Call Server Client.
Example:
(return for this cpu, q to quit) >192.168.4.56
the CLIENT CPU is : pabx56
Please confirm this choice (y/n, default y): y
**
Example installation of version E2.400 on a machine in France. Delivery comprises a major
Linux 3.0 version, a Linux 3.2 update, and a patch to be installed on a machine in France
(country code: fr).
The master or distrib cpu checking is correct
***************************
BEGIN INSTALLATION OF MODULE 3.0...
Secdonde version cleaned
Getting Rload/version /E2.400/linux/3.0from...
Getting the .rpm files from ...
Installing the RPM packages...
Installing the bootp server...
THE MODULE 3.0 IS CORRECTLY INSTALLED
***************************
BEGIN INSTALLATION OF MODULE LINUX...
Checking linux version
Transfer for pkg part in preparation
List of packages...
Installing ... package
package installed
...
THE MODULE linux IS CORRECTLY INSTALLED
***************************
BEGIN INSTALLATION OF MODULE facil...
List of packages...
1-120 ! " #$ " %&' ( "

247 of 459
) &


package installed
...
THE MODULE facil IS CORRECTLY INSTALLED.
***************************
BEGIN INSTALLATION OF MODULE RPMS...
List of packages...
package installed
...
New LINUX patch 3.2 is correctly installed
THE MODULE RPMS IS CORRECTILY INSTALLED
***************************
BEGIN SINTALLATION OF MODULE fr...
List of packages...
Common post installation
List of operations...
End of post installation
THE MODULE fr IS CORRECTLY INSTALLED
Press return
1.6.2.4 Switching Versions Manually

This option allows the version installed on the inactive partition to be switched to the active
partition. The telephone is shut down during the switch operation.
Return to the initial swinst Expert menu.
Select option 3 Cloning & duplicate operations.
The options offered by the application are listed in the Swinst - Operation - Switching versions
(active - inactive).
1.6.2.5 Cleaning a Call Server Master/Distributor
This option allows any delivery to be removed remotely (or locally) from a Call Server
Master/Distributor.
Select option 7 Cleaning operation on master/distributor CPU.
Example:
(return for this cpu, q to quit) >192.168.4.56
The CLIENT CPU is : pabx56
Please confirm this choice (y/n, default y): y
**
Remove version E2.400 (y/n): y
Remove patch E2.400.1 (y/n): y
You are going to remove these deliveries on master/distrib cpu pabx56
version E2.400
patch E2.400.1
Please confirm your action (y/n, default y):
Done
Press return
1.6.2.6 Programming a Sequence of Operations

A sequence is a series of operations required for remote download. It can be programmed in
advance then executed on demand simultaneously with other sequences.
When a sequence is being programmed, the application asks the same questions as for each
individual operation.
! " #$ " %&' ( "

1-121
248 of 459
Chapter 1 ) &

Example:
1. Transfer CD-ROM content to a Call Server.
2. Transfer (or install) the archive to another Call Server.
3. Transfer (or install) the archive to a third Call Server via IP tunnel
Figure 1.114: Programming a Remote Download

If connection is impossible, the corresponding sequence is stopped. The next sequence is
executed. The Call Server Master/ Distributor performing the installation must be permanently
connected.
Select option 8 Programmed operations.
Caution:
If the The job Execute sequences is working message is displayed when the menu is
opened, wait for job execution to end before creating or deleting a sequence of operations.
1.6.2.6.1 Creating or Modifying a Sequence

In the 8 Programmed operations option submenu, select option 1 Create/overwrite
a sequence.
If no sequence has been defined, the tool displays:
No sequences
If sequences have been defined, the tool details all the sequences already registered.
Example:
1-122 ! " #$ " %&' ( "

249 of 459
) &

SEQUENCE : 1
-------------
OPERATION : Remote load a cpu as master or distributor
Source name : cdar37
Server type : Call Server
Client CPU : clin13
Version delivery to load : E1.502
Patch delivery to load : no
Dynamic patch to load : no
list of export : fr
type of cpu to load : DISTRI
Client checking after remote installation : no check
SEQUENCE : 2

OPERATION : Remote installation of the client CPU
Master CPU : clin13
Client CPU : clin12
Version delivery to install : E1.502
Patch delivery to install : no patch installation
Dynamic patch to install : no dynamic patch installation
Master checking before remote installation : presence of files
Connection during the remote installation : connected
Entrer the number of sequence to create or overwrite : 1
In the submenu, select the desired type of sequence:
Choose the operation to program
1 Make a remote install of a client CPU
2 Retry a remote installation
3 Edit the log file of a remote installation
4 Load a CPU as master or distributor
5 Retry a remote load
6 Edit the log file of a remote load
>4
Enter the name or IP address of the server
If you have to use a GATEWAY, enter its name or IP adress
(return for no) ->
Press Enter (for no).
Reminder:
If the operation is not performed via the public network, systematically answer no to any question on
GATEWAY.
Some choices can be made while the sequence is being executed instead of programming
them in advance.
Example:
Remote load of version ?
(y/n q for manual choice at execution time)
> q
1.6.2.6.2 Deleting a Sequence

In the 8 Programmed operations option submenu, select option 2 Delete a
sequence.
The tool lists the sequences already registered, then prompts:
Enter the sequences to delete (blank separated and return)
=>
Enter the numbers of the sequences to delete (separated by the space character).
The tool confirms deletion
Done
Press return
1.6.2.6.3 Show Existing Sequences

In the 8 Programmed operations option submenu, select option 3 List sequences.
! " #$ " %&' ( "

1-123
250 of 459
Chapter 1 ) &

1.6.2.6.4 Executing One or More Sequences

In the 8 Programmed operations option submenu, select option 4 Execute
sequences.
Enter the numbers of the sequences to execute (separated by a space) in the order of their
execution.
Example:
Enter the sequences to execute (blank separated and return)
=> 1 2

EXECUTE SEQUENCE : 1

**
Installing cpu client ...
Source address : cdar37
Type of source : UNIX
Client cpu : 192.40.103.213
etc.
END OF REMOTE LOADING OPERATION AT
DATE : 03/19/02 TIME : 15:19:32
As soon as this sequence has been executed, the tool immediately starts execution of the next
sequence.

EXECUTE SEQUENCE : 2

*
Installing cpu client ...
The master or distrib cpu checking is correct
etc.
THE MODULE fr IS CORRECTLY INSTALLED.

PROGRAMMED EXECUTION ENDED

Press return
1.6.2.6.5 Checking Connections

This operation is particularly useful after creating a sequence to check the status of the
connection between the server and the client. It triggers the traceroute command, that
details routing through the various hosts, including routers and gateways.
In the 8 Programmed operations option submenu, select option 5 Check
connections.
Example:
Enter the sequences to check (blank separated and return)
=> 1 2

CHECK SEQUENCE : 1

**
traceroute to cdar37 (155.132.43.67), 20 hops max, 38 byte packets
1 colomcC3MC43 (192.40.103.254) 16.646 ms 13.045 ms 51.676 ms
2 broadcast (155.132.43.67) 0.968 ms 0.956 ms 0.919 ms
traceroute to clin12 (192.40.103.212), 20 hops max, 38 byte packets
1 clin12 (192.40.103.212) 12.412 ms * 1.020 ms
Connections successfully checked

CHECK SEQUENCE : 2

*****
Impossible to make the connection between server_name and client_name
1-124 ! " #$ " %&' ( "

251 of 459
) &

1.6.2.6.6 Programming Execution of One or More Sequences

Execution of one or more sequences can be programmed up to 24 hours in advance. These
sequences must be accurately defined (manual choices during execution are not allowed).
In the 8 Programmed operations option submenu, select option 6 Postponed
operations.
Note:
Only one execution (comprising one or more sequences) can be programmed in advance.
Example:
No postponed execution has been registered
1 Set a posponed execution
2 Cancel a postponed execution
3 List the registered sequences
Q Go back to previous menu
Your choice [1..3, Q] 1
EXISTING SEQUENCES
------------------
SEQUENCE : 1
-------------
OPERATION : Remote load a cpu as master or distributor
Source name : cdar37
Server type : Windows
Client CPU : clin13
Version delivery to load : E1.502
Patch delivery to load : no
Dynamic patch to load : no
list of export : fr
type of cpu to load : DISTRI
SEQUENCE : 2

OPERATION : Remote installation of the client CPU
Master CPU : clin13
Client CPU : clin12
Version delivery to install : E1.502
Patch delivery to install : no patch installation
Dynamic patch to install : no dynamic patch installation
Master checking before remote installation : presence of files
Connection during the remote installation : connected
Enter the sequences to execute (blank separated and return)
=>1 2
At which time do you want to execute the sequence ?
1 - Hours ( between 0-23 ) :22
2 - Minutes ( between 0-59 ) : 0
Your request is registered
Press return
Cancelling Programmed Execution

Select option 2 Cancel a postponed execution.
Example:
A postponed execution is set at : 2003-02-25 22:00
1 Set a postponed execution
2 Cancel a postponed execution
3 List the registered sequences
Your choice [1..3, Q] 2
Your postponed execution is canceled
Press return
Checking Execution Details

Select option 3 List the registered sequences to display the detail of the different
sequences programmed for postponed execution.
! " #$ " %&' ( "

1-125
252 of 459
Chapter 1 ) &

Checking the Last Execution Performed

Select option 7 About last programmed execution.
Note:
This menu is available only if traces of the last operations exist.
1.6.3 Maintenance
1.6.3.1 Useful Commands
- ping: from the Call Server Master/Distributor to the Client and vice versa allows checking
that the IP connection is set up between both machines.
- traceroute: to check the status of the routes between both machines.
1.6.3.2 Typical swinst Error Messages
- Permission denied: means that host not declared (see :netadmin - Overview)
- Error when connecting to client CPU: means that the client network cannot be
reached
- The client entry point cannot reach client CPU: means that the client
network cannot reach the client server and the client CPU
- Error when installing client CPU: means that the archive (or at least one of its
components) does not exist on the Call Server Master/Distributor
- Impossible to remote load a CPU over itself: means that there is an error in
the download PC IP address (same address as that of the Call Server)
- ftp: connect: Connection refused ftp: Can't connect or login to
host: means that the PC Installer software is not installed on the downloading PC
- Operating system Chorus on client xxx is not compatible: means that
both environments (Chorus and Linux) are not compatible
1.6.3.3 Traces
In the event of a malfunction while connections are correct. Create a directory named:
/tmpd/soft_install/RLOAD_TRACE. Traces are displayed on screen and recorded in
logs. Delete the directory once traces have been recorded. Contact Alcatel-Lucent support.
1.6.3.4 Log Files
As of R9.1, the download process provides log files. For each CPU, the following temporary
log files are created on the master CPU:
- /tmpd/softinstall/SoftwareUpdateStatus_<session_id>_<seq_index>
- /tmpd/rmtpgm_<seq_index>.log
- /tmpd/softinstall/Pcxrmtseq_<seq_index>
Where:
- <session_id> is the sequence index of the CPU in the order of CPU upgrades
determined by the system
1-126 ! " #$ " %&' ( "

253 of 459
) &

- <seq_index> is the numerical value to identify the session

When all updates are over, the contents of these temporary files are reproduced in the file:
/var/ftp/pcx/logs/softwareUpdateStatus_<session_id>_end. Temporary files
are deleted.
For each updated CPU, the recorded events are:
- Download status with information on the download performed:
The name of the updated CPU
The name of the downloaded software
The update status OK/NOK
Additional information such as reason for error(s)
- Switch status with information on the switch of partitions:
The name of the switched CPU
The switch type: Immediate/Relative/Absolute
The switch status OK/NOK
Additional information such as reason for error(s)
1.7 Swinst
1.7.1 Detailed description

1.7.1.1 Overview
Note:
This documentation is valid for Linux environments only.
The Facilities menu (more commonly referred to as "swinst", from the session identifier name)
is used to:
- Install or update:
OS files on the Alcatel-Lucent OmniPCX Enterprise CS from an external disk. These
files may be a complete Linux release, packages or a patch.
Binary files (constituting the telephone application).
- Duplicate a Call Server (to compensate for any failure of the main system Call Server).
- Back up and restore:
Alcatel-Lucent OmniPCX Enterprise CS data.
ACTIS files.
- Access system management.
- Perform database operations (create, translate, delete).
Two different menus may be used, according to needs:
- The "Easy" menu (covered in the documentation dealing with installation via the Wizard).
- The "Expert" menu (described below).
Call Server hard disk structure is described in the Standard Call Server installation - Overview
.
! " #$ " %&' ( "

1-127
254 of 459
Chapter 1 ) &

1.7.2 Operation
Access and Navigation
On a PC connected to the OmniPCX Call Server by V24 or IP link, open a session (log on)
using the mtcl account, then enter "swinst", before entering the required password.
-LUCENT ENTERPRISE FACILITIES
Main menu Installation FACILITIES 2.24.0
1 Easy menu
2 Expert menu
Q Exit
Your choice [1..2, Q] ?
Navigation is performed using the keyboard. The desired option is accessed by pressing the
keys shown on screen.
When swinst asks a question, there is no timer for automatic selection of the default option.
When swinst indicates that an item is selected by default, it is not necessary to enter the item.
To stop a current process (scrolling of a file list for example) press Q.
-LUCENT ENTERPRISE FACILITIES
Expert menu Installation FACILITIES 2.24.0
1 Packages installation
2 Deliveries installation
3 Cloning & duplicate operations
4 Backup & restore operations
5 OPS configuration
6 System management
7 Database tools
8 Software identity display
9 Remote download
1.7.2.1 Packages Installation

Select option 1 Packages installation.
1 Install package from server
2 Display package
3 Install Linux patch from server
4 Install Linux on inactive version from server
Option 1 Install package from server is reserved to the Alcatel-Lucent R&D and
Integration departments (as is option 3 Install Linux patch from server).
Option 2 Display package is used to check installation of a specific file.
Example:
Enter the name of the package (return for all) -> swinst
Name : swinst Relocations: (not relocateable)
Version : 2.24.0 Vendor : Alcatel-Lucent
Release : 3oxe Build Date: Wed Jan 30 07:02:39 2008
Install date: Mon Apr 28 10:22:26 2008 Build Host: csbu064
Group : Applications/System Source RPM: swinst-2.50.0-3oxe.src.rpm
Size : 805829 License: Alcatel-Lucent
Packager : xxx.xxxxxxx@col.bsf.alcatel-lucent.fr
Summary : The SoftWare INSTallation package for Alcatel-Lucent OmniPCX
Enterprise
Description : Swinst package is mainly intended for delivery installation, backup
of databases and system maintenance.
1.7.2.2 Deliveries Installation
1-128 ! " #$ " %&' ( "

255 of 459
) &

Select option 2 Deliveries installation.

Installation is on the inactive or active version as desired.
1 Install delivery from server
2 About last install deliveries operations
Select option 1 Install delivery from server, before entering the address (or name)
of the server and confirming the installation request.
Note:
For server name to be recognized, it must have been previously configured in netadmin.
Caution:
This operation may take some time.
For installation on the active version, the tool offers to "back up" the system, i.e. make a copy
of the binary files used before the installation operation. The resulting backup files can be
restored via the Restore operations menu.
Option 2 About last install deliveries operations gives details about the:
- Last installation of a dynamic patch
- Last installation of a static patch
- Last full installation delivery
1.7.2.3 Cloning & Duplicate Operations
Select option 3 Cloning & duplicate operations.
Cloning & duplicate operations menu:
1 CPU cloning
2 Partitions duplication
3 Switch on inactive version
4 Postponed switch on inactive version
1.7.2.3.1 CPU Cloning

See the Call Server duplication - Overview
1.7.2.3.2 Partitions Duplication
Select option 3 Cloning & duplicate operations, then option 2 Partitions
duplication.
Then select the desired option(s).
Note:
To duplicate all data, select option 5 Duplicate all. This operation may take some time.
1 Duplicate Linux, packages and Linux data
2 Duplicate Linux data
3 Duplicate delivery
4 Duplicate database
5 Duplicate all
Example:
! " #$ " %&' ( "

1-129
256 of 459
Chapter 1 ) &

Confirm the duplication of Linux, packages and Linux data (y/n, default y): y
Duplicating Linux and packages
Clean the second Linux version. Confirm (y/n, default is y):
Second version cleaned
(list of files)
Linux and packages are duplicated
Duplicating the network configuration
Duplicate the network configuration in the second Linux version.
Confirm (y/n, default is y):(N4G-apply):
The network configuration is duplicated
Duplicating the Linux data
Building list of files...
Deleting the old files on inactive version...
Duplicating data on inactive version...
(list of files)
The Linux data are duplicated
Duplicating the timezone
Updating timezone ...
The timezone is duplicated
Press return
1.7.2.3.3 Switching on Inactive Version

This feature allows to switch on the second partition by rebooting the CPU.
Note:
This operation can be performed with the telephone running.
Important:
When the switch has been performed, you must log on again with the swinst account before
restarting the telephone.
Select option 3 Cloning & duplicate operations, then option 3 Switch on
inactive version.
The operator must confirm the operation:
Please confirm switching on the inactive version (y/n, default y)
If no Linux has been installed on the "inactive" version, the operation stops. If a telephone
application is installed on the active and "inactive" version, the tool displays the current status
of autostart mode:
Before the switch autostart mode is :
Autostart is [not] set
The operator can duplicate this autostart mode on the "inactive" version:
Do you want to keep this autostart mode after switching (y/n, default y)
Autostart is [not] set on inactive version
When the system is running on the new version and a shutdown occurs before a specified
delay, the system can reboot on the same version or go back to the previous one:
Do you want to switch back to the previous version if system resets (y/n,
default n): y
Enter the delay (1..7 days, q to quit): 1
A final confirmation is required before the CPU reboots:
Do a version switch. Confirm (y/n, default y):
1.7.2.3.4 Postponed Switch on Inactive Version

Postponed switch menu
1-130 ! " #$ " %&' ( "

257 of 459
) &

No postponed switch has been registered

1 Set a postponed switch
2 Cancel a postponed switch
Your choice [1..2 Q]
This feature allows the operator to register a switch at an appointed time in the next 24 hours.
The operator can register a switch, check if a switch is registered or discard a registered
switch.
Note:
The Linux data and database are automatically duplicated just before the switch.
1.7.2.4 Backup and Restore Operations

Select option 4 Backup and restore operations.
Backups can be performed on the Call Server hard disk or another Call Server (network),
using the swinst account. They can also be performed via the swinst Easy menu (see the
Installation Wizard documentation) or the Archive Data menu of the Alcatel-Lucent OmniVista
4760 Network Management System application.
Note:
A backup operation performed with swinst can be processed by the Alcatel-Lucent OmniVista 4760
Network Management System application.
1 Immediate backup operations
2 Periodic backup operations
3 Restore operations
4 Format floppy disks
1.7.2.4.1 Immediate Backup Operations

Select option 1 Immediate backup operations.
1 Immediate backup on cpu disk
2 Immediate backup on network
3 Immediate backup on USB key
4 Immediate backup on floppy
5 Immediate backup on TWIN CPU floppy
6 About last backup
Option 3 is only available, as of R7.1, on CPUs where a USB port is available (CPU7-2 and
Appliance Server). This operation is not available on the USB port of CS-2 board and blade
center.
Options 4 and 5 are only available on CPUs where a floppy drive is available (CPU5, CPU6
and CPU7-2).
Immediate Backup on CPU Disk
This option performs an immediate backup of the local CPU. Backup files are saved to
/usr4/BACKUP/IMMED.
A submenu is displayed to select the data to backup.
! " #$ " %&' ( "

1-131
258 of 459
Chapter 1 ) &

ALCATEL-LUCENT ENTERPRISE
Immediate backup on network Installation FACILITIES 2.38.0
1 Backup mao, voice guides and accounting data
2 Backup mao data
3 Backup accounting data
4 Backup voice guides
5 Backup mao data for rebuild
6 Backup traffic history
7 Backup Acd config & statistic files
8 Backup 4645 data
9 Backup 4645 data without messages
10 Backup 4635 data
11 Backup Linux (Unix) site specific data
Your choices [1..11, Q] ?
One choice per line and just press "return" to end the selection
your choice ==>
Option 1 Backup mao, voice guides and accounting data triggers mao, voice
guide and accounting backup (mao, vg and acc files)
Note 1:
Dynamic voice messages are automatically backed up, the tool also offers to back up specific voice
messages (custom directory). However, generic and standard voice messages (available on the voice
guide CD-ROM) are not backed up.
Option 3 Backup accounting data, triggers an accounting data backup operation (acc
file).
Option 6 Backup traffic history, triggers a traffic analysis backup operation (obstraf
file).
Option 7 Backup Acd config & statistic data, triggers a traffic analysis backup
operation (acd file).
Option 8 Backup 4645 data, triggers a 4645 voice mail data backup operation - messages,
mailboxes and greetings (eva-msg file).
Option 9 Backup 4645 data without messages, triggers a 4645 voice mail data backup
operation - except for received messages - (eva file).
Option 11 Backup linux ( unix ) site specifics data, triggers a backup
operation of the cho-dat file (system-specific Linux data).
Note 2:
OPS file backup operations are managed from option: OPS Configuration .
Immediate Backup on Network

Select the data to backup (see: Immediate Backup on CPU Disk ).
Enter the name of the remote Call Server.
If this name is not declared in the Call Server host file, enter the IP address of the remote Call
Server.
When a "backup on network" has been saved, for any new backup of this type, the application
offers the last used address as the default setting.
Example:
Backup on network
1-132 ! " #$ " %&' ( "

259 of 459
) &

your choice ==> 3

Name of remote host (default 192.168.4.52) ->
Name of user on 192.168.4.52 (default swinst) ->
Name of remote file (full path) -> /usr4/BACKUP/save2604
your choice ==>
Starting immediate backup on network
Stopping the none process...
Backing up of obstraf files...
(list of backup files)
352+0 records in
352+0 records out
Backup completed
*******************************************************
* The backup operation for traffic history, all files
* are completed
*******************************************************
Press return
Immediate Backup on USB Key

This option allows to backup the local or a remote Alcatel-Lucent OmniPCX Enterprise CS on
an USB key.
Select the Alcatel-Lucent OmniPCX Enterprise CS to backup:
Name of host (default localname) ->
Enter the data to backup (see: Immediate Backup on CPU Disk ).

Note:
This option requests the USB drive to be enabled (see: Enable [Disable] USB Key )
Immediate Backup on Floppy Disk

This option allows an immediate backup (see Immediate Backup on CPU Disk ). Backup files
are recorded on the floppy disk.
Immediate Backup on TWIN CPU Floppy
This option allows to backup Linux data of the twin CPU. The cho-dat backup file is created.
About Last Backup
This option gives details (date, time, files saved) of the last backup performed.
1.7.2.4.2 Periodic Backup Operations
This type of backup can only be performed in "local" mode.
It is based on a calendar type mechanism (DAY, DAY-1, DAY-2, ... DAY-6, WEEK-1, WEEK-2,
WEEK-3, MONTH-1, MONTH-2).
When swinst is first installed, daily backup to the hard disk is automatically enabled at a time
set by the system. The user is informed of this by the message:
A daily backup will be executed on cpu disk at 5 hour 45 mn.
If periodic backup is programmed, the user is informed of this by the message:
A periodic backup is already registered.
Reactivating daily backup resets the calendar mechanism but previous backups are not
deleted.
Periodic backup directories are saved in directories of type /usr4/BACKUP/DAY DAY-1 etc.
The directories used to store immediate backups are in /usr4/BACKUP/IMMED.
! " #$ " %&' ( "

1-133
260 of 459
Chapter 1 ) &

Example:
Accessing periodic backups
A periodic backup is registered
1 Periodic backup on cpu disk
2 Periodic backup on USB key
3 Cancel periodic backup operation
4 List periodic operations
5 About last backup
Periodic Backup on CPU Disk

This option performs periodic backups of the local Alcatel-Lucent OmniPCX Enterprise CS on
the local disk.
Select the data to backup and the time for backup operations.
Example:
Space used on cpu disk: 3%
1 Backup mao data for rebuild and
Backup Linux (Unix) site specific data
Your choices [1..1, Q] ?
One choice per line and just press "return" to end the selection
your choice ==>1
your choice ==>
Computing the best time for the backup operation (between 0-6 AM)...
The time proposed by the system is 5 hour 45 min
Do you agree with it (y/n, default y): n
At which time do you want to execute the save operation ?
1 - Hours ( between 0-23 ) : 1
2 - Minutes ( between 0-59 ) : 0
***************************************
* Your request is registered
***************************************
Press return
Periodic Backup on USB Key

This option performs periodic backups of the local Alcatel-Lucent OmniPCX Enterprise CS on
the local USB key.
Select the data to backup and the time for backup operations (see: Periodic Backup on CPU
Disk ).
Canceling Periodic Backup
This option cancels periodic backup operation.
Example:
***************************************
* Your periodic backup is canceled
***************************************
Press return
List Periodic Backup Operations

This option displays information on periodic backups.
Example:
1-134 ! " #$ " %&' ( "

261 of 459
) &

Hour : 5 Minute : 45
Day of the month : all
Month of the year : all
Day of the week (0=Sunday) : all
executed command : /DHS3bin/soft_install/bin/bck -save 1>/dev/null 2>&1
Backup of "Linux data" performed on "cpu disk"
Backup of "MAO data only" performed on "cpu disk"
Press return
About Last Backup

This option gives details on the last backup operation (whether immediate or periodic).
Example:
**************************************************
* Last backup operation
**************************************************
For client : For CPU : oxe
backup of Linux-data
for Linux data
to LOC_ARCHIVE
data version : F1.600
in date of Wed Jun 16 15:13:54 CEST 2004
local cpu : oxe
twin cpu : unknown
Periodic backup performed on cpu disk
**************************************************
--------------------------------------------------
Pre backup operation
--------------------------------------------------
Stopping the none process...
(list of files)
Backup completed
--------------------------------------------------
Post backup operation
--------------------------------------------------
End of backup operation
--------------------------------------------------
Note:
This option can also be accessed from the previous menu.
Save Directories on USB Key

On a USB key, the backup files are organized as follows:
! " #$ " %&' ( "

1-135
262 of 459
Chapter 1 ) &

1.7.2.4.3 Restore Operations

Any restore operation is performed on the active part of the hard disk and must be performed
with the telephone shut down (see the swinst Easy menu for details on how to shut down the
telephone).
Select option 3 Restore operations.
Restore operation menu Installation FACILITIES 2.24.0
1 Restore from cpu disk
2 Restore from network
3 Restore from USB key
4 Restore from floppy
5 Restore from TWIN CPU floppy
6 Clean IMMEDIATE backups on cpu disk
7 Clean IMMEDIATE backups on USB key
8 About last restoring
Depending on the backup operations performed, select a restore operation from the network,
the floppy, the USB key or the local hard disk.
Restore from CPU Disk
The available backups are displayed.
Example 1:
1-136 ! " #$ " %&' ( "

263 of 459
) &


1 Restore from IMMEDIATE backup
2 Restore from FEB 18 backup
Select the backup to be restored from the list of dates shown.
Then select the data to be restored.
Example 2:
1 Restore mao data for rebuild
2 Restore Linux ( Unix ) site specific data
Your choice [1..2, Q] ? 2
You are going to restore linux-data from cpu disk
# For client : For CPU : oxe
# for Linux data
# in date of Wed Feb 18 05:45:12 CET 2003
# data version 13.0
Confirm your action (y/n, default y): y
Restore from Network

If a "backup on network" operation has already been performed, keep or modify the default
data offered.
If secure restore is requested by the administrator, the previous files are backed up and the
system automatically offers to clean (purge) the backup when the procedure is complete.
Name of remote host (default 192. 168.4.52) ->
Name of user on 192.168.4.52 (default swinst) ->
Name of remote file (full path) -> /usr4/BACKUP/save2604
You are going to restore obstraf from network
# For client : For CPU : oxe
# for traffic history
# in date of Mon Feb 17 11:00:05 CET 2003
# data version no-version
confirm your action (y/n, default y):
Do you wish to secure the restoration (y/n): y
Checking disk space ...
Wait the system is backing up old files ...
(list of files)
Archive of old files is created
Restoring data...
Display of the security configuration (in reversed video):
For example:
Security configuration:
[+] Aging password configured for some account.
[+] The internet accesses to the PABX are currently secured.
[+] Trusted host(s) declared on your system.
[+] TCP WRAPPER activated for configured trusted hosts.
[-] The SSH security is currently NOT set.
(list of files)
Restoration completed
End of restoring data
Do you wish to clean up the archive : get rid of old files (y/n): y
********************************************************
* The restore operation for traffic history, all files
* is completed
********************************************************
Press return
! " #$ " %&' ( "

1-137
264 of 459
Chapter 1 ) &

Restore from USB key

This operation is not available on the USB port of CS-2 board and blade center.
Select a folder.
The available folders are:
localname
hostname1
hostname2
hostname3
....
Name of folder (default localname) ->
Select the Alcatel-Lucent OmniPCX Enterprise CS to restore.
Name of host (default localname) -> hostname1
Select restore type.

Restore from USB key Installation FACILITIES 2.36.0
For hostname1
Space used on USB key: 24%
1. Restore from IMMEDIATE backup
2. Restore from NOV 17 backup
3. Restore from NOV 16 backup
Select the data to backup.
Restore from IMMEDIATE backup Installation FACILITIES 2.36.0
For hostname1
1. Restore mao, voice guides and accounting data
2. Restore Linux (UNIX) site specific data
The header of the selected archive is displayed and after confirmation, the archive is installed
on the local or remote Alcatel-Lucent OmniPCX Enterprise CS.
Clean Immediate Backups on CPU Disk
Select the data to be cleaned.
Clean IMMEDIATE backups Installation FACILITIES 2.36.0
Space used on CPU disk: 24%
1. Clean mao, voice guides and accounting data
2. Clean Linux (UNIX) site specific data
The selected data is deleted.
Note:
Periodic daily archives are never displayed because they cannot be deleted.
Clean Immediate Backups on USB Key

Select an Alcatel-Lucent OmniPCX Enterprise CS and the data to be cleaned.
Clean IMMEDIATE backups Installation FACILITIES 2.36.0
For hostname1
1. Clean mao, voice guides and accounting data
2. Clean Linux (UNIX) site specific data
The selected data is deleted.
1-138 ! " #$ " %&' ( "

265 of 459
) &

Note:
Periodic daily archives are never displayed because they cannot be deleted.
1.7.2.4.4 Format Floppy Disks

This option allows to format floppy disks used for backup operations.
This option is only available on CPUs where a floppy drive is available (CPU5, CPU6 or CPU7
board).
Note:
The floppy disk drive slot is located on the front panel of the CPU board.
1.7.2.5 OPS Configuration

This option allows to display and manage OPS files.
See the Licenses - Overview.
1.7.2.6 System Management
Select option 6 System management.
System management menu Installation FACILITIES 2.24.0
1 Date & time update
2 Autostart management
3 Shutdown powerfail delay (Current Value : 0 h 1 m )
4 Console configuration
5 UPS configuration
6 User's accounts management
7 IMAP server management
8 Enable [Disable] USB key
1.7.2.6.1 Date & Time Update

Select option 1 Date & time update.
The exact time can be obtained from a reference clock then used to synchronize all system
OmniPCXs via NTP (Network Time Protocol).
The difference between summer and winter time (when appropriate) is automatically managed
by the system depending on OmniPCX installation country.
Note:
This time change is automatically performed on the duplicated Call Server (if there is one).
The date is MAR 24, 2003 and the time is 11:21:05 (11:21:05 AM)
The timezone is Europe/Paris
1 Set date & time
2 Set timezone
3 NTP server management
Set Date and Time

Select option 1 Set date & time.
Enter the year (default is 2003) : 2002
Enter the month (01..12, default is 03) : 03
Enter the day (01..31, default is 24) : 29
Enter the hour (00..23, default is 04) : 18
Enter the minutes (00..59, default is 21) : 39
The date & time have been set on your CPU
Press return
! " #$ " %&' ( "

1-139
266 of 459
Chapter 1 ) &

Set Timezone
This option allows CCx type applications to manage calls according to the timezone of the
parties to be called. The timezone selected is saved as being that of the OmniPCX.
Select option 2 Set timezone.
timeconfig 3.0.2 - (C) 1999 Red Hat Software
Configure Timezones

Format machine time is stored in:

[*] Hardware clock set to GMT

Europe/Malta
Europe/Minsk
Europe/Monaco
Europe/Moscow
Europe/Oslo
Europe/Paris #

Ok Cancel

<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
In the above example, OmniPCX timezone is shown by the # symbol.

As shown on the screen, use the Tab and Alt keys to select another timezone. Confirm your
selection with the space bar.
Note:
The scroll arrows and alphabetic keys on the keyboard are used to navigate through the list. When
selection has been made, swinst requests confirmation.
After setting a new timezone , YOU HAVE TO REBOOT THE SYSTEM
Do you really want to set timezone to: GB (y/n, default y): n
If you make a mistake, enter n (for no) before pressing the "Return" key.
NTP server management
The NTP server allows to synchronize time with a reference clock. For more information on
NTP configuration, see: Network Time Protocol (NTP) - Configuration procedure.
1.7.2.6.2 Autostart Management
Select option 2 Autostart management.
Note:
After a shutdown or power failure, the telephone has to be started manually if "autostart" is not selected:
- either with the RUNTEL command,
- or via the swinst Easy menu (option 8, "Start the telephone").
If autostart is enabled (set to "Yes") then, in the case of a duplicated Call Server, it is also set to "Yes"
(automatically) on the Stand-by Call Server. However if set to "No" on the Main Call Server, it has to be
manually disabled on the Stand-by Call Server.
1-140 ! " #$ " %&' ( "

267 of 459
) &

Autostart is not set

1 Set autostart
2 Unset autostart
Autostart is set
1.7.2.6.3 Shutdown Powerfail Delay

Select option 3 Shutdown powerfail delay (Current value : 0h 0m).
This is the delay between mains power supply failure and the beginning of system shutdown.
This delay is used when the Call Server is hosted in:
- CS board located in an S or L rack with internal batteries
- Appliance Server connected to the UPS with a serial V24 port
Enter the hours (default is 0) : 0
Enter the minutes (default is 0) : 2
Please confirm the shutdown delay 0 h 2 m (y/n, default y): y
If you want to correct the delay, enter n (for "No") and repeat the actions.
For more information on Call Server startup and shutdown, see the Call Server stop/restart
procedure - Operation.
1.7.2.6.4 Console Configuration
Select option 4 Console configuration.
This operation allows the configuration of the console communication port. The available
options are displayed and include a "help" option to assist in the configuration.
Enter the console mode (direct,modem,ppp,ups,?)
- direct: the link between the CPU and the console is a simple V24 cable.
- modem: the console is far away from the CPU, the serial link is transmitted via a
commutated line with modem. Kernel messages are transmitted to the console.
- ppp: instead of character, the modem line, linked to the console with a modem, transmits
data packets. Kernel messages are not transmitted to the console.
- ups: the serial port is used to drive an UPS system.
- ?: provides help about the configuration.
Confirm your modification (y/n, default y):
Apply modifications immediatly ? [Yes|No]:
The new configuration can be taken into account immediately or at next reboot.
1.7.2.6.5 UPS Configuration
As of R6.1, this option allows the configuration of the UPS monitoring process.
For more information, see: Appliance Server - Detailed description - Uninterruptable Power
Supply (UPS).
Access
Select option 5 UPS configuration.
! " #$ " %&' ( "

1-141
268 of 459
Chapter 1 ) &

UPS configuration menu Installation FACILITIES 2.24.0

UPS is stopped (1)
1 Start UPS on USB
2 Start UPS on console
3 Stop UPS
4 UPS status
(1) This line gives the main UPS status: start or stop.
Start UPS on USB
This option starts a UPS monitoring process via a USB port.
The UPS device must allow USB connections. For UPS configuration, see the UPS
manufacturer documentation.
Caution:
To take into account this new configuration (port COM to port USB), reboot the Call Server and
the UPS:
1. Stop the Appliance Server
2. Stop UPS with the front panel ON/OFF button
3. Disconnect the UPS from the mains supply
4. Wait for the fan to stop
5. Connect the UPS to the mains supply
6. Restart the UPS with the front panel ON/OFF button
7. Restart the Appliance Server
Start UPS on Console
This option starts a UPS monitoring process via the console serial port (COM).
The UPS device must allow serial connections. For UPS configuration, see the UPS
manufacturer documentation.
Caution:
To take into account this new configuration (port USB to port COM), reboot the Call Server and
the UPS.
1. Stop the Appliance Server
2. Stop UPS with the front panel ON/OFF button
3. Disconnect the UPS from the mains supply
4. Wait for the fan to stop
5. Connect the UPS to the mains supply
6. Restart the UPS with the front panel ON/OFF button
7. Restart the Appliance Server
Stop UPS
This option stops the UPS monitoring process.
UPS Status
1-142 ! " #$ " %&' ( "

269 of 459
) &

This option checks the connection between the Appliance Server and UPS and details UPS
status.
Example:
battery.charge: 100 (1)
battery.runtime: 13524 (2)
battery.voltage: 2.3 (3)
driver.name: hidups (4)
driver.parameter.port: /dev/usb/hiddev0 (5)
driver.version: 2.0.0 (6)
ups.load: 14 (7)
ups. MGE UPS SYSTEMS (8)
ups.model: EXtreme (9)
ups.serial: 884E06029 (10)
ups.status: OL (11)
Press return
1. Displays batteries charge (in percentage)
2. Batteries autonomy according to batteries level and electric load (in seconds)
3. Batteries voltage (in volts)
4. Reserved for Alcatel-Lucent
11. UPS status:
OL : On Line (mains supply)
OB: On Batteries
1.7.2.6.6 User's Accounts Management
This swinst menu allows to configure user authentications.
Select option 6 User's accounts management.
This opens a sub-menu with the following options:
1 Change account password
2 Change account aging password
3 Set maximum authentication attempts
4 Configure RADIUS authentication
5 Create the 'client' account
6 Remove the 'client' account
1. This option allows to modify the password of a specified account. The following instructions
are displayed:
! " #$ " %&' ( "

1-143
270 of 459
Chapter 1 ) &

Current password check rules :

- password string must have a minimum of 8 characters (can be
lower/upper case, numeric or punctuation). This rule doesn't concern
accounts root and swinst, but nevertheless a warning is displayed.
- new password must be different from the last three.
- at least fifty percent of characters of the new password must be
different from the previous one.
Enter a username : XXXX
Changing password for XXXX
(current) UNIX password :
New UNIX password :
Retype new UNIX password :
2. This option displays the current aging password status for every account available. It
allows to modify the maximum time during which to use a password for a specified
account.
Current aging password status :
[root] 100 days / last change 0 days ago, 100 days left
[swinst] Not activated
[mtcl] - 200 days / last change 5 days ago, 195 days left
[adfexc] Not activated
[client] Not activated
Enter a username : XXXX
How many days do you want to keep validate passwords (10<X<366, 0 for no
aging)?
3. This option defines the number of authorized failed attempts when trying to login. When
the number of attempts is reached, an alarm (incident 3070) is sent to the administrator
and the account is locked for 15 seconds. The maximum number of attempts is common
for all accounts.
How many failed authentication attempts allowed for login (0<x<100, default 2)?
The default value is set to the current one.
4. This option opens the Radius configuration sub-menu:
1 View configured RADIUS servers
2 Add/Modify RADIUS server
3 Delete RADIUS server
4 View RADIUS users
5 Add/Modify RADIUS user
6 Delete RADIUS user
7 Enable/Disable RADIUS authentication
8 RADIUS authentication without local User
9 Local database authentication
10 Enable/Disable Export authentication to MGR
1. View configured RADIUS servers: displays the configuration and the status of
the previously defined Radius servers. For security reasons, the shared secret is not
displayed.
2. Add/Modify RADIUS server: allows to create or modify a Radius server. Up to 2
Radius servers can be defined to ensure redundancy in case of failure. The first
Radius server declared is called the primary Radius server, the second server is called
the secondary Radius server. The secondary Radius server is used only when the
primary Radius server is not reachable.
In order to define Radius servers, the following menus are displayed:
Enter the name or the IP address of the RADIUS server:
When a name is used, the Radius server must be declared previously in the host
database, using the netadmin tool (see: netadmin - Operation - Host Names and
Addresses).
If the defined server is already known as a Radius server, it can be modified, if not the
Radius server can be created.
Enter the destination port (default is 1812):
1-144 ! " #$ " %&' ( "

271 of 459
) &

Enter the shared secret:

Enter the timeout value in second (default is 3):
The destination port is the port number used by Radius requests sent to the Radius
server. Destination port = 1812 is the standard value.
The shared secret is shared between the Call Server and Radius server. The shared
secret acts as a key for encryption of the Radius requests. The shared secret must be
identical on the Radius server and Call Server. It must be at least 8 characters long
and not more than 64 characters.
The timeout feature checks responses to the Radius requests. When the timer
expires, the Radius server is declared not reachable.
If the server is being modified, the default value is set to the current one. The current
value of the shared secret is not displayed for security reasons. The shared secret
must be entered each time a modification is performed.
3. Delete RADIUS server : allows to delete a Radius server.
4. View RADIUS users: displays the corporate login list
Example:
Login: john Account: mtcl
Login: william Account: root
Press return
In this example, user john can open a session with mtcl rights.
5. Add/Modify RADIUS user: allows to create or modify a corporate login
Example:
Enter the RADIUS user (eg: Peter SMITH): tom
Enter the system user (root, swinst, mtcl, adfexc, client): mtcl
In this example user tom is created with mtcl rights.
User logins are recorded in the /etc/passwd file. In duplicated Call Server
configurations, this file is copied on the twin Call Server when activating the copy linux
data menu from the swinst tool.
6. Delete RADIUS user: allows to delete a corporate login
7. Enable/Disable RADIUS authentication: allows to enable or disable Radius
authentication. When trying to enable authentication, the system checks the defined
Radius server(s). In case of no answer, the Radius authentication cannot be enabled.
The following message is displayed:
WARNING: No RADIUS server configured! Cannot enable RADIUS
authentication.
8. RADIUS authentication without local User allows to authorize the login of
users not declared on the Call Server.
If the RADIUS authentication without local User option is enabled and:
There is no corresponding local user in the Call Server for this particular corporate
user, the final identity of the corporate user is mtcl
A local user is present with different a permission (UID) in the Call Server, the
session opens with the corresponding permission.
If the RADIUS authentication without local User option is disabled, all corporate
users must be declared on the Call Server using the Add/Modify RADIUS user menu
9. Local database authentication. The local database authentication is used
when no Radius server is reachable. The following submenu is displayed:
Note : If primary and secondary RADIUS servers are unreachable
for any reason, it can be allowed to the administrator to access
the system and modify the configuration if this is the origin of
the problem. Default behavior is to forbid local database
authentication.
Current configuration : Local database authentication from any
! " #$ " %&' ( "

1-145
272 of 459
Chapter 1 ) &

connection (console and IP)

1 No local database authentication
2 Local database authentication only from console port
3 Local database authentication from any connection (console and
IP)
No local database authentication: local authentication is not allowed.
Local database authentication only from console port: local authentication is
allowed on the system console only. In this case, authentication is performed
according to the security policy defined in the local database.
Local database authentication from any connection (console and IP): local
authentication is allowed for local and remote users.
10. Enable/Disable Export authentication to MGR: allows to enable or disable
the Access control to mgr feature. For more details on Access control to mgr, see :
Security - Detailed description - Access control to management.
5. This option allows to create a client account, which contains a single maintenance menu.
A password is requested.
6. This option allows to delete the client account created previously.
For more information on security, see: Security - Detailed description - User authentication
1.7.2.6.7 IMAP Server Management
Select option 7 IMAP server management.
See: IMAP service - Configuration procedure.
1.7.2.6.8 Enable [Disable] USB Key
Select Enable [Disable] USB Key when plugging and unplugging the USB key..
Proceed as follows:
1. Plug in the key
2. Enable the key
3. Use the key ...
4. Disable the key
5. Unplug the key
This is requested before a backup/restore on or from the USB key.
When the user disables the USB key, a warning is displayed if a periodic backup was
previously registered for the USB key. In this case, the periodic backup is postponed. When
the user enables the USB key again, a message is displayed and the periodic backup on the
USB key is automatically restarted.
1.7.2.7 Database Tools
Some operations on the database must be performed with the telephone shut down. If an
operation is not allowed, it is not performed and a warning message is displayed.
Select option 7 Database tools.
1.7.2.7.1 Database Translation
1-146 ! " #$ " %&' ( "

273 of 459
) &

Translation consists in making data file format comply with a new software version (release). It
is automatically performed when the Call Server reboots after a new release has been loaded.
Select option 1 Database translation.
1.7.2.7.2 Creating an Empty Database
Select option 2 Create an empty database.
This operation overwrites the existing database and the lock files. It can only be performed
with the telephone shut down.
Note:
Creation of a new database may take some time.
Restart the Call Server after this operation (and before restarting the telephone).
1.7.2.7.3 Remove Database
Note:
At installation, the existing database is automatically overwritten and replaced by the new database.
Select option 3 Remove database.

1.7.2.7.4 Acd Stat File Translation
Select option 4 Acd stat file translation.
1.7.2.8 Software Identity Display
This feature allows specific details on the operating system, software release and patch and
binary releases (versions) to be obtained. It also allows all known data on a specific
component to be viewed.
Select option 8 Software identity display.
Then select the desired option.
ALCATEL-LUCENT ENTERPRISE
Software identity display Installation FACILITIES 2.24.0
1 System release identity
2 Application software identity
3 Delivery status
4 Component status
5 System release validity checking
6 Application software validity checking
Option 1 System release identity gives the Linux version used by the system.
Option 2 Application software identity gives the telephone version used by the
system.
Option 3 Delivery status gives the version of software firmware and modules.
Option 4 Component status gives the version of a module found by performing a search
on a keyword.
Example 1:
! " #$ " %&' ( "

1-147
274 of 459
Chapter 1 ) &

Enter the component name : bios

bios_cpu5 from /twdhs3/col_int/ws/r_bios_cpu5_4.0_3BA20032ADAB01 delivered
in e2.400
bios_cpu5d from /twdhs3/col_int/ws/r_bios_cpu5_4.0_3BA20032ADAB01 delivered
in e2.400
bios_cpu6 from /twdhs3/col_int/ws/r_bios_cpu6_2.4_3BA24084AAAA04 delivered
in d1.305
bios_cpu6d from /twdhs3/col_int/ws/r_bios_cpu6_2.4_3BA24084AAAA04 delivered
in d1.305
new bios_cpu6s2 from /twdhs3/sxb_int/ws/r_bios_cpu6s2_3BA24095AAAB03_4.6
bios_cpu7 from /twdhs3/sxb_int/ws/r_bios_cpu7_3BA24115AAAA13_2.16 delivered
in f2.500
new ch_cpbios from /twdhs3/col_int/ws/r_f3.301
Press return
Option 5 System release validity checking checks package versions (no CRC
check). Some packages are only loaded on certain CPUs. The results of the command specify
which packages are not installed.
Option 6 Application software validity checking checks telephone version by
size and checksum.
Note 1:
This operation may take some time (a few minutes).
Note 2:
Although some files can be modified, neither binaries nor executables should be modified.
Example 2:
Please wait ..
Checking mode : 1=size & sum 2=size only (default is 1) 1
Checking size and sum of all files , please wait ...
file modified (authorized) : /DHS3data/afe/params.cfg checksum is not correct :
The application software is correct
Press return
1.7.2.9 Remote Download

Select option 9 Remote download.
This operation is described in the Remote download / installation - Detailed description
1-148 ! " #$ " %&' ( "

275 of 459

2.1 Overview
2.1.1 Overview
The OXE Media Services (called OXE-MS in the rest of this document) offer media processing
features that used to be provided by the GD-3 board of an OmniPCX Media Gateway. The
OXE-MS does not require any specific hardware for media processing features: it is a
fully-fledged software solution that can be deployed on any of the following:
- A server on which an OmniPCX Enterprise is running (as of R11). In this configuration, the
OXE-MS and OmniPCX Enterprise are deployed on Virtual Machines using VMware ESXi.
Figure 2.1: Configuration example using an OmniPCX Enterprise and OXE-MS on virtualized infrastructure
- An OpenTouch Business Edition server (as of R2.0). Like the other components of an
OpenTouch Business Edition (OmniPCX Enterprise and OmniVista 8770), the OXE-MS
is installed on a Virtual Machine using the Kernel-based Virtual Machine (KVM) tool.
Figure 2.2: OpenTouch Business Edition server architecture example including an OXE-MS
Note:
For more information on the OpenTouch Business Edition server architecture, refer to the
OpenTouch Business Edition document: Installation on a physical machine.
Notes:
! " #$ " %&' ( "

2-1
276 of 459
Chapter 2 # &*

- Only one instance of OXE-MS per Virtual Machine is allowed. The OXE-MS cannot operate when
other applications (such as the OmniPCX Enterprise or Alcatel-Lucent 4645 Voice Mail System) are
installed on the same Virtual Machine
- The OXE-MS runs in the Virtual Machine with its own IP address
- The OXE-MS can operate with hardware Media Gateway such as Common Media Gateway
2.1.2 Features provided

The OXE-MS provides the following main features:
- VoIP codecs (G711 and G729)
- Voice guides (Up to 30 per PCM. Max. 120)
As of R11.0, only static voice guides are supported.
As of R11.0.1 (K1.5) static and dynamic voice guides are supported.
Note:
Set linked to the OOXE-MS cannot be used to record dynamic messages
- Generation of tones
- Three-party conferences
- 6-party conference (as of R11.0.1)
- G.722 conference
- RTP payload for DTMF digits (RFC 4733 or previously called RFC 2833)
- QoS tagging (802.1p/DiffServ)
- Codec transcoding
- H.323 (only for ABC-F):
As of R11.0.1 (K1.5) , only one H.323 access is supported
As of R11.1 , two H.323 accesses are supported
Notes:
- Configurations of trunk groups and analog/TDM/IP sets are not supported.
- The OXE-MS does not support A/ law conversion.
2.1.3 G.722 conference

As of R11.1, conferences on OXE-MS can support participants connected with G.711, G.729
or G.722 coding algorithms.
When a participant with G.722 speaks, participants with G.722 receive a high quality voice
flow. Participants with G.711 or G.729 receive a lower quality voice flow.
Participants with G.711 (or G.729) speaks, other participants listen with their corresponding
algorithm. The voice quality is always G.711(G.729) .
Conditions for a G.722 conference are:
- The G722 conference with OMS system option must be set to Yes
2-2 ! " #$ " %&' ( "

277 of 459
# &*

- The participant must support G.722

- The trunk groups used by participants must support G.722
- IP domains between participants and OXE-MS must support G.722.
The conference type can be:
- An N-party conference (mastered or meet me conference)
- A 3-party conference
- A barge-in (also called intrusion)
- Voice recording through 4645 or an external SIP recorder
2.1.4 Com Server duplication

The OXE-MS supports Com Server duplication in the same subnetwork, as well as duplication
with the two Com Servers on two different subnetworks (spatial redundancy).
Example:
Two OXE-MS (OXE-MS1 and OXE-MS2) are connected to the main Com Server. When the main Com
Server activity is interrupted, the standby Com Server switches to main and the two OXE-MS are
connected to this Com Server.
Figure 2.3: Switchover between two Com Servers
Note:
In case of loss of the two Com servers, a Passive Communication Server (PCS) cannot provide
continuity of services for the OXE-MS.
2.1.5 Security
! " #$ " %&' ( "

2-3
278 of 459
Chapter 2 # &*

2.1.5.1 Binary authentication

A digital signature is introduced in the OXE-MS release production of software binaries. The
signature is verified by the Public Verification Key (PKI) when an OXE-MS software upgrade is
performed on customer location.
2.1.5.2 Signaling and voice flow encryption
IP Touch Security modules (SSM or MSM) must be used for OXE-MS signaling and voice flow
encryption. The OXE-MS uses UDP ports (2049 and 2050) to exchange messages with the IP
Touch Security module placed in front of the server.
The figure below represents a configuration with a Com Server and an OXE-MS protected by
an SSM.
Figure 2.4: OXE-MS secured by an SSM
2.2 Installation process overview
2.2.1 Manual installation

2.2.1.1 Overview
The following sections only describe the installation of an OXE-MS on a Virtual Machine using
VMware ESXi.
2-4 ! " #$ " %&' ( "

279 of 459
# &*

Figure 2.5: OXE-MS installation on virtualized infrastructure
2.2.1.2 Installation process overview

OXE-MS installation consists in:
- Installing and configuring the VMware ESXi on the physical server (see: Call Server in
Virtual Machine - Installing the VMware ESXi )
- Installing the vSphere Client on an administration computer (see: Call Server in Virtual
Machine - Installing the vSphere Client ). The vSphere Client is the configuration interface
used to create a Virtual Machine on top of the VMware ESXi
- OXE Media Services Installation - Creating a Virtual Machine for the OXE-MS
- OXE Media Services Installation - Configuring the OXE-MS on the OmniPCX Enterprise
- OXE Media Services Installation - Installing the OXE-MS on a Virtual Machine
2.2.2 Automatic installation via the ALEDS

An OXE-MS on a virtual machine using VMware ESXi can be installed automatically via the
ALEDS.
See the corresponding dedicated documentation for more information.
2.3 Installing the VMware ESXi
2.3.1 Overview

Call Server in Virtual Machine - Over-
view Call Server in Virtual Machine - In-
OXE-MS installation: stalling the vSphere Client
! " #$ " %&' ( "

2-5
280 of 459
Chapter 2 # &*


installed and configured.
See the latest vSphere documentation for more information:
2.3.2 Requirements
The installation of VMware ESXi infrastructure requires:
- A VMware ESXi 5.1 (or higher) for OXE-MS installation on Virtual Machine
- Hardware, recent enough to provide sufficient capacity:
Processors:
Memory: 4Go of physical memory is required for VMware ESXi 5.5

Before installation
Set the boot order of your server so that it boots from the CD-ROM:
1. Power on the server, insert the VMware ESXi CD, and boot from the CD
The initial boot screen is displayed
Figure 2.6: Initial boot page example

Ensure ESXi Installer is selected and press Enter .
2-6 ! " #$ " %&' ( "

281 of 459
# &*

Note 1:
If you need to change the boot order of the BIOS on the server, change the bios boot order and
reboot the machine, while booting from the CD/DVD ROM drive.
2. The installation routine proceeds.
Press Enter to install the ESXi hypervisor.
Note 2:
This may take a few minutes.
Figure 2.7: Installation welcome page example

3. Press F11 to accept the End User License Agreement.
! " #$ " %&' ( "

2-7
282 of 459
Chapter 2 # &*

Figure 2.8: End user license agreement page

4. Select the hard disk drive where you wish to install VMware ESXi to and press Enter to
continue.
Figure 2.9: Disk selection page example

Note 3:
Due to differences in hardware, and hardware configuration, the screens displayed can be different.
The example screenshots provided here were taken from a VMware ESXi instance of VMware ESXi
(ESXi installed virtually on an ESXi hypervisor).
5. Press F11 to install the ESXi hypervisor.
2-8 ! " #$ " %&' ( "

283 of 459
# &*

Note 4:
This erases the data that may be present on the drive you have selected for installation.
Figure 2.10: Installation confirmation page

ESXi installation starts on the physical hardware of the machine.
6. Remove the installation media (CD-ROM, DVD-ROM) and press Enter to reboot the server
and boot into ESXi for the first time.
! " #$ " %&' ( "

2-9
284 of 459
Chapter 2 # &*

Figure 2.12: Installation complete page example

When installation is successfully completed, the initial console screen is displayed.
This screen indicates that the VMware ESXI server 5.1.0 is installed. You can proceed with the
configuration of the VMware ESXI server 5.1.0.
2.3.4 Configuration Procedure

1. From the summary screen, Press F2 to set up the ESXi hypervisor
2-10 ! " #$ " %&' ( "

285 of 459
# &*

Figure 2.14: Summary screen example

2. Enter your Login Name and Password. The initial default login credentials are root,
without password.
Press Enter when finished.
3. Select Configure Keyboard using the arrow keys, and press Enter.
! " #$ " %&' ( "

2-11
286 of 459
Chapter 2 # &*

Select the type of keyboard from the keyboard list.

4. Select Configure Password using the arrow keys, and press Enter.
Figure 2.17: System customization page example

5. Enter your password in the New Password field and Confirm the Password field; press
Enter when finished.
2-12 ! " #$ " %&' ( "

287 of 459
# &*

6. Select Configure Management Network, and press Enter.
7. Select IP Configuration, and press Enter.
! " #$ " %&' ( "

2-13
288 of 459
Chapter 2 # &*

8. Use the arrow keys to select Set static IP address and network configuration: and
press the space bar to confirm your choice. Press the down arrow to set the IP address,
Subnet Mask, and Default Gateway fields. Press Enter when you have entered the correct
values.
Figure 2.21: IP configuration page example
2-14 ! " #$ " %&' ( "

289 of 459
# &*

Important:
Changing this address does not affect virtual machine behavior.
However, this address must.
NOT be changed without a good reason
NOT be on the same IP subnet as virtual machine traffic
9. Select DNS Configuration, and press Enter.
10. Enter your network primary DNS server, alternate DNS server, and a hostname.
Note 1:
Do not try to use the option Obtain DNS server addresses and a hostname automatically
! " #$ " %&' ( "

2-15
290 of 459
Chapter 2 # &*

Note 2:
You are not required to set a hostname, but if you already have an existing DNS infrastructure,
setting a hostname may be beneficial for future connectivity to the ESXi hypervisor.
11. The Configure Management Network screen is displayed. Press Escape to exit.
A request to Apply changes and restart the management network is displayed, press
'Y' to continue.
When you have validated the changes with Y, the VMware ESXI server 5.1.0 is configured for
your network and the server is restarted . The next step is to create a virtual machine on this
2-16 ! " #$ " %&' ( "

291 of 459
# &*

host with a vSphere client.
2.4 Installing the vSphere Client
2.4.1 Overview

stalling the OmniPCX Enterprise on Vir-
tual Machine
stalling the VMware ESXi
OXE-MS installation:
OXE Media Services Installation - Cre-
ating a Virtual Machine for the OXE-MS
installed and configured
For more information, see the vSphere documentation:
In the following example
- The IP address of the ESXi server is 172.19.32.22
- The browser is Microsoft Explorer
Note:
An internet connection is required to download the software.

1. Open a web browser and navigate to the IP address of your ESXi server.
Enter the IP address in the address bar.
2. If a security warning appears, click Continue to this website (not recommended).

Note:
The display may be different according to the web browser.
! " #$ " %&' ( "

2-17
292 of 459
Chapter 2 # &*

The welcome page is displayed.

3. Click Download vSphere Client and save the vSphere client to an appropriate location on
the hard drive.
2-18 ! " #$ " %&' ( "

293 of 459
# &*

Figure 2.28: VMware ESXi welcome page example

4. After downloading the appropriate vSphere client, browse to the directory where the
executable is saved. Double click the file name to run the installation program.
! " #$ " %&' ( "

2-19
294 of 459
Chapter 2 # &*

5. Double click the setup file
6. Select the language for your installation from the drop-down list and click OK.
2-20 ! " #$ " %&' ( "

295 of 459
# &*

7. Click Next.
The installation wizard welcome page is displayed.
8. Click Next.
The end-user patent agreement page is displayed.
! " #$ " %&' ( "

2-21
296 of 459
Chapter 2 # &*

9. Click Next.
The end-user license agreement page is displayed.
2-22 ! " #$ " %&' ( "

297 of 459
# &*

10. Select the radio button: I agree to the terms in the license agreement, and click Next.
The customer information page is displayed.
! " #$ " %&' ( "

2-23
298 of 459
Chapter 2 # &*

11. Enter a User Name and Organization and click Next.

The destination folder page is displayed.
2-24 ! " #$ " %&' ( "

299 of 459
# &*

12. Accept the default installation location and click Next.

A confirmation page is displayed.
! " #$ " %&' ( "

2-25
300 of 459
Chapter 2 # &*

13. Click Install.

The installation completed page is displayed.
2-26 ! " #$ " %&' ( "

301 of 459
# &*

14. Click Finish.
2.5 Creating a Virtual Machine for the OXE-MS
2.5.1 Overview
OXE Media Services Installation -

Configuring the OXE-MS on the Omni-
stalling the vSphere Client
PCX Enterprise
This section describes the creation of a Virtual Machine on top of the VMware ESXi installed
on the physical server.
Note:
For readability purposes, the Virtual Machine on which the OXE-MS is installed is called OXE-MS Virtual
Machine in the rest of this chapter.
2.5.2 Requirements
The installation of the OXE-MS requires:
- The VMware ESXi, installed and configured on the physical server (see: Call Server in
! " #$ " %&' ( "

2-27
302 of 459
Chapter 2 # &*

Virtual Machine - Installing the VMware ESXi )

- The vSphere Client, installed on an administration computer (see: Call Server in Virtual
Machine - Installing the vSphere Client )
2.5.3 Creating the Virtual Machine for the OXE-MS

This operation consists in creating a Virtual Machine on top of the VMware ESXi already
installed on the physical server.
1. From the administration computer, double click the VMware vSphere Client icon ( ) to
start the management console of vSphere Client
The vSphere Client can also be launched from the menu: Start > VMware.
A login page opens
Figure 2.39: Login page example

2. Complete the following fields:
IP address: enter the IP address of the server on which the VMware ESXi is installed
User name: enter your login name
Password: enter the password defined at vSphere Client installation
Note 1:
These parameters have been defined at VMware ESXi configuration (see: Call Server in Virtual
Machine - Installing the VMware ESXi - Configuration Procedure )
3. Click Login
A security warning may display
2-28 ! " #$ " %&' ( "

303 of 459
# &*

Figure 2.40: Security warning example

If this occurs, select Install this certificate and do not display any security warnings
for "x.x.x.x", and click Ignore.
Note 2:
Certificate warnings are automatically generated, unless you are working within an internal PKI
infrastructure.
The vSphere Client inventory window opens.
! " #$ " %&' ( "

2-29
304 of 459
Chapter 2 # &*

Figure 2.41: VSphere client inventory window example

4. Right click the IP address of the VMware ESXi and select New Virtual Machine
The Virtual Machine configuration window opens
2-30 ! " #$ " %&' ( "

305 of 459
# &*

Figure 2.42: Virtual Machine configuration window example

5. Select Typical and click Next
The name configuration window opens
! " #$ " %&' ( "

2-31
306 of 459
Chapter 2 # &*

Figure 2.43: Name configuration page example

6. Enter the name used to identify the Virtual Machine in the vSphere Client, and click Next
The storage configuration window opens
7. Click Next
The Operation System configuration window opens
2-32 ! " #$ " %&' ( "

307 of 459
# &*

Figure 2.44: Operation System configuration window example

8. Select Linux and Red Hat Enterprise Linux 6 (64-bit) in the Version field, then click
Next
The network connections configuration window opens
9. Click Next
The virtual disk size configuration window opens
! " #$ " %&' ( "

2-33
308 of 459
Chapter 2 # &*

Figure 2.45: Virtual disk size configuration window example

10. In the Virtual disk size field, enter 4 GB and click Next
The summary window opens
11. Select the Edit the virtual machine settings before completion check box , and click
Continue
The Virtual Machine properties window opens
2-34 ! " #$ " %&' ( "

309 of 459
# &*

Figure 2.46: Virtual Machine properties window example

12. In the Memory Size field, enter 512 MB and click Finish
The Virtual Machine for the OXE-MS is now displayed in the vSphere Client inventory
! " #$ " %&' ( "

2-35
310 of 459
Chapter 2 # &*

Figure 2.47: VSphere client inventory window example
2.6 Configuring the OXE-MS on the OmniPCX Enterprise
2.6.1 Process overview
OXE Media Services Installation - Cre- OXE Media Services Installation - In-
ating a Virtual Machine for the OXE- stalling the OXE-MS on a Virtual Ma-
MS chine
The OXE-MS configuration consists in:

- Verifying the software locks dedicated to the OXE-MS
- Declaring the OXE-MS
- Configuring the OXE-MS parameters
- Entering the Ethernet (MAC) address of the OXE-MS
2.6.2 Verifying the software locks dedicated to the OXE-MS
2-36 ! " #$ " %&' ( "

311 of 459
# &*

Two software locks are dedicated to the OXE-MS:

- 384-OXE Media Servers: this software lock controls the number of OXE-MS declared
in the OmniPCX Enterprise
- 385-VoIP channels on OMS: this software lock controls the total number of VoIP
channels (compressors) allowed for all the OXE-MS declared in the OmniPCX Enterprise
The two software locks must be greater than 0.
To display software lock states, enter the spadmin command from the OmniPCX Enterprise
prompt.
2.6.3 Declaring the OXE-MS

The OXE-MS is declared as a media gateway in the OmniPCX Enterprise (called OXE-MS
media gateway in the rest of this chapter).
OXE-MS declaration can be performed from any of the following:
- The Shelf menu. In this case, review/modify the following attributes:
Shelf Address Enter the rack address of the OXE-MS media gateway
Shelf Type Select: Media Gateway Large
OXE Media Server Select YES
Default value: NO
- The Media Gateway menu. In this case, review/modify the following attributes:
Main shelf Address Enter the rack address of the OXE-MS media gateway
Main shelf type Select: Media Gateway Large
OXE Media Server Select YES
Default value: NO)
Declaring the OXE-MS in the Shelf menu automatically creates the OXE-MS in the Media
Gateway menu and vice-versa.
Caution:
Do not declare any secondary racks and boards.
2.6.4 Configuring the OXE-MS parameters

Declaring the OXE-MS rack results in the automatic creation of a GD-3 board in the controller
position (position 0).
1. Select Shelf > Board
2. Review/modify the following attributes:
Shelf address Enter the number of the OXE-MS media gateway
Board Address Displays 0 (controller position)
! " #$ " %&' ( "

2-37
312 of 459
Chapter 2 # &*

Interface Type Displays GD3

Caution:
Do not modify this board type.
Max simultan- Enter the maximum number of simultaneous voice guides.
eous voice This value must comply with PCM rules. See note below.
guides
N-part confer- Select the type of N-party conference:
ence type Add-on (default value)
Meet-Me
No. of Com- Enter the number of compressors (VoIP channels) allowed for IP devices.
pressors for IP This number must be compatible with hardware resources.
Devices Default value: 0 (maximum value: 120)
Max. number of Enter the number of 3-party conferences allowed on the OXE-MS media
3-part confer- gateway.
ences Default value: 0 (maximum value: 40)
To take the modified value into account, the OXE-MS media gateway must
be restarted.
Max. number of Enter the maximum number of 6-party conferences
6-part confer- This value must comply with PCM rules. See note below.
ences
ences
ences
3. Confirm your entries

Note:
PCM rules:
Voice guides and n-party conferences are performed by a PCM (Pulse Code Modulation).
The OXE-MS media gateway supports 4 PCM.
Each PCM can perform:
- Up to 30 voice guides
- Up to 4 6-party conferences
A PCM does not support mixed configuration: only voice guides or only conferences of the same type.
The table below gives configuration possibilities:
Simultaneous voice Max. number of Max. number of Max. number of

guides 29-party conferences 14-party conferences 6-party conferences
<= 30 3
<= 30 2 1 or 2
2-38 ! " #$ " %&' ( "

313 of 459
# &*

Simultaneous voice Max. number of Max. number of Max. number of

guides 29-party conferences 14-party conferences 6-party conferences
<= 30 2 <= 4
<= 30 1 3 or 4
<= 30 1 1 or 2 <= 4
<= 30 1 <= 8
<= 30 5 or 6
<= 30 3 or 4 <= 4
<= 30 1 or 2 <= 8
<= 30 <= 12
31 <= x <= 60 2
31 <= x <= 60 1 1 or 2
31 <= x <= 60 1 <= 4
31 <= x <= 60 3 or 4
31 <= x <= 60 1 or 2 <= 4
31 <= x <= 60 <= 8
61 <= x <= 90 1
61 <= x <= 90 1 or 2
61 <= x <= 90 <= 4
91 <= x <= 120
In case of misconfiguration, a warning message is displayed.
2.6.5 Entering the Ethernet (MAC) address of the OXE-MS

The Ethernet (MAC) address of the OXE-MS Virtual Machine must be entered in the OXE-MS
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
OXE-MS is started.
1. Select Shelf > Board > Ethernet Parameters
Shelf address Enter the number of the OXE-MS media gateway
Board Address Enter 0 (controller position)
Interface Type Displays GD3
Board Ethernet Enter the MAC address of the OXE-MS Virtual Machine (see note below)
Address

Note:
The MAC address of the OXE-MS Virtual Machine can be retrieved from the VSphere client inventory as
follows:
! " #$ " %&' ( "

2-39
314 of 459
Chapter 2 # &*

1. Select the OXE-MS Virtual Machine and click the Edit Settings option available on the right side of
the window
This opens the Virtual Machine properties

2. Select the Hardware tab and the Network adapter 1 option
The MAC address is displayed on the right side of the window
2.6.6 G722 conference

To allow G722 conferences, the G722 conference with OMS system option must be
configured.
1. Select System > Other System Param > Compression Parameters
2-40 ! " #$ " %&' ( "

315 of 459
# &*

Option Select: G722 conference with OMS

G722 confer- No: no G722 conference allowed with OXE-MS (default value)
ence with OMS Yes: G722 conference allowed with OXE-MS
Note:
The OXE-MS must be reset for this option modification to be taken into account
2.7 Installing the OXE-MS on a Virtual Machine
2.7.1 Overview
OXE Media Services Installation - Con-

figuring the OXE-MS on the OmniPCX
Enterprise
This section describes the installation and commissioning of the OXE-MS on the Virtual
Machine.
Note:
For readability purposes, the Virtual Machine on which the OXE-MS is installed is called OXE-MS Virtual
Machine in the rest of the section.
2.7.2 Requirements
The installation of the OXE-MS requires:
- The ALEDS, deployed on an administration computer. For its deployment, ALEDS
demands:
The ALEDS software delivered as a 7-Zip self-extracting archive (for example:
ale-deployment-solution-<version>.exe). The minimum version is 3.0.1
Specific ALEDS engine network settings (free IP address, subnet mask and router of
the customer LAN)
512 MB of RAM for the ALEDS engine. This means that the administration computer
must have at least 1 GB of RAM
A VMware virtualization software which can be any of the following:
VMware player: this is a free product. The minimum version is 2.5.x
VMware workstation: this is a commercial product which must be purchased. The
minimum version is 6.5.x
These products can be downloaded from: http://www.vmware.com/download/player. In
all cases, download and launch the virtualization tool and follow the installation
instructions displayed on screen.
Caution:
To avoid the display of a warning message, if VMware player/Workstation has just been
installed on the administration computer, run it at least once to create a preferences file,
before you proceed with OXE-MS installation.
- The OXE-MS package which must include the boot DVD and OXE-MS iso files (for
example: bootdvd.<version>.iso (linux package) and oms<version>.iso)
! " #$ " %&' ( "

2-41
316 of 459
Chapter 2 # &*

2.7.3 Process overview

The installation of the OXE-MS consists in:
- Preparing the OXE-MS installation
- Installing the OXE-MS on the Virtual Machine
2.7.4 Preparing the OXE-MS installation

1. From the administration computer, launch the ALEDS interface as follows:
a. Copy the ALEDS package (ale-deployment-solution-<version>.exe) in a
dedicated directory
b. Double click the ale-deployment-solution-<version>.exe to extract the
ALEDS package
c. Double click the ale-deploy.exe file
The ALEDS interface opens
Figure 2.49: ALEDS interface example

2. From the ALEDS interface, select the Engine tab and configure the parameters of the
ALEDS engine (that is the Virtual Machine of the administration computer, used to deploy
the OXE-MS on a remote server):
VM net: If there is only one NIC (Network Interface Card) or if only one NIC is
connected, keep the default value: bridged.
IP Address: enter a free IP address for the ALEDS engine
2-42 ! " #$ " %&' ( "

317 of 459
# &*

Caution:
This IP address must be different from the computer IP address on which the ALEDS
engine runs
IP Mask: enter the subnet mask of the customer LAN
IP Gateway: enter the default IP gateway of the customer LAN
DNS Server: enter the IP address of the DNS server of the customer LAN
Host name: enter the name of the ALEDS engine (for example: pxe)
Domain Name: enter the domain name of the customer LAN
3. Select the DNS tab and configure the parameters of the OXE-MS Virtual Machine
This configuration is recommended when the deployment is performed in the customer
intranet (LAN).
Reminder:
The OXE-MS Virtual Machine must have been previously created on the physical server via the
vSphere Client (see: Call Server in Virtual Machine - Installing the vSphere Client ).
Figure 2.50: DNS configuration window example

Complete the following fields:
IP address: enter the IP address of the OXE-MS Virtual Machine
Name: enter the host name of the OXE-MS Virtual Machine
MAC address: enter the MAC address of the OXE-MS Virtual Machine
! " #$ " %&' ( "

2-43
318 of 459
Chapter 2 # &*

Note:
This MAC address can be retrieved from the VSphere client inventory as follows:
i. Select the OXE-MS Virtual Machine and click the Edit Settings option available on the right
side of the window
This opens the Virtual Machine properties
ii. Select the Hardware tab and the Network adapter 1 option
The MAC address is displayed on the right side of the window

4. Select the OXE/OMS tab and select the iso files required for OXE-MS installation
2-44 ! " #$ " %&' ( "

319 of 459
# &*

Complete the following fields:

IP address: use the drop-down menu to select the IP address of the OXE-MS Virtual
Machine
Red Hat iso: use the Browse button to select the boot dvd iso file (for example:
bootdvd.<version>.iso)
OMS iso: use the Browse button to select the OXE-MS iso file (for example:
oms-<version>.iso)
The OXE-MS is now ready to be installed on the Virtual Machine (see: Installing the OXE-MS
on the Virtual Machine ).
2.7.5 Installing the OXE-MS on the Virtual Machine

To install the OXE-MS on the Virtual Machine:
1. From the ALEDS interface, click the Start VM button to start the ALEDS engine
This operation opens a VMware player console and displays the ALEDS engine startup
! " #$ " %&' ( "

2-45
320 of 459
Chapter 2 # &*

Figure 2.53: VMware player console example

The VMware player console must display the iso files for OXE-MS installation and the
following start message:
Alcatel-Lucent ESD Deployment Server version x.x.x.x YYYYMMDD :
HHMM at <IP address of the ALEDS engine>
2. From the vSphere Client inventory, right click the OXE-MS Virtual Machine name and
select Open Console
The console of the OXE-MS Virtual Machine opens. This allows to follow the OXE-MS on
the Virtual Machine
3. Right click the OXE-MS Virtual Machine name again and select Power > Power On
After initialization, a boot menu is displayed
2-46 ! " #$ " %&' ( "

321 of 459
# &*

Figure 2.54: OXE-MS Virtual Machine console example

4. Use the down arrow key to select the OXE Mediaserver installation option and press the
Enter key
Note 1:
When the OXE Mediaserver installation option is selected, the iso files for OXE-MS installation are
displayed.
A second menu opens
! " #$ " %&' ( "

2-47
322 of 459
Chapter 2 # &*


5. Use the down arrow key to select OXE Mediaserver (OMS) option and press the Enter
key
The Red Hat installation starts, followed by the OXE-MS software installation. At the end of
process, a login window opens
6. Enter root credentials, then enter the omsconfig command
Note 2:
If this is the first installation, a password change is requested.
2-48 ! " #$ " %&' ( "

323 of 459
# &*


7. Verify that the OXE-MS version and parameters (MAC address, IP address, Netmask
and Gateway address) correspond to those defined for OXE-MS installation
8. Complete the other parameters:
The OmniPCX Enterprise IP address (menu 1. IP address)
The IP network mask (menu 2. Netmask)
The router IP address (menu 3. Gateway address)
The local OmniPCX Enterprise Call Server main IP address (menu 4. CS role
address)
The duplicated OmniPCX Enterprise Call Server main IP address in a duplicated
OmniPCX Enterprise Call Server configuration where the two OmniPCX Enterprise
Call Servers are on different IP subnetworks (menu 5. CS redundancy role
address)
The rack address of the OXE-MS Media Gateway (menu 6. Crystal number). For
more information, see: OXE Media Services Installation - Configuring the OXE-MS on
the OmniPCX Enterprise
9. Save and reboot the OXE-MS
10. On the OmniPCX Enterprise, verify the status of the OXE-MS (see: Maintenance )
2.7.6 Maintenance
On the OmniPCX Enterprise, the status of the OXE-MS can be verified using the command
! " #$ " %&' ( "

2-49
324 of 459
Chapter 2 # &*

config <number of OXE-MS crystal>

Example 1:
(1)cs80> config 10
Fri Jul 5 15:02:10 CEST 2013
+-------------------------------------------------------------------+
| Cr | cpl| cpl type | hw type | cpl state | coupler ID |
|----|----|------------|-----------|--------------|-----------------|
| 10 | 0 | GD3| OXE MS | IN SERVICE | NO PCMS CODE |
+-------------------------------------------------------------------+
--- Inter Crystal Topology ---
+-------------------------------------------------------------------------+
| CR | CPL Type Role Free/Tot Role Type CPL | CR |
|-------------------------------------------------------------------------|
|010 | 00 -GD3 (MAIN ) --- 120/120--- ( INT_A) INTIP3A - 01 |019 |
|-------------------------------------------------------------------------|
(1)cs80>
The status of the OXE-MS can also be verified using other OmniPCX Enterprise commands
such as cplstat or listerm.
You can access the OXE-MS using an SSH connection. From the prompt of OmniPCX
Enterprise, enter the following command: ssh l admin -2 <OXE-MS IP address>. A
password is asked for access: it corresponds to the password of the OmniPCX Enterprise root
account.
Example 2:
(1)cs80>ssh l admin -2 192.168.201.145
2-50 ! " #$ " %&' ( "

325 of 459
Alcatel-Lucent 4059 IP Attendant Console
User Manual
326 of 459
Legal notice:

owners.
Directives:
- 1999/5/EC (R&TTE)
327 of 459

Chapter 1
Introduction to the 4059 Attendant console
Introduction .............................................................................................. 1.1

System Architecture .............................................................................. 1.1
The 4059 IP Keyboard ........................................................................... 1.2
Switchover Key .............................................................................................. 1.3
Call Handling Keys ........................................................................................ 1.3
Audio Keys .................................................................................................... 1.4
Specific LEDs ................................................................................................ 1.4
Standard Keys Used for Call Handling .......................................................... 1.4
Attendant Set Characteristics in IP or Mixed IP Configurations
........................................................................................................................ 1.4
Set Types ...................................................................................................... 1.5
Set Audio Devices ......................................................................................... 1.5
Selection between Handset and Headset Mode ........................................... 1.5
Bluetooth Bonding Sequence ........................................................................ 1.5
Bluetooth Call Recovery Sequence ............................................................... 1.6

Audio Device Keys ........................................................................................ 1.6
Set Incompatible Features ............................................................................. 1.6
The Call Window ..................................................................................... 1.7
On-line Help ................................................................................................... 1.7
Title and Menu Bars ...................................................................................... 1.8
Information Display Field ............................................................................... 1.8
Status Bar .....................................................................................................1.11
Call Handling Fields ......................................................................................1.12

! " #

0-1
328 of 459

" $

Function Keys ...............................................................................................1.15
Date and Time ..............................................................................................1.15
Chapter 2
IP Attendant activation/deactivation
Modifying the 4059 IP Attendant ....................................................... 2.2

Deleting the 4059 IP Attendant .......................................................... 2.2
Viewing the Associated Alcatel-Lucent 8 series /
Alcatel-Lucent 9 series set ................................................................. 2.2
Modifying the Associated Alcatel-Lucent 8 series /
Alcatel-Lucent 9 series Set ................................................................. 2.3
Deleting the Associated Alcatel-Lucent 8 series /
Alcatel-Lucent 9 series Set ................................................................. 2.3
Chapter 3
Attendant console operation
Opening a Session ................................................................................. 3.1

Implementing the Console (Status) ................................................. 3.1
Methods for Calling a Number ........................................................... 3.1
Direct Dialing ................................................................................................. 3.1
Call Using the Set Directory .......................................................................... 3.1
Call Using Programmed Key ......................................................................... 3.2
Dial by Name ................................................................................................. 3.2
Call by Speed Dialing .................................................................................... 3.4
Call to an Internal User ......................................................................... 3.4
Reserving (locking) an Internal User Set (Attendant Control) ....................... 3.5
The Called Set is Free ................................................................................... 3.5
The Called Set is Busy .................................................................................. 3.5
Special Cases: Sets Forwarding or Cannot Be Reached .............................. 3.7
0-2

! " #

329 of 459

" $
External Calls ........................................................................................... 3.8

Answering Calls ...................................................................................... 3.8

Selecting the Answer Type: Automatic or Manual ......................................... 3.9

Choosing which Call to Answer First ............................................................. 3.9

Answering an Internal Call ............................................................................3.10

Answering an External Call ..........................................................................3.10

The Attendant Does not Answer Immediately ..............................................3.10
Holding a Call .........................................................................................3.11
Redial Function: Redialing a Number ............................................3.11
Consultation Call ...................................................................................3.11
Broker Call ...............................................................................................3.12
Barge-In ....................................................................................................3.12
Call Transfer (Routing) ........................................................................3.13
Selecting the Transfer Type: Automatic or Manual ......................................3.13
Manual Transfer without Presentation ..........................................................3.14
Transfer to a Call Put on Hold ......................................................................3.15
Transfer to a Meet Me Conference ..................................................3.16
Adding the First Party ...................................................................................3.16
Adding other Participants .............................................................................3.16
Adding Participants into a Conference in Progress ......................................3.16
Text Messaging ......................................................................................3.16
Chapter 4
Additional features
Overview .................................................................................................... 4.1

S Keys ........................................................................................................ 4.1
Chained Call .................................................................................................. 4.1
Charged Call .................................................................................................. 4.1
Release Ctrl ................................................................................................... 4.1
Frwrd Attnd .................................................................................................... 4.1
DTMF ............................................................................................................. 4.2

Record ........................................................................................................... 4.2

! " #

0-3
330 of 459

" $
Rotary ............................................................................................................ 4.2

Flash .............................................................................................................. 4.2
Auto Forward ................................................................................................. 4.2
Malicious ........................................................................................................ 4.2
Programmable Keys .............................................................................. 4.2
Call Presentation ........................................................................................... 4.3
Directory No Supervision ............................................................................... 4.4
Speed Dialing Number .................................................................................. 4.4
Individual Routing .......................................................................................... 4.4
Network/Network Transfer ............................................................................. 4.4

Trunk Group Supervision ............................................................................... 4.4
Out of Service Trunk Supervision .................................................................. 4.5
Individual Hold ............................................................................................... 4.5
Transfer with Privilege ................................................................................... 4.5
Chapter 5
Management from the attendant console
Secret code of the set ........................................................................... 5.1

Connection history ................................................................................ 5.1
Customizing user interface ................................................................ 5.1
Choice of Language ...................................................................................... 5.2
Ringing - melody - volume level .................................................................... 5.3
Ringing - present or absent ........................................................................... 5.3
Window appearance and display ................................................................... 5.4
Displaying the date and time ......................................................................... 5.5

Background color ........................................................................................... 5.5
Programming the individual directory ............................................ 5.5
Configuring the directories ................................................................ 5.6
Adding and configuring an external directory ................................................ 5.6
Selecting directories to use for the dial by name option ................................ 5.7
Appointment reminder ......................................................................... 5.8
Creating text messages in advance ................................................ 5.9
0-4

! " #

331 of 459

" $
Assigning programmable keys and supervision icons ........... 5.10

Programmable keys ......................................................................................5.10
Supervision icons .........................................................................................5.10
Reserving a trunk group .....................................................................5.11
Reserving trunk groups ................................................................................5.12
Trunk group auto reservation .......................................................................5.12
Direct Seize ..................................................................................................5.13
Changing the status of the attendant group sets or the entity ...
5.13
Programming the attendant group status .....................................................5.13
Programming the entity status ......................................................................5.13
Overflow between attendants (mutual aid) .................................. 5.14
Enabling overflow between attendants .........................................................5.14
Defining the overflow threshold ....................................................................5.15
Managing users .....................................................................................5.16
Metering (charging) ..............................................................................5.17
Counter .........................................................................................................5.17
Financial report .............................................................................................5.18
Monitoring users ...........................................................................................5.18
Decommissioning a defective external line ................................. 5.20
Date - Time ...............................................................................................5.21
Configuring DECT/PWT mobile (cell) phones ............................. 5.22

! " #

0-5
332 of 459

" $
0-6

! " #

333 of 459

1.1 Introduction
The 4059 IP also called SBC (Screen Based Console), is integrated into the Alcatel-Lucent
OmniPCX Enterprise Communication Server. This application provides the maximum level of
comfort and user friendliness. It is used when there is just a single attendant set for a system.
It may also form part of a team of attendants when telephone requirements mean that several
dedicated sets are necessary.
The Alcatel-Lucent 4059 IP can be set up in one of the two configurations:
- an IP configuration using the IP network, where the terminal is referred to as
Alcatel-Lucent 4059 IP and the attendant set is an Alcatel-Lucent 8 series set.
- a mixed IP configuration using the TDM and IP network, where the terminal is referred to
as Alcatel-Lucent 4059 IP and the attendant set is an Alcatel-Lucent 9 series set.
The Alcatel-Lucent 4059 IP is used to optimize call management: to reply to and easily direct
incoming calls, to manage internal calls and, if necessary, to connect internal sets to recipients
outside the system.
This console also allows the attendant to take some responsibility for system management.
The following operations, among others, are available to the attendant:
- Switching over the system from standard operation to a status configured for reduced
activity (at night, for example)
- Reserving external lines for a specific use
- Controlling the use of internal and external lines by the users
- Selecting automatic connection of calls
- Programming the date and time of the system, the checking of call costs, etc.
You are advised to read this user manual before using the console.
1.2 System Architecture

All attendants must be part of an attendant group, consisting of up to 50 attendant
sets/consoles (the maximum number of attendants in an attendant group depends on the
product software version).
The attendants within a group can use different sets/consoles, but all the terminals of the
group must be on the same node and the same IP network. An attendant terminal can only
belong to one group.
The 4059 IP application runs on a PC with one of the following operating systems:
- Microsoft Windows XP Professional SP2 (minimum)
- Windows Vista (as of release 5.1.0)
- Windows 7 (as of release 5.2.3)
The 4059 IP application environment includes a software, a specific keyboard, and an
Alcatel-Lucent 8 series or Alcatel-Lucent 9 series set.

! " #

1-1
334 of 459
Chapter 1 "% &
Figure 1.1: 4059 IP Attendant Console (IP or Mixed IP Configuration)
1.3 The 4059 IP Keyboard
1-2

! " #

335 of 459
"% &
The USB Telephonic keyboard has specific keys for call handling and other telephone
functions. With an IP or a mixed IP configuration, the loudspeaker is replaced by a cover as
the audio features are provided by the Alcatel-Lucent 8 series or Alcatel-Lucent 9 series set.
On this keyboard, all keys which are not identical to those on a standard PC keyboard are
used by the 4059 application. These keys are used for immediate call handling, even when
using another application or when the application and/or the PC are off.
A LED is associated with each keyboard key dedicated to call handling. A lit LED informs the
attendant that the corresponding key is available for any operation.
Certain standard PC keys can also be used for call handling.
1.3.1 Switchover Key
This key is also called the application switchover key. When the 4059 application
started on the PC, the key is used to switch from the 4059 window to another PC
application (and vice versa).
Note:
Ensure that in the display configuration, the 4059 activation option: By Application switch
key is selected (see Alcatel-Lucent 4059 Attendant Console - Management from the attend-
ant console - Window Appearance and Display)
1.3.2 Call Handling Keys
Opens the personal directory of the console (to configure it, see Alcatel-Lucent
4059 Attendant Console - Management from the attendant console - Programming
the Individual Directory)
Release: ends the attendant intervention on a call.
Answer an internal call.
Redial a number from the list of the last 10 outgoing calls.
Broker call.
Place on hold/transfer: places a call on hold (or transfers a call).
Cancel the consultation call: returns to the main call.
Call: calls the selected set.
Answer an external call: displays the list of incoming calls.

! " #

1-3
336 of 459
Chapter 1 "% &
External trunk: displays the list of calls routed or placed on hold.
1.3.3 Audio Keys
Note:
For IP or mixed IP configurations, the following keys activate/deactivate the audio functions on the
associated Alcatel-Lucent 8 series or Alcatel-Lucent 9 series set.
Activate/deactivate the hands-free function
Mute
Activate/deactivate the loudspeaker
Lower the volume
Raise the volume
1.3.4 Specific LEDs

Six specific LEDs provide information on the system status.
Note:
The System message LED light is not on even if the attendant receives a message.
1.3.5 Standard Keys Used for Call Handling

These keys are located on the numeric keypad of the keyboard.
0 to 9 To dial a number
# To indicate the end of dialing
- To seize a trunk on the same trunk group without having to dial
1.4 Attendant Set Characteristics in IP or Mixed IP Configurations

All the audio features of the 4059 IP attendant are provided by the Alcatel-Lucent 8 series or
Alcatel-Lucent 9 series set. Audio keys and icons are disabled on the set. The USB Telephonic
1-4

! " #

337 of 459
"% &
keyboard audio keys or corresponding 4059 application audio menu are used instead.
1.4.1 Set Types

The 4059 IP attendant set can be one the following types:
- in IP configurations: Alcatel-Lucent IP Touch 4008 Phone,Alcatel-Lucent IP Touch
4018 Phone, Alcatel-Lucent IP Touch 4028 Phone, Alcatel-Lucent IP Touch 4038 Phone,
or Alcatel-Lucent IP Touch 4068 Phone
- in mixed IP configurations: 4009, Alcatel-Lucent 4019 Digital Phone, Alcatel-Lucent 4029
Digital Phone, or Alcatel-Lucent 4039 Digital Phone
1.4.2 Set Audio Devices

1.4.2.1 Audio Devices
The following device can be used on the associated set:
- Corded Handset
- Corded Handset AND Jack Headset
- Bluetooth Handset (with associated Alcatel-Lucent IP Touch 4068 Phone only)
- Handset AND Bluetooth headset (with associated Alcatel-Lucent IP Touch 4068 Phone
only)
Note:
The bounding sequence is not available when the set is associated to 4059 IP. There is no
display/information on the bounded devices on the 4059 IP attendant application.
1.4.2.2 Icons
- There is no handset icon.
- When a headset is detected by the set, the associated set displays a headset icon (there is
no headset icon on the PC).
1.4.3 Selection between Handset and Headset Mode

When the headset is in service, the attendant is automatically in Headset mode.
Possible audio modes are:
heaset, headset and loudspeaker, hands-free, mute or not.
When the headset is out of service, the attendant is automatically in Handset mode.
Possible audio modes are:
handset, Group listening, hands-free, mute or not.
1.4.4 Bluetooth Bonding Sequence

The bounding sequence is only possible when the 4059 IP is in plugged-out state.
There is no display or information about the bound devices on the 4059 IP attendant
application.

! " #

1-5
338 of 459
Chapter 1 "% &
1.4.5 Bluetooth Call Recovery Sequence
Figure 1.4: Bluetooth Handset:
Figure 1.5: Bluetooth Headset
Caution:
The associated sets will take a few seconds (about 20 seconds, Alcatel-Lucent IP Touch
4068 Phone characteristics) before it detects the loss or retrieval of the Bluetooth link.
1.4.6 Audio Device Keys

The keys on the Bluetooth handset have no effect. The On/Off key on the handset can switch
on/off the handset.
The keys on the Bluetooth headset have no effect. The On/Off key on the headset can switch
on/off the headset.
The key located on the Jack headset has no effect on the attendant.
1.4.7 Set Incompatible Features

The 4059 IP attendant set cannot support the following features:
- Multiline (for example: boss-secretary, twin set, supervisor)
1-6

! " #

339 of 459
"% &
- ACD
- Hotel (except administrative set)
- Pickup group or hunt group
- Alarm set
- 4980 application software
- Subdevice S0 or Z
1.5 The Call Window
Note:
There may sometimes be differences in the display and the terms used:
- Depending on the country the system is in, the application may designate certain functions using a
different name.
- Depending on the configuration carried out by the system administrator, this display may show calls
on hold in a Routing calls frame.
1.5.1 On-line Help

! " #

1-7
340 of 459
Chapter 1 "% &
The Help menu in this window allows you to access:

- This user manual
- Help on interactions between the 4059 application and Assisted Telephony
- A reminder on the meaning of the USB Telephonic keyboard keys
- An About window giving the 4059 version used and the identity of the attendant
1.5.2 Title and Menu Bars

The standard Windows title bar is located at the top of the window. It gives the name of the
application and the name of the authorized user:Alcatel-Lucent 4059 IP (attendant login) .
The menu bar is found directly below the title bar. It is used to access the different functions of
the application. For example:
1.5.3 Information Display Field

The display field occupies the top part of the window. It contains two fields: the first is Busy
lamp field, the second is Programmable keys.
The windows of these fields may be re-sized and re-positioned in order to better organize the
screen (see the Alcatel-Lucent 4059 Attendant Console - Management from the attendant
console - Window Appearance and Display).
The color of the individual title bar for these two fields indicates whether they are active.
You can pass from one sub-window to the other using the mouse or using the Tab key on the
keyboard.
Within a single field, if there are too many icons or programmable keys to be displayed,
several pages are created. You can use the Page Up or Page Down keys to move between
pages.
1.5.3.1 Busy Lamp Field
To configure the supervision icons in the busy lamp field, see the Alcatel-Lucent 4059
Attendant Console - Management from the attendant console - Supervision Icons.
The supervision icons indicate the status of sets, trunks, and trunk groups. A maximum of
eight supervision icons can be displayed on a single console. To display more icons, install the
4059 BLF application.
Double-click on an icon to activate it. To find out the function and status of an icon (and display
1-8

! " #

341 of 459
"% &
a help field), point the cursor at the icon.

Equipment which is not configured in the Alcatel-Lucent OmniPCX (or located on a different
OmniPCX node to the attendant console) is represented by the icon . The meaning of the
other icons is given below.

The attendant console only supervises the equipment located on the same node as itself.
1.5.3.1.1 Digital Sets
Set free (icon green)

Set out of service (icon red)
Set inaccessible (icon yellow)
Set positioned to Do Not Disturb (icon gray)
Set busy (internal party)
Set busy (external party)
Set busy without conversation (icon yellow)
Set absent (having left an absence (apology) message)
1.5.3.1.2 Analog Sets

Set inaccessible (icon yellow)
Set positioned to Do Not Disturb (icon gray)
Set busy (with an internal party)
Set busy (with an external party)
Set off-hook
Set absent (having left an absence (apology) message)
1.5.3.1.3 Attendant sets (and consoles)

! " #

1-9
342 of 459
Chapter 1 "% &

Set busy
Set not connected
Attendant absent
1.5.3.1.4 Fax
Available (icon green)

Busy (icon yellow)
Out of service (icon red)
1.5.3.1.5 Hunt Groups

A hunt group consists of two or more sets. These sets share the same directory number so
that calls can be answered by any one of them.
Hunt group free (icon green)
Hunt group busy (icon yellow)
Hunt group partly busy (icon green at front and yellow at back).
1.5.3.1.6 Trunks
A trunk is a telephone line between two systems. It connects two Alcatel-Lucent OmniPCX or
an Alcatel-Lucent OmniPCX and another PBX.
Trunk free (icon green)
Trunk busy (icon yellow)
Trunk placed out of service for Hardware or Software (icon red).
1.5.3.1.7 Trunk Groups

A trunk group is a group of trunks of the same type, all configured identically.
Trunk group free (icon green)
Trunk group busy (icon yellow)
Trunk group partly busy (icon green at top and yellow at bottom)
Trunk group out of service for Hardware or Software (icon red)
1.5.3.2 Programmable Keys
1-10

! " #

343 of 459
"% &
Point the cursor to a programmable key to display help for this function. The status of the key
is indicated by a LED (green=active). These keys are programmed by the system administrator
or by the attendant (see the Alcatel-Lucent 4059 Attendant Console - Additional features -
Programmable Keys).
To select a function, double-click on the key or press the key directly on the USB keyboard (F1
to F8) which corresponds to the function required.
If there are more than eight functions programmed, use the Page Up or Page Down keys on
the keyboard to display the other programmable keys.
Note:
For each new page, although the keys displayed present different functions, their order corresponds to
the keys F1 to F8 on the keyboard.
1.5.4 Status Bar

This display field, which is located directly above the call handling field, is divided into several
parts:
- Call waiting counters
- Status icons
- Dialing area
1.5.4.1 Call Counters
This field indicates the number of incoming calls. Each call is represented by a colored
rectangle:
- Red: urgent calls on hold (Urgent)
- Yellow: average calls on hold (Medium)
- Green: incoming calls on hold (Normal)
Example:
1.5.4.2 Status Icons

The status of the attendant set is indicated by a row of icons in the status bar.
Example:
If the icon is grayed out, the corresponding function is not active.

Each icon has a specific meaning:
In use/activated
Attendant absent. When a console is not used and the attendant has not
replied to calls for a certain amount of time, the console automatically
changes to absent mode.
Day service

! " #

1-11
344 of 459
Chapter 1 "% &
Night service
Status of the supervision icons (activated or deactivated)
Hands-free mode
Mute deactivated - micro activated
Loudspeaker
Automatic answer
Automatic transfer
Loudspeaker volume
Rotary dialing (deactivated)
Service mode
Guide mode
1.5.4.3 Dialing Area

The dialing area only appears (in place of the status icons) for the time it takes to dial the
number.
1.5.5 Call Handling Fields

1.5.5.1 Console Idle
1-12

! " #

345 of 459
"% &
When idle, the fields displayed are:

- The field identifying the calls to be handled
- The field for routing calls or on hold calls
- The call waiting counters (see Call Counters )
1.5.5.1.1 Incoming Calls (Next Calls)
The following information is displayed for each caller:

- Caller identity (surname-first name)
- Directory number
- Entity
- If the caller is a VIP guest
Note:
The system administrator can configure a different display and unique ringing tone for calls from VIP
guests.
The VIP feature is special to hotels and hospitals.
Additional information appears when the attendant takes the call.
1.5.5.1.2 On Hold Calls
The following information is displayed for each caller:
- Caller identity (last name-first name)
- Directory number
- Entity
1.5.5.2 Active Console
The active window of the Alcatel-Lucent 4059 offers a user-friendly display of the calls in
progress.
Note:
The console is active when a call is sent or received by the attendant.
On the active console, the Next calls and Routing calls fields detail:
- The main call

! " #

1-13
346 of 459
Chapter 1 "% &
- The call on hold (information on a consultation call)
1.5.5.2.1 Main Call
This field displays:

- An icon corresponding to the call status
- The caller's last name and first name
- Entity
- If the caller is a VIP guest
- The status of the calling set
- Directory number
- Telephone facilities class of service (category)
Note:
The icon displays the status of the user set. The information displayed changes according to the call
handling.
Meaning of the icons showing the status of the set to be called:
Idle (on-hook)
Set rung
1-14

! " #

347 of 459
"% &
Set placed on hold (or transfer)
Set busy or in conversation
Wrong number (or set out of service, or access prohibited)
1.5.5.2.2 On Hold Call

This field displays information concerning an internal or external consultation call initiated by
the attendant (to transfer the main call, for example).
It gives the name, the directory number called, the class of service for the connection (to the
public network) of the set, the nature of the call and the entity to which the set belongs.
Note:
The information field for the call in progress is in color; the field for the main caller is grayed out.
1.5.6 Function Keys

There are six function keys available to the attendant. These functions, relating to call
handling, are only carried out using the keys numbered S1 to S6 (on the window or on the
USB keyboard).
The functions associated with keys S1 to S6 depend on the status of the call in progress.
The and keys on the keyboard correspond to the and keys on the screen. They
are used to move from one page to another if more than six functions are programmed.
1.5.7 Date and Time

This field, located at the bottom of the 4059 window, gives the PC date and time.
Note:
The attendant can change the date and time on their PC. They must have authorization from the system
administrator to modify them on the Alcatel-Lucent OmniPCX Enterprise CS. If there is a difference
between the time on the PC and the time on the Alcatel-Lucent OmniPCX, when starting the application,
a dialog box prompts the attendant to contact the system administrator to rectify the problem.

! " #

1-15
348 of 459
Chapter 1 "% &
1-16

! " #

349 of 459

The IP attendant features are activated only when all of the following actions are completed:
- the PC is connected to the TCP/IP network
- the 4059 IP application is running
- the attendant is activated (refer to module Alcatel-Lucent 4059 attendant console -
Introduction to the 4059 Attendant console / Call window)
Once the IP Attendant features are activated, the associated Alcatel-Lucent 8 series or
Alcatel-Lucent 9 series set is dedicated to the attendant audio features and cannot be used as
a standard set. Any call to this set is forwarded to the attendant.
When the IP Attendant features are not activated, the Alcatel-Lucent 8 series or Alcatel-Lucent
9 series set can be used as a non-attendant dedicated set and no attendant features are
available. Refer to module Alcatel-Lucent 4059 attendant console / Introduction to the 4059
Attendant console / Attendant set in IP or mixed IP configurations for the incompatible set
features.
Interactions with other features are detailed in the following table:
Feature IP attendant activated IP attendant deactivated
Message All signalization about mail is All message features that are
disabled on the set (the LED standard on the set are
is off) provided
The set retrieves mail signaliz-
ation and features
Forward Associated Alcatel-Lucent 8 Associated Alcatel-Lucent 8
series / Alcatel-Lucent 9 series / Alcatel-Lucent 9
series set is immediately for- series set is immediately for-
warded: warded:
Attendant checked-in, all the Attendant checked-out, all the
calls to Alcatel-Lucent 8 series calls to Alcatel-Lucent 8 series
/ Alcatel-Lucent 9 series set / Alcatel-Lucent 9 series follow
reach the attendant. the forward.
A set XXX is immediately for- A set XXX is immediately for-
warded to the associated Alc- warded to the associated Alc-
atel-Lucent 8 series / Alcatel- atel-Lucent 8 series / Alcatel-
Lucent 9 series set: Lucent 9 series set:
Attendant checked-in, all the Attendant checked-out, all the
calls to the XXX set reach the calls to the XXX set reach the
attendant. associated Alcatel-Lucent 8
series / Alcatel-Lucent 9
series set.
Overflow Same as Forward Same as Forward
DND Same as Forward Same as Forward
Call back - The set is protected The set is protected against
against call back call back
- The set cannot request a
call back
PRS Same as out of service set (if the attendant is plugged-in)

! " #

2-1
350 of 459
Chapter 2 %'% ( %'%
Feature IP attendant activated IP attendant deactivated

Wakeup When the attendant is unplugged, a wake up can be set on
the associated set, an icon is displayed on the set when the
wake up is programmed.
When the attendant is plugged-in with a wake-up to come, the
wake-up icon is erased.
When the attendant is unplugged again, with a wake-up to
come, the wake-up icon is displayed again.
When the wake-up occurs, there is a first try.
If the attendant is unplugged, the wake-up can occur.
If the attendant is plugged-in, the set is out of service, the
wake-up cannot occur and there will be a second try (the last
one) 2 minutes later.
Wake-up second try:
If the attendant is unplugged, the wake-up can occur.
If the second try fails, an incident is generated. This incident
reports the wake-up cannot take place. This is the common
working way of wakes-up.
Night forward The associated Alcatel-Lucent 8 series / Alcatel-Lucent 9
series set can be a night forward set
If the attendant is plugged-in, the calls to the night forward set
are diverted to the attendant.
CDT The set can be a distribution table
Prefix Cannot be dialed on the set Can be dialed
as the set keyboard is dis-
abled
Substitution - total substitution is not possible on Alcatel-Lucent 8 series
/ Alcatel-Lucent 9 series set
- partial substitution is possible
2.1 Modifying the 4059 IP Attendant

If the 4059 IP Attendant is in plug-in state
- It is forbidden to modify the Associated Set
- It is forbidden to modify the Terminal Ethernet Address
2.2 Deleting the 4059 IP Attendant

- The 4059 IP Attendant must be unplugged (with Alcatel-Lucent 8 series / Alcatel-Lucent 9
series set).
- Delete the 4059 IP Attendant termination (the Alcatel-Lucent 8 series / Alcatel-Lucent 9
series set is no longer associated with the 4059 IP).
2.3 Viewing the Associated Alcatel-Lucent 8 series /

Alcatel-Lucent 9 series set
2-2

! " #

351 of 459
%'% ( %'%
You can view the QMCDU of the 4059 IP in the data of the associated Alcatel-Lucent 8 series /
Alcatel-Lucent 9 series set but you cannot modify it.
2.4 Modifying the Associated Alcatel-Lucent 8 series /

Alcatel-Lucent 9 series Set
It is forbidden to modify the Terminal Ethernet Address if the 4059 IP attendant is plugged-in.
Every modification must follow restrictions.
2.5 Deleting the Associated Alcatel-Lucent 8 series /

Alcatel-Lucent 9 series Set
- The 4059 IP attendant must be unplugged (with Alcatel-Lucent 8 series / Alcatel-Lucent 9
series set).
- Dissociate the Alcatel-Lucent 8 series / Alcatel-Lucent 9 series set from the 4059 IP (in the
Operator configuration).
- Delete the Alcatel-Lucent 8 series / Alcatel-Lucent 9 series set termination.

! " #

2-3
352 of 459
Chapter 2 %'% ( %'%
2-4

! " #

353 of 459

3.1 Opening a Session

When the PC has been started up, you can either:
- Double-click on the Alcatel-Lucent 4059 icon on the desktop
- Click on Start > Programs > Alcatel-Lucent 4059.
3.2 Implementing the Console (Status)

When the console is first powered on, it initializes in inactive mode (unplugged position). This
is indicated on the screen by the icon (grayed out) in the status bar.
To bring the console into operation, select the Sign on option in the Attendant menu. The
console becomes active, as shown by the change in color of the icon.
Note 1:
For a full description of the icons in the status bar, see the Alcatel-Lucent 4059 Attendant Console -
Introduction to the 4059 Attendant console - Status Bar.
To use the USB keyboard and its specific keys, press the key. The red LED of the key
should be lit.
Note 2:
For a full description of the specific keys on the keyboard, see the Alcatel-Lucent 4059 Attendant
Console - Introduction to the 4059 Attendant console - The IP Keyboard.
3.3 Methods for Calling a Number
3.3.1 Direct Dialing

Dial the number directly on the numeric keypad of the keyboard.
To reach an external number, first dial the external line seize prefix, then the external number.
To set up the call: once the number has been dialed, press the key.
3.3.2 Call Using the Set Directory

The personal directory (which can be programmed from the 4059 console, see the
Alcatel-Lucent 4059 Attendant Console - Management from the attendant console -
Programming the Individual Directory) is used to select a user directly via a key, without having
to dial their number on the keyboard.
Note:
The number called may be an internal, external, or speed dialing number.

! " #

3-1
354 of 459
Chapter 3 ) "%
Calls using the personal directory can be made with the attendant set in the idle state or being
used for a consultation call.
To access the directory, press the key.
Select the name to be called and click on Redial. Press the key.
3.3.3 Call Using Programmed Key

When a key is programmed with a directory number, click on this key (or press the
corresponding F key on the keyboard, then the key).
Note:
These keys (see the Alcatel-Lucent 4059 Attendant Console - Introduction to the 4059 Attendant console
- Programmable Keys) are either programmed by the system administrator or programmed from the
console (see the Alcatel-Lucent 4059 Attendant Console - Management from the attendant console -
Programmable Keys).
3.3.4 Dial by Name

This feature allows you to call an internal (or external) user without having to dial their directory
number. Dial by name can be requested either from the idle state or during a consultation call.
When a dial by name request is made, the system carries out an internal search in the
available directories. These directories can be the personal directory for the set, the system
directory, or a standardized LDAP or ODBC directory. They are managed by the system
administrator. To determine which directories are used to dial by name, see the Alcatel-Lucent
4059 Attendant Console - Management from the attendant console - Selecting Directories to
Use for the Dial by Name Option.
3.3.4.1 Call Via the Keyboard
1. On the keyboard, type the first two letters of the name to be called.
Note:
Pressing any key on the alphabetical keyboard switches the console to Dial by name mode.
2. Enter the following letter(s).

3. The application searches for a match in all the directories selected for the search by name
(see Alcatel-Lucent 4059 Attendant Console - Management from the attendant console -
Selecting Directories to Use for the Dial by Name Option).
3-2

! " #

355 of 459
) "%
4. If the result does not correspond to the name required, enter one or more additional letters.
5. If several names appear, select the required name.
6. Click on to dial the selected number. This closes the directory search window.
To close the search window without dialing a number, click on .
7. To start dialing, press the key.
3.3.4.2 Dial by Name Using the Directories

This option is used to search by last name, by last name + first name, or by initials.
The Directory menu contains the Multi-Directory Search option, as well as a configured
directory option.
1. Select the required option in the Directory menu.
2. For a search by initials, enter the initials of the last name and first name, then click on
Initials S3 or press the S3 key on the keyboard.
For a search by last name, enter the first letters of the last name, then click Name S2 or
press the S2 key on the keyboard.
For a search by last name and first name, enter the first letters of the last name and the
first name, then click First Name S4 or press the S4 key on the keyboard.

! " #

3-3
356 of 459
Chapter 3 ) "%
To move from one field to another, use the mouse or the Tab key on the keyboard.
3. If several names appear, select the required name. If the required name does not appear,
enter one or more additional letters. The vertical arrows of the keyboard can be used to
select one of the names displayed. The right (horizontal) arrow can be used to display
additional details concerning a party (as entered in the LDAP and ODBC directories). Click
on the heading to each column to sort the users by alphabetical order or by phone number.
4. Click on (or press Enter on the keyboard) to dial the selected number. This closes the
directory search window.
To close the search window without dialing a number, click on .
5. To start dialing, press the key.
3.3.5 Call by Speed Dialing

To dial an abbreviated number, you can either:
- Dial the direct call prefix
- Dial the access prefix followed by the row of the abbreviated number
Speed dialing is most often used for external dialing only. Once the dialed number has been
analyzed by the system, the procedure is then the same as for an ordinary call.
3.4 Call to an Internal User

To call an internal user:
1. Dial the set number. The status of this set (free, busy, other) is shown in the call handling
field (see the Alcatel-Lucent 4059 Attendant Console - Introduction to the 4059 Attendant
console - Active Console).
2. If the set is free (on-hook), press the key.
Depending on the status of the set, the function keys are used to send a specific message
or to run another function on the called set (see the Alcatel-Lucent 4059 Attendant Console
3-4

! " #

357 of 459
) "%
- Introduction to the 4059 Attendant console - Function Keys).

3. To end the call, press the key.
3.4.1 Reserving (locking) an Internal User Set (Attendant Control)

When an internal user number is dialed, the user set, if free, is reserved by the attendant. The
user can no longer dial a number or access another service.
This attendant control is indicated on the user set:
- By the symbol on the resource keys (multiline set)
- By the deletion of any entry on the screen

The user set does not ring until the attendant presses the key.
This special console feature allows the called user to be reached at all times. If the user picks
up the receiver, they hear the hold music (or the corresponding tone), indicating that the set is
reserved and that all outgoing calls are denied.
3.4.2 The Called Set is Free

The call handling field displays:
- The key rings the set.
- The key releases the call.
- The Call Back function key sends a call back request to the called set (see Sending a Call
Back Request ).
- The Text Mail function key is used to send a text message to the called set (see Text
Messaging ).
3.4.3 The Called Set is Busy

3.4.3.1 The Set Is Multiline
If the user set is a multiline set, it is not locked and can make calls. However, a set resource is
used for the incoming call from the attendant set.

! " #

3-5
358 of 459
Chapter 3 ) "%
The attendant can use:

- The key to ring the set.
- The key to release the call.
The procedure to be followed after this screen is the same as the procedure described for
calling a free set.
3.4.3.2 The Set Is a Single Line Set

- The Break In function key to barge in to a conversation in progress (see Barge-In )

- The Call Back function key to activate a call back request (see Sending a Call Back
Request ).
- The Display Mail function key to display a message on the user set
- The Text Mail function key to leave a text message (see Text Messaging )
3.4.3.3 Sending a Call Back Request
When a set is busy, the attendant console can send a call back message by clicking on the
Call Back function key. The user is notified of the arrival of a message during the call (LED
flashing).
By reading this message, the user can activate the call back to the attendant. This call is
handled like a standard incoming call.
3-6

! " #

359 of 459
) "%
3.4.4 Special Cases: Sets Forwarding or Cannot Be Reached

The call handling field gives the status of the called set.
If this set cannot be reached, is out of service, or is not authorized, press the key to
release the call.

3.4.4.1 The User Is Absent (Apology Message)
When a user can leave an absent (apology) message because he or she cannot answer, the
attendant can read the message when the user is selected.
To call the set despite the user request, press the key.
3.4.4.2 The Set Is Forwarding to Another Set

3.4.4.2.1 The Set Is in Immediate Forwarding Mode
The call handling field shows the forwarding destination and the entity to which it belongs, then
the set called (set initiating the forward) and its number. It also gives the status of the set to
which the called set is forwarded:

- The key to ring the set (forwarding destination).
- The Override function key, to override the forward and call the initial set
- The Call Back function key to activate a call back request
- The Text Mail function key to leave a text message
3.4.4.2.2 The Set Is Forwarding on No Answer
The call handling field shows the set called (set initiating the forward), then the forwarding
destination and its number. It also gives the status of the set to which the called set is
forwarded:

! " #

3-7
360 of 459
Chapter 3 ) "%

- The key to ring the set.
- The Forward function key to reserve the forwarding destination

Note:
The attendant can then either ring the forwarding destination or use the Override (to return to the
initial destination) or Text Mail (to send a text message to the forwarding destination) function keys.
- The Call Back function key to activate a call back request
- The Text Mail function key to leave a text message
3.5 External Calls

Dial the trunk group seize prefix: the call handling field displays the name of the trunk group.
Then dial the number of the external party.
Once the length of the number is recognized by the system, the trunk is reserved.
Use:
- The key to send the dialing (when the length of the number is not recognized by the
system).
- The key to release the call and seize the same trunk again (to make another external
call).
3.6 Answering Calls

When a call is presented on the console, it is indicated by:
- A ringing (depending on the system configuration)
- The lighting of the LEDs on the and/or line seize keys
- The appearance of an icon in the call counters (see the Alcatel-Lucent 4059 Attendant
Console - Introduction to the 4059 Attendant console - Call Counters)
3-8

! " #

361 of 459
) "%
The call handling field gives information on the nature (or even the party) for this call (see the
Alcatel-Lucent 4059 Attendant Console - Introduction to the 4059 Attendant console - Call
Handling Fields).
To answer a call when it arrives, press the key.
To release the call, press the key.
3.6.1 Selecting the Answer Type: Automatic or Manual

This operating mode is used to automatically connect the console to any incoming call or call
on hold.
1. In the Extension menu, select the Guide mode option, or press F11 on the keyboard.
2. Double-click on Auto answer, or click on Auto answer and then press Enter on the
keyboard.
3. Select Enable to activate automatic answering of incoming calls by the console.

Select Disable to manually answer calls.
4. Select Apply to save the changes.
5. Click on Close to close the window.
3.6.2 Choosing which Call to Answer First

All incoming calls are displayed in the call handling field. When several calls are presented, it
is possible to select a specific call to answer first.

! " #

3-9
362 of 459
Chapter 3 ) "%
The call can be selected from any of the lists given in the call handling fields.
If the list cannot be seen on the screen, do one of the following:
- Press Shift and the key simultaneously to display the list of incoming calls.
- Press Shift and the key simultaneously to display the list of calls on hold.
Note:
The list of calls on hold is displayed according to the system configuration.
By default, the first call is selected. If necessary, use the Page Up and Page Down keys to
display the call to be answered as a priority.
To answer this call, double-click on it or use the keyboard as follows:
1. Select the call.
2. Press Enter, or press the key corresponding to the number of the call in the list.
3.6.3 Answering an Internal Call

Proceed as in Answering Calls .
If a call is for the attention of an attendant group (when several attendants handle calls on the
same system), the key lights up.
To answer this call, do one of the following:

- Press the key (which allows you to answer group calls as a priority).
- Press the key.
3.6.4 Answering an External Call

Proceed as in Answering Calls .
3.6.5 The Attendant Does not Answer Immediately

If the attendant does not answer immediately, the call changes to medium, then to urgent (see
the Alcatel-Lucent 4059 Attendant Console - Introduction to the 4059 Attendant console - Call
Counters).
3-10

! " #

363 of 459
) "%
The console signals this urgent call on hold by:

- A ringing on the attendant console
- Lighting up the LED of the line seize key
- Displaying Call on Hold in the next calls field

- Increasing the value on the counter
If the attendant still does not answer, they are considered by the system to be absent. The
icon is replaced by the icon on the status bar.
Incoming calls are then handled as if the console were in night mode.
To bring the console back into service, proceed as in Implementing the Console (Status) .
3.7 Holding a Call

Use the key to place a call on hold. The call counter is automatically increased. The user
hears the hold music or the corresponding tone.

If the attendant console is not in conversation and the call is not taken before the end of the
timer, ringing is activated to indicate that the call is returned. The call waiting counter changes
to Urgent.
To return to the first call placed on hold, press the key.
To return to another call placed on hold, proceed as in Choosing which Call to Answer First .
3.8 Redial Function: Redialing a Number

The Redial function is used to redial a previously dialed number.
1. In the Attendant menu, select the Redial option or press the key.
2. In the list that displays, select one of the last ten called parties.
3. Double-click on the name or click on Redial to dial the number.
3.9 Consultation Call

The consultation call is activated when a console is already involved with a first call.
Dial a number using the numeric keypad on the keyboard or use another method (see
Methods for Calling a Number ) to call a second party.
The first call is in conversation. The second call (if it is an internal call) is reserved (see
Reserving (locking) an Internal User Set (Attendant Control) ).

! " #

3-11
364 of 459
Chapter 3 ) "%
Use the following keys:

- To call the second party
- To cancel the consultation call and return to the main call
- To transfer the main call to the second call
- To release the call in progress and the reservation of the second party (if internal)
At the bottom of the screen, use the following keys:

Call Back To activate a call back request on the second party's set
Text Mail To leave a text message on the second party's set.
3.10 Broker Call

The broker call is used to move rapidly from one party to another during a consultation call.
1. Press the key. The first party is placed on hold. The second is in conversation with the
console.
2. Press the key again to place the second party on hold. The first party is in
conversation with the console.
This operation can be repeated as often as necessary.
3.11 Barge-In
Barge-in (or intrusion) allows the attendant to interrupt a conversation between two users.
After dialing, the console indicates that the user is busy.
3-12

! " #

365 of 459
) "%
At the bottom of the screen, the Break In function key is used to barge into a conversation.
Press this key, or the corresponding S key on the keyboard.
The Break In key becomes Break In. The two users are informed of the presence of the
attendant by a beep.
To end this barge-in, press the Break In key or the corresponding S key on the keyboard.
3.12 Call Transfer (Routing)

The console is in conversation with a user (internal or external user). To transfer a call to a
user, use the consultation call function (see Consultation Call ).
Note:
For an external call made by the attendant and transferred to an internal set, the charge units are
charged to the attendant console when it is the last set to be involved in the call (in the case of no answer
to a transfer, for example).
You can then either:
- Directly transfer the call (transfer without presentation)
- Orally present the call to the second user before the transfer (transfer with presentation)
3.12.1 Selecting the Transfer Type: Automatic or Manual

Automatic transfer is used to transfer a call to a free user immediately after the dialing by the
user, without the need for any further action.
2. Double-click on Auto transfer, or click on Auto transfer and then press Enter on the
keyboard.

! " #

3-13
366 of 459
Chapter 3 ) "%
3. Select Enable to activate the automatic transfer.

Select Disable to deactivate the automatic transfer.
If the console is configured to automatically transfer calls, a specific call in progress can be
transferred manually:
1. In conversation with the first party, click Auto Forward (or press the corresponding S
key on the keyboard).
2. Dial the number of the second party.
3. Trigger the dialing.
4. Present the call before pressing the key.
3.12.2 Manual Transfer without Presentation
Press the key. The two parties are in conversation and the attendant console is released.
This type of transfer can be carried out on a free or a busy set. If the set receiving the transfer
does not take the call after a certain time, this call is directed back to the attendant console.
3-14

! " #

367 of 459
) "%
3.12.3 Transfer to a Call Put on Hold

As of OmniPCX Enterprise R11.0 and release 5.3.5 of the application, a call, whether outgoing
or incoming, can be transferred to a call put on hold by the attendant.
When in conversation with a party, a Call on hold can be selected by the attendant.
If a call on hold is selected, all the operations detailed: Consultation Call are available.
Press the key to place the call back on hold.

! " #

3-15
368 of 459
Chapter 3 ) "%
Reminder:
In a standard consultation call, press this key to release the call.
This type of transfer is not available for camped-on, barged-in and reserved call on a set in the
do not disturb state.
3.13 Transfer to a Meet Me Conference

The attendant (who cannot take part in a programmed conference) can add a party if the
conference circuit is not saturated. The attendant can also reserve a conference circuit to add
different parties (up to 29) to this Meet Me conference (also called an N party conference).
During these conference transfer operations, the attendant can no longer answer internal or
external calls. However, the normal and urgent call waiting counters are updated by incoming
calls.
If an external party is alone in the conference, they are forwarded to the attendant console
after a timer. However, if another party joins the conference, this timer is canceled and the
conference begins.
3.13.1 Adding the First Party

In conversation:
1. Click the MeetMeCf button (or press the corresponding S key on the keyboard).
2. Enter the code assigned to the conference. The first participant is connected. All the time
this participant is alone, the hold music or the corresponding tone is heard.
3.13.2 Adding other Participants

With the conference circuit still reserved, dial the number of the following participant in
consultation call mode and activate this call.
When the user answers, press the CfProg key to connect them to the conference.
Repeat this operation for the following participants.
3.13.3 Adding Participants into a Conference in Progress

To add other participants into a conference in progress, proceed as in Adding the First Party .
3.14 Text Messaging

The attendant console can send text messages to all authorized internal sets equipped with an
alphanumeric keyboard.
To send a text message:
1. Dial the internal set number. The set is reserved (see Reserving (locking) an Internal User
Set (Attendant Control) ).
2. Press the Text Mail function key (or press the corresponding S key on the keyboard).
3-16

! " #

369 of 459
) "%
3. In the Type field, select System messages to send a pre-recorded message from the
Alcatel-Lucent OmniPCX, or select Attendant text-messages to send a message
programmed on the console (see the Alcatel-Lucent 4059 Attendant Console -
Management from the attendant console - Creating Text Messages in Advance).
4. Select the message to be sent, or complete the message of your choice using the
keyboard. To send a message other than a pre-programmed one, enter the message
directly in place of the displayed message.
Note:
The message should not exceed 127 characters.
5. Click on Send.
6. The Receive status field indicates whether the message has been sent correctly.

! " #

3-17
370 of 459
Chapter 3 ) "%
3-18

! " #

371 of 459

4.1 Overview
This chapter details:
- The additional functions offered on the S keys (from the window and the USB keyboard)
- The operation of the keys pre-programmed by the system administrator
4.2 S Keys
During call handling, additional functions (presented on the S keys) can be used for the
following operations:
Note:
The keys are used to change page.
4.2.1 Chained Call

Routing with chained release.
Routing with chained release allows the attendant to transfer an external call to an internal set.
The external party is rerouted to the attendant set as soon as the internal user has on-hooked.
The same call can therefore be routed to several sets in succession.
4.2.2 Charged Call

Routing with charged release.
During the routing of an external outgoing call to an internal user, the charged release
activates the call back to the attendant set when the internal set on-hooks. Answering the call
back displays the identity of the set and the number of charge units charged to this set.
4.2.3 Release Ctrl

Routing with release control.
During the routing of an external call to a busy internal set, the attendant can put the call on
hold with release control. When the internal user on-hooks, their set is not rung, but the
external call returns to the attendant set. The attendant can then route it to the called user.
4.2.4 Frwrd Attnd

Forwarding between attendants.
The attendant can forward an internal or external call to another attendant (or attendant group)
whose set is in service and available. The attendant can thus successively route the same call
to several user sets.

! " #

4-1
372 of 459
Chapter 4 %% * "
4.2.5 DTMF
Voice frequency/DTMF.
Also called transparent dialing, or overdialing (DTMF), this function is used to resend
additional dialing to the same party on the line.
4.2.6 Record
Records the current conversation.
To end recording, press the Record key again.
4.2.7 Rotary
Sends decimal rotary dialing to send a number to the current party.
4.2.8 Flash
Sends a calibrated pulse, also called cut-off or flashing.
This operation is used to activate a service for the recipient of a call (to another PCX or any
other flash-compatible communication system). This is used to:
- Send additional numbers
- Call back a service (a remote attendant, for example)
4.2.9 Auto Forward

Deletes automatic transfer for a specific call (see the Alcatel-Lucent 4059 Attendant Console -
Attendant console operation - Selecting the Transfer Type: Automatic or Manual).
4.2.10 Malicious
Malicious call (not available in the USA).
Indicates a malicious call, to the system administrator for an internal call, or to the telephone
operator for external calls.
Note:
For external calls to be indicated as malicious, you must have a subscription for this service with the
telephone operator.
4.3 Programmable Keys

The programmable keys can be programmed by the attendant (see the Alcatel-Lucent 4059
Attendant Console - Management from the attendant console - Programmable Keys). These
keys can also be pre-programmed by the system administrator.
Note:
All keys presented here do not necessarily appear on a console. Contact the system administrator for an
4-2

! " #

373 of 459
%% * "
additional configuration or further information.

To find out the function of the pre-programmed keys, right-click in the Programmable keys
window (see the Alcatel-Lucent 4059 Attendant Console - Introduction to the 4059 Attendant
console - Programmable Keys).
This dialog box is used to select a key from the list of programmable keys, to program the
associated type of element, and to give comments.
Example:
4.3.1 Call Presentation

This feature is used to assign the waiting queue operating mode. One or more traffic flows can
be associated with one or more keys. By pressing a key, the attendant takes the waiting call
with the highest priority from the traffic flow(s) served by the key.
Several presentation keys can be configured by the system administrator to present only the
following calls:
- Non DDI entities (trunk group call all entities)
- Public entities (public DDI call all entities)
- Private entities (private DDI/internal call, all entities)
- Deb DDI entities (non answered DDI call all entities)
- Internal calls (private network)
- External calls (public network)

! " #

4-3
374 of 459
Chapter 4 %% * "
- VIP
- VIP2
- Call back (attendant)
- Transfer between attendants
- Other (misc.)
- General hold
- Chained call
- Charged release
- Individual call
Key 1 is pre-programmed by default as a call presentation (Miscellaneous) key. This cannot be
modified. This allows the attendant to take the call with the highest priority from those on hold
resulting from traffic flow(s) indicating an external party (external call, call back, return from
chaining, etc.).
4.3.2 Directory No Supervision

Press the key to lock the supervised internal set.
The attendant can configure a supervision icon (see the Alcatel-Lucent 4059 Attendant
Console - Introduction to the 4059 Attendant console - Busy Lamp Field) so that this icon
shows the status of the supervised set in real time (see the Alcatel-Lucent 4059 Attendant
Console - Management from the attendant console - Supervision Icons).
4.3.3 Speed Dialing Number

Press the key to call the corresponding number.
The attendant can also configure a key with a speed dialing number.
4.3.4 Individual Routing

Individual routing allows the attendant to route an external (supervised) call without placing it in
the queue.
4.3.5 Network/Network Transfer

This feature is used to inter-connect two external parties via the system, with the possibility of
releasing the connection.
Following an incoming call, the attendant makes an outgoing call to a party and is in
conversation. Pressing the key connects the two trunks and supervision is activated.
Pressing the key again allows the attendant to barge in. Pressing the key again exits the
barge-in and restarts supervision.
4.3.6 Trunk Group Supervision

This function allows the attendant to monitor the occupation level of a trunk group. If there are
4-4

! " #

375 of 459
%% * "
still trunks free, pressing this key corresponds to an ordinary seizure without dialing of an
external trunk from this supervised trunk group.
Console - Management from the attendant console - Supervision Icons) so that this icon
shows the status of the supervised trunk group in real time.
4.3.7 Out of Service Trunk Supervision

This feature warns the attendant of a trunk malfunction (no tone on seizure). When this key is
pressed, the display shows the number of the defective termination(s).
The termination can be isolated from the trunk group (see the Alcatel-Lucent 4059 Attendant
Console - Management from the attendant console - Decommissioning a Defective External
Line).
Console - Management from the attendant console - Supervision Icons) so that this icon
shows the status of the supervised trunk group in real time.
4.3.8 Individual Hold

Individual hold puts an external outgoing or incoming party on hold on a specific circuit.
Pressing the key connects the party to this individual circuit connected to the hold music.
Several keys can be programmed for individual hold, according to the size of the system.
The party can only be retrieved from the idle state. If the attendant console switches to idle
mode, calls on hold are redistributed after a timer.
4.3.9 Transfer with Privilege

This feature lets the attendant transfer an external outgoing trunk to a user set if the
corresponding direct seize prefix is programmed on this key. The user will then dial the
external party number as a call in direct seize.

! " #

4-5
376 of 459
Chapter 4 %% * "
4-6

! " #

377 of 459

5.1 Secret code of the set

The system administrator can use a secret code to authorize, prohibit, or control access to
several facilities (including bringing the set into service: see the Alcatel-Lucent 4059 Attendant
Console - Attendant console operation - Implementing the Console (Status)).
The secret code of the console can only be modified by the system administrator.
Certain functions are only accessible after entering the code for the console. The icon
indicates the functions which require this code.
Once the attendant requests access to the facility which the administrator has set to Allowed
with Attendant Code, a window displays requesting the password.
A dialog box requests the input of the password. If it is correct, the function is automatically
activated.
Inaccessible functions are indicated by the icon.
5.2 Connection history

When the console of a PC is shared between several attendants, it may be helpful to check
the history of the latest connections.
In the Option menu, select Login history.
The window shows the PC username and the start and end dates and times of the
connections to a 4059 console session.
Click on Close to close the window.
5.3 Customizing user interface

! " #

5-1
378 of 459
Chapter 5 $ + , *", &
The console interface can be configured (and checked). In the Extension menu, select the
Guide mode option, or press F11 on the keyboard.
Example:
All modifications described here are taken into account immediately. The application does not
have to be restarted.
5.3.1 Choice of Language

The system administrator chooses the languages available for the whole system. For the
attendant to have access to a particular language, their choice must be one of the languages
programmed by the administrator.
2. Double-click on Language, or click on Language and then press Enter on the keyboard.
5-2

! " #

379 of 459
$ + , *", &
3. Select the language to use.

5.3.2 Ringing - melody - volume level

The call ringing melody on the associated Alcatel-Lucent 8 series or Alcatel-Lucent 9 series
set can be selected from 16 available melodies. Each melody has seven different volume
levels.
2. Click on Console, then double-click on Program Melody, or click on Program Melody and
then press Enter on the keyboard.
3. Select the melody to use.

4. Set the ringing level for the melody by moving the corresponding cursor.
5. To hear the reconfigured ringing, click on Test.
5.3.3 Ringing - present or absent

By default, the ringing or on the associated Alcatel-Lucent 8 series or Alcatel-Lucent 9 series
set is programmed in normal mode: ringing starts on presentation of a call on the attendant
set.
2. Click on Console, then double-click on Ringing type, or click on Ringing type and then
press Enter on the keyboard.

! " #

5-3
380 of 459
Chapter 5 $ + , *", &
3. Select the ringing type to be used.

5.3.4 Window appearance and display

- In the View menu, select Configuration...
5-4

! " #

381 of 459
$ + , *", &
This dialog box offers the following options:

- Show or hide the programmable keys
- Show or hide the busy lamp fields (supervision icons)
- Define two sizes for the busy lamp fields when the programmable keys are not displayed
- Show or hide the individual call waiting counters
- Select the 4059 activation mode when the user is in another application
- Define the priority for call seizure when entity calls and other calls are received
- Modify the layout of the different windows on the screen when the Use full resizing
options mode is selected.
Click on OK to save the changes and close the window.
5.3.5 Displaying the date and time

1. In the View menu, select Status Bar.
2. If the date and time were already displayed, they disappear. If they were not already
displayed, they appear at the bottom of the window.
5.3.6 Background color

1. In the View menu, select Background color...
2. Select a basic color or click on Define custom colors.

3. Once you have chosen the color, click on OK.
5.4 Programming the individual directory

The attendant has an individual directory which can be configured, in addition to the system

! " #

5-5
382 of 459
Chapter 5 $ + , *", &
directory and any external directories.

This directory can contain up to 3000 entries.
Note:
The individual directory is stored in the file Alcabc32/store.dat. If the console is uninstalled, it is deleted.
Save it before any new installation.
To access the console directory:
1. In the Attendant menu, select Store and Redial.
2. Enter the last names, first names, and the number of the directory entry to be stored.
3. Click on Add.
To modify the last name (or the first name or the number) of a directory entry, double-click
on it to retype it using the keyboard.
Click on Delete to delete the selected name from the individual directory.
Click on Redial to dial the number of the selected user and close the window.
Click on Close to close the window without redialing a number.
5.5 Configuring the directories
5.5.1 Adding and configuring an external directory

One or more external directories (several ODBC directories and one LDAP directory) can be
used by the attendant console.
For more information on configuring external directories, contact the system administrator.
In the Options menu, select Directory, then Directory configuration:
5-6

! " #

383 of 459
$ + , *", &
This dialog box allows you to program the different directory configuration parameters:
- Add/Remove LDAP directory...: To add, modify or remove an LDAP type directory
- Add/Remove ODBC directory...: To add, modify or remove an ODBC type directory
- Search configuration...: To modify the existing LDAP and/or ODBC directory parameters
5.5.2 Selecting directories to use for the dial by name option

This option is used to define the directories used when searching via the keyboard (see the
Alcatel-Lucent 4059 Attendant Console - Attendant console operation - Call Via the Keyboard).
In the Options menu, select Directory, then Dial by name:
Click on Dial by name...:

! " #

5-7
384 of 459
Chapter 5 $ + , *", &
Check the check boxes to include or remove the directory for a search by name.
OK Validates the selection
Cancel Cancels the selection and closes the dialog box
5.6 Appointment reminder

From the attendant console, appointment reminders can be programmed on system internal
sets.
At the specified time, the internal set is rung and a voice guide informs the user that this is an
appointment reminder.
In the Extension menu, click on Appointment reminder:
5-8

! " #

385 of 459
$ + , *", &
1. Enter the time in the format HH:mm.

The time format depends on computer configuration:
If the computer uses format hh:mm:ss AM/PM, enter hh:mm AM/PM, e.g. 01:00 PM
or 01:00:00 PM
If the computer uses format hh:mm:ss, enter hh:mm, e.g. 13:00 or 13:00:00
2. Enter the telephone number of the internal set to be called.
3. Click on Add.
If no appointment is already programmed for this user, a dialog box confirms that the
appointment has been programmed. Otherwise, a dialog box indicates that an appointment
is already programmed.
To delete an appointment programmed on the console:
1. Uncheck the Appointment reminder box.
2. Enter the number of the internal set on which the appointment is to be deleted.
3. Click on Delete.
5.7 Creating text messages in advance

The attendant can send text messages to internal users. A certain number of messages are
stored by default in the system.
To send a text message, see the Alcatel-Lucent 4059 Attendant Console - Attendant console
operation - Text Messaging.
To create specific messages in advance and send them with a single click:
1. In the Options menu, select Attendant text-messages.
2. Enter up to 127 characters for a new message.

Click on Add... to add this message to the list.
Click on Delete to delete the selected message from the list.
Click on Close to save and close the window.

! " #

5-9
386 of 459
Chapter 5 $ + , *", &
5.8 Assigning programmable keys and supervision icons
5.8.1 Programmable keys

The programmable keys (see the Alcatel-Lucent 4059 Attendant Console - Introduction to the
4059 Attendant console - Programmable Keys) are programmed by the system administrator
(see the Alcatel-Lucent 4059 Attendant Console - Additional features - Programmable Keys)
and/or by the attendant.
The keys programmed by the administrator cannot be modified from the console.
In the Option menu, click on Programmable keys (or place the cursor in the programmable
keys window, right-click, and select Configuration).
Example:
To modify the content of a programmable key:

1. Select the programmable key: a box at the bottom of the window allows you to assign a
call number to it.
2. Enter the directory number to be dialed when this key is pressed.
3. Confirm the entry by clicking on OK.
If the system directory recognizes the number, the key displays the user's name.
To exit the menu, press Cancel.
5.8.2 Supervision icons

The supervision icons can be programmed from the 4059 console (the meaning of the icons is
5-10

! " #

387 of 459
$ + , *", &
described in the Alcatel-Lucent 4059 Attendant Console - Introduction to the 4059 Attendant
console - Busy Lamp Field).
In operation other than the BLF application, up to eight icons can be programmed from the
console.
In the Option menu, click on Busy lamp field (or place the cursor in the busy lamp field
window, right-click, and select Configuration).
Example:
To create or modify the content of a supervision icon:

1. Select the icon to be created/modified: the fields at the bottom of the window are used to
configure this icon.
2. Select the type of supervision (individual station, trunk line, trunk group). Free indicates
that the icon has not yet been configured.
3. In the next field, enter the number of the object to be supervised.
The third field (optional) is used to enter additional information. This information, if entered,
displays in place of the number entered in the second field.
4. For a new icon, click on Insert. Otherwise click on OK.
To delete an existing icon, select it from the list, then click on Delete.
To exit the menu, click on Cancel.
5.9 Reserving a trunk group

The attendant console can reserve one or more (analog) trunk groups so as to always have an
outside access.
In the Extension menu, select Service mode (or press the F10 key). Then double-click on
Trunk groups.

! " #

5-11
388 of 459
Chapter 5 $ + , *", &
This option authorizes:

- The reservation of one or more trunk groups by the console (to allow the attendant to call
an outside line when nearly all the available lines are being used by internal sets)
- The automatic reservation of a trunk group (if a trunk group is out of service, then brought
back into service, the reservation remains active)
- The direct seizing of a trunk group (which prohibits the seizing of trunk groups by internal
users)
5.9.1 Reserving trunk groups

This window displays all trunk groups. Each trunk group in the list is described by:
- A reservation indicator (an icon if reserved, otherwise blank)
- The trunk group name
- An automatic reservation indicator (yes if the bundle can be auto reserved, otherwise
blank)
When the user selects a trunk group, the name of the button changes according to the
reservation status of the trunk group:
- If the button says Free, the selected trunk group is reserved.
- If the button says Reserved, the selected trunk group is free.
To release or reserve a trunk group, the attendant must select the trunk group and press the
Free or Reserved button. The change is made automatically.
5.9.2 Trunk group auto reservation

This window is used to enable or disable the automatic reservation. If enabled, the attendant
reserves all system trunk groups that have been declared as automatically reservable.
Click on Apply.
5-12

! " #

389 of 459
$ + , *", &
5.9.3 Direct Seize

This window is used to authorize or refuse public network access for all sets on the system.
Click on Apply.
5.10 Changing the status of the attendant group sets or the entity
The system administrator configures the call routings for the whole system in one of four states
(night, day, Forward1, Forward2).
The attendant console is used to change:
- The status of the attendant group to which it belongs
- The status of one or more entities in the system
In the Extension menu, select Service mode (or press the F10 key). Select Status
programming.
5.10.1 Programming the attendant group status

In the Status programming option, select Group status.
1. Select one of the available options.

2. Click on Apply.
5.10.2 Programming the entity status

In the Status programming option, select Entities status.

! " #

5-13
390 of 459
Chapter 5 $ + , *", &
1. Select the entity to be modified.

2. Select one of the available options.
Note:
The Normal option assigns the entity the same status as the attendant group.
3. Click on Apply.
5.11 Overflow between attendants (mutual aid)

The overflow between attendants function allows other attendants to handle calls when there
are too many on one console.
The 4059 console allows you to enable this function and to choose how many calls there must
be on a console before overflow to the other attendants takes place.
In the Extension menu, select Service mode (or press the F10 key). Select Traffic.
5.11.1 Enabling overflow between attendants

In the Traffic option, select Traffic state.
5-14

! " #

391 of 459
$ + , *", &
1. Select Enable to implement overflow between attendants.

Select Disable to stop overflow to other attendants.
2. Click on Apply.
5.11.2 Defining the overflow threshold

In the Traffic option, select Traffic threshold.
1. In the Overflow threshold field, enter the number of calls there must be on a console before
overflow to other attendants takes place.
2. Click on Apply.

! " #

5-15
392 of 459
Chapter 5 $ + , *", &
5.12 Managing users

Double-clicking on this function opens the following window:
1. Select the search type.

2. Enter the information to search for.
3. Click on Search.
A list of users displays.
4. Select a user.
5. Click on Select....
The name and the number of the user appear at the top right.
5-16

! " #

393 of 459
$ + , *", &
6. Click on one of the tabs to access the corresponding service.

The modifications made to each service take effect once the attendant selects a new
service or clicks on Apply.
Info: displays information on the user, their cost center, operating class of service
(category), metering (charging) parameters, etc.
DND: enables the Do Not Disturb function on the user's set.
Passwd: resets the password on the user's set.
Forward: used to program certain forwards on the user's set:
no forwarding
unconditional forwarding
forwarding on busy
forwarding on no answer
forwarding on busy and no answer
Note:
The main line forwarding and secondary line forwarding functions are only available for
multiline sets.
Enter the number of the set to which calls are to be forwarded.
To delete a forward, choose No forwarding in the list or press Reset.
Click on Apply to store the changes.
Click on Close to close the window.
5.13 Metering (charging)

Configuration of the tracking of costs is the system administrator's responsibility. On the 4059
console, the metering (charging) function is used to configure the charge counters for the
users, send a financial report, and monitor user calls.
In the Extension menu, select Service mode (or press the F10 key). Select Charging.
Note:
When the call has been transmitted via a QSIG network, the application can only display the number of
charging units, not the actual call cost.
5.13.1 Counter
The counter is used to obtain call costs per set and per system node. Since this information is
of a sensitive nature, it is advisable for the system administrator to limit access to it using a
password.
Double-click on Counter:

! " #

5-17
394 of 459
Chapter 5 $ + , *", &
1. Select the search type (by name or by number).

2. Enter the information to search for (user name or number).
3. Click on Search.
A list of users displays.
4. Select a user.
5. Click on Select....
6. Once the information is obtained, click on:
Reset to reset the counters.
Search to return to the previous screen and carry out a new search.
5.13.2 Financial report

The financial report is used to search for and classify user metering (charging) data. Since this
information is of a sensitive nature, it is advisable for the system administrator to limit access
to it using a password.
Double-click on Financial report.
In the relevant fields, enter the start and end dates of the report to be created.
Click on Print to print the report.
5.13.3 Monitoring users

This function is used to create filters to monitor costs generated by certain sets. Monitoring can
be carried out by user or by groups of users. Certain specific calls (exceeding a duration x or a
cost y) can also be monitored.
5.13.3.1 Monitoring options
Double-click on Monitoring options.
5-18

! " #

395 of 459
$ + , *", &
To put a filter in place, select:

- No user: no internal set is monitored.
- All users: all users are monitored.
- Users in list: users in the list defined by the attendant are monitored.
Then select:
- By duration: to monitor calls according to their duration.
- By cost: to monitor calls according to their cost.
- By cost and duration: to monitor calls according to their cost and duration.
- All calls: to monitor all calls.
Confirm your choices by pressing the Apply button.
5.13.3.2 Tax threshold
This function is only available if the filter defined in Monitoring options is By cost or By cost
and duration.

! " #

5-19
396 of 459
Chapter 5 $ + , *", &
1. Enter the minimum value of the cost to take into account in the reports.
2. Click on Apply.
5.13.3.3 Duration threshold
This function is only available if the filter defined in Monitoring options is By duration or By
cost and duration.
1. Enter the minimum value of the duration of calls to take into account in the metering
(charging) reports.
2. Click on Apply.
5.14 Decommissioning a defective external line

In the Extension menu, select Service mode (or press the F10 key). Select Out of service
5-20

! " #

397 of 459
$ + , *", &
trunk(s).
The list of out of service trunks displays.

The same window can be accessed via a programmable key, as long as the system
administrator has programmed it.
5.15 Date - Time

In the Extension menu, select Service mode (or press the F10 key). Select System.
1. Modify the date and time used by the Alcatel-Lucent OmniPCX.

2. Click on Apply.

! " #

5-21
398 of 459
Chapter 5 $ + , *", &
5.16 Configuring DECT/PWT mobile (cell) phones

This function is used to display and configure the users of DECT/PWT mobile (cell) phones on
the system. This function is obsolete.
5-22

! " #

399 of 459
Gigabit
Ethernet
Switches
AT-GS900/5E
AT-GS900/8E
Installation
Guide
PN 613-000551 Rev A
400 of 459
Copyright 2006 Allied Telesis, Inc.
www.alliedtelesis.com
All rights reserved. No part of this publication may be reproduced without prior written permission from Allied Telesis, Inc.
All other product names, company names, logos or other designations mentioned herein are trademarks or registered trademarks
of their respective owners.
Allied Telesis, Inc. reserves the right to make changes in specifications and other information contained in this document without
prior written notice. The information provided herein is subject to change without notice. In no event shall Allied Telesis, Inc. be
liable for any incidental, special, indirect, or consequential damages whatsoever, including but not limited to lost profits, arising
out of or related to this manual or the information contained herein, even if Allied Telesis, Inc. has been advised of, known, or
should have known, the possibility of such damages.
401 of 459
Electrical Safety and Emissions
Standards
This product meets the following standards.
U.S. Federal Communications Commission

Radiated Energy
Note: This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15
of FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency
energy and, if not installed and used in accordance with this instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case
the user will be required to correct the interference at his own expense.
Note: Modifications or changes not expressly approved of by the manufacturer or the FCC, can void your right to operate
this equipment.
Industry Canada
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numrique de la classe A est conforme la norme NMB-003 du Canada.
EMI FCC Class A, CISPR 22 Class A, EN55022 Class A, C-TICK, CE
Warning: In a domestic environment this product may cause radio interference in

which case the user may be required to take adequate measures.
Immunity EN55024
Electrical Safety UL 60950 (CULUS), EN60950 (TUV)
402 of 459
Electrical Safety and Emissions Standards
Translated Safety Statements
Important: Appendix B contains translated safety statements for installing this equipment. When
you see the , go to Appendix B for the translated safety statement in your language.
Wichtig: Anhang B enthlt bersetzte Sicherheitshinweise fr die Installation dieses Gerts. Wenn
Sie sehen, schlagen Sie in Anhang B den bersetzten Sicherheitshinweis in Ihrer Sprache nach.
Importante: El Apndice B contiene mensajes de seguridad traducidos para la instalacin de este

equipo. Cuando vea el smbolo , vaya al Apndice B para ver el mensaje de seguridad traducido
a su idioma.
Important : L'annexe B contient les instructions de scurit relatives l'installation de cet

quipement. Lorsque vous voyez le symbole , reportez-vous l'annexe B pour consulter la
traduction de ces instructions dans votre langue.
Importante: lAppendice B contiene avvisi di sicurezza tradotti per linstallazione di questa

apparecchiatura. Il simbolo , indica di consultare lAppendice B per lavviso di sicurezza nella
propria lingua.
: B
. , B
.
403 of 459
Contents
Electrical Safety and Emissions Standards ................................................................................................................... 3

Preface ............................................................................................................................................................................... 7
How This Guide is Organized .............................................................................................................................................. 7
Document Conventions ....................................................................................................................................................... 8
Contacting Allied Telesis ..................................................................................................................................................... 9
Online Support .............................................................................................................................................................9
Email and Telephone Support ......................................................................................................................................9
Returning Products.......................................................................................................................................................9
For Sales or Corporate Information ..............................................................................................................................9
Chapter 1
Product Description ....................................................................................................................................................... 10
Overview............................................................................................................................................................................ 11
Key Features ..................................................................................................................................................................... 13
Standards .......................................................................................................................................................................... 13
Hardware Feature Description........................................................................................................................................... 14
10/100Base-TX Twisted Pair Ports ............................................................................................................................14
LEDs...........................................................................................................................................................................15
DC Power Connector .................................................................................................................................................16
A Few Ethernet Switching Basics ...................................................................................................................................... 17
MAC Address Table ...................................................................................................................................................17
Duplex Mode ..............................................................................................................................................................18
Store and Forward......................................................................................................................................................18
Back Pressure and Flow Control ................................................................................................................................19
Network Topologies ........................................................................................................................................................... 20
Power Workgroup Topology .......................................................................................................................................20
Collapsed Backbone ..................................................................................................................................................21
Chapter 2
Installation ....................................................................................................................................................................... 22
Reviewing Safety Precautions ........................................................................................................................................... 23
Selecting a Site for the Switch ........................................................................................................................................... 24
Planning the Installation .................................................................................................................................................... 25
Unpacking the Switch ........................................................................................................................................................ 26
Installing the Switch on a Table or Desktop....................................................................................................................... 27
Wall-Mounting the Switch .................................................................................................................................................. 29
Cabling the Switch ............................................................................................................................................................. 31
Powering On the Switch .................................................................................................................................................... 32
Chapter 3
Troubleshooting ............................................................................................................................................................. 33
Appendix A
Technical Specifications ................................................................................................................................................ 34
Physical Specifications ...................................................................................................................................................... 34
Environmental Specifications............................................................................................................................................. 34
Power Specifications ......................................................................................................................................................... 34
Safety and Electromagnetic Emissions Certifications........................................................................................................ 35
Compliance Standards ...................................................................................................................................................... 35
RJ-45 Twisted Pair Port Connectors ................................................................................................................................. 36
404 of 459
Contents
Appendix B
Translated Safety Statements ........................................................................................................................................ 37
405 of 459
Preface
This guide contains the hardware installation instructions for the

AT-GS900/xE Gigabit Ethernet switches.
How This Guide is Organized
This guide contains the following chapters and appendices:
Chapter 1, Product Description on page 10

Chapter 2, Installation on page 22
Chapter 3, Troubleshooting on page 33
Appendix A, Technical Specifications on page 34
Appendix B, Translated Safety Statements on page 37
This preface contains the following sections:
How This Guide is Organized on page 7

Document Conventions on page 8
Contacting Allied Telesis on page 9
406 of 459
Preface
Document Conventions
This document uses the following conventions to highlight important

information:
Note
Notes provide additional information.
Warning
Warnings inform you that performing or omitting a specific action
may result in bodily injury.
Caution
Cautions inform you that performing or omitting a specific action
may result in equipment damage or loss of data.
407 of 459
AT-GS900/xE Gigabit Ethernet Switch Installation Guide
Contacting Allied Telesis
This section provides Allied Telesis contact information for technical

support as well as sales or corporate information.
Online Support You can request technical support online by accessing the Allied Telesis
Knowledge Base from the following web site:
http://www.alliedtelesis.com/support/kb.aspx. You can use the
Knowledge Base to submit questions to our technical support staff and
review answers to previously asked questions.
Email and For Technical Support via email or telephone, refer to the Allied Telesis
Telephone web site: http://www.alliedtelesis.com. Select your country from the list
displayed on the website. Then select the appropriate menu tab.
Support
Returning Products for return or repair must first be assigned a Return Materials
Products Authorization (RMA) number. A product sent to Allied Telesis without a
RMA number will be returned to the sender at the senders expense.
To obtain a RMA number, contact Allied Telesis Technical Support at our

web site: http://www.alliedtelesis.com. Select your country from the list
For Sales or You can contact Allied Telesis for sales or corporate information at our
Corporate web site: http://www.alliedtelesis.com. Select your country from the list
Information
408 of 459
Chapter 1
Product Description
This chapter contains the follows sections:
Overview on page 11
Key Features on page 13
Standards on page 13
Hardware Feature Description on page 14
A Few Ethernet Switching Basics on page 17
Network Topologies on page 20
409 of 459
Overview
The AT-GS900/xE switch is an unmanaged five- or eight-port Gigabit

Ethernet switch.
The AT-GS900/xE switch switch offers a range of features and capabilities

that can be used in a variety of network configurations and topologies,
such as:
Creating small workgroups with dedicated 10 megabits per second

(Mbps), 100 Mbps, and 1000 Mbps links to your network devices, such
as workstations, servers, printers, and routers.
Interconnecting Ethernet hubs or switches to provide a bridge between
the different workgroups of your network.
Connecting to other Ethernet switches so that they can be part of a
larger Ethernet network.
Maximizing your existing network by providing full-duplex operation
over a twisted pair port.
Figure 1 illustrates the front panel of the AT-GS900/5E switch.
1000 LINK ACT 10/100 LINK ACT FDX HDX COL
AT-GS900/5E
5 Port 10/100/1000 Mbps Ethernet Switch
POWER
1 2 3 4 5
1 2 3 4 5
1036
Figure 1. AT-GS900/5E Front Panel
Figure 2 illustrates the front panel of the AT-GS900/8E switch.
AT-GS900/8E 1000 LINK ACT 10/100 LINK ACT FDX HDX COL
POWER
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
1031
Figure 2. AT-GS900/8E Front Panel
410 of 459
Chapter 1: Product Description
Figure 3 illustrates the back panel of the AT-GS900/5E switch.
12VDC
1037
Figure 3. AT-GS900/5E Back Panel
Figure 4 illustrates the back panel of the AT-GS900/8E switch.
12VDC
1032
Figure 4. AT-GS900/8E Back Panel
The AT-GS900/5E switch features five 10/100/1000 Mbps ports with

RJ-45 connectors. The AT-GS900/8E switch features eight 10/100/1000
Mbps ports with RJ-45 connectors. Each twisted pair port has an RJ-45
connector with a maximum operating distance of 100 meters (328 feet).
The twisted pair port can operate at 10 Mbps, 100 Mbps, or 1000 Mbps,
and in half- or full-duplex mode.
The AT-GS900/xE switch can be used on a desktop, or mounted to a wall.

The switch is easy to install and does not require software configuration or
management.
411 of 459
Key Features
The AT-GS900/xE Series switch has the following key features:
Five or eight 10/100/1000 Mbps twisted pair ports with RJ-45

connectors
System and port LEDs
Auto MDI/MDI-X on all 10/100/1000 Mbps twisted pair ports
Support half- or full-duplex mode on all 10/100/1000 Mbps twisted pair
ports
Auto-Negotiation (IEEE 802.3u-compliant)
Flow control (IEEE 802.3x-compliant)
Store-and-forward packet forwarding
Storage up to 8K MAC addresses
For use on a desktop or on a wall
RoHS Compliant
Standards
IEEE 802.3 Ethernet

IEEE 802.3i 10Base-T standard
IEEE 802.3u 100Base-TX standard
IEEE 802.3ab 1000Base-T Gigabit Ethernet
IEEE 802.3z Full Duplex
IEEE 802.3x Flow Control, Symmetric and Asymmetric
412 of 459
Hardware Feature Description
The below sections describe the hardware features of the AT-GS900/xE

Gigabit Ethernet switch:
Five or eight 10/100/1000 Mbps twisted pair ports

System and port LEDs
DC power jack
10/100Base-TX The AT-GS900/xE Gigabit Ethernet switch features sixteen twisted pair
Twisted Pair ports. The features of the twisted pair ports are explained in the following
sections.
Ports
Type of Connector
All twisted pair ports feature 8-pin RJ-45 connectors. (For the port pinouts,
refer to RJ-45 Twisted Pair Port Connectors on page 36.)
Speed
The ports are 10Base-T, and 100Base-T compliant and are capable of 10
megabits per second (Mbps), 100 Mbps, and 1000 Mbps speeds. The
ports are IEEE 802.3u Auto-Negotiation compliant. With Auto-Negotiation,
the switch automatically matches the highest possible common speed
between each switch port and each end-node. For example, if an end-
node is capable of only 10 Mbps, the switch sets the port connected to the
end-node to 10 Mbps.
Duplex Mode
Each twisted pair port on the switch can operate in either half- or full-
duplex mode. The twisted pair ports are IEEE 802.3u-compliant and will
Auto-Negotiate the duplex mode setting.
Note
In order for the switch to set the duplex mode for each port correctly,
the end-nodes that you connect to the switch ports should also use
Auto-Negotiation. Otherwise, a duplex mode mismatch can occur,
affecting network performance. For further information, refer to
Duplex Mode on page 18.
413 of 459
Type of Cabling
For 10 Mbps operation, Category 3 or better 100 ohm shielded or

unshielded twisted pair cabling is required. For 100 Mbps operation,
Category 5 and Enhanced Category 5 (5E) 100 ohm shielded or
unshielded twisted pair cabling is required.
Maximum Distance
Each twisted pair port has a maximum operating distance of 100 meters
(328 feet).
Auto MDI/MDI-X
All of the twisted pair ports on the switch are auto-MDI and IEEE 802.3ab-
compatible. The ports use the auto-MDI feature to automatically configure
themselves as MDI or MDI-X when connected to an end-node.
Consequently, you can use a straight-through twisted pair cable to
connect any network device to a port.
LEDs The system and port LEDs on the front panel of the AT-GS900/xE switch
display status information. Each port has three LEDs. Table 1 describes
the system and port LEDs on the AT-GS900/xE Gigabit Ethernet switch.
Table 1. System and Port LEDs
LED State Description
POWER Green The switch is powered ON and operating

normally.
OFF The switch is not receiving power.
L/A Green The port is operating at a speed of 1000 Mbps.
Blinking The port is receiving activities at 1000 Mbps
Green speed.
Orange The port is operating at a speed of 10/100
Mbps.
Blinking The port is receiving activities at 10/100 Mbps
Orange speed.
OFF No link is established on the port.
D/C Green The port is operating in full-duplex mode.
Blinking The port is experiencing a collision in half-
Green duplex mode.
OFF The port is operating in half-duplex mode.
414 of 459
DC Power The AT-GS900/xE Gigabit Ethernet switch has a single DC power jack on
Connector the back panel. Refer to Appendix A, Technical Specifications on
page 34, for the input voltage specifications.
To power ON or OFF the switch, you connect or disconnect the power

adapter.
415 of 459
A Few Ethernet Switching Basics
An Ethernet switch interconnects network devices, such as workstations,

printers, routers, and other Ethernet switches, so that they can
communicate with each other by sending and receiving Ethernet frames.
MAC Address Every hardware device on your network has a unique MAC address. This
Table address is assigned to the device by the devices manufacturer. For
example, when you install a Network Interface Card (NIC) in a computer
so that you can connect it to the network, the NIC already has a MAC
address assigned to it by its manufacturer.
The MAC address table in the AT-GS900/xE switches can store up to 8K

MAC addresses. The switch uses the table to store the MAC addresses of
the network end nodes connected to the ports, along with the port number
on which each address was learned.
A switch learns the MAC addresses of the end nodes by examining the
source address of each packet received on a port. It adds the address and
port on which the packet was received to the MAC table if the address had
not already been entered in the table. The result is a table that contains all
the MAC addresses of the devices that are connected to the switchs
ports, and the port number where each address was learned.
When the switch receives a packet, it also examines the destination

address and, by referring to its MAC address table, determines the port on
which the destination end node is connected. It then forwards the packet
to the appropriate port and on to the end node. This increases network
bandwidth by limiting each frame to the appropriate port when the
intended end node is located, freeing the other switch ports for receiving
and transmitting data.
If the switch receives a packet with a destination address that is not in the
MAC address table, it floods the packet to all the ports on the switch. If the
ports have been grouped into virtual LANs, the switch floods the packet
only to those ports which belong to the same VLAN as the port on which
the packet was received. This prevents packets from being forwarded into
inappropriate LAN segments, decreasing network security. When the
destination end node responds, the switch adds its MAC address and port
number to the table.
If the switch receives a packet with a destination address that is on the

same port on which the packet was received, it discards the packet without
forwarding it on to any port. Since both the source end node and the
destination end node for the packet are located on the same port on the
switch, there is no reason for the switch to forward the packet.
416 of 459
Duplex Mode Duplex mode refers to how an end node receives and transmits data. If an
end node can receive or transmit data, but not both simultaneously, the
end node is operating in what is referred to as half-duplex mode. If an end
node can both receive and transmit data simultaneously, the end node is
said to be operating in full-duplex mode. Naturally, an end node capable of
operating in full-duplex can handle data much faster than an end node that
can only operate in half-duplex mode.
The twisted pair ports on the AT-GS900/xE switches can operate in either
half-or full-duplex mode. They are IEEE 802.3u-compliant and use Auto-
Negotiation to set the duplex mode setting for you automatically.
For Auto-Negotiation to operate properly on a switch, the end nodes

connected to the switch should also use Auto-Negotiation. If an end node
does not have this feature and has a fixed duplex mode of full-duplex, the
result will be a duplex mode mismatch between the end node and a switch
port. A port on the Gigabit Ethernet switch connected to an end node with
a fixed duplex mode of full-duplex will operate at only half-duplex. This
results in the end node using full-duplex and the switch port using half-
duplex. This can produce network performance problems. Should you
encounter this situation, you must configure the port on the end node to
use Auto-Negotiation or, if it lacks that feature, to half-duplex.
Note
Since the ports on the AT-GS900/xE switches operate in Auto-
Negotiate mode only, the end nodes connected to the AT-GS900/5E
or AT-GS900/8E switch must also be configured to operate in the
Auto-Negotiate mode. If an end node is configured to a specific
duplex in a manual mode, it will not respond to the Auto-Negotiate
protocol from the AT-GS900/5E or AT-GS900/8E switch. (The
speed is determined from the link pulses, however, so the speed is
always detected correctly.) As a result, the port setting on the
AT-GS900/5E or AT-GS900/8E switch will end up at half-duplex. If
the end node is manually configured to full-duplex, there will be a
duplex mismatch and data will be lost. If the end node is manually
configured to half-duplex, both ports will have the speed and duplex
match up correctly.
Store and The AT-GS900/xE switches use store and forward as the method for
Forward receiving and transmitting frames. When a Ethernet frame is received on a
switch port, the switch does not retransmit the frame out the destination
port until it has received the entire frame and stored the frame in a port
buffer. It then examines the frame to determine if it is a valid frame. Invalid
frames, such as fragments or runts, are discarded by the switch. This
insures that only valid frames are transmitted out the switch ports and that
damaged frames are not propagated on your network.
417 of 459
Back Pressure To maintain the orderly movement of data between the end nodes, an
and Flow Control Ethernet switch may periodically need to signal an end node to stop
sending data. This can occur under several circumstances. For example, if
two end nodes are operating at different speeds, the switch, while
transferring data between the end nodes, might need to instruct the faster
end node to stop transmitting data to allow the slower end node to catch
up. An example of this would be when a server operating at 100 Mbps is
sending data to a workstation operating at only 10 Mbps.
How a switch signals an end node to stop transmitting data differs

depending on the speed and duplex mode of the end node and switch
port. A twisted pair port operating at 100 Mbps and half-duplex mode will
stop an end node from transmitting data by forcing a collision. A collision
on an Ethernet network occurs when two end nodes attempt to transmit
data using the same data link at the same time. A collision causes end
nodes to stop sending data. When the switch needs to stop a 100 Mbps,
half-duplex end node from transmitting data, it forces a collision on the
data link, which stops the end node. When the switch is ready to receive
data again, the switch stops forcing collisions. This is referred to as back
pressure.
A port operating at 100 Mbps and full-duplex mode uses PAUSE frames,
as specified in the IEEE 802.3x standard, to stop the transmission of data
from an end node. Whenever the switch wants an end node to stop
transmitting data, it issues this frame. The frame instructs the end node to
cease transmission. The switch continues to issue PAUSE frames until it is
ready again to receive data from the end node. This is referred to as flow
control.
The AT-GS900/xE switches support both TX and RX flow control.
418 of 459
Network Topologies
This section illustrates two network topologies that you can create with the
AT-GS900/xE switches: a power workgroup and collapsed backbone.
Both types of topologies are described below.
Power The topology shown in Figure 5 is commonly referred to as a power

Workgroup workgroup topology. Each workstation or end node is connected directly to
a port on the AT-GS900/8E switch. Each end node has a dedicated data
Topology link to the switch for best performance and reliability. The devices can
operate at 10 Mbps, 100 Mbps or 1000 Mbps.
AT-GS900/8E Switch
POWER
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
1044
Legend
10 Mbps
100 Mbps
1000 Mbps
Figure 5. Power Workgroup Topology
419 of 459
Collapsed In the topology illustrated in Figure 6, an AT-GS900/8E connects Fast

Backbone Ethernet switches that have Gigabit Ethernet uplinks. This type of topology
is often referred to as a collapsed backbone topology. The switch functions
as the focal point of the network and transfers an Ethernet frame between
the Fast Ethernet switches only when the destination end node for the
frame is on a different switch than the end node that originated the frame.
This reduces the amount of unnecessary data traffic in each workgroup,
freeing up bandwidth and improving network performance.
AT-GS900/8E Switch
POWER
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
1045
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
Fast Ethernet Switches with Gigabit Uplinks
Legend
10 Mbps
100 Mbps
1000 Mbps
Figure 6. Collapsed Backbone - Hub Topology
420 of 459
Chapter 2
Installation
This chapter contains the following sections:
Reviewing Safety Precautions on page 23

Selecting a Site for the Switch on page 24
Planning the Installation on page 25
Unpacking the Switch on page 26
Installing the Switch on a Table or Desktop on page 27
Wall-Mounting the Switch on page 29
Cabling the Switch on page 31
Powering On the Switch on page 32
421 of 459
Reviewing Safety Precautions
Please review the following safety precautions before you begin to install
the switch or any of its components. Refer to Translated Safety
Statements on page 37 for translated safety statements in your language.
Warning
To prevent electric shock, do not remove the cover. No user-
serviceable parts inside. This unit contains hazardous voltages and
should only be opened by a trained and qualified technician. To
avoid the possibility of electric shock, disconnect electric power to
the product before connecting/disconnecting the LAN cables. 3
Warning
Do not work on equipment or cables during periods of lightning
activity. 4
Warning
Power cord is used as a disconnection device. To de-energize
equipment, disconnect the power cord. 5
Warning
Class I Equipment. This equipment must be earthed. The power
plug must be connected to a properly wired earth ground socket
outlet. An improperly wired socket outlet could place hazardous
voltages on accessible metal parts. 6
Caution
Pluggable Equipment: The socket outlet shall be installed near the
equipment and shall be easily accessible. 7
Caution
Air vents: Air vents must not be blocked and must have free access
to the room ambient air for cooling. 8
Caution
Operating Temperature: This product is designed for a maximum
ambient temperature of 40C. 9
Caution
All Countries: Install this product in accordance with local and
National Electric Codes. 10
422 of 459
Chapter 2: Installation
Selecting a Site for the Switch
Observe the following requirements when choosing a site for the

AT-GS900/xE Gigabit Ethernet switch:
If you are installing the switch on a table, be sure that the table is level
and secure.
The power outlet for the switch should be located near the unit and
should be easily accessible.
The site should provide for easy access to the ports on the front of the
switch. This will make it easy for you to connect and disconnect
cables, as well as view the switchs LEDs.
To allow proper cooling of the switch, air flow around the unit and
through its vents on the side and rear should not be restricted.
Do not place objects on top of the switch.
Do not expose the switch to moisture or water.
Ensure that the site is a dust-free environment.
You should use dedicated power circuits or power conditioners to
supply reliable electrical power to the network devices.
423 of 459
Planning the Installation
Table 2 contains the cabling specifications for the twisted pair ports.
Table 2. Twisted Pair Cabling and Distances
Maximum
Speed Type of Cable Operating
Distance
10 Mbps Category 3 or better 100-ohm 100 m (328 ft)

shielded or unshielded twisted pair
cable
100 Mbps Category 5 or Category 5E 100 m (328 ft)
(Enhanced) 100-ohm shielded or
unshielded twisted pair cable
1000 Mbps Category 5 and Category 5E 100 m (328 ft)
(Enhanced) 100-ohm shielded or
unshielded twisted pair cable
Note
The twisted pair ports on the switch feature auto-MDI when
operating at either 10 or 100 or 1000 Mbps. Each port is individually
configured as MDI or MDI-X when connected to an end node.
Consequently, you can use either a straight-through or crossover
twisted pair cable when connecting any network device to a twisted
pair port on the switch.
424 of 459
Unpacking the Switch
To unpack an AT-GS900/xE switch, perform the following procedure:
1. Remove all components from the shipping package.
Note
Store the packaging material in a safe location. You must use the
original shipping material if you need to return the unit to Allied
Telesis.
2. Place the switch on a level, secure surface.
3. Verify that the following hardware components are included in your

switch package. If any item is missing or damaged, contact your Allied
Telesis sales representative for assistance.
One AT-GS900/xE Gigabit Ethernet switch

Four self-adhesive rubber feet
Wall-mounting kit
External power supply
Documentation CD
Warranty card
425 of 459
Installing the Switch on a Table or Desktop
To install the AT-GS900/xE switch on a table or desktop, perform the

following procedure:
1. Remove all the items from the packaging and store the packaging
material in a safe place. In the event a problem occurs and you need to
return the unit, please use as much of the original shipping material as
possible.
2. Attach the four self-adhesive rubber feet to the bottom of the switch, as
shown in Figure 7.
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
POWER

COL HDX FDX ACT 10/100 LINK ACT 1000 LINK AT-GS900/8E
1033
Figure 7. Attaching the Rubber Feet
3. Place the switch on a flat and secure surface, leaving ample space
around the switch for ventilation.
4. Connected the twisted pair cables to the twisted pair ports.
When connecting a twisted pair cable to a port, observe the following

guidelines:
An RJ-45 connector should fit snugly into the port on the switch.
The tab on the connector should lock the connector into place.
You should check to be sure that you are using the appropriate
type of twisted pair cabling. Refer to Twisted Pair Cabling and
Distances on page 25 for twisted pair cable specifications.
Since the twisted pair ports feature Auto MDI/MDI-X, you can use a
straight-through twisted pair cable to connect any type of network
device to a port on the switch.
5. Apply DC power to the switch by plugging the DC power connector

from the external power adapter to the DC power jack on the back
panel of the unit, as described in Powering On the Switch on
page 32.
426 of 459
Warning
Power cord is used as a disconnection device: To de-energize
6. Verify that the POWER LED is green. If the LED is OFF, refer to
Troubleshooting on page 33 for instructions.
Note
The switch perform a self-diagnostic test upon power up. This takes
about 20 seconds to complete.
7. Power ON the end-nodes connected to the switch.
8. Check that all the L/A LEDs are green. If any of the LEDs is OFF, refer
to Troubleshooting on page 33 for instructions.
The switch is now ready for use.
427 of 459
Wall-Mounting the Switch
The AT-GS900/xE switch can be mounted horizontally on a wall using the

two keyhole slots in the bottom of the switch.
To mount an AT-GS900/xE switch onto a wall, perform the following

procedure:
1. Remove all equipment from the package and store the packaging
material in a safe place.
2. If attached, remove the rubber feet, data cables, and power cord from
the switch.
3. Select a wall location for the switch.
4. Mark two hole locations on the wall.
5. At the marked locations for the holes, pre-drill for the drywall anchors
and drive the screws through the holes.
6. Align the switch horizontally, as illustrated in Figure 8..
PO
W
ER
8
1
P
A
or
T-G
t 10
2
/1
S
00
/1
90
00
3
0
0/8
M
bp
E
s
4
E
th
er
ne
5
tS
w
itc
h
6
7
8
1
2
3
10
00
4
LI
NK
AC
T
10
/1
00
5
LI
NK
AC
T
6
FD
X
HD
X
7
CO
L
8
1041
Figure 8. Aligning an AT-GS900/8E for Wallmount Installation
428 of 459
7. Position and hang the switch onto the wall using the two keyhole slots
located in the bottom of the switch, as illustrated in Figure 9.
8
L
CO
7
X
HD
X
FD
6
T
AC
5
NK
LI
00
/1
10
T
AC
NK
4
LI
00
10
3
2
1
8
7
6
h
itc
w
tS
5
ne
er
th
E
0 E
4
s
bp
00 /8
M
0
90
3
/1
S
00
/1
T-G
2
t 10
or
A
P
1
8
ER
W
PO
1042
Figure 9. Wallmounting an AT-GS900/8E Switch
8. Make sure that the switch is securely mounted onto the wall.
The switch is now ready for cabling.
429 of 459
Cabling the Switch
To connect the twisted pair cables to the ports on the AT-GS900/xE

switch, perform the following procedure:
1. Connect the twisted pair data cables to the RJ-45 ports on the switch,
as shown in Figure 10.
1000
LINK
ACT
10/1
00 LI
NK
ACT
2
FDX
HDX
3
COL
1034
Figure 10. Connecting the Twisted Pair Data Cables
When connecting a twisted pair cable to a port, observe the following

guidelines:
An RJ-45 connector should fit snugly into the port on the switch.
The tab on the connector should lock the connector into place.
The ports on the switch are auto-MDI/MDI-X. You can use a
straight-through twisted pair cable to connect any type of network
device to a port on the switch.
The network should not contain data loops, which can adversely
affect network performance. A data loop exists when two or more
network devices can communicate with each other over more than
one data path.
430 of 459
Powering On the Switch
To apply power to the AT-GS900/xE switch, perform the following

procedure:
1. Apply DC power to the switch by plugging the DC power connector

from the external power adapter to the DC power jack on the back
panel of the unit, as shown in Figure 11.
Warning
Power cord is used as a disconnection device: To de-energize
Caution
Use only safety licensed power supply cord.
12V
DC
1035
Figure 11. Connecting the DC Power Connector to Switch
2. Plug the AC end of the external power adapter into a wall outlet.
3. Power on the end-nodes.
4. Verify that the POWER LED is green. If the LED is OFF, refer to
Troubleshooting on page 33.
The switch is ready for network operations.
431 of 459
Chapter 3
Troubleshooting
This chapter contains information on how to troubleshoot the switch in the

event a problem occurs.
Note
If you are still unable to resolve the problem after following the
instructions in this chapter, contact Allied Telesis Technical Support
for assistance. Refer to Contacting Allied Telesis on page 10.
Check the POWER LED on the front of the switch. If the LED is OFF,
indicating that the unit is not receiving power, do the following:
Verify that the external power supply is securely connected to the

power source and to the DC power jack on the back panel of the
switch.
Verify that the power outlet has power by connecting another device to
it.
Try connecting the unit to another power source.
Try using a different power cord.
Verify that the voltage from the power source is within the required
levels for your region.
Verify that the L/A LED for each port is ON. If a L/A LED is OFF, do the
following:
Verify that the end-node connected to the port is powered ON and is

operating properly.
Verify that the twisted pair cable is securely connected to the port on
the switch and to the port on the end-node.
Ensure that the twisted pair cable does not exceed 100 meters (328
feet).
Verify that you are using the appropriate category of twisted pair cable:
Category 3 or better for 10 Mbps operation and Category 5 and
Category 5E for 100 Mbps operation.
432 of 459
Appendix A
Technical Specifications
Physical Specifications
Dimensions: (W x D x H)
AT-GS900/5E 140 mm x 101 mm x 31 mm
(5.5 in x 4.0 in x 1.2 in)
AT-GS900/8E 195 mm x 114 mm x 36 mm
(7.7 in x 4.5 in x 1.4 in)
Weight:
AT-GS900/5E 0.24 kg (0.528 lbs)
AT-GS900/8E 0.36 kg (0.8 lbs)
Environmental Specifications
Operating Temperature: 0 C to 40 C (32 F to 104 F)
Storage Temperature: -25 C to 70 C (-13 F to 158 F)
Operating Humidity: 5% to 90% non-condensing
Storage Humidity: 5% to 95% non-condensing
Operating Altitude Range: Up to 10,000 feet (3,048 meters)
MTBF: 490,000 hours
Power Specifications
Chassis Power Consumption:

AT-GS900/5E 6.4 W maximum
AT-GS900/8E 9 W maximum
DC Input 12 VDC / 1A maximum
External Power Adapter:

Input Voltage Range 120 VAC 60 Hz (US)
230 VAC 50 Hz (UK)
240 VAC 50 Hz (EU & AUS)
DC Output 12 VDC / 1A maximum
433 of 459
Safety and Electromagnetic Emissions Certifications
EMI FCC Class A, CISPR 22 Class A,

EN55022 Class A, C-TICK, CE
Immunity EN55024
Electrical Safety UL 60950 (CULUS), EN60950 (TUV)
Compliance Standards
IEEE 802.3 Ethernet
IEEE 802.3i 10Base-T
IEEE 802.3u 100Base-TX
IEEE 802.3x Flow Control, Symmetric and Asymmetric
RoHS Compliant
434 of 459
Appendix A: Technical Specifications
RJ-45 Twisted Pair Port Connectors
This section lists the connectors and connector pinouts for the
AT-GS900/xE Gigabit Ethernet switch and its components.
Figure 12 illustrates the pin layout to an RJ-45 connector and port.
8 8
1 1
Figure 12. RJ-45 Connector and Port Pin Layout
Table 3 lists the RJ-45 pin signals when a twisted pair port is operating in
the MDI configuration.
Table 3. MDI Pin Signals (10Base-T or 100Base-TX)
Pin Signal
1 TX+
2 TX-
3 RX+
6 RX-
Table 4 lists the RJ-45 port pin signals when a twisted pair port is
operating in the MDI-X configuration.
Table 4. MDI-X Pin Signals (10Base-T or 100Base-TX)
Pin Signal
1 RX+
2 RX-
3 TX+
6 TX-
435 of 459
Appendix B
Translated Safety Statements
Important: This appendix contains multiple-language translations for the safety statements in this
guide.
Wichtig: Dieser Anhang enthlt bersetzungen der in diesem Handbuch enthaltenen

Sicherheitshinweise in mehreren Sprachen.
Importante: Este apndice contiene traducciones en mltiples idiomas de los mensajes de

seguridad incluidos en esta gua.
Important: Cette annexe contient la traduction en plusieurs langues des instructions de scurit
figurant dans ce guide.
Importante: Questa appendice contiene traduzioni in pi lingue degli avvisi di sicurezza di questa
guida.
: ,
.
436 of 459
Appendix B: Translated Safety Statements
Laser Safety Notices

1 Warning: Class 1 Laser product.
2 Warning: Do not stare into the laser beam.
Electrical Safety Notices

3 Warning: To prevent electric shock, do not remove the cover. No user-serviceable
parts inside. This unit contains hazardous voltages and should only be opened by a
trained and qualified technician. To avoid the possibility of electric shock, disconnect
electric power to the product before connecting or disconnecting the LAN cables.
4 Warning: Do not work on equipment or cables during periods of lightning activity.
5 Warning: Power cord is used as a disconnection device. To de-energize equipment,

disconnect the power cord.
6 Warning: Class I Equipment. This equipment must be earthed. The power plug must
be connected to a properly wired earth ground socket outlet. An improperly wired
socket outlet could place hazardous voltages on accessible metal parts.
7 Pluggable Equipment. The socket outlet shall be installed near the equipment and
shall be easily accessible.
8 Caution: Air vents must not be blocked and must have free access to the room
ambient air for cooling.
9 Warning: Operating Temperature. This product is designed for a maximum ambient

temperature of 40 degrees C.
10 All Countries: Install product in accordance with local and National Electrical Codes.
11 Warning: As a safety precaution, install a circuit breaker with a minimum value of 15
Amps between the equipment and the DC power source.
Always connect the wires to the LAN equipment first before you connect the wires to
the circuit breaker. Do not work with HOT feeds to avoid the danger of physical injury
from electrical shock. Always be sure that the circuit breaker is in the OFF position
before connecting the wires to the breaker.
12 Warning: Do not strip more than the recommended amount of wire. Stripping more
than the recommended amount can create a safety hazard by leaving exposed wire
on the terminal block after installation.
13 Warning: When installing this equipment, always ensure that the frame ground
connection is installed first and disconnected last.
437 of 459
14 Warning: Check to see if there are any exposed copper strands coming from the
installed wire. When this installation is done correctly there should be no exposed
copper wire strands extending from the terminal block. Any exposed wiring can
conduct harmful levels of electricity to persons touching the wires.
15 This system works with positive grounded or negative grounded DC systems.
16 Warning: Only trained and qualified personnel are allowed to install or to replace this
equipment.
17 Caution: The attached mounting brackets must be used to securely mount the device
on the wall.
18 Caution: Do not install in direct sunlight, or a damp or dusty place.
19 Caution: Do not expose the gateway device to moisture or water.
20 Caution: If the gateway device is installed indoors, make sure that the site is a dust-
free environment. The site should provide for easy access to the ports of the gateway
device.This will make it easy for you to connect and disconnect cables, as well as
view the LEDs.
21 Warning: The power source for the gateway unit should be located near the unit and
should be easily accessible.
22 Caution: To allow proper cooling of the gateway device, make sure that the air flow
around the unit and through its heatsink cooling fins on the rear is not restricted.
23 Circuit Overloading: Consideration should be given to the connection of the

equipment to the supply circuit and the effect that overloading of circuits might have
on overcurrent protection and supply wiring. Appropriate consideration of equipment
nameplate ratings should be used when addressing this concern.
24 Caution: Risk of explosion if battery is replaced by an incorrect type. Replace only
with the same or equivalent type recommended by the manufacturer. Dispose of used
batteries according to the manufacturers instructions.
Attention: Le remplacement de la batterie par une batterie de type incorrect peut

provoquer un danger dexplosion. La remplacer uniquement par une batterie du
mme type ou de type quivalent recommande par le constructeur. Les batteries
doivent tre limines conformment aux instructions du constructeur.
25 Warning: For centralized DC power connection, install only in a restricted access
area.
26 A tray cable is required to connect the power source if the unit is powered by
centralized DC power. The tray cable must be a UL listed Type TC tray cable and
rated at 600 V and 90 degrees C, with three conductors, minimum 14 AWG.
438 of 459
Appendix B: Translated Safety Statements
27 Warning: Mounting of the equipment in the rack should be such that a hazardous
condition is not created due to uneven mechanical loading.
28 Warning: Remove all metal jewelry, such as rings and watches, before installing or
removing a line card from a powered-on chassis.
29 Use dedicated power circuits or power conditioners to supply reliable electrical power
to the device.
30 Warning: The chassis may be heavy and awkward to lift. Allied Telesis recommends
that you get assistance when mounting the chassis in an equipment rack.
31 Warning: Do not look directly at the fiber optic cable ends or inspect the cable ends
with an optical lens.
32 Warning: This unit might have more than one power cord. To reduce the risk of
electric shock, disconnect all power cords before servicing the unit.
33 Warning: Only trained and qualified personnel are allowed to install or to replace this
equipment.
34 Warning: The power input must be provided from SELV source only, per IEC 60950.
Do not connect to a centralized DC battery bank.
35 UL recognized wires of 18 AWG minimum should be provided by the installer.
36 UL recognized wires of 22 AWG minimum should be provided by the installer.
37 Caution: Power to the hub must be sourced only from the adapter.
38 If installed in a closed or multi-unit rack assembly, the operating ambient temperature
of the rack environment may be greater than the room ambient temperature.
Therefore, consideration should be given to installing the equipment in an
environment compatible with the manufacturers maximum rated ambient
temperature (Tmra).
39 Caution: Installation of the equipment in a rack should be such that the amount of air
flow required for safe operation of the equipment is not compromised.
40 Warning: Reliable earthing of rack-mounted equipment should be maintained.
Particular attention should be given to supply connections other than direct
connections to the branch circuits (e.g., use of power strips).
439 of 459
Telecommunications Compliance Notices

41 Warning: When using your telephone equipment, basic safety precautions should
always be followed to reduce the risk of fire, electronic shock, and injury to persons,
including the following:
Do not use this product near water, for example, near a bathtub, washbowl, kitchen
sink, or laundry tub in a wet basement or near a swimming pool.
Avoid using a telephone (other than a cordless type) during an electrical storm.
There may be a remote risk of electric shock from lightning.
Do not use the telephone to report a gas leak in the vicinity of the leak.
42 Warning: Before connecting to the telephony (TEL) ports on the gateway device,
make sure to disconnect the Public Switch Telephone Network (PSTN) feed to the
premises.
43 Warning: To reduce the risk of fire, use only No. 26 AWG or larger
telecommunication line cord.
440 of 459
Liebert GXT MT+
441 of 459
Table of Contents
1. Important Safety Warning 1
1-1. Transportation 1
1-2. Preparation 1
1-3. Installation 1
1-4. Operation 1
1-5. Maintenance, service and faults 2
2. Installation and setup 3

2-1. Rear view 3
2-2. Setup the UPS 3
3. Operations Instruction. 6
3-1. Button operation 6
3-2. LCD Panel 7
3-3. Audible Alarm 8
3-4. LCD display wordings index 8
3-5. UPS Setting 9
3-6. Operating Mode Description 11
3-7. Faults Reference Code 12
3-8. Warning indicator 12
4. Troubleshooting... 13
5. Storage and Maintenance. 15
6. Specifications 16
442 of 459
1. Important Safety Warning
Please comply with all warnings and operating instructions in this manual strictly. Save this manual
properly and read carefully the following instructions before installing the unit. Do not operate this
unit before reading through all safety information and operating instructions carefully
1-1. Transportation
z Please transport the UPS system only in the original package to protect against shock and
impact.
1-2. Preparation
z Condensation may occur if the UPS system is moved directly from cold to warm
environment. The UPS system must be absolutely dry before being installed. Please allow
at least two hours for the UPS system to acclimate the environment.
z Do not install the UPS system near water or in moist environments.
z Do not install the UPS system where it would be exposed to direct sunlight or near heater.
z Do not block ventilation holes in the UPS housing.
1-3. Installation
z Do not connect appliances or devices which would overload the UPS system (e.g. laser
printers) to the UPS output sockets.
z Place cables in such a way that no one can step on or trip over them.
z Do not connect domestic appliances such as hair dryers to UPS output sockets.
z The UPS can be operated by any individuals with no previous experience.
z Connect the UPS system only to an earthed shockproof outlet which must be easily
accessible and close to the UPS system.
z Please use only VDE-tested, CE-marked mains cable (e.g. the mains cable of your
computer) to connect the UPS system to the building wiring outlet (shockproof outlet).
z Please use only VDE-tested, CE-marked power cables to connect the loads to the UPS
system.
z When installing the equipment, it should ensure that the sum of the leakage current of the
UPS and the connected devices does not exceed 3.5mA.
1-4. Operation
z Do not disconnect the mains cable on the UPS system or the building wiring outlet
(shockproof socket outlet) during operations since this would cancel the protective
earthing of the UPS system and of all connected loads.
z The UPS system features its own, internal current source (batteries). The UPS output
sockets or output terminals block may be electrically live even if the UPS system is not
connected to the building wiring outlet.
z In order to fully disconnect the UPS system, first press the OFF/Enter button to disconnect
the mains.
z Prevent no fluids or other foreign objects from inside of the UPS system.
443 of 459
1-5. Maintenance, service and faults
z The UPS system operates with hazardous voltages. Repairs may be carried out only by
qualified maintenance personnel.
z Caution - risk of electric shock. Even after the unit is disconnected from the mains
(building wiring outlet), components inside the UPS system are still connected to the
battery and electrically live and dangerous.
z Before carrying out any kind of service and/or maintenance, disconnect the batteries and
verify that no current is present and no hazardous voltage exists in the terminals of high
capability capacitor such as BUS-capacitors.
z Only persons are adequately familiar with batteries and with the required precautionary
measures may replace batteries and supervise operations. Unauthorized persons must be
kept well away from the batteries.
z Caution - risk of electric shock. The battery circuit is not isolated from the input voltage.
Hazardous voltages may occur between the battery terminals and the ground. Before
touching, please verify that no voltage is present!
z Batteries may cause electric shock and have a high short-circuit current. Please take the
precautionary measures specified below and any other measures necessary when working
with batteries:
remove wristwatches, rings and other metal objects
use only tools with insulated grips and handles.
z When changing batteries, install the same number and same type of batteries.
z Do not attempt to dispose of batteries by burning them. This could cause battery
explosion.
z Do not open or destroy batteries. Escaping electrolyte can cause injury to the skin and eyes.
It may be toxic.
z Please replace the fuse only with the same type and amperage in order to avoid fire
hazards.
z Do not dismantle the UPS system.
444 of 459
2. Installation and Setup
NOTE: Before installation, please inspect the unit. Be sure that nothing inside the package is
damaged. Please keep the original package in a safe place for future use.
NOTE: There are two different types of online UPS: standard and long-run models. Please refer to the
following model table.
Model Type Model Type

1000 1000L
2000 Standard 2000L Long-run
3000 3000L
2-1. Rear View

1000(L) TOWER 2000(L) TOWER 3000(L) TOWER
1. Programmable outlets: connect to non-critical 7. USB communication port

loads. 8. RS-232 communication port
2. Output receptacles: connect to mission- 9. SNMP intelligent slot
critical loads. 10. External battery connection (only available
3. AC input for L model)
4. Input circuit breaker 11. Output terminal
5. Network/Fax/Modem surge protection 12. Output circuit breaker
6. Emergency power off function connector
(EPO)
2-2. Setup the UPS

Step 1: UPS input connection
Plug the UPS into a two-pole, three-wire, grounded receptacle only. Avoid using extension cords.
Use the input power cord from your server or protected equipment. Use the supplied output cable
to connect between UPS and your server.
445 of 459
Step 2: UPS output connection
There two kinds of outputs: programmable outlets and general outlets. Please connect non-critical
devices to the programmable outlets and critical devices to the general outlets. During power failure,
you may extend the backup time to critical devices by setting shorter backup time for non-critical
devices.
Step 3: Communication connection

Communication port:
USB port RS-232 port Intelligent slot
To allow for unattended UPS shutdown/start-up and status monitoring, connect the communication
cable one end to the USB/RS-232 port and the other to the communication port of your PC. With the
monitoring software installed, you can schedule UPS shutdown/start-up and monitor UPS status
through PC.
The UPS is equipped with intelligent slot perfect for either SNMP or AS400 card. When installing
either SNMP or AS400 card in the UPS, it will provide advanced communication and monitoring
options.
PS. USB port and RS-232 port cant work at the same time.
Step 4: Network connection

Network/Fax/Phone surge port
Connect a single modem/phone/fax line into surge-protected IN outlet on the back panel of the
UPS unit. Connect from OUT outlet to the equipment with another modem/fax/phone line cable.
Step 5: Disable and enable EPO function

Keep the pin 1 and pin 2 closed for UPS normal operation. To activate EPO function, cut the wire
between pin 1 and pin 2.
Its in closed status for UPS

normal operation.
Step 6: Turn on the UPS

Press the ON/Mute button on the front panel for two seconds to power on the UPS.
Note: The battery charges fully during the first five hours of normal operation. Do not expect full
battery run capability during this initial charge period.
446 of 459
Step 7: Install software
For optimal computer system protection, install UPS monitoring software to fully configure UPS
shutdown. You may insert provided CD into CD-ROM to install the monitoring software. If not,
please follow steps below to download and install monitoring software from the internet:
1. Go to the website h ttp://www.power-software-download.com
2. Click ViewPower software icon and then choose your required OS to download the software.
3. Follow the on-screen instructions to install the software.
4. When your computer restarts, the monitoring software will appear as an orange plug icon located
in the system tray, near the clock.
Step 8: External battery connection (for long-run models only)

Follow the right chart to make external battery
connection.
447 of 459
3. Operating Instruction
3-1. Button operation
Button View
Button Function
Turn on the UPS: Press and hold ON/MUTE button for at least 2 seconds
to turn on the UPS.
Mute the alarm: When the UPS is on battery mode, press and hold this
button for at least 5 seconds to disable or enable the alarm system. But
its not applied to the situations when warnings or errors occur.
ON/MUTE Button
Up key: Press this button to display previous selection in UPS setting
mode.
Switch to UPS self-test mode: Press ON/MUTE buttons simultaneously for
5 seconds to enter UPS self-testing while in AC mode, ECO mode, or
converter mode.
Turn off the UPS: Press and hold this button at least 2 seconds to turn off
the UPS in battery mode. UPS will be in standby mode under power
normal or transfer to Bypass mode if the Bypass enable setting by
OFF/ENTER Button
pressing this button.
Confirm selection key: Press this button to confirm selection in UPS
setting mode.
Switch LCD message: Press this button to change the LCD message for
input voltage, input frequency, battery voltage, output voltage and
output frequency. It will return back to default display when pausing for
10 seconds.
SELECT Button
Setting mode: Press and hold this button for 5 seconds to enter UPS
setting mode when UPS is in standby mode or bypass mode.
Down key: Press this button to display next selection in UPS setting
mode.
Switch to bypass mode: When the main power is normal, press ON/MUTE
ON/MUTE + and SELECT buttons simultaneously for 5 seconds. Then UPS will enter to
SELECT Button bypass mode. This action will be ineffective when the input voltage is out
of acceptable range.
448 of 459
3-2. LCD Display
Display Function
Backup time setting and information
Indicates the backup time in pie chart.
Indicates the backup time in numbers.

H: hours, M: minute, S: second
Setting operation
Indicates the setting operation.
Fault & warning information

Indicates that the warning situation occurs.
Indicates the warning and fault codes, and the codes are listed in
details in 3-5 section.
Mute operation
Indicates that the UPS alarm is disabled.
UPS information
Indicates the input and output voltage, frequency, battery voltage,
load information, and internal temperature.
Vac: input/output voltage, Vdc: battery voltage, Hz: frequency, %: load level,
C/F: temperature,
Load information
Indicates the load level by 0-25%, 26-50%, 51-75%, and 76-100%.
Indicates overload.
Indicates the load or the UPS output is short circuit.
Programmable outlets information
Indicates that programmable management outlets are working.
Mode operation information

Indicates the UPS is in online mode.
449 of 459
Indicates the UPS is in battery mode.
Indicates the UPS is bypass mode.

Indicates the UPS is in ECO mode.
Indicates the UPS is in converter mode.
Indicates the UPS is charging battery.
Battery information
Indicates the Battery capacity by 0-25%, 26-50%, 51-75%, and
76-100%.
Indicates the battery is fault.

Indicates low battery level and low battery voltage.
3-3. Audible Alarm

Battery Mode Sounding every 4 seconds
Low Battery Sounding every second
Overload Sounding twice every second
Fault Continuously sounding
Bypass Mode Sounding every 10 seconds
3-4. LCD display wordings index

LCD Area Abbreviation Display content Meaning
ENA Enable
DIS Disable
ESC Escape
B.L Low battery
O.L Overload
N.C Battery is not connected
O.C Overcharge
S.F Site fault
C.H Charger
E.P EPO
F.A Fan
B.V Bypass voltage range
T.P Temperature
450 of 459
3-5. UPS Setting
There are two parameters to set up the
UPS.
Parameter 1
Parameter 1: Its for program
alternatives. There are 8 programs to set
Parameter 2 up. Refer to below table.
Parameter 2 is the setting option or value
for each program.
z 01: Output voltage setting

Interface Setting
Parameter 2: Output voltage setting
You may choose the following output voltage in parameter
2:
208: presents output voltage is 208Vac
z 02: Frequency Converter enable/disable
Interface Setting
Parameter 2: Enable or disable converter mode. You may
choose the following two options:
CF ENA: converter mode enable
CF DIS: converter mode disable
z 03: Output frequency setting

Interface Setting
Parameter 2: Output frequency setting.
You may set the initial frequency on battery mode:
BAT 50: presents output frequency is 50Hz
BAT 60: presents output frequency is 60Hz
If converter mode is enabled, you may choose the following
output frequency:
CF 50: presents output frequency is 50Hz
CF 60: presents output frequency is 60Hz
451 of 459
z 04: ECO enable/disable
Interface Setting
Parameter 2: Enable or disable ECO function. You may
choose the following two options:
ENA: ECO mode enable
DIS: ECO mode disable
z 05: Bypass enable/disable when UPS is off

Interface Setting
Parameter 2: Enable or disable Bypass function when UPS is
off. You may choose the following two options:
ENA: Bypass enable
DIS: Bypass disable
z 06: Programmable outlets enable/disable

Interface Setting
Parameter 3: Enable or disable programmable outlets.
ENA: Programmable outlets enable
DIS: Programmable outlets disable
z 07: Programmable outlets setting

Interface Setting
Parameter 3: Set up backup time limits for programmable
outlets.
0-999: setting the backup time limits in minutes from 0-999
for programmable outlets which connect to non-critical
devices on battery mode.
z 00: Exit setting

Interface Setting
ESC: Exit the setting menu.
452 of 459
3-6. Operating Mode Description
Operating Description LCD display
mode
Switch on When pressing ON/MUTE button, if battery
voltage is within acceptable range, ON will
flash until the UPS is turned on.
Online mode When the input voltage is within acceptable

range, UPS will provide pure and stable AC power
to output. The UPS will also charge the battery at
online mode.
ECO mode Energy saving mode:

When the input voltage is within voltage
regulation range, UPS will bypass voltage to
output for energy saving.
Frequency When input frequency is within 40 Hz to 70 Hz,

Converter mode the UPS can be set at a constant output
frequency, 50 Hz or 60 Hz. The UPS will still
charge battery under this mode.
Battery mode When the input voltage is beyond the acceptable

range or power failure and alarm is sounding
every 4 second, UPS will backup power from
battery.
Bypass mode When input voltage is within acceptable range

but UPS is overload, UPS will enter bypass mode
or bypass mode can be set by front panel. Alarm
is sounding every 10 second.
Standby mode UPS is powered off without output power, but

the battery still can be charged.
453 of 459
Fault mode The UPS is in fault mode when no output power
is supplied from the UPS and the fault icon
flashes on the LCD display, although the
information of UPS can be displayed in the
screen.
3-7. Faults Reference Code

Fault event Fault code Icon Fault event Fault code Icon
Bus start fail 01 x Inverter voltage Low 13 x
Bus over 02 x Inverter output short 14
Bus under 03 x Battery voltage too high 27
Bus unbalance 04 x Battery voltage too low 28
Inverter soft start fail 11 x Over temperature 41 x
Inverter voltage high 12 x Over load 43
3-8. Warning indicator

Indicator
Warning Alarm
Word Icon (flashing)
Low battery B.L Sounding every second
Overload O.L Sounding twice every second
Battery is not connected N.C Sounding every second
Overcharge O.C Sounding every second
Site wiring fault S.F Sounding every second

EPO enable E.P Sounding every second
Fan failure F.A Sounding every second
Over temperature T.P Sounding every second
Charger failure C.H Sounding every second
Out of bypass voltage range B.V Sounding every second
454 of 459
4. Troubleshooting
If the UPS system does not operate correctly, please solve the problem by using the table below.
Symptom Possible cause Remedy
No indication and alarm even The AC input power is not Check if input power cord
though the mains is normal. connected well. firmly connected to the
mains.
The AC input is connected to Plug AC input power cord to
the UPS output. AC input correctly.
The icon and the warning code EPO function is activated. Set the circuit in closed
position to disable EPO
flashing on LCD display and function.
alarm is sounding every second.
The icon and flashing on Line and neutral conductors Rotate mains power socket
LCD display and alarm is sounding of UPS input are reversed. by 180 and then connect to
every second. UPS system.
The external or internal Check if all batteries are
battery is incorrectly connected well.
The icon and flashing on connected.
LCD display and alarm is sounding
every second.
Fault code is shown as 27 and the Battery voltage is too high Contact your dealer.
icon is lighting on LCD or the charger is fault.
display and alarm is continuously
sounding.
Fault code is shown as 28 and the Battery voltage is too low or Contact your dealer.
icon is lighting on LCD the charger is fault.
display and alarm is continuously
sounding.
The icon and is UPS is overload Remove excess loads from
flashing on LCD display and alarm is UPS output.
sounding twice every second. UPS is overloaded. Devices Remove excess loads from
connected to the UPS are UPS output.
fed directly by the electrical
network via the Bypass.
After repetitive overloads, Remove excess loads from
the UPS is locked in the UPS output first. Then shut
Bypass mode. Connected down the UPS and restart it.
devices are fed directly by
the mains.
Fault code is shown as 43 and The The UPS shut down Remove excess loads from
icon is lighting on LCD automatically because of UPS output and restart it.
display and alarm is continuously overload at the UPS output.
sounding.
455 of 459
Fault code is shown as 14 and the The UPS shut down Check output wiring and if
icon is lighting on LCD automatically because short connected devices are in
display and alarm is continuously circuit occurs on the UPS short circuit status.
sounding. output.
Fault code is shown as 1, 2, 3, 4, 11, A UPS internal fault has Contact your dealer
12, 13 and 41 on LCD display and occurred. There are two
alarm is continuously sounding. possible results:
1. The load is still supplied,
but directly from AC power
via bypass.
2. The load is no longer
supplied by power.
Battery backup time is shorter than Batteries are not fully Charge the batteries for at
nominal value charged least 5 hours and then check
capacity. If the problem still
persists, consult your dealer.
Batteries defect Contact your dealer to
replace the battery.
The icon and the warning code

Check fans and notify
flashing on LCD display and Fan is locked or not working
dealer!!
alarm is sounding every second.
456 of 459
5. Storage and Maintenance
5-1. Operation
The UPS system contains no user-serviceable parts. If the battery service life (3~5 years at 25C
ambient temperature) has been exceeded, the batteries must be replaced. In this case, please
contact your dealer.
Be sure to deliver the spent battery to a recycling facility or ship it to your

dealer in the replacement battery packing material.
Storage
Before storing, charge the UPS 5 hours. Store the UPS covered and upright in a cool, dry
location. During storage, recharge the battery in accordance with the following table:
Storage Temperature Recharge Frequency Charging Duration
-25C - 40C Every 3 months 1-2 hours
40C - 45C Every 2 months 1-2 hours
457 of 459
6. Specifications
CAPACITY* 1000 VA / 800 W 2000 VA / 1600 W 3000 VA / 2400 W

INPUT
160 VAC / 140 VAC / 120 VAC / 110 VAC 5 %
Low Line Transfer
( based on load percentage 100% - 80 % / 80 % - 70 % / 70 - 60 % / 60 % - 0)
Voltage
Range Low Line Comeback 175 VAC 5 %
High Line Transfer 300 VAC 5 %
High Line Comeback 290 VAC 5 %
Frequency Range 40Hz ~ 70 Hz
Phase Single phase with ground
Power Factor 0.99 @ 220-230 VAC (input voltage)
OUTPUT
Output voltage 208/220/230/240VAC
AC Voltage Regulation 3% (Batt. Mode)
Frequency Range 47 ~ 53 Hz or 57 ~ 63 Hz (Synchronized Range)
Frequency Range (Batt. Mode) 50 Hz 0.25 Hz
100%~110%: audible warning
110%-130%: UPS shuts down in 30 seconds at battery mode or transfers to bypass
Overload mode when the utility is normal.
>130%: UPS shuts down immediately at battery mode or transfer to bypass mode
when the utility is normal.
Current Crest Ratio 3:1
3 % THD (Linear Load) 4 % THD (Linear Load)
Harmonic Distortion
6 % THD (Non-linear Load) 7 % THD (Non-linear Load)
Transfer AC Mode to Batt. Mode Zero
Time Inverter to Bypass 4 ms (Typical)
Waveform (Batt. Mode) Pure Sinewave
EFFICIENCY
AC Mode ~ 85% ~ 88%
Battery Mode ~ 83%
BATTERY
Battery Type 12 V / 7 AH 12 V / 7 AH 12 V / 9 AH
Numbers 3 6 6
Standard
Recharge Time 4 hours recover to 90% capacity (Typical)
Model
Charging Current 1.0 A(max.)
Charging Voltage 41.0 VDC 1% 82.1 VDC 1%
Numbers 3 8
Long-run
Charging Current 4.0 A or 8.0 A(max.)
Model
Charging Voltage 41.0 VDC 1% 82.1 VDC 1%
PHYSICAL
Tower Dimension, D X W X H 397 X 145 X 220 (mm) 421 X 190 X 318 (mm)
Case Net Weight (kgs) 13 7 26 13 28 13
ENVIRONMENT
Operation Humidity 20-90 % RH @ 0- 40C (non-condensing)
Noise Level Less than 45dBA @ 1 Meter
MANAGEMENT
Smart RS-232 or USB Supports Windows 98/2000/2003/XP/Vista/2008, Windows 7, Linux, and MAC
Optional SNMP Power management from SNMP manager and web browser
* Derate capacity to 60% of capacity in Frequency converter mode and to 80% when the output voltage is adjusted to 208VAC
458 of 459
Runtime Chart:
Model Load Level
25% 50% 75% 100%
1000 30 15 8 5
2000 24 18 10 6
3000 31 13 8 5
NOTE: All run times are in minutes, assume fully charged batteries and are typical at 77F (22C).
459 of 459

(Cmsa-A0-El-ma-cya-0010) O&m Manual For Communication System - Telephone System

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

(Cmsa-A0-El-ma-cya-0010) O&m Manual For Communication System - Telephone System

Uploaded by

Copyright:

Available Formats

Power Cogeneration Plant Company

SAUDI ARAMCO THIRD PARTY COGENERATION PROJECTS

Installation, Operation and Maintenance Manual

A 20-MAY-2015 Issued for Information J. H. Shin S. J. Kwon S.Choi S.Choi

PREPARED CHECKED APPROVED

SAMSUNG ENGINEERING CO., LTD

0 15-May-2015 Issued for Construction Ryan Salgado Roberto Bautista Jawn Ng

POWER COGENERATION PLANT COMPANY

SAMSUNG ENGINEERING CO., LTD.

SECL PROJECT NO. : SP2673

VECTOR INFOTECH PTE LTD

Rev. Issue Date Description

A 29.APR.2015 ISSUED FOR APPROVAL

S/N Brand Description Page No.

1 Alcatel-Lucent / Omni PCX OXE System: Common Hardware Installation Manual 4

OXE System: Common Hardware Installation Manual

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of

The information presented is subject to change without notice.

Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright 2014 Alcatel-Lucent. All rights reserved.

 Description of Racks ............................................................................. 1.1

 !"# $ %  $ &' (  ! ) $  

 Safety Standards .................................................................................... 2.1

 Environmental Conditions .................................................................. 3.1

0-2  !"# $ %  $ &' (  ! ) $  

 Overview .................................................................................................... 5.1

 Equipment Reception ........................................................................... 6.1

 Overview ........................................................................................................ 6.1

 Installation Procedure in a Standard 19" Cabinet .......................................... 6.1

 Overview .................................................................................................... 7.1

 !"# $ %  $ &' (  ! ) $  

 General ....................................................................................................... 8.1

0-4  !"# $ %  $ &' (  ! ) $  

 Connecting the Protective Ground .................................................. 9.1

 !"# $ %  $ &' (  ! ) $  

 Replacing the Internal Batteries ......................................................10.1

0-6  !"# $ %  $ &' (  ! ) $  

1.1 Description of Racks

1.1.1 S (SMALL) Rack

Figure 1.1: Small Rack Front Panel

1.1.2 L (LARGE) Rack

 !"# $ %  $ &' (  ! ) $  

Figure 1.2: Large Rack Front Panel

1.2 Boards Description

1-2  !"# $ %  $ &' (  ! ) $  

BOARDS FUNCTIONS DAUGHTERBOARDS CONNECTION

 !"# $ %  $ &' (  ! ) $  

BOARDS FUNCTIONS DAUGHTERBOARDS CONNECTION

1-4  !"# $ %  $ &' (  ! ) $  

- The GA-3 board cannot be hosted in a small rack

Figure 1.3: CS Board Front Panel

1.2.1.2 CS Board Micro Switches Setting

Controller position 0x09

 !"# $ %  $ &' (  ! ) $  

CS board position Micro switches value Micro switches setting

Other positions 0x01

1.2.2 CS-2 Board

Figure 1.4: CS-2 Board Front Panel

1-6  !"# $ %  $ &' (  ! ) $  

Figure 1.5: CS-2 Daughterboards Installation

1.2.2.4 Dual Ethernet

 !"# $ %  $ &' (  ! ) $  

1.2.2.4.2 Ethernet Load Balancing

Description of Racks ............................................................................. 1.1

!"# $ % $ &'( ! ) $

Safety Standards .................................................................................... 2.1

Environmental Conditions .................................................................. 3.1

0-2 !"# $ % $ &'( ! ) $

Overview .................................................................................................... 5.1

Equipment Reception ........................................................................... 6.1

Overview ........................................................................................................ 6.1

Installation Procedure in a Standard 19" Cabinet .......................................... 6.1

Overview .................................................................................................... 7.1

!"# $ % $ &'( ! ) $

General ....................................................................................................... 8.1

0-4 !"# $ % $ &'( ! ) $

Connecting the Protective Ground .................................................. 9.1

!"# $ % $ &'( ! ) $

Replacing the Internal Batteries ......................................................10.1

0-6 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-2 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-4 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-6 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-8 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-10 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-12 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-14 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-16 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-18 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-20 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-22 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $

1-24 !"# $ % $ &'( ! ) $

!"# $ % $ &'( ! ) $