System Networking PDF

Alcatel OmniPCX Enterprise
PARTICIPANT'S GUIDE
System Networking
Part 1/2
REF. ENTPTE402US
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

System Networking
ACSE Core level
REFERENCE ENTPTE402US DELIVERY LANGUAGE English (course material in English)
DURATION METHOD
7 hours Virtual self-paced training on the computer
5 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 in
network
OBJECTIVES
At the end of the course, the participant will be able to:

• Configure and maintain a complex networking solution on Alcatel OmniPCX Enterprise
• Configure and maintain hybrid links
• Configure and maintain the dedicated networking phone services
• Ensure the maintenance of a networking configuration
PREREQUISITES
• To have attended Alcatel OmniPCX Enterprise System Configuration training course (Ref.: ENTPTE401US or
ENTPWB401US)
REQUIRED TECHNICAL CONFIGURATION
For i-learning
Access to the Business Partner Web Site. Internet Explorer version 5.5 or better, Macromedia Flash 7 and Acrobat
Reader version 6 or better. Virtual Microsoft Java Machine (MSJVM).
System Networking
ACSE Core level
PROGRAM DESCRIPTION
Phase 1: i-learning 7 hours

Describe the networking architecture
• Homogeneous network
• Heterogeneous network
• ABC network structure
Describe network links structure:
• ABC-F Links
• ABC-F Trunk groups
Describe the different types of routing
Describe the principles of a dialing plan in network
Describe the principles of the synchronization plan in network
Describe the principles of the IP addressing plan in network
Describe the principles of the audit
Describe the principles of the broadcast
Describe the network supervision tool: SUPROUTAGE
Describe the principles of the private to public overflow
Describe the principles of the public to private rerouting
Describe the centralized services:
• Voicemail centralization
• System messages centralization
Describe the principles of the hybrid links
Describe the principles of the VPN overflow
Describe the network facilities:
• Set supervision
• Manager / Assistant groups
• Hunt groups
• Meet-me conference
• DECT/PWT network mobility
• Calls distribution
• Ubiquity
System Networking
ACSE Core level
Phase 2: c-learning 5 days
Configure the IP addressing plan of an Alcatel OmniPCX Enterprise in networking configuration

Configure the synchronization plan of an Alcatel OmniPCX Enterprise in networking configuration
Describe, configure and maintain the network links:
• ABC-F links
• ABC-F Trunk groups
Supervise the network links via the embedded tool SUPROUTAGE
Describe, configure and perform an audit
Describe, configure and initialize the broadcast
Describe and configure the areas for the audit and the broadcast services
Describe, configure and maintain the hybrid links
Describe, configure and maintain the VPN overflow
Configure and maintain the network services:
• Set supervision
• Manager / Assistant group
• Voicemail centralization
• System messages centralization
• DECT/PWT mobility
• Hunt groups
Configure the private to public overflow
Configure the public to private rerouting
Describe and configure the ARS Server
Ensure the maintenance of the managed elements
System Networking
ACSE Core level
Alcatel University Alcatel OmniPCX Enterprise
System Networking toc.doc
DOCUMENTATION CHANGES
ISSUE DATE ISSUE DATE
01 02/06
Alcatel OmniPCX Enterprise System Networking
File reference: ENTPTE402US
GENERAL SUMMARY
Part 1
CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION
1. IP addressing in ABC network

ENTP0457P06TEUS.................................................................................................................7
ENTP0457C02TEUS ..............................................................................................................13
ENTP0457H03TEUS ..............................................................................................................19
2. System Synchronization and System Synchronization in network

ENTP0437P01TEUS...............................................................................................................23
ENTP0437P02TEUS...............................................................................................................29
ENTP0437M01TEUS..............................................................................................................35
3. ABC-F link
ENTP0434P01TEUS...............................................................................................................43
ENTP0434C01TEUS ..............................................................................................................55
ENTP0434M01TEUS..............................................................................................................65
ENTP0434H01TEUS ..............................................................................................................71
4. Suproutage
ENTP0524P01TEUS...............................................................................................................75
Issue 01 REF. ENTPTE402US 0.1

© Copyright Alcatel Business Systems 2006
Transmission or copying of this document is not permitted without prior written authorization.
The wording "Document Alcatel Business Systems" must appear on all authorized reproduction.
1
Alcatel OmniPCX Enterprise Alcatel University
toc.doc System Networking
5. Audit
ENTP0435P01TEUS...............................................................................................................89
ENTP0435C01TEUS ............................................................................................................101
ENTP0435M01TEUS............................................................................................................119
ENTP0435H01TEUS ............................................................................................................123
6. Broadcast and Broadcast area

ENTP0436P02TEUS.............................................................................................................127
ENTP0436C01TEUS ............................................................................................................141
ENTP0436M02TEUS............................................................................................................149
ENTP0436H01TEUS ............................................................................................................155
7. ABC-F Trunk Group

ENTP0434P02TEUS.............................................................................................................159
ENTP0434C02TEUS ............................................................................................................165
ENTP0434H02TEUS ............................................................................................................169
8. Hybrid links
ENTP0461P01TEUS.............................................................................................................173
ENTP0461C01TEUS ............................................................................................................189
ENTP0461C02TEUS ............................................................................................................195
ENTP0461C03TEUS ............................................................................................................201
ENTP0461C04TEUS ............................................................................................................209
ENTP0461C05TEUS ............................................................................................................215
ENTP0461C06TEUS ............................................................................................................221
ENTP0461M01TEUS............................................................................................................231
ENTP0461H01TEUS ............................................................................................................239
0.2 REF. ENTPTE402US Issue 01

2
Part 2
9. VPN overflow
ENTP0450P01TEUS.............................................................................................................247
ENTP0450C01TEUS ............................................................................................................259
ENTP0450M01TEUS............................................................................................................273
ENTP0450H01TEUS ............................................................................................................289
10. Executive / Assistant in network

ENTP0407P02TEUS.............................................................................................................293
ENTP0407M02TEUS............................................................................................................297
ENTP0407C03TEUS ............................................................................................................299
ENTP0407H02TEUS ............................................................................................................303
11. 4645 in network

ENTP0432P05TEUS.............................................................................................................307
ENTP0432M05TEUS............................................................................................................311
ENTP0432C05TEUS ............................................................................................................315
ENTP0432H05TEUS ............................................................................................................319
12. System messages centralization

ENTP0421P02TEUS.............................................................................................................323
ENTP0421C02TEUS ............................................................................................................327
ENTP0421H03TEUS ............................................................................................................333
13. DECT in network

ENTP0419P12TEUS.............................................................................................................337
ENTP0419C12TEUS ............................................................................................................343
ENTP0419M12TEUS............................................................................................................351
ENTP0419H04TEUS ............................................................................................................355
14. Hunt groups in network

ENTP0405P04TEUS.............................................................................................................359
ENTP0405C05TEUS ............................................................................................................363
ENTP0405M02TEUS............................................................................................................369
ENTP0405H03TEUS ............................................................................................................371
15. Private to public overflow

ENTP0451P01TEUS.............................................................................................................375
ENTP0451C01TEUS ............................................................................................................381
ENTP0451H01TEUS ............................................................................................................387

3
16. Public to private rerouting

ENTP0452P01TEUS.............................................................................................................391
ENTP0452C01TEUS ............................................................................................................395
ENTP0452H01TEUS ............................................................................................................401
17. ARS Server

ENTP0454P01TEUS.............................................................................................................405

4

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

6
IP Addressing in ABC-F Network

Transmission or copying of this document is not permitted without prior written authorization. 1
OBJECTIVES:
◆ To describe the IP addressing principles in ABC-F network
◆ To describe the different interfaces used
Alcatel OmniPCX Enterprise – IP Addressing in ABC network

Ref. ENTP0457P06TEUS Issue 01
7
IP Addressing in ABC-
ABC-F Network
IP configuration and ABC-
ABC-F Network
In ABC-F network, IP is required for communication

between nodes
➨ Management files exchanges between nodes
➨ System configuration, maintenance
➨ etc…
According to the topology, IP links used may be:

➨ Carried by the customer LAN
▼ LAN connection with or without router
➨ Carried by the IP/X25 tunnel

▼ Use of the maintenance PLL of the ABC-F link


8
ABC-F Network
Connections
Customer LAN connection

Node 1 Node 2
Router
LAN LAN
Management PC
Connection via the IP/X25 tunnel of the ABC-F link

ABC-F link
Node 1 Node 2
D channel
Node 1 acts like a router between the local network used by the
PC and the tunnel network used to reach node2
LAN
Management PC


9
ABC-F Network
Elements required
Each node inside the ABC network is identified by:
➨ The local IP address (Ethernet interface: eth0)
▼ Role addressing or physical
▼ Subnet Mask
▼ Default router if required
➨ The IP/X25 address (tunnel interface: tun0)
▼ Identifies in a single way the node inside the ABC network
▼ Address based on:
✦ the ABC network number: 0 to 127
✦ the node number in the network: 0 to 99

The IP/X25 configuration is mandatory for Alcatel OmniPCX Enterprise in ABC-F network environment.

10
ABC-F Network
Addressing plan
Default IP addressing
➨ Local Ethernet Interface eth0
▼ IP Address in 10.Network.Node.Type
▼ Subnet mask: 255.255.255.192
▼ Example (Network 1, Node 4, CPU Main) : 10.1.4.3
➨ Local tunnel Interface tun0
▼ IP Address in 172.30.Network.Node
▼ Subnet mask: 255.255.0.0
▼ Example (Network 1, Node 4) : 172.30.1.4
➨ RIP routing can be activated between nodes in network

The ABC network number is included between 0 and 127. For network number 0, this value is replaced by 253 in the IP address.
The node number is included between 0 and 99. For node number 0, this value is replaced by 253 in the IP address.
The CPU type can have 4 values: CPU-A, CPU-B, Main or Stand-bye. By default, values are 1,2,3 and 4 respectively.
Address example for CPU-A of node 0, network 0: 10.253.253.1
The subnet mask defines 4 IP sub networks:
•10.R.N.0 10.R.N.63 Ethernet interface
•10.R.N.64 10.R.N.127 Crystal interface (unused in OXE but used in the OmniPCX 44400)
•10.R.N.128 10.R.N.191 PPP/SLIP interface for remote connections via modem
•10.R.N.192 10.R.N.254 Unused
To allow the connection for the PC to all the nodes of the network via the IP/X25 tunnel, the different nodes have to broadcast
between them the IP networks they know. This is done by activating the routing protocol RIP on all the nodes.
If RIP is activated, the nodes don’t have to be connected to the customer LAN.
Otherwise, IP connections will be done via the LAN by using the routing possibilities of the LAN.

11
ABC-F Network
Addressing plan
Customized IP addressing (connection via the LAN)
➨ Local Ethernet Interface eth0
▼ IP Address: Given by the network administrator
▼ Subnet mask: Given by the network administrator
▼ Default router: Given by the network administrator
▼ Example: 192.168.6.214 / 24, router 192.168.6.100
➨ Local tunnel Interface tun0
▼ IP Address in 172.30.Network.Node
▼ Subnet mask: 255.255.0.0
➨ RIP routing must be inactivated on all nodes

In LAN configuration, IP parameters (address, subnet mask, default router, etc…) is given by the network administrator.
If the customer LAN used the same IP addressing plan that the IP/X25 network (172.30.0.0/16), it’s possible to modify the IP/X25
tunnel addressing in the system.
To allow the connection for the PC to all the nodes of the network, it’s mandatory to give the IP address of the default router in the
PC and all the nodes in the network.
RIP must be inactivated, when the nodes are connected to the customer LAN.
If specific IP routes are required for management, it will be necessary to create static routes in concerned nodes.

12
Netadmin in network
PROCEDURE
Netadmin in network
OBJECTIVE
- To learn how to create and modify the IP parameters of the Alcatel OmniPCX Enterprise in a
network configuration
REFERENCE
- System Documentation CD-ROM: Custom System Documentation/ Technical documentation /
Maintenance / Maintenance Commands / Netadmin
OVERVIEW
This procedure explains how to create the IP configuration in network using netadmin and if
necessary how to modify the IP/X25 tunnel using the choice 7 of the menu in netadmin.
Here, node number is 1, the same as the number defined in the ABC network.
Issue 02 REF. ENTP0457C02TEUS.doc C.1

13
Netadmin in network
PROCEDURE
1. Create a new IP configuration in ABC-F network using netadmin
1.1 Private IP addressing

Application netadmin (under mtcl) Tab
Path Warning: for a specific setup please use menu mode (netadmin -m).
Do you want to erase the existing setup (y/n default is 'n') ? y
Do you intend to use IP/X25 on your system (y/n default is 'n') ? y
X25 private network number (0 to 252, '0' by default) ? 1
Unique site number (between 0 to 252, one different number per Alcatel
e-Mediate of the network)? 1
Warning: the node name must be unique.

Enter node name (default is node001001)?

Do you want to activate internal name resolver (y/n default is 'n')?
Enter local CPU position (a or b) for duplicated configuration

or n for single CPU (default is 'n')?
Ethernet interface setup
============

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

CPU address (default is 10.1.1.1)?
Please wait, working...
The setup has been correctly achieved.
Note: It’s possible to use options to netadmin to define automatically node and network numbers,
as well as the position of the CPU (a or b).” netadmin –n 1 1” will create automatically
addresses for CPU A, B, Main and Stand-By in network 1 node 1 (-n : network id, ABC
network id and node number). “netadmin –n 1 2 b” will create automatically addresses
for CPU A, B, Main and Stand-By in network 1 node 2. Local address will be CPU B (option
b). Role addressing must be preferably managed for VoIP environment or IP architecture.
C.2 REF. ENTP0457C02TEUS.doc Issue 02

14
Netadmin in network
1.2 Customized IP addressing (LAN configuration)

Application netadmin (under mtcl) Tab
Path Warning: for a specific setup please use menu mode (netadmin -m).
Do you want to erase the existing setup (y/n default is 'n') ? y
Do you intend to use IP/X25 on your system (y/n default is 'n') ? y
X25 private network number (0 to 252, '0' by default) ? 1
Unique site number (between 0 to 252, one different number

per Alcatel e-Mediate of the network) ? 1
Warning: the node name must be unique.
Enter node name (default is node001001) ?

Do you want to activate internal name resolver (y/n default is 'n')?
Enter local CPU position (a or b) for duplicated configuration or n
for single CPU (default is 'n') ?
Ethernet interface setup
============
CPU name (default is xa001001) ?
CPU address (default is 10.1.1.1) ? 10.45.1.1
Network mask (default is 255.255.255.192) ? 255.255.255.0
Default router setup
====================
Do you use an external gateway as default router (y/n default is n) ?
y (1)
Default router name ? router1
Default router address ? 10.45.1.254
Please wait, working ...
The setup has been correctly achieved.

15
Netadmin in network
2. Modify the IP address of the IP tunnel IP/X25 using netadmin

IP/X25 interface addressing must be modified only if it conflicts with client addressing. The
modification must be applied to all network nodes.
Application netadmin -m (under mtcl) Tab
Path Alcatel e-Mediate IP Network Administration
=======================
1. 'Installation'
2. 'Show current configuration'
3. 'Local Ethernet interface'
4. 'CPU redundancy'
5. 'Role addressing'
6. 'Serial links (PPP)'
7. 'Tunnel'
8. 'Routing'
9. 'Host names and addresses'
10. ‘Copy setup’
11. ‘Security’
12. ‘DHCP configuration’
13. ‘SNMP configuration’
14. ‘Vlan configuration’
15. ‘Node configuration’
16. ‘History of last actions’
17. ‘Apply modifications’
‘Quit’
What is your choice ?
Action 7
Path 7.Tunnel setup

==============
1. 'Show local Tunnel setup'
2. 'Show logical channel setup'
3. 'Create/Update local Tunnel setup'
4. 'Delete local Tunnel setup'
0. 'Previous menu'
Action 3

16
Netadmin in network
Path Setup of the local IP/X25 interface

===================================
IP/X25 tunnel interface name (default is x001001_tun) ?
Action
Path IP/X25 tunnel interface address (default is 172.30.1.1) ?
Action
Path 7.Tunnel setup

==============
1. 'Show local Tunnel setup'
2. 'Show logical channel setup'
3. 'Create/Update local Tunnel setup'
4. 'Delete local Tunnel setup'
0. 'Previous menu'
Action a
Note: use shortcut ‘a’ to apply instead of choice 17 of the menu.
2.1 Check the IP tunnel address

Application ifconfig tun0 (under mtcl) Tab
Path tun0 Link encap:Ethernet HWaddr 00:FF:CB:ED:67:89
inet addr:172.30.1.1 Bcast:172.30.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100

17
Netadmin in network

18
IP configuration in network
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the IP configuration of the Call Server in network
MANAGEMENT
1. Manage the IP configuration of the e-Communication Server regarding to the classroom

definition (IP address, subnet-mask, router, IP/X25 tunnel). Nodes 1, 2 and 3 are in network
1. Nodes 4, 5 and 6 in network 2.
2. Check this IP configuration via the “netadmin” tool as well as with the “ipconfig” command
(with the different available options)
3. Use the “ping” command to test the IP connection between the different e-Communication
Server
4. Perform a backup of this IP configuration via the 4760i management tool (do not forget to
save, beforehand, the Linux data through the “swinst” menu)
Issue 01 REF. ENTP0457H03TEUS HO.1

19
IP configuration in network
HO.2 REF. ENTP0457H03TEUS Issue 01

20
Alcatel University NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
Alcatel University – https://www.businesspartner.alcatel.com
21
NOTES Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
22
System synchronization

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

23
Principles
The good transmission of communications over a digital

access (T0, T1, T2 or MIC) is linked to a common
synchronization between all the systems
This reference is provided by the public carrier
The ACTs of a system and of a node of a ABC network

must be synchronized via this clock.
➨ Management of a synchronization plan to allocate priorities

to the various digital accesses used
➨ Broadcast of the clock in the system using the inter-ACT

links (INT2, INTOF or RT2)
➨ Broadcast of the clock in the network using the ABC links

The public carriers must be synchronized with each other.

This common clock can be retrieved at any time on T1, T2 or MIC access (level 2 permanent) or in communication for T0 access
(level 2 established during the call).
The 512 kHz clock is extracted from the frame of a digital access.
The synchronization plan is one the first thing to be defined during an installation (in stand alone and in network).
The synchronization plan allows to allocate a synchronization priority to the various available resources (public accesses, private
accesses, ABC links, etc.) and to guarantee the use of a common clock on all systems.
The RT2 links must always be established (no multiplexer) in order to have a good synchronization resource.

24
TDM Architecture (Crystal)
In this kind of architecture, the inter-ACT links are digital

(INT2, INTOF or RT2)
The synchronization resources can be located in extension

shelves
➨ The system is able to:
▼ Broadcast the clock from the crystal 0 to a peripheral shelf
▼ Synchronize itself on a link from a extension shelf
All the shelves belong to the synchronization domain by

default (domain 0)
200 levels of synchronization priority: 0 to 199

The value 0 corresponds to the maximum priority. It is reserved for the public accesses (T1 / T2).
The value 255 means that the clock is ignored on the access.

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

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

In this example, the system has 2 T2 accesses and 1 T0 access.

The level 2 of a T2 being permanent, it is possible to retrieve the clock and to synchronize the system on the public carrier.
The associated priority in management 0 corresponds to the maximum priority (The 2 T2 provide the same clock, the system will
choose the first access to be in service). In this example, the T2 #1 synchronizes the system.
If the T2 become out of order, it is possible to synchronization the system on the T0 access of the ACT #3. The priority is lower (5)
therefore this clock can, be used only as a backup.
The ACT #1 and #2 are synchronized via the INTOF links of the ACT #0. The ACT #3 is synchronized by the RT2 link from the ACT
#2 (3-level architecture).
If the T2 #1 is out of order, the synchronizing resource will become the T2 #2 (priority equal and higher compared to the T0 access).
The clock will synchronize the ACT #0 via the INTOF link (modification of the synchronization direction).
The synchronization of the ACT #1 and #3 do not change.
All the shelves belong to the same synchronization domain.

26
IP Architecture (Media-
(Media-Gateway & Crystal)
In this kind of architecture, the inter-ACT links cannot

broadcast a 512 kHz clock
Synchronization resources must be located in:
➨ The main rack of a Media-Gateway
➨ An extension rack over IP for a Crystal architecture
Each synchronizing resource in a shelf defines an

independent synchronization domain
➨ A synchronization resource can be broadcast in the same

domain
55 levels of synchronization priority: 200 to 254)

The value 200 (highest priority in a domain) is reserved to the public accesses (T1 / T2).
The value 255 means that the clock is ignored on the access.
If there is no synchronizing resource in a shelf, the synchronization will be generated locally (by the GD or INTIP board).
The Id. of a synchronization domain is the Id. of the shelf where the synchronization resource is located.
Example: Synchronizing T2 in the main rack le rack principal (ACT 3) of a Media-Gateway creation of the synchronization domain
#3.
The 55 priority levels are independent between the domains and the nodes of an ABC network.
The resource with the priority 200 of the domain #3 will never synchronize a shelf belonging to the domain #5 or to the default
domain.
Crystal shelves connected via a compressed linked use the synchronization domains following the same principles (no synchronization
retrieval from this kind of link).

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

In this example, the call server is a CPU7.

ACT #1 and #2 and the Media-Gateway shelves #3 and #4 belong to are linked to the CS via the IP network. It is not possible to
broadcast a clock to synchronize these shelves.
The T2 #1 synchronizes the shelf #0 (maximum priority 0). The domain 0 is always allocated to the ACT where the CPU is located.
The T2 “2 synchronizes the ACT #2. As this shelf is not connected via an INT2 or INTOF link, the use of the synchronization domains
is mandatory.
The priority 200 (highest priority in a domain) allocated to the T2 will create a synchronization domain #2 (Id. Of the ACT).
The T0 synchronizes the shelf #3 of in the main rack when a communication is established. This shelf is connected via IP to the Call
Server: the use of the synchronization domains is mandatory. The priority 205 will create the synchronization domain #3 (Id. Of the
ACT).
As the shelf #4 is an extension rack of the shelf #3 and as no synchronizing resource is declared in the rack, it belongs to the
domain #3.
The CPU-GD will broadcast the clock to the MEX boards of the Media-Gateway via the HSL link (The HSL link is seen as INT2A/INT2B
link for the system).
The ACT #1 has no synchronizing resource. It stays independent for the clock that will be generated bu the iNTIP board and
broadcast to the shelf’s boards.

28
System synchronization in network

OBJECTIVE:
◆ To describe the synchronization system in an ABC-F network
Alcatel OmniPCX Enterprise – System synchronisation in ABC-F network

29
Principles
All the nodes inside an ABC network must be synchronized

with the same clock
This reference is usually provided by the public carrier
Management of a synchronization plan allows:
➨ to synchronize nodes without digital public accesses
➨ to backup the clock in case of public synchronizing access

failure
ABC-F link is used as synchronizing source on

synchronized nodes

The synchronization plan is one of the first thing to define in a system (stand alone or ABC network).
It’s used to define the order of priorities between the different sources of synchronization possible (public accesses, private accesses,
ABC F links, e.g.) and to be sure that a common clock is used in all systems.
This clock can be retrieved on permanent ABC links on T0, T1, T2 or PCM link used to transport B channels (hybrid links).

30
Rules and constraints
All synchronizing rules in stand-alone apply in network
➨ Synchronizing management is always local
➨ The ABC link is a supplementary synchronizing link
Each node must be synchronized with others
➨ Otherwise, Modem and Data communications are disturbed

or impossible
Synchronizing loop is forbidden

Node synchro Node synchro Node
1 2 3
synchro

If the communication is unsynchronized , there are some audible "crackles" if the message transmitted is voice, a degraded image if
the message transmitted is a fax and a lower useful rate if the message transmitted is a data transmission
If the clocks are too different, data, fax and modem communications can be cut-off.
Synchronization loop:
In this example, Node 1 is synchronizing node 2 and indirectly node 3 (synchronized by node2). Node is synchronizing itself with
node 3. It’s receiving his own clock, giving a loop.
This configuration type is forbidden, the system is always trying to synchronize itself to an external clock, the internal clock will be
shifted, producing the shift of the external synchro source, etc…
All communications will be disturbed and the telephone application may produce a shutdown (defense reaction).

31
Management Rules
The maximum priority is reserved for ISDN public accesses
Avoid to define consecutive priority levels to allow later

modifications
The master node for synchro in network must provide

public ISDN accesses
➨ Several public accesses if possible
➨ Several links toward the network if possible
Synchronization plan has to take into account all failure

cases
T0 accesses must have low priorities

Value 0 corresponds to the maximum synchronization priority if domains are not used, 200 otherwise.
Value 255 can break a possible synchronization loop.
Modify synchronization plan in the future:

In case of supplementary node, ISDN access, topology modification, the synchronization plan must be again analyzed.
If modifications are required, it’s very delicate to insert a new synchronization priority level between consecutive levels.
Example: on one node, levels 0, 1, 2, and 3 are used. A new access must take place of priority 2 and other accesses levels must be
shifted.
All the management has to be done again and may be on all the network.
The problem would have not occurred if priorities were defined with, 0, 10, 20, and 30 for instance (or 200, 205, 210 and 215).
Analyze of synchronization plan has to take into account a degraded mode functioning.
If a public T2 access disappears on one node, consequences have to be analyzed on all the network.
In addition, in case of ABC link breakdown (central node for instance), synchro sources of each node have to be checked.
Analyze is long and compulsory.
T0 accesses priority
T0 level 2 is not permanent (except for accesses using X25 PLL or SO/FV type).
This type of accesses is not used to synchronize a system all over the network. The T0 priority must be smaller then ABC link access.
This way, access will be synchronizing only when the node is isolated from network (ABC link breakdown) and only during external
calls.

32
Crystal architecture example
Synchro plan possible in meshed topology
T2
T2 T0 T2 0
0 Alcatel OmniPCX
Enterprise
25 Alcatel OmniPCX 0 Alcatel OmniPCX
Enterprise
Enterprise
255 10 10 255
Call Server Call Server
Call Server
255 10 10 255
10
Alcatel OmniPCX 255 255Alcatel OmniPCX

Enterprise
Enterprise
Call Server
10 10 255
Call Server
0
25 0
T0 T2
Master Node T2

Configuration example:
T2 accesses have maximum priority 0, node 5 has got 2 T2 accesses and 4 ABC links to other nodes, it’s becoming master node for
synchronization.
Node 2 doesn’t have public T2, it’s synchronizing on node 5. It’s the first synchronization level (1st system receiving the same
synchronization source), usually value 10 is used (level value per 10).
Node 1 is the first synchronization level and take value 10 on ABC link coming from node5. The synchronization level counts from the
value of the highest level of the common source (here the source is public T2 of node 5).
This access will be a backup synchro source.
Node 4 don’t have T2, it’s the first synchronization level after master node, it takes value 10 on ABC link.
Because node 3 has got 2 public T2, it can be a synchronization source to backup node 5.
In this case, node 5 synchro loop must be avoided on itself. Node 5 is the first synchronization level according to node 3 and take
value 10 on ABC link coming from node 3.
To block synchro loop, node 3 mustn’t receive the network clock, and then uses value 255 on ABC link coming from node 2.
Node 2 is synchronized on first level by node 3 and 1, so value 10 can be used.
Node 4 is synchronized on first level by node 1, so value 10 can be used on this access.
T0 are missing. No permanent synchro source is provided, so a smaller value than the smallest can be used in the node (25 in this
example). This value allows to modify easily the synchro plan later.
Inconvenient:
In case of node 3 T2 breakdown, this one will not be synchronized by the network. But if the way is changed between Node 3 and
node 5, the same problem will occur for master node.
Synchro plan is always a compromise between needs and breakdowns risks.

33
IP Media-
Media-Gateway architecture example
Synchro plan possible in line topology
Master Node
T2 T0 T0
200 254 254
N1 N2 N3
255 210 255 220
255 255
210 230
255 220
N5 N4
254 254
T0 T0

Configuration example:
Node 1 has got 1 T2 access and take the maximum priority value in domain: 200.
It’s the only node in the network with a T2, so it’s becoming master node for synchronization.
2 big options are possible for this configuration:

• Node 1 synchronizes all nodes in line and the synchro loop is broken by using N1-N5 link as non synchronizing link (255 for both
ends)
• Node 1 synchronizes nodes by using both ends of the network. In this case, if an ABC link is broken in the middle of the network,
the loss of synchro risk is limited.
In this example, the second configuration is used.
Without public T2 for other nodes, synchronizing source is always the ABC link.
But a local T0 is present, this one will be a backup.
Node 2 is synchronized on first level by node 1, so ABC link N1-N2 can use value 210 (level value x 10 + 200).
Node 5 is synchronized on first level by node 1, so ABC link N1-N5 can use value 210
Node 3 is synchronized on second level by node 2, so ABC link N2-N3 can use value 220
Node 4 is synchronized on third level by node 3, so ABC link N3-N4 can use value 230.
It’s also is synchronized on second level by node 1, so ABC link N4-N5 can use value 220.
T0 are missing. No permanent synchro source is provided, so a smaller value can be used. The smallest possible in a domain is 254,
no problem to use it.
Inconvenient:
In case of N2-N3 breakdown, Node 3 will not be synchronized with the network. But if the way is changed between Node 3 and
node 4, the same problem will occur for node 4 in case of N5-N4 failure.
Synchro plan is always a compromise between needs and breakdowns risks.

34
System Synchronization

OBJECTIVE:
◆ To maintain system synchronization.

Ref. ENTP0437M01TEUS Issue 01
35
Management control
Checking the management with infocs command
➨ Wrong synchronization
(1)xa000001> infocs
+----------------------------------------------------------------------+
| N_CR | N_CPL | TYPE | N_ACCES | PRIO | SYNC_CLOCK | TG/LK |
+----------------------------------------------------------------------+
| 0 | 5 | BPRA2 | 1 | 10 | NOT SYNC | TG:10 |
+----------------------------------------------------------------------+
+---------------------------------------------------------------------+
| Synchronization on global domain |
+---------------------------------------------------------------------+
+---------------------------------------------------------------------+
| Synchronization on domain no 1 |
+---------------------------------------------------------------------+
+---------------------------------------------------------------------+
| 1 | 3 | PRA T2 | 0 | 200 | NOT SYNC | TG:22 |
+---------------------------------------------------------------------+
| Warning domain no 1 is on free running |
+---------------------------------------------------------------------+
***************************************************************
* warning : system not synchronized *
***************************************************************

In this example there are two synchronization accesses declared.

In global domain (crystal 0, ACT type), the priority of the T0 (access 1 on BPRA2) is 10 but T0 is not activated, therefore the system is
not synchronized.
In domain 1 (IPMG), the T2 access is not in service. Synchronization is not possible, so domain 1 is synchronized by an internal clock
(free running).
Since none of the accesses is operational, the system is not synchronized (as said in the warning).
Note : information concerning the DECT synchronization have been erased for lack of space.

36
Management control
Checking the management with infocs command
➨ Correct synchronization
(2)xa000002> infocs
+----------------------------------------------------------------------+
+----------------------------------------------------------------------+
| 0 | 5 | BPRA2 | 0 | 0 | SYNCHRO | TG:22 |
+----------------------------------------------------------------------+
+---------------------------------------------------------------------+
| Synchronization on global domain |
+---------------------------------------------------------------------+
+========================== Synchro DECT ==================================+
+--------------------------------------------------------------------------+
| N_CR | N_CPL | TYPE | DECT_CLOCK | Depending Crystals |
+--------------------------------------------------------------------------+
+--------------------------------------------------------------------------+
+========= campus synchronization via INTOFS ====================+
this node 2 is SLAVE of campus synchronization (master node = ?)

synchro = PHASE_NO_OPERATION (phase shift values = 0,0)
info1=0 info2=0 info3=0 info4=0

In this example, there is one synchronized access declared.

In the global domain (crystal 0, ACT type), the priority for the T2 is 0, T2 is running (access 0 of the BPRA2 board), therefore system is
correctly synchronized.
DECT synchronization is not managed in this example, DECT Campus information is not significant in this case.

37
Hardware synchronization status
Checking the real synchronization with clockstat
➨ Local synchronization
(1)xa000001> clockstat
Crystal clock (16MHz) forced on local oscillator
flg_synchro_512=0 (0:NOK, 1:OK, 2:INIT)

flg_16MHz=1 (0:NOK, 1:OK)
Note : these flags are not significant in clock consumer role.
➨ Correct external synchronization

(1)xa000001> clockstat
Automatic synchronization of Crystal clock :
-on extern pilot clock (512 Khz) if present and of good quality
-on local oscillator otherwise
flg_synchro_512=1 (0:NOK, 1:OK, 2:INIT)

flg_16MHz=1 (0:NOK, 1:OK)
Note : these flags are not significant in clock consumer role.

clockstat command (only available on crystal hardware) gives information about IO1 board synchronization (integrated on CPU 6 or
7).
The result of this command is not linked to the management but to the real synchronization state on the CPU.
In case infocs indicates that the system is synchronized though there are symptoms of de-synchronization, you have to use clockstat
command to see the real status of the system.

38
ACT synchronization over IP
Checking INTIP-B boards synchronization
➨ INTIP-B boards are in charge of the ACT synchronization
▼ Using the board oscillator
▼ Via an external clock (512 Khz) on a T0 / T1 / T2 access
Knowing the synchronization source state
➨ Connection to the board with cpl_online Cr Cpl
➨ Enter vivaldi command
➨ Read the information with clock command
➨ Quit cpl_online with Ctrl-D

cpl_online maintenance command is used by the R&D.

This command has options that can stop or re-init the INTIP board.
Do not use any other commands except the ones described below.
(1)xa000001> cpl_online 2 10
00000055-0001317B: Connected to Crystal 2 Coupler 10

Escape character is '^D'
INTIP:vivaldi
Vivaldi>:clock

39
ACT synchronization over IP
Checking INTIP-B boards synchronization
➨ Local synchronization
Vivaldi: Coupleur role is INTIP-B Main

--------------------------------------------------------------
| Parameters | Result |
| Vivaldi to Backplane (16MHz, 8KHz, SynCC) | ON |
| 512KHz to Backplane | ON |
| Vivaldi Synch Mode | Free Run mode |
--------------------------------------------------------------
➨ Correct external synchronization
Vivaldi: Coupleur role is INTIP-B Main

--------------------------------------------------------------
| Parameters | Result |
| Vivaldi to Backplane (16MHz, 8KHz, SynCC) | ON |
| 512KHz to Backplane | ON |
| Vivaldi Synch Mode | Slave mode |
| Vivaldi Synch Source | Backplane 512KHz|
--------------------------------------------------------------

The coupler’s role is displayed in the first line.

If INTIP-B coupler is stand by, then Vivaldi to Backplane must be OFF (it means the clock isn’t broadcasted in the back panel).
Vivaldi Synch Mode indicates the way INTIP board is synchronized.
• Free Run Mode : No external synchronization, shelf is not synchronized
• Slave Mode : local oscillator is set with the Vivaldi Synch Source
• Backplane 512KHz = a T0/T1/T2 coupler gets the clock

40
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
41
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
42
ABC-F links

OBJECTIVES:
◆ To remind the principles of the network architecture up to 100 nodes
◆ To describe the principle of an ABC-F link
◆ To describe the principle of ABC routing
Alcatel OmniPCX Enterprise – ABC-F links

43
ABC-
ABC-F links
Reminder
An ABC-F network consists of nodes interconnected

together by private links
➨ ABC-F permanent link on T0 / T1 /T2
▼ D channel signaling
▼ Voice and data in the B channels
➨ Permanent hybrid link

▼ Signaling support on B channel, IP, X25, Frame relay, etc …
▼ Voice and data on PCM links, T2, IP, ATL, etc …
➨ Dynamic hybrid link

▼ Signaling on switched B channel
▼ VPN overflow or PCM links, T2, ATL, etc … for voice and data


44
ABC-
ABC-F links
Reminder
Each system is identified according to its sub network and

node number
➨ ABC network number 0 to 127
➨ Node number in the network 0 to 99
These identification elements are unique in all the ABC

network
Alcatel OmniPCX Sub-network 0 Alcatel OmniPCX
Enterprise Enterprise
Network 0 Network 0
Node 1 Node 3
ABC-F links
Network 0
Node 2

Each node is identified in the network by a number defined in the database (and in netadmin for the IP/X25 layer management).
For an empty database, the default values are:
•Network number: 0
•Node number: 1

45
ABC-
ABC-F links
Reminder
The Network capacity is limited to 100 nodes
These nodes can be:

➨ Backbone nodes (maximum 32)
▼ Provide the call routing inside the network
➨ End nodes (maximum 68)
▼ Linked to a backbone node (called then routing node)
Two types of call routing inside the network:

➨ Dynamic routing used in the backbone
➨ Static routing used between the backbone and the end

nodes

Above 32 nodes, the routing tables exchange between nodes will be too slow, it may result that nodes won’t have a correct view of
the network topology (and availability of TS in ABC link).
All the nodes in the backbone know in real time the ABC network topology.
End nodes are connected to only one routing node. They only know this node in the network.

46
ABC-
ABC-F links
Reminder
ABC links can be:
➨ Permanent: T0 / T1 / T2 ABC links or hybrid
➨ Dynamic: hybrid links on demand
Routing can be:

➨ Dynamic: X25 routing information exchange
➨ Static: No X25 routing information exchange
Possible Permanent ABC Dynamic

Configurations link ABC link
Dynamic
routing
Authorized Forbidden
Static routing Authorized Mandatory

Permanent ABC link uses a permanent physical link (usually leased).

Dynamic ABC link uses a public or private data communication channel. The link is up only for a period of time necessary for the
signaling establishment.
Dynamic routing permanently exchanges via ABC link the state of the network topology. It’s also called adaptive routing (real time
update of the routs’ cost).
It’s not compatible with a link on demand. D channel is not always established, so information exchanges will cause very often the
establishment of the signaling link via the public network.
Since the static routing doesn’t send information to the other nodes, it’s appropriate to on demand link (dynamic).
A end node only knows its routing node. All network calls will be sent to the routing node (which knows the backbone topology), it will
be in charge of routing the calls.

47
ABC-
ABC-F links
Reminder
Network architecture
X25 routing information No X25 routing
exchange Backbone Information exchange
Alcatel OmniPCX
Dynamic routing Alcatel OmniPCX
Call Server
Backbone Call Server
Routing node Routing node

Alcatel OmniPCX Alcatel OmniPCX
Call Server
Call Server
End node Routing node End node

Backbone
Routing node Backbone
Alcatel OmniPCX
Enterprise
Alcatel OmniPCX
Enterprise
Call Server
Call Server
Static routing
End node End node
End node

Definitions:
Backbone node is a node which has only dynamic routing ABC link.
Routing node is a node which has at least one dynamic routing ABC link and a static routing ABC link.
End node is a node which has one and only one static routing ABC link.
Topology:
Network topology seen by an end node only shows the link between this node and the routing node.
Network topology seen by a backbone node shows all the nodes inside the network.

48
ABC-
ABC-F links
Reminder
Topology seen from a end node

Backbone
Dynamic routing
Alcatel OmniPCX
Enterprise
Call Server
Routing node
Alcatel OmniPCX
Enterprise
Call Server
Static routing
End node

Definitions:
Backbone node is a node which has only dynamic routing ABC link.
Routing node is a node which has at least one dynamic routing ABC link and a static routing ABC link.
End node is a node which has one and only one static routing ABC link.
Topology:
Network topology seen by an end node only shows the link between this node and the routing node.
Network topology seen by a backbone node shows all the nodes inside the network.

49
ABC-
ABC-F links
Overview
A permanent ABC-F link consists of:
➨ One or several T0 / T1 / T2 link between two nodes in the

same network
▼ ISDN signaling uses ABC-F2 protocol
▼ Each ISDN link consists of one physical access
✦ These accesses (16 maximum) must be of the same type (T0, T1 or T2)
➨ A X25 permanent logical link using the D channel of one

access of this ABC link
▼ This PLL allow to exchange routing information and IP calls
establishment between nodes (IP/X25)
There can be only one ABC link between two nodes

ABC-F2 protocol (Alcatel Business Communication Features 2) is a proprietary protocol based on QSIG-GF (Q point Signaling –
Generic Features).
ABC-F2 allows to have the same level of features in network than in stand alone.
16 T2 links maximum can be in an ABC link (i.e. 480 channels).

In this configuration, there is only one ABC link but 16 different accesses.
The PLL will use the D channel of one of these accesses. In case of access failure, the routing application will automatically switch the
PLL in the D channel of another access.
Between 2 nodes, only one permanent ABC link or only one hybrid link.
Two types of ABC links can coexist on the same node.

50
ABC-
ABC-F links
Overview
ABC link constitution

Network 0 Network 0
Node 1 Node 2
Alcatel OmniPCX
Enterprise
Call Server
N1-N2 ABC link

B B B B B D B B B B B
ABC-F2 signaling X25 PLL

for B channels of the access X25 routing IP/X25 tunnel
ABC-F
Network nodes state Incidents retrieval

QSIG-GF
TS state in the ABC link Audit & Broadcast, FTP
QSIG-BC
Etc.. Etc..
ISDN

D channel of ABC link ensures:

•Signaling for B channels of the access
•Routing of X25 routing information via the PLL automatically created (maintenance PLL)
•IP/X25 tunnel which allows to create an IP network between nodes of the network via the maintenance PLL.This one allows to:
•exchange audit and broadcast data
•centralization of system messages on a supervisor node
•accounting tickets retrieval to the node connected to the OmniVista 4760
•etc…

51
ABC-
ABC-F links
Numbering Plan
Numbering plan must be homogeneous in the network

➨ Same prefixes and suffixes used in the different nodes
➨ Extension numbers are managed locally on each node and are

single within the network
Two types of prefix can be used
➨ Routing number
▼ One prefix corresponds to a slice of remote directory numbers
➨ Network number
▼ One prefix will correspond to a remote directory number
The two types of prefix can coexist

In network configuration an homogeneous numbering plan is strongly recommended. Speed dialing numbers and class of service
must be common (local speed dialing numbers can be reserved for specific needs). Otherwise, problems can occur:
•Impossible phone calls
•Unexploitable facilities in some cases (incompatible class of service, incoherent suffixes)
•Disturbed DECT sets mobility
Prefixes examples:
•Routing number: 32
•Network Number: 0
•Node Number/ABC-F Trunk Group: 3
•Number of Digits: 5
•Number With Subaddress (ISDN) + NO
•Network number: 32000
•Network Number: 0
•Node Number/ABC-F Trunk Group: 2
•Number With Subaddress (ISDN) + NO
•Type + Station
•A network number is always priority on a routing number.
•All call beginning by "32" with 5 digits will be routed to node “3" of sub network “0", except if it’s 32000 which will be routed to
node “2".

52
ABC-
ABC-F links
Call routing in network
X25 routing knows in real time the state of routes available

in the network
For this state a cost is related
The call cost:
➨ Depends on free TS number for this type of call
➨ Is the sum of all the routes used
➨ Routing choose always the less expensive route
➨ For an end node, the routes’ cost is always calculated by the

routing node

The routes’ cost is calculated for each call type (Voice / DATA / VPN /X25 / Nx64 / Frame Relay).
It’s directly depending on the number of available TS (or VC, rate) on ABC links.
For one communication, values are:
•More than 8 TS: cost = 1
•Between 2 and 7 TS: cost = 2
•Only one TS: cost = 3
•No TS: unlimited cost

53
ABC-
ABC-F links
Call routing in network
Call routing example

Alcatel OmniPCX
Enterprise Alcatel OmniPCX
Enterprise
Call Server
Call Server
12 free TS
Network 0 Network 0
Node 1 Cost = 1 Node 3
1 free TS 9 free TS
Cost = 3 Cost = 1
31000
32000: Network No
Network Number: 0
Node Number: 2 Network 0 32000
Type: Station Node 2
Routing Application Cost calculation Route choice

State of network resources Total cost N1-N3-N2 < N1-N2
Destination node: 2
Possibility 1: Link N1-N2 Possibility 1: Cost 3 Possibility 1: Route refused
Possibility 2: Link N1-N3 & N3-N2 Possibility 2: Cost 1 + 1 = 2 Possibility 2: Route selected
The route N1-N3-N2 will be used because total the cost is the lowest

The routes’ cost is calculated for each call type (Voice / DATA / VPN /X25 / Nx64 / Frame Relay).
It’s directly depending on the number of available TS (or VC, rate) on ABC links.
For one communication, values are:
•More than 8 TS: cost = 1
•Between 2 and 7 TS: cost = 2
•Only one TS: cost = 3
•No TS: unlimited cost

54
T0 / T1 / T2 ABC-F link
PROCEDURE
OBJECTIVE
- To learn how to create a permanent T0 / T1 / T2 ABC-F link
REFERENCE
- System Documentation CD-ROM System Documentation / Technical documentation / Private
Networks / ABC-F homogeneous private network / ABC-F homogeneous private network /
OVERVIEW
The example consists of ABC-F link between nodes 1 and 2 in network 1 using ISDN link.

55
PROCEDURE
1. Preliminary management
Application mgr
Path system
Action Review / Modify
On node 1 On node 2
Node number 1 1
Network number 1 2
Nb PABX in transit Enter the number of nodes Enter the number of nodes
Action CTRL-V two times
Note: Don’t forget to reboot the Call Server to taken into account these values.
2. Management of the routing numbers

Application mgr
Path Translator / Prefix plan
Action Create
On node 1 On node 2
Number 32 31
Prefix meaning Routing number Routing number
Action CTRL+V
Network number 1 1
Node / ABC-F trunk group number 2 1
Number of digits 5 5
Action CTRL+V
Note: Routing numbers allow to easily check the good working of the ABC-F links. After the audit,
all directory numbers of remote users will be translated in network numbers, routing
numbers will become useless.

56
3. Creation of the optimization prefixes for communications transfer

Application mgr
Action Create
On node 1 On node 2
Number 31990 32990
Prefix meaning Local features Local features
Action CTRL+V
Local features PABX address in PABX address in
DPNSS DPNSS
Action CTRL+V
Note: PABX address in DPNSS: This feature allows the system to transfer communications between
nodes and releasing B channels (example: a set of node 1 calls a set of node 2 who
transfers the call to a third use of node 1. Without these prefixes ,the communication
between the two users of node 1 will use 2 B channels on the ABC-F link).

57
4. Create the permanent ABC-F link on T2
4.1 Create the permanent ABC-F link

Application mgr
Path Inter-nodes link / Logical links (ABC-F)
Action Create
On node 1 On node 2
Link Name N1-N2 N2-N1
Link Type + T2 + T2
Adjacent Node 2 1
Adjacent Network 1 1
B Channel Choice +YES +NO
Signal Establis.Mode + Permanent User + Permanent User
Routing Type + Dynamic Routing + Dynamic Routing
Action CTRL-V
MUX presence + NO + NO
Action CTRL-V
Note: B Channel Choice: Item used for negotiating the B channel offered by the node: one end
must be in exclusive mode (item validated), the other end in preferential mode (item not
validated).
4.2 Create the link access

Application mgr
Path Inter-nodes link / Logical links (ABC-F) / Link Bus Access
Action Create
On node 1 On node 2
Physical Access 1-2-0 1-2-0
Access Type + T2 + T2
Action CTRL-V

58
4.3 Modify the digital access on node 1 (master node) and node 2 (user node)
Application mgr
Path Shelf / Board / Digital Access
On node 1 On node 2
Shelf Address 1 1
Board Address 2 2
T0/T2 Access No. 0 0
Action CTRL-V
Synchronization Priority 255 210
Network Mode + YES + NO
Action CTRL-V
Note: Network Mode: this parameter specifies level 2 operating mode on the link. One end of the
link must be set to user mode (item disabled), the other to network mode (item enabled).

59

Application mgr
Action Create
On node 1 On node 2
Link Type + T1 + T1
Adjacent Node 2 1
Action CTRL-V
Action CTRL-V
validated).

Application mgr
Action Create
On node 1 On node 2
Action CTRL-V

60
Application mgr
On node 1 On node 2
Shelf Address 1 1
Board Address 2 2
Action CTRL-V
Action CTRL-V

61

Application mgr
Action Create
On node 1 On node 2
Link Type + T0 + T0
Adjacent Node 2 1
Action CTRL-V
Action CTRL-V
validated).

Application mgr
Action Create
On node 1 On node 2
Action CTRL-V

62
Application mgr
On node 1 On node 2
Shelf Address 1 1
Board Address 4 4
Action CTRL-V
Access Type S0 + YES + NO
Action CTRL-V
Note: Access Type S0: This attribute concerns the initialization of the T0 interfaces to level 2. One
side must be validated and the other side not validated.

63
7. Wait for the link activation

Application Suproutage (under mtcl) Tab
Path Node Routing Supervision... xa001001
1: Description of Output Links
2: Network's Global Topology
3: Description of a Distant Node's Links
4: Optimum Path Tree
5: Description of the Output Trunks
6: Network Trunk Descriptions
7: Description of local X.25 DTE
Q: Exit the Supervisor
Action 2
Example of display before link activation:
NETWORK TOPOLOGY COSTS FOR TELEPH Quality Voic
Local Node: 1
1 2
Cost = 1(TS_FREE>=8), 2(8>TS_FREE>=2), 3(TS_FREE=1), S(TS_FREE=0)

X25D:<1> TELEPH:<2> Nx64:<3> FRELAY:<4> VPN:<5> QUIT:<Q>
Example of display when the link is up:

Local Node: 1
1 1 2


64
ABC-F link

OBJECTIVE:
◆ To maintain ABC-F link
Alcatel OmniPCX Enterprise – ABC-F Link

65
ABC-
ABC-F links
Maintenance commands
trkvisu ‘Link nb’ (2000-2099) command
(102)xa001002> trkvisu 2000
link 2000 ;
****************** data in Trunk_Group structure ****************
******** data FAISCEAU_NON_RESIDENT

nomfais = N2-N1
************
typjo : (6) => T2
************
node_number = 1
network_number = 1
************
******** data ARTERE(link)

cat_signa = 18 ch_canalb = 1 deborde_it = 1 access_turn = 1 mode_reseau = 0
presence_mux = 0 sig_mode = Permanent (0) routing_mode = Dyn (0)
************

In order to only display important information the result of the command is shorten.
trkvisu command syntax :

trkvisu <num_TG (0-1999) | num_Link (2000-2099) | all | trk | link | comp | ip>
Command’s result :
•Trunk group name, related trunk type, nodes and network destination numbers.
•Pieces of information concerning the management :
•Signalization category : 18 (ABC-F)
•B channel choice enabled (ch_canalb = 1)
•Data to voice TS overflow enabled (deborde_it = 1)
•TS distribution enabled (access_turn = 1)
•Network mode disabled (mode_reseau = 0)
•MUX presence disabled (presence_mux = 0)
•Signal establishment mode = Permanent user (sig_mode = Permanent)
•Routing type = Dynamic routing (routing_mode = Dyn)

66
ABC-
ABC-F links
lkvisu all or lkvisu ‘Node nb’ commands
(102)xa000000> lkvisu all

List of all links node by node
node 1 :
=========
link 2000 (N2-N1 ) T2 sig_mode = Permanent, routing_mode = Dyn
-- acces 1 in 0-5-0 : => GPA 3 : T2, ON
trkstat ‘Link nb’ (2000-2099) command
➨ Displayed information is the same as a classical ISDN trunk

group

lkvisu command syntax :

lkvisu all
lkvisu (node: 0-99)
Management pieces of information on each node :

•Link’s name, number and type (T2)
•Signalization type (PERMANENT)
•Routing type (Dyn)
•The list of all accesses of the link and for each one the main and the backup carriers :
•Coupler’s position (0-5-0), X25 access cluster (GPA 3), the signalization type (T2) and the status operational or not (ON)

67
ABC-
ABC-F links
ABC-
ABC-F Traces
Starting a level 3 ISDN trace
➨ Use of t3 script
▼ trc i ; t3
➨ Use of tracing tools
▼ trc i ; tuner km ; tuner clear-traces cpu cpl ; mtracer –a
Stopping the trace
➨ Stop mtracer by Ctrl-C, empty the buffer and re-init trc
▼ tuner clear-traces ; trc i
➨ Restart mtracer with default configuration
▼ dhs3_init –R MTRACER

trc command is used to filter accesses to be traced.

Example of trace :
______________________________________________________________________________
| (049625:000093) 905: Send_IO1 (link-nbr=0, sapi=0, tei=0) :
| long: 491 desti: 0 source: 11 cryst: 0 cpl: 5 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 03
|
| CONCATENATION OF 2 SEGMENTED MESSAGES
|______________________________________________________________________________
|
| [a1] Sending complete
| EI :[04] BEARER_CAPABILITY (l=3) :80 90 a3
| EI :[18] CHANNEL (l=3) : a9 83 85 -> T2 : B channel 5 exclusive
| EI :[1c] FACILITY (l=98)
| Service discriminator [91] : supplementary service
| [aa] NFE (l=6) :
| [80] Source Entity : (l=1) : End_PTNX
| [82] Destination Entity (l=1) : End_PTNX
| [a1] INVOKE (l=16) :
| Invoke Ident. : 2ee0 (12000)
| OP : ECMA RO_CALLING_NAME (0)
| [80] Name presentation allowed (l=4) : 'DUPONT Jean'
| [a1] INVOKE (l=69) :
| Invoke Ident. : 0001 (1)
| OP : ALCATEL RO_CLASSMARKS (1)
| [30] Sequence (l=56) :
| [80] Feature identifier (l=5) : 06 44 6a 1f 04
| [82] Cug (l=1) : 00
| [83] Trunk call priority (l=1) : 00
| [ab] Sequence of Project data (l=41) :
| [30] Sequence (l=15) :

68
ABC-
ABC-F links
suproutage tool
ABC-F links detailed information via suproutage

OUTPUT LINKS DESCRIPTION FOR NODE 2 NUMBER OF LINKS = 1
|Link| Node|PCM|Activ| State |Position|Circ| Circ | Circ|

| | | | | | | |Transp|Occup|
| 1 | 1 | 3| 1 |_ CONNECT2 | 0 5 0| 30 | 30 | 0 |
| | | | | | | | | |
PCM Detail – Link number, PCM number and <Entrer> Hybrid <H> QUIT <Q>

The state of each link toward other nodes is given under menu 1 « Description of Output Links ».
To node 1, we can clearly see that the access is operational (CONNECT2), is given also the coupler position.
The access cluster number is written in column PCM.
Available TS are displayed in the Circuits columns.
It is possible to display the status of an access TS by entering the link number, dash, followed by the PCM number (example : 1-3).

69
ABC-
ABC-F links
To delete a link
To delete an ABC-F link
➨ Deactivate the X25 access cluster for each access
▼ / Inter-Node Links / Logical Links / Link Bus Access / X25

Synchronization
✦ X25 Cluster access + Disable
or
▼ / X25 / X25 Access Cluster / Review/Modify
✦ Operational + NO
➨ Delete the link’s accesses
➨ Delete the link
Topology will be updated after a shutdown

In the OmniVista 4760 or 4760i application, the field X25 Synchronization is available under tab Action.
It’s better to use X25 Synchronization in the management field of the trunk groups, it avoids to deactivate another access cluster by
mistake.

70
Permanent ABC link on T2
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to put into service permanent ABC links on T2
MANAGEMENT
1 Topology
Node A Node C
ABC links
Node A,B,C= Node 1,2,3

or Node B
Node A,B,C= Node 4,5,6
Subnetwork 1 : nodes 1, 2 and 3

Subnetwork 2 : nodes 4, 5 and 6
1.1. Run netadmin on each node
1.2. Manage (or verify) the node number and subnetwork on each node ( System
parameters)
1.3. Create the necessary PRA couplers on each node.
Issue 01 REF. ENTP0434H01TEUS.doc HO.1

71
Permanent ABC link on T2
1.4. Node A management:

1.4.1 Create an ABC link to node B
1.5. Node B management:
1.5.1 Create an ABC link to node A
1.6. Create an ABC link to node C.
1.7. Node C management:
1.7.1 Create an ABC link to node B
2 Check the different links status using suproutage command.
3 Make some telephone tests (create routing prefixes and network prefixes).
4 Connect (telnet) on other nodes via the tunnel.
HO.2 REF. ENTP0434H01TEUS.doc Issue 01

72
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
73
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
74
Suproutage

OBJECTIVE:
◆ To describe the maintenance tool suproutage
Alcatel OmniPCX Enterprise – Suproutage

75
Suproutage
Overview
Suproutage tool allows to display in real time

information on:
➨ Status of ABC-F link between nodes
➨ The cost related to each link according to the call type
▼ Used by routing application to determine the route for a call
▼ Used to view available Time Slots on a link or trunk groups (VPN)
➨ Resources used by VPN
➨ VC used for X25 applications
▼ Tunnel, Broadcast, Virtual services, etc…


76
Suproutage
Main menu
Main menu of suproutage
Node Routing Supervision... node1

─────────────────────────────────

Suproutage menu:
1: This option displays the data concerning the outgoing links (ABC-F T2/T1 links or hybrid links) of the supervised node (status of
accesses, channels, X25 VC used, etc…).
2: This option displays the topology of the network seen from the local node (nodes and links between these nodes). The limit is 6
nodes displayed. But suproutage can display data “seen” from an another node.
3: This option describes all the output links of any given node of the network (information obtained by X25 routing).
4: For networks of less than 6 nodes, the option "Optimum path tree" provides the optimal path that will be used for the next
communication (Phone or X25).
5: This option gives information concerning the outgoing trunk groups of the supervised node, ISDN trunk groups used for VPN or
distributed trunk groups (supervised by routing trunk groups).
6: This option is used to display all the trunk groups which link the local OmniPCX Enterprise network to a second network.
7: This option gives information concerning the X25 applications.
Q: Exit
Use ? for help.

77
Suproutage
Main menus
Description of Output Links (choice 1)

Output Hybrid Link Description for Node 1
│ Node│Access│ Main Signal │ Second. Sig │Circ│ Circ │ Circ│

│ │ │ Position LAP Activ│ Position LAP Activ│ │Transp│Occup│
│ 2 │ 1 │ IP 19, 0, 0 R 1 1 │ │ 0 │ 0 │ 0 │
│ │ │ │ │ │ │ │
PCM Detail - Node number, Access number <Enter> Link <L> QUIT <Q>

This option displays the data concerning the outgoing links of the supervised node.
To display hybrid links, press key H (press L for previous display).
In this example, the following information are available for each link:
•Remote node n° and related access
•Link type and coupler’s position (in case of IP hybrid link position is 19-0-0 (fictive coupler)).
•Routing (R symbol) is used on this link and the virtual service used this X25 group access (LAP n° blackened)
•Active access (Active=1)
•No backup signaling
•No trunks for this access (Circuit=0)
•If trunks are related to the access, TS numbers in DATA quality (Transparent) and busy TS are displayed
For further details concerning a PCM, enter : link number - PCM number and carriage return.
•Example: 2-1 to display details of the access 2 of the link 1

78
Suproutage
Main menus
Network's global topology (choice 2)

Local Node : 1 ┌───┐
│ 2│
└─┬─┘
│
┌──────────────────────────────── 1 ─────────┘
│
│
│
│
┌───┤ ┌───┐
│ 1├─────────────────────────14───── S ────14────────────────────────┤ 3│
└───┘ └───┘
Cost = 1 (TS_FREE>=8), 2 (8>TS_FREE>=2), 3 (TS_FREE=1), S (TS_FREE=0)


It is not possible to display properly more than 6 nodes. If there are more than 6 nodes in the network, the user must choose the
nodes he wishes to display (6 maximum). Two methods are available:
•select the nodes you wish to display, then type 1: Nodes Topology. The topology describing the selected nodes and their links is then
displayed.
•select only one node, then type 2 : Adjacent Nodes Topology. The selected node is then displayed with 5 of its adjacent nodes and
the links between them.
If a node has more adjacent nodes than the ones displayed in the topology, a ? is displayed on this node. You can move from one ?
to another one using the left and right arrows. If you press CR on a node with a ? it will display the topology of this node with its
closest nodes.
In this example, the following information are available:

•Links out of node 1 are up (straight lines between nodes)
•Cost between nodes 1 and 2 is 1, it means that more than 8 TS are free
•Cost between nodes 1 and 2 is S, it means that the link is saturated but number 14 means that the node has resources to adjacent
network 14. This number indicates the possibility of VPN overflow.
•The cost given by routing is the Voice cost (cf. top right of page).
•To view the VPN cost (available TS on trunk groups supervised by routing), press key 5 (information VPN : <5> in bottom of page).
•Keys 1, 2, 3 and 4 allows respectively to display cost for X25 communications in D channel, phone calls, Nx64 data
communications, X25 calls in Frame Relay overflow in B channel.

79
Suproutage
Main menus
Network's global topology (choice 2) – VPN costs

NETWORK TOPOLOGY COSTS FOR VPN Quality Voic
│ 2│
└───┘
┌───┐ ┌───┐
│ 1├─────────────────────────14───── 1 ────14────────────────────────┤ 3│
└───┘ └───┘


After pressing key 5 (VPN costs):

•Between nodes 1 and 2, no VPN cost exists
•Between nodes 1 and 3, value 1 indicates cost related to VPN calls (cf. bottom of page).

80
Suproutage
Main menus
Output links description (choice 3)

OUTPUT LINKS DESCRIPTION FOR NODE 1
Local Node: 1
Rate = 600
IO2 Resources : 0
│ Node│ COST │Numb TS Free│Numb TS Free│Overflow│ Network│

│DESTI│X25D X25B TelDATA TelVoic│Max Data/PCM│ Total DATA │ VPN │Overflow│
│ 1 │ 1 S S S │ ??? │ ??? │ 1 │ 14 │
GRAPHICAL DISPLAY: <1> QUIT: <Q>

Data given by routing (display of link between 3 and 1):

• Selected node is 3 (in title of page)
• Local node is 1: number of the node where suproutage is launched.
• On node 3, a link exists toward node 1 with following characteristics:
• X25 communications in D channel are possible (at least 8 VC available because cost is 1)
• Phone calls in transparent mode or frame relay are impossible (cost is S, it means saturated)
• Information about available TS not displayed (??? instead)
• A VPN overflow exists (value 1 in the column)
• Adjacent network used for VPN is 14

81
Suproutage
Main menus
Description of the outgoing trunk groups (choice 5)

OUTPUT TRUNKS DESCRIPTION FOR NODE 1
│Netwk│PCM│ LAP│Activ│ State │Position│Circ│ Circ │ Circ│ TrnkId│

│ │ │ │ │ │ │ │Transp│Occup│ │
│ 14 │ 1│ 2│ 0 │ INIT_T2 │ 3 2 0│ 30 │ 30 │ 0 │ 12 │
│ │ │ │ │ │ │ │ │ │ │
For PCM Details <Enter Network number-PCM number> QUIT <Q>

Information given:
• Trunk groups list supervized by routing on local node (node 1)
• Adjacent network 14 related to the digital access 3-2-0 is in initial state
• X25 group access is the second (LAP 2)
• There are 30 trunks in this T2
• Trunk groups used is n° 12 (TrnkId=12)
For further details concerning a PCM, enter: network number - PCM number and carriage return.
•Example: 14-1 for Description of the PCM 3 of network 14

82
Suproutage
Main menus
Description of the trunk groups of a network (choice 6)

TRUNKS LINKED TO NETWORK DESCRIPTION 14
Local Node: 1
Rate = 600 Quality DATA
│ Node│ COST │ COST Tel │ COST VPN │ COST │ COST COMP│TrnkId│

│DESTI│X25D X25B│DATAIn DATAOut│DATAIn DATAOut│ X31 │ DATAOut │ DATA │
│ 3 │ OFF OFF│ 1 1 │ 1 1 │ OFF │ 1 │ 32 │
│ 1 │ OFF OFF│ 1 1 │ 1 1 │ S │ 1 │ 12 │
NEXT PAGE: <v> QUIT: <Q>

This option is used to display all the trunk groups which link the local OmniPCX Enterprise network to a second network.
Data given for each node of the network:

• TrnkId Data : number of the trunk group for a Data communication.
• Node N° that routing supervises (column Node DESTI)
• X25 COST: No cost for X25 communications in channel D and no X25 communication possible on B channel.
• COST Tel: cost for phone communications. The cost is different according to the direction of the communication (In or Out).
• COST VPN: cost for the VPN communications. The cost is different according to the direction of the communication (In or Out).
• COST X31: no X31 communication possible on B channel.
• COST COMP: Outgoing Compressed communications

83
Suproutage
Main menus
Description of local X.25 DTE (choice 7)

Description of X.25 DTE for node 1
│ Position │ Type│Activ│LAP│TEI│ LCN │VCBsy│PVCBsy│SWin│SPkt│ X25 Address │

│ X25 Brdc │Appli│ 1 │ 0│194│ 1-127│ 0 │ 0 │ 4 │ 256│ │
│ Servirt │Appli│ 1 │ 0│184│ 1-127│ 0 │ 0 │ 4 │ 256│ │
│ Hybrid │Appli│ 1 │ 0│183│ 1-127│ 0 │ 0 │ 4 │ 256│ │
│ Tunnel │Appli│ 1 │ 0│134│ 1-127│ 0 │ 0 │ 4 │ 256│ │
│ Mao │Appli│ 1 │ 0│108│ 1-127│ 1 │ 0 │ 4 │ 256│ │
Retour au menu <Q>

Default X25 DTE concern X25 applications used in the ABC-F network. They are used through the different access points of the X25
cluster access 0.
For each application, following pieces of information are available :

•A symbolic name
•X25 Brdc: Information broadcast in non connected mode through the virtual service
•Servirt: Virtual service associated to a particular VC (unused by default, the VC uses the PLL 0)
•Hybrid: Hybrid links management
•Tunne: IP/X25 calls establishment through the PLL 0 of the link
•Mao: Management modifications broadcast in the network
•Access point N° (TEI column)
•Related logical channels
•Virtual circuits and permanent virtual circuits occupied in real time (here broadcast uses a VC to another node)
•Specific data linked to X25 application parameters (size of window and packets)
•Possible X25 call nb (external applications)

84
Suproutage
Other commands
Redraw screen
➨ Press space bar
Help display
➨ Press key ? inside menus
Isolate a link
➨ A link can be isolated for test without cutting off current calls
➨ Press key i to:
▼ Choose nodes to isolate (use arrows and return)
▼ Choose isolation type (local or global) or establish back the link

Once the nodes are chose, you have to specify the type of isolation (or reestablishment) :
• Local Isolation (1) or local reestablishment (2):
• The link is considered as deactivated only by the X25 routing of local node.
• The other nodes consider that the link is still active.
• Global Isolation (3) or global reestablishment (4):
• The link is considered as deactivated by all the nodes of the network.
• This access won’t be used for calls
This feature can also be used to determine the path of a call in the network
• Isolation of an access toward the node
• Menu 4 : Optimum Path Tree
• Analysis of the given route

85
Suproutage
Other commands
Manual isolation of a link in topology (key i)

│ 2│
└─┬─┘
│
┌──────────────────────────────── 1 ─────────┘
│
│
│
│
┌───┤ ┌───┐
│ 1├_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._┤ 3│
└───┘ └───┘


In this example, link between node 1 and 3 has been globally isolated (_._._._. line).

86
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
87
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
88
Audit

OBJECTIVES:
◆ To describe audit principles
◆ To describe different phases of audit
Alcatel OmniPCX Enterprise – Audit

89
Audit
Overview
Audit is a tool allowing an exceptional coherency update

of the PABXs database of the ABC network.
Audit is done in two phases:
➨ Construction of a reference database
▼ This database is updated on only one local or remote node (called

reference node)
▼ It’s built with other nodes databases and reference database
➨ Downloading of the reference database over the

network
▼ All databases are updated with this database

All audit phases except simulation modify directly the database of the node on which the audit is launched.
For this reason, it’s mandatory to realize a simulation ( specific menu in audit) before launching a real audit

90
Audit
Reference building
In a ABC network, some objects must be in common
➨ Examples: numbering plan, phonebook, trunks
➨ These objects are called common objects
During construction of the reference database, these

objects are retrieved from all concerned nodes by the audit
▼ These data are analyzed by the reference node
▼ It’s inserted in the database if there is no incoherency with local node

List of the 31 common objects:
Dialing Plan Entity Incoming State Hours

Phone Book Discriminator Selector
Trunk Groups DID number translator
Entities Access Prefix
Call Distribution tables Trunk group NPD selector
DDI Translation Skill Domain
Voice mail titulars
Skill parameters
Free Numbers Ranges List
PIN (Personal Ident.No.) Ubiquity Assistant Template
Suffix Plan Supervision keys
Hunt Group Recording Resource
Progr.Keys ATM Address List
PSPDN Complementary Address Call Restriction Service
X25 Command RSI
Entity Spd Dial Number Range SIP Dictionary
Entity Outgoing State Hours Network Routing Table

91
Audit
Reference building
Some objects can’t be in common with other nodes
➨ Examples: access or phone feature class of service
➨ These objects are called local objects in audit
During construction of the reference database, these

objects are retrieved without changes on reference node
➨ reference on local node
▼ No change in the database
➨ reference on remote node
▼ Substitution of local objects in the database

List of the 30 local objects:
Speed Dialing Number

Voice Mail Dir.No
VPN Overflow
Classes of Service
Access COS
Phone Features COS
Project account code
Cost Center
Tones
Timers
Security and Access Control
Flow Control
Input Configuration
Output Configuration
Data menu: Logon
Set-up
V120
X25 Packet Handler
Appli Rights
Dialing (Numbering) Discrimin.
Caller Rights COS
Public Access COS
Private Access COS
Network Access COS
Business Access COS
Trunk Group Access COS
Numbering Plan Description
Connection COS / CLU
4645 VM VPIM
LDAP Phone Books

92
Audit
Reference downloading
Reference node is the only node updated in the network by

now
To put in coherency all the network, this one will

download his own tables in other nodes
➨ Common objects downloading
▼ Analyze and insertion in databases of the others nodes if no

inconsistency is detected
➨ Local objects downloading
▼ Systematic substitution of existing data in concerned tables on all the

nodes
All the network is now updated

In case of incoherency between common objects and local management, what ever during the creation or downloading of the
reference, incidents are generated and errors are stored in audit reports and system messages.
Audit usually works directly with database tables, in case of failure it’s not possible to come back to the previous state ( only if a
restoration of the previous database is done).
Therefore, it’s compulsory to use before the SIMULATION menu.

93
Audit
Cases for use
Audit can be used in the following cases:
➨ Data coherency in network

▼ Preventive or curative maintenance for existing nodes
➨ Addition of a node in the network

▼ Importation of the network database to the added node
Two types of functioning
➨ Manual activation in the following cases:
▼ Node addition or update in case of link problems
➨ Automatic activation in the following cases:
▼ Periodic maintenance or pre-programmed simulation


94
Audit
Functioning principles
Nodes databases must be compatible between them
Audit can be partial (one or several objects or nodes)
Conversion of the database tables into ASCII format files
File compression before ftp transfer
Exchange in client-server mode
Storage of audit actions in the MAO History
Storage of actions and incidents in LOG files (ASCII)

All the nodes in network must have the same software release. But, in case of migration of network to a new release, it’s sometimes
difficult to update simultaneously all the nodes. In this case, it’s useful to block the audit for some objects not compatible together
according to the release.
Information on release compatibility can be found in the installation procedure for version (available on BPWS).
An ASCII file is created for each table. This allows file compression and faster transfer via ABC link (IP/X25 tunnel use).
Client-server: Structure message exchange (request, acknowledgement...).

The reference node is the server. All clients are simultaneously contacted for common object request.
Concerned tables are in ASCII format, locally compressed and each client (remote node) informs the server (reference node) when is
ready to send data. Then the server asks each node individually to send data.
Each operation done in database is stored in MAO history.

The maohist command allows to find executed action traces and source of actions.
Error files are viewable directly in audit menu.

Moreover, incidents can be locally created during audit in case of incoherency with local management (incidents stored in system
messages).

95
Audit
Sequence of the audit
Reference building on local node

DATABASE
AUDIT: Reference building : DATABASE
AUDIT: Reference building :
1 Local node reference (node 1)
Local node reference (node 1) Common objects
Audit on all objects Trunk group
Audit on all objects
DDI translator
Objects sent 3
Numbering plan
Node 1 Node 2 ...
Request of
2 common objects
Local objects
DATABASE ABC link Class of service
DATABASE ...
Common objects
Trunk group AB
DDI translator
Updates N1
Updates N1 2 Cl Translates
Translatesthethedata
data
tables ink ABC
Numbering plan tables 4 co m R e q link ofofcommon
commonobjects
objects
with N2 table mo estu
... with N2 table n o of into
intoASCII
ASCIIfiles
filesand
and
contents bje
contents sends
N2 data Ob cts sendscompressed
compressed
Updates N1 jec files
Updates N1 ts s files
tables ent
tables 6
N3 data with N3 table
with N3 table 5 DATABASE
contents DATABASE
contents
Node 3 Common objects
Local objects Trunk group
Class of service DDI translator
... Numbering plan
...
The content of the local objects do not change.
The content of the local objects do not change.
The node 1 database is now the reference and contains
The node 1 database is now the reference and contains 7 Local objects
all common data
all common data Class of service
…

During reference building, Node 1 ask simultaneously other nodes tables.

Local objects are not required because in this example reference is local node.
If reference was node 2, this one would have sent his own local objects which would have been replaced those of node 1.
When nodes are ready (compressed ASCII files available) they inform reference node.
This one request each node to send common objects.
After analysis, data are inserted into node 1 tables.
Node 2 and 3 databases are unchanged (and are not updated with network data).
At this time of audit, only reference node contains all information.

96
Audit
Sequence of the audit
Downloading the reference in the network

DATABASE
AUDIT : Reference downloading DATABASE
AUDIT : Reference downloading
1 Local node reference (node 1)
Local node reference (node 1) Common objects
Audit on all objects Trunk group
Audit on all objects Results of audit
3 DDI translator
Numbering plan
Node 1 Node 2 ...
Common and
2
local objects sent Local objects
Class of service
DATABASE ABC link
DATABASE ...
Common objects
Trunk group AB
DDI translator
After reference
After reference Cl Insertion
Insertionofofcommon
common
building, N1 3 Co ink ABC link
Numbering plan building, N1 lo c mm objects
objectsininlocal
local
database contains al o on database
... database contains bje and database
information coming c ts
information coming Substitution
Database updated from node 2 & 3.
from node 2 & 3.
Re
sul
sen
t Substitutionofoflocal
local
with common objects Local objects are not ts o objects
objects
Local objects are not fa
of nodes of the modified (local node ud
modified (local node it
network is reference). DATABASE
is reference). 3 DATABASE
Node 3 Common objects
Local objects Trunk group
Class of service DDI translator
... Numbering plan
...
Local objects are copied on all nodes.
Local objects are copied on all nodes.
Databases of all nodes in the network are updated
Databases of all nodes in the network are updated 7 Local
Local objects
objects
with reference database. Class
with reference database. Class of
of service
service
...
...

Node reference database contains all network data.

During reference loading, node 1 will send as compressed ASCII files his own database tables (audit on all objects).
Each will receive and process the files.
Common objects are analyzed and inserted in local databases of nodes 2 and 3. In case of problem (set created on 2 nodes with
same number for instance), node will generate a local error and send information to reference node.
Common objects contain now all network information.
Local objects are replaced by local reference node (common objects can’t be in common like class of service for instance).
Each node sends audit results report to reference node.
This report can be check from audit menu.
Now all network nodes are updated.

97
Audit
Audit procedure
Audit modifies directly database tables
➨ In case of error, old data doesn’t exist anymore
To limit the risks, it’s mandatory to use simulation

mode
➨ In this mode, audit works on a copy of tables and doesn’t
modify the database
➨ Simulation exists for 2 steps of audit
After analysis and correction of errors, the corresponding

phase (construction or downloading of reference) can be
launched on the network

In simulation, audit doesn’t really work on tables, mentioned actions in results report are not done.
So, some errors will be “normal”, because concerned data are not written, modifications are refused by MAO.
Example:
• Entity 2 exists on node 2 and is unknown on node 1. This one inserts in the table with no error (but doesn’t insert it in the real
database)
• Node 2 translator contains entity call prefix for entity 2. This one must be inserted in translator of node, but result report will not
mention this error. Indeed, entity 2 doesn’t exist in the database and the translator modification is refused, although
everything is correct.
This kind of error will not occur in a real audit.
The same kind of problem arises during the very first one audit.
Objects as entities, attendant groups, attendants and all call distribution elements are in the same case. The system will refuse for
instance the creation of attendant, attendant or entity call prefixes in the dialing plan because these elements are unknown at this
stage of audit. In the same way, during entities creation, call distribution is often refused because it contains attendant or
attendant call prefixes not yet known.
To deal with this problem, two solutions exist:
1) - Do a partial audit for dialing plan, entities, attendant, attendant groups, call distribution
- Do a general audit
1) - Do a general audit twice

98
Audit
Audit procedure
First phase of Audit:

No modification
➨ Simulation: Immediate execution in the database
of the reference node
▼ «Reference building » on local node
✦ Objects selection for audit and port of audit
▼ Simulation launching
▼ Consultation of simulation results and errors correction

Only the reference node
➨ Immediate execution database is updated
in the network
▼ «Reference building » on local node
▼ Real audit launching
▼ Analysis of audit results

It’s compulsory to use simulation phase.

A simulation can be programmed to be run during the week-end for instance, results will be available for analysis next week.
On the other hand, it’s strongly misadvised to use the delayed programming to do a general audit.
It’s impossible to use simulation of the two phases without running one real audit.
System reaction in case of complete simulation and real audit next:
•Simulation of construction of reference No modification done in database
•Simulation of loading of reference Modifications are simulated with current database,
but not with the existing one created after a real audit
•Construction of reference Result is conform to simulation
•Loading of reference Completely unpredictable result

99
Audit
Audit procedure
Second phase of Audit:

No modification
➨ Simulation: Immediate execution in the database
of nodes in network
▼ «Reference downloading » in the network
✦ Objects selection for audit and port of audit
▼ Simulation launching
▼ Consultation of simulation results and errors correction

All database nodes
➨ Immediate execution in the network
are updated
▼ «Reference downloading » in the network
▼ Real audit launching
▼ Analysis of audit results

Consequences of reference loading on network nodes can’t be known without simulation.

For local objects, the result is substitution of objects of the nodes by the objects of the reference node.
For common objects, only simulation will allow to determine the behavior of other nodes during insertion of data in local database.
It’s useful to realize a database backup on the hard disk before audit for sensitive systems.

100
Audit
PROCEDURE
Audit
OBJECTIVE
- To learn how to launch an audit
REFERENCE
- System Documentation CD-ROM: System Documentation / Technical documentation / Private
Networks / ABC-F homogeneous private network / Audit and Broadcast
OVERVIEW
Two cases are possible, a first audit or an update audit:
1. Running a first audit
a) Simulation: build a reference on the local node (sub menu 4 of menu 1)

- selection of objects used as reference on the local node,
- selection of a network node (x0000n_tun),
Next, following the results analysis, carry out the manual updates required.
b) Build a reference on the local node (sub menu 1)

Some objects are not audited the first time, so do simulation and real building a second
time.
c) Simulation: build a reference on the local node (sub menu 4 of menu 1)
d) Next, following the results analysis, carry out the manual updates required.
e) Build a reference on the local node (sub menu 1)

101
Audit
f) simulation of node data load on the network (sub menu 4 of menu 1)

g) node data load on the network

- selection of the network node (x0000n_tun).
Some objects are not loaded the first time, so do simulation and real loading a second
time
h) simulation of node data load on the network (sub menu 4 of menu 1)
i) node data load on the network
2. Running an update audit
a) Simulation: build a reference on the local node (sub menu 4 of menu 1)

Next, following the results analysis, carry out the manual updates required.
b) Build a reference on the local node (sub menu 1)

c) simulation of node data load on the network (sub menu 4 of menu 1)

d) node data load on the network

- selection of the network node (x0000n_tun).

102
Audit
PROCEDURE
1. Save Data Base on all the nodes

In case of problem, it should be possible to come back on previous state.
2. Configuration
From R6.1, it’s possible to manage nodes and objects lists in the configuration menu (10
maximum for each type). This way, several configurations can be saved and reused for next
audits. Files are backup under /usr4/mao directory of the hard disk with the names
name_list_objects.obl for objects list files and name_list_nodes.ndl for nodes list files.
To manage nodes and objects lists, you can use paragraph 2.2 of this procedure.
Before R6.1, it’s possible to select nodes and objects for audit but it’s impossible to save
several configurations. To manage nodes and objects selection, you can use next paragraph.

103
Audit
2.1 Nodes and objects Selection

Application audit –l US0 (under mtcl)
Action Choice: 4 - Configuration
Action Choice: 1 - Selection of nodes
Path Selection of nodes
Exit
1 local 2 x001002_tun (xm001002)
3 - Select all the nodes 4 - Deselect all the nodes
Choice [0 - 4] :
Action 3
0 Exit
1 + local 2 + x001002_tun (xm001002)
Choice [0 - 4] :
Action 0
Remark Symbol + appears in front of selected nodes
Result For some objects, the reference building is done from
only one remote node.
If you specify the local node, this step will not be done.
Choice [1 - 2] :
Action Hit RETURN to continue
Result 1 * local 2 + x001002_tun (xm001002)
Hit RETURN to continue
Remark The symbol * is displayed next to reference node
Action Hit return to get back to the configuration menu
Result Configuration
0 – Exit
1 - Selection of nodes
2 - Selection of objects
3 - Timer Configuration
4 - Manage node lists
5 - Manage object lists
Choice [0 - 5] :

104
Audit
Action 2
Path Selection of objects
1 Numbering Plan 2 Phone Book
3 Speed Numbering Number 4 Trunk Groups
………………………………………………………………………………
59 SIP Dictionnary 60 LDAP Phone Books
61 Network Routing Table
62 – Select all the objects 63 – Deselect all the objects
Choice [0 – 63]:
Action 62
Result Additionnal choice [0 - 63, ? : Display again] :
Action ?
Result 0 - Exit
1 + Numbering Plan 2 + Phone Book
3 + Speed Numbering Number 4 + Trunk Groups
………………………………………………………………………………
59 + SIP Dictionnary 60 + LDAP Phone Books
61 + Network Routing Table
62 - Select all the objects 63 - Deselect all the objects
Additionnal choice [0 - 63, ? : Display again] :
Action 0
Remark Symbol + appears in front of selected objects

105
Audit
2.2 Manage nodes and objects lists

Application audit –l US0 (under mtcl)
Action Choice: 4 - Configuration
Path Configuration
0 – Exit
Choice [0 - 5] :
Action 4
Path Manage node lists
0 – Exit
1 - View node lists
2 - Create node list
3 - Modify node list
4 - Delete node list
Choice [0 - 4] :
Action 2
Path Create node list
Node list name:
Action list_node1 and hit RETURN
Result Selection of nodes

0 Exit
1 local () 2 x001002_tun (xm001002)
Choice [0 - 4] :
Action 3
Selection of nodes
0 Exit
1+ local () 2 + x001002_tun (xm001002)
Choice [0 - 4] :
Action 0
Remark Symbol + appears in front of selected nodes

106
Audit
Result For some objects, the reference building is done from

only one remote node.
If you specify the local node, this step will not be done.
Choice [1 - 2] :
Result 1 * local 2 + x001002_tun
(xm001002)
Action Hit RETURN to get back to the menu
Result Manage node lists
0 – Exit
1 - View node lists
2 - Create node list
3 - Modify node list
4 - Delete node list
Choice [0 - 4] :
Action 1
Path View node lists
Select a node list :
0 – Exit
1 - Liste_node1.ndl
Action 1
Result 1 * local 2 + x001002_tun (xm001002)
Action Hit RETURN, then use choice 0 and go back to configuration menu
Result Configuration
0 – Exit
Choice [0 - 5] :

107
Audit
Action 5
Result Manage object lists
0 – Exit
1 - View object lists
2 - Create object list
3 - Modify object list
4 - Delete object list
Choice [0 - 4] :
Action 2
Result Create object list
Object list name : List_object1
Action list_objects1 and hit RETURN

3 Speed Numbering Number 4 Trunk Groups
5 Entities 6 Call Distribution tables
…………………………………………………………….
59 SIP Dictionnary 60 LDAP Phone Books
62 – Select all the objects 63 – Deselect all the objects
Choice [0 - 63] :
Action 62
Additional choice [0 - 63, ? : Display again] :
Action ?
0 - Exit
…………………………………………………………….
Additional choice [0 - 63, ? : Display again] :

108
Audit
Action 0
Path Object list created : List_object1
Manage object lists
0 – Exit
1 - View object lists
2 - Create object list
3 - Modify object list
4 - Delete object list
Choice [0 - 4] :
Action 1
Path View object lists
0 – Exit
1 - List_object1.obl
Choice [0 - 1] :
Action 1
0 - Exit
…………………………………………………………….
Remark Symbol + appears in front of selected objects

109
Audit
3. Launching of immediate simulation reference building in the local

node
Application audit –l US0 (via mtcl)
Action Choice: 1 - Activation of the consistency checks
Action Choice: 4 - Simulation: Immediate running
Path Simulation
0 - Exit
1 - Reference building in the local node
2 - Reference downloading over the network
Choice [0 - 2]:
Action 1
0 – Exit
3 * Speed Numbering Number 4 Trunk Groups
…………………………………………………………….
59 SIP Dictionnary 60 * LDAP Phone Books
62 - General checks 63 - Selected objects
64 - Load an object list
Choice [0 - 64] :
Remark Symbol * appears in front of local objects
Action 64
Path Select a object list
0 – Exit
Choice [0 - 1] :
Action 1
0: Exit
1: Global network
2: Only one node
3: Selected nodes
4 : Node list restore
Choice [0 - 4]:
Action 4

110
Audit
Path Select a node list :

0 – Exit
1 - Liste_node1.ndl
Action 1
Remark Simulation is being done. Once it is finished, you should proceed to the
simulation results analysis
Path Results of the consistency checks
0 - Exit
1 - Results Analysis
2 - Global Results
Choice [0 - 3]:
Action 1
Results of the consistency checks:
0: on screen
1: in a file
Choice [0 - 1]:
Action 0
Deletion Of The Check Log Files After Reading (0=No/Default, 1=Yes) ?
Action 1
Note: Simulation results analysis is being displayed, at the end of this display, press enter to come
back to previous menu.
Please note that you may have to act on the programming according to the simulation
results.

111
Audit
4. Real Reference building in the local node

Action Choice: 1 - Immediate running
Path Immediate running
0 - Exit
Choice [0 - 2]:
Action 1
0 – Exit
…………………………………………………………….
Choice [0 - 64] :
Action 64
0 – Exit
Choice [0 - 1] :
Action 1
0: Exit
1: Global network
2: Only one node
3: Selected nodes
Choice [0 - 4]:
Action 4
0 – Exit
1 - Liste_node1.ndl

112
Audit
Action 1
Remark Audit is being done. Once it is finished, you should proceed to the results
analysis
0 - Exit
2 - Global Results
Choice [0 - 3]:
Action 1
Result Results of the consistency checks:
0: on screen
1: in a file
Choice [0 - 1]:
Action 0
Action 1
Note: Results analysis is being displayed, at the end of this display, press enter to come back to
previous menu.
results.
Example of error during the first audit

The system will refuse for instance the creation of attendant, attendant or entity call prefixes in
the dialing plan because these elements are unknown at this stage of audit. In the same way,
during entities creation, call distribution is often refused because it contains attendant or
attendant call prefixes not yet known.
To deal with this problem, two solutions exist:
- Do a partial audit for dialing plan, entities, attendant, attendant groups, call distribution
- Do a general audit
- Do a general audit twice
Conclusion: After a first audit, it’s necessary to do the simulation of building the
reference follow-up of the real immediate running of building the reference a second
time.
For this, do a second time paragraphs 3 and 4.

113
Audit
5. Launching of immediate simulation reference network

downloading over the network
Action Choice: 4 - Simulation: Immediate running
Result Simulation
0 - Exit
Choice [0 - 2]:
Action 2
0 – Exit
…………………………………………………………
59 SIP Dictionary 60 * LDAP Phone Books
Choice [0 - 64] :
Action 64
0 – Exit
Choice [0 - 1] :
Action 1
0: Exit
1: Global network
2: Only one node
3: Selected nodes
Choice [0 - 4]:
Action 4

114
Audit

0 – Exit
1 - Liste_node1.ndl
Action 1
Remark Simulation is being done. Once it is finished, you should proceed to the
simulation results analysis
0 - Exit
2 - Global Results
Choice [0 - 3]:
Action 1
0: on screen
1: in a file
Choice [0 - 1]:
Action 0
Action 1
Remark Simulation results analysis is being displayed, at the end of this display, press
enter to come back to previous menu
Please note that you may have to act on the programming according to the
simulation results

115
Audit
6. Launching of immediate reference network downloading over the

network
Application audit –l US0 (viamtcl)
Action Choice: 1 - Immediate running
Action 1
Path Immediate running
0 - Exit
Choice [0 - 2]:
Action 2
0 – Exit
…………………………………………………………….
Choice [0 - 64] :
Action 64
0 – Exit
Choice [0 - 1] :
Action 1
0: Exit
1: Global network
2: Only one node
3: Selected nodes
Choice [0 - 4]:
Action 4

116
Audit

0 – Exit
1 - Liste_node1.ndl
Action 1
Remark Audit is being done. Once it is finished, you should proceed to the results
analysis
0 - Exit
2 - Global Results
Choice [0 - 3]:
Action 1
0: on screen
1: in a file
Choice [0 - 1]:
Action 0
Action 1
Note: Results analysis is being displayed, at the end of this display, press enter to come back to
previous menu.
results
After a first audit, it’s necessary to do the simulation of downloading the reference follow-
up of the real immediate running of downloading the reference a second time.
For this, do a second time paragraphs 5 and 6.

117
Audit

118
Audit

OBJECTIVE:
◆ To maintain Audit application

119
Audit
Files used
Log files of the Audit application
➨ Reference building
▼ /usr4/mao/bmaudit.log (contains audit results)
▼ /usr4/mao/bmreport.log (not directly exploitable)
➨ Reference downloading
▼ /usr4/mao/lmaudit.log (contains audit results)
▼ /usr4/mao/lmreport.log (not directly exploitable)
➨ Content of the exchanged tables
▼ /usr4/mao/ad* (one file per table)
✦ Those files are not directly exploitable

The Audit configuration files (node customization, audited objects, etc…) are located also under /usr4/mao.

120
Audit
Processes used
Programs launched by the Audit application
➨ Reference building
▼ Process buildmain (reference node)
▼ Process builddist (network nodes)
➨ Reference downloading
▼ Process loadmain (reference node)
▼ Process loaddist (network nodes)
Broadcast configuration
➨ No audit on non broadcasted objects

If audit is blocked, it maybe because there are still active processes running on some nodes.
In that case, another audit cannot be launched (since one is still running).
If there is not any other audit running, you just have to kill those processes (kill n° PID).
Broadcast configuration is kept by audit. This concerns broadcasted objects (or not) as well broadcast areas.
If audited node is in a different area than the reference node, then some tables may not be transferred.

121
Audit
X25 parameters
In case of some problems occurring during the audit,

check X25 application parameters
➨ X25 / X25 Access Cluster N° 0 / X25 Access Point
▼ Access Point 134: Tunnel application
✦ Audit files transfer
▼ This access point must be operational
➨ X25 / Network Nodes
▼ IP & IP/X25 addresses must be coherent
▼ Broadcast must be enabled for this node

In case of errors in the management, data configured in the network nodes might be wrong. So some problems might occur for
broadcast and / or audit (wrong IP address for instance, node with broadcast disabled, etc…).

122
Audit
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to configure the audit application
MANAGEMENT
WARNING: Audit application must be launched on a single node only
For this Lab, the configuration is:
- Sub-network 1: Nodes 1 to 3
- Sub-network 2: Nodes 4 to 6
1. Launch an audit on nodes 1 and 4 by following these steps: Nodes 1 and 4 will be the
reference nodes.
1.1. Configure the audit application in order to select all the nodes and all objects during the
audit. Use the procedure ENTP0435C01TEUS.
1.2. Run a simulation of reference database construction on nodes 1 and 4.
1.3. Consult the result files concerning the audit simulation.
1.4. Launch the “real” construction of the reference database on nodes 1 and 4.
1.5. Consult the result files concerning the audit.
1.6. Run a simulation of reference database downloading to nodes 2, 3, 5 and 6.
1.7. Consult the result files.
1.8. Launch the real downloading of the reference database to nodes 2, 3, 5 and 6.
1.9. Consult the result files

123
Audit
2. During the first audit, several errors on the call distribution occur. You must run the audit
twice.
2.1. Repeat the steps from step 1.2 to correct the error linked to the calls distribution.

124
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
125
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
126
Broadcast areas

OBJECTIVES:
◆ To describe the broadcast principle in ABC network
◆ To describe the areas broadcast principle
Alcatel OmniPCX Enterprise – Broadcast areas

127
Broadcast
Overview
Broadcast application is a tool allowing a permanent coherency

update of the PABXs database of the ABC network.
➨ Creation of sets, speed dialing numbers, trunks, etc…
➨ Modification (class of service, phonebooks, etc…)
➨ Deletion (sets, entities, etc…)
Broadcast configuration allows to specify:
➨ Input/Output objects management
➨ Nodes selection
IP/X25 tunnel is used for broadcast

IP/X25 tunnel allows to use IP facilities (FTP file transfer, telnet, etc…) through X25 PLL available in signaling channel of ABC link

128
Broadcast
Overview
Broadcast principles
Broadcast
application
Node 1 Node 2
DB ABC link DB
AB
Broadcast Cl
ink ABC
application link
DB
MAO
management
Node 3
Broadcast
application

Modifications done in node 1 database in MAO are reflected in nodes 2 and 3 by the application

129
Broadcast
IP/X25 tunnel
Broadcast principles
Node 1 Node 2
D channel
DB DB
Broadcast Broadcast
application application
IPC 108 IPC 108

IPC 134 IPC 134
D channel
PH PLL PH

A modification in node 1 database will be sent to broadcast application to all nodes of the network configured in this application.
Broadcast uses access point (IPC) 108 of X25 applications group (group 0). IP/X25 tunnel uses access point 134 of the same group.
All X25 communications are provided by X25 packets handler (PH: Packets Handler).
To allow communication between the two applications on node 1 and 2, broadcast (IPC 108) request tunnel (IPC 134) application to
establish a virtual circuit with tunnel of node 2. Access point 108 of node 2 (remote broadcast application) is then linked with node 1
via the tunnel.
Modifications are reflected in the node 2 database.
The same operation will occur if data are modified in node 2, broadcast will request B channel establishment with broadcast
application to transfer information.

130
Broadcast
Functioning
Broadcast Initialization on each nodes
Definition of the following elements
➨ Broadcast area and nodes list
➨ The list and behavior of the various objects

▼ Emission behavior
✦ Emission in network / In area / No broadcast
▼ Reception behavior
✦ From network / In area / Not taken into account
Files creation during MAO modifications
➨ Temporary files and LOG files

Modification broadcast is done automatically. For particular reasons, broadcast can be forced immediately without waiting for LOG
file creation timer.
It’s done in menu /System/Broadcast/Immediate broadcast (and Action tab in 4760).
Broadcast reset:
All sequences counters and existing LOG files are reset.
Broadcast configuration:
Nodes concerned by broadcast and objects behavior modifications can be chosen.
Files creation by broadcast:

Modifications are stored in a buffer to limit number of files sent to other nodes and created in LOG files.
temporary buffers called:
•cm_cb.sav network broadcast
•area_cm_cb.sav area broadcast
LOG files called:
•LOG.N.Seq N:Node N°, Seq : Sequence N° (modification index )
•A.Z.N.Seq A: area, Z: zone N°, N :Node N°, Seq : Sequence N°

131
Broadcast
Functioning
For each LOG file creation, broadcast sends the

sequences counter value to other nodes
➨ This file contains index number of modifications
If sequence number is different from theirs, other nodes

request missing LOG files transfer
➨ LOG files sent to other nodes
➨ Apply modifications of data inside LOG file
MAO errors management into RLOG files
➨ If modification is not compatible with local management,

broadcast register the MAO error

Sequences counter:
lupd.dat file contains modifications index for all nodes.
For each node,the last number of LOG file loaded or created is given (local LOG file).
lupd.dat is transmitted to the remote node.
If a shift has been observed between the sequence numbers of the LOG files, a file transfer request is sent.
Example:
the management operation which occurred on node 1 creates a LOG file with the higher Index, 18.
lupd.dat is transmitted to the node 2 and observed a shift. So a LOG file is requested.
The name is based on node number and sequence number, here is LOG.1.18.
LOG file is executed and database is updated.
Error Files:
•RLOG.N.Seq N:Node N°, Seq: Sequence N° (modification index )
•EA.Z.N.Seq EA: Error Area, Z: zone N°, N:Node N°, Seq: Sequence N°

132
Broadcast
Internal mechanisms
Files creation
MAO
Modification
Broadcast timer duration

cm_cb.sav
area_cm_cb.sav
Adding
modifications LOG file
creation
Broadcast poll
lupd.dat lupd.dat
update reception
LOG.N.Seq or A.Z.N.Seq request

Sequence
comparison
LOG file sent

LOG.N.Seq
reception
Acknowledgment
request
RLOG.N.Seq Possible
MAO action
creation error

Database modifications are stored in buffer file.

According to modified objects, behavior and area broadcast management, the file used will be cm_cb.sav or area_cm_cb.sav.
At the end of broadcast buffer timer (10 minutes by default), this file is copied in the new LOG.N.Seq or A.Z.N.Seq file and
lupd.dat file is updated.
If the modification is deletion, timer is 10 seconds.
At the end of broadcast poll timer (10 minutes by default), nodes receive lupd.dat file.
If a shift has been observed between the sequence numbers of the LOG files, a file transfer request is sent.
The LOG file is transmitted and the node received acknowledgment request from remote nodes. If all transfers are acknowledged, the
file is removed. By default, 20 LOG files are stored on disk, but the maximum number of LOG files can be 127.
Node receives LOG files and execute actions included in this file.
In case of management errors (impossible or incoherent modification) a RLOG.N.Seq or EA.Z.N.Seq file is created on the
concerned node.
This one can be seen in maintenance tool on the node where modifications have been done.
Specific case for dynamic ABC link (on request link):

ABC link is not permanently established. As soon as a call is established, broadcast can use the IP/X25 tunnel to transfer waiting files.
However, if no communication is established, broadcast application will establish itself the link to transfer files as soon as on of these
threshold is reached:
•Dynamic Link Poll Timer (60 minutes by default)
•Threshold (%log files) for dyn.links (50% by default, 20 by default, 127 maximum)

133
Broadcast
Example
Set 3100 creation on node 1

Diffusion lupd.dat file
Diffusion lupd.dat file
1 Prefix plan: Emission/Reception
Prefix plan: Emission/Reception
sequence N° 4
sequence N° 4
Network broadcast
Network broadcast
2 Node 1 Node 2
cm_cb.sav file
cm_cb.sav file
Prefix plan ABC link
•Number : 31000
•Type : Network No
Phonebook
3 AB
Cl ABC
•Phonebook No:31000 ink
End of timer of link
•Name : UA_31000 End of timer of
broadcast buffer
•Type : Users broadcast buffer
5 4
LOG.1.5 file lupd.dat file

LOG.1.5 file lupd.dat file Node 3
Sequence N° 5
Prefix plan Sequence N° 5
•Number: 31000
•Type: Network No
Phonebook
Directory No: 31000 6
•Name: UA_31000
cm_cb.sav file is empty
•Type: Users cm_cb.sav file is empty
it’s available for other modifications
it’s available for other modifications

1) Broadcast application is configured to broadcast in the network all modifications in prefix plan
2) 31000 set creation gives following MAO modifications for other nodes:
• network number to node 1 creation
• Entry created in phonebook
3) At the end of broadcast buffer timer, lupd.dat file is updated
4) Sequence number is changer from 4 to 5
5) LOG file is created, with name LOG.1.5
6) Buffer is empty available to store new modifications

134
Broadcast
Example
lupd.dat N2 file
Lupd.dat broadcast lupd.dat N2 file
Node 1 :
LOG Sequence 4
Node 2 :
LOG Sequence 9
Node 3 :
LOG.1.5 request 3 LOG Sequence 24
Node1 Node 2
1 lupd.dat sent
lupd.dat file
lupd.dat file
ABC link lupd.dat N1 file
Node 1 : lupd.dat N1 file
LOG Sequence 5 Node 1 :
Node 2 : LOG Sequence 5
LOG Sequence 9 AB Node 2 :
1 Cl ABC
Node 3 : ink LOG Sequence 9
lu p
LOG Sequence 24 d.d link
at Node 3 :
sen
LO t LOG Sequence 24
G.
1. 5r
eq
u es
t
3 lupd.dat N3 file
lupd.dat N3 file
2 Node 3 Node 1 :
LOG Sequence 4
Node 2 and 3 request for file LOG.1.5 Node 2 :
Node 2 and 3 request for file LOG.1.5
at the end of broadcast poll timer LOG Sequence 9
at the end of broadcast poll timer
Node 3 :
LOG Sequence 24

1) Node 1 sends the lupd.dat file to other nodes. They compare sequence numbers with their own file.
2) at the end of broadcast poll timer, nodes request for missing LOG files
3) In this case, new sequence number is 5, previously the known number was 4, so only one file is missing: LOG.1.5

135
Broadcast
Example
lupd.dat N2 file
LOG file use lupd.dat N2 file
Node 1 :
7
LOG Sequence 5
31000 network Node 2 :
31000 network
prefix creation LOG Sequence 9
prefix creation
Node 3 :
Acknowledgment 5 LOG Sequence 24
Node 1 Node 2
4 LOG.1.5 sent
lupd.dat file
lupd.dat file
ABC link Broadcast
Node 1 : Broadcast
Configuration
LOG Sequence 5 6 Configuration
Node 2 :
AB Reception behavior :
LOG Sequence 9 4 Cl Reception behavior :
ink ABC • Prefix plan :
Node 3 : LO • Prefix plan :
G. link Update all behaviors
LOG Sequence 24 1.5 Update all behaviors
sen • Phonebook :
t • Phonebook :
Ac k Update all behaviors
no Update all behaviors
w le
dg
me
nt
5 lupd.dat N3 file
lupd.dat N3 file
9 Node3 Node 1 :
LOG Sequence 5
n° 31000 is defined as local subscriber Node 2 :
n° 31000 is defined as local subscriber
on node 3, this one generates LOG Sequence 9
on node 3, this one generates 8
RLOG.1.5 file Node 3 :
RLOG.1.5 file
LOG.1.5 file will be erased on node 1. RLOG.1.5 LOG Sequence 24
LOG.1.5 file will be erased on node 1. RLOG.1.5
File creation
File creation

4) Node 1 sends LOG file requested to other nodes.

5) At reception, remote nodes send acknowledgment and increment their lupd.dat file.
6) Broadcast executes LOG files according to parameters configured at initialization (in this example, modifications coming from
network are taken into account)
7) MAO of node 2 inserts network prefix 31000 and related phonebook name in the database.
8) MAO of node 3 refuses modifications. Indeed, a local set already exists with the same number. A directory number can exist only
in one node, so a error file is created with concerned LOG file reference (RLOG.1.5).
9) Technician must analyze causes coming from RLOG.1.5 creation, no deletion of object will be automatically done by broadcast
application.
10) LOG.1.5 will be removed in node 1 when transfer is acknowledged for all nodes. If LOG files number has reached the maximum
value in management (20 by default, 127 maximum), this file will be removed even if it was not transferred to all the nodes.
In this case, only audit allow to retrieve modifications in databases of nodes which have not received the file.
This problem occurs only if ABC link is down for a long period. In this case, a system message (impossible LOG.N.S file transfer)
is created for each LOG file lost.

136
Broadcast
Information
Broadcast application files location
➨ Temporary files and LOG (network and area)
▼ Directory /usr4/mao
➨ Sequences counter lupd.dat
▼ Directory /usr3/mao
Broadcast activation
➨ MGR and 4760
▼ /System/Broadcast/Operational Yes
➨ Or mao +/- br command


137
Broadcast
Information
System process used
➨ /DHS3bin/servers/broadcast
Broadcast reset all over the network
➨ Cleanbroad tool
Error files screen-out
➨ prog_diff tool ( -l US0 for English)
Audit application follows broadcast configuration

➨ Broadcast area respect
➨ Objects behaviors respect in Emission/Reception

Almost part of objects are broadcasted in the network. Some objects have only a local behavior and not broadcasted, others are
partially broadcasted.
Main objects not broadcasted:
•Hardware architecture of nodes (shelves, boards, etc…)
•System parameters
•Voice guides
•IP data (compression, IP domains, etc…)
•DHCP configuration
Objects which are not completely broadcasted:

•Translator
•No broadcast of trunk group prefixes and ARS tables
•Speed dialing
•Direct speed dialing are always broadcasted, speed dialing by ranges according to the range type
•Local range: no broadcast (neither range size, nor prefixes)
•Network range: size and contents range are broadcasted

138
Broadcast
Broadcast areas
Inside a big network, broadcast all the objects can pose a

problem
➨ Needs for different speed dialing numbers, different class of

service, etc…
The use of broadcast areas can restrict the consequences

of modifications
➨ An object can be:
▼ Broadcasted in network
▼ Broadcasted in area
▼ Not broadcasted
128 broadcast areas can be used


139
Broadcast
Broadcast areas
Areas architecture
Node 1 Node 2 Node 4
ABC link ABC link
AB
Cl ABC ABC
ink
Area 1 link Area 2 link
Node 3 Node 5
ABC
link
Area 1
Node6

An area is made of adjacent nodes

Broadcast is done by contagion (each node receiving LOG files send them to his adjacent nodes).
In area broadcast case, a node in an another area non concerned by modifications will not execute the LOG file (A.Z.N.Seq) from
node source of the broadcast. Broadcast will remove this file and it won’t be transmitted to other nodes.
Area numbers are from –1 (no area) to 127 (soit 128 areas).
There is no control in management of coherency of broadcast areas !

140
Broadcast
PROCEDURE
Broadcast
OBJECTIVE
- To learn how to configure broadcast
REFERENCE
- System Documentation CD-ROM: Custom System Documentation / Technical documentation /
Private Networks / ABC-F homogeneous private network / Audit and Broadcast
OVERVIEW
The broadcast tool is used to maintain the coherence of all the elements of the network in real time.
When a management operation allocates the elements that depend on a network node, the
broadcast is responsible for transmitting the modifications required to the other nodes in order to
maintain overall coherence.
The broadcast is activated when the PCX is started up, then reactivated after certain management
commands. The range of the broadcast may be either the network as a whole or the areas defined
on management.

141
Broadcast
PROCEDURE
1. Check broadcast state

Action mao -a (under mtcl)
BROADCAST is off
MAOAGENT running process 0
MAO is on
MAO trace : off
Trace on BRODCAST is off
Synchronization 4400-47xx is on
2. Activate broadcast
2.1 First possibility: use of mao +br

Action mao +br (under mtcl)
Broadcast was inhibited -> Broadcast is activated
Action mao -a
BROADCAST is on
MAO is on
MAO trace : off
2.2 Same action using mgr

Application mgr -l US0 (under mtcl)
Path System / Broadcast
Operational + YES

142
Broadcast
2.3 Second possibility: use of cleanbroad

“cleanbroad ” tool is used to restart and reinitialize the broadcast. All the broadcast files are
deleted and the sequence numbers are reset to 0.
Activated on one node of the network, it is automatically applied to all the nodes of the
network.
Action cleanbroad -all (under mtcl)
Cleanbroad for node 1
Cleanbroad for node 2 (172.30.1.2)
Cleanbroad for node 3 (172.30.1.3)
INIT: Warning: Application "BROADCAST" will be killed
…
RESULT of the RESTART
Successful Restart broadcast on node 1
Action mao -a
BROADCAST is on
MAO is on
MAO trace : off
2.4 Check the sequences counters

Action mao -lupd (under mtcl)
broadcast pid 5125
number of nodes: 3, local_node 1, local_area -1
node 001 log seq 0 action 0 node_param: -V, dynamic_timer 0
area -1, area seq 0, step 0
X25Addr 000000000100100, pref IP/X25
IP/X25Name x001001_tun IP/X25Addr 172.30.1.1
rem all: 0
X25Addr 000000000100200, pref IP
IPName xm001002 IPAddr 10.1.2.3
rem all: 0
X25Addr 000000000100300, pref IP/X25
rem all: 0

143
Broadcast
3. Modify the broadcast parameters

Broadcast Buffer Timer-step 1mn 10
Broadcast Poll Timer-step 1mn 10
Dynamic Link Poll Timer-step 1mn 60
Maximum number of log files 20
Thres. (%log files) for dyn.links 50
Broadcast Area Number -1
Operational + YES
Update all Behaviours + NO
Note: Broadcast Buffer Timer: Enter the value of the broadcast buffer timer. The time can be
set in steps of 1min. A LOG file contains the management operations which occurred during
the time interval defined by this parameter. A management operation may only be
broadcast when this timer expires.
Broadcast Poll Timer: Enter the value of the poll period during which each node consults
the status of the lupd.dat table of the adjacent nodes.
Dynamic Link Poll: Enter the value of the poll period applied via the dynamic logical
links. In order to reduce the data flow on the dynamic links, this value must be high.
Maximum number of log files: Enter the maximum number of LOG files that will be
saved on the disk (maximum value:127).
Thres. (%log files) for dyn.links: Enter the proportion of the maximum number of files
stored on the disk from which a broadcast operation will be triggered via a dynamic link.
Broadcast Area Number: Enter the number of the area to which the node belongs. The
default value -1 signifies that the node does not belong to a particular broadcast area
(maximum value:127).
Update all Behaviors: Select Yes in order to ensure that all the objects have the same
behaviour as that defined in the next heading ("Global behavior). Select No to be able
to attribute an individual behaviours to each object. In this case, complete the outgoing and
incoming behaviour of each object that follows.
Global behaviour: Only appears if the "Update all behaviors" parameter is set to
"Yes" . The global behavior of all the objects on transmission and reception must be
defined.
Outgoing behavior: Select one of the following behaviors:
No broadcast: the management operations relating to the object will not be broadcast.
The range of management operations remains local to the node.
Broadcast in the area: the broadcast range of management operations relating to the
object will be limited to the area to which its node belongs.

144
Broadcast
Broadcast over the network: the broadcast range of management operations relating
to the object will be the whole network. Default value.
Incoming behavior
Select one of the following behaviors:
Coming from the network: management operations concerning the object, received by
broadcast, are accepted whatever the source of the broadcast file. Default value.
Only from the area: management operations concerning the object, received by
broadcast, are accepted provided that the broadcast file comes from a specified area.
Not taken into account: the object is closed to the broadcast and does not accept any
management operation that has been broadcast.
4. Object behavior
Path System / Broadcast / Broadcast objects
Action + Connection COS
Action CTRL-V
Outgoing + Broadcast over network
Incoming + Always included
Note: Outgoing : With the Update all Behaviours attribute (BROADCAST object) at NO: . For
each object, the manager can choose not to broadcast it, to broadcast it in the area (see
attribute Broadcast area number) or throughout the network. With the behavior update
attribute set to YES: . Only 'Global behavior' is taken into account: for globally all the
objects: the manager can choose not to broadcast them, to broadcast them in the area (see
attribute Broadcast area number) or throughout the network.
Note: Incoming : With the Update all Behaviours attribute (BROADCAST object) at NO: . Object
by object, the manager can choose the reception mode: not supported, from the area (see
Broadcast Area Number attribute) or from the network. With the behavior update attribute
(BROADCAST object) at YES: . Only 'Global Behaviour' (BROADCAST object) is supported:
for all the objects globally, the manager can choose the reception mode: not supported,
from the area (see Broadcast Area Number attribute) or from the network.
Note: Usually, this option is used to define a default position conform to the needs for the most
part of objects. After, for objects which need different behavior, it’s enough to modify them
individually.

145
Broadcast
5. Immediate broadcast
Path System / Broadcast / Immediate broadcast
Action CTRL-V
Note: If you don’t want to wait for the end of the Broadcast Buffer Timer, you can execute
immediate broadcast.

146
Broadcast
6. Check of the management of the broadcast: status of nodes

Action prog_diff _l US0 (under mtcl)
Broadcast management: General menu
Path 0 - Exit
1 - Edition of the error files
2 - State of nodes
3 - Edition of Broadcast history
4 - Presentation of the tool
Choice [0 - 4]:
Action 2
State of nodes
Path 1 - x001001_tun
2 - xm001002
Node to edit (0 Exit)
Choice [0 – 2]:
Action 1
x001001_tun
mao + broadcast +
Node 1: Sequence number = 1
Node 2: Sequence number = 0
x001001_tun
List of the remote ERRLOG files
No ERRLOG files on the remote node
Note: Command 2 “State of nodes" is used to find out the situation of the consulted node in
relation to the broadcast application. For each node consulted, it is possible to know
whether the broadcast is activated and to find out the last ten sequence numbers of the
broadcast files received from the other nodes.

147
Broadcast
7. Check of the management of the broadcast: LOG files edition

Action prog_diff _l US0 (under mtcl)
Broadcast management: General menu
Path 0 - Exit
1 - Edition of the error files
2 - State of nodes
3 - Edition of Broadcast history
4 - Presentation of the tool
Choice [0 - 4]:
Action 1
Escape string is : "$"
Path Hit <RETURN> to have the list of files
Which log file ?
Action LOG.1.1
Create Object [890037,Prefix Plan]
Path Node Number (reserved): 101
Instance (reserved): 1
Number: 31400
Prefix Meaning: Network No.
Domain Identifier: 0
Hit <RETURN> to continue:
Action Hit <RETURN>

Create Object [890081,Phone Book]
Node Number (reserved): 101
Directory Number
Directory Number: 31400
Alias No.: 0
Directory name: john
Directory First Name: john
Phone Book Type: Users
Can be Called/Dialed By Name: YES
Hit <RETURN> to continue:
Note: To find the name of the last LOG or RLOG files use choose choice 1. edit state of nodes.
LOG.N.Seq: N is the node number and Seq the sequence number.

148
Broadcast with areas

OBJECTIVE:
◆ To maintain Broadcast application with areas
Alcatel OmniPCX Enterprise –Broadcast with areas

149
Application status
prog_diff tool
➨ Error files edition
▼ Files are locally available for consultation for a given node
▼ Reads broadcast and broadcasted files buffer
➨ Displays the state of the network nodes
▼ State of the sequence counters
Reinitialize broadcast
➨ cleanbroad locally
➨ cleanbroad –all whole network

Using –l US0 option with prog_diff will choose language English.

This tool was at the beginning designed to configured the broadcast application, which explains its name.
It’s possible to edit a log file or the buffer by giving its name in the application as if it was an error file.
cleanbroad command give the possibility to re-init broadcast. By default it will act locally except if you add option –all
(whole network).
It stops broadcast process, erase LOG files, re-init sequence counters then starts broadcast process.
With option –all, all these actions are done on the whole network.
cleanbroad –all command has to be used in order to put into service for the first time broadcast application.

150
Files used
Files used by broadcast application
➨ /usr4/mao/cm_cb.sav & /usr4/mao/area_cm_cb.sav
▼ Broadcast (with or without areas) buffers
➨ /usr4/mao/LOG.N.S & /usr4/mao/A.Z.N.S
▼ Exchange file for node N and sequence S (in area Z)
➨ /usr4/mao/RLOG.N.S & /usr4/mao/EA.Z.N.S
▼ Errors files for node N and sequence S (in area Z)
➨ /usr3/mao/lupd.dat
▼ Sequence file

Error files RLOG are created on the node were the error occurred (incoherency, etc..).
The sequence number is the same as the one of the LOG file that produced the error.
The creation of a RLOG file comes with a system message.
Files specific to broadcast areas start with A or EA and content the area nb, node nb, and sequence nb.
Only lupd.dat file is located in the database directory.
Areas must be adjacent. In the contrary, files A.Z.N.S can’t reach all nodes in the broadcast area.

151
MAO management
Enable / disable broadcast
➨ mao +/- br command

or
➨ / System / Broadcast
▼ Operational : YES / NO
State of the sequence counter and mao
➨ mao –lupd command
➨ mao –a command
History of modifications done by broadcast

➨ Maohist command

Commands given by mao –lupd can be found easily with prog_diff.
Traces activation on broadcast : mao brv

De-activation of traces : mao brs

152
IP/X25 Tunnel
In case of problems with broadcast, check X25 application

parameters
➨ X25 / X25 Access Cluster N° 0 / X25 Access Point
▼ Access Point 108: Broadcast application
✦ Sequence counter exchange
▼ Access Point 134: Tunnel application
✦ LOG and RLOG files transfer via FTP
▼ These access points must be operational
➨ X25 / Network Nodes
▼ IP & IP/X25 addresses must be coherent
▼ Broadcast must be enabled for this node

If some access points of cluster 0 are disabled, the related applications won’t or badly work (no file transfer if tunnel is down for
instance).
In case of errors in the management, data configured in the network nodes might be wrong. So some problems might occur for
broadcast and / or audit (wrong IP address for instance, node with broadcast disabled, etc…).

153
IP/X25 Tunnel
Information coherency under suproutage (menu 7)

Description of X25 DTE for node 1
│ Position │ Type│Activ│LAP│TEI│ LCN │VCBsy│PVCBsy│SWin│SPkt│ X25 Address │

│ X25 Brdc │Appli│ 1 │ 0│194│ 1-127│ 0 │ 0 │ 4 │ 256│ │
│ Servirt │Appli│ 1 │ 0│184│ 1-127│ 0 │ 0 │ 4 │ 256│ │
│ Hybrid │Appli│ 1 │ 0│183│ 1-127│ 0 │ 0 │ 4 │ 256│ │
│ Tunnel │Appli│ 1 │ 0│134│ 1-127│ 0 │ 0 │ 4 │ 256│ │
│ Mao │Appli│ 1 │ 0│108│ 1-127│ 1 │ 0 │ 4 │ 256│ │
Number of Size of windows

Logical channel and packets
Return to menu <Q>

X25 parameters changed when OmniPCX 4400 release 3.0 came out.
If some nodes (or databases) in the network come from versions prior to R3.0 (due successive migrations), the X25 profiles will be
different from the one of an OmniPCX Enterprise.
In that case, it’s mandatory to configure the profiles used by the applications (all access points from cluster 0) on the migrated nodes
and restart the telephone on those stations.

154
Broadcast
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the broadcast application by using the procedure ENTP0436C01TEUS.
MANAGEMENT
1. Reduce the broadcast buffer timer and the broadcast poll timer to 1 minute on each node.
2. Validate the broadcast concerning all the objects (in reception and emission modes).
3. Activate the broadcast on each node.
4. Create or delete a user in one node and check that the modification has been made in all the
nodes of the network.
5. Check the sequence implementation in lupd.dat file.

155
Broadcast

156
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
157
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
158
ABC-F Trunk Groups

OBJECTIVES:
◆ To describe the principles of ABC-F Trunk Groups
◆ To describe the architecture of a ABC-F supra-network
◆ To describe the main cases of inter working in ABC
Alcatel OmniPCX Enterprise – ABC-F Trunk Groups

159
ABC-
ABC-F Trunk Groups
Overview
ABC-F Trunk Groups allow the connection of the Alcatel

OmniPCX Enterprise with:
➨ Other Alcatel OmniPCX Enterprise belonging to different

ABC networks
➨ Other Alcatel PBX:
▼ Alcatel OmniPCX 4400 / Enterprise ABC-F2 protocol
▼ Alcatel 4300 S/M ABC-F2 protocol (with restrictions)
▼ Alcatel 4300 L ABC-F1 protocol
▼ Alcatel 4600 ABC-F1 protocol
These trunk groups use interfaces like T0 / T1 / T2

The ABC-F protocol is a proprietary protocol based on an evolution of the ISDN protocol.
Different types of protocols based on ISDN are:
•Basic ISDN
•QSIG-BC (Q point Signaling – Basic Call)
•QSIG-GF (Q point Signaling – Generic Features)
•QSIG-SS (Q point Signaling – Supplementary Services)
•Protocol giving possibilities to use proprietary messages above the GF layer (ABC-F uses QSIG-SS)
•ABC-F1 (Alcatel Business Communication – intermediate feature level)
•Allow more evolved services than QSIG-GF but not the complete possibilities of ABC
•Used with old Alcatel PABX like 4300 or 4600
•ABC-F2 (Alcatel Business Communication – maximum feature level)
•According to the adjacent PABX, the level of feature can change
•ABC-F2 (300): reduced compatibilities with Alcatel 4300 S/M
•ABC-F2: maximum compatibilities with Alcatel OmniPCX 4400 or Enterprise
Use the system documentation to see the list of available features of ABC protocol

160
ABC-
ABC-F Trunk Groups
Overview
An ABC-F Trunk Groups is a private ISDN trunk group

➨ The protocol used is directly depending on the adjacent
network number related to the call
Inter-sites calls are done by:

➨ Trunk group prefix and remote set number
➨ Routing prefix
Voice compression can be used

➨ Compressed trunk groups on LIOx boards (Crystal
Hardware)(1)
An ABC-F trunk group can transit via a PABX that handles

QSIG-GF protocol

(1) : Compression on LIO boards is no more available on new installations. This type of configuration concerns only migration cases.

161
ABC-
ABC-F Trunk Groups
Topologies
Network of homogeneous OmniPCX Enterprise networks
Alcatel OmniPCX Sub-network 0

Enterprise Alcatel OmniPCX
Enterprise
Call Server
Call Server
N1 ABC-F Trunk Groups

N2 Trunk
group 1 on T0 / T1 / T2
N3
Alcatel OmniPCX
Enterprise
Sub-network 1
Alcatel OmniPCX
Enterprise
Call Server
Call Server
Trunk N1 N2
group 10
N3

Alcatel OmniPCX Enterprise homogeneous networks can be connected to form a network of homogeneous sub-networks. The
networks are interconnected via ABC_F trunk groups. The maximum size in a network is 100 nodes.
According to the network topology, the number of nodes or sites, the geographical localization... It may be interesting to merge
different homogeneous networks. In that case we talk of “Network of networks” or Supra-Network.
The network of sub-networks advantageously replaces a homogeneous network that is too large and in which routing tables updates
are too slow and therefore inoperative.
A supra-network interconnects ABC-F sub networks with ABC-F trunk groups.

The level of services available between sub-networks is ABC-F2 (Alcatel OmniPCX Enterprise).
In this type of configuration, the dialing is done by network routing prefix.

162
ABC-
ABC-F Trunk Groups
Topologies
Heterogeneous ABC-F Network (Alcatel PBX)

Alcatel OmniPCX
Enterprise
Call Server
4400
Sub-network 0
Alcatel OmniPCX
Enterprise
Alcatel OmniPCX
Enterprise
ABC-F2
Call Server
Call Server
N1 N2
ABC-F2
4300
M
N3
ABC-F1
4600
ABC-F1
4300 L

A heterogeneous ABC-F network is composed of OmniPCX Enterprises and/or OmniPCX 4400s linked by private links to other
PBXs (4300 L, 4300 S/M, 4600, etc.) with ABC-F network protocol. Heterogeneous nodes are linked by trunk groups.
According to the adjacent PBX, the level of feature can be more or less high.

163
ABC-
ABC-F Trunk Groups
Topologies
ABC-F protocol in transit on heterogeneous network
Alcatel OmniPCX
Enterprise
Alcatel OmniPCX
Enterprise
Call Server
Call Server
ABC-F2
QSIG-GF QSIG-GF
PBX

The OmniPCX Enterprise are not directly connected together but trough QSIG-GF links.
The ABC-F2 protocol can transit using the QSIG-GF links.
The QSIG protocol allow transparency: transparent transport of signaling between two nodes via a QSIG transit PBX. The signaling
thus exchanged allows, for example, two Alcatel ends to offer ABC-F network services (conference, etc.) via a non-Alcatel transit PBX.

164
ABC-F Trunk groups
PROCEDURE
ABC-F Trunk groups
OBJECTIVE
- To learn how to manage a ABC-F2 Trunk group
REFERENCE
Private Networks / ABC-F homogeneous private network / Network of enterprise sub-networks /
OVERVIEW
A ABC-F2 trunk group allow to connect sub-networks.
This procedure gives the management details to connect node 1 of sub-network 1 (numbering plan:
31XXX) to node 2 of sub-network 2 (numbering plan: 32XXX) using a private T2 on a PRA board
(slot 1-2).

165
ABC-F Trunk groups
PROCEDURE
1. Create the ABC-F2 trunk groups
1.1 Trunk groups creation

Application mgr
Path Trunk groups
Action Create
On node 1 On node 2
Trunk Group ID 16 26
Trunk Group Type T2 T2
Trunk Group Name ABC-F T2 ABC-F T2
Action Ctrl-V
Node number 1 2
Q931 Signal variant ABC-F ABC-F
Number Of Digits To 5 5
Send
Action Ctrl-V
Note: The number of digits to be send is related to the remote numbering plan, here 5 digits.
1.2 Trunk group local parameters

Application mgr
Path Trunk Groups / Trunk Group
Action Review/Modify
On node 1 On node 2
B Channel choice YES NO
Action Ctrl-V
validated).

166
ABC-F Trunk groups
1.3 Creation of the trunks

Application mgr
Path Trunk Groups / Trunk Group / T0/T1/T2 Access
Action Create
On node 1 On node 2
Physical Address 1-2-0 1-2-0
Access Type T2 T2
Action Ctrl-V
1.4 Management of the digital accesses

Application mgr
On node 1 On node 2
Network Mode YES NO
Synchronization priority 255 230
Action Ctrl-V
Note: Choose the previously managed access (Shelf1, Board 2, Access 0). One end is in network
mode (node 1 for example), and the other in user mode. The synchronization priority on the
node 2 in this example is according to the type of T2 board used. In crystal hardware,
priority can vary between 0 and 199 (0 is for public T2) ; in media gateway, priorities vary
between 200 and 254 (200 is for public T2).

167
ABC-F Trunk groups
1.5 Creation of the routing prefixes

Application mgr
Path Translator / Prefix Plan
Action Create
On node 1 On node 2
Number 32 31
Prefix Meaning Routing No Routing No
Action Ctrl-V
Network Number 2 1
ABC-F Trunk Group 16 26
Number of Digits 5 5
Action Ctrl-V
Note: It’s also possible to create “network” prefixes with the node number and network number
Note: The dialled incoming and outgoing numbering can be modified in the system with the object
Translator / Network routing table. For each sub-network, the rank of the first digit to be
sent can be given (deletion of the N first digits) and the incoming identification prefix
(dialing sequence that will be inserted in the header of numbers received in order to adapt
to local dialing).

168
ABC-F Trunk Groups
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage a network of sub-networks
MANAGEMENT
1 Topology
Network 1 Network 2
Node 1 Node 2 Node 3 Node 4 Node 5 Node 6
ABC links ABC ABC links

Trunk Group
2 Manage the ABC_F trunk group between node 3 and node 4

- This trunk group has a 5 digits numbering
- Node 3 access is declared in network mode and node 4 access in user mode
- The ABC_F trunk group is managed on T0, T1 or T2 equipment
- Manage the trunk groups with the parameter “ Supervised by routing = yes ”
- Network 1 trunk group number = 36
- Network 2 trunk group number = 46
- Network 1 seizure trunk group prefix = #36 (trk group 36)
- Network 2 seizure trunk group prefix = #46 (trk group 46)
3 Check that the broadcast application has created trunk groups in remote nodes inside the
same network.

169
ABC-F Trunk Groups
4 Test the ABC_F trunk group
5 Manage on each node the routing prefixes for the remote network sets.
6 Check that each set can call the other sets

170
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
171
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
172
Hybrid links

OBJECTIVES:
◆ To describe hybrid link principles
◆ To describe different hybrid link types
◆ To describe signaling backup
Alcatel OmniPCX Enterprise – Hybrid links

173
Hybrid links
Terminology
ABC link
➨ Directional link between two nodes of a ABC-F network
➨ An ABC link must be managed in a symmetric way on both
sides
Access
➨ Physical link type carrying signaling
Trunk
➨ Physical link type carrying voice or data

A permanent T1/T2 ABC link contains:

• link between node 1 and node for instance (an another exists between node 2 and node 1)
• one or several T1/T2 accesses carrying D channel on T2
• trunks corresponding to B channels of each access

174
Hybrid links
Overview
An hybrid link is an ABC-F2 link that uses one physical link

for signaling and another one for the voice channels
➨ Voice / data
▼ B channels on ISDN link, TS on PCM

▼ Compressed B channel on ISDN links (internal compression)
▼ Analog lines on EMTL, ACEM
➨ Signaling channel (D channel)
✦ LAPD on IO2 or OBCA (B channel) Only Crystal
✦ X25 virtual circuit (PLL in D or B channel) Only Crystal
✦ Compressed link (virtual access) Only Crystal
✦ IP network Any kind of hardware

Hybrid link is a complement of links usually built on T0/T2 accesses.

Its main feature is to separate the signaling from the circuit resources (they are not necessary on the same board).
Each circuit channel is not dependent to each other and can be defined on different support types.
The signaling channels are able to support ABF_F protocol and also routing messages.
They are mainly classified into 2 classes :
- LAP D (HDLC procedure)
- X25 virtual circuit (B ch., PLL ...)
This signaling channel is permanently established.
The association between the signaling channel and the circuit channel is logically done (reminder that in case of normal ABC link
both are physical coordinates).
VPN overflow can also be used for B channels transport.

175
Hybrid links
Different types
Permanent hybrid links

▼ Used on leased lines
▼ Several accesses possible in the same hybrid link
▼ Possibility to secure the signaling channel
On-demand links
▼ Used on public or private ISDN lines
▼ Multi-accesses configuration possible
▼ No possibility to secure the signaling channel

Multi-accesses configuration:
Multi access hybrid link to YES:
•Allows to create several accesses (24 possible accesses with 30 B channels maximum per access) in one ABC link.
•Allows to create signaling backup ( 2 accesses are used on for the main link and one for the stand bye link)
•Allows to avoid to reserve a specific DDI number for ABC link on demand (use of a specific sub-address)
Multi access hybrid link to NO:

•Only one access in the link (30 B channels maximum)
•No signaling backup
•For an ABC link on demand, a dedicated DDI number must be used
Multi access should always be used. It’s incompatible with mono access mode (used before R3.0 release of OmniPCX Enterprise
Ux).
In multi access on demand ABC link, ISDN network used must transport the ISDN sub-address.

176
Hybrid links
Signaling link
B channel signaling
➨ B channel on synchronous leased line
➨ ISDN B channel switched on T0 / T2
➨ Leased B channel on T2 / T1 / PCM

Only
X25 Packet mode signaling Crystal
Hardware
➨ Permanent logical link
▼ in D channel on T0 / T2
▼ in B channel on T0 / T2
Compressed signaling on LIO board

These types of signaling can only be used with Crystal Hardware (use IO2 or OBCA)
Leased B channel on synchronous link:

The link is connected through second generation terminal adapter TA 4083 SYV
Switched B channel on T0/T1/T2 :

The link is connected using a 64 Kbytes/s channel of an ISDN access. The switched network used must allow the transparency of the
ISDN sub-address (ISDN or QSIG network).
Compressed signaling:
With crystal hardware compression function can be used with LIOX, LIOB and LIOP boards. In this case, virtual access is used,
because signaling channel will use a channel multiplexed with voice in a support TS (6 or 8 B channels and on D channel in one
support TS at 64 kb/s)

177
Hybrid links
Signaling link
IP signaling
➨ LAN connection between nodes
D channel signaling
➨ D channel on leased T1 or T2
➨ Possibility to use standby signaling
➨ Without signaling access
▼ Number of B channels can be increased without adding an other

signaling media
▼ Signaling is derived by an other access

These types of signaling can be used with Crystal Hardware or common hardware
IP signaling:
One of the most used. Signaling is carried on customer LAN
D channel type signaling:

Allows to switch from a permanent ABC link to an hybrid link, the advantage is to profit from signaling backup functionalities
available with hybrid link.
It’s also possible to increase the number of accesses (16 with a permanent T1/T2 ABC link and 24 for hybrid link).
access without signaling:

The limit of B channels is fixed to 30 at the management for one hybrid access.
But one D channel can support up to 60 communications.
•Example:
•2 hybrid link accesses
•access N°1:
signaling: D channel
trunks: B channels of T2/T1 link
•access N°2:
signaling: without signaling
sig. provider access number for main: 1
trunks: analog link on ATL

178
Hybrid links
Phone facilities
Hybrid links features level is the same as permanent ABC

link
➨ ABC routing process
➨ ABC-F2 level
▼ Telephone facilities
▼ ARS management
▼ Virtual Private Network (VPN)
▼ Distributed trunk groups
▼ IP/X25 tunneling
✦ Consistency, Broadcast, Centralized voice mail and management, etc …


179
Hybrid links
Configuration examples
Hybrid link on leased B channel on PCM

N1-N2 ABC link Call Server
Call Server
N2
N1
D1
B1 B2
B2 B1
D1
B1
B2
D2
MUX
N1 B1
-N Alcatel OmniPCX Enterprise
2A B2
BC D2
lin
k Call Server
Optimization of a 2Mb/s N3
link
the same link to 2 directions

Node 1 uses 2 hybrid links toward node 2 and 3. Leased B channel support is used.
It’s the multiplexer (external hardware) which mix TS between the 3 links, that allows to route TS from the PCM used on node 1 to
other nodes.
In this example, configuration could be:
N1-N2 ABC link: 2 B channels (B1 and B2) and D channel D1 using TS 1, 2 ,and 3 of the link toward the Multiplexer.
Mix of TS:
TS 1, 2 ,and 3 of N1 link routed to TS 1, 2 ,and 3 of N2 link
TS 4, 5 ,and 6 of N1 link routed to TS 1, 2 ,and 3 of N3 link
This way, the link coming from N1 to the multiplexer allows to create several ABC links.
In permanent ABC F link on T1/T2, as many accesses should be required as directions out of N1.

180
Hybrid links
Hybrid link on B channel on synchronous link
Alcatel OmniPCX Enterprise Alcatel OmniPCX Enterprise
N1-N2 ABC link

Call Server
Call Server
B1 B2 B3 B4
N1 N2
TA TA
T2 D T2
D’
B B
Carrier
Main signaling (D) Backup signaling (D’)

on synchronous link on ISDN switched B channel
B channel on a 2Mb/s
link or automatic tie line

Hybrid links between node 1 and 2 is B channel type on Leased B channel support
Main signaling is provided by a synchronous link at 64 kb/s (point to point leased line with synchronous modem, digital line with
multiplexer and digital output for instance), connected to 2 TA 4083SYV.
A signaling backup is envisaged via public network (use of a public B channel to establish a call if required (synchronous link failure)).
Main signaling is permanent, backup signaling is on demand.
Everything forms only one ABC link with one access managed with stand bye.

181
Hybrid links
Hybrid link on switched B channel
N1-N2 ABC link

Call Server
Call Server
N1 N2
T2 T2
D
B B
B
B B
Carrier
Main signaling (D) B channels are provided

on ISDN switched B channel by the VPN overflow

Hybrid links between node 1 and 2 is B channel type on switched B channel support
This kind of ABC link is for end nodes with low traffic (static routing mandatory).
Link is up as soon as a call is established. A B channel is used on the ISDN link which connects 2 nodes to the carrier. The network
used must allow the transparency of the ISDN sub-address.
At this moment, the ABS link is in service but doesn’t provide B channels, the link is saturated.
VPN overflow on busy link allows to establish a private call via the public network.
D channel is established as long as the communication is not released. If a second call uses the ABC link, an other VPN overflow will
be used, the signaling for calls will use the switched D channel.
To optimize number of B channels on public links, it’s possible to use compression with LIO boards (up to 8 simultaneous calls on the
same TS at 64 kb/s).

182
Hybrid links
Hybrid link on IP link

Call Server
N1-N2 ABC link Call Server
B1 B2 B3 B4
N1 N2
B channels on 2Mb/s link

T2 or ATL link T2
D’
B B
Carrier

on IP link on ISDN switched B channel
D LAN

Hybrid links between node 1 and 2 is IP type
B channels can be on a 2 Mb/s link or analog ATL link. It’s possible not to use B channels, in this case the link is permanently
saturated and a VPN overflow will be used to establish calls.
Signaling link is always up on the customer LAN.
It’s possible to backup this link with a leased or switched line.
If the main is on IP the backup cannot be on IP.
(same support, same physical access no real backup).
In VoIP environment, it’s possible to use IP trunk group which use the LAN to route calls. Using VPN overflow on
this trunk group, the communications cost will be reduced to minimum.

183
Hybrid links
Hybrid link on D channel of T1/T2 link
N1-N2 ABC link

B1 B2 D B3 B4
N1 N2
B
B channels
channels on
onT2
T1/T2
link
T2 (VPN overflow in backup) T2
B
B B
Carrier

on T2 link on IP link
D’ LAN

Hybrid links between node 1 and 2 is D channel type
Main signaling is transmitted on D channel of the T1/T2 link.

Because the hybrid link is a multi access hybrid link, it’s possible to add a backup access (main interest of this kind of configuration).
Backup signaling uses IP customer network (permanent backup).
If main signaling is down, B channels are lost also (same physical link). In this case, backup allows to keep ABC link functions but the
link is saturated.
A VPN overflow is required to route inter-nodes calls in case of private ISDN link breakdown.

184
Hybrid links
Hybrid link without signaling access
N1-N2 ABC link

B1 B2 DD B3 B4
N1 B1
N2
B2
B3
Access 1
Access 2
Access
Access
1 on
1 on
T2T2
support
link
Access 2 on analog ATL
Main signaling (D) Access 2 signaling in

on T2 link access 1 signaling

Hybrid links between node 1 and 2 is D channel type
Main signaling is transmitted on D channel of the T1/T2 link.

To reuse the 3 ATL analog lines between the 2 nodes, normally a second access must be created.
To avoid this, the second access can de declared without signaling and define access 1 as signaling provider.
D channel of ISDN link will provide signaling for both accesses.
If first access is down, B channels of second access are lost also. It’s possible to declare a backup for first access, in this case the
second access will be automatically backing up.
Everything forms only one ABC link with 2 accesses.

185
Hybrid links
Backup signaling on two accesses
N1-N2 ABC link

B1 B2 B3 B4
N1 N2
B1 B2 B3
T2 TA TA T2
D1
B D1’
B
B D2’
B
Carrier
Access 1 B channel signaling Access 2 IP signaling with

with switched B channel backup switched B channel backup
D2 LAN

Hybrid links multi access with backup

Each access has his own signaling: the signaling of B channels of the first access go through D channel of this access, the one of the
second access go through the D channel of the second access.
In case of signaling breakdown, the stand bye takes the relay in this example.
If signaling B channels are out of service (main + backup), B channels of this access are lost.
In case of access breakdown (no signaling support), X25 routing switches automatically to the other access available. ABC functions
are still available, but current communications on the access are lost.
Everything forms only one ABC link with 2 accesses with backup.

186
Hybrid links
Remarks
Backup establishment mode management
➨ Leased type backup link
▼ Backup must be declared in permanent mode
➨ Switched type backup link
▼ Backup must not be declared in permanent mode
Case of multi accesses behavior
➨ X25 routing uses indifferently one of the accesses
▼ If one access disappears, it switch automatically to the second one
➨ Current communications on one access which fails will be

lost


187
Hybrid links
B channel state control
B channel access lost is not detected like a permanent

T0/T1/T2 permanent ABC link
➨ T0/T1/T2 permanent ABC link: if D channel is lost, all B
channels are lost
➨ Hybrid link: two links are independent
The B channels state of an analog ATL link is supervised

regularly by audio test on both ends
➨ Frequency send on a B channel of an access
➨ Test request on this B channel to the other node
➨ If no frequency detected B channel is put out of service

In case of hybrid link, B channels can be on digital or analog medias.

The state of a digital access is related to the level 2 linked to this access, but it’s not possible with an analog link.
The audio test of B channels handled by ATL lines is done by using Q23X detectors on node receiving the frequency.
If the node doesn’t detect this frequency, the trunk is out of service.
Q23X resources must be available for the node (available on GPA, GPA2, SUVG or GD/GA boards).
If no Q23X resources are available, supervision must be blocked to avoid all ABC link (however operational) B channels to be OOS.
This parameter is in : System/ Other system param. / Stop IA Supervision (Yes / No)

188
Hybrid link with signaling on IP with signaling backup on ISDN
PROCEDURE
Hybrid link with signaling on IP with
signaling backup on ISDN
OBJECTIVE
- To learn how to create a hybrid logical link with signaling on IP with signaling backup on ISDN
switched B channel (on demand)
REFERENCE
Private Networks / ABC-F homogeneous private network / Hybrid logical links / Configuring IP
signaling
OVERVIEW
- The signaling support is an Ethernet network using the Internet protocol (IP) with signaling
backup on ISDN switched B channel (on demand). The OmniPCX Enterprise can be connected to
an Ethernet network.
- IP addressing must be well managed previously (main addresses on both CPU, coherent IP
tunnel addresses).
- In this example, nodes 1 and 2 belong to ABC network 1, IP addressing is default with role
addressing.
- Each node uses a T2/T1 (TG seize: #012, # 022) and installation number is 020143N000
(N=Node N°).
- A PCM link is used for B channels (slot 0-9), 2 channels will be used (one per access).
Note: This configuration uses only Crystal hardware (CPU5, 6 and 7)

189
PROCEDURE
1. Program the node number

Application mgr
Path system
On node 1 On node 2
Node number 1 2
Network number 1 1
Number Of Transit PCX Number of nodes in the Number of nodes in the
network network
Action CTRL-V
2. Declare Optimized B Channels Access for each CPU crystal
2.1 First case: OBCA daughterboard on CPU5 and CPU6

Application mgr
Path Shelf / Board
Shelf Address 0
Board Address 6
CPU w/ Optimized B + Yes
Channel Access
Action CTRL-V
Note: Use the uhwconf command to check the presence of OBCA. Don’t forget to reboot the Call
Server to taken into account these values. Use incvisu –s obca (downloading end message
shows that the board is taken into account by the system). Use one OBCA per CPU in case
of duplication

190
2.1.1 Second case: IO2 / IO2N board for CPU5 and CPU7
Application mgr
Path Shelf / Board
Action Create
Shelf Address 0
Board Address 7
Interface Type + IO2 or + IO2N
Action CTRL-V
Remote Shelf Address 0
Remote Board Address 6
Action CTRL-V
Note: Remote shelf and board address: associated with a CPU board in the same ACT shelf. Stop
the CPU5 and connect IO2 and CPU with ATB2 connector on the front side. Use one IO2
per CPU in case of duplication
3. Create the hybrid link

Application mgr
Action Create
On node 1 On node 2
Link Name H12 H21
Link Type + Hybrid + Hybrid
Adjacent Node 2 1
Action CTRL-V
Multi access hybrid link + YES + YES
Action CTRL-V

191
4. Create the hybrid link access

Application mgr
Path Inter-nodes link / Logical links (ABC-F) / Hybrid Link
Access
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
Signaling type + IP + IP
Has StandBy Signaling + True + True
StandBy Signaling Type + B channel + B channel
Action CTRL-V
Called Number or Main CPUa IP addr 10.1.2.3 10.1.1.3
Main CPUb IP address
StandBy Called Number #0120214032000 #0220214031000
StandBy Signal Always Established + False (on demand) + False (on demand)
Action CTRL-V
Note: Called Number or Main CPUa IP address: The other node IP address (it must be the
main CPU IP address (address by role) in case of duplicated system)
Note: Main CPUb IP address: For hybrid links, and in particular for declaring an access for
which the signaling support is IP, when spatial redundancy mode is used for the IP
addressing of the node of the adjacent link concerned, this attribute is used to give the IP-
MAIN address of the second CPU.
Note: Stand By Called Number: LAPD on ISDN B channel commutated via the public network:
Trunk group prefix + DDI No. Use “professional trunk group seize” prefix and not the prefix
seize with overlapping.
Note: Stand By Signal Always Established : in this case, signaling is switched type, backup
is not always up.

192
5. Create trunks
Path Inter-nodes link / Logical links (ABC-F) / Hybrid Link Access / Hybrid
Link trunk
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
Physical Address 0-9-1-0 0-9-1-0
TS number 1 1
Data Transparency + True + True
Trunk COS 18 18
Real Trunk COS 18 18
Action CTRL-V
Note: Physical Address: This address must correspond to the same voice channel on both
nodes. Physical address is expressed in the format:
Digital support (T0, T1, T2): “Shelf number”—”Board number”—”Physical access
number”—”TS number”.
PCM support: “Shelf number”—”Board number”—”TS number”—”not significant
number”.
Analog support: “Shelf number”—”Board number”—”Physical access number”.
Data Transparency: True: for digital supports.
False: for analogue supports.
Note: Trunk COS ID: 18 for PCM, T2, T1, T0 trunk groups.
Note: Real Trunk COS ID: This attribute applies to analogue trunks only. It is he number of the
real COS. It will be used instead of trunk COS (the preceding attribute) after reset.
0 for NDDI (LS, GS).
4 for DDI.
7 for LIA (2 wires) trunk groups (EMTL, ACEM).
Note: TS number must be coherent on each node. Don’t make the confusion between TS number
and Trunk number used to carry the voice. In the first case, the TS are a logical view of the
trunks of the hybrid access, in the second one trunks depend on the link used for voice and
can have different number than the TS related to the access.

193

Action 2
Local Node: 1
1 2

Example of display when the link is up :

Local Node: 1
1 S 2


194
Hybrid link with D channel signaling with IP backup
PROCEDURE
Hybrid link with D channel
signaling with IP backup
OBJECTIVE
- To learn how to create a Hybrid link with D channel signaling with backup on IP
REFERENCE
Private Networks / ABC-F homogeneous private network / Hybrid logical links / Configuring D
channel signaling
OVERVIEW
- The signaling support is an private ISDN link (T1/T2) in slot 0-5-0 with signaling backup on IP.
The OmniPCX Enterprise can be connected to an Ethernet network.
tunnel addresses).
addressing.

195
PROCEDURE
1. Program the node number

Application mgr
Path system
On node 1 On node 2
Node number 1 2
Network number 1 1
network network
Action CTRL-V

Application mgr
Action Create
On node 1 On node 2
Link Name H12 H21
Adjacent Node 2 1
Action CTRL-V
Action CTRL-V

196
3.1 On node 1
Application mgr
Access
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
Signaling type + D channel + D channel
StandBy Signaling Type + IP + IP
Action CTRL-V
Main Trunk Group ID 100 200
Phys Access for Main Trunk Group 0-5-0 (T2/T1 access) 0-5-0 (T2/T1 access)
StandBy Called Number 10.1.2.3 10.1.1.3
StandBy Signal Always Established + True + True
Action CTRL-V
Note: Main Trunk Group ID: The hybrid trunk group accesses with channel D type signaling
must be associated with a trunk group. If it is not declared manually by the manager, it will
be created automatically. Phys Access for Main Trunk Group : Physical address to be
declared for the hybrid trunk group accesses with D channel or compressed type signaling.
StandBy Called Number: Remote CPU IP address. StandBy Signal Always
Established : YES: in case of IP backup, the standby signaling is established permanently.

197
4. Create trunks
Link trunk
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
TS number 1 1
Trunk COS 18 18
Action CTRL-V
PCM support: “Shelf number”—”Board number”—”TS number”—” number”.
Note: Data Transparency: True: for digital supports.

Note: Real Trunk COS ID: 18 for PCM, T2, T1, T0 trunk groups.

198

Action 2
Local Node: 1
1 2


Local Node: 1
1 S 2


199

200
Hybrid link with B channel signaling with switched B channel backup
PROCEDURE
Hybrid link with B channel signaling with
switched B channel backup
OBJECTIVE
- To learn how to create a Hybrid logical link with B channel signaling with signaling backup on
ISDN switched B channel (on demand)
REFERENCE
Private Networks / ABC-F homogeneous private network / Hybrid logical links / Configuring
synchronous modem signaling
OVERVIEW
- The signaling support is on B channel on synchronous link with signaling backup on ISDN
switched B channel (on demand).
- To simulate the leased line a crossed V24 link will be used
- A PCM link is used for voice (slot 0-9), 2 channels will be used (1 per access).

201
PROCEDURE
1. Program the nodes number

Application mgr
Path system
On node 1 On node 2
Node number 1 2
Network number 1 1
network network
Action CTRL-V

202

Application mgr Tab
Path Shelf / Board
Shelf Address 0
Board Address 6
Channel Access
Action CTRL-V
of duplication
2.2 Second case: IO2 / IO2N board for CPU5, CPU6 and CPU7
Application mgr Tab
Path Shelf / Board
Action Create
Shelf Address 0
Board Address 7
Action CTRL-V
Action CTRL-V

203

Application mgr
Action Create
On node 1 On node 2
Link Name H12 H21
Adjacent Node 2 1
Action CTRL-V
Action CTRL-V

204
4. Create the TA adapters
4.1 V24 adapter creation

Application mgr Tab
Path Shelf / Board / TA adapter
Action Create
On node 1 On node 2
Shelf Address 0 0
Board Address 3 3
Equipment Address 5 5
V24 Adapter + True + True
Action CTRL-V
4.2 TA Creation
Application mgr Tab
Path DATA / Data terminal
Action Create
On node 1 On node 2
Directory Number 31888 32888
Shelf Address 0 0
Board Address 3 3
Specialization + Hybrid + Hybrid
Action CTRL-V

205
4.3 On node 2
Application mgr Tab
Directory Number 32888
Action CTRL-V
Flow Control ID 14
Action CTRL-V
Note: Because during the hands on the connection between the TA adapters is done directly with
a crossed V24 cable. The adjacent TA must give the clock so the default flow control must
be modified with 14 instead 15 (default value).

Application mgr
Access
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
Signaling type + B channel + B channel
Action CTRL-V
Called Number 31888 32888
Action CTRL-V
Note: Called number: for analog line: TA directory No.
Stand By Called Number: LAPD on ISDN B channel commutated via the public network:
seize with overlapping. . Stand By Signal Always Established : in this case, signaling
is switched type, backup is not always up.

206
6. Create trunks
Link trunk
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
TS number 1 1
Trunk COS 18 18
Action CTRL-V
number”.
4 for DDI.

207

Action 2
Local Node: 1
1 2


Local Node: 1
1 S 2


208
Hybrid link switched B channel type (on request)
PROCEDURE
OBJECTIVE
- To learn how to create a Hybrid logical links switched B channel signaling type (on request)
REFERENCE
- System Documentation CD-ROM: R6.1 Custom System Documentation / Technical
documentation / Private Networks / ABC-F homogeneous private network / Hybrid logical links /
Configuring switched T1-T2 B channel signaling
OVERVIEW
Hybrid link between node 1 and 2 is switched B channel type (on request). This type of link
is for an end node with low traffic (static routing).
- An access with switched B channel signaling on a T2 or T1 link is a hybrid logical link that uses a
switched B channel to transport signaling. This type of support is usually charged by call
duration.
- The logical link is set up (established) on request. Communication (signaling support) is set up
when the first call request is made on this logical link. Subsequent calls use the same signaling
channel. When the last call has been made, the support is suppressed. This operating mode is
recommended when duration charging is used for the support.
- The following procedure deal only with the D channel signaling set up. The management of B
channels (VPN overflow) is not shown in this procedure.

209
PROCEDURE

Application mgr
Path system
On node 1 On node 2
Node number 1 2
Network number 1 1
network network
Action CTRL-V

210

Application mgr
Path Shelf / Board
Shelf Address 0
Board Address 6
Channel Access
Action CTRL-V
of duplication
2.2 Second case: IO2 / IO2N board for CPU5, CPU6 and CPU7
Application mgr
Path Shelf / Board
Action Create
Shelf Address 0
Board Address 7
Action CTRL-V
Action CTRL-V

211
3. Create the hybrid links

Application mgr
Action Create
On node 1 On node 2
Link Name H12 H21
Adjacent Node 2 1
Signal Establis.Mode + On request + On request
Routing Type + Static Routing + Static Routing
Action CTRL-V
Action CTRL-V
Note: Signal Establishment mode : On request (for dynamic signaling): For each network
call, if the signal channel has not been established, a forwarding signal request asking for it
to be re-established is sent. Routing Type : Static routing: no broadcasting of routing
messages on this link, and routing carried out using the static routing table. Restriction: a
dynamic signaling link necessarily has static routing type (unlike a non dynamic signaling
link which can have static or dynamic routing type).

212
4. Create the hybrid link accesses

Application mgr
Access
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
Action CTRL-V
Called Number #0120214032000 #0220214031000
Action CTRL-V
Note: Called number: LAPD on ISDN B channel commutated via the public network :Trunk
group prefix + DDI No. Use “professional trunk group seize” prefix and not the prefix seize
with overlapping.

213

Action 2
Local Node: 1
1 2


Local Node: 1
1 S 2


214
Hybrid link with access without signaling
PROCEDURE
OBJECTIVE
- To learn how to create a Hybrid logical link with an access without signaling
REFERENCE
Private Networks / ABC-F homogeneous private network / Hybrid logical links / Configuring
access without signaling
OVERVIEW
- First signaling is on IP, the second one is without signaling.
- Access without signaling is an access that uses another one. This feature allows to declare an
access that provides supplementary B channels.
- On access can handle signaling for 60 B channels (his access and a second one without
signaling).
tunnel addresses).
addressing.
- A PCM link is used for B channels (slot 0-9), 2 channels will be used (one per access).

215
PROCEDURE

Application mgr
Path system
On node 1 On node 2
Node number 1 2
Network number 1 1
network network
Action CTRL-V

Application mgr
Action Create
On node 1 On node 2
Link Name H12 H21
Adjacent Node 2 1
Signal Establis.Mode + Permanent user + Permanent user
Action CTRL-V
Action CTRL-V

216
3. Create the first hybrid link access

Application mgr
Access
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
Has StandBy Signaling + False + False
Action CTRL-V
Action CTRL-V
Note: Called Number or Main CPUa IP address: The other node IP address (it must be the main
CPU IP address (address by role) in case of duplicated system)
Note: Main CPUb IP address: IP-MAIN address of the second CPU in case of spatial redundancy.
3.1 Create the second hybrid link access

Application mgr
Access
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 2 2
Signaling type Without signaling Without signaling
Has StandBy Signaling + False + False
Action CTRL-V
Sig Provider Access No. for Main 1 1
Action CTRL-V
Note: Sig Provider Access Number for Main: Access number which provides the signaling

217
4. Create trunks
4.1 On access 1
Link trunk
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
TS number 1 1
Trunk COS 18 18
Action CTRL-V
number”.
4 for DDI.
Note: TS number must be coherent on each node. Don’t make the confusion between TS number and
Trunk number used to carry the voice. In the first case, the TS are a logical view of the

218
4.2 On access 2
Link trunk
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 2 2
TS number 1 1
Trunk COS 18 18
Action CTRL-V

219


Action 2

Local Node: 1
1 2


Local Node: 1
1 S 2


220
Hybrid link with two accesses
PROCEDURE
OBJECTIVE
- To learn how to create a Hybrid link with two accesses
REFERENCE
Private Networks / ABC-F homogeneous private network / Hybrid logical links / Configuration
procedure
OVERVIEW
- Hybrid link with two accesses.
- The signaling support of the first access is on B channel on synchronous link with signaling
backup on ISDN switched B channel (on demand).
- To simulate the leased line a crossed V24 link will be used
- The signaling support of the second access is over IP with signaling backup on ISDN switched B
channel (on demand).
- A PCM link is used for voice (slot 0-9), 2 channels will be used (1 per access).
tunnel addresses).
addressing.

221
PROCEDURE

Application mgr
Path system
On node 1 On node 2
Node number 1 2
Network number 1 1
network network
Action CTRL-V

222

Application mgr Tab
Path Shelf / Board
Shelf Address 0
Board Address 6
Channel Access
Action CTRL-V
of duplication
2.1.1 Second case: IO2 / IO2N board for CPU5, CPU6 and CPU7
Application mgr Tab
Path Shelf / Board
Action Create
Shelf Address 0
Board Address 7
Action CTRL-V
Action CTRL-V

223
3. Create the TA adapter
3.1 V24 adapter creation

Application mgr
Path Shelf / Board / TA adapter
Action Create
On node 1 On node 2
Shelf Address 0 0
Board Address 3 3
V24 Adapter + True + True
Action CTRL-V
3.2 TA Creation
Application mgr
Action Create
On node 1 On node 2
Directory Number 31888 32888
Shelf Address 0 0
Board Address 3 3
Specialization + Hybrid + Hybrid
Action CTRL-V

224
3.3 On node 2
Application mgr
Directory Number 32888
Action CTRL-V
Flow Control ID 14
Action CTRL-V
Note: Because during the hands on the connection between the TA adapters is done directly with
a crossed V24 cable. The adjacent TA must give the clock so the default flow control must
be modified with 14 instead 15 (default value).

Application mgr
Action Create
On node 1 On node 2
Link Name H12 H21
Adjacent Node 2 1
Action CTRL-V
Action CTRL-V

225
5. Create the first hybrid link accesses

Application mgr
Access
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
Action CTRL-V
Called Number 31888 32888
Action CTRL-V
Note: Called number: for analog line: TA directory No.
Stand By Called Number: LAPD on ISDN B channel commutated via the public network:
seize with overlapping. Stand By Signal Always Established : in this case, signaling is
switched type, backup is not always up.

226
6. Create the second hybrid link access

Application mgr
Path Inter-nodes link / Logical links (ABC-F) / Hybrid
Link Access
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 2 2
Action CTRL-V
StandBy Called Number + False (on demand) + False (on demand)
StandBy Signal Always Established #0120214032000 #0220214031000
Action CTRL-V
Note: Called Number or Main CPUa IP address: The other node IP address (it must be the
main CPU IP address (address by role) in case of duplicated system). Main CPUb IP
address: IP-MAIN address of the second CPU in case of spatial redundancy.
Note: Stand By Called Number: LAPD on ISDN B channel commutated via the public network:
seize with overlapping. Stand By Signal Always Established : in this case, signaling is
switched type, backup is not always up.

227
7. Create trunks
7.1 On access 1
Link trunk
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 1 1
TS number 1 1
Trunk COS 18 18
Action CTRL-V
7.2 On access 2
Link trunk
Action Create
On node 1 On node 2
Link Name H12 H21
Access number 2 2
TS number 1 1
Trunk COS 18 18
Action CTRL-V
number”.

228

4 for DDI.

229

Action 2

Local Node: 1
1 2


Local Node: 1
1 S 2


230
Hybrid links

OBJECTIVE:
◆ To maintain the hybrid links

231
Hybrid links
Command trkvisu ‘Link N°’ (2000-2099)
(102)xa001002> trkvisu 2000
link 2000;
****************** data in Trunk_Group structure ****************
******** data FAISCEAU_NON_RESIDENT

nomfais = N2-N1
************
typjo: (6) => T2HYBRID
************
node_number = 1
network_number = 1
************
******** data ARTERE(link)

cat_signa = 18 ch_canalb = 1 deborde_it = 1 access_turn = 1 mode_reseau = 0
presence_mux = 0 sig_mode = Permanent (0) routing_mode = Dyn (0)
************

The command results are truncated to show only the most significant data.
Trkvisu command syntax:

Usage: trkvisu <num_TG (0-1999) | num_Link (2000-2099) | all | trk | link | comp | ip>
Command results:
•Trunk Group name, trunks type, node and network numbers towards which point this link
•Management DATA:
•Signaling COS: 18 (ABC-F)
•B channel choice validated (ch_canalb = 1)
•DATA to voice TS overflow validated (deborde_it = 1)
•TS distribution validated (access_turn = 1)
•Network mode not validated (mode_reseau = 0)
•Multiplexer presence not validated (presence_mux = 0)
•Signal Establishment mode = Permanent User (sig_mode = Permanent)
•Routing Type = Dynamic Routing (routing_mode = Dyn)

232
Hybrid links
Command hybvisu [ all | Link N° |Node N°]
(102)xa000000> hybvisu 1
Hybrid link 2000 (N2-N1) to node 1 (PERMANENT)

----------------------------------------------
List of accesses
+----+---------------------------------+-------------------------+-----+
| | Main signalling support | Stby signalling support | Nb |
| Nb | GPA State Position Support | GPA State Support | trk |
+----+---------------------------------+-------------------------+-----+
| 1 | ON UP (19, 0, 0) IP | ON DOWN B Channel | 0 |
+----+---------------------------------+-------------------------+-----+
(102)xa001002> hybvisu -f all
List of hybrid links of node 2

Hybrid link 2000 (N2-N1) to node 1 (PERMANENT)
----------------------------------------------
ch_canalb = TRUE deborde_it = TRUE mode_reseau = FALSE
List of accesses
+----+---------------------------------+-------------------------+-----+
| | Main signalling support | Stby signalling support | Nb |
| Nb | GPA State Position Support | GPA State Support | trk |
+----+---------------------------------+-------------------------+-----+
| 1 | ON UP (19, 0, 0) IP | ON DOWN (D) B Channel | 0 |
+----+---------------------------------+-------------------------+-----+

The first command gives the state of ABC link accesses going from node 2 to node1.
The second one with option –f indicates the same results with more detailed management parameters.
hybvisu command syntax:

Usage: hybvisu [-f] all
hybvisu [-f] link (2000-2099)
hybvisu [-f] node (0-99)
hybvisu [-f] link (2000-2099) access (1-24|all)
hybvisu [-f] node (0-99) access (1-24|all)
-f: full display
Management data:
•Link type (PERMANENT)
•B channel choice validated (ch_canalb = TRUE)
•DATA to voice TS overflow validated(deborde_it = TRUE)
•Network mode not validated (mode_reseau = FALSE)
•Accesses list in the ABC link and for each data about the main and standby support:
•X25 Access Group operational (GPA = ON)
•Operational access (State = UP) or not (State = DOWN)
•X25 Access position (virtual crystal or dynamic)
•Signaling support type (IP or B channel)
•Trunks number in the ABC link (here 0)

233
Hybrid links
Command lkvisu all or lkvisu ‘Node N°’
(102)xa000000> lkvisu all

List of all links node by node
node 1:
=========
link 2000 (N2-N1 ) HYBRID sig_mode = Permanent, routing_mode = Dyn
-- acces 1 in 19-0-0: => GPA 1: Hybr_IP, ON
Main sig: IP CPUa: 10.253.253.1 IP CPUb: 255.255.255.255
Twin sig: B channel, called number: 00201431000 (sig_alw_est 0)
Command rsthyb ‘Node N°’ ‘Access N° | all’
(102)xa000000> rsthyb 1 1
Reset of hybrid access (1, 1)
The system will try to re-establish the access (1, 1) in 70 s
Command trkstat ‘Link N°’ (2000-2099)

lkvisu command syntax:

Usage: lkvisu all
lkvisu (node: 0-99)
Management data for each node:

•N°, name and type of kink (HYBRID)
•Signaling type (PERMANENT)
•Routing type (Dyn)
•Accesses list in the ABC link and for each data about the main and standby support:
•X25 Access Group number (GPA 1), signaling type (IP) and state operational or not (ON)
•Called number for each type of signaling link
•Main signaling: IP type, CPU A address and CPU B address (spatial redundancy)
•Standby signaling: (B channel type), called number (0 0201431000), signaling always established = No (0)
rsthyb command syntax:

Reset access by access
Usage: rsthyb <distant node> <access number>
OR
Reset all accesses
Usage: rsthyb <distant node> all
trkstat ‘Link N°’ command is used like for ISDN trunk group.

234
Hybrid links
Traces
Trace setting up of level 3 ISDN traces

➨ Deactivate tuner parameters and empty the buffer
▼ trc i; tuner km; tuner clear-traces
➨ Activate the level 3 ISDN Traces on hybrid links

▼ tuner cpu cpl; tuner hybrid=on; mtracer –a
Stop the trace

➨ Stop mtracer using Ctrl-C keys, empty the trace buffer and
activate trc
▼ tuner clear-traces; trc i
➨ Restart the original process

▼ dhs3_init -R MTRACER

trc command allows to filter access to trace.

Trace example:
______________________________________________________________________________
| (049625:000093) 905: Send_IO1 (link-nbr=0, sapi=0, tei=0):
| long: 491 desti: 0 source: 11 cryst: 19 cpl: 0 us: 8 term: 0 type a5
| tei: 0 <<<< message sent: SETUP [05] Call ref: 00 03
|
| CONCATENATION OF 2 SEGMENTED MESSAGES
|______________________________________________________________________________
|
| [a1] Sending complete
| EI:[04] BEARER_CAPABILITY (l=3) :80 90 a3
| EI:[18] CHANNEL (l=3) : a9 83 85 -> T2 : B channel 5 exclusive
| EI:[1c] FACILITY (l=98)
| Service discriminator [91] : supplementary service
| [aa] NFE (l=6):
| [80] Source Entity : (l=1) : End_PTNX
| [82] Destination Entity (l=1) : End_PTNX
| [a1] INVOKE (l=16):
| Invoke Ident. : 2ee0 (12000)
| OP: ECMA RO_CALLING_NAME (0)
| [80] Name presentation allowed (l=4) : 'DUPONT Jean'
| [a1] INVOKE (l=69):
| Invoke Ident. : 0001 (1)
| OP: ALCATEL RO_CLASSMARKS (1)
| [30] Sequence (l=56) :
| [80] Feature identifier (l=5) : 06 44 6a 1f 04
| [82] Cug (l=1) : 00
| [83] Trunk call priority (l=1) : 00
| [ab] Sequence of Project data (l=41) :
| [30] Sequence (l=15) :

235
Hybrid links
Traces
Trace setting up of hybrid link function traces

➨ Activate the trace

▼ tuner at; actdbg hybr=on; mtracer –a
Stop the trace

➨ Stop mtracer using Ctrl-C, empty the trace buffer and
activate trc
▼ tuner clear-traces; actdbg all=off


Trace example:
(037415:000012) HYB_EtabSig NEQT = 6945

(037415:000013) HYBDYN_EtabSig sig principale NEQT 6945 ( 5, 1)
(037415:000014) HYB_LancerAppel sig principale NEQT 6945 ( 5, 1)
(037415:000015) Numdest = #0620201035000
(037415:000016) Numdest = #0620201035000
(037415:000017) HYB_LancerAppel numcomp[0] = 12
(037415:000022) HYB_LancerAppel numcomp[5] = 2 Dialing of call number of
(037415:000023) HYB_LancerAppel numcomp[6] = 10 remote access
(037415:000031) VPN_InitEtatCanal NEQT= 6945 Etat= 2 nd_dest= 5 num_acces= 1
(037415:000032) EtabCanalB neqt: 6945 Data in sub-address
(037415:000033) EtabCanalBViaFaisceaux NEQT = 6945 «hybrid»
(037415:000034) APPLI_getjonc NumFaisc apres getfais =62
(037415:000035) rz_mess_t2

236
Hybrid links
Traces
Trace setting up of supervision on hybrid link traces

➨ Activate the trace

▼ tuner at; actdbg shybr=on; mtracer –a
Stop the trace

➨ Stop mtracer using Ctrl-C, empty the trace buffer and
activate trc
▼ tuner clear-traces; actdbg all=off


Trace example:

(043530:000219) rz_mess_t2
(043530:000220) APPLI_getjonc: typjo=6
(043530:000221) IO2E_GetUserPosition numldem =62
(043530:000222) IO2E_transfert_etab MaintenanceDemi =5
(043530:000223) envoi_prise_t2 avant send_q931 MaintenanceDemi =5
(043532:000224) Passage dans io2_exploit_status. Index = 7 Status = 0
(043534:000225) Primitive IO2E_Connex
(043534:000226) Sortie rech_it_courant
(043543:000227) HYB_LancerSupervision syst_opt_bool_42 = 0 numfais =2000 neqt=205
(043546:000228) HYB_RelancerSupervision neqt= 63
(043612:000230) HYB_ArretSupervision NeqtNamedSuperv =-1
(043663:000233) rz_mess_t2
(043663:000234) APPLI_getjonc: typjo=6
(043663:000235) IO2E_GetUserPosition numldem =62
(043663:000236) IO2E_transfert_etab MaintenanceDemi =5
(043663:000237) envoi_prise_t2 avant send_q931 MaintenanceDemi =5
(043663:000238) Passage dans io2_exploit_status. Index = 7 Status = 0
(043665:000239) Primitive IO2E_Connex
(043665:000240) Sortie rech_it_courant
(043674:000241) HYB_LancerSupervision syst_opt_bool_42 = 0 numfais =2000 neqt=205

237
Hybrid links
Suproutage tool
Details on hybrid links using suproutage

Output Hybrid Link Description for Node 2
│ Node│Access│ Main Signal │ Second. Sig │Circ│ Circ │ Circ│

│ │ │ Position LAP Activ│ Position LAP Activ│ │Transp│Occup│
│ 1 │ 1 │ IP 19, 0, 0 R 1 1 │ B 19, 0, 1 4 0 │ 0 │ 0 │ 0 │
PCM Detail - Node number, Access number <Enter> Link <L> QUIT <Q>
L for permanent ABC link / H for hybrid link

Details on hybrid links using suproutage is displayed in menu Description of Output Links.

238
Hybrid link
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the hybrid links
MANAGEMENT
1. Do a system data base backup. It will be used as a default data base during the next exercise.
2. Configuration #1: the signaling support (D) is on B channel on synchronous link with
signaling backup (D’) on ISDN switched B channel (on demand). Use the management
procedure ENTP0461C07TEUS.
B1 B2 B3 B4
N1 N2
TA D TA
T2 T2
D’
B B
Carrier
2.1. Manage between the nodes 1 and 2 (same thing for Nodes 3 and 4, 5 and 6 or 4 and
5 if there are only 5 nodes) a permanent hybrid access through TA (to simulate a leased
line, connect the 2 TAs by a crossed cable). Don’t forget to check the presence of the
IO2 or OBCA board!
2.2. The nodes are connected by a PCM link. Allocate only the first 4 PCM timeslots.
2.3. The nodes belong to the backbone.

239
Hybrid link
2.4. Try to ping the nodes.

2.5. Check the information given by the suproutage command.
2.6. Carry out an audit and check that you can call the remote extensions.
3. Configuration #2: All nodes are now in the backbone. The nodes 1 and 2 (same thing for
nodes 3 and 4, 5 and 6 (if present)) are connected for signaling through IP (D channel) with
signaling backup (D’ channel) on ISDN switched B channel (on demand). Use the
management procedure ENTP0461C01TEUS.
B1 B2 B3 B4
N1 N2
T1/T2 T1/T2
D’
B B
Carrier
LAN
3.1. The nodes are connected by a PCM link. Allocate only the first 4 PCM timeslots.
3.2. Check the information given by the suproutage command.

240
Hybrid link
4. Configuration #3: All nodes are in the backbone. The nodes 1 and 2 (same thing for nodes 3
and 4, 5 and 6 (if present)) are connected for signaling through a D channel of a ISDN link
(T1/T2)) with signaling backup (D’ channel) on IP. Use the management procedure
ENTP0461C02TEUS.
B1 B2 D B3 B4
N1 N2
T1/T2
LAN
D’
4.1. The nodes are connected by a T1 or T2 link. Allocate only the first 4 ISDN timeslots.
4.2. Check the information given by the suproutage command
and 4, 5 and 6 (if present)) are connected for signaling through a D channel of a ISDN link
(T1/T2)) for the first access and without signaling for the second access. Use the management
Call Server
Call Server
B1 B2 D B3 B4
N1 Access 1 T1/T2
N2
Access 2 PCM B1 B2 B3 B4
5.1. The B channels of the first access are provided by the ISDN link. Allocate only the first 4
PCM timeslots.
5.2. The B channels of the second access are provided by a PCM link. Allocate only the first 4
PCM timeslots.

241
Hybrid link
and 4, 5 and 6 (if present)) are connected for signaling (D1) on B channel on synchronous link
with signaling backup (D1’) on ISDN switched B channel (on demand) for the first access and
with IP signaling (D2) for the second access with signaling backup (D2’) on ISDN switched B
channel. Use the management procedure ENTP0461C06TEUS.
B1 B2 B3 B4
N1 N2
TA D1 TA
T2
T2
D1’
B B
D2’
B B
PSTN
LAN
D2
6.1. The B channels of the first access are provided by the PCM link. Allocate only the first 4
PCM timeslots.
6.2. The B channels of the second access are also provided by the PCM link. Allocate only the
next 4 PCM timeslots.

242
Hybrid link
7. Configuration #5: Hybrid link between node 1 and 2 is switched B channel type (on request).
This type of link is for an end node with low traffic (static routing). Use the management
N1 N2
D
B B
T2 T2
B
B B
PSTN
7.1. The B channels are provided by the VPN overflow. Use the management procedure
ENTP0450C01TEUS.

243
Hybrid link

244
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
245
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
246
PARTICIPANT'S GUIDE
System Networking
Part 2/2
REF. ENTPTE402US
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).
System Networking TOC.doc
DOCUMENTATION CHANGES
ISSUE DATE ISSUE DATE
01 02/06
Alcatel OmniPCX Enterprise System Networking
File reference: ENTPTE402US
GENERAL SUMMARY
Part 2
9. VPN overflow
ENTP0450P01TEUS.......................................................................................................... 247
ENTP0450C01TEUS ......................................................................................................... 259
ENTP0450M01TEUS......................................................................................................... 273
ENTP0450H01TEUS ......................................................................................................... 289
10. Executive / Assistant in network

ENTP0407P02TEUS.......................................................................................................... 293
ENTP0407M02TEUS......................................................................................................... 297
ENTP0407C03TEUS ......................................................................................................... 299
ENTP0407H02TEUS ......................................................................................................... 303
11. 4645 in network

ENTP0432P05TEUS.......................................................................................................... 307
ENTP0432M05TEUS......................................................................................................... 311
ENTP0432C05TEUS ......................................................................................................... 315
ENTP0432H05TEUS ......................................................................................................... 319
12. System messages centralization

ENTP0421P02TEUS.......................................................................................................... 323
ENTP0421C02TEUS ......................................................................................................... 327
ENTP0421H03TEUS ......................................................................................................... 333

TOC.doc System Networking
13. DECT in network

ENTP0419P12TEUS.......................................................................................................... 337
ENTP0419C12TEUS ......................................................................................................... 343
ENTP0419M12TEUS......................................................................................................... 351
ENTP0419H04TEUS ......................................................................................................... 355
14. Hunt groups in network

ENTP0405P04TEUS.......................................................................................................... 359
ENTP0405C05TEUS ......................................................................................................... 363
ENTP0405M02TEUS......................................................................................................... 369
ENTP0405H03TEUS ......................................................................................................... 371
15. Private to public overflow

ENTP0451P01TEUS.......................................................................................................... 375
ENTP0451C01TEUS ......................................................................................................... 381
ENTP0451H01TEUS ......................................................................................................... 387
16. Public to private rerouting

ENTP0452P01TEUS.......................................................................................................... 391
ENTP0452C01TEUS ......................................................................................................... 395
ENTP0452H01TEUS ......................................................................................................... 401
17. ARS Server

ENTP0454P01TEUS.......................................................................................................... 405

System Networking TOC.doc

TOC.doc System Networking
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:

VPN overflow

OBJECTIVE:
◆ To describe the VPN hop principles

Main principles
Necessary elements
Call set-up
VPN privilege
Resources limitation
Alcatel OmniPCX Enterprise – VPN overflow

247
VPN overflow
Objectives
Objective of Virtual Private Network overflow
➨ Offers to ABC-F users the network features in case of private

link saturation
▼ Use system trunk groups (public or private) to route ABC
communications
➨ Optimize the link used between nodes
▼ Systematic use of VPN on low rate links
▼ Enhance telephone traffic without increasing the rate of link
➨ Optimize the communication cost in case of overflow
▼ Use of ARS with or without restriction according to user category


248
VPN overflow
Necessary elements
An operational ABC-F network
➨ ABC-F2 link on T0,T1,T2 or compressed
➨ Hybrid link (leased line, IP network, dynamic link,

compressed link, etc..)
Incoming/Outgoing trunk groups on both sites
➨ ISDN or IP trunk group
Dedicated number (prefix) for VPN service
➨ DDI numbers in case of non IP trunk group
▼ Those numbers are used to establish the VPN call via the public
carrier even if the called number is not DID

This feature is a software lock

VPN numbers must be accessible directly without going through attendant
•In ISDN trunk groups, they must be DID
•In case of private links (ISDN or IP), they must belong to the dialing plan reachable by remote party

249
VPN overflow
Call set-
set-up
VPN call set-up
➨ Dialing of a network prefix from departure node
▼ Look for the best path trough ABC network (X25 routing)
➨ VPN service request on the remote node
▼ VPN number allocation to the called number
▼ VPN number creation (internal and public) according to the prefix used
➨ Sending of these two numbers through the ABC link
➨ VPN prefix analysis on the departure node
▼ Call set-up according to management (with or without ARS)
▼ Sending of information over ABC and release of VPN prefix on the remote
node.


250
VPN overflow
VPN hop without ARS
1 2 3 VPN Table N°
Call of 32000 Link saturated VPN service request 32000 32599
Node 1 Node 2
D chan.
31000 32000
32599 0201032599
32599 32599
99 5
VPN prefix distant 325 VPN prefix local
Info (N° ARS) : -1 Info (N° DPN) : 33
6 4
99
25
Call.back.transl 0 10
3 ISDN NPD 33
02
DEF : Add 00 network NDI : 020103
0 : Add 0 DDI transl : 0
0201032599
Prefix Plan DDI transl 0
7
0 : public T2 Internal : 32000
External : 2000
Size : 600

The ABC network is made up of an ABC-F link (T0,T1,T2 or hybrid) and a VPN hop using public T2 ISDN trunk group .
• Number dialing over ABC network
• The routing asks for VPN service because the ABC link is saturated of the VPN service is available.
• VPN prefix allocation to VPN call using for voice set-up between extension 31000 and 32000.
• Send of VPN information number over ABC link.
• VPN information send by the remote are analyzed by the departure node ,because the information in the VPN prefix equal –
1 the departure node uses its call back translator to establish the VPN call.

251
VPN overflow
VPN hop with ARS
1 2 3 VPN Table N°
Call of 32000 Link saturated VPN service request 32000 32599
Node 1 Node 2
D chan.
31000 32000
32599 0201032599
32599 32599
99 5
VPN prefix distant 325 VPN prefix local
Info (N° ARS) : 12 Info (N° DPN) : 33
6 4
9
ARS table 12 32
59 ISDN NPD 33
Route 1 : TG. 12 network NDI : 020103
Add : 72010 DDI transl : 0
7201032599
Timed Based Route DDI transl 0
7
1 : Route 1 Internal : 32000
External : 2000
Size : 600

The main differences with the previous slide are :

• The information is managed now in the VPN prefix on the departure node.
• This information corresponds to the ARS table used by the departure to set-up the VPN call.

252
VPN overflow
Hop limits
For one call, the maximum number of VPN hop is 2
VPN VPN VPN

N1 1-2 N2 2-3 N3 3-4 N4
➨ The call between node 1 and node 4 is impossible
VPN
2-4
VPN VPN VPN

N1 1-2 N2 2-3 N3 3-4 N4
VPN
1-3
➨ The call between node 1 and node 4 is now possible

▼ It is possible now to use VPN hop 1 – 2 2 – 4, or 1 – 3 3 - 4


253
VPN overflow
X25 Routing
The routing knows the VPN hop management

It supervises the resources status (B channels) on the trunk
group used by the VPN
➨ Use of X25 access cluster linked to the trunk group (IP or
ISDN)
➨ Use of an adjacent network to broadcast the resources

status over the ABC-F network.
▼ This adjacent network must be different than the adjacent network
used by default (usually 15)
The VPN hop and prefixes must be known on all the nodes
of the ABC-F network
▼ Use audit and broadcast


254
VPN overflow
Access service rights
A VPN overflow call is set-up through a trunk group
➨ According to the network architecture, this overflow can be:
▼ Mandatory
✦ Hybrid link saturated permanently (Example: hybrid link over IP with IP

trunk group)
✦ Mandatory for some kind of calls

(Example: data call on compressed link)
▼ Conditional
✦ Use of ISDN trunk group in case of ABC link saturation
The VPN hop is allowed according to the VPN hop

management and network topology

If B channels are compressed (internal or external compression), it’s impossible to use B channels for data communication. In this
case, VPN hop via public network is the only solution for calls establishment.

255
VPN overflow
Access service rights
This barring is not linked to the public barring allocated to

the users
➨ Management of a specific right in the public access class of
service
▼ VPN cost limit (-1, or from 0 to 31)
Each VPN hop has a VPN cost allocated in

management
➨ For the «Voice» or « Data » calls it is possible to declare if
the VPN hop is mandatory or not
▼ Mandatory hop if there is no B channel for this type of call
➨ The cost of a VPN call equal the sum of each VPN hop
used for this call
▼ Maximum 2 VPN hops

The VPN cost cannot be inferior to 1 in management.

When the VPN hop is declared as mandatory the cost of this VPN hop equal 0
In the user public access COS the VPN cost can be managed from –1 to 31.
• -1 : VPN forbidden
• 0 : Only mandatory VPN hop allowed .
•1 to 31 : VPN authorized according to the sum of the different VPN hops necessary to set-up the VPN call.
Ex : Cost (N1 - N3) = Cost of (N1 - N2) + Cost of (N2 - N3)

256
VPN overflow
Necessary condition for VPN hop set-
set-up
The ABC link must be operational and the VPN hop

known by X25 routing application
The VPN cost in the user public access COS must be

superior or equal to the VPN hop cost
B channel must be available on the incoming and

outgoing trunk group used for VPN
A VPN prefix must be available on the remote node
In case of using ARS the management must be set-up

correctly on the caller node
The trunk groups used by VPN must be operational.

1. If ABC link is not operational, no information can be exchanged in ABC protocol about VPN hop, the VPN hop must be known so
that routing can do a VPN request.
2. VPN hop user cost in public access COS must be superior or equal to the sum of each VPN hop cost (2 maximum). In case of
mandatory VPN hop, the cost is 0, so it’s enough to have a COS with VPN cost to 0 to authorize all VPN calls.
3. State of B channels of trunk groups used for VPN hop is supervised by routing with adjacent network concept defined in the trunk
group.
4. VPN prefix is affected during the VPN call in network. It’s immediately released after reception of public call via the trunk group (1
or 2 seconds maximum usually).
5. Local ARS management allows to optimize the cost of VPN calls, in case of error the system can try to call by using external
callback translator. If management is not correct (or if distant prefix number is unknown), the call will fail definitely.
6. The operational state (T2 level 2) is supervised by routing. In some ABC network configurations (static routing with end nodes for
instance) it’s impossible to know before calling the state of resources. In this case, the call is launched and it will fail if the trunk
group doesn’t work or is saturated on remote node.

257
VPN overflow
Resources limitation
The number of VPN calls can be limited in different ways
➨ For each trunk group allocation of a percentage of VPN

Time slot
▼ Example: 50% VPN TS
✦ 15 VPN calls maximum in case of T2 trunk group
For each VPN hop

▼ Maximum number of call allowed
✦ For VoIP calls (IP trunk groups)
✦ For other calls (public or private ISDN trunk groups)

The percentage of TS allows to limit the number of incoming and outgoing calls on each system. This facility allows to guarantee a
number of B channels available for ISDN calls.
For IP trunk group the percentage of TS which can be used for VPN equal 100% by default.
The type of compression algorithm used on IP trunk group is defined in system parameters.
The maximum number of calls allowed is available from R5.1.
This function allows to limit the number of communications per direction. The same trunk group (ISDN or IP) can be used for several
VPN hops, this allows to reserve resources for a specific direction or to take into account bandwidth limitations according to the
network.

258
VPN overflow
PROCEDURE
VPN overflow
OBJECTIVE
- To learn how to manage a VPN overflow with and without ARS management
REFERENCE
Private Networks / ABC-F homogeneous private network / VPN overflow
OVERVIEW
This procedure deals with the management of VPN overflow between nodes 1 and 2 via an ISDN
link (T2/T0/T1) using ARS and in case of ARS error using external call back translator.
In case of error in the ARS management, the system switches automatically to the management of
the external callback translator. This last has to be managed on customer site.

259
VPN overflow
PROCEDURE
1. Program the VPN overflow
1.1 Modify the remote network in the T2 trunk group used for the VPN hop
Application mgr
Path Trunk groups
On node 1 On node 2
Action CTRL-V
Remote network 14 14
Action CTRL-V
Note: The remote network number must not be the default value (15) nor the ABC F network
number.
1.2 Validate the routing supervision of the ISDN trunk group, and the number of
time slots that can be used by the VPN hop
Application mgr
Path Trunk groups / Trunk group
On node 1 On node 2
Action CTRL-V
Supervised by Routing +YES +YES
VPN TS % 50 50
Action CTRL-V
Note: Supervised by routing: For T2 and T0: YES: a GPA (access point group: cluster x25) is
created automatically and associated to this trunk group. The automatic
creation/destruction of this GPA is done at the same time as the creation/destruction of the
trunk group bus-access. This attribute can be consulted but not modified. For any
modification of the VPN HOP, this cluster must be de-validated
VPN TS %: By default, the half of the time slots can be used for the VPN. This value is
sufficient for a T2. In some cases, these value can reach 100%.

260
VPN overflow
1.3 Check broadcast validation

Application mgr
On node 1 On node 2
Operational +YES +YES
Action CTRL-V
Note: Audit have been done previously and a "cleanbroad all" (use this command carefully), only
on one node.
1.4 Check hybrid link status

Application suproutage (under mtcl) Tab
Action 2

Local Node: 1
1 S 2


261
VPN overflow
1.5 Create the local VPN prefixes

Application mgr
Action Create
On node 1 On node 2
Number 31099 32099
Prefix Meaning VPN overflow VPN overflow
Prefix Info 33 34
VPN Type +Local (NPD No.) +Local (NPD No.)
Action CTRL-V
Note: Number of VPN prefixes is according to traffic. Number of local VPN prefixes must be equal
to the number of simultaneous VPN calls (4 or 5 usually). “NPD N°” into the prefix info must
be managed in case of external callback use (without ARS). With ARS, keep the default
value 0.
1.6 Wait for the arrival of the distant VPN prefix from the remote node (the
broadcast must be running for that !) or use the immediate broadcast.
Application mgr
On node 1 On node 2
Number 32099 31099
Prefix Info -1 -1
VPN Type + Distant(List route No.) + Distant(List route No.)
Action CTRL-V

262
VPN overflow
1.7 Creation of the NPD in case of external call back use (without ARS)
Application mgr
Path Translator / External Numbering Plan / Numbering Plan Description
(NPD)
Action Create
On node 1 On node 2
Description identifier 33 34
Name VPN1 VPN2
Install. number source + NPD source + NPD source
Called DID identifier 0 0
Calling DID identifier 0 0
Action CTRL-V
Installation number 02010 02010
Note: NPD id is free, but NPD exist already in the system so this one must be created between 33
and 50. DID translator used for incoming and outgoing can be specific translators. But
usually VPN prefixes belong to the DID numbering plan, the default DID translator( id 0) is
appropriate most of the time.
1.8 Creation of DDI default translator rules (without ARS)

Application mgr
Path Translator / External Numbering Plan / Default DID num. translator
Action Create
On node 1 On node 2
First External Number 31000 32000
First Internal Number 31000 32000
Range size 100 100
Action CTRL-V

263
VPN overflow
1.9 Creation of external callback translator

Application mgr
Path Translator / External Numbering Plan / Ext.Callback Translation
Action Create
On node 1 On node 2
Basic Number DEF DEF
No.Digits To Be 0 0
Removed #012 (TG seiz. prefix) #022 (TG seiz. prefix)
Digits To Add
Action CTRL-V
1.10 Change the ARS table linked with the Distant VPN prefix
Application mgr
On node 1 On node 2
Number 32099 31099
Prefix Info 12 21
VPN Type + Distant(List route No.) + Distant(List route No.)
Action CTRL-V

264
VPN overflow
1.11 Create the ARS tables linked with the Distant VPN prefix
1.11.1 Create the ARS tables

Application mgr
Path Translator / Automatic Route Selection / ARS Route list /
Action Create
On node 1 On node 2
ARS Route list 12 21
Name VPN 12 VPN 21
Action CTRL-V
1.11.2 Create the ARS routes in the table

Application mgr
Path Translator / Automatic Route Selection / ARS Route list / ARS Route
Action Create
On node 1 On node 2
Route 1 1
Name T2 T2
Trunk Group 12 22
Digits To Add 02010 02010
Quality + Speech + Speech
Action CTRL-V
Note: Digits to add: Add the digits indicated at the beginning of the number (Installation
Number). This attribute is used to change dialing, this is the only means of doing, it in the
case of a T1, T2, T0 trunk group.

265
VPN overflow
1.12 Create the ARS time based route lists in the table
Application mgr
Path Translator / Automatic Route Selection / ARS Route list /
Time-based Route List
Action Create
On node 1 On node 2
Time-based Route List ID 1 1
Action CTRL-V
Action Add
Time-based Route 1 1
Number
Action CTRL-V

266
VPN overflow
1.13 Update the users access category
1.13.1 Consult the Public Network COS allocated to the users on both nodes
Application edsbr -l US0 (under mtcl)
enter criteria or command dir
enter criteria or command pna
enter criteria or command go
Result Example:
+--------+---+
|dir |pna|
+--------+---+
|31000 | 2|
|31001 | 22|
|31201 | 2|
|31202 | 2|
|31300 | 2|
|31600 | 2|
+--------+---+
Note: Dir ->Directory number, pna -> Pub Ntwrk/PSTN Access
1.13.2 Update the users Classes of Service (Public Network COS)

Application mgr
Path Classes of Service / Access COS
On node 1 On node 2
Public Network COS 2 2
Action CTRL-V
VPN Cost Limit
Night 0 0
Day 0 0
Mode 1 0 0
Mode 2 0 0
Action CTRL-V

267
VPN overflow
1.14 Create the VPN hop (on one node only !)
1.14.1 Create the VPN hop on one node (example: on node 1)

Application mgr
Chemin Inter-Node Links / VPN Overflow
Action Create
Node X - Node Y 1-2
Network 1 14
Network 2 14
VPN Hop cost 1
Mandatory VPN hop in quality 0 +YES
Mandatory VPN hop in quality 0 +YES
IP Compression Type + Default
Maximum number of IP calls -1
Maximum number of other calls -1
Note: Node X - Node Y: This attribute enables the declaration of the 2 link nodes, local and
remote. Syntax: X-Y, obligatorily in ascending order (X<Y).
Network 1 and 2:These 2 attributes enable the identification of the network (transporter)
for nodes X and Y respectively. The network numbers corresponding to the remote network
declared on each side in the trunk group.
VPN hop cost: This attribute gives the average VPN overflow cost in connection with the
public network (transporter) cost. It therefore serves to limit VPN hops according to the
caller's privileges: the add on cost for each hop is compared with caller's cost limit. (see
PUBLIC NETWORK ACCESS COS - VPN cost limit). If the caller's cost is lower than the VPN
hops add on cost, the call is rejected. (Cost limits compared with VPN hop costs can be
found in USER under PUBLIC NETWORK ACCESS COS, in the ARS ROUTING TABLE under
ARS overflows and also in TRUNK GROUP under external incoming calls).
Mandatory VPN hop in quality 0: Quality 0 = DATA quality, Quality 1 = voice quality
YES: The VPN hop is carried out without accounting for it's cost in the cost limit calculation.
This is useful when the B channels of an ABC-F link are constantly unavailable (obligatory
VPN hop). Without this feature, certain users whose cost limits are too low can no longer
communicate (saturated link and VPN overflow rejected).
IP Compression Type: - Default = type of compression managed in INSTALLATION
(COMPRESSION PARAMETERS). Not compressed G711, - Compressed: G723 or G729
Maximum number of IP calls: This attribute allows the number of calls on an IP trunk
group to be limited for the specified VPN hop (outgoing and incoming). It is to adapt the
flow of IP calls with the available bandwidth. -1 = no control
Maximum number of other calls: This attribute allows the number of calls other than IP
to be limited for the specified VPN hop (outgoing and incoming). It is possible in this way to
control the number of VPN calls in each direction. -1 = no control

268
VPN overflow
1.15 Enable the VPN service in the system
1.15.1 On node 1
Application mgr
Path System / Other system param.
On node 1 On node 2
VPN service + True + True
Action CTRL-V

269
VPN overflow
1.16 Check the complete programming of the VPN

Application lookvpn -test (under mtcl)
Result Example:
*******************************************************************
VPN is ALLOWED
* nodes 1 - 2 (netw 14 -- netw 14) cost 1 mandatory q0: Y q1: Y
Checking trunk groups corresponding to local hop to node 1 ( 1 - 2)
+ Trunk group 22:name = T2 state: FREE
trk_type T2 next_trk_grp = -1 variant T2
nb_chif_uti = 6 specificity: NONE
x25 ok. vpnRate = 100 immTrkForVpn=1
Public NPD 15 Incoming DID 0
Private NPD 0 Incoming DID 0
+ Trunk group 25:name = IP state: FREE
trk_type T2 next_trk_grp = -1 variant ISDN
nb_chif_uti = 0 specificity: IP
x25 ok. vpnRate = 100 immTrkForVpn=1
Public NPD 9 Incoming DID -1
Private NPD 0 Incoming DID -1
WARNING: another NPD can be used (depends on the byte3 of the called number)
Verify which NPD is used on arrival with looknumin
*******************************************************************
Table of vpn numbers for the local node
Index | State | Eqt<-> | NPD | VPN Local Nber | Ext.Transl. | VPN DDI Nber |SDA trad.
_____ | _____ | ______ | ___ | _______________|_____________|______________|_________
0 | Free | None | 34 | 32099 | 32099 |0213132099 | -1
_____ | _____ | ______ | ___ | _______________|_____________|______________|_________
*******************************************************************
External Call Back Translator Tables
1)beginning_of_number=A nb_digits_to_suppr=1 number_to_add = 900
2)beginning_of_number=0 nb_digits_to_suppr=0 number_to_add = 9
3)beginning_of_number=DEF nb_digits_to_suppr=0 number_to_add = 90
*******************************************************************
Table of distant vpn numbers
31099 Tsl_Distant_VPN_Number RLN 21
---------------------------------------
Rout List ARS 21
1) trk_grp=22 nb_deleted_digits=0 inserted_digits = 02131 (ie. 0213131099)

270
VPN overflow
1.17 Check the programming of the access categories

Application lookvpn -categ (under mtcl)
Result Example:
*******************************************************************
VPN Rights values in Public Categories
ind| night day mode1 mode2 |
----------------------------------------
0 | -1 -1 -1 -1 |
1 | -1 -1 -1 -1 |
2 | 0 0 0 0 |
3 | -1 -1 -1 -1 |
4 | -1 -1 -1 -1 |
5 | -1 -1 -1 -1 |
6 | -1 -1 -1 -1 |
7 | -1 -1 -1 -1 |
8 | -1 -1 -1 -1 |
9 | -1 -1 -1 -1 |
10 | -1 -1 -1 -1 |
11 | -1 -1 -1 -1 |
12 | -1 -1 -1 -1 |
13 | -1 -1 -1 -1 |
14 | -1 -1 -1 -1 |
15 | -1 -1 -1 -1 |
16 | -1 -1 -1 -1 |
17 | -1 -1 -1 -1 |
18 | -1 -1 -1 -1 |
19 | -1 -1 -1 -1 |
20 | -1 -1 -1 -1 |
21 | -1 -1 -1 -1 |
22 | -1 -1 -1 -1 |
23 | -1 -1 -1 -1 |
24 | -1 -1 -1 -1 |
25 | -1 -1 -1 -1 |
26 | -1 -1 -1 -1 |
27 | -1 -1 -1 -1 |
28 | -1 -1 -1 -1 |
29 | -1 -1 -1 -1 |
30 | -1 -1 -1 -1 |
----------------------------------------
********************************************************************

271
VPN overflow

272
VPN Overflow

OBJECTIVES:
◆ To maintain the VPN overflow
◆ To analyze the important information in the commands of maintenance
Alcatel OmniPCX Enterprise – Maintenance VPN Overflow

273
VPN Overflow
Steps of a VPN call
Different steps for a call establishment between 31000

(N1) and 32000 (N2)
➨ Network must be operational and the link saturated
➨ VPN service must be activated and resources available
➨ The set’s COS must allow VPN hop
➨ Request for a VPN number on node 2
➨ Receipt of a local & public VPN number
➨ Received prefix has to be declared as a distant VPN prefix
➨ Either callback translator or ARS table is used
➨ Dialing of the number then VPN synchronization message is

sent

VPN resources are:

•Available B channels for the type of call (Voice, Data, Fax, etc..) on local & distant trunk groups supervised by X25 routing
•Distant VPN numbers must be free
The value in the public access COS must be superior or equal to the VPN hop cost (0 means mandatory VPN hop only).
The called node sends through the ABC network 2 numbers: the VPN prefix and the public number built according to the NPD and
the local prefix. In case of a VPN hop over IP, it sends also the IP address (hexadecimal) corresponding to the coupler of the trunk
group used for the VPN.
Prefix received can be linked either to a callback translator (info –1) or an ARS table (info between 1 and 4000).
If such prefix doesn’t exist, then call is aborted.
If the callback translator is used, the number for the public network is the public number received in the ABC frame.
If ARS is used, VPN prefix received will be modified before sending.
Synchronization VPN message is sent through the link. Then the prefix will be reserved for the call for 30 sec (default value), if the call
is not established after this period of time the prefix is released on the distant node.

274
VPN Overflow
To check the management of the VPN hop
➨ lookvpn command
▼ Can be used with options –test / –user N° / –categ
To check the resources available
➨ suproutage command
ABC-F exchange traces
➨ ISDN traces with t3 or mtracer –a
To supervise VPN communications

➨ vpnstat and trkstat commands

lookvpn -test command summarized the management of the different VPN hops declared on the node.
lookvpn –user Nb command summarized some important parameters for one set.
lookvpn –categ command indicates for each COS the VPN cost value.
suproutage command gives information about X25 routing managed resources.
ISDN traces can be used to analyze the exchange between nodes (for instance VPN numbers received).
vpnstat and trkstat commands display B channels used on trunk groups.

275
VPN Overflow
lookvpn command
lookvpn –test command

(1)xa000001> lookvpn -test
***************************************************************************
VPN is ALLOWED
* nodes 1 -- 2 (netw 14 -- netw 14) cost 1 mandatory q0 : Y q1 : Y
Checking trunk groups corresponding to local hop to node 2 ( 1 -- 2)
+ Trunk group 11 : name = IP Noeud1 state : FREE

trk_type T2 next_trk_grp = -1 variant ISDN
nb_chif_uti = 0 specificity : IP
x25 ok. vpnRate = 100 immTrkForVpn = 1
Public NPD 9 Incoming DID -1
Private NPD 0 Incoming DID -1
+ Trunk group 12 : name = T2 Noeud1 state : FREE

trk_type T2 next_trk_grp = -1 variant T2
nb_chif_uti = 0 specificity : None
x25 ok. vpnRate = 50 immTrkForVpn = 1
Public NPD 15 Incoming DID 0
Private NPD 1 Incoming DID 0
WARNING : another NPD can be used (depends on the byte3 of the called number)
Verify which NPD is used on arrival with looknumin

Analysis of the command results:

VPN is ALLOWED: VPN service has been validated in the system parameters
Following lines show all VPN hop known on this node with information concerning the remote network (supervised by X25 routing)
(here network 14) and the cost of the VPN hop (VPN hop is mandatory for voice and data).
Per hop, the command displays all available trunk groups (all those that use the remote network indicated in the VPN hop).
In this example there is 2 TG, 11 (IP T2) and 12 (ISDN T2). Are displayed:
•T2 state (FREE, OOS, etc…)
•Protocol used (ISDN = ISDN all countries, T2 = ISDN France)
•Specificities (IP or None)
•The X25 access cluster status used by routing (x25 ok or nok)
•NPD used (can be modified if the byte 3 value in the SETUP is not standard).
•Incoming DDI translator

276
VPN Overflow
lookvpn command
lookvpn –test command (next)

Table of vpn numbers for the local node
Index | State | Eqt<-> | NPD | VPN Local Nber | Ext.Transl. | VPN DDI Nber |SDA trad.
_____ | _____ | ______ | ___ | _______________|_____________|______________|_________
0 | Free | None | 33 | 31600 | 1600 | 201431600 | 0
1 | Free | None | 33 | 31601 | 1601 | 201431601 | 0
2 | Free | None | 33 | 31602 | 1602 | 201431602 | 0
3 | Free | None | 33 | 31603 | 1603 | 201431603 | 0
_____ | _____ | ______ | ___ | _______________|_____________|______________|_________
***************************************************************************
External Call Back Translator Tables
1) beginning_of_number = DEF nb_digits_to_suppr = 0 number_to_add = 00

2) beginning_of_number = 0 nb_digits_to_suppr = 0 number_to_add = 0
3) beginning_of_number = A nb_digits_to_suppr = 1 number_to_add = 000
***************************************************************************

Analysis of the command results (next):

•The list of local VPN numbers with the corresponding management:
•NPD used (here 33)
•Local VPN number and DDI
•The full VPN number sent
•The DDI translator used used to create the public number
•The external callback translator
•Used with the public number received in the ABC protocol

277
VPN Overflow
lookvpn command
lookvpn –test command (next)

Table of distant vpn numbers

---------------------------------------
Rout List ARS 12
1) trk_grp=11 nb_deleted_digits=0 inserted_digits = vpnCostLimit=0

(ie. 32600)
2) trk_grp=12 nb_deleted_digits=0 inserted_digits = 02014 vpnCostLimit=0

(ie. 0201432600)

---------------------------------------
Rout List ARS 12
1) trk_grp=11 nb_deleted_digits=0 inserted_digits = vpnCostLimit=0

(ie. 32601)
2) trk_grp=12 nb_deleted_digits=0 inserted_digits = 02014 vpnCostLimit=0

(ie. 0201432601)
***************************************************************************
Value of VPN synchronisation timer --> T_VPN_SYNCHRO = 300
***************************************************************************

Analysis of the command results (next):

•The list of distant VPN numbers with the corresponding management:
•In this example each number is linked to an ARS table (Route List Number (RLN 12))
•Each route of the ARS table is displayed
•Per physical route the number that will be dialed is indicated
•In this example, is sent first the prefix over the IP trunk group, then the public number rebuilt over the public T2
•The timer default value 30 seconds
•If the call doesn’t succeed during that timer, the prefix is released

278
VPN Overflow
lookvpn command
lookvpn –user 31000 command

(1)xa000001> lookvpn -user 31000
SET : pub.cat = 2, entity_num = 1, state = 0 => limit_cost = 0
lookvpn –categ command

(1)xa000001> lookvpn -categ
***************************************************************************
VPN Rights values in Public Categories
ind| night day mode1 mode2 |

----------------------------------------
0 | -1 -1 -1 -1 |
1 | -1 -1 -1 -1 |
2 | 0 0 0 0 |
******
28 | -1 -1 -1 -1 |
29 | -1 -1 -1 -1 |
30 | -1 -1 -1 -1 |
----------------------------------------

lookvpn –user nb
Are displayed: the public access COS of the set is 2, its entity (1) , its status Night (state 0), and the limit cost related to its COS 0
(means mandatory VPN hop only).

279
VPN Overflow
suproutage command
suproutage command (Topology)

NETWORK COST TOPOLOGY FOR VPN Quality Voice
Local Node : 1
┌───┐ ┌───┐
│ 1├─────────────────────────14───── 1 ────14────────────────────────┤ 2│
└───┘ └───┘
Cost = 1 (TS_FREE>=8), 2 (8>TS_FREE>=2), 3 (TS_FREE =1), S (TS_FREE =0)


Key 5 pressed (VPN costs):

• Between nodes 1 and 2, the number 1 indicates the cost associated to the VPN hop which means that there are at least 8 free TS
• The cost indicated by the routing is concerning VPN communications (indicated on top of the page).

280
VPN Overflow
suproutage command
suproutage command (Network’s Trunks description)

TRUNKS LINKED TO NETWORK DESCRIPTION 14
Local Node: 1
Rate = 600 Quality DATA
│Node │ COST │ COST Tel │ COST VPN │ COST │ COST COMP│Trnkld│

│DESTI│X25D X25B│DATAIn DATAOut│DATAIn DATAOut│ X31 │ DATAOut │ DATA │
│ 2 │ OFF OFF│ S S │ S S │ OFF │ S │ 32 │
│ 1 │ OFF OFF│ 1 1 │ 1 1 │ OFF │ 1 │ 12 │
NEXT PAGE: <v> QUIT: <Q>

Choice 6 displays a page where you can select the remote network you interested with. Once you’ve chosen, all trunk groups related
to this remote network are displayed.
For each node of the ABC network the information given are:
• The Id of concerned trunk groups (TrnkId column)
• The node number that the routing supervises (Node column)
• Calculated costs by the X25 routing for each type of communication
In this example, the S indicates that VPN resources for this node (node 2) are saturated.
The trunk group (or X25 cluster access) might be out of service.

281
VPN Overflow
ISDN Traces
ISDN exchange analysis in the ABC link
➨ Request for a VPN number
➨ Receipt of VPN numbers (prefix and public number)
▼ The IP address of the gateway is indicated for a IP trunk group
➨ The public call is made on the corresponding trunk group
▼ Use of the received prefix (ARS table) or the public number (External
callback translator)
➨ Synchronization message is sent
➨ Connection / Release of the ABC & ISDN communications

Lunching a ISDN trace:

•Classical ABC link: t3
•Hybrid link: tuner km; tuner clear-traces; tuner cpu cpl; tuner hybrid=on; mtracer –a
Stopping the ISDN trace:

•Ctrl-C then tuner clear-traces; dhs3_init –R MTRACER
Accesses to tracer can be filtered by trc

282
VPN Overflow
ISDN Traces
ABC message SETUP

| IE:[18] CHANNEL (l=1) a8 -> T2 : No B channel No B channel in the link
***********
| OP: ALCATEL RO_VPN_NODE_LIST (7032)
| [30] Sequence of (l=13)
| [30] Sequence (l=3) Here is given the list of VPN hops
| [02] Node (l=1) 01 (here Node 1 to Node 2)
| [30] Sequence (l=6) hop is authorized (Barre = true)
| [02] Node (l=1) 02
| [01] Barre (l=1) 01 True
***********
| [a1] INVOKE (l=27):
| Invoke Ident. : 1b75 (7029)
| OP: ALCATEL RO_VPN_DDI_NUMBER (7029)
| [40] QSIGInformationElement (l=12) Request for a VPN number
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3 the call is of type Voice
| IE:[7d] HLC (l=2) 91 81 (BC = 80 90 A3)
| IE:[32] EI_PARTY_CATEGORY (l=1) 81
***********
| [a1] INVOKE (l=16):
| Invoke Ident. : 1b7e (7038)
VPN hop is mandatory cost = 0
| OP: ALCATEL RO_VPN_COST (7038)
| [02] Integer (l=1) 00
***********
| IE:[6c] CALLING_NUMBER (l=7) -> 00 81 Num : 31000
Extension 31000 calls 32000
| IE:[70] CALLED_NUMBER (l=6) -> 80 Num : 32000

ISDN messages were cut in order to keep only significant elements.

283
VPN Overflow
ISDN Traces
ABC message PROGRESS

| OP : ALCATEL RO_VPN_DDI_NUMBER (7029)
| [30] Sequence (l=28) Receipt of the VPN nb list
| [80] VPN Local Number (l=5) '32600' - local nb (prefix for ARS)
| [81] VPN DDI Number (l=5) '201432600' - DDI nb (ext. callback translator)
| [aa] Project Data (l=12)
| OP :RO_VPN_DDI_EXTENSION (7017) if VPN over IP, the IP address
| [30] Sequence (l=6) of board GD / INTIP is indicated:
| [80] IP Address (l=4) 0a fd fd 2d 0a fd fd 2d = 10.253.253.45
ISDN message emitted SETUP (on the VPN trunk group)

| IE:[05] EI_IP_INFOS (l=9) -> G723 Ece 1 Vad 0 Profil 2, IPv4 :10.253.253.45.
Call of the IP address received.
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3 Compression type G723, echo
| IE:[18] CHANNEL (l=3) a8 83 81 -> T2 : No B channel cancellation (Ece), no VAD.
| IE:[6c] CALLING_NUMBER (l=1) -> 81 Num :
| IE:[70] CALLED_NUMBER (l=6) -> 81 Num : 32600 Call the VPN nb received (voice)
ABC message emitted FACILITY

| OP: ALCATEL RO_VPN_SYNCHRO (7037) Timer started (30 sec)

ISDN messages were cut in order to keep only significant elements.

284
VPN Overflow
vpnstat command
vpnstat command
(1)xa000001> vpnstat -g 11
+------------------------------------------------------------------------------+
| E Q P T S T A T E Link number : 11 Name : T2 IP |
| Nb of Acc. : 1 Nb ts : 30 |
| |
| Neqt : 445 446 447 448 449 450 451 452 453 454 455 456 |
| State : na OVO . . . . . . . . . . |
| |
| Neqt : 457 458 459 460 461 462 463 464 465 466 467 468 |
| State : . . . . . . . . . . . . |
| |
| Neqt : 469 470 471 472 473 474 475 476 477 478 479 480 |
| State : . . . . . . . na . . . . |
| |
| Neqt : 481 482 483 484 485 486 487 488 489 490 491 492 |
| State : . . . . . . . . . . . . |
| |
| Neqt : 493 494 495 496 497 498 499 500 501 502 503 504 |
| State : . . . . . . . . . . . . |
| |
| Neqt : 505 506 507 508 |
| State : . . . . |
| <0> Quit <H> Help |
+------------------------------------------------------------------------------+

Vpnstat command:
use: > vpnstat [-r | -g | -c] <Trunk_group_nbr of a link>
Trunk_group_nbr: Trunk group number (2000 - 2099)
-r trk_grp : Refresh periodically the screen
-g trk_grp : Graphic mode (VT100 required)
-c <trk_grp> : display of the VPN calls on the node (text mode)
-d <Ext Numb> : display of the VPN calls for a set number on the node (text mode)
The calls are represented with

•OVO (Overflow outgoing): outgoing VPN calls
•OVI (Overflow incoming): incoming VPN calls

285
VPN Overflow
System messages
System messages linked to VPN overflow
➨ 4100 Inconsistency of VPN node list
➨ 4102 Lack of VPN resources
➨ 4103 Incoming VPN call aborted
➨ 4104 Outgoing VPN call aborted
➨ 4105 VPN call failed due to lack of time-slots
➨ 4108 VPN call failed in a remote node


286
VPN Overflow
To delete a VPN hop
VPN hop deletion
➨ Deactivate X25 access cluster linked to trunk groups
➨ Remove supervised by routing on trunk groups
➨ Delete the VPN hop
➨ You can possibly remove:
▼ Trunk groups
▼ VPN prefixes
▼ ARS management
▼ VPN service in the system parameters
➨ The hop will disappear from routing only after a shutdown

This management must be done in agreement on all the nodes of the network concerned.
Broadcast must be operational so all the deletions will be echoed in the network.

287
VPN Overflow
To delete a VPN hop
VPN hop deletion(next)
➨ Disable a X25 cluster access
▼ / Trunk groups / Trunk group / X25 Synchronization
✦ X25 Cluster access + Disable
or
▼ / X25 / X25 Access Cluster / Review-Modify
✦ Operational + NO
➨ Delete supervision by routing
▼ / Trunk groups / Trunk group / Review-Modify
✦ Supervised by Routing + NO

In the OmniVista 4760 or 4760i application, the field X25 Synchronization is available under tab Action.
It’s better to use X25 Synchronization in the management field of the trunk groups, it avoids to deactivate another access cluster by
mistake.
Once you’ve remove supervised by routing, it’ll automatically delete the related X25 cluster access.

288
VPN overflow
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to set up the VPN overflow
MANAGEMENT
1 Topology of the network:
Vpn hop A-B
Node A Node B
Public
Operator
IP
Network
Vpn hop A-C Node C
Vpn hop B-C

NodeA,B,C =Node1,2,3
or
NodeA,B,C =Node4,5,6

289
VPN overflow
2 On each node of the network:

2.1 Manage the T2 trunk group (or T0 trunk group) for VPN overflow in the remote network
14. Put the VPN TS % to 100% for the Lab.
2.2 Manage the local VPN prefix 3X099
2.3 Manage the ARS table N° 4X for VPN (X: Node number). For this Lab, it is not useful to
create one ARS table per remote node as the public dialing is the same for the whole
classroom.
2.4 Manage a VPN hop between your node and the two remote nodes.
Be careful: le VPN overflow must be named “X-Y” where X is lower than Y.
2.5 Manage a VPN hop between node A and Node C
2.6 Manage the appropriate access categories to authorize the overflow.
2.7 Allow the system to use the VPN facility
2.8 Check the management by using lookvpn –test command
2.9 Manage the routing prefix to test the calls between nodes
2.10 Wait until the broadcast of the VPN prefixes of the other nodes
2.11 Modify the received prefixes. They must use the ARS table 4X.
2.12 Check the global management by using lookvpn –test command
2.13 Check the VPN resources by using the suproutage command

290
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
291
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
292
Executive / Assistant group in ABC-F network

OBJECTIVES:
◆ To describe the executive / assistant feature in ABC network
◆ To describe restrictions linked to the screening and network supervision
Alcatel OmniPCX Enterprise – Executive / Assistant group in network

293
Executive / Assistant group in network
Overview
Multi-lines features available in network :
➨ Set supervision
➨ Executive / Assistant group in network
Restrictions :
➨ Overflow assistant must be located on the same node as the
manager’s set
➨ No discreet listening
➨ Feature not recommended with on demand links
▼ The link will be established each time the status of the sets changes
it results expensive costs of communications


294
Overview
Exchanges between sets
ABC Link
N1 D N2
Manager’s set Assistant’s set
31000 32000
31000 31000 32000 32000
X25 exchanges
Assistant Screening Manager
A31000
Call Key Call
Supervision Supervision Screening

A31000
32500 32785 Supervision

The creation of an executive / assistant group in network is done the same way as it was in stand alone configuration (except for the
overflow assistant). The number A31000 is the second directory number assigned to the assistant’s set associated to the filtering of set
31000.
Sets’ supervision in network is done via the X25 exchanges using the PLL of the ABC link.
Sets supervision data are broadcasted over the network to update the databases (broadcast application must be operational).
In that kind of configuration, X25 exchanges are frequent (each time the status of a supervised or filtered set changes). Though it’s
mandatory to have a permanent link between concerned nodes.
The routing type doesn’t matter (dynamic or static).

295
Reminder
Multi-line sets supervision
➨ Impossible to contact
▼ All lines are busy
Key Icon
➨ Partially busy
▼ At least one line is free
Key Icon

Set supervision behave the same way in ABC network as in stand alone configuration.

296

OBJECTIVE:
◆ To maintain filtering coherency of executive / assistant group in network
Alcatel OmniPCX Enterprise – Executive / Assistant in network

297
Maintenance
It’s possible to perform an audit concerning the multi-line

sets’ data
➨ audit command
▼ Choose item Progr. Keys
▼ Choose item Supervision key
Principles
➨ Using this command retrieves the list of all supervising /
supervised sets in the network
➨ Analysis of the local tables’ data

▼ Correction of the local errors during the reference building
▼ Correction of the distant errors during the reference downloading

Reminder :
It’s way far safer to perform a simulation of the construction and downloading of the reference before launching an audit.
Principles :
•Reference building on the local node :
•Retrieval of all supervised sets by the local node and all supervised sets on local node.
•Data analysis :
•If supervising set is local and the supervision key of a distant set doesn’t exists then :
•Suppression of the supervision feature of the distant set during the reference building
•If supervising set is distant and supervised set is local but not in supervisions’ tables then :
•Insertion of supervising set in the local table
•Downloading of the reference over the network
•Errors concerning sets belonging to the reference node will be erased from the supervisions’ tables
Coherency of supervision and filtering data is linked and managed by the broadcast application.
Broadcast has to be operational, as well as the IP/X25 tunnel for the LOG files exchange.
prog_diff command may be used to check the content of the error files generated by broadcast application.
multitool command can list the local filtering groups.

With multitool REPAIR it’s possible to “repair” supervision keys locally (only).
Alcatel OmniPCX Enterprise – Executive / Assistant in network

298

OBJECTIVE:
◆ To manage the executive / assistant feature in ABC network

Ref. ENTP0407C03TEUS Issue 01
299
Executive/Assistant Group in Network
Management
Executive/Assistant group in Network:
➨ Same management procedure than the one used in stand

alone
➨ Conditions for a good working:
▼ Tunnel IP/X25 in service

▼ Broadcast application has to be started

Remark:
- Broadcast application 1st start : The cleanbroad command can be used to activate the broadcast on the local node or on the
complete network
- Broadcast Stop / Start: /System/Broadcast
➥Operational: No/Yes
or use the maintenance command: mao -br: stop

mao +br: start

300
Executive/Assistant Group in Network
Management
Executive/Assistant group in Network:
➨ Management reminder - Executive/Assistant group creation

on the executive extension:
▼ /Users/Progr. Keys:
✦ Key No.:
✦ Function: Assistant call
✦ Directory number: Assistant directory number
✦ Key number: Free key on Assistant extension (executive call)
▼ Executive and Assistant extensions must be multiline.

Key Number: Enter here a free key number of the Assistant extension. The system will automatically modify this programmable key
on the Assistant extension to "Executive call".

301
Management
Set supervision in Network:
➨ On the supervising extension:

▼ /Users/Progr. keys:
✦ Key No.:
✦ Function: Set supervision
✦ Directory number: Supervised extension directory number
➨ List of the supervised and supervising extensions:

▼ /Specific telephone services/Supervised user:
✦ Directory number:
✦ Supervisor list:

Reminder: A supervising extension must be multiline first of all.
Remark: It is possible to perform an audit on the network supervision keys.

302
Executive /Assistant group in network
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the Executive / Assistant groups in network
MANAGEMENT
1. Set up the following configuration:
3A000 3B003
Boss extension Secretary extension

NodeB
3A003 3B000
NodeA
NodeC
Secretary extension Boss extension
3C000 3C003

303
Executive /Assistant group in network
3x000 3x000 3x003 3x950

Secretary call Executive call
3x900
Screening Screening Screening supervision
Unscreening Unscreening Screening supervision
Screening and Unscreening programmable keys

Key 5 (Screening) : All external calls
Key 6 (Screening) : All internal calls
Key 7 (Unscreening) : Extension 3x010 only
Key 8 (Unscreening) : Extension 3x002 only
2. Do some tests to verify your management
3. Manage an overflow Assistant for each Executive. Where should it be located?

304
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
305
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
306
Centralized Alcatel OmniMessage 4645

OBJECTIVE:
◆ To describe the principles of centralized voice mail in ABC network
Alcatel OmniPCX Enterprise – Centralized Alcatel OmniMessage 4645

307
Overview
Centralized voice mail allows:
➨ To lower the number of installed voice mail
▼ Reduce the cost of the installation
▼ Easy maintenance
➨ To offer to the user the same level of services as a local

voice mail would do
Network resources are used for:

➨ Mailboxes creation, modification (ABC Protocol)
➨ Messages notification (ABC Protocol)
➨ Messages consultation (B channel / VPN hop)

Voice mail 4645 offers 8 or 16 simultaneous accesses, 40 hours of recording and up to 1000 mailboxes.
4645 is available for CPU-CS or CPU-AS.

308
Principles
Topology
BDD
31000
32000
33000 Alcatel OmniPCX
Enterprise
Node 1 + 4645 Call Server
Node 3
ABC-F Links
31000 33000
Node 2
32000

ABC-F network can be composed either with classical ABC links or hybrid links.
Connections to the voice mail are made through the ABC network, the public network or the IP network (LAN).

309
Principles
Message notification
BDD
Msg
for
32000 Alcatel OmniPCX
Enterprise
Node 1 + 4645 Call Server
Extension 33000 leaves a message for 32000

Node 3
ABC-F Links
31000 33000
Node 2
Notification
32000

The recording of a message uses a B channel provided by the ABC-F network.

When a message is recorded in the voice mail, the 4645 uses the ABC-F2 protocol to notify the set on its node.
The light blinks or the set rings to alert the mailbox owner (same as stand alone configuration).

310

OBJECTIVE:
◆ To maintain centralized voice mail
Alcatel OmniPCX Enterprise –Centralized Alcatel OmniMessage 4645

311
Management control
Broadcast must be operational
Check network prefix associated to the voice mail

➨ Network & node numbers must be correct
➨ Prefix type must be Voice Mail
+-Review/Modify: Prefix Plan----------------------------------------------+

| |
| Node Number (reserved) : 102 |
| Instance (reserved) : 1 |
| Number : 31645 |
| |
| Prefix Meaning + Network No. |
| Network Number : 1 |
| Node Number/ABC-F Trunk Group: 1 |
| Number with subaddress(ISDN) + Non |
| Type + Voice Mail |
| Identifier : 121 |
| |
+-------------------------------------------------------------------------+

In case of database migration, check that the type of the network prefix used to call the voice mail is Voice Mail.

312
Checking the mail boxes in the voice mail
Eva_tool command offers the possibility to list all mail

boxes, even mailboxes of ABC network sets
➨ Choice 5 (List of nodes, mailboxes & messages)
➨ Choice 1 (List of mailboxes & nodes)
EVA_TOOL : DumpMailboxList
EVA_TOOL : number of mailboxes 5 of 1000
EVA_TOOL : Nb MCDU TYPE NAME
EVA_TOOL : 0 | 00 | 6 | Administration Mailbox
EVA_TOOL : 1 | 01 | 4 | Default Automated Attendant
EVA_TOOL : 2 | 31101 | 1 | Gorgeous Paul
EVA_TOOL : 3 | 32000 | 1 | Spring Michael Those sets are network
EVA_TOOL : 4 | 32100 | 1 | Burns Montgomery numbers toward node 2
EVA_TOOL : Dumpnetworkmailboxes
EVA_TOOL : number of network mailboxes 0 of 50000
EVA_TOOL : Nb MCDU VM_NODE_NUMBER NAME
EVA_TOOL : Dumpnetworknode
EVA_TOOL : number of network nodes 0 of 500
EVA_TOOL : Nb MCDU TYPE NAME

The presence of mailboxes associated to network numbers indicates that the creation was successful.

313
Audit mail boxes
audit command gives the possibility to update voice mail

holders in the network
Selection of objects
0 - Exit
5 Entities 6 Call Distribution tables
7 DDI Translation 8 Voice mail titulars
9 * Voice Mail Dir.No. 10 * VPN Overflow
11 Free Numbers Ranges List 12 PIN (Personal Ident.No.)
13 Suffix Plan 14 * Classes of Service
15 * Access COS 16 * Phone Features Classes
17 * Project account code 18 * Cost Center
19 Tones 20 * Timers
21 * Security and Access Control 22 Hunt Group
23 Progr.Keys 24 * Flow Control
25 * Input Configuration 26 * Output Configuration
27 * Data menu: Logon 28 * Set-up
29 * V120 30 * X25 Packet Handler
31 PSPDN Complementary Address De 32 X25 Command
33 * Appli Rights 34 Entity Spd Dial Numbers

Choices 8 and 9 can be used to create in the 4645 voice mail the mailboxes associated to sets in the network, and also to correctly
create the network prefix for the voice mail.

314
OmniMessage 4645 voicemail in network
PROCEDURE
OBJECTIVE
- To learn how to configure the centralization of an Alcatel OmniMessage 4645 in an ABC-F
network
REFERENCE
- System Documentation CD-ROM: /Technical documentation / Voicemail systems / Centralized
voicemails
OVERVIEW
Example of centralization of an OmniMessage 4645 located on node 1
Node 1 Node 2
Set 31000 (4035) Set 32000 (4035)

Set 31010 (Z) Set 32010 (Z)

315
PROCEDURE
1. Checking of the broadcast activity between nodes

Application mgr
Path System parameters / Broadcast
On node 1 On node 2
Operational Yes Yes
Action CTRL+V
Note: Do not forget to check the ABC network state via suproutage. This one must be in service to
get the voicemail centralization running.
2. Creation of the voicemail on node 1

Application mgr
Path Applications / Voicemail
Voicemail Directory 31645
number
Directory name Mevo
Voicemail type 4645
Action CTRL+V
Voicemail CPU xa001001
Action CTRL+V
Note: Voicemail directory number : A free DID/NDID of the dialing plan. The broadcast
service will create network prefixes corresponding to the voicemail on the other nodes..
Note: Voicemail type : In this example, we use an OmniMessage 4645. The principle is the
same for an Alcatel OmniMessage 4645.
Note: Voicemail CPU: With the OmniMessage 4645,enter the name or the IP address of the
CPU where the voicemail is configured. This name or address must be part of the host file of
the CPU. In this example, the voicemail is located on node 1.

316
3. Checking of the creation of the network prefix on node 2

Application mgr
Number 31645
Action CTRL+V
Prefix meaning Network No
Node No 1
ABC-F trunk group No / 1
Node No
Type Voicemail
Action CTRL+V
Note: If the prefix has not been created, check the parameters of the broadcast and / or use the
functionality Immediate broadcast to accelerate information transfer. The type of the prefix
must be voicemail.
4. Allocation of mailboxes to the users

Application mgr
Path Users
On node 1 On node 2
Directory number 31000 32000
Voicemail dir. number 31645 31645
Action CTRL+V
Note: The creation of the mailbox of the user 32000 on the voicemail located on node 1 will be
done during the broadcast between nodes. You can still use Immediate broadcast
functionality to accelerate the process.

317

318
Centralized Alcatel 4645
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to put the Alcatel 4645 centralized voice mail system into operation
MANAGEMENT
1. Check that the broadcast facility is activated on all the nodes of the network
2. The Alcatel 4645 will be installed on nodes 1 and 4
3. On nodes 1 and 4, manage the voice mail parameters:

/ Applications / Voice mail:
- Directory number: 3x777
- Name: VM_NTWK
- Voicemail type: 4645
- Voice mail CPU name : xa000001 or xa000004
4. Operate a shutdown on nodes 1 and 4
5. Check that the voicemail directory number is known on all the nodes of the same subnetwork.
6. On each node allocate a mailbox to two extensions.
7. Check that the mailbox has been created.

319
Centralized Alcatel 4645
8. If the set does not answer, the calls have to overflow to its mailbox.
8.1 Check the telephone facilities category of this user.
8.2 Manage the following items in this category (last data in the category ) :
- Default overflow type: Forward on no reply
- Default overflow address: Voice mail
8.3 Check that operation is correct.

320
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
321
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
322
System messages centralization

OBJECTIVE:
◆ To describe the principles of system messages centralization
Alcatel OmniPCX Enterprise – System centralization messages

323
Overview
Within the ABC network the system messages

centralization give the possibility :
➨ To put together all important messages on one node
▼ Use of the incident filter
➨ To facilitate the network supervision
▼ All important messages are recorded on the same node
➨ To lower the number of direct IP connections
▼ Network supervision by using the OmniVista 4760 application
System messages centralization uses the IP/X25 tunnel

available on all kind of ABC-F link

System messages centralization is always done toward one node the “master node”.
The incident filters are used for the purpose that they send to the master node only the most important messages.
When the network topology doesn’t allow a direct IP connection between the OmniVista 4760 and the distant nodes, the IP/X25
tunnel can ensure the management and the recovery of the system messages toward the centralizing node (master node).

324
Principles
Centralization on one network node
Loss of a
coupler
Hard (Node 3)
Disk
Incident
4104 (N2)
Alcatel OmniPCX
Alcatel OmniPCX
Enterprise
Enterprise
Call Server
Call Server
Network 0 Network 0
Node 1 Node 3
ABC-F links
Network 0 Incident Filter

Node 2
Incidents
Incident Filter

System messages centralization on one node of the network:

The network incidents are centralized on the master node (in that case node 1).
The incidents are filtered locally and notified through the IP/X25 tunnel toward the master node.
The incidents can be (according to the configuration of the incident filter) stocked in the local messages (viewable by incinfo) and/or
displayed on the screen.

325
Principles
Centralization on one node using OmniVista 4760
ACB-F network
Filter
Filter
N1 N2
Filter
N3
LAN
Alarm
4760 Application

In this example, the OmniVista 4760 application is connected via IP to one network node.
All system messages of other nodes are filtered and centralized toward node 1 (master node).
The Alarm application of the 4760 displays in real time the messages from all nodes of the network.

326

OBJECTIVE:
◆ To manage the system messages centralization
Alcatel OmniPCX Enterprise – System messages centralization

327
Overview
Centralization around a network node
➨ It is possible to centralize some incidents in a network

Master node
Node 1
Node 3 Node 2
Network
Incident Filter Incident Filter
Faults

Centralized incident on a network node

Network incident is centralized on the master node.
Faults are notified via the IP/X25 tunnel.
At each node, a filter lets you choose the network faults to be handled by the centralized system.

328
Management
Node 1 management
➨ Management tool
▼ /Applications/Incident manager/Supervised node/create

Create: Supervised Node
Node Number (reserved) : 1

Instance (reserved) : 1
Supervised id
Network Number : 1
Node Number : 2
Associated Timer : 86400

Establish connection Counter : 3
Establishment Timer : 5


329
Management
Node 2 management
➨ It is necessary on this node to manage the filter per

centralized incident
➨ In the following example the incident 2042 (coupler lost) will

be centralized
➨ Management tool
▼ /Applications/Incident manager/Incident filter/create


330
Management
Node 2 management (continued)
Create: Incident Filter
Filter id
Incident Number : 2042

Network Number : -1
Node Number : -1
ACT shelf Number : -1
Coupler Number : -1
Behind Us : -1
Set Address : -1
Rma Action + None

Alarm Action + None
Table Id : 0
Screen Display + YES
Disk Storage + NO
Network Incident + YES
SNMP Incident + NO


331

332
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to put system messages centralization into service
MANAGEMENT
1. Node 1 or 4 will be the centralized node for the incidents.
2. On nodes 2, 3, 5 and 6, manage the 2042 incident so that this incident will be centralized
and shown on node 1 or 4.
3. Reset the UAI8 coupler and check the display on node 1 and 4.

333

334
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
335
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
336
DECT mobility in ABC-F network

OBJECTIVES:
◆ To describe principles of network mobility in ABC-F network
◆ To describe transmitted data
Alcatel OmniPCX Enterprise – DECT mobility in ABC-F network

337
DECT mobility in network
Overview
Network mobility can be used on all the nodes of the ABC-

F network
A DECT user in visited node keep:
➨ Its DECT directory extension number
➨ The “Basic User Profile" characteristics
▼ Identification in phonebook, cost center, classes of services
▼ Set phonebook, supervisions, screening, twinset, etc…
This facility (licenses requirements) is completely

transparent for users

DECT mobility in network can’t enable to keep calls established moving from one node to another one (this feature is called Campus
mobility).
Software license allowing DECT mobility in network is controlled by ops license n° 90.
A sufficient number of DECT set licenses must be available to welcome moving sets from other nodes.

338
Overview
DECT mobility requires:
➨ An operational ABC-F network
➨ A DECT infrastructure on concerned nodes
➨ Mobile sets liable to use the feature
▼ All Alcatel sets 4072,4074, Mobile 100/200
➨ Fictitious sets available on visited nodes
▼ These sets are called empty shells
➨ The corresponding OPS licenses on concerned nodes

Public network and phone facility classes of service must be the same on all the nodes of the network.
Otherwise, it’s likely that the visitor set will not be able to use its phone correctly.
The fictitious set or empty shell is entered in DECT users licenses of the system.
The sets with network mobility right are entered in mobility license N°90.

339
Overview
Two numbers are used to identify the DECT set:
➨ IPUIN number
➨ IPUIO number
▼ 22 digits number allowing to retrieve the home directory number

during registration
▼ Systematic use of IPUIO number if defined
PARK number in the set must be compatible with PARI

installation numbers
➨ Coherent PARI numbers in the network
➨ PLI management

IPUIN : International Portable User Identity type N: Number identifying the handset. Number fixed in the memory of the set (14
figures in octal)
IPUIO : International Portable User Identity type O. Number identifying the handset in case of roaming in a PABX network. N°
managed automatically in the handset at the registration of the home node. 22 figures in octal. Number calculated from the handset
directory number
PARI : Primary Access Right Identifier: Number identifying the PABX. N° programmed in the PABX. 31 bits coded in 11 octal digits
PARK : Primary Access Right Key: Number allowing the set to recognize the PABX
PLI : Park Length Identifier

Number of significant bits in a PARI number (Allow a set to use different PARI)

340
PLI management
Configuration example
Alcatel OmniPCX
Enterprise
Call Server
ABC-F link
Node 1 Node 2
1 Conversion in binary of PARI numbers

Node 1 : 001 000 000 000 000 100 000 000 010 111 000
Node 2 : 001 000 000 000 000 100 000 000 110 111 000
PARI PARI
10000400270 10000400670
2 Search of identical bits for the PLI
Node 1 : 001 000 000 000 000 100 000 000 010 111 000
Node 2 : 001 000 000 000 000 100 000 000 110 111 000
PARK 3 The 24 first bits are the same

10000400270
PLI = 31 With a PLI to 31, the set can’t be recognized on node 2
PLI = 24
With a PLI to 24, the set can be recognized on both nodes

A PARI number contains 11 digits in octal (33 bytes).

The last 2 bytes are always 0, so the last octet can only be 0 or 4.
Conversion octal / binaries:

0 : 000 1 : 001
2 : 010 3 : 011
4 : 100 5 : 101
6 : 110 7 : 111

341
DECT set registration
Alcatel OmniPCX
Enterprise
Call Server
ABC-F link
Local Visited
node Mobility rights for 31000 ? Node
ABC-F2 protocol
O
UI
IP
User 31000 User 31000

Name, entity Name, entity
cost center, Moving to other node cost center,
etc... etc...
Fictitious
Users

Registration on visited node:

•The visitor set can be identified with IPUIO
•IPUIO is translated into directory number by visited node, which corresponds to a network prefix to the local node.
•Via ABC-F2 protocol, the visited node ask local node to check the mobility rights of the set.
•If rights are correct, an available empty shell is given to the DECT set.
•The directory number of the DECT set is sent automatically to the empty shell.
•Set parameters are retrieved by the link via ABC-F2 protocol.
Transfer of set characteristics:

•Identification (name, password).
•Rights (forwarding, teleservices, categories (COS), supplementary services).
•Services (charging indicators/advice of charge, set features).
•Destination numbers (for forwarding, for overflow).
Additional information is added, comprising:

•Entity number.
•For set programmable keys:
•Language ID.
•Key type.
•Associate number.
•Cost center. •Key content.
•Charging COS, Public network access COS, Features COS, Connection COS. •The content of the entries in the set directory (phone book).
•ISDN supplementary services, validated or not.
•Called number masking in the accounting record(charging ticket).
•Emergency call.
•Dial (Call) by name/text message authorized or not.
•UUS access code.
•Ringing and audio parameters.
•DECT paging overflow parameters.

342
DECT/PWT Configuration in ABC Network
PROCEDURE
OBJECTIVE
- To learn how to manage IBS and RBS installations in ABC-F network and to install mobile
100/200
REFERENCE
OmniMobility / DECT
OVERVIEW
The purpose of this procedure is to explain you how to put in service a DECT/PWT configuration in
network (IBS or/and RBS).
The first step is to manage the PARI number (IBS or RBS), to manage the hardware (boards, base
stations) and to know the way for the installation of the DECT/PWT sets.

343
PROCEDURE
1. DECT management on nodes 1 & 2 (IBS)

Application mgr
Path /DECT System
Action Consult / Modify
On node 1 On node 2
Base station type + IBS + IBS
PLI for CTM 28 (value to be calculated) 28 (value to be calculated)
Action CTRL-V
Path / DECT System / IBS Parameters
On node 1 On node 2
PARI value 10000401010 10000401020
Action CTRL-V
Path /Shelves
Action Consultation / Modification
On node 1 On node 2
Shelf address 0 or 1 according to hardware 0 or 1 according to hardware
PARI No Pari IBS Pari IBS
Action CTRL-V
Path /Shelves/ Carte/ IBS
Action Create
On node 1 On node 2
Shelf address 0 or 1 according to hardware 0 or 1 according to hardware
Board address 3 (UA or UAI board position) 3 (UA or UAI board position)
Equipment address 2 (even position of a free 2 (even position of a free
equipment) equipment)
Line delay + Short line + Shot line
Number of UA links 1 or 2 (check cabling) 1 or 2 (check cabling)
Action CTRL-V

344
2. DECT management on nodes 1 & 2 (RBS)

Application mgr
Path / DECT system
On node 1 On node 2
Base station type + RBS + RBS
PLI for CTM 28 (value to be calculated) 28 (value to be calculated)
Multi ACT
Handover / DTM + 0ui + 0ui
synchro
Action CTRL-V
Synchro DECT ACT 0 0
shelf number
Action CTRL-V
Patch / DECT system / RBS Parameters / PARI
Action Create
On node 1 On node 2
Pari No 0 0
PARI value 10000401010 10000401020
Action CTRL-V
Path /Shelves
On node 1 On node 2
Shelf address 0 0
Pari No Pari 0 Pari
Action CTRL-V
Path / Shelf / Board
Action Create
On node 1 On node 2
Shelf address 0 0
Board address 8 8
Interface type DECT8 DECT8
Action CTRL-V
Board with DTM + Yes + Yes

345
Action CTRL-V
Path / Shelf / Board / DECT RFP
On node 1 On node 2
Shelf address 0 0
Board address 8 8
Action CTRL-V
Base station place Corridor Building A
Administrative state RFP_INS RFP_INS
Operational state RFP_OOS RFP_OOS
Action CTRL-V
Note: Administrative state / operational state :These parameters allow to modify the state
(administrative) or to display the state (operational state) of a RBS.
3 different states :
RFP_OOS : Borne Out Of Service
RFP_INS : base station in service
RFP_FROZEN : Base station in service but it will switch to out of service (maintenance
purpose) when the last communication will be released.

346
3. DECT/PWT users management
3.1 Users creation

Application mgr
Path /Users
Action Create
On node 1 On node 2
Name DECT DECT
First name Node 1 Node 2
Shelf address: 255 255
Board address 255 255
Equipment address 255 255
Type of set GAP+ GAP+
Action CTRL-V
Path /Users / DECT set
On node 1 On node 2
Network mobility True True
Action CTRL-V
Note: Network mobility : This parameter allows to authorize the DECT/PWT set to register itself
on remote nodes.

347
3.1.1 Empty shells management

Application mgr
Path /Users
Action Create
On node 1 On node 2
Directory number C31900 C32900
Name Shell Shell
First name No 1 No 2
Shelf address 255 255
Board address 255 255
Equipment address 255 255
Type of set 4074/Shell 4074/Shell
Action CTRL-V
Path /Users / DECT set
On node 1 On node 2
Directory number C31900 C32900
Empty shell True True
Action CTRL-V
Note: Type of set : It must be 4074 to be able to create an empty shell(even if Mobile 100/200
or PWT sets will use this empty shell).
Empty shells do not have the network mobility right.

348
4. DECT/PWT sets installation
4.1 On-air registration launching on the Call Server

Application dectinston –g (via mtcl)
Result Choice of a specific base station (Y/N - default is N) ?
Action N (or Return)

Result GAP characteristics
_______________________________________________________
Directory Number : 31020
User's name : DECT Noeud 1
MAO type : GAP+
Dect parameters used.
PARI : 10000401010
PLI : 28
_______________________________________________________
Do you agree to install this set. (Y/N - default is Y) ?
Action Y (or Return)
Result Start the registration on the handset.
Wait until the set rings, but you don't have to hang up !!!
Action Launch the registration on the set (see next)
Result _______________________________________________________
Installation succeed.
Effective Security Level : No Security
_______________________________________________________
Installation of a handset ?
No -> 0
With automatic choice of a GAP dir. number -> 1
With the choice of a directory number -> 2
(default 0) ==>
Remark When the message “Installation succeed” is displayed, the
registration is successful
Remark After the installation, several choices:
- 0 : exit
- 1 : To launch the registration of an other set (Message: Subscription
Running… on the screen),. The system selects automatically the
directory number
- 2 : To launch the registration of an other set (Message: Subscription
Running… on the screen. You select the directory number.

349
4.2 On-air registration launching on the handset

Mobiles 100/200/200ex
Remark If the set has never been registered, you access to the installation menu
directly when switching on the set. Otherwise, you must the procedure
detailed below.
Action Switch on the set by pressing simultaneously the keys “ON/OFF” and
calls management (colored keys)
Action Select: 4.EEPROM Reset then OK
Result SYSTEM 1
Auto install ?
Action OK
Result Launch Subscription?
Action OK
Result SYSTEM 1
Subscription Running…
Remark The set rings and on the screen the directory number is displayed if the
installation succeeded.

350
DECT mobility in ABC-F network

OBJECTIVE:
◆ To maintain the network mobility feature

351
Elements required for network mobility
ABC-F network and broadcast must be operational

DECT sets and empty shells must be known as network
prefixes on other nodes
DECT licenses must be well configured according to the

management
The PLI value must be the same on all the nodes at allow a
correct registration on the other nodes
Check the DECT sets management

➨ Set type
➨ Network mobility rights
➨ Empty shells

DECT sets must have these parameters:

• for empty shells:
•Set type = 4074/Shell
•Right to network mobility = NO
•Empty shell = YES
•For DECT set:
•Set type = according to real type
•Right to network mobility = YES
•Empty shell = NO

352
Display of DECT information on a set
➨ Command dectsets s ‘Set N°
▼ Allow to retrieve shell number given to the set
➨ Command dectsets v
▼ Display detailed data of all the sets
Display exchanges between nodes
➨ Set parameters transmitted via ABC-F
➨ ISDN trace on ABC-F link allow to view transmitted data


353
Release of shells
➨ Shells unused for 24 hours are released automatically

above a threshold
▼ By default the threshold is 50 % of the number of unused shells
▼ The value can be modified in DECT parameters:
✦ Max % of full unused shells
➨ Shells are released as soon as the associated DECT set is

connected to another node
➨ A command can be used to release the shell
▼ Command dectclean ‘set N’


354
DECT/PWT Mobility
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to put the DECT/PWT mobility in network into service
MANAGEMENT
1. Manage the DECT/PWT parameters of your system according to the following requirements:
/ DECT system:
- Radio base type: IBS
- PLI for CTM: Calculate the PLI according to the network’s PARI numbers
- Station base type: DECT
/ DECT System / IBS System:
- Pari value: 100004SCNN0 with SC = classroom number and N = node number
- Area type: 1 area of 256 IBS
/ Shelf:
- Shelf number: 1
- Pari number: Pari IBS
2. On each node, create on an UA or UAI equipment N an IBS connection using one UA link.
3. On each node, create two DECT subscribers with the following parameters:
/ Users:
- Directory number: 3x030 and 3x031
- Directory name: DECT One and DECT Two
- Shelf address: 255
- Board address: 255
- Equipment address: 255
- Type of set: GAP+

355
DECT/PWT Mobility
4. All the DECT subscribers will have the correct network mobility. ( / Users / DECT set).
5. On each node, create 2 empty shells used to welcome DECT roamers:

/ Users:
- Directory number: 3x060 to 3x063
- Directory name:
- Shelf address: 255
- Board address: 255
- Equipment address: 255
- Type of set: 4074
/ Users / DECT set:
- Shell: Yes
6. To make your tests, disconnect the base stations of two nodes of the same subnetwork and
check that all the DECT subscribers can still work on the last IBS.

356
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
357
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
358
Hunt groups in ABC-F network

OBJECTIVE:
◆ To describe hunt groups in network
Alcatel OmniPCX Enterprise – Hunt groups in network

359
Hunt group in ABC-
ABC-F network
Overview
Available features :
➨ Sets can belong to different nodes
➨ Local call routing if network unavailable
➨ Call pick up possible in network as well as in local
➨ DECT and multi-lines sets allowed
Restrictions :
➨ No parallel hunt group in network
➨ 200 groups of 40 sets maximum per node
▼ All type of hunt group (ACD, RSVP, S0, local, network)

A network hunt group always belongs to a « Reference node ». It means that the sets allocation can only be done on this node.
The call pick up is possible for the sets belonging to the group (using prefix Agent processing group call pickup) and also for the
sets external to the group (using prefix Group call pickup).
Only cyclical and sequential search types are possible in a network hunt group.
A set belongs to one group only.
The user’s public access COS can be kept, even if the user enters a hunt group.

360
Hunt group in network
Example
Hunt group in network, example

Node 1 Node 2 Node 3
Directory nb : 31100 Directory nb : 31100 Directory nb : 31100
Search type : Cyclical Search type : Cyclical Search type : Cyclical
Type : Network Type : Network Type : Network
Node reference : 1 Node reference : 1 Node reference : 1
Numbers allocated : Numbers allocated : Numbers allocated :
•31000 (local) •32000 (local) •33000 (local)
•32000 (network prefix)
Network 0 Network 0
Node 1 Node 3
Broadcast
Bro
ad
ca st
Network 0
Node 2
Creation of
network
group 31100

The creation of a network hunt group on node 1 will lead to the creation of this group on other nodes via broadcast.
Les numéros affectés peuvent être locaux ou réseaux.
Reference node indicates which node handles the call routing.

361
Hunt group in network
Example
Description of a call toward a hunt group

Node 1
Directory nb : 31100
Search type : Cyclical
Type : Network
Node reference : 1
Numbers allocated :
•31000 (local)
Network 0 Network 0
Node 1 Node 3
1 3
calling
Network 0 31100
Node 2

A set on node 3 dials 31100. This number is a network prefix to node 1 and correspond to a network hunt group.
Search type is cyclical, first call is for extension 31000 on node 1.
If the set doesn’t answer, the call is routed toward the second extension 32000.
And if extension 32000 doesn’t answer then 33000 is rung.
All features are available (overflow, % waiting queue, call pick up, etc…).
If node 3 is isolated from the network at the time the group is called, then the call is routed locally, if sets are available… in this
example it means that extension 33000 will be rung.

362
Hunt groups management in network
PROCEDURE
OBJECTIVE
- To learn how to manage a hunt group in network
REFERENCE
- System Documentation CD-ROM: Custom System Documentation / Technical documentation/
User Services -> Hunt Groups
OVERVIEW
A Hunt group is a method of assigning the same directory number to more than one phone set from
the network. There are two types of searches that are used to define how the group will respond to
calls.
In this procedure you will create a hunt group that will search the group of sets in a cyclical fashion
(round-robin).
Assign certain users the ability to enter and exit the hunting group.
Set an overflow set for the group (if all sets in the group are busy).
In this example, the hunting group will be created in the network on node 1 and directory numbers
allocated to the group of node 1 and node2.

363
PROCEDURE
Note: One user can belong to only one hunt group.
1. Create a create a hunt group that will search the group of sets in a
cyclical fashion (round-robin) and assign Users of the network to
the PCX Hunt Group:
On mgr
Select Group
Hunt group
Action Create
Entry Directory Number: 31014
Directory Name: Cyclic Group
Type of Hunt Group + Network Hunt Group
Circular Search Type + Circular
Overflow Directory Number: 31020
Dir.No Assigned to the group: 31000,32000
Subnetwork reference : 1
Node reference : 1
Remark:
Type of Hunt Group: Defines the type of Hunt Group (Local Hunt
Group/Network Hunt Group/RSVP Hunt Group)
Search Type: When a station group is called, the search of the station to be
rung is of type: circular or sequential
Dir.No Assigned to the group:
Before to assign 32000 directory number, Check on the reference node
database that this number is present as a network number.
circular: each station is rung in the order given in the list; the system rings the
free station which follows the station previously called.
sequential: the search is made from the station at the head of the hunt group
(the first found to be free rings).
parallel: a parallel grouping is not enable in network.
If a call is sent to an empty hunt group or a busy group with a full waiting
queue, the call is routed to the overflow directory number, if one has been
defined.
The overflow number may be: a local user set, a network user set, another
hunt group, an attendant set.
% authorized camp on calls = (MAX. NUMBER OF CAMP ON CALLS
AUTHORIZED / NUMBER OF ACTIVE STATIONS IN THE HUNTING GROUP) X
100

364
2. Display content of group

On the call server
Login mtcl
Command pbxstat d 31014
Result Usage: pbxstat [-w][d numan][n nu_group][all][sets][menu]

-w ->To display the waiting queue-not relevant for S0 PBX
numan -> Directory number of the Hunting Group
nu_group -> Hunting Group number
all -> To dump all the declared groups
sets -> Display all the sets of the node in a group
menu -> Open a menu to manage groups
** mcduapp 31014 Num Group 0 pbx_type PBX_NETWORK **
ref. Node 1 and ref. network 1
this Node 1 and this network 1
nu_tete 1 mcdu de tete 31000
max_att 50%
idx_acc 255
modcycle CYCLIC
traiatt 0 debor 1
autoret 1 pooccgrp 0 grp_prio 0 abca_blf 0
gnbppgr 1 nbpoeff 1 idx_rasgo 0
grcatptt 2 grctconx 0 set_categ 0 entity_nr 1
idx_mevo 255
mcdudeb 31020
station_grp_name GROP0
PBX_RoutingFlag 0
pickup_no_pbx 0
etat_groupe ABCA_SG_FREE
PBX_preemptable 0
tab_pres[1..40]
Nelgr: nulog local 1 in:31000 etat_poste ABCA_IDLE
Nelgr: nulog index reseau 1 in:32000 etat_poste ABCA_IDLE
Node=2

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

On mgr
Select Translator
Prefix plan
Action Create
Entry Number: 20 (e.g.)
Prefix Meaning + General Features
Station Features + Agent processing group call pickup
Action CTRL+V or F1 to validate the creation
CTRL+C as many times as needed to come back on the main menu
5. Create Prefixes to Exit from the PCX Hunt Group

On mgr
Select Translator
Prefix plan
Action Create
Prefix Meaning + Set features
Station Features + Sta. group exit
Action CTRL+V or F1 to validate the creation
CTRL+C as many times as needed to come back on the main menu

366
6. Create Prefixes to Enter in the PCX Hunt Group:

On mgr
Select Translator
Prefix plan
Action Create
Prefix Meaning + Set features
Station Features + Sta. group entry
Action Press CTRL+V or F1 to validate the creation
Press CTRL+C as many times as needed to come back on the main menu
7. Allow Users 3X00 and 3X01 to Enter and Exit the group and pick
up group call
On mgr
Select users
Entry Directory Number: 31000
Tel. Features COS ID: 0
Remark:
By default, the Tel. Features COS assigned to the phone set is 0.
If you want to validate the right to enter or to exit to group, follow this path
Classes of Service/Phone Features Classes of Service/Review-Modify/CTRL V or
F1/thus change the set features properties to:
Sta. group exit: 1
Sta. group entry: 1
This attribute, validated at 1, enables a set to return or exit to its group
If you want to validate the right to agent group call pick up, follow this path
Classes of Service/Phone Features Classes of Service/Review-Modify/CTRL V or
F1/thus change the general features properties to:
Processing group call pick up: 1
Action Press CTRL+V or F1 to validate your choice
Press CTRL+C as many times as needed to come back on the main menu

367

368
Hunt groups in ABC-F network

OBJECTIVE:
◆ To maintain hunt groups in network
Alcatel OmniPCX Enterprise – Maintenance Hunt groups in network

369
Hunt groups in network
Maintenance
supgpbx command
➨ Resources out of service in the group: group status OOS
➨ Sets non demanded or unreachable: set status NONE
pbxstat d group nb command

(102)xa000000> pbxstat d 32222
***** mcduapp 32222 Num Group 0 pbx_type PBX_NETWORK --
ref. node 2 and ref. network 1
this node 2 and this network 1
nu_tete 1 mcdu de tete : 32000
max_att 50%
*********************
****
*********************
etat_groupe ABCA_SG_FREE
PBX_preemptable 0
tab_pres[1..40]
nelgr: nulog local 1 in:32000 etat_poste ABCA_IDLE
nelgr: nulog local 2 in:32100 etat_poste ABCA_IDLE
nelgr: index reseau 0 in:31100 etat_poste ABCA_IDLE node=1
nelgr: index reseau 1 in:31101 etat_poste ABCA_IDLE node=1

Those commands give all the pieces of information only if they are used on the reference node for the hunt group.
If not, will only be displayed information about local sets.
Remark: the information displayed by pbxstat command is partially complete to be perfectly clear.
Alcatel OmniPCX Enterprise – Maintenance Hunt groups in network

370
Hunting groups in network
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to put the hunting groups in network into service
MANAGEMENT
1. Create the following hunting group in the network on node 1 or 4:

- Directory number 3x014
- Directory name PBX_Node 14
- Type of search: Cyclic
- Directory numbers allocated to the group:
- Alcatel 4020 of node 1 or 4
- Analog extensions of node 2 or 5
2. Create the following hunting group in network on node 2 or 5:

- Directory name: PBX_Node 25
3. Create the following hunting group in network on node 3 or 6:

- Directory name: PBX_Node 36
4. Perform some tests by calling the different hunting groups.

371
Hunting groups in network

372
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
373
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
374
Private to public overflow

OBJECTIVE:
◆ To describe private to public overflow mechanisms

Overflow between nodes
Overflow between ABC sub-networks
Alcatel OmniPCX Enterprise – Public to private overflow

Ref. ENTP0451P01TEFUS Issue 01
375
Overview
Private to public overflow allows to redirect automatically

private calls on public trunks groups if the ABC link is
saturated or out of service
If the VPN overflow service is managed, the system will use

it first in case of ABC link saturation
The private to public overflow is able to translate the

private number of a set into a public number
➨ DID set user DID N°
➨ Non DID set set system N°

The feature public to private overflow ha been modified from R6.1 to allow overflow between IP Media Gateway of a node in case of
IP link saturation (saturated compressors, number of calls authorized in IP domain reached, etc..)
In this case, this facility is called local private to public overflow.
VPN works only if ABS link is operational.

In case of ABC link breakdown, only private to public overflow is possible.

376
Overview
Mechanism
32000
Node 1 DID
ABC link Node 2

31000 2
saturated or
OOS 32200
Non DID
0 : ARS seizure 6a 0101432000
T2
T2 6b 0101432008
32008
Operator
1a Call of 32000 00101432000
Carrier
1b Call of 32200 00101432008
Rights control
3
Phone class of service
Private/Public overflow
Network Acc. Pref. to node 2 :
Number to Add: 0 010143 The same management must be done all over
4 Installation No: 2008 the nodes in network to allow a complete
Translator SDA Node 2 : backup of ABC links by public carrier
Ext / Int : 2000 / 32000
Size : 100
Public access COS

5
Barring

Set 31000 dials 32000

The translator indicates that 32000 is a network number in node 2. X25 routing informs the system that the link is saturated or OOS.
The set 31000 has the right to use the public to private overflow in his COS.
Management on node 1 indicates that sets of node 2 needs to:
Add 0 (ARS prefix) then 010143 (installation number)
For DID sets (size from 32000 to 32099 in DID translator of node 2), 2000 to 2099 is added
For non DID sets, 2008 is added (attendant call of node 2).
Set 32000 belongs to the range so the number to dial is 0 0101432000
Number dialed is analyzed in discriminator rules for COS of set 31000.
Call is authorized number 0101432000 is sent to the public carrier.
This one routes the call to the remote trunk group and then the call is routed to set 32000.
In the second case, set 31000 dials 32200

This set doesn’t belong to the range, the final number is attendant number 0101432008.
This one routes the call to the remote trunk group and then the call is routed to the attendant and then transferred to the set 32200.
Public to private overflow must be managed all over the network

377
Overview
A specific DID translator is used to build the public number

to use
➨ DID numbers definition is mandatory
➨ Private / Public DID translators are broadcasted into th

network
It is necessary to define for each node of ABC network:
➨ Seizure prefix to use (trunk group or ARS) Local
➨ Remote installation number (fixed part) Local
➨ The default installation number for non DID users Broadcasted
➨ The DID translator of remote node Broadcasted

Different DID translators of the external dialing plan are not used.
Even if all sets are DID, it’s compulsory to define a DID range, using 2 ways:
•Create a DID blank range (including all sets)
•Declare the DID translator in transparent mode (all numbers are reused without modification)

378
Overview
The barring is managed using two ways

➨ The private to public overflow is authorized or not according
to the phone facilities parameters
▼ Private to public overflow on busy link: Yes/No
▼ Private to public overflow if link OS: Yes/No
➨ The system checks the barring management to authorize or

not the private to public overflow
No software licenses is required
The sets authorized to use the overflow must be defined

according to the customer agreement

The cost of calls is not negligible so sets authorized must be defined according to the customer agreement.

379
Overflow between ABC sub-
sub-networks
The same principle is used for ABC sub-networks overflow
Management objects used

(Translator / External Numbering Plan)
➨ Overflow between nodes of the same sub-networks
▼ Node Access Prefix
▼ Node DID Translation
➨ Overflow between nodes of different sub-networks
▼ Network Access Prefix
▼ Network DID Translation

The overflow between nodes of different ABC sub-networks is done with ABC trunk groups (not ABC link) saturated or OOS.
Management and functioning is the same for the 2 types of overflow.

Access rights is done the same way by using phone facility COS.
Barring is done the same way by using public access COS.
No software licenses are required.

380
PROCEDURE
OBJECTIVE
- Learn how to manage the Private to public overflow in an ABC-F network and in two different
ABC-F networks
REFERENCE
- CD-ROM System Documentation: Custom System Documentation / Technical documentation /
Private Networks / ABC-F homogeneous private network / ABC-F homogeneous private network
OVERVIEW
When an ABC link of the private network is unavailable, out of service or saturated, internal calls of
the ABC network can overflow to the public network.
There is two cases: overflow between nodes in the same network and overflow between nodes
belonging to different networks.

381
PROCEDURE
1. Overflow between nodes in the same network

ABC TG
Node 1 n°120
Neywork 1
ABC
link
ABC TG
n°210
Node 4
Neywork 2
Node 2
Neywork 1
The example below requires to have to following configuration:

Node 1
- Sub-network: 1
- Installation number: 0201431000
- DDI range on ten digits (6 first digits removed), DDI range size: 100 numbers
- T2 TG with prefix : #012
Node 2
- Sub-network: 1
Broadcast must be activated all over the network.
1.1 Phone features COS management

Application Mgr
Path Class of Services / Phone Features COS
Busy priv.to public overfl. 1
O/S private to public overflow 1
Action Ctrl – V
Note: Management has to be done according to client’s requirements (overflow if ABC link busy
and/or out of service)

382
1.2 Creation of the node access prefixes

This creation is done on each node. The local manager knows the best the DID numbering
usable on his site, just like the number to be dialed to reach the non DID sets (sets, groups,
attendant, etc…), it’s to him to define this parameters for his own site.
Application Mgr
Path Translator / External Numbering plan / Node Access Prefix
Action Creation
On node 1 On node 2
Destination Node No. 1 2
Number to Add
Install.No.Last Part 1000 2000
Action Ctrl – V
Note: Number to add is not necessary for local node overflow. After broadcast, each node will
complete this number for the remote site.
1.3 Creation of a translation table on both node

Application Mgr
Path Translator / External Numbering plan / Node Access Prefix / Node
DDI Translation
Action Creation
On node 1 On node 2
Range size 100 100
Action Ctrl – V
Note: Each node configures his own DID translator for overflow.

383
1.4 Modify the network access prefix after broadcast

Application mgr
Path Translator / External Numbering plan / Network Access Prefix
Action Creation
On node 1 On node 2
Network No 2 1
Digits to Add #012020143 #022020143
Action Ctrl – V
Note: Installation N° is already managed and must not be modified

384
2. Overflow between nodes in different network

ABC TG
Node 1 n°120
Neywork 1
ABC
link
ABC TG
n°210
Node 4
Neywork 2
Node 2
Neywork 1
The example below requires to have to following configuration:

Node 1
- Sub-network: 1
Node 4
- Sub-network: 2
Broadcast must be activated all over the network.
2.1 Creation of the node access prefixes

Application Mgr
Action Creation
On node 1 On node 4
Network Number 2 1
Number to Add #012020143 #042020143
Install.No.Last Part 4000 1000
Action Ctrl – V
2.2 Creation of a translation table on both node

Application Mgr

385
Path Translator / External Numbering plan / Node Access Prefix / Node

DDI Translation
Action Creation
On node 1 On node 4
Range size 100 100
Action Ctrl – V
2.3 Modify the network access prefix after broadcast

Application mgr
Action Creation
On node 2
Network No 2
Digits to Add #022020143
Action Ctrl – V
Note: Each node of all the networks has to customize the outgoing prefix as well as the first digits
to reach the remote network according the available resources.

386
Private to Public overflow
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the private to public overflow
MANAGEMENT
1. Manage the node access prefix with each node of your own subnetwork
1.1 Use the T2 trunk group for the overflow (Install N°: 02CC0 where CC is the classroom
number)
1.2 Only the sets from 3x000 to 3x099 are DID on the remote nodes
1.3 The 3x000 should be rung in case of non DID sets call
2. Manage the phone facility categories in order to have the following behavior:
- the UA sets can overflow if the ABC link is out of service or saturated
- the analog sets can overflow only if the logical link is out of service

387
Private to Public overflow

388
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
389
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
390
Public to private rerouting

OBJECTIVE:
◆ To describe public to private rerouting mechanisms
Alcatel OmniPCX Enterprise – Public to private Rerouting

391
Overview
Public to private rerouting allows to redirect automatically

public calls intended to a network set in internal calls
➨ Cost optimization
➨ Use of ARS to force calls to private link
Public numbers are automatically are changed in internal

numbers and dialed by the system
➨ In case of call failure, overflow to a public route is still

possible
▼ ARS management (second route or private to public overflow)

This kind of rerouting doesn’t concern ABC F calls.

The same configuration is applicable to:
•Inter node calls
•Sub-networks calls
•Calls to system reachable via private links (ISDN, QSIG, PCM, ATL, VoIP, etc…)

392
Overview
Mechanism
32000
Node 1 DID
Alcatel OmniPCX
Enterprise
Nœud 2
31000 Call Server
4 Call of 32000
0 : ARS seizure
T2
T2
1 Call of 0 0101432000 32000

Carrier
Discrimination rules
Public translator : 0101432
2 Area :1
ARS table 12
Digits number: 10
ARS table 12
1rst route :
Trunk group : -1
No.Digits To Be Removed: 5 Non DID sets are not concerned by this
3 Digits To Add : management
2nd route :
Trunk group : 12
No.Digits To Be Removed: 0
Digits To Add :

Set 31000 dials 0 010143200

The translator indicates that 0101432 is in area 1 and uses ARS table 12.
In In ARS table 12, two routes are created:
Route 1:
•Trunk group: -1 number must pass by again into the translator for analyze
•No.Digits To Be Removed: 5 first 5 digits are removed
• Digits To Add : no modification
Route 2t
•Trunk group: 12 public trunk group
•No.Digits To Be Removed: 0 no modification
• Digits To Add : no modification
The number left after passing by in ARS route 1 of ARS table 12 is then 32000.
This number is analyzed into the translator, and corresponds to a network prefix towards node 2.
Call is sent via ABC link towards node 2.

393
Overview
New analyzing of dialing
➨ Value –1 on trunk group force to pass by again the number

into the translator
➨ Only one ARS route with this value per table
➨ This route must be in first position in the table
➨ In case of problems in the private network, a second public

route can be used
▼ Dialing modification possible
▼ Access restrictions possible using ARS cost threshold

Threshold ARS cost is defined into timed base route list for each route.
For each passing by into the table, the system compares this value with the ARS privilege defined into the public access COS.
If ARS privilege is greater than the cost defined of ARS table used, the call is authorized.

394
Public to private re-routing
PROCEDURE
OBJECTIVE
- To learn how to manage Public to private re-routing
REFERENCE
Public Networks / ARS / Configuration examples
OVERVIEW
Nodes 1 and 2 are connected through a ABC-F link.
A User of node 1 dials 0101432000. The PCX analyzes the dialing:
- Initially, it forces the call on ABC-F link (private link).
- Then, if the link is saturated, the call overflows on 0101432000 via public trunk group T2.
The manager must:
- Configure the general parameters,
- Create the route list,
- Create the time-based route list.

395
PROCEDURE
1. Configuring the general parameters
1.1 Create the ARS prefix

Application mgr Tab
Path Translator / Prefix Plan
Action Create
Number 0
Prefix Meaning ARS Prof.Trg Grp Seizure
Action CTRL-V
Discriminator No. 0
Action CTRL-V
1.2 Create discrimination rules

Application mgr Tab
Path Translator / External numbering plan / Numbering
discriminator / Discriminator rule
Action Create
Call Number 0101432
ARS Route List Number 12
Number of digits 10
Action CTRL-V
Note: In the discriminator rule, the call number must be the most precise possible to concern only
the DID range of the remote node. Example, don’t use 01014 that concerns numbers not
only belonging to the remote node, but 0101432 for only node 2.

396
2. Optional management
2.1 ARS privilege

Application mgr Tab
Path System
ARS Parameters
Route Restriction + YES
Action CTRL-V
Note: Route Restriction: YES: The cost thresholds of the ARS route list are applicable from the 1st
external routing for the 'STOP POINTS' only (see ARS ROUTE LIST). NO: The cost thresholds
are not applicable to the 1st external routing; they are applicable to secondary routing. The
cost threshold makes it possible to reject the call when the ARS class of service of the
subscriber has reached this threshold.
2.2 ARS privilege of user

Application mgr Tab
Path Classes of service / Access COS
Public Network COS 2
Action CTRL-V
ARS privilege
Night 0
Day 0
Mode 1 0
Mode 2 0
Action CTRL-V
Note: ARS privilege (Automatic Route selection): The ARS privilege level (0 to 31) is used when a
call is rerouted and is compared to a cost threshold. If the cost threshold is equal or
superior to the privilege, the call is rejected.

397
3. Creating the route list (routing table)

Application mgr Tab
Path Translator / Automatic Route Selection / ARS route list
Action Create
Name Re routing
Action CTRL-V
3.1 Creating the ARS routes

Application mgr Tab
Path Translator / Automatic Route Selection / ARS route list /
ARS Route
Action Create
Route 1
Name Private route
Trunk Group -1
No.Digits To Be Removed 5
Route Type + Private
Quality + Voice / Fax
Application mgr Tab

ARS Route
Action Create
Route 2
Name T2
Trunk Group 12
No.Digits To Be Removed 0
Route Type + Public
Quality + Voice / Fax

398
3.2 Creating the Time-based Route List

Application mgr Tab
Time-based Route List
Action Create
ARS Route List 12
Time-based Route List ID 1
Action Add
Route Number 1
Waiting Cost Limit -1
Stopping Cost Limit -1
Action CTRL-V
Action Add
Route Number 2
Waiting Cost Limit -1
Stopping Cost Limit -1
Action CTRL-V
Note: Waiting Cost Limit: Enter the value of the waiting cost between 0 and 31. Leave this field
blank to indicate that the value is the same as the previous route in the list (default value).
The value of the waiting cost threshold must be defined so as to be consistent with the
search order defined in the time-based route list,
Note: Stopping Cost Limit: Enter the value of the stopping cost between 0 and 31. Leave this field
blank to indicate that the value is the same as the previous route in the list (default value).
The upper limit is fixed at 30 so as to prevent filtering all calls. This is because the calls of
users whose cost threshold is 31 will always try to take this route. The parameter can only
be activated on condition that the routing restriction option is valid (system parameter in
Installation).
The value of the Stopping cost threshold must be defined so as to be consistent with the
search order defined in the time-based route list.

399

400
Public to Private rerouting
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the public to private rerouting
MANAGEMENT
1. Topology: ABC links are permanent T2 links and to reach the public network ISDN links are
used.
PSTN
ISDN links
NODE A NODE C
ABC links
Node A, B, C =1, 2 , 3
Or =4, 5, 6
NODE B
2. Create the ABC-F links or restore a database with permanent ABC links on ISDN.

401
Public to Private rerouting
3. Manage the ARS for outgoing calls beginning by 02CL53N (CL: Classroom Id, 5: T0 trunk
group for incoming call, N: Remote node)
- First route will be the private link
- Second route will be the public network
4. Test the feature. Dial for instance 0 02CL13Y000 and check that the private link is used.

402
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
403
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
404
ARS server

OBJECTIVES:
◆ To describe server ARS principles in ABC network
◆ To describe main use cases
Alcatel OmniPCX Enterprise – ARS server

405
ARS server
Overview
The ARS Server can facilitate the management of an

homogeneous ABC-F network
➨ Centralization of ARS management of one or several

directions on only one node of the network
➨ Use of local ARS management for proximity breakout
The same ARS table can contain:
➨ Local routes (standard management)
➨ Remote nodes ARS routes
The ARS management is local, it is not broadcast


406
ARS server
Overview
The ARS route inserts a ARS server prefix in the number
➨ This prefix indicates the node which will analyze the number
➨ The call is sent to the concerned node via the network
➨ The remote node (ARS server) analyzes the number in his

own translator
▼ Use of local ARS management
The ARS table must contain ARS local route to allow calls
in case of network failure
➨ Saturated ABC links or OOS
➨ Remote ARS routes saturated


407
ARS server
Example Area 01
Paris N1
Directions : Direct link
01 : ARS server = N1 Area 06
02 : Local ARS GSM
0298153 : Local ARS Directions :
03 : ARS server = N3 01 : Local ARS
06 : ARS server = N1 02 : ARS server = N2
0039 : ARS server = N3 k 03 : ARS server = N3
lin 06 : Local ARS
C
AB 0039 : ARS server = N3
Brest N2
Alcatel OmniPCX
AB
Enterprise
Cl
ink
Call Server
Opérateur Germany
G
SI
Area
Q
en
Direct 0039
Li
public N° link
AB
0298153 C li
nk
Area 02 Directions : Strasbourg N3

01 : ARS server = N1
03 : Local ARS
0039 : Local ARS Area 03

Configuration example for specific links with carriers and optimization of proximity breakouts.
•Node 1, located in Paris (public area n° 01), has a direct link with a GSM carrier which allows to reduce costs for mobile calls.
•Node 2, located in Brest (public area n° 02), has a direct link (QSIG) with a specific site (n° 0298153xxx).
•Node 3, located in Strasbourg (public area n° 03), has a direct link with a German carrier (area0039).
The ARS server can allow to simplify sites management.

On nodes 1 and 3:
•Every number beginning with 02 is sent to node 2. Then, ARS management of node 2 is used (local way-out for 02, and QSIG link if
number is 0298153).
On nodes 2 and 3:
•Every number beginning with 01 or 06 is sent to node 1. Then, ARS management of node 1 is used (local way-out for 01, and direct
link for GSM number).
On nodes 1 and 2:
•Every number beginning with 03 or 0039 is sent to node 3. Then, ARS management of node 3 is used (local way-out for 03, and
direct link for German carrier for 0039).
Routes and carriers choices will be optimized locally by site manager (who knows the best this configuration).
So, other nodes management is strongly simplified.

408
ARS server
Example
Node 1 uses node 2 as ARS server

Set 31000 Node 2
Entity : 1 Alcatel OmniPCX
Enterprise
Pub. Access COS: 3
Node 1
32111 0102030405 Call Server
0 0102030405 Entity 1 / Pub. Access COS. 3

ABC link
0 : ARS prefix Translator (prefix plan)

Discriminator : 2 32111 : ARS Server Pref.
Network : 0 / Node : 2
Entity 1 discriminator N° : 2
(discriminators)
Logical 2 Real 2 Entity 1
(discriminators)
Logical 2 Real 2
Discriminator 2 ARS table 1 ARS table 10
010203 : Area 1 Route 1 Discriminator 2 Route 1
ARS Table : 1 Trunk group : -1 010203 : Zone 1 Trunk group : 22
Schedule N° : -1 Del : 0 ARS table: 10 Del : 0
Add : 32111 Schedule N°: -1 Add :
Translator (prefix plan) Route 2 Route 2
32111 : ARS Server Pref. Trunk group : 12 Trunk groups Trunk group : 20
Network : 0 Del : 0 20 : T0 access Del : 0
Node : 2 Add : 22 : T2 access Add :

Set 31000 dials 0 0102030405, prefix 0 is a ARS prefix which uses logical number 2.
Set is in entity 1, which do the link with real discriminator 2.
In discriminator 2, corresponding area points towards ARS table 1.
In ARS table 1, two routes are created:
Route 1:
•Trunk group: -1
•Prefix add 32111
Route 2:
•Trunk group 12 (T2)
The ARS timed based route list uses first route 1 and, then route 2.
Prefix 32111 is a ARS server prefix which points towards to node 2.
The number modified by ARS table passes in analyze in dialing plan and is sent via BC link to node 2 (node N° given by ARS server
prefix).
On node 2, ARS server prefix 32111 is defined (received after broadcast) and corresponds to local node, logical discriminator
number is 2. The real discriminator is given by set entity (given in ABC message as well as the public access COS). Real discriminator
to use is always 2, system analyzes the public number in the translator.
Number 010203 uses ARS table 10.
In table 10, 2 local routes are defined:
Route 1: Trunk group 22 (T2)
Route 2: Trunk group 20 (T0)

409
ARS server
Remarks
The number modified on source node is transmitted via

ABC link and analyzed on incoming node
➨ Determination of real discriminator
▼ Via ARS server prefix and set entity
➨ Analyze of public number in translator
▼ Area compatibility with set class of service
Comparison is always done with local management on

incoming node
➨ Discriminators and entities must be coherent all

over the nodes of the network


410
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
411
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
412

System Networking PDF

Uploaded by

Copyright:

Available Formats

You might also like

System Networking PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Networking 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 ENTPTE402US DELIVERY LANGUAGE English (course material in English)

7 hours Virtual self-paced training on the computer

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

REQUIRED TECHNICAL CONFIGURATION

Phase 1: i-learning 7 hours

Phase 2: c-learning 5 days

Configure the IP addressing plan of an Alcatel OmniPCX Enterprise in networking configuration

ISSUE DATE ISSUE DATE

Alcatel OmniPCX Enterprise System Networking

File reference: ENTPTE402US

CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION

1. IP addressing in ABC network

2. System Synchronization and System Synchronization in network

Issue 01 REF. ENTPTE402US 0.1

6. Broadcast and Broadcast area

7. ABC-F Trunk Group

0.2 REF. ENTPTE402US Issue 01

10. Executive / Assistant in network

11. 4645 in network

12. System messages centralization

13. DECT in network

14. Hunt groups in network

15. Private to public overflow

Issue 01 REF. ENTPTE402US 0.3

16. Public to private rerouting

17. ARS Server

0.4 REF. ENTPTE402US Issue 01

Issue 01 REF. ENTPTE402US 0.5

SECTION CHAPTER PAGE DESCRIPTION OF THE ERROR

0.6 REF. ENTPTE402US Issue 01

IP Addressing in ABC-F Network

© Copyright Alcatel Business Systems 2005

◆ To describe the IP addressing principles in ABC-F network

◆ To describe the different interfaces used

Alcatel OmniPCX Enterprise – IP Addressing in ABC network

In ABC-F network, IP is required for communication

➨ System configuration, maintenance

According to the topology, IP links used may be:

➨ Carried by the IP/X25 tunnel