Media Server Standalone

In larger networks with many SIP end-point traffic, it may be beneficial to have the Media Server reside in a separate server or VM to avoid putting load on the Service Node. Also, if there is a need to have more than one Media Server controlled by the same MX-ONE Service Node, the other Media Server instance would have to run in separate Linux server / VM, although managed by the same Service Node.

Media Server Standalone

Standard Hyper-V and Failover Clustering/ KVM

RTP

Memory (GB)

CPU

CPU

Disk

Application

Number of RTP channels

Minimum Memory required/reserved in GB per VM

Minimum CPU/vCPU required

Minimum MHz required/reserved

Disk Size (GB)

Type of Application

500

6

2

2000

100

Media Server

1000

8

3

2500

100

Media Server

2000

10

4

4000

100

Media Server

Note: Force gateway calls require more CPU resources.