Avaya Configuring Aura User Manual

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

1 of 47

AAM61SM61BCM60

These Application Notes describe a sample configuration of Avaya Aura® Messaging 6.1 as a voice mail solution for Avaya Business Communication Manager 450 6.0. In this configuration Avaya Aura® Messaging and Business Communication Manager 450 are connected to Avaya Aura® Session Manager R6.1 over SIP trunks. Avaya Aura® Session Manager provides SIP proxy/routing functionality, routing SIP sessions across a TCP/IP network with centralized routing policies. Avaya Aura® Messaging supports Business Communication Manager 450 endpoints for voice messaging features such as greeting menu, user mailbox services and transfer functionalities.

These Application Notes provide information for the setup, configuration, and verification of the call flows tested for this solution.

Avaya Solution & Interoperability Test Lab

Configuring Avaya Aura® Messaging 6.1 as a Voice Messaging Solution for Avaya Business Communication Manager 450 Release 6.0 with SIP trunking through Avaya Aura® Session Manager 6.1 – Issue 1.0

Abstract

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

2 of 47

AAM61SM61BCM60

1. Introduction

These Application Notes describe a sample configuration of Avaya Aura® Messaging 6.1 as a voice mail solution for Avaya Business Communication Manager (BCM) 450 6.0. In this configuration Avaya Aura® Messaging and Avaya BCM are connected to Avaya Aura® Session Manager over SIP trunks. Avaya Aura® Session Manager provides SIP proxy/routing functionality, routing SIP sessions across a TCP/IP network with centralized routing policies. Avaya Aura® Messaging provides unified communications features such as greeting menu, user mailbox services and transfer functionalities. Avaya Aura® Communication Manager is setup as an emulated PSTN connected to Avaya BCM through T1 connection.

2. Interoperability Testing and Test Result

Interoperability was tested between Avaya Business Communication Manager and Avaya Aura® Messaging with SIP trunking through Avaya Aura® Session Manager.

2.1. Interoperability Compliance Testing

Interoperability testing was executed between a variety of Avaya telephones such as Digital, UNIStim registered to Business Communication Manager, Avaya SIP phones registered to Session Manager and Avaya H323, Digital phones registered to Communication Manager. The focus was to verify call and messaging functionality between Communication Manager, Business Communication Manager and Avaya Aura® Messaging in a SIP network with trunking through Session Manager.

The following Avaya Aura® Messaging capabilities were covered:

No Answer Personal Greetings Bypass Greetings Message Waiting Indication Reply Call Forwarding Multiple Call Forwarding Call Transfer Simultaneous Calls Personal Operator Personal Operator – No Answer Auto Attendant Auto Attendant – No Answer Call to Forward All (forward to messaging access number) endpoint. Call to Busy endpoint (messaging access number is set if this endpoint busy) All the call

is forwarded to pilot number.

The following Avaya Aura® Messaging capabilities were not in scope for this testing:

Call Sender Reach Me Notify Me

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

3 of 47

AAM61SM61BCM60

2.2. Test Results and Observations

Interoperability testing of Avaya Aura® Messaging 6.1 Single Server as a voice mail solution for Avaya Business Communication Manager with SIP Trunking through Avaya Aura® Session Manager R6.1 was successful.

3. Reference Configuration

Figure 1 below illustrates the configuration used in these Application Notes. The sample configuration shows an enterprise with Avaya BCM communicating with the Avaya Aura® Messaging via a SIP trunk. The Avaya BCM has an analog, a digital and an IP Telephone connected as endpoints.

For security purposes public IP addresses have been masked out or altered in this document.

Figure 1: Network Configuration

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

4 of 47

AAM61SM61BCM60

4. Equipment and Software Validated

Equipment

Software

S8800 Server

Avaya Aura® Messaging Release 6.1

S8800 Server

Avaya Aura® Session Manager Release 6.1

S8800 Server

Avaya Aura® System Manager Release 6.1 G450 with S8300D, emulated PSTN

Avaya Aura® Communication 6.0 PRI, Digital Trunk Interface Module

Business Communication Manager 450

Avaya BCM450 R6 SU 011-201205 2 – Avaya 1140E IP Telephone (SIP)

Firmware Version: 0625C8J

2- Digital Phones T7316

n/a

2 – Analog Phones

n/a

The following equipment and software were used for the sample configuration provided:

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

5 of 47

AAM61SM61BCM60

5. Configure Avaya Business Communication Manager with SIP Trunking to Avaya Aura® Session Manager

This section describes the procedure for setting up Avaya BCM. The following administration activities will be described:

Configure Proxy for Private SIP Trunking Configure the Global setting for SIP Trunking Configure general info for IP Trunks Configure the routing Configure the destination code Configure the private network for dialing plan Configuring the Public network for the dialing plan Configure Target Lines Assign a target line to a selected set Configure Active Sets

The highlights in the following screens indicate the values used during the compliance test. Default values may be used for all other fields. Please keep in mind that the values used in this guide may be unique to the example shown. User will have to use values unique to their site, where this solution is being deployed (e.g., site’s IP address, extension numbers, etc).

Avaya BCM configurations can be performed through Business Element Management only.

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

6 of 47

AAM61SM61BCM60

5.1. SIP Trunking Configuration

This section explains the steps to configure a SIP trunk routing entry that will access the Messaging via Session Manager from the Avaya BCM.

5.1.1. Configure Proxy for Private SIP Trunking

After logging into the BCM element manager, configure a private proxy for the SIP trunking by selecting, Configuration  Resources  IP Trunks  SIP Trunking

Select the tab Private  Proxy to add a proxy as shown in figure below:

Domain: the defined domain that the Avaya Aura® Messaging and Avaya Aura®

Session Manager system is assigned to. During compliance test bvwdev.com domain is used.

IP Address: is Session Manager’s IP.

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

7 of 47

AAM61SM61BCM60

5.1.2. Configure the Global settings for SIP Trunking:

Navigate to Configuration  Resources  IP Trunks  SIP Trunking

Select the tab Global Settings as shown in figure below:

Local Domain: is the defined domain that the AAM and ASM system is assigned to. Call Signaling port: 5060

5.2. IP Trunks Configuration

This section describes how to configure the general settings for IP trunk.

5.2.1. General IP trunk settings:

Navigate to Configuration  Resources  IP Trunks  General IP Trunk Settings Setup the general information for the IP trunk as below:

Forward redirected OLI: First Redirect. Remote capability MWI: checked Send name display: checked.

Note: for detail of these setting please refer to Avaya BCM documentation listed in reference Section 12

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

8 of 47

AAM61SM61BCM60

5.3. Dialing Plan Configuration

This section describes how to configure the dialing plan, routes and pool that will be used by the Avaya BCM to communicate with the Avaya Aura Messaging.

5.3.1. Configure the routing:

Navigate to Configuration  Telephony  Dialing Plan  Routing In Routes tab to add a new route by click on the Add button. Enter the route number 001 and click OK when Done. Double click on new created Route and assign value to the route as below:

Use Pool: BlocA. DN Type: Private

The rest of the values leave them as default.

5.3.2. Configure the destination code:

Navigate to Configuration  Telephony  Dialing Plan  Routing In Destination Codes tab add a destination code as shown in figure below:

Destination Code: 399. The destination code 399 is chosen because the AAM pilot

number used in the example is 39990.

Normal Route: 001 Absorbed Length: 0

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

9 of 47

AAM61SM61BCM60

5.3.3. Configure the dialing plan private network:

Configuration  Telephony  Dialing Plan  Private Network

Configure the private network as shown in figure below:

Private Received number length: 5. Private network type: CDP. Private DN length: 5

5.4. Target Lines Configuration

This section describes how to configure target lines which will be assigned to telephones that will be used as endpoints connected to the BCM.

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

10 of 47

AAM61SM61BCM60

5.4.1. Configure a target line to a selected set:

Navigate to Configuration  Telephony  Lines  Target Lines In the Target Lines screen, select a Line and enter DN to selected Line For example in the figure shown below:

Line: 413 has been selected. DN: 22235 has been assigned by clicking on the Add button under the Assigned DNs tab.

Note: Add unique set DN to one Target line. Require one line assignment for every telephone device in the system.

Also for the assigned set to generate busy tone while it is busy. Select Preferences tab:

If Busy field: Busy tone has to be selected as shown in figure below.

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

11 of 47

AAM61SM61BCM60

5.5. Active Sets Configuration

This section describes the steps to configure the sets that have been assigned to a line as explained in Section 5.4

5.5.1. Configure the Active sets:

Select Configuration  Telephony  Sets  Active Sets Example configuration for Line Access tab of selected active set:

Select DN: 22235 Fwd No Answer: 39990 Fwd Busy: 39990

Note: 39990 is the pilot number of Avaya Messaging. Example configuration for Line Assignment tab of selected active set:

Vmsg Set: checked so that voice mail can be accessed by the DN 22235 Priv. Received#: 22235 Pub. Received #: 22235.

Figures below show the additional configurations to be done to the selected DN which has to be member of the BlocA pool found in the Line Pool Access tab.

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

12 of 47

AAM61SM61BCM60

In the Capabilities and Preferences tab make sure the following options are selected:

DND on Busy: checked. Allow redirect: checked.

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

13 of 47

AAM61SM61BCM60

6. Configure Avaya Business Manager 450 with PRI trunk to PSTN

6.1. Administer Resources

This section describes how to configure a PRI Trunk on BCM to PSTN.

6.1.1. Administer Application Resource for PRI Trunks

These Application Notes assume that the basic configuration has already been administered. This section describes steps for configuring Application Resource for PRI Trunks on BCM to work with Service Provider system. For further information on Avaya Business Communication Manager 450 configuration, please consult references in Section 12.

Enable the PRI device on Avaya BCM by select Resources  Telephony Resources. Under Configured Device column, select DTM + PRI and then click Enable button if it is not already enable as show in figure below. Configure PRI trunk parameter as highlighted in red box. Others are left as default:

Trunk type: PRI Protocol: NI-2 NSF extension: None. B channel selection: Descending Sequential. Clock source: Internal. CO fail: TIA-547A. Interface levels: ISDN. Framing: ESF. Line config: B8ZS.

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

14 of 47

AAM61SM61BCM60

6.1.2. Routing Settings

This section describes how to configure the dialing plan, routes and pool that will be used by the Avaya BCM to connect to PSTN. Navigate to Telephony  Dialing Plan  Routing. In Routes tab to add a new route to PSTN by click on the Add button. Enter the route number 002 and click OK when Done. Double click on new created Route and assign value to the route as below, other leave as default:

Use Pool: BlocB. DN Type: Private. Service Type: Tie.

6.1.3. Administer Destination Codes

To assign Destination Codes to dial to PSTN via PRI. Perform similar step as shown in section

5.3.2 for with the following information

Destination Code: 4521. Extension on Avaya Communication manager is 52xxx. Digit 4

to let Avaya BCM route the call through route 002

Normal Route: 002. Absorbed Length: 1. Drop the first digit 4.

6.1.4. Administer Telephony Lines

Assign the pool to telephone line by navigate to Telephony  Lines  Active Physical Lines. Double click on a selected line under the Line Type, choose Pool:BlocB in this example as shown below.

PM; Reviewed: SPOC 02/26/2013

Solution & Interoperability Test Lab Application Notes

15 of 47

AAM61SM61BCM60

6.1.5. Administer Telephony Target Lines

Assign a DN: 22234 to an available target line Line: 362. See Section 5.4 for detail procedure.

6.1.6. User/Telephone Sets Configuration for Incoming/Outgoing Call

This section show how to configure telephone sets to specific physical line for incoming/outgoing calls to/from a digital set. Select Telephony  Sets  Active Sets. In the Line Access, select the available digital set which has the Model is T7316/M7310.

Assign Priv. OLI: 22234. This will allow the delivery of the Calling Line Identification Display.

For incoming call: Assign the line that configured in Section 6.1.5 o this phone by click on the Add button in Line Assignment tab. Enter line number, in this example 362 and click OK.

Modify the detail information of the line parameters as values highlighted in red boxes in the below figure:

Caller ID Set: checked. Vmsg Set: checked. Priv. Received #: 22234. Pub. Received #: 22234.

+ 32 hidden pages