Media5 Mediatrix 4104, Reference Manual

Page: 299 / 466

Interop Parameters Reference Manual (SIP Version)
Mediatrix 4104 277

To copy the uri-parameters to the level of proxy authentication:
1. In the sipInteropMIB , set the sipInteropProxyAuthenticationUriParametersEnable variable to
enable .
Unsupported INFO Request
You can define the Mediatrix 4104’s behaviour upon reception of an unknown type of INFO request.

To define the unsupported INFO request behaviour:
1. In the sipInteropMIB , set the sipInteropAckUnsupportedInfoRequests variable with the proper
behaviour.
Outbound Proxy Usage
You can define whether or not SIP requests sent to the proxy contain a Route header displaying the proxy's
address. It is only effective when an outbound proxy host is configured (see “Outbound Proxy Server” on
page 166 for more details). It is useful when interoperating with SIP servers that are not in conformance with
RFC 3261’s recommended practice concerning outbound proxy usage.

To set the outbound proxy usage:
1. In the sipInteropMIB , set the sipInteropRemoveOutboundProxyRouteHeader variable with the
proper behaviour.
International Code Mapping
Some international calling parties have their caller ID prepended with the “+” character. You can instruct the
Mediatrix 4104 to substitute this “+” character with a user-defined value.

To define an international code mapping:
1. In the sipInteropMIB , set the sipInteropInternationalCodeMappingString variable with the character
string that is substituted to the “+” character that prepends some international caller IDs.
2. Set the sipInteropInternationalCodeMappingEnable to enable .
The default value is disable , which means that no substitution is performed and the '+' character is
simply removed.
Table 178: Unsupported INFO Request Behaviour
Parameter Description
disable Unknown INFO requests trigger a 415 Unsupported Media Type response.
enable Reception of unknown INFO requests is acknowledged with a 200 OK response.
Table 179: Outbound Proxy Usage
Parameter Description
disable SIP requests sent to the outbound proxy contain a Route header, as per RFC
3261's recommendation. This is the default behaviour.
enable SIP requests are routed to the outbound proxy without inserting a Route header in
the SIP packet.