OXOCXTE300EN

OXO CONNECT - R6.
0 MD1
STARTER - EDITION 12
PARTICIPANT'S GUIDE
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
Proprietary Ownership Declaration
I agree not to copy, produce, reproduce, transfer, distribute, decode and/or modify any
ALE material (including any and all documentation, manuals, software presentation,
student book and software files) made available and/or used as part of the ALE training.
I acknowledge that sharing of any kind of courseware and media used are strictly forbidden
without approval from ALE Training Services.
I represent and warrant that I will not use or not permit to use the courseware and\or
educational tools supplied by ALE to provide trainings in a private capacity or for my
employer or any third party.
I also acknowledge and agree that ALE owns and reserves all copyright in and all other
intellectual property rights relating to the ALE training material (including courseware and
all associated documentation) provided during the training.
I understand that any breach or threat of breach of the above shall entitle ALE to injunctive
and other appropriate equitable relief (without the necessity of proving actual damages),
in addition to whatever remedies ALE may have at law.
Furthermore, I acknowledge and agree that ALE will be entitled to cancel immediately any
and all of my Certifications in case of any breach of the above.
Maintenance – eBook
The eBook is available on the Knowledge Hub training platform. Internet access is required
to download the eBook.
Participants should be informed that they must bring their laptop for the classroom or
virtual session.
In case of issue for downloading the eBook, the user can open a ticket with the ALE
Welcome Center for assistance.
ALE technical support will be provided on an "AS IS" and "AS AVAILABLE" basis without
warranty of any kind.
The course step- This training is intended for technicians and
engineers responsible for the installation and
by-step configuration of OXO Connect systems
OBJECTIVES
At the end of the course, you will be able to:
• Install the system.
OXO Connect STARTER • Manage the users and the common
OXOCTE300 telephony features.
• Configure internal and external call
distribution.
• Implement Rainbow.
Duration 3 days • Ensure the first level of maintenance.
The presentations are followed by han

ds-on exercises
ACFE Certification
At the end of this training, don’t forget the ACFE
Certification online exam!
The course step- OXO Connect solution overview
Solution overview, OXO Connect and OXO Connect Evolution
by-step hardware.
Commissioning
Data collection, Start-up and FTR.
OMC
Overview and OMC installation, licenses management.
Initial set-up
Course material OXO Connect default configuration, IP settings.
Alcatel-Lucent Terminals
ALE Terminals, ALE terminals comparison tool, Commissioning of a
Premium IP Deskphone and DECT registration with xBS base stations.
Numbering plans
Description and numbering plans management
The course step- Groups management
Hunting groups, pick-up groups, broadcast groups and
by-step manager/secretary relations.
User settings
Telephony features and user rights.
Voicemail
Overview and user voicemail boxes management.
SIP carrier access

Course material Description and SIP public gateway management.
incoming calls
Call distribution, attendants groups, pre-annoucement and welcome
messages.
outgoing calls
Trunk groups access and barring
The course step- Maintenance
System backups, software download, types of reset and security.
by-step Rainbow
Introducing rainbow, administrators roles, OXO Connect connection
to Rainbow infrastructure and WebRTC configuration.
End of the course
Course material
Training lab environment
OXO Connect
Fully Virtualized (RLAB only, no classroom equipment)
OVERVIEW
Introduction
Remote Lab allows accessing a pool of virtual machines and hardware (when required)
hosted in a data center.
Learners RLAB environment Pods are

independent
of each other
Hardware when
required
POD 1 …
…
Pods have
the same
POD 2 … configuration
V-Class
Remote Lab POD n …
Data Center
Common NAS (Softs, licenses,..)
resources
SIP Simulator Pods have
access to
common
resources
How to connect to the Rlab portal and use it? Click HERE to download the user guide.
Training platform
POD 1 to n
Network 192.168.1.X
Pods common resources

Network 10.20.30.x
Client
192.168.1.254
PC
NAS: softs, licenses, …
SIP simulator 10.20.30.254 OXO
Connect
Data
Center
RLAB Dashboard
Session number / course ref / pod number
Access using RDP

session (Remote
Access to a web console desktop connection)
POD CONFIGURATION
Client PC
This virtual machine is used to perform the labs.
POD x
❑ SIP Softphones are already preinstalled :
• 4 MicroSIP softphones clients for internal users directory numbers: 100, 101, 102, 103 POD
• 2 MicroSIP softphones to simulate public numbers.
• Refer to the SIP simulator presentation for more details
VM PC Client
OXO Connect
Evolution
❑ An IPDSP to be installed, it will be the main softphone to use directory number: 104
❑ A network drive, available in the explorer, connected to the NAS allows you to
download the software to perform the labs (system version, Distributions,
applications...)
Client PC
POD x
• Host name: Client1 POD

• IP Address: 192.168.1.100
• Mask: 255.255.255.0 VM PC Client

• Gateway: 192.168.1.254
OXO Connect
• DNS Server 1: 192.168.1.254 Evolution
Login • Administrator
Password • superuser
OXO Connect Evolution hardware
POD
• IP address: 192.168.1.246
• Mask: 255.255.255.0 VM PC Client

• Gateway : 192.168.1.254
OXO Connect
• DNS Server 1: 192.168.1.254 Evolution
Training lab environment
OXO Connect
Hybrid mode (RLAB + classroom equipment)
Topology
PC Client
8378 DECT
IP-xBS
IP BOX
ALE-30h ALE-20h
POE Switch Hybrid IP/TDM Hybrid IP/TDM 8214 8234 8244
RAP
ALE-2
ALE-300 Rack 1U + Power CPU EE + MIX484
ALE-500 SIP
IP only
IP only
▪ IP BOX used for Starter course

▪ Power CPU used for Advanced course
▪ IP BOX or Power CPU used for other courses
Cloud Connect
Remote Lab FTR/RTR
(SIP Simulator, NAS)
PC Client
POD x
• Host name: Client1 POD

• IP Address: 192.168.1.100
• Mask: 255.255.255.0 PC Client

• Gateway: 192.168.1.254
OXO Connect
• DNS Server 1: 192.168.1.254 hardware
Login • Administrator
Password • superuser
PC Client
▪ Create a network drive to access the NAS hosted in
POD x
the RLAB infrastructure
POD
PC Client
OXO Connect
hardware
▪ Credentials: no login, no password required

OXO Connect hardware
• IP address: 192.168.1.246
POD
• Mask: 255.255.255.0
• Gateway : 192.168.1.254
PC Client
• DNS Server 1: 192.168.1.254
OXO Connect
hardware
OR
SIP Carrier Simulator
OXO Connect
SIP Simulator overview - ITSP1 with one SIP Gateway
POD topology POD P (P is the POD number)

Public numbers
Outgoing call
Incoming call National numbers
PBX users
SIP Simulator
International numbers
Mobile numbers
ITS1 ITSP1
SIP Trunk Group Public Carrier Emergency numbers
PBX P Incoming calls
ITSP2 SIP simulator is hosted in
only
Network 192.168.1.x the RLAB common area
SIP Simulator details Public and Emergency numbers

These numbers are simulated via 2 MicroSIP
clients registered on ITSP1 SIP public
PBX P
ITSP1 SIP Gateway 1 ITSP1 Public gateway
Public numbers:
gateway1.itsp1.com public.itsp1.com
Id: publicP@itsp1.fr
10.20.30.51 10.20.30.50
Id: pbxP password: public
password: alcatel
SIP domain:
SIP domain: Emergency numbers:
sip.itsp1.fr id: urgenceP@itsp1.fr
itsp1.fr
Password: public
Network 192.168.1.x
Network 10.20.30.x
Public and Emergency numbers – MicroSIP clients configuration
On PC Client 1, select the Public and Emergency profiles corresponding to your Pod number
Call to Emergency numbers from your PBX

This SIP user Urgence has several alias (E164 numbers)
and can be called via the following numbers:
112, 15, 17, 18
Call to Public numbers from your PBX

This SIP user Public has several alias (E164 numbers) and can be called via the following numbers:
National numbers Mobile numbers International numbers

Country code: 33,44
3311PN12345 3361PN12345 International call to UK Area number: 1,2,3,4,5, 6,7
3321PN12345 3371PN12345 4421PN12345 PN: your Pod Number on two digits
3331PN12345 Others digits in black are fixed
3341PN12345
3351PN12345
The main number of the SIP user Public is 3321PN12345.

Call to Public and Emergency numbers from your PBX – Examples for POD 3 (PN = 03)
National call (to area 1) Mobile call (to area 6)

public3@itsp1.fr public3@itsp1.fr
Dialed number: Dialed number:
0110312345 0610312345
SIP Trunk Group SIP Trunk Group ITSP1

ITSP1
Public Carrier Public Carrier
PBX 3 Number sent by the PBX: PBX 3 Number sent by the PBX:
+33110312345 +33610312345
International call (to country code 44) Call to emergency number (to 112)
public3@itsp1.fr urgence3@itsp1.fr
Dialed number: Dialed number:
0044210312345 112
SIP Trunk Group SIP Trunk Group ITSP1

ITSP1
Public Carrier Public Carrier
PBX 3 Number sent by the PBX: PBX 3 Number sent by the PBX:
+44210312345 +112 or 112
Call to your PBX
Pbx configuration
POD P POD 1 POD 2 POD 3 POD 4 POD 5 POD 6
PBX installation nb 3321PN41000 33210141000 33210241000 33210341000 33210441000 33210541000 33210641000
DDI table - First external nb 41100 41100 41100 41100 41100 41100 41100
DDI table – Last external nb 41199 41199 41199 41199 41199 41199 41199
Example: 100’s external nb 3321PN41100 33210141100 33210241100 33210341100 33210441100 33210541100 33210641100
Examples for POD 3 (PN = 03)
Call from Public user Call from PBX 3 (loop)

101
public3@itsp1.fr Dialed number:
102 0210341102 or 33210341102
Dialed number:
Number sent by the PBX:
0210341102 or 33210341102
+33210341102
SIP Trunk Group ITSP1
Public Carrier
Number received by the PBX: PBX 3
+33210341102 Number received by the PBX:
ITSP1 +33210341102
Public Carrier SIP Trunk Group
PBX 3
102
SIP OXO config
▪ SIP Gateway
• Name: ITSP1G1
• Target domain name: sip.itsp1.fr
• Local domain name: sip.itsp1.fr
• Realm: sip.itsp1.fr
• Outbound Proxy: gateway1.itsp1.com
• Registrar name: sip.itsp1.fr Public
• DNS A: 192.168.1.254 Carrier SIP Simulator
▪ SIP account (P= POD number 1 to 6)
• Login: pbxP
• Password: alcatel
• Registered username: pbxP
Installation number • 210P41000

DDI subscribers • 41100 to 41199 base 100
DDI Operator group • 41000 base 9
Communication Suite for SMB
OXO Connect
Introduction
OXO Connect is a phone system for
Enterprises and Hotels with up to 300 users
Cloud-based collaboration
Video collaboration.
Everywhere. Secure.
Open to all
On-premise communications
extended through the cloud
Scalable communications
OXO Connect Evolution up to 300 users
LAN, WLAN, IP DECT
LAN switches, Controller-less WLAN Access Points, IP DECT Base Stations
Business Communications
Business phones, business handsets, software phones, 24/7 virtual front door
24/7
High performance mobility Stylish, robust design,

Operational simplicity Customer-focused experience
OXO Connect facilities
Customer welcome company greetings, automated attendant, call routing…
Efficient desktop environment desk sharing, conference, groups…
Wireline DeskPhones digital, IP, SIP, analog
On-site mobility DECT, VoWlan
Off-site mobility Rainbow, OpenTouch Conversation…
Converged voice and data network
Hotel and hospitality features
MyPortal links for ALE employees

Brochure Datasheet OXO Connect • Brochure
Web site • Datasheet
Communication servers
IP Pure IP – 300 users

Hybrid Cloud
IP OXO Connect Evolution
300
Hybrid Hybrid TDM/IP - 300 users

Hybrid Cloud
TDM / IP / UCaas
300
OXO Connect (PowerCPU-EE)
Pure TDM
TDM VOIP optional
TDM
OXO Connect Compact

Scalability “We connect everything”
300 users – Communications – Mobility - Collaboration Analog-Fax-Digital-IP-SIP-CSTA-TAPI-DECT-IP DECT-WLAN-LAN Cloud
Connect
WebRTC Gateway Compact Small Large 150W Evolution

hybrid TDM/IP hybrid TDM/IP hybrid TDM/IP Full IP
OXO Connect
ALE-20h ALE-30h
Hybrid Digital/IP Phones
8088 ALE-2 ALE-3

Analog ports ALE-20 ALE-500 ALE-500 ALE-400 ALE-300
No handset
SIP ports
IP/ALE DeskPhones "Enterprise"
DECT IP DECT
Base Stations 8379 8328 8378 Base Stations Stellar WLAN AP
8214 8234 8244 8254 8262/8262Ex 8158s 8168s
DECT Handsets WLAN Handsets Rainbow apps

Commercial offer and licenses
Wireline Phones Wireless Phones
Customer
Experience Essential/ Enterprise IP Desktop OmniTouch 8105s EGO IP Desktop Extended
Softphone 8135s Softphone 82xx/82xx EX DECT 8158s/8168s/WiFi WLAN
DeskPhones Capacity
Efficient Desktop Professional Greetings

Efficient
Communications PIMphony Rainbow Call Center Office
Universal
Telephony
Hot Desking
Smart Call Routing
License
One Number Service on any phone External Mobility

Powerful
OpenTouch Conversation for iPhone and Android
Mobility Software
Assurance
Communication
Server OXO Connect
Compact
OXO Connect
Small
OXO Connect OXO Connect OV8770 Network
Large EVOLUTION Management Center Rainbow
(webRTC)
LAN Infrastructure Voice-over-WLAN infrastructure

Network
Infrastructure OmniSwitch 6360 OmniSwitch 6560 OmniSwitch 2260 Remote Access OmniAccess WiFi Stellar Access Cloud Connect /
Point Points Fleet dashboard
OXO Connect
OXO hardware: IPBox and PowerCPU EE
OXO Connect Evolution IPBox hardware
IPBox for OXO Connect Evolution
SD card interface (rear side)

Used for backup (optional)
Micro USB USB RJ45 AFU 2 Ethernet ports On/Off button & LEDs
Console port reserved to Auxiliary ETH0: LAN & POE Bi color Led to supervise
factory Functions ETH1: For Instant start up and run,
Management access on connection to the cloud,
site (DHCP, DNS) alarm, …
IPBox installation
OCE can be installed as well as desktop, wall mounted or rack product (1/2 of 19” form factor, 1U)
=
The PoE has to be Osxxx (PoE) OCE
activated on
OmniSwitch side, before
“zerotouch” can be
performed with IP-Box
OXO Connect Evolution: Serviceability
ETH1 can be used to easily start and configure OXO

Connect Evolution
Startup wizard
• First startup wizard (registration)
• Allocate an IP address to ETH0, Proxy/DNS configuration
• Enter directly in the diagnostic tool (WebDiag)
• OMC
Eth0 Eth1
ETH1 has been designed to accept HTTP/HTTPs connection
from a PC in peer to peer with a simple LAN cable LAN
• Eth1 is configured with a fixed IP address and an active DHCP server
• Fixed IP address: 192.168.94.246 ETH0 is connected on the LAN to
• Netmask: 255.255.255.0 provide connection to all services
• Gateway: 192.168.94.1
• DHCP range: 192.168.94.247, 192.168.94.254 •Sip trunks, IP phones, Management tools,
• DHCP lease: 2 hours Cloud connect, Rainbow, etc.
• DNS server: 192.168.94.246 (provided by DHCP)
• A DNS server is also active on this interface. Using string “myipbox.ale” in
the URL or in OMC directly connects to the server
• It can be used to configure IP parameters of Eth0. This URL only allows
configuring OXO Connect Evolution parameters and diagnosing with Webdiag.
An identification is required (installer, operator or manufacturer). No user
applications are allowed on ETH1
Security warning:
Eth1 MUST not be connect on the LAN
No access to Eth0 LAN is allowed from Eth1.
Eth1 can be disabled in OMC.
Eth1 is disabled in case of IP conflict with Eth0
OXO Connect Hardware with PowerCPU EE
OXO Connect Communication platforms with PowerCPU EE
OXO Connect Compact

• Compact rack with a PowerCPU EE
or a PowerCPU EE C25
OXO Connect Small

PowerCPU
• 1U with a PowerCPU EE EE C25
OXO Connect Medium

• 2U with a PowerCPU EE
PowerCPU
OXO Connect Large EE
• 3U with a PowerCPU EE
PowerCPU EE
PowerCPU EE Front panel
Default hardware capacity

• Processor MPC8377 @ 800 MHz
• DDR2 512 MB RAM running at 400 MHz
• LAN Ethernet port 10/100/1000 MB/s
MSDB memory
• 16VoIP resources (1 DSP TMS320C6421) daughter board
• 2 Mbyte NOR Flash Memory for boot loader
• eMMC flash Eprom available on MSDB daughter board
• MSDB is by default equipped with a 8GB eMMC flash memory
• MSDB = Mass Storage Daughter Board
• eMMC = Embedded Multi-Media Card
PowerCPU EE daughter boards
The PowerCPU EE board can be equipped with the following daughter boards:
• AFU-1 (General bell, Doorphone, Audio in, Audio out )
• HSL1 or HSL2 (Module 1 and 2, connection to PowerMex)
• Mini-Mix 2xT0 + 2Z (Only on Compact Edition)
• Armada 32 and Armada 64 (VoIP ressources)
76 DSP channels when using the Armada 64
The maximum number of DSP channels is extended from 60 to 76 when using the Armada 64
• Benefits
• Break the limitation to deploy Private SIP trunk & SIP Trunk applications
• 76 SIP trunks (60 in former release 2.0, 48 in OXO R10.3)
• Pre requisite
• PowerCPU EE
• Capacities according to VoIP Channels mode
OXO CONNECT DSP Number of VoIP channels

Mode
hardware Availability Codecs Total
PowerCPU EE w/o
Always Multi-Codec 16x G711/G729 16
daughter board
+ ARMADA-32
Optional Multi-Codec 48x G711/G729 48
daughter board
Multi-Codec 60x G711/G729 60

+ ARMADA-64
Example settings in OMC for a PowerCPU EE equipped with Armada 64, Optional Multi-Codec 30x G711/G729
daughter board
2 choices are possible: + + 76
• 60 multi-codecs G711/G729 G711 46x G711
• 30 multi-codecs G711/G729 + 46 G711 = 76
PowerCPU EE Slot
PowerCPU EE installation rules

• Whatever the rack, the CPU position is always the CPU slot
1 2 CPU Slot
3 4 5
6 7 8
1 2 CPU Slot
3 4 5
1 2 CPU Slot
Compact Unit with PowerCPU EE
AMIX, MIX and CPU positions in the Compact unit
power
12V-DC
MIX Board
or
AMIX Board
PowerCPU EE
with or without
Mini-Mix
Detachable
cover
CPU Connection
PowerCPU EE alone, without local area network connection
Ethernet crossed cable
PC with
Or OMC
V24 crossed cable
CPU Connection
PowerCPU EE + LANX-16
V24 crossed cable

PC with OMC
Ethernet cable PC with OMC

CPU Connection
PowerCPU EE connected to the customer network
V24 crossed cable

PC with
OMC
Ethernet Cable Switch
Data Network VoIP Network
Management PC with
OMC / Webview
Extension unit installation
OXO Connect with PowerCPU EE multi-cabinet

• Up to 3 racks can be interconnected using HSL links
• The HSL link connects the PowerCPU EE to the PowerMEX board
• The maximum length between the master rack and the extension rack is 5 meters
1 2 3 4 5 6 7 8
TX+ TX- RX+ RX-
PowerCPU EE
PROCESSING UNIT CPU-3m
HSL Link
1 2 3 4 5 6 7 8
HSL link
HSL link
PowerMEX PowerMEX
Data collection
Data collection gathers customer

needs, information on its
Bring all the documents and
software to perform the
ecosystem and the functionalities
installation, such as licenses, to be implemented.
software version, OMC, technical
documentation ... etc
Ecosystem Internet/SIP
Provider/Cloud/Rainbow
IP Configuration
• OXO Connect Evolution:
• Eth0: 192.168.1.246
Management PC
• Eth1: 192.168.94.246 OXO Connect
Evolution
• PC: 192.168.1.100
• DNS: 192.168.1.254
LAN Eth1 RAP
• DHCP phones/xBS: 192.168.1.10 to 69
• Default router address: 192.168.1.254 OmniSwitch
Installation mode
• Business
DECT DECT xBS IP DeskPhones

FTR settings
Data collection •
•
•
Partner fleet reference:
Sub-fleet reference:
Installation ID:
System passwords
Accounts Passwords
Attendant Letacla1
Administrator Qwerty12
Installer Alcatel1
Download Oxopb123
Settings NMC (omnivista) Pbxnmc12
ACD Acdc1064
Users 142535
Alcatel-Lucent terminals
• 4 IP Deskphones
• 1 DECT xBS basestation - dynamic configuration
• 1 DECT handset
Numbering plans
Data collection 3 digits numbering plan
Company installation number: 0210P31199
Internal numbering plan:

• Subscribers: 100 to 199
• Main trunk group: 0
• Hunting groups: 500 to 525
• Attendant: 0
• Telephony features directory numbers to modify such as:
Hunting groups, call pick-up, call forwarding…
Settings Public numbering – DDI numbers

• Subscribers: 41100 to 41199
• Attendant: 41100
The company operates in day / night mode - Call distribution differs

between the 2 modes
Groups
Data collection •
•
•
1 Hunting group 501 containing 3 phones.
1 pick-up group containing 3 phones.
1 broadcast group containing 1 phone with « broadcast » right
and 2 other phones with « receive » right.
• 1 manager-secretary relation group.
Paramètres usagers
Change a subscriber directory number
Programmable keys configuration

• Direct call keys
• Call diversion
Settings • Selective diversion
• Automatic call
• External diversion
• Several DDI numbers associated to one subscriber
Call routing on no answer on voicemail or colleague
Voicemail
• 1 user with an answer only mailbox
• 1 user allowed to record conversations and to listen to messages
deposit in real-time.
• Create and delete mailboxes
SIP Carrier information
•
Data collection
SIP Gateway
• Name: ITSP1G1
• Registrar name: sip.itsp1.fr
• DNS A: 10.20.30.254
• SIP account
• Login: pbx1
• Registered username: pbx1
Incoming calls
Settings 2 attendant groups in normal mode
• Group 1: One phone
• Group 2: message 1
• Group 8: default group
Time ranges:
• 8am –7pm: Grp1
• 7pm– 8am: Grp2
General pre-annoucement during ringing with welcome message

Outgoing calls
Data collection • Users can dial 9 to exit
• 1 user will not be authorized
• International calls and special numbers will not be allowed
• Some subscribers will have to go through the Attendant to

access the external line
Maintenance
1 automatic periodic backup to manage
System version update to be planned

Settings
Rainbow
OXO Connect will be connected to Rainbow including the WebRTC
gateway.
A Rainbow company has already been created
An administrator has been identified
• IP gateway: 192.168.1.254
• DNS: 10.20.30.254
• Proxy: 192.168.1.254 :3128
Additional information will be provided by the trainer

OpenTouch Suite for SMB
OXO Connect
System startup
OXO Connect deployment solutions
Cloud Connect solution:

• Auto registration on Cloud Connect
Standard Solution:
OXO Connect
• On-site management with OMC
“Cloud Connect” solution
Deployment summary
First Installation Cloud-based Operations
Always Auto. update software

Unpack/customer LAN connection up-to-date
1 • Plug-and-play: 6 from the Cloud
IP config
Installation Id
Web-based
2 Auto. Connection to the Cloud 5 Analytics, Inventory
for entire fleet
On-site or Remote
Software and license
3 auto. download from the Cloud
4 Management management
Console
Firewall-friendly
“Standard” Solution
Deployment summary
First Installation
• On-site management
1 • Install OMC
Management
Console
2 • Connect with the OCE default IP address:

• 192.168.92.246
3 • Upload the software in the OCE
4 • Upload the 2 Licences in the OCE

• .msl & .csl
Start & Stop the system
OXO Connect Evolution: Serviceability
ETH1 can be used to easily start and configure OXO
Connect Evolution
Startup wizard
• First startup registration (FTR*)
• Allocate an IP address to ETH0, Proxy/DNS configuration
• Enter directly in the diagnostic tool (WebDiag)
• OMC
Eth0 Eth1
ETH1 has been designed to accept HTTP/HTTPs connection
from a PC in peer to peer with a simple LAN cable LAN
• Eth1 is configured with a fixed IP address and an active DHCP server
• Fixed IP address: 192.168.94.246
• Netmask: 255.255.255.0
• Gateway: 192.168.94.1 ETH0 is connected on the LAN to
• DHCP range: 192.168.94.247, 192.168.94.254 provide connection to all services
• DHCP lease: 2 hours
• DNS server: 192.168.94.246 (provided by DHCP) •SIP gateway**, IP phones, Management tools,
• A DNS server is also active on this interface. Using string “myipbox.ale” in Cloud connect, Rainbow, etc.
the URL or in OMC directly connects to the server
• It can be used to configure IP parameters of Eth0. This URL only allows
configuring OXO Connect Evolution parameters and diagnosing with Webdiag.
An identification is required (installer, operator or manufacturer). No user
applications are allowed on ETH1
*FTR = First Time Registration
**The ISP's SIP network can be connected either to Eth0 or directly
to the dedicated Eth1 connector of the OCE. In the case of Eth1,
Security warnings: this ensures more security between the two networks (subnets,
• Eth1 MUST not be connect on the LAN eth0 and eth1) by enabling data routing between these two subnets
• No access to Eth0 LAN is allowed from Eth1.
• Eth1 can be disabled in OMC.
• Eth1 is disabled in case of IP conflict with Eth0
Start/Stop
Power ON-OFF Button
• Short push (< 5 s) = start / restart

• Long push (> 5 s) = shut down (system stop) + local DC/DC off (behind PoE)
• LOLA mode : PoE ON with start button pushed until the LED is Fast Flashing Green
Power Off of IP Box
• Long press on start button (shutdown) and then disconnect LAN cable (removing PoE) = OFF
Power ON and Start of IP Box
• By connecting LAN cable on ETH0 (PoE = ON) or push of start button

• To be sure to restart if PoE disappears and is back again (auto-restart)
Power bicolor LED (Red-Green) associated to Power ON-OFF Button
• OFF : LAN disconnected or PoE is off

• Fix RED : PoE is ON (5Vdc active) and system in STOP mode
• Fix GREEN : Secondary DC/DC ON (behind PoE)
• Slow Flashing RED : Shutdown of system (Linux)
• Fast Flashing RED : Restart
• Slow Flashing GREEN : SW (Linux) is running
• Fast Flashing GREEN : “LOLA” mode
• After PoE connection with start button pushed
OXO Connect
OCE Start-up & first Time Registration (FTR)
How to
✓ Start & make the OCE First Time Registration (FTR)
Contents
1 Unpack and connect the OXO Connect Evolution ......................................... 2
1.1. Topology ............................................................................................. 2
2 Make the first registration of the OCE (FTR) .............................................. 3
2
Implementation
1 Unpack and connect the OXO Connect Evolution
This lab is to be adapted according to the type of training, in classroom or virtual class.
- In classroom: Realize the lab as follows
- Virtual class: Not possible to perform. It is not possible to connect the PC to the ETH1 port to perform
the registration procedure on Cloud Connect. The OCE is initialized with its default settings. It will be
necessary to use the OMC usual connection procedure in order to change the OCE IP configuration.
1.1. Topology
Connect the ETH0 port of the IP Box to the POE switch.
Connect the ETH1 port of the IP Box to the management PC.
Power on the switch.
Internet/SIP
Provider/Cloud
OXO Connect
Evolution
LA Management
N PC
OmniSwitch
IP
DeskPhones
…
Notes
Wait for the complete start of the OXO Connect Evolution (approximately 3 min), green on / off indicator 1 sec
on / 1 sec off
3
2 Make the first registration of the OCE (FTR)

To register the OCE on Cloud Connect, open the web browser and enter as URL:
- 192.168.94.246 (ETH1)
Install the OXO Connect Evolution with the following settings:

- IP address of the IP Box (ETH0): 192.168.1.246
- Subnet mask: 255.255.255.0
- Gateway address: 192.168.1.254
- Proxy server address: 192.168.1.254 port 3128
- DNS server address: 192.168.1.254
- Partner fleet reference = OXOP (P=corresponds to a Pod number (1 to 6) that will be
provided to you by the trainer)
- Partner sub-fleet reference = TRAINING
- Installation reference = LAB
Configure the PC in DHCP
From an internet browser

type in the url bar:
192.168.94.246
Click on “Register”
Login: installer
Pwd: pbxk1064
At the very first time, the

system asks to put a new
password, put Alcatel1
during the training
4
Enter information
Customer references
provided by the trainer
Example:
Partner fleet reference =
OXOP
(P=corresponds to a Pod number
(1 to 6) that will be provided to
you by the trainer)
Partner sub-fleet reference

= TRAINING
Installation reference = LAB
Enter the parameters of

Basic IP Configuration Web
Proxy according to your 192.168.1.254
environment
192.168.1.254
192.168.1.254
And click on V at the bottom

right
Result
Notes
The system registers in the Cloud
Indication of registration status
Licenses are downloaded from the Cloud
The system is updated
Cloud Connect: More information here:

The system becomes For BP: https://myportal.al-enterprise.com/alebp/a4F5I000000YD5oUAG
accessible remotely via OXO
Connectivity and the Fleet For internal ALE: https://al-enterprise.lightning.force.com/a4F5I000000YD5oUAG
Dashboard
OXO Connect
OMC management tool
Installation OMC
OXO Connect OMC management software is available on the Web site Alcatel-Lucent Enterprise
Alcatel-Lucent Enterprise
https://myportal.al-enterprise.com
• Download then unzip the file

Windows installation • Launch the Setup.exe file
• Follow the instructions
To start OMC software

double-click on OMC icon • xx.x / yy.y represents the software version
located on your desktop
If the OMC is installed for the first time on the PC, Dotnet Framework is a prerequisite
• Dotnet Framework is available in PIMPhony package
• Available on the Alcatel-Lucent MyPortal web site
• Extract “Framework_Net” folder and copy it into the OMC directory
Welcome screen
The OMC welcome screen proposes different management modes
Data Collection and Tools:

•Data Collection executes a Data Collection wizard, do
not require to be connected to an OXO Connect
ToolsMigration from a database software release to
another one Software download of a new version
Software or data download to several systems
Installation Typical :
•Execute an installation wizard to configure
the system at the very first time
•Loading a Data Collection into a system
Modification Typical :
•Access to wizard pages in order to add
modifications to the customer database
Multi site:
Access to the Multi-sites systems
configuration
Expert:
Access to the system configuration manually or by wizard
Connection modes
Connect the PC (serial port) to the CPU (config port) by a V24 DB9 cable
Use a local modem to reach a remote system Call of a remote DID number
Use a local modem to reach a remote system.

After the first connection, the call is released and the OXO
system calls back your modem
Use the local area network to access to the OXO system.

The PC and the OXO system must belong to the same network
In the event of failure, the PC IP address must be controlled!
Authentication
To be authenticated, select the Installer mode, enter the password and press OK
• Default IP Address: 192.168.92.246

• Default Password: pbxk1064 (First connection)
Default Installer
password at first
connection :
pbxk1064 Installer
mode
Server authentication
OMC checks system certificate to

authenticate the server that it
connects to
Self signed or Certification Authority signed certificate
Controlled by flag ‘Server authentication’,enabled by default

• Also possible to manage it on a connection basis
Warning popup is displayed in case of security issue,

non-trusted certificate
If the certificate is not accepted, connection is closed
Applicable whatever type of connection (LAN/WAN)
Connection online icon is displayed in OMC status bar, bottom

right: Green (Authenticated), Red (Unsecure)
Option also made available in the ‘Command line’ mode

Server authentication
Certificate must be
installed in the trusted
root certification
authorities store
OXO Connect checks

certificate names and
validity dates
• Urgent alarm in the history file, can be

In case of invalid reported to OmniVista 8770
certificate, an alarm is
generated • Email sent to the 8770 administrator
In OXO Connect, the

certificates
management is done
through Webdiag
installer session
First connection
Enter Customer Info - Mandatory
It is mandatory for Installer to change all the

default passwords in order to proceed further
Software keys
The software keys are linked to the Main CPU serial
number
When saving the client database, the software keys are

saved
Import of the software key thanks to the system

modification wizard
• The main key f103f217.msl is imported thanks to the first import key
button
• The CTI key f103f217.csl is imported thanks to the import key button
below
• The apply button transfers the software key in the system
• The Details button shows the services opened by the software keys.
Import software keys

•OMC/Modification
typical/System/Software
key
OMC installation wizard
The OMC installation wizard allows to choose between Business or Hotel at the very first installation
(and after a cold reset)
Select the Business

or Hotel Initial
Installation Wizard
OXO Connect
OMC Installation
How to
✓ Install OMC, connect to the PCX
Contents
1 OMC installation ............................................................................... 2
2 Connection to the system .................................................................... 6
2.1. Connection to the system ......................................................................... 6
2.2. Security Alert messages ........................................................................... 7
2.3. Certificate installation ............................................................................ 7
3 Define the passwords ......................................................................... 9
3.1. Administration and default users’ passwords ................................................... 9
4 Enter the customer information .......................................................... 10
4.1. Customer and supplier information ............................................................. 10
2
OMC Installation
1 OMC installation
Install OMC on the administrator PC
The OMC software can be found in the SOFTS OXO CONNECT directory on the PC desktop
In Virtual Class:
In your Rlab Pod, use the console mode to connect to the PC Client VM
(OXOC_PC_CLIENT) and install the OMC (available on the desktop, folder SOFTS OXO
CONNECT)
- OXO Connect default IP address 192.168.92.246
- Password 1st login: pbxk1064
On the client PC
Unzip the OMC file that is
located in the SOFTS OXO
CONNECT directory on the PC
desktop
In the unzipped OMC

directory,
click on setup.exe
select Run as administrator
Select the language for the

set up in the list
Then click on OK
3
OMC Installation
Click on Next to begin the

installation
Select the Destination folder.
And click on Next

4
OMC Installation
Select the target

Country/Distribution Channels
(several countries can be
chosen.
And click on Next
Select the Target Product
And click on Next
Select the language(s) for the

display of the OMC
And click on Next

5
OMC Installation
Click on Install to begin the

installation
Installation in progress….
At the end, click on Finish
6
OMC Installation
2 Connection to the system
Make a connection to the system with OMC in Expert mode with server authentication
2.1. Connection to the system

OMC application
Open the OMC application.

Choose “Expert” menu
Use LAN/WAN connection
Enter the default IP address

192.168.92.246
Check the field “Server

pbxk1064
authentication”
Enter the default installer

password pbxk1064 only used
for the first connection
Password The Installer password is “pbxk1064” when logging for the fisrt time
7
OMC Installation
2.2. Security Alert messages

OMC
Security Alert will be
displayed.
Choose View certificate
Choose View certificate
2.3. Certificate installation

In order to avoid displaying the security alert at each connection, you must install the certificate the 1 st
time.
OMC
Click on Install certificate
8
OMC Installation
Then browse to, “Trusted

Root Certification Authorities”
And click on OK
Click on Finish
Then when import is

successful click on OK
9
OMC Installation
3 Define the passwords
Define the passwords given by the trainer for all the different accounts
3.1. Administration and default users’ passwords

OMC application
Enter the passwords for the
different accounts
The passwords must be

different for each customer!
Passwords can be modified if

necessary in OMC/Security
menu
10
OMC Installation
4 Enter the customer information
Information marked with an * are mandatory.
4.1. Customer and supplier information

OMC application
Enter the customer
information, mandatory at the
first connection to the OXO
And optionally the supplier's

information, ie the contact
details of the technician
performing the installation
11
OMC Installation
OMC is ready to start with the

customer configuration
The icon on the bottom right

shows that you are connected
to the OXO
OXO Connect
OXO Connect IP settings modification
How to
✓ Change OXO Connect IP settings
Contents
1 Change the IP settings of the OXO connect ............................................... 2
2 Change the IP settings of the client PC (OXO_PC_CLIENT) .............................. 4
2
Implementation
1 Change the IP settings of the OXO connect

With the OMC, change the OXO Connect IP settings:
- Address IP: 192.168.1.246
- Subnet mask: 255.255.255.0
- Default router address: 192.168.1.254
- DNS 1 : 192.168.1.254
- DNS 2 : 10.20.30.254
- DHCP range : 192.168.1.10 to 192.168.1.39
- Restart OXO connect
In Virtual Classroom:
Use console mode to connect to the Client PC VM (OXO_PC_CLIENT).
- Once the IP addressing is changed, you will be able to connect to the Client PC VM
with "Remote Desktop Connection" - RDP
OMC/ Hardware and limits/ Lan/IP configuration
Open Lan/IP
configuration
Choose the Boards tab,

and enter a value for the
Main CPU: 192.168.1.246
3
Tab LAN Configuration
Default Router Address:

192.168.1.254
Mask: 255.255.255.0
In the DNS tab:
DNS 1: 192.168.1.254
DNS 2: 10.20.30.254
In the DHCP tab, define

the IP addresses range
for deskphones:
Start: 192.168.1. 10
End: 192.168.1. 39
Click OK & Re-start the OXO Connect

4
2 Change the IP settings of the client PC (OXO_PC_CLIENT)
Change the PC IP settings:

- IP Address: 192.168.1.100
- Subnet mask: 255.255.255.0
- Gateway: 192.168.1.254
- DNS 1: 192.168.1.254
- DNS 2: 10.20.30.254
OXO Connect
Default configuration
Default Configuration
Default configuration available after a system start up

• After a system start up, the boards are recognized one by one from slot 1 then 2 etc. IPBox PowerCPU EE
• Usually, a UAI is inserted in slot 1
All present sets get a default profile

• Programmable keys
• Feature rights
• Call restriction (barring) etc.
• For further details on profiles see the installation manual available on the Business Portal
Also new added station is immediately operational (except IP Phones, refer to auto
provisioning feature)
• A directory number is assigned
• A default profile is also assigned
Default Operator set
•The operator station by default is the 1st equipment of the 1st set board detected
IPBox PowerCPU EE
•Recommendations: connect an Alcatel-Lucent 8039 Deskphone
• (Allow access to operator sessions)
•This station is automatically put into attendant groups 1 and 2 and in the default attendant group 8
Manager/Assistant group (after having carried out an installation wizard)

•Assistant: equipment 2
IPBox PowerCPU EE
•Manager: equipment 3
•Authorized stations: multiline sets
Dynamic Routing
• Users (internal and external calls) directed to the voice mail after 12 seconds
• Operator calls to the default operator group (N°8) after 24 seconds
The Voice Mail accesses are programmed in the default operator group (automated attendant)
Voice mail
• All sets have got a voice mailbox by default
• For the first access the mailbox must be customized
Predefined analogue fax Configuration
• 1st equipment on the 1st Single Line board (SLI)
• Service: Fax 2/3, voice IPBox PowerCPU EE
• Dynamic routing: not active
• Feature rights:
• Intrusion protection
• Camp on protection
• Warn tone protection
• Conference not allowed
Predefined Configuration Hotel Version (after having carried out an installation wizard)
• Phone booth: second equipment on the 1st Single Line board (SLI)
• Administration sets: all digital sets IPBox PowerCPU EE
• Rooms: all analogue equipments except the 1st (fax) and the 2nd (Phone booth)
An internal numbering plan is preset by default, it depends on the country of installation

• Example: extension numbers 100 for the 1st set of the first set interface, 101 for the second etc.
• Attendant call with 9
• Main trunk group seizure 0
• Etc.
Suffixes (features in conversation codes) are also preset by default, they depend on the
country of installation
• Example
• Consultation Camped call by 60
• Resend MF codes by 61
• Etc.
Main trunk group

• The first equipment of the first external accesses interface board is added automatically in the Main trunk
group
• APA
• T0
• T2
• DLT2
How to know the release installed on the OXO Connect

• By MMC Station on phone 8078s/8068s/8038/8039:
• Menu/System/Version
• ONEFR03x/xxx.yyy
Default IP Addresses
• Main CPU: 192.168.92.246
• Subnet mask: 255.255.255.0
• Default gateway: 192.168.92.1
Passwords
The administration passwords must be defined at the first start up of the system
• Total length of 8 characters
• At least one lowercase alphabet letter (a-z)
• At least one uppercase alphabet (A-Z)
• At least one digit (0-9)
• Special characters are not allowed
The passwords management is centralized in the menu: Refer to OMC online help
• OMC/Security/Passwords/Management Password
• Attendant, Administrator, Installer, Download, NMC, ACD
It is strongly recommended
• OMC/Security/Passwords/Subscribers Passwords to comply with the safety
• 4 or 6 digits, strongly advising to use 6 digits for enhanced security requirements described in
the Technical
Communication N°1143
available on the BPWS
Old default Also used

passwords for first
(< Release 10.1) installation
• Installer : pbxk1064
Don’t • Administrator : kilo1987
use • Attendant: help1954

• Download: pbxk1064
anymore • NMC: tuxalize

• Users: 151515
OXO Connect
ALE terminals
Alcatel-Lucent IP & TDM - Essential Business - Enterprise Business
ALE-2 ALE-20 ALE-500 w/o

ALE-30h ALE-300 ALE-400 ALE-500
ALE-3 ALE-20h Handset
ALE-2: 2,8" B&W 2,8" 128 x 64 white 4,3" color touch 480 x 5,5" color touch 720 5,5" color touch 720
Display 3,5" color 320 x 240 3,5" color 320 x 240
ALE-3: 2,8" color backlight 272 x1280 x1280
Narrow Band - Wide Super Wide Band, Audio Super Wide Band, 3D Super Wide Band, 3D Super Wide Band, 3D
Narrow Band - Wide Narrow Band - Wide
Audio Band (IP) 360 Symphonic HD Symphonic HD Symphonic HD
Band (IP) Band (IP)
1 Microphone 3 Microphones 3 Microphones 3 Microphones
1 port Hybride UA et 1 port Hybride UA et

2 ports GE RJ45 - 2 x 2 ports GE RJ45 - 2 x 2 ports GE RJ45 - 2 x
Fast Ethernet RJ45 Fast Ethernet RJ45 (pas 2 ports GE RJ45 - 2 x
SIP 2 ports GE RJ45 USB C USB C USB C
Connectivity (pas de connexion de connexion PC), 1 USB C
ALE-3: 1 x USB-A 1 port ext. 1 port ext. 1 port ext.
PC), 1 port RJ9 port RJ9 BT/Wi-Fi cartridge
BT/Wi-Fi cartridge BT/Wi-Fi cartridge BT/Wi-Fi cartridge
1 x USB C, 1 x USB-A 1 x USB C, 1 x USB-A
BT/Wi-Fi cartridge BT/Wi-Fi cartridge

BT/Wi-Fi cartridge
BT Handset BT Handset
USB-C Local Power Alphabetic Keyboard
Alphabetic Keyboard USB-C Local Power Alphabetic Keyboard
Local Power Supply USB-C Local Power Supply Expansion Module
Expansion Module Supply Expansion Module
Options Wall Mountig Kit Supply Wall Mountig Kit USB-C Local Power
USB-C Local Power Wall Mountig Kit USB-C Local Power
Wall Mountig Kit Alphabetic Keyboard Supply
Supply Customisation Kit Supply
Expansion Module Wall Mountig Kit
Wall Mountig Kit Wall Mountig Kit
Customisation Kit
Customisation Kit Customisation Kit
Available accessories : Refer to the catalog on MyPortal

Premium DeskPhones
8088
Key highlights 100% Touch,

at a glance Video, Android apps
Rainbow connected ◼
Touch screen ◼
Bluetooth ◼
Color screen ◼
Mag. Alphabetic keyboard ◼
Adjustable foot-stand ◼
OXO Connect menus ◼
Wideband Audio ◼
PC port GE

Alcatel-Lucent mobile telephony
(*)
Information workers, Sales force, execs,
Assistants, retail staff, nurses Industry
contractors remote workers
8214 8234 8158 8168 8244 8254 8262 8262EX IP Desktop Any mobile Rainbow OpenTouch
Softphone (remote Smartphone, PC, MAC Conversation
DECT DECT WLAN WLAN DECT DECT DECT DECT Smartphone extension)
Usage On-site On-site On-site On-site Industry Industry Industry ATEX On-site Everywhere Everywhere Everywhere
Long talk time        
Instant messaging, presence  
Enterprise directory Local           
Multiline features           
       
Visual screening, call delegation
One touch call shift          
Alarm key    
Bluetooth headset connectivity    
Isolated Worker Protection   
Push-to-talk 

(*) 8214:
• Only on R6.0 MD1. Compatibility on R5.2 is planned End 2023
• Predefined Messages icon (as 8212) (for IP-xBS/IBS) planned end 2023. (Available with 8328)
IP Desktop SoftPhone
• IP Desktop SoftPhone (IPDSP) allows voice communications

Integrated telephone • Available on following devices
application on Multimedia • PC, tablets, mobiles
device • ≤V12 Emulates a 8068s Premium DeskPhone
• Requires an IPDSP licence = UTL
IPDSP
IPDSP v12 IPDSP v13 (windows client)
SIP Phones
ALE-2/ALE-3
• ALE-2: 2.8” B&W display
• ALE-3: 2.8” color display
• Line Keys with LED, Dual Gigabit ethernet ports, POE (or external power supply)
OmniTouch 8135s OmniSound® audio HD
• SIP conference device

• Up to 20 participants
• « ALE Unite » Application
• Meeting notification Supports ALE Unite App
• Discover nearest device

NFC Bluetooth USB for collaboration
• Meeting management
8105s EGO
• Portable conferencing module, Rainbow companion
Other manufacturer SIP types of set

• SIP Basic
• Open SIP
Analog-SIP Gateway for OCE
Objectives: manage analog calls, Z

services, Fax
3 models Analog-SIP Gateway in

the catalog
• MEDIA5 4102 - 2S = 2 x RJ-11 + 2 x RJ-45 connectors OCE

• MEDIA5 C710 - 4S = 4 x RJ-11 + 2 x RJ-45 connectors
• MEDIA5 C711 - 8S = 8 x RJ-11 + 4 x RJ-45 connectors IP Phones
PoE
Deployment guide PoE LAN Switch
• Go to MyPortal web site Appears in

Requires
one UTL +
4102
OMC as one Open
MyPortal links for ALE employees Open SIP SIP license
Terminal per analog
• Deployment guide Fax Analog phone port
Check out the ALE phones range
Click on the banner below to access the site

OXO Connect
Put in service an IP phone
How to
✓ Put in service an IP phone in static and dynamic mode
Contents
1 Put in service an IP phone in STATIC mode................................................ 2
1.1. Enable the automatic provisioning in the OMC ........................................ 2
1.2. Switch the IP deskphone to STATIC mode .............................................. 3
2 Put in service an IP phone in DYNAMIC mode ............................................. 7
1. Manage DHCP Server ...................................................................... 7
2.1. Enable the automatic provisioning in the OMC ........................................ 7
2.2. Switch the deskphone in DYNAMIC mode ............................................... 8
2
Implementation
1 Put in service an IP phone in STATIC mode
1.1. Enable the automatic provisioning in the OMC
Enable « auto provision » in the Subscribers/Base stations list to allow IP devices

to register onto the OXO Connect
OMC/ Subscribers BaseStations list

Enable temporarily Auto-
Provision
3
1.2. Switch the IP deskphone to STATIC mode
Enter the following settings:

- IP address: 192.168.1.50
- Net mask:255.255.255.0
- Gateway:192.168.1.254
- TFTP address:192.168.1.246
On the set
Disconnect the power
supply of the phone and
reconnect it.
While the set is booting

*
press and #
simultaneously during
phase 2/5 or 3/5.
OR
Press the Settings icon on
the screen and Config

MMI
In the Main Menu select IP
parameters
4
Select IP config
Select IPv4 wired
Select Network Settings

5
At IPv4 mode select Static
And
Enter the
• Phone IP address
• Subnet mask
• Router IP address
Validate
Select System Settings
Enter the NOE IP

Administrator Password
Found in
OMC/Security/Device
administrator password
6
TFTP1: Enter the OXO

Connect IP address
192.168.1.246
Don’t touch TFTP#2 or

TFTP port if it is not
required
Validate and leave the

menu
The deskphone reboots.
At the start up, the OXO

Connect will automatically
assign a directory number
to the deskphone.
The deskphone is now in

service
7
2 Put in service an IP phone in DYNAMIC mode
1. Manage DHCP Server
Manage the OXO Connect DHCP server by entering the following IP address range
for ALE devices:
- Start : 192.168.1.10
- End : 192.168.1.39
OMC/ Hardware and limits / LAN/IP Configuration / DHCP tab

ALU IP Phones : DHCP IP
Range
Enter the IP range

192.168.1.10 to
192.168.1.39
2.1. Enable the automatic provisioning in the OMC
Enable « auto provision » in the Subscribers/Base stations list to allow IP devices

to register onto the OXO Connect
OMC/ Subscribers BaseStations list

Enable temporarily Auto-
Provision
8
2.2. Switch the deskphone in DYNAMIC mode
Switch to DYNAMIC mode on the deskphone
On the set
Disconnect the power
supply of the phone and
reconnect it.
While the set is booting

press * and #
simultaneously during
phase 2/5 or 3/5.
OR
Press the Settings icon on
the screen and Config

MMI
In the main Menu select IP
parameters
9
Select IP config
Select IPv4 wired
Select Network Settings

10
Select Dynamic
Validate and leave the

menu
The deskphone reboots.
At the start up, the OXO

Connect will automatically
assign a directory number
to the deskphone.
The deskphone is now in

service
11
Notes
There are 2 modes for Dynamic: Dynamic and Dynamic Alcatel.
- In the first mode the phone takes an IP address from any DHCP server.
- In the second mode the sets accepts an IP address from an Alcatel system (OXO exclusively.
OXO Connect
IP-DECT xBS classroom installation
How to
✓ Manage IP-DECT feature
Contents
1 LAN/IP Configuration of the OXO Connect ................................................ 2
1.1. Boards IP setting .................................................................................... 2
1.2. DHCP settings ....................................................................................... 2
2 Configure the 8378 DECT IP-xBS ............................................................ 3
2.1. PARI Dect Settings .................................................................................. 3
3 Plug the 8378 DECT IP-xBS on a PoE switch ............................................... 4
3.1. Check the xBS LED status .......................................................................... 4
3.2. Verify the subscribers/Base stations list ........................................................ 4
4 Handset management ........................................................................ 5
4.1. Create some DECT handsets ...................................................................... 5
5 Test by making calls .......................................................................... 6
2
Implementation
1 LAN/IP Configuration of the OXO Connect

Manage the OXO CPU IP address as 192.168.1.246
Manage a DHCP range for the 8378 DECT IP-xBS
Range: 192.168.1.10 to 192.168.1.30
1.1. Boards IP setting
OMC/ Hardware and Limits / LAN/IP Configuration / Boards tab

Enter your system IP@
example 192.168.1.246
Warning
Validate and do not forget to make a warm reset, that can be done after DHCP configuration
1.2. DHCP settings
OMC/ Hardware and Limits / LAN/IP Configuration / DNS-DHCP tab

Enable the integrated DHCP-
Server
Enter the range of @IP

192.168.1.10 to 192.168.1.30
IMPORTANT: N'oubliez pas d'activer Autoprovision dans le menu liste des postes
3
2 Configure the 8378 DECT IP-xBS
2.1. PARI Dect Settings

Enter the ARI number (11 digits in octal)
Reminder the unique ARI number for each OXO is to recover on the eBuy site
It is here given by the trainer
OMC/ Dect / DECT-PWT ARI-GAP / ARI

Enter the ARI number
11000436010 for POD 1

11000436020 for POD 2
11000436030 for POD 3
11000436040 for POD 4
11000436050 for POD 5
11000436060 for POD 6
Note: the ARI number is common for IBS and IP-DECT

4
3 Plug the 8378 DECT IP-xBS on a PoE switch

This lab is only possible in the classroom because you must physically connect the xBS
base station to a PoE switch
3.1. Check the xBS LED status
- Wait few minutes

LED RED
• Step 1: Network initialization, LED blinked 100ms On and 3000ms Off
• Step 2: IP parameters acquisition, LED blinked 100ms On/400 ms Off/100ms On and
3000ms off
• Step 3: Configuration file, LED blinked (100ms On/400 ms Off/100ms)*2 and 100ms On
and 3000ms off
• LED ORANGE:
• Step 4: Software download, LED blinked 100ms On and 3000ms Off
• Step 5: Call server link setup, LED blinked 100ms On/400 ms Off/100ms On and 3000ms
off
• Step 6: Base configuration by call server, LED blinked (100ms On/400 ms Off/100ms)*2
and 100ms On and 3000ms off
• LED Green: Base station is alive, LED blinked 1s On/1s Off
3.2. Verify the subscribers/Base stations list
OMC/ Subscribers/Base stations list

As soon as the base sattion is
operational, it must appear in
the Subscribers/Basestations
list
5
4 Handset management
4.1. Create some DECT handsets

Create some DECT handsets in the subscribers list and register these handsets on the
system
OMC / Subscribers/BaseStations List / Add / IBS-xBS sets / enter the desired number of devices /
Add an IBS-xBS DECT handset
Choose its future directory

number and give it a name
Click on GAP registration

6
Click Assign as soon as the

IPUI appears
Tips
Start registration on 8214/8234/8244/8254/8262 DECT handset
Auto install mode (after having switched back the handset to factory settings)
or Menu\Install\Register\ Enter PIN: 0000 \ Skip all other parameters
The terminal type appears

automatically when registered
5 Test by making calls

OXO Connect
Dialing Plans
Dialing Plans
Public networks Private networks

Internal users
PUBLIC INTERNAL PRIVATE

DIALING PLAN DIALING PLAN DIALING PLAN
Internal
IN CONVERSATION
Public
Restricted Public
OXO Connect/OCE
Private
FEATURES IN
CONVERSATION
Default Dialing Plans
Two types of default Dialing Plans
• Star type: the prefixes to activate a function are preceded by « * » and cancellation prefixes by « # » with 2, 3 or 4
digits
• Standard national type: prefixes with 2, 3 or 4 digits

• Three-digits default Dialing Plan
Modify default Dialing Plan

• Selected in installation wizard
• Path: OMC/Dialing/Default Configuration
Dialing Plans modification
Add, delete or modify a prefix
• OMC\ Numbering\ Numbering Plans
• Select the function in the pull-down menu
• Enter a start and an end prefix in the fields at the top of the window
• Enter a base if required
• Click on Add or modify
Dialing Plans modification
Add, delete or Modify a suffix
• OMC\ Numbering\ Feature in Conversation
• Select the function
• Enter a start and an end suffix
• Click on Add or Modify
Features in
conversation
Dialing Plans bases
Internal numbering plan

Directory number 100 – Base 100
Base = 100
Private numbering plan Public numbering plan

Private directory number 8800 – Base 100 DDI number 41100 – Base 100
Dialing Plans bases for prefixes
Pick up:
0: for handset pickup
1: for group pickup
2: to answer a general call
3: for parked call retrieval
(prefix also available under the name Pickup Parked Call but with base
0)
Forwarding:
0 cancel all call diversion types

Fixed
1 immediate diversion
2 diversion on busy Bases
3 do Not Disturb
4 diversion on paging
5 forward group call
6 join into a group (cancel group withdraw)
7 group withdraw
8 forward Calls type diversion (follow-me)
9 canceling Forward Calls type diversion
10 selective diversion
Installation number
Enter installation number in Dialing menu
• Installation number can also be entered at installation wizard
• It is the main system DDI number
• Enter the installation number without the first digit
• OMC\ Numbering\ Installation Numbers
Installation
numbers
OXO Connect
Setting up the numbering plan
How to
✓ Set up the numbering plan
Contents
1 Programming mode ........................................................................... 2
2 Station call pick-up ........................................................................... 3
3 Users directory numbers ..................................................................... 4
4 Speed dialing numbers ....................................................................... 5
2
1 Programming mode
Set up the prefix 20 to enter in programming mode (change password, set language etc.)
OMC application
Open object
“Numbering
Plans” in OMC
Numbering
menu
Subscriber range
from 200 to 299
already exists.
To avoid
conflicts,
remove these
prefixes: select
the line then
click on
“delete”
Then click on
“ok”
Select
“Programming
Mode” in the
function list.
Put value 20 as
“start” and
“end” value.
Base : empty
Click on “Add”
and then on
“OK”
3
2 Station call pick-up
Set up prefix 21 as set call pick-up.
OMC application
Open object
“Numbering Plans” in
OMC Numbering menu
Select « Pick Up » in the

function list.
Put 21 as « start » and

« End » value.
Base : enter 0 which

corresponds to the set
call pickup function
Click on « Add » and

then on « OK »
4
3 Users directory numbers

Configure directory numbers from 100 to 149 for extension calls
This makes numbers 150 to 199 available for possibly other functions.
OMC application
Open object
OMC Numbering menu
A range of users (from

100 to 199) already
exists.
Select the line

Subscriber
Put value 149 for the

“end”
Base : leave 100. It is

the first station of the
range
Click on “Modify” and

then on “OK”
5
4 Speed dialing numbers

Set up 2 ranges of speed dialing numbers :
1. range from 400 to 499
2. and another range from 600 to 699
OMC application
Open object
OMC Numbering menu
A range prefixes (from

400 to 434) already
exists for secondary
trunk groups.
To avoid conflicts,
delete this Secondary
Trunk Group: click on
the corresponding line
and click on "Delete".
For the same reasons

delete the prefix 60
"Appointment"
Select “Collective Speed
Dial” in the list of
function.
Put 400 as start value

and 499 as End value
Base :0
Click on “Add” and then

Click on “OK”
Range 600 to 699 Do the same for range from 600 to 699 (set base to 100). All the prefixes
beginning by 6 must be deleted before!
Base Always a number from 0 to 2199
OXO Connect
Groups management
Hunt Groups N°540
Parallel Hunt group
Call to 540
A Hunt group is a pool of several
telephones in the same group
that can be called by dialing
one directory number
Incoming calls are Sequential Circular

Calls are routed to
Parallel
routed according to a All calls are each member of All Group
routed to the 1st the group in a
distribution type members ring
group member, 2nd circular rotation simultaneously
member, …etc until the call in
answered
Pick-up groups
When one phone in a pre-defined group is called, any group member can pick
up the call by dialing the interception prefix or pressing a specific soft key
Pick-up group
A
B
A pick-up the call which

was meant for B by
pressing a Dynamic key or
prefix
C calls B
C
Broadcast group
Broadcast group
C broadcasts an announcement on
A the phone speakers of other users
C
receive right
Send/receive right
B
receive right
The noteworthy address PairedGrb allows to pair up to 2 broadcast groups, thus allowing up to 64 members
Manager/Assistant group
Programmable keys
An assistant
screens
calls for Managers and
manager assistants use
multiline
telephone sets
Manager Assistant
• RSL secretary • RSL manager
• Screening • Screening
• Secretary • Manager
supervision supervision
Add-on modules
are useful
OXO Connect
Setting up a hunting group
How to
✓ Set up a hunting group
Contents
1 Create a hunting group ....................................................................... 2
1.1. Create the group ................................................................................... 2
1. Test other types of search ........................................................................ 4
2
Implementation
1 Create a hunting group

Select the hunting group 501.
- Assign the name: Welcome
- Add extensions 101 and 102
- Define a “Sequential” search type
Call 501 to perform your test.
1.1. Create the group
OMC/ Hunting groups
Open the "Hunting groups"

menu
Select the group

501 and click on
“Details”.
Warning: the
group 500 is used
by the voice mail
server!
3
Click on “Add” to
add group
members 101 and
102.
Define the name:

Welcome
Type: Sequential
Click on “OK” to
apply and then
click on “return”.
Final
configuration
Notes
To test your settings, dial the hunting group directory number: 501
4
1. Test other types of search
Test other types of research: Cyclic and parallel.
OMC/ Hunting groups
Edit Group 501
Test Cyclic and Parallel

Types
OXO Connect
Setting up a pick up group
How to
✓ Set up a pick up group
Contents
1 Pick-up group .................................................................................. 2
1.1. Manage the pick-up group ......................................................................... 2
1.2. Create a programmable key “Group pick-up” on each extension. .......................... 4
1.3. Perform the tests ................................................................................... 5
2
Implementation
1 Pick-up group
Configure the Pick-up group “1”
Add extensions 101, 102 and 103
In Virtual Classroom, place the IPDSP 104 in the group and use it to create the “group
pick-up” key.
1.1. Manage the pick-up group
Configure group #1
OMC/ Pickup groups
Open the menu

“Pickup Groups”
Select the group 1

and click on
“Details”.
3
add extensions
101, 102 and 103
into the group.
apply and then
click on “return”.
Final
configuration
4
1.2. Create a programmable key “Group pick-up” on each extension.
Group members will be able to pick up their colleagues' calls with a programmable
"Group pickup" key
Create this key on each deskphone in the group.
Example on extension 101
OMC/ Subscribers – BaseStations list
Select 101 and click on

"Details"
Click on "Keys"
5
Select a blank key
Create the key:
Keytype: Function key
Keyfunction: Pickup
Define a name
Select: Group
Do the same management on the other extensions of the group.
1.3. Perform the tests
Call extension 102, let it ring and pick up the call using the key managed on extension 101.
OXO Connect
Setting up a broadcast group
How to
✓ Set up a broadcast group
Contents
1 Manage a broadcast group ................................................................... 2
1.1. Manage the broadcast group ...................................................................... 2
2
Implementation
1 Manage a broadcast group

Manage Broadcast Group 1 (Call number: *2)
Extension 101 must be able to activate the speakers of extensions 102 and 103 in order
to broadcast voice information to them.
Extensions 102 and 103 will not be able to broadcast, just receive.
Warning: To receive, a deskphone must have a loudspeaker.
In Virtual Classroom there is no deskphone with speaker to test. For configuration, use
IPDSP to receive and microSip to broadcast
1.1. Manage the broadcast group
OMC/ Broadcast group

Select the
broadcast group
menu.
Select the group 1

and click on
“Details”.
3
Add extensions
101, 102 and 103
to the group by
clicking "Add".
Extension 101 will

have “Send” right
Extensions 102
and 103 will have
"Reception" right
The group name is

“workshop”
Click “OK” to
validate
Attribute The members of the group may call the group (send) or be rung (receive) or both
(send/rec).
From extension 101, dial the directory number of the broadcast group *2.
The loudspeakers on extensions 102 and 103 should be activated and you must hear your voice on the
loudspeakers.
OXO Connect
Setting up a manager/secretary group
How to
✓ Set up a manager/secretary group
Contents
1 Create a Manager/secretary group ......................................................... 2
1.1. Create the manager/secretary group............................................................ 2
2
Implementation
1 Create a Manager/secretary group

Create a manager/secretary group, the two sets must be multiline sets.
Manager: 101
Secretary: 102
In Virtual classroom: No test possible. Requires 2 multiline phones.
1.1. Create the manager/secretary group
OMC application
Open “Manager-
Secretary
Relations” menu
Click on “Add”
3
Select the
manager
extension number
in the directory.
Select the
secretary
extension number
in the directory.
Set the keys used

for:
- Screening
- RSL
- Supervision
apply
Screening key The key used to activate the screening can be modified.
Activate the filter key on the manager set – Call the manager.
Activate the filter key on the secretary set – Call the manager.
Test the RSL key on the manager and secretary sets.
Test the manager and secretary supervision key.
OXO Connect
User's Features
Phone sets management
Managing sets:
• OMC\ Subscribers-Basestations List
Phone sets management
Phone set details
To reset the user Set and Voice

mail Password
Note:
The password management for all the users is
centralized in the menu:
OMC/System Miscellaneous/
Passwords/Subscribers Passwords
To control the diversion

status
To set out-of-service
a subscriber
Keys
Keys
•3 types of Keys are available on OXO Connect
• Call keys
• Feature keys
• Resources keys
Direct call Key:
• allows to make automatically a call, just by

pressing the pre-programmed key, without
dialing the number.
• The number programmed in the Calling key can
be changed by the user.
Feature Key:
• allows to activate a function just by pressing the

key
• Available functions: VoiceMail, transfer,
Pickup, Conference….
Keys
On multiline sets, a resource key corresponds to a call
General resources (RGM):

• To manage incoming and outgoing , internal and external calls
Dedicated resources (RSL, RSP, RSB, RSD): Resource

• Local call (RSL): to reach and monitor an internal number Keys
• Special Physical Access (RSP): to select and monitor an access to make an external call
• Special trunk group (RSB): to select a trunk group to make an external call
• DID call key (RSD): to monitor DID calls
Supervision
• To supervise one key of one set for a type of call
Keys management
Keys are configured by the installer according the needs of the customer

• Button Keys
Key Profiles
The default key profile for a phone depends on
• The phone type: ALE-300, ALE-400…

• The mode: key system or PCX mode
• The user type: attendant, manager, secretary or normal
• See Expert documentation/User services/Resource key
Type of subscriber Normal

Mode Single line Key system PCX
Default resource keys 3 « virtual » resource keys 2 RGM 2 RGM
n RSP 2 RSB
Simultaneous management 1 conversation 1 conversation 1 conversation
1 hold (n+1) holds + camp-on 3 Holds + camp-on
1 camp-on
n = number of analogue lines and B channels (within the station key limit)
Dynamic routing
Phone set behavior on unanswered call
• Allows to forward automatically an incoming call (internal or external), according two levels and two timers.
Incoming Call
TIMER 1 TIMER 2
ex: 12s ex: 15s
SET 106 LEVEL 1: LEVEL 2:
SET 102 ATTENDANT
Dynamic routing Automated attendant (lev. 1): If this box is checked, the automated attendant is called
when level 1 dynamic routing is activated (if the level 1 dynamic routing destination
number is the directory number of the group containing the accesses to the voice mailbox )
Phone set dynamic routing Automated attendant (lev. 2): This box is used to chose between the mailbox of the called
party and the automated attendant as the destination of the level 2 dynamic routing (if the
voice mailbox is part of the AA group)
• OMC\ Subscribers-Basestations List Timer 1 for level1: Up to 3276 seconds

• Button: Dyn Rout
Timer 2 for level2: Up to 3276 seconds
Use the level 1 timer: If the timer is not selected but a destination has been entered, the
diversion to this destination will be immediate.
Destination No: Hunt group or User/Subscriber or Common/Collective speed dialing

number (default destination is Voice mail Hunt group)
Use the level 2 timer: if the timer is not selected but a destination has been selected, the
diversion to this destination will be immediate after level 1 timeout
Routing to general level: General level means active Att/OP group
General level and general bell: Active Att/OP group + General bell (General bell is active
for incoming external calls only)
Diversion apply: If "apply diversion" is not ticked, all diversion, including users’ forwarding
(immediate, on-busy, selective…) will be disabled.
Dynamic routing cascading
If a subscriber/group receives a dynamically routed call and if it is not answered, then the new
cascading mechanism enhances the call distribution by implementing receiver’s Dynamic Routing
•Dynamic Routing cascading is supported for subscribers and Hunting groups

•Maximum value allowed: 5
T1 set 101
101
T2 set 101
102 103 104
“Maximum Number of
Dynamic Routing T1 set 103
T1 set 102
Cascading Levels” = 3
Active attendant group
T1 attendant
T2 attendant
106
Default attendant
group
Selective call diversion
It is dependant upon the caller number

• Button: Sel Divers
Used to define The diversion is

for one handset activated only
two lists of in response to a
callers affected call from a
by an subscriber
immediate contained in
diversion this list
Diversion administration
Diversion supervision & management:

• Button: Diversion
Manage the phones features services categories
Authorize or deny the phone features
Protect or not against the phones features
• OMC\ Subscribers-Basestations List\ Details

• Button: Features
Copying settings from one user to another one
Select the user whose settings should be

1 copied
Select parameters to be copied

2 The features for example
Select the destination users for the copy

3 Ability to sort by Address, Number, Type or Name
OXO Connect
Users’ settings and features management
How to
✓ Set up users’ parameters
Contents
1 Direct Call ...................................................................................... 2
2 Call forwarding ................................................................................ 3
3 Dynamic routing ............................................................................... 4
4 Selective diversion ............................................................................ 5
5 Automatic routing ............................................................................. 6
6 Intrusion ........................................................................................ 7
6.1. Allow extension to intrude ........................................................................ 7
6.2. Manager extension protection against intrusion ............................................... 8
7 Forward to external........................................................................... 9
2
Implementation
1 Direct Call
Create a RSL key to call directly another internal extension
In virtual classroom, use the IPDSP.
OMC application
Open object
“Subscribers/Basestatio
ns List”.
Select the user to be

modified and click on
“details”
Click on “Keys” button.
Select a free key
Select “Resource Key”

for the key type.
Select “Local Call” for

the “key function”.
Enter the extension

target number in the
field Dialing
3
2 Call forwarding
Create a feature key diversion to forward calls on busy towards another extension
OMC application
Open object
ns List”.

forwarded and click on
“details”.
Click on “Keys” and

select a free key.
Select “Feature key” for

the key type.
Select “Diversion” in
the function.
Select “On Busy” for the

diversion type.
Enter the Dialing

number of the
diversion.
Give this key a name

with Keylabel, e.g.
to103
Clock on “OK” to apply.

4
3 Dynamic routing
Schedule a dynamic routing after 10 seconds: if the station does not answer internal
calls, after 10 seconds a second station will also be rung
OMC application
Open object
ns List”.
Select the user to

modify and click on
“details”
Click on the button
“Dyn. Rout.”
Modify the timer 1 value

= 10 sec
For the Local Calls, at

Level 1 Use Timer 1 and
enter the Destination
No
Clik “OK” to apply.

5
4 Selective diversion
Program a station that no longer wants to receive calls from 2 other positions. Forward
calls from these 2 stations to another station in the system
OMC Application
Open object
“Subscribers/Basestati
ons List”
Select the user and
click on “details”
Click on the key “Sel

Divers” in the user
In the “Selective
Diversion”table:
Turn the list 1 from
“unused” to “active”
Select “Telephone”
for
Service
Enter the Internal

Diversion Target
number No.
Add 2 extensions to
filter (“Black
list”) Callers’s
Numbers
Click on “Add”
Click on “OK” to apply

6
5 Automatic routing
On the analog phone set up an automatic routing on off-hook to the attendant
In Virtual Classroom: impossible to test. Requires a physical set.
OMC Application
Open object
“Subscribers/Basestati
ons List”.
Select the user to

modify and click on
“details”
Click on the button

“Misc.”
Select “Immediate”
for the parameter
“Hotline”
Enter the operator

destination number 9
Click “OK” to apply

7
6 Intrusion
The user must be able to make telephone intrusions on all the stations that are in
communication, except on the manager station
6.1. Allow extension to intrude

OMC application
Open object
“Subscribers/Ba
sestations List”.
Select the user

to modify and
click on
“details”
Click on
“Features”
In the Feature
Rights first part
validate the
parameter
“Intrusion
Allowed”.
8
6.2. Manager extension protection against intrusion

OMC application
Open object
“Subscribers/Ba
sestations List”.
Select the
manager set to
modify and click
on “details”
Click on button
“Features”
In the Feature
Rights first part
validate the
parameter
“Intrusion
Protection”.
9
7 Forward to external
Only the manager will be allowed to forward his calls to the outside
OMC application
Open object
ns List”.
Select the manager set

to modify and click on
“details”
Click on “Features”
In the Feature Rights

first part validate the
parameter External
Diversion
Validate by OK
And validate the set

modification by OK
again
OXO Connect
Voice Mailbox basic services
Commercial Offer
Voice mail is integrated in CPU with the following feature

• Voice mail box for each set
• 2 accesses
• 4 languages
• 1 hour of stored messages
• Remote customization
• Greeting messages for the subscriber and general mailbox
• Up to 120 seconds
• Conversation recording and distribution lists

• Additional ports (up to 8)
Optional • Additional message storage time and languages
Services • 4 hours
• 30 hours
• 200h
Voice mail initialization
Mailbox initialization
• After first startup
• One mailbox is automatically assigned to each set
• The user mailbox voice guide depends on the set's display language
• The default voice guide of the mailbox is the first system language
• It can be change during the installation wizard or the software download
• One general mailbox accessible from each attendant set
Mailboxes customization
• When the user enters his mailbox for the first time, he must customize it:
• Enter the default users password + record his name and enter his new password
• Password security rule
• The system do not allow users to configure weak phone passwords (000000,123456…)
The first protection against phreaking is

•Change frequently the voice mail password
•Don’t use simple digit sequence for the password
•It is strongly recommended to comply with the safety requirements described in the Technical
Communication N°1143
The modes to access a voice messaging configuration
• Customization & consultation do not use any port.

Consultation in •From the user point of view, this one uses:
•The key Message
APPLICATION Mode •The prefix dedicated to the mailbox application.
•A programmable key “Voice mail”
• The subscriber uses one voice messaging port and DTMF codes
(End Device Number + Password). By default, he calls the first hunt group
from any set by default and manages his mailbox by voice guides.
Consultation in •From user point of view, the user dials:
CONNECTED Mode • Internally, the Directory Number of the port or the hunt group number for the
Voice Messaging system
• Externally, the DID/DDI number assigned to the Voicemail or the Automated
Attendant or the Audiotext.
Management
◼Manage a subscriber’s mailbox from OMC
Standard •This operational mode is typically provided for a
user
Mailbox •It provides all user interfaces related to a mailbox
•This running mode is used in the Hotel version for

Guest Mailbox guest rooms
•It provides a limited user interface to mailbox
Answer Only •This operational mode should be provided for a

user who does not want to receive voice messages
Mailbox (e.g.: long absence)
Voice file ADPCM, 4bits, 8khz, Mono format
Voice file .WAV au format PCM, 16bits, 8khz, Mono format
WAV files adaptation to ADPCM files and inversely

Voice mail features
Message Screening
• Capability to listen to the message being recorded in the mailbox and
immediately answer the call at any moment (as an answering machine
at home)
• Activation by function key: Voice Mail Screening + Secret code

Voice mail features Options
Possibility to do a pause while recording conversations
Only set with softkeys
Conversation Limitation of pause time
recorder
• Possibility to record telephone End of recording
conversations Press on the # key
By going on-hook (hanging up)
If silence during 15 seconds (by default)
• Activation by suffix, dynamic key or
function key: Voice Mail Conversation
Recorder
Conversations recordings deleted after 30 days by default
• Activate the right in the mailbox
parameters / options tab
Automatic Recording Conversation
•A supported set is able to automatically record

external outgoing and incoming calls and store them
to either own or a specific mailbox
•Enabled by the noteworthy address AutoRec

General Mailbox
One General Mailbox

• The general mailbox is accessible through Automated Attendant
• Its only function is to store messages that can be easily rerouted to any extension by the
attendant(s)/operator(s), who are the only persons allowed to access it
• The general mailbox is not attached to a set, and it cannot be customized from a set customization
The operator is the only one allowed to listen to the messages in it

• Deposited messages are indicated on all attendant/operator sets
• The password of the general mailbox is the operator password
To record general mailbox greeting

• OMC/Voice Processing/Mailboxes/General Mailbox
• DHM/Expert/Voice mail/Gen. mailbox
OXO Connect
Voice Mail management basic services
How to
✓ Manage the voice mail unit
Contents
1 User voice mailbox customization .......................................................... 2
2 Mailbox configuration......................................................................... 3
2.1. Answer only mode .................................................................................. 3
2.2. Conversation recording and mailbox screening ................................................ 4
2.3. Remote access to the mailbox .................................................................... 5
3 Mailbox deletion ............................................................................... 6
4 Mailbox creation............................................................................... 7
2
Implementation
1 User voice mailbox customization
Customize the voice mailboxes by recording the greeting messages, the user name and
entering a 6 digits password 14 25 36.
On the set
From the phone set,

press the key “Message”
or the corresponding
prefix “Mailing”
Enter the default users

password of this OXO
(ex.14 25 35)
Enter the new password

chosen by the user 14
25 36
Record the username
Record the greeting

(option).
3
2 Mailbox configuration
Set up the following configuration:
- On one of the sets put its Mailbox in answer-only mode.
- On another set, his voice mailbox can filter messages and record conversations.
- Manage the ability to access the voice mail remotely through the voice mail DDI
number
In Virtual Classroom, use the IPDSP. The message screening test will not be possible.
2.1. Answer only mode

OMC application
Open object
ns List”.

modified and click on
“details”
Click on Mailbox button

- tab Options”,
Choose the mailbox
mode as answer only
Notes
The different modes are:
- Answer only : no possibility to leave a message
- Standard :all user interfaces related to a mailbox
- Guest : limited user interface to mailbox
4
2.2. Conversation recording and mailbox screening
OMC application
Open object
ns List”.
Select another user to
be modified and click
on “details”
Click on Mailbox button
- tab Options”,
Determine the right
Recording of
Conversation allowed
Program a function key
to activate the
Conversation Recording
feature
Select a free key.
the key type and “Voice
Mail: Conversation Rec”
Program a function key

to activate the
Screening feature
Select a free key.
the key type and “Voice
Mail: Screening”
Notes
activation of the feature “Voice Mail: Screening” from the user point of view is password
protected (user password, must be different from the default password !)
5
2.3. Remote access to the mailbox

OMC application
Open the object

OMC “Numbering” menu
Select the "Public

Numbering Plan" tab
and Add voice mail DDI
number
Eg. 41500 base 500
Function Hunting group Choose « Hunting group » in the list

Start 41500 Enter the DDI number
End 41500 Enter the DDI number (same value than “Start”)
Base 500 Choose the hunting group containing the voicemail ports (by default “500”
in France)
Click on “Add” then
“OK” to apply
Allow the remote
consultation
Open object
ns List”.
Select the user to
modify and click on
“details”
Click on “Features” In
the Feature Rights part
3 validate the
parameter “Mailbox
remote consultation”
6
3 Mailbox deletion
Delete the mailbox of one set
OMC application
Open object
ns List”.
Select the user to
modify
then click on “Del

Mailbox” button to
remove the mailbox of
this user
7
4 Mailbox creation
Create again a mailbox for this set
OMC application
Open object
ns List”.
Select the user to
modify
click on “Mailbox”
button
Click on « Yes »to

create the mailbox
associated to the user
OXO Connect
Public SIP gateway management
Topology – Public SIP provider access
• This topology makes it possible to establish communications with all the equipment of
network NGN
• SBC: Control SIP sessions at the SIP provider border
• CE: Router/Firewall/NAT + SIP NAT
• SIP Proxy: Distribution of calls in the SIP network
Access to the • Registrar: SIP Subscriber Authentication
public SIP • Location: SIP Subscriber localization
provider • Gateway: Gateway between SIP and the ISDN network
Gateway
SBC SoftSwitch ISDN

Proxy SIP
DNS Server Registrar / Location
Database
SIP Trunk Group
SIP Internet or @provider.com

CE
Customer Edge Router Trusted Network
sbc.provider.com
Session Border Controller
Compatible SIP Providers (extract)
USA Belgium
• ATC • Belgacom
• Broadvox • Proximus
• Fusion
Italy
UK
• Planetel
• VoIPunlimited
• Voiceflex • VoipVoice
• Gamma Germany
France • Deutsche Telecom
• OBS-Biv • HL komm
• Bretagne Telecom
• OpenIP Austria
• SFR • A1
• Keyyo • Net-Cloud
•…
Portugal
Netherlands
• Portugal Telecom • Infopact
• Vodafone • KPN
Australia Spain
• Exetel • Colt
• Telstra • LCR
For a complete list, refer to the technical communication:

TC1284 Public SIP Trunking Interoperability and Technical Support procedure
Public SIP Trunk Group
To offer the service public SIP Trunk

Group, each OXO Connect must be
connected to the local area network Under software license control
by an external or internal switch
(LANX)
OCE specifics:
The ISP's SIP network can be connected either to Eth0 or
directly to the dedicated Eth1 connector of the OCE. In
the case of Eth1, this ensures more security between
or the two networks (subnets, eth0 and eth1) by enabling
data routing between these two subnets
SIP Trunk Group + ARS
Gateway
SBC SoftSwitch ISDN

LAN Proxy SIP
DNS Server
Registrar / Location
Database
Internet or @isp.com
CE
Customer Edge Router Trusted Network
sbc.isp.com
Session Border Controller
SIP trunks – Level of services
VoIP resources:
•120 with IP Box Fax Over IP is compatible T38 ECM or Fax over G711
•120 Simultaneaous SIP trunks supported
•Up to 76 with POWERCPU EE and a daughter board ARMADA DTMF Signal (RFC2833)
VoIP64 (16 by default)
QoS setting and statistic
Voice CODEC: OPUS, G711, G722, G722.2, • QoS level 3: IP ToS/DiffServ (RFC 2474)
G723.1, G729a • QoS level 2: 802.1 p/q
• QoS Ticket (OmniVista 8770)
•VAD (Voice Activity Detection - Silence suppression –
Comfort noise generation)
•G711/G722 Framing 20 - 30 - 60 ms UDP & TCP
•G723 Framing 30 - 60 - 90 - 120 ms
•G729 Framing 20 - 30 – 40 – 50 - 60 - 90 - 120 ms RFC 4566
•Maximum framing for IP Touch: 60ms • SDP specifications
Direct RTP and RTP Proxy on public or private SIP

Trunk
SIP Gateway configuration example
Main CPU IP@: 192.168.1.246

100 101 102… Installation number: +33210141000
DDI: 41100 to 41199
or
SIP Trunk Group
SBC, Registrar and Proxy IP@
Example: sip.itsp1.fr Gateway
SoftSwitch ISDN
SBC Proxy SIP
LAN DNS Serveur Registrar / Location
Database
Internet or @itsp1.fr
CE: Customer Edge Router Trusted Network
192.168.1.254
SBC Authentication parameters
Login: pbx1
Password: *****
Realm: sip.itsp1.fr
SIP Domain: sip.itsp1.fr
SIP Gateway configuration
Configure the Customer Edge Router as a default gateway

• OMC/Hardware and Limits / LAN/IP Configuration
Customer Edge
Router IP address
Manage the installation numbers

• OMC/Numbering/Installation Numbers
• The default SIP numbering format is the canonical format
• Canonical format is:
• + International code, Intercity code, Installation number + DID
Installation main
phone number
Manage DDI numbers

• OMC/Numbering/Public Dialing Plan
Subscribers and Operator

DDI numbers
Configure the VoIP external lines

• OMC/External lines/List of Accesses
Configure the number of channels

for this access
Declare the accesses

as Public
Must be configured as soon as a
Public SIP gateway is created
Manage a trunk group with the SIP accesses

• OMC/External Lines/list of Trunk Groups, add the VoIP accesses
Add VoIP access to the main

trunk group
Modify the link categories if
necessary
Configure the gateway parameters 1/4

• OMC/External Lines/SIP/SIP Gateway/
• Create a new one
• These infos are given to the client by the public provider
Domain Name
defined by the SIP
provider
Numbers format index makes

reference to the SIP Public
Enter the very next SIP equipment
numbering menu
to which the OXO Connect Server
Canonical, International etc.
must send messages

• OMC/External Lines/SIP/SIP Gateway
• Create a new gateway
• This information are provided to the customer by the Define the
public operator bandwidth
reserved for
voice on IP to the
remote gateway.
The number of
Indicates whether the possible
PCX must register to simultaneous
this SIP gateway communications
depends on this
value

• OMC/External Lines/SIP/SIP Gateway
Indicates if Calling
Line Identification
Restriction
management,
satisfying RFC3325
is supported by the
remote proxy
server
Enable/disable the DNS

feature
Configure the gateway parameters 4/4 Enable/disable the

• OMC/External Lines/SIP/SIP Gateway NAT feature
OCE specifics:
The ISP's SIP network can be
connected either to Eth0 or
directly to the dedicated Eth1
connector of the OCE. In the
case of Eth1, this ensures more
security between the two
networks (subnets, eth0 and
eth1) by enabling data routing
between these two subnets
Associate the Gateway with this VoIP access

• OMC/External Lines/List of Accesses
Associate the
previously configured
Gateway with this
VoIP access
Creating the SIP account associated with the previously configured Gateway settings
• OMC/External Lines/SIP/SIP Accounts
• Right clic\ Add
Enter login and

password for this SIP It is also possible to send the “company
Provider name” only for the non-DDI users and
“extension name” for the DDI users
Verify that
the SIP
gateway is
registered The user can
now make
calls
SIP Trunks profiles Import/Export via OMC
An Import/Export service via OMC of SIP profile facilitates

and accelerates the commissioning of SIP accesses
Select in the list the
Profile to be
Imported/Exported
SIP Trunk Profile
•Once a new SIP provider gets approved by the TSS, the configuration related to
this provider is collected by ALE and put in a file called Profile, available on
MyPortal
•The referenced SIP profile of this provider is mentioned into SIP Carrier
compatibility official document TC1284
SIP Profile content
•A set of a given Gateway parameters

•A set of the related SIP Public Numbering parameters
•A subset of the VoIP Global parameters
•Some specific Noteworthy addresses
Import/Export
•Import/Export via OMC/Import/Export/Import/Export Data/ select the SPF file

of the SIP provider
Refer to TC1994: SIP Easy Connect: SIP Trunk Profile Import/Export

ALE process in relation with public SIP Trunk solutions
Click and refer

to the following TC1284 Public SIP Trunking
Interoperability and Technical
Technical Support procedure
Communication:
SIP trunk easy setup through Cloud Connect
Values
• SIP trunk easy setup thanks to an OXO Webpage

• All technical configuration is done behind the scene (SIP trunk, SIP Gateway, SIP
account, numbering, …)
• Could be used for first installation or later for adding other SIP trunks
How
• In the OXO settings Webpage, the installer selects the SIP profile he wants to use
• The SIP profile is chosen from a list filtered according to the OXO release and the
software target
• Few parameters to fill in the Settings OXO Webpage (SIP trunk, the SIP gateway,
and the SIP account)
Details
• Prerequisite : systems must be Cloud Connected

• Available for OCO and OCE
• The service eases the installation of a public SIP trunk:
• Avoid the installer to download the SIP profile from “My Portal” and to upload it
via OMC
• Avoid the installer to configure many SIP parameters
• Future modifications of SIP trunk can be done via OMC
Sip trunk easy creation
Reminder:
The TC1284 allows you to find
the TC specific to the SIP
provider whose profile is
installed, as well as the non-
profile settings to be
configured manually
Complementary Setup
Complementary Setup needed for completing the OMC configuration

(parameters not managed by SIP Easy Connect)
This is SIP Provider dependent and Country dependent
According to the SIP provider and its

public SIP numbering formats,
OMC/Numbering/Automatic Routing
additional lines in the ARS call OMC/Numbering Plans/Internal
Selection/Automatic Routing
routing table must be created to numbering plan - Add an entry
Prefixes/right click on mouse to
cope with specific public phone toward ARS table
activate the Opt.Parameters
numbers (e.g. short numbers or
emergency numbers)
Complementary Setup – SIP provider dependent – Country dependent
OMC/Numbering/Automatic Routing Selection/Automatic Routing Prefixes

Here below is a typical example for France, comprising four Prefix entries/ranges
User comment
•Line 1: copes with standard phone numbers starting with digit 0 (national / international calls)
•Line 2: copes with all public emergency numbers. The network attribute "emerg" permits the line to point automatically to the system list of emergency numbers. This
list is country-dependent and can be edited via the OMC menu Emergency-> Emergency Numbers
•Line 3 and 4: for external short numbers. Depending on the country, the complete list of short numbers will require one or several ARS lines.
•Line 3: example for France, for short numbers that begin with digit 3 (e.g. 3611, 3900, …)
•Line 4: example for France, for short numbers that begin with digit 1 (e.g. 112, 118712, …)
Complementary Setup
ARS Trunk Groups Lists

To enable voice calls via the ARS system, it’s necessary to have ARS Trunk Groups created via
the OMC/Numbering/Automatic Routing Selection/Trunk Groups Lists
New lines are created after clicking the mouse right button and selecting function “Add”
Index 1 corresponds here to

the trunk group where are
located the VoIP trunks
associated to the SIP Gateway
In any case always refer to the Technical Bulletin dedicated to each provider
« SIP Trunk Solution Provider xxx: Configuration Guideline »
available on MyPortal
OXO Connect
Public SIP Gateway
How to
✓ Configure a public SIP Gateway
Contents
1 Public SIP Gateway description ............................................................. 3
1.1. Topology ............................................................................................. 3
2 Lan IP Configuration .......................................................................... 4
2.1. Main CPU \ VoIP (Master) .......................................................................... 4
2.2. DNS ................................................................................................... 4
2.3. Default Router Address ............................................................................ 5
2.4. DHCP ................................................................................................. 5
3 Phone Numbering plan ....................................................................... 6
3.1. Public Numbering Plan ............................................................................. 6
3.2. Installation number ................................................................................ 7
4 VoIP Trunks and Trunk groups ............................................................... 8
4.1. Program VoIP Trunks as public ................................................................... 8
4.2. Program VoIP Trunk Group ........................................................................ 8
4.3. Adjust VoIP Trunk Group link category .......................................................... 9
5 Public SIP Gateway Settings ............................................................... 10
5.1. Program a New SIP Gateway ..................................................................... 10
5.1.1. Gateway Parameters Details (General Tab) .......................................................... 10
5.1.1. Gateway Parameters Details (DNS Tab) ............................................................... 10
5.1.1. Gateway Parameters Details (DNS Tab) ................................. Erreur ! Signet non défini.
5.1.2. Gateway Parameters Details (Domain Proxy Tab) ................................................... 11
2
Public SIP Gateway
5.1.3. Gateway Parameters Details (Registration Tab) ..................................................... 11

5.1.4. Gateway Parameters Details (Media Tab) ............................................................. 12
5.1.5. Gateway Parameters Details (Identity Tab) .......................................................... 13
5.1.6. Gateway Parameters Details (Protocol Tab) .......................................................... 14
5.1.7. Gateway Parameters Details (Topology Tab) ......................................................... 14
5.1.8. Gateway Parameters Details (Security Tab) .......................................................... 15
5.2. SIP Accounts (Authentication) ................................................................... 15
5.3. Associate the newly created gateway with the VoIP external line ......................... 16
5.4. Check the registration of the OXO Connect on the public SIP provider ................... 17
6 Test ........................................................................................... 18
6.1. Launch a SIP trace with Webdiag ............................................................... 18
6.2. Analyze the trace with Wireshark software ................................................... 19
3
Public SIP Gateway
Implementation
1 Public SIP Gateway description
1.1. Topology
Configure a public SIP Gateway, Refer to document OXOCCTExxxITSPEN “SIP Carrier
Simulator”
Short numbers and emergency numbers are not processed in this exercise, so no ADL
table management
Possibilities to establish calls with:

• Users belonging to the different PBXs
• Note: It is possible to come back on the same POD (loop): to call a user of the same node
• Public users
• Users declared and registered directly on the SIP provider simulator platform
• Emergency numbers
• Declared and registered directly on the SIP provider simulator platform
(e.g. 112, … according to the country)
▪ SIP Gateway
• Name: ITSP1G1
• Registrar name: sip.itsp1.fr
• DNS A: 192.168.1.254
▪ SIP account (P= POD number 1 to 6)
• Login: pbxP
• Registered username: pbxP
4
Public SIP Gateway
2 Lan IP Configuration
Check the IP parameters of the OXO Connect:
- IP address: 192.168.1.246
- Mask: 255.255.255.0
- Router: 192.168.1.254
- DNS: 192.168.1.254
- DHCP range: 192.168.1.10 to 192.168.1.39
2.1. Main CPU \ VoIP (Master)

OMC/ Hardware and Limits/LAN IP Configuration/ Boards
The OXO IP@ is 192.168.1.246
2.2. DNS
OMC/Hardware and Limits/LAN IP Configuration/ DNS
DNS = 192.168.1.254
5
Public SIP Gateway
2.3. Default Router Address

OMC/Hardware and Limits/LAN IP Configuration/ Default Router Address
The router @ IP to reach the
SIP service provider is
192.168.1.254
Reset the OXO to take into account the modification
2.4. DHCP
OMC/Hardware and Limits/LAN IP Configuration/ DHCP
The terminals IP@ are in the
same subnet as the OXO
6
Public SIP Gateway
3 Phone Numbering plan

Define the public numbering plan:
- DDI numbers for subscribers: 41100 to 41199
- Attendant call: 41000
Installation number: 210P41000 (P: Pod number)
3.1. Public Numbering Plan

OMC/Numbering/Numbering Plans/Public Numbering Plan
DDI numbers for subscribers:
41100 to 41199
Attendant call: 41000
Notes
Copy the config to the Restricted Public Numbering Plan if necessary
7
Public SIP Gateway
3.2. Installation number

OMC/Numbering/Installation Numbers
Enter the installation linked to
your pod
210P41000
Here is an example for OXO 1

in France (+33)
+33 (0)2 10 1 41000

8
Public SIP Gateway
4 VoIP Trunks and Trunk groups
4.1. Program VoIP Trunks as public

Create a VoIP access
- 8 channels
- Public network
Put this access in the main trunk group “0”
- Check link categories
OMC/External Lines/List of Accesses/VoIP details

The total number of VoIP
channels available depends on
the hardware configuration of
your OXO Connect and the
license.
Trunk channels: 8
Put VoIP access as Public

trunk
The Gateway index must be

filled in later when the SIP
Gateway is created
4.2. Program VoIP Trunk Group

OMC/External Lines/List of Trunk Groups/Details
Click on Add to add VoIP
accesses to the trunk group
9
Public SIP Gateway
4.3. Adjust VoIP Trunk Group link category

OMC/External Lines/ List of Trunk Groups/Details/Link-Cat.
Adjust the values in order to
allow external calls
Check barring
10
Public SIP Gateway
5 Public SIP Gateway Settings

Enter the parameters given by the SIP provider to the customer
- Name: ITSP1G1
- Target domain name: sip.itsp1.fr
- Local domain name: sip.itsp1.fr
- Realm: sip.itsp1.fr
- Outbound Proxy: gateway1.itsp1.com
- Registrar name: sip.itsp1.fr
- DNS A: 192.168.1.254
5.1. Program a New SIP Gateway
5.1.1. Gateway Parameters Details (General Tab)
OMC/ External Lines / SIP / SIP Gateways / General tab

Program a New Gateway
Parameters Index 1
The index label is ITSP1G1
SIP numbers format index: 1

(For canonical format)
Select: End of dialing table

used
5.1.2. Gateway Parameters Details (DNS Tab)
OMC/ External Lines / SIP / SIP Gateways / DNS tab

Choose DNS A for this specific
SIP provider
DNS A: 192.168.1.254
Don't forget to now configure

the Outbound Proxy:
gateway1.itsp1.com
in the Domain Proxy tab
11
Public SIP Gateway
5.1.3. Gateway Parameters Details (Domain Proxy Tab)
OMC/ External Lines / SIP / SIP Gateways / Domain Proxy tab

The type of IP will be dynamic
after configuring the DNS tab
Target domain name:

sip.itsp1.fr
Local domain name:
sip.itsp1.fr
Realm: sip.itsp1.fr
Outbound Proxy:
gateway1.itsp1.com
The following setting can only
be configured after filling in
the DNS tab!
5.1.4. Gateway Parameters Details (Registration Tab)
OMC/ External Lines / SIP / SIP Gateways / Registration tab
Registration requested
Registrar name: sip.itsp1.fr

12
Public SIP Gateway
5.1.5. Gateway Parameters Details (Media Tab)
OMC/ External Lines / SIP / SIP Gateways / Media tab
Validate RTP Direct
Put the bandwidth at 5

minimum calls in order to
allow external calls
13
Public SIP Gateway
5.1.6. Gateway Parameters Details (Identity Tab)
OMC/ External Lines / SIP / SIP Gateways / Identity tab
Use RFC 3325

14
Public SIP Gateway
5.1.7. Gateway Parameters Details (Protocol Tab)
OMC/ External Lines / SIP / SIP Gateways / Protocol tab

Default settings
5.1.8. Gateway Parameters Details (Topology Tab)
OMC/ External Lines / SIP / SIP Gateways / Topology tab

Choose the ETH0 interface for
this customer equipped with
an OXO Connect Evolution
15
Public SIP Gateway
5.1.9. Gateway Parameters Details (Security Tab)
OMC/ External Lines / SIP / SIP Gateways / Security tab

SIP flows will not be
encrypted to this operator,
default value on the OXO
Connect Evolution
5.2. SIP Accounts (Authentication)
Manage authentication
- Login: pbxP (P = Pod number)
- Password: alcatel
- Registered Username: pbxP (P = pod number)
- Gateway Parameters Index: ITSP1G1
OMC/ External Lines / SIP / SIP Accounts

Right click on your mouse and
Add a line
Enter the parameters given by

the SIP provider to the
customer
SIP account (P= POD number 1
to 6)
Login: pbxP
Password: alcatel
Registered username: pbxP
Gateway Parameters Index:
ITSP1G1
Here is the OXO 1

Login: pbx1
Password: alcatel
Registered username: pbx1
16
Public SIP Gateway
5.3. Associate the newly created gateway with the VoIP external line
- Associate the SIP Gateway to the VoIP Access
OMC/External Lines/List of Accesses

Associate the newly created
gateway with the VoIP trunks
17
Public SIP Gateway
5.4. Check the registration of the OXO Connect on the public SIP provider
OMC/History and Anomalies/History Table
Message displayed:
SIP registration success
18
Public SIP Gateway
6 Test
To test your configuration, call a user of your own OXO by their DDI number
0210P41150… or one of the public numbers of the simulator (0) 0210P12345 or a set from
another OXO
6.1. Launch a SIP trace with Webdiag

OMC/Tools/Webdiag
Login = installer
Password = Alcatel1 for
example
In the menu at the left select

TCP Dump traces
Choose SIP
And start the capture
Stop the trace

A file is automatically
generated
19
Public SIP Gateway
6.2. Analyze the trace with Wireshark software

PC/Wireshark
Wireshark is installed on lab
PC to analyze VoIP SIP
messages
This trace can be saved and

transmitted to technical
support for analysis
Any other sniffer software can

be used
OXO Connect
Messages 1 to 20 utilization
Messages 1 to 20 utilization
According to the Software The messages can be

keys, the system can have recorded by MMC Station
4 to 20 audio messages or by OMC
This length is allocated

The total length of the dynamically to the 20
messages is 320 seconds messages
The messages can be used for the following features
DISA:
Remote External The message
Welcome:
Pre-announcement: substitution: forwarding: replaces the tone
The message
The message is The message The message tells and indicates the
belongs to an
played before or replaces the tone to the caller he is caller the
operator group
during a station is and indicates the automatically procedure to follow,
(i.e.Opening hours
rang caller the forwarded to an overdialing +
of the company)
procedure to follow external destination internal phone
number
OXO Connect
Music on hold and Preannouncement messages downloading
How to
✓ Download Music on hold and Preannouncement messages
Contents
1 Music on hold .................................................................................. 2
2 Preannouncement messages ................................................................. 5
2
Implementation
1 Music on hold
Upload a file .wav from the PC to the OXO in order to personalize the music on hold
- Reminder: this music is only used when putting on hold external calls (beep beep
with internal calls)
- Files .wav must be in 16-bit PCM 8 Khz Mono or CCITT A-law or μ-law 8-bit 8Khz
Mono format
- The audio files are made by a recording studio commissioned by the customer or can
be made by the installer from software specialized in the creation of audio files
If you do not have .wav files, record messages by MMC station in operator session: Menu
Operator/Expert/Voice/Hold music/scroll to Music xx
Application OMC/System Miscellaneous/Music on Hold
Open the object

“Music on Hold”
3
Select the Entity

for which you
would like a
custom music.
Select Recorded
Music
Entity1 by Select the entity number for which you wish to configure the music-on-hold.
default Default value: Entity1 (possible values entity 1 to entity 4 used in case of multi
company). Note: If no music-on-hold is available for an entity, the default music is
played for this Entity.
Music source Default Music: The standard system music created by Alcatel.
Tape: Music from an audio source (such as a cassette tape player) connected to
Recorded Music the audio-in connection of the system's CPU card.
Recorded Music: custom audio file (with .wav extension) stored in the system.
This option is grayed out when there is no custom audio file present in the system
Select the
function PC to
OXO download
Load from and

transfer
Click on the '3

dots' to search
for a .wav file
Note The 'Transfer and save as...' menu serves the other way to recover music already on the
OXO and save it to the PC
4
On the source
PC drive select
the .wav file to
download.
Then click on
« arrow » to
transfer
Reminder
The .wav file must be converted in audio format CCITT A-law 8bits 8Khz Mono CCITT µ-
law 8bits 8Khz Mono or PCM 16 bits 8 Khz Mono.
5
2 Preannouncement messages
Uploading a file .wav from the PC to the OXO in order to personalize MSG1 to MSG20
welcome messages (4 by default, 20 with license)
- .wav files must be in 16-bit PCM 8 Khz Mono or CCITT A-law or μ-law 8-bit 8Khz
Mono format
- The audio files are made by a recording studio commissioned by the customer or can
be made by the installer from software specialized in the creation of audio files
If you do not have .wav files, record messages by MMC station in operator session: Menu
Operator/Expert/Voice/Hold music/Message xx
OMC application/Subscribers Misc/Preannouncement Messages
Open the object

“Preannouncement
Messages”
Select in the list the

message to customize
(MSG1 to MSG20)
Select the function

“Load from and
transfer”
Click on the '3 dots' to

search for a .wav file
6
On the PC select the

.wav file to download
Then click on arrow to

transfer
Notes
Music on hold and welcome messages can also be recorded from mmc station by Operator
session Menu Operator/Expert/Voice/Hold music/Message xx or Music xx
OXO Connect
Incoming calls management
Call distribution
Public network Private network
Call
distribution
through Public
and Private PUBLIC PRIVATE
DIALING PLAN DIALING PLAN
Dialing Plan
Oxo Connect/OCE
Attendant / users
Incoming calls management - Dialing Plans Management
Management of the Public and Private Dialing Plan
• OMC\ Numbering \ Numbering Plans
• Tab: Public Numbering Plan
• Tab: Public Restricted Numbering Plan
• Tab: Private Numbering Plan
Function Start End Base TMN Priv Fax

Subscriber 41100 41199 100 - No -
The normal / restricted mode is used for INCOMING calls distribution

• 2 DDI numbering plans
• One for normal mode, another for restricted mode
The normal / restricted mode ( manual or automatic)

• Manual mode by the key NR Mode of an attendant
• Automatic mode according the time range
Attendant groups management
Available items Phone sets
in attendant Message
group General bell
Voicemail ports (Auto. attendant)
Remote access
1. Creating attendant
• OMC/ Attendant groups
groups
Incoming calls management - Attendant groups management
2. Creating time ranges for • OMC/Time Ranges
attendant groups
Calls distribution to attendant groups

Example: Management of the following case
08.00 to 12.00: sets 100 and 150 (OP grp 1)
12.00 to 14.00: MSG1 opening hours (OP grp 2)
14.00 to 18.00: set 150 (OP grp 3)
18.00 to 08.00: MSG1 opening hours (OP grp 2)
Incoming calls management - Attendant groups management
Attendant group diversion
• By the "attendant diversion" function key.
• This key is used to divert attendant calls to an external number via the collective speed dial number
• OP diversion status can be seen in OMC/Time ranges or OP diversion key blinking
• Using the "Diversion if restricted mode manually activated" and "Diversion destination for time ranges" settings
in the time ranges window
Attendant groups management - Dynamic routing
Dynamic routing
T1 set 101 T2 set 101
101 102
Active attendant
group
T1 attendant
T2 attendant
Default
attendant group 106
Attendant groups management – Attendant help
Attendant help
When the Attendant help feature is activated on the extension, the terminal user is the
destination number of external calls intended for the active attendant group
The Attendant help can be activated using the feature key “ Attendant help”
For analog stations

• by the code “Programming Mode + 6”
• Need to create a virtual key “General Monitoring” on the analog set
Pre-announcement
For DDI calls, messages can be assigned to a set or to the global installation as pre-
announcement messages
• Number of entries for individual greetings: 200
• Number of preannouncement messages: 20
• Messages duration: 320 seconds
OMC/Subscribers Misc/Preannoucement Overview

Pre–announcement / welcome greeting
The Pre–announcement is configured for each time range.
• In each time range is defined
• The mode (none / before call distribution / during call distribution)
• The message number (from 1 to 20)
• A flag for busy state only activation

OXO Connect
Attendant Group and Time Ranges Management
How to
✓ Manage attendant groups and time ranges
Contents
1 Attendant group creation .................................................................... 2
2 Time range management during the week ................................................ 4
3 Time range management during the weekend ............................................ 6
4 Preannouncement messages ................................................................. 7
2
Implementation
1 Attendant group creation

Set up two attendant groups:
Group 1: Extensions 100 & 101
Group 2: Message “MSG1” indicating working hours
- MSG1 can be recorded by MMC station in Operator session
In Virtual Classroom: IPDSP must belong to attendant group 1
OMC/ Attendant groups

Open “Attendant
groups”
Select the attendant

group 1 and click on
“Details”
3
select the
extensions belonging
to the group. Click
on “OK” to apply.
Choose extension
101 in the list and
click on “OK” to
apply.
Repeat the
operation once more
for Attendant group
2. This time, only
add “MSG1”
MSG1 can be
recorded by MMC
station in Operator
session
Or imported from
the OMC
Notes
Members of a PO group can be:
• Extensions
• Welcome messages (MSG1 to 20) e.g. opening hours
Ggeneral bell (SG)
• Or voicemail access (to build an auto attendant)
An attendant group is always in parallel mode.
4
2 Time range management during the week

During the week (Monday to Friday):
- Group 1 is active from 8 a.m. to 7 p.m.
- Group 2 from 7pm to 8am
The attendant will be able to divert calls to a predefined collective speed dial number,
if it manually switches to restricted mode.
- Via the N/R mode key
Manage the “400” speed dial number (or 8000 if default numbering plan) with an
internal number or DDI number to perform the test
Test your configuration by changing the system time
OMC/ Time ranges

Open the menu “Time
Ranges”.
Fill in “Monday tab” and

“Copy/paste” to the other
days of the week.
8am to 7pm: Group 1
7pm to 8am: group 2
Number This first column represents the Time range index

5
Start Beginning of the range
End End of the range

To modify this column, modify the “Start” column of the next line.
Call Distribution Normal/Opening hours or Restricted/Closing hours
Att. Grp Active attendant group for the specified time range
Att. div Is the Attendant group is diverted or not depending time ranges? (and if the field
“destination for time ranges” is filled out
Default Attendant Group Used to indicate an attendant group deployed in place of the active attendant group when:
- there is no attendant available in the active attendant group and diversion is not
authorized,
an attendant of the active attendant group manually places the system in restricted mode
and there is no destination indicated in the Destination if restricted mode manually activated
field.
- Destination of the attendant diversion following manual switch to restricted mode: Defines the destination
of the diversion of active attendant group calls when the system is manually switched to restricted mode
- Destination of attendant diversion for time ranges: defines the destination when diverting an active
attendant group to a time range. This diversion must be authorized: YES must be specified in the field
Attendant diversion
Copy the days of the week

6
3 Time range management during the weekend

During the weekend only the Group 2 will be active.
OMC/ Time ranges

Fill out “Saturday”, and
choose “Copy” button to
apply to the other days (ie
Sunday and Public Holidays).
Notes
Create a function key “Attendant diversion” on the attendant set, with the Common Speed Dialing pre-
programmed number. (Remind: protected key with operator password)
7
4 Preannouncement messages
Manage a general preannouncement "MSG2" for the entire company:
- MSG2 can be recorded by MMC station in Operator session
Before routing any incoming calls to its destination, a message indicating the company
name will be broadcasted.
OMC/ Subscribers Misc/ Preannouncement Overview

Open the object
“Preannouncement Overview”
located in “Subscribers Misc”
In “Global Greetings”, select

the button “Details”
8
In this window, configure the
preannouncement “Before call
distr.” for time range 1 only.
Select MSG2 in the list.
Don’t forget to copy to the

other days.
Time range Number pointing to the time ranges defined in paragraph 2 &3
Mode Before Call distr.: The message is broadcasted entirely then the destination will ring
During Call distr.: The message is broadcasted and the destination will ring at the same time.
If the called party answer before the end of the message, then the message is interrupted.
Message Select in the dropdown list the message you want to broadcast to the caller.
Only if busy Checked: the message is broadcast to the caller if the destination is busy (already in
conversation)
Unchecked: the preannouncement message is always broadcasted.
OXO Connect
Outgoing calls management
Outgoing calls process
Outgoing call restrictions
•Traffic sharing link category
The set is either allowed (authorized) or not allowed (forbidden) to
seize a trunk group
•Barring link category

If allowed to seize a trunk group, the number dialed is either allowed
(authorized) or not (forbidden)
SIP/ISDN
User Restriction link TG Restriction link

COS Barring level COS
Traffic sharing
User Traffic sharing TG Traffic sharing
Yes / No link COS
link COS
«0» Trunk group

Phones Trunk groups
Trunk group creation
Manage a trunk group with the SIP accesses
•OMC/External Lines/list of Trunk Groups, add the VoIP accesses
•See also chapter "Managing a public SIP gateway"
In case of
PowerCPU EE and
according to
interface cards
2 channels B of
T0 or a channel B
See chapter
of T2 are
Add VoIP access to the main default
configuration
automatically put
in the trunk
trunk group group 0
Modify the link categories if

necessary
Trunk group traffic sharing matrix
Trunk groups
Connection point:
« + »: Access from an extension set to a trunk
group is authorized
« Blank »: Access from an extension set to a

trunk group is prohibited
Trunk group
Phones traffic
sharing
matrix
Barring matrix and Barring tables
6 barring tables = 6 levels of barring
International calls are barred by default

The international prefix 00 is added with type “Forbidden” in all
Trunk groups barring table
Phones Barring
matrix
Barring
Connection point table
• Matches a barring table
Barring tables - digit counters
Counter 1
•Indicates the maximum number of digits which can be dialed
•If there is an authorized prefix in the table
•If there is no authorized prefix in the table
Counter 2
•Indicates the maximum number of authorized digits for prefixes not explicitly recognized in the table which contains
authorized prefixes
Link Category Management
Subscribers Trunk Groups

• OMC\ Subscribers list \ Detail \Baring • OMC\External lines\ List of trunk group \detail \Link Category
Idem for the Accesses in case of Break-in/Break-out

Menu: OMC\External lines\ List of accesses \detail \Link Category
Normal/Restricted modes
Normal/restricted mode can be activated by:
• N/R mode key on the attendant set
• Automatically using the time ranges
If the restricted •The system uses restricted LC values for

traffic sharing, barring and collective
mode is activated speed dial access
By default the users

• Except if the "Inhibition time
don't follow the ranges" flag is disable
time range state.
Subscriber normal / restricted mode
• Another feature right allows the subscriber to stay in normal

Inhibition flag mode although the system has switched to the restricted mode
forced by an operator action (programmable key)
Features
rights
• The feature right allows the subscriber to stay in normal mode

Inhibition time ranges although the system has switched to the restricted mode due to
the current time range
Multiple DDI number
Current behavior
•If there are multiple DDI ranges available for a subscriber and multiple
trunk lines in an OXO:
•the first DDI of the subscriber is always sent to the external party
Modified behavior
•It is possible to configure the DDI range to be used according to the
trunk line used.
•Identifiers of trunk lines will be displayed in Public numbering plan

which can be selected to associate a trunk line to required DDI range Example: N002 is configured against DDI range
• 5800-5890
•After selection in OMC, when the calls are made the outgoing calling
address(DDI) is sent based on the trunk line configured for DDI range
Now when a call is made from Subscriber 100
through [N02] second T0 trunk line connected DDI
•This new behavior is controlled with a newly introduced noteworthy number sent out to external party is 5800
address DDIonPRI
•This behavior is applicable for all types of trunks like T0, T2, Analog and
VoIP trunk
Access to collective speed dial directory
Omc/collective speed dial Subscribers list / Details / speed dial
collective
speed dial
directory
barring
OXO Connect
Call barring management
How to
✓ Manage the Call barring
Contents
1 Main trunk group seizure ..................................................................... 2
1.1. For the week ........................................................................................ 2
1.2. For the weekend and the Public Holidays ....................................................... 3
2 Secondary trunk group seizure .............................................................. 4
2.1. Numbering plan management .................................................................... 4
2.2. Trunk group management ......................................................................... 5
2.3. Traffic sharing Link-Category modification for the authorized subscriber ................. 7
3 Barring management.......................................................................... 9
3.1. Barring table management ........................................................................ 9
3.2. Barring link category .............................................................................. 10
3.3. Selecting the discrimination table that extensions will use ................................. 11
2
Implementation
1 Main trunk group seizure

Sets will be able to make external calls via trunk group 0, except from 12h to 13h and
from 19h to 8h from Monday to Friday (all the days except the Sunday and the Public
Holidays).
Prerequisite: a Public SIP Gateway is programmed according to the classroom
1.1. For the week

OMC application
Open object “Time

Ranges”
Choose “Monday” tab.

create 4 time ranges,
set it up with the
requested values
restricted from 12h to
1am and from 7pm to
8am.
Then copy and paste on
the other days.
Line 1 and line 3 Opening hour of the company.

It means that all the extensions can seize main trunk group because of the
default Traffic sharing Link Category values.
Start Beginning of the period.
Line 2 and line 4 Closing hour of the company.
It means that noone can seize trunk group because of the default Traffic
sharing Link Category values.
End End of the period : to fill in the end of the period you have to enter the
beginning of the period below.
3
1.2. For the weekend and the Public Holidays
OMC application
Open object “Time

Ranges”
Configure Public
holidays tab
then Copy and paste for
“Sunday” and
“Saturday”
Line 1 Closing hour of the company. It is Impossible to seize a trunk group due to
the default behavior of the system.
Notes
In the set “details/Feature Rights Part 2”, disable the parameter “Inhibition Time-
ranges”, so that extensions follow Normal/restricted mode defined in time ranges.
Otherwise, the phone sets always stay in normal mode even if the system switches in
restricted mode.
4
2 Secondary trunk group seizure

Create a secondary trunk group (seized by pressing #). Only one station will have access
to this trunk group.
2.1. Numbering plan management

OMC Application
Open object
“Numbering Plans”
in OMC Numbering
menu.
Select “Secondary
trunk group”
Modify the “start”
value by 401 and
base by 2
then click on
“modify”.
Secondary Trunk Modify the “Start” column (put “default value” +1, i.e. 401) and the base
Group (“default value” +1, i.e.”2”) of this feature. Click on modify to validate your
modification
5
OMC Application
Click on “function”
and select
“secondary Trunk
Group”.
Enter # for start
and End.
Enter base =1
Then click on
“Add”
Secondary Trunk Create a new secondary trunk group with base 1 and seizure prefix #.Click on
Group “add”.
2.2. Trunk group management

OMC application
Open object “List of

Trunk Groups «in
“External Lines”
The previous
management of the
numbering plan gives
the following change in
the list of trunk groups:
In index 2, the trunk
group number is no
more 400 but “#”.
Choose line 2 and click

on “Details”
6
Click on “Add” to add at

least 1 VoIP of the SIP
gateway
and then click on “Link-
Cat.”
By default, the traffic

sharing Link category
values are :
“Normal mode = 12”
and “restricted mode =
12”
7
2.3. Traffic sharing Link-Category modification for the authorized subscriber
OMC application
Open
Subscribers/Basestation
s list and select the user
to authorize.
Click on user “Details”

then on “Barring”
button
Modify the values as

follow:
“Traffic Sharing Link
Cat./ Mode normal = 5”
and “Mode Restricted =
5”
Open the object “List of

Trunk Groups” located
in “External Lines”.
8
Choose “#” trunk group

and then click on “Link-
Cat.”. The values are
the following. Don’t
modify them.
Open the object

“Traffic Sharing Matrix
«located in Traffic
Sharing and Barring
Find the intersection

between Subscriber
category (5) and trunk
group category (12).
The data “+” means YES
the extension is
authorized to seize this
trunk group.
Notes
For the other extensions, there is nothing to do because by default the Link Category
value is 12, meaning that the intersection between 12 and 12 is empty = NO. So, the
other extensions cannot seize # trunk group by default
9
3 Barring management
All sets of the installation will be forbidden to make international calls except towards
country code 53
3.1. Barring table management

OMC application
Open object “Barring

Tables”
Located in “Traffic
Sharing & barring”.
For table number 2

enter a prefix 0053.Turn
this prefix Type into
authorized type then
click on “Add”.
Show barring level Value from 1 to 6. Represents the barring tables. Choose “2” in our case.
Prefix Enter the prefix (beginning of the number dialed) you want to manage,
“0053” in our case.
Type Forbidden: the corresponding prefix will be forbidden
Authorized: the corresponding prefix will be authorized
In our case, choose authorized.
10
3.2. Barring link category
OMC application
Open again
Subscribers/Basestation
s list
Click on “Details” then
“Barring”
All the extensions will

have the following
values:
“Barring Link
Categories/ Normal = 2
And “Barring Link
Categories/ Restricted
=2
Repeat for all

extensions one by one
or use the button Copy
in the subscribers list
11
3.3. Selecting the discrimination table that extensions will use
OMC application
Open the object

“Barring Matrix” located
in “Traffic Sharing and
Barring”.
Look at the intersection

between line “2” and
column “1”: the value is
2, meaning we use the
barring table 2.
OXO Connect
System data saving
Summary
Basic automatic Data Saving
• OXO Connect
• OXO Connect Evolution
Manual backup & restore with the OMC

• OXO Connect
• OXO Connect Evolution
OCE: Automatic and manual backups on SD card
OMC backup migration

Basic Automatic Data Saving
Basic Automatic Data Saving
Procedure to do a backup
periodically
• OMC \ Data Saving & Swapping \Date &
Time Data Saving
PowerCPU EE
• Program the date of the first back-up,
On the eMMC OCE the periodicity of the next ones and
flash Eprom validate
available on In the files
MSDB daughter system Procedure to do a backup
board immediately
• OMC \ Data Saving & Swapping \
Commands
• Immediate Backup
Procedure to do the restore of

Maintenance the database
•POWER CPU EE • OMC \ Data Saving & Swapping \
•Replace Power CPU by a spare one Commands
•eMMC flash Eprom of the failed PowerCPU EE can be used on the • Immediate Restore
new PowerCPU EE
•It is necessary to generate a new license
Manual backup & restore with the OMC
Immediate manual backup by the OMC OXO Connect & OCE
Read the data from the PBX
• OMC\ Comm \ Read all from PBX

• Voice Prompts
• Central services
•…
• Button: OK
Save the data base in a file

on the PC
• OMC \ File \ Save As
• [Name: xxxx] [Customer: xxxx]
• Button: Save As
Store the file on a external

backup media
• OMC \ Comm \ Disconnect
• OMC \ File \ Backup \ Store
• Select the file to store
• Button: Save -> e:\xxxx.cdb
The database is stored in the OMC tool and

can be exported to an external media
Database restoration by the OMC OXO Connect & OCE
Restore the backup from the

computer
• OMC \ File \ Backup \ Restore
• Select the file to restore:
e:xxxx.cdb
• Button: Ok
Open the data base in Off

Line on OMC
• OMC \ File \ Open
• Select the file [Name: xxxx]
[Customer: xxxx]
• Button: Open
Restore the data to the PBX
• OMC\ Comm \ Auto Connect for

restore
• Installer password
• Voice Prompts
• Central services
•…
• Button: OK
OCE
Automatic and manual backups on SD card
SD card for backup
Scheduled & User & Configuration Several recovery

Backup & restore immediate data backup points
Remotely manageable Encrypted (AES 256) Led status
SD card slot is located at the

back OXO Connect Evolution.
• Insert the SD card when the
system is OFF
Led indicates
backup status
SD card is not provided by ALE
Configuration video click on the video to play
Click HERE to play this video in your internet browser
IP Box SD card Backup/Restore
Path:
Data saving
& swapping /
Backup & restore
(scheduled, immediate) data backup
& restore
Several recovery
points
Configuration data &
User data
The backup frequency is based on number of days

Misc
SD Card
• The minimum size is 2
The number of GB and maximum size
The oldest Restore of a is 32GB
recovery points is
recovery point is recovery point is • SD and SDHC supported
based on the size
deleted only supported in • SDXC is not
of SD Card and size supported
automatically by a the same major
of the recovery • Formatting only via
new one release
point OMC
• Supported file system
is EXT2
DBAdapter is downloadable on
DBAdapter is a software tool MyPortal web site
to convert database files • Install DBAdapterSetup.msi
saved with a previous version
of OMC to the latest installed
version
DBAdapter
After DBAdapter installation,
The OMC converts
automatically an old backup
when it open it
• Conversion is transparent
• Without DBAdapter, OMC suggests its
installation when it open an old
backup
OXO Connect
Saving and restoring the OXO Connect database
How to
✓ Save and restore the database
Contents
1 Database saving ............................................................................... 2
1.1. Database saving on the PC ........................................................................ 2
1.2. Database exportation on an external media .................................................... 3
2 Database restoration ......................................................................... 5
2.1. Importation from an external media ............................................................ 5
2.2. Open a database file in off-line mode for consultation ....................................... 6
2.3. Restoration of the database into the OXO (on-line mode) ................................... 7
2
Implementation
1 Database saving
1.1. Database saving on the PC

Application OMC
In order for the

backup to contain a
complete database
with the latest
changes, click on
"Read all from PCX".
The main objects of

the database are
validated by default
Optionally check
additional options
(especially if you have
recorded voice guides)
Click on « OK » to
activate the transfer.
Wait until the end of

the transfer.
3
Then open « file » and

click on « Save As ».
Give a Name to your

saved file.
Click on “Save As” to

activate the saving.
By default the location

of saving is in
Documents\OMC
1.2. Database exportation on an external media

Application OMC
Before exporting you

must Disconnect from
the OXO
4
Then open « File » and

then click on
Backup/Store
Select the database you

would like to export and
click on “Save”.
It is possible to extract
several databases.
Save the file into a

folder of your own.
(USB device, network
drive…)
5
2 Database restoration
2.1. Importation from an external media

Application OMC
To import you must be

disconnected from the
OXO
To do that you must

open « Comm » and
click on “Disconnect”
Open « File » and click

on Backup and select
“Restore”
Select the database to

import on the external
media.
Click on “OK” to start

importation.
As the result the

database is now in the
working folder on the
PC (Documents/OMC).
6
2.2. Open a database file in off-line mode for consultation

OMC application
Open “File” and click on

“Open”
In the default working

folder select the
database you would like
to Open in off-line
mode.
The selected database

is now loaded in OMC
application.
You can consult the

customer data base in
off-line mode (at that
time not connected to
his OXO)
7
2.3. Restoration of the database into the OXO (on-line mode)

OMC application
Open a database in off-

line mode .
See previous chapter for
details.
Then open “Comm” and

click on Auto-Connect
for Restore
Enter the Installer

password
Select the data to

restore, Classic data
Click on OK to start the

restoration.
8
Some updates will be

activated after a restart
of the OXO.
Click on Yes to restart

the OXO
Wait for the end of data

transfer.
If required the OXO

does a warm reset at
the end of the transfer
Once the OXO has

completely restarted ,
Connect on the OXO
You are now in on line

mode on the OXO with
the restored database
OXO Connect
Software Download
Software Download
Used to load and update the version of an OXO Connect or OCE via OMC
• Software Download through LAN & modem connection

• Use standard HTTPS protocol
2 versions simultaneously available

on a system
An active version
A replacement version
Downloading process
OXO Connect OXO Connect

OMC
Files system Files system
Software
downloading
Replacement Replacement
Software release software software
Running software Swap Running software

(With or without
data saving)
Swap:
replacement of
File transfer of the new
Data saving the current Data restore
software
software by the
new one
Software download tool
Start the Software
download tool
The software release is • OMC \Tools \Software download
available on the BPWS
• Enter the “Download” password
• https://myportal.al-enterprise.com (customized at the system startup)
• It’s mandatory to download the following • When the site is connected, your OMC
files downloading session is operational
• The PBX software release xxx_xxx.zip
• The associated OMC xx.xx.zip
• The technical communication associated
• All these files must be unzip on the

management PC
Software download screen
Back to the previous version
After a
download it is Swap can be
possible to go Swap must be
scheduled done with or
back to the without data
previous version • OMC/Data saving and
swapping/SW-downloading saving
by performing a
switchover
OXO Connect
System reset
System reset
Warm reset
• Allows to unlock hardware malfunction without losing the customer database
• The system stops
• The system restarts without losing the data
Cold reset
3 system • Allows to come back in default configuration and customize the system again
resets • After a cold reset you loose all the customer’s configuration
are • User Data
• System Data
available • Cloud Connect Data
• Network, installer passwords and Management Data
Factory Reset
• Removes all the sub categories of data in cold reset and additionally it removes
system logs
• After Factory reset, system state is close to that of Lola installation
Note:
Cold reset options When Cold reset is triggered without selecting any sub options
• The following settings are not deleted:
• Installer passwords
Information categorized as Cloud Connect Data: • Network settings
• Management services access flags
• Activation state • Cloud Connect parameters
Information related to • FTR completion status
users/subscribers is categorized as • Server URL
User Data: • One Time Activation account and password
• Voice mail (VMU) • Final account and password
• Instant Messaging (IM) Network Data includes:
• Mails • Host Name
• IP address
• Net Mask
• Broadcast
• Gateway
• VLAN
• Router
• Domain Name Server
• Web Proxy parameters
▪ IP/hostname
Information categorized as System Data: ▪ Port
• Data saving files ▪ Account
• Metering ▪ Password
• Traces and core files Management Passwords
• ACD statistics and logs • Attendant
• Administrator
• Installer
• Download
• NMC
Management Data
• Allow Management services from WAN
System reset
By MMC Station on phone operator session:

• Menu/Operator/enter the OP password/Expert/System reset
• Warm: system restarts without losing the configuration
• Cold: system restarts and deletion of user data, system data
How to • Cloud Connect data, network, installer password are not deleted
do a
reset? Use OMC Expert mode
• OMC \ System Miscellaneous \ System Reset
• Reset Type
• Cold (with options), Warm or Factory
• Reset Time
• Manual or Automatic
Manual Shutdown followed by a system restart is a warm reset

OXO Connect
Security warning
Security warning
The Phreaking is the name for the telephony system hacking
When somebody hacks your PABX, the target is not your PABX, the target is your customer’s wallet
• The victims can loose more than 20 K€ in one weekend
• Your phreaked line is sell to the long distance carrier
• Your phreaked line can be connect to a premium rate number
The freaking is a business run by organised crime

Security warning
Configure the system, users & features according to recommended rules
•Refer to the SECURITY chapter from The Expert Documentation

•See Security Recommendations for OXO system document: TC1143_Security_Recommendations_for_OXO_Connect
Manage the system & users passwords with common sense:

•Not default
•Change them regularly
•Not simple, not short…
A system upgraded to the last version benefits from most recent improvements as well as default
values & security patches
Security warning
The objective of the TC1143 It is highly critical that installer
document is to provide the and user/system administrator
customer with the Alcatel- provide diligent attention to
Lucent Enterprise’s system management and
recommendations for setting an security recommendations of
optimal security on ALE system’s Alcatel-Lucent Enterprise to
configuration and deployment effectively reduce the risks
It is installer’s responsibility to
System installer must also
carefully inform users/system
discuss with the user/system
administrators of the OXO
administrator the level of
Connect system’s security
security to best customize the
features
system
Security warning
For this the TC1143 deals in depth with the following topics:
•Access Control: Password Policies
•User password management
•Management of system passwords
•Network Security: Remote Access Configuration
•System configuration settings
•Summary of Security Settings Outstanding Addresses and System Options
It is mandatory to have document latest edition, read and apply its recommendations and also the
SECURITY Chapter from Expert Documentation
TC1143
OpenTouch Suite for MLE
Rainbow
Overview
Rainbow
Is the cloud solution for team Collaboration and Unified Communications featuring phone and
web calls, video conferencing, mobility, security and many APIs open to all developers
BE SPONTANEOUS
Chat, group chat, presence BE ENGAGED

File sharing
Multi-device Audio/video Calls
Screen sharing
BE IN CONTROL
Administration
Analytics
APIs and openness
PBX Integration
2 feature-rich Cloud solutions
Unified Communications Communication Platform

as a Service [UCaaS] as a Service [CPaaS]
Rainbow is a ready-to-use, business communications, team In addition, Rainbow also offers an open, business-friendly
collaboration and conferencing that can federate with an on-premises Communications Platform as a Service (CPaaS) for developers,
customer PBX system that addresses the customer needs for Business Applications
integration to empower the end-customer relationships and the
employee efficiency.
COLLABORATION HYBRID Cloud model

Contacts, presence, instant Unification of PBX infrastructures (ALE and
messaging, voice/video VoIP non-ALE), common directory
call, document sharing, BUSINESS APPLICATIONS CUSTOMER RELATION
mobility, persistent Optimization of business Integration of real time
collaboration process Open APIs & SDK for communications in public apps
easy business apps integration
https://hub.openrainbow.com
Global view
Rainbow APIs - CPaaS
Verticals & openness
3rd party applications

• Alarms & Monitoring • Chat, call, video
• Analytics • End-to-end experience
Machines
• Control & management • Integration in business process
AGENT
API
• Cloud telephony
Rainbow
PSTN • Conferencing
Platform • Multimedia traffic
Connected Platforms
AGENT
Rainbow app AGENT • PBX Telephony
Other PBXs • Call control
• Unique User Experience OXO Connect AGENT
• Federation
• Contacts & Workplace
• Rich presence OXE
• Notification
Rainbow Workplace - UCaaS

Architecture - UCaaS
PBX connected to Rainbow with WebRTC gateway
Communications
•Manage and establish calls between Rainbow clients
•Manage and establish calls between Rainbow clients
and any phone number or extension
•Manage your routing profile according to your needs
Clients
•PC Rainbow App
•Web
•Mobile
Customer premise
Subscription plans
Rainbow Essential This free option is available to anyone who wants to try Rainbow for an unlimited period (no SLA). The
Essential subscription can also be blended with any premium subscription, optimizing the cost of the
solution for the whole organization.
Rainbow Business The per-user subscription addresses individuals and teams who want to improve their daily communication,
on or off-site, on-the-move, or as a productive remote worker.
Rainbow The per-user subscription includes all services from Rainbow Business, but with the addition of collaborative
multi-party services with video conferencing and extended file storage. Integration into existing office tools
Enterprise such as Microsoft 0365 and Google Suite also forms part of this service plan.
Find the details of
Rainbow This per-user subscription packages the Rainbow Enterprise service plan with unlimited phone conferencing the plans on:
minutes. The Rainbow Enterprise Conference user subscription is pre-paid yearly in advance (twelve
Enterprise months). openrainbow.com
Conference
/Subscription plans
Rainbow An optional service proposed as a “pay-as-you-go” model for phone (PSTN) conferencing with a price-
perminute/per-connection. The organizer of the meeting can be a Rainbow Essential (freemium) user, or
Conference premium user with Rainbow Business or Rainbow Enterprise subscriptions.
Rainbow Connect The per-user subscription addresses users of any Customer Relationship Management (CRM) application. The
integration of the Rainbow functionality is provided using a specific connector dedicated to the compatible
CRM application.
Rainbow Room An optional per-room subscription proposed for meeting rooms equipped with large screens for
communication and interaction with people inside and outside of the company. Additional hardware is
required to equip the meeting room and ALE has audio and video hardware kits readily available.
Find us on your Knowledge Hub portal !
Free RAINBOW courses are available

Rainbow
Rainbow administrators
Summary
Reseller administrator
End-customer administrator
Reseller administrator
Assign
Manage end-
Manage its own subscriptions to
customer
company end-customer
companies
companies
Has a view Create PBXs & Assign PBX

Manage
activate extensions to
on the WebRTC
administrator &
user accounts
Rainbow
customers gateways accounts
companies
Monitor the
Manage user
activity through …
profiles
the dashboard
End-customer Administrator
Manage user Manage company's
accounts information
Assign
subscriptions to View related PBXs
users accounts
Manages
its own Associate users
company phones with their
Manage user
profiles
Rainbow accounts
Monitor the
activity through
the dashboard …
OXO Connect
Connect an OXO to Rainbow
How to
✓ Configure Rainbow agent in OXO
Contents
1 How to find PBXIDs and activation codes? ................................................. 2
1.1. How to find these credentials? ................................................................... 2
1.2. Find the credentials with the client administrator account .................................. 2
2 Connect the OXO to Rainbow ................................................................ 4
2.1. Enter Rainbow PBX-ID and activation code ..................................................... 4
3 Maintenance ................................................................................... 6
3.1. Status of the connection by the Webdiag tool ................................................. 6
3.2. System log files ..................................................................................... 6
3.3. Rainbow user log file ............................................................................... 7
2
Implementation
The creation of companies and PBXs has already been done in the Rainbow administration. The trainer
must show you the configuration done.
1 How to find PBXIDs and activation codes?
1.1. How to find these credentials?
- The credentials can be given to you by your reseller, who created the PBXs for your company. For
example, the trainer in this case.
- You can also find them on your own, by logging into Rainbow with your Rainbow client administrator
account.
1.2. Find the credentials with the client administrator account
Log in to the Rainbow interface with the client company's administrator account:
- Login : cCpP.admin@ale-training.com (C : class number, P : pod number)
- Password: Superuser-P* (P : pod number)
https://web.openrainbow.com
Enter the email address of the
customer administrator
account
3
Enter the password

and click Connect
Click on the company
management icon then

My company
Select the Communication

menu
Click on the OXO in the list
You will find here:

• PBXID
• Activation code
Copy – paste this information

into the OMC/ Cloud/ Rainbow
4
Tips
The administrator can also use the Rainbow application installed on his PC to carry out the
configuration/management operations of the company.
2 Connect the OXO to Rainbow
Connect your OXO Connect to Rainbow with the credentials

- PBX-ID
- Activation code
2.1. Enter Rainbow PBX-ID and activation code

OMC/Cloud/Rainbow
In Cloud menu, select
Rainbow
Enter the Rainbow PABX-ID
Enter the Activation code
Click on Rainbow enabled
Apply
Domain name Leave the default value: openrainbow.com

Rainbow PABX-ID The Rainbow ID is generated by Rainbow.
Activation code The activation code is generated by Rainbow.
5
Check connection status

6
3 Maintenance
3.1. Status of the connection by the Webdiag tool
OMC /Tools /Webdiag /Services /Rainbow Status

Control the connection status:
« connected with final
password »
Login: installer
Password: enter installer pwd
3.2. System log files

Through Webdiag tool
System tab/ System Files/ Log
files
The rainbow agent log file

name is:
ccrbagent.log
Login: installer
Password: enter installer pwd
7
3.3. Rainbow user log file

Through Rainbow interface
User Settings tab
About Rainbow tab
Menu Open logs

OXO Connect
Rainbow accounts configuration and use
How to
✓ Create new Rainbow user accounts.
Assign ENTERPRISE subscriptions.
Use Rainbow clients
Contents
1 Company Administrator Account ............................................................ 2
1.1. Login to the company's administrator account ................................................. 2
1.2. Verify that the administrator has an "Enterprise" subscription .............................. 3
2 Manually create a new member ............................................................. 4
2
Implementation
The client administrator account cCpP.admin@ale-training.com is already created.
We will create an additional user account: cCpP.user1@ale-training.com.
- cCpP.user1@ale-training.com will be created manually by the administrator
- It is also possible to create users by invitation or to import users in bulk (Refer to the Support site)
1 Company Administrator Account
1.1. Login to the company's administrator account
Log in to the Rainbow interface with the client company's administrator account:
- Login : cCpP.admin@ale-training.com (C class number and P pod number)
Using a browser:
https://web.openrainbow.com
Enter the email address of the
administrator account
3
Enter the password and click

Connect
1.2. Verify that the administrator has an "Enterprise" subscription
Click on Members
Select the administrator

account
On the Services tab, validate

the Enterprise subscription
4
2 Manually create a new member
Create the following Rainbow user account:

- Login : cCpP.user1@ale-training.com (C class number and P pod number)
- Name : cCpP
- Firstname: User1
- Subscription: Enterprise
https://web.openrainbow.com (or Rainbow App on PC)

Click on Members and then on
Create
5
Fill in the required fields
Login Enter the user's email address: cCpP.user1@ale-training.com

Password Specify a password: Superuser-P*
Sign-in method Keep default value: Login and password will be asked to sign-in.
Visibility Keep “same as company”. The company is managed as private.
Last name cCpP
First name User1
Subscription Enterprise
Send enrollment email to new If validated, an e-mail is sent to the user to notify him of the creation of his Rainbow
users account
6
Notes
If the "send enrollment email to new users" option has been validated, you can consult the user's mailbox:
Example: c2p1.user1@ale-training.com, password: Password1*
Mail server: https://mail44.lwspanel.com/
Username: e-mail address-> cCpP.user1@ale-training.com

(P pod number and C class number which is given by the trainer)
Password : PasswordP* (P : pod number)
PLEASE DELETE THE OLD EMAILS IN THE MAILBOX
Warning
CHECK THAT THE EMAILS SENT BY THE RAINBOW PLATFORM DO NOT ARRIVE IN THE SPAM.
3 user accounts are created:

OXO Connect
Associate extension numbers with Rainbow user accounts
How to
✓ Associate OXO Connect extension numbers with Rainbow users
Contents
1 Assign extension numbers to company members ......................................... 3
2 Test RCC features ............................................................................. 5
2.1. Outgoing call to an OXO Connect user .......................................................... 5
2.2. Incoming call ........................................................................................ 5
2
Implémentation
This lab consists of linking the extension numbers of the OXO Connect to the Rainbow members created in the
previous lab.
Once associated, members will be able to supervise their phone from Rainbow (unhook, hang up, put on hold),
this is the RCC (Remote Call Control) mode.
Without a WebRTC gateway, the audio will be exclusively managed on the phone.
The goal of the next lab will be to manage the WebRTC gateway so that users benefit from all call routing
services.
If Training in virtual classroom:

- IPDSP 104 will be associated with the Client administrator account: cCpP.admin@ale-training.com
- Regarding the User1, he will be managed in softphone mode (anydevice) in the next lab seen after the
WebRTC presentation.
3
1 Assign extension numbers to company members
Assign the following extension numbers:

- Extension 100 will be assigned to the client administrator: cCpP.admin@ale-
training.com
- Extension 101 will be assigned to the member: cCpP.user1@ale-training.com
If training in Virtual Classroom:

- IPDSP 104 will be assigned to the client administrator: cCpP.admin@ale-training.com
Rainbow PC application or https://web.openrainbow.com

Using the company's
administrator account.
Click on the company
management icon then

My company
Click on Members
Select the member to

configure
Example:
c2p1.admin@ale-training.com
4
Select the Telephony tab
Select oxo Connect from the

list ("Equipment" field )
Select the extension number

related to the member.
In classroom: 100
In V-Class: 104
Click Apply
Equipment Sélectionner l’OXO Connect

Extension number Sélectionner le poste OXO connect à associer au compte.
Public number DDI number associated with the user in the OXO Connect
Notes
The list of OXO Connect extension numbers is synchronized live with the Rainbow environment.
Once the association done, a new field is displayed, the Rainbow number.
Example:
This number will be retrieved later for WebRTC gateway use. It will be automatically configured in Remote
Extension number by the Rainbow agent (e.g. BBB10070254106463346) when the user selects “computer” as
routing from his Rainbow client (PC or smartphone).
Perform the same operation with USER 1:

- Extension 101 will be assigned to the member: cCpP.user1@ale-training.com
5
2 Test RCC features
Tester les fonctionnalités « Remote Call Control »
2.1. Outgoing call to an OXO Connect user
From the Rainbow client, using the account linked to the extension 100/104
(cCpP.admin@ale-training.com: C class number and P pod number) :
- Select "Office phone"
- Call extension 101 by dialing from the Rainbow app
- Does it works ?
2.2. Incoming call
From extension 101, call extension 100/104.

Is it possible to pick up the call that arrived using the Rainbow client?
What action(s) is/are available?
OXO Connect WebRTC Gateway
Rainbow WebRTC Gateway
The WebRTC Gateway brings voice interoperability between Rainbow Clients and PBX ecosystem.
• This enables an audio media relationship between Rainbow applications and devices of a PBX connected to Rainbow
Installation requirement
OXO Connect OXO Connect PowerCPU EE
Evolution
Web RTC Gateway virtual OXO Connect WebRTC Front End Web RTC Gateway virtual Web RTC Gateway virtual
machine is integrated (on OCE Front End) machine installed on Mini machine installed on a
PC (NUC) server ESXi
Rainbow Enterprise
Rainbow Business
• Audio between Rainbow clients /
any phones / Off-net
• Unified multi-devices experience
Use case examples of Rainbow WebRTC Gateway
PBX calls distributed to both PBX Incoming
devices and Rainbow clients calls
Outgoing Make calls from Rainbow to any

calls telephone extension
VoIP
VoIP
User
Incoming Rainbow or
PBX calls ring devices
according to user’s
routing profile
settings Any phone
DECT phone
WebRTC
Office phone
WebRTC PSTN
PBX
PBX
External phone number Incoming call
Internal phone number
Deployment steps
Prerequisites the PBX must be connected to Rainbow
• The WebRTC gateway requires an OXO Connect or OXO Connect Evolution
External WebRTC gateway OCE – Integrated WebRTC gateway

Automatic configuration
The automatic configuration of the internal / external WebRTC
gateway is available from system version R4.0.020.002
• Automatic deployment is managed from the Rainbow Reseller administrator account
Internal WebRTC External WebRTC
The following settings are managed automatically:

• Creation of WebRTC SIP gateway
• Activation of internal WebRTC gateway (OCE only)
• Configuration of the SIP Account with the Rainbow PBX ID
• Creation of WebRTC SIP gateway
• Creation of VoIP accesses and trunk group
• Configuration of the SIP Account with the Rainbow PBX
• Configuration of ARS table to route Rainbow calls
ID
• Creation of VoIP accesses and trunk group
The following settings are still to be done by the installer as
• Configuration of ARS table to route Rainbow calls
they are specific to each customer:
• Connect PBX to Rainbow
The following settings are still to be done by the installer
• Installation & configuration of the external WebRTC virtual
as they are specific to each customer :
machine / Standalone PC
• Connect PBX to Rainbow
• Creation and association of the AnyDevice/Rainbow virtual
• Creation and association of the AnyDevice/Rainbow
terminals
virtual terminals
• Configuration of numbering plans and of the barring
• Configuration of numbering plans and of the barring
• Activation of the WebRTC gateway
Automatic configuration
Automatic deployment is managed from the Rainbow
Reseller administrator account
• Edit the client company's PBX in order to activate automatic configuration
Internal WebRTC External WebRTC

(OCE Front End or NUC or ESXI)
External on OCE Front End

Deployment steps on OXO Connect
Create the terminals for VoIP on PC (Softphone)
• To be done whatever the topology, integrated WebRTC or external WebRTC
• Create a Multiset TC2479 Rainbow
• The main station is the physical station WebRTC Gateway with
• The secondary station is OXO Connect / OXO
• Free Rainbow in Twinset from R6.0 Connect Evolution
• (Anydevice up to R5.2)
Secondary station from Release 6.0:

In the case of a user with only Rainbow
The Free Rainbow in Twinset virtual
(without a physical station), create for
terminal must be used in order to save
this user only an Anydevice terminal
an UTL license (UTL Bypass) Note: Until Release 5.2 the AnyDevice equipment
was also used as a secondary station in multiset
Use case # 1
WebRTC integrated to OXO Connect Evolution
RAINBOW WebRTC Gateway integrated in OCE
Same feature level as the external WebRTC GW SIP Trunk Public

External
topology Licenses
needed
WebRTC GW Trunk
Private SIP Trunk
Easy to configure and maintain via OCE

management tools Before R3.2
SW upgrade via OXO management tool and Cloud

Connect Update service
No need for SIP trunk licenses (bypass)

Public
SIP Trunk
Trunk
• Supported for OCE and OXO Connect Licenses
• Supported topologies: Integrated and External

Integrated
WebRTC GW
From R3.2
OCE Integrated WebRTC GW
Security
• Communication flows between the WebRTC GW
and Rainbow over the internet are secured with
HTTPS and SRTP
• This applies for external and integrated
WebRTC GW topologies
Configuration
• The activation and configuration of the WebRTC
gateway is now carried out from the Rainbow
administration
• Activation triggers the configuration on the OXO
Connect side
• Unique configuration for the WebRTC gateway
which can be internal OCE or external OXO /
OCE
Use case # 2
WebRTC gateway on OCE Front End
Introduction Release ≥ R4.0 MD is mandatory
The WebRTC gateway runs on an IPBox on the customer’s
LAN, in front of another OXO Connect which runs the
customer Call Server
The release ≥ R4.0 MD must be installed on both the Front-

End RGW and the OXO Connect call server
Installation and maintenance procedures same as usual

(FTR, OXO Connectivity, OMC…)
https
No dedicated software for Front-End (but specific license
for free)
Easy WebRTC deployment and configuration through Cloud

Connect FTR SIP Public Trunks
The license is free and auto-provisioned (FTR)
Full ALE solution, easy to buy (one order for OXO Connect OXO Connect Call Server
and OCE Front-End)
Rainbow WebRTC Gateway on OCE Front-End
A standard OXO Connect Evolution (HW and SW) is used
A specific free License provides the behavior WebRTC Gateway on OCE Front-End
• An OCE in front-end Mode is limited to WebRTC GW feature (No UTLs, etc…)
The Rainbow WebRTC Gateway on OCE Front-End solution management

• Rainbow Admin (for coupling the OXO to the company & WebRTC GW activation)
• Cloud Connect (for OCE Front-End management)
Type of Rainbow GW OXO Connect OXO Connect evolution

(Power CPU EE) (IPBox)
Internal GW Not supported 20 calls max.
External GW (NUC) 50 calls max. 50 calls max.
OCE-FE GW 20 calls max. Not supported
Remarks
• OCE Front-End does not provide PBX capabilities
• OMC tool is not needed for OCE Front-End provisioning
Installation
Installation of the OCE Front-End is automated with the FTR procedure
• FTR provides the OCE Front-End license and upgrades the OCE release (≥ R4.0 MD) if necessary
Connect to the OCE Front-End ETH1 in DHCP mode

• and start a Web browser to 192.168.94.246
At the first connection to a brand

new IPBox, an installer password
must be defined
•Alcatel1 for example
Define the product type ‘Frontend WebRTC’
Enter the customer
Select Frontend WebRTC reference, IP parameters…
FTR OK
This IPBox is now an OXO Connect

FrontEnd WebRTC Gateway and ready
to be associated to the OXO Connect
customer call server
Rainbow WebRTC Gateway on OCE Front-End status
A warm reset is necessary to take into account

modification to Rainbow WebRTC Gateway on OCE
Front-End
Front-End WebRTC CPU status can be checked
• In menu Settings
• In Webdiag tool
Rainbow BP administration – Rainbow WebRTC Gateway on OCE Front-
End configuration
Activate the WebRTC gateway for the For the type of WebRTC gateway
corresponding customer company select: External on OCE Front-End
External on OCE Front End
20 max
OMC – Rainbow WebRTC Gateway on OCE Front-End configuration
The private SIP gateway is

automatically created on
the OXO Connect call
server
Verify port numbers to

5059 in the SIP Gateway
parameters
Rainbow PBXID must be the • On the OXO, by entering an FTR, the PBXID and the activation code are initialized
by default to "FleetRef-Installref", which allows the installer to prepare the
same in both OXO Connect, equipment in advance in RB WebAdmin: the OXO will automatically connect to RB
Front-End and call server at the end of the FTR to FleetRef-Install_ID
Note: if the Rainbow company was already created put also the PbxId in both OXO
e.g:PBX9a86-5916-b74a-436c-aec6-c08a-58b6-5bb0
OMC - Rainbow WebRTC Gateway on OCE Front-End configuration
Check OXO Connect Rainbow status
OXO Call Server OXO Front-End
Details about Front-End mode configuration in document Rainbow WebRTC cookbook

available on MyPortal
Rainbow WebRTC Gateway on OCE Front-End
Cloud Connect evolutions for Rainbow WebRTC Gateway on OCE Front-End
1 line per device in Fleet Dashboard

with same root of install_id In Fleet Dashboard & OXO Connectivity:
- Identification of PABX/OCE-Front-End
- Dynamic link to access the peer device
with a single click
The commissioning of an OCE-FE can be
done with different scenarios
Adding OCE-FE to an
Order made WITH or
existing PBX
New complete WITHOUT Partner
installation, PBX + •PBX already existing in fleet reference and
R4
OCE-FE •Existing PBX version
Installation
lower than R4 reference
For this it is essential to follow the

document "Rainbow WebRTC cookbook"
latest edition available on MyPortal
This document describes the specifics of the different use cases

Use case # 3
External WebRTC gateway-
Virtual Machine deployment on vmware
Deployment steps on vmware
Download the WebRTC Gateway virtual

machine from MyPortal
Deploy and configure the virtual machine on an
external server by using the following procedure:
• Installation and configuration procedure
Download procedures from the Rainbow Support website, ALE equipments (PBX) section
• Deploy the virtual machine on Vmware environment

WebRTC Gateway virtual machine deployment

• Deploy the .ovf file with Vmware Player and start the virtual machine
WebRTC Gateway configuration steps

• Configure the Network settings (static or DHCP)
• IP, NETMASK, GATEWAY and DNS
• Add the OXO Connect IP@ and Rainbow PBXID
• TURN server configuration according to site location

Deployment steps on RAINBOW
Rainbow administration
• Select the option "Activate the WebRTC gateway“ for the
company
• Define an external gateway and the number of channels
• The OXO Connect is managed automatically
Rainbow users configuration

•Each user needs to be granted with either a Business or an Enterprise
license
•And the Rainbow account must be associated to this user PBX phone
Use case # 4
External WebRTC gateway -
Vitual Machine deployment on a mini-PC
Installation on a Mini PC (NUC)
The main deployment steps are the same as installing a virtual machine apart the mini PC
installation
Whitelist (Available in the procedure)
The Software package available on MyPortal contains the OVF files for VMWARE installation,
and, an ISO file for installation on a mini PC
NUC: Next Unit of Computing

Installation on a Mini PC
Mini PC installation:
• Download the ISO file from MyPortal
• Create a Bootable USB drive
• Install the ISO file on the mini PC Storage device
• Reboot the standalone PC and setup the configuration parameters
Follow the deployment instructions available in the installation guide
Follow the procedure to configure the WebRTC gateway on a mini PC
Download procedures from the Rainbow Support website, ALE equipments (PBX) section
Software is needed to create a bootable USB drive. RUFUS is very easy to use for this purpose, and is available here: https://rufus.akeo.ie
Dimensioning
Rainbow WebRTC gateway dimensioning
50 VoIP calls maximum if the WebRTC gateway is external on Mini PC or ESXi server
20 VoIP calls maximum with OCE integrated WebRTC gateway or if the WebRTC gateway is external on OCE Front
End
• External WebRTC GW topology is also supported on OCE when more WebRTC channels are needed (max 50)
Maximum of OXO users with Rainbow VoIP option increased from 50 to 150
• Applies for both OXO Connect and OXO Connect evolution
Number of Rainbow Users with Number of trunk channels in Number of Rainbow Users with VOIP
VOIP Option Rainbow WebRTC GW & SIP trunk Option
(recommended)
External (OXO and OCE) External / Integrated or Front End Integrated (OCE)
5 5/5 5
10 7/7 10
20 11/11 20
30 15/15 30
50 20/20 50
70 27/NA 70(*)
100 36/NA 100(*)
150 50/NA 150(*)
(*) Integrated WebRTC on OCE: the maximum Rainbow Users with VoIP limits depends on the number of configured Rainbow
Channel and end user traffic. Value indicated here is for direction only for 20 configured WebRTC GW channels. But
Maximum limit is 150 that is ok in case of very low traffic
Note: External WebRTC gateway is also available with OCE if

more channels are needed
OXO Connect
Internal WebRTC Gateway automatic configuration on OXO Connect Evolution
How to
✓ Configure automatically the internal WebRTC gateway on OXO Connect Evolution.
Contents
1 Applies to system versions ................................................................... 2
2 Description ..................................................................................... 2
3 Automatic configuration by the Reseller administrator ................................. 2
3.1. Reseller Administrator Logs in to Rainbow ..................................................... 2
3.2. Edit the PBX of the customer company ......................................................... 3
3.3. Activate the WebRTC Gateway ................................................................... 3
3.4. Manage an Internal WebRTC gateway ........................................................... 4
4 Check activation in the OMC ................................................................ 5
2
Implementation
1 Applies to system versions

Automatic configuration applies to versions greater than R4.0.020.002
2 Description
- Activation of internal WebRTC gateway (OCE only)
- Creation of WebRTC SIP gateway
- Configuration of the SIP Account with the Rainbow PBX ID
- Creation of VoIP accesses and trunk group
- Configuration of ARS table to route Rainbow calls
The following settings are still to be done by the installer as they are specific to each customer:
- Connect PBX to Rainbow
- Creation and association of the AnyDevice subscribers
- Configuration of numbering plans and of the barring
3 Automatic configuration by the Reseller administrator
Automatic activation of the WebRTC gateway is performed by the trainer with a reseller
administrator account
- Enable Internal WebRTC Gateway
- Define several communication channels
3.1. Reseller Administrator Logs in to Rainbow
He is the only authorized account to manage this service

3
3.2. Edit the PBX of the customer company
Client Company / Communication

Manage connection
3.3. Activate the WebRTC Gateway
Information tab
Select Activate WebRTC
Gateway
4
3.4. Manage an Internal WebRTC gateway

Settings tab
Select "Internal" and set the
number of channels
WebRTC gateway is enabled
The Client administrator can

check the status of
connections
5
4 Check activation in the OMC
Verify in the OMC, the activation and configuration of the WebRTC gateway
OMC / Cloud / Rainbow

WebRTC Gateway is
Connected and Enabled
Rainbow
OXO Connect
Create and assign Anydevice/virtual terminals to rainbow user accounts for

VoIP
How to
✓ 1 - Manage users with physical deskphone + Rainbow Virtual terminals
2 - Manage users with AnyDevice terminals only (Rainbow VoIP softphone)
Contents
1 Users with physical extension and Rainbow application ................................. 2
1.1. Create Virtual Free Rainbow in Twinset terminal ............................................. 3
1.2. Associate the Virtual Free Rainbow in Twinset terminal as a secondary set
of the user's primary extension ................................................................... 3
2 Manage a Rainbow user in softphone mode, without a physical extension ........... 4
2.1. Create an AnyDevice terminal .................................................................... 4
2.2. Assign the number 133 to the Rainbow member cCpP.user1@ale-training.com........... 5
3 User interfaces after configuration ......................................................... 6
3.1. Rainbow user interface in softphone mode, without physical set ........................... 6
3.2. Rainbow user Interface with physical extension and Rainbow application ................. 7
2
Create and assign Anydevice/virtual terminals to rainbow user accounts for VoIP
Implementation
In order to use all capabilities of PBX-Rainbow phone features, 2 different user profiles can be created :
- User with physical extension and Rainbow application:

o Allows to manage telephone communications from the physical extension or the Rainbow
application, web or mobile (Softphone mode). Requires a physical extension + a Free Rainbow
virtual terminal.
- Rainbow user only (Softphone and mobile mode), without a physical extension:
o All communications are managed via the Rainbow app, web or mobile. Use in Softphone mode,
no physical extension. Requires an Anydevice terminal.
Notes
• Deskphone + Free Rainbow virtual terminal = 1 UTL
• Anydevice only = 1 UTL
1 Users with physical extension and Rainbow application
Users manage their communications from their extension or Rainbow application, according to the chosen
routing.
Associate each user with extension, Virtual Free Rainbow in Twinset terminal:
User 100
- Create Virtual Free Rainbow in Twinset terminal: 130
- Associate it with extension 100 as a secondary set (Directory number 100 is already
associated with the Rainbow user account)
User 104 (IPDSP)
- Create Virtual Free Rainbow in Twinset terminal: 135
- Associate it with extension 104 as a secondary set (Directory number 104 is already
associated with the Rainbow user account)
- User1 will be Rainbow Softphone user.

3
1.1. Create Virtual Free Rainbow in Twinset terminal
OMC/Subscribers list
Create a Virtual terminal Free
Rainbow in twinset for each
user who wants to use his
physical extension and the
Rainbow application to
manage his calls through the
WebRTC gateway
Here, a virtual terminal is

created for the user cCpP
admin
(C : Class, P : Pod)
1.2. Associate the Virtual Free Rainbow in Twinset terminal as a secondary set of the user's
primary extension
OMC/ Subscribers list

This Virtual Free Rainbow in
Twinset terminal must be
added as a secondary set of
the main extension of the user
4
2 Manage a Rainbow user in softphone mode, without a physical

extension
All communications are managed via the Rainbow app, web or mobile. Used in Softphone mode, without
physical set.
Create an Anydevice terminal: 133

This terminal will be associated with the Rainbow user account: cCpP.user1@ale-
training.com
Use in softphone mode
- Create an Anydevice terminal: 133
- This terminal will be associated with the Rainbow user account: cCpP.user1@ale-
training.com - Use in softphone mode
2.1. Create an AnyDevice terminal
OMC/ Subscribers list

Create an AnyDevice terminal
for each user who wants to
operate without a physical set
Example:
Here, an AnyDevice 133 is
created for the user
c2p1.user1
5
2.2. Assign the number 133 to the Rainbow member cCpP.user1@ale-training.com
Rainbow PC application or https://web.openrainbow.com

Click on Members
Select User1
Example :
c2p1.user1@ale-training.com
Select the Telephony tab
Select OXO Connect from the

list ("Equipment" field)
Select the extension number

related to the member: 133
Click Apply
6
3 User interfaces after configuration
3.1. Rainbow user interface in softphone mode, without physical set
cCpP.user1@ale-training.com: Number 133

The user has added his mobile number himself in his profile. He can choose his call routing and manage his
calls as he wishes from:
- His computer (Rainbow softphone)
- His mobile
- Other phone
- He can also forward his calls
7
3.2. Rainbow user Interface with physical extension and Rainbow application
cCpP.admin@ale-training.com: Number 100/104

The user has added his mobile number himself in his profile. He can choose his call routing and manage his
calls as he wishes from:
- His office phone
- His computer (Rainbow softphone)
- His mobile
- Other phone
- He can also forward calls
Rainbow
Attendant Console
Rainbow attendant console
Available for OmniPCX Enterprise and OXO Connect
Attendant console allow to

•Supervise member status
•Presence and call control
•Call queue management
•Manage up to 10 calls for OXE
•And up to 8 calls for OXO Connect
•Manage calls for supervised members
•Pick-up calls, call transfer, voicemail forwarding, forwarding status…
Members & attendant must belong to the same supervision groups (administrator)
•Supervision of a company department, e.g
An Attendant subscription is required for each member using this feature

•Available on the Rainbow Web and Desktop applications
•Attendant console not available on mobile. It delivers Business/Enterprise services.
•An Attendant user must have a telephone line, as well as VoIP softphone capability
Attendant console – In conversation
Call Control of
Call queue current
(X calls) communication
Attendant console
Supervision
groups
Busy lamp field

area
(Supervision)
Attendant console – Idle state
Attendant console
Supervision groups
In order to supervise the members of a company, users with the attendant
subscription, and the supervised members must belong to a supervision group
Each supervision group includes

• One or several supervisors: they must be granted an Attendant license to use the attendant
console
• The company members to supervise
Maximum number
of supervision
groups for a 5
supervisor
Maximum number
of users in a
group (supervisors 30
+ supervised)
Supervision groups
Principle
• Each tab represents a group, as defined by an administrator
• A call indicator (red dot) appears on groups whose tab is not

visible
• An audio notification is possible, as an option, to signal calls

presented to the supervisees
• An additional tab reproduces the list of the supervisor user's

favorites
Possible actions
• Interception of phone calls presented on supervised users
• Forward of supervised persons can be forced (to voicemail) or

cancelled
Misc
• The attendant may have a deskphone, but none of the functionalities are possible
Attendant features are only available on the deskphone itself.
on PC (thick client or web mode): • Same behavior for a smartphone
• The number of calls that can be put on hold, depends on the multi-line resources
All phone calls are handled by the assigned to the Attendant's softphone line :
PBX • REX on OXE : Up to 10 calls
• AnyDevice on OXO Connect (minimum R6 version) : Maximum 8 calls
Consult the technical communication

for the OXE (TC2462) or OXO Connect
(TC2479) for Rainbow configuration
• Interception is only possible if supervisors and supervisees are on the same PBX.
Supervision : Only phone calls can be intercepted.
Rainbow Hub
Attendant console
How to
✓ Assign Attendant console subscription to a member and manage supervision groups
Contents
1 Subscribe to ATTENDANT subscription ..................................................... 2
2 Assign the ATTENDANT subscription to a member ....................................... 3
3 Supervision group ............................................................................. 4
4 Console attendant view ...................................................................... 6
2
Attendant console
Implementation
1 Subscribe to ATTENDANT subscription
- Subscribe to the service “ATTENDANT”
Companies/Customer companies/ <company to manage> “Subscriptions” section /

Service : ATTENDANT
Click
"Subscribe to offer"
Choose the subscription offer:
Attendant Monthly
DON’T USE “PREPAID” IN

THE TRAINING
3
Attendant console
Set the number of licenses: 1
Click on Subscribe
2 Assign the ATTENDANT subscription to a member
Associate the subscription to a member of your company

- Example: cCpP.user1@ale-training.com
“Members” section / Edit the user/ “Services” tab

Select subscription “Attendant
Monthly“
4
Attendant console
3 Supervision group
Create a supervision group
- Supervisor: cCpP.user1@ale-training.com (with the ATTENDANT subscription)
- Members to supervise: Add all other users of your company
Log in with cCpP.user1@ale-training.com to supervise the group members
Companies/Customer companies/ <company to manage>

“Communication” section / “Supervision” tab
Click on “Create”
Complete the fields
And click on “Create”
Name Define a group name

Description Enter a description
5
Attendant console
Select the supervisor with a

ATTENDANT subscription
Select the members who will

be supervised
6
Attendant console
4 Console attendant view
- Log in with cCpP.user1@ale-training.com
web.openrainbow.com or application
Click on to access
Attendant console
OXO Connect
Actions to perform at the END of a training
Actions to perform at the END of a training
Erase the MLAA voice guides if used
Clear ACD voice guides if used
Return to ACD / SCR factory settings if used
OXO Cold Reset with the following settings:

•User data
•System data
•Cloud connect data
•Network, installer passwords and management data
OXO Connect
OXO hardware: Interfaces boards for the Racks
Boards position
Equipment board installation rules

• Usually, equipment board are installed in the rack according to the ascending order of the slots and the restrictions
1 2 CPU Slot
3 4 5
Slots without any restrictions
6 7 8
Boards restrictions
1 2 CPU Slot SLI16, DDI2, DDI4
APA8
3 4 5
MIX, AMIX, UAI-16
1 2 CPU Slot
Boards
UAI, digital sets connections

• Used for ALE Hybrid digital phones
• Used for IBS DECT base stations (with one or two links)
ALE Hybrid digital IBS DECT

Boards
MIX and A-MIX boards connections

PSTN
• Used for ALE Hybrid digital phones (UA)
• Used for IBS DECT base stations (with one or two links)
• Used for analogue sets (Z) connections
• Used for trunks connections
• MIX: T0 trunks
• A-MIX: APA trunks
ALE Hybrid IBS DECT Analog phones

digital
Boards
SLI, analogue sets connections APA, analogue trunks connections

• Used for analogue sets (Z), fax or modem connections • Used for APA trunk connections
PSTN
Analog phones
Boards
BRA, basic accesses T0 connections PRA, Primary accesses T2 connections

• Used for T0/DLT0 trunk connections • Used for T2/DLT2 trunk connections
• DLT0 for private network • Only one port can be used at the same time
• DLT2 for private network
PSTN PSTN
OXO Connect
PowerCPU EE Start and Stop
Start the system
Press the front switch on the

main CPU (power on)
Startup monitoring
Step 6 Step 5 Step 4 Step 3 Step 2

Step 7 Detection of Detection of Step 1 Step 0 Basic
Detection of Init of the Init of the configuration
Init of the the cards of the cards of End of the Starting of (Initial
the cards of extension extension
main the the phone start the VoIP Installation
the main cabinet 1 cabinet 2
cabinet extension extension up ( VMU ) services Wizard)
cabinet (HSL1) (HSL2)
cabinet 1 cabinet 2
Stop the system
The shutdown stops • When the CPU is shutting down the Power LED blinks in red
correctly the CPU and rack • When the CPU is stopped the Power LED is steady red
power supply
Manual Shutdown (On/Off • To switch off the system

Button) • To change CPU board
• In case of power supply problem

Automatic Shutdown • Problem of batteries
• Software or hardware anomaly
OXO Connect
Installation Wizards
Presentation
Wizards are integrated tools used to optimize the installation: quick, friendly-to-use, easy-to-use
The installation Modification

wizard wizards
Objective: Manage a basic Objective: Basic
configuration of the modifications on a existing
2 types system configuration
of •The system must be in initial •These wizards allow
wizards state modifications on:
•After the first system starting •System settings
up •External accesses
•After a cold reset •Users
•Wizard using: from OMC or from •Groups
a phone 8068s, 8078s ou 8039 •Common speed dial repertory
•DECT
•Wizard using: from OMC only
Phone set installation wizard stages
Define the basic system configuration
Start
System: operation mode Business or hotel
Installation number
IP addresses modification/VLAN/DHCP
Internal numbering plan
Define public extension numbers
Number of trunks to public network
Subscriber modes
Operators modes
Terminals Mailboxes
DECT ARI number*
Subscribers language
Basic metering unit cost

At the first system starting up or after
Time and Date
a cold reset
Restart the system in new configuration
Finish
OMC installation wizard
Start the OMC installation wizard for initial installation
Select the Business or Hotel Installation Wizard

OMC installation wizard stages
Start
1. LAN configuration\Boards\DHCP 10. List of Users
2. Default Dialing Plans 11. User misc.
3. Installation number 12. Common speed dial
4. Operation mode
13. Attendant groups
5. Channels in main trunk group

14. Hunt groups
6. DECT ARI*
15. Broadcast groups
7. Handset creation
16. Pickup groups
8. Charge rate
17. Screening
9. Date and time End
Installation Wizards - Modification wizards
The Modification wizards allow simple and fast system modifications on an existing
configuration
Contrary to the installation wizard, modification wizards are accessible constantly

OXO Connect
Initial installation wizard
How to
✓ Make the initial configuration wizard of an OXO Connect from the
phone set
Contents
1 Wizard Business mode by phone set ........................................................ 2
2 Installation Wizard parameters ............................................................. 3
2
Implementation
1 Wizard Business mode by phone set
The OXO Connect must be in default configuration, i.e. during its first commissioning or
after a cold reset.
Start the Installation Wizard from a phone set with a large display with access to the
Operator menu
From the operator set with a large display
Check that the OXO is in

default configuration,
if this is not the case do
a cold reset.
On the attendant set

display you should see
“Define the Basic
System Configuration”
Otherwise press
"Operator"
Click on “Go on” to

begin
Note: the initial installation wizard can also be done with the PC via the
'Installation Typical’ menu in the start screen of the OMC
3
2 Installation Wizard parameters
Enter the following parameters

- Installation number: 0210141100
- IP address of the CPU: 192.168.1.246
- Numbering plan type: 3 digits national numbering plan
- Subscriber management:
Internal Numbers DDI number

100 41100
101 41101
- Main trunk group with 2 B channels
- Language: English
From the operator set with a large display
Choose the system

operation mode
Business or Hotel
Business in our case,

and click on “Next”
Note: the Initial Installation Wizard is the one and only way to put
an OXO a Hotel mode
Fill in the installation
number “Public Netw
Nbr”
4
Modify the network

configuration if
necessary.
Enter the CPU IP@,

“MAIN@”
Validate with “OK”
button.
Press the down arrow to

see the “Next” button
because it is hidden by
default.
5
Choose a 3-digits
internal numbering
plan.
Define the public

numbering plan.
Press “choice”
Fill out the first DDI

number “Public Ext”
then “Down” for the
next DDI number etc.
6
When all DDI numbers

are entered, then
choose “OK All”.
Enter the Number of

Trunks to Public
network (channels in
the main trunk group).
Define the management

mode for users and
operators.
PBX mode for users and

Intercom mode for
operators.
7
Choose the Mailbox

generation type All
Terminals, or None
Choose the Language
This step activates the

metering feature with a
Charge rate per Unit.
Leave to default
settings.
8
Configure Date and time
Installation is now
finished.
Click on “Finish” to
restart the system in
new configuration.
OXO Connect
8328 base stations and 8214 handsets classroom installation
How to
✓ Manage 8328 base station and 8214 handsets
Contents
1 Deployment of an 8328 base station ....................................................... 3
1.1. Configuring the OXO DHCP Server ................................................................ 3
1.2. DHCP settings in the OMC ......................................................................... 3
1.3. Initial Setup of the 8328 DECT Base sation with Web Admin ................................. 3
2 Deployment an 8214 Handset ............................................................... 7
2.1. Creating the handset in the OXO ................................................................. 7
2.2. Handset configuration in base station 8328 .................................................... 9
2.2.1. Handset Registration ....................................................................................... 9
2.2.2. Starting Registration on the 8214 Handset ............................................................ 10
2.2.3. Declaration of the extension............................................................................ 11
2
Implementation
The following procedure describes the declaration of an 8214 DECT handset on a single-cell
8328 base station. More information can be found in the document 8328 SIP-DECT SINGLE
BASE SATION – System Guide, available on the Alcatel MyPortal website.
3
1 Deployment of an 8328 base station
1.1. Configuring the OXO DHCP Server
The factory IP configuration of an 8328 base station is a dynamic IP configuration. Therefore, a DHCP
server must be present and configured in order to respond to the request from this DECT 8328 base
station.
Manage the OXO DHCP server here in order to address the 8328
1.2. DHCP settings in the OMC
OMC/ hardware and limits / LAN/IP Configuration / DHCP tab

Enable the built-in DHCP
server
Enter the @IP range

192.168.1.10 to 192.168.1.69
IMPORTANT: Don't forget to activate Auto-Provisioning in the menu of the Subscribers/Basestations List.
Notes
Connect the 8328 to the IP network using an Ethernet cable. After a while, it should flash green, which means
it has received its IP settings and can access the network.
1.3. Initial Setup of the 8328 DECT Base sation with Web Admin
Using the 8328 administration web interface, configure the following settings :
- Country : France
- NTP Server : 192.168.1.254
- OXO Server Declaration
Tips
If you don't know the IP address of the base station 8328, for example, if its MAC address has not been specified
in the DHCP server to provide a fixed IP address, you can use an 8214 handset to find it out. To do this, on the
handset in the idle state, press the "menu" button, then dial *47*, you will access the base station search
function :
4
MENU
Start a web browser and enter the IP address of the kiosk as the URL:
Browser : https//<8328 station IP @>
Enter the credentials
For example, 192.168.1.17
Username admin
Password admin (by default)
5
Country
Once connected, go to the
Country section to manage
the country and NTP server
Select country Select your country. Example here: France

Time server Enter the IP address of the R-lab NTP server: 192.168.1.254
Network
In the Network section, verify
that the address(es) of the
DNS server(s) were provided
by the DHCP server.
6
Servers
In the Servers section, declare

the OXO as a SIP server.
Fill in the fields
Alias = OXO for example
Registrar = 192.168.1.246
Registration time = 3600 sec.
Fill in the fields
Sipping 19 = Disabled
Remote Caller ID Source

Priority = ALERT_INFO – PAI –
FROM
Click on Save
7
2 Deployment an 8214 Handset
2.1. Creating the handset in the OXO
A SIP extension must be declared for each user using an 8214 handset registered on an 8328 base station.
Create a user with the following settings:

- Directory Number: 120
- Extension Type: Open SIP Phone
- SIP Password: Enter a password
OXO Management Tool

OMC: Subscribers/Base stations List
Add an IP Terminal
Choose a free directory

number from the dial plan,
example 120
Type of terminal, declare it in

Open SIP Phone
Terminal Details
IP/SIP Button
SIP Parameters Tab
Make a note of the SIP

password that will be used
when the extension is created
in 8328 base station
8
Change the VoIP Flag in

Advanced Settings:
OMC/Voice over IP/VoIP

Parameters/Advanced
no_pack_support_for_siphone
set its value to true
9
2.2. Handset configuration in base station 8328
2.2.1. Handset Registration
Declare a new handset and register it at 8328 base station.
Using the base station webadmin interface :
Extensions / Handset
Click on "Add Handset"
Click on "Save"
Check the row in the table

corresponding to the new
handset that has just been
declared and is to be
registered.
Then click on "Register

Handset(s)"
Perform the registration

action on the handset itself
(see section 2.2.2)
10
2.2.2. Starting Registration on the 8214 Handset
Perform the registration action on the handset.
To carry out the registration, the AC (Authentication Code) may be requested
Tips
The access code is visible in the webadmin interface and can be changed :
On the DECT handset

If the handset is in factory
configuration (first
installation) or is no longer
registered on the system, at
startup, it must offer
registration:
Auto Install?
Press the "SIP" choice using

the left button.
Enter the handset PIN if

prompted (0000 by default).
Then enter the AC code

specified in the 8323 base
station management:
➢ 0000 (default)
After a while, you will receive

a message to inform you of
the successful registration:
Registration success !
After a while, the "home

page" will indicate that there
is no SIP registration, which is
normal, as this step is going to
be done in the next step.
11
Using the webadmin interface of the base station :
Extensions / Handset
Looking at the table, the
handset is now registered.
The IPEI number is no longer
the generic/default number
(FFFFFFFFFF)
2.2.3. Declaration of the extension
Declare an extension and make the association with the handset that has just been
registered
- Directory number: 120
- Authentication information (number and password created in the OMC)
- Server: OXO declared in point 1.2
Using the webadmin interface of the base station :
Extensions / Extensions
Click on "Add extension"
12
Enter required fields
Enter the directory number.

For example, 120
Enter the SIP authentication

login. Example 120
Enter the user's SIP password.

Example
Enter the extension's

voicemail number. For
example, 120
Enter the voice server dial-in

number. 67 in the OXO
internal numbering plan
Associate the extension with

the handset registered before:
Tick the box for the available
handset
Then click on the "Save"

button at the bottom of the
page:
In the table, we can now see

the extension-handset
association: the IPEI is
assigned to extension 120
13
On the handset, you should now have:
On the handset screen

The name of the terminal is
displayed.
The handset is associated with

the extension.
Test handset operation:

- Call another user of the system from the handset
- Call the DECT handset from another user
END OF TRAINING EVALUATIONS
C L A S S R O O M S E S S I O N O R V I RT U A L C L A S S S E S S I O N
YOUR FEEDBACKS ARE
IMPORTANT!
Thank you to complete the training

evaluation online survey before leaving
your session. This will take you 2 minutes!
You must complete the end of training

evaluation to be able to download your
training certificate of attendance.
LOGIN TO ALE KNOWLEDGE HUB
• Connect to ALE Knowledge Hub (https://enterprise-education.csod.com ) with your usual

credentials
ACCESS TO THE ONLINE EVALUATION SURVEY (1/2)
• Click on My Training on the home page
• Search for the training course by the reference provided by your instructor
ACCESS TO THE ONLINE EVALUATION SURVEY (2/2)
• From the session, select Evaluate in the dropdown menu and follow the instructions
OR
• From the curriculum, select Open Curriculum
• Then select Evaluate in the dropdown menu associated to the session and follow the
instructions
THANK YOU
Find a Course
Browse our catalog available on https://enterprise-education.csod.com/ to find your training path
and course detail.
Feedback
In order to improve the quality of the documentation, please report any feedback and address to:
Alcatel-Lucent Enterprise
115-225 rue Antoine de Saint-Exupéry
ZAC Prat Pip – Guipavas
29806 BREST CEDEX 9 – France
FAX: (33) 2 98 28 50 03
or mail to: emea.education-services@al-enterprise.com

OXOCXTE300EN

Uploaded by

Document Information

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

OXOCXTE300EN

Uploaded by

Copyright:

Available Formats

OXO CONNECT - R6.

by-step configuration of OXO Connect systems

The presentations are followed by han

by-step manager/secretary relations.

SIP carrier access

End of the course

Learners RLAB environment Pods are

Pods common resources

Session number / course ref / pod number

Access using RDP

• Host name: Client1 POD

• Mask: 255.255.255.0 VM PC Client

• Mask: 255.255.255.0 VM PC Client

▪ IP BOX used for Starter course

• Host name: Client1 POD

• Mask: 255.255.255.0 PC Client

▪ Credentials: no login, no password required

POD topology POD P (P is the POD number)

Network 192.168.1.x the RLAB common area

SIP Simulator details Public and Emergency numbers

Call to Emergency numbers from your PBX

Call to Public numbers from your PBX

National numbers Mobile numbers International numbers

The main number of the SIP user Public is 3321PN12345.

National call (to area 1) Mobile call (to area 6)

SIP Trunk Group SIP Trunk Group ITSP1

SIP Trunk Group SIP Trunk Group ITSP1

Examples for POD 3 (PN = 03)

Call from Public user Call from PBX 3 (loop)

Installation number • 210P41000

High performance mobility Stylish, robust design,

Customer welcome company greetings, automated attendant, call routing…

Efficient desktop environment desk sharing, conference, groups…

Wireline DeskPhones digital, IP, SIP, analog

On-site mobility DECT, VoWlan

Off-site mobility Rainbow, OpenTouch Conversation…

Converged voice and data network

Hotel and hospitality features

MyPortal links for ALE employees

IP Pure IP – 300 users

Hybrid Hybrid TDM/IP - 300 users

OXO Connect Compact

WebRTC Gateway Compact Small Large 150W Evolution

Hybrid Digital/IP Phones

8088 ALE-2 ALE-3

8214 8234 8244 8254 8262/8262Ex 8158s 8168s

DECT Handsets WLAN Handsets Rainbow apps

Efficient Desktop Professional Greetings

One Number Service on any phone External Mobility

LAN Infrastructure Voice-over-WLAN infrastructure

SD card interface (rear side)

ETH1 can be used to easily start and configure OXO

OXO Connect Compact

OXO Connect Small

OXO Connect Medium

PowerCPU EE Front panel

Default hardware capacity

• Capacities according to VoIP Channels mode

OXO CONNECT DSP Number of VoIP channels

Multi-Codec 60x G711/G729 60

PowerCPU EE installation rules

AMIX, MIX and CPU positions in the Compact unit

PowerCPU EE alone, without local area network connection

Ethernet crossed cable