Alcatel OmniPCX Enterprise

ISVPN
NOTE:

Product specifications contained in this document are subject to change

without notice. Products and services described in this document may not be
offered in every country. For the most current information, please contact
your Alcatel representative or your Alcatel equipment provider.

Copyright (c) 2006 Alcatel. All rights reserved for all countries. This
document may not be reproduced in whole or in part without the express
written permission of Alcatel.

Alcatel® and the Alcatel logo are registered trademarks of Alcatel. All other
trademarks are the property of their respective owners.

The CE mark indicates that this product conforms to the following Council
Directives:
- 89/336/CEE (concerning electro-magnetic compatibility)
- 73/23/CEE (concerning electrical safety)
- 1999/5/CE (R&TTE)
   



Chapter 1
Overview

 General ....................................................................................................... 1.1

 Principle ..................................................................................................... 1.1
 Services ..................................................................................................... 1.1
 Related modules ..................................................................................... 1.2

Chapter 2
Detailed description

 Service presentation ............................................................................. 2.1

 General ......................................................................................................... 2.1
 Services ........................................................................................................ 2.1
 ISVPN network topology ............................................................................. 2.1
 Use of DDI .................................................................................................... 2.2
 Protocol ..................................................................................................... 2.2
 Numbering plan ...................................................................................... 2.4
 Services ..................................................................................................... 2.5
 Services for ISVPN subscribers ................................................................. 2.5
 Services for attendants ............................................................................... 2.7
 Inter-operation with ISDN .................................................................... 2.7

Call distribution ...................................................................................... 2.8

 0-1



 Distribution to attendant via an ISVPN call ............................................... 2.8

 Distribution on set via an ISVPN call ......................................................... 2.8

 Distribution after entering conversation ................................................... 2.9
 Charging .................................................................................................... 2.9
 Charging ticket ....................................................................................... 2.10

Chapter 3
Configuration procedure

 General observations ........................................................................... 3.1

 Declaration of an ISVPN node ........................................................... 3.1
 Declaration of an ISVPN subscriber ................................................ 3.1
 Declaring local ISVPN subscribers ............................................................ 3.1
 Declaring remote ISVPN subscribers ........................................................ 3.2

Chapter 4
Configuration examples

 Overview .................................................................................................... 4.1

 Management ............................................................................................. 4.2

0-2 
 

1 

1.1 General
The Integrated Services Virtual Private Network is a private network implementing the ISDN
infrastructure to inter-connect the nodes. It is used to provide a variety of private network type
services without having to lease 2 Mb links (G703) from the public operator. The installation
and operating costs are thus reduced and only depend on the use of the network thereby set
up.
An ISVPN can be made up of OmniPCX Enterprise and of OmniPCX 4400 (R4.2).

1.2 Principle
The ISVPN uses User to User Signalling (UUS1) provided by the ISDN to route ABC protocol
messages and thereby offer a variety of services to ISVPN communications.

Figure 1.1: ISVPN network

1.3 Services
The ISVPN offers a "Center/Satellite" type service over the ISDN.

  
     
    1-1
Chapter 1 

Network services User services ISDN services

(without ISVPN added value)
Homogeneous numbering Display number and name of Call by name,
plan, the calling and caller parties, Advice of charge for ISVPN
Virtual DDI, Optimized transfer and private calls,
Centralised DDI and routing, Enquiry call, broker call,
attendants, processing ISVPN calls as Hold,
Inter-operation with ABC-F internal calls, Conference
networks, Optimized unconditional ...
Optimization of routing on forwarding,
transfer Automatic call-back on free
subscriber

1.4 Related modules

ISVPN is described in the following modules:
- Functional description (see module ISVPN - Detailed description )
- Management (see the module ISVPN - Configuration procedure ),
- Management examples (see module ISVPN - Configuration examples ).

1-2
  
     
   
 

2
  

2.1 Service presentation

2.1.1 General
A call is recognized as an ISVPN call if the establishment message received contains a UUS
information element with a specific protcol discriminator.
ISVPN physical links
The interface connections within the OmniPCX Enterprise are:
- an E1-CCS type interface (Common Channel Signalling, liaison 30 B+D),
- a T1-CCS type interface (Common Channel Signalling, liaison 23 B+D),
- a T0 type interface (liaison 2 B+D).
Call
All the ISVPN specific functions are based on the identification of ISVPN abbreviated numbers.
A subscriber makes an ISVPN call by dialling a prefix (preferably equivalent to the called
party's MCDU) corresponding to a direct ISVPN abbreviated number used to reach the called
party over the ISDN.

2.1.2 Services
On an ISVPN, the subscribers and attendants can implement additional services during a call:
- Dsplay name
- barge-in (enquiry) call/broker call
- Transfer
- Conference
- Forward
- ISVPN call presentation
- Called party status
- Transfer on ringing
- Supervised routing with an ISVPN subscriber.

2.1.3 ISVPN network topology

Two separate topologies exist in the ISVPNs:
- Pure ISVPNs, in which the nodes are only inter-connected over the ISDN. There is no ABC
link
- Mixed ISVPN - ABC networks, where, in part of the network, the nodes are inter connected

 
     
   !" #$% 2-1
Chapter 2 !" #$%

over the ISDN and, in the other part, via private ABC links (see figure below).

Figure 2.1: ISVPN network

2.1.4 Use of DDI

ISVPN users must be reachable through the public network. Thre are two possible cases:
- ISVPN users own DDI accesses, they are directly reached by their DDI numbers,
- ISVPN users do not have DDI accesses, see below.
It is possible to run an ISVPN service on sites that do not run a DDI service, but if they at least
provide a sub-adress service, it is possible to make ISVPN calls.
The ISVPN called party number will be built using and modifying the received ISDN called
party number and sub address (the last three digits from the called party number will be
replaced by the three digits from the sub address).
The level of service will be the same as with DDI.
Note:
- It is possible on the same ISVPN link to use ISVPN with DDI in one direction and without
DDI in the other. It is also possible on the same direction to use both.
- The ISVPN service operational mode (with or without DDI) is exclusively determined by
management.

2.2 Protocol
Since the ISVPN is based on the ISDN, the protocol used on the inter-PCX links is the
standardized D protocol (level 3: Q931/Q932, level 2: Q921, level 1: I430). To provide the
ISVPN services, private messages are exchanged using user to user signalling (UUS)
corresponding to the UUS-1 complementary service. UUS is a standardized complementary

2-2
 
     
   !" #$%
 !" #$%

service used for data exchange between ISDN subscribers during all the communication
phases.

 
     
   !" #$% 2-3
Chapter 2 !" #$%

2.3 Numbering plan

The numbering plan of the ISVPN is homogeneous. Each subscriber is called by the same
numbering sequence from any point in the network. The repertory number of an ISVPN
subscriber is unique within the network and can have up to 8 digits.
The numbering plan within an ISVPN is based on direct abbreviated number prefixes. The
prefixes of the abbreviated numbers managed for the ISVPN refer to the numbers of the public
ISDN subscribers.
Direct abbreviated number prefix
Each ISVPN subscriber section is identified by an incomplete direct abbreviated number prefix.
If an isolated ISVPN subscriber must be declared, a complete direct abbreviated number prefix
is used.
- The direct abbreviated number prefix then corresponds to the ISVPN number of the
subscriber.
- The call number must be completed with the number of the subscriber in the public
network numbering plan.
- The call type must be ISVPN.
In order for an incoming call to the system to find a name associated with the caller number
received via the abbreviated numbers, the trunk group seize used in the abbreviated number
must be the same as the one used in the external call-back translator. All ISVPN abbreviated
numbers must therefore be defined with the ISDN seize prefix used in the external call-back

2-4
 
     
   !" #$%
 !" #$%

translator.
The ISVPN abbreviated numbers used in the CDT numbering command tables must be
complete.

Figure 2.5: ISVPN numbering plan

2.4 Services
The services offered on an ISVPN are divided into two categories:
- services available to ISVPN subscribers
- services available to the attendants.

2.4.1 Services for ISVPN subscribers

2.4.1.1 Display name
The display on the caller set uses the information contained in the messages (alert,
connection) received from the public network.
2.4.1.2 Consultation (enquiry) call / broker call
The ISVPN consultation call has the same behavior as when carried out on external calls,
except that an ISVPN subscriber who has been subject to a consultation call also has the
possibility of carrying out a consultation call as well.
2.4.1.3 Transfer
During transfer, routing is optimized, before and after reply.
To authorize a transfer between an ISVPN subscriber and another equipment, the ISVPN
trunk transfer category is used (instead of the ISVPN subscriber transfer category).
Transfer during conversation

 
     
   !" #$% 2-5
Chapter 2 !" #$%

All transfers during conversation can be carried out by on-hooking. If the transfer is not
authorized (transfer category), the set initiating the transfer will be rung again.
1st call
Local caller External caller ISVPN caller
Local called party Yes Yes Yes
2nd call External called party Yes Yes Yes
ISVPN called party Yes Yes Yes

Transfer on ringing or on busy

Outgoing transfers are not possible.
1st call
Local caller External caller ISVPN caller
Local called party Yes Yes Yes
2nd call External called party No No No
ISVPN called party Yes Yes(*) Yes

(*): on an external incoming call, the attendant can carry out a supervised transfer to an ISVPN
subscriber before the latter replies.
2.4.1.4 Conference
The only restrictions imposed by ISVPN on the conference are the same as those detailed for
transfer in the case of conference controller withdrawal.
2.4.1.5 Barge-in (intrusion)
This service is available to ISVPN subscribers and attendants. It operates in the same way as
in an ABC-F network.
2.4.1.6 Reminder
In order for the service to operate, the call-back numbering must correspond locally to an
ISVPN abbreviated number. The numbering used to carry out the call-back is the one received
in the call establishment message.
Call-back on free set
Indication of call-back on busy set
2.4.1.7 Forwarding
The forwarding service provided in ISVPN is the immediate forwarding service. Time delayed
or on busy forwarding are not available.
To avoid forwarding loops (sets forwarded to each other), the maximum number of forwarding
operations that can be chained is limited to five.
External call on ISVPN forwarded set
ISVPN call on forwarded ISVPN sets
The recording of the forwarding is carried out using the ISVPN abbreviated number. This
avoids any conflict problem concerning the external translator zones but it is essential that the

2-6
 
     
   !" #$%
 !" #$%

ISDN numbering be coherent for the entire ISVPN network.

The initial ISVPN call is released and a second ISVPN call is established with the numbering
received in the ISVPN -UUS.
ISVPN call on a non ISVPN forwarded set
If the called party is forwarded to a non ISVPN number, the call will retain its ISVPN
characteristic and will be connected to the forwarding numbering.
In this case, there is no route optimizing to charge the overcosts, due to forwarding, to the
person who performed the forwarding operation. Route optimization is, in this case, implicit,
since the initial call is released.

2.4.2 Services for attendants

A complete ISVPN number can be used in the distribution tables of the attendants, attendant
groups or entities. This allows the centralized attendant service to be offered at the ISVPN
network level.
2.4.2.1 ISVPN call presentation
An incoming ISVPN call is presented as a local call with the information received in the
establishment message regardless of the type of called party. In the case of an ISDN-ISVPN
transit, the call is presented as an external call.
2.4.2.2 Called party status
When the attendant calls an ISVPN subscriber, he receives an indication of the status of this
subscriber:
- Rung: if the ISVPN called party can take this call (free set, multi-line set partially busy)
- Busy: if the ISVPN call cannot be presented. In this case the call is released.
- Forwarded: if the ISVPN called party is forwarded. In this case, the forwarding is
systematically followed.
2.4.2.3 Transfer on ringing
An attendant can carry out an optimized transfer (with rerouting) between an external incoming
call and an ISVPN subscriber before the latter answers.
2.4.2.4 Supervised routing with an ISVPN subscriber
Following the transfer on ringing, the attendant can carry out a return to call from hold as long
as the ISVPN subscriber has not answered this call.

2.5 Inter-operation with ISDN

There is an inter-operation between the ISDN and ISVPN when:
- an ISVPN subscriber performs an outgoing call to the public network (ISDN).
- an ISVPN subscriber receives an incoming call from the public network (ISDN).
In these operating cases, most of the standardized complementary services provided by the
ISDN are operational across the ISVPN.

 
     
   !" #$% 2-7
Chapter 2 !" #$%

ISDN services Inter-operation Comments

ISDN/ISVPN
Advice of charge (AOC) No On an outgoing call that transits via
the ISVPN, the charge units are not
re-transmitted over the ISVPN
Calling Line Identification Yes
Presentation (CLIP)
Non identification of the caller Yes
(CLIR)
Called party identification (COLP) Yes
Called party non-identification Yes
(COLR)
Call Waiting (CW) Yes
Malicious call identification No The MCID request is made on the
(MCID) ISVPN call and not on the ISDN call
Direct dial inwards (DDI) Yes
Sub address (SUB) Yes
Mini message (UUS) Yes/No Yes, because the UUS received in
an ISDN call will de retransmitted on
ISVPN,
No because, due to a lack of space,
the two functions cannot be used
simultaneously.

2.6 Call distribution

2.6.1 Distribution to attendant via an ISVPN call

The attendants are called either by direct call or following overflow.
For the direct calls, the attendants are reached by prefix:
- individual attendant
- attendant group
- entity call
- attendant general call.
The ISVPN calling party dials an abbreviated number corresponding to the DDI number of one
of these call prefixes. Therefore, the call prefixes must be managed on the node receiving the
call. The distribution tables used are therefore those of the node receiving the call.
The internal ISVPN calls are presented (queue, guide, etc.) to the attendant as local calls.

2.6.2 Distribution on set via an ISVPN call

Incoming calls to sets follow the general distribution mechanisms for external calls. Therefore,
on arrival on a busy set or on no answer, the following actions will be taken:

2-8
 
     
   !" #$%
 !" #$%

Caller External ISVPN set ISVPN

ISVPN attendant
Wait Yes Yes Yes
Overflow to associate (same node) Yes Yes Yes
Forward (immediate or time delayed*) Yes Yes Yes
Overflow to attendant Yes No No
Overflow or forwarding to voice mail (same Yes Yes Yes
node)
Pre-"off-hook" guide Yes No No
Automated
Menu guide Yes Yes Yes
Attendant
Automated attendant Yes No No

Note:
- (*): for time delayed forwarding, the forwarded set and the destination set must be on the
same node.
- ISVPN camp-on on busy set (by set or by attendants) is automatic.
- Forwarding is always followed even if the ISVPN caller is an attendant.
- For the automated attendant, the category used for the combined rights (rights used to
determine the authorised guides output: Voice Mail, Wait, automated attendant, attendant)
is the category of the trunk group that received the ISVPN call and not the category of the
trunk group that received the external call.

2.6.3 Distribution after entering conversation

In the case of re distribution of an ISVPN call, after entering conversation (no retrieval from call
park, transfer on call ringing, etc.), distribution is carried out on the final ISVPN node.

2.7 Charging
On ISVPN calls, although presented as local calls, the real-time communication cost is
supplied at the calling end.

 
     
   !" #$% 2-9
Chapter 2 !" #$%

Figure 2.6: ISVPN charging

For detailed information on the integrated charging application: see module Internal accounting
- Overview .

2.8 Charging ticket

The charging ticket is printed in real-time by the integrated charging application and has the
following format:

To recognize a call using the ISVPN, analyze the Network Service attribute. This attribute is
used to know the network services used during the call. It comprises six fields:
Field V S A T M R
Meaning VPN ARS Abbrev. Charge unit Mini Messaging Forwarding
Value I : ISVPN S :ARS C: central D: during M : mini mess. B : busy
V: VPN I: E : end R : no reply
individual S : start U: incondit.
Note If the service is not used for the call, the corresponding field is left blank.

Therefore, if the call is ISVPN type, the V field in the network service attribute will contain the
letter I.

2-10
 
     
   !" #$%
 

3  

3.1 General observations

The management of an ISVPN includes the following actions:
- declaration of ISVPN nodes
- declaration of ISVPN subscribers.

3.2 Declaration of an ISVPN node

In the ISVPN, each PABX is marked by a node number. This number can be parametered by
the administrator. By default, it is equal to the node number in the ABC network.
Object name: System > Other System Param.
Attribute:
ISVPN Node No. : Enter the number of the node in the ISVPN. By default, it is
equal to the node number in the ABC network.

3.3 Declaration of an ISVPN subscriber

3.3.1 Declaring local ISVPN subscribers

There is no specific right to configure in order for a subscriber to be able to use ISVPN;
however:
- in order to be able to send an ISVPN call, subscribers must have in their collection
categories the right to make external calls,
- in order to be able to receive ISVPN calls, the subscriber must have direct dial inwards
(DDI) authorisation. In certain configurations, it is possible for a subscriber to have several
DDI numbers.

  
     
   &$%'("$% $ ( 3-1
Chapter 3 &$%'("$% $ (

Figure 3.1: DDI numbering

3.3.2 Declaring remote ISVPN subscribers

All the remote subscribers who can be reached via the ISVPN must be declared on the node,
using the complete or incomplete direct abbreviated numbers.
Object name: Abbreviated Numbering > Direct Abbrev. Numbers > Direct Abbrev. No
Pref.
Attributes:
Direct Abbr. No Prefix : Enter the number of the subscriber in the ISVPN
numbering plan
Call Number : Depending on the availability of DDI numbers:
- DDI mode
Enter the public trunk group seize prefix followed
by the subscriber number (complete or
incomplete) in the public network numbering
plan. Public trunk group seize prefix + subscriber
DDI number
- non DDI mode
Enter the public trunk group seize prefix followed
by the complete subscriber number followed by
"*" followed by the sub address (at least three
digits).
Directory name : Enter the name of the subscriber. This name is
displayed on the set and can be substituted for the
display of the data received from the remote end.
Directory First Name : Enter the first name of the subscriber
Barring : False.
Overfl. Dir. Abbrev. No Pref. : -1
Auto. Attendant Calling Right : 0
Call Type : ISVPN.
Timed Forward. Dir. Abbrev. No : -1
Range Number : 255

3-2
  
     
   &$%'("$% $ (
 &$%'("$% $ (

Note:
- All the ISVPN abbreviated numbers must be defined with the ISDN seize prefix used in the
external call-back translator. In fact, so that - on an incoming call - the name associated with the
calling number received via the abbreviated numbers can be retrieved, the trunk group seize used in
the abbreviated number must be the same as the one defined in the external call-back translator.
- The ISVPN abbreviated numbers used in the numbering command tables must be complete.

  
     
   &$%'("$% $ ( 3-3
Chapter 3 &$%'("$% $ (

3-4
  
     
   &$%'("$% $ (
 

4   

4.1 Overview
The example below illustrates the case of a company with four sites:
- 1central site implementing a centralized DDI
- 3 agencies (local sites).

Figure 4.1: ISVPN network

The ISVPN network described in this example includes four nodes linked to the public network
by T2 links. Two of the nodes (node 1 and node 2) are inter-connected by an ABC logical link
and therefore form an ABC network.
The numbering plan in the network (ISVPN) is homogeneous and uses 4 digits. The network
uses centralized DDI. Seen from the public network subscriber view point (external to the
ISVPN network), the number of an ISVPN subscriber will have the following form:
014785XXXX.
Directory numbers Centralized DDI Local DDI
numbering numbering
Node 1 :1000 subscribers 5000 0147855000
- -
5999 0147855999
Node 2: 400 subscribers 6000 0147856000 0143225000
- - -
6399 0147856399 0143225399

  
     
   &$%'("$% "
# 4-1
Chapter 4 &$%'("$% "
#

Node 3: 20 subscribers 7000 0147857000 0139123300

- - -
7019 0147857019 0139123319
Node 4:10 subscribers 7100 0147857100 0139253400
- - -
7109 0147857109 0139253409

Note 1: on node 1, it is assumed that DDI numbers divided into different thousands have been obtained.

Note 2: to define the subscriber directory numbers corresponding to the centralized DDI numbers, you
must choose the directory numbers in the central node DDI sections. This imposes on the other nodes
(agency nodes) the use of DDI transcoding to adapt the directory number to the local DDI number
(unless the central node can unite all the agency node DDI ranges). In addition, there are only 32 DDI
sections per node.

4.2 Management
Rows: to take the node into account.
Columns: Management to carry out on the Node.
Node 1 Node 2 Node 3 Node 4
Node 1 Direct abbrev. num. 70 71
pref.
Call Number 01391233 01392534
Call Type ISVPN ISVPN
Node 2 No management to carry out, the abbreviated numbers are distributed, the
ABC network nodes benefit from the management of node 1.
Node 3 Direct abbrev. num. 5 6 71
pref.
Call Number 0147855 0143225 01392534
Call Type ISVPN ISVPN ISVPN
Node 4 Direct abbrev. num. 5 6 70
pref.
Call Number 0147855 0143225 01392534
Call Type ISVPN. ISVPN ISVPN

4-2
  
     
   &$%'("$% "
#