External Services PDF

Alcatel OmniPCX Enterprise
PARTICIPANT'S GUIDE
External Services
REF. ENTPTE408US
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
System Configuration
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

External Services
ACSE Core level
REFERENCE ENTPTE408US DELIVERY LANGUAGE English (course material in English)
DURATION METHOD
Virtual self-paced training on the computer
3 days Traditional classroom or practical sessions with tutorials (TAP LAB)
Tutored virtual training sessions accessible via an internet connection
MAXIMUM NUMBER OF PARTICIPANTS 12
PUBLIC
System Installers
Technicians and Engineers in charge of the configuration and the maintenance of an Alcatel OmniPCX Enterprise
OBJECTIVES
At the end of the course, the participant will be able to:

• Configure and maintain the external services provided by an Alcatel OmniPCX Enterprise:
o Multi-translator (Identity, ARS, DID translation)
o Private and business calls
o DISA Service
o Remote extension users
• Configure and maintain enhanced services:
o Multi-entities
o Dynamic and static V24 accesses
PREREQUISITES
• To have attended Alcatel OmniPCX Enterprise System configuration training course (Ref.: ENTPTE401US or
ENTPWB401US)
External Services
ACSE Core level
PROGRAM DESCRIPTION
Describe, configure and maintain a multi-entities configuration

Describe, configure and maintain the multi-translator for:
• Identity sending
• DID translation
• External calls barring
• Automatic Route Selection (indirect carrier, time dependence)
Describe, configure and maintain the private calls service
Describe, configure and maintain the business calls service
Describe, configure and maintain the DISA service
Describe, configure and maintain the dynamic and static V24 accesses
Describe and configure the LDAP overflow
Describe, configure and maintain the remote extension facility
Describe, configure and maintain the partial rerouting facility
Alcatel University Alcatel OmniPCX Enterprise
External Services TOC.doc
DOCUMENTATION CHANGES
ISSUE DATE ISSUE DATE
01 04/06
Alcatel OmniPCX Enterprise External Services
File reference: ENTPTE408US
GENERAL SUMMARY
CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION
1. Multi-entities
ENTP0417P02TEUS.................................................................................................................5
ENTP0417C02TEUS ..............................................................................................................21
ENTP0417M02TEUS..............................................................................................................31
ENTP0417H02TEUS ..............................................................................................................35
2. Multitranslator / NPD
ENTP0424P03TEUS...............................................................................................................39
ENTP0424C03TEUS ..............................................................................................................57
ENTP0424M03TEUS..............................................................................................................77
ENTP0424H03TEUS ..............................................................................................................81
3. Complex ARS (time dependance, indirect operator)

ENTP0425P03TEUS...............................................................................................................85
ENTP0425C03TEUS ..............................................................................................................95
ENTP0425M01TEUS............................................................................................................111
ENTP0425H03TEUS ............................................................................................................115
ENTP0425P04TEUS.............................................................................................................117
ENTP0425C04TEUS ............................................................................................................123
ENTP0425H04TEUS ............................................................................................................135
Issue 01 REF. ENTPTE408US 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 External Services
4. Private calls
ENTP0428P01TEUS.............................................................................................................139
ENTP0428C01TEUS ............................................................................................................149
ENTP0428M01TEUS............................................................................................................157
ENTP0428H01TEUS ............................................................................................................159
5. Business calls
ENTP0429P01TEUS.............................................................................................................165
ENTP0429C01TEUS ............................................................................................................169
ENTP0429H01TEUS ............................................................................................................173
6. Static and dynamic V24 accesses

ENTP0443P03TEUS.............................................................................................................179
ENTP0443C02TEUS ............................................................................................................199
ENTP0443P04TEUS.............................................................................................................217
ENTP0443C03TEUS ............................................................................................................227
ENTP0443M02TEUS............................................................................................................245
ENTP0443H02TEUS ............................................................................................................251
7. LDAP overflow
ENTP0466P01TEUS.............................................................................................................255
ENTP0466C01TEUS ............................................................................................................259
ENTP0466M01TEUS............................................................................................................263
ENTP0466H01TEUS ............................................................................................................273
8. DISA
ENTP0430P01TEUS.............................................................................................................277
ENTP0430C01TEUS ............................................................................................................289
ENTP0430H01TEUS ............................................................................................................295
9. Remote Extension
ENTP0474P01TEUS.............................................................................................................299
ENTP0474C01TEUS ............................................................................................................311
ENTP0474M01TEUS............................................................................................................319
ENTP0474H01TEUS ............................................................................................................325
10. Partial re-routing

ENTP0544P01TEUS.............................................................................................................329
0.2 REF. ENTPTE408US Issue 01

2
External Services TOC.doc
FEEDBACK SHEET
In order to improve the quality of the documentation, please report any errors found by returning
this sheet to the address below.
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:
Issue 01 REF. ENTPTE408US 0.3

3
TOC.doc External Services
0.4 REF. ENTPTE408US Issue 01

4
Multi-entities

Transmission or copying of this document is not permitted without prior written authorization. 1
OBJECTIVE:
◆ To describe the principles and components of calls distribution
Alcatel OmniPCX Enterprise – Multi-Entities

Ref. ENTP0417P02TEUS Issue 01
5
Multi-
Multi-entities
Overview
Single entity
➨ Same behavior for all
Company “Thomas Consulting”

Department 1 Department 2 Department 3
Entity 1


6
Multi-
Multi-entities
Overview
Several entities
➨ Specific behavior per department (entity)
Company “Thomas Consulting”
Department 1 Department 2 Department 3
Entity1 Entity 2 Entity 3


7
Multi-
Multi-entities
Overview
Each system entity can be associated a directory number

(most of the time a “DDI number”) corresponding to the
company or department number
➨ People who wants to call this company or department has to

dial this number
➨ It is then 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

8
Multi-
Multi-entities
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 another can be done

automatically by the changeover time management or by an
action from an attendant associated to this entity


9
Multi-
Multi-entities
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
Is accessed by a prefix:
Contains:
- directory number* (mono/multi-line set)
- entity call
- attendant set physical number
- attendant group physical number - 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

10
Multi-
Multi-entities
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 supplementary number is transmitted
after the installation number,
✦ If the subscriber is DDI: it is the station number of the DDI caller which is
transmitted instead of this supplementary number after the installation
number.


11
Multi-
Multi-entities
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


12
Multi-
Multi-entities
Overview
Status of the distribution
➨ A status (mode: day, night…) is given to each entity, each

attendant, each attendant group
▼ The status of the entity can change automatically*, by using the

changeover time management
▼ An attendant, who is allowed to do such modifications, can modify

the status of the entity
▼ The status of an attendant group depends on the status of its

attendants**.
▼ The status of the attendant are: day (plugged ) or 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” by associating an Attendant Group Manager to the entity.
During the period corresponding to this status, the entity status follows the attendant group status (allowing more flexibility).
Moreover, an attendant of this group who has the rights can modify the status of this entity.
** If the last attendant (in service) of an Attendant Group switches in night mode, the attendant group automatically switches in night
status.

13
Multi-
Multi-entities
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…


14
Multi-
Multi-entities
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


15
Multi-
Multi-entities
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


16
Multi-
Multi-entities
Overview
Optional attendant group manager
➨ This attendant group number has two main functions:
▼ The entity status (day, night,…) follows the associated attendant

group status if “attendant group” is notified in the “changeover time”
▼ The attendants, who have the right and who belongs to this
attendant group, can manage (modify) the elements associated to
this entity:
✦ traffic overflow
✦ entity routing numbers (CDT)
✦ entity state (day, night, mode 1, mode 2), “force a state”
✦ entity changeover time “modify the switching time between states”
✦ Access to the ranges of the speed dialing
✦ station and directory number


17
Multi-
Multi-entities
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 another
➨ It is possible to manage separately:

▼ incoming calls changeover time, which modifies (according to the
CDT management) the routing of the incoming calls remaining
unanswered
▼ outgoing calls changeover time, which modifies the behavior on
outgoing calls (according to the “barring rules” and “public access
class of service”)


18
Multi-
Multi-entities
Overview
Music on hold
➨ It is the tone (or voice guide) broadcasted when a user from
this entity put someone on hold
Attendant waiting guide

➨ This concerns the voice guide broadcast during an external
call overflowing on no answer by the attendant (by default:
voice guide 110)


19
Multi-
Multi-entities
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 according to the calls distribution table of
the trunk group’s entity.


20
Multi-Entities

OBJECTIVE:
◆ To describe and set-up a multi-entities configuration

Ref. ENTP0417C02TEUS Issue 01
21
Multi-
Multi-Entities
Management
Entity management
➨ /Entities /Review modify
▼ Entity number:
▼ Name:
▼ Attendant group manager:
▼ Priority:
▼ Traffic Overflow
▼ Installation N° (ISDN):
▼ Supplement. install N° (ISDN):
▼ Caller identity secret:

Entity number:
This number identifies the entity: user sets, attendant sets, group of sets, trunk circuits, automatic switchboard associated with this
number will use the corresponding characteristics
It is also used by the entity call prefix. The user dialing this prefix will see his call routed towards the numbers contained in the the
routing table of the entity assigned to this prefix.
Note that the general attendant call prefix works differently. The user dialing this prefix will see his call routed towards numbers
contained in the routing table it belongs to.
Comment: The entity 0 receives all calls where the entity is not identified (wrong number dialed, ABC-F link cut off during call)
Name: The name of the company or department corresponding to this entity. This name is displayed on internal sets and on private
network sets.
Attendant group manager: the entity state change according to the attendant group status .
Priority: YES The calls from trunk groups of this entity are declared priority: they immediately go into the PRIORITY state.
Traffic overflow: used for mutual help between attendants .
Installation n° (ISDN): This index contains the first digits of the company directory numbers preceding the DDI numbers (company
numbers root). This number, followed by a DDI set number( see additional installation number) is transmitted if user is in ”sending
identity” state.
Supplement installation N° (ISDN): This index contains the DDI set number for the attendant, as well as the installation n° and
the supplement installation n° representing the official complete number for the company
- If user is non-DDI this “ancillary installation number” is transmitted following the «installation number»
- If user is DDI: the number of the caller’s DDI set is transmitted instead of the “ancillary installation number” is
transmitted following the «installation number»
Caller identity secret: Send: if the subscriber has not the right to the secret identity prefix, no identifying number is transmitted.

22
Multi-
Multi-Entities
Management
Entity management
➨ /Entities /Review modify
▼ Adv.Of Charg.2 requests(AOC2):
▼ Adv.Of Charg.3 requests(A0C3):
▼ Auto. Locking: 0
▼ Voice Mail Box No.for attendt: 31990

Adv.Of Charg.2 requests(AOC2): YES: the users who have right to service are informed in real time of the number of meter pulses
relative to the outgoing communication.
Adv.Of Charg.3 requests(A0C3):YES: the users who have right to service are informed at the end of the communication of the
number of meter pulses relative to the outgoing call.
Auto. Locking: (0 or 1 ): the sets of this entity change over to automatic locking mode at the next state change, except if the next
state is DAY.
Voice Mail Box No.for attendt: This voice mail box number is used by the attendant to record a conversation

23
Multi-
Multi-Entities
Management
Entity management
➨ /Entities/Review modify
➨ Call distribution
▼ Overflow routing N°:
▼ Forwarding on routing + YES
▼ 1st night routing:
▼ 1st day routing:
▼ 1st Mode 1 routing:

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 (see routing numbers attribute).
The directory numbers cannot be transferred in the following cases:
- multi-line number,
- hunting group number (as well as integrated directory numbers in hunting groups),
- SO set numbers
Forwarding on routing :
no: if the routing overflow number (see this attribute) of any trunk circuit is also entered in one of the routing numbers
(Night, Day, transfer 1, transfer 2) transfer is direct on this overflow number without taking other routing or overflow numbers into
account.
yes: normal operating: transfers on routing numbers
Inform routings for each set-up state Day/Night/State 1/State 2 + routing overflow n°.
Remark: For the other attributes, see the Database Management documentation - chapter « Entity »

24
Multi-
Multi-Entities
Management
Entity management
➨ Call Priority
▼ Normal Public Trk grp Ent.: 6
▼ Urgent Public Trk grp Ent.: 5
▼ Normal Private trk grp Ent.: 10
▼ Urgent Private Trk grp Ent.: 9
▼ Normal Public DDI Entity: 6
▼ Urgent Public DDI Entity: 5
▼ Normal Private DDI Entity: 10
▼ Urgent Private DDI Entity: 9
▼ Normal Int Callee DDI Entity: 12
▼ Urgent Int Callee DDI Entity: 11
▼ Normal Public Non Answer DDI: 4
▼ Urgent Public Non Answer DDI: 3
▼ Normal Private Non Answer DDI: 8
▼ Urgent Private Non Answer DDI: 9

Entity Calls Priority:

This information concerns the priority order according to the origin type of the entity calls.
The call types with identical priority are presented in their order of arrival.
The values indicate the standard priority order (values by default).
higher priority: 0,
Low priority: 14.
A priority is affected to attendants calls. This priority is used to classify the calls in the attendants waiting queues.
The call priority has 2 levels:
A priority is affected to each traffic presentation class,
A priority is affected in each traffic presentation class according to the call origin: private public or local.
A call has the priority when its priority is inferior. The maximal priority is 0.

25
Multi-
Multi-Entities
Management
Entity management
Voice guides
➨ Waiting Guide: 2
➨ Operator Waiting Guide: 110
➨ Overflow Timer: 200
➨ Company Call Number: 34
➨ Centrex Centralised Serv. + False
➨ Overflow LDAP Phone Book: -1

Waiting Guide: This information concerns the voice guide transmitted during a local hold.The waiting guide is by default the
number 2.
Operator Waiting Guide: This information concerns the voice guide transmitted by the attendant during an external call
overflowing on no answer.
Overflow timer: The time after which a call overflows to the overflow routing number, when the entity call has not been successful.
Company Call Number: Use in case of Centrex feature ( multi company ) validation ( see System/other system parameters / Spec.
Customer Features Parameters /
Centrex -> On ) . This information defines the root of the local extension number. In this case, all the local extension numbers must
start with 34.
Note: to modify this information, there is no extensions allocated in the entity .
Centrex Centralised Serv: This attribute is used by the Centrex application (Multi-company).
TRUE: the company is of the common type, i.e. it can access the entire directory (DIRECTORY object).
FALSE: the company is of the normal type, i.e. it can only access its own users in the directory.
Overflow LDAP Phone Book: index of LDAP server which has been created in: / applications /LDAP phone books

26
Multi-
Multi-Entities
Management
Management of the «entity call» prefix

➨ /Translator/prefix plan
▼ Number:
▼ prefix meaning: entity call
▼ Information:

Number: corresponds to entity call number
prefix information: entity number

27
Multi-
Multi-Entities
Management
Changeover times management for incoming calls

➨ /Entities/Descend hierarchy/Entity incoming state hours
▼ Monday
✦ changeover 1
Hour
Minute
State
✦ changeover 2
✦ changeover 3
✦ changeover 4
▼ Tuesday
▼ Wednesday
▼ Thursday
▼ Friday
▼ Saturday
▼ Sunday

Example:
changeover 1: Day’s first time division.
For each division, hour and minute of start time must be indicated.
hour: hour of start of changeover
Minute: Minute of start of changeover
State: Status of entity Day/Night/State 1/State 2/attendant group during changeover division 1
Manage the changeover times like the changeover 1.

28
Multi-
Multi-Entities
Management
Changeover times management for outgoing calls

➨ /Entities /Descend hierarchy/entity outgoing state hours
▼ Monday
✦ changeover 1
Hour
Minute
State
✦ changeover 2
✦ changeover 3
✦ changeover 4
▼ Tuesday
▼ Wednesday
▼ Thursday
▼ Friday
▼ Saturday
▼ Sunday

Example:
changeover 1: Day ’s first time division.
For each division, hour and minute of start time must be indicated.
hour: hour of start of changeover
Minute: Minute of start of changeover
State: Status of entity Day/Night/State 1/State 2/attendant group during changeover division 1

29
Multi-
Multi-Entities
Management
Attendant waiting guide
➨ Attendant waiting guide (pre-off hook guide) defined per

entity
▼ Operator waiting guide:110
➨ Notes: If default 110 voice guide is not used, manage the

parameter:
➨ /System/Other System Param/Attendant parameters/

no answered call entity guide: yes


30
Multi-Entities

OBJECTIVE:
◆ To maintain a multi-entities configuration

Ref. ENTP0417M02TEUS Issue 01
31
Multi-
Multi-Entities
Maintenance
Display 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
Display the entity’s CDT

➨ Command: cdtstat <identification number>

ednump: Parameters:
-dir: prefix number
-mean: prefix meaning
cdtstat: identification number (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

32
Multi-
Multi-Entities
Maintenance
Display entity’s changeover times parameters
➨ Command: entitystat <entity number> -b

▼ Entity’s parameters
▼ Outbound time table
▼ Inbound time table

Option -b of entitystat provides time tables for outgoing and incoming calls.

33

34
Multi-Entities
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to modify one existing entity
MANAGEMENT
1. Create 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 calls distribution.
When the entity is in night position, the extension set 3x005 will be the night service set.
Issue 01 REF. ENTP0417H02TEUS.doc HO.1

35
Multi-Entities
4. We decide to improve the management:

4.1 The status of the entity 1x 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
HO.2 REF. ENTP0417H02TEUS.doc Issue 01

36
Alcatel University NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
Alcatel University – https://www.businesspartner.alcatel.com
37
NOTES Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
38
Multi-Translator / NPD

OBJECTIVES:
◆ To describe and modify DDI translator
◆ To setup multi-translator for DDI transcoding
Alcatel OmniPCX Enterprise – Multi-Translator / NPD

39
Multi-
Overview
Purposes
➨ to translate an incoming call (I/C)
➨ to send an appropriate identity (O/G)
Vocabulary rules
➨ Installation Number: Installation Identity Number
➨ Supplementary Installation Number: User Identity Number
➨ e.g.: 021403 1000
Inst. Nb Supplement. Inst. Nb
Default setup
Suppl.Inst.Nbr.
➨ The Installation Number is assigned in the entity of the caller


40
Multi-
Overview
Principles
➨ The Numbering Plan Descriptor (NPD) is used
▼ to translate the number received: incoming calls
▼ to build the Inst. Nb+Suppl. Inst. Nb.: outgoing calls
➨ NPD selection in case of incoming calls

▼ depends on the call type: public or private (byte 3 value)
➨ NPD selection in case of outgoing calls

▼ depends on the trunk group seize prefix
▼ depends on the ARS table
➨ In the NPD object, a DID translator is associated for

incoming and outgoing calls.
In the DID translator, the translation rules are defined for
the Supplementary Installation Number.

The NPD from 0 up to 32 are reserved for the system. They are created after empty database.
The NPD from 33 up to 49 do not exist and can be created by the manager.
DID=Direct Inward Dialing

The DID translator 0 is a default one. This DID translator is not broadcasted and is used by default in some NPD.
The other DDI translators (from 1 up to 99) can be created by the manager and allocated in manager NPD. They are broadcasted all
over the network without their rules.
It is possible to manage one DID translator for the O/G calls and one DID translator for the I/C calls.

41
Multi-
Overview
NPD contents
Node-Network number (reserve soft): 101

Instance (reserve soft): 1
Instance (reserve soft): 1
Descriptor Identifier: 14
Name: U_IN_E_E_NDDI
Calling Numbering plan Id + NPI/TON Isdn National
Called Numbering plan Id + Unknown
Authorize personal calling num use + None
Install Nb source + Entity Source
Installation number:
Default number source + Entity Source
Default Instal. Number:
Called DID identifier: -1
Calling/Connected DID identifier: -1

Name: 16 characters-string, friendly way to identify the NPD
Called DDI identifier: gives the DID translator number which is used for the called party translation.
-1 means that no translation will be done
Calling DDI identifier: gives the DID translator number which is used for outgoing calls to build the calling and connected party
this DID translator can be different than the called DDI identifier
-1 means that no translation will be done
Authorize personal calling num. use:

indicates if the system checks or not in the user management the field for specific Suppl. Inst. Nbr.
YES: allows use of a directory number (source No.) managed in the user data (e.g. GSM number,
secretary number for the boss, etc.).
Installation Nb source: Defines what is the Inst. number to add to the user number (Suppl.Inst.Nbr.)
none = none
Entity source = Installation Nb in the entity
NPD source= Installation Nb managed in the NPD
Installation number: Inst.Nbr.I to put if source is NPD
Default number source: Defines what is the supplementary installation number

none = none
Entity source = default Installation Nb in the entity
NPD source = default Installation Nb managed in the NPD
Default Nb (supl. inst): default supplementary number to send for none DID users if Default installation Nb source is NPD

42
Multi-
Overview
NPD use for O/G
➨ Direct seize prefix:

▼ an information «public or private» associated to the prefix allows to
select two possible NPDs (public and private) assigned in the trunk
group
➨ Sub-menu in the trunk groups:

▼ Trunk group NPD selector
✦ allows to assign the public and private NPD Number.
➨ ARS route list:

▼ An NPD number can be managed in each route
▼ the default value is 255, it means the NPD used is the one in the
trunk group selected through the ARS
▼ if a different value is managed, it takes priority over the one in the
trunk group


43
Multi-
Overview
Example 1: Entity installation number sent (default

configuration)
Identification Nb
Identification Nb sent TG
32000 received
0214032000 0214032000
Entity 2
ENTITY
ENTITY22
³³Installation CO
InstallationNb:
Nb:02140
02140


44
Multi-
Overview
Example 2: installation number not sent
Identification Nb
TG
32000 Identification Nb sent received
32000 32000
Entity 2
CO
ENTITY
ENTITY22
³³Installation
InstallationNb:
Nb:02140
02140

If CO does not accept installation number from PABX.

45
Multi-
Overview
Example 3: installation number sent but different

according to the entities
Identification Nb
TG
0000032000 0000032000
Entity 2
CO
ENTITY
ENTITY22
³³Installation
InstallationNb:
Nb:02140
02140


46
Multi-
Overview
Example 4: private numbers managed in user
Identification Nb
32000 received
0612345678 0612345678
Entity 2
CO
ENTITY
ENTITY22 USER
USER32000
32000
³³Installation
InstallationNb:
Nb:02140
02140 ³³Use
Useofofpersonal
personalcalling
callingnum:
num:yes
yes
³³Private calling Number:0612345678
Private calling Number:0612345678

Authorize private data use: Indicates if the system checks or not the specific Suppl. Inst. Nbr. is user management
example: cell phone, secretary number

47
Multi-
Overview
Example 5: Different installation number depending on the

TG used
0000032000
or
2222232000
200
0 CO
003
000
TG 20
200
223
32000 222
32000 TG 21
Entity 2
TG 20
TG 20
ENTITY
ENTITY22
³ NPD installation Nb: 00000
³³Installation
InstallationNb:
Nb:02140
02140 TG 22
TG 22


48
Multi-
Overview
Example 6: Selection of NPD (public/private) by prefix
2222232000
or
3333332000
200
0 CO
223
222
00
TG 21
33 32 0
‘#022’ 333
‘#023’
32000
Entity 2
prefix
prefix#022
#022
³ public prefix
³ public prefix
³ Public NPD installation Nb: 22222
³ Public NPD installation Nb: 22222
prefix
prefix#023
#023
³ private prefix
³ private prefix
³ Private NPD installation Nb: 33333
³ Private NPD installation Nb: 33333


49
Multi-
Overview
Example 7: Selection of the NPD through the ARS
5555532000
CO
TG 22
‘0’
0
555553200
32000
Entity 2
ARS
ARSprefix
prefix ARS
ARSroute
route
³0 ³NPD Nb 41
³0 ³NPD Nb 41 TG NPD number ignored
NPD
NPD41
41
installation Nb: 55555 TG 22
installation Nb: 55555 TG 22


50
Multi-
Overview
NPD used in I/C call:
➨ The NPD selection depends on the information received into

the SETUP message
▼ Private: Private NPD of the incoming trunk group
▼ Other values: Public NPD of the incoming trunk group

NPI: Numbering plan descriptor is one of the field of the information elements with telephone number type in the Q931 messages.
The interesting values of the NPI are:
- Unknown
- ISDN Numbering plan and Private Numbering plan

51
Multi-
Overview
Example 1: I/C call on a DID set
Number dialed:
0214032200
TG 22
TG 22
³ DDI Transcoding: Yes
DDI
DDItranslator
translator
CO
³³external Nb:32200
externalNb: 32200
internal Nb:32000
³³internal Nb: 32000 TG 22
‘0214032200’
32000

When the DDI transcoding is set to yes the system checks the DDI translator in the NPD
When the DDI transcoding is set to no the system doesn’t use any DDI translator

52
Multi-
Overview
Example 2: Force calls to the attendant in case of

incoming call on non DID users
TG 22 Number dialed:
TG 22
³ DDI Transcoding: Yes 0214032025
DDI
DDItranslator
translator
³³external Nb:32020
externalNb: 32020
internal Nb:32018
³³internal Nb: 32018
³³Range
Rangesize:
size:100
³³Unique
100 CO
UniqueNb: Nb:Yes
Yes
TG 22
‘0214032025’
32018
Attendant Set
Att.
Att.Group
Group
32018
32018


53
Multi-
Overview
Example 3: Non DDI sets
32000 Identification send

DDI 0214032000
TG 22 CO
Identification sent TG 22
TG 22
0214032018 ³ DDI Transcoding: Yes
32025 ³ NPD installation Nb: Entity source
³ NPD installation Nb: Entity source
Non DDI ³ Default number source: Entity source
³ Default number source: Entity source
DDI
DDItranslator
translator
ENTITY 2
ENTITY 2 ³³external
externalNb:Nb:32000
32000
³ Installation Nb: 02140
³ Installation Nb: 02140 ³³internal
³ Suppl. installation Nb: 32018
³ Suppl. installation Nb: 32018 internal Nb:32000
Nb: 32000
³³range
rangesize:
size:20
20
³³Unique
UniqueNb: Nb:NoNo


54
Multi-
Overview
Example 4: Force the callbacks on two different carriers
Carrier 1 Carrier 2
020
103
0
2 20
03 TG 20
2
01 TG 20
200
2 ³ NPD installation N°: 02010

33 ³ NPD installation N°: 02010
00
TG 20 TG 22
DDI
DDItranslator
translator
³³external N°:32200
externalN°: 32200
³³internal N°:32000
internalN°: 32000
TG 22
TG 22
³ NPD installation N°: 00332010
³ NPD installation N°: 00332010
DDI translation for I/C

32000
DDI translation for O/G

TG 20
For incoming call through TG 20, the number 0201032200 which is used to call 32000 ( I/C DDI translation is necessary ) translates
32200 into 32000.
For outgoing call the installation number and the supplementary installation number must be 0201032200 ( needs reverse
translation ).
TG 22
For incoming call through TG 22, the number 6732000 is used to call 32000 (no translation).
If 32000 makes an outgoing call through the carrier 2 (TG 22), the system has to send the identity of the French operator (installation
number and supplementary installation number), it means the number: 0033201032200.

55

56

OBJECTIVES:

57
Multi-
Management
Trunk groups parameters
➨ /Trunk groups/Review modify

▼ global parameters
✦ Trunk Group Id: 10
DDI transcoding: True / False
➨ /Trunk groups/Descend hierarchy/Trunk group NPD

selector /Review Modify
✦ Trunk Group Id: 10
Public NPD id : 14
Private NPD id : 11
Configuration Mode + Automatic
Public DDI Transcoding + False

Configuration mode:
Automatic: automatic allocation of the NPD 2 (no transcoding) and the NPD 3 (with transcoding)
Normal: possibility to assign a different NPD number than the 2/3

58
Multi-
Management
Translators parameters
➨ /Translator/Automatic Route Selection/ARS route

list/Descend hierarchy/ARS route/Review modify
✦ ARS Route List:
✦ Route:
NPD Identifier: 255 or NPD value

By default the NPD value is 255, it means that the system will select the NPD managed in the TG of the ARS Route.
If a value different than 255 is managed, it takes priority over that of the TG.

59
Multi-
Management
NPD parameters
➨ /Translator/External dialing plan/Dialing Plan

Description/Review modify
✦ Description identifier: 14
✦
Name: U_IN_E_E_NDDI
Calling Numbering plan ident+ NPI/TON Isdn National
Called numbering plan ident. + Unknown
Authorize personal calling num use + False
Install. number source + Entity source
Default number source + Entity source
Called DID identifier: -1
Calling/Connected DID identifier: -1


60
Multi-
Management
Translators parameters
➨ /Translator/ External dialing plan
/DDI number translator/Create
DDI num. transl. identifier :4

Name : my translator
➨ /Translator/ External dialing plan

/DDI number translator/Descend hierarchy
/DID number translator rules/Create
DDI num. transl. identifier :4

First External Number : 32000
First Internal Number : 32200
Range Size : 50
Unique Internal Number : NO


61
Multi-
Management
Entities parameters
Entity number:
Installation No (ISDN):
Supplement.Install.No (ISDN):
Users parameters
➨ /Users/Review modify
Directory number:
Use personal calling number use: Yes / False
Private Calling Number:


62
Multi-
Management
Basic management
➨ /Trunk groups
▼ DDI transcoding: Yes
➨ Find the NPD automatically allocated in TG
➨ Check that the NPD uses the default DDI translator (0)
➨ Manage the default translator 0


63
Multi-
Management
Specific management of the DDI transcoding
➨ Manage one specific DDI translator (1 up to 100)
➨ Manage one specific NPD that will use the DDI translator
created before
➨ Associate this NPD to the concerned trunk groups
➨ Check that the system has automatically validated the DDI

transcoding in the trunk groups


64
Multi-
Management
Outgoing example 1: Entity installation number
Identification Nb
32000 received
0214032000 0214032000
Entity 2
Trunk group 20
Trunk group 20
³ Public NPD 14 (default value)
³ Public NPD 14 (default value)
CO
ENTITY 2 Translator/NPD 14
ENTITY 2 Translator/NPD 14
³Installation Nb ³ Install. number source + Origin entity
³Installation Nb ³ Install. number source + Origin entity
02140 ³Called DID identifier: -1
02140 ³Called DID identifier: -1
³Calling/Connected DID identifier: -1
³Calling/Connected DID identifier: -1


65
Multi-
Management
Example 2: Installation number not sent
Identification Nb
Identification Nb sent TG 20
32000 received
32000 32000
Entity 2
Trunk group 20 CO
Trunk group 20
³ Public NPD 33
³ Public NPD 33
ENTITY 2 translator/NPD 33
³Inst Number (ISDN) ³ Install. number source: None
³Inst Number (ISDN) ³ Install. number source: None
02140
02140 ³ Default number source: None
³ Default number source: None


66
Multi-
Management
Example 3: Installation number sent but different as the

one managed in the entity
TG 20 Identification Nb
0000032000 0000032000
Entity 2
TG 20
ENTITE 2 TG 20
ENTITE 2 ³ Public NPD: 33
³ Inst. Number (ISDN) ³ Public NPD: 33
³ Inst. Number (ISDN)
02140
02140
CO
translator/NPD 33
translator/NPD 33
³ Install. number source: NPD
³ Install. number source: NPD
³ Installation number: 00000
³ Installation number: 00000


67
Multi-
Management
Example 4: Non DID sets
32000 Identification send

DDI 0214032000
TG 22
CO
TG 22
TG 22
³ Public NPD 3
³ Public NPD 3
Identification sent
0214032018
32025
Non DDI
ENTITY 2
ENTITY 2
³ Installation Nb:02140 translator/NPD 3
³ Installation Nb:02140 translator/NPD 3
³ Supplem. Instal. Nb: 32018 ³ Install. number source + Origin entity
³ Supplem. Instal. Nb: 32018 ³ Install. number source + Origin entity
³ Default number source+ Origin entity
³ Default number source+ Origin entity
³ I/C DDI Id: 0
Default DDI translator ³ I/C DDI Id: 0
Default DDI translator ³ O/G DDI Id: 0
³ 1st external Nb: 32000 ³ O/G DDI Id: 0
³ 1st external Nb: 32000
³ 1st internal Nb: 32000
³ 1st internal Nb: 32000
³ Range size: 20
³ Range size: 20
³ Unique internal Nb: NO
³ Unique internal Nb: NO

NDDI = non DID

68
Multi-
Management
Example 5: private numbers managed in user
Identification
Identification Number TG 20
32000 Number received
sent 0612345678
Entity 2 0612345678
TG 20
TG 20
³ Public NPD 33
³ Public NPD 33
User 32000
User 32000
³ Use personal calling N°: yes
³ Use personal calling N°: yes CO
³ Private calling N°:0612345678
³ Private calling N°:0612345678
translator/NPD 33
translator/NPD 33
³ Install. number source + Origin entity
³ Install. number source + Origin entity
³ Authorize personal calling num use + YES
³ Authorize personal calling num use + YES


69
Multi-
Management
Example 6: Different installation numbers depending on

the TG used
0000032000
or
2222232000
200
0 CO
003
TG 20 000
0
2 3200
2222
32000 TG 21
32000
Entity 2
TG 20 TG 21
TG 20 TG 21
³ Public NPD: 34 ³ Public NPD: 33
ENTITY 2 ³ Public NPD: 34 ³ Public NPD: 33
ENTITY 2 translator/NPD 34 translator/NPD 33
³ Installation Nb: 02140 translator/NPD 34 translator/NPD 33
³ Installation Nb: 02140 ³ Install. number source:NPD ³ Install. number source:NPD
³ Install. number source:NPD ³ Install. number source:NPD
³ Installation Nb: 00000 ³ Installation Nb: 22222
³ Installation Nb: 00000 ³ Installation Nb: 22222


70
Multi-
Management
Example 7: Selection of NPD (public/private) by prefix
2222232000
or
3333332000
prefix prefix
prefix prefix
³ #022 ³ #023
³ #022 ³ #023
³ TG 20 ³ TG 20
³ TG 20 ³ TG 20
³ public ³ private
³ public ³ private
200
0 CO
223
222
00
TG 21
33 32 0
‘#022’ 333
‘#023’
32000
Trunk group 21
Entity 2 Trunk group 21
³ Public NPD : 33
³ Public NPD : 33
³ Private NPD: 34
³ Private NPD: 34
translator/NPD 33 translator/NPD 34
translator/NPD 33 translator/NPD 34
³ Install. number source: NPD ³ Install. number source: NPD
³ Install. number source: NPD ³ Install. number source: NPD
³ Installation N°: 22222 ³ Installation N°: 33333
³ Installation N°: 22222 ³ Installation N°: 33333


71
Multi-
Management
Example 8: NPD selection through the ARS
5555532000
CO
TG 22
‘0’
0
555553200
32000
Entity 2
ARS prefix ARS table #1 translator/NPD 35

ARS prefix ARS table #1 translator/NPD 35
³0 Route 1 ³ Install. number source: NPD
³0 Route 1 ³ Install. number source: NPD
³ Discrim.Nb:0 Trunk group: 22 ³ Installation Nb:55555
³ Discrim.Nb:0 Trunk group: 22 ³ Installation Nb:55555
NPD Identifier: 35
NPD Identifier: 35


72
Multi-
Management
Example 9: Force the callback on one CO
Callback
Callbackon
onCO1
CO1
0214032000
0214032000
C02
C01
00
40 32 0
021
TG 20
00
40 32 0
TG 21 021
TG 21 TG 20
TG 21 TG 20
32000 ³ Public NPD: 33
³ Public NPD: 33
³ Public NPD: 33
³ Public NPD: 33
Entity 2
³ Installation Nb ³ Installation number source:Entity source
³ Installation Nb ³ Installation number source:Entity source
02140
02140

This example can only be managed in the training center.

73
Multi-
Management
Incoming example 1:
Number dialed:
0214032200
CO
TG 22
‘0214032200’
TG 22
TG 22
³ Public NPD 15
³ Public NPD 15
³ DDI Transcoding: yes
32000 ³ DDI Transcoding: yes
Default DDI translator translator/NPD 15

Default DDI translator translator/NPD 15
³ 1st external Nb:32200 ³ Installation number source + Origin entity
³ 1st external Nb:32200 ³ Installation number source + Origin entity
³ 1st internal Nb: 32000 ³ I/C DDI Id: 0
³ 1st internal Nb: 32000 ³ I/C DDI Id: 0
³ Range size: 100 ³ O/G DDI Id: 0
³ Range size: 100 ³ O/G DDI Id: 0


74
Multi-
Management
Example 2: Force calls to the attendant in case of

incoming call on non DID numbers
Number dialed:
0214032025
TG 22
CO
32018
Attendant Set
‘0214032025’
TG 22
Att. TG 22
Att.Group
Group ³ Public NPD 3
³ Public NPD 3
32018
32018 ³ DDI Transcoding: Yes
DDI translator Id 1 translator/NPD 3

DDI translator Id 1 translator/NPD 3
³ 1st external N°: 32020 ³ Install. number source + Origin entity
³ 1st external N°: 32020 ³ Install. number source + Origin entity
³ 1st internal N°: 32018 ³ Default number source + Origin entity
³ 1st internal N°: 32018 ³ Default number source + Origin entity
³ Range size: 100 ³ I/C DDI Nb: 0
³ Range size: 100 ³ I/C DDI Nb: 0
³ Unique internal Nb: yes ³ O/G DDI Nb: 0
³ Unique internal Nb: yes ³ O/G DDI Nb: 0

Note: 32018 is here an “Attendant group call” prefix

75

76

OBJECTIVES:

77
Multi-
Maintenance
Command: looknpd –h
➨ looknpd i: Interactive mode to find the npd used
➨ looknpd n NPD_Number:
Lists the content of the numbering plan descriptor
➨ looknpd n all:
Displays all the numbering plan descriptors defined on the
local node


78
Multi-
Maintenance
Command: looknpd i
(101)xa001001> looknpd i
Outgoing Prefix: #012
Directory Nb : 31000
Trunk seizure case, entity Nb = 1, TG Nb = 12 with lignpriv = FALSE: publicNPD used

====================================================================
| NUMBERING PLAN DESCRIPTOR No 14 |
====================================================================
| Calling NPI TON = 21 : TON: National Nb NPI: ISDN / Telephony
| Called NPI TON = 00 : TON: UNKNOWN NPI: UNKNOWN
| Incoming DID identifier = -1
| Outgoing DID identifier = -1
| Authorise private data use = 0 : FALSE
| Used Installation Number = 0 : ENTITY SOURCE ==> 02140
| Used Default Number = 0 : ENTITY SOURCE ==> NOT DEFINED !!!!
| Installation Number = Not Defined / Not Used
| Default Number = Not Defined / Not Used
====================================================================


79

80
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage NPD
MANAGEMENT
OUTGOING CALLS
1. Users send identity as followed for all outgoing calls:

Inst. Nbr.: 02cc0
cc: Classroom number
Supl. Inst.Nbr.: the user directory number
2. Users send only their Suppl.Inst.Nbr. (no Inst.Nbr.).
3. On T0 trunk group, Inst. Nbr is 00000.

On other trunk groups, Inst.Nbr is 02cc0.
4. The user 3x000 must send the Supl.inst.Nbr. 3x008 (attendant directory number) for all
outgoing calls.
5. The user 3x000 sends:

- 02cc1 + 3x008 for T0 outgoing calls,
- 02cc0 + own directory number for T2 outgoing calls.
6. When users seize T2 trunk group:

- they send Inst. Nbr. 02cc0 using prefix #0n2,
- or they send 02cc1 using prefix #0n3.

81
INCOMING CALLS
1. Manage a parallel hunting group with the directory number 3x009. Assign the analog users
3x010 and 3x011 in it.
When these analog users call an outside number the system send Inst.Nbr. from entity plus
their directory numbers.
An incoming external call on these numbers must be directly routed to the hunting group
3x009.
2. UA users are DDI numbers and analog users are NDDI.

- When the analog sets seize T0 trunk group they send the Suppl.Inst.Nbr. of the attendant.
- When they seize the T2 trunk group they send the Suppl.Inst.Nbr. defined in their entities
(attendant group directory number).

82
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
83
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
84
ARS – Time based

OBJECTIVE:
◆ To describe the ARS with time table
Alcatel OmniPCX Enterprise – ARS – Time based

85
ARS
Overview
The ARS feature is protected by a software lock
The ARS is used to:

➨ choose the less expensive external line depending on:
▼ the number dialed
▼ the time
➨ access to an indirect carrier
The choice of the route depends on the number dialed
Chapter’s content:
➨ the choice of the route depending on the time
➨ the access to an indirect carrier


86
ARS
Overview
The default management can be updated:

➨ to customize the access to the routes depending on the time
➨ to enable the access to an indirect carrier
First step: the route lists have to be updated:

➨ routes available, with or without indirect carrier access
➨ list of routes available in the time based route lists
➨ several time based route lists in case of time-based ARS
Second step: the outside numbers have to be updated:

➨ route list used depending on the number dialed

Note: one or several new ARS route lists can be created if more than 2 different route lists have to be used.

87
ARS
Overview
Time based ARS: principles
➨ One external number dialed by a user can be associated to

one ARS route list and one ARS schedule
➨ One ARS route list can contain up to 10 different routes
➨ One route can be associated to one carrier
➨ The route order is defined in a time based route list
➨ Each ARS table can have up to 8 time based route list ( 8

different route orders for each ARS route list )


88
ARS
Overview
Example: call of the outside number 0039….
➨ In the real discriminator:
▼ call number: 0039

▼ area number: 3 (for barring purpose)
▼ ARS route list number: 12 (routes available for those calls)
▼ ARS schedule number: 28 (used to choose the right time based route
list depending on time)

The (-1) default value means that, for this destination number, the route list selection is not day /time dependant. Therefore, the call
shall be established according to using obviously, the route list number found in the translator and the default time based route list
(N°1).

89
ARS
Overview
Example: The outside number 0039 is associated to the

ARS route list 12
➨ Content of the table 12
Routes Route 1 Carrier 1

definition
Route 2 Carrier 2
Route 3 Carrier 3
. .
. .
Route 10 Carrier X
Time based Time based 1st Route Route 3

Route order route list route list
N°1
definition 2nd Route Route 1
3rd Route Route 2
.
.
10th Route Route 10

The carrier will be used in the following order:

1) Carrier 3
2) Carrier 1
3) Carrier 2

90
ARS
Overview
8 different time based route lists maximum in each ARS

route list
Time based 1st Route Route 3
route list
N°1
2nd Route Route 1
3rd Route Route 2
.
.
Routes Route 1 Carrier 1
definition 10th Route Route 10
Route 2 Carrier 2
Route 3 Carrier 3
Definition of the
carrier use
. . order
. .
Route 10 Carrier X
route list
N°8
2nd Route Route 3
3rd Route Route 1
.
.
10th Route Route 10


91
ARS
Overview
Example: The external number 0039 is associated to the

ARS route list 12 and to the ARS schedule 28
ARS schedule number: 28
Name of the ARS schedule: Italy

Day SA SU MO TU WE TH FR BH1 BH2
ARS time table
number 1 2 3 3 3 3 3 4 4
route list
ARS route list 12 N°1
2nd Route Route 1
ARS time table N°5
3rd Route Route 2
Heure de début de Numéro de la route
tranche
ARS time table N°4
temporelle
Routes Route 1 Carrier 1 .
definition . Heure de début de Numéro de la route
Route 2 Carrier 2 10th Route Route 10
00:00
tranche ARS time table 1 N°3
temporelle
Heure deARS
débuttime
de Numéro de la route
Route 3 Carrier 3 00:00
tranche 08:00
table 1 N°2
temporelle8
. . ARS
00:00
08:00 time table 1 8N°11
. . tranche 18:00 temporelle
Route 10 Carrier X route list Beginning of the Time based route list N°
N°8 Time 00:00
slice08:00
18:00
1
8 1
2nd Route Route 3
00:00
08:00 1 8
3rd Route Route 1 18:00 1
.
.
08:00
18:00 8 1
10th Route Route 10
18:00 1

On Saturday at 8:30 AM, one user dials the external number 0039XXXXXXXX.
The ARS schedule 28 indicates that the time based route list to use is the number 8.The ARS route list associated to the dialled number
indicates that in the time based route list 8, the first route to use is the one corresponding to carrier N°2.

92
ARS
Overview
ARS schedule description
ARS schedule N°: 28
ARS schedule name: Italy

Day SA SU MO TU WE TH FR BH1 BH2
ARS time table (1 to 5) ARS time table
number 1 2 3 3 3 3 3 4 4
ARS time table N°5
les
Heure de début de
ARS time tableNuméro de la route
N°4
tab
tranche temporelle

00:00
trancheARS time tabletemporelle
1 N°3
5
ARS
00:00 time
tranche 08:00
table 1 N°2
temporelle8
ARS
00:00 time table
08:00 1 8N°11
tranche 18:00 temporelle
Beginning of the Time based route list
00:0008:00 1
number
time slice 18:00 8 1
00:00
08:00 1 8
18:00 1
24 time
slices max 08:00
18:00 8 1
18:00 1

Each day type is associated to one ARS time table number.

When an ARS time table is not necessary for a specific day, the ARS time table number has to be set-up to -1.
In this case, the call will be routed according to the ARS route list and according to the default time-based route list managed in the
ARS table.

93
ARS
Overview
A calendar exists for ARS and for time-based route list
➨ It is used to determine the bank holidays
▼ Bank holiday 1 and 2
➨ The fixed Bank Holidays are listed for the current year
➨ The not fixed Holidays can be managed for:
▼ the current year
▼ for the next years

To deal with particular international networks where a day is not necessary a bank holiday in many countries, the OmniPCX Enterprise
calendar offer 2 kinds of bank Holiday which are named BH1 and BH2.
The manager can also use these bank holiday to define the operator special offer days, different from bank Holiday.

94
ARS – Time based

OBJECTIVE:
◆ To put into operation the ARS with time table

95
ARS
Management
Outside line prefix

➨ Translator / Prefix plan / Review modify
▼ Parameters:
✦ Number: 0 or 9
✦ Prefix meaning: ARS prof. trk. grp. seiz. with overlapping
✦ Discriminator nb.: 0
Logical discriminator in the users’ entity

➨ Entities / Descend hierarchy / Discriminator selector /
Review modify
▼ Parameters:
✦ Entity number:
✦ Discriminator 00: 0


96
ARS
Management
Outside numbers in the discriminator 0 ( public

discriminator )
➨ Translator / External Dialing Plan / Dialing (Numbering)
discriminator / Descend hierarchy / Discriminator rule
/Review modify
✦ Discriminator number: 0
✦ Call number: 02 <first digits of the outside number>
✦ Dialing Area: 1 (used for barring)
✦ ARS route list number: 1
✦ Schedule number: -1
✦ Number of digits: 10 (external number format)
ARS route list 1

➨ Translator / Automatic route selection / ARS route list /
Review modify
✦ ARS route list: 1
✦ Name: Route_list_1


97
ARS
Management
Routes in the ARS route list

➨ Translator / Automatic route selection / ARS route list
/ Descend hierarchy / ARS route / Review modify

✦ Route: 1
✦ Name: Route_1
✦ Trunk group: 18
✦ Quality + Speech

✦ Route: 2
✦ Name: Route_2
✦ Trunk group: 16
✦ Quality + Speech


98
ARS
Management
Time based route list in the ARS route list

Descend hierarchy / Timed-based route list / Review modify

✦ Time-based route list id.: 1
✦ Route Number: 1
✦ Waiting cost limit: -1
✦ Stopping cost limit: -1
[ Next ]
✦ Route Number: 2


99
ARS
Management
Results: when a user uses the ARS prefix 0 (or 9) to

establish an outgoing call starting with 02:
▼ access to the discriminator 0
▼ according to the discriminator 0, access to the ARS route list 1
▼ 1st available route found in the route list 1: the route 1

✦ the route 1 corresponds to the trunk group 18 (T2 line)
▼ if the T2 is not available, 2nd route available: the route 2

✦ the route 2 corresponds to the trunk group 16 (T0 line)


100
ARS
Management
Example 1: time based ARS (customization)
T2 not available at the week-end for international calls
Update the outside numbers « 00 » in the discriminator

/Review modify
✦ Schedule number: 1


101
ARS
Management
Create a new the time based route list in the ARS list 1
Descend hierarchy / Timed-based route list / Create

✦ Time-based Route List ID: 2
[ Add ]
✦ Route Number: 2


102
ARS
Management
Create the ARS schedule 1

➨ Translator / Automatic Route Selection / ARS Schedule /
Create
✦ name: international (example)
✦ Day list:
[ Add ]
Day: Sunday
Time table: 2
[ Add ]
Day: Saturday
Time table: 2
[ Add ]
Day: Monday
Time table: 1
etc ..

Warning: don’t forget to manage all type of day in the schedule !!

103
ARS
Management
Create the time tables 1 and 2 in the ARS Schedule 1

Descend hierarchy / ARS time table / Create
✦ Schedule Number: 1
✦ ARS Time Table Number: 1
[ Add ]
Hour: 0
Minutes: 0
Time based route list: 1
[ Add ]
Hour: 0
Minutes: 0


104
ARS
Management
Example 2: time based ARS (customization)
For the calls of 01xxx (every day):

➨ access to T0 and T2 between 8AM and 5PM
➨ access to T2 and T0 for the rest of the time

/Review modify


105
ARS
Management
Create a new ARS route list

Create
✦ ARS route list : 3
✦ Name : Route_list_3


106
ARS
Management
Create the 2 routes in the new ARS route list

Descend hierarchy / ARS route / Create

✦ Route: 1
✦ Name: T2
✦ Trunk group: 18
✦ Quality: + Speech

✦ Route: 2
✦ Name: T0
✦ Trunk group: 16


107
ARS
Management
Create the 2 time based route list required in the new ARS
route list
ARS route list:3 ARS route list:3

Time-based Route List ID: 1 Time-based Route List ID: 2
[ Add ] [ Add ]
Route Number: 1 Route Number: 2
Waiting cost limit: -1 Waiting cost limit: -1
Stopping cost limit: -1 Stopping cost limit: -1
[ Add ] [ Add ]
Route Number: 2 Route Number: 1
Waiting cost limit: -1 Waiting cost limit: -1
Stopping cost limit: -1 Stopping cost limit: -1


108
ARS
Management
Create the ARS schedule 2

Create
✦ name: 01xxx (example)
✦ Day list:
[ Add ]
Day: Sunday
Time table: 1
[ Add ]
Day: Saturday
Time table: 1
[ Add ]
Day: Monday
Time table: 1
etc ..


109
ARS
Management
Create the time table 1 and its time slices in the ARS
schedule 2

Descend hierarchy / ARS time table / Create
[ Add ]
Hour: 0
Minutes: 0
[ Add ]
Hour: 8
Minutes: 0


110
ARS

OBJECTIVE:
◆ To maintain the ARS
Alcatel OmniPCX Enterprise – ARS

111
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


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

113
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>
====================================================================
====================================================================
--------------------------------------------------------------------
====================================================================

114
ARS – Time Based
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to put into operation an ARS configuration with time table.
MANAGEMENT
1. Manage the ARS as follow

1.1 For international calls ( 00 ), the T2 line is not available during the week-end.
1.2 For national calls 01, the T0 will be used at first between 7AM and 7PM every working
day.
1.3 If the T0 interface is saturated , the T2 will be used.
1.4 For the rest of the day the T2 interface will be used at first, if the T2 is saturated the T0
will be used.
2. Check the management by the maintenance command “lookars”

115
ARS – Time Based

116
ARS – Indirect carrier

OBJECTIVE:
◆ To describe the ARS with an indirect carrier
Alcatel OmniPCX Enterprise – ARS – Indirect carrier

117
Overview
Indirect access to a carrier
➨ Some telephone networks are only accessible through a

gateway
Central
Office
Specialized
Network
Gateway

Depending on the country, the use of the public network can be provided by several operators.
It sometimes even happens that one operator can only be accessed via another.
Effectively, some operators are specialized in carrying high traffic over long distances (long distance operators), others in connecting
local subscribers to a geographical area (local operators).
In this case, very often, the long distance operators offer their services through the network of local operators.
In this framework, the indirect operator selection service provides the possibility of:
- modifying the dialing to select the access gateway to the indirect network,
- identifying the caller on the gateway.

118
Overview
➨ Modification commands of the initial dialed number:
▼ Add: Additional digits

▼ Delete: Delete digits (on 2 digits)
▼ Wait: Pause in dialing (on 2 digits)
▼ Force: DTMF Mode
▼ Code: Send an authorization code
▼ Insert: Insert remaining digits

Some long distance operators do not supply direct access to the user’s switch, but are accessible via a local operator which provides
a gateway.
These types of action allow some complex cases, like an access to an operator through another one.
Example:
-first dialling towards operator 1 to contact operator 2,
-waiting for connection to operator 2,
-adapt its dialling mode,
-sending operator 2 the authorisation code for customer identification
-and dialling via operator 2 to the final destination in adapting it to the required format.
Dialling commands provide a flexible way of giving these services without modifying the number transmitted on the charging ticket.

119
Overview
Indirect access example
Public N°:
0154545454
T2
Trunk Group 18 Public network Private
(gateway)
carrier
User A dials 0 0388773000
Private network
Real Discriminator: 03887730xx: ARS route list N° 1 N° 041
Route N° TG N° DCT N° Del Add

1 18 1 0
Public N° : 0388773000
Dialing Command Table N° 1 Private N°: 3000
Command: D06A0154545454FW02A041I
Set B

DCT: Dialling Command Table
In this example, the dialled number :

-D06 : Deletion of the six first digits - Storage of the remaining digits in one buffer, here: 3000
-A0154545454 : Add of the indirect operator n° at the beginning (access through TG 10)
-F : Switch to MF Q23 over-dialling
-W02 : Pause of 2 seconds before continuing with the number send
-A041 : Add of the prefix 041 to access to the private network from the indirect operator
-I : Insertion of the buffer content (here: 3000)

120
Overview
➨ Authorization code
▼ Sending an access code according to:
✦ Code number
code number 8
✦ User cost center High cost Authorization
Low cost
center center code
Dialing command
0 122 12345678
Add : 01200
Force DTMF 123 179 445566
Wait : 05
Cost center: 150 Code :8 180 255 98765
Insert
Dialing Buffer
Result in the DCT: A01200FW05C8I

When a long distance operator is contacted indirectly via a local operator, the identity of the subscriber is sometimes transferred
automatically to the long distance operator with reference to the public network access used (by using the caller number information
of the public network).
When this method is not possible, the subscriber can be identified by using an authorisation code inserted in the dialling when the
call is established.
The authorisation code is not explicitly specified in the dialling command table but is managed separately.
This enables the customer to enter the confidential code while ARS management is performed by the technician.
Moreover the authorisation code also depends on the cost centre, this makes the same operator possible to have several codes.
The dialling command specifies which of the 10 authorisation codes piles to use.
When this command is encountered by the ARS process, it searches in the table an authorisation code with an identical pile and cost
centre 0, then the authorisation code is dialled.

121

122

OBJECTIVE:
◆ To put into operation the ARS with an indirect carrier

123
Management
For the call numbers 02xxx:

➨ access to the indirect carrier « 0246031600 » through the
T2, and sending the last 5 digits of number dialed (after 5
seconds)

/Review modify


124
Management

Create
Create only the route 1 in the new ARS route list

✦ Route: 1
✦ Name: T2
✦ Trunk group: 18
✦ Dialing command table Id.: 1


125
Management
Create the time based route list 1 in the new ARS route list

[ Add ]
✦ Route Number: 1


126
Management
Create the dialing command table 1
➨ Translator / Automatic route selection / Dialing command

table / Create
✦ Table Id.: 1
✦ carrier reference: 0
✦ Command: D05A0246031600FW05I


127
Management
For the calls of 03xxx:
➨ access to the indirect carrier « 0246031000 » through T0
➨ then switching in DTMF
➨ then pause of 2 seconds
➨ then sending of a code depending on the cost center:

▼ cost center 0: code 1234
▼ cost center 1: code 5678
➨ then pause of 3 seconds
➨ then sending of the last 5 digits of number dialed


128
Management

discriminator / Descend hierarchy / Discriminator rule /
Review modify


129
Management

Create
Create only the route 1 in the new ARS route list

✦ Route: 1
✦ Name: Indirect
✦ Trunk group: 18
✦ Dialing command table Id.: 2


130
Management
Create the time based route list 1 in the new ARS route list

[ Add ]
✦ Route Number: 1


131
Management
Create the dialing command table 2
➨ Translator / Automatic route selection / Dialing command

table / Create
✦ Table Id.: 2
✦ carrier reference: 1
✦ Command: D05A0246031600FW02C1W03I


132
Management
Create the authorization code table 1

➨ Translator / Automatic route selection / Code Table
Authorization / Create
✦ Bank number: 1
[ Add ]
✦ Upper Cost Center Value: 0
✦ Authorization Code: 1234
[ Add ]
✦ Upper Cost Center Value: 1
✦ Authorization Code: 5678
Manage the cost center number in users

➨ Users / Review modify
✦ Cost Center Id: 0


133

134
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to put into operation an ARS configuration with time table
MANAGEMENT
1. Manage the ARS as follow

For the national calls of 03…, the T2 line will be only used with:
- access through an indirect carrier number 02yy03x600,
- the code 1234 is sent on the line (whatever the user’s cost center is),
- the number dialed (except the 5 first digits) is sent by Q23 frequencies after 5 seconds.
2. Check the management by the maintenance command “lookars”

Note:
yy -> Classroom number
x -> Node number

135

136
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
137
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
138
Private calls

OBJECTIVE:
◆ To describe the principle of private calls
Alcatel OmniPCX Enterprise – Private calls

139
Private calls
Overview
Assign an external call to a cost center

➨ Update user’s metering counters
Types of private calls

➨ Private call prefix
➨ Personal identification number code (PIN code)
▼ Linked to a user
Types of users
➨ User with a physical set
➨ User with a fictitious set
Metering
➨ Personal call
➨ PIN code

The private call feature provides privacy by dialing a code only known by the user (example: secret code, PIN code).
There are two ways to make a private call:

- by dialing a personal trunk group seizure prefix (with or without overlapping),
- by using a unique code assigned to the user, called PIN (personal identifier number) code, with or without a secret code.
Comment: these two services are not available simultaneously.
A designated user of a physical set can use both types of call.

A designated user of a fictitious set can only use the PIN code.
Restrictions linked to user type:

- no private call from the operator,
- no private call transfer.
If the PIN length is other than zero, the ticket will then indicate a personal call and the PIN code, otherwise a personal call will be
indicated.

140
Private calls
Overview
Users declared with a physical set
➨ Personal trunk group seizure prefix

➨ No PIN code
trunk group
Public/private
+ +
Personal trunk group Secret code external
seizure prefix for set Number

In this case, the user must use his set to make the private call, as the secret code for the set is requested.
Voice guide:
4: «Please dial your personal code».

141
Private calls
Overview
Users declared with a physical set
➨ With PIN code
32006
Personal trunk group
seizure prefix
+ + PIN
Code
Secret code
for set
+ External
number
secret code: 1234

secret code: 1234
PIN code: 2233
PIN code: 2233
trunk group
Public/private
32007

In this case, the user 32006 can use any set in the installation to make the private call (ex: 32007).
The user’s PIN code and secret code are used, the code is assigned to:
- User’s physical set: 32006.
Here, the user is the designated user of set 32006 and is making a private call from set 32007.
The requested codes are:
- secret code: 1234,
- PIN code: 2233.
Voice guide:
4: «Please dial your personal code».
14: «Please dial the number the call is to be charged to ».

142
Private calls
Overview
Users declared with a fictitious set
➨ With PIN code
32006
Personal trunk group
seizure prefix
+ + PIN
Code
Secret code
for set
+ Outside
number
secret code: 1234

secret code: 1234
PIN code: 2233
PIN code: 2233
trunk group
Public/private
32007

In this case, the user 32006 can use any set in the installation to make the private call (example: 32007).
The user’s PIN code and secret code are used, the code is assigned to:
- User’s fictitious set 32006.
Here, the user does not have a physical set but is the designated user of fictive et 32006 and is making a private call from set 32007.
The requested codes are:
- secret code: 1234
- PIN code: 2233
The « blank » UA set represents a fictitious set.

143
Private calls
Overview
To illustrate
➨ Maintenance department
➨ Staff do not have a physical set
▼ No « fixed » set

Maintenance staff do not have a phone, due to mobility and cost problems.
They can use the installation’s sets by using the PIN code and secret code of a fictitious set (which has a « maintenance » cost center).
The calls are charged to this cost center.
The fictitious set has its own categories and can be discriminated.

144
Private calls
Overview
PIN code operating principle

External
private
Phone facilities
Phone facilities call
category
category
Private Call
Private Call
Category
Category
( Barring )
( Barring )
Connection
Connection
category
category
User Private
User Private
call
call

Using the PIN code requires the following main elements:
- user: defining the secret code and PIN code,

- phone facilities category: access to the feature,
- private Call Category Number: call discrimination by PIN code,
- connection Category Number: access to installation ’s set to make private calls by PIN code.

145
Private calls
Overview
Personal Identification Number
➨ Possibility to use REDIAL or MEMORY key for private calls
▼ Possibility to send automatically the PIN
➨ S0 set are allowed to use PIN function

Remark:
- If a secret code is associated to the PIN, the user need always to dial this number
- This parameter «Project Code In Redial Key « is also validated for business call
- PIN must be unique over a network

146
Private calls
Overview
Restrictions
➨ The PIN length is not broadcast or audited
➨ Private call is not authorized from attendant set
➨ Forbidden transfer
➨ S0 set
▼ The PIN dialed is always displayed and stored in the set (redial)
▼ The prefix and the PIN digits also count for the maximum numbers of
digits you can dialed
▼ No portability


147

148
Private calls

OBJECTIVE:
◆ To set up private calls

149
Private calls
Management
To manage all possible configurations when making a

private call, you must:
▼ define a personal trunk group seizure prefix,

▼ define the private call profile,
▼ assign a phone features class of service to the set with the right to
private call,
▼ define the personal identification number (PIN) and the limits of its
use,
▼ define, if necessary, the secret code,
▼ authorize or not the storage of the PIN code in the "Redial" or
"memory" key,
▼ assign a private call connection class of service to the set enabling it
to authorize or not access to the sets in the system,
▼ assign an access class of service ( for the barring ).

Personal trunk group seizure prefixes enable calls of a private nature to be made, thus informing the metering field.

150
Private calls
Management
Creating personal trunk group seizure prefix
➨ Translator/prefix plan
▼ Number:
✦ Enter a prefix number compatible with the existing numbering plan
▼ meaning:
✦ Personal trunk group seizure
✦ Pers. tr. GR. seiz. With overlap
✦ ARS Personal Trk Grp
✦ ARS Personal Trk Grp with Overlap
▼ Prefix Information:
✦ Enter the number of the trunk group to be used,
▼ Private Call Profile:

✦ Enter the profile number (0 to 19).

Private call protection makes impossible to dial personal trunk group seizure prefixes.

151
Private calls
Management
A profile number is associated with each personal trunk

group seizure prefix
➨ Translator / Private Call Profile
▼ Id: displays the profile number (0 to 19)
▼ Use PIN: True / False
▼ Use secret code: True / False
▼ User type in accounting ticket:

Accounting ticket w. PIN user ind.,
Accounting ticket w. Guest user ind,
Accounting ticket with -reserved 1-, ...
▼ Call Type:
Normal Call,
VIP Call,
Guest Call, ...
▼ Public network COS

Enter the public network COS No. for barring of this call.

-Use PIN: True the PIN code must be entered,
-Use secret code: True the secret code must be entered (case without PIN),
-User type in accounting ticket: Select the call type in the accounting ticket.Indication of the call type in the accounting (Private,
Visitor, etc.),
-Call Type: Defines the type of private call,
-Public network COS: public network COS number for barring.

152
Private calls
Management
A phone features COS must be allocated to the set

(between 0 and 31)
➨ Classes of service / Phone Features Classes of service
▼ Prot. against Priv. Call: 0/1

▼ Prot. against Guest Private Call: 0 / 1
▼ Prot. against VIP Private call: 0/1
▼ Prot. against Private Call res 1: 0 / 1
▼ Prot. against Private Call res 2: 0 / 1
Defining PIN code lengths
➨ System
▼ PIN length

Prot. against Priv. Call: Enter 0 to allow private calls, 1 to forbid them.
Prot. against Guest Private Call: Enter 0 to allow guest private calls, 1 to forbid them.
Prot. against VIP Private call: Enter 0 to allow VIP private calls, 1 to forbid them.
Prot. against Private Call res 1: Enter 0 to allow reserved1 private calls, 1 to forbid them.
Prot. against Private Call res 2: Enter 0 to allow reserved2 private calls, 1 to forbid them.
Management of PIN code length validates the service.

The PIN code appears onto the accounting ticket.
System / PIN length:

-from 1 to 8,
-0 means: Personal prefix + secret code + external number,
--1 means: Personal prefix + external number «Personal call» which is mentioned onto accounting ticket (useful for a different
barring).

153
Private calls
Management
Defining PIN (Personal ID Number) code

➨ Users or Translator/ PIN
▼ PIN No.: Enter the PIN number
▼ PIN With Secret Code: True / False
▼ Type of control:
✦ By COS
✦ Restricted to owner set
✦ Universal access
✦ By group
Case when the PIN control is “by group”:

▼ PIN group control:
✦ No group
✦ All groups
✦ By group number
▼ PIN group number: Enter PIN group number of the set (value
between 1 and 65000)

PIN codes can be directly managed at the user attribute level or via the translator object. In this case, the directory number it belongs
to must be provided.
Validating a flag makes possible to associate or not the user’s secret code during its use.
Comment: the PIN code must be unique.
PIN No.: Enter the PIN number

PIN With Secret Code: Yes, the user must enter his secret code after the PIN
Type of control:
By category: the PIN can be used on any set in the system if the user's private calls connection category is
compatible with that of the physical set used
Restricted to owner set: the PIN can only be used on the set in the system that it is associated with
Universal access: the PIN can be used on all sets in the system
By group: the PIN can be used on all sets in the system which belong to the same group (in this case complete the
attribute below)
PIN group control:

No group: no private call with a PIN controlled by group is possible from this set,
All groups: all private calls with a PIN controlled by group are possible from this set,
By group number: from this set, only private calls with a PIN controlled by group with a PIN group number equal to
the group number of the set are possible (see the attribute below).
PIN group number: Enter PIN group number of the set (value between 1 and 65000)
Notes:
-If the secret code is associated to the PIN number, the user must dial his code,
-The PIN code must be unique over the network,
-Under /usr3/mao, launch the cfgUpdate command to modify the number of PIN codes authorized at the creation. A shutdown is
mandatory to take into account the modifications.

154
Private calls
Management
Connection between sets for private calls

➨ Classes of service / Private calls connect. COS
▼ Categories X
Defining private call discrimination

➨ Classes of service / Access COS / private access COS
▼ area 1 to area 64 in Day, Night, Mode 1, Mode 2
Using private calls and REDIAL key

➨ System / 0ther System Parameters / Project Code In Redial
Key: True / False
▼ If true, in case of REDIAL or MEMORY, the PIN is dialed
automatically

•The private call connection COS enables authorization or refusal to make a private call from one of the installation’s sets.
This parameter is used if the PIN is controlled "by category".
Example:
A user is the designated user of set «A» with PIN code.
He can use the set «B» to make a private PIN call if and only if the private call connection category of « A » is compatible with the
private call connection category of «B».
The private call category index is the same as the set connection category.
•The private access COS enables private call discrimination depending on the set entity.
•The attribute « project code in redial key » also concerns the business code calls.

155

156
Private calls

OBJECTIVE:
◆ To display some information about sets

157
Private calls
Maintenance
Display the personal trunk group seizure prefixes

➨ Command: ednump
▼ dir
▼ mean
Display set information

➨ Command: edsbr
▼ dir
▼ code
▼ pna
▼ fc
▼ cxc

These 2 commands can be used with a specific language by using the option: -l US0, -l GEA… (e.g: edsbr -l US0)
“Enter a criteria or a command “: ? * is used in order to display all the available commands.
? is used in order to display the help
go is used in order to launch the request (after criteria selection)
edsbr parameter meanings:

- dir: directory number
- code: secret code
- pna: access category
- fc: phone facility category
- cxc: connection category
ednump parameter meanings:

- dir: directory number
- mean: meaning

158
Private calls
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to setup private calls facility
MANAGEMENT
1. Setup the length of the PIN codes to 4 digits
Path System
Action Filter the parameter « PIN length », then click on edit
Parameters PIN length: 4
2. Create a prefix in order to be able to carry out a private call using the T2
Path Translator / Prefix Plan

Action Create
Parameters Number : free number
Prefix meaning : Personal Trk Grp seizure with overlapping
Prefix information : <Index of the T2 trunk group >

159
Private calls
3. Allocate a PIN code to the users 3x001 and 3x002. The users will have to dial their PIN code
and their personal code to be able to make a call.
Path Users
Action Open a grid edit containing only the PIN parameters
Filter the users 3x001 and 3x002 in this grid edit
Parameters PIN (Personal Ident.No.)
PIN No.: xxxx (choice of the manager)
PIN with Secret Code : True
4. Create a fictitious user ( 3x017 ) and allocate to this user a PIN code, check that this PIN code
can be dialed using the system’s extensions.
Path Users
Action Create
Parameters Directory Number : 3x017
Entity no. : 1
PIN (Personal Ident. No.)
5. The user 3x002 must be able to carry out a private call using his own extension only.
Path Users
Action Filter the user 3x002, then click on edit
Parameters PIN (Personal Ident. No.)
Type of control : Restricted to owner set

160
Private calls
6. Protect the user 3x003 against any private call
6.1 Forbid the connection of the private call connection category 0 with the 31
Path Classes of service / Private Calls Connect. COS

Action Filter the COS 0, then click on edit
Parameters COS 31 : 0
6.2 Allocate the COS No.31 to the user 3x003
Path Users
Action Filter the user 3003, then click on edit
Parameters Connection COS id: 31
7. Allocate a PIN code to the users 3x010 and 3x011; the users must be able to use their PIN
code on both extensions but not on the others ones of the system.
Path Users
Action Filter the users 3x010 and 3x011, then click on edit
Parameters PIN (Personal Ident. No.):
Type of control : By group
Note : X : node number

161
Private calls

162
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
163
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
164
Business calls

OBJECTIVE:
◆ To describe and manage the business calls service
Alcatel OmniPCX Enterprise – Business calls

165
Business calls
Overview
Objective: to link the outgoing calls to business codes
Business code
prefix
+ + Business
code
Trunk group
seizure prefix
+ Outside
number
Trunk
Public / Private
32007
Accounting ticket

A business call can be performed after an enquiry call .

The user is asked to dial a business code by a voice guide.
The outside number can be a speed dial number.

The system can store up to 255 business codes made of 1 to 12 digits each (digits: 0 to 9, A, B, C, D, * and #).
The metering ticket edited at the end of the communication contains the business code dialed to make the call.

166
Business calls
Overview
Example of use:
➨ Lawyer: communications for 3 customers
123
432
567

Using the business calls feature, it’s easy to charge the different customers for the calls made for them.
The user has just to enter the right business code before making the outside call.

167

168
Business calls

OBJECTIVE:
◆ To describe and manage the business calls service

169
Business calls
Management
Define business codes length

➨ Specific telephone services
▼ Project account code length:
Declare business code

➨ Specific telephone services / Project account code
▼ Id number: 1 to 9999
▼ Project account code:
Create the prefix

➨ Translator / Prefix plan
▼ Prefix meaning : external features
▼ External features : business account code

The business codes are limited to 12 digits.
By default, the business codes are controlled by the PCX, and must be declared by management.
This control can be cancelled.
Up to 9999 business codes can be created.

The id number can be 1 to 9999.
The business codes must have the length defined in management.

170
Business calls
Management
Business calls discrimination
➨ COS / Public network COS / business access right

▼ Outgoing area X: area 1 to area 64
▼ Business calls access: True / False
Features rights
➨ COS / Phone features COS

▼ External services
✦ Business account code

Special discrimination can be defined for calls by business code.

171
Business calls
Management
Feature customization
➨ System / Other. System Param
▼ No control: Business Account Code
▼ Business Pref.With Business No
▼ Project prefix With Code
▼ Transfer all Business Call Types
▼ Project code in redial key

No control: Business Account Code: Default value: False.

Set to True to disable business account control. In this case, the number dialed is not checked (it may not be listed in the table of
business account numbers).
Business Pref.With Business No.: Default value: True.

The user must enter the business account number after the business call charge prefix. If this parameter is set to False, the user does
not enter business account number and the business account number field is completed with # characters (same number of
characters as business account number)..
Project prefix With Code: Default value: False.

Set to True, the user must enter set password before trunk seize.
Transfer all Business Call Types: Default value: True.

Set to True, all types of business calls can be transferred and parked. Set to False, business account calls with no number or number
control cannot be transferred or parked. This option only concerns set parking and set to set transfer. It is operational when the No
control: Business Account Code attribute is set to True and the Pref.With Business No. is set to False (business account calls
with no business/project code). In all other cases (with business/project code and checking (control) of this code), the user has the
right to transfer and park calls.
Note: This attribute must be identical on all network nodes.
Project code in redial key: Default value: True.

Business account calls are handled by the redial key except for checked business/project codes (see the No control: Business
Account Code attribute above).

172
Business calls
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the business calls
MANAGEMENT
1. Define the business codes length to 3 digits
Path Specific telephone services

Action Edit the parameter: project account code length
Parameters Project account code length : 3
2. Create business codes
Path Specific telephone services/Project account code

Action Create
Parameters Id number: 1 to 9999
Project account code: free
3. Create a prefix to make business calls using the T2 line
Path Translator/Prefix plan

Action Create
Parameters Number: a free number
Prefix meaning: External features
External features: Business account code

173
Business calls
4. Check the right to make outside calls using the business codes
4.1 Check the public network COS of the extensions
Path Users
Action Edit
Parameters Public network COS
4.2 Check that the COS makes the calls possible
Path COS/Public network COS/business access right

Action Edit the COS
Parameters Outgoing area x
Access to the business calls: true
5. Enable the feature on the extensions
5.1 Check the extensions phone features COS
Path Users
Action Edit
Parameters Phone features COS
5.2 Check that the COS enables the feature
Path COS/Phone features COS

Action Edit the COS
Parameters Business account code : 1

174
Business calls
6. Check the feature by dialing :

- the business calls prefix,
- a business code created in the database,
- the trunk group seizure prefix,
- an outside number.
7. Test the feature customization parameters
Path System / Other. System Param

Action Edit the parameters (change the values and check the way it works one by
one)
Parameters No control: business Account Code
Business Pref. with Business No
Project prefix with Code
Transfer all Business Call Types
Project code in redial key

175
Business calls

176
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
177
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
178
Static V24 accesses

OBJECTIVE:
◆ To describe the static V24 communications existing on Alcatel OmniPCX Enterprise
Alcatel OmniPCX Enterprise – Static V24 access

179
Static V24 accesses
Summary
Introduction
TA and TSC interfaces
V110 and V120 protocols
V24/IP box
Static V24 access


180
Static V24 accesses
Introduction
A lot of external applications (hotel, accounting...) need

additional V24 accesses on CPU (Crystal Server, Call
Server or Appliance Server)
Remote accesses (maintenance console) are available

through these V24 accesses
There are different ways to provide these V24 accesses
V24 accesses can be:

➨ static
➨ or dynamic


181
Static V24 accesses
Overview
Optional V24 UA interface
➨ Support
▼ TA box (reference 4088)
➨ Optional V24 cards
▼ V24 asynchronous 1+ MAC/PC (reference 4083 ASM)

✦ V110 protocol
▼ V24 asynchronous 2 + MAC/PC (reference 4083 ASP)
✦ V110 protocol or V120 protocol
V24 A1 X.XX
-> 4083 ASM
V24 A2 X.XX
-> 4083 ASP


182
Static V24 accesses
Overview
TSC V24 Reflexes plugware
➨ Can be connected:
▼ directly to a UA board
▼ behind a UA 3G set
➨ Reference:
▼ Alcatel 4093 ASY: V24 / CTI Asynchronous
✦ Communication Protocols: V25 bis, HAYES

✦ Adaptation Protocol: V110, V14E
➨ This plugware allows only V110 connections (no V120)

TSC V24 Reflexes plugwares can be connected behind all types of UA 3G sets.

183
Static V24 accesses
Overview
V110 and V120 protocols
➨ Realize the adaptation of a data terminal or application's

binary rate in a 64 kbits/s B channel
➨ Binary rate until 19200 bits/s
➨ V110 protocol
▼ allows to access to applications declared on V24 ports
➨ V120 protocol (more efficient)

▼ frames with HDLC format
▼ allows to access to applications declared on V24 ports and B

channels

HDLC: High Level Data Link Control

The advantage to use V120 protocol rather than V110 protocol is the possibility to use B channels.

184
Static V24 accesses
Overview
V24/IP box
➨ Some OmniPCX Enterprise applications need V24 port

(hotel, login, accounting,…)
➨ The number of local V24 ports on the Call Server is limited

to 1 (CPU-CS or Appliance Server)
➨ It can be necessary to increase this number of ports


185
Static V24 accesses
Overview
Solution
➨ Using a device connected to the LAN providing an interface
between IP and applications on V24 link
IP
network
Call login
server Client
Remote
V.24 PPP link Maintenance
box
Accounting
display
V24
Console


186
Static V24 accesses
Overview
The solution selected by Alcatel is:

➨ the Nport Server Lite DE.304 from MOXA manufacturer
Characteristics
➨ 4 ports v24 RS 232
➨ 10/ 100 base T IP link (auto-detection)
➨ It's possible to configure the box (IP@, mask, router).
Many V24/IP boxes can be used in a client configuration

Internet Site: www.moxa.com.

4 boxes in maximum can be configured (4x4 V24 ports).

187
Static V24 accesses
Overview
Software
➨ Drivers and Linux tools necessaries are integrated in the
Call Server
➨ For the Moxa, a process is launch at the starting up

(moxatty). It allows the link between IP and V24 ports
The Nport server has an IP configuration
Data are sent from e-CS to this IP@ and are routed to V24
ports via specific TCP ports ( 950-953)


188
Static V24 accesses
Overview
Installation
➨ 3 steps for the installation:

▼ IP configuration for the moxa (@IP, mask, router),
▼ declare the Nport Moxa in the e-CS,
▼ manage the ports and the applications in the e-CS.
➨ In the e-CS, the link between the ports and the V24 must be
done
✦ Example: the login application is associated to a V24 port of V24/IP box


189
Static V24 accesses
Overview
Static V24 access
➨ An asynchronous static V24 access is established between a

caller terminal and a V24 port dedicated to an application
➨ The application is managed by a process present at the

starting up of the system on a V24 port
➨ V24 ports used are:

▼ V24 port on CPU5 step3, CPU6 step2 or CPU7 (4 ports: 2 ports for
applications),
▼ V24/IP box for every platforms (16 ports maximum),
▼ V120 B channels on IO2N/OBCA2:

✦ 60 B channels for the IO2N: 60 virtual V24 ports,
✦ 3 B channels for the OBCA2.

No OBCA2 on CPU7
V24 ports are in asynchronous mode.
Each application is identified by a number.
The process started depends on the application chosen:

Example:
-login application: process = pre_login,
-hotel application: process = hotmenu.

190
Static V24 accesses
Overview
Types of accesses to the applications in V24 static
➨ Common hardware
▼ Direct access
▼ Access via terminal adapter (TA)
➨ Crystal hardware
▼ Direct access
▼ Access via B channel (needs of IO2N or OBCA2)


191
Static V24 accesses
Overview
Direct static V24 access for common hardware
IP
Com
Server
V24/IP box
(4 boxes Login
maximum)
➨ The access to an application is realized by connecting to

V24 real port

Each V24 port is dedicated to an application.

192
Static V24 accesses
Overview
Static V24 access via TA for common hardware

TA V110
UA
V110
TA
Com
Server UA
IP V24 cable
V24/IP box hotel menu
➨ The access to an application is done dialing the TA number

connected to the V24 port

The connection can be done with V110 or V120 mode. It depends on the type of interface used!
The TA is made of a box and of a V24 interface (V110 or V120 mode).
The caller TA is connected to a V24 port which uses the V110 or V120 protocol.
The 2 TA are used during all the connection.
You need a straight cable between the TA and the PC and between the TA and the V24 port.
It is possible to connect a V120 TA and a V110 TA because V120 TA supports also V110 protocol. V120 TA restarts with V110
protocol.
You can not use V120 protocol with a 3G TA. It's necessary to use a 2G TA.

193
Static V24 accesses
Overview
Direct static V24 Access for crystal hardware
login
CPU5 step3 or
CPU6 step2 or
CPU7
connecting box
(4 ports maxi)
➨ The access to an application is realized by connecting to a

V24 physical port

Each V24 port is dedicated to an application.

194
Static V24 accesses
Overview
Static V24 access via TA for crystal hardware

TA V110
UA
TA
UA
V110
login CPU5 step3 or

CPU6 step2 or
CPU7
connecting box
➨ The access to an application is done by dialing the TA

number connected to the V24 port

The connection can be done with V110 or V120 mode . It depends on the type of interface used!
The TA is made of a box and a V24 interface (V110 or V120 mode).
The caller TA is connected to a V24 port which uses the V110 or V120 protocol.
The 2 TA are used during all the connection.
You need a straight cable between the TA and the PC and between the TA and the V24 port.
It is possible to connect a V120 TA and a V110 TA because V120 TA supports also V110 protocol. V120 TA restarts with V110
protocol.
You can not use V120 protocol with a 3G TA. It's necessary to use a 2G TA.

195
Static V24 accesses
Overview
Static V24 access via B channel for crystal hardware
TA
CPU + IO2N
or OBCA2
V120
login
Hotel menu
➨ A B channel is associated to an application

➨ You access to an application by dialing the directory
number associated to the B channel

The calling TA must run with V120 mode. This is the only mode which allows to use B channels.
The connection between the calling TA and the application is done by C1 link (OBCA2 board).

196
Static V24 accesses
Overview
Welcome data menu

menu 1 -> choose Type of terminal

menu 2 -> choose set-up: to scroll possible set-ups press space par then RC
to validate a new set-up press Y then RC
menu 3 -> change connection mode (welcome data menu, hayes, V25 bis). In hayes or V25 bis mode, the sequence $*# followed by
RC lets you redefine the connection mode (TA must be disconnected)
menu 4 -> to call a TA via its number. To be able to make a call by number, the calling TA ’s connection category must be
compatible with the category 0. If not, the calling le TA d can only establish connections via menu 5
menu 5 ->to call a TA via a name. The index management to be done is:
\Data\Menu data\Repertoire
- call n°: n° of TA to call
- directory name: name attributed to TA
- data CX category n°: definition of calling rights between TAs
- set-up n°: if set-up is incompatible between 2 TAs, the call is refused
If user does not know names attributed to TA, he simply presses RC to display the list of existing names
menu 6 ->to call associated TA data keyed in the parameter «\Data\data Terminal ->n° of associated set»
menu 7 -> to record in management modifications of terminal characteristics
menu 8 -> pass from protocol V110 to V120 and vice-versa
at top right-> protocol used by the TA, at lower left -> TA ’s directory n°, at lower right ->set-up used by the TA

197

198
Static V24 accesses

OBJECTIVE:
◆ To put into operation static V24 PABX remote accesses

199
Static V24 accesses
Management
Management steps
➨ Direct - V24 static access
➨ TA-TA - V24 static access
➨ TA - B channel - V24 static access


200
Static V24 accesses
Management
Direct access
➨ Configuration of the MOXA box (if needed) (this

management is not seen in this chapter)
➨ System / V24 Port
▼ Port No.:
▼ Dynamic: No
▼ Speed: 9600
▼ Parity: None
▼ Data bits: 8
▼ Stop bit: 1
▼ Type of terminal: VT100
Login
▼ V24 Application: Login


201
Static V24 accesses
Management
TA-TA access (1/7)
➨ Management of the MOXA box if needed (not seen in this

chapter)
➨ Management of the V24 optional interfaces
➨ Management of the data terminals
➨ Management of the transmission parameters
➨ Management of the V24 port
UA board
TA
Login V110/V120


202
Static V24 accesses
Management
TA-TA access (2/7): V24 optional interfaces management
➨ Case of an interface in an UA extension
▼ Users
✦ Directory number:
✦ V24 extension: Yes
➨ Case of an interface in a TA box
▼ Shelf / Board / TA Adapter
✦ Equipment address: UA equipment No

✦ V24 Interface: Yes


203
Static V24 accesses
Management
TA-TA access (3/7): Management caller data terminal
➨ DATA / Data terminal
▼ Directory No.:
▼ Shelf address: UA set shelf No
▼ Board address: UA set board No
▼ Equipment address: UA set equipment No
▼ Adapter type: V110 + V120 asynchronous
▼ Terminal type: VT100
▼ Use: Welcome DATA menu
▼ Setup Id.: 1
▼ Input config. Id.: 1
▼ Output config. Id.: 1
▼ Adaptation protocol: V120
▼ On hook by 108: Yes
▼ Synchronous: Asynchronous


204
Static V24 accesses
Management
TA-TA access (4/7): Management of the called data

terminal
▼ Directory No.:
▼ Shelf address: TA box shelf No
▼ Board address: TA box board No
▼ Equipment address: TA box equipment No
▼ Use: Set (No emulation)
▼ Setup Id.: 1
▼ Automatic answer on UA set: Yes
▼ Synchronous: asynchronous


205
Static V24 accesses
Management
TA-TA access (5/7): Management of the transmission

parameters (1)
➨ DATA / Set-up
▼ Setup Id.: 1
▼ Emission speed: 9600
▼ Reception speed: 9600
▼ Parity: None
▼ Data bits: 8
▼ Stop bit: 1


206
Static V24 accesses
Management

parameters (2)
➨ DATA / Input configuration
▼ Input configuration Id.: 1

▼ Break key: Transparent
▼ Hold detection: Yes
▼ Sequence length: 3
▼ N-2 char.: 43
▼ N-1 char.: 43
▼ Disconnection char.: 43
▼ Inactivity timeout: 6 or 0


207
Static V24 accesses
Management
TA-TA access (7/7): Management of the V24 port
▼ Port No:
▼ Dynamic: No
▼ Speed: 9600
▼ Parity: Sans
▼ Data Bits: 8
▼ Stop bit: 1


208
Static V24 accesses
Management
TA - B channel access (1/7)
➨ Management of the V24 optional interface

➨ Management of the caller data terminal
➨ Management of IO2N / OBCA2 boards
UA board
Login
IO2N or OBCA2 board


209
Static V24 accesses
Management
TA - B channel access (2/7): V24 optional interface

management
▼ Users


210
Static V24 accesses
Management
TA - B channel access (3/7): Management caller data

terminal
▼ Directory No.:
▼ Shelf address: UA set shelf No
▼ Board address: UA set board No
▼ Equipment address: UA set equipment No
▼ Setup Id.: 1


211
Static V24 accesses
Management
TA - B channel access (4/7): Management of the

transmission parameters (1)
➨ DATA / Set-up
▼ Setup Id.: 1
▼ Parity: None
▼ Data bits: 8
▼ Stop bit: 1


212
Static V24 accesses
Management
TA - B channel access (5/7): Management of the


▼ N-2 char.: 43
▼ N-1 char.: 43

ASCII code: 43 corresponds to the character “+”.

Disconnection: +++.

213
Static V24 accesses
Management
TA - B channel access (6/7): IO2N / OBCA2 couplers

management
➨ Management of an IO2N coupler
▼ Shelf / Board
✦ Board address:
✦ Type of interface: IO2N
✦ Remote shelf address: 0
✦ Remote board address: CPU coupler Position
➨ Management of an OBCA2 board
▼ Shelf / Board
✦ Board address: CPU coupler Position
✦ Type of interface: CPU6
✦ CPU with optimized B channel: Yes


214
Static V24 accesses
Management
TA - B channel access (7/7): Management of the V24 port
▼ Port No.:
▼ Dynamic: No
▼ Speed: 9600
▼ Parity: None
▼ Data bits: 8
▼ Stop bit: 1
▼ Port dir. No. (static): Unused DATA directory number


215

216
Dynamic V24 accesses

OBJECTIVE:
◆ To describe dynamic V24 communications existing on Alcatel OmniPCX Enterprise
Alcatel OmniPCX Enterprise – Dynamic V24 access

217
Overview
Target: remote connections to internal applications

➨ CPU Login for management and maintenance,
➨ Hotel menu,
➨ CCd, ...
A V24 port is not dedicated to an application
The connection to the application is done by dialing the

directory number associated to the application
The application is controlled by a process

➨ Starting up of the V24 dynamic application on the
connected port
➨ The application is deleted at the disconnection

V24 accesses are in asynchronous mode.

Each application is identified by a directory number.
The started process changes according the asked application.

Example:
-login appli: process = pre_login,
-hotel appli: process = hotmenu.
A0 and B0 port can not be used.

A B channel is a virtual V24 port ( only available by C1 link).
Connection establishment:
-a calling TA dials the directory number associated to the application,
-the system looks for a free V24 dynamic port,
-the process is started on the selected V24 port,
-the caller TA is connected to the TA connected to the V24 port (only with the case of TA-TA connection),
-at the disconnection, the process is deleted, the V24 port is free for another application.

218
Overview
V24 ports used are
➨ V24 Ports on CPU5 step3, CPU6 step2 or CPU7
➨ V24 ports on V24/IP box (MOXA box)
➨ IO2N B channels
➨ OBCA2 B channels


219
Overview
There are different types of accesses to the applications
➨ Common hardware
▼ Access via Terminal Adapter (TA)
➨ Crystal hardware
▼ Access via B channel (IO2N or OBCA2)

No OBCA2 on CPU7

220
Overview
Dynamic V24 access via TA for common hardware
V110
V24 cable
UA
Com
Server
TA
IP
UA
Data Applications: V110
3600 -> login
3700 -> hotel menu login
V24 cable
V24 dynamic port

Data applications are defined in management.

The calling TA accesses to an application by dialing the associated directory number.
Alcatel OmniPCX Enterprise controls the connection with the TA connected to the dynamic V24 port.
The connection between the 2 TA is possible if the set up are compatible.
The directory number associated to the V24 port is declared in management.

Use a straight cable between the TA and the terminal and also between the TA and the V24 port.

221
Overview
Dynamic V24 access via TA for crystal hardware
V110
UA
CPU TA
UA
Data Applications: V110
3600 -> login
3700 -> hotel menu login
CPU5 step3 or
CPU6 step2 or
CPU7 V24 dynamic port
connecting box

Data application are defined in management.

The calling TA access to an application by dialing the associated directory number.
Alcatel OmniPCX Enterprise controls the connection with the TA connected to the dynamic V24 port.
The connection between the 2 TA is possible if the set up are compatible.
The directory number associated to the V24 port is declared in management.

Use a straight cable between the TA and the terminal and also between the TA and the V24 port.

222
Overview
Dynamic V24 access via B channel (IO2N board) for

crystal hardware
➨ Access with 60 B channels in V120 mode
0+0298143600 ISDN 64Kbs T0
DDI n° T2
Com
Remote maintenance console 64Kbs Server
UA
3
7
0 CPU IO2N
0
V24
Data: Applications
TA V120 3600 -> login
Hotel Console
3700 -> hotel menu


223
Overview
Dynamic V24 access via B channel OBCA2 (CPU

daughter board) for crystal hardware
➨ Access with 3 B channels in V120 mode
0+0298143600 ISDN 64Kbs T0
DDI n° T2
Remote maintenance console 64Kbs

UA
3
7
0 CPU 6+
0 OBCA2
V24
Data applications:
TA V120 3600 -> login
Hotel Console
3700 -> hotel menu

OBCA2 (Optimized B channel CPU Access): Same function than IO2N.
V120: rate adaptation protocol in the B channel.

224
Overview
Welcome data menu

menu 1 -> choose Type of terminal

menu 2 -> choose set-up: to scroll possible set-ups press space par then RC
to validate a new set-up press Y then RC
menu 3 -> change connection mode (welcome data menu, hayes, V25 bis). In hayes or V25 bis mode, the sequence $*# followed by
RC lets you redefine the connection mode (TA must be disconnected)
menu 4 -> to call a TA via its number. To be able to make a call by number, the calling TA ’s connection category must be
compatible with the category 0. If not, the calling le TA d can only establish connections via menu 5
menu 5 ->to call a TA via a name. The index management to be done is:
\Data\Menu data\Repertoire
- call n°: n° of TA to call
- directory name: name attributed to TA
- data CX category n°: definition of calling rights between TAs
- set-up n°: if set-up is incompatible between 2 TAs, the call is refused
If user does not know names attributed to TA, he simply presses RC to display the list of existing names
menu 6 ->to call associated TA data keyed in the parameter «\Data\data Terminal ->n° of associated set»
menu 7 -> to record in management modifications of terminal characteristics
menu 8 -> pass from protocol V110 to V120 and vice-versa
at top right-> protocol used by the TA, at lower left -> TA ’s directory n°, at lower right ->set-up used by the TA

225

226

OBJECTIVE:
◆ To put into operation dynamic V24 communications
Alcatel OmniPCX Enterprise – Dynamic V24 accesses

227
Management
Management steps
➨ TA-TA - V24 dynamic access
➨ TA - B channel - V24 dynamic access


228
Management
TA-TA access (1/8)
➨ Management of the MOXA box if needed (common

hardware - not seen in this chapter)
➨ Management of the Data terminals
➨ Management of the DATA application
UA board
TA
Login V110/V120
IO2N or OBCA2 board


229
Management
TA-TA access (2/8): V24 optional interfaces management
▼ Users
➨ Case of an interface in a TA box:
▼ Shelf / Board / TA Adapter
✦ Equipment address: UA equipment number



230
Management
TA-TA access (3/8): Management caller data terminal
▼ Directory No.:
▼ Shelf address: UA set shelf number
▼ Board address: UA set board number
▼ Equipment address: UA set equipment number
▼ Setup Id.: 1


231
Management
TA-TA access (4/8): Management of the called data

terminal
▼ Directory No.:
▼ Shelf address: TA box shelf number
▼ Board address: TA box board number
▼ Equipment address: TA box equipment number
▼ Use: Set ( No emulation )
▼ Setup Id.: 1
▼ Automatic answer on UA set: Yes


232
Management

parameters (1)
➨ DATA / Set-up
▼ Setup Id.: 1
▼ Parity: None
▼ Data bits: 8
▼ Stop bit: 1


233
Management

parameters (2)

▼ N-2 char.: 43
▼ N-1 char.: 43


234
Management
TA-TA access (7/8): Management of the DATA application
➨ DATA / DATA application
▼ Directory number:
▼ Directory name: LOGIN
▼ Executable: /chbin/pre_login


235
Management
TA-TA access (8/8): Port V24 management
▼ Port No.:
▼ Dynamic: Yes
▼ TA directory number: TA directory number
▼ Speed: 9600
▼ Parity: None
▼ Data bits: 8
▼ Stop bit: 1
▼ V24 Application: None


236
Management
TA-B channel access (1/8)

➨ Management of the caller data terminal
➨ Management of the DATA application
➨ Management of the OBCA2 / IO2N couplers
➨ Management of the V24 ports
UA board
Login
IO2N or OBCA2 board


237
Management
TA-B channel access (2/8): V24 optional interfaces

management
▼ Users
➨ Case of an interface in a TA box
▼ Shelf /Board / TA Adapter
✦ Equipment address: UA equipment number



238
Management
TA-B channel access (3/8): Management caller data

terminal

▼ Directory No.:
▼ Shelf address: UA set shelf number
▼ Board address: UA set board number
▼ Equipment address: UA set equipment number
▼ Setup Id.: 1


239
Management
TA-B channel access (4/8): Management of the

➨ DATA / Set-up
▼ Setup Id.: 1
▼ Parity: None
▼ Data bits: 8
▼ Stop bit: 1


240
Management
TA-B channel access (5/8): Management of the


▼ N-2 char.: 43
▼ N-1 char.: 43


241
Management
TA-B channel access (6/8): Management of the DATA

application
➨ DATA / DATA Application
▼ Directory number:
▼ Directory name: LOGIN
▼ Executable: /chbin/pre_login

Example of application executable commands:
- /DHS3bin/servers/hotmenu for the hotel menu

- /DHS3bin/servers/acdafibar for the ACD barometer
- /DHS3bin/servers/bascul for the bascul management

242
Management
TA-B channel access (7/8): IO2N / OBCA2 couplers

management
➨ Management of an IO2N coupler:
▼ Shelf / Board
✦ Board address:
✦ Type of interface: IO2N
✦ Remote shelf address: 0
✦ Remote board address: CPU coupler Position
➨ Management of an OBCA2 board
▼ Shelf / Board
✦ Board address: CPU coupler Position
✦ Type of interface: CPU6
✦ CPU with optimized B channel: Yes


243
Management
TA-B channel access (8/8): Management of the V24 port
▼ Port No.:
▼ Dynamic: Yes
▼ TA directory No.:
▼ Speed: 9600
▼ Parity: Sans
▼ Data bits: 8
▼ Stop bit: 1
▼ V24 Application: None


244
V24 Communications

OBJECTIVE:
◆ To maintain the V24 communications accesses
Alcatel OmniPCX Enterprise – V24 Communications

245
V24 communications
Maintenance
Adapters status
➨ listerm <shelf> <UA board>

listerm
Type of terminals:
-POS_NUM -> UA set,
-POS_DATA -> option board in UA set,
-TM_BOX -> TA box,
-TM_DATA -> option board in TA box
Comment: only option boards physically present in the set or TA are listed by the command listerm.

246
V24 communications
Maintenance
Checking the processes running on the V24 ports
➨ ps -edf

The column TTY supplies the names of V24 ports used by the Alcatel OmniPCX Enterprise’s applications.
In this example, the console port (port A0) is used to connect to the system and the hotel application (executable hotmenu) is
declared on the port scc1a (port D).

247
V24 communications
Maintenance
Displaying information about the V24 ports
➨ v24_config -s <V24 port number>

This command gives the status of the V24 port, its setup, the associated executable.
It also indicates the presence of boards IO2, SPB, OBCA (0-> board absent, 1 -> board present).
Details of useful fields:

line = «setup du V24 port» ex: 13-8N1 =>9600 -8N1(14=19200, 13=9600, 12=4800, 11=2400, ....)
name = «executable» ex: /DHS3bin/servers/hotmenu =>appli hotel
param = «parameter of the appli» ex: -l F => appli in French language
status = «status of appli» ex: status = 1 => appli started pid = «process number»
Note: The command ‘v24_config -r <n° V24 port>' is used to restart an application

248
V24 communications
Maintenance
Managing the A0 and B0 ports
➨ « ttyconf » command
➨ Used to switch off the ports and change their settings

« ttyconf » command is only used for A0 and B0 ports. For other V24 ports, the set-up is defined in management.
To set a V24 other than A0 and B0 to off, simply manage the port without an application
\System\V24 ports
- application: none

249
V24 communications
Maintenance
Consol port reset
➨ Ctrl G + Ctrl C:
allows to kill the current task on the consol port only and
give back the login
Reset of the V24/IP MOXA box ports
➨ dhs3_init –R V24_CONFIG:
allows to reset the management application of the V24
ports and to reset the V24 ports (only for the MOXA V24
ports, it doesn’t work on the consol port)


250
V24 communications
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to put into service remote PABX accesses (TA, IO2N, OBCA2, login)
MANAGEMENT
STATIC V24 ACCESS ON COMMON HARDWARE
1. Manage the following remote PABX access:

TA V110
UA
UA
Com
V110 Serv
V24/IP box
IP
TA
Login
V24 cable
2. Configure and connect the V24/IP MOXA box
3. Declare the data terminal optional V24 interface plugged in the UA extension.
4. Create the data terminal optional V24 interface plugged in a TA box (Equipment 5).
(/ Shelf / Board / TA Adaptator)

251
V24 communications
5. Create the two data terminals as indicated in management section: (/ DATA / Data terminal)
6. Manage the set-up and the input configuration used by the two DATA terminals as indicated in
management section.
(/ DATA / Setup and / DATA / Input configuration)
7. Manage on the CPU V24 port the login process. (/ System / V24 port)
8. Try a connection to the login application using the Welcome DATA menu on your terminal
application.
DYNAMIC V24 ACCESS ON CPU CRYSTAL SERVER
9. Manage the following remote PABX access using dynamic V24 access:
UA board
Login
IO2N or OBCA2 board
10. Declare on your system the OBCA2 or the IO2N board.
11. Create a DATA application associated to the login application as indicated in management
section in your training guide. (/ DATA / DATA applications)
12. Check that the V24 ports of the IO2N or OBCA2 are managed in dynamic mode.
(/ System / V24 port)
13. Try a connection to the login application using the Welcome DATA menu from your terminal
application.

252
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
253
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
254
LDAP overflow

OBJECTIVE:
◆ To describe the phone book overflow on LDAP server
Alcatel OmniPCX Enterprise – LDAP Overflow

255
LDAP overflow
Overview
Purpose:
➨ Enrich OmniPCX Enterprise Call-By-Name feature
Implementation:
➨ Improvement of the Phone Book (Phone Book ++) by

integrating a LDAP client
▼ Possible overflow (or "Off-board" Seek) on a designated LDAP server
when using the Call By Name
Kustorica Emir: Kustorica Emir:
34200 34200 LDAP Server
Kustorica Emir ? Kustorica Emir ?

Call Server
with PB++
Kustorica Emir unknown or

not the right one
Kustorica Emir = 34200

Phone Book ++: improvement of the former phone book (Phone Book +) by integrating an LDAP client.
Phone Book +: Improvement of the Phone Book allowing the management of up to 32000 entries.
LDAP: Lightweight Directory Access Protocol

256
LDAP overflow
Overview
Services
➨ Search scheme:
▼ Normal Mode
✦ Automatic overflow:
in case of unsuccessful search in Alcatel OmniPCX Enterprise's phone book, a
search is automatically launched in the LDAP server directory
✦ Manuel overflow:
in case of successful search (at least one answer) in Alcatel OmniPCX
Enterprise's phone book, the user can overflow on the LDAP server directory by
pressing a dynamic key
▼ Multi-company (multi-tenant) mode

✦ target LDAP directory managed in the entity
➨ If several phone numbers for one name, only one will be

taken in this priority order
▼ Internal phone number, external number, GSM number

If the result of the search in the local database (e-CS one) does not satisfy the user, he may be able to launch a search on the LDAP
server manually by pressing a dynamic key of the user set.

257
LDAP overflow
Overview
Restrictions
➨ LDAP version 3.0 or higher
➨ Manual overflow on 4035 sets only
➨ No dynamic key on 4059
➨ 5 LDAP servers maximum
➨ No referral
➨ The "LDAP overflow" feature is enabled only if the "Call By

Name" lock is open

No referral: if a request of a name failed in the managed LDAP server, this server sends an other LDAP server address for a new
connection. The user of the Alcatel OmniPCX Enterprise do not use it.

258
LDAP overflow

OBJECTIVE:
◆ To manage the phone book overflow on LDAP server
Alcatel OmniPCX Enterprise – LDAP overflow

259
LDAP overflow
Management
LDAP server declaration
➨ Applications / LDAP Phone Books
▼ LDAP phone book: From 1 to 5

▼ Server Name:
▼ Server IP address:
▼ Server port Number: port used by LDAP server (389 by default)
▼ User identification:
▼ User password:
▼ Confirm:
▼ Directory root entry: search base
▼ Selection criteria:

Server Name: this name has to be declared in the e-CS host file or you specify directly the server IP address.
User Identification:
- if not managed, connection as "anonymous" (default login for LDAP client which has a read-only right on non-confidential
entries (=persons) of the directory),
- if managed, it must corresponds to an existing person of the directory.
Syntax example: uid=superuser,o=alcatel university (where superuser is the User Id. of a person located in the organisation alcatel
university)
User password: password of the person superuser managed above or nothing if "anonymous" login is used
Directory root entry:

example for the OmniVista 4760 directory, if the Company directory root is "alcatel university", the directory root entry is:
o=alcatel university (o stands for organisation in the LDAP protocol)
Selection criteria: character string allowing filtering (dedicated to multi-company centrex)

260
LDAP overflow
Management
Overflow right and multi-company management
➨ System / Other system parameters / System parameters
▼ Phone Book Overflow on Ldap Server: +True
➨ Entities
▼ Overflow LDAP Phone book: index of the LDAP server on which the
overflow should be performed for the users belonging to this entity
(from 1 to 5)

Up to now, the multi-company mode is not implemented, use LDAP server number 1.

261

262
LDAP overflow

OBJECTIVE:
◆ To insure the phone book overflow on LDAP server maintenance

263
LDAP overflow
Maintenance
Process
➨ The process which handles the overflow is "pbmd"
(1)Node1A> ps -edf | grep pbmd

root 817 499 0 12:19 ? 00:00:00 /DHS3bin/servers/pbmd -l -a
mtcl 4997 4874 0 13:25 ttyS0 00:00:00 grep pbmd


264
LDAP overflow
Maintenance
Timer
➨ 301 (TIMOUT_SEARCH_LDAP)
▼ In System/ Timers
▼ The LDAP seek is stopped after this timeout
▼ Default value: 3800 (38 seconds)


265
LDAP overflow
Maintenance
Traces
➨ Connection to the LDAP directory

No. Source Destination Protocol Info
1 155.132.5.1 omnivista LDAP MsgId=1 MsgType=Bind Request
2 omnivista 155.132.5.1 LDAP MsgId=1 MsgType=Bind Result
➨ Search in the directory

3 155.132.5.1 omnivista LDAP MsgId=10 MsgType=Search Request
4 omnivista 155.132.5.1 LDAP MsgId=10 MsgType=Search Entry
5 omnivista 155.132.5.1 LDAP MsgId=10 MsgType=Search Result


266
LDAP overflow
Maintenance
Traces
➨ Connection to the directory (request)
Frame 1 (68 on wire, 68 captured)
Ethernet II
Destination: 00:50:8b:dc:f5:0e (omnivista)
Source: 00:d0:95:33:29:20 (XYLAN_33:29:20)
Type: IP (0x0800)
Internet Protocol, Src Addr: 155.132.5.1 (155.132.5.1), Dst Addr: omnivista
(155.132.0.60)
Source: 155.132.5.1 (155.132.5.1)
Destination: omnivista (155.132.0.60)
Transmission Control Protocol, Src Port: 10014 (10014), Dst Port: 389 (389), Seq:
3962469206, Ack: 512323829
Source port: 10014 (10014)
Destination port: 389 (389)
Lightweight Directory Access Protocol
Message: Id=1 Bind Request
Message Length: 7
Version: 2
DN: (null)
Auth Type: Simple (0x00)
Password: (null)


267
LDAP overflow
Maintenance
Traces
➨ Connection to the directory (reply)
Ethernet II
Destination: 00:d0:95:33:29:20 (XYLAN_33:29:20)
Source: 00:50:8b:dc:f5:0e (omnivista)
Type: IP (0x0800)
Internet Protocol, Src Addr: omnivista (155.132.0.60), Dst Addr: 155.132.5.1
(155.132.5.1)
Source: omnivista (155.132.0.60)
Destination: 155.132.5.1 (155.132.5.1)
512323829, Ack: 3962469220
Source port: 389 (389)
Message: Id=1 Bind Result
Message Length: 7
Result Code: Success (0x00)
Matched DN: (null)
Error Message: (null)


268
LDAP overflow
Maintenance
Traces
➨ Search in the directory (request)

...
Internet Protocol, Src Addr: 155.132.5.1 (155.132.5.1), Dst Addr: omnivista
(155.132.0.60)
Source: 155.132.5.1 (155.132.5.1)
Destination: omnivista (155.132.0.60)
Transmission Control Protocol, Src Port: 10011 (10011), Dst Port: 389 (389 Source
port: 10011 (10011)
Message: Id=10 Search Request
Message Length: 107
Base DN: o=alcatel university
Scope: Subtree (0x02)
Dereference: Never (0x00)
Size Limit: 48
Time Limit: 3800
Attributes Only: False
Filter: (&(sn=kust)(telephonenumber=*))
Attribute: sn
Attribute: givenname
Attribute: telephonenumber
Attribute: facsimilenumber


269
LDAP overflow
Maintenance
Traces
➨ Search in the directory (reply)

...
(155.132.5.1)
Destination: 155.132.5.1 (155.132.5.1)
511181287, Ack: 2727404920
Message: Id=10 Search Entry
Message Length: 181
Distinguished Name:
TelephoneNumber=34200,Cn=TelephonicDevices,SubnetworkNodeNumber=4,
SubnetworkNumber=0, NetworkNumber=1, o=alcatel university
Attribute: sn
Value: Kustorica
Attribute: givenname
Value: Emir
Attribute: telephonenumber
Value: 34200


270
LDAP overflow
Maintenance
Traces
➨ Search in the directory (reply)

...
(155.132.5.1)
Destination: 155.132.5.1 (155.132.5.1)
511181477, Ack: 2727404920
Message: Id=10 Search Result
Message Length: 7
Result Code: Success (0x00)
Matched DN: (null)
Error Message: (null)


271

272
LDAP overflow
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the phone book overflow on an external LDAP server
MANAGEMENT
1. Manage a LDAP server, use the index number 1.

The directory root entry is o=Alcatel University.
2. Associate this LDAP directory to the entity of your sets and validate the overflow.
3. Perform a “Call By Name” on a user existing in your local phone book.

Perform a “Call By Name” on an external user and verify the appearance of the dynamic key
on a set (to check the overflow on the LDAP server).

273
LDAP overflow

274
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
275
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
276
DISA

OBJECTIVE:
◆ To describe the principles of the DISA
Alcatel OmniPCX Enterprise – DISA

277
DISA
Overview
Virtual DID
DISA 0241031555
0241031555 +31000
Carrier
31000

DISA: Direct Inward System Access

DDI = DID = Direct Inward Dialing
The DISA enables an external user of the PBX (on the public network, for example) to benefit from certain features which are normally
only accessible from within the PBX.
For example, this service may be used by people who are not in their company to enable them to use telephone services which may
normally only be accessed from within the company.
The external user accesses the PBX using a DTMF Q23 keypad and a number which corresponds to a DISA-declared trunk group.
Once connected, the user changes over to Q23 over dialing and sends commands to the PBX (the internal number of one set for
example).
In this example, you see one feature of the DISA which is called the “virtual DID”. It enables you to call any user of the system (DID or
non DID) without the help of the attendant. The DISA number is the number used to reach the PBX, so it has to be a DID number.
Once the call is established, DTMF over dialing is used to send commands to the system (a set internal number for example).

278
DISA
Overview
Management of your set parameters
DISA 0241031555
0241031555 + substitution prefix + 31000 +

personal code +immediate forward + voice mail
number
Voice mail
Forward to
Carrier
31000

Warning: no substitution prefix starting with *

279
DISA
Overview
Long distance call billed to the company
DISA 0241031555
0241031555 + substitution prefix + 31000 + personal

code + trunk circuit seizure prefix + 004122767007
Carrier
31000
004122767007

N.B.:
Charge ticket will be issued on set number which has been substituted.

280
DISA
Overview
Call by speed dialing number
DISA 0241031555
0241031555 + 6000
Speed dialing number 6000:

90155667000
Carrier
CHARGING: call is billed to

DISA Dir N°: 31000 the number 31000
0155667000

N.B.:
Charge ticket will be issued on set number declared as a DISA number in /Specific telephone services.

281
DISA
Overview
Automatic DISA
DISA 0241031555
0241031555
ISDN identification number: 0155664533
Speed dialing number 6000:

90155664533
External DISA Dir N°: 31000
Carrier
31000

N.B.:
Charge ticket will be issued on set number declared as DISA number in the abbreviated number.

282
DISA
Overview
Securing access
DISA 0241031555
Access code for DISA service
0298143535 + DISA access code + …
Carrier
31000


283
DISA
Overview
Inbound DISA Inbound DISA

Caller managed in Caller unknown in
speed dialing with speed dialing
a DISA Dir N°
NO
YES without Automatic
code substitution
YES with
code
Trunk group YES Guide: « Please dial

Access code your personal code »
Caller managed in NO
Or
speed dialing with
a DISA Dir N° and
Dialing the Code Presence of a
automatic substitution
Caller unknown in Or DISA directory
speed dialing or no number in specific
automatic substitution telephone services
Guide: « Please dial your Dialing substitution Code Calling to

service access key number » +directory N° + personal code a local user
YES
Or
Set feature Outbound call
Call using speed dialing


284
DISA
Overview
DISA temporary locking
Automatic DISA temporary locking after errors...

➨ In DISA secret code dialing
➨ in user secret code dialing after substitution
One counter is used to store the number of errors
When it equals 30 (fixed value), the DISA is temporarily

locked
➨ This counter is:
▼ incremented by 2 in case of error
▼ decrement in case of right code in the first attempt

Temporary locking DISA: the system provides the standard DISA with a failure counter which records the number of unsuccessful
attempts to enter secret codes. Once a particular threshold is reached, the DISA access is locked temporarily.
When an external user accesses the PBX via a DISA access, he must enter the DISA secret code (if validated) and the set secret code
(in manual substitution).
•if both codes are entered correctly, the user may access the PABX services,
•if not, the temporary locking DISA increments the failure counter for the secret codes on all the DISA accesses. When
this failure counter reaches a threshold which was predefined in the software (non-manageable), the DISA changes over
to a temporary locking state for all the DISA entries.
The user is disconnected from the PBX if he enters a wrong DISA or set secret code 3 times.
Operation of the failure counter
This counter is set at 0 when the telephone application is started.
It is incremented by 2 if a secret code failure occurs during a DISA access. This incrementation is stored if the external user set on-
hooks or is disconnected by the PBX after the wrong secret codes are entered. The incrementation is not stored if the correct secret
code is entered at the 2nd or 3rd attempt.
It is decremented by 1 when the secret code is entered correctly at the 1st attempt.
The counter's decrementation limit is 0 and the locking threshold is its incrementation limit (threshold set at 30).
This counter is reset to 0 during automatic or manual unlocking.

285
DISA
Overview
Manual unlock
➨ using management tool,
➨ using a prefix with an authorized local station.
A dissuasion voice guide is used during the DISA

lock, and the concerned DISA access is locked.

Operation of the temporary locking
The temporary locking phase is accessed once the locking threshold is reached (this threshold is set at 30 – non-modifiable).
During this phase:
•the DISA access attempts are locked and connected to a dissuasion voice guide,
•any new DISA access secret code failures during this phase will extend the locking duration.
The DISA service returns to normal operation (or automatic locking) after a delay. The failure counter is reset to 0.
The DISA entries are only locked temporarily on the node where the intrude attempts occurred.

286
DISA
Overview
DISA temporary locking duration (Dtl)
➨ 2 limits are used:

▼ Dtl min
▼ Dtl max
Dtl = Dtl min x failures nb during Dtl

Dtl min =1 min Dtl max limits the Dtl value
Dtl max =60 min
Dtl
normal Functioning
lock
1 min Dtl max

1st failure
Dtl max

Timers:
-timer 257 (Dtl_min): 1 min (default),
-timer 258 (Dtl_max): 60 min (default).
Incidents:
-731: DISA failure with QMCDU (access nb), locking DISA, duration in min (Dtl),
-732: manual locking DISA,
-733: manual unlocking DISA.
Remarks: DISA temporary locking is used only in the node where DISA accesses are concerned.

287
DISA
Overview
DISA temporary locking duration (Dtl)
Dtl 1 =1min
Dtl min =1 min
Dtl max =60 min Lock normal Functioning
Dtl max
1st failure
Dtl 2 = 2 x Dtl1 = 2min
Lock normal Functioning
Dtl max
2nd failure
Dtl 3 = 2 x Dtl2 = 4min
Lock normal Functioning
Dtl max
3rd failure

Remarks:
• During the DISA temporary locking process, the DISA access is locked, but the caller can also try to dial the code:
if the system detects 1 new code error, then the Dtl is double.
• If the new Dtl is equal to Dtl max, the new code failures are not taken into account.

288
DISA

OBJECTIVE:
◆ To manage the DISA feature

289
DISA
Management
DISA number management

➨ Translator / Prefix plan / Create
Number : 31600
Prefix Meaning + DISA
Trunk groups management

➨ Trunk groups / Descend hierarchy / Trunk group
/ Review modify
TS Distribution on Accesses + YES
Quality profile for voice over IP + Profile #1
---------------
---------------
DTMF end-to-end signal. + NO
Trunk group used in DISA + YES
DISA Secret Code : 1234
---------------
---------------
Automated Attendant + NO

The DISA prefix has to be a DDI number.

If “Trunk group used in DISA” information is set at NO, the DISA incoming call is routed to attendant.
The DISA code length is fixed: 4 digits.

290
DISA
Management
Management of the substitution directory number

➨ Specific telephone services / Review modify
Node Number (reserved) : 1

Instance (reserved) : 1
Flashing Equivalent : -
Flashing In End-to-End Signal. : D
---------------
---------------
DISA dir.No. : 31000
Video UCI PC node : -1
DISA status + Normal

DISA directory number: charged number in accounting when using abbreviated numbers without automatic substitution.
External DISA directory number: charged number in accounting in case of automatic substitution.

291
DISA
Management
Automatic DISA
➨ System / Descend hierarchy / Other system param. /
Descend hierarchy / DISA parameters
System Option + Automatic DISA Substitution
Automatic DISA Substitution + Without code
➨ Speed dialing / Direct speed dialing numbers / Descend

hierarchy / Review modify
Direct Speed Dial No. Prefix : 6000
Call Number : 00246131000

Directory name : Alcatel
External DISA Dir.No. : 31000
Phone book Name (Dial by name) : Alcatel
Phone book First Name : --------

Automatic DISA substitution:

-No: if the caller is managed in the speed dialing (ISDN identification) he will have to use the substitution prefix,
-Yes with code : if the caller is managed in the speed dialing (ISDN identification) he will get the telephone rights of the internal
user which is managed in the “External DISA Dir N°” in speed dialing after dialing the trunk group DISA secret
code
-Yes without code: Same feature without dialing the trunk group DISA secret code.
External DISA directory number: charged number in case of automatic substitution.

292
DISA
Management
Management of DISA lock

➨ Temporary DISA lock Activation:
▼ System / Descend hierarchy / Other system param / Descend
hierarchy / DISA parameters/ Review modify
System Option + DISA Temporary Locking
DISA Temporary Locking + True
➨ Manual unlocking DISA and DISA status info:

▼ Specific telephone services / Review modify
Flashing Equivalent : -
Flashing In End-to-End Signal. : D
---------------
---------------
DISA dir.No. : 31000
Video UCI PC node : -1
DISA status + Normal

DISA temporary locking is used to validate the DISA locking feature:

-Normal: DISA is active, this parameter is not modifiable,
-True: DISA is locked. But it can be unlocked through the DISA status parameter (mgr, 4760) or from an authorized set
using the unlocking DISA prefix.

293
DISA
Management
Management of DISA lock

➨ Unlocking DISA prefix:
▼ Translator / Prefix plan / Create
Number : 10
Prefix Meaning + Unlock DISA
➨ Unlocking DISA right:

▼ Class of service / Phone Features Classes of Service / Review modify
Tel. Features COS ID : 0
Rights
Prot.against dir.call pickup : 0

Protected against all barge-in : 0
---------------
Prot.against Automatic answer : 0
Authorized DISA unlocking : 1

The DISA can be manually unlocked:

-through the DISA status parameter (mgr, 4760),
-or from an authorized set using the unlocking DISA prefix.

294
DISA
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to setup the DISA feature
MANAGEMENT
1. Manage the DISA prefix 3X045. It has to be a DID number.
2. Use the T2 to establish a connection to the DISA feature.

2.1 Manage a DISA secret code in trunk group.
2.2 Test the DISA connection.
3. From the DISA feature:

- Manage an immediate forward of the set 3X002 to the set 3X001,
- Make an internal call,
- Make an external call.
4. Test the DISA automatic substitution

4.1 Manage the following speed dialing number:
- Direct speed dialing number: 6000,
- Call number: 902SS013X000,
- Directory Name: Alcatel,
- External DISA Dir Number: 3X000.
4.2 From extension 3X000, establish a DISA incoming and test the automatic substitution.

295
DISA
5. Manage an access code to DISA and the DISA lock feature.

5.1 Establish an incoming DISA a call. Dial 3 times a wrong code secret and on hook . Do
the same operation 5 times .
5.2 Check on the system the incident DISA locking.
5.3 Unlock manually the DISA from mgr (or 4760) and from one user .

296
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
297
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
298
Remote extension

OBJECTIVE:
◆ To describe the remote extension features
Alcatel OmniPCX Enterprise – Remote extension

299
Remote extension
Overview
The “remote extension” or “Cellular client” feature

provides to external phones the same level of services of
PBX GAP phones
External phones can be:
➨ external fixed
➨ external mobile phones

The remote extension does not have the UA level of services, but can only have the GAP level of services (see the available services
and the restrictions in the next pages).

300
Remote extension
Overview
The external user calls the specific remote extension DISA

prefix
➨ Automatic (CLI) or manual identification

▼ On the local users, the remote extension directory number or the
name (if managed) is displayed.
➨ After identification, the external user is considered as a local

set in off-hook status
A ghost equipment is used to establish the outgoing calls

from a remote extension


301
Remote extension
Overview
Available services
➨ External accesses
▼ Public accesses
▼ ARS
▼ Calls using a business account
➨ Call forwards
▼ Immediate
▼ Busy
▼ On no answer
➨ Callback request
▼ On busy subscriber
▼ On free subscriber


302
Remote extension
Overview
Available services
➨ Camp on busy set
➨ Call enquiry, broker call
➨ Transfer
➨ Three party conference
➨ Supervision (both ways)

▼ of the remote extension by a local set
▼ of a local set by the remote extension


303
Remote extension
Overview
Available services
➨ Tandem
➨ Hunting and pickup groups
➨ Manager / assistant group

▼ restricted functions: no mini messages, …
➨ PC assisted telephony (A4980, soft phone...)
➨ Hotel client


304
Remote extension
Overview
Restrictions
➨ Dial by name
➨ Mini messaging
➨ Alarm set of a notification server
➨ ACD agent


305
Remote extension
Overview
Call from remote extension Speed dialing N° : 36777

Call N° : 00250133000
External DISA Dir.No: 35777
Automatic substitution
Carrier
0250133000 Remote extension

0244135799 35799 DISA prefix
Dialing Tone
Pin code, user secret code

Trunk group DISA code Optional
Local user, speed dialing, Seize prefix,
DTMF receiver
voice mail, Mpk, key functions… xxxxx… (kept during the call)
(All available services…)
The escape sequence ** allows the remote
user to access to the services or to make an
other call


306
Remote extension
Overview
Call towards remote extension
Carrier
Remote extension
0250133000 Directory number
0250133000 35777
Remote user can use DTMF receiver

escape sequence (**) (kept during conversion)
xxxxx…
during the call to make
a call towards:
Local user, speed dialing
Seize prefix, voice mail
Mpk, key functions…
(All available services…)

The routing number for a remote extension is specified in the management.

307
Remote extension
Overview
Conference from remote extension
Carrier
0250133000
35100
Consultation DTMF receiver

(kept during conversion)
** 2 35000
35100
35000
Broker
DTMF receiver
** 1
35000
35100
Conference DTMF receiver

** 3
35000
35100


308
Remote extension
Overview
Programmable keys Speed dialing N° : 36777

Call N° : 00250133000
External DISA Dir.No: 35777
Automatic substitution
Carrier
0250133000 Remote extension

0244135799 35799 DISA prefix
Dialing Tone
MPK 5: call forwarding DTMF receiver

** 0 5 (kept during conversion)
Voice guide
Forwarding validated


309
Remote extension
Overview
Supervision keys
35100
35000
The remote extension is ringing because it

supervises the 35000 user (MPK)

Supervision key must be managed with ringing in order to ring the remote extension.

310
Remote extension

OBJECTIVE:
◆ To manage the remote extension features

311
Remote extension
Management
DISA prefix
➨ Translator / Prefix Plan / Create
▼ Number: 35799
▼ Prefix Meaning + Remote Extension DISA
➨ Trunk groups / Trunk group / Review modify
▼ Trunk Group Id: 50

▼ Trunk group used in DISA + YES
▼ DISA Secret Code: ----


312
Remote extension
Management
Users creation
➨ Users / Create
▼ Directory Number: 35777
▼ Directory name: DUPONT
▼ Shelf Address: 255
▼ Board Address: 255
▼ Equipment Address: 255
▼ Set Type: + Remote extension
▼ PIN No.: --------
▼ PIN With Secret Code: + True
➨ Users / Remote extension

▼ Remote extension number: 0520244036800

When the remote user calls the remote extension DISA prefix, he must dial the PIN code if this one is managed.
The personal code of the set must be dialed after the PIN code if PIN with secret code is managed.
Remote extension number: 0520244036800 => the number where the calls for the remote user are routed.
It is necessary to enter a number in order to route the call to the external user.

313
Remote extension
Management
Programmable keys
➨ Users / Progr.Keys / Review modify
▼ Key No.: 1
▼ Function: + Programmed
▼ Content: 35300
▼ Key No.: 2
▼ Function: + Multi-line


314
Remote extension
Management
Virtual set
➨ Users / Create
▼ Shelf Address: 255

▼ Board Address: 255
▼ Equipment Address: 255
▼ Set Type + ANALOG
▼ Ghost Z + True
▼ Ghost Z Feature + Remote extension

The number of virtual set determines the maximum number of remote extension which can make simultaneously connections on the
system.

315
Remote extension
Management
Speed dialing number
➨ Speed Dialing / Direct Speed Dialing Numbers / Direct

Speed Dialing Number prefixe / Create
▼ Direct Speed Dial No. Prefix: 36777

▼ Call Number: 0520244036800
▼ External DISA Dir.No.: 35777

This abbreviated number is used for the automatic DISA authentication.

316
Remote extension
Management
Remote set key functions
➨ Applications / Remote extension parameters / Review

modify
▼ 1 + Broker
▼ 2 + Consultation
▼ 3 + Three-Party Conference
▼ 4 + Transfer
▼ 5 + Not Assigned
▼ 0 + MPK activation
▼ * + Soft release
▼ # + Not Assigned
▼ Escape sequence: **

-Consultation: to do an enquiry call,

-Broker: back and forth,
-MPK activation: access to the 10 programmable keys,
-Soft release: release the call but not the line (dial tone is received to dial a new number),
-Escape sequence: during a call press twice « * » then after the key function
Examples :
**2 for consultation
**01 to use the programmable key 1 (of the local set)

317

318
Remote extension

OBJECTIVE:
◆ To check the remote extension feature

319
Remote extension
Maintenance
Virtual equipment and key functions
➨ (5)xa000005> remoteghosts
Neqt = 01889 Numan = 35778
Total = 1 Maximum = 5000
➨ (5)xa000005> remoteinfo 0
Key functions:
1: Broker
2: Enquiry call
3: Three-party conference
4: Transfer
5: Enquiry call
6: Not assigned
7: Not assigned
8: Not assigned
9: Not assigned
0: MPK Activation
*: Soft release
#: Not assigned
Escape sequence: **
CLI format: Standard number

Remoteghosts: provides the list of virtual sets used for remote extension connection.
Remoteinfo: provides information about keys functions setup.

320
Remote extension
Maintenance
Reset of all remote extension

➨ Remoterestart
➨ (5)xa000005> remotesets
Neqt = 01888 Numan = 35777 ExtNbr = #0500244135111 No abbreviated number associated.
Neqt = 01895 Numan = 35888 No external number associated.
Total = 2 Maximum = 5000
➨ (5)xa000005> remoteview
No communication is running.
➨ (5)xa000005> remoteview
1 communication is running.
Lcei=0003 Neqt=1888 Unman=35777 Trunk=0695
Calls checking
➨ (5)xa000005> listincall |grep 35777
|19: 4: 8: 0| 1511 | 4035(MR2_3 | 35000 |IS| CONVERS| 1888| 35777

Remoterestart: releases all remote extensions calls.
Remotesets: provides the list of all remote extensions created with the abbreviated numbers associated to each of them.
Remoteview: provides the list of the remote extensions calls established.

321
Remote extension
Maintenance
Direct T0 incoming call
➨ (5)xa000005> listincall
| Coupler: 1 9 Logic type: CPL_BRA Board: BRA 2 State: IN SERVICE |

+-----------------------------------------------------------------------------+
|: : : | | | |ST| partner one info |
|C:cp:ac:ter| neqt | typ term | dir_nb |AT|------------------------------|
|: : : | | | |US| link name | neqt | dir nb |
|-----------------------------------------------------------------------------|
|1: 9: 0: 1| 0694 | JONCT | |IS| CONVERS| 1511| 35000 |
+-----------------------------------------------------------------------------+
| Coupler:19 4 Logic type: CPL_UA Board: UA_FIC State: IN SERVICE |
+-----------------------------------------------------------------------------+
|-----------------------------------------------------------------------------|
|19: 4: 8: 0| 1511 | 4035(MR2_3 | 35000 |IS| CONVERS| 694| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| Nombre total de terminaux en com hors service: 0 |
| Nombre total de terminaux en com en service : 2 |
+-----------------------------------------------------------------------------+

An external user arrives on the DISA prefix and dials the local number 35000.
No DTMF receiver is used during the communication

322
Remote extension
Maintenance
Remote extension incoming call
➨ (5)xa000005> listincall
| Coupler: 1 9 Logic type: CPL_BRA Board: BRA 2 State: IN SERVICE |
+-----------------------------------------------------------------------------+
|-----------------------------------------------------------------------------|
|1: 9: 0: 1| 0694 | JONCT | |IS| RCL| 1132| |
+-----------------------------------------------------------------------------+
| Coupler: 1 27 Logic type: CPL_GPA Board: GPA FI State: IN SERVICE |
+-----------------------------------------------------------------------------+
|-----------------------------------------------------------------------------|
|1:27: 0: 64| 1132 | DSP_CHAN | |IS| RCL| 694| |
+-----------------------------------------------------------------------------+
| Coupler:19 4 Logic type: CPL_UA Board: UA_FIC State: IN SERVICE |
+-----------------------------------------------------------------------------+
|-----------------------------------------------------------------------------|
|19: 4: 8: 0| 1511 | 4035(MR2_3 | 35000 |IS| CONVERS| 1888| 35777 |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| Nombre total de terminaux en com hors service: 0 |
| Nombre total de terminaux en com en service : 3 |
+-----------------------------------------------------------------------------+

An external user arrives on the remote extension DISA prefix and dials the local number 35000.
A DTMF receiver is used during all the communication.

323
Remote extension
Maintenance
DTMF receiver for remote extension
➨ (5)xa000005> dspstat 1 0
Logic coupler type : INTMGD ;

MAO coupler type : GD ;
Coupler state : IN SERVICE ;
Dsp number : 2;
Enable types of detection :
- R2 with pay-load of 5 %;
- TONE with pay-load of 3 %;
- Q23 with pay-load of 4 %;
- Q23X with pay-load of 4 %;
Current pay-load : 4 %
Free pay-load : 96 %
+----------------------------------------------------------------+
| dsp neqt | dsp term | dsp state |calling neqt|calling dir nb|
|----------------------------------------------------------------|
| 1132 | 64 | GPA_Q23 | 694 | |

A DTMF receiver is used during the communication.

324
Remote extension
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage remote extension users
MANAGEMENT
X: node number
SS: classroom number
1. Manage the remote extension DISA access prefix 3X666 dedicated for the remote extension
users.
2. Declare the DISA service in the RNIS trunk group.
3. Create a virtual user 3X599 for the remote extension feature.
4. Create the remote extension 3X500 and 3X501.
5. Manage the programmable keys 1 & 2 of these sets with the multiline function.
Manage the programmable key 3 of these sets to call the user 3X000.
6. Create the abbreviated number 3X400: call number « seize prefix »+02SS0 3X110.
Information: 02SS0: digits according to the classroom for the ISDN routing.
Associate the DISA number 3X500.
7. Manage the callback translator with the default entry DEF.
8. Make a DISA access from the set 3X110 to verify that the automatic substitution on the 3X500
works correctly.

325
Remote extension
Call the set 3X000: during this communication call the set 3X500 to check that the new call is
routed to its 2nd line.
9. Perform a DISA access from a set by using the 3X501 to check that when the automatic
substitution is not available, the user must identify itself.
Call the user 3X000: during this communication, make a second call to the set 3X501 to check
that the new call is routed on a second line.
10. Make a call to the 3X500 or 3X501.
11. Manage on the 3X500 the programmable key 4 to supervise with ringing the 3X000 and
check that a call on this set rings the 3X500.
Programmables keys
1 : 3X500
2 : 3X500
3 : call 3X000
4 : supervision with ringing of 3X000
Abbreviated N°
N° 3X400
Call N° : xxxxxxxx3X110
DISA N°: 3X500 3X000
3X500
Services on line Automatic Substitution

1 : Broker
2 : Consultation
3 : Three party conference
4 : Transfer ISDN
0 : MPK activation System N
* : Soft release DISA
Escape sequence : **
Manual substitution
3X501
Programmables keys
1 : 3X501
2 : 3X501
3 : call 3X000

326
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
327
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
328
Partial Re-Routing

OBJECTIVE:
◆ To describe the Partial re-routing feature
Alcatel OmniPCX Enterprise – Partial Re-Routing

329
Telephone Facilities
Partial Re-
Re-routing: functioning
Situation
➨ An installation extension is forwarded(1) to an external
number (a mobile for example)
➨ The Partial Re-Routing feature is activated on tha public

accesses
In case of public incoming call, the CS notifies the public

Operator that the initially called number is forwarded to
an external number
➨ In such a case, the Public Operator is in charge of
establishing the call from the calling party to the forwarded
number
➨ Therefore, a TS optimization is realized on the public

accesses of the private PBX(2)

(1) The type of call forwarding can be:

- Call Forwarding unconditional (CFU)
- Call Forwarding on Busy (CFB)
- or Call Forwarding on no reply (CFNR)
Selective call forwarding or call deflection is not available with this feature
(2) Without this feature,the “B” channel” switching is realized by the Private PBX (which does not notify the Public switches of the re-
routed number)
- One TS is used for the incoming call [to reach the initial called party (PBX user)]
- A second TS is used to call the external number (forwarded extension)

330
Partial Re-
Re-routing: functioning
Example
Called Number:
0203432000
“Facility message)”
Re-routing nb:
0671431001
Signaling (only)
User “32000” forwarded on Voice communication
0671431001
➨ If the public Operator does not acknowledge this facility

message (feature not supported), after 2 seconds, the CS
establishes itself the call toward the forwarded number
(0671431001 in this example)
▼ In such a case, two TS are used like in the previous releases


331
Example of Facility message
(in connection with the previous example
| (681029:000242) 1028: Send_IO1 (link-nbr=2, sapi=0, tei=0) :

| long: 89 desti: 0 source: 15 cryst: 0 cpl: 2 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : FACILITY [62] Call ref : 80 17
|______________________________________________________________________________
|
| IE:[1c] FACILITY (l=69)
| [91] Discriminator of supplementary service applications
| [a1] INVOKE (l=66):
| Invoke Ident. : 000e (14)
| OP: 000e (14)
| [30] Sequence (l=58)
| [0a] Enumerated (l=1) 01
Re-Routed number: 0671431001
| [a1] Context specific (l=17)
| [12] Numeric string (l=10) 30 36 37 31 34 33 31 30 30 31
| [02] Integer (l=1) 01
| [40] Application (l=9) 04 03 80 90 a3 7d 02 91 81
| [80] Context specific (l=9) 32 30 33 34 33 32 30 30 30
Id of the initial called party:
|______________________________________________________________________________
203432000


332
Telephone Facilities
Partial Re-
Re-routing configuration
/Trunk groups
➨ Call Diversion in ISDN + Yes (No by default)
/System/Other System Parameters/Network parameter

➨ ISDN Rerouting in ABCF Network + True (“false” by default)
Prerequisite condition
➨ The “Call diversion” has to be implemented in the public switches
▼ Only available on “ISDN all countries” signaling type (ETSI)
Restrictions
➨ The trunk group selected for the forwarding has to be the same as
the incoming one (even in case of ARS)
➨ Only available on Business extensions


333

334
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
335
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
336

External Services PDF

Uploaded by

Copyright:

Available Formats

External Services 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

External Services 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 ENTPTE408US DELIVERY LANGUAGE English (course material in English)

Virtual self-paced training on the computer

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

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:

Describe, configure and maintain a multi-entities configuration

ISSUE DATE ISSUE DATE

Alcatel OmniPCX Enterprise External Services

File reference: ENTPTE408US

CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION

3. Complex ARS (time dependance, indirect operator)

Issue 01 REF. ENTPTE408US 0.1

6. Static and dynamic V24 accesses

10. Partial re-routing

0.2 REF. ENTPTE408US Issue 01

SECTION CHAPTER PAGE DESCRIPTION OF THE ERROR

Issue 01 REF. ENTPTE408US 0.3

0.4 REF. ENTPTE408US Issue 01

© Copyright Alcatel Business Systems 2005

◆ To describe the principles and components of calls distribution

Alcatel OmniPCX Enterprise – Multi-Entities

➨ Same behavior for all

Company “Thomas Consulting”

© Copyright Alcatel Business Systems 2005

Alcatel OmniPCX Enterprise – Multi-Entities

➨ Specific behavior per department (entity)

Company “Thomas Consulting”

Department 1 Department 2 Department 3

Entity1 Entity 2 Entity 3

© Copyright Alcatel Business Systems 2005

Alcatel OmniPCX Enterprise – Multi-Entities

Each system entity can be associated a directory number

➨ People who wants to call this company or department has to

➨ It is then necessary to put in place a «call routing» for the

▼ This is done via a calls distribution table linked to each entity

© Copyright Alcatel Business Systems 2005

Alcatel OmniPCX Enterprise – Multi-Entities

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,

➨ The switch from a state to another can be done