Avaya DECT Messenger Fundamentals User Manual
DECT Messenger Fundamentals
Avaya Communication Server 1000
NN43120-120, 04.02
7.5
March 2012
©
2012 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves the
right to make changes and corrections to the information in this
document without the obligation to notify any person or organization of
such changes.
Documentation disclaimer
“Documentation” means information published by Avaya in varying
mediums which may include product information, operating instructions
and performance specifications that Avaya generally makes available
to users of its products. Documentation does not include marketing
materials. Avaya shall not be responsible for any modifications,
additions, or deletions to the original published version of
documentation unless such modifications, additions, or deletions were
performed by Avaya. End User agrees to indemnify and hold harmless
Avaya, Avaya's agents, servants and employees against all claims,
lawsuits, demands and judgments arising out of, or in connection with,
subsequent modifications, additions or deletions to this documentation,
to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web
sites referenced within this site or documentation provided by Avaya.
Avaya is not responsible for the accuracy of any information, statement
or content provided on these sites and does not necessarily endorse
the products, services, or information described or offered within them.
Avaya does not guarantee that these links will work all the time and has
no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on its Hardware and Software
(“Product(s)”). Refer to your sales agreement to establish the terms of
the limited warranty. In addition, Avaya’s standard warranty language,
as well as information regarding support for this Product while under
warranty is available to Avaya customers and other parties through the
Avaya Support Web site:
you acquired the Product(s) from an authorized Avaya reseller outside
of the United States and Canada, the warranty is provided to you by
said Avaya reseller and not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE,
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED
FROM ANYONE OTHER THAN A V A Y A, AN A V A Y A AFFILIA TE OR AN
AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE
USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY
INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR
AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF
YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER
REFERRED TO INTERCHANGEABL Y AS “YOU” AND “END USER”),
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE
http://support.avaya.com. Please note that if
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, or Hardware
provided by Avaya. All content on this site, the documentation and the
Product provided by Avaya including the selection, arrangement and
design of the content is owned either by Avaya or its licensors and is
protected by copyright and other intellectual property laws including the
sui generis rights relating to the protection of databases. You may not
modify, copy, reproduce, republish, upload, post, transmit or distribute
in any way any content, in whole or in part, including any code and
software unless expressly authorized by Avaya. Unauthorized
reproduction, transmission, dissemination, storage, and or use without
the express written consent of Avaya can be a criminal, as well as a
civil offense under the applicable law.
Third-party components
Certain software programs or portions thereof included in the Product
may contain software distributed under third party agreements (“Third
Party Components”), which may contain terms that expand or limit
rights to use certain portions of the Product (“Third Party Terms”).
Information regarding distributed Linux OS source code (for those
Products that have distributed the Linux OS source code), and
identifying the copyright holders of the Third Party Components and the
Third Party Terms that apply to them is available on the A vaya Support
Web site:
Preventing Toll Fraud
“T oll fraud” is the unauthorized use of your telecommunications system
by an unauthorized party (for example, a person who is not a corporate
employee, agent, subcontractor, or is not working on your company's
behalf). Be aware that there can be a risk of Toll Fraud associated with
your system and that, if Toll Fraud occurs, it can result in substantial
additional charges for your telecommunications services.
Avaya Toll Fraud Intervention
If you suspect that you are being victimized by T oll Fraud and you need
technical assistance or support, call Technical Service Center Toll
Fraud Intervention Hotline at +1-800-643-2353 for the United States
and Canada. For additional support telephone numbers, see the Avaya
Support Web site:
vulnerabilities with Avaya products should be reported to Avaya by
sending mail to: securityalerts@avaya.com.
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation and Product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its affiliates, or other third
parties. Users are not permitted to use such Marks without prior written
consent from Avaya or such third party which may own the Mark.
Nothing contained in this site, the Documentation and Product(s)
should be construed as granting, by implication, estoppel, or otherwise,
any license or right in and to the Marks without the express written
permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners,
and “Linux” is a registered trademark of Linus Torvalds.
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support Web site:
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems
or to ask questions about your Product. The support telephone number
is 1-800-242-2121 in the United States. For additional support
telephone numbers, see the Avaya W eb site: http://support.avaya.com.
http://support.avaya.com/Copyright.
http://support.avaya.com. Suspected security
http://support.avaya.com.
2 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Contents
Chapter 1: New in this release...........................................................................................
Features....................................................................................................................................................
Revision history.........................................................................................................................................
Chapter 2: Avaya DECT Messenger Administrator Guide...............................................
Preface......................................................................................................................................................
Avaya DECT Messenger overview...........................................................................................................
What is Avaya DECT Messenger.....................................................................................................
Modules overview.............................................................................................................................
eCONFIG basic concepts.................................................................................................................
DECT Messenger concepts.............................................................................................................
Maintaining DECT Messenger using eCONFIG........................................................................................
Starting the eCONFIG......................................................................................................................
eCONFIG main window....................................................................................................................
Managing devices............................................................................................................................
Managing groups..............................................................................................................................
Managing group members...............................................................................................................
Managing users................................................................................................................................
Adding a DECT device to the Messenger system....................................................................................
Chapter 3: DECT Messenger Customer Engineer Manual..............................................
Preface......................................................................................................................................................
About the manual.............................................................................................................................
Guidelines for maintenance and administration of a server or specialized computer......................
DECT Messenger overview......................................................................................................................
Avaya DECT Messenger functional description...............................................................................
Modules overview.............................................................................................................................
Linking modules...............................................................................................................................
DECT Messenger in a WAN or MAN network...........................................................................................
Licensing...................................................................................................................................................
CSTA connection (link) license.........................................................................................................
SOPHO CTI module License Manager licenses..............................................................................
Detailed module descriptions....................................................................................................................
eKERNEL.........................................................................................................................................
eDMSAPI..........................................................................................................................................
eIO....................................................................................................................................................
eSMTP.............................................................................................................................................
eSMTP_Server.................................................................................................................................
eAPI..................................................................................................................................................
eWEB...............................................................................................................................................
eCONFIG.........................................................................................................................................
eGRID..............................................................................................................................................
eTM..................................................................................................................................................
eLOG................................................................................................................................................
eCAP................................................................................................................................................
eESPA..............................................................................................................................................
7
7
7
9
9
10
10
12
14
16
19
19
20
22
31
37
42
48
53
53
54
54
56
56
58
61
64
65
65
68
69
69
70
70
70
71
71
72
73
73
73
74
74
74
DECT Messenger Fundamentals March 2012 3
eLOCATION.....................................................................................................................................
eSMS................................................................................................................................................
eSNMP.............................................................................................................................................
eFR...................................................................................................................................................
Web administrator............................................................................................................................
What is required to run DECT Messenger................................................................................................
Hardware Requirements..................................................................................................................
Software Requirements....................................................................................................................
DMC Configuration...........................................................................................................................
DATABASES in DECT Messenger............................................................................................................
Supported Database types...............................................................................................................
How to set up the Databases...........................................................................................................
Installing and getting started.....................................................................................................................
Stopping IIS WEB Services..............................................................................................................
Installing DECT Messenger..............................................................................................................
Getting Started.................................................................................................................................
Using eCONFIG........................................................................................................................................
Using eCONFIG (Local) on the DECT Messenger Server PC.........................................................
Using eCONFIG (Remote) on remote PC (client) in the Network....................................................
Using eTM.................................................................................................................................................
eDMSAPI Inbound....................................................................................................................................
Incoming Alarm (IA) from DMC........................................................................................................
Incoming Alarm (IA) from IP DECT..................................................................................................
Incoming Confirmation (IC)..............................................................................................................
Parameters required to set an alarm................................................................................................
SET/RESET structure......................................................................................................................
eLOCATION..............................................................................................................................................
How it works.....................................................................................................................................
eLOCATION Module in eCONFIG....................................................................................................
Connecting National Instruments modules...............................................................................................
General.............................................................................................................................................
Hardware Installation........................................................................................................................
Software Installation.........................................................................................................................
Understanding Security features...............................................................................................................
Session Guarding.............................................................................................................................
Watchdog.........................................................................................................................................
Using eBackup..........................................................................................................................................
Setting up e-mail integration (eSMTP_Server/eSMTP)............................................................................
General.............................................................................................................................................
Using eSMTP Server................................................................................................................................
How eSMTP Works..........................................................................................................................
Installing IIS......................................................................................................................................
Configuring eSMTP_Server in eConfig............................................................................................
Configuring IIS for DECT Messenger...............................................................................................
Using eSMTP............................................................................................................................................
Sending SMS messages...........................................................................................................................
eSMTP.............................................................................................................................................
74
74
75
75
75
76
76
77
77
80
80
81
81
81
82
83
90
90
92
93
94
94
95
96
96
103
107
108
109
110
110
113
114
119
119
119
126
130
130
131
131
134
134
135
138
139
139
4 DECT Messenger Fundamentals March 2012
eASYNC...........................................................................................................................................
V.24 - RS232 connections (eCAP, eESPA)...............................................................................................
eCAP................................................................................................................................................
eESPA..............................................................................................................................................
Using Import/Export menu........................................................................................................................
eLOG.........................................................................................................................................................
OUTrqs.csv file.................................................................................................................................
How to use the Files.........................................................................................................................
Checking diagnostics................................................................................................................................
General.............................................................................................................................................
Logging.............................................................................................................................................
Module Window................................................................................................................................
eKERNEL Window...........................................................................................................................
Simulation Options in a Module........................................................................................................
eKERNEL Service Options...............................................................................................................
Index.....................................................................................................................................
139
142
143
143
144
145
150
155
155
155
156
158
163
164
164
165
DECT Messenger Fundamentals March 2012 5
6 DECT Messenger Fundamentals March 2012
Chapter 1: New in this release
Features
There are no new features introduced with this release.
Revision history
March 2012 Standard 04.02. This document is up-issued
to support Avaya Communication Server
1000 Release 7.5, and contains additional
changes relating to updates in Release 4.1
of the Messenger software.
November 2010 Standard 04.01. This document is up-issued
to support Avaya Communication Server
1000 Release 7.5.
June 2010 Standard 03.01. This document is up-issued
to support Avaya Communication Server
1000 Release 7.0.
May 2009 Standard 02.01. This document is up-issued
to support Communication Server 1000
Release 6.0.
October 2008 Standard 01.06 This document is up-issued
to support Communication Server 1000
Release 5.5, and contains additional
changes relating to updates in Release 4 of
the Messenger software.
September 2008 Standard 01.02. This document is up-issued
to support Communication Server 1000
Release 5.5, and contains changes relating
to updates to the Messenger software.
May 2008 Standard 01.01 This document is issued to
support Communication Server 1000
Release 5.5. Some of the information in this
DECT Messenger Fundamentals March 2012 7
New in this release
new document was previously in DECT
Fundamentals, NN43120-114.
8 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Chapter 2: Avaya DECT Messenger
Administrator Guide
This chapter contains information on the following topics:
• Avaya DECT Messenger overview on page 10
- What is Avaya DECT Messenger on page 10
Modules overview on page 12
-
- eCONFIG basic concepts on page 14
- DECT Messenger concepts on page 16
Maintaining DECT Messenger using eCONFIG on page 19 eCONFIG Section
•
- Starting the eCONFIG on page 19
eCONFIG main window on page 20
-
- Managing devices on page 22
Managing groups on page 31
-
- Managing group members on page 37
- Managing users on page 42
Adding a DECT device to the Messenger system on page 48
•
Preface
This chapter contains an overview of Avaya DECT Messenger in general, and information for
users of the eCONFIG module specifically . It contains important information on the underlying
structure of the eCONFIG module, and on creating, deleting, and making changes to Users,
Devices, and Groups.
This chapter does not cover all of the menus and associated menu items that are available in
the eCONFIG module. Menus and associated menu items that are not covered require detailed
technical background knowledge.
For information about the other menu parameters in the eCONFIG module, or information for
any of the other modules in Avaya DECT Messenger, refer to Avaya DECT Messenger
Installation and Commissioning, NN43120-301.
DECT Messenger Fundamentals March 2012 9
Avaya DECT Messenger Administrator Guide
Avaya DECT Messenger overview
DECT Messenger provides a software tool, the eCONFIG, for making changes to the
configuration. The eCONFIG is on either the same PC as the DECT Messenger software, or
on another PC in the TCP/IP network. After you run eCONFIG on another PC, the number of
items you can change is limited.
What is Avaya DECT Messenger
DECT Messenger is a software platform that allows message generation, message routing,
and message protocol conversion. Figure 1: Avaya DECT Messenger on page 10 shows the
inputs and outputs of DECT Messenger.
Figure 1: Avaya DECT Messenger
Message input
The following input can generate messages in DECT Messenger:
• ESPA 4.4.4 pager protocol: DECT Messenger can receive pager messages from ESPA
4.4.4-compatible pager equipment.
• RS232/V.24 serial input: many protocols are supported as input for generating a
predefined message or a user defined message.
• DECT handset with E2 (Low Rate Messaging Services [LMRS]) messaging.
• E-mail to the DECT Messenger server PC: send a message from e-mail to a telephone
set or SMS to cell phone or any other output on DECT Messenger.
• Switches (push button, toggle): message alerts generated by alarm contacts, door
contacts, fire contacts, and so on.
10 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
• Analogue voltage/current levels: this form of message generation is used to guard
industrial equipment. For example, equipment output messages can indicate pressure,
temperature, and so on.
• Web interface from which you generate messages manually.
• Programs you write that communicate (using TCP/IP socket) with DECT Messenger:
DECT Messenger provides a port on TCP/IP that is open to receive input data from this
type of unique program.
Message output
DECT Messenger supports the following output:
• DECT E2 messages (up to 160 characters)
Although DECT Messenger supports up to 160 characters, the DECT equipment or the
handset can limit this number to 128, or even 48, characters. If the handset supports only
48 characters, the message is broken into sections and sent in parts to the handset.
• Messages sent to Ergoline or DECT extensions during ringing and after a call is connected
Avaya DECT Messenger overview
Each device type can specify message length. Messages that are too long to be displayed
are broken into sections suitable for the display devices.
• SMS messages to cell phones
DECT Messenger can send SMS messages to cell phones. A modem or a box that
behaves like an actual cell phone with a Subscriber Identity Module (SIM) card can be
the interface to the cell phone provider.
This option is mainly used as an alternative device. You can forward the message to a
cell phone if a message to a DECT handset is not acknowledged.
• E-mail messages
DECT Messenger can send e-mail using Simple Mail T ransfer Protocol (SMTP) to any e-
mail server.
• Digital output to control relays or similar equipment
In the event of an alarm, use the relay contacts to control equipment such as lamps, door-
contacts or hooters. Contacts are used as alternative devices (overflow) in case a
message is not confirmed.
• ESPA 4.4.4 pager protocol
DECT Messenger can send messages to paging equipment using the ESPA 4.4.4
protocol.
DECT Messenger Fundamentals March 2012 11
Avaya DECT Messenger Administrator Guide
Modules overview
DECT Messenger consists of separate modules. There are three main groups of modules:
• Core—core components of the software, including security and maintenance tools.
• Input/Output modules—used for sending or receiving messages to or from supported
devices.
• Add-Ons—optional expansion modules adapted for specific customer needs.
• Web Administrator—a web application that enables web-based access to a limited set of
functions.
The following sections provide an overview of the modules. Detailed module descriptions are
provided in Avaya DECT Messenger Installation and Commissioning, NN43120-301.
Core modules
The following core modules are available:
• eKERNEL
The eKERNEL is the core software in the system and must always be present. eKERNEL
is between the incoming and the outgoing modules and must always be running. The
system does not operate if eKERNEL is absent or nonfunctional.
• eCONFIG/eGRID
The eCONFIG module is used to set up and configure the system, messages, and
message flows. The eCONFIG is a user-friendly variant of the eGRID.
• eGUARDIAN
The eGUARDIAN is a integrated into eKERNEL and is used in conjunction with an input
module that receives data at regular intervals. The eGUARDIAN module checks the data
input at regular intervals. If the input is not received within a specified time period, the
eGUARDIAN module sends a message indicating that an input is down.
• eBACKUP
The eBACKUP module takes care of making a backup of the configuration database at
regular intervals. -
• eTM
The eTM (T ask Manager) is a background module that automatically starts up other DECT
Messenger modules in case they are down. Most of the core modules are typically
deployed on the server PC. Exceptions are eCONFIG, which can optionally be deployed
and used from a client PC (with limited configuration capabilities) and eTM, which is
recommended to run on every DECT Messenger PC, client or server.
12 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Incoming and outgoing modules
There is a wide range of incoming and outgoing modules available. They all communicate with
the eKERNEL module. Each module has a specific incoming or outgoing function. This means
that the incoming modules can receive messages and outgoing modules can send messages.
provides an overview of the modules.
Table 1: Incoming and outgoing Modules
Module Name Function Incoming Outgoing
Avaya DECT Messenger overview
eCAP V.24/RS232 interface and protocol
converter.
eESPA Input/Output module for the
connection to pager interfaces.
eAPI Input device for custom-made
programs.
eIO Digital and analogue inputs and
digital outputs (contacts and
switches).
eWEB Web interface. Yes eSMTP-server Receiving e-mail messages. Yes eSMTP (client) Sending e-mail messages. - Yes
eDMSAPI Sending and receiving E2-DECT
messages using the CSTA interface.
eASYNC Asynchronous modem interface to
cell phone SMS provider, or to wide
area paging system.
Yes -
Yes Yes
Yes -
Yes, analogue
levels and
digital levels
(contacts)
Yes, receiving
E2-DECT
messages
- Yes
Yes, switches
Yes, sending
E2-DECT
messages
eLOCATION Location detection after a call is made
from a DECT handset or when LRMS
(E2) is sent from DECT handset.
eVBVoice Interactive Voice Responds used to
various message types
eSNMP Receive an SNMPv1 or SNMPv2c
trap from an SNMP sending process
or equipment
eSMS Send SMS message to a mobile
phone. Inbound SMS can be used to
confirm alarm
DECT Messenger Fundamentals March 2012 13
In addition to
the eCSTA
module.
Yes Yes
Yes
Yes (to
confirm)
Yes
Avaya DECT Messenger Administrator Guide
Add-on modules
The add-ons are input/output modules tailored to specific customer needs. They are not
covered by the standard product documentation.
• Web Administrator
The Web Administrator is a web-based user interface that offers access to certain
configuration functions, sending messages to users and groups, reporting functions, and
so on.
• Logging
The eKERNEL has built-in logging functionality for technical purposes known as eLOG.
The log files are located in the following directory: [INSTALLDIR]\Logs where
[INST ALLDIR] is the installation directory . The default installation directory is: C:\Program
Files\Avaya\Avaya DECT Messenger\.
eCONFIG basic concepts
The system configuration is stored in a database. You use the eCONFIG module to make
changes to the configuration. This section explains how the eCONFIG module uses the
database.
You can use the eCONFIG on the local DECT Messenger server PC. You can also install the
eCONFIG on a remote PC to do remote configuration maintenance. Database handling is
different for local and remote situations.
eCONFIG (local) on the DECT Messenger server PC
After the eCONFIG is installed on the DECT Messenger server PC, the database is handled
as shown in eCONFIG (local) on the server PC.
Figure 2: Database handling after eCONFIG is on local PC
After you open the eCONFIG for the first time, the eCONFIG makes a copy of the operational
configuration database in DECT Messenger . This copy is stored locally on the server PC where
14 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Avaya DECT Messenger overview
eCONFIG is running. If you make configuration changes using the eCONFIG, these changes
are stored in the local working copy of the database in the eCONFIG. To make these changes
active, you must close down all the DECT Messenger modules and then close the eCONFIG
using the File > Exit menu. The operational database is deleted automatically, and the
database from the eCONFIG is saved into the DECT Messenger directory and becomes the
new operational database. After you restart the modules that you closed down, the new
configuration becomes active.
After you make changes in Users, Groups, or Devices, the changes are saved in the eCONFIG
database, as well as in the operational database, and so are immediately activated.
Note:
While making configuration changes with eCONFIG, ensure that no one else is making
changes in the operational database. If there are other pending changes, an error may occur
after you shut down the eCONFIG and attempt to apply the configuration changes.
Note:
If there are monitored devices in the active configuration, and one of these devices initiates
a follow-me, the diversion information is stored in the active database. Therefore, you cannot
restore the eCONFIG database, and all the changes that you make are lost (except for the
changes in Users, Groups, and Devices).
eCONFIG (remote) on remote PC (client) in the network
After the eCONFIG is installed on a remote PC (not the DECT Messenger server PC) in the
network, the database is handled as shown in
installed on a remote PC on page 15.
Figure 3: Database handling after eCONFIG is installed on a remote PC
After you open the eCONFIG for the first time at the remote PC, a copy is made of the
configuration database of DECT Messenger. This copy is stored on the remote PC where the
eCONFIG is running. You cannot make system configuration changes in this database, but
you can make changes in Users, Groups, and Devices.
After you make changes in Users, Groups, or Devices, these changes are stored in the
eCONFIG database on your PC. The changes are also immediately stored in the operational
database on the DECT Messenger (server) PC and are, therefore, immediately active.
Figure 3: Database handling after eCONFIG is
DECT Messenger Fundamentals March 2012 15
Avaya DECT Messenger Administrator Guide
Note:
If there is more than one eCONFIG active at the same time, on different PCs, the individual
eCONFIG databases are not updated/synchronized after a user makes a change in one
eCONFIG. Only the database in the eCONFIG module where the change is made is
updated, together with the operational database. Changes made in Groups using the eWEB
interface are not written into the databases of the eCONFIG modules — these changes are
only written into the operational database.
Note:
The database is never saved to the server PC when you work on a remote PC.
Restarting eCONFIG
When you start eCONFIG, the program may find a working database in the local maintenance
directory . If so, eCONFIG asks you whether you want to continue with this database or retrieve
a fresh copy from the operational database.
Figure 4: Message box asking which database to use
Avaya recommends choosing No to make a fresh copy of the operational database and ensure
that there is no database inconsistency.
DECT Messenger concepts
DECT Messenger receives alarms (messages) from input modules. Understanding how these
incoming alarms are processed is an important step towards understanding the eCONFIG
menu structure.
16 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Avaya DECT Messenger overview
Figure 5: Alarm processing structure on page 17 shows the relation among the modules and
how messages are processed.
Figure 5: Alarm processing structure
Alarms originate at an input program (input module). An incoming alarm carries an alarm
identifier and a group identifier. The alarm identifier must match an identifier in the Alarm
Properties functional block, which specifies how the alarm is processed (priority , time intervals,
and so on). The group identifier determines the final destination. The incoming group identifier
must match a group identifier in the Groups functional block, which contains one or more output
destinations (that is, the group members). The group members are the devices assigned to a
Group.
Figure 6: eCONFIG on page 17 shows the main window of eCONFIG with an example of an
input module (the application programming interface [eAPI]). The eAPI input module is found
in eCONFIG in the Modules > eAPI menu. Select the instance of the module as it appears on
your screen (in this example, the menu selection is Modules > eAPI > API - area Area 1).
Each input module displays different properties.
Figure 6: eCONFIG
The following explanations relate to the blocks in Maintaining DECT Messenger using
eCONFIG on page 19:
• Input Module
The Alarm carries two dif ferent identifiers from the input module to the actual Kernel: the
alarm identifier and the group identifier. The identifier provides the message for the output
device.
DECT Messenger Fundamentals March 2012 17
Avaya DECT Messenger Administrator Guide
You can set or change the properties of an input module.
• Alarm Properties
The alarm identifier is used to determine how the alarm is processed. Specifications are
in the All Alarms menu (for more information, see
page 20). Examples of the alarm properties are Priority, Repeat Interval Time, and so
on.
Note:
There are alarm identifiers predefined in the system configuration. Therefore, it is not
necessary to define all alarm identifiers. For information on available alarm properties,
see DECT Messenger Installation and Commissioning, NN43120-301.
• Group
The group identifier that originates at the input module determines the group to which the
alarm must be sent. In Maintaining DECT Messenger using eCONFIG on page 19, the
group identifier is 00001. The group identifier can be a group name or any string of
characters.
• Group Member -- Device
eCONFIG main window on
The group is composed of group members, and each group member is an actual device
(for example, an Ergoline, a DECT handset, or an e-mail address). The output device can
be a member of more than one group. For example, a DECT handset with extension
number 2000 can be assigned to more than one group as a group member. In
Figure 6:
eCONFIG on page 17, Group 00001 has two devices (2000 and 1010). Device 2000 uses
the output program eDMSAPI, which means that Device 2000 is a DECT handset using
E2 messaging.
• Output Module - Output Program
An output device makes use of an output module, also referred to as an output program.
You can specify settings in the output module to process the output alarm.
Refer to the following sections for instructions on creating, deleting, and changing parameters
for Groups, Users, and Devices:
•
Managing devices on page 22
• Managing groups on page 31
• Managing group members on page 37
• Managing users on page 42
18 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Maintaining DECT Messenger using eCONFIG
Maintaining DECT Messenger using eCONFIG
This chapter explains the eCONFIG user interface and available functionality.
Starting the eCONFIG on page 19
•
Starting the eCONFIG
The procedures below describe the steps necessary to start the eCONFIG module.
Before starting eCONFIG:
1. Ensure that DECT Messenger is correctly installed and already preconfigured by a
technician.
2. Ensure that the Kernel software is installed and running.
If you are on a remote PC (not the server PC), ensure that the main server is booted.
If you are using the server PC, an icon appears in the Windows task bar to indicate
that the eKERNEL is running.
If other modules are also running, an icon is displayed for each (for example, the
eDMSAPI).
To launch the eCONFIG configuration utility:
1. Use the shortcut available in the Start Menu:
Start > Programs > Avaya DECT Messenger > eCONFIG
2. Enter your login information.
Log in with the username and password provided by your system manager. If you
are the system manager, and you have not changed any usernames and passwords
yet, log in with the default login. The default login is admin (username), admin
(password).
3. Select the database.
Note:
The eCONFIG asks you which database you want to use. Ensure that you read
the information on database handling in eCONFIG basic concepts on page 14
before proceeding.
DECT Messenger Fundamentals March 2012 19
Avaya DECT Messenger Administrator Guide
You have two options for database selection:
• Click YES: the eCONFIG uses the database that is still available in the
eCONFIG module from a previous session. This database can be an old
database.
• Click NO: the eCONFIG makes a fresh copy of the operational database from
the DECT Messenger server . Avaya recommends that you choose this option.
It ensures that you have a copy of the actual operational database. If you work
on a remote PC, you must select this option to avoid conflicts with changes
made from other locations by other users.
4. The eCONFIG main window opens.
Detailed information is provided in
eCONFIG main window
The main eCONFIG window is shown in eCONFIG main window.
eCONFIG main window on page 20.
Figure 7: eCONFIG main window
Note:
The contents of the eCONFIG window are different for each user or for each system
configuration. eCONFIG main window shows all the menu items that are possible.
20 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Maintaining DECT Messenger using eCONFIG
The following menu items are available:
• Import/Export menu: provides the option to import configuration data into tables in the
configuration database, or to export configuration data from the configuration database
tables. The file type is .csv.
Note:
Do not use the Import/Export menu items if you do not have detailed configuration
database knowledge. If you make mistakes, it can corrupt your system.
• License information: provides information about the current licenses that are active in your
DECT Messenger. You cannot make license changes from this menu.
• Site Site 1: indicates the location of the eKERNEL (core) software. There is typically only
one eKERNEL in a system, so there is only one site displayed. (In exceptional cases,
there can be more than one site, but only one eKERNEL (that is, one site) can be active
at any given instant.
• Areas: indicates the subdivisions in a site. Areas are used only if you have a connection
from your DECT Messenger to more than one DECT Mobility Card (DMC) with DECT.
For each connection from your DECT Messenger to a DMC system or an IP DECT
system, you must specify a different area. Use a number to identify the area. The area
number is used in the various modules in DECT Messenger. Note that in almost all
installations you have only one area.
• Modules: provides an overview of all the modules in the Messenger.
Note:
The list of modules can differ for each user . The list of modules is displayed only if you
have view/edit rights.
Note:
The All TCP Clients menu item is not a module. All TCP Clients provides information
about the module TCP/IP connections. You cannot make any configuration changes
from this menu.
• All Alarms: provides a list of all alarm specifications available in Messenger.
Note:
The alarm specification is linked to an input module. Therefore, to create a new alarm
specification, you must use the Module menu. From the All Alarms menu, you can make
changes only to existing alarm specifications.
• All Users: defines all users. Note that there are two separate groups of users: eCONFIG
users and eWEB users. If you have sufficient rights, you can change user settings and
add new users from this menu.
• Groups and devices: use this menu to make changes in group and device characteristics.
Y ou cannot create new groups here because a group is always uniquely linked to an input
DECT Messenger Fundamentals March 2012 21
Avaya DECT Messenger Administrator Guide
module. You can, however, create new devices here because a device does not have a
unique relationship with only one group.
• Holiday: use this menu to specify the public holidays. This information is used for the
group members. You enable the specified holidays in the properties for each group
member.
Note:
If you are using the eCONFIG on a remote PC, you cannot make changes to property
settings. You can change only Users, Groups, and Devices.
Managing devices
The following sections provide information that explain the following DECT Messenger tasks:
• creating a new device
• changing the parameters of an existing device
• editing device parameters
The following are examples of device types in DECT Messenger:
• DNR in the DMC
• Directory Number (DN) in SIP DECT
• e-mail address
• cell phone number (for SMS)
• relay contacts
You must know the properties of each device type relative to the equipment that hosts it (that
is, device properties in the DMC, in the Mail Server, and so on).
Note:
Task procedures are explained in the following sections. T o carry out these procedures, you
must have sufficient user rights to access all the menus that are used in these procedures.
If you do not have sufficient rights, you cannot see the menu options described, or you see
them but cannot make changes.
Creating a new device
Complete the following steps to create a new device.
Creating a new device
1. Access the eCONFIG Groups and Devices menu.
• Open eCONFIG.
22 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
• Expand the Groups and Devices menu by clicking the + to the left of it.
2. Add a new device.
• Right-click the All Devices parameter.
• Select New Device as shown in the following example:
3. Set parameters for the new device.
Note the following when setting parameters:
Maintaining DECT Messenger using eCONFIG
• A red bullet before an item indicates that the item is mandatory.
• Some items contain default parameter values.
• Avaya recommends that you use the Browse option, when present, to define
a location, rather than typing an entry.
The parameters are described in Device parameters on page 25.
4. Confirm your choices.
Click OK and follow the instructions on screen.
5. Assign the new device to a group (optional).
DECT Messenger Fundamentals March 2012 23
Avaya DECT Messenger Administrator Guide
Select All Groups from the Groups and Devices menu, or Group from the input
module menu of your choice.
Changing device parameters
Complete the following steps to change device parameters.
Changing device parameters
1. Access the eCONFIG Groups and Devices menu.
• Open eCONFIG.
• Expand the Groups and Devices menu by clicking the + to the left of it.
2. Open the All Devices information window.
Left-click the All Devices parameter. The following window appears:
3. Select the device of your choice.
• In the right panel, browse in the list of devices in DECT Messenger.
• Double-click the device that you want to edit. The Properties window of the
device opens:
24 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Maintaining DECT Messenger using eCONFIG
4. Change the parameters.
Click the name of the property you want to change. If you edit the parameters, note
the following:
The parameters are described in
5. Confirm your choices.
Click OK and follow the instructions on the screen, if applicable.
Deleting a device
To delete a device, follow
button. DECT Messenger asks you to confirm the action. After you confirm the action, the
device is deleted immediately.
Device parameters
As in previous sections, you can specify the following parameters for a device:
• Output Program
• You cannot change the Output Program, the Site ID, the Area ID, or the
Device ID.
• Avaya recommends that you use the Browse option, when present, to define
a location, rather than typing an entry.
Device parameters on page 25.
Changing device parameters on page 24; at Step 4, click the Delete
This field specifies the output program that processes a request. A device can be defined
in more than one module. The indicated application threads the message using the
capabilities of the infrastructure. The eDMSAPI can, for example, send E2 messages
DECT Messenger Fundamentals March 2012 25
Avaya DECT Messenger Administrator Guide
(non-voice-call to extensions such as DECT C4050 and C4060). The supported output
programs are currently:
- eASYNC for sending SMS to PROXIMUS, or KPN and PAGING to BELGACOM.
- eDMSAPI for sending E2 messages to DECT handsets that support E2 (LRMS).
- eESPA for sending messages to an ESPA 4.4.4 interface (pager equipment).
- eIO for enabling/disabling discrete output contacts.
- eSMTP for sending e-mail to an e-mail provider.
- eSMS for sending SMS messages to GSM phones.
Note:
The output program is associated with a Site ID (which is typically 1) and an Area ID.
If there is more than one entry of the same output program, each one can have a
different area. Select the correct area.
Note:
Selecting the output program is only possible when you create a new device. Always
use the Browse button to select the output program. Figure 8: Select Output Program
browser window on page 26 shows the browser window.
Figure 8: Select Output Program browser window
• Device ID
The device ID is the actual identifier of the device in the output equipment.
26 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Maintaining DECT Messenger using eCONFIG
Device ID consists of <board-id> and <index> delimited with #. For example, 04#01.
Table 2: Variable definitions
Variable Definition
<board-id> A fixed length value, in the range of 01 to 32, which
indicates the DMC card ID in a PBX.
<index> A variable length value, in the range of 00 to 509, which
indicates the index of a DECT handset subscribed to a
DMC card.
The <board-id> value is calculated differently against a system type as follows:
- For a small system, such as Option 11C, the <board-id> of a DMC card placed in
the Main Cabinet/Chassis is the same as the card slot number where the DMC card
is installed (in the range of 01 to 10). DMC card numbering in Expansion Cabinets/
Chassis continues sequentially in the range 11 to 20.
The following table illustrates Device ID numbering for a small system.
Table 3: Device ID numbering for a small system
Cabinet/Chassis Card slot <board id> Device ID
Main Cabinet or
Main Chassis +
Chassis Expander
Expansion
Cabinet or
Expansion
Chassis 1 +
Expander
1 1 01#xxx
2 2 02#xxx
… … …
9 9 09#xxx
10 10 10#xxx
1 11 11#xxx
2 12 12#xxx
… … …
9 19 19#xxx
10 20 20#xxx
- For a large system, such as Avaya Communication Server 1000E, <board-id> falls
in the range of 01 to 32, and is calculated with the formula: <board-id> = 16 *
<shelf_number> + <card_slot_number> + 1
The following table illustrates Device ID numbering for a large system.
Table 4: Device ID numbering for a large system
Shelf Card slot <board id> Device ID
0 0 1 01#xxx
DECT Messenger Fundamentals March 2012 27
Avaya DECT Messenger Administrator Guide
Shelf Card slot <board id> Device ID
0 1 2 02#xxx
… … … …
0 14 15 15#xxx
0 15 16 16#xxx
1 0 17 17#xxx
1 1 18 18#xxx
… … … …
1 14 31 31#xxx
1 15 32 32#xxx
The following table shows examples of valid device IDs.
Table 5: Example device IDs
DMC Card installed in Device ID
2nd slot on Main Cabinet on Avaya CS1000 M, handset is
subscribed with index 01
7th slot of shelf 0 on CS 1000E, handset is subscribed with
index 123
14th slot of shelf 1 on CS 1000E, handset is subscribed with
index 03
02#01
08#123
31#03
• Output program facility
The indicated application threads the message using the capabilities of the output device.
The display of extensions can differ in character length, and so on. Therefore, DECT
Messenger must know to which device type the message is being sent (for example,
C4050 or 4060 for eDMSAPI).
Use the Browse button to select the correct output program facility .
Figure 9: Device Select
Facility on page 29 shows the selection window for the eDMSAPI.
28 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Maintaining DECT Messenger using eCONFIG
Figure 9: Device Select Facility
• Description
The Description field is used to enter a description of the device. The description is used
to show information about the devices in the web interface (for example, DECT: John
Peterson).
• Pincode
The pincode is used to confirm messages using the eDMSAPI (IC). Confirmation means
that an active alarm on the device is reset from the same or another extension. To reset
the alarm using eDMSAPI (IC), the CLI of the calling extension must be entered here as
the pincode.
• Priority
Reserved for future use.
• Retry count alternative device
Retry count alternative device defines how many times the application tries to deliver
the message before switching to an alternative device (if one is defined in the list of
Alternative Devices in the Groups and Devices menu). The default value is 30.
Therefore, if an alarm has a silence interval (defined in the alarm properties) of 120
seconds, the alarm is removed for this device after one hour (and set for the alternative
device, if defined).
A value of 0 indicates that the application never tries to send the message to an alternative
device, and that the alarm is sent to the device every silence interval until the alarm is
reset by the input program, for example (a reset). A value of 1 indicates that after one
DECT Messenger Fundamentals March 2012 29
Avaya DECT Messenger Administrator Guide
attempt, the application clears the message for this device and send the message to the
alternative device, if defined.
Note:
In this second case (value=1), the switch to the alternative device is immediate (that
is, there is no silence interval between the two calls). Therefore, you must ensure that
there are no loop conditions defined in the list of alternative devices.
A value of 2 indicates that the alternative device is contacted after the second attempt.
• IO Register
This parameter is only applicable for devices that are assigned to output program
eDMSAPI.
All devices with this value set to True are monitored by the eDMSAPI to see if an E2
message is sent. After a device sends an E2 message, the message always goes to
DECT Messenger directly (and not to the destination number). Messages sent to DECT
Messenger are processed by DECT Messenger in the same way that messages from
other input devices are processed. There must be a correct specification in the eDMSAPI
inbound configuration that points to a group and an alarm. The message is sent to the
group members in the group that is assigned to the inbound configuration in the
eDMSAPI.
• Alternative devices
Use this parameter to assign one or more alternative devices to a device. After you click
this item, a panel at the right side of the window displays the list of possible alternative
devices. Select New from the menu to add an alternative device. Select Edit to make
changes in the list of alternative devices already assigned to this device.
• Remote access site
The Remote access site parameter is only applicable when you have more than one
site, and you are using the web interface. A web server (eWEB) and a device are each
assigned to only one site; if both are assigned to the same site, you can see the device
from the web interface. Devices assigned to sites other than that to which the web server
is assigned are only visible if the Remote access site parameter is set to True.
• Remote access area
The Remote access area parameter is only applicable when you have more than one
area, and you are using the web interface. A web server (eWEB) and a device are each
assigned to only one area; if both are assigned to the same area, you can see the device
from the web interface. Devices assigned to areas other than that to which the web server
is assigned are only visible if the Remote access area parameter is set to True.
• Comments
This field is informational only, and can contain remarks from the administrator.
30 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com
Loading...