Application Notes for Configuring the Esna Officelinx version with Avaya Communication Server 1000 Release 7.65 SP8 - Issue 1.

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Configuring the Esna Officelinx version with Avaya Communication Server 1000 Release 7.65 SP8 - Issue 1.1 Abstract These Application Notes describe the procedure for configuring Esna Officelinx 10.6 Build 1724 to interoperate with the Avaya Communication Server 1000 Release 7.65 SP8. The Officelinx voice server connects to the Avaya Communication Server 1000 through a SIP connection and provides unified communications features such as the greetings menu, user mailbox services, wake up services and call transfer functions. Information in these Application Notes was obtained through DevConnect compliance testing and additional technical discussions. Testing was conducted via the DevConnect Program at the Avaya Solution and Interoperability Test Lab. RS; Reviewed: Solution & Interoperability Test Lab Application Notes 1 of 31

2 1. Introduction These Application Notes describe the procedure for configuring Esna Officelinx 10.6 Build 1724 (Officelinx) to interoperate with Avaya Communication Server 1000 (CS1000) Release The objective of this compliance testing is to verify that Officelinx can connect via a SIP trunk to the CS1000 and provides unified communication services such as greetings, messaging and transfer functions. 2. General Test Approach and Test Results The general test approach was to place calls to the Esna Officelinx voice server, and verify that the user can: Establish calls between Officelinx and the CS1000 end points. Calling from CS1000 to OL, enter password and send new message to other user = passed. Transfer from Officelinx. Call from CS1000 endpoint to OL then transfer call to the CS1000 endpoint = passed. Leave and retrieve messages to/from client mailboxes. Login to OL from a CS1000 endpoint and leave a message. Login to OL from another CS1000 endpoint and listen to/delete the message = passed. The Esna Officelinx server was tested for serviceability and the objectives were to verify that: Officelinx can successfully re-establish a connection after the Ethernet cable has been disconnected and reconnected. Tested = passed. Officelinx can successfully recover after a reboot. Tested = passed. RS; Reviewed: Solution & Interoperability Test Lab Application Notes 2 of 31

3 2.1. Interoperability Compliance Testing The interoperability compliance test included features and services that operate using a SIP connection. The focus of the compliance testing was primarily to verify the interoperability between Officelinx and the Avaya CS1000 R7.65 with regard to the following features: CS1000 end points can access the Officelinx pilot number. Tested = passed. Officelinx can access the CS1000 end points. I can make call from OL to CS1000 = passed. Officelinx provides messaging services to the CS1000 end points. Send new message, WMI did not change = fail. (this feature is not supported per ) Officelinx can conduct transfer operations for end points. Tested = passed Test Results All the relevant tests were performed and passed Support Contact Esna Technical support for further assistance with Officelinx: techsupp@esna.com Phone (905) RS; Reviewed: Solution & Interoperability Test Lab Application Notes 3 of 31

4 3. Reference Configuration Figure 1 illustrates the environment used in these Application Notes. The configuration shows a setup of a CS1000 communicating with Officelinx via a Network Routing Server (NRS, also known as SIP Proxy Server) using a SIP trunk. The CS1000 has IP and SIP telephones connected as endpoints. For interoperability, Officelinx requires the use of the G.711MU codec, and transmission of DTMF tones using RFC2833. Figure 1: Reference Configuration 4. Equipment and Software Validated The following equipment and software/firmware were used during testing: Avaya CS1000 Equipment Software/Firmware SW Version : 7.65 SP8 Avaya Telephones: i2004 (IP) 0604DCO 1120E (SIP) Avaya NRS/SPS SW Version : 7.65 SP8 Officelinx Voice Server Windows Server 2012 R2 Standard Officelinx SW Version 10.6 Build 1724 RS; Reviewed: Solution & Interoperability Test Lab Application Notes 4 of 31

5 5. Configure Avaya CS1000 Rls 7.65 SP8 This section describes the procedure for setting up CS1000. The steps include configuring: Routes, Route Line Block Indices (RLB) and Distant Steering Codes (DSC). NRS/SPS domain, End Points and Routing Information. Node properties. Endpoints/Telephones. Note: The values used in this guide are specific to the test environment. Clients must enter values appropriate to their site (e.g. IP address, domain names, extension numbers, etc.). CS1000 configurations are performed through the Unified Communications Manager (UCM), Element Manager (EM) and Command Line Interface (CLI) Route, RLB and DSC Configuration This section explains the steps to configure a Routing entry that will access the Officelinx server from the CS1000 using RLB and DSC values. After logging into the UCM, click the EM link of the respective CS1000 (Not Shown). Go to Routes and Trunks > Routes and Trunks. Click Add route as shown in Figure 2. Figure 2: Adding Route RS; Reviewed: Solution & Interoperability Test Lab Application Notes 5 of 31

6 Figure 3 shows the configuration of the route being added. The values that are circled in red are configured by the user. The values shown were used during testing. Figure 3: Route Configuration The value for the Private network identifier (PNI) is taken from the Network Data PNI field. Figure 4: Network Data PNI and VPNI RS; Reviewed: Solution & Interoperability Test Lab Application Notes 6 of 31

7 To configure the RLB using EM, go to Dialing and Numbering Plans > Electronic Switched Network > Network Control & Services > Route List Block (RLB) as shown in Figure 5. Figure 5: Accessing RLB RS; Reviewed: Solution & Interoperability Test Lab Application Notes 7 of 31

8 Enter the value of the route list index and click to Add to continue the configuration as shown in Figure 6. During testing, a value of 40 was used. Figure 6: Adding RLB Figure 7 shows the Route Number 1 being selected for the RLB created. Route 1 was selected since it was the route number assigned while adding a route (see Figure 3). Figure 7: Selecting the configured Route to RLB RS; Reviewed: Solution & Interoperability Test Lab Application Notes 8 of 31

9 To configure the DSC using EM, go to Dialing and Numbering Plans > Electronic Switched Network > Coordinated Dialing Plan (CDP) > Distant Steering Code (DSC) (see Figure 5). In the Distant Steering Code List page, select Add from the drop down menu (Figure 8). Figure 8: Adding a new DSC Enter the value of the DSC and click to Add (Not Shown). As shown in Figure 9, a DSC value of 337 was added during testing. The value 337 was configured since the pilot DN of the Officelinx system was Flexible Length number of digits identifies the length of the directory number (DN). During testing, a value of 4 was used. Route List to be accessed for trunk steering code was set to 40 from the drop down list. This value is selected based upon the RLB created in Figure 6. Figure 9: DSC configuration For additional information on Route, RLB and DSC configuration, refer to Section 9[1]. RS; Reviewed: Solution & Interoperability Test Lab Application Notes 9 of 31

10 5.2. NRS/SPS domain, End Points, Routing Information Configuration This section explains the configuration of the NRS/SPS required to enable communication between the CS1000 and Officelinx. The NRS/SPS can be accessed from the UCM and selecting the appropriate NRS/SPS (Not Shown). Note: When the NRS/SPS is being configured, the database must be in Standby mode. To configure a service domain in the NRS/SPS, go to Numbering Plans > Domains > Service Domains. Click the Add button to start adding a domain (see Figure 10). Figure 10: Accessing NRS/SPS to add Service Domain Populate the Domain name field with a name shown in Figure 11. During testing, the Domain name used was aam1.com. Figure 11: Adding Domain Name RS; Reviewed: Solution & Interoperability Test Lab Application Notes 10 of 31

11 Similar to the steps shown in Figure 10 and Figure 11, L1 and L0 Domains must be added. In this example, UDP2 and CDP2 were added to L1 and L0 respectively (see Figure 12). Figure 12: Other Domains RS; Reviewed: Solution & Interoperability Test Lab Application Notes 11 of 31

12 Two endpoints must be configured, one for the CS1000 and another for Officelinx. To configure an endpoint from the NRS/SPS, go to Numbering Plans > Endpoints. Figure 133 and Figure 14 show the endpoint being configured for the CS1000 system. During testing, cp-sw5 was used for End point name, SIP support is Static SIP endpoint. The Static endpoint address is the IP address of the CS1K 1000, and the SIP TCP and UDP transport enabled boxes are checked. Figure 13: CS1000 Endpoint configuration Figure 14: CS1000 Endpoint configuration continued RS; Reviewed: Solution & Interoperability Test Lab Application Notes 12 of 31

13 Figure 15 and Figure 16 show the endpoint configuration of Officelinx. The End point name is esna, and SIP support is Static SIP endpoint. The Static endpoint address is the IP address of the Officelinx server. SIP TCP and UDP transport enabled are checked. Figure 15: Officelinx Endpoint configuration Figure 16: Officelinx Endpoint configuration continued RS; Reviewed: Solution & Interoperability Test Lab Application Notes 13 of 31

14 Two routes need to be configured for the endpoints. The routes are configured for the CS1000 and the Officelinx server. To configure a route from the NRS/SPS, go to Numbering Plans > Routes. For the Limit results to Domain fields, set the service, L1 and L0 domains to aam1.com, udp2 and cdp2 respectively. Set the endpoint name to cp-sw5. Click Add to attach a route to the CS1000 endpoint as shown in Figure 17. Figure 17: Adding Routing Entry for CS1000 Choose Private level 0 regional (CDP steering code) for DN type. For DN prefix, 5 was configured since the DN range used for the test CS1000 was 5xxx. Route cost was set to 1 during testing. Refer to Figure 18 for the configuration screen. Figure 18: Routing Entry configuration for CS1000 RS; Reviewed: Solution & Interoperability Test Lab Application Notes 14 of 31

15 Figure 19 and Figure 20 show the routes being added to the Officelinx endpoint, where the Endpoint Name is esna. The DN prefix value is 3 since the Officelinx DN range used in the test was 3xxx. Figure 19: Adding Routing Entry for Officelinx Figure 20: Routing Entry configuration for Officelinx After completion of the NRS/SPS configuration, go to System > Database and select Cut Over and then choose Commit (Not shown). Note: The database can now be put back into Active mode. For additional information on NRS/SPS configuration, refer to Section 9[1]. RS; Reviewed: Solution & Interoperability Test Lab Application Notes 15 of 31

16 5.3. Node IP (SIP Gateway) Configuration This section describes the configuration of the SIP Gateway application running on the CS1000 signaling server. In the test environment, Node ID 1010 was used since it has the SIP Gateway application enabled. For additional information on Nodes configuration, refer to Section 9[1]. To configure the SIP Gateway from EM, go to System > IP Network > Nodes: Servers, Media Cards and click Node ID 1010 as shown in Figure 21. Figure 21: Accessing IP Telephony Nodes Click Gateway (SIPGw & H323Gw) as shown in Figure 22. Figure 22: Accessing SIP and H323 Gateway RS; Reviewed: Solution & Interoperability Test Lab Application Notes 16 of 31

17 On the General tab, enter the SIP domain name as bvwdev.com (from Figure 11), set the Local SIP port to 5060, Gateway endpoint name to sw-cp5 (from Figure 13) and Application node ID to 1010 (from Figure 21) as shown in Figure 23. Figure 23: Configuration of General Fields RS; Reviewed: Solution & Interoperability Test Lab Application Notes 17 of 31

18 Figure 24 shows the Primary TLAN IP address, which is the IP address of the NRS/SPS server. Support registration and Primary CDS proxy boxes are enabled. Disable TLS security. Figure 24: Configuring the NRS/SPS IP Address RS; Reviewed: Solution & Interoperability Test Lab Application Notes 18 of 31

19 Figure 25 shows the SIP URI Map configuration where the CDP field is configured as cdp2.udp2. Figure 25: Configuring SIP URI Map Fields Figure 26 shows the Microsoft Unified Messaging configuration where the MWI application DN is configured as This is the pilot DN being used to reach the Officelinx voice server during testing. CDP is the selected MWI dialing plan. Figure 26: Configuring Microsoft Unified Messaging Fields RS; Reviewed: Solution & Interoperability Test Lab Application Notes 19 of 31

20 Figure 27 shows the Subscriber Access Service number and Auto Attendant Service number configuration. The values 3370 and 3371 were used during testing. Figure 27: Configuring Subscriber Access Service and Auto Attendant Service Fields Note: The steps shown in Figure 26 and Figure 27 are important. If these fields are not configured, Officelinx receives the SIP Message Header with Content-Type: multipart/mixed which Officelinx does not currently support. This will cause the program to not accept calls with multipart/mixed message bodies. Officelinx requires Content-Type: application/sdp Endpoint/Telephone Configuration This section explains the provisioning of an endpoint/telephone. The endpoint/telephone can be configured using the CLI of the CS1000 from overlay LD 11/20. Refer to Section 9[1] for further information regarding adding and configuring endpoints/telephones. In Figure 28, values that are shown in red are configured by the user. The FDN and HUNT value of 3370 was used during testing as the pilot DN of the Officelinx system. RS; Reviewed: Solution & Interoperability Test Lab Application Notes 20 of 31

21 Figure 28: Configuring an Endpoint/ Telephone RS; Reviewed: Solution & Interoperability Test Lab Application Notes 21 of 31

22 6. Configuring the Esna Officelinx server The Officelinx installation is covered in referenced product documentation. During the install, the PBX template for Nortel CS1000 can be selected providing a pre-defined configuration. This section only describes the interface configuration as a reference for verification so that Officelinx can communicate with the CS1000. For further details on Officelinx configuration not covered here, refer to Section 9[2]. The integration of Officelinx with CS1000 is done through the Officelinx SIP Configuration Tool. To access the SIP Configuration Tool on the Officelinx server, go to Start > All Programs > Officelinx > SIP Configurator (Not shown). Figure 29 shows the SIP Configuration tool where a new PBX is added. During testing, Generic SIP Trunk was added as the PBX. Figure 29: Adding new PBX RS; Reviewed: Solution & Interoperability Test Lab Application Notes 22 of 31

23 Figure 30 shows the General tab of the SIP Configuration Tool. Fields circled in red are populated by user. For IP Address and for Realm enter the domain name. In the From Field, enter REMOTE. Figure 30: General Configuration RS; Reviewed: Solution & Interoperability Test Lab Application Notes 23 of 31

24 Figure 31 shows the Advanced tab of the SIP Configuration Tool. Enable the Use TCP checkbox. Figure 31: Advanced Configuration RS; Reviewed: Solution & Interoperability Test Lab Application Notes 24 of 31

25 Figure 32 shows the pilot DN of the Officelinx voice server configured in the Channels tab of the SIP Configuration Tool. During testing, were configured as the Officelinx pilot DN. Figure 32: Channels Configuration Figure 33 shows the Force MWI box enabled under the MWI tab. Figure 33: MWI Configuration RS; Reviewed: Solution & Interoperability Test Lab Application Notes 25 of 31

26 The integration mode number for Officelinx to communicate with CS1000 is 4. This Integration Mode field can be configured from the ANI tab of the SIP Configuration Tool (see Figure 34). Figure 34: ANI Configuration RS; Reviewed: Solution & Interoperability Test Lab Application Notes 26 of 31

27 Figure 35 shows the General Settings tab where the Outbound Proxy IP address is set to the IP address of the NRS/SPS. Figure 35: Outbound Proxy IP configuration RS; Reviewed: Solution & Interoperability Test Lab Application Notes 27 of 31

28 Officelinx must be configured for SIP to send the Message Waiting Light indication to the PBX. To configure this feature, access the Office Linx Admin screen through Start > All Programs > Officelinx > Office Linx Admin (Not Shown). Access the Properties of the PBX as shown in Figure 36. Figure 36: Accessing PBX Properties Screen RS; Reviewed: Solution & Interoperability Test Lab Application Notes 28 of 31

29 Select the SIP radio button from the Message Light tab as shown in Figure 37. Then restart the UC SIP service and UC Voice Server service through Windows. Figure 37: Message Light Configuration RS; Reviewed: Solution & Interoperability Test Lab Application Notes 29 of 31

30 7. Verification Steps The following steps may be used to verify the integration: From the CS1000 end point, call the Officelinx pilot DN 3370 and verify that a general greeting is played. Works as expected. From the Officelinx server, verify a CS1000 endpoint receives a wakeup call. Transfer call from OL to CS1000 endpoint = works as expected. Verify that a call from a CS1000 endpoint to another CS1000 endpoint can be transferred via Officelinx. Call ring and no answer, I can send new message to an OL mailbox, Message Light status on OL turns on. After reading the new message, the Message Light status on OL is turned off. Verify the correct Officelinx greeting messages are played depending on the status of the CS1000 endpoints. Correct OL greeting messages are played depending on the status of the CS1000 endpoints when I call to CS1000 endpoint. [Busy or available] = works as expected. Verify a message can be left for a CS1000 endpoint and retrieved via Officelinx. Read/delete message on CS1000 endpoint, I see the number of messages updated on OL = works as expected. 8. Conclusion All of the relevant test cases have passed the objectives outlined in Section 2. The Esna Officelinx 10.6 software is considered compliant with Avaya CS1000 Rls Additional References [1] Product documentation for Avaya products may be found at: [2] Product documentation for Esna Officelinx may be found at: RS; Reviewed: Solution & Interoperability Test Lab Application Notes 30 of 31

31 2018 Avaya Inc. All Rights Reserved. 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 RS; Reviewed: Solution & Interoperability Test Lab Application Notes 31 of 31