Note: Parts of this guide still refer to Nexmo. Vonage acquired Nexmo in June 2016. Visit the Vonage Knowledge Base to obtain the current list of IP addresses.
- 1. Introduction
2. SIP Trunking Network Components
- 2.1 Network Components
- 3.1.1 Features Supported
- 3.1.2 Features Not Supported by PBX
- 3.1.3 Caveats and Limitations
- 4.1 IP Address Worksheet
- 4.2 Configuring Avaya Aura Communication Manager
- 4.2.1 Licenses
- 4.2.2 System Features
- 4.2.3 IP Node Names
- 4.2.4 IP Codecs
- 4.2.5 IP Network Region
- 4.2.6 Signaling Group
- 4.2.7 Trunk Group
- 4.2.8 Route Pattern
- 4.2.9 Dialing Pattern and Feature Code
- 4.2.10 Call Routing
- 4.2.11 Caller ID
- 4.2.12 Avaya Aura Extensions
- 4.3 Configuring Avaya Aura Session Manager
- 4.3.1 Add Adaptations
- 4.3.2 SIP Entities
- 4.3.3 Routing Policies
- 4.3.4 Dial Patterns
- 4.3.5 SIP Extension
- 4.4 Configuring Avaya Session Border Controller for Enterprise
- 4.4.1 Global Profile
- 4.4.2 Domain Policies
- 4.4.3 Device Specific Settings
- 4.5 Avaya Modular Messaging
- 4.6 Nexmo Configuration
- 4.6.1 Configure Numbers in Nexmo Account
This document is intended for the SIP trunk customer’s technical staff and Value Added Retailer (VAR) having installation and operational responsibilities. This configuration guide provides steps for configuring Avaya Aura 188.8.131.52.631804 and Avaya SBCe 6.3.7-01-12611 to Nexmo SIP Trunking services.
The network for the SIP trunk reference configuration is illustrated below and is representative of an Avaya Aura and Avaya SBCe configuration to Nexmo SIP trunking.
|Avaya MM||5.2-11.0||Avaya Voicemail|
|Cisco IP Phone||
||This Cisco IP Phone is the PSTN test device|
- Incoming and outgoing off-net calls using G711ULAW & G711ALAW voice codecs
- Calling Line (number) Identification Presentation
- Calling Line (number) Identification Restriction
- Call hold and resume
- Call transfer (unattended and attended)
- Call Conference
- Call forward (all, no answer)
- DTMF relay both directions (RFC2833)
- Media flow-through on Avaya SBCe
- Session refresh is always done by Avaya Aura. The issue does not impact the calls.
The specific values listed in the table below and in subsequent sections are used in the lab configuration described in this document, and are for illustrative purposes only. The customer must obtain and use the values for your deployment.
|Component||Lab Value||Customer Value|
|LAN IP Address||
|LAN Subnet Mask||
|WAN IP Address||
|WAN Subnet Mask||
|System IP Address||
This section describes the Avaya Aura Communication Manager configuration necessary to support connectivity to Avaya SBCe. A SIP trunk is established between Communication Manager and Session Manager for use by signaling traffic to and from Nexmo via Avaya SBCe. It is assumed that the general installation of Communication Manager, the Avaya G430 Media Gateway and Session Manager has been previously completed.
The Avaya Aura Communication Manager configuration was performed using System Access Terminal (SAT) via Putty.
In order to connect to Nexmo, Avaya Aura Communication Manager needs to have enough SIP
trunk licenses. Use the
display system-parameters customer-options command to verify the
available SIP Trunk licenses
change system-parameters features command and ensure Trunk to Trunk Transfer is set
display node-names IP command to verify that node names have been properly defined
for Communication Manager (
procr) and Session Manager (AASM in this test). These node
names will be needed for configuring the Signaling Group later.
ip-codec-set command is used for assigning the proper codecs. For this setup,
ip-codec-set 1 is used.
For this test, IP Network region 3 was created using the change
ip-network-region 1 command
add signaling-group x command to create a signaling group 2 between Communication
Manager and Session Manager for SIP trunk calls.
add trunk-group x command to create trunk groups for the associated signaling group,
trunk group 2 is associated with Signaling group 2 for SIP trunk between CM and SM.
- The Numbering Format is set to Public. Outbound calls to Nexmo uses this trunk and uses the Public Numbering table to send the calling party number.
- Send Diversion Header is enabled to send the diversion information for voice mail.
change route-pattern 2 command to add routing preference for SIP trunk to Session
- This route is associated with trunk group 2
change dialplan analysis and
change feature-access-codes commands
- ARS access code is set to 9
change ars analysis command is used for outbound PSTN call routing. 121 is shown as an
example setup for this test.
- Route pattern 2 is used for PSTN call routing.
change private-numbering 2 command is used to assign the Caller ID for 4 digit Avaya Aura
- Trunk group number 2 is used.
Create a SIP extension as shown below.
- Enter station extension.
- Application: Type
- Trunk Selection: Type
The Avaya Aura Session Manager configuration utilizes Avaya Aura System Manager. The Avaya
Aura System Manager Web login screen is accessed via
https://IP Address/FQDN. Use admin
as User ID and input associated password, and then click Log on. It is assumed that the
Domain, Location and Endpoint for Session Manager have been previously configured.
Navigate to Home > Elements > Routing
Modifications to the SIP messaging within the Session Manager can be made in the Adaptions module. The idea here is to create an adaptation entity, identified by its Name, and then assign it to a SIP Entity.
Navigate to Routing > Adaptations > New
The following adaption rules are provisioned in the "Module parameter" field:
fromto =true: If set to true, then adaptation modifies
To headers of the message.
- An adaptation is created under the Digit Conversion for Outgoing Calls from SM to cause SM to insert the + sign in the From and To headers on SM-originated calls routed to Avaya SBCe.
- Add the AvayaSBC Adaption created earlier, to the SIP Entity
- The link between the SM and the Avaya sBCe was configured as trusted using TCP protocol and port 5060
- The link between the Avaya SM and the CM was configured as trusted using TCP protocol and port 5060.
- The link between the Avaya SM and the Avaya MM was configured as trusted using TCP protocol and port 5060
Navigate to Routing > Routing Policies > New
Create a routing policy to Avaya SBCe as shown below.
Create a routing policy to Avaya CM as shown below
Create a routing policy to Avaya MM as shown below
- Create a dial pattern to route the call to PSTN via Avaya SBCe and link the Routing Policy to Avaya SBCe as shown above.
- Create a dial pattern to route the call to Avaya Aura and link the Routing Policy to Avaya CM as shown above
- Create a dial pattern to route the call to Avaya MM and link the Routing Policy to Avaya MM as shown above
Create a SIP user profile as shown below.
Navigate to User Management> Endpoints > Manage Users
- Log into Avaya Session Border Controller for Enterprise (SBCE) web interface by typing "https://X.X.X.X/sbc".
- Enter the assigned Username and Password
- Click Log In
Navigate to System Management > Global Profiles > Server Interworking. Create a clone named
AASM of predefined Interworking Profile
avaya-ru as shown below.
Create a Serving Interworking profile for Avaya SM as shown below.
Create a Serving Interworking profile for Nexmo as shown below.
Navigate to System Management > Global Profiles > Routing
Creating a Routing profile for Avaya Session Manager as shown below.
Creating a Routing profile for Nexmo as shown below.
Navigate to System Management > Global Profiles > Server Configuration
Create a Server configuration profile for Avaya Session Manager as shown below.
Create a Server configuration profile for Nexmo as shown below.
Navigate to System Management > Global Profiles > Topology Hiding
Creating a Topology hiding profile for Avaya Session Manager as shown below
Signaling Rules define the actions to be taken (Allow, Block, Block with Response, etc.) for each type of SIP-specific signaling request and response message.
Headers such as P-Location, P-Charging-Vector and others are sent in SIP messages from Session Manager to the Avaya SBCe for egress to the Nexmo.
A Signaling Rule was created, to later be applied in the direction of the enterprise to block unwanted headers coming from Session Manager from being propagated to Nexmo.
End Point Policy group "Avaya SM" is created as shown below
Navigate to System Management > Device Specific Settings > Media Interface. Create Internal and External Media Interface as shown below.
Navigate to System Management > Device Specific Settings > Signaling Interface. Create Internal and External Signaling Interface as shown below.
Navigate to System Management > Device Specific Settings > End Point Flows. Select the Server Flows tab and click Add. Create a Server flow for Avaya Session Manager as shown below.
Select the Server Flows tab and click Add. Create a Server flow for Nexmo as shown below.
This section describes the steps for configuring the Avaya Modular Messaging to inter-operate with Avaya Aura Session Manager via SIP trunking.
Navigate to Messaging Administration > Networked Machines to configure Modular Messaging Server parameters as shown below.
Navigate to Messaging Administration > Subscriber Management. Configure a subscriber for the Messaging server as shown below.
Login to the Nexmo account using the credentials provided at the time of registration. A Key and Secret will be displayed on the dashboard and this can be used as the username and password for Registration SIP Trunks.
In order to provide the URL to which the call has to be routed from Nexmo, navigate to the Numbers tab
Click Edit against each number as shown below
A pop-up will be displayed
Select the " Forward to " and provide the URL to which the calls route
Click Update to save the changes