Avaya CS1000 User Manual

Browse online or download User Manual for Smartphones Avaya CS1000. Avaya CS1000 User's Manual

  • Download
  • Add to my manuals
  • Print
  • Page
    / 245
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews

Summary of Contents

Page 1 - Commissioning — Book 1

DECT Messenger Installation andCommissioning — Book 1Avaya Communication Server 10007.5NN43120-301, 03.02March 2012

Page 2

Introduction10 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 3

Once a link is established between eCAP and the alarm system, the eCAP handles furthercommunications and informs eKERNEL when relevant information is

Page 4

Manufacturer ModelTELEVIC PROTOCOL CONVERTOR – L:03TYCO MINERVA 80VSK DE LICHTERVELDEVSK OLV VAN VREDEVSK ST-JOZEFWORMALD *BASEWORMALD L:01WORMALD G:E

Page 5

Figure 56: Sample Aritech protocol dataAritech alarms are always sent to group ARITECH, because no pager information is availablein the datastream. Me

Page 6

Figure 57: ARITECH Model 1 alarm (based upon installation RUCA)Aritech model 1 alarms are always sent to group ARITECH_F, ARITECH_C, or ARITECH_B,depe

Page 7 - Revision history

BEMACValid manufacturer is BEMAC, valid model is DIANA 1 and DIANA 2.Bemac is based upon installation Clinique St-Vincent Rocourt.Figure 58: Sample Be

Page 8 - New in this release

For example, L:48-0:RC-1:SR-2:SS-3:SS-4SR means the alpha-messages are 48 bytes long,tone code 0 denotes *RESET alarm remove after *CALC, tone code 1

Page 9 - Chapter 2: Introduction

Model 3400The GENT model 3400 transmits binary datastreams of 56 bytes. The first bytes identify thealarm type. Currently, only Fire and Super Fire ar

Page 10 - Introduction

Model VIGILIN EN54Figure 61: Sample Model VIGILIN EN54Currently, only records starting in 3rd line MCP or FIRE are processed.For FIRE alarms, the grou

Page 11 - Server PC requirements

The group is identified by the first fields, for example, 00001, and the message is identified bythe second field (This is a sample message). Currentl

Page 12 - Database server requirements

STEAFA Note:The Landis-Steafa interface was not ordered nor implemented and protocol information isprovided on an as-is basis. Contact your software v

Page 13 - Network information

Chapter 3: System requirementsThe following sections describe the system requirements for DECT Messenger.Supported operating systemsThe following ope

Page 14 - System requirements

BEERPUT -> BEERPUT• Look up the occurrence of the first space characterNUR K100 -> 4BEERPUT -> 8• Keep the leading non-blank charactersNUR K1

Page 15

Figure 64: Sample Televic protocol dataTelevic is an extended two-direction protocol, which provides a number of protocol rules tokeep the communicati

Page 16 - Installation steps

TYCOThe valid manufacture is TYCO and the valid model is MINERVA 80.Figure 65: Sample MINERVA 80 protocol dataAn alarm is sent to the group MINERVA an

Page 17

Valid models are:• DE LICHTERVELDE• OLV VAN VREDE• ST-JOZEFVSK is based upon the three installations defined in the model, with a different implementa

Page 18 - Preparing external devices

Figure 67: Sample OLV VAN VREDE protocol dataModule - eCAP114 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? infodev@a

Page 19

Figure 68: Sample ST-JOZEF protocol dataFire alarms are sent to group VSK_F (fire alarm) with alarm description VSK_F, system errorsare sent to group

Page 20 - Table 3: I/O modules overview

All alarms are *SET with remove after *RESET. When GENERAL RESET occurs in thedatastream, all active alarms for the VSK input program are reset for al

Page 21

Table 10: F8000 REV EVACUA groupsModel Group*BASE WORMALD_F.L:01 8 (group description: field GRP_Descr_strfrom table eKERNEL_GROUP)L:02 80L:03 800L:04

Page 22

Table 12: RUCA0000. BrandBoodschapMG 099 MLD 009 01:01:00 01.01.97This datastream results in a *SET of alarm description WORMALD_F, with messageBoods

Page 23 - Software installation

Chapter 15: Module - eESPAThe module eESPA consists of one program. The program is eESPA.exe and is written in Visual Basic(v6.0).In general, the pro

Page 24

Client PC RequirementsDECT Messenger client modules are supported on any PC capable of running the supportedoperating systems. A DVD drive is required

Page 25 - Installing IIS

section of the shortcut that initiates eESPA.exe. This shortcut is usually located in the WindowsStartup group.Figure 69: Typical parameters in the sh

Page 26

Figure 70: Typical cfgrqs configuration request and its received cfgrpy configuration replyRefer to the appropriate sections on the database tables th

Page 27

Figure 71: eESPA Connection tab showing a valid configurationBecause the eESPA is designed to handle serial data communications with a number of pagin

Page 28

the distance between the DECT Messenger and the external-paging system is relatively small,so no extra hardware is needed.Once a link is established b

Page 29

eESPA handles only data blocks of type 1, Call to Pager data blocks. If another type of datablock comes in, eESPA reacts by sending an ACK, but the da

Page 30

an offline list (also known as a black list) the polling interval is not disturbed by repeatedtimeouts of some slaves.The controlling station stops po

Page 31 - Installing Adobe Reader 9

LoggingIn the Logging tab, only basic (default) logging is shown.Basic logging: incoming and outgoing data on the communication port (I:COM and O:COM)

Page 32 - Installing SQL Server

Figure 77: Field model containing VSKRestrictions:• Configure eESPA as Control station value No. The remote system is then control stationand handles

Page 33

Figure 79: 1[ENQ][EOT], no responseFor example, the FalconNet fire detection system alternatively polls itself and then the remotesystem (eESPA), as s

Page 34

Figure 81: Logging using model VSKManufacturer ESPA and model VSKDECT Messenger Installation and Commissioning — Book 1 March 2012 129

Page 35

Network informationTable 1: Network informationPort Description80 Port for HTTP traffic used by Web Administrator application1433 Default SQL Server p

Page 36

Module - eESPA130 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 37 - Installing DECT Manager

Manufacturer ESPA and model VSKDECT Messenger Installation and Commissioning — Book 1 March 2012 131

Page 38 - Install DECT Manager

Module - eESPA132 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 39

Chapter 16: Module - eESPA - sampleMASTER (address 1) SLAVE (address 2)No data to be transferred2ENQEOTMaster has data to be transferred1ENQ (I want

Page 40

MASTER (address 1) SLAVE (address 2)1NAKEOTSlave has data to be transferred2ENQ1ENQ (I have data for address 1)ACK (I am ready to receive data)DATA Bl

Page 41

Chapter 17: Module - eDMSAPIThe module eDMSAPI consists of two separate programs. One program is eDMSAPI and is written inVisual Basic. The other pro

Page 42

of the first NIC adapter found in the PC. You can determine the IP address using theIPCONFIG.exe command or in the appropriate sections of the Windows

Page 43 - Uninstalling DECT Messenger

DMC DMC ETHERNET_DMCAVAYA AVAYA DasgifRefer to the chapters of this document that deal with the database tables for more informationon each value. A d

Page 44

Figure 85: eDMSAPI tabNote that during call handling, the eDMSAPI tab shows an overview of current call states ofeach device. The window consists of t

Page 45 - Messenger

Overview of CSTA_Service.EXEThe CSTA_Service runs behind the scenes and communicates through CSTA.DLL with a PBX.The CSTA_Service acts as TCP server t

Page 46 - Configuring DECT Messenger

System requirements14 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 47

Figure 87: Logging informationSample logging data is shown in Figure 88: Log example: initialization procedure onpage 141.Module - eDMSAPI140 DECT

Page 48

Figure 88: Log example: initialization procedureLoggingDECT Messenger Installation and Commissioning — Book 1 March 2012 141

Page 49 - Starting eKERNEL

Module - eDMSAPI142 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 50 - Using eCONFIG (Configurator)

LoggingDECT Messenger Installation and Commissioning — Book 1 March 2012 143

Page 51

Figure 89: Log example: Message handlingModule - eDMSAPI144 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? infodev@ava

Page 52

LoggingDECT Messenger Installation and Commissioning — Book 1 March 2012 145

Page 53 - Configuring site information

Module - eDMSAPI146 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 54 - Removing unused modules

Chapter 18: Module - eFR Important:Due to the ongoing development of the DECT Messenger product suite, some modules that provideadditional functional

Page 55 - Configuring area information

Overview of monitoringThe monitoring section covers four items.• OM sectionThe OM section is not applicable for traditional and SIP DECT systems.• DIS

Page 56 - Configuring PBX information

different information is found. You are notified when the socket is no longer "listening" orestablished, and you are notified when the socke

Page 57 - Adding a device

Chapter 4: Installation stepsThe Avaya DECT Messenger installation steps assume that all operating system and hardwarerequirements are met. The follo

Page 58

and active on the destination system, and all prerequisite conditions for named pipesmessaging applies.Install module eFRFollow the steps in the next

Page 59

Do not logoff the desktop as this ends the monitoring application.License module eFRThe module eFR is a licensed software module. The module eFR canno

Page 60

You can use Microsoft Internet Explorer to access files with XML extensions. TheseXML files must have the correct syntax or XML cannot be opened by In

Page 61 - Publishing changes

Other transport mechanisms can require you to perform actions in the destinationsite, for example for NET SEND, the messenger service needs to be acti

Page 62

You can use the windows delivered with Notepad or Wordpad accessories maintainthe XML file.On the internet, a number of free XML editors are available

Page 63 - Discarding changes

• SMS SMS is used with SMS technology to send a SMS message to adestination mobile GSM phone.• SMTP SMTP is used when sending an e-mail message by mea

Page 64 - Configuring the eCONFIG.ini

Figure 92: Parameter toDestinations type SMSThe following figure illustrates Destinations type SMS.Figure 93: Destinations type SMSThe following param

Page 65 - Chapter 10: Module eAPI

Figure 94: Destinations type SMTPThe following parameters are specific to SMTP.• The parameter "description" refers to the name of the desti

Page 66 - Message format

Figure 95: Destinations type SNMPThe following parameters are specific to SNMP.• The parameter "description" refers to the name of the desti

Page 67

Figure 96: Example of monitoring section and subsectionsThe parameter interval, with a default value of 600, specifies the frequency at which themonit

Page 68 - Module eAPI

• Installing SQL Server on page 32• Installing DECT Manager on page 37• Configuring DECT Messenger on page 46•Install a DECT Messenger Client on page

Page 69 - More extended program

Monitoring type DISKThe monitoring of disk drives is configured through the section in the XML file shown in thenext figure.Figure 97: Monitoring type

Page 70 - Real-world examples

Figure 98: Define drives for monitor type DISKThe line shown in the following figure is the opening tag for a drive definition.Figure 99: Opening tag

Page 71

Figure 100: Required conditions met for monitor type DISKYou define the message and the destinations to be informed in the following circumstances.• W

Page 72 - Module - eAPI sample

Figure 105: Drive not ready to be sent as SNMPv1 trapThe following figure shows the message received by the destination device, implemented inDECT Mes

Page 73

Figure 107: Monitoring type PING configurationThe definition of a system that needs to be monitored with PING is done using a <System>line.Figur

Page 74

system and the larger the possible timeout, the less responsive the system. This means thatthe processing time increases, and the number of verificati

Page 75

Monitoring type NETSTATYou can verify the configured list of connections using the NETSTAT monitoring capability. Youcan verify the TCP server connect

Page 76

Figure 113: TCP server definitionThe definition of a connection contains the following parameters.• Define the parameter id (name) with a unique ident

Page 77

Figure 115: Monitoring the state of the TCP serverIf the SMTP Server is stopped by an administrator, the socket no longer is "listening" on

Page 78

address and the port the server listens to. The following figure illustrates that the server listenson port 3102.Figure 117: TCP client/server connect

Page 79

Chapter 5: Preparing external devicesThis chapter provides information on preparing external devices.Integration with IP-DECT ManagerYou can connect

Page 80

Figure 119: Sample e-mailModule - eFR170 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 81 - Chapter 12: Module - eASYNC

Chapter 19: Module - eGRIDThe eGRID application gives you a view of the different tables in the databases.You can start the eGRID.exe application wit

Page 82 - Module - eASYNC

• Use the third drop-down list to select a table. The available tables are retrieved automatically fromthe database object• Use the fourth drop-down l

Page 83

Figure 121: eGRID with Show help modeDECT Messenger Installation and Commissioning — Book 1 March 2012 173

Page 84 - Figure 42: eASYNC tab

Figure 122: eGRID with View another table modeModule - eGRID174 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? infodev

Page 85 - Figure 43: eASYNC Logging tab

Figure 123: eGRID grouping functionsBecause eGRID is the preferred access method for maintenance, an extra functionality is implementedto optimize fle

Page 86

Figure 124: eGRID Data FilteringLook at the column header to find out what data type the field has. Because the filtering function is basedupon SQL in

Page 87

Important:Ensure the eGRID module is not made available for unauthorized access. Remove the shortcut whereapplicable. The eGRID module provides direc

Page 88

Module - eGRID178 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 89 - Chapter 13: Module - eBACKUP

Chapter 20: Module - eIOOverviewThe eIO module is a stand-alone application that communicates with eKERNEL. The moduleis capable of controlling and m

Page 90 - To_file

Figure 2: Integration with Call Server 1000IP-DECT Manager TCP/IP port for DECT MessengerOn the IP-DECT Manager system, there is a TCP/IP port open fo

Page 91

value is usually specified, because eKERNEL and eIO both share the same networkadapter. When eIO is running on a different computer, the IP address of

Page 92 - Module - eBACKUP

Figure 129: eIO configuration request and responseWhen the configuration is received, the eIO updates the configuration information on theConnections

Page 93 - Figure 51:

Figure 130: eIO Connections updateeIO ModulesSelect the eIO tab to see a panel with details of the available modules and contacts. Use thedrop-down li

Page 94 - Figure 51: Sample backup log

Figure 131: eIO analogue input modulesFor each module, the URL is shown, and the module identifier. When you hold the mousepointer over the status are

Page 95 - Figure 52: File copy example

Figure 132: Analogue input ranges Note:Alarm values are given in pairs. Both maximum and minimum alarms are set and resetwith different values. This w

Page 96

Figure 133: Digital Input module information Note:When the value of a contact changes from Off to On or from On to Off, the Before and Afterfields are

Page 97 - Chapter 14: Module - eCAP

Figure 134: Digital Output module information Note:When the value of a contact changes from Off to On or from On to Off, the Before and Afterfields ar

Page 98

Figure 135: eIO loggingThe log files on disk contain the same information as shown on-screen. On the next few pages,Figure 135: eIO logging on page 18

Page 99

Figure 137: Log example: Configuration procedureModule - eIO188 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? infodev

Page 100 - Functional description

Figure 138: Log example: Binding to OPC ServersFigure 139: Log example: Message RequestFigure 140: Log example: TerminationLoggingDECT Messenger Insta

Page 101

[DAPPRF] ; Start of DAPPRF address section 192.168.17.74 [CDA] ; Start of CDA address section 192.168.17.74 30160 [GK] ; Start gatekeeper address sect

Page 102 - Module - eCAP

Module - eIO190 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 103

Chapter 21: Module - eKERNELGeneraleKERNEL is the core engine of the DECT Messenger, and is in the basic implementation theonly module that accesses

Page 104

License ManagerThe Avaya DECT Messenger package is secured by a licensing system, to prevent unlicensedusage of certain modules and clients.Figure 142

Page 105

Equipment and Functionality modelsThe licensing system distinguishes between equipment models and functionality models.• The following models are assi

Page 106 - Model 3400

license cannot be bound or no correct functionality is available, the eKERNEL tab-page is notupdated, and the crossed-through key icon remains.eAPI an

Page 107 - Model VIGILIN EN54

menu command: eKERNEL > License > functionality as shown in Figure 144: Addinglicense functionality on page 195. Note:eKERNEL makes this same ch

Page 108

DatabaseThe eKERNEL application is the only application that communicates directly with thedatabases. Every external application receives its configur

Page 109

Menu options• File > ExitThis option closes the eKERNEL application.• eKERNEL > Reset all alarmsThis option clears all active alarms in the data

Page 110 - Comments? [email protected]

Figure 145: Watchdog enabledGuardingFor every input program, the administrator can configure a guarding facility, as shown in Figure146: Guarding info

Page 111

Figure 146: Guarding informationGuardingDECT Messenger Installation and Commissioning — Book 1 March 2012 199

Page 112

© 2012 Avaya Inc.All Rights Reserved.NoticeWhile reasonable efforts have been made to ensure that theinformation in this document is complete and accu

Page 113

Table 2: Control modules overviewModuletypeDescription Additional InfoFP-1601 Control module with IPinterfaceInterface module between the I/O modules

Page 114

Module - eKERNEL200 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 115

Chapter 22: Module - eLICENSE Important:Due to the ongoing development of the DECT Messenger product suite, some modules that provideadditional funct

Page 116

add-on modules are activated. In the majority of the cases, add-on modules, such as eFR,reside on the MESSENGER system running eKERNEL. However, when

Page 117 - 27/04/99 19:56:12

2. Save the XML file by selecting File > Save Fingerprint.3. Accept the default path C:\SOPHO Messenger@Net\Xml .The default filename is usually yo

Page 118 - 0001. Reset

Applying the keyThe license file name contains the originating computer name, for example, MESSENGER, aswell as the licensed module name, for example,

Page 119 - Chapter 15: Module - eESPA

Figure 148: Invalid license key warningIf this occurs, request an updated license file. Note:If you cannot wait to restart the system, type the word E

Page 120 - Module - eESPA

Module - eLICENSE206 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 121

Chapter 23: Module - eLOCATION Important:Due to the ongoing development of the DECT Messenger product suite, some modules that provideadditional func

Page 122

Figure 149: eLocation module keywordsThe following keywords are used to start the eLocation module.• The "site" keyword indicates the site t

Page 123

Figure 151: eLocation configuration connections tabThe logging tab shows logging information.Figure 152: eLocation configuration logging tabInitializa

Page 124 - Data flow

The following figure shows an example of how a rail of National Instruments I/O modules canbe connected to DECT Messenger. On a rail, there can be var

Page 125

Program activityWhen the startup phase is done, eLOCATION has two permanent socket connections.• One socket connection is established with the eKERNEL

Page 126

Figure 154: Idle state of system at startupAfter the processing of a location request, the panels are updated as shown in the followingfigure.Figure 1

Page 127

Figure 156: Logging panelArchitectureThere are several steps involved to make eLOCATION operational.The effected items in the setup of the functionali

Page 128

Figure 157: eConfig illustrates the configuration processIn the following two figures, extension 112 with type '*LA' is defined for location

Page 129

Figure 158: Module eDMSAPI• The next item that you must define is the correct record in the tableeDMSAPI_INBOUND_EVENT for the special number defined

Page 130

Figure 159: Module eDMSAPI inbound eventThe following figure illustrates detailed configuration for a special number ineDMSAPI_INBOUND_EVENT table.Arc

Page 131

Figure 160: Module eDMSAPI inbound event - detailed configuration• Next the eKERNEL module contacts the eLOCATION module to find out the physicallocat

Page 132

Controller. This DAP Controller, 192.168.32.10, is handled by eLOCATION site 1 area 2as shown in the following figure.Figure 161: Configuration of eLO

Page 133

Figure 162: Module eLOCATION board definitionFigure 163: Module eLOCATION board 00 definitionModule - eLOCATION218 DECT Messenger Installation and

Page 134

• Next the eLOCATION_RPN table must be populated with records for every RPN knownin the DAP Controller configuration. In the following figure, RPN &qu

Page 135 - Chapter 17: Module - eDMSAPI

Figure 5: Example of connecting multiple FP rails to DECT MessengerThe connection between the DECT Messenger PC and the first rail is achieved by mean

Page 136

Figure 165: eLOCATION_INBOUND_EVENT tableIn the sample in the following figure, alarms from the eDMSAPI input program 12901, site1, area 2 and all cal

Page 137 - AVAYA AVAYA Dasgif

Figure 166: eLOCATION inbound result SOS message from eDMSAPIThe following figure shows an example of a message sent to the group as defined in theMes

Page 138 - Module - eDMSAPI

number] is introduced in release 3.0. In release 3.0 and subsequent releases, when thesystem configuration configures a device with a visual DNR, this

Page 139 - Overview of CSTA_Service.EXE

Chapter 24: Module - eSMS Important:Due to the ongoing development of the DECT Messenger product suite, some modules that provideadditional functiona

Page 140

• an antenna for the TC35i, included in TC35i• a SIM card of mobile provider of choice with a PIN and a PUK codeFollow the steps in the next procedure

Page 141

SMS_service.exe and SMS_service.ini are two resources related to SMS_servicefunctionality.Configure SMS_service through the .INI file. The default val

Page 142

For example, if you have a need for high-level redundancy, you can use SIM cards from twodifferent mobile providers. If one box of SIM card fails, you

Page 143

Figure 173: SMS_service operationalThe module polls the box to find out if inbound messages are received from external mobilephones through the mobile

Page 144

Figure 174: Startup values promptThe command line parameters are shown in the following figure.Figure 175: Command line parametersThe module eKERNEL r

Page 145

Figure 177: eSMS Main screenThe section on the left features outbound messaging and the section on the right featuresinbound messaging.Figure 178: Inb

Page 146

Hardware installationThe detailed installation procedures for the FP modules are in the installation documentslocated on the DECT Messenger DVD:D:\Doc

Page 147 - Chapter 18: Module - eFR

Figure 179: Configuration details in tab connectionsOutbound messagingThe eSMS module can send outbound SMS messages to mobile phones. It connects to

Page 148 - Overview of monitoring

Figure 181: Details under logging tabThe logging files provide more details on the data exchange.Figure 182: Logging filesWhen message delivery is suc

Page 149 - Overview of notification

Figure 183: Example of message delivery failureInbound messagingThe eSMS module also handles inbound SMS messages. These messages are received onthe G

Page 150 - Launch module eFR

Figure 184: Reception of an inbound SMS messageMore details on this data exchange are given under the logging tab, as shown in the followingfigure.Fig

Page 151 - Configure module eFR

Figure 186: Logging filesConfigurationThe eSMS module is configured through the eCONFIG module. The eSMS module requireseCONFIG 2.9.10 or above.The fo

Page 152 - Destinations planning

Figure 187: eCONFIG configuratorFigure 188: Sign on to DECT Messenger configuratorConfigurationDECT Messenger Installation and Commissioning — Book 1

Page 153 - Destinations configuration

Figure 189: eSMS area IBS 1Module - eSMS236 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 154 - Module - eFR

Figure 190: Module eSMS inbound definitionsFigure 191: Module eSMS - InboundConfigurationDECT Messenger Installation and Commissioning — Book 1 March

Page 155 - Destinations type NET

Figure 192: Module eSMS - Inbound ACLFigure 193: Module eSMS eKERNEL_DEVICE_FORMATModule - eSMS238 DECT Messenger Installation and Commissioning —

Page 156 - Destinations type SMTP

Figure 194: SMS Service logging tabWeb interfaceWhen eSMS is configured, the new Web Administrator interface features a window where youcan send an SM

Page 157 - Destinations type SNMP

Figure 6: DECT Messenger interaction with FP I/O modules Important:The OPC Server software can be controlled by only one application. This means that

Page 158 - Monitoring

Figure 195: Select destinationModule - eSMS240 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 159

Figure 196: Enter message informationWeb interfaceDECT Messenger Installation and Commissioning — Book 1 March 2012 241

Page 160 - Monitoring type DISK

Figure 197: Logging tabModule - eSMS242 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 161

IndexAAdd-on modules ...201Add—On module ...

Page 162

eKERNEL.exe ...119ELDAD ...

Page 163 - Monitoring type PING

PPING ...158PING section ...

Page 164

Chapter 6: Preparing the Operating SystemAs a general rule, ensure that the operating system of the target PC is up-to-date, with the latest servicep

Page 165

Figure 7: Windows Components Wizard window5. Select Details. The Internet Information Services (IIS) details window appears,listing the installed IIS

Page 166 - Definition of a TCP server

Figure 8: Internet Information Services (IIS) window8. Select World Wide Web Service and click Details; in the World Wide Web Servicedetails window th

Page 167

Figure 9: Server Manager window3. Click Add Role. The Add Roles Wizard opens. Click Next to skip the openingscreen.4. Check the Web Server (IIS) box i

Page 168 - Definition of a TCP client

3. Click Add Features. The Add Features Wizard window opens, as shown in thefollowing figure.Figure 10: Add Features Wizard window4. Check SMTP Servic

Page 169 - Sample e-mail

ContentsChapter 1: New in this release...7Features...

Page 170 - Figure 119: Sample e-mail

Preparing the Operating System30 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 171 - Chapter 19: Module - eGRID

Chapter 7: Installing third-party softwareThis chapter describes how to install the optional third-party software that is required to run certain DEC

Page 172 - Module - eGRID

Figure 11: Adobe Reader 9 Destination Folder window3. Verify the installation location and click Next.If you want to change the destination folder, cl

Page 173

Note:SQL Server 2000/MSDE2000 are not supported. When using an SQL Server installed on aPC different from the DECT Messenger PC, the uptime of DECT M

Page 174

Installing National Instruments Field Point and DataSocketThis section describes the installation of modules related to the eIO component of DECTMesse

Page 175

Figure 12: National Instruments Measurement & Automation Explorer screenFor details on how to configure the Field Point modules with Measurement &

Page 176

Installing third-party software36 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 177 - Important:

Chapter 8: Install DECT ManagerThis chapter describes how to install the DECT Messenger software. If you need to deploy one or moreDECT Messenger sof

Page 178

Figure 13: System Configuration Check window Note:If the Pending Restart Requirement check fails (for example, due to a conflict withother installed s

Page 179 - Chapter 20: Module - eIO

Figure 14: Install Prerequisites window4. The Setup Wizard checks if all necessary third-party software components arepresent and attempts to automati

Page 180 - Module - eIO

More extended program...69Rea

Page 181

9. Select Complete to install all available components in the default installation pathand click Next to continue.The Database Installation window app

Page 182 - Analogue input

13. When the installation completes, the InstallShield Wizard Completed screenappears. Click Finish to finalize the installation process.14. When prom

Page 183

7. Select Custom and click Next to continue.The Custom Setup window displays, allowing you to specify the components youwant to install and run on the

Page 184

Uninstalling DECT MessengerDECT Messenger can be uninstalled using one of the following procedures. The proceduresare applicable for both Server and C

Page 185

Install DECT Manager44 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 186

Chapter 9: Getting started with DECTMessengerThis chapter describes the actions required for getting a DECT Messenger Server up and running. Forfurth

Page 187 - Figure 135: eIO logging

3. In the License Manager menu, go to File > Load a New License String and browsefor the license key file received from Avaya. Click Open to load i

Page 188

– whenever possible – a standard configuration as a starting point when setting up a customersite.Standard configuration databaseStandard configuratio

Page 189

5. Browse for the main database directory.For example: C:\Program Files\Avaya\Avaya DECT Messenger\Database.Rename the existing MessengerConfig.mdb to

Page 190

Figure 20: Web Administrator Import Configuration screen7. A message appears stating the import was successful. Important:Standard configuration datab

Page 192 - License Manager

When eKERNEL starts, it displays a main window similar to the one shown in the followingfigure:Figure 21: The eKERNEL main windowThe list on the left

Page 193

3. When using eCONFIG from a client PC, you will be prompted for the location ofMessengerConfig.mdb database. Browse to the network share of the serve

Page 194 - License maintenance

The left pane shows a tree with the available configuration items, while the rightpane shows details on the currently selected configuration item.Work

Page 195 - External interfaces

The modules node lists all modules configured, grouped by module type. Setting up moduleparameters requires advanced technical knowledge; in most case

Page 196 - TCP Connections

4. On the middle-right, a description text explains the purpose of the selected item andhow it should be configured.5. On the bottom-right, the curren

Page 197 - Watchdog

Deleting a module1. Expand Site NEC node in the tree.2. Expand the Modules node.3. Under the Modules node, expand the node that represents the type of

Page 198 - Guarding

Figure 26: eCONFIG Area configuration window4. Select the Description item and type a new description.5. Click OK to save the changes.Configuring PBX

Page 199

Figure 27: eDMSAPI module details window4. Select and modify PBX type to indicate the type of device the module connects to(iS3000, Avaya or DAP Contr

Page 200 - Module - eKERNEL

Adding a device1. Expand the Site NEC node in the tree.2. Expand Groups and devices.3. Right-click All devices and select New Device.The device detail

Page 201 - Install module eLICENSE

Figure 29: Select Output Program window5. Select eDMSAPI by clicking the black arrow and click OK.6. Select and specify a Device ID (the extension num

Page 202 - Run module eLICENSE

Chapter 23: Module - eLOCATION...207Initialization...

Page 203

Figure 30: Select Facility window8. Select a handset model and click OK.9. Select and specify other properties if necessary (e.g. ‘Description’).10. C

Page 204 - Disaster recovery

Also, while eKERNEL and associated modules are down, no input and output is performed,and alarm input and distribution is suspended.Stopping active mo

Page 205

5. When the database is successfully published, a message appears stating that theregistry files necessary for eTM module are created, as shown in the

Page 206 - Module - eLICENSE

on the client PC corresponding to that specific environment, after stopping eTMand other associated processes.12. Start eTM to bring the environment o

Page 207 - Initialization

where the MessengerConfig.mdb resides on the DECT Messenger Server must be sharedover the network to enable remote machines to access the shared datab

Page 208 - Module - eLOCATION

Chapter 10: Module eAPIIntroductionThe module eAPI is not a real module, but rather a description of a public Application ProgramInterface (API) for

Page 209

configuration techniques (through registry, .INI files, database, command line parameters, andso on) to control the behavior of their applications.Bas

Page 210 - Program activity

- The parameter alarmdescr must start with <alarmdescr> and end with the </alarmdescr> tag- The parameter msg must start with <msg>

Page 211

6. Run the program. If you click the Command1 button, a message request is sent toeKERNEL.7. You can alter the code shown in Figure 36: Sample socket

Page 212 - Architecture

Figure 36: Sample socket client codeMore extended programRefer to Module - eAPI sample on page 71 for a detailed source code listing of a morecomplete

Page 213

Chapter 1: New in this releaseThe following sections detail what’s new in this document for Avaya Communication Server 1000 Release7.5:• Features on

Page 214 - Figure 158: Module eDMSAPI

Some typical features include:• Ability to specify certain runtime parameters of the program by means of the commandline parameters in the shortcut, s

Page 215

Chapter 11: Module - eAPI sampleeAPI_form - 1Option Explicit' --------------------------------------' This program requires a valid command

Page 216

log S, INF, Warning : parameter ' & keyword & ' not available in ' & xml & 'Elseparse_xml = lcl_valueEnd IfOn Erro

Page 217

End SubPrivate Sub lst_log_DblClick()' show detailsOn Error Resume Next: Err = 0txt_log.Text = lst_log.List(lst_log.ListIndex)On Error GoTo 0show

Page 218

' Terminate if undefined valuesIf g_site = N/A Thenlcl_rc = MsgBox(eAPI could not start. Parameter '/Site:xxx' missing in command strin

Page 219

g_ekernel_local_address = ip_ekernel.LocalIPlab_ekernel_local_address = & g_ekernel_local_addressg_ekernel_local_port = ip_ekernel.LocalPortlab_

Page 220

If lcl_ekernel_cur_state <> g_ekernel_prv_state Theng_ekernel_prv_state = lcl_ekernel_cur_stateSelect Case lcl_ekernel_cur_stateCase 0lab_ekerne

Page 221

--------------------------------------------------------------------------While lst_ekernel_jobq.ListCount > 0process_ekernel_jobq lst_ekernel_jobq

Page 222 - DNR instead of the device id

lcl_guarding = Timer - g_guardingIf lcl_guarding < 0 Then lcl_guarding = lcl_guarding + 86400If (lab_guarding <> Format$(lcl_guarding, 00000)

Page 223 - Chapter 24: Module - eSMS

Select Case Left$(g_log_path, 3)Case C:\g_log_path = D:\ + Mid$(g_log_path, 4)lab_log_path = & g_log_pathCase D:\g_log_path = C:\ + Mid$(g_log_p

Page 224 - SMS service

New in this release8 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 225 - Figure 169: INI file

Module - eAPI sample80 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 226 - Module - eSMS

Chapter 12: Module - eASYNCThe module eASYNC consists of one program eASYNC.exe, written in Visual Basic.OvervieweASYNC.exeThe eASYNC.exe is the Visu

Page 227

At startup, the eASYNC.exe sends an XML string to eKERNEL.exe requesting a configuration.This step is needed for each module that interacts with eKERN

Page 228

If the <cfgrpy> shown in Figure 39: eASYNC module receives this cfgrpy from the eKernel ifno license is available for eASYNC on page 83 is recei

Page 229 - Figure 177: eSMS Main screen

Figure 41: Sample eKERNEL message request and eASYNC feedbackDuring communications, eASYNC contacts the provider and handle the dialog that is require

Page 230 - Outbound messaging

LoggingLogging information is available both on-screen and in logging files.You can view on-screen logging through the Logging tab.Figure 43: eASYNC L

Page 231 - Figure 182: Logging files

Figure 45: Sample logging data for SMS to KPNModule - eASYNC86 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? infodev@

Page 232 - Inbound messaging

Figure 46: Sample logging data for PAGING to BELGACOMLoggingDECT Messenger Installation and Commissioning — Book 1 March 2012 87

Page 233 - Figure 185: Logging tab

Module - eASYNC88 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 234 - Configuration

Chapter 13: Module - eBACKUPYou can use the eBACKUP module to make a backup of a predefined list of files.The eBACKUP.exe must be started from a shor

Page 235

Chapter 2: IntroductionDECT Messenger is a client-server software platform for processing and converting messages betweenvarious protocols. It consis

Page 236 - Figure 189: eSMS area IBS 1

SiteFrom path From file To path To file3 C:\SOPHO Messenger@Net\ExeeAPI.exe C:\Temp\[weekday]\SOPH OMessenger@Net\ExeeAPI.exe3 C:\SOPHO Messenger@Net\

Page 237

Figure 48: Backup start windowClick Backup to begin the backup procedure.When all the files are successfully copied, the window becomes green.DECT Mes

Page 238

Figure 49: Backup successfulIf one or more files are not copied, the window becomes red.Module - eBACKUP92 DECT Messenger Installation and Commiss

Page 239 - Web interface

Figure 50: Backup error windowDuring backup, logging information is written to the hard disk, an example of which is shown in Figure 51:Sample backup

Page 240

Figure 51: Sample backup logModule - eBACKUP94 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 241

Avaya recommends that you close all the DECT Messenger applications before starting the backupprocedure. In release 2, the file copy procedure is impl

Page 242 - Figure 197: Logging tab

Module - eBACKUP96 DECT Messenger Installation and Commissioning — Book 1 March 2012Comments? [email protected]

Page 243

Chapter 14: Module - eCAPThe module eCAP consists of the program eCAP.exe, written in Visual Basic. In general, DECT Messengerprograms reside in the

Page 244

keyword Log drive refers to the drive where the logging data must be stored. Usually this is C:\SOPHO Messenger@Net\Log\.At startup, the eCAP.exe send

Page 245

Figure 55: eCAP Connection tabBecause the eCAP is designed to handle asynchronous serial communications with a numberof alarm systems, the eCAP requir

Comments to this Manuals

No comments