Howto:How to configure an e164 Numbering Scheme with x Nodes on one PBX with one Breakout

From innovaphone wiki
Revision as of 11:33, 2 June 2009 by Afi (talk | contribs) (→‎Configuring Customer Objects and Media Gateways)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Applies To

This information applies to

  • V6 SR2 PBX

Build 08-60900.32 or later.


More Information

This application scenario suppose every customer site is an innovaphone ISDN Gateway providing ISDN PRI or BRI Trunk for Customer.

On other side are Gateways providing breakout to global PSTN network shared between all customers.

The call routing is made by innovaphone PBX containing e164 node tree with appropriate placed Gateways for each customer.

E164 Node Konzept one Breakout.png


For general explanation of the numbering node and PBX please read the description of the Numbering Scheme used in V6.


Configuration

Configuring the PBX

At first create an e164 node tree for all appropriate customer numbers:

GSTW Node Konzept 02.png


Node for Austria will look like this:

GSTW Node Konzept 03.png


Node for Salzburg in Austria:

GSTW Node Konzept 04.png


Define a Gateway Object used for breakout to PSTN network. On this object you will register all ISDN interfaces to PSTN. Place this objects long name under PBX General Config. "Route Root-Node External Calls to". All calls made to numbers not found in the PBX will go to this object.

GSTW Node Konzept 01.png


Configuring Gateway Objects for Customer Side

Gateway Objects are defined with subscriber number, placed in appropriate node:

GSTW Node Konzept 05.png


Configuring Customer Objects and Media Gateways

The CDPN of the calls incoming to PBX have to be set to international format like 00497031730090. The CGPN must set depending of the type of the trunk (PtP or PtMP) to the extension or to the subscriber number.

Point-to-Multipoint ISDN

The PBX Object type for an MSN is a User Object. Each MSN is defined as a User Object in the appropriate node. Than you can register an ISDN interface to this user object.

In case you want to provide more then one MSN to a single ISDN interface, a GW must be registered with multiple aliases to the user objects. Use full international number to register an alias:

How to configure an e164 Numbering Scheme MSN registration.png


Additionally routes from GW1 to TEL/BRI interface must be created:

How to configure an e164 Numbering Scheme MSN route.png


Number mappings are performed on the particular ISDN interface at customer side.

For the incoming calls from customer CGPN-In is used for validation check of the number sent by the customer:

4455661→4455661    //detect valid MSNs for the customer
7755666→7755666
3322888→3322888
!→4455661          //set default MSN 4455661 if no, or wrong provided by the customer


The CDPN-In must be converted from international, national or subscriber format into normalized number:

i→00   //e.g. map from i497031730090 to 00497031730090
n→0    //e.g. map from n7031730090 to 07031730090
s→     //e.g. map from s730090 to 730090

Numbers sent to the customer are, depending on the destination, sent in international or national format. Use following CGPN-Out mapping for this:

00→i
0→n

On Point-to-Multipoint trunks MSN in subscriber format is used as a called number sent to the customer. Following CDPN-Out is used for this:

→s     //Subscriber ISDN flag is added to MSN number 


Point-to-Point ISDN

For a Point-to-Point a Trunk Object should be used, so you can register more than one ISDN interface on it and round robin the calls over the multiple ISDN interfaces. The trunk number(e.g. 73009) is configured as a number of Trunk Object.

Since the number format sent by a customer may vary you can catch all of possible variations by the following (a little bit paranoid, but robust) CGPN-In maps:

i49703173009→      //detect international, national and local mapped numbers
n703173009→
s73009→
u0049703173009→    //detect unknown mapped numbers
u0703173009→
u73009→
u→
!→0                //replace with 0 if no above maps are passed
                   //(no or wrong number is sent by the customer)


The CDPN-In and CGPN-Out mappings are the same as on Point-to-Multipoint trunk.


The CDPN-Out is prefixed with the trunk number and subscriber flag:

→s73009

Redundancy

Standby PBX can be used as usual.


Howto:How to configure numbering node with X nodes and X pbx.

Reference:PBX Locations

Howto:Description of the Numbering Scheme used in V6