This process adds the secondary server to the primary server’s network. For a new server it also takes the server through its initial configuration.
If required you can separate the two processes. Do that by first logging in to the new server's IP address and completing its initial configuration. Then log in to the primary server's address and add the new server.
Connect to the primary IP Office server using IP Office Web Manager. See Starting Web Manager.
Click Solution.
Select Configure > Add System to Solution.
Select Secondary server.
Enter the IP address set during the server ignition. Otherwise click on Discovery Preferences and configure the range of addresses to search.
Click Discover.
From the list of discovered IP Office servers, select the required IP Office server and click Next.
If prompted, select the primary IP Office server IP address to link and click OK.
For a newly ignited IP Office server, the initial configuration menu server is displayed.
In the System Mode, select one of the following:
System Mode
Description
Server Edition
Select this option for a primary server that will use a PLDS file for licensing.
Server Edition - Select
Select this option for a primary server that will use a PLDS file for licensing that includes Select licenses. Note that if in a network, all servers in the network requires a Select license.
Server Edition - Subscription
Select this option for a primary server that will use subscriptions for licensing.
Set a unique System Name for the system. This will appear in other administration menus and helps identify the particular server.
If applicable, enter the Services Device ID issued for support of the server.
Set the Locale to match the customer location. Set this accurately as it affects a number of default telephony settings that the system will then use.
Set and confirm the Default Extension Password. This is used to set the extension password required to register IP extension unless a separate specific password is configured in the extension’s own settings.
Using the Public LAN Interface control:
Select LAN1 and check that the IP Address and IP Mask match the network settings that the server should use for its eth0 port.
Select which DHCP Mode the server should support on the LAN.
Option
Description
Server
The server will act as a DHCP server for the network on that interface. For its own address it will use the IP Address details entered in this menu.
Client
The server will obtain its IP address settings automatically from a DHCP server elsewhere on the network.
Dial In
This DHCP mode is not supported on Linux-based IP Office servers.
Disabled
The server will use the fixed IP address details entered in this menu.
Select LAN2 and check that the IP Address and IP Mask settings match the network settings that the server should use for its eth1 port.
Set the Gateway address for the customer network.
Having set and checked the IP address and DHCP details, select which port, LAN1 or LAN2, will be used for outgoing connections from the customer network for general internet access. This choice adds a default IP route from that LAN to the specified Gateway address.
Check that Server Edition Primary is set to the IP address of the primary server.
If the customer network has a specific DNS Server, enter its address.
Enter an Web Socket Password password. This password is used for the links to other IP Office servers in the network.
Check the settings are all as required and match the customer network requirements.
Click Next. The IP Office services on the servers are restarted using the new configuration.
For non-subscription systems, assign the licenses required by the server from those available on the networks primary server. See Assigning PLDS licenses.
