Deploy Avaya CMM with ease, step by step configuration.

In this blog post ‘Deploy Avaya CMM with ease, step by step configuration’ I walk you through step by step how to configure the Avaya Aura Communications Manager Messaging. CMM or the legacy IA770 is an embedded voicemail solution with the old Audix voiccemail prompts, features and functionalities.

Years ago when Avaya integrated the IA770 with CM as part of one solution without the need of adding hardware onto the S8300 Server Blade, we were rushed to learn the integration pretty fast without formal training. After exercising different implementation methods, I came up with these steps that once helped me deploy the embedded voicemail. I hope that you find them useful.

For a successful CMM installation follow these steps=

• 1.- Verify Features and Licenses
• 2.- Create a DAC and FAC for Voicemail and trunk access
• 3.- Setting internal Parameters for messaging
• 4.- Local node number
• 5.- Setup the Node Names
• 6.- System Parameter coverage
• 7.- Add a signaling trunk group
• 8.- Add a new Trunk Group
• 9.- Configure the Signaling Group for Messaging
• 10.- AAR /ARS Digit Conversion
• 11.- Create a new route pattern
• 12.- Change AAR Analysis 5199 (enter desired number)
• 13.- Creating a Hunt Group for Messaging
• 14.- Adding a Coverage Path for Messaging
• 15.- Create the system extensions
• 16.- Configuring AI770 through the web browser
• 17.- Using ASA or CLI to complete the Voicemail configuration

  

1.- Verify all the features and licenses

Before the initial implementation it is very important to have the correct RTUs activated. Check with the sales engineer or yourself by going through the PLDS or RFA portals. After confirming the purchased licenses, run this command=

Display system-parameters customer-options

• Page 2 Maximum Administered H.323 trunks (needs to match the number of VM ports)
• Page 3 ARS and ARS/AAR are flagged to yes
• Page 4 IP Trunks and ISDN-PRI flagged t yes
• Page 5 Private Networking, Processor Ethernet and UDP flagged to yes
• Page 8 Basic call setup, Basic supplementary services, Supplementary Services with routing, transfer into QSIG voice mail, and Value-Added set to yes

Press cancel to exit.

2.- Create a FAC and DAC to access voicemail and trunk groups

Feature Access Codes and Dial Access Codes are commands configured under the Avaya Communications Manager (CM) to access its components as part of CM’s Dial Plan Tables. Run the following command=

change dialplan ana 0

8 = FAC to dial AAR

5199= FAC VM Pilot number 

Once the Dial Plan is created, go to the system feature access codes and create a AAR access code by running this command=

change features-access-codes

Insert an 8 under AAR

3.- Setting internal Parameters for messaging

Configure the system’s parameters-features by running=

Change system-parameters features

Page 1 trunk to trunk transfer set to all

Page 8 enter the QSIG/ETSI TSC Extension number 5198 (integrates the vm and pbx)

MWI-Number of digits per voicemail

Subscriber= 4 (mailbox ext range)

Unknown numbers considered internal

For AUDIX= y Maximum Length= 4

QSIG Path Replacement extension=

5197 (it has to be a number greater or

Lesser than the QSIG/ETSI TSC Ext

Path replace while in queue/vector= y

4.- Local node number

Each system has to have a node number associated with it

Change dialplan parameters

Local node number= 1

Setup the Node Names

5.- Node Names

In order to allow communication between elements or components, the Avaya Aura system utilizes the node names to allow the association of IP Addresses to Names for better troubleshooting and identification.

Change node-names ip

msgserver=  CMM  // procr= s8300

IP Interfaces

For  both S8300 and S8400 Servers, need to be configured under the IP-Interfaces Procs

change ip-i proc

  6.- System Parameters Coverage

Change system-parameters coverage-forwarding

Page 1 Coverage- caller response interval = 1, threshold for blocking off-net redirection of incoming trunk calls= n, keep held sba at coverage point?= n, Maintain SBA At principal= n

  7.- Add a signaling trunk group

Add sig 99

Group type= h.323

Remote office= n

Max number of NCA TSC= 10

Max number of CA TSC= 10

Trunk Group for NCA TSC= Blank

Trunk Group for Channel S.= Blank

TSC Supplementary Service P.= b

Near-end Node Name= procr

Far-end Node Name= msgserver

Near-end Listen port= 1720

Far-end Listen port= 1720

Far-end network region= 1

Calls share IP Signaling Connection= y DTMF over IP= Out of band

Enable Layer 3 test= n                          Direct IP-IP Audio connections= y

Interworking message= PROGress

If using different far end network region. Change-network-region <n> Verify that intra-region IP-IP Direct Audio set to yes, inter-region IP-IP Direct Audio set to yes and IP Audio Hairpining is set to n. (refer to the  IA770 Docs)

Verifying the messaging settings on the media gateway

Change media-gateway 1, remove the messaging analog from V8 if present

See Page 19 of System Features to match

8.- Add a new Trunk Group

Add trunk-group 99

Group Type= isdn

Group Name= msgserver

Carrier Medium= H.323

COR= 1

Dial Access=     y

Service Type= tie

Outgoing Display= n

Member Assignment Method= auto

Signaling Group= 99

Number of member= 10 (license ports purchased) display system-parameters customer-options on page two IP PORT CAPACITIES Maximum Administered H.323 Trunks= 10. TAC= 199.

Go to page 2 supplementary service protocol= b, Digit Handling (in/out)= enbloc/enbloc, Format= pub-unk, Disconnect Supervision – In= y, out?= n .

Go to page 3 Send Name=n, NCA-TSC Trunk Member=1, Send Calling Number= y, Format=Private.

Go to Page 4 Path Replacement with Retention= n, Path Replacement Method=better-route, Qsig Value-added=y

9.- Configure the Signaling Group for Messaging

Under Trunk Group for NCA TSC and Trunk Group for Channel Selection assign the messaging trunk group previously created= 99

10.- AAR /ARS Digit Conversion

Depending on the format field on page 3 in the trunk group form you must translate the AAR and ARS Digit Conversion tables.

Format=private

If using Public, unknown and

Unk-Pvt see the Avaya Aura CMM DOCS

Chang AAR Digit-conversion 0

Matching Pattern= 5

min=4, max=4, del=0

Net= ext, conv=y, Req=n

11.- Create a route pattern for the new trunk group

Add route 99

Pattern Name= msgserver

Group No.= 99

FRL= 0

DCS/QSIG Intw= n

IXC= user

BCC Value 01234W= yyyyyn

TSC= y

TSC=y

CA-TSC Request= none

ITC= rest

LAR= rehu

*Once saved change the CA-TSC Request to as-needed

12.- Change AAR Analysis 5199 (VM Pilot Number)

Enter the command ‘cha aar ana 5199’ (5199= vm access code)

Dialed String= 5199

Min=4 Max= 4

Route Pattern= 99

Call Type= aar

Change Public-Unknown-Numbering (if using private numbering then use ‘private’ instead.)

Ext Length= 4

Ext Code= 5

Trunk Group= 99

CPN Length= 4

13.- Creating a Hunt Group for Messaging

The voicemail number will be associated with a Hunt Group. run the command=

Add Hunt-group 99

Group Name= msgserver

Group Ext= 5199

Group Type= ucd-mia

COR= 1

Message Center= qsig-mwi

Send Reroute Request= y

Voice Main Number= 5199

Routing Digits AAR/ARS Access

Code= 8

14.- Adding a Coverage Path for Messaging

Add Coverage Path 99

Number of rings= 4

Point1= h99

I used Coverage path 3 on this one

15.- Create the system extensions

This is assuming that your system is new, and you don’t have any stations currently assigned.

Add station 5102 (Might need to update the dialplan to match the extension range.).

Assign coverage path 99

Message Lamp= 5102

On PAGE 2

LWC Reception= spe

LWC Activation?= y

MWI served user type= qsig-mwi

Save trans

16.- Configuring AI770 through the web browser

Open http://192.11.13.6

Browse to Administration/Messaging/switch link ID

Switch Number= 1

Extension Length= 4

Switch IP Address= CM’s IP Address (S8300) for newer versions the CMM IP Address will be entered here using the same CM’s IP Address but different network port numbers.

Voice Ports= 10 Max= 12, Trunks= 16      Max= 18, Transfer Ports= 6, Call Center PHB= 46, Audio PHB= 46.

Restart Messaging

Stop and Start Messaging under Administration/Messasging/Utilities Stop and Start Messaging.

17.- Using ASA or CLI to complete the Voicemail configuration

Using ASA Login into the AUDIX run the command “change machine”

Machine Name= msgserver, Machine Type= tcpip, Voiced name= n, Extension length= 4, Voice ID= 0, Default Community= 1, Location= local, Address Ranges= 0000-9999

Go to page two verify the media Server IP Address is correct

Adding subscriber

Add sub 5200, Name= Day Attendant, Extension= 5200, COS= Custom

Go to 2 page

Under Permissions type= Auto-attendant, Announcement control= y

On Page 3

Allow call transfer= y, Depending the customer, Modify the button, extension, and Treatment

Route calls right to voicemail

Change auto-attend-routing-table

Incoming Called Number= 5200

Business Schedule= bus1 (need to be configured)

Holiday Schedule= hol1 (need to be configured)

Day Service mbox= 5200

Night Service mbox= 5200

Question – How about you? – When deploying CMM which steps do you normally follow?