Avaya Aura Communication
Manager 7.1 Application Notes
Avaya Aura Communication
Manager 7.1 Application Notes

Avaya Aura Communication Manager 7.1 Application Notes

Application with verizon business ip contact center (ipcc) services suite
Table of Contents

Advertisement

Avaya Solution & Interoperability Test Lab
Application Notes for Avaya Aura® Communication
Manager 7.1, Avaya Aura® Session Manager 7.1, and Avaya
Session Border Controller for Enterprise 7.2 with Verizon
Business IP Contact Center (IPCC) Services Suite – Issue 1.0
These Application Notes describe a sample configuration of Avaya Aura® Communication
Manager 7.1, Avaya Aura® Session Manager 7.1, and Avaya Session Border Controller for
Enterprise 7.2 with Verizon Business IP Contact Center (IPCC) Services suite. The Verizon
Business IPCC Services suite includes the IP Toll Free VoIP Inbound and IP-IVR SIP trunk
service offers. This service suite provides toll free inbound calling via standards-based SIP
trunks as well as re-routing of inbound toll free calls to alternate destinations based upon SIP
messages (i.e., REFER) generated by Communication Manager. The Communication Manager
Network Call Redirection (NCR) and SIP User-to-User Information (UUI) features can be
utilized together to transmit UUI within SIP signaling messages to alternate destinations via
the Verizon network. These Application Notes update previously published Application Notes
with newer versions of Communication Manager, Session Manager, and Avaya Session
Border Controller for Enterprise.
Readers should pay attention to Section 2, in particular the scope of testing as outlined in
Section 2.1 as well as any 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 in the Avaya Solution &
Interoperability Test Lab, utilizing a Verizon Business Private IP (PIP) circuit connection to
the production Verizon Business IPCC Services.
DDT; Reviewed:
SPOC 10/18/2017
Abstract
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
1 of 95
CM71SM71-VzIPCC

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Aura Communication Manager 7.1 and is the answer not in the manual?

Questions and answers

Summary of Contents for Avaya Aura Communication Manager 7.1

  • Page 1 Abstract These Application Notes describe a sample configuration of Avaya Aura® Communication Manager 7.1, Avaya Aura® Session Manager 7.1, and Avaya Session Border Controller for Enterprise 7.2 with Verizon Business IP Contact Center (IPCC) Services suite. The Verizon Business IPCC Services suite includes the IP Toll Free VoIP Inbound and IP-IVR SIP trunk service offers.
  • Page 2: Table Of Contents

    Entity Link to Avaya Aura® Communication Manager – Public Trunk ....25 5.5.1 Entity Link to Avaya Aura® Communication Manager – Local Trunk ....26 5.5.2 5.5.3 Entity Link for the Verizon Business IPCC Services via the Avaya SBCE .....26 5.5.4 Entity Link to Avaya Aura® Messaging ..............26 5.6. Time Ranges ......................26 5.7.
  • Page 3 6.17. Configure Avaya Session Border Controller for Enterprise Release 7.2 ....57 System Management – Status ...................58 7.1. 7.2. TLS Management......................59 Verify TLS Certificates – Avaya Session Border Controller for Enterprise ....59 7.2.1 7.2.2 Server Profiles ......................60 7.2.3 Client Profiles ......................61 7.3.
  • Page 4 Example Incoming Call from PSTN via Verizon IPCC to Telephone .....84 9.1.2 Example Incoming Call Referred via Call Vector to PSTN Destination ....86 9.2. Avaya Aura® System Manager and Avaya Aura® Session Manager Verifications88 9.3. Avaya Session Border Controller for Enterprise Verification ........89 9.3.1 Welcome Screen .......................89...
  • Page 5: Introduction

    In the sample configuration, an Avaya Session Border Controller for Enterprise (Avaya SBCE) is used as an edge device between the Avaya CPE and Verizon Business. The Avaya SBCE performs SIP header manipulation and provides topology hiding to convert the private Avaya CPE IP addressing to IP addressing or domains appropriate for the Verizon access method.
  • Page 6: General Test Approach And Test Results

    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.
  • Page 7: Interoperability Compliance Testing

    “recvonly”. While the call remains on hold, RTP will flow from the Avaya CPE to Verizon, but no RTP will flow from Verizon to the Avaya CPE (i.e., as intended). When the user resumes the call from hold, bi-directional media path resumes.
  • Page 8: Test Results

     DTMF transmission using RFC2833. For inbound toll-free calls, PSTN users dialing post- answer DTMF digits are recognized properly by the Avaya CPE.  Proper DiffServ markings for SIP signaling and RTP media flowing from the Avaya CPE to Verizon.
  • Page 9: Support

    2.3. Support 2.3.1 Avaya For technical support on the Avaya products described in these Application Notes visit http://support.avaya.com 2.3.2 Verizon For technical support on Verizon Business IPCC Services offer, visit online support at http://www.verizonenterprise.com/support/ DDT; Reviewed: Solution & Interoperability Test Lab Application Notes...
  • Page 10: Reference Configuration

    Verizon Business IPCC Services node. The Avaya CPE location simulates a customer site. At the edge of the Avaya CPE location is an Avaya Session Border Controller for Enterprise. The Avaya SBCE receives traffic from the Verizon Business IPCC Services on port 5060 and sends traffic to the Verizon Business IPCC Services using destination port 5072, using UDP for transport.
  • Page 11: History Info And Diversion Headers

    IPCC Services was added to a configuration that already used domain “avayalab.com” at the enterprise. As such, the Avaya SBCE is used to adapt the domains as needed. These Application Notes indicate the configuration that would not be required in cases where the CPE domain in Communication Manager and Session Manager match the CPE domain known to Verizon.
  • Page 12: Call Flows

    1. A PSTN phone originates a call to a Verizon IP Toll Free number. 2. The PSTN routes the call to the Verizon IP Toll Free service network. 3. The Verizon IP Toll Free service routes the call to the Avaya Session Border Controller for Enterprise.
  • Page 13: Inbound Ip Toll Free Call With Unsuccessful Network Call Redirection

    Upon answer, the calling party is connected to the target party. 4. The Verizon IP Toll Free service notifies the Avaya CPE that the referred call has been answered (NOTIFY/sipfrag 200 OK). Communication Manager sends a BYE. The calling party and the target party can talk.
  • Page 14 VOLUM E SPEAKER MUTE Agent / Phone Figure 5: Inbound Verizon IP Toll Free– Post-Answer SIP REFER Redirection Unsuccessful DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 14 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 15: Equipment And Software Validated

    Equipment/Software Release/Version Avaya Aura® Communication Manager 7.1.0.532.0-23985 (7.1.1.0.0-FP1) 7.1.1.0.046931 Avaya Aura® System Manager 7.1.1.0.711008 Avaya Aura® Session Manager Avaya Session Border Controller for Enterprise 7.2.0.0-18-13712 Avaya Aura® Messaging 7.0 SP 0 Avaya Aura® Media Server 7.8.0.323 G450 Gateway 38.18.0 Avaya 96X1- Series Telephones (SIP) R7.1.0.1.1...
  • Page 16: Configure Avaya Aura® Session Manager Release 7.1

    Consult [1] - [4] for further details. This section provides the procedures for configuring Session Manager to process inbound and outbound calls between Communication Manager and the Avaya SBCE. In the reference configuration, all Session Manager provisioning is performed via System Manager.
  • Page 17: Sip Domain

     IP Address Pattern: Leave blank.  Notes: Add a brief description. Step 3 - Click Commit to save. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 17 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 18: Common Location

    5.2.2 Common Location To configure the Avaya SBCE Location, repeat the steps in Section 5.2.1 with the following changes:  Name – Enter a descriptive name (e.g., Common). DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 18 of 95 SPOC 10/18/2017 ©2017 Avaya Inc.
  • Page 19: Configure Adaptations

     The Verizon called number digit string in the Request URI is replaced with the associated Communication Manager extensions defined for Agent skill queue VDNs/telephones. 5.3.1 Adaptation for Avaya Aura® Communication Manager Extensions The Adaptation administered in this section is used for modification of SIP messages to Communication Manager extensions from Verizon.
  • Page 20 Step 5 - Click on Commit. Note – No Digit Conversion for Incoming Calls to SM were required in the reference configuration. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 20 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 21: Adaptation For The Verizon Business Ipcc Services

    Communication Manager, as well as calls to Messaging.  Avaya SBCE (Section 5.4.4) – This entity, and its associated Entity Link (using TLS and port 5061), is for calls from the Verizon Business IPCC Services via the Avaya SBCE.
  • Page 22: Avaya Aura® Session Manager Sip Entity

    Note – In the reference configuration, TLS is used as the transport protocol between Session Manager and Communication Manager (ports 5061 and 5071), and to the Avaya SBCE (port 5061). The connection between the Avaya SBCE and the Verizon Business IPCC Services uses UDP/5072 per Verizon requirements.
  • Page 23 Entity Links are defined in Section 5.5. The SIP Responses to an OPTIONS Request section of the form is not used in the reference configuration. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 23 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 24: Avaya Aura® Communication Manager Sip Entity - Public Trunk

    5.4.2 Avaya Aura® Communication Manager SIP Entity – Public Trunk Step 1 - In the SIP Entities page, click on New (not shown). Step 2 - In the General section of the SIP Entity Details page, provision the following:  Name – Enter a descriptive name (e.g., CM-TG2).
  • Page 25: Avaya Aura® Communication Manager Sip Entity - Local Trunk

    Note – See the information in Section 5.4 regarding the transport protocols and ports used in the reference configuration. 5.5.1 Entity Link to Avaya Aura® Communication Manager – Public Trunk Step 1 - In the left pane under Routing, click on Entity Links, then click on New (not shown).
  • Page 26: Entity Link To Avaya Aura® Communication Manager - Local Trunk

    To configure this Entity Link, repeat the steps in Section 5.5.1, with the following changes:  Name – Enter a descriptive name for this link to the Avaya SBCE (e.g., SM to SBC1).  SIP Entity 1 Port – Enter 5061.
  • Page 27: Routing Policies

    In this section, the following Routing Policies are administered:  Inbound calls to Communication Manager extensions (Section 5.7.1).  Inbound calls to Aura® Messaging (Section 5.7.2). 5.7.1 Routing Policy for Verizon Routing to Avaya Aura® Communication Manager This Routing Policy is used for inbound calls from Verizon.
  • Page 28 Note – Once the Dial Patterns are defined (Section 5.8) they will appear in the Dial Pattern section of this form. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 28 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 29: Routing Policy For Inbound Routing To Avaya Aura® Messaging

    Step 3 - Scrolling down to the Originating Location and Routing Policies section of the Dial Pattern Details page (not shown), click on Add. Step 4 - In the Originating Location, check the checkbox corresponding to the Avaya SBCE location, e.g., Common.
  • Page 30 Step 6 - Returning to the Dial Pattern Details page click on Commit. Step 7 - Repeat Steps 1-6 for any additional inbound dial patterns from Verizon. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 30 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 31: Verify Tls Certificates - Session Manager

    Step 2 - In the left pane under Inventory, click on Manage Elements and select the Session Manager element, e.g., SessionManager. Click on More Actions  Manage Trusted Certificates. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 31 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 32 Manager. If the Subject Details and Subject Alternative Name fields of the System Manager signed certificate need to be updated, click Replace, otherwise click Done (not shown). DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 32 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 33: Configure Avaya Aura® Communication Manager Release 7.1

    This section illustrates an example configuration allowing SIP signaling via the “Processor Ethernet” of Communication Manager to Session Manager. Note – The initial installation, configuration, and licensing of the Avaya servers and media gateways for Communication Manager are assumed to have been previously completed and are not discussed in these Application Notes.
  • Page 34 Multimedia Call Handling (Enhanced)? y Hospitality (G3V3 Enhancements)? y Multimedia IP SIP Trunking? y IP Trunks? y IP Attendant Consoles? y DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 34 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 35: System-Parameters Features

    Auto Abbreviated/Delayed Transition Interval (rings): 2 Protocol for Caller ID Analog Terminals: Bellcore Display Calling Number for Room to Room Caller ID Calls? n DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 35 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 36: Dial Plan

    Length Type 6.4. Node Names Node names define IP addresses to various Avaya components in the enterprise. In the reference configuration a Processor Ethernet (procr) based Communication Manager platform is used. Note that the Communication Manager procr name and IP address are entered during installation. The procr IP address was used to define the Communication Manager SIP Entities in Section 5.4.
  • Page 37: Processor Ethernet Configuration

    Suppression Per Pkt Size(ms) 1: G.722-64K 2: G.711MU 3: G.729A Media Encryption Encrypted SRTCP: enforce-unenc-srtcp 1: 1-srtp-aescm128-hmac80 2: none DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 37 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 38 Size(ms) t.38-standard ECM: y Modem TDD/TTY H.323 Clear-channel SIP 64K Data Media Connection IP Address Type Preferences 1: IPv4 DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 38 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 39: Codecs For Ip Network Region 2 (Calls From Verizon)

    Network regions provide a means to logically group resources. In the shared Communication Manager configuration used for the testing, the Avaya G450 Media Gateway and Avaya Media Server are in region 1. To provide testing flexibility, network region 2 was associated with other components used specifically for the Verizon testing.
  • Page 40 IP NETWORK REGION RTCP Reporting to Monitor Server Enabled? y RTCP MONITOR SERVER PARAMETERS Use Default Server Parameters? y DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 40 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 41: Sip Trunks

    Note that this trunk will use TLS port 5061 as described in Section 5.5.2. Note – Although TLS is used as the transport protocols between the Avaya CPE components, UDP was used between the Avaya SBCE and the Verizon Business IPCC Services. See the note in Section 5.4 regarding the use of TLS transport protocols in the CPE.
  • Page 42: Sip Trunk For Inbound Verizon Calls

     Direct IP-IP Audio Connections – Set to y, indicating that the RTP paths should be optimized directly to the associated stations, to reduce the use of media resources on the Avaya Media Gateway when possible (known as shuffling). Use the default parameters on page 2 of the form (not shown).
  • Page 43 XOIP Treatment: auto Delay Call Setup When Accessed Via IGAR? n Caller ID for Service Link Call to H.323 1xC: station-extension DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 43 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 44 Accept Redirect to Blank User Destination? n Enable Q-SIP? n Interworking of ISDN Clearing with In-Band Tones: keep-channel-active Request URI Contents: may-have-extra-digits DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 44 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 45: Local Sip Trunk (Avaya Sip Telephone And Messaging Access)

    Application Notes. 6.9.1 Announcements Various announcements will be used within the vectors. In the sample configuration, these announcements were sourced by the Avaya G450 Media Gateway. The following abridged list DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 45 of 95 SPOC 10/18/2017 ©2017 Avaya Inc.
  • Page 46: Post-Answer Redirection To A Pstn Destination

    Note that Verizon Business IPCC Services require the “+” in the Refer-To header for this type of call redirection. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 46 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 47: Post-Answer Redirection With Uui To A Sip Destination

    The Refer-To header will also contain the UUI set in variables A and B. Verizon will include this UUI in the INVITE ultimately sent to the SIP-connected target of the REFER, which is toll-free DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 47 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 48: Acd Configuration For Call Queued For Handling By Agent

    Skill? y Expected Call Handling Time (sec): 180 AAS? n Service Level Target (% in sec): 80 in 20 DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 48 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 49 08 stop The following screen illustrates an example agent-loginID 20001. In the sample configuration, an Avaya one-X® Deskphone logged in using agent-loginID 20001 and the configured Password to staff and take calls for skill 1. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes...
  • Page 50: Public Numbering

    Step 1 - Enter change public-unknown-numbering 5 ext-digits xxxxx, where xxxxx is the 5- digit extension number to change. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 50 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 51: Private Numbering

     Trk Grp(s) – Enter the number of the Local trunk group (e.g., 3).  Total Len - Enter the total number of digits after the digit conversion (e.g., 5). DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 51 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 52: Route Pattern For Calls Within The Cpe

    This form defines the Route pattern for the local SIP trunk, based on the route-pattern selected by the AAR table in Section 6.13 (e.g., calls to Avaya SIP telephone extensions or Messaging). Step 1 - Enter the change route-pattern 3 command and enter the following: ...
  • Page 53: Avaya G450 Media Gateway Provisioning

    6.14. Avaya G450 Media Gateway Provisioning In the reference configuration, a G450 Media Gateway is provisioned. The G450 is located in the Main site and is used for local DSP resources, announcements, Music On Hold, etc. Note – Only the Media Gateway provisioning associated with the G450 registration to Communication Manager is shown below.
  • Page 54: Avaya Aura® Media Server Provisioning

    Mutual Authentication? optional 6.15. Avaya Aura® Media Server Provisioning In the reference configuration, an Avaya Aura® Media Server is provisioned. The Media Server is located in the Main site and is used, along with the G450 Media Gateway, for local DSP resources, announcements, and Music On Hold.
  • Page 55: Save Translations

    Note – Testing was done with System Manager signed identity certificates. The procedure to create and obtain these certificates is outside the scope of these Application Notes. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 55 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 56 Step 3 - Click on Security  Server/Application Certificates, and verify the System Manager CA certificate is present in the Communication Manager certificate repository. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 56 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 57: Configure Avaya Session Border Controller For Enterprise Release 7.2

    7. Configure Avaya Session Border Controller for Enterprise Release 7.2 These Application Notes assume that the installation of the Avaya SBCE and the assignment of all IP addresses have already been completed, including the management IP address. Consult [10] and [11] for additional information.
  • Page 58: System Management - Status

    Step 1 - Select System Management and verify that the Status column says Commissioned. If not, contact your Avaya representative. Note – Certain Avaya SBCE configuration changes require that the underlying application be restarted. To do so, click on Restart Application shown below.
  • Page 59: Tls Management

    Application Notes. In the reference configuration, TLS transport is used for the communication between Session Manager and Avaya SBCE. The following procedures show how to create the client and server profiles.
  • Page 60: Server Profiles

    Step 2 - Accept default values for the next screen (not shown) and click Finish. The following screen shows the completed TLS Server Profile form: DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 60 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 61: Client Profiles

     Verification Depth: enter 1.  Click Next. Step 2 - Accept default values for the next screen (not shown) and click Finish. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 61 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 62: Global Profiles

    Manager. Step 1 - Select Global Profiles  Server Interworking from the left-hand menu. Step 2 - Select the pre-defined avaya-ru profile and click the Clone button. Step 3 - Enter profile name: (e.g., Enterprise Interwork), and click Finish. DDT; Reviewed: Solution &...
  • Page 63 Step 5 - The General screen will open.  Check T38 Support.  All other options can be left with default values.  Click Finish. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 63 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 64: Server Interworking - Verizon

    Step 3 - The SIP Timers and Privacy screens will open (not shown), accept default values for these screens by clicking Next. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 64 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 65  In the Record Routes field, check Both Sides.  All other options can be left as default.  Click Finish. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 65 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 66: Signaling Manipulation

    Note – Use of the Signaling Manipulation scripts require higher processing requirements on the Avaya SBCE. Therefore, this method of header manipulation should only be used in cases where the use of Signaling Rules or Interworking Profiles does not meet the desired result. Refer to [10] for information on the Avaya SBCE scripting language.
  • Page 67: Server Configuration - Session Manager

    7.3.4 Server Configuration – Session Manager This section defines the Server Configuration for the Avaya SBCE connection to Session Manager. Step 1 - Select Global Profiles  Server Configuration from the left-hand menu. Step 2 - Select Add Profile and the Profile Name window will open. Enter a Profile Name (e.g., EnterpriseCallServer) and click Next.
  • Page 68: Server Configuration - Verizon

    Repeat the steps in Section 7.3.4, with the following changes, to create a Server Configuration for the Avaya SBCE connection to Verizon. Step 1 - Select Add and enter a Profile Name (e.g., Verizon IPCC) and select Next (not shown).
  • Page 69: Routing - To Session Manager

    (Session Manager IP address). Also note that the Transport field is grayed out.  Click on Finish. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 69 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 70: Routing - To Verizon

     Server Configuration = Verizon IPCC (from Section 7.3.5).  Next Hop Address: select 172.30.205.55:5072 (UDP). Step 3 - Click Finish. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 70 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 71: Topology Hiding - Enterprise Side

    Step 4 - Populate the fields as shown below, and click Finish. Note that avayalab.com is the domain used by the CPE (see Sections 5.1, 6.7, and 6.8). DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 71 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 72: Domain Policies

    7.3.9 Topology Hiding – Verizon Side Repeat the steps in Section 7.3.8, with the following changes, to create a Topology Hiding Profile for the Avaya SBCE connection to Verizon.  Enter a Profile Name (e.g., Vz IPCC th profile).  Overwrite the headers as shown below with the FQDNs known by Verizon.
  • Page 73: Media Rules

    Step 1 - Select Domain Policies  Media Rules from the left-hand side menu (not shown). Step 2 - From the Media Rules menu, select the avaya-low-med-enc rule. Step 3 - Select Clone button (not shown), and the Clone Rule window will open.
  • Page 74 7.4.2.2 Verizon – Media Rule Repeat the steps in Section 7.4.2.1, with the following changes, to create a Media Rule for Verizon. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 74 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 75: Signaling Rules

     Verify that Enabled is selected.  Select DCSP  Select Value = EF Step 5 - Click Finish. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 75 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 76: Endpoint Policy Groups - Enterprise Connection

     Media Rule: enterprise med rule (created in Section 7.4.2)  Security Rule: default-low  Signaling Rule: enterprise sig rule (created in Section 7.4.3.1) DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 76 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 77: Endpoint Policy Groups - Verizon Connection

     Media Rule: Vz SIPTrk Med Rule (created in Section 7.4.2.2)  Signaling Rule: Vz SIPTrk Sig Rule (created in Section 7.4.3.2) Step 2 - Select Finish (not shown). DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 77 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 78: Device Specific Settings

    These values are normally specified during installation. These can be modified by selecting Edit; however, some of these values may not be changed if associated provisioning is in use. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 78 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 79: Media Interfaces

    7.5.2 Media Interfaces The Media Interface screen is where the SIP media ports are defined. Avaya SBCE will send SIP media on the defined ports. Create a SIP Media Interface for both the inside and outside IP interfaces. Step 1 - Select Device Specific Settings from the menu on the left-hand side.
  • Page 80: Signaling Interface

    7.5.3 Signaling Interface The Signaling Interface screen is where the SIP signaling ports are defined. Avaya SBCE will listen for SIP requests on the defined ports. Create a Signaling Interface for both the inside and outside IP interfaces. Step 1 - Select Device Specific Settings from the menu on the left-hand side.
  • Page 81: Server Flows - For Session Manager

     Topology Hiding Profile: Enterprise-Topology (Section 7.3.8).  Let other values default. Step 4 - Click Finish (not shown). DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 81 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 82: Server Flows - For Verizon

     End Point Policy Group: Vz-policy-group (Section 7.4.5).  Routing Profile: route to SM (Section 7.3.6).  Topology Hiding Profile: Vz IPCC th profile (Section 7.3.9). DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 82 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 83: Verizon Business Ipcc Services Suite Configuration

    Verizon Business sales representative. The reference configuration described in these Application Notes was located in the Avaya Solutions and Interoperability Test Lab. Access to the Verizon Business IPCC Services suite was via a Verizon Private IP (PIP) T1 connection. Verizon Business provided all of the necessary service provisioning.
  • Page 84: Verification Steps

    This section illustrates verifications from Communication Manager. 9.1.1 Example Incoming Call from PSTN via Verizon IPCC to Telephone Incoming PSTN calls arrive from Verizon at Avaya SBCE, which sends the call to Session Manager. Session Manager sends the call to Communication Manager. On Communication Manager, the incoming call arrives via signaling group 2 and trunk group 2.
  • Page 85 Note the signaling using port 5071 between Communication Manager and Session Manager. Note the media is “ip-direct” from the IP Telephone (10.64.91.157) to the inside IP address of Avaya SBCE (10.64.91.50) using codec G.729. status trunk 2/1 Page...
  • Page 86: Example Incoming Call Referred Via Call Vector To Pstn Destination

    001V9 ext 11006 cid 0x62d 12:28:17 Connected party uses public-unknown-numbering 12:28:17 SIP<ACK sips:+18668523221@10.64.91.65:5071;transport=tls SI 12:28:17 SIP<P/2.0 <continued on next page> DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 86 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 87 0002/005 T00015 in-service/idle 0002/006 T00016 in-service/idle 0002/007 T00017 in-service/idle 0002/008 T00018 in-service/idle 0002/009 T00019 in-service/idle 0002/010 T00020 in-service/idle DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 87 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 88: Avaya Aura® System Manager And Avaya Aura® Session Manager Verifications88

    9.2. Avaya Aura® System Manager and Avaya Aura® Session Manager Verifications This section contains verification steps that may be performed using System Manager for Session Manager. Log in to System Manager. Expand Elements  Session Manager  System Status  SIP Entity Monitoring. A screen such as the following is displayed.
  • Page 89: Avaya Session Border Controller For Enterprise Verification

    9.3. Avaya Session Border Controller for Enterprise Verification This section illustrates verifications from Avaya Session Border Controller for Enterprise. 9.3.1 Welcome Screen The welcome screen shows alarms, incidents, and the status of all managed Avaya SBCEs at a glance. 9.3.2 Alarms A list of the most recent alarms can be found under the Alarm tab on the top left bar.
  • Page 90 Incident Viewer: Further Information can be obtained by clicking on an incident in the incident viewer. DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 90 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 91: Diagnostics

    The full diagnostics check will verify the link of each interface, and ping the configured next-hop gateways and DNS servers. Click on Diagnostics on the top bar, select the Avaya SBCE from the list of devices and then click “Start Diagnostics”.
  • Page 92: Conclusion

    10. Conclusion As illustrated in these Application Notes, Avaya Aura® Communication Manager 7.1, Avaya Aura® Session Manager 7.1, and Avaya Session Border Controller for Enterprise 7.2 can be configured to interoperate successfully with Verizon Business IP Contact Center Services suite.
  • Page 93: References

    [6] Administering Avaya Aura® Communication Manager, Release 7.1.1, Issue 2, August 2017 [7] Administering Avaya G450 Branch Gateway, Release 7.1, Issue 1, May 2017 [8] Deploying and Updating Avaya Aura® Media Server Appliance, Release 7.8, Issue 3, August 2017 [9] Quick Start Guide to Using the Avaya Aura® Media Server with Avaya Aura®...
  • Page 94: Verizon Business

    The following documents may be obtained by contacting a Verizon Business Account Representative.  Retail VoIP Interoperability Test Plan  Network Interface Specification Retail VoIP Trunk Interface (for non-registering devices) DDT; Reviewed: Solution & Interoperability Test Lab Application Notes 94 of 95 SPOC 10/18/2017 ©2017 Avaya Inc. All Rights Reserved. CM71SM71-VzIPCC...
  • Page 95 2017 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.

This manual is also suitable for:

Session border controller for enterprise 7.2

Table of Contents