Mitel Deutschland GmbH 68635RFP36U-01 ユーザーズマニュアル
OMM Web Service
71
5.4.3.4 DTMF settings
You can set DTMF parameters in the DTMF section.
You can set DTMF parameters in the DTMF section.
•
Out-of-band: Used to configure whether DTMF Out-of-band is preferred or not.
•
Method: The OMM supports the following DTMF Out-of-band methods:
- RTP (RFC 2833)
- RTP (RFC 2833)
Transmits DTMF as RTP events according to RFC 2833 (/14/) after the payload type negotiation
via SIP/SDP. If the payload type is not negotiated, “in band” will be used automatically.
via SIP/SDP. If the payload type is not negotiated, “in band” will be used automatically.
- INFO
The SIP INFO method is used to transmit DTMF tones as telephone events (application/dtmf-relay).
This setting should be used if RFC 2833 is not supported.
This setting should be used if RFC 2833 is not supported.
- BOTH
DTMF telephones events are send according to RFC 2833 and as well as SIP INFO method.
Note:
Possibly, the other party recognizes events twice.
•
Payload type: If the Out-of-band option is enabled, this setting specifies the payload type which is
used for sending DTMF events based on section 3.1, reference /14/.
5.4.3.5 Registration traffic shaping
Registration traffic shaping parameters allow you to limit the number of simultaneous SIP registrations at
startup/fail over of the OMM. This feature is always activated because disabling it may overload the
OMM or the call server.
Registration traffic shaping parameters allow you to limit the number of simultaneous SIP registrations at
startup/fail over of the OMM. This feature is always activated because disabling it may overload the
OMM or the call server.
Some providers use a keep-alive mechanism based on SIP registration renewals for remote endpoints
that are behind a Network Address Translator (NAT), as in an IP-Centrex solution. The keep-alive
mechanism keeps the pinhole open and ensures communication between the remote endpoint and the
Session Border Controller (SBC).
that are behind a Network Address Translator (NAT), as in an IP-Centrex solution. The keep-alive
mechanism keeps the pinhole open and ensures communication between the remote endpoint and the
Session Border Controller (SBC).
The OMM feature that spreads the registration renewals to prevent bottlenecks in large systems is not
compatible with the keep-alive mechanism. With SIP-DECT 6.0 or later, you can disable the spread
mechanism and configure a registration renewal timer to allow support for the NAT feature.
compatible with the keep-alive mechanism. With SIP-DECT 6.0 or later, you can disable the spread
mechanism and configure a registration renewal timer to allow support for the NAT feature.
•
Simultaneous registrations: The maximum number of simultaneously started registrations.
•
Waiting time: The waiting time between a registration finish and starting the next registration in ms
(0-1000ms).