System Configuration PDF

Alcatel OmniPCX Enterprise
PARTICIPANT'S GUIDE
System Configuration
Part 1/3
REF. ENTPTE401US
This document has no contractual value and may
be changed or withdrawn at any time by Alcatel Issue 01
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 OmniPCX Enterprise R7.0 - Core
Technical Training offer
Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Legend
Page 2
represents training courses involved in ACSE certification

I=xh C=xd V=xd
Course name
COURSE REFERENCE
represents training courses involved in ACFE certification

I=xh C=xd V=xd
Course name
COURSE REFERENCE
I=xh C=xd V=xd
Course name
COURSE REFERENCE represents training courses involved in AQFP certification
represents training courses that are not involved in
I=xh C=xd V=xd
Course name
COURSE REFERENCE
certification program
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

Alcatel OmniPCX Enterprise R7.0
Newcomers
Page 3
SYSTEM EXPERT:
•Software loading & update C=4d
•CPU Duplication
•Alarms System Expert
•Maintenance & troubleshooting I= 6 h C=3d
SYSTEM NETWORKING: ENTPTE403
•Network architecture CCD Basic
•Hybrid links OTCCTE451
•Centralized services I= 7 h C=5d C or V = 3 d
•VPN
EXTERNAL SERVICES: System Networking External Services
•ARS, DISA, DID translation
ENTPTE402 ENTPTE408 or ENTPWB408
•Multi-entity
SYSTEM CONFIGURATION:
•Advanced services configuration
•Voice guides
•IP Touch & IP Phones I=12 h C = 3 d V or C = 5 d
•Level 2 maintenance
•Remote Maintenance Access System Configuration
ENTPTE401 or ENTPWB401 C=2d
VOICE SERVICES:
•4645 enhanced services
•Conferences Voice Services
ENTPTE406
SYSTEM INSTALLATION:
• OmniPCX Enterprise architecture
I= 6 h C=2d I= 2 h IP TOUCH PHONE FACILITIES:
• Hardware installation and cabling
•Every day use of phone
• Users basic management System Installation IP Touch Phone Facilities facilities on Alcatel 8 & 9
• System working check
ENTPTE400 CLIEU76 series

Associated Solutions
Page 4
OMNIMESSAGE 4635 EXPERT: GET AUTONOMY

• System parameters
• FAX Server C=3d C=5d ACSE
• Automated attendant OmniMessage 4635
• OPS, Incidents, Traffic analysis 4635 Advanced OmniMessage 4635 Expert R5.x
OMNIMESSAGE 4635 ADVANCED: 4635TE310 4635TE312
• Software loading
• Mailbox configuration & languages
management
MOBILITY EXPERT:
C=2d
• Radio coverage tools ACSE DECT
Mobility Expert
• DECT Engineering rules
• Radio coverage test AP00TE085
STARTER & ACCOUNTING:
•4760 client and server setup in simplified
mode
I = 13 h C=5d
•Put the accounting into service ACSE Accounting
Starter & Accounting
•Carrier cost configuration & codebook
4760TE800
HOTEL / HEALTHCARE: RUN BUSINESS

• Guest and room management modes
• Accounting C=3d
• Hotel services
ACFE
• AHL Hotel / HealthCare Hotel / Healthcare
• Suites ENTPTE409
I= 12 h C = 3 d V or C = 5 d
ENTPTE401 or ENTPWB401
Prerequisite

V-Lab Offer
Page 5
v-Lab
Audience
Alcatel OmniPCX Enterprise •Media-Gateway setup Engineers in charge of the installation
Architecture V = 0.5 d •Signaling back-up configuration
ENTPTAVA02 •Software downloading & the maintenance of stand alone
solutions
v-Lab
Audience
Alcatel OmniPCX Enterprise •Audit/Broadcast configuration Engineers in charge of the design,
Networking V = 0.5 d setup
ENTPTAVA03 •VPN overflow management installation & the maintenance of
•Hybrid link over IP configuration complex network solutions

TAP-Lab offer
Page 6
c-Lab
•Networking Audience
Alcatel OmniPCX Enterprise •VPN Overflow
Engineers in charge of the design,
TAP-Lab R7.x C=3d •Hybrid links
ENTPTA0A05 •ARS, DID and NPD installation & the maintenance of
•Voice Guides complex solutions

Certification offer
Page 7
c-learning
MCQ (60 Questions)+ c-lab
ACSE Core R7.x C: 1 Day
ENTPTC0C8
MCQ
MCQ (30 Questions)
ACFE Core R7.x I: 45 Min
ENTPTC2C6
MCQ
MCQ (20 Questions)
AQFP Core R7.x I: 30 Min
ENTPTC1C6

Page 8
www.alcatel.com

ACFE Core level
REFERENCE ENTPTE401US DELIVERY LANGUAGE English (course material in English)
DURATION METHOD
12 hours Virtual self-paced training on the computer
8 days Traditional class room 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 and the maintenance of an Alcatel OmniPCX Enterprise in
stand alone
OBJECTIVES
At the end of the course, the participant will be able to:

• Configure the system in stand alone:
o Hardware
o Users
o Trunk groups
o Major Phone services
• Ensure the level 2 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 configure a new system from the beginning.
PREREQUISITES
• To have attended Alcatel OmniPCX Enterprise System Installation training course (Ref.: ENTPTE400US)
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).
ACFE Core level
PROGRAM DESCRIPTION
Phase 1: i-learning 12 hours

Describe the range of terminals that can be connected to an Alcatel OmniPCX Enterprise:
• Alcatel IP Touch
• Alcatel 8 series
• Reflexes
• Mobiles 100/200
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 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
Describe attendant sets and attendant groups principles
Describe the principles of the internal calls distribution (attendant call)
Describe the principles of DECT/PWT mobility
Describe DECT/PWT equipment:
• Boards
• Base stations
• Terminals
Describe the internal accounting mechanisms
ACFE Core level
Describe the available remote maintenance solutions:

• e-RMA
• Crystal RMA
• RMA on common hardware
Phase 2: c-learning 8 days

Describe the tools and the training materials provided during the training course
Describe the Customer Site File
Refresh on system accesses and configuration tools
Create an empty database
Configure the IP addressing plan of the system
Install the licenses
Save and restore the licenses
Configure and screen out the dialing plan:
• Prefixes
• Suffixes
• Directory numbers
Configure and maintain the users
• IP Phone
• UA phones
• Plugwares
• Add-On modules
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.)
Describe and configure Manager / 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
ACFE Core level
Describe and configure the automatic callback on busy trunk group facility
Describe and modify the default DID translator
Describe and configure the external callback translator
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 and configure the Calling Line Identification service on analogue and digital trunk groups
Describe and configure the caller name display if managed in the personal directory
Describe, configure and maintain a DECT/PWT solution:
• Hardware configuration
• DECT/PWT users creation and registration
• Multi-ACT configuration
Describe the fields of the system messages
Edit the system messages
Describe, configure and maintain the direct speed dialing
Describe, configure and maintain an Alcatel OmniMessage 4645 voicemail system:
• Voicemail creation
• Mailboxes allocation
• Voicemail classes of services configuration
Describe, configure and maintain a twinset group
Configure and maintain a MLA group
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
Alcatel University Alcatel OmniPCX Enterprise
System Configuration toc.doc
DOCUMENTATION CHANGES
ISSUE DATE ISSUE DATE
01 03/06
Alcatel OmniPCX Enterprise System Configuration
File reference: ENTPTE401US
GENERAL SUMMARY
Part 1
CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION
1. IP Addressing Plan
ENTP0457P05TEUS.................................................................................................................9
ENTP0457C01TEUS ..............................................................................................................13
ENTP0457H01TEUS ..............................................................................................................15
2. Empty Database creation

ENTP0411P03TEUS...............................................................................................................19
ENTP0411C01TEUS ..............................................................................................................23
ENTP0411H03TEUS ..............................................................................................................27
3. Licenses
ENTP0412P09TEUS...............................................................................................................31
ENTP0412P11TEUS...............................................................................................................39
ENTP0412C01TEUS ..............................................................................................................45
ENTP0412C02TEUS ..............................................................................................................59
ENTP0412H03TEUS ..............................................................................................................65
Issue 01 REF. ENTPTE401US 0.1

© Copyright Alcatel Business Systems 2006
Transmission or copying of this document is not permitted without prior written authorization.
The wording "Document Alcatel Business Systems" must appear on all authorized reproduction.
1
Alcatel OmniPCX Enterprise Alcatel University
toc.doc System Configuration
4. Shelves and boards creation

ENTP0401P10TEUS...............................................................................................................69
ENTP0401C10TEUS ..............................................................................................................79
ENTP0401C11TEUS ..............................................................................................................91
ENTP0401C12TEUS ..............................................................................................................93
ENTP0401H10TEUS ............................................................................................................101
ENTP0401H11TEUS ............................................................................................................103
ENTP0401M01TEUS............................................................................................................105
5. Voice Guides
ENTP0439P01TEUS.............................................................................................................113
ENTP0439C01TEUS ............................................................................................................135
ENTP0439C02TEUS ............................................................................................................141
ENTP0439M01TEUS............................................................................................................149
ENTP0439M02TEUS............................................................................................................157
ENTP0439H02TEUS ............................................................................................................163
ENTP0439H01TEUS ............................................................................................................165
6. Users
ENTP0403P01TEUS.............................................................................................................169
ENTP0403P06TEUS.............................................................................................................175
ENTP0487P01TEUS.............................................................................................................189
ENTP0403P11TEUS.............................................................................................................199
ENTP0403C03TEUS ............................................................................................................211
ENTP0403C05TEUS ............................................................................................................215
ENTP0403C07TEUS ............................................................................................................223
ENTP0487C01TEUS ............................................................................................................229
ENTP0403M01TEUS............................................................................................................245
ENTP0403M04TEUS............................................................................................................251
ENTP0545M01TEUS............................................................................................................259
ENTP0403H01TEUS ............................................................................................................273
ENTP0403H02TEUS ............................................................................................................275
7. Terminal Adapters
ENTP0403P07TEUS.............................................................................................................279
ENTP0403C12TEUS ............................................................................................................285
ENTP0403H12TEUS ............................................................................................................291
0.2 REF. ENTPTE401US Issue 01

2
Part 2
8. Trunk groups
ENTP0409P01TEUS.............................................................................................................295
ENTP0409C02TEUS ............................................................................................................301
ENTP0409C03TEUS ............................................................................................................305
ENTP0409C05TEUS ............................................................................................................311
ENTP0409C07TEUS ............................................................................................................317
ENTP0409M01TEUS............................................................................................................325
ENTP0409M02TEUS............................................................................................................331
ENTP0409H01TEUS ............................................................................................................333
9. System synchronization
ENTP0437P01TEUS.............................................................................................................337
ENTP0437H01TEUS ............................................................................................................343
10. Automatic Callback on Busy Trunk Group

ENTP0481P01TEUS.............................................................................................................347
ENTP0481C01TEUS ............................................................................................................355
ENTP0481M01TEUS............................................................................................................359
ENTP0481H01TEUS ............................................................................................................363
11. DID Translator

ENTP0424P01TEUS.............................................................................................................367
ENTP0424C01TEUS ............................................................................................................375
ENTP0424H01TEUS ............................................................................................................381
12. External Callback Translator

ENTP0427P01TEUS.............................................................................................................385
ENTP0427C02TEUS ............................................................................................................389
ENTP0427H01TEUS ............................................................................................................391
13. Classes of services

ENTP0404P06TEUS.............................................................................................................395
ENTP0404C02TEUS ............................................................................................................403
ENTP0404H02TEUS ............................................................................................................413
14. Groups
ENTP0405P03TEUS.............................................................................................................417
ENTP0405C03TEUS ............................................................................................................429
ENTP0405C04TEUS ............................................................................................................431
ENTP0405M01TEUS............................................................................................................437
ENTP0405H02TEUS ............................................................................................................443

3
15. Multiline sets

ENTP0406P02TEUS.............................................................................................................447
ENTP0406C02TEUS ............................................................................................................457
ENTP0406C04TEUS ............................................................................................................463
ENTP0406H02TEUS ............................................................................................................469
16. Assistant / Manager groups

ENTP0407P01TEUS.............................................................................................................473
ENTP0407C02TEUS ............................................................................................................483
ENTP0407M01TEUS............................................................................................................493
ENTP0407H01TEUS ............................................................................................................497
17. External Calls Barring

ENTP0426P01TEUS.............................................................................................................501
ENTP0426C02TEUS ............................................................................................................517
ENTP0426M01TEUS............................................................................................................531
ENTP0426H01TEUS ............................................................................................................535
18. Automatic Route Selection (ARS)

ENTP0425P01TEUS.............................................................................................................539
ENTP0425C02TEUS ............................................................................................................551
ENTP0425M01TEUS............................................................................................................559
ENTP0425H01TEUS ............................................................................................................563
19. Attendants
ENTP0416P02TEUS.............................................................................................................567
ENTP0415P03TEUS.............................................................................................................575
ENTP0415P02TEUS.............................................................................................................595
ENTP0416C01TEUS ............................................................................................................609
ENTP0415C02TEUS ............................................................................................................617
ENTP0416M01TEUS............................................................................................................625
ENTP0415M01TEUS............................................................................................................627
ENTP0415H03TEUS ............................................................................................................629

4
Part 3
20. Calls Distribution

ENTP0418P01TEUS.............................................................................................................633
ENTP0418P02TEUS.............................................................................................................649
ENTP0418C01TEUS ............................................................................................................665
ENTP0418M01TEUS............................................................................................................677
ENTP0418H01TEUS ............................................................................................................681
21. DECT
ENTP0419P01TEUS.............................................................................................................685
ENTP0419P04TEUS.............................................................................................................693
ENTP0419C01TEUS ............................................................................................................699
ENTP0419C03TEUS ............................................................................................................703
ENTP0419C04TEUS ............................................................................................................707
ENTP0419M01TEUS............................................................................................................715
ENTP0419H02TEUS ............................................................................................................731
22. Twinset
ENTP0479P01TEUS.............................................................................................................735
ENTP0479C02TEUS ............................................................................................................745
ENTP0479H01TEUS ............................................................................................................749
23. Speed Dialing

ENTP0408P01TEUS.............................................................................................................753
ENTP0408C02TEUS ............................................................................................................761
ENTP0408H01TEUS ............................................................................................................765
24. Multiple Line Appearance (MLA)

ENTP0480P02TEUS.............................................................................................................769
ENTP0480C02TEUS ............................................................................................................787
ENTP0480H02TEUS ............................................................................................................797
25. Alcatel 4645

ENTP0432P01TEUS.............................................................................................................801
ENTP0432C01TEUS ............................................................................................................819
ENTP0432C02TEUS ............................................................................................................833
ENTP0432M01TEUS............................................................................................................837
ENTP0432H01TEUS ............................................................................................................845

5
26. MOXA V24/IP Box

ENTP0444P01TEUS.............................................................................................................849
ENTP0444C01TEUS ............................................................................................................857
ENTP0444M01TEUS............................................................................................................863
ENTP0444H01TEUS ............................................................................................................875
27. Database Save & Restore

ENTP0411P04TEUS.............................................................................................................879
ENTP0411C02TEUS ............................................................................................................883
ENTP0411H02TEUS ............................................................................................................889
28. RMA Solutions & System Messages

ENTP0431P01TEUS.............................................................................................................893
ENTP0431P06TEUS.............................................................................................................903
ENTP0431P07TEUS.............................................................................................................915
ENTP0431P08TEUS.............................................................................................................925
ENTP0421P01TEUS.............................................................................................................931
ENTP0431C06TEUS ............................................................................................................939
ENTP0431C08TEUS ............................................................................................................951
ENTP0431H08TEUS ............................................................................................................957

6
FEEDBACK SHEET
In order to improve the quality of the documentation, please report any errors found by returning
this sheet to the address below.
SECTION CHAPTER PAGE DESCRIPTION OF THE ERROR
Alcatel University
8 Rue de Kervézennec
CS 82802
29228 BREST CEDEX 2 - FRANCE
FAX: (33) 2 98 14 36 36
Please return this sheet to:
DATE:

7

8
System IP addressing

Transmission or copying of this document is not permitted without prior written authorization. 1
OBJECTIVE:
◆ To describe the call server IP address
Alcatel OmniPCX Enterprise – System IP addressing

Ref. ENTP0457P05TEUS Issue 01
9
Overview
The goal is to integrate on the customer’s LAN:
➨ The computers for maintenance, management or others

applications
➨ Alcatel OmniPCX Enterprise
➨ And every IP elements of installation (GD, INTIP, IP

phones,…)
➨ The tool used for management is netadmin


10
Overview
PC and Call server connection
Company’s LAN
Ethernet Cable
@IP: 10.253.1.50
@IP: 10.253.1.10 @IP: 10.253.1.1
Cable V24


11
Overview
IP management is very important for a good working of

the system
Next, the best procedure for a new installation:
➨ IP management with netadmin

➨ Role addressing* management with netadmin -m
➨ Creation of the empty database
➨ Loading of OPS

* The role addressing is used in case of duplication (2 Call Server)

12
Modify the IP settings
PROCEDURE
OBJECTIVE
- To learn how to modify the IP address and the subnet mask of the Alcatel OmniPCX Enterprise.
PROCEDURE
Issue 01 REF. ENTP0457C01TEUS.doc C.1

13
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 ? 10.253.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 ? 10.253.1.1.254

14
IP configuration management
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the call server IP configuration
MANAGEMENT
1. Connect the Windows terminal to the Call Server
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 “ipconfig” command
(with the different available options)
4. Use the “ping” command to test the IP connection
Issue 01 REF. ENTP0457H01TEUS.doc HO.1

15
IP configuration management

16
Alcatel University NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
Alcatel University – https://www.businesspartner.alcatel.com
17
NOTES Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
18
Database management

OBJECTIVE:
◆ To describe the Database management
Alcatel OmniPCX Enterprise – Database management

19
Database management
What is the database?
The database contains the customer’s configuration
The database is called MAO
Two tools are used for management
➨ MGR
➨ Alcatel Expert Tool
Ethernet cable
@IP: 10.253.1.1
@IP: 10.253.1.10 V24 cable


20
Database management
What can I do?
Create an empty database
➨ Starting point of the configuration (necessary for a new

installation)
Save & restore database
➨ Save the database is to copy from the Alcatel OmniPCX

Enterprise the customer’s configuration to a PC*
➨ Restore the database is to send from a PC the customer’s

configuration to the Alcatel OmniPCX Enterprise*

* With the Alcatel Expert Tool just on step, else in two steps with the using of swinst and one FTP session (See procedures)

21

22
Empty Database creation
PROCEDURE
Empty database creation
OBJECTIVE
- To learn how to create an empty database
REFERENCE
- System Documentation -> Technical documentation->Maintenance->swinst-> Database
management->creating new 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).

23
PROCEDURE
1. Swinst
On the call server
Login swinst
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

On the call server
Loading chorus/mix emulation layer:/etc/rc3.d/S98emulation(1): S98emulation
[ OK ]
Linux Mandrake for eMediate release 7.2 (Odyssey) for i486
Kernel 2.4.1-ll-dhs3 on an i486 / ttyS0
xa001001 login:
3. Swinst
On the call server
Login swinst
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
C.2 REF. ENTP0411C01TEUS.doc Issue 02

24
4. Restart the telephone

On the call server
Login swinst
Select 1. Easy Menu
8. start the telephone
Entry Please confirm to start the telephone (y/n, default y): ENTER

25

26
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)

27
HO.2 REF. ENTP0411H03TEUS.doc Issue 01

28
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
29
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
30
Licenses and OPS files

OBJECTIVES:
◆ To describe the principle of e-licensing and e-commerce
◆ To describe the role of the different OPS files
Alcatel OmniPCX Enterprise – Licenses and OPS files

31
Overview
The system of licenses allows to
➨ Supply a unique installation medium independently from the

applications bought by each customer
➨ Avoid the risks of fraudulent use of the software
➨ Define a commercial policy fitted to:
▼ The customer needs
▼ The market constraints
It is based on two distinct elements
➨ The licenses file
➨ The software locks controlled by the Call Server

OPS: Offer Preparing System

32
Definitions
The Call Server features and applications are controlled by

hardware/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 an 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

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.

33
Definitions
The system identifier (CPU-Id) is encrypted in the license

file and supply 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

eCom: Alcatel Internet server dedicated to receive orders for licenses and hardware
ACTIS: Alcatel 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.

34
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

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).

35
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

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

36
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)


37
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

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.

38
OPS

OBJECTIVE:
◆ To describe the OPS
Alcatel OmniPCX Enterprise – OPS

39
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 Omnivista 4760)

xx corresponds to the customers id

40
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 the two next files:
▼ hardware.mao
▼ software.mao (created from xx.swk)


41
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
▼ Copy and install the OPS files in one time


42
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 in your PC


43
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
▼ Copy OPS files from /usr3/mao/ to your PC (by passing to

/usr4/BACKUP/OPS/ automatically)


44
Save and restore licenses
PROCEDURE
OBJECTIVE
- To learn how to save and restore licenses
REFERENCE
- System Documentation -> System services -> License management
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. This licenses are unique.
When you receive a new system the licenses are already installed.

45
PROCEDURE
1. Save licenses
1.1 On the Call Server disk

On the call server
Login swinst
Password SoftInst
Result ALCATEL BUSINESS SYSTEMS
FACILITIES Main menu Installation FACILITIES 2.24.0
1 Easy menu
2 Expert menu
Q Exit
Your choice [1..2, Q] ?
Enter 2
FACILITIES Expert menu Installation FACILITIES 2.24.0
1 Packages installation
2 Deliveries installation
3 Cloning & duplicate operations
4 Backup & restore operations
5 OPS configuration
6 System management
7 Database tools
8 Software identity display
9 Remote download
Q Go back to previous menu
Enter 5

46

OPS management menu Installation FACILITIES 2.24.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
Your choice [1..8, Q]
Enter 1
Result Confirm the backup of OPS files on your cpu disk (y/n, default y):y
Result ops 2.0.2: operation successful
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
Remark: The OPS files are stored under /DHS3dyn/BACKUP/OPS
(the partition DHS3dyn corresponds to usr4)

47
1.2 From the Call Server disk on a PC

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

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
Enter ftp> bin
Result 200 Type set to I.
Remark:
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.
Remark:
Go to this specific folder to get the OPS files
Enter ftp> get hardware.mao
Result 200 PORT command successful.
150 Opening BINARY mode data connection for hardware.mao (3308 bytes).
226 Transfer complete
ftp: 3308 bytes received in 0.00Seconds 3308000.00Kbytes/sec.
Remark:
Save the file hardware.mao under c:/backup/
ftp> get fr02901a.swk

48

150 Opening BINARY mode data connection for fr02901a.swk (9539 bytes).
Remark:
Save the file fr02901a.swk under c:/backup/
Enter ftp> get fr02901a.hw
150 Opening BINARY mode data connection for fr02901a.hw (3308 bytes).
Remark:
Save the file fr02901a.hw under c:/backup/
Enter ftp> get fr02901a.zip
150 Opening BINARY mode data connection for fr02901a.zip (13848
bytes).
ftp: 13848 bytes received in 0.00Seconds 13848000.00Kbytes/sec
Remark:
Save the file fr02901a.zip under c:/backup/
Enter ftp> get fr02901a.sw4760
Remark:
Save the file fr02901a.sw4760 under c:/backup/
Remark: The name of OPS (fr02901a) depends of the customer, for each
system the name is different.

49
2. Restore licenses
2.1 From a PC to the Call Server disk

On Command prompt
Action On your PC: Start / Run… on the field Open enter “command”
Remark:
OPS are saved in a folder called “backup” for this example
Enter C:/> cd backup
C:/>ftp 155.132.1.1
220 xa0001001 FTP server (Version wu-2.6.1(1) Wed Feb 28 15:50:32
Enter User (155.132.1.1: (none)): mtcl
Password: mtcl
Remark:
Use the ftp connection to send OPS files on the cpu disk (155.132.1.1 = cpu
IP@)
Enter ftp> bin
Remark:
Enter ftp> cd /usr4/BACKUP/OPS
Remark:
Go to this specific folder to get the OPS files
Enter ftp> send hardware.mao hardware.mao
150 Opening BINARY mode data connection for hardware.mao (3308 bytes).
Remark:
hardware.mao is written two times to keep the good file format under
/usr4/BACKUP/OPS (No cap letters)
Enter ftp> send fr02901a.swk fr02901a.swk

50

Remark:
fr02901a.swk is written two times to keep the good file format under
Enter ftp> send fr02901a.hw fr02901a.hw
150 Opening BINARY mode data connection for fr02901a.hw (3308 bytes).
Remark:
fr02901a.hw is written two times to keep the good file format under
Enter ftp> send fr02901a.zip fr02901a.zip
150 Opening BINARY mode data connection for fr02901a.zip (13848
bytes).
Remark:
fr02901a.zip is written two times to keep the good file format under
Enter ftp> send fr02901a.sw4760 fr02901a.sw4760
Remark:
fr02901a.sw4760 is written two times to keep the good file format under
Remark:
See the chapter 2.1 to install this OPS files on the system

51
2.2 From the Call Server disk

On the call server
Login swinst
Password SoftInst
1 Easy menu
2 Expert menu
Q Exit
Enter 2
5 OPS configuration
6 System management
7 Database tools
9 Remote download
Enter 5
Enter 2

52
Result You are going to restore these OPS files from cpu disk
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 2004 Thu Feb 12 15:36:34 2004
OPS version = E0101 OPS version = E0101
1-Group Telephony = 9999 1-Group Telephony = 9999
2-Phonebook users = 9999 (0) 2-Phonebook users = 9999 (0) h/Help
q/Quit, Lines 1-23/202 (0%)
Remark:
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

53
Result Do you agree the new software keys (y/n): y

ooo Reading string-file /DHS3bin/oneshot/mtcl/objects.US0 ...
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/04 16:42> ...
ooo Compiling Command file "/tmpd/MGRYZODda" ...
ooo Job completed. at <23/02/04 16:42> ...
ops 2.0.2: operation successful
Tables updated. You must reboot your system
Press return
Remark:
OPS are now installed on the system

54
3. Check the OPS files

On the call server
Login swinst
Password SoftInst
1 Easy menu
2 Expert menu
Q Exit
Enter 2
5 OPS configuration
6 System management
7 Database tools
9 Remote download
Enter 5
ALCATEL BUSINESS SYSTEMS
Entrer 3
OPS administration

55
Remark:
This "swinst" menu is identical to the "spadmin" maintenance command
Result ooo Reading string-file/DHS3bin/oneshot/mtcl/objects.US0
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

Result (SP) Software Protection counters:
PANIC Flag : 0
Group Telephony Counter : 0
Call By Name Counter : 9
…
Remark:
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
Result Cpu Id 01 = 0000CC7F
Your System CPU-Id: 0000CC7F
System CPU-Id found
Handle 4760 = 123456AB
Timestamp:
Thu Feb 12 15:36:34 2004
Remark:
Check the presence of the CPU id for this OPS files
Select Choice 3: Check active file coherency
Result > Checking active file /DHS3data/mao/software.mao
File OK

56
Remark:
Check if the software.mao file is activated or not
Select Choice 4: Check active file coherency
File OK
Remark:
Select Choice 4: Install a new file
Remark:
Installation of the OPS files from the cpu disk (See chapter 1.1)
Select Choice 5: Read the system CPUID
Result Your System CPU-Id: 0000CC7F
Remark:
Read the cpu id of the system
Select Choice 6: CPU-Ids management
Result Spadmin: CPU-Ids management
---------------------------
Add CPU-Ids .....................................…. 1
Remove CPU-Ids .................................... 2
Update a CPU-Id ................................... 3
Back to previous ................................…. 0
Remark:
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
Remark:
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

57
Result OPS limits

Remanent size (Kb) = 12500
Number of stations = 512
Number of trunks = 512
Number of half-contexts = 512
Stand-alone = 0
Number of BLF = 1
Remark:
Display the limits given by the OPS
Select Choice 9: Display ACK code
Result Code: 0cb0
Remark:
This command displays the acknowledgement code. The acknowledgement
code is used for transferring licenses.

58
PROCEDURE
OBJECTIVE
- To learn how to save and restore licenses with Alcatel Expert Tool
REFERENCE
- System Documentation -> System services -> License management
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. This licenses are unique.
When you receive a new system the licenses are already installed.

59
PROCEDURE
1. Save OPS on the user’s hard disk

Application Expert tool Tab
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
Remark:
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 Tab
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
Remark:
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

60
3. Check the OPS files

Application On mtcl Tab
Login swinst > Expert menu > OPS configuration > OPS administration
Select 2. Expert menu
5. OPS Configuration
3. OPS Administration
Remark:
This "swinst" menu is identical to the "spadmin" maintenance command
Result ooo Reading string-file /DHS3bin/oneshot/mtcl/objects.US0 ...
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
Result (SP) Software Protection counters:
PANIC Flag : 0
Group Telephony Counter : 0
Call By Name Counter : 9
Remark:
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
Action Choice 2: Display active file
Result Cpu Id 01 = 0000CC7F
Your System CPU-Id: 0000CC7F
System CPU-Id found
Handle 4760 = 123456AB
Timestamp:
Thu Feb 12 15:36:34 2004

61
Remark:
Check the presence of the CPU id for this OPS files
Action Choice 3: Check active file coherency
File OK
Remark:
Action Choice 4: Check active file coherency
File OK
Remark:
Action Choice 4: Install a new file
Remark:
Installation of the OPS files from the cpu disk (See chapter 1.1)
Action Choice 5: Read the system CPUID
Result Your System CPU-Id: 0000CC7F
Remark:
Read the cpu id of the system
Action Choice 6: CPU-Ids management
Result Spadmin: CPU-Ids management
---------------------------
Add CPU-Ids ......................................…. 1
Remove CPU-Ids ..................................... 2
Update a CPU-Id .................................... 3
Back to previous .................................…. 0
choice:
Remark:
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
Action Choice 7: Display active and new file
Remark:
This command displays in two columns the contents of the current file and of
the file to be installed

62
Action Choice 8: Display OPS limits

Result OPS limits
Remanent size (Kb) = 12500
Number of stations = 512
Number of trunks = 512
Number of half-contexts = 512
Stand-alone = 0
Number of BLF = 1
…
Remark:
Display the limits given by the OPS
Action Choice 9: Display ACK code
Result Code: 0cb0
Remark:
This command displays the acknowledgement code. The acknowledgement
code is used for transferring licenses

63

64
Downloading 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 PC and call server.
2. Transfer the four OPS files from PC to call server via FTP.
3. Install these OPS files with swinst
4. Start or restart the telephone application.

65
Downloading and installation of OPS files via FTP

66
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
67
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
68
Media Gateway (IP and Crystal)

OBJECTIVE:
◆ To describe the Media Gateway (IP and Crystal)
Alcatel OmniPCX Enterprise – Media Gateway (IP and Crystal)

69
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

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

70
Overview
Different type of hardware are possible for the

configuration: Common hardware and Crystal hardware
Using of CPU-CS and Appliance Server

➨ With Common hardware only (Case 1)
➨ With Common hardware and Crystal hardware (Case 2)
Using of CPU5/6/7
➨ With Crystal hardware only (Case 3)
➨ With Crystal hardware and Common hardware (Case 4)


71
On CPU-
CPU-CS and AS
Case 1: Common hardware
Call Server: CPU-CS or AS
IP Media Gateway: GD IP Media Gateway: GD


72
On CPU-
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

INTIPB board in CPU position on Crystal hardware

73
On CPU-
CPU-CS and AS
Case 1 & 2: Common hardware and Crystal hardware
➨ Possibility to connect several IP and Crystal Media gateway

on the LAN (or WAN) with the same Call Server
➨ The Call Server are always in the rack 0*

▼ Position 6 and 10
➨ The IP and Crystal Media Gateway have their own shelf’s

number (except 18 and 19)

* 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 )

74
On CPU5/6/7
Case 3: Crystal hardware

Main ACT
Call Server: CPU5/6/7
Links:
- IP
- Digital
- Optical
Peripheral ACT Peripheral ACT


75
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


76
On CPU5/6/7
Case 3 and 4: Crystal hardware and Common Hardware
➨ You must define an shelf number for each rack

▼ For example 0 for the main ACT and 1, 2,… for the peripheral ACT
➨ The rack 19 is reserved for the IP-link
➨ For a Crystal hardware Call Server no rack 18 (4645 not

used by this type of hardware)


77
On CPU5/6/7
The Boards are different according to the type of hardware

used
➨ For the Common hardware

▼ In management the name of the boards start by MG-xxx
✦ Example: MG-UAI8
➨ For the Crystal hardware

▼ In management the name corresponds to the “real” name of the
board
✦ Example: UA32


78
IP Media Gateway management
PROCEDURE
OBJECTIVE
- To learn how to manage an IP Media gateway and GD
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

79
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

80
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.
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

81
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
2.1.3 Management of the compressors daughterboard in the GD
2.1.3.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 |
|-------------------------------------------------------|

82
2.1.3.2 Manage the daughterboard

Application mgr
Path Shelf/boards/
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)

83
2.2 Dynamic mode
2.2.1 DHCP Server Management

Application mgr Tab
Path DHCP configuration
Entry Configuration: DHCP Server
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
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
Select Apply modification

84

Application mgr

login admin
Password admin
Command su
Command mgconfig
Select 1. Startup mode
Select 6. Callserver address
2. Current mode is: MANUAL - switch to automatic? y
Select 8. Crystal number
Entry 0. Exit

85

Application mtcl
Command Config 1 -d
+-------------------------------------------------------+
|----|----|----------|---------|-----------|------------|
+-------------------------------------------------------+
|-------------------------------------------------------|
|-------------------------------------------------------|

Application mgr
Path Shelf/boards/
is not enabled
example.

86
2.3 Dynamic mode with reservation
Note: This method can be used if you receive a new GD from Alcatel (No binaries installed)

Application mgr Tab
Local Subnetwork
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
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
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)

87

Application mgr

login admin
Password admin
Command su
Command mgconfig
1. Startup mode
Select 1. Startup mode
Select 6. Callserver address
Select 8. Crystal number
Entry 0. Exit

88

Application mtcl
Command Config 1 -d
+-------------------------------------------------------+
|----|----|----------|---------|-----------|------------|
+-------------------------------------------------------+
|-------------------------------------------------------|
|-------------------------------------------------------|

Application mgr
Path Shelf/boards/
is not enabled
example.

89

90
Crystal shelf management
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 19 can not be used for the shelf number.

91
PROCEDURE
1. Create the Main Crystal shelf

Application mgr
Path Shelf
Action Create
Entry Create Shelf
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
Entry Shelf Role : + Main (Master)
Main Shelf Address : -1 (default value)
2. CPU management
Application mgr
Path Shelf/boards
Action Create
Entry Create Shelf
Shelf Address: 0
Board Address : 6
Board Type: + CPU7
Remark You can use : CPU5 step 3
CPU6 step 2

92
Remote Crystal Media Gateway management
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)

93
PROCEDURE
1. Create the remote ACT

Application mgr
Path Shelf
Action Create
Entry Create Shelf
Shelf Address: 3
Shelf Type: + ACT 14 Positions
Name of rack: -------------------
Entry Shelf Role : + Remote ACT
Main Shelf Address : 0
Remark The main shelf address is the main rack address
- Every time 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)

94
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
1 for ON
For examples:
Value of the
- shelf number = 2 switch
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…

95
2.2 Create the INTIPB board

Application mgr
Path Shelf/boards
Action Create
Entry Create Shelf
Shelf Address: 2
Board Address : 6
Board Type: + INTIPB
INTIP Daughterboard: 1 GIP6
No. of Compressors for IP Devices: 16
No. of Compressors for Gateway : 16
Remark Daughterboards used with the INTIP board
1 GIP6: one GIP6 daughterboard

2 GIP6: two GIP6 daughterboards
1 GIP6A: one GIP6A daughterboard
2 GIP6A: two GIP6A daughterboards
1 GIP4-4: 32 compressors
2.3 Management of the MAC address in the Ethernet parameters

Application mgr
Entry Board Ethernet Address: : 00:80:9f:31:03:1e
Action Press CTRL+C as many times as needed to come back on main menu
Remark Select the remote ACT containing the INTIPB board, then the Ethernet
parameters of the INTIPB board and enter the INTIPB board Ethernet address.

96
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)
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

Entry Config:chmode
Current IP Configuration Mode: Static

Enter new mode (0 Dynamic, 1 Static):1
Action Press Enter to validate
Entry Config:chip
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
Entry Config:save
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 !

97
2.5 IP configuration in Dynamic mode

Application mgr Tab
Local Subnetwork
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
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

98
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

Entry Config:chmode
Current IP Configuration Mode: Static

Enter new mode (0 Dynamic, 1 Static):0
Entry Config:save
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 !

99
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
Remark Daughterboards used with the INTIP board
1 GIP6: one GIP6 daughterboard
2 GIP6: two GIP6 daughterboards
1 GIP6A: one GIP6A daughterboard
2 GIP6A: two GIP6A daughterboards

100
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

101

102
Creation of Crystal Media Gateway
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 or the command config)
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
Remark: The INTIPB board starts, if there is (in minimum) one board created in the shelf (e.g.
UA32)

103

104
Coupler

OBJECTIVE:
◆ Use the maintenance tool to check the interfaces boards status
Alcatel OmniPCX Enterprise – Coupler

Ref. ENTP0401M01TEUS Issue 01
105
Coupler maintenance
Access to the maintenance web Tool
To access to the maintenance Web Tool, the URL used is:

▼ http or https://IP@ of the Call Server main/wtool/html/tools.html
▼ The account used to access to the tool is: mtcl

https is used if SSL security is implemented on the call server

106
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..


107
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

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

108
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


109

110
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
111
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
112
Voice Guides

OBJECTIVES:
◆ To describe the static and dynamic voice guides
◆ To describe the voice guides required in a CCd environment
◆ To describe the boards used to broadcast voice guides
◆ To talk about the voice guides format
◆ To describe the “Vgtransfer” tool
Alcatel OmniPCX Enterprise – Voice Guides

113
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 Reflexes set

or the AAS application


114
Voice Guides
Overview
The Alcatel OmniPCX Enterprise uses specific couplers for

voice guides:
➨ In case of crystal hardware
▼ VG or SU-VG with Flash-Card (phase-out hardware)
▼ Z20-VG boards
▼ GPA board with Flash-Card or RAM-Card (phase-out) or GPA2
▼ CPU6s2 board
➨ In case of common hardware
▼ GD or GA board


115
Voice Guides
Overview
Voice guides
➨ According to applications present 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)


116
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 mn of static guides)
▼ 1 x 7,5 MB of RAM Memory (1 x 15 mn of dynamic guides)

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.

21
117
Voice Guides
Hardware
Z20-VG board
➨ This board contains:
▼ 20 equipments for Z sets
▼ 1 VGU module
➨ The VGU part offers
▼ 4 MB of embedded flash (8 mn of static guides)
▼ 1 MB of embedded RAM (2 mn of dynamic guides)
▼ 13 channels to broadcast voice guides
➨ This board is planned for small installations

VGU: (Voices Guides Unit): Voice guides Module
There is only one area for the flash memory, so only one language file can be used.

118
Voice Guides
Hardware
CPU6s2 board
➨ This board has a VPU module quite the same

as the Z20VG VGU module
➨ The CPU6 board has an analog input for

on-hold music
➨ The VPU part offers
▼ 8 MB of embedded flash (16 mn of static guides)
▼ 1 MB of embedded RAM (2 mn of dynamic guides)
▼ 15 channels to broadcast voice guides

VPU: (Voices Processing Unit): Voice guides Module
There is only one area for the flash memory, so only one language file can be used.

119
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

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

120
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


121
Voice Guides
VG Recording
Alcatel Audio Station
➨ 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

The Alcatel 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).

122
Voice Guides
VG Recording
Alcatel Audio Station (next)
➨ Recording Alcatel Audio Station guides
▼ Outputs on Flash-Card, Floppy disks, CD-ROM, File ...
Prom
FTP Flash-Card
Call Server
Floppy disk
CD-ROM

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

123
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


124
Voice Guides
VG Recording
Registering guides on the GPA2 and GA / GD boards
Call Server System

4035+ IAK
Guides
/DHS3ext/vg/dhs
guide 1
guide 1’ ^ Ram Memory
guide
guide
2
3
^ Downloading (GPA2 / Gx)
selected guides
guide 4 ^
guide 4’’
etc...
Hard Disk
Alcatel Audio-station
(^) selection (made per set or management)

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.

22
21
125
Voice Guides
VG Transfer Tool
“VgTransferTool” software
➨ Start the installation of the tool with the setup.exe delivered

on the voice guides CD-ROM

The tool is compatible with: Windows 95, Windows 98, Windows Me, Windows NT4 and Windows 2000pro

126
Voice Guides
VG Transfer Tool
Select the destination folder


127
Voice Guides
VG Transfer Tool


128
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 )


129
Voice Guides
VG Transfer Tool
Connection to e-CS and guide type selection

Select e-CS and «connect»
Select the voice guide type


130
Voice Guides
VG Transfer Tool
Transferring the voice guides
Select «Transfer» and wait

For the message «Transfer
/DHS3ext/vgadpcm/flash/custom
completed »

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

131
Voice Guides
VG Downloading
The voice messages are played from GD or GA boards, or

GPA2, Z20VG, or CPU6 boards.
➨ Two different voice message file formats are offered,

depending on the board used to play them:
▼ G711 to play messages from:
✦ GPA2 board
✦ Z20VG board
✦ CPU6 board
▼ ADPCM 32 to play messages from:
✦ GD board with a virtual GPA board

✦ GA board with a virtual GPA board


132
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


133

134
Static voice guides
PROCEDURE
Static voice guides
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.
Note: External: music-on-hold (in most cases) played by a device external to the OmniPCX.

135
Static voice guides
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

136
Static voice guides
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.

137
Static voice guides
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
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
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
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

138
Static voice guides
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

139
Static voice guides
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
….

140
Dynamic Voice Guide
PROCEDURE
Dynamic Voice Guide
OBJECTIVE
- To learn how to record a dynamic voice guide by using a 4035 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

141
Dynamic Voice Guide
PROCEDURE
1. Hardware declaration (example given with GPA2 board)
1.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.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

142
Dynamic Voice Guide
2. Create the Voice guide

Application mtcl
Path System / voice guide / create
Parameters Voice guide n°: 866 (exemple)
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

143
Dynamic Voice Guide
5. Allow to the users “type 4035T” the possibility to record the voice
guide and enable the keyboard use
5.1 Filter a set of type 4035T, note down its phone facilities categories and enable
its alpha numeric keyboard.
Application mtcl
Path Users
Parameters Directory n: _ _ _ _ _
Set type: 4035T
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

144
Dynamic Voice Guide
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
VG messages management: Main menu
Record. Downld
6.3 Specify the voice guide number and apply: e.g. 866
On set
Action
Recording of VG message nbr : 866
Apply
6.4 Check the available duration on the board and valid

On set
Action
Maximum recording duration : 506.9 sec
Apply Cancel

145
Dynamic Voice Guide
6.5 Record the message using START

On set
Action
Recording of voice guide nbr : 866
Start Cancel
6.6 Stop the recording

On set
Action
Recording of voice guide nbr : 866 0:30
Stop Cancel
6.7 Validate your message (after listening to it or/and recording it again)

On set
Action
Recording of voice guide nbr : 866 0:30
Listen Rstart Apply Cancel

146
Dynamic Voice Guide
6.8 Name the file stored on hard disk corresponding to your guide (e.g.: greeting)
On set
Action
Enter the file name: greeting
Apply Delete Rubout Back
6.9 Enter a memo (eg.: pilot1 greeting)

On set
Action
Enter the memo: pilot1 greeting
greeting
Apply Delete Rubout Back

147
Dynamic Voice Guide
6.10 File creation

On set
Action
Patience: File creation in progress ..
«greeting» created for VG nbr: 866

Apply
6.11 Voice guide downloading on the board

On set
Action
Do you want to select this VG file ?
Yes No
6.12 Off hook

148
Voice Guides

OBJECTIVE:
◆ To ensure conference and voice guides maintenance

149
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 |
+-------------------------------------------------------------------------+
+-------------------------------------------------------------------------+
|-------------------------------------------------------------------------|
| 03 | 00 - MGD (MAIN ) --- 09/09 --- ( INT_A) INTIPA - 01 | 02 |
|-------------------------------------------------------------------------|


150
Voice Guides
Maintenance
(6)xa000006> vgstat 3 27




Static voice guides Language: 255 - Not used
Slot 5: No Memory Card


151
Voice Guides
Maintenance
+---------------+------+------+------+------+------+------+------+------+------+
+---------------+------+------+------+------+------+------+------+------+------+
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
GPATT 16 16 284
GPINACMOMEN 17 17 285
GPDONDIST 18 18 286
FILM_EXT 58 58 917
PBX_ABS 63 63 287
TONREVEIL 65 65 288
FILM_EET 68 68 289
// // // //
+---------------+------+------+------+------+------+------+------+------+------+
Dynamic messages configured but not downloaded:

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


152
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 | |

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.

153
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 equipements on this coupler:

- first dsp 0 terminal number : 0 ;
- last dsp 0 terminal number : 15 ;
- dsp 0 program : VG_PRG ;
- dsp 1 program : CONFERENCE_PRG ;


154
Voice Guides
Maintenance

- dsp 2 program : DTO_R2_PRG ;
Voice guide equipements 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;


155
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)


156
Voice Guides recording on Media Gateway

OBJECTIVE:
◆ To maintain the Voice Guides recording on Media Gateway
Alcatel OmniPCX Enterprise – Voice Guides recording on Media Gateway

157
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 |
+-------+-----+------+------+---------+-----+


158
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

Slot 2: Card status register = 4E Identifier = 3ba50162enaa



Static voice guides Language: 255 - Not used
Slot 5: Card status register = 3C

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)


159
Display of static guides, dynamic guides and recording

duration on one board (2/2)
...
+---------------+------+------+------+------+------+------+------+------+------+
+---------------+------+------+------+------+------+------+------+------+------+
MUSICATT 2 2
GPMERAC 3 3-D 271-D
GPNUMCOD 4 4 272
GPMANAUT 5 5 273
GPCONUDE 6 6 274
GPRV 7 7 275
….
Dynamic messages configured but not downloaded:
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


160
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 |
+------+-----------------+----+----+-----+------+---+-------------------------+


161
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


162
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 MOH
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.

163
Voice guides

164
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.

165
Voice guides

166
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
167
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
168
Sets

OBJECTIVE:
◆ To describe sets
Alcatel OmniPCX Enterprise – Sets

169
Sets
Global overview
Sets available on the Alcatel OmniPCX Enterprise

Modems Analog sets Fax group 3
Videophone
Z z
UA Z
S0
Attendant set
S0
UA
Digital set
IP
UA
S0 IP
DECT
RBS or IBS
Fax group 4


170
Sets
Global overview
Alcatel sets ranges
➨ Reflexes & e-Reflexes ranges
▼ The e-Reflexes sets range are connected on IP link

▼ The Reflexes sets range are connected on UA link
➨ X8/X9 series ranges
▼ The X8 series sets range are connected on IP link

▼ The X9 series sets range are connected on UA link

IP link connected on a LAN or WAN

UA link connected on UA board (UA=3B+D)

171
Sets
Global overview
Alcatel sets ranges (cont.)
➨ DECT sets and PWT sets
▼ Mobile 100/200 (DECT)

▼ TSC- DECT (plugware connected behind a reflexes set)
▼ Alcatel 4073 GS Pocket Pro PWT
Non-Alcatel ranges
▼ SIP sets
▼ ASCOM sets (DECT alarm)


172
Sets
Global overview
Analog sets and fax ranges
➨ All types of analog sets (Alcatel or others)
➨ All types of analog fax
Digital sets and fax ranges
➨ Sets connected on S0 (Alcatel TTN2 set or others)
➨ All types of digital fax


173

174
Reflexes & e-Reflexes sets

OBJECTIVE:
◆ To describe Reflexes & e-Reflexes sets
Alcatel OmniPCX Enterprise – Reflex & e-Reflex sets

175
Reflexes & e-
e-Reflexes sets
Reflexes sets range
Connected on UA link
➨ For Common hardware

▼ UAI & MIX boards
➨ For Crystal hardware

▼ UA & e-UA boards
Possibility to add plugwares
➨ V24, S0, Analog, CTI


176
Reflexes & e-
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


177
Reflexes & e-
e-Reflexes sets
e-Reflexes sets range
Connected on IP link
➨ On LANx or SLANx boards
➨ All kinds of switch or hub
Impossible to add plugwares


178
Reflexes & e-
e-Reflexes sets
✔ Caller Id ✔ Caller Id ✔ Caller Id

✔ Call by name ✔ Call by name ✔ Speaker
✔ Hands free ✔ Hands free ✔ Wall mounted
✔ Add on modules ✔ Add on modules ✔ Double lines
✔ Physical integration ✔ Physical integration
of plugwares of plugwares
✔ Dynamic keys
✔ Navigator


179
Reflexes & e-
e-Reflexes sets
Ergonomics Reflexes & e-
Navigator Large display

Dynamic keys
Ergonomic handset
Standard ITU-T 161

Keypad
Audio Control Keyboard according to the country


180
Reflexes & e-
e-Reflexes sets
Innovations
Alphabetic keyboard
Navigator and large display
2 x 40
Customized labels
Audio control keys Hide
Transparent Plastic
LCD supervision
grip


181
Reflexes & e-
e-Reflexes sets
Icons
➨ Functions keys
function activated
function requiring an intervention
HP- HP+ Speaker & handset sound level
➨ Resources keys (line, set): In multilines configuration
(blinking) Incoming call
resource in dialing or in conversation with a set
In hold
➨ Supervision keys: In multilines configuration

Supervised resources occupied
(blinking) Call in progress on the supervised


182
Reflexes & e-
e-Reflexes sets
Interactive display
➨ Main principles – set at rest:
➨ 1st page
• Up line: Do not disturb 20-01-05 14:23
Status of the set, Forward IntCall RdV Julie Lulu
date and time
• Down line: access to the

functions or to the programmed keys
➨ 4 next pages
• 10 functions by
Lyon Lille NYork Madrid London
page on the Advanced
DerApp Data JJK Lock Muriel
• programmable
by the user
• access by dynamic keys


183
Reflexes & e-
e-Reflexes sets
Interactive display
➨ Main principles – set in communication:
➨ Up line
Wagner Charles is busy
• information about the call Callbk Intru On hold Msg
(State of the called set, name
of the caller...)
➨ Down line
Zimmer Jean // Duval Claude
• list of accessible functions End2°C Back Conf Transf
at time
• access to the functions

by dynamic keys


184
Reflexes & e-
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

185
Reflexes & e-
e-Reflexes sets
Connection of e-
Local power Ethernet Ethernet

connection connection
PC<-> IP-phone IP-phone <-> LAN
220 V
Customer LAN


186
Reflexes & e-
e-Reflexes sets
Connection of e-
Remote power Ethernet

connection
PC<-> IP-phone
Ethernet
connection
IP-phone <-> LAN
Transmission/Reception
and 0/-48V
Power supply
Customer LAN


187
Reflexes & e-
e-Reflexes sets
Connection of e-
Rear IP Phone view
PC
Connection Power supply
Connection
LAN
Connection


188
X8/X9 series sets

OBJECTIVE:
◆ To describe the X8/X9 series sets
Alcatel OmniPCX Enterprise – X8/X9 series sets

189
X8/X9 series sets
X8 series sets range
Alcatel 4068 Alcatel 4038 Alcatel 4028 Alcatel 4018

IP touch IP touch IP touch IP touch
Adjustable graphical Adjustable graphical Adjustable graphical 1x20 character

color display 4 grey level display B&W display display
2 direction navigator 2 direction navigator 4 direction navigator 2 direction navigator
Direct access to Direct access to Direct access to Direct access to
directory directory directory directory
Hands Free Hands Free Hands Free Hands Free
Mute key Mute key Mute key Mute key
Redial key Redial key Redial key Redial key
Direct access to Direct access to Direct access to Direct access to
mailbox mailbox mailbox mailbox
10 soft keys (physical) 10 soft keys (physical) 6 soft keys (physical) 6 programmable
keys
40 programmable 40 programmable 40 programmable
soft keys soft keys soft keys
Alphabetic keyboard Alphabetic keyboard Alphabetic keyboard


190
X8/X9 series sets
IP Connectivity
➨ LAN
➨ PC
➨ Power *
➨ Add-on
➨ Handset
➨ Headset (jack)

* The IP Touch, like the IP Phone V2, is compatible with the 802.3af standard [power supply feeding through the Ethernet cabling (use
of a Power Patch Panel)]
Remark:
In case of cascaded configuration (an IP Touch connected behind an other one), the first IP Touch can use the power supply
feeding through the Ethernet cable, but the second IP-Touch (the last equipment) has to use its own external power supply
(The IP Touch is an Powered Device (PD), it means that it can only receive the power supply)

191
X8/X9 series sets
IP Connectivity
PC
USB LAN
Power jack
External ringing signal
Handset
Key modules Headset jack


192
X8/X9 series sets
Alcatel 4039 Alcatel 4029 Alcatel 4019
Adjustable graphical Adjustable graphical 1x20 character

4 grey level display B&W display display
2 direction navigator 4 direction navigator 2 direction navigator
Direct access to Direct access to Direct access to
directory directory directory
Hands Free on 4018 Hands Free on 4018 Hands Free on 4018
Mute key Mute key Mute key
Redial key Redial key Redial key
Direct access to Direct access to Direct access to
mailbox mailbox mailbox
10 soft keys (physical) 6 soft keys (physical) 6 programmable
40 programmable 40 programmable keys
soft keys soft keys
Alphabetic keyboard Alphabetic keyboard


193
X8/X9 series sets
UA connectivity
UA Link
Handset
Add on module Headset jack


194
X8/X9 series sets
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


195
X8/X9 series sets
Option on X8/X9 series sets
Additional key modules
➨ Two models
▼ 10 keys
▼ Electronic 14 keys
▼ 40 keys
➨ Limits
▼ 2 Add-on Modules per phone sets

▼ Up to 50 additional keys
▼ Add-on module shall be lined up, and the AOM10 shall only take
place at the end of the queue


196
X8/X9 series sets
Recommendation on X8/X9 series sets
MLA features
➨ Used an external add-on module to manage MLA

secondary keys
▼ All the keys of the virtual module are not displayed permanently
(several pages)
Executive group features
➨ Use an external add-on module to manage the executives

group keys
▼ All the keys of the virtual module are not displayed permanently
(several pages)


197
X8/X9 series sets
Restrictions on X8/X9 series sets
No sub-device for X8 series sets
New S0, Analog, and V24/CTI sub-devices for X9 series

sets and UA third generation extensions
X8/X9 series sets are not available for Attendant extension


198
IP-Phone specificities

OBJECTIVE:
◆ To describe the IP-Phone specificities
Alcatel OmniPCX Enterprise – IP-Phone specificities

199
IP-
Overview
The IP-phone is connected to the LAN and allows to

connect an other peripheral on a switched port.
It needs to dialog with the OmniPCX Enterprise Call server:
➨ Via an INT-IP A virtual coupler with Common hardware
➨ Via an INT-IP A physical coupler with Crystal hardware

The INTIP A handles the signaling of 4000 IP Phones

200
IP-
Overview
It is possible to configure the IP Phone IP address
➨ Manually
▼ Setup of the IP Phone flash
➨ Dynamically
▼ OmniPCX Enterprise is used as DHCP server or relay
▼ DHCP server of the customer (example Windows NT)
Binaries are downloaded in the IP Phone by the Call Server

of the OmniPCX Enterprise
For the UA signaling the IP Phone needs to dialog the INT

IP A coupler
Voice is using RTP connection


201
IP-
Overview
When the IP Phone is powered, the initialization phase

starts
During the initialization, it is possible to manage the IP

configuration in the flash manually


202
IP-
Overview
Initialization cycle (after the flash memory programming)
➨ IP configuration loading in memory
➨ lanpbx.cfg file loading from TFTP server IP @ managed in

the flash memory
▼ Contains the Call server MAIN IP address
➨ The IP-Phone software file is loaded from the Call Server in

the flash memory
➨ the file, containing the UDP port N° used by the IP Phone for
signaling channel, is loaded from the Call Server in the
flash memory


203
IP-
Overview
The IP Phone generates the dial tone and display the

message: SET
➨ Enter a set number created in the database as an IP Phone
The IP Phone generates the dial tone and display the

message: CODE
➨ enter the user personal code
If the set number is available and if the personal code is

right, the CPU updates its database with the MAC@ and
the IP@ of the TSC IP (and this one switch in service)


204
IP-
Overview
Connection of a registered IP Phone
➨ Initialization process phases (previously described)
➨ The Call Server checks if the MAC@ is in its database and

updates the IP@ if necessary.
➨ Then the IP Phone switches in service.


205
IP-
Overview
A DHCP server is mandatory
DHCP: Dynamic Host Configuration Protocol
➨ protocol used between a server and a client
➨ used by the OmniPCX Enterprise to allocate dynamically the

IP configuration to the IP Phones
▼ IP address
▼ Subnet mask
▼ Gateway
▼ TFTP server address


206
IP-
Overview
The OmniPCX Enterprise DHCP server can allocate IP @ to

Alcatel clients (IP-Phone, GD or INTIPB) and, if the option
is validated, other types of clients (PC…)
IP-Phone clients accept IP@ from the OmniPCX Enterprise

DHCP server and also from other DHCP servers
If those 2 type of DHCP servers are present on the LAN,

the Alcatel clients will answer in priority to OmniPCX
Enterprise DHCP server


207
IP-
Overview
When the IP Phone is powered, the initialization phase

starts
During the initialization it is possible to setup the IP

configuration in dynamic mode
Initialization cycle (after flash memory programming)
➨ The device looks for a DHCP server to obtain a full IP

configuration
➨ The next steps of initialization are identical in static or

dynamic mode


208
IP-
Overview
Communication between two IP Phones connected on the

same node
➨ No compressors used
➨ Direct RTP between IP Phone
Direct RTP allows compressors optimization between IP

Phones which belong to the same Alcatel OmniPCX
Enterprise


209
IP-
Overview
INT-IPA boards send to IP Phones the IP@ and the UDP

port N° of the called party to allow them to establish
directly the RTP connection
➨ Signaling exchange with the virtual INT-IP A

➨ Voice is exchanged directly between IP Phones
IP Phones generates the tones locally and needs a

connection with one GD only to receive voice guides or
"hold on" music (There is nothing to manage for this
feature)


210
DHCP server for IP-Phones

OBJECTIVE:
◆ To manage the DHCP server for IP-Phones
Alcatel OmniPCX Enterprise – DHCP server for IP-Phones

Ref. ENTP0403C03TEUS Issue 01
211
DHCP server for IP-
IP-Phones
Management
DHCP Configuration / local subnetwork/IP address range

(local network)
➨ Manage a range of IP addresses for IP phone in dynamic
mode.
Create: IP Address Range(local network)
Node Number (reserved) : 1

DHCP Configuration : 1
Instance (reserved) : 1
Range first address : 155.132.1.90
Range last address : 155.132.1.99


212
DHCP server for IP-
IP-Phones
Management
DHCP configuration / Review/modify

Review/modify: DHCP Configuration
Node number (reserved) : 1

DHCP Configuration : 1
Configuration : DHCP Server

Alcatel Terms only : YES
DHCP configuration / Apply modifications

Apply modifications: Configuration DHCP
No node-network (reserve soft) : 1

Configuration DHCP : 1


213

214
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
- 4035 (Advanced)
- 4020 (Premium)
- 4010 (Easy)
- 4004 (first)
- 4039 (x9 series)
- 4029 (x9 series)
- 4019 (x9 series)
- Analog

215
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
Remark 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
Remark Priority
YES: during a search for free directory numbers, the search will be made on
the priority range if no range is indicated.
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

216
3. Display free directory numbers

Application On mgr
Path System /Free directory numbers
Action Review/Modify
Entry 31000 31005
31001 31006
31002 31007
31003 31008
31004 31009
Remark 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
Select Set filters
Entry Terminal type == UA
Result 1- 1-32
1- 1-33
1- 1-34
1- 1-35
5. Display free addresses for Analog sets

Application On mgr
Path System / Free address
Select Set filters
Entry Terminal type == Z
Result 1- 1-64
1- 1-65
1- 1-66

217
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 + 4020
Remark 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
Note : sets available :

4035, 4020, 4010, 4004
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

218
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
Remark Directory number : select the number in the list
Physical addresses : select the number in the list (see 4)
-1 / -1 / -1 for automatic allocation
or 255/255/255 for resurrection
Set type : select the right type in the list
Note : sets available :
Analog
Action Press CTRL+C as many times as needed to come back on the main menu

219
8. Display terminal status

Application On the call server
Login mtcl
Command Termstat d 31000
Result +COUPLER_INFORMATIONS ----------------------------------+

| Logic coupler type : CPL_MIX
|
| MAO coupler type : MIX244
|
| 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.
Your choice [1-5, q for quit]: 1
[1] : Device features.
UA TERMINAL -------------------------------------------+
| Device: 1-1-0-32 Neqt: 1126
| Logic number: 16
| Terminal type: UA_MR2 Locked: No
| State: IN_SERV |
| Directory number: 31000 Set type: 4035(MR2_3G)
| Associate directory: 31000 PIN: 0000
| Overflow validate: No Multiline set: Yes
| PBX group number: none PBX state: OUTSIDE
| Dev.type: 0 Carac. Number: 8
| Set Revision: 03,32 DTI vers: 241
| Vta type: 3 Hardware Config: 123
+----------------------------(PRESS ANY KEY TO CONTINUE
Remark The set has been declared as 4020.The system detected a 4035 at the
connection, and have changed automatically the type in management
parameters

220
9. Display terminal status

Login mtcl
Command Listerm 1 1
Remark Listerm act-n° cpl-n°
--------------------------------------------------------------------
|Coupler: 1 1 Logic type: CPL_MIX Board: MIX244 State: IN SERVICE|
|------------------------------------------------------------------|
|Cry:Cpl:ac: term| neqt | typ term | dir nb |Out of service cause |
|------------------------------------------------------------------|
| 1 1 0 32 | 01126|4035(MR2_3| 31000 | . . . . . . . . . |
| 1 1 0 33 | 01127| T_RESU | | A . I . . . . . . |
| 1 1 0 34 | 01128| T_RESU | | A . I . . . . . . |
| 1 1 0 35 | 01129| T_RESU | | A . I . . . . . .|
| 1 1 0 64 | 01158| AUTPOS | 31100 | . . . . . . . . . |
| 1 1 0 65 | 01159| T_RESU | | A . I . . . . . . |
| 1 1 0 66 | 01160| T_RESU | | A . I . . . . . . |
| 1 1 0 67 | 01161| 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 : 2
|
UA TERMINAL -------------------------------------------------------+
|Device: 1-1-0-32 Neqt: 1126 |
|Logic number: 16 |
|Terminal type: UA_MR2 Locked: No |
|State: IN_SERV |
|Directory number: 31000 Set type: 4035(MR2_3G) |
|Associate directory: 31000 PIN: 0000 |
|Overflow validate: No Multiline set: Yes |
|PBX group number: none PBX state: OUTSIDE |
|Dev.type: 0 Carac. Number: 8 |
|Set Revision: 03,32 DTI vers: 241 |
|Vta type: 3 Hardware Config: 123 |
+----------------------------------------------- (PRESS ANY KEY TO
CONTINUE

221
10. Edit users

Login mtcl
Command edsbr
Entry enter criteria or command: dir
enter criteria or command: act
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 | 1| 10| 0|4035 |
|31100 | 1| 11| 0|ana |

222
e-Reflexes management
PROCEDURE
OBJECTIVE
- To learn how to manage an e-Reflexes
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.
In case of dynamic configuration, IP network data is transmitted by a DHCP server

223
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

224
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

225
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


IP Address : 010.001.001.075

Subnet Mask: 255.255.255.000

Router Address:: 010.001.001.254

226
3. Subnet Mask 5. TFTP Address

4. Router Address 6. CPU Address
TFTP Address:: 010.001.001.001

Press two times 0 to leave the menu

227

228
Configuration of Alcatel 8 series sets
PROCEDURE
OBJECTIVE
- To learn how to configure the Alcatel 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.

229
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

230
2. Forward management if IP extension out of service

Application mgr
Path Classes of service / Phone features 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
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.

231
3. Management of the “Applications COS”

Application mgr
Path IPTouch / IPTouch classes of service / COS applications
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
Remark 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

232
4. Management of the Phone COS

Application mgr
Path IPTouch / IPTouch classes of service / Phone COS
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/ IPTouch_parameters
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
Remark Select an Application COS between 0 to 31
Select a Phone COS between 0 to 31
(1) Default Home Page, 4 available choices:
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

233
6. IP configuration setup of the Alcatel 8 series terminal: static mode

Application On the station
Action Re-initialize the Alcatel series 8 extension
Remark To reset an Alcatel 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


234
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
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

235
Result
IP Parameters

IP Mode Static
IP addr 010.001.002.006
Subnet 255.255.255.255
Router 255.255.255.255
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

236
Result
IP Parameters

IP Mode Static
IP addr 010.001.002.006
Subnet 255.255.255.000
Router 010.001.002.100
Action Use the navigator key (“▼”) 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

237
Action
IP Parameters

IP addr 010.001.002.006
Subnet 255.255.255.000
Router 010.001.002.100
TFTP 010.001.002.003
Main Menu

Action Leave the menu

Action
Main Menu

Result
Initializing
Remark The Alcatel 8 series is re-initialized

238
Result
1/5 Network start
2/5 Network setup
3/5 Config download
4/5 Config download

239
Result
5/5 Connecting
Action Register the Alcatel 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 8 series extension (“0000” by default)
Action
Registration
Enter your pin code number :
Result The Alcatel 8 series is automatically re-initialized, then switches to “in servce”
mode

240
7. IP configuration setup of the Alcatel 8 series terminal: dynamic

mode
Application On the station
Action Re-initialize the Alcatel 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

Action Select « IP Parameters »

Action
Main Menu


241
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
Remark 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


242
Action Leave the “main menu”

Action
Main Menu

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

243

244
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 OmniPCX Enterprise – e-Reflexes

245
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
and
lanpbx.cfg and connection
try the
to to reach
TFTP server
the TFTP server
Downloading of the IP@. Look for a DHCP server

in dynamic mode
Bootstrap


246
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.


247
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 ----------------------------------------------------------------+

| Device: 19-1-10-0 Neqt: 797 |
| Logic number: 17 |
| Terminal type: UA_MR2: IP PHONE Locked: No |
| State: IN_SERV |
| Directory number: 31500 Set type: 4035(MR2_3G) |
| Associate directory: 31500 PIN: 0000 |
| Overflow validate: No Multiline set: Yes |
| PBX group number: 31400 PBX state: INSIDE |
| Dev.type: 0 Carac. Number: 8 |
| Set Revision: 03,32 DTI vers: 239 |
| Vta type: 3 Hardware Config: 123 |
+-------------------------------------------------(PRESS ANY KEY TO CONTINUE)+


248
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 |
+----------------------------------------------------------------------------+
+------+----------------------+---+-------+----------+------+-----------------+---------------+
| Indx | Mac Address | | Neqt | QMCDU | Name | Ip Address | TSCIP Type |
+------+----------------------+---+-------+----------+------+-----------------+---------------+
| 0001 | 00:80:9f:3b:0c:ae:00 | - | 00797 | 31500 | Will | 155.131.001.040 | TSCIPV1 |
| Sign | 19/1 | | NO CNX| ON CPL | | | |
+------+----------------------+---+-------+----------+------+-----------------+---------------+
Ip domain is: 0
Ip Voice Coding is IntraDom G723: ExtraDom G723
QOS parameters for category 0:
DSCP diffserv: 0
802.1Q used No
Vlan Identifier (Vid): 0
User priority (8021Q pri.): 5
Firmware version is Unknown on a 10 Mega hardware


249
Actions on e-
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


250
Users

OBJECTIVE:
◆ Use the maintenance Web tool to check the users status
Alcatel OmniPCX Enterprise – Users

251
Users maintenance
To access to the maintenance Web Tool, the URL used is:

▼ http or https://IP@ of the Call Server main/wtool/html/tools.html
▼ The account used to access to the tool is: mtcl


252
Users maintenance
Main menu

the system
release etc..


253
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 »


254
Users maintenance
Example of one user

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).

255
Users maintenance
Example of one out of order user

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.

256
Users maintenance
Example of one user in communication

In this example the user 31000 is connected to user 31001 (DEMI-COM INFORMATION, Partner direc: 31001)

257

258
Alcatel 8 & 9 Series Customization and Localization

OBJECTIVE:
◆ To check Alcatel 8 & 9 Series Customization and Localization features
Alcatel OmniPCX Enterprise – Customization and Localization

259
Checking the presence of the files
/usr2/downbin/
➨ Customization files
-rw-r--r-- 1 mtcl tel 85088 Sep 28 2005 /usr2/downbin/cust-default-40x8
➨ Localization files
-rw-r--r-- 1 mtcl tel 1114712 Dec 5 2005 /usr2/downbin/chi-4068
-rw-r--r-- 1 mtcl tel 414760 Dec 5 2005 /usr2/downbin/chi-40x8
-rw-r--r-- 1 mtcl tel 388279 Dec 5 2005 /usr2/downbin/chi-40x9
-rw-r--r-- 1 mtcl tel 1059568 Dec 5 2005 /usr2/downbin/jpn-4068
-rw-r--r-- 1 mtcl tel 382664 Dec 5 2005 /usr2/downbin/jpn-40x8
-rw-r--r-- 1 mtcl tel 343152 Dec 5 2005 /usr2/downbin/jpn-40x9
-rw-r--r-- 1 mtcl tel 618420 Oct 21 2005 /usr2/downbin/kor-4068
-rw-r--r-- 1 mtcl tel 207528 Oct 21 2005 /usr2/downbin/kor-40x8
-rw-r--r-- 1 mtcl tel 39271 Oct 21 2005 /usr2/downbin/kor-40x9

The cust-default-40x8 is used by all type of sets. This file contain different melodies compare with the default.
Chi=Chinese
jpn=Japanese
Kor=Korean

260
Checking the loading of all sets
tftp_check -c
===================== IP phones state ========================
Total Ip phone number: 3
In service: 2 Out of service: 1
===================== IP phones types =========================

V1 V1S V2 NOE A NOE B NOE C NOE D MIPT 300
0 0 1 0 0 1 1 0
========= In service IP phones version state =================

Code: Good version: 2 Bad version: 0
Data: Good version: 2 Bad version: 0
Localization: Good version: 2 Bad version: 0
Customization: Good version: 2 Bad version: 0
============== IP phones tftp init state =====================

Idle: 3 Locked: 0
Update eval. requested: 0 Update is on going: 0


261
Checking the loading of one set
tftp_check -n 1494
Terminal state: IN SERVICE
Terminal type: NOE D
Terminal segment versions are: code 03.60.20, data 03.60.20
Terminal localization file: kor-4068 version: 1.00.00
Terminal customization file: cust-default-40x8 version: 1.01.00
For this Terminal, call server versions are:
Code: 3.60.20
Data: 3.60.20
Localization: name: kor-4068 version: 1.00.00
Customization: name: cust-default-40x8 version: 1.01.00
Terminal tftp state is: IDLE
Current update action:NONE
tftp_check -s -t 5
IP terminal binary update will start in 5s

Tftp_check -n 1494: 1494 is the equipment N° of an IP touch

Tftp_check -s –t 5: after t is specified the number of seconds

262
Checking the available files for TFTP transfer
tftp_check –L
|---------------------------------------------------|
|---------------- LOCALIZATION FILES ---------------|
|---------------------------------------------------|
| Lang ID | file root name | model | version |
|---------------------------------------------------|
| |A|B|C|D| |
|---------------------------------------------------|
| 1 | kor-4068 |.|.|.|X| 1.00.00 |
| 1 | kor-40x8 |.|X|X|.| 1.00.00 |
| 2 | jpn-4068 |.|.|.|X| 1.00.00 |
| 2 | jpn-40x8 |.|X|X|.| 1.00.00 |
| 3 | chi-4068 |.|.|.|X| 1.03.00 |
| 3 | chi-40x8 |.|X|X|.| 1.03.00 |
|---------------------------------------------------|
|--------------------------------------------------------|
|--------------------- CUSTOMIZATION FILES --------------|
|--------------------------------------------------------|
| Cos ID | file name | model | version |
| bits | | | |
|--------------------------------------------------------|
| |A|B|C|D| |
|--------------------------------------------------------|
| 0x1 | cust-default-40x8|X|X|X|X| 1.01.00 |
|--------------------------------------------------------|

Be carrefull if the file is present in /usr7/client/bin or /usr2/downbin and not available in the table it means that the shutdown was
not done after the management of the languages in system.

263
Checking of the binary release
downstat i
***Current version for V1 Ip Phone (10 Mega) is 00.05.2
***Current version for V1s Ip Phone (100 Mega) is 00.03.0
***Current version for Ipp_Int Ip Phone Integre (100 Mega) is 2.27.00
***Current version for IP Touch is:
- soft version for 'IP Touch A' is 3.60.20
- data version for 'IP Touch A' is 3.60.20
- soft version for 'IP Touch B,C,D' is 3.60.20
- soft version for 'IP Touch B,C,D' is 3.60.20
- (1) use 'tftp_check -L' to see and force system to take new
Localization or customization files
** 3 Ip phones are declared on this node !!
** 1 Ip phones are not updated with the right binary !!
** 0 Ip phones can be reset for download !!
| IP Touch B,C,D already downloaded with version 3.60.20
+--------+--------------+--------------------+-+-----+---------------+----+
| QMCDU | Name | Mac Address | |Neqt | Ip Address |Type|
+--------+--------------+--------------------+-+-----+---------------+----+
|32000 |32000 |00:80:9f:56:49:78 |V|01494|010.048.020.102| Ipt|
|32001 |32001 |00:80:9f:56:61:b4 |V|01495|010.048.020.117| Ipt|
+--------+--------------+--------------------+-+-----+---------------+----+
** 2 Ip phones in this list: End of list

downstat i: for IP sets

downstat t: for TDM sets
(1) This tool gives the syntax to use in order to get information about customization and localization

264
Checking of the binary release
downstat i (cont.)
| TSCIP that have to be downloaded

| These sets will be download automatically at back in service step
+--------+--------------+--------------------+-+-----+---------------+----+
| QMCDU | Name | Mac Address | |Neqt | Ip Address |Type|
+--------+--------------+--------------------+-+-----+---------------+----+
|32002 |32002 |00:80:9f:3b:0c:e1 |-|01496|000.000.000.000|Intg|
+--------+--------------+--------------------+-+-----+---------------+----+
** 1 Ip phones in this list: End of list
Press ENTER to quit the tool


265
Checking of the customization and localization releases
getnoeversion d 32000
getnoeversion started 2000-08-14 at 04:51:22
+---------------------------------------------------------------------------------------------------------------+
| dir numb | in | typ term | dom | serial number | hardware version | code vers | data vers |rom |ram |
+---------------------------------------------------------------------------------------------------------------+
| 32000 | OK | 4068(NOE_D_IP) | 0 | H0400427118856 | 3GV23014ADCA080433 | 3.60.20 | 03.60.20 | 8 | 8 |
+---------------------------------------------------------------------------------------------------------------+
| No AOM detected - No bluetooth detected. |
| CUSTOMIZATION: File name: cust-default-40x8 Version: 1.01.00 |
| LOCALIZATION: File name: jpn-4068 Version: 1.00.00 |
+---------------------------------------------------------------------------------------------------------------+
getnoeversion ended 2000-08-14 at 04:51:22
getnoeversion d 32001
32001 isn't in service !!


266
Saving the result in an xml or csv file
getnoeversion all xml

100% achieved ..
getnoeversion ... 1 extensions retrieved out of 1 configured in
management.
getnoeversion ... inventory file path is /DHS3dyn/mao/getnoeversion.xml.Z
getnoeversion all csv

100% achieved ..
getnoeversion ... 1 extensions retrieved out of 1 configured in
management.
getnoeversion ... inventory file path is /DHS3dyn/mao/getnoeversion.csv.Z

The first syntax saves the results in xml format in a compressed file: /DHS3dyn/mao/getnoeversion.xml.Z
The second syntax saves the results in csv format in a compressed file: /DHS3dyn/mao/getnoeversion.csv.Z

267
Xml information
getnoeversion.xml
<liste>
<extension>
<directoryNumber>32000 </directoryNumber>
<in-outOfService>OK</in-outOfService>
<typeTerm>4068(NOE_D_IP)</typeTerm>
<domIP> 0</domIP>
<serialNumber>H0400427118856</serialNumber>
<hardwareVersion>3GV23014ADCA080433</hardwareVersion>
<softwareVersion>3.60.20</softwareVersion>
<dataVersion>03.60.20</dataVersion>
<romSize> 8</romSize>
<ramSize> 8</ramSize>
<custName>cust-default-40x03.60.20</custName>
<custVersion>1.01.00</custVersion>
<locnName>jpn-4068</locnName>
<locnVersion>1.00.00</locnVersion>
<aomDevice1>No AOM </aomDevice1>
<bluetoothDevice1>No bluetooth detected</bluetoothDevice1>
<bluetoothDevice2></bluetoothDevice2>
</extension>
</liste>

This file is extracted from the compressed file /DHS3dyn/mao/getnoeversion.xml.Z

268
Xml informations
getnoeversion.csv
dir numb in typ term dom serial number hardw version softw version data version rom size ram size cust name cust version locn name locn version
32001 OK 4038(NOE_C_IP) 0 H0400428225414 3GV23014ACDA020440 3.60.20 03.60.20 8 8 cust-default-40x03.60.20 1.01.00 kor-40x8 1.00.00
This file is extracted from the compressed file

/DHS3dyn/mao/getnoeversion.csv.Z


269
Initialization after customization changes
1 Lanpbx.cfg
2 cust-default-40x8
3 Lanpbx.cfg
4 startnoe
5 Signaling + Keep alive

1) The IP touch 4068 requests the lanpbx.cfg to the CS

2) The set requests the file that contain the specific melodies
3) The IP touch 4068 requests again the lanpbx.cfg to the CS
4) The IP touch 4068 requests the startnoe to the CS
5) The signaling link is established and the keep alive start

270
Initialization after languages changes
1 Lanpbx.cfg
2 kor-4068
3 Lanpbx.cfg
4 startnoe
5 Signaling + Keep alive

1) The IP touch 4068 requests the lanpbx.cfg to the CS

2) According to the language selected, the set request the language file that contain the specific font
3) The IP touch 4068 requests again the lanpbx.cfg to the CS
4) The IP touch 4068 requests the startnoe to the CS
5) The signaling link is established and the keep alive start

271

272
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

273
User management

274
User management
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to bring into service IP-Phone and IP Touch X8 series
MANAGEMENT
1. Connect the e-Reflexes and 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 dynamic mode for the e-Reflexes stations and 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

275
User management

276
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
277
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
278
Plugwares for Reflexes sets

OBJECTIVE:
◆ To describe plugwares for Reflexes sets
Alcatel OmniPCX Enterprise - Plugwares for Reflexes

279
Overview
4 types of plugwares for Reflexes sets
➨ Connected behind a set of the Reflexes range or not (used

alone, directly connected on the UA link) *
➨ On the Advanced & premium sets, the plugware is

integrated inside the set itself, not for the others

* If you use the plugware alone, you need to change the position of one jumper(see technical documentation for more information)

280
4091 : TSC-
TSC-CTI
Allows to connect a PC behind a set (CTI link)
➨ Used for calls management and supervision
Set
UA link CTI link


281
4093 : TSC-
TSC-V24/CTI
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 Lien V24


282
4094 : TSC-
TSC-S0
Allows to connect a S0 bus (2B+D)
➨ Used to connect S0 sets (TTN2 Alcatel) or all the S0

equipments (Fax, PC equipped with a S0 interface, …)
Set
Power supply
UA link S0 link

Power supply of 48v

283
4095 : TSC-
TSC-AP
Allows to connect analog terminal
➨ Used to connect analog sets, fax, modem,…
Set
Power supply
UA link Analog link

Power supply of 30v

284
Z and S0 plugware
PROCEDURE
Z and S0 plugware
OBJECTIVE
- To learn how to manage S0 and Z plugware
MANAGEMENT
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

Communication et reproduction interdites sans autorisation préalable écrite. La mention document
"Alcatel Business Systems" doit obligatoirement figurer en cas de reproduction autorisée.
285
Z and S0 plugware
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
➥ Set type + S0 set
➥ Entity number: 1

286
Z and S0 plugware
3. S0 plugware without UA set

Note: You have to move a internal switch in order to use the plugware without set.
3.1 Create TA
Path Shelf / board/ TA adapter
Action Create
➥ 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
➥ Protocol type + ETSI
➥ long passive bus + no
3.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
➥ Set type + S0 set
➥ Entity number: 1

287
Z and S0 plugware
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 an 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)

288
Z and S0 plugware
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.

289
Z and S0 plugware

290
Plugware
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to set up the AP plugware
MANAGEMENT
Analog plugware
1. Install AP plugware between a 4035 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.

291
UA Plugware

292
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
293
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
294
PARTICIPANT'S GUIDE
Part 2/3
REF. ENTPTE401US
System Configuration TOC.doc
01 03/06
GENERAL SUMMARY
Part 2
8. Trunk groups
ENTP0409P01TEUS.............................................................................................................295
ENTP0409C02TEUS ............................................................................................................301
ENTP0409C03TEUS ............................................................................................................305
ENTP0409C05TEUS ............................................................................................................311
ENTP0409C07TEUS ............................................................................................................317
ENTP0409M01TEUS............................................................................................................325
ENTP0409M02TEUS............................................................................................................331
ENTP0409H01TEUS ............................................................................................................333
9. System synchronization
ENTP0437P01TEUS.............................................................................................................337
ENTP0437H01TEUS ............................................................................................................343
10. Automatic Callback on Busy Trunk Group

ENTP0481P01TEUS.............................................................................................................347
ENTP0481C01TEUS ............................................................................................................355
ENTP0481M01TEUS............................................................................................................359
ENTP0481H01TEUS ............................................................................................................363

TOC.doc System Configuration
11. DID Translator

ENTP0424P01TEUS.............................................................................................................367
ENTP0424C01TEUS ............................................................................................................375
ENTP0424H01TEUS ............................................................................................................381
12. External Callback Translator

ENTP0427P01TEUS.............................................................................................................385
ENTP0427C02TEUS ............................................................................................................389
ENTP0427H01TEUS ............................................................................................................391
13. Classes of services

ENTP0404P06TEUS.............................................................................................................395
ENTP0404C02TEUS ............................................................................................................403
ENTP0404H02TEUS ............................................................................................................413
14. Groups
ENTP0405P03TEUS.............................................................................................................417
ENTP0405C03TEUS ............................................................................................................429
ENTP0405C04TEUS ............................................................................................................431
ENTP0405M01TEUS............................................................................................................437
ENTP0405H02TEUS ............................................................................................................443
15. Multiline sets

ENTP0406P02TEUS.............................................................................................................447
ENTP0406C02TEUS ............................................................................................................457
ENTP0406C04TEUS ............................................................................................................463
ENTP0406H02TEUS ............................................................................................................469
16. Assistant / Manager groups

ENTP0407P01TEUS.............................................................................................................473
ENTP0407C02TEUS ............................................................................................................483
ENTP0407M01TEUS............................................................................................................493
ENTP0407H01TEUS ............................................................................................................497
17. External Calls Barring

ENTP0426P01TEUS.............................................................................................................501
ENTP0426C02TEUS ............................................................................................................517
ENTP0426M01TEUS............................................................................................................531
ENTP0426H01TEUS ............................................................................................................535
18. Automatic Route Selection (ARS)

ENTP0425P01TEUS.............................................................................................................539
ENTP0425C02TEUS ............................................................................................................551
ENTP0425M01TEUS............................................................................................................559
ENTP0425H01TEUS ............................................................................................................563

19. Attendants
ENTP0416P02TEUS.............................................................................................................567
ENTP0415P03TEUS.............................................................................................................575
ENTP0415P02TEUS.............................................................................................................595
ENTP0416C01TEUS ............................................................................................................609
ENTP0415C02TEUS ............................................................................................................617
ENTP0416M01TEUS............................................................................................................625
ENTP0415M01TEUS............................................................................................................627
ENTP0415H03TEUS ............................................................................................................629

Part 3

ENTP0418P01TEUS.............................................................................................................633
ENTP0418P02TEUS.............................................................................................................649
ENTP0418C01TEUS ............................................................................................................665
ENTP0418M01TEUS............................................................................................................677
ENTP0418H01TEUS ............................................................................................................681
21. DECT
ENTP0419P01TEUS.............................................................................................................685
ENTP0419P04TEUS.............................................................................................................693
ENTP0419C01TEUS ............................................................................................................699
ENTP0419C03TEUS ............................................................................................................703
ENTP0419C04TEUS ............................................................................................................707
ENTP0419M01TEUS............................................................................................................715
ENTP0419H02TEUS ............................................................................................................731
22. Twinset
ENTP0479P01TEUS.............................................................................................................735
ENTP0479C02TEUS ............................................................................................................745
ENTP0479H01TEUS ............................................................................................................749
23. Speed Dialing

ENTP0408P01TEUS.............................................................................................................753
ENTP0408C02TEUS ............................................................................................................761
ENTP0408H01TEUS ............................................................................................................765

ENTP0480P02TEUS.............................................................................................................769
ENTP0480C02TEUS ............................................................................................................787
ENTP0480H02TEUS ............................................................................................................797
25. Alcatel 4645

ENTP0432P01TEUS.............................................................................................................801
ENTP0432C01TEUS ............................................................................................................819
ENTP0432C02TEUS ............................................................................................................833
ENTP0432M01TEUS............................................................................................................837
ENTP0432H01TEUS ............................................................................................................845

26. MOXA V24/IP Box

ENTP0444P01TEUS.............................................................................................................849
ENTP0444C01TEUS ............................................................................................................857
ENTP0444M01TEUS............................................................................................................863
ENTP0444H01TEUS ............................................................................................................875

ENTP0411P04TEUS.............................................................................................................879
ENTP0411C02TEUS ............................................................................................................883
ENTP0411H02TEUS ............................................................................................................889

ENTP0431P01TEUS.............................................................................................................893
ENTP0431P06TEUS.............................................................................................................903
ENTP0431P07TEUS.............................................................................................................915
ENTP0431P08TEUS.............................................................................................................925
ENTP0421P01TEUS.............................................................................................................931
ENTP0431C06TEUS ............................................................................................................939
ENTP0431C08TEUS ............................................................................................................951
ENTP0431H08TEUS ............................................................................................................957


FEEDBACK SHEET
Alcatel University
CS 82802
FAX: (33) 2 98 14 36 36
DATE:


Trunk groups

OBJECTIVE:
◆ To describe trunk groups
Alcatel OmniPCX Enterprise – Trunk groups

295
Trunk groups
overview
Connection with an operator
digital
ISDN T2 / T0
Operator
BCA
Analog


296
Trunk groups
overview
Connection with non Alcatel PABX
ATL, QSIG Digital
ATL, BCA
Analog


297
Trunk groups
overview
Connection to an Alcatel PABX
ABC_F digital
ATL, BCA Analog


298
Trunk groups
overview
Main characteristics
Trunk group number
Seize prefix
Trunk group type
ressources


299
Trunk groups
overview
Trunk category
What’s your name?
Comment t’appelles tu?
➨ Contains the data concerning the communications protocol

used.


300
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.

301
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

302
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
Trunk Group
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

303
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
4. Maintenance
On the call server
Login mtcl
Command trkstat 10
Result T R U N K S T A T E Trunk group number : 10
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
Result Numb Name Type Var. Node Pfx
TG 10 Analog BCA 1 => local 10
Remark: for more details, use the command trkstat + Trung Group
Number (eg: trksat 10)

304
ISDN T0 trunk groups
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.

305
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
|----|-----|--------------|-----------------------|--------------------|
| 1 | 0 | GD | IN SERVICE| NO OPS FILE |
| 1 | 2 | PRA T1 | IN SERVICE| NO OPS FILE |
+----------------------------------------------------------------------+

306
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)
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.

307
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
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).
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
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

308
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)
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)
1.7 Reset the board in order to initialize the trunk group

On the call server
Login mtcl
Command rstcpl 1 3 (1= shelf address, 3= board address)

309
1.8 Check the status of the trunk lines

On the call server Tab
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.

310
PROCEDURE
OBJECTIVE
- To learn how to create ISDN T2 trunk groups with mgr
OVERVIEW

311
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
+-------------------------------------------------------------------------+
Result
|----|-----|--------------|--------------------------|--------------------|
+-------------------------------------------------------------------------+

312
1.2 In case of PRA E1 boards: create a T2 trunk group

On mgr
Select Trunk groups
Action Create
Trunk Group Type: T2
Trunk Group Name: (for example: T2-1)
Tone on seizure: (For example: True)
Remark:
Q931 Signal variant
trunk group:
DID Transcoding

313

On mgr
Select Trunk groups
Trunk group
Remark:

On mgr
Select Trunk groups
Trunk group
T2/T1/T0 access
Action Create
Access type: T2
Remark:
Physical Address:
Time Slots:

314

On mgr
Select Shelf
Digital access
On mgr
Select Translator
Prefix plan
Action Create

On the call server
Login mtcl

315

Login mtcl
+============================================================================+
Result
| T R U N K S T A T E Trunk group number : 2 |
| Trunk group name : dev4-dev1 |
| Number of Trunks : 30 |
+----------------------------------------------------------------------------+
| Index : 1 2 3 4 5 6 7 8 9 10 11 12 13 |
| State : F F F F F F F F F F F F F |
+----------------------------------------------------------------------------+
| Index : 14 15 16 17 18 19 20 21 22 23 24 25 26 |
| State : F F F F F F F F F F F F F |
+----------------------------------------------------------------------------+
| Index : 27 28 29 30 |
| State : F F F F |
+----------------------------------------------------------------------------+
| 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 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.

316
T1 trunk groups
PROCEDURE
T1 trunk groups
OBJECTIVE
- To learn how to create ISDN T1 CSS trunk groups with mgr
OVERVIEW

317
T1 trunk groups
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
+----------------------------------------------------------------------+
Result | Cr | cpl | cpl type | coupler state | coupler ID |
|----|-----|--------------|--------------------------|-----------------|
+----------------------------------------------------------------------+

318
T1 trunk groups
1.2 In case of PRA T1 boards: create a T1 trunk group

On mgr
Select Trunk groups
Action Create
Trunk Group Type: T1CCS
Trunk Group Name: (for example: T1CCS-1)
Tone on seizure: (for example: True)
Carrier ID: AT&T
Auto. DTMF dialing on outgoing call: YES
Remark:
Q931 Signal variant:
trunk group:
DID Transcoding:

319
T1 trunk groups

On mgr
Select Trunk groups
Trunk group
DTO joining: True
Remark:

320
T1 trunk groups

On mgr
Select Trunk groups
Trunk group
T2/T1/T0 access
Action Create
Access type: T1 CCS
Remark:
Physical Address:
Time Slots:

On mgr
Select Shelf
Digital access
Used access: Yes
Multiframe type: ESF AT&T TR54016
Line type: Short Haul 0 to 45 meters
Pulses encoding: B8ZS

321
T1 trunk groups
On mgr
Select Translator
Prefix plan
Action Create

On the call server
Login mtcl

322
T1 trunk groups

On the call server
Login mtcl
+-------------------------------------------------------------------+
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 |
|-------------------------------------------------------------------|
| | 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.

323
T1 trunk groups

324
Trunk groups

OBJECTIVE:
◆ Use the maintenance tool to check the trunk group status
Alcatel OmniPCX Enterprise – Trunk Groups

325
Trunk Group maintenance
To access to the maintenance Web Tool, the URL used

is:http or https://IP@ of the Call Server
main/wtool/html/tools.html
➨ The account used to access to the tool is: mtcl


326
Main menu

the system
release etc..


327
Trunk Group maintenance menu
For trunk group maintenance select « Trunk group status »

in the menu.
➨ It is possible to select one trunk group by clicking in the
« Location » column on the line of the trunk group to
visualize.

The information « Type » corresponds to the trunk group type:

Trunk group 10 -> Type T0
Trunk group 12 -> Type T2
The prefix seize of the trunk group corresponds to the information« Prefix »
#010 for the trunk group 10
#012 for the trunk group 12

328
Trunk group example

➨ In this example the trunk group has 30 B channels.
▼ Channel 1 to 15 and 17 to31
▼ Channel 16 is reserved for signaling
➨ 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.


329
Example of trunk group out of service

➨ 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


330
Trunk groups

OBJECTIVE:
◆ To manage the trunk groups

331
Trunk group
Maintenance
Information about the trunk groups status
-r: optional parameter used

-r: optional parameter used
to refresh the screen
to refresh the screen
➨ trkstat (-r) <trunk group n°>
Indicate the board's position where is the access

Indicate the board's position where is the access
➨ trkstat (-r) <Media Gateway> <board>

-r to refreshment

332
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 trunk group (without DDI translation)

Index T0: X0
Index T2: 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 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.

333
Trunk groups

334
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
335
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
336
System synchronization

OBJECTIVES:
◆ To describe synchronization principles
◆ To describe the principles of the synchronization per domain
Alcatel OmniPCX Enterprise – System synchronization

337
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 a 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

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.

338
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

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.

339
TDM Architecture (Crystal)
Example: TDM Architecture
Alcatel OmniPCX ACT 2

Enterprise INTOF link
Sy RT2 link
Call Server
ro nc
ch hr
i or 2
0
Syn o
Pr 2 N°
i ty
ACT
0
T
T2 N ACT 3
Prio °1
rity
0 T0
Carrier ty 5
Priori
Sy
nc
hr
INTOF link
o
ACT 1
Domain 0

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.

340
IP Architecture (Media-
(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)

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).

341
Architecture IP (Media-
(Media-Gateway & Crystal)
Example: IP architecture
Domain 2
Domain 0
Alcatel OmniPCX
Enterprise ACT 2
Call Server
0
i t y °2
20
Pr T 2 N
Domain 3
i or
T2 N ACT 3
Prio °1
rity
0 T0 05
2
Carrier r iority
P ACT 4
Independent
ACT 1
IP network

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.

342
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.

343
Synchronization

344
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
345
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
346
Automatic Callback on Busy Trunk

OBJECTIVE:
◆ To describe the feature “Automatic Callback on Busy Trunk”
Alcatel OmniPCX Enterprise – Automatic Callback on Busy Trunk

347
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) system

compatible with the overlapping dialing

(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)

348
Functioning mode
The automatic Callback on Busy trunk is made of two

main steps
➨ The callback registration
➨ And the execution
Topology example
Faisceau
Public carrier


349
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 it has the right(2)
The user is notified of this possibility with the voice guide

n°8 (3) and with a dynamic key (only available with 4035
type of set)
If the user uses the associated suffix (or the dynamic key)
the “Automatic Callback on Busy Trunk Group” will be
recorded
The voice guide n° 3 (4) notifies the user that the callback
is registered

(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”

350
“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 n°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

(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

351
Restrictions
Feature unavailable 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


352
Miscellaneous
If several callback demands are associated to the same

trunk group, they are treated in the order of registration
When a coupler (1) is reset, 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

(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)

353

354

OBJECTIVE:
◆ To configure the system to provide the “Automatic Callback on Busy Trunk”

355
/Classes of Service/ Phone Features Classes of Service
➨ Review/Modify
▼ Callback on free or busy set: 1 (default value)

▼ Auto. Call back satell. Trk grp: 0 or 1 (1)
/Trunk groups
➨ Review/Modify
▼ Overlap dialing + YES (default value)

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 satell. Trk grp: 1 The Automatic Callback on Busy Trunk is proposed by the phone
Auto. Call back satell. Trk grp: 0 The Automatic Callback on Busy Trunk is not proposed by the phone

356
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 Callback1
➨ /Translator/Suffix plan
▼ Create
✦ Number: 5 (according the VG)
✦ Suffix meaning: Callback on free or busy set

1 – VG used for the Automatic Callback is: “You may request automatic callback by dialing 5 ….. ” (for instance)

357

358

OBJECTIVE:
◆ To maintain the “Automatic Callback on Busy Trunk” feature

359
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 |

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

360
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_

Other available options of the « callbstat » command

n neqt
z idx1 idx2 (idx = callback area index)
all

361
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

(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

362
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 test the automatic call
back.

363
Automatic call back on busy trunk group

364
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
365
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
366
DID translator

OBJECTIVE:
◆ To describe the principles of the DID translation for incoming and outgoing calls
Alcatel OmniPCX Enterprise – DID translator

367
DID 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

Public Operator
▼ Installation number
▼ DID range
➨ Between them: the transcoding

▼ Management:
✦ identification of the external ranges of numbers (DID numbers)
✦ Identification of the internal ranges of numbers (directory numbers)
✦ Establishment of the link between those ranges


368
DID translator
Transcoding needs
The transcoding has to be managed systematically for

different reasons:
➨ DID numbers equivalent to the internal directory numbers:

▼ The system has to know the subscribers which don’t have a DID
number, so as to build up the right ISDN number for an outgoing
call
➨ DID numbers different to the internal directory numbers:

▼ The DID numbers have to be transcoded in internal numbers
✦ Example: DID number ‘2000’ transcoded in internal number ‘6000’
➨ Number of digits different between DID and internal

Suppl.Inst.Nbr.
numbers:
▼ The DID numbers have to be transcoded in internal numbers
✦ Example: DID number ‘2000’ transcoded in internal ‘42000’


369
DID translator
Numbering Plan Descriptor
A NPD (Numbering Plan Descriptor) is used to:
➨ Select the DID translator to use
▼ For outgoing calls

▼ For incoming calls
➨ Determine the identification to send
▼ Entity source
▼ NPD source
▼ Nothing
▼ Personal calling number authorization
The NPD used is managed in the trunk group used to

establish the communication

The trunk group used to establish the call is associated to the NPD (Numbering Plan Descriptor) 14 by default (15 in case you have
DID translation)
Attention, in case of ARS the NPD used is managed in the ARS route

370
Incoming call mechanism
Incoming call mechanism

er
0 u mb
30 dn
Ca 013
lle
Public Operator
14
02
ISDN
Trunk group
Trunk
Trunkgroup
group
User
³³DID transcoding:Yes
DIDtranscoding: Yes
User6000
6000
³³Entity:
³³Nb
Nbofofdigits
digitsunused (ISDN):66
unused(ISDN):
Entity:11
11 ³³Public
PublicNPD
NPDid:id:15
15
NPD
NPD1515
³³Called
CalledDID Translator:00
DIDTranslator:
DID
DIDtranslator
translator00
³³33xx
33xx-->
-->60xx
60xx

A Numbering Plan Descriptor (NPD) is used to translate the received number (incoming call)

371
Outgoing call: DID user
Outgoing call: DID user

t
en
(without ARS and with standard management)
mb
e rs
u
n n 00
a tio 3 Public Operator
13
fic
nti
Ide 40
21
ISDN
Trunk group
Trunk
Trunkgroup
groupseizure
seizureprefix
prefix
route type, private:NO
³³route type, private: NO
User
User6000
6000 Trunk
Trunkgroup
group
Entity:11
³³Entity: 11 ³³DID Transcoding:Yes
DIDTranscoding: Yes
³³Public NPD:15
PublicNPD: 15
Entity
Entity11
11 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
CallingDID id:00
DIDid:
The number “6000” belongs to the range and is DID
DIDtranslator
translator00
transcoded in “3300” ³³33xx
33xx-->
-->60xx
60xx

³ 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 DID’ subscribers for the outgoing call
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 DID subscribers)

372
Outgoing call: none DID user
Outgoing call: none DID user (without ARS and with

standard management)
t
sen
er
mb
nu
n 3
ca
tio 33 Public Operator
n tifi 01 3
Ide 2 14
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: 11 ³³DID Transcoding:Yes
DIDTranscoding: Yes
³³Public NPD:15
PublicNPD: 15
Entity
Entity11
11 NPD
NPD15 15
³³Installation No:21401
InstallationNo: 21401 ³³Installation
Installationnumber source:Entity
numbersource: Entity
³³Supplementary
SupplementaryInstallation No*: 3333
InstallationNo*: 3333 Default number source:Entity
³³Default number source: Entity
³³Calling
CallingDID id:00
DIDid:
DID
DIDtranslator
translator00
The number “6100” does not belong to the range ³ ³³33xx
33xx-->
-->60xx
60xx

³ 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 DID’ subscribers for the outgoing call
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 DID subscribers)

373

374
DID translator
PROCEDURE
DID Translator
OBJECTIVE
- To learn how to configure the DID translator with mgr
OVERVIEW
Create the DID translator by using the mgr application.
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 to 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.
Manage the DID translation DID numbers for the users, groups, attendant sets, DISA, voice mail.

375
DID translator
PROCEDURE
In this example, the external number are 36XXX and the internal number are 34XXX
1. Management of the DID numbers for all the directory numbers

which have to be translated (users, groups, voice mail, and so on)
1.1 Check the internal numbers created for the users, groups, attendant sets, …
On mgr
Select System
Free numbers range list
Action Create
Entry Name: (for example: 1)
Range beginning: 34001
Range end: (for example: 34999)
Digits authorized: 0,1,2,3,4,5,6,7,8,9
Max. number: (for example: 10) (10= max. numbers that you can create
in this range)
1.2 Create as many DID numbers ranges as needed for all the internal numbers
that need one
On mgr
Select Translator
External Dialing plan
Default DID num. translator
Action Create
Entry First external number: (for example: 36001)
First internal number: (for example: 34001)
Range size: (for example: 99)
Unique internal number: No

376
DID translator
Remark:
We have created a range who contain 99 numbers (external numbers: from
3601 until 3699 and internal numbers: from 3401 until 3499)
Example, there are 99 DID numbers.
The internal number 3401 is reachable from outside by dialing
“xxxxxx+3601”
(xxxxxx =company installation number)
“xxxxxx+3602”
“xxxxxx+3699”
And so on…
1.3 Validate the DID translation in the trunk group parameters

On mgr
Select Trunk groups
Entry Trunk group Id.: (for example: 1) (enter the trunk group number)
DID transcoding: True
Remark:
As soon as the DID transcoding is validated in the trunk group parameters, a
specific dialing plan descriptor is assigned to it (see step 2.4)
1.4 Check the Dialing plan descriptor assigned in the trunk group parameters
On mgr
Select Trunk groups
Trunk group NPD selector
Entry Trunk group Id.: (for example: 1) (enter the trunk group number)
Consult Public NPD ID: 3 (remember this number)
Management mode: Automatic
Public DID transcoding: True

377
DID translator
1.5 Check that the DID translator number managed in step 2.2 is assigned in the
Dialing plan descriptor used by the trunk group (step 2.4)
On mgr
Select Translator
External Dialing plan
Dialing plan description (NPD)
Entry Description identifier: (for example: 3) (3= the public NPD Id.)
Consult Called DID identifier: 0 (0=Default DID num. translator)
Calling/connected DID identifier: 0 (0= Default DID num. translator)
Remark:
By default, when the DID transcoding is used, the dialing plan descriptor
uses the default DID translator (number 0).

378
DID translator
1.6 Check the default DID translator management

On the call serverl
Login mtcl
Command didtest
Result 0 : exit
1 : select did
2 : incoming did
3 : outgoing did
4 : view selected did data
5 : exec time
choice :
Entry 1
Result general did or public overflow : [g]/p
Entry g
Result did id : <0..99> :
Entry (for example: 0) (0= the did number)
Result 0 : exit
1 : select did
2 : incoming did
3 : outgoing did
4 : view selected did data
5 : exec time
choice :
Entry 4
Result DID Mode : 0
DID slice 1 :
start ext : 3601
start int : 3401, size 99, unique int. number : NO

379
DID translator

380
DDI translator
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to Manage the default DDI translator
MANAGEMENT
1. Manage the DDI translator according to the file site (or use the configuration given by the
trainer)
2. Test the configuration to check if the stations can be reached from the public network

381
DDI translator

382
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
383
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
384
External callback translator

OBJECTIVE:
◆ To describe the external callback translator
Alcatel OmniPCX Enterprise – External callback translator

385
External Callback Translator
Overview
The external callback translator allows:
➨ display of the caller number of sets with display
➨ consultation on the digital set with display of the list of

unanswered ISDN calls, with a view to call back
➨ call back the number display


386
External Callback Translator
Overview
Display incoming number and external callback

Trunk group seizure prefix: 0
Caller identification:
0298143322
Identification sent by the operator:

298133322
Basic N° Nb of digits to Digits OPERATOR

0298133322 be removed to add
DEF 0 00
A 1 000

To insure the calling identification display, it is necessary to manage the external callback translator.
The system modifies the calling number received from the ISDN before storing it in the system.
Depending on the country and its numbering plan, characters need to be removed from the head of the number.
To allow callback, the o/g seize prefix must be added to the head of the number, followed, where appropriate, by another call area
related prefix.

387
Overview
Callbacks for unanswered external calls

Trunk seizure prefix: 0 Caller’s number:
004122767000
Identity transmitted by carrier:

A4122767000
external callback translator
N° base Digits to Digits

Call 004122767000 16/02/98
delete to add
CARRIER
Callback
DEF 0 00
A 1 000

The carrier number (0=operator by default, 7=CEGETEL...) should not be managed in the entity’s NDI. The carrier only carries over
the 9 digits of the calling subscriber, the external callback translator of the called party installation takes care of added the carrier it
uses.
In fact, the caller and called party don’t necessarily use the same carrier.

388
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

389
PROCEDURE:
1. 1.Manage the external call back translator

On mgr
Select Translator
External dialing plan
External callback translation
Action Create
Entry Basic Number: (for example: DEF)
No. Digits To BE Removed: (for example: 0)
Digits To Add: (for example: 9)
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.

390
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
avec:
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?

391
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.

392
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
393
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
394
Classes of Services

OBJECTIVE:
◆ To describe the features, connection and transfer COS
◆ To set up the routing off-hook
Alcatel OmniPCX Enterprise - Classes of Services

395
Categories
Overview
3 types of classes of service:

➨ Connection
Direct Call
not allowed
➨ Transfer
Transfer
not allowed
Immediate
forward not allowed
➨ Phone facilities


396
Categories
Overview
Connection COS
➨ Allow or not the connection between the equipment inside

the system:
▼ Extension ↔ extension (Internal call)
▼ Extension ↔ trunk (external incoming/outgoing call )
▼ Trunk ↔ Trunk (trunk to trunk connection)


397
Categories
Overview
Connection category
CALL
cat=1 cat=2
called party
0 1 2 3 4 5
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


398
Categories
Overview
Transfer COS
➨ Allow or not the transfer between the equipment
▼ 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

category Id but 2 matrix are manageable


399
Categories
Overview
Transfer category
TRANSFER
cat=1 cat=3 called party

0 1 2 3 4 5
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


400
Categories
Overview
Phone Features COS
➨ Allow or not the use of the phone facilities

▼ example: forward
➨ Protect against some phone facilities

▼ example: barge-in
➨ Define the routing mode on off hook

▼ example: Delayed routing
➨ There are 32 phone Features COS in the system


401
Categories
Overview
Phone facilities categories are classified according to
➨ Rights
➨ Routing mode at off hook
➨ Set features
➨ General services
➨ Local services
➨ External services
➨ Suffixes
➨ Abbreviated dialing areas
➨ Voice mail forwarding
➨ Default overflow type
➨ Default overflow addressee
➨ Quality profile for voice on IP


402
Classes of service
PROCEDURE
Classes of service
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.

403
Classes of service
PROCEDURE
1. Access class of service

On mgr
Select Classes of service
Access COS
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
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

404
Classes of service
1.2 Private Access COS

On mgr
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.
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

405
Classes of service
1.3 Business Access COS

On mgr
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 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

406
Classes of service
1.4 Network Access COS

On mgr
Access COS
Descend hierarchy
Action Press ENTER
Select Network Access COS
All instances
Action Press CTRL+V
Remark:
By default the network access COS 2 is selected, you can change this value.
Action Select one of the 16 networks ID
Select 2 (e.g.)
Action Press ENTER
Entry Network Access Rights
Night: 1 or 0
Day: 1 or 0
Mode1: 1 or 0
Mode2: 1 or 0
Action Press CTRL+V

407
Classes of service
1.5 Trunk Group Access COS

On mgr
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

408
Classes of service
2. Connection class of service

On mgr
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
Transfer COS
All instances
Action Press CTRL+V
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

409
Classes of service
4. Private Calls Connection class of service

On mgr
Private calls connection COS
All instances
Action Press CTRL+V
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

410
Classes of service
5. Phone features Classes of service

On mgr
Phone features class of service
All instances
Action Press CTRL+V
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

411
Classes of service

412
Classes of Service
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage classes of service
- Upon successful completion of this lab, you will be able to:

- Prevent UA sets to call IP Phone set,
- Allow IP Phone set to call UA sets,
- Prevent UA sets to use the immediate forward prefix.
MANAGEMENT
1. Assign User Connection COS

Assign connection COS 1 to the IP Phone (3x100).
Assign connection COS 2 to the UA sets (3x110, 3x200).
2. Connection COS
Set up the programming to declare connection COS 2 incompatible with connection COS 1
Set up the programming to declare connection COS 1 compatible with connection COS 2
3. Tests
Set up a call from user 3x100 to user 3x110. What happens and why?
Set up a call from user 3x110 to user 3x100. What happens and why?
Assign user Telephone Features COS
This lab uses 2 prefixes for the immediate forward and for the forward cancellation. Check the
presence of these prefixes, create them if it is not already done.
Assign telephone features COS ID number 3 to the UA sets (3x110, 3x210), do not modify
other users.
4. Telephone Features COS

For the Telephone Features COS number 3, forbid the immediate forward.

413
Classes of Service
5. Tests
Dial the immediate forwarding prefix on the user 3x100. Does it work?
Dial the immediate forwarding prefix on the user 3X110. Does it work?
Note: Set the connection and phone features COS back to 0 for the users so that they will not
conflict with future labs.

414
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
415
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
416
Groups

OBJECTIVES:
◆ To describe pick up groups
◆ To describe hunt groups
Alcatel OmniPCX Enterprise -Groups

417
Group
Overview
Two types of Group
➨ Pick-up Group
➨ Hunt Group (PCX)


418
Pick-
Pick-up group
Overview
Call pick-up enables a user to answer an incoming call to

another set on his own set by dialing a prefix
1 CALL
conversation
3
2
Pick-up prefix

There are two types of call pick-up: direct call pick-up and group call pick-up.
For direct call pick-up, you must enter the prefix of the routed call, 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.
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 users.
Group call pick-up enables a 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 (you don't need to dial the set number).

419
Hunt Group
Overview
A hunt group combines 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 types
➨ Sequential
➨ Circular
➨ Parallel


420
Hunt Group
Overview
Sequential hunt
➨ The call always rings the extension at the head of the group:
the first one free is rung
Circular hunt
➨ Each extension is rung in the order on the list: the system
rings the next free extension after the one previously called
Parallel hunt
➨ The extensions in the group are rung simultaneously
➨ The extensions in the group can not be multi-line extensions

Each extension is rung in the order in the list assigned to the group: the first is number N.
The system rings the next free extension after the one previously called.

421
Hunt Group
Overview
Functionalities
➨ Number of allowed waiting calls

▼ % on number of active sets in the hunt group
➨ Internal group pick-up
➨ Right to pick up private call : y/n
allowance to pick up a private call
✦ Prefix «agent processing group call pick up»
private
call
call pick up
PS: only available in network mode

Number of allowed waiting calls.

- An incoming call waiting on the Hunt 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 sets in the Hunt 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 Hunt 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, we can not pick up
this call with that prefix.
Agent processing group call pick up: only for Hunt group sets
In a Hunt group, when an extension rings, whatever the type of the call (private or Hunt group call), we can pick up this call from an
other extension (belonging in the same Hunt group) using the “Agent processing group call pick up” prefix.
Remarks:Prefix creation: general features / agent processing group call pick up
Service to validate: Tel. features COS

422
Hunt Group
Overview
Functionalities
➨ Call pick up by external : y/n

allowance to pick up a Hunt group call from an external set
of the group
✦ «Direct call pick up» prefix + Hunt group directory nb
Hunt group call
Call pick up

- Call pick up by external: used by extension external to the hunt group.

423
Hunt Group
Overview
Distribution of internal calls
internal
calls
Group directory N°
overflow N° if
Group empty yes
supported, otherwise
call not possible
no
Queue full overflow N° if
Extensions free no yes supported, otherwise
call not possible
yes no
Extensions ring
Hold/call back possible
by caller action

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 (for
cyclical or sequential hunt).
The queue is defined as a percentage of the number of extensions in the group
eg: Group of six extensions with 100 % queue
no extensions withdrawn -> number of calls waiting= 6
two extensions withdrawn -> number of calls waiting = 4
The group overflow N° can be a user, group or operator number.

424
Hunt Group
Overview
Distribution of external calls
external
call
Group directory N°
yes overflow N° if supported,

Group empty otherwise distributed according
to entity’s CDT
no
yes
no Queue full
Extensions free
yes no
Extensions ring then overflow to Ringing tone then overflow to

the entity’s CDT after trunk the entity’s CDT after trunk
overflow timer overflow timer

If there is no answer from a free extension, the call is routed to another extension in the group when the rotation timer expires (for
circular or sequential hunt).
If no phone 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 category 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

425
Hunt Group
Overview
Functionalities
➨ Exit the group by dialing a code
➨ Enter the group by dialing a code
➨ Forbid the last extension to leave the group
➨ Time out pause between 2 calls
➨ Group overflow destination
➨ Number of allowed waiting calls
▼ % of the number of active sets in the hunt group
Group class of service

➨ Connection COS
▼ Used to define user's calling rights to the group
➨ Public network COS
▼ Assigned to extensions when they are in the group
▼ If they leave the group, the extensions retrieve their own COS

Leave or join a group:

- A user can join the hunt group by dialing a prefix or can temporarily leave the hunt group by dialing a prefix.
WARNING:
When a set is in the hunt group, this set uses the hunt group parameters:
- the access COS
- the connection COS
- the entity
When a set is out of the hunt group, this set uses its own parameters
Last extension inhibited to leave the group:

The last set in the group can only leave the group if the facility has been programmed for the hunt group. In that case, calls are
diverted to the overflow directory number.
Manageable pause between calls
It is possible to set by management a pause between two calls for a hunt group members. A set belonging to a group has an idle
time between two calls (pre-set by management). After hooking on an idle time starts before next call. (Call distribution delay)
Group overflow
- Overflow is possible on a directory number. This directory number can be a set, a hunt group, an attendant console, a voice mail
- Overflow is effective if the two following conditions are met:
-The number of authorized waiting calls has been reached.
-All the sets have left the group or are in miscall situation.

426
Hunt Group
Overview
Multiline set in a PBX
➨ Only for sequential and circular groups
➨ Two possible options:
▼ The extension is considered busy if at least one line is busy:

✦ ex: if a multi-line set is busy then a hunt group call overflows to the next
free extension
▼ The extension is considered busy if all its lines are busy

✦ ex: if a multi-line set is busy then a hunt group call appears on a free
multi-line key on this extension and not on the following one.

Multi-line in hunt group

- In case of partially busy set (in conversation: at least one line is free) two modes are possible according to MAO management:
-First mode: the hunt group call will be presented on the set without overflow possibility.
-Second mode: the hunt group call won't be presented on this set, it is considered as a monoline set in busy state.
If all sets of the group are busy, the call will be presented nonetheless on the free line of the set.
- Each line of a set (with group number) is seen as a set for the call distribution. This means that all the free lines of a set may be rung
(after timer) before diversion to another set. In the same way if the first line of the set is busy the second line which is free may be
rung.

427
Hunt Group
Overview
Limits and restrictions
➨ 200 hunt groups per nodes
➨ 40 extensions in an hunt group (analog or digital)
➨ 5 PWT sets in a parallel group
➨ A set can not belong to several hunt groups
➨ No multi-line set in a parallel group


428
Call pick-up group management
PROCEDURE
Call pick up group management
OBJECTIVE
- To learn how to create a pick-up group with mgr
REFERENCE
- System Documentation CD-ROM: R6.X System Documentation
OVERVIEW
The Call Pick-up group is a group of phone sets that are authorized to pick up calls to one of the
group’s phone set, via a prefix number, when it is ringing.
In this lab you will create a prefix, which allows for a set to answer the call by dialing this prefix.
Protect a set against individual (direct call) pick up.
Issue 01 REF.ENTP0405C03TEUS 1
429
Call pick-up group management (MGR)
PROCEDURE
Note: A subscriber can only belong to one pickup group.
1. Create a prefix for call pickup within pickup group

You will install a NTP server on a PC in order to synchronize the call server.
On mgr
Select Translator
Prefix Plan
Action Create
Entry Create: Prefix Plan
Number: 60 (e.g.)
Prefix Meaning: General Features
General Features + Group call pickup
Press CTRL+C as many times as needed to come back on the main menu
2. Assign users to a call pickup group

On mgr
Select Users
Entry Review/Modify: Users
Directory Number : 31000 (e.g.)
Pickup Group Name : PGK1
3. Test procedure for group call pickup

On set
Action From the user 3X000, call 3X001
From 3X100, dial the group call pickup prefix
Verify the results
2 REF. ENTP0405C03TEUS.doc Issue 01

430
Hunt groups management
PROCEDURE
OBJECTIVE
- To learn how to manage a hunt group with mgr
REFERENCE
OVERVIEW
A Hunt group is a method to assign the same directory number to more than one phone set. 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).
Authorize some users to be able to enter and to exit the hunting group.
Set an analog extension as an overflow extension for the group (if all sets in the group are busy).

431
PROCEDURE:
Note: One user can belong to only one hunt group.
1. Create a hunt group with cyclical search mode and assign users to
this Hunt Group
On mgr
Select Group
Hunt group
Action Create
Entry Directory Number : 35000 (e.g.)
Directory Name : Cyclic Group
Type of Hunt Group + PCX Hunt Group
Circular Search Type + Circular
Overflow Directory Number : 31020 (e.g.)
Dir.No Assigned to the group : 31002 (e.g)
Remark:
Type of Hunt Group:
Defines the type of Hunt Group (Local Hunt Group/Network Hunt
Group/RSVP Hunt Group)
Search Type:
When a station group is called, the search of the station to be rung is of type:
circular or sequential or parallel
circular: each station is rung in the order given in the list; the system rings the
free station which follows the station previously called.
sequential: the search is made from the station at the head of the hunt group
(the first found to be free rings).
parallel: a parallel grouping enables several sets to be rung simultaneously
using just one number (the sets cannot be multiline in a parallel group).
If a call is sent to an empty hunt group or a busy group with a full waiting
queue, the call is routed to the overflow directory number, if one has been
defined.
The overflow number may be a local user set, a network user set, another hunt
group, an attendant set.
% authorized camp on calls = (MAX. NUMBER OF CAMP ON CALLS
AUTHORIZED / NUMBER OF ACTIVE STATIONS IN THE HUNTING GROUP) X
100

432
2. Display content of group

On the call server
Login mtcl
Command pbxstat d 35000 (e.g)
Result Usage: pbxstat [-w][d numan][n nu_group][all][sets][menu]
-w ->To display the waiting queue-not relevant for S0 PBX
numan -> Directory number of the Hunting Group
nu_group -> Hunting Group number
all -> To dump all the declared groups
sets -> Display all the sets of the node in a group
menu -> Open a menu to manage groups
** mcduapp 35000 Num Group 0 pbx_type PBX_LOCAL **
nu_tete 1 mcdu de tete : 31002
max_att 50%
idx_acc 255
modcycle CYCLIC
traiatt 0 debor 1
autoret 1 pooccgrp 0 grp_prio 0 abca_blf 0
nbppgr 1 nbpoeff 1 idx_rasgo 0
grcatptt 2 grctconx 0 set_categ 0 entity_nr 1
idx_mevo 255
mcdudeb 31020
station_grp_name tutu0
PBX_RoutingFlag 0
pickup_no_pbx 0
etat_groupe ABCA_SG_FREE
PBX_preemptable 0
tab_pres[1..40]
nelgr: 18 in :31002 etat_poste ABCA_IDLE
tab_pres[1..40]
nelgr: 18 in :31002 etat_poste ABCA_IDLE

433
3. Monitor the state of all the groups on a node and the state of the
sets in a group
On the call server
Login mtcl
Command supgpbx
Result Hunting group supervisor - xa000001
1: Group's sets state
2: State of all the hunting groups of the node
3: Group statistics
4: Help
5: Options
q: Quit the hunting group supervisor
4. Create the prefix to enter in the Hunt Group:

On mgr
Select Translator
Prefix plan
Action Create
Entry Number : 10 (e.g.)
Prefix Meaning + Set features
Station Features + Sta. group entry
Action CTRL+V or F1 to validate the creation
CTRL+C as many times as needed to come back on the main menu
5. Create the prefix to exit the Hunt Group

On mgr
Select Translator
Prefix plan
Action Create
Entry Number: 11 (e.g.)
Prefix Meaning + Set features
Station Features + Sta. group exit

434
6. Allow users 3X000 and 3X001 to enter and exit the group
On mgr
Select users
Entry Directory Number : 31002 (e.g.)
Tel. Features COS ID : 0
Remark:
By default, all Tel. Features COS allow for entering and exiting of a group.
If you want to check it, follow this path
Classes of Service/Phone Features Classes of Service/Review-Modify/CTRL V or
F1/CTRL F ( 3 times)/
Sta. group exit: 1
Sta. group entry: 1
This attribute, validated at 1, enables a set to return or exit to its group
Action Press CTRL+V or F1 to validate your choice

435

436
Groups

OBJECTIVES:
◆ To maintain pick up group
◆ To maintain hunt group
Alcatel OmniPCX Enterprise Maintenance – Groups

437
Pick up groups
Maintenance
Commands
➨ zdpost
▼ find the identity of the group (pickup_id)
➨ edsbr
▼ find the extension's and the group's identity
➨ listrad
▼ find the prefix


438
Hunt Group
Maintenance
Commands
➨ pbxstat
▼ to display static data about a hunting group
➨ supgpbx
▼ to display dynamic data about a hunting group

TIMERS : - timer 36 : rotating time within a group ( 25s by default )

- timer 31 : idle timer between two hunting group calls if validated in management ( 1s by default )

439
Hunt groups
Maintenance
pbxstat
➨ Syntax: [-f][d dirnum][n nu_group][all]
(3)xa00003> pbxstat -f d 33555

***** mcduapp 33555 Num Group 1 GPBX *****
nu_tete 1 mcdu de tete : 33010
max_att 50%
idx_acc 255
modcycle PARAL
traiatt 0 debor 0
autoret 1 pooccgrp 0 grp_prio 0 abca_blf 0
nbppgr 4 nbpoeff 4 idx_rasgo 0
mcdudeb
grcatptt 0 grctconx 0 entity_nr 1
etat_groupe ABCA_SG_FREE
tab_pres[1..40]
nelgr 0 in : 33010
nelgr 3 in : 33013
nelgr 2 in : 33012
nelgr 1 in : 33011
Waiting queue empty

[-f] Details
[d numan] PBX directory number
[n nu_group] PBX logical number
[all] All PBXs
etat_groupe ABCA_SG : _FREE all extensions are free

_TOT_BUSY all extensions are busy
_PART_FREE some extensions are free

440
Hunt groups
Maintenance
Supgpbx
3)xa00003> supgpbx
Hunting group supervisor - xa001001
1: Group's sets state

2: State of all the hunting groups of the node
3: Group statistics
4: Help
5: Options
q: Quit the hunting group supervisor


441
Hunt groups
Maintenance
Parameters linked to the PCX
➨ edsbr
▼ dir
▼ hunt
▼ fc
➨ ednump
▼ dir
▼ mean
Voice guides
➨ vgton

Parameter meanings:
- dir : directory number
- mean : meaning
- fc : phone facilities class of service

442
Pick up / Hunt groups
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to create call pick-up and hunt groups
MANAGEMENT
1. Call pick-up groups

- Create a pick-up group called ‘Training’ with the sets : 3x000,3x001, 3X011
- Create the “group call pickup” prefix
- Create the “direct call pickup” prefix
- Create the “agent processing group call pickup” prefix
(NB: Choose free directories numbers in the dialing plan)
- 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
- Test it
2. Hunt groups
- Create a circular hunt group 3x500 with the sets : 3x004, 3x001, 3x002
- Test it
- Modify the group type search to sequential
- Test it
- Create the “sta.group exit “ prefix
- Create the “sta.group entry “ prefix
- Test these 2 prefixes
- When the 3 sets are withdrawn, the calls must be presented to the set 3x003.
- Modify the rotation timer (timer No. 36) value to 10 seconds
- Test it

443
Pick up / Hunt groups

444
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
445
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
446
Multiline / Supervision

OBJECTIVES:
◆ To describe multi-line functions
◆ To describe supervision functions
Alcatel OmniPCX Enterprise – Multiline / Supervision

447
Overview
One number on several keys: multi-keys
➨ Receiving calls
▼ receiving on one key

▼ second call on the second key
with the first call on hold
▼ several calls at a time
➨ Caller display 4510

4510
▼ display updated for each new 4510
event
4510
▼ calls on each key displayed
➨ Flexibility
▼ the extension is considered free so
long as one line is free

The use of programmable keys is required for those functions.

Per type of set, it exists a certain number of free programmable keys, modifiable pre-programmed keys, unchangeable pre-
programmed keys.
In the example, 4510 is the main directory number of the set.

448
Overview
Several numbers on the same extension: multi-number
➨ Receiving calls
▼ distinguishing the call origin
✦ internal calls
✦ different business calls
✦ several simultaneous calls
4510 4520 4530
➨ Displaying the call 4510 4520
4510
▼ display updated for
each new event
▼ calls on each key
displayed
Customer DID
Company DID
Internal

In this example, 4510 is the primary directory number of the set and 4520, 4530 are called secondary directory numbers and they
are in the dialing plan associated to this set. Now this set can be called with different directory numbers.

449
Overview
Pictograms
➨ Example
▼ a colleague is put on hold (1)

▼ a conversation with a customer (2)
▼ another customer calls (3)
2 1
customer company
4510 4520
customer company
4510 4520
3 customer
4510


450
Overview
Automatic line seizure
➨ Automatic line seizure outgoing
➨ Automatic line seizure incoming
Selective forwarding
➨ Main lines
➨ Secondary lines
➨ All lines (main and secondary)

Automatic line seizure: these two options can be independently enabled or not for each Multiline extension.
-if this option is validated (for outgoing or incoming calls), the line will be automatically selected without any manual action:
- outgoing calls: on off-hook, the first free line is seized
- incoming calls: the first ringing line is seized
-if this option is not validated, whatever the kind of call (incoming or outgoing), the line can only be seized by pressing the needed
multi-line key
The main lines are the different multi-lines keys which correspond to the directory number used for the creation the user.
(Given an user created with the directory number:4100, all keys programmed with the same directory number will be the main lines).
The secondary lines are the supplementary directory numbers.
(Given the previous example, if you add other multi-lines with a different number (4200, 4300), they will be secondary lines).
Selective forwarding option:

- Main lines: only all lines with the main directory number will be forwarded (e.g.: 4100)
- Secondary lines: only all lines which do not correspond to the main directory number will be forwarded (e.g.: 4200, 4300)
- All lines: all lines with the main directory number, and all lines with the other directory numbers will be forwarded.

451
Overview
Set supervision
➨ Notification of status
▼ partially busy
▼ totally busy
▼ free
B A
▼ rung
Superv. A
➨ Call interception on ringing
(caller's name displayed)
Superv. B
➨ Direct call Superv. C
➨ Fax Notification
C

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.
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).
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.
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.

452
Overview
Display
➨ The same number on several extensions (eg: 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
▼ Normal ring
4520 4510 4530 4510 4540 4510
4520 4510 4530 4540
Set 1 Set 10 Set 21

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
normal 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 (overlaid) ringing signal (one bleep) 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 additional (overlaid) ringing signal (one bleep) if he/she is in the same situation as for the ringing option (the bleep is
controlled by the system management function).

453
Overview
Supervision of a voice mailbox (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.

This feature is compatible with the following mailboxes:4635,4620 (VPS)
Voice mailbox supervision is also available on a homogenous network or an ABC-F2 link.
It is available on UA multiline sets ( 4010, 4020, 4035, IP-Phone, TSC DECT).Not with the 4004
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.

454
Overview
Trunk group supervision
➨ Supervising a trunk group means indicating its status (free

or busy) using an 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.
➨ The maximum number of trunk group that can be

supervised is 32. However, the sum of the trunk groups and
trunks supervised cannot exceed 96.
➨ A trunk group can be supervised by a maximum of 20 sets.


455
Overview
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
➨ 96 trunks maximum can be supervised.
➨ A trunk can be supervised by a maximum of 20 sets.


456
Multiline extension management (MGR)
PROCEDURE
OBJECTIVE
- To learn how to create a multiline extension with mgr
OVERVIEW
The term "multiline" means that a dedicated digital set can have one or more call numbers and each
call number can be associated with one or more programmable keys.
A multiline set may be a UA dedicated set (Alcatel 4004, 4010, 4020 or 4035) or a DECT set (4074
Mobile 100/200) or PWT set, with or without keypad extension and having programmed keys for
carrying out certain facilities specific to multiline sets

457
PROCEDURE
1. Create multiline keys on one extension

On mgr
Path Users/ Descend hierarchy/ Progr.Keys/ Review-Modify/ All instances (enter the
set number)
Action Descend hierarchy
Prog. keys
Entry Directory number: 31000 (e.g.)
Key number: 1 (e.g.)
Entry Directory Number : 31000
Key Number : 1
Function + Multi-line
Mnemonic (Pocket,Mobile,4040) : ------------ (empty)
Associate Directory key Number : 0
Remark :
A multiline set has more than one multiline key, so you can create another one
Key Number : 2

458

Remark:
It’s possible to manage the Multi directory number (or Multi MCDU), the user
has one or more call number for his set.
For example, to one or more private lines
Warning : the directory number must not correspond to an existing number
but can be DDI
Parameters Directory Number : 31000
Key Number : 3

459
2. Check the management of the multiline sets

Login mtcl
Command multitool
Result (1)xa000001> multitool
+------- [ 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 number: 1
Result CHOICE ? 1
+----[ Consult Multilines And Supervised Sets ] -------+
Nulog | Numan | Domain | Multiline | Supervised

1 | 31000 | 0 | Yes | No
ooo Number of Multilines Set = 1
ooo Number of Supervised Set = 0
h/Help q/Quit, Lines 1-9/9 End Of File

460
On the call server

Login mtcl
Command multitool
Result CHOICE ? 10
+----[ Multiline Sets With Their Multiline Keys ]-------+
[ 0] - Father Menu
[ 1] - From Database
[ 2] - From Memory
CHOICE ?
Result CHOICE ? 1
+------------[ From Database ]-------------+
Sorted by [0=Logical Number, 1=Set Number] ?
Entry Sorted by [0=Logical Number, 1=Set Number] ? 1
Result |Nulog|Set Number|Order|Key Number|Multiline Number|tab_mcdu|
-------------------------------------------------------------
| 2| 31000| | 1| 31000| 0|
| | | | 2| 31000| 0|
| | | | 3| 31001| 0|

461

Login mtcl
Command readkey
Result (1)xa000001> readkey
--> 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
Enter mcdu: 31000
Result Keys state of the 31000 mcdu phone set:
Phone set type: UA 4035
Number of keys = 28
Key 1: Multi MCDU ---> Key content: 31000
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 3: Multi MCDU ---> Key content: 31001
inf_num: -1
etat_led: 45
pri_cour_line: 0-0
cor_pre: 0
keytype: 255

462
Set supervision management (MGR)
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 multiline).
Warning : an attendant or set group cannot be supervised.

463
PROCEDURE
1. Management of the set supervision

Application On mgr
Select Users
Descend hierarchy
Prog. keys
Entry Directory number: 31000
Key number: 11
Key No. : 11
Function + Set Supervision
Mnemonic (Pocket,Mobile,4040) : --------------
Ringing Mode + No Ring
Deferred ring + NO
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.

464
2. Check the management of the supervision set

Login mtcl
Command multitool
+------------------- [ Main Menu ] ---------------------+
[ 0] - Exit
CHOICE ?
Entry Choice ? 1
Result CHOICE ? 1
+-----[ Consult Multilines And Supervised Sets ] -------+
0 | 31010 | 0 | No | Yes
1 | 31000 | 0 | Yes | No
Remark :
you can see if the set is supervised or not

465

Login mtcl
command multitool
+--------------------[ Main Menu ]----------------------+
[ 0] - Exit
CHOICE ?
Entry Choice ? 5
Result CHOICE ? 5
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 ?
Entry Choice ? 1
Result +---[ Consult All <Supervised> Directory Number ]-------+
Supvised N | Dom. Spvis | Spvised Nu | Dom. Spvis
31010 | 0 |
ooo Number of <Supervised> Number = 1
Action Press Enter to come back on the previous menu
Entry Choice ? 2
Result +--[ Consult All <Supervisor> Of a Directory Number ]---+
< Supervised Number > ? 31010
Spvisor Nu | Dom. Spvis | Spvisor Nu | Dom. Spvis
31000 | 0 |
ooo Number Of <Supervisor> For the Directory Number [31010] = 1

466

Entry Choice ? 2
Result +------------[ Consult All <Supervisor> ]---------------+
Nulog Spvi| Numan Spvi|Key Spviso|Dom. Spvis|Supervised | Dom. Super
2 | 31000 | 8 | 0 | 31010 | 0
ooo Number Of <Supervision Directory Number Key> = 1
ooo Number Of <Remote Supervisor Directory > = 0

467

468
Multiline
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to use multiline sets
MANAGEMENT
1. Multiline sets
- Modify the reflex sets to make them multiline with this configuration:
- Set 3x001
- Key 1 Multiline 3x001
- Set 3002
- Set 3003
- 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)

469
Multiline

470
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
471
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
472
Manager/assistant group

OBJECTIVE:
◆ To describe the manager/assistant group
Alcatel OmniPCX Enterprise – Manager/assistant group

Ref. ENTPTE0407P01TEUS Issue 01
473
Manager/Assistant Group
Overview
Manager/assistant group
➨ Two multiline sets defined one as Manager and the other as

assistant
▼ On the manager extension, there is a “assistant call” key.
▼ On the assistant extension, there is a “manager call” key.
▼ Those both keys are used as a hot line (direct call, supervision).
▼ A multi-line extension can be both "manager" and "assistant"
▼ Limits:
✦ 1 Manager / 8 assistants
✦ 1 assistant / 8 Managers

-The manager/assistant features described next are available on multiline sets only: 4035, mobile reflexe...
-The maximum number of assistant and manager extensions depends on the number of keys available on the extension with a
maximum of eight
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

474
Overview
Filtering
➨ Screening: Immediate Forwarding by Origin

➨ Unscreening key: Immediate Pickup by Origin
➨ These keys are associated to a filtering table.
Filtering tables
➨ 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
▼ an abbreviated number or several
▼ an attendant number or several
▼ a T2 number (specific ISDN number: see next page) or several
➨ It is possible to mix in the same filtering table different parameters.

Filtering:
- The manager has the possibility to activate or deactivate his filtering.
- The manager can have several screening or unscreening keys and several assistants.
-A SCREENING (Immediate forwarding according to origin) key is associated with a filtering table. This function is only possible if the
set is MANAGER.
When the key is activated, only calls from users whose number is contained in this filtering table will be directed to the assistant set,
the other calls will arrive directly on the manager set.
An UNSCREENING (Immediate seize according to origin) key is associated with a filtering table. This function is only possible if the set
is MANAGER.
When the key is activated, only calls from users whose number is contained in the filtering table will be directed to the manager set,
the other calls being forwarded to the assistant set. If the UNSCREENING table is empty, all the calls will be forwarded to the assistant
set.
- 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.

475
Overview
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 validated by the assistant

▼ assistant can validate the filtering with a «filtering supervision» key
Discrete listen-in
▼ Dynamic key on the manager's extension
▼ Call interception
▼ Notification on assistant set

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.

476
Overview
Away assistant function
➨ Only possible on an assistant set and on one key only
➨ Allows the assistant to signal her absence to her manager(s)
➨ Filtering is then suspended until the assistant presses this key

again.
➨ When this key is validated, personal calls destined to the

assistant still reach the assistant set.

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.

477
Overview
Routing assistant function
➨ In a manager - assistant configuration, there can be one

overflow assistant who will automatically replace the official
assistant when the latter is in assistant away position and
who will carry out the same functions.
➨ There is only one overflow assistant per manager, but this

overflow assistant can have several managers.
➨ This set must not already be declared assistant for this

manager.


478
Overview
Screening supervision key
➨ Used to activate or disable forwarding according to call

origin (Screening or Unscreening) by the assistant.
➨ Allows an assistant to activate the manager filtering and to

disable any manager filtering remotely ( from her set ).
➨ A » screening supervision » key is needed for each screening

or unscreening key.


479
Overview
Manager/assistant messaging
Arrival of Mr. X
next
➨ Extensions busy or free
assistant set
urgent call from Mr. X.

next
keyboard
manager message
urgent call from Mr. SMITH
valid next erase

This application is available only on Alcatel 4035 UA set (requires dynamic keys for the manager's extension) fitted with an alphabetic
keypad (characters entered on the assistant extension)
If there are several managers, the assistant must select the manager after pressing the "MANAGER MESSAGE" key.
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
The assistant cannot send short messages to a manager on a conference call, dialing, three party call, on a call with his assistant.
The manager can receive or send a message either if he is taking part in telephone conversation or in idle state.

480
Overview
Manager/assistant messaging
assistant: busy or free Manager: busy or free
urgent call from Mr. SMITH
valid next erase
answer: urgent call from Mr. SMITH

He calls Wait I call Put through Return
answer: put him through please Caller’s directory number

return


481

482
Manager / Assistant Group management (MGR)
PROCEDURE
OBJECTIVE
- To learn how to manage Manager / Assistant Groups
OVERVIEW
An assistant set is made up of two multiline sets, one of which is declared MANAGER set and the
other ASSISTANT set.

483
PROCEDURE
1. Create manger and secretary call keys

On mgr
Select Users
Descend hierarchy
Prog. keys
Entry Directory number: 31000 (e.g.; enter the manager set n°)
Key number: 3
Action Press CTRL+V or F1 to validate your selection
Entry Directory Number: 31000
Key Number: 3
Function + Assistant call
Mnemonic (Pocket,Mobile,4040): ------------ (empty)
Action Press CTRL+V or F1 to validate your management
Key Number: 3
4040 – Mnemonic2: ------------- (empty)
Remark:
The management of the Assistant call key on the Manager set (31000) creates
automatically the Manager call key on the Assistant set (31001) position 3

484
2. Create an Absence assistant function key

On mgr
Select Users
Descend hierarchy
Prog. Keys
Entry Directory number: 31001 (e.g.; enter the assistant set number)
Key number: 4
Key Number: 4
Function + Assistant away
Remark:
The manager can see on the Assistant call key if the secretary is absent or not.

485
3. Create a Manager Mail function key

On mgr
Select Users
Descend hierarchy
Prog. Keys
Entry Directory number: 31001 (e.g.; enter the assistant set number)
Key number: 5
Key Number: 5
Function + Manager mail
Remark:
The secretary send a text message on the manager set screen and he can
make an answer.

486
4. Manage the screening function and filtering tables
4.1 Create the screening function key

On mgr
Select Users
Descend hierarchy
Prog. Keys
Entry Directory number: 31000 (e.g.; enter the manager set number)
Key number: 4
Key Number: 4
Function + Screening key
Entry Filtering table N°: 2
Remark:
The management of the filtering table will be seen in chapter No. 4.3. .

487
4.2 Create the unscreening function key

On mgr
Select Users
Descend hierarchy
Prog. Keys
Entry Directory number: 31000 (e.g.; enter the manager set number)
Key number: 5
Key Number: 5
Function + Unscreening key
Entry Filtering table N°: 1
Remark:
The management of the filtering table will be seen in chapter No. 4.3. .

488
4.3 Create the Filtering tables

Application On mgr
Select Specific Telephones Services
Descend hierarchy
Filtering table
Action Create
Parameters Table ID: 2
Filtering key Type
[ Add ] [ Remove ] [ Next ] [Previous]
Filtering key Type
Filter Type + ---------------
Content: ---------------
Action Go to “Add” with the arrow keys
Press Enter
Entry Table ID: 2
Filtering key Type
[ Add ] [ Remove ] [ Next ] [Previous]
Filtering key Type
Filter Type + One Directory No.
Content: 31010
Action Press CTRL+V to validate your management
Remark:
- Table ID corresponds to the Filtering table No. configured on the Screening
or Unscreening keys.
- There is different Filter types:
• All Directory No.
• All Trunk Groups
• One Directory No.
• One Speed Dialing No.
• One Attendant number
• T2 Key
• Directory
Remark:
- 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 .

489
5. Check the Executive/Secretary Group configuration

Login mtcl
Command multitool
+--------------------[ Main Menu ]----------------------+
[ 0] - Exit
CHOICE ?
Entry Choice ? 1
Result +----[ Consult Multilines And Supervised Sets ]---------+
0 | 31010 | 0 | No | Yes
1 | 31000 | 0 | Yes | No
Remark:
you can see if the set is supervised or not

490

Login mtcl
Command multitool
+---------------------[ Main Menu ]---------------------+
[ 0] - Exit
CHOICE ?
Entry Choice ? 2
Result +------- [ Consult Boss/Secretary ] -------+
[ 0] - Father Menu
[ 1] - Consult All <Boss> Sets
[ 2] - Consult All <Secretary> Sets
[ 3] - Consult All <Routing Secretary> Sets
CHOICE ?
Entry Choice ? 1
Result +-------------[ Consult All <Boss> Sets ]---------------+
Nulog Secr|Numan Secr|Key Secret|Dom.Secre|Boss Mcdu |Key Boss|Dom.Boss
3 |31001 |3 | 0 | 31000 | 3 | 0
ooo Number Of <Boss> Sets = 1
Entry Choice ? 2
Result +-----------[ Consult All <Secretary> Sets ]------------+
Nulog Boss|Numan Boss|Key Boss|Dom. Boss|Secretary|Key Secret|Dom.Secre
2 | 31000 | 3 | 0 | 31001 | 3 | 0
ooo Number Of <Secretary> Sets = 1

491
Entry Choice ? 3
Result +----------[ Consult All <Secretary> Sets ]------------+
Nulog Rout| Numan Rout| Dom. Rout.| Boss Mcdu | Dom. Boss
2 | 31000 | 3 | 0 | 31001 | 3
| 0
Nulog Rout | Numan Rout | Dom. Rout. | Boss Mcdu | Dom. Boss
2 | 3400 | 0 | 3404 | 0
ooo Number Of <Secretary> Sets = 1

492
Multiline / Manager - assistant groups

OBJECTIVES:
◆ To maintain Manager / assistant groups
◆ To check programmable keys management
Alcatel OmniPCX Enterprise - Multiline / Manager - assistant groups

493
Multiline,
Multiline, Manager - Assistant groups
Maintenance
Commands
➨ Multi-line, Manager/assistant Group sets edition: multitool
+------- [ Main Menu ] -------+

[ 0] - Exit
CHOICE ?

This menu can also be accessed by the client account or command menuclient under the account mtcl or mtch
The path is:
1-Database
1-Show multi-line sets

494
Multiline,
Multiline, Manager - Assistant groups
Maintenance
Commands
➨ Sets keys display: readkey
▼ --> main menu <--

2) display by mcdu
q) quit


495

496
Manager - assistant group
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the manager/assistant group
MANAGEMENT
1. Management of a group 1 manager / 1 assistant

- Create a group between the sets 3x000 (Manager) and the set 3x001 (Assistant).
- The manager key number 2 (Assistant call) must correspond to the assistant 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
- 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)
- 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

Note: The manager mail needs some sets type 4035 or 4037.
- Create on the assistant set a key type ‘manager mail’
- Test it
3. Maintenance
- Using the command “multitool” display the information about the manager / assistant
teams.

497
Manager - assistant group

498
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
499
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
500
External Call Barring

OBJECTIVE:
◆ To set up the multi translator for barring restriction
Alcatel OmniPCX Enterprise – External Call Barring

501
Barring restriction
Overview
Barring principle
➨ To reduce the company costs, the barring facility is used to
allow/forbid external outgoing calls according to the user
and the called number
User A Areas Definition

Local: 603 XXXX
National: 1 XXXXXXX
International: 00 or 011(NA)
Special Phone: 08 Central
User B Office
Example of baring restriction

User A is allowed to make Local and National calls
but is not allowed to make International calls and Special calls
User B is allowed to make all calls


502
Barring restriction
Overview
Definition of the areas
➨ Dialing Discriminator:
▼ The dialing DISCRIMINATOR object defines the external numbering
plan that is to say the areas for all the system.
▼ The areas definition depends on the PCX localization and on the cost
of calls
✦ Local calls are usually the cheapest or might be free
✦ International call can be the most expensive calls
▼ e.g. Dialing discriminator #1

✦ Area 1 ( Local Calls)
Called Number starting with: 603 and 899
✦ Area 2 ( National Calls )
Called Number starting with: 1
✦ Area 3 (International Calls)
Called Number starting with: 00 or 011 (North America)

Limits
256 different dialing DISCRIMINATOR can be managed in the system.
Each dialing Discriminator can contain 64 areas
Lots of called number can be managed in one area

503
Barring restriction
Principle
When a user dials an outgoing number, what does the

system check?
➨ Step 1: Selection of the Dialing Discriminator (definition of

the areas)
▼ associated to the used trunk Group
➨ Step 2: Selection of the Area number

▼ associated to the called number
➨ Step 3: Checking of the Area authorization

▼ associated to the caller


504
Barring restriction
Principle
Step 1: Selection of the Dialing Discriminator
➨ When a user seizes a trunk group (via prefix code), the

system checks a pointer Id in the associated Trunk group.
This parameter is called the LOGICAL DISCRIMINATOR
object (0 to 7)
➨ Then the system checks the link between the logical

discriminator and the dialing discriminator in the entity of
the user
➨ e.g. User A seizing Trunk Group 20

▼ TG 20 param.: Logical Discriminator #3
▼ User's entity: Logical Discriminator #3 = Dialling DISCRIMINATOR
#1
▼ The system knows it must check the DISCRIMINATOR #1

Limits:
One entity can point on 8 real discriminators.

505
Barring restriction
Principle
Step 2: Selection of the Area number
➨ Once the system has selected the Dialing Discriminator (e.g.

#1), it searches in it to find the best match between the
called number and the numbers defined in the areas
➨ e.g.:
▼ The user dialed 1339324792
▼ Dialing discriminator #1
✦ Area 1 ( Local Calls)
Called Number starting with: 603 and 899
✦ Area 2 ( National Calls )
Called Number starting with: 1
✦ Area 3 (International Calls)
Called Number starting with: 00 or 011 (North America)
▼ The systems knows that the corresponding area is the area #2 and
has know to check if the area is allowed or not.


506
Barring restriction
Principle
Step 3: Checking of the Area authorization
➨ The areas access right depends on the user class of services
➨ The system checks in which class of Service the caller

belongs to.
➨ In this class of service, the area is allowed or not
➨ e.g.:
▼ Caller parameters: Access Class of service #4
▼ Access Class of service #4:
✦ Area 2: Allowed
▼ The system knows that the call is authorized

Limits
32 Access Clas sOf services

507
Barring
Additional possibilities
Additional topics
➨ It is possible to completely forbid the seizure of one trunk

group to a caller regardless of the called number
➨ It is possible to forbid one area during Night System Mode

and to allow it during the Day Mode
➨ The configuration of several Dialing DISCRIMINATOR is

mainly useful:
▼ in case of multi-company configuration ( each company can ask for
its specific management)
▼ when the barring must be different according to Trunk Group seized


508
Barring restriction
Overview
General overview
Central Office
Entity
Entity
Entity_Discriminator_Selector trunk group
Entity_Discriminator_Selector trunk group
Discriminator_00: 0 Num. compatible with : 0..7 ³ logical discriminator
Discriminator_00: 0 Num. compatible with : 0..7 ³ logical discriminator
// -1 ³ no barring restriction
// -1 ³ no barring restriction
Discriminator_07: 0
Discriminator_07: 0
1 Max Number of digits : if no logical discriminator is used,
Max Number of digits : if no logical discriminator is used,
the max. length of digits must be set.
the max. length of digits must be set.
Logical Real
0..7 0..255 2
Dialing Discriminator
Dialing Discriminator
³ Dialing Discriminator (0..255: Real)
³ Dialing Discriminator (0..255: Real)
0: Public
0: Public
Access class of service (0..31) ³ Discriminator rule
Access class of service (0..31) 3 ³ Discriminator rule
Area 1 (1..64) call number : 00
Area 1 (1..64) call number : 00
Night : 1 ³ authorized Dialing area :1
Night : 1 ³ authorized Dialing area :1
Day : 0 ³ not authorized ARS route list Nb: 0
Day : 0 ³ not authorized ARS route list Nb: 0
Mode 1: 1 ³ authorized Schedule Nb : -1
Mode 1: 1 ³ authorized Schedule Nb : -1
Mode 2: 1 ³ authorized Number of digits: 10
Mode 2: 1 ³ authorized Number of digits: 10


509
Barring restriction
Overview
Simple Barring configuration
Central Office
In all Trunk group (by default) Trunk group

In all Trunk group (by default) Trunk group
Num. compatible with : -1 Num. compatible with : 0
Num. compatible with : -1 Num. compatible with :
to be
In Translator/ Dialing Discriminator changed In Translator/ Dialing Discriminator
In Translator/ Dialing Discriminator In Translator/ Dialing Discriminator
³ Dialing Discriminator (0..255: Real) ³ Dialing Discriminator (0..255: Real)
³ Dialing Discriminator (0..255: Real) ³ Dialing Discriminator (0..255: Real)
0: Public 0: Public
0: Public 0: Public
³ Discriminator rule ³ Discriminator rule
³ Discriminator rule ³ Discriminator rule
empty area creations
empty
In all Entity (by default) In Access class of service linked to users

In all Entity (by default) In Access class of service linked to users
Entity_Discriminator_Selector Area #
Entity_Discriminator_Selector Area #
Discriminator_00: 0 Night,Day,Mode1,Mode2
Discriminator_00: 0 Night,Day,Mode1,Mode2
1 ³ authorized
Default Configuration 0 ³ not authorized


510
Barring restriction
Overview
Example 1: Allowed outgoing call
#0520045985400 TG: 10
Central
authorized call Office
35000
Entity 5
1 Public network COS 5 2
Prefix plan
Prefix plan Entity 5
professional seize prefix: #052 Entity 5
professional seize prefix: #052 Entity_Discriminator_Selector
Trunk group 10 Entity_Discriminator_Selector
Trunk group 10 Discriminator_03: 15
Num. compatible with : 3 Discriminator_03: 15
Num. compatible with : 3
3 Translator
Translator 4
³ External dialing plan
³ External dialing plan
³ Dialing Discriminator
³ Dialing Discriminator Access classe of service 5
15: AT&Tent5 Access classe of service 5
15: AT&Tent5 Area 1
³ Discriminator rule Area 1
³ Discriminator rule Night : 1
Call number : 00 Night : 1
Call number : 00 day : 1
Dialing area :1 day : 1
Dialing area :1 Mode 1: 1
ARS route list Nb: 0 Mode 1: 1
ARS route list Nb: 0 Mode 2: 1
Schedule Nb : -1 Mode 2: 1
Schedule Nb : -1
Number of digits:10
Number of digits:10


511
Barring restriction
Overview
Example 2: Forbidden outgoing call
#0520045987400 TG: 10 CO
call not authorized

35001
Entity 5
1 Public network COS 6
2
3 Translator
Translator
³ external dialing plan
³ external dialing plan 4
Call Number : 00 Night : 0
Call Number : 00 Night : 0
Dialing area :1 Day : 0
Dialing area :1 Day : 0
ARS route list Nb: 0 Mode 1 : 0
ARS route list Nb: 0 Mode 1 : 0
Schedule Nb : -1 Mode 2 : 0
Schedule Nb : -1 Mode 2 : 0
Number of digits: 10


512
Barring restriction
Overview
Example 3: Forbidden outgoing call
#0520214603400
TG: 10 C0
call not authorized
35000
Entity 5
Public network COS 5
1
3
Prefix plan
Prefix plan Translator
professional seize prefix: #052 Translator
professional seize prefix: #052 ³ External dialing plan
Trunk group 10 ³ External dialing plan
Trunk group 10 ³ Dialing Discriminator
Num. compatible with : 3 ³ Dialing Discriminator
Num. compatible with : 3 20: AT&Tent5
!
20: AT&Tent5
³ Discriminator rule
³ Discriminator rule
Call number : 00
Call number : 00
2 Dialing area :1
Dialing area :1
…
…
Entity 5 Call number : 0234
Entity 5 Call number : 0234 0214... is not a call number
Entity_Discriminator_Selector Dialing area : 2
Entity_Discriminator_Selector Dialing area : 2 in the translator 20
Discriminator_03: 20
Discriminator_03: 20


513
Barring restriction
Overview
Example 4: Different barring restriction to different trunk

groups (For the same entity)
CO1
34000 TG 40
TG 40
Entity 4
TG 42
TG 42 CO2
34001
3
Entity 4
1
2 Translator
Trunk group 42 Translator
Trunk group 42 ³ External dialing plan
Num. compatible with : 5 ³ External dialing plan
Num. compatible with : 5 ³ Dialing Discriminator: 7
Entity 4 ³ Dialing Discriminator: 7
Entity 4
Entity_Discriminator_Selector
Entity_Discriminator_Selector
Trunk group 40 Discriminator_04: 7 Translator
Trunk group 40 Discriminator_04: 7 Translator
Num. compatible with : 4 Discriminator_05: 15 ³ External dialing plan
³ Dialing Discriminator: 15


514
Barring restriction
Overview
Example 5: Different barring on 2 different trunk groups

(For different entities)
34000
Entity 4 CO1
TG 40
TG 40
CO2
34001
Entity 41 TG 42
TG 42
1 2 3
Entity 4
Trunk group 40 Entity 4
Trunk group 40 Entity_Discriminator_Selector Translator
Num. compatible with : 4 Entity_Discriminator_Selector Translator
Discriminator_04: 14 ³ External dialing plan
Discriminator_05: 15 ³ Dialing Discriminator: 14
Trunk group 42 ³ Dialing Discriminator: 15
Trunk group 42 Entity 41 ³ Dialing Discriminator: 15
Num. compatible with: 5 Entity 41
Num. compatible with: 5 Entity_Discriminator_Selector Translator
Entity_Discriminator_Selector Translator


515

516
External call barring configuration
PROCEDURE
OBJECTIVE
- To learn how to configure the external call barring in a simple configuration
OVERVIEW
Call restrictions - barring (discrimination) is used by the system to check whether the caller has the
right to call the number dialed.
To decide whether to authorize or bar a call, the system uses:
The initial digits of the number dialed.
The public network carrier. This is because the signification of the number dialed differs depending
on carrier.
Caller entity. The restriction/barring (discrimination) rules are not necessarily the same on different
entities.
The time of the call. Calls authorized at certain times (during the day, for example), may not be
authorized at other times (during the night, for example). System mode (day/night) is set either by
the attendant or by a time period schedule (automatic switchover at a predetermined time).
The calling set. Calls authorized on a manager set are not allowed on a booth (i.e. "public"/self-
service) set.
On this configuration procedure we are going to setup 3 different barring configurations:
a) a simple barring with creation of areas, validation of barring and management of users rights
for a mono-entity site and barring management not depending on outbound trunk group used.
b) an advanced barring with creation of areas, validation of barring and management of users
rights for a multi entity site and barring management not depending on outbound trunk group
used.

517
PROCEDURE
1. Simple barring Management - Example 1

In this management procedure, we want to configure a simple barring including the use of the
default DIALING DISCRIMINATOR (#0) and having different Public Network Class Of Services
According to user barring profiles. All the users belong to the same Entity (#1)
In this example we create 3 areas (#1,#2,#3) .
Area #1 contains the local calls (Number starting with 01, 02)
Area #2 contains the national calls (Number starting with 0 )
Area #3 contains the international calls (Number starting with 00)
Area #1 allowed for Public COS 10, 20, and 30
Area #2 allowed for Public COS 10 and 20
Area #3 allowed for Public COS 10
User 3000 belongs to Public COS 10
User 3000
Public COS 10
Entity 1
Trunk Group ID:30
User 3001
Public COS 20 Central Office
Entity 1
User 3002
Public COS 30
Entity 1

518
Areas definition - Edit the dialing discriminator #0 and manage the associated rules
On mgr
Select Translator
External Dialing Plan
Dialing (Numbering) Discriminator
Discriminator Rule
Action Create
Discriminator No.: 0
Entry
Call Number: 01
Dialing Area: 1
Number of Digits : 10
Action Press CTRL+v to validate the creation
Entry
Call Number: 02
Dialing Area: 1
Entry
Call Number: 0
Dialing Area: 2
Entry
Call Number: 00
Dialing Area: 3

519
1.1 Barring Validation

On mgr
Select Trunk Groups
Trunk Groups
Entry Trunk group ID: (for example: 30, the Trunk Group that must be barred)
Trunk Group ID : 30
Trunk Group Type + T1
Trunk Group Name : AT&T
Number Compatible With : 0
Remark:
By putting 0 in "Number Compatible with" attribute, the system will now use
the barring facility each this trunk group will be used. The system will go
through the default Dialing DISCRIMINATOR 0, named Public to check the
areas definition.
To check if you are in this default configuration, you must go on the entity to
check the link between the Entity Discriminator (logical) and the Dialing
DISCRIMINATOR :
Select Entity
Discriminator Selector
Entry Entity Number : 1 (in the example, all the users belong to the entity 1)
Consult Discriminator 00 : 0

520
1.2 Public Network COS definition(Authorize the call numbers)

On mgr
Select Classes of Service
Access COS
Public Access COS
Select Public Network COS : 10
Area Identifier : 1
Review/Modify : Public Access COS
Entry
Public Network COS : 10
Area Identifier : 1
Public Access Rights
Night : 1
Day : 1
Mode 1 : 1
Mode 2 : 1
Action Press CTRL+v to validate the edition
Remark :
To authorize: select 1
To forbid: select 0
Area Identifier : 2
Entry
Area Identifier : 2
Night : 1
Day : 1
Mode 1 : 1
Mode 2 : 1
Area Identifier : 3
Entry
Area Identifier : 3
Night : 1
Day : 1
Mode 1 : 1
Mode 2 : 1

521

Area Identifier : 1
Entry
Area Identifier : 1
Night : 1
Day : 1
Mode 1 : 1
Mode 2 : 1
Area Identifier : 2
Entry
Area Identifier : 2
Night : 1
Day : 1
Mode 1 : 1
Mode 2 : 1
Area Identifier : 1
Entry
Area Identifier : 1
Night : 1
Day : 1
Mode 1 : 1
Mode 2 : 1
Remark: the other Areas number must have parameters set to 0
Night : 0
Day : 0
Mode 1 : 0
Mode 2 : 0

522
1.3 User Rights (Public Network COS)

On mgr
Select Users
Select Directory Number : 3000
Entry Public Network COS : 10
Press CTRL+c
Press CTRL+c
Press CTRL+c
1.4 Baring command

Application On the Call server
Login mtcl
Command discrlist
(101)xa001001 > 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 : 1
Remark:
Choice: 1
978 : tsled digit number 3
dblto 0 , to 0 area 1 rlid 0 sched -1 maxdgt 10 pause 0
01 : call number
area : dialing area
rlid : ARS Route List Nb
maxdgt : Number of digits

523
2. Advanced Barring - Example 2 ( MultiCompany)

In this management procedure, we want to configure an advanced barring including the use
of 2 DIALING DISCRIMINATORS: 0 (for entity 7) and 5 (for entity 8). We will use the same
Public Network Class Of Services and a Multi Entity configuration.
The prefix 9 is the professional trunk group seizure prefix for the trunk group ID: 30
We create 3 areas (1,2,3) for Entity 7
- Area 1 contains the local calls (Number starting with 01, 02)
- Area 2 contains the national calls (Number starting with 0 )
- Area 3 contains the international calls (Number starting with 00)
We create 3 areas (1,2,3) for Entity 8
- Area 1 contains the local calls (Number starting with 01, 02)
- Area 2 contains the national calls (Number starting with 0 )
- Area 3 contains the international calls (Number starting with 00)
- Area 1 allowed for Public COS 10 - Area 1 allowed for Public COS 20
- Area 2 allowed for Public COS 10 - Area 2 not allowed for Public COS 20
- Area 3 allowed for Public COS 10 - Area 3 not allowed for Public COS 20
Entity 7: Entity 8:
User 3000 belongs to Public COS 10 User 3010 belongs to Public COS 10
User 3002 belongs to Public COS 20 User 3012 belongs to Public COS 20
Users : 3000 I 3002 Trunk Group ID:30

Public COS: 10 I 20
Entity 7
Central Office
Users : 3010 I 3012

Public COS: 10 I 20
Entity 8

524
2.1 Areas definition - Edit the dialing discriminator 0 and create the number 5
Manage the associated rules
On mgr
Select Translator
Discriminator Rule
Action Create
Entry
Call Number: 01
Dialing Area: 1
Press CTRL+c to cancel and create another area
Entry
Call Number: 02
Dialing Area: 1
Entry
Call Number: 0
Dialing Area: 2
Entry
Call Number: 00
Dialing Area: 3
Select Translator
Action Create
Entry Discriminator No : 5
Name : Public Discriminator Office2

525
Press CTRL+c and go descend hierarchy to Access to Discriminator Rule

Action Create
Entry Discriminator No.: 5
Call Number: 1
Dialing Area: 1
Call Number: 2
Dialing Area: 1
Call Number: 0
Dialing Area: 2
Call Number: 7
Dialing Area: 3
Call Number: 8
Dialing Area: 3

526
2.2 Barring Validation and Use of logical discriminator 1

On mgr
Select Trunk Groups
Trunk Group
Entry Trunk group ID: (for example: 30, the Trunk Group that must be barred)
Trunk Group ID : 30
Trunk Group Type + T1
Trunk Group Name : AT&T
Number Compatible With : 1
2.3 Association of the real and logical discriminators in the entities of the users
Select Entity
Discriminator Selector
Entry Entity Number: 7
Discriminator 01: 0
Action Press CTRL+v to validate
Entry Entity Number: 8
Discriminator 01: 5
Action Press CTRL+v to validate

527
2.4 Public Network COS definition (Authorize the call numbers)

On mgr
Select Classes of Service
Access COS
Public Access COS
Area Identifier : 1
Entry
Area Identifier : 1
Night : 1
Day : 1
Mode 1 : 1
Mode 2 : 1
Remark :
To authorize: select 1
To forbid: select 0
Area Identifier : 2
Entry
Area Identifier : 2
Night : 1
Day : 1
Mode 1 : 1
Mode 2 : 1
Area Identifier : 3
Entry
Area Identifier : 3
Night : 1
Day : 1
Mode 1 : 1
Mode 2 : 1

528

Area Identifier : 1
Entry
Area Identifier : 1
Night : 1
Day : 1
Mode 1 : 1
Mode 2 : 1
Area Identifier : 2
Entry
Area Identifier : 2
Night : 0
Day : 0
Mode 1 : 0
Mode 2 : 0
Area Identifier : 3
Entry
Area Identifier : 3
Night : 0
Day : 0
Mode 1 : 0
Mode 2 : 0
Press CTRL+C as many time as needed to go back to the main menu

529
2.5 User Parameters (Public Network COS and Entity number)

On mgr
Select Users
Entity Number : 7
Press CTRL+c
Entity Number : 7
Press CTRL+c
Entity Number : 8
Press CTRL+c
Entity Number : 8
Press CTRL+c

530
Barring restriction

OBJECTIVE:
◆ To check the multi translator management for barring
Alcatel OmniPCX Enterprise – Barring restriction

531
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:

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 1

5: change discriminator id
to display its data

532
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


533

534
External calls barring
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage external calls baring with mgr and with Alcatel Expert Tool
MANAGEMENT
AT&T
Trunk Group x0
UA sets
Public Network Category: 3
Entity: 1
1. Manage your system according to the following table:
Users Outgoing Operator Authorized Numbering Forbidden Numbering

IP Phone T1 CCS 978 011
1
UA sets T1 CCS 978 1
011
3. Check and manage the trunk group seizure prefixes and the logical discriminators 0.

535
External calls barring
4. Manage the real discriminator 0, and the dialing areas according to the table above.
5. Check and manage the association , in the user entity, between the logical and the real
discriminator.
6. Check, in the access COS of the users, that the dialing areas are allowed or forbidden.
7. Do the different tests

536
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
537
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
538
ARS Principle

OBJECTIVES:
◆ To describe and configure the ARS
◆ To describe the ARS without time table principles
Alcatel OmniPCX Enterprise – ARS Principle

539
ARS
Overview
ARS = Automatic route selection
The ARS is used to select the best way (the cheapest) to

place an outgoing call. The seeking process is made by
the PCX (it is transparent for the caller).
➨ The PCX takes the way 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.
➨ The PCX operator manages the ARS according to:

▼ PCX resources (trunks , connections to operators)
▼ The tariffs (regular or discount)
▼ The periods of the day


540
ARS
Overview
Supplementary features
➨ The ARS can be linked to the barring
➨ The routes vary depending on the time and the traffic
➨ The ARS can modify the number dialed to reroute the call.
(not explained in this training)
➨ Private codes can be inserted in the number

(not explained in this training).

L’ARS en fonction du temps et l’accès aux opérateurs indirects sont expliqués dans la formation avancée.

541
ARS
Overview
Principle
Users System Trunk groups Networks
Only one external ISDN - Operator 1

line prefix.
the prefix ”9"
Which route?
ISDN- Operator 2
Dialing: Automatic tie line

9 0565478823
Telephone call Called number


542
ARS
Overview
Principle
Users System Trunk groups Networks
Only one external ISDN - Operator 1

line prefix.
ARS
the prefix ”9"
ISDN- Operator 2
Dialing: Automatic tie line

Route selection
9 0565478823
according to the
criteria managed:
•Dialed N° (direction)
•Cost
Telephone call Called number


543
ARS
Overview
ARS prefix
➨ To use the ARS, the ARS prefix must be dialed before the
external number
➨ We will use the prefix number 0 or 9

* "Discriminator number" corresponds to a logical discriminator used as a pointer for a real discriminator
The real discriminator contains the barring rules (possible dialed number). Each number can be associated with an ARS table
The link between the Logical an d Real discriminators is realized in the caller’s entity
[By default, the Real discriminator "0" is always used]

544
ARS
Overview
ARS routing table
➨ An ARS table is associated to a direction (call number)*
✦ One call number One ARS table
➨ We can define up to 10 routes per table
✦ 10 different ways to route the call for the same direction

(a route corresponds to a physical resource [trunk group] ).
✦ The order to use the routes is given in the "time based route list"
In case of "busy" or "out of order" state, there is an overflow between the routes
according to the management order

* This association is performed by the Real discriminator
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 indicated. This provides several possibilities to set the 10 available
routes in the correct order.

545
ARS
Overview
Definition of an ARS table
route 1 Operator 1
Route creation
Definition of route 2 Operator 2 (All the possible route)
the routes for one direction (called number)
route 3 Operator 3
Route N°1 route 1

Time based Time based
route liste Route N°2 route 2 Order given
route list in the table
N°1
Route N°3 route 3


546
ARS
Overview
Link between a direction and an ARS table
➨ Realized by the discriminator
➨ One ARS table can be associated to each external number

defined in the translator
Link between Discriminator and ARS
➨ Professional Trunk Group seizure

✦ The logical discriminator is placed in the global parameters of the trunk
group
➨ In case of ARS prefix:

✦ The logical discriminator is placed in the ARS prefix
✦ The logical discriminator in the global parameters of the trunk group is
ignored

* Schedule number: -1 corresponds to the default functioning. In this case, the default "time based route list number 1 is used to
give an order to the predefined routes

547
ARS
Overview

34000
Entity 4
N° dialled: 9 001939428
OP1
Trunk group 40
Trunk group 40
1 OP2
Prefixes plan Trunk group 42
Prefixes plan Trunk group 42
Prefix ARS: 9
Prefix ARS: 9
N° discriminator: 4
N° discriminator: 4 2 3
Translator
Entity 4 Translator
Entity 4 ³ Discriminator Trk group 40 is placed
Discriminator selector ³ Discriminator
Discriminator selector 7: OP1ent4 on top of ARS table 0 as
Discriminator 04: 7 7: OP1ent4
Discriminator 04: 7 ³ Discrimination rule it is considered to be the
³ Discrimination rule best way.
Called number: 00
Called number: 00 If trk group 40 is busy
Area: 1
Area: 1 the call falls back onto
ARS table: 0 trk group 42
ARS table: 0
³ ARS Table 0:
³ ARS Table 0:
route 1: trk group 40


548
ARS
Overview

34000
Entity 4
N° dialed: 9 001939428
OP1
Trunk group 40
Trunk group 40
1 OP2
Trunk group 42
Prefix plan Trunk group 42
Prefix plan
Prefix ARS: 0
Prefix ARS: 0
N° discriminator: 4
N° discriminator: 4 2 3
Translator
Entity 4 Translator
Entity 4 ³ Discriminator
Discriminator selector ³ Discriminator
Discriminator selector 7: OP1ent4
Discriminator 04: 7 7: OP1ent4
Discriminator 04: 7 ³ Discriminator rule
³ Discriminator rule The PCX checks that calls
Called number: 00
Called number: 00 towards area 1are
Area: 1
Area: 1 authorized
ARS table: 0
ARS table: 0
³ ARS Table 0:
³ ARS Table 0:
route 1: trunk group 40


549

550
ARS

OBJECTIVE:
◆ To put into operation the ARS functionality
Alcatel OmniPCX Enterprise – ARS

551
Automatic Route Selection
Management
ARS prefix:
➨ /Translator
✦ /Prefix plan
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


552
Management
/Entities
➨ /Entity_discriminator_Selector
✦ consult-modify/entity number
Discriminator_00: 0
Discriminator_01: 0
Discriminator_02: 0
Discriminator_03: 0
Discriminator_04: 2
Discriminator_05: 0
Discriminator_06: 0
Discriminator_07: 0


553
Management
/Translator
➨ /External dialing plan
▼ /Dialing discriminator
✦ create
discriminator _id = 2
name = CENTRAL2000
▼ /Discriminator rules
✦ create
discriminator_Id: 2
Call number: 020103XX
Dialing area: 1
ARS route list number: 1
Schedule number: -1

Discriminator Nr.: enter the discriminator number (0..255),
Call Number : enter the initial digits of the authorized public numbers (up to 60 digits),
Dialing Area : 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.

554
Management
ARS route list definition:
▼ /Translator /Automatic Route Selection /ARS route list
ARS route list n°:

route n°: from 1 to 10
name:
trunk group:
Nb of digits to be removed:
Digits to add:
Dialing command table Id:
NPD identifier: 0
Route Quality: Speech

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: 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 dialing 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:

enter a dialing command table identifier (one per route), between 1 and 30. 0 indicates that no table is used,
NPD identifier:
along with the route type (Private or Public), this field is used to generate the caller number in a private or public
numbering plan,
Route Type: select the route type (Private or Public),
Quality: select the quality level offered by the route. The following levels are offered. Select the route type: private or public:
• Speech,Fax,Restricted digital information, Unrestricted digital information,Low Level Signaling Route: when an
attempt is made to set up a call via a route which offers this quality level, the call fails for an unspecified
reason. No signaling message indicates the reason, and a new attempt cannot be made on this route before
a time delay expires,Out of service.

555
Management
ARS time-based route list definition
➨ /Translator/Automatic Route Selection/ARS route list/timed

based route list
✦ create
route list id: 1
time based route list Id: from 1 to 8
✦ add
route number: from 1 to 10
waiting cost: -1
stopping limit: -1

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: enter the value of the waiting cost 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 value of the waiting cost threshold must be defined so as to be consistent with the running order defined in the time based route
list,
Stopping Cost Limit:enter the value of the stopping cost 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. In fact 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),
The value of the stopping cost threshold must be defined so as to be consistent with the running order defined in the time based route
list.

556
Management
User management
➨ /Users:
▼ directory number:
▼ public network COS:
Classes of service management
➨ /Classes of service
✦ Access COS
ARS privilege
night:
day:
mode 1:
mode 2:

ARS privilege : enter a number between 0 - 31 for the access COS required by the user. 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 higher than the route cost threshold

557
Management
System management
➨ /System
✦ ARS parameters
Route restriction:
Tone on seizure:

ARS Parameters
Route Restriction: (Yes/No - default No) enables additional barring restriction by comparing the cost threshold of the user with the
cost of the primary route defined for this user.
If the cost threshold of the user is considerably lower than the cost of the route, the call is rejected,
Tone on seizure: authorizes simulation of the public network dial tone after an ARS prefix has been dialed. This is used to make
ARS use identical to public trunk group seizure.

558
ARS

OBJECTIVE:
◆ To maintain the ARS

559
ARS
Maintenance
Maintenance tool to check the ARS settings: lookars
Tool access:
Console Login: mtcl

Password:xxxx
(1)xa000000> lookars <option>

available options:
=>lookars -h: for help
=>lookars i: Interactive mode to find the route used
(you can use there the 'help' command)
=>lookars r <route_list_nbr>: Search the route list with the number

passed in argument
=>lookars r all: Search all the route lists defined on the local node


560
ARS
Maintenance
Display of 1 ARS route list managed:

(1)xa000000> lookars r 1
====================================================================
| A R S R O U T E S L I S T No 1 |
--------------------------------------------------------------------
| ROUTES DEFINITIONS |
--------------------------------------------------------------------
|
| 1) trk_grp = 18 dialing_table = 0
| nb_deleted_digits = 0 inserted_digits =
| vpnCostLimit = 0
| idx_atm = -1
|
| --> trk_grp 18 local TG name: T2_Trunk state: FREE
| type: T2 variante: T2
| fais_suiv = 16 category = 0 nbjonc = 15
| vpnRate = 50 vpnCostLimit = 0
| Route usefull for: SPEECH
--------------------------------------------------------------------
|
...

End of the display of this ARS route list:
...
| vpnCostLimit = 0
| idx_atm = -1
|
| --> trk_grp 16 local TG name: T0_Trunk state: FREE
| type: T0 variante: T2
| fais_suiv = 11 category = 0 nbjonc = 6
--------------------------------------------------------------------
|
| vpnCostLimit = 0
| idx_atm = -1
|
| --> trk_grp 11 local TG name: NDDI_Trunk state: OOS
| type: BCA
| fais_suiv = -1 category = 0 nbjonc = 8
--------------------------------------------------------------------

561
ARS
Maintenance
Interactive mode
(1)xa000000> lookars i
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 : 20/03/2001
Time : 15:18
ARS Prefix : 0
Directory No: 3304
External No : 0256565656
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: 3304 Entity: 11 Discri Real Id: 0
| Route List No: 1 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
| Third route to try is route nb 3 stop = -1 wait = -1
====================================================================

More examples:
ARS Prefix : 0
Directory No: 3304
External No : 0123236565
Command: <return>
====================================================================
====================================================================
--------------------------------------------------------------------
====================================================================
ARS Prefix : 0
Directory No: 3304
External No : 0032323232/
Command: <return>
====================================================================
====================================================================
--------------------------------------------------------------------
====================================================================

562
ARS
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage ARS
MANAGEMENT
1. Manage ARS as follows:
IP Phone
Access category: 2
Entity: 1
Trunk group x0
x0
AT&T
British
Trunk group x2 Telecom
UA set
Access category: 3
Entity: 1

563
ARS
SIMPLE ARS
2. Manage the ARS prefix 0.
3. Realize the management of the Alcatel 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.
Remark: the barring is already managed and is working.
3.1 Manage in each real discriminator one ARS rout list number (for example 0 and 1)
vTranslator
vExternal numbering external scheme
vNumbering discriminator
3.2 Create the 2 ARS rout list
vTranslator
vAutomatic route selection
vARS route list
vARS route (declare T2 and T0 trunk groups)
vTine based route list (manage the list n°1)
4. Make the tests by using the “trkstat” command to display the used trunk group.

564
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
565
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
566
Attendant group

OBJECTIVE:
◆ To describe attendant group and its state
Alcatel OmniPCX Enterprise – Attendant group

567
Attendant group
Overview
The attendant group
Prefix: «Attendant group call»
Group 1
Physical directory number
Call distribution
Group index table

« Operator group call» Prefix:

Allows outside users ( N° DDI in this case 1a)and inhouse user to end up on call distribution table of the Operator group.
Physical directory N°:

No-dial number (EX: A000)
Informed in call distribution tables as routing1, routing2, routing3
Used in call distribution mechanism
Group Index:
Identifies group at system level (a group = an index)
Links call distribution elements (entity,OP group,op,CDT) at system management level
EX: group manager of entity.
Call distribution table:

Routes calls intended for group according to its call distribution status
maximum number of group: see commissioning procedure for version used in this training course

568
Attendant group
Overview
With a group call, all attendants are rung
Group call

REM: Call presentation can be generated on each Operator in group (Pcots). In this case each one will be rung according to
presentation defined in Pcots.

569
Attendant group
Overview
Attendant group’s position
➨ In service
▼ At least one Operator from the group is idle or busy
➨ Unplugged
▼ When the last Operator has been unplugged, the group is
unplugged
➨ Absent
▼ When the last Operator from the group goes absent, the group is
absent


570
Attendant group
Overview
Statistical call distribution on attendant group
OP1: 20s OP3: 10s

OP2: 25s
GROP waiting queue
Call 1 Call 2 Call 3 Call 4
Idle times counters:

- OP1: 20s
- OP2: 25s
- OP3: 10s

Remark: Automatic changeover from statistical to parallel Overview for a call when:
- nb 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
Personal OP call are taken account for idle time counter

571
Attendant group
Overview
Possibility of making traffic overflow between the operator

group
Calls overflow
call 4
Overflow
call 3
call 2 threshold
call 1
Mutual help
validated

Two cases possible:

Case 1:
Traffic overflow on group call with «Operator group call» prefix. The physical directory N° of group is informed under routing in the
CDT .
Overflow takes place once it is managed in the group
Case 2:
Traffic overflow on entity call with « entity call » prefix. The physical directory N° group is informed under routing in the entity ’s CDT.
Overflow takes place if it is managed at group level, but furthermore, it has just been authorized on entity level in the routing where
the group’s physical directory number has been placed.
In both of these cases, do not forget that a group operator will manually activate the mutual help (traffic overflow)

572
Attendant group
Overview
Call distribution table for the attendant group
group status Call distribution
Day Night M1 M2
Routing 1
Table Routing 2
routing
overflow Routing 3
Routing overflow N° Routing 4


573
Attendant group
Overview
Group’s Call distribution state is defined either
➨ By the group’s position
▼ in service =day
▼ unplugged = night
➨ Manually by an attendant of the group if service is

authorized
▼ Day
▼ Night
▼ Mode 1
▼ Mode 2

For manual modification by the operator, the service must be authorized in Management.

574
Attendants

OBJECTIVE:
◆ To describe A4035 / A4049/59 attendant consoles
Alcatel OmniPCX Enterprise – Attendants

575
Attendant set
Overview
The Attendant set
Prefix: «individual attendant call »
physical directory number

Alcatel 4049 or 4059 on PC
4035T set
Call distribution
attendant id table

«individual Attendant call » prefix:

External calls ( DID number in this case ) and internal calls are routed on the call distribution table of the Attendant.
It is also used to have Attendant name on the internal user’s set. A directory entry has to be created with the prefix.

Undialed number (EX: A100)
Given in call distribution tables as routing1, routing2, routing3
Used in call distribution mechanism
Group index:
Identifies the Attendant at system level (an Attendant = an index)
Links call distribution elements (entity,Attendant group,Attendant,CDT) at system management level.
EX: Attendant in the Attendant group
Call distribution table:

Enables routing of calls intended for Attendant terminal according to its call distribution status
Maximum number of Attendants: see commissioning procedure for the version used in this training course

576
Attendant set
Overview
Types of attendant terminals
➨ 4035 = 4035 extension set

➨ 4049 = PC screen + TA-PAC + multimedia keyboard
➨ 4059 = PC + TA-PAC + multimedia keyboard + 4059
software .
Functionality provided
➨ Telephone
➨ Access to a given management service
➨ Customized keyboard

TA-PAC = Terminal Adapter Professional Attendant Console

577
Attendant set
Overview
Access to services
➨ Customer management
➨ Charging
➨ System management
➨ Installation states
➨ Call distribution

Att. group status.: Night/Day/State 1/ State 2

Service cat.update
Connect.Category Update
Public Network Categ.Update
Charging Category Update
Cost center update
Like Manager Att.Group
System Date Update
System Time Update
Abbreviated Number Update
Sets and Dir.No.update
Accounting
Trunk Group Auto.Book/Remov.
Trunk Group Book/Remove
Traffic overflow
Users Facilities Update
Entity Status:NIGHT
Entity Status:DAY
Entity Status:MODE 1
Entity Status:MODE 2
Att.Set Routing Table
Att.Group Routing Table
Entity Routing Table
DECT sets registration
DECT permanent registr.
DECT sets installation

578
Attendant set
Overview
Customizing the keyboard
➨ Allows the role of programmable keys on the attendant’s

keypad to be defined
4035
Programmable keys

Number of programmable keys:
Operator set 4035:

Additional key boxes Maximum 60 keys.
2 types of modules 20 keys or 40 keys

579
Attendant set
Overview
Programmable key possible
➨ Calls presentation
➨ Directory number supervision
➨ Trunk or trunk group supervision
➨ Individual hold
➨ etc ...

Other possibilities and those mentioned are detailed in the Management section.

580
Attendant set
Overview
Calls presented (Pcots)
➨ Designed for each operator set
➨ Enables telephone traffic routed on the CDT to be divided

into several flows
➨ A flow is considered to be a traffic presentation class
➨ The traffic presentation class will be associated with one of

the operator’s programmable keys

Pcots: Presentation class of traffic ( Class of traffic presentation ).

581
Attendant set
Overview
Illustration
Phone
Presentation Call routing traffic
Classes
Entity Grop Attend. sets
DDI private call DDI private call

/ local entity 1 / local entity 2
DDI call DDI call Chained calls
No answer entity 1 No answer entity 2
entity call 1 entity call 2 Trunk circuit calls
Other all entities

Entity DDI public call: via public trunk with dialing.
Entity DDI call no answer: call by a set via a public or private trunk with dialing Set does not answer or is busy.
Private DDI call / entity internal call: entity call prefix made by a private trunk with dialing or by a set from the installation
Trunk circuit call all entities: call from a public or private trunk circuit without dialing
Chained call: Receives all calls chained by the Attendant
Others: Receives all calls routed towards an Attendant or group of Attendants which do not possess the PCOT corresponding to the
call.
Up to 8 traffic classes can be on the same key.

582
Attendant set
Overview
Priority over call presentations
➨ Priority over traffic classes is assigned by the system (in

Management)
➨ Within the same traffic presentation class
▼ A priority value for normal call

▼ A priority value for the the same call for emergency


583
Attendant set
Overview
Attendant set position
➨ Idle
▼ Attendant takes no action, neither phoning nor managing
➨ Busy
▼ Attendant is on line or carrying out management action
➨ Unplugged
▼ Handset disconnected
▼ Function has been activated by a key on terminal
➨ Absent
▼ Attendant at rest, does not answer for timer 76 (80 sec) , goes to
absent position


584
Attendant set
Overview
Ringing Attendant set
Call presented
Normal Urgent
30 s 80s t
Time out 141
Time out 76
idle position absent position

The type of ringing is defined when operator is created «Parameter: type of ringing»
Possible cases:
No ring
Normal ring
Delayed ring
Delayed ring with beep

585
Attendant set
Overview
Delayed ring
Call presented Normal Urgent
30 s 80s t
Time out 141
Time out Time out

140 142

Time out default values:

141 = 30 s
140 = 15 s
142 = 15 s

586
Attendant set
Overview
Delayed ring, with beep
Call presented Urgent

Normal
30 s 80s t
Time out 141
beep
Time out Time out

140 142


587
Attendant set
Overview
Pre Off Hook (ringing tone then incoming greeting guide)
Call Passing to
return Guide 110 conversation
Time out 102
Normal Urgent
30 s 80s t

The time out 102 is the default value 0 which means an indefinite length of time.

588
Attendant set
Overview
Attendant Call distribution table
group Call distribution state
Day Night M1 M2
Routing 1
Table Routing 2
routing
overflow Routing 3

The table development conditions are the same as those presented in the entity module

589
Attendant set
Overview
Attendant Call distribution state
➨ Identical to status of the group it belongs to
Attendant Call distribution state

=
Attendant group Call distribution state


590
Attendant set
Overview
Attendant:
➨ Calls between attendants are authorized

➨ Transfer after a conversation, between attendants , is
authorized
Waiting guides:
➨ Waiting guide for attendants (pre-off hook) can be

managed by each entity (Guide n°110 by default)


591
Attendant set
Overview
Attendant assistant on UA set

GROP PFX
ENTITy PFX
Waiting queue GROP

IIIII I
4035
Assistant key Start ringing threshold: 6

OP

RESTRICTIONS:
• The assistant set is multi-line set

• This functionality is only available for 4035
FUNCTIONALITIES:
• The start ringing threshold defines the calls number present in the waiting queue for the overflow on the attendant
assistant
• Many assistants in GROP

•The call is presented on the attendant assistant key, then on a multi-line key
•The attendant assistant key is also used to supervise the waiting calls
•Emulation of the attendant display

592
Attendant set
Overview
Waiting queue GROP

II
Set is
not
rung
4035
Assistant key StOP ringing threshold: 2

OP

FUNCTIONALITIES:
The stop ringing threshold defines the calls number of the waiting queue from which the assistant sets will not be rung.

593

594
Alcatel 4059

OBJECTIVE:
◆ To describe and manage the Alcatel 4059 attendant console
Alcatel OmniPCX Enterprise – Alcatel 4059

595
Alcatel 4059
Overview
The Alcatel 4059 includes
➨ A terminal adapter box remotely powered by the Alcatel

OmniPCX Enterprise
➨ A custom keyboard with PC compatibility and audio

functions
▼ It receives power supply from the terminal adapter
➨ A PC with its own standard VGA display

▼ Alcatel 4059 software has to be installed
➨ Connecting cables for the central unit

▼ MAC/PC: to exchange information between the Alcatel 4059
software and the terminal adapter
▼ Keyboard: to use custom keyboard with the PC


596
Alcatel 4059
Overview
Alcatel 4059 cabling

UA
connection
PC
Keyboard connection
PC TEL <-> PC COM1

Connection
Keyboard
connection


597
Alcatel 4059
Overview
Keyboard Audio keys Call handling

Function keys keys
Automatic answer Automatic

Night status indicators indicator
Microphone transfer indicator


598
Alcatel 4059
Overview
Audio keys
Microphone O/S Loudspeaker activation

Hands-free mode activation
Loudspeaker level adjustment

Remark:
This information is available in the console status area

599
Alcatel 4059
Overview
Call handling keys

Commute to 4059
Directory
Redial
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 makes it possible to switch immediately to the A4059 application If the A4059 or PC is out of
order, it offers the possibility of using the keyboard

600
Alcatel 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

601
Alcatel 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

602
Alcatel 4059
Overview
Supervision icons
Analog set or fax (green) Busy set with external

call (yellow)
Analog set in off hook
Hunt group
status (yellow)
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

603
Alcatel 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:

604
Alcatel 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


605
Alcatel 4059
Overview
Attendant group status modification


606
Alcatel 4059
Overview
Alcatel OmniPCX Enterprise management
➨ With "mgr" management tool
▼ Path: /Attendant/Attendant sets

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
New type of attendants:

- A4035T
- A4035T + PC: A4035+V24-MAC/PC+PC+A4059
- A4059MAC : TA-MAC+PC
V24 Extension: yes

MAC/PC: MAC/PC
MAC/PC with trace (debug)
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
It is possible to check the A4059 software version, to reset it and to download it with the maintenance commands

607
Alcatel 4059
Overview
PC software management
➨ Install the Alcatel 4059 MAC and the Alcatel 4059 busy
lamp field software on the PC
➨ Manage the ABCA link management on PC as follows:


608
Attendant group

OBJECTIVES:
◆ To manage attendant group
◆ To manage attendant group call distribution table

609
Attendant group
Management
Attendant group management
➨ /Attendant/ Attendants groups

▼ Physical directory Number:
▼ Attendant group id:
▼ Name


The physical directory n° is the "physical" number of the groups operator: it is only that used in management to direct calls to its
destination; It is not recommended for use by the user.
It has from 1 to 8 characters corresponding to the dialing keypad on (0 to 9, *, and #).
Characters A to D may also be used..
OP group ID:
This number associates the groups operator with »its » call distribution table , The number is used by operator group call prefixes
Name: name appears on display of correspondents inhouse on or private network
For other attributes see technical documentation- Notice operation Section 2 chapter 2 or Database management of operator group

610
Attendant group
Management
Call distribution table management

➨ /Attendant/Attendant group call distrib.
▼ Attendant group ID:
▼ Overflow routing number:
▼ Att. group status: Night
Routing 1
Routing 2
Routing 3
▼ Att. group status: Day
Routing 1
Routing 2
Routing 3
▼ Att. group status: Mode 1
Routing 1
Routing 2
Routing 3
▼ Att. group status: Mode 2
Routing 1
Routing 2
Routing 3

routing overflow n°: the routing overflow number corresponds to the call number of a user set; this number is used in reduced
service, as well as in routing overflow .
This routing overflow n° is common to all distribution states ( DAY , NIGHT , MODE1 , MODE2 ) and corresponds to the fourth
routing in the CDT
The following directory numbers cannot be informed - multi-line number, - set grouping number (as well as integrated directory
numbers in set groups), - SO set numbers
Routing overflow transfer:
if this number is given in another CDT as a routing overflow N° then the system will stop call distribution on it if the parameter is set to
No.
If this should be considered as a conventional routing overflow N° in this CDT then put yes
For other attributes, see the technical documentation - Notice operation Section 2 chapter 2 or Database management chapter
Operator group.

611
Attendant group
Management
Attendant group call prefix management
➨ /translator/prefix plan
▼ Number:
▼ Prefix meaning: Select «attendant group call»
▼ Info: <attendant group id>

attendant group id = index number of attendant group create on previous slide

612
Attendant group
Management
Statistical call distribution on attendant group
➨ System/Descend hierarchy/Other system param/Descend

hierarchy/Attendant parameters/Review modify
▼ Attendant group call Presentation:
✦ parallel
✦ statistic


613
Attendant group
Management
Traffic overflow management
➨ /Attendant/ Attendants groups/Review modify

▼ Physical Directory N°:
▼ Max nb of calls bef. overflow:
▼ Traffic Overflow Dir.No.
▼ Traffic overflow - Night:
▼ Traffic overflow - Day:
▼ Traffic overflow - Mode 1:
▼ Traffic overflow - Mode 2:

Max nb calls before overflow: Max number of calls contained in queue beyond which traffic will overflow on to the directory number
of traffic overflow (if the "Traffic overflow" service is activated by the Attendant).
Traffic overf. N°: The traffic overflow directory number is used if this service is activated by Attendant and if so, when the number of
calls is above the threshold (see previous attribute).
This number must be an Attendant group physical address or an Attendant physical address located on the same node

614
Attendant group
Management
Traffic overflow management ( next )
➨ /Attendant/Attendants set/Review modify

▼ Physical Directory No.:
▼ Services Access Rights
▼ Traffic overflow: authorized without control
➨ /Entities/Review modify
▼ Entity Number:
▼ Traffic overflow: authorized without control
➨ Do not forget to validate Overflow on attendant service key!

The traffic overflow parameter of the Attendant Set is taken into account for traffic overflow with a call by the « Attendant group call »
prefix
The traffic overflow parameter of the entity is taken into account for a traffic overflow with a call by the « Entity call » prefix

615

616
Attendant set

OBJECTIVES:
◆ To manage an attendant set
◆ To manage attendant set call distribution table
Alcatel OmniPCX Enterprise – Attendant set

617
Attendant set
Management
Attendant management
➨ /Attendant/Attendant sets/Create
▼ Physical directory Number:

▼ Attendant ID:
▼ Attendant group ID:
▼ Shelf address:
▼ Board address:
▼ Equipment address:
▼ Type of set:
▼ Entity Number:

Physical directory N°: "physical" number of the attendant groups. It is only used in management to route the calls (used in Call
Distribution tables) .
It has from 1 to 8 characters corresponding to the dialing keypad on (0 to 9, *, and #).
Characters A to D may also be used.
Attendant ID: This is the attendant’s reference number, enabling the attendant to be associated with a Call distribution table
It is also used by the ”Individual Attendant call” prefix
Attendant group ID: Attendants are assigned to one of the Attendant groups using this number.
An attendant MUST BELONG TO A GROUP.
Type of set : 4034 / Console 4048 (FBC -Flat Bed Console) 2 equipment / Console 4048 ) 4 equipment / set 4034 +PC (SBC -
Screen Bed Console)/ 4035 set / 4035 set +PC/ 4059 MAC / PAC / 4037 (4035 +TSC-IP)
Set type available on Alcatel OmniPCX Enterprise:
4035T -> UA set 4035
4059 MAC -> PC + 4059 software + Multimedia keyboard + TA connected on 4 UA equipment .
MAC 2 equipts -> PC + 4059 software + Multimedia keyboard connected on 2 UA equipment .
PAC -> PC screen + Multimedia keyboard + TA connected on 4 UA equipment
PAC 2 equipts -> PC screen + Multimedia keyboard + TA connected on 2 UA equipment
Entity N°: Assignment to an entity provides: installation number (ISDN) processing and use of abbreviated number list
For more details on call presentation keys refer to technical documentation - Notice operation section 2 chapter 2 or Database
management chapter Operator.

618
Attendant set
Management
Call distribution table management

➨ /Attendant/Attendant call distribution
▼ attendant ID:
▼ Overflow routing Number
▼ Attendant status: Night
Routing 1:
Routing 2:
Routing 3:
▼ Attendant status: Day
Routing 1:
Routing 2:
Routing 3:
▼ Attendant status: Mode 1
Routing 1:
Routing 2:
Routing 3:
▼ Attendant status: Mode 2
Routing 1:
Routing 2:
Routing 3:

For other attributes see the technical documentation - Notice operation Section 2 chapter 2 or database Management chapter
Operator.

619
Attendant set
Management
Individual attendant call prefix management

➨ /translator/prefix plan
▼ Number:
▼ Prefix meaning: Select «Individual attendant call»
▼ Prefix information: <attendant ID>
Display attendant’s name on correspondent’s set (local)

➨ /phone book
▼ Directory N°: < individual attendant call prefixN°>
▼ Alias: 0 if it is the first of names
▼ Name:
▼ First name:

Attendant ID -> index number of attendant ( see previous slide )

620
Attendant set
Management
Attendant’s timer management
➨ /System/Timer
▼ Timer number
✦ 140
✦ 141
✦ 142
✦ 76
✦ 102

For details on Attendant Timers (number + duration) see the technical documentation - Database management Chapter Timers.
Timers concerning Attendants: 28;32;33;43;102;140;141;142;144;76;165

621
Attendant set
Management
Attendant programmable keys management (customizing

the keypad)
➨ /Attendant/ Attendant set /Attendant keyboard

▼ Attendant Key number:
▼ Key type:
▼ Key label:
▼ Prefix:
▼ Prefix information:

Key type:
not assigned
Directory number supervision:A directory number existing in the system is associated to this key.
A supervision key of a directory number makes it possible to be informed of the status of an individual set by the display of an icon.
Abbreviated N° : an abb. number index is associated with this key
Individual Routing: instead of "release", Attendant can supervise routing by pressing this key
Network/Network Transfer: Attendant can connect 2 networks without taking transfer categories into account, simply by pressing
this key
Trunk group Supervision:A trunk group supervision key makes it possible to display the status of the trunk group (free or busy)
with an icon
O/S trunk supervision: When the system sees a trunk which is out of service, the icon of this key becomes steady.
Individual hold: Simple hold of any type of trunk
call presentation: this key can be used to present calls defined in the attribute "Attendant calls presentation" or the
attribute "Entity calls presentation"
Programmable: This key enables Attendant to program a call number herself.
Transfer with privilege: This key contains 2 sub-attributes for info: - an outgoing prefix, - a public network access category
The attendant can transfer a user if he belongs to this access public network category.

622
Attendant set
Management
Managing programmable keys on Attendant (Calls

presentation):
➨ /Attendant/ Attendant set /Attendant keyboard
▼ key number:
▼ Key type: <Call presentation>
▼ Att. calls pres. key:
✦ Options menu
▼ Entity calls pres. key:
✦ Entity N°:
✦ Trunk circuit call:
✦ DDI public call:
✦ DDI private call/ local:
✦ NO answer DDI call:

Attendant call presentation key:

trunk group NDDI call
public DDI all entities call
private DDI call / internal DDI all entities call
no answer DDI all entities call
these first 4 cases take entity call types assigned to no entity presentation key
private network call (internal call)

public network call
VIP
Recall
Att. Transfer
Common hold
Chained call
Charging Recall
Individual call
Others (Misc.) take attendant or entity call types, assigned to no presentation key.
for more details on call presentation keys see the technical documentation - Notice operation section 2 chapter 2 or database
management chapter Operator.

623
Attendant set
Management
➨ Attendant group
▼ Start ringing threshold: 20 calls (by default)
▼ Stop ringing threshold: 10 calls
➨ Users
▼ Programmable keys
✦ Attendant assistant
Ringing mode: no ring, short ring, long ring, short ring without overring, long
ring without overring
Attendant group: attendant group number (helped by this UA set)


624
Attendant Group

OBJECTIVE:
◆ To maintain the Attendant Group
Alcatel OmniPCX Enterprise – Attendant Group

625
Attendant group
Maintenance
Information on attendant group status

➨ Command: grpopestat <Id 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°
Display the attendant group’s CDT

➨ Command: cdtstat <Index N°>

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 OmniPCX Enterprise – Attendant Group

626
Attendant set

OBJECTIVE:
◆ To maintain attendant sets

627
Attendant set
Maintenance
Information on attendant state

➨ opstat
▼ Index N°
▼ OP name
▼ State ( unplugged… )
▼ Nbr urgent/normal calls
▼ etc..
Information on the attendant set’s CDT

➨ cdtstat <Index N°>
( under mtch )

cdtstat Command: 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 Operator set 2: cdtstat 2
Rem: cdtstat is available under mtch

628
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 attendant 2
Night forward ( 3x001)

629
Call distribution
Attendant name Physical directory number Individual attendant call prefix.

OPE1 A9x001 9x001
OPE2 A9x002 9x002
Attendant group name Physical directory number Attend group call prefix
GROP1 A9x51 9x051
2. Create 2 prefixes used to call directly each attendant set. Manage the call distribution table in
order to call the corresponding attendant according the installation status. Where are this
tables?
3. Do the test with the 2 prefixes and check the transfer between attendants..
4. Manage a prefix in order to call the attendant group.. For any installation’s status, in case of
attendant N°1 group call, the call will be routed like this:
- The 2 attendants ring simultaneously
Test also the statistical distribution
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 2 night forward sets 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.
10. Manage the set 3x001 as an attendant assistant. Do the test.

630
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
631
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
632
PARTICIPANT'S GUIDE
Part 3/3
REF. ENTPTE401US
01 03/06
GENERAL SUMMARY
Part 3

ENTP0418P01TEUS.............................................................................................................633
ENTP0418P02TEUS.............................................................................................................649
ENTP0418C01TEUS ............................................................................................................665
ENTP0418M01TEUS............................................................................................................677
ENTP0418H01TEUS ............................................................................................................681
21. DECT
ENTP0419P01TEUS.............................................................................................................685
ENTP0419P04TEUS.............................................................................................................693
ENTP0419C01TEUS ............................................................................................................699
ENTP0419C03TEUS ............................................................................................................703
ENTP0419C04TEUS ............................................................................................................707
ENTP0419M01TEUS............................................................................................................715
ENTP0419H02TEUS ............................................................................................................731

22. Twinset
ENTP0479P01TEUS.............................................................................................................735
ENTP0479C02TEUS ............................................................................................................745
ENTP0479H01TEUS ............................................................................................................749
23. Speed Dialing

ENTP0408P01TEUS.............................................................................................................753
ENTP0408C02TEUS ............................................................................................................761
ENTP0408H01TEUS ............................................................................................................765

ENTP0480P02TEUS.............................................................................................................769
ENTP0480C02TEUS ............................................................................................................787
ENTP0480H02TEUS ............................................................................................................797
25. Alcatel 4645

ENTP0432P01TEUS.............................................................................................................801
ENTP0432C01TEUS ............................................................................................................819
ENTP0432C02TEUS ............................................................................................................833
ENTP0432M01TEUS............................................................................................................837
ENTP0432H01TEUS ............................................................................................................845
26. MOXA V24/IP Box

ENTP0444P01TEUS.............................................................................................................849
ENTP0444C01TEUS ............................................................................................................857
ENTP0444M01TEUS............................................................................................................863
ENTP0444H01TEUS ............................................................................................................875

ENTP0411P04TEUS.............................................................................................................879
ENTP0411C02TEUS ............................................................................................................883
ENTP0411H02TEUS ............................................................................................................889

ENTP0431P01TEUS.............................................................................................................893
ENTP0431P06TEUS.............................................................................................................903
ENTP0431P07TEUS.............................................................................................................915
ENTP0431P08TEUS.............................................................................................................925
ENTP0421P01TEUS.............................................................................................................931
ENTP0431C06TEUS ............................................................................................................939
ENTP0431C08TEUS ............................................................................................................951
ENTP0431H08TEUS ............................................................................................................957

FEEDBACK SHEET
Alcatel University
CS 82802
FAX: (33) 2 98 14 36 36
DATE:


Entities

OBJECTIVES:
◆ To describe and setup a multi-entity configuration
◆ To describe the principles of an multi-entity configuration
Alcatel OmniPCX Enterprise – Entities

633
Entities
Overview
Entity
➨ Alcatel OmniPCX Enterprise logical subassembly
➨ Allows a large company to be divided into several

subassemblies
➨ Thus each one enjoys customized routing for its calls


634
Entities
Overview
Illustration: a single entity
Company X
Department 1 Department 2 Department 3
User_1 User_2 User-3 User_4 User_5 User_6
Entity 1

Entities 0 and 1 are created by default.

Users are assigned by default to entity 1.

635
Entities
Overview
The entity: ➨ Directory N°

➨ Users of installation
➨ IDSN installation N°
➨ changeover times
Department 1 ➨ Music on hold
➨ Abbreviated N°range
User_1 User_2 ➨ Trunk groups
➨ Waiting guide on
attendant
Entity_1 ➨ Discriminator selection
➨ Call distribution table
➨ Optional attendant
group manager

Directory N°:
corresponds to «Call entity prefix». In general the company or department n°
Ex: Call entity prefix: 3322
installation n° ISDN: 029814 & complementary installation N°: 3322
Users of installation:
Each set must be associated with an entity.
ISDN installation N°:
Informed in 2 parts in entity. The installation n° and the ancillary installation n°.
Ex:installation N° (ISDN): 029814
ancillary installation N°:3322
The installation n° will be used by DDI users in their ISDN calls to transmit the entire number (10 digits)
The installation n° + the ancillary installation N° for non-DDI users
Changeover times:
Makes it possible for the entity to change an installation’s status during the same day depending on requirements
Music hold:
See music hold chapter
Abbreviated N° groups
See abbreviated number chapter
Inbound no-dial trunk circuits
No-dial trunk circuits use the entity’s call distribution table to route calls
Call distribution Table
Enables calls intended for the entity (made using call entity prefix) to be routing according to a call distribution status
Manager Attendant group
The Manager group modifies the entity’s installation status. The entity follows the group status.

636
Entities
Overview
Entity Call distribution table
Entity Call distribution state
Day Night M1 M2
Routing 1
Table
Routing 2
routings
overflow Routing 3

CDT enables calls intended for the entity to be routed according to its Call distribution state .
Access Point to CDT: entity call prefix

637
Entity
Overview
Numbers accepted in a CDT
☞ Physical directory N°
☞ Sets
Day Night M1 M2 ☞ PBX Group
☞ Voice messaging
☞ Automated attendant
☞ network prefix
Routing overflow N°
☞ voice guide
☞ Alcatel OmniTouch
– Driver N°
– Agent N°


638
Entity
Overview
Entity state for the call distribution
➨ Defined by incoming call changeover times
▼ Day
▼ Night
▼ Mode 1
▼ Mode 2
▼ Attendant group


639
Entities
Overview
Routing overflow condition in a CDT
External call presented
Overflow
Routing 1
Attendant
Overflow on
Timer 76 No answer /Busy Routing 2
set
Trunk timer Routing 3
Answer

The same is true for the call distribution tables of entity, attendant group, Attendant.
Timer 76: Default time 80 seconds. Corresponds to Attendant going to absent position.
Trunk timer: Parameterised in the trunk category

By default
No answer: 30 seconds
Busy: 30 seconds

640
Entities
Overview
Internal call presented
Overflow
Routing 1
Attendant
Overflow on
Timer 76 No answer /Busy Routing 2
set
Timer 144 Routing 3
Answer

The same is true for call distribution tables of entity, attendant group, attendant.
Timer 76: Default time 80 seconds. Corresponds to attendant going into absent position.
Timer 144: Default value 15 seconds

641
Entities
Overview
Call presented
Immediate overflow
Routing 1
Group unplugged
Immediate overflow
Routing 2
Group absent
Routing 3
Answer

The same is true for call distribution tables of entity, attendant group and attendant.

642
Entities
Overview
Call presented
Immediate overflow
Routing 1
Att. unplugged
Immediate overflow
Routing 2
Att. absent
Routing 3
Answer

The same is true for call distribution tables of entity, attendant group and attendant.

643
Entities
Overview
Routing overflow condition in the CDT of an entity
External call presented
Overflow
Routing 1
ATT
Overflow
Timer 76 Routing 2
ATT
Timer
for overflow Timer 76 Routing 3
of entity
Answer

The entity overflow timer is parameterized in the entity.

It is only taken into account between the first and second routing.
It is only activated during an external call

644
Changeover times
Overview
Makes it possible for the entity to change the system state

during a given day depending on requirements
➨ For incoming calls

▼ Distribution of entity’s calls
➨ For outgoing calls

▼ Discrimination of entity’s users


645
Changeover times
Overview
4 time changeovers per day, from Monday to Sunday
For each changeover there are 5 possible states

➨ Day
➨ Night
➨ Mode 1
➨ Mode 2
➨ Attendant group
▼ The entity follows the state of the group assigned as attendant
manager group

Holidays are not taken into account by the system.

646
Changeover times
Overview
Principle
➨ Status: Day/Night/Mode 1/Mode 2
Attendant Services
Modifying entity status

Attendants
Day Night M1 M2 Idem GROP
changeover times Entity status

Management:State Day incoming calls
changeover times Entity status

Management:State Day outgoing calls

Note: Grop = attendant group
Attendants can modify entity status for incoming calls using attendant services if authorized.
This is only true if the attendant is the attendant group manager of the entity.

647
Changeover times
Overview
Principle
➨ status: Attendant group
Attendant Services
Modifying Group status Modifying entity status
Day Night M1 M2 Day Night M1 M2 Idem GROP
Attendant Entity status

incoming calls
Position of Group’s
Attendant status
Entity status
Outgoing calls

An attendant of a manager group can modify:

- group status
- entity status
In conclusion:
Attendants can modify the entity status using the Attendant services for incoming calls without modifying the group status.
This enables incoming calls and outgoing calls to be disassociated.

648
Calls distribution

OBJECTIVE:
◆ To describe the principles and components of calls distribution
Alcatel OmniPCX Enterprise – Calls distribution

649
Calls distribution
Overview
Single entity
➨ Same behavior for all
Company “Thomas Consulting”

Entity 1


650
Calls distribution
Overview
Several entities
➨ Specific behavior per department (entity)
Company “Thomas Consulting”
Entity1 Entity 2 Entity 3


651
Calls distribution
Overview
Each system entity can be associated a Directory Number

(most of the time “DDI number”) corresponding to the
Company or Department number
➨ If someone wants to call this Company or Department, it

has to use this number
➨ Then, it is necessary to put in place a «call routing» for the

different local internal users
▼ This is done via a Calls distribution Table linked to each Entity

To call an entity, an « Entity call » prefix has to be used (usually a DDI number)
This prefix allows to reach the Calls distribution table of the entity

652
Calls distribution
Overview
Calls distribution table (CDT)
➨ Each entity has its own Calls distribution table
➨ A prefix (Entity Call) allows to access to this table
➨ 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 an other can be done

automatically by the changeover time management or by an
action from an attendant associated to this entity


653
Calls distribution
Overview
Calls distribution elements
Calls distribution table Is linked with:

Day Night Mode1 Mode2
- an entity
--------------------- Routing 1 --------------------
--------------------- Routing 2 --------------------
--------------------- Routing 3 --------------------
Overflow routing number
It is accessed by a prefix:
Contains:
- directory number* (mono/multi-line set)
- entity call
- attendant set physical number
- attendant group physical number - general attendant call
- PBX group
- Speed dialed number
- voice guide
Prefix Calls distribution Table used
- automated attendant
- CCd agent Entity Call CDT of the Entity pointed by the prefix
Attendant Call CDT of the Entity of the calling user

* If we use a set for the overflow routing number, it has to be a mono-line

654
Calls distribution
Overview
Caller Identification
➨ 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 “additional system number” is
transmitted after the “system number”
✦ If the subscriber is DDI: it is the station number of the DDI caller which is
transmitted instead of this “additional system number” after the “system
number”


655
Calls distribution
Overview
Calls distribution Table (CDT)
➨ Contains different terminals which can handle calls
➨ Four different status are associated to this table (Day, Night,

Mode1, Mode2)
➨ For each status, three specific (successive) overflow numbers

are possible
➨ A fourth overflow number is common to the four status


656
Calls distribution
Overview
Status of the distribution
➨ A status (mode: day, night…) is given to each Entity,

Attendant, Attendant group
▼ The status of the Entity can change automatically*, by using the

changeover-time management
▼ An attendant, having the rights of modification, can modify the status

of the Entity
▼ The status of an Attendant Group depends on the status of its

attendant**.
▼ The status of the attendant are: Day (plugged), Night (unplugged)

* The management of the changeover-time allows to link some periods to a status

example: from 0h to 8h: night
from 8h to 12: day
from 12h to 13h30 mode1
from 13h30 to 18h day
from 18h to 24h00 night
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)
** If the last Attendant (in service) of an Attendant Group switches in night mode, automatically, the Attendant Group switches in night
status

657
Calls distribution
Overview
Call Routing
➨ The call routing is done in the CDT (pointed by the prefix)
➨ According to the distribution status, the call is routed

towards the routing number associated to this status in the
predefined Calls distribution table
➨ 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,
and so on…


658
Calls distribution
Overview
Local call
Attendant call prefix Check entity in user

Entity state
Distribution
status?
Calls distribution table

Attendant Group Routing 1 --------------------

No answer/ Busy
--------------------- Routing 2 --------------------
No answer/ Busy
--------------------- Routing 3 --------------------
No answer/ Busy Overflow routing number


659
Calls distribution
Overview
Incoming call
Public DID Entity

Operator call Prefix
Entity state
Distribution
status?
Calls distribution table

Attendant Group Routing 1 --------------------

No answer/ Busy
--------------------- Routing 2 --------------------
No answer/ Busy
--------------------- Routing 3 --------------------
No answer/ Busy Overflow routing number


660
Calls distribution
Overview
Optional attendant group manager
➨ This attendant group number has to 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 attendants 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 ranges of the speed dialing
✦ station and directory number


661
Calls distribution
Overview
Changeover time
➨ This feature allows to split a day in 4 (max) different

periods. Each period can correspond to a specific status of
the company (opening hours, midday break, night hours…)
➨ The entity switches automatically from a status to an other
➨ 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”)


662
Calls distribution
Overview
Music on hold
➨ It is the tone (or voice guide) broadcast when a user from

this entity put someone on hold
Attendant waiting guide
➨ This concerns the voice guide broadcast during an external

call overflowing on no answer by the attendant (by default:
voice guide 110)


663
Calls distribution
Overview
Installation users
➨ All users are linked to an entity
➨ For all calls, the user can use the parameters linked to the
entity previously described
No-dial trunk circuits
➨ An incoming call on a no-dial trunk circuit (NDDI trunk

groups) is routed in function of the entity’s «Distribution des
Appels» table content


664
Calls distribution
PROCEDURE
Calls distribution
OBJECTIVES
- To learn how to manage with mgr
- Call distribution is the process whereby the PABX finds the final destination for a call, according
to the call characteristics (origin, type, etc.) and installation status (Day, night).
REFERENCE
- System Technical Documentation
OVERVIEW
Call distribution is implemented for certain PABX calls depending on the initial called party. It carries
out a routing function: choice of call destination according to the initial called party. Furthermore, it
handles the priorities between the different calls present at a given moment and is used to present
the calls according to their specific characteristics.
The three types of call (depending on the initial called party) defined are:
- individual attendant calls,
- attendant group calls,
- entity calls.
Each of these call types has a corresponding numbering plan function: a call prefix.

665
Calls distribution
PROCEDURE
1. Attendant group management
1.1 Attendant group creation

mtcl
Path Attendant / Attendants Group
Action Create
Parameters Physical Directory No.: A100
Attendant Group ID: 1
Name: GROP_1
Max No. Of Calls Bef.Overfl.: 5 [put the value that you
want]
Traffic Overflow Dir.No.
Traffic overflow: NIGHT: --------
Traffic overflow: DAY: A200 [e.g.]
Traffic overflow: MODE 1: --------
Traffic overflow: MODE 2: --------
Attendant assistant thresholds

Start Ringing Threshold: 20 [put the value that you want]
Stop Ringing Threshold: 10 [put the value that you want]
No display Threshold on 4059 list: 6
The attendants groups managed as overflow numbers must be created before.

666
Calls distribution
1.2 Attendant group call distribution table management

Mtcl
Path Attendant / Attendant Group Call Distrib.
Parameters Attendant Group ID: 1
Overflow Routing No.: 3401 [e.g.]

Att.Group Status: NIGHT
Routing 1: A200 [e.g.]
Routing 3: --------
Att.Group Status: DAY
Routing 1: A100
Routing 3: --------
Att.Group Status: MODE 1
Routing 3: --------
Att.Group Status: MODE 2
Routing 2: --------
Routing 3: --------
The numbers specified as routing numbers must be objects ( attendant groups, attendant
sets, sets, voice guides, ….) existing, they must be created before.

667
Calls distribution
2. Entities management
2.1 Create or modify an entity

Mtcl
Path Entities
Action Create or Review/Modify
Parameters Entity Number: 1 [e.g.]
Name: Training [e.g.]
Attendant Group Manager: 1 [e.g.]
Traffic Overflow: Allowed with no control [e.g.]
Installation No. (ISDN): 29814 [e.g.]
Supplement.Install.No. (ISDN): 3000 [e.g.]
Auto. Locking: 0
Voice Mail Box No.for attendt: 3111
Call Distribution
Overflow Routing No.: 3010 [e.g., must existing]
1st Night Routing: A200 [e.g., must existing]
2nd Night Routing: --------
3nd Night Routing: --------
1st Day Routing: A100 [e.g., must existing]
2nd Day Routing: A200 [e.g., must existing]
3nd Day Routing: --------
1st MODE 1 Routing: --------
2nd MODE 1 Routing: --------
1st MODE 2 Routing: --------

668
Calls distribution
Voice Guides
Waiting Guide: 2
Attendant Waiting Guide: 110 [modify by the guide number that you
need]
Entity Number:
Select an unallocated number between 1 and 255.
Name:
This is displayed on the set display of the correspondents and is limited to 16 characters
maximum.
Attendant Group Manager:
Enter a number corresponding to the attendant group administrating the entity.
Installation No (ISDN):
Enter the root for the company numbers, initial digits of corporate repertory numbers
preceding DDI numbers.
Supplement Install No. (ISDN):
Enter the default MCDU to send if the set making the call is not DDI.
Calls Distribution
Overflow Routing No.:
Enter the call number of a set (except multilines, set group, S0 set) to be used in reduced
service or routing overflow. This number can be managed by administrator group attendants.
Routing number:
For each status of the ATT group (Night, Day, Status1, Status2), complete the list of 3 routing
numbers (Routing 1, 2, 3).
It is not mandatory to complete each number.
Within the same status, numbers must be entered in increasing order (you cannot enter routing
number 2 if number 1 has not already been entered).
Attendant Waiting guide:
when there is a call on the entity call prefix, it is the played guide if the timer 102 has been
(see step6). By default it is the guide 110.

669
Calls distribution
2.2 Entity incoming state hours management

Mtcl
Path Entities/Entity Incoming State Hours
Parameters Entity Number: 1
Day: Monday
Changeover 1
Hour: 24 [must not be modified]
Minute: 0 [must not be modified]
Status: Night [e.g.]
Changeover 2
Hour: 7 [e.g.]
Minute: 30 [e.g.]
Status: Day [e.g.]
Changeover 3
Hour: 17 [e.g.]
Minute: 0 [e.g.]
Status: Mode 1 [e.g.]
Changeover 4
Hour: 19 [e.g.]
Minute: 0 e.g.]
Status: Night [e.g.]
The management must be done for all days of the week:: monday, tuesday, wednesday,
thursday, Friday, saturday, sunday
States: 5 possibilities: Day, Night, Mode 1, Mode 2 , Attendant Group (follows the attendant
group state)

670
Calls distribution
3. Attendant sets management
3.1 Attendant set(s) creation

mtcl
Path Opératrice / Attendant sets
Action Create
Parameters Physical Directory No.: A101 [e.g.]
Attendant ID: 1 [e.g.]
Attendant Group ID: 1 [e.g.]
Shelf Address: 3 [e.g.]
Board Address: 2 [e.g.]
Equipment Address: 6 [e.g.]
Set Type: 4059 MAC [e.g.]
Entity Number: 1 [e.g.]
Add On Module 1: None
External Alphanumeric Keyboard: None
Internal Alphanum.Keyboard: English
Secret Code: ****

Confirm: ****
Physical Directory No.: Enter the attendant directory number. It is used in management
to route calls to the destination.
Attendant ID: Enter the attendant reference number.
Attendant Group ID: Enter the number of the attendant group to which this set is
attached. (-1: no attendant group).
Warning: An attendant group must be defined before any attendant sets are declared.
Set Type: Select:
- 4035T: used for an attendant set.
- PAC 2 equipt: used for the 4049 attendant console.
- 4059 MAC: used for the Alcatel 4059 MAC application.
Warning: For the 4049 and 4059 consoles, equipment number must be a mutliple of 2
(0, 2, 6, etc.).

671
Calls distribution
Parameters Services Access Rights

672
Calls distribution
Cost Center ID: 1 [e.g.]

Cost Center Name: Training [e.g.]
Charging COS: Justified
Public Network COS: 2 [e.g.]
Call Restriction COS: 0
Applicable Restriction COS: 0
Language ID: 1
Ringing: Normal Ringing

Automatic Transfer: NO
Tone Presence: NO
ISDN Subscriber: YES
Access Code to UUS messages: YES
Incidents Teleservice: NO
Caller COS: 4
VSI Transparency: NO
Inter-Company Calling Right: False
Implicit Priority
Activation mode: 0
Cost Center ID:

Enter the number of the cost centre used for attendant call charging (accounting) records.
Caution: The cost centre must have been previously declared.
Cost Center Name:
Enter the name of the cost centre corresponding to the cost centre index. It is used to emit
charging (accounting) records.
Public Network COS:
Enter a public network access COS number.

673
Calls distribution
3.2 Attendant call distribution table management

mtcl
Path Attendant /Attendant Call Distribution
Parameters Attendant ID: 1 [Attendant ID created in the previous step (3.1) ]
Overflow Routing No.: 3401 [e.g.]
Att.Status: NIGHT
Routing 3: --------
Att.Status: DAY
Routing 1: A101
Att.Status: MODE 1
Routing 3: --------
Att.Status: MODE 2
Routing 2: --------
Routing 3: --------
The numbers specified as routing numbers must be objects ( attendant groups, attendant
sets, sets, voice guides, ….) existing, they must be created before.
Remark: For each status (Night, Day, Status1, Status2), complete the list of 3 routing
numbers (Routing 1, 2, 3). It is not mandatory to complete each number.
Within the same status, numbers must be entered in increasing order (you cannot enter
routing number 2 if number 1 has not already been entered).

674
Calls distribution
4. Prefixes creation
mtcl
Path Translator / Prefix Plan
Parameters Number: 9
Prefix Meaning: Attendant Call

Parameters Number: 3000 [e.g.]
Prefix Meaning: Entity Call
Prefix Information: 1 [e.g.]
Prefix Information: it is the entity number. A call on this prefix will be routed int eh entity
C.D.T.
Prefix Meaning: Attendant Group Call
Prefix Information: it is the attendant group ID. A call on this prefix will be routed in the
attendant group C.D.T.
Prefix Meaning: Individ.Attendant Call
Prefix Information: it is the attendant ID. A call on this prefix will be routed in the
attendant C.D.T.

675
Calls distribution
5. Attendant alias creation in the phone book

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.
mtcl
Path Phone Book
Action Create
Parameters Directory Number: 3101 [Individ.Attendant Call prefix created in the
setp 4]
Alias No.: 255
Directory name: Training OP 1
Directory First Name: July
Phone Book Type: Users
Can be Called/Dialed By Name: YES
6. Timer 102 modification

To play the voice guide specified in the entity (by default, it is the guide number 110), the 102
timer value must be modified.
mtcl
Path System/Timers/102
Parameters Timer No.: 102
Timer units: 30 [e.g.]
Timer units: ‘0’ by default, the guide doesn’t start. Enter an integer value. The adjustment
of the timers is made by number of units of 100 ms.

676
Entities

OBJECTIVES:
◆ To describe and setup a multi-entity configuration
◆ To maintain a multi-entity configuration

677
Entities
Maintenance
Displaying entity parameters

➨ Command: entitystat <N°entity>
▼ Outgoing call state
▼ Incoming call state
▼ Manager group
▼ Installation N°
Locating «entity call» prefix

➨ Command: ednump
▼ Parameter: dir,mean
Displaying the entity’s CDT

➨ Command: cdtstat <N° identification>

Ednump dir: N° of prefix

mean: prefix meaning
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
example: To have the configuration of the CDT of entity 1: cdtstat 161

678
Changeover Times
Maintenance
Displaying entity’s changeover times parameters
➨ Command: entitystat <N°entity> -b
▼ Entity’s parameters
▼ Outbound time table
▼ Inbound time table

Option -b of entitystat provides time tables for outgoing and incoming calls.

679

680
Entities
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to modify the existing entity in one system
MANAGEMENT
1. Modify the entity 1x as follow:

1.1 Entity 1x: Name: Alcatel
Installation number: 02SC1
Supplementary installation number: 3X200
Overflow Routing set: 3X001
Entity call: 3X200
Attendant call: 9
2. The Entity status follows the attendant group 1 status.
3. When the entity is in status 1 or status 2 the attendant group 2 will insure the call distribution.
When the entity is in night position the extension set 3x005 will be the night service set.

681
Entities
4. We decide to improve the management:

4.1 The status of the entity x1 doesn’t follow the attendant status , but a time table:
Open days:
00-00 to 08-00 -> Entity status: Night
08-00 to 12-00 -> Entity status: Day
12-00 to 13-00 -> Entity status: Mode 1, The incoming calls are routed to the night
service set .
13-00 to 18-00 -> Entity status: Day
After18-00 -> Entity status: Night, The users of each entity are automatically locked.
Week end days: Entity status: Night
4.2 During the nights all the outgoing calls are forbidden.

682
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
683
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
684
Mobility DECT

Alcatel OmniPCX Enterprise - Mobility DECT

685
DECT overview
Standard
DECT
➨ Digital Enhanced Cordless Telecommunication
➨ Standard published by ETSI

▼ European Telecommunication Standard Institute
Management protocol about set PABX exchanges
DECT


686
DECT overview
Elements
Four elements are mandatory for the mobility
1 ➨ PABX
2 ➨ Base stations (IBS or RBS)
3 ➨ DECT Handset (GAP, GAP+ and UA handset)
2 3
Base station DECT Handset

1 PABX


687
DECT overview
Principle
Cell
Multi-Cell
Base stations
Coverage by base stations
Multiple cells management
12 simultaneous calls per RBS

➨ 11 normally + 1 in case of exceptional traffic peak


688
DECT overview
Principle (next)
3 or 6 simultaneous calls per IBS
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)


689
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.


690
DECT overview
PARI number
➨ Identifying the PABX
PARK number
➨ Allowing the set to recognize the PABX
RPN number
➨ Identifying the base station
IPUIN number
➨ Identifying the handset


691
DECT overview
IPUIO number
➨ Identifying the handset in case of roaming in a PABX
network
PLI number
➨ Binary elements analyzed in the received PARI number in
network configuration


692
Mobility DECT sets

Alcatel OmniPCX Enterprise - Mobility DECT sets

693
DECT sets
Alcatel Handsets
Mobile 100 handset (4G)
• Major characteristics:
- GAP and GAP+ reliant handset

- Headset connection
- Navigator
- Battery: NiMh (Loading time: 300 min)
- Autonomy: 13h in communication and 120h
in idle state


694
DECT sets
Alcatel Handsets
Mobile 200 handset (4G)
- GAP and AGAP reliant handset

- Navigator
- Back-enlighten keypads and display
- Battery: LiIon (loading time: 150 min)
in idle state


695
DECT sets
Alcatel Handsets
Mobile 200 Ex handset (4G)
- GAP and AGAP reliant handset

- Ex standard compatible for Explosive
environment
- Navigator
- Back-enlighten keypad and display
- Battery: LiIon (Loading time: 150 min)
in idle state


696
DECT sets
Alcatel Handsets
Alcatel Mobile 100/200 Chargers
Desktop
Wired charger charger
Bi-position desktop
charger


697
DECT sets
Ascom set
ASCOM DECT for industrial environment: Ascom 9d24
➨ It’s an handset with an alarm button
➨ Only with the Crystal hardware
➨ GAP+ protocol
▼ Dial by name
▼ Automatic off hook
▼ Guide services
▼ Message signaling
▼ Mini–messaging and alarms
consultation


698
DECT Configuration (Mono-ACT, Mono-PARI
PROCEDURE
DECT Configuration (Mono-ACT, Mono-PARI)
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

699
PROCEDURE
1. IBS configuration
Application mgr Tab
Path /PWT/DECT system
Action Select “Review/modify” and press “enter”
Action On the next window, press “enter” and “Ctrl v” to validate
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

700

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 the shelf number the Up and Down arrows and press “enter”
Result Shelf Address : 3
Shelf Type + Media Gateway Small

Name : --------------------
Virtual crystal + NO
Pari Number + Pari IBS
Shelf role + Main (Master)
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”
Board Address : 1
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

701

702
PROCEDURE
DECT Configuration
(Mono-ACT, Mono-PARI)
OBJECTIVE
- To learn how to manage a RBS installation
OVERVIEW
The purpose of this procedure is to explain you how to put in service a DECT configuration RBS.
The first step is to manage the PARI number RBS, then to manage the hardware (boards, base
stations).

703
PROCEDURE
1. RBS configuration
Application mgr Tab
Path /PWT/DECT system
Radio base type + RBS

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 “RBS “ in the Radio base type field and “Ctrl v” to validate
Path /PWT/DECT system/RBS system:

704

Action Instance (reserved) : 1
Inter-ACT Handoff or DTM Synchro + Yes

Flag External Handoff + NO
Base station busy trigger : 8
Number of PARI : 1
Remark Select yes if the DECT synchronization is generated by the UBAC0 component
of the DECT8 board, used in DTM mode
Path /PWT/DECT system/RBS system/PARI
PARI Number : 0
PARI Value : 1000567300

Area type + 1 Area of 256 RFP
Reserved + YES
Action Enter the PARI numbering the Paris value field and “Ctrl v“ to validate
Path /Shelf
Action Select the shelf number the Up and Down arrows and press “enter”
Shelf Type + ACT-28 Interfaces

Name : --------------------
Virtual crystal + NO
Pari Number + PARI 0
Shelf role + Main (Master)
Law + Default
Reference + NO
Action Enter PARI 0 in the Pari number field end press “Ctrl v” to validate
Remark The PARI 0 corresponds to the PARI Number created above
Path /Shelf/Board
Board Address : 8
Interface Type + DECT8
Serial number : --------------
Action Choose the DECT8 for Interface Type and “Ctrl v”
Country Protocol Type + Default
Result PWT/DECT Location area number : 255
Board with DTM + False
Incidents Teleservice + YES

705
Action Select the presence or not of the DTM daughterboard in the board
Path /Shelf/Board/ RFP
Action Select the RBS station connected to the board created before and press “enter"
Board Address : 8
RFP number : 0
Base Station Location : Corid-A

Administrative State + RFP_INS
Operational State + RFP_OOS
Base in noisy audio environment + NO
Action Enter a name to define the where is the base station
Remark - Administrative state: This parameter allows you to put a base station in
service or out of service , three different states:
RF_OOS: Base station out of order
RF_INS: Base station in service
RF_FROZEN: Base station will be out of order after the release of the last
communication done on the base station
- Operational State: information about the real status of the base station
Action Check these parameters according to the configuration and ”Ctrl v” to
validate

706
PROCEDURE
DECT Configuration
(Mono-ACT, Mono-PARI)
OBJECTIVE
- To learn how to install mobile 100/200 and TSC-DECT
OVERVIEW
The purpose of this procedure is to know the way for the installation of the Mobile 100/200 and the
TSC-DECT.

707
PROCEDURE
Management of DECT users

1. Management of mobile 100/200
1.1 Creation of users
Application mgr Tab
Path Users
Entry Number: (For example: 31020)
Name: Dect1
Shelf address: 255
Board 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 100/200/200ex
Remark If the mobile phone is new one, when you press the start button you access
directly on the installation menu, else you need to follow the next procedure.
Action Switch on the handset by a long simultaneous press on the “ON/OFF” key
and the two management call keys (color keys)
Select with the joystick: 4.EEPROM Reset and press OK
Result SYSTEM 1
Auto install?
Action Press OK
Result Launch Subscription?
Action OK
Result SYSTEM 1
Subscription Running…
Remark During this time it’s necessary to make some management under mtcl, for this
follow the procedure in the next chapter (1.2.2)

708
1.2.2 Registration command

Login mtcl
Command dectinston 31020
Result Choice of a specific base station (Y/N - default is N)?
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
Result GAP characteristics
_______________________________________________________
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

709
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

710
2. Management of TSC DECT users
2.1 Creation of users

Application mgr Tab
Entry Number: (For example: 31020)
Name: Dect1
Shelf address: 255
Board address: 255
Set type: 4036
Remark The different set types are:
4036 (4035 & TSC DECT)
4021 (4020 & TSC DECT)
4010 & TSC DECT
4004 & TSC DECT
2.2 Installation of the TSC DECT set
2.2.1 Management on the TSC DECT set

On the TSC DECT Tab
Remark If the TSC DECT is new one, when you connect the power supply you start the
installation process, if else you need to follow the next procedure.
Action Powered the TSC DECT and enter the next sequence *#*86734#*#
Remark If the flashing LED sequence is 1s ON, 0.2s OFF, the TSC DECT is reinitialized
and ready for installation
During this time it’s necessary to make some management under mtcl, for this
follow the procedure in the next chapter (2.2.2)

711
2.2.2 Management on the call server

Login mtcl
Command dectinston 31020
Result Choice of a specific base station (Y/N - default is N)?
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
Result GAP characteristics
_______________________________________________________
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 agree press y +enter to
start the registration

712
Action 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
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

713

714
DECT System

OBJECTIVE:
◆ To use the DECT maintenance commands
Alcatel OmniPCX Enterprise –DECT System

715
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)


716
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 |
-------------------------------------------------------------------------


717
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;


718
DECT System
Commands: Outserv/
Outserv/inserv and termstat
IBS: Reset base stations
➨ outserv / inserv n <N°eqt>
➨ termstat


719
DECT System
Command: infocs
RBS: Synchronization
➨ infocs
| N_CR | N_CPL | TYPE | N_ACCES | PRIO | SYNC_CLOCK | TG/LK |

+--------------------------------------------------------------------+
| 1 | 3 | PRA T2 | 0 | 200 | SYNCHRO | TG:18
| 1 | 7 | BRA 4 | 0 | 201 | NOT_SYNCHRO | TG:15
+---------------------------------------------------------------------+
Clock
+========= Synchro DECT ====================+ synchronization
+----------------------------------------------------------------+
| N_CR | N_CPL | TYPE | DECT_CLOCK | Depending Crystals |
+----------------------------------------------------------------+
| 3 | 3 | DECT8 | DTM SYNCHRO |
+----------------------------------------------------------------+
DECT frame
synchronization

synchronization:
The base station synchronization is made with:
➨The clock synchronization , i.e. the binary synchronization, is realized by the board generating the most precise clock:
➊T2 board, connected to the public network
➋T0 board, if there’s a permanent logical link….
➨The DECT frame synchronization is realized by a DECT board

This synchronization is used for emission and reception of DECT frame from and to DECT sets
infocs COMMAND
Shows the synchronization status in the Alcatel OmniPCX Enterprise.
Status:
SYNCHRO: synchronizing equipment in the Alcatel OmniPCX Enterprise
DTM_SYNCHRO: synchronizing DTM for DECT equipment
POT_SYNCHRO: Equipment waiting to synchronize the system
NOT SYNCHRO: not synchronizing equipment in the Alcatel OmniPCX Enterprise
The synchronization priority of each board is managed in the board parameters of the database (with mgr or Alcatel Expert Tool)

720
DECT System
Command: cplstat
RBS: Status of a DECT board
➨ cplstat <act> <cpl>
(1)xa001001> cplstat 3 3
---------------- DECT COUPLER CURRENT STATE ---------------
CRYSTAL : 3
DECT COUPLER : 3
Logic coupler type : CPL_DECT (33);

MAO coupler type : DECT8 ;
Ghost equipement nbr : 5210 ;
Radio Coupler nbr : 0 and 1
Location Area nbr : 0
Board with DTM : 1
Number of RFP : 8

This command gives the status of a coupler, its ADPCMs and the base stations that are connected to it.

721
DECT System
Command: cplstat
RBS: Status of the base stations of a DECT board
➨ cplstat <act> <cpl> ( continued )

+-----+--------------+-----------+-----------+
| RFP | Localization | Adm State | Ope State |
+-----+--------------+-----------+-----------+
| 0 | stairs | INS | INS |
+-----+--------------+-----------+-----------+
| 1 | corridor | INS | INS |
+-----+--------------+-----------+-----------+
| 2 | classroo | INS | INS |
+-----+--------------+-----------+-----------+
| 3 | | INS | OOS |
+-----+--------------+-----------+-----------+
| 4 | | INS | OOS |
+-----+--------------+-----------+-----------+
| 5 | | INS | OOS |
+-----+--------------+-----------+-----------+
| 6 | | INS | OOS |
+-----+--------------+-----------+-----------+
| 7 | | INS | OOS |
+-----+--------------+-----------+-----------+
Coupler state: IN SERVICE;


722
DECT System
Command: cplstat
RBS: Status of the base stations of a DECT board
➨ cplstat <act> <cpl> ( continued )
--------- BASE STATIONS ------------------------------------------

DECT BS: 0 RPN = 80 NEQT:0021 STATE: IN SERVICE CALLS: 2
DECT BS: 3 RPN = 83 NEQT:0024 STATE: OUT OF SERVICE
------------- ADPCM RESSOURCES ------------------------------------
------- DSP: 0 Neqt = 0017 -----
---DTM present---
------- DSP: 1 Neqt = 0018 -----
ADPCM CHANNEL: 01 STATE: NOT USED
ADPCM CHANNEL: 02 STATE: FREE
...


723
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

724
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)…

725
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 )

726
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 |
| | | | | |
+----------+-----------+-----------+-----------------+-------------------------+


727
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.

728
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:
CTM shells for internal visitor handsets:
Total internal visitors handsets = 1
================================================================================
External visitor handsets:
CTM shells for external visitor handsets:
Total external visitors handsets = 1
================================================================================
* Set in Analog Add-On configuration
================================================================================


729

730
Management of a DECT installation (RBS or IBS)
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage a DECT installation (RBS or IBS)
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 equipement
1.4. Connect the IBS on this equipement. 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.
2. Management on RBS solution (Crystal hardware only)
2.1. Select the radio base station type: RBS
2.2. Manage the PARI number 1000044yyx0 and assign it to the shelf.
note: yy = room number
x = node number
2.3. Create a DECT8 board with DTM
2.4. Manage ta base station on this board

731
Management of a DECT installation (RBS or IBS)
2.5. Connect the RBS on this equipement. Check the state of the base station after a
moment.
2.6. Create the DECT sets 3x070 and 3x071. Make the registration. Check the good
working.

732
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
733
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
734
Twin set

OBJECTIVE:
◆ To describe the twin set feature
Alcatel OmniPCX Enterprise – Twin set

735
Twin set
Overview
Logical association between a desktop (main) set and a

Cordless (secondary) set
Tandem
3000
Main Secondary
3000 3100
Tandem based on the main set directory number

SETS CHARACTERISTICS
●The main set must be a desktop (wired set).
●The second set can be another desktop.
●Both sets must belong to the same node.
●Both sets must be multiline.
●The directory number of the tandem is the directory number of the desktop set main line.
●They can’t be:
ÁCD or CCdistribution set,
áttendant set,
´booth, room,...
´belong to a PBX.

736
Twin set
Overview
Call handling
3000
3000
3000 3100
3000
3100
3000 3100

CALL HANDLING.
The both sets ring if a call is presented on the main line or the secondary lines of the main set (desktop).
The both sets can answer to the call.
The tandem is busy when all the lines of the main set are busy.
The secondary set is busy when all its lines are busy. When one of these lines becomes free again a waiting call of the main set is
presented on it.

737
Twin set
Overview
Call for a private line
The caller dials the number 3333
3000
On the handset 3100, a *

3333
before the calling number
3000 3100

The set 3000 has a private number (3333)

738
Twin set
Overview
Call handling - Executive / Secretary configuration
▼ Executive main line
I/C Filtering
Executive
Secretary Caller Id
▼ Executive secondary lines
I/C Filtering
Executive Secretary * Caller Id

EXECUTIVE / SECRETARY CONFIGURATION
●The tandem secondary set doesn’t have the filtering keys (screening, unscreening, executive call,...), but only the line keys
●The secondary set can make an executive call even if this one is in filtering
The call presentation on the secretary secondary set is displayed depending on the call type (secretary call, executive filtering on the
●
main and the secondary line and executive call (filtering key))
● Features not implemented on the secondary secretary set
Éxecutive mail
Éxecutive forward from the secretary
´Listen-in
MULTILINE
●Tandem supervision
´Tandem supervision is done on the tandem main directory number
´The supervision key takes in order the tandem main and secondary sets status
Free - No set busy
Partially busy - One line at least is busy on one of the both set and one line is free on the main set
Totally busy - All the lines of the main set are busy
Ringing - Tandem is ringing

739
Twin set
Overview
Secretary call
Secretary
Boss # Caller Id


740
Twin set
Overview

➨ Call presentation priority for the executive/secretary call
Executive Secretary
I/C call Conversation

I/C call
R.T
Executive Secretary
Secretary
I/C call Conversation

Secretary call Secretary call

Remarks: A secretary call takes place a normal ringing call on the secondary set, if there is no free resources.
The call will ring till a resource becomes free .
RT: ringing tone

741
Twin set
Overview
Service level
➨ Same service level for the both sets
➨ Facilities can be set up from the main or the secondary sets
3000
FACILITIES
Duplication of the
configuration
3000 3100

TANDEM FEATURES LIST (Features activated for the both set of the tandem)
• Local or network call
● Outgoing call (main set NDS)
● Forwarding
● Overflow on associated set
● Voice mail notification and consultation
● Record on voice mail
● Secret code management
● Associated set management
● Call parking
● Secret of identity
● Call pick-up
● Read of the metering counter
● DND
● Camp-on control
● Alarms consultation
● Call-back consultation
● Call of the last caller
● Meet-me reminder
FEATURES NOT PROVIDED ON TANDEM

• Padlock Available on each set only
● Group call pick-up Available on each set only
● Call back by Redial key Available on each set only
● Malicious call Available on each set only
● Forward from the main to the secondary Not allowed
● Overflow between the both sets Not allowed

742
Twin set
Overview
Tandem specific feature
➨ Transfer between the both sets of the tandem

▼ From the cordless set, press ok to put the call in hold then off hook
the desktop set to pick-up the call
▼ From the desktop set, press the park key then off hook on the
cordless set
➨ Enable/Disable one set ringing

▼ Done by prefix
▼ Suppress the ringing of the selected set


743

744
Twin sets management with mgr
PROCEDURE
OBJECTIVE
- To learn how to manage a twin sets with mgr
OVERVIEW
The twin sets group (or tandem) is a logical association between two sets, one called "main set" and
the other "secondary set"
The tandem function is defined so that the telephone services are provided homogeneously on the
two sets
Warning: the two sets used for the tandem must be declared as multi-lines

745
PROCEDURE
1. Twin sets management
1.1 Main set

Application On Mgr
Select Users
Action Press CTRL+V or F1 to validate
Users
Result
31000
31001
Action Select a set with the arrow keys
Remark Select the main set, in our example it’s the set 31000 (Advanced)
Review/Modify Users
Result
Directory name : Main set
Directory First Name : -----------------
Location Node : 1
Shelf Address : 1
Board Address : 1
Set Type + 4035T
Entity Number : 1
Set Function + Default
Profile Name : ---------------
Key Profiles + None
Domain Identifier : 0
Language ID : 1
Secret Code : ****
Confirm : ****
Action Press 6 times CTRL+F to find the Tandem parameters
Tandem
Entry
Tandem Directory Number : 31010
Main set in the tandem + True
Partial busy + False
Ringing in partial busy + Long Ring
Specific supervision + False

746
Remark Meaning of the different attributes

Tandem Directory Number: Enter the directory number of the secondary
set
Main set in the tandem: Select Yes (because the set 31000 is the main set)
Partial busy:
- False: (by default) the status of the tandem reflects the occupation status of
the main set
- True: the tandem is seen as busy as soon as one of the sets of the tandem
is busy
Ringing in partial busy:
- Long Ringing: (by default) long ringing for all ringing sets
- Short Ringing: short ringing for free set (if the second is busy)
Specific supervision :
- False: the supervision performed by this set is of normal type
- True: the supervision performed by this set is of tandem type
1.2 Secondary set

Remark The tandem parameters are automatically created according to the main set
tandem configuration

747

748
Twin-set configuration
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage a twin-set configuration
MANAGEMENT
1. Realize the following configuration with an 4035 or 4039

1.1 Check if the sets are multilines sets
1.2 Use a DECT handset for the secondary set
Twin-set number = main set number
2. Test the configuration

749
Twin-set configuration

750
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
751
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
752
Direct Speed Dialing

OBJECTIVE:
◆ To describe the principle of the Direct Speed Dialing
Alcatel OmniPCX Enterprise – Direct Speed Dialing

753
Overview
Services provided by speed dialing numbers

➨ Simplified dialing
▼ Abbreviated numbers are used by internal users to contact often-

called external correspondents
▼ Makes dialing faster (Fewer risks of mistakes when typing in)
0004415644XXXXX
▼ More easily memorized

▼ Number dialed can be checked visually (the name corresponding to
the code dialed is displayed on UA sets)
London:Mr Smith
3322


754
Overview

➨ Barring
▼ The abbreviated number can be controlled or not by baring

principles
▼ Mr. Smith wants to call his correspondent in England

His network access category denies him access to international
service
000441XXXXXX
Speed Dialing Table

3322
Prefix Call Nb Barring.
3322 000441XXXXX no
3333 000443XXXXX yes
3333


755
Overview

➨ Speed Dialing number overflow
▼ Enables automatic dialing of another abbreviated number when it is
impossible to use the outgoing trunk circuit of the abbreviated
number initially dialed
Speed Dialing table

Code call nb overflow Call server TG1 seizure Pref.:0
3322 10 441XXXXXX
3323 0 00441XXXXXX
TG2 seizure Pref:10
Dials 3322 (TG2 saturated)
Speed Dialing table

Code call nb overflow
3322 10 441XXXXX 3323
3323 0 00441XXXXX
Dials 3322 (TG2 saturated)
OK via TG1


756
Overview

➨ Delayed overflow
▼ Corresponds to another call number used if the user does not

complete the incomplete speed dial number
▼ Example: a user generates the n° 05566 by dialing the

abbreviated number 40:
Speed Dialing table
Code Call Numbers Nb timed overflow
40 0015566 41
41 00155667000
▼ If the user does not complete the number 015566 automatically

before the time out, the system will dial the number contained in the
code 41: 00155667000 (usually attendant number)


757
Overview

➨ More user-friendly presentation of incoming calls
▼ If the external caller set number is known in the abbreviated number

table, the presentation of the call on the called party’s UA set with
display is more user friendly.
Smith John is calling
Instead of
014077XXXX is calling


758
Overview
Direct speed dialing features
➨ Only one range of of speed dial numbers is manageable
➨ Each direct abbreviated number has its prefix in the

numbering plan
➨ The user has to dial
▼ The prefix "abbreviated number"

e.g.: ”6000", then the corresponding "call number" is used
Call number: 0 022503200
(Trunk group seizure or ARS prefix + external number)


759
Overview
"Direct abbreviated number" operation
" 6000 "
System Abbreviated ...

Call number Phone book name
Index prefix
Direct 0 6000 0 02 98 14 35 42 Alcatel ...
abbreviated 1 6001 0 02 98 14 32 62 Training Department
n° range
... ...
First index: 0
Size: 1000 n° 999
1000
Available area for
...
abbreviated numbers
by range


760
Direct speed dialing management
PROCEDURE
OBJECTIVE
- To learn how to manage direct speed dialing with mgr
OVERVIEW
- Create one Free numbers ranges list (ex: for 1000 direct speed dialing numbers)
- Create one direct speed dialing range
- Create several direct speed dialing numbers using mgr tool

761
PROCEDURE
1. Create the direct one free numbers ranges list

Application mgr
Path System / Free Numbers Ranges List /
Action Create
Entry Name : Speed dialing
Range beginning : 1000
Range End : 1999
Digits Authorized : 0,1,2,3,4,5,6,7,8,9
Max. number : 10
Action Ctrl v or F1 to validate
2. Display free speed dialing numbers

Application mgr
Path System /Free Directory Numbers /
Result 1000 1005
1001 1006
1002 1007
1003 1008
1004 1009
Remark The system display 10 free numbers. Link to the previous managed parameters
3. Create the direct speed dialing range

Application mgr
Path Speed dialing / Direct speed Dialing Numbers/
Entry Index of 1st Speed Dial Number : 0
Length for Speed Dialing Numbers : 1000
Remark This range is unique and 15000 numbers are available on the system
So don’t hesitate to be large during direct speed dialing range creation

762
4. Create a direct speed dial Number

Application mgr
Path Speed dialing / Direct speed Dialing Numbers/
Action Create
Entry Direct speed dial number N° Prefix : 1000
Call number : #0120232132000)
Directory name: Smith
Directory frist name: John
Call restrictions –Barring: true
Can be called/Dial by name: true
5. Display the list of direct speed dialing Numbers

Application Under mtcl
Command edabv
Result (101)xa001001> edabv
==========================
enter criteria or command:name
==========================
1 - pref -> Prefix number
2 - num -> Call number
3 - name -> Phone book name
==========================
enter criteria or command: go
==========================
Query launched !
23/01/04 EDABV V. 4.00 Page : 1

+--------+------------------------------+---------------+
|pref |num |name |
+--------+------------------------------+---------------+
|1000 |#0120213132000 |smith john |

763

764
Direct speed dialing
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage direct speed dialing numbers
MANAGEMENT
1. Define the direct speed dialing range (ex :from index 0 and for 1000 direct speed dialing
numbers)
2. Create a direct speed dialing number 37100, its content will include the DOD prefix followed
by the number 01012603x10 (outgoing call).
3. Test: from user 3x000, dial 37100. Does your extension 3x100 ring?
4. Display the list of direct speed dialing Numbers using the following command: edabv.

765
Direct speed dialing

766
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
767
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
768
Multiple Line Appearance

OBJECTIVE:
◆ To describe the Multiple Line Appearance
Alcatel OmniPCX Enterprise – Multiple Line Appearance

769
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


770
Overview
Example of configuration:
GR
3200
GR
GR 3301
3100
GR
3200
GR
3003 3301
GR GR
3100 3100
3000 3002


771
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
Order id:1
Order id:2
Order id:3


772
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.


773
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
Order id:1
Order id:2
Order id:3


774
Overview
Signalling 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

!!! 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.

775
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


776
Overview
Display on the UA set
➨ For the primary MLA key

▼ Like a regular multiline 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 overring)
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

Timer N° 297 for the delayed ringing: default value 5s

777
Overview
Restrictions:
➨ No MLA set in parallel PBX
➨ No twin set management with sets with MLA keys
➨ No 4980
➨ Network moving is not authorised for sets using MLA keys
➨ Extension must be multiline


778
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)


779
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


780
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 Callback
▼ Only the set on which the MLA key is managed is notified
▼ If you set up the callback, the system sends through the isdn network:
✦ installation N° + Principal directory number of the set


781
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 dialled 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

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.

782
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

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.

783
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

On the charging ticket appears the call number of the MLA group (field 35)

784
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.


785

786
MLA management with mgr
PROCEDURE
OBJECTIVE
- To learn how to manage MLA with mgr
REFERENCE
OVERVIEW
The A-MLA (Alcatel Multi-line Appearance) service is a pseudo parallel hunt group with Multiline
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.

787
PROCEDURE
1. Create a virtual set for the MLA primary set

Application On mgr
Path Users
Action Create
Shelf Address : 255
Board Address : 255
Set Type + UA VIRTUAL (4035 VIRTUAL)

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)
Key Number : 1
Mnemonic (Pocket,Mobile,4040) : ------------

788
3. Create the MLA keys

Application On mgr
Path Users / Progr.Keys
Key Number : 3

Entry Function + Primary MLA

Order : 1
Remark The set 31500 must be multiline. 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:
Order : 2
Path Users / Progr.Keys
Key Number : 3
Entry Function + Secondary MLA

Order : 1
Ringing Mode + No Ring
Deferred ring + NO
Remark The set 31000 must be multiline.

789
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:
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).

790
4. Management of the supervised hold ring back mode

Application On mgr
Path System / Other System Param. / MLA Parameters
Select System Option + Supervised Hold Ringback Mode

Entry Supervised Hold Ringback Mode + Ring All Supervisor Sets
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
Select System Option + MLA Line Key Option

Entry MLA Line Key Option + Supervised Hold

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.

791
Select System Option + MLA Hold Key Option

Entry MLA Hold Key Option + Privacy Hold
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.

792
5. Timers management
5.1 Trunk supervised hold timer

Application On mgr
Path System / Timers
Entry Timer No. : 296

Entry Timer units : 1200

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


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


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.
Path System / Other System Param. / Local Features Parameters
Select System Option + Ring On Hangup Private Hold

793

Entry Ring On Hangup Private Hold + Do Not Ringback

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

Entry Automatic Outgoing Seizure for MLA + True

Remark By pressing the MLA key, the user will be able to make directly an outgoing
call.!

794
7. Check the management of MLA primary keys

Login mtcl
Command readkey
Result --> main menu <--
2) display by mcdu
q) quit
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
inf_num: -1
etat_led: 45
pri_cour_line: 0-0
cor_pre: 0
keytype: 255
Key 4: Multi MCDU MLAP ---> Key content: 31600
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).

795
8. Check the management of the MLA secondary keys

Login mtcl
Command multitool
Result +------- [ Main Menu ] -------+
[ 0] - Exit
CHOICE ?
Entry +------- [ Consult Secondary MLA Keys ] -------+

[ 0] - Father Menu
[ 1] + Consult All Secondary MLA keys
[ 2] - Consult All Secondary MLA keys Of a Directory Number
CHOICE ? 1
Entry +------- [ Consult All Secondary MLA keys ] -------+

[ 0] - Father Menu
[ 1] - From Database
[ 2] - From Memory
CHOICE ? 1
Entry +------- [ From Database ] -------+
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

796
MLA management
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.2. In the second set :

797
MLA management

798
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
799
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
800
Alcatel OmnPCX Enterprise
Alcatel 4645

OBJECTIVE:
◆ To describe Alcatel 4645 voice mail application
Alcatel OmnPCX Enterprise – Alcatel 4645

801
Alcatel 4645
content
Overview
Capacity
Software locks
Features
Environment and architecture


802
Alcatel 4645
Overview
The Alcatel 4645 is a voice mail integrated to the

OmniPCX Enterprise call server in the IPRS and IPAS
configurations.
This mail system cannot be managed in offers using 4400

hardware
The Alcatel 4645 software can be supported by the call

server disk
No need of a specific hardware
The signaling between Alcatel 4645 and the call server is

done according to ABC-A protocol

IPRS: IP Rack Server

IPAS: IP Appliance Server
The voice mail 4645 is not available on CPU5-3, CPU6 et CPU7.

803
Alcatel 4645
Overview
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”
➨ No basic voice guides recording on digital sets
Voice mail networking (VPIM)


804
Alcatel 4645
Capacities
Maximum number of accesses

➨ 16 on appliance server or 8 on CPU CS*
➨ 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)

*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)

805
Alcatel 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


806
Alcatel 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


807
Alcatel 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


808
Alcatel 4645
Features
Automated attendant
➨ Direct call of AA (Automated Attendant) menu
➨ Supervised transfer
➨ Call pre-routing: company greeting
➨ Language selection
➨ Multi-level with multiple entries
➨ Audiotex feature


809
Alcatel 4645
Features
Ubiquity function:
➨ Default settings
▼ if no personal greeting a default greeting message is available
➨ 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


810
Alcatel 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

811
Alcatel 4645
A single voice mail can manage all type of sets
CS Alcatel
4645
IP
Network
GD


812
Alcatel 4645
Configuration 1
➨ The call server and the voice mail are embedded on the
same CPU
e-CS + e-CS +
Alcatel 4645 Alcatel 4645
Common hardware Appliance server:

8 ports 16 ports


813
Alcatel 4645
Configuration 2
➨ The call server and the voice mail are working on 2

separated CPU
CS Alcatel
4645
IP
Network
GD


814
Alcatel 4645
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

4645
IP
Network


815
Alcatel 4645
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
4645
IP
Network

Caution: The voice mail is not duplicated

816
Alcatel 4645
Configuration 4: switch-over
➨ Status after call server switch-over
▼ The previous Main Call Server has become Stand-by, and the Alcatel
4645 is still driven by the Main CPU
e-CS Main e-CS Stand by
Alcatel
4645
IP
Network


817
Alcatel 4645
Telephone working and IP environment
G711
e-CS Alcatel
4645
IP
G711
Network
G723
e-MG
IP-PHONE

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 IP phone 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.

818
Alcatel 4645 with mgr
PROCEDURE
OBJECTIVE
- To learn how to put into operation Alcatel 4645 with mgr
OVERVIEW
The Alcatel 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.

819
PROCEDURE
1. Alcatel 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
GD

820
1.1 Check Software lock with spadmin command

Login mtcl
Command spadmin
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 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.

821
1.2 Declare the name and IP address of the CPU 4645

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
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) ?
N

822
1.3 the IP address and name of the CPU CS in the CPU 4645 Host file
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'
Entry 1
9.1.Host database update
Result
========================
1. 'View'
2. 'Add/Update'
3 'Delete'
0. 'Previous menu'
Entry 2
Host database update
Result
====================
Host name ?
Entry xa001001
Host address (default is 10.1.1.1) ?
Result
Entry 10.1.1.1

823

Result
========================
1. 'View'
2. 'Add/Update'
3 'Delete'
0. 'Previous menu'
Entry a

824
1.4 Check IP address and name of the CPU-CS

Login mtcl
Command netadmin -m
Result
1. 'Installation'
4. 'CPU redundancy'
7. 'Tunnel'
8. 'Routing'
10. 'Copy setup'
11. 'Security'
0. 'Quit'
Entry 3
3.Local Ethernet interface
Result
==========================
1. 'View'
2. 'Update'
0. 'Previous menu'
Entry 1
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'
Entry 0 (as many times as needed)

825
1.5 Add IP address and name of the CPU 4645 in the CPU-CS host file
Login mtcl
Command netadmin -m
Result
1. 'Installation'
4. 'CPU redundancy'
7. 'Tunnel'
8. 'Routing'
10. 'Copy setup'
11. 'Security'
0. 'Quit'
Entry 9
9.Host names and addresses
Result
==========================
1. 'Host database update'
2. 'Aliases'
0. 'Previous menu'
Entry 1
Result
========================
1. 'View'
2. 'Add/Update'
3. 'Delete'
0. 'Previous menu'
Entry 2
Host database update
Result
====================
Host name ?
Entry ev001001 (cpu Alcatel 4645 )
Host address ?
Result
Entry 10.1.1.15

826

Result
========================
1. 'View'
2. 'Add/Update'
3. 'Delete'
0. 'Previous menu'
Entry a
0 (as many times as needed)

827
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
Remark
Voice Mail CPU Name:
Name or IP address where is implemented The Alcatel 4645 (warning: don’t

use role address)
After the voice mail number directory creation one shelf is automatically
created , Alcatel 4645 is seen as a rack in the call server
1.7 Check the presence of 4645 voice mail and eva.cfg files
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 |
+--------------------------------------------------------------------+
|------------------------------------------------------------------- |
| 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

828
2. Alcatel 4645 on the call server

829
2.1 Check software locks with spadmin command

Login mtcl
Command spadmin
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 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.

830
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
Remark Voice Mail CPU Name:
Name or IP address where is implemented The Alcatel 4645 (warning: don’t
use role address)
After the voice mail number directory creation one shelf is automatically
created , Alcatel 4645 is seen as a rack in the call server
2.3 Check the presence of 4645 voice mail and eva.cfg files
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 |
+--------------------------------------------------------------------+
-------------------------------------------------------------------- |
| 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

831

832
Alcatel 4645 mailboxes allocation
PROCEDURE
OBJECTIVE
- To learn how to allocate mailboxes to users with mgr
REFERENCE
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.

833
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)
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

834
3. Check the voice mailbox creation

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 :
Entry 1

835
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

836
Alcatel 4645

OBJECTIVE:
◆ To maintain Alcatel 4645 voice mail application

837
Alcatel 4645
Maintenance
The Eva_tool is a simple tool used for Alcatel 4645

maintenance
The “auditmevo” command on the call server allows to

update the Alcatel 4545 data base according to e-CS data
base . This command is very useful specially if case of
Alcatel 4545 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 4645).

838
Alcatel 4645
Maintenance
Eva_tool maintenance tool description (Telephone

application started)
➨ This command is launched under the mtcl account on the

CPU supporting the Alcatel 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 4545 data base
2 : Modify a password -> Used to modify in Alcatel 4545 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:

839
Alcatel 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 Remaalz -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:

840
Alcatel 4645
Maintenance
Eva_tool maintenance tool description (next) Telephone

Application
➨ Display information on mail boxes started
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


841
Alcatel 4645
Maintenance
➨ 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

842
Alcatel 4645
Maintenance
➨ 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


843
Alcatel 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 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.

844
Alcatel 4645
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to bring into service the Alcatel 4645 voice mail
MANAGEMENT
1. 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.

845
Alcatel 4645
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.

846
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
847
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
848
V24/IP box

OBJECTIVE:
◆ To describe the remote V24/IP box
Alcatel OmniPCX Enterprise – V24/IP box

849
V24/IP box
Overview
Context
Solution
Hardware characteristics
Software
Installation


850
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


851
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


852
V24/IP box
Overview
The hardware solution selected by Alcatel 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.

853
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)


854
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.

855

856
V24/IP box

OBJECTIVE:
◆ To manage a remote IP V24 box

857
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


858
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 ▲▼

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 [ ]

859
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.

860
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

861
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”.

862
V24/IP box

OBJECTIVE:
◆ To provide V24/IP box maintenance

863
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

864
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


865
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.

866
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


867
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)


868
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) ?
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) ?


869
V24/IP box
Maintenance
Npadm program (5/8)
➨ Configuration check
[ 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...

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.


870
V24/IP box
Maintenance
Npadm program (6/8)
➨ Server configuration
MAIN MENU
Add server
Delete server
Configure server
Ports Monitor
Driver removal
Exit

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


871
V24/IP box
Maintenance
Npadm program (7/8)
➨ Firmware upgrade

Configure Server
Server property
Port property
Upgrade firmware
Save & Restart
Exit
Enter Firmware FileName:/usr/etc/moxatty/NPL.ROM
<Esc>: Cancel <Ctrl+F>: OK


872
V24/IP box
Maintenance
Npadm program (8/8)
➨ Firmware upgrade
[ 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...


873

874
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.1 the V24 Port /dev/rv24/b1/tty1 for hotel menu
4.1.2 the V24 Port /dev/rv24/b1/tty2 for login

875
V24/IP box

876
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
877
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
878
Database backup and restore

OBJECTIVE:
◆ Describe the backup of the database with swinst
Alcatel OmniPCX Enterprise – Database back up and restore

879
Overview
To protect the customer’s database against

➨ The system crash
➨ Mistakes made on the database itself
To recover the customer’s database after

➨ An empty database creation
➨ A software downloading


880
Overview
After any objects modification or creation (1)

➨ Use swinst account to backup
On the system there is also an automatic backup everyday

at 5:45 AM by default
All of this backup’s files are stored on the CPU’s hard disk
To copy the backups 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

881

882
Database save & restore
PROCEDURE
OBJECTIVE
- To learn how to save and restore the database via swinst
OVERVIEW
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.

883
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 operation
1 Immediate backup operation
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
220 xa0001001 FTP server (Version wu-2.6.1(1) Wed Feb 28
15:50:32
Entry User (155.132.1.1: (none)): mtcl
Password: mtcl

884
Remark:
Use the ftp connection to save OPS files on your PC (155.132.1.1 = cpu IP@)
command ftp> bin
Remark:
command ftp> cd /usr4/BACKUP/IMMED
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
3 Restore operation
3 Clean immediate backups on the cpu disk
1 clean mao, voice guides and accounting data
Action Press Q as many times as needed to exit from swinst menu

885
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
220 xa0001001 FTP server (Version wu-2.6.1(1) Wed Feb 28
15:50:32
Entry User (155.132.1.1: (none)) : mtcl
Password: mtcl
Remark :
Use the ftp connection to restore mao-acc file on your PC (155.132.1.1 = cpu
IP@)
command ftp> bin
Remark :
command ftp> cd /usr4/BACKUP/IMMED
Remark :
Go to this specific folder to send the database file
command ftp> put mao-acc
ftp>quit

886
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
Result Linux Mandrake for eMediate release 7.2 (Odyssey) for i486
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
3 Restore operation
1 Restore from cpu disk
1 Restore from IMMEDIATE backup
1 Restore mao, voice guides and accounting 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

887
3.4 Restart the phone application

On the call server
Login mtcl
Command swinst
Select 1 Easy menu
8 Start the telephone
Entry Please confirm to start the telephone: y

888
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 an user
3. Restore the saved database via swinst
4. Test it

889

890
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
891
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
892
Remote Maintenance Access

OBJECTIVE:
◆ To describe the RMA solutions
Alcatel OmniPCX Enterprise – Remote Maintenance Access

893
Overview
The RMA system is an interface used to carry out

maintenance and administration operations on the OXE
This maintenance is carried out by an operator either

locally or remotely via the public network or a private
network.
The RMA carries out three main functions

➨ Access and act on the two Call server of a duplicated node
➨ It reinforces access security
➨ It can feed-back information from the PABX to the remote
maintenance center -> alarms


894
Overview
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


895
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:
+ ▼ Remote access with automatic call back to a fixed number

S
e
c
u
▼ Remote access with automatic call back to the caller number
r
i
t ▼ Simple remote access
y -
Alarms sending


896
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 the 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


897
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 server login and password
Login:mtcl
Login:remote
Password:xxxx
Password:xxx
mtcl>
RMA> Login: remote 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.

898
Overview
Call back on the caller number to enter after login:

number
➨ 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 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


899
Overview
Call back on a predetermined number:

number
➨ 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
server login and password
RMA Login: toto
Password: ****
Please wait, I ’ll call you back.
Public RMA
Network box
Modem number: 0298143500


900
Overview
The OmniPCX Enterprise call server is generating incidents

that are used by the technicians to supervise the state of
the system (board reset, call rejected, …), these messages
➨ Can be stored on the e-CS hard disk (to generate reports…)

➨ Can be displayed on the e-CS Ethernet or V24 access
(terminal, printer…)
➨ Can be ringing an alarm set (possibility to ring a 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…)


901
Overview
RMA alarm
Alarms table
CS Alarm Alarm 1
Alarm 2
Alarm 3
OXE Alarm 4
Alarm 5
OXE Incidents
OPERATOR
?
Call and alarm transmission
to a remote site
TD RD CD 19 14 96 ON
3 External alarm contacts


902
RMA – Crystal hardware

OBJECTIVE:
◆ To describe the RMA for the Crystal hardware
Alcatel OmniPCX Enterprise – RMA – Crystal hardware

903
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)


904
Overview
Principle: RMA board inside the crystal media gateway

Local Remote
console console
CPU A
RMA
Modem
Modem
CPU B
OPERATOR


905
Overview
Principle: RMA board inside the connecting box

Local Remote
console console
RMA
CPU A
Modem
Modem
CPU B
OPERATOR


906
Overview
Connecting box
Ports
Portsnot
notavailable
availablewhen
when
BRMA
BRMAboard
boardisisconnected.
connected.
Port
Portdedicated
dedicatedto
tolocal
local
system
systemterminal.
terminal.
Port
Portdedicated
dedicatedto
toremote
remote
maintenance modem.
maintenance modem.
Port
Portenabling
enablingeither
eitheraaTA,
TA,or
oran
an
external application to be connected.
external application to be connected.


907
Overview
RMAB board
ACT PWI
INT
CPU
EXT
Coupler
Couplerreset
resetbutton
button. .
Debug
Reset
RMA
RMAboard
boardcancanbe
beconnected
connected either
either
in
inaaslot
slotof
ofthe
theOmniPCX
OmniPCXEnterprise,
Enterprise,
or
orin
inthe
the BRMA
BRMA boxbox to
tofree
freeaaslot
slotin
in
the OmniPCX Enterprise’s
the OmniPCX Enterprise’s ACT.ACT.
RMAB


908
Overview
RMA accesses Remote login secured or not

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 OmniPCX
Enterprise
Local login
- modem for outgoing call
PC (local connection)


909
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>


910
Overview
Remote access to the RMA (through ExB or ExC)
Public
network
at
OK
atdt00298762208
CONNECT 9600
RMA Login: amr

Password: ***

Phone: xx xx xx xx
Monday April 01 18:25:41 2001

RMA>


911
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: ***

Phone: xx xx xx xx
Tuesday April 02 11:13:19 2001
RMA>


912
Overview

➨ on a predefined number
atd00298762208
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: ***

Phone: xx xx xx xx
Tuesday November 30 11:13:19 1999
RMA>


913
Overview
Access to the Alcatel 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


914
RMA – Common hardware

OBJECTIVE:
◆ To describe the RMA for Common hardware
Alcatel OmniPCX Enterprise – RMA – Common hardware

Ref. ENTPT0431P07TEUS Issue 01
915
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


916
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


917
Overview
RMA accesses Remote login secured or not

- 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 OmniPCX
Enterprise
Local login
- modem for outgoing call
PC (local connection)


918
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: ***

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>


919
Overview
Remote access to the RMA (through ExB or ExC)
Public
network
at
OK
atdt00298762208
CONNECT 9600
RMA Login: amr

Password: ***

Phone: xx xx xx xx
Monday April 01 18:25:41 2001

RMA>


920
Overview

➨ on a number entered after the login
atd00298762208
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: ***

Phone: xx xx xx xx
Tuesday April 02 11:13:19 2001
RMA>


921
Overview

➨ on a predefined number
atd00298762208
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: ***

Phone: xx xx xx xx
Tuesday November 30 11:13:19 1999
RMA>


922
Overview
Access to the Alcatel 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


923

924
RMA - e-RMA

OBJECTIVE:
◆ To describe the e-RMA solution
Alcatel OmniPCX Enterprise – RMA – e-RMA

925
RMA - e-RMA
Overview
Alternative software solution to the RMA box(No hardware)
➨ Full software solution: free of charge
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


926
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


927
RMA - e-RMA
Overview
Incoming call from remote assistance center
➨ The remote assistance center dials a DDI number which

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 on 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 on a predefined
number


928
RMA - e-RMA
Overview
e-RMA limits and remarks
➨ The e-RMA application can not work if telephone

application is not running
▼ If telephone application is stopped, it can't 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


929

930
System Messages

OBJECTIVE:
◆ To describe the system message
Alcatel OmniPCX Enterprise – System Messages

931
System Messages
Overview
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
To define the minimum severity level of messages

displayed, stored and sent:
➨ path: Applications / Incident manager
To define some exceptions, and the incidents sent to the

RMA:
➨ path: Applications / Incident manager / Incident filter


932
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

933
System Messages
Overview
Backup Files
counter 1 counter.txt
➨ Incidents saved as files counter 2
➨ on hard disk 1
inc-3.txt
2
➨ To read the messages stored
3
➨ on the disk: inc-2.txt
▼ incvisu, with the option: 4
✦ -1: before the last reset
✦ -2: before the last reset but one 5
✦ -3: before the last reset but two inc-1.txt
✦ -r: oldest to newest 6
✦ -t x: the x last messages
✦ -s “abc”: messages that contain 7
the string “abc” 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

934
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

935
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

936
System Messages
Overview
Incident management
➨ /Applications/Incident manager
V24 port used for
,Consult/Modify: Incident manager,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, the alarms retrieval
. .
. Node Number (reserved): 1 .
. Instance (reserved): 1 .
. .
.
.
V24 No. + /dev/rv24/b1/tty3 (47)
RMA + eRMA
.
.
RMA solution used for
. RMA Network + NO . the alarms retrieval
. 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 .
. .
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

RMA solution: e-RMA or RMA

937
System Messages
Overview
Incident filter management

➨ /Applications/Incident manager/Incident filter
, Consult/Modify: Incident Filter,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
. .
. Node Number (reserved): 1 .
. .
. Filter id .
. .
. Incident Number: 2042 .
. Network Number: -1 .
. Node Number: -1 .
. ACT shelf Number: -1 . Determine the “action”
. Coupler Number: -1 .
. Behind Us: -1 . use for this incident
. 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 .
. .
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

The configuration of the action is done on the RMA board or under mgr for the e-RMA

938
RMA automatic calls
PROCEDURE
RMA automatic calls
OBJECTIVES
- To learn how to configure the remote accesses via the RMA board
- To learn how to configure the OmniPCX Enterprise and the RMA board to call automatically in
case of alarms.
OVERVIEW
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.

939
RMA automatic calls
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
Parameters Enter the number of the line to update: 3

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

940
RMA automatic calls
3. Program a basic call back remote login

Choice:
Action
➥3 – Management
➥6 – Logins
Parameters Enter the number of the line to update: 4

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

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

941
RMA automatic calls
5. Data saving
Choice:
Action
➥3 – Management
➥9 - Save
Do you really want to save set up?
Parameters
[Yes/No – default is no]: Yes

942
RMA automatic calls
PROGRAMMING OF THE AUTOMATIC CALLS ON RMA
6. Consult the programming of the destination numbers used for the

automatic calls
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:
[1] Phone 1: ExB -
[2] Phone 2: ExB -
Your choice:
[1] Phone 1: ExB -
[2] Phone 2: ExB -
Your choice:
[1] Phone 1: ExB -
[2] Phone 2: ExB -
Your choice:

943
RMA automatic calls
7. Consult the programming of the CPU alarm in the RMA

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
Choice:
Path
➥3 – Management
➥ 4 – PABX incidents
➥ 1 – Incidents action0
Parameters First destination: _ _ _ _ _ _

944
RMA automatic calls
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
F2 key several times to exit mgr
Action
‘exit’ command to leave the ‘mtcl’ session.
‘Ctrl+A’ twice to disconnect from the CPU

945
RMA automatic calls
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 -
Parameters [1] ExB (default value)
Your choice: 1
/Management/Automatic call/Destinations/Destination 1/Phone 1
Phone 1: 0298143636
[1] Phone 1: ExB - 0298143636
[2] Phone 2: ExB -
Your choice: 3
/Management/Automatic call/Destinations/Destination 1/Timeout for user
connection
Default value: 30
Timeout for user connection: 60
[1] Phone 1: ExB - 0298143636
[2] Phone 2: ExB -
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

946
RMA automatic calls
9.3 Program the automatic call in case of CPU alarm activation

➥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
9.4 Enable the automatic calls

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)

947
RMA automatic calls
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

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

F2 key several times to leave mgr
Action
‘exit’ command to leave the ‘mtcl’ session
twice ‘ctrl+A’ for CPU disconnection

948
RMA automatic calls
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

Choice:
Path
➥3 – Management
➥ 4 – PABX incidents
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

949
RMA automatic calls

950
Setup the e-RMA
PROCEDURE
Setup the e-RMA
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

951
Setup the e-RMA
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
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

Action mgr
Path /Applications/e-RMA/e-RMA application
Action Enter a free directory number (DDI number)
Result Instance (reserved): 1
Directory No : 31600
Login attempts: 3
Unreachable delay: 15
Delay between two incident calls: 15

952
Setup the e-RMA
3. Management of e-RMA logins

Action mgr
Path /Applications/e-RMA/e-RMA application
Action Enter e-RMA login + Password + Security method
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

Action mgr
Path /Applications/e-RMA/e-RMA actions
Action Enter Action type + Alarm center number
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

953
Setup the e-RMA
5. Incident management
Action mgr
Path /Applications/Incident manager
Action Select e-RMA
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

954
Setup the e-RMA
6. Incident filter management

Action mgr
Path /Applications/Incident manager/Incident filter
Action Enter al
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

955
Setup the e-RMA

956
e-RMA management
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)

957
e-RMA management

958
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
959
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
960

System Configuration PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Configuration PDF

Uploaded by

Copyright:

Available Formats

Alcatel OmniPCX Enterprise

Technical Training offer

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

represents training courses involved in ACSE certification

represents training courses involved in ACFE certification

I=xh C=xd V=xd

I = x h stands for Individual learning, in hours

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

OMNIMESSAGE 4635 EXPERT: GET AUTONOMY

HOTEL / HEALTHCARE: RUN BUSINESS

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

REFERENCE ENTPTE401US DELIVERY LANGUAGE English (course material in English)

12 hours Virtual self-paced training on the computer

Tutored virtual training sessions accessible via an internet connection

MAXIMUM NUMBER OF PARTICIPANTS 12

At the end of the course, the participant will be able to:

REQUIRED TECHNICAL CONFIGURATION

Phase 1: i-learning 12 hours

Describe the available remote maintenance solutions:

Phase 2: c-learning 8 days

ISSUE DATE ISSUE DATE

Alcatel OmniPCX Enterprise System Configuration

File reference: ENTPTE401US

CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION

2. Empty Database creation

Issue 01 REF. ENTPTE401US 0.1

4. Shelves and boards creation

0.2 REF. ENTPTE401US Issue 01

10. Automatic Callback on Busy Trunk Group

11. DID Translator

12. External Callback Translator

13. Classes of services

Issue 01 REF. ENTPTE401US 0.3

15. Multiline sets

16. Assistant / Manager groups

17. External Calls Barring

18. Automatic Route Selection (ARS)

0.4 REF. ENTPTE401US Issue 01

20. Calls Distribution

23. Speed Dialing

24. Multiple Line Appearance (MLA)

25. Alcatel 4645

Issue 01 REF. ENTPTE401US 0.5

26. MOXA V24/IP Box

27. Database Save & Restore

28. RMA Solutions & System Messages

0.6 REF. ENTPTE401US Issue 01

SECTION CHAPTER PAGE DESCRIPTION OF THE ERROR

Issue 01 REF. ENTPTE401US 0.7

0.8 REF. ENTPTE401US Issue 01

© Copyright Alcatel Business Systems 2005

◆ To describe the call server IP address

Alcatel OmniPCX Enterprise – System IP addressing

The goal is to integrate on the customer’s LAN:

➨ The computers for maintenance, management or others

➨ Alcatel OmniPCX Enterprise

➨ And every IP elements of installation (GD, INTIP, IP

➨ The tool used for management is netadmin