Application Notes for Configuring a Survivable Modular … · In the event of a disaster or...

JMC; Reviewed:

SPOC 8/12/2009

Solution & Interoperability Test Lab Application Notes

©2009 Avaya Inc. All Rights Reserved.

1 of 81

SMM-MSS-SIP-AC

Avaya Solution & Interoperability Test Lab

Application Notes for Configuring a Survivable Modular

Messaging Solution with Avaya Message Storage Server and

SIP Integration to Cisco Unified Communications Server

Using AudioCodes Mediant 1000 – Issue 1.0

Abstract

These Application Notes describe the steps required to configure an Avaya Survivable

Modular Messaging solution in a MultiSite environment that utilizes Avaya Message Storage

Server (MSS) incorporating AudioCodes Mediant 1000 for connectivity to Cisco Unified

Communications Manager. The Avaya Survivable Modular Messaging solution is a disaster

recovery solution for failover voicemail service to a Secondary site following an outage at the

Primary Site.

JMC; Reviewed:

SPOC 8/12/2009



2 of 81

SMM-MSS-SIP-AC

Contents 1. Introduction ........................................................................................................................... 4

2. Equipment and Software Validated .................................................................................... 5

3. Configure Avaya Modular Messaging................................................................................. 6 3.1. Configure Primary Avaya Modular Messaging Site ....................................................... 6

3.1.1. MultiSite Configuration........................................................................................... 6

3.1.2. Configuration of Services. ..................................................................................... 11

3.1.3. Configuration of Services. ..................................................................................... 13

3.1.4. Subscriber Creation. ............................................................................................. 15

3.1.5. Backup Avaya MAS ............................................................................................... 16

3.1.6. Backup Avaya MSS Data....................................................................................... 18

3.2. Configure Secondary Avaya Modular Messaging Site ................................................. 20

3.2.1. Restore Avaya MSS. .............................................................................................. 20

3.2.2. Restore Avaya MAS ............................................................................................... 22

3.2.3. Post Avaya MAS Restoration Configuration ......................................................... 24

4. Configure AudioCodes Mediant 1000 Media Gateway ................................................... 26 4.1. Using Configuration File ............................................................................................... 26

4.2. Manual Configuration Changes .................................................................................... 27

4.2.1. Configure Trunk Settings ...................................................................................... 28

4.2.2. Configure SIP General Parameters ...................................................................... 29

4.2.3. Configure Media Security ..................................................................................... 30

4.2.4. Configure Proxy and Registration ........................................................................ 31

4.2.5. Configure Coder .................................................................................................... 32

4.2.6. Configure Digit Collection Setup .......................................................................... 32

4.2.7. Configure SIP Advanced Parameters ................................................................... 33

4.2.8. Configure Trunk Group ......................................................................................... 34

4.2.9. Configure Voice Mail Settings .............................................................................. 34

4.2.10. Configure TDM Bus Settings ................................................................................ 35

4.2.11. Configure DNS ...................................................................................................... 35

4.2.12. Configure Admin Parameters................................................................................ 36

4.3. Reset Gateway ............................................................................................................... 37

5. Configure Cisco 2811 MGCP Gateway ............................................................................. 38 5.1. Log into Gateway .......................................................................................................... 38

5.2. Administer MGCP Protocol .......................................................................................... 39

5.3. Administer T1 Interface Card ....................................................................................... 40

5.4. Administer Dial Peers and Voice Ports ......................................................................... 41

5.5. Administer MGCP PRI Backhaul ................................................................................. 42

6. Configure Cisco Unified Communications Manager ....................................................... 43 6.1. Log into Cisco Unified Communications Manager ...................................................... 43

6.2. Administer Media Resource Group............................................................................... 44

6.3. Administer Media Resource Group List ....................................................................... 45

6.4. Administer Service Parameters ..................................................................................... 47

6.5. Administer MGCP Gateway ......................................................................................... 49

6.6. Administer Route Pattern .............................................................................................. 55

6.7. Administer Voice Mail Pilot ......................................................................................... 57

JMC; Reviewed:

SPOC 8/12/2009



3 of 81

SMM-MSS-SIP-AC

6.8. Administer Voice Mail Profile ...................................................................................... 58

6.9. Administer Phones ........................................................................................................ 59

7. Avaya Modular Messaging Configuration upon Outage ................................................ 62

8. Verification Steps ................................................................................................................ 64 8.1. Verify Avaya Modular Messaging ................................................................................ 64

8.1.1. Verification at Secondary Site ............................................................................... 65

8.2. Verify AudioCodes Mediant 1000 Gateway ................................................................. 65

8.3. Verify Cisco 2811 MGCP Gateway and Cisco Unified Communications Manager .... 66

9. Conclusion ............................................................................................................................ 67

10. Additional References ......................................................................................................... 67

11. Appendix A .......................................................................................................................... 68

12. Appendix B .......................................................................................................................... 76

JMC; Reviewed:

SPOC 8/12/2009



4 of 81

SMM-MSS-SIP-AC

1. Introduction These Application Notes describe the steps required to configure an Avaya Survivable Modular

Messaging solution in a MultiSite environment that utilizes Avaya Message Storage Server

(MSS) incorporating AudioCodes Mediant 1000 for connectivity to Cisco Unified

Communications Manager. The Avaya Survivable Modular Messaging solution is a disaster

recovery solution for failover voicemail service to a Secondary Site following an outage at the

Primary Site.

The configuration shown in Figure 1 is spread across three separate locations. Site A contains

Cisco Unified Communication Manager and AudioCodes Mediant 1000 (AC1000). The AC1000

is connected via a SIP trunk to the Primary Avaya Modular Messaging system at Site B. During

normal operations, the Cisco Unified Communications Manager Server with Cisco 2811 MGCP

Media Gateway, AC1000 and Primary Avaya Modular Messaging Server handle all calls and

voicemail needs for all subscribers. The Avaya Modular Messaging Servers at Site C (Secondary

Site) are on standby during normal operations but do not handle calls or voicemails for

subscribers.

Figure 1 – Survivable Modular Messaging Test Configuration

JMC; Reviewed:

SPOC 8/12/2009



5 of 81

SMM-MSS-SIP-AC

In the event of a disaster or complete outage at the Primary Avaya Modular Messaging site, such

that Avaya Modular Messaging servers are unavailable, the Avaya Modular Messaging Servers

at the Secondary Site, following some manual failover steps, become active. These steps include

manual changes to the DNS server and optionally the AC1000.

2. Equipment and Software Validated Table 1 lists equipment used for the sample configuration provided:

Equipment Software

Avaya Modular Messaging

• Messaging Storage Server - 8730

• Messaging Application Server - 8730

5.1 (9.0.370.16)

5.1

AudioCodes Mediant 1000 Media Gateway 5.60A.007.004

Acronis True Image Server 9.1 (Build 3.854)

Cisco Unified Communications Manager 7.0.2.10000-18

Cisco 2811 MGCP Gateway

• WIC2-1MFT-T1/E1

• PVDM (DSP Resources)

C2800NM-SPSERVICESK9-M),

Version 12.4(3i)

Cisco 7911 SIP Telephone SIP11.8-4-3S

Cisco 7911 SCCP Telephone SCCP11.8-4-3S

Cisco 7960 SIP Telephone P0S3-08-8-00

Table 1 – Test Equipment And Software List.

JMC; Reviewed:

SPOC 8/12/2009



6 of 81

SMM-MSS-SIP-AC

3. Configure Avaya Modular Messaging This section focuses on configuring the Avaya Modular Messaging servers at both the Primary

and Secondary Sites. The configuration procedures include the following areas:

• Configuration of Primary Modular Messaging Site

• Configuration of Secondary Modular Messaging Site

• Steps to maintain service during an outage.

The Data Collection Tool (DCT) file is created as part of pre-installation planning and used as

input to automate MAS installations. Full details of configuring a Modular Messaging system

using a DCT file are described in reference [1]. Details specific to the configuration of the

Primary Site are discussed in this section.

3.1. Configure Primary Avaya Modular Messaging Site

This section deals with the configuration of the primary Avaya Modular Messaging Site. It also

describes how to make a copy of the primary installation that can be used to create the Secondary

installation. It is assumed that Avaya MAS and Avaya MSS servers have the correct software

installed and are appropriately licensed.

Ensure that the FQDN of Avaya MSS and Avaya MAS are configured on the DNS servers in the

system to point to Primary Avaya MAS and Avaya MSS. The IP addresses of all Avaya Modular

Messaging Servers are static.

• MAS: mascp2.avayalabs.com

• MSS: msscp2.avayalabs.com

Note that a private Windows domain is used for communication between Avaya MSS and Avaya

MAS.

3.1.1. MultiSite Configuration

In order to enable MultiSite functionality on the Primary Modular Messaging Site the MAS must

be configured as shown in this section. Appendix A contains the DCT information used to

configure the Primary system for these Application Notes. The configuration can be verified by

following the instructions in this section. Log in to the Avaya MAS server using the appropriate

credentials. Select Start�� Programs �� Avaya Modular Messaging ��Voice Mail System

Configuration to start the Voice Mail System Configuration tool.

JMC; Reviewed:

SPOC 8/12/2009



7 of 81

SMM-MSS-SIP-AC

From the Voice Mail System Configuration window go to Voice Mail Domains �� SMMLAB

�� Sites. From the subsequent Voice Mail Domain window, confirm that the Enable MultiSite

checkbox is selected in the screen as shown. Click Configure to open the Site Configuration

window.

In this example the Dublin site has an ID of 3531207, a Full Mailbox length of 11 and a Short

Mailbox length of 4. The PBX Name is the name of the PBX as shown in Voice Mail Domains

�� PBXs described later in this section.

JMC; Reviewed:

SPOC 8/12/2009



8 of 81

SMM-MSS-SIP-AC

To configure these settings in the DCT file prior to installation, Enable MultiSite must be

checked in the Voice Mail Domain section as shown.

The Site Configuration for SMMLAB screen discussed earlier in this section can be configured

in the DCT tool via the Dial Plan option in the left menu structure and then clicking Configure.

JMC; Reviewed:

SPOC 8/12/2009



9 of 81

SMM-MSS-SIP-AC

To configure or confirm the SIP integration of Avaya MAS, from the Voice Mail System

Configuration window, go to Voice Mail Domains �� SMMLAB �� PBXs and click on the

SIP tab. Ensure that the IP address or fully qualified domain name (FQDN) of the AC1000 is

entered in the Address/FQDN field. Configure Protocol and SRTP settings to match the

AC1000 settings discussed in Section 4.2.3. In this example, SRTP was not enabled and the

chosen Protocol was TLS. Enter the SIP Domain to match the Gateway Name configured in

Section 4.2.4. Click the Configure button located near the bottom of the screen to configure the

incoming and outgoing phone number translation rules.

The Translation Rules screen opens as shown below. The example translation rules shown

below will map an incoming number of 6010 to its canonical form of +35312076010. For more

details in creating incoming and outgoing translation rules please refer to [5].

JMC; Reviewed:

SPOC 8/12/2009



10 of 81

SMM-MSS-SIP-AC

To configure the DCT file prior to installation, click Switch Integration Information. Enter the

following information :

• IP Address : IP Address of the Cisco Unified Communications Manager

• Switch Name : Name for the PBX

• Gateway Address : Address of the AC1000

• Default Gateway : Specific to network topology

• SIP Domain : Match the Gateway Name configured in Section 4.2.4.

• Subnet Mask : Specific to network topology

The remaining values are arbitrary. Click Save to save any changes.

JMC; Reviewed:

SPOC 8/12/2009



11 of 81

SMM-MSS-SIP-AC

3.1.2. Configuration of Services.

From the Voice Mail System Configuration Application Window, go to Voice Mail Domains

�� SMMLAB and double click Message Waiting Indicator.

In the Message Waiting Indicator screen that opens, check Enable Message Waiting

Indicator (MWI). Then set Message Application Servers that support MWI to the computer

name of the Primary Site MAS server as shown. Click OK.

JMC; Reviewed:

SPOC 8/12/2009



12 of 81

SMM-MSS-SIP-AC

From the Voice Mail System Configuration Application Window, go to Voice Mail Domains

�� SMMLAB and double click Call Me. In the Call Me popup that appears, check Enable Call

Me and set MAS Call Me Server as shown.

JMC; Reviewed:

SPOC 8/12/2009



13 of 81

SMM-MSS-SIP-AC

3.1.3. Configuration of Services.

This section describes how to configure an example Class-of Service that can be used in creating

Avaya Modular Messaging subscribers. Configuration is performed through the Modular

Messaging Message Administration application. To launch the application, enter Avaya MSS

hostname or IP address in the URL field of a web browser. Log in with the appropriate

credentials. The following webpage is displayed.

Select the Classes-of-Service menu option from the Messaging Administration Menu on the left

of the screen. The Manage Classes-of-Service screen opens up. Select an unused class of

service from the displayed list and click Edit the Selected COS as shown.

JMC; Reviewed:

SPOC 8/12/2009



14 of 81

SMM-MSS-SIP-AC

The Edit a Class-of-Service screen opens. Scroll down the screen to the Subscriber Feature and

Services section and set the options as appropriate for the configuration. In this case Call Me

Allowed, Find Me Allowed and Message Waiting Indication Allowed are all set to yes. The

remaining settings can be left at their default values.

Save any changes made by clicking Save which is located at the bottom of the screen (not

shown).

JMC; Reviewed:

SPOC 8/12/2009



15 of 81

SMM-MSS-SIP-AC

3.1.4. Subscriber Creation.

Click on the Subscriber Management option in the Messaging Administration Menu. Enter the

Local Subscriber Mailbox Number and click Add or Edit. Here the Mailbox Number is

35312076010.

In this example, the Canonical form of the PBX Extension is used. This refers to the

combination of the Site ID, 3531207 as configured in Section 3.1.1, and the Switch Native

extension, in this case 6010. Enter in the appropriate details for the subscriber and ensure that the

Class-of-Service is set to the one described in Section 3.1.3. The default Community ID is

selected.

Save any changes by clicking the Save button (not shown) and repeat the process for all required

subscribers.

JMC; Reviewed:

SPOC 8/12/2009



16 of 81

SMM-MSS-SIP-AC

3.1.5. Backup Avaya MAS

In order to create an exact copy of the Primary Avaya MAS at the Secondary Site, an image copy

is made of the Primary Avaya MAS and sent to the Secondary Site for restoration. In this case

Acronis True Image Server is used to copy the image of Avaya MAS onto a USB II hard drive

with at least 300GB capacity. Full details of how to use Acronis True Image Server Software are

available in reference [9] and will not be described here.

A bootable rescue media is created using Acronis True Image Server that has been installed on a

client server. A copy of this media should be made available at both the Primary and Secondary

Sites. Place this disk in the CD tray of the Primary Avaya MAS server and reboot. Once booted,

the Acronis software asks the user which version to run. Select the Full Version. The following

screen is displayed. Select the Backup option to start the Backup wizard.

JMC; Reviewed:

SPOC 8/12/2009



17 of 81

SMM-MSS-SIP-AC

During Wizard configuration, ensure that the entire disk contents or individual partitions

radio button is selected. Select a New full backup archive and Use Default Options in the

subsequent screens. Add a Comment as desired. Before the backup can start a confirmation

screen is displayed as shown. Confirm all the backup details and click Proceed to start the

backup.

Once the backup is complete the 300GB hard drive can be shipped to the Secondary Avaya

Modular Messaging Site and used as described in Section 3.2.2.

JMC; Reviewed:

SPOC 8/12/2009



18 of 81

SMM-MSS-SIP-AC

3.1.6. Backup Avaya MSS Data.

This section describes the steps involved in creating a backup of all data stored on the Primary

Avaya MSS sever. This backup is made to an FTP server that can by reached via the network

from the Primary Avaya MSS. Using the Modular Messaging Message Administration

application introduced in Section 3.1.3, click the Remote Storage Configuration option on the

Backup/Restore Menu. Set the following parameters and click Save:

• Backup Mode: Select FTP.

• Host Name: Set this to point to a working FTP server.

• User Name: A user name on the FTP server.

• Directory: The directory path on the FTP server where to store files.

• Password: The associated password for the user.

JMC; Reviewed:

SPOC 8/12/2009



19 of 81

SMM-MSS-SIP-AC

Select Backup from the Backup/Restore Menu and ensure System Data, Names and Greetings

and Messages are set to yes. Then click Start Backup. Stopping the Voice System is optional

while performing the backup. If the Voice System is stopped prior to the backup, remember to

restart it from the Utilities Menu by clicking Start Messaging when backup is complete.

JMC; Reviewed:

SPOC 8/12/2009



20 of 81

SMM-MSS-SIP-AC

3.2. Configure Secondary Avaya Modular Messaging Site

This section deals with the restoration of Primary Site Avaya MMS data collected in Section

3.1.6 and the Primary Site Avaya MAS image created in Section 3.1.5 to the Secondary Modular

Messaging Site.

3.2.1. Restore Avaya MSS.

Launch the Messaging Administration tool on the Secondary Avaya MSS as described in

Section 3.1.2. Ensure that the Secondary Avaya MSS server can connect to the FTP server that

contains the backup files created in Section 3.1.6 and configure the Remote Storage

Configuration appropriately.

• Backup Mode : Select FTP.

• Host Name: Set this to point to a working FTP server.

• User Name: A user name on the FTP server.

• Directory: The directory path on the FTP server where the files are stored.

• Password: The associated password for the user.

JMC; Reviewed:

SPOC 8/12/2009



21 of 81

SMM-MSS-SIP-AC

Select Restore from the Backup/Restore Menu and click Stop Voice System which is displayed

on the subsequent screen. When the messaging system is stopped click Restore again. The

following screen is displayed. Select the file that was created in Section 3.1.6 and ensure System

Data, Names and Greetings and Messages are set to yes. Then click Start Restore.

Once the restore operation is completed, the system prompts the user to reboot. Before this can

happen the TCP/IP Network Configuration should be reset to the values required for operation

at the Secondary Site. This is because the restore operation overwrites the values with those of

the Primary Site. Click on TCP/IP Network Configuration in the Server Administration Menu

and change the Default Gateway Address and IP Address fields to reflect the values needed at

the Secondary Site. Click Save (not shown)

• Default Gateway Address : Changed from 10.10.3.1 to 10.10.3.1

• IP Address: Changed from 10.10.3.201 to 10.10.3.201

JMC; Reviewed:

SPOC 8/12/2009



22 of 81

SMM-MSS-SIP-AC

Reboot Avaya MSS by clicking Reboot Server from the Utilities Menu and clicking Reboot in

the subsequent screen. In normal operation, it is also recommended to restart Avaya MAS after a

restoration of MSS data.

3.2.2. Restore Avaya MAS

Full details of how to use Acronis True Image Server Software are available in [9] and will not

be described here. Place the bootable rescue media from Acronis created in Section 3.1.5 into the

CD tray of the Secondary Avaya MAS server. Connect the USB II hard drive created in Section

3.1.5 and reboot. Once booted, the Acronis software asks the user which version to run. Select

the Full Version. The following screen is displayed. Click Recovery to start the Recovery

Wizard.

JMC; Reviewed:

SPOC 8/12/2009



23 of 81

SMM-MSS-SIP-AC

As the wizard progresses, select the file to restore in this case WedPM1.tlb. In this example the

WedPM.tlb backup file is split into 3 separate files each of which need to be restored. Ensure

Restore disks or partitions and Primary Partition Type are selected and drive C: is the

primary active drive. Before the recovery can start, a confirmation screen similar to the one

shown below is displayed. Confirm all the Recovery details and click Proceed to start the

process.

JMC; Reviewed:

SPOC 8/12/2009



24 of 81

SMM-MSS-SIP-AC

3.2.3. Post Avaya MAS Restoration Configuration

Once the recovery process is complete the IP address details of the Secondary Avaya MAS must

be changed to reflect the settings of the Secondary Avaya MAS and not those of the Primary

system. To do this log into Avaya MAS with the appropriate credentials and click

Start��Settings��Network Settings. Select Local Area Connection and then click Properties

from the subsequent dialog. Select Internet Protocol (TCP/IP) and open its Properties dialog.

Ensure that the IP address and Default gateway are correct for the secondary site. In the

example the IP address is changed from 10.10.3.200 to 10.10.1.200 and the Default gateway

from 10.10.3.1 to 10.10.1.1.

Click Advanced to open the Advanced TCP/IP Settings dialog and ensure that Register this

connection’s addresses in DNS on the DNS tab is unchecked as shown.

JMC; Reviewed:

SPOC 8/12/2009



25 of 81

SMM-MSS-SIP-AC

Update the “hosts” file located in “C:\WINDOWS\system32\drivers\etc” directory, to ensure the

correct IP addresses are used for both Avaya Modular Messaging Servers at the Secondary Site.

Reboot Avaya MAS. Log in to the Secondary Avaya MAS with the appropriate credentials and

open a Windows Explorer. Locate the “C:\Avaya_Support\Tools\FEDBSync” directory and run

the FEDBSync Tool. The tool is shown below. Click Execute.

Click OK to continue.

Wait for event 1027 to appear in the Windows Event Viewer. Once completed, subscriber

functionality will operate correctly.

JMC; Reviewed:

SPOC 8/12/2009



26 of 81

SMM-MSS-SIP-AC

4. Configure AudioCodes Mediant 1000 Media Gateway This section describes the configuration of the AudioCodes Mediant 1000 Media Gateway

(AC1000) to provide SIP connectivity to the Modular Messaging system and T1 connectivity to

the Cisco Unified Communications Manager. Details of how to perform basic configuration such

as assigning an IP address are detailed in reference [1] and are not repeated here.

4.1. Using Configuration File

Reference [5] contains a sample INI file that can be used to configure the AC1000 using the

AudioCodes Web interface. Copy the example into a text file and make appropriate changes to

suit the intended topology. Appendix B contains the INI file used to configure the system shown

in Figure 1 and should be used as a reference. In the event of an error, Section 4.2 descibes how

changes can be made to the configuration once the INI file has been loaded. Access the Web

interface by using the URL “http:// ip-address” where ip-address is the IP address of the

AudioCodes. Log in using a valid username and password. Select the Management tab followed

by Software Update��Configuration File. Locate the INI file on the computer by clicking the

Browse button. Click Load INI File.

JMC; Reviewed:

SPOC 8/12/2009



27 of 81

SMM-MSS-SIP-AC

4.2. Manual Configuration Changes

This section describes the relevant configuration screens used in these Application Notes. This

section can be used to manually configure the Web GUI if a configuration INI file is not used as

described in Section 4.1. It can also be used to confirm the configuration after uploading an INI

file. The following steps are described:

• Configure Trunk Settings

• Configure SIP General Parameters

• Configure Media Security

• Configure Proxy And Registration

• Configure Coder

• Configure Digit Collection Setup

• Configure SIP Advance Parameters

• Configure Trunk Group

• Configure Voice Mail Settings

• Configure TDM Bus Settings

• Configure DNS

• Configure Admin Parameters

During configuration ensure that the Full radio button and the Configuration tab are selected.

This will show all the options that are available for configuration.

JMC; Reviewed:

SPOC 8/12/2009



28 of 81

SMM-MSS-SIP-AC

4.2.1. Configure Trunk Settings

Select PSTN Settings �� Trunk Settings on the Configuration tab. De-activate the trunk to

make changes by clicking Stop Trunk (not shown). Ensure the following values are set:

• Protocol Type: T1 QSIG

• Framing Method : T1 FRAMING ESF CRC6

• ISDN Termination Side: Network Side.

• Q931 Layer Response Behavior 0x40000000

The ISDN Termination Side setting corresponds to setting Protocol Side to User in Section

6.5. Remaining values can remain unchanged. Click Apply Trunk Settings (not shown) to

commit any changes and wait for the setting to be applied to trunk 1.

JMC; Reviewed:

SPOC 8/12/2009



29 of 81

SMM-MSS-SIP-AC

4.2.2. Configure SIP General Parameters

Select Protocol Configuration��Protocol Definition��SIP General Parameters on the

Configuration tab. Ensure the following values are set:

• Channel Select Mode: Ascending

• SIP Transport Type: TLS

• SIP TLS Local Port: 5061

• SIP Destination Port : 5061

Remaining values can remain unchanged. Click Submit to commit any changes.

JMC; Reviewed:

SPOC 8/12/2009



30 of 81

SMM-MSS-SIP-AC

4.2.3. Configure Media Security

Select Media Settings��Media Security on the Configuration tab. Ensure the following values

are set to configure a TLS connection without SRTP between Avaya Modular Messaging and

AC1000.

• Media Security: Disabled

• Media Security Behavior: Mandatory

• Disable Encryption on Transmitted

RTP Packets : 0

Remaining values can remain unchanged. Click Submit (not shown) to submit any changes.

JMC; Reviewed:

SPOC 8/12/2009



31 of 81

SMM-MSS-SIP-AC

4.2.4. Configure Proxy and Registration

Select Protocol Configuration��Protocol Definition��Proxy & Registration on the

Configuration tab. Ensure the following values are set:

• Use Default Proxy : Yes

• Enable Registration : Disable

• Gateway Name : The FQDN name that is to be used for the Gateway.

Corresponds to SIP Domain in Section 3.1.1.


Click the Proxy Set Table arrow. On the subsequent screen set the Proxy Address to the FQDN

or IP address of Avaya Modular Messaging MAS. Set the Transport Type to TLS.

Click Submit (not shown) to submit any changes.

JMC; Reviewed:

SPOC 8/12/2009



32 of 81

SMM-MSS-SIP-AC

4.2.5. Configure Coder

Select Protocol Configuration��Protocol Definition��Coders on the Configuration tab.

Ensure the following values are set:

• Coder Name : G.711U-law

• Packetization Time : 20 msec

• Rate : 64 kbps


4.2.6. Configure Digit Collection Setup

Select Protocol Configuration��Protocol Definition��DTMF & Dialing on the Configuration

tab. Ensure the following values are set:

• Max Digits In Phone Num : 30 digits.

• Default Destination Number : serveduser


JMC; Reviewed:

SPOC 8/12/2009



33 of 81

SMM-MSS-SIP-AC

4.2.7. Configure SIP Advanced Parameters

Select Protocol Configuration��SIP Advanced Parameters��Advanced Parameters on the

Configuration tab. Ensure the Disconnect on Broken Connection parameter is set to No.


JMC; Reviewed:

SPOC 8/12/2009



34 of 81

SMM-MSS-SIP-AC

4.2.8. Configure Trunk Group

Select Protocol Configuration��Trunk/IP Group��Trunk Group on the Configuration tab.

Ensure the following values are set:

• Module : Module 1 PRI (the module that contains the physical connection)

• Trunk : 1 (The range of trunks to be used)

• Channels : 1-24 channels.

• Phone Number : 4299 (Voice Mail Pilot number)


4.2.9. Configure Voice Mail Settings

Select Advanced Applications��Voice Mail Settings on the Configuration tab. Ensure the

Voice Mail Interface is set to QSIG. Remaining values can remain unchanged. Click Submit

(not shown) to submit any changes.

JMC; Reviewed:

SPOC 8/12/2009



35 of 81

SMM-MSS-SIP-AC

4.2.10. Configure TDM Bus Settings

Select TDM Configuration��TDM Bus Settings on the Configuration tab. Select MuLaw in

the PCM Law Select drop down and Network in the TDM Bus Clock Source drop down.


4.2.11. Configure DNS

Select Network Settings��Application Settings on the Configuration tab. Scroll down to the

DNS Settings Section. Enter the IP address of the DNS server. Click Submit (not shown) to

submit any changes.

Select Protocol Configuration��Routing Tables��Internal DNS Table on the Configuration

tab. Ensure that the Domain Names anonymous.invalid and stockleyg3.com are entered giving

the IP address of the AC1000 as the First IP Address in both cases.


JMC; Reviewed:

SPOC 8/12/2009



36 of 81

SMM-MSS-SIP-AC

4.2.12. Configure Admin Parameters

Access this by using the URL “http:// ip-address/AdminPage” where ip-address is the IP address

of the AC1000. Log in using a valid username and password. Select ini Parameters on the left

hand side of the screen. The following values must be configured from the screen:

• ISDNIBehavior : 1073741824

• EnableMWI : 1

• ECNLPMODE : 1

• SubscriptionMode : 1

• TrunkTransferMode_0 : 0

In the Parameter Name field enter ISDNIBehavior and enter the corresponding value

1073741824 in the Enter Value field. Click the Apply New Value button. Repeat this for each

of the values listed above.

JMC; Reviewed:

SPOC 8/12/2009



37 of 81

SMM-MSS-SIP-AC

4.3. Reset Gateway

After configuration has been completed, burn the configuration to the AC1000 flash memory and

reset the gateway. Click the Device Actions��Reset. Verify that Burn To Flash is set to Yes

and click the Reset Button. The AC1000 will then take about 60 seconds to reboot.

JMC; Reviewed:

SPOC 8/12/2009



38 of 81

SMM-MSS-SIP-AC

5. Configure Cisco 2811 MGCP Gateway The procedures for configuring Cisco 2811 MGCP Gateway include the following areas:

• Log into Gateway

• Administer MGCP Protocol

• Administer T1 Interface Card

• Administer Dial Peers and Voice Ports

• Administer MGCP PRI Backhaul

5.1. Log into Gateway

Access the MGCP Gateway command line interface via a hyper terminal application running on

a personal computer. This computer has a serial cable connected to the MGCP Gateway console

port. The output from the MGCP Gateway has been trimmed down in the subsequent sections, in

order to focus on the key settings for the configuration. Values highlighted in bold italics

represent values entered by the system administrator.

Command Comment

User Access Verification

Password: xxxxx

2811>

2811> enable

Password: yyyyy

2811#

User Access Verification is displayed.

Enter a valid user password.

A sample response indicating successful log in.

2811> in this case is the gateway hostname that

was previously configured.

Enter the enable command to enable the privileged

EXEC mode.

Enter the valid user password for the EXEC mode.

A sample response indicating successful entry into the

EXEC mode.

JMC; Reviewed:

SPOC 8/12/2009



39 of 81

SMM-MSS-SIP-AC

5.2. Administer MGCP Protocol

Use the command line interface to enable support for the MGCP protocol and support for Cisco

Unified Communications Manager.

Command Comment

2811# configure terminal

2811(config)#

2811(config)# mgcp

2811(config)# mgcp call-agent

callmgr.avayalabs.com service-type

mgcp version 0.1

2811(config)# mgcp dtmf-relay voip

codec all mode out-of-band

2811(config)# ccm-manager mgcp

Enables the global configuration mode.

A sample response indicating successful entry into the

global configuration mode.

Enables the MGCP protocol.

Specifies the Cisco Unified Communications Manager,

the gateway control service, and version of service-

type. In this case, callmgr.avayalabs.com is the fully

qualified domain name for the Cisco Unified

Communications Manager. The servicetype is mgcp,

and the version for MGCP is 0.1.

Specifies the codec type and dual tone multifrequency

(DTMF) relay services.

Enables the MGCP gateway to support Cisco Unified

Communications Manager.

JMC; Reviewed:

SPOC 8/12/2009



40 of 81

SMM-MSS-SIP-AC

5.3. Administer T1 Interface Card

Use the command line interface to administer the T1 controller.

Command Comment

2811(config)# card type t1 0 0

2811(config)# controller t1 0/0/0

2811(config-controller)# framing esf

2811(config-controller)# linecode

b8zs

2811(config-controller)# pri-group

timeslots 1-24 service mgcp

2811(config-controller)# exit

2811(config)#ip routing

From the global configuration mode use the card type

command to configure the card type of the controller as

T1.

From the global configuration mode, use the controller

command to enter the controller configuration mode. In

this case, t1 is used to specify T1. The first 0 implies

the module is directly inserted into the 2811 chassis.

The second 0 is the physical slot number of the network

module card and the third 0 is the port number.

Specifies esf as the framing type.

Specifies b8zs as the line encoding method.

Specifies MGCP as the control protocol with 24 ports.

Exits the controller configuration mode.

Enables IP routing to allow two-way audio connection.

JMC; Reviewed:

SPOC 8/12/2009



41 of 81

SMM-MSS-SIP-AC

5.4. Administer Dial Peers and Voice Ports

Use the command line interface to administer dial peers and voice ports for MGCP, beginning in

the global configuration mode.

Command Comment

2811(config)# dial-peer voice 1

pots

2811(config-dial-peer)# Service

MGCPAPP

2811(config-dial-peer)# port 0/0/0:23

2811(config-dial-peer)# exit

2811(config)# voice-port 0/0/0:23

2811(config-voiceport)# no shut

2811(config-voiceport)# exit

From the global configuration mode, use the dial-peer

command to enter the dial peer configuration mode, and

designate the specified dial peer as a POTS dial peer

using VoIP encapsulation.

Enables MGCP on the dial peer. Note that the

command is case-sensitive in some Cisco IOS versions.

Binds the MGCP application to the specified voice

ports. In this case, 0/0/0 represents “0/slot/ port”.

The first 0 signifies the card is inserted directly into the

rear of the 2811 chassis.

Exits the dial-peer configuration mode.

From the global configuration mode, use the voice-port

command to enter the voice port configuration mode. In

this case 0/0/0 represents “0/slot/ port”.

Activates the voice port.

Exits the voice port configuration mode.

JMC; Reviewed:

SPOC 8/12/2009



42 of 81

SMM-MSS-SIP-AC

5.5. Administer MGCP PRI Backhaul

MGCP PRI backhaul is a method for transporting information from the signaling D-channel of

the MGCP gateway to Cisco Unified Communications Manager over a TCP connection. Use the

command line interface to configure for MGCP PRI backhaul, beginning in the global

configuration mode.

Command Comment

2811(config)# interface serial

0/0/0:23

2811(config-if)# isdn switchtype

primary-qsig

2811(config-if)# isdn bind-L3 ccm-

manager

2811(config-if)# exit

From the global configuration mode, use the interface

serial command to enter the serial interface

configuration mode. In this case, 0/0/0:23 represents

“0/slot/port:timeslot”.

Specifies QSIG as the ISDN switch type.

Enables ISDN to backhaul Q.931.

Exits the serial interface configuration mode.

JMC; Reviewed:

SPOC 8/12/2009



43 of 81

SMM-MSS-SIP-AC

6. Configure Cisco Unified Communications Manager The procedures for configuring Cisco Unified Communications Manager include the following

areas:

• Log into Cisco Unified Communications Manager

• Administer Media Resource Group

• Administer Media Resource Group List

• Administer Service Parameters

• Administer MGCP Gateway

• Administer Route Pattern

• Administer Voice Mail Pilot

• Administer Voice Mail Profile

• Administer Phones

6.1. Log into Cisco Unified Communications Manager

Access the Cisco Unified Communications Manager Administration web interface by using the

URL “http://<ip-address>” in an Internet browser window, where “<ip-address>” is the IP

address of the Cisco Unified Communications Manager. Note that the IP address for the Cisco

Unified Communications Manager may vary, and in this case “10.10.5.100” is used. This was

configured as part of installation.

Click on Cisco Unified Communications Manager Administration at the bottom of the

screen, and log in with appropriate credentials.

JMC; Reviewed:

SPOC 8/12/2009



44 of 81

SMM-MSS-SIP-AC

6.2. Administer Media Resource Group

The Cisco Unified CM Administration screen is displayed. Select Media Resources �� Media

Resource Group, as shown below.

The Find and List Media Resource Groups screen is displayed next. Click Add New to add a

new Media Resource Group.

JMC; Reviewed:

SPOC 8/12/2009



45 of 81

SMM-MSS-SIP-AC

The Media Resource Group Configuration screen is displayed. Enter descriptive text into the

Name and Description fields. Select all resources from the Available Media Resources section,

and use the down arrow to move the resources to the Selected Media Resources section. For

this interoperability testing, all available media resources were selected. Click Save.

6.3. Administer Media Resource Group List

Scroll to the top of the screen, and select Media Resources �� Media Resource Group List, as

shown below.

JMC; Reviewed:

SPOC 8/12/2009



46 of 81

SMM-MSS-SIP-AC

The Find and List Media Resource Group Lists screen is displayed next. Click Add New to

add a new media resource group list.

The Media Resource Group List Configuration screen is displayed. Enter a descriptive text

into the Name field. Select the media resource group created in Section 6.2 from the Available

Media Resource Groups section, and use the down arrow to move to the Selected Media

Resource Groups section. Click Save.

JMC; Reviewed:

SPOC 8/12/2009



47 of 81

SMM-MSS-SIP-AC

6.4. Administer Service Parameters

Scroll to the top of the screen, and select System �� Service Parameters, as shown below.

The Service Parameter Configuration screen is displayed next. Select the appropriate values in

the Server and Service fields for the network configuration, which were administered as part of

installation. The Service Parameter Configuration screen is updated with service parameter

fields (not shown).

JMC; Reviewed:

SPOC 8/12/2009



48 of 81

SMM-MSS-SIP-AC

Scroll down to the Clusterwide Parameters (Feature – Forward) section. For the Forward By

Reroute Enabled field, select True from the drop-down list to enable the QSIG forward by

reroute feature. For the Include Original Called Info for Q.SIG Call Diversions field, select

Always from the drop-down list to enable encoding of the original called party name and number

for all QSIG call diversions. Retain the default values for the remaining fields.

Scroll down to the Clusterwide Parameters (Feature – Path Replacement) section. For the

Path Replacement Enabled field, select True from the drop-down list to enable the QSIG path

replacement feature.

The message pop up box below is displayed, click OK to proceed. Retain the default values for

the remaining fields. Scroll down to the bottom of the screen and click Save (not shown).

JMC; Reviewed:

SPOC 8/12/2009



49 of 81

SMM-MSS-SIP-AC

6.5. Administer MGCP Gateway

Scroll to the top of the screen, and select Device �� Gateway, as shown below.

The Find and List Gateway screen is displayed. Click Add New to add a new gateway.

The Add a new Gateway screen is displayed next. Select Cisco 2811 from the Gateway Type

drop-down list. Click Next to proceed.

JMC; Reviewed:

SPOC 8/12/2009



50 of 81

SMM-MSS-SIP-AC

On the subsequent screen select MGCP from the Protocol drop-down list. Click Next to

proceed.

The Gateway Configuration screen is displayed. Enter the following values for the specified

fields, and retain the default values for the remaining fields.

• Domain Name: 2811.mm.com (The fully qualified

domain name for the gateway)

• Description: MCGP Gateway (A descriptive text)

• Cisco Unified

Communication Manager Group: Default

• Module in Slot 0: NM-4VWIC-MBRD

Scroll down to the bottom of the screen, leaving the other values unchanged and click Save.

JMC; Reviewed:

SPOC 8/12/2009



51 of 81

SMM-MSS-SIP-AC

The screen is updated with 4 Subunit fields appearing below the Module in Slot 0 field. For the

Subunit 0 field, select VWIC2-1MFT-T1E1-T1 from the drop-down list. Scroll down to the

bottom of the screen and click Save (not shown).

The screen is updated with icons appearing to the right of the Subunit 0 field. Click the icon

next to the 0/0/ 0 field.

The Find and List Gateway screen is displayed. Select Digital Access PRI from the Device

Protocol drop-down list, and click Next.

JMC; Reviewed:

SPOC 8/12/2009



52 of 81

SMM-MSS-SIP-AC

The Gateway Configuration screen is displayed next. Enter the following values for the

specified fields, and retain the default values for the remaining fields.

• Device Pool: Default

• Call Classification: OffNet

• NetworkLocale: Ireland (The applicable locale for the network

configuration)

• Media Resource Group List: DublinSIL (The media resource group list from

Section 6.3.)

Scroll down to the Interface Information section. Select PRI ISO QSIG T1 for the PRI

Protocol Type field. Ensure Protocol Side is set to User (User/Slave) to mirror the Network

Side setting of ISDN Termination Side configured in Section 4.2.1. Select Top Down for the

Channel Selection Order field. Retain the default values for the remaining fields.

JMC; Reviewed:

SPOC 8/12/2009



53 of 81

SMM-MSS-SIP-AC

Scroll down to the Call Routing Information – Outbound Calls section. Select Allowed for

the Calling Party Presentation field and retain the default values for the remaining fields.

Scroll down to the PRI Protocol Type Specific Information section. Select Allowed for the

Connected Line ID Presentation (QSIG Inbound Call) field.

Scroll down to the bottom of the screen. Maintain all default values in the remaining fields, and

click Save. Click OK to the subsequent Reset Gateway message pop up box. (Not shown).

JMC; Reviewed:

SPOC 8/12/2009



54 of 81

SMM-MSS-SIP-AC

Next, the screen is updated with additional buttons appearing at the bottom of the screen. Click

Reset.

In the Device Reset dialog box, click Reset, followed by Close.

JMC; Reviewed:

SPOC 8/12/2009



55 of 81

SMM-MSS-SIP-AC

6.6. Administer Route Pattern

Scroll to the top of the screen, and select Call Routing �� Route/Hunt �� Route Pattern, as

shown below.

The Find and List Route Patterns screen is displayed. Click Add New to add a new route

pattern.

JMC; Reviewed:

SPOC 8/12/2009



56 of 81

SMM-MSS-SIP-AC

The Route Pattern Configuration screen is displayed. Enter a route pattern for the Route

Pattern field, in this case 4299 as defined in Section 4.2.8 to denote the 4-digit extension for

Avaya Modular Messaging. Enter a descriptive text for the Description field, and select the

MGCP gateway from Section 6.5 for the Gateway/Route List field drop-down list. Uncheck the

Provide Outside Dial Tone field. Retain the default values in the remaining fields, and scroll

down to the bottom of the screen to click Save (not shown).

Click OK on the two subsequent pop up dialog boxes.

JMC; Reviewed:

SPOC 8/12/2009



57 of 81

SMM-MSS-SIP-AC

6.7. Administer Voice Mail Pilot

Scroll to the top of the screen, and select Voice Mail �� Voice Mail Pilot, as shown below.

The Find and List Voice Mail Pilots screen is displayed. Click Add New to add a new voice

mail pilot for Avaya Modular Messaging.

The Voice Mail Pilot Configuration screen is displayed next. Enter the Avaya Modular

Messaging pilot number into the Voice Mail Pilot Number field, in this case 4299 as previously

configured in Section 4.2.8. Enter a descriptive text into the Description field, and click Save.

JMC; Reviewed:

SPOC 8/12/2009



58 of 81

SMM-MSS-SIP-AC

6.8. Administer Voice Mail Profile

Scroll to the top of the screen, and select Voice Mail �� Voice Mail Profile, as shown below.

The Find and List Voice Mail Profiles screen is displayed. Click Add New to add a new voice

mail profile for Avaya Modular Messaging.

The Voice Mail Profile Configuration screen is displayed next. Enter a descriptive name and

description into the Voice Mail Profile Name and Description fields. For the Voice Mail Pilot

field, select the voice mail pilot number administered in Section 6.7 from the drop-down list.

Click Save.

JMC; Reviewed:

SPOC 8/12/2009



59 of 81

SMM-MSS-SIP-AC

6.9. Administer Phones

Scroll to the top of the screen, and select Device �� Phone, as shown below.

The Find and List Phones screen is displayed. Click Find.

The Find and List Phones screen is updated with a listing of all existing phones. Click on the

Device Name field for a phone that will use Avaya Modular Messaging for voice messaging

services.

JMC; Reviewed:

SPOC 8/12/2009



60 of 81

SMM-MSS-SIP-AC

The Phone Configuration screen is displayed next. Click the first directory number in the left

pane, in this case Line [1] – 6010 (no partition).

The Directory Number Configuration screen is displayed. Scroll down to the Directory

Number Settings section. For the Voice Mail Profile field, select the voice mail profile created

in Section 6.8 for Avaya Modular Messaging. Retain the default values in the remaining fields.

JMC; Reviewed:

SPOC 8/12/2009



61 of 81

SMM-MSS-SIP-AC

Scroll down to the Call Forward and Call Pickup Settings section. Check the call forward

related parameters as shown below.

Scroll down to the Forwarded Call Information Display on Device SEP0023049CDB32

section. Check all checkboxes, and click Save.

Repeat this section for all directory numbers on the phone and for all phones that will use Avaya

Modular Messaging for voice messaging services.

JMC; Reviewed:

SPOC 8/12/2009



62 of 81

SMM-MSS-SIP-AC

7. Avaya Modular Messaging Configuration upon Outage In the event of an outage at the Primary Avaya Modular Messaging site, call coverage will not be

available on the Secondary Site until the following actions are complete.

Change the FQDN of Avaya MSS and Avaya MAS on the DNS servers in the system to point to

the IP addresses of the Secondary Avaya MAS and Avaya MSS. Details of how to configure a

DNS server are outside the scope of these Application Notes. To ensure that changes in the DNS

are seen by AC1000, click the Device Actions��Reset followed by the Reset Button as shown

below. The AC1000 will then take about 60 seconds to reboot.

Log in to the Secondary Avaya MAS and change Register this connection’s addresses in DNS

on the DNS tab of the Advanced TCP/IP Settings described in Section 3.2.3 on Avaya MAS to

checked.

JMC; Reviewed:

SPOC 8/12/2009



63 of 81

SMM-MSS-SIP-AC

In order to ensure the Message Waiting Indicator (MWI) is correctly reflected on subscriber

handsets, an MWI update can be initiated using the Voice Mail System Configuration tool.

Select Message Waiting Indicator �� SMMLAB �� Start MWI Update… .

Select the Re-evaluate mailbox MWI rules for lamp state radio button to force an accurate

update of individual subscriber lamp states. Click OK.

JMC; Reviewed:

SPOC 8/12/2009



64 of 81

SMM-MSS-SIP-AC

8. Verification Steps Verification can be carried out in several points in the test system. These include:

• Verification of Avaya Modular Messaging

• Verify AudioCodes Mediant 1000 Gateway

• Verify Cisco 2811 MGCP Gateway and Cisco Unified Communications Manager

8.1. Verify Avaya Modular Messaging

Make a call from one subscriber to another and verify that the call covers to Avaya Modular

Messaging upon no answer. Leave a voice message for the subscriber. From that subscriber, dial

the Avaya Modular Messaging pilot number to retrieve the message. Verify that the Avaya

Modular Messaging system identifies the subscriber and that the voice message can be retrieved.

Log in to the Avaya Message Storage Server web interface as described in Section 3.1. Select

Logs �� Subscriber Activity from the left pane. Enter the mailbox number of the subscriber,

enter the appropriate date and time for the above activities, and click Display. Verify that a

listing of the detailed activities is displayed into the bottom portion of the right hand pane. Verify

that there is an entry showing the message being left and also verify that there is an entry

showing the message being retrieved.

Make a note of the subscriber options associated with that subscriber. For example note down if

‘Find Me’ or ‘Call Me’ features are enabled for that subscriber.

JMC; Reviewed:

SPOC 8/12/2009



65 of 81

SMM-MSS-SIP-AC

8.1.1. Verification at Secondary Site

Disconnect the Primary Avaya MM Servers and follow the procedure outlined in Section 7 on

how to modify configuration upon outage.

Place a call to the pilot number from the same subscriber’s phone used in this Section. Ensure

that the correct ‘Welcome’ message for that subscriber is played. This indicates that the caller is

recognized by the voicemail system. Compare the subscriber options associated with that

subscriber with those noted down in the previous section. Restore the Primary site by undoing

the steps carried out in this verification section.

8.2. Verify AudioCodes Mediant 1000 Gateway

To verify that the T1 trunk is correctly configured check that the status is green as shown below.

Click on the Status & Diagnostics tab and select Message Log. Dial the Pilot number from a

subscriber handset and check to see that the SIP messages are sent to Avaya Modular Messaging

with out error as shown.

JMC; Reviewed:

SPOC 8/12/2009



66 of 81

SMM-MSS-SIP-AC

8.3. Verify Cisco 2811 MGCP Gateway and Cisco Unified Communications Manager

From the Cisco 2811 MGCP Gateway command line interface, enter the show isdn status

command to verify connectivity. Verify that the Layer 1 Status is ACTIVE, and that the Layer

2 Status is MULTIPLE_FRAME_ESTABLISHED, as shown below.

2811#show isdn status Global ISDN Switchtype = primary-qsig

%Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may not apply

ISDN Serial0/0/0:23 interface

dsl 0, interface ISDN Switchtype = primary-qsig

**** Slave side configuration ****

L2 Protocol = Q.921 0x0000 L3 Protocol(s) = CCM MANAGER 0x0003

Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x8000003F

Number of L2 Discards = 1, L2 Session ID = 63

Total Allocated ISDN CCBs = 0

Enter the show ccm-manager command to verify the registration status with Cisco Unified

Communications Manager. Verify that the Status is Registered, and that the Host contains the

name administered in Section 5.2.

2811#show ccm-manager MGCP Domain Name: 2811.mm.com

Priority Status Host ============================================================

Primary Registered callmgr.avayalabs.com (10.10.5.100) First Backup None

Second Backup None

Current active Call Manager: 10.10.5.100

Backhaul/Redundant link port: 2428

Failover Interval: 30 seconds

Keepalive Interval: 15 seconds

Last keepalive sent: 14:01:36 UTC Mar 26 2009 (elapsed time: 00:00:03

)

Last MGCP traffic time: 14:01:36 UTC Mar 26 2009 (elapsed time: 00:00:03

)

Last failover time: None

Last switchback time: None

Switchback mode: Graceful

MGCP Fallback mode: Not Selected

Last MGCP Fallback start time: None

Last MGCP Fallback end time: None

MGCP Download Tones: Disabled

JMC; Reviewed:

SPOC 8/12/2009



67 of 81

SMM-MSS-SIP-AC

9. Conclusion As illustrated in these Application Notes, Avaya Survivable Modular Messaging utilizing Avaya

Message Storage Server (MSS) interoperates with AudioCodes Mediant 1000 for connectivity to

Cisco Unified Communications Manager in a MultiSite Environment.

10. Additional References This section references the product documentation relevant to these Application Notes.

1. Modular Messaging for the Avaya Message Store Server (MSS) Configuration Release

5.1 Installation and Upgrade, June 2009, available at http://support.avaya.com.

2. Modular Messaging for the Avaya Message Storage Server (MSS) Configuration -

Survivable Modular Messaging Guide. June 2009, available at http://support.avaya.com.

3. Modular Messaging MultiSite , June 2009, available at http://support.avaya.com.

4. Installing, Administering , Maintaining And Trouble Shooting Avaya AuraTM SIP

Enablement Services May 2009, available at http://support.avaya.com.

5. AudioCodes Mediant 1000 Configuration Note, Cisco Cisco Call Manager 4.1 available

at http://www.audiocodes.com/avaya

6. Cisco Unified Communications Manager and Cisco IOS Interoperability Configuration

Guide, available at http://www.cisco.com.

7. Cisco 2600 and 3600 Routers MGCP Voice Gateway Interoperability with Cisco

Communication Manager, available at http://www.cisco.com.

8. Cisco Unified Communications Manager Administration Guide, Release 7.0(1), available

at http://www.cisco.com

9. Acronis True Image Server 9.1 for Windows User Guide, available at

http://www.acronis.com.

JMC; Reviewed:

SPOC 8/12/2009



68 of 81

SMM-MSS-SIP-AC

11. Appendix A The configuration screens in this section are provided as a reference on how the Data Collection

Tool (DCT) file used to configure the Primary Avaya Modular Messaging Site in Figure 1 was

completed. Only screens relevant to this integration are shown.

JMC; Reviewed:

SPOC 8/12/2009



69 of 81

SMM-MSS-SIP-AC

JMC; Reviewed:

SPOC 8/12/2009



70 of 81

SMM-MSS-SIP-AC

JMC; Reviewed:

SPOC 8/12/2009



71 of 81

SMM-MSS-SIP-AC

JMC; Reviewed:

SPOC 8/12/2009



72 of 81

SMM-MSS-SIP-AC

JMC; Reviewed:

SPOC 8/12/2009



73 of 81

SMM-MSS-SIP-AC

JMC; Reviewed:

SPOC 8/12/2009



74 of 81

SMM-MSS-SIP-AC

JMC; Reviewed:

SPOC 8/12/2009



75 of 81

SMM-MSS-SIP-AC

JMC; Reviewed:

SPOC 8/12/2009



76 of 81

SMM-MSS-SIP-AC

12. Appendix B The INI file used to configure the AC1000 used in Figure 1 are provided here as a guide.

;************** ;** Ini File ** ;************** ;Board: Mediant 1000 ;Serial Number: 2003350 ;Slot Number: 1 ;Software Version: 5.60A.007.004 ;DSP Software Version: 624AE3 => 560.10 ;Board IP Address: 10.10.1.34 ;Board Subnet Mask: 255.255.255.0 ;Board Default Gateway: 10.10.1.1 ;Ram size: 128M Flash size: 32M ;Num DSPs: 12 Num DSP channels: 72 ;Profile: NONE ;Key features:;Board Type: Mediant 1000;IP Media: Conf VXML VoicePromptAnnounc(H248.9) ;PSTN Protocols: ISDN IUA=4 CAS ;DSP Voice features: EC128mSec AdditionTimeslotSummation FastSlowPlayback BargeIn PatternDetector IpmDetector ;E1Trunks=4;T1Trunks=4;Coders: G723 G729 NETCODER GSM-FR G727 ;Channel Type: RTP PCI DspCh=240 ;Security: IPSEC MediaEncryption StrongEncryption EncryptControlProtocol ;Control Protocols: MSFT MGCP MEGACO H323 SIP ;Default features:;Coders: G711 G726; ;------- Mediant-1000 HW components------- ; ; Slot # : Module type : # of ports ;----------------------------------------- ; 1 : FALC56 : 2 ; 2 : Empty ; 3 : Empty ; 4 : Empty ; 5 : Empty ; 6 : Empty ;----------------------------------------- [SYSTEM Params] DNSPriServerIP = 10.10.5.5 SyslogServerIP = 135.64.23.88 EnableSyslog = 1 TLSVersion = 1 [BSP Params] PCMLawSelect = 3 TDMBusClockSource = 4 StorageServerNetworkAddress = 255.255.255.255 [ATM Params] [Analog Params] MinFlashHookTime = 100 FXSLoopCharacteristicsFilename = 'M1K13-1-fxs16khz.dat' FXOLoopCharacteristicsFilename = 'M1K12-1-16khz-fxo.dat'

JMC; Reviewed:

SPOC 8/12/2009



77 of 81

SMM-MSS-SIP-AC

[ControlProtocols Params] AdminStateLockControl = 0 [MGCP Params] [MEGACO Params] EP_Num_0 = 0 EP_Num_1 = 1 EP_Num_2 = 0 EP_Num_3 = 0 EP_Num_4 = 0 [PSTN Params] TraceLevel = 1 ProtocolType_0 = 23 ProtocolType_1 = 0 TerminationSide_0 = 1 TerminationSide_1 = 0 FramingMethod_0 = D FramingMethod_1 = 0 LineCode_0 = 0 LineCode_1 = 2 ISDNIBehavior = 1073741824 ISDNGeneralCCBehavior = 32 PSTNReserved3 = 8 [SS7 Params] [Voice Engine Params] CallProgressTonesFilename = 'usa_tones_13.dat' IdlePCMPattern = 85 ECNLPMode = 1 BrokenConnectionEventTimeout = 3 FaxModemBypassCoderType = 1 DTMFDetectorSensitivity = 1 AggressiveDTMFErasure = 770 TTYTRANSPORTTYPE = 1 [WEB Params] HTTPSCipherString = 'RC4:EXP' [SIP Params] ISPROXYUSED = 1 SIPDESTINATIONPORT = 5061 CHANNELSELECTMODE = 2 GWDEBUGLEVEL = 5 ISDNRXOVERLAP_0 = 1 ISDNRXOVERLAP_1 = 0 ISDNRXOVERLAP_2 = 0 ISDNRXOVERLAP_3 = 0 ISDNRXOVERLAP_4 = 0 ISDNRXOVERLAP_5 = 0 ISDNRXOVERLAP_6 = 0

JMC; Reviewed:

SPOC 8/12/2009



78 of 81

SMM-MSS-SIP-AC

ISDNRXOVERLAP_7 = 0 ISDNRXOVERLAP_8 = 0 ISDNRXOVERLAP_9 = 0 ISDNRXOVERLAP_10 = 0 ISDNRXOVERLAP_11 = 0 ISDNRXOVERLAP_12 = 0 ISDNRXOVERLAP_13 = 0 ISDNRXOVERLAP_14 = 0 ISDNRXOVERLAP_15 = 0 ISDNRXOVERLAP_16 = 0 ISDNRXOVERLAP_17 = 0 ISDNRXOVERLAP_18 = 0 ISDNRXOVERLAP_19 = 0 DEFAULTNUMBER = 'serveduser' SIPGATEWAYNAME = 'ac1000.avayalabs.com' DISCONNECTONBROKENCONNECTION = 0 ENABLEMWI = 1 ISFAXUSED = 1 VoiceMailInterface = 3 SUBSCRIPTIONMODE = 1 SIPTRANSPORTTYPE = 2 PLAYRBTONE2TRUNK_0 = 0 PLAYRBTONE2TRUNK_1 = -1 PLAYRBTONE2TRUNK_2 = -1 PLAYRBTONE2TRUNK_3 = -1 PLAYRBTONE2TRUNK_4 = -1 PLAYRBTONE2TRUNK_5 = -1 PLAYRBTONE2TRUNK_6 = -1 PLAYRBTONE2TRUNK_7 = -1 PLAYRBTONE2TRUNK_8 = -1 PLAYRBTONE2TRUNK_9 = -1 PLAYRBTONE2TRUNK_10 = -1 PLAYRBTONE2TRUNK_11 = -1 PLAYRBTONE2TRUNK_12 = -1 PLAYRBTONE2TRUNK_13 = -1 PLAYRBTONE2TRUNK_14 = -1 PLAYRBTONE2TRUNK_15 = -1 PLAYRBTONE2TRUNK_16 = -1 PLAYRBTONE2TRUNK_17 = -1 PLAYRBTONE2TRUNK_18 = -1 PLAYRBTONE2TRUNK_19 = -1 MEDIASECURITYBEHAVIOUR = 1 DIGITALOOSBEHAVIORFORTRUNK_0 = 0 DIGITALOOSBEHAVIORFORTRUNK_1 = -1 DIGITALOOSBEHAVIORFORTRUNK_2 = -1 DIGITALOOSBEHAVIORFORTRUNK_3 = -1 DIGITALOOSBEHAVIORFORTRUNK_4 = -1 DIGITALOOSBEHAVIORFORTRUNK_5 = -1 DIGITALOOSBEHAVIORFORTRUNK_6 = -1 DIGITALOOSBEHAVIORFORTRUNK_7 = -1 DIGITALOOSBEHAVIORFORTRUNK_8 = -1 DIGITALOOSBEHAVIORFORTRUNK_9 = -1 DIGITALOOSBEHAVIORFORTRUNK_10 = -1 DIGITALOOSBEHAVIORFORTRUNK_11 = -1 DIGITALOOSBEHAVIORFORTRUNK_12 = -1 DIGITALOOSBEHAVIORFORTRUNK_13 = -1 DIGITALOOSBEHAVIORFORTRUNK_14 = -1 DIGITALOOSBEHAVIORFORTRUNK_15 = -1 DIGITALOOSBEHAVIORFORTRUNK_16 = -1 DIGITALOOSBEHAVIORFORTRUNK_17 = -1 DIGITALOOSBEHAVIORFORTRUNK_18 = -1 DIGITALOOSBEHAVIORFORTRUNK_19 = -1

JMC; Reviewed:

SPOC 8/12/2009



79 of 81

SMM-MSS-SIP-AC

[SCTP Params] [VXML Params] [IPsec Params] [Audio Staging Params] VideoEnableTestPattern = 1 VideoRateControlType = 0 ; ; *** TABLE DspTemplates *** ; This table contains hidden elements and will not be exposed. ; This table exists on board and will be saved during restarts ; ; ; *** TABLE CoderName *** ; ; [ CoderName ] FORMAT CoderName_Index = CoderName_Type, CoderName_PacketInterval, CoderName_rate, CoderName_PayloadType, CoderName_Sce; CoderName 0 = g711Ulaw64k, 20, 0, 255, 0; [ \CoderName ] ; ; *** TABLE TrunkGroup *** ; ; [ TrunkGroup ] FORMAT TrunkGroup_Index = TrunkGroup_TrunkGroupNum, TrunkGroup_FirstTrunkId, TrunkGroup_FirstBChannel, TrunkGroup_LastBChannel, TrunkGroup_FirstPhoneNumber, TrunkGroup_ProfileId, TrunkGroup_LastTrunkId, TrunkGroup_Module; TrunkGroup 0 = 0, 0, 1, 24, 4299, 0, 0, 1; [ \TrunkGroup ] ; ; *** TABLE Dns2Ip *** ; ; [ Dns2Ip ] FORMAT Dns2Ip_Index = Dns2Ip_DomainName, Dns2Ip_FirstIpAddress, Dns2Ip_SecondIpAddress, Dns2Ip_ThirdIpAddress, Dns2Ip_FourthIpAddress; Dns2Ip 0 = anonymous.invalid, 10.10.1.34, 0.0.0.0, 0.0.0.0, 0.0.0.0; Dns2Ip 1 = stockleyg3.com, 10.10.1.34, 0.0.0.0, 0.0.0.0, 0.0.0.0; [ \Dns2Ip ] ; ; *** TABLE ProxyIp *** ;

JMC; Reviewed:

SPOC 8/12/2009



80 of 81

SMM-MSS-SIP-AC

; [ ProxyIp ] FORMAT ProxyIp_Index = ProxyIp_IpAddress, ProxyIp_TransportType, ProxyIp_ProxySetId; ProxyIp 0 = mascp2.avayalabs.com, 2, 0; [ \ProxyIp ] ; ; *** TABLE TxDtmfOption *** ; ; [ TxDtmfOption ] FORMAT TxDtmfOption_Index = TxDtmfOption_Type; TxDtmfOption 0 = 4; [ \TxDtmfOption ] ; ; *** TABLE ProxySet *** ; ; [ ProxySet ] FORMAT ProxySet_Index = ProxySet_EnableProxyKeepAlive, ProxySet_ProxyKeepAliveTime, ProxySet_ProxyLoadBalancingMethod, ProxySet_IsProxyHotSwap; ProxySet 0 = 0, 60, 0, 0; [ \ProxySet ]

JMC; Reviewed:

SPOC 8/12/2009



81 of 81

SMM-MSS-SIP-AC


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. The configurations, technical data, and

recommendations provided in these Application Notes are believed to be accurate and

dependable, but are presented without express or implied warranty. Users are responsible for

their application of any products specified in these Application Notes.

Please e-mail any questions or comments pertaining to these Application Notes along with the

full title name and filename, located in the lower right corner, directly to the Avaya Solution &

Interoperability Test Lab at [email protected]

Date post:	09-Aug-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

Application Notes for Configuring a Survivable Modular … · In the event of a disaster or...

Documents