Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Configuring Conveyant Systems Sentry E9-1-1 Solution with Avaya Aura Application Enablement Services and Avaya Aura Communication Manager - Issue 1.0 Abstract These Application Notes describe the procedures for configuring the Conveyant Systems Sentry E9-1-1 Solution to interoperate with Avaya Aura Application Enablement Services (AES) and Avaya Aura Communication Manager. The Conveyant Systems Sentry E9-1-1 Solution is a software based solution that is comprised of a network tracker and scout service. The network tracker service (i.e. Conveyant Network Tracker) automates the tracking of an IP phone s switch and port on the network. The scout service (i.e. Aura Scout) establishes a Device, Media, and Call Control (DMCC) client connection to Application Enablement Services to receive a notification (event) when an emergency number has been dialed. The scout service also establishes a System Management Service (SMS) client connection to Application Enablement Services to receive data and push updates to the Communication Manager. Information in these Application Notes has been obtained through DevConnect compliance testing and additional technical discussions. Testing was conducted via the DevConnect Program at the Avaya Solution and Interoperability Test Lab. 1 of 29

2 1. Introduction These Application Notes describe the procedures for configuring the Conveyant Systems Sentry E9-1-1 Solution to interoperate with Avaya Aura Application Enablement Services (AES) and Avaya Aura Communication Manager. When an emergency call (e.g. 911) has been placed, an organization s ability to provide assistance to the first responders is a crucial component in keeping employees, customers, patients, guests, and others safe. Some of the immediate responsibilities of the organization include identifying the caller s exact location and notifying on-site personnel that an emergency call has been made. The Conveyant Systems Sentry E9-1-1 Solution is a tool to assist enterprises in protecting themselves and their customers in an emergency. By providing on-site notification to key personnel, via screen pops or , first responders may quickly be directed to the emergency. In addition, database management facilities ensure that the right information is sent to the Public Safety Answering Point (PSAP), and that the call is directed to the right place. The Conveyant Systems Sentry E9-1-1 Solution is comprised of a network tracker and scout service. To determine a caller s location, the Conveyant Systems Sentry E9-1-1 Solution utilized the network tracker service to actively query the network switches to determine where IP phones are physically located. To track IP phones across an enterprise network, the network tracker service relies on two things: 1. Managed network switches that can be queried via SNMP v2c to determine what devices are physically connected to the switch s ports. 2. A network map describing the relationship between network switch ports and actual physical locations. When an IP phone s location is detected on the network, the Aura Scout will push the phone s Emergency Location Extension (ELE) to Communication Manager via the System Management Service (SMS) interface of Application Enablement Services. Additionally, the Aura Scout Service utilizes the Device, Media, and Call Control (DMCC) interface of Application Enablement Services to receive an event when an emergency call has been placed. 2. General Test Approach and Test Results This section describes the general test approach used to verify the interoperability of the Conveyant Systems Sentry E9-1-1 Solution with an Avaya infrastructure (consisting of Avaya Aura Application Enablement Services and Avaya Aura Communication Manager). This section also covers the test results. 2 of 29

3 2.1. Interoperability Compliance Testing The general test approach was to verify the integration of the Sentry E9-1-1 Solution with Application Enablement Services and Communication Manager. Various emergency calls were placed from Avaya non-sip endpoints (i.e. analog, digital, and H.323 endpoints) to an emergency number to verify the events were properly logged by the Sentry E9-1-1 solution in a timely manner. IP telephones were given different IP addresses, and the IP phones were moved between different switches and ports within the network to verify that the Sentry E9-1-1 solution correctly identified the IP address and network location of each phone. Additionally, basic serviceability testing examined the handling of and recovery from error conditions (such as network disconnects and power failures) Test Results The Conveyant Systems Sentry E9-1-1 Solution successfully passed compliance testing Support For technical support on the Conveyant Systems Sentry E9-1-1 solution, contact Conveyant Systems at: Web: Phone: (949) support@conveyant.com 3 of 29

4 3. Reference Configuration Figure 1 below illustrates the reference configuration used during compliance testing. The Conveyant Systems Sentry E9-1-1 Solution (Sentinel Web Server, Network Tracker, and Aura Scout) was installed on a Windows Server 2008 R2 Enterprise system. Figure 1: Sentry E9-1-1 Solution with AES and Communication Manager 4 of 29

5 4. Equipment and Software Validated The following equipment and software were used for the reference configuration in Figure 1: Equipment Avaya S8300D Server with an Avaya G450 Media Gateway Dell PowerEdge R610 Server Avaya Ethernet Routing Switch T-PWR Avaya 9600 Series IP Deskphones Various Avaya Analog and Digital endpoints Windows Server 2008 R2 Enterprise Server Software Avaya Aura Communication Manager 6.0.1, R016x , Patch (Avaya Aura System Platform: ) Avaya Aura Application Enablement Services (Avaya Aura System Platform: ) FW: SW: v Service Pack 2 (H.323) - Conveyant Systems Sentry E9-1-1 Solution Configure Avaya Aura Communication Manager This section provides the procedures for configuring Avaya Aura Communication Manager as provisioned in the reference configuration (Figure 1). The assumption has been made that the basic configuration for connectivity between Communication Manager and AES has already been completed. It is also assumed that a login and password account has been created on Communication Manager (which will be utilized by the SMS client). An account can be created by logging into the Communication Manager System Management Interface and navigating to Administration Server (Maintenance) Administrator Accounts. During compliance testing, an account with the login name sentry was created. The configuration of Communication Manager was performed using the System Access Terminal (SAT). After the completion of the configuration, perform a save translation command to make the changes permanent. 5 of 29

6 1. Create an IP Softphone with a Crisis Alert Button Use the add station command to create a soft phone with a crisis alert button. A valid Extension must be entered as part of the add station <extension> command Set Type to 9630 Enter a descriptive Name (optional) Set the Security Code to match the Extension Set IP Softphone to y add station Page 1 of 5 STATION Extension: Lock Messages? n BCC: 0 Type: 9630 Security Code: TN: 1 Port: S00047 Coverage Path 1: COR: 1 Name: Sentry Coverage Path 2: COS: 1 Hunt-to Station: STATION OPTIONS Time of Day Lock Table: Loss Group: 19 Personalized Ringing Pattern: 1 Message Lamp Ext: Speakerphone: 2-way Mute Button Enabled? y Display Language: english Button Modules: 0 Survivable GK Node Name: Survivable COR: internal Media Complex Ext: Survivable Trunk Dest? y IP SoftPhone? y IP Video Softphone? n Short/Prefixed Registration Allowed: default Customizable Labels? y One Page 2, note the Emergency Location Ext field and value. This value can be modified by the Conveyant Systems Sentry E9-1-1 solution as described in Section 8, Step 2. add station Page 2 of 5 STATION FEATURE OPTIONS LWC Reception: spe Auto Select Any Idle Appearance? n LWC Activation? y Coverage Msg Retrieval? y LWC Log External Calls? n Auto Answer: none CDR Privacy? n Data Restriction? n Redirect Notification? y Idle Appearance Preference? n Per Button Ring Control? n Bridged Idle Line Preference? n Bridged Call Alerting? n Restrict Last Appearance? y Active Station Ringing: single EMU Login Allowed? n H.320 Conversion? n Per Station CPN - Send Calling Number? Service Link Mode: as-needed EC500 State: enabled Multimedia Mode: enhanced Audible Message Waiting? n MWI Served User Type: AUDIX Name: Display Client Redirection? n Select Last Used Appearance? n Coverage After Forwarding? s Multimedia Early Answer? n Remote Softphone Emergency Calls: as-on-local Direct IP-IP Audio Connections? y Emergency Location Ext: Always Use? n IP Audio Hairpinning? n 6 of 29

7 Create an IP Softphone with a Crisis Alert Button (continued) One Page 4, add a crisis alert button (crss-alert). As a result of adding this button, the station will receive an alert when an emergency number has been dialed. The Conveyant Systems Sentry E9-1-1 Solution uses DMCC to monitor this station in order to receive an event when an emergency number has been dialed. Conveyant Systems logs the event and can take additional action such as notifying key personnel on-site via screen pops or . During compliance testing, only the logged events were verified (via their Sentinel web interface) to ensure their timely delivery and accuracy. Additional actions that Conveyant Systems may take to relay the data (e.g. generating a screen-pop or ) were beyond the scope of compliance testing. add station Page 4 of 5 STATION SITE DATA Room: Headset? n Jack: Speaker? n Cable: Mounting: d Floor: Cord Length: 0 Building: Set Color: ABBREVIATED DIALING List1: List2: List3: BUTTON ASSIGNMENTS 1: call-appr 5: 2: call-appr 6: 3: call-appr 7: 4: crss-alert 8: voic 2. Configure an Emergency Number During compliance testing, since Communication Manager was connected to the PSTN, 911 was never dialed to avoid an actual 911 call being placed and having local authorities alerted. Rather, an arbitrary emergency number (i.e ) was created and used during testing. To create an emergency number, use the change ars analysis command to enter a Dialed String that has a Call Type of alrt. change ars analysis 2 Page 1 of 2 ARS DIGIT ANALYSIS TABLE Location: all Percent Full: 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd alrt n 7 of 29

8 6. Configure Avaya Aura Application Enablement Services This section provides the procedures for configuring Avaya Aura Application Enablement Services as provisioned in the reference configuration (Figure 1). The assumption has been made that the basic configuration for connectivity between Communication Manager and AES has already been completed. Step 1. Login Access the AES OAM web based interface by using the URL in an Internet browser window, where <ip-address> is the IP address of the AES server. Click the Continue to Login link (not shown). The Login screen is displayed as shown below. Log in using appropriate credentials. The Welcome to OAM screen is displayed, as shown below. 8 of 29

9 2. Enable DMCC Unencrypted Port Navigate to Networking Ports to enable DMCC Unencrypted Port Click the Apply Changes button (not shown). 9 of 29

10 3. Enable Standard Reserved Ports Navigate to Security Standard Reserved Ports to enable HTTP Port 80 and TOMCAT HTTP Port Click the Apply Changes button (not shown). 10 of 29

11 4. Add User Navigate to User Management User Admin Add User to create a DMMC user login and password. Enter appropriate values for User Id, Common Name, Surname, User Password, and Confirm Password. Set CT User to Yes. Click the Apply button (not shown). 11 of 29

12 5. Edit User Navigate to Security Security Database CTI Users List All Users. Select the User ID (i.e. Sentry) created in the previous step and click the Edit button. Check the box for Unrestricted Access to give the user the ability to monitor the station added in Section 5, Step 1. Click the Apply Changes button. 12 of 29

13 7. Configure Conveyant Systems Sentry E9-1-1 Solution This section provides the procedures for configuring the Conveyant Systems Sentry E9-1-1 Solution as provisioned in the reference configuration (Figure 1). Step 1. Aura Scout Installation & Configuration Double-click the AuraScoutInstaller.msi file provided by Conveyant Systems to begin the Aura Scout installation. Install and configure the Aura Scout as directed by Conveyant Systems. During installation, enter the following information shown below: Sentinel Settings o Sentinel Service URL Set to localhost/sentinel/rest AES Settings o AES User Name: Set to <login>@<communicationmanager_ipaddress>. <login> is the login name used to access Communication Manager (as referenced in the first paragraph of Section 5). The IP Address of Communication Manager in the reference configuration (Figure 1) is o AES Password: Set to the password associated with the login name used to access Communication Manager (as referenced in the first paragraph of Section 5). AES SMS Address: Set to The IP Address of AES in the reference configuration (Figure 1) is Check the box to Enable Crisis Alerting Crisis Alert Settings o Crisis Alert Extension: Set to the extension of the station added in Section 5, Step 1 (i.e ). 13 of 29

14 14 of 29

15 Aura Scout Installation & Configuration (continued) Use the scroll bar on the right to scroll further down the screen and enter the following information: DMCC User Account o User Name: Enter the User Id created in Section 6, Step 4. o Password: Enter the User Password created in Section 6, Step 4. AES Settings o IP Address: Enter the IP address of AES. o Port: Enter the DMCC Unencrypted Port as shown in Section 6, Step 2. CM Settings o Switch IP: Enter the IP address of Communication Manager. o Switch Name: Enter the Connection Name for the Switch Connection configured on AES. The Connection Name is not shown in this document since it is configured while setting up basic connectivity between AES and Communication Manager; however, the Connection Name can be found by navigating to Communication Manager Interface Switch Connections in the AES OAM web based interface used in Section 6. Click the Apply Changes button. 15 of 29

16 2. Network Tracker Installation & Configuration Double-click the NetworkTrackerInstaller.msi file provided by Conveyant Systems to begin the Network Tracker installation. Install and configure the Network Tracker as directed by Conveyant Systems. During installation, enter the following information on the screen below: Sentinel Settings o Sentinel Service URL Set to localhost/sentinel/rest Click the Apply Changes button. 16 of 29

17 3. Edit Network Tracker Network Switch VLAN Timeout (if necessary) During compliance testing, the Network Tracker Network Switch VLAN timeout parameter value needed to be modified to allow the Network Tracker more time to traverse through the VLANS in the network. To modify the VLAN timeout parameter, navigate to and open the following file: C:\Program Files (x86)\conveyant Systems\Network Tracker\NetworkTracker.exe.config Set NetworkSwitchVLanTimeout to the desired value (in this case, 00:00:30.000). 17 of 29

18 4. Set Services Startup Type After installation is complete, verify the following two services have a Startup Type of Automatic (Delayed). AuraScoutService Conveyant network tracker 18 of 29

19 5. Sentinel Web Interface Access the Sentinel web interface by opening a web browser and entering the following URL: The screen below is displayed. 6. Sites Add a Site by clicking the Sites tab and then the Create link. 19 of 29

20 7. Create Site The Avaya SIL Lab entry seen in the previous step was created by entering the values shown on the screen below. Click the Submit button to add the site. 20 of 29

21 8. Call Servers After the site is added, click the Call Servers link on the Sites tab. The screen shown below is displayed. Click the Create link. 21 of 29

22 9. Add (Edit) Call Server The call server entry seen in the previous step was created by entering the values shown on the screen below. The IP Address is the Communication Manager IP address (i.e ). The User Name and Password is the Communication Manager login user name and password referenced in the first paragraph of Section 5. Set the ServerType to Avaya Aura Communication Manager v6.0 or above. Click the Submit button to add the call server. 22 of 29

23 10. Network Switches Click the Switches link on the Sites tab. The screen shown below is displayed. Click the Add Switch link. 23 of 29

24 11. Create Network Switch The 3rd entry seen in the previous step (i.e. for the network switch with an IP address of ) was created by entering the values shown on the screen below. Enter the desired Default ERL and the appropriate values for the network switch. Click the Create button to add the network switch. 24 of 29

25 8. Verification Steps The following steps may be used to verify the configuration: Step 1. Verify IP Phones Detected Allow the Network Tracker enough time to poll the network switches, as determined by the Poll switches interval shown on the screen in Section 7, Step 2 (e.g. 10 minutes). Access the Sentinel web interface as described in Section 7, Step 5. Click the Phones link on the Sites tab. Verify all the connected IP phones on the network have been detected and are shown in the screen below with the correct information. Move an IP phone to a different port or switch and verify the information is updated after the next network switch poll. 25 of 29

26 2. Use Sentinel to Change Emergency Location Ext: on Communication Manager Navigate to the Network Switch screen as shown in Section 7, Step 10. Click the Ports link for one of the switches that has IP phones connected to it. For one of the ports that has an IP phone connected, modify the ERL value and click the Save Changes button (not shown). 26 of 29

27 Using the Communication Manager System Access Terminal (SAT), enter the display station <extension> command, where <extension> is the station extension of the IP phone connected to the port with the modified ERL value above. On Page 2 (see Section 5, Step 1 for an example of the screen), verify the Emergency Location Ext: field is updated with the ERL value (e.g ) entered above. 3. Events Place a call to an emergency number. Click the Events tab and verify that the call appears on the screen with the correct information. 27 of 29

28 9. Conclusion The Conveyant Systems Sentry E9-1-1 Solution passed compliance testing. These Application Notes describe the procedures required for the Conveyant Systems Sentry E9-1-1 Solution to interoperate with Avaya Aura Application Enablement Services and Avaya Aura Communication Manager to support the reference configuration shown in Figure Additional References Product documentation for Avaya products may be found at [1] Avaya Aura TM Communication Manager Feature and Implementation, Doc # , August [2] Administering Avaya Aura TM Communication Manager, Doc # , August [3] Avaya Aura Application Enablement Services Administration and Maintenance, April Product documentation for the Conveyant Systems Sentry E9-1-1 Solution may be obtained by contacting Conveyant Systems. 28 of 29

29 Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya DevConnect Program at 29 of 29