Two or more Call Servers can be connected to create one system where one will act as the Primary Call Server and all Call Servers connected to the Primary Call Server become Secondary Call Servers. This can be via the LAN or via a WAN link.
On power up, by default, each Call Server will use 192.168.0.1 as its IP address and act as a DHCP Server. If this feature is not required because, for example, 192.168.0.1 is already being used and another DHCP Server exists on the network do not connect the new Call Server to the network until this default configuration has been changed as described on page 20.
Linking two Call Servers across a LAN 1 On the Primary Call Server:
a. Open Manager, select Modules and select the Call Server from the list b. You may wish to give the Call Server a unique name to help identify this Call
Server eg Primary Call Server
c. Select the Call Server tab and note the Administration Mode field is set to Primary
2 On the Secondary Call Server:
a. Power up the Secondary Call Server
b. This Call Server must have a unique IP address and be on the same network as the Primary Call Server. Therefore, if necessary, change the IP address of the Call Server as described on page 20. It is recommended that this address be outside the address range given out by the DHCP Server, eg 192.168.0.252 c. You may wish to the rename the Call Server to help identify this Call Server, eg
Secondary Call Server.
d. Power down your Call Server, as described on page 181.
e. Connect the Call Server to the Primary Call Server either via the network or directly to a LAN port on the Primary Call Server.
f. Power up the Call Server
g. Open Manager on the Secondary Call Server, eg http://192.16.0.252/manager h. Open System then Commands
i. Within the Ask Master field change the IP Address to that of the Primary Call Server, eg 192.168.0.1
j. Click on the Ask Master button 3 On the Primary Call Server:
a. In Manager open the Unassigned Modules section of the configuration.
b. Select the new Call Server, eg Secondary Call Server
c. From the Module Status list box select Member and Submit the change d. Return to the Management Information list and select Modules.
e. Select the Secondary Call Server, select the Call Server tab and note that the Administration Mode is set to Secondary.
The Secondary Call Server will now be a part of the system controlled by the Primary Call Server. The Primary Call Server will replicate the relevant configuration information to the Secondary Call Server. This means that the configuration of the system can be administered from either Call Server.
Linking two Call Servers across a WAN link
1 Ensure you are running the same version of software at both ends.
2 On the Primary Call Server:
a. This Call Server must be on different network to Secondary Call Server.
Therefore, if necessary, change the IP address of the Call Server as described on page 20, eg 194.168.0.1. If this Call Server is to act as the DHCP Server change the DHCP properties as described on page 21, eg
Start Address = 194.168.0.2 End Address = 194.168.0.250 Base Address = 194.168.0.0
b. Within Manager, select Modules and select the Call Server from the list c. You may wish to give the Call Server a unique name to help identify this Call
Server eg Primary Call Server
d. Select the Call Server tab and note the Administration Mode field is set to Primary
3 On the Secondary Call Server:
a. Power up the Secondary Call Server
b. This Call Server must be on different network to Primary Call Server.
Therefore, if necessary, change the IP address of the Call Server as described on page 20, eg 192.168.1.1. If this Call Server is to act as the DHCP Server change the DHCP properties as described on page 21, eg
Start Address = 192.168.1.2 End Address = 192.168.1.250 Base Address = 192.168.1.0
c. Within Manager, select Modules and select the Call Server from the list. You may wish to the rename the Call Server to help identify this Call Server, eg Secondary Call Server.
d. Within Manager select WAN Links and select the Secondary Call Server e. Select the default WANLink. (For further details please refer to page 175.) f. Under the IPRoutes tab remove all the existing routes and add an entry to route
back to the Primary Call Server, eg IP Address = 194.168.0.0 IP Mask = 255.255.255.0 Metric = 1
g. Power down your Call Server, as described on page 181.
h. Connect the Call Server to the Primary Call Server via your WAN link.
i. Power up the Call Server.
j. The WAN LEDs on both Call Servers will be solid if a connection has been made. You may wish to ping the Primary Call Server to verify that you can communicate with the Primary, eg ping 194.168.0.1
k. In Manager open System then Commands
l. Within the Ask Master field change the IP Address to that of the Primary Call Server, eg 194.168.0.1
m. Click on the Ask Master button 4 On the Primary Call Server:
a. In Manager open the Unassigned Modules section of the configuration.
b. Select the new Call Server, eg Secondary Call Server
c. From the Module Status list box select Member and Submit the change d. Return to the Management Information list and select Modules.
e. Select the Secondary Call Server, select the Call Server tab and note that the Administration Mode is set to Secondary.
5 On the Secondary Call Server
a. In Manager select the WAN Links section of the configuration b. Select the Secondary Call Server and select WANLink
c. Under the IPRoutes tab note that the default routes have reappeared.
d. Repeat step 3(f) above.
e. You may wish to ping the Primary Call Server to verify that you can communicate with the Primary, eg ping 194.168.0.1
The Secondary Call Server will now be a part of the system controlled by the Primary Call Server. The Primary Call Server will replicate the relevant configuration information to the Secondary Call Server. This means that the configuration of the system can be administered from either Call Server.
Connecting a Phone or Trunk Module to the Secondary Call Server
A Phone or Trunk module can be connected to the Secondary Call Server as described on page 27 and page 31.
The Location field within the Phone or Trunk Module’s configuration form will display the name of the Call Server that the module it is connected to.
When connecting a Phone Module to a Secondary Call Server the additional Users created are all listed under the Users list and have taken the next available extension numbers. Their Initial Phone field displays which port on which Phone Module they are using and their Current Home field, which determines which Call Server is providing their voicemail service, displays the name of the Secondary Call Server.
Connecting a PCS to the Secondary Call Server
A PCS 400, PCS 100 or PCS 50 IP Softphone can be connected to the Secondary Call Server as described from page 41.
The Initial Phone field within the User’s configuration form will display which Call Server the PCS is connected to. Please refer to page 56 for further details.
Select Phones from the Management Information list and then the relevant Call Server to display which PCSs are connected to this Call Server.
Connecting an existing Primary Call Server to another Primary Call Server
Where a Call Server has been previously working as a standalone system and is now to be connected to another system the same method described above is used however the following should be noted:
a. Any configuration (other than the IP address and Call Server Name) previously stored on the Secondary Call Server will be lost as this Call Server becomes a part of the Primary Call Server’s system and takes its configuration from the Primary Call Server.
b. Any Phone and/or Trunk modules and/or PCS 400, 100 and 50 IP Softphones should be disconnected from the Secondary Call Server before it is connected to the Primary