Media Server
Standard Setup
The following tables show the Media Server requirements for Direct Media and Forced Gateway scenario. The recommended figures in below tables are done with the Media Server co-located in the same virtual machine as the Service Node, called MX-ONE Softswitch.
Direct Media Setup
It means that a full SIP solution (SIP trunk and SIP extensions) was deployed and the media server is used for conference calls, for example.
|
Other Service Node and Other Service Node Standby without applications |
||||||
|---|---|---|---|---|---|---|
|
Standard Proxmox VE |
||||||
|
Number of Devices |
Memory (GB) |
CPU |
CPU |
Disk |
Application |
Max Traffic |
|
Max SIP Devices Capacity |
Minimum Memory required/reserved in GB per VM |
Minimum CPU/vCPU required |
Minimum MHz required/reserved |
Disk Size (GB) |
Type of Application |
Calls per Second |
|
500 |
6 |
2 |
2000 |
100 |
SN, SNM, Cassandra |
1.00 |
|
1000 |
8 |
3 |
2500 |
100 |
SN |
2.00 |
|
2500 |
8 |
4 |
3500 |
100 |
SN |
5.00 |
|
5000 |
10 |
4 |
5500 |
100 |
SN |
10.00 |
|
15000 |
16 |
6 |
8000 |
100 |
SN |
15.00 |
* G.729/G.722 codec is not supported in this configuration.
Forced Gateway
In some traffic cases transcoding is required and for those cases more RTP gateway resources are needed. As a consequence, more CPU resources are necessary to handle those gateway calls in the media server.
* G.729/G.722 codec is not supported in this configuration.