Search

Page tree
Skip to end of metadata
Go to start of metadata

 

Table of Contents

 

Document Overview

This document provides a configuration guide for Ribbon Session Border Controller Edge Series (SBC) when connecting to Avaya Session Manager 7 (SM7) and Avaya Communication Manager (CM7).

Introduction

The interoperability compliance testing focuses on verifying inbound and outbound call flows between Ribbon SBC Edge and Avaya Session Manager 7 (SM7) and Avaya Communication Manager (CM7) .

Audience

 This technical document is intended for telecommunication engineers with the purpose of configuring the Ribbon SBC Edge series aspects of the AT&T Flex Reach SIP trunk group with the Avaya SM7 and CM7This configuration requires the navigation of a third-party server and the Ribbon SBC Web browser user interface, Embedded Management Application (EMA). Understanding the basic concepts for IP/Routing, SIP, RTP, and TLS are also required for completing the configuration and any necessary troubleshooting.

Requirements

The following equipment and software were used for the sample configuration (see Topology):

 

 

Equipment

Software Version

Ribbon Networks

Ribbon SBC Edge (2000)

 

 

 

7.0.0b476

Third-party Equipment

Avaya Communication Manager 7.0R017x.00.0.441.0 
 Avaya Session Manager 7.07.0.0.0.700007
 Avaya 9608 IP Deskphone

6.3037

Reference Configuration

The following reference configuration illustrates the connectivity between a third-party and the Ribbon SBC Edge..

Figure : Topology

 

Support

For any questions regarding this document or the content herein, please contact your maintenance and support provider.

 

Third-Party Product Features

The testing was executed with the AT&T test plan, and the following features were tested:

  • Basic originated and terminated calls 
  • Calling Number presentation
  • Hold and Resume
  • Voice Mail
  • Conference Call
  • Call Transfer
  • Call Forwarding
  • Auto Attendant
  • Meet-Meet Conference
  • AT&T IP Teleconferencing
  • N11 Calls
  • FAX
  • DTMF
  • Network Based Enhanced Features

Not Supported Features

  • cRTP
  • SBC does not send SIP with SDP without p-time
  • SBC does not support network based transfer with SIP Refer method


Verify License

No special licensing required.

 

Avaya SM 7 Configuration

This section includes the following new configurations :

  1. Domain
  2. Location
  3. SIP Entity
  4. Entity Link
  5. Routing Policy
  6. Dial Pattern

1. Domain

Select Home > Routing > Domains

Figure : Domain

 

2. Location

Select Home > Routing > Locations

Figure : Location for CM

 

 

Figure : Location for SBC

 

3. SIP Entity

Select Home > Routing > SIP Entities

Figure : SIP Entity for CM

Figure : SIP Entity for SBC

 

Select Home > Routing > Entity Links

Figure : Entity Link for CM

Figure : Entity Link for SBC

5. Routing Policy

Select Home > Routing > Routing Policies

Figure : Route Policy for CM

Figure : Route Policy for SBC

 

6. Dial Pattern

Select Home > Routing > Dial Patterns

Note

Use this procedure to create any Dial Pattern configuration.

Figure : Dial Pattern for CM

Figure : Dial Pattern for SBC

 

Avaya CM 7 Configuration

 This section includes the following new configurations:

  1. Node Name
  2. Signaling Group
  3. Trunk Group
  4. Route Pattern
  5. ARS Digit Analysis Table
  6. Station
  7. Vector Directory Number
  8. Vector


1. Node Name

  1. Using the Site Administration, log into Avaya CM 6.0.
  2. Type  change node-names ip in the command line.  
  3. Press the Down Arrow key to a blank line and add the appropriate information.
  4. Press F3 to save when complete.

Figure : Node Name


2. Signaling Group

  1. Using the Site Administration, log into Avaya CM 7.0.
  2. Type add signaling-group next in the command line.

    Note

    The "next" switch will auto-generate the next available group number for the Signaling Group and is the most efficient method to use when creating a new Signaling Group.


  3. Add the appropriate information and press F3 to save when complete. For more details, refer to Avaya CM 7.0 guide.

Figure : Signaling Group

 

3. Trunk Group

  1. Using the Site Administration, log into Avaya CM 7.0.
  2. Type add trunk-group next in the command line.
  3. Add the appropriate information and press F3 to save when complete. For more details, refer to Avaya CM 7.0 guide.

Figure : Trunk Group

 

4. Route Pattern

  1. Using Site Administration, log into Avaya CM 7.0.
  2. Type list route-pattern in the command line to determine the next available route pattern.
  3. Identify the route pattern number you are going to use and then press F1 to exit the current operation.
  4. Type change route-pattern and then enter the available route pattern number. Add the appropriate information and press F3 to save when complete.

Figure : Route Pattern


5. ARS Analysis Table

  1. Using the Site Administration, log into Avaya CM 7.0.
  2. Type change ars analysis (dialed number) to add or change the called number handling.

Figure : ARS Digit Analysis Table


6. Station

  1. Using the Site Administration, log into Avaya CM 7.0.
  2. Type add station next to add a new station.

Figure : Station


7. Vector Directory Number

  1. Using the Site Administration, log into Avaya CM 7.0.
  2. Type add vdn <extension> to add a new vector directory number.

Figure : Vector Directory Number for Auto Attendant

Figure : Vector Directory Number for Meet-Me Conference

 

8. Vector

  1. Using the Site Administration, log into Avaya CM 7.0.
  2. Type add vector next to add a new vector.

Figure : Vector for Auto Attendant

Figure : Vector for Meet-Me Conference

 

Ribbon SBC Edge Series Configuration

The following steps provide an example of how to configure Ribbon SBC Edge.

  1. Easy Configuration Wizard
  2. SIP Profile
  3. Q.850 Cause Code to SIP Override Tables
  4. Tone Table
  5. Media Profile
  6. Media System Configuration
  7. Media List
  8. Message Manipulation
  9. SIP Server
  10. Signaling Group
  11. Transformation
  12. Call Routing Table  


1. Easy Configuration Wizard

The SBC interface includes an Easy Configuration Wizard, which enables end users to quickly deploy SBC.  Based on a template, you can configure items such as endpoint (define user and provider), routing (routing configuration applied to scenario), and country (tone table parameters and emergency numbers for a particular country).

Figure : Easy Configuration Wizard

 

 

2. SIP Profile

SIP Profiles control how the Ribbon SBC Edge communicates with SIP devices. The SIP Profiles control characteristics such as

  • Session timers
  • SIP Header customization
  • SIP timers
  • MIME payloads
  • Option tags

To configure the SIP Profiles, select Settings > SIP > SIP Profiles.

Figure : AT&T-IPFR: Avaya SIP Profile

Figure : AT&T-IPFR: ATT SIP Profile

 

3. Q.850 Cause Code to SIP Override Table

By default, the SBC Edge uses RFC 3398 cause code mappings. Q.850 Cause Code to SIP Override Table allows you to define other mappings for cause codes.

To configure the Q.850 Cause Code to SIP Override Table, select Q.850 Cause Code to SIP Override Tables.

Figure : Q.850 Cause Code to SIP Override Table AT&T-IPFR: ATT

 

4. Tone Tables

Tone tables allow the SBC Edge administrator to customize the tones a user hears when placing a call. You can modify the tone to match your local PSTN or PBX. The default tone table configures the following categories with the United States' values:

  • Ringback
  • Dial
  • Busy
  • Congestion
  • Call Waiting
  • Disconnect
  • Confirmation

To configure the Tone Tables, select Settings > Tone Tables.

Figure : Tone Table AT&T-IPFR: United States

 

5. Media Profile

Media profiles specify the individual voice and fax compression codecs, and their associated settings for inclusion into a Media list. Different codecs provide varying levels of compression, which enables the reduction of bandwidth requirements at the expense of voice quality. 

To access the Media Profile, select Settings > Media > Media Profiles.

Figure : AT&T-IPFR (Avaya)

 

Figure : AT&T-IPFR (ATT)

 

6. Media System Configuration

The Media System Configuration contains systemwide settings for the Media System. To configure the Media System, set the number of RTP/RTCP port pairs and the starting port.

To access the Media Profile, select Settings > Media > Media System Configuration.

Figure : Media System Configuration

7. Media List

The Media List shows the selected voice and fax compression codecs and their associated settings.

To access Media lists, select Settings > Media > Media List.  

Figure : AT&T-IPFR: Avaya List


Figure : AT&T-IPFR: ATT Trunk List


8. Message Manipulation

Condition rules are rules that apply to a specific component of a message (for example, diversion.uri.host, from.uri.host, and such) with the value in the Match Type list box. The value is matched against a literal value, token, or REGEX.

To configure Message Manipulation, select Settings > SIP > Message Manipulation > Condition Rule Table. 

The rule on the next figure changes a host part for the PAID (P-Asserted-Identity) header for all outbound calls to ATT SIP Trunk with an IP address of public interface.

Figure : SMM TO ATT


9. SIP Server

The SIP Server tables contain information about the SIP devices connected to the Ribbon SBC Edge. The table entries provide information about the IP addresses, ports, and protocols used to communicate with each SIP server. The entries also contain links to counters that are useful for troubleshooting.

To configure the SIP Server, select Settings > SIP > SIP Server Tables.

Figure : AT&T-IPFR: Avaya CM

Figure : AT&T-IPFR: Border Element

Figure : Fax-TenorGW


10. Signaling Group

Signaling Groups allow telephony channels to be grouped together for routing and shared configuration. The Signaling Groups are the entity to which calls are routed and where the Call Routes are selected.  In the case of SIP, Signaling Groups will specify protocol settings and link to server, media, and mapping tables.

To configure Signaling Groups, select Settings > Signaling Groups.

Figure : AT&T-IPFR: Avaya CM

 

Figure : AT&T-IPFR: ATT Border Element

 

Figure : Fax-TenorGW

 
 

11. Transformation

Transformation tables facilitate the conversion of names, numbers, and other fields when routing a call. For example, transformation table converts a public PSTN number into a private extension number or a SIP address (URI). Every entry in a Call Routing table requires Transformation tables, which are sequentially selected. In addition, Transformation tables are configurable as a reusable pool that action sets can reference.

To configure the Transformation table, select Settings > Transformation.

Figure : AT&T-IPFR: From ATT


Figure : AT&T-IPFR: From Avaya CM

Figure : From Fax-TenorGW


Figure : From ATT to FAX

 

12. Call Routing Table

Call Routing allows calls to be carried between Signaling Groups, which allows calls to be carried between ports and between protocols (for example, ISDN to SIP). Routes are defined by Call Routing tables, which allows for flexible configuration of calls that are carried, as well as how the calls are translated. These tables are one of the central connection points of the system linking Transformation tables, Message translations, Cause Code Reroutes, Media lists, and the three types of Signaling Groups: ISDN, SIP, and CAS.

To configure the Call Routing Table, select Settings > Call Routing Table.

Figure : AT&T-IPFR: From Avaya CM


Figure : AT&T-IPFR: From ATT


Figure : From Fax-TenorGW



Conclusion

These Application Notes describe the configuration steps required for Ribbon SBC Edge Series to successfully interoperate with AT&T IP Flex Reach SIP Trunk. All feature and serviceability test cases were completed.