Installation & Configuration Guide

Transcription

1 icds Installation & Configuration Guide Reordering Info: IGICDS/R6, Jun 2014

2 All rights reserved Copyright 2014, Speakerbus Technology Printed in the UK Speakerbus Technology Limited reserves the right to make changes to the information in this document at any time without notice. Information published in this document is believed to be reliable. However, Speakerbus Technology Limited assumes no liabilities for inaccuracies or omissions in this document, or liability arising from the use of such information. Speakerbus Technology Limited assumes no liability for the infringement of patents or other intellectual property rights owned by third parties which may result from the application of this information. No part of this document may be reproduced or transmitted in any form or by any means electronic or mechanical, for any purposes, without the written permission of Speakerbus Technology Limited. Trademarks Speakerbus Technology company logo is a registered trademark of Speakerbus Technology Limited. Speakerbus is a trademark of Speakerbus Technology Limited. Statement of Conditions Speakerbus reserves the right to make changes to the products described in this document without notice. Speakerbus Technology Limited does not assume any liability that may occur due to the use or application of the product(s) describes herein. Previous Revision(s) Revision 1 September 2008 Reviision 2 June 2013 Revision 3 August 2013 Revision 4 December 2013 Revision 5 March 2014

3 Contents About this Guide...5 Using this Guide... 5 Further Help... 5 Related Manuals... 6 Software Version... 6 icds Overview...7 Prerequisites...8 Installation and Configuration Overview... 9 System Requirements...10 Supported Operating Systems Hardware Requirements Physical Requirements Additional Virtualisation Requirements Software Requirements Software Installation...12 Installing the icds Server Application Software Upgrade...17 System Requirements Supported Operating Systems Hardware Requirements Software Requirements Upgrading the icds Server Application Configuration...22 Configuring the icds File imanager Configuration imanager Deskstation Configuration id 712 Deskstations iturret Deskstation Using icds Monitor for Testing & Diagnostic Purposes Uninstalling the icds Server Application

4 Screen Reference...34 icds Configuration File icds Section ServerIPAddress DeviceServerPort ThirdPartyServerPort MonitorPort LogCDR_Events ThirdPartyDevice Section DeviceXProtocol DeviceXIP DeviceXPort icds Monitor Application Introduction Starting the icds Monitor Application Tree Structure Description icds Server Devices rd Party Devices

5 Using this Guide icds Installation & Configuration Guide About this Guide This guide describes how to install and configure the imanager Call Data Services (icds) System. The icds system is middleware which handles call data records (CDR), allowing third party devices such as voice recorders or call loggers to receive the call data records. Before operating the icds system, please read these instructions carefully. The icds Installation & Configuration Guide comprises of the following sections: icds Architecture Prerequisites Solution Installation and Configuration Overview Software Installation Software Upgrade Configuration Using icds Monitor for Diagnostic & Testing Purposes Uninstalling the icds Server Application Screen Reference Further Help In all instances, first seek help from your System Administrator. If necessary, your System Administrator can the Speakerbus Global Helpdesk at Please supply the following from the icds server: Speakerbus Log files for the period around the problem: File location C:\Program Files\Speakerbus Technology Ltd\i cds\ LogFiles. A copy of the icds.ini file: File location C:\Program Files\Speakerbus Technology Ltd\i cds\bin. Microsoft Windows Event Logs: Application Log Security Log (if available) 5

6 System Log System Information: Host name and IP Information (LmHost/Hosts file) Speakerbus Software levels Any other pertinent information. Related Manuals This document needs to be used in association with the following documents: imanager Installation Guide imanager Administrator s Guide Software Version This document is written for icds software version 2.2 (and above). 6

7 icds Overview icds is the middleware software which handles call data records. The diagram below displays the icds network architecture. If the voice recorder supports RTP audio the turrets send recording streams direct to voice recorders through voice over internet protocol (VOIP). If the voice recorder does not support RTP audio, the recording streams can be sent via a Speakerbus analogue or digital gateway to accommodate legacy recording solutions. 7

8 Prerequisites This document assumes the icms server is already installed and the appropriate deskstations (id 712 and iturret Deskstations) have users seated on them. It also assumes a third party voice recorder is installed and configured. Please note that the machine that the icds Server Application is being upgraded on will require a system restart after the installation process. 8

9 Installation and Configuration Overview To install and configure the icds solution please complete the following steps: 1. Install or upgrade the icds Server Application. For more information, see the Software Installation section on page 12 or the Software Upgrade section on page Configure the appropriate settings within the CDS.ini file for icds and voice recording. For more information, see the Configuring the icds File section on page Restart the Speakerbus icds service using the Computer Management console. 4. Configure the appropriate settings and options using imanager. For more information, see the imanager Configuration section on page 23. If the icds Server Application needs to be uninstalled please refer to the Uninstalling the icds Server Application section on page 32. 9

10 System Requirements Supported Operating Systems icds Server Microsoft Windows Server 2003 Microsoft Windows Server 2003 R2 Microsoft Windows Server 2008 R2 Microsoft Windows Server 2012 R2 icds Monitor Microsoft Windows XP Microsoft Windows Server 2003 Microsoft Windows Server 2003 R2 Microsoft Windows Vista Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Microsoft Windows 7 Hardware Requirements Physical Requirements Processor Intel Pentium 4 Processor (or 100% compatible) RAM 1Gb RAM (512 RAM Minimum) Network Ethernet card with TCP/IP installed Additional Virtualisation Requirements icds can be supported on either VMWare or Microsoft Hypervisor virtualised environments. Speakerbus supports VMWare Server ESXi V4.1 and V5 along with Microsoft Hyper V 2008 R2. The minimum host server specification is based on a Speakerbus Appliance Server and is as follows: Processor: Intel XEON (E5520 8MB Cache 2.26Ghz) RAM: 2GB Hard Disk: 135GB Guest configuration for icds is as follows: CPU: 2 Processors minimum, 4 Processors recommended RAM: 1Gb RAM minimum, 4Gb RAM recommended Network: Directly connected to the physical network using auto detect (switch port connected to should be a minimum of 100/Full). For ESXi you must use E1000 as the network adapter. 10

11 Hard Disk: Minimum 20GB avaliable. This can be thin provisioned. Software Requirements Microsoft.NET Framework

12 Software Installation Installing the icds Server Application To install the icds Server Application: 1. Locate the icds installation files and double click Setup.msi. This displays the icds Main Menu. 2. Click Install icds. This displays the Welcome InstallShield. The installation checks if the server has Microsoft.NET Framework 2.0 already installed. If it is not installed you will be invited to install Microsoft.NET Framework Click Next. This displays Customer Information. 12

13 4. Type a user name and company name in User Name and Company Name respectively. 5. Click Next. This displays Choose Destination Location. 6. If the default installation location is appropriate click Next. This displays Select Features. 13

14 Typically both the Monitor and Server components will both be installed on the server machine. However you can install the Monitor component separately on a machine other than the server to use it as a diagnostic tool, to ensure the icds is running correctly. 7. Click Next. This displays the Speakerbus Software License Agreement. 8. Accept the license agreement and click Next. This displays the Apache License Agreement. 14

15 9. Accept the license agreement and click Next. This displays Ready to Install the Program. 10. Select Install. The installation process will now take place. The InstallShield wizard below is displayed when the installation is complete. 15

16 11. Click Finish on the InstallShield wizard ensuring the Start the icds Server service check box is selected. 16

17 Software Upgrade System Requirements Supported Operating Systems icds Server Microsoft Windows Server 2003 Microsoft Windows Server 2003 R2 Microsoft Windows Server 2008 R2 Microsoft Windows Server 2012 R2 icds Monitor Microsoft Windows XP Microsoft Windows Server 2003 Microsoft Windows Server 2003 R2 Microsoft Windows Vista Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Microsoft Windows 7 Hardware Requirements Processor Intel Pentium 4 Processor (or 100% compatible) RAM 1Gb RAM (512 RAM Minimum) Network Ethernet card with TCP/IP installed Software Requirements Microsoft.NET Framework 2.0. Upgrading the icds Server Application Please note that the machine that the icds Server Application is being upgraded on will require a system restart after the installation process. To upgrade the icds Server Application: 1. Locate the icds installation files and double click Setup.msi. This displays the icds Main Menu. 17

18 2. Click Install icds. This displays the Welcome InstallShield. The installation checks if the server has Microsoft.NET Framework 2.0 already installed. If it is not installed you will be invited to install Microsoft.NET Framework Click Next. This displays Select Features. 18

19 Typically both the Monitor and Server components will both be installed on the server machine. However one may install the Monitor component separately on a machine other than the server to use it as a diagnostic tool, to ensure the icds is running correctly. 4. Click Next. This displays the Speakerbus Software License Agreement. 5. Accept the license agreement and click Next. This displays the Apache License Agreement. 19

20 6. Accept the license agreement and click Next. This displays Ready to Install the Program. 7. Select Install. The installation process will now take place. Any previous installed versions of the icds Server Application will be uninstalled and removed before the new version is installed. The InstallShield wizard below is displayed when the installation is complete. 20

21 8. Click Finish. You will be prompted to restart the machine. 9. Ensure the Yes, I want to restart my computer now option is selected, and click OK to restart the machine. When the machine has restarted the Speakerbus icds Service will automatically start running. 21

22 Configuring the icds File Configuration The icds Configuration filename is CDS.ini and is typically located at the following directory path: C:\Program Files\Speakerbus Technology Ltd\iCDS\Bin This section will briefly described how to set up the file for a single third party voice recorder. For more information on each setting within the CDS.ini file, see the Screen Reference section on page Open the CDS.ini file. You will notice the [icds] section within the file displays the following information: ServerIPAddress= DeviceServerPort=7788 ThirdPartyServerPort=7789 MonitorPort=8850 LogCDR_Events=0 The ServerIPAddress option will be left blank in most cases. An IP address will only need to be specified if the machine running the icds Server Application has multiple network adapters. The DeviceServerPort number is used by the id 712 or iturret Deskstation to connect them to the icds Server Application. The ThirdPartyServerPort number is used by third party voice recorders to connect to the ics Server Application The MonitorPort is required when using the icds Monitor Application. Upon opening you will be prompted to enter the MonitorPort number. The LogCDR_Events option is used for logging CDR messages for diagnostic purposes. The [ThirdPartyDevice] section within the file displays the parameters required to connect to a third party voice recorder. An example of the parameters are displayed below. The values associated with each parameter are used for example purposes. Device1Protocol=Client Device1IP= Device1Port=

23 The Device1Protocol option needs to be set to either Client, UDPClient or Server. Please contact the voice recorder vendor for what this setting should be set to. The Device1IP option needs to specify the IP address of the third party voice recorder. The Device1Port option needs to specify the port number of the third party voice recorder. 2. Save the CDS.ini file. 3. Restart the Speakerbus icds Server service using the Computer Management console. imanager Configuration imanager, the management application used to manage the icms server, is required to configure the iturret and id 712 Deskstations for the icds Server. This section describes how to set up iturret and id 712 Deskstations with third party voice recorders using imanager. Please note imanager version 2.5 is used to set up the icds and voice recording. imanager Deskstation Configuration id 712 Deskstations In this section you will: create an icds Server network service create an Voice Recorder network service connect the Voice Recorder network service to the Default Intercom Recording policy connect the icds Server network service to the Default Call Logging policy, and ensure Default Intercom Recording and Default Call Logging policies are attached to an id 712 Deskstation. Using imanager create an icds Server network service. To do this: 1. Select Network Services from the side menu and click New. This displays the small Network Services General tab. 23

24 2. Type a name for the icds Server in the Name text box. 3. Select icds Server from the Type. This displays the icds server settings. 4. Type the IP address and port number of the icds Server in Private Address and Public Adress Port respectively. 5. Click OK to save the changes. Create a Voice Recorder network service. To do this: 1. Ensure Network Services is selected again and click New. This displays the Network Services General tab. 2. Type a name for the voice recorder in the Name text box. 3. Select Voice Recorder from the Type list box. This displays the voice recording settings. 24

25 4. Type the voice recorder IP address in Private Address and click OK. Please ensure the IP address matches the Device1IP setting under the ThirdPartyDevice section within the CDS.ini file. For more information, see ThirdPartyDevice Section on page 35. Connect the Voice Recorder network service to the Default Intercom Recording policy. To do this: 1. Select Policies from the side menu. 2. Select Default Intercom Recording from the list box. This displays the Default Intercom Recording options. 3. Select the Stream #1 tab to display its settings. 4. Select the voice recording network service that you created earlier (in steps 6 to 9) from the Primary Recorder list box. 5. Type the voice recording port number in the Voice Recorder Port text box and click Apply. Please ensure the port number matches the Device1Port setting under the ThirdPartyDevice section within the CDS.ini file. For more information, see ThirdPartyDevice Section on page 35. Connect the icds Server network service to the Default Call Logging policy. To do this: 1. Select Policies from the side menu. 2. Select Default Call Logging from the list box. This displays the Default Call Logging options. 3. Select the icds Server network service that you created earlier (in steps 1 to 5) from the Primary icds Server list box and click Apply. 25

26 Ensure the Default Call Logging and Default Intercom Recording policies are attached to the id 712 Deskstation. To do this: 1. Select the Deskstations side menu and click the required id 712 Deskstation. This displays the id 712 Deskstation s tab settings. 2. Select the Recording tab for the id 712 Deskstation. 3. Ensure the Call Logging Policy option is set to Default Call Logging. 4. Ensure the Recording Policy option is set to Default Intercom Recording. 5. Click Apply if required. iturret Deskstation In this section you will: create an icds Server network service create an Voice Recorder network service connect the Voice Recorder network service to the Default Intercom Recording policy connect the icds Server network service to the Default Call Logging policy, and ensure Default Intercom Recording and Default Call Logging policies are attached to an iturret Deskstation. Using imanager create an icds Server network service. To do this: 1. Select Network Services from the side menu and click New. This displays the small Network Services General tab. 2. Type a name for the icds Server in the Name text box. 3. Select icds Server from the Type. 26

27 This displays the icds server settings. icds Installation & Configuration Guide 4. Type the IP address and port number of the icds Server in Private Address and Private Adress Port respectively. 5. Click OK to save the changes. Create a Voice Recorder network service. To do this: 1. Ensure Network Services is selected again and click New. This displays the small Network Services General tab. 2. Type a name for the voice recorder in the Name text box. 3. Select Voice Recorder from the Type list box. This displays the voice recorder settings. 4. Type the voice recorder IP address in Private Address and click OK. Please ensure the IP address matches the Device1IP setting under the ThirdPartyDevice section within the CDS.ini file. For more information, see ThirdPartyDevice Section on page 35. Connect the Voice Recorder network service to the Default Intercom Recording policy. To do this: 1. Select Policies from the side menu. 2. Select Default iturret Recording from the list box. 27

28 This displays the Default iturret Recording options. 3. Select the Stream #1 tab to display its settings. 4. Select the voice recording policy created earlier from the Primary Recorder list box. 5. Type the voice recording port number in the Primary Port text box and click Apply. Please ensure the port number matches the Device1Port setting under the ThirdPartyDevice section within the CDS.ini file. For more information, see ThirdPartyDevice Section on page 35. Connect the icds Server network service to the Default Call Logging policy. To do this: 6. Ensure Policies is selected on the side menu. 7. Select Default Call Logging from the list. This displays the Default Call Logging options. 8. Select the icds Server network service created earlier from the Primary icds Server list box and click Apply. 28

29 Ensure the Default Call Logging and Default Intercom Recording policies are attached to the iturret Deskstation. To do this: 1. Select the Deskstations side menu and click the required iturret Deskstation. This displays the iturret Deskstation s tab settings. 2. Select the Recording tab for the iturret Deskstation. 3. Ensure the Call Logging Policy option is set to Default Call Logging. 4. Ensure the Recording Policy option is set to Default iturret Recording. 5. Click Apply if required. 29

30 Using icds Monitor for Testing & Diagnostic Purposes This section will describe how to test the configuration of the CDS.ini file (completed in the Configuring the icds File section on page 22) and imanager configuration (completed in the imanager Configuration section on page 23). For more information and description on the all the options within the icds Monitor application, see icds Monitor Application on page Start the icds Monitor application. This displays the IP address and port number options. These are required to connect to the icds Server application. 2. Type the IP address and port number of the server used to run the icds Application in the IP Address and Port text boxes respectively. Click OK. The icds Monitor should now be connected to the icds Server application. 3. Expand the icds Server tree option to display the Settings and Threads options. 4. Double click the Threads option to display the Threads dialog 30

31 5. Ensure the (i) icds Server Thread and icds Monitor Thread status are Running and (ii) 3rd Party Device status are Running - Connected. You should also notice that the deskstation and voice recorder configured earlier is connected to the icds Server Application. This is indicated within the tree structure. The number in the brackets for Devices indicate the number of connected deskstations. The deskstation s IP address and port number is also displayed when the Devices option is expanded. The number in the brackets for 3rd Party Devices indicate the number of connected voice recorders. The voice recorder s IP address and port number is also displayed when the 3rd Party Devices option is expanded. 31

32 Uninstalling the icds Server Application To uninstall the icds server application: 1. Open Add or Remove Programs through the Windows Control Panel. 2. Select icds from the list of currently installed programs and click Remove. 3. Confirm you wish to remove the icds Server Application by selecting OK on the Confirm Uninstall information box. This displays the InstallShield wizard. 32

33 Click Next. icds Installation & Configuration Guide The icds InstallShield wizard will now begin uninstalling the icds Server Application. The InstallShield wizard below is displayed when the uninstallation process is complete. You will also notice the icds Server Application has been removed from the Add or Remove Programs software list. 33

34 Screen Reference This section describes the parameters and functions on both the icds Configuration file and icds Monitor Application. icds Configuration File The icds Configuration File is used to specify the configuration parameters for the icds server. The default configuration file location is C:\Program\ Speakerbus Technology Ltd\bin. The exact filename description is CDS. ini. It is located in the same folder directory as the icds server executable file (CDSServer.exe). When opened, the.ini file has two sections: [icds] and [ThirdPartyDevice]. These two sections are described in more detail below. icds Section The icds section comprises of the following settings: ServerIPAddress, DeviceServerPort, ThirdPartyServerPort and MonitorPort. These settings are described below. Changes to the ini file may require the icds server service to be restarted. Please refer to the information for each setting for details of which settings require a restart of the icds server service. Below is an example of the parameters and syntax used for the icds settings. ServerIPAddress= DeviceServerPort=7788 ThirdPartyServerPort=7789 MonitorPort=8850 ServerIPAddress This is the IP address used by the icds server to listen for device and third party connections. When the machine running the icds has multiple network adapters, specifying a specific IP address in this setting will force the icds server to only listen on one specific adapter. If this setting is blank the icds server will listen on all available network adapters. The icds Server service must be restarted for changes to this setting to take effect. Below is an example of the parameter and syntax used for ServerIPAddress setting. ServerIPAddress= DeviceServerPort This is the port number that the icds server uses to listen for device connections. The default value is The icds Server service must be restarted for changes to this setting to take effect. Below is an example of the parameter and syntax used for DeviceServerPort setting. DeviceServerPort=

35 ThirdPartyServerPort icds Installation & Configuration Guide This is the port number that the icds server uses to listen for third party device connections. The default value is The icds Server service must be restarted for changes to this setting to take effect. Below is an example of the parameter and syntax used for ThirdPartyServerPort setting. MonitorPort ThirdPartyServerPort=7789 This is the port number that the icds server uses to listen for icds monitor connections. The default value is When no value is set the monitor port is disabled. To change this at runtime, the setting must be configured as blank first, saved, and then a new value entered and saved. Below is an example of the parameter and syntax used for MonitorPort setting. MonitorPort=8850 LogCDR_Events This option is used for logging CDR messages for diagnostic purposes. Please note that enabling this may cause icds performance issues, especially if the configuration contains a large number of iturret Deskstations. For this reason, this should only be enabled if instructed to do so by a member of the Speakerbus Technical Operations Team. In new installations from software version 2.2 and above the CDS.ini file within the [icds] section will contain the following string by default: LogCDR_Events=0 The 0 in the above string means CDR message logging is disabled. The 0 needs to be replaced with a 1 as shown below to enable CDR message logging. LogCDR_Events=1 Entering anything other than 1 after the = symbol will default CDR message logging. Please note that if the icds software has been upgraded from a pre 2.2 software version to software version 2.2 and above, you will need to manually change the CDR message string from LogCDR_Events=true to either LogCDR_Events=0 or LogCDR_Events=1. ThirdPartyDevice Section This section details the configuration for third party device connections, (for example, call loggers and voice recording devices). The details of each connection must be configured in this section. The icds server can accommodate up to sixteen third party device connections. The sixteen third party device connection parameters and syntax is laid out in the icds 35

36 configuration file. An example of the parameter detail for the first third party device connection looks as follows: Device1Protocol=Client Device1IP= Device1Port=8000 The above will almost be identical for other third party device connections accept where each parameter has the number 1 after the word Device, the number 2 for example, will be used for the second third party device connection. As previously mentioned above a maximum of sixteen third party device connections can be accommodated. The line parameters (DeviceXProtocol=, DeviceXIP=, and DeviceXPort) are described in the sections below. DeviceXProtocol Where X is the arbitrary third party device number, this is the protocol used to the third party device. This should be set to Client when the icds server connects to the third party device, UDPClient when icds connects to a third party using UDP or Server when the third party device connects to the icds server. Please contact the voice recorder vendor for what this setting should be set to. A blank setting disables this device connection. The icds Server service must be restarted for changes to this setting to take effect. DeviceXIP Where X is the arbitrary third party device number, this is the IP address of the third party device. A blank setting disables this device connection. The icds Server service must be restarted for changes to this setting to take effect. DeviceXPort Where X is the arbitrary third party device number, this is the port number of the third party device. A blank setting disables this device connection. The icds Server service must be restarted for changes to this setting to take effect. icds Monitor Application Introduction The icds Monitor Application is a diagnostic tool used to test the connection of the icds Server Application with connected deskstations and voice recorders. This section will describe: how to start the icds Monitor Application, and the parameter settings within the application. 36

37 Starting the icds Monitor Application icds Installation & Configuration Guide When attempting to start the icds Monitor application the screen the main graphical user interface application is displayed. A small dialog, Connect to icds Server, is also displayed. Below is an explanation of what is required in the text box options: The IP Address - The IP address in this option needs to match the IP address used to run the icds Server application. Port - The port number in this option needs to match the port number used to run the icds Server application. The port number can be obtained from the CDS.ini file alongside the MonitorPort option. Lastly, the OK button needs to be selected when the IP address and port number has been typed into the IP Address and Port text boxes respectively. Tree Structure Description The icds Monitor Tree Structure has three main sections: icds Server, Devices and 3rd Party Devices. The icds server refers to the icds Server application. Devices refers to deskstations and can include id 712 or / and iturret deskstations. These three sections are described further below. 37

38 icds Server The icds Server tree structure has two options when expanded: Settings and Threads. These two options are fully explained below. Settings Dialog The Settings information dialog is displayed when one double clicks the Settings tree option. This action displays the Settings dialog which contains a number of read only settings. Most of these settings can be changed in the CDS.ini Configuration file. For more information, see icds Configuration File on page 34. The above read only options are described below. icds Server IP Address - This is the IP address used by the icds server to listen for device and third party connections. When the machine running the icds has multiple network adapters, specifying a specific IP address in this setting will force the icds server to only listen on one specific adapter. If this setting is blank the icds server will listen on all available network adapters. Device Server Port - This is the port number that the icds server uses to listen for device connections. The default value is Third Party Server Port - This is the port number that the icds server uses to listen for third party device connections. The default value is Monitor Port - This is the port number that the icds server uses to listen for icds monitor connections. The default value is When no value is set the monitor port is disabled. Heartbeat Interval - This is the interval time period the device sends a heartbeat to the third party voice recorder. The interval period is 60 seconds. If the device does not receive a heartbeat from the third party voice recorder within 60 seconds the socket to the voice recorder is closed. Device Timeout - This is the timeout period in seconds for the device heartbeat to the icds Server Application. The timeout period is 90 seconds. If the device does not receive a heartbeat within 90 seconds the 38

39 socket to the icds Server Application is closed. Threads Dialog icds Installation & Configuration Guide The Threads dialog is displayed when one double clicks the Threads tree option. Its main purpose is to provide a real time visual indication of connected and running components. Components being the icds Server Application, icds Monitor Application and Third Party Voice Recorders. Below provides a description of the parameters and settings: Thread - This column details the different threads and described below. icds Server Thread - This option refers to the icds Server Application and contains a green indicator when it is running and a red indicator when it is not running. icds Monitor Thread - This option refers to the icds Monitor Application and contains a green indicator when it is running and a red indicator when it is not running. 3rd Party Device Thread - This option refers to the third party voice recorder and contains a green indicator when it is running and a red indicator when it is not running. The icds Server Application can accommodate a maximum of sixteen voice recorders. Status - This column contains the following status: Running, Running - Connected and Not Running. Message Queue - This is a real time count of the message waiting to be sent to the icds Server Application. Most of the time the value should be 0 or very low. If the number is high this may indicate a message traffic issue. 39

40 Devices Devices Dialog The Devices tree structure when expanded displays connected deskstations (id 712s and iturrets). The IP address and port number of the connected deskstation is displayed within the tree structure. Double clicking the link displays the Device dialog. An illustration of this dialog is shown below. The available settings in the above dialog are listed and described below. IP Address - This displays the IP address of the deskstation. Port - This displays the port number of the deskstation. Protocol Version - This displays the deskstation version number. User id - This displays the extension of the deskstation. Username - This displays the name of the person who owns the user id or extension number. Connected - This displays the date and time when the icds Server Application connected to the deskstation. Last Message Received - This displays the date and time the device last sent a message to the icds Server Application. Sequence Number - Sequence numbers are displayed in the blank space in the bottom half of the Device dialog. The sequence number refers to an events undertaken by the connected deskstation. 40

41 3rd Party Devices icds Installation & Configuration Guide The 3rd Party Devices tree structure when expanded displays connected third party voice recorders. The IP address and port number of the connected voice recorder is displayed within the tree structure. Double clicking the link displays the 3rd Party Device dialog. An illustration of this dialog is shown below. The above read only options are described below. IP Address - This is the IP address of the voice recorder. A blank setting disables this device connection. Port - This is the port number of the voice recorder. A blank setting disables this device connection. Protocol - This is the protocol used to the third party voice recorder. This will be set to either Client when the icds server connects to the voice recorder, or Server when the voice recorder connects to the icds server. Please contact the voice recorder vendor for what this setting should be set to. A blank setting disables this device connection. Connected - This displays the date and time when the icds Server Application connected to the third party voice recorder. Last Message Sent - This displays the date and time the voice recorder last sent a message to the icds Server Application. Send Queue - This is a real time count of the message waiting to be sent to the icds Server Application. Most of the time the value should be 0 or very low. If the number is high this may indicate a message traffic issue. 41

42

43

44 Speakerbus Technology Limited 2014 Registered Office: Fourways House, 4-10 Ware Road, Hoddesdon, Hertfordshire EN11 9RS Registered in England No: