DECT Messenger Installation and Commissioning — Book 2 Avaya Communication Server 1000 7.5 NN43120-301, 03.
© 2012 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes.
Contents Chapter 1: Module - eSMTP................................................................................................ 15 Initialization............................................................................................................................................... 15 Output program activity............................................................................................................................. 17 Logging..........................................................
Chapter 8: Module - eWEB................................................................................................. 127 Sign-on procedure..................................................................................................................................... 127 Sign-off procedure............................................................................................................................ 128 Send DMS-API Message................................................................
Configuration of advanced devices.................................................................................................. 175 Configuration of advanced groups................................................................................................... 178 Configuration of advanced users...................................................................................................... 180 Expert................................................................................................
eDMSAPI _PBX_address_str........................................................................................................... 210 eDMSAPI_PBX_port_str.................................................................................................................. 210 eDMSAPI_PBX_type_str.................................................................................................................. 211 eDMSAPI_PBX_licence_str...........................................................................
eESPA_DataId_Group_str................................................................................................................ 227 eESPA_Group_default_str............................................................................................................... 229 eESPA_DataId_Msg_str................................................................................................................... 229 eESPA_Msg_default_str.........................................................................
eIODI_Site_id_n............................................................................................................................... 255 eIODI_Area_id_n.............................................................................................................................. 255 eIODI_Module_str............................................................................................................................ 255 eIODI_Contact_str.........................................................
DEV_OUTPGM_str.......................................................................................................................... 278 DEV_OUTPGM_facility_str.............................................................................................................. 279 DEV_Visual_dnr_str......................................................................................................................... 279 DEV_Descr_str............................................................................
GRP_InPGM_id_n............................................................................................................................ 296 GRP_Name_str................................................................................................................................ 296 GRP_Descr_str................................................................................................................................ 297 GRP_Comments_str..............................................................
eKERNEL_HOLIDAY parameters............................................................................................................. 315 Holiday_str....................................................................................................................................... 315 Holiday_Comments_str.................................................................................................................... 316 Chapter 34: Table: eKERNEL_INPGM................................................
eLOCIR_Calling_dev_str.................................................................................................................. 348 eLOCIR_eLOC_Site_id_n................................................................................................................ 348 eLOCIR_eLOC_Area_id_n............................................................................................................... 348 eLOCIR_GRP_Name_str.............................................................................
eSMTPS_Poll_intv_n....................................................................................................................... 362 eSMTPS_Email_dir_processed....................................................................................................... 362 eSMTPS_Email_keep_processed_n................................................................................................ 363 eSMTPS_Email_dir_error_str................................................................................
WSCA_Site_id_n.............................................................................................................................. 375 WSCA_Area_id_n............................................................................................................................ 375 WSCA_Script_id_n........................................................................................................................... 375 WSCA_UserID_str.................................................................
Chapter 1: Module - eSMTP The eSMTP module is an output program that receives message requests from the eKERNEL module. The eSMTP connects to an SMTP server, and delivers mail requests to the mail server according to the RFC821 specifications. This involves a sockets connection between eSMTP and the SMTP server of choice. For such a connection, eSMTP is TCP client and the SMTP server is TCP server, listening on port 25. Initialization The eSMTP module is started by means of a shortcut.
Module - eSMTP Figure 2: eSMTP configuration request When the configuration is received, a window similar to the one shown Figure 3: Configuration information on page 16 opens. The configuration can be viewed in the Connections tab. Figure 3: Configuration information 16 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Output program activity Output program activity The eSMTP module is now ready to receive message requests from eKERNEL. These requests are handled on a first-in first-out basis. The requests are received in the format shown in Figure 4: Message request format on page 17. Figure 4: Message request format The message requests are executed one at a time, by means of a TCP sockets connection to the SMTP server of choice.
Module - eSMTP Request handling 1. The request is analyzed and the required keywords are extracted and shown to the right. The left-hand side of the window shows the actual dialog with the SMTP server. See Figure 6: Request queue with extracted keywords on page 18 for an example of an active message. Figure 6: Request queue with extracted keywords 2. The eSMTP module sends the status of the request back to the eKERNEL. This status can either indicate a positive acknowledge or a negative acknowledge.
Logging Figure 8: Example of mail produced by eSMTP module Figure 8: Example of mail produced by eSMTP module on page 19 shows an example of the raw data of the mail that is produced by the eSMTP module. Figure 9: Raw data of mail produced by eSMTP module Logging The eSMTP application provides logging both on-screen and on disk. Figure 10: eSMTP on-screen logging on page 20 shows the on-screen logging, displayed on the Logging tab.
Module - eSMTP Figure 10: eSMTP on-screen logging The following two figures show an example of a log file on disk, as viewed with a text editor. 20 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Logging Figure 11: Log files on hard disk — part 1 DECT Messenger Installation and Commissioning — Book 2 March 2012 21
Module - eSMTP Figure 12: Log files on hard disk — part 2 Relaying and Routing Important: A common configuration error, related to relaying and routing settings, occurs when eSMTP tries to deliver a message to a mail destination user that is not residing in the same domain, as shown in Figure 13: Relaying and Routing error on-screen on page 23. 22 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Relaying and Routing Figure 13: Relaying and Routing error on-screen The error is usually recorded in the log files with a message similar to the one shown in Figure 14: Relaying error log (relay failed) on page 23. Figure 14: Relaying error log (relay failed) Other messages can be shown instead, for example, 550 - prohibited, 550 - Unable to relay, and so on. To correct this issue, consult with the system administrator regarding the rights granted for routing and relaying in the module.
Module - eSMTP Windows SMTP server In Windows SMTP Server (part of the Internet Information Server), you can for instance grant access by clicking Start on the Windows task-bar, and choosing Settings > Control Panel > Administrative Tools > Properties > Internet Service Manager. Figure 15: Setting SMTP relay on page 24 illustrates the settings needed to grant the SMTP server access to relay from both 127.0.0.1 and 10.110.50.138. These addresses are the addresses where eSMTP modules reside.
Relaying and Routing Domino (Lotus Notes) The same techniques discussed for Windows SMTP server on page 24 can be implemented on other SMTP servers. For example, in Domino (Lotus Notes), you can allow inbound SMTP requests from other parties (eSMTP).
Module - eSMTP 26 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 2: Module - eSMTP_server The eSMTP_server module is a member of the input program family. Therefore, the eSMTP_server is capable of generating alarms to eKERNEL. The name eSMTP_server can be rather confusing. In fact, there is no SMTP server functionality implemented in the module. This means the application is not acting as an SMTP server, and is not listening on port 25 for inbound SMTP requests.
Module - eSMTP_server Figure 18: Example of inbound e-mail Important: There are many competing specifications for mail formatting. A basic implementation is specified in RFC821. Many other specifications were added, for example, RFC1251 described the MIME format. The current release of eSMTP_server is not designed to be fully compatible with all available functionality embedded in e-mail messages.
Keyword processing Keyword processing For the purpose of illustration, examples in this chapter ignore all mail contents, and process only the following keywords: • x-sender. The value of the x-sender tag is stored. • x-receiver. The value of the x-receiver tag is stored. • Subject. The value of the Subject: tag is stored. Because the x-sender and x-receiver tags are Microsoft proprietary, the module eSMTP_server also looks for Fromand Tokeywords, if the x-sender and x-receiver tags are missing.
Module - eSMTP_server The eKernel address keyword denotes the IP address that is assigned to the eKERNEL module. The eSMTP_server contacts this IP address to connect to the eKERNEL. • eKERNEL Port The eKernel Port keyword denotes the port number that is assigned in the configuration for the eSMTP_server instance. On startup, the eSMTP_server application attempts to connect to the eKERNEL, as shown in Figure 21: eKERNEL connection attempt on page 30.
Initialization Figure 22: Configuration request Figure 23: Configuration reply When the configuration is received, the Connections tab of the eSMTP_server module is updated with information similar to what is shown the panel shown in Figure 24: Updated eSMTP Connection information on page 31.
Module - eSMTP_server Activity of eSMTP_server The eSMTP_server module is now ready to send message requests to eKERNEL. These requests are sent on a first-in first-out basis. Click the eSMTP_server tab to view request processing, as shown in Figure 25: Request processing shown on the eSMTP_server tab on page 32.
Activity of eSMTP_server Figure 26: Default inbound mail (drop) directory Inbound mail messages are processed one by one. During processing, a window opens similar to the one shown in Figure 27: Mail processing on page 33.
Module - eSMTP_server This is a long filename and refers to the filename of the e-mail message that is being processed. These names were generated by the Microsoft SMTP Server component. • From field Isolated from the tag. • To field Isolated from the tag. • Subject field Isolated from the Subject: tag. With these values, the eSMTP_server produces a message request for eKERNEL, as shown in Figure 28: eSMTP message request for eKERNEL on page 34.
Activity of eSMTP_server Figure 30: Specifying the location to file accepted messages • Message Rejected If the message is not accepted in eKERNEL, a negative reply is sent, as shown in Figure 31: Message reply: rejected on page 35. Figure 31: Message reply: rejected Refer to the log files of eKERNEL (see the eKERNEL > Logging tab) to find out why the message was not accepted. Following is an example of the informational message that is shown: S: Alarm not processed.
Module - eSMTP_server Figure 32: Specifying the error target directory Note: Because these rejected inbound mail messages are still available online, you can let the administrator determine the cause of the problem, and if necessary adjust the configuration settings. In many cases, the problems are related to wrong configuration, or processing of unexpected mail messages (spawn mail, hackers, and so on).
Logging Figure 33: On-screen logging Figure 36: Log file on disk — part 3 on page 40 shows the log file stored on disk.
Module - eSMTP_server Figure 34: Log file on disk — part 1 38 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Logging Figure 35: Log file on disk — part 2 DECT Messenger Installation and Commissioning — Book 2 March 2012 39
Module - eSMTP_server Figure 36: Log file on disk — part 3 40 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 3: Module - eSNMP 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 - eSNMP Figure 37: eSNMP parameters missing The module eKERNEL responds to the with . This configuration is taken from the Messenger_CFG database table eSNMP. The Messenger_CFG database table contains, for example, the port number 162 that is used to receive SNMPv1 and SNMPv2 traps. See the following figure. Figure 38: Messenger_CFG database table Figure 39: eSNMP connections The SNMP traps are shown under the eSNMP tab. SNMP traps are ASN.1 BER-encoded.
Architecture Figure 40: eSNMP traps The eSNMP module can determine the originator of the SNMP trap. For example, in Figure 40: eSNMP traps on page 43, an SNMPv1 trap was received from 10.128.84.22. The SNMP trap also contains some “header” information, such as the following. • community, for example public • enterprise oid, for example 1.3.6.1.4.1.28088.32.1 • generic trap (value between 0 and 6) • specific trap (0 or >0) • a timestamp Optionally, additional parameters can be received.
Module - eSNMP Figure 41: Parameters used by eKERNEL to generate a message The eKERNEL module has two configuration tables to support the eSNMP module. The eSNMP table provides configuration items for an instance of eSNMP, and provides the information in and parameter exchange. The eSNMP table can also define automatic creation of trap definitions in the eSNMP_TRAPS table, and provides default values for those automatically created definitions in eSNMP_TRAPS.
Architecture When the eSNMP table specifies auto-configuration, the eSNMP_TRAPS are automatically populated with definitions as new traps are received. This allows system administrators to gradually optimize configurations by updating the definitions, and associating alarm identifiers, groups and message. See the following figure.
Module - eSNMP The message can be a combination of fixed text and replacement values. In many cases, SNMP traps provide a list of variable binding parameters. The eSNMP module supports up to nine varbind parameters. The value of those parameters can be embedded in the resulting message. The following figure shows a sample of such a definition. Figure 46: Message with varbind parameters Supported replacement values are listed in the following figure.
Send SNMP Message for Win32 Send SNMP Message for Win32 A sample program of Send SNMP Message is available on the DECT Messenger CD in the directory 09-Add-ons\Send SNMP Message. When you install the program, it resides in the directory C:\Program Files\Send SNMP Message\Exe and is called Send SNMP Message. When the program is launched, a window appears and defaults to IP address 127.0.0.1 and port 162.
Module - eSNMP Send SNMP Message for Web The Web Administrator provides a web-based interface to send SNMPv1 traps from the Web Administrator to the module eSNMP. The implementation is based upon PHP script and hosted in the Apache HTTP Server on the Messenger platform. Since sending SNMPv1 traps is reserved for system administrators, the SNMP trap is reserved for Web Administrator users with a security level equal to administrator.
Send SNMP Message for iSeries Send SNMP Message for iSeries A similar program called Send SNMP Message is available for the IBM eServer iSeries platform. This program is also referred to as IBM AS/400 or IBM i5. This Send SNMP Message for iSeries features a command line interface, and is easily embedded in existing legacy code written on CLP, RPG, RPG/LE an so on. Figure 51: Send SNMP message (SNDSNMPMSG) Contact Avaya product support to obtain more details.
Module - eSNMP 50 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 4: Module - eTM The module eTM is an application that is represented as a small icon in the system tray on the bottom right-hand side of the desktop. This tray is usually populated with other applications, as shown in Figure 52: System Tray on page 51, where the eTM icon is shown to the immediate left of the clock. Figure 52: System Tray When the mouse is moved over the icon in the system tray, right-click to open the menu shown in Figure 53: Open Task Manager on page 51.
Module - eTM Figure 54: eTM Task Manager Note: The window contents vary according to your configuration settings. The window is composed of the following sections: • The upper section presents a tree-view of the environment, and contains a hierarchical overview of all configured tasks. Every task has the following keywords and values: - The keyword PID denotes the process identifier of the task. This identifier is formatted as a 10digit numeric value.
Value Description 4 Window is restored to its most recent size and position. The currently active window remains active. 6 Window is displayed as an icon. The currently active window remains active. - The keyword Shortcut denotes the command line parameter that is used to launch the process. • The second section shows a log of the changes in the state of the tasks.
Module - eTM The Windows Registry Editor (regedit or regedt32) can be used to maintain the configuration of the eTM. Figure 56: Sample eTM configuration registry entry on page 54 shows a sample configuration, as represented in the system registry as a result of the configuration process. Figure 56: Sample eTM configuration registry entry Figure 57: Sample eTM configuration on page 54 shows a sample configuration for the eTM module that defines the following: • One instance of CSTA_Service.
Merging .reg files 1. Select the Mergecommand. In Windows Explorer: • Locate the file you wish to merge. • Right-click the file. • Choose Merge from the pop-up menu, as follows: 2. Confirm that you wish to merge the registry. Click Yes to continue. 3. Confirm completion of the registry merge. Click OK.
Module - eTM The command RegEdit or RegEdt32 can be used to verify the configuration, or to apply changes to an existing configuration. A future release of DECT Messenger will provide automatic procedures for configuring the Task Manager from the Configurator module. In Release 4, the eGRID module features a command button Generate registry files for eTM.
Figure 58: Example of configuration of four environments • Site 1 - Environment GNTN1SFMI - Environment GNTN1SKDS • Site 2 - Environment *LOCAL • Site 3 - Environment *LOCAL The first two environments reside on site 1, the other environments reside on other sites. In this example, the modules of site 1 are distributed across two environments (two separate PC platforms).
Module - eTM environment GNTN1SFMI contains a full-featured installation with one or more instances of each module; the second environment GNTN1SKDS contains a subset of the modules only. Figure 59: eTM - Site 1 Environment GNTN1SFMI.reg on page 58 shows the registry file corresponding to the foregoing example. 58 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Figure 59: eTM - Site 1 - Environment GNTN1SFMI.
Module - eTM Figure 60: eTM - Site 1 - Environment GNTN1SKDS.reg Figure 61: eTM - Site 2 - Environment LOCAL.reg 60 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Figure 62: eTM - Site 3 - Environment LOCAL.reg At startup, the eTM retrieves the configuration, and launches all tasks that are defined in the environment according to the configuration. As shown in the example in Figure 62: eTM - Site 3 - Environment LOCAL.reg on page 61, the environment GNTN1SCTI launches the DECT Messenger modules CSTA Server, and the module eKERNEL.
Module - eTM This interruption usually occurs during maintenance of one of more of the programs that are guarded by the eTM. Such a temporary condition is shown in the log as illustrated in Figure 65: Yellow icon indicates a task that is paused on page 62. Figure 65: Yellow icon indicates a task that is paused A system administrator can also terminate a task from within the eTM_HA environment using a Terminate process API-call.
Shutting down eTM_HA Figure 67: A task is terminated Note: When the eTM is running, the system relaunches the terminated tasks within 10 seconds. When the eTM form is closed through the control box on the right top of the form, the application does not shut down, but is instead minimized to an icon in the system tray. This function is designed to prevent the user from accidentally closing the eTM and associated tasks.
Module - eTM Right-click the eTM_HA icon in the system tray. 2. Stop the eTM_HA. • Choose the menu item Task Manager - Stop. • Choose the menu item Exit. The following confirmation prompt is shown; do not click OK or Cancel yet: Note: The application also responds to a system Log off or Shut down event. 3. Shut down the applications. Close down all programs using the program specific instructions.
Chapter 5: Module - eTM_HA Important: Setting up the eTM_HA module in a networked environment is a complex task, and requires training to set up, maintain, and use in the DECT Messengerenvironment. Read the following documentation closely, and refer to the training session on eTM_HA for more details. Overview The module eTM_HA is the high-availability implementation of the eTM module. If you wish to migrate your system from eTM to eTM_HA, you must update the system registry.
Module - eTM_HA Figure 70: eTM-HA Task Manager - Overview tab The Logging tab provides data as shown in Figure 71: eTM-HA Logging tab on page 67. 66 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Publisher and Subscriber Figure 71: eTM-HA Logging tab Note: The information shown in Figure 69: Open Task Manager on page 65 is intended as an example. The exact information for your system differs according to your configuration settings. Publisher and Subscriber A typical eTM_HA environment involves one system configured be Publisher, and one or more system configured as Subscribers.
Module - eTM_HA The eTM_HA software must be installed on both the Publisher and the Subscriber site. Based upon configuration settings in the registry, the instance behaves as Publisher or as Subscriber.
Registry settings eTM Important: If the environment names for eTM_HA are not defined with a name containing the local IP address, rename the registry structure generated by eGRID or eCONFIG, so that the IP address is available in the name. The eTM structure can contain one or multiple environments. If you launch the eTM_HA.exe without additional parameters, the program analyzes the available environments of the registry, and prompts for an initial environment at startup.
Module - eTM_HA Note: In eTM.exe a similar function existed, but the keyword was called /Site. In eTM_HA the keyword is renamed to /Environment. eTM registry entries accept the following parameters: • PID The keyword PID denotes the process identifier of the task. This identifier is formatted as a 10-digit numeric value. The PID is also shown when Microsoft Task Manager is used to represent the processes. A special value 0000000000 is shown when the task is not running.
Registry settings eTM Figure 74: Sample registry file of the eTM, illustrating a Publisher site — part 1 Figure 75: Sample registry file of the eTM, illustrating a Publisher site — part 2 Figure 76: Sample registry file, illustrating a Subscriber section in production mode on page 72 shows another example, illustrating a Subscriber section in production mode.
Module - eTM_HA is no eKERNEL reference in this example, as all modules refer to the eKERNEL on the publisher system. Figure 76: Sample registry file, illustrating a Subscriber section in production mode Figure 77: Sample registry file, illustrating a Subscriber section in backup mode on page 73 shows another example, illustrating a Subscriber section in backup mode. Here an eKERNEL reference is shown, as the environment runs when the publisher is unavailable.
Registry settings eTM_HA Figure 77: Sample registry file, illustrating a Subscriber section in backup mode Registry settings eTM_HA The configuration of environments and tasks is stored in the following section: [HKEY_CURRENT_USER\Software\Philips\SOPHO Messenger@Net\eTM_HA] This section contains additional configuration settings that are needed for configuring the highavailability functionality that is added in eTM_HA.
Module - eTM_HA Figure 78: Registry settings: General section The General section defines the following parameters: • Interval CheckAvailability • Interval CheckTasks • Interval KeepAlive • Interval GetImage • Timeout KeepAlive • Timeout GetImage • Timeout Task • Log days • Publisher database • Subscriber database • Subscriber workspace • Subscriber image The Publisher section contains a structure as shown Figure 79: Registry settings: Publisher section on page 75: 74 DECT Messenger Installation and Com
Registry settings eTM_HA Figure 79: Registry settings: Publisher section The same information is represented in the eTM_HA Overview tab, as illustrated in Figure 80: Registry settings: Publisher overview in eTM_HA on page 76.
Module - eTM_HA Figure 80: Registry settings: Publisher overview in eTM_HA The Subscribers section contains a structure as illustrated in Figure 81: Registry settings: Subscribers (0) section on page 76 and Figure 82: Registry settings: Subscribers (1) section on page 77. Figure 81: Registry settings: Subscribers (0) section 76 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Registry settings eTM_HA Figure 82: Registry settings: Subscribers (1) section The same information is represented in the eTM_HA Overview tab, as illustrated in Figure 83: Registry settings: Subscribers overview in eTM_HA on page 78.
Module - eTM_HA Figure 83: Registry settings: Subscribers overview in eTM_HA The General section contains a structure as illustrated in Figure 84: Registry settings: General on page 78. Figure 84: Registry settings: General The same information is shown in the eTM_HA Overview tab, as shown in Figure 85: Registry settings: General in eTM_HA on page 79. 78 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Merging registry files Figure 85: Registry settings: General in eTM_HA Merging registry files Use the steps in Merging .reg files on page 79 to merge registry files. Merging .reg files 1. Select the Merge command. In Windows Explorer: • Locate the file you wish to merge. • Right-click the file.
Module - eTM_HA 2. Confirm that you wish to merge the registry. Choose Yes to continue. 3. Confirm completion of the registry merge. Click OK. The command RegEdit or RegEdt32 can be used to verify the configuration, or to apply changes to an existing configuration. 80 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Check tasks Future releases of DECT Messenger will provide automatic procedures for configuring the Task Manager from the Configurator module. The eGRID module features a command button Generate registry files for eTM. Click this button to read the eKERNEL_TCPCLIENT table and automatically generate the required shortcuts for each site and environment, as shown in Generate shortcuts on page 81. Generate shortcuts 1. Use eGRID to generate registry files for eTM.
Module - eTM_HA When the eTM_HA is paused or stopped, the routine that verifies and restarts the process is temporarily interrupted. This usually occurs during maintenance of one of more of the programs that are guarded by the eTM_HA. This temporary condition is shown in the logging. A system administrator can also terminate a task from within the eTM_HA environment using a Terminate process API-call.
Check tasks down serial and sockets communications, free resources, clean up garbage, and so on. To stop the processes gracefully, follow the steps in Shutting down eTM_HA on page 83. Shutting down eTM_HA 1. Open the eTM_HA pop-up menu. Right-click the eTM_HA icon in the system tray. 2. Stop the eTM_HA. • Choose the menu item Task Manager - Stop. • Choose the menu item Exit.
Module - eTM_HA Publisher The publisher instance of eTM_HA features a TCP Server listing on a port specified in the registry. Typically, port 7000 is used as the default port. The TCP Server is a multiple-accept model, so multiple clients can connect at the same time. The number of simultaneous connections is also defined in the registry. Specify a number at least as great as the number of subscribers.
Publisher Figure 88: TCP Server Error response In an operational environment, the eTM_HA instances of the Subscribers send these two requests to the publisher on a regular basis: KeepAlive, and GetImage. • KeepAlive A KeepAlive request is exchanged between subscriber and publisher, and allows both parties to verify the presence of the other. Interval and timeout between attempts are defined in the registry.
Module - eTM_HA Figure 90: TCP Server Get Image response The XML image file provided by the GetImage request can be expanded and collapsed with the plus (+) and minus (-) signs, as shown in Figure 91: Expanded information on page 86. For more information on the XML image, see XML image on page 90. Figure 91: Expanded information Note: Messenger_CFG contains sensitive data, and is exchanged as plain text in XML format.
Keeping track of states subscriber. During tests with Internet Explorer, you must disable the proxy server for local addresses or specify the IP address of the publisher in the bypass list. Keeping track of states Both publisher and subscriber keep track of the state of the other party. This leads to a socalled "image" of Boolean settings of publisher and subscriber. Subscriber On the subscriber level, there is a state represented by P:0 and P:1, indicating whether the publisher can be reached.
Module - eTM_HA Figure 93: Example of an image at the publisher level on page 88 shows a network where one Publisher and two Subscribers lead to eight images, and depend on each Boolean state of available (1) or unavailable (0). The syntax for images on publisher level are similar to P:1:S0:1-S1:1. Each section is separated by a minus sign (-).
Keeping track of states Figure 94: Example: Site 1 - Environment 147.93.169.
Module - eTM_HA Figure 95: Example: Site 1 - Environment 147.93.169.130 (backup) XML image The Subscriber receives the result of the GetImage in a flat-file repository, located in the following directory: C:\SOPHO Messenger@Net\Xml Important: This directory must be created manually on Subscriber systems. Also a copy of the Messenger_CFG.mdb with the exact layout of the database of the publisher must be created in this directory.
Keeping track of states the database at startup. Therefore, after applying a new version of eKERNEL, you must first start eKERNEL, and then copy the Messenger_CFG.mdb database. If you install new versions of eKERNEL, you must synchronize the eKERNEL modules on all systems. Also the latest layout of Messenger_CFG of publisher (after automatic upgrade changes at first run) must be manually placed in the directory of the Subscribers. GetImage puts a file Messenger_CFG.
Module - eTM_HA C:\SOPHO Messenger@Net\Xml\Messenger_CFG.mdbat subscriber • (activated on subscriber) C:\SOPHO Messenger@Net\Mdb\Messenger_CFG.mdbat subscriber Figure 96: Sample SQL script Use this (optional) SQL script to modify the contents of the database, as arrived from the operational publisher system. In some environments no changes are required; in more demanding customer environments complex scenarios can be set up to allow applying changes to the database. This can include changing .
Conclusion and customer specific factors that are beyond our control, the authors of eTH_HA cannot accept responsibility for malfunction of the software.
Module - eTM_HA 94 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 6: Module - eVBVOICE 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 of Release 4.0. • eFR • eLICENSE • eLOCATION • eSMS • eSNMP • eVBVOICE The eFR module is an add-on module and is licensed separately through the eLICENSE module.
Module - eVBVOICE Figure 97: eVBVOICE inbound call Figure 98: eVBVOICE outbound call 96 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Introduction Inbound calls General configuration parameters General parameters for each eVBVOICE application are specified in the eVBVOICE table. Figure 99: General configuration parameters An eVBVOICE application must be unique for every site + area. Functionality The telephone number when a user calls eVBVOICE can be a group number, or a direct number, as defined in the telephone switch. The users hears the Welcome message, eVBV_Welcome_str and then can select specific menu options.
Module - eVBVOICE eVBVOICE menu option level 1 Figure 100: Menu option level 1 Figure 101: Menu option level 1 - General tab Depending on the data entered in the configuration table for the first menu, eVBVOICE_MENU_L1, the user can select an option by pressing the corresponding keystroke or dtmf tone. The users hears the wave file linked with that option. 98 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Introduction When a user hears the Welcome message, and presses 1 and #, for example, the users hears the wave file AlarmConfirmation.wav. There are 4 different types of menu options possible for eVBVM_L1_Menu_Type_str = • *CONFIRM • *SET • *RESET • *RECORD CONFIRM For menu type = *CONFIRM for confirmation of alarms, there are no entries possible in the eVBVOICE_MENU_L2 table. With the eVBVOICE application, users can confirm messages with a personal pincode (DEV_PinCode_str in eKernel_device).
Module - eVBVOICE Menu option level 2 SET and RESET For menu types *SET and *RESET, the related alarms must be specified in the eVBVOICE_MENU_L2 table. Figure 102: eVBVOICE option level 2 100 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Introduction Figure 103: Menu options level 2 - General tab All possible alarms that can be set (*SET) or reset (*RESET) with a dtmf keystroke must be entered in this table. Although there is no password access protection, you can secure the activation of an emergency by choosing a very large menu option. Choosing a large menu option is very difficult to guess by an unauthorized person.
Module - eVBVOICE Example site 1: Figure 104: eVBVOICE_Menu_L1 Figure 105: eVBVOICE_Menu_L2 To make a call to the eVBVOICE application, enter: • 1# to record AlarmConfirmation.wav file • 2# 102 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Introduction to record AlarmSET.wav file • 2*1# to record EvacuationSET.wav file For recording the general wave files specified in the eVBVOICE table, the wave files must be specified in the eVBVOICE_MENU_L2. Figure 106: eVBVOICE MENU Options table Also wave files specified in the eKernel_Message_format table can be entered in the eVBVOICE_MENU_L2 table. These wave files can be then be recorded by the eVBVOICE application.
Module - eVBVOICE Figure 107: Properties for AlarmConfirmation.wav Outbound calls An alarm that is linked with a wave file, if the wave file exists, can be sent to a device with the eVBVOICE module. Once all the wave files for a specific call are played, you enter a keystroke to ensure messages are delivered. This functionality is necessary to be sure the user hears the messages. Answering machines and voice mails perform in the same manner.
Introduction Figure 108: eVBVOICE Outbound calls Note: The keystroke you enter to ensure messages are delivered does not confirm an alarm. If you want to confirm an alarm, you must call the eVBVOICE application and enter your pincode to confirm the active alarms. Important: It is very important that you link all possible alarms with a wave file in the eKernel_Message_format table.
Module - eVBVOICE Voicecard-related settings are documented in the Hardware Installation manual, and in the online help. [Conference] Figure 109: Ini settings - Conference [DataFind] Figure 110: Ini settings - DataFind [Dialogic] Voicecard-related settings are documented in the Hardware Installation manual and in the online help. [Directories] Figure 111: Ini settings - Directories [Languages] [Languages] controls which rules are used for each language.
Introduction • useitaliangender 0x40 - always use male one if saying 81 or 101 or something • usethouforyear 0x80 - french say one thou, nine hundred, and so on, for year • useofyear 0x200 - spanish say of between month and year • dontuseordinalsfordays 0x400 - spanish • usehundredgender 0x800 - not used • usehoursandminutes 0x1000 - spanish - say 12 and 30 for 12.
Module - eVBVOICE Figure 113: Languages - Default settings [Layout] A value of 0 means do not show the name/type. A value of 1 means show the name/type. Figure 114: Ini settings - Layout [Logs] Figure 115: Ini settings - Logs [PBX] 108 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Introduction Figure 116: Ini settings - PBX [PlayMsgs] Figure 117: Ini settings - PlayMsgs [Record] DECT Messenger Installation and Commissioning — Book 2 March 2012 109
Module - eVBVOICE Figure 118: Ini settings - Record [Rhetorex] Refer to VBV4.INI Hardware-specific settings on page 114. [SAPI_TTS] Figure 119: Ini settings - SAPI_TTS [SAPI_ASR] Figure 120: Ini settings - SAPI_ASR [System] 110 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Introduction Figure 121: Ini settings - System [VoiceCard] VBV4.
Module - eVBVOICE Figure 122: Ini settings - VoiceCard 112 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Introduction DECT Messenger Installation and Commissioning — Book 2 March 2012 113
Module - eVBVOICE VBV4.INI Hardware-specific settings Note: Ini settings use both upper and lower case for readability; however, the entry in the file is not case-sensitive. [AccuCall] Figure 123: Ini settings - AccuCall [Dialogic] Figure 124: Ini settings - Dialogic [Rhetorex] Figure 125: Ini settings - Rhetorex [Voicecard] - (ACULAB specific settings) 114 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Introduction Figure 126: Ini settings - [Voicecard] (ACULAB specific settings) [Voicecard] - (Dialogic specific settings) Figure 127: Ini settings - [Voicecard] (Dialogic specific settings) [Voicecard] - (Dialogic T1 specific settings) T1 bit pattern settings are used to configure the T1 bit patterns for the A & B bits for nonstandard T1 configurations. The first digit is the value for 'A' bit, the second is the value for 'B' bit.
Module - eVBVOICE Valid values for t1hookflash_start and t1hookflash_end are as follows: • 0 = set the bit specified in t1hookflash, clear any others • 1 = set the bit specified in t1hookflash, leave others unchanged • 2 = clear the bit specified in t1hookflash, leave others unchanged The difference between t1answer and t1hangup settings is used to test for hangup notification from the switch. For example, if t1answer is 11 and t1hangup is 10, the B bit going to 0 is used to detect hangup.
Introduction Figure 130: Ini settings - [Voicecard] (Rhetorex specific settings) [Voicecard] - (Rhetorex T1 specific settings) When the first seizure attempt fails, a random back-off is performed followed by another seizure attempt. If this second attempt fails, a failure is reported. Most T1 settings for Brooktrout/ Rhetorex cards are now set in the RealCTdrivers. Figure 131: Ini settings - [Voicecard] (Rhetorex T1 specific settings) From VBVOICE4.
Module - eVBVOICE Figure 132: vbvConfig tool - Voicecard 118 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Introduction Figure 133: vbvConfig - System DECT Messenger Installation and Commissioning — Book 2 March 2012 119
Module - eVBVOICE 120 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 7: Module - eVBVOICE AHVR 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 - eVBVOICE AHVR Configuration In eConfig you define the menu structure. One of the options on level 1 is to ‘SET’ an alarm. See the following figure. Figure 134: Level 1 - Set alarm On level 2, you define the alarm ID and the group. See the following figure 122 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Configuration Figure 135: Level 2 - Define alarm ID and group You need to set the only visible deviation from normal alarm handling. Instead of identifying the prerecorded message, use the keyword *RECORD. See the following figure.
Module - eVBVOICE AHVR Figure 136: RECORD The following figure shows how *RECORD looks In the Access tables. Figure 137: RECORD in the access tables Example 1 Consider the customer site shown in the following figure. 124 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Configuration For the example, assume there are 3 types of alarms: fire, reanimation and security. Also assume that the alarm recipients are located in all of the iS3070 locations. Figure 138: Example 1 - Customer site Also assume for Example 1 that there is one eVBVoice module on site. Your goal is to add ad hoc voice messages to the reanimation alarms. The IVR menu could look like the following figure.
Module - eVBVOICE AHVR Figure 140: Example 2 - IVR menu Voice messages are stored on the system where the eVBVoice module is located. This means that voice messages can only be distributed by the eVBVOICE module on the same system as the voice messages. The voice messages are not automatically removed. For this reason Avaya suggests that you manually remove old and handled message from time to time. 126 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 8: Module - eWEB When you start your web browser application and navigate to the DECT Messenger system that has the eWEB module operational, a sign-on window opens. Contact the system administrator to obtain the URL address assigned to the system. Sign-on procedure A sign-on is required; because you are not yet authenticated to the application, this window is presented in English.
Module - eWEB When a valid user and password is found, you are able to continue working in the eWEB module. It is important to know that during the sign on procedure, two additional parameters are fetched: the language code and the security level. The language code determines the language of the forms that are presented to the user. If for example the language code is 2909 – Belgian English, the panels are in English. If the language code is 2963 – Belgian Dutch, the panels are in Dutch.
Send DMS-API Message Figure 142: Expired login Send DMS-API Message This function allows you to send an E2-data message to a peripheral that is capable of receiving messages through this technology. The web interface presents all DECT extensions that are defined in the eKERNEL_DEVICE table for the local site and area and the output program eDMSAPI. Important: The eWEB application is configured in the eWEB table, and identifies its site and area based upon the IP address of the Apache Web Server.
Module - eWEB Figure 143: Local extensions Figure 144: Local and remote extensions on page 130 shows the list of extensions that all reside locally on the same site and area, but also displays an extension that resides on another area, which is made available through the DEC_Ras_Area_b value in the eKERNEL_DEVICE table. Figure 144: Local and remote extensions Note: The Send DMS-API Message form always contacts that local DMS-API Service of the same site and area as the Apache Web Server.
Send Server Message You can also make devices that are allocated to a remote area available through the DEV_Ras_Area_b value in the eKERNEL_DEVICE table. An example is shown in Figure 145: Sending messages to remote addresses on page 131: Figure 145: Sending messages to remote addresses As a result, the SMTP server is contacted, and a message is sent.
Module - eWEB In the example shown in Figure 146: Alarm types on page 132, you can choose between three alarm types, which are defined in the eKERNEL_ALARM table. Figure 146: Alarm types Important: You can only access alarm types in the eKERNEL_ALARM table with field ALA_Trace_b equal to False. While assigning alarm types, always make a distinction between alarms for Send Server Message (False) and Send Script Message (True). The destination of the message is also defined in the database.
Send Group Message Figure 147: Group list Send Group Message In step 1, shown in Figure 148: Select a group on page 133, you can choose from a list of groups. These groups are retrieved from the eKERNEL_GROUP and eKERNEL_GROUP_MEMBER tables. All the groups that use a matching input program with the appropriate eWEB module (site/area) are shown to the user. Collapse or expand the group to see the group members. Click the arrow to select the group.
Module - eWEB Figure 149: Select a message Finally, you can send the request to eKERNEL and submit the request for further processing. The example shown in Figure 150: Confirm and send message on page 134 shows a situation in which a user-defined message has been selected, so you must enter the message text manually. Figure 150: Confirm and send message The Send Group Message completed normally message indicates the message has been submitted to eKERNEL.
Send User Message Figure 151: Select the group Step 2 provides an overview of the user messages that are preconfigured for your current user profiles, which is used during the login procedure in the initial window of eWEB. As shown in Figure 152: Select a message on page 135, the eWEB_SNDUSRMSG table can define private messages per user, shared messages for all users, or user-defined entered messages.
Module - eWEB Send Script Message You can choose from the following sub-functions: • Set Script is used to activate a script. The scripts are defined the eWEB_SCRIPT table. • Trace Active Script is used to see an overview of activated scripts. These scripts are still running. • Cancel Script is used to abort a script that has been activated. • Trace ended Script is used to see an overview of these scripts that are completed.
Send Script Message Figure 154: Overview of defined scripts In Figure 155: Script details on page 137, the third script has been activated, and more detailed information on the script is provided (only one such script can be activated at a time). The window shows us that one device is a member of the group, and the device is configured to be available 24/24 hours and 7/7 days. A minimum of one device must confirm the alarm, therefore you must not clear the device selection.
Module - eWEB Figure 157: Cancel script Cancelled scripts are removed from the list, as shown in Figure 158: Cancelled script removed from the list on page 138. Figure 158: Cancelled script removed from the list Trace Ended Script Trace Ended Script, shown in Figure 159: Trace Ended Script on page 138, allows you to monitor the event handling of scripts that are finished. Figure 159: Trace Ended Script Alarm Inquiry Alarm Inquiry allows you to see all relevant parameters for the eKERNEL_ALARM file.
Device Inquiry Device Inquiry The device inquiry allows you to see all relevant parameters for the eKERNEL_DEVICE file. Only those records are shown that refer to the site where the current eWEB instance resides. The information is retrieved from one table: eKERNEL_DEVICE. You can either display data for all output programs (by specifying *ALL) or select one output program. Group Inquiry The group inquiry allows you to see all relevant parameters for the eKERNEL_GROUP and eKERNEL_GROUP_MEMBER files.
Module - eWEB In step 1, shown in Figure 160: Select a group on page 140, select a group. You can collapse or expand a group to preview the group member information. Figure 160: Select a group Next, you can either maintain an existing device or add a new device. The example shown in Figure 161: Select a device on page 140 demonstrates selecting an existing device for maintenance (update or delete).
Work with Groups Figure 162: Confirm changes If you select to add a new device, a window similar to the one in Figure 163: Select new device on page 141 is shown. Select one of the configured devices and specify the additional parameters prior to adding the device. Figure 163: Select new device Note: You can access only the devices that belong to the same site as used by the eWEB module.
Module - eWEB Change Password Change Password allows you to enter a new password. You must enter: • your User ID • your old password • your new password • your new password (for verification) This option eliminates the need for an eGRID-based administration of passwords of existing user profiles. Note: More advanced security settings or resetting passwords of users that forgot their password, still must be performed through eGRID in the eWEB_USER_AUTH table.
Plug-in Support Plug-in Support The DECT MessengereWEB module allows embedding plug-in modules that add additional functionality to the web interface. The plug-in modules can be integrated easily through the standard eWEB_TOC table. This is illustrated in Figure 164: Plug-ins added to eWEB on page 143, where additional table-of-contents entries are added for the plug-in MyPortal@Net. Figure 164: Plug-ins added to eWEB Plug-in module MyPortal@Net An example of a plug-in module is MyPortal@Net.
Module - eWEB Figure 165: MyPortal@Net plug-in The module uses native CSTA.DLL interfacing to handle voice-calls. This option is currently not supported. Contact Avaya to determine if plug-in models are available. 144 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 9: Module - Web Administrator The module Web Administrator provides a web-based user interface. Web Administrator builds on the infrastructure of eWEB and depends on the same prerequisites, such as the Apache HTTP Server, PHP scriping engine, and ODBC DSN for Messenger_CFG and Messenger_DATA database. To log on to Web Administrator, refer to Logging on to Web Administrator on page 145 Logging on to Web Administrator 1. To start the web interface, enter the URL: http://messenger/ez_index.
Module - Web Administrator Work with Users When you login with the default user name and password, you have the default administrative rights and full access to the Web Administrator. One of the features is Work with Users. Use this feature to maintain the users, as shown in Figure 167: Work with Users in Web Administrator on page 146. Figure 167: Work with Users in Web Administrator 146 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 10: Module - Web Administrator User Guide The Web Administrator provides a web-based user interface. Ensure that you have a compatible web browser, such as Internet Explorer 6.0 or Mozilla Firefox 2.0. In the web browser's Address field, enter the URL where Web Administrator is installed; for example, http://messenger/ez_index.php. When you enter this URL in your web browser, the Login page appears, as shown in Figure 168: DECT Messenger Login screen on page 147.
Module - Web Administrator User Guide Authorization level The contents of the navigation pane in the Web Administrator varies depending on the authorization granted to the user account that is used to log on. Figure 169: Navigation pane for Administrator user on page 148 shows an example of a navigation pane for a user with Administrator rights. Users with less authorization see a reduced number of links, restricting access to certain functions.
Authorization level Table 5: User authorization levels Authorization level User (basic) Functionality • Send a Message - DECT handset - Mobile phone - Email - Windows • Security • Logout Authorization level User (advanced) Functionality • Send a Message - DECT handset - Mobile phone - Email - Windows - Group Message - User Message • Security • Logout Authorization level User (expert) Functionality • Send a Message - DECT handset - Mobile phone - Email - Windows - Group Message - User Message • Reporti
Module - Web Administrator User Guide Authorization level Functionality • Ended alarms • Report • Configuration - Basic • Group members • Alternative devices • Overview • Security - Change password • Logout Authorization level Supervisor Functionality • Send a Message - DECT handset - Mobile phone - Email - Windows - Group Message - User Message • Work with scripts - Activate script - End script • Reporting - Alarms • Active alarms • Ended alarms • Report - Scripts • Active alarms • Ended alarms • Confi
Authorization level Authorization level Functionality • Alternative devices • Overview • Security - Change password • Logout Authorization level Administrator Functionality • Send a Message - DECT handset - Mobile phone - Email - Windows - Group Message - User Message • Work with scripts - Activate script - End script • Reporting - Alarms • Active alarms • Ended alarms • Report - Scripts • Active alarms • Ended alarms • Configuration - Basic • Group members • Alternative devices • Overview - Advanced •
Module - Web Administrator User Guide Authorization level Functionality • Facilities • Groups • Users - Expert • Tasks • Configuration • PHP Info • Import • Security - Change password • Logout The following section describes the functionality of accounts that have User authorization levels. Other accounts are described in Supervisor on page 167 and Administrator on page 172. Log in Your system administrator provides your user name and password.
Authorization level The Web Administrator page The top part of the left pane of the Web Administrator page shows graphics or images that are related to the environment or the functionality that appears on the page. When you select an option in Web Administrator the graphic changes to represent the selected function. The middle of the left pane is a navigation menu that provides a hierarchical representation of the available functions.
Module - Web Administrator User Guide campus, address, building, and so on. When you send a message, you must first select the area. Send a message to a DECT handset Use the following procedure to send a message to a DECT handset. You can only send messages to DECT Handsets that are configured on the system by the administrator. Sending a message to a DECT handset 1. Log in to Web Administrator. 2. In the navigation menu, click DECT handset.
Authorization level 6. Click Submit. Web Administrator indicates whether the message delivery succeeded or failed. Table 6: Job aid: maximum message length System Maximum length of message traditional DECT up to 48 characters SIP DECT up to 160 characters Table 7: Job aid: message priorities Priority Behavior Normal The system verifies delivery of the message without requesting confirmation from the recipient.
Module - Web Administrator User Guide Sending a message to a mobile phone 1. Log in to Web Administrator. 2. In the navigation menu, click Mobile phone.OR If multiple areas are defined, click the name of the area, then click Mobile phone. The Send a Message page appears, on which appears a list of mobile phones to which you can send a message. There is room to display 14 devices on the screen at any one time.
Authorization level There is room to display 14 devices on the screen at any one time. If there are more than 14 address listed, click [pgdn] or [pgup] to navigate to the next page or previous page. To return to the first page, click [home]. 3. Select a recipient by clicking the green arrow at the left of the entry. The Send a Message > Please enter message information page appears. 4. Enter the text of your message in the Message field.
Module - Web Administrator User Guide Up to three types of messages are supported, depending on your system configuration: • Private messages • Shared messages • Free messages 5. Select the message to send by clicking the green arrow next to it. If you select Free message, type the text of your message. 6. Click Submit. Web Administrator indicates whether the message delivery succeeded or failed.
Authorization level Up to three types of messages are supported, depending on your system configuration: • Private messages • Shared messages • Free messages 5. Select the message to send by clicking the green arrow next to it. If you select Free message, type the text of your message. 6. Click Submit. Web Administrator indicates whether the message delivery succeeded or failed.
Module - Web Administrator User Guide Reports are generated from the information that is stored in the Messenger_DATA database, which is an internal repository that temporarily stores active alarms. Alarms are organized according to output program, and the number of active alarms appears next to each output program. The report provides a snapshot of an instant in time, and is not updated in real-time. Click refresh to update the information in the report.
Authorization level You can also perform optional filtering, for example upon Message. Figure 170: Work with Ended alarms - Input requests Reports on alarms Reports on alarms is available to User (expert) and Supervisor and Administrator. Work with Report provides an easy web-based reporting function to combine the available information gathered by eLOG module. Work with Report also exposes the data available in comma separated files.
Module - Web Administrator User Guide Configuration of basic group members Users (expert), Supervisors, and Administrators can use the configuration function Work with Group Members for web-based maintenance of group members. The function also internally maintains the content of the eKERNEL_GROUP_MEMBER table. Follow the steps in the next procedure to configure Work with Group Members. Configuring Work with Group Members 1. Select the input module you want to maintain on the first page.
Authorization level 4. To update the details, change the start hour and end hour and click the [update] link. In the example shown in the next figure, an update is done by changing From into 08:00 and To into 12:00 and clicking the [update] link. 5. Click the [remove] link to remove a group member. See the example in the following figure. 6. Select a destination device in the right-hand area to insert a new group member.
Module - Web Administrator User Guide 7. Optionally, adjust the default settings and click [insert]. In the example shown in the following figure, the default settings Sat, Sun, and Hol are changed to No. Configuration of basic alternative devices User (expert), Supervisor and Administrator can use the function Work with Alternative Devices. Work with Alternative Devices provide a web-based user interface to maintain the internal configuration table eKERNEL_DEVICE_ALT.
Authorization level 4. Select an output program. Peripherals are associated to output programs and therefore, Mobile phones resides under an instance of the eSMS module, and DECT handsets resides under an instance of eDMSAPI. In the example shown in the following figure, an alternative device for a Windows PC is required. The output module eNET is selected.
Module - Web Administrator User Guide To add the mobile phone of Francis Missiaen as an alternative device, Francis is typed into the subset field under Click on devices to add alternative device, and [subset] is clicked. 7. If you want to add the name of an alternative device, type the name you want to add in the [subset] field under the section on the right called Click on device to add alternative device. 8. Click on [subset].
Authorization level Configuration basic overview The Configuration basic overview function is available to User (expert), Supervisor, and Administrator. You can select a group, check the group members, and check the alternative devices with Overview. Overview basically responds to the question: "What happens to my alarms?" Follow the steps in the next procedure to configure basic overview.
Module - Web Administrator User Guide Reporting is extended with Scripts, with access to link Active scripts and Ended scriptsEnded scripts. Figure 173: Supervisor access to Work with Scripts Work with scripts - activate script The Activate Script function in Work with Scripts is available to Supervisor and Administrator. Follow the steps in the next procedure to use activate script. Using Activate Script 1. Open Work with Scripts and click Active script.
Authorization level The next window shows a preview of the script. In the top section, details are visible on the script, such as message and group and current user. The bottom section shows the group members belonging to the selected group. Your ability to check or un-check the check boxes in front of groups members depends on the configuration of the script. In some configurations, you cannot uncheck group members as the check boxes are disabled.
Module - Web Administrator User Guide Work with Scripts - End Script The function Work with End Script is available to Supervisor and Administrator. Follow the steps in the next procedure to use Work with End Script. Ending Scripts 1. Open the Work with Scripts window and click End script. An empty screen indicates that no active scripts are present and so no active scripts are available to end. 2. Ensure that the script you end is the correct active script. Verify the date and time and description. 3.
Authorization level When no active scripts are available, an empty screen is shown. 3. When one or more active scripts are available, highlight the script identifier to see details. The window shows the progress of an active script. There is a subset box near the top of the window. The subset box has the options *ALL, *PENDING, *ACK, and *NACK. When you select *ALL, you get a list of all active scripts. When you want to narrow the results of your search, choose *PENDING, *ACK, or *NACK.
Module - Web Administrator User Guide Administrator A user with Administrator rights has full access to all capabilities of the Web Administrator. Send an SNMP trap The function Send an SNMP trap is available to Administrator. SNMP trap is shown in the Send a Message window when the system has the eSNMP module installed, licensed and configured. SNMP trap provides a web-based basic implementation of an SNMPv1 trap sender. For details on the capabilities of SNMP trap, refer to Module - eSNMP on page 41.
Authorization level Figure 174: SNMPv1 trap example In the example one varbind parameters is given. A resulting action depends on the Messenger configuration settings. For example, in Figure 175: eSNMP module receives SNMP trap on page 173 the eSNMP module receives the SNMP trap in Figure 174: SNMPv1 trap example on page 173. Figure 175: eSNMP module receives SNMP trap In this example, the result is that a Windows popup message is sent through eNET.
Module - Web Administrator User Guide Figure 176: Popup message sent through eNET Advanced configuration The advanced configuration is reserved for users with Administrator rights, and provides maintenance of Devices, Facilities, Groups, and Users. Configuration of advanced facilities The configuration of advance facilities function is available to Administrator. Follow the steps in the next procedure to configure advanced facilities. Configuring advanced facilities 1.
Authorization level When no definitions are available, an empty screen appears. 4. Use the [home], [pgup], and[pgdn] links to navigate through the list of definitions. 5. Click the [insert] link to add a new definition. 6. Click the green arrow to change an existing definition. Note: A Facility is considered an unique key. If, for example, you have defined C944 once, you cannot add a second C944 definition. The next figure shows the details of the selected definition C944. 7.
Module - Web Administrator User Guide Note: This function maintains the internal configuration table eKERNEL_DEVICE in the Messenger_CFG database. 4. In the first window, select the Output module. An overview of the existing Devices is shown. When no definitions are available, an empty screen is shown. 5. Use the [home],[pgup], and[pgdn] links to navigate through the list of definitions. 6. To add a new definition, click the [insert] link. 7. To change an existing definition, click the green arrow.
Authorization level 9. Type [apply] to insert the definition. 10. To return from the detailed screen, click [cancel]. Note: Avaya highly recommended that you add a meaningful Description, as this is represented to the Web Administrator during further maintenance. Avaya also strongly recommends that you specify first name and last name, or any other unique reference, to define the owner of the peripheral. 11. To maintain an existing device, click the green arrow in front of an existing definition. 12.
Module - Web Administrator User Guide When the[delete] link is clicked, the device is removed. Note: The current release of Web Administrator allows deleting a device without checking if it is in use by other configuration tables. Many configuration tables can be involved, for example, eKERNEL_GROUP_MEMBER, and eKERNEL_DEVICE_ALT, but also the tables related to inbound eCSTA, eDMSAPI and eLOCATION definition. Carefully verify if a device is used prior to deleting it.
Authorization level Configuring advanced groups 1. Open the Configuration window and click Advanced. 2. To access Work with Groups, click Groups. Groups are associated to input capable modules. Therefore, on the first screen a selection is requested on the Input module. Next an overview of existing groups for the chosen input module is shown. 3. Use [home], [pgup], and [pgdn] to navigate through the list of definitions. 4. To add a new definition, click [insert]. 5.
Module - Web Administrator User Guide 8. Enter changes, then click [apply]. 9. To delete an existing definition, select the group and click [delete]. Note: In current release of Web Administrator, no check is performed to verify if the group is in use. • There can be group members but they are not removed automatically when a group is deleted. You should verify if group members exist and remove them prior to deleting the group.
Authorization level Note: The Work with Users function maintains the eWEB_USER_AUTH configuration table of the Messenger_CFG database. The eWEB_USER_AUTH configuration table defines access to eWEB and Web Administrator modules. Do not delete the *ALL or admin definitions. When you delete these definitions, you are no longer able to authenticate for future maintenance through eWEB or Web Administrator. On the Work with Users main page, an overview of existing users is shown. 3.
Module - Web Administrator User Guide Figure 178: Available languages The remaining fields in the Work with Users window are available for backwards compatibility with eWEB. However, these fields are not implemented in Web Administrator. You can leave the default values. Expert The Expert function is available to Administrator. A number of additional links can be available in Web Administrator. Expert tasks The Expert tasks function is available to Administrator.
Authorization level Figure 179: Task Manager (eTM.exe) Note: eKERNEL also features an overview of modules. In the overview of modules, there is more focus on the TCP/IP connection status between eKERNEL and clients. As a result, eKERNEL can show more modules than are available in Web Administrator, since, for example eKERNEL can also connect modules that run distributed on a remote PC. For this reason, the task does not run on the CPU of the Web Administrator and is not seen in Work with Tasks.
Module - Web Administrator User Guide Figure 180: eKERNEL overview of modules Expert configuration The Expert configuration function is available to Administrator. To access this function, open the Configuration window, click Expert, and then click Configuration. Expert configuration provides an overview of the available configuration tables in Messenger_CFG database. Expert PHP information The Expert PHP information function is available to Administrator.
Authorization level Export import The function Export import is available to Administrator. Note: The Import link is shown only when the Template databases are installed on the Messenger system. The Template databases reside in the path C:\SOPHO Messenger@Net\Mdb \Templates and are typically installed as part of the installation process step 02.02. SOPHO Messenger@Net – Templates. The administrator can decide to not install these templates.
Module - Web Administrator User Guide 6. Change the default password for admin as soon as possible to prevent intrusion by users that attempt to authenticate with admin and admin defaults. 7. Refer to the chapter DECT Messenger – Templatesin Volume 1 of this document for further information, such as information related to creating shortcuts. Any further configuration is beyond the scope of Web Administrator.
Chapter 11: Table: eASYNC eASYNC parameters Figure 181: eASYNC parameters eASYNC_Site_id_n This field specifies the site, as defined in eKERNEL_SITE table. In most cases the value is 1. An example of an entry typically found in this field is as follows: 1 eASYNC_Area_id_n This field specifies the area, as defined in eKERNEL_AREA table. In most cases the value is 1.
Table: eASYNC Support for other providers and types can be added in future releases, or can be built on request. For example: • PAGING (requires the field eASYNC_Provider_str to equal BELGACOM) • SMS (requires the field eASYNC_Provider_str to equal PROXIMUS) • SMS (requires the field eASYNC_Provider_str to equal KPN) eASYNC_Provider_str This field specifies the provider, which is related to the type specified in the eASYNC_Type_str field, which can be either PAGING or SMS.
eASYNC parameters An example of an entry typically found in this field is as follows: *NONE eASYNC_COM_Port_str This field specifies the COM port that handles the asynchronous communication. Usually an asynchronous modem is attached to port COM02. In this case, specify COM02. Important: Verify that the resource is available, and that the modem is attached to the correct resource. There are environments where many COM ports are available, which can lead to confusion during configuration.
Table: eASYNC Type SMS Provider PROXIMUS Password proximus Settings 9600,N,8,1 Telnr 00475161622 Note: Avaya recommends that you specify 9600,N,8,1 for PAGING/BELGACOM service provider. An example of an entry typically found in this field is as follows: 00475161622 eASYNC_Init_str This field allows you to specify a modem initialization string command. This is useful in situations where a clean start is required.
eASYNC parameters of messages that must be in the queue before processing starts. This value is supported only for PROXIMUS – SMS and KPN – SMS. This is the only provider that allows the delivery of more than one message in a single dial-out request, thus potentially reducing communication costs at the expense of speed. Avaya recommends a value of 1 for most environments, because processing is usually executed as soon as possible, and any related call setup costs are therefore less important.
Table: eASYNC eASYNC_Silence_intv_n This value specifies how frequently users are informed of remaining active messages. The default value is 600 seconds, which reduces unnecessary calling traffic to the provider. Note that a similar value is implemented in eKERNEL_ALARM table. The value here overrides the value in the eKERNEL_ALARM table due to bandwidth constraints.
Chapter 12: Table: eBACKUP eBACKUP parameters BU_Site_id_n This field specifies the site identifier, as defined in the eKERNEL_SITE table. Usually, there is only one site defined, and the value 1 is used. An example of an entry typically found in this field is as follows: 1 BU_From_Path_str This field specifies the path of the file that must be saved.
Table: eBACKUP You do not need to manually build the directory tree structure, as the nested directory path is built automatically step-by-step during the backup procedure. In most cases, Avaya recommends that you not overwrite a previous backup. System administrators typically want to make a copy of the environment both before and after making maintenance updates, and in some cases want to store a history online.
Sample Data BU_Comments_str This field can be filled with reminder information for an administrator, for example the usage of the file. You can leave the field blank. An example of an entry typically found in this field is as follows: Configuration Database Sample Data Table 11: Sample data Sit e From path From file To path To file 3 C:\Php php.ini C:\Temp\[weekday]\php php.ini 3 C:\Program Files \Apache group \Apache\conf httpd.
Table: eBACKUP Sit e 196 From path From file To path C:\Temp\[weekday] \SOPHO Messenger@Net\Exe To file 3 C:\SOPHO Messenger@Net\Exe eIO.exe 3 C:\SOPHO Messenger@Net\Exe eKERNEL.ex C:\Temp\[weekday] e \SOPHO Messenger@Net\Exe eKERNEL.exe 3 C:\SOPHO Messenger@Net\Exe eSMTP.exe eSMTP.exe 3 C:\SOPHO Messenger@Net\Exe eSMTP_serv C:\Temp\[weekday] er.exe \SOPHO Messenger@Net\Exe eSMTP_server.e xe 3 C:\SOPHO Messenger@Net\Exe omnithread_r C:\Temp\[weekday] t.
Chapter 13: Table: eCAP_generic eCAP_generic parameters eCAPG_Inpgm_id_n This field refers to the input program identifier, as defined in eKERNEL_INPGM table. An example of an entry typically found in this field is as follows: 11101 eCAPG_Line_Sep_str This field specifies the character sequence that is used to separate input lines that are processed through the generic eCAP interface. This value must be formatted using one or more 2-byte hexadecimal ASCII values.
Table: eCAP_generic Although the separator us used to isolate logical blocks, a number of hard-coded routines are active within eCAP module. 0A0D and 0C0D blocks are always ignored. An example of an entry typically found in this field is as follows: 0D0A eCAPG_Line_Select_start_n This value, together with eCAPG_Line_Select_len_n and eCAPG_Line_Select_str, is used to optionally define selection criteria, which are used to select only those records in a asynchronous datastream that are defined.
eCAP_generic parameters eCAPG_Line_Omit_start_n This value, together with eCAPG_Line_Omit_len_n and eCAPG_Line_Omit_str, are used to optionally define omit criteria, which are used to omit specific records in a asynchronous datastream. The value 0 denotes the omit capabilities are not in use. As a result, the corresponding values are ignored, and no records are omitted. In this case, the field eCAP_Line_Omit_len_n must be 0 and the field eCAPG_Line_Omit_str must be N/A.
Table: eCAP_generic eCAPG_Field_Sep_str This field can optionally define field separators. Field separators can be used when no fixed format of datastreams is available, and individual fields are to be retrieved from a variablelength datastream. In most cases, this field is not used, and the special value N/A is specified. The generic eCAP module is targeted to handle only datastreams that use a fixed format layout (for example, printer ports typically produce such formatted data).
eCAP_generic parameters If the field eCAPG_GRP_Name_start_n is not set to 0, the eCAPG_GRP_Name_len_n must be non-0 as well, and define the length of the group name. An example of an entry typically found in this field is as follows: 4 eCAPG_GRP_Name_field_n This field specifies the occurrence number of the field that denotes group name, and only applies when a field separator is defined. In this case, no positional definition is active. The field must be 0 when no such definition is active.
Table: eCAP_generic If the field eCAPG_Msg_start_n equals 0, the eCAPG_Msg_len_n must be 0. If the field eCAPG_Msg_start_n is non-0, the eCAPG_Msg_len_n must be non-0, and define the length of the message. Note the length specified in eKERNEL_ALARM table. An example of an entry typically found in this field is as follows: 16 eCAPG_Msg_field_n This field specifies the occurrence number of the field that denotes message, and only applies when a field separator is defined.
eCAP_generic parameters If the field eCAPG_Ala_Descr_start_n is non-0, the eCAPG_Ala_Descr_len_n must be non-0 as well. An example of an entry typically found in this field is as follows: 1 eCAPG_Ala_Descr_field_n This field specifies the occurrence number of the field that denotes alarm description, and only applies when a field separator is defined. In this case, no positional definition is active. The field must be 0 when no such definition is active. A positive value indicates the field number.
Table: eCAP_generic eCAPG_Reset_start_n This value, together with eCAPG_Reset_len_n and eCAPG_Reset_str, refers to the optional reset functionality that can be deployed in the eCAP generic module. In most cases, a eCAP generic is implemented in environments, where alarms are detected through an asynchronous serial interface, such as a printer port. The eCAP generic is targeted to environments, where each alarm indication results in sending an alarm request to the eKERNEL interface.
eCAP_generic parameters eCAPG_Reset_str This parameter also refers to the optional reset capabilities, and contains the string that must be found in the starting position eCAP_Reset_start_n with length eCAP_Reset_len_n. In most cases the reset functionality is not used, and the default value N/A is defined. An example of an entry typically found in this field is as follows: GENERAL RESET eCAPG_Remove_after_str This parameter accepts the value *SENT or *RESET.
Table: eCAP_generic 206 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 14: Table: eDMSAPI eDMSAPI parameters eDMSAPI_site_id_n This field specifies the site identifier, as defined in eKERNEL_SITE table. This value is set to 1 in most environments. An example of an entry typically found in this field is as follows: 1 eDMSAPI_Area_id_n This field specifies the area identifier, as defined in eKERNEL_AREA table. This value is set to 1 in most environments.
Table: eDMSAPI eDMSAPI_Seats_count_n This field specifies the total number of seats available for E2 messaging (aCsOpenStream). Sending an E2 message to a DECT extension consumes one seat (one seat is allocated between the StartDataPath and the StopDatPath). For receiving E2 messages (generation of an alarm), DECT extensions that are configured to generate alarms (table eKERNEL_DEVICE field DEV_IoRegister_b) must be IoRegistered.
eDMSAPI parameters An example of an entry typically found in this field is as follows: 10.110.50.138 eDMSAPI_External_Port_str This field specifies the port reserved for requests from the External clients. This port can accept eDMSAPI_External_Seats_count_n simultaneously requests.
Table: eDMSAPI For example, if 1 is specified, alarms with alarm priority of 1 are handled as emergency messages, whereas alarms with priority of 2, 3, 4, and so on are handled as urgent or normal messages. Avaya recommends that you carefully evaluate the consequences of changes to this field, for two reasons: • Emergency messages impact the DECT C4060 user (different tone, user intervention required for acknowledge).
eDMSAPI parameters controller and Avaya is 28001; however, depending on the configuration settings, other values (for example, 2001) are appropriate. An example of an entry typically found in this field is as follows: 2555 eDMSAPI_PBX_type_str This field specifies the PBX type used to handle the DMSAPI functionality. The value is introduced in R3.0. Supported values are DMC, DAP, and Avaya. Note that the eDMSAPI_PBX_port_str must also be set according to the recommendations of the PBX type.
Table: eDMSAPI eDMSAPI_Msg_dly_n This field specifies the delay in seconds between sending the individual requests: send normal message and send urgent message. An example of an entry typically found in this field is as follows: 3 eDMSAPI_GeneralTimeOut_n This field specifies the Time, in seconds, the eDMSAPI program waits for an event from the CSTA service. This value is by default 10 seconds, and must be greater than 5.
Chapter 15: Table: eDMSAPI_INBOUND eDMSAPI_inbound parameters eDMSAPII_Site_id_n This field specifies the site identifier, as defined in eKERNEL_SITE table. In most environments, this value is 1. An example of an entry typically found in this field is as follows: 1 eDMSAPII_Area_id_n This field specifies the area identifier, as defined in eKERNEL_AREA table. In most environments, this value is 1.
Table: eDMSAPI_INBOUND These values are interpreted by eKERNEL module of DECT Messenger. *IC When a call is made, the calling line identifier of the calling party (also known as CLID) is used to confirm outstanding messages for those devices in DEVICE table with the DEV_Pincode_str equal to the CLID.
eDMSAPI_inbound parameters eDMSAPII eDMSAPII_ eDMSAPII_ eDMSAPII _ _Site_id_n Area_id_n Called_dev_str Type_str eDMSAPII_Comments_str 1 1 888 *IA NOOD 1 1 999 *IA REA DECT Messenger Installation and Commissioning — Book 2 March 2012 215
Table: eDMSAPI_INBOUND 216 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 16: Table: eDMSAPI_INBOUND_EVENT eDMSAPI_inbound_event parameters eDMSAPIIE_Site_id_n This field specifies the site, as defined in eKERNEL_SITE table. Is most environments, the value is 1. An authorized of an entry typically found in this field is as follows: 1 eDMSAPIIE_Area_id_n This field specifies the area, as defined in eKERNEL_AREA table. Is most environments the value is 1.
Table: eDMSAPI_INBOUND_EVENT eDMSAPIIE_Calling_dev_str This field specifies the Calling device in an incoming call alarm generation situation, handled by eDMSAPI. The Calling device specified here defines those extensions that can generate an alarm by sending a message to the related called device. 1. Define an extension by number, for authorized, 866. 2. Define a generic value *ALL. 3. Define a generic number starting with some characters 85*.
eDMSAPI_inbound_event parameters eDMSAPIIE_Comments_str This field can contain remarks from the administrator and is informational only.
Table: eDMSAPI_INBOUND_EVENT 220 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 17: Table: eDMSAPI_INBOUND_RESULT eDMSAPI _inbound_result parameters eDMSAPIIR_Site_id_n This field specifies the site, as defined in eKERNEL_SITE table. In most environments, this value is 1. An authorized of an entry typically found in this field is as follows: 1 eDMSAPIIR_Area_id_n This field specifies the site, as defined in eKERNEL_AREA table. In most environments, this value is 1.
Table: eDMSAPI_INBOUND_RESULT The value must be the extension number of the device where the message is sent. In most situations each device defined in eDMSAPI_INBOUND table as *IA has at least one record in this table. An authorized of an entry typically found in this field is as follows: 999 eDMSAPIIR_Calling_dev_str This field specified a descriptor of the calling device.
eDMSAPI _inbound_result parameters Refer to the sample data in Table 14: Sample Data on page 223 for authorizeds of message definitions.
Table: eDMSAPI_INBOUND_RESULT Site 224 Area Called device Calling device Group Message 1 1 56789 866 E2TESTG RP TEST 866 [msg] 1 1 860 86* REA REA : [msg] from [Calling number] to [Called number]. 1 1 860 865 REA REA [msg] from [Calling number] to [Called number]. 1 1 860 866 REA REA [msg] from [Calling number] to [Called number]. 1 1 860 867 REA REA [msg] from [Calling number] to [Called number]. 1 1 860 868 REA REA [msg] from [Calling number] to [Called number].
Chapter 18: Table: eESPA eESPA parameters eESPA_Site_id_n This field specifies the site identifier, as defined in eKERNEL_SITE. This value is, in most environments, equal to 1. An authorized of an entry typically found in this field is as follows: 1 eESPA_Area_id_n This field specifies the area identifier, as defined in eKERNEL_AREA. This value is, in most environments, equal to 1.
Table: eESPA eESPA_Link_Type_str This field specifies the type of physical link between the controlling and the controlled system. The only supported value that can be entered in this field is RS232. An authorized of an entry typically found in this field is as follows: RS232 eESPA_ControlStation_b This value specifies whether the station is a control (master) station, or a slave.
eESPA parameters If more than one address must be polled, the addresses must be separated with a ^ sign. In this release, only a point to point link is supported, so only one address can be specified. An authorized of an entry typically found in this field is as follows: 2 eESPA_LocalAddress_n This field specifies the address of the local espa interface. An authorized of an entry typically found in this field is as follows: 1 eESPA_ExternalAddress_n This field specifies the address of the remote station.
Table: eESPA US Unit separator RS Record separator BCC Checksum The incoming alarm/message, must be translated to a valid message request and sent to the eKERNEL, as shown in Figure 182: Example: eESPA module acts as input program on page 228. Figure 182: Example: eESPA module acts as input program If the specified data identifier is not present in the available datastream record, than the field eESPA_Group_default_str must be used to define a group in the message request.
eESPA parameters Figure 183: Example: eESPA module acts as output program Note: An eESPA module can act as input and output program simultaneously, so can receive alarms from the espa infrastructure and sends a message request to the eKERNEL, and can receive on message requests from the eKERNEL and sends the alarms to the espa infrastructure.
Table: eESPA This parameter is only relevant if eESPA acts as an input program (so receives external data from the espa infrastructure. If the specified data identifier is not present in the available datastream record, than the field eESPA_Msg_default_str must be used to define a default message. If the eESPA module acts as input program: The received espa record must be translated to a valid message request, and sent to the eKERNEL application.
eESPA parameters Figure 185: Example: eESPA module acts as output program An authorized of an entry typically found in this field is as follows: 2 eESPA_Msg_default_str This field is used to provide a default message, in the event that no value can be retrieved from the available datastream. In this case, the same value is used for all alarms generated through this eESPA interface instance.
Table: eESPA Than the data identifiers must be separated by a ^ sign. If for instance the beep code (data identifier 3) in combination with the priority (data identifier 6) must result in the alarm description, this value must be 3^6. If the display message (data identifier 2) is a part of the alarm description, you can specify the first x characters of the message as the alarm description.
eESPA parameters Figure 187: Example: eESPA module acts as output program An authorized of an entry typically found in this field is as follows: 2:3^3. This indicates that the first 3 characters of the display message, a ^ and the values of data identifier 3 is equal to the alarm description. The value NUR^1, NUR^2, SAN^1, and so on, must be configured in the eKERNEL_ALARM table.
Table: eESPA eKERNEL immediately upon arrival and these alarms are processed within DECT Messenger. In some environments, the remote peripherals cannot indicate that pending alarms are reset, and therefore the eKERNEL must handle the alarms. Use this field to configure eKERNEL_ALARM table to correctly handle the alarm requests and refrain from endless-loop conditions. As such alarms are typically *set with the option remove after sent. The eESPA_Remove_after_str are then set to *SENT.
eESPA parameters eESPA_Handshaking_n This field sets and returns the hardware handshaking protocol. The possible values are: 0 No handshaking. (comNone) 1 XOn/XOff handshaking. (ComXonXoff) 2 Request-to-send/clear-to-send handshaking (comRTS) 3 Both request-to-send and XOn/XOff handshaking. (comRTSXonXoff) The default value is 0.
Table: eESPA Figure 188: Example: eESPA module acts as output program An authorized of an entry typically found in this field is as follows: 3 eESPA_OUT_Nmbr_transm_default_str This field is only relevant if the eEPSA module acts as an output program, so for message sent from the eKERNEL to the eESPA interface. A request from the eKERNEL to the espa interface, contains a tag that defines the value for data identifier 5 (transmission number).
eESPA parameters Figure 189: Example: eESPA module acts as output program An authorized of an entry typically found in this field is as follows: 1 eESPA_Comments_str This field can be filled with comments, to allow administrators to add some remarks to the configuration record.
Table: eESPA 238 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 19: Table: eESPA_OUTBOUND_CFG eESPA_outbond_cfg parameters eESPAO_Site_id This field specifies the site identifier, as defined in eKERNEL_SITE. This value is, in most environments, equal to 1. An authorized of an entry typically found in this field is as follows: 1 eESPAO_Area_id_n This field specifies the site identifier, as defined in eKERNEL_AREA. This value is, in most environments, equal to 1.
Table: eESPA_OUTBOUND_CFG With the fields eESPAO_ALA_Prty_from_n and eESPAO_ALA_Prty_to_n you can specify a range of alarm priorities and set a relationship to the beepcode record type and the priority record type of the espa datablock. The Data identifier for the beepcode record type is 3. The Data identifier for the priority record type is 6.
eESPA_outbond_cfg parameters eESPAO_BeepCode_str This field specifies the data that must be entered in the espa datablock for record type beepcode (data identifier 3). An authorized of an entry typically found in this field is as follows: 1 eESPAO_Priority_str This field specifies the data that must be entered in de espa datablock for record type priority (data identifier 6).
Table: eESPA_OUTBOUND_CFG 242 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 20: Table: eIO_MODULE eIO_modules parameters eIOM_Site_id_n This field specifies the site identifier, as defined in eKERNEL_SITE table. In most environments, this value is 1. An authorized of an entry typically found in this field is as follows: 1 eIOM_Area_id_n This field specifies the area identifier, as defined in eKERNEL_AREA table. In most environments, this value is 1.
Table: eIO_MODULE Note: Specify the leading 0 in the numbering (enter the value 01, not 1).
eIO_modules parameters An authorized of an entry typically found in this field is as follows: 8 eIOM_Comments_str This field can be entered with remarks from an administrator, and is informational only. You can use this filed to document the physical connection here too, to ease later configuration. An authorized of an entry typically found in this field is as follows: OR 004 – fire detection. Table 21: eIO_module sample data on page 245 provides sample eIO module table data.
Table: eIO_MODULE 246 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 21: Table: eIO_AI eIO_AI parameters eIOAI_Site_id_n This field refers to the site identifier, as defined in the eKERNEL_SITE table. In most environments, this value is 1. An authorized of an entry typically found in this field is as follows: 1 eIOAI_Area_id_n This field refers to the area identifier, as defined in the eKERNEL_AREA table. In most environments, this value is 1.
Table: eIO_AI Current implementation of eIO is limited to configurations of up to 8 modules attached to one FP-1000 controller module. Avaya recommends starting the first module with number 01 and incrementing by one for the other modules. Specify the leading 0 in the numbering (do not specify 1, but specify instead 01). An authorized of an entry typically found in this field is as follows: 01 eIOAI_Contact_str This value refers to each individual contact, and is specified in the FieldPoint Explorer.
eIO_AI parameters eIOAI_Min_R_str The value specifies the analogue level measured on a contact to reset a minus-level alarm. If minus-level alarms are to be disabled a 00,000000 value can be specified. Note: All values must be specified in format 00,000000 with 2 digits before the decimal separator and 6 digits after the decimal separator. The decimal separator must be set according to the operating system regional settings.
Table: eIO_AI Belgium (Dutch) in Belgium, even when an English operating system is installed. These regional settings result in internal usage of decimal separator symbols in the form of period (.) or comma (,). If your system is set up with comma (,) as decimal separator, a comma (,) must also be specified when values are entered in the database.
eIO_AI parameters ALA_id_n ALA_INPGM_id ALA_Descr_str ALA_Remove_ 1160102 11601 A-INPUT ALA_Prty_n *RESET 5 An authorized of an entry typically found in this field is as follows: A-INPUT eIOAI_GRP_Name_str The group name describes what group is informed on the error condition, and refers to a group defined in eKERNEL_GROUP and eKERNEL_GROUP_MEMBER tables.
Table: eIO_AI SI A M C T R o o e E d n a t 252 Min_S Min_R Max_R Max_S ALA_d escr Gr ou p MSG 1 1 0 1 0 3 00,000000 00,000000 12,000000 20,000000 AINPUT AI Analog Input 03 1 1 0 1 0 4 00,000000 00,000000 12,000000 20,000000 AINPUT AI Analog Input 04 1 1 0 1 0 5 00,000000 00,000000 12,000000 20,000000 AINPUT AI Analog Input 05 1 1 0 1 0 6 00,000000 00,000000 12,000000 20,000000 AINPUT AI Analog Input 06 1 1 0 1 0 7 00,000000 00,000000 12,000000 20,000000 AINPUT
eIO_AI parameters SI A M C T R o o e E d n a t Min_S Min_R Max_R Max_S ALA_d escr Gr ou p MSG 2 1 0 1 0 8 00,000000 00,000000 12,000000 20,000000 AINPUT AI Analog Input 08 2 2 0 1 0 1 00,000000 00,000000 12,000000 20,000000 AINPUT 00 00 1 Analog Input 01 2 2 0 1 0 2 00,000000 00,000000 12,000000 20,000000 AINPUT 00 00 1 Analog Input 02 2 2 0 1 0 3 00,000000 00,000000 12,000000 20,000000 AINPUT 00 00 1 Analog Input 03 2 2 0 1 0 4 00,000000 00,000000 12,000000 20,0
Table: eIO_AI 254 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 22: Table: eIO_DI eIO_DI parameters eIODI_Site_id_n This field refers to the site identifier, as defined in the eKERNEL_SITE table. In most environments, this value is 1. An authorized of an entry typically found in this field is as follows: 1 eIODI_Area_id_n This field refers to the area identifier, as defined in the eKERNEL_AREA table. In most environments, this value is 1.
Table: eIO_DI and incrementing by one for the other modules. Specify the leading 0 in the numbering (do not specify 1, but specify instead 01). An authorized of an entry typically found in this field is as follows: 02 eIODI_Contact_str Valid values are in the range between 01 and 08 for the modules with 8 contacts and between 01 and 16 for the modules with 16 contacts. Note contact numbers start with 01 and are incremented by one.
eIO_DI parameters Table 24: eIO alarm description Alarm ID Input program Alarm description Remove after Priority 1160101 11601 D-INPUT *SENT 5 1160101 11601 D-INPUT *RESET 5 An authorized of an entry typically found in this field is as follows: D-INPUT eIODI_GRP_Name_str The group name describes what group is informed on the error condition, and refers to a group defined in eKERNEL_GROUP and eKERNEL_GROUP_MEMBER table.
Table: eIO_DI S A it R e e a 258 Mod Contact Type ALA_Descr GRP_ Name Message 1 1 01 03 GS D-INPUT DI Digital Input 03 1 1 01 04 GD D-INPUT DI Digital Input 04 1 1 01 05 OD D-INPUT DI Digital Input 05 1 1 01 06 OD D-INPUT DI Digital Input 06 1 1 01 07 OD D-INPUT DI Digital Input 07 1 1 01 08 OS D-INPUT DI Digital Input 08 1 1 01 09 OD D-INPUT DI Digital Input 09 1 1 01 10 OS D-INPUT DI Digital Input 10 1 1 01 11 GS D-INPUT DI Di
Chapter 23: Table: eIO_DO eIO_DO parameters eIODO_Site_id_n This field specifies the site identifier, as defined in the eKERNEL_SITE table. In most environments, this field has value 1. An authorized of an entry typically found in this field is as follows: 1 eIODO_Area_id_n This field specifies the area identifier, as defined in the eKERNEL_AREA table. In most environments, this field has value 1.
Table: eIO_DO An authorized of an entry typically found in this field is as follows: 01 eIODO_Contact_str This value refers to each individual contact, and is specified in the FieldPoint Explorer. Valid values are in the range between 01 and 16 for the currently supported FP-DO-401. Note contact numbers start with 01 and are incremented by one. You must specify the leading 0 in the numbering (do not specify 1, but specify instead 01).
eIO_DO parameters Site Area Module Contact Seconds 1 1 03 03 5 1 1 03 04 5 1 1 03 05 5 1 1 03 06 5 1 1 03 07 5 1 1 03 08 5 2 1 03 01 5 2 1 03 02 5 2 1 03 03 5 2 1 03 04 5 2 1 03 05 5 2 1 03 06 5 2 1 03 07 5 2 1 03 08 5 2 2 03 01 5 2 2 03 02 5 2 2 03 03 5 2 2 03 04 5 2 2 03 05 5 2 2 03 06 5 2 2 03 07 5 2 2 03 08 5 DECT Messenger Installation and Commissioning — Book 2 Comments March 2012 261
Table: eIO_DO 262 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 24: Table: eKERNEL_AREA eKERNEL_area parameters AREA_Site_id_n This field refers to the site identifier, as defined in the eKERNEL_SITE table. In most cases only one site is configured. A typical value is 1. An authorized of an entry typically found in this field is as follows: 1 AREA_Area_id_n This field indicates the area identifier. The combination site and area must be unique in the database. In most cases the configuration consists of 1 site and 1 area.
Table: eKERNEL_AREA The most significant focus is however on output program level. With the area concept, you can now configure, for authorized, more than one instance of eDMSAPI. This is most useful in larger environments (for authorized, 3 high-range iS-3090 switches covering 3 locations in an IMP network), where you can now install one eDMSAPI per area (location).
Chapter 25: Table: eKERNEL_ALARM eKERNEL_alarm parameters ALA_id_n This field specifies the unique identifier of the alarm. Although you can to enter a numeric value of choice, Avaya recommends developing a logical naming convention for alarms. A common approach is to base the numbering scheme upon input program identifier (that in turn is built upon site and area of the input program and a input program sequence number). A two-byte sequence number is the appended. This brings the length to seven bytes.
Table: eKERNEL_ALARM Byte 4-5 Byte 6-7 6 eIO 7 eWEB 8 eSMTP_server 9 eDMSAPI 01-99 Input program sequence number Alarm sequence number As shown in Table 27: Alarm identifiers on page 265, the first bytes denote the site identifier. The second byte denotes the area identifier. The third byte denotes the input application type. The fourth and fifth byte indicates a sequence number. These five first bytes refer to the inputprogram identifier.
eKERNEL_alarm parameters Byte 4-5 7 eWEB 8 eSMTP_server 9 eDMSAPI 01-99 Input program sequence number Avaya recommends using five digits to uniquely identify an input program. With the guidelines above, the identifier implies the site, area, input program application and sequence number. The ALA_id_n and ALA_INPGM_id_n both form a unique key, thus one input program with ALA_INPGM_id_n value 11101 cannot have two records with the same ALA_id_n value 1110101.
Table: eKERNEL_ALARM Example 2: TELEVIC TELEVIC sends alarms where behavior depends on tone code or message contents. If the alarm is described as TELEVIC, the system looks first for a string pattern (first blank or first xx characters as specified in the L:xx description of the INPGM_Model_str field of the eKERNEL_INPGM table (PROTOCOL CONVERTOR – L:03). If no length (L:xx) is specified, the default value is 3.
eKERNEL_alarm parameters you must specify *SENT, to prevent alarms that do not receive a *RESET from remaining active in the system. An authorized of an entry typically found in this field is as follows: *SENT ALA_Prty_n This field specifies the priority of an alarm. A low value indicates an important alarm, a high value a less important alarm. Avaya recommends that you exercise caution when assigning priorities to alarms.
Table: eKERNEL_ALARM ALA_to_Queued_n This field specifies the number of seconds a peripheral is kept in camp-on-busy state before taking further action. This parameter is ignored for all peripherals and is provided for backwards compatibility issues. An authorized of an entry typically found in this field is as follows: 15 ALA_Silence_intv_n This field specifies the number of seconds a peripheral is left quiet (idle) before repeating any outstanding messages (also referred to as pace interval).
eKERNEL_alarm parameters ALA_Scroll_intv_n This field specifies the number of seconds that is used as scroll interval, when peripherals allow scrolling. This parameter is, due to architectural reasons, ignored for most peripherals and is provided for backwards compatibility issues. An authorized of an entry typically found in this field is as follows: 3 ALA_Group_delivery_str This value defines the degree of message delivery that is required on delivery of a message to a group.
Table: eKERNEL_ALARM ALA_Repeat_intv_n This value defines the number of seconds between repeating alarm. Be careful not to confuse this entry with ALA_Silence_intv_n discussed above. The ALA_Repeat_intv_n is in most cases 0, meaning the alarm system does not repeat active alarms. ALA_Repeat_intv_n is kept to 0 in situations where the alarm systems can set a SET and RESET, or when the alarm system sends an alarm once at SET.
eKERNEL_alarm parameters For all other alarms, set this value to False. An authorized of an entry typically found in this field is as follows: False (-1) ALA_Trace_dayToKeep_n This value also refers to the trace function described in the ALA_Trace_b field. Set this value to 0, unless the value ALA_Trace_b is set to True (-1). In this case, tracing is activated for the alarm, and the number of days to keep the trace data must be entered. A typical value is 14 days.
Table: eKERNEL_ALARM 274 Alarm Inpgm Descr Remove after Priority ... 1110207 11102 REA *SENT 1 ... 1110208 11102 REA *RESET 1 ... 1110209 11102 1 *RESET 10 ... 1110210 11102 1 *SENT 10 ... 1110211 11102 *OTHER *RESET 20 ... 1110212 11102 *OTHER *SENT 20 ... 1110213 11102 GUARDING *SENT 10 ... 1110301 11103 API SENT *SENT 10 ... 1110302 11103 API RESET *RESET 10 ... 1110401 11104 GENERIC *SENT 10 ... 1110501 11105 1 *SENT 10 ...
eKERNEL_alarm parameters Alarm Inpgm Descr Remove after Priority ... 1190102 11901 E2_MSG_U *SENT 2 ... 1190103 11901 E2_NOODOPROEP *SENT 1 ... 1190104 11901 E2_REANIMATIE *SENT 1 ... 1190105 11901 E2_TEST_N *SENT 5 ... 1190106 11901 E2_TEST_U *SENT 2 ... 1210501 12105 1 *SENT 10 ... 1210502 12105 2 *SENT 999 ... 1210503 12105 3 *SENT 5 ... 1310501 13105 1 *SENT 999 ... 1310502 13105 2^9 *RESET 2 ... 1310503 13105 NUR *SENT 10 ...
Table: eKERNEL_ALARM 276 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 26: Table: eKERNEL_DEVICE eKERNEL_DEVICE parameters DEV_site_id_n This field refers to the site as specified in eKERNEL_SITE table. Usually this field has value 1. In most environments, this value is 1. An authorized of an entry typically found in this field is as follows: 1 DEV_Area_id_n This field refers to the area identifier, as defined in the eKERNEL_AREA table. In most environments, this value is 1.
Table: eKERNEL_DEVICE DEV_id_str This field contains a reference to the destination device as known in our internal infrastructure. When a device is, for instance, a DECT extension, this field specifies the extension number (for authorized, 865). When a mail destination is defined, this field contains a mail address (for authorized, francis.missiaen@1s.be). As such the next field GRP_OUTPGM_Appl_str further identifies the device for a specific site and area.
eKERNEL_DEVICE parameters • eSMTP for sending mail to SMTP-compliant infrastructure • eVBVOICE for sending audible messages DEV_OUTPGM_facility_str The indicated application handles the message using the capabilities of the infrastructure. The supported values are specified in the field FMT_OUTPGM_Facility_str of the eKERNEL_DEVICE_FORMAT table for the corresponding output program.
Table: eKERNEL_DEVICE and eSMS my means of inbound SMS message (based on CLIP of mobile phone or pincode in SMS message). With these pincodes, all messages for all devices with a matching pincode can be cleared. For authorized, pincode 12345 clears the alarms for those devices that specify 12345 in the DEV_PinCode_str field. An authorized of an entry typically found in this field is as follows: 12345. DEV_Prty_n This field is currently not implemented, but is foreseen for future enhancements.
eKERNEL_DEVICE parameters Important: In this case, the switch to the alternative device is immediate, which means that there is no silence interval between those two calls. Therefore, be very careful that there are no loop conditions defined in the eKERNEL_device_alt table. The value = 2 means that after the second try, the alternative device is contacted. For authorized, 2 => after 2 times trying to send the message, the alternative devices is set.
Table: eKERNEL_DEVICE See DEV_Div_Site_id_n An authorized of an entry typically found in this field is as follows: 1 DEV_Div_OUTPGM_Appl_str This field specifies the output program of the diverted device. See DEV_Div_Site_id_n An authorized of an entry typically found in this field is as follows: 1 DEV_Div_OUTPGM_Facility_str This field specifies the output program of the diverted device.
eKERNEL_DEVICE parameters Some multi-area environments require that you present devices that are configured for a remote area. You can select for each device whether the remote device is available to the local eWEB area or not. An authorized of an entry typically found in this field is as follows: False (0) DEV_Comments_str This field can contain remarks from the administrator, and is informational only.
Table: eKERNEL_DEVICE 284 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 27: Table: eKERNEL_DEVICE_ALT eKERNEL_DEVICE_ALT parameters ALT_Dev_Site_id_n This field refers to the site as specified in eKERNEL_SITE table. Usually this field has value 1. In most environments, this value is 1. An authorized of an entry typically found in this field is as follows: 1 ALT_Dev_Area_id_n This field refers to the area identifier, as defined in the eKERNEL_AREA table. In most environments, this value is 1.
Table: eKERNEL_DEVICE_ALT Define the device (site, area, device and outpgm) as a valid device in eKERNEL_DEVICE table. An authorized of an entry typically found in this field is as follows: 865 ALT_OUTPGM_Appl_str The field is associated with the previous field and defines the device. An authorized of an entry typically found in this field is as follows: eDMSAPI ALT_Sequence_n This field is a sequence number to make a record definitions in eKERNEL_DEVICE_ALT unique.
eKERNEL_DEVICE_ALT parameters ALT_Alt_OUTPGM_Appl_str This field defines, in combination with ALT_Alt_DEV_Site_id_n, ALT_Alt_DEV_area_id_, ALT_Alt_dev_id_str and ALT_Alt_OUTPGM_Facility_str the alternate device. Check for possible loop conditions when setting up this table.
Table: eKERNEL_DEVICE_ALT 288 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 28: Table: eKERNEL_DEVICE_FORMAT eKERNEL_DEVICE_FORMAT parameters Figure 191: eKERNEL_DEVICE_FORMAT parameters listing FMT_OUTPGM_Appl_str This field identifies the output program. The following options are supported: eASYNC, eCSTA, eDMSAPI, eESPA, eIO, eSMS, eSMTP and eVBVOICE. An authorized of an entry typically found in this field is as follows: eDMSAPI FMT_OUTPGM_Facility_str This field specifies the supported facility or facilities for a specified output program.
Table: eKERNEL_DEVICE_FORMAT Application Facility eASYNC KPN eCSTA C311 eCSTA C322 eCSTA C911 eCSTA C922 eCSTA C933 eCSTA D330 eCSTA D340 eCSTA P375D eDMSAPI C922 eDMSAPI C933 eDMSAPI C944 eDMSAPI I600 eESPA ESPA eIO DO eSMS SMS eSMTP SMTP FMT_Bytes_line1_n This field specifies the number of bytes available on the first line. In general, the maximum length is to be used. Refer to the sample data in Table 33: eKERNEL_DEVICE_FORMAT sample data on page 293 for authorizeds.
eKERNEL_DEVICE_FORMAT parameters FMT_Bytes_line3_n This field specifies the number of bytes available on the third line. In general, the value is smaller than the actual available size to reserve room for page indication and more indication. When a customer has infrastructure with extensions capable of displaying three lines of 16 bytes, alarm lengths up to 48 bytes can be displayed (without page indication and more indication).
Table: eKERNEL_DEVICE_FORMAT Table 32: More indication syntax 0 (no more indication) 1 + 2 + Note: This value is only implemented on eDMSAPI and eCSTA output programs. An authorized of an entry typically found in this field is as follows: 2 FMT_Concatination_b This field defines whether small messages that fit on one display are merged to one page. If, for authorized, a DECT C933 extension is defined as 16/16/0/5/2 and messages are a maximum 16 bytes, you can show two messages on a single page.
eKERNEL_DEVICE_FORMAT parameters to peripherals that support it. To prevent problems, the default equals false, so enabling emergency calls on supported devices is performed only on demand. Note: This value is only implemented on C944 devices. An authorized of an entry typically found in this field is as follows: 0 (false) FMT_Descr_str An administrator can enter a description of the template in this field. This value is informational only.
Table: eKERNEL_DEVICE_FORMAT 294 Application Facility Line 1 Line 2 Line 3 Page More eDMSAPI C4050 16 16 0 5 2 -1 999 eIO DO 1024 0 0 0 0 0 999 eSMTP SMTP 32 0 0 0 0 0 999 eVBVOICE VBVOIC E 1024 0 0 0 0 0 999 eESPA ESPA 128 0 0 0 0 0 999 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 29: Table: eKERNEL_GROUP eKERNEL_GROUP parameters Figure 192: eKERNEL_GROUP parameters listing GRP_id_str The field defines a unique identifier for a group. The field is a unique key in the database.
Table: eKERNEL_GROUP For each defined group, one or more group member must be defined in the eKERNEL_GROUP_MEMBER table. You can assign authority to the groups by means of the eKERNEL_GROUP_AUTH table. An authorized of an entry typically found in this field is as follows: 31101_00001 GRP_InPGM_id_n As described above, group identifiers are uniquely defined by combining input program identifier and group name. The input program is the value specified in the eKERNEL_INPGM table.
eKERNEL_GROUP parameters information in the alarm string. This can, for authorized, be referred to with terms such as paging number, group, or destination. Note that the above-described design allows sharing the same group name between multiple input programs. A first eCAP instance can have a different understanding for group 00001 than a second eCAP instance. In most cases the group names are determined by third-party vendors, and in many environments cannot be changed.
Table: eKERNEL_GROUP Group id 31801_00001 298 Input program 31801 Group name 00001 Description Comments Test from eSMTP DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 30: Table: eKERNEL_GROUP_AUTH eKERNEL_GROUP_AUTH parameters Figure 193: eKERNEL_GROUP_AUTH parameters listing GRPA_GRP_id_str This field refers to the unique group identifier, as described in the eKERNEL_GROUP table. Each group identifier must be defined in the eKERNEL_GROUP table. The member of each group identifier must be defined in the eKERNEL_GROUP_MEMBER table. At least one group member per group identifier must be defined, because empty groups result in loss of alarms.
Table: eKERNEL_GROUP_AUTH Note that eWEB only allows maintenance of the groups that are assigned to input programs of the same site as the eWEB. This means a eWEB instance of site 1 only allows maintenance of groups of site 1. An authorized of an entry typically found in this field is as follows: FMI GRPA_Comments_str This field can contains remarks of an administrator, and is informational only. eKERNEL_GROUP_AUTH parameters on page 299 provides sample eKERNEL_GROUP_AUTH table data.
Chapter 31: Table: eKERNEL_GROUP_MEMBER eKERNEL_GROUP_MEMBER parameters Figure 194: eKERNEL_GROUP_MEMBER parameters listing GRPM_GRP_id_str The field defines a unique identifier for a group. The field is a unique key in the database.
Table: eKERNEL_GROUP_MEMBER 7 - eWEB 8 - eSMTP_server 9 - eDMSAPI Byte 4-5 Input program sequence number Byte 6 (Underscore character) Byte 7-... Group name Example: 31101_00001 denotes site 3, area 1, input program type eCAP or eAPI, input program sequence 01, group name 00001. Each group must be defined in the eKERNEL_GROUP table. For each defined group, one or more group member must be defined in the eKERNEL_GROUP_MEMBER table.
eKERNEL_GROUP_MEMBER parameters Site Area Device Output program Facility 1 1 DO_03_05 eIO DO 1 1 DO_03_06 eIO DO 1 1 DO_03_07 eIO DO 1 1 DO_03_08 eIO DO 1 1 francis.missiaen@1s.be eSMTP SMTP 1 1 kristien.daneels@1s.be eSMTP SMTP GRPM_Dev_Site_id_n This value refers to the site identifier of the input program that is associated with the group. Refer to Table: eKERNEL_SITE on page 329 for more details on the site parameter.
Table: eKERNEL_GROUP_MEMBER Table 40: Supported output applications GRP_From_str This value specifies an hour and time in the format xx:xx. The valid range is 00:00 to 23:59; values outside this range produce unpredictable results. GRP_From_str denotes the start of the time interval where the defined device is an active member of the specified group GRP_Name_str. For authorized, 00:00 indicates the group-member is active at midnight, and 12:00 indicates the group-member starts at noon.
eKERNEL_GROUP_MEMBER parameters Table 41: Group member schedule authorizeds: GRP_Mon_b This value specifies whether the group-member record is active on Mondays. Accepted values are True (-1) or False (0). When -1 is specified, the group-member record is active on Mondays. When 0 is specified, the record is not active on this day. An authorized of an entry typically found in this field is as follows:-1 GRP_Tue_b This value specifies whether the group-member record is active on Tuesdays.
Table: eKERNEL_GROUP_MEMBER GRP_Fri_b This value specifies whether the group-member record is active on Fridays. Accepted values are True (-1) or False (0). When -1 is specified, the group-member record is active on Fridays. When 0 is specified, the record is not active on this day. An authorized of an entry typically found in this field is as follows:-1 GRP_Sat_b This value specifies whether the group-member record is active on Saturdays. Accepted values are True (-1) or False (0).
eKERNEL_GROUP_MEMBER parameters GRPM_Activate_timestamp_str This field specifies the timestamp when the record becomes activated. The format is YYYYMMDDHHMMSS. The GRPM_Activate_timestamp_str and GRPM_Desactivate_timestamp_str fields can be used to define a time interval, where records are active.
Table: eKERNEL_GROUP_MEMBER 308 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 32: Table: eKERNEL_GUARDING eKERNEL_GUARDING parameters Figure 195: eKERNEL_GUARDING parameters listing GUA_INPPGM_id_n This field specifies the unique identifier of the input program. Note that this identifier is defined in the eKERNEL_TCPCLIENT table (field TCPCLIENT_INPGM_id_n). Refer to Table: eKERNEL_TCPCLIENT on page 337 for more information on how to set up these input programs.
Table: eKERNEL_GUARDING GUA_To_str This value specifies an hour and time in the format xx:xx. The valid range is 00:00 to 23:59; values outside this range produce unpredictable results. The value denotes the end of the time period during which the guarding facility is active. The active time period begins at the time specified in GUA_From_str. Note: GUA_From_str can be larger than GUA_To_str, resulting, for authorized, in a job that starts at 21:00 and ends at 06:00.
eKERNEL_GUARDING parameters GUA_Wed_b This value specifies whether the group-member record is active on Wednesdays. Accepted values are True (-1) or False (0). When -1 is specified, the group-member record is active on Wednesdays. When 0 is specified, the record is not active on this day. An authorized of an entry typically found in this field is as follows:-1 GUA_Thu_b This value specifies whether the group-member record is active on Thursdays. Accepted values are True (-1) or False (0).
Table: eKERNEL_GUARDING GUA_Timeout_n This field specifies the timeout in seconds, before the defined guarding alarm is activated if no request (configuration request, message request, and so on) of the input program is received by the eKERNEL. If for instance a timeout of 900 seconds is defined, a guarding alarm is generated if the input program (eCAP, eAPI, and so on) does not send any request within fifteen minutes.
eKERNEL_GUARDING parameters An authorized of an entry typically found in this field is as follows: 11101. Refer to Table 43: Examples of alarm characteristics on page 313 for more authorizeds. Table 43: Examples of alarm characteristics GUA_Comments_str This field can optionally be used by an administrator to store reminder information, describing, for authorized, the usage of the file.
Table: eKERNEL_GUARDING 314 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 33: Table: eKERNEL_HOLIDAY eKERNEL_HOLIDAY parameters Figure 196: eKERNEL_HOLIDAY parameters listing Holiday_str This field defines a date that is to be considered as a holiday. Days that are entered here as holidays are important when eKERNEL processes the group members that are defined in the eKERNEL_GROUP_MEMBER table. Holidays must always be formatted as 8 bytes numeric values in format YYYYMMDD; for authorized, Christmas 2001 is defined as 20011225.
Table: eKERNEL_HOLIDAY Holiday_Comments_str This field can contain remarks from an administrator and is used only for informational purpose. Refer to Table 45: Holiday comments authorizeds on page 316 for authorizeds of Holiday comments values. Table 45: Holiday comments authorizeds Holiday_str Holiday_Comments_str 20050101 20050501 20050721 20050815 316 National Holiday DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 34: Table: eKERNEL_INPGM eKERNEL_INPGM parameters Figure 197: eKERNEL_INPGM parameters listing INPGM_id_n This field specifies the unique identifier of an input capable program. For each input program, a record must be entered in the eKERNEL_INPGM table. You must also define a matching record in the eKERNEL_TCPCLIENT table (field TCPCLIENT_INPGM_id_n). Avaya recommends that you develop a naming strategy in assigning values for this identifier.
Table: eKERNEL_INPGM 5 eCSTA 6 eIO 7 eWEB 8 eSMTP_server 9 eDMSAPI Byte 4-5 01-9 9 Input program sequence number Avaya recommends using five digits to uniquely identify an input program. Using this method, the identifier indicates the site, area, input program application, and sequence number. An authorized of an entry typically found in this field is as follows: 11101 INPGM_Site_id_n This field specifies the number of the site, as defined in eKERNEL_SITE table. In most cases this is 1.
eKERNEL_INPGM parameters INPGM_Manufacturer_str The behavior of different input program modules depends to the external alarm system, and is therefore manufacturer-related. You must always enter a valid value in this field. Refer to Table 47: Valid model values on page 319 for a complete list of valid values in current release.
Table: eKERNEL_INPGM Application Manufacturer Model eCAP TYCO MINERVA 80 eCAP WORMALD L:01 eCAP WORMALD *BASE eCAP WORMALD 1 eCAP WORMALD G:EIPM eESPA ESPA *BASE eESPA ESPA VSK (see PSI for details) eESPA ESPA ASCOM (see PSI for details) eDMSAPI DMSAPI *BASE eIO NATIONAL*BASE INSTRUMENTS eSNMP SNMP *BASE eSMTP_server SMTP *BASE eDMSAPI DMSAPI *BASE eVBVOICE VBVOICE *BASE eWEB eWEB *BASE INPGM_Bidir_b This field defines when the protocol is bidirectional to eKE
eKERNEL_INPGM parameters An authorized of an entry typically found in this field is as follows: COM01 INPGM_Settings_str This value must be set to blanks for the modules eAPI, IO, SMTP_server, VBVOICE and eWEB. The value must be set to the so-called COM-setting for the module eCAP (RS-232 interfaces). The settings must be a supported combination of baud-rate, parity, data-bits, and stop bits. The value must off-course match the settings of the attached alarm system.
Table: eKERNEL_INPGM An authorized of an entry typically found in this field is as follows: 0 INPGM_Default_DEV_OUTPGM_str The field INPGM_AutoCreateGRP_b allows you to indicate whether auto-create is enabled or disabled. If O is specified, the value INPGM_Default_DEV_OUTPGM_str is ignored. If -1 is specified, the value INPGM_Default_DEV_OUTPGM_str is used to indicate the output program that is associated with the device that is created automatically in the eKERNEL_DEVICE.
eKERNEL_INPGM parameters INPGM_Comments_str This field can contain remarks from the administrator and is informational only.
Table: eKERNEL_INPGM 324 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 35: Table: eKERNEL_MESSAGE_FORMAT eKERNEL_MESSAGE_FORMAT parameters Msg_Ala_id_n This field refers to the unique alarm identifiers as specified in the eKERNEL_ALARM table. See Table: eKERNEL_ALARM on page 265 for more information on alarm identifies. In a typical environment, input programs (for authorized, 11101) have a number of alarm identifiers (for authorized, 1110101 up to 1110107) each of them defining characteristics (alarm priority, length, and so on).
Table: eKERNEL_MESSAGE_FORMAT Byte 4-5 Byte 6-7 7 eWEB 8 eSMTP_server 9 eDMSAPI 01-9 9 Input program sequence number Alarm sequence number An authorized of an entry typically found in this field is as follows: 1110101 Msg_Msg_str This field describes the format of the result message after internal processing through eKERNEL. When no records are specified, received messages are transmitted as is to the destination party.
eKERNEL_MESSAGE_FORMAT parameters Msg_Comments_str This field can be updated with remarks of the system administrator. The value is informational only. Table 49: eKERNEL_MESSAGE_FORMAT sample data on page 327 shows authorizeds of data found in the eKERNEL_MESSAGE_FORMAT table.
Table: eKERNEL_MESSAGE_FORMAT 328 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 36: Table: eKERNEL_SITE eKERNEL_SITE parameters CFG_site_id_n This field specifies the site ID. In DECT Messenger, a site is the place where the eKERNEL module runs. Each eKERNEL instance has an appropriate database Messenger_CFG and Messenger_DATA. Note that a site can span multiple physical areas spread over multiple locations, and still being considered as one single site, because there is only one eKERNEL running. Note: The field is numeric.
Table: eKERNEL_SITE CFG_Site_Descr_str This field specifies a brief description of the site; usually the name of the institution or the name of the city is entered here. You can also enter, for authorized, your Avaya customer number. An authorized of an entry typically found in this field is as follows: Number One Systems CFG_Site_Admin_name_str This field specifies the name of the system administrator who is responsible within the institution for the installation.
eKERNEL_SITE parameters CFG_Site_eKERNEL_port_str This field specifies a port number. Valid port numbers are in the range between 0 and 65535. However, Avaya recommends that you avoid using ports in the range of 0 and 1024, as these ports are likely to used by other applications. Note: You can use the NETSTAT command to find out what ports are in use.
Table: eKERNEL_SITE For authorized, Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Password=sa;Initial Catalog=Messenger_DATA;Data Source=127.0.0.1; 3. SQL server 2000 Desktop Engine (residing on Messenger PC) For authorized, Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Password=philips;Initial Catalog=Messenger_DATA;Data Source=127.0.0.1; 4. SQL Sever resides on host SQLSERVER For authorized, Provider=SQLOLEDB.
eKERNEL_SITE parameters Note: On systems with a high workload the eLOG-files can consume a lot of disk space. To correct this, specify a small value for this parameter. An authorized of an entry typically found in this field is as follows: 30 CFG_Connectionstring_CFG_str This field is reserved for future releases and is not implemented yet. The default value is shown below: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\SOPHO Messenger@Net\Mdb \Messenger_CFG.
Table: eKERNEL_SITE CFG_GarbageCollection This field specifies the rate of garbage collection (internal use only). CFG_GarbageCollection refers to the number of seconds when alarms are considered expired when a does not receive a . This helps establishing internal recovery for non-responding devices and peripherals. Avaya recommends that you specify 600 for this value.
eKERNEL_SITE parameters For more information, see the user manual of the internal serial watchdog page 9 till 13. An authorized of an entry typically found in this field is as follows: 0x21 CFG_INRQS_id_n This field specifies a value that is used internally by eKERNEL, and you must not change the value unless explicitly instructed to do so. The value stored in CFG_INRQS_id_n is used to generate unique numbers to incoming message requests. Manipulation of this value can result in system malfunction.
Table: eKERNEL_SITE An authorized of an entry typically found in this field is as follows: "Development site of Number One System". Table 50: eKERNEL_SITE sample data on page 336 shows authorizeds of data found in the eKERNEL_SITE table (authorized data is split to improve readability) Table 50: eKERNEL_SITE sample data S it e Description Admin 3 Sample Site 3 Francis Missiaen Mail Address francis.missiaen @ 1s.be 10.110.50 .138 Port 9000 Socket ... Close after send ...
Chapter 37: Table: eKERNEL_TCPCLIENT eKERNEL-TCPCLIENT parameters TCPCLIENT_site_id_n This field refers to the site ID specified in the eKERNEL_SITE table. Usually this field has value 1. An authorized of an entry typically found in this field is as follows: 1 TCPCLIENT_kernel_port_str This field specifies the port that is reserved for the specified module. A client/server connection is established between eKERNEL and all adjacent modules.
Table: eKERNEL_TCPCLIENT Each module must have a dedicated TCP/IP port. Through this port, a socket connection is established between the module and the eKERNEL. The eKERNEL_TCPCLIENT table defines for the eKERNEL module an overview of all defined modules, and starts a socket server for each module.
eKERNEL-TCPCLIENT parameters Byte 4-5 2 eSNMP 4 eVBVOICE 5 eCSTA 6 eIO 7 eWEB 8 eSMTP_server 9 eDMSAPI 01-99 Input program sequence number Avaya recommends using five digits to uniquely identify an input program. With the guidelines above, the identifier implies the site, area, input program application, and sequence number. This value is refers to the unique identifier defined in the eKERNEML_INPGM table.
Table: eKERNEL_TCPCLIENT Note: For the eWEB module the value Close after receive must be specified if no script messages are used. If the Send Script Message functionality is implemented in eWEB, the value Close after send must be specified. This is a major issue, because closing a connection too soon can prevent eKERNEL from sending a feedback to the eWEB module. Note: When eAPI is used, you have the choice to specify any value.
eKERNEL-TCPCLIENT parameters Table 53: eKERNEL_TCPClient sample data on page 341 shows authorizeds of data found in the eKERNEL_TCPClient table.
Table: eKERNEL_TCPCLIENT 342 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 38: Table: eLOCATION eLOCATION parameters eLOC_Site_id_n This parameter refers to the site identifier, as defined in eKERNEL_SITE table. The eMODULE instance is uniquely defined through a site and an area, so eLOC_Site_id_n and eLOC_Area_id_n form a unique key in the table. An authorized of an entry typically found in this field is as follows: 1 eLOC_Area_id_n This parameter refers to the area identifier, as defined in eKERNEL_AREA table.
Table: eLOCATION PBX to obtain the IP address. The DAP Controller port is performing the role of TCP Server; the eLOCATION module is performing the role of TCP Client. An authorized of an entry typically found in this field is as follows: 10.110.49.169 eLOC_LA_port_str This parameter refers to the port number that is TCP Server on the DAP Controller is listening to. This value for a SIP DECT system should be 28008.
eLOCATION parameters eLOC_Retry_intv_n This field specifies the interval in seconds, to re-send a location request to the eLOCATION module when it previously received a negative acknowledge. An authorized of an entry typically found in this field is as follows: 10 eLOC_Polling_intv_n This parameter is not implemented in current release. Specify value “0” here.
Table: eLOCATION 346 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 39: Table: eLOCATION INBOUND RESULT eLOCATION_INBOUND_RESULT parameters eLOCIR_Inpgm_id_n This field defines an input program identifier, as defined in the table eKERNEL_INPGM. The identifier refers to the input program that generates the alarm. In the case of location detection, the detection of the location detection alarms are identified through inbound message on special extension that are defined in eDMSAPI_INBOUND table as type *LA (location alarm).
Table: eLOCATION INBOUND RESULT eLOCIR_Calling_dev_str This field contains the (internal) extension of the calling party, so the extension that initiated the alarm by sending a message to an extension type *LA specified above. This field can contain a fully qualified extension number (for instance 860) or a generic extension using an ending wildcard-character (for instance 86*) or a generic value '*ALL'. Fully qualified definitions have a higher priority than generic definitions.
eLOCATION_INBOUND_RESULT parameters eLOCIR_Msg_str This field defines the message that is used to generate a resulting alarm. The value can be a combination of constant text and replacement values.
Table: eLOCATION INBOUND RESULT 350 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 40: Table: eLOCATION RPN eLOCATION_RPN parameters eLOCRPN_Site_id_n This parameter refers to the site identifier, as defined in eKERNEL_SITE table. Each eLOCATION instance is uniquely defined through a site and an area. The eLOCATION_RPN table defines the relation between the RPNs and the associated text that describes the physical location on the RPN. For authorized, the DAP Controller with IP address 10.110.49.
Table: eLOCATION RPN key in the table eLOCATION_RPN table. The value should be formatted as a two-byte representation. For authorized, 1 should be formatted as 01. A special value “?” can be used as a catch-call to handle the RPNs that are not qualified. It is however recommended to specify all associated RPNs in the definition. A catch-all definition “?” could however be handy to detect missing definitions.
Chapter 41: Table: eOAI eOAI parameters eOAI_Site_id_n This field describes the site identifier, as defined in eKERNEL_SITE table. An instance of eOAI is uniquely defined by means of a site and area identifier. An authorized of an entry typically found in this field is as follows: 1 eOAI_Area_id_n This field describes the area identifier, as defined in the eKERNEL_AREA table. An instance of eOAI is uniquely defined by means of a site and area identifier.
Table: eOAI An authorized of an entry typically found in this field is as follows: 9090 eOAI_ALA_Prty_DTMF_Confirm_n This value refers to the priority of the alarm as specified in eKERNEL_ALARM table. Alarms distributed to eOAI with a priority above the defined value are automatically considered acknowledged when the destination receives the message. For most cases this is suitable. However, eOAI could deliver messages to infrastructure that are unable to respond.
Chapter 42: Table: eOAP eOAP parameters eOAP_Site_id_n This field describes the site identifier, as defined in eKERNEL_SITE table. An instance of eOAP is uniquely defined by means of a site and area identifier. An authorized of an entry typically found in this field is as follows: 1 eOAP_Area_id_n This field describes the area identifier, as defined in eKERNEL_AREA table. An instance of eOAP is uniquely defined by means of a site and area identifier.
Table: eOAP An authorized of an entry typically found in this field is as follows: 9090 eOAP_ALA_Prty_DTMF_Confirm_n This value refers to the priority of the alarm as specified in eKERNEL_ALARM table. Alarms distributed to eOAP with a priority above the defined value are automatically considered acknowledged when the destination receives the message. For most cases this is suitable. However, eOAP could deliver messages to infrastructure that are unable to respond.
Chapter 43: Table: eSMTP_CLIENT eSMTP_CLIENT parameters eSMTP_Site_id_n This field specifies the site identifier, as defined in eKERNEL_SITE table. In most environments, the value is 1. An authorized of an entry typically found in this field is as follows: 1 eSMTP_Area_id_n This field specifies the area identifier, as defined in eKERNEL_AREA table. In most environments, the value is 1.
Table: eSMTP_CLIENT An authorized of an entry typically found in this field is as follows: 10.110.17.6 eSMTP_srv_port_str This field specifies the port number used for SMTP access. In most environments, this is value 25. An authorized of an entry typically found in this field is as follows: 25 eSMTP_srv_domain_str This field refers to the domain name used in the SMTP connection. Refer to the RFC821 specifications on the process involved in message delivery through SMTP.
eSMTP_CLIENT parameters An authorized of an entry typically found in this field is as follows: 2 eSMTP_Silence_intv_n This field specifies the silence interval, the time between repeating outstanding messages that need confirmation. The parameter corresponds with the parameter available in the eKERNEL_ALARM table, but overrules the latter value. Due to bandwidth restrictions, a larger value than specified in eKERNEL_ALARM table is suitable.
Table: eSMTP_CLIENT 360 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 44: Table: eSMTP_SERVER eSMTP_SERVER parameters eSMTP_Site_id_n This field denotes the site identifier, as defined in eKERNEL_SITE table. In most environments, this field has a value of 1. An authorized of an entry typically found in this field is as follows: 1 eSMTPS_Area_id_n This field denotes the area identifier, as defined in eKERNEL_AREA table. In most environments, this field has a value of 1.
Table: eSMTP_SERVER This directory contains e-mail files (with the extension .EML) that are processed by DECT MessengereSMTP_server module, which analyzes the inbound e-mail files and handles them as alarm input. An authorized of an entry typically found in this field is as follows: c:\inetpub\mailroot\drop eSMTPS_Poll_intv_n This parameter defines the interval between individual poll operations the eSMTP_server module handles to look for inbound mail.
eSMTP_SERVER parameters eSMTPS_Email_keep_processed_n This field specifies the number of days the archive of processed e-mail messages is kept on the hard disk. The value is expressed in days, and has typically a value of 5 days. Adjust this value to accommodate for the number of inbound e-mail messages, the requested archive period, and the available disk space.
Table: eSMTP_SERVER eSMTPS_Delivery_text_str When an inbound e-mail message is accepted by eKERNEL, the sender receives a delivery report. This delivery report is sent through eSMTP client. (The eSMTP module is a prerequisite.) The message text for the delivery messages is defined in the eSMTPS_Delivery_text_str field.
Chapter 45: Table: eWEB eWEB parameters eWEB_Address_str This field specifies the IP address of the system where the Apache Web Server is running. You can obtain the address with the IPCONFIG command. The eWEB module uses this address to obtain its site, area number, and the address of the eKERNEL (based upon eWEB table) and to obtain the port number at which eKERNEL listens (based upon eKERNEL_TCPCLIENT table). This process is carried out in the PHP-scripts that run on the Apache Web Server.
Table: eWEB eWEB_Area_id_n This field specifies the area number associated to the eWEB instance obtained by the IP address of the Web Server. In most cases this value is 1, as defined in eKERNEL_AREA. An authorized of an entry typically found in this field is as follows: 1 eWEB_eKERNEL_address_str This field specifies the IP address of the eKERNEL. In the current release, this value is the same as the eWEB_Address_str field. Therefore, eKERNEL and the Apache Web Server must reside on the same computer.
Chapter 46: Table: eWEB_SCRIPT eWEB parameters WSC_Site_id_n This field specifies the site, as defined in eKERNEL_SITE table. In most environments, the value is 1. An authorized of an entry typically found in this field is as follows: 1 WSC_Area_id_n This field specifies the area, as defined in eKERNEL_AREA table. In most cases the value is 1.
Table: eWEB_SCRIPT Although you are free to enter a numeric value of choice, Avaya recommends establishing a naming convention for script messages. In the field ALA_Trace_b of the eKernel_alarm table, the administrator can activate this field (note that this feature is supported only for script messages in the current release), which means that the whole call flow is logged in the data database.
eWEB parameters WSC_Msg_str This field describes the message that is sent to the group members. Avaya recommends that you add a descriptive message that allows the recipient sufficient information to handle the alarm condition. Mobile users often lack immediate access to other information resources, such as a site map or technical specification. Avaya recommends that you keep the message length less than or equal to the maximum length defined in the associated eKERNEL_ALARM table.
Table: eWEB_SCRIPT WSCA_Comments_str This field can be used by an administrator to enter remarks. The field is informational only. 370 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 47: Table: eWEB_SCRIPT_SET_AUTH eWEB_SCRIPT_SET_AUTH parameters WSSA_Site_id_n This field specifies the site, as defined in eKERNEL_SITE table. In most environments, the value is 1. An authorized of an entry typically found in this field is as follows: 1 WSSA_Area_id_n This field specifies the area, as defined in eKERNEL_AREA table. In most cases the value is 1.
Table: eWEB_SCRIPT_SET_AUTH WSSA_UserID_str This field must have a username that corresponds with the USERA_UserID_str field of the eWeb_user_auth table or can be the keyword *ALL. If the value *ALL is entered, any user can set this script message. If one or more users are defined, only those users can set the related script message. If nothing configured in this table for a specific script message, no one can activate this script message.
Chapter 48: Table: eWEB_SCRIPT_TRACE_AUTH Note: An alarm is only traceable for script message if the ALA_Trace_b alarm ID related to the script message has the field ALA_Trace_b in the eKERNEL_ALARM table set to True. Note: In the current release, traceable alarms are only supported for script messages. eWEB_SCRIPT_TRACE_AUTH parameters Figure 198: eWEB_SCRIPT_TRACE_AUTH parameters WSTA_Site_id_n This field specifies the site, as defined in eKERNEL_SITE table. In most environments, the value is 1.
Table: eWEB_SCRIPT_TRACE_AUTH WSTA_Script_id_n This field must have a value that corresponds with any of the definitions in eWEB_script table for the eWEB interface. An authorized of an entry typically found in this field is as follows: 1 WSTA_UserID_str This field must have a username that corresponds with the USERA_UserID_str field of the eWeb_user_auth table or can be the keyword *ALL. If the value *ALL is entered, any user can trace this script message.
Chapter 49: Table: eWEB_SCRIPT_CANCEL_AUT H eWEB_SCRIPT_CANCEL_AUTH parameters WSCA_Site_id_n This field specifies the site, as defined in eKERNEL_SITE table. In most environments, the value is 1. An authorized of an entry typically found in this field is as follows: 1 WSCA_Area_id_n This field specifies the area, as defined in eKERNEL_AREA table. In most cases, the value is 1.
Table: eWEB_SCRIPT_CANCEL_AUTH WSCA_UserID_str This field must have a username that corresponds with the USERA_UserID_str field of the eWeb_user_auth table or can be the keyword *ALL. If the value *ALL is entered, any user can cancel this script message. If one or more users are defined, only those users can cancel the related script message. If nothing configured in this table for a specific script message, no one can cancel this script message.
Chapter 50: Table: eWEB_SNDGRPMSG eWEB_SNDGRPMSG parameters WGM_Site_id_n This field specifies the site identifier, as described in table eKERNEL_SITE. In most cases this value is 1. An authorized of an entry typically found in this field is as follows: 1 WGM_Area_id_n This field specifies the area identifier, as described in table eKERNEL_AREA. In most cases this value is 1.
Table: eWEB_SNDGRPMSG When entering a value in this field, ensure that the specified group name exists in the eKERNEL_GROUP table, and that the eKERNEL_GROUP_MEMBER contains at least one member. An authorized of an entry typically found in this field is as follows: 00001 (qualified group) or *ALL (generic group) WGM_Sequence_n This field is a sequence number and makes the records unique in the database.
eWEB_SNDGRPMSG parameters WGM_Comments_str This field can be used by an administrator to enter some remarks. The field is informational only. Table 56: eWEB_SNDGRPMSG sample data on page 379 shows authorizeds of data found in the eWEB_SNDGRPMSG table.
Table: eWEB_SNDGRPMSG Site 380 Area Group Sequence Message Alarm id Comment s 3 1 RAMPENPLAN 5 Fase 2 - end 317010 2 3 1 RAMPENPLAN 6 Fase 3 - end 317010 2 3 1 VSK_F 1 Brand gelijkvloers 317010 2 3 1 VSK_F 2 Brand verdieping 1 317010 2 3 1 VSK_F 3 Brand verdieping 2 317010 2 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 51: Table: eWEB_SNDUSRMSG eWEB_SNDUSRMSG parameters WUM_User_id_str This field specifies the user, as defined in eWEB_USER_AUTH table. The user is defined at the login process, where the web user enters a valid user and password. This user name is stored in the Web browser and reused as needed when authentication is needed for Web requests.
Table: eWEB_SNDUSRMSG WUM_Message_str This field specifies the message that is shown to the eWEB user in the Send User Message functionality, and finally is sent to the destination users. Note the length of the message must be smaller than or equal to the maximum length associated with the WUM_AlA_id_n definition in eKERNEL_ALARM table. For authorized, when an alarm identifier defines maximum length in eKERNEL_ALARM table of 48 bytes, the specified message must not be longer that 48 bytes.
eWEB_SNDUSRMSG parameters User Sequence Message Alarm id FMI 1 Private message 1 for FMI 3170103 FMI 2 Private message 2 for FMI 3170103 FMI 3 Private message 3 for FMI 3170103 FMI 4 Private message 4 for FMI 3170103 KDS 1 Private message 1 (Medium) 3170102 KDS 2 Private message 2 (Short) 3170101 KDS 3 Private message 3 (Long) 3170103 DECT Messenger Installation and Commissioning — Book 2 Comments March 2012 383
Table: eWEB_SNDUSRMSG 384 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 52: Table: eWEB_TOC eWEB_TOC parameters WTC_Site_id_n This field specifies the site identifier, as defined in eKERNEL_SITE table. The site is in most cases equal to 1. The Web Server determines its site and area based upon its own IP address, as defined in the eWEB table. An authorized of an entry typically found in this field is as follows: 1. WTC_Group_n This field contains a numeric sequence number, which is combined with WTC_Item_n and WTC_Language_str to generate a key.
Table: eWEB_TOC to logically sort table of contents in groups and items. Avaya recommends starting the first item in a group at 1 and incrementing by 1. An authorized of an entry typically found in this field is as follows: 1. WTC_Language_str This field contains a 4-byte language code. Refer to the documentation of the Table: eWEB_USER_AUTH on page 391 for a list of language codes.
eWEB_TOC parameters In most cases, this field contains a valid filename of a PHP-script, a HTML- filename of another valid string understood by a browser (for authorized, mailto:francis.missiaen@1s.be). Table 58: Valid WTC_Link_str values on page 387 provides a list of valid links that can be used. The files are shipped with eWEB module and are located in C:\SOPHO Messenger@Net \Web\htdocs. Table 58: Valid WTC_Link_str values eWEB_alarm_inquiry.php eWEB_chgpwd.php eWEB_device_inquiry.php eWEB_eDMSAPI.
Table: eWEB_TOC WTC_Comments_str This field can be used by an administrator to enter remarks. The field is informational only. Table 59: eWEB_TOC sample configuration on page 388 shows authorizeds of data found in the eWEB_TOC table. Figure 199: eWEB_TOC sample result (language 2909 and language 2963) on page 390 shows an authorized of the eWEB_TOC result for language 2909 and language 2963.
eWEB_TOC parameters Si Gr It t e ou e p m Language Text Link Level 3 4 0 2963 Overzicht 3 4 1 2909 Alarm Inquiry eWEB_alarm_inquiry.php 20 3 4 1 2963 Alarm overzicht eWEB_alarm_inquiry.php 20 3 4 2 2909 Device Inquiry eWEB_device_inquiry.ph p 20 3 4 2 2963 Device overzicht eWEB_device_inquiry.ph p 20 3 4 3 2909 Group Inquiry eWEB_group_inquiry.php 20 3 4 3 2963 Groeps overzicht eWEB_group_inquiry.php 20 3 4 4 2909 Table View eWEB_table_view.
Table: eWEB_TOC Figure 199: eWEB_TOC sample result (language 2909 and language 2963) 390 DECT Messenger Installation and Commissioning — Book 2 Comments? infodev@avaya.
Chapter 53: Table: eWEB_USER_AUTH EWEB_USER_AUTH parameters USERA_UserID_str This field contains a User ID. The eWEB module must define at least one user profile for authentication purposes. Avaya recommends that you create a user profile for each user that has access to the eWEB interface, to avoid alarms generated by unauthenticated users.
Table: eWEB_USER_AUTH Note: eWEB stores passwords without encryption in the Access 2000 database, and are therefore available to anyone who can access the DECT Messengersystem. Depending on your configuration, table information is accessible through eWEB. Because the security mechanism is limited, Avaya recommends that users not use the same password used on other systems that contain secured information, as that poses a serious security risk. Inform all users of this important issue.
EWEB_USER_AUTH parameters USERA_Allobj_b This field specifies whether a user has the authority to access all objects. In most cases the value False (0) is used. This means the user does not have authority to access all objects. Instead, the user only has access to maintain the groups he or she has been granted access to, as defined in the eKERNEL_GROUP_AUTH table.
Table: eWEB_USER_AUTH USERA_Language_str This field contains a 4-byte identifier that denotes the language used for eWEB-access and eGRID-access. Enter one of the valid language codes provided in Table 60: Currently supported language values in eWEB on page 394. The codes are in the range 2900–2999. A small number of languages are currently supported, but additional languages can be implemented if needed.
EWEB_USER_AUTH parameters Code Language 2929 German 2931 Spanish 2932 Italian 2933 Norwegian 2937 Swedish 2938 English Uppercase Support for Double-Byte Character Set (DBCS) 2939 German Multinational Character Set 2940 French Multinational Character Set 2942 Italian Multinational Character Set 2950 English Uppercase 2954 Arabic 2956 Turkish 2957 Greek 2958 Icelandic 2961 Hebrew 2962 Japanese Double-Byte Character Set (DBCS) 2963 Belgium Dutch 2966 Belgium French 2972
Table: eWEB_USER_AUTH Code Language Character Set (DBCS) 2989 Simplified Chinese Double-Byte Character Set (DBCS) (PRC) 2992 Romanian 2994 Slovakian 2995 Albanian 2996 Portuguese Multinational Character Set 2998 Farsi Note: The language-code corresponds with an entry in eGRID that provides a directory where the language dependent files are stored. This path is usually C:\SOPHO Messenger@Net\pdf \mri29xx.
Index Special Characters .reg files ......................................................................79 A AccuCall ....................................................................114 Activate scripts .........................................................168 Active alarms ............................................................159 Active scripts ............................................................170 Activity of eSMTP_server ...........................................
Configuration of advanced facilities ..........................174 Configuration of advanced groups ............................178 Configuration of advanced users ..............................180 Configuration of basic alternative devices ................164 Configuration of basic group members .....................162 Configuration of environments and tasks ...................73 Configuration of eVBVOICE AVHR ..........................122 Configuration tables .............................................
eDMSAPI_DataPathDelay_n ....................................212 eDMSAPI_eKERNEL_Seats_count_n .....................208 eDMSAPI_External_Address_str .............................208 eDMSAPI_External_Port_str ....................................209 eDMSAPI_External_Seats_count_n .........................208 eDMSAPI_GeneralTimeOut_n .................................212 eDMSAPI_Guarding_Polling_intv_n .........................211 eDMSAPI_Guarding_Retry_intv_n ...........................
eIODO_Seconds_n ..................................................260 eIODO_Site_id_n .....................................................259 eIOM_Area_id_n ......................................................243 eIOM_Comments_str ...............................................245 eIOM_Contact_cnt_n ................................................244 eIOM_Module_str .....................................................243 eIOM_Site_id_n ........................................................
eSMTP_Silence_intv_n ............................................359 eSMTP_Site_id_n .............................................357, 361 eSMTP_srv_domain_str ...........................................358 eSMTP_srv_ip_str ....................................................357 eSMTP_srv_port_str .................................................358 eSMTP-server shortcut parameters ...........................29 eSMTPS_ALA_id_n ..................................................364 eSMTPS_Area_id_n ..........
GRP_To_str ..............................................................304 GRP_Tue_b ..............................................................305 GRP_Wed_b ............................................................305 GRPA_Comments_str ..............................................300 GRPA_GRP_id_str ...................................................299 GRPA_UserID_str .....................................................299 GRPM_Activate_timestamp_str ...............................
N National Instruments example ..................................267 O Outbound calls ...........................................................95 Output program activity ..............................................17 P P .................................................................................91 0 ...........................................................................91 1 ...........................................................................91 Password ................................
Table eKERNEL_DEVICE_ALT ................................285 Table eKERNEL_DEVICE_FORMAT .......................289 Table eKERNEL_GROUP ........................................295 Table eKERNEL_GROUP_AUTH .............................299 Table eKERNEL_GROUP_MEMBER .......................301 Table eKERNEL_GUARDING ..................................309 Table eKERNEL_HOLIDAY ......................................315 Table eKERNEL_INPGM ..........................................
WSSA_Comments_str ..............................................372 WSSA_Script_id_n ...................................................371 WSSA_Site_id_n ......................................................371 WSSA_UserID_str ....................................................372 WSTA_Area_id_n .....................................................373 WSTA_Auth_str ........................................................374 WSTA_Comments_str ..............................................
