Specifications

Interoperability Configuration Reference Manual (MGCP/NCS Version)

Mediatrix 4100

Multiple Fax Tone Detection

You can control whether the Mediatrix 4100 reports more than one occurrence of the fax tone during the

negotiation phase. This is used when event notification requests can be received after the fax tone.

 To enable multiple fax tone detection:

1. In the mgcpncsExperimentalMIB, set the mgcpncsMultipleFaxToneDetection variable to enable.

The Mediatrix 4100 will report every occurrence of the fax tone event.

If you set the variable to disable, when establishing a fax call, the Mediatrix 4100 only reports the

first occurrence of the fax tone event.

Connected RTP Sockets

You can define whether the endpoints will listen to RTP sources other than the one with which they established

a RTP session.

 To use connected RTP sockets:

1. In the mgcpncsExperimentalMIB, set the mgcpncsConnectRtpSockets variable to enable.

The endpoints will only play packets coming from the address established in the RTP session.

If you set the variable to disable, the Mediatrix 4100 uses unconnected sockets and the endpoints

will play any RTP packets addressed to them.

2. Restart the Mediatrix 4100 so that the changes may take effect.

UDP Checksum

You can enable the UDP checksum in the RTP stack.

A checksum is a count of the number of bits in a transmission unit that is included with the unit so that the

receiver can check to see whether the same number of bits arrived. If the counts match, it's assumed that the

complete transmission was received.

UDP checksumming is disabled by default to gain performance. In this case, the UDP checksum is not

calculated. The value 0 is written in the checksum field of each RTP packet header.

 To enable UDP checkum:

1. In the mgcpncsExperimentalMIB, set the mgcpncsRtpUdpChecksumEnable variable to enable.

The UDP checksum is calculated for each RTP packet. Note that this may affect performance. The

parameter takes effect on the next connection.

max-32bits The session ID and the session version number are represented with a

32-bit integer. They have a maximum length of 10 digits.

max-64bits: The session ID and the session version number are

represented with a 64-bit integer. They have a maximum length of 20

digits.

Table 59: Session ID/Version Parameters (Continued)

Parameter Description