DECT Messenger Installation and Commissioning — Book 1 Avaya Communication Server 1000 7.5 NN43120-301, 03.
© 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: Introduction.........................................
More extended program............................................................................................................................ 69 Real-world examples................................................................................................................................. 70 Chapter 11: Module - eAPI sample.................................................................................... 71 Chapter 12: Module - eASYNC................................................................
Install module eFR.................................................................................................................................... 150 Launch module eFR.................................................................................................................................. 150 License module eFR................................................................................................................................. 151 Configure module eFR.................................
Chapter 23: Module - eLOCATION..................................................................................... 207 Initialization............................................................................................................................................... 207 Program activity........................................................................................................................................ 210 Architecture.............................................................
Chapter 1: New in this release The following sections detail what’s new in this document for Avaya Communication Server 1000 Release 7.5: • Features on page 7 • Revision history on page 7 Features There have been no updates to the feature descriptions in this document. Revision history March 2012 Standard 03.02. This document is up-issued to support Avaya Communication Server 1000 Release 7.5, and contains changes relating to updates to the Messenger software. November 2010 Standard 03.01.
New in this release 8 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 2: Introduction DECT Messenger is a client-server software platform for processing and converting messages between various protocols. It consists of several modules, some of which can be deployed independently on other PCs in the same network. The DECT Messenger modules are grouped as follows: • 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.
Introduction 10 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 3: System requirements The following sections describe the system requirements for DECT Messenger.
System requirements Client PC Requirements DECT Messenger client modules are supported on any PC capable of running the supported operating systems. A DVD drive is required in order to install the product. Optional hardware Depending on the way DECT Messenger is being used, there are several hardware devices that may be needed in order to use certain features: • National Instruments equipment for digital input/output (contacts) and analogue input for software module eIO.
Network information Network information Table 1: Network information Port Description 80 Port for HTTP traffic used by Web Administrator application 1433 Default SQL Server port (when using SQL Server as database storage engine) 3101 Default eKERNEL server port for eDMSAPI 3102 Default eKERNEL server port for eCAP – Eldad 3103 Default eKERNEL server port for eCAP – Televic 3104 Default eKERNEL server port for eCAP – Generic 3105 Default eKERNEL server port for eASYNC module 3106 Default eK
System requirements 14 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 4: Installation steps The Avaya DECT Messenger installation steps assume that all operating system and hardware requirements are met. The following flow chart summarizes the installation and setup procedures.
Installation steps • Installing SQL Server on page 32 • Installing DECT Manager on page 37 • Configuring DECT Messenger on page 46 • Install a DECT Messenger Client on page 41 16 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 5: Preparing external devices This chapter provides information on preparing external devices. Integration with IP-DECT Manager You can connect DECT Messenger to an IP-DECT system. The communication between DECT Messenger and the IP-DECT system is only for LRMS to or from the DECT handsets. DECT Messenger uses the CTI port on the IP-DECT system to send and receive LRMS messages. This port does not support CSTA.
Preparing external devices Figure 2: Integration with Call Server 1000 IP-DECT Manager TCP/IP port for DECT Messenger On the IP-DECT Manager system, there is a TCP/IP port open for LRMS (E2) messages sent to and from handsets. The port number is not fixed but determined in a configuration file (dapcfg.txt) located on the DAP Controller PC. The path to the dapcfg.
National Instruments Analog/Digital Hardware [DAPPRF] ; Start of DAPPRF address section 192.168.17.74 [CDA] ; Start of CDA address section 192.168.17.74 30160 [GK] ; Start gatekeeper address section 192.168.17.200 5060 [XDS] ; Start SIP section b2b_ua=yes [CONFIG] ; Start of static config section CONFIGFILE=replace IPCONFIG=replace The TCP/IP port for Messaging is located in the [DS] section. The IP address of the DAP Controller PC is followed by a port number range.
Preparing external devices Table 2: Control modules overview Module type Description Additional Info FP-1601 Control module with IP interface Interface module between the I/O modules and DECT Messenger. Controls up to 9 I/O modules directly. FP-1000 Control module with V.24 interface Interface module between the I/O modules and DECT Messenger. Controls up to 9 I/O modules directly. Up to 24 FP-1001 modules can be connected using RS485 bus to expand the system with extra I/O modules.
National Instruments Analog/Digital Hardware The following figure shows an example of how a rail of National Instruments I/O modules can be connected to DECT Messenger. On a rail, there can be various types of I/O modules. The maximum number of modules for each rail is 8. Important: Although you can build configurations with many input or output modules, there is a limitation on the number of input or output modules than an eIO DECT Messenger module instance can handle.
Preparing external devices Figure 5: Example of connecting multiple FP rails to DECT Messenger The connection between the DECT Messenger PC and the first rail is achieved by means of V.24. This means that the maximum cable length is determined by the V.24 characteristics and the cable type. If you have more than one rail (only available on a project basis), the connection between the rails and therefore the connection between the FP- 1000 and FP-1001 modules is achieved by means of an RS-485 connection.
Hardware installation Hardware installation The detailed installation procedures for the FP modules are in the installation documents located on the DECT Messenger DVD: D:\Documentation\\Background –eIO – xxx.pdf where D: is the drive letter of your DVD drive. For the latest version of the documents, also refer to National Instruments website at http:// www.ni.com. Software installation To connect to the FP I/O modules, DECT Messenger requires third-party software components from National Instruments.
Preparing external devices Figure 6: DECT Messenger interaction with FP I/O modules Important: The OPC Server software can be controlled by only one application. This means that you can have either the eIO Module or the Measurement & Automation Explorer active, but not both. Remember to close one of the applications before starting the other. Both components are part of the National Instruments FieldPoint software package that is located on the DECT Messenger DVD.
Chapter 6: Preparing the Operating System As a general rule, ensure that the operating system of the target PC is up-to-date, with the latest service packs and patches installed prior to installing DECT Messenger product. Note: Avaya recommends that you do not configure the Automatic Updates feature in Windows to Automatic. This will avoid system reboots while DECT Messenger is operating.
Preparing the Operating System Figure 7: Windows Components Wizard window 5. Select Details. The Internet Information Services (IIS) details window appears, listing the installed IIS subcomponents. 6. Verify that Common Files and Internet Information Services Snap-In options are checked. 7. (Optional) If you intend to use SMTP Server module in DECT Messenger, ensure that SMTP Service option is also checked, as shown in the following figure.
Installing IIS Figure 8: Internet Information Services (IIS) window 8. Select World Wide Web Service and click Details; in the World Wide Web Service details window that appears, ensure that World Wide Web Service is checked, then click OK to close it. 9. Click OK to close the Internet Information Services (IIS) details window. 10. Click Next to begin the installation. You may be prompted to insert the Windows installation CD/DVD during this step. 11. Click Finish to complete the installation.
Preparing the Operating System Figure 9: Server Manager window 3. Click Add Role. The Add Roles Wizard opens. Click Next to skip the opening screen. 4. Check the Web Server (IIS) box in the list of available roles and click Next. 5. Read the introductory information displayed, and then click Next again to reach the Select Role Services wizard page. 6. In the list of role services, verify that the following options are checked: a. Web Server > Application Development > CGI b.
Installing IIS 3. Click Add Features. The Add Features Wizard window opens, as shown in the following figure. Figure 10: Add Features Wizard window 4. Check SMTP Service from the list of available features. A confirmation screen displays, prompting to add other features and services dependent on SMTP Service. 5. Click Add Required Role Services. 6. Click Next to proceed to the Web Server (IIS) role information screen. 7. Click Next.
Preparing the Operating System 30 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 7: Installing third-party software This chapter describes how to install the optional third-party software that is required to run certain DECT Messenger modules. The software is located on the DECT Messenger DVD. Installing Adobe Reader 9 Adobe Reader 9 is required to read the documentation on the DVD. On the server, it is also used by the eGRID configuration module to display information about the configurable database fields.
Installing third-party software Figure 11: Adobe Reader 9 Destination Folder window 3. Verify the installation location and click Next. If you want to change the destination folder, click Change Destination Folder and specify a new location. 4. Click Install to start the installation. 5. Click Finish after installation completes. Installing SQL Server DECT Messenger optionally uses SQL Server for its MessengerData database.
Installing SQL Server Note: SQL Server 2000/MSDE2000 are not supported. When using an SQL Server installed on a PC different from the DECT Messenger PC, the uptime of DECT Messenger depends on the uptime of the database server PC. The software continuously uses the database for storing temporary data, such as active alarms. Therefore, stopping the database server PC causes DECT Messenger to stop functioning.
Installing third-party software Installing National Instruments Field Point and DataSocket This section describes the installation of modules related to the eIO component of DECT Messenger. You can skip this section if you do not plan use the eIO module. 1. Insert the DECT Messenger product DVD. The DVD Main Menu window appears. (If the menu does not appear, double click D:\Autorun.exe, where D is the drive letter of your DVD drive). 2. From the DVD Main Menu, select National Instruments Field Point 6.0.
Installing National Instruments Field Point and DataSocket Figure 12: National Instruments Measurement & Automation Explorer screen For details on how to configure the Field Point modules with Measurement & Automation Explorer software, refer to the National Instruments documentation.
Installing third-party software 36 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 8: Install DECT Manager This chapter describes how to install the DECT Messenger software. If you need to deploy one or more DECT Messenger software modules on a different PC, you can find the steps for installing additional DECT Messenger copies in client mode in the Installing DECT Messenger Client subsection.
Install DECT Manager Figure 13: System Configuration Check window Note: If the Pending Restart Requirement check fails (for example, due to a conflict with other installed software), click Cancel to stop the installation and reboot the PC, and then restart the installation procedure. 3. Click Next to continue. The Install Prerequisites window appears, as shown in the following figure: 38 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Installing DECT Manager Figure 14: Install Prerequisites window 4. The Setup Wizard checks if all necessary third-party software components are present and attempts to automatically install any missing mandatory ones. The mandatory components are as follows: • Sentinel Dongle Driver package • CTI Runtime Library 2.0 5. Verify the warning messages about missing optional components.
Install DECT Manager 9. Select Complete to install all available components in the default installation path and click Next to continue. The Database Installation window appears, as shown in the following figure. Figure 15: Database Installation selection window Note: On Windows Server 2008, you might get a Files in Use warning window. If this happens, select Automatically close and attempt to restart applications and click OK.
Install a DECT Messenger Client 13. When the installation completes, the InstallShield Wizard Completed screen appears. Click Finish to finalize the installation process. 14. When prompted to restart the computer, click Yes . Install a DECT Messenger Client Depending on customer needs, there might be situations when it is necessary to spread certain DECT Messenger components on several computers in the same network.
Install DECT Manager 7. Select Custom and click Next to continue. The Custom Setup window displays, allowing you to specify the components you want to install and run on the client PC, as shown in the following figure. Figure 16: Custom Setup window 8. Select the features to install and click Next. The Ready to Install window appears. 9. Click Install to begin the installation process. 10. When the InstallShield Wizard Completed screen appears, click Finish.
Uninstalling DECT Messenger Uninstalling DECT Messenger DECT Messenger can be uninstalled using one of the following procedures. The procedures are applicable for both Server and Client installs. Note: During uninstall, the DECT Messenger databases and module configuration files (*.ini) are automatically removed. Make backups if you intend to restore them at a later point in time. Uninstalling from Control Panel (Windows XP/2003) 1. Go to Start > Settings > Control Panel and open ‘Add or Remove Programs’.
Install DECT Manager 44 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 9: Getting started with DECT Messenger This chapter describes the actions required for getting a DECT Messenger Server up and running. For further details on how to configure and use the Input/Output modules, refer to DECT Messenger Fundamentals, NN43120-120. Loading licenses Note: Before using DECT Messenger, you need a license key and a dongle attached to one of the USB ports of your PC. 1.
Getting started with DECT Messenger 3. In the License Manager menu, go to File > Load a New License String and browse for the license key file received from Avaya. Click Open to load it. 4. Verify the loaded licenses are correct. The following figure shows the loaded licenses in License Manager. Figure 18: License Manager loaded licenses Configuring DECT Messenger Most DECT Messenger configuration settings are stored in a Microsoft Access database (*.mdb file).
Configuring DECT Messenger – whenever possible – a standard configuration as a starting point when setting up a customer site. Standard configuration database Standard configuration databases are installed with the main product during a Server-mode installation. They are located in the following directory: [INSTALLDIR]\Default Templates\Database Figure 19: Default database templates You can manually apply a configuration database or import one using Web Administrator.
Getting started with DECT Messenger 5. Browse for the main database directory. For example: C:\Program Files\Avaya\Avaya DECT Messenger \Database. Rename the existing MessengerConfig.mdb to MessengerConfig_old.mdb, in case you need to return to the default configuration. 6. Paste the MessengerConfig.mdb template file into the main database directory. To import a configuration database using Web Administrator: 1. Ensure that all DECT Messenger modules are stopped. 2.
Configuring DECT Messenger Figure 20: Web Administrator Import Configuration screen 7. A message appears stating the import was successful. Important: Standard configuration databases are not changed during the installation to match the environment. As a result, the file path and IP address of the DECT Messenger server PC are set to the default values by the installer.
Getting started with DECT Messenger When eKERNEL starts, it displays a main window similar to the one shown in the following figure: Figure 21: The eKERNEL main window The list on the left indicates the configured modules, their status, and the connection information required to connect to eKERNEL. Using eCONFIG (Configurator) You can install and useCONFIG on the server or on one of the client PCs.
Configuring DECT Messenger 3. When using eCONFIG from a client PC, you will be prompted for the location of MessengerConfig.mdb database. Browse to the network share of the server PC containing the MessengerConfig.mdb database. 4. If a working configuration database already exists (from a previous eCONFIG session), you will get a message box asking whether to use the locally modified copy of the MessengerConfig.
Getting started with DECT Messenger The left pane shows a tree with the available configuration items, while the right pane shows details on the currently selected configuration item. Working with the eCONFIG user interface • Left-click on any node in the tree to show more information on the right pane. • Right-click on the nodes to show a pop-up menu with actions available for that node. • Double-click on a node to show a screen where you can perform maintenance changes. • Select File > Exit to close.
Configuring DECT Messenger The modules node lists all modules configured, grouped by module type. Setting up module parameters requires advanced technical knowledge; in most cases, the provided defaults are sufficient. Refer to the Administrator Guide for detailed information on each module. The alarms are notifications (also called messages) received by eKERNEL from input modules.
Getting started with DECT Messenger 4. On the middle-right, a description text explains the purpose of the selected item and how it should be configured. 5. On the bottom-right, the current value of the selected item is shown, as well as any validation errors related to the value entered in the input control. The following figure shows an example of a site configuration error: Figure 25: Site configuration error message 6. Enter a new value for the selected item. 7.
Configuring DECT Messenger Deleting a module 1. Expand Site NEC node in the tree. 2. Expand the Modules node. 3. Under the Modules node, expand the node that represents the type of module which you do not intend to use. 4. Double-click the module name (e.g. ‘eESPA – area Hilversum’). The module details window appears – see Figure XY. 5. In the module configuration window, click Delete. A confirmation window appears. 6. Click OK to confirm the removal.
Getting started with DECT Messenger Figure 26: eCONFIG Area configuration window 4. Select the Description item and type a new description. 5. Click OK to save the changes. Configuring PBX information Note: When using eDMSAPI, you also need to specify the IP address and port of the PBX (or IPDECT DAP Controller PC) that the module should connect to. Modifying the PBX information 1. Expand the Modules node. 2. Expand the eDMSAPI node. 3.
Configuring DECT Messenger Figure 27: eDMSAPI module details window 4. Select and modify PBX type to indicate the type of device the module connects to (iS3000, Avaya or DAP Controller). 5. Select and modify PBX address to match the IP address of your target device. 6. Select and modify PBX port to match the port number of your target device. 7. Select and modify the Seats count according to the number of seat licenses available in your PBX.
Getting started with DECT Messenger Adding a device 1. Expand the Site NEC node in the tree. 2. Expand Groups and devices. 3. Right-click All devices and select New Device. The device details screen appears, as shown in the following figure: Figure 28: Device details window 4. Select the Output Program and click Browse. The Select Output Program window appears, as shown in the following figure: 58 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Configuring DECT Messenger Figure 29: Select Output Program window 5. Select eDMSAPI by clicking the black arrow and click OK. 6. Select and specify a Device ID (the extension number, e.g. ‘2000’). 7. Select the Output program facility and click Browse.
Getting started with DECT Messenger Figure 30: Select Facility window 8. Select a handset model and click OK. 9. Select and specify other properties if necessary (e.g. ‘Description’). 10. Click OK to save the new device. Several devices can be added to a group, as group members. Working with groups and group members, as well as further details on supported output devices can be found in DECT Messenger Fundamentals, NN43120–120.
Configuring DECT Messenger Also, while eKERNEL and associated modules are down, no input and output is performed, and alarm input and distribution is suspended. Stopping active modules 1. On the server PC (where the database is located), check if eTM (Task Manager) module is running. • If eTM is not running, close every running module by clicking the box in the top-right corner of each module main window. • If eTM is running, right-click its icon in the Windows taskbar notification area and choose Stop.
Getting started with DECT Messenger 5. When the database is successfully published, a message appears stating that the registry files necessary for eTM module are created, as shown in the following figure: Figure 32: Successful publication window 6. Open the registry editor: • Start menu > Run • Type regedit 7. Locate the HKEY_CURRENT_USER\Software\Avaya\Avaya DECT Messenger\eTM registry key and delete it. 8.
Configuring DECT Messenger on the client PC corresponding to that specific environment, after stopping eTM and other associated processes. 12. Start eTM to bring the environment online. The following figure shows an example of eTM running configured modules: Figure 33: eTM with running modules Discarding changes 1. When asked whether to apply the new configuration, click No. A window appears asking you to confirm that you want to exit the application. 2. Click Yes.
Getting started with DECT Messenger where the MessengerConfig.mdb resides on the DECT Messenger Server must be shared over the network to enable remote machines to access the shared database. Note: Contact your network administrator for details on security and access privileges over the network. To avoid browsing for the location of MessengerConfig.mdb, you can specify its location in the eCONFIG.ini file. Configuring the eCONFIG.ini 1. Open Windows Explorer. 2.
Chapter 10: Module eAPI Introduction The module eAPI is not a real module, but rather a description of a public Application Program Interface (API) for third-party developers who want to communicate with DECT Messenger. This chapter is intended for developers who want to build an interface to the eKERNEL module. The objective of this document is to describe how developers can integrate applications with DECT Messenger. Note that the eAPI interface has limited capabilities.
Module eAPI configuration techniques (through registry, .INI files, database, command line parameters, and so on) to control the behavior of their applications. Basic architecture The architecture of eAPI is embedded in the eKERNEL module. The eAPI interface refers to the ability of eKERNEL to provide a TCP server, which listens to a specified port, and receives TCP sockets packages that contain message requests.
Introduction to a sockets client - The parameter alarmdescr must start with and end with the tag - The parameter msg must start with tag and end with the tag - The parameter remove_after must start with tag and end with the tag • The parameter set_or_reset can supports the following values: *SET or *RESET • The parameter group refers to a configured group defined in the eKERNEL_GROUP table • The parameter alarm_descry refers to a confi
Module eAPI 6. Run the program. If you click the Command1 button, a message request is sent to eKERNEL. 7. You can alter the code shown in Figure 36: Sample socket client code on page 69 to specify the correct parameters for the parameters group (use one of the values specified in the eKERNEL_GROUP table), alarm description (use one of the values specified in the eKERNEL_ALARM table), and so on.
More extended program Figure 36: Sample socket client code More extended program Refer to Module - eAPI sample on page 71 for a detailed source code listing of a more complete implementation of a Visual Basic program that implements eAPI functionality. The compiled program eAPI.exe and the source code eAPI.zip (zipped) are shipped with the DECT Messenger and the .exe is installed when you select eAPI module during custom install.
Module eAPI Some typical features include: • Ability to specify certain runtime parameters of the program by means of the command line parameters in the shortcut, such as: /Site:2 /eKernel address:*LOCAL /eKernel port: 3209 /Log drive:C • A menu that provides a queue (list) that the module can use to handle situations in which eKERNEL is temporarily unavailable. • Logging facilities on-screen, with the option to left-click a log entry to see details.
Chapter 11: Module - eAPI sample eAPI_form - 1 Option Explicit ' -------------------------------------' This program requires a valid command$ ' -------------------------------------' /Site:1 ' /eKernel address:*LOCAL or value xxx.xxx.xxx.
Module - eAPI sample log S, INF, Warning : parameter ' & keyword & ' not available in ' & xml & ' Else parse_xml = lcl_value End If On Error GoTo 0 End Function Private Sub lab_message_Click() End Sub Private Sub cmd_transmit_Click() Dim lcl_xml As String ' Validate If Trim$(txt_group) = Then lab_msg = Error. Group must be entered. txt_group.SetFocus Exit Sub End If If Trim$(txt_alarmdescr) = Then lab_msg = Error. Alarm description must be entered. txt_alarmdescr.
End Sub Private Sub lst_log_DblClick() ' show details On Error Resume Next: Err = 0 txt_log.Text = lst_log.List(lst_log.ListIndex) On Error GoTo 0 show_pages End Sub Private Sub Form_KeyDown(KeyCode As Integer, Shift As Integer) 'F3=Exit If KeyCode = 114 Then Unload Me 'End End If End Sub Private Sub Form_Load() Dim lcl_rc As String Dim lcl_o Dim lcl_version Dim Lcl_Msg As String Dim lcl_h As Integer ' Set application title Me.Caption = eAPI - SOPHO Messenger@Net - v & App.Major & . & App.Minor & . & App.
Module - eAPI sample ' Terminate if undefined values If g_site = N/A Then lcl_rc = MsgBox(eAPI could not start. Parameter '/Site:xxx' missing in command strin g., vbCritical, eAPI - SOPHO Messenger@Net) Unload Me End If If g_ekernel_remote_address = N/A Then lcl_rc = MsgBox(eAPI could not start. Parameter '/eKernel address:xxx.xxx.xxx.xxx' m issing in command string., vbCritical, eAPI - SOPHO Messenger@Net) Unload Me End If If g_ekernel_remote_port = N/A Then lcl_rc = MsgBox(eAPI could not start.
g_ekernel_local_address = ip_ekernel.LocalIP lab_ekernel_local_address = & g_ekernel_local_address g_ekernel_local_port = ip_ekernel.
Module - eAPI sample If lcl_ekernel_cur_state <> g_ekernel_prv_state Then g_ekernel_prv_state = lcl_ekernel_cur_state Select Case lcl_ekernel_cur_state Case 0 lab_ekernel_msg = Closed lab_ekernel_state.BackColor = RGB(0, 0, 0) Case 1 lab_ekernel_msg = Open lab_ekernel_state.BackColor = RGB(200, 130, 0) Case 2 lab_ekernel_msg = Listening lab_ekernel_state.BackColor = RGB(255, 255, 0) Case 3 lab_ekernel_msg = Connection pending lab_ekernel_state.
-------------------------------------------------------------------------While lst_ekernel_jobq.ListCount > 0 process_ekernel_jobq lst_ekernel_jobq.List(0) lst_ekernel_jobq.RemoveItem 0 eAPI_form - 6 Wend ' -------------------------------------------------------------------------' Handle requests in ekernel outq ' -------------------------------------------------------------------------On Error Resume Next: Err = 0 Do While lst_ekernel_outq.ListCount > 0 lcl_o = lst_ekernel_outq.List(0) ip_ekernel.
Module - eAPI sample lcl_guarding = Timer - g_guarding If lcl_guarding < 0 Then lcl_guarding = lcl_guarding + 86400 If (lab_guarding <> Format$(lcl_guarding, 00000)) Then lab_guarding = Format$(lcl_guarding, 00000) End If ' Process ekernel process_ekernel ' Enable timer to resume processing tim.Enabled = True End Sub Private Sub txt_log_GotFocus() lst_log.
Select Case Left$(g_log_path, 3) Case C:\ g_log_path = D:\ + Mid$(g_log_path, 4) lab_log_path = & g_log_path Case D:\ g_log_path = C:\ + Mid$(g_log_path, 4) lab_log_path = & g_log_path Case Else g_log_path = C:\ + Mid$(g_log_path, 4) lab_log_path = & g_log_path End Select End If Err = 0 ' make D:\SOPHO Messenger@Net lcl_path = g_log_path If Len(Dir$(lcl_path, vbDirectory)) = 0 Then MkDir lcl_path End If ' make D:\SOPHO Messenger@Net\log lcl_path = lcl_path + \log If Len(Dir$(lcl_path, vbDirectory)) = 0 Then
Module - eAPI sample 80 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 12: Module - eASYNC The module eASYNC consists of one program eASYNC.exe, written in Visual Basic. Overview eASYNC.exe The eASYNC.exe is the Visual Basic component of the eASYNC module. The program communicates with two processes: the eKERNEL.exe and the asynchronous modem attached to a COM port. The eKERNEL.exe is the central engine that centralizes all database access and communication with input and output capable modules. The eASYNC.exe communicates with eKERNEL.exe by means of TCP sockets.
Module - eASYNC At startup, the eASYNC.exe sends an XML string to eKERNEL.exe requesting a configuration. This step is needed for each module that interacts with eKERNEL.exe, because this approach allows central administration using a single database, even if some client modules are located on a distributed machine. Figure 38: A typical cfgrqs configuration request and reply Refer to the appropriate sections on the database tables that define the received parameters for more information on each value.
eASYNC.exe If the shown in Figure 39: eASYNC module receives this cfgrpy from the eKernel if no license is available for eASYNC on page 83 is received, no license is available, and the eASYNC module cannot connect to the eKernel module anymore. Figure 39: eASYNC module receives this cfgrpy from the eKernel if no license is available for eASYNC The eASYNC Connections tab is shown in Figure 40: eASYNC Connections tab on page 83.
Module - eASYNC Figure 41: Sample eKERNEL message request and eASYNC feedback During communications, eASYNC contacts the provider and handle the dialog that is required to deliver the message. The transactions are processed on a first-in first-out basis. However, configuration settings can be active that request a wait time or a queue depth that must be reached prior to initiating the communication process.
Logging Logging Logging information is available both on-screen and in logging files. You can view on-screen logging through the Logging tab.
Module - eASYNC Figure 45: Sample logging data for SMS to KPN 86 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Logging Figure 46: Sample logging data for PAGING to BELGACOM DECT Messenger Installation and Commissioning — Book 1 March 2012 87
Module - eASYNC 88 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 13: Module - eBACKUP You can use the eBACKUP module to make a backup of a predefined list of files. The eBACKUP.exe must be started from a shortcut, which provides a number of command line parameters.
Module - eBACKUP Si te From path From file To path To file 3 C:\SOPHO Messenger@Net eAPI.exe \Exe C:\Temp\[weekday]\SOPH O eAPI.exe Messenger@Net\Exe 3 C:\SOPHO Messenger@Net eASYNC.exe \Exe C:\Temp\[weekday]\SOPH O eASYNC.exe Messenger@Net\Exe 3 C:\SOPHO Messenger@Net eBACKUP.exe \Exe C:\Temp\[weekday]\SOPH O eBACKUP.exe Messenger@Net\Exe 3 C:\SOPHO Messenger@Net eCAP.exe \Exe C:\Temp\[weekday]\SOPH O eCAP.exe Messenger@Net\Exe 3 C:\SOPHO Messenger@Net eDMSAPI.
Figure 48: Backup start window Click Backup to begin the backup procedure. When all the files are successfully copied, the window becomes green.
Module - eBACKUP Figure 49: Backup successful If one or more files are not copied, the window becomes red. 92 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Figure 50: Backup error window During backup, logging information is written to the hard disk, an example of which is shown in Figure 51: Sample backup log on page 94. Note that in the example, the file eIO.exe was not saved.
Module - eBACKUP Figure 51: Sample backup log 94 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Avaya recommends that you close all the DECT Messenger applications before starting the backup procedure. In release 2, the file copy procedure is implemented by means of a Windows API-call, as shown with the code excerpt in Figure 52: File copy example on page 95: Figure 52: File copy example Important: To ensure a complete and consistent image, you must close all applications before backup. The code shown in Figure 52: File copy example on page 95 can back up files, even if they are open.
Module - eBACKUP 96 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 14: Module - eCAP The module eCAP consists of the program eCAP.exe, written in Visual Basic. In general, DECT Messenger programs reside in the default directory C:\SOPHO Messenger@Net\Exe, unless otherwise implemented in your environment. Overview eCAP.exe The eCAP.exe is a Visual Basic component of the eCAP module. The program communicates with two processes: the eKERNEL.exe and an external alarm interface. The eKERNEL.
Module - eCAP keyword Log drive refers to the drive where the logging data must be stored. Usually this is C: \SOPHO Messenger@Net\Log\. At startup, the eCAP.exe sends an XML string to eKERNEL.exe requesting a configuration. This step is needed for each module that interacts with eKERNEL.exe, because this approach allows central administration using a single database, even if some client modules are located on a distributed machine.
eCAP.exe Figure 55: eCAP Connection tab Because the eCAP is designed to handle asynchronous serial communications with a number of alarm systems, the eCAP requires configuration settings to start processing. These values are returned through the reply that is sent on return of the request.
Module - eCAP Once a link is established between eCAP and the alarm system, the eCAP handles further communications and informs eKERNEL when relevant information is to be exchanged. Functional description In general, eCAP is designed to provide eKERNEL with alarm information. This is carried out using a message request. For some interfaces eKERNEL must send feedback to the alarm system, a process that is handled through message reply request.
ARGINA Manufacturer Model TELEVIC PROTOCOL CONVERTOR – L:03 TYCO MINERVA 80 VSK DE LICHTERVELDE VSK OLV VAN VREDE VSK ST-JOZEF WORMALD *BASE WORMALD L:01 WORMALD G:EIPM ARGINA The valid manufacturer is ARITECH and the valid model is *BASE. Argina *BASE is based upon installation Maas en Kempen-Campus Bree.
Module - eCAP Figure 56: Sample Aritech protocol data Aritech alarms are always sent to group ARITECH, because no pager information is available in the datastream. Messages are sent with alarm description ARITECH. An alarm is set only when Gebeur occurs in the datastream. When BRAND occurs the message is BRAND; in other cases the message is ARITECH. When HERSTEL occurs a general reset of all ARITECH alarms is issued. Note: Use of this protocol usually requires consulting services and customizing.
ARITECH Figure 57: ARITECH Model 1 alarm (based upon installation RUCA) Aritech model 1 alarms are always sent to group ARITECH_F, ARITECH_C, or ARITECH_B, depending on the datastream. Messages are sent with alarm description ARITECH_F, ARITECH_C, or ARITECH_B, depending on the datastream. Alarms are *SET with option *CALC. To define alarms, remove after *RESET. When HERSTEL occurs a general reset of all ARITECH alarms is issued for *ALL groups and *ALL alarm descriptions.
Module - eCAP BEMAC Valid manufacturer is BEMAC, valid model is DIANA 1 and DIANA 2. Bemac is based upon installation Clinique St-Vincent Rocourt. Figure 58: Sample Bemac protocol data Bemac alarms contain three fields, a pager number, a message and a tone code. Alarms are sent with group equal to the first parameter (for example, 866). The message is retrieved from the second parameter (for example, LOC 101B). When the third parameter is 0 the message is reset.
GENT For example, L:48-0:RC-1:SR-2:SS-3:SS-4SR means the alpha-messages are 48 bytes long, tone code 0 denotes *RESET alarm remove after *CALC, tone code 1 and 4 denote *SET alarm remove after *RESET, and tone code 2 and 3 denote *SET alarm remove after *SENT. Bemac is based upon installation Sint-Franciskus-Ziekenhuis Heusden-Zolder. The syntax is 'STX' + XXXXTZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZYYYYYP + 'LF' + 'CR' • XXXX = pager number • T = Tone-code • ZZ..
Module - eCAP Model 3400 The GENT model 3400 transmits binary datastreams of 56 bytes. The first bytes identify the alarm type. Currently, only Fire and Super Fire are processed. Figure 60: GENT Model 3400 The message is retrieved from bytes 25 to 56. The group is always FIRE and the alarm description is always FIRE. Alarms are *SET with the option: remove after *sent. 106 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Model VIGILIN EN54 Model VIGILIN EN54 Figure 61: Sample Model VIGILIN EN54 Currently, only records starting in 3rd line MCP or FIRE are processed. For FIRE alarms, the group is FIRE and the alarm description is FIRE. Messages are sent with the option: remove after *sent. For MCP alarms, the group is MCP and the alarm description is MCP. Messages are sent with the option: remove after *sent. The message is retrieved from the remaining part of the line after FIRE or MCP.
Module - eCAP The group is identified by the first fields, for example, 00001, and the message is identified by the second field (This is a sample message). Currently, alarms are sent with alarm description P0 and sent with option Remove after *sent. NIRA The valid manufacturer is NIRA and the valid model is *BASE. Nira is based upon installation Eeuwfeestkliniek Antwerpen.
STEAFA STEAFA Note: The Landis-Steafa interface was not ordered nor implemented and protocol information is provided on an as-is basis. Contact your software vendor for implementation. Figure 63: Sample Steafa protocol data TELEVIC The valid manufacturer is TELEVIC and the valid model is PROTOCOL CONVERTOR–L:xx, with xx between 01 and 99. Note: The extension – L:xx is new in release 2, and must be specified. The functionality is introduced to obtain more flexibility in message handling.
Module - eCAP BEERPUT -> BEERPUT • Look up the occurrence of the first space character NUR K100 -> 4 BEERPUT -> 8 • Keep the leading non-blank characters NUR K100 and 4 -> NUR BEERPUT and 8 -> BEERPUT • Keep the leading characters only, with length specified in L:xx NUR and L:03 -> NUR BEERPUT and L:03 -> BEE Table 8: Televic Example Length L:01 L:02 L:03 L:04 L:05 Original message Resulting alarm type Length NUR K100 N 1 WC 120 W 1 BEERPUT B 1 NUR K100 NU 2 WC 120 WC 2 BEERPUT BE
TELEVIC Figure 64: Sample Televic protocol data Televic is an extended two-direction protocol, which provides a number of protocol rules to keep the communication secure; for example, through sequencing each packet, requesting acknowledge string, handshake through clear-string, return of feedback on message delivery through what is called terugmelding string, error detection through checksum, and so on. Refer to the protocol specifications for details on Televic protocol.
Module - eCAP TYCO The valid manufacture is TYCO and the valid model is MINERVA 80. Figure 65: Sample MINERVA 80 protocol data An alarm is sent to the group MINERVA and the alarm description FIRE_EVACUATE, as well as a remove after *SENT and message BGU.FRONT HALL EAST. The group is always MINERVA and the alarm description comes from the first line when _ symbol appears. The message is retrieved from the second line, for example, BGU.FRONT HALL EAST. VSK Valid manufacturer is VSK.
VSK Valid models are: • DE LICHTERVELDE • OLV VAN VREDE • ST-JOZEF VSK is based upon the three installations defined in the model, with a different implementation for each, as illustrated in Figure 66: Sample DE LICHTERVELDE protocol data on page 113, Figure 67: Sample OLV VAN VREDE protocol data on page 114, and Figure 68: Sample STJOZEF protocol data on page 115.
Module - eCAP Figure 67: Sample OLV VAN VREDE protocol data 114 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
VSK Figure 68: Sample ST-JOZEF protocol data Fire alarms are sent to group VSK_F (fire alarm) with alarm description VSK_F, system errors are sent to group VSK_S (system errors) with alarm description VSK_S, detector errors are sent to group VSK_D (detector errors) with alarm description VSK_D.
Module - eCAP All alarms are *SET with remove after *RESET. When GENERAL RESET occurs in the datastream, all active alarms for the VSK input program are reset for all groups. Small differences between the three models are found, for example, in the level of detail in the messages that are sent (for example, FOUT BRANDCENTRALE in DE LICHTERVELDE, VSKFOUT in ST JOZEF and all details in OLV VAN VREDER).
WORMALD Table 10: F8000 REV EVACUA groups Model Group *BASE WORMALD_F. L:01 8 (group description: field GRP_Descr_str from table eKERNEL_GROUP) L:02 80 L:03 800 L:04 8000 G:BRAND BRAND (for all alarms, including fire and prealarms) 27/04/99 19:55:52 VOORALARM 0001-024 ION 9003 KEU EETPL This datastream results in *SET of alarm with alarm description WORMALD_P and message P9003 KEU EETPL, remove after *RESET. The group varies depending on the model.
Module - eCAP Table 12: RUCA 0000. Brand Boodschap MG 099 MLD 009 01:01:00 01.01.97 This datastream results in a *SET of alarm description WORMALD_F, with message Boodschap and remove after *RESET. The group varies depending on the model Table 13: F8000 REV EVACUA groups Model Group *BASE WORMALD_F. L:01 B L:02 Bo L:03 Boo L:04 Bood G:EIPM EIPM for all alarms 0001.
Chapter 15: Module - eESPA The module eESPA consists of one program. The program is eESPA.exe and is written in Visual Basic (v6.0). In general, the programs reside in the default directory C:\SOPHO Messenger@Net\Exe, unless otherwise implemented in your environment. Note: In release 4.0 an additional implementation is available that you can activate by specifying manufacturer ESPA and model VSK.
Module - eESPA section of the shortcut that initiates eESPA.exe. This shortcut is usually located in the Windows Startup group. Figure 69: Typical parameters in the shortcut In the example shown in Figure 69: Typical parameters in the shortcut on page 120, the eESPA.exe identifies itself as belonging to site 1, and specifies the location of eKERNEL through IP address *LOCAL and port 3114. The special value *LOCAL refers to the assigned IP address of the first NIC adapter found in the PC.
eESPA.exe Figure 70: Typical cfgrqs configuration request and its received cfgrpy configuration reply Refer to the appropriate sections on the database tables that define the received parameters for more information on each value. The information in this document is provided for informational purposes only; a detailed description of these internal inter-process communications is beyond the scope of this document.
Module - eESPA Figure 71: eESPA Connection tab showing a valid configuration Because the eESPA is designed to handle serial data communications with a number of paging systems, the eESPA must be configured before use. These values are returned through the reply that is sent on return of the request.
Functional description the distance between the DECT Messenger and the external-paging system is relatively small, so no extra hardware is needed. Once a link is established between eESPA and the paging system, the eESPA handles further communications and informs eKERNEL when relevant information is to be exchanged. For a detailed description of the ESPA4.4.4 protocol, refer to the proposal for serial data interface for paging equipment (Nov.
Module - eESPA eESPA handles only data blocks of type 1, Call to Pager data blocks. If another type of data block comes in, eESPA reacts by sending an ACK, but the data block is not processed. Delivery can also fail if a timeout occurs while sending the data block. The temporary master station, which is always the sending side, expects to receive an ACK within a timeout of eESPA_Timeout_n seconds. In the event of a timeout on sending a data block, the sending side tries to re-send the data block.
Data flow an offline list (also known as a black list) the polling interval is not disturbed by repeated timeouts of some slaves. The controlling station stops polling when data is waiting to be sent to one of the slaves, or when a slave has indicated that data is ready to send. The controlling station stops polling when a message request is received from the eKERNEL. The controlling station then creates a data block and sends this to the appropriate slave address.
Module - eESPA Logging In the Logging tab, only basic (default) logging is shown. Basic logging: incoming and outgoing data on the communication port (I:COM and O:COM), incoming and outgoing data on the socket communication with the eKernel (I:TCP and O:TCP), and warning information. To show and log additional information, choose the menu item eESPA > Logging > Detailed. The additional information is set in bold in Figure 76: Detailed logging information on page 126.
Manufacturer ESPA and model VSK Figure 77: Field model containing VSK Restrictions: • Configure eESPA as Control station value No. The remote system is then control station and handles polling. • Set the field Polling to No. • Only one data block is received at a time.
Module - eESPA Figure 79: 1[ENQ][EOT], no response For example, the FalconNet fire detection system alternatively polls itself and then the remote system (eESPA), as shown in Figure 80: FalconNet fire detection system on page 128. Figure 80: FalconNet fire detection system To improve problem determination, a more detailed and human readable logging is enabled when the model VSK is used. 128 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Manufacturer ESPA and model VSK Figure 81: Logging using model VSK DECT Messenger Installation and Commissioning — Book 1 March 2012 129
Module - eESPA 130 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Manufacturer ESPA and model VSK DECT Messenger Installation and Commissioning — Book 1 March 2012 131
Module - eESPA 132 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 16: Module - eESPA - sample MASTER (address 1) SLAVE (address 2) No data to be transferred 2ENQ EOT Master has data to be transferred 1ENQ (I want to send something) 2ENQ (Destination address) ACK (I am ready to receive data) Data Block1 1NAK Data Block1 ACK EOT EOT 2ENQ (polling) Master has data to be transferred (Slave is not ready to receive data) 1ENQ (I want to send something) 2ENQ (Destination address) 1NAK (Transmission error) EOT 1ENQ 2ENQ DECT Messenger Installation and Commissioning —
Module - eESPA - sample MASTER (address 1) SLAVE (address 2) 1NAK EOT Slave has data to be transferred 2ENQ 1ENQ (I have data for address 1) ACK (I am ready to receive data) DATA Block1 ACK DATA Block2 1NAK (Transmission error) DATA Block2 ACK EOT 2ENQ (Polling) EOT 2ENQ EOT ... 134 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 17: Module - eDMSAPI The module eDMSAPI consists of two separate programs. One program is eDMSAPI and is written in Visual Basic. The other program is called CSTA_Service.exe and is written in C++. In general, both programs reside in the default directory C:\SOPHO Messenger@Net\Exe, unless otherwise implemented in your environment. Overview eDMSAPI.exe The eDMSAPI is the Visual Basic component of the eDMSAPI module. The program communicates with two processes: the eKERNEL and the CSTA Service.
Module - eDMSAPI of the first NIC adapter found in the PC. You can determine the IP address using the IPCONFIG.exe command or in the appropriate sections of the Windows network settings. The keyword Log drive refers to the drive where the logging data must be stored; usually this is C: \SOPHO Messenger@Net\Log\. At startup, the eDMSAPI sends an XML string to eKERNEL requesting a configuration.
eDMSAPI.exe DMC DMC ETHERNET_DMC AVAYA AVAYA Dasgif Refer to the chapters of this document that deal with the database tables for more information on each value. A detailed description of these internal inter-process communications is beyond the scope of this document. The parameter specifies how much DECT extension is IoRegistered (can send data messages to the DECT Messenger application).
Module - eDMSAPI Figure 85: eDMSAPI tab Note that during call handling, the eDMSAPI tab shows an overview of current call states of each device. The window consists of two sections: • The Jobq section contains two job queues. One jobq is for the request from eKernel, and the other is for requests from external clients. This area is used to temporarily store requests that are waiting to be executed. For instance, when all the data paths are in use, new requests must wait until resources are available.
Overview of CSTA_Service.EXE Overview of CSTA_Service.EXE The CSTA_Service runs behind the scenes and communicates through CSTA.DLL with a PBX. The CSTA_Service acts as TCP server towards eCSTA. Communications to a PBX is done through CSTA.DLL, based upon Ethernet iS-Link CSTA interface on Ethernet. Details on these communications are beyond the scope of this document. The CSTA_Service has no user interface, but an icon appears in the tray when it is running.
Module - eDMSAPI Figure 87: Logging information Sample logging data is shown in Figure 88: Log example: initialization procedure on page 141. 140 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Logging Figure 88: Log example: initialization procedure DECT Messenger Installation and Commissioning — Book 1 March 2012 141
Module - eDMSAPI 142 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Logging DECT Messenger Installation and Commissioning — Book 1 March 2012 143
Module - eDMSAPI Figure 89: Log example: Message handling 144 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Logging DECT Messenger Installation and Commissioning — Book 1 March 2012 145
Module - eDMSAPI 146 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 18: Module - eFR Important: Due to the ongoing development of the DECT Messenger product suite, some modules that provide additional functionality may become available after the initial release of DECT Messenger 4.0. The following modules are described in this document but are not available at initial General Availability. • eFR • eLICENSE • eLOCATION • eSMS • eSNMP • eVBVOICE The eFR module is an add-on module and is licensed separately through the eLICENSE module.
Module - eFR Overview of monitoring The monitoring section covers four items. • OM section The OM section is not applicable for traditional and SIP DECT systems. • DISK section The DISK section verifies the state of a hard disk drive and notifies you on: - whether the disk drive is ready or not, - how much disk space is available. The status information is compared with a previous run for the same drive. You are notified if different information is found.
Overview of notification different information is found. You are notified when the socket is no longer "listening" or established, and you are notified when the socket returns "listening" or established. Overview of notification The notification part covers the following items. • The SMTP destinations refer to the notification based upon e-mail by means of SMTP protocol.
Module - eFR and active on the destination system, and all prerequisite conditions for named pipes messaging applies. Install module eFR Follow the steps in the next procedure to install the software. Installing module eFR 1. Double-click the EXE files delivered by Avaya. 2. Accept all defaults to install the software. After installation, a number of items ARE installed. Launch module eFR Follow the steps in the next procedure to launch module eFR.
License module eFR Do not logoff the desktop as this ends the monitoring application. License module eFR The module eFR is a licensed software module. The module eFR cannot be copied without valid agreement from Avaya. A software key is required to launch the program. If you do not have a software license key, the following window appears. Figure 90: Software license key required Contact Avaya to obtain an evaluation or a permanent key for using the software.
Module - eFR You can use Microsoft Internet Explorer to access files with XML extensions. These XML files must have the correct syntax or XML cannot be opened by Internet Explorer and results in a failure of module eFR. Destinations Destinations planning Follow the steps in the next procedure for destinations planning. Planning destinations 1. Determine what notification methods to use. Notification methods include technologies such as the following.
Destinations configuration Other transport mechanisms can require you to perform actions in the destination site, for example for NET SEND, the messenger service needs to be activated in the target PC. 3. Gather a list of destination users or destination peripherals with specific information to uniquely address the destination device. For example, for e-mail users you need the e-mail address of the target user and for SMS message, you need the extension number of the mobile GSM phone.
Module - eFR You can use the windows delivered with Notepad or Wordpad accessories maintain the XML file. On the internet, a number of free XML editors are available. These tools typically feature syntax checking, colored editing, and advanced editing features including copy and pasting of nodes. You can download the file XmlNotepad.msi (XML Notepad 2007) on the Microsoft web site. 2. Ensure that every destination has a unique value for the parameter id.
Destinations type NET • SMS SMS is used with SMS technology to send a SMS message to a destination mobile GSM phone. • SMTP SMTP is used when sending an e-mail message by means of an SMTP enabled mail server infrastructure, resulting in delivery of an e-mail message to the inbox of the destination addressee. • SNMP SNMP is used when sending SNMPv1 trap to a destination SNMP trap receiver. Depending of the selected notification type, define additional parameters as needed.
Module - eFR Figure 92: Parameter to Destinations type SMS The following figure illustrates Destinations type SMS. Figure 93: Destinations type SMS The following parameters are specific to SMS. • The parameter "description" refers to the name of the destination user, and allows you to assign a user name. For example, you can enter the first name and last name of the user. • The parameter "address" refers to the IP address of the system that runs the SMS_service process.
Destinations type SNMP Figure 94: Destinations type SMTP The following parameters are specific to SMTP. • The parameter "description" refers to the name of the destination user, and allows you to assign a user name. For example, enter the first and last name of the user. • The parameter "address" refers to the e-mail system IP address that runs the SMTP Server process. When the e-mail server supporting SMTP runs on the same system, use the loopback value 127.0.0.1.
Module - eFR Figure 95: Destinations type SNMP The following parameters are specific to SNMP. • The parameter "description" refers to the name of the destination party, and allows you to assign a destination system name. For example, you can enter the name of the SNMP receiving infrastructure. • The parameter "address" refers to the SNMP server IP address. Contact the SNMP receiving infrastructure administrator to obtain this value. • The parameter "port" refers to the SNMP server port number.
Monitoring Figure 96: Example of monitoring section and subsections The parameter interval, with a default value of 600, specifies the frequency at which the monitoring process takes place. When a value of 600 is specified, a delay of 600 seconds takes place between the last monitoring action and the next monitoring action. The eFR module captures information about the configured items roughly every 10 minutes. • The default value is 600 seconds • The minimum value is 60 seconds.
Module - eFR Monitoring type DISK The monitoring of disk drives is configured through the section in the XML file shown in the next figure. Figure 97: Monitoring type DISK The opening tag and the closing tag provide space for configuring the drives that must be monitored. You can define each drive that needs to be monitored in the section between . 160 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Monitoring type DISK Figure 98: Define drives for monitor type DISK The line shown in the following figure is the opening tag for a drive definition. Figure 99: Opening tag for a drive definition You must define two parameters. • Create the parameter "id" as a single upper case character that represents the drive name to be monitored. For example, entering C as the "id" indicates that the C: drive is monitored. This character is typically the drive letter you assign to the hard disk drive.
Module - eFR Figure 100: Required conditions met for monitor type DISK You define the message and the destinations to be informed in the following circumstances.
Monitoring type PING Figure 105: Drive not ready to be sent as SNMPv1 trap The following figure shows the message received by the destination device, implemented in DECT Messenger module eSNMP. The window shows that an SNMPv1 trap is received. The varbind 1 parameter contains the message. Figure 106: Message received by destination device Monitoring type PING You configure the monitoring of PING through the section starting with tag and ending with closing tag .
Module - eFR Figure 107: Monitoring type PING configuration The definition of a system that needs to be monitored with PING is done using a line. Figure 108: Monitoring type PING definition The following parameters are available. • Define the parameter id with a unique identifier of the monitored item. All items must have a unique identifier. For example, Lookback is an identifier. Avaya recommends that you specify a name meaningful to you to make future maintenance easier.
Monitoring type PING system and the larger the possible timeout, the less responsive the system. This means that the processing time increases, and the number of verifications decreases. The following figure shows an example of a definition of a system for PING. The message to be sent when a system is no longer responding to an ICMP check and the destinations informed are defined in the "NotResponding" section.
Module - eFR Monitoring type NETSTAT You can verify the configured list of connections using the NETSTAT monitoring capability. You can verify the TCP server connections in status "LISTENING", and you can verify the TCP client connections in status "ESTABLISHED". Figure 111: Monitoring type NETSTAT The configuration for NETSTAT is in the monitoring section starts with the opening tag and the closing tag .
Definition of a TCP server Figure 113: TCP server definition The definition of a connection contains the following parameters. • Define the parameter id (name) with a unique identifier of the monitored item. For example, value Mail Server defines the connection. Avaya recommends that you choose meaningful names name for the parameters. • Define the parameter "port" to identify the port number. For example, use the value 25 specified the port used for SMTP servers. • Define the parameter "state".
Module - eFR Figure 115: Monitoring the state of the TCP server If the SMTP Server is stopped by an administrator, the socket no longer is "listening" on port 25 and the message "Mail Server is down" is sent as an SNMPv1 trap to the configured SNMP destination. Definition of a TCP client A sample definition of a connection is shown in the following figure. The definition is very similar to the definition of a TCP Server, but the state is "established" instead of "listening".
Sample e-mail address and the port the server listens to. The following figure illustrates that the server listens on port 3102. Figure 117: TCP client/server connection If connection is successful, a connection is established between the client and the server. In a NETSTAT command window, a line appears illustrating that a TCP connection is found on port 3102 with the state ESTABLISHED. Figure 118: NETSTAT command window The previous figure shows the client address and port in the third column, 10.
Module - eFR Figure 119: Sample e-mail 170 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 19: Module - eGRID The eGRID application gives you a view of the different tables in the databases. You can start the eGRID.exe application without command line parameters. At startup, the window in Figure 120: eGRID startup window on page 171 is shown: Figure 120: eGRID startup window Seven drop-down lists are available at the top of the window. From left to right, the functions of these dropdown lists are as follows.
Module - eGRID • Use the third drop-down list to select a table.
Figure 121: eGRID with Show help mode DECT Messenger Installation and Commissioning — Book 1 March 2012 173
Module - eGRID Figure 122: eGRID with View another table mode 174 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Figure 123: eGRID grouping functions Because eGRID is the preferred access method for maintenance, an extra functionality is implemented to optimize flexibility. This functionality is referred to as Data Filtering and is handled through the command buttons Subset, Clear filter, and an entry field between the column heading and the first row. Figure 124: eGRID Data Filtering on page 176 illustrates the usage of Data Filtering.
Module - eGRID Figure 124: eGRID Data Filtering Look at the column header to find out what data type the field has. Because the filtering function is based upon SQL instructions, you must specify subset data that results in valid SQL grammar: • Selecting partial data (omitting training characters) is valid only for string fields with the extension _str. For example, DEV_OUTPGM_str can be part of a subset with e, eD, eDM, and so on.
Important: Ensure the eGRID module is not made available for unauthorized access. Remove the shortcut where applicable. The eGRID module provides direct access to the tables in the database. There is no password protection on this module.
Module - eGRID 178 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 20: Module - eIO Overview The eIO module is a stand-alone application that communicates with eKERNEL. The module is capable of controlling and measuring Distributed I/O peripherals of National Instruments. eIO offers support for analogue input, digital input and digital output. See Install PC - Step 3 - National Instruments for a detailed explanation of installation and configurations issues of the modules, and the supporting Measurement Studio components (FieldPoint Explorer and OPC Server).
Module - eIO value is usually specified, because eKERNEL and eIO both share the same network adapter. When eIO is running on a different computer, the IP address of the eKERNEL must be specified. • eKernel port Refers to the port number eKERNEL listens to for that specific eIO instance. This port is defined in the eKERNEL_TCPCLIENT table. • Log drive Specifies the drive letter where logging files must be stored.
Startup Figure 129: eIO configuration request and response When the configuration is received, the eIO updates the configuration information on the Connections tab, as shown in Figure 130: eIO Connections update on page 182. During this time, the eIO is temporarily less responsive to user input. This is due to the large number of OPC Server connections that take place at startup time.
Module - eIO Figure 130: eIO Connections update eIO Modules Select the eIO tab to see a panel with details of the available modules and contacts. Use the drop-down list at the right-hand side of the window to select the module to view. Analogue input When you select an analogue input module (FP-AI-100), a window similar to the one in Figure 131: eIO analogue input modules on page 183 is shown. For each module a graphical display shows the available contacts.
Analogue input Figure 131: eIO analogue input modules For each module, the URL is shown, and the module identifier. When you hold the mouse pointer over the status area of a contact, detailed information is shown. An example of the information provided is as follows: Min (set: 02,000000 - reset: 08,000000) Max (reset: 14,000000 - set: 20,000000) The chart shown in Figure 132: Analogue input ranges on page 184 explains the behavior of these settings.
Module - eIO Figure 132: Analogue input ranges Note: Alarm values are given in pairs. Both maximum and minimum alarms are set and reset with different values. This was implemented to prevent continuous switching between set and reset when measured values are in the neighborhood of alarm values. • Left-click in the status zone of an analogue contact to display the currently measured value.
Digital output (discrete output) Figure 133: Digital Input module information Note: When the value of a contact changes from Off to On or from On to Off, the Before and After fields are updated with the status of the contact before the change occurred and the status of the contact after the change occurred. The Change field is also updated with the new value.
Module - eIO Figure 134: Digital Output module information Note: When the value of a contact changes from Off to On or from On to Off, the Before and After fields are updated with the status of the contact before the change occurred and the status of the contact after the change occurred. The Change field is also updated with the new value. Note: You can also change the status of the contacts to On or Off by using the mouse to drag the switch to the On or Off position.
Logging Figure 135: eIO logging The log files on disk contain the same information as shown on-screen. On the next few pages, Figure 135: eIO logging on page 187 through Figure 140: Log example: Termination on page 189 show examples of log information saved on disk during different steps of eIO setup and use.
Module - eIO Figure 137: Log example: Configuration procedure 188 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Logging Figure 138: Log example: Binding to OPC Servers Figure 139: Log example: Message Request Figure 140: Log example: Termination DECT Messenger Installation and Commissioning — Book 1 March 2012 189
Module - eIO 190 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 21: Module - eKERNEL General eKERNEL is the core engine of the DECT Messenger, and is in the basic implementation the only module that accesses the database. The eKERNEL receives information from various input sources, and exchanges information with various output sources. Communication with eKERNEL is performed through TCP/IP stream sockets, where the eKERNEL acts as a server. The other modules that communicate to the eKERNEL act as clients.
Module - eKERNEL License Manager The Avaya DECT Messenger package is secured by a licensing system, to prevent unlicensed usage of certain modules and clients. Figure 142: License Manager At startup, the eKERNEL searches for a valid license. If there is no valid license (because, for instance, the license expired or licensing system is not installed), the eKERNEL program aborts. To determine if the installed licensing system is valid, use the Avaya License Manager.
Equipment and Functionality models Equipment and Functionality models The licensing system distinguishes between equipment models and functionality models. • The following models are assigned as equipment: eCAP, eESPA, eIO, eLOCATION, eSMS, and eSNMP. • The following models are assigned as functionality: eWATCHDOG, eBACKUP, eCONFIG, eDMSAPI, eASYNC, eCSTA, eWEB, eSMTP, eSMTP_server, eAPI, and eVBVoice.
Module - eKERNEL license cannot be bound or no correct functionality is available, the eKERNEL tab-page is not updated, and the crossed-through key icon remains. eAPI and eWEB eAPI and eWEB do not send configuration requests. To ensure that eAPI and eWEB are licensed properly, eKERNEL checks these two functionality models individually. If eAPI and eWEB are found in the License system, the TCP/IP ports for any clients of this kind are opened.
External interfaces menu command: eKERNEL > License > functionality as shown in Figure 144: Adding license functionality on page 195. Note: eKERNEL makes this same check automatically at midnight. Note that rechecking all licensing can take a little time. Figure 144: Adding license functionality If a license is installed with fewer equipment licenses than there are clients that need them, the clients that are no longer licensed continue to function until the license is rechecked.
Module - eKERNEL Database The eKERNEL application is the only application that communicates directly with the databases. Every external application receives its configuration from eKERNEL. There are two databases. One is named Messenger_CFG.mdb, and another is named Messenger_data.mdb. Both databases are in Microsoft Access 2000 format, and are processed through applications written in Microsoft Visual Studio 6.0 (Visual Basic and C+ +). In release 4.
Menu options Menu options • File > Exit This option closes the eKERNEL application. • eKERNEL > Reset all alarms This option clears all active alarms in the data database. • eKERNEL >Refresh logfiles This option closes and reopens the log file of the eKERNEL application. Perform this action before opening the log file for the current day, so all data that is still in memory is copied to the log file. • Service > Delete all data records This function deletes all the records of the selected table.
Module - eKERNEL Figure 145: Watchdog enabled Guarding For every input program, the administrator can configure a guarding facility, as shown in Figure 146: Guarding information on page 199. If guarding is activated for a specific input program, an indication is given in the Client information frame for every TCP/IP client.
Guarding Figure 146: Guarding information DECT Messenger Installation and Commissioning — Book 1 March 2012 199
Module - eKERNEL 200 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 22: Module - eLICENSE Important: Due to the ongoing development of the DECT Messenger product suite, some modules that provide additional functionality may become available after the initial release of DECT Messenger 4.0. The following modules are described in this document but are not available at initial General Availability. • eFR • eLICENSE • eLOCATION • eSMS • eSNMP • eVBVOICE The eFR module is an add-on module and is licensed separately through the eLICENSE module.
Module - eLICENSE add-on modules are activated. In the majority of the cases, add-on modules, such as eFR, reside on the MESSENGER system running eKERNEL. However, when add-on modules are installed on different systems, install eLICENSE on the systems where add-on modules are installed. Installing eLICENSE 1. Locate and open the eLICENSE module from the CD-ROM image, found in directory 09 - Add-ons - 2008.04.23 > 2008.04.23 – eLICENSE. 2. Double-click the SETUPEX.EXE file to install. 3.
Run module eLICENSE 2. Save the XML file by selecting File > Save Fingerprint. 3. Accept the default path C:\SOPHO Messenger@Net\Xml . The default filename is usually your computer name with extension Xml. For example, on computer MESSENGER the file is MESSENGER.Xml. The resulting XML file contains 7 parameters retrieved from your hardware and operating system. 4. Use Internet Explorer to open the XML file. Double-click the file residing in C: \Program Files\Messenger@Net\Xml.
Module - eLICENSE Applying the key The license file name contains the originating computer name, for example, MESSENGER, as well as the licensed module name, for example, eFR. Therefore, if you request a license for computer MESSENGER for add-on eFR, the filename is MESSENGER_eFR.reg. A sample license file follows. Figure 147: Sample license file Applying the license file 1.
Disaster recovery Figure 148: Invalid license key warning If this occurs, request an updated license file. Note: If you cannot wait to restart the system, type the word Evaluation in the text box in the invalid license key warning, shown in Figure 148: Invalid license key warning on page 205. This gives you access to the module, but it does not apply a permanent key. By entering the word Evaluation, you can continue to run the application until you receive a new valid license for the changed system.
Module - eLICENSE 206 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 23: Module - eLOCATION Important: Due to the ongoing development of the DECT Messenger product suite, some modules that provide additional functionality may become available after the initial release of DECT Messenger 4.0. The following modules are described in this document but are not available at initial General Availability. • eFR • eLICENSE • eLOCATION • eSMS • eSNMP • eVBVOICE The eFR module is an add-on module and is licensed separately through the eLICENSE module.
Module - eLOCATION Figure 149: eLocation module keywords The following keywords are used to start the eLocation module. • The "site" keyword indicates the site that is assigned to the eLOCATION module • The "eKernel address" keyword indicates the IP address that is assigned to the eKERNEL module. The eLOCATION contacts this IP address to connect to the eKERNEL • The "eKernel port" keyword indicates the port number that is assigned in the configuration for the eLOCATION client instance.
Initialization Figure 151: eLocation configuration connections tab The logging tab shows logging information.
Module - eLOCATION Program activity When the startup phase is done, eLOCATION has two permanent socket connections. • One socket connection is established with the eKERNEL and is used to exchange "location requests" and "location reply" data flow. • The other socket connection is established with the DAP Controller PC (DCC) and follows a proprietary protocol to retrieve location information of SIP DECT extensions.
Program activity Figure 154: Idle state of system at startup After the processing of a location request, the panels are updated as shown in the following figure. Figure 155: eLocation updated panels The "history" panel keeps track of all location request results. In the previous figure several requests with positive feedback are presented in a history tab. The "logging" panel in the following figure illustrates the detailed data exchange with the DAP Controller for the previous requests.
Module - eLOCATION Figure 156: Logging panel Architecture There are several steps involved to make eLOCATION operational. The effected items in the setup of the functionality follow. • One special number with '*LA' type should be defined in the eDMSAPI module in the eDMSAPI_INBOUND table (i.e. number 112 or 911). In the following figure, eCONFIG is used to illustrate the configuration process. 212 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Architecture Figure 157: eConfig illustrates the configuration process In the following two figures, extension 112 with type '*LA' is defined for location detection.
Module - eLOCATION Figure 158: Module eDMSAPI • The next item that you must define is the correct record in the table eDMSAPI_INBOUND_EVENT for the special number defined above in the same manner as it is done for all other extensions. The following figure shows an example of the special number configuration in the eDMSAPI_INBOUND_EVENT table. 214 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Architecture Figure 159: Module eDMSAPI inbound event The following figure illustrates detailed configuration for a special number in eDMSAPI_INBOUND_EVENT table.
Module - eLOCATION Figure 160: Module eDMSAPI inbound event - detailed configuration • Next the eKERNEL module contacts the eLOCATION module to find out the physical location of the SIP DECT user. In DECT Messenger prior to release 2.9.10, the eKERNEL contacts only the eLOCATION of the same site and the same area as the eDMSAPI module that alerted the alarm. This means if the alarm was detected from eDMSAPI site 1 area 1, eKERNEL only contacts eLOCATION site 1 area 1.
Architecture Controller. This DAP Controller, 192.168.32.10, is handled by eLOCATION site 1 area 2 as shown in the following figure. Figure 161: Configuration of eLOCATION For each DAP Controller and each eLOCATION instance, a number of associated definitions are required in the tables eLOCATION_BOARD, eLOCATION_RPN, and eLOCATION INBOUND_RESULT. The eLOCATION_BOARD defines the SIP DECT extensions that are registered in the DCC board.
Module - eLOCATION Figure 162: Module eLOCATION board definition Figure 163: Module eLOCATION board 00 definition 218 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Architecture • Next the eLOCATION_RPN table must be populated with records for every RPN known in the DAP Controller configuration. In the following figure, RPN "11" up to RPN "13" is defined. A generic catchall definition is indicated with a "?". For each RPN, we define a description in words that tell the end-user the physical location of the RPN.
Module - eLOCATION Figure 165: eLOCATION_INBOUND_EVENT table In the sample in the following figure, alarms from the eDMSAPI input program 12901, site 1, area 2 and all calling devices, that called special extension 112, result in an alarm sent to group 3000. 220 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Architecture Figure 166: eLOCATION inbound result SOS message from eDMSAPI The following figure shows an example of a message sent to the group as defined in the Message parameter. Figure 167: SOS message sent to group The eKERNEL parses the data stream and performs the appropriate replacements of the replacement values [calling number], [location] and [location time]. Note: The "Site ID eLOCATION module" equals 1 and the "Area ID eLOCATION module" equals 1 in the example shown in the previous figure.
Module - eLOCATION number] is introduced in release 3.0. In release 3.0 and subsequent releases, when the system configuration configures a device with a visual DNR, this DNR is used to format a message when it contains [Calling number]. The end-used is confronted with the visual DNR instead of the device id. 222 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Chapter 24: Module - eSMS Important: Due to the ongoing development of the DECT Messenger product suite, some modules that provide additional functionality may become available after the initial release of DECT Messenger 4.0. The following modules are described in this document but are not available at initial General Availability. • eFR • eLICENSE • eLOCATION • eSMS • eSNMP • eVBVOICE The eFR module is an add-on module and is licensed separately through the eLICENSE module.
Module - eSMS • an antenna for the TC35i, included in TC35i • a SIM card of mobile provider of choice with a PIN and a PUK code Follow the steps in the next procedure to install the Siemens TC35i module. Installing the Siemens TC35i module 1. Install the SIM card in a regular mobile phone. 2. Power on the mobile phone. 3. Refer to the SIM card information and obtain the valid PIN and PUK codes. You usually need the pincode at startup. 4.
SMS service SMS_service.exe and SMS_service.ini are two resources related to SMS_service functionality. Configure SMS_service through the .INI file. The default values suit most environments. You can change the parameter COM Port if COM1 is not available. Change the value according to your environment, for example specify 3 if COM3 is available. In the sample file illustrated in Figure 168: Default configuration section on page 225, there is a single INI file.
Module - eSMS For example, if you have a need for high-level redundancy, you can use SIM cards from two different mobile providers. If one box of SIM card fails, you can use the other box. You setup a configuration to first send to devices on eSMS area 1, mobile provider 1, and if NACK occurs, you use alternative devices defined on eSMS area 2, mobile provider 2. You alter the shortcuts referring to the desired configuration section shown in the following figure.
eSMS module Figure 173: SMS_service operational The module polls the box to find out if inbound messages are received from external mobile phones through the mobile network. The logging file can feature the AT+CMGL loop condition during the idle time. eSMS module The support for SMS messaging is implemented with different processes. The eKERNEL process integrates with eSMS process, and eSMS process integrates with SMS_service process.
Module - eSMS Figure 174: Startup values prompt The command line parameters are shown in the following figure. Figure 175: Command line parameters The module eKERNEL responds to the with . This configuration is retrieved from the Messenger_CFG database table. In native mode, the configuration is retrieved from the eSMS table. This table contains, for example the IP address and the port number used to connect to the SMS_service process.
eSMS module Figure 177: eSMS Main screen The section on the left features outbound messaging and the section on the right features inbound messaging. Figure 178: Inbound and outbound messaging The tab connections shows the details of the configuration received from the eKERNEL.
Module - eSMS Figure 179: Configuration details in tab connections Outbound messaging The eSMS module can send outbound SMS messages to mobile phones. It connects to the mobile world through an SMS box, controlled by the SMS_service process. The eSMS module contacts the SMS_service process during the messaging delivery process. The message delivery process bidirectional. The eSMS sends a request to the SMS_service and the SMS_service sends a reply to the eSMS module.
Outbound messaging Figure 181: Details under logging tab The logging files provide more details on the data exchange. Figure 182: Logging files When message delivery is successful, positive feedback is returned to eKERNEL. This XML datastream contains the characters. When message delivery fails, a negative response is sent to eKERNEL, as shown in the following figure. The window in the following figure shows that the eSMS cannot connect to the SMS_service due to a network error.
Module - eSMS Figure 183: Example of message delivery failure Inbound messaging The eSMS module also handles inbound SMS messages. These messages are received on the GSM box, and transferred to the eSMS module to be processed in DECT Messenger by eKERNEL. For this purpose, additional tables eSMS_INBOUND and eSMS_INBOUND result are added to the Messenger_CFG database. The eSMS module communicates with the SMS_service through a separate TCP connection.
Inbound messaging Figure 184: Reception of an inbound SMS message More details on this data exchange are given under the logging tab, as shown in the following figure. Figure 185: Logging tab The logging files provide more details on the data exchange, as shown in the following figure.
Module - eSMS Figure 186: Logging files Configuration The eSMS module is configured through the eCONFIG module. The eSMS module requires eCONFIG 2.9.10 or above. The following eight figures illustrate the configuration process for both outbound and inbound messages. 234 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Configuration Figure 187: eCONFIG configurator Figure 188: Sign on to DECT Messenger configurator DECT Messenger Installation and Commissioning — Book 1 March 2012 235
Module - eSMS Figure 189: eSMS area IBS 1 236 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Configuration Figure 190: Module eSMS inbound definitions Figure 191: Module eSMS - Inbound DECT Messenger Installation and Commissioning — Book 1 March 2012 237
Module - eSMS Figure 192: Module eSMS - Inbound ACL Figure 193: Module eSMS eKERNEL_DEVICE_FORMAT 238 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Web interface Figure 194: SMS Service logging tab Web interface When eSMS is configured, the new Web Administrator interface features a window where you can send an SMS message from the web interface. This window retrieves all defined devices from the eKERNEL_DEVICE table configured for the eSMS output program.
Module - eSMS Figure 195: Select destination 240 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Web interface Figure 196: Enter message information DECT Messenger Installation and Commissioning — Book 1 March 2012 241
Module - eSMS Figure 197: Logging tab 242 DECT Messenger Installation and Commissioning — Book 1 Comments? infodev@avaya.
Index Add-on modules .......................................................201 Add—On module ..........................................................9 adding a device ..........................................................57 Alarm information .....................................................100 Alarms ......................................................................101 Alexianen Bouchout installation ................................116 Analogue input .........................................
eKERNEL.exe ...........................................................119 ELDAD ......................................................................104 eLICENSE ................................................................201 eLICENSE installation ..............................................201 eLICENSE running ...................................................202 eLOCATION architecture ..........................................212 eLOCATION initialization ..........................................
P PING .........................................................................158 PING section ............................................................148 Planning destinations ...............................................152 PROTOCOL CONVERTOR-L ..................................109 xx ........................................................................109 R Real world examples of using eAPI ............................70 Removing modules .....................................................
