UCM6300 Series Enterprise Grade IP PBX Phone System User Guide

: July 10, 2024
: UCM

Table of Contents

UCM6300 Series Enterprise Grade IP PBX Phone System
Product Usage Instructions
INTRODUCTION
CONFIGURATION STEPS
Media Server
CONSIDERATIONS
CLUSTER CAPABILITIES
HIGH AVAILABILITY WITH THE CLUSTER
FAQ
References
Read User Manual Online (PDF format)
Download This Manual (PDF format)

UCM6300 Series Enterprise Grade IP PBX Phone System

UCM6300-Series-Enterprise-Grade-IP-PBX-Phone-System-
product

Specifications:

Product Model : UCM630X
Supported Devices: UCM6304, UCM6308
Feature : 1+N Media Cluster

Product Usage Instructions

Configuration Steps: Business Server

Setting static IP address

Access the UCM’s web UI, go to System Settings > Network Settings.
Set a static IP on the network interface connected to the media servers’ network.
Click Save to save the configuration on the UCM.

Configure Cluster-related settings

Navigate to System Settings > Cluster.
Enable Media Cluster and choose Device Role as Business Server.
Choose Multicast Network Port based on networking settings.
Enter a multicast IP address and port range for sending multicast traffic.
Click Save to save the configuration.

Media Server(s):

Setting static IP address
Assign a static IP address for the media server(s) in the same network segment as the business server.

Configure Cluster-related settings

Navigate to System Settings > Cluster.
Enable Media Cluster and choose Device Role as Media Server.
Enter the same Multicast Network Port and Multicast IP Address as configured on the Business Server.
Set the Multicast Address Port Start and End values.
Save the configuration.

INTRODUCTION

UCM630X 1+N media cluster feature allows clustering multiple UCM6300 Series devices to expand the number of concurrent calls and meeting participants.
The deployment architecture of this feature consists of one main business server that handles signaling, and at least one other server handling the media traffic. Please see the illustration below.

$UCM6300-Series-Enterprise-Grade-IP-PBX-Phone-System-fig- $1$$

Important
Please note that 1+N media cluster feature is currently supported on the UCM6304 and UCM6308 only.

Notes

All UCMs that make up the media cluster must be under the same switch, and their IP addresses must be in the same network segment.
The Business Server and Media Servers must use the same firmware version.
Please ensure that the IP addresses of the business server and media server in the cluster environment do not change.Otherwise, the connection between the cluster devices will be affected. The cluster will need to be rebuilt if a change in IP address occurs

CONFIGURATION STEPS

The configuration of the cluster feature consists of two main parts, one part will be about the configuration of the business server, and the other part will be about the configuration of the media server(s).

Business Server

Setting static IP address
To ensure that the connection isn’t lost to the business server, the user must configure a static IP on the business server. This can either done on the DHCP server by reserving an IP address using the MAC address of the network interface of the UCM, or we can set a static IP address on the intended network interface of the UCM.

To set the address statically on the UCM, please follow the steps below:

Access the UCM’s web UI, navigate to System Settings > Network Settings, and then set a static IP on the network interface which is connected to the network where the media servers are hosted. $UCM6300-Series-Enterprise-Grade-IP-PBX-Phone-System-fig- $2$$
Click “Save” to save the configuration on the UCM.

Configure the Cluster-related settings
To configure the UCM as the business server, please follow the steps below:

Navigate to System Settings > Cluster, then tick the option Enable Media Cluster.
Choose “Business Server” as the Device Role.
Choose the Multicast Network Port. This depends on the networking settings for the UCM (Route mode or Dual mode).
Enter a multicast IP address that will be used to send multicast traffic. Please ensure that the IP address used is within the range of multicast IP addresses.
Enter a port range start value and end value in the corresponding fields. Please ensure that the range of ports is between 1024 – 65535.
Enter the Business Server Listening Port number. Please ensure that the port number is within the range 1024 – 65535.
Then, we will enter the media server addresses, we can enter the addresses for now, then assign them later to the media server(s), in this example, we will assign the IP address 192.168.5.171, which will be set as a static IP address for the media server(s) in the following section regarding the configuration steps for the media server(s).
Once all the settings mentioned above are configured, please click “Save” to save the configuration.

$UCM6300-Series-Enterprise-Grade-IP-PBX-Phone-System-fig- $3$$

__

Enable Media Cluster

| __

Enable Media Cluster feature.

---|---
__

__

Device Role

| __

Conﬁgure the device role.

__

● Business Server: Choosing this role will make the UCM as the main server for operations.

● Media Server: Choosing this role will make the UCM as a media server only. All the PBX related features will be disabled.

__

Multicast Network Port

| __

Choose the network port which will be used for the multicast.

__

Multicast IP Address

| __

The allowed multicast IP address range is 224.0.1.0 – 238.255.255.255

__

Multicast Address Port Start Value

| __

Enter the multicast address port start value. The port number value can be within the range 1024 – 65535.

Note : The multicast address port start value must be lower or equal to the multicast address port end value.

__

Multicast Address Port End Value

| __

Enter the multicast address port end value. The port number value can be within the range 1024 – 65535.

Note: The multicast address port end value must be greater or equal to the multicast address port start value.

__

Business Server Listening Port

| __

The port on which the business server listens and receives information reported by the media server. The value of the listening port value can be within 1024 – 65535.

---|---
__

__

Media Server IP

| __

Enter the IP address of the media server. The user can pair up to 5 media servers with one Business server.

The statuses of the media servers are indicated using three colors:

__

● Green : The server is available.

● Yellow : The server is in use.

● Gray : The server is oﬄine.

__

Memory Usage Threshold (%)

| __

When the memory usage of this media server is exceeded, media services will be assumed by another media server in the cluster with the lowest usage at the time.

__

CPU Usage Call Control Threshold (%)

| __

When the CPU usage of this media server is exceeded, media services will be asssumed by another media server in the cluster with the lowest usage at the time.

__

Memory Usage Threshold (%)

| __

When this server’s memory usage exceeds the speciﬁed threshold, service from

this server will be temporarily paused.

__

CPU Usage Call Control Threshold (%)

| __

When this server’s CPU usage exceeds the speciﬁed threshold, service from this

server will be temporarily paused.

__

Disk Available Space (MB)

| __

When the percentage of available space in the device’s disk data partition falls below the set value, this server will not be used until the amount of available space is above the threshold again.

The availability of the media server is indicated using the icons below:

$UCM6300-Series-Enterprise-Grade-IP-PBX-Phone-System-fig- $4$$

Media Server

Setting static IP address
Similar to the business server, we also need to set the static IP address for the media server to avoid losing the connection to it.

Access the UCM’s web UI, navigate to System Settings > Network Settings, and then set a static IP on the network interface which is connected to the network where the business server is hosted. $UCM6300-Series-Enterprise-Grade-IP-PBX-Phone-System-fig- $5$$
Click “Save” to save the configuration on the UCM.

Configure the Cluster-related settings
To configure the UCM as a media server, please follow the steps below:

Please navigate to System Settings > Cluster
Tick the option “Enable Media Cluster”
Select “Media Server” as the Device Role
Enter the IP address of the business server and the listening port configured on the Business server. $UCM6300-Series-Enterprise-Grade-IP-PBX-Phone-System-fig- $6$$
__

Enable Media Cluster

| __

Enable Media Cluster feature.

---|---
__

Device Role

| __

Conﬁgure the device role.

__

Business Server IP and Port

| __

Enter the IP address of the business server with the listening port.

| If the business server is using HA Local Hot Standby, the Hot Standby Cluster IP address must be used.

If the business server is using HA Remote Disaster Recovery, the primary UCM and secondary UCM must have their own respective cluster environments.

---|---
5. Then click “Save” to save the configuration.

CONSIDERATIONS

Meeting Settings
Please ensure that the following settings are identical across all the UCMs involved in the cluster deployment. To access the configuration page, please navigate to Call Features > Multimedia Meeting.

$UCM6300-Series-Enterprise-Grade-IP-PBX-Phone-System-fig- $7$$

SIP Settings
Please ensure that the following ToS SIP settings are identical across all the UCM devices which are involved in the cluster. To access the configuration page please navigate to PBX Settings > SIP Settings > ToS

$UCM6300-Series-Enterprise-Grade-IP-PBX-Phone-System-fig- $8$$ RTP Settings
In case when the Business Server is behind a NAT router and does not possess a RemoteConnect plan, the user must configure port forwarding on the router and all the UCMs should have different ports ranges for the RTP and BFCP. Assuming that UCM1 has an RTP range of 10000-20000, UCM2 should use 20001-30000, and UCM3 should use 30001-40000 etc… The same logic should apply to BFCP, then port forwarding rules for both RTP and BFCP should be created at the level of the router, each range should correspond with its respective UCM IP address as the destination of the forwarding. If TURN server is used, then the same TURN server can be used for all the media servers.

To access the configuration page of RTP Settings, please navigate to PBX Settings > RTP Settings

$UCM6300-Series-Enterprise-Grade-IP-PBX-Phone-System-fig- $9$$

CLUSTER CAPABILITIES

The following table mentions the number of calls each business server is capable of processing and the additional calls that each media server will process based on the model of the UCM used.

|

UCM6304

|

UCM6308

---|---|---

Business Server

Max Concurrent Calls

|

300

|

450

Max Meeting Participants

|

200

|

300

Media Server

Media Server Additional Concurrent Calls

|

335

|

390

Media Server Additional Meeting Participants

|

250

|

300

HIGH AVAILABILITY WITH THE CLUSTER

Local Hot-standby:
If the business server is configured with HA Local Hot-standby, then media server must configure the Business Server IP field with the HA cluster IP address. In case of HA failover, the secondary unit will also be able to take advantage of the existing media cluster.

Note
To configure Local Hot-standby for the UCM devices, please refer to the following guide:

UCM630x/A – High Availability User Guide: Local HA

Remote Disaster Recovery:
Cluster configuration is not synced in Remote Disaster Recovery environments. Users can choose to expand the capacity of only one of the UCMs or both units. In case of the latter, the primary and secondary units must configure their own separate cluster environments.

Note
To configure Remote Disaster Recovery for the UCM devices, please refer to the following guide:

UCM630x/A – High Availability User Guide: Remote Disaster Recovery

FAQ

Q: Which UCM models support the 1+N Media Cluster feature?
A: The feature is supported on UCM6304 and UCM6308 models only.

Q: Can the IP addresses of the business server and media server change in a cluster environment?
A: No, the IP addresses must remain static within the same network segment to maintain cluster connectivity. Changing IP addresses will require rebuilding the cluster.