Aastra SIP-DECT User's Guide download pdf (Page 20)

Compendium: OM SIP – DECT Solution OM AXI Specification

OM AXI Specification

This chapter describes an alternative approach to interact with the OMM: the

“OM Application XML Interface”, or short “OM AXI”. OM AXI is an application pro-

gramming interface (API) that allows external software to configure the OMM and

to use the OMM’s various interfaces, e.g. to realize interactive applications. Here

are some examples:

■ a GUI application programmed in Java with dialogues and menus to configure

some of the OMM’s features similar to the OMP.jar application;

■ a web application programmed in PHP that offers a form-based user interface,

e.g. to send and receive text messages;

■ an XML key on an Aastra 675xi or Aastra 673xi SIP system telephone that calls a

PHP page on a web server that in turn triggers some functions on the OMM.

Because of the nature of OM AXI, a complete programming example is beyond the

scope of this compendium. However, the following basic concepts apply:

■ OM AXI features an XML-based message exchange.

■ Your application sends an XML snippet, e.g. “<Open seq="1" username="omm"

password="x" />” terminated by a null character (0x00). The OMM responds

with an XML snippet “<OpenResp seq="1" ommStbState="None"

protocolVersion="35" />”.

■ The OMM offers two TCP ports for OM AXI communication by default:

– Port 12621 for unencrypted communication for debugging,

– Port 12622 for SSL encrypted communication (preferred).

■ For performance reasons, you do not need to open or close single sessions for

subsequent XML commands. You can just re-use the already opened command

stream for this.

Details are available in the “OM Application XML Interface specification (OM AXI) ”.

SIP–DECT XML terminal interface

The SIP-DECT 4.0 solution also supports the SIP–DECT XML terminal interface.

With this, external applications provide interactive content displayed on the

Aastra 600 c/d DECT handsets:

■ In the OMP Java tool, you configure XML application hooks for the DECT

handsets on the System features: XML applications menu page. With this,

e.g. the redial list or an entry in the OMM system menu is linked to an URI that

triggers a query on an external server.

■ The queried server pushes the content back to the DECT handset by means of a

SIP notify message.

Details are available in the “SIP-DECT XML terminal interface specification”.

Note

If required, contact Aastra A2P2 support for the XML specification documents.

There are also examples available that implement some of the mentioned

programming techniques.

1 2 ... 15 16 17 18 19 20 21 22 23

No comments

Aastra SIP-DECT User's Guide Page 20