Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Configuring Conveyant Systems Sentry E911 Emergency Location Management Solution with Avaya Aura Session Manager and Avaya Aura Communication Manager - Issue 1.0 Abstract These Application Notes describe the procedures for configuring the Conveyant Systems Sentry E911 Emergency Location Management Solution to interoperate with Avaya Aura Session Manager and Avaya Aura Communication Manager. The Conveyant Systems Sentry E911 Emergency Location Management Solution is a software based solution that is comprised of a scout service. The scout service (i.e. Sentry Scout for Avaya Aura Session Manager) registers to and receives a notification (ec-alert event) from Avaya Aura Session Manager) when an emergency number has been dialed. Readers should pay attention to Section 2, in particular the scope of testing as outlined in Section 2.1 as well as the observations noted in Section 2.2, to ensure that their own use cases are adequately covered by this scope and results. 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 28

2 1. Introduction These Application Notes describe the procedures for configuring the Conveyant Systems Sentry E911 Emergency Location Management Solution to interoperate with Avaya Aura Session Manager (Session Manager) and Avaya Aura Communication Manager (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 E911 Emergency Location Management Solution (Sentry E911) 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 Sentry E911 is comprised of a scout service. Sentry Scout for Avaya Aura Session Manager on the Sentry server registers as a Listener on the SIP Domain, receives an OPTIONS command from Session Manager, and sends an OK response with allowed verbs: OPTIONS, PUBLISH. This enables Sentry E911 to then receive Publish and Registration messages which contain the SIP phones registrations and the ec-alerts which contain the 911 call information. Sentry E911 will also update the Emergency Location Identification Number (ELIN) field back on Session Manager for discovered SIP phones. Session Manager s Adjunct Emergency Location Server (AELS) interface is being used by Sentry E911to receive ec-alerts with extension, IP address and MAC address for SIP phones dialing General Test Approach and Test Results This section describes the general test approach used to verify the interoperability of the Sentry E911 with an Avaya infrastructure (consisting of Avaya Aura Session Manager and Avaya Aura Communication Manager). This section also covers the test results. DevConnect Compliance Testing is conducted jointly by Avaya and DevConnect members. The jointly-defined test plan focuses on exercising APIs and/or standards-based interfaces pertinent to the interoperability of the tested products and their functionalities. DevConnect Compliance Testing is not intended to substitute full product performance or feature testing performed by DevConnect members, nor is it to be construed as an endorsement by Avaya of the suitability or completeness of a DevConnect member s solution. 2 of 28

3 2.1. Interoperability Compliance Testing The general test approach was to verify the integration of the Sentry E911 with Session Manager and Communication Manager. Various emergency calls were placed from Avaya SIP endpoints to an emergency number to verify the events were properly logged by the Sentry E911 in a timely manner. Sentry E911 was also verified for discovering all the SIP endpoints that were registered to the Session Manager and if it was able to update the ELIN information for these SIP endpoints Test Results The Conveyant Systems Sentry E911 Emergency Location Management Solution successfully passed compliance testing. Note: The Sentry Scout for Avaya Aura Session Manager used in this solution is only applicable in an Avaya Aura Session Manager and Avaya Aura Communication Manager environment with SIP endpoints Support For technical support on the Conveyant Systems Sentry E911 Emergency Location Management solution, contact Conveyant Systems at: Web: Phone: (949) support@conveyant.com 3 of 28

4 3. Reference Configuration Figure 1 below illustrates the reference configuration used during compliance testing. The Conveyant Systems Sentry Sentinel Server was installed on a Windows Server 2008 R2 Standard SP1 operating system running on a virtualized environment. Figure 1: Sentry E911 Emergency Location Management Solution with Session Manager and Communication Manager 4 of 28

5 4. Equipment and Software Validated The following equipment and version were used in the reference configuration described above: Equipment/Software Release/Version Avaya Aura Communication Manager FP1SP1 running on virtualized environment Avaya Aura Session Manager running on virtualized environment Avaya Aura System Manager running on (SP2) virtualized environment Avaya Aura Media Server running on virtualized environment Avaya G450 Media Gateway FW /1 Avaya 96x1 Series IP Telephones: 9641 (SIP) (SIP) Avaya Communicator for Windows Conveyant Systems: Sentry Sentinel Server running Sentry E Emergency Location Management Solution installed on Win 2008R2 Standard Server SP1 running on virtualized environment Sentry Beacon installed on Win 2008R Standard Server SP1 running on virtualized environment 5. Configure Avaya Aura Communication Manager This application notes assumes that Communication Manager has been configured correctly to communicate with Session Manager. For details on configuring the Communication Manager with Session Manager, refer to Section of 28

6 6. Configure Avaya Aura Session Manager This section provides the procedures for configuring Session Manager. The assumption has been made that the basic configuration for connectivity between Communication Manager and Session Manager has already been completed as mentioned in Section 5. The procedures include the following areas: Launch System Manager Administer Domain Administer locations Administer SIP entity Administer dial patterns Link the ELIN entity Import Conveyant TLS Certificate 6.1. Launch System Manager Access the System Manager web interface by using the URL in an Internet browser window, where ip-address is the IP address of System Manager. Log in using the appropriate credentials. 6 of 28

7 6.2. Administer Domain In the subsequent screen (not shown), select Elements Routing to display the Introduction to Network Routing Policy screen below. Select Routing Domains from the left pane, and click New in the subsequent screen (not shown) to add a new domain The Domain Management screen is displayed. In the Name field enter the domain name, select sip from the Type drop down menu and provide any optional Notes. 7 of 28

8 6.3. Administer Locations Select Routing Locations from the left pane, and click New in the subsequent screen (not shown) to add a new location for Trio Enterprise. The Location Details screen is displayed. In the General sub-section, enter a descriptive Name and optional Notes. Retain the default values in the remaining fields. Scroll down to the Location Pattern sub-section, click Add and enter the IP address of all devices involved in the compliance testing in IP Address Pattern, as shown below. Retain the default values in the remaining fields. 8 of 28

9 6.4. Administer SIP Entity Add a new SIP entity for the Conveyant Systems Sentinel Server. Select Routing SIP Entities from the left pane, and click New in the subsequent screen (not shown) to add a new SIP entity for Trio Enterprise. The SIP Entity Details screen is displayed. Enter the following values for the specified fields, and retain the default values for the remaining fields. Name: A descriptive name. FQDN or IP Address: The IP address of the Sentinel Server. Type: ELIN server Notes: Any desired notes. Location: Select the location name from Section 6.2. Time Zone: Select the applicable time zone. 9 of 28

10 Scroll down to the Entity Links sub-section, and click Add to add an entity link. Enter the following values for the specified fields, and retain the default values for the remaining fields. Name: A descriptive name. SIP Entity 1: The Session Manager entity name, in this case DevvmSM. Protocol: TLS Port: 5063 SIP Entity 2: The Sentinel Server entity name from this section. Port: 5063 Connection Policy: trusted Note that only TLS protocol was tested. Click on Commit button to complete the configuration. 10 of 28

11 6.5. Administer Dial Patterns Add a new dial pattern for a simulated PSAP. An emergency call initiated by a SIP phone will route the call through this dial pattern to a simulated PSAP. Select Routing Dial Patterns from the left pane, and click New in the subsequent screen (not shown) to add a new dial pattern to reach the simulated PSAP. The Dial Pattern Details screen is displayed. In the General sub-section, enter the following values for the specified fields, and retain the default values for the remaining fields. Pattern: A dial pattern to match, in this case 911. Min: The minimum number of digits to match. Max: The maximum number of digits to match. Emergency Call: Check the box. Emergency Priority: Retain the default value of 1. Emergency Type: Enter Police. SIP Domain: The signaling group domain name from Section 6.1. Notes: Any descriptive notes. In the Originating Locations and Routing Policies sub-section, click Add and create an entry for reaching the simulated PSAP. In the compliance testing, the entry allowed for call originations from all Communication Manager Endpoints in locations Belleville and terminated at a simulated PSAP. 11 of 28

12 6.6. Link the ELIN Entity This section explains the linking of the ELIN entity as the ELIN server for the Session Manager instance. From the System Manager home screen (not shown), select Elements Session Manager to display the Session Manager Dasboard screen shown below. Select Session Manager Session Manager Administration from the left pane, and under the Global Settings tab for the ELIN SIP Entity field, select the Conveyant SIP entity configured in Section 6.4. Retain default values for all other fields and click on the Commit button to save the configuration. 12 of 28

13 6.7. Import Conveyant TLS Certificate This section explains the importing of the TLS certificate for ELIN communications. From the System Manager home screen (not shown), select Services Inventory to display the main Inventory screen shown below. Navigate to Manage Elements from the left pane and select the Session Manager Element. Click on the Configure Trusted Certificates from the More Actions drop down menu and click on the Add button (not shown). 13 of 28

14 In the Add Trusted Certificate screen shown below, select the Import as PEM certificate radio button and paste the contents of the PEM certificate. The contents of the certificate can typically be found in the file path C:\Program Files\Conveyant Systems\Sentry on the Sentinel server. Open the file ConveyantELIN.pem in a text editor to copy and paste in the screen shown below. Click on Commit button to complete the import. 14 of 28

15 After importing the PEM certificate, install the Root certificate by importing the file directly. Select Import from File radio button, and browse to the ConveyantRootCA.cer file which is typically found in the file path C:\Program Files\Conveyant Systems\Sentry on the Sentinel server as shown in the screen below. Click the Retrieve Certificate button and then the Commit button to import the Root certificate. A restart of the System Manager might be required for all of the above changes to take effect. The Trusted Certificates screen is shown below after the certificates have been installed. 15 of 28

16 7. Configure Conveyant Systems Sentry E911 Emergency Location Management Solution This section provides the procedures for configuring the Conveyant Systems Sentry E911 Emergency Location Management Solution. Run the SentrySetup.msi file provided by Conveyant Systems and follow the steps to complete the installation of the Sentinel Server Configure Call Servers After the installation is complete, start the web interface by typing in the URL of the Sentinel server. During compliance testing the web interface was launched on the same system as the server was installed on. The screen bellows shows the home page of the Sentinel web interface. Navigate to Configure Call Servers as shown below to add a Call Server. 16 of 28

17 From the Call Servers screen as shown below, select Avaya SIP Session Manager from the Select a call server type drop down box and click on the Create button. 17 of 28

18 In the Create Avaya SIP Session Manager screen as shown below, configure the following fields. Description: A descriptive name. IP Address: The IP address of Session Manager. Username: Username of Session Manager. Password: Password of Session Manager. SIP Domain: The domain configured in Session Manager as in Section 6.2. SIP ELIN Listen Port: The port configured in Session Manager as in Section 6.4. Retain default values for all other fields and click on the Submit button. 18 of 28

19 The configured Call Servers screen is shown below Configure IP Range Locations Navigate to Configure IP Range Locations as shown in the screen below and click on the Create button to configure an IP Range. 19 of 28

20 From the Create screen as shown below, configure the following values. From IP Address: Starting IP Address range of SIP endpoints. To IP Address: Ending IP Address range of SIP endpoints. ERL/ELE: An associated ERL/ELE value for call back to the SIP endpoints in this range. Click on the Submit button to complete the configuration. Screen below shows an example of the IP Range Locations created during compliance testing. 20 of 28

21 7.3. Configure Locations To configure a Location for an ERL/ELE, navigate to Configure Locations as shown in the screen below and click on the Create button. In the Create Location screen shown below, configure the required fields for a particular ERL/ELE. During compliance testing only the Address Description, Building and Floor fields were configured for the ERL/ELE of 28

22 Screen below shows an example of the Locations created during compliance testing. 22 of 28

23 8. Verification Steps The following steps may be used to verify the configuration: On Avaya Aura System Manager, navigate to Elements Session Manager System Status SIP Entity Monitoring. Value in the Conn. Status column, should be UP. This verifies that the SIP connectivity between Avaya Aura Session Manager and Sentinel Server is established successfully. 23 of 28

24 From the Sentry E911 application s web interface verify if the IP phones have been discovered by navigating to View IP Phones as shown in the screen below. Example below shows the SIP endpoints registered to the Session Manager during compliance testing. On Avaya Aura System Manager, navigate to Elements Session Manager System Status Users Registrations. Select a registered SIP endpoint and verify that the ELIN Number and ELIN Last Updated fields are populated. This verifies that any change made to ELIN Number on the Sentinel Server is updated on the Session Manager. 24 of 28

25 Verify that 911 calls can be placed from different SIP endpoints and verify it these alerts are seen in the Sentry E911 application by navigating to View Emergency Calls as shown in the screen below. 25 of 28

26 Alerts can also be verified by the Sentry Beacon tool as shown in the screen below. 26 of 28

27 9. Conclusion These Application Notes describe the steps required to configure Conveyant Systems Sentry E911 Emergency Location Management Solution to interoperate with Avaya Aura Session Manager and Avaya Aura Communication Manager. All feature and serviceability tests were completed successfully with observation/s if any noted in Section Error! Reference source not found Additional References These documents form part of the Avaya official technical reference documentation suite. Further information may be had from or from the local Avaya representative. 1. Implementing Avaya Aura Session Manager Document ID Administering Avaya Aura Session Manager, Doc ID Deploying Avaya Aura System Manager, Release Administering Avaya Aura System Manager for Release 7.0, Release Quick Start Guide to Using the Avaya Aura Media Server with Avaya Aura Communication Manager. 6. Deploying and Updating Avaya Aura Media Server Appliance, Release Administering Avaya Aura Communication Manager, Release 7.0, Avaya Aura Communication Manager Feature Description and Implementation, Release 7.0, Product documentation for the Conveyant Systems Sentry E911 Emergency Location Management Solution may be obtained by contacting Conveyant Systems. 27 of 28

28 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 28 of 28