Home

Avaya CS1000 User's Manual

1. Manufacturer Model TELEVIC PROTOCOL CONVERTOR L 03 TYCO MINERVA 80 VSK DE LICHTERVELDE VSK OLV VAN VREDE VSK ST JOZEF WORMALD BASE WORMALD L 01 WORMALD G EIPM ARGINA The valid manufacturer is ARITECH and the valid model is BASE Argina BASE is based upon installation Maas en Kempen Campus Bree Table 6 Sample ARGINA protocol data BAL Z002 D003 00000 00000 00000 Inkomhal Argina alarms are always sent to group ARGINA since no pager information is available in the data stream Messages are sent with an alarm description based upon the first part before the comma The character is omitted This means BAL results in an alarm description BAL The message is based upon the sixth element for example Inkomhal omitting the leading and trailing spaces Alarms are sent with the option remove after sent ARITECH The valid manufacturer is ARITECH and the valid model is BASE and 1 Aritech BASE is based upon the installation Floreal Nieuwpoort DECT Messenger Installation and Commissioning Book 1 March 2012 101 Module eCAP 19980218 08 49 41 19980218 08 49 41 Fout 71 Gebeu 1258 Aktief 19980218 08 49 41 Poort SER1 Printer afgekoppeld 19980218 08 49 41 18 02 98 08 19 31 P 1 19980218 08 49 41 19980218 08 49 41 Actie 4 Gebeu 1259 Gelogd 19980218 08 49 41 Stop Zoemer 19980218 08 49 41 18 02 98 08
2. ceccceeeeeeeeeeeeeeeeeeeeeeaeeees 152 PROTOCOL CONVERTORGCL 0 ccccceceseseeeeeeeees 109 MOG T E A E AEE AE E E ETT 109 R Real world examples of using API ceee 70 Removing MOUIES 0 eee eee eeeeeeeeeeeeeeeeeeeeeteeeeeeeeenees 54 Revision history cccecceeceeeeeeeeeeeeeeteeeeeeeeeeeseeneeeaaees Zz RUCA Antwerpen installation s s s 116 Running module eLICENSE cceseeeeeeeeeeeeeeeeee 202 S Siemens TC35i module ccccccceeseeeeeeeeeeeasaeeeeees 223 SMS iea a E 156 SMS Service module ccccccceeeeeeeeeeeeeeeeeeeees 223 224 SMS_service exe ooo ccc ccc ce ccc ee cesses eesseeeeeeceeeeeeeeseeeeneaes 224 SMS_service ini 0 0 cece ce eccccccceceececaeeeeeeeeeeeeeeeeeeeeeeeees 224 IPS eee e a 156 SMTP destinations c cccceccccseeeeseeeeeeeeaeaeeeeeeeeeees 149 SMTP notification 2 0 0 0 cece cccccccceseeeeeceeeeeaeaeeeeeeeeeees 149 SNMP irinna an A E 157 SNMP destinations cccccccccececeeeeceeeeeeeeeeeseeeenenes 149 SNMPY I trapson a 149 Sockets client cccccceccceseeeececeeeececeeeeeeeeeeeeeeeeaeaaaees 67 DECT Messenger Installation and Commissioning Book 1 ST JOZEF rnia a a 112 Standard configuration database ccccccceeeeeees 47 Starting EKERNEL cccccccccecceeeeeeeeeeeeeeeeeteeeeeeess 49 Status of Master SlaVE ccccccecceceeesceeaeeeeseeeeeeeeeenes 124 STEAFA ainiai tis avtvddersasandetnans
3. Book 1 March 2012 Comments infodev avaya com Chapter 15 Module eESPA The module eESPA consists of one program The program is eESPA exe and is written in Visual Basic v6 0 In general the programs reside in the default directory C SOPHO Messenger Net Exe unless otherwise implemented in your environment Note In release 4 0 an additional implementation is available that you can activate by specifying manufacturer ESPA and model VSK In most cases the new VSK implementation is likely to be more compatible than the BASE system and therefore the preferred method to configure the eESPA module Manufacturer ESPA and model BASE For backwards compatibility to activate the original implementation of module eESPA by specifying manufacturer ESPA and model BASE Overview eESPA exe The eESPA exe is a Visual Basic component of the eESPA module The program communicates with two processes the eKERNEL exe and external paging equipment The eKERNEL exe is the central engine that centralizes all database access and communication with input and output capable modules The eESPA exe communicates with eKERNEL exe by means of TCP sockets In this communication eESPA exe is a TCP client software that connects to the eKERNEL component acting as TCP server software At start up eESPA exe contacts the eKERNEL exe by means of a socket connection eESPA exe requires at start up a few parameters so that eESPA can identify itsel
4. Book 1 March 2012 Comments infodev avaya com SMS service SMS _service exe and SMS _service ini are two resources related to SMS_ service functionality Configure SMS_ service through the INI file The default values suit most environments You can change the parameter COM Port if COM1 is not available Change the value according to your environment for example specify 3 if COMS is available In the sample file illustrated in Figure 168 Default configuration section on page 225 there is a single INI file There can be more than one instance of SMS_ service with multiple Siemens TC35i boxes In most cases only one Siemens TC35i is used and only a single instance of eSMS and SMS service is used When the service is started with the following shortcut the default configuration section is used C SOPHO Messenger Net Exe SMS_service exe Figure 168 Default configuration section The default configuration is configured in INI file with the statements shown in the next figure Default System Module 1 Figure 169 INI file The statement in Figure 169 INI file on page 225 indicates that in absence of a System xxxx in the shortcut the default system is used In the sample configuration in the following figure the configuration Module 1 is set as a default system This means only Module 1 is used Module 1 Manufacturer Model COM port COM settings Mode Log days Queue depth Local Remote
5. 148 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Overview of notification different information is found You are notified when the socket is no longer listening or established and you are notified when the socket returns listening or established Overview of notification The notification part covers the following items e The SMTP destinations refer to the notification based upon e mail by means of SMTP protocol SMTP destinations requires an e mail server infrastructure that is configured to support inbound SMTP connections originated from the eFR module Depending on the e mail infrastructure you may need to configure the e mail server to enable SMTP allow inbound SMTP connections from the IP address where eFR runs and allow relaying of e mail request to defined destinations You can configure the SMTP notification to send notification messages when changes occur in the state of monitoring items such as DISK NETSTAT PING start of error condition and resume of normal condition The SNMP destinations refer to notification based upon the SNMP protocol In SNMP destinations SNMPv1 traps can be sent based upon the UDP protocol stack Since UDP protocol is datagram oriented SNMPv1 traps can be sent even if the SNMP receiver infrastructure is not in place on the destination system When the SNMP receiver infrastructure is not in place on the destination system the trap is u
6. Log drive C Figure 53 Typical parameters in the shortcut In the example shown in Figure 53 Typical parameters in the shortcut on page 97 the eCAP exe identifies itself as belonging to site 1 and specifies the location of eKERNEL through IP address LOCAL and port 3102 The special value LOCAL refers to the assigned IP address of the first NIC adapter found in the PC You can determine the IP address using the IPCONFIG exe command or in the appropriate sections of the Windows network settings The DECT Messenger Installation and Commissioning Book 1 March 2012 97 Module eCAP keyword Log drive refers to the drive where the logging data must be stored Usually this is C SOPHO Messenger Net Log At startup the eCAP exe sends an XML string to eKERNEL exe requesting a configuration This step is needed for each module that interacts with eKERNEL exe because this approach allows central administration using a single database even if some client modules are located on a distributed machine lt xml gt lt cfgrqs gt lt appl gt eCAP lt appl gt lt site gt 1 lt site gt lt cfgrqs gt lt xml gt lt xml gt lt cfgrpy gt lt manufacturer gt ELDAD lt manufacturer gt lt model gt L 48 0 RC 1 SR 2 SS 3 SS 4 SR lt model gt lt bidir gt N lt bidir gt lt link_type gt RS232 lt link_type gt lt resource gt COM01 lt resource gt lt settings gt 9600 N 8 1 lt settings gt lt descr gt Eldad DP6000 lt d
7. The eFR module is an add on module and is licensed separately through the eLICENSE module Some of the modules listed in this attention box are available only on a site specific basis Architecture The eSMS module works with the SMS_ service module Together these modules provide the ability to send outbound SMS messages from DECT Messenger to mobile GSM phones Incoming SMS messages that originate from mobile GSM phones can also be processed to confirm alarms Siemens TC35i module The SMS_ service module currently only supports the Siemens TC35i module Verification of compatibility of other SMS boxes can be handled on a project by project basis Some other modules are compatible and other modules show intermediate problems of incompatibility issues In addition a Siemens TC35i module you need the following items e a serial cable to connect the TC35i with the PC included in TC35i a power unit and cable for the TC35i included in TC35i DECT Messenger Installation and Commissioning Book 1 March 2012 223 Module eSMS e an antenna for the TC35i included in TC35i e a SIM card of mobile provider of choice with a PIN and a PUK code Follow the steps in the next procedure to install the Siemens TC35i module Installing the Siemens TC35i module 1 Install the SIM card in a regular mobile phone 2 Power on the mobile phone 3 Refer to the SIM card information and obtain the valid PIN and PUK codes You usually need the p
8. 1ENQ I want to send something BS 2ENQ Destination address ES ES 1NAK Transmission error EOT ES 1ENQ ES 2ENQ LS DECT Messenger Installation and Commissioning Book 1 March 2012 133 Module eESPA sample MASTER address 1 SLAVE address 2 ES 1NAK EOT ES Slave has data to be transferred 2ENQ E ES 1ENQ I have data for address 1 ACK I am ready to receive data ES ES DATA Block1 ACK ES ES DATA Block2 1NAK Transmission error E BS DATA Block2 ACK BS ES EOT 2ENQ Polling ES ES EOT 2ENQ E ES EOT 134 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 Chapter 17 Module eDMSAPI The module eDMSAPI consists of two separate programs One program is eDMSAPI and is written in Visual Basic The other program is called CSTA_Service exe and is written in C In general both programs reside in the default directory C SOPHO Messenger Net Exe unless otherwise implemented in your environment Overview eDMSAPI exe The eDMSAPI is the Visual Basic component of the eDMSAPI module The program communicates with two processes the eKERNEL and the CSTA Service The eKERNEL is the central engine that centralizes all database access and communication with input and output capable modules The eDMSAPI communicates with both eKERNEL and CSTA_Service exe by means of TCP sockets In
9. 20010110 00 00 12 I 22 37 0777 08 5 336 C A 20010110 00 00 33 I 22 38 0777 08 5 336 C A 20010110 00 00 33 I 22 38 0781 10 6 416 C 20010110 02 02 17 I 00 39 0777 08 5 336 C A 20010110 02 02 18 I 00 39 0784 10 7 520 A 20010110 02 02 38 I 00 40 O777 08 5 336 C A 20010110 02 02 59 I 00 40 O777 08 5 336 C A Figure 62 Sample NIRA protocol data Alarms are always SET and repeat mechanisms are configured to indicate if an alarm is no longer active logical RESET is based upon no longer repeating For this reason Avaya recommends that the alarm repeat interval be specified for example to 30 seconds The room number is retrieved from the data stream and is used as a group for example 416 419 336 and so on The message is 4 bytes long and consists of the room number followed by either aC or an A indication Datastreams in the format XXX C and XXX A are considered as C and datastreams in the format XXX A and XXX AA and XXX AAA are considered A type alarms Message text is 416C or 520A The alarm description is NIRA_C for messages that end with C and NIRA_A for alarms that end with A All messages are removed after SENT Note This protocol typically requires project based consulting services and modifications 108 DECT Messenger Installation and Commissioning Book 1 March 2012 C
10. 3 C SOPHO Messenger Net eSMTP_ C Temp weekday SOPH O eSMTP_ Exe server exe Messenger Net Exe server exe 3 C SOPHO Messenger Net omnithread_rt dll_ C Temp weekday SOPH O omnithread_rt Exe Messenger Net Exe dil 3 C SOPHO Messenger Net Messenger_CFG C Temp weekday SOPH O Messenger_CF Mdb mdb Messenger Net Mdb G mdb 3 C SOPHO Messenger Net Messenger_Data C Temp weekday SOPH O Messenger_Da Mdb mdb Messenger Net Mdb ta mdb From_path and From_file specify the path and the name of the file that are copied to the To_path and To_file When eBACKUP is started a blank window with one button is shown for example Backup site 3 90 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 eu Figure 48 Backup start window 00000 16 01 44 Click Backup to begin the backup procedure When all the files are successfully copied the window becomes green DECT Messenger Installation and Commissioning Book 1 March 2012 91 Module eBACKUP Backup sites ru Toone TBI Figure 49 Backup successful If one or more files are not copied the window becomes red 92 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com IL Backup ste 3 ru CNEA Figure 50 Backup error window During backup logging information is written to the hard di
11. 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 3 06 06 06 06 06 10 10 10 11 11 it 12 12 12 13 13 13 15 15 15 1 1 1 1 1 1 18 18 18 18 18 18 19 19 19 19 19 19 20 20 20 20 20 20 23 23 23 23 24 24 24 24 26 26 HHOHHHOHHHOHH HHH OHHHHH OHHH AAA OHA Aa OWA AH OHH OHH OHH OHH aa INF COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM Manufacturer ESPA and model VSK COMO01 opened with settings 9600 N 8 1 1 ENQ 2 ENQ ACK 2 ENQ EOT 2 ENQ EOT 2 ENQ EOT 1 ENQ EOT 2 ENQ EOT 1 ENQ EOT 2 ENQ EOT 1 ENQ EOT 2 ENQ EOT 1 ENQ EOT 2 ENQ EOT 1 ENQ EOT 2 ENQ EOT EOT 2 ENQ EOT EOT 2 ENQ EOT 1 ENQ Figure 81 Logging using model VSK DECT Messenger Installation and Commissioning Book 1 March 2012 129
12. DIAGNOSTIC NOTICE 001 Dump information available 68 22 12 2 d 2007 03 30 5 15 44 3 O68 OBTAINABLE NOTICE Database update locked due to an operational restart during updating 61 22 12 2 100 2007 04 03 2 16 04 46 4 2 061 INFORMATORY EVENT 046 Announcement message not available EXECUTED gt DISILA 01 Message 31 No relations or data found EXECUTED gt DIBLCK 01 Message 31 No relations or data found EXECUTED Figure 119 Sample e mail 170 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 Chapter 19 Module eGRID The eGRID application gives you a view of the different tables in the databases You can start the eGRID exe application without command line parameters At startup the window in Figure 120 eGRID startup window on page 171 is shown GB cGRID SOPHO Messenger Net v2 8 0 heno He Elease ea diea Subset Clear Fiter Generate registry files for eTM ee e eet 100452500001 AT amp O05063 Ooosi6sa141414 AT 00475161622 ATECOSO 3 OAR 4d gt ot oD BIR A Ss Boa Table eASYNC nafs ers gt ezexinese Gill amp GRRE iise Messenger_crG Table eASYNC pond EAE Figure 120 eGRID startup window Seven drop down lists are available at the top of the window From left to right the functions of these drop down lists are as follows e Use the first drop down list on the far l
13. Module eESPA 130 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 26 2 2 2 28 28 28 28 28 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 31 31 31 31 31 31 31 31 31 31 31 31 HHH HAHAHAHAHAHA HAHAHA AA AAA AAA AAA AAA A Aa AA AA AAA A Aa OAR OR a COM CO
14. Note On Windows Server 2008 you might get a Files in Use warning window If this papper select Automatically close and attempt to restart applications and clic Note The default installation path is C Program Files Avaya Avaya DECT Messenger on 32 bit platforms and C Program Files x86 Avaya Avaya DECT Messenger on 64 bit platforms Choose whether to use a Microsoft Access only database or to use an existing Microsoft SQL Server If using Microsoft SQL Server also enter the location of the database server and the credentials required to connect to it Click Next to validate the database connection and continue The Ready to Install window appears Click Install to begin the installation process 40 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Install a DECT Messenger Client 13 When the installation completes the InstallShield Wizard Completed screen 14 appears Click Finish to finalize the installation process When prompted to restart the computer click Yes Install a DECT Messenger Client Depending on customer needs there might be situations when it is necessary to spread certain DECT Messenger components on several computers in the same network The Client mode installation is actually part of the same installation package and with a few exceptions follows the same steps described for the Server mode setup Before you continue ensure that t
15. Other transport mechanisms can require you to perform actions in the destination site for example for NET SEND the messenger service needs to be activated in the target PC 3 Gather a list of destination users or destination peripherals with specific information to uniquely address the destination device For example for e mail users you need the e mail address of the target user and for SMS message you need the extension number of the mobile GSM phone Destinations configuration Follow the steps in the next procedure to configure destinations Configuring destinations 1 Define the destinations in the Destinations section of the eFR xml file The destinations section starts with the tag lt Destinations gt and ends with the closing tag lt Destinations gt The following figure shows sample destinations DECT Messenger Installation and Commissioning Book 1 March 2012 153 Module eFR C Program Files Messenger Net Exe eFR xl Microsoft Internet Explorer Jeg File Edit yiew Favorites Tools Help ar Der E gt BOD Preah krs O B B Address C Program Files Messenger Net Exe eFR xml x gt Go Links lt xml version 1 0 encoding utf 8 gt lt eFR gt lt Monitoring interval 600 gt lt Destinations gt lt Destination id eNET type NET description Francis Missiaen from Messenger Net to BENB121027 gt lt Destination id eSMTP type SMTP description Francis Missiaen
16. Serice EX Erranen ainn 139 D Data TOW ssc ssid innasta a g i 123 D Ata ASCs sererken a ERENT 196 DE LICHTERVELDE 0 cccceececeeeeeeeeeeeeeeeeeeseeeeees 112 Destinations Configuration cceeeeeeeeeeeeteeeeeeees 153 DECT Messenger Installation and Commissioning Book 1 Destinations planning 20 ee eeeeeeeetteeeeeeeeeeeeentaaeees aby Destinations type NET eee eeeceeeeeeeeeeeeteeeeeeeeenaaees 155 Destinations type SMS ccceeeeeeeeeeeeeeeeeeeeeetes 156 Destinations type SMTP eessen 156 Destinations type SNMP ececeeeeeeeeeeeeeeeeeteeeee 157 DIANA tand 2ra a a a a 104 Digital IMPUt raires irene 184 Digital OUTPUT rnana a E AE 185 Disaster recovery cceceeeeeeeeeeeneeceeeeeeeeeeeeeeeeeeenees 204 Discrete IMPUt sesarrencciraiordniroriniai 184 Discrete OUtPUE ccceceeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeeeees 185 DISK oa n sven amenstautiesdaeevouindieesen 158 DISK section cccccccccecceceseeeeseeeeeeececeeeeceeeeesaeaeaenesees 148 Distributed environment ccccseeceeeeeceeceseeeeeeeeeenes 63 E e mail sample erarnan a 169 SAP EA OE A A EA E 65 194 eAPI basic architecture ccccccseseecceeeeseeeseeeeeeeaees 66 eAPI interface to eKERNEL cccccccseseeeeeeeeeeeees 70 GAP I limMItatiONS mieit 65 eAPI real world examples ccccccsseeceesssstteeeeeeeeaes 70 SAPI sample irisscan arenan aiia 71 BASING iia cgcsetis aa cdc cn asan
17. e Clear key icon license bound License manager e Crossed through key icon license unbound License manager 192 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 Equipment and Functionality models Equipment and Functionality models The licensing system distinguishes between equipment models and functionality models e The following models are assigned as equipment eCAP eESPA elO eLOCATION eSMS and eSNMP e The following models are assigned as functionality eWATCHDOG eBACKUP eCONFIG eDMSAPI eASYNC eCSTA eWEB eSMTP eSMTP_ server eAPI and eVBVoice Akey difference between equipment and functionality models is the count of available licenses as illustrated in Table 15 License examples on page 193 Equipment models have only a specified number of available licenses while functionality models have an unlimited number of available licenses Table 15 License examples Module total licenses used free ECAP equipment 3 2 1 EESPA equipment 2 2 0 ECSTA functionality unlimited N A N A DMSAPI functionality unlimited N A N A Whenever a client connects to the eKERNEL through a configuration request the eKERNEL determines whether the client is an equipment or functionality model e Equipment model If the client is defined as equipment the eKERNEL tries to bind this equipment to the license Success depends on t
18. lab_ekernel_local_port amp g_ekernel_local_port lab_ekernel_local_address amp g_ekernel_local_address End Sub Private Sub process_ekernel Diiw lel AS Strie Dim lcl_version As String Handle sockets status continuously attempt to stay connected Dim lcl_ekernel_cur_state As Integer lcl_ekernel_cur_state ip_ekernel Stat DECT Messenger Installation and Commissioning Book 1 March 2012 75 Module eAPI sample If lcl_ekernel_cur_state lt gt g_ekernel_prv_state Then g_ekernel_prv_state lcl_ekernel_cur_state Select Case lcl_ekernel_cur_state Case 0 lab_ekernel_msg Closed lab_ekernel_state BackColor RGB 0 0 0 Case 1 lab_ekernel_msg Open lab_ekernel_state BackColor RGB 200 130 0 Case 2 lab_ekernel_msg Listening lab_ekernel_state BackColor RGB 255 255 0 Case 3 lab_ekernel_msg Connection pending lab_ekernel_state BackColor RGB 200 130 0O Case 4 lab_ekernel_msg Resolving host lab_ekernel_state BackColor RGB 200 130 0 Case 5 lab_ekernel_msg Host resolved lab_ekernel_state BackColor RGB 200 130 0 Case 6 lab_ekernel_msg Connecting lab_ekernel_state BackColor RGB 200 130 0 Case 7 lab_ekernel_msg Connected lab_ekernel_state BackColor RGB 0 200 0 Case 8 lab_ekernel_msg Closing lab_ekernel_state BackColor RGB 200 130 0 Case 9 lab_ekernel_msg Error lab_ekernel_state BackColor RGB 1
19. 44 44 44 44 44 44 44 44 44 44 44 44 44 46 46 44 45 45 46 54 54 55 57 57 58 58 59 59 00 00 48 49 49 00 01 01 02 02 03 03 04 23 24 24 25 37 38 38 39 14 14 continued on next 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 11 11 11 11 14 11 11 11 11 46 46 46 46 46 46 46 46 46 15 15 29 29 30 34 34 7 35 D KAMER 1 ZONE 00 Z 000 D 0001 26 01 98 04 13 BRAND S VERWIJDER CFG STRAP 9146 26 01 98 04 12 SYS FOUT D KAMER 56 Z 001 D 0056 26 01 98 04 12 ISOLATIE D KAMER 1 ZONE 00 Z 000 D 0001 26 01 98 04 13 BRAND S VERWIJDER CFG STRAP 9146 26 01 98 04 12 SYS FOUT D KAMER 56 Z 001 D 0056 26 01 98 04 12 ISOLATIE D KAMER 1 ZONE 00 Z 000 D 0001 26 01 98 04 13 BRAND S NETONDERBREKING 9048 L1 0 26 01 98 04 13 SYS FOUT D KAMER 49 Z 001 D 0049 26 01 98 04 14 DET FOUT S VERWIJDER CFG STRAP page 9146 26 01 98 04 17 SYS FOUT S VERWIJDER CFG STRAP 9146 26 01 98 04 12 SYS FOUT D KAMER 56 Z 001 D 0056 26 01 98 04 12 ISOLATIE Figure 68 Sample ST JOZEF protocol data VSK Fire alarms are sent to group VSK_F fire alarm with alarm description VSK_F system errors are sent to group VSK_S system errors with alarm description VSK_S detector errors are sent to group VSK_D detector errors with alarm description VSK_D
20. C2000 CONFIG aot wre 2 ewe 16583 Figure 141 eKERNEL interface DECT Messenger Installation and Commissioning Book 1 March 2012 191 Module eKERNEL License Manager The Avaya DECT Messenger package is secured by a licensing system to prevent unlicensed usage of certain modules and clients G 3 Licence Manager File View Heb licensed Acpications Compters Hosting Apelication Free Instence Licences T Module Host Name IP Addiecs Dafi BENB 121027 192 168 1 12 f Licences Expire never Equpmert Ucencex Functionality Leerces Equipment Modal Used Fiee Msg et cGucrdan Meg Met Ful 0 1 Mag e ewastchdog Maget cLAP 3 2 Msg N et eBackup Msg et cESPAAH 1 4 Msg N eConlig Msg Net el 0 l 4 Msg N eDMSAF Msalet eLocD 1 4 Msg h e eS pre Magi et eSHS 1 4 Msg N amp ef STA Magi et eSNMP 1 4 Msg N amp eweb PPRA R A Ready Figure 142 License Manager At startup the eKERNEL searches for a valid license If there is no valid license because for instance the license expired or licensing system is not installed the eKERNEL program aborts To determine if the installed licensing system is valid use the Avaya License Manager If this component is not yet installed refer to Install PC Step 1e License Manager If a valid application is bound all Tabs of the eKERNEL program show a crossed through key icon while the eKERNEL Tab shows a clear key icon
21. When installing a new license with new available functionality eGuardian or eWatchdog the eKERNEL must be told about the new license To tell eKERNEL about a new license use the 194 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com External interfaces menu command eKERNEL gt License gt functionality as shown in Figure 144 Adding license functionality on page 195 Note eKERNEL makes this same check automatically at midnight Note that rechecking all licensing can take a little time KERNEL SOPHO Messenger Net 2 8 0 File eKernel Service Reset all alarms Sit te site LOG Path C SOPHO Messenger r Refresh Logfile Functionality eGUARDIAN Recheck license For all clients open port eWATCHDOG Figure 144 Adding license functionality If a license is installed with fewer equipment licenses than there are clients that need them the clients that are no longer licensed continue to function until the license is rechecked When the license is rechecked unlicensed clients receive a status message lt pgmsts gt NO LICENCE AVAILABLE lt pgmsts gt and their TCP IP port is closed This same principle applies to functionality models such eWEB and eAPI External interfaces There are a number of external interfaces that you can attach to the eKERNEL These interfaces can act as input source output source or play both roles An
22. amp amp lcl_file For Append As 1 write log record Print 1 Format Now dd mm yyyy hh mm ss amp amp log_type amp amp log_sts amp amp log_dta close log file Close 1 disabl rror recovery On Error GoTo 0 End Sub DECT Messenger Installation and Commissioning Book 1 March 2012 79 Module eAPI sample 80 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 12 Module eASYNC The module eASYNC consists of one program eASYNC exe written in Visual Basic Overview eASYNC exe The eASYNC exe is the Visual Basic component of the eASYNC module The program communicates with two processes the eKERNEL exe and the asynchronous modem attached to a COM port The eKERNEL exe is the central engine that centralizes all database access and communication with input and output capable modules The eASYNC exe communicates with eKERNEL exe by means of TCP sockets In this communication eASYNC exe is a TCP client software that connects to the other component acting as TCP server software At startup eASYNC exe contacts the eKERNEL exe by means of a socket connection Startup parameters are required to identify eASYNC exe and locate the eKERNEL exe program These parameters are set in the Properties section of the shortcut that initiates eASYNC exe This shortcut is usually located in the Windows Startup group click Start and choos
23. eKERNEL 200 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 22 Module eLICENSE Important Due to the ongoing development of the DECT Messenger product suite some modules that provide additional functionality may become available after the initial release of DECT Messenger 4 0 The following modules are described in this document but are not available at initial General Availability e eFR e eLICENSE eLOCATION eSMS e eSNMP e eVBVOICE The eFR module is an add on module and is licensed separately through the eLICENSE module Some of the modules listed in this attention box are available only on a site specific basis In DECT Messenger release 4 0 portions are packaged and distributed as add on modules including eLICENSE License mechanism The license mechanism used is the major difference between regular modules and add on modules Regular modules are licensed through the License Manager and protected by a hardware dongle and license string Add on modules use a different license mechanism Ordering Add on modules are currently not supported Contact Avaya for further information Install module eLICENSE The module eLICENSE provides a windows application used in to retrieve the fingerprint of the system The eLICENSE software must be installed at the destination system where the DECT Messenger Installation and Commissioning Book 1 March 2012 201
24. i a fal DAP Ethernet Network i 100Mb s Soo DAP 4 mil IP Phone PC with Web browser used for configuration mp DECT Messenger DAP Figure 2 Integration with Call Server 1000 IP DECT Manager TCP IP port for DECT Messenger On the IP DECT Manager system there is a TCP IP port open for LRMS E2 messages sent to and from handsets The port number is not fixed but determined in a configuration file dapcfg txt located on the DAP Controller PC The path to the dapcfg txt file depends on the version of the IP DECT Manager system as shown in this example C Documents and Settings All Users Application Data Avaya DAP Controller lt version system name gt dapcfg txt Open the file with an ASCII editor of your choice such as Notepad Important Do not make any changes to the file The following is an example of the dapcfg file contents Gapcfg txt for system My System Created by DapConf exe on 09 07 2010 16 20 56 i i i Please do not modify this file DAP IMAGEFILE Start of DAP image file section 4910b510 dwl DS Start of DS address section 192 168 17 74 28000 28017 DAP Start of DAP address section 239 192 49 49 3000 22635 1 18 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com National Instruments Analog Digital Hardware DAPPRF Start of DAPPRF address section 192 168 17 74 CDA Start of CDA address sectio
25. ult sec lt section is ce Af module CON port and HTTP ports a ha sane com por Supported values for manufacturer and model are shown below SEEMENS T0355 NOKIA 30 STCMENS T351 vaip Butte mere NO 29080 M Msg Nessanger Nsgitiet Massangerenet STEMENS 1c354 aa nd gt t Of HTTP port usad ta idantify s a retrieved fron should be unique xML part Figure 172 Default configuration At startup initialization takes place The SMS_ service contacts the Siemens TC35i module and initializes the system A message window appears that states Initialization completed normally The SMS_ service is then operational for sending outbound messages received from eSMS 226 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com eSMS module FF SMS Service SOPHO Messenger Met v3 1 3 i Service Help Requests Logging 00000 Port 1 opened with settings 9 00 n 8 1 D00000 Svent comEvDSR received DSR 1s True 00000 4Te 013 00000 0131 01010K 0131 010 00000 4TEO 913 00000 ATEO O131 013 OL010K 0131 1010 00000 AT4CSN 013 O0000 EMET number is 350467851405880 00000 019 010 350467891405890 013 1012 010 0H 1013 010 00000 ATI 10131 00 013 010 Sansung SGH 8300 019 013 010 0K 019 010 00000 AT CPAS 1013 00000 013 010 4CPAS O 012 013 010 OR 0
26. you can write external applications in your language of choice Visual Basic C Java and so on These applications can collect alarm information from external systems for example by means of asynchronous communications or a network connection It is important however to realize that the scope of the eAPI interface to eKERNEL is limited and there is for instance no ability to give feedback to eAPI and the alarm system upon successful or failed message delivery within DECT Messenger Avaya recommends investigating alternatives such as reusing an existing module of DECT Messenger for example eCAP generic or contacting Avaya to request the development of a new integrated module There is a road map procedure within the Avaya group that keeps track of all new requirements 70 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 11 Module eAPI sample eAPI_form 1 Goricom Bolier This program requires a valid commands Sees eKernel address LOCAL or value E eKernel port 2001 1 fio Civet Private Function parse_cmd_line keyword As String As String This routine isolates the value of a keyword from the commands Dame keeno MA SEs Seren Dim lcl_str As Integer Dim lcl_end As Integer On Error Resume Next Err 0 lcl_cmd g_command lel sti InStr 1 UCase lcl_cmd UCase keyword amp 3 Pe dhl chess 0 Iaxeua parse_
27. 01 MP SYSTEM RESET Remote Panel Zone 12 16 38 22 Nov 05 Remote Panel Point Panl 03 MP ISOLATE STATUS ON System Zone 12 16 40 22 Nov 05 Non Addressable Pnt Zn 0100 PALM BEAMS ISOLATED 12 16 40 22 Nov 05 Non Addressable Pnt Panl 01 MP R02 PRINTER OFFLINE System Zone 12 16 44 22 Nov 05 Non Addressable Pnt Zn 0400 LB00 R04 FIRE EVACUATE GROUND FLOOR 12 13 14 22 Nov 05 BGU FRONT HALL EAST Zn 0110 F 63 Figure 65 Sample MINERVA 80 protocol data An alarm is sent to the group MINERVA and the alarm description FIRE_EVACUATE as well as a remove after SENT and message BGU FRONT HALL EAST The group is always MINERVA and the alarm description comes from the first line when _ symbol appears The message is retrieved from the second line for example BGU FRONT HALL EAST VSK Valid manufacturer is VSK 112 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Valid models are e DE LICHTERVELDE e OLV VAN VREDE e ST JOZEF VSK is based upon the three installations defined in the model with a different implementation for each as illustrated in Figure 66 Sample DE LICHTERVELDE protocol data on page 113 Figure 67 Sample OLV VAN VREDE protocol data on page 114 and Figure 68 Sample ST VSK JOZEF protocol data on page 115 19990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 1
28. 126 Model 3400 sssssssssssserirrereserrrrrssssrsnrrneesenrnrnresenenenne 105 ESPRESSO ooccccccccccccccecccecccceccececcecececccesececeeseceee C107 Model ASCOM sete teshedesneniasatentsconeadecmutte tote cheas 126 EWER e uitansce teach pata eh ant 184 Model BASE cccccccsctenssuessssernesesnineecdsnscsrnennanetees 119 External COVICSS sinwsccntaiacnwnnsiarndlesavaiiivintvswss sudan 47 Model VIGILIN EN54 cece ctscseecacensstisersssassneranssaees 107 External interfaces ccccccccccccccceccccccccccccccececccceseeccceeeees 495 Model VSK Genrererrrererer eer rare eee er eer ree 126 Module CAPI inrano R aE 65 F Module eAPI Sample cececceeeeeeeceeeeeeeeeeeesetaaeees 71 Module SASYNG serron annn eii 81 Functionality models ccccsssececeeeesesseeeeeeeeeennaees 193 Modules OVErVIEW ccccccceececcesseceeceeeeeaeseeeeseneeeeas 9 MONIOMING arnesses annei 147 148 158 G Monitoring type DISK ccccccccccesssssscececseseeseeececsesees 160 Monitoring type NETSTAT n se 166 GOMGNIC E E E E E 118 Monitoring type PING c csccscsesscscesesseseeseseeetseeeeseees 163 GENT Aerei ae n a a 105 Getting started DECT Messenger 00 0eeeeeee 45 Guarding configuration ccccceeecseeeeetsteeeeeenaees 198 N H National Instruments Analog Digital Hardware 19 LS ge et a oP PT 155 hardware installation sssceseeeeeeeeeenenes 23 NETSTAT ocisicscsatdasicedesonieutdnaccaessegucarca
29. 16 21 21 22 21 47 47 47 47 47 47 47 47 32 32 32 32 40 53 53 53 53 aw DDD D S GENERAL RESET 9130 17 11 98 00 11 SYS FOUT D BEZOEKZAAL 303 Z 003 D 0193 R 17 11 98 00 11 DET FOUT 03 R 03 R 03 R 03 R 41 R 41 R 41 R 41 R 14 R 14 R 14 R 14 R 51 R 51 R 51 R 51 Ri 10 R 10 R 10 R 10 R D BEZOEKZAAL 303 Z 003 D 0193 17 11 98 00 13 DET FOUT BUZZER RESET 9131 17 11 98 00 18 SYS FOUT S NACHTBEL POORT 9176 GP01 17 11 98 05 44 SYS FOUT S BUZZER RESET S 9131 17 11 98 05 44 SYS FOUT S NACHTBEL POORT 9176 GPO1 17 11 98 06 29 SYS FOUT Figure 67 Sample OLV VAN VREDE protocol data 114 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 19980318 11 11 11 11 11 11 ans a le n e N Li 11 11 11 11 n i DE 1i 11 11 Li 11 14 11 11 ii 11 11 11 11 11 11 i e C ad id 41 44 11 ii 11 30 30 30 30 30 40 40 40 40 40 40 40 40 40 41 41 42 42 42 44 44
30. 19 35 P 1 19980218 08 49 42 19980218 08 49 42 Fout 2 Gebeu 1260 Gelogd 19980218 08 49 42 Deur contact 19980218 08 49 43 18 02 98 08 19 47 P 1 19980218 08 49 43 19980218 08 49 43 Actie 35 Gebeu 1261 Gelogd 19980218 08 49 43 Stop Zoemer 19980218 08 49 43 18 02 98 08 19 48 P 1 19980218 08 49 43 19980218 08 49 43 Actie 76 Gebeu 1262 Gelogd 19980218 08 49 43 Deurcontact gesloten 19980218 08 49 43 18 02 98 08 21 09 P 1 19980218 08 49 43 19980218 08 49 43 Fout 2 Gebeu 1263 Gelogd 19980218 08 49 43 Deur contact 19980218 08 49 43 18 02 98 08 21 11 P 1 19980218 08 49 43 19980218 08 49 43 Actie 37 Gebeu 1264 Gelogd 19980218 08 49 43 HERSTEL 19980218 08 49 43 18 02 98 08 22 35 P 1 19980218 14 28 29 19980218 14 28 29 Alarm od Gebeu 1509 Aktief 19980218 14 28 30 Zone 2 Gebied 0 19980218 14 28 30 Adres 3 4 Brand 19980218 14 28 30 DKKV 18 02 98 14 24 05 P 1 19980218 14 28 30 C TELEFOONCENTRALE 19980218 14 28 46 19980218 14 28 46 Actie 3 Gebeu 1510 Gelogd 19980218 14 28 46 Stop Zoemer 19980218 14 28 46 18 02 98 14 24 23 P 1 Figure 56 Sample Aritech protocol data Aritech alarms are always sent to group ARITECH because no pager information is
31. 23 Chapter 6 Preparing the Operating SyStem cccccccccesssseeseeeeeeeeeeeeeeeeeeeeeeseeseeeeeeeeneeees 25 iae cana OUTS ssc anspor aa grace pans A A dented helene a eben a 25 Chapter 7 Installing third party SOftWALE ccccssseeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeseneeeeeeeeeeeseeeeees 31 MRE LAU MIO OR ACOG FRONT pssst pedtissea wp vanessa tals aes pearance a Sicee oaeduncneetinnaceuesnpestene i msuceeebaniaay 31 Mamo SaL SAV sae kk sca rah Sted ae E E EGA 32 Installing National Instruments Field Point and DataSocket cccceeeecceeeeeeeeeeeeeeeeeeeeeeeeeeeseaeeeeeeaaeeess 34 Chapter 8 Install DECT PIAA Ol viissssssissinsasansssnsinasdinsnioncassasaciviadansiuaninsdiasassansdnisteaniionianns 37 PAROS you Slaine a ah eae Ce ee ee ta atest 37 etting Ted Yaseen carta ata tana cuttinte Ataasattan aaa 37 Install as DECT MSS Stier GEN saranoina EAEE aS 41 MUS ARN SCS VRE ais since anuinsascsansaseseccsatansds sxduaaawinnGia sna aiey daciuetsinn cidduasiins gunninsikepasaniiaseesacanauns 43 Chapter 9 Getting started with DECT Messenget cccccssssssseeeeeeeeeeeeeeeeeeeeeeeeeees 45 Coada EO sete pesera scree peexanqaien Ganniasaundtanesiaauae stone inasentmtaduak th wmtazgulewneaapie ee brataaa panes 45 CITI DECI Vela ati sits cassisesccs aes sic ssottaiiade seed E uiacdonsdaapinddanedaabtadeamecepdeamesaniaiaes 46 Standard GOni QURAN databas Esasi areata sata iis A 47 Sar GH at ELL secs uasjustenen ppp vantactientasceceeneaiaa
32. 2XXXXXX 3XXXXXX SXXXXXX QIXXXXXX COM Correction with backspace delete or COM Terminate each input with RETURN KEY COM Disconnect with ctrl D COM IMPORTANT INFORMATION 98 COM NEW Email Notification for paging COM Interested Send a mail to Email pag HAHHHHHHHAHHHHHHHHOHMH HHO 9 S H 19 03 2001 15 56 42 I COM Catalog Mobiles Solutions Pagers 99 19 03 2001 15 56 42 I COM _ 19 03 2001 15 56 42 I COM Type the 7 digits of the 19 03 2001 15 56 42 I COM wanted pager number 01 19 03 2001 15 56 43 0 COM 9789074 19 03 2001 15 56 44 I COM 19 03 2001 15 56 44 I COM 9789074 19 03 2001 15 56 44 I COM 19 03 2001 15 56 44 I COM Type your alpha numeric message 30 19 03 2001 15 56 45 0 COM Test paging to Belgacom with SOPHO Messen ger Net continued on next page 19 03 2001 15 56 46 I COM 02 Ties a6 oe eibis 055 6 210 ones amp we ele We es eee ee Se S E pie wae Sis sues a a Rs 19 03 2001 15 56 46 I COM _ A_ ATest paging to Belgacom with SOPHO Mes senger Net 19 03 2001 15 56 47 I COM 19 03 2001 15 56 47 I COM CALL ACCEPTED 80 19 03 2001 15 56 48 S INF Port closed 19 03 2001 15 56 48 O TCP lt xml gt lt msgrpy gt lt id gt 00001 lt id gt lt sts gt ACK lt sts gt lt msgrpy gt lt xml gt Figure 46 Sample logging data for PAGING to BELGACOM DECT Messenger Installation and Commissioning Book 1 March 2012 87 Module eASYNC
33. 47 12 0300 Cenfiauration 07 eDMSEPI eESPA eWEB iS3000 Tue 29 Mar 2011 09 47 06 0300 PHP info 00 COMSEPI eCSPA eWEB IP DECT Tue 29 Mer 2031 09 47 14 0300 B Import Security 08 eDMSAPL eESPA eWEB eSNMP IP DECT Tue 29 Mar 2011 09 47 12 0300 O Chenge pessword Giro a 11 Messenger Xpress BE Tue 29 Mar 2011 09 47 10 0300 E rogout 12 Massenger Xpress BE add on Tue 29 Mar 2021 09 47 12 0300 99 Al modules on iS3000 Tue 29 Mer 2011 09 47 16 0309 retreshl Fo 7 Trusted stes Protected Mode Off Fas Rios 7 Figure 20 Web Administrator Import Configuration screen 7 Amessage appears stating the import was successful Important Standard configuration databases are not changed during the installation to match the environment As a result the file path and IP address of the DECT Messenger server PC are set to the default values by the installer Be sure to use eGRID module to verify the values in the following tables and adjust them if necessary eKERNEL Site columns CFG_Connectionstring_CFG_str CFG_Connectionstring_ DATA_str CFG_Log_path_str CFG_eLOG_Path_str eDMSAPI columns eDMSAPI_API_address_ str eDMSAPI_External_address_str e eCSTA column eCSTA_API_address_str Starting eKERNEL To start eKERNEL click the associated shortcut Start gt Programs gt Avaya DECT Messenger gt eKERNEL You can also use and adjust the shortcuts located at the C SOPHO Messenger Net Lnk directory
34. 80 FalconNet fire detection system on page 128 06 06 2007 18 38 01 I COM 1 06 06 2007 18 38 01 1 COM ENQ 06 06 2007 18 38 01 I COM EOT 06 06 2007 18 38 03 I COM 2 06 06 2007 18 38 03 I COM ENQ 06 06 2007 18 38 03 0 COM EOT Figure 80 FalconNet fire detection system To improve problem determination a more detailed and human readable logging is enabled when the model VSK is used 128 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 0670672007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 06 06 2007 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 T83 18 18 18 TB 18 18 18 18 37 38 38
35. Activate senpt an End soript Reporting aterm E O scripts confiauration ka B besic E Gdavvanoed homa poup ratresh podn Figure 195 Select destination 240 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com fle Ed Mew Go Gokmerts Iocs teb S op g amp A DD http stems messengerss eptop mesiaen com 23860 ME Diab al Cocker Csr Farmer Imes Lfematerr C Hecelanousr YA Oxtner C3 Resizer G Teck T vw Sourcer i Optioner Web interface Send a Message Please enter message information Identifier Facility Description Comments 32473897171 SMS Francis Missiaen Default commerts Desens a Message SEQ DECT handset O arat This is s anple EHE mobile phone nessagel Area i Email EHO windows 0 Aree 1 amp Cawiri phone i D Areal EYsntt trap HO Group Message LS user message work with Scripts f Activate script H D End soript Dreepartng P BDaterms O scripts configuration P basic EE Advanced Message Figure 196 Enter message information DECT Messenger Installation and Commissioning Book 1 March 2012 241 Module eSMS E ed Peed 2008 by NEC Phiips Unified Solutions Woensdag 20 december 2006 11 95 90 Figure 197 Logging tab 242 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Index A Add on MOUIES ccccesceecesseceecee
36. Contact 00 Value 00 000000 00139 22 46 38 Figure 134 Digital Output module information Note When the value of a contact changes from Off to On or from On to Off the Before and After fields are updated with the status of the contact before the change occurred and the status of the contact after the change occurred The Change field is also updated with the new value Note You can also change the status of the contacts to On or Off by using the mouse to drag the switch to the On or Off position This must be carried out only while installing or testing In most environments the eKERNEL application is responsible to activate or deactivate the alarm condition of the discrete outputs You can however manually reset a status of a contact for example if manual intervention is required Logging The elO module provides logging facilities both on screen and on log files on disk The on screen logs are visible through the Logging tab as shown in Figure 135 elO logging on page 187 186 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com 42 BIO SOPHO Messenger Net v2 eKernel elO Logging Logging FP AI 100 FP AI 100 FP AI 100 FP AI 100 FP AI 100 FP AaI 100 FP AI 100 ms S g de S S S S S S S module module module module module module module 0l 0l 0l ol 0l 0l 0l contact contact contact contact con
37. DECT Messenger Installation and Commissioning Book 1 March 2012 203 Module eLICENSE Applying the key The license file name contains the originating computer name for example MESSENGER as well as the licensed module name for example eFR Therefore if you request a license for computer MESSENGER for add on eFR the filename is MESSENGER_eFR reg A sample license file follows oD MESSENGER_oFR reg Notepad JOE File Edt Format Yew Help windows Registry Editor version 5 00 a c 9ES20303 622 7 EA3147EEE968CF13 E Figure 147 Sample license file Applying the license file 1 To apply the license file place the license file in any directory of your destination system for example in C Program Files Messenger Net Reg 2 Double click the license file A message appears 3 Click Yes when the message appears that asks if you are sure you want to add the information in the license files for example C Program Files Messenger Net Reg Messenger_eFR reg to the registry A Registry Editor message appears that states that the Information in your license file is successfully entered into the registry 4 Click OK when the Registry Editor message appears When you request a license key for other add on modules you receive additional REG files that also must be merged Disaster recovery If your system is replaced by another system the following message box appears to indicate that the previous license file i
38. Drag and drop to group records using Group The example in Figure 121 eGRID with Show help mode on page 173 shows the Show help mode 172 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Figure 121 eGRID with Show help mode DECT Messenger Installation and Commissioning Book 1 March 2012 173 Module eGRID Figure 122 eGRID with View another table mode 174 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com GB cGRID SOPHO Messenger Net v2 8 0 laaja aga 828832288 f j 3 BB adiad l ago 3 5 E Database Merenge CFG Table eKERNEL_DEVICE 00000 141723 Figure 123 eGRID grouping functions Because eGRID is the preferred access method for maintenance an extra functionality is implemented to optimize flexibility This functionality is referred to as Data Filtering and is handled through the command buttons Subset Clear filter and an entry field between the column heading and the first row Figure 124 eGRID Data Filtering on page 176 illustrates the usage of Data Filtering This example shows a subset of the devices of site 3 area 1a and output program eDMSAPI in the table eKERNEL_DEVICE You can clear the subset criter
39. E A E E T 126 Manufaciurr ESPA and modal ASCOM niiina N EA AA A 126 Manufactirer ESFA and model VSK sonreir tea aE E EA E EREA N RAE 126 Chapter 16 Module eESPA Sampple seeeeeeeeeeeeeeeeeeneeeeseeeneeeeeeeeseeeeeesenseeseeeeenees 133 Chapter 17 Module COIS AP lt s asion aasa ae aaan e aiaia 135 E EE E I E E E A ew ae E T eee E Ecce 135 B a ARE A E E E eater ua E E E A E AE E ETE 135 ENR C o T ei E E aa sats cancesecectaareacevaseiesuaramereccranes 139 Eae ha o T E E E E E E rr E E E T T 139 Ghapter 18 Module FRacsasnnnnnasnenn nen 147 EE E i ETE E EEE AN I E A E EA OA A A A S 147 Be ONN aaa 147 Wwenew ai Manton a a SS 148 SAE eS o T A E E E E E A E E A T A 149 4 DECT Messenger Installation and Commissioning Book 1 March 2012 merai NN aaa ese saat setae vid a aaar 150 Launch Lg 2 6 01 0 1 lm Dp rm nero eet PrnO pT a S YT EOEDPeTaE Ty EPCUIY EOD T TT aE TT Orr Per Pr rE NTT 150 Licenca PVCS aF R acae nia ra a aa RaR 151 Connie Meddle BF rinii ann inane nl eae 151 Ups SANGLI aea P r E E E E E E E E T 152 Pestnatone 2 LULL Aer eee tet ne i E A TEP OTT ern PeP rT str eT PPOTT Rr TrT ret Tyr 152 Epes eR FNS Connouaioecsnionni ia a 153 Destinations Ty NE Tecrit iL nie an ia e iaia 155 Destmatine De PERE ascites ed vaduide ces a a a T A 156 Destinations type SMTP vesnssaissy ates iatyteadieketcead a a aa A ar 156 Pesinatons DPE ONMP neccusiiana caieauaide ucaiaendedleatuetacaneents 157 ianea a E E
40. Messenger Installation and Commissioning Book 1 March 2012 7 New in this release 8 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 2 Introduction DECT Messenger is a client server software platform for processing and converting messages between various protocols It consists of several modules some of which can be deployed independently on other PCs in the same network The DECT Messenger modules are grouped as follows e Core core components of the software including security and maintenance tools e Input Output modules used for sending or receiving messages to or from supported devices e Add Ons optional expansion modules adapted for specific customer needs e Web Administrator a web application that enables web based access to a limited set of functions A configuration tool called eCONFIG is also available See Getting Started with DECT Messenger for details on configuring a fresh installation There are two installation types available for DECT Messenger e Server mode includes the Kernel module the database and the web access module all other modules are also available for selection e Client mode includes a limited set of modules that can be deployed on a client PC These modules connect to a DECT Messenger Server installed in the same network Using the client mode installation is optional for small sites the modules can be deployed on
41. Module eLICENSE add on modules are activated In the majority of the cases add on modules such as eFR reside on the MESSENGER system running eKERNEL However when add on modules are installed on different systems install eLICENSE on the systems where add on modules are installed Installing eLICENSE 1 Locate and open the eLICENSE module from the CD ROM image found in directory 09 Add ons 2008 04 23 gt 2008 04 23 eLICENSE 2 Double click the SETUPEX EXE file to install 3 Accept all defaults After installation the software resides in C Program Files Messenger Net Exe 4 Open Explorer and navigate to C Program Files Messenger Net Lnk 5 Copy the directory R4 0 Messenger Net add on and drag it to the Start button bottom left of the windows desktop e Link oe File Edit View Favorites Toob Help kid Oea Oy P sead Gy roles Fv Adcress C C Program FilesiMessenger fetiLnk Go Name Size Type File and Folder Tasks 7R4 0 Messenger Net add cn Fie Folder Other Places x Messenger Net H My Documents 5 8ENB121027 w My Network Places Details y Run module eLICENSE Running module eLICENSE 1 Start the module eLICENSE by double clicking file C Program Files Messenger Net Exe eLICENSE exe A window similar to the one in the following figure appears 202 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Run
42. NETSTAT The following figure shows a more complete definition of a configuration section monitoring the state of TCP Server that is expected to be always in state listening The figures illustrates the example of an environment running a local Internet Information Server with SMTP Server component listening to default port 25 DECT Messenger Installation and Commissioning Book 1 March 2012 167 Module eFR lt Connection id Mail Server port 25 state Listening gt lt ConnectionDown gt lt Message gt Mail Server is down lt Message gt lt Destinations gt lt Destination gt eSNMP lt Destination gt lt Destinations gt lt ConnectionDown gt lt ConnectionUp gt lt Message gt Mail Server is up lt Message gt lt Destinations gt lt Destination gt eSNMP lt Destination gt lt Destinations gt lt ConnectionUp gt lt Connection gt Figure 115 Monitoring the state of the TCP server If the SMTP Server is stopped by an administrator the socket no longer is listening on port 25 and the message Mail Server is down is sent as an SNMPv1 trap to the configured SNMP destination Definition of a TCP client Asample definition of a connection is shown in the following figure The definition is very similar to the definition of a TCP Server but the state is established instead of listening lt Connection id Messenger Net eCAP port 3102 state Established gt Figure 116 Definition of a
43. Refresh _ EMT_OUTPGM_Appl_ str FMT_OUTPGM_Facility_sti FMT_Bytes_inel_n FMT_Bytes_Ine2_n FMT_Bytes_line3_n FMT_Page_ind_n Figure 193 Module eSMS eKERNEL_DEVICE_FORMAT 238 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Web interface Service Help RD A We E 2006 by NEC Philips Unified Solutions Woensdag 20 december 2006 11 12 38 Figure 194 SMS Service logging tab Web interface When eSMS is configured the new Web Administrator interface features a window where you can send an SMS message from the web interface This window retrieves all defined devices from the eKERNEL_DEVICE table configured for the eSMS output program DECT Messenger Installation and Commissioning Book 1 March 2012 239 Module eSMS Ele Eck lew Go Gookunerks Teck Heb e ice gt z a amp A DI http itive messengers laptop misssen com 23800 HE ceabler La Cockers F css O Ferme Zi Imee formatere C Mecelareaer 1 Otiner 3 Resizer E Tock T vion Source i Optia Send a Message Please select destination Identifier Facility Description Comments Dsene a message 32473897171 SMS Francis Missiaen Default comments EHE DECT handset 6 area i P EE SMS Francis Missiaen Default comments H mobile phone Area 1 Emal HE windows fread S wifi phone D area B EDSNHP tep 1 0 Group Massage 0 User Message Work with Scripts HO
44. SHS tok Sal iy lt reply gt Your inbound SMS request with p BHOHHOM MN xml version 1 0 gt lt reply gt Your inbound SMS request with pincode 238 confir A Data arrival 148 bytes received fiom eKERNEL J 00050 21 51 47 amp Figure 185 Logging tab The logging files provide more details on the data exchange as shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 233 Module eSMS I TCP lt xml version 1 0 gt lt SMSmessage gt lt type gt SMS DELIVER lt type gt lt originat ingAddress gt 32495363201 lt originat ingAddress gt lt userD ataLength gt 11l lt userDataLength gt lt userData gt Confirm 238 lt userData gt lt SMSmessage gt O TCP lt xml gt lt smsrqs gt lt id gt 32495363201 lt id gt lt msg gt Confirm 238 lt msg gt lt smsrqs gt lt xml gt I TCP lt xml gt lt smsrpy gt lt id gt 32495363201 lt id gt lt sts gt ACK lt sts gt lt msg gt Your inbound SMS request with pincode 238 confirmed 0 alarms on 5 devices lt msg gt lt smsrpy gt lt xml gt O TCP lt xml version 1 0 gt lt reply gt Your inbound SMS request with pincode 238 confirmed 0 alarms on 5 devices lt reply gt lt result gt 0K lt result gt Figure 186 Logging files Configuration 234 The eSMS module is configured through the eCONFIG module The eSMS module requires eCONFIG 2 9 10 or above The following eight figures illustrate the configurat
45. Site NEC node in the tree 2 Expand the Modules node 3 Under the Modules node expand the node that represents the type of module which you do not intend to use 4 Double click the module name e g eESPA area Hilversum The module details window appears see Figure XY 5 In the module configuration window click Delete A confirmation window appears 6 Click OK to confirm the removal Configuring area information When using the default database configuration deployed by the installer two areas are already present You can view them by expanding the Site NEC node and clicking the Areas node in the tree Modifying the description of an area 1 Expand the Site NEC node in the tree 2 Select the Areas node 3 Double click the desired area listed in the right pane The Area configuration window appears as shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 55 Getting started with DECT Messenger eCONFIG Messenger Net v4 1 7 admin LOCAL Messenger Net Import Export License information CB Site NEC Areas Modules All alarms All users Groups and devices Al groups Group without devices tae Group Authorty Fly All devices Gad Inbound LMRS SP Monitored devices Fle Devices with a Pincode Alemative devices Device format Fle Devices not assigned to a group E Hobday Figure 26 eCONFIG Area configuration window 4 Select the Descrip
46. TCP client The definition of a connection contains the following parameters e Define the parameter id which defines the unique identifier of the monitored item The value Messenger Net eCAP in the example defines the connection You can specify a value of your choice Avaya recommends that you use a name meaningful to you e Define the parameter port which defines the port number For example the value 3102 specifies a specific port used by DECT Messenger e Define the parameter state For monitoring TCP Clients define the value established It is expected that a TCP Server is always up and running and is in state connected on port 3102 with a TCP Client in the local system that runs the eFR monitoring process Note The specified port is the port on the TCP Server In a TCP client server connection a TCP Server listens on a specific port A client can reside on the same system or on another system and make a socket connection by specifying the 168 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Sample e mail address and the port the server listens to The following figure illustrates that the server listens on port 3102 C WINDOWS system32 cmd exe B x ICP 6 0 8 0 3102 CACAO RCH LISTENING Figure 117 TCP client server connection If connection is successful a connection is established between the client and the server In a NETSTAT command window
47. a criminal as well as a civil offense under the applicable law Third party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements Third Party Components which may contain terms that expand or limit rights to use certain portions of the Product Third Party Terms Information regarding distributed Linux OS source code for those Products that have distributed the Linux OS source code and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site http support avaya com Copyright Preventing Toll Fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party for example a person who is not a corporate employee agent subcontractor or is not working on your company s behalf Be aware that there can be a risk of Toll Fraud associated with your system and that if Toll Fraud occurs it can result in substantial additional charges for your telecommunications services Avaya Toll Fraud Intervention If you suspect that you are being victimized by Toll Fraud and you need technical assistance or support call Technical Service Center Toll Fraud Intervention Hotline at 1 800 643 2353 for the United States and Canada For additional support telephone numbers see the Avaya Support Web site http sup
48. a line appears illustrating that a TCP connection is found on port 3102 with the state ESTABLISHED C WINDOWS system32 cmd exe lof x TCP 10 128 65 159 3102 16 128 65 159 4817 ESTABLISHED aren Figure 118 NETSTAT command window The previous figure shows the client address and port in the third column 10 1289 65 159 4817 In many environments the client is not bound to a fixed port and receives a random assigned port number for example 4817 The capability of eFR monitoring client connections of NETSTAT is oriented towards application environments with a persistent socket connection For example DECT Messenger is an example of a software suite based upon client server architecture where the majority of client modules must be connected permanently with predefined ports on the server Typically you must monitor the TCP clients eDMSAPI eCSTA eSMS eCAP modules connected to eKERNEL on the configured ports Sample e mail A sample e mail is shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 169 Module eFR Insert Format Tools Actions Hep francis missiaen nec philips com Sent do 05 04 2007 10 06 Missiaen Francis cc Subject Fault Report for i53000 unit 01 gt DIMAJA O1 Message 31 No relations or data found EXECUTED gt DIMINA 01 Alarm buffer 14 unit 1 CODE TYPE SHELF BRD CRT occ DATE TIME QLF ADD 33 22 12 a 1 2007 03 06 2 16 41 1 2 0 033
49. address refers to the IP address of the system that runs the SMS_ service process When the service runs on the same system use the loopback value 127 0 0 1 e The parameter port refers to the port number that is configured in the SMS_ service process for inbound SMS request The default value 29081 matches most installations Refer to the SMS_ service system administrator e The parameter extension is the most important parameter as extension defines the destination peripheral of the SMS notification Format extension starting with and country code which results in a valid mobile GSM phone For example in Belgium a valid mobile extension number is formed starts with 32 followed by the remaining numbers of the mobile GSM phone Destinations type SMTP The following figure illustrates Destinations type SMTP 156 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Destinations type SNMP lt Destination id eSMTP type SMTP description Francis Missiaen address 127 0 0 1 port 25 dom ain nec philips com from frands missiaen nec philips com to francis missiaen necphilips com gt Figure 94 Destinations type SMTP The following parameters are specific to SMTP e The parameter description refers to the name of the destination user and allows you to assign a user name For example enter the first and last name of the user e The parameter address refers
50. address gt ENQ that tells the controlling station that this slave wants to transmit some data If a slave receives data that is not assigned to the slave address the slave ignores the data If a slave does not respond to an enquiry within eESPA_Timeout_n seconds the controlling station places this slave in a special offline list When polling the controlling station reads the offline list to determine if a slave is online or not before sending an enquiry After 60 seconds the slave is removed from the offline list and polling to the IP address of the slave is restarted If the slave does not react the slave is put back in the offline list By using 124 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Data flow an offline list also known as a black list the polling interval is not disturbed by repeated timeouts of some slaves The controlling station stops polling when data is waiting to be sent to one of the slaves or when a slave has indicated that data is ready to send The controlling station stops polling when a message request is received from the eKERNEL The controlling station then creates a data block and sends this to the appropriate slave address A slave station sends data in the same fashion but with one difference the slave first has to wait to be polled to tell the controlling station that data is ready to send When a slave is polled and has data to send the slave te
51. and reboot the PC and then restart the installation procedure 3 Click Next to continue The Install Prerequisites window appears as shown in the following figure 38 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Installing DECT Manager Cy Requirements Setup Wizard Ea Install Prerequisites Installs software components required prior to installing e the product __ Action _Status V Microsoft Windows Installer 3 1 Success V Sentinel Dongle Driver Reboot R Vv CTI Runtime Library 2 0 0 Success SMTP Server Warming SMTP Server feature of Internet In A Internet Information Server Warming Internet Information Server IIS or Jv Adobe Reader 9 0 Success A National Instruments DataSocket 4 7 1 Warning National Instruments DataSocket 4 A National Instruments FieldPoint 6 0 6 Waming National Instruments FieldPoint 6 0 MOXA NPort Administration Suite 1 12 Waming MOXA NPort Administration Suite 1 Installation Progress Progress Information 9of9 Finished Beport Figure 14 Install Prerequisites window 4 The Setup Wizard checks if all necessary third party software components are present and attempts to automatically install any missing mandatory ones The mandatory components are as follows e Sentinel Dongle Driver package e CTI Runtime Library 2 0 5 Verify the warning messages about missing optional compo
52. area False Comments Defauk configuration 2 Output program The current value for this parameter is Delete Refresh OK Cancel Figure 28 Device details window 4 Select the Output Program and click Browse The Select Output Program window appears as shown in the following figure 58 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Configuring DECT Messenger Device Select Output Program xi Nom vy Subset __Cear subset Reteh _ TCPCLIENT Area d n CoLTCPCLIENT_ Pgm_nam TCPCUENT Comments str Figure 29 Select Output Program window 5 Select eDMSAPI by clicking the black arrow and click OK 6 Select and specify a Device ID the extension number e g 2000 7 Select the Output program facility and click Browse The Select Facility window appears as shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 59 Getting started with DECT Messenger Device Select Facility x Normal v Subset Clear subset Refresh femi UU IPGM Facility sir Figure 30 Select Facility window 8 Select a handset model and click OK 9 Select and specify other properties if necessary e g Description 10 Click OK to save the new device Several devices can be added to a group as group members Working with groups and group members as well as further
53. available in the datastream Messages are sent with alarm description ARITECH An alarm is set only when Gebeur occurs in the datastream When BRAND occurs the message is BRAND in other cases the message is ARITECH When HERSTEL occurs a general reset of all ARITECH alarms is issued Note Use of this protocol usually requires consulting services and customizing 102 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com ARITECH SCENARIO 1 Brand actie SET message T112 det groep ARITECH_B alarm description ARITECH_B Alarm 1 Gebeu 2109 Aktief Zone 42 Geb 0 Adres 3 1 Brand OPT 04 07 05 10 19 03 P 6 T122 det SCENARIO 2 Fout actie SET message Printer afgekoppeld G 1 groep ARITECH_F alarm description ARITECH_F Fout 1 Gebeu 661 Aktief Poort SER2 Printer afgekoppeld 04707705 10 08 39 G 1 SCENARIO 3 Fout communicatie fout actie SET message T122 det F6 groep ARITECH_C alarm description ARITECH_C Fout 1 Gebeu 2106 Aktief Zone 42 Geb 0 Adres 3 1 Communicatie fout OPT 04 07 05 09 59 54 P 6 T122 det SCENARIO 4 Herstel RESET naar alle input Actie 1 Gebeu Herstel 04707705 10 30 19 P 8 Figure 57 ARITECH Model 1 alarm based upon installation RUCA Aritech model 1 alarms are always sent to group ARITECH_F ARITECH_C or ARITECH_B depending on the datastream Messages are sent with alarm d
54. avaya com Logging lt msgtype gt normal lt msgtype gt lt direction gt outbound lt direction gt lt senddata gt lt xml gt 03 10 2002 12 08 58 I TCP lt xml gt lt SendDataResult gt lt invokeID gt 59 lt in vokeID gt lt SendDataResult gt lt xml gt 03 10 2002 12 09 00 I TCP lt xml gt lt SendDataArgument gt lt invokeID gt 31206 lt in vokelID gt lt ioCrossRefIdentifier gt 5697 lt ioCrossRefIdentifier gt lt Provider gt 1 lt Provider gt lt Text gt lt ack gt lt Text gt lt SendDataArgument gt lt xml gt 03 10 2002 12 09 00 O TCP lt xml gt lt senddataresult gt lt invokeID gt 31206 lt in vokelID gt lt senddataresult gt lt xml gt 03 10 2002 12 09 00 O TCP lt xml gt lt stopdatapath gt lt iocrossrefid gt 5697 lt iocrossrefid gt lt originator gt pbx lt originator gt lt stopdatapath gt lt xml gt 03 10 2002 12 09 00 I TCP lt xml gt lt stopdatapath gt lt iocrossrefid gt 5697 lt iocrossrefid gt lt originator gt pbx lt originator gt lt stopdatapath gt lt invokeID gt 61 lt invokeID gt lt xml gt 03 10 2002 12 09 06 I TCP lt xml gt lt StopDataPathResult gt lt InvokeID gt 61 lt In vokelID gt nodata lt StopDataPathResult gt lt xml gt DECT Messenger Installation and Commissioning Book 1 March 2012 145 Module eDMSAPI 146 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 18 Module eFR
55. character NUR K100 gt 4 BEERPUT gt 8 e Keep the leading non blank characters NUR K100 and 4 gt NUR BEERPUT and 8 gt BEERPUT e Keep the leading characters only with length specified in L xx NUR and L 03 gt NUR BEERPUT and L 03 gt BEE Table 8 Televic Example Length Original message Resulting alarm type Length L 01 NUR K100 N 1 WC 120 W 1 BEERPUT B 1 L 02 NUR K100 NU 2 WC 120 WC 2 BEERPUT BE 2 L 03 NUR K100 NUR 3 WC 120 WC 2 BEERPUT BEE 3 L 04 NUR K100 NUR 3 WC 120 WC 2 BEERPUT BEER 4 L 05 NUR K100 NUR 3 WC 120 WC 2 BEERPUT BEERP 5 Refer to the official specifications on Televic Protocol Convertor You can obtain these specifications from the manufacturer or through Avaya sales support Detailed information is beyond the scope of this document Televic is based upon installation CAZK campus Groeninghe Kortrijk 110 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com TELEVIC 07 01 2001 00 02 15 07 01 2001 00 02 15 07 01 2001 00 02 22 07 01 2001 00 02 23 07 01 2001 00 02 24 07 01 2001 00 02 25 07 01 2001 00 11 17 07 01 2001 00 11 17 07 01 2001 00 11 23 07 01 2001 00 11 24 07 01 2001 00 11 25 07 01 2001 00 11 26 07 01 2001 00 16 39 07 01 2001 00 16 39 COM _00103224210 8POORT1O0Y4C_ COM _A0103Y1A_ COM _T010312421052_ COM _A0103Y1A_ COM _T0103124210
56. com Logging 03 10 2002 13 59 00 S INF TCP local port 59000 connected with remote port 59000 csta service PBX type DMC 03 10 2002 13 59 00 O TCP lt xml gt lt connecttopbx gt lt ipad dress gt 10 110 49 171 lt ipaddress gt lt port gt 2555 lt port gt lt guarding gt 60 lt guard ing gt lt seats gt 20 lt seats gt lt licence gt Messenger lt licence gt lt network gt ETHERNET_DMC lt network gt lt connecttopbx gt lt xml gt PBX type DAP controller 03 10 2002 13 59 00 O TCP lt xml gt lt connecttopbx gt lt ipad dress gt 10 110 49 171 lt ipaddress gt lt port gt 28001 lt port gt lt guarding gt 60 lt guard ing gt lt seats gt 20 lt seats gt lt licence gt Messenger lt licence gt lt network gt dasgif lt network gt lt connecttopbx gt lt xml gt PBX type CS 1000 03 10 2002 13 59 00 O TCP lt xml gt lt connecttopbx gt lt ipad dress gt 10 110 49 171 lt ipaddress gt lt port gt 28001 lt port gt lt guarding gt 60 lt guard ing gt lt seats gt 20 lt seats gt lt licence gt Messenger lt licence gt lt network gt dasgif lt network gt lt connecttopbx gt lt xml gt 03 10 2002 13 59 00 I TCP lt xml gt lt connecttopbx gt lt result gt success lt re sult gt lt guarding gt 60 lt guarding gt lt autoguarding gt 1 lt autoguarding gt lt connecttop bx gt lt xml gt 03 10 2002 13 59 00 S INF Service connected and logical link estab lished 03 10 2002 13 59 00 O TCP lt xml gt lt iore
57. computer administrator account During installation you may be prompted for the Windows operating system installation media CDs DVD Ensure they are available before proceeding Use the following procedures to install IIS Installing IIS on Windows XP Windows Server 2003 Windows Server 2003 R2 To install IIS or to verify that all necessary components are installed perform the following steps 1 Click Start gt Settings gt Control Panel 2 Select Add or Remove Programs 3 Select theAdd Remove Windows Components tab The Windows Components Wizard window appears 4 Ensure that Internet Information Services IIS option is checked as shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 25 Preparing the Operating System 26 Windows Components You can add or remove components of Windows XP To add or remove a component click the checkbox A shaded box means that only pe Wd the component will be installed To see what s included in a component click Components C Fax Services O G Indexing Service V intemet Explorer A Ss Mananement and Manitarina Tans Description Includes Web and FTP support along with support for FrontPage transactions Active Server Pages and database connections Total disk space required 19 8 MB Details Space available on disk 3608 0 MB Z lt Back J Nen Figure 7 Windows Components Wizard window 5 Select Details Th
58. details on supported output devices can be found in DECT Messenger Fundamentals NN43120 120 Publishing or discarding changes When you are working with eCONFIG changes to users devices and groups are published immediately However structural changes to sites areas and modules require the local database to be copied back over the production database on the DECT Messenger Server Note Publishing overwrites any changes made to the production database after eCONFIG created its local copy during start up You must ensure that users did not make changes to the production database after the local copy was created When you want to end the configuration process select File gt Exit from the eCONFIG main menu You are then asked if you want to apply the configuration changes Click Yes to apply the changes or No to cancel Before you can publish the new configuration you must ensure the current database is not in use This means that all DECT Messenger modules must be stopped Before stopping a production environment take into consideration that all pending alarms are cleared at restart 60 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Configuring DECT Messenger Also while eKERNEL and associated modules are down no input and output is performed and alarm input and distribution is suspended Stopping active modules 1 On the server PC where the database is located check
59. eAPI form 3 Site 1 eKernel address LOCAL eKernel port 3209 Log drive C g_command Command If g_command Then Lcl_Msg Warning eAPI is started without command line parameters Chr 10 Ch r 10 Lcl_Msg Lcl_Msg Check the command string in the target value in the properties o i Wier Sloowicewmes a CleS il a Claics 10 Lcl_Msg Lcl_Msg Please confirm to start this session with the following replacem ent values Chr 10 Chr 10 g_command Site 2 eKernel address LOCAL eKernel port 3209 Log drive C tel re InputBox Lcl_Msg Me Caption g_command ime dieul see Mhen End Else G Commenee tel re Bn Lf Eno If Initialise screen labels lab_ekernel_remote_address N A lab_ekernel_remote_port N A lab_ekernel_local_address N A lab_ekernel_local_port N A Get command line parameter g_site parse_cmd_line Site g_ekernel_remote_address parse_cmd_line eKernel address g_ekernel_remote_port parse_cmd_line eKernel port g_log_drive parse_cmd_line Log drive Handle special values If g_ekernel_remote_address LOCAL Then g_ekernel_remote_address ip_ekernel LocalIP 1 o Steaiate log S INF Application amp Me Caption amp started with parameters amp g_command DECT Messenger Installation and Commissioning Book 1 March 2012 73 Mod ule eAPI sample Terminate if undefined values ae g_s
60. gt lt ent_01 gt 8 lt cnt_01 gt lt mod_02 gt FP DI 300 lt mod_02 gt lt url_02 gt opce National Instruments OPCFieldPoint FP Res FP DI 330 2 Channel lt url_02 gt lt cnt_02 gt 8 lt cnt_02 gt lt mod_03 gt FP DO 401 lt mod_03 gt lt url_03 gt opce National Instruments OPCFieldPoint FP Res FP DO 401 3 Channel lt url_03 gt lt cnt_03 gt 16 lt cnt_03 gt lt ai_01_01_min_s gt 00 000000 lt ai_01_01_min_s gt lt ai_01_01_min_r gt 00 000000 lt ai_01_01_min_r gt lt ai_01_01_max_r gt 12 000000 lt ai_01_01_max_r gt lt ai_01_01_max_s gt 20 000000 lt ai_01_01_max_s gt lt ai_01_08_min_s gt 00 000000 lt ai_01_08_min_s gt lt ai_01_08_min_r gt 00 000000 lt ai_01_08_min_r gt lt ai_01_08_max_r gt 12 000000 lt ai_01_08_max_r gt lt ai_01_08_max_s gt 20 000000 lt ai_01_08_max_s gt lt log_path gt C SOPHO Messenger net lt log_path gt lt log_days gt 1 lt log_days gt lt cfgrpy gt lt xml gt Figure 129 elO configuration request and response When the configuration is received the elO updates the configuration information on the Connections tab as shown in Figure 130 elO Connections update on page 182 During this time the elO is temporarily less responsive to user input This is due to the large number of OPC Server connections that take place at startup time DECT Messenger Installation and Commissioning Book 1 March 2012 181 Module elO 42 eIO SOPHO Messenger Net v2 0 6 eKer
61. id gt lt sts_cnt gt 1 lt sts_cnt gt lt sts_01 gt ACK lt sts_01 gt lt msgrpy gt lt xml gt Figure 76 Detailed logging information The label Last message shows the last sent or received message Manufacturer ESPA and model ASCOM In release 4 0 an additional implementation of ESPA 4 4 4 protocol is available You can activate it by defining manufacturer ESPA and model ASCOM For further information contact Unified Communications Professional Services UCPS division for more information Manufacturer ESPA and model VSK In release 4 0 an additional implementation of ESPA 4 4 4 protocol is available and is activated by defining the manufacturer ESPA and model VSK 126 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Manufacturer ESPA and model VSK a eESPA SOPHO Messenger Net v4 0 0 Slave PE eKERNEL eESPA Loggirg eKERNEL Connections eKERNEL Corfiguration a ESPA d definiti local 132168112 3301 Controlinastation No Pe Pata ene Remcte 192168112 ai1 Poling No ____ _ mee lore Interval meeconds 150 Address es Message 2 Tink ppe R5232 Alarm dezcipton 3 eESPA Resouce com Calltype 4 Pot COM1 Settings amans Nmbr of tansm 5 Settings 9500 M 81 NAK ety count 2 Prioiity 6 tau Open J Timeout seconds 10 Remove after SENT Log path C SOPHO Messenger N et Modal vek Log days T4 Answer de
62. lab_ekernel_state Backcolour RGB 0 0 0 Show copyright lab_msg amp App LegalCopyright Initialise CFGROS variables g_log_path g_log_drive SOPHO Messenger Net g_log_days 14 lab_log_path amp g_log_path lab_log_days amp g_log_days Ininitialise guarding g_guarding Timer Enable timer for eKernel tim Interval 100 tim Enabled True End Sub Private Sub ip_ekernel_Connect Dim lcl_version As String Dyin Ikeul_ As G Update screen 74 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 g_ekernel_local_address ip_ekernel LocalIP lab_ekernel_local_address amp g_ekernel_local_address g_ekernel_local_port ip_ekernel LocalPort lab_ekernel_local_port amp g_ekernel_local_port iog Sp NE Woe local pore amp Korvac G eksrasl local joorce OOOO connected with remote port amp FormatS g_ekernel_remote_port 00000 amp eKERN End Sub Private Sub ip_ekernel_DataArrival ByVal bytesTotal As Long ip data received lab_msg Data arrival amp bytesTotal amp bytes received from eKERNEL Dim Lel L AS STA ip_ekernel GetData lcl_i vbString Append to buffer and isolate a valid lt xml gt xxxx lt xml gt sockets data stream g_ekernel_buffer g_ekernel_buffer lcl_i Dim lcl_str_xml As Integer Dim lcl_end_xml As Integer Daim lel clea ssw Ag Sitrin Begin Loop Do 1 Check i lt mi gt gerino oCeur
63. launched 20110330161012 PID VODOTNOT Emer Task Messergen Net eNET Port 3118 coud no be lawehed 201705301 61012 PID 000000251 Tack Messenger Nel eSMS Port 3117 bunched 20110330161012 PID 0020000828 Tack Mescenge Ne eSMTP Por 3111 launched eC51A Pot 3107 eDM SAFI Port 3101 ESPA Pot 3113 el Pon 3108 Kenal Site 1 oLOCATION Pot 3115 Worosda 39March 2011 16 10 2007 2011 NEC Nedolland BY eo Figure 33 eTM with running modules Discarding changes 1 When asked whether to apply the new configuration click No A window appears asking you to confirm that you want to exit the application 2 Click Yes Any changes are discarded without being published Using eCONFIG in a distributed environment When eCOMFIG is on the server PC the path to the configuration database in the INI file is automatically populated by the installation program You can run eCONFIG on another PC but you can only add or modify users groups and devices When running in a distributed environment with eCONFIG installed on a client PC you require access to the configuration database located on the server PC This means that the directory DECT Messenger Installation and Commissioning Book 1 March 2012 63 Getting started with DECT Messenger where the MessengerConfig mdb resides on the DECT Messenger Server must be shared over the network to enable remote machine
64. module eLICENSE TE eLICENSE SOPHO MessengeroNet v4 00 OB zle Help Identifier 86 Family 6 Model 13 Stepping 8 Mac Address Joz 00 4C 4F 4F 50 Module eFCS Generate 1 gt Expire date 31 12 2099 Temp Perm Apaly key 2007 by NEC Philips Unified Solutions 2 Save the XML file by selecting File gt Save Fingerprint 3 Accept the default path C SOPHO Messenger Net xXml The default filename is usually your computer name with extension Xml For example on computer MESSENGER the file is MESSENGER Xml The resulting XML file contains 7 parameters retrieved from your hardware and operating system 4 Use Internet Explorer to open the XML file Double click the file residing in C Program Files Messenger Net Xn1l File Edit View Favorites Tools Help Osx O fH DO Aarh rats O 3 B VRAD s 2 c Program Files Messenger Net xmi MESSENGER xml l lt xml version 1 0 gt lt Fingerprint gt lt ComputerName gt BENB121027 lt ComputerName gt lt RegisteredOrganization gt NEC Philips Unified Solutions lt RegisteredOrganization gt lt RegisteredOwner gt NEC Philips Unified Solutions lt RegisteredOwner gt lt Productid gt 76487 641 3119356 23175 lt Productid gt lt VolumeSerialNumber gt 584F A5D8 lt VolumeSerialNumber gt lt Identifier gt x86 Family 6 Model 13 Stepping 8 lt identifier gt lt MacAddress gt 02 00 4C 4F 4F 50 lt MacAddress gt lt Fingerprint gt
65. of the following messages Error Configuration database is in use eKERNEL Of Error Configuration database is in use eGRID If this happens verify that the mentioned module is shut down on the server Select the configuration database to import as shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Configuring DECT Messenger gt Messenger Net Web Administrator Windows Internet Explorer Gorle 127 0 0 1 perNet Aas x p Ge Favortes P SogrtedStes gt P Web Sice Galery Meccenger Net Wob Adninictrator M O om bs Seye Tok Oe Import Configuration Please select configuration database to import NEC UNIFIED SOLUTIONS Description Comments 00 Defeult Tue 29 Mer 2021 09 47 10 0309 00 Empty Tue 29 Mar 2011 09 47 14 0300 GJ Send Message DECT hencset 01 eDMSAPI eLOCATION eWEB iS3000 Tue 29 Mar 2011 09 47 14 0300 A pecrsnd tenian 02 COMSAPT eLOCATION eW2D I gt DECT Tue 29 Mer 2011 09 47 12 0300 Group Meccage Ucer Mescage 02 oDMSAPI LOCATION eWEB oSNMP 1P DECT Tue 29 Mar 2011 09 47 10 0300 03 eDMSAPI eLOCATION eSMS eWEB iS3000 Tue 29 Mar 2011 09 47 08 0300 04 EDMSEPI ELOCATION eSMS eWEB IF DECT Tue 29 Mar 2021 09 47 14 0300 S eDMSAPI clO ewEB iS3000 Tue 29 Mer 2011 09 47 14 0300 gt K 06 eDMSEPI e10 eWEB 1P DECT Tue 29 Mar 2011 09
66. or subdirectories DECT Messenger Installation and Commissioning Book 1 March 2012 49 Getting started with DECT Messenger When eKERNEL starts it displays a main window similar to the one shown in the following figure KERNEL Messenger hct v4 1 7 Ele KERNEL Ste li NEC PahLoc C Progom Files xOO WEC Mersenge QNel Logs Ucense Meszenger Net PULL PathelOG C rogan Fides SEINE CW ersenger NeNLogs Conmmuncat faeo TT N OO 00101 DMAP papei Sever 1321600172 000 Chose efter rom O2104 eCAP chert T farLntenns TT ee gt fhe aed Dorse D Max connections 5 O16 eVSVOICE 02107 oCSTA Loggng 0nB e0 0109 owEB 0110 eSMIP_Sever 03111 oSMTP O21 2 ear 03113 ESPA 021 4 eESPA 00115 LOCATION 0116 eSNMP 00117 oSMS of 0118 eNET Booo sconci EP z oo a Figure 21 The eKERNEL main window The list on the left indicates the configured modules their status and the connection information required to connect to eKERNEL Using eCONFIG Configurator 50 You can install and useCONFIG on the server or on one of the client PCs However when running from a client PC you can only modify a limited number of properties users groups and devices eCONFIG requires access to the configuration database as well as an open TCP IP connection to eKERNEL Ensure that eKERNEL is running and configured to accept eCONFIG connections No
67. pop up message on a destination PC with a Windows operating system 154 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Destinations type NET e SMS SMS is used with SMS technology to send a SMS message to a destination mobile GSM phone e SMTP SMTP is used when sending an e mail message by means of an SMTP enabled mail server infrastructure resulting in delivery of an e mail message to the inbox of the destination addressee e SNMP SNMP is used when sending SNMPV1 trap to a destination SNMP trap receiver Depending of the selected notification type define additional parameters as needed Typically additional parameters define the remaining values that are specific to the selected transport mechanism and contain information to identity the destination user or device as well as parameters that define the intermediate infrastructure The following Destination types are described in this chapter e Destinations type NET e Destinations type SMS e Destinations type SMTP e Destinations type SNMP Destinations type NET The following figure illustrates Destinations type NET lt Destination id eNET type NET description Frands Missiaen from Messenger Net to BENB121027 gt Figure 91 Destinations type NET The following parameters are specific to NET e The parameter description refers to the name of the destination user and allows you to assign a user name For exampl
68. services and lesuo oe abo ruled es Bide Serveer hergin ai Web Server its Wie Sewer lli rowtden a rethebte z Mansgesde and scaldi Wed appicsdon range ot Managenent Tool poe ap xg 5 BS E Marayoners Coroadtity Wen Sever Heath and Dugrootos Renae Server Adminetation Tods Fasha cretion Tonks SMIP Servas Tooti e ness J vee e a Distant server Manoger Ga 2 gt i gt me me Figure 10 Add Features Wizard window 4 Check SMTP Service from the list of available features A confirmation screen displays prompting to add other features and services dependent on SMTP Service 5 Click Add Required Role Services 6 Click Next to proceed to the Web Server IIS role information screen 7 Click Next The Select Role Services wizard page appears with the necessary services already selected 8 Click Next The Confirm Installation Selections page displays where you may review the components to be installed 9 Click Install to being the installation 10 When installation is completed click Close to close the wizard DECT Messenger Installation and Commissioning Book 1 March 2012 29 Preparing the Operating System 30 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 7 Installing third party software This chapter describes how to install the optional third party software that is required to run certain DECT Messenger modules The software is loca
69. setting eESPA_ControlStation_b on No in the database for example you can use a local address of 2 and an external address of 1 In this case the module communicates directly with the controlling station e The label Status shows log information to allow users to see special actions Figure 75 Status of master slave on page 125 shows an example of the eESPA status bar Received 14 18 04 EOT Local adress 1 External address 2 Last msg Sent 14 18 04 2ENQ Status Polling is active Figure 75 Status of master slave DECT Messenger Installation and Commissioning Book 1 March 2012 125 Module eESPA Logging In the Logging tab only basic default logging is shown Basic logging incoming and outgoing data on the communication port 1 COM and O COM incoming and outgoing data on the socket communication with the eKernel I TCP and O TCP and warning information To show and log additional information choose the menu item eESPA gt Logging gt Detailed The additional information is set in bold in Figure 76 Detailed logging information on page 126 I INF gt Created datablock is _1 156789 2eAPI Koekoek 51 63_0 O COM _1_156789 2eAPI Koekoek 51 63_0 I INF gt ACK received on sending datablock O COM EOT I INF gt Concluded transaction with sending an EOT I COM ACK I COM EOT I INF gt Received EOT character after sending messages O COM EOT 0 TCP lt xml gt lt msgrpy gt lt id gt 00124 lt
70. started without command line Parameters Check the command string in the target value in the Cancel properties of the shortcut Please confirm to start this session with the following replacement values Site 1 eKemel address LOCAL eKemel port 3117 Log drive C Figure 174 Startup values prompt The command line parameters are shown in the following figure Site 1 eKernel address LOCAL eKernel port 3107 Log drive C Figure 175 Command line parameters The module eKERNEL responds to the lt cfgrqs gt with lt cfgrpy gt This configuration is retrieved from the Messenger_CFG database table In native mode the configuration is retrieved from the eSMS table This table contains for example the IP address and the port number used to connect to the SMS_ service process This SMS_ service is a separate program that communicates with the SMS box and can run on a local or distributed PC The trace of the configuration exchange is shown in the following figure S INF Application eSMS SOPHO Messenger Net v4 0 0 started with parameters Site 1 eKernel address LOCAL eKernel port 3117 Log drive c S INF TCP local port 01158 connected with remote port 03117 eKERNEL O TCP lt xml gt lt cfgrqs gt lt appl gt eSMS lt appl gt lt site gt 1 lt site gt lt cfgrqs gt lt xml gt I TCP lt xml gt lt cfgrpy gt lt sms_address gt 127 0 0 1 lt sms_address gt lt sms_outbound_por t gt 29081 lt sms_out
71. that one NIRA serial protocol is implemented does not mean that every version of serial input from NIRA is compatible Ensure that a specific alarm system model is supported by DECT Messenger before purchasing or installing it In most cases manufacturers are not using the same standard for all of their equipment so obtain information on protocols and specifications Avaya recommends pre sales consultation If necessary a modification of the current release of eCAP can be made to embed new protocols The most typical protocols are listed in Table 5 Supported manufacturer model protocols on page 100 and described in more detail in the pages following the table Refer to the protocol specifications of each vendor for more information as detailed protocol issues are beyond the scope of this document The information in Table 5 Supported manufacturer model protocols on page 100 provides a list of supported manufacturers and models This information is provided on an as is basis to illustrate the eCAP module Table 5 Supported manufacturer model protocols Manufacturer Model ARGINA BASE ARITECH BASE ARITECH 1 BEMAC DIANA 1 BEMAC DIANA 2 ELDAD L 48 0 RC 1 SR 2 SS 3 SS 4 SR GENERIC BASE GENT 3400 GENT VIGILON EN54 M TECH ESPRESSO NIRA BASE 100 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 ARGINA
72. to close one of the applications before starting the other Both components are part of the National Instruments FieldPoint software package that is located on the DECT Messenger DVD Also required is a DataSocket package that DECT Messenger uses to interact with the OPC Server For details on how to install these packages refer to Installing National Instruments Field Point and DataSocket on page 34 24 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 6 Preparing the Operating System As a general rule ensure that the operating system of the target PC is up to date with the latest service packs and patches installed prior to installing DECT Messenger product Note Avaya recommends that you do not configure the Automatic Updates feature in Windows to Automatic This will avoid system reboots while DECT Messenger is operating The following modules require additional features that are not enabled by default during a standard installation of Windows e Web Administrator requires Internet Information Server IIS On IIS 7 x Windows 2008 Windows 2008 R2 CGI support and IIS 6 Metabase compatibility options must also be enabled e SMTP Server requires IIS and SMTP Service Installing IIS The steps necessary to install Internet Information Server depend on the operating system version Important Before installing IIS verify that you are logged in using a
73. used to handle currently active requests There are three different sections in this area the eKernel the External and the loRegister The eKERNEL and External areas show the active extensions Active requests wait for acknowledge from the CSTA Service A normal message receives an ACK or NAK StopDataPathRequest reply An urgent message receives an initial ACK or NAK Urgent messages that receive ACK wait lt Ack2TimeOut gt seconds for a second ACK or a NAK 138 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Overview of CSTA_Service EXE Overview of CSTA_Service EXE The CSTA_Service runs behind the scenes and communicates through CSTA DLL with a PBX The CSTA_Service acts as TCP server towards eCSTA Communications to a PBX is done through CSTA DLL based upon Ethernet iS Link CSTA interface on Ethernet Details on these communications are beyond the scope of this document The CSTA_Service has no user interface but an icon appears in the tray when it is running When you right click on the icon a pop up windows appears and shows the following options e About CSTA Service shows a banner with a copyright information panel similar to the one shown in the next figure About CSTA Service i x gt CSTA Service for SOPHO Messerger Net 3 0 version 30 1 SOPHO Exposing the functionality from SOPHO CT library to the network Messenger Net 2000 2004 IBS
74. 00 Value 00 000000 00121 22 46 21 Figure 133 Digital Input module information Note When the value of a contact changes from Off to On or from On to Off the Before and After fields are updated with the status of the contact before the change occurred and the status of the contact after the change occurred The Change field is also updated with the new value Digital output discrete output When you select a digital output module FP DO 401 a window appears similar to the one shown in Figure 134 Digital Output module information on page 186 For each module a graphical display shows the available output contacts A grey switch directed to the bottom indicates a discrete output value is Off a grey switch directed to the upwards position indicates a discrete output value is On In Figure 134 Digital Output module information on page 186 contacts 01 and 04 and 07 are On all others are Off DECT Messenger Installation and Commissioning Book 1 March 2012 185 Module elO 42 eIO SOPHO Messenger Net v2 0 6 eKernel elO cae ia 01 02 03 04 05 O06 Of 08 09 10 11 12 13 14 15 16 fos rp po 401 v i it i Pi j EEI i Ei j URL opc National Instruments OPCFieldPoint FP Res FP D0 401 3 Channel Before 1001000000000000 Module FP D0 401 modue 03 After 1001001000000000 Change Contact 07 changed to statusi NATIONAL INSTRUMENTS ae Module 00
75. 00 12 05 12 10 12 15 12 20 12 25 12 30 12 35 12 40 12 45 time Figure 132 Analogue input ranges Note Alarm values are given in pairs Both maximum and minimum alarms are set and reset with different values This was implemented to prevent continuous switching between set and reset when measured values are in the neighborhood of alarm values e Left click in the status zone of an analogue contact to display the currently measured value e If a measured value generates a maximum or minimum alarm boundary the Change area of the interface is updated Digital input discrete input When you select a digital input module FP DI 300 FP DI 301 or FP DI 330 a window appears similar to the one shown in Figure 133 Digital Input module information on page 185 For each module a graphical display shows the available contacts A grey rectangle indicates a discrete input value is Off a green rectangle indicates a discrete input value is On 184 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Digital output discrete output 42 eIO SOPHO Messenger Net v2 0 6 eKernel elO Logra Connections 0 02 03 04 05 06 OF 08 E SP Pe A E S A E Pel FP oz FP DI 300 URL ope National Instruments OPCFieldPoint FP Res FP DI 330 2 Channel Before J 00000000 Module JFP DI 300 module 02 Alter 00000000 Change NATIONAL INSTRUMENTS ae Module 00 Contact
76. 005 Express SQL Server 2000 Desktop Engine MSDE or an external SQL 2000 or 2005 server The Messenger_CFG mdb contains several tables and defines the configuration of the DECT Messenger software These tables determine the behavior of the product The Messenger_data mdb contains several tables and are an internal work space of DECT Messenger Some models such as eKERNEL access this database heavily Avaya recommends that you avoid using the data database except for problem determination and recovery services TCP Connections The eKERNEL acts as a TCP Server and typically listens to several ports You can configure the TCP clients in the configuration database The status of each connection is visible on the screen of the eKERNEL application In normal operation an active connection is indicated by the color green A client that is not connected is indicated by the color yellow Other colors indicate an intermediate state or an error condition Logging You can log every event to ASCII log files and on the screen The on screen buffer is limited to 100 records To see details double clicking on the log records The log files are commonly stored in the directory specified in the CFG_Log_path_str field of the eKERNEL_ site table If CFG_Log_path_str C SOPHO Messenger net all log files are stored in the C SOPHO Messenger Net log eKERNEL directory Each day a new log file is created at midnight 196 DECT Messenger Installation
77. 007 18 38 31 I COM RS 06 06 2007 18 38 31 I COM 6 06 06 2007 18 38 31 I COM US 06 06 2007 18 38 31 I COM 1 06 06 2007 18 38 31 I COM ETE 06 06 2007 18 38 31 I COM 06 06 2007 18 38 31 S INF Processing of received data SOH 1 STX 1 US GROEPB 3 RS 2 US T6 ASYSTOLIE HF 0 Marie 343 1 Masschelein RS 4 US 3 RS 3 USJ1 RS 6 USJ1 ETX 06 06 2007 18 38 31 0 COM ACK 06 06 2007 18 38 31 0 TCP lt xml gt lt msgrqs gt lt set_or_reset gt SET lt set_or_reset gt lt msqg gt T6 xx x ASYSTOLIE HF 0 Marie 343 1 Masschelein lt msg gt lt alarmdescr gt T lt alarmdescr gt lt group gt GROEPB 3 lt group gt lt remov e_afte r gt SENT lt remove_after gt lt msgrqs gt lt xml gt 06 06 2007 18 38 34 I COM EOT DECT Messenger Installation and Commissioning Book 1 March 2012 131 Module eESPA 132 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 16 Module eESPA sample MASTER address 1 SLAVE address 2 No data to be transferred 2ENQ LS ES EOT Master has data to be transferred 1ENQ I want to send something BS 2ENQ Destination address ES ES ACK I am ready to receive data Data Block1 LS ES 1NAK Data Block1 ES ES ACK EOT BS ES EOT 2ENQ polling BS Master has data to be transferred Slave is not ready to receive data
78. 01 Connecting Parsing URL 25 10 2001 10 41 37 S TCP FP AI 100 module 01 contact 01 Connecting Connecting to OPC Server 25 10 2001 10 41 38 S TCP FP AI 100 module 01 contact 01 Active Connected to OPC Serv er 25 10 2001 10 41 39 S TCP FP DI 300 module 02 contact 01 Connecting Parsing URL 25 10 2001 10 41 39 S TCP FP DI 300 module 02 contact 01 Connecting Connecting to OPC Server 25 10 2001 10 41 39 S TCP FP DI 300 module 02 contact 01 Active Connected to OPC Serv er 25 10 2001 10 41 39 S TCP FP DO 401 module 03 contact 01 Connecting Parsing URL 25 10 2001 10 41 39 S TCP FP DO 401 module 03 contact 01 Connecting Connecting to OPC Server 25 10 2001 10 41 39 S TCP FP DO 401 module 03 contact 01 Active Connected to OPC Serv er Figure 138 Log example Binding to OPC Servers 25 10 2001 10 42 47 O TCP lt xml gt lt msgrqs gt lt type gt DI lt type gt lt module gt 02 lt mod ule gt lt contact gt 01 lt contact gt lt sts gt 1 lt sts gt lt msgrqs gt lt xml gt Figure 139 Log example Message Request 25 10 2001 10 41 59 O TCP lt xml gt lt pgmsts gt lt value gt Shutdown lt value gt lt pgmsts gt lt xml gt 25 10 2001 10 41 59 S INF Application ended Figure 140 Log example Termination DECT Messenger Installation and Commissioning Book 1 March 2012 189 Module elO 190 DECT Messenger Installation and
79. 1 Event code MSB LSB Event description g Fire reset y ll faults cleared x ll disablements cleared Alarms silenced 7 Alarms sounded Supervisory on Supervisory off Fault System Fault Outstanding Loop Disablement Fire 0 X Super Fire Byte 25 56 Outstanding Zole Supervisory Panel label RR Bd N e oT om Gon Figure 60 GENT Model 3400 The message is retrieved from bytes 25 to 56 The group is always FIRE and the alarm description is always FIRE Alarms are SET with the option remove after sent DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 Model VIGILIN EN54 Model VIGILIN EN54 Time 14 38 35 Thu 29 June 2006 Call Point Operated MCP FAP 1 BLOCK 2 LOWER GROUND FLOOR Z Number 149 on Loop 1 Sector 1 Group 1 Zone 1 Time 14 38 35 Thu 29 June 2006 Call Point Operated MCP FAP 1 BLOCK 2 LOWER GROUND FLOOR Z Number 149 on Loop 1 Sector 1 Group 1 Zone 1 Time 14 38 35 Thu 29 June 2006 Call Point Operated MCP FAP 1 BLOCK 2 LOWER GROUND FLOOR Z Number 149 on Loop 1 Sector 1 Group 1 Zone 1 Time 14 38 35 Thu 29 June 2006 Call Point Operated FIRE FAP 1 BLOCK 2 LOWER GROUND FLOOR Z Number 149 on Loop 1 Sector 1 Group 1 Zone 1 Figure 61 Sample Model VIGILIN EN54 Currently only records starting in 3rd line MCP or FIRE are processed For FIRE alarms the group is FIRE and the alarm description is FIRE Messages are sent w
80. 13 010 00000 AT CMGF 1 0131 00000 012 010 0K 012 010 00000 AT CPMS 0131 00000 013 010 CDMS BH HE SM HE SM 012 012 010 0K 012 010 00000 AT CPMS ME NE ME 013 00000 013 010 4 CDMS ME 0 50 HE 0 0 NE 0 S0 013 1013 010 OK 013 010 00000 Initvialisation completed normally 00000 AT CMCL 013 I 00000 013 010 0K 013 010 SCRHOHOHOHSOHOHROHSOH OMG O o a a PD 2005 by NEC Plies Unified Solutions Woensdag 20 december 206 1103 05 Figure 173 SMS_ service operational The module polls the box to find out if inbound messages are received from external mobile phones through the mobile network The logging file can feature the AT CMGL loop condition during the idle time eSMS module The support for SMS messaging is implemented with different processes The eKERNEL process integrates with eSMS process and eSMS process integrates with SMS_ service process This design is similar to other modules such as e amp KERNEL eDMSAPI CSTA_ service or eKERNEL eCSTA CSTA_ service At startup eSMS contacts the eKERNEL to request its configuration You configure the IP address and port in the shortcut When parameters are absent you are prompted for startup values DECT Messenger Installation and Commissioning Book 1 March 2012 227 Module eSMS eSMS SOPHO Messenger Net v4 0 0 Waring eSMS is
81. 16 discrete output channels Max 2A per output max 8A per module Maximum voltage 30VDC Note For each I O module one Terminal Base TB 1 is required 20 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com National Instruments Analog Digital Hardware The following figure shows an example of how a rail of National Instruments I O modules can be connected to DECT Messenger On a rail there can be various types of I O modules The maximum number of modules for each rail is 8 Important Although you can build configurations with many input or output modules there is a limitation on the number of input or output modules than an elO DECT Messenger module instance can handle One elO module can handle up to 8 input output modules So when you connect a 9th module even though it is recognized by National Instruments Measurement amp Automation Explorer it cannot be handled by the elO module DECT Messenger 24 VDC power P Y FP 1000 Al 100 DI 330 DO 401 TMT TNT TTT t__s inputs inputs outputs ER HUN eat a j 1mm Pad NS p V24 interface Figure 4 Example of an I O module connected to DECT Messenger Note The maximum number of contacts per elO Module in the DECT Messenger is 128 If necessary more than one rail can be connected to DECT Messenger The following figure shows an example configuration of three rails with National Instruments mo
82. 2012 163 Module eFR gj C Program Files Messenger Net Exe eFR aml Microsoft Internet Explorer provided by NEC agg ar Eile Edit Yiew Favorites Tools Help J x al A Search FE Favorites ge lt X Ee rel A Address E C Program Files Messenger Net Exe eFR xml is Go Links lt xml version 1 0 encoding utf 8 gt lt e8FR gt lt Monitoring interval 600 gt lt OM gt lt DISK gt lt PING gt lt Systems gt lt System id Loopback adcress 127 0 0 1 size 32 timeout 1000 gt lt System id iS3000 address 192 168 1 12 size 32 timeout 3000 gt lt Systems gt lt PING gt lt NETSTAT gt lt Monitoring gt lt Destinations gt lt eFR gt a yE 4 My Computer Al Figure 107 Monitoring type PING configuration The definition of a system that needs to be monitored with PING is done using a lt System gt line Figure 108 Monitoring type PING definition The following parameters are available e Define the parameter id with a unique identifier of the monitored item All items must have a unique identifier For example Lookback is an identifier Avaya recommends that you specify a name meaningful to you to make future maintenance easier For example specify names such as Mail Server Firewall Router IP DECT and so on e Define the parameter address to specify the IP address used in the PING test using ICMP protocol e Define the
83. 28 0 0 Case Else End Select Enc tf Only process if ekernel_outq is populated If lst_ekernel_outgq ListCount 0 Then Exit Sub Not yet connected If ip_ekernel State lt gt 7 Then On Error Resume Next Err 0 If ip_ekernel State lt gt sckClosed Then ip_ekernel Clos g_ekernel_local_address N A g_ekernel_local_port N A lab_ekernel_local_address amp g_ekernel_local_address lab_ekernel_local_port amp g_ekernel_local_port ip_ekernel RemoteHost g_ekernel_remote_address ip_ekernel RemotePort g_ekernel_remote_port ip_ekernel Connect DoEvents Eie Slo Omueths Orem OOum 0 Ene Lf Connected g_ekernel_local_address ip_ekernel LocalIP g_ekernel_local_port ip_ekernel LocalPort lab_ekernel_local_address amp g_ekernel_local_address lab_ekernel_local_port amp g_ekernel_local_port Handle requests in ekernel jobqueue 76 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 While lst_ekernel_jobq ListCount gt 0 process_ekernel_jobq lst_ekernel_jobq List 0 lst_ekernel_jobq RemovelItem 0 eAPI_form 6 Wend Handle requests in ekernel outq On Error Resume Next Err 0 Do While lst_ekernel_outq ListCount gt 0 lcl_o lst_ekernel_outq List 0 HomekerncimocmellD ait quel Gimme et mC nian il mete Claacou dO If Err Then laD mec maros ee WIE ISIS NCte Moe sL IM LOG Ege EAR S
84. 29 17 37 18 t4xml gt lt nusgrpy gt lt id gt POLLING lt id gt lt board gt 00 lt board gt lt extension gt 5006 lt extension Locooosoo9 LOC1015009 112008 07 29 17 35 54 Locooosool LOC1015001 112008 07 29 17 36 22 HOHOOHOOH LOC101S009 112008 07 29 17 35 54 PBB Data arrival 33 bytes received from DCC o2 1738235 amp Figure 156 Logging panel Architecture There are several steps involved to make eLOCATION operational The effected items in the setup of the functionality follow One special number with LA type should be defined in the eDMSAPI module in the eDMSAPI_INBOUND table i e number 112 or 911 In the following figure eCONFIG is used to illustrate the configuration process 212 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Architecture eCONHIG Avaya DECT Messenger admin LOCAL 5 Avaya DECT Messenger Import Export E ba License information E E Site Site 1 Areas 8 Modules F eaPl H eASYNC eBACKUP Ga eDMSAPI area DECT E a eDMSAPI area SIP DECT MEF Alarm 6 Group Inbound configuratior 8 Inbound data calls E a eDMSAPI area SIP DECT Sys E eESPA a eGUARDIAN HA e0 Eh eLOCATION eLOCATION area DECT i eLOCATION area SIP DECT bY L omm bere a Request information received f 15 46 38 Figure 157 eConfig illustrates the config
85. 52_ COM _A0103Y1A_ COM _00104225091 1NUR PALIY52_ COM _A0104Y1D_ COM _T01041250915F_ COM _A0104Y1D_ COM _T01041250915F_ COM _A0104Y1D_ COM _00105225091 1NUR PALIY53_ COM _A0105Y1C_ OHHOHOODOHHOHOOH Figure 64 Sample Televic protocol data Televic is an extended two direction protocol which provides a number of protocol rules to keep the communication secure for example through sequencing each packet requesting acknowledge string handshake through clear string return of feedback on message delivery through what is called terugmelding string error detection through checksum and so on Refer to the protocol specifications for details on Televic protocol Regarding configuration the following details are important The datastream contains a pager indication This pager indication is used as a group indication Alarms can either be sent as type 1 SET of an alarm that has a RESET type 0 type 0 RESET of an alarm that was previously SET through code 1 and finally a type 2 SET of an alarm that does receive a RESET As a result messages can be SET or RESET with remove after SENT or remove after RESET The DECT Messenger implements three distinct alarm descriptions 1 The highest priority is assigned to alarm types that are configured through the specified length L xx of the alarm text For example L 03 NUR ASS SAN REA MUG and so on If this definition is found the alarm attributes are
86. 88 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 13 Module eBACKUP You can use the eBACKUP module to make a backup of a predefined list of files The eBACKUP exe must be started from a shortcut which provides a number of command line parameters Figure 47 eBACKUP shortcut with required line parameters on page 89 shows an example of a shortcut with the required command line parameters C SOPHO Messenger Net Exe eBACKUP exe Path C SOPHO Messenger Net Log drive C Site 1 Batch N Figure 47 eBACKUP shortcut with required line parameters The following keywords are available e Path specifies the default path where the MDB subdirectory resides e Log drive specifies the letter of the drive in which logging information resides e Site specifies the site identifier to be saved e Batch specifies whether the application runs in interactively or in batch In batch mode you do not need to click the Backup site Close button to close the program after execution Batch is typically used in environments in which automated backup is scheduled at set intervals You can use the eBACKUP application to back up the files that are configured in the BACKUP table of the configuration database Table 4 eBACKUP sample data on page 89 shows sample data Table 4 eBACKUP sample data Si From path From file To path To file te 3 C Php php ini
87. 9990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 19990329 Figure 66 Sample DE LICHTERVELDE protocol data 11 11 11 11 Lis ais 1i 11 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 58 29 R 29 R 29 R 47 R 47 R 47 R 47 R 27 R 27 R 27 R 27 R 34 R 34 R 34 R 34 R 59 R 59 R 59 R 59 R 06 R 06 R 06 R 06 R 58 58 58 59 59 59 59 08 08 08 08 08 08 08 08 08 08 08 08 eat 21 21 21 21 D HOOFDBORD CENTR L707 Z 043 D 0945 29 03 99 11 59 DET FOUT S GENERAL RESET S 9130 29 03 99 12 00 SYS FOUT S GENERAL RESET S 9130 29 03 99 12 09 SYS FOUT S GEEN PAPIER MEER 9098 29 03 99 12 09 SYS FOUT S BUZZER RESET 9131 29 03 99 12 09 SYS FOUT D GANG G710 Z 043 D 0931 29 03 99 12 21 DET FOUT DECT Messenger Installation and Commissioning Book 1 March 2012 113 Module eCAP 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 19981117 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 05 05 05 05 05 05 05 06 06 06 06 06 14 14 14 30 30 30 14 14 14 14 16 16 16
88. A E AI OOA A A A eisai dadetnasiiudentins 196 Monu opio onae N 197 AETA 21 gt EE E T E T AEE E A E E E 197 RATAN AEE A E T E E E E E A E tne E E T 198 Ghapter 22 Module LICENSE rrisnin esni kennimanna aaiae 201 Goens mechani Miria a a racine caaleatuc cua 201 Seidla e A E E E E S 201 MANN sha SLE EN Easa eaa E E AE a E N esau dE ES 201 R n module e LICENSE srisrieiisieircinn roai An airi 202 APOVNO ME KIY aicina iian SO A Tar eer Tren y FT opp Ter 204 Disaster TOCSY osc tacdirensetaiainoassiancdinenntt ined icoan seca dincanta aes dizeantetesdiceence aa 204 DECT Messenger Installation and Commissioning Book 1 March 2012 5 Chapter 23 Module GLOCAT ION vsicisisncsetasrtascsesesnavsnevavssennisneenssianetheisannsasiernneniaaemins 207 DAN SAMO AEA EA E E A A EAEE E EAO AA E IAEE E nen 207 Programi ACHYRA 210 PCS ci aan A Renae 212 Ghapter 24 Module e SM9 sss natindsiasndsstipiiananisininisindiuadinsdianaaedddpiensiaceneipibiaianediandinddaadannns 223 POPU g e N EE E E EAE Y E EA E A PEA E A E EEEE TEA AEE A ene 223 Siemens TC3S MOGUC sisii aaie aia i a AEE a i aE Eaa 223 SMS SEVO seo i E E PE 224 l TE aw cose ET E AEA AE E seen E A AE TEE A A N R E E C A AER N 227 bound NSS RING iai a R 230 PAU MESS aM adna a a EA 232 Boli e DIE E1 PEE coca EE E E E E E E E E E E E E aeesehntes 234 Wep SASS ia R a 239 NOES E EE E E EAEE E E EE EEE E EE E E EE 243 6 DECT Messenger Installation and Commissioning Book 1 March 2012 Ch
89. ATION 4 w Active Request ID Board J Timeout Extension History EE Data arrival 223 bytes received from eKERNEL 00043 18 40 52 8 Figure 154 Idle state of system at startup After the processing of a location request the panels are updated as shown in the following figure g eLOCATION SOPHO Messenger Net v4 0 0 eKERNEL eLOCATION eLOCATION gt Active Request ID Board Timeout dEwtension Board 00 Extension 5001 RPN 11 Date 2008 07 29 Time 17 31 25 Board 00 Extension 5006 APN 11 Date 2008 07 29 Time 17 27 24 Board 00 Extension 5009 APN 11 Date 2008 07 29 Time 17 30 53 GB Data arrival 33 bytes received from DCC J o0039 7325 amp Figure 155 eLocation updated panels The history panel keeps track of all location request results In the previous figure several requests with positive feedback are presented in a history tab The logging panel in the following figure illustrates the detailed data exchange with the DAP Controller for the previous requests DECT Messenger Installation and Commissioning Book 1 March 2012 211 Module eLOCATION H eLOCATION SOPHO Messenger Net v4 0 0 eKERNEL eLOCATION Logging eLOCATION LOC1015001 112008 07 29 17 36 22 lt xml gt lt msgrpy gt lt id gt POLLING lt id gt lt board gt 00 lt board gt lt extension gt S5001 lt extension gt Locoooso06 L0C1015006 112008 07
90. AVAYA DECT Messenger Installation and Commissioning Book 1 Avaya Communication Server 1000 7 5 NN43120 301 03 02 March 2012 2012 Avaya Inc All Rights Reserved Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing Avaya assumes no liability for any errors Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information operating instructions and performance specifications that Avaya generally makes available to users of its products Documentation does not include marketing materials Avaya shall not be responsible for any modifications additions or deletions to the original published version of documentation unless such modifications additions or deletions were performed by Avaya End User agrees to indemnify and hold harmless Avaya Avaya s agents servants and employees against all claims lawsuits demands and judgments arising out of or in connection with subsequent modifications additions or deletions to this documentation to the extent made by End User Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this si
91. C Temp weekday php php ini 3 C Program Files Apache httpd conf C Temp weekday Program httpd conf group Apache conf Files Apache Group Apache conf 3 C SOPHO Messenger Net csta dll C Temp weekday SOPH O csta dll Exe Messenger Net Exe 3 C SOPHO Messenger Net CSTA_Service ex C Temp weekday SOPH O CSTA_Service Exe e Messenger Net Exe exe DECT Messenger Installation and Commissioning Book 1 March 2012 89 Module eBACKUP Si From path From file To path To file te 3 C SOPHO Messenger Net eAPI exe C Temp weekday SOPH O eAPI exe Exe Messenger Net Exe 3 C SOPHO Messenger Net eASYNC exe C Temp weekday SOPH O eASYNC exe Exe Messenger Net Exe 3 C SOPHO Messenger Net eBACKUP exe C Temp weekday SOPH O eBACKUP exe Exe Messenger Net Exe 3 C SOPHO Messenger Net eCAP exe C Temp weekday SOPH O eCAP exe Exe Messenger Net Exe 3 C SOPHO Messenger Net eDMSAPI exe C Temp weekday SOPH O eDMSAPI exe Exe Messenger Net Exe 3 C SOPHO Messenger Net eGRID exe C Temp weekday SOPH O eGRID exe Exe Messenger Net Exe 3 C SOPHO Messenger Net elO exe C Temp weekday SOPH O elO exe Exe Messenger Net Exe 3 C SOPHO Messenger Net eKERNEL exe C Temp weekday SOPH O eKERNEL exe Exe Messenger Net Exe 3 C SOPHO Messenger Net eSMTP exe C Temp weekday SOPH O eSMTP exe Exe Messenger Net Exe
92. Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 21 Module eKERNEL General eKERNEL is the core engine of the DECT Messenger and is in the basic implementation the only module that accesses the database The eKERNEL receives information from various input sources and exchanges information with various output sources Communication with eKERNEL is performed through TCP IP stream sockets where the eKERNEL acts as a server The other modules that communicate to the eKERNEL act as clients All data streams are formatted in XML format and are delimited with an lt xml gt start tag and an lt xml gt end tag followed by CHR 13 and CHR 10 Within these tags a number of keywords are embedded with their appropriated values In short the eKERNEL is the central engine of the DECT Messenger and controls the functioning of all the other modules Figure 141 eKERNEL interface on page 191 shows the eKERNEL interface CD ORERNEL SOPHO Messenger cNet v4 0 0 aoe Ele sHERNEL Sie 7 REC Pigs Pah lOG OC SSOPHO MercengeGine B Pakao eSOFHD hmr Ares 1 Hiversun Seats on FOX Sewer 192180112 not Keep open 120 Cheek THS2T8R172 F686 ckConnected IDMSA Derse S PERSE Locana I veals tc for que appl re DHSA IS Japplyvraterl lt xitersictgraey lt sal O sumlecctgrpyrcsene_cnt gt 20sssaso cnu gt smsy_dly gt s lt rase Gly gt lt cete api ad reserii 02211 eSMTP
93. DECT Messenger Installation and Commissioning Book 1 March 2012 115 Module eCAP All alarms are SET with remove after RESET When GENERAL RESET occurs in the datastream all active alarms for the VSK input program are reset for all groups Small differences between the three models are found for example in the level of detail in the messages that are sent for example FOUT BRANDCENTRALE in DE LICHTERVELDE VSKFOUT in ST JOZEF and all details in OLV VAN VREDER Also fire alarm messages are formatted slightly differently between the models BRAND or BR xxxxx where xxxxx denotes a location Note Use of this protocol usually requires consulting services and customizing WORMALD The valid manufacturer is WORMALD and the valid model is BASE L xx new in release 2 9 11 or G xxxx new in release 3 1 Wormald is based upon installation Alexianen Bouchout and RUCA Antwerpen and is compatible with both versions through automatic protocol recognition programming The model L xx defines the group The model BASE identifies the group WORMALD_F or WORMALD P depending on the type of alarm see the examples Table 9 Alexianen on page 116 and Table 12 RUCA on page 118 If the model L xx the first xx characters of the message define the group The model G xxxx is new in release 3 1 0 and defines the group used for all the alarms The group is xxxx for example in G EIPM no message is sent to the group EIPM If th
94. IE Called dev_str eDMSAPIIE_Calling dev_str eDMSAPIIE Ala id PBX license Messenger gt BIF ALL Guarding polling interval 60 Guarding retry interval 20 i Message delay 3 General timeout 15 gt Timeout for second acknowledge 30 Datapath delay 2 i eCSTA area for QD 2 Comments SIP DECT Auto create group False 4 Default output program eDMSAPI Default output program facility C933 Input program description SIP DECT Input program comments SIP DECT amp Inbound data call handling gt gt gt Module eDMSAPI Inbound B Module eDMSAPI Inbound Event i gt gt gt Module eDMSAPI Inbound Result amp Interface with eKERNEL Delete Refresh OK Cancel Figure 159 Module eDMSAPI inbound event The following figure illustrates detailed configuration for a special number in eDMSAPI_INBOUND_EVENT table DECT Messenger Installation and Commissioning Book 1 March 2012 215 Module eLOCATION Module eDMSAPI Inbound Event xj SitelD 1 Called device realD 2 fiz Calling device ALL Alarm ID for normal messages 1290101 Browse Alarm ID for urgent messages 1290102 Comments Default configuration 8 Called device The curent value for this parameter is 112 Delete Refresh OK Cancel Figure 160 Module eDMSAPI inbound event detailed configuration e Next the eKERNEL modul
95. 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 e eLICENSE e eLOCATION eSMS e eSNMP e eVBVOICE The eFR module is an add on module and is licensed separately through the eLICENSE module Some of the modules listed in this attention box are available only on a site specific basis Introduction Module eFR is a Windows based software module that monitors a number of items The letters FR in Module eFR stand for fault reporting The eFR module can run standalone or can run in an environment powered by DECT Messenger When DECT Messenger infrastructure is available additional functionality becomes available Basic overview The eFR module consists of two major parts monitoring and notification DECT Messenger Installation and Commissioning Book 1 March 2012 147 Module eFR Overview of monitoring The monitoring section covers four items e OM section The OM section is not applicable for traditional and SIP DECT systems e DISK section The DISK section verifies the state of a hard disk drive and notifies you on whether the disk drive is ready or not how much disk space is available The status information is compared with a previous run for the sa
96. J il rm External loRegister available 1 20 10 3 7 Local 10 110 50 140 2010 Seats required 14 Status sckListening Guarding polling interval 60 Retry interval 20 m ESTA service CE _L Semice 10 110 50 140 59000 General timeout al PBX Tio7io49171 ones SecondACKtmet 30 ETHERNET IS3000 Logpath TCAS0PHO Messenger Net SSO Status Connected Flog days 14 KeepAliveinteval 60 OO16 J IB Data arrival 127 bytes received from CSTA Poo 135335 amp Figure 84 eDMSAPI Connections In the left panel of the window shown in Figure 84 eDMSAPI Connections on page 137 the configuration and state of the different socket connections is shown On the right side the configuration parameters received lt cfgrpy gt from the eKernel are shown Note When the eDMSAPI functionality is not licensed the eKernel sends the following configuration reply lt xml gt lt cfgrpy gt lt license gt NO LICENSE AVAILABLE lt license gt lt cfgrpy gt lt xml gt After sending this reply to eDMSAPI the port through which the eDMSAPI is communicating is closed on the eKernel side DECT Messenger Installation and Commissioning Book 1 March 2012 137 Module eDMSAPI eDMSAPI SOPHO Messenger Net 2 8 0 a iol x eKernel CSTA eDMSAPI ekKernel lt msqrqs gt Extermal amp eKerel 10 seats available Dect 861 16 22 22 5565 SendDa
97. M COM COM COM COM COM COM COM COM COM COH COM COM COM COM COM COM COM COM COM CON COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM COM EOT 2 ENQ EOT ENQ 2 ENQ ACK SOH 1 STE 1 US G RS US BDH rv r H ODMoOwW Wm MHP OHUHUM Yr amp Oo ROR DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 Manufacturer ESPA and model VSK 06 06 2007 18 38 31 I COM 3 06 06 2007 18 38 31 I COM 4 06 06 2007 18 38 31 I COM 3 06 06 2007 18 38 31 I COM 06 06 2007 18 38 31 I COM 1 06 06 2007 18 38 31 I COM 06 06 2007 18 38 31 I COM M 06 06 2007 18 38 31 I COM a 06 06 2007 18 38 31 I COM s 06 06 2007 18 38 31 I COM c 06 06 2007 18 38 31 I COM h 06 06 2007 18 38 31 I COM e 06 06 2007 18 38 31 I COM 1 06 06 2007 18 38 31 I COM e 06 06 2007 18 38 31 I COM i 06 06 2007 18 38 31 I COM n 06 06 2007 18 38 31 I COM RS 06 06 2007 18 38 31 I COM 4 06 06 2007 18 38 31 I COM US 06 06 2007 18 38 31 I COM 3 06 06 2007 18 38 31 I COM RS 06 06 2007 18 38 31 I COM 3 06 06 2007 18 38 31 I COM US 06 06 2007 18 38 31 I COM 1 06 06 2
98. Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Architecture E eLOCATION INBOUND RESULT E Genera Input program eDMSAPI Message Called device 112 sos from calling number on location location Calling device ALL Site ID eLOCATION module 1 ArealD eLOCATION module 2 Group name 3000 E Message SOS from calling number on locatio Comments Default eLOCATION_INBOUND_R amp Message The current value for this parameter is SOS from calling number on location i Delete Refresh OK Cancel Figure 166 eLOCATION inbound result SOS message from eDMSAPI The following figure shows an example of a message sent to the group as defined in the Message parameter SOS from calling number on location location at location time Figure 167 SOS message sent to group The eKERNEL parses the data stream and performs the appropriate replacements of the replacement values calling number location and location time Note The Site ID eLOCATION module equals 1 and the Area ID eLOCATION module equals 1 in the example shown in the previous figure The example indicates that the location request is resolved by the eLOCATION module site 1 and area 1 In DECT Messenger prior to release 2 9 10 the request is only forwarded to eLOCATION with matching site and area same for eDMSAPI and eLOCATION This means when eDM
99. N A Message isiu Kennan Link type RS232 Alarm description Poe p eESPA Resource COMot Call ype 4 Port COMOT Settings 9600 N 8 1 Nmbr of transm 5 Senos 0n eon a o 8 Stus Opn Ma Timeout seconds 10 7 Remove after SENT flogpath CAS0PHO Messenger Net 0 flogdys OoOO SSS O Received Local adress 2 External address 1 Last msg J Sent J Status J oy J Data arrival 693 bytes received from eKERNEL 00004 16 41 03 E Figure 71 eESPA Connection tab showing a valid configuration Because the eESPA is designed to handle serial data communications with a number of paging systems the eESPA must be configured before use These values are returned through the lt cfgrpy gt reply that is sent on return of the lt cfgrqs gt request Note The values shown in Figure 71 eESPA Connection tab showing a valid configuration on page 122 are retrieved from the DECT Messenger database from the KERNEL_INPGM table and from the eESPA eESPA_ OUTBOUND CFG and the eKERNEL SITE tables At start up the eESPA exe appears the specified COM port with the specified settings Note The COM port you identify must be available and you must specify a valid baud rate and so on As well a physical connection between the specified COM port and the external paging system must be available which requires a serial cable In most cases you can u
100. OTHER THAN AVAYA AN AVAYAAFFILIATE OR AN AVAYA AUTHORIZED RESELLER AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE BY INSTALLING DOWNLOADING OR USING THE SOFTWARE OR AUTHORIZING OTHERS TO DO SO YOU ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING DOWNLOADING OR USING THE SOFTWARE HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC OR THE APPLICABLE AVAYA AFFILIATE AVAYA 2 DECT Messenger Installation and Commissioning Book 1 Copyright Except where expressly stated otherwise no use should be made of materials on this site the Documentation Software or Hardware provided by Avaya All content on this site the documentation and the Product provided by Avaya including the selection arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases You may not modify copy reproduce republish upload post transmit or distribute in any way any content in whole or in part including any code and software unless expressly authorized by Avaya Unauthorized reproduction transmission dissemination storage and or use without the express written consent of Avaya can be
101. Outbound HTTP port Outbound HTTP sockets Outbound XML port Outbound XML sockets Inbound interval Inbound XML address Inbound XML port Inbound signatures Figure 170 SIEMENS TC35i ni 9600 n 8 1 Text 7 10 32473897171 32473897171 29082 Msg Messenger Msg Net Messenger Net Sample configuration Special circumstances exist where two instances of eSMS and SMS service and TC35i can be requested DECT Messenger Installation and Commissioning Book 1 March 2012 225 Module eSMS For example if you have a need for high level redundancy you can use SIM cards from two different mobile providers If one box of SIM card fails you can use the other box You setup a configuration to first send to devices on eSMS area 1 mobile provider 1 and if NACK occurs you use alternative devices defined on eSMS area 2 mobile provider 2 You alter the shortcuts referring to the desired configuration section shown in the following figure C SOPHO Messenger Net Exe SMS service exe System Module 1 C SOPHO Messenger Net Exe SMS_service exe System Module 1 Figure 171 Altered shortcuts The following figure shows the default configuration E SmS _service int Notepad Be Edt Fumat ex bake the sMs Please note ba not specify twice manufacturer Model Marufacturer model Default Systen module 1 Q dapth Local L port wica axe c an ba star command line paraneter
102. RNEL_GROUP table e The parameter alarm_descry refers to a configured alarm description defined in the eKERNEL_ALARM table e The parameter remove_after supports the following values SENT RESET or CALC Refer to the appropriate chapters of this document for more information on the tables Introduction to a sockets client Refer to the documentation of your development environment for more information on sockets programming The code sample shown in Figure 36 Sample socket client code on page 69 describes an introduction for beginner programmers on how to build a very simple Visual Basic program that contacts the DECT Messenger eKERNEL module and delivers a message request Note that the source code is provided for illustration only and does not include error recovery Creating a basic sockets client using Visual Basic Creating a basic sockets client using Visual Basic 1 Start Visual Basic and open a new project of Standard EXE type In the menu choose Project gt Components and add the Microsoft Winsock Control component to the project This component usually refers to C WINNT system32 MSWINSCK OCX 2 Drag a CommandButton control to the form You can use the default name Command1 3 Drag a Winsock control to the form You can use the default name Winsock1 4 Add the code shown in Figure 36 Sample socket client code on page 69 in the Private Sub Command1_ Click 5 Specify the correct IP address the IP address of
103. SAPI resides on site 1 area 1 only the configuration records in eLOCATION_INBOUND_RESULT with reference to site 1 and area 1 are used In DECT Messenger release 2 9 10 and in subsequent releases these requests are published to all available eLOCATION modules residing on the same site and the most recent location is used In this environment the matching definitions for the available areas must also be defined The possibility of using a visual DNR to a device in Messenger new field DEV _Visual_dnr_str in table eKERNEL_DEVICE for the replacement value calling DECT Messenger Installation and Commissioning Book 1 March 2012 221 Module eLOCATION number is introduced in release 3 0 In release 3 0 and subsequent releases when the system configuration configures a device with a visual DNR this DNR is used to format a message when it contains Calling number The end used is confronted with the visual DNR instead of the device id 222 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 24 Module eSMS Important Due to the ongoing development of the DECT Messenger product suite some modules that provide additional functionality may become available after the initial release of DECT Messenger 4 0 The following modules are described in this document but are not available at initial General Availability eFR e eLICENSE e eLOCATION eSMS e eSNMP e eVBVOICE
104. SOPHO Messenger Net Log At startup the eDMSAPI sends an XML string to eKERNEL requesting a configuration This step is needed for each module that interacts with eKERNEL because this approach allows central administration using a single database even if some client modules are located ona distributed machine lt xml gt lt cfgrqs gt lt appl gt eDMSAPI lt app1 gt lt site gt 1 lt site gt lt cfigrqs gt lt xml gt lt xml gt lt cfgrpy gt lt seat_cnt gt 20 lt seat_cnt gt lt msg_dly gt 3 lt msg_dly gt lt csta_api_address gt 10 110 50 140 lt csta_api_address gt lt csta_api_port gt 59000 lt csta_api_port gt lt external_seat_cnt gt 3 lt external_seat_cnt gt lt external_port gt 2010 lt external_port gt lt csta_pbx_address gt 10 110 49 171 lt csta_pbx_address gt lt csta_pbx_port gt 2555 lt csta_pbx_port gt lt csta_licence gt Messenger lt csta_licence gt lt guarding_intv gt 60 lt guarding_intv gt lt guarding_Retry_intv gt 20 lt guarding_Retry_intv gt lt eKernel_ Seat_cnt gt 10 lt eKernel_Seat_cnt gt lt GeneralTimeOut gt 15 lt GeneralTimeOut gt lt Ack2TimeOut gt 3 0 lt Ack2TimeOut gt lt DataPathDelay gt 2 lt DataPathDelay gt lt network gt ETHERNET_DMC lt network gt new in Msg Net R3 0 lt pbxtype gt DMC lt pbxtype gt new in Msg Net R3 0 lt IoReg_cnt gt 3 lt IoReg_cnt gt lt IoReg_0001 gt 863 lt IoReg_0001 gt lt IoReg_0002 gt 123 lt IoReg_0002 gt lt IoReg_0003 g
105. SQL Server and Windows Authentication 12 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Network information Network information Table 1 Network information Port Description 80 Port for HTTP traffic used by Web Administrator application 1433 Default SQL Server port when using SQL Server as database storage engine 3101 Default eKERNEL server port for eDMSAPI 3102 Default eKERNEL server port for eCAP Eldad 3103 Default eKERNEL server port for eCAP Televic 3104 Default eKERNEL server port for eCAP Generic 3105 Default KERNEL server port for eASYNC module 3106 Default eKERNEL server port for eVBVoice 3107 Default eKERNEL server port for eCSTA 3108 Default eKERNEL server port for elO 3109 Default eKERNEL server port for eWEB 3110 Default eKERNEL server port for eSMTP Server 3111 Default eKERNEL server port for eSMTP 3112 Default eKERNEL server port for eAPI 3113 Default eKERNEL server port for eESPA Master 3114 Default eKERNEL server port for eESPA Slave 3115 Default eKERNEL server port for LOCATION 3116 Default eKERNEL server port for eSNMP 3117 Default eKERNEL server port for eSMS 3118 Default eKERNEL server port for eNET 9000 Default KERNEL server port for eCONFIG DECT Messenger Insta
106. Sample socket client code on page 69 assumes the data is actually transmitted with the SendData and does not wait for the Winsock1_SendComplete event e The values for IP address and port are hard coded and users must be able to set them as parameters in a real word program e The values in the message request are hard coded and must be filled with actual alarm information and appropriate configured values as defined in the configuration database 68 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com More extended program Private Sub Commandi_ Click close the socket Winsock1 Close specify eKERNEL protocol ip addres and port hardcoded Winsock1 Protocol sckTCPProtocol Winsock1 RemoteHost 10 110 50 138 Winsock1 RemotePort 3204 connect to the eKERNEL server Winsock1 Connect we wait indefinitely until asynchronous connect before sending Do Select Case Winsockl1 State Case Is lt gt 7 DoEvents Case Else send the data when connect completes Winsock1 SendData lt xml gt lt msgrqs gt lt group gt 1 lt group gt lt alarmdescr gt 2 lt alarmdescr gt lt message gt 3 lt m essage gt lt set_or_reset gt set lt set_or_reset gt lt remove_after gt sent lt remove a fter gt lt msgrqs gt lt xml gt Chr 13 Chr 10 allow asynchronous event to complete to purge data DoEvents Exit Do End Select Loop close the socket Winsock1 Cl
107. Select and modify PBX address to match the IP address of your target device 6 Select and modify PBX port to match the port number of your target device 7 Select and modify the Seats count according to the number of seat licenses available in your PBX Note Ensure that the seat count number plus the seats required by module eCSTA is equal or lower than the maximum number of seats licensed on the target PBX Otherwise you will not be able to make a LRMS message call 8 Click OK to save the changes Adding a device You require devices to output alarm messages notifications received from input modules The following procedure describes how to add a device for sending alarm messages to DECT handsets You can repeat the same procedure for other device types You can also modify the sample devices installed by default with the product DECT Messenger Installation and Commissioning Book 1 March 2012 57 Getting started with DECT Messenger Adding a device 1 Expand the Site NEC node in the tree 2 Expand Groups and devices 3 Right click All devices and select New Device The device details screen appears as shown in the following figure Output program faciity Visual DNR Description Created on 29 03 1188 at 17 48 Browse Pincode Priosity 999 Retry count altemative device 30 Monito False 10 register False gt gt gt Altemative devices Remote access site False Remote access
108. T E E E E E 158 PRCA EAM woe DIS siari iE iE EEE A EEA AEEA E 160 Montano noe FIN Ser ae ere rr errr ee T AO 163 M ntarmg type NETS ITA Dee eee tire eine eer er anen Ome eee npr a ry eee ee err Serene eer er rere 166 BSL UDA aii TOF SEN ea aa rer t terre rent rer arerr en fry trey erre vrrreser ener rent rrr rer rererre terre r rrrrrnery tee 166 Bernier ota OP CNM acacia Rae ANA 168 Sampe SIN Bement ere oper e trpeege cnr E irene trea er er er resrrtrtr rer Cece tira reer fentr A 169 CGhapier 19 Module CAD iiiiiiecsesasaiiincntncensoanecasanariiossseniiasadasasnininubeladnissanenbennbiseeedandaad 171 Chapter 20 Module Gl srianan taaan i aia a oai 179 OVENI EW oriire Ea aaa a aa Ea ETE aAA OA OSERE 179 N N s EE E E A E A OE EA E O E E ET T N E E A TT 179 EO MOES einne e iaaa 182 AELS eie aao E aa es E A E E E E E E S 182 Dgtalinput raseras MOU esien a a eaae 184 Doig het OUT discretie GUIDO nir E AAE 185 Koreai ora a E E E E A A A A A E T 186 Chapter 21 Module GR ERB aiiccccssiciniccsicsannnaicsananasaaananadaneccksanuhsesheuntseeniwandaadasniunanadanunt 191 E E E E E E I A E A A E E A EE E E 191 LIGIER iuncreniae a tic staat aneasneedlaaeahaet ead aer rel aaae reaieas 192 Eguipment and Funcionaliy Models ienaa iA 193 BAP OME E E E E E E E A T 194 Eee aaee lae e e E A ind daca coh E E E E E EO A amanesacanaaes 194 External Mengt ES osnan Ni TeSatetle 195 Di aie a cic E E ER A A A E awed rei E E E T E TS 196 TP Connec na R E R 196 ENE O E E
109. Technology amp Services Belgium OK Figure 86 About CSTA service e You can use Kill all clients to disconnect all TCP connections for example the TCP IP connection to eCSTA Do not perform this function unless instructed to do so by service support e You can use End CSTA Service to close the CSTA_Service program Logging The eDMSAPI application provides logging to both the window and to logging files on disk You can view the on screen log through the Logging tab DECT Messenger Installation and Commissioning Book 1 March 2012 139 Module eDMSAPI a eDMSAPI SOPHO Messenger Net Figure 87 Logging information Sample logging data is shown in Figure 88 Log example initialization page 141 140 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Logging 03 10 2002 13 58 52 S INF Application eDMSAPI SOPHO Messenger Net v2 8 0 started with parameters Site 1 eKernel address LOCAL eKernel port 3101 Log drive c 03 10 2002 13 58 53 S INF TCP local port 01619 connected with remote port 03101 eKERNEL 03 10 2002 13 58 53 O TCP lt xml gt lt cfgrqs gt lt appl gt eDMSAPI lt appl gt lt site gt 1 lt site gt lt version gt 2 8 0 lt version gt lt cfgrqs gt lt xml gt PBX type DMC 28 06 2004 13 58 55 I TCP lt xml gt lt cfgrpy gt lt seat_cnt gt 20 lt seat_cnt gt lt msg_dly gt 3 lt msg_dly gt lt csta_api_address gt 10 110 50 140
110. Temp 4 SOPHO Messenger Net Exe eCAP exe completed normally 25 10 2001 16 06 22 S INF FileCopy C SOPHO Messenger Net Exe eDMSA PI exe C Temp 4 SOPHO Messenger Net Exe eDMSAPI exe completed nor mally 25 10 2001 16 06 23 S INF FileCopy C SOPHO Messen ger Net Exe eGRID exe C Temp 4 SOPHO Messenger Net Exe eGRID exe completed normally 25 10 2001 16 06 23 S INF FileCopy C SOPHO Messenger Net Exe eI0 exe C Temp 4 SOPHO Messenger Net Exe eIO exe ended abnormally 25 10 2001 16 06 23 S INF gt Error occured 25 10 2001 16 06 23 S INF FileCopy C SOPHO Messenger Net Exe eKER NEL exe C Temp 4 SOPHO Messenger Net Exe eKERNEL exe completed nor mally continued on next page Figure 51 Sample backup log 94 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 25 10 2001 16 06 23 S INF FileCopy C SOPHO Messenger Net Exe eS MTP exe C Temp 4 SOPHO Messenger Net Exe eSMTP exe completed normal ly 25 10 2001 16 06 23 S INF FileCopy C SOPHO Messen ger Net Exe eSMTP_server exe C Temp 4 SOPHO Messen ger Net Exe eSMTP_server exe completed normally 25 10 2001 16 06 23 S INF FileCopy C SOPHO Messen ger Net Exe omnithread_rt dll C Temp 4 SOPHO Messen ger Net Exe omnithread_rt dll completed normally 25 10 2001 16 06 23 S INF FileCopy C SOPHO Messen ger Net Mdb Messenger_CFG mdb C Temp 4 SOPHO Messen ger Net Mdb Messenger_CFG mdb comple
111. ZZYYYYYP LF CR e XXXX pager number e T Tone code e ZZ Alpha message usually 24 or 48 bytes e YYYYY 5 digit information message if ZZ are all e P present flag 20000419 00 00 45 20000419 00 00 45 20000419 00 01 35 20000419 00 01 35 20000419 00 03 38 I _01244ASS A203 00000P 20000419 00 03 38 O _ ACK I _01241NUR A203 00000P 0 I Oo I 0 20000419 00 03 50 I _01244ASS A203 00000P Oo I 0 I 0 _ ACK _01640NUR A203 00000P _ ACK 20000419 00 03 50 O _ ACK 20000419 00 07 09 I _01142TECHNISCH 00000P 20000419 00 07 09 O _ ACK 20000419 00 11 41 I _01643BRAND 00000P 20000419 00 11 41 O _ ACK Figure 59 Sample Eldad protocol data Eldad messages are either SET or RESET based upon tone code and model configuration The group is located from the datastream 4 byte pager number The message is retrieved from the alpha message but if the aloha message is a string of period characters then 5 byte digit information is used instead The alarm description is the tone code for example 1 or 2 or 3 and so on GENT The valid manufacturer is GENT and the valid model is 3400 and VIGILON EN54 DECT Messenger Installation and Commissioning Book 1 March 2012 105 Module eCAP Model 3400 The GENT model 3400 transmits binary datastreams of 56 bytes The first bytes identify the 106 alarm type Currently only Fire and Super Fire are processed Byte 0 and
112. _Click End Sub Private Olounc MmClan transmi eae Dia lell ssn As Siew sin eyword amp not available in amp xml amp Validate If Trim txt_group Then lab_msg Error Group must be entered txt_group SetFocus lapse Stio Enel TE If Trim txt_alarmdescr Then lab_msg Error Alarm description must be entered txt_alarmdescr SetFocus eAPI_form 2 Exit Sub EDE LE If Trim txt_msg Then lab_msg Error Message must be entered txt_msg SetFocus ISIE Suid Boe LE 1 Build XML string lcl_xml lt xml gt lt msgrqs gt lt site gt amp g_site amp lt site gt iel u lcl mnl lt setlon rest amp o0 set on racet amp lt setlor recet lcl_xml lcl_xml lt group gt amp Trim txt_group amp lt group gt lcl_xml lcl_xml lt alarmdescr gt amp Trim txt_alarmdescr amp lt alarmdescr gt lcl_xml lcl_xml lt msg gt amp Trim txt_msg amp lt msg gt lcl_xml lcl_xml lt remove_after gt amp cbho_remove_after amp lt remove_after gt lel smil lel saml lt msgrqs gt lt xml gt Submit request eAPI_form lst_ekernel_outq AddItem lcl_xml Inform user lab_msg Message submitted to eKERNEL End Sub Private Sub Form_QueryUnload Cancel A DAME HO wA Siesta tse Submit lt pgmsts gt shutdown request to s Integer UnloadMode As Integer kernel if connected On Error Resume Next Err 0 If i
113. a license for eASYNC is valid 82 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com eASYNC exe If the lt cfgrpy gt shown in Figure 39 eASYNC module receives this cfgrpy from the eKernel if no license is available for eASYNC on page 83 is received no license is available and the eASYNC module cannot connect to the eKernel module anymore lt xml gt lt cfgrpy gt lt licence gt No licence available gt lt licence gt lt cfgrpy gt lt xml gt Figure 39 eASYNC module receives this cfgrpy from the eKernel if no license is available for eASYNC The eASYNC Connections tab is shown in Figure 40 eASYNC Connections tab on page 83 EASYNC SOPHO Messenger Net 2 8 0 E lol xi eKernel e SYNC Loasa m eKernel Configuration local 10 110 50 140 1779 interface 2 L Epes Remote 10 110 50 140 3105 Portandsettings COM S600N817 Status Connected Type tC Provider and password KPN NONE Number andmodemint 0031653141414 iCTAT Retyintervalandcount 60 2 Port COMO E Settings 9600 N 8 1 EE CASOPHO Messenger Net Status Open LL S Hl 00012 1716 32 amp m e SYNC Figure 40 eASYNC Connections tab The eASYNC module receives message requests from eKERNEL After processing feedback is sent from eASYNC to eKERNEL Figure 41 Sampl
114. adapter is not responding lt Message gt lt Destinations gt lt Destination gt eSNMP lt Destination gt lt Destinations gt lt NotResponding gt lt Responding gt lt Message gt Loopback adapter is responding lt Message gt lt Destinations gt lt Destination gt eSNMP lt Destination gt lt Destinations gt lt Responding gt lt System gt Figure 109 Message sent after ICMP check Note You can use the PING command to verify the ability to perform an ICMP check prior to defining a system in the eFR xml configuration C WINDOWS system32 cmd exe 5 x C gt ping 127 0 0 1 n 1 1 32 inging 127 0 8 1 with 32 bytes of data Reply from 127 0 0 1 bytes 32 time lt ims TTL 128 Ping statistics for 127 6 0 1 Packets Sent 1 Received 1 Lost loss Approximate round trip times in milli seconds Minimum Gms Maximum Gms Average Gms CsN gt Figure 110 PING command verifying ability to perform ICMP check DECT Messenger Installation and Commissioning Book 1 March 2012 165 Module eFR Monitoring type NETSTAT You can verify the configured list of connections using the NETSTAT monitoring capability You can verify the TCP server connections in status LISTENING and you can verify the TCP client connections in status ESTABLISHED C Program Files Messenger Net Exe eFR xml Microsoft Internet Explorer provided by NEC Philips Unified Joey Ble Edt yew Fav
115. address 127 0 0 1 port 2525 domain nec philips com from francis missiaen nec philips com to francis missiaen nec philips com gt lt Destination id eSNMP type SNMP description Messenger Net address 127 0 0 1 port 162 community public oid 1 3 6 1 4 1 28088 32 1 generic 6 specific 1 gt lt Destination id eSMS type SMS description Francis Missiaen address 127 0 0 1 port 29081 extension 32473897171 gt lt Destinations gt lt eFR gt Z My Computer You can use the windows delivered with Notepad or Wordpad accessories maintain the XML file On the internet a number of free XML editors are available These tools typically feature syntax checking colored editing and advanced editing features including copy and pasting of nodes You can download the file XmINotepad msi XML Notepad 2007 on the Microsoft web site 2 Ensure that every destination has a unique value for the parameter id In the sample file in the previous figure the id values are eNET eSMTP eSNMP eSMS and so on The parameter id must be unique You can use identifiers that are more meaningful to you such as your name for example Francis Missiaen e mail or Francis Missiaen sms 3 Ensure that each destination has a unique value for the parameter type The current release supports the following values for parameter types e NET NET is used with NET SEND technology when you generate a Windows
116. ager window 3 Click Add Role The Add Roles Wizard opens Click Next to skip the opening screen 4 Check the Web Server IIS box in the list of available roles and click Next 5 Read the introductory information displayed and then click Next again to reach the Select Role Services wizard page 6 In the list of role services verify that the following options are checked a Web Server gt Application Development gt CGI b Management Tools gt IIS 6 Management Compatibility gt IIS 6 Metabase Compatibility 7 Click Next The Confirm Installation Selections page displays where you may review the components to be installed 8 Click Install to being the installation 9 When installation is completed click Close to close the wizard Adding the SMTP server feature To add the SMTP server feature do the following 1 Go to the Server Manager window automatically opens when the computer is started if not open right click on the My Computer icon on the desktop and select Manage 2 Inthe left pane select Features The right pane is updated with the server features currently installed 28 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Installing IIS 3 Click Add Features The Add Features Wizard window opens as shown in the following figure jk Add role services and features required for SMTP Servor w You cannot ndal SMTP Sarre udesi Ce requried iie
117. alled number and the physical location With this knowledge eKERNEL can resume processing A group of users is alerted with an alarm message in words not technical code that contains enough information to let the group of users know the geographical location of the alerting DECT user This is done using the eLOCATION_INBOUND_EVENT table as illustrated in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 219 Module eLOCATION 220 i Module eLOCATION o xi Site ID 1 Col eLOCIR_Inpgm_i Col eLOCIR Called_de Col eLOCIR Calling de Col_el Site description Site 1 Di 12901 112 ALL Area ID 2 Area description SIP DECT MERA i Location Agent address 192 168 32 10 Location Agent port 28008 i General timeout 10 i Retry count 5 lt 4 Retry interval 10 Polling interval 60 4 gt gt gt Board definition gt gt gt RPN definition 4 Comments eLOCATION configuration for SIP E amp Inbound call handling gt gt gt eCSTA inbound event gt gt gt eDMSAPI inbound event eLOCATION Inbound result New Edit Interface with eKERNEL E Delete Refresh OK Cancel Figure 165 eLOCATION_INBOUND_EVENT table In the sample in the following figure alarms from the eDMSAPI input program 12901 site 1 area 2 and all calling devices that called special extension 112 result in an alarm sent to group 3000 DECT
118. and Commissioning Book 1 March 2012 Comments infodev avaya com Menu options Menu options e File gt Exit This option closes the eKERNEL application e eKERNEL gt Reset all alarms This option clears all active alarms in the data database e eKERNEL gt Refresh logfiles This option closes and reopens the log file of the eKERNEL application Perform this action before opening the log file for the current day so all data that is still in memory is copied to the log file e Service gt Delete all data records This function deletes all the records of the selected table Perform this action to be sure you start with a clean data database at the customer Watchdog When the Watchdog facility is enabled an icon of adog is visible at the right top of the window as shown in Figure 145 Watchdog enabled on page 198 When active Watchdog sends the command string entered in the CFG_Watchdog_cmd_sitr field of the eKERNEL_SITE table to the connected com port The command string is sent every CFG_Watchdog_interval_n seconds DECT Messenger Installation and Commissioning Book 1 March 2012 197 Module eKERNEL six File eKernel Service Site 1 IBS TS template site LOG Path CASOPHO Messenger net a oe ee ee TCP Status CLIENT Info Area 1 IBS TS default area 1 Client 7011050140 3515 Keep open DMSAPI eKernel 10 110 50 140 3101 sckConnected 20 BASE Guarding T 0 NVA Logging I lt xml
119. apter 1 New in this release The following sections detail what s new in this document for Avaya Communication Server 1000 Release 7 5 e Features on page 7 e Revision history on page 7 Features There have been no updates to the feature descriptions in this document Revision history March 2012 November 2010 June 2010 November 2009 October 2008 September 2008 May 2008 Standard 03 02 This document is up issued to support Avaya Communication Server 1000 Release 7 5 and contains changes relating to updates to the Messenger software Standard 03 01 This document is up issued to support Avaya Communication Server 1000 Release 7 5 Standard 02 01 This document is up issued to support Avaya Communication Server 1000 Release 7 0 Standard 01 07 This document is up issued to support Communication Server 1000 Release 5 5 and contains clarifications relating to add on modules Standard 01 06 This document is up issued to support Communication Server 1000 Release 5 5 and contains changes relating to updates to the Messenger software Standard 01 02 This document is up issued to support Communication Server 1000 Release 5 5 and contains changes relating to updates to the Messenger software Standard 01 01 This document is issued to support Communication Server 1000 Release 5 5 Some of the information contained in this new document was previously contained in DECT Fundamentals NN43120 114 DECT
120. arding If lcl_guarding lt 0 Then lcl_guarding lcl_guarding 86400 If lab_guarding lt gt Format lcl_guarding 00000 Then lab_guarding Format lcl_guarding 00000 EDE LE Process ekernel process_ekernel Enable timer to resume processing tim Enabled True End Sub Private Sub txt_log_GotFocus ist_log SetFocus End Sub Submlo gio gmisyp cm As Gcrinecy log ste As String log cta As Hn ite taser cp Dim lcl_rc As Integer Check log_type Select Case log_type eAPI_form 7 Case I Case O Case S Case E Case Else lel ze MsgBox Invalid log type amp log_type IESE Suid End Select Check log_sts Select Case log_sts Case TCP Case COM Case INF Case ERR Case Else lcl_rc MsgBox Invalid log status amp log srs Exit Sub End Select 1 Ace log carte to Liiethiox lst_log AddItem log_type amp amp log_sts amp amp log_dta Do Wile lsr log bistteotrne gt 99 lIst_log RemoveItem 0 Loop ler log bistindes Llar log mistCemmne a 1 Add log data to logfile 1 do not log is g_log_days 0 If g_ekernel_remote_port Then Exit Sub build directory and file Dam Tele path As Strang Dim lel rile As SieiesiaG start error recovery On Error Resume Next Err 0 if specified drive is valid try to toggle between C drive and D drive cic 0 Dim lcl_chk As Integer lel cik Len Dir g_log_path vbDirectory Telmpath onog pa
121. as possible because during the delay time the application is inactive so high values can disrupt the operation of the system At start up the eESPA exe sends an XML string to eKERNEL exe requesting a configuration This step is needed for each module that interacts with eKERNEL exe because this approach allows central administration from a single database even if some client modules are located on a distributed machine DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com eESPA exe lt xml gt lt cfgrqs gt lt app1 gt eESPA lt app1 gt lt site gt 1 lt site gt lt cfgrqs gt lt xml gt lt xml gt lt cfgrpy gt lt resource gt COM01 lt resource gt lt settings gt 9600 N 8 1 lt settings gt lt link_type gt RS232 lt link_type gt lt ControlStation gt Y lt ControlStation gt lt polling_intv gt 300 lt polling_intv gt lt Polling_address_list gt 2 lt Polling_address_list gt lt localAddress gt 1 lt localAddress gt lt externalAddress gt 2 lt externalAddress gt lt dataId_Group gt 1 lt dataId_Group gt lt group_default gt eESPA lt group_default gt lt dataId_Msg gt 2 lt dataId_Msg gt lt msg_default gt Default ESPA msg lt msg_default gt lt dataId_Ala_descr gt 3 lt dataId_Ala_descr gt lt ala_descr_default gt 1 lt ala_descr_default gt lt remove_after gt RESET lt remove_after gt lt nak_retry_cnt gt 2 lt nak_retry_cnt gt lt timeout gt 600 l
122. asSe ssesssesonssoresnnnsnnosnnnnnnnnnn nanninannan annainne 7 KOT E E E E E E E E E E E icant tataieeketetnie 7 PoV ON T e teams sane mmiaana tes maGsaae Reade ee alasaa AARNE RARER 7 Chapter 2 TATED ck sistianceneeciitinntiindiansssadisascdsddandblulaiiadindnansdiatbiinladubisebbunidnubhiabbeebbins 9 Chapter 3 System POCquireiiG ss siiscoeecicisicticctancnntsasennianinanstasansiacanibebandiiseivansncsusaasauninananans 11 Supponed Bela st tcl gta Boas L210 cae ere eRe pee ai aaaeaii aiai ARAE 11 SP PC EOU rNestin a EA a EA Ake EEEE 11 Sa aae A a E A A pada a E E wenn iad A E AEE E 12 piora Nar Wai sca cst sh res date Coane sccaaie acacia ey thereat eect ace ee te aude Gy det tamed edd pLaeaete emia ean 12 DRS Da Se conor MOCUIN RTS E naa ane aR taTe 12 Pal Setanta a T EA E ba ae E E E E E mae tic Sao kbenalicdas Rian ealidduckbansuiadaeteamndieds 13 Chapter 4 Installation OU sists ntn aes nesedsnceeeiansnsinesesennnen inns cad ductdawandaaddnadannianndsnadansddnadiananne 15 Chapter 5 Preparing external AeVICES sssseeeeeeeeeeseeeeeeeeeenseeeeneeeeeeseeneeeeeeeeeeeeneneees 17 Date eon wiih I DECT MANGE sect sckcs coches tase cased hae eat ak dean eee eee a tne 17 National Instruments Analog Digital Hardware cccccceccceeeeeeeeeeeeaeeeeesaaeeeecaeeeeesaeeeeseaaaeeeeaaaeeeseneeeeeeaaes 19 FMA WSU SIO cases ctsaa crease sdacerebued anaE E Aias 23 SN i ISLS ANU he Lads hens eu denna d aioe sass San anstsited E E EE OE TEN
123. ase If there are errors copying the database a warning box prompts you to close all applications and retry DECT Messenger Installation and Commissioning Book 1 March 2012 61 Getting started with DECT Messenger 5 10 When the database is successfully published a message appears stating that the registry files necessary for eTM module are created as shown in the following figure eCONFIG Messenger Net v4 1 7 admin LOCAL The registry files are created in the directory C Program Files x86 NEC Messenger Net Please distribute the files if necessarily to the appropriate machines First manually delete the registry key Software NEC Messenger Net eTM in HKEY_CURRENT_USER Then double click on the reg file to merge the new configuration into the registry Finally restart the eTM module Figure 32 Successful publication window Open the registry editor Start menu gt Run e Type regedit Locate the HKEY_CURRENT_USER Software Avaya Avaya DECT Messenger eTM registry key and delete it Locate the registry file in the directory mentioned in the message by default c Program Files Avaya Avaya DECT Messenger Maintenance Registry Identify the file s corresponding to the DECT Messenger Server environment Check the file names they should be in the format eTM Site lt id gt Environment LOCAL reg Double click the registry file s to merge the i
124. at eAPI and eWEB are licensed properly eKERNEL checks these two functionality models individually If eAPI and eWEB are found in the License system the TCP IP ports for any clients of this kind are opened If no eAPI or eWeb functionality is available in the license system the ports are not opened and the eAPI or eWeb clients are not able to connect License maintenance Every 24 hours at midnight each client that is connected to the eKERNEL is checked to determine whether the license is still valid If the Application license eKERNEL program is expired eKERNEL sends a message to all of its clients and closes all of its ports so no client is able to reconnect After checking the Application license equipment and functionality models are checked for validation When installing a new license with more available equipment models or adding one of the functionality models eWeb or eAPI the eKERNEL must explicitly be told about the new license To tell eKERNEL about a new license use the menu command eKERNEL gt License gt Recheck license of all clients open port as shown in Figure 143 Rechecking licenses on page 194 Note eKERNEL makes this same check automatically at midnight Note that rechecking all licensing is a time consuming process pret File ekKernel Service Reset all alarms je LOG Path CAS Refresh Logfile Functionality gt TCP Status i CLIENT Figure 143 Rechecking licenses
125. ation system and all prerequisite conditions for named pipes messaging applies Install module eFR Follow the steps in the next procedure to install the software Installing module eFR 1 Double click the EXE files delivered by Avaya 2 Accept all defaults to install the software After installation a number of items ARE installed Program Progran Program Progran Progran Progran Program Program Program Program ESO ESO OOCL EO Files Messenger Net Exe eFR exe Files Messenger Net Exe eFR xml Files Messenger Net Mdb eFR mdb Files Messenger Net Exe MSWINSCK OCX Files Messenger Net Exe MSWINSCK OCX Files Messenger Net Exe TABCTL32 O0CX Files Messenger Net Exe MSCOMCTL OCX Files Messenger Net Pdf Module_eFR pdf Files Messenger Net Reg readme txt Files Messenger Net Reg eFR reg Launch module eFR Follow the steps in the next procedure to launch module eFR 150 The eFR module is implemented as a application and not as a service Launching module eFR 1 Logon to your PC Implementation as an application means you launch the EXE file after logon on the PC 2 Create a shortcut to the file eFR exe for example C Program Files Messenger Net Exe eFR exe 3 Drag the shortcut to the Startup menu of the user that logs on to the computer 4 Configure an automatic logon recommended Your ability to configure an automatic logon depends on your security policy When you hav
126. b 19 03 2001 19 03 2001 19 03 2001 19 03 2001 19 03 2001 19 03 2001 19 03 2001 19 03 2001 19 03 2001 19 03 2001 10 10 10 10 10 10 10 10 10 10 57 57 57 57 57 57 57 57 57 57 25 26 26 27 27 27 27 49 49 50 HHHHHHOON INF COMO02 opened with settings 9600 N 8 1 COM AT amp COS0 3 COM ATDT 00475161622 COM AT amp COS0 3 COM COM OK COM ATDT 00475161622 COM COM CONNECT 33600 V42bis O COM _01 00121 0 01 32475353215 proximus 3 534D5320746F2050726F78696D7573207769746820534F50484F204D657373656E67657 2404E6574 A3_ 19 03 2001 10 57 19 03 2001 10 57 19 03 2001 10 57 19 03 2001 10 57 sts gt lt msgrpy gt lt xml gt Figure 44 Sample logging data for SMS to PROXIMUS 54 54 55 755 I COM connected I COM _01 00019 R 01 A 69_ Ss O TCP lt xml gt lt msgrpy gt lt id gt 00002 lt id gt lt sts gt ACK lt INF Port closed DECT Messenger Installation and Commissioning Book 1 March 2012 85 Module eASYNC S INF COM03 opened with 02 05 2002 02 05 2002 02 05 2002 02 05 2002 02 05 2002 02 05 2002 02 05 2002 02 05 2002 02 05 2002 13 13 13 13 13 13 13 13 13 57 257 57 257 257 257 758 58 25S 37 O COM AT COM COM OK COM ATDT 00653141414 COM ATDT 00653141414 COM COM CONNECT 33600 V42bis Q 38 38 38 39 43 16 16 17 H HHHOHHAH s
127. both communications EDMSAPI is a TCP client software that connects to the two other components acting as TCP server software For external clients eWEB the eDMSAPI acts as a multiple socket server At start up eDMSAPI contacts the eKERNEL by means of a socket connection For the eDMSAPI module to locate the eKERNEL the eDMSAPI must start up with parameters that identify the eDMSAPI module and locate the eKERNEL program These parameters are provided to eDMSAPI in the Properties section of the shortcut that initiates eDMSAPI This shortcut is usually located in the Windows Startup group click Start on the Windows task bar and choose Programs gt Startup C SOPHO Messenger Net Exe eDMSAPI exe Site 1 eKernel port 3101 eKernel address LOCAL Log drive Cc Figure 82 Typical parameters in the shortcut In the example shown in Figure 82 Typical parameters in the shortcut on page 135 eDMSAPI identifies itself as belonging to Site 1 and specifies the location of eKERNEL through IP address LOCAL and port 3101 The special value LOCAL refers to the assigned IP address DECT Messenger Installation and Commissioning Book 1 March 2012 135 Module eDMSAPI of the first NIC adapter found in the PC You can determine the IP address using the IPCONFIG exe command or in the appropriate sections of the Windows network settings The keyword Log drive refers to the drive where the logging data must be stored usually this is C
128. bound_port gt lt sms_inbound_port gt 29080 lt sms_inbound_port gt lt ve rsion gt 2 9 10 lt version gt lt log_path gt C SOPHO Messengergnet lt log_path gt lt log_days gt 14 lt log_days gt lt cfgrpy gt lt xml gt Figure 176 Configuration exchange At startup the main screen appears shown in the following figure 228 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com eSMS module f WM is aiva 242 bytes received fiom EXERNEL Foose eros 8 Figure 177 eSMS Main screen The section on the left features outbound messaging and the section on the right features inbound messaging WW a arial 242 bytes received fiom KERNEL Joos aor 8 Figure 178 Inbound and outbound messaging The tab connections shows the details of the configuration received from the eKERNEL DECT Messenger Installation and Commissioning Book 1 March 2012 229 Module eSMS GI eSMS SOPHO Messenger Net v4 0 0 eKkernat SMS Help Logging Jcbq Actve Outbound iil I Inbound ram gt js ra j lt E BE daa aval 242 bytes received fiom KERNEL Joos 2047 B Figure 179 Configuration details in tab connections Outbound messaging The eSMS module can send outbound SMS messages to mobile phones It connects to the mobile world through an SMS box controlled by the SMS_service process The eSMS module contacts the SMS_ service proce
129. bound_port gt 29081 lt s TCP local port 01182 connected with remote port 29081 lt xml version 1 0 gt lt smsrequest gt lt destination gt 32479467238 lt destination gt lt mes SMS is sent lt xnl gt lt musgrpy gt lt id gt 00001 lt id gt lt sts gt ACK lt sts gt lt msgrpy gt lt xml gt TCP error 10061 Connection is forcefully rejected eSHS sqrpy gt lt id gt 00001 lt id gt lt sts gt NACK Permanent sockets error occ S S oO Ez S oO ze 0 E 1040 A E Send SMS ended abnormally Peimanent sockets eror occured 00011 21 44 03 Figure 183 Example of message delivery failure Inbound messaging The eSMS module also handles inbound SMS messages These messages are received on the GSM box and transferred to the eSMS module to be processed in DECT Messenger by eKERNEL For this purpose additional tables eSMS_INBOUND and eSMS_INBOUND result are added to the Messenger_CFG database The eSMS module communicates with the SMS_ service through a separate TCP connection The eSMS module acts as the TCP Server and the SMS _ service module acts as the TCP Client The eSMS is listening to a port for example 29080 for inbound messages requests from mobile phones In the current release of eSMS the inbound functionality can confirm alarms either based upon the calling line identifier or mobile phone extension number or based upon a pincode provided in the SMS message The following figur
130. cific trap identifier for example 1 TIP Contact the administrator of the SNMP trap receiver infrastructure In many cases this is the DECT Messenger administrator when the eSNMP module is used to process received SNMPV1 traps Monitoring The monitoring section is defined in the eFR xml file The monitoring section starts with the tag lt Monitoring gt Within the tag are the following subsections e OM section is not applicable for traditional and SIP DECT systems e DISK is available starting with lt DISK gt and ending with lt DISK gt e PING is available starting with lt PING gt and ending with lt PING gt e NETSTAT is available starting with lt NETSTAT gt and ending with lt NETSTAT gt The following figure illustrates the monitoring section and subsections 158 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com C Program FilesWessenger Net Exe eFR xml Microsoft Internet Explorer provided hy NEC Phi O EJ Ele Edt Wew Favorbes Tools Help Ye 3 p x A LA po sath Sy Fevontes G 2 a ee w R Fel 3 Sddress CilProgrem Fies Mecsenger Net ExeterR carl vE o lt xml version 1 0 encoding utf 9 7 gt nitorina interval 600 gt m gt cSystem id NEC Philips unit 02 unit O2 addrass 127 0 0 1 port 29 gt lt SystemNotReedy gt lt Message gt i83000 unit 02 is not ready lt Moessage gt lt D ns gt x 1 gt BSNMP lt Destinatian gt 1 g
131. cmd_line N A log S INF Warning parameter amp keyword amp not available in amp lcl_cmd amp Else lel end rosti lel sri 1 UCase lel cme S m parse_cmd_line MidS g_command Space 5 lcl_str 2 Len keyword lcl_end tel swr r Len keyword 3 End If If Err Then sgBox Err Description amp Unexpected error in parse_cmd_line function ALO Why IRI RDS SCID EONS Unexpected error in parse_cmd_line function EDC IL Ie On Error GoTo 0 End Function Private Function parse_xml keyword As String xml As String As String Isolates the value for a keyword from a xml string When no value is found N A is returned On Error Resume Next Err 0 Dim lcl_start As Integer Dim lcl_end As Integer Dium lel irom AS Serine Dim lel to As Siviestine Dim lcl_value As String lcl_from LCase lt amp keyword amp gt lcl_to LCase lt amp keyword amp gt lel stearre PSr weases Cani Lel riom lcl_end ibiSiere Chel evene ap GSA e stom wcaseas Gan Ieil ice Lelivelue Nidi Cm hellistant hen ielstrom 1 lelmend Wellistant Len lcl_to If Err Then parse_xml N A ll lt i DECT Messenger Installation and Commissioning Book 1 March 2012 71 Module eAPI sample log S INF Warning parameter amp k Else parse_xml lcl_value End If On Error GoTo 0 End Function Private Sub lab_message
132. connected with remote port 03203 eKERNEL O TCP lt xml gt lt cfigrqs gt lt app1 gt eLOCATION lt appl1 gt lt site gt 1i lt site gt lt cfigrqs gt lt xml gt I TCP lt xml gt lt cfigrpy gt lt la_address gt 192 166 32 10 lt la_address gt lt la_port gt 2 00 amp la_port gt lt generaltimeout gt 10 lt generaltimeout gt lt polling intv gt 60 lt polling_ intv gt lt log path gt C SOPHO Messenger net lt log path gt lt log days gt 14 lt log days gt lt cfgrpy gt lt xml gt S INF TCP local port 02549 connected with remote port 28008 DCC Figure 150 Initiation procedure When the configuration is received a screen similar to the one shown in the following figure is shown View the configuration in the Connections tab 208 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Initialization H eLOCATION SOPHO Messenger Net v4 0 0 eKERNEL eLOCATION eLOCATION Connections m eKernel m Configuration local 192 168 3210 1126 Remoteaddess 1921683210 Remote 1921683210 3203 Remoteprt os Status Connected Poling interval 60 General timeout 10 DEC logpath CSS0PHO Messenger net Cts local 192 168 3210 1127 _ Log days 14 Remote 192 168 3210 1025 Status Connected Bi Data arrival 223 bytes received from eKERNEL 00025 18 30 13 8 Figure 151 eLocation configuration connections tab The logging tab shows logg
133. d according to specific rules A sample request is illustrated in Figure 35 Sample message request on page 66 lt xml gt lt msgrqs gt lt set_or_reset gt SET lt set_or_reset gt lt group gt 1 lt group gt lt alarmdescr gt 2 lt alarmdescr gt lt msg gt 3 lt msg gt lt remove_after gt SENT lt remove_after gt lt msgrqs gt lt xml gt Figure 35 Sample message request The following rules apply e The string must start with lt xml gt lt msgrqs gt and end with lt msgrs gt lt xml gt tags At the end of the string a carriage return ASCII 13 and line feed ASCII 10 must be appended e The message request must contain 5 parameters The parameter set_or_reset must start with lt set_or_reset gt tag and end with the lt set_or_reset gt tag The parameter group must start with lt group gt tag and end with the lt group gt tag 66 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Introduction to a sockets client The parameter alarmdescr must start with lt alarmdescr gt and end with the lt alarmdescr gt tag The parameter msg must start with lt msg gt tag and end with the lt msg gt tag The parameter remove_after must start with lt remove_after gt tag and end with the lt remove_after gt tag e The parameter set_or_reset can supports the following values SET or RESET e The parameter group refers to a configured group defined in the eKE
134. dly gt lt csta_api_address gt 10 110 50 140 lt csta_api_address gt lt csta_api_port gt 59000 lt csta_api_port gt lt external_seat_cnt gt 3 lt external_seat_cnt gt lt external_port gt 2010 lt external_port gt lt csta_pbx_address gt 10 110 49 171 lt csta_pbx_address gt lt csta_pbx_port gt 28001 lt csta_pbx_port gt lt csta_licence gt Mes senger lt csta_licence gt lt guarding_intv gt 60 lt guarding_intv gt lt guarding_Retry_intv gt 20 lt guarding_Retry_intv gt lt eKernel_Seat_cnt gt 10 lt eKernel_Seat_cnt gt lt GeneralTim eOut gt 15 lt GeneralTimeOut gt lt Ack2TimeOut gt 30 lt Ack2TimeOut gt lt DataPathDelay gt 2 lt DataPathDelay gt lt network gt dasgif lt network gt lt pbxtype gt NORTEL lt pbx type gt lt IoReg_cnt gt 9 lt IoReg_cnt gt lt IoReg_0001 gt 860 lt ToReg_0001 gt lt IoReg_0002 gt 861 lt IoReg_0002 gt lt IoReg_0003 gt 862 lt ToReg_0003 gt lt IoReg_0004 gt 999 lt IoReg_0004 gt lt IoReg_0005 gt 869 lt IoReg_0005 gt lt IoReg_0006 gt 868 lt IoReg_0006 gt lt IoReg_0007 gt 867 lt IToReg_0007 gt lt IoReg_0008 gt 866 lt IoReg_0008 gt lt IoReg_0009 gt 865 lt IoReg_0009 gt lt log_path gt C SOPHO Messenger net lt log_path gt lt log_days gt 14 lt log_days gt lt cfgrpy gt lt xml gt 03 10 2002 13 58 55 S INF Warning Not enough seats available for IoRegister continued on next page 142 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya
135. dules connected to a DECT Messenger The three rails with modules are connected together via the RS 485 bus DECT Messenger Installation and Commissioning Book 1 March 2012 21 Preparing external devices DECT Messenger 24VDC power FP 1000 Al 100 DI 330 DO 401 inputs inputs outputs TT a a an 4 N V24 interface 24VDC RS 485 J iii interface FP 1001 DI 330 DO 401 inputs outputs a g 24VDC RS 485 power interface FP 1001 Al 100 DO 401 j inputs outputs u e Figure 5 Example of connecting multiple FP rails to DECT Messenger The connection between the DECT Messenger PC and the first rail is achieved by means of V 24 This means that the maximum cable length is determined by the V 24 characteristics and the cable type If you have more than one rail only available on a project basis the connection between the rails and therefore the connection between the FP 1000 and FP 1001 modules is achieved by means of an RS 485 connection This is a 4 wire bus connection that allows a maximum distance of approximately 1000 meters Instead of using an FP1000 module as Controlling Module on a rail you can use the FP 1601 module The FP 1601 module has an Ethernet interface to DECT Messenger instead of the V 24 interface However this module is not supported in the standard DECT Messenger product range it is only supported on a project basis 22 DECT Messenger Installati
136. e Programs gt Startup C SOPHO Messenger Net Exe eASYNC exe Site 1 eKernel port 3105 eKernel address LOCAL Log drive C Figure 37 Typical parameters in the shortcut In the example in Figure 37 Typical parameters in the shortcut on page 81 the eASYNC exe identifies itself as belonging to Site 1 and specifies the location of eKERNEL through IP address LOCAL and port 3105 The special value LOCAL refers to the assigned IP address of the first NIC adapter found in the PC You can find this use the IPCONFIG exe command or in the appropriate sections of the Windows network settings The keyword Log drive refers to the drive in which the logging data must be stored usually this is the C drive referring to C SOPHO Messenger Net Log structure DECT Messenger Installation and Commissioning Book 1 March 2012 81 Module eASYNC At startup the eASYNC exe sends an XML string to eKERNEL exe requesting a configuration This step is needed for each module that interacts with eKERNEL exe because this approach allows central administration using a single database even if some client modules are located on a distributed machine lt xml gt lt cfgrqs gt lt app1 gt eASYNC lt app1 gt lt site gt 1 lt site gt lt cfgrqs gt lt xml gt lt xml gt lt cfgrpy gt lt interface_cnt gt 2 lt interface_cnt gt lt com_port_01 gt COM02 lt com_port_01 gt lt settings_01 gt 9600 N 8 1 lt settings_01 gt lt t
137. e you can enter the first name and last name e The parameter from is part of the resulting Windows pop up message and is shown to the user The parameter from allows the destination user to identify what user or application has sent the pop up message For example you can use DECT Messenger e The parameter to is the most important parameter as this parameter defines the destination system used by the embedded NET SEND functionality The parameter to must be the correct PC name of the destination user As a suggestion open the command window on the target system and use the echo computername command to find out the value that needs to be specified in the field to For example In the figure the resulting value is BENB121027 DECT Messenger Installation and Commissioning Book 1 March 2012 155 Module eFR C WINDOWS system32 cmd exe x C gt echo zcomputernamez BENB121027 Gs gt Figure 92 Parameter to Destinations type SMS The following figure illustrates Destinations type SMS lt Destination id eSMS type SMS descripton Francis Missiaen address 127 0 0 1 port 29081 extension 32473897171 gt Figure 93 Destinations type SMS The following parameters are specific to SMS e The parameter description refers to the name of the destination user and allows you to assign a user name For example you can enter the first name and last name of the user e The parameter
138. e Internet Information Services IIS details window appears listing the installed IIS subcomponents 6 Verify that Common Files and Internet Information Services Snap In options are checked 7 Optional If you intend to use SMTP Server module in DECT Messenger ensure that SMTP Service option is also checked as shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Installing IIS Internet Information Services IIS To add of remove a component click the check box shaded box means that only part of the component will be installed To see what s included in a component click Details Subcomponents of Intenet Information Services IIS v a Documentation 3 5 MB CJ A File Transfer Protocol FTP Service 0 1 MB O Q FrontPage 2000 Server Extensions 4 3 MB 7 F Intemet Information Services Snapn 1 3MB v 3 SMTP Service 1 1 MB a Misa V aa eT Nim Description Uses the HTTP protocol to respond to Web client requests on a TCP IP network Total disk space required 19 8 MB Details Space available on disk 3608 0 MB Figure 8 Internet Information Services IIS window 8 Select World Wide Web Service and click Details in the World Wide Web Service details window that appears ensure that World Wide Web Service is checked then click OK to close it 9 Click OK to close the Internet Information Services IIS details w
139. e asynchronous serial communications with a number of alarm systems the eCAP requires configuration settings to start processing These values are returned through the lt cfgrpy gt reply that is sent on return of the lt cfgrqs gt request Some parameters refer to asynchronous communication settings for example port number baud rate data bits parity bits stop bits and so on others refer to general information settings for example logging parameters the rest are parameters that actually determine the alarm system for example manufacturer model bidirectional and so on Note The values shown in Figure 55 eCAP Connection tab on page 99 are received from the DECT Messenger database from the eKERNEL_INPGM table eCAP_generic table and the eKERNEL_SITE table At startup the eCAP exe appears the specified COM port with the specified settings The COM port specified must be available be set to use a valid baud rate and so on A physical connection must exist between the specified COM port and the external alarm system through a properly wired serial cable In many cases alarm systems support a limited number of control signals for example ground and send so consult the alarm system vendor on cable specifications In most cases you can use a standard null modem cable If no more COM ports are available extra hardware such as DigiBoard PC 4e or DigiBoard PC 8e is needed to provide extra serial ports Check compatibility i
140. e automatic logon after a power failure the PC restarts and logs on automatically DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com License module eFR Do not logoff the desktop as this ends the monitoring application License module eFR The module eFR is a licensed software module The module eFR cannot be copied without valid agreement from Avaya A software key is required to launch the program If you do not have a software license key the following window appears eFR SOPHO Messenger Net License key is invalid for this system Please contact you software representative and eat order a licence key for Messenger Net module eFR The software will be registered to NEC Philips Unified Solutions NEC Philips Unified Solutions 76487 641 3119356 231 75 You may be asked to provide the info listed below Computer name BENB121027 Serial number 230464 584F OEM A5D8 MAC address 00 15 C5 07 5B 4C Processor x86 Family 6 Model 13 Stepping 8 Enter the license key below and press OK to continue Figure 90 Software license key required Contact Avaya to obtain an evaluation or a permanent key for using the software Configure module eFR The module eFR is configured using an XML file Follow the steps in the next procedure to configure module eFR Configuring module eFR 1 Browse to the directory C Program Files Messenger Net Exe 2 Doubl
141. e click on the file eFR xml DECT Messenger Installation and Commissioning Book 1 March 2012 151 Module eFR You can use Microsoft Internet Explorer to access files with XML extensions These XML files must have the correct syntax or XML cannot be opened by Internet Explorer and results in a failure of module eFR ej C Program Files Messenger Net Exe eFR oml Mic Jog File Edit view Favorites Tools Help ir 4 z A Pi Search 5 Favorites Address C Program Files Messenger Net Exe eFR xml x Go Links A lt xml version 1 0 encoding utf 8 7 gt lt eFR gt lt Monitoring interval 600 gt lt Destinations gt lt eFR gt 4 My Computer Destinations Destinations planning Follow the steps in the next procedure for destinations planning Planning destinations 1 Determine what notification methods to use Notification methods include technologies such as the following e mail windows popup e SMS message to mobile GSM phone e SNMPv1 trap 2 Check what prerequisite actions and infrastructure are needed to make the destinations operational Consultant services are available to assist in this process For some transport mechanisms you can depend on other parties and people for example the administrator of the e mail infrastructure 152 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Destinations configuration
142. e contacts the eLOCATION module to find out the physical location of the SIP DECT user In DECT Messenger prior to release 2 9 10 the eKERNEL contacts only the LOCATION of the same site and the same area as the eDMSAPI module that alerted the alarm This means if the alarm was detected from eDMSAPI site 1 area 1 eKERNEL only contacts eLOCATION site 1 area 1 This was a limitation to the scalability of the solution as there is a one to one relationship between eDMSAPI numbering and eLOCATION numbering In release 2 9 10 and in subsequent releases the eKERNEL contacts every instance of eLOCATION of the same site of the originating eDMSAPI module This means that an alert from eDMSAPI site 1 area 1 is forwarded to all eLOCATION instances of site 1 As a result in a environment with three DAP Controller PCs and three associated eLOCATION instances the location request is sent to all three eLOCATION modules Each DAP Controller PC then has the opportunity to provide feedback on the last known location of the requested extension or calling party and return this last known location to eKERNEL Depending on the version of eKERNEL prior to release 2 9 10 or release 2 9 10 and subsequent releases the eXKERNEL interprets the results from the location request In release 2 9 10 and newer version the last use timestamp indication is used to determine the location For these steps the eLOCATION instances must be configured as shown in the following f
143. e eKERNEL message request and eASYNC feedback on page 84 shows an example of a message request and the feedback generated by eASYNC DECT Messenger Installation and Commissioning Book 1 March 2012 83 Module eASYNC lt xml gt lt msgrqs gt lt id gt 00005 lt id gt lt type gt SMS lt type gt lt provider gt PROXIMUS lt provider gt lt password gt proximus lt password gt lt to gt 32475353215 lt to gt lt pag_01l gt test message lt pag_01 gt lt pag_more gt N lt pag_more gt lt msgrqs gt lt xml gt lt xml gt lt msgrpy gt lt id gt 00005 lt id gt lt sts gt NACK lt msgrpy gt lt xml gt No carrier while waiting for connection lt sts gt Figure 41 Sample eKERNEL message request and eASYNC feedback During com munications e ASYNC contacts the provider and handle the dialog that is required to deliver the message The transactions are processed on a first in first out basis However configuration settings can be active that request a wait time or a queue depth that must be reached prior to initiating the communication process This is especially relevant for SMS messaging to PROXIMUS or KPN because these providers support the ability to deliver more than one SMS message during one single dial up connection A gt eASYNC SOPHO Messenger Net v2 0 6 eKernel eASYNC iG 0 ATacoso 3 a Fequest 00005 Waiting 30 seconds for INIT reply Settings co
144. e group is not defined in the Messenger_CFG mdb database the eKernel application sends the request to the group identified with a question mark if one is defined in the table eKERNEL_GROUP field GRP_Descr_str This feature is supported for eCAP WORMALD only when model L xx Examples Table 9 Alexianen 27 04799 155305325 ALARM 001 084 DK 8000 REV EVACUA This datastream results in SET of alarm with alarm description WORMALD_F and message F8000 REV EVACUA remove after RESET The group varies depending on the model 116 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com WORMALD Table 10 F8000 REV EVACUA groups Model Group BASE WORMALD_F L 01 8 group description field GRP_Descr_str from table eKERNEL_GROUP L 02 80 L 03 800 L 04 8000 G BRAND BRAND for all alarms including fire and pre alarms 27 04 99 19 55 52 VOORALARM 0001 024 ION 9003 KEU EETPL This datastream results in SET of alarm with alarm description WORMALD_P and message P9003 KEU EETPL remove after RESET The group varies depending on the model Table 11 P9003 KEU EETPL groups Model Group BASE WORMALD _P L 01 9 L 02 90 L 03 900 L 04 9003 G BRAND BRAND for all alarms including fire and pre alarms 27 04 99 19 56 12 Reset This datastream results in a RESET of alarm description ALL for gr
145. e illustrates the reception of an inbound SMS message The message confirms all alarms for the devices that have pincode 238 232 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Inbound messaging fi eSMS SOPHO Messenger Net 2 9 10 Bee eKernel eSMS Help Logging Outbound J Inbound El S Inbound SMS from 32495363201 I Confirm 238 I lt xml version 1 0 gt lt SMSmessayge gt lt type O lt xml version 1 0 gt lt reply gt Your inbow A ON MB Data arrival 148 bytes received fiom eKERNEL J 00034 21 51 30 amp Figure 184 Reception of an inbound SMS message More details on this data exchange are given under the logging tab as shown in the following figure ff SMS SOPHO Messenger Net 2 9 10 Biel x eKernel eSMS Help Logging Application eSMS SOPHO Messenger Net vZ 9 10 started with parameters Si TCP local port 01184 connected with remote port 03117 eKERNEL xml gt lt cfgrqs gt lt appl gt eSMS lt appl gt lt site gt 1l lt site gt lt cfgrqs gt lt xml gt lt xml gt lt cfgrpy gt lt sms_address gt 127 0 0 1 lt sms_address gt lt sms_outbound_port gt Z9081 lt s i xml version 1 0 gt lt SMSmessage gt lt type gt SMS DELIVER lt type gt lt originatingd ddress i lt xml gt lt smsrqs gt lt id gt 32495363Z01 lt id gt lt msg gt Confirm 238 lt msg gt lt smsrqs gt lt xnl gt AARE a AN AA E AESLAR AAA RAA inbound
146. eKERNEL without any external models is unable to perform work A minimum configuration requires at least one input source for example eCAP for capturing a TELEVIC PROTOCOL CONVERTOR signalling system and one output source for example eDMSAPI for sending E2 data messages to cordless DECT handsets You can attach additional input sources to the product For example eCAP for other signalling systems elO for unpowered contact detection eSMTP for receiving MAIL and eWEB for receiving messages from the Internet You can attach additional output sources to the product For example eSMTP for sending electronic mail eASYNC for sending short messages to GSM and Pagers eCSTA for sending voice call based user to user messages eVBVOICE for handling outgoing voice calls Note In release 4 0 the maximum amount of modules has been increased from 21 to 30 DECT Messenger Installation and Commissioning Book 1 March 2012 195 Module eKERNEL Database The eKERNEL application is the only application that communicates directly with the databases Every external application receives its configuration from eKERNEL There are two databases One is named Messenger_CFG mdb and another is named Messenger_data mdb Both databases are in Microsoft Access 2000 format and are processed through applications written in Microsoft Visual Studio 6 0 Visual Basic and C In release 4 0 the Messenger_DATA database can also reside on SQL Server 2
147. eady come with preconfigured input output modules alarms and alarm groups Avaya recommends using 46 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Configuring DECT Messenger whenever possible a standard configuration as a starting point when setting up a customer site Standard configuration database Standard configuration databases are installed with the main product during a Server mode installation They are located in the following directory INSTALLDIR Default Templates Database Ac Program Files x86 NEC Messenger Net Default Templates Database fo Defauk Templates Database K J Search Database 2 Organize indudeinibrary Sharewith Burn New folder He gt i Q We Favorttes J 00 Defaut Hl Desktop d 00 Empty JB Downloads J 01 eDMSAPI eELOCATION eWEB 153000 E Recent Places 02 eDMSAPI ELOCATION eWEB IP DECT 02 eDMSAPI ELOCATION eWEB eSNMP IP DECT wy Ubraries Ji 03 eDMSAPI eELOCATION eSMS eWEB 153000 J 04 eDMSAPI eLOCATION eSMS eWEB IP DECT 1M Computer IJ 05 eOMSAPI e10 eWEB 153000 amp SYSTEM C Ji 06 eDMSAPI e10 eWEB IP DECT a DATA 03 1J 07 eOMSAPI eESPA eWEB 153000 a 03 eDMSAPI eESPA eWEB IP DECT d 08 cOMSAPI eESPA eWEB eSNMP IP DECT 11 Messenger Xpress BE 12 Messenger Xpress BE add on J 99 All modules on 153000 Gia Network F
148. ee Os e Oo amp to SkKERNEL EREDO Else lst_ekernel_outq RemoveItem 0 log Wer del o By ee Loop OnE OneG OMOmO Err amp e Err Description amp during SendData amp lcl_ Close socket after send DoEvents ip_ekernel Close Set socket state indicator to defaults lab_ekernel_state BackColor RGB 0O O O Update screen g_ekernel_local_address ip_ekernel LocalIP lab_ekernel_local_address amp g_ekernel_local_address g_ekernel_local_port ip_ekernel LocalPort lab_ekernel_local_port amp g_ekernel_local_port End Sub Private Sub process_ekernel_jobq cmd As String Dim lel re As Integer lt xXxxXxXxXX gt If Left cmd Space 13 13 lt xml gt lt xxxxxx gt Then TODO you could add code here EAC EE lt yyyyyy gt If Left cmd Space 13 13 lt xml gt lt yyyyyy gt Then TODO you could add code here maei E End Sub Sub show_pages End Sub Private Sub tim_Timer Dim lcl_guarding As Variant Disable timer to prevent recursive calls tim Enabled False Update clock lab_clock amp Format Now hh nn ss Update guarding DECT Messenger Installation and Commissioning Book 1 lab_log Format lst_log ListIndex 1 00 amp amp Format lst_log ListCount 00 March 2012 77 Module eAPI sample lcl_guarding Timer g_gu
149. eeeceaeeteaeeseensaaes 201 Add O On module cccccccceccceeeeeeceeeeeeeeeeeeeeeceeeeeeeeeeeenees 9 AGING A CSVICE PE S E 57 Alarm information sssseeeeeseeesssssrrrrrssssrrerrrnrnnsssssrsns 100 Alar S saiet tananana a ania EA AE EEE ENEA AESA 101 Alexianen Bouchout installation ceeeeeeeees 116 Analogue Input sess essan RE n A R 182 Application Program Interface 0 eee 65 Applying the Key assioni sn aA 204 ARGHITEGH eissernir aaa 101 ARGINA raiu renidi aa EE 101 PS GO rinra aa 126 B BASE rinita ia ee 108 118 BASE G fessiecs tise cantaastgesentasenstlecsecdieatihageresdennigy 116 MAME Genim A 116 KKM E PE E EA 116 Basic architecture Of CAPI neeesser 66 Basic sockets cccssecccesseeeeeeesceecesseeeeceuseeeeseeeeensaees 67 BEMAC iiinis annei a a 104 C Clinique St Vincent Rocourt installation 104 Configuration Of CSMS c ccsssccceeeeeeessseessttntaeeees 234 configuring area information ccc eeeseeeeeeeeeneee 55 Configuring DECT Messenger sesers 46 Configuring destinations c cccceeeeeesseeeeeeteeeees 153 Configuring guarding ccceeeeeeeeeeeeeeeeeeeneeeeeeenees 198 Configuring module CFR cceeeceeeeeseeeeeteeeeeeeees 151 Configuring PBX information seeen 56 Configuring site information cceeeeereeesteeeeeeees 53 control MOCUIES rarose 19 Core software module sssssssssrsrinesesesrrnrrrrrirensrrrrrrrrns 9 GCGSTA
150. eft to select the Messenger_CFG database or the Messenger_DATA database e Use the second drop down list to select one of the following Perform inquiry functions using the View table Perform maintenance using the Edit table Export a table to a comma separated file using Export to CSV Export to an HTML file using Export to HTML DECT Messenger Installation and Commissioning Book 1 March 2012 171 Module eGRID e Use the third drop down list to select a table The available tables are retrieved automatically from the database object e Use the fourth drop down list to control the GRID view as follows Normal uses default view Inverted uses a rotated view Drag and drop to group records in Group e The fifth drop down list offers the following choices None uses a full screen interface for one table Show help splits the window interface in two halves the top half is used to access the table the bottom half is used to show the related PDF file help information You can select a second table with View another table which splits the window in two the upper half is used to access the first table the lower half is used to access the second table e The sixth drop down list is available only if a View another table is specified Use this list to select the second table e Use the seventh drop down list on the far right to modify the view of the second table Normal uses default view Inverted uses a rotated view
151. ense key file received from Avaya Click Open to load it 4 Verify the loaded licenses are correct The following figure shows the loaded licenses in License Manager License Manager OE Xx Ele Edt view Help gt Licensed Applications Msg Net SOPHO CTI Module Equipment Model Used Free Msg Net eGuardian Msg Net eSMS 0 3 Msg Net eWatchdog Msg Net eSNMP 0 9 Msg Net eBackup Msg Net Full 0 1 Msg Net eConfig Msg Net eCAP 0 3 Msg Net eDMSAPI Msg Net eESPA444 0 3 Msg Net eASyne Msg Net el 0 0 3 Msg Net eCSTA Msg Net eLocD 0 3 Msg Net eweb Msg Net eweb adv Msg Net eSMTP Chent Msg Net eSMTP Server Msg Net eAPI Msg Net eVBVoice Msg Net eLog Msg Net eNet Ready hn Figure 18 License Manager loaded licenses Configuring DECT Messenger Most DECT Messenger configuration settings are stored in a Microsoft Access database mdb file The database is located on the server PC together with eKERNEL and other server specific core components in the following location ra INSTALLDI R Database MessengerConfig mdb The recommended way to configure DECT Messenger is by using the eCONFIG Configurator module For expert users it is also possible to modify directly the configuration database by using the eGRID module link to subchapter below For convenience DECT Messenger comes with a set of standard configuration databases link to subchapter below also known as template databases These databases alr
152. escr gt lt log_path gt c SOPHO Messenger net lt log_path gt lt log_days gt 30 lt log_days gt lt cfgrpy gt lt xml gt Figure 54 A typical cfgrqs configuration request and its received cfgrpy configuration reply Note The generic eCAP configuration sends extra keywords and values as defined in the eCAP_generic table Refer to the chapters of this document that describe the database tables for more information on each value Detailed descriptions of these internal inter process communications is beyond the scope of this chapter When the configuration is received the Connection tab displays information similar to what is pictured in Figure 55 eCAP Connection tab on page 99 98 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com eCAP exe BS eCAP SOPHO Messenger Net v2 0 6 eKernel eCAP Logging Connections eKernel Configuration local 10 110 50 138 1303 Manufacturer ELDAD Remote 10 110 50 138 3102 Model L 48 0 RC 1 5R 2 95 3 55 4 5R Status Connected Bidirectional Y Resource COMDI Settings a0 J Port COMOT E SSC dLsSstC lt lt C lt C lt CS S 3St i i i t tt J Settings 9600 N 8 1 Uogpath IC ASOPHO MessengeraNet co m eCAP ae Be Data arrival 261 bytes received from eKERNEL 00006 13 22 18 Figure 55 eCAP Connection tab Because the eCAP is designed to handl
153. escription ARITECH_F ARITECH_C or ARITECH_B depending on the datastream Alarms are SET with option CALC To define alarms remove after RESET When HERSTEL occurs a general reset of all ARITECH alarms is issued for ALL groups and ALL alarm descriptions Note This protocol usually requires project based consulting services and customizing DECT Messenger Installation and Commissioning Book 1 March 2012 103 Module eCAP BEMAC Valid manufacturer is BEMAC valid model is DIANA 1 and DIANA 2 Bemac is based upon installation Clinique St Vincent Rocourt 20000913 15 07 09 20000913 15 09 09 I lt 861 LOC 222B 0 gt 20000913 15 09 31 I lt 861 LOC 333B 0 gt I lt 866 LOC 101B 0 gt I I 20000913 15 10 47 I lt 861 LOC 444B 0 gt I I I 20000913 15 11 34 I lt 999 RESET 0 gt 20000913 15 12 04 I lt 999 RESET 0 gt 20000913 15 12 39 I lt 999 RESET 0 gt Figure 58 Sample Bemac protocol data Bemac alarms contain three fields a pager number a message and a tone code Alarms are sent with group equal to the first parameter for example 866 The message is retrieved from the second parameter for example LOC 101B When the third parameter is 0 the message is reset When the message is RESET all messages for all groups are reset in other cases only the specific message for the specified group is reset When the third parameter is a value other than 0 the message is set During set the alarm description i
154. ettings 9600 N 8 1 COM AT COM _01 00084 0 01 0620032328 3 456D657267656E637920534F5320312045766163756174696F6E E2_ 02 05 2002 13 58 33 S INF Port closed 02 05 2002 13 58 33 O TCP lt xml gt lt msgrpy gt lt id gt 00142 lt id gt lt sts gt ACK lt sts gt lt msgrpy gt lt xml gt Figure 45 Sample logging data for SMS to KPN 86 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 Logging 19 03 2001 15 56 08 19 03 2001 15 56 09 19 03 2001 15 56 10 19 03 2001 15 56 10 19 03 2001 15 56 10 19 03 2001 15 56 09 19 03 2001 15 56 10 19 03 2001 15 56 10 19 03 2001 15 56 34 19 03 2001 15 56 34 19 03 2001 15 56 40 19 03 2001 15 56 40 19 03 2001 15 56 40 19 03 2001 15 56 40 19 03 2001 15 56 40 19 03 2001 15 56 40 19 03 2001 15 56 40 19 03 2001 15 56 40 19 03 2001 15 56 40 19 03 2001 15 56 40 19 03 2001 15 56 40 19 03 2001 15 56 40 ing belgacom be 19 03 2001 15 56 41 I COM or Contact 02 5406161 NL 02 5406302 FR 19 03 2001 15 56 42 I COM www belgacom be cgi bin echannel web in dex jsp LANGUAGE EN amp DIVISION RES 19 03 2001 15 56 42 I COM Select INF COM02 opened with settings 9600 N 8 1 COM ATECOS0 3 COM ATECOS0 3 COM OK COM ATDT 00452500001 COM OK COM ATDT 00452500001 COM CONNECT 14400 V42bis COM WELCOME TO THE BELGACOM PAGING SERVICE COM You can call numbers in the range COM
155. f and locate the eXKERNEL exe program This is carried out by means of parameters in the properties DECT Messenger Installation and Commissioning Book 1 March 2012 119 Module eESPA 120 section of the shortcut that initiates eESPA exe This shortcut is usually located in the Windows Startup group C SOPHO Messenger Net Exe eESPA exe Site 1 eKernel address LOCAL eKernel port 3114 Log drive C SleepBeforeAnswer 0 Figure 69 Typical parameters in the shortcut In the example shown in Figure 69 Typical parameters in the shortcut on page 120 the eESPA exe identifies itself as belonging to site 1 and specifies the location of eKERNEL through IP address LOCAL and port 3114 The special value LOCAL refers to the assigned IP address of the first NIC adapter found in the PC You can determine the IP address using the IPCONFIG exe command or in the appropriate sections of the Windows network settings The keyword Log drive refers to the drive where the logging data must be stored Usually this is C SOPHO Messenger Net Log The keyword SleepBeforeAnswer refers to the number of milliseconds the system waits before sending an answer to the linked station Some systems block the answer if the answer is sent immediately less than 6 milliseconds after receipt Use this parameter to set a delay of x milliseconds before the output is sent Note The maximum supported value is 150 milliseconds Set this value as low
156. fetched there 2 When the first definition is unavailable alarm types are fetched equal to the tone code 0 1 2 3 4 5 6 7 8 9 If this definition is found the alarm attributes are fetched there 3 As the last option the alarm types are fetched through OTHER special value If this definition is found alarm attributes are fetched there In absence of any of the three definitions the alarms are ignored The alarm message is retrieved from the datastream NUR PAL POORT 100 and so on DECT Messenger Installation and Commissioning Book 1 March 2012 111 Module eCAP TYCO The valid manufacture is TYCO and the valid model is MINERVA 80 FIRE EVACUATE GROUND FLOOR 12 13 14 22 Nov 05 BGU FRONT HALL EAST Zn 0110 F 63 CLEAR GROUND FLOOR 12 13 24 22 Nov 05 BGU FRONT HALL EAST Zn 0110 F 63 SYSTEM SILENCE Fire System Zone 12 13 54 22 Nov 05 Silence Zn 0300 LBOO S02 SYSTEM RESET 12 13 56 22 Nov 05 Non Addressable Panl 01 MP SYSTEM RESET All Zones 12 13 56 22 Nov 05 Unknown Panl 03 MP ISOLATE STATUS ON System Zone 12 13 58 22 Nov 05 Non Addressable Zn 0100 PALM BEAMS ISOLATED 12 13 58 22 Nov 05 Non Addressable Panl 01 MP R02 PRINTER OFFLINE System Zone 12 13 58 22 Nov 05 Non Addressable Zn 0400 LBOO R04 FIRE ALARM GROUND FLOOR 12 16 20 22 Nov 05 SD SAFE DEPOSIT Zn 0110 F 7 SYSTEM SILENCE Fire System Zone 12 16 30 22 Nov 05 Silence Zn 0300 LBOO S02 SYSTEM RESET 12 16 38 22 Nov 05 Non Addressable Pnt Panl
157. ft com support kb articles Q207 7 03 asp DECT Messenger Installation and Commissioning Book 1 March 2012 95 Module eBACKUP 96 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 14 Module eCAP The module eCAP consists of the program eCAP exe written in Visual Basic In general DECT Messenger programs reside in the default directory C SOPHO Messenger Net Exe unless otherwise implemented in your environment Overview eCAP exe The eCAP exe is a Visual Basic component of the eCAP module The program communicates with two processes the eKERNEL exe and an external alarm interface The eKERNEL exe is the central engine that centralizes all database access and communication with input and output capable modules The eCAP exe communicates with eKERNEL exe by means of TCP sockets In this communication eCAP exe is a TCP client software that connects to the eKERNEL component acting as TCP server software At startup eCAP exe contacts the eKERNEL exe by means of a socket connection Startup parameters identify eCAP exe and locate the eKERNEL exe program These parameters are set in the Properties section of the shortcut that initiates eCAP exe This shortcut is usually located in the Windows Startup group click Start on the Windows toolbar and choose Programs gt Startup C SOPHO Messenger Net Exe eCAP exe Site 1 eKernel address LOCAL eKernel port 3102
158. g a new verification the exact frequency is somewhat larger than the specified interval depending on the processing time DECT Messenger Installation and Commissioning Book 1 March 2012 159 Module eFR Monitoring type DISK The monitoring of disk drives is configured through the section in the XML file shown in the next figure C Program Files Messe nger Net Exe eFR x BAX File Edit View Favorites Tools Help ay Dp P x a A DO Search Address C Program Files Messenger Net Exe eFf EJ Go Links lt xml version 1 0 encoding utf 8 gt lt eFR gt lt Monitoring interval 600 gt lt OM gt lt DISK gt lt Drives gt lt Drive id C usage 70 gt lt Drive id D usage 50 gt lt Drives gt lt DISK gt lt PING gt lt NETSTAT gt lt Monitoring gt lt Destinations gt lt eFR gt Figure 97 Monitoring type DISK The opening tag lt DISK gt and the closing tag lt DISK gt provide space for configuring the drives that must be monitored You can define each drive that needs to be monitored in the section between lt Drives gt 160 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com fie Edt Wew Favertes Icos tielp 9 A G Asem genom O B a RA Agress C Program Flasi Messanger met Exa eFR xm miS Es lt xml version 1 0 enceding utf 3 7 gt Vestinations gt iweNo
159. g station that polls devices on the communication line Polling means sending out requests for data The polling device which is also called controlling station or master sends out requests to the other devices available on the communication line Every device on the line has a specific address The characters 0 to 9 are available as addresses Avaya recommends that you assign the character 1 to the controlling station In the field eESPA_Polling_address_list_str of the table eESPA you can define multiple addresses of slave devices At least one address that represents a slave is required in this field Multiple addresses are separated by For example the value 2 4 5 in eESPA_Polling_address_list_str defines three slaves that are polled by the controlling station Define a control station by placing eESPA_ControlStation_b in the eESPA table on True eESPA_LocalAddress_n and eESPA_ExternalAddress_n must be filled up respectively with the local address of the module a controlling station prefers a local address 1 and the address of an external eESPA module or device with which the module communicates The controlling station polls every address with an enquiry To extend the example the controlling station sends 2ENQ 4ENQ and 5ENQ The field eESPA_Polling_intv_n in the eESPA table defines the time between sequencing polls A slave whose address is polled reacts by replying with either a nothing to transmit EOT or an enquiry lt master
160. gister gt lt regdevice gt 860 lt regde vice gt lt calltype gt data lt calltype gt lt appltype gt messaging lt appltype gt lt ioregis ter gt lt xml gt 03 10 2002 13 59 00 I TCP lt xml gt lt IoRegisterResult gt lt invokeID gt 1 lt in vokeID gt lt IoRegisterReqidentifier gt 746 lt IoRegisterReqidentifier gt lt IORegis terResult gt lt xml gt 03 10 2002 13 59 00 I TCP lt xml gt lt cstaSystemstatusReq gt lt invokeID gt 31762 lt invokeID gt lt cstaSystemstatusReq gt lt xml gt Guarding gt lt xml gt DECT Messenger Installation and Commissioning Book 1 March 2012 143 Module eDMSAPI 03 10 2002 12 08 57 I TCP lt xml gt lt msgrqs gt lt id gt 00774 lt id gt lt ext gt 861 lt ext gt lt ext_prty gt 6 lt ext_prty gt lt pag_01 gt Guarding AM TELEVIC lt pag_01 gt lt prty_01 gt N lt prty_01 gt lt pag_more gt N lt pag_more gt lt format gt 16 16 0 5 2 lt format gt lt msgrqs gt lt xml gt PBX type DMC and DAP controller NORMAL and or URGENT messages 03 10 2002 12 08 57 O0 TCP lt xml gt lt startdatapathdevice gt lt deviceID gt 861 lt de vicelID gt lt pathtype gt text lt pathtype gt lt dirtype gt bi lt dirtype gt lt homelocationnumber gt 1 lt homelocationnumber gt lt start datapathdevice gt lt xml gt PBX type CS 1000 NORMAL and or URGENT messages 03 10 2002 12 08 57 0 TCP lt xml gt lt startdatapathdevice gt lt deviceID gt 861 lt de viceID gt lt pa
161. gt lt cfgrqs gt lt appl gt eDMSAPI lt appl gt lt site gt 1 lt site gt lt cfgrqs gt lt xml gt O lt xml gt lt cfgrpy gt lt seat cnt gt Z0 lt seat cnt gt lt msg dly gt 3 lt msg dly gt lt csta api address gt l License manager 2 02 02 Detail Config reply send amp active messages for this client are reset Configuration reply sent to eDMSAPI a 745050 Figure 145 Watchdog enabled Guarding For every input program the administrator can configure a guarding facility as shown in Figure 146 Guarding information on page 199 If guarding is activated for a specific input program an indication is given in the Client information frame for every TCP IP client The Guarding T O field specifies the timeout that is defined in the eKERNEL_guarding table and the last event field text box shows the number of seconds that have passed since the last request was received from the TCP IP client Once the Last event value exceeds the guarding timeout value a guarding alarm is generated 198 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Guarding 3 eKERNEL SOPHO Messenger Net v2 8 0 O lt xml gt lt cfgrpy gt lt seat cnt gt Z0 lt seat ont gt lt usg dly gt 3 lt msg dly gt lt est a api address gt l Figure 146 Guarding information DECT Messenger Installation and Commissioning Book 1 March 2012 199 Module
162. havatvauduavsravctetadies 109 System requirements ccccceeeeeeeeeeeeeeeeeeeeeteeeeeeeeees 11 T TCP client definition 0 0 ceeeeeeseeeeeeceeeeeeeeeeeeenenes 168 TCP CONNECTIONS ccccccccccceeeeeeeeeeeeeeeeeeaeneeeeeeeeeeenes 196 TCP server definition cccccceccecceesceeeeseeseeeeeeeeeeees 166 TBE VIG siccsiccaverdatnvarsvavenasavetetiveadesaraasherdedibbaneesasaedies 109 TYCO cekon a 112 TYPO DISK rcce ke ieee NEEE Ei 160 Type NETSTAT rlen NR 166 Type PING encan 163 U Uninstalling DECT Messenger seeen 43 Using CCONFIG 1 ssi 50 V Visual Basic ccccccceececcecseeceeeaseeeeeeeeeeeeeess 67 97 135 Visual Basic v6 0 ceccee cee e cece eee eeeeeeeeeeeeeeeeeeeeeeees 119 Ni acces uaen es eceattn ovat oaateesdtee sence sdedteeateadcencameoes 112 126 Ww WatChdog rinrisapa 197 Web Administrator module ccccsseeececeeeseeeeeeaeeeees 9 WED INte aCe isise sinana 239 WORMALD sisi ccscvcvcusenesandvevceecadschavaiessPetasan covavanssiea tone 116 March 2012 245
163. he availability of a free license To verify how many licenses are available on the system use the Avaya License Manager This program gives an overview of bound licenses If an equipment model disconnects its license is unbound and the total of free equipment licenses is increased On the other hand if an equipment module connects the total of free equipment licenses is decreased and the total of used equipment licenses increased A bound equipment model receives a valid configuration reply If the equipment model cannot be bound a status message is sent as follows lt pgmsts gt NO LICENCE AVAILABLE lt pgmsts gt e Functionality model If a client is a functionality model the eKERNEL checks if the given functionality is available in the license system and if so sends a valid configuration reply If the requested functionality is not available in the license a status message is sent as follows lt pgmsts gt NO LICENCE AVAILABLE lt pgmsts gt When a client equipment or functionality model is licensed eKERNEL also provides a configuration reply and the specific eKERNEL tab page is updated with a clear key icon If the DECT Messenger Installation and Commissioning Book 1 March 2012 193 Module eKERNEL license cannot be bound or no correct functionality is available the eKERNEL tab page is not updated and the crossed through key icon remains eAPI and eWEB eAPI and eWEB do not send configuration requests To ensure th
164. he connection is broken eLOCATION attempts to reestablish a session a eLOCATION SOPHO Messenger Net 4 0 0 5 x eKERNEL eLOCATION eLOCATION Connections m eKernel r Configuration local 192 168 32 10 1126 Remote 192 168 32 10 3203 Remote port 1025 Status Connected Polling interval Remote address 192 168 32 10 60 General timeout 10 L r DCC Log path C SOPHO Messenger net Local 192 168 32 10 1127 Log days 14 Remote 192 168 32 10 1025 Status Connected E Data arrival 223 bytes received from eKERNEL 00025 18 30 13 8 Figure 153 eLocation program activity Note Define The IP address of the PC that runs eLOCATION in the PBX When the IP address is not defined the connection request is rejected by the DAP Controller The two green indicators on the bottom of the eLOCATION panel illustrate the successful connection state between both external parties Keep track of the progress of the actual location detection process through the eLOCATION tab The location detection process takes place when eKERNEL sends a location request to eLOCATION The following figure shows the idle state at system startup prior to executing the first request 210 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Program activity g eLOCATION SOPHO Messenger Net v4 0 0 eKERNEL eLOCATION eLOC
165. he following preconditions are met Ensure that the computer and operating system is prepared as described in the preparation chapters e Ensure that any third party software necessary for modules that you intend to use on this client PC for example National Instruments software is installed Installing a DECT Messenger Client 1 Insert the DECT Messenger product DVD The DVD Main Menu window appears If the Menu does not appear double click D Autorun exe where D is the drive letter of your DVD drive Select Client from the DVD Main Menu The Requirements Setup Wizard checks that the server meets the configuration requirements If the Pending Restart Requirements check fails for example due to conflicts with other installed software click Cancel to stop the installation and reboot the PC and then restart the installation procedure Click Next to continue The Install Prerequisites window appears Verify the warning messages about missing optional components If you intend to use Messenger Net software modules that are mentioned as not available in the warning messages cancel the installation Then install the required components as indicated in the Preparing Operating System and Installing Third Party Software chapters Click Next The Welcome to the InstallShield Wizard for Messenger Net window appears Click Next The Setup Type window appears DECT Messenger Installation and C
166. hen all parameters are correctly specified the elO contacts the eKERNEL application producing the log information shown in Figure 128 Logging information for elO on page 180 25 10 2001 10 41 35 S INF Application eIO SOPHO Messenger Net v2 0 6 started with param eters Site 3 eKernel address LOCAL eKernel port 3108 Log drive C 25 10 2001 10 41 36 S INF TCP local port 01183 connected with remote port 03108 eKERNEL 25 10 2001 10 41 36 Figure 128 Logging information for elO Once connected to eKERNEL the elO module requests its configuration This is performed through a configuration request The eKERNEL fetches the configuration from the IO_MODULE elO_Al elO_DI and elO_DO tables and responds with all relevant parameters that are needed for elO to continue processing Figure 129 elO configuration request and response on page 181 shows the configuration request and the response eKERNEL sends back DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Startup lt xml gt lt cfgrqs gt lt appl gt eI0 lt app1 gt lt site gt 3 lt site gt lt cfgrqs gt lt xml gt lt xml gt lt cfgrpy gt lt manufacturer gt NATIONAL INSTRUMENTS lt manufacturer gt lt model gt BASE lt model gt lt mod_cnt gt 3 lt mod_cnt gt lt mod_01 gt FP AI 100 lt mod_01 gt lt url_01 gt opc National Instruments OPCFieldPoint FP Res FP AI 100 1 Channel lt url_01
167. i_port gt lt external_seat_cnt gt 3 lt external_seat_cnt gt lt external_port gt 2010 lt external_port gt lt csta_pbx_address gt 10 110 49 171 lt continued on next page Figure 88 Log example initialization procedure DECT Messenger Installation and Commissioning Book 1 March 2012 141 Module eDMSAPI csta_pbx_address gt lt csta_pbx_port gt 28001 lt csta_pbx_port gt lt csta_licence gt Mes senger lt csta_licence gt lt guarding_intv gt 60 lt guarding_intv gt lt guarding_Retry_intv gt 20 lt guarding_Retry_intv gt lt eKernel_Seat_cnt gt 10 lt eKernel_Seat_cnt gt lt GeneralTim eOut gt 15 lt GeneralTimeOut gt lt Ack2TimeOut gt 30 lt Ack2TimeOut gt lt DataPathDelay gt 2 lt DataPathDelay gt lt network gt dasgif lt network gt lt pbxtype gt DAP Controller lt pbx type gt lt IoReg_cnt gt 9 lt IoReg_cnt gt lt IoReg_0001 gt 860 lt IoReg_0001 gt lt IoReg_0002 gt 861 lt IoReg_0002 gt lt IoReg_0003 gt 862 lt IoReg_0003 gt lt IoReg_0004 gt 999 lt ToReg_0004 gt lt IoReg_0005 gt 869 lt ToReg_0005 gt lt IoReg_0006 gt 868 lt IoReg_0006 gt lt IoReg_0007 gt 867 lt IoReg_0007 gt lt IoReg_0008 gt 866 lt IoReg_0008 gt lt IoReg_0009 gt 865 lt IoReg_0009 gt lt log_path gt C SOPHO Messenger net lt log_path gt lt log_days gt 14 lt log_days gt lt cfgrpy gt lt xml gt PBX type CS 1000 28 06 2004 13 58 55 I TCP lt xml gt lt cfgrpy gt lt seat_cnt gt 20 lt seat_cnt gt lt msg_dly gt 3 lt msg_
168. ia with the Clear Filter button by selecting another table or by selecting Refresh Note Incomplete information is displayed when you use Data Filtering because only the records with matching criteria are shown DECT Messenger Installation and Commissioning Book 1 March 2012 175 Module eGRID Subset Clear Filter _ DEV Site _id_ n DEV_Area_id_n DEV_id_str ES ea SS DEV_Descr_str eDMSAPI DEV_OUTPGM_str DEV_OUTPGM_facility_str Francis Missiaen Kristien Daneels 3 1 867 eDMSAPI C922 Erika Vloebergs 3 1 868 eDMSAPI C933 Mieke Goethals Figure 124 eGRID Data Filtering Look at the column header to find out what data type the field has Because the filtering function is based upon SQL instructions you must specify subset data that results in valid SQL grammar e Selecting partial data omitting training characters is valid only for string fields with the extension _ str For example DEV_OUTPGM_str can be part of a subset with e eD eDM and so on Boolean fields with extension _b and numeric fields with extension _n cannot be part of a subset with partial values and must be fully qualified e You must not specify special characters e String values can also be subset with syntax EN which select SEND Specify to accept generic leading characters Specifying invalid filter criteria can result in errors such as the one shown in Figure 125 Invalid filter criteria erro
169. ick on any node in the tree to show more information on the right pane e Right click on the nodes to show a pop up menu with actions available for that node e Double click on a node to show a screen where you can perform maintenance changes e Select File gt Exit to close You are asked whether to apply the changes see Publishing or discarding changes on page 60 Overview of DECT Messenger and eCONFIG concepts A site represents a PC running a DECT Messenger Server EeKERNEL module Normally only one site should exist An area is a subdivision of a site Multiple areas are normally only necessary when DECT Messenger is connecting to multiple iS3000 PBXs with DECT or when using a mixed environment of iS3000 2000 IPS for DECT phones 52 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Configuring DECT Messenger The modules node lists all modules configured grouped by module type Setting up module parameters requires advanced technical knowledge in most cases the provided defaults are sufficient Refer to the Administrator Guide for detailed information on each module The alarms are notifications also called messages received by eKERNEL from input modules Alarms received are processed according to rules specified in DECT Messenger and distributed using groups containing group members to output devices A more detailed presentation of concepts and their interaction i
170. if eTM Task Manager module is running e If eTM is not running close every running module by clicking the box in the top right corner of each module main window e If eTM is running right click its icon in the Windows taskbar notification area and choose Stop Then close any other running modules by clicking the box in the top right corner of each module main window 2 Right click the eTM icon again and select Exit Aconfirmation dialog appears 3 Click OK to confirm Publishing changes 1 When asked whether to apply the new configuration click Yes 2 Awarning message appears advising you to close down eKERNEL and all other running DECT Messenger modules as shown in the following figure eCONFIG Messenger Net v4 1 7 For a successful apply of the new configuration the Following A steps are necessarry Step1 If eTM is running you should pause the eTM module and manually close down all associated running tasks then close down the eT M module If eTM is not running you should close down the eKERNEL module and any other running modules Step 2 When the above steps are completed you can continue by pressing the OK button This will apply the new configuration Figure 31 eCONFIG warning message 3 Ensure that all modules are stopped refer to procedure above 4 Click OK to apply the configuration eCONFIG copies the local MessengerConfig mdb database over the production configuration datab
171. igure The configuration of eLOCATION involves a record in eLOCATION for each DAP 216 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Architecture Controller This DAP Controller 192 168 32 10 is handled by eLOCATION site 1 area 2 as shown in the following figure a Module eLOCATION xi Site ID 1 L42NE__ Bosrd number Comment mrn Site description Site 1 TF eLOCATION_B Area ID 2 Default eLOCATION_B Area description SIP DECT MERA Default eLOCATION_B Location Agent address 192 168 32 10 Default eLOCATION_B Location Agent port 28008 General timeout 10 Retry count 5 Retry interval 10 Polling interval 60 gt gt gt RPN definition Comments eLOCATION configuration for SIP C amp Inbound call handling i gt gt gt eCSTA inbound event gt gt gt eDMSAPI inbound event gt gt gt eLOCATION Inbound result New Edit amp Interface with eKERNEL Delete Refresh OK Cancel Figure 161 Configuration of eLOCATION For each DAP Controller and each eLOCATION instance a number of associated definitions are required in the tables eLOCATION_BOARD eLOCATION_RPN and eLOCATION INBOUND_RESULT The eLOCATION_BOARD defines the SIP DECT extensions that are registered in the DCC board See the configuration of the PBX to determine the DECT extensions that are associated with a DAP Control
172. igure 19 Default database templates You can manually apply a configuration database or import one using Web Administrator To manually apply a configuration database 1 Ensure that all DECT Messenger modules are stopped 2 Open Windows Explorer 3 Browse for the location of the desired template database on the server PC For example C Program Files Avaya Avaya DECT Messenger Default Templates Database 02 eDMSAPI eLOCATION eWEB IP DECT 4 Copy the chosen MessengerConfig mdb template file DECT Messenger Installation and Commissioning Book 1 March 2012 47 Getting started with DECT Messenger 48 5 Browse for the main database directory For example C Program Files Avaya Avaya DECT Messenger Database Rename the existing MessengerConfig mdb to MessengerConfig_old mdb in case you need to return to the default configuration 6 Paste the MessengerConfig mdb template file into the main database directory To import a configuration database using Web Administrator 1 Ensure that all DECT Messenger modules are stopped Open Web Administrator by going to Start menu gt Programs gt Avaya DECT Messenger gt Web Administrator Login with your username and password The default username is admin and the default password is admin On the left side tree navigate to Configuration gt Expert gt Import If KERNEL or eGRID are running on the server an error message displays one
173. incode at startup 4 Use the menu options of your regular mobile phone to disable the PIN code check at power up To verify that this step is complete switch the regular mobile phone off and on The mobile phone no longer asks for a PIN code and immediately becomes operational Important Do not continue unless this step completed 5 Ensure the location where you plan to install the Siemens TC35i has sufficient coverage of your mobile provider The building environment can prevent good reception of a mobile operator signal When the reception is not optimal consider moving the antenna and box to a location with better reception Another solution to less than optimal reception on your mobile phone is moving DECT Messenger to another place You can also consider a distributed setup running the eSMS and SMS service on a different PC 6 Send and receive an SMS message manually to ensure operator connectivity for SMS messaging runs properly 7 Remove the SIM from your regular mobile phone and insert it in the Siemens TC35i module Refer to the documentation that comes with the Siemens TC35i module for installation details SMS service When you install eSMS the eSMS module the SMS_ service module SMS_ service ini and SMS_service exe are installed in the directory C GOPHO Messenger Net Exe The SMS_ service module is a separate process and communicates with the GSM box 224 DECT Messenger Installation and Commissioning
174. indow 10 Click Next to begin the installation You may be prompted to insert the Windows installation CD DVD during this step 11 Click Finish to complete the installation You may be prompted to restart the computer Installing IIS on Windows Server 2008 Windows Server 2008 R2 Windows Server 2008 R2 platforms introduce the concept of server roles and server features On these operating systems IIS is built into the Web Server role while SMTP Server functionality is a server feature that runs on top of the Web Server role Use this procedure to add the Web Server IIS role on a Windows Server 2008 R2 server 1 Go to the Server Manager window This window automatically opens when the computer is started If it does not open right click the Computer icon on the desktop and select Manage 2 In the left pane select Roles The right pane is updated with the server roles currently installed as shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 27 Preparing the Operating System E Server Manager M x Ele Aton yew Help 2m B ia Server Manager PHILIPSX64 gt a gi Features at PB gostes View the health of the roles installed on your server and add or remove roles and features 4 gf Configuration fi 3 ES orage Roles Summary z Roles Summary Help Roles 0 of 17 installed Ip Add Roles CQ Last Refresh Today at 2 09PM Configure refresh Figure 9 Server Man
175. ing DECT Messenger software ensure that the following preconditions are met The computer and operating system are prepared as described in Preparing external devices on page 17 and Preparing the Operating System on page 25 e Any third party software for modules that you intend to use such as National Instruments software is installed as described in Installing third party software on page 31 Installing DECT Manager 1 Insert the DECT Messenger product DVD The DVD Main Menu window appears If the Main Menu does not appear double click D Autorun exe where D is the drive letter of your DVD drive 2 Select Server from the DVD Main Menu The Requirements Setup Wizard checks that the server meets the configuration requirements as shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 37 Install DECT Manager 6 Requirements Setup Wizard X System Configuration Check Checking the system for installation requirements gi Status Message J Success Success Success V System Memory Requirement S Pending Restart Requirement V Windows Operating System Requirement Requirements Statistics E Q s 3 Total 0 Fail DESS 3 Success 0 Waning Figure 13 System Configuration Check window Note If the Pending Restart Requirement check fails for example due to a conflict with other installed software click Cancel to stop the installation
176. ing information W eLOCATION SOPHO Messenger Net v4 0 0 eKERNEL eLOCATION Logging Logging ERSE S INF TCP Teale Parn 01126 FT alc remote AFT 03203 eKERNEL oO TCP lt xml gt lt c fgrqs gt lt app1 gt eLOCATION lt appl gt lt site gt 1 lt site gt lt cfarqs gt lt xml gt I TCP lt xml gt lt cfgrpy gt lt la_ address gt 192 168 32 10 lt la _address gt lt la_port gt 1025 lt la_port gt lt c S INF TCP local port 01127 connected with remote port 01025 DCC Application eLOCATION SOPHO Messenger Net v4 0 0 started with parameter gt I EE Data arrival 223 bytes received from eKERNEL 00032 18 36 37 8 Figure 152 eLocation configuration logging tab DECT Messenger Installation and Commissioning Book 1 March 2012 209 Module LOCATION Program activity When the startup phase is done LOCATION has two permanent socket connections e One socket connection is established with the eKERNEL and is used to exchange location requests and location reply data flow e The other socket connection is established with the DAP Controller PC DCC and follows a proprietary protocol to retrieve location information of SIP DECT extensions The link with the DAP Controller exchanges data on regular time interval so both parties can verify the activity of the remote party This guarding is typically represented by the informational message Data arrival 1 bytes received from DCC When t
177. ion process for both outbound and inbound messages DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Configuration SOPHO Messenger Net eConfig Warming Configurator is started without command line soph ia are Check the command string in the target value in properties of the shortcut _Lancel_ Please confirm to start this session with the following SOPHO Messenger Net a is Figure 188 Sign on to DECT Messenger configurator DECT Messenger Installation and Commissioning Book 1 March 2012 235 Module eSMS eCOMIG 2 9 10 befmi LOCAL Fie View esms arca lBS 1 IP address SMS server Outbound port SMS Ser 127 0 0 1 29081 G SOPHO Messenger Net ae License information E G Site Site 1 Areas Modules E lf AP E cASYNC a eBACKUP qf eCAP S oCSTA eDMSAPI eESPA i gy eGUARDIAN Hd el a eLOCATION Bl esms Fe AS n A E eSMTP CLIENT Wl eSMTP SERVER Hg eSNMP i eTM Hefe eVBVOICE et ewEB flip Al TCP Clients All alarms All users 44 Groups and devices a Request informetion received 21 59 40 Figure 189 eSMS area IBS 1 236 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com port SMS Server March 2012 Configuration Module eSMS E SiteID 1 _ eSMSI_Prefiz_st e5MSI_Type_str eSM5I_ C
178. is normally carried out through configuration requests cfgrqs from the module to eKERNEL and configuration replies cfgrpy from eKERNEL to the module As a result third party developers must provide their own DECT Messenger Installation and Commissioning Book 1 March 2012 65 Module eAPI configuration techniques through registry INI files database command line parameters and so on to control the behavior of their applications Basic architecture The architecture of eAPI is embedded in the eKERNEL module The eAPI interface refers to the ability of eKERNEL to provide a TCP server which listens to a specified port and receives TCP sockets packages that contain message requests Therefore when building an eAPI based third party product you require an application that acts as TCP client and establishes a sockets connection to the eKERNEL module which acts as TCP server Depending on the eKERNEL settings the sockets connections are kept open or are closed after reception of a request When the socket is kept open the port remains allocated to the connected client This is suitable for implementations where a dedicated connection is required If multiple clients must address the same eKERNEL port Avaya recommends that you close the socket after each ad hoc request With this approach a single port can serve to accept message requests from multiple input sources Message format Message requests to eKERNEL must be formatte
179. ite N A Then lcl_re MsgBox eAPI could not start Parameter Site xxx missing in command strin g vbCritical eAPI SOPHO Messenger Net Unload Me End Tf If g_ekernel_remote_address N A Then lcl_re MsgBox eAPI could not start Parameter eKernel address xxx xxx xxx xxx m issing in command string vbCritical eAPI SOPHO Messenger Net Unload Me Eno fr If g_ekernel_remote_port N A Then ae Wie lcl_re MsgBox eAPI could not start Parameter eKernel port xxxxx missing in com mand string vbCritical eAPI SOPHO Messenger Net Unload Me EmDee LE g_log_drive N A Then lcl_re MsgBox eAPI could not start Parameter Log drive x missing in command st ring vbCritical eAPI SOPHO Messenger Net Unload Me EDE LE Len g_log_drive lt gt 1 Then lcl_re MsgBox eAPI could not start Parameter Log drive x is invalid in command string vbCritical eAPI SOPHO Messenger Net Unload Me Ene ei Update screen labels lab_ekernel_remote_address amp g_ekernel_remote_address lab_ekernel_remote_port amp g_ekernel_remote_port Initialise eAPI screen fields With cbo_set_or_reset Clear AddItem SET AddItem RESET ListIndex 0 End With With cbo_remove_after Clear AddItem SENT AddItem RESET AddItem CALC eAPI_form 4 ListIndex 0 End With Set socket state indicator to defaults
180. ith the option remove after sent For MCP alarms the group is MCP and the alarm description is MCP Messages are sent with the option remove after sent The message is retrieved from the remaining part of the line after FIRE or MCP For example FIRE FAP 1 BLOCK 2 LOWER GROUND FLOOR Z returns the message FAP 1 BLOCK 2 LOWER GROUND FLOOR Z M TECH The valid manufacturer is M TECH and the valid model is ESPRESSO Table 7 Sample M TECH data lt 00001 This is a sample message gt The first field starts between lt and in the example 00001 The second field starts between and gt in the sample M TECH data message DECT Messenger Installation and Commissioning Book 1 March 2012 107 Module eCAP NIRA The group is identified by the first fields for example 00001 and the message is identified by the second field This is a sample message Currently alarms are sent with alarm description PO and sent with option Remove after sent The valid manufacturer is NIRA and the valid model is BASE Nira is based upon installation Eeuwfeestkliniek Antwerpen 20010110 00 00 02 I 22 37 0781 10 6 416 C 20010110 00 00 12 I 22 37 0784 10 6 419 C 20010110 00 00 12 I Tuesday 9 JANUARY 2001 20010110 00 00 12 I 20010110 00 00 12 I TIME ADDR LINK S P CODE CALL INFO ID MESSAGE 20010110 00 00 12 I 4 4 4
181. lO 0 TCP lt xml gt lt cfgrqs gt lt appl gt eI0 lt appl gt lt site gt 3 lt site gt lt version gt 2 0 6 lt ver sion gt lt cfgrqs gt lt xml gt 25 10 2001 10 41 37 I TCP lt xml gt lt cfgrpy gt lt manufacturer gt NATIONAL INSTRUMENTS lt manufacturer gt lt model gt BASE lt model gt lt mod_cnt gt 3 lt mod_cnt gt lt mod_01 gt FP AI 100 lt mod_01 gt lt url_01 gt opce National Instruments OPCFieldPoint FP Res FP AI 100 1 Channel lt url_01 gt lt cnt_01 gt 8 lt cnt_01 gt lt mod_02 gt FP DI 300 lt mod_02 gt lt url_02 gt opce National Instruments OPCFieldPoint FP Res FP DI 330 2 Channel lt url_02 gt lt cnt_02 gt 8 lt cnt_02 gt lt mod_03 gt FP DO 401 lt mod_03 gt lt url_03 gt ope National Instruments OPCFieldPoint FP Res FP DO 401 3 Channel lt url_03 gt lt cnt_03 gt 16 lt cnt_03 gt lt ai_01_01_min_s gt 00 000000 lt ai_01_01_min_s gt lt ai_01_01_min_r gt 00 000000 lt ai_01_01_min_r gt lt ai_01_01_max_r gt 12 000000 lt ai_01_01_max_r gt lt ai_01_01_max_s gt 20 000000 lt ai_01_01_max_s gt lt ai_01_02_min_s gt 00 000000 lt ai_01_02_min_s gt lt ai_01_02_min_r gt 00 000000 lt ai_01_02_min_r gt lt ai_01_02_max_r gt 12 000000 lt ai_01_02_max_r gt lt ai_01_02_max_s gt 20 000000 lt ai_01_02_max_s gt lt ai_01_03_min_s gt 00 000000 lt ai_01_03_min_s gt lt ai_01_03_min_r gt 00 000000 lt ai_01_03_min_r gt lt ai_01_03_max_r gt 12 000000 lt ai_01_03_max_r gt lt ai_01_03_max_s gt 20 000000 l
182. lay 0 Received Local 2 Status Processing confiquration request recewed from eKerrel Sert J Remote 1 Meg J pes WD Data rival 734 bytes received from eKEANEL none 172117 G Figure 77 Field model containing VSK Restrictions e Configure eESPA as Control station value No The remote system is then control station and handles polling e Set the field Polling to No e Only one data block is received at a time In the example shown in Figure 78 2 ENQ with response EOT on page 127 it is assumed e The remote system master is using address 1 e The local system slave is using address 2 Different application logic and code is used when model VSK is used mainly because different polling is supported The original code assumes polling is 2 ENQ with the response EOT 06 06 2007 18 38 11 I COM 2 06 06 2007 18 38 11 I COM ENQ 0670672007 18 38 11 0 COM EOT Figure 78 2 ENQ with response EOT VSK implementation also supports local polling of the control station Note that 1 ENQ EOT is received and no response is made DECT Messenger Installation and Commissioning Book 1 March 2012 127 Module eESPA 06 06 2007 18 38 11 I COM 1 06 06 2007 18 38 11 I COM ENO 06 06 2007 18 38 11 I COM EOT Figure 79 1 ENQ EOT no response For example the FalconNet fire detection system alternatively polls itself and then the remote system eESPA as shown in Figure
183. le Description Additional Info type FP 1601 Control module with IP Interface module between the I O modules and interface DECT Messenger Controls up to 9 I O modules directly FP 1000 Control module with Interface module between the I O modules and V 24 interface DECT Messenger Controls up to 9 I O modules directly Up to 24 FP 1001 modules can be connected using RS485 bus to expand the system with extra I O modules FP 1001 Expansion control Must be connected to the RS485 interface on the module FP 1000 One FP 1001 can control up to 9 I O modules The maximum number of FP 1001 modules one RS485 bus is 24 PS 2 Power Supply 24 Volts DC Table 3 I O modules overview Module Description Additional Info type FP AI 100 Analogue input 8 Analogue inputs each can be set to one of the following ranges 30V 15V 5V 1V 0 30V 0 15V 0 5V 0 1V 20mA 0 20mA 4 20mA FP DI 300 Digital input 8 discrete input channels These inputs are sinking inputs for 24VDC FP DI 301 Digital input 16 discrete input channels These inputs are sinking inputs for 24VDC FP DI 330 Digital input 8 discrete input channels Universal inputs work with any voltage from 5V TTL up to 250VDC VAC Compatible with sourcing sinking or power sensing applications FP DO 400 Digital output 8 discrete output channels Max 2A per output max 8A per module Maximum voltage 30VDC FP DO 401 Digital output
184. ler The devices are entered in the system as shown in the following two figures DECT Messenger Installation and Commissioning Book 1 March 2012 217 Module eLOCATION kg Module eLOCATION xi Site ID 1 Site description Site 1 Default LOCATION D Area ID 2 efault eLOCATION Area description SIP DECT MERA i Location Agent address 192 168 32 10 Location Agent port 28008 i General timeout 10 i Retry count 5 Retry interval 10 Polling interval 60 B Board definition gt gt gt RPN definition Comments eLOCATION configuration for SIP L amp Inbound call handling gt gt gt eCSTA inbound event i gt gt gt eDMSAPI inbound event gt gt gt eLOCATION Inbound result Interface with eKERNEL Delete Refresh OK Cancel Figure 162 Module eLOCATION board definition fi Module eLOCATION BOARD x Site ID 1 Area ID 2 DNA 3000 EE E oard number 00 Comments Default eLOCATION_BOARD conf Board number identifies the home board of the portable part The board number in this address information element must be in the range 01 32 SNMP style addressing 8 Board number The current value for this parameter is 00 Valid values for this parameter are 00 01 02 03 04 05 06 07 08 09 10 11 12 Delete Refresh OK Cancel Figure 163 Module eLOCATION board 00 definition 218 DECT Messenger In
185. llation and Commissioning Book 1 March 2012 13 System requirements 14 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 4 Installation steps The Avaya DECT Messenger installation steps assume that all operating system and hardware requirements are met The following flow chart summarizes the installation and setup procedures A Prepare External Devices B Prepare Operating System j C ipstall gaci Earty Software D Install Database Server Install DECT Messenger i Server F Configure DECT Messenger hiiia Legend G Install DECT Messenger D Required Client s a Optional Figure 1 DECT Messenger installation steps For more information about each step refer to the following topics e Preparing external devices on page 17 e Preparing the Operating System on page 25 e Installing third party software on page 31 DECT Messenger Installation and Commissioning Book 1 March 2012 15 Installation steps e Installing SQL Server on page 32 e Installing DECT Manager on page 37 e Configuring DECT Messenger on page 46 e Install a DECT Messenger Client on page 41 16 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 5 Preparing external devices This chapter provides information on preparing external devices Integration with IP DECT Manager You ca
186. llation and Commissioning Book 1 March 2012 205 Module eLICENSE 206 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 23 Module eLOCATION Important Due to the ongoing development of the DECT Messenger product suite some modules that provide additional functionality may become available after the initial release of DECT Messenger 4 0 The following modules are described in this document but are not available at initial General Availability e eFR e eLICENSE e eLOCATION eSMS e eSNMP e eVBVOICE The eFR module is an add on module and is licensed separately through the eLICENSE module Some of the modules listed in this attention box are available only on a site specific basis The eLOCATION module is used with SIP DECT systems only It collaborates with eDMSAPI and eKERNEL to allow location detection of SIP DECT extensions The eLOCATION module receives message location detection requests from the eKERNEL module and responds with location reply results to eKERNEL Then eKERNEL resumes processing and dispatches the resulting alarm message to the defined group of users Each eLOCATION connects to a DAP Controller and communicates with it to find out the last used RPN for the requested SIP DECT extension This involves a sockets connection between eLOCATION and the DAP Controller For this connection eLOCATION is the TCP client and the DAP Controller is TCP
187. lls the controlling station to stop polling The controlling station accepts this request by sending an ACK to the slave that wants to send data When it receives an ACK from the controlling station the slave becomes temporarily master station Only a master station is able to send data blocks A master station always sends data a slave always receives In this scenario the controlling station becomes temporarily a slave Every eESPA module has a status bar with some additional information about the actual communication situation e The label Receiving shows the timestamp and the latest incoming databits Values that can appear on this label are as follows ACK NAK EOT address ENQ SOH start of data and data e The label Sent shows the timestamp and the databit that was last sent Values that can appear on this label are as follows ACK NAK EOT address ENQ SOH start of data and data The Local address field shows the defined value of eEESPA_LocalAddress_nin the eESPA table Avaya recommends that you set the controlling station local address to 1 The field eESPA_ControlStation_b in the eESPA table defines whether this module is a controlling station or not In the DECT Messenger model a module always communicates with one other module master to slave or point to point The address of the other station is defined in the eESPA_ExternalAddress_n field in the eESPA table In the case of a non controlling module defined by
188. lows you to send e mail to users of any domain Contact the e mail infrastructure administrator to discuss the parameters and to determine if an adjustment of the e mail server is necessary Destinations type SNMP The following figure illustrates Destinations type SNMP DECT Messenger Installation and Commissioning Book 1 March 2012 157 Module eFR lt Destination id eSNMP type SNMP description Messenger Net address 127 0 0 1 port 162 community public oid 1 3 6 1 4 1 28088 32 1 generic 6 specific 1 gt Figure 95 Destinations type SNMP The following parameters are specific to SNMP e The parameter description refers to the name of the destination party and allows you to assign a destination system name For example you can enter the name of the SNMP receiving infrastructure e The parameter address refers to the SNMP server IP address Contact the SNMP receiving infrastructure administrator to obtain this value e The parameter port refers to the SNMP server port number The default value usually used is the well known port number 162 Contact the SNMP receiving infrastructure administrator to obtain this value e The parameter community identifies the community for example public e The parameter oid identifies the enterprise OID for example 1 3 6 1 4 1 28088 32 1 e The parameter generic identifies the generic trap identifier for example 6 e The parameter specific identifies the spe
189. lt csta_api_address gt lt csta_api_port gt 59000 lt csta_api_port gt lt external_seat_cnt gt 3 lt external_seat_cnt gt lt external_port gt 2010 lt external_port gt lt csta_pbx_address gt 10 110 49 171 lt csta_pbx_address gt lt csta_pbx_port gt 2555 lt csta_pbx_port gt lt csta_licence gt Mes senger lt csta_licence gt lt guarding_intv gt 60 lt guarding_intv gt lt guarding_Retry_intv gt 20 lt guarding_Retry_intv gt lt eKernel_Seat_cnt gt 10 lt eKernel_ Seat_cnt gt lt GeneralTim eOut gt 15 lt GeneralTimeOut gt lt Ack2TimeOut gt 30 lt Ack2TimeOut gt lt DataPathDelay gt 2 lt DataPathDelay gt lt network gt ETHERNET_DMC lt network gt lt pbxtype gt DMC lt pbx type gt lt IoReg_cnt gt 9 lt IoReg_cnt gt lt IoReg_0001 gt 860 lt IoReg_0001 gt lt IoReg_0002 gt 861 lt IoReg_0002 gt lt IoReg_0003 gt 862 lt IoReg_0003 gt lt IoReg_0004 gt 999 lt IoReg_0004 gt lt IoReg_0005 gt 869 lt IoReg_0005 gt lt IoReg_0006 gt 868 lt IoReg_0006 gt lt IoReg_0007 gt 867 lt ToReg_0007 gt lt IoReg_0008 gt 866 lt TIoReg_0008 gt lt IoReg_0009 gt 865 lt ToReg_0009 gt lt log_path gt C SOPHO Messenger net lt log_path gt lt log_days gt 14 lt log_days gt lt cfgrpy gt lt xml gt PBX type DAP controller 28 06 2004 13 58 55 I TCP lt xml gt lt cfgrpy gt lt seat_cnt gt 20 lt seat_cnt gt lt msg_dly gt 3 lt msg_dly gt lt csta_api_address gt 10 110 50 140 lt csta_api_address gt lt csta_api_port gt 59000 lt csta_ap
190. mdincecsonecannanaces 158 hardware modules ccceccesesceeeeeeeseseeseeeseeeeesneees 19 NETSTAT SOCHION o 148 Network information ccccccssseceeceeceeeeseeeeaeeseeeeaaes 13 I New in this release cccccecesseececceaseceeeeanseeeeceanees T NRA a cect neteceanesteeasseenecens 108 A ee i p Notification Aicteneas de arte Qict hoa teicher 147 149 Initialization of LOCATION 207 Notification Methods cccccceseeeeeeeesseeeeceaeeeeanes 152 Input and output module sssrini 9 Install module eLICENSE ceeceeeceseseseceseeeeseseeeens 201 O Installation DECT Manager cceceeseseesseeeeeeeeeeees 37 Installation steps 20 0 0 ccceceeceeceeeeeeeeeeeeeeeeaeeeeeeeeeeeeeeeees 15 OLV VAN VREDE coccccccccccccccecccccccccccccccecececececceceseecees 112 Installing CFR osc eee 150 OM section saceseccsastesccscusblesssedstdsecsusveceracansecdeueneatatees 148 Invalid license key warning eee eee 204 Operating System ccccccecccsescsesescecsestsceeetsteseeeeeees 25 Outbound MESSAGES ceccccccececeeeeesseeeeeteeeeeeeeeeees 223 L Outbound messaging eceeeeeeeeeeeeeeeeeeeeeeeeeeeetaeeees 230 Landis Steafa interface cccccccccecssssssseesseeeeeeeeees 109 Sere iM eee eae ier eigen emncts 32 244 DECT Messenger Installation and Commissioning Book 1 March 2012 P PING e 158 PING Section wissiediccticaiadesaviscandecisstecstaiecuataneveareitiaiess 148 Planning destinations
191. me drive You are notified if different information is found You are notified when the drive is not ready and you are also notified when the drive is ready e PING section The PING section verifies if the PING command is successful in finding a destination address For the destination addresses you can enter The loopback adapter addresses or local IP addresses to verify local TCP stack and network resources Aremote IP addresses to ensure that the network is responding on ICMP level The status is compared with a previous run for the same destination You are notified if different information is found You are also notified when the PING is not responding You are notified when the PING reestablishes a response e NETSTAT section The NETSTAT section verifies if a TCP Server is in a listening state by determining whether a defined port has a socket in a listening state For example when an SMTP server is present listening on socket 25 it can be verified if a socket is listening for inbound connections or not Similar tests are possible for all kinds of TCP Servers on well known ports such as Telnet 23 HTTP 80 HTTPS 443 and so on or user defined ports It is also possible to verify that a TCP connection is established on a predefined port Typical usage verifies that a connection that needs to be established continuously is available The status is compared with a previous run for the same port You are notified if
192. ments products What do you want to do a Manage my devices and interfaces g Manage my installed National Instruments software A Manage virtual channels or tasks for my devices 4 Create scales for my virtual instruments ivi Configure my M instrument drivers Eo importiexport my device c onfiguration file B Note Some categories are device specific For example the M category appears only if you have IVI installed For more information about using MAX select available help categories from the Help menu Ifyou need further assistance or want to know more about your device visit the National Instruments Technical Support Web site Figure 12 National Instruments Measurement amp Automation Explorer screen For details on how to configure the Field Point modules with Measurement amp Automation Explorer software refer to the National Instruments documentation DECT Messenger Installation and Commissioning Book 1 March 2012 35 Installing third party software 36 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 8 Install DECT Manager This chapter describes how to install the DECT Messenger software If you need to deploy one or more DECT Messenger software modules on a different PC you can find the steps for installing additional DECT Messenger copies in client mode in the Installing DECT Messenger Client subsection Before you start Before install
193. moz 9600 N 8 1 BEL NCCEE IS Provider SMS PROXIMUS 00475161622 F I 0K To 32475353215 O ATDT 00475161622 Message rest message a S Waiting 60 seconds for cormnection ATDT 00475161622 00009 14 25 33 Figure 42 eASYNC tab 84 DECT Messenger nstallation and Commissioning Book 1 March 2012 Comments infodev avaya com Logging Logging Logging information is available both on screen and in logging files You can view on screen logging through the Logging tab BX eASYNC SOPHO Mes eKernel eASYNC senger Net y Logging s E s g T a S o E I INF ERR pen ue TCP SIERS TCP INF Application eASYNC SOPHO Messenger Net v2 0 6 started with parameters a TCP error 10061 Cornection is forcefully rejected eKERNEL TCP local port 01842 connected with remote port 03105 eKERNEL lt xml gt lt cfgrqs gt lt appl gt eASYNC lt appl gt lt site gt 3 lt site gt lt version gt 2Z 0 6 lt version gt lt c xml gt lt cfgrpy gt lt interface_cnt gt Z lt interface_cnt gt lt com_port_01 gt COM02 lt com_port 2 lt xml gt lt msgrqs gt lt id gt 00005 lt id gt lt type gt SMS lt type gt lt provider gt PROXIMUS lt provider gt lt t COMOZ opened with settings 9600 N 8 1 COM AT amp COSO 3 COM ATSCOSO 3 COM COM OK oe as eASYNC ended abnormally No carrier while waiting for connection 00052 14 26 16 Figure 43 eASYNC Logging ta
194. n 192 168 17 74 30160 GK Start gatekeeper address section 192 168 17 200 5060 XDS Start SIP section b2b_ua yes CONFIG Start of static config section CONFIGFILE replace IPCONFIG replace The TCP IP port for Messaging is located in the DS section The IP address of the DAP Controller PC is followed by a port number range The port for LRMS messaging is the first port number plus 1 In the above example the LRMS port on the DAP Controller is port 28001 This is the port number that must be entered in the DECT Messenger eDMSAPI module along with the DAP Controller IP address The port number for Location Detection is the first port number plus 8 In the above example the Location Detection port on the DAP Controller is port 28008 This is the port number that must be entered in the DECT Messenger eLOCATION along with the DAP Controller IP address National Instruments Analog Digital Hardware To use Digital Input Output and Analogue Input functionality in message processing DECT Messenger requires National Instruments FieldPoint FP hardware modules Figure 3 National Instruments FieldPoint hardware modules DECT Messenger supports the following types of IO modules e Control modules e 1 O modules The following tables provide an overview of these modules DECT Messenger Installation and Commissioning Book 1 March 2012 19 Preparing external devices Table 2 Control modules overview Modu
195. n connect DECT Messenger to an IP DECT system The communication between DECT Messenger and the IP DECT system is only for LRMS to or from the DECT handsets DECT Messenger uses the CTI port on the IP DECT system to send and receive LRMS messages This port does not support CSTA The connection consists of a TCP IP connection between the DECT Messenger and the IP DECT system However the IP DECT system is normally placed in a separate VLAN that is used only for VoIP Therefore in general the connection between DECT Messenger and the IP DECT system is established using a VLAN router Before installing DECT Messenger you must verify that the VLAN router allows traffic from the DECT Messenger to the IP DECT system The IP DECT system can be connected to CS 1000 The following subsections give a description of the connections Integration with Call Server 1000 The following figure shows an IP DECT system configured with CS 1000 and DECT Messenger As shown here DECT Messenger can be connected directly to the VLAN which is used for VoIP or it can be connected to that VLAN via a VLAN router Connection via a VLAN Router requires that the VLAN Router allows traffic between the DECT Messenger PC and the DAP Controller PC IP DECT system DECT Messenger uses a TCP IP port on the DAP Controller DECT Messenger Installation and Commissioning Book 1 March 2012 17 Preparing external devices DAP Controller oco Call Server 1000 See
196. nel elO Logging Connections m eKernel Configuration Local 127 0 0 1 4872 Manufacturer J NATIONAL INSTRUMENTS Remote 127 0 0 1 3108 Model BASE J Status Connected 02 FP DI 300 03 FP DO 401 mela J NAA N A J N A J N A J Log path C SOPHO Messenger Net J J Log days i ae i Data arrival 1913 bytes received from eKERNEL 00043 22 45 02 Figure 130 elO Connections update elO Modules Select the elO tab to see a panel with details of the available modules and contacts Use the drop down list at the right hand side of the window to select the module to view Analogue input When you select an analogue input module FP Al 100 a window similar to the one in Figure 131 elO analogue input modules on page 183 is shown For each module a graphical display shows the available contacts The analogue input also shows the analogue levels 182 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Analogue input 42 eIO SOPHO Messenger Net v2 0 6 eKernel elO pe 0 02 03 04 05 06 07 08 o1 FP AI 100 gt J URL opc National Instruments OPCFieldPoint FP Res FP Al 100 1 Channel J Before 00000000 J Module FP 4I 100 module 01 After 00000000 Change NATIONAL INSTRUMENTS a Module 00 Contact 00 Value 00 000000 03829 23 48 08 Figure 131 elO analogue input modules For each module the URL is sh
197. nents If you intend to use DECT Messenger software modules that are mentioned as not available in the warning messages cancel the installation Then install the required components as indicated in the Preparing the Operating System and Installing Third Party Software chapters 6 Click Next 7 When prompted to restart the system click Restart Now Wait until the PC is restarted and the installation continues 8 When the Welcome to the InstallShield Wizard for Messenger Net window appears click Next The Setup Type window appears DECT Messenger Installation and Commissioning Book 1 March 2012 39 Install DECT Manager 9 10 11 12 Select Complete to install all available components in the default installation path and click Next to continue The Database Installation window appears as shown in the following figure ie Messenger Net InstallShield Wizard Database Installation Select database server and authentication method Use built in Microsoft Access database C Use an existing Microsoft SQL Server tabase server to install to From the list below or click Browse to see a list of a abase servers You can als spe way to authenticate your login using your current credentials or a SQL Login ID and Password Databa rver 7 Connect usir o 1 5 if g rou amp Se sing the nd p jt ER Password Ins i o _ Figure 15 Database Installation selection window
198. nformation into the server registry A Registry Editor confirmation message appears asking for permission to merge the data into the registry Click Yes to confirm A message box appears informing that the merge was successful Click OK to acknowledge and continue Note When configured for using a distributed environment with additional DECT Messenger clients installed on other PCs eCONFIG generates additional registry files for each environment You must copy these files and repeat the above steps 62 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Configuring DECT Messenger on the client PC corresponding to that specific environment after stopping eTM and other associated processes 12 Start eTM to bring the environment online The following figure shows an example of eTM running configured modules eTM Messenger net v4 1 5 Site 1 Environment LOCAL CI xj 2 Messerqcor Not O Messergen Net I Mossergor Not E Task Manager Ste 1 E Mesrergei Net Merrergei Net Envronment LOCAL CST4 Service GASYNC Port 3106 eCAP Port 31 eCAP Port 3103 oCAP Por 3104 fe Messerge Nel Messergei Net E Mossergor Not Messerge Nel E Mesrerge net E Mossorgor Not E Messergei Nel NET Pot 3118 E Merrerge Net eSMS Port 3117 201103301 61012 PIO 000003604 Tack Messeng Ne eLOCATION Port 3115
199. ng figure shows an example of a site configuration error Site ID 1 Site Description NEC Administrator name Administrator Administrator emal admey nec uniied com eKernel IP address 127 0 Garbadge collection 600 Connection string CFG ProvidereMicrosoft Jet Connection string DATA Provider Microsoft Je Path eL0G C Program Fies x85 NEC Mess Number of days to keep eLOG fies 30 Logging Watchdog 8 Corfo E Komel iP address The curent value for this parameter is 127 0 0 1 Figure 25 Site configuration error message 6 Enter a new value for the selected item 7 If necessary select another item and modify it using the same procedure 8 Click OK to store the changes in the local copy of the database Note The type of input control text box combo box or grid depends on the item selected Removing unused modules The database configuration deployed by the installer contains a variety of input modules already preset with working default parameters For modules which you do not intend to use or have not been installed Avaya recommends to delete their configuration entry that appears in eCONFIG This will avoid could not launch module errors that appear when using eTM Task Manager module during daily operation 54 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Configuring DECT Messenger Deleting a module 1 Expand
200. nnssanrsuaaianakinaiembenibdaannakabs 89 Chapter 14 Module ists vs ahead ca nh nenna anaana aa aaan 97 DE asst E A E E T S E E A A 97 E A E E aia E TE E RE S E E AET EETA A TS 97 Fanctonaldeseriphi nasa a 100 ARGIN ae srt alps A ead aati TEA ES adler csueraaleiriie 101 ARME CHinni E aiad aenepatled tsi A N 101 BENA Gurnita A A S A A auea aes ladeatine 104 2 EE E EAA E A ADT E IT L er ect A A E EA A A te error E A et ert crn tt rrr 104 DEN T oriire AEE EE 105 Mae e ea a A A ap sor aussie estas Gira ae i sian aad EA E O cde EE E E E E E 106 Moce IOIEN ENGA seo N 107 MEE CR ia a TU RerNT on Cr emmeny er Sree ernie oer enter oery emer ease etree ar 107 iee E E E E E E A E R E E E E E A E T E 108 STEA F Aprene S ERS ERN ANEA 109 TELE Se oran O err ree n One ren Terre iat creer rer tererrn ete errr eer rere errr creer er 109 TO eee en etre reer tee rere reer re rere Terr prer Terr Pree ter Terer errr Terey terry rere reer rere rrr errr TT errr rye 112 e E siete A E E E E E E E N N EE E T 112 WORVAL Disrann a e a E R a E TA derives 116 EE aE A A A E A A E A A E E E A T 118 Chapter 15 Module GES PA iicsisittitisiscsaccadsatasandnctadandsasancsdnadadandsatasaadiasandndsndadesdaciaddaannnann 119 Menutacttrer ESPA and model BASE unssin kinada ai aanak 119 ET PUY E E E E E E A E E R 119 coca ace cd crater T a S S 119 FU NCHS deseriphiO Msro aN E NEONA CATA arans 123 E E E TAN AE A A A A N E A A AOA E O ATAA 124 aia alg o A A E E A A A
201. nprocessed The intended use is oriented towards an infrastructure capable of receiving SNMPv1 traps and performing further actions The DECT Messenger suite features a module eSNMP that is optimized for this functionality DECT Messenger can receive the SNMPv1 trap and reliably process it through several notification channels including DECT Messaging SMS messaging Interactive Voice Response discrete contacts e mail and so on In addition the software allows detecting if message reaches its destination and optionally needs end user confirmation DECT Messenger can retry and escalate to alternative destinations The SMS destinations refer to notification based upon SMS messaging to mobile phones SMS destinations requires at least the SMS_ service engine and a supported GSM box with a SIM card You can add SMS destinations with such an infrastructure to run in stand alone mode or as part of an existing DECT Messenger infrastructure NET destinations refer to the notification based upon named pipes transport towards the messenger service that is part of the Windows operating system The functionality of NET destinations is similar to the NET SEND command found in the Windows operating system NET destinations allows you to send a Windows pop up message to a Windows PC The depending messenger service must be enabled DECT Messenger Installation and Commissioning Book 1 March 2012 149 Module eFR and active on the destin
202. nt Nov 1984 reference JMJ182 NB 12B and 1SO1745 Information processing basic mode control procedures for data communication systems Functional description In general eESPA is designed to provide eKERNEL with paging information This is carried out using a lt msgrqs gt message request For some interfaces eKERNEL must send feedback to the paging system a process that is handled through lt msgrpy gt message reply request lt xml gt lt msgrqs gt lt id gt 00786 lt id gt lt group gt 1234 lt group gt lt call_type gt 3 lt call_type gt lt transmission_nmbr gt 1 lt transmission_nmbr gt lt alarm_cnt gt 1 lt alarm_cnt gt lt message_01 gt NURSE ROOM45 lt message_01 gt lt beep_code_01 gt 1 lt beep_code_01 gt lt priority_01 gt 2 lt priority_01 gt lt msgrqs gt lt xml gt Figure 72 msgrqs message request Every lt msgrqs gt message belongs to a group and has a specific group ID A group contains one or more requests For every message request in a group a data block is created A data block consists of a header record separators unit separators and data that is retrieved from the message request Every data block also contains a specifically calculated checksum block check character ISO 1155 After sending the data over the serial line the receiving side uses the block check character BCC to determine whether data has arrived properly or not In the event of a successful delivery the receiving side ans
203. ntosnaeiadest annie dees enniszessetseuictertecutanatatepareantenianentetpuiaes 49 Usmo CONFIG Connguralo ssrin e aa ANSE RON AAE REENA ONONE 50 Using eCONFIG in a CistibUted envionment sisisisrisiiainnaisviniranadaiiidaaeiduoyi aaaeaii aiie 63 Chapter 10 Module CAP asisccsisiicndiassnansssasninicanhoninceatinasdaanandssdasaududahiedeceabanincsmaddadniundnetanate 65 Meie otan a E E E T E E TE A C E EE E A E T 65 W e NG E E N A E T 65 inpoi pronam tictionraiy on sina NA ae aia tees 65 Weke ee ai UIT SHANG sa cso E AE E E E E T 65 ECE E L E EE IAA E I E NA AA EEA PAA O A A TE 66 Messana Om aieia 66 Mroducdion to a ocr oe ot ea ren aS ere entree Tr cree Tr rere Tree rrr Tree Trees 67 Creating a basic sockets client Using Visual Basie ccscccicsdzsccetsnsedsacsscscesseqineseaestannesdacesevespessinicestesstnevsaades 67 DECT Messenger Installation and Commissioning Book 1 March 2012 3 More extended AT ais testes ct So ssinee aaa aa A E OAN A AAE a 69 EE NUNS A EA E E A O E EE E E E E A T 70 Chapter 11 Module eAPI SAM DIG wissiscisansasssnisnsnansunndcasianaiesddcniidenansnanasananeninunnanienbiaiaimane 71 Chapter 12 Module CAS YING ooveisiiscisisascncncesetincssdinanedanasaiaiasandiadasanmiadananisaianeadiaiedanannanane 81 MPN RUE EE E E A E A E E A E E ea eeeataanniude 81 PAGI NGERE conni A EE ai ai 81 cle a E E a are ere ereare cee yerr are ae rr 85 Chapter 13 Module GB ACK UP a sississssisnssscasnseasieccteeitensticmuneheanac
204. ok 1 March 2012 33 Installing third party software Installing National Instruments Field Point and DataSocket This section describes the installation of modules related to the elO component of DECT Messenger You can skip this section if you do not plan use the elO module 1 Insert the DECT Messenger product DVD The DVD Main Menu window appears If the menu does not appear double click D Autorun exe where D is the drive letter of your DVD drive 2 From the DVD Main Menu select National Instruments Field Point 6 0 6 f1 The automated installation begins Wait until it completes 3 Select National Instruments DataSocket 4 7 1 The automated installation begins Wait until it completes 4 Restart the computer 5 Verify that the software was correctly installed by double clicking the Measurement amp Automation shortcut on the desktop The Measurement amp Automation Explorer screen opens as shown in the following figure 34 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com X My System Measurement amp Automation Explorer x Ele Edt yew Tools Help Installing National Instruments Field Point and DataSocket 3 6 Software amp Remote systems E Data Neighborhood a Devices and Interfaces National Instruments Measurement amp Automation Explorer Measurement amp Automation Explorer MAX provides access to your National Instru
205. omments infodev avaya com STEAFA STEAFA Note The Landis Steafa interface was not ordered nor implemented and protocol information is provided on an as is basis Contact your software vendor for implementation 19970403000053 COM 03 04 97 Prio 1 CONTROLLER 00 SYSTEM STAEFA test alarm 19970403000054 COM 00 05 00 COM NICO RS MODU U L EN NORMAAL UIT 19970403000054 COM 00 cos 2000 19970403000154 COM ____ 19970403000154 COM 03 04 97 Prio 1 CONTROLLER 00 SYSTEM STAEFA test alarm 19970403000154 COM 00 06 01 GEEN COMMUNICATIE NICO RS MODU U L EN IN 19970403000154 COM 00 cos 2000 19970403000252 COM ___ 19970403000253 COM 03 04 97 Prio 1 CONTROLLER 00 SYSTEM STAEFA test alarm 19970403000253 COM 00 07 00 COM NICO RS MODU U L EN NORMAAL UIT 19970403000253 COM 00 cos 2000 19970403000354 COM Figure 63 Sample Steafa protocol data TELEVIC The valid manufacturer is TELEVIC and the valid model is PROTOCOL CONVERTOR L xx with xx between 01 and 99 Note The extension L xx is new in release 2 and must be specified The functionality is introduced to obtain more flexibility in message handling The following string handling is performed e Remove leading spaces of the message NUR K100 gt NUR K100 e Append a trailing space to the result DECT Messenger Installation and Commissioning Book 1 March 2012 109 Module eCAP BEERPUT gt BEERPUT e Look up the occurrence of the first space
206. omments str Site description Site 1 p Conin C Default configuration ealD 1 rea desciiption IBS 1 Server IP adcess 127 0 01 Server outbound pot 29081 Server nbourd port 25080 gt gt gt Inbound definitions gt gt gt Inbound access control list Alarm piorty for DTMF confirmation 2 i Silence interval 600 Comments Default SM5 configuration amp Interface with eKERNEL 4 Procram name eSMS O Kemel pert 3117 Socket Keep open Environment LOCAL New Edit Comments Delete Refresh OK Cancel Figure 190 Module eSMS inbound definitions f Module eSMS Inbound xi SitelD 1 Prefix Ares ID 31 Confim Frefis Cortirm O Type IC Comments Default configuration S Prefix The current value for this parameter is Confirm Delete Refresh OK Cancel Figure 191 Module eSMS Inbound DECT Messenger Installation and Commissioning Book 1 March 2012 237 Module eSMS Module eSMS Inbound ACL xi General SitelD 1 Confirm by clip Ares ID 21 E Clip 32479467238 Confirm by clip False Confirm by pircode True Comments Francis Missiaen 8 Confirm by clip The curent value for this parameter True Delete Refresh 0K Figure 192 Module eSMS Inbound ACL f Module esMS xl General Overview JeXERNEL_DEVICE_FORMAT 7 Normal x Subset Clear subset
207. ommissioning Book 1 March 2012 41 Install DECT Manager 7 Select Custom and click Next to continue The Custom Setup window displays allowing you to specify the components you want to install and run on the client PC as shown in the following figure ie Messenger Net Client InstallShield Wizard Custom Setup Select the program features you want installed Click on an icon in the list below to change how a feature is installed m Feature Description Core Addons Tools Configurator Documentation This Feature requires OKB on your hard drive It has 5 of 5 subfeatures selected The subfeatures require 9SMB on your hard drive Install to C Program Files x86 Nec Messenger Net Change InstallShield tee s m Figure 16 Custom Setup window 8 Select the features to install and click Next The Ready to Install window appears 9 Click Install to begin the installation process 10 When the InstallShield Wizard Completed screen appears click Finish When running a DECT Messenger Client installation the following components are not available e eKERNEL and associated core components e Web Administration console e eSMTP Server module 42 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Uninstalling DECT Messenger Uninstalling DECT Messenger DECT Messenger can be uninstalled using one of the following procedu
208. on ayy EATE ee ee ee a Next check in 105 seconds Please wait 14 31 37 E OM ID NEC Philips unit 02 anit 02 address 127 0 0 1 port 23 E bis 50 El NETSTAT ID Mail Server port 25 state Listening ID Wessenger Net eCAP port 3102 stats Established E PING Sys em Loopback addiess 127 0 0 1 court 1 size 32 bytes tmeout 1000 ms Syscem i 3000 address 192 168 1 12 count 1 size 32 bytes imeout 3000 ms Figure 100 Required conditions met for monitor type DISK You define the message and the destinations to be informed in the following circumstances 162 DECT Messenger Installation and Commissioning Book 1 e When the drive is not ready lt DriveNotReady gt Figure 101 Drive not ready e When the drive is ready again lt DriveReady gt Figure 102 Drive ready e When the drive is above threshold usage level lt DriveAboveThreshold gt Figure 103 Drive above threshold usage level e When the drive is below threshold usage level lt DriveBelowThreshold gt Figure 104 Drive below threshold usage level e When the D drive is not ready to be sent as SNMPv1 trap to an SNMP server March 2012 Comments infodev avaya com Monitoring type PING lt Destination id eSNMP type SNMP description Messenger Net address 127 0 0 1 port 162 community public oid 1 3 6 1 4 1 28088 32 1 generic 6 specific 1 gt Figure 105 Dri
209. on and Commissioning Book 1 March 2012 Comments infodev avaya com Hardware installation Hardware installation The detailed installation procedures for the FP modules are in the installation documents located on the DECT Messenger DVD D Documentation Background eIO xxx pdf where D is the drive letter of your DVD drive For the latest version of the documents also refer to National Instruments website at http www ni com Software installation To connect to the FP I O modules DECT Messenger requires third party software components from National Instruments The software consists of two main parts e Measurement amp Automation Explorer software for setting up the configuration of the FieldPoint modules e OPC Object Linking and Embedding for Process Control Server The DECT Messenger elO module connects through the OPC Server to control the I O modules as shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 23 Preparing external devices DECT Messenger Either elO OR FieldPoint Explorer can be active never both at the same time FieldPoint Explorer vw V 24 to FP 1000 Figure 6 DECT Messenger interaction with FP I O modules Important The OPC Server software can be controlled by only one application This means that you can have either the elO Module or the Measurement amp Automation Explorer active but not both Remember
210. ose End Sub Figure 36 Sample socket client code More extended program Refer to Module eAPI sample on page 71 for a detailed source code listing of a more complete implementation of a Visual Basic program that implements eAPI functionality The compiled program eAPI exe and the source code eAPI zip zipped are shipped with the DECT Messenger and the exe is installed when you select eAP module during custom install Note that this code is provided on as is basis and is not intended to be used without modification Usage of the code is the responsibility of the third party developer as all aspects needed to make the code reliable are not implemented The eAPI program is designed to provide the same look and feel as is found in other DECT Messenger modules DECT Messenger Installation and Commissioning Book 1 March 2012 69 Module eAPI Some typical features include e Ability to specify certain runtime parameters of the program by means of the command line parameters in the shortcut such as Site 2 eKernel address LOCAL eKernel port 3209 Log drive C e A menu that provides a queue list that the module can use to handle situations in which eKERNEL is temporarily unavailable e Logging facilities on screen with the option to left click a log entry to see details e Logging facilities to disk in the same directory structure mechanism as used for all other modules Real world examples Using eAPI
211. oup ALL and message ALL DECT Messenger Installation and Commissioning Book 1 March 2012 117 Module eCAP Table 12 RUCA 0000 Brand MG 099 MLD 009 0101 00 01 01 97 Boodschap This datastream results in a SET of alarm description WORMALD_ F with message Boodschap and remove after RESET The group varies depending on the model Table 13 F8000 REV EVACUA groups Model Group BASE WORMALD F L 01 B L 02 Bo L 03 Boo L 04 Bood G EIPM EIPM for all alarms 0001 Reset This datastream results in RESET of alarm description ALL for group WORMALD_F with message ALL and remove after RESET Note Use of this protocol usually requires consulting services and customization Generic Valid manufacturer is GENERIC valid model is BASE This new manufacturer and model combination is implemented in release 2 to handle fixed formatted serial inputs that are built upon single lines and separated with a fixed character There are many parameters available to define the interpretation of the datastreams that are received through the generic eCAP implementation These parameters define criteria for retrieval of group message alarm description set_or_reset and remove_after parameters There are also default values available if some parameters are missing Another set of parameters describes record separators field separators and so on 118 DECT Messenger Installation and Commissioning
212. own and the module identifier When you hold the mouse pointer over the status area of a contact detailed information is shown An example of the information provided is as follows Min set 02 000000 reset 08 000000 Max reset 14 000000 set 20 000000 The chart shown in Figure 132 Analogue input ranges on page 184 explains the behavior of these settings The chart shows the voltage levels between 0 and 24 V on the Y axis and the time between 12 00 and 12 45 on the X axis There are four different configuration values which are indicated in yellow These values are retrieved from the elO_Al table and match the environment in FieldPoint Explorer On the chart the analogue measured values are shown in black The green area is the idle zone the red areas are alarm zones and the grey areas are transition zones e When the measured value reaches 20 00000 V a MAX ALARM condition is set This is shown in the chart on 12 07 e When the measured value drops to 14 00000 B the MAX ALARM condition is reset This is shown in the chart on 12 27 e When the measured value drops to 02 00000 B the MIN ALARM condition is reset This is shown in the chart on 12 37 e When the measured value reaches 08 00000 V a MIN ALARM condition is set This is shown in the chart on 12 45 DECT Messenger Installation and Commissioning Book 1 March 2012 183 Module elO Volt 24 23 22 21 20 wo O NWEAOHOOOH NWE ADA 12
213. p_ekernel State 7 Then lcl_o lt xml gt lt pgmsts gt lt value gt Shutdown lt ip_ekernel SendData 1lcl_o Chr 13 If Err Then value gt lt pgmsts gt lt xml gt ar Chaves 1110 lab_msg Error amp Err amp amp Err Description log E ERR LCP esendeatbames Oi cnet a1 e amp bre Description amp cues cl_o amp could not be sent to eKERNEL Else lst_ekernel_outq RemoveItem 0 log Op wee lel EDe LE ONS ErrCOrECONORO BDE LE DoEvents oc log S INF Application ended end End 72 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com End Sub Private Sub lst_log_Db1Click show details On Error Resume Next Err 0 ere logs Tese ler loep bise dar loco tist Tace Om mercor Coro 0 show_pages End Sub Private Sub Form_KeyDown KeyCode As Integer Shift As Integer F3 Exit If KeyCode 114 Then Unload Me End ENC IE End Sub Private Sub Form_Load Diim lel re AS SEUN Dame Dim lcl_version Dim Lcl_Msg As String Dim lcl_h As Integer 1 Set application title Me Caption eAPI SOPHO Messenger Net v amp App Major amp o amp App Minor amp amp App R evision Startup values required to enable logging g_log_path D SOPHO Messenger Net g_log_days 14 lab_log_path amp g_log_path lab_log_days amp g_log_days Default command line parameters
214. parameter size to indicate the size of the ICMP packet during the PING test using ICMP protocol A default value of 32 bytes meets most requirements e Define the parameter timeout to indicate the number of milliseconds to wait for a response The default value is 1000 This means you can expect feedback on the PING command within 1 second For some environments 1000 is too small a number and depending on your network topology and system resources a larger value can be appropriate Avaya recommends limiting the definition of system to systems that must be verified and are expected to respond Do not define an excessively long timeout The larger the number of the 164 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Monitoring type PING system and the larger the possible timeout the less responsive the system This means that the processing time increases and the number of verifications decreases The following figure shows an example of a definition of a system for PING The message to be sent when a system is no longer responding to an ICMP check and the destinations informed are defined in the NotResponding section The message to be sent when a system resumes responding to an ICMP check and the destinations informed are defined in the Responding section lt System id Loopback address 127 0 0 1 size 32 timeout 1000 gt lt NotResponding gt lt Message gt Loopback
215. port avaya com Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to securityalerts avaya com Trademarks The trademarks logos and service marks Marks displayed in this site the Documentation and Product s provided by Avaya are the registered or unregistered Marks of Avaya its affiliates or other third parties Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark Nothing contained in this site the Documentation and Product s should be construed as granting by implication estoppel or otherwise any license or right in and to the Marks without the express written permission of Avaya or the applicable third party Avaya is a registered trademark of Avaya Inc All non Avaya trademarks are the property of their respective owners and Linux is a registered trademark of Linus Torvalds Downloading Documentation For the most current versions of Documentation see the Avaya Support Web site http support avaya com Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your Product The support telephone number is 1 800 242 2121 in the United States For additional support telephone numbers see the Avaya Web site http support avaya com March 2012 Comments infodev avaya com Contents Chapter 1 New in this rele
216. portant information that is required to understand and configure the elO module To avoid duplicate information the concepts are not repeated in this chapter Startup You must start the elO application by means of a shortcut that uses the syntax described in Figure 127 Parameters in the shortcut for elO on page 179 C SOPHO Messenger Net Exe elI0 exe Site 3 eKernel address LOCAL eKernel port 3108 Log drive C Figure 127 Parameters in the shortcut for elO The following parameters are required e Site Defines the site identifier and is used by eKERNEL to verify the identifier with the eKERNEL_TCPCLIENT and eKERNEL_INPGM settings This identifier is also required so that eKERNEL can respond with the appropriate configuration settings e eKernel address Defines the IP address of eKERNEL Use the special value LOCAL to refer to the same address as the system where elO resides In a single computer environment the LOCAL DECT Messenger Installation and Commissioning Book 1 March 2012 179 Module elO 180 value is usually specified because eKERNEL and elO both share the same network adapter When elO is running on a different computer the IP address of the eKERNEL must be specified e eKernel port Refers to the port number eKERNEL listens to for that specific elO instance This port is defined in the eKERNEL_TCPCLIENT table e Log drive Specifies the drive letter where logging files must be stored W
217. pyes aml gt MM 52d SHS Messages conpleted normaly Joms aras 9 Figure 181 Details under logging tab The logging files provide more details on the data exchange S INF TCP local port 01182 connected with remote port 29081 O TCP lt xml version 1 0 gt lt smsrequest gt lt destination gt 32479467238 lt destination gt lt message gt Demo outbound SMS with module eSMs lt message gt lt smsrequest gt I TCP SMS is sent O TCP lt xml gt lt msgrpy gt lt id gt 00001 lt id gt lt sts gt ACK lt sts gt lt msgrpy gt lt xml gt Figure 182 Logging files When message delivery is successful positive feedback is returned to eKERNEL This XML datastream contains the lt ACK gt characters When message delivery fails a negative response is sent to eKERNEL as shown in the following figure The window in the following figure shows that the eSMS cannot connect to the SMS _service due to a network error DECT Messenger Installation and Commissioning Book 1 March 2012 231 Module eSMS fi eSMS SOPHO Messenger Net 2 9 10 eKernel eSMS Help Logging eKernel Connections Application eSMS SOPHO Messenger Net vZ 9 10 started with parameters Si TCP local port 01177 connected with remote port 03117 eKERNEL lt xml gt lt cfgrqs gt lt appl gt eSMS lt appl gt lt site gt 1l lt site gt lt cfgrqs gt lt xml gt lt xml gt lt cfigrpy gt lt sms_address gt 127 0 0 1 lt sms_address gt lt sms_out
218. r on page 176 Provider Filter cannot be opened Figure 125 Invalid filter criteria error ad I Normal Generate registry files for eTM ntact_ent_njel0M_Comments_str Figure 126 Accessing Generate registry files for eTM Click Generate registry files for eTM to export the configuration for the module eTM also referred to as Task Manager 176 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Important Ensure the eGRID module is not made available for unauthorized access Remove the shortcut where applicable The eGRID module provides direct access to the tables in the database There is no password protection on this module DECT Messenger Installation and Commissioning Book 1 March 2012 177 Module eGRID 178 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 20 Module elO Overview The elO module is a stand alone application that communicates with eKERNEL The module is capable of controlling and measuring Distributed I O peripherals of National Instruments elO offers support for analogue input digital input and digital output See Install PC Step 3 National Instruments for a detailed explanation of installation and configurations issues of the modules and the supporting Measurement Studio components FieldPoint Explorer and OPC Server All these documents contain im
219. r or remove these statements Tampering with branding related information may violate copyright regulations 64 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 10 Module eAPI Introduction The module eAPI is not a real module but rather a description of a public Application Program Interface API for third party developers who want to communicate with DECT Messenger This chapter is intended for developers who want to build an interface to the eKERNEL module The objective of this document is to describe how developers can integrate applications with DECT Messenger Note that the eAPI interface has limited capabilities An alternative to developing your own program is to contact Avaya and request the development of an integrated solution Limitations Input program functionality only The functionality implemented in the eAPI interface is limited to the sending of message requests to the eKERNEL module This process is carried out through so called message request msgrqs transactions Therefore third party application programs that are created using eAPI technology are limited to input program functionality only No central configuration A second limitation in eAPI is that there currently is no support for configuration request messages In all other modules there is a central configuration database where all relevant parameters are centrally administered This process
220. res The procedures are applicable for both Server and Client installs Note During uninstall the DECT Messenger databases and module configuration files ini are automatically removed Make backups if you intend to restore them at a later point in time Uninstalling from Control Panel Windows XP 2003 1 Go to Start gt Settings gt Control Panel and open Add or Remove Programs 2 Select DECT Messenger from the list of programs and click Remove Wait until the product is completely removed Uninstalling from Control Panel Windows 2008 1 Go to Start gt Control Panel and select Uninstall a program below Programs 2 In the Uninstall or change a program window select DECT Messenger and click Uninstall Wait until the product is completely removed Uninstalling from the DVD 1 Insert the DECT Messenger product DVD The DVD Main Menu window appears If not double click D Autorun exe where D is the drive letter of your DVD drive 2 Select Server from the DVD Main Menu or Client if this is a client installation 3 The Requirements Setup Wizard checks that the server meets the configuration requirements 4 Click Next to continue to the Install Prerequisites page 5 Click Next 6 The Welcome to the InstallShield Wizard for Messenger Net window appears Click Next 7 The Program Maintenance window appears 8 Select Remove and click Nex
221. rkes Tools Help amp x 2 A p Search gt Favortes amp Ste de e ee rel 3 Address c Program Fles MessencerdiNet Exe 2 R xml i Go Lk lt xm version 1 0 encoding utf B gt lt eFR gt lt Monitoring interval 600 gt lt OM gt lt DISK gt lt PING gt lt NETSTAT gt lt Connections gt lt Connection ic Mail Server port 25 state Listening gt lt Connection id Messenger Net eCAP port 3102 state Establishad gt lt Connections gt lt NETSTAT gt lt Monitoring gt lt Destinations gt lt eFR gt 2 Y My Computer Figure 111 Monitoring type NETSTAT The configuration for NETSTAT is in the monitoring section starts with the opening tag lt NETSTAT gt and the closing tag lt NETSTAT gt This area contains a subsection starting with opening tag lt Connections gt and ending with closing tag lt Connections gt lt NETSTAT gt lt Connections gt lt Connections gt lt NETSTAT gt Figure 112 NETSTAT connections Definition of a TCP server A sample definition of a connection is shown in the following figure 166 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Definition of a TCP server Figure 113 TCP server definition The definition of a connection contains the following parameters e Define the parameter id name with a unique identifier of the monitored item For example
222. s lcl_str_xml InStr g_ekernel_buffer lt xml gt Incomplete block without lt xml gt is not yet processed ie lel erri Sal 0 Trisni isat IDG 0 Check ir lt xm gt Stiine OCSUrTS lel enc mi mscr lel ser sml G ekernal burrar lt mi gt cr Cars 13 sp Cars iL Aa gm Incomplete block without lt xml gt is not yet processed If lcl_end_xml O Then Exit Do Both lt xml gt and lt xml gt tags are found isolate this data stream Lei eho sail iWavels eke rne Epner iletl gicie sail ileal yevel saqul akedl sie samil a 13 Keep remainder of this data stream if any is available g_ekernel_buffer Mid g_ekernel_buffer lcl_str_xml Len 1lcl_dta_xml1 Mdo EDON log ip Wer Iel clea sini Submit request to ekernel jobqueue lst_ekernel_jobq AddItem lcl_dta_xml End loop Loop End Sub Private Sub ip_ekernel_Error ByVal number As Integer Description As String ByVal Scode As L ong ByVal Source As String ByVal HelpFile As String ByVal HelpContext As Long CancelDispl ay As Boolean lab_msg Error amp number amp Description log E ERR TCP error amp number amp amp Description amp eKERNEL End Sub Private Sub mnu_ekernel_disconnect_Click ip_ekernel Close lab_ekernel_state Backcolour RGB O 0 0 g_ekernel_local_address N A g_ekernel_local_port N A eAPI_form 5
223. s BEMAC_x where x is the specified tone code for example tone code 3 sets message with alarm description BEMAC_ 3 ELDAD 104 Valid manufacturer is ELDAD valid model is specified through a special syntax for example L 48 0 RC 1 SR 2 SS 3 SS 4SR Note that the model is built upon components having syntax A BB and separated with a hyphen e L xx denotes that the length of an alpoha message is xx bytes For example L 48 means that aloha messages are 48 bytes long L 24 denotes alpha messages are 24 bytes long e 0 xx specifies behavior of tone code 0 1 xx specified behavior of tone code 1 2 xx specifies behavior of tone code 2 and so on For each tone code the syntax ends on two characters The first character can be S or R S denotes set of alarm R denotes reset of alarm The second character can be S or R or C The value S refers to remove after SENT the value R refers to remove after RESET the C refers to remove after CALC DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com GENT For example L 48 0 RC 1 SR 2 SS 3 SS 4SR means the alpha messages are 48 bytes long tone code 0 denotes RESET alarm remove after CALC tone code 1 and 4 denote SET alarm remove after RESET and tone code 2 and 3 denote SET alarm remove after SENT Bemac is based upon installation Sint Franciskus Ziekenhuis Heusden Zolder The syntax is STX XXXXTZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
224. s also available in the Administrator Guide Configuring site information When using the default database configuration deployed by the installer a Site NEC node should be visible in the left side tree You can use this site as a starting point of your configuration Configuring site information 1 Double click the site node in the eCONFIG tree The Site configuration window appears as shown in the following figure Site She lID 1 Site Description NEC Adninistrator name Administrator Adninistrator e mail admin nec unified com eKemel IP address 127 0 0 1 Gabadge colleciion 600 Connection string CFG Provider Microsoft Jet Connection string DATA Provider Microsoft Je Path eLOG C Program Files xB6 NEC Mezs Number of days lo keep eL0G files 30 5 Administrator name The current value for thi parameter is Administrator Figure 24 Site configuration window 2 From the list on the left select the item to configure 3 On the top right an input control allows you to modify the selected item DECT Messenger Installation and Commissioning Book 1 March 2012 53 Getting started with DECT Messenger 4 Onthe middle right a description text explains the purpose of the selected item and how it should be configured 5 On the bottom right the current value of the selected item is shown as well as any validation errors related to the value entered in the input control The followi
225. s no longer valid For example if your hard disk and Ethernet adapter are both replaced this warning appears 204 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Disaster recovery eFR SOPHO Messenger Net License key is invalid for this system Please contact you software representative and Cancel order a licence key for Messenger Net module eFR k x The software will be registered to NEC Philips Unified Solutions NEC Philips Unified Solutions 76487 641 3119356 231 75 You may be asked to provide the info listed below Computer name BENB121027 Serial number 230464 584F 0EM A5D8 MAC address 02 00 4C 4F 4F 50 Processor x86 Family 6 Model 13 Stepping 8 Enter the license key below and press OK to continue Figure 148 Invalid license key warning If this occurs request an updated license file Note If you cannot wait to restart the system type the word Evaluation in the text box in the invalid license key warning shown in Figure 148 Invalid license key warning on page 205 This gives you access to the module but it does not apply a permanent key By entering the word Evaluation you can continue to run the application until you receive a new valid license for the changed system Note The invalid license key warning appears each time the software starts unless you apply the new license key DECT Messenger Insta
226. s to access the shared database Note Contact your network administrator for details on security and access privileges over the network To avoid browsing for the location of MessengerConfig mdb you can specify its location in the eCONFIG ini file Configuring the eCONFIG ini 1 Open Windows Explorer 2 Browse to the directory with the eCONFIG executable by default this is c Program Files Avaya Avaya DECT Messenger Configurator 3 Double click the file to open it with the default text editor typically Notepad 4 Modify the MessengerConfig setting to indicate the location of MessengerConfig mdb configuration database 5 Save the changes and close the text editor For example if directory c Program Files Avaya Avaya DECT Messenger Database is shared as MyNetworkShare on eKERNEL system MyMessengerServer the configuration setting would look as pictured in the following figure j eCONFIG ini Notepad Pile Ea Ele Edt Format Yew Help essengerCconf ig mMyMess enger Server MyNetwork Shar e mess engerconfig mdb Branding Branding NEC Nederland B v SOPHO NEC Nederland B v essenger net Messenger net Figure 34 Example of an eCONFIG ini file Important To meet the requirement of eCONFIG to support both NEC and AVAYA environments additional tags are available in the eCONFIG INI file These tags provide internal steering parameters for the user interface of the eCONFIG instance Do not alte
227. sabdavastiatietdgvaniscoint acwateceticteacnenast 81 CAS YING 6X6 srna a i aai 81 CCAR aa a E 97 100 101 104 105 eCAP functional description eeeeeeeeeeeeeeeeeeeeen 100 ECAP eXe ea re E A 97 SCONFIG meee cach eatedeneanedeneatemeecet 63 eCONFIG concepts ccceeeessteeeeeeeeesstteeeeeeeesennaees 52 SDMSAPI eere E R ER 56 135 ECDMSAPI OXE ccceccccccccccceceeeeseseeceeeeeeeeeeesauaesseeseeess 135 CES PA raono O AR 119 eESPA logging ssesssssssssssssssssresssrrsssressrsssrssssssnessnnnes 126 GESPA CXC viados a a 119 Eeuwfeestkliniek Antwerpen sssssssssssessrrrssserrrssses 108 UY ANDE AA EE PEE E E A avaatudguettenees 147 CFR configuration saeeeessseeeesessrrrrneeeerernnnenerrnnnnnn eal CERLINSLAIALION seinere annin 150 GFR LAUNCH 20 0 eccccceeeeeececesseceeceesceeeaneeeeeceaaeeeeeseunes 150 CE RAICEMSS soscat vacate cxcudencteveateisgatac huvendateatndtaauseemensans 151 EO EE 179 GIO JOGGING seninter 186 CIO modules 0 cc eeeeeeeecccceeececaeeesseceeceeeeeueaeaeeeeeess 182 ClO SLAMUP seks cic sactiten T ca desta tie ca casaeiie cae deaetiaecees 179 EKERNEL 2 00 ccceeeeeeeccecceeeseeeeeseeeeeeeeeaesaeees 67 191 196 March 2012 243 CRERNEL EXC icasi 119 Launching module eFR cececeeeeeeeeeeeeeeeeeeeeeeeee 150 EL DAD isisccesssaesivestes enaa AA E A aaa ENRE 104 License MAINTENANCE ssseensesesnenrnoessnrnroresnrerene 194 ELICENS EB vsssiasavsneshecatntasdagawebedaantidvesssd
228. se a standard null modem cable However in some cases alarm systems support a limited number of control signals for example ground send and receive so consult the alarm system vendor for cable specifications If no COM ports are available extra hardware such as DigiBoard PC 4e and DigiBoard PC 8e is required to provide extra serial ports Investigate compatibility issues operating system support driver available and so on and hardware requirements memory available slots IRQ conflicts and so on before purchasing equipment or configuring the system In some cases additional hardware is needed for example when RS 232 C limitations apply for example at 9600 baud maximum limit of 9 metres In some cases galvanic isolation is requested or base band modems SOPHO LAM CISCO equipment and so on are needed to bridge the distance between the DECT Messenger and the alarm system In many cases 122 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Functional description the distance between the DECT Messenger and the external paging system is relatively small so no extra hardware is needed Once a link is established between eESPA and the paging system the eESPA handles further communications and informs eKERNEL when relevant information is to be exchanged For a detailed description of the ESPA4 4 4 protocol refer to the proposal for serial data interface for paging equipme
229. senger client modules are supported on any PC capable of running the supported operating systems A DVD drive is required in order to install the product Optional hardware Depending on the way DECT Messenger is being used there are several hardware devices that may be needed in order to use certain features e National Instruments equipment for digital input output contacts and analogue input for software module elO This is only required if you use the elO software module e V 24 multi port card e Analogue Modem for dialing to GSM provider to send SMS messages This is only required to send SMS messages to a GSM cell phone provider using a dial in option Database server requirements DECT Messenger optionally uses Microsoft SQL Server to store data the choice is presented when installing in Server mode In most cases Microsoft SQL Server 2008 Express Edition is sufficient a copy is distributed with the DECT Messenger DVD If necessary you can use a non Express edition of SQL Server e g for maintenance tools and to increase the database size limits Installation of non Express editions is not covered by this guide and is subject to additional licensing costs to Microsoft DECT Messenger supports SQL Server 2005 and 2008 editions Note During the installation the system administrator sa account is used Make sure you know the password for the sa account and that the SQL Server is configured to run in mixed mode
230. server listening on port 28008 Initialization You use a shortcut to start the eLOCATION module The following figure shows an example of the required keywords DECT Messenger Installation and Commissioning Book 1 March 2012 207 Module eLOCATION C SOPHO Messenger Net Exe ite 1 eKernel Figure 149 eLocation module keywords The following keywords are used to start the eLocation module e The site keyword indicates the site that is assigned to the eLOCATION module e The eKernel address keyword indicates the IP address that is assigned to the eKERNEL module The eLOCATION contacts this IP address to connect to the eKERNEL e The eKernel port keyword indicates the port number that is assigned in the configuration for the eLOCATION client instance When the eLOCATION application starts the application attempts to connect to the eKERNEL The attempt to connect is based upon the address and port information obtained from the Shortcut At connection the eLOCATION requests that the eKERNEL provide additional configuration settings This request is known as a configuration request The eKERNEL then authenticates the client and responds with a configuration reply The following figure illustrates the initialization procedure S INF Application eLOCATION SOPHO Messenger Net v4 0 0 started with parameters Site 1 eKernel address LOCAL eKernel port 3203 Log drive C S INF TCP local port 02545
231. sk an example of which is shown in Figure 51 Sample backup log on page 94 Note that in the example the file elO exe was not saved DECT Messenger Installation and Commissioning Book 1 March 2012 93 Module eBACKUP 25 10 2001 16 06 20 S INF Application eBACKUP SOPHO Messenger Net v2 0 1 started with parameters Path C SOPHO Messenger Net Log drive C Site 3 Batch N 25 10 2001 16 06 22 S INF FileCopy C Php php ini C Temp 4 php php ini completed normally 25 10 2001 16 06 22 S INF FileCopy C Program Files Apache group Apache conf httpd conf C Temp 4 Program Files Apache Group Apache conf httpd conf completed normally 25 10 2001 16 06 22 S INF FileCopy C SOPHO Messenger Net Exe csta dll C Temp 4 SOPHO Messenger Net Exe csta dll completed normally 25 10 2001 16 06 22 S INF FileCopy C SOPHO Messen ger Net Exe CSTA_service exe C Temp 4 SOPHO Messen ger Net Exe CSTA_service exe completed normally 25 10 2001 16 06 22 S INF FileCopy C SOPHO Messenger Net Exe eAPI exe C Temp 4 SOPHO Messenger Net Exe eAPI exe completed normally 25 10 2001 16 06 22 S INF FileCopy C SOPHO Messen ger Net Exe eASYNC exe C Temp 4 SOPHO Messenger Net Exe eASYNC exe completed normally 25 10 2001 16 06 22 S INF FileCopy C SOPHO Messenger Net Exe eBACK UP exe C Temp 4 SOPHO Messenger Net Exe eBACKUP exe completed nor mally 25 10 2001 16 06 22 S INF FileCopy C SOPHO Messenger Net Exe eCAP exe C
232. ss during the messaging delivery process The message delivery process bidirectional The eSMS sends a request to the SMS_ service and the SMS _service sends a reply to the eSMS module The following figure shows a sample message is sent to a mobile phone F eSMS SOPHO Messenger Net v2 9 10 eker eSMS Help S Outbound SMS to 32479467298 O Demo outbound SM3 with nodule esms E 2 SHS Messages congeted normally Joos ara amp Figure 180 Example of an outbound message to a mobile phone More details on this dialogue are listed under the Logging tab 230 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Outbound messaging ff eSMS SOPHO Messenger Net v2 9 10 BBE cker cSMS Help Logging INP Application eSMS SOPHO Messenger Net v2 9 10 started with parameters Si INF TCP Local port 01177 connected with remote port 03117 eKERNEL IT TCP lt xml gt lt cforqs gt lt app l gt eSMS lt appl gt lt site gt l lt site gt lt etgrgs gt lt xml gt 2 TCD lt 9ml gt lt cforpy gt lt sms_address gt 127 0 0 1 lt sus_address gt lt sms_outbeund_port gt 79081 lt s IHF TCP Local port 01102 connected with remote port 29061 iTCPi lt xml version 1 0 lt susrequest gt lt destination gt 3247594 67235 lt destination lt nes TCP SMS 15 sent PH ORH OR MR O TCP lt xml gt lt nsgrpy gt lt 1d gt 00001 lt 1d gt lt scs gt aCK lt sts gt lt msgr
233. ssananivassauasduestat 201 License Manager e ceeeeeeeenceeccaeeaeeeeeeeeeeees 192 eLICENSE installation c cccccccscseseecceeeeeeeaeeeeeeees 201 LICENSE MECHANISM ccccecceeessseceeaeeeseeeeaneesenees 201 LICENSE running ccccceeeeeesesseeeeeeeeeesseennnaees 202 Licensing module eFR 2 e eeeeereeceeeeeeeeeeeees 151 eLOCATION architecture 0 cceccecessseseeeeeeeeeeees 212 Limitations of CAPI ccc ccccccseceeeesseeceeeeeeeaeeeeeeeanes 65 CLOCATION initialization ccccccccccccceseeeeeeeeeeeeeees BOF LOJO isinisi 85 126 139 186 196 eLOCATION Program activity cceeeeeeeeeeeeeees 210 Equipment models sessies 193 M eSMS architecture 0 0 0 cccceseesececceeeeeeeaeaeueneeeeees 223 eSMS configuration 0 0 0 ec cceeeettteeeeeeeeseeeeeeaeeeeeess 234 eSMS inbound messaging cscsee eee eseseeseees tees 232 Sp ete err ee eer ere ee 107 eSMS Module csscesesecssesecsscssesseseseesseeseesee 223 227 Making eLOCATION operational ss sss 111sr111 212 eSMS outbound messaging cscsecsessseseseseseesesees 230 Menu Options s s ssesssisssenssisrssrensnisnennsnnnneneninnennenenns 197 eSMS startup eee ane a een eee nee entee emer tree 227 MessengerContig mdb cscs 50 OSMS Web INtELACE oecccccccccccccccccccceccccccccesececeeeseescecs 239 MINERVA GO coos sadeanctosesenctesertesceed sateen censeniatncasereee 112 SPA O A 119
234. ssues Supported by operating system driver available and so on and hardware requirements memory available slots IRQ conflicts and so on before ordering or configuring a system In many cases the distance between the DECT Messenger and the external alarm system is relatively small so no extra hardware is needed In some conditions hardware is needed such as when RS 232 C limitations apply for example at 9600 baud maximum limit of 9 metres In some cases galvanic isolation is requested or base band modems SOPHO LAM CISCO equipment and so on are needed to bridge the distance between the DECT Messenger and the alarm system DECT Messenger Installation and Commissioning Book 1 March 2012 99 Module eCAP Once a link is established between eCAP and the alarm system the eCAP handles further communications and informs eXKERNEL when relevant information is to be exchanged Functional description In general eCAP is designed to provide eKERNEL with alarm information This is carried out using a lt msgrqs gt message request For some interfaces eKERNEL must send feedback to the alarm system a process that is handled through lt msgrpy gt message reply request Important The eCAP module is compatible with a number of alarm system installations However many of the supported vendors offer a broad variety of hardware and software environments all of which are not necessarily compatible with eCAP For example the fact
235. stallation and Commissioning Book 1 March 2012 Comments infodev avaya com Architecture e Next the eLOCATION_RPN table must be populated with records for every RPN known in the DAP Controller configuration In the following figure RPN 11 up to RPN 13 is defined A generic catchall definition is indicated with a For each RPN we define a description in words that tell the end user the physical location of the RPN In the sample illustrated in the following figure the texts are nearby RPN 011 nearby RPN 012 but in a real environment the text appears in words rather than technical code for example Emergency room Elevator 1 Psychiatric department and so on i Module eLOCATION E General SiteID 1 Site description Site 1 realD 2 it ENOL Area description SIP DECT MERA nearby RPN 012 RPNO12 Location Agent address 192 168 32 10 nearby RPN 013 RPN013 Location Agent port 28008 General timeout 10 Retry count 5 Retry interval 10 Polling interval 60 gt gt gt Board definition RPN definition Comments eLOCATION configuration for SIP C amp Inbound call handling gt gt gt eCSTA inbound event gt gt gt eDMSAPI inbound event gt gt gt eLOCATION Inbound result New Edit amp Interface with eKERNEL Delete Refresh OK Cancel Figure 164 eLOCATION_RPN table At this stage you already know the calling number the c
236. t 9 On the following window click Remove to begin uninstalling 10 When done click Finish to close the wizard DECT Messenger Installation and Commissioning Book 1 March 2012 43 Install DECT Manager 44 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 9 Getting started with DECT Messenger This chapter describes the actions required for getting a DECT Messenger Server up and running For further details on how to configure and use the Input Output modules refer to DECT Messenger Fundamentals NN43120 120 Loading licenses Note Before using DECT Messenger you need a license key and a dongle attached to one of the USB ports of your PC 1 On the DECT Messenger Server PC go to Start Menu gt Programs gt CTI Developer Kit gt Configurators gt License Manager The License Manager tool starts up showing a warning message that no license key is present as shown in the figure below amp License Manager loj x Licensed Applications No icense string present You must enter a license string before you canuse the License Manager Ready ZA Figure 17 License Manager no license warning 2 Click OK to discard the warning DECT Messenger Installation and Commissioning Book 1 March 2012 45 Getting started with DECT Messenger 3 Inthe License Manager menu go to File gt Load a New License String and browse for the lic
237. t ai_01_03_max_s gt lt ai_01_04_min_s gt 00 000000 lt ai_01_04 min_s gt lt ai_01_04_ min_r gt 00 000000 lt ai_01_04_min_r gt lt ai_01_04_max_r gt 12 000000 lt ai_01_04_max_r gt lt ai_01_04_max_s gt 20 000000 lt ai_01_04_max_s gt lt ai_01_05_min_s gt 00 000000 lt ai_01_05_min_s gt lt ai_01_05_min_r gt 00 000000 lt ai_01_05_min_r gt lt ai_01_05_max_r gt 12 000000 lt ai_01_05_max_r gt lt ai_01_05_max_s gt 20 000000 lt ai_01_05_max_s gt lt ai_01_06_min_s gt 00 000000 lt ai_01_06_min_s gt lt ai_01_06_min_r gt 00 000000 lt ai_01_06_min_r gt lt ai_01_06_max_r gt 12 000000 lt ai_01_06_max_r gt lt ai_01_06_max_s gt 20 000000 lt ai_01_06_max_s gt lt ai_01_07_min_s gt 00 000000 lt ai_01_07_min_s gt lt ai_01_07_min_r gt 00 000000 lt ai_01_07_min_r gt lt ai_01_07_max_r gt 12 000000 lt ai_01_07_max_r gt lt ai_01_07_max_s gt 20 000000 lt ai_01_07_max_s gt lt ai_01_08_min_s gt 00 000000 lt ai_01_08_min_s gt lt ai_01_08_min_r gt 00 000000 lt ai_01_08_min_r gt lt ai_01_08_max_r gt 12 000000 lt ai_01_08_max_r gt lt ai_01_08_max_s gt 20 000000 lt ai_01_08_max_s gt lt log_path gt C SOPHO Messenger net lt log_path gt lt log_days gt 1 lt log_days gt lt cfgrpy gt lt xml gt Figure 137 Log example Configuration procedure 188 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Logging 25 10 2001 10 41 37 S TCP FP AI 100 module 01 contact
238. t timeout gt lt handshaking gt 0 lt handshaking gt lt log_path gt C SOPHO Messenger net lt log_path gt lt log_days gt 14 lt log_days gt lt cfigrpy gt lt xml gt Figure 70 Typical cfgrqs configuration request and its received cfgrpy configuration reply Refer to the appropriate sections on the database tables that define the received parameters for more information on each value The information in this document is provided for informational purposes only a detailed description of these internal inter process communications is beyond the scope of this document If no valid license is available to run an eESPA module the eKERNEL sends a reply lt xml gt lt pgmsts gt NO LICENSE AVAILABLE lt pgmsts gt lt xml gt and close its port If you receive this message upon connection to the eKernel use Avaya License Manager to see if there is an available license When the configuration is received the Connection tab displays information similar to what is pictured in Figure 71 eESPA Connection tab showing a valid configuration on page 122 DECT Messenger Installation and Commissioning Book 1 March 2012 121 Module eESPA aye eESPA SOPHO Messenger Net 2 8 0 Slave l l xl eKernel eESPA Logging Connections m eKermnel m Configuration TESPA d definition koca 1011050140 1730 Contioling station No E A Remote 10 110 50 140 3114 Poling No L 5 Interval mseconds 0 Address es
239. t 914 lt ToReg_0003 gt gt lt keepalive gt 60 lt keepalive gt lt log_path gt C SOPHO Messenger net lt log_path gt lt log_days gt 14 lt log_days gt lt cfgrpy gt lt xml gt Figure 83 A typical cfgrqs configuration request and its received cfgrpy configuration reply Table 14 Possible values for the network and pbxtype tags eDMSAPI_PBX_type_str eDMSA lt pbxtype gt lt network gt PI DAP controller DAP Controller dasgif 136 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com eDMSAPI exe DMC DMC ETHERNET_DMC AVAYA AVAYA Dasgif Refer to the chapters of this document that deal with the database tables for more information on each value A detailed description of these internal inter process communications is beyond the scope of this document The parameter lt loReg_cnt gt specifies how much DECT extension is loRegistered can send data messages to the DECT Messenger application The parameter lt loReg_xxxx gt where xxxx starts with 0001 until loReg_cnt specifies the DECT extensions that must be loRegistered eDMSAPI SOPHO Messenger Net 3 0 0 la xj eKernel CSTA lt DMGAR Cabal eKernel M Configuration Local 10 110 50 140 2335 J Total seats acsOpenStream J 20 J Remote 10 110 50 140 3101 Reserved eKernel seats 10 Reserved External seats 3 J Status Connected loRegister count Hdevices
240. t BNET lt Dastination gt 182000 unit 02 is ready lt Message gt inations gt lt Oestination gt eSNMP lt Destination gt lt Destination gt eNET lt Destination tinations gt 2eady lt Report gt Message gt Fault Report for iS3000 unit 02 lt Message gt 17 BSMITP lt Destination gt lt NETSTAT gt lt Monitoring gt lt Destinatinns gt gjeFR gt J M Computer Figure 96 Example of monitoring section and subsections Monitoring The parameter interval with a default value of 600 specifies the frequency at which the monitoring process takes place When a value of 600 is specified a delay of 600 seconds takes place between the last monitoring action and the next monitoring action The eFR module captures information about the configured items roughly every 10 minutes e The default value is 600 seconds e The minimum value is 60 seconds Every minute a verification cycle takes place When a value smaller than 60 is configured the system adjusts it to 60 seconds e The maximum value is 86400 seconds so once a day a verification cycle takes place When a larger value than 86400 is configured the system will adjust to 86400 seconds Note The processing cycle takes some time for example PING to a large number of systems that are not responding increases processing time Since the interval effects the time between ending the previous verification and startin
241. tResdy gt Threshalds hreshold gt Drive C usage below threshold level lt Message gt 2 My Computer EIG Program Files WassengeraNet baw FR anl Microsoft Internet Exploror provided by NE 063 ka Figure 98 Define drives for monitor type DISK Monitoring type DISK The line shown in the following figure is the opening tag for a drive definition Figure 99 Opening tag for a drive definition You must define two parameters e Create the parameter id as a single upper case character that represents the drive name to be monitored For example entering C as the id indicates that the C drive is monitored This character is typically the drive letter you assign to the hard disk drive e Create the parameter usage as a numeric value that specifies a percentage of allowed disk usage For example enter 70 to indicate that up to 70 of the hard disk can be used When less than 30 free capacity is available you must notify users The window in the following figure shows a green bullet next to the C drive to indicate that the required conditions are met The window shows a red bullet next to the D drive to indicate that for that drive the conditions are not met D drive is not ready or has reached the defined usage DECT Messenger Installation and Commissioning Book 1 March 2012 161 Module eFR eFR SOPHO Messenger Net v3 0 0 la m O E zile About Logging Monitoring Notificati
242. tact contact contact ol ol ol oz 02 oz 03 tApplication eI0 SOPHO Messenger Net v2 0 6 started with parameters S a TCP local port 04872 connected with remote port 03108 eKERNEL i xml gt lt cfgrqs gt lt appl gt el0 lt appl gt lt site gt 3 lt site gt lt version gt Z 0 6 lt version gt lt cfgr i xml gt lt cfgrpy gt lt manufacturer gt NATIONAL INSTRUMENTS lt manufacturer gt lt model gt BAs Connecting Parsing URL Connecting Connecting to OPC Server Active Connected to OPC Server Connecting Parsing URL Connecting Connecting to OPC Server Active Connected to OPC Server Connecting Parsing URL ae Data arrival 1913 bytes received from eKERNEL Figure 135 elO logging 00056 22 45 15 The log files on disk contain the same information as shown on screen On the next few pages Figure 135 elO logging on page 187 through Figure 140 Log example Termination on page 189 show examples of log information saved on disk during different steps of elO setup and use 25 10 2001 10 41 35 S INF Application eIO SOPHO Messenger Net v2 0 6 started with param eters Site 3 eKernel address LOCAL eKernel port 3108 Log drive C 25 10 2001 10 41 36 S INF TCP local port 01183 connected with remote port 03108 eKERNEL 25 10 2001 10 41 36 Figure 136 Log example initialization procedure DECT Messenger Installation and Commissioning Book 1 March 2012 187 Module e
243. tadrgument D1 ack Dect 863 16 22 19 StartD ataPathR equest 8 Extemal 3 seats available Dect 865 16 22 23 5568 SendDatadrgument O1ack amp loRedister 9 seats 7 seats available Dect 860 15 35 26 loRegisterResult Dect 861 15 35 26 loRegisterResult Dect 862 15 35 26 loRegisterResult Dect 999 15 35 26 object not known Dect 869 15 35 26 loRegisterResult Dect 868 15 35 26 loRegisterResult amp Dect 867 15 35 26 loReaisterResult Sa JG Data arrival 96 bytes received from CSTA 0005s 16 2224 amp Figure 85 eDMSAPI tab Note that during call handling the eDMSAPI tab shows an overview of current call states of each device The window consists of two sections e The Jobq section contains two job queues One jobg is for the request from eKernel and the other is for requests from external clients This area is used to temporarily store requests that are waiting to be executed For instance when all the data paths are in use new requests must wait until resources are available Requests can come from the eKernel lt msgrqs gt or from an external client SGNDNMSG IDJDNR IMESSAGE lt cr gt lt lf gt or SNDUMSG ID DNR MESSAGE lt cr gt lt lf gt The functionality to receive requests from external clients is supported only for the DECT Messenger application internal use only e The Active section contains active jobs This area is
244. te By default eKERNEL listens for an eCONFIG connection on port 9000 The eCONFIG module needs to copy this database locally to make configuration changes Launching the eCONFIG configuration utility 1 Use the shortcut available in the Start Menu Start gt Programs gt Avaya DECT Messenger gt eCONFIG 2 When prompted for login enter the username and password The default login that is available after installation is username admin password admin DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Configuring DECT Messenger 3 When using eCONFIG from a client PC you will be prompted for the location of MessengerConfig mdb database Browse to the network share of the server PC containing the MessengerConfig mdb database 4 If a working configuration database already exists from a previous eCONFIG session you will get a message box asking whether to use the locally modified copy of the MessengerConfig mdb database previously used by eCONFIG or to replace it with a fresh copy of the latest data as shown in the following figure eCONFIG Messenger Net 4 1 6 There is still a working database available By pressing the YES button you will continue working on this database By pressing the NO button a fresh copy of the messenger configuration database will be taken and all changes you made before will be lost Continue working on
245. te or documentation provided by Avaya Avaya is not responsible for the accuracy of any information statement or content provided on these sites and does not necessarily endorse the products services or information described or offered within them Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages Warranty Avaya provides a limited warranty on its Hardware and Software Product s Refer to your sales agreement to establish the terms of the limited warranty In addition Avaya s standard warranty language as well as information regarding support for this Product while under warranty is available to Avaya customers and other parties through the Avaya Support Web site http support avaya com Please note that if you acquired the Product s from an authorized Avaya reseller outside of the United States and Canada the warranty is provided to you by said Avaya reseller and not by Avaya Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE HTTP SUPPORT AVAYA COM LICENSEINFO ARE APPLICABLE TO ANYONE WHO DOWNLOADS USES AND OR INSTALLS AVAYA SOFTWARE PURCHASED FROM AVAYA INC ANY AVAYA AFFILIATE OR AN AUTHORIZED AVAYA RESELLER AS APPLICABLE UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE
246. ted normally 25 10 2001 16 06 25 S INF FileCopy C SOPHO Messen ger Net Mdb Messenger_Data mdb C Temp 4 SOPHO Messen ger Net Mdb Messenger_Data mdb completed normally 25 10 2001 16 06 30 S INF Application ended Avaya recommends that you close all the DECT Messenger applications before starting the backup procedure In release 2 the file copy procedure is implemented by means of a Windows API call as shown with the code excerpt in Figure 52 File copy example on page 95 Declare Function apiCopyFile Lib kernel32 Alias CopyFileA ByVal lpExistingFileName As String ByVal lpNewFileName As String ByVal bFail IfExists As Long As Long Result apiCopyFile SourceFile DestFile False Figure 52 File copy example Important To ensure a complete and consistent image you must close all applications before backup The code shown in Figure 52 File copy example on page 95 can back up files even if they are open Therefore you can initiate the eBACKUP while for instance eKERNEL is active and the Messenger_CFG mdb database is open Although you can use the eBACKUP to save the open files Avaya does not guarantee that the copied file is a complete image or a consistent database image During activity of eKERNEL parts of the Access 2000 database are sometimes in use and transactions are pending Saving open files is not officially supported For more information visit the Microsoft web site at http support microso
247. ted on the DECT Messenger DVD Installing Adobe Reader 9 Adobe Reader 9 is required to read the documentation on the DVD On the server it is also used by the eGRID configuration module to display information about the configurable database fields Note Only the English version of Adobe Reader is available on the DVD You can download a copy in other languages from the Adobe website http get adobe com reader To install Adobe Reader 9 complete the following steps 1 Insert the DECT Messenger product DVD The DVD Main Menu window appears If the Main Menu does not appear double click D Autorun exe where D is the drive letter of your DVD drive 2 Select Adobe Reader 9 from the DVD Main Menu The installer prepares the files and then the Destination Folder window appears as shown the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 31 Installing third party software ie Adobe Reader 9 3 4 Setup yu Destination Folder Click Next to install to this Folder or click Change to install to a different folder E Install Adobe Reader 9 3 4 to C Program Files x86 Adobe Reader 9 04 WARNING This program is protected by copyright law and international treaties Change Destination Folder Figure 11 Adobe Reader 9 Destination Folder window 3 Verify the installation location and click Next If you want to change the destination folder click Change Destina
248. the same PC using the server mode installation DECT Messenger Installation and Commissioning Book 1 March 2012 9 Introduction 10 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Chapter 3 System requirements The following sections describe the system requirements for DECT Messenger Supported operating systems The following operating systems are supported by DECT Messenger both client and server install e Windows XP Service Pack 3 x86 e Windows Server 2003 Service Pack 2 x86 e Windows Server 2003 R2 Service Pack 2 x86 e Windows Server 2008 x86 x64 e Windows Server 2008 R2 Note When using a Microsoft SQL Server database engine for the DECT Messenger database a server operating system is required Server PC requirements DECT Messenger is supported on all servers that fulfill the Microsoft Hardware Compatibility List HCL and meet the following minimum requirements e 1 4 GHz or higher CPU 2 GHz or higher is recommended e 256 MB of RAM 1 GB or more is recommended e 1 GB of free hard disk space 10 GB or more is recommended DVD drive e 1 free USB port for Security Dongle 2 if you use the Monitoring Diversion feature in conjunction with a 2000 IPS PBX system The recommended computer name for the server PC is Messenger DECT Messenger Installation and Commissioning Book 1 March 2012 11 System requirements Client PC Requirements DECT Mes
249. the system where eKERNEL runs and port number the configured port for eAPI as defined in eKERNEL_TCPCLIENT table DECT Messenger Installation and Commissioning Book 1 March 2012 67 Module eAPI 6 Run the program If you click the Command1 button a message request is sent to eKERNEL 7 You can alter the code shown in Figure 36 Sample socket client code on page 69 to specify the correct parameters for the parameters group use one of the values specified in the eKERNEL_GROUP table alarm description use one of the values specified in the eKERNEL_ALARM table and so on Note The code shown in Figure 36 Sample socket client code on page 69 is not intended to represent a reliable TCP client and is meant only to illustrate how to start programming with eAPI using minimal code entry A real life program must take all necessary action to handle all error conditions The following issues usually require improvement e The sample code shown in Figure 36 Sample socket client code on page 69 does not respond on the asynchronous connection attempt by means of the Winsock1_Connect event The code assumes that the connect succeeds after doing a DoEvents The Winsock1 State must be 7 before a SendData can be requested e The sample code shown in Figure 36 Sample socket client code on page 69 includes appropriate error recovery but does not respond to failed connection attempts e The sample code shown in Figure 36
250. the work database Figure 22 eCONFIG database message If you are not sure choose No This is the safest option it discards the local possibly outdated database copy and replaces it with a copy of the server database 5 If eKERNEL cannot be contacted an error message appears as shown in the following figure eCONFIG Messenger Net v4 1 7 vo y Connection with eKernel not established Please verity the IP address and Port of the eKernel application specified in the command Application will be closed Figure 23 eCONFIG and eKERNEL connection error If this happens verify that eKERNEL is running on the server PC and that the eKERNEL address and port number passed to eCONFIG correspond to those shown in the eKERNEL main window 6 The main window appears as shown in the following figure DECT Messenger Installation and Commissioning Book 1 March 2012 51 Getting started with DECT Messenger eCONFIG Messenger Net v4 1 6 admin LOCAL File View Messenger Net Sarain Import View and work with areas Export s View and work with Modules License information View and work with all alarms View and work with all users View and work with all groups and devices View and work with holidays The left pane shows a tree with the available configuration items while the right pane shows details on the currently selected configuration item Working with the eCONFIG user interface e Left cl
251. thtype gt text lt pathtype gt lt dirtype gt bi lt dirtype gt lt homelocationnumber gt 0 lt homelocationnumber gt lt start datapathdevice gt lt xml gt PBX type DMC and DAP controller also Emergency messages 03 10 2002 12 08 57 0 TCP lt xml gt lt startdatapathdevice gt lt deviceID gt 861 lt de vicelD gt lt pathtype gt text lt pathtype gt lt dirtype gt bi lt dirtype gt lt callcategory gt emergency lt callcategory gt lt homeloca tionnumber gt 1 lt homelocationnumber gt lt startdatapathdevice gt lt xml gt PBX type CS 1000 Emergency messages 03 10 2002 12 08 57 O0 TCP lt xml gt lt startdatapathdevice gt lt deviceID gt 861 lt de viceID gt lt pathtype gt text lt pathtype gt lt dirtype gt bi lt dirtype gt lt callcategory gt emergency lt callcategory gt lt homeloca tionnumber gt 0 lt homelocationnumber gt lt startdatapathdevice gt lt xml gt 03 10 2002 12 08 58 I TCP lt xml gt lt StartDataPathResult gt lt IoCrossRefIdenti fier gt 5697 lt IoCrossRefIdentifier gt lt invokeID gt 58 lt invokeID gt lt StartDataPathResult gt lt xml gt 03 10 2002 12 08 58 O TCP lt xml gt lt senddata gt lt iocrossrefid gt 5697 lt iocross refid gt lt Text gt Guarding AM TELEVIC 01 01 lt Text gt lt originator gt pbx lt orig inator gt continued on next page Figure 89 Log example Message handling 144 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev
252. ti If Len Dir lcl_path vbDirectory 0 Then Mite Ikeil_joaticin Eme LE lcl_chk Len Dir g_log_path vbDirectory ie ame 2 Ore el eas O nen 78 DECT Messenger Installation and Commissioning Book 1 Comments infodev avaya com March 2012 Select Case Left g_log_path 3 Case Cy g_log_path D Mid g_log_path 4 lab_log_path amp g_log_path Gasembray g log pera Gate Mich G log petn 4 lab_log_path amp Cp lkog_joeicla Case Else Gulogupavh Gs 4 MadSi gmilogmpath 4 lab_log_path amp g_log_path End Select Iaol EE Err 0 make D SOPHO Messenger Net tel jaarin g Iloc gerra If Len Dir lcl_path vbDirectory 0 Then MkDir lcl_path moek IL ac make D SOPHO Messenger Net log let jeyeneley Ikeiil jeteyel sp ilkexe If Len Dir lcl_path vbDirectory 0 Then MkDir lcl_path Eae IGE make D SOPHO messenger Net log 02001_eAPI lcl_path lcl_path Format g_ekernel_remote_port 00000 _eAPI If Len Dir lcl_path vbDirectory 0 Then MkDir lcl_path ael IS Kill log files older then x days if g_LastLogFile not today If Mid S g_LastLogFile 1 8 lt gt Format Now yyyymmdd Then eAPI_form 8 KILL OLD_LOGFILES lcl_path End If make 20001030 txt lcl_file Format Now yyyymmdd amp txt g_LastLogFile lcl_file open file D SOPHO messenger Net log 02001_eAPI 20001030txt Open lcl_path
253. tion Folder and specify a new location 4 Click Install to start the installation 5 Click Finish after installation completes Installing SQL Server DECT Messenger optionally uses SQL Server for its MessengerData database This database contains runtime message information and increases the performance in high load environments If performance is not an issue you do not need to install SQL Server as DECT Messenger includes a Microsoft Access database that can be used with no additional configuration If an existing Microsoft SQL Server is available for use DECT Messenger can deploy its database to it In this case you only need to provide the credentials SQL system administrator account and password necessary to connect to it 32 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Installing SQL Server Note SQL Server 2000 MSDE2000 are not supported When using an SQL Server installed on a PC different from the DECT Messenger PC the uptime of DECT Messenger depends on the uptime of the database server PC The software continuously uses the database for storing temporary data such as active alarms Therefore stopping the database server PC causes DECT Messenger to stop functioning Installation of the SQL Server Express Edition software requires that the following software be installed on the system e Microsoft NET Framework 3 5 with SP1 selectable from the DVD Main Men
254. tion item and type a new description 5 Click OK to save the changes Configuring PBX information Note When using eDMSAPI you also need to specify the IP address and port of the PBX or IP DECT DAP Controller PC that the module should connect to Modifying the PBX information 1 Expand the Modules node 2 Expand the eDMSAPI node 3 Double click the eDMSAPI area Hilversum node to edit the preconfigured module The module details window appears as shown in the following figure 56 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Configuring DECT Messenger Module eDMSAPI Site 0 1 PBX address Site description NEC fise 168 254 44 Area lD 31 Area description Hilversum Sests count 20 Sests count for eKERNEL 10 Seats count for external 3 Exemal IP address 192 168 0172 Exemal port 2010 Alarm priority for urgent messadine 2 Alarm priory for emergency messaging 1 AFI address 192 168 0172 AFI port 59000 PBX address 192 168 254 48 PBX port 2555 PEX type 353000 PBX license Mersenger Guarding polling interval 60 Guarding retry interval 20 8 PEX addess The current value for this parameter is 192 168 254 48 Figure 27 eDMSAPI module details window 4 Select and modify PBX type to indicate the type of device the module connects to iS3000 Avaya or DAP Controller 5
255. to the e mail system IP address that runs the SMTP Server process When the e mail server supporting SMTP runs on the same system use the loopback value 127 0 0 1 Contact your e mail server administrator to obtain this value e The parameter port refers to the port number configured in the SMTP server for inbound SMTP requests The default value 25 matches most installations Contact the e mail server system administrator to obtain this value e The parameter domain refers to the e mail domain name configured on the SMTP server In most cases this matches the characters after the of the company local e mail addresses Contact the e mail server administrator to obtain this value e The parameter from refers to an e mail address that acts as originator of the e mail address In many cases the syntax matches user domain com In some environments the domain must match the existing domain or be a registered domain Contact the e mail server administrator to obtain this value Avaya recommends that you use an existing e mail address so people can respond to the e mail if necessary e The parameter to is the most important parameter and refers to the e mail address of the destination e mail user Depending on relay settings of the e mail server infrastructure this can be limited to an internal e mail user only which limits you to send e mail only to users of the same domain The parameter to can also be an external e mail user which al
256. u e Microsoft Windows Installer 4 5 selectable from the DVD Main Menu If these items are not already installed you can install them during the SQL Server 2008 Express Edition installation process as they are included on the DECT Messenger DVD Installing SQL Server 2008 Express Edition Note For convenience a free copy of SQL Server 2008 Express Edition is included on the DVD 1 Insert the DECT Messenger product DVD The DVD Main Menu window appears If the Main Menu does not appear double click D Autorun exe where D is the drive letter of your DVD drive 2 If not already installed select and install the following from the DVD Main Menu e Microsoft NET Framework 3 5 with SP1 e Microsoft Windows Installer 4 5 3 From the DVD Main Menu select SQL Server 2008 Express Edition SP1 4 Select Default SQL 2008 Instance or Named SQL 2008 Instance 5 Enter the password for the sa administrator account you will also need this during the main DECT Messenger install Although the SQL Server Express Edition meets all requirements for a live production DECT Messenger system it has the following limitations e The maximum database size is 4 GB SQL Server 2008 Express Edition uses only one processor from the server computer e To schedule backups you must install additional software as SQL Server 2008 Express Edition does not include an SQL agent for this purpose DECT Messenger Installation and Commissioning Bo
257. uration process In the following two figures extension 112 with type LA is defined for location detection DECT Messenger Installation and Commissioning Book 1 March 2012 213 Module eLOCATION Module eDMSAPI xi PBX type DAP controller PBX license Messenger Default ont gi aratior Guarding polling interval 60 Guarding retry interval 20 i Message delay 3 General timeout 15 gt Timeout for second acknowledge 30 Datapath delay 2 i eCSTA area for QD 2 Comments SIP DECT Auto create group False Default output program eDMSAPI Default output program facility C933 Input program description SIP DECT Input program comments SIP DECT amp Inbound data call handling Module eDMSAPI Inbound gt gt gt Module eDMSAPI Inbound Event gt gt gt Module eDMSAPI Inbound Result O Interface with eKERNEL Delete Refresh OK Cancel Figure 158 Module eDMSAPI e The next item that you must define is the correct record in the table eDMSAPI_INBOUND_ EVENT for the special number defined above in the same manner as it is done for all other extensions The following figure shows an example of the special number configuration in the eDMSAPI_INBOUND_EVENT table 214 DECT Messenger Installation and Commissioning Book 1 March 2012 Comments infodev avaya com Architecture Module eDMSAPI xi PBX type DAP controller _JeDMSAPI
258. value Mail Server defines the connection Avaya recommends that you choose meaningful names name for the parameters e Define the parameter port to identify the port number For example use the value 25 specified the port used for SMTP servers e Define the parameter state e Define the parameter Listening for monitoring TCP Servers A TCP Server is always up and running and in state of listening on port 25 on a local system that runs the eFR monitoring process Note You can use the command window to verify the current servers The command netstat a n shows a screen similar to the one shown in the following figure In the figure a TCP server in the first column with the value TCP listening on port 25 in the second column ending with 25 is in the state of listening C WINDOWS system32 cmd exe EI x C gt netstat a n Active Connections k D a a b gt a Local P 0 0 0 0 M Seeoageqgggs State LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING eoeeogoqeoeot Seeaagueoecr Seeoaegeggnp 5 0 8 0 0 0 8 0 0 4 5 5 Figure 114 Verify current servers Note Important NETSTAT assumes that TCP servers remain listening Important Only apply NETSTAT monitoring to TCP Servers that are multiple access socket servers When a TCP server is a single connection server the TCP server is connected while it is monitored by
259. ve not ready to be sent as SNMPv1 trap The following figure shows the message received by the destination device implemented in DECT Messenger module eSNMP The window shows that an SNMPv1 trap is received The varbind 1 parameter contains the message eSNMP SOPHO Messenger Net v3 1 0 fo 2Kernel eSNMP Help lt snmp gt Saddress gt 1U 123 65 159 lt address gt lt version gt 1 lt version gt lt community gt sublic lt community gt senterprise oid gt 1 3 6 1 4 1 28088 32 1 lt enterprise oic gt generic trap gt 6 lt generic trap gt lt specific_trap gt l lt specific trap gt lt timestamp gt J lt timestamp gt svbl_1_01d71 3 6 1 4 1 28088 32 1 14 vb1_1_o1a lt vbl_1_valu2 gt Drive D is not ready lt vbl_1_value gt lt vbl_1_type gt 4 lt vbl_1_ type gt snmo gt lt po ry E Data arrival 137 bytes received from eKERNEL 00019 14 40 00 8 Figure 106 Message received by destination device Monitoring type PING You configure the monitoring of PING through the section starting with tag lt PING gt and ending with closing tag lt PING gt This area contains a starting tag lt Systems gt and ending tag lt Systems gt Adding a lt System gt definition for each system that you want to monitor The window in the following figure shows two definitions one for address 127 0 0 1 and another for address 192 168 1 12 DECT Messenger Installation and Commissioning Book 1 March
260. wers with an ACK lt xml gt lt msgrpy gt lt id gt 00786 lt id gt lt sts_cnt gt 1 lt sts_cnt gt lt sts_01 gt ACK lt sts_01 gt lt msgrpy gt lt xml gt Figure 73 msgrpy message ACK If an incorrect BCC is found delivery fails and the receiving side sends a NACK which is prefixed with error code 1 Transmission error corrupt characters or corrupt BCC received by the station DECT Messenger Installation and Commissioning Book 1 March 2012 123 Module eESPA eESPA handles only data blocks of type 1 Call to Pager data blocks If another type of data block comes in eESPA reacts by sending an ACK but the data block is not processed Delivery can also fail if a timeout occurs while sending the data block The temporary master station which is always the sending side expects to receive an ACK within a timeout of eESPA_Timeout_n seconds In the event of a timeout on sending a data block the sending side tries to re send the data block This retry is attempted x times where x is the defined value of the field eESPA_NAK_retry_cnt_n in the eESPA table After retrying x times and not receiving an ACK the temporary master station decides that the transaction is unsuccessful lt xml gt lt msgrpy gt lt id gt 00786 lt id gt lt sts_cnt gt 1 lt sts_cnt gt lt sts_01 gt NACK lt sts_01 gt lt msgrpy gt lt xml gt Figure 74 msgrpy message NACK Data flow The ESPA4 4 4 protocol prescribes a controllin
261. ype_01 gt PAGING lt type_01 gt lt provider_01 gt BELGACOM lt provider_01 gt lt password gt NONE lt password gt lt number_01 gt 00452500001 lt number_01 gt lt init_01 gt AT amp C0S0 3 lt init_01 gt lt rty_intv_01 gt 60 lt rty_intv_01 gt lt rty_cnt_01 gt 1 lt rty_cnt_01 gt lt snd_depth_01 gt 1 lt snd_depth_01 gt lt snd_time_01 gt 600 lt snd_time_01 gt lt com_port_02 gt COM02 lt com_port_02 gt lt settings_02 gt 9600 N 8 1 lt settings_02 gt lt type_02 gt SMS lt type_02 gt lt provider_02 gt PROXIMUS lt provider_02 gt lt pas sword gt proximus lt password gt lt number_02 gt 00475161622 lt number_02 gt lt init_02 gt AT amp C0S0 3 lt init_02 gt lt rty_intv_02 gt 60 lt rty_intv_02 gt lt rty_cnt_02 gt 2 lt rty_cnt_02 gt lt snd_depth_02 gt 1 lt snd_depth_02 gt lt snd_time_02 gt 600 lt snd_time_02 gt lt log_path gt C SOPHO Messenger net lt log_path gt lt log_days gt 1 lt log_days gt lt cfgrpy gt lt xml gt Figure 38 A typical cfgrqs configuration request and reply Refer to the appropriate sections on the database tables that define the received parameters for more information on each value The information in this document is provided for informational purposes detailed description of these internal inter process communications is beyond the scope of this document If the lt cfgrpy gt shown in Figure 38 A typical cfgrqs configuration request and reply on page 82 is received

Avaya CS1000 User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents