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

Page 31

Advertising
background image

SIP–DECT OM System Manual Release 3.0

3 Enhanced Feature Overview

Aastra

depl-1624/1.0

Page: 31 (241)

personalized user account on different DECT handsets, import of user data from an external
provisioning server, automatically subscribe new DECT handsets or control subscription
specific system functions from DECT handsets. Refer also to the “OpenMobility Provisioning”
user guide for details see /27/.

SIP–DECT XML terminal interface

The SIP–DECT XML terminal interface allows external applications to provide content for the
user on the DECT handsets display and much more. The list of potential applications is
endless. The interface is derived from the XML API for Aastra SIP Phones and coexists with
the OM AXI features e.g. text messaging.

Partners can get access to the interface specification /34/ by registering at the A2P2
program.

To call a certain URI there are a number of hooks available for the Aastra 600d / 650c
handsets which can be put on a programmable key or can be called from a menu.

The following hooks are available:

Hook

Description

Programmable Key Menu entry

Call log

To replace the local call log

yes

yes

Redial list

To replace the local redial list

yes

yes

Server Menu

Hook to reach a server menu

yes

yes

1

Presence

Hook to reach a presence application yes

yes

Applications

List of 10 hooks; each of them can be
freely defined (App1 – App10)

yes

yes

App1 – App10 10 hooks which can be freely defined yes

no

Event Actions

URI to be called in case of
user/device events

no

2

no

2

1

The server menu is integrated in the OMM system menu. The (OMM) system menu is

available as a menu entry in the local main menu of the handset (soft key

) or directly

available by a long press of the soft key

. If no user is assigned to the handset, then the

server menu is the only available XML application hook.

2

The URI to be called is configured in the OMM via OMP. Content can be pushed towards

the handset via SIP notify. For more information please see /34/.

Integration into external management systems

To integrate the SIP–DECT system into external management systems, you can use the
following features.

Each RFP may run an SNMP agent that can be queried by SNMP management
software (see 9.16).

To further integrate into external configuration management systems, the DECT
system’s configuration is available my means of ASCII-based configuration files.
You can configure automatic import or export of configuration files from/to an
external server. For RFP configuration files see chapter 7.6.4; for user
configuration files refer to the “OpenMobility Provisioning” user guide, see /27/.

Advertising