Multi Cell System
This section describes how to setup a multi cell environment, by connecting Galaxy AP500M bases into one system.
Step 1
Connect the base stations to a private network via the standard Ethernet cable (CAT 5).
Step 2
Access the first base by determining the IP address and then logging into the user interface of the device.
Step 3
To ensure a stable synchronization between the bases in the system, you must configure the time zone. For this purpose, navigate to the Country page and configure the Country and Time server settings.
- Select the Country, then select the Region if applicable.
- Enter the Time Server address, e.g. 0.rhel.pool.ntp.org.
- Select the checkbox for Set timezone by country/region.
- Select the checkbox for Set DST by country/region.
- Click Save and Reboot.
Make sure that the Time server is set on the base, else the multi cell feature will not work. This can be done by verifying that the Time Server address is still present in the field, after the reboot.
Step 4
Navigate to the Servers page and click on Add Server to add the UCX server information. This is the server that contains the extensions. Fill in the following fields and click Save.
- Server Alias – Enter a descriptive name for the server. (Limited to 11 characters.)
- Registrar – Enter the hostname or IP address of UCX with the SIP port number.
For example: 192.168.1.200:5060
Step 5
Navigate to the Extensions page and click on Add Extension.
Fill in the following fields and click Save.
- Line Name – Enter a name for the line (This field is not shown on Galaxy AP500D)
- Extension – Extension number
- Authentication User Name – Extension number
- Authentication Password – Secret for the extension
- Display Name – Name to be shown on the phone
- Mailbox Name – Extension number
- Mailbox Number – *97
- Server – Select the server created in Step 4.
To configure a multi cell environment, it is important to create at least one extension on the base station to define the primary base. Thus, registering a handset at this point is not a requirement.
Step 6
After creating an extension, you can now configure the base in multi cell mode. Navigate to the Multi cell page. Enable the Multi cell system parameter and type in a value for the System chain ID. Press Save and Reboot.
After the reboot, on the front page of the UI will be displayed the following System information status:
“Unchained Allowed to Join as Primary”
Step 7
Login to the base station that you wish to connect to the multi cell chain.
Step 8
Navigate to the Multi cell page, enable the Multi cell system parameter and enter the System chain ID that you previously typed for the primary base station (see step 6). Press Save and Reboot.
After reboot, the base will try to find and synchronize to the primary base station.
Depending on the base’s role, the System information status will display Primary or Secondary on the front page of the UI, as soon as the multi cell system is ready.
To add more base stations, repeat Steps 7-8.
It takes up to 5 minutes (synchronization time) to add a new base station to a multi cell system.
Step 9
Register your handsets.
LAN Sync
The Galaxy AP500M base station supports the LAN Sync feature, which allows data synchronization over the network, instead of Over-the-air (Air sync). This feature, specified by the IEEE1588 standard, has the advantage of providing a larger coverage installation option for places where the bases cannot “see” each other.
Before configuring LAN Sync, the administrator must be aware of the network requirements in order to minimize the impact from other devices on the network. Please refer to DECT – Traffic Planning and Deployment for more details.
The following sections present the available settings on the LAN Sync page.
IEEE1588 LAN Synchronization Settings
By default LAN sync is disabled. To enable the LAN Sync feature, set IEEE1588 to Enabled.
Zone LAN sync setup
The following settings cover the global configuration of the synchronization in a zone.
| Parameter | Default Value | Description |
|---|---|---|
| Multicast IP Address | 224.0.1.129 | This setting defines the IP address where to listen for IEEE1588 PTP packages (IP address of the multicast group). The IP must be the same for all devices in the specific zone. NOTE: This should only be changed in case other IEEE1588 equipment is on the network using this specific IP address. NOTE: The IP address must start with 224.0.xx.xx and this cannot be changed. NOTE: Before setup, make sure no other devices are using the given IP. This means that each zone should have a different IP! |
| Multicast Port | 319 | Define the port which the system will communicate on (where to listen for the IEEE1588 PTP messages). The port must be the same for all devices in the specific zone. NOTE: This should only be changed in case other IEEE1588 equipment on the network is using this specific port. NOTE: Each zone must have a different port. |
| Domain Number | 0 | This setting selects the domain number, which is the preferred method to divide the IEEE1588 PTP messages into zones in IEEE 1588-2008. Valid input: 0-127 |
| Alternative Domain Number | 64 | Alternative domain is only used in case the primary sync source from the main domain fails. If so, the base station will sync to the alternative domain. NOTE: It must NOT have the same value as the domain number. Valid input: 0-127 |
| Multi Cell Debug Mode | None | This feature should be enabled if one wants the system to catalogue low level multi cell debug information or traces. NOTE: Must only be used for debug purpose and not enabled on a normal running system Available Options: Data Sync: Writes header information for all sent and received packets to be used to debug specific issues. Generates a lot of Syslog signaling and is only recommended to enable shortly when debugging. Auto Tree: Writes states and data related to the Auto Tree Configuration feature. Both: Both Data Sync and Auto Tree are enabled. IEEE1588 Debug: Writes IEEE1588 debug information to the syslog |
External LAN sync setup
This covers the configuration of an external (multi-level) synchronization. This means that, in order to support more than 250 Base stations in a system, it is necessary to use multi-level synchronization. This feature is used to define the Primary zone to which all the other zones will sync.
| Parameter | Default Value | Description |
|---|---|---|
| External Sync Source | Disabled | Enable the feature by choosing one of the options below: Primary zone configuration Secondary zone configuration In a default setup, Zone 0 is set as Primary zone and the rest of the zones are configured as Secondary zone. |
| Multicast IP Address | 224.0.1.129 | To listen for IEEE1588 PTP packages, the IP address should be defined. NOTE: This should only be changed in case other IEEE1588 equipment is on the network using this specific IP address. NOTE: The IP address must start with 224.0.xx.xx and this cannot be changed. NOTE: Before setup, make sure no other devices are using the given IP. |
| Multicast Port | 319 | Define the port on which the system will listen to IEEE1588 PTP messages. NOTE: This should only be changed in case other IEEE1588 equipment is on the network using this specific port. |
| Domain Number | 1 | This setting selects the domain number, which is the preferred method to divide the IEEE1588 PTP messages into zones in IEEE 1588-2008. Valid input: 0-127 NOTE: The input must NOT be the same as the one used in the previous section “Zone LAN Sync setup” |
| Alternative Domain Number | 65 | Alternative domain is only used in case the primary sync source from the main domain fails. If so, the base station will sync to the alternative domain. NOTE: The input must NOT have the same value as the “Domain number” and must NOT be used in the “Zone LAN Sync setup” section. Valid input: 0-127 |
Base Station Group
The Base station group lists various parameter settings for the base stations and allows the administrator to check the status information for the whole system.
This Unit Debug
This section displays debug information, which is used only by support to debug LAN Sync network issues. In case debug is needed, send this information to the support team. The debug data is not synced between the bases.
