OMNIPCX ENTERPRISE - R100

8378 DECT IP-XBS & 8379 IBS

EDITION 07
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.
Training lab environment
OmniPCX Enterprise - DECT
Hybrid mode (RLAB + classroom equipment)

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
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.
POD CONFIGURATION
 Training platform
Pod P
OXE CSA IT SERVER
Phys: 192.168.1.1 192.168.1.252
Main: 192.168.1.3 NTP Server
Common resources

NAS: softs, licenses

192.168.1.254
OMS CSA CSB FLEXLM SERVER
192.168.1.13 192.168.1.80
Internal DNS
SIP simulator
10.20.30.254 Subnet 1 - 192.168.1.x
External DNS
10.20.30.x

Subnet 1 - 192.168.1.x RAP Classroom VLAN 1

PC Classroom

POE Switch

MIX484 GD4

192.168.1.12

xBS
DECT 8212 DECT 8234 DECT 82144
31017 31015 31016 ALE-30h ALE-500 ALE-300 ALE-20h
31020 31010 31011 31012
IBS xBS
RLAB dashboard

OXE

Flexlm Server

IT Server

OMS
Settings
Name Instance Name Hostname IP Address Subnet Mask Default gateway Login Password Comments

mtcl mtcl
csa (physical) 192.16.8.1.1
OXE DECT_OXE_CSA 255.255.255.0 192.168.1.254 swinst SoftInst
csm (main) 192.16.8.1.3
root letacla

OMS ENTP_OMS_CSA_CSB_NODE1 192.168.1.13 255.255.255.0 192.168.1.254 root letacla1

FLEXLM SERVER ENTP_FLEXLM flex 192.168.1.80 255.255.255.0 192.168.1.254 root letacla1

IT SERVER ENTP_ITSERVER iterver 192.168.1.252 255.255.255.0 192.168.1.254 training superuser NTP Server

CLASSROOM EQUIPMENT

PC CLASSROOM client 192.168.1.9 255.255.255.0 192.168.1.254 Administrator superuser IPDSP 31000

admin letacla1
GD4 192.168.1.12 255.255.255.0 192.168.1.254
root mg4.ale
NAS server
On PC Classroom:
▪ A network drive can be mapped to the NAS from the explorer.
▪ How to map
▪ Folder: \\10.20.30.40\softs
SIP Carrier Simulator

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
SIP Simulator overview - ITSP1 with one SIP Gateway

POD topology POD P (P is the POD number)

Outgoing call
Incoming call
PBX users
SIP Simulator
Public numbers
ITS1 ITSP1 National numbers
SIP Trunk Group Public Carrier International numbers
PBX (POD P)
ITSP2 Mobile numbers
SIP simulator is hosted in
Network 192.168.1.x the RLAB common area

SIP Simulator details

PBX (POD P)
ITSP1 SIP Gateway 1 ITSP1 Public gateway
gateway1.itsp1.com public.itsp1.com
10.20.30.51 10.20.30.50
Id: pbxP
password: alcatel

SIP domain:
SIP domain:
sip.itsp1.fr
itsp1.fr

Network 10.20.30.x
External calls

Pbx configuration
POD P POD 1 POD 2 POD 3 POD 4 POD 5 POD 6
PBX installation nb 3321PN 332101 332102 332103 332104 332105 332106
DDI table - First external nb 41000 41000 41000 41000 41000 41000 41000
DDI table – First internal nb 31000 31000 31000 31000 31000 31000 31000
Example: 31002’s external nb 3321PN41002 33210141002 33210241002 33210341002 33210441002 33210541002 33210641002

Example for POD 3 (PN = 03)

External call (loop)

31001
Dialed number:
0210341002 or 33210341002

Number sent by the PBX:

+33210341002
SIP Trunk Group ITSP1
Public Carrier
PBX
POD 3 Number received by the PBX:
+33210341002

31002
OpenTouch Suite for MLE
OmniPCX Enterprise

Pod Configuration for the labs

How to
✓ Configure the Pod for the labs

Contents
1 POD set up ..................................................................................... 2
1.1. OXE Preconfiguration .............................................................................. 2
1.2. Rack and boards .................................................................................... 2
1.2.1. Hybrid Mode (RLAB + Classroom equipment) ........................................................... 2
1.3. Users ................................................................................................. 3
1.3.1. Hybrid Mode (RLAB + Classroom equipment) ........................................................... 3
1.4. External SIP gateway ............................................................................... 4
1.5. DID Translation ..................................................................................... 4
1.6. External calls........................................................................................ 5

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
 2
Pod Configuration for the labs

Implementation

1 POD set up

Start all the Virtual machines:

1.1. OXE Preconfiguration

OXE VMs used for this training are already configured (Database and Linux Data), such as:
• Software licenses are restored
• SSH is disabled
• NTP Server (192.168.1.252) is declared
• FlexLM Server (192.168.1.80) is declared
• DHCP server is activated
o VLAN 1 IP @ range: 192.168.1.145….192.168.1.155
• Shelves / boards are created
• Users (Deskphones & softphones) are created
• Voice guides are downloaded
• Public SIP trunk group is created

1.2. Rack and boards

Racks and boards are created in the OXE database.

1.2.1. Hybrid Mode (RLAB + Classroom equipment)

Please check (or configure if needed) that the equipment, available for this training, is
in service (with the following parameters):

For the MAIN site

• Hardware Rack 1U
o Rack N° 2
o GD4 (slot 0) IP @: 192.168.1.12/24
o GD4 MAC @: to be checked in the classroom
o MIX484 (slot1)
• Software Rack 3U (OMS)
o Rack N° 4
o Virtual GD4 (slot 0) IP @: 192.168.1.13/24
o Virtual GD4 MAC @: 00:50:56:01:01:13
 3
Pod Configuration for the labs

1.3. Users

1.3.1. Hybrid Mode (RLAB + Classroom equipment)

Users are created in the OXE database.

Bring into service the IPDSP softphone and Deskphones as mentioned in the table below.

Directory Nb First name / Name Set Type Comment

31000 Brad Barkley IP DSP Installed on PC Classroom
31010 Charles Cooper ALE-500 (IP NOE) Dynamic IP @
31011 Calixta Cartier ALE-300 (IP NOE) Dynamic IP @
31012 Caitleen Connor ALE-20H (IP NOE) Dynamic IP @
31020 David Douglas ALE-30H (TDM/UA) -

Don’t forget to specify the TFTP server IP @ in the IP DSP settings.

IP DSP
Do a right click and go to
“Settings”

Select the “Network” tab

And enter the right TFTP

server IP @ (OXE CS Main IP
@)

TFTP Server Main 192.168.1.3

 4
Pod Configuration for the labs

1.4. External SIP gateway

The Public SIP trunk group is already configured in the OXE database, but you must specify your own
“POD” parameters into the external SIP gateway, to activate the access to the public SIP carrier

According to your POD number, configure 2 parameters in your external SIP gateway:
• Registration ID: pbxN (where N is your POD Number)
o e.g.: for POD 3, pbx3
• Outgoing username= pbxN (where N is your POD Number)
o e.g.: for POD 3, pbx3

SIP/SIP Ext. Gateway

Select your external SIP
gateway

Registration ID pbxN (where N is your POD number)

For POD 3: Registration ID= pbx3
Outgoing username pbxN (where N is your POD number)
For POD 3: Outgoing username= pbx3

1.5. DID Translation

The DID translation of your system must match your POD number.

According to your POD number, configure the DID translator as follow:

• First external number: 33210N41000 (where N is your POD Number)
• First internal number: 31000
• Range size 500
 5
Pod Configuration for the labs

Translator/External Numbering Plan/Default DID num. translator

“create” button

First external number 33210N41000 (where N is your POD Number)

For POD 3: First external number= 33210341000
First internal number 31000
Range Size 500

1.6. External calls

To make sure that access to public SIP carrier is working properly, set up some outgoing
calls.
Refer to the document SIP Carrier Simulator to know how to use the SIP simulator.
OpenTouch Suite For MLE
OmniPCX Enterprise Communication server
DECT – Overview
DECT Standard

◼DECT for
⚫ Digital
⚫ Enhanced
⚫ Cordless
⚫ Telecommunications

◼The DECT standard is published by the ETSI

⚫ ETSI: European Telecommunication Standard Institute.

◼DECT was developed as a European standard since 1993 and was later adopted by more than 110 countries
⚫ It is considered as a world-wide standard for cordless telephony applications
⚫ In United States it has been adopted in 2005
⚫ Japan is still using an other technology (PHS) since 1995
DECT overview

The DECT protocol is used between a

cordless set and a DECT interface for
accessing to the PABX
DECT Base station DECT handset
Based on cellular technology

Frequencies used according to the countries:

1880 MHz – 1900 MHz European
1900 MHz – 1920 MHz China UA Protocol DECT Protocol
1910 MHz – 1930 MHz Latin America OXE
1920 MHz – 1930 MHz North America

OmniPCX Enterprise

High-density traffic (up to 10000

E/Km2).
DECT elements

DECT radio coverage

Base stations
The radio coverage over a base station
is called a cell DECT
DECT

DECT Cells
OXE
DECT offer

The OmniPCX Enterprise offers various hardware configurations to implement the DECT service

DECT Offer

Low-cost DECT mobility

TDM offer VOIP offer for users connected
to small PCX configurations

4070 DECT RBS

Crystal or common Crystal or common
Crystal hardware
hardware hardware

RBS : Radio Base IBS : Intelligent

xBS
Station Base station
8379 DECT IBS

Connected on a Connected on an UA Connected to the

DECT board board customer LAN 8378 DECT IP-xBS
DECT characteristics

Radio transmission
Radio power 250 mW

Passband 1880/1900 MHz (Europe)

Channel bandwidth 1,728 MHz

Transmission carriers 10
Frequency band
Carrier spacing 2 MHz ¬ Europe: 1.88 GHz – 1.90 GHz
Time multiplexing inside 12 TSs for reception (direction: ¬ US: 1.92 GHz to 1.93 GHz
each carrier for RBSs base station –> handset) ¬ South America: 1.91 GHz to 1.93 GHz
• 12 TSs for transmission (direction: ¬ Except Brazil: 1910 to 1920 MHz
handset –> base station) ¬ Asia: 1.90 GHz to 1.906 GHz
That is, 120 multiplexed radio channels
Time multiplexing inside 6 TSs for reception (direction:
each carrier for IBSs base station –> handset)
• 6 TSs for transmission (direction:
handset –> base station)
Time multiplexing inside 12 TSs for reception (direction:
each carrier for xBSs base station –> handset)
• 12 TSs for transmission (direction:
handset –> base station)
That is, 120 multiplexed radio channels
DECT characteristics

◼Radio multiplexing

FDMA : Frequency-Division Multiple Access

TDMA : Temporal-Division Multiple Access TDD : Temporal-Division
Duplex
Consists of dividing the It consists in dividing the Is a technique allowing a
bandwidth of the communication time, for example every telecommunication channel using
medium into separate frequency second, into small intervals, the same transmission resource (a
bands. Channel 1 data will be radio channel for example), to
and assigning a given time multiplex in time the transmission
transmitted in band A, channel 2
will be transmitted in band B, interval to each channel and the reception
and so on.
DECT characteristics

◼DECT Frequency division

1.728 MHz
2 MHz

F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 Frequency

10 transmission carriers
DECT characteristics

◼Temporal division inside each carrier

10 ms
12 time slots : base station to handset direction 12 time slots : handset to base station direction

24 time slots
per frame 0 1 11 12 23

32 bits 392 bits 56 bits

Synchro Data Hold Each DECT frame is 480 bits

Field A - info CRC Field B - voice

32 bits 16 bits 320 bits

Field A: command and signaling throughput 6.4 Kbit/s

Field B: voice throughput 32 Kbit/s
DECT characteristics

◼DECT frame structure

Timeslots
OXE

0 1 2 3 4 5 6 7 8 9 10 11 0 1 2 3 4 5 6 7 8 9 10 11
0
1
TS4 (up) 2
TS4 (down)
3

Carrier 4
(Frequencies) 5
TS2 (up)
TS2 (down) 6
7
8
TS9 (up) 9
TS9 (down)

Data base to the handset Handset to the Database

DECT characteristics

Non adjacent cells can use the same channel

( frequency + timeslot)

Cell size and traffic density

F0 to F9

The power of the transmitters is constant Frequency:

(around 250 mW)
F0 to F9

The range of a transmitter ( the cell size)

depends on the environment (walls, ceilings,
metallic screens, presence of sources of
interference)

Cells may overlap partially or totally to

increase traffic density

10 transmitters (frequency), means the

channels can be used again by a non-adjacent
cell Two base stations to increase the traffic density
(Cells overlap totally)
Identification numbers

◼ Each element of a DECT communication is

identified by an unique specific number
⚫ Allows the handsets to know on which system they can
be locked
RPN PARK
⚫ Allows the DECT system to identify each handset RFPI
DECT PLI
PARI IPUI
IPUI

OXE

PARI: Primary Access Right Identifier, identification of the PABX, made of 31 bits or 8 hexa decimal digits
RPN: Radio Part Number: coded in two hexadecimal digits
RFPI: Radio Fixed Part Identifier, identification of the Base station composed of the PARI and of the RPN
PARK: Portable Access Right Key, identification of the DECT system in the set that corresponds to the PLI + the PARI
number of this system (coded in 13 digits)
PLI: Park Length Indicator (maximum value 31)
IPUI: International Portable User Identity, identification of the handset international number written in the EPROM of
the set composed by 14 octal digits
Identification numbers

PARI

OXE
• Number programmed in
the system
• 31 bits coded in 11 octal
digits
PARI: Number • A different PARI is
identifying the mandatory per type of
PBX DECT hardware deployed
on an OXE
• IBS
• RBS
• xBS

Example:
➢ PARI in binary : 001 000 000 000 000 100 001 010 011 100 1(00 fixed)
➢ PARI in octal : 1 0 0 0 0 4 1 2 3 4 4
Identification numbers

RPN

• Id allocated to the base

station by the PBX
RPN: Number • The base station
identifying the creation (IBS system)
base station • DECT board creation
(RBS system)
• The IP-xBS registration
Identification numbers

PARK

PLI
• Number sends in the
PARK: Number handset set at the IPUI
registration
allowing the PARI and PLI Information are received by the Handset
• The PARK is composed of
handset to 13 digits at the registration stage
recognize the • PLI value (2 digits in
system decimal form) + PARI (11
digits in octal form)

Example:
PLI=31 and PARI=10000400100 → PARK=3110000400100
Identification numbers
PLI Information is received by the Handset
at the registration stage

PARK
• The PLI determines how
many bits, of the PARI PLI
received from the base
station, must be
compared to the local IPUI
PARK
PLI: Number
• If the PLI is decreased,
of binary the handset is compatible
elements with more PARI
analyzed in • Used in a Multi PARI
the received configuration
PARI number • Number sends to the
handset at the
registration
• Number programmed in
the system
Identification numbers

 One PARI PARK

RPN PLI
DECT
PLI = 31
IPUI
PLI = 31 PARI =10000412344

OXE

PARI in octal 1 0 0 0 0 4 1 2 3 4 4
PARI in binary 001 000 000 000 000 100 001 010 011 100 100
Logical AND
PLI = 31 111 111 111 111 111 111 111 111 111 111 1xx
Result 001 000 000 000 000 100 001 010 011 100 1xx

The 31 digits of the PARI are taken into account by the set
Identification numbers

 Multi PARI RPN

PARI =10000412340 PARK

PLI = 29 PLI
PLI = 29
IPUI
OXE
RPN
PARI =10000412350

PARI 1 1 0 0 0 0 4 1 2 3 4 0 PARI 2 1 0 0 0 0 4 1 2 3 5 0
Binary 001 000 000 000 000 100 001 010 011 100 000 Binary 001 000 000 000 000 100 001 010 011 101 000
Logical AND Logical AND
PLI = 29 111 111 111 111 111 111 111 111 111 110 0xx PLI = 29 111 111 111 111 111 111 111 111 111 110 0xx
Result 001 000 000 000 000 100 001 010 011 100 0xx Result 001 000 000 000 000 100 001 010 011 101 0xx

29 Digits are taken into account Don’t care 29 Digits are taken into account Don’t care
Identification numbers

PARK
Example:
IPUI in octal: 0 0 0 0 0 3 5 1 4 7 6 7 6 0 PLI
• Number identifying the
IPUI: handset IPUI
International • Number fixed in the
Portable User memory of the set
Identity • 14 figures in octal
Identification numbers

RPN RFPI
DECT

IPUI
• Number emitted by the
RFPI: Radio Base Station
Fixed Part • The RFPI number contains
Identifier the PARI and the RPN
numbers
DUMMY channel

Time-slot (or channel) used for signaling exchanges between the system and
the handsets

The couple TS/F (Time Slot/Frequency) is randomly chosen by the Base station

It contains:

• In the transmission side

• The RFPI number
• The next analyzed frequency for the free reception TS
• The already used TS-F (Time slot/frequency) couples by the other handsets
• The broadcast data allowing the base station to present a call to a set
• In the reception side
• The IPUI of the handsets locked on this Dummy channel
• Used by the base station for the localization
The roaming

Allows the user to make or The handset must be

The system permanently
receive calls from any permanently active and have
monitors the position of each
location in the PCX coverage been previously registered on
mobile in the coverage area
area the system

Roaming implements a The handset moves over the

mechanism whereby the radio coverage (Roaming) and
mobile is recognized by the the Base station must be able
system (and vice versa), to find it (Localization) when
called the "location phase“ a call is received
Roaming

Location phase description

Identification numbers

The handset
The handset
regularly scans all The mobile selects
transmits its
radio channels in the base station
information (IPUI +
order to measure with the most
the signal strength powerful signal
PARK) to the base PARI Base station Hanset
station RFPI
of each one

OXE
Once recognition
The handset IPUI + PARK
The Base station has been
compares system
returns its RFPI performed, the
PARI with its PARK
number mobile “locks onto”
number
the system

user can make and

receive calls on his
mobile
Handover

Process permitting a transparent change of Base Station

during a communication

In order for handover to be possible, all the base station must

start their DECT frame at exactly the same time. This
condition implies highly accurate synchronization
Handover

Handover procedure description

1 2
While communicating on the When the handset must
initial channel handover from one base
•The handset scans the other station to another 1
channels • A second radio link to the future
•Qualifies these channels and base station is established
identifies the base stations offering •The handset is transmitting to the
the best transmission conditions two base stations simultaneously

3
When the new link is
established, handover takes
3
place:
Handover is completely
•The voice signal uses the new transparent for the user
channel and the old channel is
released
DECT capacity

RBS IBS IP-xBS

DECT calls per base 11 3 or 6 11

station
Number of PARI 8 1 8

Base station per PARI 256 256 254

Base stations 1000 256 2032

supported by a system
DECT handsets

◼GAP protocol
International and multi-manufacturer
⚫ Generic Access Profile
protocol

Allows the connection of all GAP

handset on any GAP reliant system

Automatic on-air registration

Provides basic services:

UA CLIP
Level of Mono-line extension

GAP services Access to the various services by prefixes

and suffixes
DECT handsets

◼Protocol GAP + (or A-GAP)

⚫ Alcatel Generic Access Profile Alcatel-Lucent protocol

Specific protocol based on the GAP

protocol

Automatic on-air registration

UA Provides the advanced services:

A-GAP Level of
Multi-line extension
services
GAP
Supervision key

Manager/Assistant extension with screening /

un-screening keys
DECT handsets

Supported Handsets

• A-GAP Mode
• 8234,8244 and 8254
• 8232,8242,8262 and 8262EX 8242 DECT handset 8262 DECT handset
• GAP mode
• 8212
• 8234,8244 and 8254
• 8232,8242,8262, 8262EX

8212 DECT handset 8232 DECT handset

8234 DECT handset 8244 DECT handset 8254 DECT handset

DECT handsets
DECT handsets

8234 8244 8254

Key highlights ALE features and Large backlit screen and Large backlit screen, IP65,
at a glance navigations Bluetooth headset antibacterial

Rainbow connected ◼ ◼ ◼

Industry/mission-critical features - Emergency Alarm / -

Notifications

Bluetooth Low Energy (beacons) - ◼ -

Bluetooth headset - ◼ -

Programmable keys 0 2 0

Screen size Standard Large Large

Backlit / color screen ◼/◼ ◼/◼ ◼/◼

Hands-free speakerphone ◼ ◼ ◼

Talk time before recharge 20h 17h 20h

Enterprise directory ◼ ◼ ◼

ALE twinset with business phone ◼ ◼ ◼

ALE features and navigation ◼ ◼ ◼

Reliability: Ingress Protection IP40 IP40 IP65

Radio DECT AGAP DECT AGAP DECT AGAP

DECT Synchronization

The system needs to use a very

accurate clock for DECT functions
• stable system synchronization The clock is used to synchronize
the base stations for the Hand-
over functions (else loss of the
communication)

TDM offer IP-xBS offer

• The clock is received from the • Synchronization is done over the
public network or made by a air from a master base station
system board
• OXE Synchronization
management
DECT Synchronization

◼TDM synchronization

• The base stations synchronization is made by

the DTM function from a DECT8 board or by
the CPU
Crystal hardware • Remote IP shelves
• INTIP3 provides the synchronization to the
local ACT (and sub levels if they exist) with
its own DTM (no DECT8 use)

• The GD provides the synchronization for a

Common hardware Common hardware rack
LAN
DECT Synchronization

◼IP-xBS Synchronization over the air

OXE Call Server

xBS-1 The IP-xBS base stations are synchronized

Master together over the air

xBS-4 xBS-2
The clock synchronization is managed by the
IP-xBS subsystem

They are also able to clock synchronize with

TDM base stations (IBS or RBS, but not both
together) over the air
xBS-3
xBS-5 xBS-6

Over the air synchronization

DECT security

◼Three levels of security

Encryption
mode
• The encryption
procedure is
Authentication initiated at call
mode setup
• The authentication • Once the
procedure is used authentication
when: procedure has been
• The handset is performed
installed • “Encryption” mode
Identity mode enables the signaling
• A call is setup
• This operating mode and data exchanged
• The mobile is between the mobile
is based on located (after an
verification of the and the system to
area change) be encrypted
IPUI-N number which • The handset is
authorizes a mobile to uninstalled
make or receive calls
DECT security
How it works ?
Authentication
• The UAK key (128 bits) used for calculation of the
code is registered in each mobile and in the database
of the system where the mobiles are installed
• It is calculated from the AC (Authentication Code)
validated for the mobile.
• It is never transmitted by radio channel or on a logical
link

System Authentication Code : AC system Encryption

• Authentication and Encryption need an unerring key which is used
both in the handset and the PBX . This key (128 bits) is called UAK • In order to cipher conversations, a special random key (64 bits)
for User Authentication Key. For security reason, it can’t be is derived from UAK
broadcasted. • This key is called DCK for Derived Cipher Key
• Handset and PBX have to build the UAK key from a common value • A new DCK is computed at the beginning of each call and is
which has to be known by the PBX and by the handset user maintained during the whole conversation, including
• This value is called AC for Authentication Code. conversations with handover(s).
• A registration phase isn’t possible if the AC key used in the PBX is • This key is never broadcasted or transmitted between PBX and
different from the AC key used in the handset the handset.
• It remains stored both in handset and the PBX until the set is
de–registered.
DECT security

◼Restrictions

⚫ For a DECT system in an IBS configuration, the system's security level is limited to “Authentication” mode

⚫ “Encryption” mode works only with the Crystal hardware

 The system must include at least one of these boards:
 A DECT 8 board (DTM module integrated)
 A CPU7-2 or CPU8 board (DTM module integrated)
 An INT-IP3B board (DTM module integrated)
OpenTouch Suite for MLE
OmniPCX Enterprise Communication server
8378 DECT IP-xBS - Overview
Lesson Summary

◼Overview
⚫ Branch offices
⚫ Mixed mode
⚫ Architecture
⚫ Base station IP xBS
⚫ DECT handsets
⚫ Description
⚫ Synchronization over the air
⚫ Time management / Daylight Saving Time
⚫ xBS base station web based management
8378 DECT IP-xBS - Overview

◼IP-xBS is a DECT mobility solution with base stations connected via the IP network and clock synchronized
over the air

Sync Sync
IP-xBS
LAN
IP-xBS IP-xBS
OXE
Sync

IP-xBS
8378 DECT IP-xBS - Overview

◼Branch Office

Branch Office
Head Quater

IP-xBS

IP-xBS

OXE Sync
Sync
WAN

Sync
IP-xBS IP-xBS

IP-xBS IP-xBS

Branch Office
8378 DECT IP-xBS - Overview

This new base station offers extension and migration solutions for installed base

From the user point of view there is the same level of service as with the DECT handsets under the legacy TDM RBS/IBS base station
coverage
• The ALE A-GAP stimuli protocol is transported transparently to / from the DECT handsets

The IP-xBS base stations are synchronized together over the air

• The synchronization is managed by the IP-xBS sub-system

The IP-xBS sub-system is responsible for managing connection handovers between Ip-xBS

Topologies supported

• Passive Communication Server (PCS),

• Normal redundancy
• spatial redundancy
8378 DECT IP-xBS - Overview

• IP-xBS with IBS or IP-xBS with RBS

• Addressed by External Handover (EHO)
• The IP-xBS base stations are geographically grouped and
EHO generating audio glitches are limited as much as
possible
Support of mixed • IP-xBS/IP-DECT is addressed by roaming only
mode • No handover is supported with IP-DECT, but only roaming, if
handsets are registered twice

• GAP and A-GAP handsets can be used on both IP-DECT and IP-
xBS/TDM systems
8378 DECT IP-xBS - Overview

◼Architecture

Or
OXE
8378 DECT IP-xBS - Overview

◼Architecture : Mixed mode

Or

OXE

PARI 2

PARI 1
8378 DECT IP-xBS - Overview

◼Base station : IP- xBS

Connectivity 10/100 baseT IEEE 802.3

POE
Cable: cat5/cat 6 UTP
Ethernet connectivity IPv6 ready Hardware
8378 DECT IP-xBS - Overview

◼Base station : IP- xBS

⚫ 3 models

8378 DECT IP-xBS integrated antennas

8378 DECT IP-xBS for external antennas

8378 DECT IP-xBS outdoor with external antennas

8378 DECT IP-xBS - Overview

◼Base station : IP- xBS

⚫ Catalog items

Sellable Items Reference

8378 DECT IP-xBS integrated antennas 3BN67365AA

8378 DECT IP-xBS for external antennas 3BN67366AA

8378 DECT IP-xBS outdoor with external antennas 3BN67367AA

Directive antenna with 8.0 dB gain, circular left polarization 3BD52206AA

Directive antenna with 8.0 dB gain, circular right polarization 3BD52205AA

Directive Dual Antennas 8.0 dB gain 3BD67185AA
Omnidirectionnal antennas with 7.5 dBi, Linear vertical polarization 3BD52212AA
8378 DECT IP-xBS Survey Kit worldwide 3BN67191AA
8378 DECT IP-xBS Tripod 3BN67192AA
8378 DECT IP-xBS - Overview

Supported Handsets

• A-GAP Mode
• 8234,8244 and 8254
• 8232,8242,8262 and 8262EX
8242 DECT handset 8262 DECT handset
• GAP mode
• 8212
• 8234,8244 and 8254
• 8232,8242,8262, 8262EX

8212 DECT handset 8232 DECT handset

8234 DECT handset 8244 DECT handset 8254 DECT handset

8378 DECT IP-xBS - Overview

◼Description

⚫ The IP-xBS solution is made up of IP-DECT xBS base stations connected to OXE Call Server thru the IP LAN

 There is no IP Multicast , only Unicast in the exchanges between IP-xBS and OXE Call Server

IP-xBS

OXE

Works as a NOE IP phones

UA Protocol
LAN
UA Protocol
Connection to OXE Call Server with UA / UDP for
configuration and signaling

UDP / IP
Ethernet IP-xBS
8378 DECT IP-xBS - Overview

◼Description

UA Protocol DECT Protocol

IP-xBS Data exchanged between the base station and
OXE the Call Server are encapsulated in UA messages
over UDP

The IP-xBS acts as a DECT / UA / UDP / IP bridge

8378 DECT IP-xBS - Overview

◼Description

System features Scalability OXE Topologies

12 radio channels - 11 Up to 2032 Base Stations per OXE

Central and peripheral zone
simultaneous voice coms node

Full IP Solution 254 bases Stations per PARI Mono and multi node

Handover and Roaming in mixed 8 IP-xBS PARI per OXE node OXE in Campus mode
IP and TDM Base Stations
Centralized management with
Com Server spatial redundancy
OXE
Support 82x2 ALE GAP/AGAP
PCS
handsets
8378 DECT IP-xBS - Overview

◼Description

OXE Call Server

IP phone Signaling link

• UA / UDP / IP socket (legacy protocol)

LAN

XBS-1 XBS-2 XBS-3

Media

Media • The media stream (RTP) is direct between an

Signaling
IP set or trunk and an IP-xBS base station
DECT handset • Supported codec are G711 and G729A
8378 DECT IP-xBS - Overview

◼Description

The Call Server establishes signaling and media

OXE Call Server connection with the initial base station ( Relay xBS)
where the DECT call was established
IP phone

All signaling and media redirection within the IP-

xBS DECT subsystem are managed by the IP-xBS
subsystem itself (Connection Handover)
LAN
In case of connection handover, the initial media
connection is maintained with the distant party
and media is rerouted between the base stations
XBS-1 XBS-2 XBS-3

Signaling and media commands are always sent by

the Call Server to the initial base station

Media

Signaling
DECT handset
8378 DECT IP-xBS - Overview

◼Synchronization over the air

OXE Call Server

The IP-xBS base stations are synchronized
together over the air
xBS-1
Master
The clock synchronization is managed by the
xBS-4 xBS-2 IP-xBS subsystem

They are also able to clock synchronize with

TDM base stations (IBS or RBS, but not both
together) over the air

The maximum of levels in the synchronisation

xBS-3 tree is 24
xBS-5 xBS-6

Over the air synchronization

8378 DECT IP-xBS - Overview

◼Time management / Daylight Saving Time

OXE NTP server is

Time on IP-xBS The NTP server
used to provide
provided by NTP gives a UTC time
time to IP-xBS

NTP server and DST

The DST (Daylight
are sent to the IP-
Saving Time) is
xBS base stations
given by the Call
during their
Server
initialization
8378 DECT IP-xBS - Overview

◼xBS base station web based management

⚫ This interface is not required for normal operations
8378 DECT IP-xBS - Overview

◼xBS base station web based management

⚫ Access to the web based management using the default IP factory IP address

 Press the Reset button between 6 seconds and 10 seconds

 Browse : http://192.168.0.2

Manual reset button

End of the module

enterprise.alcatel-lucent.com
OpenTouch Suite for MLE
OmniPCX Enterprise Communication server
8378 DECT IP-xBS – Management objects

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
Lesson Summary - OXE management objects

◼PARI management
◼RPN management
◼Location area management
◼Sites management
8378 DECT IP-xBS - Management objects

◼PARI management

• Up to 8 different PARI
The Call Server can manage several PARI
• 254 base stations per PARI
8378 DECT IP-xBS - Management objects

◼RPN management
• The RPN is used for geo-location of DECT
handsets
The RPN (Radio Part Number) identifies the
base station over the air interface • The RPN is also used for the
synchronization over the air to identify a
base station
8378 DECT IP-xBS - Management objects

◼Location area management

• Location areas are identified according to

Location areas may be defined, to optimize the base station RPN
traffic in case of high density installation • Inside a PARI, up to 64 location areas may
be defined

Location area type selection

8378 DECT IP-xBS - Management objects

◼Location area management

⚫ Example of configuration

4 areas are defined

Area RPN

0 1-63

1 64-127

2 128-191

3 192-254

System administrator can configure

the area number for a base station.
A free RPN related to this area is then
affected by the system
 8378 DECT IP-xBS - Management objects

◼Site management
⚫ A SITE is a group of 8378 DECT IP-xBS linked to a call server and located in the same geographical location where it is
possible to do handover

Site 2

IP-xBS
Site 1

Branch Office
IP-xBS
Head Quater
Sync Sync
WAN

OXE Site 3

Sync
IP-xBS IP-xBS

IP-xBS IP-xBS

Branch Office
8378 DECT IP-xBS - Management objects

◼Site management

Handover is only available on a same site

Site 1
No Handover between site

IP-xBS

Sync Sync
LAN or WAN

OXE Site 2

×
Sync
IP-xBS IP-xBS

IP-xBS IP-xBS

Handover
8378 DECT IP-xBS - Management objects

◼Site management

Roaming is possible between sites

Site 1

IP-xBS

Sync Sync
LAN or WAN

OXE Site 2

Sync
IP-xBS IP-xBS

IP-xBS IP-xBS

Roaming
8378 DECT IP-xBS - Management objects

◼Site management

The sites are defined by the system administrator

through the management tools

By default, all base stations are in the same site

Additionnal Site must be created for branch offices

8378 DECT IP-xBS - Management objects

◼Site management

The system administrator may also change the

assignment of an IP-xBS base station to a site
8378 DECT IP-xBS - Management objects

◼Site management

One PARI may be shared between several sites, to allow

definition of many small branch offices Site 2

PARI 1

Site 1

PARI 1

Site 3

PARI 1
8378 DECT IP-xBS - Management objects

◼Site management

A site may contain bases stations belonging to different

PARI

PARI synchronization links must be configured to allow Handover

global synchronization inside this site

Site 1

PARI 1 PARI 2 PARI 3

Ext Sync Ext Sync

8378 DECT IP-xBS - Management objects

◼Site management

The Data Sync Primary is a xBS base station in charge of

synchronizing the data between all the xBS base
stations of a PARI inside a Site Site 2

PARI 1

Site 1

PARI 1 PARI 2

Data Sync Primary Base Station

> One Data Sync Primary for every couple Site/PARI

> The Data Sync Primary is selected automatically by the
system
> Handover is only possible between base stations with the
same Data Sync Primary
8378 DECT IP-xBS - Management objects

◼Site management

⚫ Data Sync Primary communicates with other Base Stations for:

 Synchronization tree optimization

 Handover mechanism
 Base stations status
 Status messages with OXE

Master
Sync

OXE

Data
Primary
8378 DECT IP-xBS - Management objects

◼Site management

⚫ Handover mechanism

Handover
Radio Who
IP-xBS 1
Domain relays ?

IP
IP-xBS 1 IP-xBS 2 IP-xBS 3 IP-xBS 1 IP IP-xBS 2 IP-xBS 3
Data Data
SIG SIG SIG SIG SIG SIG Primary
Primary
RTP RTP RTP RTP RTP RTP

IP
Domain Media Media

Signalling Signalling
UA / UDP UA / UDP
CS Caller CS Caller

OXE OXE

1) DECT terminal communicates with an IP phone. Signalling and RTP flows are established with xBS1.
2) DECT set moves close to xBS2 (bearer request), xBS2 communicates with Data Primary, to know the base connected with DECT set.
3) xBS2 establishes IP relay with xBS1 (sig and media) and establishes radio communication with Dect
8378 DECT IP-xBS - Management objects

◼Site management

⚫ Handover mechanism

Handover I know xBS1 relays

Radio this DECT phone set..
Domain

IP-xBS 1 IP IP-xBS 2 IP-xBS 3 IP-xBS 1 IP-xBS 2 IP-xBS 3

Data Data
SIG SIG SIG Primary SIG SIG SIG Primary
RTP RTP RTP RTP IP RTP RTP

IP
Domain Media Media

Signalling Signalling
UA / UDP UA / UDP
CS Caller CS Caller

OXE OXE

4) When DECT set moves close to xBS3, handover process is the same:
xBS3 which is Data Primary, knows xBS1 is the first Base establishing RTP and Signalling flows,

5) xBS 3 establishes IP relay with xBS1 (sig and media) + radio communication with DECT. Flow between xBS1 and xBS2 is stopped.
8378 DECT IP-xBS - Management objects

◼Site management

⚫ Handover: IP-XBS capacity

IP-xBS Base Station supports simultaneoulsly 11 DECT radio communications + 11 IP Relays.

Example below shows the resources (DECT channels & IP relays) available on each base, during handover process.

DECT Channels
available 10 11 11 11 10 11 11 11 10

IP Relays
available 11 11 11 10 11 11 10 11 11

xBS 1 xBS 2 xBS 3 xBS 1 xBS 2 xBS 3 xBS 1 xBS 2 xBS 3

SIG SIG SIG SIG SIG SIG SIG SIG SIG
RTP RTP RTP RTP RTP RTP RTP RTP RTP

CS Caller CS Caller CS Caller

OXE OXE OXE

OpenTouch Suite for MLE
OmniPCX Enterprise Communication server
8378 DECT IP-xBS – Synchronization over the air
Lesson Summary

◼Air Synchronization
⚫ Internal Synchronization
 Sync Master Base Station

⚫ Sync Cluster
⚫ External Synchronization
 Inter-PARI synchronization

⚫ Internal synchronization management

◼Synchronization topologies
8378 DECT IP-xBS – Synchronization over the air

◼Internal Synchronization

Internal Synchronization is a set of 8378 DECT IP-xBS

inside the same PARI of a same SITE which are Site 2
synchronized (time aligned) together
PARI 1

Site 1 Sync Sync

PARI 1 PARI 2
Sync
Sync

Sync Internal Synchronization

Sync

Sync
Sync

Sync Sync
8378 DECT IP-xBS – Synchronization over the air

◼Sync Master Base Station

A SYNC MASTER is the 8378 DECT IP-xBS root of the Site 2

internal synchronization tree
PARI 1

Site 1

PARI 1 PARI 2

Sync Master Base Station

 The Sync Master is automatically selected by the xBS subsystem

and it may change over the time (modification of radio environment,
base station failure…)
8378 DECT IP-xBS – Synchronization over the air

◼Sync Cluster

Only for Special cases when

A SYNC CLUSTER is a set of 8378 DECT IP-xBS which are the radio coverage is tricky
synchronized (time aligned) together at DECT radio
interface

Site 1
 Up to 8 Sync Clusters per couple Site/PARI
PARI 1
 By default, all base stations belong to Sync Cluster 0

 System administration can indicate which Sync Clusters each base station belongs

 A base station may belong up to 8 Sync Clusters

Cluster 0
 Scope of a Sync Cluster is a group of base stations defined by the couple Site/PARI
8378 DECT IP-xBS
Air Synchronization
◼Sync Cluster

Cluster It may be useful to group the DECT base stations so that some
management in don’t synchronize together,
which case ? For example, when internal synchronization between some bases
may not be stable because of a changing radio environment

Site 1 Site 1

PARI 1 PARI 1
Cluster 0

Cluster 0
Cluster 2
Cluster management
in the OXE configuration

Cluster 1
8378 DECT IP-xBS – Synchronization over the air

◼Sync Cluster

⚫ System administration can indicate which Sync Clusters each base station belongs
8378 DECT IP-xBS – Synchronization over the air

◼External Synchronization

The External Synchronization allows to synchronize two sets of xBS

which are synchronized with Internal Synchronization; or it allows
to synchronize a set of xBS with a set of TDM base stations

Site 1

PARI 1 PARI 2

External Synchronization
8378 DECT IP-xBS – Synchronization over the air

◼Multi PARI synchronization

The xBS system is only able to build one

synchronization tree per PARI

Several PARI are needed In case of large

Sites with more than 254 base stations
Site 1
Synchronization between all these base
PARI 1 PARI 2 station (i.e belonging to different PARIs)
may be expected

It is possible to synchronize both trees

together using External Synchronization
Ext Sync The selection of the base station used for
external synchronization ("Master Sync"
and "External Synchronization RPN" is done
manually
The Sync master base station does not
support any communications

A backup Sync Master must also be setup

Sync Master and configured

External synchronisation RPN

8378 DECT IP-xBS – Synchronization over the air

◼Synchronisation Multi-PARI

PARI 0 (10000400104) PARI 1

Master

Sync Backup Sync Master Sync

Sync Sync
Sync Sync

Ext Sync
Sync Sync

Sync Master

The PARI 1 gets the synchronisation from

the PARI 0 via the « Sync Master»base station
8378 DECT IP-xBS – Synchronization over the air

◼Mixed mode synchronisation

PARI RBS or IBS (10000400104) PARI 0 (xBS)

Backup Sync Master Sync

UA Sync
Sync

Ext Sync
UA Sync

Sync Master
UA UA

UA

The PARI 0 (xBS) gets the synchronisation from

Synchro the PARI TDM via the « Sync Master»base station
8378 DECT IP-xBS – Synchronization over the air

◼Multi-PARI Synchronization
⚫ External synchronization : Sync Master xBS and backup Sync Master xBS

 When External synchronization is used, the Backup Sync Master is mandatory to secure redundancy
 This Backup Sync Master needs to be placed near to the Sync Master, it must see the same External Sync BS

 The Backup Sync Master could carry traffic not supported by the Sync Master
 but if the Sync Master fails, the Backup Sync Master will not be able any more to support this traffic

 If this is not acceptable, an additional xBS must be placed near Sync Master and Backup Sync Master to support the traffic in all
conditions. The Back-up Sync Master will be acting as Sync Master (meaning no traffic) if the original Sync Master is down

 Restriction:

 in case of failure of the master and the backup or of a key base

 The other base will not work anymore, there is no island creation
 When the failing bases are back there is no automatic recovery of the whole synchronization (will be improved in a future release)
8378 DECT IP-xBS – Synchronization over the air

◼Inter-PARI synchronization
⚫ Configuration of Sync Master/backup and External Sync source PARI/BS
8378 DECT IP-xBS – Synchronization over the air

◼Inter-PARI synchronization

⚫ When more than 2 PARIs are synchronized together using external sync, additional configuration is needed: a
synchronization highway
8378 DECT IP-xBS – Synchronization over the air

◼Inter-PARI synchronization

⚫ Additional configuration is needed: a synchronization highway

8378 DECT IP-xBS – Synchronization over the air

◼Internal synchronization management

⚫ Internal synchronization tree

Dynamic synchronization tree

xBS 0 RPN 0
Sync Master
Sync
xBS 1
Sync
Sync RPN 4 RPN 1

Sync
xBS 4 xBS 2
RPN 3 RPN 2
xBS 3
8378 DECT IP-xBS – Synchronization over the air

• The Internal Synchronization is automatically established inside the xBS

subsystem for each Sync Cluster

• The internal synchronization tree is built step by step with information

retrieved by each base station on its own radio environment

• The criteria which enter in the algorithm of building the internal

Internal synchronization synchronization tree:
Management • Link quality / RSSI (Received Signal Strength Indication)
• Optimization of the number of hops to the root

• In case of modification in the radio environment or in case of failure of one

base station, the xBS subsystem automatically reorganizes itself by building
a new internal synchronization tree

• There is no configuration needed by default

8378 DECT IP-xBS – Synchronization over the air

Internal synchronization Management

In case of mix of xBS and TDM IBS/RBS base stations

• The system administrator may decide to synchronize the xBS base stations of a Site
on a TDM base station, using External Synchronization

• There is no such synchronization by default

• Synchronization is done to a particular TDM BS (External Sync PARI/RPN)

8378 DECT IP-xBS – Synchronization over the air

◼Internal synchronization management xbssynchro command

⚫ Display the synchronization tree

 Oxe tool: xbssynchro

Note: xbssynchro gets from the Sync Primary base

station the representation of the synchronization
tree.
The tree (with RPN & RSSI) is displayed on the
console in text format

⚫ Incidents:

 Command: incvisu | grep xBS ( or 60 , 78)

 To see only the IP-Xbs incident
Synchronization topologies
8378 DECT IP-xBS – Synchronization over the air

◼Example: One Site

OXE Call Server

xBS-1
Master

xBS-4 xBS-2

Site 1
xBS-3
xBS-5 xBS-6

Over the air synchronization

All base stations are clock synchronized together
8378 DECT IP-xBS – Synchronization over the air

◼Example: 3 Clusters
OXE Call Server

Cluster 3

Floor 2
Cluster 1

XBS-4 XBS-5 XBS-3 XBS-6

XBS-2

Cluster 2
Floor 1

XBS-7 XBS-8 XBS-1 XBS-9

Master

Over the air synchronization

Elevator shaft UA link synchronization

8378 DECT IP-xBS – Synchronization over the air

◼Example: Branch Offices

OXE Call Server

XBS-1
Master
XBS-7
Master
XBS-2 XBS-3
XBS-4
XBS-8 XBS-9
XBS-
10
XBS-6 XBS-5

Site 3

Site 1

XBS-7
Master

XBS- XBS-
8 9

Over the air synchronization

Site 3
8378 DECT IP-xBS – Synchronization over the air

◼Example: Two PARI

OXE Call Server

xBS-1 PARI 1
Master
xBS-4 PARI 2
xBS-4 PARI 1 xBS-2 PARI 1

Backup
Sync Master

xBS-2 PARI 2

Site 1
xBS-3 PARI 1 Ext Sync
xBS-5 PARI 2
xBS-3 PARI 2
xBS-6 PARI 1
xBS-5 PARI 1 Sync Master
xBS-1 PARI 2

synchronisation par les airs

End of the module

enterprise.alcatel-lucent.com
OpenTouch Suite for MLE
OmniPCX Enterprise Communication server
8378 DECT IP-xBS – Commissioning
Lesson Summary

◼IP-xBS Commissioning

⚫ IP Configuration
⚫ Firmware update
⚫ IP-xBS registration
⚫ Maintenance Tools
⚫ Engineering Rules
8378 DECT IP-xBS - Commissioning

◼IP-xBS Commissioning

IP-xBS IP configuration Management & Maintenance

• Dynamic
• Static
IP-xBS firmware update IP-xBS

• TFTP server Firmware

• Manual update TFTP Server
IP Setting
IP-xBS registration
• MAC @ in the OXE Database DHCP Server

OXE Mac @

MAO
8378 DECT IP-xBS - Commissioning

◼IP Configuration

Dynamic Mode

IP-xBS

IP address ranges DHCP Server

✓ IP address
✓ Mask
OXE ✓ Gateway
✓ TFTP server

Static Mode

IP-xBS

Static management:
✓ IP address
✓ Mask
✓ Gateway
8378 DECT IP-xBS - Commissioning

◼IP Configuration

Dynamic Mode with the internal

DHCP Server

192.168.1.149

IP-xBS

DHCP Server

192.168.1.150

OXE IP-xBS

IP-xBS

192.168.1.151

A new Vendor Class has been added in the internal DHCP

to provide an ip settings to the xBS
8378 DECT IP-xBS - Commissioning

◼IP Configuration

Dynamic Mode with an external

DHCP server

192.168.1.149

OXE
IP-xBS

192.168.1.150

IP-xBS
DHCP Server

IP-xBS

192.168.1.151
8378 DECT IP-xBS - Commissioning

◼Firmware update

Automatic update

IP-xBS
Firmware upgrade
TFTP Server

OXE

Manual update

IP-xBS
Firmware update

IP-xbs Firmware file

available on the PC
 8378 DECT IP-xBS - Commissioning

◼Firmware update

Automatic update

IP-xBS

OXE IP-xBS

TFTP Server

Firmware upgrade Process:

• The base stations start with their current (old) software.
• When the call server has some free resources, it requests an xBS to start downloading
IP-xBS
the new firmware on its RAM in background. So that it is still running for handsets calls.
• After successful download and when base station is idle, the call server restarts them
to switch on the new firmware
8378 DECT IP-xBS - Commissioning (1)csa> downstat x

Tue May 3 19:13:03 CEST 2022

*** XBS 8378 system binary version: V0073B0003

◼Firmware update +---------------------+------+--------+----------+----------+---------------+

|Tue 05/03/22 19:13:03| | | Current |Downloaded| |
| Site PARI RPN|State |Location|FW Version| Version |Download status|
+---------------------+------+--------+----------+----------+---------------+
⚫ Background mode |
|
0
0
1
1
0|OK
1|OK
|F1_B1
|F1_B2
|0073B0003 |V0074B0008|READY_TO_FLASH |
|0073B0003 |V0074B0008|READY_TO_FLASH
| 0 1 2|OK |F1_B3 |0073B0003 |V0074B0008|IN_PROGRESS |
Minimum firmware version: v73b0003 +---------------------+------+--------+----------+----------+---------------+

When all Base Stations are ready,

When download is completed, the system can be restarted
Base Station downloads new firmware
base station sends a message automatically or manually. During
in background mode
to OXE. restart, new firmware is flashed in
the main memory, then Base
Station reboots

Download in Ready to Flash and

progress flash! reset

OXE OXE OXE

OXE Console OXE Console OXE Console
8378 DECT IP-xBS - Commissioning

◼Firmware update
➢ Allow auto. Reset after update: NO
⚫ Management The reset will be managed thanks to ‘downstat x’ command

(1)csa> downstat x

Tue May 3 19:13:03 CEST 2022

*** XBS 8378 system binary version: V0073B0003

+---------------------+------+--------+----------+----------+---------------+
|Tue 05/03/22 19:13:03| | | Current |Downloaded| |
| Site PARI RPN|State |Location|FW Version| Version |Download status|
+---------------------+------+--------+----------+----------+---------------+
| 0 1 0|OK |F1_B1 |0073B0003 | |UP TO DATE |
| 0 1 1|OK |F1_B2 |0073B0003 | |UP TO DATE |
+---------------------+------+--------+----------+----------+---------------+
All xBS are up to date

1. Start download of new xBS firmware

2. Send Flash and Reset command to some xBS
3. Restore all xBS to legacy mode (no download in background at next startup)
4. Allow new download of xBS in DOWNLOAD_FAILED state
0. Exit
Return. Refresh

Your choice :

Note : After choice 2, the tool requests the user to choose which site/pari are concerned.
Then a confirmation is requested before sending the command ‘flash and reset’

➢ Allow auto. Reset after update: YES

All xBS of a site/pari will automatically reset
when background download has succeeded for them.
8378 DECT IP-xBS - Commissioning

◼Firmware update

Manual update

1 IP-xBS

2
4
3
8378 DECT IP-xBS - Commissioning

◼IP-xBS registration

⚫ Enable the registration

⚫ Alternative to enable the automatic registration is to do the manual registration by directly enter the Terminal
Ethernet Address (MAC@) manually for each base station
8378 DECT IP-xBS - Commissioning

◼IP-xBS registration

MAC Address

IP Address
8378 DECT IP-xBS - Commissioning

◼IP-xBS start up

Power On
DHCP Server 2
DHCP Request

IP-xBS
DHCP request 3
TFTP Server Firmware
• IP configuration

OXE 4 Mac @
TFTP server
• Firmware update
MAO

IP-xBS registration
• MAC @ in the OXE Database
1 Power On
8378 DECT IP-xBS - Commissioning

◼Maintenance Tools

⚫ The following tools are adapted to work for xBS in the same way as for IBS/RBS

 dectview (1)csa> dectview xbs

 dectinston Wed May 11 09:06:35 CEST 2022
 dectinfo
 dectarea ================= DECT RESOURCES BUSY STATE ===============

 dectobs Resource Max busy free percent busy

-----------------------------------------------------
 obstraf Link 276 0 276 0.00
 ippstat LCEI 300 0 300 0.00
ADPCM 0 0 0
 downstat Buffer UA-> 135 0 135 0.00
 Domstat **** XBS registration NODE 1 (my local node is 1) ****
 tftp_check +---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
|Virtual @|XBS Site PARI-Area-RPN| Neqt|State |Location| IP @ | Mac @ |FW Version|Clusters|NR|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
| 1/00/051|000 0 Labo_BR 0- 0- 0| 896|OK P | |192.168.1.149 |00:08:7b:16:4c:f9|0073B0003 |00000001| 0|
| 1/00/052|001 0 Labo_BR 0- 0- 1| 897|OK +| |192.168.1.148 |00:08:7b:16:50:e6|0073B0003 |00000001| 0|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
NR = Number of Radio links established
NOK = out of service
OOS = outserv used; use inserv to put in service again
P = data sync Primary xbs (the one which collects data)
M = Master configured (for DECT synchronization)
B = Backup configured (for DECT synchronization)
+ = Master free running of DECT synchronization (not available in st-by CPU)
* = Master locked of DECT synchronization (not available in st-by CPU)
Region 0 (EUROPE) has 1 site(s) with 2 XBS in service.
8378 DECT IP-xBS - Commissioning

◼Maintenance Tools
8378 DECT IP-xBS - Commissioning

◼Engineering Rules
OXE
Easy deployment
• IP-xBS only
Create • 1 PARI, 1 location area
xBS PARI
• 1 site
• 1 cluster

Dynamic IP parameters

xBS Auto-discovery
IP-xBS is registered automatically, using default
parameters set in OXE configuration
(PARI, location area), as long as registration is allowed
Automatic air (configuration parameter)
synchronization

Refer to the document

Deployment Assessment Getting started IP-xBS
available on the BP Web Site

End
8378 DECT IP-xBS - Commissioning

◼Engineering Rules
Complex deployment
• Branch office
OXE • Mix of IP-xBS and TDM base stations
• Multi Pari

Create xBS PARI

No Full coverage
not possible Yes Use several “Sync
using air sync Clusters”
Dynamic IP within a site?
parameters Refer to the document
Getting started IP-xBS
available on the BP Web Site

No Are there Yes

branch Create several “SITE”
offices? No More than Yes Use External
254 xBS? synchronization

Automatic air
synchronization

xBS Auto-discovery
No More than 2 Yes
PARI? Use SYNC HIGHWAY Deployment
Assessment

End
8378 DECT IP-xBS - Commissioning

◼IP-xBS start up
End of the module

enterprise.alcatel-lucent.com
OpenTouch Suite for MLE
OmniPCX Enterprise Communication Server

8378 DECT IP-xBS

How to
✓ Deploy 8378 IP-xBS

Contents
1 IP- xBS configuration.......................................................................... 3
1.1. Global DECT parameters .......................................................................... 3
1.1.1. Select the Radio Base Type ............................................................................... 3
1.1.2. Manage the PLI.............................................................................................. 3
1.1.3. Manage the AC code ....................................................................................... 3
1.2. xBS parameters ..................................................................................... 3
1.2.1. Declare the number of PARI for using the IP-xBS ...................................................... 3
1.2.2. xBS WBM ..................................................................................................... 4
1.3. xBS PARI ............................................................................................. 4
1.3.1. Create a PARI ............................................................................................... 4
1.4. xBS Site .............................................................................................. 4
1.4.1. Modify the site number 0 .................................................................................. 4
1.5. xBS Base station .................................................................................... 4
1.5.1. Modify the parameters..................................................................................... 4
1.5.2. Check the xBS to clusters ................................................................................. 5

2 DHCP Management ............................................................................ 5

2.1. DHCP server (internal or external) ............................................................... 5

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
 2
8378 DECT IP-xBS

3 xBS registration ................................................................................ 6

3.1. Enable the registration of the xBS ............................................................... 6
3.2. Check the status of the xBS ....................................................................... 6
4 Time server in the xBS ....................................................................... 7
4.1. Check the time server in the xBS ................................................................ 7
 3
8378 DECT IP-xBS

Implementation

1 IP- xBS configuration

Deploy an IP-xBS solution with one PARI in a single site.
- PARI number: 100004101x4 (x = platform number)
- PLI = 31
- AC code = 1111

1.1. Global DECT parameters

1.1.1. Select the Radio Base Type

PWT/DECT System
Radio base type xBS or Mixed
Station Base Type DECT Europe

1.1.2. Manage the PLI

PWT/DECT System
PLI for CTM 31

Notes
In multi PARI or in mixed mode, the PLI must be adapted

1.1.3. Manage the AC code

PWT/DECT System
AC System 1111
Security level Authentication

Notes
The AC code is optional

1.2. xBS parameters

1.2.1. Declare the number of PARI for using the IP-xBS

PWT/DECT System / xBS System

Number of PARI 0

Notes
Up to 8 PARI
 4
8378 DECT IP-xBS

1.2.2. xBS WBM

PWT/DECT System / xBS System

Allow xBS Web Based YES
Management
xBS WBM engineer password <Enter your password>
(Default: Engineer00!)
xBS WBM admin password <Enter your password>
(Default: Admin00!)

1.3. xBS PARI

1.3.1. Create a PARI

PWT/DECT System / xBS System / xBS Pari

PARI Number 0
PARI Value 100004100x4 < this is an example of PARI >
Area type 1 area of 256 xBS

1.4. xBS Site

1.4.1. Modify the site number 0

PWT/DECT System / xBS System / xBS Site

Site Number 0
Site Name BREST
Station Base Type DECT Europe

Notes
By default, the site 0 is created

1.5. xBS Base station

1.5.1. Modify the parameters

PWT/DECT System / xBS / xBS base station

Terminal Ethernet Address < Automatically assigned >
Location name GF-01
Phone COS 0
Site Number 0
PARI Number 0
Location Area 0
RPN < consultation only>

Notes
When the base station is registered in the OXE, the MAC @ of the base station is present and the system has
been assigned an RPN value to the xBS.
 5
8378 DECT IP-xBS

1.5.2. Check the xBS to clusters

PWT/DECT System / xBS / xBS base station

Cluster 0 YES
Cluster 1 YES or NO
Cluster 2 YES or NO
Cluster 3 YES or NO
Cluster 4 YES or NO
Cluster 5 YES or NO
Cluster 6 YES or NO
Cluster 7 YES or NO

Notes
By default, all xBS belong to the cluster 0.

2 DHCP Management
A range of IP addresses in the internal OXE DHCP server already exit
- Range: 192.168.1.145 to 192.168.1.155

2.1. DHCP server (internal or external)

Notes
Technical documentation: oxe12.1_sd_IP_PCXNetworks_8AL91007USAH_1_en.pdf

A new Vendor Class for the xBS: Vendor id: alcatel.ipxbs.0

 6
8378 DECT IP-xBS

3 xBS registration

Enable the registration on the OXE and plug the two xBS.

3.1. Enable the registration of the xBS

PWT/DECT System / xBS System
Registration node 1
Registration enabled YES
Default PARI for registration 255
Default location area for reg. 255

Notes
Don’t forget to specify the registration node.

3.2. Check the status of the xBS

Under mtcl
Command dectview xbs
(1)csa> dectview xbs

Wed May 11 09:06:35 CEST 2022

================= DECT RESOURCES BUSY STATE ===============

Resource Max busy free percent busy

-----------------------------------------------------
Link 276 0 276 0.00
LCEI 300 0 300 0.00
ADPCM 0 0 0
Buffer UA-> 135 0 135 0.00

**** XBS registration NODE 1 (my local node is 1) ****

+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
|Virtual @|XBS Site PARI-Area-RPN| Neqt|State |Location| IP @ | Mac @ |FW Version|Clusters|NR|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
| 1/00/051|000 0 Labo_BR 0- 0- 0| 896|OK P | GF-01 |192.168.1.149 |00:08:7b:16:4c:f9|0073B0003 |00000001| 0|
| 1/00/052|001 0 Labo_BR 0- 0- 1| 897|OK +| FL1-01 |192.168.1.148 |00:08:7b:16:50:e6|0073B0003 |00000001| 0|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
NR = Number of Radio links established
NOK = out of service
OOS = outserv used; use inserv to put in service again
P = data sync Primary xbs (the one which collects data)
M = Master configured (for DECT synchronization)
B = Backup configured (for DECT synchronization)
+ = Master free running of DECT synchronization (not available in st-by CPU)
* = Master locked of DECT synchronization (not available in st-by CPU)

Region 0 (EUROPE) has 1 site(s) with 2 XBS in service.

(1)csa> exit
 7
8378 DECT IP-xBS

4 Time server in the xBS

NTP server ( 192.168.1.252 – ITServer) is already declared in the OXE to synchronize the
time.
Check that the time server defined in the base station is the OXE.

4.1. Check the time server in the xBS

On the xBS Web Base Management
Check the Time server IP
address

Notes
The timer server is the OXE. This information is transmitted to the base station via the UA signaling link.
You can manage manually any other IP address if you want.
OpenTouch Suite for MLE
OminPCX Enterprise Communication Server

8378 DECT IP-xBS

How to
✓ Replace an out of service xBS base station

Contents
1 Un-register the xBS ........................................................................... 2
1.1. Un-register the xBS Base station ................................................................. 2
2 New xBS base station registration .......................................................... 2
2.1. Register the new base station .................................................................... 2
2.2. Check the status of the xBS ....................................................................... 3
2.3. Check if the new base station is registered in the OXE Database ........................... 3
 2
8378 DECT IP-xBS

Implementation

1 Un-register the xBS

For the lab purpose, do a base station exchange with your neighbor to simulate an out of
service xBS
Unplug the base station id 0.
Remove the MAC @ and note the location name

1.1. Un-register the xBS Base station

PWT/DECT System / xBS / xBS base station

Base station id 0 < consultation only>
Terminal Ethernet Address <Remove the MAC @>
Location name GF-01
Site Number 1

2 New xBS base station registration

Enter manually the MAC @ and re-enter the location name and plug the new xBS
(just received from your neighbor).
Check if the xBS is registered in the OXE data base

2.1. Register the new base station

PWT/DECT System / xBS / xBS base station

Base station id 0 < consultation only>
Terminal Ethernet Address <Enter the MAC @>
Location name <Enter the same location name GF-01>
Site Number 1

Notes
The manual registration is recommended when replacing a broken base station by a new one (with a new
MAC@)
When using the automatic registration, the first free RPN will be used and it can be different. This could be
problematic if alarming and geo localization is used.
 3
8378 DECT IP-xBS

2.2. Check the status of the xBS

Under mtcl
Command dectview xbs
(1)csa> dectview xbs

Wed May 11 09:06:35 CEST 2022

================= DECT RESOURCES BUSY STATE ===============

Resource Max busy free percent busy

-----------------------------------------------------
Link 276 0 276 0.00
LCEI 300 0 300 0.00
ADPCM 0 0 0
Buffer UA-> 135 0 135 0.00

**** XBS registration NODE 1 (my local node is 1) ****

+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+-
-+
|Virtual @|XBS Site PARI-Area-RPN| Neqt|State |Location| IP @ | Mac @ |FW
Version|Clusters|NR|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+-
-+
| 1/00/051|000 0 Labo_BR 0- 0- 0| 896|OK P | GF-01 |192.168.1.149 |00:08:7b:16:4c:f9|0073B0003 |00000001|
0|
| 1/00/052|001 0 Labo_BR 0- 0- 1| 897|OK +| FL1-01 |192.168.1.148 |00:08:7b:16:50:e6|0073B0003 |00000001|
0|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+-
-+
NR = Number of Radio links established
NOK = out of service
OOS = outserv used; use inserv to put in service again
P = data sync Primary xbs (the one which collects data)
M = Master configured (for DECT synchronization)
B = Backup configured (for DECT synchronization)
+ = Master free running of DECT synchronization (not available in st-by CPU)
* = Master locked of DECT synchronization (not available in st-by CPU)

Region 0 (EUROPE) has 1 site(s) with 2 XBS in service.

(1)csa> exit

2.3. Check if the new base station is registered in the OXE Database
PWT/DECT System / xBS / xBS base station
Base station id 0
Terminal Ethernet Address < Automatically assigned >
Location name GF-01
Phone COS 0
Site Number 0
PARI Number 1
Location Area 0
RPN < consultation only>

Notes
When the base station is registered in the OXE, the MAC @ of the base station is present and the system has
been assigned an RPN value to the xBS.
OpenTouch Suite for MLE
OmniPCX Enterprise Communication server
8378 DECT IP-xBS – DECT users
Lesson Summary

◼DECT users

⚫ Users creation
⚫ Handsets subscription
8378 DECT IP-xBS - DECT users

◼Users creation
⚫ Type : A-GAP or GAP
8378 DECT IP-xBS - DECT users

◼Handsets subscription

The subscription of the DECT

handsets is managed by the Call
DECT Handsets subscription Server
• Commande: dectinston

In case of mix of both IP-xBS and

TDM IBS, the subscription may be The subscribed handsets can be
done thru either an IP-xBS or a used either on IP-xBS or TDM IBS
TDM IBS base station subsystems
8378 DECT IP-xBS - DECT users

◼Handsets subscription
End of the module

enterprise.alcatel-lucent.com
OpenTouch Suite for MLE
OminPCX Enterprise Communication Server

8378 DECT IP-xBS

How to
✓ Create and register the DECT handsets

Contents
1 DECT Users ..................................................................................... 2
1.1. Create the DECT users ............................................................................. 2
2 DECT handset subscription ................................................................... 2
2.1. Register the handset ............................................................................... 2
2.1.1. Start the registration on the OXE ........................................................................ 2
2.2. Register the phone ................................................................................. 3
 2
8378 DECT IP-xBS

Implementation

1 DECT Users
Create 3 users with the following directory numbers, 31015, 31016 and 31017 and the
set type “GAP+ “.
Create one user with the directory number 31018 and the set type “GAP”.
For the name and first name put any name you want.

1.1. Create the DECT users

Users
Directory number < free directory number>
Directory name < 20 characters max>
Directory First name < 20 characters max>
Set type GAP + or GAP Handset

2 DECT handset subscription

Install the 3 handsets with the command “dectinston”

2.1. Register the handset

2.1.1. Start the registration on the OXE

Under “mtcl”
command dectinston <directory number> or dectinston -g
Press “Enter” (1)csa> dectinston -g

Fri Apr 6 14:21:44 CEST 2018

Choice of a specific base station (Y/N - default is N) ?

Press “Enter” GAP characteristics

_______________________________________________________
Directory Number : 31016
User's name : DECT Handset
MAO type : GAP+

Dect parameters used.

PARI : 10000400100
PLI : 31
_______________________________________________________

Do you agree to install this set. (Y/N - default is Y)?

 3
8378 DECT IP-xBS

Wait the DECT set ringing Start the registration on the handset.

Wait until the set rings, but you don't have to

hang up!!!
_______________________________________________________

Press 0 to leave Installation succeed.

Effective Security Level : No Security
_______________________________________________________
Installation of a handset ?
No -> 0
With automatic choice of a GAP dir. number -> 1
With the choice of a directory number -> 2
(default 0) ==>

Notes
You have different choices after the installation:
- If you enter 0, you leave the program
- If you enter 1, you make an automatic installation of the mobile phone ready
for it (message Subscription Running… on the screen) the system selects
automatically for you the directory number
- If you press 2, you make a manual installation of the mobile phone, you select
the directory yourself for handsets

2.2. Register the phone

On the DECT phone
Press “Ok”

Press “Ok”
 4
8378 DECT IP-xBS

Enter the PIN code then press

“Ok”

Press “Ok”

Press “Ok”

Enter the AC code if defined

in the configuration
then press “Ok”
 5
8378 DECT IP-xBS

Select “Normal”

l
Select “Yes”

The handset tries to register

 6
8378 DECT IP-xBS

The Handset rings one and the

registration information has
been displayed
(Name, first name, extension
number, PARI and PLI).

The handset has been

registered
OpenTouch Suite for MLE
OmniPCX Enterprise Communication Server

DECT users

How to
✓ uninstall and remove a DECT handset

Contents
1 Uninstall a DECT handset .................................................................... 2
1.1. Uninstall the handset .............................................................................. 2
1.2. The phone is deregistered ........................................................................ 2
2 Delete a DECT User ........................................................................... 3
2.1. Delete a DECT user ................................................................................. 3
 2
DECT users

Implementation

1 Uninstall a DECT handset

Uninstall the 3 handsets with the command “dectrm”

1.1. Uninstall the handset

Start the deregistration on the OXE

Under “mtcl”
command dectrm <directory number>
Press “Enter” 1)csa> dectrm 31015

Tue Sep 4 16:12:58 CEST 2018

_______________________________________________________
Directory Number : 31015
User's name : Volfoni Raoul
MAO type : GAP +
IPEI : 0953506683031
Registered : Yes
_______________________________________________________
Are you really sure to remove this set. (Y/N - Default is Y) ?
Wait the DECT set ringing Attempt to send a deregistration message to the set.

Operation succeed.
_______________________________________________________
(1)csa>

1.2. The phone is deregistered

On the DECT phone
 3
DECT users

2 Delete a DECT User

Delete the 3 users with the following directory numbers, 31015, 31016 and 31017.

2.1. Delete a DECT user

Users
Directory number < selected directory number>
Then “Delete”
OpenTouch Suite for MLE
OmniPCX Enterprise Communication server
8378 DECT IP-xBS - Syslog Server
8378 DECT IP-xBS - Syslog Server

◼Collect base station logs on a Syslog server

End of the module

enterprise.alcatel-lucent.com
OpenTouch Suite for MLE
OminPCX Enterprise Communication Server

8378 DECT IP-xBS

How to
✓ Collect xBS logs on a syslog server

Contents
1 Syslog server ................................................................................... 2
1.1. Install a free software ............................................................................. 2
1.2. Launch the Syslog server application ............................................................ 5
2 Send xBS Logs to the Syslog server ......................................................... 6
2.1. Declare the syslog server .......................................................................... 6
2.2. Select the “debug” syslog level for a base station ............................................ 6
2.3. Check the information’s received on the Syslog server ....................................... 6
 2
8378 DECT IP-xBS

Implementation

1 Syslog server

1.1. Install a free software

For lab purpose, Install the free software “Visual Syslog server” on the client PC
The installation program, visualsyslog_setup.exe, is available on the NAS server.
To get there, map a network drive on the classroom PC ( \\10.20.30.40\softs).

On the client PC: launch the “setup” file

 3
8378 DECT IP-xBS
 4
8378 DECT IP-xBS
 5
8378 DECT IP-xBS

1.2. Launch the Syslog server application

On the client PC: launch the application
 6
8378 DECT IP-xBS

2 Send xBS Logs to the Syslog server

Declare a Syslog server IP @ and port number in the OXE configuration.
Select the debug level for the base station id 0 and check that the information’s are
available in the syslog server application.

2.1. Declare the syslog server

PWT/DECT System / xBS system
SYSLOG IP address < Enter the IP address of the syslog server > 192.168.1.9
SYSLOG port < Enter the port number of the syslog server> 514
default value: 514

2.2. Select the “debug” syslog level for a base station

PWT/DECT System / xBS system / xBS base station
Base station Id Select the base station
Syslog level Debug

Possible choices are:

- Debug
- Normal operation
- Syslog off
- System Analyze

2.3. Check the information’s received on the Syslog server

On the syslog server application
OpenTouch Suite for MLE
OmniPCX Enterprise Communication server
8378 DECT IP-xBS - Supported Topologies
Lesson Summary

◼Supported Topologies

⚫ IP-xBS only
⚫ IP-xBS with Branch Office
⚫ Mixed xBS/TDM
⚫ Mixed xBS/TDM without Branch Office and overlap
⚫ Mixed xBS/TDM with Branch Office
⚫ Mixed IP-DECT/xBS
⚫ Mixed xBS/TDM in OXE network
⚫ Mixed xBS/TDM in campus
8378 DECT IP-xBS - Supported Topologies

◼IP-xBS only

• 1 node
• 8 PARI max
• 2048 base stations

PARI1 PARI2

Handover
External Handover
External inter node handover
Roaming
8378 DECT IP-xBS - Supported Topologies

◼IP-xBS with Branch Office

• 1 node
• 8 PARI max
SITE 1 • 2048 base stations
SITE 2

WAN

Handover
External Handover
External inter node handover
Roaming
SITE 3
8378 DECT IP-xBS - Supported Topologies

◼Mixed xBS/TDM
• One node
• 8 PARI max
External synchronization link • 2048 xBS
SITE 1 possible • 1000 RBS or 256 IBS

xBS PARI TDM PARI

RBS/IBS area

Handover
External Handover
External inter node handover
Roaming
8378 DECT IP-xBS - Supported Topologies

◼Mixed xBS/TDM without Branch Office and overlap

• 1 node
• 8 PARI max
SITE 1
• 2048 xBS
When it is not possible to have an external • 1000 RBS or 256 IBS
synchronization, the distance between the
area must be > 1km.

PARI xBS

Zone RBS/IBS

Handover
PARI TDM
External Handover
External inter node handover
Roaming
8378 DECT IP-xBS - Supported Topologies

◼Mixed xBS/TDM with Branch Office

• 1 node
Head quater : SITE 1 Head quater : IBS/RBS area • 8 PARI max
• 2048 xBS
• 1000 RBS or 256 IBS

PARITDM
PARI1 xBS

Branch office: IBS/RBS area

PARI TDM
WAN

Handover
External Handover
PARI2 xBS External inter node handover
Roaming

Branch office : SITE 2

8378 DECT IP-xBS - Supported Topologies

◼Mixed IP-DECT/xBS

Roaming of the A-GAP handsets only • 1 node

• 8 PARI max
SITE 1 • Ip-xBS and 8340 IP
DECT

PARI xBS PARI IP-DECT

IP-DECT area Handover

External Handover
External inter node handover
Roaming
8378 DECT IP-xBS - Supported Topologies

◼Mixed xBS/TDM in OXE network

Node 1: SITE 1 • Several nodes
Node 1: IBS/RB area • 8 PARI max
• 2048 xBS
• 1000 RBS or 256 IBS
• roaming
PARITDM
PARI1 xBS

Node 2: IBS/RBS area

PARI TDM

Two nodes are

not synchronized Handover
External Handover
External inter node handover
PARI2 xBS
Roaming

Node 2: SITE 1
8378 DECT IP-xBS - Supported Topologies

◼Mixed xBS/TDM in campus • Several nodes

Node 1 : SITE 1 • 8 PARI max
Node1 : IBS/RBS area • 2048 xBS
• 1000 RBS or 256 IBS
• Only 4400 hardware
• Nodes are synchronized via
PARITDM the INTOFS boards
PARI1 xBS

Node 2 : IBS/RBS area

PARI TDM

Two nodes are

synchronized Handover
External Handover
PARI2 xBS
External inter node handover
Roaming

Node 2 : SITE 1
End of the module

enterprise.alcatel-lucent.com
OpenTouch Suite for MLE
OminPCX Enterprise Communication Server

8378 DECT IP-xBS

How to
✓ Manage the multi sites (Branch Offices)

Contents
1 Multi-site configuration ...................................................................... 2
1.1. xBS Site .............................................................................................. 2
1.1.1. Create a Site ................................................................................................ 2
1.1.1. Modify a Site ................................................................................................ 2
1.2. Assign the xBS Base station to a site............................................................. 2
1.2.1. Modify the parameters..................................................................................... 2

2 Synchronization topology .................................................................... 3

2.1. Check the site number ............................................................................. 3
2.1. Check the synchronization tree of each site using the xBS web based management ..... 4
2.1.1. xBs web based management .............................................................................. 4

3 Roaming inter site............................................................................. 5

 2
8378 DECT IP-xBS

Implementation

1 Multi-site configuration
Add a new site with the name “BO” (for Branch Office) and move the xBS base station id
1 to it.
Modify the name of the site number 0 by the new name HQ (for head quarter).

1.1. xBS Site

1.1.1. Create a Site

PWT/DECT System / xBS System / xBS Site

Site Number 1
Site Name BO
Station Base Type DECT Europe

1.1.1. Modify a Site

PWT/DECT System / xBS System / xBS Site

Site Number 0
Site Name HQ

1.2. Assign the xBS Base station to a site

1.2.1. Modify the parameters

PWT/DECT System / xBS / xBS base station

Base station id 1 < consultation only>
Terminal Ethernet Address < Automatically assigned >
Location name FL1-01
Site Number 1

Notes
The default site assigned to a xBS is the site 0
 3
8378 DECT IP-xBS

2 Synchronization topology
Check if the base stations belong to the right site number, if each base station are
master inside its own site (remember, only one synchronization tree per Site).

2.1. Check the site number

Under mtcl
Command dectview xbs
(1)csa> dectview xbs

Thu May 12 09:16:07 CEST 2022

================= DECT RESOURCES BUSY STATE ===============

Resource Max busy free percent busy

-----------------------------------------------------
Link 276 0 276 0.00
LCEI 300 0 300 0.00
ADPCM 0 0 0
Buffer UA-> 135 0 135 0.00

**** XBS registration NODE 1 (my local node is 1) ****

+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
|Virtual @|XBS Site PARI-Area-RPN| Neqt|State |Location| IP @ | Mac @ |FW Version|Clusters|NR|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
| 1/00/051|000 0 HQ 0- 0- 0| 896|OK P +|GF-01 |192.168.1.149 |00:08:7b:16:4c:f9|0073B0003 |00000001| 0|
| 1/00/052|001 1 BO 0- 0- 1| 897|OK P +|FL1-01 |192.168.1.148 |00:08:7b:16:50:e6|0073B0003 |00000001| 0|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
NR = Number of Radio links established
NOK = out of service
OOS = outserv used; use inserv to put in service again
P = data sync Primary xbs (the one which collects data)
M = Master configured (for DECT synchronization)
B = Backup configured (for DECT synchronization)
+ = Master free running of DECT synchronization (not available in st-by CPU)
* = Master locked of DECT synchronization (not available in st-by CPU)

Region 0 (EUROPE) has 2 site(s) with 2 XBS in service.

(1)csa> exit
 4
8378 DECT IP-xBS

2.1. Check the synchronization tree of each site using the xBS web based management

2.1.1. xBs web based management

Browse the IP @ of the base station id 0 to check the synchronization tree.

https:// 192.168.1.148
Select “multi Cell”

See the DECT chain

information
 5
8378 DECT IP-xBS

Browse the IP @ of the base station id 1 to check the synchronization tree.

https:// 192.168.1.149
Select “Multi Cell”

See the DECT chain

information

3 Roaming inter site

For the lab purpose, we are going to simulate a roaming from the head quarter to the
branch office.
Switch off the handsets. Unplug the base station of the head quarter
Switch on the handsets and try to make calls
OpenTouch Suite for MLE
OmniPCX Enterprise Communication server
Firmware upgrade over the air of DECT handsets

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
Firmware upgrade over the air

OXE is able to upgrade DECT handsets using their radio channel

Only one communication channel New Command : downstat m

can be opened at a time with a The DECT application decide the •Display information about the handsets
handset order of the downloads and the firmware
•Display information about the downloads
•The Audio communication is preferred number of downloads that can be in progress
over downloading done in parallel according to the
•that means that a software download is •Allow to download a specific handset or a
stopped during an audio communication traffic and the number of base group of handsets
and will resume later station up and running

Software
The handsets switch on the new Upgrade
downloaded software version All 82x2 handsets are supported OXE
when they are put on a charger
cradle
Firmware upgrade over the air

◼Architecture Download Server

✓ Start/Stop the software download for the devices
✓ Monitor the download status of the devices
✓ Check the devices version
✓ Provide the list of candidate devices to download

Telephonic Application
✓ Handle of the list of devices for download
❖ Filter out unavailable devices
(for instance devices involved in conversation)
❖ Filter out the number of parallel download requests
according the load of the system
❖ Send the download request to the Download Server
✓ Upon a request from the Download Server, establish a DECT
data channel with a handset.

User interface
✓ Command line : downstat m

The max number of handsets that can be downloaded in parallel depends on the number of base stations
and on the ratio of radio channels that can be used for the download.
Firmware upgrade over the air

Characteristics OXE

• The feature is available through IBS, RBS and IP-xBS base

stations Binaries location on the Call Server:
• The theoretical duration of a download is between 6-8 hours
(1)csa> cd /usr2/downbin
• When switching on a standby CPU all downloads are stopped. (1)csa> ll bin82*
The Download Server resumes the downloads but not necessary -rw-r--r--. 1 mtcl tel 917153 Dec 4 13:45 bin8212
in the same order than on the main CPU -rw-r--r--. 1 mtcl tel 1045789 Jan 17 12:08 bin8232
-rw-r--r--. 1 mtcl tel 1994500 Nov 9 14:10 bin8242
-rw-r--r--. 1 mtcl tel 1698947 Jan 14 08:14 bin8262
-rw-r--r--. 1 mtcl tel 1699461 Jan 14 08:33 bin8262EX

Restrictions

• The handset firmware MUST support FWU protocol in order to

allow an on-the-air upgrade
• If not, the handsets have to be upgraded manually using USB
link as described in the documentation
• Handsets on visited node in case of roaming/campus are not
downloaded
Firmware upgrade over the air

◼Management

Enable /disable automatic download of the DECT handsets

Enable /disable automatic download of a specific DECT handset

Note: If the parameter is set to « Yes » , the upgrade of the DECT

handset must be bone manually using the command downstat m
<directory number>.
Firmware upgrade over the air

◼Command line : downstat m

(1)csa> downstat m

Tue Apr 16 14:41:07 CEST 2019

*** DECT 8212 system binary version: v0012

*** DECT 8232 system binary version: v4383
*** DECT 8242 system binary version: v6382
*** DECT 8262 system binary version: v5681
*** DECT 8262EX system binary version: v7681

*** 82x2 DECT phones: 0/2 (with system binary/declared) *** downstat m
Display information about the download of the DECT handsets
*** Automatic FirmWare Update activated ***

DECT phones downloaded informations : downstat m n <directory number 1>, <directory number 2>,...
------------------------------------- Immediate download of one or a list of 82x2 handsets
1 Display DECT phones with system binary
2 Display download status downstat m b binary name n <directory number 1>,
3 Display all downloadable DECT phones
<directory number 2>,...
4 Download one DECT phone
5 Cancel the download on a DECT phone Immediate download of one or a list of 82x2 handsets with a
0 Quit specific binary

Your choice ?
Firmware upgrade over the air

◼Command line : downstat m

DECT phones downloaded information :
-------------------------------------
1 Display DECT phones with system binary
2 Display download status
3 Display all downloadable DECT phones
4 Download one DECT phone
5 Cancel the download on a DECT phone
0 Quit

Your choice ? 1
Display the binary version
*** DECT 8212 system binary version: v0012
of the DECT handsets *** DECT 8232 system binary version: v4383
*** DECT 8242 system binary version: v6382
*** DECT 8262 system binary version: v5681
*** DECT 8262EX system binary version: v7681

*** 82x2 DECT phones: 0/2 (with system binary/declared) ***

*** Automatic Firmware Update activated ***

Firmware upgrade over the air

◼Command line : downstat m DECT phones downloaded information :

-------------------------------------
1 Display DECT phones with system binary
2 Display download status
3 Display all downloadable DECT phones
4 Download one DECT phone
5 Cancel the download on a DECT phone
0 Quit

Your choice ? 2

*** DECT 8212 system binary version: v0012

*** DECT 8232 system binary version: v4383
*** DECT 8242 system binary version: v6382
*** DECT 8262 system binary version: v5681
*** DECT 8262EX system binary version: v7681

*** 82x2 DECT phones: 0/2 (with system binary/declared) ***

Display the download status *** Automatic Firmware Update activated ***

of the DECT handsets 8242 download status (A = Auto download - X = Auto exclude - M = Manual download with downstat)
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| QMCDU | Neqt | Name | Type | Current | Download status | Note |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| 31015 | 01278 | Maxine | 8242 | v6781 | A 7.1% WRITING | |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
Total: 1

8262 download status (A = Auto download - X = Auto exclude - M = Manual download with downstat)
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| QMCDU | Neqt | Name | Type | Current | Download status | Note |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| 31016 | 01279 | Eric | 8262 | v5381 | A 8.2% WRITING | |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
Total: 1
Firmware upgrade over the air
8262 download status (A = Auto download - X = Auto exclude - M = Manual download with downstat)
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
Help about the field« download status » | QMCDU | Neqt | Name | Type | Current | Download status | Note |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| 31016 | 01279 | Eric | 8262 | v5381 | A 8.2% WRITING | |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
Total: 1

Mode (A, X, M)
A Automatic download: the set is in automatic mode. System automatically updates the set if it is not in the current pbx release.
X This set is excluded from automatic mode. It will NOT be updated by the system.
M The set was excluded from the automatic mode. A manual download was launched through “downstat m” menu 4.

Percentage: either 0.0% if the set has no current download or the actual percentage of progress.

Automation state:
IDLE: virtual state for a bigger real state. The set stays like this until the system decided to load a new firmware.

ERASE REQUESTED: system asked to the set to prepare the memory flash zone for the new firmware downloaded. Eventually telling to put the set
back on his cradle: "charger required".

WRITING: system is in the phase of writing the new firmware.

PAUSED: the set is not available for the moment. The system is waiting to continue the upload

WAIT FOR FLASHING: indicates that the system asked to the set to start the new firmware. This always needs a restart of the set on his cradle

ERROR: the protocol failed in automatic mode & the set will be downloaded again later. There is not further information.
Firmware upgrade over the air

◼Command line : downstat m DECT phones downloaded information :

-------------------------------------
1 Display DECT phones with system binary
2 Display download status
3 Display all downloadable DECT phones
4 Download one DECT phone
5 Cancel the download on a DECT phone
0 Quit

Your choice ? 3

*** DECT 8212 system binary version: v0012

*** DECT 8232 system binary version: v4383
*** DECT 8242 system binary version: v6382
*** DECT 8262 system binary version: v5681
*** DECT 8262EX system binary version: v7681

*** 82x2 DECT phones: 2/3 (with system binary/declared) ***

Display the list of
*** Automatic FirmWare Update activated ***
downloadable DECT handsets
8242 with system binary
+----------+-------+-----------------------------+---------+
| QMCDU | Neqt | Name | Type |
+----------+-------+-----------------------------+---------+
| 31015 | 01273 | Maxine | 8242 |
+----------+-------+-----------------------------+---------+
Total: 1

8212 download status (A = Auto download - X = Auto exclude - M = Manual download with downstat)
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| QMCDU | Neqt | Name | Type | Current | Download status | Note |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| 31017 | 01477 | DECT Handset | 8212 | v0009 | A 0.0% IDLE | |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
Total: 1
Firmware upgrade over the air

◼Command line : downstat m

DECT phones downloaded information :

-------------------------------------
Manual download of a 1
2
Display DECT phones with system binary
Display download status
DECT handsets 3
4
Display all downloadable DECT phones
Download one DECT phone
5 Cancel the download on a DECT phone
0 Quit

Your choice ? 2
DECT phones downloaded information :
------------------------------------- *** DECT 8212 system binary version: v0012
1 Display DECT phones with system binary *** DECT 8232 system binary version: v4383
2 Display download status *** DECT 8242 system binary version: v6382
3 Display all downloadable DECT phones *** DECT 8262 system binary version: v5681
4 Download one DECT phone *** DECT 8262EX system binary version: v7681
5 Cancel the download on a DECT phone
0 Quit *** 82x2 DECT phones: 2/3 (with system binary/declared) ***

Your choice ? 4 *** Automatic FirmWare Update activated ***

Enter a directory number you want to manage : 31017 8212 download status (A = Auto download - X = Auto exclude - M = Manual download with downstat)
Download requested for handset 31017 +----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| QMCDU | Neqt | Name | Type | Current | Download status | Note |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| 31017 | 01477 | DECT Handset | 8212 | v0009 | M 0.4% WRITING | |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
Total: 1
Note: the parameter « Exclude from automatic FW update
for the DECT user must be set to « Yes »
Firmware upgrade over the air DECT phones downloaded informations :
-------------------------------------
1 Display DECT phones with system binary
2 Display download status
◼Command line : downstat m 3 Display all downloadable DECT phones
4 Download one DECT phone
5 Cancel the download on a DECT phone
0 Quit

Your choice ? 2

*** DECT 8212 system binary version: v0012

*** DECT 8232 system binary version: v4383
Immediate download *** DECT
*** DECT
8242
8262
system
system
binary
binary
version:
version:
v6382
v5681
of a list of 82x2 handsets *** DECT 8262EX system binary version: v7681

*** 82x2 DECT phones: 2/5 (with system binary/declared) ***

*** Automatic FirmWare Update activated ***

8212 download status (A = Auto download - X = Auto exclude - M = Manual download with downstat)
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
(1)csa> downstat m n 31018,31019 | QMCDU | Neqt | Name | Type | Current | Download status | Note |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| 31017 | 01477 | DECT Handset | 8212 | v0009 | M 98.4% PAUSED | |
Fri May 10 14:12:29 CEST 2019
| 31018 | 01478 | DECT 1 Handset | 8212 | v0009 | M 0.0% IDLE | |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
numan list: 31018,31019 Total: 2
Download requested for handset 31019
Download requested for handset 31018 8242 download status (A = Auto download - X = Auto exclude - M = Manual download with downstat)
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| QMCDU | Neqt | Name | Type | Current | Download status | Note |
+----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
| 31019 | 01275 | DECT 2 Handset | 8242 | v6980 | M 0.0% IDLE | |
Note: the parameter « Exclude from automatic FW update +----------+-------+-----------------------------+---------+---------+-------------------------------+------------------+
Total: 1
for the DECT user must be set to « Yes »
OpenTouch Suite For MLE
OmniPCX Enterprise Communication server
Introduction to radio coverage
Radio coverage

Three important elements must be processed

Coverage Capacity Audio Quality

a subscriber who
The choice of base Ensuring the is not covered or
Covering the area Ensuring user has no channels
positions is crucial establishment of
where the service is
to be provided
for correct communications in satisfaction available to
coverage the covered area make a call will
not be satisfied
Radio coverage

Received Signal Strength Indication by the handset

RSSI : Received Signal Strength Indication

Radio power : 250 mW

Pe= 23 dB
 Coverage and Speech Quality
Relation between coverage and voice quality in an indoors environment

Rs is a distance corresponding to a RSSI level

for satisfactory voice quality:
-70 dBm (for easy coverage) Rs
- 60dBm (for tricky coverage)

1 2 3 4 5 6

1. Excellent
Rl 2. Good
3. Satisfactory
4. Poor
5. Very poor
6. Almost no speech at all
Rl is a distance depending on the RF sensitivity of the handsets
and on the environment (interferers, fading, etc.…)
Coverage and Speech Quality

Minimum RSSI level between and ALE DECT handset and a base station

Zone of voice quality: Satisfactory

-70 dB
Site with no coverage problem(s) = Easy

• Offices tertiary
• Store rooms (no obstacles and no metallic
partitions),
• Etc.
Coverage and Speech Quality

Minimum RSSI level between an ALE DECT handset and a base station

Zone of voice quality: Satisfactory

-60 dB
Site with difficult coverage (Metallic environment)
(=Tricky)

• Production plant,
• certain buildings using metallic partitions,
clean rooms
• etc.
Coverage and IP –xBS over the air synchronization

Minimum RSSI level between the base stations

Zone of quality for DAP synchronization

-80 dB

Over the air synchronization

Site Survey Kit

◼The “Site Survey Kit” (SSK) allows you to do a Site Survey

⚫ TDM DECT system

⚫ IP-xBS system
⚫ IP DECT system

The content of the DECT Site Survey Kit is:

• One suitcase
• One 8378 IP-xBS integrated antenna dedicated for the survey kit
• One 8378 IP-xBS for external antenna dedicated for the survey kit
• One gain antenna 8dBi with two TNC to SMA cables
• 2x power banks to power the base stations with 2 micro USB to USB A cable to charge the
batteries
• One power to connect power bank to base stations
• One ethernet cable to connect a PC on a Base station
• One support to assembly Base station, power bank and external antenna
• 2x 8242 DECT handset with battery and belt clip
• 2x Dual desktop charger for 8242 DECT handsets
• 2x verticals pouches for 8242 DECT Handsets
SSK • 2x wired headsets for 8242 DECT Handsets
Ref: 3BN67191AA • 2x power supply for 8242 DECT Handsets dual charger Telescopic Tripod for the Site Survey Kit
Ref: 3BN67192AA
Engineering rules

◼Documentation available on the BP web site

⚫ im_DECT_EngineeringRules_8AL90874USAA_6a.pdf
OpenTouch Suite for MLE
OmniPCX Enterprise Communication Server

Introduction to radio coverage

How to
✓ Switch On / Switch Off the survey mode on the DECT handset

Contents
1 Switch On the survey mode on the DECT handset ........................................ 2
1.1. Switch On the survey mode ....................................................................... 2
1.2. Switch Off the survey mode....................................................................... 4
 2
Introduction to radio coverage

Implementation

1 Switch On the survey mode on the DECT handset

Switch on the Survey mode on the 8244 DECT handset. Then, move around the place to
looking for the limit of the coverage area (-70dB) of your system.

1.1. Switch On the survey mode

On the DECT phone
in idle homepage, press OK
key to get menu screen

type *7378423* (mnemonic:

*service*)

Select Site Survey mode in the

menu
 3
Introduction to radio coverage

Press “On” to activate the

survey mode

The survey mode is now

activated
 4
Introduction to radio coverage

1.2. Switch Off the survey mode

On the DECT phone
Press “Off” to de-activate the
survey mode

Press “On hook”

Back to the idle homepage

OpenTouch Suite For MLE
OmniPCX Enterprise Communication server
8379 DECT IBS – Overview

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
8379 DECT IBS

◼IBS for Intelligent Base Station Board type Numbers

Base stations UAI4, 2

⚫ Connected on an UA board per coupler MIX2/4/8,
MIX4/4/8, 2
 UAI, eUA, and MIX MIX2/4/4,
MIX0/4/4
⚫ 1 UA link or 2 UA links UAI8, 4
MIX0/8/4,
 1 UA link corresponds at 3 B channels available for voice communications MIX4/8/4
UAI16 or 8
 2 UA link corresponds at 6 B channels available for voice communications UA16
 Master link connected on an even port, slave link connected on the next odd port
UA32 16

⚫ Only one PARI number available

⚫ Up to 256 base stations for the entire system

8379 DECT IBS - Connectivity

Connectivity Connected on UA board

Cable SYT 0.5 mm Max length : 800m

Cable LY278 0.6 mm Max length : 1200m

8379 DECT IBS - Wiring
8379 DECT IBS – Base station models

◼3 models
Options
• 3BN67172AA Explosion proof model 4070 IO-Ex
• Wall mounting kit, external antennas, connectors, cords

8379 DECT IBS integrated antennas

External antennas

8379 DECT IBS for external antennas

Outdoor

8379 DECT IBS outdoor

8379 DECT IBS - Topologies

◼Common Hardware
Handover
▪ 1 PARI
▪ 256 IBS
Clock sync : P 200
Roaming

No Clock sync over IP

OXE
LAN
Clock sync : P 200
8379 DECT IBS - Topologies

Floor 2

With the common hardware all the

base stations must be connected on
the same media gateway to allow
the Handover over the site Floor 1

Ground floor

UA link Clock sync for the DECT

OXE

LAN
8379 DECT IBS - Topologies

◼Common Hardware
Handover
Head Quater
▪ 1 PARI
▪ 256 IBS
Roaming

OXE
WAN

Branch Office
8379 DECT IBS - Topologies

◼Crystal Hardware
Handover

▪ 1 PARI
▪ 256 IBS

INTOF link

DECT SYNC
Fonction

Main ACT Peripheral ACT

The ACTs including the IBS stations must be interconnected by INTOF boards
which carry the synchronization

The DECT synchronization of IBS is realized by the CPU7 step 2 /CPU8 or by a DECT8 declared in “DECT_SYNC” for better synchronization
8379 DECT IBS - Topologies

◼Crystal Hardware
Handover
▪ 1 PARI
▪ 256 IBS

Roaming

DECT SYNC
Fonction

LAN
DECT SYNC
Fonction

Main ACT Peripheral ACT

The DECT synchronization of IBS in the remote shelf is realized by the DTM module on the INTIP3 B
8379 DECT IBS - Topologies

◼Crystal Hardware & Common Hardware

▪ 1 PARI Handover
▪ 256 IBS

Roaming

INTOF link

DECT SYNC
Fonction
Peripheral ACT
Main ACT

LAN
OpenTouch Suite for MLE
OmniPCX Enterprise Communication Server

IBS DECT Infrastructure deployment

How to
✓ Deploy IBS infrastructure for DECT solution

Contents
1 General settings ............................................................................... 2
1.1. Global parameters .................................................................................. 2
1.2. PARI number ........................................................................................ 3
2 Hardwre configuration ....................................................................... 3
2.1. IBS PARI assignment ................................................................................ 3
2.2. IBS station management ........................................................................... 4
3 Maintenance ................................................................................... 4
3.1. Edition of IBS station status and information ................................................... 4
3.2. Reset of IBS station ................................................................................ 6

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
 2
IBS DECT Infrastructure deployment

Implementation

1 General settings
Restore the Database with the default configuration (Done during the LAB “POD
configuration).
Configure the system in order to use IBS station(s) with following parameters:
- PLI = 31
- Authentication mode with AC code = 1111

1.1. Global parameters

PWT/DECT System
Complete the required fields
for IBS use

Radio base type Select IBS (or Mixed if RBS and/or xBS stations are also used)
PLI for CTM 31
AC System 1111
Security level Authentication
Station base type Select the area (e.g. DECT Europe)

Notes
Security level:
- “Identity” by default (no authentication)
- “Authentication” (Use of AC code during set registration)
- Can’t be Encryption (Only for RBS)
AC System: (optional, depends on the security level)
- Corresponds to a code used during the installation of the DECT sets
- Only DECT sets with this code can be registered in your system
- You have to enter it on the set during the installation process

Warning
IN CASE OF MIXED MODE, SO WITH MULTI PARI NUMBERS, THE PLI MUST BE ADAPTED.
 3
IBS DECT Infrastructure deployment

1.2. PARI number

Manage the IBS PARI number as 100004101x0 with:

- x: POD number

PWT/DECT System/ IBS

Complete the fields

PARI Value Enter a PARI number (e.g. 10000410110 for POD 1)

Area type Specify the number of stations per area in order to optimize the DECT terminals search
according to the roaming

2 Hardwre configuration

2.1. IBS PARI assignment

Assign the IBS PARI number to the used media gateway

Shelf / <concerned media gateway>

In the settings of the
concerned media gateway,
configure the correct PARI for
IBS

PARI Number Select the “PARI IBS”

 4
IBS DECT Infrastructure deployment

2.2. IBS station management

In a media gateway, create an IBS station on a free equipment of the MIX board
- Use 2 UA links

Shelf / <concerned media gateway> / Board / <concerned UA board> / IBS

Create an IBS station on a UA
board

Equipment address Enter the physical address of the base station (an even port if 2 UA links used)
Location name Enter a name for this base station
Line delay Select the distance between the UA board to the base station
- Short line (O-400M)
- Medium line (400-800M)
- Long line (800-1200M)
Number of UA links Select 1 UA link (3 TS) or 2 UA links (6 TS)
The next port address is reserved by the system if you select “2”.
IBS generation Select the generation of the IBS station
- (IBS 1G for 1st generation)
- IBS 2G for 2nd generation

3 Maintenance

3.1. Edition of IBS station status and information

Use the “dectview” command to verify the IBS station(s) status

(1)csa> dectview ibs

Wed May 18 09:02:02 CEST 2022

================= DECT RESOURCES BUSY STATE ===============

Resource Max busy free percent busy

-----------------------------------------------------
Link 276 0 276 0.00
LCEI 300 0 300 0.00
ADPCM 0 0 0
Buffer UA-> 135 0 135 0.00

================= IBS States =======================

2/01/34 neqt 359 RPN : 0 INSERV just 3 channels DECT V 2G 4070 53.02 odd AUTHE NORMAL NbRadios=0
 5
IBS DECT Infrastructure deployment

Using “listerm” command, verify the status of UA links used for IBS station(s)
- Use: listerm <mg> <cpl>

(1)csa> listerm 2 1

Wed May 18 09:02:35 CEST 2022

-------------------------------------------------------------------------
|Coupler: 2 1 Logic type: CPL_MIX Board:MIX484 State: IN SERVICE |
|-------------------------------------------------------------------------|
| Cry:Cpl:ac:term| neqt | typ term | dir nb | Out of service cause |
|-------------------------------------------------------------------------|
| 2 1 0 32 | 00357 | ALE-30h TDM | 31020 | . . . . . . . . . . |
| 2 1 0 33 | 00358 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 34 | 00359 | IBS/3B+D | | . . . . . . . . . . |
| 2 1 0 35 | 00360 | IBS/3B+D | | . . . . . . . . . . | IBS in service
| 2 1 0 36 | 00361 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 37 | 00362 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 38 | 00363 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 39 | 00364 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 64 | 00365 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 65 | 00366 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 66 | 00367 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 67 | 00368 | T_RESU | | A . I . . . . . Y . |
-------------------------------------------------------------------------
| (A: att_mserv|S: hs smooth), C: hs_defich, I: hs_isolauto, X: hs_isolman|
| T: hs_terdef U: hs_usdef, P: hs_errparite, B: hs_bascul, Y: hs_cristisol|
-------------------------------------------------------------------------
| Nombre total de terminaux hors service : 0 |
| Nombre total de terminaux en service : 3 |
|-------------------------------------------------------------------------|

(1)csa> listerm 2 1

Wed May 18 09:02:35 CEST 2022

-------------------------------------------------------------------------
|Coupler: 2 1 Logic type: CPL_MIX Board:MIX484 State: IN SERVICE |
|-------------------------------------------------------------------------|
| Cry:Cpl:ac:term| neqt | typ term | dir nb | Out of service cause |
|-------------------------------------------------------------------------|
| 2 1 0 32 | 00357 | ALE-30h TDM | 31020 | . . . . . . . . . . |
| 2 1 0 33 | 00358 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 34 | 00359 | IBS/3B+D | | . . . . T . . . . . | IBS out of
| 2 1 0 35 | 00360 | IBS/3B+D | | . . . . T . . . . . | service
| 2 1 0 36 | 00361 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 37 | 00362 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 38 | 00363 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 39 | 00364 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 64 | 00365 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 65 | 00366 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 66 | 00367 | T_RESU | | A . I . . . . . Y . |
| 2 1 0 67 | 00368 | T_RESU | | A . I . . . . . Y . |
-------------------------------------------------------------------------
| (A: att_mserv|S: hs smooth), C: hs_defich, I: hs_isolauto, X: hs_isolman|
| T: hs_terdef U: hs_usdef, P: hs_errparite, B: hs_bascul, Y: hs_cristisol|
-------------------------------------------------------------------------
| Nombre total de terminaux hors service : 0 |
| Nombre total de terminaux en service : 3 |
|-------------------------------------------------------------------------|
 6
IBS DECT Infrastructure deployment

Using “listibs” command, edit information about the station:

- Use: listibs p <mg> <cpl> 0 <equip.>

(1)csa> listibs p 2 1 0 34

Wed May 18 09:03:51 CEST 2022

IBS_name = Floor_1A;
line_delay = SHORT_LINE_0_400M;
nb_ua_link = 2;
rpn = 0;
reset = 0;
antenna_diversity = 1;
encryption_supported = 1;
nb_ua_link_present = 1;
radio_type = 0;
ibs_generation = 1;

3.2. Reset of IBS station

Reset an IBS station using “outserv” and then “inserv” commands.
- Use: “command” p <mg> <cpl> 0 <equip.>

(1)csa> outserv p 2 1 0 34

Wed May 18 09:04:21 CEST 2022

Do you really want to put out of service this device ? (Y/N) :Y

(1) csa>

(1)csa> inserv p 2 1 0 34

Wed May 18 09:04:54 CEST 2022

Do you really want to put in service this device ? (Y/N) :Y

(1)csa>
OpenTouch Suite for MLE
OmniPCX Enterprise

Pod Configuration for the labs

How to
✓ Configure the Pod for the labs

Contents
1 POD set up ..................................................................................... 2
1.1. OXE Preconfiguration .............................................................................. 2
1.2. Rack and boards .................................................................................... 2
1.2.1. Hybrid Mode (RLAB + Classroom equipment) ........................................................... 2
1.3. Users ................................................................................................. 3
1.3.1. Hybrid Mode (RLAB + Classroom equipment) ........................................................... 3
1.4. External SIP gateway ............................................................................... 4
1.5. DID Translation ..................................................................................... 4
1.6. External calls........................................................................................ 5

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
 2
Pod Configuration for the labs

Implementation

1 POD set up

Start all the Virtual machines:

1.1. OXE Preconfiguration

OXE VMs used for this training are already configured (Database and Linux Data), such as:
• Software licenses are restored
• SSH is disabled
• NTP Server (192.168.1.252) is declared
• FlexLM Server (192.168.1.80) is declared
• DHCP server is activated
o VLAN 1 IP @ range: 192.168.1.145….192.168.1.155
• Shelves / boards are created
• Users (Deskphones & softphones) are created
• Voice guides are downloaded
• Public SIP trunk group is created

1.2. Rack and boards

Racks and boards are created in the OXE database.

1.2.1. Hybrid Mode (RLAB + Classroom equipment)

Please check (or configure if needed) that the equipment, available for this training, is
in service (with the following parameters):

For the MAIN site

• Hardware Rack 1U
o Rack N° 2
o GD4 (slot 0) IP @: 192.168.1.12/24
o GD4 MAC @: to be checked in the classroom
o MIX484 (slot1)
• Software Rack 3U (OMS)
o Rack N° 4
o Virtual GD4 (slot 0) IP @: 192.168.1.13/24
o Virtual GD4 MAC @: 00:50:56:01:01:13
 3
Pod Configuration for the labs

1.3. Users

1.3.1. Hybrid Mode (RLAB + Classroom equipment)

Users are created in the OXE database.

Bring into service the IPDSP softphone and Deskphones as mentioned in the table below.

Directory Nb First name / Name Set Type Comment

31000 Brad Barkley IP DSP Installed on PC Classroom
31010 Charles Cooper ALE-500 (IP NOE) Dynamic IP @
31011 Calixta Cartier ALE-300 (IP NOE) Dynamic IP @
31012 Caitleen Connor ALE-20H (IP NOE) Dynamic IP @
31020 David Douglas ALE-30H (TDM/UA) -

Don’t forget to specify the TFTP server IP @ in the IP DSP settings.

IP DSP
Do a right click and go to
“Settings”

Select the “Network” tab

And enter the right TFTP

server IP @ (OXE CS Main IP
@)

TFTP Server Main 192.168.1.3

 4
Pod Configuration for the labs

1.4. External SIP gateway

The Public SIP trunk group is already configured in the OXE database, but you must specify your own
“POD” parameters into the external SIP gateway, to activate the access to the public SIP carrier

According to your POD number, configure 2 parameters in your external SIP gateway:
• Registration ID: pbxN (where N is your POD Number)
o e.g.: for POD 3, pbx3
• Outgoing username= pbxN (where N is your POD Number)
o e.g.: for POD 3, pbx3

SIP/SIP Ext. Gateway

Select your external SIP
gateway

Registration ID pbxN (where N is your POD number)

For POD 3: Registration ID= pbx3
Outgoing username pbxN (where N is your POD number)
For POD 3: Outgoing username= pbx3

1.5. DID Translation

The DID translation of your system must match your POD number.

According to your POD number, configure the DID translator as follow:

• First external number: 33210N41000 (where N is your POD Number)
• First internal number: 31000
• Range size 500
 5
Pod Configuration for the labs

Translator/External Numbering Plan/Default DID num. translator

“create” button

First external number 33210N41000 (where N is your POD Number)

For POD 3: First external number= 33210341000
First internal number 31000
Range Size 500

1.6. External calls

To make sure that access to public SIP carrier is working properly, set up some outgoing
calls.
Refer to the document SIP Carrier Simulator to know how to use the SIP simulator.
OpenTouch Suite for MLE
OminPCX Enterprise Communication Server

8378 DECT IP-xBS – Mixed DECT infrastructure (TDM & xBS)

How to
✓ Deploy 8378 IP-xBS base stations on an OXE having a TDM DECT solution

Contents
1 Topology ........................................................................................ 3
1.1. Configuration........................................................................................ 3
2 IP- xBS configuration.......................................................................... 4
2.1. Global DECT parameters .......................................................................... 4
2.1.1. Select the Radio Base Type ............................................................................... 4
2.1.2. Manage the PLI.............................................................................................. 4
2.1.3. Manage the AC code ....................................................................................... 4
2.2. xBS parameters ..................................................................................... 4
2.2.1. Declare the number of PARI for using the IP-xBS ...................................................... 4
2.2.2. xBS WBM ..................................................................................................... 5
2.3. xBS PARI ............................................................................................. 5
2.3.1. Create a PARI ............................................................................................... 5
2.4. xBS Site .............................................................................................. 5
2.4.1. Change the name of the site 0 ........................................................................... 5
2.5. xBS Base station .................................................................................... 5
2.5.1. Modify the parameters..................................................................................... 5
2.5.2. Check the xBS to clusters ................................................................................. 6

3 DHCP Management ............................................................................ 6

 2
8378 DECT IP-xBS – Mixed DECT infrastructure (TDM & xBS)

3.1. DHCP server (internal or external) ............................................................... 6

4 xBS registration ................................................................................ 6
4.1. Enable the registration of the xBS ............................................................... 6
4.2. Check the status of the xBS ....................................................................... 7
 3
8378 DECT IP-xBS – Mixed DECT infrastructure (TDM & xBS)

Implementation

1 Topology

Setup an IP-xBS solution on a site with an existing IBS infrastructure. The IBS PARI is
100004101x0. The new xBS PARI will be 100004101x4 ( x = POD number)
The PLI value will be 30. With that all DECT users will be able to connect on all DECT
base stations (xBS & TDM).

1.1. Configuration

IBS PARI : 100004101x0 xBS PARI : 100004101x4

RPN 0 RPN 1
RPN 0

PLI = 30
 4
8378 DECT IP-xBS – Mixed DECT infrastructure (TDM & xBS)

2 IP- xBS configuration

Deploy an IP-xBS solution with one PARI in a single site.
- PARI number: 100004101x4 (x = platform number)
- PLI = 30
- AC code = 1111

2.1. Global DECT parameters

2.1.1. Select the Radio Base Type

PWT/DECT System
Radio base type Mixed
Station Base Type DECT Europe

2.1.2. Manage the PLI

PWT/DECT System
PLI for CTM 30

Notes
In multi PARI or in mixed mode, the PLI must be adapted

2.1.3. Manage the AC code

PWT/DECT System
AC System 1111
Security level Authentication

Notes
The AC code is optional

2.2. xBS parameters

2.2.1. Declare the number of PARI for using the IP-xBS

PWT/DECT System / xBS System

Number of PARI 1

Notes
Up to 8 PARI
 5
8378 DECT IP-xBS – Mixed DECT infrastructure (TDM & xBS)

2.2.2. xBS WBM

PWT/DECT System / xBS System

Allow xBS Web Based YES
Management
xBS WBM engineer password <Enter your password>
(Default: engineer!01)
xBS WBM admin password <Enter your password>
(Default: Admin!00)

2.3. xBS PARI

2.3.1. Create a PARI

PWT/DECT System / xBS System / xBS Pari

PARI Number 0
PARI Value 100004100x4 < this is an example of PARI >
Area type 1 area of 256 xBS

2.4. xBS Site

2.4.1. Change the name of the site 0

PWT/DECT System / xBS System / xBS Site

Site Number 0
Site Name BREST
Station Base Type DECT Europe

Notes
By default, the site 0 is created

2.5. xBS Base station

2.5.1. Modify the parameters

PWT/DECT System / xBS / xBS base station

Terminal Ethernet Address < Automatically assigned >
Location name GF-01
Phone COS 0
Site Number 0
PARI Number 1
Location Area 0
RPN < consultation only>

Notes
When the base station is registered in the OXE, the MAC @ of the base station is present and the system has
been assigned an RPN value to the xBS.
 6
8378 DECT IP-xBS – Mixed DECT infrastructure (TDM & xBS)

2.5.2. Check the xBS to clusters

PWT/DECT System / xBS / xBS base station

Cluster 0 YES
Cluster 1 YES or NO
Cluster 2 YES or NO
Cluster 3 YES or NO
Cluster 4 YES or NO
Cluster 5 YES or NO
Cluster 6 YES or NO
Cluster 7 YES or NO

Notes
By default, all xBS belong to the cluster 0.

3 DHCP Management
A range of IP addresses in the internal OXE DHCP server already exit
- Range: 192.168.1.145 to 192.168.1.155

3.1. DHCP server (internal or external)

Notes
Technical documentation: oxe12.1_sd_IP_PCXNetworks_8AL91007USAH_1_en.pdf
A new Vendor Class for the xBS: Vendor id: alcatel.ipxbs.0

4 xBS registration

Enable the registration on the OXE and plug the two xBS.

4.1. Enable the registration of the xBS

PWT/DECT System / xBS System
Registration node 1
Registration enabled YES
Default PARI for registration 1
Default location area for reg. 0

Notes
Don’t forget to specify the registration node, default PARI for registration and the Default location area for reg.
With the default value, it doesn’t work.
 7
8378 DECT IP-xBS – Mixed DECT infrastructure (TDM & xBS)

4.2. Check the status of the xBS

Under mtcl
Command dectview xbs
(1)csa> dectview xbs

Wed May 11 09:06:35 CEST 2022

================= DECT RESOURCES BUSY STATE ===============

Resource Max busy free percent busy

-----------------------------------------------------
Link 276 0 276 0.00
LCEI 300 0 300 0.00
ADPCM 0 0 0
Buffer UA-> 135 0 135 0.00

**** XBS registration NODE 1 (my local node is 1) ****

+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
|Virtual @|XBS Site PARI-Area-RPN| Neqt|State |Location| IP @ | Mac @ |FW Version|Clusters|NR|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
| 1/00/051|000 0 Labo_BR 0- 0- 0| 896|OK P | GF-01 |192.168.1.149 |00:08:7b:16:4c:f9|0073B0003 |00000001| 0|
| 1/00/052|001 0 Labo_BR 0- 0- 1| 897|OK +| FL1-01 |192.168.1.148 |00:08:7b:16:50:e6|0073B0003 |00000001| 0|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+--+
NR = Number of Radio links established
NOK = out of service
OOS = outserv used; use inserv to put in service again
P = data sync Primary xbs (the one which collects data)
M = Master configured (for DECT synchronization)
B = Backup configured (for DECT synchronization)
+ = Master free running of DECT synchronization (not available in st-by CPU)
* = Master locked of DECT synchronization (not available in st-by CPU)

Region 0 (EUROPE) has 1 site(s) with 2 XBS in service.

(1)csa> exit
OpenTouch Suite for MLE
OmniPCX Enterprise Communication server
DECT handset automatic re-registration
DECT handset automatic re-registration

Re-registration is mandatory when

One PARI Multi PARI

✓ We increase the DECT capacity
✓ We deploy Mixed DECT infrastructure
RPN
DECT
PLI = 31 PLI = 31

OXE
RPN
PARI =10000412344
PARI =10000412340

PARI needs PLI = 29

to be changed

PLI = 29
RPN RPN
DECT PARI =10000412350
PLI = 31 PLI = 31 OXE

OXE PARI =10000476540

DECT handset automatic re-registration

Till R12.3
Not convenient when many handsets are deployed on a site
• The handset must be unregistered
(need to collect all the handset). Moreover, this must be done in a
• Command “dectrm”
short delay, because it leads to service interruption.
• And registered again with the new identifier (PARI +
PLI)
• Command “dectinston”
• Manipulation must be done on the Handset

In R12.3, a new way to push the new

identifier (PARI + PLI) to the handset,
with no action on the phone
• Command dectinston with new options
• dectinston -update or -forceUpdate
• indication of PARI and PLI is mandatory, as long as
The new identifiers (PARI+ PLI) are sent to the handset a list of handsets to re-register
that updates its internal data. • <directory number list> single directory number,
the re-registration is seamless for the handset’s user. or -f <file>, where “file” contains the list of
directory numbers to update.
• “-pari”: the new PARI attributed to the handset
• “-pli”: the new PLI attributed to the handset
• In case of failure, the handset keeps its previous
installation parameters
DECT handset automatic re-registration

◼Supported handsets and infrastructure 82x2 handsets support automatic

re-registration from version:
• 8212 – v0012
All 82x2 handsets (8212, 8232,8242,8262, 8262EX) are • 8232 – v4383
supported • 8242 – v6382
• 8262 – v5681
• 8262Ex – v7681
Available for IBS, RBS and xBS

Not available with IP-DECT

When handsets are already deployed with
older software versions, they need to be
Handsets must be already registered on the system, updated first
and running • Thanks to Firmware upgrade over the air
feature
• 82x2 handsets can be automatically updated
DECT handset automatic re-registration

◼Performance
⚫ Total duration of a batch of handsets update is proportional to the duration of one set (2-3s)
⚫ Unitary duration is split into two parts:
 Paging of the handsets: from 1,3s for a reachable handset to 6,5s for a handset that is out of coverage, with default paging
configuration (5 paging retransmissions)
 Duration of the procedure: about 800ms

◼Security
⚫ The handset remains registered with the same level of security as before applying the tool
⚫ In case of authentication/ciphering level, the UAK is not computed again.
⚫ The handset and the PBX continue using the UAK calculated at initial registration
⚫ Keys are never exchanged over the air

◼Restrictions
⚫ Handset that are not under radio coverage of their installation node cannot be updated
 Handsets off when the command is launched
 Handsets connected to a visited node in case of OXE DECT networking
 DECT handset automatic re-registration

New PARI as close as possible of the existing ones

RPN Use the option “- update”

PARI =10000412340

PLI = 29
• PARI and PLI are compatible with the existing system,
• the handset moves to new PARI immediately after
Auto re-registration
PLI = 29
RPN
PARI =10000412350
OXE Exemple for the DECT user 31000:
csa(1)>dectinston –update 31000 –pari 10000412350 –pli 29
DECT handset automatic re-registration

When we can’t have a new PARI as close as possible of the existing one, we need to change it
For an installation where PARI needs to be changed,
automatic re-registration must be done before changing the system PARI.
The handsets must be still reachable while launching the procedure . Use the option « - forceUpdate »

• the handsets are no longer able to communicate with the

RPN system, as soon as they receive their new configuration
DECT • The system configuration must be changed only once the
PLI = 31 PLI = 31 maximum of handsets have been registered.
• Handsets for whom the procedure has failed will need
manual reinstallation
OXE PARI =10000412344

Exemple for the DECT user 31000:

PARI needs csa(1)>dectinston –forceUpdate 31000 –pari 10000476540 –pli 29
to be changed

RPN RPN
DECT DECT
PLI = 29 PLI = 29 PLI = 29

OXE PARI =10000476540 PARI =10000476550

DECT handset automatic re-registration

Affects a new PARI and PLI (1)csa> dectinston -update 31016 -pari 10000410114 -pli 30
to the DECT handset Mon May 13 17:02:09 CEST 2019

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reinstallation process starts for Dir Num 31016

_______________________________________________________
Directory Number : 31016
User's name : DECT 2 Handset
MAO type : GAP+

Dect parameters used.

- pari <octal> affects an other PARI than the system one

PARI : 10000410114
- pli <decimal> affects an other PLI than the system one PLI : 30

Auto Re-registration in progress !!!!!

_______________________________________________________

31016 re-installed successfully!!!

DECT handset automatic re-registration
(1)csa> dectinston -update -f DECT.txt -pari 10000410114 -pli 30

Affects a new PARI and PLI Mon May 13 16:45:55 CEST 2019
================DECT handsets re-installed one by one===============
to a list of DECT handset
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Reinstallation process starts for Dir Num 31017
_______________________________________________________
Directory Number : 31017
User's name : DECT 3 Handset
MAO type : GAP

Dect parameters used.

PARI : 10000410114
PLI : 30

The file contains a list of directory numbers Auto Re-registration in progress !!!!!
which has to be installed with new PARI and _____________________________________________________
PLI.
Note :A line beginning with “#”followed by a 31017 re-installed successfully!!!
space delimiter is considered as a comment ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
and is not taken into account NOTE : Two Output files are generated in the same path as Input file
ReinstallSuccessHandsetsList.txt - Contains list of handsets for which Auto re-
registration has been successful
ReinstallNOKHandsetsList.txt - Contains list of handsets for which Auto re-registration
has failed
========================Process Completed!!=========================
DECT handset automatic re-registration

Check the result files

❖ Auto re-registration has been successful
❖ Result file location:
(1)csa> more ReinstallSuccessHandsetsList.txt
Two Output files are generated in the path same as Input file
#-------------------------------------------------------------------------------
(1)csa> pwd ----------
/tmpd # Wed Apr 17 14:22:50 2019
(1)csa> ll Reins*
-rw-rw-r--. 1 mtcl tel 271 May 13 16:45 ReinstallNOKHandsetsList.txt # dectinston -update -f DECT.txt -pari 10000400014 -pli 29
-rw-rw-r--. 1 mtcl tel 825 May 13 16:45 ReinstallSuccessHandsetsList.txt #-------------------------------------------------------------------------------

#-------------------------------------------------------------------------------
# Wed Apr 17 14:31:48 2019

❖ Auto re-registration has failed # dectinston -update -f DECT.txt -pari 10000400014 -pli 29
#-------------------------------------------------------------------------------
31016
(1)csa> more ReinstallNOKHandsetsList.txt
#-------------------------------------------------------------------------------
# Mon May 13 16:45:55 2019
#-----------------------------------------------------------------------
# Mon May 13 16:45:55 2019
# dectinston -update -f DECT.txt -pari 10000410114 -pli 30
#-------------------------------------------------------------------------------
# dectinston -update -f DECT.txt -pari 10000410114 -pli 30
31017
#------------------------------------------------------------------------
OpenTouch Suite for MLE
OmniPCX Enterprise Communication Server

DECT handset automatic re-registration

How to
✓ Re-register automatically DECT handsets

Contents
1 Configuration of PARI and PLI ............................................................... 2
1.1. Configuration........................................................................................ 2
2 Automatic re-registration of a user......................................................... 2
2.1. Start the re-registration of the DECT user 31015 .............................................. 2
3 Automatic re-registration of a list of users ................................................ 3
3.1. Create the text file ................................................................................ 3
3.2. Start the re-registration of the DECT ............................................................ 3
3.1. Consult the result files ............................................................................ 4
3.1.1. List of users that succeed to re-register ................................................................ 4
3.1.1. List of users that didn't succeed to re-register ......................................................... 4
 2
DECT handset automatic re-registration

Implementation

1 Configuration of PARI and PLI

For the roaming between the two PARI is possible, the PLI was managed at 30.
Automatically re-register DECT users with new PARI xBS and the new PLI value
The “-update” option will be used.

1.1. Configuration

PARI IBS : 100004101x0 PARI xBS :

100004101x4

RPN 0 RPN 1
RPN 0

PLI = 30

2 Automatic re-registration of a user

Start the re-registration of the DECT 31015 stations with the new xBS PARI and the new
system PLI

2.1. Start the re-registration of the DECT user 31015

Sous mtcl
Start the re-registration (1)csa> dectinston -update 31015 -pari 10000410114 -pli 30
procedure with:
The directory number of the Mon May 13 17:02:09 CEST 2019
DECT user ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The PARI xBS via the option -p Reinstallation process starts for Dir Num 31015
The PLI via the option -pli _______________________________________________________
Directory Number : 31015
User's name : DECT 2 Handset
MAO type : GAP+
Dect parameters used.
PARI : 10000410114
PLI : 30
Auto Re-registration in progress !!!!!
_______________________________________________________
31015 re-installed successfully!!!
 3
DECT handset automatic re-registration

3 Automatic re-registration of a list of users

Create a text file containing a list of DECT users (31017 and 31017) to re-register
Start the re-registration of DECT stations with the new xBS PARI and the new system PLI.

3.1. Create the text file

Open Notepad++
Create a file un
f« DECT.txt « containing the
directory numbers 31016 et
31017

Then transfer the file via FTP

to the OXE directory: /tmpd

3.2. Start the re-registration of the DECT

Under mtcl
Move to the directory: (1)csa> cd /tmpd
/tmpd
Start the re-registration (1)csa> dectinston -update -f DECT.txt -pari 10000410114 -pli 30
procedure with: Mon May 13 16:45:55 CEST 2019
The text file containing the ================DECT handsets re-installed one by one===============
directory numbers via the ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
option -f Reinstallation process starts for Dir Num 31017
The PARI xBS via the option -p _______________________________________________________
The PLI via the option -pli Directory Number : 31017
User's name : DECT 3 Handset
MAO type : GAP
Dect parameters used.
PARI : 10000410114
PLI : 30
Auto Re-registration in progress !!!!!
_______________________________________________________
31017 re-installed successfully!!!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
NOTE : Two Output files are generated in the same path as Input file
ReinstallSuccessHandsetsList.txt - Contains list of handsets for
which Auto re-registration has been successful
ReinstallNOKHandsetsList.txt - Contains list of handsets for which
Auto re-registration has failed
========================Process Completed!!=========================
 4
DECT handset automatic re-registration

3.1. Consult the result files

3.1.1. List of users that succeed to re-register

under mtcl
(1)csa> more ReinstallSuccessHandsetsList.txt

#-------------------------------------------------------------------------
# Wed Apr 17 14:22:50 2019

# dectinston -update -f DECT.txt -pari 10000400014 -pli 29

#-------------------------------------------------------------------------
#-------------------------------------------------------------------------
# Wed Apr 17 14:31:48 2019

# dectinston -update -f DECT.txt -pari 10000400014 -pli 29

#-------------------------------------------------------------------------
31016

#-------------------------------------------------------------------------

# Mon May 13 16:45:55 2019

# dectinston -update -f DECT.txt -pari 10000410114 -pli 30

#------------------------------------------------------------------------
31017

3.1.1. List of users that didn't succeed to re-register

Under mtcl
(1)csa> more ReinstallNOKHandsetsList.txt

#------------------------------------------------------------------------
# Mon May 13 16:45:55 2019

# dectinston -update -f DECT.txt -pari 10000410114 -pli 30

#------------------------------------------------------------------------
----------
OpenTouch Suite for MLE
OmniPCX Enterprise Communication Server

8378 DECT IP-xBS - External synchronization link

How to
✓ Manage the external handover on a mixed DECT configuration (TDM et xBS)

Contents
1 Configuration of a Mixed DECT infrastructure ............................................ 2
1.1. Topology ............................................................................................. 2
1.2. Mixed Base stations ................................................................................ 2
1.2.1. Check the radio base type ................................................................................ 2
1.3. PARI management .................................................................................. 3
1.3.1. Check the xBS PARI......................................................................................... 3
1.3.2. Check the IBS PARI ......................................................................................... 3
1.4. xBS site management .............................................................................. 3
1.4.1. Check the site............................................................................................... 3
1.5. Check the value of the PLI ........................................................................ 3
2 Management of the external synchronization link ....................................... 4
2.1. Allow the « External Handover » ................................................................. 4
2.2. Create an external synchronization link ........................................................ 4
3 Test the external synchronization link ..................................................... 5
3.1. Check the DECT synchronization ................................................................. 5
3.2. Estimate the « handover » area .................................................................. 6
3.3. Looking for the established communication .................................................... 7
3.3.1. On the IBS base station .................................................................................... 7
3.3.1. On the xBS base station ................................................................................... 7
 2
8378 DECT IP-xBS - External synchronization link

Implementation

1 Configuration of a Mixed DECT infrastructure

Setup the external handover on a mixed DECT infrastructure (IBS et xBS).

1.1. Topology

PARI IBS : 10000410110 PARI 1 (xBS)

External Synchronisation RPN Sync Master 15 mètres

External synchronisation
link

RPN 0 RPN 1
RPN 0

RSSI > 70 dB
Handover area
Check the radio coverage
RSSI < 70 dB
(handset in survey mode)

1.2. Mixed Base stations

1.2.1. Check the radio base type

PWT / DECT System

Radio base type Mixed
Station base type DECT Europe
 3
8378 DECT IP-xBS - External synchronization link

1.3. PARI management

1.3.1. Check the xBS PARI

PWT/DECT System / xBS System / xBS Pari

PARI Number 0
PARI Value 100004100x4 < this is an example of PARI >
Area type 1 area of 256 xBS

1.3.2. Check the IBS PARI

PWT/DECT System / IBS System

PARI Value 100004101x0
Area type 1 area of 256 xBS

1.4. xBS site management

1.4.1. Check the site

PWT/DECT System / xBS System / xBS Site

Site Number 0
Site Name BREST
Station Base Type DECT Europe

Notes
By default, the site 0 is created

1.5. Check the value of the PLI

PWT/DECT System
PLI for CTM 30

Notes
In multi PARI or in mixed mode, the PLI must be adapted
 4
8378 DECT IP-xBS - External synchronization link

2 Management of the external synchronization link

Allow the external handover.
Add an external synchronization link between the IBS PARI and the xBS PARI 0.

2.1. Allow the « External Handover »

PWT / DECT System
Flag External Handover yes

2.2. Create an external synchronization link

PWT / DECT System / xBS system / xBS Site / External Synchronization
PARI Number 0
Sync Master RPN 0 (RPN of the xBS base station that we want to use as Sync Master)
Sync Master backup RPN 255
External Synchronization 10000410110
PARI
External Synchronization 0 (RPN of the TDM base station from which one the Master Sync base station of the PARI xBS
RPN will retrieve the synchronization)

Notes
PARI Number: xBS PARI number we want to synchronize from the TDM system.
Sync Master RPN: RPN number of the xBS base station that will be the “Master Sync”.
Sync Master Backup: RPN of the base station that will be the Sync Master backup. It becomes the Master Sync
base station in case of failure.
External Synchronization PARI: Provide the PARI TDM (IBS or RBS) from which one the xBS PARI will retrieve
the synchronization.
External Synchronization RPN: RPN of the TDM base station from which one the Master Sync base station of
the PARI xBS will retrieve the synchronization.
 5
8378 DECT IP-xBS - External synchronization link

3 Test the external synchronization link

Position the base stations as shown in the topology diagram.
Using the DECT handset in "Survey mode", estimate the "handover" area between the IBS
and xBS base stations.
Make a call from a DECT handset:
- Check if we are using a time slot on the IBS base station: Command dectview com.
- Maintain the communication and move to the xBS base station to do an “handover”.
- Check if we are using a time slot on the xBS (RPN1) with the command dectview
com.

3.1. Check the DECT synchronization

under mtcl
Command (1)csa> dectview xbs

Wed May 18 11:13:36 CEST 2022

================= DECT RESOURCES BUSY STATE ===============

Resource Max busy free percent busy

-----------------------------------------------------
Link 276 0 276 0.00
LCEI 300 0 300 0.00
ADPCM 0 0 0
Buffer UA-> 135 0 135 0.00

**** XBS registration NODE 1 (my local node is 1) ****

+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+-
-+
|Virtual @|XBS Site PARI-Area-RPN| Neqt|State |Location| IP @ | Mac @ |FW
Version|Clusters|NR|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+-
-+
| 1/00/056|000 0 BREST 0- 0- 0| 901|OK PM*|GF-01 |192.168.1.149 |00:08:7b:16:50:e6|0073B0003 |00000001|
0|
| 1/00/057|001 0 BREST 0- 0- 1| 902|OK |FL-01 |192.168.1.150 |00:08:7b:16:4c:f9|0073B0003 |00000001|
0|
+---------+------------------------------+-----+------+--------+---------------+-----------------+----------+--------+-
-+
NR = Number of Radio links established
NOK = out of service
OOS = outserv used; use inserv to put in service again
P = data sync Primary xbs (the one which collects data)
M = Master configured (for DECT synchronization)
B = Backup configured (for DECT synchronization)
+ = Master free running of DECT synchronization (not available in st-by CPU)
* = Master locked of DECT synchronization (not available in st-by CPU)

Region 0 (EUROPE) has 1 site(s) with 2 XBS in service.

+-----------------------+-------------------------------------------+
| External sync source | Local Site/PARI |
| IBS-10000410120 | 0 BREST - PARI 0-10000410124 |
+-----------------------+-------------------+-----------------------+
| External sync source | Master/Backup | Highway Sync |
| RPN location | RPN - location | |
+-----------------------+-------------------+-----------------------+
| S 0-IBS xxxx ----> *M 0-GF-01 | |
| | B 255-XBS xxxx | |
+-----------------------+-------------------+-----------------------+
 6
8378 DECT IP-xBS - External synchronization link

3.2. Estimate the « handover » area

On the DECT handset in Survey mode
Switch on the Survey mode
The IBS base station is on the
top of the list because it has
the best gain (-28 dBm)

Move to the xBS base station

with the RPN 01

When she goes first in the list

(best gain), you will be in the
Handover area.
 7
8378 DECT IP-xBS - External synchronization link

3.3. Looking for the established communication

3.3.1. On the IBS base station

Attention
THE CALL MUST BE ESTABLISH ON THE IBS BASE STATION

Under mtcl
Command dectview com
(1)csa> dectview com

Tue Apr 30 15:55:27 CEST 2019

================= DECT RESOURCES BUSY STATE ===============

Resource Max busy free percent busy

-----------------------------------------------------
Link 276 1 275 0.36
LCEI 300 1 299 0.33
ADPCM 0 1 -1
Buffer UA-> 135 0 135 0.00

====== There are 1 Communication(s) running ========

Link/State : 040/STABLE CC/MM/FWU/SECU :1/0/0/1 DLEI/BS: 65/1 MAC: 12/01/020 LCEI: 001 ADPCM:
255/255/255 Num:31016

====== Elastiques (External Handover in ABC) ========

On the DECT handset in Survey mode

Communication established on
the IBS base station RPN 0

3.3.1. On the xBS base station

Attention
MOVE TO HAVE A HANDOVER WITH THE XBS BASE STATION AND CHECK THAT THE COMMUNICATION IS WELL
ESTABLISHED
 8
8378 DECT IP-xBS - External synchronization link

Under mtcl
Command dectview com
(1)csa> dectview com

Tue Apr 30 15:53:14 CEST 2019

================= DECT RESOURCES BUSY STATE ===============

Resource Max busy free percent busy

-----------------------------------------------------
Link 276 1 275 0.36
LCEI 300 1 299 0.33
ADPCM 0 1 -1
Buffer UA-> 135 0 135 0.00

====== There are 1 Communication(s) running ========

Link/State : 039/STABLE CC/MM/FWU/SECU :1/0/0/1 RELAY : 1/0/55 PORT 32522 RADIO = 1/0/55 Num:31016

====== Elastiques (External Handover in ABC) ========

On the DECT handset in Survey mode

Communication established on
the IBS base station RPN 1
OpenTouch Suite for MLE
OmniPCX Enterprise
Twin-Set
Principle

◼Logical association between a desktop (main) set and a Cordless (secondary) set

⚫ The directory number of the tandem is the directory number of the desktop set main line

Tandem
31000
◼Sets characteristics

⚫ The main set must be a desktop (wired set)

⚫ The second set can be another desktop

⚫ Both sets must be multiline(1) Main Secondary

31000 31015
⚫ Both sets must belong to the same node
Call handling

◼Main set
31000

31000

31000 31015
◼Secondary set

31000

31015

31000 31015
Call handling

◼The both sets ring if a call is presented on the main line or the secondary lines of the main set (desktop)

◼When one of the sets takes the call, the other stops ringing

◼Both sets can answer to the call

◼The tandem is busy when all the lines of the main set are busy

◼The secondary set is busy when all its lines are busy
When one of these lines becomes free again a waiting call of the main set is presented on it
Busy state

◼By default, the status of the tandem reflects the occupation status of the main set

⚫ If the main set busy, the tandem is considered as busy

 The set is busy when all the lines are busy

◼The tandem can be seen as busy as soon as one of the sets of the tandem is busy

⚫ If the main set or the secondary set is busy, the tandem is considered as busy

 The set is busy when all the lines are busy

◼The parameter “Partial busy” has to be modified to change the behavior

Service level

◼Same service level for the both sets

◼Facilities can be set up from the main or the secondary sets

31000

FACILITIES

Duplication of the
configuration

31000 31015
Specific feature

◼Transfer between the both sets of the tandem

⚫ From the cordless set:

 Press ok to put the call in hold

 Off hook the desktop set to pick-up the call

⚫ From the desktop set:

 Dial the “park call” prefix, enter the directory number of the twin-set configuration (main set number), the call is parked

 Go to the secondary set and press “Off hook” key

◼Enable/ Disable one set ringing

⚫ Suppress the ringing of the selected set

 Done by prefix
Call on private line

◼Same behavior than if you call the main lines

The caller dials the number 31333 (Private Nb)

31000

31333 The two sets are rung

31000 31015
Tandem supervision

◼Tandem supervision is done on the tandem main directory number

◼The supervision key takes in order the tandem main and secondary sets status

⚫ Free - No set busy

⚫ Partially busy - One line at least is busy on one of the both set and one line is free on the main set

⚫ Totally busy - All the lines of the main set are busy

⚫ Ringing - Tandem is ringing

Call handling - Executive / Secretary configuration

◼The tandem secondary set doesn’t have the filtering keys (screening, unscreening, executive call,...), but
only the line keys

◼The secondary set can make an executive call even if this one is in filtering

◼Features not implemented on the secondary secretary set

⚫ Executive mail

⚫ Executive forward from the secretary

⚫ Listen-in
Call handling - Executive / Secretary configuration

◼Screening / unscreening

I/C Filtering

Manager
Secretary
Different ringing
manageable
◼Secretary call / Manager call

Secretary call

Manager
Secretary
OpenTouch Suite for MLE
OmniPCX Enterprise Communication Server

Twin-set configuration

How to
✓ Manage a twin-set configuration

Contents
1 Twin-set declaration .......................................................................... 2
1.1. Multi-line configuration............................................................................ 2
1.2. Tandem creation ................................................................................... 3
 2
Twin-set configuration

Implementation

1 Twin-set declaration
A tandem (twinset) is configured between 2 devices: A main desktop phone and the DECT handset for
example.

1.1. Multi-line configuration

To configure a tandem, the desktop phone and DECT handset, both must be multi-line devices.
At least two lines have so to be configured on both devices.

Configure the main set (e.g. 31010) and the DECT handset (e.g. 31015) as multi-lines
devices:
- Configure 2 lines on each device with the directory number of the device

Users/Prog. Keys

Select the concerned device.

Example: 31001

Select a free key

Function Multi-line
Directory Number Directory number of the key (for the first one, it must be the same as device number)
 3
Twin-set configuration

1.2. Tandem creation

Configure the association between the main and secondary devices

Users
Select the main desktop
phone of the user

(e.g.: 31001)

And “Assoc. Sets” section

Specify the directory number

of the secondary device

Tandem Directory Number Directory number of the secondary device (DECT). Example : 31015
Main set in the tandem Checked

Tips
You can edit the settings of the secondary device (DECT) to verify that the “reverse” configuration is
automatically done:
- Tandem directory number = main set directory number
- Main set in the tandem: Yes
OpenTouch Suite for MLE
OmniPCX Enterprise
IP-xBS Native Encryption
IP-xBS Native Encryption
Architecture

8378 DECT IP-xBS solution supports the Native Encryption

OXE (HA)

EGW
Softswitch

OTSBC IP-xBS
(« CPE » SBC) SIP TLS
NOE-DTLS
SRTP

NOE-DTLS
NOE-DTLS
Carrier Network
IP Link-DTLS
VPN Server
NOE-DTLS

The UA/xBS message will be

encrypted in a DTLS session.

Secured RTP will be applied for

media communication
Remote Worker IP Media gateway NOE 3GEE Phone NOE 3GEE Phone
the master key will be delivered in
UA/xBS message (SRTP)
IP-xBS Native Encryption
Configuration

xBS system parameter

•Enabled for all the base stations (No partial

encryption )

Certificate-based authentication
(SHA2)
• CTL acquisition
•Trust On First Use mode (TOFU)
• manual import via 8378 AP’s WBM
•Mutual authentication supported
•Default (based on ALE CA) or customer
certificate
•Issued to the base station’s MAC address
•Import of custom certificate via the base’s
WBM
•SCEP protocol not supported

Note:
DTLS encryptions cipher suites
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 media encryption (SRTP)
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 AES_CM_128_HMAC_SHA1_80
IP-xBS Native Encryption
Initialization
◼Endpoints learn about various DTLS parameters (including support of DTLS) through lanpbx.cfg file
OXE
DTLS capable
Endpoint IP-xBS

TFTP (“lanpbx.cfg” Read Request/Response)

(File integrity checked using the signature)
(DTLS parameters retrieval)

Binaries download

DTLS Handshake
(CS certificate verification)
Clear (Client certificate verification; if mTLS)
(“startxxx-DTLS-MAC@” file request/ack.)
Encrypted
Application level DL establishment (Connect/Ack.)
(NOE signaling message exchange over DTLS)
 IP-xBS Native Encryption
First start-up

OXE

IP-xBS Flash memory

DTLS_ENCRYPTION = False
xBS Native encryption = True

Startup
inconsistency UA link is established In Clear mode
between the encryption state
and the Native encryption setting

UA message : set_param_req = DTLS Flash memory

DTLS_ENCRYPTION = True

Reboot

DTLS link is established

 IP-xBS Native Encryption
Disable the xBS Native encryption

OXE

IP-xBS Flash memory

DTLS_ENCRYPTION = True
xBS Native encryption = True

Startup
inconsistency DTLS link is established In DTLS mode
between the encryption state
and the Native encryption setting Flash memory
UA message : set_param_req = NO-DTLS
DTLS_ENCRYPTION = False

Reboot
UA link is established

Note:
In case the CS changes the encryption level to clear while a xBS is not connected to the network, this xBS will have its flag DTLS_ENCRYPTION = True
and will try on next start to establish a DTLS socket on a clear CS. The socket is refused by the CS (TBC), the base will not succeed to start
and will reset infinitively. A workaround is to set again the CS in encryption mode and go back in clear when all the xBS are connected.
Another workaround could be to do a factory reset on this base (but this needs a local intervention).
IP-xBS Native Encryption
Mutual Authentication: Alcatel-Lucent digital certificates

OXE CTL content after software loading

11.11.3.Endpoint CTL (Trust Store)
==================================

1. 'Import Endpoint CTL'

Alcatel-Lucent uses digital The ALE factory IP-xBS These certificates are 2. 'View Endpoint CTL'
certificates that certificate is installed by issued by a PKI (Public Key
authenticate equipment default Infrastructure) 3. 'Delete Endpoint CTL'

0. 'Previous menu'

What is your choice ? 2

1 - ALE_CTL.pem
--------------------
subject=/C=FR/O=Alcatel/OU=PKI Authority/CN=Alcatel Enterprise Solutions
notBefore=Sep 28 10:03:42 2005 GMT
notAfter=Sep 28 10:11:08 2055 GMT

subject=/C=FR/O=Alcatel/OU=PKI Authority/CN=Alcatel IP Touch

notBefore=Sep 28 10:02:47 2005 GMT
notAfter=Sep 28 08:22:04 2025 GMT

subject=/C=FR/O=Alcatel/OU=PKI Authority/CN=AIPT 1
notBefore=Sep 29 12:09:33 2005 GMT
notAfter=Sep 28 08:22:04 2025 GMT

subject=/C=FR/O=Alcatel/OU=PKI Authority/CN=AIPT 2
notBefore=Sep 29 12:13:19 2005 GMT
notAfter=Sep 28 08:22:04 2025 GMT

subject=/C=FR/O=Alcatel/OU=PKI Authority/CN=AIPT 3
notBefore=Sep 29 12:13:19 2005 GMT
notAfter=Sep 28 08:22:04 2025 GMT

subject=/C=FR/O=Alcatel/OU=PKI Authority/CN=AIPT 4
notBefore=Sep 29 12:13:19 2005 GMT
notAfter=Sep 28 08:22:04 2025 GMT
Wired Phone subject=/C=FR/O=Alcatel-Lucent/OU=PKI Authority/CN=Wired Phones
Autority certificate notBefore=Jan 28 11:20:34 2010 GMT
notAfter=Jan 28 11:30:34 2040 GMT

subject=/C=FR/O=Alcatel-Lucent/OU=PKI Authority/CN=Enterprise Wireless Terminals

notBefore=Jan 28 11:18:30 2010 GMT
notAfter=Jan 28 11:28:30 2040 GMT

Note: the CN (common name) is the MAC @ of the base station

IP-xBS Native Encryption
Mutual Authentication: Customer digital certificates

OXE CTL content

11.11.3.Endpoint CTL (Trust Store)
==================================

Certificates that 1. 'Import Endpoint CTL'

These certificates are
authenticate IP-xBS This certificates must be 2. 'View Endpoint CTL'
issued by a PKI (Public Key
equipment must be upload in each base station
Infrastructure) 3. 'Delete Endpoint CTL'
generated 0. 'Previous menu'

What is your choice ? 2

1 - ALE_CTL.pem
--------------------
subject=/C=FR/O=Alcatel/OU=PKI Authority/CN=Alcatel Enterprise Solutions
notBefore=Sep 28 10:03:42 2005 GMT
notAfter=Sep 28 10:11:08 2055 GMT

subject=/C=FR/O=Alcatel/OU=PKI Authority/CN=Alcatel IP Touch

notBefore=Sep 28 10:02:47 2005 GMT
notAfter=Sep 28 08:22:04 2025 GMT

|
|
|
|
|
subject=/C=FR/O=Alcatel-Lucent/OU=PKI Authority/CN=Enterprise Wireless Terminals
notBefore=Jan 28 11:18:30 2010 GMT
notAfter=Jan 28 11:28:30 2040 GMT

2 - RootCA.pem
--------------------
subject=/C=FR/ST=BZH/L=BREST/O=ALE/OU=IT/CN=xca/[email protected]
notBefore=Sep 1 09:08:00 2021 GMT
notAfter=Sep 1 09:08:00 2022 GMT
The trusted certificate of
the certification authority

Note: the CN (common name) is the MAC @ of the base station

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: [email protected]