Howto:Master - Slave numbering node with X nodes and X pbx

From innovaphone wiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

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

Applies To

This information applies to

  • IP 6000, V6
  • IP 3000, V6
  • IP 800, V6
  • IP 305, V6
  • IP 302, V6
  • IP 202, V6

Build 06-60400.87 or later

More Information

General explanation of the node and pbx – numbering node schema (formerly known as locations concept)

Go to Howto:Description of the Numbering Scheme used in V6

The scenario and configuration way described here

Having more innovaphone locations. On every site (location) is an innovaphone gateway with ISDN connection (local ISDN trunk) and more nodes over all locations. That means it is possible to have same phone extensions over different nodes. Every endpoint dials only the extension in-between the own node- if its to reach another node the prefix of this node has to be dialed too.

Also every endpoint dials the trunk line number (e.g 0) and gets a local break out.

x Nodes and x PBX

System Requirements

At least 2 innovaphone gateways with activated pbx (basic lic on every gateway and pbx lic only on every gateway). Also ISDN and DSP lics for the ISDN local breakout and innovaphone Phones/Endpoints J

Configuration

Configuring the master pbx

Configuring the Master PBX

Pbx mode master

System name is the Gatekeeper Id (AT01)

And the pbx name (A).

Here you define the pbx name , later in the user objects you configure on what physical pbx (pbx name) the phones should register.


Configuring the node with prefix

Configuring the node with prefix

Long name /name – define the name of this node/location, and the number 100 here is the prefix for this node/location.


Configuring/Registering endpoints on the master pbx

Configuring endpoints on the master pbx

The node: The endpoint is in node A therefore choose the node Anode

The node root is the upper tree node, all other nodes are below the root node – this are all own virtual pbx. So if in a node a number is not found it will go to the upper node. On the pbx field you define on what pbx the phones register, here it is the local pbx (A).

When registering an endpoint to Anode you have to put the prefix also in the registration on the phone. So in this case you have to configure in the phone the number 100101.

Then you have to define the pbx of the remote node (location) at the master.

Configuring the remote node

The name and long name is the same as the pbx name on the remote location.

Node is the root and the pbx is the master pbx (A), Password is not needed, if you take a password then you have to configure this in the slave pbx also.

(andminstration/pbx/general slave pbx password)

The number here is 200 ,so the prefix for node B is 200


Trunk user for node A

Configuring trunk user A

The trunk user must be also in the Anode

As the phones in the A node dialing the 0 they get dropped out via this trunk object.


Configuring the slave Pbx

Pbx password

Configuring the PBX Password

The Pbx password of all the slaves must be the same as on the master pbx


Configuring the slave mode

Configuring the PBX slave mode

Pbx mode is slave,.

System name (Gatekeeper ID) is the same as on the master

Slave pbx, master: Here put the IP address of the master pbx

Having an alternate master (Standby pbx put here the IP address of the masters standby pbx)

Password : If you configured a password on the pbx object in the master pbx then put the same here.


Configuring Ldap

All the user objects of all nodes (locations) get configured in the master pbx (A)

The remote locations (slaves) get this user objects automatically in their pbx – therefore we work with LDAP replication.

Configure the LDAP replication on a slave pbx

Configuring LDAP Replication on a slave

The default Ldap user is ldap-guest and the password is ipxxx

Activate write access.


In the replicator configure the Ldap master

Configuring LDAP Replication on a slave

Server : IP address of the master pbx

Location: if it is empty all user data from the master pbx will be replicated.

Here you only need the user data of this slave pbx (B) - own user data.

User and password as above.


To see if the Ldap replication works go to replicator status

Full replication must be UP

Replication status


Configuring /Registering an endpoint for the pbx B and node B

In the master pbx open a new user object

Configuring Endpoints for pbx and node B


Node root and pbx B (the pbx of the remote ocation – slave pbx where the phone should register)

This user must now be replicated to the slave pbx.

Also you see we use the same phone extension for the endpoint in the salve as in the master.


Trunk User for node B

Here you define the same trunk user as in the master,only that this trunk user is in another node.

Configuring trunk user B


In the end you should see something like this on the master

Configuring PBX Objects on master


And on the slave

Configuring PBX Objects on slave


For registering the local trunk object to an Isdn interface -here an example - master pbx connected direct with Isdn interface (routes between interface and trunk object is then configured automaticly - see the RX routes in the routing table)


Gatekeeper address - take the own IP address, and in the name configure the long name from the trunk objet in the local pbx ,and no number.

Configuring the trunk object


You should now be able to dial with 0 the local trunk object ,in between the node without prefix and with the prefix + extension the remote node/location endpoint

Related Articles

Howto:How to configure a Numbering Scheme with one Node and more Pbx/Locations

Reference:PBX Locations

Howto:Description of the Numbering Scheme used in V6