Mitel Deutschland GmbH 68635RFP36U-01 ユーザーズマニュアル
SIP-DECT OM System Manual
40
The SIP-DECT system allows logging into and out of different DECT phones with a personalized user
account, import of user data from an external provisioning server, automatic subscription of new DECT
phones, and control of subscription-specific system functions from DECT phones.
account, import of user data from an external provisioning server, automatic subscription of new DECT
phones, and control of subscription-specific system functions from DECT phones.
See the SIP-DECT DECT Phone Sharing and Provisioning Guide for details on this feature.
3.25 USER MONITORING
The OMM monitors the status of the user’s DECT phone to verify the user’s availability to receive calls or
messages. By default, passive and active user monitoring is disabled.
messages. By default, passive and active user monitoring is disabled.
In addition to the standard request, response and notification messages, the OMM generates alarm
triggers if a user becomes unavailable. The alarm triggers can be consumed by the OM IMA, the OM
Locating application, or another application using OM AXI. If a user becomes available again, the OMM
sends an additional alarm trigger to indicate the change in status.
triggers if a user becomes unavailable. The alarm triggers can be consumed by the OM IMA, the OM
Locating application, or another application using OM AXI. If a user becomes available again, the OMM
sends an additional alarm trigger to indicate the change in status.
User status information is available via OM AXI and OMP.
For a detailed description of the “User monitoring” feature see section 7.29.
3.26 SIP-DECT XML TERMINAL INTERFACE
The SIP-DECT XML terminal interface allows external applications to provide content for the user on the
DECT phones display and much more. The list of potential applications is endless. The interface is
derived from the XML API for Mitel SIP Phones and coexists with the OM AXI features e.g. text
messaging.
DECT phones display and much more. The list of potential applications is endless. The interface is
derived from the XML API for Mitel SIP Phones and coexists with the OM AXI features e.g. text
messaging.
Partners can get access to the interface specification /37/ by registering for the A2P2 program.
To call a certain URI there are a number of hooks available for the Mitel 600 DECT phones which can be
put on a programmable key or can be called from a menu. You can activate the predefined XML hooks
via the OMM Web service (see section 5.9.4) or the OMP (see section 6.12.6).
put on a programmable key or can be called from a menu. You can activate the predefined XML hooks
via the OMM Web service (see section 5.9.4) or the OMP (see section 6.12.6).
You can also activate the XML hooks through the Configuration over Air (CoA) feature; see section 7.23
for more information.
for more information.
Please note:
From SIP-DECT release 3.1 on, behavior for XML objects has been added or
changed (see SIP-DECT XML terminal interface specifications “PA-001008-05-00” and
“req-0715” (version 0.21) for more details).
“req-0715” (version 0.21) for more details).
3.26.1 FEATURE ACCESS CODES TRANSLATION
Many PBXs allow the control of PBX supplementary services by dialing specific numbers called feature
access codes (FAC).
access codes (FAC).
SIP-DECT supports the XML application “Feature Access Codes Translation” to avoid any conflict to
SIP-DECT feature access codes or digit treatment rules with PBX feature access codes.
SIP-DECT feature access codes or digit treatment rules with PBX feature access codes.
If “Feature Access Codes Translation” is activated, SIP-DECT users can chose “FAC” menu on the
Mitel 600 or Mitel 142d DECT phones in any call state and enter the feature code en-bloc. The input is
sent to the PBX (Application server) within a URI request.
Mitel 600 or Mitel 142d DECT phones in any call state and enter the feature code en-bloc. The input is
sent to the PBX (Application server) within a URI request.