AASTRA SIP-DECT (Release 3.0)- OM System Manual - Installation, Administration and Maintenance EN - Manual (Page 53)

SIP–DECT OM System Manual Release 3.0 7 OMM Web Service
Aastra depl-1624/1.0 Page: 53 (241)
- RTP (RFC 2833)
Transmit 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.
- INFO
The SIP INFO method is used to transmit DTMF tones as telephone events
(application/dftmf-relay). 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 1.3 reference /14/.
Registration traffic shaping
Allows to limit the number of simultaneous SIP registrations at startup/fail over of the OMM. If
activated, it prevents bursts of SIP registration during startup/fail over of the OMM.
•
Active : The registration traffic shaping mechanism can be switched off/on herewith.
•
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).
Supplementary Services
Call forwarding / Diversion : The handset user can (de)activate call forwarding/diversion in
the OMM via menu. In some installations the implemented call forwarding/diversion feature in
the IPBX system is in conflict with the OMM based call forwarding/diversion. Thus, the OMM
based call forwarding/diversion can be deactivated to let menu on the handset disappear.
This setting becomes active on handsets with the next DECT “Locating Registration” process
(Can be forced by switching the handset off and on again). An already activated call
forwarding is ignored if the call forwarding feature is deactivated.
Local line handling : In some installations the implemented multiple line support in the IPBX
system is in conflict with the OMM based multiple line support. Thus, the OMM based
multiple line support can be deactivated. Note, that the OMM based multiple line support is
active by default.
A deactivation of the “Local line handling” flag results in the following implications:
•
Only one line is handled for each user (exceptional SOS call 1 )
•
If a user presses the “R” key or hook-off key in a call active state a DTMF event is send to
the IPBX via SIP INFO including signal 16 (hook-flash). All Hook-flash events are send in
every case via SIP INFO independently from the configured or negotiated DTMF method
during call setup. All other key events are send via configured or negotiated DTMF
method.
•
The OMM based call features “Call waiting”, “Call Transfer”, “Brokering” and “Hold” are
not any longer supported.
1 The OM SOS call feature is unchanged. The initiation of a SOS call in call active state
result in the creation of a new line which handles the SOS call.