100% found this document useful (2 votes)

484 views

Basico PDF

Uploaded by

Jose Luis Hortua Garcia

Available Formats

Download as PDF, TXT or read online on Scribd

100% found this document useful (2 votes)

484 views

Basico PDF

Uploaded by

Jose Luis Hortua Garcia

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 1132

Alcatel-Lucent OmniPCX Enterprise

R9.0
Starter Pack Enterprise

Part 1/3 PARTICIPANT’S GUIDE

Alcatel-Lucent Enterprise Solutions Training REF. ENTPTE900US Issue 01
This document has no contractual value and may be changed or withdrawn
at any time by Alcatel-Lucent.
This product includes software. Its use may be subject to legislation concerning computer technology,
databases and civil liberties (in case of France see the law N° 7817 dated 6 january1978).
Alcatel-Lucent OmniPCX Enterprise – Release 9.0
Post-sales Training Offer

Enterprise Solutions Training

December, 2008

All Rights Reserved © Alcatel-Lucent 2008

Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Legend

VALUE ADDED OPTIONS

To complement the basic portfolio by value added solutions or applications:

Configuration & administration of complementary features, associated solutions & applications

SOLUTION BASED

To answer to customer standard customization:

Configuration & administration of services & advanced features

STARTER PACK

For a quick start of the solution:

Install the OmniPCX Enterprise and the infrastructure and ensure the start up of the system

FUNDAMENTALS

2 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Legend

I=x h represents an optional training course, not involved in

Course Name
C=x d
Reference
V=x d certification program
I=x h
Course Name
C=x d
Reference represents training courses involved in ACSE certification
V=x d
Alcatel-Lucent Certified System Expert
I=x h
Course Name
C=x d
Reference
V=x d represents training courses involved in ACFE certification
Alcatel-Lucent Certified Field Expert
I=x h
Course Name
C=x d
Reference represents training courses involved in ACPS certification
V=x d
Alcatel-Lucent Certified Presales
I=x h
Course Name
C=x d
Reference represents training courses involved in AQPS certification
V=x d
Alcatel-Lucent Qualified Presales
I=x h
Course Name
C=x d
Reference represents training courses involved in ACSR certification
V=x d
Alcatel-Lucent Certified Sales Representative
I=x h
Course Name
C=x d
Reference represents administrators training courses
V=x d

I=x h
Course Name
C=x d
Reference represents fundamentals training courses
V=x d

I = x h stands for Individual learning, in hours

C = x d stands for Classroom learning, in days
V = x d stands for Virtual learning, in days

3 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Newcomer
BUSINESS SOLUTION BASED CORPORATE SOLUTION BASED VALUE ADDED OPTIONS
STARTER PACK Duration: I=25 h and C=28 d
Duration: I=15 h and C=20 d OmniMobility
Duration: I=8 h and C=10 d
Expert C=2 d
ACSE ACSE
ACFE OmniPCX AP00TE085
OmniPCX Enterprise OmniPCX Enterprise
Enterprise R9
Business R9 Corporate R9
ENTPC2C8 ENTPTC0C13 ENTPTC0C12 OmniMessage OmniMessage
30 MCQ: 45 min 60 MCQ: 1 h / lab: 2.5 h 60 MCQ: 1 h / lab: 2.5 h 4635 Advanced C=3 d 4635 Expert C=5 d
4635TE310 4635TE312

Users Profiles I=2h On Site Mobility DECT C=2d Hotel

ENTPWB901 ENTPTE910 Voice Services
C=2 d /healthcare C=3 d
ENTPTE906
ENTPTE909

On Site Mobility
CPU loading & Off Site Mobility
Starter Pack Enterprise I=8h I=1h Security Access I=4h I=2 h VoWLAN C=2 d
Architecture ENTPWB907
ENTPTE900 C = 10 d C=5d ENTPTE912 C=1d ENTPTE913
ENTPTE903

External Free Desktop

I=1 h
Services C=2 d Mobility C=2 d
ENTPTE908 ENTPTE911
VoIP Advanced & I=6h I=6h
Multi Site Network
Backup C=5d C=5d
ENTPTE902 Tap Lab OmniPCX
ENTPTE904 C=2 d IP Touch Security
Enterprise I=12 h
or Solution
ENTPTA0A9 or C=3 d
C=3d ENTPTE905
ENTPTA0A10

VoIP Technologies I=8h

FUNDAMENTALS
FG00WB065

Technology Overview Technology Overview Technology Overview Technology Overview

Basic Telephony
C=2d Series: IP Overview I = 60 min Series: LAN I = 30 min Series: WAN I = 15 min Series: WLAN I = 24 min
FG00TE082
TGK30001W TBU30052W 3EY0SA065 3EY0SA064

4 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Curricula R8.x vs R9(1/2)
Release 8.x Release 9
+ 802.1x TLS
+ MG hardening
Security access Security access
+ IP ABC TG
Multi-Site Network Multi-Site Network

On Site Mobility DECT On Site Mobility DECT

ACSE Corporate
Removed: Content divided into all modules
Troubleshooting

Removed from Alcatel-Lucent OmniPCX Enterprise offer

CCD Starter
I=6h C=5d + IP R9 News (T38 fax, VoIP
VoIP Advanced CDR, SIP…)
VoIP Advanced & Backup + Public SIP trunk groups
CPU loading & Redund. I=1h C=5d (existing)
+ CLI
CPU loading & Architecture

ACSE Business
Multi-Site Single Node + multi timezone

+ new hardware
Users Profiles + Ring tones Users Profiles
- Public SIP trunk groups
Starter Pack Enterprise Starter Pack Enterprise

ACFE
5 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Curricula R8.x vs R9 (2/2)

Release 8.x Release 9

Tap Lab OmniPCX Enterprise Tap Lab OmniPCX Enterprise

OmniMobility Expert OmniMobility Expert

OmniMessage 4635 Expert OmniMessage 4635 Expert

OmniMessage 4635 Advanced OmniMessage 4635 Advanced

Hotel / Healthcare Hotel / Healthcare

+ PIN code enhancement, transfer of private call
External Services External Services

OPTIONS
Voice Services Voice Services
+ remote extension deactivation
Off Site Mobility Off Site Mobility
+ evolutions
On Site Mobility VoWLAN On Site Mobility VoWLAN
+ evolutions
Free desktop mobility Free desktop mobility
+ MG signaling encryption
IP touch Security Solution IP touch Security Solution

6 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Fundamentals

FUNDAMENTALS
Basic Telephony VoIP Technologies
basic principles of telephony Voice & data switching techniques
Basic Telephony VoIP Technologies
organization of a telephonic network C=2d I=8h Quality of Service on IP (QOS)
FG00TE082 FG00WB065
protocols used in telephony INTSERV, DIFFSERV
principle et composition of PCXs MPLS model
telephone features H323 ( ITU) , SIP , MGCP protocols
concept, characteristics et features of
the ISDN
basic concepts of Voice over IP

Technology Overview Series: IP Technology Overview Series: LAN

Overview Technology Overview Technology Overview The LAN webcast is presented by
The IP webcast is presented by Series: IP Overview I = 60 min Series: LAN I = 30 min industry analyst et educator Steve
industry analyst et educator Steve TGK30001W TBU30052W Shepard. It provides essential
Shepard. It provides essential background on key LAN technologies
background on key IP technologies et their use in today's Enterprise
et their use in today's Enterprise

Technology Overview Series

Technology Overview Series: WLAN
WAN Technology Overview Technology Overview The WLAN webcast is presented by
•Learn about Wide Area Networks Series: WAN I = 15 min Series: WLAN I = 24 min industry analyst et educator Steve
including what they are et what
3EY0SA065 3EY0SA064 Shepard. It provides essential
they are used for. The course
background on key WLAN technologies
also covers the fundamental
et their use in today's Enterprise
infrastructure et different
options for WAN transport.

7 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Newcomer

STARTER PACK
Duration: I=8 h and C=10 d

Starter Pack Enterprise User Profiles

Global overview Profiles description
Management tools Starter Pack Enterprise I=8h Users Profiles Description where to find the right
I=2h
Users management, multi line ENTPTE900 C = 10 d ENTPWB901 training for each profile
DECT users with IBS …
IP Phones (static & dynamic)
Internal DHCP
Tel features, prefixes & suffixes, COS
Speed dial numbers
Operators, Entities
Voice guide, MoH
4645 voice mail
External features: TG, DID, Translator
External COS
ARS
RMA features & alarms
Backup & restore
OPS
Traces...

8 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Newcomer

SOLUTION BASED OPTIONS

for Corporate & Business
CPU Loading & Architecture VoIP Advanced & Backup
Version loading CPU loading & I=1h VoIP Advanced & I=6h • SIP users / SIP gateway
multi partition Architecture C=5d Backup C=5d • SIP trunk groups
patch loading ENTPTE903 ENTPTE904 Centralized DHCP
CPU redundancy Gatekeeper
Spatial redundancy IP Domains (CAC, QOS)
Remote shelves VLAN
Multi translator IP specifics
Multi Entity Passive Call Server
IP Domains (multisite) IP MG, signaling Backup
Multi timezone Hybrid MG
CLI for urgent calls IP Phones survivability

9 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Newcomer

SOLUTION BASED OPTIONS for Corporate

VALUE ADDED OPTIONS for Business

Multi Site Networking

ABC Links
ABC Trunk Groups Multi Site Network I=6h
Hybrid links ENTPTE902 C=5d
Full IP Link
Services (Audit Broadcast)
Centralized Service

10 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Newcomer

VALUE ADDED OPTIONS

for Corporate & Business (1/2)
Voice Services Free desktop mobility
Voice Services Free Desktop Mobility I=1 h Free Desktop
4645 advanced features C=2d
ENTPTE906 ENTPTE911 C=2 d IP Touch Door cam
N party conference
… …

External services Off Site mobility

Advanced Multi translator External Services Off Site Mobility DISA
C=2d I=2h
Multi Entity ENTPTE908 ENTPWB907 Ubiquity
Business & personal calls Cellular extension
ARS with DCT / Time based RL My Pocket Communicator
…
Tap Lab OmniPCX Enterprise On Site mobility VoWLAN
The participant selects himself the Tap Lab OmniPCX WLAN architecture overview
C=3d On Site Mobility VoWLAN C=2d
subjects and topics he wants to cover Enterprise Spectralink overview
ENTPTE913
A technical and pedagogic assistance ENTPTA0A9 WLAN management
is provided by a trainer WLAN extensions
Examples of subjects that can be …
covered:
Voice over IP and IP-Phones IPTouch Security Solution
Tap Lab OmniPCX IP Touch Security I=12 h
Networking,VPN overflow C=2d VoIP Encryption
Enterprise Solution C=3 d
Hybrid links MGSec
ENTPTA0A10 ENTPTE905
Call server duplication …
Spatial redundancy
Other

11 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Newcomer

ASSOCIATED APPLICATIONS
Hotel/Healthcare
Duration: C=3 d

ACFE
Hotel / Healthcare
4400TC2C3
30 MCQ: 45 min

Hotel / Healthcare
Room management
Hotel /health care C=3d Accounting
ENTPTE909 Hotel services
AHL
Suites
…

12 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Newcomer

ASSOCIATED APPLICATIONS
OmniMobility DECT
Duration: C=2 d

ACSE OmniMobility
DECT
AP00TC0C0
40 MCQ: 45 Min / lab: 2.5 h

OmniMobility Tap Lab

OmniMobility TAP-Lab C=1d The participant selects himself the
AP00TA0A0 subjects and topics he wants to cover
A technical and pedagogic assistance is
provided by a trainer

Mobility Expert
OmniMobility Expert C=2d Tools for radio coverage test
AP00TE085 DECT Engineering rules
Radio coverage survey

13 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Newcomer

ASSOCIATED APPLICATIONS
OmniMobility DECT
Duration: C=2 d

ACSE OmniMessage
4635 R5.x

4635TC0C1
40 MCQ: 45 Min / lab: 2.5 h

OmniMessage 4635 Tap Lab

OmniMessage 4635
TAP-Lab C=1d The participant selects himself the
4635TA0A1 subjects and topics he wants to cover
A technical and pedagogic assistance is
provided by a trainer

OmniMessage 4635 OmniMessage 4635 Expert

Expert C=5d System parameters
4635TE312
FAX Server
Automated attendant
OPS, Incidents, Traffic analysis

OmniMessage 4635 OmniMessage 4635 Advanced

Advanced C=3d •Software loading
4635TE310
•Mailbox OmniPCX Enterprises &
languages configuration

14 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Experienced

Upgrade R8.x to R9
ACSE OmniPCX
ACSE OmniPCX
Enterprise Corporate R9
Enterprise Corporate R8.x
(On line MCQ)

Trained up to
ACSE OmniPCX Enterprise Upgrade R8.x to R9
Corporate R8.x level ACSE OmniPCX
Not yet R8.x certified Enterprise Corporate R9
(Classroom exam:QCM + LAB)

Upgrade R8.x to R9 ACSE OmniPCX

ACSE OmniPCX
Enterprise Business R8.x Enterprise Business R9
(On line MCQ)

Trained up to
ACSE OmniPCX Enterprise
Upgrade R8.x to R9 ACSE OmniPCX
Business R8.x level
Not yet R8.x certified Enterprise Business R9
(Classroom exam:QCM + LAB)

15 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Experienced

Multi-Site Network

On Site Mobility DECT ACSE OmniPCX

ACSE OmniPCX Enterprise Corporate R9
Security access
Enterprise Business R8.x (Classroom exam:
Upgrade R8.x to R9 QCM + LAB)

Multi-Site Network

On Site Mobility DECT ACSE OmniPCX

ACSE OmniPCX Enterprise Corporate R9
Enterprise Business R9 Security access (Classroom exam:
QCM + LAB)

16 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise - Release 9.0
Post-sales Experienced

Upgrade R8.x to R9
Evolution of telephony features
New hardware
Evolution of the security
802.1X EAP-TLS
GD signaling encryption Upgrade
Evolution of SIP features C=3d
R8.x to R9
NOE/SIP Dual stack for IP Touch
ENTPTE920
End point level of service increase
Multi time zone
IP ABC trunk group
Calling Line Identification per IP Domain
Fax T38 relay between IPMG

ACSE OmniPCX ACSE OmniPCX

Enterprise R9.0 Enterprise R9.0
Corporate Business
ENTPTC0C12 ENTPTC0C13
60 MCQ: 1 h / lab: 2.5 h 60 MCQ: 1 h / lab: 2.5 h

ACSE Upgrade ACSE Upgrade

Only available for OmniPCX Enterprise OmniPCX Enterprise Only available for
ACSE OmniPCX Enterprise R8.x R9.0 Corporate R9.0 Business ACSE OmniPCX Enterprise R8.x
ENTPTC0U12 ENTPTC0U13 Business certified
Corporate certified
20 MCQ: 45 Min 20 MCQ: 45 Min

17 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
www.alcatel-lucent.com

18 | Alcatel-Lucent OmniPCX Enterprise Postsales Training Offer | December 2008 All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise

REFERENCE ENTPTE900US DELIVERY LANGUAGE English (course material in English)

DURATION METHODS
8 hours Virtual self-paced training on the computer. 8 hours before c-learning

10 days Traditional classroom or practical sessions with tutorials (TAP LAB)

Tutored virtual training sessions accessible via an internet connection

MAXIMUM NUMBER OF PARTICIPANTS 12

PUBLIC
System Installers
Technicians and Engineers in charge of the configuration of an Alcatel-Lucent OmniPCX Enterprise in stand alone

OBJECTIVES
At the end of the course, the participant will be able to:
• Install and ensure the cabling of the system
• Check the correct start-up of the system (Boards, Users & Trunk groups)
• Activate the main phone services on terminals
• Configure the system in stand alone:
• Hardware
• Users
• Trunk groups
• Major Phone services
• Ensure the basic maintenance of the system
• Configure and activate a remote connection to the system via RMA solution
The « + » of this training: Using a real customer site file, the participant will learn the exact installation
(cabling, system start and stop, etc.) and will configure a new system from the beginning.
A IP Touch simulator describing the main set features will be given during the training to the students.

PREREQUISITES
• To have attended Basic Telephony (Ref.: FG00TE082US) and Network knowledge (Ref.: FG00WB535US)
training courses is strongly advised or to have equivalent knowledge
• To have knowledge of basic Computing skills (PC start and stop, IP address modification, Current use of
PC)

REQUIRED TECHNICAL CONFIGURATION

For i-learning
Access to the Business Partner Web Site. Internet Explorer version 5.5 or better, Macromedia Flash 7 and Acrobat Reader version 6 or better.
Virtual Microsoft Java Machine (MSJVM).

All Rights Reserved © 2008, Alcatel-Lucent

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise

PROGRAM DESCRIPTION

Phase 1: i-learning 8 hours

Describe Alcatel-Lucent OmniPCX Enterprise global offer

Describe Alcatel-Lucent OmniPCX Enterprise architecture
Describe the hardware architecture:
• Cabinets
• System couplers (boards)
• Terminals
Describe the system cabling
Perform the system cabling using simulation tools
Describe how to access to the system
Describe the available logins
Describe how to start and how to stop the system
Describe MGR integrated configuration tool
Describe Alcatel-Lucent Expert integrated configuration tool (Alcatel-Lucent 4760i)
Describe the range of terminals that can be connected to an Alcatel-Lucent OmniPCX Enterprise:
• Alcatel-Lucent 8 & 9 series
• Mobiles 300/400
Describe the Add-On modules that can be added to the terminals
Describe the available plugwares
Describe how to start and stop the system
Describe IP addressing plan principles
Describe how to implement an Alcatel-Lucent OmniPCX Enterprise in a customer LAN
Describe how to modify the IP addressing plan via netadmin
Describe how to create an empty database
Describe how to save and restore a database
Describe the principles of the software licenses
Describe the Bulk and Move service for licensing
Describe how to save and restore the system licenses
Describe the principles of the classes of services:
• Connection class of service
• Phone facilities class of service
• Transfer class of service
• Public network class of service
• Private calls class of service
Describe hunt groups principles
Describe call pick-up groups principles
Describe multiline sets and associated services
Describe Multi Line Appearance principles

All Rights Reserved © 2008, Alcatel-Lucent

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise

Describe attendant sets and attendant groups principles

Describe entities principles
Describe the principles of the internal calls distribution (attendant call)
Describe the principles of DECT mobility
Describe IBS DECT equipment:
• Base stations
• Terminals
Describe the internal accounting mechanisms
Describe the available remote maintenance solutions:
• e-RMA
• Crystal RMA
• RMA on common hardware
Describe the principle and how to configure :
• Display and Call by name with UTF8 characters
• Alcatel-Lucent x8 & x9 series sets customization and localization
• Automatic callback on busy trunk group facility
• Calling Line Identification service on analogue trunk groups
• Caller name display if managed in the personal directory
• Call overflow when IP extension is unreachable
• Alarm retrievals (Alarm sets, External alarms, CPU alarms and RMA alarms)
Describe the Premium Customer Support (PCS) process and the associated services
Describe the ROHS rules on Alcatel-Lucent OmniPCX Enterprise
Describe the process to contact our Professional Services et how to create a Service Request
Describe how to start and generate traces
Describe the Crashdump & Kernel Debugger
Describe the OLCA tool

All Rights Reserved © 2008, Alcatel-Lucent

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise

Phase 2: c-learning 10 days

Describe the tools and the training materials provided during the training course
Describe the customer site file
Start and stop the system
Access to the system using the available logins
Check the correct startup of the system couplers
Use MGR and Alcatel-Lucent Expert configuration tools
Create an empty database
Configure the IP addressing plan of the system
Install, save and restore the licenses
Describe and modify the internal dialing plan:
• Prefixes
• Suffixes
• Directory numbers
Configure and maintain the users
• IP Phones (in static/dynamic mode)
• Digital phones
• Plugwares and interface modules
• Add-On modules
Configure and maintain the IP parameters of the Voice over IP boards
Describe and configure the internal DHCP server
Describe and configure the ring tones customization tool
Describe and configure the MOXA V24/IP Box
Configure the classes of services:
• Connection class of service
• Phone facilities class of service
• Transfer class of service
• Public network class of service
Configure the groups:
• Hunt groups
• Call pick-up groups
Configure multiline sets and associated services (sets supervision, etc.)
Configure and maintain a MLA group
Describe and configure Executive / Assistant groups
Describe and configure trunk groups:
• ISDN T0 / T2 trunk groups
• T1 trunk group (North American market)
• Analogue trunk groups
Describe and manage the system synchronization
Describe and modify the default DID translator
Describe and configure the external callback translator
Describe and configure the outgoing external calls barring

All Rights Reserved © 2008, Alcatel-Lucent

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise

Describe, configure and maintain a simple Automatic Route Selection configuration (direct carrier, no time
dependence)
Describe, configure and maintain the calls distribution:
• Attendant groups
• Attendant sets
• Entity
• Calls distribution tables
Describe, configure and maintain an IBS DECT solution:
• IBS base station configuration
• DECT users creation and registration
Display and describe the fields of the system messages
Describe, configure and maintain the direct speed dialing and the speed dialing by range
Describe, configure and maintain an Alcatel-Lucent OmniMessage 4645 voicemail system:
• Voicemail creation
• Mailboxes allocation
• Voicemail classes of services configuration
Describe and configure the internal accounting parameters
Save and restore the system database
Describe, configure and maintain a RMA solution
Describe, configure and maintain the voice guides
Describe, configure and maintain the music on hold

All Rights Reserved © 2008, Alcatel-Lucent

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
toc.doc

DOCUMENT CHANGES

Issue Date Issue Date

Alcatel-Lucent OmniPCX Enterprise R9.0 Starter Pack Enterprise 01 12/08

File reference: ENTPTE900US

GENERAL SUMMARY

Part 1

CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION

1. Customer Site File (CPU CS)

ENTP0401H04TEUS ........................................................................................... 11

2. Customer Site File (CPU Crystal)

ENTP0401H05TEUS ........................................................................................... 31

3. Access to the system

ENTP0495P05TEUS ........................................................................................... 53
ENTP0495C01TEUS ........................................................................................... 57

4. Start & Stop the System

ENTP0402P05TEUS ........................................................................................... 65
ENTP0402H01TEUS ........................................................................................... 77

5. IP Addressing Plan
ENTP0457P10TEUS ........................................................................................... 81
ENTP0457C01TEUS ........................................................................................... 85
ENTP0457H01TEUS ........................................................................................... 87

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent i

1
Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
toc.doc

6. Empty database creation

ENTP0411P03TEUS............................................................................................91
ENTP0411C01TEUS............................................................................................95
ENTP0411H03TEUS............................................................................................97

7. Licenses
ENTP0412P09TEUS.......................................................................................... 101
ENTP0412P11TEUS.......................................................................................... 109
ENTP0412C01TEUS.......................................................................................... 115
ENTP0412C02TEUS.......................................................................................... 127
ENTP0412H03TEUS.......................................................................................... 133

8. Management tool: “MGR”

ENTP0413P02TEUS.......................................................................................... 137
ENTP0413C01TEUS.......................................................................................... 141
ENTP0413C02TEUS.......................................................................................... 147

9. Management tool: “Alcatel-Lucent Expert tool”

ENTP0414P02TEUS.......................................................................................... 153
ENTP0414C01TEUS.......................................................................................... 157

10. Maintenance Web Tool

ENTP0458P01TEUS.......................................................................................... 173

11. Shelves & Boards

ENTP0401P10TEUS.......................................................................................... 181
ENTP0401C10TEUS.......................................................................................... 191
ENTP0401C11TEUS.......................................................................................... 203
ENTP0401C12TEUS.......................................................................................... 205
ENTP0401M01TEUS ......................................................................................... 211
ENTP0401H10TEUS.......................................................................................... 219
ENTP0401H11TEUS.......................................................................................... 221

12. Static Voice Guides

ENTP0439P01TEUS.......................................................................................... 225
ENTP0439C01TEUS.......................................................................................... 245
ENTP0439M01TEUS ......................................................................................... 251
ENTP0439H02TEUS.......................................................................................... 259

13. Entity
ENTP0417P03TEUS.......................................................................................... 263

ii All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

2
Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
toc.doc

14. Users
ENTP0403P01CLUS ..........................................................................................273
ENTP0403P11TEUS ..........................................................................................283
ENTP0403C03TEUS ..........................................................................................295
ENTP0403C05TEUS ..........................................................................................299
ENTP0403C06TEUS ..........................................................................................307
ENTP0487C01TEUS ..........................................................................................313
ENTP0403M04TEUS..........................................................................................327
ENTP0403H01TEUS ..........................................................................................337
ENTP0403H02TEUS ..........................................................................................339

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent iii

3
Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
toc.doc

Part 2

15. Terminal Adapters

ENTP0403P07TEUS.......................................................................................... 343
ENTP0403C12TEUS.......................................................................................... 349
ENTP0403H12TEUS.......................................................................................... 353

16. Prefix Plan

ENTP0420P02TEUS.......................................................................................... 357
ENTP0420C07TEUS.......................................................................................... 363

17. Suffix plan

ENTP0420P03TEUS.......................................................................................... 367
ENTP0420C02TEUS.......................................................................................... 371
ENTP0420M04TEUS ......................................................................................... 373

18. Phone Feature Class of Services

ENTP0404P08TEUS.......................................................................................... 383
ENTP0404C08TEUS.......................................................................................... 387
ENTP0404H08TEUS.......................................................................................... 391

19. Dynamic Voice guides

ENTP0439C02TEUS.......................................................................................... 397
ENTP0439M02TEUS ......................................................................................... 407
ENTP0439H01TEUS.......................................................................................... 413

20. Music on Hold - Capacity increase

ENTP0800P02TEUS.......................................................................................... 417

21. Ringing Tones Customization Tool

ENTP0800P03TEUS.......................................................................................... 425
ENTP0800C03TEUS.......................................................................................... 433

22. Trunk groups

ENTP0409P10TEUS.......................................................................................... 437
ENTP0409C02TEUS.......................................................................................... 443
ENTP0409C03TEUS.......................................................................................... 447
ENTP0409C05TEUS.......................................................................................... 453
ENTP0409C07TEUS.......................................................................................... 459
ENTP0409M01TEUS ......................................................................................... 465
ENTP0409H01TEUS.......................................................................................... 475

iv All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

4
Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
toc.doc

23. System synchronization

ENTP0437P01TEUS ..........................................................................................479
ENTP0437H01TEUS ..........................................................................................485

24. DID Translator

ENTP0424P01TEUS ..........................................................................................489
ENTP0424C05TEUS ..........................................................................................497
ENTP0424M05TEUS..........................................................................................501
ENTP0424H01TEUS ..........................................................................................505

25. External Callback Translator

ENTP0427P01TEUS ..........................................................................................509
ENTP0427C02TEUS ..........................................................................................515
ENTP0427H01TEUS ..........................................................................................517

26. External Calls Barring

ENTP0426P01TEUS ..........................................................................................521
ENTP0426C03TEUS ..........................................................................................531
ENTP0426M01TEUS..........................................................................................535
ENTP0426A01TEUS ..........................................................................................539
ENTP0426H03TEUS ..........................................................................................543

27. Automatic Route Selection (ARS)

ENTP0425P01TEUS ..........................................................................................547
ENTP0425C02TEUS ..........................................................................................557
ENTP0425M01TEUS..........................................................................................565
ENTP0425H01TEUS ..........................................................................................569

28. Automatic Callback on Busy Trunk Group

ENTP0481P01TEUS ..........................................................................................573
ENTP0481C01TEUS ..........................................................................................581
ENTP0481M01TEUS..........................................................................................585
ENTP0481H01TEUS ..........................................................................................589

29. Connection & transfer Classes of services

ENTP0404P06TEUS ..........................................................................................593
ENTP0404C02TEUS ..........................................................................................599
ENTP0404H02TEUS ..........................................................................................609

30. Multi-line sets

ENTP0406P02TEUS ..........................................................................................613
ENTP0406C02TEUS ..........................................................................................625
ENTP0406C04TEUS ..........................................................................................629
ENTP0406H02TEUS ..........................................................................................635

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent v

5
Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
toc.doc

31. Assistant / Manager groups

ENTP0407P01TEUS.......................................................................................... 639
ENTP0407C02TEUS.......................................................................................... 649
ENTP0407M01TEUS ......................................................................................... 657
ENTP0407H01TEUS.......................................................................................... 661

32. Multiple Line Appearance (MLA)

ENTP0480P02TEUS.......................................................................................... 665
ENTP0480C02TEUS.......................................................................................... 683
ENTP0480H02TEUS.......................................................................................... 693

vi All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

6
Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
toc.doc

Part 3

33. Groups
ENTP0405P03TEUS ..........................................................................................697
ENTP0405C01TEUS ..........................................................................................713
ENTP0405C02TEUS ..........................................................................................717
ENTP0405M01TEUS..........................................................................................721
ENTP0405H02TEUS ..........................................................................................727

34. Call Distribution

ENTP0418P10TEUS ..........................................................................................731

35. Call Distribution - Entities

ENTP0418P11TEUS ..........................................................................................741
ENTP0418C11TEUS ..........................................................................................747
ENTP0418M01TEUS..........................................................................................753
ENTP0418H11TEUS ..........................................................................................759

36. Call Distribution - Attendant Groups

ENTP0418P12TEUS ..........................................................................................763
ENTP0416C02TEUS ..........................................................................................769
ENTP0416M01TEUS..........................................................................................773

37. Call Distribution – Attendants sets

ENTP0418P13TEUS ..........................................................................................781
ENTP0415C13TEUS ..........................................................................................787
ENTP0415P02TEUS ..........................................................................................793
ENTP0415P04TEUS ..........................................................................................807
ENTP0415C03TEUS ..........................................................................................813
ENTP0882P02TEUS ..........................................................................................819
ENTP0882C02TEUS ..........................................................................................823
ENTP0415M01TEUS..........................................................................................831
ENTP0415H03TEUS ..........................................................................................839

38. DECT - IBS

ENTP0419P01TEUS ..........................................................................................843
ENTP0419C01TEUS ..........................................................................................851
ENTP0419C04TEUS ..........................................................................................855
ENTP0419M01TEUS..........................................................................................859
ENTP0419H02TEUS ..........................................................................................871

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent vii

7
Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
toc.doc

39. Direct Speed Dialing

ENTP0408P01TEUS.......................................................................................... 875
ENTP0408C04TEUS.......................................................................................... 883
ENTP0408M01TEUS ......................................................................................... 887
ENTP0408H01TEUS.......................................................................................... 891

40. Speed Dialing by range

ENTP0408P02TEUS.......................................................................................... 895
ENTP0408C03TEUS.......................................................................................... 901
ENTP0408H02TEUS.......................................................................................... 907

41. Alcatel-Lucent OmniMessage 4645

ENTP0432P01TEUS.......................................................................................... 911
ENTP0432C01TEUS.......................................................................................... 927
ENTP0432C02TEUS.......................................................................................... 939
ENTP0432M01TEUS ......................................................................................... 943
ENTP0432H01TEUS.......................................................................................... 951

42. MOXA V24/IP Box

ENTP0444P01TEUS.......................................................................................... 955
ENTP0444C01TEUS.......................................................................................... 963
ENTP0444M01TEUS ......................................................................................... 969
ENTP0444H01TEUS.......................................................................................... 981

43. Database Save & Restore

ENTP0411P04TEUS.......................................................................................... 985
ENTP0411C02TEUS.......................................................................................... 989
ENTP0411H02TEUS.......................................................................................... 995

44. RMA Solutions & System Messages

ENTP0431P01TEUS.......................................................................................... 999
ENTP0431P06TEUS.........................................................................................1009
ENTP0431P07TEUS.........................................................................................1021
ENTP0431P08TEUS.........................................................................................1031
ENTP0421P01TEUS.........................................................................................1037
ENTP0431C06TEUS.........................................................................................1045
ENTP0431C08TEUS.........................................................................................1055
ENTP0431H08TEUS.........................................................................................1059

45. Appendix A – Reflexes & e-Reflexes

ENTP0403P06TEUS.........................................................................................1063
ENTP0403C07TEUS.........................................................................................1077
ENTP0403M01TEUS ........................................................................................1081

viii All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

8
Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
toc.doc

FEEDBACK SHEET
In order to improve the quality of the documentation, please report any errors found by
returning this sheet to the address below.

CHAPTER PAGE DESCRIPTION

Please return this sheet to:

Alcatel-Lucent Enterprise Solutions Training
8, rue de Kervézennec
CS 82802
29228 BREST CEDEX 2 – FRANCE
FAX : (33) 2 98 14 36 36
Email: [email protected]
Website: www.businesspartner.alcatel-lucent.com

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent ix

9
Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
toc.doc

x All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

10
Alcatel-Lucent OmniPCX Enterprise
Starter Pack Enterprise Site File

CUSTOMER SITE FILE (CPU-CS)

DETAILED SPECIFICATION FOR IPC STARTER CORE COURSE

Issue 04 Ref. ENTP0401H04TEUS.doc AP. 1

The objective is to used the same documentation model during the training lab, then the
participant can act as if she/he was on site

Notice
The information contained in this document is subject to change without notice.

ALCATEL MAKES NO WARRANTY OF ANY KIND WITH REGEARD TO THIS MATERIAL, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MECHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. Alcatel shall not be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing, performance, or use of this material.

Alcatel assumes no responsibility for the use or reliability of interconnected equipment that is
not furnished by Alcatel.

This document contains proprietary information that is protected by copyright. All rights are
reserved. No part of this document may be photocopied, reproduced or translated to another
program language without prior written consent of Alcatel.

The information contained herein has been prepared by Alcatel, solely for use by Alcatel
employees, agents and customers. Dissemination of the information and/or concepts contained
herein to other parties is prohibited without Alcatel prior written consent.

Materials in the Student Guide are intended for training purposes

The training materials are intended to be a representative sample, not an exhaustive reference
source. For specific system information, refer to the equipment manuals shipped with the
system.

AP. 2 Ref. ENTP0401H04TEUS.doc Issue 04

TABLE OF CONTENTS

1. PRELIMINARY .................................................................................... 5
1.1. Object ........................................................................................ 5
1.2. Contact ....................................................................................... 5

2. LANGUAGE....................................................................................... 5

3. DATE AND TIME DISPLAY FORMAT ............................................................ 5

4. SYSTEM OVERVIEW ............................................................................. 6

4.1. TOPOLOGY OF EACH NODE................................................................. 6
4.1.1. Call Server.................................................................................... 6
4.1.2. Media Gateway .............................................................................. 6
4.2. RELEASE ...................................................................................... 7
4.3. IP Addressing Plan .......................................................................... 7

5. DIALLING PLAN.................................................................................. 8
5.1. Installation Number......................................................................... 8
5.2. Numbering Plan ............................................................................. 8
5.2.1. Generic numbers (Prefix Plan) ............................................................ 8
5.2.2. Stations: .................................................................................... 11

6. INCOMING CALL ................................................................................12

6.1. Direct Incoming call .......................................................................12
6.2. Incoming calls to the main number .....................................................12
6.2.1. Day mode ................................................................................... 12
6.2.2. Night Mode ................................................................................. 12
6.2.3. Internal General Attendant Call......................................................... 12

7. OUTBOUND CALL ..............................................................................13

7.1. Direct Outbound Calls .....................................................................13
7.2. Area definition for barring ...............................................................13

8. IP –PCX CONFIGURATION .....................................................................14

8.1. User name & first name...................................................................14
8.2. Sets Profile..................................................................................14
8.2.1. Basic digital sets (4020) .................................................................. 14
8.2.2. Advanced digital sets (4035)............................................................. 15
8.2.2.1. Digital set.......................................................................................... 15
8.2.2.2. Digital set (4029) ................................................................................. 16
8.2.2.3. Digital set (4039) ................................................................................. 16

Issue 04 Ref. ENTP0401H04TEUS.doc AP. 3

8.3. Class of services............................................................................17

8.3.1. Phone facilities ............................................................................ 17
8.3.2. Class of Service for External Access .................................................... 18
8.3.2.1. Numbering area................................................................................... 18
8.3.2.2. Class Of Access (Public and Private) .......................................................... 18
8.3.2.3. Private Access..................................................................................... 18

AP. 4 Ref. ENTP0401H04TEUS.doc Issue 04

1. PRELIMINARY

1.1. Object
From the architecture define by pre sales and customer needs, this document
reviews all details and configuration choices to ensure a smooth implementation on
site.

1.2. Contact
Consider your instructor as the Contact of this Project. Do not hesitate to ask
him/her details if needed.

2. LANGUAGE
All the OmniPCX will be installed with only one language: US

3. DATE AND TIME DISPLAY FORMAT

All the OmniPCX will use the English format.

mm/dd/yy hh:mm Am or pm

Issue 04 Ref. ENTP0401H04TEUS.doc AP. 5

4. SYSTEM OVERVIEW

4.1. TOPOLOGY OF EACH NODE

3X004
3X100 3X101 3X005

3X110 3X111
Rack 1 IP
Réseau
Network
IP

Rack 2
3X200 3X201

3X210 3X211
Rack 3
ISDN
Network
Réseau
3X000 3X001 RNIS

3X002

3X010 3X011 3X003

4.1.1. Call Server

Type: Call Server: CS
Duplication used
4.1.2. Media Gateway
The media gateway (GD) has to be configured manually. The media gateway
number one used as a reference
Rack 1: Media Gateway Large

Position Type
0 GD
1 UAI8
2 PRA T2
3 SLI8
4 BRA 4

AP. 6 Ref. ENTP0401H04TEUS.doc Issue 04

Rack 2: Media Gateway Large ( Expansion of rack 1)

Position Type
0 MEX
1 MIX 2/4/4

Rack 3: ACT 14

Position Type
3 UA32
4 Z24
5 BPRA2
9 PCM2
10 INTIPB

4.3. IP Addressing Plan

IP Network LAN addressing: 10.SC.x.0 (Sub Net Mask: 255.255.255.0)
CS IP Address: 10.SC.x.1
GD IP Address: 10.SC.x.11
PC IP Address: 10.SC.x.10
INTIP address: 10.SC.x.30
Gateway IP address: 10.SC.x.254
SC = Classroom number
X = Node number

Issue 04 Ref. ENTP0401H04TEUS.doc AP. 7

5. DIALLING PLAN
Country Code:;US0

5.1. Installation Number

The installation number is 2SC43 xxxx
The station are based on a 4-digit plan.
The supplementary number is x008.

5.2. Numbering Plan

5.2.1. Generic numbers (Prefix Plan)

Prefix Prefix Meaning

0 Professional TG With Overlapping
3X000 Station
3X001 Station
3X002 Station
3X003 Station
3X004 Station
3X005 Station
3X010 Station
3X011 Station
3X100 Station
3X101 Station
3X110 Station
3X111 Station
3X200 Station
3X201 Station
3X210 Station
3X211 Station
400 Set In/Out of service
401 Recordable Voice Guides
402 Park Call/Retrieve

AP. 8 Ref. ENTP0401H04TEUS.doc Issue 04

Prefix Prefix Meaning

403 Accounting/Chargeback Readout
404 Associated Direct. No. modif.
405 Password modification
406 Redial last number
407 Night service answering
408 Adjust Display Visibility
409 Secret/Identity
41 Forward cancellation
42 Do not disturb
43 Voice Mail Access
44 Cancel auto. callback on busy
45 Lock
46 Access Callback list
470 Access to waiting call
471 Business account code
472 Message deposit
473 Paging call answer
474 Language
480 Sta. group entry
481 Sta. group exit
482 Switch off Message LED
483 Mask remote identity
484 Cancel Remote forward
485 Overfl.busy to assoc.set
486 Overf.busy/no answer to assoc.set
487 Conversation Recording
490 Ubiquity Mobile Programming
495 Ubiquity

Issue 04 Ref. ENTP0401H04TEUS.doc AP. 9

Prefix Prefix Meaning

500 Last Caller Callback
501 Remote forward
502 Overfl.on no answer to associate
503 Cancel Overfl.to associate
504 Protect. against barge-in & beeps
505 Substitution
506 Wake-up/appointment reminder
507 Cancel Wake-up
508 Forward cancel.by destinat.
509 Meet-me Conference
51 Immediate forward
52 Immediate forward on busy
53 Forward on no answer
54 Forward on busy or no answer
55 Direct call pickup
56 Group call pickup
570 Voice Mail Deposit
580 Tone test
581 Personal directory Programming
582 Personal Directory Use
583 Force Set Type Identification
584 Suite Wake-up
585 Suite Wake-up Cancel
586 Suite Do Not Disturb
587 Room status management
588 Mini-bar
589 Direct Paging Call
599 Professional trunk seize

AP. 10 Ref. ENTP0401H04TEUS.doc Issue 04

Prefix Prefix Meaning

9 Attendant Call
* DTMF end-to-end dialing
#0X0 Professional trunk seize
#0X2 Professional trunk seize
A3X008 Physical Attendant set No.
A3X018 Physical Attd Group No.

5.2.2. Stations:

Directory nb Function Name Position Type

3x000 Sets UA3x000 Nx Rack 1- Board UAI8 (1-1-0) 4035
3x001 Sets UA3x001 Nx Rack 1- Board UAI8 (1-1-1) 4020
3x002 Sets UA3x002 Nx Rack 1- Board UAI8 (1-1-2) 4039
3x003 Sets UA3x003 Nx Rack 1- Board UAI8 (1-1-3) 4029
3x004 Sets UA3x004 Nx 4038
3x005 Sets UA3x005 Nx 4028
3x010 Sets PS3x010 Nx Rack 1- Board SLI8 (1-3-0) Analog
3x011 Sets PS3x011 Nx Rack 1- Board SLI8 (1-3-1) Analog
3x100 Sets UA3x100 Nx Rack 2- Board MIX (2-1-32) 4035
3x101 Sets UA3x101 Nx Rack 2- Board MIX (2-1-33) 4020
3x110 Sets PS3x110 Nx Rack 2- Board MIX (2-1-64) Analog
3x111 Sets PS3x111 Nx Rack 2- Board MIX (2-1-65) Analog
3x200 Sets UA3x200 Nx Rack 3- Board UA32 (3-3-0) 4035
3x201 Sets UA3x201 Nx Rack 3- Board UA32 (3-3-1) 4020
3x210 Sets PS3x210 Nx Rack 3- Board Z24 (3-4-0) Analog
3x211 Sets PS3x211 Nx Rack 3- Board Z24 (3-4-1) Analog
A3x008 Attendant Rack 1- Board UAI8 (1-1-7) 4035

Issue 04 Ref. ENTP0401H04TEUS.doc AP. 11

6. INCOMING CALL

6.1. Direct Incoming call

All the UA Sets have the Direct Dialling Inward Facility.
The analogue sets can not be called directly but can be reached through the
Attendant transfer.
The numbering plan descriptor (NPD) number 15 will be used for outbound and
inbound DID translation:
Name: Public Outgoing
Calling Numbering Plan Identification: Unknown
Called Numbering Plan Identification: Unknown
Authorize personal calling number use: No
Installation number source: Entity Source
Default number source: Entity Source
Caller DID identifier: 0 (Incoming Call)
Calling DID identifier: 0 (Outbound Call)
DID translator: 0
First external number: x000
First internal number: 3x000
Range size: 50
Unique internal number: No
In case of failure, entity information (Installation Nb 02CL0 and Supplementary
Installation Nb x008 will be used)

6.2. Incoming calls to the main number

The main number will be the « entity #1 call » prefix 3x008 in order to be able to
make a difference between day and night mode.
Here is the required management for the Call Distribution Table of the entity 1
6.2.1. Day mode
On day Mode (when at least one attendant is present)
Routing #1: A3x018 (Attendant Group)
Overflow Routing Number: 3x010
6.2.2. Night Mode
Overflow Routing Number: 3x010
6.2.3. Internal General Attendant Call
When an internal user wants to reach an attendant, the prefix 9 is dialed.
This prefix must rout the call to the Call Distribution Table of the user's
entity.

AP. 12 Ref. ENTP0401H04TEUS.doc Issue 04

7. OUTBOUND CALL

7.1. Direct Outbound Calls

In a first Step, professional Trunk Group seizure must be used (no ARS)
Resources of the system:
ISDN Trunk Group:
Id: x0 T0
Id: x2 T2
Board: PRA-E1 (Rack 1, Board Position 2, Access 0) for T2
Board: BRA 4 (Rack 1, Board Position 4, Access 0) for T0
Trunk Group Seizure: #0X0 for T0
Trunk Group Seizure: #0X2 for T2
Baring: Yes

7.2. Area definition for barring

The dialing DISCRIMINATOR 0 (Public) has to be used.
area 3 : international calls: 00;
area 2: National calls: 03;04;
area 1: local calls + emergency calls: 01;02;
(See User Profile to know which area is allowed)

Issue 04 Ref. ENTP0401H04TEUS.doc AP. 13

8. IP –PCX CONFIGURATION
Object of this section is to define the different profiles which will be used for the . Each
user will be define by the following parameters:
Set type
Programmable key profile
Phone Facilities COS
External access COS
Voice Mail COS

8.1. User name & first name

The first name is defined on 8 characters in capital letters and contains the site
name.
The last name is defined on 12 characters in capital letters and contains the
function.
Example:
Last Name: PRINCIPAL
First Name: CIMARRON
Display: PRINCIPAL CIMARRON

8.2. Sets Profile

8.2.1. Basic digital sets (4020)
Call by name allowed

Programming /
Display mode

Personal directory
Programmable keys
See below the profile

Secret / Intercom

Transfer

Loudspeaker Message
Hands Free
End

Key 1 Not Assigned Key 2 Not Assigned

Key 3 Not Assigned Key 4 Not Assigned
Key 5 Not Assigned Key 6 Not Assigned
Key 7 Redial Memory Key 8 ISDN
Key 9 Immediate Forward Key 10 Three Party Conference
Key 12 Manual Hold Key 15 Transfer

AP. 14 Ref. ENTP0401H04TEUS.doc Issue 04

8.2.2. Advanced digital sets (4035)

Call by name allowed
Soft Keys
Navigator

Mute

Loudspeaker Programmable keys

Loudspeaker See below
Depending of the profile

End
Hands free

Key 1 Key 2 Key 13 Key 14

Key 3 Key 4 Key 15 Key 16
Key 5 Key 6 Key 17 Key 18
Key 7 Key 8 Key 19 Key 20
Key 9 Key 10 Key 21 Key 22 ISDN
Key 11 Key 12 Key 23 Redial Key 24 Redial Memory

8.2.2.1. Digital set

Call
Call
Presentation Plugged/Unp
Key 1 Presentation Key 2 Key 13 Key 14
common lugged
other calls
hold
Key 3 Key 4 Key 15 Key 16
Key 5 Key 6 Key 17 Key 18
Key 7 Key 8 Key 19 Key 20
Key 9 Key 10 Key 21 Key 22 ISDN
Key 11 Key 12 Key 23 Redial Key 24 Redial
Memory

Issue 04 Ref. ENTP0401H04TEUS.doc AP. 15

8.2.2.2. Digital set (4029)

Program keys
Navigator

Mute

End

Hands free
Loudspeaker

8.2.2.3. Digital set (4039)

Programmables key
Navigator

End Loudspeaker

Hands free

Mute

AP. 16 Ref. ENTP0401H04TEUS.doc Issue 04

8.3. Class of services

8.3.1. Phone facilities

0 1 5 10
Rights / Forward to External Number X X X
Rights / Protected again interception
Rights / Protected against set intrude X X X
Rights / Protected against all intrudes X X X
Rights / Protected against forwarding
Rights / Protection against beep X X X
Rights / Protect against Call Announcement X X X
Rights / Follow External Forwarding
Rights / Not Receive Mini Mail
Set Features / Substitution X X X
Set Features / Password Modification X X X X
Set Features / Padlock X X X X
Set Features / Do Not Disturb X X
Set Features / No Ringing
Local Services / Meet me conference
Local Services / Voice mail consultation
Local Services / Recording conversation
By Pass on Do Not Disturb: Allowed X X
Intrusion: Allowed X X X
Three party conference: Allowed X X X X

All users belong to Tel. Features COS 0 by default

Issue 04 Ref. ENTP0401H04TEUS.doc AP. 17

8.3.2. Class of Service for External Access

8.3.2.1. Numbering area
area 3: international calls: 00;
area 2: National calls: 03;04;
area 1: local calls + emergency calls: 01;02;
(See User Profile to know which area is allowed)

8.3.2.2. Class Of Access (Public and Private)

Public Access (without PIN Code) Private Access (With PIN)

International

International
Emergency

National

National
Local +

Local

COS 0 X X X X X X
COS 1 X X X X X
COS 2 X X X X

All users belong to Public Class of Service 2 by default

8.3.2.3. Private Access
PIN Code length: 5 digits (PIN Code must be unique in a network ,
they’re broadcasted)
Profile private call: 0
Use PIN YES
Use code check NO
Call type Normal
Public Network Cat. -1
To do a private call, user have to dial: Private Access Prefix ( #8 ) + PIN
Code (5digits) + External Number
Restrictions:
On private call, call transfer is not allowed.
On attendant console or attendant set, private call is not allowed.

AP. 18 Ref. ENTP0401H04TEUS.doc Issue 04

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

29
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

30
Alcatel-Lucent OmniPCX Enterprise
Starter Pack Enterprise Site File

CUSTOMER SITE FILE (CPU CRYSTAL)

DETAILED SPECIFICATION FOR IPC STARTER CORE COURSE

Issue 04 Ref. ENTP0401H05TEUS.doc AP. 1

This document used for the LAB, is based on the template used by the Professional services
team. It allows you the customer configuration that has to be deployed according to numbering
plan, phone facilities, external call configuration …
The objective is to used the same documentation model during the training lab, then the
participant can act as if she/he was on site

Notice
The information contained in this document is subject to change without notice.
ALCATEL MAKES NO WARRANTY OF ANY KIND WITH REGEARD TO THIS MATERIAL, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MECHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. Alcatel shall not be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing, performance, or use of this material.
Alcatel assumes no responsibility for the use or reliability of interconnected equipment that is
not furnished by Alcatel.
This document contains proprietary information that is protected by copyright. All rights are
reserved. No part of this document may be photocopied, reproduced or translated to another
program language without prior written consent of Alcatel.
The information contained herein has been prepared by Alcatel, solely for use by Alcatel
employees, agents and customers. Dissemination of the information and/or concepts contained
herein to other parties is prohibited without Alcatel prior written consent.

Materials in the Student Guide are intended for training purposes

only.
Due to variations in hardware configurations and software versions, it is not possible for the
training materials to match exactly every customer’s equipment. Although this student guide
may be structured for the most current release, it is applicable to previous releases.
The training materials are intended to be a representative sample, not an exhaustive reference
source. For specific system information, refer to the equipment manuals shipped with the
system.

AP. 2 Ref. ENTP0401H05TEUS.doc Issue 04

TABLE OF CONTENTS

2. LANGUAGE....................................................................................... 5

3. DATE AND TIME DISPLAY FORMAT ............................................................ 5

4. SYSTEM OVERVIEW ............................................................................. 6

4.1. Topology of each node ..................................................................... 6
4.1.1. Call Server.................................................................................... 6
4.1.2. Media Gateway .............................................................................. 6
4.2. RELEASE ...................................................................................... 7

6. INCOMING CALL ................................................................................12

7. OUTBOUND CALL ..............................................................................13

7.1. Direct Outbound Calls .....................................................................13
7.2. Area definition for barring ...............................................................13

8. IP –PCX CONFIGURATION .....................................................................14

8.1. User name & first name...................................................................14
8.2. Sets Profile..................................................................................15
8.2.1. Basic digital sets (4020) .................................................................. 15
8.2.2. Advanced digital sets (4035)............................................................. 16
8.2.3. Attendant or equivalent .................................................................. 16
8.2.3.1. Digital set (4029) ................................................................................. 17
8.2.3.2. Digital set (4039) ................................................................................. 17

Issue 04 Ref. ENTP0401H05TEUS.doc AP. 3

8.3. Class of services............................................................................18

8.3.1. Phone facilities ............................................................................ 18
8.3.2. Class of Service for External Access .................................................... 19
8.3.2.1. Numbering area................................................................................... 19
8.3.2.2. Class Of Access (Public and Private) .......................................................... 19
8.3.2.3. Private Access..................................................................................... 19

AP. 4 Ref. ENTP0401H05TEUS.doc Issue 04

1. PRELIMINARY

1.1. Object
From the architecture define by pre sales and customer needs, this document
reviews all details and configuration choices to ensure a smooth implementation on
site.

1.2. Contact
Consider your instructor as the Contact of this Project. Do not hesitate to ask
him/her details if needed.

2. Language
All the OmniPCX will be installed with only one language: US

3. Date and time display format

All the OmniPCX will use the English format.
mm/dd/yy hh:mm Am or pm

Issue 04 Ref. ENTP0401H05TEUS.doc AP. 5

4. SYSTEM OVERVIEW

4.1. Topology of each node

3X004
3X100 3X101 3X005

3X110 3X111 IP
Rack 1 Réseau
IP
Network

Rack 2

3X200 3X201

3X210 3X211
3X002

3X003
3X000 3X001 Rack 0
Network
ISDN

3X010 3X011

4.1.1. Call Server

Type: Call Server: CPU 6,CPU 7 or CPU 5_3
Duplication used
4.1.2. Media Gateway
The media gateway (GD) has to be configured manually. The media gateway
number one used as a reference
Rack 1: Media Gateway Large

Position Type
0 GD
1 UAI8
2 PRA T2
3 SLI8
4 BRA 4

AP. 6 Ref. ENTP0401H05TEUS.doc Issue 04

Rack 2: Media Gateway Large (Expansion of rack 1)

Position Type
0 MEX
1 MIX 2/4/4

Rack 0: ACT 14

Position Type
3 UA32
4 Z24
5 BPRA2
6 CPU6,CPU 7 or
CPU5_3
9 PCM2
11 INTIP

4.2. RELEASE
SYSTEME RELEASE: OmniPCX Enterprise Software R9
Ask your Contact Manager to know the exact Release Number (e.g. H1.301.23)
Release: _____________
Static Patch: __________
Dynamic Patch: ______
IP Addressing Plan
IP Network LAN addressing: 10.SC.x.0 (Sub Net Mask: 255.255.255.0)
CS IP Address: 10.SC.x.1
GD IP Address: 10.SC.x.11
PC IP Address: 10.SC.x.10
INTIP address: 10.SC.x.30
Gateway IP address: 10.SC.x.254
SC = Classroom number
X = Node number

Issue 04 Ref. ENTP0401H05TEUS.doc AP. 7

5. DIALLING PLAN
Country Code:;US0

5.1. Installation Number

The installation number is 2SC43 xxxx
The station are based on a 4-digit plan.
The supplementary number is x008.

5.2. Numbering Plan

5.2.1. Generic numbers (Prefix Plan)

Prefix Prefix Meaning

AP. 8 Ref. ENTP0401H05TEUS.doc Issue 04

Prefix Prefix Meaning

Issue 04 Ref. ENTP0401H05TEUS.doc AP. 9

Prefix Prefix Meaning

AP. 10 Ref. ENTP0401H05TEUS.doc Issue 04

Prefix Prefix Meaning

9 Attendant Call
* DTMF end-to-end dialing
#0X0 Professional trunk seize
#0X2 Professional trunk seize
A3X008 Physical Attendant set No.
A3X018 Physical Attd Group No.

5.2.2. Stations:

Directory nb Fonction Name Position Type

3x000 Sets UA3x000 Nx Rack 0- Board UA32 (0-3-0) 4035
3x001 Sets UA3x001 Nx Rack 0- Board UA32 (0-3-1) 4020
3x002 Sets UA3x002 Nx Rack 0- Board UA32 (0-3-1) 4039
3x003 Sets UA3x003 Nx Rack 0- Board UA32 (0-3-1) 4029
3x004 Sets UA3x004 Nx 4038
3x005 Sets UA3x005 Nx 4028
3x010 Sets PS3x010 Nx Rack 0- Board Z24 (0-4-0) Analog
3x011 Sets PS3x011 Nx Rack 0- Board Z24 (0-4-1) Analog
3x100 Sets UA3x100 Nx Rack 1- Board UAI8 (1-1-0) 4035
3x101 Sets UA3x101 Nx Rack 1- Board UAI8 (1-1-1) 4020
3x110 Sets PS3x110 Nx Rack 1- Board SLI8 (1-3-0) Analog
3x111 Sets PS3x111 Nx Rack 1- Board SLI8 (1-3-0) Analog
3x200 Sets UA3x200 Nx Rack 2- Board MIX (2-1-32) 4035
3x201 Sets UA3x201 Nx Rack 2- Board MIX (2-1-33) 4020
3x210 Sets PS3x210 Nx Rack 2- Board MIX (2-1-64) Analog
3x211 Sets PS3x211 Nx Rack 2- Board MIX (2-1-65) Analog
A3x008 Attendant Rack 1- Board UAI8 (1-1-7) 4035

Issue 04 Ref. ENTP0401H05TEUS.doc AP. 11

6. INCOMING CALL

6.1. Direct Incoming call

All the UA Sets have the Direct Dialing Inward Facility.
The analogue sets can not be called directly but can be reached through the
Attendant transfer.
The numbering plan descriptor (NPD) number 15 will be used for outbound and
inbound DID translation:
Name: Public Outgoing
Calling Numbering Plan Identification: Unknown
Called Numbering Plan Identification: Unknown
Authorize personal calling number use: No
Installation number source: Entity Source
Default number source: Entity Source
Caller DID identifier: 0 (Incoming Call)
Calling DID identifier: 0(Outbound Call)
DID translator: 0
First external number: x000
First internal number: 3x000
Range size: 50
Unique internal number: No
In case of failure, entity information (Installation Nb 02CL0 and Supplementary
Installation Nb x008 will be used)

6.2. Incoming calls to the main number

AP. 12 Ref. ENTP0401H05TEUS.doc Issue 04

7. OUTBOUND CALL

7.1. Direct Outbound Calls

In a first Step, professional Trunk Group seizure must be used (no ARS)
Resources of the system:
ISDN Trunk Group:
Id: x0 T0
Id: x2 T2
Board: BPRA 2 (Rack 0, Board Position 5, Access 0) for T2
Board: BPRA 2 (Rack 0, Board Position 5, Access 1) for T0
Trunk Group Seizure: #0X0 for T0
Trunk Group Seizure: #0X2 for T2
Baring: Yes

7.2. Area definition for barring

The dialing DISCRIMINATOR 0 (Public) has to be used.
- Area 3: international calls: 00;
- Area 2: National calls: 03;04;
- Area 1: local calls + emergency calls: 01;02;
(See User Profile to know which area is allowed)

Issue 04 Ref. ENTP0401H05TEUS.doc AP. 13

8.1. User name & first name

AP. 14 Ref. ENTP0401H05TEUS.doc Issue 04

8.2. Sets Profile

8.2.1. Basic digital sets (4020)
Call by name allowed

Programming /
Display mode

Personal directory
Programmable keys
See below the profile

Secret / Intercom

Transfer

Loudspeaker Message
Hands Free
End

Key 1 Not Assigned Key 2 Not Assigned

Key 3 Not Assigned Key 4 Not Assigned
Key 5 Not Assigned Key 6 Not Assigned
Key 7 Redial Memory Key 8 ISDN
Key 9 Immediate Forward Key 10 Three Party Conference
Key 12 Manual Hold Key 15 Transfer

Issue 04 Ref. ENTP0401H05TEUS.doc AP. 15

8.2.2. Advanced digital sets (4035)

Call by name allowed
Soft Keys
Navigator

Mute

Loudspeaker
Loudspeaker

Programmable keys
See below
Hands free End Depending of the profile

Key 1 Key 2 Key 13 Key 14

Key 3 Key 4 Key 15 Key 16
Key 5 Key 6 Key 17 Key 18
Key 7 Key 8 Key 19 Key 20
Key 9 Key 10 Key 21 Key 22 ISDN
Key 11 Key 12 Key 23 Redial Key 24 Redial Memory

8.2.3. Attendant or equivalent

Key 1 Call Key 2 Key 13 Call Key 14 Plugged/Un

Presentatio Presentation plugged
n other common
calls hold
Key 3 Key 4 Key 15 Key 16
Key 5 Key 6 Key 17 Key 18
Key 7 Key 8 Key 19 Key 20
Key 9 Key 10 Key 21 Key 22 ISDN

AP. 16 Ref. ENTP0401H05TEUS.doc Issue 04

8.2.3.1. Digital set (4029)

Program keys
Navigator

Mute

End

Hands free
Loudspeaker

8.2.3.2. Digital set (4039)

Programmables key
Navigator

End Loudspeaker

Hands free

Mute

Issue 04 Ref. ENTP0401H05TEUS.doc AP. 17

8.3. Class of services

8.3.1. Phone facilities
0 1 5 10
Rights / Forward to External Number X X X
Rights / Protected again interception
Rights / Protected against set intrude X X X
Rights / Protected against all intrudes X X X
Rights / Protected against forwarding
Rights / Protection against beep X X X
Rights / Protect against Call Announcement X X X
Rights / Follow External Forwarding
Rights / Not Receive Mini Mail
Set Features / Substitution X X X
Set Features / Password Modification X X X X
Set Features / Padlock X X X X
Set Features / Do Not Disturb X X
Set Features / No Ringing
Local Services / Meet me conference
Local Services / Voice mail consultation
Local Services / Recording conversation
By Pass on Do Not Disturb: Allowed X X
Intrusion: Allowed X X X
Three party conference: Allowed X X X X

All users belong to to Tel. Features COS 0 by default

AP. 18 Ref. ENTP0401H05TEUS.doc Issue 04

8.3.2. Class of Service for External Access

8.3.2.1. Numbering area
- Area 3 : international calls: 00;
- Area 2: National calls: 03;04;
- Area 1: local calls + emergency calls: 01;02;
(See User Profile to know which area is allowed)
8.3.2.2. Class Of Access (Public and Private)

Public Access
Private Access (With PIN)
(without PIN Code)

International

International
Emergency

National

National
Local +

Local
COS 0 X X X X X X
COS 1 X X X X X
COS 2 X X X X

All users belong to Public Class of Service 2 by default

8.3.2.3. Private Access
PIN Code length: 5 digits (PIN Code must be unique in a network , they’re
broadcasted)
Profile private call: 0
Use PIN YES
Use code check NO
Call type Normal
Public Network Cat. -1
To do a private call, user have to dial: Private Access Prefix ( #8 ) + PIN
Code (5digits) + External Number
Restrictions:
On private call, call transfer is not allowed.
On attendant console or attendant set, private call is not allowed.

Issue 04 Ref. ENTP0401H05TEUS.doc AP. 19

AP. 20 Ref. ENTP0401H05TEUS.doc Issue 04

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

51
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

52
Alcatel-Lucent OmniPCX Enterprise

System accounts

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the most common used system accounts

Alcatel-Lucent OmniPCX Enterprise – System accounts

Ref. ENTP0495P05TEUS Issue 02

53
System accounts

What is a system account?

An account is used to protect and to secure accesses to the system by using a

“login” and a “password”

An account is linked to a specific environment

Default directory
Specific maintenance commands

After the system installation, the main accounts used for maintenance are:
“mtcl”
Webtool access
Maintenance commands

“client”
Default environment for maintenance use

“swinst”
Save/Restore operations

All Rights Reserved © 2008, Alcatel-Lucent 2

Remark
The “swinst” account can only be accessed via v24 connection (if only an IP connection is available, “mtcl” account has to be
used, then, the “swinst” command has to be used to access to this account)

Alcatel-Lucent OmniPCX Enterprise – System accounts

Ref. ENTP0495P05TEUS Issue 02

54
System accounts

Each account is set up with a default password

“mtcl” Á “mtcl”

“client” Á This account does not exist by default in the system

At its creation , the system administrator has to give a password

“swinst” Á “SoftInst”

The default account password has to be modified in order to ensure more

security for the system access

For example, it is not possible to access to the “Webtool” without modifying

the “mtcl” account password

The “passwd”(1) command can be used to modify the account passwords

All Rights Reserved © 2008, Alcatel-Lucent 3

(1) This command has to be used under the concerned account

Alcatel-Lucent OmniPCX Enterprise – System accounts

Ref. ENTP0495P05TEUS Issue 02

55
System accounts
Connections

The command “last” allows to check the last connections to the system
It show the account name, the connection port (and IP @ if it exist), date &
time, connection status and duration of the connection

(1)alu-brest-a> last
client pts/1 10.48.2.10 Sun Dec 30 21:08 - 21:12 (00:04)
mtcl pts/0 10.48.2.6 Sun Dec 30 16:00 still logged in
mtcl ttyS0 Sun Dec 30 15:19 - 15:24 (00:05)
reboot system boot 2.4.17-ll-dhs3 Sun Dec 30 15:18 (05:53)
mtcl pts/0 routerv1 Wed Dec 19 10:36 - down (2+07:52)
mtcl pts/0 10.48.2.10 Wed Dec 19 10:22 - 10:29 (00:06)
mtcl ttyS0 Wed Dec 19 10:17 - down (2+08:12)
reboot system boot 2.4.17-ll-dhs3 Wed Dec 19 10:10 (2+08:19)
mtcl ttyS0 Tue Dec 18 18:23 - 18:29 (00:06)
mtcl pts/1 10.48.2.10 Tue Dec 18 18:21 - 18:31 (00:09)
mtcl pts/0 10.48.2.150 Tue Dec 18 18:19 - crash (15:50)
reboot system boot 2.4.17-ll-dhs3 Tue Dec 18 18:16 (3+00:13)
mtcl pts/0 10.48.2.150 Tue Dec 18 18:13 - down (00:01)
mtcl ttyS0 Tue Dec 18 18:05 - down (00:09)
mtcl ttyS0 Tue Dec 18 15:41 - 15:59 (00:17)
reboot system boot 2.4.17-ll-dhs3 Tue Dec 18 15:41 (02:33)
mtcl pts/0 10.48.2.150 Thu Dec 6 17:52 - 17:58 (00:06)
mtcl pts/0 10.48.2.150 Thu Dec 6 11:21 - 17:51 (06:30)
mtcl pts/0 10.48.2.6 Wed Dec 5 23:18 - 23:51 (00:32)

wtmp begins Wed Dec 5 23:12:12 2007

All Rights Reserved © 2008, Alcatel-Lucent 4

Those commands are available under “mtcl” account

In this above example, at least three different ports have been used:
- pts/0: First Telnet port
- pts/1: second Telnet port (only viewable when a a first Telnet session is already active)
- ttyS0: v24 connection port
Types of port

Alcatel-Lucent OmniPCX Enterprise – System accounts

Ref. ENTP0495P05TEUS Issue 02

56
Alcatel-Lucent OmniPCX Enterprise
System accounts

PROCEDURE

OBJECTIVE

- To learn how to make a connection with: root, mtcl and swinst accounts

OVERVIEW
Three mains accounts are used to manage and to maintenance the system, each one have some
specifics rights , the root account is used for the expert maintenance, mtcl account is used for
management of the database and technician’s maintenance and the last one , swinst, is used for
the management of the system like software downloading, save and restore database, OPS ,
etc…
Note: To disconnect enter “exit” for mtcl and root accounts and press “q” to leave
swinst

Issue 02 Ref. ENTP0495C01TEUS.doc P. 1

PROCEDURE

1. “root” account

1.1. Under the login prompt

On the call server

Entry on root
login prompt
Action Press “Enter”
Entry on letacla
password
prompt
Action Press “Enter”
Result xa000001 login: root
Password: letacla
Alcatel OmniPCX Enterprise
standard installation last performed: 26-mar-2008 15:26:45
[root@xa000001 /root]#
Remark If you don’t have the “xa000001 login:” press “Enter”

1.2. Under the mtcl account

On the call server

Entry su
Action Press “Enter”
Entry letacla
Action Press “Enter”
Result (1)xa000001> su
Password: letacla
[root@xa000001 mtcl]#
Remark If you don’t have the “(1)xa000001>” press “Enter”

Note: letacla is the default password, ask the installer to have the new password

P. 2 Ref. ENTP0495C01TEUS.doc Issue 02

2. “mtcl” account

On the call server

Entry mtcl
Action Press “Enter”
Entry mtcl
Action Press “Enter”
Result xa000001 login: mtcl
Password: mtcl
Last login: Mon Jun 4 15:13:20 on ttyS0
Alcatel OmniPCX Enterprise
standard installation last performed: 26-mar-2008 15:26:45
# The role of the CPU is MAIN
Application software identity
R9.0-h1.301-23-fr-c80s1
Business identification: R9.0
Release:
DELIVERY h1.301
Patch identification: 23
Dynamic patch identification: none
Country: fr
Cpu: c80s1
ACD VERSION
release : 6
bug_fixing : 1
protocol_id : 90
version_dy_hr_stat : 11
(1)xa000001>
Remark If you don’t have the “xa000001 login:” press “Enter”

Note: mtcl is the default password, ask the installer to have the new password

Issue 02 Ref. ENTP0495C01TEUS.doc P. 3

3. “swinst” account

3.1. Under the login prompt

On the call server

Entry Swinst
Action Press “Enter”
Entry SoftInst
Action Press “Enter”
Result xa000001 login: swinst
Password: SoftInst
Last installed delivery
DELIVERY h1.301.23
ALCATEL BUSINESS SYSTEMS
FACILITIES Main menu Installation FACILITIES 2.50.0
1 Easy menu
2 Expert menu
Q Exit
Your choice [1..2, Q] ?
Remark If you don’t have the “xa000001 login:” press “Enter”

3.2. Under the mtcl account

On the call server

Under the Swinst
prompt
(1)xa000001>

Action Press “Enter”

Under the SoftInst
prompt
Password

P. 4 Ref. ENTP0495C01TEUS.doc Issue 02

Action Press “Enter”

Result (1)xa000001> swinst
Password: SoftInst

Last installed delivery

DELIVERY h1.301.23
ALCATEL BUSINESS SYSTEMS
FACILITIES Main menu Installation FACILITIES 2.50.0
1 Easy menu
2 Expert menu
Q Exit
Your choice [1..2, Q] ?
Remark If you don’t have the “(1)xa000001>” press “Enter”

3.3. Under the root account

On the call server

Entry Swinst
Action Press “Enter”
Result [root@xa000001 /root]# swinst

Last installed delivery

Note: SoftInst is the default password, ask the installer to have the new password

Issue 02 Ref. ENTP0495C01TEUS.doc P. 5

4. Check in which account you are logged

On the call server

Remark Under mtcl or root (not for swinst)
Action who
Result [root@xa000001 /root]# who
root ttyS0 Jun 26 16:45 for root
Result (1)xa000001> who
mtcl ttyS0 Jun 26 16:48 for mtcl

P. 6 Ref. ENTP0495C01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

63
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

64
Alcatel-Lucent OmniPCX Enterprise

Start & Stop the System

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe how to stop and start the system

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

65
System startup
Cabinet switch over

Before to start the system, please check the followings:

The Call Server and the processing unit boards must be switched OFF

The interface boards must be in the slot defined in the site file

Switch the power on of the shelves

Connect the PC Com port to the OmniPCX Enterprise:

V24

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

66
Terminal startup
Run the terminal emulation on the P.C.

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

67
Terminal settings
Setup the terminal emulation on the P.C.

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

68
Terminal settings
Setup the terminal emulation on the P.C.

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

69
Terminal settings
Setup the terminal emulation on the P.C.

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

70
CPU-CS startup
Switch on the Call Server

Start up of the Call Server until the following system message appears:

No problem with compatibilities

Waiting time before viewing the message: between 5 or 10 minutes

according to the Call Server type.

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

71
System stopping

It is sometimes required to stop the Call Server for maintenance or initial

configuration purposes.

The Call Server operating system is based on Linux.

Directly switch off the Call Server may cause some disturbances to the
software.

It is mandatory to stop the system applications before switching off.

All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

72
Stopping the system by swinst

Console Login: mtcl

Password: mtcl
(1)xa00000> swinst, then choice: 1 - Easy menu

Alcatel-Lucent BUSINESS SYSTEMS

FACILITIES Easy menu Installation FACILITIES 2.50.0
1 Easy start
2 DECT registration
3 Save database
4 Restore database
5 Database re-init
6 Save OPS files
7 Restore OPS
8 Stop the telephone
9 Start the telephone
10 Set new internet address
11 Stop the system
Q Go back to previous menu

Your choice [1..11, Q] ? 11

All Rights Reserved © 2008, Alcatel-Lucent 9

As soon as all applications are stopped the following message is displayed:

The system is halted

Power down
Any key to reboot

It is then possible to:

- switch the CPU-CS off and unplug it from the back-panel
- restart the CPU-CS by pressing any key

Instead of using the swinst menu it is possible to use directly the on-line command:
shutdown –h now

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

73
System reset

2 reasons to reboot the Call Server:

to take some management into account
to stop the telephone application

When the Call Server restarts, it can run:

with telephone application: normal status of the Call Server
without telephone application: sometimes necessary to restore the database,
create a new database for example

All Rights Reserved © 2008, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

74
Restarting the system with telephone application

Console Login: mtcl

Password: mtcl
(1)xa00000> swinst, and then 1 - Easy menu

Alcatel-Lucent BUSINESS SYSTEMS

Your choice [1..11, Q] ? 9

All Rights Reserved © 2008, Alcatel-Lucent 11

* When starting the telephone via swinst menu, the automatic startup of the telephone is also validated for the next reboot.

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

75
Restarting the system without telephone application

Console Login: mtcl

Password: mtcl
(1)xa00000> swinst, and then 1 - Easy menu

Alcatel-Lucent BUSINESS SYSTEMS

Your choice [1..11, Q] ? 8

All Rights Reserved © 2008, Alcatel-Lucent 12

If the telephone is stopped via swinst then the automatic startup is also inhibited.
The telephone must be started again via swinst menu in order to activate again the automatic startup.

Alcatel-Lucent OmniPCX Enterprise – Start & Stop the System

Ref. ENTP0402P05TEUS Issue 02

76
Alcatel-Lucent OmniPCX Enterprise
System Start up

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to check the correct start-up of the system

MANAGEMENT

1. Realize and check the system cabling

1.1. Connect the PC COM1 port on the Communication Server V24 port

1.2. Check the different users connection on the interfaces in the racks according to the
information in the site file

1.3. Switch on the Communication Server

2. Check the system start up

2.1. Check the messages display on the PC screen

2.2. Wait about 5 minutes the telephone application start up

2.3. Check with the « Web Tool » the couplers start up

2.4. Do some tests on the telephone users

Issue 02 Ref. ENTP0402H01TEUS.doc HO. 1

HO. 2 Ref. ENTP0402H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

79
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

80
Alcatel-Lucent OmniPCX Enterprise

IP Environment

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the IP environment of the Alcatel-Lucent OmniPCX Enterprise

Alcatel-Lucent OmniPCX Enterprise – IP Environment

Ref. ENTP0457P10TEUS Issue 02

81
System IP addresses
Generalities

The Alcatel-Lucent OmniPCX Enterprise is more and more integrated in some IP

environments (IP customer networks)

The Alcatel-Lucent OmniPCX Enterprise architecture uses several different

devices interconnected via the IP network

The PC where is hosted the Alcatel-Lucent OmniVista 4760 application used

to configure the system and also used to check the system devices status

The Alcatel-Lucent OmniPCX Enterprise

The Com Server (mono CPU or duplicated)

The IP extensions (Alcatel-Lucent IP Touch 8 Series, SIP, H323)

The IP Media Gateways

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – IP Environment

Ref. ENTP0457P10TEUS Issue 02

82
System IP addresses
Used IP addresses

Each OmniPCX Enterprise device owns an IP address(1)

Com Server specific case

Mono-CPU configuration

An address is linked to the CPU physical interface (Ethernet)(2)

A second address can be managed to the “role MAIN status” of the system
Telephone application(3)

Duplicated configuration

An address is linked to each CPU physical interface (CPUa / CPUb)

An additional address has to be associated to the “role MAIN status” of the system
This “MAIN” address will have to be used by all the devices wanted to access to the system’s
MAIN(4)

All Rights Reserved © 2008, Alcatel-Lucent 3

(1) It is important that there is not IP conflict in the network, otherwise the devices could not exchange the signaling correctly
with Com Server (and therefore remain “out of service”)

(2) This address can be used to access to the Com Server, whatever the telephone application status (started or stopped)

(3) This second address will only be activated (and usable) from the moment that the Telephone application reaches the status “
MAIN”

(4) In case of a duplicated Com Server, (in normal situation) only one CPU uses the role “MAIN”, and the second one uses the role
“Stand-by”. All the services (Telephone and applications) are supported by the MAIN CPU! It is therefore mandatory that all
the IP devices and external applications use this (role) MAIN CPU address in order to access to the active Com Server CPU!

This example describe a classical duplication of the Com Server (both CPUs belongs to the same IP sub-network (the role MAIN
address as well)

It is possible that both CPUs belong to different IP sub-networks. In this particular case, two MAIN addresses have to be
managed. Only one is activated at a time. Only the CPU using the telephonic role “MAIN” status activates the MAIN role
address. The other CPU (stand-by) uses only its “physical” IP address

Alcatel-Lucent OmniPCX Enterprise – IP Environment

Ref. ENTP0457P10TEUS Issue 02

83
System IP addresses
Topology example

OmniVista 4760

Physical IP @: 151.10.1.1
Main IP @: 151.10.1.3

IP @: 140.21.2.50
Router

Router

IP
Network
IP @: 140.21.2.51

GD IP @: 151.10.1.4

IP @: 151.10.1.50

IP @: 151.10.1.51

All Rights Reserved © 2008, Alcatel-Lucent 4

Remark
All the IP devices have to know (in there IP configuration), their local router IP address in order to communicate with the IP
devices belonging to some other IP sub-networks

Alcatel-Lucent OmniPCX Enterprise – IP Environment

Ref. ENTP0457P10TEUS Issue 02

84
Alcatel-Lucent OmniPCX Enterprise
Modify the IP settings

PROCEDURE

OBJECTIVE

- To learn how to modify the IP address and the subnet mask of the Alcatel-Lucent OmniPCX
Enterprise.

Issue 02 Ref. ENTP0457C01TEUS.doc P. 1

PROCEDURE

1. Modify the IP address, the subnet mask and the PC address.

Note: The 3 values have to be provided by the customer

On the call server

Login mtcl
Password mtcl
(E)xa000000>
Result
Action netadmin
Warning: for a specific setup please use menu mode (netadmin -m).
Result Do you want to erase the existing setup (y/n default is 'n') ? y
Do you intend to use IP/X25 on your system (y/n default is 'n') ? n
Warning: the node name must be unique.
Enter node name (default is n) ?
Do you want to activate internal name resolver (y/n default is 'n') ?
Enter local CPU position (a or b) for duplicated configuration
or n for single CPU (default is 'n') ? n
Ethernet interface setup
========================
CPU name (default is xa000000) ? Site_Brest
The name you gave isn't in our hosts database. Do you want to add it and so
give the corresponding address (y/n default is 'n') ? y
CPU address ? 155.131.1.1
Network mask (default is 255.255.255.192) ? 255.255.255.0
Default router setup
====================
Do you use an external gateway as default router (y/n default is n) ? n or y
(1)
Please wait, working ...
The setup has been correctly achieved.
Security
=======
Do you want to enhance security (y/n, default is y) ?n
(E)xa000000>
(E)xa000000>exit
Action
(E)Site_Brest login :
Result

(1) Along our installation but if y

Default router name? Router

The name you gave isn’t in our hosts database. Do you want to add it and so give the
corresponding address (y/n default is ‘n’)? Y

Default router address? 155.131.1.254

P. 2 Ref. ENTP0457C01TEUS.doc Issue 02

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage the call server IP configuration

MANAGEMENT

1. Connect both Call Server and PC to the LANX board and use the v24 connection (PC-PCX)
for the following configuration steps

2. Use the netadmin command to manage the call server IP configuration as follows:

2.1. CPU name: xa00100X

2.2. CPU address: 10.S.X.1

2.3. Network mask: 255.255.255.0

2.4. Use an external gateway

2.5. Default router name: routerNTX

2.6. Default router address: 10.S.X.254

Note:
S = Classroom number
X = node number

3. Check this IP configuration via the “netadmin” tool as well as with the “ifconfig” command
(with the different available options)

4. Use the “ping” command to test the IP connection

Issue 02 Ref. ENTP0457H01TEUS.doc HO. 1

HO. 2 Ref. ENTP0457H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

89
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

90
Alcatel-Lucent OmniPCX Enterprise

Database management

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Database management

Alcatel-Lucent OmniPCX Enterprise – Database management

Ref. ENTP0411P03TEUS Issue 02

91
What is the database?

The database contains the customer’s configuration

The database is called MAO

Two tools are used for management

MGR
Alcatel-Lucent Expert Tool

Ethernet cable

@IP: 10.253.1.1
@IP: 10.253.1.10 V24 cable

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Database management

Ref. ENTP0411P03TEUS Issue 02

92
What can I do?

Create an empty database

Starting point of the configuration (necessary for a new installation)

Save & restore database

Save the database consists in copying from the Alcatel-Lucent OmniPCX

Enterprise the customer’s configuration to a PC(1)

Restore the database consists in sending from a PC the customer’s

configuration to the Alcatel-Lucent OmniPCX Enterprise(2)

All Rights Reserved © 2008, Alcatel-Lucent 3

(1) With the Alcatel-Lucent Expert Tool just on step, else in two steps with the using of swinst and one FTP session (See
procedures)
(2) The Alcatel Expert Tool can only transfer the database backup by a ftp session but restoring has to be done over swinst

Alcatel-Lucent OmniPCX Enterprise – Database management

Ref. ENTP0411P03TEUS Issue 02

93
All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Database management

Ref. ENTP0411P03TEUS Issue 02

94
Alcatel-Lucent OmniPCX Enterprise
Empty Database creation

PROCEDURE

OBJECTIVE

- To learn how to create an empty database

OVERVIEW
This operation overwrites the existing database and the lock files. It can only be performed if
the telephone application is stopped.
Note: Creation of a new database may take time. Restart the Call Server after this
operation (and before restarting the telephone).
(All the following actions have to be realized on the Call Server)

Issue 04 Ref. ENTP0411C01TEUS.doc P. 1

PROCEDURE

1. Swinst

Login swinst
Password SoftInst
Select 1. Easy Menu
7. stop the telephone
Entry Please confirm to stop the telephone (y/n, default y): ENTER

2. Wait for the call server start-up

xa001001 login:

3. Swinst

Login Swinst
Password SoftInst
Select 2. Expert Menu
7. Database tools
2. Create an empty database
Entry Create empty data base (Y/N Q to quit): Y
Please confirm removing the database .(Y/N) Y
Enter your country in capital letter: US
Do you want to create all the data base (Y/N) ? Y
Value to modify (0 = Exit) : 0

4. Restart the telephone

Login Swinst
PassWord SoftInst
Select 1. Easy Menu
8. start the telephone
Entry Please confirm to start the telephone (y/n, default y): ENTER

P. 2 Ref. ENTP0411C01TEUS.doc Issue 04

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to create an empty database

MANAGEMENT

1. Check the connection between the Call server and the PC

2. Create an Empty database

3. Select the country (“US” for USA, or “FR” for France)

Issue 02 Ref. ENTP0411H03TEUS.doc HO. 1

HO. 2 Ref. ENTP0411H03TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

99
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

100
Alcatel-Lucent OmniPCX Enterprise

Licenses and OPS files

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVES

To describe the principle of e-licensing and e-commerce

To describe the role of the different OPS files

Alcatel-Lucent OmniPCX Enterprise – Licenses and OPS files

Ref. ENTP0412P09TEUS Issue 02

101
Licenses and OPS files
Overview

The system of licenses allows to

Supply an unique installation medium independently from the applications

bought by each customer

Avoid the risks of fraudulent use of the software

Define a commercial policy fitting with:

The customer needs
The market constraints

It is based on two distinct elements

The licenses file

The software locks controlled by the Call Server

All Rights Reserved © 2008, Alcatel-Lucent 2

OPS: Offer Preparing System

Alcatel-Lucent OmniPCX Enterprise – Licenses and OPS files

Ref. ENTP0412P09TEUS Issue 02

102
Licenses and OPS files
Definitions

The Call Server features and applications are controlled by hardware and/or
software keys

Each system is uniquely identified

This reference is stored:

In the PROM for each CPU board (CPU-Id)

It is the case for the CPU-CS, the Appliance Servers and the new CPU5/6/7 boards

In a hardware PAL-key plugged on the CPU5 or CPU6 boards

This hardware key was used before in the software protection system of the OmniPCX 4400
It is still compatible in case of a migration to OmniPCX Enterprise

All Rights Reserved © 2008, Alcatel-Lucent 3

PROM: Programmable Read Only Memory

PAL: Programmable Array Logic

If the system is duplicated, there are whether 2 CPU-Id, whether 2 hard key numbers in the license file.

Alcatel-Lucent OmniPCX Enterprise – Licenses and OPS files

Ref. ENTP0412P09TEUS Issue 02

103
Licenses and OPS files
Definitions

The system identifier (CPU-Id) is encrypted in the license file and supplies the
software key

System ID

CPU ID or
License file Software key
hardware key

The software keys are ordered through eCom and/or the software Actis or
ExpressQuote

Hardware and software can be ordered separately

All Rights Reserved © 2008, Alcatel-Lucent 4

eCom: Alcatel-Lucent Internet server dedicated to receive orders for licenses and hardware
ACTIS: Alcatel-Lucent Configuration Tool for International Sales
Configuration and costing software used to calculate complex offers for OmniPCX Office, OmniPCX 4400 and OmniPCX
Enterprise
ExpressQuote: Quick costing tool for OmniPCX Office and OmniPCX Enterprise (up to IPMG 250)
Available in 3 versions:
A paper version
An electronic offline version
An electronic online version (Website)

The license file contains the listing of the software locks open in the Call Server software, the listing of the CPU identifiers (CPU-
Id), miscellaneous technical information and a software key.
This key is generated from information contained in the file and from a secrete key.
It is impossible to modify the licenses in this file because the software key wouldn’t correspond anymore.

Alcatel-Lucent OmniPCX Enterprise – Licenses and OPS files

Ref. ENTP0412P09TEUS Issue 02

104
Licenses and OPS files
Software protection

Control of the licenses

In normal working mode, the Call Server checks every 4 hours the coherency
of the protection elements

It checks the coherency of the management data comparing to the features

bought by the customer
In case of inconsistency, the system switches to degraded mode

It checks that the CPU-Id matches the data in the licenses file
In case of inconsistency, the system first considers that it is an maintenance
operation
After 30 days, the system switches to degraded mode

All Rights Reserved © 2008, Alcatel-Lucent 5

The coherency can be checked using the command spadmin.

Menu 1 (Display current counters), look at the state of the « Panic Flag »(0 = OK, 1 = NOK).

Alcatel-Lucent OmniPCX Enterprise – Licenses and OPS files

Ref. ENTP0412P09TEUS Issue 02

105
Licenses OPS files
Software protection

Risks in case of fraud

Legal Risks

The software replication or the unlocking of features without authorization is an

illegal operation

Offenders will be liable to prosecution.

Functional Risks

When the Call Server software detects an incoherency between the different keys
or with the features, it switches to the degraded mode and triggers some actions

All Rights Reserved © 2008, Alcatel-Lucent 6

System behavior in degraded mode:

action 1 (as soon as detected)

• display a warning to the attendant (acknowledge mandatory) as soon as she’s free.
• erase the terminal screen and display the incident message
• the incident is stored in the incidents file
• continuous ring on the alarm set
• some management commands are locked and just give the error: “Software protection error"
action 2 (4 hours later):
• display the message « Please call your administrator » on every set with screen
action 3 (8 hours later):
• Loop back on actions 1 et 2

Alcatel-Lucent OmniPCX Enterprise – Licenses and OPS files

Ref. ENTP0412P09TEUS Issue 02

106
Licenses and OPS files
Replacement of a CPU board

If a CPU board is replaced, the software key stored on the Call Server is not
valid anymore

The CPU_Id of this new board is different

The system can still work for 30 days

After these 30 days, the system will switch to the degraded mode

A new key has to be loaded on the system to recover a normal working mode

This key can be downloaded through the e-Com server (Business Partner Web
Site)

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – Licenses and OPS files

Ref. ENTP0412P09TEUS Issue 02

107
Licenses and OPS files
Replacement of a CPU board

Replacement modes of a CPU board

Case 1
The technician registers the CPU change before the Hardware Support received the
defective CPU board
Standard Service

Case 2
The technician registers the CPU change after the Hardware Support received the
defective CPU board
Standard Service

Case 3
The Hardware Support registers the CPU board change and reception
Plug and Play Service

All Rights Reserved © 2008, Alcatel-Lucent 8

Operating modes depending on the case

Case 1
The technician replaces the defective CPU board by the new one and registers the exchange on the e-Com website (Business
Partner Web Site)
The technician sends the defective CPU board to the Hardware Support
The Hardware Support receives the defective CPU board and register the reception on the eLP (e-Licensing Product) website
The technician downloads the keys from the e-Com website and installs it on the customer’s system

Case 2
The technician sends the defective CPU board to the Hardware Support. At reception, the Hardware Support registers it on
the eLP website
The technician receives a new CPU board and install it on the customer’s system
The technician gives the two CPU numbers on the e-Com website and downloads the licenses. Then, he installs the licenses
on the customer’s system.

Case 3
Everything is done by the Hardware Support: registration of the change (through eLP) at the reception of the defective board
and license management for the customer

The working mode depends on the support contract of the customer.

Alcatel-Lucent OmniPCX Enterprise – Licenses and OPS files

Ref. ENTP0412P09TEUS Issue 02

108
Alcatel-Lucent OmniPCX Enterprise

Backup and Restore the OPS files via FTP

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the OPS

Alcatel-Lucent OmniPCX Enterprise – OPS

Ref. ENTP0412P11TEUS Issue 02

109
OPS
Overview

The OPS control the rights at the system level

They are composed of 4 or 5 files

hardware.mao
xx.swk
xx.hw
xx.ZIP
xx.sw4760 (optional if using of Alcatel-Lucent OmniVista 4760)

All Rights Reserved © 2008, Alcatel-Lucent 2

xx corresponds to the customers id

Alcatel-Lucent OmniPCX Enterprise – OPS

Ref. ENTP0412P11TEUS Issue 02

110
OPS
Restore

1st step: OPS files are copied in one specific folder on the Call Server
/usr4/BACKUP/OPS/

2nd step: OPS files are installed in the folder /usr3/mao/

You must find in this folder those two files:

hardware.mao
software.mao (created from xx.swk)

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – OPS

Ref. ENTP0412P11TEUS Issue 02

111
OPS
Restore

To install the OPS, you have two choices:

Ftp session + swinst

Copy OPS files from the PC to /usr4/BACKUP/OPS and install them with swinst

Alcatel-Lucent Expert Tool

Copy and install the OPS files in one time

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – OPS

Ref. ENTP0412P11TEUS Issue 02

112
OPS
Backup

1st case:
OPS files are installed by default in /usr4/BACKUP/OPS/, the only thing to do
is to copy them in your PC with a ftp session

2nd case:
OPS files are not in /usr4/BACKUP/OPS/, so you have to do a backup from
/usr3/mao/ to /usr4/BACKUP/OPS/ and make a ftp session to copy them on
to your PC

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – OPS

Ref. ENTP0412P11TEUS Issue 02

113
OPS
Backup

To backup the OPS, you have two choices:

swinst + ftp session

Copy OPS files from /usr3/mao/ to /usr4/BACKUP/OPS with swinst and make a ftp
session to copy them to your PC

Alcatel-Lucent Expert Tool

Copy OPS files from /usr3/mao/ to your PC (by passing to /usr4/BACKUP/OPS/
automatically)

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – OPS

Ref. ENTP0412P11TEUS Issue 02

114
Alcatel-Lucent OmniPCX Enterprise
Save and restore licenses

PROCEDURE

OBJECTIVE

- To learn how to save and restore licenses

OVERVIEW
The system of licenses and locks allows you to sell the customer only the features that he needs.
The reason is: the Call Server's software program is unique and contains all the functions
available on the OmniPCX Enterprise. Under these conditions, it would be unfair to charge
customers for features they do not use.
For each system, the licenses (or OPS) are created with the Id of the CPU and the services needs
by the customer. These licenses are unique.
When you receive a new system the licenses are already installed.

Issue 04 Ref. ENTP0412C01TEUS.doc P. 1

PROCEDURE

1. Save licenses

1.1. On the Call Server disk

On the call server

Login swinst
Password SoftInst
ALCATEL BUSINESS SYSTEMS
Result
FACILITIES Main menu Installation FACILITIES 2.50.0
1 Easy menu
2 Expert menu
Q Exit
Your choice [1..2, Q] ?

Enter 2
ALCATEL BUSINESS SYSTEMS
Result
FACILITIES Expert menu Installation FACILITIES 2.50.0
1 Packages installation
2 Deliveries installation
3 Cloning & duplicate operations
4 Backup & restore operations
5 OPS configuration
6 System management
7 Database tools
8 Software identity display
9 Remote download
Q Go back to previous menu
Your choice [1..9, Q] ?

Enter 5
ALCATEL BUSINESS SYSTEMS
Result
OPS management menu Installation FACILITIES 2.50.0
1 Backup OPS files on cpu disk
2 Restore OPS from cpu disk
3 OPS administration
4 Software protection recover
5 Backup OPS files on a DOS floppy
6 Restore OPS from a DOS floppy
7 View a DOS floppy disk
8 Format a DOS floppy disk
Q Go back to previous menu
Your choice [1..8, Q]

P. 2 Ref. ENTP0412C01TEUS.doc Issue 04

Enter 1
Result Confirm the backup of OPS files on your cpu disk (y/n, default y):y
ops 2.0.2: operation successful
Result
Updating hardware.mao according to data base ok
Copying software.mao into fr02901a.swk
Copying hardware.mao into fr02901a.hw
Copying fr02901a.sw4760
Copying fr02901a.zip
Copying hardware.mao
Copying hardware.old
Creating ops.lis
Press return

Note: The OPS files are stored under /DHS3dyn/BACKUP/OPS

(the partition DHS3dyn corresponds to usr4)

1.2. Transfer the files from the Call Server disk to a PC

On Command prompt
Action On your PC: Start / Run… on the field Open enter “cmd”
Create a specific folder to save your OPS (eg: backup)
Enter C:\> mkdir backup
C:\> cd backup
Note: All files will be saved on this folder
Enter C:\backup>ftp 155.132.1.1
Connected to 155.132.1.1.
Result
220 xa0001001 FTP server (Version wu-2.6.1(1) Wed Feb 28 15:50:32
User (155.132.1.1: (none)): mtcl
Enter
331 Password required for mtcl.
Password: mtcl

Result 230 User mtcl logged in.

Note: Use the ftp connection to save OPS files on your PC (155.132.1.1 = CPU IP@)
Use the “mtc”l login and pass for the ftp connection
Enter ftp> bin
Result 200 Type set to I.
Note: The command “bin” is used to transfer the data in binaries and not in ASCII
Enter ftp> cd /usr4/BACKUP/OPS
Result 250 CWD command successful.
Note: Go to this specific folder to get the OPS files

Issue 04 Ref. ENTP0412C01TEUS.doc P. 3

Enter ftp> get hardware.mao

200 PORT command successful.
Result
150 Opening BINARY mode data connection for hardware.mao (3308 bytes).
226 Transfer complete
ftp: 3308 bytes received in 0.00Seconds 3308000.00Kbytes/sec.

Note: Save the file hardware.mao under c:\backup>

ftp> get fr02901a.swk
200 PORT command successful.
Result
150 Opening BINARY mode data connection for fr02901a.swk (9539 bytes).
226 Transfer complete
ftp: 9539 bytes received in 0.40Seconds 23.79Kbytes/sec.

Note: Save the file fr02901a.swk under c:\backup>

Enter ftp> get fr02901a.hw
200 PORT command successful.
Result
150 Opening BINARY mode data connection for fr02901a.hw (3308 bytes).
226 Transfer complete
ftp: 3308 bytes received in 0.00Seconds 3308000.00Kbytes/sec.

Note: Save the file fr02901a.hw under c:\backup>

Enter ftp> get fr02901a.zip
200 PORT command successful.
Result
150 Opening BINARY mode data connection for fr02901a.zip (13848 bytes).
226 Transfer complete
ftp: 13848 bytes received in 0.00Seconds 13848000.00Kbytes/sec

Note: Save the file fr02901a.zip under c:\backup>

Enter ftp> get fr02901a.sw4760
200 PORT command successful.
Result
150 Opening BINARY mode data connection for fr02901a.swk (9539 bytes).
226 Transfer complete
ftp: 9539 bytes received in 0.40Seconds 23.79Kbytes/sec

Note: Save the file fr02901a.sw4760 under c:\backup>

The name of OPS (fr02901a) depends of the customer, for each system the name is
different.
It is also possible to use the command “mget *” and answer “y” to the expected
files
The FTP server will ask you, for all the files existing in the connected directory, if
you want to download the different files (file by file)

P. 4 Ref. ENTP0412C01TEUS.doc Issue 04

2. Restore licenses

2.1. Transfer the OPS files from a PC to the Call Server disk

On Command prompt
Action On your PC: Start / Run… on the field Open enter “cmd”
Note: OPS are saved in a folder called “backup” for this example
Enter C:\> cd backup
C:\backup> ftp 155.132.1.1
Connected to 155.132.1.1.
Result
220 xa0001001 FTP server (Version wu-2.6.1(1) Wed Feb 28 15:50:32
User (155.132.1.1: (none)): mtcl
Enter
331 Password required for mtcl.
Password: mtcl
230 User mtcl logged in.
Result
Note: Use the ftp connection to send OPS files on the cpu disk (155.132.1.1 = cpu IP@)
Use the mtcl login and pass for the ftp connection
Enter ftp> bin
Result 200 Type set to I.

Note: The command “bin” is used to transfer the data in binaries and not in ASCII
Enter ftp> cd /usr4/BACKUP/OPS
Result 250 CWD command successful.

Note: Go to this specific folder to get the OPS files

Enter ftp> send hardware.mao hardware.mao
200 PORT command successful.
Result
150 Opening BINARY mode data connection for hardware.mao (3308 bytes).
226 Transfer complete
ftp: 3308 bytes received in 0.00Seconds 3308000.00Kbytes/sec.

Note: hardware.mao is written twice to keep the good file spelling under
/usr4/BACKUP/OPS (No cap letters)
Enter ftp> send fr02901a.swk fr02901a.swk
200 PORT command successful.
Result
150 Opening BINARY mode data connection for fr02901a.swk (9539 bytes).
226 Transfer complete
ftp: 9539 bytes received in 0.40Seconds 23.79Kbytes/sec.

Note: fr02901a.swk is written twice to keep the good file spelling under
/usr4/BACKUP/OPS (No cap letters)

Issue 04 Ref. ENTP0412C01TEUS.doc P. 5

Enter ftp> send fr02901a.hw fr02901a.hw

200 PORT command successful.
Result
150 Opening BINARY mode data connection for fr02901a.hw (3308 bytes).
226 Transfer complete
ftp: 3308 bytes received in 0.00Seconds 3308000.00Kbytes/sec.

Note: fr02901a.hw is written twice to keep the good file spelling under
/usr4/BACKUP/OPS (No cap letters)
Enter ftp> send fr02901a.zip fr02901a.zip
200 PORT command successful.
Result
150 Opening BINARY mode data connection for fr02901a.zip (13848 bytes).
226 Transfer complete
ftp: 13848 bytes received in 0.00Seconds 13848000.00Kbytes/sec

Note: fr02901a.zip is written twice to keep the good file spelling under
/usr4/BACKUP/OPS (No cap letters)
Enter ftp> send fr02901a.sw4760 fr02901a.sw4760
200 PORT command successful.
Result
150 Opening BINARY mode data connection for fr02901a.swk (9539 bytes).
226 Transfer complete
ftp: 9539 bytes received in 0.40Seconds 23.79Kbytes/sec

Note: fr02901a.sw4760 is written twice to keep the good file spelling under
/usr4/BACKUP/OPS (No cap letters)
See the chapter 2.1 to install this OPS files on the system
Note: It is also possible to use a unique command to transfer all the files: “mput *”. For
each file existing in the connected directory (PC side), it will be asked if you want
to transfer the files (file by file)

P. 6 Ref. ENTP0412C01TEUS.doc Issue 04

2.2. Install the files from the Call Server disk

On the call server

Login swinst
Password SoftInst
ALCATEL BUSINESS SYSTEMS
Result
FACILITIES Main menu Installation FACILITIES 2.50.0
1 Easy menu
2 Expert menu
Q Exit
Your choice [1..2, Q] ?

Enter 2

Issue 04 Ref. ENTP0412C01TEUS.doc P. 7

You are going to restore these OPS files from cpu disk
Result
fr02901a hw 3308 Feb 23 14:39
fr02901a sw4760 496 Feb 23 14:39
fr02901a swk 9539 Feb 23 14:39
fr02901a zip 13848 Feb 23 14:39
hardware mao 3308 Feb 23 14:39
hardware old 3308 Feb 23 14:39
Confirm your action (y/n, default y): y
Duplicating fr02901a.swk into software.new
ooo Reading string-file /DHS3bin/oneshot/mtcl/objects.US0 ...
ooo Reading string-file /DHS3bin/oneshot/mtcl/spadmin.dct ...
DLL version = 0110 DLL version = 0110
File version = 0 File version = 0
OXE version = 0110 OXE version = 0110
Soft Key=f069fe45f019340e124e Soft Key=f069fe45f019340e124e
Cpu Id 0 = 0000CC7F Cpu Id 0 = 0000CC7F
Your System CPU-Id: 0000CC7F Your System CPU-Id: 0000CC7F
System CPU-Id found System CPU-Id found
Handle 4760 = 123456AB Handle 4760 = 123456AB
Timestamp: Timestamp:
Thu Feb 12 15:36:34 2006 Thu Feb 12 15:36:34 2006
h/Help q/Quit, Lines 1-23/202 (0%)

Note: During this stage, press the “space bar” to see the scroll down of the different
services open with your OPS or press “q” to quit this phase
Do you agree the new software keys (y/n): y
Result
ooo Reading string-file /DHS3bin/oneshot/mtcl/objects.US0 ...
ooo Reading string-file /DHS3bin/oneshot/mtcl/spadmin.dct ...
Version 0 -> Version 0
Copying fr02901a.hw
Copying fr02901a.sw4760
Copying fr02901a.swk
Copying fr02901a.zip
Copying hardware.mao
Enter OPS working mode: 1=running 2=simulate (default is 1) 1
# MGR script generated
# History-file OPS.dat updated
# Running MGR
ooo Starting at <23/02/06 16:42> ...
ooo Compiling Command file "/tmpd/MGRYZODda" ...
ooo Job completed. at <23/02/06 16:42> ...
ops 2.0.2: operation successful
Tables updated. You must reboot your system
Press return

Note: OPS are now installed on the system

P. 8 Ref. ENTP0412C01TEUS.doc Issue 04

3. Check the OPS files

On the call server (use the command “spadmin” or the following menu)
Login swinst
Password SoftInst
ALCATEL BUSINESS SYSTEMS
Result
FACILITIES Main menu Installation FACILITIES 2.50.0
1 Easy menu
2 Expert menu
Q Exit
Your choice [1..2, Q] ?

Enter 5
ALCATEL BUSINESS SYSTEMS
OPS management menu Installation FACILITIES 2.50.0
1 Backup OPS files on cpu disk
2 Restore OPS from cpu disk
3 OPS administration
4 Software protection recover
5 Backup OPS files on a DOS floppy
6 Restore OPS from a DOS floppy
7 View a DOS floppy disk
8 Format a DOS floppy disk
Q Go back to previous menu
Your choice [1..8, Q]

Enter 3
OPS administration
Note: This "swinst" menu is identical to the "spadmin" maintenance command

Issue 04 Ref. ENTP0412C01TEUS.doc P. 9

ooo Reading string-file/DHS3bin/oneshot/mtcl/objects.US0

Result
ooo Reading string-file/DHS3bin/oneshot/mtcl/spadmin.dct
Display current counters .......................... 1
Display active file .................……………..………………..2
Check active file coherency ..................……….. 3
Install a new file ................................ 4
Read the system CPUID ...................…......... 5
CPU-Ids management ............…………...............… 6
Display active and new file ....................... 7
Display OPS limits .............................….. 8
Display ACK code .................................… 9
Exit ........................................………... 0
choice:

Select Choice 1: Display current counters

(SP) Software Protection counters:
Result
PANIC Flag : 0
Group Telephony Counter : 0
Call By Name Counter : 9
…

Note: The "Panic Flag" indicates that an inconsistency has been detected in the OPS files
and that the degraded mode procedures of the system are activated:
- PANIC Flag = 0 normal operation
- PANIC Flag = 1 operation in degraded mode
- List of the counters corresponding to each one of the locks
Select Choice 2: Display active file
Cpu Id 01 = 0000CC7F
Result
Your System CPU-Id: 0000CC7F
System CPU-Id found
Handle 4760 = 123456AB
Timestamp:
Thu Feb 12 15:36:34 2009

Note: Check the presence of the CPU id for this OPS files
Select Choice 3: Check active file coherency
> Checking active file /DHS3data/mao/software.mao
Result
File OK

Note: Check if the software.mao file is activated or not

Select Choice 4: Check active file coherency
> Checking active file /DHS3data/mao/software.mao
Result
File OK

Note: Check if the software.mao file is activated or not

Select Choice 4: Install a new file
Note: Installation of the OPS files from the cpu disk (See chapter 1.1)

P. 10 Ref. ENTP0412C01TEUS.doc Issue 04

Select Choice 5: Read the system CPUID

Result Your System CPU-Id: 0000CC7F

Note: Read the cpu id of the system

Select Choice 6: CPU-Ids management
Spadmin: CPU-Ids management
Result
---------------------------
Add CPU-Ids .....................................…. 1
Remove CPU-Ids .................................... 2
Update a CPU-Id ................................... 3
Back to previous ................................…. 0

Note: This command allows an installation technician to carry out an on-site Call Server
add-on or Call Server exchange
The tool requests the Call Server number(s) as well as the new software key from
the operator. The action is performed only if the new software key is consistent
Select Choice 7: Display active and new file
Note: This command displays in two columns the contents of the current file and of the
file to be installed
Select Choice 8: Display OPS limits
OPS limits
Result
Remanent size (Kb) = 12500
Number of stations = 512
Number of trunks = 512
Number of half-contexts = 512
Stand-alone = 0
Number of BLF = 1

Note: Display the limits given by the OPS (“PARAMO” from the hardware.mao file)
Select Choice 9: Display ACK code
Code: 0cb0
Result
Note: This command displays the acknowledgement code. The acknowledgement code is
used for transferring licenses.

Issue 04 Ref. ENTP0412C01TEUS.doc P. 11

P. 12 Ref. ENTP0412C01TEUS.doc Issue 04

PROCEDURE

OBJECTIVE

- To learn how to save and restore licenses with Alcatel-Lucent Expert Tool

OVERVIEW
The system of licenses and locks allows you to sell the customer only the features that he needs.
This is because the Call Server's software program is unique and contains all the functions
available on the OmniPCX Enterprise. Under these conditions, it would be unfair to charge
customers for features they do not use.
For each system, the licenses (or OPS) are created with the CPU-Id and the services needs by the
customer. These licenses are unique.
When you receive a new system the licenses are already installed.

Issue 04 Ref. ENTP0412C02TEUS.doc P. 1

PROCEDURE

1. Save OPS on the user’s hard disk

Application Expert tool

Action Open Internet explorer
Entry https://IP@ of the CS
Select Maintenance
Login mtcl
Action Double click on “Save OPS”
Action Click on “Search…”
Action Select the desired backup destination
Action Click on the green mark to validate

Note: The local backup directory is structured as follows:\User path\ops\”PCX

name”\”backup date”
When “Disconnected” is displayed on the data field, the backup is complete

2. Restore OPS from the user’s hard disk

Application Expert tool

Action Open Internet explorer
Entry https://IP@ of the CS
Select Maintenance
Login mtcl
Action Double click on “Restore OPS”
Action Select one or several files in the left selection of the window
Action Click on the left arrow to confirm
Action Click on the green mark to validate

Note: The files selected are the same than the files saved during the backup phase
(select these all files)
To deselect a file click on the left arrow

P. 2 Ref. ENTP0412C02TEUS.doc Issue 04

3. Check the OPS files

Application On mtcl
Login swinst > Expert menu > OPS configuration > OPS administration
Select 2. Expert menu
5. OPS Configuration
3. OPS Administration

Note: This "swinst" menu is identical to the "spadmin" maintenance command

ooo Reading string-file /DHS3bin/oneshot/mtcl/objects.US0 ...
Result
ooo Reading string-file /DHS3bin/oneshot/mtcl/spadmin.dct ...
Display current counters ........................... 1
Display active file ..............................…… 2
Check active file coherency ..................…. 3
Install a new file ...............................……. 4
Read the system CPUID ............................ 5
CPU-Ids management ...........................… 6
Display active and new file ........................ 7
Display OPS limits ...............................….. 8
Display ACK code .................................… 9
Exit .............................................………... 0
choice:

Action Choice 1: Display current counters

(SP) Software Protection counters:
Result
PANIC Flag : 0
Group Telephony Counter : 0
Call By Name Counter : 9

Action Choice 2: Display active file

Cpu Id 01 = 0000CC7F
Result
Your System CPU-Id: 0000CC7F
System CPU-Id found
Handle 4760 = 123456AB
Timestamp:
Thu Feb 12 15:36:34 2004

Note: Check the presence of the CPU id for this OPS files

Issue 04 Ref. ENTP0412C02TEUS.doc P. 3

Action Choice 3: Check active file coherency

> Checking active file /DHS3data/mao/software.mao
Result
File OK

Note: Check if the software.mao file is activated or not

Action Choice 4: Check active file coherency

> Checking active file /DHS3data/mao/software.mao
Result
File OK

Note: Check if the software.mao file is activated or not

Action Choice 4: Install a new file

Note: Installation of the OPS files from the cpu disk (See chapter 1.1)

Action Choice 5: Read the system CPUID

Your System CPU-Id: 0000CC7F
Result

Note: Read the cpu id of the system

Action Choice 6: CPU-Ids management

Spadmin: CPU-Ids management
Result
---------------------------
Add CPU-Ids ......................................…. 1
Remove CPU-Ids ..................................... 2
Update a CPU-Id .................................... 3
Back to previous .................................…. 0
choice:

Action Choice 7: Display active and new file

Note: This command displays in two columns the contents of the current file and of the
file to be installed

P. 4 Ref. ENTP0412C02TEUS.doc Issue 04

Action Choice 8: Display OPS limits

OPS limits
Result
Remanent size (Kb) = 12500
Number of stations = 512
Number of trunks = 512
Number of half-contexts = 512
Stand-alone = 0
Number of BLF = 1
…

Note: Display the limits given by the OPS

Action Choice 9: Display ACK code

Result Code: 0cb0

Note: This command displays the acknowledgement code. The acknowledgement code is
used for transferring licenses

Issue 04 Ref. ENTP0412C02TEUS.doc P. 5

P. 6 Ref. ENTP0412C02TEUS.doc Issue 04

All Rights Reserved © 2005, Alcatel-Lucent
132
Alcatel-Lucent OmniPCX Enterprise
Download and installation of OPS files via FTP

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to download OPS files via FTP

MANAGEMENT

1. Check the connection between the PC and the call server.

2. Transfer the four OPS files from the PC to the call server via FTP.

3. Install these OPS files with swinst

4. Start or restart the telephone application.

Issue 02 Ref. ENTP0412H03TEUS.doc HO. 1

All Rights Reserved © 2008, Alcatel-Lucent
133
Alcatel-Lucent OmniPCX Enterprise
Download and installation of OPS files via FTP

HO. 2 Ref. ENTP0412H03TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

135
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

136
Alcatel-Lucent OmniPCX Enterprise

MGR configuration tool

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe mgr configuration tool

Alcatel-Lucent OmniPCX Enterprise – MGR configuration tool

Ref. ENTP0413P02TEUS Issue 02

137
What is MGR?

mgr is one of the management tool

It is integrated in the Communication Server

Used for the management of the database

Shelves, boards, users, etc…

This tool is working in text mode

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – MGR configuration tool

Ref. ENTP0413P02TEUS Issue 02

138
How to access?

By V24 or Ethernet connection (1)

Under the “mtcl” account

By running the command “mgr -l XXX” (2)

All Rights Reserved © 2008, Alcatel-Lucent 3

(1) Ethernet connection: connection over a telnet session

(2) XXX is the language used by mgr (e.g.: US0 for English)

Alcatel-Lucent OmniPCX Enterprise – MGR configuration tool

Ref. ENTP0413P02TEUS Issue 02

139
MGR menu

-> Shelf Specific telephone services

Media Gateway Atm
PWT/DECT system Events routing discriminator
System Security and Access control
Translator IP
Classes of service SIP
Attendant DHCP Configuration
Users Alcatel 8&9 Series
Users by Profile SIP Extension
Set profile Encryption
Groups Passive Com. Server
Speed dialing SNMP Configuration
Phone book
Entities
Trunk groups
External services
Inter-Node links
X25
DATA
Applications

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – MGR configuration tool

Ref. ENTP0413P02TEUS Issue 02

140
Alcatel-Lucent OmniPCX Enterprise
MGR configuration tool

PROCEDURE

OBJECTIVE

- To learn how to access mgr and modify one user parameter

OVERVIEW
Become familiar with navigating the system configuration using mgr (manager) application. This
application is contained in the Alcatel OmniPCX enterprise system software. It allows creation,
deletion, and modification of all components and services within the Alcatel OmniPCX
enterprise.
Note: Manager (mgr) is a menu application allowing the administrator to create, modify
and view configuration parameters. Only one manager instance should be started
at one time.

Issue 02 Ref. ENTP0413C01TEUS.doc P. 1

PROCEDURE

1. Access to MGR

1.1. mgr command

On the call server

Login mtcl
Password mtcl
Entry mgr –l US0 (have to be done only once and stay in this language until
a new change)
Note: -l allows the language selection:
- DE0: German for Germany
- DE1: German for Austria
- IT0: Italian for Italy
- NL1: Dutch for Belgium
- GEA: Generic English of Alcatel
- US0: English for US
- FR0: French for France
- EN0: English for England
(Have to be done only once and stay in this language until a new change)
-> Shelf Specific telephone services
Result
Media Gateway Atm
PWT/DECT system Events routing discriminator
System Security and Access control
Translator IP
Classes of service SIP
Attendant DHCP Configuration
Users Alcatel 8&9 Series
Users by Profile SIP Extension
Set profile Encryption
Groups Passive Com. Server
Speed dialing SNMP Configuration
Phone book
Entities
Trunk groups
External services
Inter-Node links
X25
DATA
Applications

P. 2 Ref. ENTP0413C01TEUS.doc Issue 02

1.1.1. Use of Function Keys

To select a line in a selection menu arrow keys or text strings can be used
To move to the next instance of the text string press CTRL+N
To move to the previous instance of the text string press CTRL+P
To delete a text string press CTRL+K
To confirm input/modification press CTRL+V or F1
To cancel or Return to previous menu press CTRL+C or F2
To refresh the screen press CTRL+W
To access help (context-sensitive) press CTRL+I
To scroll to next or previous page press CTRL+F or CTRL+B
To move cursor to first or last position type CTRL+A or CTRL+E
Pour ouvrir une autre fenêtre ou basculer vers une autre fenêtre CTRL O
Quit Manager by using CTRL+C or F2

Issue 02 Ref. ENTP0413C01TEUS.doc P. 3

2. Example of using

On the call server under the mtcl account

Action Launch the command “mgr”
Action Select the “Users” object with the arrows
Shelf Specific telephone services
Result
Media Gateway Atm
PWT/DECT system Events routing discriminator
System Security and Access control
Translator IP
Classes of service SIP
Attendant DHCP Configuration
->Users Alcatel 8&9 Series
Users by Profile SIP Extension
Set profile Encryption
Groups Passive Com. Server
Speed dialing SNMP Configuration
Phone book
Entities
Trunk groups
External services
Inter-Node links
X25
DATA
Applications

Action Press “Enter” when “Users” is selected

Descend Hierarchy
Result
Review/Modify
Review/Modify object profile
Create
Create Object limit(s)
Modify
Modify Object limit(s)
Delete
FORCED DELETE
Memory re-initialization
Features

Action Select the “Review/Modify” object with the arrows en press “Enter”
Review/Modify: Users
Result
[ All instances ]
[ Set filters ]
[Select attributes]
Node number (Reserved) : 1
Directory number : -------

P. 4 Ref. ENTP0413C01TEUS.doc Issue 02

Action When the cursor it’s on “All instances” press “Enter“ and press CTRL+V or
F1 to validate
[4]Instances Users
Result
-> 31000
31019
31029
31100
31101
31666
31900
31901
33000

Action Select the user 31000 and press “Enter”

Review/Modify : Users
Result
Node number (reserved) : 1
Directory number : 31000
Directory name : DUPONT
Directory first name : Elvis
Location node : 1
Shelf address : 1
Board address : 1
Equipment address : 1
Set type + 4039
Entity number : 1
Language Id : 1
Secret code : ****

Action Move the cursor to “Directory First name”, delete and replace it by “John”
and press CTRL+V or F1

Issue 02 Ref. ENTP0413C01TEUS.doc P. 5

P. 6 Ref. ENTP0413C01TEUS.doc Issue 02

PROCEDURE

OBJECTIVE

- To learn how to access mgr and modify 4760I

OVERVIEW
Become familiar with navigating the system configuration using mgr (manager) application. This
application is contained in the Alcatel-Lucent OmniPCX enterprise system software. It allows
creation, deletion, and modification of all components and services within the Alcatel-Lucent
OmniPCX enterprise.
Note: Manager (mgr) is a menu application allowing the administrator to create, modify
and view configuration parameters. Only one manager instance should be started
at one time.

Issue 02 Ref. ENTP0413C02TEUS.doc P. 1

PROCEDURE

1. Access to MGR

1.1. mgr command

On the call server

Note: l allows the language selection:

– DE0: German for Germany
– DE1: German for Austria
– IT0: Italian for Italy
– NL1: Dutch for Belgium
– GEA: Generic English of Alcatel
– US0: English for US
– FR0: French for France
– EN0: English for England
(Have to be done only once and stay in this language until a new change)

Remark
-> Shelf Specific telephone services
Result
Media Gateway Atm
PWT/DECT system Events routing discriminator
System Security and Access control
Translator IP
Classes of service SIP
Attendant DHCP Configuration
Users Alcatel 8&9 Series
Users by Profile SIP Extension
Set profile Encryption
Groups Passive Com. Server
Speed dialing SNMP Configuration
Phone book
Entities
Trunk groups
External services
Inter-Node links
X25
DATA
Applications

P. 2 Ref. ENTP0413C02TEUS.doc Issue 02

1.1.1. Use of Function Keys

2. Example of 4760I

On the call server under the mtcl account

Action Launch the command “mgr”
Action Select the “Users” object with the arrows
Shelf Specific telephone services
Result
Media Gateway Atm
PWT/DECT system Events routing discriminator
->System Security and Access control
Translator IP
Classes of service SIP
Attendant DHCP Configuration
Users Alcatel 8&9 Series
Users by Profile SIP Extension
Set profile Encryption
Groups Passive Com. Server
Speed dialing SNMP Configuration
Phone book
Entities
Trunk groups
External services
Inter-Node links
X25
DATA
Applications

Issue 02 Ref. ENTP0413C02TEUS.doc P. 3

Action Press “Enter”

Descend Hierarchy
Result
Action Press “Enter”
Other System Param.
Result
Descend Hierarchy
Result
Action Select the “System Parameters” object with the arrows en press “Enter”
[ All instances ]
Result
[ Set filters ]
[ Select attributes ]

Node Number(reserved) : 1
Instance (reserved) : 1
Instance (reserved) : 1
système Option + Law

Action Select the “All instances” object with the arrows en press “Enter”
Review/Modify: Users
Result
[ All instances ]
[ Set filters ]
[Select attributes]
Node number (Reserved) : 1
Directory number : -------

Action When the cursor it’s on “All instances” press “Enter“ and press CTRL+V or
F1 to validate
Law
Result
Circuit
…
…
->Use of 4760I

Action Select the use 4760I and press “Enter”

Node Number(reserved) : 1
Result
Instance (reserved) : 1
Instance (reserved) : 1
system Option + use of 4760I

Use of 4760I + True

Action CTRL+V or F1

For a taking into account it is necessary to start again the system.

P. 4 Ref. ENTP0413C02TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

151
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

152
Alcatel-Lucent OmniPCX Enterprise

Alcatel-Lucent Expert tool

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe Alcatel-Lucent Expert tool

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent Expert tool

Ref. ENTP0414P02TEUS Issue 02

153
Alcatel-Lucent Expert tool
What is Expert tool?

The Alcatel-Lucent Expert tool is:

An integrated configuration tool

Used to configure the Database

Shelves, users, categories…

Used to “Save/Restore” database and/or OPS

This tool is accessible in two different ways

Via a WEB client (connection with https or http) (1)

Or via the “4760i” client(2)

It’s a GUI using JRE(3)

All Rights Reserved © 2008, Alcatel-Lucent 2

(1) From the R7.0 release, if a connection request is done on the default http port (80), this connection is automatically
redirected to the secured http Server (https, port 443)

(2) You need to install the 4760i software in your PC, provided with the release or directly available on the CPU
(http://IP@of_the_CPU/nmc/client/)

(3) JRE means Java Runtime Environment

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent Expert tool

Ref. ENTP0414P02TEUS Issue 02

154
Alcatel-Lucent Expert tool
How to access?

To the WEB client(1)

By using a browser (Internet Explorer or Netscape)

By the URL: https://IP@ of the CPU(2)

By using the account “mtcl”

To the ”4760i” client(1)

By running the program from “Program Files”

To enter the IP@ of the CPU

By using the account “mtcl”

All Rights Reserved © 2008, Alcatel-Lucent 3

(1) For the first connection you need to install JRE and the plug-in associated
(2) According to the management it’s possible to use the CPU name and also an http connection

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent Expert tool

Ref. ENTP0414P02TEUS Issue 02

155
Alcatel-Lucent Expert tool

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent Expert tool

Ref. ENTP0414P02TEUS Issue 02

156
Alcatel-Lucent OmniPCX Enterprise
Alcatel-Lucent Expert Tool

PROCEDURE

OBJECTIVE

- To learn how to access to the Alcatel-Lucent Expert tool, install JRE and the plug-in and
connect to the “Configuration” and “Maintenance “menu.

OVERVIEW
Become familiar with navigating the system configuration using the Alcatel-Lucent Expert tool
application. This application is contained in the Alcatel-Lucent OmniPCX enterprise system
software. It allows creation, deletion, and modification of all components and services within
the Alcatel-Lucent OmniPCX Enterprise

Issue 02 Ref. ENTP0414C01TEUS.doc P. 1

PROCEDURE

1. Access to Alcatel-Lucent Expert tool – Web client

1.1. Access to the main page

On Internet Explorer or Netscape

Entry IP address of the CPU (e.g. https://10.1.1.1) (role address if managed)
Action Press “Enter” or click
Result

Note: The Web browser shows you this security message to warm you about a potential
security problem (which is not real in this case). The Alcatel-Lucent OmniPCX
Enterprise creates itself its own digital certificate, usually, it is an Authentication
Authority which delivers this kind of information

Action Click “Yes” to continue

Result

Note: The “Unified Maintenance tool” is used to check some system status (CPU, boards,
users, trunk groups…)

P. 2 Ref. ENTP0414C01TEUS.doc Issue 02

Action Click on “Configuration / save - restore “

Result

1.2. Select the interface’s language

Action
Select the main window language:
Result

Issue 02 Ref. ENTP0414C01TEUS.doc P. 3

1.3. Install JRE and the plug-in

Action In the left of the window, click on the first “click here” message

Result

Action Click “Open” and follow instructions

Note: At the end of the installation of JRE, the computer asks you to restart, select
“NO”, You will restart manually the computer after the installation of the plug-in

Action In the left of the window click on second “click here” message

Result

Action Press on “Open” button

Note: Restart the computer

P. 4 Ref. ENTP0414C01TEUS.doc Issue 02

2. Access to Alcatel-Lucent Expert Tool client

Note: You can install the Alcatel-Lucent Expert Tool client from the given 4760 Software
pack, or from the Call Server itself.

2.1. How to find the Alcatel-Lucent Expert Tool client on the Call Server?

Action Enter the next URL: https://IP@_of_the_CPU/nmc/client/Clt4760i.EXE

Note: You can also use name of Call Server if the management is done (DNS)

Action Select “Save” , then choose a directory on your computer

2.2. Installation

Action Run the “Clt4760i.EXE” file (storage directory selected in the previous step)
Result

Issue 02 Ref. ENTP0414C01TEUS.doc P. 5

Action Extract the files in a folder (created by yourself e.g. c:/4760i)

Result

Action Run the “setup.exe”

Result

Action Select the installation’s language and click OK

Result

P. 6 Ref. ENTP0414C01TEUS.doc Issue 02

Action Click “Yes” to accept the License Agreement

Result

Action Enter the IP address of the Call Server (e.g. 10.1.1.1) and click “Next”

Note: If a role IP address is configured in the PCX, use the “main” role address to access
to the Web Tool

Result

Issue 02 Ref. ENTP0414C01TEUS.doc P. 7

Action Click “Next” to continue

Result

Action Click “Finish” to validate the installation

P. 8 Ref. ENTP0414C01TEUS.doc Issue 02

3. Using of the Alcatel-Lucent Expert tool

3.1. Web client

Note: You are connected to the main page(end of the step 1.1)

3.1.1. Save and restore

Note: You are going to see how to save the database from the Call Server disk to the PC

Action

Click on the maintenance button

Result

Action Enter “mtcl” as “user name” and its corresponding password, then click on
”OK”
Result

Issue 02 Ref. ENTP0414C01TEUS.doc P. 9

Action Click on “PCX Backup”

Result

Action Select the data you want to backup (e.g. “MAO, voice guides, and

accounts”) and click

Result

Note: You have the possibility to select the location of the “backup directory”
If you let the “Save in the default directory” field validated by default, the
backup of the expected files is located in:
C:/Documents and Settings/”User-Account-name”/Desktop
Or, if you de-activate this field, the backup location can be an other directory (use
the “browse” button)

P. 10 Ref. ENTP0414C01TEUS.doc Issue 02

3.1.2. Configuration

Action In the main page (last point of step 1.1)

Click on the configuration button

Result

Action Enter “mtcl” as “user name” and its corresponding password,

then click on ”OK”
Result

Issue 02 Ref. ENTP0414C01TEUS.doc P. 11

Action If you want to see the complete tree, click on the first little symbol just
one time
Result

Remark If this window appear to the screen press “OK”

3.2. Alcatel-Lucent Expert Tool client

3.2.1. Save and restore

Action
Click on , select “Programs”, “OXE 4760i Client” and “Launch Save-
Restore”
Result Identical to the web client, for the following steps

3.2.2. Configuration
Action
Click on , select “Programs”, “OXE 4760i Client” and “Launch
Configuration”
Result Identical to the web client, for the following steps

P. 12 Ref. ENTP0414C01TEUS.doc Issue 02

4. Example of using

Note: You are connected on the Alcatel-Lucent Expert tool.

You should change the directory first name

Action Double click on the object called “Users” or make one click on in front of
“Users”
Result

Action Select the first object (user)

Result

In the right part you can see details about this user

Issue 02 Ref. ENTP0414C01TEUS.doc P. 13

Action Double click on the field where the name “BOND” is

Result

Action Enter a new name (e.g. TUTU)

Result

Action
Click the to validate the modification

P. 14 Ref. ENTP0414C01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

171
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

172
Alcatel-Lucent OmniPCX Enterprise

Web Tool

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe how to access to the Web Tool maintenance tool

Alcatel-Lucent OmniPCX Enterprise – Web Tool

Ref. ENTP0458P01TEUS Issue 02

173
Web Tool
Generalities

Before being able to check some information on the OmniPCX Enterprise, the
Network administrator has to provide you the Com Server IP address

The maintenance tool to be used is the “Web Tool”

A web browser has to be used

If the role “MAIN” address is configured, used this address to access to the
system

HTTP and/or HTTPS prompts can be used

Anyway, the system Web Server redirects automatically all the connections to the secured
access (https)

This maintenance tool can be used to verify the status of the system, in Stand-
Alone and/or Network configuration

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Web Tool

Ref. ENTP0458P01TEUS Issue 02

174
Web Tool
Access to the maintenance tool

Access to the tool (via a Web browser)

The URL used to access to the WebTool as to be:

http://OmniPCX-Enterprise-IP@/webtool2/

Ex:

At the connection to the system, a Security message is displayed

All Rights Reserved © 2008, Alcatel-Lucent 3

A Digital Certificate as to be taken into account to authenticate and secure the connection.
If you dismiss this message, the connection to the web server (OmniPCX Enterprise) is rejected.
As soon as the Security message is acknowledged, the connection to the Web Server is authorized , and Web Tool access window
is displayed (next page)

Remark:
It is also possible to access to this tool giving only the “CS” IP address in the Web browser. The “Maintenance “ tab has to be
selected, then, the HTTP server redirects the connection to the “Webtool2” page

Alcatel-Lucent OmniPCX Enterprise – Web Tool

Ref. ENTP0458P01TEUS Issue 02

175
Web Tool
Access to the maintenance tool (Cont’)

To access to the maintenance Web Tool:

The language has to be selected

The “mtcl” login and password have to be given

All Rights Reserved © 2008, Alcatel-Lucent 4

The default “mtcl” password can not be used. This one has to be therefore modified

Alcatel-Lucent OmniPCX Enterprise – Web Tool

Ref. ENTP0458P01TEUS Issue 02

176
Web Tool
Access to the Stand-Alone system status

When authenticated, a menu is displayed on the left of page

Press on “Toolbox” menu to reach the Stand-Alone system status Tool

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Web Tool

Ref. ENTP0458P01TEUS Issue 02

177
Web Tool
Stand-Alone system status

A new page provides several submenus and information about the system

All Rights Reserved © 2008, Alcatel-Lucent 6

Remark
The different submenus will detailed in the some other subjects

Alcatel-Lucent OmniPCX Enterprise – Web Tool

Ref. ENTP0458P01TEUS Issue 02

178
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

179
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

180
Alcatel-Lucent OmniPCX Enterprise

Media Gateway (IP and Crystal)

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Media Gateway (IP and Crystal)

Alcatel-Lucent OmniPCX Enterprise – Media Gateway (IP and Crystal)

Ref. ENTP0401P10TEUS Issue 02

181
Media Gateway (IP and Crystal)
Overview

System installation is done thanks to different elements called shelves (or rack,
or ACT)

A Call Server controls these elements

The Call Servers are:

For the common hardware

CPU-CS
Appliance Server

For the Crystal Hardware

CPU5/6/7

All Rights Reserved © 2008, Alcatel-Lucent 2

Warning

Shelves and boards are automatically created from the file “HARDWARE.MAO”, you have the possibility to modify or create
others shelves and boards

Alcatel-Lucent OmniPCX Enterprise – Media Gateway (IP and Crystal)

Ref. ENTP0401P10TEUS Issue 02

182
Media Gateway (IP and Crystal)
Overview

Different types of hardware are possible for the configuration: Common

hardware and Crystal hardware

Use of CPU-CS and Appliance Server

With Common hardware only (Case 1)

With Common hardware and Crystal hardware (Case 2)

Use of CPU5/6/7

With Crystal hardware only (Case 3)

With Crystal hardware and Common hardware (Case 4)

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Media Gateway (IP and Crystal)

Ref. ENTP0401P10TEUS Issue 02

183
Media Gateway (IP and Crystal)
On CPU-CS and AS

Case 1: Common hardware

Call Server: CPU-CS or AS

IP Media Gateway: GD IP Media Gateway: GD

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Media Gateway (IP and Crystal)

Ref. ENTP0401P10TEUS Issue 02

184
Media Gateway (IP and Crystal)
On CPU-CS and AS

Case 2: Common hardware and Crystal hardware

Call Server: CPU-CS or AS

IP Media Gateway: GD

Crystal Media Gateway: INTIPB

All Rights Reserved © 2008, Alcatel-Lucent 5

INTIPB board in CPU position on Crystal hardware

Alcatel-Lucent OmniPCX Enterprise – Media Gateway (IP and Crystal)

Ref. ENTP0401P10TEUS Issue 02

185
Media Gateway (IP and Crystal)
On CPU-CS and AS

Case 1 & 2: Common hardware and Crystal hardware

Possibility to connect several IP and Crystal Media gateways on the LAN (or
WAN) with the same Call Server

The Call Server are always in the rack 0*

Positions 6 and 10

The IP and Crystal Media Gateway have their own shelf’s numbers (except 18
and 19)

All Rights Reserved © 2008, Alcatel-Lucent 6

* In the case of Call Server duplication (Call Server backup) the two positions are used (or In Service)

Shelf 18 associated for the 4645 (Voice mail)

Shelf 19 associated for IP-link (Process used for exchanges between the Call Server and the IP Media Gateway )

Alcatel-Lucent OmniPCX Enterprise – Media Gateway (IP and Crystal)

Ref. ENTP0401P10TEUS Issue 02

186
Media Gateway (IP and Crystal)
On CPU5/6/7

Case 3: Crystal hardware

Main ACT Call Server: CPU5/6/7

Links:
- IP
- Digital
- Optical

Peripheral ACT Peripheral ACT

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – Media Gateway (IP and Crystal)

Ref. ENTP0401P10TEUS Issue 02

187
Media Gateway (IP and Crystal)
On CPU5/6/7

Case 4: Crystal hardware and Common Hardware

Main ACT Call Server: CPU5/6/7

Links:
- IP
- Digital
- Optical

IP Media Gateway: GD

Peripheral ACT

All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Media Gateway (IP and Crystal)

Ref. ENTP0401P10TEUS Issue 02

188
Media Gateway (IP and Crystal)
On CPU5/6/7

Case 3 and 4: Crystal hardware and Common Hardware

You must define a shelf number for each rack

For example 0 for the main rack and 1, 2, … for the peripheral ACTs

The rack 19 is reserved for the IP-link

For a Crystal hardware Call Server: no rack 18 (Alcatel-Lucent 4645 voicemail

system not used by this type of hardware)

All Rights Reserved © 2008, Alcatel-Lucent 9

Alcatel-Lucent OmniPCX Enterprise – Media Gateway (IP and Crystal)

Ref. ENTP0401P10TEUS Issue 02

189
Media Gateway (IP and Crystal)
On CPU5/6/7

The boards are different according to the type of hardware used

For the Common hardware

In management the names of the boards start by MG-xxx

Example: MG-UAI8 for a UAI8 board providing 8 UA equipments

For the Crystal hardware

In management the names corresponds to the “real” name of the board

Example: UA32 for an UA32 board providing 32 UA equipments

All Rights Reserved © 2008, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – Media Gateway (IP and Crystal)

Ref. ENTP0401P10TEUS Issue 02

190
Alcatel-Lucent OmniPCX Enterprise
IP Media Gateway management

PROCEDURE

OBJECTIVE

- To learn how to manage an IP Media gateway and the GD board

OVERVIEW
The creation of the IP Media Gateway is done automatically by the OPS files (hardware.mao),
it’s possible after time to modify or/and create others shelves
The rack 0 is always used by the Call Server.
The rack 18 and 19 are used also by the system.
For the management of the GD, you can use static or dynamic IP address assignment

Issue 04 Ref. ENTP0401C10TEUS.doc P. 1

PROCEDURE

1. Create the IP Media Gateway

Application mgr
Path Shelf
Action Create
Entry Create Shelf
Node Number (reserved): 1
Shelf Address: 1
Shelf Type: + Media Gateway Large
Name of rack: -------------------
Remark For 1 U rack, the type of the shelf is “Media Gateway Small”
For 3 U rack, the type of the shelf is “Media Gateway Large”
Action Press CTRL+V one time to entry the shelf role
Entry Shelf Role: + Main (Master)
Main Shelf Address: -1 (default value)
Remark The role shelf can also be " Expansion 1 " or " Expansion 2 ", in this case, it
is necessary to inform the number of the main shelf to which it will be
attached in Main Shelf Address.
Remark The GD is created automatically in position 0 of the rack

P. 2 Ref. ENTP0401C10TEUS.doc Issue 04

2. Management of the GD

2.1. Static mode

2.1.1. Management of the MAC address in the Ethernet parameters

Application mgr
Path Shelf/Boards/Ethernet parameters
Action Consult/modify
Entry Board Ethernet Address:: 00:80:9f:31:03:1e
Action Press CTRL+V to validate
Press CTRL+C as many times as needed to come back on main menu
Remark Select the main shelf containing the GD board, then the Ethernet
parameters of the GD board and enter the GD board Ethernet address.

Issue 04 Ref. ENTP0401C10TEUS.doc P. 3

2.1.2. Management of the IP configuration on the GD

Application On the GD (V24 config port)

login : admin
Password : admin
Command su
Command mgconfig
1. Startup mode
Entry Enter new startup mode: (0:Static - 1:Dynamic - 2:Bios) 0
2. IP address
Entry Enter new IP address: 10.1.1.30 (eg)
3. Netmask
Entry Enter new Netmask: 255.255.255.0 (eg)
4. Gateway address
Entry Enter new Gateway address: 10.1.1.254 (eg)
5. TFTP server address
Entry Enter new TFTP server address: 10.1.1.1 (eg)
6. Callserver address
2. Current mode is: AUTOMATIC - switch to manual?
Entry Enter new callserver address: 10.1.1.1 (eg)
8. Crystal number
2. Current mode is: AUTOMATIC - switch to manual?
Entry Enter new crystal number:1 (eg)
Configuration not saved - do you want to save now? (y/n) y
Do you want to reboot now? (y/n) y
Entry 0. Exit
Configuration not saved - do you want to save now? (y/n) y
Do you want to reboot now? (y/n) y

P. 4 Ref. ENTP0401C10TEUS.doc Issue 04

2.1.3. Management of the compressors daughterboard in the GD

2.1.3.1. Check the type of daughterboard present on the GD

--- Inter Crystal Topology ---

+-------------------------------------------------------+
| CR | CPL Type Role Free/Tot Role Type CPL | CR |
|-------------------------------------------------------|
| 01 | 00 - GD (MAIN)---08/08---(INT_A)INTIPA - 02 | 19 |
|-------------------------------------------------------|

2.1.3.2. Manage the daughterboard

Application mgr
Path Shelf/boards/
Action Consult/modify
Action Select the GD
Entry INTIP Daughterboard: MCV8
No. of Compressors for Gateway: 4
No. Of Compressors for IP Devices: 3
Remark Choose MCV8, MCV24, MADA1 et MADA3
The two parameters No. of Compressors for Gateway and No. of
Compressors for IP Devices are not used if the direct RTP in network
service is not enabled
By default, the system select MADA3 and the N° of compressors for Gateway
and the N° of compressors for IP Devices are fixed to 12.
If there is a mcv8, it is mandatory to change the N° of compressor as the
example.
In other case the validation is refused
(see on technical documentation in Management GA, GD, INT-IP boards)
Remark A restart of the GD is mandatory. (rstcpl 1 0)

Issue 04 Ref. ENTP0401C10TEUS.doc P. 5

2.2. Dynamic mode

2.2.1. DHCP Server Management

P. 6 Ref. ENTP0401C10TEUS.doc Issue 04

2.2.2. Management of the MAC address in the Ethernet parameters

2.2.3. Management of the IP configuration on the GD

Application On the GD (V24 config port)

login admin
Password admin
Command su
Command mgconfig
Select 1. Startup mode
Entry Enter new startup mode: (0:Static - 1:Dynamic - 2:Bios) 1
Select 6. Callserver address
2. Current mode is: MANUAL - switch to automatic? y
Select 8. Crystal number
2. Current mode is: MANUAL - switch to automatic? y
Entry 0. Exit
Configuration not saved - do you want to save now? (y/n) y
Do you want to reboot now? (y/n) y

Issue 04 Ref. ENTP0401C10TEUS.doc P. 7

2.2.4. Management of the compressors daughterboard in the GD

2.2.4.1. Check the type of daughterboard present on the GD

Application mtcl
Command Config 1 -d
+-------------------------------------------------------+
Result | Cr | cpl| cpl type | hw type |cpl state |coupler ID |
|----|----|----------|---------|-----------|------------|
| 1 | 0 | GD|---------|IN SERVICE |NO PCMS |
| 1 | 0 | MCV-8|---------|IN SERVICE |NO PCMS |
--- Inter Crystal Topology ---
+-------------------------------------------------------+
| CR | CPL Type Role Free/Tot Role Type CPL | CR |
|-------------------------------------------------------|
| 01 | 00 - GD (MAIN)---08/08---(INT_A)INTIPA - 02 | 19 |
|-------------------------------------------------------|

2.2.4.2. Manage the daughterboard

P. 8 Ref. ENTP0401C10TEUS.doc Issue 04

2.3. Dynamic mode with reservation

Note: This method can be used if you receive a new GD from Alcatel (No binaries
installed)

2.3.1. DHCP Server Management

Application mgr
Path DHCP configuration
Entry Configuration: DHCP Server
Action Press CTRL+V to validate
Select DHCP configuration
Local Subnetwork
Entry Default router address:10.1.1.254
TFTP server address: 10.1.1.1
Remark Example: DHCP Configuration:
Subnet address: 10.1.1.0
Subnet mask: 255.255.255.0
Broadcast address: 10.1.1.255
Default router address: 10.1.1.254
TFTP Server address: 10.1.1.1
Action Press CTRL+V to validate
Path DHCP configuration / Local Subnetwork/ Static IP address (local subnet)
Action Create
Entry IP address: 10.1.1.30
MAC address: 00:80:9f:31:03:1e
TFTP Server address: 10.1.1.1
Configuration file: GD:/DHS3bin/downbin/emg/binmgst
Remark e.g: IP address: 10.1.1.20 (of the GD board)
MAC Address: 00:80:9f:31:03:1e (of the GD board)
TFTP Server address: 10.1.1.1 (call server address)
Configuration file GD: /DHS3bin/downbin/emg/binmgst (to load on GD)
Path DHCP configuration
Select Apply modification
Action Press CTRL+V to validate

Issue 04 Ref. ENTP0401C10TEUS.doc P. 9

2.3.2. Management of the MAC address in the Ethernet parameters

2.3.3. Management of the IP configuration on the GD

Application On the GD (V24 config port)

login admin
Password admin
Command su
Command mgconfig
1. Startup mode
Select 1. Startup mode
Entry Enter new startup mode: (0:Static - 1:Dynamic - 2:Bios) 1
Select 6. Callserver address
2. Current mode is: MANUAL - switch to automatic? y
Select 8. Crystal number
2. Current mode is: MANUAL - switch to automatic? y
Entry 0. Exit
Configuration not saved - do you want to save now? (y/n) y
Do you want to reboot now? (y/n) y

P. 10 Ref. ENTP0401C10TEUS.doc Issue 04

2.3.4. Management of the compressors daughterboard in the GD

2.3.4.1. Check the type of daughterboard present on the GD

Application mtcl
Command config 1 -d
+-------------------------------------------------------+
Result | Cr | cpl| cpl type | hw type |cpl state |coupler ID |
|----|----|----------|---------|-----------|------------|
| 1 | 0 | GD|---------|IN SERVICE |NO PCMS |
| 1 | 0 | MCV-8|---------|IN SERVICE |NO PCMS |
--- Inter Crystal Topology ---
+-------------------------------------------------------+
| CR | CPL Type Role Free/Tot Role Type CPL | CR |
|-------------------------------------------------------|
| 01 | 00 - GD (MAIN)---08/08---(INT_A)INTIPA - 02 | 19 |
|-------------------------------------------------------|

2.3.4.2. Manage the daughterboard

Issue 04 Ref. ENTP0401C10TEUS.doc P. 11

P. 12 Ref. ENTP0401C10TEUS.doc Issue 04

PROCEDURE

OBJECTIVE

- To learn how to manage a Crystal shelf

OVERVIEW
The creation of the Crystal shelf is done automatically by the OPS files (hardware.mao), it’s
possible after time to modify or/and create others shelves
The Id. 19 cannot be used for the shelf number.

Issue 02 Ref. ENTP0401C11TEUS.doc P. 1

PROCEDURE

1. Create the Main Crystal shelf

Application mgr
Path Shelf
Action Create
Entry Create Shelf
Node Number (reserved): 1
Shelf Address: 0
Shelf Type: + ACT 14 positions
Name of rack: -------------------
Remark You can use also: ACT 28 positions
Voice Hub
WM1
The CPU position depends of the type of rack used
Action Press CTRL+V one time to entry the shelf role
Entry Shelf Role : + Main (Master)
Main Shelf Address : -1 (default value)

2. CPU management

Application mgr
Path Shelf/boards
Action Create
Entry Create Shelf
Node Number (reserved): 1
Shelf Address: 0
Board Address : 6
Board Type: + CPU7
Remark You can use : CPU5 step 3 / CPU6 step 2 / CPU7
Action Press CTRL+V one time to entry the shelf role

P. 2 Ref. ENTP0401C11TEUS.doc Issue 02

PROCEDURE

OBJECTIVE

- To learn how to manage a Remote Crystal Media Gateway (over IP)

OVERVIEW
With the Common Hardware, the rack 0 is used for the Call Server and the rack 19 is used for
the IP-link (INTIPA virtual) for the signaling exchanges with the INTIPB board connected to the
Remote ACT
With the Crystal Hardware, the rack 0 (for example) is the main rack and it’s necessary in this
rack to create an INTIPA board, for the signaling exchanges between the CPU and the INTIPB
board connected to the Remote ACT
For the connection of the INTIP board on the LAN, the CBC1 connector is connected on the back
panel behind the INTIP board and from this CBC1a connection to the LAN (via a LANX for
example)

Issue 04 Ref. ENTP0401C12TEUS.doc P. 1

PROCEDURE

1. Create the remote ACT

Application mgr
Path Shelf
Action Create
Entry Create Shelf
Node Number (reserved): 1
Shelf Address: 3
Shelf Type: + ACT 14 Positions
Name of rack: -------------------
Action Press CTRL+V one time to entry the shelf role
Entry Shelf Role : + Remote ACT
Main Shelf Address : 0
Remark The main shelf address is the main rack address
- Always “0” if you use for the main ACT the Common hardware (CPU-CS
or AS)
- The main ACT number managed for the Crystal hardware (CPU5/6/7)

2. Management of the INTIPB

2.1. Manage the shelf number

The shelf number is managed by switches on the INTIP board itself

0 for OFF
Value of
For examples: 1 for ON
the switch
- shelf number = 2
I need to move in the “on” position the switch number 3 on the S401 (1*21=2)
- shelf number = 5
I need to move in the “on” position the switch number 2 and 4 on the S401
(1*22+1*21=5)
etc…

P. 2 Ref. ENTP0401C12TEUS.doc Issue 04

2.2. Create the INTIPB board

Application mgr
Path Shelf/boards
Action Create
Entry Create Shelf
Node Number (reserved): 1
Shelf Address: 2
Board Address : 6
Board Type: + INTIPB
INTIP Daughterboard: 1 GIP4-4
No. of Compressors for IP Devices: 16
No. of Compressors for Gateway : 16
Action Press CTRL+V to validate

Note: Daughterboards used with the INTIP board

- 1 GIP4-4: 32 compressors
- 2 GIP4-4: 60 compressors
- 1 GIP4-1: 8 compressors
- 2 GIP4-1: 16 compressors

2.3. Management of the MAC address in the Ethernet parameters

Application mgr
Path Shelf/Boards/Ethernet parameters
Action Consult/modify
Entry Board Ethernet Address: : 00:80:9f:31:03:1e
Action Press CTRL+V to validate
Action Press CTRL+C as many times as needed to come back on main menu

Note: Select the remote ACT containing the INTIPB board, then the Ethernet parameters
of the INTIPB board and enter the INTIPB board Ethernet address.

Issue 04 Ref. ENTP0401C12TEUS.doc P. 3

2.4. IP configuration in Static mode

2.4.1. Management of the IP configuration on the INTIPB

Application On the INTIPB (V24 config port)

Available commands:
- view : display current IP configuration
- chmode: change IP Configuration Mode (Static/Dynamic)
- chip : change Static IP Parameters
- chqual: Change default quality Parameters
- save : save modified configuration
- reset : reset coupler

Use ? or ? <cmd> to get help on command

Config:chmode
Entry

Current IP Configuration Mode: Static

Enter new mode (0 Dynamic, 1 Static):1
Action Press Enter to validate
Config:chip
Entry
Enter new IP Address
(default 010.001.001.022):010.001.001.040
Enter new IP SubNetMask
(default 255.255.000.000):255.255.255.000
Enter new IP Default Router
(default 000.000.000.000):010.001.001.254
Enter new IP TFTP Server
(default 010.001.001.001):010.001.001.001
UseDuplex (0 no 1 yes)
(default 0):1
Action Press Enter to validate
Config:save
Entry
New Configuration saved.

WARNING: Coupler must be restarted to take in account new

configuration
Do you want to restart coupler now ! (y/n): y
Coupler will reset in 5 seconds !

P. 4 Ref. ENTP0401C12TEUS.doc Issue 04

2.5. IP configuration in Dynamic mode

2.5.1. DHCP Server Management

Note: Example of DHCP Configuration :

- Subnet address : 10.1.1.0
- Subnet mask : 255.255.255.0
- Broadcast address : 10.1.1.255
- Default router address : 10.1.1.254
- TFTP Server address : 10.1.1.1

Action Press CTRL+V to validate

Path DHCP configuration / Local Subnetwork/ IP Addresses Range (local subnet)
Action Create
Entry Range first address: 10.1.1.50
Range last address:10.1.1.55
Path DHCP configuration
Select Apply modification
Action Press CTRL+V to validate

Issue 04 Ref. ENTP0401C12TEUS.doc P. 5

2.5.2. Management of the IP configuration on the INTIPB

Application On the INTIPB (V24 config port)

Remark If you use an INTIP or INTIP2 board the V24 cable is different
For INTIP2 same cable as a GD
For INTIP specific cable
---------------------------------------------------------------
Result IP Configuration Menu
---------------------------------------------------------------
Available commands:
- view : display current IP configuration
- chmode: change IP Configuration Mode (Static/Dynamic)
- chip : change Static IP Parameters
- chqual: Change default quality Parameters
- save : save modified configuration
- reset : reset coupler
Use ? or ? <cmd> to get help on command
Config:chmode
Entry
Current IP Configuration Mode: Static
Enter new mode (0 Dynamic, 1 Static):0
Action Press Enter to validate
Config:save
Entry New Configuration saved.
WARNING: Coupler must be restarted to take in account new
configuration
Do you want to restart coupler now ! (y/n): y
Coupler will reset in 5 seconds !

3. Declaring the INT-IPA in case of using the Crystal shelf

Note: The main Act is using the Crystal hardware (CPU5/6/7)

Application mgr
Path Shelf/board
Object Create
Parameters Shelf address: : 0 (enter the shelf number)
Board address : 11 (enter the board position)
Interface type : INT-IP A
Daughterboard : 1 GIP6

Note: Daughterboards used with the INTIP board

- 1 GIP4-4: 32 compressors
- 2 GIP4-4: 60 compressors
- 1 GIP4-1: 8 compressors
- 2 GIP4-1: 16 compressors

P. 6 Ref. ENTP0401C12TEUS.doc Issue 04

Coupler Maintenance

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To use the maintenance tool to check the interfaces boards status

Alcatel-Lucent OmniPCX Enterprise – Coupler Maintenance

Ref. ENTP0401M01TEUS Issue 02

211
Web Tool
Access to the maintenance tool

Access to the tool (via a Web browser)

The URL used to access to the WebTool as to be:

http://OmniPCX-Enterprise-IP@/webtool2/

Ex:

At the connection to the system, a Security message is displayed

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Coupler Maintenance

Ref. ENTP0401M01TEUS Issue 02

212
Web Tool
Access to the maintenance tool (Cont’)

To access to the maintenance Web Tool:

The language has to be selected

The “mtcl” login and password have to be given

All Rights Reserved © 2008, Alcatel-Lucent 3

The default “mtcl” password can not be used. This one has to be therefore modified

Alcatel-Lucent OmniPCX Enterprise – Coupler Maintenance

Ref. ENTP0401M01TEUS Issue 02

213
Web Tool
Access to the Stand-Alone system status

When authenticated, a menu is displayed on the left of page

Press on “Toolbox” menu to reach the Stand-Alone system status Tool

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Coupler Maintenance

Ref. ENTP0401M01TEUS Issue 02

214
Coupler maintenance
Main menu

When you are connected on the Web maintenance tool, the following menu will
be shown on the screen

On this screen you can view general information concerning the system

CPU name,IP address,Node number,Network number,Software release etc..

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Coupler Maintenance

Ref. ENTP0401M01TEUS Issue 02

215
Coupler maintenance
Coupler maintenance menu

For the coupler maintenance , you can select « Board hardware status » in the
menu

It possible to select one board when you click on the board number

All Rights Reserved © 2008, Alcatel-Lucent 6

In this example we can see that all couplers of Crystal 1 are in service except the board in position 3 (SLI8(Z))

Alcatel-Lucent OmniPCX Enterprise – Coupler Maintenance

Ref. ENTP0401M01TEUS Issue 02

216
Coupler maintenance
Coupler maintenance menu

Example of board status

In this example we can see that the UAI_8 coupler is correctly started

The SLI_8 is out of service,you have to check if the board is present and
correctly plugged in the rack

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – Coupler Maintenance

Ref. ENTP0401M01TEUS Issue 02

217
All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Coupler Maintenance

Ref. ENTP0401M01TEUS Issue 02

218
Alcatel-Lucent OmniPCX Enterprise
Creation of IP Media Gateway

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to create an IP Media Gateway and boards

MANAGEMENT

1. Check the shelf #0 and “19 (by using the maintenance web tool or the command config)

2. Create the shelf #1 (main shelf) and 1 expansion cabinet (shelf #2)

3. Manage the GD in static mode (see IP addresses in the file site or use the IP address given
by the trainer)

4. Create the boards according to the file site (or the boards plugged in your system)

5. Check the good working of these shelves

Issue 02 Ref. ENTP0401H10TEUS.doc HO. 1

HO. 2 Ref. ENTP0401H10TEUS.doc Issue 02

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to create an Crystal Media Gateway and boards

MANAGEMENT

1. Check the shelf #0 and #19 (by using the maintenance web tool)

2. Create the shelf #3 (Remote Crystal Media Gateway)

3. Manage the INTIPB board in static mode (see the IP address in the file site or use the IP
address given by the trainer)

4. Create the boards according to the file site (or the boards plugged in your system)

5. Check the good working of these shelves

Note: The INTIPB board starts, if there is (in minimum) one board created in the shelf
(e.g. UA32)

Issue 01 Ref. ENTP0401H11TEUS.doc HO. 1

HO. 2 Ref. ENTP0401H11TEUS.doc Issue 01

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

223
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

224
Alcatel-Lucent OmniPCX Enterprise

Voice Guides

All Rights Reserved © 2005, Alcatel-Lucent 1

OBJECTIVES

To describe the static and dynamic voice guides

To describe the boards used to broadcast voice guides

To talk about the voice guides format

To describe the “Vgtransfer” tool

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

225
Voice Guides
Overview

Voice guide overview

A voice guide comprises one or more voice messages.
The purpose of the voice messages is to assist users with phone operation
and/or provide users with information.
The CCd (Contact Center Distribution), integrated Automated Attendant and
many other phone features use voice messages

Types of voice messages

Voice messages may be:

Static: cannot be modified by the user:
Generic: compatible with generic numbering plans and offered in at least 6 different
languages for all countries.
Standard: adapted to a country with special requirements and/or a numbering plan differing
from the generic numbering plan.
Custom: to an area or company
Dynamic: modifiable, recorded by users and/or managers via a set or the
Alcatel-Lucent Audio Station application (AAS)

All Rights Reserved © 2005, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

226
Voice Guides
Overview

The Alcatel-Lucent OmniPCX Enterprise uses specific couplers for voice guides:

In case of crystal hardware

GPA2

In case of common hardware

GD or GA board

All Rights Reserved © 2005, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

227
Voice Guides
Overview

Voice guides

According to applications available in the installation

Guides used for phone features
Guides used for Call Center Distribution
Music On Hold, etc..

Stored on different medias:

Flash-Cards or RAM-Cards (VG, SU-VG, GPA boards)
Flash Memory or RAM Memory (Z20-VG, CPU6s2, GA, GD, GPA2)

Multi-language possibility (8 languages maximum)

All Rights Reserved © 2005, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

228
Voice Guides
Hardware

GPA2 board

Functions
N party conference
Voice guides (in RAM or Flash memory on the board)
R1/R2 multi frequencies detection and generation
Tones generation
Silence detection (VAD)

Functional Blocks
4 x 6 MB of Flash Memory (4 x 12 min of static guides)
1 x 7,5 MB of RAM Memory (1 x 15 min of dynamic guides)

All Rights Reserved © 2005, Alcatel-Lucent 5

GPA2: (General Purpose Auxiliary 2): Auxiliary Board for general use version 2
VAD: (Voice Activity Detection): Feature linked to CCD used to detect customer’s answers during outbound campaign

This board is an evolution of the GPA board.

Flash and Ram are embedded on the board so Flash-Cards and Ram-Cards are not used with this board .
Voice guides are downloaded from the CS hard disk to the Flash or RAM memory.
Guides related to one language are downloaded in the same area of the memory of the flash memory, so it’s possible to have 4
languages at the same time, they can be simultaneously broadcasted on 60 channels
An internal battery can backup messages in RAM for a few hours outside the shelf.

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05
21
229
Voice Guides
Hardware

GD board

GD virtual GPA functions

Q23
Q23X
Tone detection
Voice guide
Conference: 3 x "3-Party Conference" per GD

Memory available for voice guides

4 x 2 MB Flash Memory for static guides
1 x 2 MB RAM Memory for dynamic guides

All Rights Reserved © 2005, Alcatel-Lucent 6

The virtual GPA is created by the Call Server in slot 27 of the main shelf of the IPMG

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

230
Voice Guides
Hardware

GA board

GA virtual GPA functions

Voice guide
Conference: 3 x "3-Party Conference" per GA

Memory available for voice guides

4 x 2 MB Flash Memory for static guides
1 x 2 MB RAM Memory for dynamic guides

All Rights Reserved © 2005, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

231
Voice Guides
VG Recording

Alcatel-Lucent Audio Station (AAS)

Builds generic or standard voice guides

Creates specific (custom) voice guides

Accepts analog and/or digital sources

Prom

Audio Tape
Flash-Card

Floppy disk
Microphone

Audio CD / CD-ROM

Analog Sources Digital Sources

All Rights Reserved © 2005, Alcatel-Lucent 8

The Alcatel-Lucent Audio Station (AAS) platform, structured around a PC with a sound board, lets you record personalized voice
guides as well as adding external music sources (ex: CD) and mixes them. After creating a series of voice guides, you can group
them and transfer -them directly onto the PABX (via ftp) or in a flash card or Eprom (4300 systems).

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

232
Voice Guides
VG Recording

Alcatel-Lucent Audio Station (next)

Recording Alcatel-Lucent Audio Station guides

Outputs on Flash-Card, Floppy disks, CD-ROM, File ...

Prom

FTP Flash-Card

Call Server
Floppy disk

CD-ROM

All Rights Reserved © 2005, Alcatel-Lucent 9

For further information on the AAS refer to the VOICE GUIDE PROGRAMMING STATION instructions

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

233
Voice Guides
VG Recording

To create file including some messages using AAS

In AAS window, create a new project

Edit this new project

To record a message, Samples/Sound record

Download the wave file in the project

Compile the project (ex: formation.msk)

Transfer the file compiled using vg tools

All Rights Reserved © 2005, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

234
Voice Guides
VG Recording

Registering guides on the GPA2 and GA / GD boards

Call Server System

X8/X9 Series+ IAK
Guides
/DHS3ext/vg/dhs

guide 1
guide 1’ ^ Ram Memory
guide 2
guide 3
^ Downloading (GPA2 / Gx)
selected guides
guide 4 ^
guide 4’’
etc...

Hard Disk
Alcatel-Lucent
Audio-station (^) selection (made per set or management)

All Rights Reserved © 2005, Alcatel-Lucent 11

IAK (Internal Alphabetic Keyboard)

This keyboard is mandatory to give a name to the file registered from the set.

When the file ends with ^, it means that it has been selected and downloaded in at least one GPA board or GA/GD.

In the case of a several Media-Gateway configuration, it can be advantageous to duplicate active guides on several GPA, GA/GD
boards to reduce traffic between Media-Gateway.

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05
22
21
235
Voice Guides
VG Transfer Tool

“VgTransferTool” software

Start the installation of the tool with the setup.exe delivered on the voice
guides CD-ROM

All Rights Reserved © 2005, Alcatel-Lucent 12

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

236
Voice Guides
VG Transfer Tool

Select the destination folder

All Rights Reserved © 2005, Alcatel-Lucent 13

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

237
Voice Guides
VG Transfer Tool

All Rights Reserved © 2005, Alcatel-Lucent 14

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

238
Voice Guides
VG Transfer Tool

Click on the icon “VG Transfer tool” on the desktop

Enter the IP@ of the e-CS

and select (Add host )

All Rights Reserved © 2005, Alcatel-Lucent 15

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

239
Voice Guides
VG Transfer Tool

Connection to e-CS and guide type selection

Select e-CS and «connect»

Select the voice guide type

All Rights Reserved © 2005, Alcatel-Lucent 16

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

240
Voice Guides
VG Transfer Tool

Transferring the voice guides

Select «Transfer» and wait

For the message «Transfer
/DHS3ext/vgadpcm/flash/custo
m completed »

All Rights Reserved © 2005, Alcatel-Lucent 17

After transfer the customized voice guides files are stored in: /DHS3ext/vgadpcm/flash/custom
formation.msk

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

241
Voice Guides
VG Downloading

The voice messages are played from GD, GA or GPA2 boards

Two different voice message file formats are offered, depending on the
board used to play them:

G711 to play messages from:

GPA2 board

ADPCM 32 to play messages from:

GD board with a virtual GPA board

GA board with a virtual GPA board

All Rights Reserved © 2005, Alcatel-Lucent 18

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

242
Voice Guides
VG Downloading

Loading static voice messages, by using « VgTransfer » tool

Selecting generic messages

Generic files (one per language) are transferred to the Call Server hard drive:
To the directory /DHS3ext/vgadpcm/flash/std for ADPCM files
To the directory /DHS3ext/vg/flash/std for G711 files

Selecting standard messages

Standard files are transferred to the Call Server hard drive:
To the directory /DHS3ext/vgadpcm/flash/std for ADPCM files
To the directory /DHS3ext/vg/flash/std for G711 files

Selecting custom messages

Custom files are transferred to the Call Server hard drive:
To the directory /DHS3ext/vgadpcm/flash/custom for ADPCM files
To the directory /DHS3ext/vg/flash/custom for G711 files

These messages correspond to a specific requirement and/or numbering plan

specific to an area or client company

All Rights Reserved © 2005, Alcatel-Lucent 19

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

243
All Rights Reserved © 2005, Alcatel-Lucent 20

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439P01TEUS Issue 05

244
Alcatel-Lucent OmniPCX Enterprise
Static voice guides

PROCEDURE

OBJECTIVE

- To learn how to load the static voice guides on the call server

OVERVIEW
Note: All numbers are given for example (e.g)

A voice guide comprises one or more voice messages. The purpose of the voice messages is to
assist users with phone operation and/or provide users with information.
Types of voice messages
Voice messages may be:

- Static: cannot be modified by the user:

Generic: compatible with generic numbering plans and offered in at least 6 different
languages for all countries.

Standard: adapted to a country with special requirements and/or a numbering plan

differing from the generic numbering plan.

Specific: to an area or a company.

Note: A static message file contains one or more messages.

- Dynamic: modifiable, recorded by users and/or managers via a Reflexes set or the AAS
application.
Note: A dynamic message file only contains one message.

External: music-on-hold (in most cases) played by a device external to the OmniPCX.

Issue 04 Ref. ENTP0439C01TEUS.doc P. 1

PROCEDURE

1. Install the static voice guides transfer tool on the PC

You need the system guides CD ROM which contains the transfer tool and voice guides to
implement static system voice guides.

On the PC
Action Install the VGTransfer Tool by double-clicking on < CD ROM
>:\install\cdvgtfr\setup.exe
Installation of the voice guides transfer tool:
« c:\program files\Alcatel\Voice guides transfert\bin\Voiceguidetft.exe »

2. Transfer of the system voice guides on the call server

On the PC
Action

Double-click on the VGTransfer Tool icon

Entry

Action
Click on “Ajouter” (Add)
Result

Action
Click on the button “Connexion”
Entry

P. 2 Ref. ENTP0439C01TEUS.doc Issue 04

Action In the window of the tool check that the FTP connection is established with
the CS.

Otherwise check that you can ping the CS from the PC.
Try a direct FTP connection:
- start: command: < cmd >
- ftp 155.132.6.1
- user: mtcl
- password: mtcl
If you’ve got the prompt you’ve got a problem with the transfer tool.
Install it again
If you have not the prompt and that the ping is ok there is a problem with
the ftp server.
Try the command: < service xinetd restart > logged as root to initialize
services driven by xinetd
Select

Action
Click on the button “Transférer” (Transfer) and
wait for the message “end of transfer”.
Check in the window “Fichiers” (File) that the default languages are
present in the CS hard disk.

This window gives the list of the voice guides files in

/DHS3ext/vgadpcm/flash/std
Now, you must choose the languages you want for downloading in each flash
of the GD and GA.

Issue 04 Ref. ENTP0439C01TEUS.doc P. 3

3. Declaration of voice guides and on hold music on the GD board

On mgr
Select Shelf
Board
Voice Guide Index MG
Action Create
Create Voice Guide Index MG
Entry
Shelf address: 1
Board address: 0
VG item: 1
Static voice guide index + 1 (French)

Action Validate
Action Create
Create Voice Guide Index MG
Entry
Shelf address: 1
Board address: 0
VG item: 2
Static voice guide index + 2 (English)

Action Validate
Remark The association between the indexes and the languages is done in this
menu:
System/Flash Voice Guides Configuration
Action Create
Create Voice Guide Index MG
Entry
Shelf address: 1
Board address: 0
VG item: 3
Static voice guide index + Music-on-hold

Action Validate
Select System
Tones
Action Delete
Entry Delete Tones
2
Action Validate

P. 4 Ref. ENTP0439C01TEUS.doc Issue 04

Remark:
The tone 2 has to be deleted and the voice guide 2 has to be managed in
order to use the internal music on hold broadcasted by the GD.
Select System
Voice Guides
Action Create
Create Voice Guides
Entry
Voice guide No: 2
Function + mono-message voice guide
Voice guide start + No
Backup tone: 56
Message by language
Message language 1: 2
Message language 1: 2
…

Action Validate

Issue 04 Ref. ENTP0439C01TEUS.doc P. 5

4. Checking of system voice guides

On the CS
Login mtcl
Command vgstat 1 0
etat_vg = VG_STABLE (0)
Result
Slot 1: Card status register = 4E Identifier = 3ba50162fraa
Static voice guides Language: 1 - FR0
Slot 2: Card status register = 4E Identifier = 3ba50162enaa
Static voice guides Language: 2 - EN0
Slot 3: Card status register = 4E Identifier =
Static voice guides Language: 21 - On hold music
…
Number of present messages = 163
Message syntax: xxxx = static, xxxx-d = dynamic, xxxx-D = dynamic and static
+------+ Press 'CR' to continue or 'q' to quit +------+
+--------------+------+------+------+------+------+------+------+------+------+
Guide Name Guide MsgLg1 MsgLg2 MsgLg3 MsgLg4 MsgLg5 MsgLg6 MsgLg7 MsgLg8
+--------------+------+------+------+------+------+------+------+------+------+
GPMERAC 3 3 271
GPNUMCOD 4 4 272
GPMANAUT 5 5 273
….

P. 6 Ref. ENTP0439C01TEUS.doc Issue 04

Voice Guides

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To ensure conference and voice guides maintenance

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439M01TEUS Issue 02

251
Voice Guides
Maintenance

Virtual GPA board checking

(6)xa000006> config 3 -v

+-------------------------------------------------------------------------+
| Cr | cpl | cpl type | coupler state | coupler ID |
|----|-----|--------------|--------------------------|--------------------|
| 3 | 0 | MGD | IN SERVICE| NO OPS FILE |
| 3 | 1 | MIX484 | IN SERVICE| NO OPS FILE |
| 3 | 2 | APA 8 | IN SERVICE| NO OPS FILE |
| 3 | 9 | BRA 4 | IN SERVICE| NO OPS FILE |
| 3 | 10 | UAI 8 | IN SERVICE| NO OPS FILE |
| 3 | 11 | SLI 4 | IN SERVICE| NO OPS FILE |
| 3 | 27 | GPA FICTIF | IN SERVICE| NO OPS FILE |
+-------------------------------------------------------------------------+

--- Inter Crystal Topology ---

+-------------------------------------------------------------------------+
| CR | CPL Type Role Free/Tot Role Type CPL | CR |
|-------------------------------------------------------------------------|
| 03 | 00 - MGD (MAIN ) --- 09/09 --- ( INT_A) INTIPA - 01 | 02 |
|-------------------------------------------------------------------------|

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439M01TEUS Issue 02

252
Voice Guides
Maintenance

(6)xa000006> vgstat 3 27

Slot 1: Card status register = 4E Identifier =

Static voice guides Language: 1 - FR0

Slot 2: Card status register = 4E Identifier =

Static voice guides Language: 2 - EN0

Slot 3: Card status register = 4E Identifier =

Static voice guides Language: 21 - On hold music

Slot 4: Card status register = 4E Identifier =

Static voice guides Language: 255 - Not used

Slot 5: No Memory Card

Number of present messages = 161

Message syntax: xxxx = static, xxxx-d = dynamic, xxxx-D = dynamic and static

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439M01TEUS Issue 02

253
Voice Guides
Maintenance

+---------------+------+------+------+------+------+------+------+------+------+
Guide Name Guide MsgLg1 MsgLg2 MsgLg3 MsgLg4 MsgLg5 MsgLg6 MsgLg7 MsgLg8
+---------------+------+------+------+------+------+------+------+------+------+
GPMERAC 3 3 271
GPNUMCOD 4 4 272
GPMANAUT 5 5 273
GPCONUDE 6 6 274
GPRV 7 7 275
GPRAPPEL 8 8 276
GPVONUM 9 9 277
GPRAPEET 10 10 278
GPRAPATT 11 11 279
GPATTRAPEET 12 12 280
GPEET 13 13 281
GPNUMAF 14 14 282
GPHEURDV 15 15 283
// // // //
+---------------+------+------+------+------+------+------+------+------+------+

Dynamic messages configured but not downloaded:

Dynamic messages waiting for download:
Available voice guides channels = 16
Active channel:

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439M01TEUS Issue 02

254
Voice Guides
Maintenance

Active voice guides:

(6)xa000006> vgemis

+------+-----------------+----+----+-----+------+---+-------------------------+
| guid | guide name | cr | cpl| term| neqt |lng| listeners neqt |
+------+-----------------+----+----+-----+------+---+-------------------------+
| 217 | GPUA_GUIDE | 3 | 27 | 0 | 321 | 1 | 471 |
+------+-----------------+----+----+-----+------+---+-------------------------+

Voice guide starting at the beginning

(6)xa000006> vgstart

--------------------------------------------------------------------
| VG message number | VG message label |starting at the beginning|
|--------------------------------------------------------------------|
| 71 | yes | |
| 72 | yes | |
| 73 | yes | |
| 74 | yes | |
| 75 | yes | |

All Rights Reserved © 2008, Alcatel-Lucent 5

Note: If the "Voice Guide Start" parameter of a voice guide is set to yes, each set of the Media Gateway listening simultaneously
to this guide will use one access. Otherwise, only one access is used to broadcast this guide, whatever the number of sets.

Whatever the value of this parameter, an IP-phone uses one access.

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439M01TEUS Issue 02

255
Voice Guides
Maintenance

Virtual GPA board equipment

(6)xa000006> cplstat 3 27

Logic coupler type : CPL_GPA ;

MAO coupler type : GPA FICTIF ;
Coupler state : IN SERVICE ;

Protocol country : FRA ( 5);

Ghost coupler neqt : 10520 ;

Detection equipments on this coupler:

- first dsp 0 terminal number : 0 ;
- last dsp 0 terminal number : 15 ;
- dsp 0 program : VG_PRG ;
Detection equipments on this coupler:
- first dsp 1 terminal number : 32 ;
- last dsp 1 terminal number : 63 ;
- dsp 1 program : CONFERENCE_PRG ;

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439M01TEUS Issue 02

256
Voice Guides
Maintenance

Detection equipments on this coupler:

- first dsp 2 terminal number : 64 ;
- last dsp 2 terminal number : 93 ;
- dsp 2 program : DTO_R2_PRG ;

Voice guide equipments on this coupler:

- voice guide state : VG_STABLE ;
- first vg terminal number : 0 ;
- last vg terminal number : 15 ;
More information about voice guide may be displayed by vgstat 3 27

Type of tone emitter registered on this coupler:TONE_R2;

Tone emitter state on this coupler : EM_R2;

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439M01TEUS Issue 02

257
Voice Guides
Maintenance

“incvisu”

03/00/-/---|= 4:0740=Beginning of an INT/IP downloading @:00.80.9f.2e.41.cc (vgadpcm.FR0)

03/00/-/---|= 5:0741=End of downloading of an INT/IP board @:00.80.9f.2e.41.cc (vgadpcm.FR0)
03/00/-/---|= 4:0740=Beginning of an INT/IP downloading @:00.80.9f.2e.41.cc (vgadpcm.EN0)
03/00/-/---|= 5:0741=End of downloading of an INT/IP board @:00.80.9f.2e.41.cc (vgadpcm.EN0)
03/00/-/---|= 4:0740=Beginning of an INT/IP downloading @:00.80.9f.2e.41.cc (adpcmmoh)
03/00/-/---|= 5:0741=End of downloading of an INT/IP board @:00.80.9f.2e.41.cc (adpcmmoh)

All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Voice Guides

Ref. ENTP0439M01TEUS Issue 02

258
Alcatel-Lucent OmniPCX Enterprise
Voice guides

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to install the system voice guides and to operate the system voice guides

MANAGEMENT

1. Install the voice guide transfer tool on the PC.

2. Transfer the voice guides from the PC to the call server.

3. Manage 2 languages on the GD.

3.1. Language 1: English

3.2. Language 2: French

4. Manage the internal music on hold

5. Restart the GD and check the uploading of the voice guides.

6. Use the “vgstat” command to check the presence of the voice guide on the GD.

Issue 02 Ref. ENTP0439H02TEUS.doc HO. 1

HO. 2 Ref. ENTP0439H02TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

261
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

262
Alcatel-Lucent OmniPCX Enterprise

Entities

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the principles and components of the Entity

Alcatel-Lucent OmniPCX Enterprise – Entities

Ref. ENTP0417P03TEUS Issue 02

263
Entity
Overview

Single entity

Same behavior for all

Company “Thomas Consulting”

Department 1 Department 2 Department 3

Entity 1

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Entities

Ref. ENTP0417P03TEUS Issue 02

264
Multi-Entities
Overview

Several entities

Specific behavior per department (entity)

Company “Thomas Consulting”

Department 1 Department 2 Department 3

Entity1 Entity 2 Entity 3

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Entities

Ref. ENTP0417P03TEUS Issue 02

265
Entity - features
Call Distribution

Each system entity can be associated a directory number (most of the time a
“DDI number”) corresponding to the company or department number

This number is used to access to a Call routing (distribution) table which

allows an optimization of the call routing (no lost call)

This table is made of 4 different status (day, night , mode1, mode 2). Each status
can have its own routing functioning

The switch from a state to another can be done automatically by the changeover
time management or by an action from an attendant associated to this entity

This configuration is optional

Each entity has its own Calls Distribution Table

A prefix (Entity Call) allows to access to this table

All Rights Reserved © 2008, Alcatel-Lucent 4

An optional Attendant group manager can be associated to the Entity

This attendant group number has two main functions:

- The entity status (day, night,…) follows the associated attendant group status if “attendant group” is notified in the
“changeover time”

- The attendants, who have the right and who belongs to this attendant group, can manage (modify) the elements associated
to this entity:
- Traffic overflow
- Entity routing numbers (CDT)
- Entity state (day, night, mode 1, mode 2), “force a state”
- Entity changeover time “modify the switching time between states”
- Access to the ranges of the speed dialing
- Station and directory number

Alcatel-Lucent OmniPCX Enterprise – Entities

Ref. ENTP0417P03TEUS Issue 02

266
Entity - features
Call Distribution : Changeover time

This feature allows to split a day in 4 different periods

Each period can correspond to a specific status of the company (opening hours,
midday break, night hours…)

A specific dedicated routing can be configured

The entity switches automatically from a status to another

It is possible to manage separately:

Incoming calls changeover time, which modifies (according to the CDT

management) the routing of the incoming calls remaining unanswered

Outgoing calls changeover time, which modifies the behavior on outgoing calls
(according to the “barring rules” and “public access class of service”)

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Entities

Ref. ENTP0417P03TEUS Issue 02

267
Entity - features
Calling Line Identification

Making an outgoing call, it can be useful to sent his/her identification

To allow the remote destination to recognize the caller
To allow the callback feature in case of unanswered calls

The Alcatel-Lucent OmniPCX Enterprise uses several ways to setup the Caller Id.
Among them, the Entity provides two elements

Installation number (ISDN)

This section contains the first digits of the company's directory numbers preceding
the DDI numbers
This number followed by a DDI station number is transmitted if the subscriber (of this
entity) is in the position "send identity” for the outgoing calls

Supplementary installation number

This section contains a DDI number (usually the attendant one or the entity call
number)
If the subscriber is non DDI: this supplementary number is transmitted after the installation
number,
If the subscriber is DDI: it is the translated station number of the DDI caller which is transmitted instead
of this supplementary number after the installation number.

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Entities

Ref. ENTP0417P03TEUS Issue 02

268
Entity - features
Miscellaneous

Music on hold

It is the tone (or voice guide) broadcasted when a user from this entity put
someone on hold

Attendant waiting guide

This concerns the voice guide broadcast during an external call overflowing
to a Call Distribution Table before the attendant off hook (by default: voice
guide 110)

In case of Call Barring feature use, the Entity is a bridge between the different
involved elements

The entity allows to use some common services to all the users belonging to this
Entity
LDAP, Secret Id …

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – Entities

Ref. ENTP0417P03TEUS Issue 02

269
All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Entities

Ref. ENTP0417P03TEUS Issue 02

270
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

271
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

272
Alcatel-Lucent OmniPCX Enterprise

Extensions Range

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Alcatel-Lucent OmniPCX Enterprise extension ranges

Alcatel-Lucent OmniPCX Enterprise – Extensions Range

Ref. ENTP0403P01CLUS Issue 01

273
Alcatel-Lucent IP extensions
X8 Series

4068 4038 4028 4018 4008

- Adjustable graphical - Adjustable graphical - Adjustable graphical - 1x20 character display - 1x20 character display
color display 4 grey level display B&W display
- 2 direction navigator - 2 direction navigator
- 4 direction navigator - 4 direction navigator - 4 direction navigator
- Hands Free - Hands Free
- Direct access to directory - Direct access to directory - Direct access to directory
- Mute key - Mute key
- Hands Free - Hands Free - Hands Free
- Redial key - Redial key
- Mute key - Mute key - Mute key
- Direct access to mailbox - Direct access to
- Redial key - Redial key - Redial key mailbox
- 6 programmable key
- Direct access to mailbox - Direct access to mailbox - Direct access to mailbox - 6 programmable keys
- Comfort Handset
- 10 soft keys (contextual) - 10 soft keys (contextual) - 6 soft keys (contextual) - Standard Handset
- PC Connectivity
- 40 programmable soft keys - 40 programmable soft keys - 40 programmable soft keys
- 2 personal keys (F1 & F2) - 2 personal keys (F1 & F2) - 2 personal keys (F1 & F2)
- Additional 10/40 key modules - Additional 10/40 key modules - Additional 10/40 key modules
- Alphabetic keyboard - Alphabetic keyboard - Alphabetic keyboard
- Comfort Handset - Comfort Handset - Comfort Handset
- Specific headset plug 3.5mm - Specific headset plug 3.5mm - Specific headset plug 3.5mm
- PC Connectivity - PC Connectivity - PC Connectivity
- Bluetooth 1.2

All Rights Reserved © 2008, Alcatel-Lucent 2

All the IP Touch x8 Series are IEEE 802.3af full compliant, and are Class 2 in class of consumption

Alcatel-Lucent OmniPCX Enterprise – Extensions Range

Ref. ENTP0403P01CLUS Issue 01

274
Alcatel-Lucent TDM extensions
X9 Series

4039 4029 4019

- Adjustable graphical - Adjustable graphical - 1x20 character display

4 grey level display B&W display - 2 direction navigator
- 4 direction navigator - 4 direction navigator - Hands Free
- Direct access to directory - Direct access to directory - Mute key

- Hands Free - Hands Free - Redial key

- Direct access to mailbox
- Mute key - Mute key
- 6 programmable key
- Redial key - Redial key
- Comfort Handset
- Direct access to mailbox - Direct access to mailbox
- 10 soft keys (contextual) - 6 soft keys (contextual)
- 40 programmable soft keys - 40 programmable soft keys
- 2 personal keys (F1 & F2) - 2 personal keys (F1 & F2)
- Additional 10/40 key modules - Additional 10/40 key modules
- Alphabetic keyboard - Alphabetic keyboard
- Comfort Handset - Comfort Handset
- Specific headset plug 3.5mm - Specific headset plug 3.5mm

All Rights Reserved © 2008, Alcatel-Lucent 3

TDM: Time Division Multiplexing

Alcatel-Lucent OmniPCX Enterprise – Extensions Range

Ref. ENTP0403P01CLUS Issue 01

275
Alcatel-Lucent extensions 8 & 9 Series
Enhanced functionalities

Intuitive icons and soft keys

Determining the status of a call is simple with the help of easy-to-understand
icons. The phones’ smart soft functions change according to the call context,
with the functions displayed on the screens. Extra programmable keys are
provided to further customize usage

Application openness (X8 Series only)

For customized third-party applications (Web services)
XML openness only available on IP Touch range

Alphanumeric Keyboard
The Alcatel-Lucent 4028, 4038 and 4068 IP Touch terminals are equipped
with an alphabetic keyboard, which provides access to the “call by name”
company directory and to messaging services

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Extensions Range

Ref. ENTP0403P01CLUS Issue 01

276
Alcatel-Lucent extensions 8 & 9 Series
Enhanced functionalities

Navigator

The Alcatel-Lucent IP Touch phone navigator feature makes the display more user-friendly
by allowing to scroll up, down, left and right. The navigator, along with the context-
sensitive soft keys, provides easy access to the Alcatel-Lucent’s many features

Dedicated function keys

At the push of a button, gain direct access to the mailbox or phone directory, simply redial
or ask the terminal for help. Audio control functions (loudspeaker volume control, hands
free audio control, mute, etc.) are separate from the system’s functional keys to facilitate
easy and clear audio control for the user

Security (X8 Series only)

The IP Touch Security Solution allows to encode the communication via IP,
useful against intrusion and hacking

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Extensions Range

Ref. ENTP0403P01CLUS Issue 01

277
Alcatel-Lucent extensions
Extension modules

A smart display module

14 direct access keys
Large LCD display for paperless identification of associated keys

Add on modules
10 keys
10-keys
40-keys

Up to 3 modules can be linked to a phone set

Smart display

Commercial packs including phone set + 10-key Add on module:

4038 & 4039 pack10
4028 & 4029 pack10
40 keys
These extension modules are available for
4068/4038/4028 and 4039/29

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Extensions Range

Ref. ENTP0403P01CLUS Issue 01

278
Option on X8/X9 series sets

Display view angle

Big foot Standard foot

at least
60°
30°

With standard foot

Max 55°
With big foot

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – Extensions Range

Ref. ENTP0403P01CLUS Issue 01

279
Plugwares for X9 Series

The plugware is used to connect a device behind the X9 Series extension

According to the type, a plugware has a specific function

Type “V24/CTI”, used to connect

A PC behind a set (CTI link)

Calls management and supervision

A data terminal (V24 link)

VT100 connection for system management

Type “Analog”, used to connect an analog device (modem, fax group 3)

Type “S0”, used to connect a fax (group 4)

All Rights Reserved © 2008, Alcatel-Lucent 8

A plugware can be used “alone”, the position of a jumper has to be changed (refer technical documentation for more
information)

CTI : Computer Telephony Integration

Alcatel-Lucent OmniPCX Enterprise – Extensions Range

Ref. ENTP0403P01CLUS Issue 01

280
Omni Mobility DECT
Characteristics

Mobile 400
GAP and GAP+
Color (4096 colors 98 x 66 pixels)
Headset connection
Loudspeaker
Navigator
Backlight (display and keyboard)
Integrated antenna
Vibrator
Battery: Loading time: 210 min
Autonomy: 20h in communication and 160h in idle state
Mobile 300
GAP and GAP+
Black & white display (96 x 48 pixels)
Navigator
Backlight (display)
Integrated antenna
Battery: Loading time: 210 min
Autonomy: 20h in communication and 160h in idle state

All Rights Reserved © 2008, Alcatel-Lucent 9

DECT: Digital Enhance Cordless Telecommunication

Desktop Charger

Bi-position Desktop charger

Alcatel-Lucent OmniPCX Enterprise – Extensions Range

Ref. ENTP0403P01CLUS Issue 01

281
VoWLAN Infrastructure
Mobile IP Touch

Mobile IP Touch

Mobile IP Touch are members of the IP Touch family

The classical IP features are available on the set :

Direct RTP
IP domains
Voice compression (G729) or not (G711)(1)
G723 is not supported
Compatible with 802.11b, 802.11a, 802.11g

MIPT 310 MIPT 610

All Rights Reserved © 2008, Alcatel-Lucent 10

(1) G711(A and µ law): Bit Rate of 64Kbps

- Provides the highest level of Voice quality when there is no bandwidth concern (LAN)
G729A: Bit Rate of 8Kbps (decreased Bandwidth consumption)
-Higher gain on WAN

Alcatel-Lucent OmniPCX Enterprise – Extensions Range

Ref. ENTP0403P01CLUS Issue 01

282
Alcatel-Lucent OmniPCX Enterprise

IP Phone Specificities

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Alcatel-Lucent IP-Touch 8 Series specificities

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

283
IP-Touch specificities
Generalities

The IP Touch is an Alcatel–Lucent IP Terminal connected to the LAN and allows

to connect an other peripheral on a switched port.

The IP Touch has to communicate to the OmniPCX Enterprise Call Server:

Via an INT-IP A virtual board on common hardware

Via a real INT-IP A board on Crystal hardware

All Rights Reserved © 2008, Alcatel-Lucent 2

One INT-IP A can managed the signaling of 4000 IP Touch sets max.

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

284
IP-Touch specificities
IP configuration: Two methods

The IP configuration of the set can be managed:

In static IP configuration mode

The configuration is stored on the device flash

In dynamic IP configuration mode

The OmniPCX Enterprise acts as a DHCP Server or as a DHCP relay
Use of an external DHCP server of the customer

The binaries are downloaded in the set from the Call Server of the OmniPCX
Enterprise

The IP set must be connected to the INTIP-A board to exchange the UA

signaling.

The voice is sent using RTP channels.

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

285
IP-Touch specificities
Extension startup

The initialization phase of the IP set starts when the set is powered.

During the initialization, it is possible to access manually to the IP parameters

management.

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

286
IP-Touch specificities
Extension startup

Initialization cycle after management of the flash memory:

IP configuration loading in memory

Request of the lanpbx.cfg file using the IP address managed as TFTP Server
in the IP parameters of the set
This address corresponds to the MAIN IP address of the Call Server

Request of the file containing the software of the IP Phone from the Call
Server. The software will be loaded in the memory of the set.

Request of the file containing the UDP port number used for the signaling
channel establishment from the Call Server in the memory of the set.

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

287
IP-Touch specificities
Overview

The IP Phone generates a tone and displays: POSTE

Enter a directory number of a IP Phone already created in the system
database

The IP Phone generates a tone and displays: CODE

Enter the personal code of the set

The system updates the database with the MAC address and the IP address of
the set. The set switches into in service state if:
The directory number entered is available
The personal code entered is the correct one

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

288
IP-Touch specificities
Overview

Connection of an IP Phone already registered:

Complete initialization procedure

The system checks that the MAC address is known in the database and
updates the IP address if necessary.

The set switches into in service state.

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

289
IP-Touch specificities
Overview

For the dynamic IP configuration of an IP Phone, a DHCP server is necessary.

DHCP: Dynamic Host Configuration Protocol

Protocol used between a server and a client

Used by the OmniPCX Enterprise to provide dynamically the IP configuration

of the IP sets:
IP address
Subnet mask
Gateway IP address
TFTP server IP address

All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

290
IP-Touch specificities
Overview

The internal DHCP server of the OmniPCX Enterprise can provide an IP

configuration to Alcatel-Lucent clients (IP sets, GD or INTIPB boards) but it can
also be used for others types of clients (PC, etc.)

The IP Phones can accept the IP configuration provided by the OmniPCX

Enterprise DHCP Server or by an external DHCP server.

If two types of DHCP server are present on a LAN, the Alcatel-Lucent clients
will respond first to the OmniPCX Enterprise.

All Rights Reserved © 2008, Alcatel-Lucent 9

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

291
IP-Touch specificities
Overview

The initialization phase of an IP Phone starts when the set is powered.

During the initialization, it is possible to switch the working mode of the sets in
dynamic configuration mode.

Initialization cycle after management of the flash memory:

Search for a DHCP server to get an IP configuration
The next steps are identical to the initialization steps of an IP Phone in static
mode.

All Rights Reserved © 2008, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

292
IP-Touch specificities
Overview

The direct RTP is valid for:

IP Touch sets registered on the same node
IP Touch sets registered on different nodes if the direct RTP in network has
been activated on the nodes

The direct RTP allows to optimize the use of the compressors when two IP
Touch sets are in communication:
No compressor for the board are used during the call
There is a direct RTP channel between the two sets

All Rights Reserved © 2008, Alcatel-Lucent 11

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

293
IP-Touch specificities
Overview

The INTIP-A board sends to the IP Touch sets the IP address of the remote
extension. It also sends the UDP port number to be used by the sets to establish
themselves their communications.
Signaling exchange with the INTIP-A board
Direct exchange of voice data between the sets

The IP Touch sets generate locally the tones and must establish a connection to
the GD board to receive the voice guides and the on hold music.

All Rights Reserved © 2008, Alcatel-Lucent 12

Alcatel-Lucent OmniPCX Enterprise – IP Phone Specificities

Ref. ENTP0403P11TEUS Issue 02

294
Alcatel-Lucent OmniPCX Enterprise

Internal DHCP Server

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To manage the internal DHCP server for Alcatel-Lucent IP-Touch 8 Series extensions

Alcatel-Lucent OmniPCX Enterprise – Internal DHCP Server

Ref. ENTP0403C03TEUS Issue 02

295
Internal DHCP Server
Main parameters

/DHCP Configuration (Review/Modify)

Configuration + DHCP Server

Alcatel-Lucent terminals only + Yes (1)

/DHCP Configuration/CPU Main Sub-network

Subnet address: CPU-network-Id

Automatically updated
Subnet mask: CPU-sub-netmask according to the
Broadcast address: Broadcast @ for the CPU sub-network “netadmin” information

Default router address: (2)

TFTP Server address: (3)

All Rights Reserved © 2008, Alcatel-Lucent 2

(1) By default, the Alcatel-Lucent OmniPCX Enterprise system provides dynamic IP configurations only to proprietary devices
(when the internal DHCP service is activated).
If the internal DHCP Server has to provide IP configurations to none Alcatel-Lucent devices, this configuration object has to be
set to: No

(2) The “default router” has to be configured manually. Even a default router is managed in “netadmin configuration”, this
object is not automatically updated!

(3) In most of the cases, this field has to remain empty! It has to be filled in only when using an external TFTP Server.

Alcatel-Lucent OmniPCX Enterprise – Internal DHCP Server

Ref. ENTP0403C03TEUS Issue 02

296
Internal DHCP Server
Device IP address configuration

/DHCP Configuration/CPU Main Sub-network

/IP Address Range (local subnet) (Create)

First address in range : Set up the first and the last (1)
IP address of the local subnet range
End of address range :

/Static IP Address (local subnet) (Create)

IP address : IP @ of the expected device

MAC Address : MAC @ of the expected device
TFTP Server address : (2)

Configuration file + None (3)

/DHCP configuration/Apply modifications (Review/Modify)

Valid the given message window

All Rights Reserved © 2008, Alcatel-Lucent 3

(1) In case of an unique IP address add-on, the first and last address are the same

(2) The TFTP Server address field has to remain empty, except in case of external TFTP server use where this field has to be the
External Server TFTP Server IP address.

(3) This configuration file field corresponds to the boot file to be used by the given device. In case of IP Touch 8 Series extension
use, let this field equal to None.

In case of board loading (flashing, CPU loading…) the board type has to be selected (a specific file is therefore provided):
PXE:/bootp/linux/pxe/pxeloader
CSE:/bootp/linux/linux.ram
Alize:/bootp/linux/alize/startup
GD:/DHS3bin/downbin/emg/binmgstart
MIPT:/DHS3bin/downbin/wifi/slnk_cf
Other

Alcatel-Lucent OmniPCX Enterprise – Internal DHCP Server

Ref. ENTP0403C03TEUS Issue 02

297
All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Internal DHCP Server

Ref. ENTP0403C03TEUS Issue 02

298
Alcatel-Lucent OmniPCX Enterprise
UA & Analog users management (MGR)

PROCEDURE

OBJECTIVE

- To learn how to create UA and Analog users

OVERVIEW
Create and manage the subscribers:

- Internal numbers range

- Extensions creation
- 4039 (x9 series)
- 4029 (x9 series)
- 4019 (x9 series)
- Analog

Issue 02 Ref. ENTP0403C05TEUS.doc P. 1

PROCEDURE

1. Validate the Reflexes sets automatic recognition

Application On mgr
Path /System/Other system parameters/System parameters
Action Review/modify
Select Force type identification is on
Entry Force type identification is on + True

Note: The system detects the type of set and changes it automatically in management

2. Update the internal numbers ranges created

Application On mgr
Path System / Free numbers ranges list
Action Create
Entry Name : user
Range beginning : 31000 (e.g.)
Range End : 31999 (e.g.)
Priority + True
Digits Authorized + 0,1,2,3,4,5,6,7,8,9
Max.number : 10

Note: Priority: YES: during a search for free directory numbers, the search will be made
on the priority range if no range is specified
Max.number: This attribute limits the number of free directory numbers that are
displayed
For example, when set to 10: only the ten first free directory numbers will be
displayed

P. 2 Ref. ENTP0403C05TEUS.doc Issue 02

3. Display free directory numbers

Application On mgr
Path /System /Free directory numbers
Action Review/Modify
31000 31005
Entry 31001 31006
31002 31007
31003 31008
31004 31009

Note: The system display 10 free numbers. Link to the previous managed parameters

4. Display free addresses for UA sets

Application On mgr
Path /System / Free address
Action Review/modify
Select All Instances
Set filters (valid)
Select Terminal Type (valid)

Note: Displayed message : “Terminal Type == Z Or UA Or ELN”

- Select the expected filter type (== ; != ;>= ; <=) pressing “Enter” to change
- Then, press the right arrow (of the keypad) to select the equipment type,
pressing “Enter” to change the value

Entry Terminal type == UA

0- 0- 0
Result 0- 0- 1
0- 0- 2
0- 0- 3
. . .

Issue 02 Ref. ENTP0403C05TEUS.doc P. 3

5. Display free addresses for Analog sets

Application On mgr
Path System / Free address
Action Review/modify
Select All Instances
Set filters (valid)

Note: Displayed message : “Terminal Type == Z Or UA Or ELN”

Entry Terminal Type == Z

0- 1- 0
Result 0- 1- 1
0- 1- 2
. . .

6. Create a user on UA set

Application On mgr
Path Users
Action Create
Entry Directory Number : 31000 ( Select a number on list .See 3)
Shelf Address : 255
Board Address : 255
Equipment Address : 255
Set Type + 4029

Note: Directory number : select the number in the list

Physical addresses : select the number in the list (see 4) or -1 / -1 / -1 for
automatic allocation or 255/255/255 for resurrection
Set type : select the right type in the list (4019/4029/4039)

Action Press CTRL+V or F1 to validate the creation

Action Press CTRL+C as many times as needed to come back on the main menu

Note: It is also possible to access directly to the main configuration page pressing “ctrl
o” ten selecting “Open a new window”

P. 4 Ref. ENTP0403C05TEUS.doc Issue 02

7. Create a user on Analog set

Application On mgr
Path Users
Action Create
Entry Directory Number : 31100 ( Select a number on list .See 3)
Shelf Address : -1
Board Address : -1
Equipment Address : -1
Set Type + Analog

Note: Directory number : select the number in the list

Physical addresses : select the number in the list (see 4) or -1 / -1 / -1 for
automatic allocation or 255/255/255 for resurrection
Set type : select the right type in the list (analog)

Action Press CTRL+V or F1 to validate the creation

Action Press CTRL+C as many times as needed to come back on the main menu

Note: It is also possible to access directly to the main configuration page pressing “ctrl
o” ten selecting “Open a new window”

Issue 02 Ref. ENTP0403C05TEUS.doc P. 5

8. Display terminal status

Application On the call server

+COUPLER_INFORMATIONS -----------------------------------------------+
| Logic coupler type : CPL_UA |
| MAO coupler type : UA32 |
| Coupler state : IN SERVICE |
+-----------------------------------------(PRESS ANY KEY TO CONTINUE)+

[1] : Device features.

[2] : Forward informations.
[3] : Subdevice informations.
[4] : Demi-com informations.
[5] : Reset the device.

[1] : Device features

+UA TERMINAL --------------------------------------------------+

P. 6 Ref. ENTP0403C05TEUS.doc Issue 02

9. Display terminal status

Application On the call server

Wed Jul 4 11:35:29 CEST 2007

-------------------------------------------------------------------------
|Coupler: 0 0 Logic type: CPL_UA Board: UA32 State: IN SERVICE |
|-------------------------------------------------------------------------|
| Cry:Cpl:ac:term| neqt | typ term | dir nb | Out of service cause |
|-------------------------------------------------------------------------|
| 0 0 0 0 | 00257 | 4029 | 31000 | . . . . . . . . . . |
| 0 0 0 1 | 00258 | T_RESU | | A . I . . . . . . . |
| 0 0 0 2 | 00259 | T_RESU | | A . I . . . . . . . |
| 0 0 0 3 | 00260 | T_RESU | | A . I . . . . . . . |
| 0 0 0 4 | 00261 | T_RESU | | A . I . . . . . . . |
| 0 0 0 5 | 00262 | T_RESU | | A . I . . . . . . . |
| 0 0 0 6 | 00263 | T_RESU | | A . I . . . . . . . |
...
| 0 0 0 22 | 00279 | T_RESU | | A . I . . . . . . . |
| 0 0 0 23 | 00280 | T_RESU | | A . I . . . . . . . |
| 0 0 0 24 | 00281 | T_RESU | | A . I . . . . . . . |
| 0 0 0 25 | 00282 | T_RESU | | A . I . . . . . . . |
| 0 0 0 26 | 00283 | T_RESU | | A . I . . . . . . . |
| 0 0 0 27 | 00284 | T_RESU | | A . I . . . . . . . |
| 0 0 0 28 | 00285 | T_RESU | | A . I . . . . . . . |
| 0 0 0 29 | 00286 | T_RESU | | A . I . . . . . . . |
| 0 0 0 30 | 00287 | T_RESU | | A . I . . . . . . . |
| 0 0 0 31 | 00288 | T_RESU | | A . I . . . . . . . |
|-------------------------------------------------------------------------|
| (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 : 1 |
|-------------------------------------------------------------------------|

Issue 02 Ref. ENTP0403C05TEUS.doc P. 7

10. Edit users

Application On the call server

enter criteria or command: pos

enter criteria or command: typ

1 - dir -> Directory number

2 - act -> ACT shelf number
3 - cpl -> Coupler number
4 - pos -> Terminal number
5 - typ -> Station type
==========================
enter criteria or command: go

+--------+---+---+---+--------+
Result |dir |act|cpl|pos|typ |
+--------+---+---+---+--------+
|31000 | 0| 0| 0|IPT_4029|
|31100 | 0| 1| 0|ana |

P. 8 Ref. ENTP0403C05TEUS.doc Issue 02

PROCEDURE

OBJECTIVE

- To learn how to create a the Alcatel-Lucent x9 Series and Analog extension type

OVERVIEW
This procedure will learn you how to create the subscribers of the Alcatel-Lucent OmniPCX
Enterprise

Issue 01 Ref. ENTP0403C06TEUS.doc P. 1

PROCEDURE

1. Validate the extension sets automatic recognition

Application Configuration Tab PCX

Path / System/Other system parameters/ System parameters
Object Force type identification is on:
Action Click on “ ” to valid

Note: The system detects the type of set and changes it automatically in management

2. Create a range of available directory numbers for subscribers

Application Configuration Tab PCX

Path / System / Free numbers ranges list
Action Create
Tab All
Parameters Name: Extension
Range beginning: 31000 (e.g.)
Range End: 31999 (e.g.)
Priority + True
Digits Authorized + 0,1,2,3,4,5,6,7,8,9
Max.number: 10

Note: Priority: True: during a search for free directory numbers, the search will be made
on the “priority range” if no range is specified
Max.number: This attribute limits the number of free directory numbers that are
displayed
For example, when set to 10: only the ten first free directory numbers will be
displayed

P. 2 Ref. ENTP0403C06TEUS.doc Issue 01

3. Display free directory numbers

Application Configuration Tab PCX

Path /System /Free directory numbers
Action Open/Close
Result 31000 31005
31001 31006
31002 31007
31003 31008
31004 31009

Note: The system display 10 free numbers. Link to the previous managed parameters

4. Display free addresses for UA sets

Application Configuration Tab PCX

Path / System / Free addresses
Action Open/Close

Note: It is interesting to use some “filters” in order to refine the expected result.
In the following result, a double filter is used, a first one to filter the Shelf “1”;
The second one to filter the set type « UA » (x9 Series)
the result will be the list of all te UA set in the shelf « 1 »

Application Configuration Tab PCX

Path / System / Free addresses
Action Filter. . .
Action

Result

Issue 01 Ref. ENTP0403C06TEUS.doc P. 3

5. Create a x9 Series extension

Application Configuration Tab PCX

Path / Users
Action Create
Tab General Characteristics
Entry Directory Number: 31000
Directory Name: Renault
(*)
Directory First Name: Jean
Shelf Address: 1
Board Address: 1
Equipment Address: 0
Set Type + 4029
Tab Facilities
Parameter Dial by name and text msg.: Yes
Action Click on “ ” to valid

Note: Directory number: select the number in the list

(*)Using a double click on the « Directory number » field, you access directly to the
list of free numbers (the length of displayed numbers depends on configuration
realized at the point 3 of this procedure)
Physical addresses: select the number in the list (see 4) or -1 / -1 / -1 for
automatic allocation or 255/255/255 for resurrection
Set type: select the right type in the list (4019/4029/4039)

P. 4 Ref. ENTP0403C06TEUS.doc Issue 01

6. Create an Analog set

Application Configuration Tab PCX

Path / Users
Action Create
Tab General Characteristics
Entry Directory Number: 31000
Directory Name: Le Doux
(*)
Directory First Name: Pierre
Shelf Address: 1
Board Address: 3
Equipment Address: 0
Set Type + Analog
Action Click on “ ” to valid

Note: Directory number: select the number in the list

7. Creation of the Alias(es)

Application Configuration Tab PCX

Path / Users <select a directory number e.g.31000 > / User Aliases
Action Create
Parameters Alias No.: 1
Directory name: Tech-Lab
Directory First name: Telecom
Can be Called/Dialed By Name: Yes
Action Click on “ ” to valid

Note: The alias management is useful when an extension is shared between several
persons or, used for different functions

Issue 01 Ref. ENTP0403C06TEUS.doc P. 5

P. 6 Ref. ENTP0403C06TEUS.doc Issue 01

All Rights Reserved © 2008, Alcatel-Lucent
312
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

PROCEDURE

OBJECTIVE

- To learn how to configure the Alcatel-Lucent 8 series sets

OVERVIEW
The e-Reflexes set has an IP address for calls made over IP network and a QMCDU (user) call
number to communicate with other sets on the telephone network. The host PCX performs
address conversion.
To operate, the e-Reflexes requires:
IP parameters: IP address, IP mask,…
A telephone binary linked to the PCX release.
They can be assigned by static or dynamic configuration.
In case of static IP configuration, the manager defines the IP data set by set.

Issue 04 Ref. ENTP0487C01TEUS.doc P. 1

All Rights Reserved © 2005, Alcatel-Lucent
313
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

PROCEDURE

1. User creation

Application mgr
Path Users
Action Creation
Parameters Directory number:
Directory name:
Directory first-name:
Shelf address: 255
Board address: 255
Equipment address: 255
Set Type: + IP Touch 4068
IP Touch 4038
IP Touch 4028
IP Touch 4018

2. Forward management if IP extension out of service

Application mgr
Path Categories / Phone Facilities Categories
Action Review / Modify
Entry Phone COS id: 0
Action Apply
Remark 32 COS ( 0 to 31). Example with the applications COS “0”
Result Phone COS id: 0
Rights
Forward if MIPT/IP out of service: 1
Action Press CTRL+V
Remark During the “out of service” state, the IP phone is seen as “immediately
forwarded” to the associated . Manage the associated set in the user’s
parameters.
If an “Immediate Forward” was configured before the switchover to the out
of service state, this forward has the priority in front of this feature.

P. 2 Ref. ENTP0487C01TEUS.doc Issue 04

All Rights Reserved © 2005, Alcatel-Lucent
314
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

3. Management of the “Applications COS”

Application mgr
Path Alcatel-Lucent 8&9 Series / Series 8&9 classes of service / COS applications
Action Review / Modify
Entry Applications COS id: 0
Remark 32 COS ( 0 to 31), example with the application COS “0”
Result Applications COS id: 0
Settings
Priority: 1
Redial
Priority: 2
Appointment
Priority: 3
Lock
Priority: 4
Text Mail
Priority: 5
Forward
Priority: 6
No reply
Priority: 7
External application Number: 0

Note: The priority value corresponds to the location of the “feature” on the extension
display (0= not displayed; 1= upper left; 2=upper right …).
If some external applications are set up (associated to the PRS), the corresponding
“applications id” will be displayed, and a priority value can be given to those
applications

Issue 04 Ref. ENTP0487C01TEUS.doc P. 3

All Rights Reserved © 2005, Alcatel-Lucent
315
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

4. Management of the Phone COS

Application mgr
Path Alcatel-Lucent Series 8&9 / Series 8&9 classes of service / Phone COS
Action Review / Modify
Entry Phone COS id: 0
Action Apply
Remark 32 COS ( 0 to 31). Example with the applications COS “0”
Result Phone COS id: 0
Right Modify default Home Page: Yes/ No
Remark This management field allows the user to modify (according to his needs)
his IP Touch “Home page”
To determine the default “Home page”, refer to the step “4”

5. Manage the IP Touch parameters

Application mgr
Path Users/ 8&9 Series Parameters
Action Review / Modify
Entry All instances ]
Directory number: xxxxx
Remark Select [ All instances ] by pressing “return” key. Then enter a directory
number of an IP Touch phone
Result Directory number: xxxxx
Application COS id: 0
Phone COS id: 0
Default HomePage: Home Perso

Note: Select an Application COS between 0 to 31

Select a Phone COS between 0 to 31
(1) Default Home Page, 4 available choices:
(2) Home Perso, Home info, Home menu, Home appli (only available in case of PRS)
In case of use of external applications (PRS), an external application can be
selected as a default “Home page”. “Home appli” has to be selected, and the
application “id” has to be added

P. 4 Ref. ENTP0487C01TEUS.doc Issue 04

All Rights Reserved © 2005, Alcatel-Lucent
316
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

6. IP configuration setup of the Alcatel-Lucent 8 series terminal: static mode

Application On the station

Action Re-initialize the Alcatel-Lucent series 8 extension
Remark To reset an Alcatel-Lucent 8 series terminal, power it off then power it on
Result

Initializing

Action Press “i” key then “#” key

Result Main Menu

Mac Address IP Parameters

Versions Miscellaneous
IP Memory Ethernet link

Action Select « IP Parameters »

Action Main Menu

Mac Address IP Parameters

Versions Miscellaneous
IP Memory Ethernet link

Result IP Parameters

IP Mode Dynamic
IP addr 255.255.255.255
Subnet 255.255.255.255
Router 255.255.255.255

Issue 04 Ref. ENTP0487C01TEUS.doc P. 5

All Rights Reserved © 2005, Alcatel-Lucent
317
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

Action Select « IP Mode »

Action
IP Parameters

IP Mode Dynamic
IP addr 255.255.255.255
Subnet 255.255.255.255
Router 255.255.255.255

Remark Press the left key then the right key to modify the mode
Result
IP Parameters

IP Mode Static
IP addr 255.255.255.255
Subnet 255.255.255.255
Router 255.255.255.255

Action Select « IP addr », then enter the IP address

Action
IP Parameters

IP Mode Static
IP addr 255.255.255.255
Subnet 255.255.255.255
Router 255.255.255.255

Result
IP Parameters

IP Mode Static
IP addr 010.001.002.006
Subnet 255.255.255.255
Router 255.255.255.255

P. 6 Ref. ENTP0487C01TEUS.doc Issue 04

All Rights Reserved © 2005, Alcatel-Lucent
318
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

Action Select “Subnet”, then enter the subnet mask

Action
IP Parameters

IP Mode Static
IP addr 010.001.002.006
Subnet 255.255.255.255
Router 255.255.255.255

Result
IP Parameters

IP Mode Static
IP addr 010.001.002.006
Subnet 255.255.255.000
Router 255.255.255.255

Action Select “Router”, then enter the router IP address (if the router is required)
Action
IP Parameters

IP Mode Static
IP addr 010.001.002.006
Subnet 255.255.255.000

Router 255.255.255.255

Result
IP Parameters

IP Mode Static
IP addr 010.001.002.006
Subnet 255.255.255.000
Router 010.001.002.100

Issue 04 Ref. ENTP0487C01TEUS.doc P. 7

All Rights Reserved © 2005, Alcatel-Lucent
319
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

Action Use the navigator key (“M”) to reach the following IP Parameters
Result
IP Parameters

IP addr 010.001.002.006
Subnet 255.255.255.000
Router 010.001.002.100
TFTP 255.255.255.255

Action Select “TFTP“, Then enter the TFTP server address (Call Server “main” address)
Action
IP Parameters

IP addr 010.001.002.006
Subnet 255.255.255.000
Router 010.001.002.100
TFTP 255.255.255.255

Result
IP Parameters

IP addr 010.001.002.006
Subnet 255.255.255.000
Router 010.001.002.100

TFTP 010.001.002.003

Action Apply the modifications

Action
IP Parameters

IP addr 010.001.002.006
Subnet 255.255.255.000
Router 010.001.002.100
TFTP 010.001.002.003

P. 8 Ref. ENTP0487C01TEUS.doc Issue 04

All Rights Reserved © 2005, Alcatel-Lucent
320
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

Main Menu

Mac Address IP Parameters

Versions Miscellaneous
IP Memory Ethernet link

Action Leave the menu

Action
Main Menu

Mac Address IP Parameters

Versions Miscellaneous
IP Memory Ethernet link

Result

Initializing

Note: The Alcatel-Lucent 8 series is re-initialized

Issue 04 Ref. ENTP0487C01TEUS.doc P. 9

All Rights Reserved © 2005, Alcatel-Lucent
321
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

Result

1/5 Network start

2/5 Network setup

3/5 Config download

4/5 Config download

P. 10 Ref. ENTP0487C01TEUS.doc Issue 04

All Rights Reserved © 2005, Alcatel-Lucent
322
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

Result

5/5 Connecting

Action Register the Alcatel-Lucent 8 series. Enter the extension directory number (e.g.
31000)
Action

Registration
Extension : 31000

Result

Registration
Enter your pin code number :

Action Enter the “secret code” of the Alcatel-Lucent 8 series extension (“0000” by
default)
Action

Registration
Enter your pin code number :

Result The Alcatel-Lucent 8 series is automatically re-initialized, then switches to “in

servce” mode

Issue 04 Ref. ENTP0487C01TEUS.doc P. 11

All Rights Reserved © 2005, Alcatel-Lucent
323
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

7. IP configuration setup of the Alcatel-Lucent 8 series terminal: dynamic mode

Application On the station

Action Re-initialize the Alcatel-Lucent 8 series extension
Remark To reset an IP Touch terminal, power it off then power it
Result

Initializing

Action Press “i” key then “#” key

Result
Main Menu

Mac Address IP Parameters

Versions Miscellaneous
IP Memory Ethernet link

Action Select « IP Parameters »

Action
Main Menu

Mac Address IP Parameters

Versions Miscellaneous
IP Memory Ethernet link

P. 12 Ref. ENTP0487C01TEUS.doc Issue 04

All Rights Reserved © 2005, Alcatel-Lucent
324
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

Result
IP Parameters

IP Mode Dynamic
IP addr 255.255.255.255
Subnet 255.255.255.255
Router 255.255.255.255

Action Select « IP Mode »

Action
IP Parameters

IP Mode Dynamic
IP addr 255.255.255.255
Subnet 255.255.255.255
Router 255.255.255.255

Note: Dynamic is the default “IP mode”, if it is required, use the second upper left or
right key to modify the IP Mode (e.g. the previous configuration was: “Static
mode”)

Action Apply the modifications

Action
IP Parameters

IP Mode Dynamic
IP addr 255.255.255.255
Subnet 255.255.255.255

Router 255.255.255.255

Result
Main Menu

Mac Address IP Parameters

Versions Miscellaneous
IP Memory Ethernet link

Issue 04 Ref. ENTP0487C01TEUS.doc P. 13

All Rights Reserved © 2005, Alcatel-Lucent
325
Alcatel-Lucent OmniPCX Enterprise
Configuration of Alcatel-Lucent IP Touch 8 series sets

Action Leave the “main menu”

Action
Main Menu

Mac Address IP Parameters

Versions Miscellaneous
IP Memory Ethernet link

Result The IP Touch terminal is automatically re-initialized

If the terminal has not been already registered yet, refer to the page “14”
for the “registration phase

P. 14 Ref. ENTP0487C01TEUS.doc Issue 04

Users

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To use the maintenance Web tool to check the users status

Alcatel-Lucent OmniPCX Enterprise – Users

Ref. ENTP0403M04TEUS Issue 02

327
Web Tool
Access to the maintenance tool

Access to the tool (via a Web browser)

The URL used to access to the WebTool as to be:

http://OmniPCX-Enterprise-IP@/webtool2/

Ex:

At the connection to the system, a Security message is displayed

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Users

Ref. ENTP0403M04TEUS Issue 02

328
Web Tool
Access to the maintenance tool (Cont’)

To access to the maintenance Web Tool:

The language has to be selected

The “mtcl” login and password have to be given

All Rights Reserved © 2008, Alcatel-Lucent 3

The default “mtcl” password can not be used. This one has to be therefore modified

Alcatel-Lucent OmniPCX Enterprise – Users

Ref. ENTP0403M04TEUS Issue 02

329
Web Tool
Access to the Stand-Alone system status

When authenticated, a menu is displayed on the left of page

Press on “Toolbox” menu to reach the Stand-Alone system status Tool

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Users

Ref. ENTP0403M04TEUS Issue 02

330
Users maintenance
Main menu

When you are connected on the Web maintenance tool, the following menu will
be shown on the screen

On this screen you can view general information concerning the system

CPU name,IP address,Node number,Network number,Software release etc..

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Users

Ref. ENTP0403M04TEUS Issue 02

331
Users maintenance
Users maintenance menu

For users maintenance, select « Subscriber status » in the menu

It is possible to select one user by entering its telephone directory number in

the following window. To validate you have to click on « Submit »

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Users

Ref. ENTP0403M04TEUS Issue 02

332
Users maintenance
Users maintenance menu

Example of one user

All Rights Reserved © 2008, Alcatel-Lucent 7

In this example the user 31001 is connected on the Rack 1 UAI8 plug 2 (Terminal 1,Logic Number 1).
The set is 4020 set type (Terminal Type: UA_LE),the set is in sevice.
The set doesn’t have voice mail mailbox (Type mevo: NO_MEVO),it doesn’t belong to a hunting group (PBX group number: none),
its calls are not forwarded (Forward type: NO_FORWARDING).

Alcatel-Lucent OmniPCX Enterprise – Users

Ref. ENTP0403M04TEUS Issue 02

333
Users maintenance
Users maintenance menu

Example of one out of order user

All Rights Reserved © 2008, Alcatel-Lucent 8

In this case the set is a 4035T set type (Terminal Type:UA_MR2),it is out of service (Terminal State: OUT OF SERVICE).
It is necessary to check the connection between the set and the equipment.

Alcatel-Lucent OmniPCX Enterprise – Users

Ref. ENTP0403M04TEUS Issue 02

334
Users maintenance
Users maintenance menu

Example of one user in communication

All Rights Reserved © 2008, Alcatel-Lucent 9

In this example the user 31000 is connected to user 31001 (DEMI-COM INFORMATION, Partner direc: 31001)

Alcatel-Lucent OmniPCX Enterprise – Users

Ref. ENTP0403M04TEUS Issue 02

335
All Rights Reserved © 2008, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – Users

Ref. ENTP0403M04TEUS Issue 02

336
Alcatel-Lucent OmniPCX Enterprise
User management

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to bring into service UA and analog users.

MANAGEMENT

1. Create one UAI board (if not created)

2. Create one SLI board (if not created)

3. Define the numbering plan according to the File site (or the numbering plan given by the
trainer)

4. Create the stations according to the File site (or the numbering plan given by the trainer)

5. Plug the stations

6. Test

Issue 02 Ref. ENTP0403H01TEUS.doc HO. 1

HO. 2 Ref. ENTP0403H01TEUS.doc Issue 02

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to bring into service IP Touch X8 series terminals

MANAGEMENT

1. Connect the X8 series to the LAN (via the LANx board)

2. Connect the power supply

3. Define the numbering plan according to the File site (or the numbering plan given by the
trainer)

4. Manage a range of IP address in DHCP server according to the File site (or the numbering
plan given by the trainer)

5. Create the stations according to the File site (or the numbering plan given by the trainer),
use the static mode for the X8 series stations.

6. While your IP touch X8 series is out of service, the calls should overflow to your own
associated set

7. Test your configuration

Issue 04 Ref. ENTP0403H02TEUS.doc HO. 1

HO. 2 Ref. ENTP0403H02TEUS.doc Issue 04

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

341
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

342
Alcatel-Lucent OmniPCX Enterprise
R9.0
Starter Pack Enterprise

Part 2/3 PARTICIPANT’S GUIDE

DOCUMENT CHANGES

Issue Date Issue Date

Alcatel-Lucent OmniPCX Enterprise R9.0 Starter Pack Enterprise 01 12/08

File reference: ENTPTE900US

GENERAL SUMMARY

Part 2

15. Terminal Adapters

ENTP0403P07TEUS ...................................................................................... 343
ENTP0403C12TEUS ...................................................................................... 349
ENTP0403H12TEUS ...................................................................................... 353

16. Prefix Plan

ENTP0420P02TEUS ...................................................................................... 357
ENTP0420C07TEUS ...................................................................................... 363

17. Suffix plan

ENTP0420P03TEUS ...................................................................................... 367
ENTP0420C02TEUS ...................................................................................... 371
ENTP0420M04TEUS ...................................................................................... 373

18. Phone Feature Class of Services

ENTP0404P08TEUS ...................................................................................... 383
ENTP0404C08TEUS ...................................................................................... 387
ENTP0404H08TEUS ...................................................................................... 391

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent i

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

19. Dynamic Voice guides

ENTP0439C02TEUS....................................................................................... 397
ENTP0439M02TEUS ...................................................................................... 407
ENTP0439H01TEUS ...................................................................................... 413

20. Music on Hold - Capacity increase

ENTP0800P02TEUS....................................................................................... 417

21. Ringing Tones Customization Tool

ENTP0800P03TEUS....................................................................................... 425
ENTP0800C03TEUS....................................................................................... 433

22. Trunk groups

ENTP0409P10TEUS....................................................................................... 437
ENTP0409C02TEUS....................................................................................... 443
ENTP0409C03TEUS....................................................................................... 447
ENTP0409C05TEUS....................................................................................... 453
ENTP0409C07TEUS....................................................................................... 459
ENTP0409M01TEUS ...................................................................................... 465
ENTP0409H01TEUS ...................................................................................... 475

23. System synchronization

ENTP0437P01TEUS....................................................................................... 479
ENTP0437H01TEUS ...................................................................................... 485

24. DID Translator

ENTP0424P01TEUS....................................................................................... 489
ENTP0424C05TEUS....................................................................................... 497
ENTP0424M05TEUS ...................................................................................... 501
ENTP0424H01TEUS ...................................................................................... 505

25. External Callback Translator

ENTP0427P01TEUS....................................................................................... 509
ENTP0427C02TEUS....................................................................................... 515
ENTP0427H01TEUS ...................................................................................... 517

26. External Calls Barring

ENTP0426P01TEUS....................................................................................... 521
ENTP0426C03TEUS....................................................................................... 531
ENTP0426M01TEUS ...................................................................................... 535
ENTP0426A01TEUS....................................................................................... 539
ENTP0426H03TEUS ...................................................................................... 543

27. Automatic Route Selection (ARS)

ENTP0425P01TEUS....................................................................................... 547
ENTP0425C02TEUS....................................................................................... 557
ENTP0425M01TEUS ...................................................................................... 565
ENTP0425H01TEUS ...................................................................................... 569

ii All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

28. Automatic Callback on Busy Trunk Group

ENTP0481P01TEUS ...................................................................................... 573
ENTP0481C01TEUS ...................................................................................... 581
ENTP0481M01TEUS ...................................................................................... 585
ENTP0481H01TEUS ...................................................................................... 589

29. Connection & transfer Classes of services

ENTP0404P06TEUS ...................................................................................... 593
ENTP0404C02TEUS ...................................................................................... 599
ENTP0404H02TEUS ...................................................................................... 609

30. Multi-line sets

ENTP0406P02TEUS ...................................................................................... 613
ENTP0406C02TEUS ...................................................................................... 625
ENTP0406C04TEUS ...................................................................................... 629
ENTP0406H02TEUS ...................................................................................... 635

31. Assistant / Manager groups

ENTP0407P01TEUS ...................................................................................... 639
ENTP0407C02TEUS ...................................................................................... 649
ENTP0407M01TEUS ...................................................................................... 657
ENTP0407H01TEUS ...................................................................................... 661

32. Multiple Line Appearance (MLA)

ENTP0480P02TEUS ...................................................................................... 665
ENTP0480C02TEUS ...................................................................................... 683
ENTP0480H02TEUS ...................................................................................... 693

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent iii

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

Part 3

33. Groups
ENTP0405P03TEUS ........................................................................................ 697
ENTP0405C01TEUS ........................................................................................ 713
ENTP0405C02TEUS ........................................................................................ 717
ENTP0405M01TEUS ........................................................................................ 721
ENTP0405H02TEUS ........................................................................................ 727

34. Call Distribution

ENTP0418P10TEUS ........................................................................................ 731

35. Call Distribution - Entities

ENTP0418P11TEUS ........................................................................................ 741
ENTP0418C11TEUS ........................................................................................ 747
ENTP0418M01TEUS ........................................................................................ 753
ENTP0418H11TEUS ........................................................................................ 759

36. Call Distribution - Attendant Groups

ENTP0418P12TEUS ........................................................................................ 763
ENTP0416C02TEUS ........................................................................................ 769
ENTP0416M01TEUS ........................................................................................ 773

37. Call Distribution – Attendants sets

ENTP0418P13TEUS ........................................................................................ 781
ENTP0415C13TEUS ........................................................................................ 787
ENTP0415P02TEUS ........................................................................................ 793
ENTP0415P04TEUS ........................................................................................ 807
ENTP0415C03TEUS ........................................................................................ 813
ENTP0882P02TEUS ........................................................................................ 819
ENTP0882C02TEUS ........................................................................................ 823
ENTP0415M01TEUS ........................................................................................ 831
ENTP0415H03TEUS ........................................................................................ 839

38. DECT - IBS

ENTP0419P01TEUS ........................................................................................ 843
ENTP0419C01TEUS ........................................................................................ 851
ENTP0419C04TEUS ........................................................................................ 855
ENTP0419M01TEUS ........................................................................................ 859
ENTP0419H02TEUS ........................................................................................ 871

iv All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

39. Direct Speed Dialing

ENTP0408P01TEUS ........................................................................................ 875
ENTP0408C04TEUS........................................................................................ 883
ENTP0408M01TEUS ....................................................................................... 887
ENTP0408H01TEUS........................................................................................ 891

40. Speed Dialing by range

ENTP0408P02TEUS ........................................................................................ 895
ENTP0408C03TEUS........................................................................................ 901
ENTP0408H02TEUS........................................................................................ 907

41. Alcatel-Lucent OmniMessage 4645

ENTP0432P01TEUS ........................................................................................ 911
ENTP0432C01TEUS........................................................................................ 927
ENTP0432C02TEUS........................................................................................ 939
ENTP0432M01TEUS ....................................................................................... 943
ENTP0432H01TEUS........................................................................................ 951

42. MOXA V24/IP Box

ENTP0444P01TEUS ........................................................................................ 955
ENTP0444C01TEUS........................................................................................ 963
ENTP0444M01TEUS ....................................................................................... 969
ENTP0444H01TEUS........................................................................................ 981

43. Database Save & Restore

ENTP0411P04TEUS ........................................................................................ 985
ENTP0411C02TEUS........................................................................................ 989
ENTP0411H02TEUS........................................................................................ 995

44. RMA Solutions & System Messages

ENTP0431P01TEUS ........................................................................................ 999
ENTP0431P06TEUS ....................................................................................... 1009
ENTP0431P07TEUS ....................................................................................... 1021
ENTP0431P08TEUS ....................................................................................... 1031
ENTP0421P01TEUS ....................................................................................... 1037
ENTP0431C06TEUS....................................................................................... 1045
ENTP0431C08TEUS....................................................................................... 1055
ENTP0431H08TEUS....................................................................................... 1059

45. Appendix A – Reflexes & e-Reflexes

ENTP0403P06TEUS ....................................................................................... 1063
ENTP0403C07TEUS....................................................................................... 1077
ENTP0403M01TEUS ...................................................................................... 1081

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent v

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

vi All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

FEEDBACK SHEET
In order to improve the quality of the documentation, please report any errors found by
returning this sheet to the address below.

CHAPTER PAGE DESCRIPTION

Please return this sheet to:

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent vii

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

viii All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

Alcatel-Lucent OmniPCX Enterprise

Plugware for Alcatel-Lucent 9 series

All Rights Reserved © 2005, Alcatel-Lucent 1

OBJECTIVE

To describe the plugware for Alcatel-Lucent 9 series

Alcatel-Lucent OmniPCX Enterprise – Plugware for Alcatel-Lucent 9 series

Ref. ENTP0403P07TEUS Issue 04

343
Plugware for 9 Series sets
Overview

It is possible to equip the 9 series sets with an additional plugware in order to

connect a 2nd terminal to the set:
A FAX machine connected to the set of an assistant
Gain of an analogue interface board for example

3 types of plugware for X9 Series sets:

Analog
CTI/V24
S0

All Rights Reserved © 2005, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Plugware for Alcatel-Lucent 9 series

Ref. ENTP0403P07TEUS Issue 04

344
Plugware for X9 Series
V24/CTI

The V24/CTI plugware allows to connect a PC behind a set (CTI link) and a data
terminal (V24 link)

Used for calls management and supervision (CTI link)

VT100 connection for system management (V24 link)

Set

UA link CTI link V24 Link

All Rights Reserved © 2005, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Plugware for Alcatel-Lucent 9 series

Ref. ENTP0403P07TEUS Issue 04

345
Plugware for X9 Series
S0

The S0 plugware allows to connect a S0 bus (2B+D)

Used to connect S0 sets (TTN2 Alcatel-Lucent) or all the S0 equipments

(Fax, PC equipped with a S0 interface, etc.)

Set

Power supply

UA link S0 link

All Rights Reserved © 2005, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Plugware for Alcatel-Lucent 9 series

Ref. ENTP0403P07TEUS Issue 04

346
Plugware for X9 Series
AP

The AP plugware allows to connect an analogue terminal

Used to connect analogue sets, fax, modem,…

Set

Power supply

UA link Analog link

All Rights Reserved © 2005, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Plugware for Alcatel-Lucent 9 series

Ref. ENTP0403P07TEUS Issue 04

347
All Rights Reserved © 2005, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Plugware for Alcatel-Lucent 9 series

Ref. ENTP0403P07TEUS Issue 04

348
Alcatel-Lucent OmniPCX Enterprise
Z and S0 plugware

PROCEDURE

OBJECTIVE

- To learn how to manage S0 and Z plugware

PROCEDURE

1. Z plugware

1.1. Select the set used with Z plugware, and:

- note set’s address
- valid Z plugware for this set

Path User
Action Use filer mode and display user
Parameters Shelf address: ______
Board address: ______
equipment address: ______
Z plugware: yes

1.2. Create an new analog set

Path User
Action Create
Parameters Directory number: from 1 to 8 characters (0 to 9, *, #)
Shelf address: see 1.1
Interface board address: see 1.1
Equipment address: see 1.1
set type: analog

Issue 02 Ref. ENTP0403C12TEUS.doc P. 1

2. S0 plugware

2.1. Manage S0 plugware on UA set

Path User/consult and modify

Action Valid S0 plugware parameter on UA set.
Parameters Directory number: -> UA set
S0 plugware: yes

2.2. Create S0 bus

Path Shelf/go down the hierarchy /board /go down the hierarchy/S0
bus/create
Action Create S0 bus on UA board
Parameters Shelf address: 3
Board address: 2
Equipment address: 2
Protocol type + ETSI
Long passive bus + no

2.3. Create S0 set on the bus

Path User/Create
Action Create S0 set
Parameters Directory number: 31450
Directory name: --------------------
Directory first name: --------------------
Shelf address: 3
Board address: 2
Equipment address: 2
Set type + S0 set
Entity number: 1

P. 2 Ref. ENTP0403C12TEUS.doc Issue 02

3. S0 plugware without UA set

Note: You have to move an internal switch in order to use the plugware without set.

3.1. Create TA

Path Shelf / board/ TA adapter

Action Create
Parameters Shelf address: 3
Board address: 2
Equipment address: 4
plugware: S0 bus

3.2. Create S0 bus on the UA board

Path shelf/go down the hierarchy /board /go down the hierarchy/S0
bus/create
Action Create S0 bus on UA board
Parameters Shelf address: 3
Board address: 2
Equipment address: 2
Protocol type + ETSI
long passive bus + no

3.3. Create S0 set on the bus

Issue 02 Ref. ENTP0403C12TEUS.doc P. 3

3.4. S0 bus parameters

Path Shelf / board / S0 bus

Action Adapt the S0 parameters
Parameters Protocol type
Long passive bus
Permanent layer 1
S0_FV
Default number
S0 user list
Protocol type: according to your set and country: VN2, VN3, VN4, ETSI (all
countries)
Long passive bus: ‘ yes’ if:
- several set (5 max.) are connected on the bus (150meters max).
- several set (5 max.) are connected on the bus (599 meters maxi).
- one set is connected (1500 m maxi).
SO FV: according to your country, a leased link S0FV can be used.
Default number: If a set belonging to the bus has no identity, this
default number is used in order to send an identity.
S0 user’s list: only for consultation (you cannot modify it)

3.5. S0 bus Parameters

Path user
Action Adapt parameters according to your ISDN configuration.
Parameters ISDN:
External
Internal
ISDN services
Default user
Sub-address
ISDN user:
- external: in case of outgoing call, you can use ISDN services (USS).
- internal: you can leave a message in case of no answered internal call.
ISDN services: compatibilities between sets.
S0 parameters: used if there is more than 1 set on the bus.
- default user: Only one can be defined. Its number is used in order to
send identity when a set belonging to the bus has not.
- sub-address: yes or no.

P. 4 Ref. ENTP0403C12TEUS.doc Issue 02

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to set up the AP plugware

MANAGEMENT

ANALOG PLUGWARE

1. Install AP plugware between a X9 Series extension and the UA line.

2. Manage an analog extension on this plugware:

- directory number: 3x045

3. Connect an analog extension to the plugware and check that it works well.

Issue 04 Ref. ENTP0403H12TEUS.doc HO. 1

HO. 2 Ref. ENTP0403H12TEUS.doc Issue 04

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

355
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

356
Alcatel-Lucent OmniPCX Enterprise

Prefix Plan

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the use of the “prefixes” in the Alcatel-Lucent OmniPCX Enterprise

Alcatel-Lucent OmniPCX Enterprise – Prefix Plan

Ref. ENTP0420P02TEUS Issue 02

357
Prefix
Definition

All the numbers of the Numbering plan are some prefixes for the system
Users
Speed dialing
Voicemail number
Numbers of the prefix plan
…

These prefixes allow to access to some specific telephone functionalities:

To call an extension: user number
To call an external number with a short dialing: speed dialing number
To access to the voicemail: Voice mail directory number
To access to a specific phone feature (e.g. Immediate forwarding):
Prefix plan number
…

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Prefix Plan

Ref. ENTP0420P02TEUS Issue 02

358
Prefix
How to use

A prefix is used after a line seizure (1):

Listening to the dial tone

Listening a voice guide (2)

This is realized before establishment of a communication

“Numbering plan”
31000 = extension

Call establishment with 31000

Dialed number: 31000

The equipment connection is realized after some controls (3)

All Rights Reserved © 2008, Alcatel-Lucent 3

(1) The line seizure can be realized in different ways: taking the handset off the hook or pressing a multi-line key (but the
extension must not be rung)

(2) For example, if the set if forwarded to and other number, at the line seizure, a voice guide is run: “
Your calls are forwarded, you can make a call. To cancel the forwarding, dial ..”

(3) This connection is realized under some conditions:

- The set 31000 has to be in service and available
- The set 31000 is not forwarded
- The set where the prefix has been dialed has the right to connect the called party
…

Alcatel-Lucent OmniPCX Enterprise – Prefix Plan

Ref. ENTP0420P02TEUS Issue 02

359
Prefix plan
Phone Features

In case of the prefix corresponds to a “phone feature prefix”, a control about

the right to use this feature is realized by the system

The Phone Feature category of the user is used to do this test

“Numbering Plan”
51 = Set features: Immediate forwarding
?

Phone Feature COS

Set features: Immediate forwarding = 0

Dialed number: 51 Forbidden feature

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Prefix Plan

Ref. ENTP0420P02TEUS Issue 02

360
Prefix
Phone Features(Cont’)

A prefix corresponds to a unique phone feature

8 digits maximum (0 to 9, A, B, C, D, #, *)

In case of busy numbering plan, if the customer requests to use several prefixes
beginning with the same digits

A temporized prefix has to be used (with a “T”)

Example:

35T: Entity Call prefix (for Entity 1)

35674: Extension number for Mr. X

If a user dials only “35”, at the end of the timer (T), the system route the call towards the Call
Distribution Table of the Entity 1 (where the Attendant of the Mr. X department takes the call)

In case of the number 35674 is completely dialed, the extension 35674 is rung

All Rights Reserved © 2008, Alcatel-Lucent 5

After the timer (n° 23) the Alcatel-Lucent OmniPCX Enterprise translates (analyses) the number

Alcatel-Lucent OmniPCX Enterprise – Prefix Plan

Ref. ENTP0420P02TEUS Issue 02

361
Phone Features
Attributes

To define a prefix, 2 or 3 parameters have to be managed according to the

prefix use:

The prefix number

The prefix signification

The prefix information (only for some prefixes)

Examples:

Number: 51 Number: 9
Prefix Signification: Set Feature Prefix Signification: Attendant Call
Set Feature: Immediate Forwarding

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Prefix Plan

Ref. ENTP0420P02TEUS Issue 02

362
Alcatel-Lucent OmniPCX Enterprise
Prefix Plan configuration

PROCEDURE

OBJECTIVE

- To learn how to configure a prefix number

OVERVIEW
Prefixes are available for many features (phone features or system feature).
Some prefixes are automatically created during the creation of the empty database and they
depend on the country.

Issue 02 Ref. ENTP0420C07TEUS.doc P. 1

PROCEDURE

1. Create a range of available directory numbers for subscribers

Application Configuration Tab PCX

Path / System / Free numbers ranges list
Action Create
Tab General Characteristics
Parameters Name : Features
Range beginning : 600(e.g.)
Range End : 659 (e.g.)
Priority + True
Digits Authorized + 0,1,2,3,4,5,6,7,8,9,*,#
Max.number : 10
Action Click on “ ” to valid

2. Creation of a prefix number

Application Configuration Tab PCX

Path / Translator / Prefix Plan
Action Create
Parameters Number: 600
Prefix meaning: Set feature
Station features: Password modification
Action Click on “ ” to valid

Note: According to the prefix meaning, a supplementary option may have to be

configured
The access to the feature is controlled by the “Phone feature Class of Services
(explained in an other subject)

P. 2 Ref. ENTP0420C07TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

365
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

366
Alcatel-Lucent OmniPCX Enterprise

Suffix Plan

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the “suffix” object

Alcatel-Lucent OmniPCX Enterprise – Suffix Plan

Ref. ENTP0420P03TEUS Issue 02

367
Suffix
Definition

A suffix” is a number that can be dialed:

When a communication is already established

Use of the number “3” to switch to conferencing mode after an enquiry call

Use of the « * » to switch to “overlapping mode” (access to vocal server…)

Listening to a tone (different than the dialing tone)

For example: on a busy tone, it is possible to use the “5” to activate the
“automatic callback”

A suffix corresponds to a phone feature

The maximum length is: 8 digits (0 à 9, A, B, C, D, #, *)

All Rights Reserved © 2008, Alcatel-Lucent 2

List of the available suffixes in the system

Broker call
Three-Party conference
Barge-in
Callback on free or busy set
Camp-on Waiting
Speaker Paging
Call announce through speaker
Consultation Call
Paging request
Business number
Rotary End-to-End Dialing
DTMF end-to-end dialing
Malicious Call
Voice Mail Message Deposit
Camp-on Control
Voice mail Access
Bypass Dialing on Do Not Disturb

Alcatel-Lucent OmniPCX Enterprise – Suffix Plan

Ref. ENTP0420P03TEUS Issue 02

368
Suffix

The use of the suffix is under access right control

The User “phone feature Category” authorizes or forbids the feature

Dial “3”
To switch to In conversation
the conference mode

On Hold

Phone feature COS

Suffix three party conference: 0

Forbidden Feature

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Suffix Plan

Ref. ENTP0420P03TEUS Issue 02

369
All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Suffix Plan

Ref. ENTP0420P03TEUS Issue 02

370
Alcatel-Lucent OmniPCX Enterprise
Suffix plan configuration

PROCEDURE

OBJECTIVE

- To learn how to configure a suffix number

OVERVIEW
Suffixes are available for many features. We are using the suffix during the conversation to make
transfer, conference, etc…
Some suffixes are automatically created during the creation of the empty database and they
depend on the country.

Issue 02 Ref. ENTP0420C02TEUS.doc P. 1

PROCEDURE
Note: There is no need to manage a range of “Free directory numbers” in case of “suffix
number configuration. A suffix number is a special number in system. It can
overlap on the numbering plan numbers

1. Suffix creation

Application Configuration Tab PCX

Path / Translator / Suffix Plan
Action Create
Parameters Number: #72 (e.g.)
Suffix Meaning: Busy camp-on (e.g.)
Action Click on “ ” to valid

Note: The use of the feature is controlled by the “Phone feature Class of Services”
(explained in a other subject)

P. 2 Ref. ENTP0420C02TEUS.doc Issue 02

Numbering Plan maintenance

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the “ednump” maintenance tool used to edit the numbering plan and the use of the 4760 client to edit the
suffix plan

Alcatel-Lucent OmniPCX Enterprise – Numbering Plan maintenance

Ref. ENTP0420M04TEUS Issue 02

373
Numbering plan
“ednump” maintenance command

The “ednump” command allows to check the numbering plan

To access to the tool, type: ednump

==========================
enter criteria or command:
==========================

Several commands are available

“help”: used to get the tool help

“dir”: directory number (prefix number)
“mean”: prefix meaning
“info”: additional information (e.g. Trunk Group Id in case of Trunk Group prefix)
“list”: listing of the activated filtering options (given commands)
“clear”: used to clear the list of already given commands (all of them)
“go”: used to launch the request

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Numbering Plan maintenance

Ref. ENTP0420M04TEUS Issue 02

374
“ednump” command
Example of request

To edit the full numbering plan:

1 - dir -> Directory_number
2 - mean -> Meaning
3 - info -> Info

==========================
enter criteria or command: go
==========================
19/12/07 EDNUMP V. 4.00 Page: 1
+-----------------+----------------------------------------------------------+------+
|dir |mean |info |
+-----------------+----------------------------------------------------------+------+
|0 |Prof_Trk_grp_without_s_addr | 0|
|2 |Attendant_Call | -1|
|31000 |Station | -1|
|31002:31003 |Station | -1|
| . . .
|405 |Password_modification | -1|
|406 |Redial_last_number | -1|
|407 |Night_service_answering | -1|
|408 |Contrast_programmation | -1|
+-----------------+----------------------------------------------------------+------+
19/12/07 EDNUMP V. 4.00 Page: 2
+-----------------+----------------------------------------------------------+------+
|dir |mean |info |
+-----------------+----------------------------------------------------------+------+

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Numbering Plan maintenance

Ref. ENTP0420M04TEUS Issue 02

375
“ednump” maintenance command
Additional criteria

To refine a request, it is possible to use the following options

“=” equal
“!=” different than
“>” greater than
“>=” greater or equal
“<” lower than
“<=” lower or equal
“[: ]” available to define a range of numbers

Those options can be combined with the commands:

“dir”
“mean”
“info”

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Numbering Plan maintenance

Ref. ENTP0420M04TEUS Issue 02

376
“ednump” command
Example of refined request

Request of a specific feature

1 - dir -> Directory_number

2 - mean = Voice_Mail -> Meaning
==========================
enter criteria or command:go
==========================

19/12/07 EDNUMP V. 4.00 Page: 1

+-----------------+---------------------------------+
|dir |mean |
+-----------------+---------------------------------+
|43 |Voice_Mail |
+-----------------+---------------------------------+

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Numbering Plan maintenance

Ref. ENTP0420M04TEUS Issue 02

377
“ednump” command

Request of all numbers lower a specific one

1 - dir <= 404 -> Directory_number
2 - mean -> Meaning
==========================
enter criteria or command:go
==========================

19/12/07 EDNUMP V. 4.00 Page: 1

+-----------------+-------------------------------------------+
|dir |mean |
+-----------------+-------------------------------------------+
|0 |Prof_Trk_grp_without_s_addr |
|2 |Attendant_Call |
|31000 |Station |
|31002:31003 |Station |
|31010 |Station |
|31100 |Station |
|31900 |Voice_Mail_Sympac |
|31T |Direct_Abbrev_Number |
|400 |Set_In/Out_of_service |
|401 |Recordable_Voice_Guides |
|402 |Park_Call/Retrieve |
|403 |Charging_meter_readout |
|404 |Associated_Set_No_Modif |
+-----------------+-------------------------------------------+

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Numbering Plan maintenance

Ref. ENTP0420M04TEUS Issue 02

378
“ednump” command
Example of refined request (Cont’)

Request around a range of numbers

1 - dir [31000:32] -> Directory_number

2 - mean -> Meaning

==========================
enter criteria or command: go
==========================

19/12/07 EDNUMP V. 4.00 Page: 1

+-----------------+----------------------------------------------------------+
|dir |mean |
+-----------------+----------------------------------------------------------+
|31000 |Station |
|31002:31003 |Station |
|31010 |Station |
|31100 |Station |
|31900 |Voice_Mail_Sympac |
|31T |Direct_Abbrev_Number |
+-----------------+----------------------------------------------------------+

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – Numbering Plan maintenance

Ref. ENTP0420M04TEUS Issue 02

379
Suffix plan
4760 Client

To edit the suffix plan, the 4760 Client has to be used

Path: /Translator/ Suffix Plan

This tool can also be used to edit the prefix plan, and numbering plan

All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Numbering Plan maintenance

Ref. ENTP0420M04TEUS Issue 02

380
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

381
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

382
Alcatel-Lucent OmniPCX Enterprise

Phone Feature Category

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Phone Feature Categories use

Alcatel-Lucent OmniPCX Enterprise – Phone Feature Category

Ref. ENTP0404P08TEUS Issue 02

383
Phone Feature Categories
Role

The Phone features categories are used to:

Protect a user from some features (initiated by some other users)

To protect against direct Call Pickup for example
The calls of user owning this protection can not be intercepted by any other user
To protect a set against the forwarding
An other user can not forward his extension onto a set protected against the forwarding

Valid or forbid some specific rights

External forwarding for example
A user can have the right to use the forwarding (set feature) but not be authorized to use
external forwarding

Define the routing mode at Off-hook

No routing, immediate or delayed routing to a predefined number (1)…

All Rights Reserved © 2008, Alcatel-Lucent 2

(1) In this case, a Routing table has to be defined in the corresponding extension

Alcatel-Lucent OmniPCX Enterprise – Phone Feature Category

Ref. ENTP0404P08TEUS Issue 02

384
Phone Feature Categories
Role

Control the access to the phone features

It is necessary to use a prefix to reach the feature
The phone COS authorizes or forbids a forwarding for example

It exists different classes of phone features

Set features
General Services
Local features
PCX Services

Or to use a suffix
The Phone COS authorizes or forbids the callback on free or / busy set

Give access or not to Speed Dialing by range (32 ranges)

Define the behavior for the voicemail forwarding (1)

Define the type of default overflow (on no answer, busy state, no overflow…)
while there was no programmed overflow on the extension
And also to define the associated forwarded device (associate, voicemail, secretary)

All Rights Reserved © 2008, Alcatel-Lucent 3

(1) Voice Mail Forwarding: If the call of a set is forwarded onto an other set and if this one is in Voice Mail Forwarding:
Ring final set: the ringing of the final set is forced (default position)
Ring final set mail: the call is forwarded to the final set mail
Ring called set mail: the call is forwarded to the mail of the first called set

Alcatel-Lucent OmniPCX Enterprise – Phone Feature Category

Ref. ENTP0404P08TEUS Issue 02

385
Phone Feature Categories
Role

To define the binary upgrade period for the x9 Series extensions

If a binary upgrade is necessary

32 categories are available the system extensions

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Phone Feature Category

Ref. ENTP0404P08TEUS Issue 02

386
Alcatel-Lucent OmniPCX Enterprise
Phone Feature Class of Services

PROCEDURE

OBJECTIVE

- To learn how to manage the Phone feature Class of Service

OVERVIEW
Each extension of the system uses a Phone feature Class of Services
This specific COS provides the access to some phone features (reachable via the use of a prefix
or suffix) and also provides some “rights” (Forward to external No..) and protections against
some other user request (Barge-in)…

Issue 02 Ref. ENTP0404C08TEUS.doc P. 1

PROCEDURE

1. Phone Feature COS modification

Application Configuration Tab PCX

Path / Classes of Services / Phone Feature COS
Action Open/Close
Object 0 (COS 0)
Parameter Rights Transfer on no answer (e.g.): 1
Rights Protected against set barge-in(e.g.): 1
Set features Immediate forward (e.g.): 1
…
PCX Recordable voice guides(e.g.): 0
…
External Services Malicious call (e.g.): 1
…
Suffixes Camp-on Waiting (e.g.): 1
…
Action Click on “ ” to valid

Note: It is also possible to use the” Filter/Grid Edit” options in order to select some
specific categories so as to modify the same parameter(s) for all of them
E.G.:

P. 2 Ref. ENTP0404C08TEUS.doc Issue 02

2. Extension Phone Feature COS assignment

Application Configuration Tab PCX

Path / User
Action Filter (select the expected extension e.g. 31000) and press Enter
Result

Tab Rights
Parameters Phone Feature COS: 0 (e.g.)
Action Click on “ ” to valid

Note: By default, at their creation, all the users point on the Phone COS: “0”
According to the needs, this category can be modified
It is also possible to use “Filter/Grid Edit” possibilities to Edit several users in
order to assign them the same/different categories

Issue 02 Ref. ENTP0404C08TEUS.doc P. 3

P. 4 Ref. ENTP0404C08TEUS.doc Issue 02

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage the Phone Feature COS, configure the Prefixes & suffixes and use
the different phone features

MANAGEMENT

1. Use the “ednump” maintenance tool to edit the default numbering plan

1.1. Use the right commands (tool options) in order to edit:

1.1.1. The full numbering plan
1.1.2. Only the “stations”
1.1.3. Only the “immediate forwarding prefix”
1.1.4. All the directory numbers between “3xx” and “5xx”
1.1.5. All the numbers greater than “6xx”

2. Use of the some phone features

2.1. For the following exercises, 3 extensions are needed. Whatever the extension type,
they are identified as:
- Station A: phone feature COS 0
- Station B: phone feature COS 1
- Station C: phone feature COS 2

2.2. Modify the user parameters in order to assign the right COS to each station

2.3. Edit the three categories (0,1,2); copy and paste the configuration of the phone
feature COS “0” to both two others COS in order to have the same configuration
starting point.

Issue 02 Ref. ENTP0404H08TEUS.doc HO. 1

3. Example of “Feature Rights (protection)”

3.1. The station “C” has to be protected against the forwarding (can not be the
destination of a forwarding)
3.1.1. Modification of the phone feature COS “2”:
3.1.1.1. The corresponding station: Protected against forwarding=1
3.1.1.2. Check which number corresponds to the “Immediate forward”
prefix in the numbering plan (if it does not exist, manage it)
3.1.1.3. Try to forward Station “A” to Station “C”
3.1.1.4. Then try to forward Station “A” to Station “B”
3.1.1.5. Call from Station B to Station A
3.1.1.6. Call from Station C to Station A

4. Example of “Set feature”

4.1. Station “B” has to be able to disable the forwarding programmed by Station “A”.
Modify the corresponding COS (“1”): Cancel Remote forward
4.1.1. Check which number corresponds to the “Cancel Remote forward” prefix in
the numbering plan (if it does not exist, manage it)
4.1.2. Cancel this forward from Station “B”

4.2. For the Station “A”, on no answer, all the calls have to be forwarded to the Station
“B”
4.2.1. Modify the COS “1” to allow this behavior
4.2.2. Check which number corresponds to the “Forward on no answer” prefix in
the numbering plan (if it does not exist, manage it)
4.2.3. Activate this feature on Station “A”
4.2.4. Station “C” calls Station “A” (that does not off-hook), what happens after a
while?
............................................................................................
4.2.5. Cancel the forwarding on extension “A”

HO. 2 Ref. ENTP0404H08TEUS.doc Issue 02

4.3. Around the associated number

4.3.1. Check if the Station “A” has the right to modify the Associated number (if
not, allow it)
4.3.2. Check which number corresponds to the “Associated Direct No modification”
prefix in the numbering plan (if it does not exist, manage it)
4.3.3. Station “A” has to configure Station “B” as its associated number
4.3.4. Set up the COS “1” in order to allow Station “A” to forward its calls in case
of no answer to its associated number
4.3.5. Check which number corresponds to the “Overflow on busy/no answer to the
associated set” prefix in the numbering plan (if it does not exist, manage it)
4.3.6. Station “C” calls Station “A” (that does not off-hook), what happens after a
while?
............................................................................................

5. General Services

5.1. Check in the Station “B” COS (1), if the “Call pick up” feature is authorized (if not,
allow it)

5.2. Check which number corresponds to the “Call pick up” prefix in the numbering plan
(if it does not exist, manage it)

5.3. Station “C” calls Station “A” (that does not off-hook), Station “B” uses the “Call pick
up” prefix to intercept the call

5.4. Modify the COS of Station “C” in order to forbid the Call pick-up feature:
Rights Protection against direct call pick-up=1

5.5. Station “A” calls Station “C” (that does not off-hook), Station “B” uses the “Call pick
up” prefix to try to intercept the call, what happens?
......................................................................................................

6. Suffix

6.1. Check the Station “B” phone COS. This COS has to allow the “camp-on Waiting”
feature

6.2. Check which number corresponds to the “busy camp-on” suffix (if it does not exist,
manage it)

6.3. Station “A” calls Stations “C”, and Station “B” calls either “A” or “C”. Use the
“camp-on Waiting” suffix or the dynamic key to request the Camp-on

Issue 02 Ref. ENTP0404H08TEUS.doc HO. 3

7. Default overflow type

7.1. Modify the COS “2” in order to valid the “default overflow” to the “associated” (only
in case of no answer)

7.2. Change the associated number of the Station “C” (either via the configuration tool or
via the prefix use): it has to be the Station “A”

7.3. Check that the Station “C” has no pre-programmed forwarding ! Station “B” calls
Station “C” that does not off-hook.
What happens?
......................................................................................................

HO. 4 Ref. ENTP0404H08TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

395
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

396
Alcatel-Lucent OmniPCX Enterprise
Dynamic Voice Guide

PROCEDURE

OBJECTIVE

- To learn how to record a dynamic voice guide by using a set

OVERVIEW
After the board (GPA, GPA2 , GD, GA…) creation, the DSP management, a dynamic voice
message is created in three steps:

- The audio sequence is recorded from the set (after a message number has been created in
management).

- The file is created (the audio sequence is assigned to the message number).

The file is downloaded to the Call Server

Issue 02 Ref. ENTP0439C02TEUS.doc P. 1

PROCEDURE

1. Hardware declaration (example given with GPA2 board)

1.1. GPA2 board creation

Application mtcl
Path Shelf/Board/Creation
Parameters Shelf Address: 0 to 99
Board Address: 0 to 27 (depends on shelf type)
Interface Type: GPA2

1.2. DSP management

Application mtcl
Path Shelf/Board/GPA DSP program/Creation
Parameters Shelf Address: 0 to 99
Board Address: 0 to 27 (depends on shelf type)
Interface Type: GPA2
Configuration: VG+4 Detections+Tone
or VG+4 VAD+Tone
or VG+2 Detections+2 VAD+Tone
or VG+Conf.+3 Detections+Tone
or VG+Conference+3 VAD+Tone
or VG+Conf.+2 Detections+1 VAD+Tone
or VG+Conf.+1 Detection+2 VAD+Tone
or VG+2 Conferences+2 Detections
or VG+ 2 Conferences+2 VAD
or VG+2 Conferences+Detection+VAD

P. 2 Ref. ENTP0439C02TEUS.doc Issue 02

2. Create the Voice guide

Application mtcl
Path System / voice guide / create
Parameters Voice guide n°: 866 (example)
Function: Single message voice guide
Flash message by language:
Flash message for language 1: 866 (example)

3. Allocate the voice guide to the GPA2 board

Application mtcl
Path System / Dynamic voice guides / assignment / create
Parameters Voice guide sub-message N°: 866 (example)
ACT shelf-board list: 0-4 (GPA2 board address)

4. Create or check the presence of the voice guide recording prefix

Application mtcl
Path Translator / prefix plan
Parameters Number:<8 digits max>
Prefix meaning: local features
Local features: recordable voice guide

Issue 02 Ref. ENTP0439C02TEUS.doc P. 3

5. Allow to the users the possibility to record the voice guide and enable the keyboard use

5.1. Filter a set, note down its phone features COS and enable its alpha numeric
keyboard.

Application mtcl
Path Users
Parameters Directory n: _ _ _ _ _
Set type: 4035
Phone features COS: 0 (0..31)
Internal alphanum. Keyboard: english

5.2. Update the user’s phone facilities category

Application mtcl
Path Classes of service / Phone features COS / Review/modify
Parameters Phone features COS: 0 (0..31)
PCX services
Recordable voice guides: 1

P. 4 Ref. ENTP0439C02TEUS.doc Issue 02

6. Record the voice guides

6.1. Dial the prefix to record the voice guide

6.2. Choose the «record.» key on the set display

On set
Action
Voice guides: main menu

Record Download

6.3. Specify the voice guide number and apply: e.g. 866

On set
Action
Enter VG number to record?

866

Apply

Issue 02 Ref. ENTP0439C02TEUS.doc P. 5

6.4. Check the available duration on the board and valid

On set
Action
Max recording: 523 sec

Apply

6.5. Record the message using START

On set
Action
Recording of voice guide nbr
866

Start record
recording

6.6. Stop the recording

On set
Action
Recording of voice guide nbr 866
0:34

Stop

P. 6 Ref. ENTP0439C02TEUS.doc Issue 02

6.7. Validate your message (after listening to it or/and recording it again)

On set
Action
Recording of voice guide nbr
866

Listen Apply
Record again

6.8. Name the file stored on hard disk corresponding to your guide (e.g.: greeting)

On set
Action
Enter the file name

Welcome

Delete Apply
Rebout

Issue 02 Ref. ENTP0439C02TEUS.doc P. 7

6.9. Enter a memo (eg.: pilot1 greeting)

On set
Action
Enter the memo

Apply

Pilot 1

Delete Apply
Rebout

6.10. File creation

On set
Action
Patience : File creation in
progress..

Delete Apply
Rebout

«greeting» created for VG nbr:

866

Apply

P. 8 Ref. ENTP0439C02TEUS.doc Issue 02

6.11. Voice guide downloading on the board

Sur le poste
Action
Do you want to select this VG file?

Yes No

6.12. Off hook

Issue 02 Ref. ENTP0439C02TEUS.doc P. 9

P. 10 Ref. ENTP0439C02TEUS.doc Issue 02

Voice Guides recording on Media Gateway

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To maintain the Voice Guides recording on Media Gateway

Alcatel-Lucent OmniPCX Enterprise – Voice Guides recording on Media Gateway

Ref. ENTP0439M02TEUS Issue 02

407
Dynamic voice guides

Locating dynamic voice guides files on hard disk

/usr7/vg/dhs/

-rw-rw-rw- 1 mtcl tel 32826 Dec 12 12:09 3_test^

-rw-rw-rw- 1 mtcl tel 32827 Dec 12 12:10 271_test2

Locating guides on boards

(1)xa000001> wherevg 3
voice guide number: 3 (GPMERAC)
+-------+-----+------+------+---------+-----+
| Cryst | Cpl | Slot | Msg | Type | Lng |
+-------+-----+------+------+---------+-----+
| 1 | 27 | 5 | 3 | Dynamic | 1 |
| 1 | 27 | 5 | 271 | Dynamic | 2 |
+-------+-----+------+------+---------+-----+

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Voice Guides recording on Media Gateway

Ref. ENTP0439M02TEUS Issue 02

408
Dynamic voice guides

Display of static guides, dynamic guides and recording duration on one board
(1/2)
(1)xa000001> vgstat 1 27

etat_vg = VG_STABLE (0)

Slot 1: Card status register = 4E Identifier = 3ba50162fraa

Static voice guides Language: 1 - FR0

Slot 2: Card status register = 4E Identifier = 3ba50162enaa

Static voice guides Language: 2 - EN0

Slot 3: Card status register = 4E Identifier =

Static voice guides Language: 21 - On hold music

Slot 4: Card status register = 4E Identifier =

Static voice guides Language: 255 - Not used

Slot 5: Card status register = 3C

Dynamic voice guides
Total size = 2096128 bytes (1024 pages) (524 sec)
Free size = 2079752 bytes (1016 pages) (519 sec)
Fill ratio = 0.8 %
Available size = 2079752 bytes (1016 pages) (519 sec)

Number of present messages = 162

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Voice Guides recording on Media Gateway

Ref. ENTP0439M02TEUS Issue 02

409
Dynamic voice guides

Display of static guides, dynamic guides and recording duration on one board
(2/2)
...
Message syntax: xxxx = static, xxxx-d = dynamic, xxxx-D = dynamic and static

Dynamic messages waiting for download:

Available voice guides channels = 16

Active channel:

Guide number 3 and 271 are present in flash and ram on the GD

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Voice Guides recording on Media Gateway

Ref. ENTP0439M02TEUS Issue 02

410
Dynamic voice guides

Display of broadcast guides

(1)xa000001> vgemis

+------+-----------------+----+----+-----+------+---+-------------------------+
| guid | guide name | cr | cpl| term| neqt |lng| listeners neqt |
+------+-----------------+----+----+-----+------+---+-------------------------+
| 3 | GPMERAC | 1 | 27 | 0 | 852 | 2 | 323 |
+------+-----------------+----+----+-----+------+---+-------------------------+

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Voice Guides recording on Media Gateway

Ref. ENTP0439M02TEUS Issue 02

411
Dynamic voice guides

Voice guides duration

vgfile guide_number
(1)xa000001> vgfile 3

------------------------------------------------------------------------
| VG msg No | file name | crc | size (bytes) | pages | time (sec)|
|------------------------------------------------------------------------|
| 3 | 3_test | 0x00891e6F | 65504 | 16 | 8.2 |
|------------------------------------------------------------------------|

or vgfile all

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Voice Guides recording on Media Gateway

Ref. ENTP0439M02TEUS Issue 02

412
Alcatel-Lucent OmniPCX Enterprise
Voice guides

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to record dynamic voice guides

MANAGEMENT

1. Create a GPA (or GPA2, or GD or GA…) board

In case of GPA / GPA2 board, declare the DSP

2. Create a prefix to record voice guides and allow the users to use it

3. Declare the voice n°866 on the GD and record it from a set.

4. Play the new prompt by using the prefix « tones test ».

5. Check the presence of the prompts on the hard disk of the cpu-cs.

6. Use the maintenance commands to verify the voice guides.

Issue 02 Ref. ENTP0439H01TEUS.doc HO. 1

HO. 2 Ref. ENTP0439H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

415
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

416
Alcatel-Lucent OmniPCX Enterprise

Music on Hold - Capacity increase

All Rights Reserved © 2007, Alcatel-Lucent 1

OBJECTIVE

To describe the method to be used to increase the MOH capacity in static voice guides partitions (GPA2 and Gx boards)

Alcatel-Lucent OmniPCX Enterprise – Music on Hold - Capacity increase

Ref. ENTP0800P02TEUS Issue 03

417
Music on Hold - Capacity increase
Problematic

In the previous releases, in case of multi sites topology(Stand-Alone), it was not

possible to use a lot of different Music on Hold, in addition to the default
MOH(1), due to:

The number of languages used on the installation

If the 8 available languages were used, the only ways to use some additional MoH
(in addition to the default MoH file)were:

To include the “moh” message in a customized language file(2) (short music tracks)

Or to record a music track via an extension, and associate this message to a board
supporting the dynamic messages(3)

The number of available system language indexes(4): 8

The free indexes could be linked to “Specific file(1)” including the “music files”

It is therefore possible to use longer music tracks, but at the maximum, only 7 files could be
used in addition to a unique system language

All Rights Reserved © 2007, Alcatel-Lucent 2

(1) At the Generic/Standard voice guide files, the “flashmoh/adpcmmoh” files are downloaded. Therefore, those files can be
associated to a Flash voice guide index, in order to use the default Music on Hold

(2) Use of the Alcatel-Lucent Audio Station software to generate this file

(3) GD, GA or GPA-2 boards

(1 dynamic voice guide slot per board, 16 minutes for a GPA2 and 8 minutes for a Gx board)

(4) Those system language indexes are configurable under:

/System/Static Voice Guides

Remark:

In addition to those possibilities, it is still possible to use external Moh. “Music devices” connected to analog equipments or to
the CPU (Crystal CPU type only)

Those two solutions require “external” music devices. It is not the purpose of this subject

Alcatel-Lucent OmniPCX Enterprise – Music on Hold - Capacity increase

Ref. ENTP0800P02TEUS Issue 03

418
Music on Hold - Capacity increase
Solution

It is now possible to use some additional “System Voice Guides” indexes to load
some Specific Files, regardless of the system languages

Instead of 8 static guide indexes, it is now possible to use 200 indexes

The “8” first indexes are usable in the same way as in the previous versions

Generic / Standard or Customized language audio files

The “192” following ones will be used as “Specific files” purpose (MoH)

Each index refers to a customized file name(1)

Those files have to be stored in

/usr7/vg/flash/custom for GPA2 boards (Crystal hardware)

/usr7/vgadpcm/flash/custom for GA and GD boards (Common hardware)

All Rights Reserved © 2007, Alcatel-Lucent 3

(1) In case of heterogeneous hardware, the “MoH” files (.msk type of file created with the Alcatel-Lucent Audio Station) have to
be stored in both directories with the same name !
Each file using the corresponding hardware compression type,
- “adpcm” for Common hardware,
- and “PCM” type for the Crystal hardware

Alcatel-Lucent OmniPCX Enterprise – Music on Hold - Capacity increase

Ref. ENTP0800P02TEUS Issue 03

419
Music on Hold - Capacity increase
Limits

The “musics on hold” can be selected among 192 Specific files (in addition to
the default “MoH” file)

Each file can contain a unique or several different music tracks (MoH)(1)

Capacity per type of board

Partitions
Boards Voice encoding Durations
(Slot x File Size)

GPA2 G711 4 x 6MB 4 x 12 minutes

GD-GA ADPCM 4 x 2MB 4 x 8minutes

The limit of indexes (tones + voice guides) is not changed

Tones + Voice Guides + MoH = 2000 indexes at maximum

All Rights Reserved © 2007, Alcatel-Lucent 4

(1) The “.msk” project file has also to contain the “215” message, which is used for voice guide tests purpose

Remark:
In order to know what are the free indexes and messages in the system, use the commands
- “tab__aux freeguide”
- “tab__aux freemsg”

Alcatel-Lucent OmniPCX Enterprise – Music on Hold - Capacity increase

Ref. ENTP0800P02TEUS Issue 03

420
Music on Hold - Capacity increase
Management

Reminder about the location files to be downloaded by the boards

/System
User Language
1 - Language Choice + French
1- Display Language No.: 0
1- Voice guide Language nb: 1 Location for Generic/standard files

2 - Language Choice + English For GPA2 board:

2- Display Language No.: 1 /usr7/vg/flash/std/flashz2vg.FR0
2- Voice guide Language nb: 2 /System/Flash Voice Guide Configuration

Index 1: French For GD/GA board:

Index 2: English /usr7/vgadpcm/std/vgadpcm.FR0
…
Index 8: not used Location for custom files
Index 9: Specific File
Á MOH-Site1.msk /usr7/vg/flash/custom/MOH-Site1.msk
Voice Guide flash slots …
For Gx boards /Shelf/Board/voice Guide Index /usr7/vgadpcm/custom/MOH-Site1.msk
Index 1: 1
Index 2: 2
Index 3: not used
Index 4: 9

For GPA2 boards /Shelf/Board

Static voice guides index 1 + 1
Static voice guides index 2 + 2
…
Static voice guides index 4 + 9

All Rights Reserved © 2007, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Music on Hold - Capacity increase

Ref. ENTP0800P02TEUS Issue 03

421
All Rights Reserved © 2007, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Music on Hold - Capacity increase

Ref. ENTP0800P02TEUS Issue 03

422
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

423
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

424
Alcatel-Lucent OmniPCX Enterprise

Ringing Tones Customization Tool

All Rights Reserved © 2007, Alcatel-Lucent 1

OBJECTIVE

To describe the Ringing Tones Customization Tool use

Alcatel-Lucent OmniPCX Enterprise – Ringing Tones Customization Tool

Ref. ENTP0800P03TEUS Issue 03

425
Customization Tool
Generalities

In order to customize the Alcatel-Lucent IP Touch 8&9 Series, a dedicated Web-

Tool has to be used (Professional Services)

Before being able to customize the ringing melodies, the Business Partner
has to have a “token(1)”

The Business Partner orders the “custom ring tone” item via the e-Buy Server
(Business Partner Web Site), an e-mail is sent back to him with a corresponding
“Token” (one “token” per customization project)

E-mail

Business Partner
Secured
Web Customization Tool
Connection Administration

e-Buy: BPWS

All Rights Reserved © 2007, Alcatel-Lucent 2

(1) This “token” is a number (unique identifier)

Alcatel-Lucent OmniPCX Enterprise – Ringing Tones Customization Tool

Ref. ENTP0800P03TEUS Issue 03

426
Customization Tool

Via the Business Partner Web Site, and with the received “token”, the Business
Partner can therefore create his project

Select the “IP Touch Ringtones” menu

All Rights Reserved © 2007, Alcatel-Lucent 3

Temporarily, the RingTones customization tool is hosted on the “www.myproserv.com” website

Alcatel-Lucent OmniPCX Enterprise – Ringing Tones Customization Tool

Ref. ENTP0800P03TEUS Issue 03

427
Customization Tool
Creation of a project

To create a project, the Business Partner has to add the new “token”
(new project)

Two fields have to be filled out (1)

The “Token ID” (the received one)

The associated project name(2)

Result of a new project definition

(3)
Press on “Edit” to
configure the
Melody project

All Rights Reserved © 2007, Alcatel-Lucent 4

(1) Example of new project creation

(2) This project name can not be longer than 12 characters (only alphanumeric characters)

(3) It is possible to modify the “project name” directly pressing on its name field

Alcatel-Lucent OmniPCX Enterprise – Ringing Tones Customization Tool

Ref. ENTP0800P03TEUS Issue 03

428
Customization Tool
Configuration of the project

Selection of the extension family(ies) and type(s)(1)

(2)

All Rights Reserved © 2007, Alcatel-Lucent 5

(1) To access to the project configuration page, the Business Partner has to select his(her) project, and press on the “Edit” field
of the selected one (see previous page)

One customization file will be generated per main family of extensions (UA or IP) according to the selection.
Example of files according to the above selection (project name: “ALTraining”)
- “cust-ALTraining-40x8” for the Alcatel-Lucent IP Touch 8 Series
- and “cust-ALTraining-40x9” for the Alcatel-Lucent IP Touch 9 Series

Remark
More than only the selection of the extension family, the selection of the extension types has also to be done in order to set
up some limits about the total duration of the ringing tones, the numbers and the length of the tones (short or long)
- 4029-4039: 7 short ringing tones
- 4018: 7 short and 1 long ringing tone
- 4028-4038-4068: 7 short and 3 long ringing tones
(If a low capability extension type is selected, the restriction of this extension will be used for the setup of the customization
file)

(2) A customization project is based on a default ringing tone file which can be the default system one (16 tones) or an already
existing project, which is going to be modified

Alcatel-Lucent OmniPCX Enterprise – Ringing Tones Customization Tool

Ref. ENTP0800P03TEUS Issue 03

429
Customization Tool
Configuration of the project (Cont’)

Creation of the list of ringing tones

Default “free of charge”

Alcatel-Lucent (3)
tones

Personal
Business Partner
tones(1)

Limits
(according to
the project (2))
% of use of the file

(4)

All Rights Reserved © 2007, Alcatel-Lucent 6

(1) The Business Partner can upload the server with his own personal tones. Those tones are not dedicated to a project.
Whatever the new project, the personal tones will be displayed as available tones

Restrictions about the ringing tones

Format: Wav
Codec type: PCMU
Sample rate: 8000 Hz
Bytes/sec:8
Channel:1
Duration/file size: 1,5s (12058 bytes) for a short ringing, 5s (40058 Bytes) for a long ringing
File name: 18 ASCII characters max (from 0x20 to 0x7e), no space

(2) Those limits depend on the selected extension types

(in this example, we have selected all extension types (in both UA and IP families). Due to the restriction of Alcatel-Lucent IP
Touch 9 Series extension, only the short ringing tones can be used)

(3) Add to list

The target ring tones list can support 20 melodies at maximum
(16 melodies by default in the system)
So, a new melody can be added to the existing target ring tones list,
or the new melody can replace an existing one

(4) Publish
When pressing on “Publish” key, the server generates the corresponding
customization files
After this step, it will not be possible to modify the project anymore

If the Business Partner wants to modify the project, he will have to

- Request a new “token”
- Or request the Professional Services to reset the Token
Whatever the case, the Project (ringing tone selection) will have to be rebuilt

Alcatel-Lucent OmniPCX Enterprise – Ringing Tones Customization Tool

Ref. ENTP0800P03TEUS Issue 03

430
Customization Tool
Configuration of the project (Cont’)

Download binaries

Content of the Reminder about the procedure

customization file to download the customization files

All Rights Reserved © 2007, Alcatel-Lucent 7

“Downloading file” window

Remark
In the main “IP Touch Ringtones Tool” window, the only available action around this project will be “Download” after the
“Publish” phase

Alcatel-Lucent OmniPCX Enterprise – Ringing Tones Customization Tool

Ref. ENTP0800P03TEUS Issue 03

431
All Rights Reserved © 2007, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Ringing Tones Customization Tool

Ref. ENTP0800P03TEUS Issue 03

432
Alcatel-Lucent OmniPCX Enterprise

Ringing Tones Customization Tool

All Rights Reserved © 2007, Alcatel-Lucent 1

OBJECTIVE

To configure the Alcatel-Lucent OmniPCX Enterprise in order to take into account the new melodies

Alcatel-Lucent OmniPCX Enterprise – Ringing Tones Customization Tool

Ref. ENTP0800C03TEUS Issue 03

433
Ringing Tones Customization Tool
Customization file allocation

The customization files have to be transferred to the /usr7/client/bin directory

(transfer binary mode required)

/Alcatel 8&9 Series/ Alcatel 8&9 Class of services/

/Phones COS (Review/Modify)

Phone COS id: 0

Customization file name : ALTtraining(1)

Example of set information (“getnoeversion” command)

getnoeversion d 34500

getnoeversion started 2007-03-21 at 11:22:02

+-------------------------------------------------------------------------------------------------------------+
| dir numb | in | typ term | dom | serial number | hardware version | code vers | data vers | rom | ram |
+-------------------------------------------------------------------------------------------------------------+
| 34500 | OK | IPT 4068 | 2 | H0400426619069 |3GV23014ADCA080427 | | 3.71.00 | 8 | 8 |

| CUSTOMIZATION : File name : cust-ALTraining-40x8 Version : 1.00.04

|
+-------------------------------------------------------------------------------------------------------------+
getnoeversion ended 2007-03-21 at 11:22:02

All Rights Reserved © 2007, Alcatel-Lucent 2

(1) Only the project name has to be given. The OXE knows that it has to find the file name corresponding to a type of extension
(or family of extension, in case of the file of a dedicated extension type does not exist) : cust-ALTraining-40x8, or cust-
ALTraining-40x9…

Remark:
After the configuration, the 40x8 extensions types will reset within about 2s.
For the 40x9 extension types, it may take longer according to the “downloading optimization” system policy

Example of corresponding system messages

21/03/07 14:49:13 001004M|000/03/-/---|=4:0260=Beginning of downloading /DHS3ext/client/bin/cust-ALTraining-40x9
term 00
21/03/07 14:49:18 001004M|000/03/-/---|=5:0261=End of downloading /DHS3ext/client/bin/cust-ALTraining-40x9 term
00

The “downstat t” tool can be used to check the “customization” of the TDM (40x9) extensions types
(some sub-menu (not shown in this page) can be used to check the different extensions information)

downstat t

Wed Mar 21 14:05:41 CET 2007

*** IPTOUCH-A(4019) TDM : soft : 3.80.40

*** IPTOUCH-B(4029) IPTOUCH-C(4039) TDM : soft : 3.80.61 - data : 3.80.60

*** NOE-BC TDM : customization file version for ALTraining : 1.00.04

*** Download time optimization: FOR EACH SET

** 2 IPTOUCH TDM phones are declared on this node !!

** 2 IPTOUCH TDM phones are not updated with the right binary !!
** 0 IPTOUCH TDM phones can be reset for update !!

Alcatel-Lucent OmniPCX Enterprise – Ringing Tones Customization Tool

Ref. ENTP0800C03TEUS Issue 03

434
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

435
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

436
Alcatel-Lucent OmniPCX Enterprise

Trunk Groups

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Trunk Group object

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409P10TEUS Issue 01

437
Trunk Group
Generalities

A Trunk Group is an essential element to interconnect the Alcatel-Lucent

OmniPCX Enterprise with:

Some other private systems

The Public Operators

The Alcatel-Lucent OmniPCX Enterprise supports a large range of trunk groups.

The most common ones are:

T0, T2, T1 (and analog trunk groups)

According to the type of connection, and the connected system, different kinds of
signaling can be used:

ISDN (France or All countries)

QSIG (Basic Function / Generic Function / Supplementary Services)
ABC-F (for Links between OXE systems)

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409P10TEUS Issue 01

438
Trunk Group
Generalities (Cont’)

With the new IP architecture two other types are also available:

IP with H323 signaling protocol

IP with SIP signaling protocol

Both IP types of trunk groups can be used to interconnect the OmniPCX

Enterprise with

Private systems (Same or different manufacturers)

Public Operators

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409P10TEUS Issue 01

439
Trunk Group
Main parameters

A trunk group has:

A trunk group index (unique in the system)

A logical discriminator (option, used for call barring)

A signaling variant (ISDN all countries, QSIG, ABCF …)

A specification (optional: e.g. IP or SIP)

A DID translator (optional)

To establish a coherence between the public / private numbering plans

The length of digits to send (only in case of direct seizure)

Number of digits to be removed for incoming calls

Can be complementary to the DID transcoding

Entity

Connection category

Public Network COS

All Rights Reserved © 2008, Alcatel-Lucent 4

By default a Trunk Group uses:

• The Entity 0, used to:

- Route a call to CDT in case of unallocated number (incoming calls)
- Set up the link between a logical discriminator to a real discriminator in case of Trunk Group to Trunk Group barring

• The Connection Category “5” used to allow or forbid the connection to some other system devices (mainly the users, trunk
groups…)

• The public COS “0” used in case of “Trunk Group to Trunk Group” barring or to customized some specific behaviors

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409P10TEUS Issue 01

440
Trunk Group
How to use

A Trunk Group can be seized:

Directly via a “Trunk group seizure prefix”

Or indirectly via the Automatic Route Selection feature

Optimization of the selected routed according to the dialed number

Two types of dialing sending are available (whatever the seizure type)for the
digital Trunk Groups

Overlapping mode
The call setup message is sent digit by digit

Bloc mode
The call setup message is sent in one message

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409P10TEUS Issue 01

441
All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409P10TEUS Issue 01

442
Alcatel-Lucent OmniPCX Enterprise
Analog trunk groups (on APA board)

PROCEDURE

OBJECTIVE

- To learn how to create an analog trunk group (on APA board) with mgr

OVERVIEW
The APA board is used on the common hardware; this board provides analog external accesses
for the system.

Issue 02 Ref. ENTP0409C02TEUS.doc P. 1

PROCEDURE

1. Create an APA board

On mgr
Select Shelf
Board
Action Create
Entry Create Board
Shelf Address: 1
Board address: 1
Interface type: MG-APA 4
Action Press CTRL+V two times to validate the creation
Press CTRL +C as many times as needed to come back on main menu

2. Create an analog trunk

On mgr
Select Trunk Groups
Action Create
Entry Create Trunk groups
Trunk Group ID: 10
Trunk Group Type: NDDI (BCA)
Trunk Group Name: Analog
Action Press CTRL+V
Entry Create Trunk groups
Node number: 1
Number Of Digits To Send: 5
Remarks:
The number of digits to send depends on your external dialing plan
Action Press CTRL+V
Press CTRL+C two times to come back to the previous menu
Select Descend hierarchy

P. 2 Ref. ENTP0409C02TEUS.doc Issue 02

Trunk Groups
All instances
Entry Trunk Group ID: 10
Action Press CTRL+V
Check and modify if it’s necessary the entity number for your trunk group
Press CTRL+C two times to come back to the previous menu
Select Descend hierarchy
Trunk
Action Create
Entry Trunk Group ID: 10
Physical Address: 1-1-0
Trunk Routing Number: 31900
Remark: For the Trunk Routing Number:
- Enter a phone number corresponding to a set for call distribution
- Nothing on the field means that you use the call distribution of the
entity associated to this trunk group (checked before)
Action Press CTRL+V two times to validate the creation
Press CTRL +C as many times as needed to come back on main menu

3. Create a trunk seizure prefix

On mgr
Select Translator
Prefix plan
Action Create
Entry Create Prefix plan
Number: #010
Prefix Meaning: Professional trunk seize
Action Press CTRL+V
Entry Prefix information: 10
Remark: Corresponds to the trunk group number created just before
Action Press CTRL+V to validate the creation

Issue 02 Ref. ENTP0409C02TEUS.doc P. 3

4. Maintenance

On the call server

Login mtcl
Command trkstat 10
T R U N K S T A T E Trunk group number: 10
Result
Trunk group name : Analog
Number of Trunks : 1
Index: 1
Neqt : 710
State: F
F: Free B: Busy Ct: busy Comp trunk Cl: busy Comp link

Remark: there are different options with this command, for more
information, use this command without attribute.
Command trkvisu all
Numb Name Type Var. Node Pfx
Result
TG 10 Analog BCA 1 => local 10

Remark: for more details, use the command trkstat + Trung Group
Number (eg: trksat 10)

P. 4 Ref. ENTP0409C02TEUS.doc Issue 02

PROCEDURE

OBJECTIVE

- To learn how to create ISDN T0 trunk groups with mgr

OVERVIEW
Create a T0 trunk groups by using the mgr application. Assign prefix numbers to each trunk
group in order to seize them.
Call other nodes in the classroom to verify that these trunk groups are correctly configured.

Issue 02 Ref. ENTP0409C03TEUS.doc P. 1

PROCEDURE

1. T0 trunk group management (Not available in North America)

1.1. Check the presence of the required boards (e.g.: BRA2/4/8 or MIX for a T0 trunk
group)

On the call server

Login mtcl
Command Config: (for example: 0) (0=shelf number)
+----------------------------------------------------------------------+
Result
| Cr | cpl | cpl type | coupler state | coupler ID |
|----|-----|--------------|-----------------------|--------------------|
| 1 | 0 | GD | IN SERVICE| NO OPS FILE |
| 1 | 1 | UAI 4 | IN SERVICE| NO OPS FILE |
| 1 | 2 | PRA T1 | IN SERVICE| NO OPS FILE |
| 1 | 3 | BRA 4 | IN SERVICE| NO OPS FILE |
| 1 | 5 | PRA T2 | IN SERVICE| NO OPS FILE |
+----------------------------------------------------------------------+

P. 2 Ref. ENTP0409C03TEUS.doc Issue 02

1.2. In case of BRA2/4/8 or MIX boards: create a T0 trunk group

On mgr
Select Trunk groups
Action Create
Entry Trunk Group Id: (for example: 1)
Trunk Group Type: T0
Trunk Group Name: (for example: T0-1)
Node Number: (for example: 1)
Tone on seizure: (For example: True)
Q931 signal variant: (for example: ISDN all countries)
Number Of Digits To Send: (for example: 10)
DID transcoding: (for example: True)
Action Press CTRL+v two times to validate the creation
Entry Press CTRL+c as many times as needed to come back on main menu
Remark:
Q931 Signal variant:
Select the signaling variant for the type of network that can be accessed by
the trunk group:
ISDN FRANCE: to use "Numéris".
ISDN all countries: for other ISDN networks.
DID Transcoding:
When the DID range supplied by the public network does not match the
internal numbering, validate the DID translator; false if no DID translation is
needed.

Issue 02 Ref. ENTP0409C03TEUS.doc P. 3

1.3. Program the number of digits unused

On mgr
Select Trunk groups
Trunk group
Entry Trunk group id: (for example: 1)
No. of digits unused (ISDN): (for example: 5)
B Channel Choice: No
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu
Remark:
No. of digits unused (ISDN):
This attribute is used when the DID number is generated from the number
received from the public network.
Indicate the number of digits to remove from the start so that the last digits
remain for analysis in ISDN DID (in FRANCE the dialing plan has 10 digits and
only 4 digits are used for DID, which means you must enter 6 for this item).

P. 4 Ref. ENTP0409C03TEUS.doc Issue 02

1.4. Create the T0 line(s) in the trunk group

On mgr
Select Trunk groups
Trunk group
T2/T1/T0 access
Action Create
Entry Trunk group id.: (for example: 1)
Physical address: (for example: 1-3-0)
Access type: T0
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu
Remark:
Physical Address:
Enter the physical position of the access in the format: Media Gateway No -
(Coupler) Board No - Device No
Time Slots:
Automatically completed by the system

1.5. Program the synchronization priorities

On mgr
Select Shelf
Digital access
Entry Shelf address: (for example: 1)
Board address: (for example: 3)
T0/T2 access: (for example: 0)
Synchronization priority: (for example: 10)
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu

Issue 02 Ref. ENTP0409C03TEUS.doc P. 5

1.6. Create the outside line prefix in order to seize this T0 trunk group

On mgr
Select Translator
Prefix plan
Action Create
Entry Number: (for example: *81)
Prefix Meaning: (for example: Professional TG With Overlapping)
Prefix Information: (for example: 1) (the trunk group id)
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu

1.7. Reset the board in order to initialize the trunk group

On the call server

1.8. Check the status of the trunk lines

On the call server

Login mtcl
Command trkstat 1 (1= trunk group Id)
+============================================================================+
Result | T R U N K S T A T E Trunk group number: 1 |
| Trunk group name : T0_USER |
| Number of Trunks : 2 |
+----------------------------------------------------------------------------+
| Index: 1 2 |
| State: F F |
+----------------------------------------------------------------------------+
| F: Free | B: Busy | Ct: busy Comp trunk | Cl: busy Comp link |
| WB: Busy Without B Channel| Cr: busy Comp trunk for RLIO inter-ACT link |
| WBD: Data Transparency without chan.| WBM: Modem transparency without chan|
| D: Data Transparency | M: Modem transparency |
+----------------------------------------------------------------------------
Remark:
This command is used to display the busy status of trunks of the selected T0
trunk group and the alarm status of the T0 board supporting the trunk group.
- F (free), B (busy): the trunk group works correctly
- hs (out of service): the trunk group is out of service.

P. 6 Ref. ENTP0409C03TEUS.doc Issue 02

PROCEDURE

OBJECTIVE

- To learn how to create ISDN T2 trunk groups with mgr

OVERVIEW
Create a T2 trunk groups by using the mgr application. Assign prefix numbers to each trunk
group in order to seize them.
Call other nodes in the classroom to verify that these trunk groups are correctly configured.

Issue 02 Ref. ENTP0409C05TEUS.doc P. 1

PROCEDURE

1. T2 trunk group management

1.1. Check the presence of the required boards (e.g.: PRA E1 for a T2 trunk group)

On the call server

Login mtcl
Command Config: (for example: 0) (0=shelf number)
+-------------------------------------------------------------------------+
Result
| Cr | cpl | cpl type | coupler state | coupler ID |
|----|-----|--------------|--------------------------|--------------------|
| 1 | 0 | GD | IN SERVICE| NO OPS FILE |
| 1 | 1 | UAI 4 | IN SERVICE| NO OPS FILE |
| 1 | 2 | PRA T1 | IN SERVICE| NO OPS FILE |
| 1 | 3 | BRA 4 | IN SERVICE| NO OPS FILE |
| 1 | 5 | PRA T2 | IN SERVICE| NO OPS FILE |
+-------------------------------------------------------------------------+

1.2. In case of PRA E1 boards: create a T2 trunk group

On mgr
Select Trunk groups
Action Create
Entry Trunk Group Id: (for example: 2)
Trunk Group Type: T2
Trunk Group Name: (for example: T2-1)
Node Number: (for example: 1)
Tone on seizure: (For example: True)
Q931 signal variant: (for example: ISDN all countries)
Number Of Digits To Send: (for example: 10)
DID transcoding: (for example: True)

P. 2 Ref. ENTP0409C05TEUS.doc Issue 02

Action Press CTRL+v two times to validate the creation

Entry Press CTRL+c as many times as needed to come back on main menu
Remark:
Q931 Signal variant
Select the signaling variant for the type of network that can be accessed by
the trunk group:
ISDN FRANCE: to use "Numéris".
ISDN all countries: for other ISDN networks.
DID Transcoding
When the DID range supplied by the public network does not match the
internal numbering, validate the DID translator; false if no DID translation is
needed.

1.3. Program the number of digits unused

On mgr
Select Trunk groups
Trunk group
Entry Trunk group id: (for example: 2)
No. of digits unused (ISDN): (for example: 5)
B Channel Choice: No
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu
Remark:
No. of digits unused (ISDN):
This attribute is used when the DID number is generated from the number
received from the public network.
Indicate the number of digits to remove from the start so that the last digits
remain for analysis in ISDN DID (in FRANCE the dialing plan has 10 digits and
only 4 digits are used for DID, which means you must enter 6 for this item).

Issue 02 Ref. ENTP0409C05TEUS.doc P. 3

1.4. Create the T2 line(s) in the trunk group

On mgr
Select Trunk groups
Trunk group
T2/T1/T0 access
Action Create
Entry Trunk group id.: (for example: 2)
Physical address: (for example: 1-5-0)
Access type: T2
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu
Remark:
Physical Address:
Enter the physical position of the access in the format: Media Gateway No -
(Coupler) Board No - Device No
Time Slots:
Automatically completed by the system

1.5. Program the synchronization priorities

On mgr
Select Shelf
Digital access
Entry Shelf address: (for example: 1)
Board address: (for example: 5)
T0/T2 access: (for example: 0)
Synchronization priority: (for example: 0)
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu

P. 4 Ref. ENTP0409C05TEUS.doc Issue 02

1.6. Create the outside line prefix in order to seize this T2 trunk group

On mgr
Select Translator
Prefix plan
Action Create
Entry Number: (for example: *82)
Prefix Meaning: (for example: Professional TG With Overlapping)
Prefix Information: (for example: 2) (the trunk group id)
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu

1.7. Reset the board in order to initialize the trunk group

On the call server

Issue 02 Ref. ENTP0409C05TEUS.doc P. 5

1.8. Check the status of the trunk lines

On the call server

Note: This command is used to display the busy status of trunks of the selected T2 trunk
group and the alarm status of the T0 board supporting the trunk group.
- F (free), B (busy): the trunk group works correctly
- hs (out of service): the trunk group is out of service.

P. 6 Ref. ENTP0409C05TEUS.doc Issue 02

PROCEDURE

OBJECTIVE

- To learn how to create ISDN T1 CSS trunk groups with mgr

OVERVIEW
Create a T1 trunk groups by using the mgr application. Assign prefix numbers to each trunk
group in order to seize them.
Call other nodes in the classroom to verify that these trunk groups are correctly configured.

Issue 02 Ref. ENTP0409C07TEUS.doc P. 1

PROCEDURE

1. T1 CCS trunk group management

1.1. Check the presence of the required boards (e.g: PRA T1 for a T1 trunk group)

On the call server

Login mtcl
Command Config: (for example: 0) (0=shelf number)
+----------------------------------------------------------------------+
Result | Cr | cpl | cpl type | coupler state | coupler ID |
|----|-----|--------------|--------------------------|-----------------|
| 1 | 0 | GD | IN SERVICE| NO OPS FILE |
| 1 | 1 | UAI 4 | IN SERVICE| NO OPS FILE |
| 1 | 2 | PRA T1 | IN SERVICE| NO OPS FILE |
| 1 | 3 | BRA 4 | IN SERVICE| NO OPS FILE |
| 1 | 5 | PRA T2 | IN SERVICE| NO OPS FILE |
+----------------------------------------------------------------------+

1.2. In case of PRA T1 boards: create a T1 trunk group

On mgr
Select Trunk groups
Action Create
Entry Trunk Group Id: (for example: 3)
Trunk Group Type: T1CCS
Trunk Group Name: (for example: T1CCS-1)
Node Number: (for example: 1)
Tone on seizure: (for example: True)
Q931 signal variant: (for example: ISDN all countries)
Carrier ID: AT&T
Number Of Digits To Send: (for example: 10)
Auto. DTMF dialing on outgoing call: YES
DID transcoding: (for example: True)

P. 2 Ref. ENTP0409C07TEUS.doc Issue 02

Action Press CTRL+v two times to validate the creation

Entry Press CTRL+c as many times as needed to come back on main menu
Remark:
Q931 Signal variant:
Select the signaling variant for the type of network that can be accessed by
the trunk group:
ISDN FRANCE: to use "Numéris".
ISDN all countries: for other ISDN networks.
DID Transcoding:
When the DID range supplied by the public network does not match the
internal numbering, validate the DID translator; false if no DID translation is
needed.

1.3. Program the number of digits unused

On mgr
Select Trunk groups
Trunk group
Entry Trunk group id: (for example: 2)
No. of digits unused (ISDN): (for example: 5)
B Channel Choice: No
DTO joining: True
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu
Remark:
No. of digits unused (ISDN):
This attribute is used when the DID number is generated from the number
received from the public network.
Indicate the number of digits to remove from the start so that the last digits
remain for analysis in ISDN DID (in FRANCE the dialing plan has 10 digits and
only 4 digits are used for DID, which means you must enter 6 for this item).

Issue 02 Ref. ENTP0409C07TEUS.doc P. 3

1.4. Create the T1 line(s) in the trunk group

On mgr
Select Trunk groups
Trunk group
T2/T1/T0 access
Action Create
Entry Trunk group id.: (for example: 3)
Physical address: (for example: 1-2-0)
Access type: T1 CCS
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu
Remark:
Physical Address:
Enter the physical position of the access in the format: Media Gateway No -
(Coupler) Board No - Device No
Time Slots:
Automatically completed by the system

P. 4 Ref. ENTP0409C07TEUS.doc Issue 02

1.5. Program the synchronization priorities

On mgr
Select Shelf
Digital access
Entry Shelf address: (for example: 1)
Board address: (for example: 2)
T0/T2 access: (for example: 0)
Synchronization priority: (for example: 0)
Used access: Yes
Synchronization priority: (for example: 10)
Multiframe type: ESF AT&T TR54016
Line type: Short Haul 0 to 45 meters
Pulses encoding: B8ZS
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu

1.6. Create the outside line prefix in order to seize this T1 trunk group

On mgr
Select Translator
Prefix plan
Action Create
Entry Number: (for example: *83)
Prefix Meaning: (for example: Professional TG With Overlapping)
Prefix Information: (for example: 3) (the trunk group id)
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu

1.7. Reset the board in order to initialize the trunk group

On the call server

Issue 02 Ref. ENTP0409C07TEUS.doc P. 5

1.8. Check the status of the trunk lines

On the call server

Login mtcl
Command trkstat 3 (3= trunk group Id)
+-------------------------------------------------------------------+
Result +-------------------------------------------------------------------+
| T R U N K S T A T E PRA T1 Coupler Crystal Nbr = 1 |
| IN SERVICE Coupler Nbr = 2 |
+-------------------------------------------------------------------+
| Type: T1 CCS Access 0: ENABLE level2: INIT_T2 |
| B channel rate: 64K |
| |
| Trunk Grp 3 3 3 3 3 3 3 3 3 3 3 3 |
| Channel 1 2 3 4 5 6 7 8 9 10 11 12 |
| State F F F F F F F F F F F F |
| |
| Trunk Grp 3 3 3 3 3 3 3 3 3 3 3 |
| Channel 13 14 15 16 17 18 19 20 21 22 23 |
| State F F F F F F F F F F F |
|-------------------------------------------------------------------|
| F: Free | B: Busy | Ct: busy Comp trunk | Cl: busy Comp link |
| | Cr: busy Comp trunk for RLIO inter-ACT link |
|-------------------------------------------------------------------|
| ALARMS COUNTERS |
|-------------------------------------------------------------------|
| LMFA | RAI | LFA | AIS | LOS | MIC_LOOP |
| 0 | 0 | 0 | 0 | 0 | 0 |
|-------------------------------------------------------------------|
| LMFA: Loss of Multi Frame Alignement| RAI: Remote Alarm Indication|
| LFA: Loss of Frame Alignement | AIS: Alarm Indication signal |
| LOS: Loss Of Signal | |
|-------------------------------------------------------------------|
Remark:
This command is used to display the busy status of trunks of the selected T1
CCS trunk group and the alarm status of the T0 board supporting the trunk
group.
- F (free), B (busy): the trunk group works correctly
- hs (out of service): the trunk group is out of service.

P. 6 Ref. ENTP0409C07TEUS.doc Issue 02

Trunk Groups

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To maintain the system Trunk Groups with “Web maintenance Tool”

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409M01TEUS Issue 02

465
Trunk Group
Maintenance

Information about the status of the trunk group

For
Foraapermanent
permanentedition
editionrefresh
refresh
this parameter is optional
this parameter is optional

trkstat (-r) <Trunk group number>

Indicate the position of the coupler

Indicate the position of the coupler
supporting the access
supporting the access

trkstat (-r) <Media Gateway> <board Number>

All Rights Reserved © 2008, Alcatel-Lucent 2

-r to refresh the screen

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409M01TEUS Issue 02

466
Web Tool
Access to the maintenance tool

Access to the tool (via a Web browser)

The URL used to access to the WebTool as to be:

http://OmniPCX-Enterprise-IP@/webtool2/

Ex:

At the connection to the system, a Security message is displayed

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409M01TEUS Issue 02

467
Web Tool
Access to the maintenance tool (Cont’)

To access to the maintenance Web Tool:

The language has to be selected

The “mtcl” login and password have to be given

All Rights Reserved © 2008, Alcatel-Lucent 4

The default “mtcl” password can not be used. This one has to be therefore modified

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409M01TEUS Issue 02

468
Web Tool
Access to the Stand-Alone system status

When authenticated, a menu is displayed on the left of page

Press on “Toolbox” menu to reach the Stand-Alone system status Tool

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409M01TEUS Issue 02

469
Webtool main menu
Trunk Group maintenance

Select “Trunk group Status” menu

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409M01TEUS Issue 02

470
Trunk Group maintenance
List of know trunk groups

This Submenu allows to access to the list of the available system trunk groups

Trunk groups

ABC-F links

It is possible to get more detail (real-time status) selecting the “Location”

column information

All Rights Reserved © 2008, Alcatel-Lucent 7

The information « Type » corresponds to the Trunk Group type:

Trunk group 10 -> Type T0
Trunk group 12 -> Type T2

The “Variante” information corresponds to the signaling protocol type

T2= ISDN (France)
ISDN= ISDN all countries

The information « Prefix » corresponds to the trunk group seizure prefix

#010: for the trunk group 10
#012: for the trunk group 12

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409M01TEUS Issue 02

471
Trunk Group maintenance
Trunk Group details

The following example show a T2 trunk group

The trunk group has 30 B channels

Channel 1 to 15 and 17 to31

Channel 16 is reserved for signaling

Color meaning

The channel with green color are free

The channel 1 (color: deep pink) is used for an incoming call

The channel 2 (color: light pink) is used for an outgoing call

All Rights Reserved © 2008, Alcatel-Lucent 8

Full color code meaning:

Red

Green

White

Deep pink

Light pink

Yellow
Not viewable with new systems
(under topology conditions for former releases)
Light grey

Deep blue

Light blue

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409M01TEUS Issue 02

472
Trunk Group maintenance
Trunk Group details (Cont’)

Example of “Out Of Service” trunk group

All the channel appear in “grey” color

In this case it is necessary to check the connection between the interface and the
public carrier

In case of T2 connection, it is possible to check the alarm on the T2 interface.

Alarm NOS: No signal

on the line

All Rights Reserved © 2008, Alcatel-Lucent 9

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409M01TEUS Issue 02

473
All Rights Reserved © 2008, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – Trunk Groups

Ref. ENTP0409M01TEUS Issue 02

474
Alcatel-Lucent OmniPCX Enterprise
Trunk groups

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to create Trunk Groups

MANAGEMENT

1. Create a MG-PRA E1 board in the main rack

2. Create a MG-BRA board in the extension rack

3. Create a T0 trunk group and a T2 or a T1 CCS trunk group (without DDI translation)
Index T0: X0
Index T2/T1: X2
Number of digits unused: 5
Note: X = Node number

4. Create the prefix #0X0 to seize the T0 trunk group (format: 10 digits)
Create the prefix #0X2 to seize the T2/T1 trunk group (format: 10 digits)
Note: X = Node number

5. Test your management:

By making incoming and outgoing calls
By using the command: trkstat ( to view the trunk group’s channels) and the web tool.

Issue 02 Ref. ENTP0409H01TEUS.doc HO. 1

HO. 2 Ref. ENTP0409H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

477
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

478
Alcatel-Lucent OmniPCX Enterprise

System synchronization

All Rights Reserved © 2005, Alcatel-Lucent 1

OBJECTIVES

To describe synchronization principles

To describe the principles of the synchronization per domain

Alcatel-Lucent OmniPCX Enterprise – System synchronization

Ref. ENTP0437P01TEUS Issue 04

479
System synchronization
Principles

The good transmission of communications over a digital access (T0, T1, T2 or

MIC) is linked to a common synchronization between all the systems

This reference is provided by the public carrier

The ACTs of a system and of a node of an ABC network must be synchronized

via this clock

Management of a synchronization plan to allocate priorities to the various

digital accesses used

Broadcast of the clock in the system using the inter-ACT links (INT2, INTOF or
RT2)

Broadcast of the clock in the network using the ABC links

All Rights Reserved © 2005, Alcatel-Lucent 2

The public carriers must be synchronized with each other.

This common clock can be retrieved at any time on T1, T2 or MIC access (level 2 permanent) or in communication for T0 access
(level 2 established during the call).
The 512 kHz clock is extracted from the frame of a digital access.

The synchronization plan is one the first thing to be defined during an installation (in stand alone and in network).
The synchronization plan allows to allocate a synchronization priority to the various available resources (public accesses, private
accesses, ABC links, etc.) and to guarantee the use of a common clock on all systems.

The RT2 links must always be established (no multiplexer) in order to have a good synchronization resource.

Alcatel-Lucent OmniPCX Enterprise – System synchronization

Ref. ENTP0437P01TEUS Issue 04

480
System synchronization
TDM Architecture (Crystal)

In this kind of architecture, the inter-ACT links are digital (INT2, INTOF or RT2)

The synchronization resources can be located in extension shelves

The system is able to:

Broadcast the clock from the crystal 0 to a peripheral shelf

Synchronize itself on a link from a extension shelf

All the shelves belong to the synchronization domain by default (domain 0)

200 levels of synchronization priority: 0 to 199

All Rights Reserved © 2005, Alcatel-Lucent 3

The value 0 corresponds to the maximum priority. It is reserved for the public accesses (T1 / T2).
The value 255 means that the clock is ignored on the access.

Alcatel-Lucent OmniPCX Enterprise – System synchronization

Ref. ENTP0437P01TEUS Issue 04

481
System synchronization
TDM Architecture (Crystal)

Example: TDM Architecture

OmniPCX Enterprise
ACT 2
INTOF link

Sy RT2 link
nc
chro hr

ior 2
0
Syn o

Pr 2 N°
ACT

ity
0

T
T2 N ACT 3
Prior °1
ity 0
T0
Carrier ty 5
Priori
Sy
nc
hro

INTOF link

ACT 1

Domain 0
All Rights Reserved © 2005, Alcatel-Lucent 4

In this example, the system has 2 T2 accesses and 1 T0 access.

The level 2 of a T2 being permanent, it is possible to retrieve the clock and to synchronize the system on the public carrier.
The associated priority in management 0 corresponds to the maximum priority (The 2 T2 provide the same clock, the system will
choose the first access to be in service). In this example, the T2 #1 synchronizes the system.
If the T2 become out of order, it is possible to synchronization the system on the T0 access of the ACT #3. The priority is lower
(5) therefore this clock can, be used only as a backup.

The ACT #1 and #2 are synchronized via the INTOF links of the ACT #0. The ACT #3 is synchronized by the RT2 link from the ACT
#2 (3-level architecture).

If the T2 #1 is out of order, the synchronizing resource will become the T2 #2 (priority equal and higher compared to the T0
access).
The clock will synchronize the ACT #0 via the INTOF link (modification of the synchronization direction).
The synchronization of the ACT #1 and #3 do not change.

All the shelves belong to the same synchronization domain.

Alcatel-Lucent OmniPCX Enterprise – System synchronization

Ref. ENTP0437P01TEUS Issue 04

482
System synchronization
IP Architecture (Media-Gateway & Crystal)

In this kind of architecture, the inter-ACT links cannot broadcast a 512 kHz
clock

Synchronization resources must be located in:

The main rack of a Media-Gateway
An extension rack over IP for a Crystal architecture

Each synchronizing resource in a shelf defines an independent synchronization

domain
A synchronization resource can be broadcast in the same domain

55 levels of synchronization priority: 200 to 254

All Rights Reserved © 2005, Alcatel-Lucent 5

The value 200 (highest priority in a domain) is reserved to the public accesses (T1 / T2).
The value 255 means that the clock is ignored on the access.
If there is no synchronizing resource in a shelf, the synchronization will be generated locally (by the GD or INTIP board).

The Id. of a synchronization domain is the Id. of the shelf where the synchronization resource is located.
Example: Synchronizing T2 in the main rack le rack principal (ACT 3) of a Media-Gateway creation of the synchronization
domain #3.

The 55 priority levels are independent between the domains and the nodes of an ABC network.
The resource with the priority 200 of the domain #3 will never synchronize a shelf belonging to the domain #5 or to the default
domain.

Crystal shelves connected via a compressed linked use the synchronization domains following the same principles (no
synchronization retrieval from this kind of link).

Alcatel-Lucent OmniPCX Enterprise – System synchronization

Ref. ENTP0437P01TEUS Issue 04

483
System synchronization
Architecture IP (Media-Gateway & Crystal)

Example: IP architecture
Domain 2
Domain 0
OmniPCX Enterprise
ACT 2

0
ior °2
20
Domain 3

Pr T2 N
ity
T2 N ACT 3
Prior °1
ity 0 T0 05
2
Carrier r i ty
Prio ACT 4

Independent

ACT 1

IP network

All Rights Reserved © 2005, Alcatel-Lucent 6

In this example, the call server is a CPU7.

ACT #1 and #2 and the Media-Gateway shelves #3 and #4 belong to are linked to the CS via the IP network. It is not possible to
broadcast a clock to synchronize these shelves.

The T2 #1 synchronizes the shelf #0 (maximum priority 0). The domain 0 is always allocated to the ACT where the CPU is located.

The T2 “2 synchronizes the ACT #2. As this shelf is not connected via an INT2 or INTOF link, the use of the synchronization
domains is mandatory.
The priority 200 (highest priority in a domain) allocated to the T2 will create a synchronization domain #2 (Id. Of the ACT).

The T0 synchronizes the shelf #3 of in the main rack when a communication is established. This shelf is connected via IP to the
Call Server: the use of the synchronization domains is mandatory. The priority 205 will create the synchronization domain #3 (Id.
Of the ACT).
As the shelf #4 is an extension rack of the shelf #3 and as no synchronizing resource is declared in the rack, it belongs to the
domain #3.
The CPU-GD will broadcast the clock to the MEX boards of the Media-Gateway via the HSL link (The HSL link is seen as
INT2A/INT2B link for the system).

The ACT #1 has no synchronizing resource. It stays independent for the clock that will be generated bu the iNTIP board and
broadcast to the shelf’s boards.

Alcatel-Lucent OmniPCX Enterprise – System synchronization

Ref. ENTP0437P01TEUS Issue 04

484
Alcatel-Lucent OmniPCX Enterprise
Synchronization

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage the synchronization on the system.

MANAGEMENT

1. The main synchronization will be performed on the MG PRA-E1 board

1.1. The synchronization priority will be equal to 200

1.2. Check the synchronization by using infocs command.

Issue 02 Ref. ENTP0437H01TEUS.doc HO. 1

HO. 2 Ref. ENTP0437H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

487
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

488
Alcatel-Lucent OmniPCX Enterprise

DDI translator

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the principles of the DDI translation for incoming and outgoing calls

Alcatel-Lucent OmniPCX Enterprise – DDI translator

Ref. ENTP0424P01TEUS Issue 02

489
DDI translator
The different elements

The different elements

On one hand of the OmniPCX Enterprise: the internal users

The dialing plan of the installation defines the directories numbers linked to the
need of the customer

On the other hand: the range of numbers given by the Central Office
Installation number
DDI range

Between them: the transcoding

Management:
Identification of the external ranges of numbers (DDI numbers)
Identification of the internal ranges of numbers (directory numbers)
Establishment of the link between those ranges

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – DDI translator

Ref. ENTP0424P01TEUS Issue 02

490
DDI translator
Transcoding needs

The transcoding has to be managed systematically for different reasons:

Public numbers are equivalent to the internal directory numbers:

The system has to know the subscribers which do not have a DDI number, so as to
build up the right ISDN number for an outgoing call

Public numbers are different to the internal directory numbers:

The DDI numbers have to be transcoded into internal numbers
Example: DDI number ‘2000’ transcoded into internal number ‘6000’

The length of the public numbers is different to internal numbers:

The DDI numbers have to be adapted to the internal numbering plan
Example: DDI number ‘2000’ transcoded in internal ‘42000’

Suppl.Inst.Nbr.
To set up the right Calling Line Identification (CLI) for outgoing calls
For a non DDI user, the Attendant number should sent in case of outgoing call

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – DDI translator

Ref. ENTP0424P01TEUS Issue 02

491
DDI translator
Numbering Plan Descriptor

A NPD (Numbering Plan Descriptor) is used to:

Select the DDI translator to use

For outgoing calls (to reach the expected internal user/service)

For incoming calls (to set up the right CLI)

Determine the identification to send

Entity source
NPD source
Nothing
Personal calling number authorization

The NPD used is managed in the trunk group selected to establish the
communication

All Rights Reserved © 2008, Alcatel-Lucent 4

The trunk group used to establish the call is associated to the NPD (Numbering Plan Descriptor) 14 by default (15 in case DDI
translation activation)
Warning, in case of ARS feature use, the NPD to use can be provided by the ARS route itself or the trunk group according to the
configuration

Alcatel-Lucent OmniPCX Enterprise – DDI translator

Ref. ENTP0424P01TEUS Issue 02

492
DDI translator
Incoming call mechanism

r
be
um
n 00
C alle
1
d
33 Central Office
140
02
ISDN
Trunk group

Trunk
Trunkgroup
group
User DDI transcoding:Yes
³³DDI transcoding: Yes
User6000
6000
³³Entity:
³³Nb
Nbof
ofdigits
digitsunused (ISDN):66
unused(ISDN):
Entity:11 ³³Public NPD id: 15
Public NPD id: 15

NPD
NPD15
15
³³Called
CalledDDI Translator:00
DDITranslator:

DDI
DDItranslator
translator00
³³33xx
33xx-->
-->60xx
60xx

All Rights Reserved © 2008, Alcatel-Lucent 5

A Numbering Plan Descriptor (NPD) is used to translate the received number (incoming call)

Alcatel-Lucent OmniPCX Enterprise – DDI translator

Ref. ENTP0424P01TEUS Issue 02

493
DDI translator
Outgoing call mechanism: DDI user

Without ARS and with standard management t

en
io ns
at 00
fic Central Office
Ide
nt i 33
01
214
ISDN
Trunk group

Trunk
Trunkgroup
groupseizure
seizureprefix
prefix
³³route private:NO
route type,private:
type, NO
User
User6000
6000 Trunk
Trunkgroup
group
Entity:11
³³Entity: ³³DDI Transcoding:Yes
DDITranscoding: Yes
³³Public NPD: 15
Public NPD: 15
Entity
Entity11 NPD
NPD15
15
³³Installation No:21401
InstallationNo: 21401 ³³Installation
Installationnumber source:Entity
numbersource: Entity
³³Supplementary
SupplementaryInstallation
InstallationNo*:
No*: 3333
3333 ³³Default
Default number source:Entity
number source: Entity
³³Calling
CallingDDI id:00
DDIid:
The number “6000” belongs to the range and is DDI
DDItranslator
translator00
transcoded in “3300” ³³33xx
33xx-->
-->60xx
60xx

All Rights Reserved © 2008, Alcatel-Lucent 6

³ Supplementary Installation number usually corresponds to the ‘Entity’ or ‘Attendant Group’ call number
This number is used, by the system, to build up the identification of the ‘none DDI’ subscribers for the outgoing call
This configuration field corresponds to a “public” number

The Numbering Plan Descriptor (NPD) is also used to build up the identification of the caller:
- Outgoing calls: Installation number + n° supplementary installation number (for none DDI subscribers)

Alcatel-Lucent OmniPCX Enterprise – DDI translator

Ref. ENTP0424P01TEUS Issue 02

494
DDI translator
Outgoing call mechanism: none DDI user

Without ARS and with standard management

t
sen
t ion
a 3
fic 33 Central Office
nt i 3
Ide 1
40
21
ISDN
Trunk group

Trunk
Trunkgroup
groupseizure
seizureprefix
prefix
route type, private:NO
³³route type, private: NO
User
User6100
6100 Trunk
Trunkgroup
group
Entity:11
³³Entity: ³³DDI Transcoding:Yes
DDITranscoding: Yes
³³Public NPD:15
PublicNPD: 15
Entity
Entity11 NPD
NPD15
15
³³Installation No:21401
InstallationNo: 21401 ³³Installation
Installationnumber source:Entity
numbersource: Entity
³³Supplementary No*: 3333
Supplementary InstallationNo*:
Installation 3333 Default number source:Entity
³³Default number source: Entity
³³Calling
CallingDDI id:00
DDIid:
DDI
DDItranslator
translator00
The number “6100” does not belong to the range ³ ³³33xx
33xx-->
-->60xx
60xx

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – DDI translator

Ref. ENTP0424P01TEUS Issue 02

495
All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – DDI translator

Ref. ENTP0424P01TEUS Issue 02

496
Alcatel-Lucent OmniPCX Enterprise
DID Translator

PROCEDURE

OBJECTIVE

- To learn how to configure the DID Translator (default configuration)

OVERVIEW
The DID service allows an internal user to be called directly from the public network. Such users
(that can be reached directly) are called "DID users" (or subscribers). Other users (referred as
"non DID users") cannot be called directly. Calls to non DID users are made via the attendant
(manual or automated), who transfers the call.

Issue 01 Ref. ENTP0424C05TEUS.doc P. 1

PROCEDURE

1. DID rule definition

Application Configuration Tab PCX

Path / Translator / External Numbering Plan / Default DID num. Translator
Action Create
Parameters First External Number: 1000 (Public No.)
First Internal Number: 31000 (internal corresponding No.)
Range Size: 100
Unique Internal Number: No
Action Click on “ ” to valid

Note: Unique Internal Number: Yes can be used in case of DID range reservation (the
customer has already reserved on the public Operator side a range of DID
numbers, but this range is not assigned to any extension yet

Note: This object can also be found in:

Path / Translator / External Numbering Plan / DID numbering Translator

Object “0” (DID num. Transl. Identifier)
Sub-Path …/ DIDI number Translator Rules
Parameters First External Number: 1000 (Public No.)
First Internal Number: 31000 (internal corresponding No.)
Range Size: 100
Unique Internal Number: No

Note: The default DID translator has the Id “0”

P. 2 Ref. ENTP0424C05TEUS.doc Issue 01

2. Two different ways are available to activate the DID translation in a Trunk group

2.1. Trunk Group Main parameters

Application Configuration Tab PCX

Path / Trunk Group
Object “12” (Trunk Group Id)
Parameters DID Transcoding:
Action Click on “ ” to valid

Note: With configuration, a default NPD (No. depends on Trunk Group Signaling Variant
and Country Parameters) will point onto the Default DID Translator (Id =”0”)

2.2. Trunk Group Submenu

Application Configuration Tab PCX

Path / Trunk Group
Object “12” (Trunk Group Id)
Sub-Path …/ Trunk group NPD Selector
Object “1” (Instance)
Parameters Public NPD ID: 9
Management Mode: Automatic (default value)
Public DID Transcoding:
Action Click on “ ” to valid
Result Public NPD ID: 10 (Remember this value)
Management Mode: Automatic (default value)
Public DID Transcoding:

Note: This configuration will automatically modify the “Public NPD Id” parameter value

Issue 01 Ref. ENTP0424C05TEUS.doc P. 3

3. Numbering Plan Descriptor (DID translator Id verification)

Application Configuration Tab PCX

Path / Translator / External Numbering Plan / Numbering Plan Descriptor
Action Filter the expected NPD Id (10 in this example)

Parameter Description Identifier: 10

Installation Number source: Entity Source
Default Number source: Entity Source
Called DID identifier: 0 (used for incoming calls)
Calling DID identifier: 0 (used for outgoing calls)

4. Calling Line Identification parameters (Caller’s Entity)

Application Configuration Tab PCX

Path / Entity
Object “1” (Entity I for example)
Parameters Installation No. (ISDN): 20143 (Public Installation number)
Supplement. Install. No (ISDN): 1000 (Public Id for the None DID users)
Action Click on “ ” to valid

P. 4 Ref. ENTP0424C05TEUS.doc Issue 01

DDI Translator / NPD

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To maintain the DDI transcoding

Alcatel-Lucent OmniPCX Enterprise – DDI Translator / NPD

Ref. ENTP0424M05TEUS Issue 02

501
Maintenance
Numbering Plan Descriptor

The command “looknpd i” allows to find which Numbering Plan Descriptor is

used

Mon Jan 7 23:19:12 CET 2008

Outgoing Prefix : #012

Directory Nb : 31000

Trunk seizure case, entity Nb = 1, TG Nb = 12 with lignpriv = FALSE : publicNPD used

====================================================================
| NUMBERING PLAN DESCRIPTOR No 10 |
====================================================================
| Calling NPI TON = 01 : TON : UNKNOWN NPI : ISDN / Telephony
| Called NPI TON = 01 : TON : UNKNOWN NPI : ISDN / Telephony
| Incoming DDI identifier = 0
| Outgoing DDI identifier = 0
| Authorise private data use = 0 : FALSE
| Used Installation Number = 0 : ENTITY SOURCE ==> 20143
| Used Default Number = 0 : ENTITY SOURCE ==> 1000
| Installation Number = Not Defined / Not Used
| Default Number = Not Defined / Not Used
====================================================================

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – DDI Translator / NPD

Ref. ENTP0424M05TEUS Issue 02

502
Maintenance
DDI translator information

The “DDItest” maintenance command allows to:

Check the configuration

Test an incoming/outgoing translation

general DDI or public overflow : [g]/p

DDI id : <0..99> : 0
DDItest

Mon Jan 7 23:28:38 CET 2008

local number : 31000
0 : exit found external number : 1000
1 : select DDI
2 : incoming DDI
3 : outgoing DDI
4 : view selected DDI data
5 : view selected DDI data order by internal number
6 : exec time
choice : DDI Mode : 0 , nb :2
DDI slice 1 :
start ext : 1000
start int : 31000 sort : 1
size 100, unique int.:NO,
in range:0, thin sector:0

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – DDI Translator / NPD

Ref. ENTP0424M05TEUS Issue 02

503
All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – DDI Translator / NPD

Ref. ENTP0424M05TEUS Issue 02

504
Alcatel-Lucent OmniPCX Enterprise
DID Translator

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage the default DDI Translator

MANAGEMENT

1. Manage the DID Translator according to the file site (or use the configuration given by the
trainer)

2. Check your configuration with the “didtest” command

3. Test the configuration to check if the stations can be reached from the public network

Issue 02 Ref. ENTP0424H01TEUS.doc HO. 1

HO. 2 Ref. ENTP0424H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

507
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

508
Alcatel-Lucent OmniPCX Enterprise

External callback translator

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the External Callback Translator

Alcatel-Lucent OmniPCX Enterprise – External callback translator

Ref. ENTP0427P01TEUS Issue 02

509
External Callback Translator
Generalities

The main objective of the external callback translator is to be able to take into
account the “Caller Id” in case of external incoming call
This information is taken from the SETUP message

As soon as this object is configured the Alcatel-Lucent OmniPCX Enterprise is

able to analyze and treat the “Caller Id” in order to:
Display the caller number in case of external incoming call on the extensions
display
In case of none answered calls, it is therefore possible to check the list of
the (external) unanswered calls
It is also possible to use the “callback” feature when consulting the unanswered
calls list

All Rights Reserved © 2008, Alcatel-Lucent 2

When configured, the External Callback Translator also allows the speed dial number reorganization (in this case the
corresponding “speed dial directory name” is displayed instead of the public Id

Alcatel-Lucent OmniPCX Enterprise – External callback translator

Ref. ENTP0427P01TEUS Issue 02

510
External Callback Translator
Mechanism

It is possible (and recommended) to manage several entries in the External

Callback Translator

Each entry corresponds to a public/private numbering format

At an incoming call reception, the Alcatel-Lucent OmniPCX Enterprise analyses

the “Caller Id” and tries to find, as much as possible, an External Callback
Translator entry matching this Id (1)
If no specific Entry has been found, a default one is used (DEF)
As soon as an entry is found (specific or default one), the corresponding
behavior is applied
It is possible to:
Add some digits (usually a trunk group seizure prefix)(2)
Remove some digits (usually in case of International Id or Private Id)(3)

All Rights Reserved © 2008, Alcatel-Lucent 3

1) Except the default External Callback Translator Entry (DEF), an Entry corresponds to the beginning of the Calling Id (e.g. “33”
for the French international Id, “298” for a French local Area Id…)

2) To allow callback, the outgoing seizure prefix must be added to the head of the number, followed, where appropriate, by
another call area related prefix

3) Depending on the country and its numbering plan, characters need to be removed from the head of the number

Alcatel-Lucent OmniPCX Enterprise – External callback translator

Ref. ENTP0427P01TEUS Issue 02

511
External Callback Translator
Example

ISDN “SETUP” message extract:

Called number : 170220155

Calling number: 298152520

External Call Back Translator:

DEF: Corresponding
Digits to add: 0 0 called party
Number of digits to be removed: 0

0 = ARS prefix Displayed number: “ 0298152520 ”

0 = Public Operator Id

All Rights Reserved © 2008, Alcatel-Lucent 4

The “Called number” in the ISDN setup message corresponds to the expected called party (the connected extension can be
different than the initial called party in case of Call pickup / Call Distribution features use…)

Alcatel-Lucent OmniPCX Enterprise – External callback translator

Ref. ENTP0427P01TEUS Issue 02

512
External Callback Translator
Minimum configuration

By default, the External Callback Translator may take into account the national
& international incoming calls in order to display the correct Ids

The “national Ids” can be taken in to account by the “Default” Callback

translator:
Basic number: DEF
No.Digits To Be Removed: 0
Digits To Add: 0 0
Where “0” = ARS or trunk group seizure prefix
“0” = Public Operator Id (French national example) / can also be “AREA code”…

The “international Ids” will be taken into account by the Entry:

Basic number: A (1)

No.Digits To Be Removed: 1
Digits To Add: 0 00
Where “0” = ARS or trunk group seizure prefix
“00” = International Prefix

All Rights Reserved © 2008, Alcatel-Lucent 5

1) An international ID is seen starting with “A”, this letter has to be removed !

Remark:
In case of Private network incoming call, the Calling Ids start with a B. It is therefore mandatory to manage a specific Entry for
this kind of Ids:

- Basic number: B
No.Digits To Be Removed: 1
Digits To Add: 0 (ARS prefix…)

Alcatel-Lucent OmniPCX Enterprise – External callback translator

Ref. ENTP0427P01TEUS Issue 02

513
All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – External callback translator

Ref. ENTP0427P01TEUS Issue 02

514
Alcatel-Lucent OmniPCX Enterprise
External callback translator

PROCEDURE

OBJECTIVE

- To learn how to configure the external callback translator

OVERVIEW
Create the external callback translator by using the mgr application. Check that this object
allows:

- To display the external caller identification

- To call back the unanswered calls

Issue 02 Ref. ENTP0427C02TEUS.doc P. 1

PROCEDURE

1. Manage the external call back translator

On mgr
Select Translator
External Numbering Plan
Ext. Callback Translation
Action Create
Entry Basic Number: (for example: DEF)
No. Digits To BE Removed: (for example: 0)
Digits To Add: (for example: 9)
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu
Remark:
Basic number:
Enter the area code, i.e. the first digit(s) of the number received,
indicating the area which is the source of the call. Example: A for an
international call.
No. Digits to be removed:
Enter the number of characters to be deleted at the start of the number
received; Example: 1 to delete the A.
Digits to add:
Enter the digit(s) to be added which correspond to the prefix.
Example: 000
9: trunk group seize prefix,
00: international access.

P. 2 Ref. ENTP0427C02TEUS.doc Issue 02

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage the external callback translator

MANAGEMENT

1. Check that the external callback translator is empty (default configuration).

Ask your neighbor to check that his installation number is managed in the entity 1 of his
system; this number is required to send the caller’s identity when an outgoing call is
performed.

Path Entity
Action Edit the entity No. 1
Parameters Installation number (ISDN): 2 CR 0
Supplement Install No. (ISDN): 3 S 000
with
CR: ClassRoom number
S: System number in the classroom

2. Make an outgoing call from an extension of your neighbor’s system; dial:

- the T2 trunk group prefix: #0 S 2
outgoing call from the system No. S
- the outside number that corresponds to one of the extensions of your system:
02CR03Szzz
Incoming call on the extension 3Szzz of the system No. S in the ClassRoom No. CR
- Is the caller’s identification number completely displayed on your extension?
If it is not, why?

Issue 02 Ref. ENTP0427H01TEUS.doc HO. 1

3. Manage the external callback translator

Path Translator / External Dialing Plan / Ext.Callback Translation

Action Create
Parameters Basic number: DEF
No.Digits To Be Removed: 0
Digits To Add: #0 S 2 (with S: System number)

4. Make the same call from the same extension

Is the caller’s identification number completely displayed on your extension this time?

5. Make the same call from the same extension

Don’t answer the call.
On the called extension, use the ISDN key to test the callback feature.

HO. 2 Ref. ENTP0427H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

519
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

520
Alcatel-Lucent OmniPCX Enterprise

External Call Barring

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To set up the Call Barring Restriction (simple configuration)

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426P01TEUS Issue 02

521
Call Barring Restriction
Generalities

Definition

The Call Barring Restriction is used to control the establishment of the

external calls

The external numbering plan can be fully opened, partially or completely forbidden
(except Emergency calls)

This facility is used to allow/forbid external outgoing calls according to

The calling user

And the called number

Two users, calling the same external number can have a different behavior

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426P01TEUS Issue 02

522
Call Barring Restriction
Involved Objects

The Call Barring Restriction of the Alcatel-Lucent OmniPCX Enterprise is based

on the use of 4 main objects, linked to each others, allowing a large flexibility
of configuration

A logical Discriminator (can be seen as a “pointer”). It can be taken from:

A trunk group in case of Direct trunk group seizure prefix use
The ARS prefix in case of ARS prefix use

The user’s Entity is used to establish the link between a “logical

Discriminator” and a “Real Discriminator”

The “Real Discriminator” contains all the “external numbering plan” (1)

Each entry is associated to an Area (e.g. 0298 Á area 1; 0033 Á area 2…)

The user’s Public Network COS is used to control the access to an area
(allowed, forbidden)
Usually an “Barring Area” corresponds to geographical Area
Area 1 = Local calls for example
Area 2= National calls area

All Rights Reserved © 2008, Alcatel-Lucent 3

1) If a number does not exist in the Real Discriminator, it is not authorized

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426P01TEUS Issue 02

523
Call Barring Restriction
Mechanism (Direct trunk group seizure)

The User wants to call the external number starting with: 0175… using a direct
seizure prefix

1 Trunk Group “X” 2

seizure prefix
Trunk Group: “X” ?
Logical Discriminator: “A”

3
- Entity Entity
- Public Network COS Logical Discriminator “A” ³ Real Discriminator “AA”

4
Real Discriminator AA
(Barring Rules)
Number: 0175 ³ Area 1
5

All Rights Reserved © 2008, Alcatel-Lucent 4

1) The user dials the trunk seizure prefix, then, starts the beginning of the external number
(The corresponding configuration field is: /Translator/Prefix Plan/Professional trunk seize Á Prefix Information: “X” where
“X” = trunk group Id)

2) According to the used prefix, the system finds the corresponding trunk group, and its corresponding “logical discriminator”
(The corresponding configuration field: /Trunk groups “X” (where “X”= Trunk group Id) Á Number compatible with= “A”
where 0<“A”ñ 7)

3) The User’s Entity is checked to find the correlation between the Logical discriminator and the Real one
(This correlation is realized in the submenu: /Entity/Discriminator Selector)

4) The content of the found Real discriminator is checked to find a corresponding entry
The most accurate entry is taken into account. For example, if the given Real discriminator contains both following entries:
- 017
- And 0175
In this example, the second entry will be taken into account !
(This Object is located at: /Translator/External Numbering Plan/Numbering Discriminator/Discriminator Rules)

5) The User’s Public Network COS allows or forbids the corresponding Area
(The system handles 4 system status: Day/Night/Mode1/Mode2. The Areas are controlled for each status)
(The object is located at: /Class of Services/Access COS/Public Access COS/Area Identifier)

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426P01TEUS Issue 02

524
Call Barring Restriction
Mechanism (ARS)

The User wants to call the external number starting with: 0175… using the ARS

1 ARS prefix
Logical Discriminator: “A”

2
- Entity Entity
- Public Network COS Logical Discriminator “A” ³ Real Discriminator “AA”

3
Real Discriminator AA
(Barring Rules)
Number: 0175³ Area 1
4 ³ ARS table “ZZ” ?

All Rights Reserved © 2008, Alcatel-Lucent 5

1) The user dials the ARS seizure prefix, then, starts the beginning of the external number
Directly in the prefix itself, the system finds the “logical discriminator”

(The corresponding configuration field is: /Translator/Prefix Plan/ARS Prof.Trg Grp Seizure ³ Discriminator No.: “A”
where 0<“A”ñ 7)

2) The User’s Entity is checked to find the correlation between the Logical discriminator and the Real one
(This correlation is realized in the submenu: /Entity/Discriminator Selector)

3) The content of the found Real discriminator is checked to find a corresponding entry
The most accurate entry is taken into account. For example, if the given Real discriminator contains both following entries:
- 017
- And 0175
In this example, the second entry will be taken into account !
(This Object is located at: /Translator/External Numbering Plan/Numbering Discriminator/Discriminator Rules)

4) The User’s Public Network COS allows or forbids the corresponding Area
(The system handles 4 system status: Day/Night/Mode1/Mode2. The Areas are controlled for each status)
(The object is located at: /Class of Services/Access COS/Public Access COS/Area Identifier)
If the dialed number is authorized, the corresponding ARS table (“ZZ” in this example) is therefore used

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426P01TEUS Issue 02

525
Call Barring Restriction
Additional possibilities

To forbid the access to a trunk group regardless of the called number

The Trunk Group Access COS authorizes is used. The aim of this specific COS
is only to authorize or forbid the access to a trunk group

By default the access to all the trunk groups is authorized

For each system status (Day/Night/Mode1/Mode2), it is possible to forbid the

access to a given trunk group without interfering with the configuration of the Call
Barring Restriction

This possibility is used to simplify the control of the access to trunk group (not to
to a given called number) without using the connection categories

This Trunk Group Access COS is a sub-object of the Public Access COS

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426P01TEUS Issue 02

526
Limits

Limits

8 Logical discriminators are available for the system

256 different Numbering (Real) Discriminators can be managed

64 areas are available

Each Entity offers the possibility to link the 8 Logical discriminators to

different Numbering discriminators (among 256)

32 Access Classes Of Services

All Rights Reserved © 2008, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426P01TEUS Issue 02

527
Call Barring Restriction
Simple Configuration

By default the trunk group Logical discriminators = -1, that means : No Barring

This value has to be changed in order to use the Barring

This point concerns only the Call Restriction in case of “Trunk group seizure” prefix
use

In case of ARS use, the trunk group parameter has no importance

For a simple configuration, a unique Logical and Real discriminator can be used
(by default the Id “0”)

The different behaviors for outgoing calls between users are realized via the
use of different Public Access COS (and areas)

All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426P01TEUS Issue 02

528
Call Barring Restriction
Simple Configuration (Example 1)

The User 31000 wants to dial “#010 0145985400”

1 #010 2
Trunk Group “10”
seizure prefix
Trunk Group: “10”
Number compatible with: “0”

3
/Entity 1
/User 31000 /Entity_Discriminator_Selector
- Entity 1 Logical Discriminator “0” ³ Real Discriminator “0”
- Public Network COS 2

5 4
Access COS: 2 /Translator/External Numbering Plan
/Numbering Discriminator 0
Area Nb 1
Discriminator Rules
Night: 1 Number: 0145 ³ Area Nb 1
Day: 1
Mode1: 1
Mode2: 1
The Call is authorized

All Rights Reserved © 2008, Alcatel-Lucent 9

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426P01TEUS Issue 02

529
Call Barring Restriction
Simple Configuration (Example 2)

The User 31001 wants to dial the same number “#010 0145985400”

1 #010 2
Trunk Group “10”
seizure prefix
Trunk Group: “10”
Number compatible with: “0”

3
/Entity 1
/User 31001 /Entity_Discriminator_Selector
- Entity 1 Logical Discriminator “0” ³ Real Discriminator “0”
- Public Network COS 3

5 4
Access COS: 2 /Translator/External Numbering Plan
/Numbering Discriminator 0
Area Nb 1
Discriminator Rules
Night: 0 Number: 0145 ³ Area Nb 1
Day: 0
Mode1: 0
Mode2: 0
The Call is not authorized!

All Rights Reserved © 2008, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426P01TEUS Issue 02

530
Alcatel-Lucent OmniPCX Enterprise
External Call Barring

PROCEDURE

OBJECTIVE

- To learn how to configure the External Call Barring

OVERVIEW
The External Call Barring Feature is used to control the establishment of the outgoing calls
Several Database objects have to be taken into account:

- The Logical Discriminators (Trunk group parameters or ARS prefix)

- The Real (Numbering) Discriminator

- The User’s Entity

To set up the correlation between a selected Logical Discriminator and a Real
Discriminator

- User’s Public Network COS

Issue 02 Ref. ENTP0426C03TEUS.doc P. 1

PROCEDURE

1. Logical Discriminator (Pointer)

1.1. This object can either take from the Trunk Group its self in case of trunk group
seizure use

Application Configuration Tab PCX

Path / Trunk groups
Object Selected Trunk Group Id (e.g. 10)
Parameters Number compatible with: 0 (logical discriminator Id)
Action Click on “ ” to valid

Note: By default this field equals “-1”, that means No Barring!

1.2. This object can also be taken from the ARS prefix in case of ARS feature use

Application Configuration Tab PCX

Path / Translator/ Prefix Plan/
Action Create
Parameters Number: 0
Prefix Meaning: ARS Prof. Trg Grp Seizure
Discriminator No: 0 (logical discriminator Id)
Action Click on “ ” to valid

P. 2 Ref. ENTP0426C03TEUS.doc Issue 02

2. Real (Numbering) Discriminator (description of the External Numbering Plan)

Application Configuration Tab PCX

Path / Translator/ External Numbering Plan/ Numbering Discriminator
Object Discriminator 0 (Public) Can be un Other Id *
Path / Discriminator Rules
Action Create
Parameters Call Number: 0145 (for example)
Area Number: 1 (1<value<64)
ARS Route lost number: Id of the ARS table if need
Schedule Number: Id of a Schedule Table linked to the ARS table
Number of digits: 10 (If the numbering format is known)
Action Click on “ ” to valid

Note: (*) By default two real discriminators exist (the 0 & 1). If some others have to be
used (in case of complex configuration, they have to be created!
The ARS parameters will be used only in case of ARS feature use

3. Entity (Correlation between the Logical & Real Discriminators)

Application Configuration Tab PCX

Path / Entities
Object Entity Number 1 (for example)
Path / Discriminator Selector
Parameters Discriminator 00 : 0 (has to correspond to the configuration step 2)
Discriminator 01 : 0
…
Logical Real
Action Click on “ ” to valid

Issue 02 Ref. ENTP0426C03TEUS.doc P. 3

4. Public Network COS (Areas control)

Application Configuration Tab PCX

Path / Class of Service / Access COS
Object Public Network COS number: 2 (for example)
Path / Public Access COS
Action Filter the required Area Identifier(s)
Parameters Area Identifier: 1
Public Access Right Night: 1
Public Access Right Day: 1
Public Access Right Mode 1: 1
Public Access Right Mode 2: 1
Action Click on “ ” to valid

Note: The Public Network COS id depends on the expected configuration & situation
It is possible to set up some different Public Access Right regarding the system
status

5. User parameters

Application Configuration Tab PCX

Path / Users
Action Filter the required user(s) directory number(s)
Parameters Directory number: 31000 (for example)
Entity: 1
Public Network COS: 2
Action Click on “ ” to valid

Note: The User’s Entity and Public Network COS have to be the ones configured in the
previous steps
The “Public Network COS” represents the “Public Access COS Id”

P. 4 Ref. ENTP0426C03TEUS.doc Issue 02

Barring maintenance

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To check the multi translator management for barring

Alcatel-Lucent OmniPCX Enterprise – Barring restriction

Ref. ENTP0426M01TEUS Issue 02

535
Barring restriction
Maintenance

Command: discrlist

(104)xa001004> discrlist

0: Exit
1: Display all the discriminator 0
2: Display one mcdu
3: Create number
4: Delete number
5: change discriminator id
6: Display one mcdu for MAO

Choice:

All Rights Reserved © 2008, Alcatel-Lucent 2

104)xa001004> discrlist

0: Exit
1: Display all the discriminator 0 Display all data of discriminator 0

2: Display one mcdu Display data for the selected mcdu in the selected discriminator

3: Create number
Modification in memory
4: Delete number

Selection of a new discriminator and come back to the choice

5: change discriminator id
1 to display its data

Alcatel-Lucent OmniPCX Enterprise – Barring restriction

Ref. ENTP0426M01TEUS Issue 02

536
Barring restriction
Maintenance

Display of user public network class of services

Command < edsbr -l US0 >

? display the command list

? * display the list of criteria

The useful criteria are:

dir: directory number display
name: name first name display
pna: public network class of service display

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Barring restriction

Ref. ENTP0426M01TEUS Issue 02

537
All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Barring restriction

Ref. ENTP0426M01TEUS Issue 02

538
Alcatel-Lucent OmniPCX Enterprise

External Call Barring

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Sub Element of the Access COS

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426A01TEUS Issue 02

539
Call Barring
Generalities

As described in the “External Call Barring” mechanism uses several objects

A prefix
Trunk group seizure prefix
ARS prefix

A logical Discriminator

The Caller’s Entity

Where a correlation is realized between the given Logical discriminator and a real
discriminator

The Real Discriminator

To define the external numbering plan

The User’s Access COS (Public Network COS)

That allow or forbid the access to a given area (with numbers)

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426A01TEUS Issue 02

540
Call Barring
Access COS – Sub Class Of Service

In fact several kinds of Call Barring can be realized with a unique Access COS

The Access COS is made of some sub-objects(1) corresponding to different kind

of Call barring. The use of a kind of sub-Access COS depends on the prefix used
to initiate the call

The following sub-Access COS are used to authorize or forbid the Access to
barring Area (same mechanism as explained in the Call Barring Overview)

Public Access COS

Use of a “Professional” prefix type
Professional trunk seize / ARS Prof. Trg Grp Seizure

Private Access COS

Use of a “Personal” prefix type
Personal trunk group seize / ARS Personal trunk group

Business Access COS

Use of a “Business account Code”(2)

All Rights Reserved © 2008, Alcatel-Lucent 3

1) Example of Access COS presentation:

2) To make a call with business account code, the user must dial:
Before making the call:
- The business account prefix
- The business account code
- The call number (direct seizure or speed dialing number)

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426A01TEUS Issue 02

541
Call Barring
Access COS – Sub Class Of Service

Network Access COS

Used in case Inter-Sub-Networks call (ABC-F / Q-SIG)
A Routing prefix or a Network prefix are used to call a remote terminal of the Network
This kind of call is not a public call

Trunk group Access COS

This Access COS contains the list of all the created trunk groups
It does not require a specific prefix use
It determines if the terminal is authorized to use the Trunk group or not, whatever the type
of use

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – External Call Barring

Ref. ENTP0426A01TEUS Issue 02

542
Alcatel-Lucent OmniPCX Enterprise
External Calls Barring

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to implement & configure the a simple external Calls Baring

MANAGEMENT

1. Situation

1.1. In this Exercise, all the extensions share the same Entity number 1

1.2. Activate the Call Barring feature in the T2 trunk group. The Logical discriminator to
be used is the “0”
1.2.1. Check that this T2 trunk group is operational and has a trunk group seizure
prefix (if it is not the case manage a prefix)

1.3. In the Entity 1,verify that the correlation between the Logical discriminator “0” &
the Real discriminator “0” is done (modify the configuration if this point is not
correct)

1.4. With a Grid Edit, copy the Access COS 2 to the Access COS 3 in order to have the
same configuration starting point
1.4.1. Assign the Public Network COS 2 to the x8 Series extensions and the Public
Network COS 3 to the x9 Series extensions

Issue 01 Ref. ENTP0426H03TEUS.doc HO. 1

2. Manage your system to meet the following requirement:

Users Operator (via the) Authorized Numbering Forbidden Numbering

x8 Series T2 01RR13 03
02RR
x9 Series T2 02RR 01RR13
03

Note: RR=Room number

2.1. Manage the Real discriminator 0:

Discriminator Rules
Á ”Call numbers” with the corresponding “Area numbers” according to the above
table

2.2. Modify the access COS (2 &3) to allow & forbid the different dialed numbers
according the above table

3. Do the different tests

HO. 2 Ref. ENTP0426H03TEUS.doc Issue 01

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

545
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

546
Alcatel-Lucent OmniPCX Enterprise

ARS

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVES

To describe and configure the ARS

To describe the ARS without time table principles

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425P01TEUS Issue 02

547
ARS
Generalities

Definition

ARS = Automatic route selection

The ARS is used to select the best way (the cheapest) to place an outgoing call.
The process is automatically made by the PCX.

The PCX takes the way (route) according to the configuration:

The number dialed by the user is associated to a table of routes. These routes are
sorted from the cheapest to the more expensive one

The PCX administrator manages the ARS according to:

PCX resources [trunks , connections to operators (public or private)]

The tariffs
The periods of the day

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425P01TEUS Issue 02

548
ARS
Generalities (Cont’)

Supplementary features (not explained in this module)

The ARS has to be linked to the barring

The routes vary depending on the time and the traffic

A public carrier can apply different tariffs for some numbers, at different times of
the day
Therefore, it can be useful to use a carrier instead of an other according to the dialed
number, according to the time of the day or the week

The ARS can modify the dialed number

To reroute the call via a private carrier
To change the carrier ID

Private codes can be inserted

Useful to edit the call reports per user

All Rights Reserved © 2008, Alcatel-Lucent 3

These ARS advanced features are explained in an other subject

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425P01TEUS Issue 02

549
ARS
Principle

Users System Trunk groups Networks

Only one external

line prefix:
the prefix ”9" ISDN - Carrier 1
Which route?

ISDN- Carrier 2

Dialing:
9 0565478823
Automatic tie line

Telephone call

Called number

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425P01TEUS Issue 02

550
ARS
Principle (Cont’)

Users System Trunk groups Networks

Only one external

line prefix.
ARS
the prefix ”9" ISDN - Carrier 1

ISDN- Carrier 2

Dialing:
Route selection
9 0565478823
according to the Automatic tie line
criteria managed:
•Dialed N°(direction)
•Cost

Telephone call

Called number

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425P01TEUS Issue 02

551
ARS
Required elements

ARS prefix
The prefix numbers 0 or 9 are mainly used worldwide
Any number can be used as ARS prefix, it just depends on the country or customer
habit

How to reach an ARS table?

An ARS prefix must be dialed and followed by the expected external number
The ARS is based on the barring mechanism to authorize or forbid a dialed
number
That means that the barring must be managed before being able to access to an
ARS table

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425P01TEUS Issue 02

552
ARS
How to access an ARS table

Synopsis of the ARS table seeking

ARS Prefix
/Entity/
1 Discriminator: 0
/Discriminator Selector
Logical Á Real Discriminator
0 Á0
2
3

User: /Translator
Entity /External Numbering Scheme
Public Network COS /Numbering Discriminator
Discriminator: 0
Á Discriminator Rule
Dialed number: 014
Numbering Area: 0
4 ARS Route List (table): XX 5
Number of digits:11 digits

All Rights Reserved © 2008, Alcatel-Lucent 7

1) A user dials an ARS Prefix followed by an external number. In this ARS prefix, the PCX picks up the discriminator Id (can be
seen as a pointer)

2) In the Entity of the dialing user, the PCX finds the relation between the logical and real discriminator

3) In the Real Discriminator, the PCX finds the discrimination rules (the available dialed numbers)
- Each “dialed number” is linked to a numbering area
- An ARS table Id can be associated to this entry

4) The Public Network category of the dialing user authorizes or forbids the access to the expected dialed number

5) If the number is authorized and linked to an ARS table, the call is routed to the corresponding ARS table

Remark

“Discriminator selection”, difference between a direct trunk group selection and ARS use

- Professional Trunk Group seizure prefix (direct seizure of a trunk group)

The logical discriminator is directly taken from the selected trunk group (the global parameters)

- In case of ARS prefix:

At the prefix dialing, the PCX ignores which trunk group is going to be used (defined later in the process), the
logical discriminator is taken from the ARS prefix itself (the logical discriminator in the global parameters of the
trunk group is ignored)

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425P01TEUS Issue 02

553
ARS
ARS routing table

An ARS table is associated to a direction (dialed number) (1)

For a user, a called number matches to an unique ARS table (2)

The link between the called number and the ARS table is realized in the real
discriminator

We can define up to 10 routes per ARS table

10 different ways to route the call for the same direction (called number)
A route corresponds to a physical resource [trunk group]

The order to use the routes is given in the "time based route list“ (3)

In case of "busy" or "out of order" state, there is an overflow between the routes according
to the management order

All Rights Reserved © 2008, Alcatel-Lucent 8

(1) This association is performed in the Real discriminator (as shown in the previous page)

(2) But several numbers can be linked to a common ARS table

(3) By default the PCX uses the “Time based route list number 1”
[The “Schedule number” is set to “: -1” in the Real Discriminator also by default]

Optional
It is possible to use a different "time based route list", but in this case, the ARS schedules have to be managed
According to the date and time, a specific time based route list is specified. This provides several possibilities to set the 10
available routes in the correct order

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425P01TEUS Issue 02

554
ARS
ARS Table Content

ARS Route list

Definition of routes Á ARS Route (up to 10)

Definition of routes Á ARS Route (up to 10)
- Route 1 / Operator 1 Route creation
- Route 1 / Operator 1 (All the possible routes
- Route 2 / Operator 2
- Route 2 / Operator 2
- Route 3 / Operator 3 for one direction
- Route 3 / Operator 3
-…
-… (called number)

Order
Orderofofthe
theroutes
routesselection
selection ÁÁTime
TimeBased
BasedRoute
RouteLists
Lists(up
(uptoto8)8)

Time Based Route List 1(default one): (up to 10 routes)

Time Based Route List 1(default one): (up to 10 routes)
- First Route / Route 1
- First Route / Route 1
- -Second
SecondRoute
Route/ /Route
Route33 First possibility of
- -Third
ThirdRoute
Route/ /Route
Route22 route selections
- -……

Time
TimeBased
BasedRoute
RouteList
List2:2:(up
(uptoto10
10routes)
routes)
- -First Second possibility of
FirstRoute
Route/ /Route
Route33
- -Second
SecondRoute
Route/ /Route
Route22 route selections
- -……

Time Based Route List 3: Third possibility of

Time Based Route List 3:
- -…… route selections

All Rights Reserved © 2008, Alcatel-Lucent 9

Remark
By default the first “Time Based Route List” is used to offer an order of selection of the predefined routes

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425P01TEUS Issue 02

555
ARS
Example

All Rights Reserved © 2008, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425P01TEUS Issue 02

556
Alcatel-Lucent OmniPCX Enterprise

ARS

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To put into operation the ARS functionality

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425C02TEUS Issue 02

557
Automatic Route Selection
ARS prefix

/Translator

/Prefix plan (create)

ARS prof trk grp seizure

Or
ARS prof trk seizure with overlapping
Or
ARS personal trk seizure
Or
ARS personal trk seizure with overlapping
Discriminator Id: from 0 to 7(1)

All Rights Reserved © 2008, Alcatel-Lucent 2

(1) This discriminator Id corresponds to “logical discriminator” which can be seen as a pointer

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425C02TEUS Issue 02

558
Automatic Route Selection
Entity object

/Entities

/Discriminator Selector (Review/Modify)

Entity number: 1

Discriminator 00 :0
Discriminator 01 :0
Discriminator 02 :0
Discriminator 03 :0
Discriminator 04 :0
Discriminator 05 :0
Discriminator 06 :0
Discriminator 07 :0

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425C02TEUS Issue 02

559
Automatic Route Selection
Discriminator object

/Translator

/External numbering plan

/Numbering discriminator (Create)

Discriminator No. :0
Name : CENTRAL2000

/Discriminator Rule (Create)

Discriminator No. :0
Call number : 0201

Area Number :1
ARS route list number : 10
Schedule number : -1
Number of Digits : 10

All Rights Reserved © 2008, Alcatel-Lucent 4

Discriminator No.: enter the discriminator number (0..255),

Call Number: enter the first digits of the expected public numbers (up to 60 digits),

Area Number: enter the area identifier (1-64) corresponding to the call number,

ARS Route list Number: enter the ARS routing table number (0-3999) which will be used when a subscriber requests the ARS by
entering a prefix,

Schedule Number: enter the number of the ARS schedule (1-100). The ARS schedule determines the time based route list to use
according to the day of the week and the time bracket relating to the call.
The value -1 assigned to this parameter inhibits the time based ARS function. The routes which are in the table are then
taken according to the order defined in the first time based route list in the table without taking account of the date of
the call,

Number of Digits: enter the maximum number of digits which can be composed (0-30) or 255 including the initial digits of the
number.

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425C02TEUS Issue 02

560
Automatic Route Selection
ARS route list definition

/Translator/Automatic Route Selection/

ARS route list (Create)

ARS Route List : 10

Name : France

/ARS route list/ARS Route (Create)

ARS route list n° : 10

Route : 1 (from 1 to 10)
Name :
Trunk Group Source : Route
Trunk group : 12 (has to be the trunk group Id)
Nb of digits to be removed :
Digits to add :
Dialing command table Id :
NPD identifier : 255
Route Quality : Speech / Fax / …

All Rights Reserved © 2008, Alcatel-Lucent 5

ARS Route list: enter the route list number (max. 4 digits 0-3999),

Route: enter the route number (between 1 and 10 inclusive). The routes can be defined in any order,

Name: enter the identifier name assigned to the route,

Trunk Group Source: the trunk group to select can be the one of the route itself, or from the caller’s Entity or its IP Domain

Trunk Group: enter the trunk group number (0 to 1999). -1 corresponds to an internal route. Between 0 and 1999 corresponds
to an external route. The trunk group must exist or have been previously created, it is checked when the route
list is validated,

Nb. Digits To Be Removed:

enter the digits to be removed. This field specifies the number of digits to be removed, starting at the beginning
of the dialed number composed by the user. Between 0 and 30 inclusive (by default 0),

Digits To Add: enter the digits to add. The number contained in this field is added in front of the dialing composed by the user.
Up to 20 digits (0 - 9, A - D, * and #) can be entered.The values A-D are only valid for an internal route. By
default this field is empty,

Dialing Command Tabl. Id: between 1 and 30. 0 indicates that no table is used. A DCT is mainly used to modify the initial dialed
number

NPD identifier: this field is used to specify which NPD has to be used for the calling user CLI (255 means that the selected trunk
group NPD is used for this route)

Route Type: (Private or Public), linked to the NPD choice. This field is used to set up the “Byte 3” field in the ISDN Setup

Quality: Quality level offered by the route. The following levels are offered. Speech,Fax,Restricted digital information,
Unrestricted digital information,Low Level Signaling Route

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425C02TEUS Issue 02

561
Automatic Route Selection
ARS time-based route definition

/Translator/Automatic Route Selection/ARS route list

/Timed based route list (Create)

ARS Route list : 10

Time-based Route list Id : 1 (from 1 to 8)

[Add ]

Route Number : 1 (from 1 to 10)

Waiting Cost Limit : -1
Stopping Limit : -1

All Rights Reserved © 2008, Alcatel-Lucent 6

Route List Id.: enter the routing table number to which the time based route list belongs,

Time Based Route List Id: enter the time based route list number (1-8). Time based route list number 1 is a particular list which
will be used by default when the time based ARS functions are inhibited. (The ARS by time bracket is not used.),

Route Number:enter the number of the route to try (1-10). The route numbers must be entered in polling order,

Waiting Cost Limit: (optional, between 0 and 31) Leave this field blank to indicate that the value is the same as the previous
route in the list (value by default).

This “waiting cost limit” is checked with the user category. In case of busy routes, if the user has the right (higher value than the
route ones), the ARS process is then reset and, following the waiting period, re-triggers a new run-through (search) sequence
from the first route indicated by the time-based route list. During the second search, only stopping cost thresholds are active in
order to limit the number of unsuccessful searches

Stopping Cost Limit (optional, between 0 and 31). Leave this field blank to indicate that the value is the same as the previous
route in the list (value by default). The upper limit is fixed at 30 so as to prevent filtering all calls.

This field allows to restrict the access to this route to some users which have a Stopping cost value (in their Public access
category) lower than the route one. In the other hand, the calls of users whose cost threshold is 31 will always try to take this
route. The parameter can only be activated on condition that the routing restriction option is valid (system parameter in
Installation)

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425C02TEUS Issue 02

562
Automatic Route Selection
ARS user’s objects

/Users (Review/Modify)

Directory number :
Entity nb : 1 (by default)
Public Network COS : 2 (by default)

/Classes of service/ Access COS (Review/Modify)

Public Network COS :2

ARS privilege

Night :0
Day :0
Mode 1 :0
Mode 2 :0

All Rights Reserved © 2008, Alcatel-Lucent 7

ARS privilege: (0 – 31) This value defines the maximum cost of a route that the user can use for his call. Value 31 corresponds to
the highest privilege and value 0 to the lowest.

Repeat the operation for the following categories:

• Day

• Night

• Mode 1

• Mode 2

You can assign a cost threshold to each route defined for a specific public network number. In order for the user to be able to
use the route, his ARS privilege must be strictly higher than the route cost threshold

The category defines only one “privilege” fields, whereas the ARS table offers two different ones (Waiting / Stopping costs)
In fact the user’s category privilege is use for both Waiting / Stopping possibilities

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425C02TEUS Issue 02

563
Automatic Route Selection
System ARS objects

/System (Review/Modify)

ARS parameters

Route restriction : NO (default value)

Tone on seizure : YES (default value)

All Rights Reserved © 2008, Alcatel-Lucent 8

Route Restriction:
- Yes: allows to reject the routing of a call directly from the first root (even if the barring feature allows the dialed number)
- No: the control of the cost threshold is not done for the first route, but only for the following ones (at least, that allows to
route a call on the first route of an ARS table)

(If the cost threshold of the user is lower than the cost of the route, the call is rejected)

Tone on seizure: authorizes simulation of the public network dialing ring (440Hz) tone after an ARS prefix has been dialed. This
is used to make ARS use identical to public trunk group seizure.

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425C02TEUS Issue 02

564
Alcatel-Lucent OmniPCX Enterprise

ARS

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To check the ARS configuration

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425M01TEUS Issue 02

565
ARS
Maintenance

The “lookars” command allows to check the ARS configuration

Available under “mtcl” account

Usage: “lookars <option>”

lookars –h
Displays the different “lookars” tool options
lookars r <route-list-nb>
Gives all the defined routes of the given table
lookars r all
Display all ARS tables of the PCX
lookars i : interactive mode
For a given user and a given external number, it allows to check the route selection
(all the involved elements are displayed: user’s entity, COS, ARS table…

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425M01TEUS Issue 02

566
ARS
lookars r <route-list-nb>

lookars r 10

Tue Jul 3 09:18:04 CEST 2007

All Rights Reserved © 2008, Alcatel-Lucent 3

End of the display of this ARS route list:

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425M01TEUS Issue 02

567
ARS
lookars i

lookars i
Tue Jul 3 09:37:01 CEST 2007
Time and Date seizure : any wrong value entered leads to use internal time
Call establishment time ==> hour (range 0 .. 23) : <return>
Internal system time used :
Date : 03/07/2007
Time : 09:37
ARS Prefix : 0
Directory No : 31000
External No : 0298143322
Command : <return>
====================================================================
| P U B L I C E X C H A N G E T R A N S L A T O R |
====================================================================
|
| Prefix number : 0 Discri Log Id : 0
| Dir. number : 31000 Entity : 1 Discri Real Id : 2 User related information
| Route List No : 10 Scheduler No : -1
| Default sub routes list -> 1 ARS Table information
|
| S U B R O U T E S L I S T E No 1 |
--------------------------------------------------------------------
|
| First route to try is route nb 1 stop = -1 wait = -1
| Second route to try is route nb 2 stop = -1 wait = -1 Selected routes
====================================================================

All Rights Reserved © 2008, Alcatel-Lucent 4

Remark

In order to know which trunk group(s) is(are) selected, you have to use “lookars –r <route-list-nb> to get the trunk group Id(s)

It is also possible to replace some digits by a “x”, in order to check the behavior for range of given numbers:

ARS Prefix : 0
Directory No : 31000
External No : 0298xxxxxx

Command :

====================================================================
| P U B L I C E X C H A N G E T R A N S L A T O R |
====================================================================
|

| Prefix number : 0 Discri Log Id : 0

| Dir. number : 31000 Entity : 1 Discri Real Id : 2
| Route List No : 10 Scheduler No : -1
| Default sub routes list -> 1
|
| S U B R O U T E S L I S T E No 1 |
--------------------------------------------------------------------
|
| First route to try is route nb 1 stop = -1 wait = -1
| Second route to try is route nb 2 stop = -1 wait = -1

====================================================================

Alcatel-Lucent OmniPCX Enterprise – ARS

Ref. ENTP0425M01TEUS Issue 02

568
Alcatel-Lucent OmniPCX Enterprise
ARS

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage ARS (basic configuration)

MANAGEMENT

1. Manage ARS as follows:

9 Series extension
Access category: 2
Entity: 1

Trunk group x0
AT&T

British
Trunk group x2 Telecom

Analog extension
Access category: 3
Entity: X1

Issue 02 Ref. ENTP0425H01TEUS.doc HO. 1

SIMPLE ARS

2. Manage the ARS prefix “0” (Or 9 according to the country habit)

3. Realize the management of the Alcatel-Lucent OmniPCX Enterprise to satisfy the following
requirements:
- Whatever the dialed number, the analog sets must use the T0 then the T2 in case of
external calls
- Whatever the dialed number, the digital sets must use the T2 then the T0 in case of
external calls

3.1. Manage in each “real discriminator” one ARS rout list number (for example 0 and 1)

3.2. Create the 2 ARS rout lists (tables) containing each both trunk groups
Manage the “time based route list in order to provide the right route selection
according to the above requirement

4. Check your configuration with the “lookars” command (use the different options)

5. Make the tests by using the “trkstat” command to display the used trunk group

HO. 2 Ref. ENTP0425H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

571
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

572
Alcatel-Lucent OmniPCX Enterprise

Automatic Callback on Busy Trunk

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the feature “Automatic Callback on Busy Trunk”

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481P01TEUS Issue 02

573
Automatic Callback on Busy Trunk
Generality

Definition

The “Automatic Callback on Busy Trunk “ feature allows a user, while placing
an outgoing call on a busy trunk group to request an automatic callback

Feature availability
Direct trunk group seizure on ISDN (T0/T1/T2)
ARS(1) trunk group seizure

This feature is only available for a public carrier compatible with the
overlapping dialing

All Rights Reserved © 2008, Alcatel-Lucent 2

(1) Function with ARS:

In case of overloading of all available routes, the automatic call back is implemented only on the first route selected by the
ARS (the less expensive route). This automatic callback on busy trunk is run with as a direct callback on the memorized trunk
group (with any ARS use)

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481P01TEUS Issue 02

574
Automatic Callback on Busy Trunk
Functioning mode

The automatic Callback on Busy trunk is made of two main steps

The callback registration

The execution

Topology example

Faisceau

Public carrier

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481P01TEUS Issue 02

575
Automatic Callback on Busy Trunk
Callback record

At the time of an outgoing call through a trunk group(1), if all the trunks are
busy, the callback demand is offered to the user if he has the right(2)

The user is notified of this possibility with the voice guide 8(3) and with a
dynamic key

If the user uses the associated suffix (or the dynamic key) the “Automatic
Callback on Busy Trunk Group” will be recorded

The voice guide 3(4) notifies the user that the callback is registered

All Rights Reserved © 2008, Alcatel-Lucent 4

(1) Possible cases:

- Direct local trunk group seizure
- ARS trunk group seizure, with local trunk groups

(2) To be able to use the “Automatic Callback” feature, the user needs:
- a “phone features Class of Services”, allowing the use of “Callback on no answer/busy” (suffix)
- to seize a trunk group, with which the “Automatic Callback” is allowed (new management field)

(3) Voice guide n°8: “You may request automatic call back by dialling …”

(4) Voice guide n°3: “Your request has been recorded, you may now hang up”

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481P01TEUS Issue 02

576
Automatic Callback on Busy Trunk
“Automatic Callback” execution

As soon as a trunk becomes free, if the user (the one who initiated the
callback) is free, a “Setup” message is sent(1) (through the trunk group
associated to the callback)

The set is rung (during a timer based the number of dialed digits
and the timer 3)(2)

If the user does not off-hook before the end of this timer, the Automatic
Callback is cancelled (and the trunk is released)

In cases of off-hook before the end of this timer, the remaining digits (of the
predefined callback number) are sent to the public operator

All Rights Reserved © 2008, Alcatel-Lucent 5

(1) The emission method of the “Setup” message is the over-dialing method. Only the beginning of the “called number” (2
digits) is sent to the public operator. This allows to reserve a trunk, in the meantime the user (which initiate the callback)
can off hook to valid this callback

(2) Refer to the Maintenance subject for the calculation details

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481P01TEUS Issue 02

577
Automatic Callback on Busy Trunk
Restrictions

This feature is not available in network configuration

ARS
Only the first route of the ARS table can be selected to callback (local route)
No callback in case of ARS Server

This feature is available for all sets, except:

S0 Type, analog with 4980, PC MM1, PCMM2, “Remote Extension”
External sets
Attendant sets

Impossible in case of private call (PIN code), and when a routing prefix is used

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481P01TEUS Issue 02

578
Automatic Callback on Busy Trunk
Miscellaneous

If several callback demands are associated to the same trunk group, they are
treated in the order of registration

When a coupler(1) resets, all the associated callbacks requests are lost

In case of CPU switch-over, the callback requests are lost(2)

Limits

The maximum number of callback for a set: 8

The maximum number of “Automatic Callback on Busy trunk group” equals
200 per system

All Rights Reserved © 2008, Alcatel-Lucent 7

(1) All types of boards allowing to use digital accesses (T2/T1/T0)

(2) The corresponding Callback memory areas are not saved. (the call references are lost. A call back corresponds to a call
reference)

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481P01TEUS Issue 02

579
All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481P01TEUS Issue 02

580
Alcatel-Lucent OmniPCX Enterprise

Automatic Callback on Busy Trunk

All Rights Reserved © 2005, Alcatel-Lucent 1

OBJECTIVE

To configure the system to provide the “Automatic Callback on Busy Trunk”

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481C01TEUS Issue 04

581
Automatic Callback on Busy Trunk

/Classes of Service/ Phone Features COS (Classes of Service)

Review/Modify
Callback on free or busy set: 1 (default value)
Auto. Call back On busy Trk grp: 0 or 1(1)

/Trunk groups

Review/Modify
Overlap dialing + YES (default value)

All Rights Reserved © 2005, Alcatel-Lucent 2

Remark
In case of a trunk is released after the end of the callback request (hang on of the handset at the end of the facility use); the
connection category of the trunk has to be compatible with itself (in this case, a free trunk will request to execute a callback
on itself)!
This restriction is released from the version f1.602.3m

(1) Auto. Call back on Busy Trk grp: 1 The Automatic Callback on Busy Trunk is proposed by the phone
Auto. Call back on Busy Trk grp: 0 The Automatic Callback on Busy Trunk is not proposed by the phone

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481C01TEUS Issue 04

582
Automatic Callback on Busy Trunk

Management of the suffix used by the system for the Automatic Callback

It’s necessary to create the suffix associated to the default VG used by the
Automatic Callback (1)

/Translator/Suffix plan
Create
Number: 5 (according the VG)
Suffix meaning: Callback on free or busy set

All Rights Reserved © 2005, Alcatel-Lucent 3

1 – VG used for the Automatic Callback is: “You may request automatic callback by dialing 5 ….. ” (for instance)

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481C01TEUS Issue 04

583
All Rights Reserved © 2005, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481C01TEUS Issue 04

584
Alcatel-Lucent OmniPCX Enterprise

Automatic Callback on Busy Trunk

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To maintain the “Automatic Callback on Busy Trunk” feature

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481M01TEUS Issue 02

585
Automatic callback on busy trunk

Automatic callback example

tabrasfo 1 10

nbrasfo_min 1 nbrasfo_max 10
idx_rasfolib = 2
| nulog | fais | teqt | jeqt | demande | demandeur | chain |
------+-------+------+------+------+----------------+----------------+-------|
[ 1] | 1 | 10 | 258 | -1 | #100046032101 | 32201 | 0 |
[ 2] | 0 | -1 | 0 | 0 | | | 3 |
[ 3] | 0 | -1 | 0 | 0 | | | 4 |
[ 4] | 0 | -1 | 0 | 0 | | | 5 |
[ 5] | 0 | -1 | 0 | 0 | | | 6 |
[ 6] | 0 | -1 | 0 | 0 | | | 7 |
[ 7] | 0 | -1 | 0 | 0 | | | 8 |
[ 8] | 0 | -1 | 0 | 0 | | | 9 |
[ 9] | 0 | -1 | 0 | 0 | | | 10 |
[ 10] | 0 | -1 | 0 | 0 | | | 11 |

All Rights Reserved © 2008, Alcatel-Lucent 2

Usage: tabrasfo [min(1-200) max(1-200)]

Meaning:
- fais = Trunk group ID
- demande = called number registered for the automatic callback
- demandeur = directory number corresponding to the calling set

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481M01TEUS Issue 02

586
Automatic callback on busy trunk

Automatic callback example

set:32201, trunk group: 10

callbstat d 32201

idx_rappel 1 for set 32201

---------------------------------------------------
zone: etat: nulog/numan/neqt Key: typ_rap
Adress of the area 1: 0x12717c94
1 BUSY 10 -1 RASFO
2 FREE
3 FREE
4 FREE
5 FREE
6 FREE
7 FREE
8 FREE
Message Led 0 Message is present 1
---------------------------------------------------
Note: neqt/nulog/nugroup/numan depends on the typ_rap data
:Be Careful neqt is used for CCBS_

All Rights Reserved © 2008, Alcatel-Lucent 3

Other available options of the « callbstat » command

n neqt
z idx1 idx2 (idx = callback area index)
all

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481M01TEUS Issue 02

587
Automatic callback on busy trunk

n° 3 (TempNum)
Used in case of Automatic Callback on Busy trunk, to determine the duration
of the ringing time of the set which initiate the callback(1)
The two first digits of the dialed number being sent to reserve the trunk, the
ringing time is equal to:
(Number of digits of the dialed number to be called back– 2) x TempNum

n° 150 (TEMPO_CB_ORIG)(2)
Used to limit the life time of the callback in memory

All Rights Reserved © 2008, Alcatel-Lucent 4

(1) If there is no off-hook of the extension with which the callback has been initiated before the end of the calculated timer, the
Automatic Callback is released

(2) This timer is common to the use of the automatic callback on busy subscriber/trunk

Remark:
The timers n° 328 (TEMP_RASFO_FACILITE) and n° 329 (TEMP_RASFO_END_SERVICE) are used only for software checking/debug

Alcatel-Lucent OmniPCX Enterprise – Automatic Callback on Busy Trunk

Ref. ENTP0481M01TEUS Issue 02

588
Alcatel-Lucent OmniPCX Enterprise
Automatic call back on busy trunk group

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to set up the automatic call back on busy trunk group and test the automatic
call back on busy trunk group

MANAGEMENT

1. Set up the automatic call back on busy trunk group on the PCX (modify the COS and trunk
as explained in the training)

2. Test the automatic call back on busy trunk group

2.1. Verify the presence of the voice prompt N°8

2.2. Put some trunks out of service with the command “outserv”

2.3. Occupy the trunks by placing outgoing calls

2.4. Once the trunk group is busy call from an additional phone and tests the automatic
call back.

Issue 02 Ref. ENTP0481H01TEUS.doc HO. 1

HO. 2 Ref. ENTP0481H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

591
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

592
Alcatel-Lucent OmniPCX Enterprise

Classes of Services

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Connection and Transfer Class Of Service

Alcatel-Lucent OmniPCX Enterprise – Classes of Services

Ref. ENTP0404P06TEUS Issue 02

593
Classes Of Service
Generalities

3 types of Classes Of Service

OmniPCX Enterprise

Connection

Direct Call
not allowed

OmniPCX Enterprise

Transfer

Transfer
not allowed

Immediate forward
programming
Phone facilities
OmniPCX Enterprise

All Rights Reserved © 2008, Alcatel-Lucent 2

The Phone facilities COS is detailed in a dedicated subject

The Access COS is explained in the External Call Barring subject

Alcatel-Lucent OmniPCX Enterprise – Classes of Services

Ref. ENTP0404P06TEUS Issue 02

594
Classes Of Service
Connection COS

This type of category is used to allow/forbid the Alcatel-Lucent OmniPCX

Enterprise devices to connect together

Extension £ extension (Internal call)

Some extensions from different department are not allowed communicate together
directly

Extension £ Trunk (external incoming/outgoing call)

Some extensions are not authorized to use some Trunk Group, regardless the Call
Barring feature

Trunk £ Trunk (Trunk to Trunk connection)

For example an external incoming call (Trunk) is allowed to be connected to an

other Trunk (for cost reasons for example)

All Rights Reserved © 2008, Alcatel-Lucent 3

Remark:
In fact, two types of Connection COS exist:

-Connection COS (here above described)

-Private Calls connection COS. This second COS can be used for the Virtual Users to set up calls from a physical extension.

“Virtual user” example: a unique extension is shared between several users.

Each person of the office has a Virtual extension (no equipment). To set up a call, those users have to use a private “trunk group
or ARS” seizure prefix + their own Personal Identification Number (unique in the installation and allows to identify which “user”
tries to set up a call
The Private Call Connection COS can therefore be used to restrict the use of the local office “physical” extension to set up calls
(the Virtual extension Connection COS is compared to the physical extension one)

Alcatel-Lucent OmniPCX Enterprise – Classes of Services

Ref. ENTP0404P06TEUS Issue 02

595
Classes Of Service
Connection COS example

The configuration of the Connection COS corresponds a matrix set up

Unauthorized Call

COS Id = 1 COS Id = 2
Called party
0 1 2 3 4 5
0 1 1 1 1 1 1
1 1 1 0 1 1 1
Caller 2 1 1 1 1 1 1
3 1 1 1 1 1 1
4 1 1 1 1 1 1
5 1 1 1 1 1 1

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Classes of Services

Ref. ENTP0404P06TEUS Issue 02

596
Classes Of Service
Transfer COS

This COS allows / forbids the call transfer between two devices

An enquiry call to be set up to be able to use the transfer feature

A communication is established between two devices. One of those parties sets up

an enquiry call, then tries to put through both parties

Extension £ Extension (Internal transfer)

Extension £ Trunk (transfer of a outside call to a phone)

Trunk £ Trunk (transfer of a outside call to another external party)

The transfer category Id is the same as the Connection COS Id, but on a
configuration point of view, two matrixes are manageable

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Classes of Services

Ref. ENTP0404P06TEUS Issue 02

597
Classes Of Service
Transfer COS example

The configuration of the Transfer COS corresponds to a matrix set up

Unauthorized Call
Transfer

COS Id = 1 COS Id = 2
Called party
First established Second established
0 1 2 3 4 5
communication communication
0 1 1 1 1 1 1
1 1 1 0 1 1 1
2 1 1 1 1 1 1
Caller
3 1 1 1 1 1 1
4 1 1 1 1 1 1
5 1 1 1 1 1 1

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Classes of Services

Ref. ENTP0404P06TEUS Issue 02

598
Alcatel-Lucent OmniPCX Enterprise
Classes of service

PROCEDURE

OBJECTIVE

- To learn how to manage classes of service

OVERVIEW
For each user, many classes of service are declared: Access COS, Connection COS, Transfer COS,
Private Calls Connection COS and Phone Features Classes of Service.
These classes of service allow for authorization or prohibition of calls from certain sets to other
particular sets or to other classes of service.

Issue 02 Ref. ENTP0404C02TEUS.doc P. 1

PROCEDURE

1. Access class of service

On mgr
Select Classes of service
Access COS
Action Review/Modify
Select All instances
Action Press ENTER
Press on CTRL+V to validate
Select 2 (e.g.)
Action Press ENTER

1.1. Public Access COS

On mgr
Select Classes of service
Access COS
Action Descend hierarchy
Select Public Access COS
All instances
Action Press CTRL+V
Remark:
By default the public access COS 2 is selected, you can change this value.
Action Select one of the 64 areas
Select 2 (e.g)
Action Press ENTER
Entry Public Access Rights
Night: 1 or 0
Day: 1 or 0
Mode1: 1 or 0
Mode2: 1 or 0
Action Press CTRL+V
Press CTRL+C as many times as needed to come back on main menu

P. 2 Ref. ENTP0404C02TEUS.doc Issue 02

1.2. Private Access COS

On mgr
Select Classes of service
Access COS
Descend hierarchy
Action Press ENTER
Select Private Access COS
All instances
Action Press CTRL+V
Remark:
By default the private access COS 2 is selected, you can change this value.
Action Select one of the 64 areas
Select 2 (e.g)
Action Press ENTER
Entry Private Access Rights
Night: 1 or 0
Day: 1 or 0
Mode1: 1 or 0
Mode2: 1 or 0
Action Press CTRL+V
Press CTRL+C as many times as needed to come back on main menu

Issue 02 Ref. ENTP0404C02TEUS.doc P. 3

1.3. Business Access COS

On mgr
Select Classes of service
Access COS
Descend hierarchy
Action Press ENTER
Select Business Access COS
All instances
Action Press CTRL+V
Remark:
By default the business access COS 2 is selected, you can change this value.
Action Select one of the 64 areas
Action Press ENTER
Select 2 (e.g)
Entry Business Access Rights
Night: 1 or 0
Day: 1 or 0
Mode1: 1 or 0
Mode2: 1 or 0
Action Press CTRL+V
Press CTRL+C as many times as needed to come back on main menu

P. 4 Ref. ENTP0404C02TEUS.doc Issue 02

Issue 02 Ref. ENTP0404C02TEUS.doc P. 5

1.5. Trunk Group Access COS

On mgr
Select Classes of service
Access COS
Descend hierarchy
Action Press ENTER
Select Trunk Group Access COS
All instances
Action Press CTRL+V
Remark:
By default the trunk group access COS 2 is selected, you can change this
value.
Action Select one of your trunk groups ID
Select 10 (e.g)
Action Press ENTER
Entry Trunk Group Access Rights
Night: 1 or 0
Day: 1 or 0
Mode1: 1 or 0
Mode2: 1 or 0
Action Press CTRL+V
Press CTRL+C as many times as needed to come back on main menu

P. 6 Ref. ENTP0404C02TEUS.doc Issue 02

2. Connection class of service

On mgr
Select Classes of service
Connection COS
All instances
Action Press CTRL+V
Action Select one of the 32 categories
Select 1 (e.g)
Action Press ENTER
Entry Connection rights
COS 0: 0 or 1
COS 1: 0 or 1
…
COS 31: 0 or 1
Action Press CTRL+V
Press CTRL+C as many times as needed to come back to the main menu

3. Transfer class of service

On mgr
Select Classes of service
Transfer COS
All instances
Action Press CTRL+V
Action Select one of the 32 categories
Select 1 (e.g)
Action Press ENTER
Entry Transfer rights
COS 0: 0 or 1
COS 1: 0 or 1
…
COS 31: 0 or 1
Action Press CTRL+V
Press CTRL+C as many times as needed to come back to the main menu

Issue 02 Ref. ENTP0404C02TEUS.doc P. 7

4. Private Calls Connection class of service

On mgr
Select Classes of service
Private calls connection COS
All instances
Action Press CTRL+V
Action Select one of the 32 categories
Select 1 (e.g)
Action Press ENTER
Entry Connection rights
COS 0: 0 or 1
COS 1: 0 or 1
…
COS 31: 0 or 1
Action Press CTRL+V
Press CTRL+C as many times as needed to come back to the main menu

P. 8 Ref. ENTP0404C02TEUS.doc Issue 02

5. Phone features Classes of service

On mgr
Select Classes of service
Phone features class of service
All instances
Action Press CTRL+V
Action Select one of the 32 categories
Select 1 (e.g.)
Action Press ENTER
Entry Phone features class of service
Rights
Prot. against dir.call pickup: 0 or 1
Set features
Immediate forward: 0 or 1
General Services
Group call pickup: 0 or 1
PCX Services
Speed call to associated set: 0 or 1
External Services
Direct trunk seizure: 0 or 1
Suffixes
Broker call: 0 or 1
Speed Dialing Area :
Area 0 : 0 or 1
…
Area 31: 0 or 1
Action Press CTRL+V
Press CTRL+C as many times as needed to come back to the main menu

Issue 02 Ref. ENTP0404C02TEUS.doc P. 9

P. 10 Ref. ENTP0404C02TEUS.doc Issue 02

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage classes of service

MANAGEMENT

1. Assign User Connection COS

1.1. Assign connection COS 1 to the extension 3n000 (where n=System Index)

1.2. Assign connection COS 2 to the UA sets (3n001 & 3n002)

2. Connection COS

2.1. Modify the Connection COS in order to make the COS 2 incompatible with the COS 1

2.2. Modify the Connection COS in order to make the COS 1 compatible with the COS 2

3. Tests

3.1. Set up a call from user 3n000 to user 3n001. What happens and why?
.......................................................................................................

3.2. Set up a call from user 3n001 to user 3n002 and 3n000. What happens and why?
.......................................................................................................

Issue 02 Ref. ENTP0404H02TEUS.doc HO. 1

HO. 2 Ref. ENTP0404H02TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

611
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

612
Alcatel-Lucent OmniPCX Enterprise

Multi-line and Supervision Keys

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe multi-line and supervision functions

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

613
Multi-line Keys
Overview

For some facilities, the stations need more than one line

By default all sets are mono-line

The number of lines depends of the number of free keys available on the set
One key = one line

In this case 3 lines are created

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

614
Multi-line Keys
Overview

For 4068, 4038, 4039, 4028 and 4029 extension type(1) is recommended to use
external add-on module(s) to create the multi-line keys

If you are in conversation by using one of this type of station, if you receive a
second call (on another multi-line key) you may not see this call on the display
screen, only a beep is heard.
To see the call you have to press the “Back” key

In case of using an add-on module, no problem, because you see the calls
arriving on a key of this module

All Rights Reserved © 2008, Alcatel-Lucent 3

(1) – In fact, stations with big display screen

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

615
Multi-line Keys
Mono-directory number

One number on several keys

Receiving calls

Receiving on one key

Second call on the second key with the first call on hold and so on
Several calls at a time

Caller display

Display updated for each new event

Calls on each key displayed

Flexibility

The extension is considered free so long as one line is free

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

616
Multi-line Keys
Multi-directory number

Several numbers on the same station (Multi-MCDU)(1)

Receiving calls(2)

Directory number(s) for internal calls

Directory number(s) for business calls
Directory number(s) for private calls
Etc …

Displaying the call

Display updated for each new event

Calls on each key displayed Internal Business DID
(31100) (31600)

All Rights Reserved © 2008, Alcatel-Lucent 5

(1) - No limit of directory numbers, except the number of keys

(2) - Internal or external calls

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

617
Multi-line Keys
Options

Automatic Incoming Seizure

If false, not automatic: you have to select a multi-line key (by pressing it)
and dial the number
If true, automatic: the system selects for you the first free key (default
functioning)

Automatic Outgoing Seizure

If false, not automatic: the line can only be seized by pressing a free key.
If true, automatic: when going off-hook, the first line which rings is seized
without the user needing to press the key concerned (default functioning)

Selective Filtering
Used in case of manager/secretary group configuration (see associated
chapters)

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

618
Supervision Keys
Overview

Only available on multi-line extensions

A supervision is used to know the status of an equipment (free, busy, in

conversation, out of service), also used to reach this equipment (in case of
station) or to size a trunk or trunk group (in case of trunk/trunk group
supervision) and also to intercept calls

Type of supervised equipments

Stations
Fax
Voice Mailboxes
Trunks
Trunk groups

All Rights Reserved © 2008, Alcatel-Lucent 7

It is possible to supervise the state of the extensions (digital, analog or Multiline) and the multiple directory numbers assigned to
Multiline extensions
An attendant or a hunting group can’t be supervised.

Remark: there is also the possibility to supervise an analog trunk or an analog trunk group. Then you have the possibility to seize
directly a trunk, intercept a call or just know if the trunk is busy, free or ringing.

LIMITS:

A set can be supervised by 20 sets maximum.

The total number of supervision keys in the system is 15000.

Only one key with the same directory number can be created on a set.

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

619
Supervision Keys
Set supervision

Notification of status
Partially busy
At least one line is free
Totally busy
All lines are busy
Free
Rung
Out of service (seen only if set receive a call!!!)

Call interception on ringing by pressing the supervision key directly

Direct call to the supervised station by pressing the supervision key directly

All Rights Reserved © 2008, Alcatel-Lucent 8

With the supervision key you can:

- intercept calls made to the supervised extension (during phase only)
- call the supervised directory number directly whether it is free or busy (if busy with a call waiting, automatic callback offered).

LIMITS:

A set can be supervised by 20 sets maximum.

300 sets can be supervised simultaneously.

The total number of supervision keys in the system is 1500.

Only one key with the same directory number can be created on a set.

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

620
Supervision Keys
Set’s display

The same number on several extensions (e.g.: workgroup)

One number can be supervised by several extensions

An incoming call is indicated on all extensions simultaneously

Choice of ring:

No ring
Short ring
Long ring
Short ring without Overring
Long ring without Overring

All Rights Reserved © 2008, Alcatel-Lucent 9

An extension can be supervised by not more than 20 extensions.

Ringing option:
no ring: switches off the bell on the "supervisor" extension, and the icon blinks
Long ring: the "supervisor" extension rings (normal ring) at the same time as the LED or icon blinks if idle.
The extension use hears an additional Overring (one beep) if:
he/she is in conversation,
he/she is not protected against this feature,
he/she is not in conference or multi conference,
he/she is not in a third part structure
Short ring: the "supervisor" extension rings (short ring) at the same time as the LED or icon blinks if idle. The extension user
hears an Overring signal if he/she is in the same situation as for the ringing option (the beep is controlled by the system
management function).

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

621
Supervision Keys
Voice mailbox supervision (of another user)

The owner of a mailbox can be supervised by one or several other users

Supervisors are notified when new messages are received in the supervised
mailbox

They will be able to consult messages left and responses, depending on the
state of the supervised mailbox

He must, however, know the secret code for the supervised mailbox and, after
dialing this code, only has access to messages in the mailbox of this set.

All Rights Reserved © 2008, Alcatel-Lucent 10

This feature is compatible with the following mailboxes:4635, 4645

Voice mailbox supervision is also available on a homogenous network or an ABC-F2 link.

A given user can supervise as many mailboxes as allowed by the number of dedicated programmable keys on his set.

This feature can be used when several users are physically sharing the same set and when each user wishes to have his own
personal voice mailbox (any given set can only have one voice mailbox). For each user, a virtual set is created, with an exclusive
voice mailbox. This virtual set is in immediate forwarding mode to a number corresponding to a multiline key of the physical set.
A programmable key on this same physical set allows supervision (and therefore gives access to) the voice mailbox of the user in
question.

Restrictions

The maximum number of supervisors for a same voice mailbox is 100 (20 in a network configuration).

The supervisors must be declared as "multiline".

This feature is not available:

• with hotel/hospital,

• with ACD, CCd,

• for a user who is replacing the supervisor set,

• if the "owner" set of the supervised voice mailbox is out of service.

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

622
Supervision Keys
Trunk group/Trunk supervision

Trunk group supervision

Supervising a trunk group means indicating its status (free or busy) using a
LED or icon on the supervisor set

The trunk group supervision key is used to seize only a free BCA trunk in this
trunk group for outgoing call

Trunk supervision

Supervising a trunk consists of indicating its status (free, busy, on hold,

ringing) using an LED or icon on the supervisor set

The trunk supervision key is used to:

Pick-up a call arriving on the trunk
Retrieve hold on this trunk
O/g seize on the trunk if it is free

All Rights Reserved © 2008, Alcatel-Lucent 11

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

623
Supervision Keys
Trunk group/Trunk supervision

Limits

A set can supervise a maximum of 20 trunks and/or trunk groups

The sum of the trunk groups and trunks supervised cannot exceed 150

All Rights Reserved © 2008, Alcatel-Lucent 12

Alcatel-Lucent OmniPCX Enterprise – Multi-line and Supervision Keys

Ref. ENTP0406P02TEUS Issue 02

624
Alcatel-Lucent OmniPCX Enterprise
Multi-line & Supervision Keys

PROCEDURE

OBJECTIVE

- To learn how to create Multi-line and supervision keys

OVERVIEW
This procedure shows you how to create multi-line and supervision keys.
The multi-line keys are used on a set for some specific features used on this set, such as
manager/secretary group.
The Supervision keys are used to supervise some internal equipment, a station for example.

Issue 02 Ref. ENTP0406C02TEUS.doc P. 1

PROCEDURE

1. Multi-line keys creation

1.1. Mono-directory number

Application Configuration Tab PCX

Path / Users
Object “31100” (User directory number)
Path / Progr.Keys
Parameters Key No. 1
Function: Multi-line
Directory number: 31100 (same number as the user)
Mnemo (Pocket,Mobile,4040,8&9): Line 1
Action
Click on “ ” to validate

Note: You can create several multi-line keys according to the needs

Note: You can use the Contextual Menu for using the graphical view of the set (easier for
programmable keys management)

Note: In this example, you have to follow the next steps

1) Select a user (31100 for instance)
2) Right click on the mouse and select “Graphical View…”

P. 2 Ref. ENTP0406C02TEUS.doc Issue 02

1.2. Multi-directory number

Note: A multi-line key with the main directory number has to be created before the
management of the multi-mcdu

Application Configuration Tab PCX

Path / Users
Object “31100” (User directory number)
Path / Progr.Keys
Parameters Key No. 3
Function: Multi-line
Directory number: 31600 (a free number)
Mnemo (Pocket,Mobile,4040,8&9): Sec-line 1
Action
Click on “ ” to validate

Note: You can create several multi-MCDU keys according to the needs
Like previously, you can use the graphical view

1.3. Optional parameters

Application Configuration Tab PCX

Path / Users
Object “31100” (User directory number)
Tab Facilities
Parameters Automatic Incoming Seizure: True/False
Parameters Automatic Outgoing Seizure: True/False
Action
Click on “ ” to validate

Note: For Automatic Incoming Seizure:

If false, not automatic: you have to select a multi-line key (by pressing it) and dial
the number
If true, automatic: the system selects for you the first free key (default
functioning)

Note: For Automatic Outgoing Seizure:

If false, not automatic: the line can only be seized by pressing a free key.
If true, automatic: when going off-hook, the first line which rings is seized without
the user needing to press the key concerned (default functioning)

Issue 02 Ref. ENTP0406C02TEUS.doc P. 3

2. Supervision keys creation

2.1. Set supervision

Application Configuration Tab PCX

Path / Users
Object “31100” (User directory number, a multi-line set)
Path / Progr.Keys
Parameters Key No. 8
Function: Set Supervision
Directory number: 31000
Ringing Mode: Short Ring
Mnemo (Pocket,Mobile,4040,8&9): Sup 31000
Action
Click on “ ” to validate

Note: The set has to be a multi-line one.

Like previously, you can use the graphical view.
Ringing mode
No ring: no ring on the supervisor set, only a visualization on the key
Short ring: a short ring or beep if the set is in conversation (for instance)
Long ring: a long ring or beep if the set is in conversation (for instance)
Short ring without Overring: a short ring but no beep
Long ring without Overring: a long ring but no beep

2.2. Voice Mailbox supervision

Application Configuration Tab PCX

Path / Users
Object “31100” (User directory number, a multi-line set)
Path / Progr.Keys
Parameters Key No. 9
Function: Voice Mail Supervision
Directory number: 31000
Mnemo (Pocket,Mobile,4040,8&9): MB 31000
Action
Click on “ ” to validate

Note: The set has to be a multi-line one.

A voice mailbox number can be associated only on one supervision key for a set
Like previously, you can use the graphical view.

P. 4 Ref. ENTP0406C02TEUS.doc Issue 02

PROCEDURE

OBJECTIVE

- To learn how to manage set supervision

OVERVIEW
Supervising a directory number of an internal set consists in indicating its status (free, busy or
ringing) using a LED or an icon on the supervisor set (The supervisor set is multi-line).
Warning: an attendant or set group cannot be supervised.

Issue 02 Ref. ENTP0406C04TEUS.doc P. 1

PROCEDURE

1. Management of the set supervision

Application On mgr
Select Users
Descend hierarchy
Prog. keys
Action Review/Modify
Select All instances
Entry Directory number: 31000
Key number: 11
Action Press CTRL+V or F1 to validate your choice
Directory Number : 31000
Entry
Key No. : 11
Function + Set Supervision
Mnemonic (Pocket,Mobile,4040,8&9) : --------------

Action Press CTRL+V or F1 to validate your choice

Entry Directory Number : 31001
Ringing Mode + No Ring
Deferred ring + NO

Action Press CTRL+V or F1 to validate your choice

Remark: There are different choices for the Ringing mode parameter :
- No Ring: without ring (no ring, only the icon or LED status indicates
trunk status),
- Long Ring: a short and repeated ring indicates that a call is waiting,
- Short Ring: a single short ring indicates that a call is waiting,
- Short Ring Without Overring,
- Long Ring Without Overring.
Action Press CTRL+C as many times as needed to come back on the main menu.

P. 2 Ref. ENTP0406C04TEUS.doc Issue 02

2. Check the management of the supervision set

Application On the call server

Login mtcl
Command multitool
(1)xa000001> multitool
Result
+------------------- [ Main Menu ] ---------------------+
[ 0] - Exit
[ 1] - Consult Multilines And Supervised Sets
[ 2] + Consult Boss/Secretary
[ 3] - Consult Sets With Data keys
[ 4] - Consult Sets With Supervision Data keys
[ 5] + Consult Directory Number Supervision
[ 6] - Consult Supervision Keys On Attendant
[ 7] - Consult Attendant Assistant Key On Attendant Group
[ 8] - Consult Supervised Trunk Groups and Keys
[ 9] + Consult Supervised Trunks and Keys
[10] + Multiline Sets With Their Multiline Keys
[11] + Consult Secondary MLA Keys
[12] + Consult Voice Mail Supervision Keys
CHOICE ?

Entry Choice ? 1
CHOICE ? 1
Result
+-----[ Consult Multilines And Supervised Sets ] -------+
Nulog | Numan | Domain | Multiline | Supervised
0 | 31010 | 0 | No | Yes
1 | 31000 | 0 | Yes | No
ooo Number of Multilines Set = 1
ooo Number of Supervised Set = 1

Remark :
you can see if the set is supervised or not

Issue 02 Ref. ENTP0406C04TEUS.doc P. 3

Application On the call server

Login mtcl
command multitool
(1)xa000001> multitool
Result
+--------------------[ Main Menu ]----------------------+
[ 0] - Exit
[ 1] - Consult Multilines And Supervised Sets
[ 2] + Consult Boss/Secretary
[ 3] - Consult Sets With Data keys
[ 4] - Consult Sets With Supervision Data keys
[ 5] + Consult Directory Number Supervision
[ 6] - Consult Supervision Keys On Attendant
[ 7] - Consult Attendant Assistant Key On Attendant Group
[ 8] - Consult Supervised Trunk Groups and Keys
[ 9] + Consult Supervised Trunks and Keys
[10] + Multiline Sets With Their Multiline Keys
[11] + Consult Secondary MLA Keys
[12] + Consult Voice Mail Supervision Keys
CHOICE ?

Entry Choice ? 5
CHOICE ? 5
Result
ooo Read_Keyboard oooooooooooo
+-------[ Consult Directory Number Supervision ] -------+
[ 0] - Father Menu
[ 1] - Consult All <Supervised> Directory Number
[ 2] - Consult All <Supervisor> Of a Directory Number
[ 3] - Consult All <Supervisor>
CHOICE ?

Action Press Enter to come back on the previous menu

Entry Choice ? 2
+--[ Consult All <Supervisor> Of a Directory Number ]---+
Result
< Supervised Number > ? 31010
Spvisor Nu | Dom. Spvis | Spvisor Nu | Dom. Spvis
31000 | 0 |
ooo Number Of <Supervisor> For the Directory Number [31010] = 1
h/Help q/Quit, Lines 1-5/5 End Of File

P. 4 Ref. ENTP0406C04TEUS.doc Issue 02

Action Press Enter to come back on the previous menu

Issue 02 Ref. ENTP0406C04TEUS.doc P. 5

P. 6 Ref. ENTP0406C04TEUS.doc Issue 02

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage multi-line and supervision keys

MANAGEMENT

1. Multi-line sets
- Modify the X8/X9 series sets to make them multi-line with this configuration:
- Set 3x001
- Key 1 Multi-line 3x001
- Key 3 Multi-line 3x101
- Set 3002
- Key 1 Multi-line 3x002
- Key 3 Multi-line 3x102
- Set 3003
- Key 1 Multi-line 3x003
- Key 3 Multi-line 3x025
- Key 5 Multi-line 3x126
- On the set 3x002, supervise the sets 3x010 et 3x011
- Check that it’s possible to make a direct call.
- Check that it’s possible to pick-up a call (when the set is rung)

Issue 04 Ref. ENTP0406H02TEUS.doc HO. 1

HO. 2 Ref. ENTP0406H02TEUS.doc Issue 04

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

637
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

638
Alcatel-Lucent OmniPCX Enterprise

Manager/Secretary group

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe manager/assistant group

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary group

Ref. ENTP0407P01TEUS Issue 02

639
Overview

Multi-line sets have to be used for manager and secretary sets

To create the manager/secretary group two keys have to be managed

The “assistant call” key on the manager set

The “manager call” key on the secretary set

Those both keys are used as a hot line (direct call, supervision)

Manager Secretary

All Rights Reserved © 2008, Alcatel-Lucent 2

Remarks
• A transfer through the hot line is moved on the own manager/assistant lines.
• The hot-line between the manager and the assistant can not be used to intercept the call.
• The state busy or free of the manager or of the assistant is given when the set is in communication on one line whatever it is
(private, internal..), and even if the set has other line free
• Limits:
1 Manager / 8 Secretaries
1 Secretary / 8 Managers

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary group

Ref. ENTP0407P01TEUS Issue 02

640
Filtering calls
Overview

On the manager/secretary group, it’s possible to filter the calls arriving on the
manager set thanks to the Screening/unscreening function

Screening: Immediate Forwarding by Origin

Unscreening key: Immediate Pickup by Origin

Keys have to be created and associated to filtering tables

It’s possible to create several screening and/or unscreening keys

When a(several) screening key(s) is(are) activated, if you press an unscreening

key, you disable the screening key(s) (and the other way as well)

All Rights Reserved © 2008, Alcatel-Lucent 3

Filtering

The manager has the possibility to activate or deactivate his filtering.

The manager can have several screening or unscreening keys and several assistants.

It is not possible to activate a screening and an unscreening key in the same time on the same manager set. But it is possible to
activate several filtering keys with the same type .A manager extension can have several screening keys. The manager can
assign different screening keys to different assistants (screening 1 to assistant 1, screening 2 to assistant 2 etc). If the
manager has several assistants, after pressing one screening key, he selects the assistant he wants to call by pressing the "call
assistant" key.

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary group

Ref. ENTP0407P01TEUS Issue 02

641
Filtering calls
Behavior

A screening key is associated to the filtering table

When the manager presses this key, if a call arrives on this manager set and
if this call is from one number managed on the table, the call is forwarded
directly on the secretary set. If the call is not in the table, the manager set
receive the call

A unscreening key is associated to the filtering table

When the manager presses this key, if a call arrives on this manager set and
if this call is from one number managed on the table, the call arrives on the
manager set. If the number is not in the table, the call is forwarded on the
secretary set

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary group

Ref. ENTP0407P01TEUS Issue 02

642
Filtering calls
Additional facilities

Filtered ISDN key

Filters an ISDN number
Supported in a filtering table
Filter not activated = directory key
ISDN number can be changed by the manager

Selective screening
No screening on the secondary lines
Total screening

Filtering supervision by the secretary

Assistant can validate/disable the filtering with a «filtering supervision» key and
supervise as well

Discrete listen-in
Dynamic key on the manager's extension
Call interception
Notification on assistant set

All Rights Reserved © 2008, Alcatel-Lucent 5

Filtered ISDN key

Without any optional management, when the manager hits on this key, he will call, directly the directory number corresponding
to this key.
In management, this key, can be associated with an screening or unscreening key. When this screening (or unscreening) key is
validated, the incoming call (with the caller directory number corresponding to the content of the ISDN key) will follow diverted
functioning.

Private (secondary) line for manager set

The manager set can have several directory numbers. The filtering facility between the manager and the assistant can be
programmed (management) for one directory number or for all the directory number.
In case of setting the manager set with several directory number, and the filtering has been programmed on one directory
number, the manager set has the possibility to receive "private calls".(no screening on secondary lines).
These calls are not following the filtering mode and constitute for the manager "private directory number".

Filtering supervision and activation/deactivation by assistant

This service allows the assistant to put ON/OFF the filtering of her manager (s) from her set and to supervise the filtering status.
For that, a supervision key must be programmed, by MAO, on the assistant set for each filtered manager (one key per Manager).

Discrete listen-in: operation depends on the set used

This feature allows the manager to enter secretly in the communication of his assistant (only on the manager calls filtered by the
assistant).
When the assistant is in communication with a call (predestined to the manager) the manager hits the softkey to intrude in the
communication. A screen indication is given to the assistant that the manager is inside the communication (but only visual). Then
the assistant can decide to release the manager by hitting a softkey.
After having intrude in the communication the manager can decide to cancel the intrusion (by hang-up or press the release
softkey) or to pick-up the call and release the assistant by hitting a blinking line key or hitting a Softkey, Then he recovers a
normal situation of a simple call.

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary group

Ref. ENTP0407P01TEUS Issue 02

643
Filtering calls
Limits

No limit about the number of screening/unscreening keys by set

256 tables usable with screening or unscreening functions

16 parameters in each table

All internal numbers

All trunk groups
An internal number or several
A trunk group or several
A speed dial number or several
An attendant number or several
A T2 number (specific ISDN number) or several

It is possible to mix in the same filtering table different parameters.

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary group

Ref. ENTP0407P01TEUS Issue 02

644
Away secretary function

Only possible on an secretary set and on one key only

Allows the secretary to signal her absence to her manager(s)

Filtering is then suspended until the secretary presses this key again

When this key is validated, personal calls destined to the secretary still reach
the secretary set

All Rights Reserved © 2008, Alcatel-Lucent 7

The LEDs or icons associated with the “away assistant” key on the assistant set and with the “assistant call” key on the manager
set flash when the assistant is away

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary group

Ref. ENTP0407P01TEUS Issue 02

645
Routing secretary function

In a manager/secretary configuration, there can be one overflow secretary who

will automatically replace the official secretary when the latter is in “secretary
away” position and who will carry out the same functions

There is only one overflow secretary per manager, but this overflow secretary
can have several managers

This set must not already be declared secretary for this manager

All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary group

Ref. ENTP0407P01TEUS Issue 02

646
Manager/Secretary messaging

It is possible to send some messages between the manager and secretary sets

For instance:
If someone arrives in the secretary office to see the manager, the secretary can
send a text message to the manager from her set, the manager can answer the
message
Some predefined messages are available

This facility can be used only if the manager is in idle state or in conversation(1)

All Rights Reserved © 2008, Alcatel-Lucent 9

(1) - The secretary cannot send short messages to a manager on a conference call, dialing, three party call, on a call with his
secretary

This key permits the assistant to send an urgent message to her manager without dialing. Five pre-set messages are available:
- Arrival of M_,
- Call from M_,
- Urgent call from M_,
- Expected in meeting,
- You have a meeting

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary group

Ref. ENTP0407P01TEUS Issue 02

647
All Rights Reserved © 2008, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary group

Ref. ENTP0407P01TEUS Issue 02

648
Alcatel-Lucent OmniPCX Enterprise
Manager/Secretary group

PROCEDURE

OBJECTIVE

- To learn how to manage a Manager/Secretary group

OVERVIEW
The manager/secretary group is created from multi-line sets.
This procedure explain you how to create the group and to manage the different facilities
associated to this group.

Issue 02 Ref. ENTP0407C02TEUS.doc P. 1

PROCEDURE

1. Creation of the group

Application Configuration Tab PCX

Path / Users
Object “31100” (User directory number of the manager set)
Path / Progr.Keys
Parameters Key No. 9
Function: Assistant Call
Directory number: 31000 (secretary directory number)
Key number: 8
Mnemo (Pocket,Mobile,4040,8&9): Secretary
Action
Click on “ ” to validate

Note: After validating, the system create automatically the Manager Call key on the
secretary set, in this example on the secretary set 31000 and on the key 8 the
Manager call key is created
Can use the graphical view for keys management

Note: In this example, you have to follow the next steps

1) Select a user (31100 for instance)
2) Right click on the mouse and select “Graphical View…”

P. 2 Ref. ENTP0407C02TEUS.doc Issue 02

2. Create an Absence assistant function key

Application Configuration Tab PCX

Path / Users
Object “31000” (User directory number of the secretary set)
Path / Progr.Keys
Parameters Key No. 9
Function: Assistant away
Mnemo (Pocket,Mobile,4040,8&9): Away
Action
Click on “ ” to validate

Note: The manager can see on the Assistant call key if the secretary is absent or not.

3. Create a Manager Mail function key

Application Configuration Tab PCX

Path / Users
Object “31000” (User directory number of the secretary set)
Path / Progr.Keys
Parameters Key No. 10
Function: Manager mail
Mnemo (Pocket,Mobile,4040,8&9): Manager mail
Action
Click on “ ” to validate

Note: The secretary sends a text message on the manager set screen and he can make an
answer.

Issue 02 Ref. ENTP0407C02TEUS.doc P. 3

4. Manage the screening function and filtering tables

4.1. Create the screening function key

Application Configuration Tab PCX

Path / Users
Object “31100” (User directory number of the manager set)
Path / Progr.Keys
Parameters Key No. 10
Function: Screening key
Filtering table n° 1
Mnemo (Pocket,Mobile,4040,8&9): Screening 1
Action
Click on “ ” to validate

4.2. Create the unscreening function key

Application Configuration Tab PCX

Path / Users
Object “31100” (User directory number of the manager set)
Path / Progr.Keys
Parameters Key No. 11
Function: Unscreening key
Filtering table n° 1
Mnemo (Pocket,Mobile,4040,8&9): Unscreening 1
Action
Click on “ ” to validate

P. 4 Ref. ENTP0407C02TEUS.doc Issue 02

4.3. Create the Filtering tables

Application Configuration Tab PCX

Path / Specific Telephones Services
Object “1” (Table identifier)
Tab All
Object Filtering Table
Action Create
Parameters Table ID 1
Filter type: One Directory no.
Content 31010
Action
Click on “ ” to validate

Note: Table ID corresponds to the Filtering table No. configured on the Screening or
Unscreening keys.
There are different Filter types:
All Directory No.
All Trunk Groups
One Directory No.
One Speed Dialing No.
One Attendant number
T2 Key
Directory

Note: For this configuration if you press the Screening key on the manager set, the calls
from the set 31010 are routed on the secretary set, not the others.
For this configuration if you press the Unscreening key on the manager set, all
calls are routed on the secretary set, not the calls from the set 31010 .

Issue 02 Ref. ENTP0407C02TEUS.doc P. 5

5. Screening supervision

Application Configuration Tab PCX

Path / Users
Object “31100” (User directory number of the secretary set)
Path / Progr.Keys
Parameters Key No. 11
Function: Screening Supervision
Directory Number: 31100
Key Number: 10
Mnemo (Pocket,Mobile,4040,8&9): Sup-Screen
Action
Click on “ ” to validate

Note: One screening supervision key per screening/unscreening key

Directory number corresponds at the manager directory number
Key number corresponds at the screening/unscreening key number created on the
manager set

6. Filtered ISDN key

Application Configuration Tab PCX

Path / Users
Object “31100” (User directory number of the manager set)
Path / Progr.Keys
Parameters Key No. 11
Function: ISDN Filtering Key
Content: 00205050505
Mnemo (Pocket,Mobile,4040,8&9): ISDN key
Locked: No
Action
Click on “ ” to validate

Note: The “content” corresponds to an external number, this number can be filtered if
the screening or unscreening uses a filtering table with the choice”T2 key”
Locked,” No” means you can modify from the set the number, “yes” not possible

P. 6 Ref. ENTP0407C02TEUS.doc Issue 02

7. Routing secretary function

Application Configuration Tab PCX

Path / Users
Object “32000” (User directory number a secretary set used for the overflow)
Path / Progr.Keys
Parameters Key No. 5
Function: Routing Assistant
Content: 31100
Mnemo (Pocket,Mobile,4040,8&9): Sec-overflow
Action
Click on “ ” to validate

Note: This secretary is not an “official” secretary for this manager

Content correspond to the manager directory number

Issue 02 Ref. ENTP0407C02TEUS.doc P. 7

P. 8 Ref. ENTP0407C02TEUS.doc Issue 02

Manager/Secretary groups

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To maintain Manager / assistant groups

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary groups

Ref. ENTP0407M01TEUS Issue 02

657
Command: multitool

When you run the command, this menu appears:

+------- [ Main Menu ] -------+

[ 0] - Exit
[ 1] - Consult Multilines And Supervised Sets
[ 2] + Consult Boss/Secretary
[ 3] - Consult Sets With Data keys
[ 4] - Consult Sets With Supervision Data keys
[ 5] + Consult Directory Number Supervision
[ 6] - Consult Supervision Keys On Attendant
[ 7] - Consult Attendant Assistant Key On Attendant Group
[ 8] - Consult Supervised Trunk Groups and Keys
[ 9] + Consult Supervised Trunks and Keys
[10] + Multiline Sets With Their Multiline Keys
[11] + Consult Secondary MLA Keys
[12] + Consult Voice Mail Supervision Keys

CHOICE ?

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary groups

Ref. ENTP0407M01TEUS Issue 02

658
Command: multitool

Select the choice 2 - Consult Boss/Secretary

CHOICE ? 2

+------- [ Consult Boss/Secretary ] -------+

[ 0] - Father Menu
[ 1] - Consult All <Boss> Sets
[ 2] - Consult All <Secretary> Sets
[ 3] - Consult All <Routing Secretary> Sets

CHOICE ?

The choice 1 gives you the possibility to check all the manager sets created on
the entire system

Manager Secretary

1 | 31000 | 7 | 0 | 31100 | 5 | 0

ooo Number Of <Boss> Sets = 1

Key number

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary groups

Ref. ENTP0407M01TEUS Issue 02

659
Command: multitool

The choice 2 gives you the possibility to check all the secretary sets created on
the entire system
Secretary Manager

1 | 31100 | 5 | 0 | 31000 | 7 | 0

ooo Number Of <Boss> Sets = 1

Key number

The choice 3 give you the possibility to check all the routing secretary sets
created on the entire system
Routing Secretary Manager

1 | 32000 | 4 | 0 | 31100 | 5 | 0

ooo Number Of <Boss> Sets = 1

Key number

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Manager/Secretary groups

Ref. ENTP0407M01TEUS Issue 02

660
Alcatel-Lucent OmniPCX Enterprise
Manager/Secretary group

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage the Manager/Secretary groups

MANAGEMENT

1. Management of a group 1 manager / 1 secretary

- Create a group between the sets 3x000 (Manager) and the set 3x001(secretary).
- The manager key number 2 (Assistant call) must correspond to the secretary key
number 2 (Manager call).
- Only the primary number of the manager must be filtered (multiline characteristics)
- Filtering table 1: Corresponds to the internal calls
- Filtering table 2: Corresponds to the external calls
- Filtering table 3: Contains the sets 3x003,3x010
- Create Screening and Unscreening keys linked with a filtering table.
- Key n°7: Screening (table 1)
- Key n°8: Unscreening (table 1)
- Key n°9: Screening (table 2)
- Key n°10: Unscreening (table 2)
- Key n°11: Screening (table 3)
- Key n°12: Unscreening (table 3)
- Test the group (Transfer of a call from the assistant set,...)
- On the assistant set, it must be possible to make a distinction between the assistant
calls, and the filtered calls.

2. Management of the manager mail

- Create on the assistant set a key of type ‘manager mail’
- Test it

Issue 04 Ref. ENTP0407H01TEUS.doc HO. 1

3. Management of the discrete listen-in and the pick-up

- Create on a manager set a ‘supervision’ key.
- Validate the short ring mode in the supervision key.
- The directory number to supervise is the assistant one.
- Activate a filtering on the manager set.
- Test it
- Is the manager able to listen to all the communications received or started on the
assistant set?

4. Maintenance
- Using the command “multitool” display the information about the manager / assistant
group.

HO. 2 Ref. ENTP0407H01TEUS.doc Issue 04

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

663
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

664
Alcatel-Lucent OmniPCX Enterprise

Multiple Line Appearance

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Multiple Line Appearance

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

665
Multiple Line Appearance
Overview

Multiple Line Appearance:

Gives the possibility to have a group of lines with the same directory number
irrespective of the physical sets

One MLA key or more per sets with the same directory number defines the
group of lines

The call is notified on every lines of the group, till this moment it will be
possible to:

Pick-up the call from every sets

Make an outgoing call from every sets

Put on hold the call and retrieve the call from every sets

Supervise the line

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

666
Multiple Line Appearance
Overview

Example of configuration: Menu/perso/info

Line Line
GR
MLA Secondary 3100 MLA primary 3200 3200
GR
3100 MLA secondary 3100 MLA primary 3301
GR
MLA secondary 3100 3301

3003

Menu/perso/info Menu/perso/info
Line 3000 Line 3020 Line Line
GR
MLA Secondary 3100
MLA primary 3100 MLA secondary 3200 3200
3000
MLA secondary 3100 MLA secondary 3301
MLA primary 3100 GR
MLA primary 3100 MLA secondary 3100 3301

GR GR
3100 3100

3000 3002

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

667
Multiple Line Appearance
Overview

The group of lines is made of two different types of keys:

Primary MLA key:

Associated to a directory number. It will be the call number of the group.

Possibility to manage several keys with the same directory number on the same set:

In this case an order id during the key creation is allocated

This order id defines the call presentation on the MLA primary keys

Menu/perso/info
Line 3000 Line 3020
Order id:1
MLA primary 3100
Order id:2
MLA primary 3100
Order id:3 MLA primary 3100

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

668
Multiple Line Appearance
Overview

Second type of keys:

Secondary MLA keys:

One secondary MLA key is systematically associated to a MLA primary key

Possibility to have several secondary MLA keys on different sets for the same
primary MLA key

A secondary MLA key is like a regular supervision key,with one more possibility:

Take the supervised line to set up a call

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

669
Multiple Line Appearance
Overview

Second type of keys:

Secondary MLA keys:

When there are several primary MLA keys on one set and we want also several
secondary MLA keys on another set:

The order id for the secondary key must be the same than the order id of the primary key

Menu/perso/info Menu/perso/info
Line 3000 Line 3020 Line 3003 Line 3025
MLA primary 3100 Order id:1 MLA secondary 3100

MLA primary 3100 Order id:2 MLA secondary 3100

MLA primary 3100 Order id:3 MLA secondary 3100

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

670
Multiple Line Appearance
Overview

Signaling on MLA keys

When a call is routed to one Primary key, it will also be automatically routed
to all the associated secondary keys

Possibility to pick-up the call from every sets

When the call is put on hold on one set, it is also on hold on all the MLA keys
of the same group

Possibility to retrieve the call from every sets

One user of the group of lines can take the line, the busy status is known on
every MLA keys of the group

Press on an primary or secondary MLA keys

All Rights Reserved © 2008, Alcatel-Lucent 7

!!! We can specify three options about the hold function on the MLA keys
Privacy hold
- the hold is local only.the other lines of the groups don’t supervised anything
Supervised hold
- the hold is supervised by all the lines of the group.All the sets can retrieve the call
Released the call
- we can not put on hold the call when we press on the MLA keys
- First press to pick-up the call
- Second press to release the call

Case of Supervised hold:

When you put on hold the call, the set is automatically released (not necessary to on hock)
There is two timers:
One for external calls - timer 296 (default value 20min)
One for internal calls - timer 298 ( default value 20min)
Timer 296
If you put on hold the incoming call,after 20mn the set will be rung again.

Timer 298
If you put on hold the internal call (can be local calls or network calls),after 20mn the set will be rung again.

There is an option in system to define if at the end of the timer 298 or 296 we want to ring back all lines of the group (MLA
primary and secondary) or only the set that put on hold the call.

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

671
Multiple Line Appearance
Overview

Icon status example:

user1 user2 user3

MLA keys free

MLA primary key rung

User2 in conversation, MLA keys seen

busy on user1 and user3

Call on hold on user1,user2,user3 and

possibility to retrieve the call from the
three sets
2nd call on user2, MLA keys seen busy on
user1 and user3
Primary Secondary Secondary
key key key

All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

672
Multiple Line Appearance
Overview

Display on the UA set

For the primary MLA key

Like a regular multi-line key

For the secondary MLA key

Depends on the type of ringing selected during the management of the key

With ringing (short or long - with or without over ring)

The secondary sets are rung and the calling name is displayed on the set

Without ringing
The secondary sets are not rung and nothing on the display

With delayed ringing

During the delay time out: no ring no display,just the icon blinking
After the delay time out the set rings and the calling name is displayed

All Rights Reserved © 2008, Alcatel-Lucent 9

Timer N° 297 for the delayed ringing: default value 5s

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

673
Multiple Line Appearance
Overview

Restrictions:

No MLA set in parallel PBX

No twin set management with sets with MLA keys

Network moving is not authorized for sets using MLA keys

Extension must be multi-line

All Rights Reserved © 2008, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

674
Multiple Line Appearance
Overview

Case of MLA set out of service:

If one set is out of service and has MLA secondary keys, the other MLA keys
of the line’s group (primary or secondary) are not in the busy state

If the primary set is out of service:

The group of lines is out of service, no calls will be presented on the primary MLA
key

All the associated secondary MLA keys are considered as busy

Not very good, isn’t it (solution next page)

All Rights Reserved © 2008, Alcatel-Lucent 11

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

675
Multiple Line Appearance
Overview

The case of out of service set

Creation of a new virtual user:

Type of set: UA VIRTUAL (4035 Virtual)

Identical management concerning the MLA keys of the primary MLA extension

All Rights Reserved © 2008, Alcatel-Lucent 12

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

676
Multiple Line Appearance
Overview

Generic services applied to MLA keys

Individual and common hold

A call presented on a primary MLA key can also be put on hold with an individual or
common hold key
In this case the communication will not be back to the MLA key but on a free multiline of
the set

Non answered ISDN calls - automatic Call-back

Only the set on which the MLA key is managed is notified

If you set up the call-back, the system sends through the isdn network:
Installation number + Principal directory number of the set

All Rights Reserved © 2008, Alcatel-Lucent 13

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

677
Multiple Line Appearance
Overview

Generic services applied to MLA keys

Forward on ringing

Only available for the primary MLA

If there are several calls on ringing, all of them will be forwarded to the directory
number defined in the MAO or dialed by the user

Hold key for the US sets (hold privacy)

If you press on the hold key:

the call is put on hold on the MLA keys (primary or secondary)
All the MLA keys of the group are busy

Not necessary to press on the MLA keys to put on hold the call

To retrieve the call press on the MLA key

All Rights Reserved © 2008, Alcatel-Lucent 14

Hold key:
There are two ways to use this key:
Privacy hold: (default value)
When you press the hold key; the call is put on hold only for the user (local hold)

Supervised hold:
when you press the hold key, the call is put on hold for all the group of lines

For the management see the management chapter.

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

678
Multiple Line Appearance
Overview

Accounting

outgoing call (charging ticket example):

====[/DHS3dyn/account/TAXAPPSQ.DAT: Ticket number 1/1/2]=======================

(00) TicketVersion = ED5.1 (01) CalledNumber = 0214132100
(02) ChargedNumber = 32000 (03) ChargedUserName = ua 32000
(04) ChargedCostCenter = (05) ChargedCompany =
(06) ChargedPartyNode = 102 (07) Subaddress =
(08) CallingNumber =
(09) CallType = PublicNetworkOutgoingCall
(10) CostType = ISDNCircuitSwitchedCall (11) EndDateTime = 20010415 09:13:56
(12) ChargeUnits = 0 (13) CostInfo = 0
(14) Duration = 10 (15) TrunkIdentity = 1
(16) TrunkGroupIdentity = 20 (17) TrunkNode = 102
(18) PersonalOrBusiness = Normal (19) AccessCode =
(20) SpecificChargeInfo = (21) BearerCapability = Speech
(22) HighLevelComp = Telephony (23) DataVolume = 0
(24) UserToUserVolume = 0
(25) ExternFacilities = CallingLineIdentificationPresentation
(26) InternFacilities = BasicCall (27) CallReference = 0
(28) SegmentsRate1 = 0 (29) SegmentsRate2 = 0
(30) SegmentsRate3 = 0 (31) ComType = Voice
(32) X25IncomingFlowRate = Unspecified (33) X25OutgoingFlowRate = Unspecified
(34) Carrier = 0 (35) InitialDialledNumber =
(36) WaitingDuration = 0 (37) EffectiveCallDuration = 0
(38) RedirectedCallIndicator = 0 (39) StartDateTime = 20010415 09:13:46
(40) ActingExtensionNumber = 32000 (41) CalledNumberNode = 9999
(42) CallingNumberNode = 9999 (43) InitialDialledNumberNode = 9999
(44) ActingExtensionNumberNode = 102 (45) TransitTrunkGroupIdentity = 32767
(46) NodeTimeOffset = 0

All Rights Reserved © 2008, Alcatel-Lucent 15

There is no charging tickets for the MLA numbers (never).always for the physical directory number.(see the previous example)

The NDS transmitted will be always the physical directory number of the set.

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

679
Multiple Line Appearance
Overview

Accounting

Incoming call (charging ticket example):

----[/DHS3dyn/account/TAXAPPSR.DAT: Ticket number 2/2/2]-----------------------

(00) TicketVersion = ED5.1 (01) CalledNumber = 0214132100
(02) ChargedNumber = 32000 (03) ChargedUserName = ua 32000
(04) ChargedCostCenter = (05) ChargedCompany =
(06) ChargedPartyNode = 102 (07) Subaddress =
(08) CallingNumber =
(09) CallType = PublicNetworkIncomingCall
(10) CostType = ISDNCircuitSwitchedCall (11) EndDateTime = 20010415 09:17:33
(12) ChargeUnits = 0 (13) CostInfo = 0
(14) Duration = 8 (15) TrunkIdentity = 0
(16) TrunkGroupIdentity = 20 (17) TrunkNode = 102
(18) PersonalOrBusiness = Normal (19) AccessCode =
(20) SpecificChargeInfo = (21) BearerCapability = Speech
(22) HighLevelComp = Telephony (23) DataVolume = 0
(24) UserToUserVolume = 0 (25) ExternFacilities =
(26) InternFacilities = BasicCall (27) CallReference = 0
(28) SegmentsRate1 = 0 (29) SegmentsRate2 = 0
(30) SegmentsRate3 = 0 (31) ComType = Voice
(32) X25IncomingFlowRate = Unspecified (33) X25OutgoingFlowRate = Unspecified
(34) Carrier = 0 (35) InitialDialledNumber = 32666
(36) WaitingDuration = 5 (37) EffectiveCallDuration = 8
(38) RedirectedCallIndicator = 0 (39) StartDateTime = 20010415 09:17:25
(40) ActingExtensionNumber = (41) CalledNumberNode = 9999
(42) CallingNumberNode = 9999 (43) InitialDialledNumberNode = 9999
(44) ActingExtensionNumberNode = 9999 (45) TransitTrunkGroupIdentity = 32767
(46) NodeTimeOffset = 0

All Rights Reserved © 2008, Alcatel-Lucent 16

On the charging ticket appears the call number of the MLA group (field 35)

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

680
Multiple Line Appearance
Overview

Limits:

1000 groups
100 sets per group
One set can supervised 60 groups
Number of MLA keys per set = Number of programmable keys of the set

OPS

No OPS lock

Networking

All the sets of the same group must be on the same node.

All Rights Reserved © 2008, Alcatel-Lucent 17

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

681
All Rights Reserved © 2008, Alcatel-Lucent 18

Alcatel-Lucent OmniPCX Enterprise – Multiple Line Appearance

Ref. ENTP0480P02TEUS Issue 02

682
Alcatel-Lucent OmniPCX Enterprise
MLA management with mgr

PROCEDURE

OBJECTIVE

- To learn how to manage MLA with mgr

OVERVIEW
The A-MLA (Alcatel-Lucent Multi-line Appearance) service is a pseudo parallel hunt group with
Multi-line sets.
This set of people forms an A-MLA group with one call number. Each member of this group has a
multi-line set with A-MLA keys (primary or secondary). The first A-MLA key is called order 1 key,
the second is called order 2 and so on.
An incoming call (local, network, or external) arriving on the group number is displayed on each
group member. The A-MLA keys of the same order are activated.

Issue 02 Ref. ENTP0480C02TEUS.doc P. 1

PROCEDURE

1. Create a virtual set for the MLA primary set

Application On mgr
Path Users
Action Create
Entry Directory Number : 31500
Shelf Address : 255
Board Address : 255
Equipment Address : 255
Set Type + UA VIRTUAL (4035 VIRTUAL)

Action Press CTRL+V to validate

Action Press CTRL+C as many times as needed to come back on main menu
Remark The set 31500 will be the primary set
The use of a virtual set for the primary’s one is better than to use a physical
set because if this one is down , the secondary keys don’t work anymore, so
you lose your MLA group

2. Create multi-line keys on the primary virtual set

Application On mgr
Path Users/ Progr.Keys/ (enter the set number)
Action Review/Modify
Entry Directory number: 31500 (e.g.)
Key number: 1 (e.g.)

Action Press CTRL+V or F1 to validate your choice

Directory Number : 31500
Entry
Key Number : 1
Function + Multi-line
Mnemonic (Pocket,Mobile,4040) : ------------

Action Press CTRL+V or F1 to validate your choice

P. 2 Ref. ENTP0480C02TEUS.doc Issue 02

3. Create the MLA keys

Application On mgr
Path Users / Progr.Keys
Action Review/Modify
Entry Directory Number : 31500
Key Number : 3

Action Press CTRL+V to validate

Entry Function + Primary MLA

Action Press CTRL+V to validate

Entry Directory Number : 31600
Order : 1

Action Press CTRL+V to validate

Action Press CTRL+C as many times as needed to come back on main menu
Remark The set 31500 must be multi-line. 31500 is the primary set.
The MLA group number is 31600.
You can create more than one MLA key for this directory number (31600).
e.g.:
Create a second MLA key with programmable key number 4
Enter:
Directory Number : 31600
Order : 2
Path Users / Progr.Keys
Action Review/Modify
Entry Directory Number : 31100
Key Number : 3

Action Press CTRL+V to validate

Entry Function + Secondary MLA

Action Press CTRL+V to validate

Entry Directory Number : 31600
Order : 1
Ringing Mode + No Ring
Deferred ring + NO

Issue 02 Ref. ENTP0480C02TEUS.doc P. 3

Action Press CTRL+V to validate

Action Press CTRL+C as many times as needed to come back on main menu
Remark The set 31000 must be multi-line.
The set 31000 is a secondary set.
The MLA group number is 31600.
You can create more than one MLA key for this directory number (31400)
but with a different order
e.g.:
create a second MLA key with programmable key number 4
Enter:
Directory Number : 31600
Order : 2
Select the ringing mode if a call is routed to a secondary MLA key
(overring=beeps).
Possibilities for the Ringing Mode of the key are:
No Ring
Short Ring
Long Ring
Short Ring Without Overring
Long Ring Without Overring
Select the Deferred ring:
the ringing mode can be differed (Yes) or instantaneous (No).

P. 4 Ref. ENTP0480C02TEUS.doc Issue 02

4. Management of the supervised hold ring back mode

Application On mgr
Path System / Other System Param. / MLA Parameters
Action Review/Modify
System Option + Supervised Hold Ringback Mode
Select
Action Press CTRL+V to validate
Entry Supervised Hold Ringback Mode + Ring All Supervisor Sets
Action Press CTRL+V to validate
Action Press CTRL+C as many times as needed to come back on main menu
Remark When a call has been put on hold and if the hold timer is exceeded, select
the extension that will be called back:
- Ring all supervisors sets: All the extensions with a MLA key
- Ring hold owner only: The extension that has put the call on hold
- Ring attendant: The attendant
Path System / Other System Param. / MLA Parameters
Action Review/Modify
Select System Option + MLA Line Key Option

Action Press CTRL+V to validate

Entry MLA Line Key Option + Supervised Hold

Action Press CTRL+V to validate

Action Press CTRL+C as many times as needed to come back on main menu
Remark MLA line key option parameter determines the behavior used in case of
pressing the MLA key when a communication is already running on the MLA
key:
- Release the call: The call can not be put on hold, it is released.
- Privacy hold: The call can be put on hold but can be retrieved only from
the hold initializing extension
- Supervised hold: The call can be put on hold and be retrieved from any
extension of the MLA group.
Path System / Other System Param. / MLA Parameters
Action Review/Modify
Select System Option + MLA Hold Key Option

Action Press CTRL+V to validate

Entry MLA Hold Key Option + Privacy Hold

Issue 02 Ref. ENTP0480C02TEUS.doc P. 5

Action Press CTRL+V to validate

Action Press CTRL+C as many times as needed to come back on main menu
Remark MLA hold key option parameter is specific US. It determines the behavior
used
in case of pressing the hold key when a communication is already running on
the MLA key:
- Privacy hold: The call can be put on hold but can be retrieved only from
the hold initializing extension
- Supervised hold: The call can be put on hold and be retrieved from any
extension of the MLA group.

P. 6 Ref. ENTP0480C02TEUS.doc Issue 02

5. Timers management

5.1. Trunk supervised hold timer

Application On mgr
Path System / Timers
Action Review/Modify
Entry Timer No. : 296

Action Press CTRL+V to validate

Entry Timer units : 1200

Action Press CTRL+V to validate

Action Press CTRL+C as many times as needed to come back on main menu
Remark 20 minutes by default. At the end of this timer, an external call put on hold
will be routed according to “Supervised hold ring back mode” parameter
(see above)
Path System / Timers
Action Review/Modify
Entry Timer No. : 298

Action Press CTRL+V to validate

Entry Timer units : 1200

Action Press CTRL+V to validate

Action Press CTRL+C as many times as needed to come back on main menu
Remark 20 minutes by default. At the end of this timer, an local call put on hold
will be routed according to “Supervised hold ring back mode” parameter
(see above)
Select System / Timers
Action Review/Modify
Entry Timer No. : 297

Action Press CTRL+V to validate

Entry Timer units : 50

Action Press CTRL+V to validate

Action Press CTRL+C as many times as needed to come back on main menu
Remark 5 seconds by default. At the end of this timer, This timer is used only if the
parameter Differed ring of a secondary MLA key is validated.

Issue 02 Ref. ENTP0480C02TEUS.doc P. 7

Path System / Other System Param. / Local Features Parameters

Action Review/Modify
System Option + Ring On Hangup Private Hold
Select
Action Press CTRL+V to validate
Entry Ring On Hangup Private Hold + Do Not Ringback

Action Press CTRL+V to validate

Action Press CTRL+C as many times as needed to come back on main menu
Remark Ring on Hang up private hold:
- Ring back after hang up
- Do not ring back
If a call is put on hold using the HOLD key and not the MLA key and if the
user hangs up, this parameter determines if the extension has to ring or
not.

6. Validation of direct outgoing seizure from MLA key

Application On mgr
Path Users
Action Review/Modify
Entry Directory Number : 31000

Action Press CTRL+V to validate

Entry Automatic Outgoing Seizure for MLA + True

Action Press CTRL+V to validate

Action Press CTRL+C as many times as needed to come back on main menu
Remark By pressing the MLA key, the user will be able to make directly an outgoing
call!

P. 8 Ref. ENTP0480C02TEUS.doc Issue 02

7. Check the management of MLA primary keys

Application On the call server

Login mtcl
Command readkey
Result --> main menu <--
1) display by phone set type
2) display by mcdu
3) help about phone set keys
q) quit
Your choice [1..3, q]:
Entry Your choice [1..3, q]: 2
Entry Enter mcdu : 31500
---------------------------------------------------
Result
Keys state of the 31500 mcdu phone set:
Phone set type: UA 4035
Number of keys = 28
Key 3: Multi MCDU MLAP ---> Key content: 31600
Dom 0 CH DATA : Tsl_CH_Local_Station ID = 2
inf_num: -1
etat_led: 45
pri_cour_line: 0-0
cor_pre: 0
keytype: 255
Key 4: Multi MCDU MLAP ---> Key content: 31600
Dom 0 CH DATA : Tsl_CH_Local_Station ID = 2
inf_num: -1
etat_led: 45
pri_cour_line: 0-0
cor_pre: 0
keytype: 255

Remark The set 31500 is in the MLA group 31600 (with MLA keys 3 and 4).

Issue 02 Ref. ENTP0480C02TEUS.doc P. 9

8. Check the management of the MLA secondary keys

Application On the call server

Login mtcl
Command multitool
+------- [ Main Menu ] -------+
Result
[ 0] - Exit
[ 1] - Consult Multi-lines And Supervised Sets
[ 2] + Consult Boss/Secretary
[ 3] - Consult Sets With Data keys
[ 4] - Consult Sets With Supervision Data keys
[ 5] + Consult Directory Number Supervision
[ 6] - Consult Supervision Keys On Attendant
[ 7] - Consult Attendant Assistant Key On Attendant Group
[ 8] - Consult Supervised Trunk Groups and Keys
[ 9] + Consult Supervised Trunks and Keys
[10] + Multi-line Sets With Their Multi-line Keys
[11] + Consult Secondary MLA Keys
[12] + Consult Voice Mail Supervision Keys
CHOICE ?

Entry Your choice [1..3, q]: 11

+------- [ Consult Secondary MLA Keys ] -------+

Entry
[ 0] - Father Menu
[ 1] + Consult All Secondary MLA keys
[ 2] - Consult All Secondary MLA keys Of a Directory Number
CHOICE ? 1
+------- [ Consult All Secondary MLA keys ] -------+
Entry
[ 0] - Father Menu
[ 1] - From Database
[ 2] - From Memory
CHOICE ? 1
+------- [ From Database ] -------+
Entry
Sorted by [0=Logical Number, 1=Set Number] ? 1
----------------------------------------------------------------------------
Result
|Nulog|Supervisor|Key Number|Supervised|Nulog vised|Order|vised key|tab_mcdu|
----------------------------------------------------------------------------
| 9| 31000 | 3| 31600 | 8 | 1 | 3 | 2|
| 9| 31000 | 4| 31600 | 8 | 2 | 4 | 2|
----------------------------------------------------------------------------
2 MLA secondary Keys..

Entry h/Help q/Quit, Lines 1-10/10 End Of File: q

P. 10 Ref. ENTP0480C02TEUS.doc Issue 02

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage a MLA configuration

MANAGEMENT

1. Create a virtual set (4035) with one free number from the numbering plan

2. Manage two multiline keys in this set

3. Manage the main MLA keys (MLA number 3x600)

3.1. Key number 3: Main MLA key (order 1)

3.2. Key number 4: Main MLA key (order 2)

4. Manage in two multiline sets the secondary MLA keys

4.1. In the first set:

4.1.1. On one free key manage the secondary MLA key (order 1)
4.1.2. On one free key manage the secondary MLA key (order 2)

4.2. In the second set:

4.2.1. On one free key manage the secondary MLA key (order 1)
4.2.2. On one free key manage the secondary MLA key (order 2)

5. Test the configuration

Issue 02 Ref. ENTP0480H02TEUS.doc HO. 1

HO. 2 Ref. ENTP0480H02TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

695
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

696
Alcatel-Lucent OmniPCX Enterprise
R9.0
Starter Pack Enterprise

Part 3/3 PARTICIPANT’S GUIDE

DOCUMENT CHANGES

Issue Date Issue Date

Alcatel-Lucent OmniPCX Enterprise R9.0 Starter Pack Enterprise 01 12/08

File reference: ENTPTE900US

GENERAL SUMMARY

Part 3

33. Groups
ENTP0405P03TEUS ...................................................................................... 697
ENTP0405C01TEUS ...................................................................................... 713
ENTP0405C02TEUS ...................................................................................... 717
ENTP0405M01TEUS ...................................................................................... 721
ENTP0405H02TEUS ...................................................................................... 727

34. Call Distribution

ENTP0418P10TEUS ...................................................................................... 731

35. Call Distribution - Entities

ENTP0418P11TEUS ...................................................................................... 741
ENTP0418C11TEUS ...................................................................................... 747
ENTP0418M01TEUS ...................................................................................... 753
ENTP0418H11TEUS ...................................................................................... 759

36. Call Distribution - Attendant Groups

ENTP0418P12TEUS ...................................................................................... 763
ENTP0416C02TEUS ...................................................................................... 769
ENTP0416M01TEUS ...................................................................................... 773

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent i

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

37. Call Distribution – Attendants sets

ENTP0418P13TEUS....................................................................................... 781
ENTP0415C13TEUS....................................................................................... 787
ENTP0415P02TEUS....................................................................................... 793
ENTP0415P04TEUS....................................................................................... 807
ENTP0415C03TEUS....................................................................................... 813
ENTP0882P02TEUS....................................................................................... 819
ENTP0882C02TEUS....................................................................................... 823
ENTP0415M01TEUS ...................................................................................... 831
ENTP0415H03TEUS ...................................................................................... 839

38. DECT - IBS

ENTP0419P01TEUS....................................................................................... 843
ENTP0419C01TEUS....................................................................................... 851
ENTP0419C04TEUS....................................................................................... 855
ENTP0419M01TEUS ...................................................................................... 859
ENTP0419H02TEUS ...................................................................................... 871

39. Direct Speed Dialing

ENTP0408P01TEUS....................................................................................... 875
ENTP0408C04TEUS....................................................................................... 883
ENTP0408M01TEUS ...................................................................................... 887
ENTP0408H01TEUS ...................................................................................... 891

40. Speed Dialing by range

ENTP0408P02TEUS....................................................................................... 895
ENTP0408C03TEUS....................................................................................... 901
ENTP0408H02TEUS ...................................................................................... 907

41. Alcatel-Lucent OmniMessage 4645

ENTP0432P01TEUS....................................................................................... 911
ENTP0432C01TEUS....................................................................................... 927
ENTP0432C02TEUS....................................................................................... 939
ENTP0432M01TEUS ...................................................................................... 943
ENTP0432H01TEUS ...................................................................................... 951

42. MOXA V24/IP Box

ENTP0444P01TEUS....................................................................................... 955
ENTP0444C01TEUS....................................................................................... 963
ENTP0444M01TEUS ...................................................................................... 969
ENTP0444H01TEUS ...................................................................................... 981

43. Database Save & Restore

ENTP0411P04TEUS....................................................................................... 985
ENTP0411C02TEUS....................................................................................... 989
ENTP0411H02TEUS ...................................................................................... 995

ii All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

44. RMA Solutions & System Messages

ENTP0431P01TEUS ...................................................................................... 999
ENTP0431P06TEUS ..................................................................................... 1009
ENTP0431P07TEUS ..................................................................................... 1021
ENTP0431P08TEUS ..................................................................................... 1031
ENTP0421P01TEUS ..................................................................................... 1037
ENTP0431C06TEUS ..................................................................................... 1045
ENTP0431C08TEUS ..................................................................................... 1055
ENTP0431H08TEUS ..................................................................................... 1059

45. Appendix A – Reflexes & e-Reflexes

ENTP0403P06TEUS ..................................................................................... 1063
ENTP0403C07TEUS ..................................................................................... 1077
ENTP0403M01TEUS ..................................................................................... 1081

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent iii

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

iv All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

FEEDBACK SHEET
In order to improve the quality of the documentation, please report any errors found by
returning this sheet to the address below.

CHAPTER PAGE DESCRIPTION

Please return this sheet to:

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent v

Alcatel-Lucent OmniPCX Enterprise R9.0
Starter Pack Enterprise
TOC.doc

vi All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

Alcatel-Lucent OmniPCX Enterprise

Groups - Overview

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVES

To describe Pick-up groups

To describe Hunting groups

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

697
Groups
General Overview

The Alcatel-Lucent OmniPCX Enterprise provides two different types of groups

The first one is the Pick-up Group

Used to pick up calls from a set belonging on the same Pick-up group by using a
prefix

The second one is the Hunting Group (or PCX)

Used to reach several sets by dialing an unique number

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

698
“Pick-up” Groups
Generalities

“Call pick-up” enables an user to answer (redirect) an incoming call of an

another set on his own set by dialing a prefix

1 CALL

3 In conversation

Dialing of the Call Pick-up prefix

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

699
“Pick-Up” Groups
Specificities

There are two types of call Pick-Up prefixes:

Group call pick-up:

Enables an user to pick-up an incoming call to a set belonging to the same pick-up
group
To pick-up the call, simply dial the group call pick-up prefix (no need to dial an
extension number)

Direct call pick-up (does not require a “pick-up group”)

This prefix has to be followed by the directory number of the set or group of sets
being called (The directory number can be a local number or another network node
number)

The Call pick-up is possible if the pick-up set is authorized to use this service and if the
called set is not protected against call pick-up. This depends on the subscription parameters
of the users

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

700
Hunting Groups
Generalities

A Hunting group combines several extensions on the same number

A call to this number is distributed to the extensions in the group according to

the search type

Three search (distribution) types

Sequential

Circular

Parallel

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

701
Hunting Groups
Call distribution

Sequential
The call is always routed to the “head” extension of the group
If this extension is not free, the following(1) first free one is rung

Circular
Each extension is rung in the order of the list(1)
The system rings the next free extension after the one previously called

Parallel
The extensions in the group are rung simultaneously
Restriction: the extensions in the group can not be multi-line extensions

All Rights Reserved © 2008, Alcatel-Lucent 6

(1) The position of an extension in the list only depends on the order of the extension assignment in the group (the first is number
“N”, the following one is “N+1”…)

Remark:
In case of Sequential / Circular hunting group, a specific (configurable) system timer is used to reroute a call inside the group in
case of no answer: Timer “36”

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

702
Hunting Groups
Specific parameters

A Hunting group has its own

Connection Cos
Public Network COS
Entity

As soon as an extension is logged in the group (default status), it takes those

parameters
It can therefore have a different behavior
If the extension is logged out from the hunting group, it takes up its own
parameters

Voice mail(1) directory number / Secret Code

This voice mailbox is especially used to forward the “Hunting group” to this
mailbox -a prefix use is required- (usually used in case of empty group)

All Rights Reserved © 2008, Alcatel-Lucent 7

(1) The language of the Mailbox can also be configured

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

703
Hunting Groups
Specific parameters (Cont’)

Overflow directory number

When configured, a call to the hunting group can overflow to this number
when:
The hunting group has no remaining active extension (possible under conditions)
The hunting group is busy (with also a full Camp on queue)

This directory number can be:

An extension (local or network user)
An other Hunting Group
An attendant extension

All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

704
Hunting Groups
Features

Number of allowed waiting calls

% on number of “active” extensions in the Hunting Group

Internal group pick-up

Right to pick up private call: y/n
Allows to pick up a private call
Prefix «Agent processing group call pick up»

Private call

Call pick up

All Rights Reserved © 2008, Alcatel-Lucent 9

Number of allowed waiting calls.

An incoming call waiting on the hunting group is authorized as long as the number of calls waiting does not exceed a
percentage defined below:

Number of waiting calls authorized

× 100 = Waiting percentage (in %)
Number of active sets in the hunting group

The waiting percentage can be from 0 to 1000 %

Example: A group of 3 sets, with 9 waiting calls authorized, the waiting percentage will be 300 %.

Internal group call pick-up:

Without knowing the number of the ringing extension (in the same hunting group), you can pick up the call using only the
prefix: group call pick-up. But this prefix use will pick-up only calls destined to the group directory number. If it is a private
call, the call can not picked up with this prefix

Agent processing group call pick up: only for hunting group extensions
In a hunting group, when an extension rings, whatever the type of the call (private or hunting group call), the call can be
picked up from an other extension (belonging to the same hunting group) using the “Agent processing group call pick up”
prefix.
Remarks:
Prefix creation: General features / Agent processing group call pick up
The Service has to be authorized via the extension Phone features COS

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

705
Hunting Groups
Features (cont’)

Call pick up by external: y/n

Allows to pick up a Hunting group call from an external extension of the

Hunting Group
«Direct call pick up» prefix + Hunting group directory number

Hunting group call

1 3

Call pick up

All Rights Reserved © 2008, Alcatel-Lucent 10

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

706
Hunting Groups
Group (cont’)

Internal calls distribution

Internal
calls

Group directory N°

Overflow N° if
yes
Group empty supported, otherwise
call not possible
no
Overflow N° if
no Queue full yes
Extensions free supported, otherwise
call not possible
yes no

Extensions ring Hold/call back possible

by caller action

All Rights Reserved © 2008, Alcatel-Lucent 11

The extensions are rung for an infinite period according to the type of search
If there is no answer from a free extension, the call is routed to another extension in the group when the rotation timer expires:
“Timer 36” (for cyclical or sequential hunting)

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

707
Hunting Groups
Group (cont’)

External incoming calls distribution

External
call

Group directory N°
Overflow N° if supported,
yes otherwise distributed
Group empty
according to entity’s CDT
no
yes
no Queue full
Extensions
free
yes no

Extensions ring then Ringing tone then overflow to

overflow to the entity’s CDT the entity’s CDT after trunk
after trunk overflow timer overflow timer

All Rights Reserved © 2008, Alcatel-Lucent 12

If there is no answer from a free extension, the call is routed to another extension in the group when the rotation timer expires:
“Timer 36” (for circular or sequential hunting)

If no one has answered the call after the trunk overflow timer, the caller is rerouted to the entity’s CDT.

A queued call is routed to an extension in the group provided, it becomes free before the end of the trunk overflow timer

Note:
The Public Network COS assigned to the group can change the distribution:
- DID/BCA/LIA overflow on waiting: yes -> same arrangement (overflow to entity's CDT after trunk overflow timer)
no -> a waiting call never overflows
- DID/BCA/LIA overflow on all busy: yes -> same arrangement (overflow if queue full)
no -> if the queue is full, the caller receives the busy tone

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

708
Hunting Groups
User Functionalities

The extension of the Hunting Group can

Exit the group by dialing a prefix

Enter the group by dialing a other prefix

To do so, the access to these features has to be authorized by the user Phone
feature COS

Even all the users of the group have the right to exit the group, a Hunting
Group parameter can forbid the last active user to exit the group
Unavailable authorized: No

All Rights Reserved © 2008, Alcatel-Lucent 13

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

709
Hunting Groups
Multi-line sets

The Multi-line extensions are available only for sequential and circular Hunting
Groups

Two possible options:

The extension is considered busy if at least one line is busy

If a multi-line set is busy, then a hunting group call overflows to the next free
extension

The extension is considered busy if all its lines are busy

The call hunting group calls are presented on the extension multi-line keys as long
as it remains a free key.
The extension is considered busy when all its lines are busy, therefore the following
calls will be presented on the next extension of the list

All Rights Reserved © 2008, Alcatel-Lucent 14

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

710
Hunting Groups
Limits and restrictions

200 hunting groups per nodes

40 extensions in an hunting group (analog or digital)

5 DECT/PWT sets per parallel hunting group

A set can not belong to several Hunting groups

No multi-line set in a parallel group

All Rights Reserved © 2008, Alcatel-Lucent 15

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

711
All Rights Reserved © 2008, Alcatel-Lucent 16

Alcatel-Lucent OmniPCX Enterprise – Groups - Overview

Ref. ENTP0405P03TEUS Issue 02

712
Alcatel-Lucent OmniPCX Enterprise
Hunting group

PROCEDURE

OBJECTIVE

- To learn how to manage a Hunting group

OVERVIEW
A Hunting group is a method to assign the same directory number several extension. There are
three types of searches that are used to define how the group will respond to calls.
In this procedure you will create a hunt group that will search the group of sets in a cyclical
mode (round-robin).

Issue 02 Ref. ENTP0405C01TEUS.doc P. 1

PROCEDURE

1. Create the Hunting group add assign the corresponding extensions

1.1. Assignment of the extensions directly at the group creation

Application Configuration Tab PCX

Path / Groups / Hunting Group
Action Create
Tab All
Parameters Directory Number: 31700
Directory Name: Support
Type of Hunt Group: PCX Hunt group
Circular Search Type: Circular
Release After Timer: True
Overflow Directory Number: 31010 (for example)
Authorized Camp on Calls%: 50 (default value)
Connection COS: 0
Public Network COS: 2
Unavailable Authorized: True/false
Dir.No Assigned to the group: 31000 (Note)
Entity Number: 1
Voice mail number:
Voice mail Secret code:
Voice mail Language:
Pickup private call: True/false
External pickup call: True/false
Action Click on “ ” to valid

Note: A user can only belong to one Hunting group

To add several extensions in the hunting group, use the “left click”, then “right
click” in the “Dir.No Assigned to the group” parameter box, then give the
following extension directory number, etc

P. 2 Ref. ENTP0405C01TEUS.doc Issue 02

1.2. The extensions can also be assigned to a group after the group creation

Application Configuration Tab PCX

Path / Users
Tab Facilities
Object 31003 (for example)
Parameters Hunt group Dir Number: 31700
Action Click on “ ” to valid

2. User features around the Hunting group

2.1. Creation of the prefix to exit the group

Application Configuration Tab PCX

Path / Translator / Prefix Plan
Action Create
Parameters Number: 480 (for example)
Prefix Meaning: Set Features
Station features: Sta. Group Exit
Action Click on “ ” to valid

2.2. Creation of the prefix to enter back to the group

Application Configuration Tab PCX

Path / Translator / Prefix Plan
Action Create
Parameters Number: 481 (for example)
Prefix Meaning: Set Features
Station features: Sta. Group Entry
Action Click on “ ” to valid

Note: Both prefixes can already exist according to the default country database

Issue 02 Ref. ENTP0405C01TEUS.doc P. 3

2.3. User rights

Application Configuration Tab PCX

Path / Class of Services / Phone feature COS
Object Phone feature COS: 0 (for example)
Parameters Set features Sta. Group exit: 1
Set features Sta. Group entry: 1
Action Click on “ ” to valid

P. 4 Ref. ENTP0405C01TEUS.doc Issue 02

PROCEDURE

OBJECTIVE

- To learn how to manage a Pick-Up Group

OVERVIEW
The Call Pick-up group is a group of extensions that are authorized to pick up calls to one of the
group’s extensions, via a prefix number, during the ringing phase

Issue 02 Ref. ENTP0405C02TEUS.doc P. 1

PROCEDURE

1. Creation of a Pick Up group / user assignment

Application Configuration Tab PCX

Path / Users
Tab Facilities
Parameters Pick up group name: PickUp-1
Action Click on “ ” to valid

Note: A subscriber can only belong to one pick-up group. If some Pick Up groups are
already defined in the system, it is possible to select the name of the group in the
existing list (via the user parameters)

1.1. After the Pickup group creation, it is possible to see it in the “Group” parameters

Application Configuration Tab PCX

Path / Groups / Pick Up group
Action Open / Close
Parameter Pickup Group Name: PickUp-1

2. Use of the feature “Group Call pick up”

2.1. Creation of the “Group Call pick up” prefix

Application Configuration Tab PCX

Path / Translator / Prefix Plan
Action Create
Parameters Number: 56 (for example)
Prefix Meaning: General Features
General features: Group Call Pickup
Action Click on “ ” to valid

Note: It is possible that this prefix already exist according to the default country
database

P. 2 Ref. ENTP0405C02TEUS.doc Issue 02

2.2. User rights

Application Configuration Tab PCX

Path / Class of Services / Phone feature COS
Object Phone feature COS: 0 (for example)
Parameters General Services Group call pickup: 1
Action Click on “ ” to valid

Issue 02 Ref. ENTP0405C02TEUS.doc P. 3

P. 4 Ref. ENTP0405C02TEUS.doc Issue 02

Groups - Maintenance

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVES

To maintain pick up group

To maintain hunt group

Alcatel-Lucent OmniPCX Enterprise – Groups - Maintenance

Ref. ENTP0405M01TEUS Issue 02

721
Groups
Pick up groups

The “zdpost” command can be used to check if an extension belongs to a Call

Pick Up group

Example of an extension that does not belong to any Pick Up group

zdpost d 31010 |grep -i pickup_id

pickup_id = -1

Example of an extension that belongs to a Pick Up group

zdpost d 31000 |grep -i pickup_id

pickup_id = 0

This extension belongs to the first created Pick Up group (id = 0)

To check the corresponding name, the configuration has to be checked

The “Grid Edit” can be useful to check such a parameter

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Groups - Maintenance

Ref. ENTP0405M01TEUS Issue 02

722
Groups
Hunting Group

“pbxstat” command

pbxstat -f d 31700

Sun Dec 30 19:37:02 CET 2007

* mcduapp 31700 Num Group 0 pbx_type PBX_LOCAL -- *

nu_tete 1 mcdu de tete : 31000
max_att 50%
idx_acc 255 First extension of the group
modcycle CYCLIC
traiatt 0 debor 0
autoret 1 pooccgrp 0 grp_prio 0 abca_blf 0
nbppgr 3 nbpoeff 3 idx_rasgo 0
grcatptt 2 grctconx 0 set_categ 0 entity_nr 1
idx_mevo 255
mcdudeb
station_grp_name Support
PBX_RoutingFlag 0
pickup_no_pbx 0
etat_groupe ABCA_SG_PART_FREE
PBX_preemptable 0
tab_pres[1..40]
nelgr: 0 in:31000 etat_poste ABCA_BUSY
nelgr: 3 in:31002 etat_poste ABCA_HW_OOS
nelgr: 1 in:31200 etat_poste ABCA_IDLE

All Rights Reserved © 2008, Alcatel-Lucent 3

Available command options

[-f] Details
[d numan] PBX directory number
[n nu_group] PBX logical number
[all] All PBXs

Status of the Group

etat_groupe: - ABCA_SG _FREE All extensions are free
- ABCA_SG _TOT_BUSY All extensions are busy
- ABCA_SG _PART_FREE Some extensions are free
- ABCA_SG_OOS All the extensions are Out Of Service

Status the assigned extension:

etat_poste: ABCA_BUSY The extension is busy
ABCA_IDLE The extension is free
ABCA_HW_OOS The extension is Out Of Service (HW=Hardware)

Alcatel-Lucent OmniPCX Enterprise – Groups - Maintenance

Ref. ENTP0405M01TEUS Issue 02

723
Groups
Hunting Group (Con’t)

The “supgpbx” tool allows to check in real time the status of the system
Hunting groups

+------------------------------------------------------------------------------+
| |
| Hunting group supervisor - alu-brest-a |
| --------------------------------------- |
| |
| |
| |
| 1: Group's sets state Selection of a group |
| |
| 2: State of all the hunting groups of the node All groups |
| |
| 3: Group statistics Equiv “pbxstat” |
| |
| 4: Help |
| Tool customization |
| 5: Options |
| |
| q: Quit the hunting group supervisor |
| |
| |
| |
| |
+------------------------------------------------------------------------------+

All Rights Reserved © 2008, Alcatel-Lucent 4

Example of a group status:

Group's sets state 31700

Group's state: SG_PART_FREE

+---------------------------------------------------------------------+
MCDU: |31000 31002 31200 |
State: |*i|.......|BUSY i|.......|HW_O i|.......|IDLE |
| |
...
+---------------------------------------------------------------------+
ENTER:Back SPACE:Waiting queue

Example of all the system Hunting groups information:

State of all the hunting groups of the node

Alcatel-Lucent OmniPCX Enterprise – Groups - Maintenance

Ref. ENTP0405M01TEUS Issue 02

724
Groups
Hunting Group (Con’t)

To list the available Hunting groups of the system: “ednump”

1 - dir -> Directory_number

2 - mean = Hunting_Group -> Meaning

==========================
enter criteria or command: go
==========================

30/12/07 EDNUMP V. 4.00 Page: 1

+-----------------+-------------------------------------------------+
|dir |mean |
+-----------------+-------------------------------------------------+
|31700 |Hunting_Group |
+-----------------+-------------------------------------------------+

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Groups - Maintenance

Ref. ENTP0405M01TEUS Issue 02

725
Groups
Hunting Group (Con’t)

To check the subscriber belonging to a Hunting group: “edsbr”

1 - dir -> Directory number

2 - hunt -> Hunting Group
3 - fc -> Facility Category

==========================
enter criteria or command:go
==========================

30/12/07 EDSBR V. 4.00 Page: 1

+--------+--------+---+
|dir |hunt |fc |
+--------+--------+---+
|31000 |31700 | 0|
|31002 |31700 | 0|
|31003 | | 1|
|31010 | | 2|
|31100 | | 1|
|31200 |31700 | 0|
+--------+--------+---+

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Groups - Maintenance

Ref. ENTP0405M01TEUS Issue 02

726
Alcatel-Lucent OmniPCX Enterprise
Pick Up / Hunting Groups

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to create call pick-up and hunt groups

MANAGEMENT

1. Call pick-up groups

1.1. In order to simplify the configuration, assign the same Phone features COS to all the
extensions used in the following exercises

1.2. Create a pick-up group called ‘Training’ with the sets : 3x000,3x001, 3X011
(where “x”=node index)

1.3. Features around the Call Pickup group

(NB: Choose free directories numbers in the dialing plan)
1.3.1. Create the “group call pickup” prefix
1.3.2. Create the “direct call pickup” prefix
1.3.3. Create the “agent processing group call pickup” prefix
1.3.4. Check the Phones features COS of the users in order to
- Allow the prefixes use
- Disable the protection rights against the direct call pick up
1.3.5. Test the right functioning of the configuration

Issue 02 Ref. ENTP0405H02TEUS.doc HO. 1

2. Hunting groups

2.1. Create a circular hunt group 3x700 with the sets : 3x004, 3x001, 3x002
(where “x”=node index)

2.2. From an extension that does not belong to this group, test the right functioning of
the circular group

2.3. Modify the group type search to sequential

2.4. From an extension that does not belong to this group, test the right functioning of
the sequential group

2.5. Check the Group status with the available maintenance tools (during the different
tests)

2.6. Features around the Call Pickup group

2.6.1. Create the “sta.group exit “ prefix
2.6.2. Create the “sta.group entry “ prefix
2.6.3. Check the Phones features COS of the users in order to allow the prefixes
use
2.6.4. Test both prefixes
2.6.5. When the 3 stations are withdrawn, the calls must be presented to the set
3x003, modify the Hunting Group configuration to meet this requirement

HO. 2 Ref. ENTP0405H02TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

729
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

730
Alcatel-Lucent OmniPCX Enterprise

Call Distribution

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the “Call Distribution” feature

Alcatel-Lucent OmniPCX Enterprise – Call Distribution

Ref. ENTP0418P10TEUS Issue 02

731
Calls distribution
Generalities

Calling an unique number, the “Call Distribution” feature allows to route a call
towards a specific “function” or “service”

This final destination can be different according to different elements:

The origin of the caller
The initial called number
The system status (working hours, night mode..)
The status of the potential stations used in the routing process

Usually, this feature is used to reach an attendant

Of the installation
Of a department

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Call Distribution

Ref. ENTP0418P10TEUS Issue 02

732
Calls distribution
Call distribution elements

Involved elements
Can be linked to:
Call Distribution Table (CDT) - An Entity
Day Night Mode1 Mode2 - An Attendant group
--------------------- Routing 1 -------------------- - A dedicated Attendant
--------------------- Routing 2 --------------------
--------------------- Routing 3 -------------------- Can be accessed by a prefix:
Overflow routing number - Entity call
- Attendant call
- Attendant group call
A CDT can contain: - Individual attendant call
- Directory numbers(1) (mono/multi-line set)
- Attendant set physical number Prefix Corresponding CDT
- Attendant group physical number
- PBX group Entity Call CDT of the Entity pointed by the prefix
- Speed dialing number Attendant Call CDT of the Entity of the calling user
- Voice guide
- Automated attendant Attendant Group Call CDT of the Attendant Group
- CCd agent Individual Attendant Call CDT of the corresponding Attendant

All Rights Reserved © 2008, Alcatel-Lucent 3

(1) If a set is used as “Overflow routing number”, it has to be a mono-line extension

Alcatel-Lucent OmniPCX Enterprise – Call Distribution

Ref. ENTP0418P10TEUS Issue 02

733
Calls distribution
Call distribution Table (day, night …)

Four different “call distribution” status are associated to this table

Day = working hours
Nights = non working hours
Mode 1 = can be lunch time for example
Mode 2 = specific condition
Each Functioning status can correspond to a specific kind of routing

For each status, three specific (successive) “overflow numbers” are possible

A fourth overflow number is common to the four status

The forth overflow is commonly called “night forwarding number”

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Call Distribution

Ref. ENTP0418P10TEUS Issue 02

734
Calls distribution
Call distribution Table (day, night …Con’t)

This call distribution status can be given by the:

Entity(ies)
Attendant(s)
Attendant group(s)

The Entity “call distribution” status can change:

Automatically(1), by using the “changeover-time” management
Depending on the corresponding Attend Group Manager(2) (if defined)

The status of an Attendant Group depends on the status of its Attendant(s)(3)

The status of the attendant are: Day (plugged), Night (unplugged)

All Rights Reserved © 2008, Alcatel-Lucent 5

(1) The management of the changeover-time allows to link some periods to a status (4 configurable changeover)
Example:

From 8h to 12: Day

From 12h to 13h30 Mode1
From 13h30 to 18h Day
From 18h to 24h00 Night

Other option:
It is also possible to give the mode: “Attendant Group” (to do that, an Attendant Group Manager has to be associated to the
Entity)
During the period corresponding to this status, the Entity mode follows the Attendant Group status (allowing more flexibility)
Further more, an Attendant of this group, having the rights, can modify the status of this Entity manually

(2) Each Entity can have its own Attendant Group Manager. Its aim is to force the Entity Call distribution status to follow the
Attendant group ones
An attendant, having the rights of modification, can modify the status of the Entity manually, or automatically the Entity Call
distribution status follows the Attendant Group status

(3) If the last Attendant (in service) of an Attendant Group switches in night mode, automatically, the Attendant Group switches
in night status

Alcatel-Lucent OmniPCX Enterprise – Call Distribution

Ref. ENTP0418P10TEUS Issue 02

735
Calls distribution
Call Routing: mechanism

To route the call, the system has to identify the “distribution status” of the
selected CDT

According to the distribution status, the call is routed towards the right routing
column

First of all, the call is routed towards the first routing number

In case of no answer or busy status of the first routing number, the call
overflows to the second routing number

In case of no answer or busy status of the second routing number, the call
overflows to the third routing number

In case of no answer or busy status of the third routing number, the call
overflows to the “Overflow routing number”

All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Call Distribution

Ref. ENTP0418P10TEUS Issue 02

736
Calls distribution
Call Routing: mechanism example

CDT
Selection(1)
e.g. “Day”

Distribution
Status?
Calls Distribution Table
Day Night Mode1 Mode2

Attendant Group ------- Routing 1 --------------------

No answer/ Busy
Attendant ------- Routing 2 --------------------
No answer/ Busy
--------------------- Routing 3 --------------------
No answer/ Busy Overflow routing number

A call routing overflows from a Routing number to the following one at the of
system timer “76” / Incoming Trunk timer(2) in case of “No answer/Busy
status(3)”

All Rights Reserved © 2008, Alcatel-Lucent 7

(1) The CDT selection is realized by:

• The use of a prefix (Entity call prefix, Attendant group prefix, Individual Attendant prefix, Attendant prefix)
• The system in case of “unallocated number” for an incoming call (in this case, the CDT of the incoming trunk group is
used)
• The system in case of “no answer” on a terminal in case of external incoming call (after the incoming trunk timer). The
selected CDT is the entity of the called party

(2) This Trunk timer is used only for the first Forwarding !
The incoming Trunk timer depends on the Trunk group Type. Each Trunk group type uses a Trunk COS
This Trunk COS (External Services) defines a timer overflow (on No Answer/Waiting)

(3) A call is presented to the selected extension (Routing number) for a specific duration (Timer 76)
“Busy status”:
• The routing number corresponds to an Attendant physical number or Attendant group physical number, if the selected
extension is in communication (busy) the call is queued (maximum queuing duration= Timer 76)
• The routing number is a classical extension, in that case the call directly overflows to the following Routing number

Alcatel-Lucent OmniPCX Enterprise – Call Distribution

Ref. ENTP0418P10TEUS Issue 02

737
All Rights Reserved © 2008, Alcatel-Lucent 8

Alcatel-Lucent OmniPCX Enterprise – Call Distribution

Ref. ENTP0418P10TEUS Issue 02

738
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

739
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

740
Alcatel-Lucent OmniPCX Enterprise

Call Distribution - Entity

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Call Distribution specificities for Entity

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entity

Ref. ENTP0418P11TEUS Issue 02

741
Call Distribution - Entity
Generalities

Most of the time an Entity corresponds to a Company or department

A specific number is used to reach the CDT of the corresponding Entity

It is the “Entity Call” prefix
It can be a “DDI” number for external incoming calls

The CDT of the Entity can also be used to ensure the routing of an incoming
public call
If the System is not able to locate the called party, the call overflows to the
CDT of the corresponding incoming trunk group

Each Entity has its own changeover time configuration

(Day, Night , Mode1, Mode 2) (1)

All Rights Reserved © 2008, Alcatel-Lucent 2

(1) For each Call distribution status, 3 different routing numbers can be managed. A common Overflow number can be used as a
forth routing number

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entity

Ref. ENTP0418P11TEUS Issue 02

742
Call Distribution - Entity
Changeover time

According to the changeover time definition, the Entity switches automatically

from a status to an other

This feature allows to split a day in 4 different periods (1)

Each period corresponds to a specific status of the company/department

Opening hours, Midday break, Night hours…
To each period, the starting time and the corresponding call distribution
status have to be defined (Day, Night ..)
To allow more flexibility, it is also possible for the Entity to follow the status of an
Attendant group (next page)

It is possible to manage separately:

“Incoming calls changeover time”, which modifies (according to the CDT
management) the routing of the incoming calls (local/external)
“Outgoing calls changeover time”, which modifies the behavior on outgoing
calls: “barring rules” & “public access Class of Service”

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entity

Ref. ENTP0418P11TEUS Issue 02

743
Call Distribution – Entity
Optional attendant group manager

This attendant group number has two main functions:

The Entity status (day, night,…) follows the associated attendant group
status if in the “changeover time” it is notified “Attendant group”

The Attendant extensions which have the right, and belonging to this
Attendant group, can manage (modify) the elements associated to this
Entity:
Traffic overflow
Entity routing numbers (CDT)
Entity state (day, night, mode 1, mode 2), “force a state”
Entity changeover time “modify the switching time between states”
Access to the speed dialing numbers by the ranges
Station and directory number

All Rights Reserved © 2008, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entity

Ref. ENTP0418P11TEUS Issue 02

744
Call Distribution - Entity
Optional Traffic overflow - Miscellaneous

According to this optional configuration field, it is possible to overflow to an

other Attendant (same node): “Mutual help”
Only from the moment where the waiting queue threshold has been reached
Defined in the Attendant Group parameters
If the call is routed to an Attendant/Attendant Group physical number in the
CDT
Only upon an Attendant manual request (via the “Service” menu)

A voice mail box can be defined

It is used when the Attendant request to record a conversation
This voicemail box is common to all the attendant sharing this Entity

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entity

Ref. ENTP0418P11TEUS Issue 02

745
All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entity

Ref. ENTP0418P11TEUS Issue 02

746
Alcatel-Lucent OmniPCX Enterprise
Call Distribution - Entity

PROCEDURE

OBJECTIVE

- To learn how to configure the Entity object for the Call Distribution feature

OVERVIEW
The Entity Object is used in several situations
The Call Distribution is one of the main functioning aim of this object. For this feature to
elements have to be configured:

- The Call Distribution Table

- The Changeover periods

This procedure focuses only the Entity parameters involved in the Call Distribution feature

Issue 02 Ref. ENTP0418C11TEUS.doc P. 1

PROCEDURE

1. Call Distribution Table & Main Entity parameters

Application Configuration Tab PCX

Path / Entities
Object “1” Entity “1” for example
Parameters Attendant Group Manager: 0 (e.g.; -1=No manager group)
Priority: Yes/No
Traffic Overflow: Disable/Allowed with no control
Voice Mailbox No. for Attendant:
Call Distribution:
Overflow Routing No.: 31010
Forwarding on routing: Yes/No
1rst Night Routing:
2nd Night Routing:
3rd Night Routing:
1rst Day Routing: A900 (e.g. Attendant group No.)
2nd Day Routing:
3rd Day Routing:
1rst Mode1 Routing: B9000 (e.g. Attend Sets No.)
2nd Mode1 Routing: B9001(e.g. Attend Sets No.)
3rd Mode1 Routing:
1rst Mode2 Routing:
2nd Mode2 Routing:
3rd Mode2 Routing:
Calls Priority
Normal Public TrK grp Entity: 6
…
Voice Guides
Waiting Guide: 2
Attendant Waiting Guide: 110
Action Click on “ ” to valid

Note: Except the Entities “O” and “1”, If some other Entities have to be used, they have
to be created

P. 2 Ref. ENTP0418C11TEUS.doc Issue 02

Note: Without any “Manager Attendant group”, to used Day, Mode1 and Mode2 status,
the Switchover periods have to be configured. With a “Manager Attendant group”,
the Entity status follows by default the Group status
Priority:
– YES: The calls from trunk groups of type NDID, Charging DID, T0, T2, DPNSS,
DASS2 of this entity are declared priority : they go immediately into the
PRIORITY state
– NO: These calls go into PRIORITY after 30s (standard state)
Traffic overflow: this configuration field allows to have a different behavior for
the Entity calls than the Attendant Manager Group behavior (even if the waiting
queue threshold is reached, the entity calls can not overflow event the other calls
do)
Voice Mailbox No. for Attendant: this mail box is used for the attendant call
recording
Calls priority: default values are given to different types of call. It allows to make
a type of call prior to an other one in the call waiting queue
Waiting guide: Tone or Voice guide listened by some how has been put on hold
Attendant Waiting Guide: Voice guide listened in case External incoming Entity
call [This voice guide is listened only if the “System Timer 102”is different than
“0” (default value)]

Issue 02 Ref. ENTP0418C11TEUS.doc P. 3

2. Changeover periods

2.1. Changeover state for Incoming calls

Application Configuration Tab PCX

Path / Entities
Object “1” (Entity “1” for example)
Sub-Path …/ Entity Incoming State Hours
Parameters Day + Monday/Tuesday/Wednesday …
Changeover1
Hour: 8
Minutes: 30
Status: Day
Changeover2
Hour: 12
Minutes: 00
Status: Mode1
Changeover3
Hour: 13
Minutes: 00
Status: Day
Changeover4
Hour: 17
Minutes: 00
Status: Attendant Group
Action Click on “ ” to valid

Note: To use the “Attendant Group” status, a “Manager Attendant Group” has to be
configured in main Entity parameters
After the configuration, the Changeover states will be really taken into account
after the first changeover state realized after the configuration
In this example, if the configuration has been done at 12h30, the Entity will really
activates the Changeover states at 13h00 (first changeover after the
configuration)

P. 4 Ref. ENTP0418C11TEUS.doc Issue 02

2.2. Changeover state for Outgoing calls

Application Configuration Tab PCX

Path / Entities
Object “1” (Entity “1” for example)
Sub-Path …/ Entity Outgoing State Hours
Parameters Day + Monday/Tuesday/Wednesday …
Changeover1
Hour: 8
Minutes: 30
Status: Day
Changeover2
Hour: 12
Minutes: 00
Status: Mode1
Changeover3
Hour: 13
Minutes: 00
Status: Day
Changeover4
Hour: 17
Minutes: 00
Status: Attendant Group
Action Click on “ ” to valid

Note: The Outgoing /Incoming Changeover states can be configured identically or

differently according to the needs

Issue 02 Ref. ENTP0418C11TEUS.doc P. 5

3. Prefixes to access to the Entity Call Distribution Table

3.1. Prefix used to access to a specific Entity CDT (mainly used in case of external
incoming calls)

Application Configuration Tab PCX

Path / Translator / Prefix Plan
Action Create
Parameters Number: 31801 (e.g.)
Prefix Meaning: Entity Call
Prefix Information: 1 (Entity Id)
Action Click on “ ” to valid

Note: This prefix can either be used by external users (if it is a DID number) and also by
internal users

3.2. Prefix only available for the Internal users

Application Configuration Tab PCX

Path / Translator / Prefix Plan
Action Create
Parameters Number: 9
Prefix Meaning: Attendant Call
Action Click on “ ” to valid

Note: If a user dials this prefix, the call is routed to the corresponding user’s Entity CDT

P. 6 Ref. ENTP0418C11TEUS.doc Issue 02

Call Distribution - Entities

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To maintain the Entity Call Distribution routing feature

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entities

Ref. ENTP0418M01TEUS Issue 02

753
Entities
Call Routing Information

The maintenance command “entitystat” allows to display some parameters of

the Entity

Usage: entitystat <Entity Id> entitystat 1

Mon Jan 7 20:07:51 CET 2008

ENTITY_1
secret_ident : 0
outgoing_curr_state: SAMEASATTGP
incoming_curr_state: SAMEASATTGP
spv_party_type : 2
spv_party_nr : 0
own_spv_party_type : 2
own_spv_party_nr : 0
group_manager : 0
prioritary : 0
with_deb : 0
trunk group : 0
music : 2
nds :
Voice Mail attribut
vm_box :
password :
language : 1
vmail_id : 255
society_call_number:
centralised_service: 0
sn_queue_trunk_att : 0
sn_multi_spv_att : 0

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entities

Ref. ENTP0418M01TEUS Issue 02

754
Entities
Status Hours

The otpion “-b” of the command “entitystat” allows to display the changeover
periods (status hours)
entitystat 1 -b

Mon Jan 7 19:57:54 CET 2008

ENTITY_1
secret_ident : 0
outgoing_curr_state: SAMEASATTGP
incoming_curr_state: SAMEASATTGP
. . .
outgoing time table
sunday | 24:0->3 24: 0->3 24: 0->3 24: 0->4
monday | 8:30->1 12: 0->2 13: 0->1 17: 0->4
tuesday | 8:30->1 12: 0->2 13: 0->1 17: 0->4
wednesday | 8:30->1 12: 0->2 13: 0->1 17: 0->4
Id meaning:
thursday | 8:30->1 12: 0->2 13: 0->1 17: 0->4
friday | 8:30->1 12: 0->2 13: 0->1 17: 0->4 0= Night
saturday | 24:0->3 24: 0->3 24: 0->3 24: 0->3
incoming time table
1= Day
sunday | 24:0->3 24: 0->3 24: 0->3 24: 0->4 2= Mode1
monday | 8:30->1 12: 0->2 13: 0->1 17: 0->4 3= Mode2
tuesday | 8:30->1 12: 0->2 13: 0->1 17: 0->4
wednesday | 8:30->1 12: 0->2 13: 0->1 17: 0->4
4= Same As Group
thursday | 8:30->1 12: 0->2 13: 0->1 17: 0->4
friday | 8:30->1 12: 0->2 13: 0->1 17: 0->4
saturday | 24:0->3 24: 0->3 24: 0->3 24: 0->3

All Rights Reserved © 2008, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entities

Ref. ENTP0418M01TEUS Issue 02

755
Entities
Call Distribution table

The “cdtstat” maintenance command allows to display the Call Distribution

Table

Usage: cdtstat <identification No.> cdtstat 161 Entity 1

Mon Jan 7 20:17:26 CET 2008

CDT idx : 161

flg_deb_nuit : 0
state : Day
group : 0
poste_nuit : 31010

state NIGHT :
state DAY : A900
state FWD1 : B9000
state FWD2 :

state NIGHT :
state DAY :
state FWD1 : B9001
state FWD2 :

state NIGHT :
state DAY :
state FWD1 :
state FWD2 :

All Rights Reserved © 2008, Alcatel-Lucent 4

cdtstat command:
N° identification: why from 160 to 415 ?
The identification Numbers go from 0 to 415 i.e.,
80 attendant indexes: 0 to 79 re-indexed as n° identification 0 to 79
80 attendant group indexes: 0 to 79 re-indexed as n° identification 80 to 159
256 entity indexes: 0 to 255 re-indexed as n° identification 160 to 415

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entities

Ref. ENTP0418M01TEUS Issue 02

756
Entity
Entity Call prefix

The command “ednump” can list the system Entity Call prefixes

ednump

1 - dir -> Directory_number

2 - mean = Entity_Call -> Meaning

==========================
enter criteria or command: go
==========================

07/01/08 EDNUMP V. 4.00 Page : 1

+-----------------+------------------------------------------
|dir |mean
+-----------------+------------------------------------------
|31801 |Entity_Call
+-----------------+------------------------------------------

All Rights Reserved © 2008, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entities

Ref. ENTP0418M01TEUS Issue 02

757
All Rights Reserved © 2008, Alcatel-Lucent 6

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Entities

Ref. ENTP0418M01TEUS Issue 02

758
Alcatel-Lucent OmniPCX Enterprise
Call Distribution - Entity

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to configure the Entity Call Distribution Table and its environment

MANAGEMENT

1. Manage the Entity 1 CDT in order to meet the following requirement:

- In Day Status, the Attendant Group A900 (Manager Attendant group 1) has to be range
(This A900 Attendant group is made of two attendant sets B9000 & B9001)
- In Night Status, the calls will directly overflow to the night forwarding number: 3n010
(where n= System Index)
- In Mode1 status, only the Attendant B9001 has to be rang (this operator starts his/her
working day at 1:00 PM)

1.1. Manage the Entity Call prefix 3n801 to access to this CDT

1.2. Use the available maintenance commands to check the configuration and right
functioning of the CDT

2. Changeover State

2.1. By default what is the status of the Entity?

.......................................................................................................

Issue 02 Ref. ENTP0418H11TEUS.doc HO. 1

3. Manage the changeover states in order to meet the following requirement.

For both incoming and Outgoing calls (same behavior for all the days):
From 8AM to 1:00PM: “Day” status
From 1:00PM to 2:00PM : Same As Attendant Manager Group
From 2:00PM to 6:00PM: “Day” Status
And after 6:00PM, it has to be “Night” status

3.1. Between 1:00 PM and 2:00, the status can be either Day or Mode1
Only the Attendant B9000 has some configuration right around the Group parameters
3.1.1. According to this statement, how the Entity can switch to the state Mode1?
.............................................................................................
3.1.2. Do the corresponding configuration

3.2. Use the available maintenance commands to check the configuration and right
functioning of the changeover states

4. Manage a new Entity “2”

4.1. Do not configure any specific parameter

4.2. Assign this Entity to the Extension 3n100 (where n= System Index) (or any free
extension of the installation)

4.3. Manage the “Attendant Call Prefix: 9”

4.4. Set up some calls from some Entity 1 extensions and Entity 2 extension. What do you
notice?
.......................................................................................................

HO. 2 Ref. ENTP0418H11TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

761
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

762
Alcatel-Lucent OmniPCX Enterprise

Call Distribution – Attendant group

All Rights Reserved © 2008, Alcatel-Lucent 1

OBJECTIVE

To describe the Call Distribution specificities for Attendant Group

Alcatel-Lucent OmniPCX Enterprise – Call Distribution – Attendant group

Ref. ENTP0418P12TEUS Issue 02

763
Attendant Group
Generalities

An Attendant Group is defined by

A group Index
It is a unique system reference (even in network configuration)

A physical directory number

Used only in CDTs (the group CDT as well as other CDTs)
Routing 1, Routing 2, Routing 3
Usually, it is a directory number which can not be dialed directly by a user
e.g. A9000
When a call is routed to this particular number, by default (more details in next
page), all the Attendant of this corresponding group are rung

A Call Distribution Table

Optional “Attendant Group” prefix

Used to access to the Group CDT

All Rights Reserved © 2008, Alcatel-Lucent 2

Alcatel-Lucent OmniPCX Enterprise – Call Distribution – Attendant group

Ref. ENTP0418P12TEUS Issue 02

764
Attendant Group
Call presentation

By default, if a call is routed to an Attendant group, the call is routed in

parallel to all the Attendants of the group

A system parameter allows to change this default mode to

Statistic mode

A call routed to an Attendant group is presented to the Attendant having the

longest “idle time”

Routed Calls
Idle times counters:
- OP1: 10s
- OP2: 25s
OP2: 25s OP1: 10s
GROUP waiting queue:

-First Call :
-Second Call
-...

All Rights Reserved © 2008, Alcatel-Lucent 3

Remark

The system forces an Automatic changeover from statistical to parallel call presentation for a call when:
- Number of calls in waiting queue upper than nb of attendants in the group
- No free attendant in the group
- No free attendant with appropriate PCOT
- Attendants have at least one waiting call in personal waiting queue

(Individual Attendant calls are taken into account for “idle time” counter)

Alcatel-Lucent OmniPCX Enterprise – Call Distribution – Attendant group

Ref. ENTP0418P12TEUS Issue 02

765
Attendant Group
Traffic overflow

When configured(1), in case of traffic picks, it is possible to use a call routing

overflow from an Attendant group to an other

To do so, an overflow threshold has to be defined

call 4
Overflow
Threshold call 3
call 2 Call overflow
call 1

Mutual help
validated

(1) A “Traffic Overflow directory number” has to be managed (a specific overflow number can be defined per distribution status
(Day, night, mode1 & mode2)

Two possible cases

Case 1: “Attendant group call prefix use”

The overflow follows the Attendant group Overflow configuration (threshold, overflow numbers)

Case 2: “Entity call prefix use”

Even if the call is routed to an Attendant group, the overflow is available only under Entity authorization (Traffic overflow:
allowed)
The corresponding overflow number is taken from the Attendant Group itself

The mutual help (traffic overflow) has to be manually activated by an attendant (via the “Service” menu), in both cases

Alcatel-Lucent OmniPCX Enterprise – Call Distribution – Attendant group

Ref. ENTP0418P12TEUS Issue 02

766
Attendant Group
Status

The Attendant Group distribution status depends on its own attendant

extensions status
“In service”
At least one Attendant is idle or busy

Absent (1)

When the last Attendant of the group goes to “absent” mode, the group becomes
“absent”

Unplugged
When the last Attendant has been unplugged, the group becomes unplugged

The Call Distribution status is given either:

Automatically by the Attendant group position
“In service” = “Day”
“Unplugged” = “Night”

Manually by an attendant of the group if service is authorized

Day / Night / Mode 1 / Mode 2

(1) When an Attendant Group is seen as “Absent”, if a call is routed to its physical number in a CDT, automatically the call
overflows to the following Routing number in the CDT

To switch back to the “In service” mode, at least on Attendant has to switch back to “In service” mode pressing on
“Logon/Logoff” button

Alcatel-Lucent OmniPCX Enterprise – Call Distribution – Attendant group

Ref. ENTP0418P12TEUS Issue 02

Alcatel-Lucent OmniPCX Enterprise – Call Distribution – Attendant group

Ref. ENTP0418P12TEUS Issue 02

768
Alcatel-Lucent OmniPCX Enterprise
Attendant Group

PROCEDURE

OBJECTIVE

- To learn how to configure the Attendant group and its associated Call Distribution Table

OVERVIEW
The Attendant Group is a part of the Call Distribution feature
It is made of a Call Distribution Table an some Attendant extensions
An Attendant group prefix allows to access to the CDT

Issue 02 Ref. ENTP0416C02TEUS.doc P. 1

PROCEDURE

1. Attendant Group creation

Application Configuration Tab PCX

Path /Attendant/Attendants group
Action Creation
Parameters Physical Directory No.: A900
Attendant group Id: 0
Name: Main-group
Max. No. of Calls Bef. Overfl.: 5
Traffic Overflow Dir.No.
Traffic Overflow Night:
Traffic Overflow Day:
Traffic Overflow Mode 1
Traffic Overflow Mode2
Attached Attendants: (done via the Attendant Set configuration)
Action Click on “ ” to valid

Note: Maxi. No of Calls Before Overflow: allows to determine the threshold of the call
waiting queue from which the calls will overflow to an other
Group/Attendant/extension (the Overflow number depends on the Group Status
(Day/Night/Mode1/Mode2)

Note: As soon as the Attendant group is created, automatically its corresponding Call
Distribution Tale is also created (some modification can therefore realized)

P. 2 Ref. ENTP0416C02TEUS.doc Issue 02

2. Call Distribution Table

Application Configuration Tab PCX

Path / Attendant/ Attendant Group Call Distribution
Object 0 (Attendant Group Id)
Parameters Overflow Routing No.: 31010 (e.g.)
Forwarding on Routing: Yes/NO (refer to the Note)
Att.Status: Night
Routing 1:
Routing 2:
Routing 3:
Att.Status: Day
Routing 1: A900 (Own Physical number)
Routing 2:
Routing 3:
Att. Status: Mode1
Routing 1: B9000 (e.g.)
Routing 2:
Routing 3:
Att. Status: Mode2
Routing 1:
Routing 2:
Routing 3:
Action Click on “ ” to valid

Issue 02 Ref. ENTP0416C02TEUS.doc P. 3

3. Prefix to access to the Attendant Group “Call Distribution Table”

Application Configuration Tab PCX

Path / Translator / Prefix Plan
Action Create
Parameters Number: 31800
Prefix Meaning: Attendant Group Call
Prefix Information: 0 (Attendant Group Id)
Action Click on “ ” to valid

P. 4 Ref. ENTP0416C02TEUS.doc Issue 02

Attendant Group

OBJECTIVE

To maintain the Attendant Group

Alcatel-Lucent OmniPCX Enterprise – Attendant Group

Ref. ENTP0416M01TEUS Issue 02

773
Attendant Group
Status

The “grpopestat” maintenance command allows to check the group status of

the Attendant Groups

Usage: grpopestat <Id group>

Name Group Name

phys status Group position
log status Call distribution state
overload_prg Mutual help validated
gpe__overload Overflow underway ( yes ou no )
nb_ope_pres Nb of present attendant
nb_gpe_call Nb of calls waiting
max_gpe_call Overflow threshold
overflow Overflow physical directory n°
att_press Indexes of the Attendants present in this group
Entity_sup Entities where the Group is Attendant Group Manager

Alcatel-Lucent OmniPCX Enterprise – Attendant Group

Ref. ENTP0416M01TEUS Issue 02

774
Attendant Group
Status (example)

grpopestat 0

Mon Jan 7 17:13:10 CET 2008

Name : Main Grop

etat_phys : PRESENT
etat_phys_redundancy : NOT_CREATED
etat_log : DAY
overload_prg : 0
grp_overload : 0
nb_att_pres : 1
nb_grp_call : 0
max_grp_call : 5 The attendant index “0” & “1”
Overflow : belong to this Group “0”
att_pres :
( 0) |11000000|00000000|00000000|00000000|00000000|00000000|00000000|00000000
( 64) |00000000|00000000
entity_sup :
( 0) |00000000|00000000|00000000|00000000|00000000|00000000|00000000|00000000
( 64) |00000000|00000000|00000000|00000000|00000000|00000000|00000000|00000000
( 128) |00000000|00000000|00000000|00000000|00000000|00000000|00000000|00000000
...
( 896) |00000000|00000000|00000000|00000000|00000000|00000000|00000000|00000000
( 960) |00000000|00000000|00000000|00000000|00000000|0
ind_assistant : 0
att_assist_start_ringing : 20
att_assist_stop_ringing : 10
seuil_next_call : 6

Alcatel-Lucent OmniPCX Enterprise – Attendant Group

Ref. ENTP0416M01TEUS Issue 02

775
Attendant Group
Call Distribution Table

To display the configuration attendant group’s CDT, use the maintenance

command “cdtstat”
Corresponds to the
Usage: cdtstat <Index N°> cdtstat 80
Attendant Group 0
Mon Jan 7 17:33:19 CET 2008

CDT idx : 80
flg_deb_nuit : 1
State : DAY
Group : 0
poste_nuit :

state NIGHT :
state DAY : A900
state FWD1 :
state FWD2 :

state NIGHT :
state DAY :
state FWD1 :
state FWD2 :

cdtstat command: Index number: from 80 to 159

The identification numbers go from 0 to 415:
80 attendant indexes: 0 to 79 re-indexed as identification numbers 0 to 79
80 attendant group indexes: 0 to 79 re-indexed as identification numbers 80 to 159
256 entity indexes: 0 to 255 re-indexed as identification number 160 to 415

For the configuration of the CDT of group 0: cdtstat 80

Alcatel-Lucent OmniPCX Enterprise – Attendant Group

Ref. ENTP0416M01TEUS Issue 02

776
Attendant sets
Attendant Group Call prefix

The command “ednump” can list the system Attendant Group Call prefixes

ednump

1 – dir -> Directory_number

2 - mean = Attendant_Group_Call -> Meaning
3 - info

==========================
enter criteria or command: go
==========================

07/01/08 EDNUMP V. 4.00 Page : 1

+-----------------+----------------------------------------------
|dir |mean
+-----------------+----------------------------------------------
|31800 |Attendant_Group_Call
+-----------------+----------------------------------------------

Alcatel-Lucent OmniPCX Enterprise – Attendant Group

Ref. ENTP0416M01TEUS Issue 02

Alcatel-Lucent OmniPCX Enterprise – Attendant Group

Ref. ENTP0416M01TEUS Issue 02

778
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

779
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

780
Alcatel-Lucent OmniPCX Enterprise

Call Distribution - Attendant

OBJECTIVE

To describe the Attendant Call Distribution specificities

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Attendant

Ref. ENTP0418P13TEUS Issue 02

781
Call Distribution - Attendant
Generalities

An Attendant is defined by

An Attendant Index
It is a unique system reference (even in network configuration)

A physical directory number

Used only in CDTs (the Attendant CDT as well as other CDTs (Entities, Groups..)
Routing 1, Routing 2, Routing 3
Usually, it is a directory number which can not be dialed directly by a user
e.g. B9000
When a call is routed to this particular number, the corresponding extension is
rung

A Call Distribution Table

Optional “Individual Attendant” prefix

Used to access to the Attendant CDT

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Attendant

Ref. ENTP0418P13TEUS Issue 02

782
Call Distribution - Attendant
Available Extensions

Two types of extensions

TDM (1) types

Alcatel-Lucent 4035 + 40 keys (Add-On)
Alcatel-Lucent 4059 MAC (Screen Based Console)
A 4059 software is installed on a PC
Multi Media Keyboard (MMK)
Terminal Adaptor Multi Media Attendant Console (TA-MAC)

IP type
Alcatel-Lucent 4059 MAC/IP (IP attendant Softphone on PC)
IP Desktop Softphone [4035 IP emulation]

Number of attendants per :

Node =50 (10 attendants per Attendant group)
Network= 80

(1) TDM: Time Division Multiplexing

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Attendant

Ref. ENTP0418P13TEUS Issue 02

783
Call Distribution - Attendant
Available Services

Telephone
Transfer
Individual hold
Chained call
Supervision
…

Access to services
Customer management (Speed dial numbers, CDT,
Charging
System management (date & time)
Installation states (Call distribution status)
…

Customized keyboard
The attendant keys can be modified (by the Attendant person) whatever the
attendant console type
The PC keyboard keys (F1 to F12 and S1 to S8) can be configured(1)

(1) The available configurable possibilities are:

- Call Presentation
- Directory number / Trunk supervision
- Individual Hold
- Speed dial number
-…

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Attendant

Ref. ENTP0418P13TEUS Issue 02

784
Call Distribution - Attendant
Extension Status

The Attendant can support 4 different status

“Idle”
The Attendant is free, neither phoning nor managing

“Busy”
Attendant is on line or carrying out management action

“Unplugged”
The handset is disconnected, or via the “Logon/logoff” key/buton the attendant
has logged off the extension
To switch back the Attendant to “in service mode”, the operator has to press on the
“Logon/logoff” key/button

“Absent”
On a presented call, if an Attendant does not off-hook before the en dof the system
timer “76” (80 s by default), this Attendnant is considered “Absent”
To switch back the Attendant to “in service mode”, the operator has to press on the
“Logon/logoff” key/button

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Attendant

Ref. ENTP0418P13TEUS Issue 02

785
Call Distribution - Attendant
Call Presentation

An Attendant physical number can be managed in several CDTs

Entity, 1 Entity 2, Attendant Group, Attendant…

In such a case, it can be difficult to clearly define all the calls

The Traffic Call Presentation keys (Pcots) allow to split the traffic into several
“classes” (traffic flows)
VIP
DID incoming calls
Chained call
Entity
…

A Traffic Presentation Class is associated to an Attendant’s programmable

keys (several classes can be associated to the same key)

Pcots: Presentation class of traffic ( Class of traffic presentation ).

In the installation parameters, some default priorities of class of services are defines. That allows to force the presentation of
some calls before some others according to their priority, instead of the using the call incoming order

Phone traffic

Call Routing
Presentation
Classes
Entity Grop Attend. sets

DDI private call DDI private call

/ local entity 1 / local entity 2

DDI call DDI call Chained calls Other

No answer entity 1 No answer entity 2

entity call 1 entity call 2 Trunk circuit calls

all entities

Key #1 Key #2 Key #3 Key #4

Alcatel-Lucent OmniPCX Enterprise – Call Distribution - Attendant

Ref. ENTP0418P13TEUS Issue 02

786
Alcatel-Lucent OmniPCX Enterprise
Attendant Configuration

PROCEDURE

OBJECTIVE

- To learn how to configure an Attendant console (generic procedure)

OVERVIEW
This procedure provides the information required to configure an attendant console
Several types of attendant extensions are available

- Alcatel-Lucent 4059 IP Attendant

- Alcatel-Lucent 4059 Screen Base Console

- Alcatel-Lucent 4035

- IP Attendant SoftPhone (4035 + IP with 40 additional keys)

This procedure does not provide the Attendant Group configuration (pre-requisites)

Issue 02 Ref. ENTP0415C13TEUS.doc P. 1

PROCEDURE

1. Attendant extension creation (example with 4035 extension type)

Application Configuration Tab PCX

Path / Attendant /Attendant sets
Action Create
Tab All
Parameters Physical Directory No.: B9000
Attendant Id: 0 (e.g.)
Attendant Group Id: 0 (e.g. has to be configured previously)
Shelf Address: 1
Board Address: 1
Equipment Address: 4
Set Type: 4035T
Entity Number: 1 (for example)
Add On Module 1: 40 Keys (only in case of use of 4035)
Secret Code: ****
Services Access Rights

P. 2 Ref. ENTP0415C13TEUS.doc Issue 02

…
Cost Center Id: 255 (or 0<already created Center Id<254)
Cost Center Name:
Charging COS: Justified/Not Ticketed
Public Network COS: 2 (e.g.)
Language Id: 1 (e.g.)
Ringing: Normal/Delayed/with beep/No ringing
Automatic Transfer: Yes/No
Action Click on “ ” to valid

Note: To each “Service Right”, it is possible to use 3 different possibilities:

– Forbidden
– Allowed with no control
– Allowed with Attendant Code
Cost Center: A Cost Center is used to regroup some devices (like a Department for
example). The accounting application can generate some reports by “Cost Center”
Charging COS:
– NOT ticketed: the attendant calls are not taken into account by the Accounting
application
– Justified: the attendant calls are taken into account by the Charging
application
As soon as the Attendant set is created, automatically its corresponding Call
Distribution Table is created

Issue 02 Ref. ENTP0415C13TEUS.doc P. 3

2. Call Distribution Table

Application Configuration Tab PCX

Path / Attendant/ Attendant Call Distribution
Object 1 (Attendant Id)
Parameters Overflow Routing No.: 31010 (e.g.)
Forwarding on Routing: Yes/NO (refer to the Note)
Att.Status: Night

Cont’ Att.Status: Day

Action Click on “ ” to valid

Note: Some other Attendant Groups /Attendants physical numbers can be used in this
CDT (depends on the system topology and customer requirements)

Forwarding on Routing:
– NO: If the routing overflow number (see this attribute) of any trunk is also
introduced into one of the routing numbers (night, day, forwarding 1,
forwarding 2), the forwarding on this overflow number will be direct
regardless of other routing or overflow numbers.
– YES: normal functioning: forwarding on routing numbers (see Routing Numbers)

P. 4 Ref. ENTP0415C13TEUS.doc Issue 02

3. Prefix to access to the Attendant Call Distribution

Application Configuration Tab PCX

Path / Translator / Prefix Plan
Action Create
Parameters Number: 31810
Prefix Meaning: Indiv. Attendant Call
Prefix Information: 0 (Attendant Id)
Action Click on “ ” to valid

4. Attendant Phone book Name

Note: To display the attendant name on a set during a call, an entry about the
Individ.Attendant Call prefix has to be managed in the phone book

Application Configuration Tab PCX

Path / Phone Book
Action Create
Parameters Directory Number: 31810 (Same as the Indiv.Attendant call
prefix)
Directory Name: Attendant (e.g.)
Directory First Name: Welcome desk (e.g.)
Phone Book Type: Phone Book Serv. No.
Can be Called/Dial by name:Yes
Action Click on “ ” to valid

Issue 02 Ref. ENTP0415C13TEUS.doc P. 5

P. 6 Ref. ENTP0415C13TEUS.doc Issue 02

Alcatel-Lucent 4059

OBJECTIVE

To describe and manage the Alcatel-Lucent 4059 attendant console

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

793
Alcatel-Lucent 4059
Overview

The Alcatel-Lucent 4059 Attendant includes

A terminal adapter box remotely powered by the Alcatel-Lucent OmniPCX

Enterprise

A Multi Media keyboard (MMK) with PC compatibility and audio functions

It receives power supply from the terminal adapter

A PC with its own standard VGA display

Alcatel-Lucent 4059 software has to be installed

Connecting cables for the central unit

MAC/PC: to exchange information between the Alcatel-Lucent 4059 software and
the terminal adapter
Keyboard: to use custom keyboard with the PC

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

794
Alcatel-Lucent 4059
Overview

Alcatel-Lucent 4059 cabling

UA
connection

PC
Keyboard connection

PC TEL <-> PC COM1

Connection

Keyboard
connection

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

795
Alcatel-Lucent 4059
Overview

Keyboard
Audio keys Call handling
Function keys keys

Automatic answer Automatic

Night status indicators indicator
Microphone transfer indicator

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

796
Alcatel-Lucent 4059
Overview

Audio keys

Microphone O/S

Hands-free mode activation Loudspeaker activation

Loudspeaker level adjustment

Remark:
This information is available in the console status area

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

797
Alcatel-Lucent 4059
Overview

Call handling keys

Commute to 4059

Broker’s call cancellation Release

Back and forth Set ringing

Call seizure in routing

Internal calls seizure

Hold calls seizure Transfer or put on hold

Remark:
This button makes possible to switch (on/off) immediately to the A4059 application. If the A4059 or PC is out of
order, it offers the possibility of using the keyboard

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

798
Alcatel-Lucent 4059
Overview

Screen

1
2

3
5

1:Tool menu

2:Supervision icons

3:Programmable keys

4:Call handling

5:Attendant console status

Remark:
The supervision and programmable keys may or may not be displayed together
The TAB key can be used to switch between these applications

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

799
Alcatel-Lucent 4059
Overview

Tool Bar Menu

Status Bar
Configuration
Background color
Switch busy lamp/Prog keys Tab
Switch Soft keys/Prog keys F12
External directory
Service mode
Guide mode
Appointment reminder
Default
system
Sign on Attendant mini-message
Mute Busy lamp field
Loudspeaker Programmable keys
Redial Directories
Store and redial
Exit

Store and redial: number list creation and use

------------
Default system: directory search in default directory defined in Option System menu

-------------
External directory: directory search in 4755 external directory
Service Mode: system management according to attendant rights
Guide Mode: attendant customization
Appointment reminder: user appointment management
-------------
Status Bar: date and time display
Configuration: work space customization
Background color: background screen color modification
Switch busy lamp/Prog Keys Tab: switch between supervision and programmable keys screens
Switch Soft keys/Prog Keys F12: activate either supervision or programmable keys

------------
Attendant mini-message: possibility of setting up messages
Busy lamp field: setting up of supervision icons
Programmable keys: setting up of programmable keys
Directories: setting up of default directory and directory presentation modifications

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

800
Alcatel-Lucent 4059
Overview

Supervision icons

Analog set or fax (green) Busy set with external

call (yellow)
Analog set in off hook
status (yellow) Hunt group

Digital set (green) Trunk group (yellow)

Digital set in off hook Programmed

status (yellow) absence message (yellow)
Busy set with internal
Set temporarily
call (green)
inaccessible (yellow)

Hunting group: if one set of the group in on call, only one set is yellow If both sets are yellow, all sets in the group are busy

Programmed absence message: if the attendant calls a set which is forwarded to an absence message, the reason is displayed
on the attendant screen The attendant can ring the set

Set temporarily inaccessible: a set in programming mode is not accessible

Integrated Supervision display limit: 8 pages of 12 icons or 3 pages of 32 icons

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

801
Alcatel-Lucent 4059
Overview

Programmable keys

In this area the attendant can manage its own internal/external numbers

16 programmable keys
F12 for pre-programmed keys then key selection
To switch to another page:

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

802
Alcatel-Lucent 4059
Overview

Console status

Console in service Hands-free mode activated

Night service Loudspeaker level

Automatic answer activated Supervision icons activated

Automatic transfer activated

DTMF activated

Secret activated -
micro deactivated

Loudspeaker activated

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

803
Alcatel-Lucent 4059
Overview

Attendant group status modification

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

804
Alcatel-Lucent 4059
Overview

Alcatel-Lucent OmniPCX Enterprise management

With "mgr" management tool

Path: /Attendant/Attendant sets

Node Number (reserved): 1

Instance (reserved): 1
Physical Directory No: A31002

Attendant Id: 2
Attendant Group Id: 1
Shelf Address: 1
Board Address: 1
Equipment Address: 6
Set Type + MAC 2 equipts
……
…..

V24 Extension + True

Mac/PC + MAC/PC
S0 Extension + False

Installation: install exe or setup exe

- A4059 is installed in directory: C:\Alcabc32
- V24-PC access parameters can be modified using the file: config.exe

Remark: an attendant must be created for correct operation Do not modify an existing attendant !

Information: When starting up, the A4059 loads files from PABX

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

805
Alcatel-Lucent 4059
Overview

PC software management

Install the Alcatel-Lucent 4059 MAC and the Alcatel-Lucent 4059 busy lamp
field software on the PC

Manage the ABCA link management on PC as follows:

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059

Ref. ENTP0415P02TEUS Issue 02

806
Alcatel-Lucent OmniPCX Enterprise

IP SoftPhone Attendant

OBJECTIVE

To describe the IP SoftPhone Attendant

Alcatel-Lucent OmniPCX Enterprise – IP SoftPhone Attendant

Ref. ENTP0415P04TEUS Issue 02

807
IP SoftPhone Attendant
Overview

IP SoftPhone Attendant is a multi-skin software application emulating a 4037

extension (4035 + IP)

Alcatel-Lucent OmniPCX Enterprise – IP SoftPhone Attendant

Ref. ENTP0415P04TEUS Issue 02

808
IP SoftPhone Attendant
Overview

Low-end solution based on IP-SoftPhone

“4035 IP Attendant” emulation with same feature level

Display
Phone keys

Interface with several skins

Key Labels management

USB headset
Ringing is done via PC loudspeakers
And voice is handled by the USB headset
Up to 15 different rings (WAV files)

Alcatel-Lucent OmniPCX Enterprise – IP SoftPhone Attendant

Ref. ENTP0415P04TEUS Issue 02

809
IP SoftPhone Attendant
Overview

Magic keys are associated to each key:

CTRL A CTRL B CTRL M CTRL N

CTRL C CTRL D CTRL O CTRL P

CTRL E CTRL F CTRL Q CTRL R

CTRL G CTRL H CTRL S CTRL T

CTRL I CTRL J CTRL U CTRL V

CTRL K CTRL L CTRL W CTRL X

Example:
To put in day mode: use the short cut “CTRL N”
To use voice amplifier: use the short cut CTRL X

Alcatel-Lucent OmniPCX Enterprise – IP SoftPhone Attendant

Ref. ENTP0415P04TEUS Issue 02

810
IP SoftPhone Attendant
Restrictions

Restrictions

No LED signaling

Not compatible with the spatial redundancy in dual IP subnet

Not compatible with the encoding offered by the IP Touch firmware

Local tone is not generated, so testing the switch tones cannot be done

Does not generate DTMF

QOS ticket are not generated

Programmable keys not supported

Alcatel-Lucent OmniPCX Enterprise – IP SoftPhone Attendant

Ref. ENTP0415P04TEUS Issue 02

Alcatel-Lucent OmniPCX Enterprise – IP SoftPhone Attendant

Ref. ENTP0415P04TEUS Issue 02

812
Alcatel-Lucent OmniPCX Enterprise

IP Attendant SoftPhone

OBJECTIVE

To manage an IP Attendant SoftPhone

Alcatel-Lucent OmniPCX Enterprise – IP Attendant SoftPhone

Ref. ENTP0415C03TEUS Issue 02

813
IP Attendant SoftPhone
Configuration

Installation
Install the application UAIPPhoneInst.exe.
Enter the IP address of the main and stand-by CS
Enter the directory number (Number that can be dialed)

Warning: the attendant number must be dialed

Alcatel-Lucent OmniPCX Enterprise – IP Attendant SoftPhone

Ref. ENTP0415C03TEUS Issue 02

814
IP Attendant SoftPhone
Configuration

Configuration of the PCX

Create a 4037 TSCIP set with internal keyboard set to English. Therefore, the
IP SoftPhone will adapt itself to the PC

Create: Attendant Sets

Node Number (reserved) : 1

Instance (reserved) : 1
Physical Directory No. : 35999

Attendant Id : 0
Attendant Group Id : 0
Shelf Address : 255
Board Address : 255
Equipment Address : 255
Set Type + 4037 (4035 & TSC IP)
Entity Number : 1
Add On Module 1 + None
Add On Module 2 + None
Add On Module 3 + None
External Alphanumeric Keyboard + None
Internal Alphanum.Keyboard + English

Secret Code : ****

Confirm : ****

Alcatel-Lucent OmniPCX Enterprise – IP Attendant SoftPhone

Ref. ENTP0415C03TEUS Issue 02

815
IP Attendant SoftPhone
Start up

IP attendant SoftPhone start up

When the client is activated the attendant works like a 4035 attendant set.
It is possible to manage sticker per key by using the right button on the
mouse

Alcatel-Lucent OmniPCX Enterprise – IP Attendant SoftPhone

Ref. ENTP0415C03TEUS Issue 02

816
IP Attendant SoftPhone
Configuration

Keys shortcut

CTRL A CTRL B CTRL M CTRL N

CTRL C CTRL D CTRL O CTRL P

CTRL E CTRL F CTRL Q CTRL R

CTRL G CTRL H CTRL S CTRL T

CTRL I CTRL J CTRL U CTRL V

CTRL K CTRL L CTRL W CTRL X

IP SoftPhone client modification

Click on the phone in the task

bar and use the right
button on the mouse

Alcatel-Lucent OmniPCX Enterprise – IP Attendant SoftPhone

Ref. ENTP0415C03TEUS Issue 02

Alcatel-Lucent OmniPCX Enterprise – IP Attendant SoftPhone

Ref. ENTP0415C03TEUS Issue 02

818
Alcatel-Lucent OmniPCX Enterprise

Alcatel-Lucent 4059 IP Attendant

OBJECTIVE

To describe the Alcatel-Lucent 4059 IP Attendant

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059 IP Attendant

Ref. ENTP0882P02TEUS Issue 02

819
Attendant Solutions
4059 IP Attendant- Generalities

The “4059 IP attendant” is based on

The current 4059-MAC software

An IP connectivity (IP-Link) instead of UA link
A new Multi-Media Keyboard (USB(1) connectivity instead of PS/2), without
loudspeaker neither handset
A 4059 IP associated set
An Alcatel-Lucent 8/9 Series extension type(2), which is used to support the audio
function (not supported any more by the MMK)

IP
Network

(1) On the PC point of view, the keyboard is changed to standard USB type, and the driver installed is changed to be Alcatel-
Lucent USB telephonic keys driver

(2) Both full ranges of extensions are available (IP: 4008/4018/4028/4038/4068 and TDM: 4019/4029/4039)
It is also possible use the 4068 SoftPhone type

Remark:
The “Alcatel-Lucent 4059 IP Attendant” feature requires the software version 5.0.x minimum

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059 IP Attendant

Ref. ENTP0882P02TEUS Issue 02

820
Attendant Solutions
4059 IP Attendant-Associated set

When the IP Attendant is logged in

All the phone functions of the associated x8 or x9 extensions Series are

disabled
And all the calls to this set will be routed to attendant
Information displayed on the associated set when the attendant is in service
“ Attendant in service…”

Information displayed on the caller display when calling an attendant

General attendant call or individual attendant prefix
GENERAL OPERATOR

Direct call of the associated set

“Name associated to the direct attendant call prefix”

The extension keyboard is disabled

Once the IP attendant is logged out, the set returns to a standard set

Remark
If the associated set has a Call forwarding activated, the calls:
- Follow this forwarding when the attendant is out of service
- Are routed to the attendant when it is in service

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059 IP Attendant

Ref. ENTP0882P02TEUS Issue 02

821
Attendant Solutions
4059 IP Attendant - Restrictions

This associated set is incompatible with some features

Multi-line (no Boss-Secretary, no twin set, not supervisor, …)
ACD, Hotel (except administrative set),
Pickup group / Hunt group
Alarm set, 4980

The 4059 IP attendant and the associated set must belong to the same node and
same IP domain

The 4059 IP attendant can not be installed on the same PC as

A 4980
Or an 4059 MAC attendant

Add-on module not available any more(4059 Add-On)

Remark
Before installing the 4059 IP software on the PC, the attendant, and its associated set must be configured in the Alcatel-Lucent
OmniPCX Enterprise

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4059 IP Attendant

Ref. ENTP0882P02TEUS Issue 02

822
Alcatel-Lucent OmniPCX Enterprise
Alcatel-Lucent 4059 IP Attendant

PROCEDURE

OBJECTIVE

- To learn how to configure and install the Alcatel-Lucent 4059 IP Attendant

OVERVIEW
The Alcatel-Lucent 4059 IP Attendant is made of two elements:

- The 4059 IP Attendant software installed on a PC (with a specific keyboard)

- An associated extension to support the audio features

The Attendant has to be configured on the Alcatel-Lucent OmniPCX Enterprise before installing
the Attendant software
(In this procedure, the Attendant Group creation is not describe (pre-requisite))

Issue 02 Ref. ENTP0882C02TEUS.doc P. 1

PROCEDURE

1. Attendant extension

1.1. Attendant extension creation

Application Configuration Tab PCX

Path / Attendant/ Attendant Sets
Action Create
Parameters Physical Directory No.: B9000
Attendant Id: 0 (e.g.)
Attendant Group Id: 0 (e.g. has to be configured previously)
Shelf Address: 255
Board Address: 255
Equipment Address: 255
Set Type: 4059 IP
Entity Number: 1 (for example)
Associated phone Set: 31200 (e.g. has to be previously configured)
Action Click on “ ” to valid

Note: After the Attendant registration, automatically the PC IP @where is hosted this
Attendant console application appears in the TSC IP parameters

Path / Attendant/ Attendant Sets /

Object Select the “Attendant associated extension” (31200 in this example)
../ TSC IP Attendant
Parameters Set Type: 4059 IP
Terminal Ethernet Address: 00-08-02-E9-CD-1A (Consultation only)
IP Address: 10.2.48.152 (Consultation only)

Note: As soon as the Attendant is created with the Associated extension, it is possible to
check the this association in the corresponding extension parameters:

Path / Users <31200> (in this example)

Object Select the “Attendant associated extension” (31200 in this example)
Sub-Path ../ 8&9 Series Parameters
Parameters 4059 Directory Number: B9000 (Consultation only)

P. 2 Ref. ENTP0882C02TEUS.doc Issue 02

1.2. Call Distribution Table

Application Configuration Tab PCX

Path / Attendant/ Attendant Call Distribution
Object 0 (Attendant Id)
Parameters Overflow Routing No.: 31010 (e.g.)
Forwarding on Routing: Yes/NO (refer to the Note)
Att.Status: Night
Routing 1:
Routing 2:
Routing 3:
Att.Status: Day
Routing 1: B9000
Routing 2:
Routing 3:
Att. Status: Mode1
Routing 1:
Routing 2:
Routing 3:
Att. Status: Mode2
Routing 1:
Routing 2:
Routing 3:
Action Click on “ ” to valid

Note: Some other Attendant Groups /Attendants physical numbers can be used in this
CDT (depends on the system topology and customer requirements)
Forwarding on Routing:
- NO: If the routing overflow number (see this attribute) of any trunk is also
introduced into one of the routing numbers (night, day, forwarding 1,
forwarding 2), the forwarding on this overflow number will be direct
regardless of other routing or overflow numbers.
- YES: normal functioning: forwarding on routing numbers (see Routing Numbers)

Issue 02 Ref. ENTP0882C02TEUS.doc P. 3

1.3. Prefix to access to the Attendant Call Distribution

Application Configuration Tab PCX

Path / Translator / Prefix Plan
Action Create
Parameters Number: 31900
Prefix Meaning: Indiv. Attendant Call
Prefix Information: 0 (Attendant Id)
Action Click on “ ” to valid

P. 4 Ref. ENTP0882C02TEUS.doc Issue 02

2. 4059 IP Attendant software Installation

2.1. USB keyboard driver installation

Application Windows Explorer Tab 4059 Software Directory

Path USBkbd/Disk1 sub-directory
Action Execute the “Setup.exe” file

Action Reboot the PC

Action Connect the USB Keyboard and “Accept” the automatic drivers installation

2.2. Attendant software installation

Application Windows Explorer Tab 4059 Software Directory

Path “4059” sub-directory
Action Execute the “Setup.exe” file

Result

Issue 02 Ref. ENTP0882C02TEUS.doc P. 5

Action Select the country “Language“ then press OK

Result

Action Select the “Alcatel-Lucent 4059 IP” package, then press “NEXT>”
Result

P. 6 Ref. ENTP0882C02TEUS.doc Issue 02

Action Manage the “Call Server IP address” and the “Attendant physical number”,
then press on “OK”
- Call Server IP address= Role Main IP @
- Attendant physical number= B9000 (in this example)
Result

Action Press on the “Quit” button on the last configuration

Note: After the installation, the PC has to be restarted !

Issue 02 Ref. ENTP0882C02TEUS.doc P. 7

2.3. Start the Application

Application PC desktop (environment)

Action Click on the “Alcatel-Lucent 4059-IP” shortcut

Result

Action To switch on “Day status”, Click-on “Sign on” submenu option

Note: When the attendant is in “night” status, the associated set is working normally. As
soon as the attendant switches the application in “day” status, the audio
functions of the associated extension are reserved to the Attendant application
The audio functions (silence, hands free…) are activated from the USB keyboard

P. 8 Ref. ENTP0882C02TEUS.doc Issue 02

Attendant sets

OBJECTIVE

To maintain attendant sets with the maintenance Web Tool and with the system maintenance commands

Alcatel-Lucent OmniPCX Enterprise – Attendant sets

Ref. ENTP0415M01TEUS Issue 02

831
Web Tool
Access to the maintenance tool

Access to the tool (via a Web browser)

The URL used to access to the WebTool as to be:

http://OmniPCX-Enterprise-IP@/webtool2/

Ex:

At the connection to the system, a Security message is displayed

Alcatel-Lucent OmniPCX Enterprise – Attendant sets

Ref. ENTP0415M01TEUS Issue 02

832
Web Tool
Access to the maintenance tool (Cont’)

To access to the maintenance Web Tool:

The language has to be selected

The “mtcl” login and password have to be given

The default “mtcl” password can not be used. This one has to be therefore modified

Alcatel-Lucent OmniPCX Enterprise – Attendant sets

Ref. ENTP0415M01TEUS Issue 02

833
Web Tool
Access to the Stand-Alone system status

When authenticated, a menu is displayed on the left of page

Press on “Toolbox” menu to reach the Stand-Alone system status Tool

Alcatel-Lucent OmniPCX Enterprise – Attendant sets

Ref. ENTP0415M01TEUS Issue 02

834
Attendant sets
Status

With the maintenance Web Tool, it is possible to check the System Attendant
sets status

Alcatel-Lucent OmniPCX Enterprise – Attendant sets

Ref. ENTP0415M01TEUS Issue 02

835
Attendant sets
Status command

The “opstat” maintenance command allows to check the status of the

attendant sets

Usage: opstat
Mon Jan 7 18:30:59 CET 2008

prem_att 0 nb_att_screen 3
|-------------------------------------------------
| INFO | ATT 0 | ATT 1 | ATT 4 |
|-------------------------------------------------
|nameat| Attendant | | |
| | Welco | | |
|-------------------------------------------------
|state | ABSENT | IDLE | UNPLUGGED |
|-------------------------------------------------
|dir nb| B9000 | B9001 | B9002 |
|-------------------------------------------------
|urgent| 0 | 0 | 0 |
|-------------------------------------------------
| usual| 0 | 1 | 0 |
|-------------------------------------------------
|typcnx| MANUAL | MANUAL | MANUAL |
|-------------------------------------------------
|calls | NO CALLS | USUAL | NO CALLS |
|-------------------------------------------------
Group Status | type | DAY | DAY | NIGHT |
|-------------------------------------------------

Alcatel-Lucent OmniPCX Enterprise – Attendant sets

Ref. ENTP0415M01TEUS Issue 02

836
Attendant sets
Call Distribution Table

Information on the attendant set’s CDT

Usage: cdtstat <Attendant Index N°>

cdtstat 0

Mon Jan 7 18:51:14 CET 2008

CDT idx: 0
flg_deb_nuit: 1
state: GROUP
group: 0
poste_nuit:

state NIGHT:
state DAY: B9000
state FWD1:
state FWD2:

state NIGHT:
state DAY:
state FWD1:
state FWD2:

cdtstat Index N°: why from 0 to 79 ?

The identification numbers go from 0 to 415, i.e.,

80 attendant indexes: 0 to 79 re-indexed as n° identification 0 to 79
80 attendant group indexes: 0 to 79 re-indexed as n° identification 80 to 159
256 entity indexes: 0 to 255 re-indexed as n° identification 160 to 415

To have the configuration of the CDT of the Attendant set 2: cdtstat 2

Alcatel-Lucent OmniPCX Enterprise – Attendant sets

Ref. ENTP0415M01TEUS Issue 02

837
Attendant sets
Individual Attendant Call prefix

The command “ednump” can list the system Individual Attendant Call prefixes

ednump

1 – dir -> Directory_number

2 - mean = Individ_Attendant_Call -> Meaning

==========================
enter criteria or command: go
==========================

07/01/08 EDNUMP V. 4.00 Page : 1

+-----------------+-------------------------------------------
|dir |mean
+-----------------+-------------------------------------------
|31810:31811 |Individ_Attendant_Call
+-----------------+-------------------------------------------

Alcatel-Lucent OmniPCX Enterprise – Attendant sets

Ref. ENTP0415M01TEUS Issue 02

838
Alcatel-Lucent OmniPCX Enterprise
Call distribution

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage call distribution and attendant assistant

MANAGEMENT

1. Realize the following configuration:

Attendant group 1

attendant 1

Night forward ( 3x001)

Attendant name Physical directory number Individual attendant call prefix.

OPE1 A9x001 9x001

Attendant group name Physical directory number Attend group call prefix
GROP1 A9x51 9x051

Issue 02 Ref. ENTP0415H03TEUS.doc HO. 1

2. Create 1 prefix used to call directly the attendant console. Manage the call distribution
table in order to call the attendant according the installation status. Where are this tables?

3. Do the test with the prefix.

4. Manage a prefix in order to call the attendant group.. For any installation’s status, in case
of attendant #1 group call, the call will be routed to the attendant #1.

5. Manage now an unique prefix in order to call from any user, the attendant group of the
corresponding entity.

6. Manage the corresponding tables knowing that a night forward set must be configured as
in the diagram page 1. Where are this tables?

7. Do the test

8. Manage the timer 102 with the value 5. Realize an external call and an internal call to the
attendant group. What happens? Which is the number of the voice guide ?

9. With maintenance commands, display the call distribution tables, attendants status,
attendant groups status and entities.

HO. 2 Ref. ENTP0415H03TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

841
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

842
Alcatel-Lucent OmniPCX Enterprise

Mobility DECT

OBJECTIVE

To describe the Mobility DECT

Alcatel-Lucent OmniPCX Enterprise – Mobility DECT

Ref. ENTP0419P01TEUS Issue 03

843
DECT overview
Standard

DECT
Digital Enhanced Cordless Telecommunication

Standard published by ETSI

European Telecommunication Standard Institute

Management protocol about set PABX exchanges

DECT

Alcatel-Lucent OmniPCX Enterprise – Mobility DECT

Ref. ENTP0419P01TEUS Issue 03

844
DECT overview
Elements

Three elements are mandatory for the mobility

PABX
Base stations (IBS or RBS)
DECT Handset

2 3

Base station DECT Handset

1 PABX

Alcatel-Lucent OmniPCX Enterprise – Mobility DECT

Ref. ENTP0419P01TEUS Issue 03

845
DECT overview
Principle

Cell
Multi-Cell
Base stations

Coverage by base stations

Multiple cells management

Alcatel-Lucent OmniPCX Enterprise – Mobility DECT

Ref. ENTP0419P01TEUS Issue 03

846
DECT overview
Principle (next)

Using IBS, 3 or 6 simultaneous calls per base station according to the number of
UA links used to connect the base station.

Hand over
Process permitting a transparent change of Base Station during a
communication

Localization
Process allowing a handset to be recognized by a PABX

Roaming
Possibility to be called everywhere (local or network)

Alcatel-Lucent OmniPCX Enterprise – Mobility DECT

Ref. ENTP0419P01TEUS Issue 03

847
DECT overview
Identification numbers

Identification of the elements:

Each element of a DECT communication is identified by an unique specific

number:

PARI RPN IPUIN / IPUIO

(PARK & PLI)
These numbers allow the set and the base station to exchange voice and
signaling data during the establishment and the maintenance of the radio
link.

Alcatel-Lucent OmniPCX Enterprise – Mobility DECT

Ref. ENTP0419P01TEUS Issue 03

848
DECT overview
Identification numbers

PARI number managed on PABX side

Identifying the PABX
11 octal digits (example: 10000401230)

PARK number managed on the handset

It is equivalent to the PARI number but in the handset
Allowing the set to recognize the PABX
11 digits in octal

RPN number
Identifying the base station
2 digits in hexadecimal

IPUIN number
Identifying the handset
Fixed in the memory of the handset

Alcatel-Lucent OmniPCX Enterprise – Mobility DECT

Ref. ENTP0419P01TEUS Issue 03

849
DECT overview
Identification numbers

IPUIO number
Identifying the handset
Allocated by the system according to the directory number of the handset

PLI number
Number of binary elements analyzed by the handset in the received PARI
number from a base station
Used in network or in multi-PARI configurations when a set has to lock itself
on two different DECT systems

Alcatel-Lucent OmniPCX Enterprise – Mobility DECT

Ref. ENTP0419P01TEUS Issue 03

850
Alcatel-Lucent OmniPCX Enterprise
DECT IBS Configuration (Mono-ACT)

PROCEDURE

OBJECTIVE

- To learn how to manage an IBS installation

OVERVIEW
The purpose of this procedure is to explain you how to put in service a DECT configuration IBS
The first step is to manage the PARI number IBS then to manage the base stations

Issue 02 Ref. ENTP0419C01TEUS.doc P. 1

PROCEDURE

1. IBS configuration

Application mgr
Path /PWT/DECT system
Action Select “Review/modify” and press “enter”
Action On the next window, press “enter” and “Ctrl v” to validate
Node Number (reserved) : 1
Result Instance (reserved) : 1

Radio base type + IBS

Max numb of paging retransm : 5
Routing tone for i ncomePWT/Dect call + Inactive
PLI for CTM : 31
Default Echo Cancellation + YES
% of channels in part rel : 0
Max % of full unused shells : 50
AC System : 1234
Security level + Authentication
Station base type + European DECT
Dect system generation + 2nd Generation
Prolonged preamble + NO
Max Time of unused shell (U=10'’ : 144

Campus

Master synchro Campus + NO

PLI Campus : 31
Subscriber profile by default : --------
Home preference (Mobile Range) + YES

Carriers available

Carrier 0 + YES
Carrier 1 + YES
Carrier 2 + YES
Carrier 3 + YES
Carrier 4 + YES
Carrier 5 + YES
Carrier 6 + YES
Carrier 7 + YES
Carrier 8 + YES
Carrier 9 + YES

Action Select “IBS “ in the Radio base type field and “Ctrl v” to validate
Path /PWT/DECT system / IBS system
Action Select “Review/modify” and press “enter”

P. 2 Ref. ENTP0419C01TEUS.doc Issue 02

Action On the next window, press “enter” and “Ctrl v” to validate

Node Number (reserved) : 1
Result Instance (reserved) : 1
Instance (reserved) : 1

Pari Value : 1000567300

Area type + 1 area of 256 IBS
Base station busy trigger : 4

Action Enter the value of the PARI number in the Pari value field and “Ctrl v“ to
validate
Path /Shelf
Action Select “Review/modify” and press “enter”
Action On the next window, press “enter” and “Ctrl v” to validate
Action Select the shelf number the Up and Down arrows and press “enter”
Node Number (reserved) : 1
Result Shelf Address : 3

Shelf Type + Media Gateway Small

Name : --------------------
Virtual crystal + NO
Pari Number + Pari IBS
Shelf role + Main (Master)
Main Shelf Address : 3
Law + Default
Reference + NO

Action Select Paris IBS in the Pari Number field and “Ctrl v“ to validate
Path /Shelf/Board/IBS
Action Select “Create” and press “enter”
Node Number (reserved) : 1
Result Shelf Address : 3
Board Address : 1
Equipment Address : 2

Radio Part Number : 0

Location Area : 0
Location name : --------
Line delay + Short line (0-400M)
Number of UA link : 2
IBS generation + IBS 1G
Antenna diversity + YES
Odd slots + NO
Base in noisy audio environment + NO

Action Enter the physical address of the base station

Action Check these parameters according to the configuration and ”Ctrl v” to
validate

Issue 02 Ref. ENTP0419C01TEUS.doc P. 3

P. 4 Ref. ENTP0419C01TEUS.doc Issue 02

PROCEDURE

OBJECTIVE

- To learn how to install Mobile 300/400

OVERVIEW
The purpose of this procedure is to know the way for the installation of the Mobile 300/400.

Issue 02 Ref. ENTP0419C04TEUS.doc P. 1

PROCEDURE

Management of DECT users

1. Management of Mobile 300/400

1.1. Creation of users

Application mgr
Path Users
Action Select “Create” and press “enter”
Entry Number: (For example: 31020)
Name: Dect1
Shelf address: 255
Board address: 255
Equipment address: 255
Set type: GAP+
Action “Ctrl v” to validate

1.2. Installation of the mobile phone

1.2.1. Management on the mobile phone

On the Mobile 300/400

If the mobile phone is new one, when you press the start button you access
directly on the installation menu, else you need to first erase the previous
configuration
Action Launch the on air registration on the set after selection of the area of
installation

Note: During this time it’s necessary to make some management under mtcl, for this
follow the procedure in the next chapter (1.2.2)

P. 2 Ref. ENTP0419C04TEUS.doc Issue 02

1.2.2. Registration command

On the call server

Login mtcl
Command dectinston 31020
Choice of a specific base station (Y/N - default is N)?
Result
Entry n
Remark The system offers to select an installation base station. This will then be
the only one authorized to transmit the installation dialog between sets and
the PCX
If No: Installation will then be performed on all base stations
If Yes: Select the base station by the crystal number, board number and the
position of the RBS or IBS station
GAP characteristics
Result
_______________________________________________________
Directory Number : 31020
User's name : DECT 1
MAO type : GAP+
Dect parameters used.
PARI: 10000400010
PLI : 31
_______________________________________________________
Do you agree to install this set. (Y/N - default is Y)?

Entry Y
Remark Characteristics of the mobile phone 31020, if you are agree press y+enter
to start the registration
Entry Start the registration on the handset.
Wait until the set rings, but you don't have to hang up!!!
_______________________________________________________
Result
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) ==>

Remark When the message “Installation succeed” appears the mobile phone rings
and the installation is completed

Issue 02 Ref. ENTP0419C04TEUS.doc P. 3

Remark 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

P. 4 Ref. ENTP0419C04TEUS.doc Issue 02

DECT Maintenance

OBJECTIVE

To use the DECT maintenance commands

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

859
DECT System
Commands: dectview

IBS: status display

dectview ibs

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

Resource Max busy free percent busy
-----------------------------------------------------
Link 1101 0 1101 0.00
LCEI 1050 0 1050 0.00
ADPCM 0 0 0 ????
Buffer UA-> 510 0 510 0.00
Paging Queue 510 0 510 0.00
================= IBS States =======================

cr= 1 cpl= 01 term= 12 neqt 17 RPN: 0 State: INSERV with 6 channels

cr= 1 cpl= 01 term= 13 neqt 18 RPN: 0 State: slave link OK
cr= 1 cpl= 01 term= 14 neqt 19 RPN: 128 State: INSERV with 3 channels
cr= 1 cpl= 01 term= 15 neqt 21 RPN: 1 State: OUTSERV (3 channels)

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

860
DECT System
Commands: listerm

IBS on a UA board

listerm <act> <cpl>

--------------------------------------------------------------------------
| Coupler: 1 1 Logic type: CPL_UA Board: UAI8 State: IN SERVICE |
|-------------------------------------------------------------------------|
| Cry:Cpl:ac:term | neqt | typ term | dir nb | Out of service cause |
|-------------------------------------------------------------------------|
| 1 1 0 0 | 0321 | 4035(MR2_3 | 34000 | A . . . T . . . . . |
| 1 1 0 1 | 0322 | 4034(MR2) | 34001 | A . . . T . . . . . |
..............
| 1 1 0 13 | 0334 | IBS/3B+D | | . . . . . . . . . . |
| 1 1 0 14 | 0335 | IBS/3B+D | | . . . . . . . . . . |
| 1 1 0 15 | 0336 | IBS/3B+D | | . . . . . . . . . . |
..............
|-------------------------------------------------------------------------|
| (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: 7 |
| Nombre total de terminaux en service : 2 |
-------------------------------------------------------------------------

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

861
DECT System
Commands: listibs

IBS: Display of information

listibs p 1 1 7 0
IBS_name =;
line_delay = SHORT_LINE_0_400M;
nb_ua_link = 1;
rpn = 0;
sync_adjust = 0;
reset = 1;

listibs p 1 1 4 0
IBS_name =;
line_delay = SHORT_LINE_0_400M;
nb_ua_link = 2;
rpn = 1;
sync_adjust = 0;
reset = 1;

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

862
DECT System
Commands: Outserv/inserv and termstat

IBS: Reset base stations

outserv / inserv n <N°eqt>

termstat

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

863
DECT System
Command: dectview

dectview bs

This command gives the states of the RBS base stations

state: the different states are: INSERV: in service, OUTSERV: out of service

dectview dsp

The "dectview dsp" command gives the DSP states.

dectview csp

The "dectview csp" command gives the CSP (Cell Site Processor) versions of
all DECT boards in the system.

The command dectview csp shows the list , the status and the software version of all the CSP of the PABX
Depending on the CSP version, a BS supports or not the GAP handsets

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

864
DECT System
Command: dectinfo

dectinfo
(1)xa001001> dectinfo
================ Usage: dect_info <argv1, argv2, argv3, argv4> ================
param_generaux ---> <0>
all links actives ---> <1>
4 first links ---> <2>
dect_fs ---> <3>
IPUI table ---> <4>
DECT SYSTEM MNT ---> <5>
Observed handsets ---> <6>
Busy UA OUT/IN BUFFERS ---> <7>
Localization areas ---> <8>
Base stations initialization ---> <9>
TSC overview and base station activity ---> <10>
All paging queues ---> <11>
lce_t_adm_link_instance[link] ---> <0, link>
lce_t_link_instance[link] ---> <1, link>
lce_t_rout_to_dlei[link] ---> <2, link>
lce_t_rout_to_lcei[link] ---> <3, link>
all precedent ---> <4, link>
lce_t_rout_from_lcei[lcei] ---> <5, lcei>
lce_t_adm_lcei[lcei] ---> <6, lcei>
DECT TRANSLATION NEQT <-> Num Anu ---> <7, neqt>
remanents indexes par max_handset ---> <8, max_handset>
Maintenance/traffic on BS behind DECT/UA ---> <0, cr_nbr, cpl_nbr>
Specific paging queue ---> <1, pari, area>
lce_t_rout_from_dlei[cr][cpl][dlei] ---> <0, cr_nbr, cpl_nbr, dlei>
IBS general information ---> ibs

This command has several options, and according to the option which is used, the result provides some information about:
- DECT global parameters (dectinfo 0)
- TSC DECT (dectinfo 10)
- Intelligent Base Stations (dectinfo ibs)…

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

865
DECT System
Command: dectinfo

dectinfo 0
(1)xa001001> dectinfo 0
________________________________________________________________________________
_________________________________

>>>>> RBS SYSTEM ONLY <<<<<

_________________________________

RBS general information

-----------------------

Pari[0]: Hexa = 10.00.96.A9 Octal = 10000434400

Pari[1]: Hexa = 10.00.9B.36 Octal = 10000434410
Pari[2]: Hexa = 00.00.00.00 Octal = 00000000000
Pari[3]: Hexa = 00.00.00.00 Octal = 00000000000
Pari[4]: Hexa = 00.00.00.00 Octal = 00000000000
Pari[5]: Hexa = 00.00.00.00 Octal = 00000000000
Pari[6]: Hexa = 00.00.00.00 Octal = 00000000000
Pari[7]: Hexa = 00.00.00.00 Octal = 00000000000
-------------------------
1) Subscription registration parameters
PARK: Hexa = 10.00.8E.40 Octal = 10000434400 PLI = 29
Network PLI = 31
-------------------------
7) Security:
AC system = FF FF Security system = No Security

This command provides a lot of information.

All information are not shown in this example

The firsts lines given by the command «dectinfo 0» show:

- the different PARI numbers managed in the Alcatel OmniPCX Enterprise database
- the PARK and the PLI numbers to manage in the handsets
- the PLI number managed in the Alcatel OmniPCX Enterprise DECT parameters (automatically managed in the
GAP handsets during their registration)

In the example:
- 2 different PARI numbers are managed in the Alcatel OmniPCX Enterprise
- the PARK to manage in the handsets is equal to 10000434400
- the PLI number to manage in the handsets is at least equal to 29 (the 1st PLI value)
- the PLI downloaded in the GAP handsets is equal to 31 (the 2nd PLI value); they can’t work on the 2nd PARI…

- No security is managed in the system ( no encryption, no authentication )

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

866
DECT System
Command: dectinfo

dectinfo 10

(1)xa001001> dectinfo 10

Instantaneous view of TSC Dect sets configuration.

__________________________________________________

Created: 2 Registered: 1 Put in service: 1

Radio link management after a call - Standard (10s): 1

Dynamic ( at least 10s): 0

Dect traffic per radio base station.

____________________________________

Max nbr of channels could be maintained in partial release state after a call.
(case of a RBS) ==> 0
(case of an IBS with 1 UA link) ==> 0
(case of an IBS with 2 UA links) ==> 0

+----------+-----------+-----------+-----------------+-------------------------+
| Base | Free chan | Busy chan | used for a call | kept in partial release |
+----------+-----------+-----------+-----------------+-------------------------+
| 01/03/04 | 5 | 1 | 1 | 0 |
| | | | | |
+----------+-----------+-----------+-----------------+-------------------------+

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

867
DECT System
Command: dectrm

To uninstall a DECT user

dectrm (under "mtcl" )

(1)xa000001> dectrm 31070

_______________________________________________________
Directory Number: 31070
User's name: DECT
MAO type: GAP +
IPEI: 0024500681045
Registered: Yes
____________________________________________________________________

Are you really sure to remove this set. (Y/N - Default is Y) ? y

Attempt to send a deregistration message to the set.

Operation succeed.

_____________________________________________________________________

If a DECT handset had previously been installed, use the dectrm <Directory No.>. to delete all data previously stored.

CAUTION

This command removes the information stored in the set ( PARI,PLI..), but the set is not deleted in the Alcatel OmniPCX
Enterprise database.

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

868
DECT System
Commands: dectsets

Display of the sets per type:

dectsets

================================================================================
Permanent handsets:
Neqt = 00297 Nbr = 3020 IPEI = 00000340311414 Type = DECT UA
Neqt = 00298 Nbr = 3021 IPEI = 00000351400620 Type = DECT UA Dereg.
Neqt = 00299 Nbr = 3030 IPEI = 00000351413612 Type = GAP
CTM shells for permanent handsets:
Total permanents handsets = 3
================================================================================
Internal visitor handsets:
Neqt = 00281 Nbr = 3023 IPEI = 00000340175164 Type = DECT UA
CTM shells for internal visitor handsets:
Total internal visitors handsets = 1
================================================================================
External visitor handsets:
Neqt = 00280 Nbr = 3022 IPEI = 00000341051760 Type = DECT UA
CTM shells for external visitor handsets:
Total external visitors handsets = 1
================================================================================
* Set in Analog Add-On configuration
================================================================================

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

Alcatel-Lucent OmniPCX Enterprise – DECT

Ref. ENTP0419M01TEUS Issue 02

870
Alcatel-Lucent OmniPCX Enterprise
Management of a DECT IBS installation

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage a DECT IBS installation

MANAGEMENT

1. Management on IBS solution

1.1. Select the radio base station type: IBS

1.2. Manage the PARI number 1000043yyx0 and assign it to the shelf.
note: yy = room number
x = node number

1.3. Create an IBS in one free UA equipment

1.4. Connect the IBS on this equipment. Check the state of the base station after a
moment.

1.5. Create the DECT sets 3x070 and 3x071. Make the registration. Check the good
working.

Issue 02 Ref. ENTP0419H02TEUS.doc HO. 1

HO. 2 Ref. ENTP0419H02TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

873
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

874
Alcatel-Lucent OmniPCX Enterprise

Direct Speed Dialing

OBJECTIVE

To describe the principle of the Direct Speed Dialing

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dialing

Ref. ENTP0408P01TEUS Issue 02

875
Direct Speed Dialing
Main features

Simplification of the dialing

When some external numbers are often called, it can be useful to use the
speed dialing numbers

A short number of the numbering plan (from 2 to 8 digits) can correspond to a

public number (up to 30 digits)

A speed dialing number can correspond to a unique number or a range of numbers

e.g.: “39000” corresponding to “0 0298131001”

e.g.: “70” corresponding to “0 01508130xx”

In this case, the subscriber has to complete the dialing 70 00 ³ 0 01508130 00
This kind of prefix is called “open” speed dialing number (prefix)

That also reduces the possible dialing mistakes

A speed dial number is easier to memorize than a complex number

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dialing

Ref. ENTP0408P01TEUS Issue 02

876
Direct Speed Dialing
Main features (Cont’)

Enhancement of the calling / called display

A name can be managed per speed dialing number

e.g. 39000 ³ Alcatel Lucent University

As soon as a name is managed in the speed dial number, the “call by name” feature
can therefore be used, if authorized(1)

Out going call

When a speed dial number is used (dialed by number or via search by name request), during
the routing, and ringing phases, the name of the speed dial is displayed
At the communication establishment, “trunk group name” is displayed

Incoming call
If the “Calling id” (ISDN message) corresponds to a speed dial number, the corresponding
“display name(3)” is shown on the called set

According to the called id recognition, a speed dial prefix can be used for
automatic substitution (in case of DISA(2) feature use)

(1) A parameter in the speed dial number allows or forbids the use of the “Called/Dial by name” feature

(2) Direct Inward System Access

(3) The display on the corresponding name is available for incoming call, only if the External Callback translator is configured !

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dialing

Ref. ENTP0408P01TEUS Issue 02

877
Direct Speed Dialing
Additional features

Call barring

According to the configuration, a speed dial number can follow or not the
Call barring feature

It can be useful to simplify the barring configuration

Prefix Called number Call Restriction

Barring
39001 0 0298131001 No

39002 10 0298131002 Yes

An user that can not call any external number, except “39001”

39001 ³ 0 0298131001 (AL Training Customer Care)

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dialing

Ref. ENTP0408P01TEUS Issue 02

878
Direct Speed Dialing
Additional features (Cont’)

Speed Dialing overflow number

It is possible to configure an overflow speed dial number

It allows to overflow automatically to an other speed dial number when the first
called number can not be reached (local trunk group unavailable(1))

Prefix Called number (2) Overflow Speed dial

number
39000 0 0298131000 39002

39002 10 0298131002

The two speed dialing numbers have to use different trunk group

If the speed dial number 39000 can not be run, the speed dial prefix 39002 will be
used
The “Overflow Speed dial number” can also be used in case of open speed dial
numbers

(1) Trunk group status “busy” or “out of order”

(2) The called number is made of a prefix (ARS or Direct seizure prefix) + an external number

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dialing

Ref. ENTP0408P01TEUS Issue 02

879
Direct Speed Dialing
Additional features (Cont’)

Timed speed dial overflow number

In the following example, if the user does not complete the number 391xx
before the end of the system timer n° 3

The system automatically dials the number contained in the prefix 39002 when a
time-out expires: 0 0156632000

Prefix Called number Timed forwarding speed

dialing number
391 0 01566320xx 39002

39200 0 0156632000

The “Timed forwarding speed dialing number” has to be complete number

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dialing

Ref. ENTP0408P01TEUS Issue 02

880
Direct Speed Dialing
Generalities

Each direct speed dialing number has its own prefix in the numbering plan

Only a unique range a “direct speed dialing numbers can be managed

A system index + a range length have to defined (from “1” to “15000” )

" 39000 " System Speed dialing

Call number Phone book name ...
Index prefix

0 39000 0 0298131000 Alcatel-Lucent University ...

Direct speed dial
number range 1 6001 00298131010 AL University Manager

First index: 0 ... ...

Size: 1000 n°
999
1000 Available area for Speed dialing
... numbers by range

Remark:
The Direct Speed dialing range can not overlap a range of speed dial numbers by range

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dialing

Ref. ENTP0408P01TEUS Issue 02

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dialing

Ref. ENTP0408P01TEUS Issue 02

882
Alcatel –Lucent OmniPCX Enterprise
Direct Speed Dialing

PROCEDURE

OBJECTIVE

- To learn how to configure the direct speed dialing

OVERVIEW

- This procedure presents how to setup the direct speed dialing. The different configuration
steps are the following ones:

- Creation of the a “free numbers range” list (ex: for 100 direct speed dialing numbers)

- Setup of the direct speed dialing range

- Creation of a direct speed dialing number

Issue 02 Ref. ENTP0408C04TEUS.doc P. 1

PROCEDURE

1. Creation of the free numbers range

Application Configuration Tab PCX

Path / System / Free numbers ranges list
Action Create
Tab All
Parameters Name: Speed Dialing
Range beginning: 39000 (e.g.)
Range End: 39099 (e.g.)
Priority + True
Digits Authorized + 0,1,2,3,4,5,6,7,8,9
Max.number: 10
Action Click on “ ” to valid

Note: This configuration is not mandatory, but is useful to predefine some numbers for a
specific use

2. Set up the Direct Speed Dialing numbers range

Application Configuration Tab PCX

Path / Speed Dialing / Direct Speed Dialing Numbers
Parameters Index for the 1rst speed dial number: 0
Length for speed dialing numbers: 100
Action Click on “ ” to valid

P. 2 Ref. ENTP0408C04TEUS.doc Issue 02

3. Speed Dialing number creation

Application Configuration Tab PCX

Path / Speed Dialing / Direct Speed Dialing Numbers / Direct Spd DI No. Pref.
Action Create
Parameters Direct Speed Dial No. Prefix: 39000
Call Number: 00298131000 (*)
Directory name: AL University
Directory First name: Welcome Desk
Call Restriction – Barring: or according to the needs
Overfll. Dir.Spd DI. No Pref: Only if expected
Timed Forward.Dir.Spd.DI.No: Only if expected
Can be Called / Dialed By Name: Yes
Action Click on “ ” to valid

Note: Directory number: select the number in the list

Note: It is possible to useUTF-8 Directory Names & First Names for specific local
characters

Issue 02 Ref. ENTP0408C04TEUS.doc P. 3

P. 4 Ref. ENTP0408C04TEUS.doc Issue 02

Direct Speed Dial

OBJECTIVE

To maintain the speed dialing numbers with the tool “edabv”

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dial

Ref. ENTP0408M01TEUS Issue 02

887
Speed Dial Numbers
Maintenance tool

The “edabv” tool uses some criteria similar to “ednump”

“edabv –l US0”

“pref” speed dial number (prefix)

“typ” type of the
“idx” prefix system index
“area” system range index
“num” Number to dial
“first” first number of speed dial range
“length” length of speed dial range
“digit” number of digits for speed dial by range
“entity” Entity number
“list” listing of the different given commands/criteria
“go” to launch the query

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dial

Ref. ENTP0408M01TEUS Issue 02

888
Speed Dial Numbers
Filtering criteria

Like the different edition tools, it is possible to filter some number thanks to
some criteria

“=” equal
“!=” different than
“>” greater than
“>=” greater than or equal
“<” lower than
“<=” lower than or equal
“[: ]” available to define a range of numbers

The criteria can be used with:

“pref”
“num”
“area”
“entity”
…

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dial

Ref. ENTP0408M01TEUS Issue 02

889
Speed Dial Numbers
Edition example

The following example displays a specific request:

To display all the configuration direct speed dial numbers included in the
range from 39xxx to 40xxx

1 - pref [39:40] -> Prefix number

2 - idx -> Speed Dialing Index No.
3 - num -> Number to dial

==========================
enter criteria or command: go
==========================

20/12/07 EDABV V. 4.00 Page: 1

+--------+----+------------------------------+
|pref |idx |num |
+--------+----+------------------------------+
|39000 | 3|00298131000 |
|39001 | 1|00298131010 |
|39002 | 2|100298131002 |
|391 | 0|0015566320 |
+--------+----+------------------------------+

Alcatel-Lucent OmniPCX Enterprise – Direct Speed Dial

Ref. ENTP0408M01TEUS Issue 02

890
Alcatel-Lucent OmniPCX Enterprise
Direct speed dialing

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage Direct Speed dialing numbers

MANAGEMENT

1. Define the direct speed dialing range (from index 0 and for 100 direct speed dialing
numbers)

2. Manage two ranges of Free numbers

2.1. 1rst number 39000, last number 39010: Name: Spd Dialing 1

2.2. 2nd number 38000, last number 38010: Name: Spd Dialing 2

3. Create a direct speed dialing number 39000

3.1. This Direct Speed Dial number has to contain a remote system number
(Call number = T2 prefix + external number)

3.2. Manage a name for this prefix

3.3. Test this prefix dialing directly the directory number, and also using the Dial by name
feature

3.4. Request the remote subscriber to call you back in order to check the display of the
speed dial number name

3.5. Use the available maintenance tools to display the direct Speed dial prefix

Issue 02 Ref. ENTP0408H01TEUS.doc HO. 1

4. Manage an open Speed dial number: “38” corresponding to the full range of DID numbers
of the same remote installation (the 3 last digits will completed by the calling user)

4.1. The trunk group prefix of the be T0 trunk group prefix

4.2. Test the speed dial number

4.3. Manage the speed dial 39000 as Overflow Spd DI number

4.4. Use the available maintenance tools to display the direct Speed dial prefix

4.5. Disconnect the T0 (or busy this trunk group)

4.6. Test the speed dial number

5. Call Restriction - Barring

5.1. Activate the barring on the system (block all out call for a user)

5.2. Modify the Speed dial number 39000 in order follow the Call Barring

5.3. Test this speed dial prefix from an user allowed to set up outbound calls, and from
an user not allowed

HO. 2 Ref. ENTP0408H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

893
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

894
Alcatel-Lucent OmniPCX Enterprise

Speed dialing by range

OBJECTIVE

To describe the speed dialing numbers by range

Alcatel-Lucent OmniPCX Enterprise – Speed dialing by range

Ref. ENTP0408P02TEUS Issue 02

895
Speed dialing by range
Principles

Speed dialing by range has the same objectives of the direct speed dialing but
it also allows to:

Define for a same call prefix:

Different numbers according to the calling set entity
Different speed dialing numbers between nodes in network

Define several call numbers for a same speed dialing number

Restrict access to some ranges according to the phone feature class of

service

Modify automatically the out dialing numbering

Use of overflow speed dialing n° and Timed overflow range N°

Identify automatically calling number

Same as direct speed dialing numbers, this speed dialing numbers can be:
• barred
• Dialed by name
• Used to identify the calling (displayed name, type of call in VIP / Normal / Local)
• Used for automatic DISA substitution
• Used in ISDN Filtering key in Executive / Assistant set

Alcatel-Lucent OmniPCX Enterprise – Speed dialing by range

Ref. ENTP0408P02TEUS Issue 02

896
Speed dialing by range
Principles

Two types of speed dialing ranges in the system

1 range of direct speed dialing numbers

This range cannot overlap the other ranges

400 ranges of speed dialing numbers by range

The ranges can overlap the others

One user can only use 32 speed dialing ranges

Use of a specific prefix Speed Dialing Area Number

This prefix is followed by an index of speed dialing number in the range

The link between ranges is defined in the entity of the user

Reminder:
•Direct speed dialing numbers are common objects inside an ABC network.
•To each direct speed dialing prefix corresponds only one call prefix in the translator.

Ranges Overlapping allows to call the same number using two different prefixes. A same number can be used in different ways.
For easy to use reasons, this configuration must be reserved for specific needs.

The maximum size of the table of speed dialing numbers is 15 000 numbers.
The default size of the table is 4 000.

Alcatel-Lucent OmniPCX Enterprise – Speed dialing by range

Ref. ENTP0408P02TEUS Issue 02

897
Speed dialing by range
Example

Common ranges for all the entities

40 : Speed dialing prefix Phone feature COS . 0 Link Entity 1
Range 0 Speed Rights Prefix Real range of Direct Speed
Dialing range of use Range spd dlg prefix dialing range
41 : Speed dialing prefix 0 1 0 0
Range 1
1 1 1 1 1st index: 0
42 : Speed dialing prefix 2 0 Length: 3000
2 2
Range 2
3 0 3 3
… … … …
29 1 29 29 Range N° 0
30 1 30 30
1st index: 3000
31 1 31 31
Length: 100
N° of digits: 2
Number Function Access Real Relative Real Number
dialed related Rights range Index Index sent

40 99 Spd rg.0 YES 0 99 3099 00298143322 Range N° 1

41 12 Spd rg.1 YES 1 12 3112 00155667000 1st index: 3100

42 38 Spd rg.2 NO 2 38 3238 00605040302 Length: 100
N° of digits: 2

Range N° 2
0298143322
1st index: 3200
ISDN Length: 100
Set 31000
Entity 1 N° of digits: 2
Phone feature COS: 0
0155667000

In this example, the table of speed dialing number is build with 3000 direct speed dialing numbers.
Modify the size of ranges in a system it’s a sensitive operation, so it’s better to do it well at first.

Numbering Analysis:
1. Set 31000 dials number 4099
• The translator determines with prefix 40 that the call concerns range index 0, the number of significant digits is
determined by management of the range (here 2 digits). So, the translator is waiting for 2 supplementary digits to
determine the location of the speed dialing number in the range.
• The phone feature COS authorizes access to range 0.
• Entity set do the link between range 0 and the real range 0 in the table of speed dialing numbers.
• The end of the number determines the index of the speed dialing number in the range, here 99.
• The range 0 begins at real index 3000, the last index is then 3099.
• This speed dialing number contains the digits to dial, that correspond to the public number 0 0298143322.
2. Set 31000 dials number 4112
• The call concerns range index 1 (prefix 41).
• The phone feature COS authorizes access to range 1 and entity points to the real range 1.
• Index is 12, range begins at 1100, the number is found in index 3112 of the table.
3. Le Set 31000 dials number 4238
• The call concerns range index 2 (prefix 42).
• This range is forbidden in the phone feature COS, the call is not authorized.
• If the call was authorized, the number found would be index 3238.

Alcatel-Lucent OmniPCX Enterprise – Speed dialing by range

Ref. ENTP0408P02TEUS Issue 02

898
Speed dialing by range
Example

Different ranges according to the entity

40 : Speed dialing prefix Link Entity 1 Link Entity 2
Range 0 Prefix Real range of Prefix Real range of
Direct Speed
Range spd dlg prefix Range spd dlg prefix dialing range
0 0 0 32
1 1 1 33 1st index: 0
2 2 2 34 Length: 3000
3 3 3 35
… … … …
Range N° 0
29 29 29 61
30 30 30 62
31 31
1st index: 3000
31 63
Length : 10
Number Function Access Real Relative Real Number N° of digits: 1
dialed related Rights range Index Index sent

Set 31000
Entity 1

0298143322

40 0 Spd rg.0 YES 0 0 3000 00298143322

Range N° 32
Set 32000
Entity 2
1st index : 3200
0605040302 Length : 10
40 0 Spd rg.0 YES 32 0 3200 00605040302
N° of digits : 1

Set 31000 is in entity 1, set 32000 in entity 2. The management of the speed dialing ranges is different for the two entities.
(from 0 to 31 for entity 1, from 32 to 63 pour for entity 2).

Numbering Analysis:
1.Set 31000 dials number 400
• The translator determines with prefix 40 that the call concerns range index 0, the number of significant digits is
determined by management of the range (here 1 digit). So, the translator is waiting for 1 supplementary digit to
determine the location of the speed dialing number in the range.
• The phone feature COS authorizes access to range 0. Entity 1 of the set do the link between range 0 and the real range 0
in the table of speed dialing numbers.
• The end of the number determines the index of the speed dialing number in the range, here 0. The range 0 begins at real
index 3000, the last index is then 3000 (corresponds to public number 0 0298143322).
2.Set 32000 dials number 400
• The translator determines with prefix 40 that the call concerns range index 0, the number of significant digits is
determined by management of the range (here 1 digit). So, the translator is waiting for 1 supplementary digit to
determine the location of the speed dialing number in the range.
• The phone feature COS authorizes access to range 0. Entity 2 of the set do the link between range 0 and the real range
32 in the table of speed dialing numbers.
• The end of the number determines the index of the speed dialing number in the range, here 0. The range 0 begins at real
index 3200, the last index is then 3200 (corresponds to public number 0 0605040302).

This configuration allows for example to do a list of speed dialing number to call companies with users changing according to the
entity of the calling.
Example : Speed dialing number 400 = Company Smith
entity 1 is coming to attendant, entity 2 to sales, entity 3 to executive, etc…

Real ranges accessible by the same logical range (given by the prefix) must have the same number of waiting digits.

Alcatel-Lucent OmniPCX Enterprise – Speed dialing by range

Ref. ENTP0408P02TEUS Issue 02

899
Speed dialing by range
Example

Different ranges according to the node of the ABC network

40 : Speed dialing prefix 41 : Speed dialing prefix
Range 0 Range 1

40 01 Number dialed 40 01
Direct Speed Direct Speed
dialing range Spd rg.0 Function related Spd rg.0 dialing range

1st index : 0 1 Relative Index 1 1st index : 0

Length : 3000 Length : 3000
3001 Real Index 3001

Range N° 0 0 0298143322 Number sent 0 0298143322 Range N° 0

1st index : 3000 1st index : 3000
Length : 100 41 12 Number dialed 41 12 Length : 100
N° of digits: 2 N° of digits: 2
Type : Network Spd rg.1 Function related Spd rg.1 Type : Network

12 Relative Index 12
Range N° 1 Range N° 1
3112 Real Index 3112
1st index : 3100 1st index : 3100
Length : 100 Length : 100
31018 Number sent 0 112
N° of digits : 2 N° of digits : 2
Type : Local Type : Local

Set 31000 Set 32000

ABC link
Node 2
Node 1

Set 31000 is on node 1, set 32000 on node 2.

The management of the speed dialing ranges is different for the two nodes. This range is locale on each node, this allows to have
different contents according to the node. The size and the position is broadcast in the network to maintain the coherency of the
network.
Numbering Analysis:
1.Sets dial number 4001
• The translator determines with prefix 40 that the call concerns range index 0. Following digits determine index of the
speed dialing number in the range.
• The type of range is Network, the content is the same in the nodes after audit and broadcast.
• The range 0 begins at real index 3000, the last index is then 3001 (corresponds to public number 0 0298143322).
2.Sets dial number 4112
The translator determines with prefix 41 that the call concerns range index 1. Following digits determine index of the speed
dialing number in the range.
• The type of range is Local, content is different in the nodes .
• The range 1 begins at real index 3100, the last index is then 3112.
• On node 1, it corresponds to internal number 31018.
• On node 2, it corresponds to public number 0 112.

This configuration is useful for emergency calls in network. If emergency exist on site, the speed dialing number will be
forwarded to local numbers. But, if there is no local emergency, it’s possible to forward to public numbers emergency.

Alcatel-Lucent OmniPCX Enterprise – Speed dialing by range

Ref. ENTP0408P02TEUS Issue 02

900
Alcatel-Lucent OmniPCX Enterprise
Direct speed dialing by range

PROCEDURE

OBJECTIVE

- To learn how to manage speed dialing by range

STEPS
Create speed dialing ranges
Create several speed dialing numbers by range using mgr tool
Use speed dial by range overflow

Issue 02 Ref. ENTP0408C03TEUS.doc P. 1

PROCEDURE

1. Modify the Speed dialing numbers by range N°0

Application mgr
Path Speed dialing / Spd Dl Numbers by Range /
Action Review/Modify
Range Number 0
Action CTRL-V
Index for 1st speed dial number 1000
Length for speed dialing numbers 100
Number of Digits 2
Used in network + Local Node
Action CTRL-V

Note: Number of Digits: Number of digits to be dialed by the user (1, 2, or 3 digits). This
number must be coherent with the length of the range: - length of range x 10: 1
digit enough, - length of range x 100: 2 digits enough, - length of range x 1000: 3
digits necessary.
Used in Network The choice is made in the menu:
- Network: the definition of the range is global on the network. The contained in
this range are the same for all the nodes.
- Local: the definition of the range is local to this node. The abbreviated numbers
contained in this range are locally defined to the node. The content of the
network ranges is automatically transmitted onto all the nodes (creation,
modification, deletion). The characteristics of the local ranges are transmitted
onto all the nodes (index of 1st abbreviated number, length...) to avoid the
same range being local on one node and network on another.

P. 2 Ref. ENTP0408C03TEUS.doc Issue 02

2. Modify the Speed dialing numbers by range N°1

Application mgr
Path Speed dialing / Spd Dl Numbers by Range /
Action Review/Modify
Range Number 1
Action CTRL-V
Index for 1st speed dial number 1100
Length for speed dialing numbers 10
Number of Digits 1
Used in network + Local Node
Action CTRL-V

Issue 02 Ref. ENTP0408C03TEUS.doc P. 3

3. Create a speed dialing Number by range with overflow

Application mgr
Path Speed dialing / Spd Dl Numbers by Range / Speed
Dialing Number
Action Create
Range Number 1
Speed Dialing No. 0
Call Number #0120201032000
Directory name Lopez
Directory First Name Jennifer
Call Restrictions – Barring + False
Overflow Range No. 0
Call Type + Normal
Timed Overflow Range No. -1
Can be Called/Dialed By Name + YES
Displayed Name
External DISA Dir.No.
Action CTRL-V
Overflow Spd Dl No. 0
Phone book Name (Dial by name)
Phone book First Name
Action CTRL-V

Note: Overflow Range No.: Is used to specify the overflow number to be called if the
trunk group used by the call number configured above is not available. Enter the
number of the range in which the overflow number is declared. -1 (no number) is
the default value.
Overflow Spd Dl No.: This parameter is only accessible if the Overflow Range No.
attribute is completed. Enter the number of the order of the overflow number in
the overflow range.
In this example, if the T2 is busy, when you use this speed dial number, there is an
overflow to range 0 and speed dial n° 0 (but GSM number outgoing with T0).

P. 4 Ref. ENTP0408C03TEUS.doc Issue 02

4. Create a speed dialing Number by range

Application mgr
Path Speed dialing / Spd Dl Numbers by Range / Speed
Dialing Number
Action Create
Range Number 0
Speed Dialing No. 0
Call Number #0100675936700
Directory name Lopez
Directory First Name Jennifer
Call Restrictions – Barring + False
Overflow Range No. -1
Call Type + Normal
Timed Overflow Range No. -1
Can be Called/Dialed By Name + NO
Displayed Name
External DISA Dir.No.
Action CTRL-V

5. Manage the entity speed dialing Numbers Range

Application mgr
Path Entities / Entity Spd Dial Numbers Range
Action Review / Modify
Entity Number 1
Speed Dialing Area 0 0
Speed Dialing Area 1 1
Speed Dialing Area 31 31
Action CTRL-V

Issue 02 Ref. ENTP0408C03TEUS.doc P. 5

6. Create speed dialling area prefixes

Application mgr
Path Translator / Prefix Plan
Action Create
Number 2
Prefix Meaning + Speed Dialing Area
Action CTRL-V
Prefix Information 0
Action CTRL-V
Path Translator / Prefix Plan
Action Create
Number 6
Prefix Meaning + Speed Dialing Area
Action CTRL-V
Prefix Information 1
Action CTRL-V

7. Authorize the access to speed dial ranges

Application mgr
Path Classes of Service / Phone Features COS
Action Review / Modify
Phone Features COS 0
Speed Dialing Area
Area 0 1
Area 1 1
Area 31 1
Action CTRL-V

P. 6 Ref. ENTP0408C03TEUS.doc Issue 02

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to set the speed dialing numbers by range.

MANAGEMENT

1. Manage the speed dialing number range #0 that uses the system indexes 1000 to 1099.
Manage the outside number “#0x202yy3z000” in the abbreviated number 0 contained in it.

2. Manage the speed dialing number range #1 that uses the system indexes 1100 to 1109.
Manage the outside number “#0x202yy3z001” in the abbreviated number 0 contained in it.

3. Manage the entity speed dialing Numbers Range.

4. Create speed dialing area prefixes.

5. Authorize the access to dial speed ranges.

Issue 02 Ref. ENTP0408H02TEUS.doc HO. 1

HO. 2 Ref. ENTP0408H02TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

909
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

910
Alcatel-Lucent OmniPCX Enterprise

Alcatel-Lucent OmniMessage 4645

OBJECTIVE

To describe Alcatel-Lucent OmniMessage 4645 voice mail application

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

911
Alcatel-Lucent OmniMessage 4645
Overview

The Alcatel-Lucent OmniMessage 4645 is a software solution voice mail

Hosted on the OmniPCX Enterprise call server (IPRS & IPAS configurations)(1)
No need of a specific hardware

The signaling between Alcatel-Lucent OmniMessage 4645 and the call server is
done according to ABC-A protocol

The “audiomaster” function allows some voice guides customization such as:
Company greeting / Automatic attendant menu...

The basic voices guides can be recorded by the “Audio-Station” (2)

Voice mail networking (VPIM(3))

1) Definition : IPRS: IP Rack Server / IPAS: IP Appliance Server

This Voice mail solution can not be set up in case of Crystal hardware Call Server

2) No basic voice guides recording on digital sets

3) VPIM: Voice Profile for Internet Mail

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

912
Alcatel-Lucent OmniMessage 4645
Capacities

Maximum number of accesses

16 on Appliance Server or 8 on CPU CS (1)

The accesses numbers is not a software lock

Maximum number of mailboxes:

1000 mailboxes

Size of voice messages:

From 1 minute to 5 hours

Maximum number of messages per mailbox:

From 5 to 100 (according to the management)

Size of vmu partition used on the hard drive:

1.5 Go (that is about 40 Hours recording)

1 )with the CPU-CS, two configurations are possible:

- With the Call handling + 4645 8 accesses available
- With only the 4645 16 accesses available from R5.1.2 (before only 8)

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

913
Alcatel-Lucent OmniMessage 4645
Capacities

Maximum length of the greeting messages

from 10 seconds to 5 minutes according to management

Number of languages
8 maximum, 1 by default (software lock)

Size of the numbering plan

from 3 to 8 digits

Automated attendant

Distribution lists
Maximum of 50 members

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

914
Alcatel-Lucent OmniMessage 4645
Features

Voice messaging services

Standard and guest mailboxes

Skip password

Variable password length (3 to 8 digits)

Default behavior for non-existing mailboxes (the caller is transferred to a

fixed default automated attendant)

Messages reading, recording and mailing

Mailboxes customization

Distribution list

IMAP4(1) access

1) Internet Message Access Protocol version 4

This Protocol allows to retrieve the Voice messages from a Mail account

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

915
Alcatel-Lucent OmniMessage 4645
Features

Voice messaging services

Dynamic keys use on digital sets for the different facilities

2 possibilities for notification:

Standard messages notification
Urgent messages notification

Auto-play for direct voice mail call

Hotel facilities
Check-in
Check-out
Multi-language

Record on-line

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

916
Alcatel-Lucent OmniMessage 4645
Features: Automated Attendant

Direct call of the AA (Automated Attendant) menu

Supervised transfer

Call pre-routing: “Company Greeting”

Language selection

Multi-level with multiple entries

Audiotex feature

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

917
Alcatel-Lucent OmniMessage 4645
Features: Ubiquity

Default settings
If there is no personal greeting, a default greeting message is provided

Ubiquity template concept which provides a model of key association for

Ubiquity subscribing

Ubiquity is available only for standard mailboxes

9 transfer destinations possible

Mobile phone number programming feature via prefix

(see phone facilities categories)

Fax detection
In case of fax tone detection , possibility to route the fax call to a
pre-programmed fax extension number

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

918
Alcatel-Lucent OmniMessage 4645
Software locks

Number of mailboxes (nb * 10)

Scheduled Packages (must match the “engine” capability):

50
200
500
+500

Number of languages
First language free

Number of ubiquity users

The 16 firsts free

Centralized voice mail

Network pack
VPIM

Number of mailboxes: sold by package of 10

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

919
Alcatel-Lucent OmniMessage 4645
Environment and architecture

A single voice mail can manage all type of sets

IP Alcatel-Lucent
OmniMessage 4645
Network

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

920
Alcatel-Lucent OmniMessage 4645
Environment and architecture

Configuration 1

The call server and the voice mail are embedded on the same CPU

e-CS + Alcatel-Lucent e-CS + Alcatel-Lucent

OmniMessage 4645 OmniMessage 4645

Common hardware Appliance server:

8 ports 16 ports

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

921
Alcatel-Lucent OmniMessage 4645
Environment and architecture

Configuration 2

The call server and the voice mail are working on 2 separated CPU

Alcatel-Lucent
CS 4645

IP
Network

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

922
Alcatel-Lucent OmniMessage 4645
Environment and architecture

Configuration 3

The call server main and the call server stand-by are separated from the
voice mail CPU

It is the call server main which insures the voice mail working

e-CS Main e-CS Stand by

Alcatel-Lucent
OmniMessage
4645

IP
Network

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

923
Alcatel-Lucent OmniMessage 4645
Environment and architecture

Configuration 4

In this configuration the voice mail is embedded on the main call server CPU

In case of main call server breakdown , the voice mail depends on the stand-by call
server

e-CS Stand by e-CS Main

Alcatel-Lucent
OmniMessage
4645
IP
Network

Caution: The voice mail is not duplicated

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

924
Alcatel-Lucent OmniMessage 4645
Environment and architecture

Configuration 4: switch-over

Status after call server switch-over

The previous Main Call Server has become Stand-by, and the Alcatel-Lucent
OmniMessage 4645 is still driven by the Main CPU

e-CS Main e-CS Stand by

Alcatel-Lucent
OmniMessage
4645
IP
Network

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

925
Alcatel-Lucent OmniMessage 4645
Environment and architecture

Telephone working and IP environment

G711
e-CS Alcatel-Lucent
4645

IP
G711
Network

G723
e-MG

X8 Series
extension

If the IP user does not work with the G711 algorithm , it is the e-MGD board which will insure the conversion G723 -> G711 or
G729 -> G711.
The voice mail work only with G711 algorithm.
The x8 Series extension can switch automatically in G711 when it works in direct RTP with the voice mail , so it does not need
compressors on e-MGD board

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent OmniMessage 4645

Ref. ENTP0432P01TEUS Issue 02

926
Alcatel-Lucent OmniPCX Enterprise
Alcatel-Lucent 4645 with mgr

PROCEDURE

OBJECTIVE

- To learn how to put into operation Alcatel-Lucent 4645 with mgr

OVERVIEW
The Alcatel-Lucent 4645 voice mail system has been developed for integration in telephone
systems running in an IP environment.
The 4645 voice mail system can operate:

- either on the same physical support as the Call Server: CS board or Appliance Server or on a
dedicated server: CS board or Appliance Server.

Issue 04 Ref. ENTP0432C01TEUS.doc P. 1

PROCEDURE

1. Alcatel-Lucent 4645 on a dedicated server: CS board or Appliance Server

Alcatel
4645
CS
Host name : ev001001
Host name : xa001001
IP @IP : 10.S.X.15
@IP : 10.S.X.1
Network

P. 2 Ref. ENTP0432C01TEUS.doc Issue 04

1.1. Check Software lock with spadmin command

Application On the call server

Login mtcl
Command spadmin
Display current counters ........................... 1
Result
Display active file ................................ 2
Check active file coherency ........................ 3
Install a new file ................................. 4
Read the system CPUID .............................. 5
CPU-Ids management ................................. 6
Display active and new file ........................ 7
Display OPS limits ................................. 8
Display ACK code ................................... 9
Exit ............................................... 0
choice:

Entry 2
DLL version = 0110
Result
File version = 0
OXE version = 0110
Soft Key = 498225a88be17b743
178-4645 Voice mail engin = 1
179-4645 users = 400 (0)
181-OmniPCX Enterprise (1 = 1
182-4645 networking = 1
183-4645 additionnal lang = 5
184-Integrated gatekeeper = 9999
185-SIP Gateway = 9999
186-E-CS redundancy = 1
194-4645 Portal users = 80
195-CCD Profile (Starter= = 0

Remark In that case, the system has a voice mail service with 400 mailboxes
available and working in a network configuration (VPIM service).
Fives languages are available in this system and eighty mailboxes have a
portal access.
Before to start to bring into service the voice mail system, it’s mandatory to
Create an empty database on the CPU 4645.

Issue 04 Ref. ENTP0432C01TEUS.doc P. 3

1.2. Declare the name and IP address of the CPU 4645

Application On the call server

Login mtcl
Command netadmin
Warning: for a specific setup please use menu mode (netadmin -m).
Result
Do you want to erase the existing setup (y/n default is 'n') ?

Entry Y
Do you intend to use IP/X25 on your system (y/n default is 'n') ?
Result
Entry N
Enter local CPU position (a or b) for duplicated configuration
Result
or n for single CPU (default is 'n') ?

Entry N
Ethernet interface setup
Result
========================
CPU name (default is xa000000) ?

Entry ev001001
CPU address (default is 10.253.253.1) ?
Result
Entry 10.1.1.15
Network mask (default is 255.255.255.192) ?
Result
Entry 255.255.255.0
====================
Result
Default router setup
====================
Do you use an external gateway as default router (y/n default is n) ?

Entry N
Security
Result
========
Do you want to enhance security (y/n, default is y) ?

P. 4 Ref. ENTP0432C01TEUS.doc Issue 04

1.3. Declare the IP address and name of the CPU CS in the CPU 4645 Host file

Application On the call server

Login mtcl
Command netadmin -m
Alcatel e-Mediate IP Network Administration
Result
1. 'Installation'
2. 'Show current configuration'
3. 'Local Ethernet interface'
4. 'CPU redundancy'
5. 'Role addressing'
6. 'Serial links (PPP)'
7. 'Tunnel'
8. 'Routing'
9. 'Host names and addresses'
10. 'Copy setup'
11. 'Security'
12. 'DHCP configuration'
13. 'SNMP configuration'
14. 'VLan configuration'
15. 'Node configuration'
16. 'History of last actions'
17. 'Apply modifications'
0. 'Quit'
What is your choice ?

Entry 9
9.Host names and addresses
Result
==========================
1. 'Host database update'
2. 'Aliases'
0. 'Previous menu'
What is your choice ?

Entry 1
9.1.Host database update
Result
========================
1. 'View'
2. 'Add/Update'
3 'Delete'
0. 'Previous menu'
What is your choice ?

Entry 2
Host database update
Result
====================
Host name ?

Entry xa001001

Issue 04 Ref. ENTP0432C01TEUS.doc P. 5

Host address (default is 10.1.1.1) ?

Result
Entry 10.1.1.1
9.1.Host database update
Result
========================
1. 'View'
2. 'Add/Update'
3 'Delete'
0. 'Previous menu'
What is your choice ?

Entry a

1.4. Check IP address and name of the CPU-CS

Application On the call server

Entry 3
3.Local Ethernet interface
Result
==========================
1. 'View'
2. 'Update'
0. 'Previous menu'
What is your choice ?

Entry 1

P. 6 Ref. ENTP0432C01TEUS.doc Issue 04

Ethernet interface setup

Result
========================
Internet name : xa001001
Internet address: 10.1.1.1
Netmask : 255.255.255.0
3.Local Ethernet interface
==========================
1. 'View'
2. 'Update'
0. 'Previous menu'
What is your choice ?

Entry 0 (as many times as needed)

1.5. Add IP address and name of the CPU 4645 in the CPU-CS host file

Application On the call server

Entry 9
9.Host names and addresses
Result
==========================
1. 'Host database update'
2. 'Aliases'
0. 'Previous menu'
What is your choice ?

Issue 04 Ref. ENTP0432C01TEUS.doc P. 7

Entry 1
9.1.Host database update
Result
========================
1. 'View'
2. 'Add/Update'
3. 'Delete'
0. 'Previous menu'
What is your choice ?

Entry 2
Host database update
Result
====================
Host name ?

Entry ev001001 (cpu Alcatel-Lucent 4645 )

Host address ?
Result
Entry 10.1.1.15
9.1.Host database update
Result
========================
1. 'View'
2. 'Add/Update'
3. 'Delete'
0. 'Previous menu'
What is your choice ?

Entry a
0 (as many times as needed)

P. 8 Ref. ENTP0432C01TEUS.doc Issue 04

1.6. Database management on call server (CPU CS)

Application On mgr
Select Application/Voice mail
Action Review /Modify
Entry Voice Mail Dir.No.: (for example: 31500)
Directory Name: (for example: voice mail)
Voice Mail Type + 4645
Voice Mail CPU Name: ev001001
Action Press CTRL+v to validate the creation
Press CTRL+c as many times as needed to come back on main menu
Remark Voice Mail CPU Name:
Name or IP address where is implemented The Alcatel-Lucent 4645
(warning: don’t use role address)
After the voice mail number directory creation one shelf is automatically
created , Alcatel-Lucent 4645 is seen as a rack in the call server

1.7. Check the presence of 4645 voice mail and eva.cfg files

Application On the call server

Login mtcl
Command config 18
| Cr | cpl| cpl type | hw type | cpl state | coupler ID |
Result
|----|----|------------|-----------|--------------|-----------------|
| 18 | 0 | GD |---------- | IN SERVICE | NO PCMS CODE |
| 18 | 1 | 4645 |---------- | IN SERVICE | NO PCMS CODE |
--- Inter Crystal Topology ---
+--------------------------------------------------------------------+
| CR | CPL Type Role Free/Tot Role Type CPL | CR |
|------------------------------------------------------------------- |
| 18 | 00 - GD (MAIN ) --- 24/24 --- ( INT_A) INTIPA - 01 | 19 |

Command more /usr3/mao/eva.cfg

Result callserver1=10.1.1.1
eva=10.1.1.15

Issue 04 Ref. ENTP0432C01TEUS.doc P. 9

2. Alcatel-Lucent 4645 on the call server

P. 10 Ref. ENTP0432C01TEUS.doc Issue 04

2.1. Check software locks with spadmin command

Application On the call server

Issue 04 Ref. ENTP0432C01TEUS.doc P. 11

2.2. Database management on call server (CPU-CS)

Application On mgr
Select Application/Voice mail
Action Review /Modify
Entry Voice Mail Dir.No.: (for example: 31500)
Directory Name: (for example: voice mail)
Voice Mail Type + 4645
Voice Mail CPU Name: localhost
Action Press CTRL+v to validate the creation
Press CTRL+c as many times as needed to come back on main menu
Remark Voice Mail CPU Name:
Name or IP address where is implemented The Alcatel-Lucent 4645
(warning: don’t use role address)
After the voice mail number directory creation one shelf is automatically
created , Alcatel-Lucent 4645 is seen as a rack in the call server

2.3. Check the presence of 4645 voice mail and eva.cfg files

Application On the call server

Login mtcl
Command config 18
| Cr | cpl| cpl type | hw type | cpl state | coupler ID |
Result
|----|----|------------|-----------|--------------|-----------------|
| 18 | 0 | GD |---------- | IN SERVICE | NO PCMS CODE |
| 18 | 1 | 4645 |---------- | IN SERVICE | NO PCMS CODE |
--- Inter Crystal Topology ---
+--------------------------------------------------------------------+
| CR | CPL Type Role Free/Tot Role Type CPL | CR |
-------------------------------------------------------------------- |
| 18 | 00 - GD (MAIN ) --- 24/24 --- ( INT_A) INTIPA - 01 | 19 |

Command more /usr3/mao/eva.cfg

callserver1=10.1.1.1
Result
eva=10.1.1.1

P. 12 Ref. ENTP0432C01TEUS.doc Issue 04

PROCEDURE

OBJECTIVE

- To learn how to allocate mailboxes to users with mgr

OVERVIEW
The Standard mailbox is commonly used for voice mail services.
It is dedicated to a set (UA, Z or IP) whose owner is the only person allowed to access and to
manage messages. When the user connects to his mailbox for the first time, he must record his
name and enter a secret code that will be requested at each subsequent connection.

Issue 02 Ref. ENTP0432C02TEUS.doc P. 1

PROCEDURE

1. Assign voice mail service to a user

Application On mgr
Select Users
Entry Directory number: (for example: 31000)
Voice Mail Dir.No.: (for example: 31500)
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many times as needed to come back on main menu

2. Manual configuration for initial access of a voice mailbox

Application On the phone set

Action Dial the voice mail directory number: 31500
Action Enter the Secret code : 0000
(provided by your administrator for initial access to your voice mailbox or
your personal code)
Action Enter your new secret access code: (for example: 2580)
Press # to confirm the End of code entry
Action
1 to change the code previously entered
Action record your name
Press # for end recording
Action
1 To record again
Action Press # To confirm the recording
Action Off hook the phone set

P. 2 Ref. ENTP0432C02TEUS.doc Issue 02

3. Check the voice mailbox creation

Application On the call server

Login mtcl
Command Eva_tool
MANAGEMENT TOOL
Result
0 : End
1 : Delete a mailbox
2 : Modify a password
3 : Delete all messages from mailbox
4 : Delete messages
5 : Dump nodes, mailboxes and messages
6 : Reset a port
7 : Update led
8 : Status of lines
9 : Disable lines after hanging up
10 : Force disable all lines
11 : Enable all lines
12 : Interactif import of greeting
13 : Automatic import of greetings
14 : Mov_debug
Your choice :
Entry 5
0 : End
Result
1 : List mailboxes and nodes
2 : Dump local mailbox
3 : Dump node
4 : Dump network mailbox
5 : Dump all
6 : Dump messages
7 : Dump rate of occupation of messages on the disc
8 : Dump COS
Your choice :

Issue 02 Ref. ENTP0432C02TEUS.doc P. 3

Entry 1
EVA_TOOL : DumpMailboxList
Result
EVA_TOOL : number of mailboxes 5 of 1000
EVA_TOOL : Nb MCDU TYPE NAME
EVA_TOOL : 0 | 00 | 6 | Administration Mailbox
EVA_TOOL : 1 | 01 | 4 | Default Automated Attendant
EVA_TOOL : 2 | 3100 | 1 | CALAGAN MOISE
EVA_TOOL : 3 | 3170 | 1 | JOHN SMITH
EVA_TOOL : 4 | 3120 | 1 | BOBO
EVA_TOOL : Dumpnetworkmailboxes
EVA_TOOL : number of network mailboxes 0 of 50000
EVA_TOOL : Nb MCDU VM_NODE_NUMBER NAME
EVA_TOOL : Dumpnetworknode
EVA_TOOL : number of network nodes 0 of 500
EVA_TOOL : Nb MCDU TYPE NAME

0 : End
1 : List mailboxes and nodes
2 : Dump local mailbox
3 : Dump node
4 : Dump network mailbox
5 : Dump all
6 : Dump messages
7 : Dump rate of occupation of messages on the disc
8 : Dump COS
Your choice :
Entry 0
MANAGEMENT TOOL
Result
0 : End
1 : Delete a mailbox
2 : Modify a password
3 : Delete all messages from mailbox
4 : Delete messages
5 : Dump nodes, mailboxes and messages
6 : Reset a port
7 : Update led
8 : Status of lines
9 : Disable lines after hanging up
10 : Force disable all lines
11 : Enable all lines
12 : Interactif import of greeting
13 : Automatic import of greetings
14 : Mov_debug
Your choice :
Entry 0

P. 4 Ref. ENTP0432C02TEUS.doc Issue 02

Alcatel-Lucent 4645

OBJECTIVE

To maintain Alcatel-Lucent 4645 voice mail application

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4645

Ref. ENTP0432M01TEUS Issue 02

943
Alcatel-Lucent 4645
Maintenance

The Eva_tool is a simple tool used for Alcatel-Lucent 4645 maintenance

The “auditmevo” command on the call server allows to update the Alcatel-
Lucent 4645 data base according to e-CS data base. This command is very
useful specially if case of Alcatel-Lucent4645 hard disk failure

This command can be helpful in case of 4645 hard drive change, so, it would
avoid to recreate all the mail boxes in the Call server data base

The « auditmevo » command works only in call server (Alcatel-Lucent 4645).

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4645

Ref. ENTP0432M01TEUS Issue 02

944
Alcatel-Lucent 4645
Maintenance

Eva_tool maintenance tool description (Telephone application started)

This command is launched under the mtcl account on the CPU supporting the
Alcatel-Lucent 4645

Depending on the telephone application status, the main menu do not offer
same functions

Main Options when telephonic application is started

2: Modify a password

5: Dump nodes, mailboxes and messages

8: Status of lines

(1)xa000000> Eva_tool

MANAGEMENT TOOL

0 : End
1 : Delete a mailbox -> Used to delete a mailbox in Alcatel-Lucent 4645 data base
2 : Modify a password -> Used to modify in Alcatel-Lucent 4645 database a user password
3 : Delete all messages from mailbox -> Use to delete all the messages in one mailbox
4 : Delete messages -> Used to delete messages according to some criteria
(duration, date, user mailbox ..)
5 : Dump nodes, mailboxes and messages -> To display information about local or network mail boxes
6 : Reset a port -> To reset an e-Va access
7 : Update led -> Used to update the led status on sets
8 : Status of lines -> Status of e-Va accesses.
9 : Disable lines after hanging up -> Used to isolate the voice mail accesses after the last hang-up
10: Force disable all lines ->Force the accesses isolation even one user is connected
11: Enable all lines -> Used to unfreeze the voice mail accesses after isolation( menu 9 and 10)

12: Interactif import of greeting -> Used to import interactive voice greeting
13: Automatic import of greetings ->Automatic import of automated voice greeting

14: Mov_debug -> Reserved for R&D department

Your choice:

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4645

Ref. ENTP0432M01TEUS Issue 02

945
Alcatel-Lucent 4645
Maintenance

Eva_tool maintenance tool description (next)

Main options when telephone application is stopped

1: List mailboxes and nodes

7: Dump rate of occupation of messages on the disc

10: 4645 partition check

((E)xa000000> Eva_tool
erreur mapping Remant -7

0 : End
1 : List mailboxes and nodes -> List of mailboxes known by e-Va 4645
2 : Dump local mailbox -> Information on mail boxes(local users)
3 : Dump node -> Information on mail boxes(network users)
4 : Dump network mailbox -> Information on mail boxes of an external mail service
5 : Dump all -> Information about e-Va (AA, mail boxes, etc)
6 : Dump messages -> Information about messages
7 : Dump rate of occupation of messages on the disc -> display the using percentage of e-Va
9 : 4645 partition format -> To manually format dedicated CMU partition
10: 4645 partition check -> Test of the VMU partition dedicated to e-Va 4645

Your choice:

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4645

Ref. ENTP0432M01TEUS Issue 02

946
Alcatel-Lucent 4645
Maintenance
Telephone
Eva_tool maintenance tool description (next)
Application
started
Display information on mail boxes

Your choice:5

0: End
1: List mailboxes and nodes
2: Dump local mailbox
3: Dump node
4: Dump network mailbox
5: Dump all
6: Dump messages
7: Dump rate of occupation of messages on the disc
8: Dump COS

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4645

Ref. ENTP0432M01TEUS Issue 02

947
Alcatel-Lucent 4645
Maintenance

Eva_tool maintenance tool description (next)

Menu 5 then 1: List mailboxes and nodes

VFMPRINTFAT: 0 | 00 | 6 | Administration Mailbox

VFMPRINTFAT: 1 | 01 | 4 | Default Automated Attendant
VFMPRINTFAT: 2 | 33003 | 1 | Lambert Gerard
VFMPRINTFAT: 3 | 33004 | 1 | Le Du Pierre
VFMPRINTFAT: 4 | 33081 | 3 | Entree OP
VFMPRINTFAT: 5 | 33082 | 3 | AAE2
VFMPRINTFAT: 6 | 33030 | 5 | Liste de dis
VFMPRINTFAT: 7 | 33801 | 8 | 33801
VFMPRINTFAT: 8 | 33061 | 7 | 33061
VFMPRINTFAT: Dumpnetworkmailboxes
VFMPRINTFAT: number of network mailboxes 0 of 50000
VFMPRINTFAT: Nb MCDU TYPE NAME
VFMPRINTFAT: Dumpnetworknode
VFMPRINTFAT: number of network nodes 0 of 500
VFMPRINTFAT: Nb MCDU TYPE NAME

Mailbox type:
1: Standard mailbox
3: Automated attendant entry
5: Distribution list
7: Ubiquity Ubiquity assistant template mailbox
8: Ubiquity subscribing mail box

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4645

Ref. ENTP0432M01TEUS Issue 02

948
Alcatel-Lucent 4645
Maintenance

Eva_tool maintenance tool description (next)

Menu 5 then 2: Dump local mailbox

31101
++++++++++++++++++++++++++++++++++++++++++++++++++++
dir_number = 31101
dir_name = IP Truc
recorded_name: msg_ref[]=01.01.00.00
language=1
pbx_node_number=1
vm_node_number=0
password.crypt=56416.46753.15430.58384
temporary_password=0
password_failed 0
password_timestamp Tue May 9 13:29:46 2000
cos_index=1imap_uid_validity = 957871739
imap_uid_last = 1
Type = STANDARD_MBX
.............................
EVA_TOOL: 2

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4645

Ref. ENTP0432M01TEUS Issue 02

949
Alcatel-Lucent 4645
Maintenance

Eva_tool maintenance tool description(next) Telephone

Application
VMU partition format stopped

This operation is not mandatory, because the formatting is performed

automatically during the Alcatel-Lucent 4645 set-up.

For troubleshooting purpose, we can reformat the partition by using choice 9 of the
menu

VMU partition check

The integrity check of the partition can be launched if needed by using choice 10 of
the menu

The VMU partition is the one dedicated to the e-Va on the call server hard drive.

Alcatel-Lucent OmniPCX Enterprise – Alcatel-Lucent 4645

Ref. ENTP0432M01TEUS Issue 02

950
Alcatel-Lucent OmniPCX Enterprise
Alcatel-Lucent 4645

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to bring into service the Alcatel-Lucent 4645 voice mail

MANAGEMENT

1. Alcatel-Lucent 4645 on the e-CS CPU.

1.1. Configuration (X = Node number)

1.2. Create the 3X500 extension call number for 4645 on the CPU.

1.3. Check the presence and the contain of the eva.cfg file on the CPU.

1.4. Do a shutdown of the CPU.

1.5. At the end of the shutdown use the command config to check that the voice mail is
correctly in service.

1.6. Create a voice mailbox on some internal users, test the voice message sending and
receiving.

Issue 04 Ref. ENTP0432H01TEUS.doc HO. 1

HO. 2 Ref. ENTP0432H01TEUS.doc Issue 04

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

953
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

954
Alcatel-Lucent OmniPCX Enterprise

V24/IP box

OBJECTIVE

To describe the remote V24/IP box

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444P01TEUS Issue 04

955
V24/IP box
Overview

Context

Solution

Hardware characteristics

Software

Installation

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444P01TEUS Issue 04

956
V24/IP box
Overview

Context

Many OmniPCX applications require serial ports V24

(hotel, login, billing system,…)

The number of V24 ports on the call server is limited to 1 (CPU-CS or

Appliance Server)

It may be necessary to provide more ports for the applications

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444P01TEUS Issue 04

957
V24/IP box
Overview

Solution

Use a device connected to the LAN supplying one interface between the IP
world and V24 serial link applications

IP
Call
Network
server
login

Remote
Maintenance
V24
V.24/IP Box connection
Real time
accounting

Console
V24

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444P01TEUS Issue 04

958
V24/IP box
Overview

The hardware solution selected by Alcatel-Lucent is:

The box Nport Server Lite DE.304 provided by the manufacturer, MOXA

Characteristics
4 x V24 ports RS 232
IP link 10/ 100 base T (auto-detection)
possible configuration on the front panel (IP@, mask, router) via a menu on
LCD screen

Several boxes can be set up on one system

Web site: www.moxa.com

On management, 4 boxes can be set up.

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444P01TEUS Issue 04

959
V24/IP box
Overview

Software
The LINUX drivers and tools required to set up the box are integrated in the
call server

For MOXA, a process which provides the link between the IP world and the
V24 ports, is launched on CS: moxatty

The Nport server has an IP configuration (IP@, mask, router)

The data are transferred from the CS to this IP address and are routed to the
V24 ports through specific TCP ports (950-953)

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444P01TEUS Issue 04

960
V24/IP box
Overview

Installation

The installation is performed in 3 steps:

on the MOXA box: IP configuration environment (IP@, mask, router),

on the CS: remote V24 box creation (IP@),

on the CS: association between V24 ports and application,

For example association between the application login and the port which is linked to the IP
address on the V24 remote box.

In case of spatial redundancy, the CPU which will be MAIN needs about one minute to access to the MOXA box.
If there is no spatial redundancy , the CPU can immediately access to the MOXA box.

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444P01TEUS Issue 04

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444P01TEUS Issue 04

962
Alcatel-Lucent OmniPCX Enterprise

V24/IP box

OBJECTIVE

To manage a remote IP V24 box

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444C01TEUS Issue 05

963
V24/IP box
Management

MOXA box installation

Remote V24 box creation

Association between V24 port and an application

Example of application: hotel menu

V24 ports configuration upgrade

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444C01TEUS Issue 05

964
V24/IP box
Management

MOXA box installation

Switch on the box and connect it to the CS LAN

a green LED on the front panel indicates the status of the physical Ethernet
connection

Manage the box IP configuration through the integrated menu on the screen

Menu key

Select NETWORK SETTING using the arrow buttons LM

enter the values: IP ADDRESS, NETMASK, GATEWAY

Back to main menu and select SAVE/RESTART

To configure the MOXA box, 2 methods:

-use the menu key and the LCD screen (see above),
-open a telnet session.

Example of a telnet session on Nport server

telnet 155.132.1.55 (IP@ of the MOXA box)
Console terminal type (1: ansi/vt100, 2: vt52): 1
MOXA NPort Server Lite V2.00
--------------------------------------------------------------------------------
[serverConfig] Serialport Diagnostic Monitor Ping Restart Exit
Config server settings

ESC: back to menu Enter: select

Server Model DE-304
Server Name [NP10473 ]
Serial Number 10473
Operating Mode [Host Based Mode ]
DHCP [Disable ]
Ethernet Status 100M/Link
MAC Address 00:90:E8:04:28:E9
IP Address [155.132.1.55 ]
Netmask [255.255.0.0 ]
Gateway [ ]
Password [ ]

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444C01TEUS Issue 05

965
V24/IP box
Management

Remote V24 box creation

System / Remote V24 box / Create

Number 1 (up to 4)
Type + Moxa Nport Server Lite
IP Address IP@ of the box
Number of ports 4

The process /usr/etc/moxatty/moxattyd runs.

4 new ports are handle in the data base per created box.

Up to 4 boxes can be set up, then the limit of extra V24 ports is 4 x 4 ports = 16.

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444C01TEUS Issue 05

966
V24/IP box
Management

Association between V24 port and an application

System / V24 port / Consult-Modify

Port /dev/rv24/b1/tty1 (or tty2, tty3, tty4)
V24 No 45 (or 46,47,48)
RTS/CTS protocol False
Dynamic + False
TA Directory No -------
Speed 9600
Parity None
Data bits 8 bits
Stop bit 1 bit
Terminal type VT100
V24 Application + Hotel Menu
Parameters -------
Port Dir. Nb (Static) -----

The name and number of all the ports:

/dev/rv24/b1/tty1 (45) Port 1 of box 1
/dev/rv24/b1/tty2 (46) Port 2 of box 1
/dev/rv24/b1/tty3 (47) Port 3 of box 1
/dev/rv24/b1/tty4 (48) Port 4 of box 1
/dev/rv24/b2/tty1 (77) Port 1 of box 2
/dev/rv24/b2/tty2 (78) Port 2 of box 2
/dev/rv24/b2/tty3 (79) Port 3 of box 2
/dev/rv24/b2/tty4 (80) Port 4 of box 2
/dev/rv24/b3/tty1 (109) Port 1 of box 3
/dev/rv24/b3/tty2 (110) Port 2 of box 3
/dev/rv24/b3/tty3 (111) Port 3 of box 3
/dev/rv24/b3/tty4 (112) Port 4 of box 3
/dev/rv24/b4/tty1 (141) Port 1 of box 4
/dev/rv24/b4/tty2 (142) Port 2 of box 4
/dev/rv24/b4/tty3 (143) Port 3 of box 4
/dev/rv24/b4/tty4 (144) Port 4 of box 4

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444C01TEUS Issue 05

967
V24/IP box
Management

Upgrade of the V24 ports configuration with the management tool

System / Remote V24 box / Apply modif. to remote V24 box

Some V24 ports parameters can be directly modified with mgr (System / V24 port / Consult-Modify):
-speed,
-parity,
-stop bit,
-data bits,
-XON/XOFF protocol.
These information will be transferred to the MOXA box by applying the modifications with mgr (System / Remote V24 box /
Apply modif. to remote V24 box).

The MOXA restarts and the result is seen by system messages:

-Fail: “1467: Fail to configure MOXA IP@”,
-Success: “1466: The MOXA IP@ configuration succeed”.

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444C01TEUS Issue 05

968
Alcatel-Lucent OmniPCX Enterprise

V24/IP box

OBJECTIVE

To provide V24/IP box maintenance

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

969
V24/IP box
Maintenance

MOXA process
ps -edf | grep moxa
root 533 10 Apr21 00:00:01 /usr/etc/moxatty/moxattyd -t 1

Symbolic links and ports

(1)xa000002> cd /dev/rv24/b1/
(1)xa000002> lm tty*
lrwxrwxrwx 1 root root 10 Mar 19 13:30 tty1 -> /dev/ttyef
lrwxrwxrwx 1 root root 10 Mar 19 13:30 tty2 -> /dev/ttyee
lrwxrwxrwx 1 root root 10 Mar 19 13:30 tty3 -> /dev/ttyed
lrwxrwxrwx 1 root root 10 Mar 19 13:30 tty4 -> /dev/ttyec

moxatty file.cf content (after configuration)

(1)xa000002 > more /usr/etc/moxatty/moxattyd.cf
ttyef 155.132.1.55 950
ttyee 155.132.1.55 951
ttyed 155.132.1.55 952
ttyec 155.132.1.55 953

Repertory /usr/etc/moxatty content:

npadm (internal program of installation and configuration of the box)
moxattyd (Daemon allowing the working, once it is setup)
moxattyd.log (file containing the information given by moxattyd at startup)
moxattyd.cf (configuration file of the ports made via npadm)
killp (necessary to npadm and moxattyd)
config (line automatically added in the file /etc/inittab)
version (version of the package)

ttyef 155.132.2.55 950

ttyee 155.132.2.55 951
ttyed 155.132.2.55 952
ttyec 155.132.2.55 953
ttyeb 155.132.4.66 950
ttyea 155.132.4.66 951
ttye9 155.132.4.66 952
ttye8 155.132.4.66 953
ttye7 155.132.4.77 950
ttye6 155.132.4.77 951
ttye5 155.132.4.77 952
ttye4 155.132.4.77 953
ttye3 155.132.4.78 950
ttye2 155.132.4.78 951
ttye1 155.132.4.78 952
ttye0 155.132.4.78 953

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

970
V24/IP box
Maintenance

From CS, open a telnet session on the Nport Server (MOXA box)
to check its IP configuration
to check the firmware release

MOXA NPort Server Lite V3.00

-------------------------------------------------------------------
[serverConfig] Serialport Diagnostic Monitor Ping Restart Exit
Config server settings

Initialization of the V24_config process

(6)xa000006> dhs3_init -R V24_CONFIG

Open a telnet session from PC to call server

do not use the console port because in the event of a process problem it is
necessary to kill it from a telnet session

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

971
V24/IP box
Maintenance

Npadm program (1/8)

[root@xa000006 mtcl]#cd /usr/etc/moxatty

[root@xa000006 moxatty]#./npadm

The npadm program is only used to maintain the MOXA box.

Since the release 6.1, the V24 ports are configured with a management tool.

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

972
V24/IP box
Maintenance

Npadm program (2/8)

Access to main menu

System checking and initializing
Please wait

Add server

MOXA NPort Server/Async Server Administration Utility (Ver. 2.05)

MAIN MENU

Add server
Delete server
Configure server
Ports Monitor
Driver removal
Exit

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

973
V24/IP box
Maintenance

Npadm program (3/8)

Add server

Auto-Probe NPort Server/Async Server

Manual Add NPort Server/Async Server
<Enter>:Select <Esc>:Exit

Enter IP Addr.: 155.132.6.81

IP@ of the Moxa box

[ Message ]
Probe for NPort Server/Async Server on the Lan
This will take a moment ...

Server Password:

Enter (no password)

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

974
V24/IP box
Maintenance

Npadm program (4/8)

Configuration check
Set Server Property < Firmware version ( 2.00) >

Name 3NP10507
IP Address 155.132.6.81
IP NetMask 255.255.255.0
Gateway 155.132.6.100
Server Password
Confirm Password

<Ctrl+F>: OK <Esc>: Cancel

<Ctrl+D>: DHCP Setting <Up>/<Dn>/<Enter>: Move
Do you really want to save these changes (Y/N) ?

MOXA NPort Server/Async Server Administration Utility (Ver. 2.05)

Set <NP10507>( 155.132.6.81) Port Property

Port Name Baud Rate Data Bit Stop Bit Parity Flow Control Interface
1 Disable 9600 8 1 NONE None RS-232
2 Disable 9600 8 1 NONE None RS-232
3 Disable 115200 8 1 NONE H/W FlowCtrl RS-232
4 Disable 9600 8 1 NONE H/W FlowCtrl RS-232

<Esc>: Cancel <Ctrl+F>: OK <Ctrl+G>: Set Grant IP <Ctrl+H>:Help

Do you really want to save these changes (Y/N) ?

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

975
V24/IP box
Maintenance

Npadm program (5/8)

Configuration check

MOXA NPort Server/Async Server Administration Utility (Ver. 2.05)

[ Message ]

Saving NP10507 Data.

This may take a moment, please wait...
Saving NPort Server/Async Server Configuration OK!
Restarting NPort Server/Async Server, please wait...

MOXA NPort Server/Async Server Administration Utility (Ver. 2.05)

Complete !

Name 3NP10507
IP Address 155.132.6.81
IP NetMask 255.255.255.0
Gateway 155.132.6.100

The NPort Server/Async Server configuration is now completed!

Press any key to continue.

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

976
V24/IP box
Maintenance

Npadm program (6/8)

Server configuration

MAIN MENU

Add server
Delete server
Configure server
Ports Monitor
Driver removal
Exit

MOXA NPort Server/Async Server Administration Utility (Ver. 2.05)

Select NPort Server/Async Server to Configure

Name IP Address Serial No. Device Type

BREST 155.132.6.80 10473 DE-304
NP10507 155.132.6.81 10507 DE-304

<Up/Down/Enter>: Select <Esc>: Exit

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

977
V24/IP box
Maintenance

Npadm program (7/8)

Firmware upgrade

MOXA NPort Server/Async Server Administration Utility (Ver. 2.05)

Configure Server
Server property
Port property
Upgrade firmware
Save & Restart
Exit

MOXA NPort Server/Async Server Administration Utility (Ver. 2.05)

Enter Firmware FileName:/usr/etc/moxatty/NPL.ROM

<Esc>: Cancel <Ctrl+F>: OK

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

978
V24/IP box
Maintenance

Npadm program (8/8)

Firmware upgrade

MOXA NPort Server/Async Server Administration Utility (Ver. 2.05)

[ Message ]
Upgrading NPort Server/Async Server Firmware...
Upgrading NPort Server/Async Server Firmware completed!
Please wait for server restart...
OK !
Press any key to continue...

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

Alcatel-Lucent OmniPCX Enterprise – V24/IP box

Ref. ENTP0444M01TEUS Issue 04

980
Alcatel-Lucent OmniPCX Enterprise
V24/IP box

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to set up a MOXA V24/IP box

MANAGEMENT

1. Connect and manage the MOXA box

2. Manage the IP configuration

3. Manage the MOXA in the Call Server

4. Manage:

4.1. the V24 Port /dev/rv24/b1/tty1 for hotel menu

4.2. the V24 Port /dev/rv24/b1/tty2 for login

Issue 02 Ref. ENTP0444H01TEUS.doc HO. 1

HO. 2 Ref. ENTP0444H01TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

983
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

984
Alcatel-Lucent OmniPCX Enterprise

Database back up and restore

OBJECTIVE

To describe the backup of the database with swinst

Alcatel-Lucent OmniPCX Enterprise – Database back up and restore

Ref. ENTP0411P04TEUS Issue 02

985
Database backup and restore
Overview

Objectives of the database save and restore?

To protect the customer’s database against

The system crash

Mistakes made in the database itself

To recover the customer’s database after

An empty database creation

A software downloading

Alcatel-Lucent OmniPCX Enterprise – Database back up and restore

Ref. ENTP0411P04TEUS Issue 02

986
Database backup and restore
Overview

After any objects modification or creation (1)

Use of swinst account to backup

On the system there is also an automatic backup everyday at 5:45 AM by

default

All of these backup files are stored on the CPU’s hard disk

To copy the backup files on your PC, you should make a FTP connection(2)

(1) An object is an element of the database (e.g. users, boards, etc…)

(2) for the FTP connection you could use the Expert Tool or one FTP client

Alcatel-Lucent OmniPCX Enterprise – Database back up and restore

Ref. ENTP0411P04TEUS Issue 02

Alcatel-Lucent OmniPCX Enterprise – Database back up and restore

Ref. ENTP0411P04TEUS Issue 02

988
Alcatel-Lucent OmniPCX Enterprise
Database save & restore

PROCEDURE

OBJECTIVE

- To learn how to save and restore the database via swinst

PROCEDURE
Save the database in the /usr4/BACKUP/IMMED using the swinst menu and download the
database in a specific Directory (e.g.: BACKUP) of your PC by FTP.

Issue 04 Ref. ENTP0411C02TEUS.doc P. 1

PROCEDURE

1. Maintenance

1.1. Save the database

1.1.1. Save the database on the CPU

On the call server

Login mtcl
Command swinst
Select 2 Expert menu
4 Backup & restore operations
1 Immediate backup operations
1 Immediate backup on cpu disk
1 Backup mao, voice guides and accounting data
Entry Your choice => 1
Action Your choice => press ENTER
Press ENTER
Press Q as many times as needed to exit from swinst menu

1.1.2. Transfer the database from the OmniPCX Enterprise to your pc

On the PC
Action Start / Run… on the field Open enter “cmd”
Create a specific folder to save your database (eg: backup)
command C:/> cd backup
Remark:
All files will be saved on this folder
command C:/backup>ftp 155.132.1.1
Connected to 155.132.1.1.
Result
220 xa0001001 FTP server (Version wu-2.6.1(1) Wed Feb 28 15:50:32
User (155.132.1.1: (none)): mtcl
Entry
331 Password required for mtcl.
Password: mtcl

Result 230 User mtcl logged in.

P. 2 Ref. ENTP0411C02TEUS.doc Issue 04

Remark:
Use the ftp connection to save OPS files on your PC (155.132.1.1 = cpu IP@)
Use the mtcl login and pass for the ftp connection
command ftp> bin
Result 200 Type set to I.
Remark:
The command “bin” is used to transfer the data in binaries and not in ASCII
command ftp> cd /usr4/BACKUP/IMMED
Result 250 CWD command successful.
Remark:
Go to this specific folder to get the database file
command ftp> get mao-acc
ftp>quit

2. Clean immediate backups on CPU disk

On the call server

Login mtcl
Command swinst
Select 2 Expert menu
4 Backup & restore operations
3 Restore operations
3 Clean IMMEDIATE backups on the cpu disk
1 clean mao data
Action Press Q as many times as needed to exit from swinst menu

Issue 04 Ref. ENTP0411C02TEUS.doc P. 3

3. Restore the database from your pc to the OmniPCX Enterprise

3.1. Send the backup file by ftp in /usr4/BACKUP/IMMED Directory

On the PC
Action Start / Run… on the field Open enter “cmd”
Remarks:
Select the folder where is your mao-acc file.
command C:/> cd backup
command C:/backup>ftp 155.132.1.1
Connected to 155.132.1.1.
Result
220 xa0001001 FTP server (Version wu-2.6.1(1) Wed Feb 28 15:50:32
User (155.132.1.1: (none)) : mtcl
Entry
331 Password required for mtcl.
Password: mtcl

Result 230 User mtcl logged in.

Remark :
Use the ftp connection to restore mao-acc file on your PC (155.132.1.1 =
cpu IP@)
Use the mtcl login and pass for the ftp connection
command ftp> bin
Result 200 Type set to I.
Remark :
The command “bin” is used to transfer the data in binaries and not in ASCII
command ftp> cd /usr4/BACKUP/IMMED
Result 250 CWD command successful.
Remark :
Go to this specific folder to send the database file
command ftp> put mao-acc
ftp>quit

P. 4 Ref. ENTP0411C02TEUS.doc Issue 04

3.2. Stop the phone application

On the call server

Login mtcl
Command swinst
Select 1 Easy menu
7 Stop the telephone
Entry Please confirm to stop the telephone: y
Linux Mandrake for eMediate release 7.2 (Odyssey) for i486
Result
Kernel 2.4.1-ll-dhs3 on an i486 / ttyS0
xa001001 login:

3.3. Restore from CPU-CS disk the database

On the call server

Login mtcl
Command swinst
Select 2 Expert menu
4 Backup & restore operations
3 Restore operations
1 Restore from cpu disk
1 Restore from IMMEDIATE backup
1 Restore mao data
Entry Confirm your action: y
Do you wish to secure the restoration: y
Remarks:
If you choose this option, you save the actual database before restoring the
new one. Like this, if there is a problem during the restoration, you can
come back.
Entry Do you wish to clean the archive: y
Remarks:
This option is used to suppress the archive which contains the previous
database, the archive created to secure the restoration
Action Press ENTER
Press Q as many times as needed to exit from swinst menu

Issue 04 Ref. ENTP0411C02TEUS.doc P. 5

3.4. Restart the phone application

On the call server

P. 6 Ref. ENTP0411C02TEUS.doc Issue 04

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to save and restore the database via swinst

MANAGEMENT

1. Save the database via swinst

2. Modify the database by deleting some users

3. Restore the previous “saved database” via swinst

4. Check that the deleted users are back in the database

Issue 01 Ref. ENTP0411H02TEUS.doc HO. 1

HO. 2 Ref. ENTP0411H02TEUS.doc Issue 01

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

997
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

998
Alcatel-Lucent OmniPCX Enterprise

Remote Maintenance Access

OBJECTIVE

To describe the RMA solutions

Alcatel-Lucent OmniPCX Enterprise – Remote Maintenance Access

Ref. ENTP0431P01TEUS Issue 02

999
Remote Maintenance Access
Overview

The RMA system is an interface used to carry out maintenance and

administration operations on the Alcatel-Lucent OmniPCX Enterprise

This maintenance is carried out either locally or remotely via the public
network or a private network

The RMA carries out three main functions

Allows to access and act on the two Call server in a duplicated mode

It reinforces the access security

It can feed-back information from the system to the remote maintenance

center -> alarms and system messages

Alcatel-Lucent OmniPCX Enterprise – Remote Maintenance Access

Ref. ENTP0431P01TEUS Issue 02

1000
Remote Maintenance Access
Overview

According to the type of hardware, different RMA solutions are available:

Using a Crystal server

SRMA daughter board (on MMSFD board in VH)

Internal RMA (RMA connecting box with RMA board in the Crystal Media Gateway)

External RMA (RMA connecting box with RMA board inside)

Using a CS board or appliance server

e-RMA

RMA hardware solution

Alcatel-Lucent OmniPCX Enterprise – Remote Maintenance Access

Ref. ENTP0431P01TEUS Issue 02

1001
Remote Maintenance Access
Overview

Whatever the RMA type (RMAB in case of crystal, RMA board or e-RMA with CS
or Appliance), the features are the following:

Local connection

Remote access:
+
S Remote access with automatic callback to a fixed number
e
c
u Remote access with automatic callback to the caller number
r
i
t Simple remote access
y -
Alarms sending

Alcatel-Lucent OmniPCX Enterprise – Remote Maintenance Access

Ref. ENTP0431P01TEUS Issue 02

1002
Remote Maintenance Access
Overview

Local connection with secured access

Advantages:
security enforced: Two logins and passwords are required, the first one to access to
the RMA functions (menu) and after to access to the OmniPCX Enterprise server

Possibility to access to both servers (in case of duplication) from the same console
without any connection modification

Login: rma Password: ****

Or
Login: mtcl Password: ****
CS 1
Login:mtcl
Login:rma
Password:xxxx
Password:xxx
mtcl>
RMA>

RMA box CS 2

Alcatel-Lucent OmniPCX Enterprise – Remote Maintenance Access

Ref. ENTP0431P01TEUS Issue 02

1003
Remote Maintenance Access
Overview

Direct connection by modem (simple call):

From the remote console, you dial the RMA modem DDI number
You give a login and password for this connection
Once connected to the RMA, you can access to the OmniPCX Enterprise giving
the call server login and password

Login: mtcl Password: ****

Public
Network RMA box
CS A

Calls: 0155124788

Modem DDI number: 0155124788

In the case of access by modem the login is managed independently from the local login, the account and the password can be
different.
The access rights to various RAM functions can vary depending on login use. At RMA initialization, this access right and login
management can only be carried out locally.

Alcatel-Lucent OmniPCX Enterprise – Remote Maintenance Access

Ref. ENTP0431P01TEUS Issue 02

1004
Remote Maintenance Access
Overview

Call back on the caller number to enter after login:

From the remote console, you dial the RMA modem DDI number
You give a login and password for this connection
Once connected to the RMA, you give your modem number
The RMA calls you back: you can then access to the OmniPCX Enterprise
giving the call server login and password

RMA Login: titi

Password: ****

Telephone number: 00298143500

Please wait, I ’ll call you back.

Public RMA
Network
box
Modem number:0298143500

Alcatel-Lucent OmniPCX Enterprise – Remote Maintenance Access

Ref. ENTP0431P01TEUS Issue 02

1005
Remote Maintenance Access
Overview

Call back on a predetermined number:

From the remote console, you dial the RMA modem DDI number
You give a login and password for this connection
Once, connected to the RMA, it cuts the communication and calls you back
to a predetermined number (your modem) managed in the RMA
You can then access to the OmniPCX Enterprise giving the call server login
and password

RMA Login: toto

Password: ****

Please wait, I ’ll call you back.

Public RMA
Network
box
Modem number: 0298143500

Alcatel-Lucent OmniPCX Enterprise – Remote Maintenance Access

Ref. ENTP0431P01TEUS Issue 02

1006
Remote Maintenance Access
Overview

The OmniPCX Enterprise call server generates system messages that are used by
the technicians to supervise the state of the system (board reset, call
rejected,…), these messages

Can be stored on the CS hard disk (to generate reports…)

Can be displayed on the CS Ethernet or V24 access (terminal, printer…)

Can ring an alarm set (possibility to ring an UA set and to display the alarm
message with acknowledgement option...)

Can be sent to an administration tool to generate reports (OmniVista 4760)

Can be sent to the RMA system (to set up a remote call…)

Alcatel-Lucent OmniPCX Enterprise – Remote Maintenance Access

Ref. ENTP0431P01TEUS Issue 02

1007
Remote Maintenance Access
Overview

RMA alarm

Alarms table
CS Alarm Alarm 1

Alarm 2

Alarm 3
OXE Alarm 4

Alarm 5

System messages

OPERATOR

?
Call and alarm transmission
to a remote site
TD RD CD 19 14 96 ON
3 External alarm contacts

Alcatel-Lucent OmniPCX Enterprise – Remote Maintenance Access

Ref. ENTP0431P01TEUS Issue 02

1008
Alcatel-Lucent OmniPCX Enterprise

RMA – Crystal hardware

OBJECTIVE

To describe the RMA for the Crystal hardware

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1009
RMA – Crystal hardware
Overview

The RMA application with Crystal hardware is used to:

Make a remote connection on your system for maintenance (reset of boards,
etc…)
Receive alarms from the system on the remote maintenance office

Hardware used for RMA connection

SRMA daughter board (on MMSFD board in VH)
Internal RMA (RMA connecting box with RMA board in the Crystal Media
Gateway)
External RMA (RMA connecting box with RMA board inside)

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1010
RMA – Crystal hardware
Overview

Principle: RMA board inside the crystal media gateway

Remote
Local
console
console

CPU A

RMA
Modem
Modem

CPU B

CARRIER

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1011
RMA – Crystal hardware
Overview

Principle: RMA board inside the connecting box

Remote
Local
console
console

RMA
CPU A

Modem Modem

CPU B

CARRIER

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1012
RMA – Crystal hardware
Overview

Connecting box

Ports
Portsnot
notavailable
availablewhen
when
RMAB
RMAB boardisisconnected
board connected

Port
Portdedicated
dedicatedto
tolocal
local
system
systemterminal
terminal

Port
Portdedicated
dedicatedto
toremote
remote
maintenance modem
maintenance modem

Port
Portenabling
enablingeither
eitheraaTA
TAor
oran
an
external application to be connected
external application to be connected

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1013
RMA – Crystal hardware
Overview

RMAB board
ACT PWI
INT

CPU
EXT
Coupler
Couplerreset
resetbutton
button
Debug

Reset

RMA
RMAboard
boardcancanbe
beconnected
connected either
either
ininaaslot
slotofofthe
theOmniPCX
OmniPCXEnterprise,
Enterprise,
ororininthe
the BRMA
BRMA box
box to
tofree
freeaaslot
slotinin
the OmniPCX Enterprise’s
the OmniPCX Enterprise’s ACT.ACT.

RMAB

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1014
RMA – Crystal hardware
Overview

Remote login secured or not

RMA accesses Choice of the connection port:
- system (console port)
- Exa
To an UA port - talk session
- consultation
CTI V24
Public
network
TA (remote connection) ExC
RMA CPU
SyA A
ExB

SyB CPU
B
Modem (remote connection) ExA

OmniPCX Enterprise

Local login
Choice of the connection port:
- system (console port)
- modem for outgoing call
PC (local connection)

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1015
RMA – Crystal hardware
Overview

Local access to the RMA (on Exa):

---------------------------------------------------------
Date: 01/04/01 18:21:12 Last restart reason saved
Power-on
---------------------------------------------------------
RMA Login: rma
Password: ***

RMA: Release 03.03.01 PCMS Code: 3BA23114AAAB03

Site: Alcatel OmniPCX Enterprise

Address: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Phone: xx xx xx xx

The access to the RMA board can be done through local console using the default
login. For security reason, please change default login.
For this, enter "mngt log" command.

Monday April 01 18:21:26 2001

RMA>

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1016
RMA – Crystal hardware
Overview

Remote access to the RMA (through ExB or ExC)

Public
network

at
OK

atdt00298762208
CONNECT 9600

RMA Login: amr

Password: ***

RMA: Release 03.03.01 PCMS Code: 3BA23114AAAB03

Site: Alcatel OmniPCX Enterprise

Address: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Phone: xx xx xx xx

Monday April 01 18:25:41 2001

RMA>

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1017
RMA – Crystal hardware
Overview

Secured remote accesses with automatic callback:

On a number entered after the login
atd00298762208
CONNECT 9600 Call number of the modem
connected to the ExB port
RMA Login: aaa
Password: ***
Phone number: 00298762207
Please wait, I call you back. Local modem
number to enter
+++ NO CARRIER
1 minute
later RING
RING
CONNECT 9600

RMA Login: aaa

Password: ***

RMA: Release 03.03.01 PCMS Code: 3BA23114AAAB03

Site: Alcatel OmniPCX Enterprise
Address: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Phone: xx xx xx xx
Tuesday April 02 11:13:19 2001
RMA>

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1018
RMA – Crystal hardware
Overview

Secured remote accesses with automatic callback:

On a predefined number

atd00298762208
CONNECT 9600
Call number of the modem
RMA Login: aaa connected to the ExB port
Password: ***

Please wait, I call you back.

Automatic
+++ NO CARRIER callback
1 minute
RING
later RING
CONNECT 9600

RMA Login: aaa

Password: ***

RMA: Release 03.03.01 PCMS Code: 3BA23114AAAB03

Site: Alcatel OmniPCX Enterprise
Address: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Phone: xx xx xx xx
Tuesday November 30 11:13:19 1999
RMA>

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1019
RMA – Crystal hardware
Overview

Access to the Alcatel-Lucent OmniPCX Enterprise Call Server through the RMA:

RMA>cnx

/Connections
[1] SyA
[1] SyB
[2] ExA
[3] ExB
[3] ExC

Your choice: 1
Type 2 CTRL-A to close connection
Connected

Console Login: mtcl

Password: xxxx
...
xa00000
...
(0)xa00000>
...
(0)xa00000>

ctrl A (twice)
Connection closed

Alcatel-Lucent OmniPCX Enterprise – RMA – Crystal hardware

Ref. ENTP0431P06TEUS Issue 02

1020
Alcatel-Lucent OmniPCX Enterprise

RMA – Common hardware

OBJECTIVE

To describe the RMA for Common hardware

Alcatel-Lucent OmniPCX Enterprise – RMA – Common hardware

Ref. ENTP0431P07TEUS Issue 02

1021
RMA – Common hardware
Overview

The RMA application with Common hardware is used to:

Make a remote connection to you system for maintenance
(reset of boards, etc…)
Receive alarms from the system to the remote maintenance office

Hardware used for RMA connection

RMA board
MODB Board

Alcatel-Lucent OmniPCX Enterprise – RMA – Common hardware

Ref. ENTP0431P07TEUS Issue 02

1022
RMA – Common hardware
Overview

RMA hardware solution (with CS and Appliance)

V24

Not used

V24
CS 2

OPERATOR
CS CS 1
or V24
Appliance

Modem

Local terminal Remote terminal

Alcatel-Lucent OmniPCX Enterprise – RMA – Common hardware

Ref. ENTP0431P07TEUS Issue 02

1023
RMA – Crystal hardware
Overview

Remote login secured or not

RMA accesses Choice of the connection port:
- system (console port)
- Exa
To an UA port - talk session
- consultation
CTI V24
Public
network
TA (remote connection) ExC
RMA CPU
SyA A
ExB

SyB CPU
B
Modem (remote connection) ExA

Alcatel-Lucent OmniPCX
Enterprise

Local login
Choice of the connection port:
- system (console port)
- modem for outgoing call
PC (local connection)

Alcatel-Lucent OmniPCX Enterprise – RMA – Common hardware

Ref. ENTP0431P07TEUS Issue 02

1024
RMA – Crystal hardware
Overview

Local access to the RMA (on Exa):

RMA: Release 03.03.01 PCMS Code: 3BA23114AAAB03

Site: Alcatel OmniPCX Enterprise

Address: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Phone: xx xx xx xx

The access to the RMA board can be done through local console using the default
login. For security reason, please change default login.
For this, enter "mngt log" command.

Monday April 01 18:21:26 2001

RMA>

Alcatel-Lucent OmniPCX Enterprise – RMA – Common hardware

Ref. ENTP0431P07TEUS Issue 02

1025
RMA – Crystal hardware
Overview

Remote access to the RMA (through ExB or ExC)

Public
network

at
OK

atdt00298762208
CONNECT 9600

RMA Login: amr

Password: ***

RMA: Release 03.03.01 PCMS Code: 3BA23114AAAB03

Site: Alcatel OmniPCX Enterprise

Address: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Phone: xx xx xx xx

Monday April 01 18:25:41 2001

RMA>

Alcatel-Lucent OmniPCX Enterprise – RMA – Common hardware

Ref. ENTP0431P07TEUS Issue 02

1026
RMA – Crystal hardware
Overview

Secured remote accesses with automatic callback:

on a number entered after the login
atd00298762208
CONNECT 9600 Call number of the modem
connected to the ExB port
RMA Login: aaa
Password: ***
Phone number: 00298762207
Please wait, I call you back. Local modem
number to enter
+++ NO CARRIER
1 minute
later RING
RING
CONNECT 9600

RMA Login: aaa

Password: ***

RMA: Release 03.03.01 PCMS Code: 3BA23114AAAB03

Site: Alcatel OmniPCX Enterprise
Address: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Phone: xx xx xx xx
Tuesday April 02 11:13:19 2001
RMA>

Alcatel-Lucent OmniPCX Enterprise – RMA – Common hardware

Ref. ENTP0431P07TEUS Issue 02

1027
RMA – Crystal hardware
Overview

Secured remote accesses with automatic callback:

on a predefined number
atd00298762208
CONNECT 9600 Call number of the modem
connected to the ExB port
RMA Login: aaa
Password: ***

Please wait, I call you back. Automatic

callback
+++ NO CARRIER
1 minute RING
later RING
CONNECT 9600

RMA Login: aaa

Password: ***

RMA: Release 03.03.01 PCMS Code: 3BA23114AAAB03

Site: Alcatel OmniPCX Enterprise
Address: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Phone: xx xx xx xx
Tuesday November 30 11:13:19 1999
RMA>

Alcatel-Lucent OmniPCX Enterprise – RMA – Common hardware

Ref. ENTP0431P07TEUS Issue 02

1028
RMA – Crystal hardware
Overview

Access to the Alcatel-Lucent OmniPCX Enterprise CPU through the RMA:

RMA>cnx

/Connections
[1] SyA
[1] SyB
[2] ExA
[3] ExB
[3] ExC

Your choice: 1
Type 2 CTRL-A to close connection
Connected

Console Login: mtcl

Password: xxxx
...
xa00000
...
(0)xa00000>
...
(0)xa00000>

ctrl A (twice)
Connection closed

Alcatel-Lucent OmniPCX Enterprise – RMA – Common hardware

Ref. ENTP0431P07TEUS Issue 02

Alcatel-Lucent OmniPCX Enterprise – RMA – Common hardware

Ref. ENTP0431P07TEUS Issue 02

1030
Alcatel-Lucent OmniPCX Enterprise

RMA / e-RMA

OBJECTIVE

To describe the e-RMA solution

Alcatel-Lucent OmniPCX Enterprise – RMA / e-RMA

Ref. ENTP0431P08TEUS Issue 02

1031
RMA - e-RMA
Overview

Alternative software solution to the RMA box (No hardware required)

Full software solution

Embedded on the call server and allows remote assistance via modem (runs
only with modem connections)

Uses the PPP protocol and only works when Call handling is running.

In case of duplicated CPU

Alcatel-Lucent OmniPCX Enterprise – RMA / e-RMA

Ref. ENTP0431P08TEUS Issue 02

1032
RMA - e-RMA
Overview

e-RMA environment: uses the GD integrated modem

Com server
e-RMA

IP
Network
Media Gateway
Integrated modem
Media Gateway
Integrated modem

Public or
private
network Modem

Remote assistance center

Alcatel-Lucent OmniPCX Enterprise – RMA / e-RMA

Ref. ENTP0431P08TEUS Issue 02

1033
RMA - e-RMA
Overview

Incoming call from remote assistance center

The remote assistance center dials a DDI number that corresponds to the e-
RMA application call
The call server routes the incoming call to a free IP MG modem
The call can be secured. In this case the call server calls back the remote
assistance center using a predefined number

Outgoing call to the remote assistance center

According to some events the e-RMA application is able to call directly the
remote assistance center using a predefined number

Alcatel-Lucent OmniPCX Enterprise – RMA / e-RMA

Ref. ENTP0431P08TEUS Issue 02

1034
RMA - e-RMA
Overview

e-RMA limits and remarks

The e-RMA application cannot work if telephone application is not running

If telephone application is stopped, it cannot be started remotely

The number of accesses depends on the number of IP MG modems available

If one IP MG has a back-up IP link through the switched telephone network,

the back-up link has the priority over the e-RMA connection

Provides less autonomy than the hardware RMA solution

Alcatel-Lucent OmniPCX Enterprise – RMA / e-RMA

Ref. ENTP0431P08TEUS Issue 02

Alcatel-Lucent OmniPCX Enterprise – RMA / e-RMA

Ref. ENTP0431P08TEUS Issue 02

1036
Alcatel-Lucent OmniPCX Enterprise

System Messages

OBJECTIVE

To describe the system message

Alcatel-Lucent OmniPCX Enterprise – System Messages

Ref. ENTP0421P01TEUS Issue 02

1037
System Messages
Overview

System messages are automatically generated by the system:

When an incident occurs
When an equipment is in service
A management is realized of some parameters

The system messages can be:

Displayed in real time on the console port
Stored in the CPU hard disk
Sent to “Alarm” application on OmniVista 4760
Sent to the RMA

According to the severity level associated to each system message, it is possible

to manage which messages will be displayed, stored or sent to the RMA:
Path: Applications / Incident manager

To define some exceptions and the incidents sent to the RMA:

Path: Applications / Incident manager / Incident filter

Alcatel-Lucent OmniPCX Enterprise – System Messages

Ref. ENTP0421P01TEUS Issue 02

1038
System Messages
Overview

Incident severity levels:

0: undetermined: no assessment of system
Degradation

1: critical: compulsory immediate correction

High degradation

2: major: urgent correction

Average degradation

3: minor: correction recommended

Slight degradation

4: warning: analysis recommended

Possible degradation

5: clear: analysis recommended

Put services back into operation

6: unknown

Example of management:
path: Applications / Incident manager
RMA: YES
Display severity: Major
Storage severity: Clear
Network severity: Clear

Alcatel-Lucent OmniPCX Enterprise – System Messages

Ref. ENTP0421P01TEUS Issue 02

1039
System Messages
Overview

Backup Files

counter 1 counter.txt
Incidents saved as files
counter 2
on hard disk
1
inc-3.txt
To read the messages stored
2
on the disk:
incvisu, with the option: 3
-1: before the last reset inc-2.txt
-2: before the last reset but one 4
-3: before the last reset but two
-r: oldest to newest 5
inc-1.txt
-t x: the x last messages
-s “abc”: messages that contain
6
the string “abc”
7
inc.txt
8

Structure of files counter.txt, inc.txt, inc-1.txt, inc-2.txt, inc-3.txt:

reset 1 reset 2 reset 3 reset 4 Now

1 2 3 4 5 6 7 8
time
Incident incvisu -3 incvisu -2 incvisu -1 incvisu
command

Each file contains a maximum of 2000 (first or last) incidents before or after CPU reset.
There are 2 buffers per file.

The first buffer X contains the 500 oldest messages since the last shutdown.

The second buffer X+1 contains the 1500 newest messages before the next shutdown.

The file counter.txt is explained below:

 counter indicating
number of incidents for
each level of severity
 counter indicating
number of incidents for
each incident

The files inc.txt, inc-1.txt, inc-2.txt, inc-3.txt, counter.txt are located in the /usr4/incid directory

Alcatel-Lucent OmniPCX Enterprise – System Messages

Ref. ENTP0421P01TEUS Issue 02

1040
System Messages
Overview

System message fields

dd / mm / yy hh: mn: ss M | c / pc / t / eqt | =s: mini = label


 information
text
incident number
degree of severity
port number
0
board slot
crystal number
M: incident from main CPU
S: incident from stand-by CPU
I: incident from local CPU whose role has not
yet been defined
time of incident (hh=hour, mn=minute, ss=second)
date of incident (dd=day, mm=month, yy=year)

Example:
07/07/98 16:25:08 000030M | 00/04/0/000 | = 4: 2113 = establishment attempt level 2 T2

Alcatel-Lucent OmniPCX Enterprise – System Messages

Ref. ENTP0421P01TEUS Issue 02

1041
System Messages
Overview

To stop the incident print-out in real time on the system terminal screen
incout -2

To start the incident print-out in real time on the system terminal screen
incout -3

To view the incident counters

inccpt

To reset incident and counters

increset

Example:
07/07/98 16:25:08 000030M | 00/04/0/000 | = 4: 2113 = establishment attempt level 2 T2

Alcatel-Lucent OmniPCX Enterprise – System Messages

Ref. ENTP0421P01TEUS Issue 02

1042
System Messages
Overview

RMA solution: e-RMA or RMA

Alcatel-Lucent OmniPCX Enterprise – System Messages

Ref. ENTP0421P01TEUS Issue 02

1043
System Messages
Overview

Incident filter management

The configuration of the action is done on the RMA board or under mgr for the e-RMA

Alcatel-Lucent OmniPCX Enterprise – System Messages

Ref. ENTP0421P01TEUS Issue 02

1044
Alcatel-Lucent OmniPCX Enterprise
RMA automatic calls

PROCEDURE

OBJECTIVE

- To learn how to configure the remote accesses via the RMA board, the OmniPCX Enterprise
and the RMA board to call automatically in case of alarms.

PROCEDURE
The RMA system (Remote Maintenance Access) is an interface used to perform maintenance
operations on a OmniPCX Enterprise. This maintenance is performed by a local or remote
operator via a modem.
The RMA manages the following functions:

- it allows you to access

the main and backup Call Servers,
PCX applications,

- it reinforces access security,

- it allows you to report PCX data to a remote maintenance center.

The operator uses a VT100 type or a connected emulation console:

- locally

- through an external modem,

- through a TA.

Issue 05 Ref. ENTP0431C06TEUS.doc P. 1

PROCEDURE
REMOTE ACCESSES MANAGEMENT

1. Edit the list of logins programmed in the RMA

1.1. Login to the RMA

Application On the terminal connected to the RMA:

RMA login: rma
Action
Password: rma

1.2. Edit the list of the RMA password

Application Enter the command “menu”, then <return>

Choice:
Path
¯3 – Management
¯6 - Logins
Login n°: _ _ _ _ _ _ , Type: _ _ _ _ _ _ _ _ _ _ _, Login: _ _ _ _ _ _
Parameters
Login n°: _ _ _ _ _ _ , Type: _ _ _ _ _ _ _ _ _ _ _, Login: _ _ _ _ _ _

2. Program a basic call back remote login

Application On the terminal connected to the RMA

Path Enter the command “menu”, then <return>
Choice:
Action
¯3 – Management
¯6 – Logins
Enter the number of the line to update: 3
Parameters
Access type:[3] Basic call back remote
New login: bcb
password: bcb
password (confirmation): bcb
Privileges list login secured, your choice: “return”
Enter the number of the line to update: “return”
Your choice: “return”

In this example: login=bcb, password=bcb

P. 2 Ref. ENTP0431C06TEUS.doc Issue 05

3. Program a basic call back remote login

Application On the terminal connected to the RMA

Path Enter the command “menu”, then <return>
Choice:
Action
¯3 – Management
¯6 – Logins
Enter the number of the line to update: 4
Parameters
Access type:[4] auto. call back remote
New login: srl
password: srl
password (confirmation): srl
Phone number: 002xx03y012
Privileges list login secured, your choice: <return>
Enter the number of the line to update: <return>
Your choice: <return>

login= srl, password=srl, phone number:002xx03y012

4. Login with specific privileges management

Application On the terminal connected to the RMA

Path Enter the command “menu”, then <return>

Choice:
Action ¯3 – Management
¯8 - Privileges
Enter the number of the line to update: 3
Privileges list login secured
Parameters [1] MNGT command (RMA configuration management): No
[2] Outgoing calls (via ExB, ExC, APA): No
[3] PABX connection (via Sya, SyB): Yes
[4] RMA board reset command: Yes
[5] PABX reset command: No
[6] Download and restore commands: No
[7] Login and privileges management: No
Your choice: <value for the right to add or remove>
Note: Select and modify the privileges one by one

In this example the rights are: OmniPCX Enterprise management and maintenance and
RMA board reset

Issue 05 Ref. ENTP0431C06TEUS.doc P. 3

5. Data saving

Application On the terminal connected to the RMA

Path Enter the command “menu”, then <return>
Choice:
Action
¯3 – Management
¯9 - Save
Do you really want to save set up?
Parameters
[Yes/No – default is no]: Yes

PROGRAMMING OF THE AUTOMATIC CALLS ON RMA

6. Consult the programming of the destination numbers used for the automatic calls

Application Enter the command “menu”, then <return>

Choice:
Path
¯3 – Management
¯ 7 – Automatic calls
¯ 1 – Destinations
¯ 5 – All
/Management/Automatic call/Destinations/Destination 1
Parameters [1] Phone 1: ExB -
[2] Phone 2: ExB -
[3] Timeout for user connection: 30 second(s)
Your choice:
/Management/Automatic call/Destinations/Destination 2
[1] Phone 1: ExB -
[2] Phone 2: ExB -
[3] Timeout for user connection: 30 second(s)
Your choice:
/Management/Automatic call/Destinations/Destination 3
[1] Phone 1: ExB -
[2] Phone 2: ExB -
[3] Timeout for user connection: 30 second(s)
Your choice:
/Management/Automatic call/Destinations/Destination 4
[1] Phone 1: ExB -
[2] Phone 2: ExB -
[3] Timeout for user connection: 30 second(s)
Your choice:

P. 4 Ref. ENTP0431C06TEUS.doc Issue 05

7. Consult the programming of the CPU alarm in the RMA

Application Enter the command “menu”, then <return>

Choice:
Path
¯3 – Management
¯ 3 – alarms
¯ 1 – CPU
Label: _ _ _ _ _ _
Parameters
Used: _ _ _ _ _ _
Active state: _ _ _ _ _ _
Alarm duration before action: _ _ _ _ _ _ second(s)
Number of alarms before action: _ _ _ _ _ _ alarm(s)
Time between two actions: _ _ _ _ _ _ minute(s)
Command activation: _ _ _ _ _ _
Call: _ _ _ _ _ _
First destination: _ _ _ _ _ _
Second destination: _ _ _ _ _ _

8. Consult the programming of the destinations for the automatic calls on system messages
reception

Application Enter the command “menu”, then <return>

Choice:
Path
¯3 – Management
¯ 4 – PABX incidents
¯ 1 – Incidents action0
Parameters First destination: _ _ _ _ _ _
Second destination: _ _ _ _ _ _
¯ 2 – Incidents action1
First destination: _ _ _ _ _ _
Second destination: _ _ _ _ _ _
¯ 3 – Incidents action2
First destination: _ _ _ _ _ _
Second destination: _ _ _ _ _ _
¯ 4 – Incidents action3
First destination: _ _ _ _ _ _
Second destination: _ _ _ _ _ _

Issue 05 Ref. ENTP0431C06TEUS.doc P. 5

9. Automatic calls on CPU alarm relay activation

9.1. Program the CPU alarm relay in the OmniPCX Enterprise

9.1.1. Connect to the CPU

Application On the terminal

RMA Command: c 1
Action
Console login: mtcl
Password: mtcl

9.1.2. Link the incident number to the CPU alarm relay

Application mgr
Applications/Incident manager/Incident filter/Create or modify
Path
Incident Number: enter the incident number (eg. 2042 = loss of a board)
Parameters Alarm Action: Alarm up

9.1.3. leave ‘mgr’ and disconnect from the OmniPCX Enterprise CPU

Application On the terminal

F2 key several times to exit mgr
Action
‘exit’ command to leave the ‘mtcl’ session.
‘Ctrl+A’ twice to disconnect from the CPU

P. 6 Ref. ENTP0431C06TEUS.doc Issue 05

9.2. Program the number to call in case of CPU alarm activation

Application On the terminal, in the RMA menu:

Choice:
Path ¯3 – Management
¯ 7 – automatic calls
¯ 1 – destinations
¯ 1 – destination 1
¯ 1 – Phone 1: ExB -
/Management/Automatic call/Destinations/Destination 1
Parameters [1] ExB (default value)
Your choice: 1
/Management/Automatic call/Destinations/Destination 1/Phone 1
Phone 1: 0298143636
/Management/Automatic call/Destinations/Destination 1
[1] Phone 1: ExB - 0298143636
[2] Phone 2: ExB -
[3] Timeout for user connection: 30 second(s)
Your choice: 3
/Management/Automatic call/Destinations/Destination 1/Timeout for user
connection
Default value: 30
Timeout for user connection: 60
/Management/Automatic call/Destinations/Destination 1
[1] Phone 1: ExB - 0298143636
[2] Phone 2: ExB -
[3] Timeout for user connection: 60 second(s)
Your choice: « return »

If the modem is connected to a direct line, no prefix needed. But if the modem is connected to
an OmniPCX Enterprise equipment, a trunk group seizure prefix is required before the called
number

9.3. Program the automatic call in case of CPU alarm activation

Application On the terminal, in the RMA menu:

¯3 – Management
Path
¯ 3 – Alarms
¯ 1 – CPU
¯ C – All
Example of programming:
Parameters
Label: CPUrelay
Used: Yes
Active state: Closed
Alarm duration before action: 0 second(s)
Number of alarms before action: 1 alarm(s)
Time between two actions: 0 minute(s)
Command activation: None
Save: Yes
Call: At the beginning of the alarm
First destination: Destination 1
Second destination: None

Issue 05 Ref. ENTP0431C06TEUS.doc P. 7

9.4. Enable the automatic calls

Application On the terminal, in the RMA menu:

Choice:
Path
¯3 – Management
¯ 7 – Automatic calls
¯ 4 – Automatic calls validation
---> Automatic calls are validate

Note: (*) After an automatic call, do not forget to disable the CPU-Relay while you are
connected (use “alarmrel” command; choice 0: disable the relay)

P. 8 Ref. ENTP0431C06TEUS.doc Issue 05

10. Automatic calls in case of system message reception

10.1. Program the system message in the OmniPCX Enterprise

10.1.1. Connect to the CPU

Application On the terminal

RMA Command: c 1
Action
Console login: mtcl
Password: mtcl

10.1.2. Link the incident number to the CPU alarm relay

Application Mgr
Path Applications/Incident manager/Incident filter/Create or modify
Incident Number: enter the incident number (eg. 2042 = loss of a board)
Parameters
Rma Action: Action 0 (example ; other possible values: action 1, 2 and 3)

10.1.3. Leave ‘mgr’ and OmniPCX Enterprise CPU disconnection

Application On the terminal

F2 key several times to leave mgr
Action
‘exit’ command to leave the ‘mtcl’ session
twice ‘ctrl+A’ for CPU disconnection

10.2. Program the number to call in case of system message reception

The programming is the same as the one performed in case of CPU relay activation:
see step 9.2

10.3. Program the automatic call in case of system message reception

Application On the terminal, in the RMA menu:

Choice:
Path
¯3 – Management
¯ 4 – PABX incidents
¯ 1 – Incidents action0

Parameters Example of settings:

First destination: Destination 1 (the destination programmed at step 9.2)
Second destination: None

Note: the “incident action0” corresponds to the action performed when a

system message linked to the “RMA action 0” (see step 10.1.2) is
received in the RMA. It’s also possible to choose the action 1, 2 or 3.

11. Enable the automatic calls: same programming as step 9.4

Issue 05 Ref. ENTP0431C06TEUS.doc P. 9

P. 10 Ref. ENTP0431C06TEUS.doc Issue 05

PROCEDURE

OBJECTIVE

- To learn how to setup the e-RMA

OVERVIEW
Note: All numbers are given for example (e.g)

The e-RMA is used to make a remote connection on the system for the maintenance,
management,… It’s possible also to use the e-RMA for the system alarms thanks to the automatic
calls., that means the system calls a specific number(e.g. Remote maintenance center)
Note: The Call handling must be running if you want to use the e-RMA application

Issue 04 Ref. ENTP0431C08TEUS.doc P. 1

PROCEDURE

1. Validation of the e-RMA in the e-MGD

Application On Call Server

Action mgr
Path Shelf/boards
Action Select a GD
Action Select Yes for the e-RMA feature
Node Number (reserved): 1
Result Shelf Address: 3
Board Address: 0
Interface Type + GD
Virtual board + NO
Usage State + Idle
Operational State + Disabled
Main/Standby State + Main (Master)
Number Of Sets Being Connect : 0
Country Protocol Type + Default
Incidents Teleservice + YES
INTIP Daughter Board + MCV24
Nb of Compressors for Gateway: 12
Nb of Compressors for IP Devices: 12
Use of volume in system + YES
Local volume (dB) : 0
AFU daughter board + NO
AFU Directory Number: --------
eMG rescue + YES
e-RMA feature + YES

2. Manage the e-RMA application

Application On Call Server

Action mgr
Path /Applications/e-RMA/e-RMA application
Action Enter a free directory number (DDI number)
Node Number (reserved): 1
Result Instance (reserved): 1
Instance (reserved): 1
Instance (reserved): 1
Directory No : 31600
Login attempts: 3
Unreachable delay: 15
Delay between two incident calls: 15

P. 2 Ref. ENTP0431C08TEUS.doc Issue 04

3. Management of e-RMA logins

Application On Call Server

Action mgr
Path /Applications/e-RMA/e-RMA application
Action Enter e-RMA login + Password + Security method
Node Number (reserved): 1
Result Instance (reserved): 1
Instance (reserved): 1
Login: erma
Password: ****
Confirm: ****
Security Method + Call back
Call back type + Calling number
Call back number: 0022113410

Remark Login: name under which the remote assistance center has to be connected
with the correct password
Security method: the e-RMA application is able to call back the remote
assistance center on the « call back number »
Call back type: the call back can be carried out on a fixed number or on a
calling number which corresponds to the ISDN identification of the remote
assistance center
Warning: The prefix used to establish the e-RMA call must be a professional
trunk group seize Do not use the ARS prefix

4. Management of e-RMA Actions

Application On Call Server

Action mgr
Path /Applications/e-RMA/e-RMA actions
Action Enter Action type + Alarm center number
Node Number (reserved): 1
Result Instance (reserved): 1
Instance (reserved): 1
Rma Action: 0
Action Type + Call alarm center
Alarm center number: 00221031410

Remark RMA Action: the action number is linked to incident number (see slide 7)
Action type: none, or call the remote assistance center
Alarm center number: call number of the remote assistance center

Issue 04 Ref. ENTP0431C08TEUS.doc P. 3

5. Incident management

Application On Call Server

Action mgr
Path /Applications/Incident manager

Action Select e-RMA

Node Number (reserved): 1
Result Instance (reserved): 1
Instance (reserved): 1
V24 No + /dev/rv24/b1/tty3
RMA + eRMA
RMA Network + NO
Display Severity + Minor
Storage Severity + Clear
Network Severity + Indeterminate
Network Incident Display Severity + Indeterminate
Network Incident Storage Severity + Clear
Topological Incident Display + YES
Topological Incident Storage + YES
Topological Network + YES
SNMP
Severity + None
Network Severity + None
Topology + NO
RMA + NO
Network + NO

6. Incident filter management

Application On Call Server

Action mgr
Path /Applications/Incident manager/Incident filter

Action Enter al
Node Number (reserved): 1
Result Instance (reserved): 1
Instance (reserved): 1
Filter id
Incident Number: 2042
Network Number: -1
Node Number: -1
ACT shelf Number: -1
Coupler Number: -1
Behind Us: -1
Set Address: -1
Rma Action + Action 0
Alarm Action + None
Table Id: 0
Screen Display + YES
Disk Storage + YES
Network Incident + NO
SNMP Incident + NO
Incident Number: 2042
Network Number: -1
Node Number: -1
ACT shelf Number: -1
Coupler Number: -1
Behind Us: -1
Set Address: -1

P. 4 Ref. ENTP0431C08TEUS.doc Issue 04

HANDS-ON EXERCISES

OBJECTIVE

- To learn how to manage e-RMA

MANAGEMENT

1. Make a connection to the CPU trough the e-RMA board

2. Manage an automatic callback for the incident 2042 (ask the trainer for the phone number)

3. Test the configuration

Issue 02 Ref. ENTP0431H08TEUS.doc HO. 1

HO. 2 Ref. ENTP0431H08TEUS.doc Issue 02

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

1061
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

1062
Alcatel-Lucent OmniPCX Enterprise

Reflex & e-Reflex sets

OBJECTIVE

To describe Reflexes & e-Reflexes sets

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1063
Reflexes & e-Reflexes sets
Reflexes sets range

Reflexes and e-Reflexes sets are the previous range of Alcatel-Lucent terminals.
They are no more available in case of a new installation.

Reflexes sets are connected via UA link

For Common hardware

UAI & MIX boards

For Crystal hardware

UA & e-UA boards

Possibility to add plugwares

V24
S0
Analog
CTI

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1064
Reflexes & e-Reflexes sets
Reflexes sets range

4004 4010 4020 4035

Monoline Caller Id Caller Id Caller Id
8 Memories Speaker Call by name Call by name
Wall mounted Wall mounted Hands free Hands free
Double lines Add on modules Add on modules
Physical integration Physical integration
of plugwares of plugwares
Dynamic keys
Navigator

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1065
Reflexes & e-Reflexes sets
e-Reflexes sets range

E-Reflexes sets are connected via IP link

On LANx or SLANx boards

All kinds of switch or hub

It is impossible to add a plugware as they already have a IP plugware.

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1066
Reflexes & e-Reflexes sets
e-Reflexes sets range

Caller Id Caller Id
Caller Id
Call by name Speaker
Call by name
Hands free Wall mounted
Hands free
Add on modules Double lines
Add on modules
Physical integration
Physical integration
of plugwares of plugwares
Dynamic keys
Navigator

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1067
Reflexes & e-Reflexes sets
Ergonomics Reflexes & e-Reflexes sets range

Navigator Large display

Dynamic keys
Ergonomic handset

Standard ITU-T 161

Keypad
Audio Control Keyboard according to the country

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1068
Reflexes & e-Reflexes sets
Ergonomics Reflexes & e-Reflexes sets range

Innovations
Alphabetic keyboard
Navigator and large display

2 x 40

Customized labels
Audio control keys Hide

Transparent Plastic

LCD supervision
grip

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1069
Reflexes & e-Reflexes sets
Ergonomics Reflexes & e-Reflexes sets range

Icons
Functions keys
Function activated

Function requiring an action

HP- HP+ Speaker & handset sound level

Resources keys (line, set): In multiline configuration

(blinking) Incoming call

Resource in dialing or in conversation with a set

Call on hold

Supervision keys: In multiline configuration

Supervised resources occupied
(blinking) Call in progress on the supervised

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1070
Reflexes & e-Reflexes sets
Ergonomics Reflexes & e-Reflexes sets range

Interactive display
Main principles – set at rest:
1st page
Up line: Status of the set, Do not disturb 20-01-05 14:23
date and time Forward IntCall RdV Julie Lulu
Down line: access to the functions
or to the programmed keys

4 next pages
10 functions by page on the Lyon Lille NYork Madrid London
Advanced DerApp Data JJK Lock Muriel
programmable by the user
access by dynamic keys

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1071
Reflexes & e-Reflexes sets
Ergonomics Reflexes & e-Reflexes sets range

Interactive display

Main principles – set in communication:

Up line
information about the call Wagner Charles is busy
(State of the called set, Callbk Intru On hold Msg
name of the caller...)

Down line
list of accessible Zimmer Jean // Duval Claude
End2°C Back Conf Transf
functions at time
access to the functions by
dynamic keys

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1072
Reflexes & e-Reflexes sets
Add on modules

The add-on modules increase the number of programmable keys of a set.

There are two types of add-on modules:

20 or 40 keys

4090 M 4090 L

3 add on modules in maximum by set

60 keys in maximum by set

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1073
Reflexes & e-Reflexes sets
Connection of e-Reflexes sets range

Local power Ethernet Ethernet

connection connection
PC<-> IP-phone IP-phone <-> LAN

110 V

Customer LAN

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1074
Reflexes & e-Reflexes sets
Connection of e-Reflexes sets range

Ethernet
Remote power connection
PC<-> IP-phone Ethernet
connection
IP-phone <-> LAN
Transmission/Reception
and 0/-48V
Power supply

Customer LAN

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1075
Reflexes & e-Reflexes sets
Connection of e-Reflexes sets range

Rear IP-Phone view

PC
Connection Power supply
Connection

LAN
Connection

Alcatel-Lucent OmniPCX Enterprise – Reflex & e-Reflex sets

Ref. ENTP0403P06TEUS Issue 04

1076
Alcatel-Lucent OmniPCX Enterprise
E-Reflexes management

PROCEDURE

OBJECTIVE

- To learn how to manage an e-Reflexes

- IP parameters: IP address, IP mask,…

- A telephone binary linked to the PCX release.

They can be assigned by static or dynamic configuration.
In case of static IP configuration, the manager defines the IP data set by set.
In case of dynamic configuration, IP network data is transmitted by a DHCP server

Issue 02 Ref. ENTP0403C07TEUS.doc P. 1

PROCEDURE

1. e-Reflexes set creation

Application mgr
Login mtcl
Path Users
Action Create
Entry Directory number: (for example: 3140)
Shelf Address: 255
Board Address: 255
Equipment Address: 255
Set type: (for example: 4037 (4035 & TSC IP))
Action Press CTRL+v two times to validate the creation
Action Press CTRL+c as many times as needed to come back on main menu

2. Management on the e-Reflexes set

2.1. In dynamic mode

The dynamic mode has to be selected thanks to the supervisor mode on the e-
Reflexes set.
By pressing Menu + #, the supervisor mode can be reached.

Menu + #

1. Mac Address 3. Versions

2. IP Parameters 4. Others

1. Mode (Dynamic) 3. Subnet Mask

2. IP Address 4. Router Address

Menu of set display

P. 2 Ref. ENTP0403C07TEUS.doc Issue 02

2.2. In static mode

The static mode has to be selected thanks to the supervisor mode on the e-Reflexes
set.
By pressing Menu + #, the supervisor mode can be reached. (Press # to validate the
modifications)

Menu + #

1. Mac Address 3. Versions

2. IP Parameters 4. Others

1. Mode (Statique) 3. Subnet Mask

2. IP Address 4. Router Address

1. Mode (Statique) 3. Subnet Mask

2. IP Address 4. Router Address

IP Address: 010.001.001.075

1. Mode (Statique) 3. Subnet Mask

2. IP Address 4. Router Address

Subnet Mask: 255.255.255.000

1. Mode (Statique) 3. Subnet Mask

2. IP Address 4. Router Address

Router Address: 010.001.001.254

Issue 02 Ref. ENTP0403C07TEUS.doc P. 3

3. Subnet Mask 5. TFTP Address

4. Router Address 6. CPU Address

TFTP Address:: 010.001.001.001

1. Mode (Statique) 3. Subnet Mask

2. IP Address 4. Router Address

Press two times 0 to leave the menu

P. 4 Ref. ENTP0403C07TEUS.doc Issue 02

e-Reflexes

OBJECTIVES

To check the status of an e-Reflexes set

To check the global status of e-Reflexes

To check the information linked to e-Reflexes

Alcatel-Lucent OmniPCX Enterprise – e-Reflexes

Ref. ENTP0403M01TEUS Issue 02

1081
Display during initialization phase

Exchange of signaling with the virtual INT-IP

Download starttscip
Downloading of the file starttscip

Download bintscip
Downloading of the file bintscip

Downloading
Download lanpbx.cfg
of the file
andlanpbx.cfg and connection
trythe
to to reach
TFTP server
the TFTP server

Downloading of the IP@. Look for a DHCP server

in dynamic mode

Bootstrap

Alcatel-Lucent OmniPCX Enterprise – e-Reflexes

Ref. ENTP0403M01TEUS Issue 02

1082
Error codes

Error code Status info Meaning

1.1 NoMacAddress No Ethernet address stored in flash.
1.2 NoDhcpServer No DHCP server responding.
1.3 BadLocalIpAddress Bad local IP address.
1.4 BadTftpIpAddress Bad TFTP server IP address.
1.5 BadRouterIpAddress Bad router IP address.
1.6 RouterNotResp Router does not respond to ping.
1.7 IpInitError Error during IP initialization.
1.8 EtherInitError Ethernet interface initialization error.
1.9 IpDupli xxxxxxxxxxxx Duplicate IP address with xxxxxxxxxxxx MAC equipment address.
2.1 LoadCfgNotResp TFTP server not responding. Impossible to download configuration file.
2.2 LoadCfgRemoteError Configuration file download error on remote side.
2.3 LoadCfgLocalError Configuration file download local error (e.g. memory allocation error).
3.1 LoadBinNotResp TFTP server not responding. Impossible to download binary file.
3.2 LoadBinRemoteError Binary file download error on remote side (e.g. no binary file on server, CPU is not operating).
3.3 LoadBinChecksumError Binary file download error - Calculated and great header checksums are different.
3.4 LoadBinLocalError Binary file download local error.
3.5 LoadBinHeaderError Binary file download – Bad length in header of downloaded binary.
3.6 LoadBinFileTooLarge Binary file download. File to large for flash memory capacity.
3.7 LoadBinGetErBadFile Binary file download. Bad file name.
4.1 BinUpdateFailed Binary file update in flash memory failed.
5.1 LoadStartNotResp TFTP server not responding. Impossible to download start file.
5.2 LoadStartLocalError Start file download local error (ex: memory allocation error).
5.3 LoadStartRemoteError Start file download error on remote side (e.g. incoherent port number).
6.1 UaLinkLost UA link lost with PBX.
6.2 AomNotSupported Add-on module not supported. Bad version of add-on module.

Alcatel-Lucent OmniPCX Enterprise – e-Reflexes

Ref. ENTP0403M01TEUS Issue 02

1083
E-Reflexes status

termstat d 31500
+COUPLER_INFORMATIONS -------------------------------------------------------+
| Logic coupler type: CPL_UA |
| MAO coupler type: UA_FICTIF |
| Coupler state: REGISTERED NOT INITIALIZED |
+-------------------------------------------------(PRESS ANY KEY TO CONTINUE)+
[1]: Device features.

+UA TERMINAL ----------------------------------------------------------------+

Alcatel-Lucent OmniPCX Enterprise – e-Reflexes

Ref. ENTP0403M01TEUS Issue 02

1084
E-Reflexes status

ippstat d 31500

Logic coupler type: CPL_UA

MAO coupler type: UA_FICTIF
Coupler state: IN SERVICE
Terminal state: OUT OF SERVICE
Terminal type: IP PHONE
+----------------------------------------------------------------------------+
| Cry:Cpl:ac:term | neqt |nulog| typ term | dir nb | Out of service cause |
+----------------------------------------------------------------------------+
| 19 1 0 10 | 0797 | 17|4035(MR2_3| 31500 | . . . . . . . . . . |
+----------------------------------------------------------------------------+
|A: att_mserv, C: hs_defich, I: hs_isolauto, X: hs_isolman, T: hs_terdef |
|U: hs_usdef, P: hs_errparite, B: hs_bascul, Y: hs_cristisol, N: hs_inex |
+----------------------------------------------------------------------------+

Alcatel-Lucent OmniPCX Enterprise – e-Reflexes

Ref. ENTP0403M01TEUS Issue 02

1085
Actions on e-Reflexes set

outserv d 31500
Put the e-Reflexes set out of service

inserv d 31500
Put the e-Reflexes set into service

termstat d 31500
5. reset the device
initialize the TSC IP

Ping the e-Reflexes set

ping 155.131.1.40

64 bytes from 155.131.1.40: icmp_seq=0. time=0. ms

64 bytes from 155.131.1.40: icmp_seq=1. time=0. ms

Alcatel-Lucent OmniPCX Enterprise – e-Reflexes

Ref. ENTP0403M01TEUS Issue 02

1086
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

1087
NOTES

_____________________________________________________________________________________________________________________________________________________

Al c at el -Luc ent Universit y – ht t p s://www.b usinessp ar t ner.alcatel-lucent.c o m

1088

OXE Training - Complete (2011)
80% (5)
OXE Training - Complete (2011)
94 pages
Alcatel Contact Center - CCD Starter
50% (2)
Alcatel Contact Center - CCD Starter
416 pages
4760 Installation Guide
No ratings yet
4760 Installation Guide
62 pages
OXO Configuration VLAN
No ratings yet
OXO Configuration VLAN
4 pages
Training Offer For Network en PDF
No ratings yet
Training Offer For Network en PDF
60 pages
ENTPCTE103EN Beta2 Letter
75% (4)
ENTPCTE103EN Beta2 Letter
232 pages
ENTPCTE104EN Beta2 Letter PDF
100% (1)
ENTPCTE104EN Beta2 Letter PDF
1,040 pages
System Networking PDF
100% (1)
System Networking PDF
432 pages
Postsales OmniPCX Enterprise R10.1
100% (3)
Postsales OmniPCX Enterprise R10.1
54 pages
System Installation PDF
100% (1)
System Installation PDF
178 pages
System Expert PDF
No ratings yet
System Expert PDF
370 pages
Alcatel-Lucent - Presales - TrainingGlobal - Training - Offer 2010
No ratings yet
Alcatel-Lucent - Presales - TrainingGlobal - Training - Offer 2010
71 pages
00-Starter Pack Enterprise
100% (2)
00-Starter Pack Enterprise
1,214 pages
Omnipcx Enterprise Purple - Presales
No ratings yet
Omnipcx Enterprise Purple - Presales
149 pages
OXE Crystal HW Evolution
No ratings yet
OXE Crystal HW Evolution
12 pages
Alcatel-Lucent Omnipcx Enterprise: NGP: New Generation Platform
No ratings yet
Alcatel-Lucent Omnipcx Enterprise: NGP: New Generation Platform
11 pages
OmniPCX Enterprise Presentation
No ratings yet
OmniPCX Enterprise Presentation
44 pages
TC1619 MyICPhone 8082 Installation-Troubleshooting Guide en Ed02
No ratings yet
TC1619 MyICPhone 8082 Installation-Troubleshooting Guide en Ed02
13 pages
ENTPXTE400EN
100% (1)
ENTPXTE400EN
769 pages
Alcatel Omnivista 4760 Client Installation
No ratings yet
Alcatel Omnivista 4760 Client Installation
6 pages
OXOCXTE300EN
No ratings yet
OXOCXTE300EN
458 pages
TCV039en Ed07
No ratings yet
TCV039en Ed07
30 pages
ENTP0400P13TEUS
No ratings yet
ENTP0400P13TEUS
34 pages
Mitel 3300cxi 3300cx en
No ratings yet
Mitel 3300cxi 3300cx en
4 pages
Alcatel-Lucent Omnipcx Enterprise Communication Server
100% (1)
Alcatel-Lucent Omnipcx Enterprise Communication Server
14 pages
CCD II Basic Alcatel Contact Center - CCD Basic
0% (1)
CCD II Basic Alcatel Contact Center - CCD Basic
350 pages
Of00te600us 03
100% (1)
Of00te600us 03
600 pages
OXOCXTE301EN
No ratings yet
OXOCXTE301EN
579 pages
Univerge: Communication Solution
No ratings yet
Univerge: Communication Solution
16 pages
Omnivista 8770 Network Management System Datasheet en
No ratings yet
Omnivista 8770 Network Management System Datasheet en
2 pages
Alcatel Multi PCX Service
No ratings yet
Alcatel Multi PCX Service
8 pages
Installation Admin Guide
100% (2)
Installation Admin Guide
87 pages
Omnivista 8770
No ratings yet
Omnivista 8770
79 pages
OXE Hardware Description
67% (3)
OXE Hardware Description
39 pages
Omni Vista
No ratings yet
Omni Vista
79 pages
Omc Alcatel PDF
0% (1)
Omc Alcatel PDF
2 pages
Alcatel-Lucent Application Partner Program API Definitions
No ratings yet
Alcatel-Lucent Application Partner Program API Definitions
45 pages
Entity
100% (1)
Entity
3 pages
OXE Avaya
No ratings yet
OXE Avaya
24 pages
Release Note ACTIS24.1.x en Ed1
No ratings yet
Release Note ACTIS24.1.x en Ed1
29 pages
Troubleshooting Guide Omnipcx Enterprise
No ratings yet
Troubleshooting Guide Omnipcx Enterprise
16 pages
Alcatel OmniPCX Installation Manual en R1 1 Ed02
100% (3)
Alcatel OmniPCX Installation Manual en R1 1 Ed02
131 pages
Alcatel
100% (2)
Alcatel
53 pages
Troubleshooting Guide
No ratings yet
Troubleshooting Guide
130 pages
Alu Oxe 10.1 en
No ratings yet
Alu Oxe 10.1 en
80 pages
Alcatel-Lucent Omnipcx Enterprise: Sip Survivability With Pcs
100% (2)
Alcatel-Lucent Omnipcx Enterprise: Sip Survivability With Pcs
9 pages
8770 R5.0 - Product Presentation Dec 2021
No ratings yet
8770 R5.0 - Product Presentation Dec 2021
21 pages
Oxo Connect SMB Datasheet en
No ratings yet
Oxo Connect SMB Datasheet en
7 pages
Training Offer For Customers
No ratings yet
Training Offer For Customers
11 pages
Alcatel Contact Center CCD Expert PDF
100% (1)
Alcatel Contact Center CCD Expert PDF
572 pages
Postsales Network Management
No ratings yet
Postsales Network Management
14 pages
External Services PDF
No ratings yet
External Services PDF
348 pages
Binder1 PDF
No ratings yet
Binder1 PDF
3,140 pages
Proportional Hydraulis TP701
No ratings yet
Proportional Hydraulis TP701
152 pages
Alcatel OmniPCX Enterprise R7.0 Û Intensive - US
No ratings yet
Alcatel OmniPCX Enterprise R7.0 Û Intensive - US
6 pages
Presales Training Offer
100% (1)
Presales Training Offer
76 pages
WB TP 501
No ratings yet
WB TP 501
296 pages
Hydraulic Basics
No ratings yet
Hydraulic Basics
204 pages
GMST pp809 - en P
No ratings yet
GMST pp809 - en P
2 pages
Infineon IKW25N120H3 DataSheet v01 10 en
No ratings yet
Infineon IKW25N120H3 DataSheet v01 10 en
17 pages
What Are The Benefits of An LGA (Land Grid Array)
No ratings yet
What Are The Benefits of An LGA (Land Grid Array)
9 pages
Hardware Software
No ratings yet
Hardware Software
16 pages
TQ 8800 Manual
No ratings yet
TQ 8800 Manual
13 pages
dmn4800lss 1
No ratings yet
dmn4800lss 1
6 pages
c5198 Transistor Datasheet
No ratings yet
c5198 Transistor Datasheet
3 pages
18 Computer Mouse
No ratings yet
18 Computer Mouse
22 pages
Computer Architecture
No ratings yet
Computer Architecture
27 pages
TreasureHawk PDF
0% (1)
TreasureHawk PDF
2 pages
Department of Education: Tablet/Laptop Borrower'S Form
No ratings yet
Department of Education: Tablet/Laptop Borrower'S Form
2 pages
Datasheet HDD-MG06ACAxxx
No ratings yet
Datasheet HDD-MG06ACAxxx
2 pages
ILER-40: QRP SSB Transceiver in Kit Manual Assembly
100% (1)
ILER-40: QRP SSB Transceiver in Kit Manual Assembly
37 pages
4 - Chapter 4 - DC Biasing-BJTs
No ratings yet
4 - Chapter 4 - DC Biasing-BJTs
63 pages
CSC 109 New Notes 2017
No ratings yet
CSC 109 New Notes 2017
62 pages
Service Manual: HCD-C770/C990
No ratings yet
Service Manual: HCD-C770/C990
140 pages
1756 Controllogix I/O Specifications: Technical Data
No ratings yet
1756 Controllogix I/O Specifications: Technical Data
274 pages
Module - 07 F2833x PWM, Capture and QEP
No ratings yet
Module - 07 F2833x PWM, Capture and QEP
90 pages
MIL STD 1605A - EMI Survey PDF
No ratings yet
MIL STD 1605A - EMI Survey PDF
16 pages
GSB Solar Product Catalog A4
100% (1)
GSB Solar Product Catalog A4
40 pages
What Is SMD (Surface Mounted Devices) ?: Source
No ratings yet
What Is SMD (Surface Mounted Devices) ?: Source
2 pages
324309-BASIC POWER ELECTRONICS (1)
No ratings yet
324309-BASIC POWER ELECTRONICS (1)
8 pages
MTCH102/5/8: 2, 5 and 8-Channel Proximity/Touch Controller Data Sheet
No ratings yet
MTCH102/5/8: 2, 5 and 8-Channel Proximity/Touch Controller Data Sheet
37 pages
Laboratory Exercise 9: A Simple Processor
No ratings yet
Laboratory Exercise 9: A Simple Processor
8 pages
Infineon-650V TRENCHSTOP 5 D2Pak IGBT-ApplicationNotes-V02 00-En
No ratings yet
Infineon-650V TRENCHSTOP 5 D2Pak IGBT-ApplicationNotes-V02 00-En
23 pages
toshiba satellite L510
No ratings yet
toshiba satellite L510
2 pages
Controlled Rectifiers
No ratings yet
Controlled Rectifiers
85 pages
1_KQCPET6 V8 and DDR34 post card (smile)
No ratings yet
1_KQCPET6 V8 and DDR34 post card (smile)
40 pages
Week6 Tutorial-Chapter4 and Chapter5 With Solution
No ratings yet
Week6 Tutorial-Chapter4 and Chapter5 With Solution
48 pages
25 Serial Peripheral Interface (SPI)
No ratings yet
25 Serial Peripheral Interface (SPI)
53 pages
Bit Fields
No ratings yet
Bit Fields
22 pages

Basico PDF

Uploaded by

Basico PDF

Uploaded by

Alcatel-Lucent OmniPCX Enterprise

Part 1/3 PARTICIPANT’S GUIDE

Enterprise Solutions Training

All Rights Reserved © Alcatel-Lucent 2008

VALUE ADDED OPTIONS

To complement the basic portfolio by value added solutions or applications:

To answer to customer standard customization:

For a quick start of the solution:

I=x h represents an optional training course, not involved in

I = x h stands for Individual learning, in hours

Users Profiles I=2h On Site Mobility DECT C=2d Hotel

External Free Desktop

VoIP Technologies I=8h

Technology Overview Technology Overview Technology Overview Technology Overview

On Site Mobility DECT On Site Mobility DECT

Removed from Alcatel-Lucent OmniPCX Enterprise offer

Release 8.x Release 9

Tap Lab OmniPCX Enterprise Tap Lab OmniPCX Enterprise

OmniMobility Expert OmniMobility Expert

OmniMessage 4635 Expert OmniMessage 4635 Expert

OmniMessage 4635 Advanced OmniMessage 4635 Advanced

Hotel / Healthcare Hotel / Healthcare

Technology Overview Series: IP Technology Overview Series: LAN

Technology Overview Series

Starter Pack Enterprise User Profiles

SOLUTION BASED OPTIONS

SOLUTION BASED OPTIONS for Corporate

On Site Mobility DECT Security Access

Multi Site Networking

VALUE ADDED OPTIONS

External services Off Site mobility

OmniMobility Tap Lab

OmniMessage 4635 Tap Lab

OmniMessage 4635 OmniMessage 4635 Expert

OmniMessage 4635 OmniMessage 4635 Advanced

Upgrade R8.x to R9 ACSE OmniPCX

On Site Mobility DECT ACSE OmniPCX

On Site Mobility DECT ACSE OmniPCX

ACSE OmniPCX ACSE OmniPCX

ACSE Upgrade ACSE Upgrade

REFERENCE ENTPTE900US DELIVERY LANGUAGE English (course material in English)

10 days Traditional classroom or practical sessions with tutorials (TAP LAB)

Tutored virtual training sessions accessible via an internet connection

MAXIMUM NUMBER OF PARTICIPANTS 12

REQUIRED TECHNICAL CONFIGURATION

All Rights Reserved © 2008, Alcatel-Lucent

Phase 1: i-learning 8 hours

Describe Alcatel-Lucent OmniPCX Enterprise global offer

All Rights Reserved © 2008, Alcatel-Lucent

Describe attendant sets and attendant groups principles

All Rights Reserved © 2008, Alcatel-Lucent

Phase 2: c-learning 10 days

All Rights Reserved © 2008, Alcatel-Lucent

All Rights Reserved © 2008, Alcatel-Lucent

Issue Date Issue Date

Alcatel-Lucent OmniPCX Enterprise R9.0 Starter Pack Enterprise 01 12/08

File reference: ENTPTE900US

CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION

1. Customer Site File (CPU CS)

2. Customer Site File (CPU Crystal)

3. Access to the system

4. Start & Stop the System

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent i

6. Empty database creation

8. Management tool: “MGR”

9. Management tool: “Alcatel-Lucent Expert tool”

10. Maintenance Web Tool

11. Shelves & Boards

12. Static Voice Guides

ii All Rights Reserved © 2008, Alcatel-Lucent REF. ENTPTE900US Issue 01

REF. ENTPTE900US Issue 01 All Rights Reserved © 2008, Alcatel-Lucent iii

15. Terminal Adapters

16. Prefix Plan

17. Suffix plan

18. Phone Feature Class of Services

19. Dynamic Voice guides