Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Sample Configuration for SIP Connectivity between Avaya Communication Manager and Avaya Distributed Office using Avaya SIP Enablement Services Issue 1.1 Abstract These Application Notes illustrate a sample configuration for an Avaya SIP (Session Initiation Protocol) based private infrastructure that supports real-time communications between Avaya Distributed Office at a branch location and Avaya Communication Manager at a headquarters or main location. The Avaya solution consists of Avaya SIP Enablement Service (SES) Edge 4.0 that performs core routing and provides SIP trunking support for the sample configuration. The SIP private network, containing Avaya SES Edge and Avaya Distributed Office, is configured using the web-based interface of Avaya Distributed Office Central Manager (DOCM), a component of Avaya Integrated Management for Avaya Distributed Office. 1 of 48

2 1. Introduction Avaya SIP Enablement Service (SES) Edge 4.0 enables enterprise real-time inter-location communications by performing core routing combined with standard functions of an Edge proxy server with SIP trunking support. Avaya SES Edge supports a scalable SIP-based private network of as many as 1000 Avaya Distributed Office platforms. Avaya Distributed Office is a small office and branch solution that encompasses Avaya Communication Manager, Avaya SES (Home), and Avaya Application Enablement Services as a single bundled offer on a single platform. The Avaya SES Edge provides SIP signaling between Avaya Distributed Office branches, as well as between these branches and a main or headquarters location of an enterprise. Typically, as in the sample configuration illustrated in Figure 1, the Avaya SES Edge server is located in a headquarters location along with an Avaya SES Home server and an Avaya S87xx server running Avaya Communication Manager 4.0 (or later release). Inter-location call routing between Avaya Distributed Office (Branch Store 2) and Avaya SES Home (Retail Store Headquarters) is achieved by using unique numeric prefixes for each location and the user extension (prefix + extension). The Avaya SES Home server manages SIP requests for the assigned domain and forwards any requests pertaining to other locations (or domains) based on assigned prefix to the Avaya SES Edge server. The Avaya SES Edge server manages SIP requests from all locations/domains, forwarding requests received from Avaya SES Home servers and Avaya Distributed Office. In addition to support for enterprise real-time inter-location communications, this architecture extends SIP enabled applications located centrally, such as Avaya Voice Portal at the Retail Store Headquarters location (Figure 1), to Avaya Distributed Office branches such as the Branch Store location in Figure 1. The configuration of Avaya Voice Portal as an Avaya SES SIP adjunct is not covered in these Application notes. However, the SIP INVITE message flow (Section 1.3) and verification (Section 6) sections do include Avaya Voice Portal. For information on configuring Avaya Voice Portal, pleaser refer to [1] in Section Avaya Distributed Office Central Manager Avaya Distributed Office Central Manager (DOCM) is a component of Avaya Integrated Management that allows for centralized administration in an Avaya Distributed Office network. Avaya DOCM is required for configuring Avaya SES Edge and Avaya Distributed Office for SIP private networking, including the assignment of the SIP Domain, numeric prefixes for each location, Avaya Distributed Office branch IP address, and the administration of Instant Messaging (IM) and Presence alphanumeric handles. 2 of 48

3 1.2. Reference Network Configuration Figure 1 illustrates the Retail Store Headquarters and Branch Store configuration used to verify these Application Notes. The Retail Store Headquarters location consists of the following equipment: Avaya Communication Manager running on Avaya S8710 Server pair Avaya G650 Media Gateway (various Telephony Network (TN) boards) Avaya SES servers (separate Home and Edge servers) Avaya DOCM server Avaya 4625SW H.323 Telephone Avaya one-x Deskphone Edition for 9630 H.323 Telephone Avaya Voice Portal system LAN switch and a WAN access router The Branch Store location consists of the following equipment: Avaya Distributed Office on an i40 Platform Avaya C363T-PWR Converged Stackable Switch Avaya one-x Deskphone Edition for 9630 SIP Telephone Avaya 4621SW H.323 Telephone Avaya IP Softphone Avaya Analog Telephone WAN access router There is a SIP trunk between Avaya Communication Manager and Avaya SES Home and between Avaya Voice Portal and Avaya SES home at the Retail Store Headquarters location (not shown). Both locations have access to a simulated PSTN and MPLS WAN. Although the sample configuration consists of a single Avaya Distributed Office branch, the Avaya solution detailed in this document applies to an enterprise network of multiple Avaya Distributed Office branches. Note: These Application Notes assume that the sample configuration depicted in Figure 1 is already in place with the exception of the Avaya SES servers, the Avaya DOCM server, and the implementation of the SIP private network connecting the Retail Store Headquarters to the Avaya Distributed Office at the Branch Store. Please consult the appropriate documentation in Section 8 of these Application Notes for more information on installing and configuring Avaya components not covered in these Application Notes. 3 of 48

4 Figure 1: Retail Store Headquarters and Branch Configuration 4 of 48

5 1.3. SIP INVITE Message Flow To better understand how SIP INVITE message are routed between the Retail Store Headquarters and Branch Store locations during call setup using SIP private networking, several SIP INVITE message flow scenarios are described in this section Retail Store Headquarters to Branch Store Call A call is placed from the Avaya one-x Deskphone Edition for 9630 H.323 Telephone (Extension ) at Retail Store Headquarters to the Avaya one-x Deskphone Edition for 9630 SIP Telephone (Extension 556) at the Branch Store location. The SIP INVITE message flow scenario is illustrated in Figure Retail Store Headquarters user at extension dials the Branch Store prefix 299 and the extension 556. Digits are sent to Avaya Communication Manager to process the call setup [H.323 Signaling]. 2. The call request is handled by Avaya Communication Manager where origination treatment such as class of service restrictions and automatic route selection is performed. Avaya Communication Manager creates a SIP INVITE message with a Uniform Resource Identifier (URI) of sip:299556@retail.com and routes it over the SIP trunk to the Avaya SES Home server. (A URI is a valid SIP user address beginning with sip: or sips: and followed by an extension). 3. The Avaya SES Home does not recognize the URI, so the call is routed to the Avaya SES Edge server. 4. The Avaya SES Edge finds a match for the prefix and proper digit length then routes the SIP INVITE message to Avaya Distributed Office at the Branch Store location via the MPLS WAN for termination processing. 5. After matching on the prefix and proper length, Avaya Distributed Office strips the 299 prefix off of the user portion of the URI and routes the SIP INVITE message to the 9630 SIP telephone with extension 556. Figure 2: Retail Store Headquarters to Branch Store Call Setup 5 of 48

6 Branch Store to Retail Store Headquarters Call A call is placed from the Avaya one-x Deskphone Edition for 9630 SIP Telephone (Extension 556) at the Branch Store location, to the Avaya one-x Deskphone Edition for 9630 H.323 Telephone (Extension ) at Retail Store Headquarters. The SIP INVITE message flow scenario is illustrated in Figure The Branch Store User at extension 556 first dials the Automatic Alternate Routing (AAR) Access code 8, and then the Retail Store Headquarters prefix 199 followed by the extension The Avaya one-x Deskphone Edition for 9630 SIP Telephone creates a SIP INVITE message with an URI of sip: @retail.com and forwards it to Avaya Distributed Office to process the call setup. 2. The call request is handled by Avaya Distributed Office where origination treatment such as class of service restrictions and AAR route selection is performed. Avaya Distributed Office strips the AAR code 8 and routes the SIP INVITE message with an URI of sip: @retail.com to the Avaya SES Edge at the Retail Store Headquarters location via the MPLS WAN. 3. The Avaya SES Edge finds a match for the prefix and proper length and routes the SIP INVITE message to the Avaya SES Home for termination processing. 4. The Avaya SES Home finds a match in the administered address map and routes the SIP INVITE message to Avaya Communication Manager over the SIP trunk. 5. After matching on the prefix and proper length, Avaya Communication Manager strips off the prefix 199 according to its Incoming Call Handling Treatment for the SIP trunk. Avaya Communication Manager then routes the call to extension using the administered dial plan [H.323 Signaling]. Figure 3: Branch Store to Retail Store Headquarters Call Setup 6 of 48

7 Avaya Voice Portal call transfer to Branch Store location An incoming call via the PSTN is placed by the customer to the Avaya Voice Portal application extension The customer then requests to speak with extension 557 at the Branch Store location and call is transferred from Avaya Voice Portal to the Avaya 4621SW H.323 Telephone (Extension 557) at the Branch Store location. The SIP INVITE message flow scenario is illustrated in Figure The customer dials and the call is routed via the PSTN to the Retail Store Headquarters location and digits are sent to Avaya Communication Manager [H.323 Signaling]. 2. The incoming call is handled by Avaya Communication Manager where origination treatment such as class of service restrictions and automatic route selection is performed. Avaya Communication Manager creates a SIP INVITE message with an URI of sip: @retail.com and routes it over the SIP trunk to the Avaya SES Home server. 3. The Avaya SES Home server recognizes the URI and routes it to Avaya Voice Portal over its SIP trunk. 4. The customer requests to speak with extension 557 at the Branch Store location. Avaya Voice Portal creates a SIP INVITE message with an URI of sip:222557@retail.com and routes it over the SIP trunk to the Avaya SES Home server. 5. The Avaya SES Home does not recognize the URI, so it routes it to the Avaya SES Edge server. 6. The Avaya SES Edge finds a match for the prefix and proper length and routes the SIP INVITE message to Avaya Distributed Office at the Branch Store location via the MPLS WAN for termination processing. 7. After matching on the prefix and proper length, Avaya Distributed Office strips off the prefix 299 and routes the call to extension 557 using the administered dial plan [H.323 Signaling]. Figure 4: Avaya Voice Portal to Branch Store Call Setup 7 of 48

8 Branch Store to Avaya Voice Portal Call A call is placed from the Analog Phone (Extension 551) at the Branch Store location to Avaya Voice Portal application extension at Retail Store Headquarters. The SIP INVITE message flow scenario is illustrated in Figure The Branch Store User at extension 551 first dials the Automatic Alternate Routing (AAR) Access code 8, and then the Retail Store Headquarters prefix 199 followed by the extension Digits are sent to Avaya Distributed Office to process the call setup [H.323 Signaling]. 2. The call request is handled by Avaya Distributed Office where origination treatment such as class of service restrictions and ARR route selection is performed. Avaya Distributed Office strips the AAR code 8 and creates the SIP INVITE message with an URI of sip: @retail.com to the Avaya SES Edge at the Retail Store Headquarters location via the MPLS WAN. 3. The Avaya SES Edge finds a match for the prefix and proper length and routes the SIP INVITE message to the Avaya SES Home for termination processing. 4. The Avaya SES Home finds a match in the administered address map and routes the SIP INVITE message to Avaya Communication Manager over the SIP trunk. 5. After matching on the prefix and proper length, Avaya Communication Manager strips off the prefix 199 according to its Incoming Call Handling Treatment for the SIP trunk. Avaya Communication Manager then routes the call over the SIP trunk to the Avaya SES Home server, based the automatic route selection, with a URI of sip: @retail.com for the SIP INVITE message. 6. The Avaya SES Home server recognizes the URI and routes it to Avaya Voice Portal over its SIP trunk. Figure 5: Branch Store to Avaya Voice Portal Call Setup 8 of 48

9 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Software Avaya S8710 Servers Avaya Communication Manager (R014x ) Avaya G650 Media gateway IPSI (TN2312BP) C-LAN (TN799DP) MEDPRO (TN2602AP) Avaya SIP Enablement Services Home server Edge server Avaya Distributed Office Central Manager Dell PowerEdge 850 Server Avaya Voice Portal Voice Portal Management System Media Processing Platform HW 10 FW 040 HW 017 FW 024 HW 02 FW Microsoft Windows Server 2003 SP Avaya one-x Deskphone Edition for 9630 H.323 Telephone 1.5 (ha96xxua1_5.bin) Avaya 4625SW H.323 Telephone 2.8 (a25d01a2_8.bin) Table 1 Retail Store Headquarters Equipment Software Avaya Distributed Office i40-analog Platform AM110 Application Module 1.1.0_33.02-SP Avaya C363T-PWR Converged Stackable Switch Avaya one-x Deskphone Edition for 9630 SIP Telephone (5) (SIP96xx_1_0_13_1.bin) Avaya 4621SW H.323 Telephone 2.8 (a25d01a2_8.bin) (H.323) Avaya IP Softphone Dell Precision 380 Microsoft Windows XP Professional SP2 Avaya 6211 Analog Telephone n/a Table 1 Branch Store 9 of 48

10 3. Configure Avaya SIP Enablement Services It is a requirement for the Avaya SES Edge to be a fresh installation for an Avaya Distributed Office R1.1 branch network. If an existing Avaya SES hardware configuration has a combined Avaya SES Home/Edge server, then it must be re-mastered as a separate Avaya SES Edge and Avaya SES Home servers, with the Avaya SES Edge as the Master Administrator web interface. Otherwise, the Avaya SES Home and Avaya SES Edge servers are both installed as new hardware components with the Avaya SES Edge as the Master Administrator web interface. For re-mastering an existing Avaya SES Home/Edge server, please refer to the procedure in Chapter 28, Remastering a combined home/edge to an edge with several homes, in reference [2] in Section 8. This section details the administration that must be performed on the Avaya SES Edge, using the Master Administration web interface, for completing the items under the Setup Menu as a reference. It is assumed that the following has been performed on both the Avaya SES Home and Edge servers: BIOS setting settings and version have been verified The installation of Avaya SES Release 4.0 completed The SAMP remote maintenance board firmware has been verified The initial_setup script has been run and the Avaya SES Edge has been chosen as the Master Administrator web interface The start of SES services Server date/time, Network Time Server, and Authentication file tasked performed using the web Maintenance interface Server License installation (requires Edge Proxy and Basic Proxy licenses) with the Avaya SES Edge running the WebLM service for the Avaya SES configuration For more information on installing Avaya SES as separate Home and Edge servers including details on the aforementioned items above, please refer to reference [2] and the appropriate sections in reference [3] in Section Perform Setup using the Avaya SES Edge - Master Administrator Access the Avaya SES Edge web interface by typing the following URL on a web browser and then pressing enter (screens not shown): or IP address of Avaya SES Edge server>/admin Press the Continue button on the Welcome web page and then press the Yes button in the Security Alert pop-up window. When the Integrated Management Standard Manager Solutions Login web page appears, log in using proper credentials. Click the Launch Administration Web Interface link to enter the Administration web pages. Once the Administration web page appears, click on Setup to display the first of the Setup screens. Step Description 1. From the first Setup screen, click on Setup SIP Domain to continue (screen not shown). 10 of 48

11 2. In the Edit System Properties screen that appears, enter the following and leave the remaining fields with the default values: SIP Domain - retail.com is the domain name assign to the sample Avaya SES configuration License Host is the IP address for the Avaya SES Edge server Management System Access Login - admin (not entered in the screen below) is the exact matching login that the Avaya DOCM server (Step 12 in Section 4) will use to configure core-routing functions on the Avaya SES Edge. Management System Access Password - (not entered in the screen below) is the exact matching password that the Avaya DOCM server (Step 12 in Section 4) will use to configure core-routing functions on the Avaya SES Edge. Click the Update button and then click on the Continue button on the confirmation screen (not shown). From the Setup screen, click on Setup Hosts to continue (not shown). 11 of 48

12 3. A host is an Avaya SES server. In the Add Host screen that appears, enter the following and leave the remaining fields with the default values: Host IP Address is the IP address of the Avaya SES Edge server DB Password - The mvss database password set at installation during the execution of the initial_setup script. Profile Service Password - Enter a unique password (used by the internal software components for secure communication between the Avaya SES servers and the master administration system) Click on the Update button and then click on the Continue button on the confirmation screen (not shown). 12 of 48

13 4. Repeat Step 3 to add the Avaya SES Home server ( ). For the Host Type field, select home from the drop down menu. From the Setup screen, click on Setup Media Servers to continue (not shown). 5. In the Add Media Server Interface screen that appears, enter the following and leave the remaining fields with the default values: Media Server Interface Name - C-LAN - A unique descriptive name for the CLAN interface located in the Avaya G650 Media Gateway in Figure 1. Host (Avaya SES Home server). SIP Trunk Link Type - TLS (Refer to Step x in Section 5). SIP Trunk IP Address (Refer to Step x in Section 5). Media Server Admin Address (IP address of Avaya S8710 Media Server). Media Server Admin Login administrator (Avaya Communication Manager administration account with System Access Terminal (SAT) access). Media Server Admin Password - <password> Media Server Admin Password Confirm - <password> Click the Add button to continue and then click on the Continue button on the confirmation screen (not shown). 13 of 48

14 6. Click the Update link to save the changes and synchronize the database on both the Avaya SES Home and Edge servers Configure Media Server Address Maps Address maps are a feature in Avaya SES used to route SIP messages to the appropriate SIP hosts based on the destination address in the INVITE message. This section details the configuration of Media Server address maps for routing calls to Avaya Communication Manager over the SIP trunk with request URI s starting with the prefix assigned to the Avaya SES Home (refer to Step 13 in Section 4). Please note that if the Avaya SES Edge has an address map for routing public numbers to a SIP service provider, the private numbers must not conflict with the public numbers. Any assigned prefixes take precedence over any configured Avaya SES address maps. Configuring Avaya SES Edge address maps for routing to a SIP service provider is beyond the scope of these Application Notes. Step Description 1. Access the Avaya SES Edge Administration web interface. From the Top menu on the left window pane, click on Media Servers and then click on List Media Servers (screens not shown). 14 of 48

15 2. Click on Map (as shown below) and then click on Add Map in New Group on the List Media Server Address Map screen that follows. 3. In the Add Media Server Address Map screen that appears, enter the following and leave the remaining fields with the default values: Name - From DO RS2 - A descriptive name to recognize the address map Pattern - ^sip:199[0-9]{7}@retail.com - Matches prefix 199 and 7 digit extension length (based on the configured dial plan in Avaya Communication Manager) Replace URI this box must be checked to overwrite the URI of the SIP messages with the contact information to send calls to Avaya Communication Manager Click the Add button and then the Continue button on the confirmation screen (not shown). The List Media Server Address Map screen appears (not shown) with the newly added address map. Please note that under the Contact column, the contact information is auto-generated as follows: sip:$(user)@ :5061; transport=tls 4. Click the Update link to save the changes and synchronize the database on both the Avaya SES Home and Edge servers. 15 of 48

16 4. Configure SIP Private Networking using Distributed Office Central Manager This section details the administration necessary on Avaya Distributed Office Central Manager (DOCM) to configure SIP private networking in an Avaya Distributed Office branch network. It is assumed that the Avaya DOCM server has been successfully installed prior to performing the tasks in this section. For more information on Avaya Distributed Office Central Manager and for other documentation regarding Avaya Distributed Office, please refer to [3] and [4] in Section 8. Step Description 1. Access the Avaya DOCM web interface by typing the following URL on a web browser and then pressing enter: or IP address of DOCM server> 16 of 48

17 2. Log in to the Avaya DOCM Server using proper login credentials. 3. In the left pane of the Avaya DOCM window that appears, click on Branches to display any Avaya Distributed Office branches in the managed configuration. 17 of 48

18 4. To add Avaya Distributed Office branches to the Branch list, click the Add button. Otherwise, skip Steps 5 through 9 to continue. 5. Click on the Select Device button to add any Avaya Distributed Office branches that have been discovered by the Network Management Console. 6. Click on a discovered Avaya Distributed Office branch in the Device Selection pop-up window (to highlight it as shown on the right) and then click on the OK button to continue. 18 of 48

19 7. Enter the selected Avaya Distributed Office login and password for the Admin Username and Admin Password fields respectively. Click on the Test Connectivity button to verify the login credentials. The Connectivity Result popup window should appear (not shown) with Successfully Connected to Branch if the login credentials are correct. Click the Save Changes button to continue. 8. In the Schedule pop-up window that appears, click on the Run now radio button to save the configuration changes for adding the Avaya Distributed Office branch and perform a full synchronization. Click the OK button to continue. To add additional Avaya Distributed Office branches, repeat Step 4 through Step 8. Note: To schedule the Add Branch <DO IP address> job at a later date and time, the other jobs in this section should also be scheduled consecutively (each job scheduled at a later date and time than the previous job). 19 of 48

20 9. Before continuing to the next task, click on Jobs to view the status of the requested job tasks and verify that the Active job completes successfully. Click on the Refresh button to refresh the status. 10. In the left pane double-click on Enterprise and then click on Private Networking to continue. 20 of 48

21 11. Click the Enable Private Networking check box to enable the feature. The General tab first appears. Enter the SIP domain name ( retail.com for the sample configuration) in the Domain Name field and then click the up or down arrow head to select the desired Prefix Length (3- digit prefixes for the sample configuration). To make a call to a particular location or branch utilizing SIP Private Networking (by means of an Avaya SES Edge Server), the user must dial the assigned Prefix for that location and the destination extension. Click the SES tab to continue. Note: If the SIP domain was already configured using the Avaya SES Web Administration Interface, changing the SIP domain here will be service affecting for the Avaya SES. 21 of 48

22 12. For the Avaya SES Edge Server, enter the IP Address and the Management System Access Login and Password assigned in Edit System Properties Screen of the Avaya SES Edge as entered in Section 3.1. Click on the Test Connectivity button to verify the login credentials. The Connectivity Result popup window should appear (not shown) with Successfully Connected to SIP Enablement Services if the login credentials are correct. Click the SIP Servers tab to continue. 22 of 48

23 13. To add Avaya SES Home server(s) to the Private Network SIP Servers table, click on the Add Row button. For the Avaya SES Home server, enter SES home server (a descriptive name) in the Name field, the IP address in the IP Address field, the assigned 3-digit prefix 199 in the Prefix (3 Digits) field, and then click the up or down arrow head to select the desired Extension Length (7-digit length for the Retail Store Headquarters location). For this sample configuration, the Avaya SES Home server provides SIP support for Avaya Communication Manger, Avaya Voice Portal, and Avaya Modular Messaging (refer to Figure 2) at the Headquarters location. To make a call from an Avaya Distributed Office branch to the Headquarters location, the aforementioned systems, or SIP registered endpoint on the Avaya SES Home server utilizing SIP Private Networking, the user must dial the 199 prefix and the destination extension. Click the Save Changes button and then in the Schedule pop-up window that appears (not shown), click on the OK button to run the Enable Private Networking job. Upon job completion the current data will be reloaded on this page to reflect the requested configuration changes. 23 of 48

24 14. Before continuing to the next task, click on Jobs to view the status of the Enable Private Networking job and verify that it has completed successfully. In the left frame, click on Branches to continue. 15. Click on an Avaya Distributed Office branch (to select it as shown below) and then click on the Edit button to continue. 24 of 48

25 16. To enable the Avaya Distributed Office branch for SIP private networking, click the Include In Private Network check box under the Private Networking (PN) section. Enter a unique 3- digit prefix (refer to Step 11) for the Avaya Distributed Office branch in the Branch Prefix field. In this configuration to make a call from Avaya Communication Manager endpoints or SIP registered endpoints at the Headquarters location to the Avaya Distributed Office branch, a user must dial the 299 prefix and the 3-digit destination extension. Click the Save Changes button and then in the Schedule pop-up window that appears (not shown), click on the OK button to run the Change Branch < > job. Upon job completion the current data will be reloaded on this page to reflect the requested configuration changes. Note the following: The Avaya Distributed Office branches are considered trusted hosts by Avaya SES Edge. Extension numbers on Avaya Communication Manager in an Avaya Distributed Office network cannot conflict with prefix + extension number in Avaya Distributed Office branch location. For Example: Avaya Communication Manager at Retail Headquarters Store has an administered extension of and Avaya Distributed Office at the Branch Store has an administered extension of 556 and a prefix of 299. If a call is made from a Retail Headquarters Store endpoint to extension 556 (using the Branch Store location prefix 299), the call will route locally to extension of 48

26 17. Click on Jobs to view the status of the Change Branch <DO IP Address> job and verify that it has completed successfully. Click on the Refresh button to refresh the status. In the left frame, click on Private Networking to continue. 18. Click on the SES tab and then click on the Force Sync button to update Avaya SES with the updated SIP private network configuration that now will include the Avaya Distributed Office branch. In the Force Sync of SES started pop-up window that appears (not shown), click on the OK button to continue. Note: Performing a Force Sync clears and resets the SES Prefix and Handle Maps which is temporarily service affecting (approximately 60 seconds). 26 of 48

27 5. Configure Avaya Communication Manager These Application Notes assume all equipment in Table 1 have been previously administered with the exception of the configuration parameters required on Avaya Communication Manager for a SIP trunk to Avaya SES Home and the for handling call routing to and from the Avaya Distributed Office branch. This section contains detail instructions on how perform the following: Verify Avaya Communication Manager Licenses Configure SIP Signaling Group and Trunk Group with the Avaya SES Home as the far end destination Configure routing to the Avaya Distributed Office at the Branch Store Configure incoming call handling treatment to strip off the prefix for calls arriving from the Branch Store location via the SIP trunk group to the Avaya SES Home Verify Avaya Communication Manager Licenses To set up a SIP trunk to Avaya SES Home, certain Avaya Communication Manger licenses must be active. The next steps verify these required licenses. If any licenses are missing, contact the Avaya Authorized Sales representative. 27 of 48

28 The following commands were entered on an Avaya Communication Manager System Access Terminal (SAT) running on an Avaya S8710 Server: Step Description 1. Issue the command display system-parameters customer-options to display the active licensed features. Go to Page 2 and verify that there is sufficient remaining SIP trunk capacity. The number of available SIP trunks is the difference between the Maximum Administered SIP Trunks and the USED field values. display system-parameters customer-options Page 2 of 11 OPTIONAL FEATURES IP PORT CAPACITIES USED Maximum Administered H.323 Trunks: Maximum Concurrently Registered IP Stations: 50 4 Maximum Administered Remote Office Trunks: 0 0 Maximum Concurrently Registered Remote Office Stations: 0 0 Maximum Concurrently Registered IP econs: 0 0 Max Concur Registered Unauthenticated H.323 Stations: 0 0 Maximum Video Capable H.323 Stations: 0 0 Maximum Video Capable IP Softphones: 0 0 Maximum Administered SIP Trunks: Maximum Number of DS1 Boards with Echo Cancellation: 0 0 Maximum TN2501 VAL Boards: 10 1 Maximum Media Gateway VAL Sources: 10 0 Maximum TN2602 Boards with 80 VoIP Channels: Maximum TN2602 Boards with 320 VoIP Channels: Maximum Number of Expanded Meet-me Conference Ports: Go to Page 3 and verify that the ARS/AAR Dialing without FAC field is set to y. The Automatic Alternate Routing (AAR) dialing without Feature Access Code (FAC) feature is required to route extensions or range of extensions over the SIP trunk to Avaya SES Home. display system-parameters customer-options Page 3 of 11 OPTIONAL FEATURES Abbreviated Dialing Enhanced List? y Audible Message Waiting? y Access Security Gateway (ASG)? n Authorization Codes? n Analog Trunk Incoming Call ID? y CAS Branch? n A/D Grp/Sys List Dialing Start at 01? n CAS Main? n Answer Supervision by Call Classifier? n Change COR by FAC? n ARS? y Computer Telephony Adjunct Links? n ARS/AAR Partitioning? y Cvg Of Calls Redirected Off-net? y ARS/AAR Dialing without FAC? y DCS (Basic)? y ASAI Link Core Capabilities? y DCS Call Coverage? y ASAI Link Plus Capabilities? y DCS with Rerouting? y Async. Transfer Mode (ATM) PNC? n Async. Transfer Mode (ATM) Trunking? n Digital Loss Plan Modification? y ATM WAN Spare Processor? n DS1 MSP? n ATMS? n DS1 Echo Cancellation? y Attendant Vectoring? y 28 of 48

29 3. Go to Page 5 and verify that the Private Networking and Uniform Dialing Plan fields are set to y. These fields, along with the ARS/AAR Dialing without FAC feature (shown in Step 2) allow for routing a range of extensions in a SIP private network. display system-parameters customer-options Page 5 of 11 OPTIONAL FEATURES Multinational Locations? y Multiple Level Precedence & Preemption? n Multiple Locations? y Personal Station Access (PSA)? y Posted Messages? n PNC Duplication? n Port Network Support? y Processor and System MSP? n Private Networking? y Processor Ethernet? y Remote Office? n Restrict Call Forward Off Net? y Secondary Data Module? y Station and Trunk MSP? n Station as Virtual Extension? n System Management Data Transfer? n Tenant Partitioning? n Terminal Trans. Init. (TTI)? y Time of Day Routing? n Uniform Dialing Plan? y Usage Allocation Enhancements? y TN2501 VAL Maximum Capacity? y Wideband Switching? n Wireless? n 5.2. Configure SIP trunk to Avaya SES Home Server This section details the administration on Avaya Communication Manager that must be performed to set up a SIP trunk to the Avaya SES Home. It is assumed that the C-LAN and Media Processor board are installed and configured on the Avaya G650 Media Gateway at the Retail Store Headquarters location. Step Description 1. Issue the command change node-names ip to assign the node names for the C-LAN board and Avaya SES home server. The node name for the Media Processor board is also assigned using this command. The following values were entered for the Name and IP Address fields for this configuration example: ses-home1 and for the Avaya SES home server, C- LAN and for the C-LAN board, and MediaResource and for the IP Media Resource 320 board. Submit the changes. change node-names ip Page 2 of 2 IP NODE NAMES Name IP Address ses-home C-LAN MediaResource of 48

30 2. Issue the command change ip-codec-set x, where x is the IP codec set number used for calls over the SIP private network to the Avaya Distributed Office branches. For this configuration example, IP codec set 7 is used. Enter G.729, G726A-32K, G K for the Audio Codec fields and retain the defaults for the remaining fields. These audio codecs match the hard coded audio codecs on Avaya Distributed Office for inter-location calling. For the Media Encryption field, enter none. Submit the changes. change ip-codec-set 7 Page 1 of 2 Codec Set: 7 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.729 n : G.726A-32K n : G K n : 5: 6: 7: Media Encryption 1: none 2: 3: 30 of 48

31 3. Issue the command change ip-network-region x, where x is the IP network region number (7 for this sample configuration). Enter retail.com for the Authoritative Domain field, 7 for the Codec Set field (refer to Step 2), and yes for the Intra-region IP-IP Direct Audio and Inter-region IP-IP Direct Audio fields. The IP-IP Direct Audio settings ensure the most efficient use of the TN2602AP Media Processor resources. change ip-network-region 7 Page 1 of 19 IP NETWORK REGION Region: 7 Location: Authoritative Domain: retail.com Name: ADO Branch Store MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes Codec Set: 7 Inter-region IP-IP Direct Audio: yes UDP Port Min: IP Audio Hairpinning? y UDP Port Max: DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: P/Q PARAMETERS Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6 Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? n H.323 Link Bounce Recovery? y Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: 5 4. Go to Page 3 to configure the Inter Network Region Connection Management parameters between IP network region 7 (Avaya Distributed Office) and IP network region 1 (Retail Store Headquarters location). Set the Codec Set field to 7 (refer to Step 2), y for the direct WAN field, and NoLimit for the WAN-BW-Limits field for calls routed between the Avaya Distributed Office branch and the Retail Store Headquarters endpoints and trunks. Submit the changes. change ip-network-region 7 Page 3 of 19 Inter Network Region Connection Management src dst codec direct WAN-BW-limits Video Dyn rgn rgn set WAN Units Total Norm Prio Shr Intervening-regions CAC IGAR y NoLimit n 31 of 48

32 5. Issue the command add signaling-group x, where x is an available signaling group number. Signaling group 8 is used for this sample configuration. Enter the following: Group Type sip Near-end Node Name C-LAN (refer to Step 1) Far-end Node Name ses-home1 (refer to Step 1) Far-end Network Region 7 (refer to Step 3) Far-end Domain retail.com (refer to Step 2 in Section 3.1) Direct IP-IP Audio Connections y (allows for the optimization of RTP paths to reduce the use of IP Media Processor resources when possible) Submit the changes. Note: Transport Layer Security tls is the default for the Transport Method field. The Nearend Listen Port and Far-end Listen Port for TLS is add signaling-group 8 Page 1 of 1 SIGNALING GROUP Group Number: 8 Group Type: sip Transport Method: tls Near-end Node Name: C-LAN Far-end Node Name: ses-home1 Near-end Listen Port: 5061 Far-end Listen Port: 5061 Far-end Network Region: 7 Far-end Domain: retail.com Bypass If IP Threshold Exceeded? y DTMF over IP: rtp-payload Enable Layer 3 Test? n Session Establishment Timer(min): 120 Direct IP-IP Audio Connections? y IP Audio Hairpinning? y 32 of 48

33 6. Issue the command add trunk-group x, where x is an available trunk group number. Trunk group 8 is used for this sample configuration. Enter the following: Group Type sip Group Name Enter a descriptive name TAC Refer to the Dial Plan to enter an available trunk access code. Service Type tie Signaling Group 8 (Refer to Step 5) Number of Members For this example configuration, 24 members were configured. Submit the changes. add trunk-group 8 Page 1 of 21 TRUNK GROUP Group Number: 8 Group Type: sip CDR Reports: y Group Name: To-Branch Store COR: 1 TN: 1 TAC: 108 Direction: two-way Outgoing Display? n Dial Access? n Night Service: Queue Length: 0 Service Type: tie Auth Code? n Signaling Group: 8 Number of Members: Issue the command save translation to make the changes permanent. 33 of 48

34 5.3. Configure Call Routing to the Avaya Distributed Office Branch This section details the administration on Avaya Communication Manager that must be performed to set up call routing to the Avaya Distributed Office branch. Step Description 1. Issue the command change route-pattern x, where x is an available route pattern number. Route pattern 8 is utilized for routing calls to the Avaya Distributed Office branch for this sample configuration. For the Pattern Name field, enter a descriptive name for the route pattern. Enter the trunk group number assigned in Step 6 in Section 5.2 for the Grp No field, and assign an appropriate Facility Restriction Level ( 0 is the least restrictive) for the FRL field. Submit the changes. change route-pattern 8 Page 1 of 3 Pattern Number: 8 Pattern Name: To ADO Branch SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: 8 0 n user 2: n user 3: n user 4: n user 5: n user 6: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR M 4 W Request Dgts Format Subaddress 1: y y y y y n n rest none 2: y y y y y n n rest none 3: y y y y y n n rest none 4: y y y y y n n rest none 5: y y y y y n n rest none 6: y y y y y n n rest none 34 of 48

35 2. Issue the command change uniform-dialplan x, where x is the leading digits (as defined in the dial plan) for the prefix assigned for routing calls to Avaya Distributed Office at the Branch Store location. In this sample configuration, the prefix 299 and extension range 5xx is set aside for the Branch Store location. Go to Page 2 to add new entries. Enter the following: Matching Pattern 299 (Leading digits dialed) Len 6 (The length of the prefix + extension) Del 0 (No digit deletion) Net aar (Sent to the Automatic Alternate Routing table) Conv n (No conversion) Submit the changes. change uniform-dialplan 299 Page 2 of 2 UNIFORM DIAL PLAN TABLE Percent Full: 0 Matching Insert Node Pattern Len Del Digits Net Conv Num aar n 3. Issue the command change aar analysis x, where x matches the same leading digits used in Step 2. The AAR DIGIT ANANLYSIS TABLE matches the leading digits dialed (as per the Uniform Dial Plan) to the desired route pattern. Go to Page 2 to add new entries to the AAR DIGIT ANANLYSIS TABLE. Enter the following: Dialed String 299 (Leading digits dialed) Total Min 6 (Minimum number of digits expected) Total Max 6 (Maximum number of digits expected) Route Pattern 8 (Refer to Step 1) Call Type aar (Automatic Alternate Routing) Submit the changes. change aar analysis 299 Page 2 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 2 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd aar n 4. Issue the command save translation to make the changes permanent. 35 of 48

36 5.4. Configure Incoming Call Handling Treatment This section details the administration on Avaya Communication Manager that must be performed to strip off the prefix 199 for calls arriving from the Branch Store location via the SIP trunk group to the Avaya SES Home. Step Description 1. Issue the command change inc-call-handling-trmt trunk group x, where x is assigned SIP trunk group in Step 6 in Section 5.2. For the Called Len, enter 10 for the total length which includes the 3-digit prefix and the 7-digit extension as per the dial plan for the Retail Store Headquarters location. Enter 199 for the Called Number field to find a match for incoming calls with the assigned prefix. Enter 3 for the Del field to remove the 3-digit prefix before routing the incoming call using the administered dial plan. Submit the changes. change inc-call-handling-trmt trunk-group 8 Page 1 of 30 INCOMING CALL HANDLING TREATMENT Service/ Called Called Del Insert Feature Len Number tie tie tie tie tie tie tie tie tie tie tie tie tie tie tie tie tie 2. Issue the command save translation to make the changes permanent. 36 of 48

37 6. Verification Steps This section details how to verify the sample configuration illustrated in Figure 1 for the Avaya solution consisting of Avaya SES Edge 4.0 supporting a SIP private network for communications between Avaya Distributed Office at the Branch Store location and Avaya Communication Manager at the Retail Store Headquarters location Verify Avaya SIP Enablement Services Prefix Map Access the Avaya SES Edge web interface by typing the following URL on a web browser and then pressing enter (screens not shown): or IP address of Avaya SES Edge server>/admin Press the Continue button on the Welcome web page and then press the Yes button in the Security Alert pop-up window. When the Integrated Management Standard Manager Solutions Login web page appears, log in using proper credentials. Click the Launch Administration Web Interface link to enter the Administration web pages. Once the Administration web page appears, click on Core Router and then click on Prefix Map from the Top menu on the left window pane. Verify that the Branch Prefix, Branch Address, Core Router and Total Length fields are correct as configured using Avaya Distributed Office Central Manager. Figure 6: Avaya SES Prefix Map 37 of 48

38 6.2. Verify Retail Store Headquarters to Branch Store Call Routing This section details how to verify Retail Store Headquarters to Branch Store call routing using the configured SIP private network. The test scenario verifies a call is successfully placed from the Avaya one-x Deskphone Edition for 9630 IP Telephone (Extension ) at Retail Store Headquarters to the Avaya one-x Deskphone Edition for 9630 SIP Telephone (Extension 556) at the Branch Store location. Step Description 1. From the Avaya Communication Manager System Access Terminal (SAT), issue the command list trace tac x, where x is the assigned TAC (refer to Step 6 in Section 5.2). Place a call from extension at the Retail Store Headquarters location to extension 556 at the Branch Store location using the Branch Store prefix 299. Verify the following: Route pattern 8 is chosen based on the dialed digits and UDP/AAR configuration (refer to Section 5.3). A member of trunk group 8 is seized (Note the trunk group member number. It will be used in following step). The audio codec G.729 is utilized for the Inter-site (IP network region 1 to IP network region 7) call (refer to Step 2 in Section 5.2) The Avaya one-x Deskphone Edition for 9630 SIP Telephone (Extension 556) at the Branch Store location rings with proper caller ID information for extension and is successfully answered. Two-way audio talk path list trace tac 108 Page 1 LIST TRACE time data 11:10:22 dial route:udp AAR 11:10:22 term trunk-group 8 cid 0x3a2 11:10:22 dial route:udp AAR 11:10:22 route-pattern 8 preference 1 cid 0x3a2 11:10:22 seize trunk-group 8 member 9 cid 0x3a2 11:10:22 Calling Number & Name spice-30 reta 11:10:22 Proceed trunk-group 8 member 9 cid 0x3a2 11:10:22 Alert trunk-group 8 member 9 cid 0x3a2 11:10:22 G729 ss:off ps:20 rn:7/ : : :10:22 xoip: fax:relay modem:off tty:us :21604 uid:0x :10:29 active trunk-group 8 member 9 cid 0x3a2 11:10:29 G729 ss:off ps:20 rn:1/ : : :10:29 G729A ss:off ps:20 rn:7/ : : of 48

39 2. Issue the command status trunk x/y, where x is the trunk group number and y is the member number for the call placed in Step 1 (trunk-group 8 member 9). Verify the following: The Signaling near-end IP address (C-LAN) for the Near-end IP Addr field, assigned in Step 5 of Section 5.2. The Signaling far-end IP address (Avaya SES Home server) for the Farend IP Addr field, assigned in Step 5 of Section 5.2. The inter-site call is using audio codec G.729 (refer to Step 2 in Section 5.2). The Audio near-end IP address for the Near-end IP Addr field of the Avaya one-x Deskphone Edition for 9630 IP Telephone (Extension ) at the Retail Store Headquarters location. The Audio far-end IP address for the Far-end IP Addr field of the Avaya Distributed Office i40 Platform. The Audio Connection Type field is ip-direct confirming IP-IP Direct Audio is enabled (refer to Steps 3 and 5 in Section 5.2). status trunk 8/009 Page 1 of 2 TRUNK STATUS Trunk Group/Member: 0008/009 Port: T00052 Signaling Group ID: Service State: in-service/active Maintenance Busy? no IGAR Connection? no Connected Ports: S00162 Port Near-end IP Addr : Port Far-end IP Addr : Port Signaling: 01A : : 5061 G.729 Audio: : : 2128 Video: Video Codec: Authentication Type: None Audio Connection Type: ip-direct 39 of 48

40 3. Go to Page 2 to view and verify the SRC PORT TO DEST PORT TALKPATH information. status trunk 8/009 Page 2 of 2 SRC PORT TO DEST PORT TALKPATH src port: T00052 T00052:TX: :2128/g729/20ms S00162:RX: :22078/g729a/20ms dst port: S of 48

41 6.3. Verify Branch Store to Retail Store Headquarters Call Routing This section details how to verify Branch Store to Retail Store Headquarters call routing using the configured SIP private network. The test scenario verifies the a call is successfully placed from the Avaya 4621SW IP Telephone (Extension 557) at the Branch Store location, to the Avaya 4625SW IP Telephone (Extension ) at Retail Store Headquarters location. Step Description 1. From the Avaya Communication Manager System Access Terminal (SAT), issue the command list trace tac x, where x is the assigned TAC (refer to Step 6 in Section 5.2). Place a call from extension 557 at the at the Branch Store location to extension at the Retail Store Headquarters location using the Retail Store Headquarters prefix 199. Verify the following: A member of trunk group 8 is seized (Note the trunk group member number. It will be used in following step). The Avaya 4625SW IP Telephone (Extension ) at the Retail Store Headquarters location rings with proper caller ID information for extension 557 and is successfully answered. Two-way audio talk path The call path is successfully shuffled directly between the two endpoints (Extension with an IP address of and Extension 557 with IP address if ). The audio codec G.729 is utilized for the Inter-site (IP network region 1 to IP network region 7) call (refer to Step 2 in Section 5.2) list trace tac 108 Page 1 LIST TRACE time data 13:21:06 Calling party trunk-group 8 member 1 cid 0x3ae 13:21:06 Calling Number & Name IP557 13:21:06 active trunk-group 8 member 1 cid 0x3ae 13:21:06 dial :21:06 ring station cid 0x3ae 13:21:06 G711MU ss:off ps:20 rn:1/ : : :21:06 xoip: fax:relay modem:off tty:us :25976 uid:0x8bff 13:21:06 G726A32K ss:off ps:20 rn:1/ : : :21:06 xoip: fax:relay modem:off tty:us :25972 uid:0x :21:13 active station cid 0x3ae 13:21:14 G726A32K ss:off ps:20 rn:1/ : : :21:14 xoip: fax:relay modem:off tty:us :25972 uid:0x :21:14 G729A ss:off ps:20 rn:1/ : : :21:14 G729 ss:off ps:20 rn:1/ : : of 48