Howto:Master - Slave Numbering Scheme with one Node and more Pbx/Locations

From innovaphone wiki
Revision as of 15:08, 4 July 2007 by Tsr (talk | contribs)
Jump to navigation Jump to search

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.31 or later


More Information

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

Having more innovaphone locations. On every site (location) is an innovaphone

Gateway with Isdn connection (Local Isdn Trunk) and one virtual Pbx over all locations.

That means every number in this location concept is uniqe.

Every Endpoint dials only the number of any phone in any location.

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


Locations 1.png

General Explanation of the numbering node and Pbx

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

Problem Details

IF for every remote location a local isdn breakout is needed –

therefore it takes a little tricky configuration.


Configuration

Configuring the Master Pbx=

Locations 2.png


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 Pbx (pbx name) the phones should register.


Registering/Configuring Endpoints (e.g Phones) on the Master Pbx.

Locations 3.png


User Object

The node: You can have different nodes on one Gateway (Pbx) to have more virtual Pbx.

For example having same extensions.

Also you can have one node per Pbx

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).


Then you have to define the Pbx of the remote Location in the Master


Locations 4.png

Pbx Object

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)


Configuring the slave Pbx

Pbx password

Locations 5.png

The Pbx Password of all the slaves must be the same as on the Master Pbx.


Configuring the Slave Mode

File:Image:Locations 6.png

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 Obejcts of all 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


Configuration/Ldap

File:Image:Locations 7.png

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

Activate write access.


In the Replicator configure the Ldap Master

File:Image:Locations 8.png


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

Locations 9.png


Configuring /Registering a Endpoint (e.g Phone) for the Pbx B

In the Master Pbx open a New User Object

Locations 10.png


Tools clipart.png FIXME: has to be finished