VoIP Network Designer

Alcatel Solutions - Presales
PARTICIPANT'S GUIDE
VoIP Network Designer
This document has no contractual value and may

be changed or withdrawn at any time by Alcatel
REF. PS00TE631US
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).
PRE-SALES TRAINING
CURRICULA PATHS
Fundamental
All rights reserved 2004, Alcatel
indicates that the knowledge provided by the

associated module(s) is required for AQPS exam

associated module(s) is required for ACPS VoIP
Network Designer exam
Learning Solutions Catalog 2004 2
UC

associated module(s) is required for ACPS
Unified Communication Designer exam
The icon marked on the right top of each module indicates the
associated certification level
CERTIFICATION LEVELS
12 hrs
LOHDUQLQJ
PS00TE630
PS00WB604
OF00TE304
Pick & Learn

Complementary packages
Migration
CCA
LOHDUQLQJ
PS00WB605
OF00TE304
Migration
CCO
LOHDUQLQJ
2 hrs
3 hrs
TRAINING
PRE-SALES
PS00WB603
OF00TE304
3 hrs
3 hrs
Fundamental
Migration
CCivr
LOHDUQLQJ
PS00WB602
OF00TE304
Migration
ACR
LOHDUQLQJ
VoIP Designer
4 days
YRUFOHDUQLQJ
PS00TE631
STEP1
24 hrs
LOHDUQLQJ
4 days
STEP2
YRUFOHDUQLQJ
VOIP DESIGNER:
System architecture
Telephone services
Call handling
Attendants
IP Telephony
OmniVista overview
Voice mail overview
DECT/PWT mobility overview
Hotel overview
Integrated Automated Attendant
CCD and CCS basics
Common configuration guidelines
Engineering rules and traffic
VoIP mechanisms
IP distributed architectures
H323, Gateways, Gatekeeper, SIP
Networking concepts
Networking call distribution
Voice Mail
Voice Mail in Network
CCD/CCS in Network
Internal Applications
External applications
Engineering rules
OmniVista
Configuration guidelines
VOIP NETWORK DESIGNER:
Alcatel OmniPCX Enterprise & OmniTouch CC R6.1

CURRICULUM FOR NEWCOMERS
OMNITOUCH CALL CENTER OFFICE:

Describe the OmniTouch Call Center
Office
Describe and use the quotation tools
Perform Case studies
PIMPHONY:
CUSTOMER DATABASE INTEGRATION :
Describe the PIMphony application
Describe the customer database
integration
VOIP:NETWORKING AND VPN

Describe the VoIP over VPN (VPN Site to
Site, VPN Client to site)
0.5 day
0.5 day
1 day
PS00TE522
OF00TE304
OmniTouchMigration
Call Center Office
YRUFOHDUQLQJ
PS00TE523
Migration
PIMphony:
OF00TE304
Customer Database
Integration
YRUFOHDUQLQJ
PS00TE524
OF00TE304
VoIP: Networking
Migration
and VPN
YRUFOHDUQLQJ
Alcatel OmniPCX Office R4.0

Fundamental
STEP1
TRAINING
PRE-SALES
OMNITOUCH UC MY TEAMWORK :
My Teamwork features and architecture
Offer and quotation
OMNITOUCH UNIFIED COMMUNICATION:

Architecture and packages
My Messaging
My Phone
My Assistant
My Teamwork
Services and features
Options
Quotations
3 days
UC
0.5 day
PS00WB634
OmniTouch UC My Teamwork
LOHDUQLQJ
Unified Communications
Environment
FG00TE606
PS00TE633
OmniTouch Unified
Communication
FOHDUQLQJ
Alcatel OmniTouch UC 3.0.x

TRAINING
PRE-SALES
Only UC
My Teamwork
Full UC
Application Suite
Fundamental
Fundamental
Enhance Operational Knowledge
Upgrade knowledge to keep autonomy

in solutions design
How to upgrade knowledge

EXPERIENCED
ENHANCED
DESIGN
TRAINING
PRE-SALES
R6.0 TO R6.1 UPGRADE:

New hardware
New phone services
Alcatel 8 and 9 series range of terminals
Hybrid Media Gateway
Spatial redundancy
Https
OmniVista 4760 enhancements
OmniTouch Contact Center enhancements
1 day
PS00WB632
R6.0 to R6.1 Upgrade
FRUYOHDUQLQJ
Pre-Sales
R6.0
Alcatel OmniPCX Enterprise & OmniTouch CC R6.1

UPGRADE CURRICULUM FOR EXPERIENCED
Fundamental
Pre-Sales
R6.1
TRAINING
PRE-SALES
OMNITOUCH UNIFIED COMMUNICATION:

Architecture and packages
My Messaging
My Phone
My Assistant
My Teamwork
Services and features
Options
Quotations
OMNITOUCH UC MY TEAMWORK :
My Teamwork features and architecture
New R3.0.x features
Offer and quotation
Pre-Sales
R2.0
Pre-Sales
R3.0
3 hrs
UC
3 days
PS00TE633
OmniTouch Unified
Communication
FOHDUQLQJ
or
PS00WB634
UC
OmniTouch UC My Teamwork
LOHDUQLQJ
Alcatel OmniTouch UC 3.0.x

UPGRADE CURRICULUM FOR EXPERIENCED
TRAINING
PRE-SALES
Pre-Sales
R3.0.x
Pre-Sales
R3.0.x
Fundamental
3 days
3 hrs
FG00TE080
2 days
FG00TE606
Unified Communications
Environment
FOHDUQLQJ
Voice, Data & Applications

Essentials
LOHDUQLQJ
FG00TE081
Network Security Essentials
FOHDUQLQJ
Examples of what you can attend

2 days
FG00TE640
Web Services Essentials
FOHDUQLQJ
GET
PREPARED
TRAINING
PRE-SALES
Refer to the Technology Training catalog for further details

https://www.businesspartner.alcatel.com/
Training/ Curricula & Schedule /Fundamentals and basics knowledge curricula
Telephony
IP Communications
Applications
Networking
Security
Acquire competence and knowledge to understand and get familiar with enterprise
environment, standards and protocols used in Alcatel Solutions
Technologies on :
Need to get prepared on Technology ?

Fundamental
Alcatel Solutions Pre Sales

REFERENCE : PS00TE631US
LANGUAGE : ENGLISH
DELIVERY METHOD : Blended Learning
C learning part could be provided as V

learning (under request)
DURATIONS :
4 days
24 hours
Part of the certifying curriculum up to :
PARTICIPANTS : 6
Min - 12
Max
ACPS VoIP Network Designer
Who should attend this course ?
Pre Sales
Project Managers
Sales and Marketing Representatives
Prerequisites :
To have the AQPS Certification or equivalent knowledge on Alcatel OmniPCX Enterprise
Main course objectives :
To achieve basic skills to analyze and design complex and networking OmniPCX Enterprise
offers

c-learning
i-learning
VoIP Mechanisms - Automatic VLAN
VoIP Mechanisms - LAN presentation
VoIP Mechanisms - VoIP protocols
VoIP Mechanisms - VoIP in OmniPCX Enterprise
VoIP Mechanisms - QoS
VoIP Mechanisms - Power feeding
VoIP Mechanisms - Firewall
VoIP Mechanisms - NAT and IPSec
VoIP Mechanisms - VoIP audit, quality and echo
IP Distributed Architectures IP domains & VPN hops
IP Distributed Architectures VoIP for Branch Offices
IP Distributed Architectures Topology examples

H323, Gateways, Gatekeeper, SIP Internal GateKeeper
in OmniPCX Enterprise
H323, Gateways, Gatekeeper, SIP SIP in OmniPCX
Enterprise
H323, Gateways, Gatekeeper, SIP H323 Gateway
4
4
Networking Concepts - Terminology
Networking Concepts - Network architecture
Networking Concepts ATM solution case
Networking Call Distribution - Moving
Networking Call Distribution Numbering plan and short

dialing
Networking Call Distribution Voice compression
mechanisms
Networking Hybrid Links and ABC VPN Audit and
broadcast
Networking Hybrid Links and ABC VPN Network
overflow solution
Networking Hybrid Links and ABC VPN Hybrid ABC
links
4
4
4
4
v-learning

Networking Hybrid Links and ABC VPN Centralization

of applications
Networking Hybrid Links and ABC VPN ABC link
Networking Hybrid Links and ABC VPN IP:X25
tunneling
Networking Hybrid Links and ABC VPN Network
features
Voice Mail Alcatel OmniMessage 4645
c-learning
i-learning
4
4
Voice Mail Alcatel OmniMessage 4635
Voice Mail Configuration guidelines
Voice Mail Automated attendant
Voice Mail Fax features
Voice Mail Voice mail centralization
Voice Mail in Network - Description
Voice Mail in Network VPIM and IMAP integration
CCD/CCS in Network CCD overflow
CCD/CCS in Network CCD networking
CCD/CCS in Network CCS in network
CCD/CCS in Network CCD and CCS licensing
CCD/CCS in Network Home agents
CCD/CCS in Network CSTA and CTI protocols
CCD/CCS in Network Offer proposal
OmniTouch Unified Communication - Overview
OmniTouch Unified Communication My Phone

overview
OmniTouch Unified Communication My Messaging
overview
OmniTouch Unified Communication My Assistant
overview
4
4
4
Design Guidelines Traffic calculation in networks
Design Guidelines Design guidelines and case studies
v-learning

Design Guidelines Assesment VoIP tool
c-learning
i-learning
Design Guidelines Fax and modem on IP
OmniVista 4760 Architecture
OmniVista 4760 Hardware and Software
OmniVista 4760 Connectivity
OmniVista 4760 Offer proposal
OmniVista 4760 Directory

OmniVista 4760 Graphical interface and configuration
applications
OmniVista 4760 Accounting
4
4
4
OmniVista 4760 Monitoring
OmniVista 4760 Performance
OmniVista 4760 Alarms
OmniVista 4760 Topology
OmniVista 4760 SNMP
OmniVista 4760 VoIP tickets
OmniVista 4760 Scheduler
OmniVista 4760 Maintenance
v-learning
Alcatel University

TOC
DOCUMENTATION CHANGES
ISSUE
DATE
01
04/05
ISSUE
DATE
Alcatel Solutions - Presales VoIP Network Designer
File reference: PS00TE631US
GENERAL SUMMARY
CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION
1.
Network Architecture
ENTP0110P03PSUS ............................................................................................... page 05
2.
IP/X25 tunnel
ENTP0111P06PSUS ............................................................................................... page 45
3.
Audit & Broadcast

ENTP0110P04PSUS ............................................................................................... page 65
4.
Centralized Applications
ENTP0110P08PSUS ............................................................................................... page 89
5.
Voice mail networking

ENTP0120P01PSUS ............................................................................................... page 115
6.
Network overflow solutions

ENTP0110P05PSUS ............................................................................................... page 145
7.
Hybrid ABC links

ENTP0110P07PSUS ............................................................................................... page 165
8.
Voice compression over ISDN

ENTP0167P02PSUS ............................................................................................... page 205
9.
TCP/IP implementation in the OmniPCX Enterprise

ENTP0111P05PSUS ............................................................................................... page 231
Issue 01
REF. PS00TE631US
0.1
Copyright Alcatel Business Systems 2005

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.
Alcatel University
TOC
10. ABC link VoIP and H323 PC

ENTP0110P11PSUS ............................................................................................... page 245
11. Alcatel IP Phones

ENTP0111P07PSUS ............................................................................................... page 303
12. VoIP QoS

ENTP0111P08PSUS ............................................................................................... page 347
13. SIP
ENTP0147P01PSUS ............................................................................................... page 395
14. Topology examples

ENTP0143P01PSUS ............................................................................................... page 439
15. SNMP implementation in the OmniPCX Enterprise

ENTP0166P00PSUS ............................................................................................... page 465
16. Data and modem transparency

ENTP0111P20PSUS .............................................................................................. page 483
17. Automatic VLAN assignment

ENTP0111P21PSUS ............................................................................................... page 501
18. OmniVista 4760 connectivity

47600112P06PSUS .............................................................................................. page 519
19. OmniVista 4760 LDAP directory

47600112P08PSUS .............................................................................................. page 541
20. Networking Solutions

CCD00010P01PSUS ............................................................................................. page 589
21. Networking Solutions Quotation

CCD00011P02PSUS ............................................................................................. page 609
22. Case study networking

ENTP0177P00PSUS ............................................................................................... page 619
ENTP0177P01PSUS ............................................................................................... page 631
0.2
REF. PS00TE631US
Issue 01
Alcatel University

TOC
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 Kervzennec
CS 82802
29228 BREST CEDEX 2 - FRANCE
FAX : (33) 2 98 14 36 36
Please return this sheet to:
DATE:
Issue 01
REF. PS00TE631US
0.3

Alcatel University
TOC
0.4
REF. PS00TE631US
Issue 01
Alcatel OmniPCX Enterprise Presales

OBJECTIVE:
To describe and to identify the Alcatel OmniPCX Enterprise network architecture
Alcatel OmniPCX Enterprise Network architecture

Ref. ENTP0110P03PSUS
Issue 02
Content
X Definition
X Features description
X Interaction with other services
X Quotation and recommendation
X Reference documentation
X Conclusion


Issue 02
Definition
X A private telephone network is the ability for users, located

on different sites, to make private telephone calls using
leased lines and not the public network.
X Different topologies:
Homogeneous networks (ABC links)
Corporate networks (ABC trunk groups)
X Different nodes types: Backbone / End nodes


Issue 02
Features description
X Topologies: Homogeneous network

ISDN
PSTN
ABC link
ABC link
ABC link
Line
ISDN
Star
PSTN
ISDN
Mix
Meshed
PTO 1
ISDN
PSTN
ABC link
The Alcatel OmniPCX Enterprise nodes are interconnected
using ABC links (T2, T1 CCS, T0, IP) giving a high level of
services
Under software license control (ABC network license)

Homogeneous Network:
The Alcatel OmniPCX Enterprise can be easily networked (using ABC links) to reach very high capacities of up to 50 000 extensions
and 100 nodes, in various geographic topologies. The service is based on a powerful protocol: The Alcatel Business Communication
or "ABC protocol". The architecture of this protocol is based on four modules:
ABC-F homogeneous: supporting the telephone features
ABC-M: supporting the management mechanisms
ABC-R: supporting the routing algorithms
ABC-A: supporting applications running in network
In addition, this architecture is based on the standard protocol QSIG-BC and GF. This has the advantage of facilitating the Alcatel
OmniPCX Enterprise integration in heterogeneous environments whilst retaining an ABC-F service level between the different Alcatel
OmniPCX Enterprise interconnected through this environment.
Topology:
The network can be configured in various topologies using ABC links: Line, Star, full meshed or a mixture. The connections are made
via digital leased lines (T2 (E1), T0 and T1), digital public lines, Frame relay X24/V11 or V36, ATM 2 Mbps, IP 10/100 BT, analog
leased lines and it could be done using compression of voice. Thanks to the architecture of these ABC links, applications like audit,
broadcast, telephone/IP routing but also telephone features like supervision, call distribution are possible between the different nodes
thanks to the X25 signaling provided by the ABC links.
ABC networking over analog leased lines is also supported. In this case, the Crystal media gateway is used to provide the tie-line
interfaces required (ACEM, EMTL boards).

Issue 02
X Topologies: Corporate network

ABC trunk groups
PSTN
Sub-network 2
Sub-network 3
Sub-network 1
PSTN
PSTN
PSTN
Homogeneous networks (sub-networks) can be connected
using ABC trunk groups (T2, T1 CCS and T0) to form a

corporate network giving a bigger configuration (more than
100 nodes and more than 50000 users)
Corporate network:
Many homogeneous Alcatel OmniPCX Enterprise networks can be federated in an extended configuration called "corporate network".
Each sub-network retains its own external connections, attendants, centralized applications and management, but ABC-F and
ARS/LCR telephone services remain coherent throughout the whole corporate network. The advantage of this configuration is that a
large company spread over national or international territories can be federated through an efficient voice communication network,
whilst maintaining local reactivity. In theory, we could configure a corporate network with up to 255 subnetworks.
Topology: these subnetworks are connected using T2, T1, T0, E1, ATM ABC trunk groups using or not compression of voice. The
difference with ABC links is that the physical supports are limited in choice and you dont have the same level of service than using
ABC links (no audit, broadcast, supervision, call distribution because no X25 signaling).
Remark: needs the ABC network license

Issue 02
X Topologies: Alcatel OmniPCX Enterprise homogeneous

network
100 nodes maximum
Network structure (2 node types)
Backbone nodes
End nodes

The homogeneous Alcatel OmniPCX Enterprise ABC network consists of Alcatel OmniPCX Enterprise systems (nodes) interconnected
via ABC links supporting the ABC-F2 protocol.
The Alcatel OmniPCX Enterprise enables to build an homogeneous network of up to 100 nodes with 50000 subscribers, 1000 data
terminals and 2000 trunk groups.
In fact, this type of network is built in two parts. It introduces the new "backbone area" idea, which is the core of the network (32
nodes), and the end node nodes which are connected to the backbone area and enable to enhance the network up to 100
nodes.
In management, each node has a Network identifier and a Node identifier. (e.g.: Network:1, Node 1).

Issue 02
10
X Topologies: Alcatel OmniPCX Enterprise Homogeneous

network
Network
Backbone
Routing
nodes
End nodes

The network can be configured in various topologies: Line, Star, full meshed, or a mixture. The connections are made via Digital
leased lines, Frame relay X24/V11 or V36, IP 10/100 BT, ATM or analog leased lines.

Issue 02
11
X Backbone
The backbone is built from several backbone nodes
connected together
Limit: 32 backbone nodes

Backbone nodes
Belong to the backbone
Global network topology is known in each backbone node

"Backbone area"
This represents the core of the network. Its "backbone nodes" number included in the backbone area is limited to 32 nodes.
Backbone's features are as follow:
Backbone nodes are interconnected with other backbone nodes by ABC links with permanent ABC signaling, and with Dynamic X25
routing. That means that all nodes in the backbone know, in real time, the status of the remote links (% of free B channels, or out
of order).
Routing nodes provide routing functions (for the end nodes calls)
Backbone nodes are connected to peripheral nodes (end nodes) with ABC links (T2, T0, IP)

Issue 02
12
X Backbone nodes
Network
Networkseen
seenfrom
frombackbone
backbonenode
node
Routing nodes
Backbone
End nodes

When a network monitoring tool (e.g.: suproutage) is used to check the status of the network from a backbone node, the
complete Alcatel OmniPCX Enterprise Network is seen.

Issue 02
13
X End nodes
Limit: 68 (if 32 backbone nodes, in fact, it depends on the
number of backbones nodes)
Connected to one routing node

Global network topology is not known in end node
Knows only the routing node
Calls from end nodes are systematically routed to the
routing node
Routing node is in charge to route the call through the
network

end nodes"
They represent the enhancement up to 100 nodes (back bone nodes included) of the new large network..
they are connected to a backbone node by ABC links
dynamic ABC links can be used along with all other solutions to connect Alcatel OmniPCX Enterprise nodes
they are not connected to another node in the periphery (only the routing node)
X25 Routing is not used with an end node (in management: Static Routing, that decreases the X25 traffic). So, this node will not
know the status of remote links.

Issue 02
14
10
X End nodes
Need a routing node to route a call through the network
Network
Networkseen
seenfrom
fromend
endnode:
node:
End node
Backbone
End nodes

11
When a network monitoring tool (e.g.: suproutage) is used to check the status of the network from an end node, only the Routing
node is seen (because of a Static X25 Routing).

Issue 02
15
X Heterogeneous network with Alcatel and non Alcatel

PABXs
QSIG protocol
Alcatel
QSIG
OmniPCX
Enterprise
thr
ou ABC
gh
the F2 sig
QS na
QSIG
IG ling
GF
Fa
cili
ti
MATRA
QSIG
SIEMENS
QSIG
es
Alcatel
OmniPCX
Enterprise

An heterogeneous network consists of PABXs from different manufacturers. So in that case, between different PABXs, the QSIG
protocol is used for the telephone signaling. Nevertheless, it is possible to use the Alcatel proprietary protocol (ABC F2) between two
Alcatel OmniPCX Enterprise, even if the signaling has to go through an other manufacturers PABX. But in that case, that PABX must
use QSIG GF (witch will let go through unknown information).

Issue 02
16
12
X Protocols
Alcatel
ABC-F2
ECMA
QSIG SS
Services
level
QSIG GF
QSIG BC

13
ABC-F, Alcatel proprietary protocol is based on QSIG GF. This diagram shows, the parallel services levels developed for Alcatel
PABXs and other manufacturers PABXs.
ECMA: European Computer Manufacturers Association.
QSIG Basic Call
Calling number identification
Called number identification
Malicious calIs identification
Sub-addresses
Data call
QSIG Generic Function
QSIG BC + Transparency for transit protocols
QSIG Supplementary Services
Charging information
Call back on no answer / on busy
Intrusion
Do not disturb
Calling Line Identification
Optimized Transfer
Optimized forwarding
List in progress and not exhaustive

Issue 02
17
X ABC-F links architecture

Only one ABC link between two nodes
An ABC link is made of one or several accesses (16
maximum)
One access is a D channel controlling one or several B channels
"Classical" ABC links
Composed of T2, T1 CCS or T0 accesses

A "Classical" ABC link contains only one type of access
Full ABC links over IP, "Hybrid" ABC links and compressed
ABC links
Please for further information refer to the corresponding module

Interfaces required for ABC-F2 links (T2/T1/T0)

- In a crystal IP Media Gateway
*T2: NPRAE, PRA, PRA2, BPRA, BPRA2, LIOP, LIOX
*T1: DPT1, LIOX
*T0: BRA, BRA2, BPRA, BPRA2, LIOB, LIOX
- In an IP media Gateway
*T2: PRA-T2
*T1: PRA-T1
*T0: BRA2, BRA4, BRA8, MIX
Full ABC link over IP: the two nodes exchange signaling and voice over (using GD, GA or INTIP boards)
"Hybrid" ABC links: the D channel and the B channels are not necessary on the same media
ex: D channel over IP and B channels over analog Tie Lines
Compressed ABC links: the B channels support several compressed B channels (the voice is compressed, it requires LIOX, P, and B
boards)

Issue 02
18
14
X ABC-F links architecture
Voice
or data
B Channels
ABC link
AB
Pro C
toc
ol
ABC-F
D Channel
ABC-R
ABC-M
5
X2 l
/
P
I
ne
tun
ABC-A

15
Roles of the IP/X25 tunnel:

- X25/IP routing
- Element status for calls distribution
- Supervision
- CCd information
- Multi-line: information about executive/secretary groups, supervision...
- IP connection for remote management, maintenance
- audit, broadcast
The ABC protocol has four main modules:
ABC-F for feature transparency - provides users with the same telephony services regardless of their location in the enterprise.
ABC-M for network wide management - allows centralized, simplified management.
ABC-R for network wide routing - optimizes routing for cost/resource optimization and simplifies routing management.
ABC-A for network wide applications allows applications to be centralized or distributed (attendant call distribution and
presentation, voice messaging, contact centers, etc.)

Issue 02
19
X ABC-F trunk groups architecture

Only one ABC trunk group between two nodes
Composed only of T2, T1 CCS or T0 accesses
Contain only one type of access
The "D channels" don't contain IP/X25 tunnels
Loss of service level
Impossible to use network applications as centralized management,

remote accesses
But phone features level will be ABC F2 (same level than in a subnetwork)
Name display...

Interfaces required for ABC-F2 trunk groups (T2/T1/T0)

- In a crystal IP Media Gateway
*T2: NPRAE, PRA, PRA2, BPRA, BPRA2, LIOP
*T1: DPT1
*T0: BRA, BRA2, BPRA, BPRA2, LIOB
- In an IP media Gateway
*T2: PRA-T2
*T1: PRA-T1
*T0: BRA2, BRA4, BRA8, MIX

Issue 02
20
16
X ABC-F trunk groups architecture

Lower level of services
Voice
or data
B Channels
ABC trunk group
D Channel
ABC
Protocol

17

Issue 02
21
X ABC links versus ABC trunks

Features Supported Over an ABC-F Trunk Group
All ABC-F2 features except centralized voicemail.
PABX Management and broadcasting of system alarms.

Compression over leased lines, ISDN, QSIG or Frame Relay
Features NOT Supported Over an ABC-F Trunk Group
Centralized voicemail.
All Virtual Services:
ABC R; Adaptive Routing Services
Distributed trunk group

ARS Server
ABC M
Set Supervision, Boss Secretary, Virtual CCD, Hunt Groups, BLF for Attendants, Twin
Sets,Realtime broadcast of Entity Status, STAP protocol used for dialing from
applications such as 4760 directory client.
Data Consistency checks (Audit)

Broadcasting (if 4760/4755 is installed we are able to broadcast phonebook
changes between sub-networks)
VPN Overflow
Hybrid Network Links
VoIP Networking


Issue 02
22
18
X ABC link types

Permanent ABC link
Telephone ABC signaling

IP/X25 tunnel (applications)
Virtual service
ABC link on demand
Public
Network
ABC
N1
N2
Permanent
N1
N2
On demand
(requires IO2 boards: Crystal hardware only !)

19
Establishment types:
Permanent: the link (D channel or B channel) is always established even if there is no communication, no network information
exchange
On demand: the link is set up only when an application needs it. It could be the telephone application , Audit, Broadcast, remote
login This solutions does not need any direct connection between the PABXs, only at least, a digital bundle connected to the
Central Office for each Alcatel OmniPCX Enterprise PABX. (solution used between End Nodes and Routing Nodes with a low traffic;
never used in the Backbone).
Remark:It is possible in the case of on demand links to allow or forbid some applications to set up the link.

Issue 02
23
X Routing types
No
NoX25
X25routing
routing
information
informationexchange
exchange
Static routing
Dynamic routing
X25
X25routing
routing
information
informationexchange
exchange
Routing nodes
Backbone
End nodes

20
The dynamic routing is also called adaptive (real time evolution of the route cost)
The Alcatel OmniPCX Enterprise ABC network is condensed by an efficient routing mechanism called Adaptive routing. Each node
is permanently informed of the link availability and traffic load. Thus, an Alcatel OmniPCX Enterprise will immediately choose the best
available route to reach the requested device whilst permanently adjusting and balancing the links traffic load. This powerful routing
algorithm called "Adaptive Routing" as an O.S.P.F data protocol equivalent for example, provides a high security level and real link
optimization.
Reminder:
Dynamic routing: Network status knowledge in real time (used to optimize the routing path for calls)
Static routing: no exchange about the network status. The call path optimization will be done by the Routing Node.

Issue 02
24
X Signaling on ABC link

The IP/X25 tunnel uses 1 access, the first established
The ABC protocol on each access concerns only its own B
channels
ABC link
B
D1: ABC
Access 1
IP/X25 tunnel
B
N1
D2: ABC
N2
Access 2
B
D3: ABC
Access 3

21
If the D1 channel is out of service, the B channels of the Access 1 are out of service (ABC signaling is lost for this access).
Then, the routing information and the tunnel (PLL part) will automatically switches into the D2 channel.
An ABC link is a group of accesses. An access corresponds to a D channel for signaling and some B channels for voice/data.
There are two types of ABC link:
-classical ABC links: this type of link is composed only of T2, T0 or T1 accesses (it is not possible to mix in the same ABC link
different type of accesses !: only T2 for instance): 16 accesses maximum.
-hybrid ABC links: the accesses from the same link could be from different types. The particularity of hybrid link is that the
signaling and the voice/data information's are not carried on the same physical medium: 24 accesses maximum (see hybrid
module).

Issue 02
25
X Reminder of possibilities
1) Dynamic routing
2) Permanent ABC link
BN5
BN1
BN2
EN9
BN3
BN4
EN7
EN8
1) Static routing
2) Permanent or on demand ABC link

BNx: Backbone node

Enx: End node

Issue 02
26
22
X Homogeneous in a network
Same prefixes and suffixes facilities
Different extension numbers on each node
The local extensions are known as prefixes on remote nodes
X 2 types of prefixes
Routing prefixes
One prefix = one range of remote extensions
Network prefixes
One prefix = one remote extension

23
A third prefix exists: short local dialing which allows to have a local numbering plan different than the network numbering plan
with shorter numbers
Routing prefix:
34: Network number 0
Node number: 4
Number of digits: 4
Meaning: all numbers beginning with 34 and with a length of 4 digits will be routed toward the node 4 in the network 0
Network prefix:
3410: Network number: 0
Node number: 4
Meaning: when the number 3410 is dialed, the Alcatel OmniPCX Enterprise routes the call toward the node 4 in the network 0
Remark: if both prefixes are managed, the Network prefix has the priority.
Directory numbers can have up to eight digits in an ABC homogeneous network (each number is unique in the network).

Issue 02
27
X Routing in a homogeneous sub-network

Identification elements in a voice sub-network
Subnetwork
number
Node
number
Network
prefix
Node
number
Network
prefix
Node number
Network prefixes: one prefix = one set directory number

Routing prefixes: one prefix = a range of directory number

Each node must be identified by an index (Node number) in the sub-network. It must be defined in the database (for routing
telephone possibilities, remote access, Audit, Broadcast...).
Values by default further to the creation of an empty database are: network n0 - Node n1

Issue 02
28
24
X Communications routing principle in a backbone

User 3200
OmniPCX Enterprise routing application
Network resources status: to Node 3
Node 2
1st Possibility: Node1 directly to Node3

2nd Possibility: Node1 to Node3 through
Node 2
Node 1
Numbering Plan
Dialing: 3300
Node 3
Number: 3300
Network number: 0
Node number: 3
User 3300

25
The routing in an homogeneous sub-network is made by the routing application of the node which originally processed the call
(except for end nodes), according to its information (resources status, etc).
To be able to call a remote user, we have to know where this user belongs to (in which network, in which node). That could be done
by the Audit application or the creation of prefixes
Thanks to the Dynamic X25 Routing, all nodes in the backbone know the complete network topology. Thus they know the different
possibilities to reach the different nodes of the network. Each backbone node has the optimized path tree. Per destination, there is a
list of different paths.
Example explanation:
The user 3300 belongs to Node 3. In Node 1 database, 3300 corresponds to a network prefix. Thanks to this prefix, the Alcatel
OmniPCX Enterprise knows that when the number 3300 will be dialed, it will have to route the call toward the node 3, in the Network
0.
To be able to route this call toward Node 3, the Alcatel OmniPCX Enterprise uses the Routing Application and checks the optimized
path tree.
In Node 1:
First case: Node 3 is reachable through a direct link,
Second case: Node 3 is reachable going through Node 2.
Each path has a cost (a weight) value updated in real time depending on use of the link (% of use, out of order). The lower value will
be associated to the link which will have the most B channels free. And the routing application will select the path with the lowest
cost value.

Issue 02
29
X Communications routing principle

for end nodes
Provided by the corresponding
routing node
Routing node
30200
30200==network
networkprefix
prefix
associated
associatedtotonode
node2.
2.
--------------------------------------------------------------Route
Routecalculation:
calculation:
N4-N1-N2
: :cost
N4-N1-N2
cost66
N5-N1-N2
:
cost
N5-N1-N2
: cost22
Backbone
7
5
1
4
Database
Number: 30200
Network: 0
Node: 2
30200
2
End nodes

26
For an End Node, all calls will automatically be routed toward the Routing Node. An End Node has only one path for all destinations:
it is going through its Routing Node, after that, the Routing Node is in charge to optimize the routing (this node belongs to the
backbone, so it knows in real time the network status).
Number: 30200 (network prefix)
Network N: 0
Node N: 2

Issue 02
30
X Routing when using ABC trunk group

Elements identification: subnet-work and ABC trunk group
number
ABC_F trunk group
Subnetwork: 0
trunk group 10
Subnetwork: 1
trunk group 100
Node 1
Node 2
Node 3
Node 3
Node 1
trunk group101
trunk group 11
ABC_F trunk group
Node 2

27
The routing mechanism between different sub-networks is a little different than routing a call in a sub-network.
To call a remote sub-networks user, the Alcatel OmniPCX Enterprise has to know in which sub-network and with which bundle it will
be able to route this call. In that case we use some Routing prefixes and Network prefix also (but in that case there is no node
specification but a bundle identification).
All bundles (trunk groups) of a sub-network can be used by all users of this sub-network.
Between two sub-networks there is no real optimization because it is specified (in the routing prefix) which bundle will be used
(whatever its percentage of use). It is possible to use shared trunk groups to increase to possibilities to reach the remote subnetwork.
In a network of homogeneous ABC networks (called a supranetwork) or a QSIG network, the private numbering plan can be
heterogeneous (between homogeneous networks) and can support up to 20 digits.

Issue 02
31
X Synchronization
ISDN
T1/T2
Sync. prio.: 0
T1/T2
Sync. prio..: 0
Sync. prio..: 10
Sync. prio.: 20
Sync. prio.: 10

28
The synchronization functioning is the same in Network than in Stand Alone configuration. The Alcatel OmniPCX Enterprise gets the
synchronization from the link or trunk group (set up) with the lower synchronization value.
In a network configuration, all Alcatel OmniPCX Enterprise systems connected to the Central Office, must have the synchronization
level 0 managed in the used digital bundles (as shown above).
Also, in the network, a synchronization plan has to be set up. A master node could be defined to send the synchronization to the
others. Usually, this master node is the node with the most T2 connections
With the above example, it is just a choice to define the node which will send the synchronization. In that case, Node 3 sends the
synchronization (priority level: 0 and Node 1: 10). So, first Node 1 gets the synchronization from the T2 public trunk group and if this
bundle is out of order, it will get the synchronization from node 3.
Maximal synchronization priority: 0 (reception of the synchronization)
No synchronization priority: 255 (sending of the synchronization)
Remark: synchronization loops within the network must be avoided.
System clock synchronization sources:
- E1 (T2), T1, T0
- GD
- CPU
- INTIP
- ATM
- DECT8
- DECT4/DECT2 ( supported but not orderable )

Issue 02
32
Interaction with other features
X In a same homogeneous network, the Release 6.x can

interwork with all the releases from the Release 4.2 except
in case of Call Center environment: all the nodes have to be
in the same release
In case of VoIP: some configurations are forbidden =>
some engineering rules have to be applied: see next slide

R5.0 Ux
VoIP ?
Call Center ?
R6.x
R4.2
R5.1
R5.0 Lx
Homogeneous
Network

29
The engineering rules are described in:

The pre-sales communication design guide for OXE
The pre-sales presentation OXE R5.1 Networking design of VoIP solutions

Issue 02
33
X Engineering rules
Concerning the engineering rules, the R6.x is like the R5.1
except in case of TSC/LIOE or/and LIOE use in the network
The TSC/LIOE and the LIOE are not supported by the Release 6.x
except in case of ATM 2Mb/s (The LIOE used for ATM 2Mb/s is
supported)
In an homogeneous network having at least one node in
Release 6.x, the mixing of LIOE and INTIP is not supported
On all the nodes of the network using TSC/LIOE or/and LIOE, these
boards have to be replaced by INTIP
R5.0 Ux
TSC/LIOE & LIOE
R6.x
NOT SUPPORTED IN THIS

HOMOGENEOUS NETWORK
R5.0 Lx

Here are some reasons explaining why the LIOE (TSC/LIOE) is not supported by the release 6.0:
The direct RTP feature is not possible
The LIOE cannot interwork with a GateKeeper
The data/modem transparency feature is not possible with the LIOE
The LIOE doesnt support the T38 standard
The maximum echo cancellation depth is 16 ms
Upgrading to INTIP Hardware allows to benefit from the latest features available with the release 6.0

Issue 02
34
R5.1
30
X Interconnection of OmniPCX Enterprise with other Alcatel

PBX (OmniPCX Office, A4300L, A4300SM ...) is supported
through ABC F1/QSIG trunk groups
X No ABC link in peripheral areas (ACTIS). Except private
analog trunks (E&M, EMTL interfaces) with Peripheral
Crystal Media gateway.

31

Issue 02
35
Quotation and recommendation
X Actis is a configuration Tool for single system

configuration.
X However, in a solution design, the type of trunking
between one system and the others can be configured.
X One offer by node
X When designing a large network with different subnets, the
overall trunk design should be done globally


Issue 02
36
32
X What are the different aspects to take in to account to

build an OmniPCX Enterprise network?
Level of service requested by the customer
Topology
Number of locations
Capacity of each location
Possible leased lines or networks used (existing or new)
Numbering plan
Dimensioning
Traffic calculation (Erlang)

OmniPCX Enterprise provisioning level
Security issues
back-up solutions

33

Issue 02
37
X What are the different aspects to take in to account to

build an OmniPCX Enterprise network?
Centralized services:
Attendants
Voice mail
Public trunk group
Call Centre
Management
Group telephony
....
Cost effective solution
optimization of solutions and customer running costs


Issue 02
38
34
X TSC/LIOE & LIOE not supported

Example: N3 is added (new node) and N1 uses LIOE and
TSC/LIOE
Crystal Central Area / Central Area / Optimization

On this node I have
to replace the LIOE
and the TSC/LIOE
using ACTIS
v
N1
R5.1
N3
R6.x
IP
Homogeneous N2
Network
R5.0
Lx
Warning: in case of Release 4.2 or 5.0 Ux,

Actis cannot replace automatically the
TSC/LIOE
Add-on LIOE, so the patch before add-on
process has to be used

35
Actually the ACTIS wording means Replace TSC-LIOE and LIOE with INTIP2 boards

Issue 02
39
Reference documentation
In the Alcatel Business Partner Web Site (BPWS), under Pre Sales, you can
find further details in:
X Standard offer, section Distributed architecture and networking

X Presales presentations
Network concept (Release 3.2) Ed01
How to transport information through A4400 network Ed01
X System Documentation, section Functional Documentation MultiPABX Services

X Others (Feature List and Product Limits, marketing documents,
user guides, .)

http://www.businesspartner.alcatel.com

Issue 02
40
36
Conclusion
X In a project design framework, Alcatel OmniPCX Enterprise has been

providing by far the more flexible and strong offer to the PBX
Networking market. Its unique dynamic (adaptive) routing which looks
ahead for the optimized path has been put in place in many large
multinational organization
X Several homogeneous Alcatel OmniPCX Enterprise networks can be
linked together in supranetwork. Each sub-network retains its own
external connections, attendants, centralized applications, and
management, but ABC-F (Alcatel Business Communication Feature
Transparency) and local PSTN routing (ARS) services remain
consistent throughout the enterprise network.
X On private digital links, QSIG (signaling at point Q) and ABC-Fx
(Alcatel Business Communication Features) inter-node signaling
exchange protocols offer network level services usually available on
the PBX in stand-alone mode.

37

Issue 02
41
Conclusion
X In a network architecture, the OmniVista 4760 provides

Configuration on X communication servers at the same time
One single management platform to manage over 400
nodes & 20000 users (up to 50000 depending on the

applications used)
All management applications are centralized on the
management platform: configuration, topology, alarms,

accounting, performance, monitoring, directory, IP
performance.


Issue 02
42
38
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
Alcatel University https://www.businesspartner.alcatel.com
43
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
44
IP/X25 Tunnel

OBJECTIVES:
To define the ABC link D channel content
To identify and to describe services supported by the IP/X25 tunnel
Alcatel OmniPCX Enterprise IP/X25 tunnel

Issue 01
45
IP/X25 tunnel
Content
X Definition
X Examples
X Conclusion


Issue 01
46
IP/X25 Tunnel
Definition
X The IP/X25 tunnel carries out the information of

applications using IP stack in one X25 virtual circuit. This
applications are:
the accounting and past time performance file transfer
(FTP),
the configuration (cmisd),

the notification of alarms (rcp) sent to the OmniVista 4760
(with Ethernet connection): alarms subscription of the node,
the audit and the broadcast (rcp),

the remote login (rlogin).


Issue 01
47
IP/X25 Tunnel
Feature description
X ABC link content: the basic elements
ABC
ABC LINK
LINK
Classical
or
Hybrid, compressed
Sig.
Sig.
Voix
Voice
VoixVoice
Voice
Voix
Voix
Voice
Voix


Issue 01
48
IP/X25 Tunnel
Feature description
X ABC link signaling channel content
ABC
F2
Signaling
Channel
SAPI S
SAPI P
QSIG
GF
QSIG
BC
Level 3
X25
Level 2 (Q921)
SAPI S (0)
Level 2
SAPI P (16)/X25.2
Level 1

SAPI: Service Access Point Identification, information in the level two frames to indicate the type of the communication
SAPI value = 0, it is called SAPI S and it is used for voice communications
SAPI value = 16, it is called SAPI P and it is used for data communications
QSIG and ABC protocols are an enlargement of the ISDN protocol, based on the ISDN level three.
Three levels can be distinguished in the QSIG protocol:
QSIG BC: Basic Call
QSIG GF: Generic Functions
QSIG SS: Supplementary Services
Two levels can be distinguished in the ABC protocol:
ABC F1: Protocol used by the Alcatel 4300
ABC F2: Protocol used between two Alcatel OmniPCX Enterprise

Issue 01
49
IP/X25 Tunnel
Feature description
X Signaling channel X25 part content (tunnel)

Level 3 X25
Connected Mode
SAPI S
Signaling
Channel
SAPI P
X25
PLL:
communication
by Virtual Circuit
Non Connected Mode

-
PLL 0
Telephone routing
Call Distribution
Multiline
Supervision
CCD ...
Niveau
Level 22
SAPI
SAPI PP

PLL: Permanent Logical Link. Created automatically by the system when creating the ABC link.
VC: Virtual Circuit
TCP/IP applications (except the routing tables broadcast) use VC in the PLL while most of the telephone applications use the non
connected mode
Information on the PLL and the VCs (connected mode) can be read using the suproutage tool (available on the Call server Linux
interface through a V24 or Telnet connection)
It is not possible to trace information carried on non connected mode.

Issue 01
50
IP/X25 Tunnel
Feature description
X Signaling channel X25 part content (tunnel)
Level 3 X25
SAPI S
Signaling
Channel
PLL 0
SAPI P
X25
VC
Connected Mode
Non Connected Mode
PLL 0:
Using IPC (LCN) for

- Audit, broadcast
- Remote access
- MAO (4760)
- Files transfer ...
Telephone routing
Call Distribution
Multiline
Supervision
CCD ...
Niveau
Level 22
SAPI
SAPI PP

LCN: Logical channel Number

Issue 01
51
IP/X25 Tunnel
Feature description
X X25 Virtual Services (non connected mode)

Exchange principle: X25 packets
Non connected mode
A X25 packet contains:
Dialing X25 @ (origin node)

Called X25 @ (destination Node)
Information about:
Telephone dynamic routing

Network supervision
Executive/secretary
OmniTouch CC applications
Calls Distribution (attendant routing )
Trunks Supervision
...


Issue 01
52
IP/X25 Tunnel
Feature description
X Connected mode (tunnel)

When an application needs to send an information to one
or several nodes, the corresponding IPC will open a VC

(using a predefined rate) toward the remote node(s)
Example: Alcatel OmniVista 4760 connection through a T2 ABC link
Ethernet
T2 ABC link IP/X25 tunnel

CS
Node 1
PRA
IPC 134
IPC 134
In D channel
PRA
CS
Node 2
a VC is open at 9600 bits/s
OmniVista 4760 server connection on node 2: node 1 used as an IP/X25 tunnel gateway

IPC: Inter Processing Communication, virtual access point to an application

Issue 01
53
IP/X25 Tunnel
Feature description
X The X25 applications and Inter Process Communication
134: Audit, TCP/IP

X25
group
N Z
108: Broadcast
ABC link
Node X
IPC
108
IPC
194
X25 group
N 0
194: IP Routes
Broadcast
Application
IPC
184
IPC
134
Packet Handler:
Handler: handles the X25 traffic
IPC
183
184: Virtual service

specific channel
X25
group
N T
ABC link
Node Y
183: Hybrid Link

10
IPC: Inter Processing Communication, virtual access point to an application

IPC 134 is the TCP/IP applications access point, used by Linux applications such as ping, telnet, rlogin, FTP, and by the audit
application (CV at 9600b/s)
IPC 108 is the broadcast application access point used to send real time updates of the Alcatel OmniPCX Enterprise database over
the network.
IPC 194 is the access point used by the "gated" process to exchange TCP/IP routing tables between nodes in the network (uses a CV
at 600b/s)
IPC 184 is only used in case of virtual service rerouting: use of a support (e.g.: Customer LAN) allowing a higher rate, suitable for the
information flow (supervision, executive/secretary, etc) to be routed in the network.
What is called here the virtual service was called the non connected mode in page 4
IPC 183 is the access point used by the hybrid links (signaling over IP)
All those access points dialog with the PH (Packet Handler) that pilots the X25 traffic and put the information into X25 packets.

Issue 01
54
IP/X25 Tunnel
Feature description
X The flow rates on line
T0 ABC link
CS
PRA
Node 1
1rst access
2nd access
9600b/s
PRA
CS
Node 2
PRA
CS
Node 3
9600 b/s
Rejected !
X In this case, possible overflow by using:

Overbooking
Frame relay

11

Issue 01
55
IP/X25 Tunnel
Feature description
X Overbooking
Purpose: to increase the maximum number of VC that can
be set up into the PLL according to the VC rate flow

administrated
Use of an Overbooking coefficient (configurable) depending
on the used access link
T2 or T1CCS = 19200 b/s per VC, T0 = 9600 b/s per VC

IP = 9600 b/s per VC
Example with a T2
Global PLL rate = 19200 b/s with an overbooking coefficient of 8

gives the possibility to open in a multiplexing mode up to 8 VC (one
per direction and per IPC)
Consequence: the average VC rate is lower but more VC are opened

12
In the IPC configuration, it is possible to setup the connection rate. If the rate is different on the two Alcatel OmniPCX Enterprise, there
will be an automatic adaptation to the lowest rate.
To increase the traffic possibilities, an overflow coefficient can be used. It allows to increase artificially the VC theoretical rate.
The system estimates that the flow is not permanently 9600 bps and that the bandwidth really available is not fully used.
This is not valid in case of a permanent file transfer through the tunnel.
The system will accept to establish new VCs if the requested rate is less than or equal to the PLL maximum rate.
This is true until the sum of the VC rates reaches the PLL basic rate modified by the overbooking coefficient

Issue 01
56
IP/X25 Tunnel
Feature description
X Frame Relay principle

Call in Frame Relay only if the Called party can:
Works
Use
with IO2N services
Possibility to establish X25 communications in B (1 VC = 1 B channel)
the Frame relay protocol
Possibility to set up Frame relay communications (X VC = 1B channel)
X Mandatory hardware in Each Node

IP Crystal server: CPU5/3, CPU6/2 or CPU7
IO2N: extremity node and transit nodes
VC Multiplexing in the B channel

Limit: 64 kb/s
OBCA/VMU-OBCA: Extremity node only
No multiplexing of VCs in the B channel in transit

For each VC there is a B channel establishment

13
Remark:
Frame Relay feature is available only when an IP crystal Server is used ( CPU5/3, CPU6/2 or CPU7 )
!! NO FRAME RELAY IN TRANSIT ON OBCA/VMU-OBCA !!
Frame Relay restrictions:

- Cannot return on channel D: Frame relay from end to end
- Frame Relay on ABC link: YES
- Frame Relay on ABC trunk groups: NO
- No Frame Relay in case of multiplexors: Use of the OVERBOOKING

Issue 01
57
IP/X25 Tunnel
Feature description
X Case of an ABC link over IP

It is obviously (for bandwidth reasons) recommended to use
directly the IP network and not the IP/X25 tunnel when using
between two nodes
Audit and broadcast

FTP, Telnet ...
The Alcatel OmniVista 4760
IP ABC link
(IP/X25 tunnel)
LAN/WAN
CS
GD
Recommended
Node 1
GD
CS
Node 2
OmniVista 4760


Issue 01
58
14
IP/X25 Tunnel
X No specific license for this feature

15

Issue 01
59
IP/X25 Tunnel
X In the Alcatel Business Partner Web Site BPWS, under Pre

Sales, you can find further details and links to other
relevant documents:
Standard offer, section Distributed Architecture and
Networking
Pre Sales presentations:
How to transport information through A4400 network ed1

Network concept (release 3.2) ed1
Others (Feature List and Product Limits, marketing
documents, user guides, .)


Issue 01
60
16
IP/X25 Tunnel
Conclusion
X 2 Parts in D channel
SAPI S for ABC-F2 services control
SAPI P for data control
X The SAPI P supports:

X25 virtual services (Telephone routing, Call Distribution,
Multiline, Supervision, CCD)

PLL or Tunnel (Audit, broadcast, Remote access, MAO
(4760), Files transfer ...)
X The PLL requires more rate according the number of VCs.

2 possibilities to reserve more bandwith:
Overbooking
Frame relay
17

Issue 01
61


Issue 01
62
18
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
63
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
64
Audit & Broadcast

OBJECTIVES:
To identify and to describe the tools and processes used to update the database in a network:
Audit tool
Broadcast process
To prepare offer proposals
To be able to answer to RFP's
Alcatel OmniPCX Enterprise Audit & Broadcast

Issue 01
65
Audit and Broadcast

Content
X Definition
X Documentation references
X Conclusion
X Appendix


Issue 01
66
Audit and Broadcast

Definition
X The audit tool has been designed to facilitate consistent

network monitoring, reconfiguration, evolution and to
easily integrate voice mail.
X Broadcasting enables data consistency to be maintained in
real time:
when there is a change on a node, it looks after transmitting
the information relating to that change to the other

OmniPCX Enterprise.
X When a node is added in a sub-network, the audit

mechanism updates all databases in the other nodes.


Issue 01
67
Audit and Broadcast

X The Audit is a maintenance tool

Test of the databases coherency in the network
Simulation
Insertion of a new node in the existing network
Upgrade of the databases in the network
Update of the databases in the network
ABC links inactivated or out of service for a long time

The audit tool has to be used to check the databases coherency in the network (in that case, a simulation of the process may be
enough) or when there is a modification in the network topology (addition of a new node in the network, node isolated from the
network during a long time)

Issue 01
68
Audit and Broadcast

X Broadcast
Real time update of the nodes databases in the network
Creation, modification, deletion of database elements
Configuration
Objects selection (same as the audit application)
for transmission
for reception
according to the area
Nodes selection
Area definition (broadcast into area)

The objects to be taken into account by the broadcast application can be managed in the database through mgr or the 47xx.
The objects behavior in the audit application follows the broadcast configuration.
The area can be used to restrict the application for some objects that will be taken into account only in this area

Issue 01
69
Audit and Broadcast

X Broadcast principle
Database
Database
node1
node1
node2
node2
ABC Link
Broadcast
application
Broadcast
application
IPC 134
IPC 108
PH
D Channel
PLL
IPC 134
PH
IPC 108
IPC: Inter Processing Communication, virtual access point to an
application(see IP/X25 tunnel module)

This mechanism does not use any bandwidth on the B channels of the ABC links; only the signaling channel (D channel) is used.
The broadcast application uses the IPC 108 but also 134 (2 VC but not opened in the same time per direction).

Issue 01
70
Audit and Broadcast

X Broadcast mechanism
node 1
node 2
Database
Database
Create
Createuser
user31000
31000
ABC link
Configuration
Configurationof
ofobjects
objects
AB
Cl
Numbering
Numberingplan:
plan:Input/output
Input/output
Broadcast:
Broadcast:All
Allnodes
nodes
Buffer
Buffer
31000
31000network
networkprefix
prefixtotonode
node11
ABC
ink
6 Empty the buffer
End of timer of
broadcast buffer
4
node 3
Sequence
Sequenceinformation
information
node
node11LOG
LOGseq
seq55
(previous
seq.
(previous seq.++1)1)
File
File
31000
31000network
networkprefix
prefixtotonode
node11

The lupd.dat file is used to store the sequences number linked with the node number
The LOG file name is built with the node number and the sequence number: LOG.node.sequence

Issue 01
71
Audit and Broadcast

X Broadcast areas
AREA 5
AREA 1
N2
N1
N4
N3
Areas are defined in each node

Use of AREA files
AREA 2
N5
A working mode is defined for each object

Used by the audit and broadcast

There is no area coherency control (the system does not check that all the nodes defined in the same area are adjacent)
An area is made of adjacent nodes
An object can be sent out or received:
- to the network scale, no area control
- in the considered area
- no reception and transmission

Issue 01
72
Audit and Broadcast

X No specific License
X This feature is associated with the private network license
Enterprise Com Server tab, Com Server licenses menu


Issue 01
73
Audit and Broadcast


Sales, you can find further details and links to other relevant
documents:
Networking
System Documentation, section Functional Documentation
Multi-PABX Services ABC-F homogeneous private

network Audit and Broadcast


Issue 01
74
10
Audit and Broadcast

Conclusion
X Audit and Broadcast tools are used in the context of the

management of a PCX network in order to maintain the consistency of
their databases.
It allows full feature transparency across the network
This is a key benefit of the OmniPCX Enterprise compared
to the competition (OPEX benefit)
X The audit should be used on system start-up, when a node is added or

when a node is isolated or else in case of excessive duration or when,
for an undetermined reason, broadcast generates errors.
X 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.

11
OPEX = operational expenses

= day to day operations
+ maintenance operations + proactive management

Issue 01
75
Audit and Broadcast

Appendix
X The Audit maintenance tool

Three ways to use it:
Manually
Scheduled (specific date and time)
Periodically
Choice of the nodes to be updated

Choice of the objects to be updated
Common tables: 31 objects

Local tables:
30 objects

The programmed and periodic ways to perform the audit are not recommended.
The nodes that are taken into account by the audit application have to be managed first (the whole network, only one node, selected
nodes)
The database objects taken into account by the audit application have to be managed in the audit menu and are divided into two
parts:
- The common objects: the content of tables coming from the different nodes are mixed (non-existing information are added)
- The local objects: a reference is chosen among the nodes of the network and the content of its tables replaces the content of the
remote nodes tables.

Issue 01
76
12
Audit and Broadcast

Appendix
X Procedure for launching an audit

Save the database on each node
Tool: audit -l xxx
Simulation of reference building

Consultation of simulation results
Launching of the audit: reference building
Consultation of results
Simulation of ref. Database loading on the network
Consultation of simulation results
Launching of the audit: ref. Database loading on the network
Consultation of results

13
Each step corresponds to a choice in the audit application menu.

Audit creates and exchanges ASCII compressed files. The SQL server is not directly used.
xxx = FR0, GEA (language)

Issue 01
77
Audit and Broadcast

Appendix
X Audit example: the local node is the reference

Objects
Objectstotosend
sendtoto
N1
N1
AUDIT
AUDIT
building:
1 Reference
Reference building:
node 1
node 1
All objects
All objects
DATABASE
DATABASE
31 common objects
Voice mail titular
Trunk group
DDI translator
Numbering plan
X25 transcoding
Free numbers ranges
...
node 2
node 1
5 Transfer of 31 common objects

End of job acknowledgment 3
2 Request of 31 common objects
2
Update its tables

Update its tables
with N2 tables
with N2 tables
contents
contents
Update
Updateitsitstables
tables
with
withN3
N3tables
tables
contents
contents
R eq
u es
to
f3
End
1c
of
om
T
job
6 rans
mo
a
no
f er
ckn
bje
of
o
w
31
cts
com ledgm
ent
mo
no
4
bje
cts
8
Translates the database

Translates the database
files.Dat associated to the
files.Dat associated to the
31 common objects into
31 common objects into
ASCII files.
ASCII files.
Compresses these ASCII
Compresses these ASCII
files before sending them
files before sending them
30 other objects
Category
...
node 3
The
Thecontent
contentofofthe
the30
30other
otherobjects
objectsdo
donot
notchange.
change.
The
Thenode
node11database
databaseisisnow
nowthe
thereference.
reference.
31 common objects
Voice mail titular
Trunk group
DDI translator
...
31 common objects
Voice mail titular
Trunk group
DDI translator
...
Objects
Objectstotosend
sendtotoN1
N1
14
List of the 31 common objects
List of the 30 local objects
1 Numbering Plan
2 Phone Book
3 * Speed Dialing Number
9 * Voice Mail Dir.No
4 Trunk Groups
5 Entities
10 * VPN Overflow
14 * Classes of Service
6 Call Distribution tables
7 DDI Translation
15 * Access COS
16 * Phone Features COS
8 Voice mail titulars
11 Free Numbers Ranges List
17 * Business account code
18 * Cost Center
12 PIN (Personal Ident.No.)
13 Suffix Plan
19 * Tones
20 * Timers
22 Hunt Group
23 Progr.Keys
21 * Security and Access Control 24 * Flow Control
31 PSPDN Complementary Address
25 * Input Configuration
26 * Output Configuration
32 X25 Command
27 * Data menu: Logon
28 * Set-up
34 Entity Spd Dial Numbers Range
29 * V120
30 * X25 Packet Handler
35 Entity Outgoing State Hours
33 * Appli Rights
38 * Numbering Discriminator
36 Entity Incoming State Hours
39 * Caller Rights COS
40 * Public Access COS
37 Discriminator Selector
45 DID numbering translator
41 * Private Access COS
42 * Network Access COS
46 Access Prefix
48 Trunk group NPD selector
43 * Business Access COS
44 * Trunk Group Access COS
49 Skill Domain
50 Skill parameters
47 * Numbering Plan Description 57 * Connection COS / CLU
51 Ubiquity Assistant Template 52 Supervision keys

53 Recording Resource
54 ATM Address List
55 Call Restriction Service
56 RSI
59 SIP Dictionnary
61 Network Routing Table

Issue 01
78
58 * 4645 VM VPIM
60 * LDAP Phone Books
Audit and Broadcast

Appendix
X Audit example: the local node is the reference

AUDIT
AUDIT
loading:
1 Reference
Reference loading:
All nodes
All nodes
All objects
All objects
node 2
node 1
Reference
ReferenceDATABASE
DATABASE
31 common objects
Voice mail titular
Trunk group
DDI translator
Numbering plan
X25 transcoding
Free numbers ranges
...
Transfer of all objects
Objects
Objectsreceived
received
from node 1 on node
from node 1 on node
22&&33
31 common objects
Voice mail titular
Trunk group
DDI translator
Numbering plan
X25 transcoding
Free numbers ranges
...
End
of
job
ack
Tr a
nsf
no
wle
er
of
dg
al l
me
ob
nt
j ec
5
ts
30 other objects
Category
...
node 3
The content of the 30 other objects changes.

The content of the 30 other objects changes.
The node 1 database is the reference.
Update
Updatetheir
theirtables
tables
with
3
withN1
N1tables
tables
contents
contents
30 other objects
Category
...

15

Issue 01
79
Audit and Broadcast

Appendix
X Audit example: the node 2 is the reference

AUDIT
AUDIT
building:
1 Reference
Reference building:
node 2
node 2
All objects
All objects
DATABASE
DATABASE
31 common objects
Voice mail titular
Trunk group
DDI translator
Numbering plan
X25 transcoding
Free numbers ranges
...
Objects
Objectstotosend
sendtoto
N1
N1
node 2
node 1
Update its tables

Update its tables
with N2 tables
with N2 tables
contents
contents
Update
Updateitsitstables
tables
with
withN3
N3tables
tables
contents
contents
Transfer of all objects
Request of all objects
2 R
equ
est
Tr a
of
ns
3
f er
of
3
1co
30 other objects
Category
...
1c
om
mo
no
mm
bje
on
cts
ob
jec
ts
30 other objects
Category
...
node 3
The content of the 30 other objects are now the same as in the node 2.
The content of the 30 other objects are now the same9as in the node 2.
The node 1 database is now the reference.
The node 1 database is now the reference.


Issue 01
80
31 common objects
Voice mail titular
Trunk group
DDI translator
...
31 common objects
Voice mail titular
Trunk group
DDI translator
...
Objects
Objectstotosend
sendtotoN1
N1
16
Audit and Broadcast

Appendix
X Audit example: the node 2 is the reference

AUDIT
AUDIT
loading:
1 Reference
Reference loading:
All nodes
All nodes
All objects
All objects
node 2
node 1
2 Transfer of 31 common objects

DATABASE
DATABASE
31 common objects
Voice mail titular
Trunk group
DDI translator
Numbering plan
X25 transcoding
Free numbers ranges
...
End
Update their tables

Update their tables
with N1 tables
3
with N1 tables
contents
contents
of
job
ack
Tr a
nsf
no
wle
er
of
dg
al l
me
ob
nt
j ec
4
ts
30 other objects
Category
...
node 3

Objects
Objectsreceived
received
from
fromnode1on
node1onnode2
node2
31 common objects
Voice mail titular
Trunk group
DDI translator
...
30 other objects
Category
...
Objects
Objectsreceived
received
from node1on node3
from node1on node3
31 common objects
Voice mail titular
Trunk group
DDI translator
...
30 other objects
Category
...
17

Issue 01
81
Audit and Broadcast

Appendix
file:
file:lupd.dat
lupd.dat
node
node11LOG
LOGseq
seq44
node 1
node 2
2) <-- Request LOG 1.5
1) Send lupd.dat -->
File:
File:lupd.dat
lupd.dat
node
node33LOG
LOGseq
seq24
24
ABC link
node
node11LOG
LOGseq
seq55
node
node22LOG
LOGseq
seq99
1)
node
node33LOG
LOGseq
seq24
24
file:
file:lupd.dat
lupd.dat(N1)
(N1)
AB
Cl
Sen
ink
dl
2) upd
<- .da
-R tequ ->
est
LO
node
node22LOG
LOGseq
seq99
ABC
node
node11LOG
LOGseq
seq55
node
node22LOG
LOGseq
seq99
node
node33LOG
LOGseq
seq24
24
1 .5
Nodes
Nodes22and
and33request
requestLOG
LOGfile
file
LOG.1.5
LOG.1.5at
atthe
theend
endof
ofthe
thepolling
pollingtimer.
timer.
file:
file:lupd.dat
lupd.dat
node 3
node
node11LOG
LOGseq
seq44
node
node22LOG
LOGseq
seq99
node
node33LOG
LOGseq
seq24
24

When nodes 2 and 3 receive lupd.dat from node 1, they start their polling timer.
At the end of this timer, they ask to node 1 to send the LOG files

Issue 01
82
18
Audit and Broadcast

Appendix
file:
file:lupd.dat
lupd.dat
node 1 LOG seq 5
node 1
node 2
6) <-- send acknowledgement
5) Send LOG.1.5 -->
file:
file:lupd.dat
lupd.dat
node
node22LOG
LOGseq
seq99
node
node33LOG
LOGseq
seq24
24
ABC
node
node11LOG
LOGseq
seq55
node
node22LOG
LOGseq
seq99
5)
AB
Sen
C
dL
6)
O
<G
.1.5
- se
nd
-->
ack
no
wle
dg
node
node33LOG
LOGseq
seq24
24
File
FileLOG.1.5
LOG.1.5will
willbe
beremoved
removedwhen
when
node
1
will
know
that
node 1 will know thatall
allthe
theother
other
nodes
nodeshave
havereceived
receivedit,it,ororwhen
whenthe
thelimit
limitofof
20
files
LOG
files
is
reached.
20 files LOG files is reached.
(this
(thisnumber
numbercan
canbe
beincreased)
increased)
ABC
Broadcast
Broadcast
configuration
configuration
numbering
numberingplan:
plan:
incoming
incomingbehavior:
behavior:
Always
Alwaystaken
takeninto
intoaccount
account
em
ent
file:
file:lupd.dat
lupd.dat
node 3
file:
file:ERRLOG.1.5
ERRLOG.1.5
31000
31000local
localuser
user
node 1 LOG seq 5

node
node22LOG
LOGseq
seq99
node
node33LOG
LOGseq
seq24
24

19
ERRLOG files are generated when the LOG file content cannot be applied to the database (eg if the user already exists as a local
user)
There will be an incident for each LOG file received and for each ERRLOG file creation

Issue 01
83
Audit and Broadcast

Appendix
X Internal mechanisms
Database
Modification
Timer:
Broadcast buffer timer
File creation
LOG
area_cm_cb.sav
cm_cb.sav
Temporary files: 2 options
cm_cb.sav (network files)
Mode: sending
File used for objects not concerned by area
area_cm_cb.sav (area files)
Mode: sending
File used for objects concerned by area

Broadcast buffer timer is set to 10 by default and to 10 in case of object deletion.

During this timer, the database modifications are stored in the same temporary file before being transferred into a LOG file
By default, the Alcatel OmniPCX Enterprise stores 20 LOG files (old one are deleted in FIFO mode). It is possible to store up to 127
(except Hard disk limitation) files.

Issue 01
84
20
Audit and Broadcast

Appendix
X Broadcast application uses

IPC 108 and 134
Broadcast files
cm_cb.sav
LOG.N.Seq
ERRLOG.N.Seq
lupd.dat
&
&
&
area_ cm_cb.sav
A.Z.N.Seq
EA.Z.N.Seq
Broadcast management: using Alcatel OmniVista 4760 or mgr

File editing: LOG, ERRLOG
Using: prog_diff (from Linux interface)
Process: broadcast

21
The IPC 108 has to be operational for the broadcast to work properly.
The following files are stored in the directory /usr4/mao
cm_cb.sav & area_cm_cb.sav are the temporary files to store database modifications
LOG.node.sequence & A.area.node.sequence are the files to be transferred to the remote nodes
ERRLOG.node.sequence & EA.area.node.sequence are the errors files generated when receiving a file that cannot be taken into
account
The lupd.dat file is stored in database directory (/usr3/mao) and is used to store the sequence numbers
The nodes and objects selection as the area management are done by the management tools 47xx or mgr
The LOG and ERRLOG files can be read using prog_diff tool
In case the broadcast has failed (eg a node has been isolated during more than 20 files), it has to be reinitialized by the command
cleanbroad.
This command will erase the sequence counters, the LOG and ERRLOG files and the area files on all the nodes of the network

Issue 01
85


Issue 01
86
22
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
87
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
88

OBJECTIVE:
To identify and to describe the different centralized applications:

Supervision & executive / secretary group
Hunting groups
Calls distribution (attendants)
Incidents centralization
Alcatel OmniVista 4760: centralized management
Alcatel OmniMessage 4635 and 4645: centralized voice mail
DECT/PWT in network
Alcatel OmniPCX Enterprise Centralized applications

Issue 01
89
Content
X Definition
X Feature description
X Conclusion


Issue 01
90
Definition
X Alcatel Intelligent Networking provides you facilities as:

Remote set supervision
Manager/assistant groups
Hunting groups
Shared attendants
Centralized management
Centralized metering & alarms
Centralized voice mail
Networking of Voice mail systems
Mobility
ARS/LCR
Shared speed dialing numbers


Issue 01
91
Feature description
X Supervision
Database
Directory n 3345
Supervised Directory n:
2500
Database
Directory n: 2500
Supervisor Directory n:
3345
2789
BROADCAST
N1
ABC Link
N2
3345
3345
3340
2500
2500
3345
Set Supervision
#2500
2501
X25 Exchange

The creation of the key Set Supervision on the 3345 set is broadcast through the network to node 2.
Supervision information are directly sent through X25 (Maintenance PLL), it means that the data information (set ringing, set busy, set
idle) are sent in datagram mode to node 1.
Object supervision: free, partially busy, totally busy, ringing

Issue 01
92
Feature description
X Manager/assistant group
BROADCAST
N1
N2
ABC Link
Manager set
3000
Assistant set
2000
3000
3001
2000
2010
Assistant
Call
Screening
manager
Call
screening
Supervision
X25 Exchange
Unscreening

As in a stand-alone configuration, the Secretary Call key creation generates automatically the Executive Call key creation and viceversa.
Executive Call key Screening / Unscreening information are directly sent through X25 (Maintenance PLL)
Number of supervisions in network, per signaling links (1 supervision = 1 supervision key on multiline set or 1 boss/secretary couple
or 1 equipment supervised by BLF):
9600 b/s: 150
16 Kb/s: 150
64 Kb/s D channel: 500
64 Kb/s B channel: 8000
IP: maximum 8000, depending on bandwidth

Issue 01
93
Feature description
X Manager/assistant group
The Overflow assistant (assistant away key) must be on the
same node than the executive set
No discreet listen-in without beep through the network

No Manager/assistant direct display messaging in network
The assistant can not activate the manager screening from
its set using the screening supervision key

Assistant
of M1 & M2
ABC_F2
Manager 2
(M2)
Manager 1
(M1)
Overflow
Assistant for M1
Overflow
Assistant for M2

The overflow secretary is a third part, out of the executive/secretary group. The overflow secretary acts as a secretary when the normal
secretary press the absent key.
The discrete listen-in allows the executive to listen discreetly to a conversation, microphone inhibited, between a caller and the
secretary. The secretary is notified on his/her screen.
It is possible only:
when the incoming call was first dedicated to the executive, who had activated his/her filtering to
the secretary
when the secretary and the executive have a 4035
when a set supervision key is managed on the executive set, supervising the secretary with
ringing
A maximum of 500 Manager sets is available private network wide.

Issue 01
94
Feature description
X Hunting groups
ABC Link
N2
N1
1.
3.
2.
3000
Dials 3000

The hunting group is created on node 1 and it is broadcast in the other nodes. Then it is possible to manage sets of the other nodes
in the hunting group.
Sequential or cyclic hunting groups are available in an homogeneous network (ABC-F2)
Mechanisms:
- A new management data is created to design:
local group
network group
- The hunt group has to be created in a reference node. The choice of the this reference node is important to optimize the call
distribution:
node with the most important number of sets
node with external incoming calls
Broadcast of group states is done to the reference node.
Standby mode:
- In case of reference node failure, each local group works normally (master node or not)

Issue 01
95
Feature description
X Hunting groups
Features
DECT/PWT and multiline sets are authorized
Local distribution if ABC link is out of service
Group call pick-up
Direct call pick-up from a set which doesnt belong to the hunting
group
No parallel hunting group in network
Limits
200 groups per node
40 sets per group

Limits:
- The maximum number of network groups is 200
- The maximum number of groups (network groups and local groups) in one node is also 200

Issue 01
96
Feature description
X Call Distribution
CDT
CDT
day night F1
N1
F2
ABC Link
day night F1
N2
ENTITY 1
GROP1
F2
Voice
GROP 1 Mail
GROP2
GROP2
Overflow routing N
Overflow routing N
Entity 1 call PFX
Attendant group call PFX
CDT
night
jour
F1
CDT
day night F1
F2
OP 1
OP 2
F2
GROP2
OP 3
OP1
GROP 1
GROP 2
Overflow routing N
Attendant group call PFX
Overflow routing N
Individual attendant call PFX

An Attendant group is always located in one node but can be distributed on several nodes.
A node can have no Attendant
Flexible night service:
- a node can have no night answering set
- works private network wide: the night answering set can be local or distant to a node
- one night service possible per attendant, attendant group and entity
The routing of a call is always performed in the origin node of this call, that means in the node of the incoming call (source node)
Two cases are possible:
- Attendant groups are located on several nodes of the homogeneous network (distributed call distribution)
- All Attendant groups are located on the same node (centralized call distribution)
CDT: Call Distribution Table
- The CDT of the entities, attendant groups and attendants are broadcast in the network
- According to the prefix (OP, GROP, ENTITY), the related CDT is used to select the destination number.

Issue 01
97
Feature description
X Incidents application without centralization

Each node sends (to the Alcatel OmniVista 4760) and
display (in its O.S.) individually its incidents
- Alcatel OmniVista 4760

incidents application
- Terminal emulation
Alarms
Incidents filter
- Alcatel OmniVista 4760

- Terminal emulation
Alarms
Node 1
PPP/Ethernet
Alarms
Node 2
Node 3
Incidents filter
Incidents filter
10
All faults in the network are notified to the fault management tool via the IP/X25 tunnel or the Ethernet link.
It is recommended that the links between the Fault Management tool and the network nodes are permanent.
In each node, a filter lets you choose network faults to be handled by the Fault Management tool.
Remarks:
-
The Alcatel OmniVista 4760 incident application will display and archive the incidents sent by each node
Each node can also display and archive its incidents. These incidents can be consulted on each node using a
terminal emulation (V24/telnet).
Alarms
IP network
Incidents filter
Incidents filter
Node 2
Issue 01
98
Node 1
Incidents filter
Node 3
Feature description
X Incidents centralization in a network node

A node defined as the incidents Master node receives the
incidents from all the network nodes

Incidents filter
Node 1 Supervisor
Alarms
Ethernet
IP/X25 tunnel
Incidents filter
Node 2 Supervised
Alcatel OmniVista 4760

Incidents filter
Node 3 Supervised

11
Centralized incidents in a network node

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

Issue 01
99
Feature description
X Centralized management, charging & traffic observation
10.i.j.0
Node A
Setup:
Node A ->IP connection
Node B ->Access via IP/X25
Node B
IP/X25 tunnel
172.30.0.0

In the setup of the Alcatel OmniVista 4760:

Node A connection is made using Ethernet and node A is managed as a gateway to the IP/X25 network address
172.30.0.0 (automatically, the PC route list is updated with this gateway)
Node B connection is made using IP/X25, and the distant IP/X25 node address is managed. Node A will be the
gateway to access to the Node B.

Issue 01
100
12
Feature description
X Centralized maintenance and management

Remote login
Terminal
or
Telnet
Node 1
telnet
telnet172.30.1.2
172.30.1.2
Node 2
IP/X25 tunnel
Tunnel @ 172.30.1.2

13
The login application is a Linux application which is launched from a mtcl connection on HyperTerminal or telnet.
Then it is possible to access to the distant node 2:
1/ by opening telnet/HyperTerminal on node 1, connecting on mtcl account and then running login 172.30.1.2
2/ by running telnet 172.30.1.2 on PC (if Node 1 is managed as a gateway to the tunnel)

Issue 01
101
Feature description
X Centralized voice mail

4645 and Alcatel OmniMessage 4635
IMAP server can also be centralized
4645
4645
or
or4635
4635
IMAP
IMAPserver
server
ABC
ABClinks
links

It is possible to centralize the 4645 or the Alcatel OmniMessage 4635 Voice Mail System in an ABC network. This means that a
subscriber located on any node will have his/her own mailbox in the unique Voice Mail System of the Alcatel OmniPCX Enterprise
ABC network .
- This topology has the following advantages:
Lower price, single installation and management operations, single global directory for all the network
Resource optimization, fewer voice storage and ports, immediate delivery of all message..
Management of the mailboxes is integrated with the management of Alcatel OmniPCX Enterprise subscriber.
Mailbox management, (create/update/delete operations) is achieved along with the subscriber management in one single
operation.
The management of the application voice mail is made in the node which contains it, then the voice mail directory number is
broadcast to the other node. At this point it is possible to create mailboxes for the users.
The centralized management allows to manage all the mailbox owner from one node.

Issue 01
102
14
Feature description

User notification
ABC-F2
Signaling
N2
4645
4645
or
or4635
4635
N1
Notification
Notification

15
The Alcatel OmniPCX Enterprise ABC network guarantees the network transparency for all Voice Mail features as for example:
notification of the set
user guidance with softkeys on UA sets
...

Issue 01
103
Feature description
X DECT/PWT in Network
Roaming mechanism
Radio coverage
Radio coverage
ABC signaling
Empty Shell
3000
PARI 1
ABC link
Home
Node
A4444=3000
PARI 2
Visited
Node
DECT/PWT
DECT/PWTUser
User3000
3000
DECT/PWT
DECT/PWTUser
UserA4444
A4444
--IPUI
IPUINumber
Number
--IPUIO
IPUIONumber
Number
--Network
Networkmobility:
mobility:YES
YES
--Empty
shell:
Empty shell:NO
NO
--IPUI
IPUINumber
Number
--IPUIO
IPUIONumber
Number
--Network
Networkmobility:
mobility:NO
NO
--Empty
shell:
Empty shell:YES
YES

16
The network mobility allows to be registered temporarily in a node which is not the user home node.
The Alcatel OmniPCX Enterprise offers a service of distant mobility for DECT/PWT users. The system insures roaming for these users
between different nodes of an ABCF network which radio coverages are disconnected (not overlapping): this is the Roaming in ABCF
Network feature.
Remark: in this case, the communication will be lost during the roaming phase.
Working conditions
PARI:
The PARI numbers have to be known in each handset
IPUIO:
In order, for the set, to be recognized by the visitor node, the system gives an IPUIO number (22 octal digits)
calculated from its local directory number
When a set has an IPUIO number, its IPUIN number is not used anymore

Issue 01
104
Feature description
X DECT/PWT in Network
Registration on the visited node
The visited node , receiving the IPUIO at the handset start-up,

deduces the set directory number and establishes a connection with
the origin node
If this set has the right for the network mobility (roaming) and if a
free empty shell is available, the visited node requests for
information about this handset to transfer them in the selected empty
shell (ABC-F2 protocol)
The empty shell is released
when the handset connects to the origin node

when the handset connects to another node
If there is no traffic through the shell for the last 48 hours

17
Basic parameters sent from the local node to a visitor node:

- identification (name, password)
- authorizations (forwarding, teleservices, categories, complementary services)
- services (accounting indicators, set facilities)
- destination numbers (for forwarding, for overflow)
Other parameters sent from the local node to a visitor node:
- entity number
- language number
- associated number
- cost center
- charging category, public network access category, connection category, phone facilities category
- ISDN teleservices validated or not
- called number masking in charging tickets
- call by name / mini message authorized or not
- UUS access code
- ringing and audio parameters
- DECT/PWT paging overflow parameters
- The programmable keys (type and content)
- the content of the entries in the individual repertory

Issue 01
105
Feature description
X Shared trunk groups

Physical accesses belonging to different nodes in the same
trunk group
One
prefix to seize the different available accesses
X Speed dialing numbers

Could be common to several network
X Multi-tenant: one entity could cover several nodes

X Call restriction: configuration rules could be broadcast in
the ABC network (common alarm level and behavior)
X MLPP: precedence and preemption on ABC link or trunk
group


Issue 01
106
18
X Attendants in network
Central area, Attendants
X DECT/PWT in network
Central area, Mobility
X DECT in Campus (Crystal IP media gateway)(Not in US)

Central area, Mobility

19
Centralized BLF
For a network configuration, if the BLF (Busy Lamp Field) application is installed on a remote node, it can show the junctor statuses of
both nodes without having to purchase an additional license. Actis configures the PARA_MAO 6 in the hardware.mao file to activate
the ABC-A module in the node.
DECT/PWT for outgoing roaming
Roaming is a privilege that enables DECT/PWT sets already declared in the installation to exit their node and be automatically
recognized on another node in the network.
In the node which welcomes the roaming DECT/PWT sets, the number of mobile terminals must be increased in order to manage the
local DECT/PWT + network DECT/PWT traffic.
Caution: The roaming function is nominative for each mobile set, this right is assigned via PBX management. So, all sets with rights to
this feature must be declared.
Licenses are delivered in levels - each level is for 10 sets.
Campus (Not available for US market)
Designed for large installations consisting of several networked PABXs on a single site, the Campus service enables a DECT user on a
call to transfer from one node to another without interrupting the call. This functionality is also known as "External Handover".
In addition to the ABC-F link, each node with DECT couplers is connected to a central node via fiber optic links using INTOFS cards.
The central node controls the DECT synchronization pulses.
Only Mobiles sets support the Campus service. Other units cause call recovery on transfer from one node to another.
Campus: The Campus service is provided on the installation.
Campus main node: The node in this configuration is declared as the Campus main node. Actis configures as many INTOFS cards on
this node as there are secondary nodes in the campus.
Box unchecked: The node in this configuration is a secondary node. Actis configures one INTOFS card with COST-MU daughter
board (optical fiber link for a distance between 600m and 4Km) and forces the CPU6 card on this node for the synchronization
requirements.
If the distance is longer than 4Km between the master node and the secondary node, you may order manually (Additional hardware)
a COST-MO daughter board (distance up to 12Km) and the VH PATCH PANEL COST MU module (only for VH).
Campus secondary nodes: Enter the total number of secondary nodes on the campus. This number cannot exceed 7. Actis uses this
field to configure the number of INTOFS cards on the main node.

Issue 01
107
X Remote management ( Crystal IP media gateway)

Central area, Private network
For CPU6 only
OR
X Alarm centralization
If Faults and alarms only
20
Maintenance / Network management

Remote maintenance and centralized management use a D channel when two nodes are connected through an ABC-F link. If higher
bandwidth is required, a B channel can be used to transmit 47XX remote maintenance or centralized management.
Network remote maintenance via B channel
Allows remote maintenance functions (Management, alarms, etc.) using a B channel between the nodes. This option requires an
OBCA2 or IO2N board to be ordered.
Centralized 47xx management via B channel
The 47XX management application directly connected to this node will be able to access other network nodes via the B channel. This
option requires an OBC2 or IO2N board to be ordered.
SNMP and HPOV Traps
Traps are alarm or incident messages sent to a management platform by the PBX. This protocol is commonly used by routers and
PBXs. HPOV (Hewlett Packard Open View) is a software program developed by Hewlett Packard, designed to be installed on a PC or
UNIX platform to provide an SNMP compatible data management platform. This platform enables, for example, a graphical
representation of network topology - each element being symbolized by an animated icon with an indication of its status.
With a view to merging voice/data, a manager using an HPOV platform can thus get a direct view of the status of their equipment,
data and PBX - without using the 47XX application.
This menu box is used to configure the use (or denial) of SNMP protocol for alarm transmission, file transfer to the HPOV station, and
use (or denial) of CMISE protocol for alarm transmission.
SNMP process
Box checked: The PBX uses SNMP protocol to transmit alarms. These alarms are also transmitted with CMISE. Actis automatically
checks the checkbox of the "Failures and alarms" section and configures: the SNMP license, and the "Failures and alarms" licenses
according to the number of users.
For a PBX network, this section must be completed for each node.
Box unchecked: The PBX does not use SNMP protocol to transmit alarms.
Failures and alarms
The PBX uses CMISE protocol to transmit alarms to another network node which is itself connected to a HPOV platform, for example.
Licenses are configured according to the number of users:
Number of users
128
128 to 250
250 to 500
500 to 1000
1000 to 1500
> 1500
Number of licenses
12
16

Issue 01
108

Voices services, voice mail
4645
4635
Allow the user of this node to have voice mail box on
another node

21
4645 voice mail capacity

Users mail boxes
This heading indicates whether or not the subscribers to the node of the offer access 4645 voice mail that is local or located on
another node.
Box checked: The subscribers to the node access 4645 voice mail that is located on this node or on a remote node. Actis issues the
licenses in blocks according to the size of the Com server engine.
Box not checked: The subscribers do not have 4645 voice mail. This can be useful if the node under consideration supports voice
mail intended for the subscribers to another node.
Centralized voice mail for 4635
For a network comprised of a voice mail service on a central node and offering voice mail service accesses to other, satellite nodes,
only check this box on the satellite nodes.
Actis issues the licenses in blocks according to the size of the Com server engine.

Issue 01
109

relevant documents:
Networking
System Documentation, section Functional
Documentation

Roaming
in network (release 3) ed2

DECT over Campus (release 4.2) ed1a
How to quote DECT/PWT in network (OXE R5.1) ed2h


Issue 01
110
22
Conclusion
X Alcatel Intelligent Networking technology allows you to

easily establish a pool of attendants across multiple sites
Consistent and reliable greeting
Improve emergency communications
Reduce staffing costs
X Alcatel Intelligent Networking provides an easily managed

and cost effective Centralized Voice Mail service to all
employees across the Enterprise improving communication
between:
Executives and line managers
HQ and branches
HQ and remote workers

23

Issue 01
111


Issue 01
112
24
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
113
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
114

OBJECTIVES:
To be able to answer RFPs regarding voice mail in network
To be able to present the advantages and drawbacks of a voice mail system on each node versus centralized voice mail
Alcatel OmniPCX Enterprise Voice mail networking

Issue 01
115

Content
X Introduction
X VPIM
Definition
Feature description
X Octelnet
Definition
Feature description
X AMIS
Definition
Feature description
X Provisioning level
X Conclusion


Issue 01
116

Introduction
X Voice mail network principle

allows subscribers with mailboxes on one voice mail system
to exchange messages with subscribers on other voice mail

(mailbox to mailbox)
extends the use of voice messaging from a single location to
many locations
X Voice mail networking is used when:

Within an OXE network, a voice mail on each node is
prefered to a centralized voice mail solution
The networking of voice mail allows features transparency across the

network
A customer owns Pabxs from different vendors and would
like to use the connection between the telephone systems (IP

or other) to network its voice mail systems


Issue 01
117

Introduction
X Several solutions can be used

VPIM is a standard used by many vendors and works with
both 4635 and 4645
Octelnet (analog) and IP Octelnet can be used with the
4635 and any other Octel voice mail systems
AMIS is a standard used by many vendors but allows very
basic features


Issue 01
118

VPIM/Definition
X VPIM
Voice Profile for Internet Mail v2 specification RFC 2421 of
EMA (Electronic Messaging Association)
Voice mail system digital networking protocol
Allows
Interconnection of Voice Mail Systems (4645 and4635 or others)

Exchange of voice messages between users having Voice Mailbox
defined on different system/node
X Integration with the OmniPCX Enterprise
Reply to message, Call Back Sender, .

Distribution List
Uses ADPCM32 format for messages encoding, MIME for e-
mail formatting, SMTP for the transport

VPIM: Voice Profile for Internet Mail

RFC 2421: VPIM version 2 r2
The goals of the Voice Profile for Internet Mail Work Group include establishing an internationally accepted standard profile of
SMTP/MIME to allow the inter-exchange of voice and fax messages between voice messaging systems
Network Node: VPIM capable messaging system with an active TCP/IP connection
Network Mailbox: entry in the local dialing plan referring to a mailbox of a distant voice mail system
SMTP: Simple Mail Transfer Protocol

RFC 821: SMTP
The objective of Simple Mail Transfer Protocol is to transfer mail reliably and efficiently
MIME: Multipurpose Internet Mail Extensions

RFC 1522: MIME
MIME means Multipurpose Internet Mail Extensions, and refers to an official Internet standard that specifies how messages must
be formatted so that they can be exchanged between different email systems

Issue 01
119

VPIM/Features description
X Networking voice mails with VPIM: 3 possible topologies

Networking with a different voice mail
CS + 4645
IP
Network
VPIM
compliant
system
Network of similar voice mail (two 4645)

CS + 4645
IP
Network
CS + 4645
Domain of similar voice mail systems (two 4645)

ABC-F
Network + IP
Network
CS (Node 1) +
4645
CS (Node 2) +
4645

VPIM: Traditionally, messages sent from one voice messaging system to another were transported using analog networking protocols
based on DTMF signaling and analog voice playback. As the demand for networking increases, there was a need for a standard
high-quality digital protocol to connect these machines. VPIM has successfully demonstrated its usefulness as this new standard.
The VPIM protocol allows the user to record his voice message and then to specify the address of the distant which should receive this
message. It uses ADPCM (Adaptive Differential Pulse Code Modulation) 32 K to encode the message.
In the same way, an image or a fax can be encoded into TIFF format. Then VPIM convert the message (attached file) using MIME
(Multipurpose Internet Mail Extensions) protocol,and send it using a simple mail transport protocol (SMTP) or an enhanced version
(ESMTP).
As VPIM uses Internet network standard (MIME or SMTP), it can operates with other messaging system. It allows the localization of the
address of the destination mail box and the send of the message through internet. The message can be retrieved using POP or IMAP
server as any ordinary e-mail.

Issue 01
120

X Networking 4645 with another type of voice mail

The VPIM protocol transmits a message to a remote voice
messaging network (Alcatel 4635, 4645 or a voice

messaging system from a different vendor)
This message is made up of:
a voice content, spoken name content, mailbox number and mailbox

name, ...
To let the user address mailboxes in remote nodes,
manually configured prefix codes are used to uniquely

identify them in the local numbering plan.
Basic voice messages features
send message, reply message

The user has to have the knowledge of the prefix code and the mailbox number in the destination node to correctly address
messages.
"Reply" is possible, if the originating node provides a valid "From:" (or "Reply-to:") address field. Reply is not possible
when the message header field "From: non-mail-user@domain" is found (typically for messages left in telephone answering mode
without CLI).

Issue 01
121

X Networking similar voice mails (two 4645) with VPIM

If the 4645 voice-messaging network is not contained within
the same OmniPCX Enterprise Call Server network, a

unique numbering plan cannot be assured
a prefix code for each destination voice mail node to reach has to be
managed
Basic voice messaging features, such as Send Message
are possible, but the user has to have the knowledge of the
prefix node number and the mailbox number in the
destination node.
The features Dial by Name and Spoken Name
Confirmation for a specific remote mailbox become

available after the first message from this remote mailbox
has been received via the 4645 network.
Prefix node number:prefix which uniquely identifies a voice mail node in the numbering plan.
Note:The address information (prefix number+mailbox number, mailbox name, spoken name) is kept in a local cache and might get
outdated when time passes by.

Issue 01
122

X VPIM domain of similar voice mails (two 4645)

4645 domains are 4645 systems networked using
OmniPCX Enterprise Call Server network capabilities and

sharing a homogenous telephone numbering plan not
requiring prefix codes to address destination voice mail
nodes.
Mail box number or dial by name to reach the destination mail box
Basic voice messaging features, such as Send Message,
Reply, Call Sender, Distribution List Expansion, Dial

by Name and Spoken Name Confirmation are
transparent to the user independent, whether it crosses
system boundaries over the network or not.

Note: In the first 4645 VPIM implementation, the scope of some Automated Attendant features is restricted to the local Voice Mail
Node.

Issue 01
123

X VPIM encoding
Audio
G711
G726
e-mail
Binary
Base64
X Temporary disk space needed for voice messages

Message Length
G.726
G.726 Base 64
G.711
G.711 Base64
2 minutes
480 Kb
~640 Kb
960 Kb
~1,3 Mb
5 hours
72 Mb
~96 Mb
144 Mb
~192 Mb

Audio Encoding: Type of compression algorithm to be set according to the bandwidth between the local node and the remote node.
Compression is used to reduce bandwidth consumption, but requires transcoding which takes up considerable CPU time:
- G.711: not compressed
- G.726: compressed
Recommendation G.726 [G726] defines the characteristics that are recommended for the conversion of a 64 kbit/s A-law or m-law
pulse code modulation (PCM) channel at 8000 samples/second to and from a 40, 32, 24 or 16 kbit/s channel.
Email Encoding:Type of encoding to be set according to the IP network. The type of coding depends on the capacity of the remote
node to decode. 4645 supports both types of encoding:
- Binary: encoding resulting in less cumbersome e-mails than base 64 encoding, but which is not supported by all systems
- Base 64: encoding resulting in more cumbersome e-mails than binary encoding.
Base64: To insure that email messages containing images or other non-text information will be delivered with maximum protection
against corruption, MIME provides a way for non-text information to be encoded as text. This encoding is known as base64.

Issue 01
124
10

Octelnet/Features description
X OCTELNET protocol principle

An analog network is configured when the remote nodes
are linked together through a public or private operator
George
You have received a

message from
"George" on the
"Washington" node
mailbox
4635
4635
Paris
Washington

4635
Jacques
mailbox
11

Issue 01
125

X OctelNet protocol features

OctelNet is a proprietary protocol of OCTEL company, so
the different nodes of the networks have to be OctelNet

compatible
OCTEL range
Alcatel OmniMessage 4635
Subscribers on the OctelNet network can record voice
messages on their local node and send the messages to

subscriber mailboxes on other nodes in the network
When subscribers are asked to enter the message
destination, they enter a network address which identifies

the remote node and the remote mailbox number


Issue 01
126
12

X OctelNet protocol features

The Namenet feature allows subscribers to address network
messages by spelling the recipients name instead of

entering the recipient mailbox number
Same level of functionality for remote or local mailboxes
Urgent,private,future delivery.. Messages
Messages for the remote node can be stored in a waiting
queue and can be sent in one time, according to the time

range and according to the message emergency degree, so
money can be saved

13

Issue 01
127

X IP OctelNet protocol
Allows customers to connect their Alcatel OmniMessage
4635 to their LAN in order to transmit voice and fax

messages over existing WANs
An digital network is configured when the remote nodes
are linked together through IP
Offers the possibility of connecting up to 1000 Alcatel
OmniMessage 4635 Worldwide
Can be used on any private or public network that supports
TCP/IP


Issue 01
128
14

X IP OCTELNET protocol benefits:

Lowers transmission costs
using the cost-effective existing LAN
Perfect transmission quality
messages are digital from one server to another
Improved delivery speed
the messages are delivered in seconds not minutes
Improves voice port throughput for other applications
the voice port are not used for network traffic
Improves message security
Message encryption
Analog Fallback message delivery (see next page)

15
Using the existing LAN/WAN architecture eliminates the low speed and higher cost transmission through normal telephone links.
There is no intermediate conversion from digital to analog and back that eliminates the loss of sound quality.
The delivery will depend on the speed of the lines connecting the Alcatel OmniMessage 4635. Example: a direct connection at
10Mbps will transfer a one minute voice message in 3 seconds.
All messages are encoded with a proprietary algorithm, providing a high level of security.

Issue 01
129

X IP Octel Networking with analog network as a backup

Ensures the transmission of messages through the central
office in case of LAN/WAN unavailability
Alcatel OmniPCX Enterprise

+ Alcatel OmniMessage 4635x

+ Alcatel OmniMessage 4635x
Central
office
Mailbox 3001
Mailbox 5001
LAN
LAN
WAN
Client PC
ROUTER
ROUTER


Issue 01
130
Client PC
16

AMIS/Definition
X AMIS protocol
AMIS: Audio Messaging Interchange Specification
AMIS protocol is usable in an analog network (when the
remote nodes are linked together through a public or

private operator)
This protocol allows messages to be sent to voice mail
systems not capable of OctelNet or VPIM
AMIS is a standard and is widely used

17

Issue 01
131

AMIS/ Features description
X AMIS protocol extends voice messaging from a single

voice processing vendor to many vendors at many
locations
X AMIS has fewer features than OCTELNET, indeed it
doesnt recognize the standard delivery options available
to subscribers:
No acknowledgement (message confirmation)
No concept of message priority (urgent, private..)
No future delivery messages
X A transmission-acceptance table can be activated in order

to selectively accept or block AMIS networking calls to the
voice mail from remote nodes


Issue 01
132
18

Provisioning level
X VPIM with 4645

Maximum number of network nodes:
255
Maximum number of network mailboxes:
48000
Maximum size of VPIM messages:
5 hours
Check receipt function is not available

19
VPIM and 4645:

The feature Check Receip is not possible over the network, it is only available from mailboxes on the local node. If the user tries to
check the receipt of messages deposited in mailboxes on remote nodes a phrase will be played to notify the user that it is impossible.

Issue 01
133

Provisioning level
X VPIM with 4635

Maximum number of network nodes:
500
Maximum number of network mailboxes:
50000
X Octelnet IP with 4635

Maximum number of remote nodes: 999
Maximum number of entries in Namenet directory:40000
Maximum message duration:30 min
Maximum number of messages per Network Call: NL
X AMIS with 4635

Maximum message duration: 8 min
Maximum number of messages per Network Call: 9

NL: no specific limit

Issue 01
134
20

X 4645 voice mail

21

Issue 01
135

X 4645 voice mail


Issue 01
136
22

X 4635 voice mail

23

Issue 01
137

X 4635 voice mail


Issue 01
138
24

X 4635 voice mail

25

Issue 01
139

X In the Alcatel Business Partner Web Site BPWS, under Pre Sales, you
can find further details and links to other relevant documents:
Presales\Virtual Presales Support\Standard Offer documents
Presales\Virtual Presales Support\Product and release
description\OmniPCX Enterprise R6.0
Feature List, Product Limits, Global Offer, Release Description
Presales\Presentations\Actis\How to quote series\
How to quote IMAP4 and 4635-4645 OXE R6.0
Presales\Presentations\Messaging solutions\
VPIM and 4635/4645 OXE R6.0
System Documentation
Others
Marketing documents
User guides


Issue 01
140
26

Conclusion
X Voice mail networking allows subscribers with mailboxes

on one voice mail system to exchange messages with
subscribers on other voice mail (mailbox to mailbox). It
extends the use of voice messaging from a single location
to many locations
X Several solutions can be used
VPIM for both 4635 and 4645
Octelnet (analog and IP)and for 4635 only
AMIS for 4635 only

27

Issue 01
141

Conclusion
X Centralized Voice mail or a voice mail on each node?

Advantage and drawback of each solution should be
presented to the customer:
centralized voice mail
advantage: need for hardware only on one node

drawbacks:
traffic on the IP network link meaning need for compression resources

(cost in terms of licenses needed and hardware for the VoIP board)
the voicemail users licences are mandatory anyway on each node (if
4645)
a voice mail on each node
advantage: local access to the voice mail so no traffic on the network

IP link
drawbacks:
cost of hardware on each node

usually requires the voice mail networking license for transparency (dial
by name across the network)


Issue 01
142
28
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
143
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
144
Network Overflow Solutions

OBJECTIVES:
To describe and to identify the VPN overflow mechanism
To describe the Private to Public overflow mechanism
To prepare offer proposals
To be able to answer to RFP's
Alcatel OmniPCX Enterprise Network Overflow solutions

Issue 01
145

Content
X Definition
X Conclusion


Issue 01
146

Definition
X Virtual Private Network (VPN) Overflow

When an ABC-F link is saturated (T2, T1, T0, IP ,hybrid,
compressed)
Mechanism used to face up to the peak of communication traffic at any

moment of the day
Overflow of the voice and data through another media (public operator)
Maintenance of the proprietary ABC-F2 protocol
X Private to public overflow

When an ABC-F link is saturated or out of service
Overflow of the signaling and the voice through another media (public
operator)
Loss of the proprietary ABC-F2 protocol
ex: ISDN signaling level


Issue 01
2
147

Feature description
X VPN Overflow: Complement to the ABC-F network features

If the ABC link is saturated
VPN overflow does not work if the ABC link has broken-down
The ABC logical link supports the signaling through a D channel
The public (ISDN/PCM R2) or private network (PCM, Tie-Line, ) supports
the voice & data
Bandwidth optimization: used during peak hours

Maximum of simultaneous supported voice/data calls per D
channel
T2 and IP = 60, T0 = 8, T1 CCS = 46
Connection to a node with low traffic
Example: ABC link with voice/data over ISDN with signaling over IP

VPN: The purpose of the VPN is to overflow on the trunk groups of the Central Office when the ABC-F link is saturated and to
maintain the proprietary protocol ABC-F
- This service is used in complement to private networks using:
- leased lines: nodes are connected with digital leased lines.
VPN when all trunks are busy
- without leased lines: for small nodes at the periphery of the network, small traffic does not justify leased lines. With
this service it is possible that all the network calls go through the public network.
Always VPN, no trunk managed = saturated link
- The manager of the network can adjust the required leased line bandwidth to carry the nominal traffic. The traffic peak during busy
hours will overflow. The benefit is the cut of the running costs of the leased line ( avoids using a larger bandwidth leased line ) while
improving the service to users during busy hours.
- When the leased line is busy, a call will overflow on the public ISDN network. But the users will benefit from ABC services (thanks the
D channel of the busy leased line) as if the call was on the leased line.
ABC VPN is transparent for the user: he/she does not know that the call has overflowed

Issue 01
148

Feature description
X VPN Overflow: Features

Signaling service level: ABC-F2
Support all types of communication
Network users and incoming trunks, voice and data
Optimization by the routing protocol
ABC-R
Barring to the service
For some or all users (based on configuration)

Routing:
- In case of a call from one node to another in a "meshed" network, i.e. with several routes possible, the adaptive routing calculates
the cheapest VPN route to join 2 nodes in case of saturation.
The adaptive routing will take into account a cost associated to each VPN jump: a VPN jump is a virtual route over the public network
which links 2 nodes, adjacent or not.
User rights:
- As each call on the public network increases the bill, some people can be barred from using the public network in case of ABC VPN
call. This will allow to further cut the running costs of network, while providing a good level of service.

Issue 01
3
149

Feature description
X VPN Overflow: Mandatory elements

ABC link and Hybrid link (with/ without compression)
Permanent link ( not on request )
Outgoing / incoming ISDN or private trunk groups
Not necessarily dedicated to the service
DID Number range or directory numbers used for VPN
service
It is necessary to define some prefixes called VPN overflow prefix
2 maximum number of VPN jumps between 2 subscribers
inside the sub network

It's possible to create a permanent overflow if the accesses are defined without B channel (e.g.: voice over IP between 2 adjacent
nodes).
With this mechanism, the architecture for signalling can be different of the voice architecture
This mechanism can be coupled with the ARS mechanism (Automatic Route Selection) when the accesses to the public network are
done through various operators.
Care:
The communication path between two subscribers distributed in a sub-network OmniPCX Enterprise can only consist of a maximum of
two VPN overflows.
This function is not compatible with the on request ABC accesses.
It's possible to define many VPN jumps between a end node and different backbone nodes to reach another end node. But when the
ABC link is busy between the end node and the backbone, it's always its VPN jump which is selected whatever the cost of this one.

Issue 01
150

Feature description
X VPN jumpsdesign consideration

A VPN jump is a virtual link through the public network
between two nodes (only one VPN hop between two nodes).
VPN hops
B
B
B
Public
Network
ABC-F2 link
Link is busy
ABC-F2 link
ABC-F2 link
Link is busy


Issue 01
11
151

Feature description
X VPN Overflow: Prefixes

Local VPN prefixes
DID numbers transmitted by broadcast all over the network
They are transformed into distant VPN prefixes (see next slide)
At its creation, a Numbering Plan Descriptor number is assigned: it

allows to build the installation number
ex: 0297333100
Transmitted to the calling node through ABC-F2 signaling

to be able to dial back the called node using the VPN
Used during the call establishment only


Issue 01
152

Feature description
X VPN Overflow: Numbers

Distant VPN prefixes
Created automatically by broadcast
Used to dial back over the Central Office
Prefix information: 2 solutions
1: Use of the external call back translator
1 to 4000: Use of ARS routing table


Issue 01
7
153

Feature description
X VPN hop using the external callback translator

Call to 3200
Saturated link
VPN service request
N1
VPN Table
3200
3299
Correlation
N2
7
D
4
3100
Distant VPN prefix

3299
prefix info: -1
3299 9782603299
3200
5
Public
Network
Ext. callback translator

DEF: 978260
Digits to add: 0
6
9782603299
3299
Local VPN prefix
prefix info: 33
(NPD)
NPD 33
INST N: 978260

10
Steps of the VPN call establishment:

1: The set 3100 ( node 1) calls the set 3200 (node 2)
The link is saturated between Node 1 and Node 2 Through the D channel a VPN request is made to node 2
2: Once the N1-request is received, the node 2 searches for a free (=not already used by another VPN hop) local prefix.
The prefix 3299 is selected.
In a dynamic table, a correlation is made between the local prefix 3299 and the called number 3200. This
correlation will be used when node 2 will be called back by the node 1 through the Central Office.
3: In the definition of the local prefix 3299, one NPD is assigned.
In this NPD the installation number 978260 of the Node 2 is managed in order to be called back by the node 1.
4: Through the D channel, two elements are sent to the node 1
- the local prefix 3299
- the entire number to be called back: 9782603299
5:Once these information are received, the node 1 searches the distant VPN prefix corresponding to the local one:3299
In the definition of the distant 3299 prefix, the prefix information value -1 indicates that the system has to use the
external callback translator .
The external call back translator is used to understand the second element 978260, the information Digits to
add 0 does not indicate the public trunk group to use. The trunk group usable for the VPN hop is specified in
the definition of the vpn hop between node 1 and 2 (trunk group supervised by routing).
6: The node 1 seizes one public trunk group usable for the VPN and calls 9782603299
7: The node 2 receives the incoming call
The system finds in the correlation table the association between the local prefix 3299 and the called number
3200
The set 3200 is rung and the prefix 3299 is released in the correlation table. 3299 is then usable for another VPN
hop. Having several local prefixes managed means being able to have several simultaneous call
establishment

Issue 01
154
11

Feature description
X VPN hop using ARS Table

2
Call to 3200
Saturated link
VPN service request
N1
VPN Table
3200
3299
Correlation
N2
7
D
4
3100
Distant VPN prefix

3299
prefix info: 5
3299 9782603299
3200
Public
Network
3299
Local VPN prefix
prefix info: 33
(NPD)
9782613299
NPD 33
INST: 978260
ARS route list

Route 1: trunk group 10
Digits to add: 978261

11
The interest of the VPN hop with ARS is that the manager of the node 1 can select the trunk group, and the installation number to call
the node2 through the CO.
Steps of the VPN call establishment:
1: The set 3100 ( node 1) calls the set 3200 (node 2)
The link is saturated between Node 1 and Node 2 Through the D channel a VPN request is made to node 2
2: Once the N1-request is received, the node 2 searches for a free (=not already used by another VPN hop) local prefix.
The prefix 3299 is selected.
In a dynamic table, a correlation is made between the local prefix 3299 and the called number 3200. This
correlation will be used when node 2 will be called back by the node 1 through the Central Office.
3: In the definition of the local prefix 3299, one NPD is assigned but not used.
NB: if the ARS is not well managed on the node 1, the node 1 uses the external callback translator (previous slide)
4: Through the D channel, two elements are sent to the node 1
- the local prefix 3299
- the entire number to be called back: 9782603299
5:Once these information are received, the node 1 searches the distant VPN prefix corresponding to the local one:3299
In the definition of the distant 3299 prefix, the prefix information value 5 indicates that the system has to use the
ARS Table #5. The entire external number 9782603299 is not used, only the first information 3299.
In the ARS table it is possible to choose the installation number (978261) and the trunk group (#10) used to call
the node 2
6: The node 1 seizes this public trunk group 10 and calls 9782613299
7: The node 2 receives the incoming call
The system finds in the correlation table the association between the local prefix 3299 and the called number
3200
The set 3200 is rung and the prefix 3299 is released in the correlation table. 3299 is then usable for another VPN
hop. Having several local prefixes managed means being able to have several simultaneous call
establishment

Issue 01
11
155

Feature description
X VPN Overflow: Rights to access to the service

VPN call
No specific barring
Right to access to the VPN service
VPN cost limit: defined in the public access category
VPN hop cost
VPN cost limit for incoming calls: defined in the trunk groups
VPN cost limit Sum of VPN hop costs

12
Depending on the right of user, called VPN privilege, the behavior of the system will be the following:
1) User has not the right to the public network in case of ABC VPN call:
User will get a voice guide saying that network is congested and then release of the call
User can perform a call back request on ABC link
Call will overflow thanks to public-to-private overflow
2) User has the right to use ABC VPN:
Depending on the VPN user privilege, this will enable a user to overflow from Boston to Acton (cheap call), but not from Boston to Los
Angeles ( expensive call).
The cost of the VPN route is calculated by the system and compared to the "VPN privilege" of the user.
If "VPN privilege" is higher, then the ABC VPN call of user will be established on public network
If "VPN privilege" is lower, the call is barred and possibilities are the same as in 1)

Issue 01
156
13

Feature description
X Private to Public Overflow

Allows to overflow 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 as a priority 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
If the set is not a DID number the system calls the attendant
on the remote node, information defined by management

13
This service gives to customer the possibility to optimize the private links in order to support peak traffic in the network and also the
possibility to back up the private links.
In this case, when the private link is saturated or broken down, for all network calls the system modifies the dialed number into a
public one and generates the call via the central office.
-The level of service for this call is limited to the one of the public network, no ABC services is provided for this type of call.
-This service is available between sub-networks in a supra-network configuration. In order to ensure a relative autonomy of
management between sub-networks, the sub-network of the calling party will only have the knowledge of the sub-network of the
called party and not its node, like in homogeneous network.
Restrictions:
- The data communications are not taken into account for this feature, only voice & fax communication are re-routed

Issue 01
157

Feature description
X Private to Public Overflow

Node 1
1a
3100
1b
Private N
3200
ABC
ABClink
link
saturated
saturatedor
orOS
OS
3220
6a
6b
03
0
20
8
20
03
6
82
97
Private/Public:
Private/Public:node
node22
Prefix
to
add:
Prefix to add:
00978260
978260
Installation
InstallationNumber
NumberLast
LastPart:
Part:
3208
3208
DDI
DDItranslator
translatorNode:
Node:
external
externalN:
N:3200
3200
internal
internal N:
N:3200
3200
range
rangesize:
size:10
10
3220
not DID
6
82
97
Phone
Phonefacilities
facilities
rights
rights
3200
Node 2
Public
Network
Attendant
3208
Public
Publicaccess
accesscat.
cat.
->
->barring
barring
management
management

Steps of the Public to Private overflow call establishment:

1a: The set 3100 ( node 1) calls the set 3200 (node 2) which is a DID set
1b: The set 3100 ( node 1) calls the set 3220 (node 2) which is a non DID set
2: The link is saturated or out or order between Node 1 and Node 2
3: The system checks in the Telephone Facility if the caller 3100 is allowed to overflow on saturated link or/and out of order link
4: On management, a private to public overflow is managed to the node 2 defining:
The outgoing seizure prefix 0
The distant installation number: 978260
The DID slices: from internal 3200 to 3209 translated into external 3200 to 3209
The number to call in case of transcoding failure: 3208 (usually an attendant group)
5: The barring of the caller is taken into account
6a: The called set 3200 is a DID user because it belongs to the DID slice dialed number: 0 978260 3200
6b: The called set 3220 is a non DID user because it does not belongs to the DID slice dialed number: 0 978260 3208

Issue 01
158
14

X No specific software license needed for private to public

overflow feature
X The VPN feature license is associated with the private
network license
Enterprise Com Server tab, Com Server licenses menu
X When designing a network solution, take into

consideration the 2 maximum number of VPN jumps
allowed between two users in the sub network

15

Issue 01
159


documents:
Standard offer, section Distributed Architecture and Networking
Presales presentation, ABC VPN VPN overflow (Release 3.2) Ed
01
Multi-PABX Services ABC-F homogeneous private network

VPN overflow


Issue 01
160
16

Conclusion
X The private to public overflow can be used when the link

between two OmniPCX Enterprise is saturated or out of
order and if the VPN overflow function is not managed.
In this case, the level of service provided between the
OmniPCX Enterprise is reduced: it is the level of service of

the public network which is used.
X The VPN overflow provides an excellent mechanism to

cope with real life traffic demands without over
dimensioning the number of resources required
Doesn't work when the accesses are out of order.
VPN is not compatible with the on request ABC accesses.
17

Issue 01
161


Issue 01
162
18
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
163
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
164
Hybrid Links

OBJECTIVE:
To identify and to describe the different types of Hybrid links
Alcatel OmniPCX Enterprise Hybrid links

Issue 02
165
Hybrid links
Content
X Definition
X Examples
X Conclusion


Issue 02
166
Hybrid Links
Definition
X Like the T0/T1/T2 ABC-F2 logical links, hybrid logical

links are used to inter-connect the nodes in a
homogeneous ABC-F2 network and thereby carry the
ABC-F2 signaling and private communications.
X They complement the T0/T1/T2 type ABC-F2 logical links
and are made up of one or several accesses, each access
being made of a signaling channel and voice/data
resources.
X The particularity of the hybrid logical links is that they
authorize different physical support for the signaling
channel and circuit resources
Hence, the signaling channel is not necessarily on the same
coupler as the circuit resources.

Many technical solutions are available to interconnect 2 OmniPCX Enterprises. All these solutions allow to answer the client's
requirements in term of infrastructure (type of links), security (level of security accesses) and/or cost with an ABC level of features

Issue 02
167
Hybrid Links
Definition
X Signaling channel
The different types of hybrid link signaling channel carry
the ABC-F2 protocol over the network. It supports X25

communications for system applications (incidents, IP/X25
tunnel, applications centralization ...)
Different types of support are available:

IP
(Internet Protocol): handled directly by the Com Servers
T2
type access D channel: PRA boards
LAPD
with IO2N or OBCA board: only with Crystal Com Server
switched B channel on ISDN

permanent B channel on ISDN / E1-CAS (PCM) / S0FV
permanent V24 synchronous on analog line with modem
permanent V24/V35 synchronous on digital line with multiplexer / on
data network
ISDN or permanent B channel through modem/TA/T2 ...

A hybrid logical link is made up of a signaling channel and from 1 to 30 time slots for transporting the calls. The signaling channel
and the time slots are logically associated by management.( In case of normal ABC link , the association is physical).
For greater implementation flexibility, the signaling channel and time slots are offered on several types of support .
Warning: Implementing a hybrid logical link on a B channel (LAPD) requires the presence of an IO2N or OBCA coupler. This is
because the LAPD, according to which the signaling link is operated, is processed on one of these couplers.
The hybrid logical link signaling channel carries the ABC-F protocol over the network. It supports X25 communications for system
applications (distribution, incidents, IP/X25 tunnel). Different types of support are available for the signaling channel:
LAPD established on a circuit support,
analog lines behind synchronous modems and synchronous TAs,
digital multiplexers with synchronous data input,
B channel not switched (PCM interface),
ISDN B channel (switched, T0/T2/T1 CCS interface),...
IP (Internet Protocol),
T2-type access D channel

Issue 02
168
Hybrid Links
Definition
X Signaling channel
Different types of support are available:
Permanent logical link through a X25 network
X25 (PLL) in D channel on ISDN

X25 (PLL) in B channel on ISDN: only with Crystal Com Server (needs
IO2N/OBCA)
Transparently through a QSIG-GF T2/T1/T0 D channel
Without signaling
corresponding B channels are using another access D channel

X25 virtual circuit: a VC is used over an external network to transport the signaling channel. This VC can be supported by:
a permanent logical link (PLL) in the B channel of a T0/T2 interface connected to an ISDN,
a B channel.
QSIG-GF,

Issue 02
169
Hybrid Links
Definition
X B channels: Voice/data
The time slots of a hybrid logical link are used to transport
private communication (voice and data) in the network.
These time slots can be of different types:
IP (Internet Protocol): INTIP, GD or GA boards
Leased T2/T0, T1 CCS/CAS: PRA, BRA boards
multidirectional ISDN B channels (E1-CCS, T0, T1-CCS) and through

multiplexers possible
PCM, EMTL, ACEM, NDDI
VPN overflow (ISDN trunk group ...)

Hybrid link is a complement of ABC network usually built on T2/T1/T0 accesses.

Its main feature is to separate the signaling from the B channels resources (they are not necessary on the same board)
Each B channel is not dependent on others and can be managed on different support types.
- T2, T1 CCS, T0
- PCM (Pulse C ode Modulation): digital automatic tie-line, provides 30 time slots
- T1 CAS: digital automatic tie-line, provides 24 time slots
- EMTL ( Ear and Mouth Tie Line ): analog automatic tie-line, provides 6 analog interfaces
- ACEM ( Alternative Current Ear and Mouth ): analog automatic tie-line, provides 4 analog interfaces
- VPN ( Virtual Private Network )
Remind: The VPN feature is used when a link is saturated; the voice is sent through the B channels of a public trunk group (for
instance) and the signaling uses the D channel of the ABC logical link
A maximum of 30 service channels can be assigned to a single access. The service channels can be located on different couplers.

Issue 02
170
Hybrid Links
Feature description
X Connection mode: Permanent or on demand

X Multi-accesses configuration possible
Several accesses in the same hybrid link (up to 16)
Possible to mix different kind of links
Necessary if the number of B channels is more than 30
X Possibility to secure the signaling channel with a signaling

channel back up for each access
X Access without D channel
To increase the number of B channels through the ABC link
The signaling is provided by another access of the same
ABC link

Permanent hybrid link:

A permanent link is always established.
Hybrid link on request:
A link on request is established only when needed.
In a hybrid access, the signaling channel is only set up on a call (telephone or X25). The signaling channel is cut off after a timer
activated at the end of the last communication.
Multi-accesses configuration:
Its possible to manage up to 16 accesses per hybrid link.
Different accesses ( ex: PCM,EMTL) can be mixed in the same link.
In case of one access failure, a back-up can be managed.
A second signaling support can be created in addition to the main signaling support of each hybrid access
This provides two signaling channels for a single access, thus securing it.
* The number of simultaneous communications depends on the signaling channel type:
T0 (16Kbs): 8 calls, T1 (64Kbs): 46 calls, T2 (64Kbs): 60 calls, TCP/IP: 60
Hybrid access with signaling in a D channel of an ABC-F T2 access
A main or standby signaling support of a hybrid access can be defined as a "D" channel support, meaning that the signaling for this
access passes via the D channel of an ABC-F T2 access.
This provides the following advantages:
- Allows hybrid accesses without signaling to use the "D channel" access as signaling supplier channel,
- Allows a T2 access to be backed up by declaring the access as a hybrid logical link access and creating a backup access for it.
Access without signaling
A hybrid access signaling support (main or standby) can be defined "without" signaling. To do so, the "No Sig" parameter must be
declared in the management function. In this case, it uses a signaling channel of another hybrid access called a "signaling provider
access".

Issue 02
171
Hybrid Links
Feature description
X Hybrid links features

Same as a classical ABC link
ABC-M/A/R protocols
ABC-F2 protocol
Telephone features
ARS, VPN , shared trunk groups ...
IP/X25 tunneling
Audit
Broadcast
Centralized voice mail, management, incidents
etc

This kind of link provides the same level of features (ABC-F2) and the same services (IP/X25, broadcast, audit ...).
ABC F: Alcatel Business Communication Feature, exchange protocol on digital links between several Alcatel PABXs in private network
Allows integration services in a private network(Phone facilities, Network mobility, Multi-line sets in a network).
ABC-R: Routing Mechanism, the Call server uses this protocol to check the remote resources (bundle); in case of busy or out of order
remote resource status, its possible to reroute a call with a local resource (ARS in the network,Dynamic routing).
ABC-M: Management Features, thanks to the 4760 management application, its possible to set up a management centralization. In
that case, only one PC could be used to manage the complete network.
The Broadcast and Audit application use the same protocol to update the database (see Audit and Broadcast chapter for more
details).
ABC-A: Networking Applications (attendant feature: 4059, centralized phone book, voice mail).

Issue 02
172
Hybrid Links
Example
X Full ABC link over IP

ABC signaling and voice over IP (no data)
H323
IP
N1
voice
ABC link
Access 1
N2
D1: ABC signaling
Uses ARS and VPN overflow
ARS first route= H323 trunk group

H323 protocol is used to establish the voice call

See corresponding module (ABC link over IP) for more details.

Issue 02
173
Hybrid Links
Example
X Mono access link with signaling backup

B
Access 1
Access 1
Main
PCM
ABC link
D1: ABC
N2
N1
Access 1
Backup
D2: ABC
Operator
X Signaling uses D1
X If D1 is out of service , theres a switch of the signaling on
D2 without any disturbance

10
Remark:
- The standby signaling support can be of the same type as the main signaling support (except for IP signaling).
- The standby signaling support can be set up permanently or not (choice defined by management). If not set up permanently,
the standby signaling support is only set up when the main signaling support is cut off. On a signaling transition, the
established telephone calls are not cut off.
When a standby signaling support is declared in addition to a main signaling support, two accesses are automatically assigned. Each
signaling support has a specific position (hybrid ACT, coupler, terminal).
Access 1:
B channels over PCM (between PCM boards)

main signaling channel: D channel over TCP/IP (between CPUs)
back up signaling channel: D channel over a B channel of ISDN (needs IO2N or OBCA in each node)

Issue 02
174
Hybrid Links
Example
X Multi-access hybrid link

ABC link
Hybrid: signaling via D channel
B
B
B
B
D1: ABC
Access 1
D2: ABC
N1
B
PCM
Access 2
N2
B
X E1/T2 access can be mixed with hybrid accesses if you

manage it as a hybrid D channel access.

11
It is not possible to mix a classical access (E1/T2) with Hybrid access (TA/ATL).
It is necessary to transform the classical access into an Hybrid via D channel.
After this change, it is possible to associate other hybrid accesses to this hybrid on D.
Access 1:
B channels and D channel over a T2 (between PRA or BPRA boards)
Access 2:

D channel over TCP/IP (between CPUs)

Issue 02
175
Hybrid Links
Example
X Multi-access hybrid link

B
PCM
Access 1
Access 1
ABC link
D1: ABC
N2
N1
PCM
Access 2
D2: ABC
Access 2
Operator
X Possibility to add a signaling backup channel associated to

each access (see next slide).

Multiple accesses
It is possible to allocate up to 16 accesses in an hybrid link.
Access 1:

Access 2:

D channel over a B channel of ISDN (needs IO2N or OBCA in each node)

Issue 02
176
12
Hybrid Links
Example
X Multi access hybrid link with backup

Access 1
Main: permanent on IP
backup: dynamic B channel
ABC link
PCM
B
B:D1bis
D1
N1
TA
Access 2
Main: Not switched B channel
backup: switched B channel
PCM
N2
D2 ABC
TA
D2 bis
Operator

13
In case of an access with backup signaling, the main one must be permanent. The second one can be permanent or on request.
If the main is on IP the backup cannot be on IP.
The signaling uses the first D channel then the second one when the first becomes out of service and without lost of established
communications.
Dont be confused between an access with 2 D channels (main and backup) and 2 different accesses with only a main D channel.
In the first case if the principal D channel is OS the system switches on the second D channel , keeping the B channels.
In the second case if the principal D channel is OS the access 1 is lost completely ! Only X25 routing will switch (tunnel, network
topology...) on the second access.
Access 1:

main signaling channel: D channel over TCP/IP (between Com Server)
back up signaling channel: D channel over a non switched B channel of the PCM link (needs IO2N or OBCA in
each node)
Access 2:

main signaling channel: D channel over a none switched B channel, through a TA (needs IO2N or OBCA)
back up signaling channel:D channel over a B channel of ISDN (needs IO2N or OBCA in each node)

Issue 02
177
Hybrid Links
Example
X Access without signaling

ABC link
Hybrid with signaling via channel D

B
D1: ABC
Access 1
N1
ATL
ATL
ATL
N2
Access 2
X First access is a hybrid via D channel (T2).

X The second hybrid access is an Automatic Tie Line using
the D channel of the T2 access for signaling (signaling
provider)

14
Access without signaling

A hybrid access signaling support (main or standby) can be defined "without" signaling. To do so, the "No Sig" parameter must be
declared in the management function. In this case, it uses a signaling channel of another hybrid access called a "signaling provider
access". As he is able to declare hybrid accesses "without" signaling, the user can limit himself to declaring and using a single
signaling channel only for more than 30 time slots. The manager must be careful not to declare too many circuit resources in relation
to the type of signaling used.
Remark: When a "No Sig" signaling support is declared, the access which will serve to carry the signaling must be indicated.
Warning: This means that:
A signaling provider access cannot have a "No Sig" signaling support (whether main or standby).
A "No Sig" signaling support becomes active once the signaling provider access becomes active.
The standby signaling support cannot be a "No Sig" type when the main signaling support is itself a "No Sig" support.
It is possible to increase the number of B channels without adding a new D channel.
It is mandatory to have minimum an access with signaling
- example:
access 1:
D channel: hybrid T2
B channels: T2
access 2:
without signaling (access 1 is signaling provider)

B channels: Automatic Tie Line trunks (EMTL, ACEM, PCM)
For an ABC-F T2 access with 30 B channels and 6 analog voice channels between two nodes, two hybrid accesses are declared:
- A "D channel" hybrid access N 1, comprising 30 B channels,
- A hybrid access N 2 with no signaling, using the N 1 access as signaling provider (meaning that it uses the signaling channel of
access N 1), comprising 6 analog voice channels.
A link containing 36 voice channels is therefore available.

Issue 02
178
Hybrid Links
Example
X Dynamic Hybrid link (on demand): Crystal Com Server only
Access 1
Hybrid
Hybridwith
withdynamic
dynamicsignaling
signaling
via
switched
via switchedBBchannel
channel
N1
N2
D1
B
ABC link
Operator
VPN HOP
VPN HOP
X The access is established when an application needs it (telephone

routing, X25 applications, tunnel...)
X The access is released when it is not needed

15
Dynamic hybrid access

In a hybrid access, the signaling channel is only set up on a call (telephone or X25). The signaling channel is cut off after a timer
activated at the end of the last communication
Remark:
- When using a switched B channel as a signaling support, it has to be defined as a link on demand.
- For other types of signaling, its useless to manage them as a link on demand.
- There is no standby signaling for dynamic signaling hybrid accesses.
In this case the link will be established only when one node will have to send information to a remote node.
A VPN HOP can be managed through the switched network to provide B channels.

Issue 02
179
Hybrid Links
Interaction with other services
X According to the Alcatel OmniPCX Enterprise hardware

(Com server, Media gateway), some restrictions
concerning the hybrid link type will appear.
If the Com Server is a CS or an Appliance Server:
IO2N and OBCA boards services are not available

No signaling in a B channel
No link on request
...
X No ABC link in a peripheral area (ACTIS)


Issue 02
180
16
Hybrid links
X Actis Parameters: Crystal hardware

Define the number of nodes

in your network connected to
this node through a classical
or hybrid link
Define the number of

simultaneous calls over the
ABC IP link

17
Number of nodes in the network

Always indicate the total number of nodes (adjacent and not adjacent nodes) in the network.
Actis updates this item when a private digital link is created. It is used for statistic issues.
VoIP: voice channels
This box concerns the IP/Ethernet highways for PABX interconnection, in the context of a private network.
The compressors on an INTIP2 board are dedicated to the IP/Ethernet access supported by this board, but form part of the shared
resources on the node. For new business, Actis configures only INTIP2 boards fitted with GIP compressors.
B channels with voice over IP for network
Enter the number of simultaneous calls over the IP link. In this manner, Actis determines the number of boards and compressors.

Issue 02
181
Hybrid links

Central area, Private network, Hybrid link
Define the number of access using
Define the number of links using
the D channel of a T2 for the signaling
a D channel over V24 for the signaling
Define the
node type

Ethernet for the signaling

a B channel for the signaling

18
Hybrid link signaling

This frame is used to set up the hybrid link signaling. A hybrid link is used to implement an ABC private link, using the most
convenient networks for voice and ABC signaling between nodes.
The voice channels are transmitted over private links (PCM or analog). Signaling is transmitted over ISDN, Ethernet or V24.
ISDN D channel
This type of VPN does not require a specific interface as it uses a T2 link D channel. The signaling between nodes is transmitted via
X25 (Permanent Logical Link) in the T2 link D channel. Declare the number of directions towards the different remote nodes.
Ethernet
The signaling between two PBXs is transmitted via Ethernet. This solution is implemented when an IP network exists between both
sites. According to the "Internal Hub on ECX Board" option, Context window, the Ethernet link is connected either directly to the PBX
CPU board, or via an ECX1 board if there are other Ethernet accesses, or to an Ethernet hub provided by the customer, this hub being
connected to the PBX CPU board. Declare the number of directions towards the different remote nodes. Actis uses this information to
dimension the CPU board, to measure the traffic and to reserve fictitious trunks.
End node
This node is physically located at the network end and is not used as a routing node. This information makes it possible for Actis to
provide an OBCA2 or IO2N board. For hybrid signalings over synchronous V24 and/or channel B, the OBCA2 board is allowed only
if the node is a terminal node and if the total number of channels B is less than 2, otherwise the IO2N board is set up.
Synchronous V24 with modem
Define the number of signaling channels transmitted by synchronous V24 via modem. For this type of link, Actis sets up a TA after a
UA equipment, a synchronous V24 interface, a modem, a cable, and a B channel on IO2N or OBCA2 board.
Synchronous V24 without modem
Same as previous item, but Actis does not set up the synchronous modem.
B channel signaling
Declare the number of B channels used for signaling. This option is used in the event of a multidirection link. The signaling must be
transmitted to several B channels if the link undergoes direction splitting through a multiplexer.

Issue 02
182
Hybrid links

Central area, Private network, Analog tie-line
Define if the D channel is on
another support
Enter the number of

analog tie-line links.
Actis configures the
corresponding
boards:NDDI, NDDI2,
ACEM, EMTL, E & M

19
Analog Tie Line

This window is used to set up the requirements for private network access via analog private trunks. Actis provides access to the type
of trunks authorized (ATL= Analog Tie Line) according to the country, to the market considered and the PBX version.
The equipped accesses are those which Actis has provided for the supply of a board, its slot in the rack and the unlocking of the
corresponding lock.
The wired accesses are intended for upgrades to the installation. For these accesses, Actis reserves positions in the cabinet and
unlocks the locks, but does not supply the board.
Hybrid link (voice channels on analog tie-lines)
One hybrid link is set up. The voice is transmitted via private links declared in this screen, signaling is set up in the "Hybrid Link
Signaling" frame of the Hybrid link" window.
Q23 recorder signalling
Use only with the analog migration boards of the 4300L.

Issue 02
183
Hybrid links

Central area, Private network, Private digital links
Then Add
Define if optical fiber

type is used for T2 links
Enter a name
for the link
Enter the number of

digital links. Actis
configures the
corresponding boards:
NPRAE, PRA2, BRA2,
DPT1

Digital private link

This window is used to declare a link to a node that is adjacent to the PBX. A link may have several access types. Use the "Add" and
"Delete" buttons to create as many windows as there are links. The equipped accesses are those which Actis has provided for the
supply of a board, its slot in the rack and the unlocking of the corresponding lock. The wired accesses are intended for upgrades to
the installation. For these accesses, Actis reserves the slots in the rack and unlocks the locks, but does not supply the board.
Link name: The link name must not exceed 20 characters.
2 Mb/s interface on optical fiber (TNLO): The ABC-F or DPNSS private link(s) declared in the following items are carried by optical
fiber. Actis sets up one or more TNLO1 board(s) and the cables connecting the PRA2/NPRAE and TNLO1 boards. It is possible to set
up TNLO1 interfaces only if T2 private accesses are declared. The other link types (T0, Transfix, DPT1) cannot be set up with the
OLDT interface.
Private PRA links (DPNSS): Declare the number of DPNSS Primary Rate Accesses for the link. Actis sets up the "ABC-F/QSIG Network"
license
Private PRA links (ABC-F): Declare the number of ABC-F Primary Rate Accesses for the link. Actis sets up the "ABC-F/QSIG Network"
license
Private T0 links: Declare the number of T0 Pra for the link. Actis sets up the " ABC-F/QSIG Network" license for this access type.
X24/V11 links (on LIOB): This is a 64 or 128 Kbps serial interface. Each interface is connected either to a digital leased line (e.g.
Transfix) or to a Frame Relay network. The number of compressed voice communications on these links must be declared in the
"Private network" window (typically 6 for a 64Kbps link or 12 for a 128Kbps link).
Declare the number of Transfix X24/V11 accesses for the link. Actis sets up the LIOB boards, the necessary X24/V11 adaptor cables,
the " ABC-F/QSIG network" and "SWL for serial link X24/V36" licenses.
V36 links (on LIOB): It is a 64 or 128 Kbps serial interface. Each interface is connected either to a digital leased line (e.g. Transfix) or
to a Frame Relay network. The number of compressed voice communications on these links must be declared in the "Private network"
window (typically 6 for a 64Kbps link or 12 for a 128Kbps link).
Indicate the number of Transfix V36 accesses for the link. Actis sets up the necessary LIOB boards, the "ABC-F/QSIG network" and
"SWL for serial link X24/V36" licenses.
Private DPT1 links (ABC-F): Indicate the number of DPT1 accesses via ABC-F for this link. Actis sets up the necessary DPT1 boards.
Each board offers 2 T1 links with 24 B channels each. Actis sets up the " ABC-F/QSIG Network" license for this access type.

Issue 02
184
20
Hybrid links

Define if a continuity test of the different
hybrid links (which voice links are supported
by T0 or T2 bearers) is implemented
periodically by the PBX
Number of nodes automatically defined

according to the number of private digital links
Select the cable length

for the X24/V11 and
V36 accesses
Select the line
impedance for the
corresponding links:
ABC-F or DPNSS

21
Private digital
This frame is used to set up the private digital links connected to the PBX.
Number of adjacent nodes
This is the number of nodes that are directly connected to the PBX. This number is for information only. It is updated by Actis,
according to the links declared.
Hybrid link (voice channels on T2/T0)
A continuity test of the different hybrid links (which voice links are supported by T0 or T2 bearers) is implemented periodically by the
PBX. This function requires a GPA2 board to be installed in the rack. A Q23 receiver is dedicated to this function.
X24/V11 links at Nx64 Kbps
Declare the number of X24/V11 links at Nx64 Kbps. These links are used to transmit high-speed data (64 to 1920Kbps) and require
one or more Nx64 boards. Each board has 4 accesses. For each access set up, Actis sets up a connection cable. Moreover, Actis sets
up a X24/V11 adaptor cable per access if the rack is a VH with Patch Panel.
Cable length
X24/V11 and V36 accesses
Specify the cable length (15m or 35m) to be provided to connect X24/V11 and V36 accesses.
Caution: The length of the other cables connecting the rack to the distribution frame (trunks, terminals, etc.) is defined in the Cabinets
window.
Line impedance
This frame is used to indicate the impedance of the ABC-F and DPNSS links declared in the "Private Network: Link" window.

Issue 02
185
Hybrid links
X Actis Parameters: Crystal or Common hardware

Central area, Private and public PCM
Then add
Dont tick this box for a

private link
In case of common hardware in central area, Actis
configures PCM2 boards in the Crystal IP auxiliary media

gateway
22
Line impedance
Enter the PCM link impedance. This must be adapted to the PBX line circuits to guarantee good transmission of the electrical signals.
The impedance recommended for the French, Austrian and Spanish markets is 120 Ohms (twisted pairs). For some countries, the
impedance used is 75 Ohms (coaxial cable).
To add a private or public PCM link, point the cursor to the table and right-click on your mouse. A pop-up menu is displayed, select
"Add". A line corresponding to the link is displayed in the table.
To delete a link, select it in the table then right-click on your mouse. A pop-up menu is displayed, select "Delete".
Qty
If other identical links must be provided (e.g. 6 identical PCM links), enter the number of identical setting links in this item.
Equipp
Box checked: The link is equipped, thus Actis plans to provide a board and its slot in the rack.
Box unchecked: The link is wired and dedicated to a further development of the installation. Actis reserves the slot in the rack, but
does not provide the board.
Public
Box checked: The PCM link is connected to the public network.
Box unchecked: The PCM link is connected to the private network.
NDDI Qty
Indicate for the link the number of NDDI channels. Actis controls all DDI and NDDI channels. Their number must be 30. Only enter
this item if the "Public" box is checked.
NDDI Sig
Indicate the signaling used for the NDDI channels. Only enter this item if the "Public" box is checked.
DDI Qty
Indicate for the link the number of DDI channels. Actis controls all DDI and NDDI channels. Their number must be 30. Only enter this
item if the "Public" box is checked.
DDI Sig
Indicate the signaling used for the DDI channels. Only enter this item if the "Public" box is checked.
Issue 02
186
Hybrid links
X Full ABC link over IP

With crystal hardware
With common hardware

23

Issue 02
187
Hybrid links
X Mono access link with signaling backup

B
Access 1
Access 1
Main
PCM
D1: ABC
N2
N1
Access 1
Backup
ABC link
D2: ABC
Operator


Issue 02
188
24
Hybrid links
X Mono access link with signaling backup (cont)

Not available with common hardware (only IP signaling)

25

Issue 02
189
Hybrid links
X Multi-access hybrid link: Case 1

ABC link
Hybrid: signaling via D channel
B
B
B
B
D1: ABC
Access 1
D2: ABC
N1
B
PCM
Access 2
N2
B

Access 1:
B channels and D channel over a T2
Access 2:


Issue 02
190
26
Hybrid links
X Multi-access hybrid link: Case 1 (cont)

Create a new link

27

Issue 02
191
Hybrid links



Issue 02
192
28
Hybrid links
X Multi-access hybrid link: Case 2

B
PCM
Access 1
Access 1
ABC link
D1: ABC
N2
N1
Access 2
PCM
D2: ABC
Access 2
Operator

29

Issue 02
193
Hybrid links



Issue 02
194
30
Hybrid links
X Multi access hybrid link with backup

Access 1
Main: permanent on IP
backup: dynamic B channel
ABC link
PCM
B
B:D1bis
D1
N1
TA
Access 2
Main: Not switched B channel
backup: switched B channel
PCM
N2
D2 ABC
TA
D2 bis
Operator

Access 1:
31

main signaling channel: D channel over TCP/IP (between Com Server)
back up signaling channel: D channel over a non switched B channel of the PCM link (needs IO2N or OBCA in
each node)
Access 2:

main signaling channel: D channel over a none switched B channel, through a TA (needs IO2N or OBCA)
back up signaling channel:D channel over a B channel of ISDN (needs IO2N or OBCA in each node)

Issue 02
195
Hybrid links
X Multi access hybrid link with backup (cont)



Issue 02
196
32
Hybrid links
X Access without signaling

ABC link
Hybrid with signaling via channel D

B
D1: ABC
Access 1
N1
ATL
ATL
ATL
N2
Access 2
Central area, Private network, Analog Tie-line

access 1:
33
D channel: hybrid T2
B channels: T2
access 2:
without signaling (access 1 is signaling provider)

B channels: Automatic Tie Line trunks (EMTL, ACEM, PCM)

Issue 02
197
Hybrid links
X Access without signaling (cont)

Create a new link


Issue 02
198
34
Hybrid links
X Access without signaling (cont)


35

Issue 02
199
Hybrid links

relevant documents:
Networking
Documentation Multi-PABX services ABC-F

homogeneous private network Hybrid logical links

ABC
VPN Hybrid link (release 3.2) ed1

ABC VPN Signaling Backup (release 3.2) ed1


Issue 02
200
36
Hybrid links
Conclusion
X A Hybrid access is an access allowing the possibility to

separate on different physical supports, the ABC-F2
signaling and the voice channels
X An ABC link can be composed of several Hybrid accesses.
X There is a back-up signaling of the hybrid access in case
of signaling connection failure
X A hybrid access can mix all types of signaling supports
with all types of voice supports

37

Issue 02
201


Issue 02
202
38
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
203
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
204

OBJECTIVE:
To identify and to describe the Integrated voice compression solutions:

Hardware
Principle
Compressed ISDN trunk group
Alcatel OmniPCX Enterprise Voice compression over ISDN

Issue 01
205

Content
X Definition
X Examples
X Conclusion

Issue 01
206

Definition
X Description of the voice compression service

The voice compression service is used to optimize resources
by throughput of several voice communications on the same

support.
This is made possible by the use of a voice compression
technique.
This technique can reduce required throughput from 64 kb
(or 56 Kb) to 8 kb for transmission of a voice call, resulting

in a reduction of the resources required for a given traffic
flow and consequently a reduction in cost.

56 Kb/s supports are notably used in the USA

Issue 01
207

Feature description
X This service can be implemented for:

ABC logical links
ABC trunkgroups
ISDN trunks
X This service may be used on:

a permanent leased support (fixed rate metering)
a support established on request (metering by duration or
volume)
X For ISDN, this support can be one of the following types:

synchronous B channel of T2/T0 type (digital signaling)
synchronous B channel of T1 type (CCS or CAS signaling)

Issue 01
208

Feature description
X LIO boards (LInk Optimizer) are used:

LIOX-2 board
8 compressors
LIOP-2 board
8 compressors
1 T2 interface
LIOB-2 board
8 compressors
4 T0 interfaces
1 serial Interface X24-V11 or V36
X The compression functions and the interface functions are

completely independent
An external adapter V35/V36 could be added

The LIOB, LIOP and LIOX board compressors are mounted on daughter boards.
There are two types of daughter board:
- Comp2: compression daughter board with 8 compressors
- Comp6: compression daughter board with 6 compressors ( The Comp6 board is an old version)

Issue 01
209

Feature description
X Compression technique used

Compression algorithm G723.1 at 6.4Kbs:
7 communications
Compression algorithm G729 at 8 Kbs:
5 communications
Integrated echo cancellation

Voice Activity Detection
Delay due to compression/decompression: 30 ms
Compatible with Q23 frequencies and analog fax (G3)
Available for uncompressed data calls
asynchronous data at 9600b/s

Compression Algorithm G723.1 or G729 according to the system parameters

The faxes adapt their transmission rate to the one of the compressed channel so their communication will not be compressed
Q23 frequencies are detected by the compressors and sent as a code. In the remote system, this code, received by the compressor, is
sent to the Com server which will generate the corresponding Q23 frequency.
VAD: if there is a silence during a conversation, on the corresponding side, a signaling message will be sent to the other side to ask
the other side to generate a silence. This process will free some bandwidth (because the silence=noise will not be transported on
the link) and then the bandwidth for signaling or eventually data information's will increase.

Issue 01
210

Feature description
X Compression function of the LIO boards

Multiplexing in the same Time Slot
Of the compressed voice channels
Up to 5 or 7 voice communications
Of a signaling channel
Of a V120 HDLC data channel
1 "composite" TS
data channel
Voice channels
Sig.
HDLC Data Frame
LIO
Sig.
Compressed
Voice channels

The rate used by the data channel depends on the number of voice communications established. It uses all the available bandwidth
and cannot be less than 9600 b/s

Issue 01
211

Feature description
X Virtual access characteristics

An access is associated to a composite TS and allows to
define the content of this composite TS
An access associates this composite TS to a physical support
TS of a leased or switched T2 line

Frame relay network
Transfix leased line
On each LIO board can be created up to 4 compressed
accesses without DATA or up to 2 compressed accesses

with DATA
These accesses share the compressors

It is possible to manage more compressed B channels than the hardware possibilities of one LIO board.
Therefore, it will be necessary to use the compressors of an other LIO board.

Issue 01
212

Feature description
X Virtual access characteristics
Virtual
Virtualaccesses
accesses
Management
Composite
CompositeTS
TS
55or
or77BB++DD
P
R
A
6B toward N2
6B toward N3
P
R
A
Physical
PhysicalSupport
Support
B7
B5
B6
6B toward N3
Node
Node22
Node
Node33
6B toward N4
P
R
A
B7
Node
Node44

The compressed access signaling can be:

- ABC-F2 (logical link or trunk group)
- ISDN (ISDN trunk group)
The support channel can be:
- A digital leased line (V36 or X24/V11or T2 B channel))
- A switched network (ISDN)
- A data backbone PVC (Frame relay)

Issue 01
213

Feature description
X The signaling bandwidth is dynamic

If there is less than 7 voice communications, all the
available bandwidth is used for signaling exchange
Voice communications have the priority
if a voice communication arrives, the signaling rate will decrease

(the bandwidth decreases)
16 Kbit/s are allocated to the signaling for each access

According to the number of voice channels used, the signaling rate decreases to a minimum of 16 Kb/s

Issue 01
214
10

Feature description
X Data communication
1 V120/HDLC data communication coming from a TA
can be multiplexed in a composite TS
The bandwidth is dynamic; the throughput varies according
to the calls set up and the signaling traffic
Behavior and throughput vary according to the operating
mode:
synchronous V120 transmission: not possible with compressed links.

asynchronous V120 transmission: throughput between 0 and 9600
b/s
transparent HDLC transmission: throughput between 0 and 48 Kb/s
Only 2 virtual accesses are available when using data

11
According to the number of B channels used, the following rates are available:
- in asynchronous V120 mode:
19,2 Kb/s
- in synchronous V120 mode:
48 Kb/s
According to the voice channels used, the DATA rate decreases to a minimum of 9600b/s

Issue 01
215

Feature description
X Mutual aid
Mutual aid allows a virtual access on a LIO board to use
compressors located on another LIO board
X Example of mutual aid use:

A LIO1 board manages 2 virtual accesses, each used by 5
voice communications: this board needs 10 compressors.
A LIO2 board manages a virtual access used by 4 voice
communications: this board needs 4 compressors.

The "Comp2" board has 8 compressors; the mutual aid
function allows the system to allocate the 4 free LIO2 board
compressors to the virtual accesses of the LIO1 board.


Issue 01
216
12

Feature description
X Mutual aid principle
system1
Com
Server
D
D
eUA 32
BBBBBB
LIO
eUA 32
BBBBBB
LIO
system2
system2
PRA
BB

13
In the central LIO, two virtual accesses have been managed as compressed links to node 2
The 8 first communications from system 1 to system 2 will use the compressors of the central LIO.
For the following B channels, because theres no more free compressors on this central LIO, the system will use compressors from
another board and route the compressed channels to the LIO board that supports the composite TS.
Remark: for security reasons, it is recommended, when several LIO boards are used, to split the virtual accesses on the different LIO
boards.

Issue 01
217

X Restrictions
Modem, Minitel, synchronous data calls are not available
on compressed links
The COMP6 and COMP2 compression boards are not
compatible, i.e. these boards cannot be installed together in

the same ABC sub-network.
Compression service is available only using Crystal
hardware


Issue 01
218
14

Examples
X Compressed ISDN trunk group

A trunk group connecting 2 OmniPCX Enterprise in different
networks can be compressed. This trunk group can be used

as support for public network B-channels.
This application is used, for example, to connect two
different companies which exchange telephone calls
frequently.
The first communication sets up the support B-channel and
the following compressed communications use the same

support.
This is known as free second communication.
Up to 5 or 7 free communications are possible
ARS improves the compression operation (not mandatory)

15
This feature is known as: 2nd call for free

Objective: to reduce the cost between 2 Alcatel OmniPCX Enterprise and 2 companies with common interests
ARS is necessary to associate a compressed trunk group dedicated to each called number concerned with compression (numbers of
the distant site)
ARS is not compulsory when using a compressed trunk group. A trunk group seize prefix is sufficient.
However, the ARS mechanism improves operation. It can be used to redirect a maximum number of calls to the compressed trunk
group while remaining transparent to the user. It can also be used to optimize the processing of compressed trunk group overflows.
To do this, an initial route to the compressed trunk group, then the overflow routes, must be declared in the ARS routing table.

Issue 01
219

Examples
ISDN B channel with voice

compression
(5/7 B+D)
PRA
PRA
S isdn
S isdn
LIOX
LIOX
ISDN
Sig
ARS
ARSisismandatory:
mandatory:
voice
voicecompression
compressionaccording
accordingtotocalled
callednumber
number
Compressed
Voice channels

When receiving the call on node 2, the sub-address will indicate to the Com server that this incoming B channel has to be routed to
the LIO board that supports the virtual access for the compressed ABC link to node 1.

Issue 01
220
16

Examples
X Establishment mechanism through a switched network

user dials:
00++028
028260
2603020
3020
0: ARS prefix
028
028260
2603020
3020->
->route
routelist
listXX
route
routelist
listXX
#2:trunk group 21prefix
Trunk
(not compressed)
group
sub-address *12: compressed TG 12

on remote system
digit to
remove
digit to
add
20
21
Call
CallNumber:
Number:
#2 028
028260
2605555
5555 *12
20: compressed trunk group

17
The number, used to establish the trunk group in charge of supporting the composite TS, can be any DID number of the remote
switch.
The system indicates that its a compressed call an adds at the end the number the requested sub-address. This sub-address
corresponds to the number of the remote compressed trunk group.
In this example, the routing table cancels 6 digits to the number initially dialed. This allows to use for incoming calls a specific
translator, or not to translate the received number on the compressed trunk group.
In that case, even if only DID numbers of the remote site can be rerouted by ARS to the compressed trunk group, with a possible
overflow to a a usual trunk group, it is possible to seize directly the compressed trunk group (or abbreviated numbering) to reach non
DID set of the remote site.
A compressed trunk group can be assimilated to a private trunk group containing 6 tie lines trunks toward the remote site, and the
ARS management can be assimilated to a public route forcing toward the private route

Issue 01
221

Examples

Charging ticket
A
ticket is created for the support communication
associated to the compressed trunk group number
associated to the name of the compressed trunk group
cost center by default: 255

transmitted number: extension N
duration
pulses received
replaced the metered number
replaced the name of metered user
For the compressed communications

A
ticket is created for each communication without cost indication
Metering information
Sets
cannot use the metering counter during a compressed call

The only metering information supplied by the public network
concerns the support communication
If for charging reasons, it is necessary to split the cost between 2 Alcatel OmniPCX Enterprise, it is possible to manage 2 compressed
trunk groups sharing the same compression resources:
-Management of 2 compressed trunk group containing 3 compressed TS.
-Use of ARS to associate distant numbers to each compressed trunk group.
-Every call from site A to site B will need the establishment of the associated trunk group, and so the creation of a charging ticket
for the first communication.
-Every call from site B to site A will generate another ticket on site B.
By the way, the use costs of the compressed trunk group are properly split between both PABX

Issue 01
222
18

X Digital public trunks quotation in Actis

To get T0 trunk
group
To get T2 trunk
group

19

Issue 01
223

X Compressed communications and directions quotation in

Actis
To get compressors
for compressed
communications
To have a data
communication in
the compressed
channel
X Following items are calculated


Issue 01
224
To get virtual
accesses ( to
calculate number of
boards)
Compressed calls
software licence
20


relevant documents:
Standard offer,
Pre Sales presentations,
System documentation,
Feature list & Product limits
Others (user guides, marketing documents,..)

21

Issue 01
225

Conclusion
X Integrated compression advantages:

Second call for free
Resources optimization
X Concerning charging information:

There will be a ticket for "real" cost, which is the cost of the
ISDN B-channel on ISDN, allocated to the A4400 origin of

the call.
There will be also "virtual" tickets, for communication
supported in the tunnel channel, with cost 0, and allocated

to subscribers.

Issue 01
226
22

Conclusion
X Who pays for what?

The cost of support ISDN B-channel is incurred by the PABX
that set up the call until the release of the support channel
and not shared between the 2 companies according to their
respective outgoing traffic.
A first approach to this is to say that this is not a problem because

the next call could be in the other direction and that statistically over
a long period of time, costs are allocated fairly to the 2 companies
according to their outgoing traffic.
A second approach is for customers dissatisfied with the first

approach. The solution is then to specialise a support channel only
for outgoing calls. This means that 2 support channels are
necessary: 1 from A to B and one from B to A and each company
only pays for its outgoing traffic.

23

Issue 01
227


Issue 01
228
24
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
229
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
230
TCP/IP Implementation

OBJECTIVE:
To identify and to describe the TCP/IP implementation in the Alcatel OmniPCX Enterprise
TCP/IP presentation in the Alcatel OmniPCX Enterprise
Default IP Addresses
Customized IP addresses
Alcatel OmniPCX Enterprise TCP/IP implementation

Issue 01
231
TCP/IP implementation
Content
X Definition
X Conclusion


Issue 01
232
Definition
X The Call servers need IP addresses to communicate

With IP devices
GD, GA, INTIP, IP phones (e-reflexes, IP touch),
Between call servers (in case of duplication)

With applications
4645 voice mail server, IMAP server

Administration tools: Alcatel OmniVista 4760, telnet, ...
CTI applications: OmniTouch Unified Communication server,
X The Call server is using applications like
TFTP, FTP, Telnet
X Uses IPV4, compatible IPV6

IPV4: an IP address is made up of four bytes coded in decimal

IPV6: an IP address is made up of 16 bytes coded in decimal
IP Address and IP mask (reminder)
An IP address comprises 4 bytes (32 bits), the value of which is generally represented in decimal form.
This address breaks down into 2 parts: the network/subnetwork identifier and the machine identifier. The IP mask is used to
distinguish the network address part from the machine address part. The mask comprises 4 bytes and is represented decimally as an
IP address. A "logical AND" between IP address and mask is used to find the subnetwork number
All the machines connected to the same subnetwork have an identical network/subnetwork address.
An OmniPCX Enterprise has one or several access points (Ethernet, IP Tunnel ...), which are all accesses to different subnetworks,
each one of which is identified by an IP address.
The system chooses the subnetwork according to the remote address, the subnetwork addresses and the associated masks. Thus,
when choosing an IP address, it is mandatory to comply with the subnetwork number.

Issue 01
233
Feature description
X DHCP service
The Call server can act as a DHCP server (configurable)
For IP address dynamic allocation
Provides
Open to all clients
Client IP address
Sub network mask IP address
Gateway IP address
TFTP server IP address (usually the Call server)
IP Phones, INTIP and Gx boards, PC
Can act also as a DHCP relay

DHCP: Dynamic Host Configuration protocol

Issue 01
234
Feature description
X TCP/IP Routing
Dynamic IP routing
A routing table contains the list of the sub-networks known by the

When using the dynamic routing, all the sub-networks known by a

node will be known by all the other nodes of the ABC link network
Thanks to a specific process running on each node
When using the static routing, all the destinations have to be
managed on all the nodes using the Netadmin tool

NetAdmin: network administrator tool available on the Call server Linux interface through a V24 or Telnet connection

Issue 01
235
Feature description
X TCP/IP Accesses
Types of link
Ethernet link (10/100 BaseT)
Call server access (local, backup, main, stand-by: 4 IP addresses)
GD, GA, INTIP, IP Phones: 1 IP address each
IP/X25 tunnel
Internal X25 network on ABC link only providing specific services like
TCP/IP connection: OmniVista 4760, telnet, FTP
Audit, broadcast
PPP: Point to Point Protocol
Asynchronous V24 link (modem, TA-TA)
Used by a Telnet connection for instance

On the Ethernet access, 2 types of addresses can be defined. One corresponding to the physical interface and a second one to the
role of the Call server (main or stand-by).
The IP/X25 tunnel is used to encapsulate the IP datagrams within the X25 packet protocol (when using ABC links). The tunnel uses the
master Call server.
The IP/X25 tunnel used one address per node: 172.30.R.N where R is the network number and N the node number.
Example: For the node 2 in the network 1, the tunnel address will be 172.30.1.2
The PPP links are defined on the V24 ports that are shared between the two Call server of the system therefore, they use the master
ones.

Issue 01
236
Feature description
X Default IP addressing plan

If no integration of the Alcatel OmniPCX Enterprise inside a
LAN or a WAN
10.1.1.1
CS
GD
10.1.1.6
Ethernet
Node 1
PRA
172.30.1.1
OmniVista 4760
10.1.1.10
172.30.1.2
PRA
ABC link: IP/X25
Node 2
CS
GD
10.1.2.1
10.1.2.6

This is the default addressing plan in use on the Alcatel OmniPCX Enterprise.This is only used when the system is not integrated in the
customers LAN.
Default IP addresses on Ethernet:
10.NET.NODE.1
first Call server
10.NET.NODE.2
second Call server
10.NET.NODE.3
main Call server
10.NET.NODE.4
stand-by Call server
Default addresses in the IP/X25 tunnel (never changed because always internal: encapsulated in ABC link signaling)
172.30.NET.NODE
There is only one address per IP/X25 tunnel access for this interface because the tunnel is only active on the main Call server

Issue 01
237
Feature description
X Customized IP addressing plan on a LAN/WAN

configuration
OmniVista
4760
IP name: Station1
IP @: 155.132.38.11
155.132.38.20
LAN 155.132.38. 0
IP name: BREST_a
150.122.13.1
150.122.13.3 CS main
IP name: router1
IP @: 155.132.38.1
Router
SIP terminal
IP @: 155.132.38.31
H323 terminal
150.122.13.50 150.122.13.60
CS standby
IP name: router1
IP @: 150.122.13.1
GD
150.122.13.11
IP name: BREST_b
150.122.13.2
150.122.13.4
4645 voice mail

150.122.13.18
LAN 150.122.13. 0

If the Alcatel OmniPCX Enterprise and the management PC are integrated in the customers LAN, it can be necessary to manage the
routers that are between the management PC and the Alcatel OmniPCX Enterprise
In this example, the Alcatel OmniPCX Enterprise and the Alcatel OmniVista 4760 are in two different networks.
To establish a connection between them, a router has to be used.
The default router IP address has to be managed in the Alcatel OmniPCX Enterprise (using NetAdmin tool) and in the management
PC (in MS Windows TCP/IP parameters)
If there is more than one router, it is necessary to manage static routes instead of a simple default router.
The default router is an address defined in the Alcatel OmniPCX Enterprise, it belongs to one of the sub-networks known by the
Every IP datagrams that have an address of destination which does not belong to one of these sub-networks will be sent to the default
router.

Issue 01
238
X No specific license


Issue 01
239

relevant documents:
Networking
Documentation System services IP facilities


Issue 01
240
10
Conclusion
X A Call server can have access to several network

interfaces: Ethernet, IP/X25 tunnel, serial link.
X An IP address is assigned to each interface.
X Thus a call server has as many IP addresses as the PBX
which supports it has network interfaces; each IP address
corresponds to a connection via an interface.

11

Issue 01
241


Issue 01
242
12
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
243
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
244
VoIP H323 Solutions

OBJECTIVE:
To identify and to describe the integrated VoIP (Voice over IP) H323 Solutions:
Standards and protocols:
- H323
- H225
- H245
- Compression algorithms
Integrated VoIP solutions:
- GD, GA, INTIP A boards
- Full IP ABC link Networking
- Inter working with H323 terminals
- External Gatekeeper interoperability
Alcatel OmniPCX Enterprise ABC link VoIP and H323 terminals

Issue 02
245
VoIP H323 Solutions

Content
X Definition
H323 standard
H225 protocol
H245 protocol
Exchange principle
GD, GA and INT IPA boards
Gatekeeper solutions (internal, external)
Full ABC link over IP
X Conclusion


Issue 02
246
VoIP H323 Solutions

Definition
X TCP/IP: layered set of protocol

Application layer (FTP, Telnet, Netaccess, ...)
Transport layer (TCP or UDP)
Network layer (IP).
Each layer is encapsulated in the lower layer protocol
X IP: Internet Protocol

X TCP: Transmission Control Protocol. Reliable transport
Service
X UDP: User Datagram Protocol. Connectionless, nonreliable transport Service
X DHCP: Dynamic Host Configuration Protocol

Issue 02
247
VoIP H323 Solutions

Definition
X LAN: Local Area Network

X Ethernet: LAN which uses the CSMA/CD (Carrier Sense
Multiple Access/Collision Detection)
X Intranet: corporate IP network
X WAN: Wide Area Network
X Internet: a collection of world-wide interconnected IP
networks
X IPv6: future release of IP (current is IPv4). IP addresses on
16 bytes (instead of 4), priority management with
ReSource reserVation Protocol, encryption and
authentication

Issue 02
248
VoIP H323 Solutions

Definition
X ITU: International Telecommunication Union

X VoIP: Voice over IP
X QoS: Quality of Service
X RTP: Real-time Transport Protocol
X RTCP: Real-time Transport Control Protocol
X MCU (Multipoint Control Unit): an endpoint on the LAN
which enables 3 or more terminals and Gateways to
participate in a multipoint conference
X H.261/H263: video coding algorithms


Issue 02
249
VoIP H323 Solutions

Definition
X RAS: 2 different meanings

Registration/Admission/Status protocol (H323/gatekeeper)
Remote Access Server (IP remote access)
X Gatekeeper: a H.323 entity that provides address

translation, control access, and sometimes bandwidth
management to the LAN/WAN for H323 terminals or
Gateways
X E.164: identification defined to access to a Gatekeeper
X T.120: data conference protocol
X T.38: procedures for real-time Group 3 facsimile
communication over IP networks

Issue 02
250
VoIP H323 Solutions

Definition
X Algorithms used for voice

ITU-T Recommendation G.711 (1988): Pulse code
modulation (PCM) of voice frequencies at 56 & 64 kbit/s
Coding algorithms
ITU-T Recommendation G.723.1 (1996): dual rate speech
coder for multimedia communication transmitting at

5.3Kbit/s & 6.4 kbit/s
Compression algorithms
ITU-T Recommendation G.729: dual rate speech coder for
multimedia communication transmitting at 8 & 11 kbit/s
Compression algorithms


Issue 02
251
VoIP H323 Solutions

Definition
X Protocols used for signaling

ITU-T Recommendation H225.0: Media Stream
Packetization and Synchronization for Visual Telephone

Systems on Non-Guaranteed Quality of Service LANs
ITU-T Recommendation H245: Control of the
communications between Visual Telephone Systems and

Terminal Equipment.
ITU-T Recommendation H323 (1996): Visual and Telephone
Systems and Equipment for Local Area Networks which

provide a non guaranteed QoS
Audio/video conferencing standard for IP network

H.225: signaling protocol (RAS, RTP/RTCP, Q.931) and message formats used by H323
H.245: protocol for capability negotiation, opening and closing channels for media streams

Issue 02
252
VoIP H323 Solutions

Definition
X H323 Standard
For video and audio data exchanges between terminals
(PC) in real time through Internet or LAN networks with a

non guaranteed QoS
It is used on TCP/IP network
Ethernet
Fast Ethernet
Token-ring
H323 terminals are able to operate with PSTN/PABX
terminals via a H323 gateway


Issue 02
253
VoIP H323 Solutions

Definition
X H323 Standard
Many companies develop their own H323 compliant
software to exchange audio and video data over IP
Software like Netmeeting manage the functions offered by
the H323 standard including G723 Codec used for voice

compression and decompression.
H323 has been adopted by many companies like IBM,
Microsoft, CISCO, Netscape, Intel, Alcatel...

Netmeeting is a Microsoft software

Issue 02
254
10
VoIP H323 Solutions

Definition
X H323 principle
H
3
2
3
E
n
t
i
t
y
System control
H225
Call
Control
Sig
H245
Control
Data
applications
Telematic
T120
System control
H225
RAS
Control
RTCP
QoS
VIDEO
AUDIO
Codec
H261, H263
Codec
G711, G723, G729
Real-time Transport Protocol

H225 frame layer
TCP = reliable = secured

Connected mode
UDP = unreliable = fast

Not Connected mode
IP

11
TCP: information are sent with security. If a packet is lost it will be transmitted again.
UDP: information are sent without security. If a packet is lost it will be not transmitted again.
Signaling and Data information uses TCP because each packet is important.
Voice and Video uses UDP because it doesnt matter to loose a packet for audio or video transmission.
H323 terminal uses H225 and H245 protocols to transmit signaling information that comes from a part of the application that we
can call User module. This module is in charge of the connection establishment and release. It sends the H323 application
possibilities (available algorithms and other needed parameters to setup a connection).
RTP (Real-time Transport Protocol) and RTCP (Real-time Transport Control Protocol) are used to send video and audio data through
UDP because transmission time is shorter and more important than loss of packet.
RTP encapsulates the data with an information header for each packet. This header contains time information and the packet id
RTCP controls the RTP packets, sends control packets to provide feedback on the quality of the data distribution. It deletes packets
received twice, puts the frames in right order, synchronizes audio video and data, informs the system about the connection status.
Provides statistics about the Quality of Service (QoS)
H323 terminal can be compatible with few compression algorithms as H261 (>64Kbit/s), H263 (<64Kbit/s) for video, G711
(56,64Kbit/s), G722 (48,56,64Kbit/s), G723 (5,3 and 6,4 Kbit/s), G728 (16 Kbit/s), G729 (8,11 Kbit/s) for audio.

Issue 02
255
VoIP H323 Solutions

Definition
X H323 standard defines

Video and audio data exchanges over IP
Terminals
Gatekeepers
Gateway
Multipoint Controller


Issue 02
256
12
VoIP H323 Solutions

Definition
X H323 terminals = multimedia PC

Sound card (full duplex recommended)
Microphone
Loudspeaker or headset
Video equipment (optional)
LAN interface (TCP/IP stack)
H323 software (ex: NetMeeting)
Data applications using T120 protocol (optional)

13

Issue 02
257
VoIP H323 Solutions

Definition
X H323 Gatekeeper features

Server which centralizes H323 entities IP@
Uses RAS to check H323 entities rights
Receives E164 @ and translates them into IP@
If DHCP servers are used, H323 terminals requests
registration to the Gatekeeper. The Gatekeeper updates

dynamically its translation table
Call authorization: reject a call due to authorization failure

Bandwidth management: reject calls due to bandwidth
limitations
Directory services

14
E164: directory N or Host name or Email@

Instead of managing an Speed dialing number for each H323 terminal it is possible to manage an open one, linked to the
Gatekeeper. The H323 will send to the Gatekeeper a directory number that will be translated into an IP@.
RAS: Registration Admission Status
The Gatekeeper server receives H323 terminal or gateway request for automatic registration (RAS) and can be managed manually by
an administrator
Remark: there is a Gatekeeper integrated in the Alcatel OmniPCX Enterprise, an external one is then not mandatory !

Issue 02
258
VoIP H323 Solutions

Definition
X H323 Gateway
Provides translation of the transmission formats and
procedures (voice/data and corresponding signaling)

LAN (IP)
G723.1 (6.4Kbs)
<--> Alcatel OmniPCX Enterprise (Telephone: C1)

G711 (64Kbs)
Translates video, audio and data formats using the H323
Recommendation

15
Remark: the GD, GA and the INT IPA boards correspond to the H323 gateways in the Alcatel OmniPCX Enterprise.

Issue 02
259
VoIP H323 Solutions

Definition
X H323 Multipoint Controller (MC)

Provides control functions to support conferences with three
or more endpoints
Can be located in Gatekeeper, gateway or H323 terminal

MC routes audio, video and/or data to Multipoint Processor
(MP)
MP provides audio mixing, send to all participants the video
of that one who is speaking or mix-up the different video in

one picture split in 4 parts
MP is located in gateway and Gatekeeper

Remark: in the case of the Alcatel OmniPCX Enterprise, the MC corresponds to the DSP0 or C1 circuit located in the GD, GA or INT
IPA boards
ex: the 3 parties conferences are supported by the DSP0 or C1

Issue 02
260
16
VoIP H323 Solutions

Definition
X H225.0 standard
Generates frames to carry all information toward H323
endpoints
Defines Registration Admission and Status exchanges with
the Gatekeeper (when used)
Establishes a connection between two H323 entities using
IP addresses returned by the RAS or provided by the applications

The Q931 protocol messages: setup, alert, connect
When H225.0 protocol has established a connection
between two H323 entities, a H245 control channel is

opened to exchange capabilities information

17
H.225.0 describes how audio, video, data and control information on a packet based network can be managed to provide
conversational services in H.323 equipment.

Issue 02
261
VoIP H323 Solutions

Definition
X H245 standard
In charge of the logical channel negotiation between two
H323 entities
Master/slave
Request mode
Used for conference: multipoint
Provides information about the communication
Available algorithms
Round trip delay measurement
Packets transmission time information

Test if the remote H323 terminal is still alive

H323 entity = H323 terminal or gateway

Issue 02
262
18
VoIP H323 Solutions

Definition
X H323 standard uses

TCP (reliable) for
Signaling (H225)
Control messages (H245)
Telematic data (T120)
UDP (unreliable but fast) for
RAS messages (H225)

Voice, video data (Hxxx and Gxxx algorithms)

19

Issue 02
263
VoIP H323 Solutions

Definition
X H323 terminals connection
Data
System
control
Telematic
T120
RTCP
System
control
H245
H225
Audio
Codec
G723
Data
System
control
Telematic
T120
RTCP
System
control
H245
H225
Audio
Codec
G723
RTP
RTP
H225 frame layer
H225 frame layer

TCP
TCP
UDP
UDP
3: QoS channel
1: Signaling connection
2: Control channel


Issue 02
264
20
VoIP H323 Solutions

Definition
X H323 terminals connection
Data
System
control
Telematic
T120
RTCP
System
control
H245
H225
Audio
Codec
G723
Data
System
control
Telematic
T120
RTCP
System
control
H245
H225
Audio
Codec
G723
RTP
RTP
H225 frame layer
H225 frame layer

TCP
TCP
UDP
UDP
Audio channel
Telematic services channel

21

Issue 02
265
VoIP H323 Solutions

X H323 voice over IP solutions overview

Large Branch-Offices
VoIP ABC link Networking
Node 1
Node 2
ABC link
IP LAN
PABX with H323 gateways
IP WAN
H323 terminals
Small Branch-Offices

22
Alcatel OmniPCX Enterprise integrated VoIP solution allows to easily integrate Alcatel OmniPCX Enterprise ABC networks in existing or
new network infrastructure.
It is an investment for the future. At the difference of other packet voice technologies, like FR, IP goes to the terminal. So VoIP will
also enable communications between standard telephone and VoIP enabled terminals.
VoIP in Alcatel OmniPCX Enterprise will be used to build an ABC network over an IP infrastructure, i.e. interconnecting Alcatel
OmniPCX Enterprises. The benefit is to reduce running costs and provide ABC feature transparency
How can VoIP cut running costs ?
If the customer has an IP infrastructure linking its sites, he/she can route voice and fax traffic over the IP network, at no additional
cost, instead of using the public toll network.
With the same available bandwidth, voice compression will enable to carry 3 calls where only one can be carried on the public
network
Silence suppression will cut by a further 2 factor the average WAN bandwidth necessary for one voice channel.
Data is transported on the same link than voice. More data can travel on the link, than if voice and data where on separate networks
(statistical multiplexing)
Where will VoIP be implemented first ?
VoIP will be used when the customer wants to speed up the investment he has done in a high-performance private IP network.
But voice quality is an issue in IP networks.
The place to implement VoIP first, is in simple IP networks where performances of the IP network can be managed.
Where VoIP runs toward end point nodes, that is without transit
Where end point node is connected through a point to point connection
Where voice traffic is low
The place is networked with branch offices, with star topology. It targets branch offices with more than 30 subscribers.

Issue 02
266
VoIP H323 Solutions

X GD, GA and INTIP2 boards common characteristics

Gateway for H323 terminals/gateways (signaling and voice)
and ABC link VoIP (voice)
H323 V2 compatible (fast start)

H323 networking under software license control
3 voice coding/compression algorithms
G.711: 64Kb,
G.723.1: 6.4 Kbs, G729: 8 Kbs
Under software license control
The choice between compression or not is done when
configuring*:
IP trunk groups (for H323 terminals/gateways calls)

VPN overflows (for VoIP ABC link Networking)

23
Which compression algorithm to use ?

Due to the high bandwidth required for G711, PCM coding should be used in LAN environment but is not recommended in the
WAN. This is due to the 64kb/s coding but also to the overhead generated by the encapsulation in IP packets, which means
around 100kb/s bandwidth at the Ethernet level.
Then the choice will be to compress the voice using G723.1 or G729A.
* A global choice for compression in the Alcatel OmniPCX Enterprise has to be done into the system parameters
- G.723.1 or G.729
Remark: The ABC link service is using the H323 Recommendation to carry the voice information into a H323 trunk group.
Fast Start: functionality provided with the H323 V2 recommendation. It could be used, for instance to force, during a H323 call, the
two parties to use the same compression algorithm (process defined in the SET UP messages.
One of the major evolutions of the new implementations in the Alcatel OmniPCX Enterprise gateways is that FastConnect is now
supported, in outgoing as well as incoming calls. The advantage of the FastConnect is that the media channel may be established in
a 2 messages interchange: a setup
and its response. This permits a quicker establishment and a more deterministic choice of the audio CODEC.

Issue 02
267
VoIP H323 Solutions


External and internal Gatekeeper compatibility
Echo cancellation
DTMF (Q23) sending/receiving
1 external 10/100 baseT (RJ45 connector): auto detection
Authorize connection to a DHCP server
Dynamic IP addressing plan
Ready for IPV6
New IP addressing plan on 16 bytes

External Gatekeeper: the aim is to enhance the level of H323 interoperability with third party products to enrich our offer with new
terminals or to integrate Alcatel OmniPCX Enterprise into IP based Next Generation Public Networks (ex: IP/H323 trunk groups to
interconnect different PABX).

Issue 02
268
24
VoIP H323 Solutions


IP packetisation and compression
TCP/IP and RTP/RTCP protocols

Packetization algorithm: G.711
Compression algorithms: G.723.1 or G729.A
Each board needs an IP address

Echo cancellation
G3 FAX relay
No compression
T38 compatibility
QoS: RTCP monitoring, IEE 802.1Q/p, TOS-Diffserv

25
H323 VoIP is realized in the Alcatel OmniPCX Enterprise by the GD, GA and INT IPA
Note: INT IPA is dedicated to VoIP. The GD, GA and INTIPA cant be used for other type of compression !
These boards concentrate the voice traffic coming from various Alcatel OmniPCX Enterprise boards or H323 entities, compress or
code this voice channels, packetize them and send the packets on the Ethernet to the corresponding destination using its IP address.
Echo cancellation is integrated because of the delays due to compression and transport on the IP network.
DTMF/Q23 codes are interpreted, coded and regenerated on the other side. This avoids any problems with distortion, on which
DTMF/Q23 receivers are very sensitive.
T38:
- The Alcatel OmniPCX Enterprise supports T38 as part of the H323 protocol suite. Connection of analog equipment (fax ) on the
LAN. Third party device will be qualified and validated on a case by case basis. Such qualification is under process and list of
qualified product will be published later.
- Example of third party Z over IP device: the VSA board of the Alcatel OmniAccess 512 (4 or 8 analog/voice over IP ports)
T38 is a way to transmit Fax over IP with H323 V2.

Issue 02
269
VoIP H323 Solutions

X GD and GA boards: in IP MG
Data
equipment
LAN connection or
directly to CS
10/100 bT
cable
female RJ 45 connectors
SlanX accesses
(4 supplementary ports)

The GD has the following main functionalities:

- Connects (over IP) the e-MG to the Call Server (e-CS)
- Gateway for H323 terminals: signaling and voice
- ABC link VoIP H323 gateway: voice.
- IP Phone signaling and voice (depending on the IP domains configuration).
- Gateway for SIP terminals (voice).
- Handles the interface with legacy equipments (UA, Z, ISDN)
The GA has the following main functionalities:
- Gateway for H323 terminals: signaling and voice
- ABC link VoIP H323 gateway: voice.
- IP Phone signaling and voice (depending on the IP domains configuration).
- Gateway for SIP terminals (voice).
Remark: the WAN connection is not used.
An Ethernet (10 Mbit/s or 100 Mbit/s ) connects the GD and GA to the IP network through two twisted pairs.
The link may be a hub (straightthrough cable) or another Ethernet terminal (crossover cable).
Twisted pairs shielded cable must be plugged into the RJ45 receptacle available at top of board.

Issue 02
270
26
VoIP H323 Solutions

X GD and GA daughter boards

MADA1 or MADA3
DSPs for voice coding/compression in Voice over IP applications,

24 or 8 DSP
G.711, G.723.1, G.729,
DTMF generation and detection
Group 3 fax relay.
SlanX (only for GA)
10/100 Mbits/s base-T Ethernet LAN switch

3 crossed ports and 1 straight port (uplink)
Auto-negotiation (full/half duplex)
Flow control

27

Issue 02
271
VoIP H323 Solutions

X INTIP2 board: in Crystal MG
Daughter board 1
Mandatory
CBC1
female RJ 45 connector
INT IP board
cable
10/100 bT
Daughter board 2
(optional)
Data
equipment

backpanel
Two types of voice over IP daughter boards
GIP4-1: 8 channels
GIP4-4: 30 channels
Modularity: 8/16/30 or 60 channels

Remarks:
- These daughter boards CAN'T BE MIXED
- When the INT IP board is used for H323 features, it is seen as an INT IPA board (software configuration).
Channel = DSP for voice coding/compression

Issue 02
272
28
VoIP H323 Solutions

X Internal Gatekeeper on the OXE Com server

Under software license control
It allows an easiest management of H323 entities and more
reliability
Not dependant on an external gatekeeper server

Com server Internal Gatekeeper services
H323 terminals and gateways (VoIP boards) registration
E164 address translation into IP addresses
H323 terminals and gateways access control: the call server checks
in the mao if they are known

29
Mao is the name for the Alcatel OmniPCX Enterprise database.

Issue 02
273
VoIP H323 Solutions

X Internal Gatekeeper registration Control

In a registration request a H323 terminal sends its IP@ and
its E164@
If the E164@ is known as an IP Speed dialing number in the
Alcatel OmniPCX Enterprise's database then the IGK

registers the H323 terminal
else the registration is rejected by the gatekeeper

An Alcatel OmniPCX Office, an OmniAccess or another
H323 gateway is declared in mao and does not register

with the IGK

Registration: the Request can be done with unicast or multicast addressing. With Unicast, the GK's IP @ must be managed locally.
Remark: a non Alcatel OmniPCX Enterprise gateway (Alcatel OmniPCX Office or OmniAccess 512 for example) has to be configured
statically in the IGK.

Issue 02
274
30
VoIP H323 Solutions

X H323 terminals registration on the internal Gatekeeper

2: Terminal existence
check in MAO
E-CS database (MAO)
3: If yes, registration in IGK
Call Server
IGK
E1 6 4 @
hos t
I P a ddr e s s
31050
H3 2 3 PC1
10. 1. 1. 10
IGK's database
H323PC1
E164@: 31050
4: Registration
confirmation
1: Registration request
(31050, 10.1.1.50))
IP@: 10.1.1.10
IP Network

31
In case of MAO modification or IP address modification, the H323 terminal must register itself again to remain operational.

Issue 02
275
VoIP H323 Solutions

X In case of e-CS duplication, the IGK is also duplicated

Main IGK
Standby IGK
X If the main e-CS falls down, the standby IGK becomes

main
Transparent for the H323 clients
Because they are using the e-CS "role IP addressing", so the
H323 gatekeeper IP address doesn't change for them
X Also, the IGKs databases are always synchronized

So H323 terminals are not affected by a switch-over

32
With a duplicated system there is an active process on the main Call server and a backup one on the stand-by Call server but only the
IGK located on the main is active.

Issue 02
276
VoIP H323 Solutions

X In a first step, the IGK will not provide

Routing of signaling (no calls forwarding)
Bandwidth control: the H323 client specifies in the ARQ
request a bandwidth value
The IGK does not control the bandwidth and copies this value
without treatment in the ACF
Exchanges with other internal or external gatekeepers
LRQ (Location Request), LRJ(Location Reject) and LCF (Location

Confirm) are used between Gatekeepers to exchange information
about users: these messages are not recognized by the IGK
Authentication of terminals (login)

33
Information messages:
- To obtain information about a terminal the IGK sends an IRQ (Information Request) message
The terminal answers with an IRR(Information Request Response).
Because IGK don't exchange information with other gatekeepers it will not answer to an IRQ message received from an other one
Resources availability:
- A gateway sends a RAI (Resource Availability Indication) to inform the IGK about its multimedia capabilities
the IGK is not able to analyse this type of message. It will not take into account the information inside the message
but will send back a RAC (Resource Availability Confirmation) because the H323 standard imposes to send an ack message
Specific Bandwidth requests:
- If the IGK receives a BRQ (Bandwidth Request) message it answers with a BRJ (Bandwidth Reject).
Other restrictions or remarks:
- 1000 H323 terminals and gateways maximum
- Use of an external gatekeeper (as in Alcatel OmniPCX 4400 R4.2) is still possible but only if the IGK is not activated
- No link with IP domains
- IGK/EGK: a H323 endpoint cannot be registered on 2 GK simultaneously

Issue 02
277
VoIP H323 Solutions

X The Alcatel OmniPCX Enterprise can also work with an

external Gatekeeper
The OXE supports call scenarios with or without Gatekeeper
(interoperability with other gateways)
Better scalability: a Gatekeeper is mandatory for address
resolution in big VoIP multi-vendor networks
Security: incoming calls are accepted by the Alcatel
OmniPCX Enterprise gateway only if the call is

acknowledged by the Gatekeeper
In an Alcatel OmniPCX Enterprise VoIP ABC network, a
Gatekeeper can be used to realize Call Admission Control
Limitation of the number of calls on the WAN to avoid congestion

34
Gatekeeper features:
-
RAS: Register, Admission and Status
The Gatekeeper, which is optional in a H323 network, provides call control services. It can be used only with an INTIP board.
(more than one Gatekeeper may be present and communicate with each other)
The Gatekeeper can provide the following services to the gateways and the terminals:
* Bandwidth Control:
. It may reject calls from a terminal due to the bandwidth limitations,
* Address Translation:
. With a Gatekeeper, the DHS3 (Alcatel OmniPCX Enterprise) doesnt need to know all the IP addresses.
Compatibility with external H323 V2 Gatekeeper:

Cisco
Radvision
Alcatel CID

Issue 02
278
VoIP H323 Solutions

X Gatekeeper implementation
Large Branch Offices
VoIP ABC link networking
Node 1
Node 2
ABC link
PABX with H323 gateways
IP LAN
IP WAN
H323 gateways
H323 terminals
External gatekeepers
Internal gatekeepers
Small Branch Offices

35
* an external gatekeeper can be used but only if the IGK is not activated. They can't be activated in the same time.

Issue 02
279
VoIP H323 Solutions

X ABC link VoIP networking principle without Gatekeeper

5
4
UA
GD
H323
trunk group
CS
VOICE
VOICE
H323 trunk group
H323 trunk group
UA
VPN
VPNhop
hop
CS
Node 1
ABC link
(Voice & Fax)
Sig
GD
Sig
Node 2
H323
trunk group
LAN/WAN
Remote
RemoteVPN
VPNPFX
PFX
3299
3299
++ARS
ARSroute
routelist
list
ARS
ARSroute
routelist
list
- -H323
H323Trunk
Trunk
Group
number
Group number
2
1
Signalling
Signalling
IPIPHybrid
HybridABC
ABClink
link
00BBchannel
channel
Local VPN PFX

Local VPN PFX
3299
3299
+ GD IP@
+ GD IP@

Remark: this example works without Gatekeeper and could be done using a GA board or an INT IPA board (in case of ACT-MG
used).

Issue 02
280
36
VoIP H323 Solutions

X Full ABC link Networking over IP

IP hybrid link without B channels (between the call server)
Used
only to route the signaling information
1 per direction (60 B maximum per IP signaling channel)
H323 trunk group (Gx/INT IPA access)

Used
to route the voice
Can be defined over several Gx/INT IPA (if more than 30 trunks)
Possibility to define several trunk groups on the same Gx/INT IPA
VPN overflow between the 2 nodes

Used
to associate the hybrid ABC link and the H323 trunk group
ARS mechanism for the VPN routes selection

Overflow
mechanism if first route is saturated
Route 1: IP
Route 2: ISDN trunk group
...

37
Remark: the ABC link VoIP feature needs several software licenses
- ABC network
- H323 network
- G711, G723 or G729
- ARS
Gx= GD or GA

Issue 02
281
VoIP H323 Solutions

X Calls restriction on an ABC-F link over IP

Use of the max number of calls type IP parameter in the
VPN hop configuration
Give the possibility to limit the number of VoIP calls per
direction (including direct RTP in network)

Example:


Issue 02
282
38
VoIP H323 Solutions

X Interworking with H323 compliant terminals/gateways

Without a Gatekeeper, the phone number is translated in
an Speed dialing number

IP
Speed dialing number (H323 terminal directory number )
IP address (H323 terminal)

H323 trunk group prefix (corresponding to the Gx/INT IPA access)
With a Gatekeeper
Outgoing
Incoming
calls
A H323 trunk group prefix and an E164 @ are used

The caller dials the prefix followed by the E164 @ of the called party
(H323 terminal, analog set behind a PABX with a H323 gateway)
calls
The Gx/INT IP boards can register on a Gatekeeper to provide the

Alcatel OmniPCX Enterprise sets directory numbers which can be called
over IP

39
The Alcatel OmniPCX Enterprise acts as a VoIP gateway, VoIP enables terminals like PCs to be able to set/receive VoIP calls to/from
Alcatel OmniPCX Enterprise terminals through Alcatel OmniPCX Enterprise VoIP gateway.
H323 terminal: VoIP enabled PC means that the PC has audio capabilities and a H323 client, like Microsoft Netmeeting or Netscape
Communicator (conference).
For calls from Alcatel OmniPCX Enterprise to VoIP enabled PC, Alcatel OmniPCX Enterprise has a table that translates the telephone
number (E164) of the PC into the IP address of the PC.
If a Gatekeeper is present in the network, Alcatel OmniPCX Enterprise VoIP can also be Gatekeeper client. This means that the table
E164 to IP is not used: for each call, Alcatel OmniPCX Enterprise requests the IP address of the PC to the Gatekeeper. The
Gatekeeper maintains the table E164 to IP.
For calls from PC to set or trunk on Alcatel OmniPCX Enterprise, PC sends the IP address of Gx/INT IP, followed by the telephone
number to be reached.
H323 is only basic call !
H323 addresses basic call only: no supplementary services supported like call back etcneither between 2 VoIP gateways, neither
between gateways and terminals.
This means that with H323 only, it is not today possible to have real private telephony like with the ABC services between nodes and
Reflex (call handling) services on PC terminals.
Remark:
- The Alcatel OmniPCX Enterprise is using H323 V2 and the name of a H323 entity can be displayed during a H323
communication (ex: a UA set calling a PC with Netmeeting)
- Calling Name Identification Presentation (CNIP)
- Can be used for INTIP and Gx boards..
- The H323 trunk group could be used by the ARS service.

Issue 02
283
VoIP H323 Solutions

Example
X A H323 terminal calls a local extension
H323 terminal
H323 terminal
<-- IP@155.132.100.200 | N34000
155.132.100.200
CS
GD
UA
34000 -->
34000


Issue 02
284
40
VoIP H323 Solutions

Example
X A H323 terminal calls an external extension
H323 terminal
H323 terminal
<-- IP@155.132.100.200 | N0 0201133000
155.132.100.200
02011
ISDN
-->
30
PRA
<
-3
CS
33000
00
GD
PRA
UA
CS
33000

41

Issue 02
285
VoIP H323 Solutions

Example
X H323 terminal calls another external H323 terminal with a

static IP address
H323 terminal
H323 terminal
<-- IP@155.132.100.200 | N00201133200
CS
ISDN
0
00 -->
1332
3 32 0
GD
0201
PRA
33200
33200 (DDI)
(DDI)
IP
IP Speed
Speed dialing
dialing nb
nb
IP@:155.131.3.10
IP@:155.131.3.10
<--
155.132.100.200
CS
H323 terminal
155.131.3.10
PRA
GD
155.131.100.200
155.131.3.10 -->


Issue 02
286
42
VoIP H323 Solutions

Example
X An internal extension calls H323 terminal with a static IP

address
155.132.4.10 -->
H323 terminal
155.132.4.10
H323 terminal
GD
CS
34201
34201
IP Speed dialing nb
IP Speed dialing nb
IP@:155.132.4.10
IP@:155.132.4.10
UA
<-- 34201
34000

43

Issue 02
287
VoIP H323 Solutions

Example
X An external extension calls H323 terminal
155.132.4.10 -->
H323 terminal
155.132.4.10
H323 terminal
ISDN
GD
201
<-- 34
--
PRA
<
CS
00
11
20
34
20
34201
34201
IP Speed dialing nb
IP Speed dialing nb
IP@:155.132.4.10
IP@:155.132.4.10


Issue 02
288
44
VoIP H323 Solutions

Example
X H323 Terminals with a DHCP Server and a Gatekeeper

Gatekeeper
DHCP server
H323 Terminal
UA
CS
GD
155.132.10.1
155.132.10.200
155.132.10.100
Dynamic IP@
<--1 0008C7196B63
0008C7196B63
IP @ request
@IP 155.132.10.300
2-->
Windows Configuration
@MAC: 0008C7196B63
Host name: DURAND
TCP/IP: to select automatically
an IP @
IP@: 0.0.0.0
3--> New IP@: 155.132.10.300

45

Issue 02
289
VoIP H323 Solutions

Example

Gatekeeper
DHCP Server
H323 terminal
UA
CS
GD
155.132.10.1
155.132.10.200
<--1 0008C7196B63
Host name Alias (@E164)

DURAND
DURAND
2100
155.132.10.100
155.132.10.300
Dynamic IP@
DURAND 2100
@IP
Netmeeting Configuration
155.132.10.300
155.132.10.300
alias (@E164): 2100

Gatekeeper: yes
Gatekeeper IP@: 155.132.10.200

Remark: it could be the Call server internal gatekeeper

Issue 02
290
46
VoIP H323 Solutions

Example

Gatekeeper
2100
DHCP Server
H323 terminal
Number=2100
1-->
UA
CS
GD
Gatekeeper: yes
Gatekeeper IP@: 155.132.10.200
155.132.10.1
Normal abbreviated N: 2100

Call N: #015 2100
155.132.10.200
155.132.10.100
Dynamic IP@
2100 ?-->2
#015= IP trunk group seizure prefix
<--3
155.132.10.300
H323 call
Host name alias (@E164)

DURAND
2100
-->4
windows Configuration
IP@
155.132.10.300
@MAC: 0008C7196B63
Host name: DURAND
TCP/IP: to select automatically
an IP@
@IP: 0.0.0.0
155.132.10.300

47
With a DHCP server:

- Dynamic IP@ allocation
- Gatekeeper server is mandatory

Issue 02
291
VoIP H323 Solutions

X Switch network recommended

X Only permanent connections between sites (routers )
PPP, X25 connections with dial-up not recommended
X A TCP/IP network doesnt guarantee a Quality of Service

when transporting real time dependant data like voice
X It is then necessary to take care about this problem
X Many features in the Alcatel OmniPCX Enterprise are
implemented to increase the Quality of Service locally on
each node
IEEE 802.1Q tagging (VLAN), TOS-Diffserv tagging
IP domains

48
The quality of voice communications is something that has been taken for granted by business users today. Alcatel is one of the
original pioneers of voice communications, and as such, believes there is no compromise between quality and bringing IP-based
voice communication services to the user.
Supporting voice communications over networks originally designed for data-only communications can only be achieved if the
appropriate measures to support voice traffic have been carefully taken. Data networks must be voice-ready, because tomorrow, an
exponential growth of the bandwidth requirement is likely to occur.
Ensuring the Quality of Service (QoS) for voice and other communications media, as networks expand and application traffic grows,
requires network control mechanisms that can classify and consequently prioritise traffic flows. The Alcatel OmniPCX Enterprise sends
the voice traffic to the network with standard tagging mechanisms that will be taken into account by switches or routers that
implement standard QoS classification and policy based management.

Issue 02
292
VoIP H323 Solutions

X Regarding VoIP on a ABC network link, a solution exist to

limit the number of VoIP communications including direct
RTP calls
It ensure voice quality by limiting the bandwidth used
Overflow mechanism available based on the ARS

49

Issue 02
293
VoIP H323 Solutions

X H323 terminals (see the IP terminals quotation module for

more details)
Central area tab / private network

50
VoIP H323 network links for H323 terminals

Enter the number of simultaneous communications over the IP link for the H323 terminals other than IP Phone (Multimedia PC, VoIP
mobile Softphone, Web Enable Call Center). Actis determines the number of MADA or GIP boards in each media gateway of the
central area.
Caution: The number of channels must be calculated as follows :
Round the total number of terminals up to the multiple of 10 immediately above or equal it.
Divide this number by the coefficient given in the table below. This table is given for information for an average traffic of 0.16 Erlang:
Number ofH323 terminals
Coefficient
10
1,25
20 to 30
40 to 60
2,5
70 to 110
120 to 180
3,5
190 to 340
350 to 710
4,5
> 720

Issue 02
294
VoIP H323 Solutions

X Integrated H323 gatekeeper

Enterprise Com server tab / Com server licenses

51
H323 Gatekeeper
H323 is a standard containing several protocols intended for telephony over IP.
H323 Gatekeeper software is integrated into the Com Server. It simplifies the management of H323 components (H323 gateways
and terminals). It checks the existence of the requested terminal and translates the IP addresses of the H323 gateways and terminals
into the numbering plan of the Media gateway. Conversely, it translates the MCDUs of a Media gateway's numbering plan into the IP
addresses of the H323 terminals.

Issue 02
295
VoIP H323 Solutions

X VoIP ABC link

Central area tab / private network

VoIP H323 network links for ABC network

Enter the number of simultaneous communications over an IP link intended to communicate with the other nodes. Actis determines
the number of MADA or GIP boards in each mdia gateway of the central area.

Issue 02
296
52
VoIP H323 Solutions

X VoIP ABC link

53

Issue 02
297
VoIP H323 Solutions

X In the Alcatel Business Partner Web Site BPWS, under Pre Sales, you
can find further details and links to other relevant documents:
Presentations\IP & VoIP\
IP domains and VPN hops
Standard offer
Pre Sales communications:
"03_VoIP_Solutions_and_QoS_aspects_with_OXE_ed8b"
"Actis_for_OXE_com_resources_estimation_ed9"
see in IP/VoIP chapters ...
System documentation
Feature list & Product limits, others (marketing ...)
See the i-learning part for more details on IP Phones and
VoIP gateway boards


Issue 02
298
54
IP telephony
Conclusion
X The traffic generated by the voice over IP and the customer

data network architecture have to be taken into account
X Before a voice over IP offer, it is recommended to make a
voice over IP audit
By taking into account the customer data network
architecture
In order to simulate voice over IP calls to see the
consequences on the network and to compare it to the voice

over IP requirements

55
Deployment
Alcatel has two processes available for helping customers construct an optimal voice and data network
A simulation process, called test of conformity , which measures and analyses voice traffic on IP
A data audit process based on:
analysis of the infrastructure and applications used,
measurements of the network,
reports specifying the inventory of the network and its performances,
some analysiss and recommendations for deploying a correct and workable solution.
The Alcatel Professional Services team helps Business Partners to grab new business opportunities in this high value added
environment while improving their customer satisfaction and loyalty.
If you need supplementary information regarding Professional Services, you can send an e-mail to the following address:
https://www.businesspartner.alcatel.com/ section Professional Services.

Issue 02
299


Issue 02
300
56
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
301
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
302
Alcatel IP Phones

OBJECTIVE:
To be able to answer to IP Phone's RFP
Alcatel OmniPCX Enterprise Alcatel IP phones

Issue 02
303
Alcatel IP Phones
Content
X Definition
X Examples
X Conclusion
X Appendix


Issue 02
304
Alcatel IP Phones
Definition
X The IP Phones provide users with transparent access to

advanced telephony features through the IP network
Same level of service as UA digital sets sine UA is
encapsulated into IP frames
X IP Touch sets provide more advanced services by providing

Xml integration and a better ergonomics


Issue 02
305
Alcatel IP Phones
Feature description
X Available terminals
IP Touch 4018, 4028, 4038 and 4068
Advanced e-Reflexes 4035IP

Premium e-Reflexes 4020IP
Easy e-Reflexes 4010IP
X Add on modules can be added on all sets except the Easy


Issue 02
306
Alcatel IP Phones
Feature description
X The IP Phones support LAN connectivity

UDP-IP and RTP protocols
Voice digitalization algorithm: G.711
Compression algorithms: G.723.1 and G.729.A
Ethernet connection:
10/100 MBPS mini-LAN switch function interface

to connect a PC desktop: Ethernet 10/100 MBPS RJ45
Remote power feeding according to 802.3af pre standard
Standard AC power pack: 117V / 230V
DHCP client
Dynamic software downloading
QoS: RTCP monitoring, IEEE 802.1p/q, TOS-Diffserv
SNMP MIB 2
Standard Ethernet cabling
Maximum of 2 IP Phones sets can be cascaded *

MIB
MIB corresponds to MIB2 standard. It will integrate later voice MIB. MIB elements can be read via SNMP V1 protocol by an openview
station for example. MIB2 has been completed with proprietary information, useful for management:
- name of user
- telephone number
- area location
- administrator name
These data are in RAM
The following security features are not defined in IP Phones
- encryption: that ensures confidentiality of voice carried over network
- authentication: that ensures to be sure of identity of distant
- access control: that protects access to administration functions
IP Phones support 3 coders: G711, G723.1 and G729. Coders are associated to VAD (voice audio detector) and CNG (comfort noise
generator) excepted for the G711.
Remark: no VAD with G711 with e-reflexes (VAD and CNG in G711 are not standardized by ITU).
* 4010 IP sets may not be cascaded

Issue 02
307
Alcatel IP Phones
Feature description
X Two different solutions to supply power to IP Phones

AC power pack
IP Phones can be supplied with an AC/DC power supply pack
To be ordered in Actis
117 V or 230 V input
OmniPower Patch Panel
Used to provide power to the IP phones
No switching function
The IP Phone is powered through the Ethernet cabling according to

the 802.3af standard
To be ordered in Actis


Issue 02
308
Alcatel IP Phones
Feature description
X OmniPower Patch Panel main characteristics

12 or 24 distribution plugs for the IP phones connection
12 or 24 RJ45 sockets for the connection to the data switch
10/100 Mbps Ethernet interface
IEEE standardized: 802.3af
48V D.C. typical over unused pairs 4,5 and 7,8 or phantom pairs
Impedance test (short circuits detection)
Maximum distance of 100 meters (non device dependant)

Overall power available is 300W for 24 plugs.
Connection to 117 V or 230 V electrical outlet
Optional battery back-up module (48V)
17Ah batteries = 4 h autonomy warranted


Issue 02
309
Alcatel IP Phones
Feature description
X OmniPower Patch Panel connectivity

IP Phones
OmniSwitch
OmniSwitch
GD
CS
OmniPower Patch
Patch Panel
Panel
OmniPower


Issue 02
310
Alcatel IP Phones
Feature description
X 802.1 p/Q:
Q for Qualification= VLAN id
P for priority
X A VLAN is a domain of broadcast. The purpose is to

separate the voice from the data to protect the IP phones
from broadcast storms.
X VLAN policy (setup on the data switches) is usually based
on:
Ports, MAC address or DHCP but could also be based on
protocols (IP, IPX, ), subnets, binding rules (combination

of rules, for example ports AND MAC add), authenticated
(802.1x, LDAP server or Radius)
X VLAN tagging (802.1Q) is most of times implemented in

addition to the VLAN policy.


Issue 02
311
Alcatel IP Phones
Feature description
X The IP phones integrate a mini switch for priority handling

between the LAN, the PC and the internal port (UA set
voice and signaling)
X Incoming packets can be classified in two ways: 802.1
Q/p or port based
802.1 priority: incoming packets will be put in high priority
or low priority
Example
tagging:
of classification rule depending on the 802.1 Q/p frames
Priority 0 to 3: low priority queue

Priority 4 to 7: high priority queue
Otherwise (for non 802.1 Q/p tagged frames) incoming
port priority will be used:

LAN
and internal port: high priority ports

PC port: low priority port

The priority is based on:

- 802.1p incoming packet header priority (programmable priority)
- Port priority (workstation port will have a lower priority)
Remark:
- both solutions may be combined (if no 802.1p packet then port priority will be used)
- each transmit port queue is split into 2 priority queues: high and low priority queues
(the switch transmits all high priority packets before low priority)
- The IP Phones mini switch does not alter the Ethernet Frame to add any priority field.
- this mini switch is not manageable
- the different thresholds are defined by R&D and are contained in the firmware

Issue 02
312
10
Alcatel IP Phones
Feature description
X Example: mechanism with 802.1 Q/p tagged frames

802.1 Q/p
priority = 7
Signaling,
Voice
IP phone
Priority 0 to 3: low
Priority 4 to 7: high
Ethernet
10/100 Switch
LAN
802.1 Q/p
priority = 2
Data
PC

11
If the Ethernet frames are tagged,

- UA set: priority 7
- PC: priority 2
the mini switch will take into account these priorities and all the information's going to or coming from the UA set will be classified as
"high priority" so they will be switched before the "low priority" information's.
When the UA set information's will be sent through the LAN port, they will go in the "high priority queue" of the data switch while the
PC information's will go in the "low priority queue".

Issue 02
313
Alcatel IP Phones
Feature description
X Example: mechanism with non tagged frames

802.1 Q/p
priority = ?
Signaling,
Voice
IP phone
UA set: high
PC port: low
Ethernet
10/100 Switch
LAN
802.1 Q/p
priority = ?
Data
PC

If the Ethernet frames are not tagged,

- UA set: priority not used
- PC: priority not used
the mini switch will analyze the origin or the destination of the information's sent or received and all the information's going to or
coming from the UA set will be classified as "high priority" so they will be switched before the "low priority" information's (which is the
case for the PC information's) because the mini switch considers that the UA set port has a higher priority than the PC port.
When the UA set information's will be sent through the LAN port, they will go in the "high priority queue" while the PC information's
will go in the "low priority queue".

Issue 02
314
12
Alcatel IP Phones
Feature description
X It is possible to setup all IP@ manually in the IP Phones

sets or to use dynamic IP@:
Alcatel OmniPCX Enterprise used as a DHCP server or
DHCP relay
External DHCP server (ex: Windows 2000)
X Some files (binaries...) are downloaded to the IP Phones by

the Alcatel OmniPCX Enterprise Com Server directly
through the TCP/IP network (not via VoIP boards)
X For registration, UA signaling and voice, the IP Phones
needs to dialog with a Gx/INTIP board:
UA signaling is encapsulated in IP frames via UDP packets
The Voice is encapsulated in IP frames via UDP packets
13
DHCP (Dynamic Host Configuration Protocol)

-Software installed in a server which allows to centralized IP configuration of stations
-Allocate dynamically an IP configuration to the DHCP clients
IP @
subnet mask @
gateway IP @
tftp server @ (Call server IP @)
DHCP Relay
A DHCP Relay must be managed in case of non transparent router use.
Indeed, if an IP Phone ,which belongs to a LAN, tries to request an IP address to a DHCP server, which belongs to an other LAN,
these two LAN being connected by a router, we must set up a DHCP Relay if the router is not transparent (DHCP discover not
authorized).
This means that if the DHCP frames cant be sent through the router, these frames must be encapsulated in IP frames.
Thus, by using a DHCP relay, the router will be able to support the DHCP messages.

Issue 02
315
Alcatel IP Phones
Feature description
X IP configuration example with the e-Reflexes (from the set)

Menu + #
1.MAC Address 3.Versions
2.IP Parameters 4.Others
MAC Address:
00:80:9F:04:00:4F
0.Back
Save Modifications ?
Save=# Ignore =*
With DHCP
1.Mode (dynamic) 3.Subnet mask
2.IP Address
4.Router Address
5.TFTP server
0.Back
6.Main Call server Address
Without DHCP
1.Mode (static) 3.Subnet mask
2.IP Address
4.Router Address
Navigator can be used

to modify IP@ digits

Remark:
- with bintscip version 4.2 minimum
- In static mode all parameters must be setup (main Com server IP@ is not accessible).
- "menu + #" is typed during the IP phone initialization phases

Issue 02
316
14
Alcatel IP Phones
Feature description
X IP configuration example with the e-Reflexes (from the set)

Menu + #
1.MAC Address
2.IP Parameters
3.Versions
4.Others
Phone Software:
Rel: 03 Rev: 31
1.Phone Software 3.IPE Software

2.IPE Hardware
0.Back
IPE Software:
00.04.2
IPE Hardware
3EU53000AAAD03

15

Issue 02
317
Alcatel IP Phones
Feature description
X IP configuration example with the e-Reflexes: MAC @ and

IP @ display
Menu [i]
WhoAmI
Dupont jean 89562

IP
IP Add: 155.131.1.50
Next Menu
Eth Add: 00:80:9F:04:00:4F

Next Menu

Remark: on the second NEXT, the subnetwork mask IP @, the e-Reflexes firmware version and the IP domain number are also
displayed.

Issue 02
318
16
Alcatel IP Phones
Feature description
X IP Phone software downloading using static IP @:
2-->
2--> Manual
Manual setup
setup (menu
(menu +
+ #)
#)
Local
Local @:155.131.1.35
@:155.131.1.35
Local
Local subnet
subnet mask:255.255.0.0
mask:255.255.0.0
Router
Router address:0.0.0.0
address:0.0.0.0
TFTP
TFTP server:155.131.1.3
server:155.131.1.3
Main
Main Com
Com server:155.131.1.3
server:155.131.1.3
MAC
:00809F03E802
MAC @
@
:00809F03E802
IP phone
MAIN Com Server

Hard Disk
Memory
Lanpbx.cfg
bintscip
starttscip
TFTP server
Gx
INTIPA
1-->
1--> Switch
Switch on
on the
the
power
power on
on aa
non
non registered
registered
set
set
transfert of Lanpbx.cfg/bintscip/starttscip
<--3

17
When an IP Phone is switched on, it requests always the file: /usr2/downbin/lanpbx.cfg

The IP Phone identifies itself with a random free port N xxxx to reach the TFTP server port 69 (standard port).
When the Alcatel OmniPCX Enterprise Com Server receives a request on the port 69 it selects a random free port N yyyy to identify
itself. Then it can reach the IP Phone port N xxxx using this new port Nyyyy as identifier .
The port 69 is used only for each new TFTP request to the server. To transfer the file the server use a random port N yyyy which is
release when the file is completely transferred
When the file lanpbx.cfg is loaded, the IP Phone knows the IP@ of the TFTP server.
The device needs to download the binary file necessary for the processor and the DSP: /usr2/downbin/bintscip
The IP Phone uses a new free random port N zzzz to reach the TFTP port 69 (the previous port N xxxx has been released).
When the Alcatel OmniPCX Enterprise Com server receive a request on the port 69 it answers on a new free random port N wwww to
reach the IP Phone port N zzzz.
This file contains the IP@ of the TFTP server that provides the binary file needed by the device.
Size of the files (about)
Lanpbx.cfg: 160 bytes
bintscip: 320 Kbytes
starttscip: 80 bytes

Issue 02
319
Alcatel IP Phones
Feature description
X IP Phone registration (initialization) using static IP @:

user
user configuration
configuration
Directory
Directory N:31051
N:31051
Set
Set Type:4035
Type:4035 IP
IP
Ethernet
Address:
Ethernet Address:
IP
IP Address:
Address:
Setup:
Setup:
Local
Local @:155.131.1.35
@:155.131.1.35
Local
Local subnet
mask:255.255.0.0
Router
address:0.0.0.0
TFTP
server:155.131.1.3
Main
Main Com
Com Server:155.131.1.3
Server:155.131.1.3
MAC
:00809F03E802
MAC @
@
:00809F03E802
MAIN Com Server
2-->
Directory Nb ?
31051
Hard Disk
Memory
Lanpbx.cfg
bintscip
starttscip
TFTP server
Gx
INTIPA
D
3--> Send e-Reflexes MAC@/IP @ for registration
Send signaling message for registration
D
<--1

When the binary file has been downloaded, the IP Phone needs to know the port N used by the Gx/INTIPA to send signaling
information. This port N can be changed in system parameters.
This information is stored in starttscip file.
The IP Phone uses a new free random port N tttt to reach the TFTP port 69 (the previous port N wwww has been released).
When the Alcatel OmniPCX Enterprise Com server receives a request on the port 69 it answer on a new free random port N uuuu to
reach the IP Phone port N tttt.
The IP Phone is now ready to receive signaling information from Gx/INTIPA. The Alcatel OmniPCX Enterprise Com server has sent to
the IP Phone the port N to use as identifier (32000 by default) to receive Gx/INTIPA information. The IP Phone knows that the
Gx/INTIPA identifier is the port N is 32640 (standard N).
The Gx/INTIPA listens to the port N 32640 and send information on the port N 32000.
The Gx/INTIPA asks to the user to dial the directory number of the set by sending on the UA screen the SET N ? message

Issue 02
320
18
Alcatel IP Phones
Feature description
X IP Phone registration (initialization) using static IP @:

user
user configuration
configuration
Directory
Directory N:
N: 31051
31051
Set
Set Type:4035
Type:4035 IP
IP
Ethernet
Address:00809F03E802
Ethernet Address:00809F03E802
IP
IP Address:155.131.1.35
Address:155.131.1.35
Setup:
Setup:
Local
Local @:155.131.1.35
@:155.131.1.35
Local
Local subnet
mask:255.255.0.0
Router
address:0.0.0.0
TFTP
server:155.131.1.3
Main
Main Com
Com server:155.131.1.3
server:155.131.1.3
MAC
:00809F03E802
MAC @
@
:00809F03E802
MAIN Com server

Hard Disk
Memory
Lanpbx.cfg
bintscip
starttscip
TFTP server
4-->
Gx
INTIPA
31051

19
In parallel the Gx/INTIPA uses a random free port N as identifier for the voice.
The IP Phone uses the port N 32002 (Gx/INTIPA signaling port N identifier + 2) as identifier for the voice.
The Gx/INTIPA sends the dial tone message to the user to request the set directory N
The IP Phone sends to the Gx/INTIPA the directory N dialed by the user.

Issue 02
321
Alcatel IP Phones
Feature description
X IP Phone registration (initialization) using a DHCP server

Discover: general broadcast from IP Phone
Dynamic IP@ range list
IP@
sunetmask
router
155.132.5.60 255.255.0.0 0.0.0.0
155.132.5.61 255.255.0.0 0.0.0.0
155.132.5.62 255.255.0.0 0.0.0.0
IP Phone
Leased IP@ list

IP@
MAC@
155.132.5.60 -> 00809F03E802
r
ove
disc
P
C
DH
main Com server IP @: 155.132.5.2

1
DH
C
MAC@
:00809F03E802
IP@
:0.0.0.0
subnet mask:255.255.255.255
router
:0.0.0.0
TFTP server @:
Pd
isc
ov
er
IP client

See appendix
ALCATL03E802 *BROADCAST DHCP Discover
(xid=AEDF28E9)
IP: Source Address = 0.0.0.0

IP: Destination Address = 255.255.255.255
UDP: IP Multicast: Src Port: BOOTP Client, (68); Dst Port: BOOTP Server (67)
DHCP: Discover
(xid=AEDF28E9)
DHCP: Client IP Address (ciaddr) = 0.0.0.0

DHCP: Your IP Address (yiaddr) = 0.0.0.0
DHCP: Server IP Address (siaddr) = 0.0.0.0
DHCP: Relay IP Address (giaddr) = 0.0.0.0
DHCP: Client Ethernet Address (chaddr) = 00809F03E802
DHCP: Option Field
(options)
DHCP: DHCP Message Type

DHCP: Client-identifier
= DHCP Discover
= (Type: 1) 00 80 9f 03 e8 02
DHCP: Host Name

DHCP: Requested Address
= TSC_DEVICE2
= 0.0.0.0
DHCP: IP Address Lease Time = 1 Days, 0:00:00

DHCP: Client Class information = (Length: 16) 61 6c 63 61 74 65 6c
2e 74 73 63 2d 69 70 2e 30
DHCP: End of this option field
<.alcatel.ip phone.0

Issue 02
322
20
Alcatel IP Phones
Feature description

Offer: from OmniPCX Enterprise Com server to IP Phone
IP@
sunetmask
router
155.132.5.60 255.255.0.0 0.0.0.0
155.132.5.61 255.255.0.0 0.0.0.0
155.132.5.62 255.255.0.0 0.0.0.0
IP Phone
Leased IP@ list

IP@
MAC@
155.132.5.60 -> 00809F03E802
f e r E8 02
P of
3
DHC 809F0
0
00
6
.
:
@
2.5
MAC 155.13
:
IP@

2
MAC@
:00809F03E802
IP @
:155.132.5.60
subnet mask::255.255.0.0
router
:0.0.0.0
TFTP server @:155.132.5.2
IP client
21
Remark:
Then the Call server downloads the 3 binaries files (Lanpbx.cfg ; bintscip; starttscip) and starts the automatic registration
(directory number allocation )
ALCATL0379CD *BROADCAST DHCP Offer
(xid=AEDF28E9)

UDP: IP Multicast: Src Port: BOOTP Server, (67); Dst Port: BOOTP Client
DHCP: Offer
(xid=AEDF28E9)

DHCP: Option Field
(options)

DHCP: Server Identifier
= DHCP Offer
<.alcatel.ip phone.0
= 155.132.5.1

DHCP: Renewal Time Value (T1) = 12:00:00
DHCP: Rebinding Time Value (T2) = 21:00:00
2e 74 73 63 2d 69 70 2e 30
DHCP: Subnet Mask
DHCP: Broadcast Address
= 255.255.0.0
= 155.132.255.255
DHCP: Vendor Specific Information = (Length: 15) 61 6c 63 61 74 65

6c 2e 61 34 34 30 30 2e 30
alcatel.Enterprise.0
Issue 02
323
Alcatel IP Phones
Feature description

through routers
Discover: general broadcast from IP Phone
IP@
sunetmask
router
155.131.1.50 255.255.0.0 155.131.100.100
155.131.1.51 255.255.0.0 155.131.100.100
155.131.1.52 255.255.0.0 155.131.100.100
155.132.100.101
155.132.0.0
Leased IP@ list

IP@
MAC@
155.132.5.60 -> 00809F03E802
155.131.100.100
155.132.5.1
main Com server IP @: 155. 131.1.1
DHCP discover
155.131.0.0
IP client
MAC@
:00809F03E802
IP@
:0.0.0.0
subnet mask:255.255.255.255
router
:0.0.0.0
TFTP server @:
DH C P
IP Phone
discove
r
155.131.9.53

Routers need to be configured to send the DHCP frames on the other subnet.
DHCP relay function has to be managed.
DHCP relay function is not validated by default !
ALCATL03E802 *BROADCAST DHCP Discover
(xid=AEDF28E9)

UDP: IP Multicast: Src Port: BOOTP Client, (68); Dst Port: BOOTP Server (67)
DHCP: Discover
(xid=AEDF28E9)

DHCP: Option Field
(options)

= DHCP Discover
= (Type: 1) 00 80 9f 03 e8 02
DHCP: Host Name

= TSC_DEVICE2
= 0.0.0.0

2e 74 73 63 2d 69 70 2e 30

Issue 02
324
22
Alcatel IP Phones
Feature description

through routers
Discover: from router to OmniPCX Enterprise Com server
IP@
sunetmask
router
155.131.1.50 255.255.0.0 155.131.100.100
155.131.1.51 255.255.0.0 155.131.100.100
155.131.1.52 255.255.0.0 155.131.100.100
155.132.100.101
155.132.0.0
Leased IP@ list

IP@
MAC@
155.132.5.60 -> 00809F03E802
DHCP discover
155.131.100.100
155.132.5.1
main Com server IP @: 155. 131.1.1
155.131.0.0
MAC@
:00809F03E802
IP@
:0.0.0.0
subnet mask:255.255.255.255
router
:0.0.0.0
TFTP server @:
IP Phone
155.131.9.53

00E01EEC3096 ALCATL0379CD DHCP Discover
23
(xid=AEDF28E9)

UDP: Src Port: BOOTP Client, (68); Dst Port: BOOTP Server (67)
DHCP: Discover
(xid=AEDF28E9)

DHCP: Option Field
(options)

DHCP: Host Name
= DHCP Discover
= (Type: 1) 00 80 9f 03 e8 02
= TSC_DEVICE2
= 0.0.0.0

2e 74 73 63 2d 69 70 2e 30

Issue 02
325
Alcatel IP Phones
Feature description

through routers
Offer: from OmniPCX Enterprise Com server to router
IP@
sunetmask
router
155.131.1.50 255.255.0.0 155.131.100.100
155.131.1.51 255.255.0.0 155.131.100.100
155.131.1.52 255.255.0.0 155.131.100.100
155.132.100.101
155.132.0.0
DHCP offer
To MAC@: 00E01EEC3096
Client IP@:155.131.1.50
Client MAC@: 00809F03E802
155.131.100.100
Leased IP@ list

IP@
MAC@
155.131.1.50 -> 00809F03E802
155.132.5.1
155.131.0.0
MAC@
:00809F03E802
IP@
:0.0.0.0
subnet mask:255.255.255.255
router
:0.0.0.0
TFTP server @:
IP Phone
155.131.9.53

ALCATL0379CD 00E01EEC3096 DHCP Offer
(xid=AEDF28E9)

UDP: Src Port: BOOTP Server, (67); Dst Port: BOOTP Server (67)
DHCP: Offer
(xid=AEDF28E9)

DHCP: Option Field
(options)

= DHCP Offer
= 155.132.5.1

2e 74 73 63 2d 69 70 2e 30
DHCP: Subnet Mask
DHCP: Router
= 255.255.0.0
= 155.131.100.100
= 155.131.255.255

6c 2e 61 34 34 30 30 2e 30

Issue 02
326
24
Alcatel IP Phones
Feature description

through routers
Offer: from router to IP Phone
IP@
sunetmask
router
155.131.1.50 255.255.0.0 155.131.100.100
155.131.1.51 255.255.0.0 155.131.100.100
155.131.1.52 255.255.0.0 155.131.100.100
155.132.100.101
155.132.0.0
Leased IP@ list

IP@
MAC@
155.131.1.50 -> 00809F03E802
155.131.100.100
155.132.5.1
DHCP offer
MAC@: 00809F03E802
IP@:155.131.1.50
155.131.0.0
6
MAC@
: 00809F03E802
IP@
:155.131.1.50
subnet mask::255.255.0.0
router
:155.131.100.100
TFTP server @: 155.131.1.1
IP Phone
155.131.9.53

25
Remark: then the Call server downloads the 3 binaries files ( Lanpbx.cfg, bintscip, starttscip ) and starts the automatic registration
00E01EEC3096 *BROADCAST DHCP Offer
(xid=AEDF28E9)

UDP: IP Multicast: Src Port: BOOTP Server, (67); Dst Port: BOOTP Client (68)
DHCP: Offer
(xid=AEDF28E9)

DHCP: Option Field
(options)

= DHCP Offer
= 155.132.5.1

2e 74 73 63 2d 69 70 2e 30
DHCP: Subnet Mask
DHCP: Router
= 255.255.0.0
= 155.131.100.100
= 155.131.255.255

6c 2e 61 34 34 30 30 2e 30

Issue 02
327
Alcatel IP Phones
Feature description
X Direct RTP: IP direct switching between 2 IP Phones

D
6--> Coding or
compression
6--> Decoding or
decompression
31200
31051
CS
1--> Dials: 31200
GD
D
3--> UA on UDP
2--> UA on UDP
4--> 31200 IP@
+ UDP port nb
4--> 31051 IP@

+ UDP port nb
5--> Direct RTP switching

for VOICE

Remarks:
- No software license
- Direct RTP is here to optimise the use of expensive IP channel/compression resources
- To control Direct RTP, IP domains can be be defined

Issue 02
328
Worksalso
alsoininnetwork
network
Works
26
Alcatel IP Phones
Feature description
X Traffic flow
The IP Phones is connected to the LAN
It needs to dialog with the Alcatel OmniPCX Enterprise Com
Server and with the Gx or INTIP board
The Com Server is used as a TFTP server
The Gx and INTIPA support UA signaling and voice
The INTIPB could be used to support voice only

Rem:
The INTIP supports 512 simultaneous signaling channels.
Rem:
1 IP channel is used for each call (to support the voice)
27

Issue 02
329
Alcatel IP Phones
Feature description
X Tones generation
All the tones are generated by the IP Phones
Tones are downloaded during initialization
Less traffic over IP and optimization of Gx/INTIP IP channels
Voice Guides and music on hold are generated in the
Gx/INTIP IP channels resources are used in this case

Remarks: by downloading the tones in the IP Phone we reduce the traffic and we optimised the IP channel/compression resources

Issue 02
330
28
Alcatel IP Phones
X They all generate IP QoS communication tickets

Treated by the OmniVista 4760 VoIP traffic observation tool
X Restrictions
IP Phones cannot use additional Plugware modules (V24 ..)

29

Issue 02
331
Alcatel IP Phones
X IP MG Signaling Link Back up and IP Phones

IP Phones can be associated to an IP Media Gateway
The IP Phones signaling is then encapsulated into the IP Media

Gateway signaling link
Possibility to secure an IP domain through the IPSLB of the IP
MG
The IP Phones belonging to an IP domain and attached to the IP

Media Gateway with IPSLB are also rescued
Same behavior as a TDM set

30
If an IP-Phone is inside an IP domain and if the IP Media Gateway it is attached uses an IP signalling Link Backup, this IP Phone
reacts exactly like a non IP Phone of that particular IP Media gateway in term of signalling (UA phone or Z phone).
The IP Media Gateway internal communications are possible: external communication abilities depends of trunk availability and inter
Media Gateway communications are forbidden.
Note:
- IPSLB can not create a backup link directly to a single IP Phone.
- IPSLB is available only for IP Media Gateway (common hardware), whatever the Com Server (IPRS, IPAS, IPCS )

Issue 02
332
Alcatel IP Phones
X The IP Phones attached to an IP MG with IPSLB are

rescued (IP domain management)
Com Server
Backup
signaling
Public
Operator
Unreachable IP
Phone
Com Server
IP domain
Reachable IP
Phone
IP Domain
with IPSLB
Broken IP link
IP Domain
without IPSLB
Reachable IP
Phone
31
Be careful: the signaling backup establishment needs another IP Media Gateway (reachable by the com server) with a free modem
access. This one has not been drawn upon (backup signaling link directly on com server) but it is mandatory.
To avoid some routing problems when the IP Signalling Link Backup is working, it is strongly recommended that each "rescuable" IP
Media Gateway has a particular IP domain.

Issue 02
333
Alcatel IP Phones
Examples
X IP Phone calls a UA set

Manual setup
Local @:155.131.1.35
Local subnet mask:255.255.0.0
Main Com server:155.131.1.3
MAC @
:00809F03E802
31000
UA
GD
1-->
Dials: 31000
CS
155.131.1.30
31051
2--> Signalling on UDP
155.131.1.3
3--> Voice on UDP

When there is no DHCP server it is necessary to setup manually in the IP Phone IP@ (except the MAC address which is already
defined and printed in the factory)

Issue 02
334
32
Alcatel IP Phones
Examples
X IP Phone calls a H323 terminal

Manual setup
3-->
31200: IP Abbreviated #
IP@:155.131.1.10
Local @
:155.131.1.35
MAC @
:00809F03E802
155.131.1.10
H323 terminal
1-->
Dials: 31200
155.131.1.30
GD
CS
D
31051
2--> Signalling on UDP
5--> Voice on UDP
D
4-->
B
Signalling on TCP
31200
6--> Voice on UDP

33
H323 terminals can be called from the Alcatel OmniPCX Enterprise by using an IP abbreviated number.

Issue 02
335
Alcatel IP Phones
Examples
X IP Phone calls a UA set via router (different subnetworks)

31200
Manual setup
Gx/INTIPA (ethernet parameters)
Local @:155.132.1.35
MAC @
:00809F03E802
Default Gateway IP Address: 155.131.100.100
B
UA
GD
CS
1-->
Dials: 31000
Netadmin
Default router:155.131.100.100
155.131.1.30
31051
155.131.1.3
B
155.131.100.100
155.132.100.101
Signalling on UDP
<--2
Voice on UDP
<--3

Remark:
The Alcatel OmniPCX Enterprise Com server needs to know how to reach the IP Phone in the other subnet. It is necessary to define a
default router or a static route in netadmin.
The Gx/INTIPA needs also to know how to reach the IP Phone. It is necessary to define a gateway in the Ethernet parameters of the
board.

Issue 02
336
34
Alcatel IP Phones
Examples
X IP Phone calls a H323 terminal via a router

Gx/INTIPA (Ethernet parameters)
Default Gateway IP Address: 155.131.100.100
3-->
31200: IP Abbreviated N
IP@:155.132.1.10
Manual setup
Netadmin
Default router:155.131.100.100
Win Gateway IP@: 155.132.100.101
Local @:155.132.1.35
MAC @
:00809F03E802
H323 terminal
GD
155.131.1.30
1-->
Dials: 31200
CS
155.131.1.20
31051
D
D
155.132.1.10
155.131.1.3
155.131.100.100
155.132.100.101
4--> Signalling on TCP

6--> Voice on UDP
Signalling on UDP <--2

Voice on UDP <--5

35
Remark:
The H323 terminal needs to know how to reach the Gx/INTIPA on the other subnet. It is necessary to declare in Windows parameters
a gateway.

Issue 02
337
Alcatel IP Phones
X Ordering IP Phones in Actis

See IP telephony module


Issue 02
338
36
Alcatel IP Phones

relevant documents:
Standard offer
OmniDesktop Telephones
Pre Sales presentations
IP/VoIP design guides and IP/VoIP presentations
Presales\Presentations\technology briefs\
Ethernet Power Feeding 802.af
System documentation
37

Issue 02
339
Alcatel IP Phones
Conclusion
X The success of today's business practices depends on

reducing the stress the business person experiences as a
result of the fast pace of modern communications. New
communications tools have the potential to save time and
do away with some tasks. However, the benefits of
communications technology are only realized if the
barriers to using the technology are lowered significantly
X For communications tools to assist individuals and
workgroups in performing their tasks, the underlying
product technology should be transparent, clear, concise,
easy-to-use, and have the ability to adapt and evolve at
the pace of modern business
X Alcatels family of IP Phones meets these challenges as
described before


Issue 02
340
38
Alcatel IP Phones
Appendix
X With DHCP server Vocabulary

ARP: Address Resolution Protocol
Sends IP@ to receive MAC@
RARP: Reverse Address Resolution Protocol

Sends MAC@ to receive IP@
TFTP: Trivial File Transfer Protocol

BOOTP: BOOTstrap Protocol
X DHCP: Dynamic Host Configuration Protocol

Protocol, based on BOOTP and ARP, used between server
and client
Used by servers to allocate IP@ dynamically to clients and
to configure the client IP parameters (mask, gateway)

39
The ARP protocol (Address Resolution Protocol)

-Defined by RFC 826
-Sends an IP@ to receive the associated MAC@
-each station has an ARP table
-updated by the ARP frames broadcasted over the network
-From a station when an application has to be connected to an other station it is the IP@ that is used
-To send frames between stations on Ethernet network it is necessary to know the MAC@ of each station

Issue 02
341
Alcatel IP Phones
Appendix
X DHCP exchanges
Client
All stations
Server
DHCP discover
Client requests
a dynamic IP@
to the DHCP server
DHCP offer
DHCP request
DHCP ack
Client checks that

this dynamic IP@
is not already allocated
in the subnet and waits for
the DHCP server validation
RARP request
RARP request
RARP reply


Issue 02
342
40

41

Issue 02
343


Issue 02
344
42
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
345
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
346
VoIP Quality of Service (QoS)

OBJECTIVE:
To identify the different elements allowing to control and guarantee a minimum of quality
of service in the case of voice over IP
Alcatel OmniPCX Enterprise VoIP Quality of Services (QoS)

Issue 02
347
VoIP Quality of Service

Content
X Definition
Tagging
Compression Algorithms
Traffic
IP domains
Direct RTP in Network
VoIP Statistic Tickets
X Conclusion

Issue 02
348

Definition
X A TCP/IP network doesnt guarantee a Quality of Service when

transporting real time dependant data like voice
X It is then necessary to take care about this problem
X Many features in the Alcatel OmniPCX Enterprise are implemented to
increase the Quality of Service in the case of voice over IP
Echo cancellation
IEEE 802.1Q tagging
TOS-Diffserv tagging
IP domains
X The traffic generated by voice over IP on the customer data network

has to be taken into account
VoIP Network compliance assessment mandatory


Issue 02
349

Definition
X QoS profiles
TOLL-Quality= For a good audio quality (MOS of 4)
Network round trip delay less than 150 ms

Jitter less than 20 ms
Packet loss less than 1%
NEAR TOLL-Quality= acceptable audio quality (some
perturbations, MOS between 3 to 4)
Network round trip delay less than 400 ms

BEST EFFORT-Quality= metallic voice, loss of syllables
network round trip delay less than 600 ms


MOS: Mean Of Score defined by ITU-T is a subjective measure of the voice quality performed by a sample of users listening to a
voice call over IP (indices from 1 to 5).

Issue 02
350

Definition
X Acceptable audio quality: 200 ms delay one way

X Compression and decompression (G723 or G729)
introduce delay
Average delays introduced by IP boards (GA/GD/INTIP)
for each compression/decompression
for each packetisation/de-packetisation
in G729: 120 ms
in G723: 150 ms
in G711: 100 ms
Gateway Transit function (INTIP only)
20 ms
Average delays introduced by IP Phones
in G711: 70 ms
in G729: 70 ms
in G723: 90 ms
X Conclusion: a VoIP communication cannot exceed 2

compression / decompression in G729 and 1 in G723
Compression / decompression: (Packetisation and de-packetisation) + compression / decompression of voice

packets). Used with G723 or G729

Issue 02
351

Definition
X Echo
Echo always exists in a TDM telephone call (mainly
introduced by analog phones or by the analog public

network) but it is not perceived by the calling parties
The delay introduced by VoIP can reveal this echo
echo cancellation function (at 64 ms) of the GD, GA and
INT-IP boards take care of the problem


Issue 02
352

Feature description
X IEEE 802.1p/Q tagging, TOS-Diffserv tagging

It is possible to tag data (voice over IP) coming from Gx,
INTIP boards but also from the IP Phones
The tag inserted in the Ethernet frame according to
IEEE802.1Q is 4 bytes long. It consists of:
A TPID (Tag Protocol Identifier: 2 bytes)

A TCI (Tag Control Information: 2 bytes): contains the user priority
field in its first three bits, and the VID field in its 12 last bits.
About Diffserv, the field to be modified is the TOS byte in
the IP frame header. It is composed of a DSCP and a CU

fields used to give a priority information at the IP level:
It contains a value that specifies a defined (by a RFC from the IETF)
packet management policy that will be applied to the IP packets.

802.1 Q: Q for Qualification= VLAN id

A VLAN is a domain of broadcast. The purpose is to separate the voice from the data to reduce the delay and to protect the IP phones
from broadcast storms.
VLAN policy is usually based on:
Ports, MAC address or DHCP but could also be based on protocols (IP, IPX, ), subnets, binding rules (combination of rules, for
example ports AND MAC add), authenticated (802.1x, LDAP server or Radius)
VLAN tagging (802.1Q) is most of times implemented in addition to the VLAN policy.
VID: Virtual Local Area Network Identification
DSCP: Differentiated Services CodePoint
CU: Currently Unused

Issue 02
353

Feature description
X IEEE 802.1Q tagging, TOS-Diffserv tagging (cont)

In order to manage QoS, each IP endpoints (Gx, INTIP, IP
Phones), are associated to a QoS category containing:
802.1p used: False/True

802.1 priority: 7 (from 0 to 7)
TOS/diffServ: 0 (from 0 to 63)
UDP Lost: 7
UDP Lost Reinit: 7
UDP Keep Alive: 3
Vlan id:
These parameters are used to give to the voice over IP
information's priorities at the Ethernet and IP levels (if used

in the data network)

There are 16 IP QoS categories.

UDP Lost (from 1 to 255): Link loss detection timeout, receive direction (no traffic or keepalive), transmission direction (not
acknowledged frame after several attempts).
UDP Lost Reinit (From 1 to 255): TSC-IP reset timeout after link loss is detected. It is possible to re-establish a new UA link during this
timeout.
UDP Keep Alive (From 0 to 255): message exchanged between to IP endpoints every 3 seconds by default.
Remark: If the switches and routers from the data network support the priority management, these priority information can be used to
increase the Quality of Service by giving priority to voice over IP (voice is a real time application so the delay is an important
parameter to care about !)

Issue 02
354

Feature description
X Compression Algorithms
In case of the voice over IP solutions, it is possible to
compress the voice or not (for bandwidth reasons)
The Alcatel OmniPCX Enterprise supports two compression
algorithms but not simultaneously (*):
G723.1 : 6.3 Kbits/s

G729.A : 8 Kbits/s
Delay of compression/decompression and bandwidth are very close
so the choice between G723 or G729 depends on the voice quality
required by the customer and the cost (**)
The choice between the default compression algorithm and
the coding algorithm is defined during the IP parameters

configuration

*: except in the case of the H323 terminals interconnection, then a system parameter (multi algorithms for compression) gives the
possibility during a H323 terminal communication establishment to negotiate the compression algorithm to use (G723, G729 or
G711).
e.g.: several H323 terminals configured with different algorithms.
Remark:
- default compression algorithm: G723 or G729
- coding algorithm: G711 (no compression, 64 Kbits/s)
(**) G729 usually provides a much better quality but it is also much more costly.
G723 might be acceptable by the customer (VoIP network compliance assessment enables the customer to listen to VoIP call made
on its data network with G7213 and G729)

Issue 02
355

Feature description
X Compression Algorithms: H323

First, a system parameter allows to define the default
compression algorithm used by the node:

G723.1
or G729.A
Then a choice has to be done when configuring a voice
over IP feature (according to the bandwidth constraints)

For
For
each ABC link VPN overflow over IP between two nodes

G711 or default
each H323 trunk group for H323 terminals

G711 or default
Then
a general parameter concerning H323 features is used to

determine the default mode (if chosen above)
With compression, without compression

Remark:
- The system parameter is defining the compression algorithm used by the node for all the types of compression.
- This H323 general parameter (Gx/INT IP parameters) is used to determine the default mode. If the compression is selected, the
Alcatel OmniPCX Enterprise will use the default compression algorithm defined in the system parameters.
- Which compression algorithm to use ?
Due to the high bandwidth required for G711, PCM coding should be used in LAN environment but is not recommended in the
WAN. This is due to the 64kb/s coding but also to the overhead generated by the encapsulation in IP packets, which means
around 100kb/s bandwidth at the Ethernet level.
The choice is between G723.1 or G729A. The last one is known to give a better quality of voice but a slight higher bandwidth.

Issue 02
356
10

Feature description
X Compression Algorithms: IP Phones

A choice is also done when configuring the following voice
IP Phones
For
each IP Phone, there is the choice between:
Default, with compression, without compression
If
default is selected, the Alcatel OmniPCX Enterprise checks the

following parameters
IP domain: intra-domain and extra-domain calls
If default is selected, the Alcatel OmniPCX Enterprise checks the

default, with compression, without compression
TSC/IP parameters: with compression, without compression

11
Remark: an IP Phone belongs always to an IP domain.

Issue 02
357

Feature description
X Voice algorithm choice for the IP Phones
System parameters
IP Phones
- G723
- G729
- without compression
- with compression
- default
IP domains
- with compression
- default
TSC IP parameters
- with compression

12
Without compression: G711 is used to code the voice

With compression: it depends on the "system parameters" (G723 or G729)
Remark: this configuration method allows to have a flexible working mode for the IP Phones. The compression/decompression choice
could be done at the IP Phone level, IP domain level or the same for all the IP phones.

Issue 02
358

Feature description
X Compression Algorithms: Media Gateway

A choice is also done when configuring the following voice
Media Gateway
The Alcatel OmniPCX Enterprise checks the following parameters
IP domain: intra-domain and extra-domain calls

default, with compression, without compression
If default is selected, the Alcatel OmniPCX Enterprise checks the

INT IP parameters: with compression, without compression

13
Remark: a GD/INT IP board belongs always to an IP domain.

Issue 02
359

Feature description
X Voice algorithm choice in case of Media Gateways
System parameters
- G723
- G729
IP domains
INT IP parameters
- with compression
- default
- with compression

14
Without compression: G711 is used to code the voice

With compression: it depends on the "system parameters" (G723 or G729)
Remark: this configuration method allows to have a flexible working mode for the Media Gateways. The compression/decompression
choice could be done at the IP domain level or the same for all the Media Gateways.

Issue 02
360

Feature description
X Rules for voice compression algorithm choices

In case of a call, between 2 IP Phones for instance
configured with different algorithms, the choice is to

economize the bandwidth and therefore to do a
compressed call.
This choice is, of course, done by the Call server which will
give the order, using signaling messages, to the IP devices

to compress their voice
In case of voice over IP Networking, it is recommended to
use the same compression algorithm on each node (to

avoid conflicts)

15
Example: a call between an IP Phone from domain 1 (compression for extra domain calls) and a GD board in domain 0 (no
compression for extra domain calls) will result in a compressed call (optimization !)

Issue 02
361

Feature description
X Compression Algorithms (cont)

X Bandwidth needs versus CODEC and packetization time
(without VAD)
LAN Configuration
WAN Configuration
Coding/ Compression
Bandwidth
at IP level
(Kb/s)
Bandwidth at
Ethernet level
(Kb/s)
Bandwidth at
PPP level
(Kb/s)
Bandwidth at PPP level

with header compression
(Kb/s)
G723.1 (6.3 Kb/s) framing of

30ms
G729A (8 Kb/s)
With framing of 30 ms
G711 (64 Kb/s)
16.7
26.6
18.75
8.85
18.2
23.4
28.1
38.3
20.3
26.6
10.4
11.7
72.9
78.1
82.8
93
75
81.3
65.1
66.4

16
VAD: When a user is not talking (then a silence is detected), the Alcatel OmniPCX Enterprise has the possibility to generate a silence
flag in order to decrease the traffic over IP. On the other side (other equipment), the Alcatel OmniPCX Enterprise receives this flag
and generates a silence. Since the silence flag is using less bandwidth than a normal silence (=noises), it is then possible to
reduce the traffic over IP. Statistics are showing that a traffic reduction of 40% can be obtained. But the maximum bandwidth may be
used at any time in the call !!
The IP Bandwidth is calculated with an IP packet size equal to:
- The voice payload (240 bytes for G711 and a framing of 30 ms, 160 bytes for G711 and a framing of 20 ms, 24 bytes for G723,
30 bytes for G729 and a framing of 30 ms, 20 bytes for G729 and a framing of 20 ms) +
- The RTP header (12 bytes) +
- The UDP header (8 bytes) +
- The IP header (20 bytes).
The Ethernet Bandwidth is determined with an Ethernet frame equal to the preamble (8 bytes) + MAC header (14 bytes) + IP packet
+ CRC header (4 bytes)+ inter-frame silence (12 bytes).
Preamble MAC IP UDP RTP Voice payload CRC
Ethernet Frame
The PPP Bandwidth is determined with a frame equal to the IP packet + PPP encapsulation (12 bytes).
Bandwidth at PPP level is with RTP/ UDP/IP header compression (header: 2 bytes). Therefore, the encapsulation size for PPP is 8 bytes.

Issue 02
362

Feature description
X How to calculate the bandwidth needed or generated ?

First, calculate the bandwidth for one call
On a WAN (IP level)
Full duplex (most cases): use the figure in the column "bandwidth at IP
level
Half duplex: multiply by two this figure (worst case)
Then, do an Erlang traffic calculation to obtain the total
number of calls between two areas
Multiply this result with the bandwidth for one call to obtain
the total bandwidth

17
IP level:
Full duplex WAN: for a 64 Kbits/s WAN connection, there is 64 Kbits/s each way
ex: using G723, the bandwidth needed will be 18.75 Kbits/s per call (for maximum voice quality !)
Half duplex WAN: for a 64 Kbits/s WAN connection, there is 64 Kbits/s in total
ex: using G723, the bandwidth needed will be 37.50 Kbits/s per call (for maximum voice quality !)
Remark: the majority of the WAN access are full duplex.
Ethernet level:
Using G723, the bandwidth needed will be 53.2 Kbits/s per call (for maximum voice quality !)
Remark:
- the VAD option can decrease statistically the bandwidth of around 50 %.
- real time constraints: an IP Phone using G723, for instance, will, during a conversation, generate voice IP packets with a constant
rate of 18.75 Kbits/s. To keep the real voice quality, these packets need to arrive to the other IP Phone respecting this rate. If this rate
is not respected by the IP network (slow traffic on the WAN, congestion) then the voice quality will decrease (packets lost, high jitter,
high delay).

Issue 02
363

Feature description
X Bandwidth calculation examples of a LAN

One voice communication using G.723.1 algorithm without
VAD ( Voice Activity Detection )
26.6 Kbs (Ethernet level)
One voice communication using G.723.1 algorithm with
VAD
26.6 + 3.7 = 30.3 Kbs ( 1 is speaking , 1 is listening )

26.6 + 26.6 = 53.2 Kbs ( both are speaking )
3.7 + 3.7 = 7.4 Kbs ( Nobody is speaking )
Depending on the environment VAD is an extra and should not be
taken into account in the calculation
Bandwidth for a Fax communication using the Fax Relay
protocol
23 Kb/s at Ethernet level


Issue 02
364
18

Feature description
X Total traffic calculation and resulting bandwidth

Do the classical number of circuits calculation (Erlang table),
for the voice calls (Nv) and the fax calls (Nf)
To find the resulting total bandwidth Br
Br = NvBv + NfBf
Bv = bandwidth for a voice call

Bf = bandwidth for a fax call

19
Switched data network are recommended (more bandwidth available !)

Remark:
3 Mbps correspond to 55 G723.1 voice communications without VAD.
Voice activity detection (VAD), silence suppression and silence regeneration sends voice frames only when the parties actually talk and
send flags when the parties do not talk.
This means that, around 40% of time (therefore bandwidth) is saved and reallocated for other traffic (e.g. data).
Silence is regenerated on the other side, it is used to simulate the presence of the interlocutor: this is called comfort noise generation.
VAD can be deactivated.
The GD/INT-IP boards must not be connected to an Ethernet or HUB which is shared with other equipment.
The Alcatel OmniPCX Enterprises call server may be connected to the same Ethernet (or HUB) as the Gx/INT-IP except if the CCd,
CSTA or 4980 applications are used.
Only the permanent connections between routers must be used. The PPP and X25 connections (connection protocols with prior
establishment) are not recommended.

Issue 02
365

Feature description
X IP domains are used to avoid voice congestion in the

LAN/WAN and optimize voice quality by:
Limiting the number of calls between some areas
CAC: Call Admission Control
Controlling the access to Alcatel OmniPCX Enterprise
resources
Voice guides
Music on hold
Conferences


Issue 02
366
20

Feature description
X IP domains are used to control:

IP direct switching between IP devices
Signaling exchange
X IP devices concerned:
Gx/INT-IP boards
IP-Phones
4980 IP Telephony, IP Web softphone
X IP domains management is a stand alone concept:

Defined independently on each node
No audit and broadcast
Can not cover 2 nodes

21
H323 features are not concerned by IP domains. The services concerned are:
- IP phones
- A4980 IP telephony R2.2
- Media Gateways

Issue 02
367

Feature description
X Domain management (1000 maximum per node):

IP@ or range of IP@ belonging to the domain
IP domain type:
IP
Non-IP
Intra-domain coding algorithm
With (defined in system parameters )==> G723.1 or G729

Without ==> G711
Default ==> use of the IP parameter of the TSC-IP parameters of
an phone or INT-IP parameters of an INT-IP board
Extra-domain coding algorithm
With (defined in system parameters )==> G723.1 or G729

Without ==> G711
Default ==> use of the IP parameter of the TSC-IP parameters of
an phone or INT-IP parameters of an INT-IP board


Issue 02
368
22

Feature description
X Domain management:
Extra-domain maximum of compressors used
-1 ( no restriction )
0 to 32000
Compression resources reserved for extra-domain

incoming or outgoing VoIP calls
IP Quality of Service category: ...

23

Issue 02
369

Feature description
X IP domains are divided in 2 types:

IP type
non-IP type
X A default domain called backbone is defined (Domain 0)

Rule: all IP devices not associated to a specific domain
belong to the default domain


Issue 02
370
24

Feature description
X Rules for IP devices belonging to IP type domains:

Signaling exchange always with IP devices belonging to
default domain
VoIP communications with direct RTP authorized with IP
devices belonging to:
the default domain

the other IP type domains
Priority for compression resources selection:
1-->
2-->
3-->
local domain
default domain
Other IP type domains
No VoIP communications with direct RTP with a non-IP
domain

25
IP type domains are used in case of bandwidth constraints on the WAN

or/and routers with limited packet processing powers

Issue 02
371

Feature description
X Rules for IP devices belonging to non-IP type domains:

Signaling exchange always with IP devices belonging to the
same domain
VoIP communications authorized with IP devices belonging
to:
the same domain with direct RTP

the other domains without direct RTP
Priority for compression resources selection:
1-->
local domain
No VoIP communications with direct RTP with a non-IP
domain


Issue 02
372
26

Feature description
X Domains overview
Direct RTP
IP domain 1
IP domain 2
Default
domain
non-IP domain
Direct RTP

27

Issue 02
373
Local private to public overflow

Feature description
X local private to public overflow for

CAC overflow and no compression resources available
A set from domain 1 wants to call a set from domain 2
No compression
resources
available
PSTN / ISDN
Or No compression
resources available
Domain 2
Domain 1
HQ
Media Gateway
Automatic
overflow of
communications
over PSTN/ISDN
Media Gateway
OmniPCX Enterprise
Or IP Saturation :
Maximum of extra
domains calls
reached
WAN/LAN

CAC overflow when the maximum number of simultaneous incoming or outgoing calls on one domain is reached (CAC saturated), if
configured, the overflow on public network is automatically put in place for any new calls.
No compression resources: when there is no compression resource available on the calling or called domain, the overflow on public
network is automatically put in place for any new calls.
Domain determination :
The domain of an a hunting group is the one of the groups head.
The domain of an attendant group is the first domain found in the group.
The domain of a DECT phone is the one of the last base, on which it hangs up.

Issue 02
374
28

Feature description
X IP domains Example 1: VoIP restriction between 2 Media

Gateways
Leased line at 64 Kbs

with G723.1 ==>2 VoIP calls with good quality
(according to the audit)
GD
GD
IP MG1
Leased line
64 Kbs
IP MG2
2 VoIP calls

29

Issue 02
375

Feature description
X IP domains Example 1: VoIP restriction between 2 Media

Gateways
With 3 simultaneous VoIP calls established

==> Voice Quality will be very bad !!!
GD
GD
IP MG1
IP MG2
Leased line
64 Kbs
3 VoIP calls


Issue 02
376
30

Feature description
X IP domains Example 1 solution: domains configuration

With 3 simultaneous VoIP calls established
==> Voice Quality will be very bad !!!
GD
GD
IP MG1
IP MG2
Leased line
64 Kbs
Domain
Type
Nb comp
: default
: IP
: -1 (no control )
Domain
Type
Nb comp
:1
: IP
:2
Only 2 VoIP calls are authorised !

31

Issue 02
377

Feature description
X IP domains Example 2: keep the leased line between

routers for Data
Leased line
VOICE
Crystal MG 1
I
N
T
I
P
A
R
T
2
B
Crystal MG 0
R
T
2
A
C
P
U
Leased line
64 Kbs for Data
20 IP Phones
20 IP Phones


Issue 02
378
I
N
T
I
P
A
32

Feature description
X IP domains Example 2 Solution: to define 2 types of

domains (IP & non-IP)
Domain
Type
Nb comp
:1
: non-IP
: -1 (no control )
VOICE
Crystal MG 1
20 IP Phones
I
N
T
I
P
A
Signalling for IP phones

only local IP coupler
Domain
Type
Nb comp
Leased line
R
T
2
B
: 0(default)
: IP
: -1 (no control )
Crystal MG 0
R
T
2
A
C
P
U
Leased line
64 Kbs for Data
VoIP communications not authorized

between IP & non-IP domains

I
N
T
I
P
A
20 IP Phones
Signalling for IP phones
33

Issue 02
379

Feature description
X IP domains Example 3: bandwidth & voice quality

optimization
GD
10 IP Phones
10 IP Phones
Leased line 256 Kbs
IP MG1
G723.1
Bandwidth optimization
G711
Voice Quality optimization
Domain
:1
Domain
:1
Type
: IP
Type
: IP
Nb comp : -1 (no control )
Intra-domain coding algorithm: G711
Extra-domain coding algorithm: with compression
G711
Voice Quality optimization
Domain
: 0 default
Domain
: 0 default
Type
: IP
Type
: IP


Issue 02
380
34

Feature description
X Direct RTP in Network

X Direct RTP in network is seen as an extra domain call
Possibility to control the number of calls
X H323 equipment's have to support the fast start feature

X All the nodes of the network need to have the "direct RTP in
network" boolean activated
X In the case of an ABC link, the overflow of the voice
through the public network (or other) according to the IP
network QoS is not available

35
Remark: there is a system parameter for each node to validate or not the "direct RTP in network" feature.

Issue 02
381

Feature description
X VoIP Statistic Tickets

Voice over IP statistic tickets contain information about
Quality Of Service concerning boards and terminals
The Com Server requests the generation of statistic tickets
at the beginning of each VoIP call concerning the

following equipment's
INTIPA
and B boards
e-Reflexes
4980 IP telephony
GD
GA
At the end of the call, the tickets are sent to the Com Server
These tickets are stored on the CS hard disk and every hour
a new file is created with the compressed tickets

The size of each ticket is 256 Bytes maximum

Issue 02
382
36

Feature description
X VoIP Statistic Tickets

The content of a ticket can be displayed on a terminal using an
OXE maintenance command but it is not a reporting tool
Reporting is performed by the OmniVista 4760

37

Issue 02
383

Feature description
X Reporting with the OmniVista 4760

End date time
Node number
Rack number
Board number
Equipment type (INTIP, IP-Phone, GA, GD, 4645)
Source IP address
Source extension number (only for IP-Phone)
Destination IP address
destination extension number (only for IP-Phone)
Call Duration (seconds )
Compression algorithm used (G711, G723, G729A)
Number of packets sent
Number of Packets received
Number of packets lost
Delay table
VoIP quality
Jitter table
information
BFI density
information used by the

4760

In the OmniVista 4760 the principle used for VoIP tickets or Traffic observation are similar:
Creation, on the PCX, of files containing information about network traffic,
Scheduled synchronization and retrieval on the 4760 server,
Loading of the files in the database, cumulative counters on many periods,
Traffic analysis
Data tracking: Sending alarms or e-mails if thresholds are exceeded
VoIP Predefined reports

Issue 02
384
38

Feature description
X VoIP performance reports are divided in two parts

Traffic analysis reports: gives information about volume of
sent, received, and lost packets. This volume is calculated by

OmniVista 4760, taking into account the voice and SID (silence
identification) packets, the framing and compression algorithm
Quality of transmission: gives information on the parameters
that may decrease the quality of the voice communications:

Roundtrip delay
BFI (bad frame interpolation)
Consecutive BFI
BFI time distribution (or BFI concentration)
BFI rate: it is the number of consecutive BFI/number of packets.
Jitter depth
In OmniVista 4760, a threshold is set up for each parameter;
when one or several values are beyond these thresholds in a VoIP

CDR, this CDR is out of range*

39
CDR: Call Detailed Record

Roundtrip delay: In OmniPCX Enterprise CDRs, it is the round trip delay (in millisecond) to send a packet.
BFI (bad frame interpolation): It is an extrapolation packet send by the DSP, when it did not receive anything from the network,
because of too much delay or loss of the packet. PLC (packet lost concealment) is a way to do that. There are three parameters
related to BFI.
Consecutive BFI: Sometimes, the DSP sends consecutive BFI. When there are too many consecutive BFI, there is a hole in the
communication, and the quality is bad.
BFI time distribution (or BFI concentration) is the % of BFI during 10s of voice communication. Depending on this %, a counter is
incremented.
BFI rate: it is the number of consecutive BFI/number of packets.
Jitter depth: when the delay to send a packet is too long, BFI are played. When the delayed packets arrive in the DSP, they have to be
stored before being sent in the next frame. When there are too many packets in this buffer, the quality is not good. The jitter depth is
the number of packets waiting in the DSP buffer.
*For example, the threshold for the roundtrip delay is 150ms. When the roundtrip delay exceeds 150 ms in a CDR, this last one is out
of range.
The analysis of the out of range CDRs provides a global follow up of the VoIP quality.

Issue 02
385

Feature description

Example: Traffic analysis on equipment, daily volume


Issue 02
386
40

Feature description

Example: Traffic analysis on IP addresses, detailed report

41

Issue 02
387

X Before a voice over IP offer, it is recommended to make a voice over IP

audit
By taking into account the customer data network architecture
In order to simulate voice over IP calls to see the consequences on
the network and to compare it to the voice over IP requirements
X No license for the OmniPCX Enterprise
X The VoIP performance license is mandatory for the reporting on
OmniVista 4760 (allows ticket loading, cumulative counter,
computation, and ticket cleaning in the database)
The Monitoring License might be needed for sending alarms or
e-mails if thresholds are exceeded *

*The monitoring license is an option of the Accounting license meaning that monitoring can not be provided without the
accounting license.

Issue 02
388
42


43

Issue 02
389


relevant documents:
Standard offer, section Introduction and Architecture
IP-PCX Networks
Design Guide,VoIP Solutions and QOS Aspects with
OmniPCX Enterprise ed8b

IP
Domains & VPN Hops ed1

Audio Quality ed1
VoIP


Issue 02
390
44

Conclusion
X Many features in the Alcatel OmniPCX Enterprise are

implemented to increase the Quality of Service in the case
of voice over IP
Echo cancellation
IEEE 802.1Q tagging
TOS-Diffserv tagging
IP domains
X To analyze the traffic, Voice over IP statistic tickets contain

information about Quality Of Service concerning boards
and terminals
X The OmniVista 4760 is used for reporting on the quality of
the communications over IP
45

Issue 02
391


Issue 02
392
46
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
393
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
394
SIP Overview

OBJECTIVES:
To define SIP protocol
To define SIP entities
To identify SIP clients
To describe the main SIP features
To describe the SIP clients registration process
To describe the forking mechanism
To describe the Alcatel OmniPCX Enterprise SIP implementation
To compare SIP and H.323
Alcatel OmniPCX Enterprise SIP Overview

Issue 02
395
SIP Overview
Content
X Definition
X Interaction with others services
X Conclusion
X Appendix


Issue 02
396
SIP Overview
Definition
X SIP (Session Initiation Protocol) is an IP signaling protocol designed to

establish, to maintain and to end multimedia sessions between
different parties.
It operates on a client-server mode.
X It is based on the exchange of text messages with a syntax similar to
that of HTTP messages. Elements of the SIP world are identified by SIP
URLs similar to e-mail addresses.
X SIP sessions involve one or more participants and can use unicast or
multicast communications
X SIP is text-encoded and highly extensible. It may be extended to
accommodate features and services such as call control services,
mobility, interoperability with existing telephony systems, and more.
X SIP standards
RFC 2543,2327
RFC 3261,3262,3264,3265

It is important to note that SIP does not provide an integrated communication system. SIP is only in charge of initiating a dialog
between interlocutors and of negotiating communication parameters, in particular those concerning the media involved (audio,
video). Media characteristics are described by the Session Description Protocol (SDP). SIP uses the other standard communication
protocols on IP: for example, for voice channels on IP, Real-time Transport Protocol (RTP) and Real-time Transport Control Protocol
(RTCP). In turn, RTP uses G7xx audio codecs for voice coding and compression.
Unlike H.323, the SIP protocol can rely on the IP network transport protocol in datagram mode User Datagram Protocol (UDP) in
addition to the IP network transport protocol in Transmission Control Protocol (TCP) connected mode. UDP has the advantage of
being an unconnected protocol that facilitates swift exchanges. It does not guarantee datagram reception and transmission sequence
preservation. Thus, SIP carries out these functions, using retransmission, acknowledgement and sequencing mechanisms.
URL: Uniform Resource Locators
HTTP : HyperText Transport Protocol

Issue 02
397
SIP Overview
Feature description
X SIP entities
A SIP network is composed of four types of logical SIP
entities:
User Agents
Proxy server
Registrar
Redirect server (not implemented in the call server)
Each entity has specific functions and participates in SIP
communication as a client (initiates requests), as a server

(responds to requests), or as both
One physical device can have the functionality of more
than one logical SIP entity. For example, a network server

working as a Proxy server can also function as a Registrar at
the same time

Issue 02
398
SIP Overview
Feature description
X User Agents
In SIP, an User Agent (UA) is the endpoint entity
User Agents initiate and terminate sessions by exchanging
requests and responses
RFC 2543 defines the User Agent as an application, which
contains both an User Agent client and User Agent server,

as follows:
User
Agent Client (UAC): a client application that initiates SIP

requests
User Agent Server (UAS): a server application that contacts the user
when a SIP request is received and that returns a response
Some of the devices that can have an UA function in a SIP
network are: SIP phones, telephony gateways, workstations

....


Issue 02
399
SIP Overview
Feature description
X User Agents
Software and hardware solutions are available for the User
Agents (or SIP endpoints)
SIP phone Thomson ST2020
SIP Softphone
SIP uses the Session Description Protocol (SDP) to describe audio,
video and multimedia sessions

- Example of softphone: "HearMe SoftPhone" from IBM

Issue 02
400
SIP Overview
Feature description
X Proxy server
A Proxy server receives SIP requests and, based on
information that it has available, forwards that request to

one or more other SIP entities
A proxy server primarily plays the role of routing: its job is to
ensure that a request is sent to the targeted user
Proxies are also useful for enforcing policy (for example,
making sure an user is allowed to make a call)
X Registrar
A Registrar is a server that accepts REGISTER requests for
the purpose of updating a location database with the

contact information of the user specified in the request
Registrar
The registrar is in charge of collecting SIP set registration requests, and then of transmitting the data to the location server.
For an SIP user, the registration consists in sending a REGISTER request to the server. This request contains its actual address at a
given time as well as the period of validity of this address.
A user can register under several addresses at the same time. In this case, the call will be routed to all his physical URLs (forking
feature).
Location server
The location server contains the database of "logical" URL - "physical" URL (current address to be actually called) relations. This
database can be entered from terminal registrations, or using other means chosen by the manager.
When a call is established, the INVITE request contains the logical URL of the recipient user. This URL cannot be used to route the call.
On receiving the request, the proxy server consults the location server to identify the user's actual URL, then routes the request to this
URL.
Proxy
The proxy is an intermediate entity that operates as a client or a server by transmitting requests for a User Agent.
The main function of the proxy is routing. On receiving an INVITE request, it transmits the request either to the recipient set, or to
another proxy, which is "closer" to the set.

Issue 02
401
SIP Overview
Feature description
X OmniPCX Enterprise R6.x: SIP Implementation

The Alcatel OmniPCX Enterprise R6.x is a SIP enabled Call
Server by integrating SIP Proxy and SIP Gateway functions
The Alcatel OmniPCX Enterprise R6.x integrates seamlessly
the SIP clients to inter-work with:
the traditional terminals (Analog, Reflexes, IP Reflexes, H323)
the traditional trunks (PSTN, ISDN)


Issue 02
402
SIP Overview
Feature description
X SIP enabled OmniPCX Enterprise

DECT
Windows XP
Win Messenger
Reflexes
Phone
PSTN/ISDN
Thomson
ST2020
IP Phone
SIP
SIP
Media GW
Mailbox
LAN
Internet
@
LDAP
OmniVista
LDAP
Directory
SIP
OmniPCX
Entreprise

SIP
Windows XP
Win Messenger
or
Other
REMARK:
A SIP user has the advantage of Voice Mail services
- Available in G711 with 4635H and 4645
- mailbox allocation
- message waiting notification to SIP users
- voice mailbox handling via DTMF

Issue 02
403
SIP Overview
Feature description
X Registration of a SIP user

Each time a SIP client is switched on (SIP phone ...), it sends
a registration request with a leased time value
John
Wayne
Hostname: SIP1
Register
From: 35800@sip.alcatel.com
To: 35800 @sip.alcatel.com
Contact: 35800 @SIP1.alcatel.com
Register
From: 35801@sip.alcatel.com
To: 35801 @sip.alcatel.com
Contact: 35801 @SIP2.alcatel.com
James
West
Hostname: SIP2
Registrar
Location
Database
Proxy
When the client is switched off, it sends a de-register request
with a null leased time

SIP1,SIP2: hostname of the SIP phone or PC supporting the SIP client

sip.Alcatel.com: domain corresponding to the IP@ of the SIP proxy SIP (e-cs)
Alcatel.com: main domain name containing the SIP clients and the e-cs (SIP proxy)
John Wayne registration:
In the SIP client, the following must be configured:
- the DNS server IP@ (ex: 156.032.1.50)
- IP domain name ( Alcatel.com)
- the SIP proxy IP@ (ex: sip.Alcatel.com). At the DNS server level, a link has to be made
between sip.Alcatel.com and the IP@ of the Call Server (SIP proxy). Example:156.032.1.3
Notes:: In the resolve.conf file of the e-CS, the domain name (Alcatel.com) is configured.
When a terminal is connecting, it sends to its proxy (sip.Alcatel.com) its directory number and the machine hostname (Directory
number@hostname.domain )
The proxy sends this information to the registrar to confirm the SIP client registration. The registrar then updates the localization
database (the client will then be reachable by other clients).
The SIP protocol allows this mobility because whatever the machine hostname used to connect the SIP client, the URL used is
automatically updated in the localization database.

Issue 02
404
10
SIP Overview
Feature description
X Personal mobility
One of the advantages of SIP is that it supports personal
mobility through the separation of user addressing and

device addressing. When a user turns on, or logs into, a SIP
device, a registration message containing the user address
and the address of the device where the user is currently
connected is sent to a location server.
The SIP address consists of a user part and domain part.
When someone wants to communicate with a user of a SIP

device, the connection request is sent to the SIP server, and
the location server is queried to see where this particular
user is logged in.

11

Issue 02
405
SIP Overview
Feature description
X SIP registrar & location (stores SIP phones URL, IP @)

Registration
database
SIP phone
192.168.3.2
IP
5000@sip.company.com
REGISTER request
5000@sip.company.com
is registered at
192.168.3.2
Registrar
ECS
SIP terminals should be declared in MAO database
Allocation of subscriber's parameters (connection category, )

If the user is not declared in the MAO
SIP trunk group parameters are allocated to the SIP user
the SIP user cannot be called via the proxy
Authentication (via login/password) is possible if the SIP user is declared in MAO.

INVITEs and REGISTERs are authenticated.
location defined by
register information
legacy information retrieved via MAO (for declared SIP phones)

12
A new type of user has been created: external user (which is not a local user, neither a network member).
DNS resolution for inter domains calls can be done, by using the internal DNS server.
First, a user registers on his SIP phone. His address of record is "sip:5000@sip.company.com". His SIP phone must be reached at
"sip:192.168.3.2". Would B use another SIP phone, his address of record would stay the same.
Digest authentication is used. B must provide a user name and a password so that he can register his SIP phone.
Digest authentication is an authentication mode where some parameters(e.g. the password) are not sent in the protocol, but used on
both side for a calculation based on an algorithm and a key.
Basic authentication (where all the parameters are sent in the protocol) is not implemented in the OmniPCX Enterprise R6.0

Issue 02
406
SIP Overview
Feature description
X A SIP session is established between an UAC and an UAS:

Directly
Philip
35800
Eric
35801
Invite SIP: 35801@poste1.alcatel.com
Hostname: poste1
Domain: Alcatel.com
Or via a proxy server
Location database
philip@alcatel.com
=
office1.alcatel.com
Philip
Invite sip:philip@alcatel.com
User Agent
Robert
Proxy

office1.alcatel.com
13

Issue 02
407
SIP Overview
Feature description
X An user can have a SIP client in a PC and a SIP phone at

work
These two clients can be switched on at the same time. The
user will have 2 different addresses.
X A Proxy Server can send an invite request toward several

destinations via the "forking" mechanism
If there are several registrations for the same user, the
server can call all destinations
In parallel mode (the server uses the first that answers)
In sequential mode (if the first doesn't answer, it tries the second )
This mode cant be used in the Alcatel OmniPCX Enterprise


Issue 02
408
14
SIP Overview
Feature description
X Forking in parallel mode

Location database
philip@alcatel.com
=
PC1.alcatel.com
Station1.alcatel.com
Philip
Invite sip:philip@alcatel.com
User Agent
Robert
Proxy
PC1.alcatel.com
Philip
User Agent
Station1.alcatel.com

15

Issue 02
409
SIP Overview
Feature description
X SIP users services

Full user integration with the following services:
Making internal/external calls
with User Accounting and Barring for PSTN access
Call by name
Receiving internal/external calls
Caller/called identity
Call forwarding (unconditional, busy, no answer)
Call hold, consultation hold
Enquiry call / Transfer
3-way Conference
Do not disturb
Mailbox allocation / Voice message notification
Touch-tones (DTMF)
Call waiting (SIP terminals dependent)
Secondary number In & Out (depends on the SIP phone)
Find me (forking)
Full user integration means that a SIP user is declared in the database and considered as a standard user (UA,Z)
Incoming & Outgoing Call Screening (internal call barring) is not implemented in ECS proxy/GW
Voice Mail services:
- Available in G711 with 4635H and 4645
- mailbox allocation
- message waiting notification to SIP users (new messages only)
- voice mailbox handling via DTMF

Issue 02
410
16
SIP Overview
Feature description
X SIP and open communication applications

SIP trunks are mandatory for the OmniTouch UC access
Voice &
Business
Data
applications
Networks
IP, PSTN,
GSM, GPRS,
UMTS, WLAN,
Bluetooth,
etc
Web Sites
Collaboration
Email Directories
Speech Access
Corporate
Resources
Anywhere

Any Device
17

Issue 02
411
SIP Overview
Feature description
X As explained before, SIP Gateway & SIP Proxy Server is available with
Alcatel OmniPCX Enterprise R6.x
X SIP Gateway & SIP Proxy Server is also available on existing Alcatel
OmniPCX 4400 in previous releases by networking it with an
OmniPCX Enterprise in R6.x
In this case, some hardware are mandatory:
1 small rack (or more)
1 CS board (with the daughter boards: XMEM)
1 GD board (with the daughter boards: HSL, MCV24)
1 PRA-T2 board (or more) to set up an ABC link with the 4400
1 MEX board (or more) for the extension racks
Some GA boards in order to provide compressors (MCV24)
X Networking: the mode direct RTP in network is mandatory


Issue 02
412
18
SIP Overview
Feature description
X SIP implementation summary in OmniPCX Enterprise R6.x

Located in the Call Server
SIP Registrar functions
SIP Proxy
Inter-work with standard SIP terminals: Phone Sets, Softphones, ...

Telephone SIP services
Forking proxy
if several callees possible locations, several parallel requests

UDP or TCP connections
Does not support multicast, encryption
SIP Gateway
Multi-Localization, Authentication services
legacy<->SIP equipment calls

inter-working services between SIP users & other non SIP users
Voice Mail services for SIP clients
SIP users can also use OmniPCXs Voice Mail server

SIP notification (new messages only) and DTMF voice mailbox handling

19

Issue 02
413
SIP Overview
Provisioning
X SIP terminals per node: 1000 max

X Simultaneous SIP communications per node: 360 max
X Authentication (digest mode)
Availability depends on the SIP terminal type


Issue 02
414
20
SIP Overview
X a SIP user cannot be

a "hotel" set,
supervised by CSTA
CCD agent
X A SIP user cannot belong to:
a group of sets,
a pick-up group,
a Boss/Secretary set.
X Other SIP entities
If allowed in management database undeclared SIP entities can
also be registered in the PCX registrar in order to use SIP location
in PCX.
level of phone service :
default accounting and discrimination,

no voice mail services,
no authentication of calls coming from undeclared SIP entities.

21

Issue 02
415
SIP Overview
X SIP clients (bunches of 10)

Central area/subscribers accesses/Voice over IP or
Peripheral area/Area X-Area name/Voice on IP/IP trunks
X SIP Gateway license

Enterprise Com server/Com Server licenses/SIP gateway

22
SIP users
Enter the number of SIP sets declared in the central area. Actis uses this value to calculate the compressors on MCV/MADA boards (or
GIP in Crystal) and issues the licenses required for the operation of these terminals. The licenses are issued in blocks of 10
SIP gateway
SIP (Session Initiation Protocol) is a VoIP signaling protocol, offering services similar to H323.
SIP gateway links SIP clients with the Call server. SIP clients may be PCs, pocket PCs hardware phone sets. This means they can
communicate with the terminals linked to the media gateway (analog sets, UA, mobiles, etc.) and have advanced telephone
functions: putting on hold, transfer, forwarding, conference, call filtering, etc.).
The services available depend on the terminal used.

Issue 02
416
SIP Overview
X SIP trunks
Central Area/Private Network
maximum number of simultaneous SIP communications:
between declared users (SIP or Legacy) and non declared users (Internet)
for SIP operator connection

23
VoIP SIP network links

Type in the number of simultaneous calls on the IP link for the SIP terminals. Actis determines the number of MCV cards in each
gateway media in the central zone.

Issue 02
417
SIP Overview
In the Alcatel Business Partner Web Site BPWS, under Pre

documents:
X Standard offer, section Distributed Architecture and

Networking
X Presales documents, SIP in OXE release 5.0Lx ed2b
X System Documentation, section Functional
Documentation IP-PCX networks SIP
X Others (Feature List and Product Limits, marketing

Issue 02
418
24
SIP Overview
Conclusion
X The benefits to the enterprise

SIP reduces the total cost of ownership for telephony, in
nearly all cases, by exploiting an enterprises private IP

infrastructure
When combined with presence, location and mobility
applications, SIP increases communications efficiency
Adding SIP to the repertoire of protocols understood and
handled by a modern communication server provides

gateways between SIP and other types of telephony
including analog and digital trunks, frame-relay, H.323...
SIP terminals are PABX platform independent; which means
that they can be used on any SIP compatible telephonic

communication server
25

Issue 02
419
SIP Overview
Appendix
X OmniPCX Enterprise SIP strategy

Active participation in SIP organizations
One of the principal active members of the SIP Center

Financial stake in Ubiquity, founder of the SIP Center
ECMA
Also active in
and

Alcatel is a major proponent of the SIP protocol through its participation in the company Ubiquity. Ubiquity is one of the founding
members of the SIP Center forum, and is equally active in the IETF standardization organization.

Issue 02
420
26
SIP Overview
Appendix
X SIP interoperability and cooperation
Interoperability tests with Partners standard SIP terminals
Thomson SIP phone ST2020

Ubiquitys Softphone (Helmsman Desktop for SIP)
Others
Interoperability tests with Ubiquitys Proxy Server (AAPP)
Helmsman SIP Network Server)
SIPit (9th SIPit, Dec 2001 in San Diego)
OmniPCX Enterprise proxy classified as intermediate level

Inter-operated with 21 companies
Standardization activity: Internet Drafts

Common choices for implementation

27
Technologies: SIP Stack (Linux, Solaris, NT), Proxy, CPL

Ubiquitys Products in AAPP (Alcatel App Partner Program)
SIP Gateway services to push
- attended transfer
- conference with signaling
- callback request (on no answer, busy)
SIP Proxy services to push
- call pick-up
- find-me (forking proxy)
- screening

Issue 02
421
SIP Overview
Appendix
X Programming SIP
SIP is familiar to Web developers due to the similarities with
HTTP and SMTP
APIs to develop new services
CPL
SIP-CGI
SIP-Servlets
JAINTM
Parlay

28
CPL (Call Processing Language)

This was the first API developed for SIP. Strictly speaking, it is not an API, but an XML-based scripting language for describing and
controlling call services. The SIP-CPL draft can be found on the IETF Website.
SIP-CGI
In the World Wide Web, the Common Gateway Interface (CGI) has served as a popular means of programming Web services. CGI
scripts have been the initial mechanism to make Websites interact with databases and other applications. Due to the similarities
between the SIP and HTTP, CGI is a good candidate for service creation in an SIP environment.
SIP Servlets
An HTTP servlet is a Java application that runs on a Web server or Application server and provides server-side processing, typically to
access a database or perform e-commerce processing. It is a Java-based replacement for CGI scripts, Active Server Pages (ASPs) and
proprietary plug-ins written in C and C++. SIP Servlets are very similar to HTTP Servlets; they simply enhance the interface to support
SIP functions. Because they are written in Java, servlets are portable between servers and operating systems. The SIP Servlet
specification can be found on the IETF site.
JAIN APIs
The JAIN APIs are being specified as a community extension to the Java platform. By providing a new level of abstraction and
associated Java interfaces for service creation across circuit switched and packet networks, JAIN is bridging IP and IN protocols to
create an open market.
Parlay
The Parlay Group was formed in 1998 to specify and promote open APIs that "intimately link IT applications with the capabilities of
the communications world". The JAIN Service Provider APIs (SPA) define a full industry standard Java technology realization of the
Parlay APIs. See the Parlay and the JAIN Websites for more information.

Issue 02
422
SIP Overview
Feature description
X Web links
Overviews
aww.stand.bsf.Alcatel.fr/OASIS
www.protocols.com
www.cs.columbia.edu/~hgs/sip
Organizations
www.ietf.org
Others
www.sipcenter.com
www.sipforum.org
http://java.sun.com/products/jain

29

Issue 02
423
SIP Overview
Appendix
X IETF: Internet Engineering Task Force

Team of technical experts in charge of Internet upgrade and
operation
123 Working Groups

2000 participants
X SIP: Session Initiation Protocol

RFC 2543 bis 09 (from IETF)
March 1999
May 2001
Text-based protocol similar to HTTP

Used to initiate interactive communication sessions between
users


Issue 02
424
30
SIP Overview
Appendix
X SAP: Session Announcement Protocol

Used for multicast sessions
X SDP: Session Description Protocol

RFC 2327
February 1998
X RTSP: Real-Time Streaming control Protocol

Ensures the multimedia flow control
A client can send commands to a multimedia server
Rewind, fast forward, pause, etc.
X UAC: User Agent Client

X UAS: User Agent Server

31

Issue 02
425
SIP Overview
Appendix
X URL: Universal Resource Locator

X Proxy: main function of the SIP servers, provides name
resolution and user location
X Registrar: receives registrations according to current user
location
X Forking: the Proxy Servers send several requests in
parallel if an SIP user has several registrations
X Dictionary (in the SIP proxy)
Provides the translation between an SIP URL and a number
Consults the available data in the following order:
Dictionary own data, local phone book, LDAP directories


Issue 02
426
32
SIP Overview
Appendix
X SIP and H.323 define mechanisms for call routing, call

signaling, capabilities exchange, media control, and
supplementary services
SIP is a protocol that offers scalability, flexibility and ease of
implementation when building complex systems
H.323 is a protocol that has been widely used because of its
manageability, reliability and interoperability with PSTN

33

Issue 02
427
SIP Overview
Appendix
SIP
H323
IETF
ITU
Internet Protocols:
Simple and Open
Carrier-class solution
addressing the wide area
WAN solution
Messages are formatted as
text (unicode) :
easy to program and debug
SIP allows for standardsbased extensions to perform
specific functions
Minimal delay - simplified
signaling scheme makes it
faster
Dedicated protocols :
Complex and not open
Focusing on enterprise
conferencing priorities
LAN solution
Binary format (ASN.1) :
not easy to program or
debug
Extensions are added by
using vendor-specific nonstandard elements
Possibilities of delay (up to 7
or 8 seconds!)


Issue 02
428
34
SIP Overview
Appendix
Service
H323v1 H323v2 H323v3
Hold
No
Transfer
No
Forwarding
No
Waiting
No
Conference
Yes
Park
No
Third Party
Control
Call Forking
SIP
Yes
(H450.4)
Yes
(H450.2)
Yes
(H450.9)
Yes
(H450.6)
Yes
Yes
(H450.4)
Yes
(H450.2)
Yes
(H450.9)
Yes
(H450.6)
Yes
Yes
(H450.5)
No
Yes
No
Yes
(H450.5)
No
No
No
No
Yes

Yes
Yes
Yes
Yes
Yes
Yes
35

Issue 02
429
SIP Overview
Appendix


Issue 02
430
36
SIP Overview
Appendix
X H.323 V1
Several TCP connections
Q.931
H.245
Very long latency
X H.323 V2
One TCP connection
Q.931 and H.245 in the same connection
Fast connect
Reduce the latency
X H.323 V3
Possibility to use UDP for signaling
Low latency

37

Issue 02
431
SIP Overview
Appendix
X H.323 Protocols Reminder
H.
3
2
3
E
n
t
i
t
y
System control
H.225
Call
Control
H.245
Control
Data
applications
Telematic
T120
System control
H.225
RAS
Control
RTCP
VIDEO
AUDIO
Codec
Codec
H.261, H.263 G.711, G.723, G.729
RTP
H.225 frame layer
TCP
UDP
IP

38
TCP: information is sent with security. If a packet is lost it will be re-transmitted.

UDP: information is sent without security. If a packet is lost it will not be re-transmitted.
Signaling and Data information use TCP for greater reliability.
Voice and Video use UDP.
The H.323 terminal uses H.225 and H.245 protocols to transmit signaling information which comes from the User module part of the
application. This module is in charge of connection establishment and release. It sends the H.323 application available algorithms
and other needed parameters to set up a connection.
RTP (Real-time Transport Protocol) and RTCP (Real-time Transport Control Protocol) are used to send video and audio data through
UDP because transmission time is shorter and more important than loss of packet.
RTP encapsulates the data with an information header for each packet. This header contains time information and the packet number
(ID).
RTCP checks the RTP packets and sends control packets to provide feedback on data distribution quality. It deletes packets received
twice, puts the frames in the correct order, synchronizes audio video and data, and informs the system about the connection status. It
also provide Quality of Service (QoS) statistics.
An H.323 terminal can be made compatible with few compression algorithms, such as H.261 (>64Kbit/s), H.263 (<64Kbit/s) for
video, and G711 (56,64Kbit/s), G722 (48,56,64Kbit/s), G723 (5,3 and 6,4 Kbit/s), G728 (16 Kbit/s), G729 (8,11 Kbit/s) for audio.

Issue 02
432
SIP Overview
Appendix
X SIP Layers
S
I
P
E
n
t
i
t
y
AUDIO
VIDEO
System control
SIP
SAP
RTSP
SDP
TCP
RSVP
RTCP
RTP
UDP
IP

39
R.T.P.: Real-time Transport Protocol, used to transport information in real time with QOS
R.T.C.P.: Real-time Transport Control Protocol, used to provide QOS statistic reports
SAP can be used for multicast communications.
SIP can be compared to H.225 from H.323 in terms of signaling.
SDP can be compared to H.245 from H.323 in terms of capabilities exchange.
SDP is encapsulated in SIP messages. To transport these messages, TCP or UDP can be used (for instance, in the Alcatel OmniPCX
Enterprise configuration, a choice must be made between TCP and UDP to transport SIP messages).
RTSP can also be transported using TCP or UDP.
RSVP can be used to increase the QoS of the corresponding communication.
RTCP and RTP are used in the same way as H.323 communications (to transport and handle voice or video flows).

Issue 02
433
SIP Overview
Appendix
X Security
SIP messages can contain confidential information
There are 3 mechanisms for protection
Encryption from end to end of the SIP message body and in some of
the header fields
Encryption hop by hop: hackers cannot access caller identification
Encryption of the Via field to mask the request path

Note: the Alcatel OmniPCX Enterprise SIP proxy does not support multicast, encryption

Issue 02
434
40
SIP Overview
Appendix
X Security
There are two registration methods with registrar
Method
Authentication Criteria
No Authentication
None
Digest
User name and password

41

Issue 02
435


Issue 02
436
42
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
437
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
438
Topology examples

OBJECTIVE:
To describe the different possible architectures of the Alcatel OmniPCX Enterprise
Alcatel OmniPCX Enterprise Topology examples

Issue 01
439
Topology Examples
Content
X Introduction
X Examples
X Conclusion


Issue 01
440
Topology Examples
Introduction
X The OmniPCX Enterprise is designed for small to large

businesses


Issue 01
441
Topology Examples
Introduction
X Factors strongly involved in the customer solution choice:

Number of users (50 to 50000?)
Customer network infrastructure (traditional, full IP, or
mixed configuration?)
Topology (branch offices?)
Security/redundancy requirements
Applications needed
e-CS
?
?
?

Whether 50 users or 50,000, specific solutions can be created to cover the entire enterprise market spectrum in an Alcatel OmniPCX
Enterprise network.
The choice of traditional, mixed, or full IP solutions depends on the customer's business objectives, organization, voice-data
convergence projects, and most importantly: expected return-on-investment.

Issue 01
442
Topology Examples
Introduction
X Branch offices solutions:

Remote stations (IP phones)
Remote IP Media Gateway
Remote crystal IP Media Gateway
Branch offices with Call Server
VSBO with OA512

SBO with O-CS
MLBO with e-CS
Voice over IP through the LAN / WAN

Network through leased line

SBO: Small Branch Office

MLBO: Medium and Large Branch Office

Issue 01
443
Topology Examples
Remote Stations: Typically 5 to10 users
X Very small branch offices
IP terminals connection
E-Reflexes
H.323 terminals
4980 IP telephony
Main site
VoIP interoperability for analog

terminals
Full services
Network management
VSBO
e-CS
QoS
IP
WAN
OA512/VSA
4980 IP
telephony
IPMG
H.323
Analog

Centralized communication server:

One central communication server
- Several Media Gateways
- Remote IP users: e-Reflexes, etc.
VSBO: Very Small Branch Office
Benefits:
- Direct IP Phones connection is the cost effective solution
- Communication within Branch office remains local: Phone to phone
- Full access to Central offices services: Greetings, PSTN/ISDN access, teamwork, LCR/ARS, Phone book
- Single management
- Call center
Alcatel OmniAccess 512 OmniPCX Enterprise branch office solution:
The Alcatel OmniAccess 512 is the industry's first integrated LAN switching/WAN routing device offering multi-service access to the
enterprise backbone.
Designed specifically to connect branch offices to corporate data centers, it combines LAN switching, WAN routing, Voice over IP
(VoIP), security and Service Level Management in a single platform.
Uplinks
Alcatel OmniAccess allows you to standardize your branch access switches throughout the enterprise. Alcatel
OmniAccess offers a variety of uplinks (frame relay, PPP, MPPP, T1/E1, FT1, and ISDN BRI) that enable you to
connect lower bandwidth branches over frame relay, and higher bandwidth branches over T1/FT1.
VoIP card
VSD: up to 60 digital channels (T1/E1)
VSA: up to 8 analog channels (FXS/FX0)
Data/voice converged network

Issue 01
444
Topology Examples
Remote Stations: Typically 5 to10 users
X Very small branch offices
IP terminals connection
E-Reflexes
H323 terminals
4980 IP telephony
e-CS
VoIP interoperability for analog

terminals
Full services
Network management
VSBO
Main site
QoS
IP
WAN
OA512/VSA
4980 IP
telephony
IPMG
H323
Analog


Issue 01
445
Topology Examples
Remote IP MG
X Small branch office

Com Server driving a remote IP MG
Connection of all types of terminals
Main site
Full services transparency
e-CS
Network management
QoS
IP
WAN
SBO
OA512/VSA
IPMG
IPMG

Centralized communication server:

One central communication server
- Several Media Gateways
- Remote IP users: e-Reflexes, etc.
Benefits:
- Communication within Branch office remains local: Phone to phone, phone to Media Gateway
- The branch retains its identity: welcome messages, voice guides, night service
- WAN bandwidth is optimized
Local tones and voice guides generation
Local Music-on-Hold
Local conference circuits
Local PSTN/ISDN access (ARS)
Local services to IP phones
- Additional voice communication cost optimization: Break-out feature (PSTN/ISDN)
- Call center
- Installation & maintenance: as easy as IP phones
Easy to install on-site: cabling (uses embedded DHCP server)
Single management: central configuration of local users
- Survivability: backup continuity of the signaling between the main site and remote Media Gateways through the ISDN/PSTN
Notes:
No Com Server required at the remote locations while leveraging the existing infrastructure. The benefits include:
- Cost savings from removing duplication at remote sites single license cost
- Single database coordinates all relevant information into one interface for ease of use
- Simplified remote location deployment
This allows a distributed solution over the WAN to be built for remote sites and over the LAN for a large campus.

Issue 01
446
Topology Examples
Remote IP MG
X Small branch office

Com Server driving a remote IP MG
Connection of all types of terminals
e-CS
Main site
Network management
QoS
Survivability
Signaling backup
IP
WAN
SBO
OA512/VSA
IPMG
IPMG


Issue 01
447
Topology Examples
Remote OmniPCX Office Call Server
X Small BO with o-CS

Main site
VoIP interoperability (H.323)

Autonomy
e-CS
QoS
H.323
SBO
IP
WAN
o-CS
IPMG

O-CS: Office Call Server (Alcatel OmniPCX Office)

This interconnection also permits integration of the "internet services" portfolio (provided through the OXO software) in the OmniPCX
Enterprise topology.

Issue 01
448
10
Topology Examples
Remote OmniPCX Office Call Server
X Small BO with o-CS

VoIP interoperability (H.323)
e-CS
Main site
Autonomy
QoS
H.323
SBO
IP
WAN
o-CS
IPMG

11

Issue 01
449
Topology Examples
Remote OmniPCX Enterprise Call Server
X Large BO with e-CS: LAN environment

Network management
QoS
Autonomy
e-CS
Main site
Node 1
LBO
Node 2
e-CS
IP
ABC link
IPMG
IPMG

Distributed communication server

Several communication servers: several nodes in an ABC network
Each site benefits from full autonomy by being equipped with a dedicated Com Server

Issue 01
450
12
Topology Examples
X Large BO with e-CS: LAN environment

Network management
QoS
Autonomy
e-CS
Main site
Node 1
LBO
Node 2
e-CS
IP
IPMG
ABC link
IPMG

13

Issue 01
451
Topology Examples
X Large BO with e-CS: WAN environment

For low traffic
e-CS
QoS
LBO
Node 2
e-CS
ABC link
IPMG
IP
WAN
IPMG



Issue 01
452
Main site
Node 1
14
Topology Examples
X Large BO with e-CS: WAN environment

For low traffic
e-CS
QoS
Main site
Node 1
LBO
Node 2
e-CS
ABC link
IPMG
IP
WAN
IPMG

15

Issue 01
453
Topology Examples
X Large BO with e-CS using ISDN leased lines
LBO
Node 2
e-CS
ABC link
Main site
Node 1
e-CS
ISDN
LEASED
line
IPMG
IPMG



Issue 01
454
16
Topology Examples
X Large BO with e-CS using ISDN leased lines
LBO
Node 2
e-CS
ABC link
Main site
Node 1
e-CS
ISDN
LEASED
line
IPMG
IPMG

17


Issue 01
455
Topology Examples
OmniPCX 4400 migration for architecture Flexibility
Campus
Branch Office
Peripheral
ACT
Peripheral
ACT
IP
WAN
Branch/Remote Office
Main ACT
Peripheral
ACT
Very small
Branch Office

The migration of the OmniPCX 4400 to OmniPCX Enterprise allows the use of common hardware for small branch offices

Issue 01
456
18
Topology Examples
Legacy based architecture
Campus
Branch Office
IPCS
(CPU5-3/CPU6)
ABC-F2
Link
Branch Office
IP
WAN
Branch Office

19

Issue 01
457
Topology Examples
Overall Spatial Redundancy
Campus
IPAS
(Appliance server)
Branch Office
IP
WAN
Branch Office


Issue 01
458
20
Topology Examples

relevant documents:
Communications\architecture\
Design guide for OmniPCX Enterprise
VoIP for Branch Offices
Virtual Presales Support\Product and release descriptions\

Virtual Presales Support\cross compatibility

21

Issue 01
459
Topology Examples
Conclusion
X There is always a solution to the customer needs

Single site with small, medium or large configuration
Multi-sites with single or multiple system configuration
Single system solution is also called stand-alone
Communication Server
It can be one or several media-gateways but only one

Communication server (or two in case of CPU redundancy)
Multi-system is also called distributed architecture or
networking
This solution is usually more expensive than the single system one
but would be necessarywhen there are strong requirements in
security/redundancy or when the capacity required exceeds ones of a
single system.


Issue 01
460
22
Topology Examples
Conclusion
X The availability of two different types of hardware allows

for any solution
Headquaters with a great number of TDM users: use of
crystal hardware
Need of spatial redundancy: use of IBM Applicance Server
with the crystal central area
Many small branch offices with IP connection available to
the headquater: use of IP-MG (common hardware)
Security is required for the branch offices connection: set-up
the IP-MG signaling backup over the public network (ISDN

or PSTN)
X There is always a solution with the OmniPCX Enterprise!

23

Issue 01
461
Topology Examples
Conclusion
X Whatever the architectural choice, with Alcatel the

customer has the best Reliability and keeps the best OPEX
& level of services which are the key drivers.
X In fact some other competitors are in trouble to propose a
good Branch office reliability without increasing a lot OPEX
(double OPEX because of Branch office manageability) !!
X The OmniVista 4760 provides
One single management platform to manage:
One management for the Communication Servers and the Media

Gateway (MG and CS do not need to be managed, neither
separately nor locally)
One action to modify profile of users belonging to several CS

Cisco:
Inter cluster feature transparency limited to H323
Max 4 call manager over a WAN
Requirements to support Inter Cluster Signaling are unrealistic:
40 ms round trip delay max between sites,
Zero packet loss,
Cisco SRST needs to manage each BO user twice (once centrally & once locally for SRST mode) double OPEX

Issue 01
462
24
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
463
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
464
SNMP Implementation

OBJECTIVE:
To describe the SNMP implementation
Alcatel OmniPCX Enterprise SNMP Implementation

Issue 02
465
SNMP implementation
Content
X Definition
Traps sent from OXE and e-Reflexes to hypervisor
Traps sent from SNMP proxy (4760) to hypervisor

X Examples
X Conclusion

Issue 02
466
SNMP implementation
Definition
X SNMP: Simple Network Management Protocol

The SNMP protocol allows the supervision, the control, and
the modification of the parameters of a network element*

based on the manager/agent model.
Referred to as "simple" because the agent requires minimal
software. Most of the processing power and the data
storage resides on the management system, while a
complementary subset of those functions resides in the
managed system.
X SNMP Model
Agents in charge of supervising an element
One or several managers which are able to interpret data
A MIB describing the managed information

SNMP protocol functions:

- get: allows the station to consult an agent
- get_next: allows the reading of the next object without knowing the name of that object
- set: allows the modification of data
- trap: allows the sending of an alarm
MIB: Management Information Base
SNMP = SNMPv1
SNMPv2 is able to manage operations between management stations. The security is intensified.
*Network elements: routers and access servers, switches and bridges, hubs, computer hosts, or printers,

Issue 02
467
SNMP implementation
Definition
X A typical agent usually:

Implements full SNMP protocol.
Stores and retrieves management data as defined by the
Management Information Base

Can asynchronously signal an event to the manager
Can be a proxy for some non-SNMP manageable network
elements.
X A typical manager usually:

Implemented as a Network Management Station (the NMS)
Also called the Hypervisor
Implements full SNMP Protocol
Query agents
Get responses from agents
Set variables in agents
Acknowledge asynchronous events from agents


Issue 02
468
SNMP implementation
Definition
X Management Information Base (MIB)

collection of information that is organized hierarchically.
MIBs are accessed using a network-management protocol

such as SNMP. They are comprised of managed objects and
are identified by object identifiers.


Issue 02
469
SNMP implementation
Definition
X MIB: Management Information Base

data model associated with SNMP
root
CCITT (0)
ISO (1)
Joint ISO-CCITT (2)
Org (3)
dod (6)
Internet (1)
private (4)
mgmt (2)
MIB (1)
Enterprise (1)
Alcatel (637)
Alcatel MIB:
Object descriptor=1.3.6.1.4.1.637.
Object name= iso.org.dod.Internet.private.enterprise.alcatel
The ASN.1 syntax is used to describe the data

An object identifier (or object ID) uniquely identifies a managed object in the MIB hierarchy. The MIB hierarchy can be depicted as a
tree with a nameless root, the levels of which are assigned by different organizations.
The top-level MIB object IDs belong to different standards organizations, while lower-level object IDs are allocated by associated
organizations.
Vendors can define private branches that include managed objects for their own products. MIBs that have not been standardized
typically are positioned in the experimental branch.
A managed object can be uniquely identified either by the object name or by the equivalent object descriptor.

Issue 02
470
SNMP implementation
Feature description
X In the OmniPCX Enterprise

The Com Server from OmniPCX 4400 R4.2 is an SNMP agent
e-Reflexes are SNMP agents
The Com Server and the e-Reflex can send traps to an hypervisor
SNMP licence required (Actis)
X The OmniVista 4760 can be used as an SNMP proxy
In fact this is the Windows OS of the 4760 server which is the
SNMP agent and Proxy
Use of a pluggin between the 4760 application and Windows OS
Installation by the Professional Services
From the OmniPCX 4400 or OmniPCX Office or 4760 to SNMP
proxy: alarms sent through Alcatel proprietary protocol

CMISE/CMIP
From Proxy to hypervisor: SNMP traps

OS: Operating System

CMIP: Common Management Information Protocol

Issue 02
471
SNMP implementation
Feature description
X SNMP proxy
All hypervisors can be used. However we have advanced
integration with :
CA Unicenter from R2.4 to 3.1 (Computer Associates products)

HP Openview from R6.4 to 7.1
IBM Tivoli R7.1.X

Advanced services offered with tested hypervisors

OmniPCXs & OmniVista 4760 visualisation plus topographic views (with Alcatel icons). But you cannot see the elements behind
the PBX icon.
Display of OmniPCXs & OmniVista alarms in the topographic views.
Alarm message display in the events browser.
Direct access to OmniVista 4760 (web client management) for:
In depth analysis of incidents,
Configuration of PABXs.

Issue 02
472
SNMP implementation
X SNMP is not used to manage the OmniPCX Enterprise or to clear

alarms from the supervisor station
X Security levels with basic SNMP
Authentication
trivial authentication based on plain text community name exchanged in

SNMP messages
authentication is based on the assumption that the message is not tampered
with or interrogated
Authorisation
Once community name is validated then agent or manager checks to see if

sending address is permitted or has the rights for the requested operation
"View" or "Cut" of the objects together with permitted access rights is then
derived for that pair (community name, sending address)
Summary
Not very secure

Extended security is possible with current protocol (example: DES and MD5)
Does not reduce its power for monitoring

Underlying communication protocols

SNMP assumes that the communication path is a connectionless communication subnetwork.In other words, no prearranged
communication path is established prior to the transmission of data. As a result SNMP makes no guarantees about the reliable
delivery of the data.although in practice most messages get through , and those that don't can be retransmitted. The primary
protocols that SNMP implements are the User Datagram Protocol (UDP) and the Internet Protocol (IP).SNMP also requires Data
Link Layer protocols such as Ethernet or TokenRing to implement the communication channel from the managment to the
managed agent.
SNMP's simplicity and connectionless communication also produce a degree of robustness. Neither the manager nor the agent
relies on the other for its operation.Thus, a manager may continue to function even if a remote agent fails. When the agent
resumes functioning , it can send a trap to the manager, notifying it of its change in operational status. The connectionless nature
of SNMP leaves the recovery and error detection up to the NMS(Network Managment Station) and even up to the agent. However
keep in mind that SNMP is actually transport independent (although original design was connectionless transport function, which
corresponds to the UDP protocol) and can be implemented on other transports as well:
TCP (Connected approach)
Direct mapping onto Ethernet MAC level
Encapsulation onto X25 protocol
Encapsulation onto ATM Cell
and so on...

Issue 02
473
SNMP implementation
Examples
X Alcatel OmniPCX Enterprise SNMP Agent

Alcatel OmniPCX Enterprise network
Incidents sent
using SNMP traps
LAN
HP OV
Animated voice topology map

Separate dedicated voice topology map
Alarm notification on voice element icons
Display of alarms according to severity in events browser

About TNG:
Common dedicated voice topology map
Alarm notification on voice element icons using traps
Display of alarms according to severity in events browser
- compatibility with TNG 2.4 on Win NT (TNG Unicenter from Computer Associates)

Issue 02
474
10
SNMP implementation
Examples
X Alcatel OmniVista 4760 SNMP proxy

Aim: Allows the animation of the topology of the network
(Alcatel OmniPCX) within a hypervisor

OXO
Alarms
Alarms
4760 Server
Hypervisor
SNMP
Trap
SNMP
Trap
SNMP Proxy

11
Alarms received by Alcatel OmniVista 4760 from Alcatel OmniPCX Enterprise: CMISE protocol
The SNMP agent responds to the SNMP requests from a hypervisor and sends it the SNMP traps
Example of hypervisor: HP Open View, TNG 2.4, TNG 3.0

Issue 02
475
SNMP implementation
Examples
X Example of advanced service offered with TIVOLI NetView

PBXs visualisation and display alarms.
PBX icons
IPphone alarm


Issue 02
476
12
SNMP implementation
X Alcatel OmniPCX Enterprise SNMP Agent

To get Alcatel
OmniPCX Enterprise
SNMP agent
Software licences
calculation based on
the engine capacity
Following items are calculated

SNMP agent licence

13

Issue 02
477
SNMP implementation
X Alcatel OmniVista 4760 SNMP proxy

License for Professional Services
Cost calculation license: based on quantity of PBX that have to send

SNMP traps.
With a maximum cost calculation up to 11PBXs. After this, the cost

remains the same.
License in Actis
Alarms license in each OmniPCX 4400/Enterprise which is managed

by OmniVista 4760.
Alarms for OmniVista 4760 (on the declaration node)
Software licences
calculation based on
the engine capacity


Issue 02
478
14
SNMP implementation

relevant documents:
Pre Sales presentations\OmniVista 4760 and Management\
4760 and Integration with Standard Management Platforms
System documentation,

15

Issue 02
479
SNMP implementation
Conclusion
X Two possibilities:
OmniPCX Enterprise as SNMP agent
Alarms licence for the OmniPCX Enterprise

SNMP process licence for the OmniPCX Enterprise
or
OmniVista 4760 as SNMP proxy
Alarms licence for the OmniPCX Enterprise

Professional Services for installation
X SNMP is only used for alarms notification on the NMS and

not for management


Issue 02
480
16
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
481
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
482
Data and modem transparency

OBJECTIVE:
To describe the data and modem transparency over IP
Alcatel OmniPCX Enterprise Data and modem transparency

Issue 01
483

Content
X Introduction
Data transparency
Modem/Fax transparency

X Conclusion


Issue 01
484

Introduction
X This Data/Modem transparency feature allows - in a LAN

environment - transmission of data over IP links from
a modem or a Fax Group 3: modem/fax transparency over
IP feature
An ISDN S0 data transmission for Video transmission
purpose or a Group 4 faxes: data transparency over IP
X To establish a data or modem connection over IP the DSP

is switched in transparent mode
This decision is either done by
the
the
CPU (data communication)

DSP (modem case)
X Transparency mode uses the algorithm G711

64 Kb/s rate maximum

Reminder with OmniPCX Enterprise R5.0 Ux & Lx

- Fax Relay is possible between Two Systems
- T38 for FoIP is available for H323 Gateway
- Data, Modem are not available
Faxes Group III: (T30 and V8 compliant): analog Fax machines
V90: an ITU-T standard modem serial line protocol (February 1998) allowing download speeds of up to 56 kbps with upload speeds
of 33.6 kbps. V.90 modems are designed for connections that are digital at one end and have only one digital-to-analogue
conversion
V.92: transmits at the same speed as V.90 but offers a reduced handshake time and an on-hold feature
Fax group 4: fax type S0

Issue 01
485

Introduction
X GA, GD, INTIP are compatible

X To avoid synchronization problems in case of IP MG
without external access the jitter buffer size is increased
X IP Network Constraints
Packet Loss Percentage must be equal to 0
Delay must be inferior to 10 ms

IP Network Constraints
Packet Loss Percentage must be equal to 0
Delay must be inferior to 10 ms
A Jitter buffer (100 ms) is used to compensate for system clock de-synchronization (2H45)

Issue 01
486
Data transparency
Feature description
X Supported data equipments:

Fax group 4 (S0)
Visiophone S0
T0/T2/T1
TA V110, TA V120 are NOT supported
X G711 algorithm is mandatory: IP domains

No VAD
X Direct RTP in network must be activated

X Echo canceller is unvalidated dynamically


Issue 01
487
Data transparency
Feature description
X Data transparency over IP: External communication
Call
Server
LAN
G711
IP MG
Carrier
IP MG
E1/T1
IP Domains
Algorithm: G711
Video conf.
equipment
TA S0
SO bus
Video conf.
equipment

A call is identified as a data call if the call set up message is received from a S0, T0, T1 or T2 Interface with the Bearer Capability
(BC) with the value unrestricted digital information

Issue 01
488
Data transparency
Feature description
X Data transparency over IP: Local communication
Call
Server
LAN
G711
IP MG
IP MG
IP Domains:
Algorithm: G711
TA S0
TA S0
SO bus
SO bus
Video conf.
equipment
Video conf.
equipment


Issue 01
489
Data transparency
Feature description
X Data transparency over IP: network communication
Call
Server
Call
Server
LAN
G711
IP MG
TA S0
SO bus
IP Domains:
Algorithm: G711
Video conf.
equipment
IP MG
TA S0
SO bus
Video conf.
equipment


Issue 01
490
Modem transparency
Feature description
X Supported equipments
Modems
V90 and V92 compliant modems are supported *
Modems and related applications must be configured or
designed to support a minimum round trip delay of 300 ms

=> Some applications may not be compatible with our
implementation or would require tuning
Fax Group 3
X The DSP switches on transparency mode if a carrier is

detected (ANS, ANSam)
X According to the IP domain management the modem
transparency is authorized or not
*With a case by case approach, other modems could be supported. But, at least, they have to use 2100 Hz carrier frequency during
call establishment
ANS: ANSwer tone
ANSAM: ANSwer tone amplitude modulation
ITUT Rec.. V.8: Procedures for starting session of data transmission over the PSTN
ITUT Rec. V.25: Automatic answering equipment and general procedures for automatic calling equipment on PSTN including
procedures for disabling of echo control devices for both manually and automatically established calls
ITUT Rec. T.30: Procedures for document facsimile transmission in the GSTN

Issue 01
491
Modem transparency
Feature description
X G711 algorithm is mandatory: IP domains

No VAD
X The 2 DSP must be in the same node

No modem transparency between call servers because IP
domains are local resources


Issue 01
492
10
Modem transparency
Feature description
X External call on a local Modem
Call
Server
LAN
G711
IP MG
Carrier
Modem
IP MG
E1/T1
IP Domains:
Algorithm: G711
Modem transparency: yes

Modem
11

Issue 01
493
Modem transparency
Feature description
X Local to local Modem
Call
Server
LAN
G711
IP MG
Modem
IP Domains:
Algorithm: G711
Modem transparency: yes


Issue 01
494
IP MG
Modem
12
Modem transparency
Feature description
X Modem communication in network
Call
Server 2
Call
Server 1
LAN
G711
IP MG
Modem
IP MG
Modem

13

Issue 01
495

X There is no specific software license

X Under PCS
X Both Modem and Data Transparency over IP features:
require an almost perfect IP network => LAN/MAN only
Are sensitive to delay (only one packetisation/
depacketisation ) => tests are mandatory


Issue 01
496
14

X In the Alcatel Business Partner Web Site BPWS, under the

Pre Sales section:
Presentations\IP & VoIP\Modem and Data transparency over
IP OXE R5.1.2
Presentations\IP & VoIP\Fax over IP overview and status OXE
R5.1
X Under the sales & marketing section:
Modem and Data transparent over IP Feature description

(8AL020033257DRASA ed2)
X System Documentation
Section Modem and data transparency over IP

15

Issue 01
497

Conclusion
X Data & Modem transparency over IP features are very

sensitive to delay:
Tests must be performed when possible
X The modem/fax transparency is not available in an

homogeneous network using ABC link over IP
X The calls are establish in RTP mode, so the required
bandwidth is the same as for a voice call in G711 mode
(without compression)


Issue 01
498
16
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
499
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
500
Automatic VLAN Assignment

OBJECTIVE:
Describe the automatic VLAN assignment principle
Alcatel OmniPCX Enterprise Automatic VLAN Assignment

Issue 01
501

Content
X Definition
X Interaction with others services
X Reference Documentation
X Conclusion


Issue 01
502

Definition
X When implanting IP telephony, for several reasons it is requested to

put IP phones in different VLANs from PCs.
LAN switch requires that the IP phone uses 802.1q VLAN tagging
to indicate to the switch in which Voice VLAN it is.
The Voice VLAN is depending on the geographic place where the
IP phone is connected. So when moving the Voice VLAN may

change, therefore introducing manually the Voice VLAN through
the IP phone configuration interface is not the solution.
Automatic VLAN Assignment is a service, based on standard
mechanisms, for the IP phone to get its Voice VLAN ID from the
network when OmniPCX Enterprise IP telephone is supported on a
Cisco Networking infrastructure.


Issue 01
503

X Different Flavors of VLANs

Static VLAN
VLAN is assigned to the data port whatever the connected user (e.g.
the default VLAN of the port),
the segmentation of VLANs is done according to topology,
geography, etc.,
Dynamic VLANs
VLAN is assigned depending on the device or the user:
Device oriented: VLAN according to traffic criteria (MAC@, etc.).
User oriented: Authenticated VLAN (Alcatel) and IEEE 802.1X for

enhanced security.
Auxiliary VLAN for voice


Issue 01
504

X The Voice VLAN Strategy

Implementing voice VLANs is recommended in enterprise IP
telephony environment:
Network segmentation data LAN from voice LAN for better

performance and security
Use private IP addressing space for voice:
protection of voice terminals against broadcast storms,

filtering in the router between data and voice subnets,
no waste of precious enterprise's public IP addresses,

no impact on data IP addressing scheme,
protect from direct DoS attacks from internet.
Enforce QoS: priority according to VLAN

This slide highlights the fact that a dedicated voice VLAN is recommended for Qos purposes without cost adding:
use of private IP addressing => do not buy extra IP addresses for IP phones,
Qos according to VLAN is implemented by all data vendors.

Issue 01
505

X The Voice VLAN Strategy

The choice of the number of voice VLANs is an IT
requirement (not an engineering rule !)
Thousands of Alcatel IP phones can be grouped in a single
voice VLAN
IP phones broadcasting is not significant (no Netbios as for PC)
Some points to take into account:
Single voice VLAN: number of MAC address declared in the switch

Multiple voice VLANs: a part of the VoIP traffic has to be routed:
impact on performance of router and therefore on QoS has to be
assessed

This slide highlights pros and cons about the number of voice VLAN to deploy.

Issue 01
506

X VLANs and Move Add and Change (MA&C)

Issue with IP phone MAC in case of multiple voice VLANs
When adding an IP phone, or moving it, it will normally have to

update Voice VLAN and therefore IP address.
802.1q tagging is required from IP phones

To move geographically without requiring VLAN (re)configuration in
LAN switches
Tags are mandatory
for segmentation with native
data VLAN of the PC on IP phone
Up to now, this required changing
manually the VLAN on

e-Reflexes which has negative
impact on the operational costs

In some environments, tagging is mandatory due to the poor level of layer 2 services the switch offers.
The tag (VLANId) must be programmed directly from the Reflexes IP phone. When moving an IP phone from one VLAN to another
one then a management operation has to be done. And this point kills the TCO ! And so is not acceptable.

Issue 01
507

X Alcatel Solution - Auto VLAN Assignment:

When IP Phone / IP Touch starts up, VLAN identification is
learnt from an AVA server (OmniPCX Enterprise)
This VLAN ID is used for 802.1q tagging by the IP Phone/ IP Touch
AVA mechanisms take advantage of standard DHCP
mechanisms
AVA server is able to identify location of requesting IP Phone

Based on this location, AVA server provides the Voice VLAN ID to IP
set, plus (eventually) IP address in the Voice VLAN
Two possible solutions
without customer DHCP server

with customer DHCP server

AVA is based on a double DHCP request using the DHCP server , not only to get the IP address but also the Voice VLAN ID
AVA components:
AVA requires to use the OmniPCX DHCP server to get VLAN ID
IP address allocation can be given by the OmniPCX DHCP server or the customer DHCP server

Issue 01
508

X AVA with OmniPCX Enterprise DHCP Server
Data VLAN #1
Virtual
router
3) IP phone changes VLAN

when using 802.1q tagging
1) DHCP request
( IP phone MAC @ & vendor ID,
IP network of VLAN#1)
2) DHCP reply
(IP network of VLAN #11,
multicast IP @)
Voice VLAN #12
Servers VLAN #99
LAN
802.1q
3 ) 2nd DHCP request

IP network of VLAN #11)
Virtual
router
Data VLAN #2
DHCP
Virtual
router
Virtual
router
Voice VLAN #11
AVA server
4) DHCP reply
(IP @,, tftp server)
802.1q
5) tftp request
Virtual
router

AVA uses the tag mechanism (as defined in IEEE 802.1q standard) to place an IP device in a dedicated VLAN (known as an IP subnetwork). The Communication Server is used to enable the function through the AVA server. In this first release, the AVA server
operates on the same server as the Communication Server.
The first DHCP request retries the voice VLAN number. This request is issued on the default VLAN of the port.
The AVA server answers the request with a VLAN number and an unused IP address (one not used by the IP device). Because some
routers check the validity of the DHCP answer, this unused IP address is used to go through the routers correctly.
The IP phone receives the offer; there is a restart the DHCP request with the new tag. The second DHCP request is run in the voice IP
sub-network in which case the DHCP server can be internal (embedded into the Communication Server) or external.
The DHCP offer delivers the IP address and all the parameters the IP phones requires to boot up correctly.
The TFTP session can now start and the boot up session, as well.

Issue 01
509

X AVA with Customer DHCP Server

802.3
Data VLAN #1
Virtual
router
3) IP phone changes VLAN

when using 802.1q tagging
1) DHCP request
Data VLAN#1 router)
2) DHCP reply
(Voice VLAN ID #11,
multicast IP @)
Servers VLAN #99
LAN
802.1q
Virtual
router
Data VLAN #2
DHCP
Virtual
router
Virtual
router
Voice VLAN #11
AVA server
Voice VLAN #12
3 ) 2nd DHCP request

( IP phone MAC @ & vendor
ID,
Voice VLAN #11 router)
4) DHCP reply
(IP @,, tftp server)
Virtual
router
DHCP server
(MicroSoft)
5) tftp request
802.1q

In this scenario, the two DHCP relay in the routers has to route the DHCP request to the corresponding DHCP server. To be discussed
with the IS manager.
1)1st DHCP request including VLANID quest, emitted on default VLAN #1
2)DHCP reply including VLANID information and a dummy multicast IP address
3)IP phone switching from no tag to 802.1q tagging policy with received VLANID #11
4)2nd DHCP request, no VLANID requested, emitted on Voice VLAN #11
5)DHCP reply including valid IP address for the equipment, next server is a call server
6)TFTP request from IPPhone to the call server to retrieve production parameters

Issue 01
510
10

X Automatic VLAN feature is

Feature is released with R.6.0
Tested and supported with following data equipment list
PC
Windows NT4 Server SP5 and Windows 2000 SP3 as DHCP

servers
Cisco switch 5000 Alcatel OmniCore 5010 (version 3.0.0r22) and
Cisco router 3620 (IOS 12.2.2(T)) used as router and DHCP Relay
Cisco switch 2950
Cisco switch 3550
Cisco switch 3500 XL
Cisco switch 5000
If other data equipment are used by the customer, Proof of
Concept or integration tests have to be performed (contact

Professional Services organization)

11
The AVA uses standard mechanisms but AVA server is mandatory.

AVA requires that the Alcatel DHCP server is updated when there are changes in the data network
( new data subnetwork,..). These information should be coherent with the voice VLANs Ids configured in LAN switches.
AVA can be used only in a campus network and can not be used in branch offices (interworking with backup continuity)
The Alcatel DHCP server manages xxx different VLANs IDs

Issue 01
511

X Compliant with eReflexes and IP Touch phones

X Communication Server duplication
no restriction in terms of database synchronization.
X IP domains are compatible

In this case, manual synchronization of the IP domains
definition and AVA must be performed.
QoS management in IP domains must be disabled when
AVA is used.
X All routers supporting DHCP relay should support AVA

service.


Issue 01
512
12

X Survivability
When a remote site on the WAN uses the IPBSLP feature, the
AVA cannot be used.
The DHCP request containing the AVA request cannot be
passed through since the WAN link is out of service.
A solution to that point is to enable data backup and to
authorize DHCP requests only from the IP devices. All the

other traffic will go through the rescued MG. This is done
through ACL defined in the access equipment.
DHCP request only
PSTN
Rescuable MG
Rescuer MG
64 kb/s data backup
Com.Server
e-CS1
AVA
WAN
AVA request
Remote site

13

Issue 01
513

X No specific license for this feature
X The AVA feature is linked to the Omni PCX enterprise

DHCP server working.
X Related to the fact that AVA principle is to associate a
VLAN Id per IP subnetwork, hence the maximum number
of VLAN ids support by AVA is 200.

Issue 01
514
14

Reference Documentation
In the Alcatel Business Partner Web Site BPWS, under Pre Sales, you can find
further details and links to other relevant documents:
Standard offer, section Distributed Architecture and Networking
Multi-PABX services ABC-F homogeneous private network

Hybrid logical links
Sales &Marketing, Alcatel OmniPCX Enterprise R5.1 - Release
Description
AutoVLAN Assignment Ed03

Automatic VLAN Ed03

15

Issue 01
515

Conclusion
X Automatic VLAN Assignment:

No actual standard today
X Intermediate solutions
CDP from Cisco
CDP is a proprietary protocol from Cisco
AVA from Alcatel using DHCP standard to be independent
from the data infrastructure
X Upcoming standard solution

802.1X
It allows to authenticate a user before granting him access to the

corporate LAN. This authentication can be used for VLAN
assignment

The AVA uses standard mechanisms but AVA server is mandatory.

If your customer requires this feature it is necessary to write a SDP request to your usual Alcatel contact prior to any official proposal.

Issue 01
516
16
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
517
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
518
Alcatel OmniVista 4760 Connectivity

OBJECTIVES:
To describe all the connection possibilities between the OmniVista 4760 server and the OmniPCX Enterprise
To be able to make the 4760 quotation corresponding to the different connection types
To be able to answer to RFP concerning the OmniVista 4760 connections to an OmniPCX Enterprise
Alcatel OmniPCX Enterprise OmniVista 4760 connectivity

Ref. 47600112P06PSUS
Issue 01
519
Alcatel OmniVista 4760 connectivity

Content
X Introduction
Ethernet Connection
IP/X25 Connection
PPP Connection
RMA Connection with PPP

X Conclusion

Issue 01
520

Introduction
X The Alcatel OmniVista 4760 is a suite of applications

running on Microsoft windows which enable the
configuration of the OmniPCX Entreprise, alarms
management
X It is based on a client/server architecture
X The aim of this chapter is to present the connection
possibilities between the 4760 server and the OmniPCX
Enterprise


Issue 01
521

Feature description
X Ethernet connection
OmniPCX Enterprise Network
LAN
Using the
- Call Server Ethernet access
- Slanx daughter board
- Lanx board
LAN
Internet
4760
Server+Client
4760
Client
4760
Web Client
DB
Internet
Explorer

The Alcatel OmniVista 4760 clients connect always on the Alcatel OmniVista 4760 Server which is connected to the Alcatel OmniPCX
Enterprise network

Issue 01
522

Feature description
X IP/X25 Connection
IP/X25 Tunnel
Internal X25 network on ABC link only
Remote access
Call server
Ethernet
4760
server
DB
PRA
Call server
ABC link
D
PRA
IP/X25
Gateway management
IP/X25 management for NMC remote access


Issue 01
523

Feature description
X With IO2/OBCA (crystal hardware) in transit over a B

channel
IO2 or OBCA on extremity node
IO2 mandatory on transit nodes
PRA
PRA
4760
server
IPCS
DB
V24 or
Ethernet
PRA
B
B
IO2/OBCA
IO2
(X25 transit)

IO2 board is mandatory on the transit node (OBCA cannot switch the X25 packets)

Issue 01
524
PRA
B
IO2/
OBCA
IPCS

Feature description
X PPP Connection: Characteristics

Protocol used: PPP (Protocol Point to Point)
Connection with security
Login and password check
Windows server is mandatory

Characteristics
Connection with modem or TA

Connection TA-IO2
Connection through RMA
Connection through e-RMA

The PPP protocol encapsulate the protocol TCP/IP

Issue 01
525

Feature description
X TA-TA PPP Link

Asynchronous option V110 or V120
Local connection
V24
TA
UA
TA
4760
server
UA
DB
V24
Com
Server
HAYES
TA
V24
Remote connection
V24/IP box
TA
UA
4760
server
DB
V24
TA
HAYES
UA
Public
Public
Network
Network
UA
Com
Server
V24
TA
V24
V24/IP box

This configuration needs:

- One CPU port in PPP
- The TA Enterprise is linked on V24 PPP
- The TA PC-NMC, This one must be managed in HAYES mode
The PPP link can be also managed with 2 analogue modems.
Remark:
UA3G TSC V24 doesnt support V120

Issue 01
526

Feature description
X TA-IO2, (OBCA) PPP Link

Asynchronous option V120
IO2/OBCA
IPCS
V24
4760
server
DB
UA
TA
(V120)
V24
4760
server
DB
TA
(V120)
UA
Public
Public
Network
Network
IO2/OBCA

IPCS
This configuration needs:

- TA PC-NMC, this one must be managed in HAYES mode with the norm V120.
- An IO2 or OBCA board (Optimized B channel CPU Access).
Remark:
UA3G TSC V24 doesnt support V120

Issue 01
527

Feature description
X More than 8 remote PCXs connected by PPP

Requires an IP/V24 extension Box (MOXA box : orderable in
Actis)
4760
Server
MOXA
DB
4 V24
Ports
IP

The hardware solution selected by Alcatel is:

The box Nport Server Lite DE.304 provided by the manufacturer, MOXA
Characteristics
4 x V24 ports RS 232
IP link 10/ 100 base T (auto-detection)
possible configuration on the front panel (@ IP, mask, router) via a menu on LCD screen

Issue 01
528
10

Feature description
X RMA Connection with PPP : crystal hardware

Local connection
C
P
U
E0
E1
A0
B0
C
Alcatel
OmniPCX
C
Enterprise
D
A1
P
U
B1
ExA
ExB
4760
server
DB
ExC
ALCATEL
BRMA
BOX
TD RD CD 19 14 96
Public
Network
ON
Remote connection
TD RD CD 19 14 96
ON

11
No alarms reception with RMA

SRMA not supported

Issue 01
529

Feature description
X RMA Connection with PPP : common hardware
IP Media
Gateway
GD
CS
GD
INTIP B
Crystal IP
Media
Gateway
IP Media
Gateway
Local connection
4760
server
Small rack with RMA board

and modem board
DB
Public
Network
TD RD CD 19 14 96
ON
Remote connection
TD RD CD 19 14 96
ON


SRMA not supported

Issue 01
530
12

Feature description
X RMA Connection with PPP : Appliance Server
GD
INTIP B
Appliance Server
Crystal IP
Media
Gateway
IP Media
Gateway
Local connection
4760
server
Small rack with RMA board

and modem board
DB
Public
Network
TD RD CD 19 14 96
ON
Remote connection
TD RD CD 19 14 96
ON

13

SRMA not supported

Issue 01
531

Feature description
X PPP through e-RMA: access + alarms reception (from eRMA)

Call server
e-RMA
IP
Network
Media Gateway
Integrated modem
Media Gateway
Integrated modem
Public or
private
network
4760
server
DB
using Modems
PPP connection

14
Incoming call from remote assistance center

The remote assistance center dials a DDI number which corresponds to the e-RMA application call.
The call server routes the incoming call to a free e-MG modem.
Outgoing call to the remote assistance center
According to some events the e-RMA application is able to call directly the remote assistance center on a predefined number

Issue 01
532

X Actis/Applications/OmniVista 4760
Example
IP/X25
ABC link
Ethernet
PBx 1
4760
server
DB
Public or
private
network
PPP
PBx 2
PBx 3
Actis configuration for node 1

The OmniVista is
ordered in the node 1
offer
Because Node 1
is used as gateway
to reach the node 2
using IP/25

15

Issue 01
533

Example
IP/X25
ABC link
Ethernet
PBx 1
4760
server
DB
Public or
private
network
PPP
PBx 2
PBx 3
Actis configuration for PBx node2


Issue 01
534
16

Example
IP/X25
ABC link
Ethernet
PBx 1
4760
server
DB
Public or
private
network
PPP
PBx 2
PBx 3
Actis configuration for PBx 3

17

Issue 01
535

In the Alcatel Business Partner Web Site (BPWS), under Pre Sales, you can find
further details and links to additional relevant documentation:
Presentations\OmniVista & Management
Presentations\Actis-How to quote series
How to quote Alcatel management tools: IP connectivity case

How to quote Remote Management
System Documentation, section 4760

Others (Feature List and Product Limits under OmniPCX
Enterprise Business User Services, marketing documents, user

guides, .)
Release Note, in eSupport section \Technical
Support\Communication


Issue 01
536
18

Conclusion
X The OmniVista 4760 is a suite of Windows applications

running on a server used for OmniPCX Enterprise
configuration, Alarms supervision, Accounting, traffic
observation and allows centralized management
X This applications require a good bandwidth to be very user
friendly
X This is why whenever possible an IP connection should be
used
other possibilities like IP/X25, PPP or RMA Connection with
PPP are available when IP is not possible
These alternative solutions can also be set up as a backup
of the IP connection

19

Issue 01
537


Issue 01
538
20
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
539
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
540
Alcatel OmniVista 4760 Directory

OBJECTIVES:
To describe the Alcatel OmniVista 4760 LDAP directory server
To be able to make a simple 4760 proposal including quotation
To be able to answer to RFP concerning the OmniVista 4760 Directory
Alcatel OmniPCX Enterprise OmniVista 4760 LDAP directory

Issue 01
541

Content
X Definition
X Conclusion


Issue 01
542

Definition
X Usually, a directory contains information about people

X By extension, a directory can contain all kinds of
information's
Names, addresses, phone numbers (confidential or not)
E-mail, Web site addresses
List of services, meeting rooms
Pictures, technical data
Etc...
X Consequently, Its a particular database format

X LDAP is an universal solution for directory access and
developing compliant applications

LDAP: Lightweight Directory Access Protocol

LDAP is THE directory protocol over TCP/IP.
Basically, LDAP is an access protocol for directory look up. A LDAP directory is a specific database of which the function is to return
one or several attributes of an object using multi criteria search.
LDAP is designed to replace proprietary directories (Novell, Microsoft, PABX, ) by providing a worldwide directory standard.
Directories allow to share database information's on the internal or external network. This type of bases can contain any kind of
information's from people addresses to technical data.
APIs are available to develop client applications.
LDAP (Lightweight Directory Access Protocol) is
The protocol allowing the access to the information stored in the directory,
An information model defining the type of data stored,
A naming model defining how the information is organized and referenced,
A functional model defining how to access to this data,
A security model defining how the data and the access are protected,
A duplication model defining how the information is distributed between servers,
Using LDIF, a data exchange format.

Issue 01
543

Definition
X Client/server organization
A single server can supply several clients
Remote information access through TCP/IP, WEB
X Advantages compared to a classical database (SQL)

One directory is conceived in order to be read
it provides a very fast access to data

it allows several simultaneous consultations
it has a hierarchical structure
X Disadvantages
Average writing performances
updates will be slower


Issue 01
544

Definition
X LDAP Directory server based on Netscape technology (Sun

ONE Directory Server 5.2 )
LDAP V3 compatible
Provides a complete corporate directory
Synchronized
with the OmniPCX Enterprise data base

Dynamic directory administration across distributed architecture
Network Directory : Storage of information used by other
applications
Access by Alcatel and standard LDAP clients

Alcatel
My SoftPhone, Alcatel 4059 Multimedia Console

Microsoft Outlook, Netscape Communicator
Import/Export with external directories (with restrictions)

LDAP : Normalised by the Internet Engineering Task Force. The current version is LDAPV3.
LDAP Import/export with other company directories
Use of LDIF (LDAP Directory Interchange File) for import/export operations
import/export: is done for directories sharing the same schema
import: creation or update of selected attributes
export: creation of text file with selected attributes
LDAP replication of all or part of the directory tree between Alcatel OmniVista 4760
Replication is only supported between Alcatel OmniVista 4760 servers

Issue 01
545

Definition
X LDAP architecture
OmniVista Web
Directory clients
Standard
LDAP clients
Alcatel LDAP clients:

OmniPCX Enterprise
My SoftPhone client
A4059 Multimedia Console
Clients
Lightweight Directory Access Protocol (LDAP)

Servers
Import/Export
Directory Server
Other Company
Directories (with restrictions)


Issue 01
546

Definition
X The OmniVista 4760 server is made of 2 directories

Company directory
Technical (or System) directory
X The Company directory represents the tree structure of one or several
companies
Countries, Cities, Departments, Groups, Persons, rooms,
Personal address book
Consultation by any LDAP client
X The Technical directory contains
Technical information from the OmniPCX Enterprise
Subnet, Node, IP address, ABC links, trunk groups, Attendants, attendant

groups, Boards, users
The 4760 applications (accounting, alarms, ) settings

Access from a 4760 client only

The Alcatel OmniVista 4760 software is based on the Netscape Directory Server (LDAP directory).
In fact, two directories are present in the Alcatel OmniVista 4760:
-Technical directory: always present, accessible only through the Alcatel OmniVista 4760 client, used for internal and technical
reasons (contains information about the Alcatel OmniPCX Enterprise network topology but also some Alcatel OmniVista 4760
configuration parameters).
The technical directory allows:
to manage the link to the PBX
to define data to be collected from PBX
The technical directory is an image of the main Alcatel OmniPCX Enterprise objects: subscribers, trunk groups, entities,
No modification in the technical directory is take in account in the PBX.
Company directory: present only if you buy the Directory application, accessible from any type of LDAP clients, used to describe
the administrative company organization (contains standard objects like Country, Organization, Person).
Company directory creation:
Step 1: Create the organization of the company directory: define countries, localities, ... services levelStep 2: Collect data
from Alcatel OmniPCX Enterprise: synchronize the nodes of the network (technical directory update)
The Company directory also includes : Security levels, password login, and passwords to access the OmniVista 4760 application
system

Issue 01
547

Definition
X Alcatel OmniVista 4760 Company Directory clients:

Alcatel OmniVista 4760 client
Alcatel OmniVista Directory Web client
with Netscape or Internet Explorer
My SoftPhone PC/IP telephony

Alcatel Multimedia Console 4059
Lotus Notes
MS Exchange
Any LDAP client

Remark: LDAP compatibility

- 4980 PC telephony R2.0 minimum
- 4059 4.0.14

Issue 01
548

Feature description
X Company information :
Easy consultation via
intranet with the call by

name function
Updated in real-time
with the OXE network
Communication with
other company
directories thanks to
LDAP standard protocol


Issue 01
549

Feature description
X Easy access via the intranet to the OmniVista 4760 home

page
Directory Access
Network
Management
access (security
login)


Issue 01
550
10

Feature description
X Easy consultation via intranet

11

Issue 01
551

Feature description
X Directory Web client , Multi - criteria search :

Look for :
Person
Group
Room
Place
Country
Company
Department
Criteria :
Surname
First name
Building
Fax number
Floor
Cost centre
Badge number

Issue 01
552
12

Feature description
X Access rights to the Company directory entries

Each directory entry is assigned a confidentiality level
Green: default value, access by everybody (including anonymous

access)
Orange: requires orange, red or Administrator access right (no
anonymous access)
Red entry : requires red or Administrator access right (no anonymous
access)
Administrator: requires Administrator access right

13

Issue 01
553

Feature description

Each person in the directory can be granted an access rights
to the directory: rights to consult/modify the directory

(example : partial view orange list, partial modification)
In that case, when consulting the directory the person must
identified itself by a login and a password
Anonymous consultation gives only access to directory entries with a

Green confidentiality level
Web directory
client
Read only or R/W depends on

Access right
And
confidentiality level of the
directory entry


Issue 01
554
4760 Directory
Server
14

Feature description

Anonymous access (default value)
No authentication (no login + no password)
Rights: only read access of green entries (no red and orange
entries)
Example of attributes masked:
Personal call number

Personal address
Car number
Employed number
Cost center
Password,
Pager
allows establishment of an automatic call using the directory number

and the secret code of the user (if stap* is authorized)

15
*STAP : Simple Telephone Application Protocol

Issue 01
555

Feature description

Access with a login and password
Personal access
Same rights as the anonymous access plus
establishment of an automatic call (if stap is authorized)
No attributes masked about the users entry

Possibility to modify its own attributes
Specific access
Rights according to the login configuration
establishment of an automatic call (if stap is authorized)
ex: 4059, administrator access


Issue 01
556
16

Feature description
X Example : consultation with anonymous login

LDAP client
Search for a person in Brest department gives :

-Guy de Maupassant
-Victor Hugo
Default level (=green)

Confidentiality level : red
Confidentiality level : green
Confidentiality level : orange

Directory Server

17

Issue 01
557

Feature description
X Example : consultation with the login "Emile Zola"

LDAP client
Search gives :
-Guy de Maupassant
-Victor Hugo
-Andr Malraux
-Emile Zola
Default level (=green)

Confidentiality level : green

Directory Server
Acces right : Total view orange list


Issue 01
558
18

Feature description
X Easy consultation via intranet : automatic call by name
Click to e-mail
Click to
dial

19

Issue 01
559

Feature description
X Personal Address Book

Each user can manage its
own address book by the
Web access
He/she must identify itself
(login & password)

The Administrator can see
the names in the list but not

the data assigned (phone
number)
Export to LDIF format is
possible

The Personal Address Book of a person is created during the first login through the WEB directory client (By default: no Personal
Address Book)
Only the directory administrators can see this tree
An directory expert can not see the tree Personal Address Book
Administrator rights
The administrator has access to the personal address book: allows the cleaning, import and export
If the manager delete a person, the personal address book is automatically deleted
If the manager rename a person, the personal address book is automatically renamed
If the manager convert a person to another type, the personal address book is automatically deleted

Issue 01
560
20

Feature description
X Personal Address Book (contd)
Delete entry
Modify entry
Back to List
Add entry

21

Issue 01
561

Feature description
X Directory consultation with the Alcatel 4059 Multimedia

attendant console
To call by name, Alcatel 4059 can consult the OmniVista
4760 directory.
Direct call to the OmniPCX Enterprise phone book + LDAP request to

the 4760 server
Alcatel 4059 pops up the OmniVista 4760 web page while
the OP calls for details
OP accesses to the directory or personal access level.
Incoming call : pop-up of data from the OmniVista 4760 entry


Issue 01
562
22

Feature description
X Personalized web pages

The administrator can tune the look and feel of the Web
directory client
He can also customize the name of the different fields; 50
empty fields can be customized in the entry of a Person
for example, the administrator can add the fields

"Responsibility", "Pin code", "birth date",
Logo
Icons
Filters
Attributes
/ zones
Background
image
Zone
headers
Font size

23
* Professional services assistance may be necessary for advanced personalization

Issue 01
563

Feature description
X Personalization of web pages (list)
Maximum
number of
lines / page
Columns
(Default 12)
Maximum
number of
responses
(Default 250)


Issue 01
564
24

Feature description
X Field Names Customization

The manager can customize all Enterprise directory
fields using a tool :
This customization applies to web directory consultation and

directory administration
Multi languages customization

25
PC application like 4980 that are LDAP compliant use their own field Names when presenting LDAP info retrieved from 4760
Directory Server.

Issue 01
565

Feature description
X Directory: Custom DICT

Dictionary customization allows to modify the translation of
LDAP attribute names (Names that appear in the company

directory)
Company directory
Instead of :
WEB Directory
Instead of :
Accounting Organization
Instead of :

Multi-language customization available

Important: For the other LDAP clients (4059 Attendant, 4980 Multimedia, Internet Explorer via Outlook express, Netscape LDAP URL,
etc.), that are LDAP compliant, use their own field Names when presenting LDAP info retrieved from the 4760 Directory Server.
Other applications that use LDAP functions will not see these customization.
Example: Misc 1 will not be translated

Issue 01
566
26

Feature description
X Print Web client grid

To dispatch regularly an extract of the Company Directory
to the Departments, Companies, Groups,

27
In the print list all the people are presents.

Issue 01
567

Feature description
X Linked fields : manager, assistant

Typically for Attendant
Quick access to the list of people reporting to the same
manager or with the same assistant.


Issue 01
568
28

Feature description
X Automatic fields inheritance

The fields Company, Department, Persons, Groups,
Rooms are automatically filled, but the user can modify

them afterwards
Company
ABS
If the fields were filled, the

automatic inheritance is not
activated.
Fields inheritance for

the entry type:
Brest
France
If the entry moves into the

organisation, the fields are not
automatically updated

The administrator
can modify the
content of each field.
29

Issue 01
569

Feature description
X Conversion of entries from Persons to Companies,

Departments, Groups or Rooms
This action may follow the automatic creation of Persons
(see next) from the OmniPCX Enterprise users *
..
Conversion
...
Company
Service
Group
Room

*also available with the OmniPCX 4400

Issue 01
570
30

Feature description
X Synchronization with the

database*
A directory entry is a
person, a room, a service,

a group ...
Several sets can be

associated to the same entry:
several office, sets, cellular
phone, fax,
Directory updated at each
move, add or change of a

user set in the network
User name and cost center
can be automatically filled

in or updated from the
directory

31
*also available with the OmniPCX 4400

Reminder: in addition to the Company directory the 4760 directory server contains
- Alcatel OmniVista Applications login
- Alcatel OmniVista Applications customization
- Technical directory: Alcatel OmniPCX 4400, OmniPCX Enterprise, OmniPCX Office

Issue 01
571

Feature description
X Directory updates mechanism

Alcatel OmniVista
4760 server

or Web directory client
Real time
Scheduled, real time

or manual
Alcatel
OmniPCX
Enterprise
Plug-in
Synchronization
Update/create
company
directory
technical
directory
Automatic creation possible


Issue 01
572
32

Feature description
X Automatic creation of Persons in the Company Directory

from OmniPCX Enterprise users*
5555
Einstein
Albert
CC_One
Ent_1
Enterprise
directory
5555
Einstein
Albert
CC_One
Ent_1
System
directory
Auto link
5555
Synchronization
PCX/4760
Does enterprise directory entry

exists for this subscriber ?
No

33
*also available wit the OmniPCX Enterprise

Issue 01
573

Feature description
X Create a company entry from the Alcatel OmniPCX

Enterprise data
Client
company
directory
technical
directory
5555
5555
Zidane
Zidane
Zinedine
Zinedine
CC11
CC
Entity
Entity 11
1
Under a specified tree
level or by default under
root.
Synchronization
If no, automatic
creation
Zidane
Zinedine
CC1
Entity 1
Enterprise/4760
Zidane
Zinedine
CC1
Entity 1
Does the company directory

entry exist for this subscriber ?

Manual or automatic user (or other) creation from technical directory (from the Alcatel OmniPCX Enterprise)
Automatic creation of individuals in the company directory:
- During a synchronisation (partial or complete) with the Alcatel OmniPCX Enterprise
- On receipt of a notification of management from the Alcatel OmniPCX Enterprise
A search of entry with the same last name and first name is done automatically in the company directory, to establish a primary link
between both directories
- That search, executed by the directory server, is only done if the name is filled
- That search can fail if the search gives several results: homonym
How does it work ?
The entries can be automatically created under a specified tree level.
This level can be selected by:
Node,
Subnetwork,
Network.
For each item above, the organisation level which is associated to the entries can be defined (by default its the root).
Automatic creation for the following types:
Subscriber,
Subscriber alias,
Abbreviated number,
The entries of these types are created under a

sheet person in the enterprise directory.
Abbreviated number alias,

External user,
Hunting group (the entries of this type are created under a sheet group in the enterprise directory)
The created link is a primary link

Issue 01
574
34

Feature description
X Create a link between the 2 directories
Client
company
directory
technical
directory
5555
5555
Zidane
Zidane
Zinedine
Zinedine
CC11
CC
Entity11
Entity
Synchronization
1
Zidane
Zinedine
Enterprise/4760
Zidane
Zinedine
Automatic link created between the 2 directories

35

Issue 01
575

Feature description
X Updating telephonic data in the company directory
Client
company
directory
5555
5555
technical
directory
Zidane
Zidane
Zinedine
Zinedine
CC11
CC
Updating
5555
Zidane
Zinedine
CC 1
1
5555
Bartez
Fabien
CC 2
5555
5555
1
Bartez
Fabien
Bartez
Fabien
Bartez
Bartez
Fabien
Fabien
CC22
CC
Automatic OmniPCX Enterprise updating


Issue 01
576
36

Feature description
X New entry in the company directory

company
directory
technical
directory
Alcatel OmniPCX
Enterprise
create a person
Alcatel
OmniVista
4760 client
Does the name and first name

exist in the technical directory ?
NO
YES
Creating a new entry without telephonic data link
Creating a new entry with a telephonic data link

(fill in phone number, entity number, CC name)

37
CC: Cost Center

Issue 01
577

Feature description
X Create or update an entry in the company directory

Client
Creating
Updating
company
directory
1
Zidane
Zinedine
technical
directory
Name and first

name arent
present in the
technical directory
Noupdating
updatingof
ofthe
thetechnical
technicaldirectory
directory=>
=>no
noupdating
updatingof
ofthe
theOmniPCX
OmniPCXEnterprise
Enterprise
No


Issue 01
578
38

Feature description
X Cost Center synchronization Principle
5555
Darwin
Charles
CC_One
5555
Darwin
Charles
CC_Two
Client
Updating
Enterprise
directory
System
directory
5555
Darwin
Charles
CC_One
Auto. link
1
1
5555
Darwin 2
Charles
CC_Three
Upgrade CC
Upgrade CC
Event
management

5555
Darwin
Charles
CC_Two
5555
Darwin
Charles
CC_Three
39

Issue 01
579

Feature description
X Directory updating Synthesis

Synchronization
Enterprise/4760
directory
Server
LDAP client
Directory updating
Directory updating
All administrative
data
Other LDAP
directory server
Automatic PABX updating

(entity, CC, name and first name)
Synchronization
server/server
(with restrictions)

Remark:
The company directory is the master directory in case of conflicts with the Alcatel OmniPCX Enterprise.

Issue 01
580
40

Feature description
X LDAP import/export with other directories

a unique solution
a challenge, synchronization in a heterogeneous
environment ...
Databases
OmniPCX Enterprise network
Import administrative info.

Real time synchronization Export telephonic info.
OmniVista 4760
Convergence
LDAP
Import administrative info.

Export telephonic info.
Data directories
@
@
@
E-mail directories

41

Issue 01
581

Feature description
X LDAP import/export with other company directories

Use of LDIF file (LDAP Directory Interchange File)
import/export: can be scheduled for directories sharing the

same schema
import:
export:
creation or update of selected attributes

creation of text file with selected attributes (ASCII)
LDAP replication of all or part of the directory tree but only
between Alcatel OmniVista 4760
Tool box developed by R&D to allow the import/export of
LDIF files with other directories
Associated with the Audit from Alcatel Professional Services


Issue 01
582
42

Feature description
X Import / export LDAP with other directories

Example of the Alcatel 4755
A4755
4760
Directory
converter
Directory
database
export
ASCII
file
Manual FTP file transfer
ASCII
file

LDIF
file
43

Issue 01
583

License generated for the OmniPCX
License generated for the OmniVista


Issue 01
584
44

X In the Alcatel Business Partner Web Site (BPWS), under Pre

Sales, you can find further details and links to additional
relevant documentation:
Presentations\OmniVista & Management
System Documentation, section 4760
Others (Feature List and Product Limits under
OmniPCX Enterprise Business User Services,

marketing documents, user guides, .)
Release Note (for hardware requirement), in eSupport
section \Technical Support\Communication

45

Issue 01
585

Conclusion
X In addition to the applications used for the OmniPCX

Enterprise administration (configuration, alarms, ) the
OmniVista 4760 can provide the customer with a high end
LDAP directory server
Attractive for small and medium business with a all in one
solution
For large business which already have a Directory server
type LDAP import/export can be performed with the

OmniVista 4760 server, the latter having the advantages of
automatic updates with the OmniPCX Enterprise
X LDAP is the standard for directory servers used by all the

actors of the convergence, Unified Messaging systems as
well as email servers and Data servers

Alarms supervision with the Topology option

Accounting with the Tracking option

Issue 01
586
46
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
587
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
588
Alcatel OmniTouch CC Standard Edition

Presales
Networking Solutions

OBJECTIVE:
Describe the networking solutions regarding Contact center

Blind mutual aid
Intelligent mutual aid
Virtual Contact center
Alcatel OmniTouch Contact Center Presales Networking Solutions

Ref. CCD00010P01PSUS
Issue 02
589
Content
X Introduction
X Definition
X Conclusion


Issue 02
590
Introduction
X Needs
Improve accessibility and service level
Use all Enterprise resources
Give access to specialists wherever they are

Provide an alternative to site expansion or move
Avoid social or legal issues
Keep the Enterprise structure
Be prepared to disaster recovery
if one Site fails ...
X Solutions
Co-operation
mutual aid mechanism with a rerouting PG

overflow mechanism used in case of local saturation
Virtual ACD
use of remote PG
Call distribution is done regardless the agents localisation
Centralized call router (external third party application)
pre-routing before call distribution by the local CCd. This router views all sites through
CTI connections and makes call-by-call routing decisions.

PG: Processing Group

Issue 02
591
Definition
X Blind mutual aid
ISDN
Site 1
Site 2
1
2
Call distribution to a rerouting PG

Overflow in queue
Ringing overflow in a PG
Pilot in General Forwarding or blocked
Emergency closure


Issue 02
592
Definition
X Intelligent mutual aid

Same use as blind mutual aid but the nodes are networked
with ABC-F protocol
node 1
node 2
ABC-F link
1
2
Benefits are
The presentation Voice Guide of the pilot is played only once (on node 1)
Displayed information on the remote agent set
Pilot number (node 1 pilot)

Total waiting time of the caller

Voice guides: The destination node is informed about the voice guides already listened in the original node
e.g.: if the greeting guide is already listened in the original node
Then no connection with it in the destination node
Display on agent phone set in the remote node:
name of the pilot called in the original node
Total waiting time since the original node
e.g.: waiting overflow time-out from a queue to a remote pilot
Note:
The call is reject by the remote pilot (pilot 2) when:
Pilot 2 is in GFW (General Forwarding) or blocked
Pilot 2 is open but saturated
No free Time Slot on the ABC link

Issue 02
593
Definition
Distributed mutual aid (also called virtual CCd or CCd in network)

Resources sharing in the OXE network
node 1
node 2
ABC-F link
2
Virtual queue
Call distribution to a remote PG

The call is then routed to a pilot (on the remote node) dedicated to a
virtual waiting queue
The nodes must be of the same version


Issue 02
594
Virtual Contact center: example
PARIS
BREST
Remote PG
Remote PG
Virtual
queue
Virtual
queue
LONDON
Remote PG
Virtual
queue

Call queuing is managed locally so as not to incur additional call costs.

Real time interchange of status information between ACDs over a data link (signaling).

Issue 02
595
Virtual Contact center: Feature description
X Information transfer between CCdistribution sites

permanent signaling
BREST
PARIS
Virtual services
P1
P0
Telephone services
Copies of head queued calls

are present in virtual queue
P0

In a network, the data link is for transferring information between ACD sites.
This data link is supported by the OXE virtual services.
The data link can be the signaling channel of the ABC link or an Ethernet, V.24 or PLL link.

Issue 02
596
P1
Virtual Contact Center: Feature description
X Resource selection is done with local parameters

with different priorities in BREST
P0
P2
P1
Remote PG
P0
P1
Virtual queue
BREST
PARIS


Issue 02
597
X Resource selection with same priorities in BREST

Selection of the resource with the maximum Idle time
LIT ?
P0
P0
P0
Remote PG
in LIT mode
00:05
P1
00:14
00:08
Virtual queue
00:10
BREST
P0
PARIS

To choose the group, the system takes into account the LIT (longest idle time)
For the non-resident PG, you can configure distribution in cyclical mode or based on the longest time ideal.
To calculate the LIT
. in cyclical mode: LIT=current date (at time of calculation) - date of last call handled by this non-resident group.
. in longest time ideal mode: LIT = LIT of an agent in the processing groups serving the local virtual queue on the remote node
In this configuration, you can also set a handicap on the LIT for the agent PGs and non-resident PGs.

Issue 02
598
10
X Call selection
An agent becomes free on the remote node
REMOTE NODE
P0
P1
Busy
Remote PG
30s 42s
Busy
Virtual queue
LOCAL NODE
PARIS
BREST
An agent
becomes free

11
No call selection priority for a non-resident PG; call selection occurs in the remote node.
In the virtual queue, there is one copy of a call for each non-resident PG serving the dedicated pilot.
There is no need for a call selection priority in the remote CCd because the call at the head of the virtual queue is the one with the
maximum waiting time (regardless the originated queue)

Issue 02
599
Networking Solution
X Call selection between virtual and normal queues
REMOTE NODE
P0
Busy
Virtual queue
P1
P0
Busy
LOCAL NODE
BREST
Remote PG
PARIS
An agent
becomes free

Call selection occurs in the remote node for normal queues and virtual queues
No call selection priority for a non-resident PG; call selection occurs in the remote node.
In the virtual queue, there is one copy of a call for each non-resident PG serving the dedicated pilot.
If several non-resident PGs are serving a dedicated pilot in the virtual queue, there will be one call per non-resident PG and the calls
copied will be placed in the virtual queue according to their waiting time.

Issue 02
600
12
X Overflow in queue
Not possible in the virtual queue because the call is
physically queued in the normal waiting queue of the local

node
Overflow to VM after
35 seconds
P0
P0
P1
P0
P1
P1
P0

13
Note: Overflow for the call at the head of a normal queue occurs only if a number is supported and is free, otherwise the call remains
queued.
If the number is a pilot number, the pilot must be in normal state, no overflow even if the blocking or general forwarding rule is used.
Note: ringing overflow in the PG is available in both local and remote nodes

Issue 02
601
Feature description
X Multi-site OmniPCX Enterprise-CCs - Architecture

Consolidated
Consolidated
reports
reports
IP network
0
CCd
OmniPCX Enterprise
64 kb/s required
1
CCd
OmniPCX Enterprise
9
CCd
OmniPCX Enterprise

Once these resources tied together, one need to provide a global view for managing the virtual ACD as well as consolidated
reporting.

Issue 02
602
14
Feature description
X Multi-site CCs - principles

Connection to the different sites at set up
up to 10 sites
Same possibilities as monosite

Configuration and Real time supervision of CCd objects belonging
to any nodes
Wall mounted display control of all sites

Consolidated statistics with CCd objects belonging to different
nodes using
lists of objects
hyper objects*

15
*An hyper object is a group of objects of the same type (pilot for example) which belong to different nodes
They are used for real time supervision and statistics.

Issue 02
603
CTI router
X Pre-call routing used to tie together multiple sites

Centralized view of all sites
call by call routing decision
PSTN
Central
Router
CTI connections
OmniPCX Enterprise
OmniPCX Enterprise

Possibility to integrate a CTI Intelligent Call Router

Added value treatment (business criteria) for a complete Virtual Call Center solution

Issue 02
604
16
X In the Alcatel Business Partner Web Site (BPWS), under the

PreSales section, you can find further details and links to
additional relevant documentation:
Presentations\Alcatel OmniTouch Contact Center
Presentations\Actis-How to quote series
How to quote VoIP agent softphone solutions

How to quote basic CCd/CCs configurations
System Documentation, section CCd

Others (Feature List and Product Limits under
OmniPCX Enterprise Business User Services, marketing

documents, user guides, sales brochures.)
Release Note (for hardware requirement), in eSupport
section \Technical Support\Communication

17

Issue 02
605
Conclusion
X In a multisite configuration several solutions are provided

to optimize the resources:
Co-operation, overflow mechanism used in case of local
saturation
Blind mutual aid

Intelligent mutual aid in case of nodes connected with ABC-F
Virtual ACD, the call distribution is done regardless the
agents localization
Centralized call router (external third party application),
pre-routing before call distribution by the local CCd


Issue 02
606
18
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
607
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
608
Alcatel OmniTouch CC Standard Edition

Presales
Networking Solutions Quotation

OBJECTIVE:
To quote OmniTouch Contact Centre networking solutions
Alcatel OmniTouch Contact Center Presales Networking Solutions Quotation

Issue 02
609

Reminder
X Chose a profile: Easy contact, Starter or Base

X Enter the number of declarable agents
X Enter the number of simultaneously logged-in-agents
X Enter the number of agents with private extension *
X Add the number of physical set (ACD authorized set)
Central area \ voice or Voice over IP (if agents on 4035IP)
X enter the number of CCs monosite needed

Applications\ ACD/ OmniTouch/ACAPI
X enter the number of CCs light needed

Applications\ ACD\ OmniTouch\ACAPI
* agents with private extension different than the ACD authorized set directory number or different than their agent number
(Actis adds the corresponding number of fictive users)

Issue 02
610

Reminder
X Voice guides
Standard or generic voice guides (logon of agents, )
Chose the language(s) (up to 8)
Voice services\call handling services\telephonic voice guides
Customized voice guides for pilot presentation, VG in
waiting queues, agent greetings,
Static VG or dynamic
X Wall boards
In OmniTouch CC\Interfaces\Wallboards
RTI license is needed if need to tune the display
serial links for wallboards if use of a predefined template and V24

access to the OXE

Customized Voice Guides are needed in the following areas

Optional Greeting guide
Up to 6 messages in the Queue (Although some will probably be music)
Specific call loading (e.g.: dissuasion)
Blocked status (e.g. no routes available)
General forwarding (calls outside opened hours)
Agent Greeting guides (up to 5 per agent)
must be dynamic voice guide --> GPA2 or GD/GA boards

Issue 02
611

Parameters specific to network offer
X If needed enter the number of remote multisite CCs that

needs to connect to this local node
OmniTouch CC\ CCA/CCs\ Simultaneous accesses for
multi-site CCs
X Multi-site CCs
This CCs supervise/configure CCd devices declared on
different nodes of an OmniPCX Enterprise Network.
enter the number of CCs multisite needed
Applications\ ACD/ OmniTouch/ACAPI
The Base profile is mandatory in that case

Note: CCs is NOT authorized with the Easy Contact profile

CCs light is authorized only if one CCs monosite (full CCs) is already selected
Standard voice guide: Please enter your agent number when an agent dial the logon prefix or press the dynamic key LogOn (set
type 4035).

Issue 02
612

Example
CCs
Monosite
CCs
monosite
CCs
Multisite
CCsupervision
Monosite
CCsupervision
Monosite
CCs monosite
CCs monosite
CCs multisite
CCs multisite
Simultaneous accesses for

multi-site CCs

multi-site CCs
CCs monosite
CCs multisite

multi-site CCs


Issue 02
613

ACTIS

Add the amount of remote Multi-site CCs that needs to connect to this local node .

Issue 02
614

ACTIS

OmniTouch
CCs Monosite
The monosite CCs is used for the supervision of a CCd forming part of the same node. The link is via Ethernet. The maximum
number of CCs depends on the CCd profile and the PABX version. The CCs software is supplied on CD-ROM.
Enter the number of monosite CCs.
CCs Multisite
The multisite CCs is used to connect various remote CCd via an SO access. The maximum number of CCs depends on the
OmniTouch profile and the PABX version. There is a special licence for the CCs multisite. The licence resides on the main declaration
node but is floating. It can be used to connect to various sites without using other licences. Actis configures one CD-ROM per multisite
CCs.
Enter the number of multisite CCs.
CCs server
This topic is only accessible from PABX version 3.2.
CCs server is software designed to improve traffic between the PABX and several CCs. CCs server is recommended when 9 or more
CCs are used and can be installed on a dedicated PC or on the CCs.
Box checked: the CCs server software is configured.
Box unchecked: the CCs server software is not configured.

Issue 02
615

ACTIS


Issue 02
616
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
617
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
618
Case study networking

OBJECTIVE:
To be able to design and quote a solution with at least two nodes in network
Alcatel OmniPCX Enterprise Case study networking

Issue 01
619
Case Study
Content
X Case study presentation

Customer profile
Site description
Customer requirements
X Questions
X Reference documentation and sizing tools
Note: Correction on a separate document


Issue 01
620
Case Study
Customer profile
X The Worldcompany has a headquater in Boston where the

existing Pabx needs to be changed
X They have a brand new office premises in Chicago
X They are interested in the OmniPCX Enterprise for its
strong network features
X An IP network link between the two sites exists
they would like to use it for data and VoIP
the link is at 100Mbits/s


Issue 01
621
Case Study
X From Boston headquaters ability to centrally manage

(configuration, accounting and alarms) the two
communication systems and features across the network
X They would like to be displayed on a map the two systems
and the ABC link and receive the alarms on this map
X A local administrator in Chicago for basic moves, adds
and changes


Issue 01
622
Case Study
X Boston headquater
200 UA 4020
20 UA 4035
50 Mobile sets, a site survey gives 8 Bases stations required
Voice mail for every one and possibility to retrieve the voice
messages from their email client
5 fax machines
1 attendant on PC and possibility to monitor around 15 sets
3 manager assistant groups
voice guides
ISDN trunk groups to be calculated since the a Contact
Center has just been added in the building (see next for the
Contact Centre requirements)


Issue 01
623
Case Study
X In the Chicago new building no cabling for analog or

digital sets. It is planned to have a solution based on VoIP
70 basic IP phones
10 high end IP phones
10 SIP users (SIP client on PC)
20 mobile sets on the same floor, 5 Bases stations
Voice mail for every one and possibility to retrieve the voice
messages from their email client
2 fax machines
1 attendant on PC
voice guides
2 ISDN trunk groups are required


Issue 01
624
Case Study
X 10 users of Boston should be given the possibility to use

their mobile DECT/PWT set in Chicago
X 2 users of Chicago should be given the possibility to use
their mobile DECT/PWT set in the Boston headquater
X Technical support is housed in Boston and Chicago with
specific requirements (see next)


Issue 01
625
Case Study
X Contact Center requirements in Boston

80 agents total but 40 simultaneous logged in
Use of skills based routing
Use of 4035 sets
2 IP wall boards (required to be able to tune the display)
2 team leaders using CCs and a 4035 set, they can log in a
PG as agent
1 CCs administrator, supervision of Boston and Chicago
nodes
20 minutes of dynamic VG


Issue 01
626
Case Study
X Contact Center requirements in Chicago

15 agents total and all simultaneously logged in
Routing based on priorities
Use of 4035IP sets
1 colour wall board (IP), with tuning capability
1 team leader-> local supervision only and focus on agents
5 minutes dynamic VG
X In case of local saturation on local Contact Centre,

possibility to overflow to a remote pilot thru the ABC link
or thru ISDN


Issue 01
627
Case Study
Questions
X Q1. How many ISDN trunk groups are necessary in

Boston for Contact Centre and business features ?
X Q2. Boston and Chicago are networked with ABC-F link
over IP. How many IP channels are necessary (assuming
that enough ISDN accesses are provided locally on each
site)?
X Q3. Which questions should be asked to the customer to
make sure the quotation is complete?
X Q4. Use Actis for the quotation of both nodes
X Q5. Make two quotations for Chicago: common and
crystal hardware . Which solution is the best?

Issue 01
628
10
Case study
Reference documentation and sizing tools
X Pre-Sales presentations & documents

ACTIS / How to Quote series
How To Quote Alcatel management tools: IP connectivity case

How to Quote Remote Management in OmniPCX Enterprise
How To Quote basic CCd/CCs configurations
OmniPCX Enterprise Design Guide
X Sizing tools
Voice Mail Sizing tool
Erlang Pro
TCS
X Others
Product descriptions
Feature List & Product Limits

11

Issue 01
629


Issue 01
630
12
Alcatel University
Networking
CASE STUDY CORRECTION

1.
Q1. In Boston, how many ISDN trunk groups are necessary for Contact Centre and business
features?
Without any specific input from the customer regarding traffic, our calculation for the number
of ISDN accesses (T2 or T1CCS) needed in Boston, is based on the following assumption:
Regular user traffic: 0,16 Erlang (66% external calls and 34 % local and network calls)
CCd agent traffic: 0.95 Erlang (100% external calls)
Traffic for business users = 0,16*0,66*270= 28,512 E
Traffic for CCd agents = 40 * 0,95 = 38E
Total traffic = 38 + 28,512 = 66, 5 E
With a 1% probability of loss, the Erlang Pro tool gives 82 channels
=> 3 T2 are required (or 4 T1CCS in USA)
Note: the TCS tool could also be used to calculate the traffic generated by the CCd agents (we
can then take into account the possible overflows to remote pilots)
2.
Q2. Boston and Chicago are networked with ABC-F link over IP. How many IP channels are
necessary?
We assume that enough ISDN accesses are provided locally on boston and Chicago.
To simplify we do not take into account:
- the voice mail traffic (usually 0.01E per user)
- the overflow on remote pilot which may occur (CCd requirements)
Other assumptions:
- End User Voice traffic: 0.16 Erlang
Encompasses internal & external traffic
Includes traffic to voice mail, auxiliaries, attendants,
Voice traffic partitioning

- Internal: 34% (.i.e 0.0544 Erlang)
- External: 66% (.i.e 0.1056 Erlang)
N = Number of simultaneous communications between Boston and Chicago on the ABC link.
This input into Actis should be calculated based upon the usual 50% probability rule with a
0.1% loss rate.
Half of the internal traffic is local traffic and half is across the network.
Total traffic = external traffic + internal traffic
Internal traffic = Network Private traffic + local traffic
Issue 01
REF. 222-ENTP0177P01PSUS
CSC.1

631
Alcatel University
Networking
Network Private traffic= 0.0544/2= .0272 (0.0544 has been calculated before, it is 34% of
0.16E)
Traffic=
(.0272 x qty of users in origin x qty of users in destination) / (total users in nw - qty of users in origin)
= (.0272 x 110 x 270) / (270+110-110)

= (.0272 x 110 x 270) / 270
= (.0272 x 110
=2.992 Erlang
With a 0.1%probability of loss, the Erlang Pro tool gives 10 channels
This is to input in Actis in Private network\ VoIP H323 network links for ABC network
3.
Questions to ask to the costumer AND answers from the customer

3.1
Is redundancy required?
in Boston: YES (not in Chicago)
it implies the need of RMA (Remote Maintenance Access) board and so a direct analog
connection to the Public network for the local modem
3.2
For solution using IP media gateway, which power supply solution? 48 V or 220V (110
V for USA)? and which autonomy is requested?
Does the customer provide UPS? YES
3.3
What kind of power supply for the IP phones?

If remote power feeding (802.3af) is required, then: Does the customer have already
switches 802.3af compliant?
If YES, on these switch, how many ports can provide simultaneously power of class 2
(3.84 to 6.49 Watts)?
Are they allowing for manual power level configuration?
-> dont forget that e-reflex IP phones are class 2 devices but do not support optional
Powered Device Classification: Default Powered Device is used instead and even if an
IP phone Requires only 4,2W in conversation state although default power class assigns
15.4W
If NO, propose the PowerDsine patch panels
the customer would like PowerDsine patch panels
3.4
Which compression algorithm? G711, G723 or G729? (G711 is provided by default)

The customer says G729
3.5
Is MLA required?
No license needed but need of fictive users in Actis because the MLA primary number is
usually created on a fictive set.
3.6
Do we need supervision of remote sets with our attendant? (related to network BLF box)
CSC.2
632
Issue 01
Alcatel University
Networking
The customer says YES

3.7
Concerning mobility, outdoor or indoor solution?

The customer says indoor only
3.8
How many simultaneous clients will be accessing the 4760 server?

The customer confirms that it is 2
3.9
What type of email server is used?

Some email servers like the Novel Groupwise are not compliant with the IMAP feature.
The customer says it is Microsoft Exchange
3.10 Agents with a private number? (this is used by Actis for the CPU memory dimensioning)
The customer says YES for private number
3.11 Is interactive queuing required? In this case the IAA is needed or CCivr?
The IAA (or CCivr) is also very used in case of ACR to build the call profiles
3.12 What kind of scripting do you need for ACR? (need of Professional Services or Expert
engineer which has a cost)
3.13 Music on hold provided by an external device (CD player) on analog line or AFU (GD
daughter board)?
3.14 Casual conference or 29 party conferences required? (license needed in this case)
3.15 Which language(s) for voice guides and voice mail?
The customer says voice guides in English and Spanish, voice mail in English only
3.16 Centralized Voice mail or a voice mail on each node?
Advantage and drawback of each solution should be presented to the customer:
centralized voice mail
- advantage: need for hardware only on one node
- drawbacks:
- traffic on the IP network link meaning need for compression resources (cost in
terms of licenses needed and hardware for the VoIP board)
- the voicemail users licenses are mandatory anyway on each node
a voice mail on each node
- advantage: local access to the voice mail so no traffic on the network IP link
- drawbacks:
- cost of hardware on each node
- usually requires the voice mail networking license for transparency (dial by name
across the network)
-> the customer says a voice mail on each node but no voice mail networking
4.
Use Actis for the quotation of Boston and Chicago nodes
Issue 01
CSC.3

633
Alcatel University
Networking
BOSTON quotation in Actis

Central area\Voice
Reflex users: 262
(Business sets: 200 type 4020 and 20 type 4035) + 2 *4035 sets for team leader + 40 set 4035
agents sets)
call by name and mini messaging license: 315 ( 262 reflex sets + 50 DECT/PWT mobile sets + 1
attendant + 2 empty shells)
DECT/PWT configuration
8 IBS base stations and 52 users (50 users and 2 incoming roaming)
outgoing roaming: 10
UTAM, US market only
The UTAM is an official certification organization for the PWT standard, which issues radio frequency
occupancy licenses.
The UTAM licenses (code 801190-00) must be entered manually at the "Additional hardware /
Miscellaneous" window level. The quantity of licenses to declare is equal to the total number of radio
base stations and PWT terminals.
Central area\Private network
Number of nodes in network: 2
VoIP H323 links for ABC network: 10
CCd configuration
OmniTouch UC & CC window tab:
select a base profile because the starter one is limited to 25 agents maximum.
- 82 declarable agent (80 agents and 2 team leaders)
- 42 simultaneous logged-in agents
1 multi-site CCS and 2 CCS light
ACR option with locals calls on OmniTouch (this one is free of charge)
Under CCd/interface, put the 20 minutes of dynamic VG required
1 RTI license is enough for the tuning of 2 wallboards.
For CCd aspect, do not forget to consider that we will have 40/270 = 15 % users with a high traffic
(this is used for CPU load dimensioning and above all for the calculation of compressors needed)
Voice mail configuration
Voice services\voice mail\4635
Select 4635J with 8 simultaneous accesses and 20 hours of storage (see Actis help)
The number of users allowed to use their email client to retrieve their voice messages is 270 (My
messaging subscribers)
More than 100 clients, so IMAP 46x5 must be installed on a dedicated MR1 server.
CSC.4
634
Issue 01
Alcatel University
Networking
4760 configuration
Boston is the declaration node for 4760,
select start pack with topology option
under option tab, put 2 simultaneous client
DO NOT check calculated mode for stand alone
The total number of subscriber is calculated as follow (except attendant):
Boston
Chicago
270 users + 5 fax (business users)
110 users + 2 fax
42 physical 4035 sets + 82 agents ( fictive set)
16 + 16 ( including TL)
empty shells: 2
10
total: 401
154
so the overall total is 555 network subscribers to be declared in 4760
Note: the private number of a CCd agent is not a fictive set (this is used for the CPU memory
dimensioning).
Issue 01
CSC.5

635
Alcatel University
Networking
CHICAGO quotation in Actis

Central area\Voice over IP
IP Touch/e-reflex: 96 (70 4020IP + 10 IP Touch 4068 + 16 4035 IP for CCd agents)
SIP users: 10
DECT/PWT configuration
Central area\Mobility
5 IBS base stations and 30 users (20 users and 10 incoming roaming)
outgoing roaming users: 2
UTAM, US market only
The UTAM is an official certification organization for the PWT standard, which issues radio frequency
occupancy licenses.
The UTAM licenses (code 801190-00) must be entered manually at the "Additional hardware /
Miscellaneous" window level. The quantity of licenses to declare is equal to the total number of radio
base stations and PWT terminals.
Central area\Private network
Number of nodes in network: 2
VoIP H323 links for ABC network: 10
CCd configuration
OmniTouch UC & CC window tab:
select a starter profile because only 16 agents are required and CCS mono-site only
- declarable agents: 16
- simultaneous logged-in agents: 16
ACR option with locals calls on OmniTouch (this one is free of charge)
1 RTI license for the wallboard tuning
Under Central area\Services\greeting guides / DISA, put the 5 minutes of dynamic VG required
For CCd aspect, do not forget to consider that we will have 16/136 = 12 % users with a high traffic
(this is used for CPU load dimensioning and above all for the calculation of compressors needed)
Voice mail configuration
If Common hardware
Voice services\voice mail\4645
4645 infrastructure: on Com server
My messaging subscribers: 110
(The number of users allowed to use their email client to retrieve their voice messages is 110)
Voice services\voice mail\IMAP 46x5 server
Infrastructure: dedicated server (on MR1)
(More than 100 clients, so IMAP 46x5 must be installed on a dedicated MR1 server.
4760 configuration
select the Start pack only
CSC.6
636
Issue 01
Alcatel University
NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
637
NOTES
Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
638

VoIP Network Designer

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

VoIP Network Designer

Diunggah oleh

Hak Cipta:

Format Tersedia

Alcatel Solutions - Presales

This document has no contractual value and may

All rights reserved 2004, Alcatel

indicates that the knowledge provided by the

indicates that the knowledge provided by the

Learning Solutions Catalog 2004 2

indicates that the knowledge provided by the

Pick & Learn

All rights reserved 2004, Alcatel

Learning Solutions Catalog 2004 3