Skip to end of metadata
Go to start of metadata

Download PDF Document

2018-09-13

For All DGW Services and Mediatrix Units

v. 43.0.1125


1 Configuration Details

When defining your DGW configuration, you must take into consideration the following information to make sure your deployment scenario will work as expected.

Call Routing

  • A call coming from a SIP interface cannot be routed to another SIP interface. In this case, the call automatically fails. To route a call from SIP to SIP, the Sbc service must be used.
  • Simultaneous ring group destinations are limited to FXS interfaces only.
  • A call automatically fails if it is redirected to a route or hunt more than 10 times.
  • The Called Bearer Channel and Calling Bearer Channel call properties are limited to ISDN interfaces only.
  • The Call Rerouting feature is not available in the NI2 and QSIG signalling protocols.
  • The T.38 priority is hard coded to 10.

Codecs

The G.722 codec is only available on the Mediatrix 4400 series.

File Upload Limits

The file upload limit is determined by the amount of space allocated to uploads.

Mediatrix Unit Maximum File Size
Sentinel 400 (Flash Memory divided by 2) - 1 GB for a maximum of 32 GB
Sentinel 100 (Flash Memory divided by 2) - 1 GB for a maximum of 32 GB
S7 1 MB
G7 1 MB
C7 256 KB
3000 1 MB
4102 0 KB - you cannot upload files
41xx 1 MB
44xx 1 MB

Jitter Buffer

  • The jitter buffer maximum length is limited to 150 ms on the Mediatrix 4400/4100/3000 platforms.
  • The jitter buffer maximum length is limited to 900 ms on all other Mediatrix platforms.

Protocols

  • The AOC features are not available in the NI2 and QSIG signalling protocols.

Provisioning

  • Only FXS lines can be managed by the TR-104 profile. BRI, PRI, or FXO lines are not supported, but can be set up with configuration parameters.

Sbc Service

  • The Sbc service does not support domain names that resolve to CNAME. When receiving such an entry, it will stop trying to contact the domain even if it has also received an A or AAAA record.

Time Clock

  • Except for the Sentinel models which have a Real-Time-Clock (RTC), all Mediatrix units need to be connected with a NTP server in order to update and synchronise the local clock at start time. Since some services require accurate time to work properly, you should configure the SNTP settings to point to an available time server.

Troubleshooting

  • PCM capture does not support sending streams with a ptime of 10 ms.

2 Overall Performance

The overall performance of a Mediatrix unit can be affected by several factors. Depending on your deployment scenario, one or several of the following aspects should be considered.

Call Routing

  • Enabling the IP routing service and adding rules has an impact on the Mediatrix unit’s overall performance as IP routing requires additional processing. The more rules are enabled, the more overall performance is affected.
  • Expiration delays will set the session refresh messages periodicity, using longer delays reduces the network usage, but it will take more time to detect dead calls.

Debugging

  • Enabling all traces could significantly slow down the performance of the Mediatrix unit.
  • Significant CPU resources are required when notifications are sent frequently to the local log. This can have an impact on the unit's performance.
  • Enabling pcapture could significantly slow down the performance of the Mediatrix unit if it is already managing several calls on most of its ports.

Firewalls

  • Enabling the local firewall or the network firewall and adding rules has an impact on the Mediatrix unit’s overall performance as the firewall requires additional processing. The more rules are enabled, the more overall performance is affected.

Fax

  • The quality of T.38 fax transmissions depends on several factors such as the system configuration and the model of fax machine used. Should some of these conditions be unsatisfactory, performance of T.38 fax transmissions may vary and be reduced below expectations.

Codecs

  • The number of calls Mediatrix units can handle simultaneously can be less than expected depending on the type of codec enabled. There is a way not to impact the number of simultaneous calls by enabling only G.711 codecs and disabling every other voice or data codecs, even T.38.
  • Enabling Secure RTP (SRTP) will have a direct impact on the Mediatrix unit overall performance, as SRTP requires CPU power. The more lines use SRTP, the more overall performance is affected. This is especially true on the Mediatrix 4116/4124 and Mediatrix LP 16/24. This could mean that a user picking up a telephone on these models may not have a dial tone due to a lack of resources.
  • The ptime has a direct impact on the number of concurrent calls that a unit can handle. For more details, refer to Packetisation Time (ptime) .
  • With the exception of Mediatrix 3000, 4400, and 4100 Series units, units operating with the G.723.1 codec may have limited processing capabilities meaning that the number of concurrent calls in G.723.1 is lower than with other codecs. There is no maximum number of concurrent calls enforced, but issues may occur when more than 10 channels are used per DSP.

Web

  • Navigating on the DGW Web Interface may impact the overall performance.

3 IPv6 Availability

DGW supports IPv6 except for:
  • CPE WAN Management Protocol (CWMP)/TR-069
  • DHCP embedded sever
  • IP Routing
  • Local Firewall (LFW)
  • Network Firewall (NFW)
  • Network Address Translation (NAT)
  • Online Certificate Status Protocol (OSCP)
  • Remote Authentication Dial In User Services (RADIUS)
  • Session Border Controller (SBC)
  • Simple Network Management Protocol (SNMP)
  • PPPoE

4 Packetisation Time (ptime)

The packetisation time, also called ptime, is the duration, in milliseconds (ms), of a voice packet.

The ptime has a direct impact on the number of concurrent calls that a unit can handle. As a general rule, the higher the ptime, the higher the number of concurrent calls can be achieved. Using a ptime of more than 30 ms, even if a ptime of 100 can be used on some models, it will not make a huge difference in the processing capacity. However, using a ptime of 10 or 20 ms will significantly reduce the number of concurrent calls the unit can handle.

Media5 recommends:

  • A 30 ms packetization time when the Local or Network firewall is enabled (instead of a 20 ms ptime, for instance) to simultaneously use all the channels available on the unit, especially with the Mediatrix 3632/4404/4124/LP24 models.
  • A 30 ms packetization time when IP routing is enabled (instead of 20 for instance) to simultaneously use all the channels available on the unit, especially with the Mediatrix 3632/4404/4104 models.
  • A 30 ms packetization time when the NAT is enabled (instead of 20 for instance) to simultaneously use all the channels available on the unit, especially with the Mediatrix 3632/4404 /4104 models.
  • 40 calls @ 20 ms ptime is the recommended setup to avoid voice call quality drop on a Mediatrix 3000.


5 Processing Capacity

The processing capacity is the number of concurrent calls a unit can handle successfully.

The processing capacity of the Mediatrix units depends on:

  • the Mediatrix unit model or cards used
  • the codec
  • if media is encrypted (SRTP)
  • the Packetisation Time (ptime)
  • if fax transmission is used at the same time
  • if several functionalities using substantial amounts of CPU are running simultaneously (such as maintenance, configuration on Web pages, or SNMP requests)
  • if 3-way conference calls are ongoing

The number of possible 3-way conferences also depends on:

  • the number of channels in use
  • the type of codec
  • if media is encrypted
However, in order to make a 3-way conference, sufficient channels must be available. For example, if all channels are in use, 3-way conference will not be possible.


5.1 Channel Limitations per Model

Model RTP and Uncompressed Codec RTP and Compressed Codec SRTP and Uncompressed Codec SRTP and Compressed Codec Max 3-way Calls
3208 10 8 8 6 2
3216 20 16 16 12 4
3308 10 8 8 6 2
3316 20 16 16 12 4
3404 10 8 8 8 0
3408 20 16 16 16 0
3531 23 23 23 23
3532 46 46 46 46
3621 15 15 15 15 0
3631 30 30 30 30 0
3632 60 60 60 60 0
3716 20 16 16 12 4
3731 40 38 38 36 2
3732 40 38 38 36 2
3734 40 38 38 38 0
3741 20 16 16 14 4
3742 20 16 16 14 2

Note: 3-way conference channels are included in the other max channel limitations.

Model RTP and Uncompressed Codec RTP and Compressed Codec SRTP and Uncompressed Codec SRTP and Compressed Codec Max 3-way Calls
4102 4 4 4 4 2

Note: 3-way conference channels are included in the other max channel limitations.

Model RTP and Uncompressed Codec RTP and Compressed Codec SRTP and Uncompressed Codec SRTP and Compressed Codec Max 3-way Calls
4108 10 8 8 6 2
4116 20 16 16 12 4
4116 LP 20 16 16 12 4
4124 30 24 24 18 6
4124 LP 30 24 24 18 6

Note: 3-way conference channels are included in the other max channel limitations.

Model RTP and Uncompressed Codec RTP and Compressed Codec SRTP and Uncompressed Codec SRTP and Compressed Codec Max 3-way Calls
4401 2 2 2 2 0
4402 4 4 4 4 0
4404 8 8 8 8 0

Note: 3-way conference channels are included in the other max channel limitations.

Model RTP and Uncompressed Codec RTP and Compressed Codec SRTP and Uncompressed Codec SRTP and Compressed Codec Max 3-way Calls
C710 6 6 6 6 2
C711 10 10 10 10 2
C730 4 4 4 4 0
C731 10 10 10 10 2
C733 8 8 8 8 0
C735 8 8 8 8 2

Note: 3-way conference channels are included in the other max channel limitations.

Model RTP and Uncompressed Codec RTP and Compressed Codec SRTP and Uncompressed Codec SRTP and Compressed Codec Max 3-way Calls
G7 - 1 PRI 30 30 30 30 0
G7 - 2 PRI 60 60 60 60 0
G7 - 4 PRI 120 120 120 120 0
G7 - 1 PRI 4 FXS 34 32 32 30 4
G7 - 1 PRI 4 FXS* 38 38 38 38 4
G7 - 1 PRI 8 FXS 44 44 44 44 6
G7 - 2 PRI 4 FXS 68 64 64 60 4
G7 - 4 PRI 4 FXS 128 128 128 120 4
G7 - 8 FXS 8 FXO 17 16 16 15 2
G7 - 16 FXO 16 16 16 15 0
G7 - 24 FXO 24 24 24 24 0

*Model with more channel processing capabilities.

Note: 3-way conference channels are included in the other max channel limitations.

Model RTP and Uncompressed Codec RTP and Compressed Codec SRTP and Uncompressed Codec SRTP and Compressed Codec Max 3-way Calls
LP08 10 8 8 6 2
LP16 20 16 16 12 4
LP24 30 24 24 18 6

Note: 3-way conference channels are included in the other max channel limitations.

Model RTP and Uncompressed Codec RTP and Compressed Codec SRTP and Uncompressed Codec SRTP and Compressed Codec Max 3-way Calls
S716 16 16 16 15 2
S716 LP 16 16 16 15 2
S724 17 16 16 15 2
S724* 24 24 24 24 4
S724 LP 17 16 16 15 2
S724 LP* 24 24 24 24 4

Note: 3-way conference channels are included in the other max channel limitations.

*: Model with more channel processing capabilities.

Model RTP and Uncompressed Codec RTP and Compressed Codec SRTP and Uncompressed Codec SRTP and Compressed Codec Max 3-way Calls
Sentinel 100 - 1 PRI 30 30 30 30 0
Sentinel 100 - 2 PRI 60 60 60 60 0
Sentinel 100 - 4 PRI 120 120 120 120 0
Sentinel 100 - 1 PRI 4 FXS 34 32 32 30 4
Sentinel 100 - 1 PRI 4 FXS* 38 38 38 38 4
Sentinel 100 - 1 PRI 4 FXS 4 FXO 42 42 42 42 4
Sentinel 100 - 2 PRI 4 FXS 68 64 64 60 4
Sentinel 100 - 2 PRI 8 FXS 8 FXO 84 80 80 75 8
Sentinel 100 - 4 PRI 4 FXS 128 128 128 120 4
Sentinel 100 - 4 FXS 6 6 6 6 2
Sentinel 100 - 8 FXS 10 10 10 10 2
Sentinel 100 - 16 FXS 17 16 16 15 2
Sentinel 100 - 24 FXS 28 28 28 28 4
Sentinel 100 - 4 FXO 4 4 4 4 0
Sentinel 100 - 8 FXO 8 8 8 8 0
Sentinel 100 - 4 FXS 4 FXO 10 10 10 10 2
Sentinel 100 - 1 PRI 8 FXS 38 38 38 38 4
Sentinel 100 - 1 PRI 12 FXS 44 44 44 44 6

*Model with more channel processing capabilities.

Note: 3-way conference channels are included in the other max channel limitations.

The Sentinel 400 does not come with predefined slotted cards. Customer is free to use any extension cards in its unit as long as it follows the guidelines stated in the hardware installation guide. The entries in the table below are given as examples to show several configurations for the Sentinel 400.

Model RTP and Uncompressed Codec RTP and Compressed Codec SRTP and Uncompressed Codec SRTP and Compressed Codec Max 3-way Calls
Sentinel 400 base unit 0 0 0 0 0
Sentinel 400 with 1 PRI card 30 30 30 30 0
Sentinel 400 with 1 DSP card 7 FXS cards 32 32 32 30 4
Sentinel 400 with 1 DSP card 7 FXO cards 28 28 28 28 0

Note: 3-way conference channels are included in the other max channel limitations.


6 Platform-Specific Service Notifications


6.1 Notifications Not Available on the Mediatrix Sentinel 400

All Service Notifications are available on the Mediatrix Sentinel 400.


6.2 Notifications Not Available on the Mediatrix Sentinel 100

Service NumKey Message
VM ALL

6.3 Notifications Not Available on the Mediatrix G7

Service NumKey Message
Sbc ALL
VM ALL

6.4 Notifications Not Available on the Mediatrix S7

Service NumKey Message
Sbc ALL
VM ALL

6.5 Notifications Not Available on the Mediatrix C7

Service NumKey Message
Dcm 30 The Power Supply Unit #%1$d is in fault state.
40 The Power Supply Unit #%1$d recovered from the previous fault state.
70 Warning, disk wear level is at %1$d percent.
Eam ALL
Isdn ALL
R2 ALL
Sbc ALL
SipEp 610 The gateway %1$s is configured for SBC binding but not its signaling interface.
620 The gateway %1$s cannot have multiple media interfaces because it is bound to the SBC.
630 The gateway %1$s servers configuration does not allow correct SBC binding.
VM ALL

6.6 Notifications Not Available on the Mediatrix 3000

Service NumKey Message
Dcm 30 The Power Supply Unit #%1$d is in fault state.
40 The Power Supply Unit #%1$d recovered from the previous fault state.
70 Warning, disk wear level is at %1$d percent.
VM ALL

6.7 Notifications Not Available on the Mediatrix 4108-16-24

Service NumKey Message
Dcm 30 The Power Supply Unit #%1$d is in fault state.
40 The Power Supply Unit #%1$d recovered from the previous fault state.
70 Warning, disk wear level is at %1$d percent.
Eam ALL
Isdn ALL
R2 ALL
Sbc ALL
SipEp 610 The gateway %1$s is configured for SBC binding but not its signaling interface.
620 The gateway %1$s cannot have multiple media interfaces because it is bound to the SBC.
630 The gateway %1$s servers configuration does not allow correct SBC binding.
VM ALL

6.8 Notifications Not Available on the Mediatrix 4102

Service NumKey Message
Dcm 30 The Power Supply Unit #%1$d is in fault state.
40 The Power Supply Unit #%1$d recovered from the previous fault state.
70 Warning, disk wear level is at %1$d percent.
Eam ALL
File 10 File %1$s has been deleted.
20 Not enough space to store file.
30 Download failed, a download is currently in progress.
35 Upload failed, an upload is currently in progress.
110 File %1$s successfully downloaded.
120 File %1$s successfully stored.
130 File %1$s failed to store.
140 File %1$s cannot be opened.
150 Maximum number of files reached, cannot store file %1$s.
160 No write permission on the destination folder %1$s.
170 No Erase permission on the destination folder %1$s.
180 No Read permission on the destination folder %1$s.
190 Unable to download the file %1$s, file not found.
200 Unable to upload the file %1$s, file not found.
210 File %1$s cannot be read.
220 File %1$s successfully uploaded.
Fpu 1000 Executing on recovery firmware.
4000 Rollback operation is starting.
4100 Rollback already in progress.
4200 Rollback operation could not complete successfully.
4300 Rollback operation could not complete successfully, retrying.
4400 Rollback to previously installed MFP succeeded.
4500 The system is now restarting to complete the firmware rollback.
Isdn ALL
R2 ALL
Sbc ALL
SipEp 610 The gateway %1$s is configured for SBC binding but not its signaling interface.
620 The gateway %1$s cannot have multiple media interfaces because it is bound to the SBC.
630 The gateway %1$s servers configuration does not allow correct SBC binding.
VM ALL
Web 60 Cancelling file upload because of timeout.

6.9 Notifications Not Available on the Mediatrix 4400

Service NumKey Message
Dcm 30 The Power Supply Unit #%1$d is in fault state.
40 The Power Supply Unit #%1$d recovered from the previous fault state.
70 Warning, disk wear level is at %1$d percent.
Eam ALL
Isdn ALL
Pots ALL
R2 ALL
Sbc ALL
SipEp 610 The gateway %1$s is configured for SBC binding but not its signaling interface.
620 The gateway %1$s cannot have multiple media interfaces because it is bound to the SBC.
630 The gateway %1$s servers configuration does not allow correct SBC binding.
VM ALL

7 Copyright Notice

Copyright © 2018 Media5 Corporation.

This document contains information that is proprietary to Media5 Corporation.

Media5 Corporation reserves all rights to this document as well as to the Intellectual Property of the document and the technology and know-how that it includes and represents.

This publication cannot be reproduced, neither in whole nor in part, in any form whatsoever, without written prior approval by Media5 Corporation.

Media5 Corporation reserves the right to revise this publication and make changes at any time and without the obligation to notify any person and/or entity of such revisions and/or changes.