OXO Connect 3.0 SD ManagementTools 8AL91210USAF 1 en

Alcatel-Lucent OXO Connect
Expert Documentation: Management Tools

Release 3.0 - July 2018
8AL91210USAF Ed. 01
Legal notice
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. To view other
trademarks used by affiliated companies of ALE Holding, visit: www.al-enterprise.com/en/legal/
trademarks-copyright. All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Neither ALE Holding nor any of its
affiliates assumes any responsibility for inaccuracies contained herein.
© 2018 ALE International. All rights reserved. http://www.al-enterprise.com
Disclaimer
While efforts were made to verify the completeness and accuracy of the information contained in this
documentation, this document is provided “as is”. To get more accurate content concerning Cross
Compatibilities, Product Limits, Software Policy and Feature Lists, please refer to the accurate
documents published on the Business Partner Web Site.
In the interest of continued product development, ALE International reserves the right to make
improvements to this documentation and the products it describes at any time, without notice or
obligation.
The CE mark indicates that this product conforms to the following Council Directives:
• 2014/53/EU for radio equipment
• 2014/35/EU and 2014/30/EU for non radio equipment (including wired Telecom Terminal
Equipment)
• 2014/34/EU for ATEX equipment
• 2011/65/EU (RoHS)
• 2012/19/EU (WEEE)
Table of
contents Expert Documentation:
Management Tools
Chapter 1
Expert Documentation structure
Chapter 2
Overview
Chapter 3
Installation procedure
3.1 Minimal PC Configuration................................................................................................. 10

3.2 Installing the OMC Software........................................................................................... 10
Chapter 4
Accessing the System
4.1 System Password......................................................................................................................11

4.2 Local Access By LAN............................................................................................................ 11
4.3 Local V24 Access For OMC............................................................................................. 12
4.3.1 Installation Procedure....................................................................................................................... 12
4.4 OMC Remote Access By Modem............................................................................... 13
4.4.1 Remote Access By ISDN Modem...............................................................................................13
4.4.2 Remote Access By The Analog Modem..................................................................................15
4.4.3 Operating Mode................................................................................................................................... 15
4.4.4 Security.................................................................................................................................................... 16
4.5 OMC Remote Access by VPN........................................................................................ 16
4.6 Access With Proxy................................................................................................................... 16
8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 3/42

Table of
Management Tools
Chapter 5
Downloading the Software
5.1 Downloading software for OXO Connect (OXO Connect Small,

Medium, Large platforms delivered in BTCO mode)...............................18
5.2 Downloading software for OXO Connect Compact platform (and
OXO Connect Small, Medium, Large platforms delivered in
stock mode).....................................................................................................................................20
Chapter 6
Download and Swap
6.1 Overview.............................................................................................................................................21
6.2 Download...........................................................................................................................................21
6.2.1 Download Binaries..............................................................................................................................22
6.3 Swap.......................................................................................................................................................22
Chapter 7
Importing/Exporting Files
7.1 Importing data...............................................................................................................................23

7.2 Exporting data.............................................................................................................................. 23

Table of
Management Tools
Chapter 8
Managing Tones
8.1 Root section....................................................................................................................................24

8.2 Frequency section.................................................................................................................... 24
8.3 Tone section................................................................................................................................... 25
8.4 Importing/exporting tones................................................................................................ 25
8.5 Appendix: example of file..................................................................................................26
Chapter 9
Managing Voice Prompts
9.1 Introduction.....................................................................................................................................30
9.2 Individual types of audio file.......................................................................................... 30
9.2.1 On-hold music.......................................................................................................................................30
9.2.2 Automated attendant......................................................................................................................... 31
9.2.3 Pre-announcement messages......................................................................................................32
9.2.4 Automatic Call Distribution voice messages..........................................................................32
9.3 Global management of audio files............................................................................ 33
9.3.1 General export procedure...............................................................................................................34
9.3.2 General import procedure...............................................................................................................34
9.3.3 Complete save of audio files......................................................................................................... 34
9.4 System language modification.....................................................................................35
Chapter 10
Services provided

Chapter
1 Expert Documentation structure
The OXO Connect Expert Documentation is split into fifteen separated documents. Each document
only describes the features supported by OXO Connect RC2.0* or higher (for example: MMC station is
not described since it is not supported). Please refer to the OXO Connect Documentation Note, for
historical information. In addition, the Cross Compatibility document is the reference for detailed status
about supported and unsupported devices and applications.
* RCz.n, with z greater than or equal to 2, stands for any release starting from 2016 introducing
Connect capabilities.
It appears on:
• Product stickers with release format: RC0zn/xx.yy
• In any documentation (including this one) as: Rz.n
These documents are:
table 1.1: Expert Documentation structure
Documentation title Part number
[1] OXO Connect Expert Documentation: General Presentation 8AL91200xxxx

Summary: this document contains general information on OXO Con-
nect, such as a brief description of services provided, platform hard-
ware, handsets and user applications available, limits, compatibility with
standards, environmental constraints.
[2] OXO Connect Expert Documentation: Hardware: Platform, interfaces 8AL91201xxxx

and devices
Summary: this document covers all hardware aspects related to OXO
Connect: this includes description of platforms (racks), boards, sets and
complementary equipment such as additional modules or interface
modules. This document also contains commissioning procedures for
sets.
[3] OXO Connect Expert Documentation: User services 8AL91202xxxx

Summary: this document gives the presentation and configuration pro-
cedure of features available for end-users. The final chapter of the
document synthesizes features availability according to the type of de-
vice or application.
[4] OXO Connect Expert Documentation: Voice mail 8AL91203xxxx

Summary: this document details the integrated voice mail system and
automated attendant (general description, management, services avail-
able for end-users), as well as the configuration procedure to connect
an external voice mail unit.

Chapter 1 Expert Documentation structure
[5] OXO Connect Expert Documentation: Mobility 8AL91204xxxx

Summary: this document contains a detailed description of mobility
services available on OXO Connect. This includes useful information to
deploy an IBS DECT, PWT, IP-DECT or xBS infrastructure, the descrip-
tion of associated base stations and handsets, and necessary informa-
tion to implement OpenTouch Conversation clients.
Note:
This document does not cover VoWLAN.
[6] OXO Connect Expert Documentation: VoIP services 8AL91205xxxx

Summary: this document describes VoIP protocols supported by OXO
Connect (such as SIP), configuration procedure of private or public ac-
cess through IP links, as well as dimensioning and maintenance basic
information.
[7] OXO Connect Expert Documentation: Private networks 8AL91206xxxx

Summary: this documentation gives a description of architectures and
protocols (such as SVPN, QSIG) supported for a private network, a de-
scription of ARS, metering, clock synchronization, and the configuration
procedure of accesses.
[8] OXO Connect Expert Documentation: General applications 8AL91207xxxx

This document gives a description of various applications available on
OXO Connect, such as Hotel, Call metering, CTI, doorphones, Network
management center, point-to-point/point to multipoint T0, permanent
logical link, multiple automated attendant, multiple entities, My IC Plugin
for Outlook®, My IC Web, PIMphony Touch.
[9] OXO Connect Expert Documentation: Web-based tool 8AL91208xxxx

Summary: this document describes the web-based tool, which is the in-
tegrated monitoring tool of OXO Connect.
[10] OXO Connect Expert Documentation: OmniTouch Call Center Office 8AL91209xxxx
Summary: this document provides the description and installation pro-
cedure of OmniTouch Call Center Office. The document also includes
presentation and operation of Announcement, Traceability, and a short
description of Agent, Statistics and Supervisor applications.
[11] OXO Connect Expert Documentation: Management tools 8AL91210xxxx

Summary: this document describes the management tool available for
OXO Connect(OMC). The document describes the OMC installation
procedure, the different types of access between OMC and OXO Con-
nect (local, remote, with or without proxy), the software installation pro-
cedure of OXO Connect via OMC and the list of services that can be
managed by OMC.

Chapter 1 Expert Documentation structure
[12] OXO Connect Expert Documentation: Maintenance services 8AL91211xxxx

Summary: this document contains basic information concerning the
maintenance of your OXO Connect. This includes a diagnosis method-
ology in case of system of terminal(s) failure, the list of system messag-
es, procedure to save/restore data, procedure to stop/restart your sys-
tem, to replace CPU, boards and sets.
[13] OXO Connect Expert Documentation: Security 8AL91212xxxx

Summary: this document gives essential information to secure your
OXO Connect. This includes deployment guide for certificate, manage-
ment of passwords, management of accesses to services from
LAN/WAN and network configuration for remote accesses.
[14] OXO Connect Expert Documentation: System services 8AL91213xxxx

Summary: this document gives information about software keys, includ-
ing their complete list. The document also describes operation of OXO
Connect with NTP (as client or server) and the configuration of the em-
bedded DHCP server.
[15] OXO Connect Glossary 8AL91214xxxx

Summary: this document contains a glossary of general telecommuni-
cations terms as well as specific terms related to OXO Connect.
In the present document, cross-references are identified by the number in the first column of the above
table.
Part numbers are given in the last column, where xx corresponds to the language code of the
document.
Outlook is either a registered trademark, or a trademark of Microsoft Corporation in the United States
and/or other countries.

Chapter
2 Overview
OMC is the PC application used to program the OXO Connect system via a local connection (V24 or
LAN) or a remote connection (the PC modem is connected to the OXO Connect integrated modem via
the public network).
Three levels of programming are available using OMC:
• Easy View is used for Wizard configurations, i.e. the essential parameters for starting the system.
• EasyPlus View is used for wizard-type configurations with the extensions offered by the Advanced
key. This key opens a window which is equivalent to Expert View.
• Expert View gives you unrestricted access to all the configuration possibilities.
The Wizard provides easy-to-use system programming, guiding the user step-by-step.

Chapter
3 Installation procedure
3.1 Minimal PC Configuration

• PC requirements: see Microsoft® requirements for Windows version
• Supported operating systems: refer to the Cross Compatibility
• Hard disk: 300 MB (recommended for installation and operation)
• Screen: 1024 x 768 pixels
• 1 mouse
• 1 serial port (connection to OXO Connect for data transfer)
• 1 Ethernet board (IP mode only; not required when there is a V24 serial port connection to OXO
Connect)
• 64K (1 B-channel), or 128K (2 B-channels) PPP-compatible ISDN modem, or V34 modem for
remote access
Note:
Before installing OMC, the framework .NET must be installed.
For Microsoft Windows 8/2012, Microsoft .NET Framework 3.5 needs to be installed before installing OMC. An
internet connection is required for this installation.
To install the Microsoft .NET Framework 3.5:
• Select on your PC the windows Feature available in Control Panel -> Programs and Features / Programs ->
Turn windows Feature on or off.
• For Windows 8: Select the .NET Framework 3.5 check box.
• For Windows server 2012:
1. Select Server Manager -> Manage -> Add Roles and Features wizard
2. Navigate to the Features window
3. Select the .NET Framework 3.5 check box.
In case more information is needed, please contact your local administrator.
3.2 Installing the OMC Software

The OMC software is installed from a CD-ROM.
Install the application by choosing options in the various windows.
When installation is finished, you access the application either:
• By double-clicking on the new icon created on the Windows desktop, or
• By selecting Start -> Program -> PCXTools -> OMC XXX yy.z. The window Welcome to OMC
appears.

Chapter
4 Accessing the System
4.1 System Password

Important:
System Password management policy
Basic rules have to be applied to the different passwords allowing an OMC connection to the system. It is
recommended to change the default Installer password for OMC Expert, Administrator password for OMC
EasyPlus and Operator password for OMC Easy.
General recommendations for good password management are:
• Implement company policy to regularly update all system passwords
• Regularly change passwords
• Avoid the use of simple passwords such as 12345678, 11111111, 00000000, etc.
• Never use a word from the everyday language. Attackers can use special dictionary cracking software
to retrieve these
• Never use a word that is closely related to you:
• Your company name
• Your name
• Your wife’s maiden name
• The name of your children or your pet
• Your favourite hobby, etc.
• Use a different password for each connection level
• Do not disclose passwords to other persons/colleagues
• Never write down your password. The first thing an attacker will do is rummage through your personal
belongings.
The rules to define management passwords are:
• Total length of 8 characters
• At least one lowercase alphabet letter (a-z)
• At least one uppercase alphabet letter (A-Z)
• At least one digit (0-9)
• Special characters are not allowed
The rules to define the operator password are:
• Total length of 8 alphanumeric characters
• At least one numeric character (e.g, “HelloYou” is rejected, “11223344”, “Hello123” are accepted)
• At least two different characters (e.g. “11111111”, “aaaaaaaa” are rejected)
• No sequence of ascending or descending characters (e.g “12345678”, “abcdefgh” are rejected)
• No special character
Administration passwords and default user password must be modified at first OMC connection.
For more information about passwords, refer to the Password Management section of the document
[13].
4.2 Local Access By LAN

The default IP address for the main CPU board is 192.168.92.246 for:

Chapter 4 Accessing the System
• A connection to the LAN port on the main CPU board via a UTP Category 5 5-100 ohm crossover
cable.
• A connection to the switch to which the main CPU board is connected by a direct cable.
The PC IP address and network mask must be compatible with the address of OXO Connect. For
example 192.168.92.1 and 255.255.255.0.
For security reasons, the OXO Connect can be configured with an additional IP address, which is used
only for management.
To configure a management IP address:
1. Navigate to OMC: Hardware and Limits > LAN/IP Configuration
2. Select the LAN Configuration tab
3. Validate the Use Management IP Address check box
4. Enter the Management IP Address
5. Validate
6. Perform a warm reset to take the new address into account
See Local V24 Access For OMC on page 12.
4.3 Local V24 Access For OMC

It is possible to use OMC software to dialog with OXO Connect using a V24 connection. In this case
the network connection is not necessary.
A specific reinforced cable must link the "Config" RJ45 connector on the system CPU to the Com port
of the PC using OMC.
Wiring of the connection cable
RJ45 SUB D 9-point (F)
1 7
2 4
3 3
4 NC
5 5
6 2
7 6
8 8
4.3.1 Installation Procedure

1. Open the OMC software on the PC.
2. Select the Expert mode.
3. Select Comm from the menu toolbar.
4. Select Connect from the dropdown menu. The Communication Path window is displayed.
5. Select Local V24.
6. The system proposes installation of OmniPCX Direct V24. Click on Yes. The Modem options
window is displayed.
7. Click Add. The Installation window is displayed.

8. In the Installation window, check Don't detect my modem. Propose the option in a list and click
on Next.
9. Select the manufacturer.
10.Select OmniPCX Direct V24.
11.Select the Com port used.
12.Click Next.
13.Click Finish.
14.Click Close.
15.Back in OMC, click Comm. The Local V24 box is now enabled and the Com port is displayed.
16.Click Ok and enter the password. It will take a few seconds for the OMC to connect to the system.
4.4 OMC Remote Access By Modem

With remote access, you can use OMC to configure or download an OXO Connect system. This
access can be managed using:
• An ISDN modem able to use ISDN PPP (point to point) protocol at 64K (1 B-channel) or 128K (2 B-
channels)
• A V34 analog modem in Hayes protocol at 33600 bds
The management of these two modems is integrated into OXO Connect.
Important:
The OMC software must be installed on the remote maintenance PC, if Windows Terminal Server is not
being used.
4.4.1 Remote Access By ISDN Modem

4.4.1.1 ISDN Modem Recommended
OXO Connect is equipped with a 64K (1 B-channel)/128K (2 B-channels) ISDN modem using PPP
protocol for remote access through the public network. It provides a point-to-point link accessible via
standard LINUX procedures (PPP, etc.).
For a 64K (1 B-channel) connection, the following modems are validated:
• KORTEX NOVAFAX ISDN 128000/33600 with PPP protocol
• FRITZ ¡X CAPI 2.0 or any standard "FRITZ" modem
• Multitech I Way Hopper MTA 128 ST 128 KBPS ISDN (see note below)
For a 128K (2 B-channels) connection, the following modems are validated:
• OLITEC USB ISDN 128K
• Multitech MTA128ST-RC ML-PPP (see note below)
• Eicon Diva 852 ISDN T/A USB - ISDN BRI ST - 128 Kbits/s
ISDN 64 to 128 KPBS modems handling the PPP protocol are generally compatible and support CHAP
authentication.
Note:
When using the Multitech modem, the authentication method must be set to CHAP. This is the default method for
current firmware versions. For modems with older firmware, you must either update the firmware or activate CHAP
with the AT command AT S58=3.

4.4.1.2 RAS Installation Process

In Windows 7/Vista, you do not need to install new operating system components before configuring a
new access method; the Remote Access Services (RAS) component is installed by default on these
systems.
The sub-sections below describe how to set up the following remote access methods:
• Direct V24 Connection (OXO Connect Direct V24)
• Remote connection via ISDN modem (an example is provided for driver installation)
4.4.1.2.1 V24 Driver Installation Procedure
1. Open the Control panel.
2. Select Phone and Modem Options.
3. Select the Modems tab.
4. Click Add.
5. Check Don't detect my modem; I will select it from the list.
6. Follow the Wizard instructions to install the modem. You will need to choose the COM port that will
be associated with the modem.
7. You may need to reboot the PC to complete the installation.
4.4.1.2.2 Installing the Driver for an ISDN Modem (example)
The following procedure describes how to install a FRITZ modem.
1. Insert the modem installation CD-ROM.
2. Click the FRITZ ¡X PC Capi driver installer icon The wizard is displayed.
a. Indicate the serial port where the modem will be connected.
b. When the install process is complete, reboot the PC.
3. Insert the modem installation CD-ROM. The wizard is displayed
a. Click the FRITZ ¡32 Communication Software installer icon.
b. Select Install and configure.
c. Use the default installation (click on Next in each Wizard screen).
d. At the end of the Wizard mode, check the Install Capi-port driver box.
4. Select AVM ISDN1 Internet (PPP over ISDN).
5. Reboot the PC.
4.4.1.3 Using Remote Access With OMC

1. Launch OMC. The OMC Welcome page is displayed.
2. Select the appropriate menu, as follows:
• the Expert menu, if you are logging in as "installer"
• the EasyPlus menu, if you are logging in as "administrator"
• the Easy menu, if you are logging in as "operator" or "attendant"
3. In the toolbar menu, click Comm.
4. Select Connect. The Communication Path window is displayed.
5. Click Modem direct, then OK.
6. Click Dialing and select AWM ISDN1 Internet (PPP over ISDN).
7. Dial the customer phone number and click OK.
8. Type in the appropriate password according to your user mode, Expert, EasyPlus or Easy.
Note:
The PC and B1 lights on the modem should light up when the connection is established.

The configuration session is open.
4.4.1.4 Remote Access to the ISDN Modem

When an ISDN modem is used, it is necessary to reserve a DDI number in the public numbering plan
to be able to establish remote access.
If no DDI number is available, check whether the system's ISDN modem access is in the default
attendant group (default group). In this case it is not necessary to keep a DDI number.
Remark:
If the modem is not currently in the attendant group, it is useful to set the Reroutdata flag to the value 01H. The
system then automatically recognizes the ISDN service corresponding to the incoming call and looks in the default
attendant group for a data terminal.
4.4.2 Remote Access By The Analog Modem

4.4.2.1 Analog Modem (recommended)
OXO Connect is equipped with an analog modem V34 for remote access through the public network.
This modem provides a point-to-point communication link accessible via standard LINUX protocols
(PPP, etc.).
Its main characteristics are:
• V34 Modem
• Maximum transmission speed: 33600 bds
• Hayes protocol
In the current version of the system, the V34 "US Robotic" modem has been validated. The other types
of modems were not validated.
4.4.2.2 Installation Process of the Remote Access by Analog Modem

Follow the procedures described in the previous paragraphs, but replace the FRITZ modem with the
US Robotics analog modem.
4.4.2.3 Remote Access to the Analog Modem

When the analog modem is used, it is necessary to hold a DDI number in the public numbering plan in
order to be able to carry out remote maintenance.
In the case of no DDI number is available, the access to the modem will be possible only via the
operator transfer.
4.4.3 Operating Mode

1. Open OMC on the remote access PC.
2. Select the Expert menu.
3. Click Comm.
4. Select Connect. The Communication Path window is displayed.
5. Click Modem direct, then OK.
6. There are two ways of establishing a remote connection:
•Select a modem phone book entry in the Used Entry field of the Modem Connection window.
•Click Dialing, select the modem to use ("used modem"), then dial the customer remote access
number in the Number field.
7. Enter the system's default password pbxk1064. It will take a few seconds for the connection to be
established.

4.4.4 Security
In the remote access, the protocol used in the "data link" OSI layer is PPP (Point-to-Point Protocol).
The TCP/IP protocols are used respectively in the "transport" and "network" layers. For each layer,
OXO Connect carries out an access control.
4.4.4.1 Authentication
At the start of the connection (PPP), an account name (system masked) and password (pbxk1064) are
required. This account name is automatically generated by OMC. The password is required by OMC to
establish a direct connection (LAN) with OXO Connect. Any other authentication will be rejected.
4.4.4.2 Firewall
If the system accepts the authentication, the PPP connection will be established, and all the data
packets received on this interface will be filtered according to the following rules:
All the packets are refused except:
• packets bound for OXO Connect FTP server via two TCP ports preset for the PBX configuration by
OMC.
• control packets using the ICMP protocol (Internet Control Message Protocol).
4.5 OMC Remote Access by VPN

As of OXO Connect 2.1, the Cloud Connect solution allows to establish a VPN connection between
OXO Connect and OMC via a VPN gateway hosted in the Remote Service Center.
4.6 Access With Proxy

A proxy server can be added to improve security.
To connect a remote OXO Connect via a proxy server, the login dialog box can request a user account
and password to connect to the proxy server.
Proxy Server
PCX-3
IP network
PCX-2
PCX-1
PC with PC with
OMC application OMC application
Agent Workstations
Figure 4.1: Configuration Example with a Proxy Server
To configure a proxy server:

1. In OMC, select Options > Proxy Parameters from the menu toolbar
The Privileged User Login window opens
2. Enter the Privileged User Password and validate
The Proxy Parameters window opens
3. Enter Proxy parameters:
• No Proxy Used: when this radio button is selected, the proxy server is not used. In this case, all
other fields are disabled
• Use Proxy Server: when this radio button is selected, requests from and to OMC are sent via a
proxy server
• Name/IP Address: enter the name or IP address of the proxy server
• Port: enter the port number used by the proxy server
• Do not use proxy for local address: when this checkbox is validated, requests are not sent
via the proxy server when destination addresses are in the same subnetwork
• User account in Proxy server: enter the user account for the proxy server
• Password: enter the associated password
If the proxy account and password are incorrect in the above parameters, each login dialog box, to
connect a remote OXO Connect, requests the proxy account and the associated password,
To modify the privileged user password:
1. In OMC, select Options > Change Privileged User Password from the menu toolbar
The Change Privileged User Password window opens.
2. Enter the Old Password (after installation, the initial password is OMCAdmin)
3. Enter the New Password
4. Confirm the New Password
Note:
If you forget the privileged user password, the only solution is to uninstall and reinstall the OMC.

Chapter
5 Downloading the Software
OXO Connect is delivered either with:

• A final software including all the countries parameters (OXO Connect Small, Medium, Large
platforms delivered in BTCO mode) or
• A software tool (OXO Connect Compact platform and OXO Connect Small, Medium, Large
platforms delivered in stock mode).
This software tool is installed on the PowerCPU EE/PowerCPU EE C25 and must be updated with a
further system software package (including the specific country parameters) also called country
software, so that the installation is complete. The country software needs to be downloaded using
OMC.
The PowerCPU EE C25 is supported as of OXO Connect R2.2.
Caution:
The OXO Connect software package cannot be installed on a PowerCPU board, regardless of the tool
used: OMC and/or LOLA.
Important:
System Password management policy
Basic rules have to be applied to the different passwords allowing an OMC connection to the system. It is
recommended to change the default Installer password for OMC Expert, Administrator password for OMC
EasyPlus and Operator password for OMC Easy.
General recommendations for good password management are:
• Implement company policy to regularly update all system passwords
• Regularly change passwords
• Avoid the use of simple passwords such as 12345678, 11111111, 00000000, etc.
• Never use a word from the everyday language. Attackers can use special dictionary cracking software
to retrieve these
• Never use a word that is closely related to you:
• Your company name
• Your name
• Your wife’s maiden name
• The name of your children or your pet
• Your favourite hobby, etc.
• Use a different password for each connection level
• Do not disclose passwords to other persons/colleagues
• Never write down your password. The first thing an attacker will do is rummage through your personal
belongings.
For more information about passwords, refer to the Password management section in the document
[13].
5.1 Downloading software for OXO Connect (OXO Connect Small,

Medium, Large platforms delivered in BTCO mode)
To download the software, proceed as follows:
1. Open OMC.
2. Open the Tools folder.
3. Open the OMC-Software Download application.

Chapter 5 Downloading the Software
4. In the Communication Mode window, select the type of download:

• Local
• Modem Direct
• Modem Call Back
• LAN
5. Enter the password pbxk1064.
6. The OMC-Software Download window opens. This window has several areas:
• A parameter setting area:
• Select the directory containing the descriptor file for the new software release. By default this
file is in the BOOT directory.
Use the Delivery file browse button.
• Select the country for the new software release.
Use the ...Delivery drop down menu in the Country & Supplier... area. As an indication, the
PBX field gives the country of the currently used software release.
• Download all the files (by checking the Download all files box) or just those whose Action
field contains the value Install.
• Save the data.
If the Data saving box is checked, the system automatically saves and restores the data after
having swapped over to the new software release.
If the Data saving box is not checked, you must use OMC to save the data before starting
the download. Restore this data after the download/swap is complete.
• Select the ACD/MLAA/SCR service box to download the ACD (Automatic Call Distribution)
and the MLAA (Multiple Automated Attendant) and the SCR (Smart Call routing) optional
components.
• Download the files needed for the Voice over IP features.
Depending on customer needs, check the My IC Phone box and/or 4135 IP Conference
Phone box (the Voice over IP services box is automatically checked).
• Select the language of the voice guides to download.
Click on the Languages button to access the Languages Download window.
• Define a time zone by selecting a city and country.
Click on the Time Zone button to access the Time Zones Download window.
• Define the software swap mode.
In the Software Exchange area, there are two possible choices:
Click on the After OMC disconnect button to swap immediately. The swap starts when you
quit the downloading application.
Click on the Date button and indicate the required date and time for a delayed swap.
Remark:
If you select immediate switching, it will take effect as soon as you quit the download application.
• A read only zone
• The Downloadable Item area allows you to see the different versions of the applications.
• The Action column lists the files to download.
• The bottom part of the window shows download progress. Each downloading and
acknowledgement action produces a message.
7. Click Start to start downloading.

Chapter 5 Downloading the Software
5.2 Downloading software for OXO Connect Compact platform (and

OXO Connect Small, Medium, Large platforms delivered in stock mode)
Remark:
Because the OXO Connect Compact platform does not use internal backup batteries like the other OXO Connect
Small, Medium, Large platforms, it is important not to cut off the cabinet's main power supply during software
download. Any power shut down during the BIOS downloading will damage the PowerCPU EE/PowerCPU EE
C25.
To download the software, proceed as follows:
1. From OMC, connect to the system.
If it is the first connection to the system, a Warning window is automatically displayed.
2. Click on the Download button.
3. Enter the IP address and the password of the PC.
The OMC - Software download window is displayed.
4. In the Delivery file field, select the path to access the system software installed on your PC.
5. Using the ...Delivery drop-down menu in the Country & Supplier... area, select the country where
the system will be installed.
6. Click Start.
When download is complete, the message Session successfully finished is displayed.
7. Click Exit to quit the downloading tool. The system will swap on the new software version and will
be available within a few minutes.
Note:
When available, a new Uboot-loader (similar to the BIOS in previous releases) version in the OXO Connect
Compact software will not be automatically included in the list of items to be downloaded from the system. You
must select and include the new Uboot-loader version manually.

Chapter
6 Download and Swap
6.1 Overview
Download is the feature used to upgrade the software and restore customer configuration (data saving
feature). The Download feature allows installers to download remotely (or locally) the updated
software, avoiding a physical intervention on system hardware (by changing a set of REPROM).
Download is generally associated to the swap feature which substitutes the current running code with
a previously downloaded new version.
The feature includes the following operations:
1. Getting information from the system
This gives OMC the ability to:
• Find out if there is enough space in the system to perform a download
• Detect the services that are installed on the system but not used (no license)
If the free space required is not available, a message is generated to uninstall an unused service
2. Transferring the files of the new software
3. Sending the list of installed services to the system
4. Saving data
5. Swapping: replacement of the current software by the transferred software
6. Restoring data
For more details on download procedures, see Downloading the Software on page 18
6.2 Download
The download session is split into several phases.
1. Login phase: login file transfer into a directory managed by the Session Manager Application (PC
password control, management of direct/guarded access method, ...),
2. Initialization phase (on the PC): system response (login OK/KO, current software version, country
file type, language file(s) currently used, etc..) used by the PC to select the files to download
(download optimization),
3. Information phase (on the PC): the OMC requests information from the OXO Connect (hardware
present, services already installed, licenses).
4. Deletion of any alternative version.
5. Download file(s) phase: files are transferred through the HTTPS protocol and downloaded to the
corresponding directory in the OXO Connect.
6. Installed service information: the OMC sends the list of installed services. This is useful for future
downloads.
7. Swap order transfer:
This file contains the swap programmed time, the list of applications to be swapped and the list of
applications which must be restarted. The download application updates system parameters with
date and time (an immediate swap is possible) and parameters of the swap order file.

Chapter 6 Download and Swap
6.2.1 Download Binaries

The OXO Connect software (with or without the My IC Phone/4135 IP Conference Phone software) can
be downloaded using the OMC software download feature.
To upgrade the OXO Connect system to a new release including the My IC Phone/4135 IP Conference
Phone software, perform your download from the Enterprise Business Portal.
To upgrade OXO Connect systems with the My IC Phone/4135 IP Conference Phone software, validate
the My IC Phone/4135 IP Conference Phone option in the OXO Connect software download window.
To upgrade OXO Connect systems without My IC Phone/4135 IP Conference Phone software, ensure
the My IC Phone/4135 IP Conference Phone option is not selected in OXO Connect software
download window.
To install/upgrade the My IC Phone/4135 IP Conference Phone software, the VoIP component must be
enabled.
Note:
Starting with Release 8.1, LoLa 400/7.1 version or higher must be used.
This version allows to select download of 8082 My IC Phone binaries.
On LoLa, there is no specific option to select for 4135 IP Conference Phone. By default, 4135 IP
Conference Phone binaries are automatically downloaded.
6.3 Swap
For more details on the configuration Swap parameters, see the section Data Saving in document [13].
Software update consists in the substitution of the current running code by a new version previously
downloaded and stored in the mass storage (SD Card).The switchover of the software can be done
immediately after downloading (immediate swap) or delayed and done at a predefined date and time
specified during the downloading operation.
If the restart of the system does not work, the system restarts once more with the initial configuration.
If a download is running when a Swap application starts, the operation aborts.
If a NMC application is running, the Swap application waits until the NMC session is over.

Chapter
7 Importing/Exporting Files
This function is used to import into OXO Connect a data file sent by a customer (or a file previously
exported from an OXO Connect system; for example, a file of collective speed dial numbers with the
extension .CRP).
7.1 Importing data

To import Excel data into OMC, follow the procedure below.
1. Edit the file in Excel.
2. Check the syntax. The name must contain no punctuation, spaces, digits in the first 2 characters, or
more than 15 characters.
3. Copy all the Excel data.
4. In OMC (connected beforehand), select Collective Speed Dial.
5. Copy the file's data into this directory. The system checks the syntax.
6. Click OK to confirm copying of the data.
7.2 Exporting data

To export Excel data from OMC, follow the procedure below.
1. In OMC (connected beforehand), select Collective Speed Dial.
2. Copy the OMC data (to put it onto the clipboard) using the contextual menu.
3. Paste the OMC data (from the clipboard) to an Excel document.

Chapter
8 Managing Tones
The tones definitions used by OXO Connect are target dependent. This chapter describes the tone
definition and the way they can be modified.
Up to R2.x, tones are managed via noteworthy addresses. As of R3.0, the tones played by the system
are described in an XML file. The file can be exported and imported via OMC.
When starting, the OXO Connect loads data dependant on the country for which it is configured. These
data include the description of tones stored in an XML file. The tone definition file corresponding to the
configured country is selected and read to generate the tones.
The XML file named tone_def.xml, stores the characteristics of the frequencies and the composition
of the tones in two distinct sections. The system simply parses it to load all the tones.
The file can be exported via OMC, possibly modified via an XML editor. The updated file can then be
imported via OMC, in order to be reloaded by the system and generate some new tones.
The following sections describe the content of the XML file, the rules to apply when updating the file,
and the way to import/export a tone description file.
8.1 Root section

The XML file is introduced by a root section as follows:
<country country_adaptation="Customizable" country_name="FR" iso_code="FR">
The field country_name indicates the name of the target country.

The field iso_code contains the code iso of the target country.
The field country_adaptation is free and allows to indicate the reasons for updating the file.
8.2 Frequency section

The frequency section gives the list of definitions of all the frequencies used by the tones. Here is an
example of frequency definition:
<freq_def label="FREQ_330_440">
<freq attenuation="-8" frequency="330" />
</freq_def>
A frequency definition is identified by the label attribute, which must be unique. A frequency can be
called in a tone definition (see Tone section on page 25) by this label. The label name must respect
one of the two following formats:
• Dual frequency: FREQ_<frequency1>_<frequency2>, where frequency1 is the first frequency
and frequency2 is the second one
• Mono frequency: FREQ_<frequency1>_<number1>, where frequency1 is the value of the
unique frequency of the definition expressed in Hertz, and number1 is an arbitrary number
Each frequency part specifies an attenuation and the frequency in Hertz. Both fields can be modified.
Frequency definitions can be added, in the limit of 15, or removed, if not used by any tone.
The frequency NIL_FREQ is implicit. It does not appear in the list of frequencies. It can be used by a
tone to indicate a period of silence.

Chapter 8 Managing Tones
8.3 Tone section

The tone section gives a list of tones. Each tone is identified by its attribute id. These identifiers are
known by the system and used to call the tone. They must not be modified. New tones must not be
created (they would not be taken into account) and existing ones must not be deleted (in fact, a
deletion has no impact, because the old definition is maintained internally to guaranty the service
level).
Here is an example of a tone:
<tone add_to_conf="ADD_TO_CONF" add_to_speech="ADD_TO_SPEECH" description="cpsw
red online rec tone" id="I_RED_ONLINE_RECORD_TONE">
<tone_freq duration="200" label="FREQ_440_16" />
<tone_freq duration="200" label="NIL_FREQ" />
</tone>
The two fields add_to_conf and add_to_speech are also two intrinsic characteristics of the tone
and must not be modified. They indicate respectively if the tone has to be added upon a conference or
a conversation.
The description field can be modified by a free text, for example a reminder of the use cases of the
corresponding tone.
A tone is a sequence of one or several frequencies, which is repeated while the tone is played. The
customization of a tone consists in manipulating, adding, removing the different frequencies which
compose it. Each frequency is specified by its identifier in the field label. This identifier must be
defined in the frequency section, except for NIL_FREQ, which can be called without any definition.
Each tone is associated with a duration, given in milliseconds, which can be configured. The particular
value 0 indicates that the frequency is played in an infinite time, In this case, the loop on the sequence
of frequencies is cancelled.
8.4 Importing/exporting tones

The current XML file of tone description can be downloaded via OMC, and consulted/modified in a
textual mode with any external standard XML editor.
To export the tone description file:
1. In OMC, select Import/Export > Import/Export Data
2. Select the Data type: otd Original Tone Description or wtd Working Tone Description
Note:
otd Original Tone Description file is used to maintain the original tone description. It cannot be modified. Only
export is available for this file.
3. Click Export
The file is exported and an event is added into the historic of the OMC tool.
To import the tone description file after update:
1. In OMC, select Import/Export > Import/Export Data
2. Select the Data type: wtd Working Tone Description
3. Click File and browse to the tone descriptions file
4. Click Import
If the file complies with the rules specified in Frequency section on page 24 and Tone section on
page 25, the file is imported and an event is recorded.
5. Warm reset the OXO Connect for the new file to be taken into account

8.5 Appendix: example of file

<?xml version='1.0' encoding='UTF-8'?>
<country country_adaptation="Customizable" country_name="FR" iso_code="FR">
<tones>
<tone add_to_conf="NO_ADD_TO_CONF" add_to_speech="NO_ADD_TO_SPEECH"
description="cpsw not used" id="I_STD_EMPTY_TONE">
</tone>
dial tone" id="I_STD_DIAL_TONE">
</tone>
red dial tone" id="I_RED_DIAL_TONE">
</tone>
ext dial tone" id="I_STD_EXT_DIAL_TONE">
</tone>
red ext dial tone" id="I_RED_EXT_DIAL_TONE">
</tone>
vmu dial tone" id="I_STD_VMU_TONE">
</tone>
red vmu dial tone" id="I_RED_VMU_TONE">
</tone>
lk dial tone" id="I_STD_LK_DIAL_TONE">
</tone>
frw dial tone" id="I_STD_FORWARDED_DIAL_TONE">
</tone>
red frw dial tone" id="I_RED_FORWARDED_DIAL_TONE">
</tone>
busy tone" id="I_STD_BUSY_TONE">
</tone>
red busy tone" id="I_RED_BUSY_TONE">
</tone>
busy tone2" id="I_STD_BUSY_TONE_2">
</tone>
red busy tone2" id="I_RED_BUSY_TONE_2">
</tone>
intr tone" id="I_STD_INTRUSION_TONE">


</tone>
red intr tone" id="I_RED_INTRUSION_TONE">
</tone>
wait tone" id="I_STD_WAIT_TONE">
</tone>
red wait tone" id="I_RED_WAIT_TONE">
</tone>
hold tone" id="I_STD_HOLD_TONE">
</tone>
hold tone" id="I_STD_EXT_HOLD_TONE">
</tone>
red hold tone" id="I_RED_HOLD_TONE">
</tone>
camp tone" id="I_STD_CAMP_TONE">
</tone>
red camp tone" id="I_RED_CAMP_TONE">
</tone>
rg tone int" id="I_STD_RG_TONE_INT">
</tone>
rg tone tel" id="I_STD_RG_TONE_TEL">
</tone>
red rg tone tel" id="I_RED_RG_TONE_TEL">
</tone>
<tone add_to_conf="NO_ADD_TO_CONF" add_to_speech="NO_ADD_TO_SPEECH"
description="cpsw rg tone ext" id="I_STD_RG_TONE_EXT">

</tone>
red rg tone ext" id="I_RED_RG_TONE_EXT">
</tone>
bip tone" id="I_STD_BIP_TONE">
</tone>
valid tone1" id="I_STD_VALID_TONE1">
</tone>
</tone>
</tone>
custo tone" id="I_STD_CUSTO_TONE">
</tone>
book tone" id="I_STD_BOOK_TONE">
</tone>
conf tone" id="I_STD_CONF_TONE">
</tone>
red conf tone" id="I_RED_CONF_TONE">
</tone>
disa tone" id="I_STD_DISA_TONE">
</tone>
red disa tone" id="I_RED_DISA_TONE">
</tone>
warn tone" id="I_STD_WARN_TONE">


</tone>
mult purpose1" id="I_STD_MULT_PURPOSE1">
</tone>
online rec tone" id="I_STD_ONLINE_RECORD_TONE">
</tone>
red online rec tone" id="I_RED_ONLINE_RECORD_TONE">
</tone>
stut dial tone" id="I_STD_STUTTER_DIAL_TONE">
</tone>
add member tone" id="I_STD_ADD_MEMBER_TONE">
</tone>
del member tone" id="I_STD_DEL_MEMBER_TONE">
</tone>
</tones>
<frequencies>
</freq_def>
</freq_def>
</freq_def>
</frequencies>
</country>

Chapter
9 Managing Voice Prompts
9.1 Introduction
OMC offers the facility to import, export and save audio files containing on-hold music, automated
attendant voice prompts, pre-announcement messages and Automatic Call Distribution voice
messages. This chapter describes audio file management.
Note:
In this chapter and in the OMC tool, the phrase "voice prompts" is sometimes used to refer to all kinds of audio
files.
The multi-entities feature allows a PCX to be shared by up to four groups of users. This feature allows
each entity to have their own Music on Hold, and voice messages.
The configuration starts by associating each user to an entity.
By default all users are associated to Entity 1. For more information about entities, refer to the Entities
section of the document [8].
9.2 Individual types of audio file

The following categories of audio files are used by the OXO Connect system:
• On-hold music
• Automated attendant voice prompts
• Pre-announcement messages
• Automatic Call Distribution voice messages
Externally recorded, custom audio files can be used for all of the above. The import and export of these
audio files are described in the sub-sections below.
9.2.1 On-hold music

On-hold music is the music played to an external phone set which has been put on hold during a call.
Three options are available:
• Default Music: This is the standard music provided by the system.
• Tape: This is music from an audio source (such as a cassette tape player) connected to the audio-
in connection of the system's CPU board.
• Recorded Music: This is music from a custom audio file (with .wav extension) stored in the system.
With regard to the last option, the OMC tool allows you to transfer a custom audio file containing on-
hold music to or from the system. You can therefore import an audio file to the system from your PC, or
export an audio file from the system to your PC. The path to the required screen within OMC is:
System Miscellaneous > Messages & Music > Music on Hold
For information on how to use this screen, refer to the OMC Help.
Note:
In order to transfer audio files, OMC must be in online mode (connected to the system) - the transfer option is not
available in offline mode. Also, this option is only available when using OMC in Expert mode.
The duration of the musical sequence in an audio file can be up to 10 minutes (the actual maximum
duration depends on your licence). A request to transfer to the system an audio file that exceeds this
duration will be refused.

Chapter 9 Managing Voice Prompts
A custom audio file for on-hold music must be a .wav file. No other audio file format is accepted. The
file must also satisfy one of the following audio encoding requirements:
Encoding Type Bits Per Sample Sample Frequency Channels
PCM 4 8 kHz Single (mono)
CCITT A-law encoded PCM 8 8 kHz Single (mono)
CCITT µ-law encoded PCM 8 8 kHz Single (mono)
Linear PCM 16 8 kHz Single (mono)
In fact, the system stores the recording as 4-bit PCM. If you provide the audio file in any of the other
encodings listed above, OMC converts the file to the PCM encoding before passing it to the system.
When an audio file is transferred from the system to a PC, OMC converts this file from 4-bit PCM to 16-
bit linear PCM, since PCM cannot be played by standard desktop media players.
9.2.2 Automated attendant

An audio file can be provided for each menu and sub-menu of the automated attendant, as well as for
an automated attendant welcome message and goodbye message. All these messages, except the
goodbye message, can exist in two different versions for use during opening hours and closing hours.
The OMC tool allows you to transfer custom audio files containing automated attendant voice prompts
to or from the system. You can therefore import audio files to the system from your PC, or export audio
files from the system to your PC. The path to the required screen within OMC is:
Voice processing > Automated attendant
Note:
A custom audio file for an automated attendant voice prompt must be .wav audio files (no other audio
file format is accepted). The file for must also satisfy one of the following audio encoding requirements:
PCM 4 8 kHz Single (mono)
In fact, the system stores the recording as 4-bit PCM. If you provide the audio file in any of the other
encodings listed above, OMC converts the file to the PCM encoding before passing it to the system.
When an audio file is transferred from the system to a PC, OMC converts this file from 4-bit PCM to 16-
bit linear PCM, since PCM cannot be played by standard desktop media players.

9.2.3 Pre-announcement messages

A pre-announcement message can be played to an external caller before their call is answered (either
before the phone starts ringing or while it is ringing), as a company welcome message, for example.
The system can store up to 20 pre-announcement messages (the maximum number depending on
your license). The durations of the messages are pooled and the total length of all the messages must
not exceed 320 seconds.
The OMC tool allows you to transfer custom audio files containing pre-announcement messages to or
from the system. You can therefore import audio files to the system from your PC, or export audio files
from the system to your PC. The path to the required screen within OMC is:
Subcribers Misc > Preannouncement Messages
Note:
A custom audio file for a pre-announcement message must be a .wav audio file (no other audio file
format is accepted). The file must also satisfy one of the following audio encoding requirements:
In fact, the system stores the recording as 8-bit CCITT A-law or µ-law encoded PCM, depending on the
country. If you provide a 16-bit linear PCM audio file, OMC converts the file to the relevant 8-bit
encoding before passing it to the system. However, you must provide either 16-bit linear PCM or the
required CCITT law encoding, as OMC will not convert between the A-law and µ-law encodings.
9.2.4 Automatic Call Distribution voice messages

There are seven Automatic Call Distribution voice messages, one for each call center action. The
seven messages (with their maximum durations) are:
Voice Message Description Maximum Duration
Welcome Broadcast when the caller arrives in the group. 60 seconds
Waiting 1 Broadcast once, when the caller joins the 60 seconds

queue.
Waiting 2 Continuously broadcast after the first waiting 300 seconds

message.
Deterrence Broadcast when the queue is full. 60 seconds
Closing Broadcast when the caller arrives in the group, 60 seconds

to indicate the group is closed.

Voice Message Description Maximum Duration
Estimated waiting Broadcast to indicate to the caller that they are 60 seconds
time likely to have a certain minimum waiting time be-
fore the call is answered (for example, 'You may
have more than 5 minutes to wait before your
call is answered').
Customer code Broadcast the caller to enter the customer code 60 seconds
In fact, you can store up to 8 such sets in the system, referred to as Automatic Call Distribution groups
1 to 8.
You can create your own voice message messages using recording software available on your PC. It is
also possible to record voice messages from one of the installed telephone handsets, e.g. by recording
Information Messages (MMC handset/Operator/Expert/Voice mail/VMU/List/Select messages 1 to
50/Record).
The OMC tool allows you to transfer custom audio files containing Automatic Call Distribution
messages to or from the system. You can therefore import audio files to the system from your PC, or
export audio files from the system to your PC. The path to the required screen within OMC is:
Automatic Call Distribution > Automatic Call Distribution Voice messages
Note:
A custom audio file for an Automatic Call Distribution voice message must be a .wav audio file (no
other audio file format is accepted). The file must also satisfy one of the following audio encoding
requirements:
In fact, the system stores the recording as 8-bit CCITT A-law or µ-law encoded PCM, depending on the
country. If you provide a 16-bit linear PCM audio file, OMC converts the file to the relevant 8-bit
encodings before passing it to the system. However, you must provide either 16-bit linear PCM or the
required CCITT law encoding, as OMC will not convert between the A-law and µ-law encodings.
9.3 Global management of audio files

This section describes a general method for managing (exporting, importing and saving) audio files
(voice prompts) of all kinds. Therefore, the actions described here apply to all audio file types (on-hold
music, automated attendant voice prompts, pre-announcement messages and Automatic Call
Distribution voice messages).

Note:
Alternatively, the different audio file types can be individually managed as described in Individual types of audio file
on page 30.
9.3.1 General export procedure

In order to export audio files, it is necessary to open the Alcatel-Lucent OMC software in direct
connection and Expert mode. The following procedure is the same for all kinds of audio file, but here
we take the example of a mailbox greeting.
1. Select the Users/Basestations list.
2. Select a subscriber of your choice which already has a personalized mailbox.
3. Click Details.
4. Click Mailbox.
5. Select Option in the Subscriber mailbox window and then select the box Voice prompt -
Personal greeting Transfer and save as. At this stage, it is possible to:
• export the voice prompt
• listen directly to the message (click Play)
• delete it (click Erase)
6. Specify the destination path for the export on your main hard drive (for example, C:/Temp/Prompts)
and the file name.
7. Click Export; at this stage, the system will suggest a file format, either the standard .wav PC format
or the regular ALE International PCM format.
8. The voice prompt is then transferred from the system to the PC; this operation may take few
seconds according the size of the file. The voice prompt will be stored on your drive in one of the
formats ALE International PCM or PCM 16 bit 8 kHz mono, according to your choice.
Note:
If no greeting has been pre-recorded (no customization), the Personal greeting box is grayed out.
9.3.2 General import procedure

The import procedure is the same as the export procedure described above.
You must specify the exact path on your PC where the file to be imported is located. You must then
click on Import. The transfer duration depends on the file size.
Note:
At any time, it is also possible to listen to or erase the audio file (the file present in the system).
9.3.3 Complete save of audio files

All audio files can be globally saved using the following save procedure:
1. Start the Alcatel-Lucent OMC software with a direct or remote connection.
2. Select the menu Comm -> Read All from PBX -> Voice Prompts.
3. Click OK.
4. Wait until the end of the transfer.
5. Save the file selecting File -> Save as.
6. Enter a file name and click OK.
The audio files will be stored at the location selected in the preferences.
The .wav files stored following this procedure are in the format ALE International PCM and can be
listened to or modified only using specific software and Codec.

9.4 System language modification

The languages present in the OXO Connect system are installed during manufacture. They depend on
key (license) ordered.
It is possible to modify the number and range of languages using the software downloading mechanism
in OMC.
Note:
Language modification can also be performed during software downloading for migration to a new software
version.
To modify the range of languages available in the system, follow the procedure below:
1. Start the OMC software.
2. Select the Tools menu.
3. Select Software Download.
4. In the Software Download window, choose the desired version in Delivery file (V19_09, for
example). You must choose a software version to be downloaded, usually the current software
version already installed in the system so that only the languages will be loaded during the
downloading.
5. Click OK.
6. Press the Languages button to display the Languages dialog box, and then modify the order
and/or choice of languages.
7. Click OK.
8. Select the Data saving box (if data saving is not performed, all customer data will be lost after the
swap).
9. Click Start.
The system downloads the different languages and corresponding voice prompts. The new
languages will be available following the download, swap and system reset. All other configuration
parameters will remain unchanged.
Note the following:
• The list of available language can be easily checked using customization mode on dedicated sets
(menu Custom, option, language).
• The default language is always the first one in the list.
• During language downloading, the system does not check if the memory capacity is sufficient for the
number of languages loaded; it is the responsibility of the installer to make sure the system
configuration is appropriate for 4 languages (maximum).
• If the language selected for a particular subscriber is no longer present after downloading, silence
will replace the missing language for that subscriber.

Chapter
10 Services provided
OMC provides a complete set of configuration tools for OXO Connect systems.
Three packages are available:
Package Corresponding views Levels of use (passwords) (1)
OMC Expert Expert View, EasyPlus View, Manufacturer

Easy View
Installer (pbxk1064)
OMC EasyPlus EasyPlus View, Easy View Administrator (kilo1987)
OMC Easy Easy View Attendant (help1954)
The default values of passwords are defined by Installer in System Password on page 11
Expert View offers Wizard-type configuration and Easy/EasyPlus View also offers some Wizard-type
configuration.
The Wizard (or configuration assistant) serves to configure the most commonly used system
parameters; OMC helps configure these parameters using a series of simple questions, with plenty of
guidance and explanation. Indeed, using the default configuration avoids having to program a lot of the
parameters.
For customized installation, there are links to Expert View menus from the pages of the Wizard, flagged
by the "Advanced" and "Details" buttons in EasyPlus View. The configuration assistant is available on
installation and throughout the life of the system.
Expert View gives you unrestricted access to all the configuration possibilities. Besides, a multisite view
can be set in all packages when OXO Connect systems are defined in multisite mode.
Features included Easy EasyPlus Expert
Tools Yes
. Software download Yes
. Batch software distribution Yes
. PhDRelay Yes
. OSC Yes
. Webdiag Yes
Customer/supplier info Yes Yes Yes
Installation Typical Yes Yes Yes
. Business Initial Installation Wizard Yes
. Hotel Initial Installation Wizard Yes

Chapter 10 Services provided
. Wizard for Data Loading Yes Yes Yes
Modification Typical Yes Yes Yes
. Subscribers Yes Yes Yes
. Groups Yes Yes Yes
. System Yes Yes Yes
. Common Speed Dialing Yes Yes Yes
. External Accesses Yes Yes Yes
. Export System overview Yes Yes
Numbering Yes
. Installation numbers Yes
. Default configuration Yes
. Dialing plans Yes
. Features in conversation Yes
. DID number modification table Yes
. Number modification table Yes
. Splitting table Yes
. End of dialing table Yes
Automatic Routing Selection (Automatic routing:

Prefixes, Trunk groups list, Hours, Day groups,
. Yes
Providers/destinations, Authorization codes,
Tone/Pause-MF, ARS Miscellaneous)
. PTN conversion Yes
Common Speed Dialing Yes Yes Yes
Directory Yes
LDAP Connector Yes Yes Yes
Users/Base stations List Yes
Voice Processing Yes

. Voice processing activation Yes
. Automated attendant Yes
. Mailboxes Yes
. Information messages Yes
. General parameters Yes
. Statistics Yes
Time Ranges Yes
Attendant groups list Yes
Hunt groups Yes
Broadcast groups Yes
Pickup groups Yes
Manager-assistant associations Yes
Subscribers Misc. Yes
. Pre-announcement (Overview, Messages) Yes
. Permanent Logical Links (PLLs) Yes
. Fax notification for users Yes
. Generic parameters for SIP phones Yes
. My IC Phone applications Yes
External Lines Yes Yes Yes
. List of accesses Yes
. List of trunk groups Yes
. Remote substitution Yes Yes Yes
. Traffic counters (number of outside calls) Yes
Protocols (analog protocols, private and public

. Yes
ISDN access at levels 2 and 3, ISVPN protocols)
. Analog Protocols Selection Yes

. Incoming call handling Yes
Hardware and Limits Yes Yes Yes
. Main cabinet Yes Yes Yes
. Extension cabinet Yes Yes Yes
. Auxiliary interfaces Yes
. LAN/IP configuration Yes
. Software key features Yes
. Fan Management Yes
. System Limits Yes
Counting Yes
. Counting Yes
. Metering transmission characteristics Yes
. Currency conversion Yes
. Tracking counters Yes
Traffic Sharing and Barring Yes
. Traffic sharing matrix Yes
. COS Rest/Barring matrix Yes
. Rest/Barring tables Yes
. Joining Yes
. Account code table Yes
. Outgoing call duration classes Yes
Network Management Control Yes
. Callback/Authorized callers Yes
. Centralized management Yes
. Select Urgent Alarms Yes

Voice over IP Yes
. VoIP: Parameters Yes
. VoIP: Traffic counters Yes
System Miscellaneous Yes Yes Yes
. Feature design Yes
. Set PCX date and time adjustment Yes
. Password Yes Yes Yes
. Subscribers Password Yes Yes Yes
. System Reset Yes
. DECT/PWT ARI/GAP Yes
. DECT/PWT Frequencies Yes
. Memory Read/Write Yes
. Timer Labels Yes
. Debug Labels Yes
. Other Labels Yes
. Numeric Addresses Yes
. Messages and Music Yes Yes Yes
. Music on Hold Yes Yes Yes
. Mailing messages Yes
. Doorphone signals Yes
. Manual normal/restricted mode Yes
. Software Versions Yes
. Network IP services Yes
Import/Export Yes
. Import/Export Data Yes

. Exporting Labels Yes
. Export Server Certificate Yes
History & Anomalies Yes
. History table Yes
. HW Anomaly Table Yes
Data Saving & Swapping Yes
. Commands Yes
. Date & Time Data Saving Yes
. SW-Downloading Yes
. Terminals Downloading Yes
Call Distribution Services Yes Yes Yes
. ACD setup Yes Yes Yes
. ACD-SCR services Yes Yes Yes
. ACD voice messages Yes Yes Yes
. ACD statistic manager Yes Yes Yes
Multiple Automated Attendant Yes Yes Yes
. MLAA Setup Yes Yes Yes
. MLAA Services Yes Yes Yes
. MLAA Voice messages Yes Yes Yes
Central Services Global Info Yes Yes Yes
WLAN Yes
. Statistics Management Yes
. Statistics File Transfer Yes
IP-DECT Yes
. DAP configurator Yes

. IP-DECT Commands Yes

OXO Connect 3.0 SD ManagementTools 8AL91210USAF 1 en

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

OXO Connect 3.0 SD ManagementTools 8AL91210USAF 1 en

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent OXO Connect

Expert Documentation: Management Tools

3.1 Minimal PC Configuration................................................................................................. 10

4.1 System Password......................................................................................................................11

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 3/42

5.1 Downloading software for OXO Connect (OXO Connect Small,

7.1 Importing data...............................................................................................................................23

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 4/42

8.1 Root section....................................................................................................................................24

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 5/42

1 Expert Documentation structure

table 1.1: Expert Documentation structure

Documentation title Part number

[1] OXO Connect Expert Documentation: General Presentation 8AL91200xxxx

[2] OXO Connect Expert Documentation: Hardware: Platform, interfaces 8AL91201xxxx

[3] OXO Connect Expert Documentation: User services 8AL91202xxxx

[4] OXO Connect Expert Documentation: Voice mail 8AL91203xxxx

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 6/42

Documentation title Part number

[5] OXO Connect Expert Documentation: Mobility 8AL91204xxxx

[6] OXO Connect Expert Documentation: VoIP services 8AL91205xxxx

[7] OXO Connect Expert Documentation: Private networks 8AL91206xxxx

[8] OXO Connect Expert Documentation: General applications 8AL91207xxxx

[9] OXO Connect Expert Documentation: Web-based tool 8AL91208xxxx

[11] OXO Connect Expert Documentation: Management tools 8AL91210xxxx

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 7/42

Documentation title Part number

[12] OXO Connect Expert Documentation: Maintenance services 8AL91211xxxx

[13] OXO Connect Expert Documentation: Security 8AL91212xxxx

[14] OXO Connect Expert Documentation: System services 8AL91213xxxx

[15] OXO Connect Glossary 8AL91214xxxx

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 8/42

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 9/42

3.1 Minimal PC Configuration

3.2 Installing the OMC Software

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 10/42

4 Accessing the System

4.1 System Password

4.2 Local Access By LAN

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 11/42

4.3 Local V24 Access For OMC

RJ45 SUB D 9-point (F)

4.3.1 Installation Procedure

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 12/42

4.4 OMC Remote Access By Modem

4.4.1 Remote Access By ISDN Modem

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 13/42

4.4.1.2 RAS Installation Process

4.4.1.3 Using Remote Access With OMC

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 14/42

The configuration session is open.

4.4.1.4 Remote Access to the ISDN Modem

4.4.2 Remote Access By The Analog Modem

4.4.2.2 Installation Process of the Remote Access by Analog Modem

4.4.2.3 Remote Access to the Analog Modem

4.4.3 Operating Mode

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 15/42

4.5 OMC Remote Access by VPN

4.6 Access With Proxy

To configure a proxy server:

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 16/42

8AL91210USAF - Ed. 01 - July 2018 - Expert Documentation: Management Tools 17/42

5 Downloading the Software