User's Manual

Chapter 10: Module eAPI
Introduction
The module eAPI is not a real module, but rather a description of a public Application Program
Interface (API) for third-party developers who want to communicate with DECT Messenger.
This chapter is intended for developers who want to build an interface to the eKERNEL
module.
The objective of this document is to describe how developers can integrate applications with
DECT Messenger. Note that the eAPI interface has limited capabilities. An alternative to
developing your own program is to contact Avaya and request the development of an integrated
solution.
Limitations
Input program functionality only
The functionality implemented in the eAPI interface is limited to the sending of message
requests to the eKERNEL module. This process is carried out through so-called message
request (msgrqs) transactions. Therefore, third-party application programs that are created
using eAPI technology are limited to input program functionality only.
No central configuration
A second limitation in eAPI is that there currently is no support for configuration request
messages. In all other modules, there is a central configuration database, where all relevant
parameters are centrally administered. This process is normally carried out through
configuration requests (cfgrqs) from the module to eKERNEL and configuration replies (cfgrpy)
from eKERNEL to the module. As a result, third-party developers must provide their own
DECT Messenger Installation and Commissioning — Book 1 March 2012 65