DECT Messenger Fundamentals Avaya Communication Server 1000 7.5 NN43120-120, 04.
© 2012 Avaya Inc. Copyright All Rights Reserved. Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or Hardware provided by Avaya.
Contents Chapter 1: New in this release........................................................................................... 7 Features.................................................................................................................................................... 7 Revision history......................................................................................................................................... 7 Chapter 2: Avaya DECT Messenger Administrator Guide.............
eLOCATION..................................................................................................................................... 74 eSMS................................................................................................................................................ 74 eSNMP............................................................................................................................................. 75 eFR.............................................................
eASYNC........................................................................................................................................... 139 V.24 - RS232 connections (eCAP, eESPA)............................................................................................... 142 eCAP................................................................................................................................................ 143 eESPA..................................................................
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.
New in this release new document was previously in DECT Fundamentals, NN43120-114. 8 DECT Messenger Fundamentals March 2012 Comments? infodev@avaya.
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
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.
Avaya DECT Messenger overview • 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.
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.
Avaya DECT Messenger overview 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 eCAP V.24/RS232 interface and protocol converter.
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.
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.
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.
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).
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 eCONFIG main window on 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.
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.
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.
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.
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.
Maintaining DECT Messenger using eCONFIG • 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: • A red bullet before an item indicates that the item is mandatory. • Some items contain default parameter values.
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.
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: • 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. The parameters are described in Device parameters on page 25. 5. Confirm your choices.
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.
Maintaining DECT Messenger using eCONFIG Device ID consists of and delimited with #. For example, 04#01. Table 2: Variable definitions Variable Definition A fixed length value, in the range of 01 to 32, which indicates the DMC card ID in a PBX. A variable length value, in the range of 00 to 509, which indicates the index of a DECT handset subscribed to a DMC card.
Avaya DECT Messenger Administrator Guide Shelf Card slot 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.
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.
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.
Maintaining DECT Messenger using eCONFIG Managing groups Creating a new group Complete the following steps to create a new group. Creating a new group 1. Open eCONFIG. 2. Access the pop-up menu of the input module for which you want to create the new group. • Select the input module for which you want to create a new group from the Modules menu. Note: A group is always associated with an input module. You cannot create a new group in the Groups and Devices menu.
Avaya DECT Messenger Administrator Guide After you enter the parameters, note the following: • A red bullet before an item indicates that the parameter 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. Note: The group name that you enter must match the group name entered for the input module.
Maintaining DECT Messenger using eCONFIG Select the input module for which you want to change group parameters from the Modules menu. Note: A group is always associated with an input module. However, to change group parameters, you can also select a group from the Groups and Devices menu. 3. Open the group. • Expand the input module for which you want to create a new group. The instances (eAPI - area IBS 1 in this example) of the input module are displayed. • Expand the instance.
Avaya DECT Messenger Administrator Guide 5. Confirm your choices. Click OK and follow the instructions on the screen, if applicable. Deleting a group To delete a group, follow Changing group parameters on page 32; at Step 4, click the Delete button. DECT Messenger asks you to confirm the action. After you confirm the action, the group is deleted immediately. Group parameters You can specify the following group parameters for a device: • Group ID The Group ID field defines a unique identifier for a group.
Maintaining DECT Messenger using eCONFIG Note: You can use the same group name for more than one input program. You can use the same group name because the DECT Messenger software adds the input program ID to the group name, which makes the group ID unique. This group ID is created automatically after you create the group. However, you can change the group name later. The Group ID remains the same.
Avaya DECT Messenger Administrator Guide Figure 10: Group members window The section Changing group member parameters on page 40 provides information on assigning new members, editing members, and deleting members. • Group authority The Group authority field defines which users are granted access to the group to make changes using the eWEB interface, or to use the eCONFIG. If you specify ALL, all users have access to this particular group, and you do not need to enter all individual users.
Maintaining DECT Messenger using eCONFIG Figure 11: Group authority Click the New button to give a new user the authority to make changes in the group. Click the Edit button to edit a user authority. Warning: If you want to delete a user from this group, do not click Delete in the window shown in Figure 11: Group authority on page 37, because that deletes the entire group. Instead, click Edit. A window specifically for that user opens. Click Delete in this window to remove the user from the group.
Avaya DECT Messenger Administrator Guide Assigning a new member to a group 1. Open eCONFIG. Ensure that the member that you want to assign to the group is already in DECT Messenger as a device. (A group member is a device that is assigned to a group.) If the member does not exist as a device, see Creating a new device on page 22. 2. Access the Group Properties window. Use one of the following methods to access the Group Properties window: • Select Input Module from the Modules menu.
Maintaining DECT Messenger using eCONFIG A list of group members displays (the example shows only one group member: device 1010). 4. Add a new member. • Click New. The following window opens. • Click the Device ID menu item. • Use the Browse button to select the device that you want to add as a member to the group. Note: After you select a device, the area and output program are defined automatically for the member. For more information on the parameters, see Member parameters on page 41. 5.
Avaya DECT Messenger Administrator Guide Click OK and follow the instructions on the screen, if applicable. Changing group member parameters Complete the following steps to change the parameters for a group member. Changing group member parameters 1. Open the Group members window. Follow Steps 1, 2, and 3 in Assigning a new member to a group on page 37. 2. Select the group member to edit. In the right panel of the window is a list of one or more group members that are assigned to the group.
Maintaining DECT Messenger using eCONFIG A window, similar to the one in Step 4 of Assigning a new member to a group on page 37, opens, however all parameters are entered. • Remove the member by clicking the Delete button. 4. Confirm your choices. Click OK and follow the instructions on the screen, if applicable. Member parameters Member parameters are parameters that are added to a device for a specific group.
Avaya DECT Messenger Administrator Guide device, you must define it as two group members (same device): one active from 08:00– 12:00, and the other active from 13:15–17:30. • Monday . . . . Saturday This value is a Boolean value: True or False. After set to True, the member is active on that day. • Holiday This value is a Boolean value: True or False. After set to True, the member is to be present on holidays. The holidays are defined in the Holiday parameter of the eCONFIG menu.
Maintaining DECT Messenger using eCONFIG Creating a new user The following procedure describes how to create a new user. Create a new user 1. Open eCONFIG. 2. Expand the All Users menu. Note: Two submenu items are listed: eWEB and eCONFIG. eWEB contains the users for eWEB, while eCONFIG contains the users for eCONFIG. These are separate from each other, however the approach and authority mechanism is the same, so the steps in this section apply to both. 3. Access the pop-up menu.
Avaya DECT Messenger Administrator Guide The parameters are explained in User parameters on page 45. 6. Confirm your choices. Click OK and follow the instructions on the screen, if applicable. Changing user properties The following procedure describes how to change the properties for user. Changing user properties 1. Open the Group Members window. 2. Expand the All Users menu. Two menu items are available: eWEB and eCONFIG. eWEB contains the users for eWEB and eCONFIG contains the users for eCONFIG.
Maintaining DECT Messenger using eCONFIG The parameters are explained in User parameters on page 45. 6. Confirm your choices. Click OK and follow the instructions on the screen, if applicable. Deleting a user The following procedure describes how to delete a user. Deleting a user 1. Open the User Properties window. Follow Steps 1, 2, 3, and 4 of the procedure in Changing user properties on page 44. 2. Delete the user. Click the Delete button. 3. Confirm your choices.
Avaya DECT Messenger Administrator Guide access to the eWEB interface. Sharing user profiles can result in unauthenticated users, which generates alarms. • Password This field contains a password with a maximum length of ten characters. Users can change their own password using the eWEB interface. You can create new users with default passwords (for example, the same as the user identifier), and request that the users change their password at first usage.
Maintaining DECT Messenger using eCONFIG The language field contains a four-digit identifier that represents the language used for eWEB and eGRID access. The codes are those used in an iSeries 400, and are in the range of 29xx. Currently supported values in eWEB are the following: • 2909: Belgian English • 2963: Belgium Dutch • 2966: Belgium French Check the commercial documentation to determine if other languages are available.
Avaya DECT Messenger Administrator Guide In most cases, the False value is used so that the user does not have all object authority. • Security administrator The Security administrator value is set to either True or False. Set the option to True to allow the user to maintain the user settings of other users (that is, to give the user Administrator rights for all other users, including the right to change passwords, and so on).
Adding a DECT device to the Messenger system 3. Configure the new device. Make the following configuration changes: • Select eDMSAPI as the Output program. • For Device ID, enter either: Board_Number#Index_Number if you are configuring traditional DECT handsets OR a DN if you are configuring SIP DECT handsets. Example: For a DMC Card in Slot 4 of an Option 11c Cabinet, and a DECT handset subscribed to index 2, the Device ID is 04#02.
Avaya DECT Messenger Administrator Guide 5. Add a group. • In eCONFIG, open the menu Modules, and expand the eDMSAPI module by clicking the + beside it. Under the eDMSAPI module, the instances of the input module (For example, eDMSAPI - area One) are listed. • Expand this instance. The items Alarm and Group appear. • Right-click Group, and select New Group in the pop-up menu. 6. Configure the new group. Make the following configuration changes: • Populate the Group_Name.
Adding a DECT device to the Messenger system 8. Configure Inbound data call handling.
Avaya DECT Messenger Administrator Guide 52 DECT Messenger Fundamentals March 2012 Comments? infodev@avaya.
Chapter 3: DECT Messenger Customer Engineer Manual This chapter contains information on the following topics: • DECT Messenger overview on page 56 • Modules overview on page 58 • DECT Messenger in a WAN or MAN network on page 64 • Licensing on page 65 • Detailed module descriptions on page 69 • What is required to run DECT Messenger on page 76 • DATABASES in DECT Messenger on page 80 • Installing and getting started on page 81 • Using eCONFIG on page 90 • Using eTM on page 93 • eDMSAPI Inbound on page 94 •
DECT Messenger Customer Engineer Manual but does not go into detail. For detailed descriptions of modules and how they work, consult Avaya DECT Messenger Installation and Commissioning, NN43120-301. The process for installing DECT Messenger is described in Avaya DECT Messenger Installation and Commissioning, NN43120-301. Note: No legal rights can be obtained from the information in this manual.
Preface on it, is essential for every production system (servers, specialized machines, and so on). The backup procedure depends on many factors, such as the following: • volume of data • rate of data change • recovery procedure • time for backup and recovery • response of the applications There are many issues to consider for your backup process: • Automatic backups can fail • Certain other applications must be aware when the backup process is taking place, to avoid conflicts and so on.
DECT Messenger Customer Engineer Manual Also consider location and environment (air conditioning, ventilation, and so on) for the equipment. 7. Avoid renaming computers. Avoid changing the name of a computer. This type of change can have far-reaching implications, sometimes necessitating the reinstallation of applications.
DECT Messenger overview 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 free message. • DECT handset with E2 (Low Rate Messaging Services [LMRS]) messaging.
DECT Messenger Customer Engineer Manual • SMS messages to cell phones DECT Messenger can send SMS messages to cell phones. The interface to the cell phone provider can be a modem, or a box that behaves like an actual cell phone with SIM card. This option is mainly used as an alternative device. If a message to a DECT handset is not acknowledged, the message can be forwarded to a cell phone. • E-mail messages DECT Messenger can send e-mail, using SMTP, to any e-mail server.
DECT Messenger overview 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 non-functional. Configuration modules There are two configuration modules: • eGRID The eGRID module is used to make inquiries and to edit the configuration database. The configuration database (an MS Access database) stores all the configuration data.
DECT Messenger Customer Engineer Manual Module Name Function Incoming Outgoing eSMTP (client) Sending e-mail messages - Yes eDMSAPI Sending and receiving LRMS (E2) DECT messages using the CSTA interface. Yes, receiving LRMS (E2) DECT messages Yes, sending LRMS (E2) DECT messages eASYNC Asynchronous modem interface to cell phone SMS provider, or to wide area paging system.
DECT Messenger overview This COM port is connected to a Watchdog card that expects the code within certain time intervals. If the code is not received within the time interval, the Watchdog card assumes that the system is down and restarts the PC or activates a alarm indication. • eTM The eTM is the Task Manager, which ensures that the DECT Messenger modules remain active. If a module fails, the eTM reboots the module automatically. You can specify which modules are monitored by the eTM.
DECT Messenger Customer Engineer Manual Figure 13: Example of logical representation of module links Figure 14: Example of module links (practical) In Figure 13: Example of logical representation of module links on page 62, four DECT Messenger modules are shown (eCAP, eKERNEL, eIO, and eDMSAPI). These modules are grouped around the eKERNEL. Each input/output module (eCAP, eIO, eDMSAPI) communicates with the eKERNEL through a socket.
DECT Messenger overview exchanges data. During this data exchange, the module indicates the IP address (PC) on which the module is found. The illustrations show an example with a site and two areas defined. These concepts are defined as follows: • Site The site is the place where the eKERNEL resides. A site has a fixed relationship with only one eKERNEL. If you have more than one site, you have more than one eKERNEL. Also, you can have only one eKERNEL for each PC.
DECT Messenger Customer Engineer Manual You can use this modular structure to do the following: • install modules on different computers in the TCP/IP network • set up a standby eKERNEL on a second site • connect more than one DMC to DECT Messenger DECT Messenger in a WAN or MAN network DECT Messenger can be used in a multiunit MAN (IMP network), or in a multinode WAN (DPNSS network).
Licensing there is a message for a DECT handset in Unit Z/Node Z, the message is transferred first to the Area 2 computer, and then to Unit Z/Node Z. Licensing Licensing is done by means of the following mechanisms. • CSTA Connection licenses in the ISPBX. See CSTA connection (link) license on page 65. • DECT Messenger License Manager. See Figure 16: DECT Messenger License Manager on page 66. • DECT Messenger CTI Licenses (for each DECT system). See SOPHO CTI module License Manager licenses on page 68.
DECT Messenger Customer Engineer Manual DECT Messenger License Manager licenses The DECT Messenger License Manager is the Avaya License Manager. This license manager uses a dongle (using either a parallel connection or USB) and a license file. Figure 16: DECT Messenger License Manager on page 66 shows the License Manager. Figure 16: DECT Messenger License Manager Note: Figure 16: DECT Messenger License Manager on page 66 also shows the CTI application as a licensed application.
Licensing Note: The application module license is shown under the equipment licenses in the License Manager. • Equipment licenses Use equipment licenses to add extra equipment to DECT Messenger. Equipment can be an I/O module, a V.24 connection to an external system, a V.24 connection to ESPA equipment, or connection to a DECT system for location detection.
DECT Messenger Customer Engineer Manual SOPHO CTI module License Manager licenses You must have SOPHO CTI module application licenses to connect to the DECT system. Figure 17: SOPHO CTI Module License Manager For each connection to a DECT system, you require a CTI application license. The number of CTI message channel licenses you require is the sum of the following items: • total number of simultaneous outgoing LRMS messages coming from the eKERNEL.
Detailed module descriptions Detailed module descriptions This section provides detailed information for the following modules: • eKERNEL on page 69 • eDMSAPI on page 70 • eIO on page 70 • eSMTP on page 70 • eSMTP_Server on page 71 • eAPI on page 71 • eWEB on page 72 • eGRID on page 73 • eTM on page 73 • eLOG on page 74 • eCAP on page 74 • eESPA on page 74 • eLOCATION on page 74 • eSMS on page 74 • eSNMP on page 75 • eFR on page 75 • Web administrator on page 75 eKERNEL The eKERNEL module is the main modu
DECT Messenger Customer Engineer Manual eDMSAPI The eDMSAPI module is both an input and an output module, which can send and receive normal and urgent LRMS (E2) messages to and from LRMS DECT handsets such as 4060, C4050, C4040, industrial handset. The Windows 2000 CSTA service must be running for the eDMSAPI module to function. The CSTA service supports simultaneous connections to one or more DMC units for eDMSAPI.
Detailed module descriptions eSMTP_Server The eSMTP_Server is an input module, and is not an SMTP or mail server. This module must be used in conjunction with the Internet Information Server (IIS). The IIS is a Windows 2000 component that is automatically installed with Windows 2000 Server. In Windows 2000 Professional, the IIS must be separately installed. Alarms are sent based on the e-mail address entered in the To: field. The alarm message appears in the Subject field of the e-mail.
DECT Messenger Customer Engineer Manual eWEB The eWeb module can send messages (entered using a web interface) to: • LRMS (E2)-compatible DECT handsets (C4040, C4050, 4060, Industrial handset, and so on) • e-mail using eSMTP (Client) • Any other output module in DECT Messenger, for example: - Global System for Mobile Communications (GSM) phones using SMS - Switch on/off an alarm contact The eWeb server runs on an Apache web server; IIS web server is not supported.
Detailed module descriptions specific messages. You can see the members of this group. The eKERNEL handles this message request as an incoming alarm. Advanced The eWeb Advanced application is an expansion on the eWeb Basic application. Use the advanced application to perform system management tasks using the web interface, and to use script messages for emergency situations.
DECT Messenger Customer Engineer Manual eLOG The eLOG module provides information on how DECT Messenger has processed an incoming alarm from the input up to the output device. This can be necessary if, for example, no response is received to indicate whether a recipient received a message or not. The eLOG module does not have a user interface, and does not provide charts. However, eLOG provides three *.csv files that contain detailed information about how the alarm was processed.
Detailed module descriptions eSNMP eSNMP is a new input module and can receive SNMPv1 and SNMPv2 traps to set or reset an alarm. Configuration tables are available to map the parameters from SNMP environment (address, community, OID, generic, specific…) into the parameters of Messenger environment (group, message, set/reset…) eFR eFR is an add-on module for Messenger that implements fault reporting.
DECT Messenger Customer Engineer Manual • Reporting functions - Inquiry active alarms and ended alarms - Inquiry active scripts and ended scripts • Basic maintenance - Work with group members - Work with alternative devices • Advanced maintenance - Work with groups - Work with users - Work with devices - Work with facilities • Expert maintenance - Import Template configuration Refer to Avaya DECT Messenger Installation and Commissioning, NN43120-301 for more information.
What is required to run DECT Messenger - CD-ROM player. • Optional PC requirements - Analogue Modem for remote maintenance/support. - Analogue Modem for dialling to GSM provider to send SMS messages. Only required if you must send SMS messages to a GSM (cell phone) provider using a dial-in option. - Internal Serial Watchdog (type 1120 from Berkshire Products, www.berkprod.com).
DECT Messenger Customer Engineer Manual General DECT Messenger version 4.0 and later require the following firmware on Avaya DECT Mobility Cards (DMC): • DMC-4 Firmware: 45100404.dwl firmware • DMC-8 Firmware: 47000404.dwl firmware Connection to a DMC The DECT Messenger Server can be connected to the DMC (DECT system) using a TCP/IP connection. Verify that your network allows traffic from DECT Messenger to the DMC.
What is required to run DECT Messenger Figure 18: Connecting to two DECT systems Example: Connecting to Two DECT systems. eKERNEL and eCONFIG are on PC One, as shown in both Figure 18: Connecting to two DECT systems on page 79 and Example: Connecting to Two DECT systems. on page 79. Within the eCONFIG are two eDMSAPI module instances configured for two areas. • eDMSAPI Area 1 contains the IP addresses for PC 1, and PBX IP address for DECT System 1.
DECT Messenger Customer Engineer Manual DATABASES in DECT Messenger This section describes the databases used by DECT Messenger. Supported Database types DECT Messenger uses two databases: • Configuration Database In this database, all configuration data is stored. You can make a copy of this database as a configuration backup. This database is always an MS Access type, and has file name: Messenger_CFG.mdb. • Dynamic Database The dynamic database contains all data about messages.
Installing and getting started This is the most extended type of database. SQL Server provides a user interface to perform Database maintenance. You must install the DECT Messenger database in MS SQL Server manually. MS SQL Server is a licensed product. For more information about the license structure, consult the Microsoft WEB Site. The MS SQL Server also requires MS Windows 2000/2003 Server. The DECT Messenger eKERNEL and the eWEB modules have access to the database through ODBC.
DECT Messenger Customer Engineer Manual Stopping WEB Services IIS for DECT Messenger 1. Open the Internet Information Services (IIS) window. Open IIS by clicking Start on the Windows task bar, and choosing Settings Control Panel > Administrative Tools > Internet Services Manager. 2. Expand the PC name. If the PC name is not expanded, click the + sign next to the name to expand the list and access options for the FTP, WEB, and SMTP services. 3. Stop the Default Web Site.
Installing and getting started Installation of DECT Messenger Software 1. Verify that the licenses and Options are set correctly in the DMC. 2. Verify that the CSTA link to the DMC is installed and operational. 3. Verify license availability. Ensure that you have a DECT Messenger application license available, and that you have sufficient Seat licenses for DECT Messenger. Note: After DECT Messenger starts, the eDMSAPI module reserves the number of licenses that are specified in the eDMSAPI configuration.
DECT Messenger Customer Engineer Manual • Close the License Manager. 3. Install a preconfigured database, if you have one. DECT Messenger already contains a configuration database with data. However you must adapt the data in the database to your needs.
Installing and getting started If you have already edited the tables using the instructions in step 4, skip to step 7. If not, start eKERNEL: • Click Start on the Windows task bar, and choose Programs >... eKERNEL. • Start the module eCONFIG. • Log in as user: admin, with password: admin. 6. Enter configuration values. • In the eCONFIG window, double-click the Site Site1 line. The following window opens: • Enter the Administrator name and Administrator e-mail.
DECT Messenger Customer Engineer Manual 8. Check the Dynamic database path. eKERNEL must have a valid path to the dynamic data database (the default database path are usually correct). Determine which type of database you are using: MS Access, MSDE, or SQL Server. The settings for MSDE and SQL Server in this window are the same as the settings in eCONFIG. • If you are using the MSDE or SQL Server database, ensure that you have set up the ODBC configuration for the eWEB correctly.
Installing and getting started Note: The path setting for the MSDE or SQL Server database must be assigned as System DSN in ODBC. Before you continue, ensure that you know the username and password for the database. Normally the User ID (login name) for the database is sa, and the password is sa. The following illustration shows the eKERNEL settings for the Messenger_DATA database with User ID sa and password philips (the default password is sa). Note: The Data Source =127.0.0.1 points to the local host.
DECT Messenger Customer Engineer Manual 11. Enter configuration information. Enter the correct values for the IP addresses: • Area Description - Description field for the DECT system you are connecting to. Seats Count - Total number of seats you require.
Installing and getting started 13. Configure eWEB module. • Expand the item Modules > eWEB Module. One instance of the eWEB module: eWEB - area is shown. • Double-click the eWEB instance to open the parameters/properties. Click IP addresses, as shown in Figure 19: eWEB Properties on page 90. The first line in the right pane contains the loop back address (127.0.0.1) of the PC. Do not change this. The second line contains the correct IP addresses. • Select the second line, and click Edit.
DECT Messenger Customer Engineer Manual Figure 19: eWEB Properties Using eCONFIG The eCONFIG Module is the tool most commonly used for making changes in the configuration. The configuration is stored in a Database. Be cautious when editing the database, because incorrect or invalid entries can interfere with the operation of DECT Messenger. You can use the eCONFIG on the local PC that is the DECT Messenger server PC.
Using eCONFIG Figure 20: Database handling with eCONFIG on the DECT Messenger Server PC (Local) After you start the eCONFIG for the first time, a copy is made of the configuration database of DECT Messenger (Messenger_CFG.MDB). This copy is stored in the eCONFIG directory: C: \SOPHO Messenger@net eConfig\Mdb with the file name: Messenger_WRK.cfg. After you make configuration changes using the eCONFIG, these changes are stored in the copy of the database (Messenger_WRK.cfg) in the eCONFIG directory.
DECT Messenger Customer Engineer Manual operational database. Avaya recommends that you make a fresh copy of the operational database, because then you are sure there is no database inconsistency. Using eCONFIG (Remote) on remote PC (client) in the Network After the eCONFIG is installed on the DECT Messenger server PC the database is handled as shown in Figure 21: eCONFIG database handling when used on a remote PC (client PC) on page 92.
Using eTM not written into the databases of the eCONFIG modules. These changes are only written into the operational database, not into the eCONFIG databases. • Starting up the eCONFIG again After you start the program again, eCONFIG finds a database in its directory. eCONFIG asks you whether you want to continue with this database or retrieve a fresh copy from the operational database.
DECT Messenger Customer Engineer Manual Environments defined as LOCAL refer to the PC where the eKERNEL is running, whereas environments that have an IP address refer to the IP address of the PC where the modules are running. To add the contents of the registry file into the registry, double-click the *.reg file. To remove the contents from the registry again, open the registry, go to (HKEY_Current_User/Software/ Philips/), and remove the key of a module from the registry.
eDMSAPI Inbound Figure 22: Incoming alarm (IA) in eDMSAPI Figure 22: Incoming alarm (IA) in eDMSAPI on page 95 illustrates the handling of an incoming message (IA) in the eDMSAPI module, as follows: • DECT extension 2000 sends a message to extension 1200. DECT extension 2000 must be IO Registered in the Device settings for extension 2000. Therefore, all LRMS (E2) messages that extension 2000 sends are sent to DECT Messenger. • DECT Messenger checks the intended destination of the message.
DECT Messenger Customer Engineer Manual system. The DECT Messenger system retrieves Incoming Alarms from IP DECT through this TCP/IP port. If a DECT handset needs to send messages to DECT Messenger, the extension number of the handset must be IO monitored (IO Registered) in DECT Messenger. After an incoming message is received by DECT Messenger from a handset, the message goes to a group that contains devices. The incoming message is sent to all the devices specified in the Group.
eDMSAPI Inbound Figure 23: eCAP Sending Message option Not all input devices are capable of generating all five input parameters. If parameters are missing (for example, if a switch is connected to the eIO module), the parameters are taken from fields in tables. The following five parameters are needed. • *SET/*RESET This is described in SET/RESET structure on page 103. • Group The Group is used to define the destination. The Group contains group members, each of which is a device.
DECT Messenger Customer Engineer Manual Figure 24: Alarm handling Note: These input parameters can come from external sources (for example, eCAP or eAPI) or partly from configuration tables. Detailed explanation of the five parameters • Group The input program provides a Group name to which the alarm must be sent. This Group name must be defined in the eKERNEL_GROUP table. From this eKERNEL_GROUP table a reference is made to the eKERNEL_MEMBER table. Here, the members in the group are defined.
eDMSAPI Inbound Figure 25: Input/output relationships Figure 25: Input/output relationships on page 99 shows the settings in the input module IO, and illustrates the relation between the contacts (push buttons, switches) that are connected to the module. For example, contact 01 under eIODI_Contact_str has the Group name Fire1 in the column eIODI_GRP_str. Only eIODI_Group_ is shown in Figure 25: Input/output relationships on page 99. Under the eIO Module in the eCONFIG, two menus appear: Alarm and Group.
DECT Messenger Customer Engineer Manual Figure 26: Groups in an input module A Group name must match a Group name that comes from the input module. In this example, the Group name (Fire1) must match the Group name that is assigned to the input contact (01) in Figure 26: Groups in an input module on page 100. Under the Group name Fire1, two Members are listed, which are actual output Devices (Device 2000 and Device DO_02_01).
eDMSAPI Inbound Figure 27: Input contact 01 Figure 27: Input contact 01 on page 101 shows an example of an input contact 01 in the Input Module eIO. The input contact 01 in the column eIODI_Contact_str is related to the alarm identifier Fire1 under the column eIODI_ALA_Descr_str. Therefore, if the contact is activated, the alarm Identifier Fire1 is sent to the eKERNEL. This also means that there must be an Alarm Identifier in the eKERNEL_ALARM table called Fire1.
DECT Messenger Customer Engineer Manual Figure 28: Alarm identifier The Alarm Identifier, illustrated in Figure 28: Alarm identifier on page 102, is used as an Alarm Description, and contains properties for the alarm (for example, ringing time, repeat intervals, scroll intervals if messages are chopped). These properties determine, in part, how the alarm is displayed. Other properties include: priority of the alarm, message length, silence interval, and so on.
eDMSAPI Inbound Figure 29: Message assigned to a button SET/RESET structure The SET/RESET structure of alarms is complex; you can Set an Alarm and wait for a Reset, or you can Set an Alarm from an Input Module to a Device. In the following section, the various aspects of the SET/RESET structure is explained. • SENT The type SENT is the simplest type of alarming. Figure 30: Sent Alarm structure on page 103 shows the structure.
DECT Messenger Customer Engineer Manual is an LRMS (E2) DECT handset, and the alarm was sent as a normal message, the acknowledgement is automatically generated at the moment that the message arrives at the device. If the alarm message was sent as an urgent message to an LRMS (E2) DECT handset, the acknowledgement is received after the user presses the accept or del button on the handset. See Figure 33: Acknowledge sequences for Normal and Urgent messages using DECT handsets on page 105.
eDMSAPI Inbound The way an alarm is processed in an LRMS (E2) DECT Handset depends on the Acknowledge/ Negative Acknowledge (ACK/NAK) structure, as shown in Figure 32: Alarm processing on page 104. • ACK/NAK A message can be sent to an LRMS (E2) DECT handset as a Normal message, or as an Urgent message. After a message is sent as a Normal message, the DMC sends an Acknowledge at the moment that the message arrives at the handset. No manual confirmation is required.
DECT Messenger Customer Engineer Manual • Resetting an alarm can be done from: - The device on which the alarm is set. Alarm is reset after the call is Acknowledged (LRMS [E2] messaging) - The Input Module from which the alarm was set (eCAP, eAPI or eIO). - An Incoming Confirmation call from eDMSAPI. • You can use the I/O to set an alarm using a push button. This is issued after the button is pushed, and is handled as a SENT alarm. The alarm cannot be reset by a push button.
eLOCATION Table 10: Options for alarm handling Field: set or Field: reset Remove after DECT Messenger action *set *sent Alarm processed as sent alarm. *set *reset Alarm set and waits for a reset. *set *calc System sets the alarm. The system searches in the eKERNEL_ALARM table for a Remove_after SENT for that Input Module with the same Alarm Description. If the system cannot find this, it searches for a Remove_after Reset with the same alarm description.
DECT Messenger Customer Engineer Manual eLOCATION can support configurations with more than 255 radios. If more than 255 radios are used, the first 255 radios use a 2-byte definition from 00 to FF. The remaining radios use a 3-byte definition, for example 100, 101, 102, and so on. Important: IMPORTANT eLOCATION can handle location registration for one DECT cluster only. eLOCATION works with SIP DECT only. How it works A handset sends a short message to the predefined extension number.
eLOCATION eLOCATION Module in eCONFIG The eLOCATION module is configured through eCONFIG. Figure 34: eLOCATION module A number of parameters, for example Site, Area, and so on, are the same for all modules and therefore, are not explained here. However, the following parameters are new in the eLOCATION module and require some explanation: • Location Agent Address This is the IP address of the DAP Controller (DCC) to which the IP connection is made.
DECT Messenger Customer Engineer Manual • >>>Board Definition Refers to the table: eLOCATION_BOARD. This table defines the relation between the DAP Controller and the predefined extension number. Each DECT extension is subscribed at one DAP Controller only. Note: DCC board numbers ranges from 01 to 32. • >>>RPN Definition Refers to the table: eLOCATION_RPN. This table defines the relation between the RPN number and a meaningful message. This message must contain the location information.
Connecting National Instruments modules Figure 35: Rail with National Instruments FieldPoint IO Modules The various types of IO modules that are supported for DECT Messenger can be classified as control modules or I/O Modules. Table 11: Overview of supported control modules on page 111 and Table 12: Overview of supported IO modules on page 112 give an overview of these modules. Table 11: Overview of supported control modules Module Type Description Additional info FP-1000 Control Module with V.
DECT Messenger Customer Engineer Manual Table 12: Overview of supported IO modules Module Type Description Additional info AI-100 Analogue input Module 8 Analogue inputs, each can be set to one of the following ranges: 30V, 15V, 5V, 1V, 0-30V, 0-15V, 0-5V, 0-1V, 20mA, 0-20mA, 4-20mA. DI-300 Digital Input 8 discrete input channels. These inputs are sinking inputs for 24VDC. DI-301 Digital Input 16 discrete input channels. These inputs are sinking inputs for 24VDC.
Connecting National Instruments modules Note: A multi rail configuration is not part of the standard product, and is only available on a Project basis. Figure 37: National Instruments Modules connected to DECT Messenger Note: The connection between the DECT Messenger computer and the first rail is achieved using V.24. Therefore, the maximum cable length is determined by the V.24 characteristics and the cable type.
DECT Messenger Customer Engineer Manual Software Installation Note: Due to subsequent software releases, the contents of this section can differ slightly from your actual product. The software for the I/O modules is based on the industry standard OLE for Process Control (OPC) Server software. After you install the software for the National Instruments modules according to the installation procedure in Avaya DECT Messenger Installation and Commissioning, NN43120-301, this OPC software is installed.
Connecting National Instruments modules Note: Do not forget to close down the FieldPoint Explorer before you start the eIO module. Conversely, do not forget to close down the eIO Module before starting up the FieldPoint Explorer. Using the National Instruments FieldPoint Explorer software on page 115 describes the steps needed to use the FieldPoint Explorer software: Using the National Instruments FieldPoint Explorer software 1.
DECT Messenger Customer Engineer Manual In this menu select Add a comm resource to this server.... The following window opens: 4. Configure the comm resource In the Comm Resources Configuration window, set the following: • Name Accept the default name (FP Res). • Port 116 DECT Messenger Fundamentals March 2012 Comments? infodev@avaya.
Connecting National Instruments modules This is the COM port on your computer to which you have connected your V.24 interface from the FieldPoint FP-1000 module. • Baud Rate Communication speed over the V.24 line. Default this is 115200 b/s. The DIP switch settings associated with the speed are displayed. Ensure that the DIP switches for the Baud rate on the FP-1000 module are in the same position as displayed in your screen.
DECT Messenger Customer Engineer Manual 6. Expand the communication name. After all the devices are detected, they are displayed in the left pane. If not, click the + sign in front of the communication name (FP Res by default). 7. Right-click the device you wish to edit. • Right-click a device. • In the pop-up menu, select Edit this Device... 8. Set channel configuration values. Click Configure channels.
Understanding Security features right pane. If the input on that device module changes, the display is updated to show the changed channel status. 11. Close the FieldPoint Explorer. If you do not close FieldPoint Explorer, the eIO Module does not receive information from the FieldPoint modules. Note: Setting up the eIO Modules is described in Module-elO. Understanding Security features Session Guarding Session Guarding is applicable for the input programs eAPI and eCAP.
DECT Messenger Customer Engineer Manual Figure 39: Berkshire Product Inc. Internal serial PC Watchdog The Watchdog card is designed to monitor PCs used in critical applications such as: File Servers, Voice Mail Systems, Internet Service Provider (ISP) systems, industrial applications, and so on. The purpose of the Watchdog card is to ensure the PC is always available; especially for systems that are not continuously monitored.
Understanding Security features Figure 40: Configuration of the Watchdog card Note: To use the reset and automatic startup, ensure that the Reset button signals the PC to restart, instead of signalling Windows to restart. If the reset button signals for Windows to restart, and Task Manager is running, Task Manager blocks the restart command. Watchdog Installation The following procedure describes how to install the Watchdog. Installing and connecting the Watchdog 1. Set DIP switches.
DECT Messenger Customer Engineer Manual 3. Attach the reset cable. Plug the supplied reset cable onto J2 on the Watchdog board, and plug the other end onto the original reset header on the motherboard. 4. Install the Watchdog. Install the Watchdog in a free slot/bracket position. 5. Connect the power. Connect the power cable to the Watchdog card. 6. Connect the serial cable. • Connect the DB-9S end of the serial cable to a free COM port on the PC.
Understanding Security features Note: If you followed the instructions in Step 1 of this procedure, you set the Watchdog timer to 30 seconds. Therefore, you must fill in a time period that is significantly lower than this value, for example, 8 seconds. Note: After selecting the COM port, keep in mind that other Modules use COM ports as well, such as eCAP, eESPA, eIO. 9. Verify correct operation.
DECT Messenger Customer Engineer Manual Top LED Indication Meaning Flashing at 350 msec. rate Watchdog operational. No alarm condition. Flashing rapidly at 100msec. 3 seconds before timer expires, and no reset received yet. Table 14: Bottom LED Indications. Bottom LED Indication Steady on. Meaning Alarm condition. The timer in the Watchdog is expired, and the alarm contact is activated. Flashing at 1 second rate, each flash 100 Input signal detected. msec.
Understanding Security features Note: These settings are fixed in DECT Messenger. Automatic Watchdog Startup The Watchdog is connected to the reset button of the PC. Watchdog automatically restarts the PC if Watchdog detects that the software is no longer running. Note: Automatic startup with automatic logon is only possible in Windows 2000 professional in a Work Group environment. If you must log on to a Windows 2000 domain, you must always log on manually.
DECT Messenger Customer Engineer Manual Using eBackup The eBACKUP module provides a means to back up files. Use the eBACKUP configuration to specify which files must be backed up, and in what directory to store the copies. 126 DECT Messenger Fundamentals March 2012 Comments? infodev@avaya.
Using eBackup Figure 41: The Backup window In the Path settings, you can specify fields that are filled in by the system: [weekday] 1 ... 7, where 1=monday up to 7=sunday [timestamp] for example, 20030930124506 [weekdayname] Monday ... Friday The eBACKUP Module is NOT a scheduler.
DECT Messenger Customer Engineer Manual Figure 42: Shortcut definition to eBACKUP Note: Figure 42: Shortcut definition to eBACKUP on page 128 shows only a part of the line. The whole line in the Target field of the shortcut is: C:\SOPHO Messenger@net\Exe\eBACKUP.exe / Path:C:\SOPHO Messenger@net /Log drive:C /Site:1 /Batch:Y • Scheduled, using Windows Scheduler If you want automatically created backups of files, you must use the Scheduler in Windows to start the Backup module.
Using eBackup Click Start on the Windows task bar, and choose Settings > Control Panel > Scheduled tasks > Add scheduled task. The Scheduled Task wizard is displayed. 2. Open the Scheduled Tasks window. In the Scheduled Task wizard, click Next. Now you are in the Window, where you must select a program. 3. Browse to the eBackup program. Use Browse to go to the eBACKUP.exe program in the C:\SOPHO Messenger@net\Exe\eBACKUP.exe, and click open. C:\SOPHO Messenger@net\Exe\eBACKUP.
DECT Messenger Customer Engineer Manual 8. Select the file to back up. In the eCONFIG module eBACKUP, select which file you want to back up. Setting up e-mail integration (eSMTP_Server/eSMTP) General DECT Messenger can both send and receive e-mail messages. The following modules are available for e-mail: • eSMTP_Server This module is capable of receiving and handling e-mail messages.
Using eSMTP Server Figure 43: Sending e-mail from client to DECT Messenger In DECT Messenger, the eSMTP_Server works in cooperation with the Microsoft Internet Information Services (IIS). It is possible that other e-mail servers can be used instead of IIS, but they are not supported. • eSMTP (client) eSMTP behaves like an e-mail client program that sends e-mail messages to an e-mail server. The format is the standard SMTP (Simple Mail Transfer Protocol) defined in the RFC 821 specification.
DECT Messenger Customer Engineer Manual Figure 44: e-mail handling in DECT Messenger After an e-mail is sent from the e-mail client to DECT Messenger, the e-mail generally goes through an e-mail provider (through a server). In this e-mail Server, relaying must be switched on, otherwise the e-mail is not transferred to DECT Messenger. Also, the e-mail Server must know to which PC the e-mail message is to be sent.
Using eSMTP Server the @ in the e-mail address) is accepted. However, the domain name (part after the @) is checked by IIS. Figure 45: Example of e-mail message The following fields in the message are processed: • x-sender: sue1@room138.edu The part that follows after x-sender: is the originator of the message; a confirmation message is sent to this address. If you have an e-mail server program other than IIS, there is no x-sender: field. Then the eSMTP_Server uses the field: From: sue1
DECT Messenger Customer Engineer Manual Installing IIS The following procedure guides you through the IIS installation process. Note: You must have the Windows CD-ROM on hand to complete this procedure. Note: In Windows 2000/XP Professional, IIS is not installed by default. In Windows 2000/2003 Server, IIS is installed by default. Install IIS 1. Open Add/Remove Programs. • Click Start on the Windows task bar, and choose Settings > Control Panel. • Double-click Add/Remove Programs. 2.
Using eSMTP Server Sending an e-mail message to a DECT handset 1. Assuming DECT Messenger has a domain name configured as messenger.com, create a group within the eSMTP_Server module called Security1@messenger.com. 2. Within this group add the eDMSAPI device 04#32, which is a DECT handset owned by Security1. Configuring IIS for DECT Messenger The IIS must be configured to work with DECT Messenger. Use the following procedure to configure IIS for DECT Messenger. Configure IIS for DECT Messenger 1.
DECT Messenger Customer Engineer Manual Hereafter, IIS does not start the FTP and WEB services. Only the SMTP Services are running. 3. Create a new domain. • Expand Default SMTP Virtual Server, by clicking on the + sign in front of it. Two submenu items are shown: Domains and Current Sessions. • Right-click Domains (under Default SMTP Virtual Server), and select New > Domain in the pop-up menu. 4. Specify the domain type. Select Alias, and click Next. 5. Set the domain name. Enter the domain name.
Using eSMTP Server 2000@messenger5.com, the part after the @ (in this example, messenger5.com) must be specified as Alias in IIS. 6. Verify the Domain Name list. After entering the Alias, the IIS window must look like the following example: Note: The name Alias in this window is an example. In your configuration a different name appears. 7. Set the Drop Directory path. • Right-click the PC name (in this example: PC75), and select Properties from the pop-up menu.
DECT Messenger Customer Engineer Manual The Drop Directory field specifies a directory where IIS drops all incoming messages. • Leave the default value in place. • Click OK. Using eSMTP The eSMTP module behaves like an e-mail client such as MS Outlook Express. Therefore, you must enter the Domain name and IP address of the SMTP Server to which you send email messages. 138 DECT Messenger Fundamentals March 2012 Comments? infodev@avaya.
Sending SMS messages Sending SMS messages eSMTP Many Global System for Mobile Communications (GSM) Service providers have an SMTP gateway into their SMS Centre, either directly, or through a third-party company. Consult with your local GSM provider to see if this facility is available. They can provide you with an e-mail address and format. For example: A DECT Messenger user wishes to use a GSM handset as an alternative device to the DECT handset.
DECT Messenger Customer Engineer Manual Figure 46: Setup for sending SMS Messages (or Wide Area Paging messages) The connection between DECT Messenger and the GSM SMS provider is made through a modem connection using the PSTN. In DECT Messenger, you must specify the correct settings for this connection. In the eCONFIG, go to the eASYNC Module to change the settings; the window shown in Figure 47: eASYNC settings on page 141 opens. 140 DECT Messenger Fundamentals March 2012 Comments? infodev@avaya.
Sending SMS messages Figure 47: eASYNC settings The following overview explains the eASYNC settings: • Type The type is either SMS for SMS messages to GSM phones, or Paging for Wide Area Paging. • Provider This is the name of the (GSM) provider that provides the dial-in option for SMS or Wide Area paging. Note: This field only supports the following names: BELGACOM, PROXIMUS, and KPN: - BELGACOM refers to the Wide Area paging protocol.
DECT Messenger Customer Engineer Manual The messenger must know what number to dial to access the provider. (This is not the extension number of the cell phone [GSM phone] to which the message must be sent.) As example, for PROXIMUS, this is number 00475161622. • Initialization string This is the initialization string for modem initialization. The string depends on the type of modem that you use. A generic modem initialization string can be for example: AT&C0S0=3.
V.24 - RS232 connections (eCAP, eESPA) eCAP There are four different types of devices that can be connected to the eCAP module using V.24/RS232, as follows: • Nurse Call systems There are many types of Nurse Call systems offering data using V.24/RS232. However, there is no standard protocol. • Building Management systems There are many types of Building Management systems offering data using V.24/RS232. However, there is no standard protocol. • Paging systems There are many types of Paging systems.
DECT Messenger Customer Engineer Manual Using Import/Export menu You can use eCONFIG to import and export configuration database tables. The menu options are shown in Figure 48: Import/Export menu options on page 144. Figure 48: Import/Export menu options The Import/Export function can only handle files of the type .csv. Double-click Export, to open the following window: Figure 49: The Export window In the left-top pane, a list of configuration database tables is shown.
eLOG Figure 50: The configuration file storage directory You can also import configuration database tables using the Import menu. You must ensure that the format of the .csv file matches the required format. To ensure that the format is correct, you can export the table as an example. Note: Ensure that the format and the contents of the .csv files are correct, before you start the import function. An improperly formatted .
DECT Messenger Customer Engineer Manual The following three files are automatically created and updated: • INrqs.csv This file contains individual records for each alarm that came into the eKERNEL. • OUTrqs.csv This file contains individual records for each outgoing alarm from the eKERNEL, for each individual device. • OUTrpy.csv This file contains individual records for the response(s) of each output device on an alarm.
eLOG The logging information is written to a 1Kb buffer, instead of to the files. The contents of the files is updated as follows: • After you shut down the eKernel • After the buffer is full. Remember the buffer is to midnight (after the date changes) • At midnight (after the date changes) and there is something in the buffer, a new set of files is created and the contents of the buffer is written to the files. • Manually.
DECT Messenger Customer Engineer Manual The incoming request was a request to Set or Reset an alarm. • TYPE Indicates the type of incoming message: - msgrqs = Message request or also called incoming alarm - incrqs *IC = Incoming Confirmation • INPGM id The Input Program ID. Each input program has its own unique identifier.
eLOG This is the message as it is sent to the output device. Note that this message can differ from the original message. There are two main items that can cause a difference between the original message and this message field: - Alarm Length as specified in the Alarm ID definitions. If the Alarm Length is set to 10 characters, only the first 10 characters of the original message are regarded as relevant and the remaining characters are stripped off.
DECT Messenger Customer Engineer Manual Not yet implemented. • PINCODE After an incoming Confirmation is received, you see the PIN code in this field. (For an Incoming Confirmation, the TYPE filed shows incrqs *IC.) • Reason not processed This field gives you information on why an incoming alarm is not processed. The messages gives you a clear indication of the cause, such as an alarm cannot be processed. Another example of a message is: Called device does not exist in table eCSTA_INBOUND_EVENT. OUTrqs.
eLOG Output Program of the output device to which the alarm was sent. • DEVICE Outpgm Facility Output Program facility of the device to which the alarm was sent. Note that the Facility specifies the device type characteristics. • DEVICE Member status This field indicates the status of the member based on its presence. This status comes from the comparison between the actual time/date and the presence definition on the device as group member.
DECT Messenger Customer Engineer Manual Output Program that is used for the diversion destination device. • DIVERTED DEVICE Outpgm Facility Output Program Facility that is used for the diversion destination device. INrqs.csv This file contains information about the response(s) (reply) that came from devices on an outgoing alarm/message. The following columns are available: • OUTRQS id This is a tag for each output request.
eLOG • ALARM id This shows the ALARM id that was used for the outgoing message, on which the device generated the response. • ALARM Prty This shows the ALARM priority that was used for the outgoing message, on which the device generated the response. • ALARM Description This shows the ALARM Description that was used for the outgoing message, on which the device generated the response. • REMOVE AFTER An Input Program provides the Remove After parameter.
DECT Messenger Customer Engineer Manual as well and didn't get it within a certain time period. Therefore an automatic NACK was generated. A manual acknowledgement is always required within 30 seconds after an Urgent message is sent to an LRMS (E2) DECT handset. You can acknowledge the alarm by pressing the OK or the Delete softkey on the DECT handset. In case of a CSTA message to a non-LRMS (E2)-DECT, a NACK is also generated after the user of the device didn't go off hook within the ringing time period.
Checking diagnostics How to use the Files The LOG files are used for tracing how an alarm call rolled out. Roughly the procedure is as follows: Tracing the roll out of an Alarm 1. Make sure that you have all three files. 2. Import these files into a Spreadsheet application. 3. Search for the required incoming alarm in the INrqs.csv file. Then write down the parameters: INRQS id, DATE, TIME and Message. 4. Search a record in the file OUTrqs.
DECT Messenger Customer Engineer Manual Logging You can use logging to trace history. All the events in each individual module are stored in a log file. Log files are stored in a common directory, as shown in Figure 53: Log file location on page 156. Figure 53: Log file location The Table eKERNEL_SITE defines the directory where the log files are stored, and the number of days that the files are retained.
Checking diagnostics Figure 54: IO Module log file Figure 54: IO Module log file on page 157 shows the contents of a log file for the IO module. The subsequent XML strings are the result of pressing a button on the DI module, module 02, contact 01. As result of pressing this button, contact 01 is activated on the Digital Output module 03 for three seconds.
DECT Messenger Customer Engineer Manual This tag specifies from which module the message comes. In Figure 54: IO Module log file on page 157, the message comes from the second module. • 01 This tag indicates the contact on the IO module. • 1 This tag indicates the contact status. 1 means that the contact was activated.
Checking diagnostics modules have a similar interface, however, the information displayed is unique in each application. If the eIO Module window is minimized, maximize it. Four tabs are visible in the window, as follows: • Logging Tab In the logging tab, the online log information is provided. Figure 55: Logging Tab There are two logging panes, the upper, called Logging, and the lower, called Detail. In the Logging pane, the XML messages are shown. These are the same as the messages in the log files.
DECT Messenger Customer Engineer Manual Figure 56: eKERNEL Tab The Jobq pane shows the pending jobs for the module. In the Outq pane, the outgoing communication from the module is shown. • eIO Tab The eIO tab shows IO module specific information. Figure 57: eIO Tab • Connections Tab The Connections tab shows information on the connections between the eIO module and the eKERNEL. This tab also shows information on the connections between the external part and the eIO module itself.
Checking diagnostics Figure 58: Connections Tab The right pane gives information about the external devices that are connected to the eIO Module. The left pane shows information about the TCP/IP connections. The connections between the eKERNEL and the eIO module are shown in the top part of the left pane. The connections between the IO module and (if applicable) an external device are shown in the bottom part of the left pane.
DECT Messenger Customer Engineer Manual Figure 59: Status lamps In the bottom part of the left pane, two lamps are visible, indicating the status of the TCP/ IP connection. The left lamp indicates the status of the connection between the IO module and the eKERNEL. The right lamp indicates the TCP/IP status between the IO module and the external device (if applicable). Both are green in Figure 59: Status lamps on page 162.
Checking diagnostics eKERNEL Window The window of the eKERNEL differs from the other modules, and has a tab for each individual module. Figure 60: eKERNEL module window Select a module tab to see the information for that specific module, as follows: • TCP status. Shows the connection data for the TCP/IP connection between the eKERNEL and the module. • Client information Shows information about the module. • Logging. Shows the logged communication between the eKERNEL and the module. • Detail.
DECT Messenger Customer Engineer Manual Simulation Options in a Module You can use a simulation menu in modules to simulate an message. The simulation is different for each individual module, because the nature of the modules differ. Figure 61: Accessing Simulate Options on page 164 shows you how to access the simulation menu.
Index A ACK ..........................................................................103 Add-on modules .........................................................14 Add—On module ........................................................12 Adding a DECT device ...............................................48 ALARM Description ...........................................145, 150 ALARM id ..........................................................145, 150 Alarm properties ........................................
eESPA ........................................13, 59, 69, 74, 142, 143 eFR .......................................................................69, 75 eGRID ........................................................12, 59, 69, 73 eGUARDIAN ..............................................................12 eIO .............................................................13, 59, 69, 70 eKERNEL ...........................................12, 58, 61, 69, 119 eKERNEL service options ................................
Linking modules .........................................................61 Log file location .........................................................156 LOG files ...................................................................155 Logging ...............................................................14, 156 Logging module ..........................................................61 M MAN network ..............................................................64 Managing devices ........................
Users ..........................................................................45 Using eBACKUP .......................................................126 Using eCONFIG .........................................................90 Using eCONFIG (local) ..............................................90 Using eCONFIG (remote) ...........................................92 Using eSMTP ...........................................................138 Using eTM .........................................................
