Application Notes - Avaya DevConnect

Avaya Solution & Interoperability Test Lab
Application Notes for FCS VoiceMail and Avaya
Communication Manager - Issue 1.0
Abstract
These Application Notes describe the procedures for configuring FCS VoiceMail to
interoperate with Avaya Communication Manager. FCS VoiceMail is a Windows-based
Voice Messaging system designed specifically for Hospitality environments
Information in these Application Notes has been obtained through DeveloperConnection
compliance testing and additional technical discussions. Testing was conducted via the
DeveloperConnection Program at the Avaya Solution and Interoperability Test Lab.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
1 of 23
CM-FCSVM
1. Introduction
These Application Notes describe the procedures for configuring FCS VoiceMail to interoperate
with Avaya Communication Manager. FCS VoiceMail is a Windows-based Voice Messaging
system designed specifically for Hospitality environments. It works seamlessly with a hotel’s
Avaya Communication Manager and Property Management System. In addition to providing
standard Voice Messaging functionality, FCS VoiceMail integrates with FCS WinSuite 1 (a
Windows-based Hospitality system that provides a real-time multitasking interface between a
PBX and a hotel’s Property Management System) to support standard Hospitality feature
requests as Automatic Wake-Up (AWU), Housekeeping/Room Status changes, and Minibar
charge postings.
The configuration used in performing compliance testing of FCS VoiceMail is shown in Figure
1. It shows a network consisting primarily of a pair of Avaya S8720 Servers running Avaya
Communication Manager in a High Reliability configuration with two Avaya G650 Media
Gateways, an FCS Voicemail server, and Avaya 4626 2 and 9640 IP Telephones (representing
guest telephones). In addition, FCS WinSuite1 was used to exercise specific capabilities in FCS
VoiceMail. Analog and digital ports on the corresponding Intel Dialogic cards in the FCS
VoiceMail server connect to ports on one of the Avaya G650 Media Gateways.
Figure 1: Sample Test Configuration
1
2
Configuration details for this product can be found in [2].
This telephone was designed and developed specifically for Hospitality environments.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
2 of 23
CM-FCSVM
2. Equipment and Software Validated
The following equipment and software were used for the sample configuration provided:
Equipment
Avaya S8720 Server
Avaya G650 Media Gateway
• TN799DP C-LAN
• TN2312AP IPSI
• TN2302AP MedPro
• TN2224CP 2-Wire
Digital
• TN464HP DS1
• TN746B Analog Line
Avaya 4626 IP Telephone
Avaya 9640 IP Telephone
FCS VoiceMail Server
Hardware/Firmware/Software
Version
Avaya Communication Manager
4.0.1 (R014x.00.1.731.2)
26.31.0
HW01 FW156
HW15 FW039
HW02 FW142
HW08 FW015
HW02 FW019
000019
2.4
S1.5
4.0.0 (with Windows 2003
Server SP 2)
• Dialogic 4-port Analog HW D4PCIUFW
Line Card
• Dialogic Digital Line
Card
FCS WinSuite Server
3.0.8 (with Windows 2003
Server SP 2)
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
3 of 23
CM-FCSVM
3. Configure Avaya Communication Manager
This section details the steps required to configure Avaya Communication Manager to
interoperate with FCS VoiceMail. These Application Notes assume the Avaya Media Gateways
(including circuit packs) have already been administered. Please refer to [1] for additional
details.
The commands listed in this section were issued at the Avaya System Access Terminal (SAT)
screen. For all steps where data are modified, submit the completed administration form for the
changes to take effect.
Step
1.
Description
Enable Mode Code interface:
Since FCS VoiceMail sends signaling information to Avaya Communication Manager
inband using DTMF tones that are interpreted as Mode Codes, this feature must be enabled
in Avaya Communication Manager. Enter change system-parameters features, advance
to Page 6, and set the Mode Code Interface? parameter to y, as shown below:
change system-parameters features
Page
6 of 17
FEATURE-RELATED SYSTEM PARAMETERS
Public Network Trunks on Conference Call: 5
Auto Start? n
Conference Parties with Public Network Trunks: 6
Auto Hold? n
Conference Parties without Public Network Trunks: 6
Attendant Tone? y
Night Service Disconnect Timer (seconds): 180
Bridging Tone? n
Short Interdigit Timer (seconds): 3
Conference Tone? n
Unanswered DID Call Timer (seconds):
Intrusion Tone? n
Line Intercept Tone Timer (seconds): 30
Mode Code Interface? y
Long Hold Recall Timer (seconds): 0
Reset Shift Timer (seconds): 0
Station Call Transfer Recall Timer (seconds): 0
Recall from VDN? n
DID Busy Treatment: tone
Allow AAR/ARS Access from DID/DIOD?
Allow ANI Restriction on AAR/ARS?
Use Trunk COR for Outgoing Trunk Disconnect?
7405ND Numeric Terminal Display?
DISTINCTIVE AUDIBLE ALERTING
Internal: 1
External: 2
Priority:
Attendant Originated Calls:
DTMF Tone Feedback Signal to VRU - Connection:
DAH; Reviewed:
SPOC 8/25/2007
y
y
n
n
7434ND? y
3
external
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
Disconnection:
4 of 23
CM-FCSVM
Step
2.
Description
Set Mode Code parameters:
Enter change system-parameters mode-codes and ensure that values are entered in the
following fields (these values will be passed to FCS Voicemail as appropriate):
•
•
•
•
Direct Inside Access
Direct Dial Access – Trunk (only needed if DID service is provided to guest
extensions)
Internal Coverage
External Coverage (only needed if DID service is provided to guest extensions)
In addition, enter the following values into the fields indicated to enable FCS VoiceMail to
interpret incoming Mode Codes properly:
•
•
DTMF Duration – Off (msec): 150
Sending Delay (msec): 200
change system-parameters mode-code
MODE CODE RELATED SYSTEM PARAMETERS
Page
1 of
1
MODE CODES (FROM SWITCH TO VMS)
Direct Inside Access: #00
Direct Dial Access - Trunk: #01
Internal Coverage: #02
External Coverage: #03
Refresh MW Lamp: #06
System In Day Service: #11
System In Night Service: #12
OTHER RELATED PARAMETERS
DTMF Duration - On (msec): 100
Off (msec): 150
VMS Hunt Group Extension:
Remote VMS Extensions - First:
DAH; Reviewed:
SPOC 8/25/2007
Sending Delay (msec): 200
Second:
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
5 of 23
CM-FCSVM
Step
3.
Description
Set feature access codes to allow Message Waiting Lamp (MWL) activation/deactivation:
Enter change feature-access-codes and advance to Page 3. Enter values for Leave Word
Calling Send A Message and Leave Word Calling Cancel A Message that are consistent
with the administered dial plan. These feature access codes (FACs) will be used by FCS
VoiceMail to activate and deactivate the MWLs on users’ stations, to be administered in
FCS VoiceMail in Section 4, Step 10.
change feature-access-codes
Page
FEATURE ACCESS CODE (FAC)
Leave Word Calling Send A Message: *66
Leave Word Calling Cancel A Message: *67
Limit Number of Concurrent Calls Activation:
Deactivation:
Malicious Call Trace Activation:
Deactivation:
Meet-me Conference Access Code Change:
PASTE (Display PBX data on Phone) Access
Personal Station Access (PSA) Associate
Per Call CPN Blocking Code Access
Per Call CPN Unblocking Code Access
Code:
Code:
Code:
Code:
3 of
7
Dissociate Code:
Priority Calling Access Code:
Program Access Code:
Refresh Terminal Parameters Access Code:
Remote Send All Calls Activation:
Self Station Display Activation:
Send All Calls Activation:
Station Firmware Download Access Code:
DAH; Reviewed:
SPOC 8/25/2007
Deactivation:
Deactivation:
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
6 of 23
CM-FCSVM
Step
4.
Description
Administer analog ports to FCS Voicemail as Voice Mail Interface (VMI) stations:
(NOTE: Steps 4 and 5 should only be completed if analog lines are used between FCS
VoiceMail and Avaya Communication Manager.)
Enter add station x (where x is a valid unused extension) and specify the following values:
•
•
•
Type: VMI.
Port: A port on the analog line card that is connected to FCS Voicemail.
Name: A descriptive name (in this case, FCS Voicemail).
add station 40011
Page
1 of
4
STATION
Extension:
Type:
Port:
Name:
40011
VMI
01B0404
FCS VoiceMail
Lock Messages? n
Security Code:
BCC:
TN:
COR:
COS:
Tests?
0
1
1
1
y
STATION OPTIONS
Time of Day Lock Table:
Loss Group: 1
Off Premises Station? n
Survivable COR: internal
Survivable Trunk Dest? Y
5.
Repeat Step 4 to add additional VMI stations for each of the analog ports connected to FCS
VoiceMail.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
7 of 23
CM-FCSVM
Step
6.
Description
Administer digital ports to FCS Voicemail as 8434D stations:
(NOTE: Steps 6 and 7 should only be completed if digital lines are used between FCS
VoiceMail and Avaya Communication Manager.)
Enter add station x (where x is a valid unused extension) and specify the following values:
•
•
•
Type: 8434D.
Port: A port on the digital line card that is connected to FCS Voicemail.
Name: A descriptive name (in this case, FCS Voicemail Digital 1).
add station 40021
Page
1 of
6
STATION
Extension:
Type:
Port:
Name:
40021
8434D
01B0801
FCS VoiceMail Digital 1
Lock Messages? n
Security Code:
Coverage Path 1:
Coverage Path 2:
Hunt-to Station:
BCC:
TN:
COR:
COS:
0
1
1
1
STATION OPTIONS
Loss Group:
Data Module?
Speakerphone:
Display Language:
2
n
2-way
english
Survivable COR: internal
Survivable Trunk Dest? y
Time of Day Lock Table:
Personalized Ringing Pattern:
Message Lamp Ext:
Mute Button Enabled?
Expansion Module?
1
40021
y
n
Media Complex Ext:
IP SoftPhone? N
7.
Repeat Step 6 to add additional 8434D stations for each of the digital ports connected to
FCS VoiceMail.
8.
Create a hunt group containing the desired set of stations created in Steps 4-6, and add this
hunt group extension as the primary coverage point in the coverage path that will be used by
Avaya Communication Manager to direct coverage calls for guest extensions to FCS
Voicemail.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
8 of 23
CM-FCSVM
4. Configure FCS Voicemail
This section details the steps required to configure FCS VoiceMail to interoperate with Avaya
Communication Manager. These Application Notes assume that the FCS Voicemail application
has already been properly installed by FCS services personnel.
Step
1.
Description
Open the FCS VoiceMail administration client. In the VoiceMail screen that is presented,
click the icon to the upper left (illustrated below) to launch the FCS VoiceMail Web GUI
login screen.
.
2.
In the Login to FCS Voicemail screen, login with the appropriate administrator credentials.
3.
At the subsequent administrative menu, select the link for System Configuration to launch
the System Configuration screen.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
9 of 23
CM-FCSVM
Step
4.
Description
Configure channels by line type:
In the Line Type Setting form that is presented, enter the following values:
•
•
•
•
No. of Line(s): The number of lines to be configured as the desired Line
Type (in this example, 1).
Line Type: Select the desired value from the drop-down (in this example,
VoiceMail lines are being configured).
Language: Select the language to be provided by FCS VoiceMail in prompts
to the user (in this example, ENGLISH).
AWU, MWL: Check these boxes if these lines are to be used for making
AWU calls or activating MWLs.
Click Add to submit the form.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
10 of 23
CM-FCSVM
Step
5.
Description
Add extension detail to lines:
The System Configuration screen that follows includes a table listing the lines that have
been configured. Select the Edit link next to one of the lines; a modified version of the
form from Step 4 is presented (see below). In the Extn No field, enter the extension
number corresponding to the port from Avaya Communication Manager connected to the
Dialogic card in the FCS VoiceMail server (in the example shown below, 40011) preceded
by the DTMF digits and pauses representing the expected Mode Code (in this case, “0,0,”).
Click Update to submit the form.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
11 of 23
CM-FCSVM
Step
6.
Description
Repeat Steps 4 and 6 until all lines have been defined and configured. The complete table
of all lines and their configured parameters, such as the one shown below, is presented.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
12 of 23
CM-FCSVM
Step
7.
Description
Add entry points:
Entry points map the expected sequences of leading DTMF digits to actions to be taken by
FCS VoiceMail. To define an entry point, select Entry Point from the System
Configuration menu in the left pane. Enter values in the associated fields as follows:
•
•
CPI Format: Enter the sequence that will match this entry point (in this
example, *10).
Description: Select the desired action to be associated with this entry point. In
this example LEAVE MAILBOX (entered by the hotel operator after recording
and sending a message to a guest mailbox) is selected. Other valid values
include:
o RETRIEVE COGMAILBOX (to allow the hotel operator to
retrieve a guest mailbox’s messages from any phone)
o RETRIEVE ROOM (to allow the hotel operator to retrieve
messages from a mailbox associated with a checked-out guest
telephone)
o DIDRETRIEVE (specifying the sequence of DTMF digits signaling
a retrieval of messages from a checked-in guest telephone)
o NOANSWER (specifying the sequence of DTMF digits signaling a
coverage call redirected from an unanswered guest telephone)
Click Add to submit the form.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
13 of 23
CM-FCSVM
Step
8.
Description
Repeat Step 7 to enter the entry points corresponding to all of the expected types of
incoming calls. The resultant table of entry points is presented as shown below.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
14 of 23
CM-FCSVM
Step
9.
Description
Set parameters for receiving Called Party ID (CPI) on incoming calls:
Select PABX Setting from the System Configuration menu in the left pane. For each of
the fields shown, click Edit and enter the following values:
•
•
CPI Type: Select DTMF (indicating CPI is sent via in-band signaling) from the
drop-down menu.
CPI Delay: Leave the default for this field (does not apply to in-band signaling
of CPI).
Click Save in each case to accept the new value.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
15 of 23
CM-FCSVM
Step
10.
Description
Set Message Waiting Lamp control parameters:
From the System Configuration menu in the left pane, select General Setting. Under the
MESSAGE WAITING LAMP section, enter the following values in the fields indicated:
•
•
•
•
Admin: PABX (from the drop-down menu), indicating that the MWLs on
administrator’s telephones will be set using DTMF tones over the voice ports to
Avaya Communication Manager.
Guest: PMS (from the drop-down menu), indicating that the MWLs on guest
telephones will be set via the PMS data link.
OnCode: The value for the Leave Word Calling Send A Message FAC
administered in Section 3, Step 3 (in this example, *66).
OffCode: The value for the Leave Word Calling Cancel A Message FAC
administered in Section 3, Step 3 (in this example, *67).
Click Update to submit the form. The completed screen is shown below.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
16 of 23
CM-FCSVM
Step
11.
Description
Define the hotel operator extensions:
From the System Configuration menu in the left pane, select Operator Setting. Enter the
station extensions in Avaya Communication Manager that correspond to the Day Operator,
Night Operator and Message Desk, respectively. Click Save to submit the form.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
17 of 23
CM-FCSVM
Step
12.
Description
Add guest mailboxes:
From the System Configuration menu in the left pane, select Guest Mailbox Setup.
Populate the fields in the form as follows:
•
•
•
DAH; Reviewed:
SPOC 8/25/2007
Room No. From, Room No. To: Enter a range of room numbers to be matched
in sequence with the extensions administered in the Extension fields below (up
to 10 at a time).
Floor No.: Enter the floor in the hotel where the indicated range of rooms is
located.
Extension 1-Extension 10: Enter the extension numbers of the guest telephones
in the rooms falling in the range specified above.
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
18 of 23
CM-FCSVM
Step
Description
13.
Click the Create button to create the guest mailboxes specified. A list of RoomNO |
ExtnNO pairs corresponding to the created mailboxes is displayed in the text box below the
administered fields, as shown below.
14.
Repeat Steps 12 and 13 until mailboxes have been created for all guest extensions.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
19 of 23
CM-FCSVM
Step
15.
Description
Create administrator mailboxes:
From the System Configuration menu in the left pane, select Admin Mailbox Setup.
Populate the fields in the form as follows:
•
•
•
•
•
Extn Range: Enter a range indicating the number of mailbox extensions to be
created by this instance of the form (in this case, 1).
Extn Type: Select MAILBOX from the drop-down menu.
Language: Select the appropriate language to be used to provide user prompts
(in this case, ENGLISH).
Extension1-Extension5: Enter up to 5 mailbox extensions.
Multiple Mailbox Single Extension: Check this box if a single administrator
station will have multiple mailboxes associated with it.
Click Create to submit the form.
16.
Repeat Step 15 until all administrator mailboxes have been created.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
20 of 23
CM-FCSVM
Step
17.
Description
To view a list of all mailboxes that have been created, select View/Delete Extension List
from the System Configuration menu in the left pane. An example from the test
configuration is shown below.
5. Interoperability Compliance Testing
Interoperability compliance testing focused on FCS VoiceMail’s ability to work with Avaya
Communication Manager. FCS VoiceMail features and capabilities that were verified included
the following: voice message delivery/retrieval/deletion and associated MWL
activation/deactivation, recording of personal greetings for guest mailboxes, changing of guest
mailbox’s PIN/password, setting/cancelling AWU calls, and Housekeeping/Room Status and
Minibar updates initiated at guest telephones.
5.1. General Test Approach
Feature functionality testing was performed manually. Inbound calls were made to the Avaya
4626 and 9640 IP Telephones (i.e. the guest telephones) over T1/PRI trunks, as well as from
other local extensions (analog, digital, and IP Telephone).
5.2. Test Results
All executed test cases were completed successfully.
6. Verification Steps
This section describes steps that may be used to verify the configuration.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
21 of 23
CM-FCSVM
Step
Description
1.
Call the FCS VoiceMail hunt group extension from a checked-in guest telephone. Verify
that an announcement summarizing the number of messages in the associated guest mailbox
is played, without the need for entering a mailbox extension or password.
2.
Call the FCS VoiceMail hunt group extension from a checked-out guest telephone. Verify
that the caller is prompted for a mailbox extension and, once such an extension is provided,
a password.
3.
From a checked-in guest telephone, dial the extension of an FCS VoiceMail port that
supports AWU. Follow the prompts to request a wake-up call for an upcoming time.
Verify that the AWU call is launched to the guest telephone at the appropriate time.
4.
From a checked-in guest telephone, dial the extension of an FCS VoiceMail port that
supports Minibar and Room Status updates. Follow the prompts to submit Minibar charges
and Room Status changes. Verify using FCS WinSuite that the data are posted accurately.
7. Support
Tor technical support on FCS VoiceMail, contact FCS Computer Systems at
http://www.fcscs.com/support.htm.
8. Conclusion
These Application Notes describe the procedures for configuring FCS VoiceMail to interoperate
with Avaya Communication Manager. All interoperability compliance test cases executed
against such a configuration were completed successfully.
9. Additional References
1. “Administration for Network Connectivity for Avaya Communication Manager,”
Document ID 555-233-504.
2. “Application Notes for FCS WinSuite with Avaya Communication Manager.”
Additional product documentation may be found at the following sites:
•
•
Avaya: http://support.avaya.com
FCS: http://www.fcscs.com
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
22 of 23
CM-FCSVM
©2007 Avaya Inc. All Rights Reserved.
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
DeveloperConnection Program at devconnect@avaya.com.
DAH; Reviewed:
SPOC 8/25/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
23 of 23
CM-FCSVM