Media5 Mediatrix 4104, Reference Manual

Page: 89 / 466

SIP Interop Reference Manual (SIP Version)
Mediatrix 4104 67
SIP Transport Type
You can globally set the transport type for all the lines of the Mediatrix 4104 to either UDP (User Datagram
Protocol) or TCP (Transmission Control Protocol). The Mediatrix 4104 will include its supported transports in
its registrations.
Please note that RFC 3261 states the implementations must be able to handle messages up to the maximum
datagram packet size. For UDP, this size is 65,535 bytes, including IP and UDP headers. However, the
maximum datagram packet size the Mediatrix 4104 supports for a SIP request or response is 5120 bytes
excluding the IP and UDP headers. This should be enough, as a packet is rarely bigger than 2500 bytes.
You can also set these parameters via SNMP, as described in “SIP Transport Type” on page 263 .

To set the SIP transport type parameters:
1. In the SIP Transport section of the Interop page, enable the transport types to use in the proper
Activation drop-down menu.
You can enable or disable the UDP and TCP transports.
Figure 32: SIP Transport Section
2. Set the priority order of the UDP and TCP transports in the proper Q Value field.
A qvalue parameter is added to each contact. The qvalue gives each transport a weight, indicating
the degree of preference for that transport. A higher value means higher preference.
The format of the qvalue string must follow the RFC 3261 ABNF (a floating point value between
0.000 and 1.000). If you specify an empty string, no qvalue is set in the contacts.
3. Click Submit if you do not need to set other parameters.
Interop Parameters
The interop parameters allow the Mediatrix 4104 to properly work, communicate, or connect with specific IP
devices.

To set interop parameters:
1. In the Interop section of the Interop page, set the Escape Pound (#) in SIP URI Username drop-
down menu with the proper behaviour.
This allows you to define whether or not the pound character (#) must be escaped in the username
part of a SIP URI.
Figure 33: Interop Section
Standards Supported RFC 3261 – SIP: Session Initiation Protocol
1 2
Table 44: Escaping Pound Character Parameter
Parameter Description
Enable The Pound character (#) is escaped in the username part of a SIP URI.
1
3
2
4