Avaya Hospitality Messaging Server 400

Maintenance

Release 2.0
NN42350-101, 05.06
December 2010
© 2010 Avaya Inc. Copyright

All Rights Reserved. Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, or Hardware
Notice provided by Avaya. All content on this site, the documentation and the
Product provided by Avaya including the selection, arrangement and
While reasonable efforts have been made to ensure that the design of the content is owned either by Avaya or its licensors and is
information in this document is complete and accurate at the time of protected by copyright and other intellectual property laws including the
printing, Avaya assumes no liability for any errors. Avaya reserves the sui generis rights relating to the protection of databases. You may not
right to make changes and corrections to the information in this modify, copy, reproduce, republish, upload, post, transmit or distribute
document without the obligation to notify any person or organization of in any way any content, in whole or in part, including any code and
such changes. software unless expressly authorized by Avaya. Unauthorized
reproduction, transmission, dissemination, storage, and or use without
Documentation disclaimer the express written consent of Avaya can be a criminal, as well as a
“Documentation” means information published by Avaya in varying civil offense under the applicable law.
mediums which may include product information, operating instructions
Third-party components
and performance specifications that Avaya generally makes available
to users of its products. Documentation does not include marketing Certain software programs or portions thereof included in the Product
materials. Avaya shall not be responsible for any modifications, may contain software distributed under third party agreements (“Third
additions, or deletions to the original published version of Party Components”), which may contain terms that expand or limit
documentation unless such modifications, additions, or deletions were rights to use certain portions of the Product (“Third Party Terms”).
performed by Avaya. End User agrees to indemnify and hold harmless Information regarding distributed Linux OS source code (for those
Avaya, Avaya's agents, servants and employees against all claims, Products that have distributed the Linux OS source code), and
lawsuits, demands and judgments arising out of, or in connection with, identifying the copyright holders of the Third Party Components and the
subsequent modifications, additions or deletions to this documentation, Third Party Terms that apply to them is available on the Avaya Support
to the extent made by End User. Web site: http://support.avaya.com/Copyright.
Link disclaimer Trademarks
Avaya is not responsible for the contents or reliability of any linked Web The trademarks, logos and service marks (“Marks”) displayed in this
sites referenced within this site or documentation provided by Avaya. site, the Documentation and Product(s) provided by Avaya are the
Avaya is not responsible for the accuracy of any information, statement registered or unregistered Marks of Avaya, its affiliates, or other third
or content provided on these sites and does not necessarily endorse parties. Users are not permitted to use such Marks without prior written
the products, services, or information described or offered within them. consent from Avaya or such third party which may own the Mark.
Avaya does not guarantee that these links will work all the time and has Nothing contained in this site, the Documentation and Product(s)
no control over the availability of the linked pages. should be construed as granting, by implication, estoppel, or otherwise,
any license or right in and to the Marks without the express written
Warranty permission of Avaya or the applicable third party.
Avaya provides a limited warranty on its Hardware and Software
Avaya is a registered trademark of Avaya Inc.
(“Product(s)”). Refer to your sales agreement to establish the terms of
the limited warranty. In addition, Avaya’s standard warranty language, All non-Avaya trademarks are the property of their respective owners,
as well as information regarding support for this Product while under and “Linux” is a registered trademark of Linus Torvalds.
warranty is available to Avaya customers and other parties through the
Avaya Support Web site: http://support.avaya.com. Please note that if Downloading Documentation
you acquired the Product(s) from an authorized Avaya reseller outside
of the United States and Canada, the warranty is provided to you by For the most current versions of Documentation, see the Avaya
said Avaya reseller and not by Avaya. Support Web site: http://support.avaya.com.

Licenses Contact Avaya Support

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA Avaya provides a telephone number for you to use to report problems
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE or to ask questions about your Product. The support telephone number
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR is 1-800-242-2121 in the United States. For additional support
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., telephone numbers, see the Avaya Web site: http://support.avaya.com.
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED
FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN
AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE
USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY
INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR
AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF
YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER
REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”),
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).

2 Avaya Hospitality Messaging Server 400 Maintenance December 2010

 Contents

Chapter 1: New in this release.................................................................................................5

Features............................................................................................................................................................5
Other changes...................................................................................................................................................5
Update to Avaya Customer Documentation Standards............................................................................5
Backup and Restore chapter removed.....................................................................................................5
Document Updates...................................................................................................................................6

Chapter 2: Introduction.............................................................................................................7
Chapter 3: Diagnostics.............................................................................................................9
Accessing the VoiceEngine module..................................................................................................................9
Job aid......................................................................................................................................................9
Accessing Orion..............................................................................................................................................10
Job aid....................................................................................................................................................10
Accessing the PMSI module...........................................................................................................................10
Job aid....................................................................................................................................................11
Customizing the PMSI module........................................................................................................................11
Functional tests...............................................................................................................................................11
Testing check in......................................................................................................................................12
Testing check out....................................................................................................................................13
Testing a room change...........................................................................................................................14
Testing guest information updates..........................................................................................................15
Testing text message update..................................................................................................................16
Testing wake up call...............................................................................................................................17
Testing connectivity................................................................................................................................18
Accessing system logs....................................................................................................................................18

Chapter 4: Service updates....................................................................................................19

Acquiring SUs from the ESPL site..................................................................................................................19
Uninstalling an SU...........................................................................................................................................20
Installing Service Updates...............................................................................................................................21
Displaying installed SUs..................................................................................................................................22

Chapter 5: Common procedures............................................................................................23

Starting the Avaya Hospitality Messaging Server 400 server.........................................................................23
Stopping or restarting the Avaya Hospitality Messaging Server 400..............................................................23

Chapter 6: SNMP traps............................................................................................................25

Dialogic SNMP traps.......................................................................................................................................25
System SNMP traps........................................................................................................................................25

Chapter 7: Windows event logs.............................................................................................29

Application events...........................................................................................................................................29
System events.................................................................................................................................................34

Avaya Hospitality Messaging Server 400 Maintenance December 2010 3

4 Avaya Hospitality Messaging Server 400 Maintenance December 2010
Chapter 1: New in this release

The following sections detail what is new in Avaya Hospitality Messaging Server 400, NN42350-101 for
HMS 400 Release 2.0.
Navigation
• Features on page 5
• Other changes on page 5

Features
For information about new features added for Avaya HMS 400 Release 2.0, see Avaya
Hospitality Messaging Server 400 Fundamentals, NN42350-104.

Other changes
See the following sections for information about feature changes.
• Update to Avaya Customer Documentation Standards on page 5
• Backup and Restore chapter removed on page 5
• Document Updates on page 6

Update to Avaya Customer Documentation Standards

All content in this book is updated to Avaya Customer Documentation Standards release 2.1.

Backup and Restore chapter removed

Chapter 3: Backup and Restore in version 04.01 of this document has been moved to Avaya
Hospitality Messaging Server 400 Administration, NN42350-600.

Avaya Hospitality Messaging Server 400 Maintenance December 2010 5

New in this release

Document Updates
This document is up issued to reflect changes made to the following section: Service
updates on page 19.
Additional editorial changes were made.
Reorganized the following content, which was moved to separate chapters:
• SNMP traps on page 25
• Windows event logs on page 29

6 Avaya Hospitality Messaging Server 400 Maintenance December 2010

Chapter 2: Introduction

This guide is for administrators, technicians, and engineers who maintain the Avaya Hospitality Messaging
Server 400 (Avaya HMS 400 ) server. This guide describes how to use system tools to identify the cause of
system problems and how to install or upgrade software components.
For detailed information, see Avaya Hospitality Messaging Server 400 Fundamentals, NN42350-104.
Navigation:
• Diagnostics on page 9
• Service updates on page 19
• Common procedures on page 23
• SNMP traps on page 25
• Windows event logs on page 29

Avaya Hospitality Messaging Server 400 Maintenance December 2010 7

Introduction

8 Avaya Hospitality Messaging Server 400 Maintenance December 2010

Chapter 3: Diagnostics

This chapter explains how to access debug pages, perform functional tests, and access system logs.
For information about traps and log files used for diagnostic activities, see SNMP traps on page 25 and
Windows event logs on page 29.
For detailed information, see Avaya Hospitality Messaging Server 400 Fundamentals, NN42350-104.
Navigation:
• Accessing the VoiceEngine module on page 9
• Accessing Orion on page 10
• Accessing the PMSI module on page 10
• Customizing the PMSI module on page 11
• Functional tests on page 11
• Accessing system logs on page 18

Accessing the VoiceEngine module

The VoiceEngine module communicates with the Avaya Communication Server 1000 and
displays all channel activities.
Prerequisites:
Start the Avaya Hospitality Messaging Server 400.

In the Avaya HMS 400 application, click the VoiceEngine icon.

OR
Or in the Windows system tray, click the VoiceEngine icon.

Job aid
The following graphic displays the VoiceEngine icon on the HMS 400 main interface and in the
Windows system tray.

Avaya Hospitality Messaging Server 400 Maintenance December 2010 9

Diagnostics

Accessing Orion
Use Orion to view records sent to and received by Orion for all database-related processing.

In the Avaya Hospitality Messaging Server 400 application, click the Orion icon.
OR
In the Windows system tray, click the Orion icon.

Job aid
The following graphic displays the Orion icon on the HMS 400 main interface and in the
Windows 2003 system tray.

Accessing the PMSI module

The Property Management System Interface (PMSI) module bridges the Hotel Property
Management System interface with the PBX Property Management System (PMS) port. The
PMSI module transmits all data from the Hotel PMS to the PBX and updates the HMS 400
database.

In the Avaya Hospitality Messaging Server 400 application, click the PMSI icon.
OR
In the Windows system tray, click the PMSI icon.

10 Avaya Hospitality Messaging Server 400 Maintenance December 2010

 Customizing the PMSI module

Job aid
The following graphic displays the PMSI module icon on the HMS 400 main interface and in
the Windows system tray.

Customizing the PMSI module

Customize the PMSI module to distinguish data streams by color.
Prerequisites:
Start the PMSI module. See Accessing the PMSI module on page 10.

1. In the PMSI module, select Tools, Customize.

2. On the Customize Colors window, double-click the color box beside the category to
configure.
3. On the Color window, select a color, and click OK.
4. Repeat Step 2 to Step 3 for each category to customize.
5. Click Save.
6. Click Close.

Functional tests
This section explains how to test common functions to ensure they work correctly. Test results
appear in the PMSI module.
The optimal time to perform these tests is if the link between Avaya Hospitality Messaging
Server 400 and the Hotel PMS is down or experiencing problems.
The processes described here are manual processes. An automated process, described in
Avaya Hospitality Messaging Server 400 Administration, NN42350-600 is also available.

Avaya Hospitality Messaging Server 400 Maintenance December 2010 11

Diagnostics

Functional tests navigation:

• Testing check in on page 12
• Testing check out on page 13
• Testing a room change on page 14
• Testing guest information updates on page 15
• Testing text message update on page 16
• Testing wake up call on page 17
• Testing connectivity on page 18

Testing check in
Manually post a check in to test functionality. The test results appear in the PMSI module.
Prerequisites:
• Ensure you have the correct room information.
• Ensure you have appropriate permission to access manual posting.

1. Open the Web interface.

2. Select Hotel Operation.
3. In the navigation pane, select Manual Posting, Check In.
4. In the Room No box, type the room number.
OR
Click the ellipsis (…) button next to the Room No box, select a room check box,
and then click OK.
5. In the First Name box, type the first name of the guest.
6. In the Last Name box, type the last name of the guest.
7. From the Language list, select the preferred mailbox language.
8. If the room belongs to a group, in the Group Code box, type a group code.

Important:
The Group Code box dims if the feature is unavailable (determined by the
keycode).
9. In the COS list, click a class of service.

12 Avaya Hospitality Messaging Server 400 Maintenance December 2010

 Functional tests

10. Review the information to ensure it is accurate, and then click Post.
11. Check the PMSI module to ensure the posting was successfully sent.

Variable Definitions

Variable Value
First name Enter the first name of the guest; maximum 20 characters
(alphanumeric).

Important:
When combined with the last name, the maximum is 27
characters.
Group Code If activated (by keycode) and if applicable, and then enter
the five-digit group code to which the guest belongs.
Last Name Enter the last name of the guest; maximum 20 characters
(alphanumeric).

Important:
When combined with the first name, the maximum is 27
characters.
Room No Enter the room number of the guest to be checked in.

Testing check out

Manually post a check out to test functionality. The test results appear in the PMSI module.
Prerequisites:
• Manually post a test check-in.
• Ensure you have the correct room information.
• Ensure you have appropriate permission to access manual posting.

1. Open the Web interface.

2. Select Hotel Operation.
3. In the navigation pane, select Manual Posting, Check Out.
4. In the Room No box, type the room number.
OR

Avaya Hospitality Messaging Server 400 Maintenance December 2010 13

Diagnostics

Click the ellipsis (…) button next to the Room No box, select a room check box,
and then click OK.
5. Optionally, in the Guest Name box, type the name of the guest.
6. Review the information to ensure it is accurate, and then click Post.
7. Check the PMSI module to ensure the posting was successfully sent.

Variable Definitions

Variable Value
Guest Name Optional. Type the exact name of the guest for the room to
check out.
Room No Enter the room number of the guest to check out, or click
the ellipsis button to select from a listing.

Testing a room change

Manually post a room change to test functionality. The test results appear in the PMSI module.
Prerequisites:
• Manually post a test check-in.
• Ensure you have the correct room information.

1. Open the Web interface.

2. Select Hotel Operation.
3. In the navigation pane, select Manual Posting, Room Change.
4. In the Old Room box, type the old room number.
OR
Click the ellipsis (…) button next to the Old Room box, select a room check box,
and then click OK.
The system lists only occupied rooms.
5. In the New Room box, type the new room number.
OR
Click the ellipsis (…) button next to the New Room box, select a room check box,
and then click OK.

14 Avaya Hospitality Messaging Server 400 Maintenance December 2010

 Functional tests

The system lists only vacant rooms.

6. Click Post.
7. Check the PMSI module to ensure the posting was successfully sent.

Testing guest information updates

Manually post a guest information update to test functionality. The test results appear in the
PMSI module.
Prerequisites:
• Manually post a test check-in.
• Ensure you have the correct room information.

1. Open the Web interface.

2. Select Hotel Operation.
3. In the navigation pane, select Manual Posting > Guest Info Update.
The current guest information appears in the table at the bottom of the Guest Info
Update window.
4. Optionally, in the Room No box, type a room number to search for that room, and
then click Display.
OR
In the Guest Name box, type a full or partial guest name to search for that guest,
and then click Display.
OR
In the Group Code box, type the exact group code to search for all the rooms
belonging to that group, and then click Display.
5. Click Change beside the room to change.
6. Make the required changes.

Important:
If you do not require a Group Code, type 0 in the Group Code box.
Group Code information is not sent to the Avaya Communication Server 1000
(CS 1000). If you enter a COS/VIP code, the code is translated to VI ON and is
sent to the CS 1000. If you do not enter a COS/VIP code, a VI OF is sent to the
CS 1000.
If you select the Reset MWL Status check box, no action is taken. If you do select
the Reset MWL Status check box, the system sends the appropriate command

Avaya Hospitality Messaging Server 400 Maintenance December 2010 15

Diagnostics

to either activate or deactivate the MWL of that room based on the current
database information.
7. Click Update.
A warning box appears, with the message "Packet sent for processing. It might take
some time to update the database. Please click Display or Show All button when
the page is loaded to obtain most current values."
8. Review the warning, and then click OK.
9. Check the PMSI module to ensure the posting was successfully sent.

Variable Definitions

Variable Value
Group Code If activated (by keycode) and if applicable, and then enter
the five-digit group code to which the guest belongs.
Guest Name Enter the name of the guest to update; maximum 30
characters; however, the CS 1000 accepts 27 characters
only.
Room No Enter the room number of the guest; maximum 10 digits.

Testing text message update

Manually post a text Message Waiting Lamp (MWL) control to test functionality. The test results
appear in the PMSI module.
This option sends the MWL ON/OFF command to the switch as well as updates the Text
message status (YES/NO) of a specific room in the database.
Prerequisites:
• Manually post a test check-in.
• Ensure you have the correct room information.

1. Open the Web interface.

2. Select Hotel Operation.
3. In the navigation pane, select Manual Posting > Text MWL Control.
4. In the Text Message Waiting Lamp window, click the Change link next to the room
to change.
5. From the Text MWL Status list, select Yes.

16 Avaya Hospitality Messaging Server 400 Maintenance December 2010

 Functional tests

OR
From the Text MWL Status list, select No.
6. Click Update.
7. If the window does not display the new Text MWL Status, in the navigation pane,
select Manual Posting > Text MWL Control again.

Variable Definitions

Variable Value
No Turn off the Message Waiting Lamp.
Yes Turn on the Message Waiting Lamp.

Testing wake up call

Configure a single Auto Wake-Up (AWU) time to test functionality. The test results appear in
the PMSI module.
Prerequisites:
Manually post a test check-in.

1. Open the Web interface.

2. Select Hotel Operation.
3. In the navigation pane, select AWU, Set Single AWU Time.
4. In the Set Single AWU Time window, click the ellipsis (…) button next to the Room
No box.
5. In the Room No List dialog box, click the room number for which to configure a
single AWU time.
6. Click Select.
7. Click the calendar icon next to the Date box.
8. Using the arrows, navigate to the correct month on the calendar.
9. Click the date on which to configure a single AWU time.

Important:
With the calendar icon, you can configure a wake up call for any day from the
current day.

Avaya Hospitality Messaging Server 400 Maintenance December 2010 17

Diagnostics

10. In the AWU Time lists, click the list items that represent the correct wake-up call
time.
11. Click Submit.

Testing connectivity
Use the PMS Link and PBX Link to verify whether the connection to the Hotel PMS or PBX is
running. The test results appear in the PMSI module.
Prerequisites:
Access the PMSI module. For more information, see Accessing the PMSI module on
page 10.

1. From the Connectivity Test menu, select either PMS Link or PBX Link, depending
on which you want to test.
2. In the Connectivity Test window, click Connect.
The test results appear in the Link Test box.
3. Check the PMSI module to ensure the posting was successfully sent.

Accessing system logs

You can view the log files for all trace screens and modules. Log files are created automatically
every day for troubleshooting.

1. Using Windows Explorer, locate the following directory: C:\HMS400V2\Log.

The logs are organized by module name.
2. Double-click the module for which to view the logs.
3. Double-click the log to view.

18 Avaya Hospitality Messaging Server 400 Maintenance December 2010

Chapter 4: Service updates

This chapter describes how to obtain and install patches and enhancement packages to the Avaya
Hospitality Messaging Server 400.
For detailed information, see Avaya Hospitality Messaging Server 400 Fundamentals, NN42350-104.
Navigation:
• Acquiring SUs from the ESPL site on page 19
• Uninstalling an SU on page 20
• Installing Service Updates on page 21
• Displaying installed SUs on page 22
Prerequisites:
Before beginning the SU:
• Make sure all files in c:\HMS400v2 are not set to read-only
• In Internet Explorer, set the Settings > Internet Options > Privacy setting bar to Medium or lower.
• Ensure there is a recent backup available before installing the SU. Avaya recommends that a backup
be performed just before performing any server maintenance activity to ensure the most recent
customer data is available if a restore is required
• Although the SU installation process only takes a few minutes, Avaya recommends planning to
perform the installation during low-traffic periods, since communication with PMS and CS 1000 is
stopped when the HMS 400 2.0 application is shut down to install the SU.

Important:
If there is an existing SU, it must be uninstalled before the new SU is installed. The SU Installer
(Installation Wizard) prompts if a previous SU is installed. For more information on un-installing a
previous SU, see Uninstalling an SU on page 20

Acquiring SUs from the ESPL site

Use this procedure to obtain Avaya Hospitality Messaging Server 400 Service Updates (SU)
from the Enterprise Solutions PEP Library (ESPL) Web site.
Prerequisites:
You must obtain a user name and password for the ESPL Web site.

Avaya Hospitality Messaging Server 400 Maintenance December 2010 19

Service updates

Important:
The Enterprise Solutions PEP Library is a secure Web site and requires a user name and a
password to log on. You can register online for a user ID and password at http://
support.avaya.com/espl. It can take up to 72 hours to process your account request.

1. Open the ESPL Web site at http://support.avaya.com/espl.

2. Navigate to the Multimedia PEP Tool section to find service updates.
3. Search for Avaya Hospitality Messaging Server 400 Release 2.0 service updates.

Uninstalling an SU
Follow this procedure to uninstall an SU.

1. Shut down (Exit) the HMS 400 application, including the browser HMS Web UI.
For more information about shutting down the HMS 400 application, see Avaya
Hospitality Messaging Server 400 Installation and Commissioning, NN42350-301.

Important:
Do not shut down the server. Shut down only the Avaya HMS 400 application.
2. Right-click the VoiceEngine icon in Windows system tray.
3. When you receive the prompt to shut down the VoiceEngine, click Yes.
4. Stop (File > Exit) the PMSI module. Enter password 000.
5. When you receive the prompt to confirm the shut down of PMSI, click Yes.
6. From the Windows Start menu, choose Control Panel > Add/Remove Programs.
7. Look for the installed SU (for example – HMS200G016R2), and click Change/
Remove.
8. At the prompt, click Yes.
9. Follow the instructions to uninstall the update.
10. After the SU has been uninstalled, proceed with the steps for installing a SU. See
Installing Service Updates on page 21.

20 Avaya Hospitality Messaging Server 400 Maintenance December 2010

 Installing Service Updates

Installing Service Updates

Use the following procedure to install a Service Update (SU), .

1. Browse to the Avaya web site location to find the SU, or run the SU from the DVD/
CD if one is provided..
2. Copy the SU file (for example, HMS200G018.exe) into a \Temp folder. Skip this step
if launched from the DVD/CD.
3. Stop (Exit) the HMS400 2.0 application, including the browser HMS Web UI, if it is
opened.
For more information about shutting down the HMS 400, see Avaya Hospitality
Messaging Server 400 Installation and Commissioning, NN42350-301.

Important:
Do not shut down the server. Shut down the Avaya HMS 400 software only.
4. Click File > Exit to stop the PMSI module. Enter password (000) and click Yes to
confirm.
5. Open and review the readme files for specific installation instructions.
6. Double-click the SU .exe (for example, HMS200G018.exe).
7. Click OK.
The Installation Wizard appears.
8. Follow the installation instructions in the Installation Wizard.

Important:
If the Installation Wizard detects a previous SU, the installation stops and you are
prompted to un-install the old version before you continue. For steps to remove
a previous SU, see Uninstalling an SU on page 20.
9. Restart the HMS 400 software, if directed by installation instructions. The HMS 400
Release 2.0 software application can be re-started through the Desktop icon or
through the Windows Start Menu.

Important:
In isolated cases, if users find the MWI is not working in a SIP environment, go
to WebUI > SIP Setting, enter the current CS 1000 Node IP address, and click
Save. This re-populates the related INI setting with the correct values.

Avaya Hospitality Messaging Server 400 Maintenance December 2010 21

Service updates

Displaying installed SUs

Use the HMS 400 Patch Utility module to view the history of all Service Update (SU)
installations and uninstallations and all currently-installed language files.
The Patch History folder is automatically created the first time you install the update and is not
removed even if you uninstall the update.

1. Click Start > Programs > Avaya HMS > Patch Utility.
The HMS 400 Patch Utility window appears, showing the list of installed and
uninstalled updates.
2. In the HMS 400 Patch Utility window, double-click an SU to view the details:
• file names
• new version and file creation date
• remarks

22 Avaya Hospitality Messaging Server 400 Maintenance December 2010

Chapter 5: Common procedures

This chapter describes common procedures that you use to maintain the HMS 400.
• Starting the Avaya Hospitality Messaging Server 400 server on page 23
• Stopping or restarting the Avaya Hospitality Messaging Server 400 on page 23

Starting the Avaya Hospitality Messaging Server 400 server

Start the Avaya Hospitality Messaging Server 400 server.

Important:
The Avaya HMS 400 cannot answer calls until the VoiceEngine shows that channels are
ready. When Channels appear in the VoiceEngine window, the Avaya HMS 400 is ready to
accept calls.
Prerequisites:
For more information, see Avaya Hospitality Messaging Server 400 Fundamentals,
NN42350-104.

1. Ensure the server is properly connected to a power source.

2. Push the power button on the front panel of the server.
Windows 2003 Server automatically loads.
3. After Windows 2003 Server starts, the Avaya HMS 400 application automatically
loads.
4. Wait approximately 5 minutes for HMS 400 to become fully operational. The Dialogic
Services must start before the Voice Engine starts.

Stopping or restarting the Avaya Hospitality Messaging

Server 400
You can stop or restart the Avaya Hospitality Messaging Server 400 application.

Avaya Hospitality Messaging Server 400 Maintenance December 2010 23

Common procedures

1. On the Avaya HMS 400 application main screen, click Stop.

2. On the Exit HMS 400 V2 window, type the password 000.
3. Click Exit.
4. To restart the Avaya HMS 400, wait for the Voice Engine to completely shut down
before attempting to restart HMS 400.
If you do not wait for the Voice Engine to shut down, certain modules cannot start
successfully. Wait for approximately 10 seconds and then check that the icon is no
longer on the System Tray before continuing.
5. On the system tray, right-click the PMSI icon and select Exit.
6. On the Exit HMS 400 V2 window, type the password 000.
7. Click Exit.
8. If the Operator Console application is active, select File, Exit on the ExtLink
Interface.
9. In the Exit Password window, type 000 and click OK.
10. On your desktop, double-click the HMS400v2 icon to restart.

24 Avaya Hospitality Messaging Server 400 Maintenance December 2010

Chapter 6: SNMP traps

Several traps are thrown as part of the Avaya Hospitality Messaging Server 400 operations, including both
Dialogic and system traps.
Navigation:
• Dialogic SNMP traps on page 25
• System SNMP traps on page 25

Dialogic SNMP traps

Dialogic throws traps with its own set of OIDs.
The Dialogic SNMP traps require the following components, which are prepared during
installation:
• Windows Service
• Dialogic Driver Software
• Compiled Dialogic Proprietary Hardware Information MIB
• Community String and Access-rights set in Services Window

System SNMP traps

Avaya Hospitality Messaging Server 400 throws SNMP traps to the SNMP Manager Device
identified on the Web Configuration page of the Avaya HMS 400.
HMS SNMP Traps
1. SUCCESS
• HMS400 Started
• HMS400 Closed
• HMS400 activated PMSI after detecting it was down
• HMS400 activated Orion after detecting it was down
• HMS400 activated VoiceEngine after detecting it was down
2. WARNING

Avaya Hospitality Messaging Server 400 Maintenance December 2010 25

SNMP traps

• Hard disk space has 10% or below remaining

• HMS400 has detected that VoiceEngine is down. If an activation message trap
is not received, please check VoiceEngine's status manually
• HMS400 has detected that Orion is down. If an activation message trap is not
received, please check Orion's status manually
3. ERROR
• HMS400 failed to connect to main server
• HMS400 encountered an error while trying to start PMSI during application
start-up
• HMS400 encountered an error while trying to start Orion during application
start-up
• HMS400 encountered an error while trying to start VoiceEngine during
application start-up
VoiceEngine Traps
The Voice Engine screen shows the status of all lines and is dependent on the information that
the Dialogic Driver software gives it. Critical errors concerning line failures are handled by the
Dialogic Service. The Dialogic Service throws the corresponding trap for the failure
encountered.
VoiceEngine also utilizes VoiceFunction DLL that controls the playing of sound files. Hence,
Avaya Hospitality Messaging Server 400 v2.0 is able to throw error traps when functions related
to playing sound files encounter errors. The following are some examples:
• VoiceEngine failed to open Dialogic device
• Failed to play the sound file: SOUNDFILENAME Source Module Name – name of the
module that produced the error is another varbind included in this trap. Function Name –
name of the function that produced the error, is included as another varbind in this trap
PMSI Traps

Important:
Different triggers produce different messages.
1. SUCCESSFUL CONNECTION
• HMS400 PMSI connected to PBX via TCP/IP connection
• HMS400 PMSI connected to PMS via TCP/IP connection
2. FAILED/ERROR IN CONNECTION
• PMSI cannot connect to the PBX Server. Please check the status of the PBX
Server.
• PMSI cannot connect to the PMS Server. Please check the status of the PMS
Server.
• HMS400v2 PMSI experiences socket error for PBX TCP/IP connection.
Please check your PBX connection.

26 Avaya Hospitality Messaging Server 400 Maintenance December 2010

 System SNMP traps

• HMS400v2 PMSI experiences socket error for PMS TCP/IP connection.

Please check your PMS connection.
• Fail to login. Please reset the switch if needed.
• HMS400v2 PMSI PMS TCP Port Error. Please check your PMS connection.
Error Msg = Trying to connect to IP Address: (IPaddress)
• HMS400v2 PMSI PBX (TCP/IP) Port Error. Please check your PBX
connection. Error Msg = IP Not Found
• HMS400v2 PMSI PMS Serial Port Error. Please check your PMS setting. Error
Msg = PMS port (port no) is being used by another application of program.
Please shut down and reconfigure to other port!
• HMS400v2 PMSI PMS Serial Port Error. Please check your PMS setting. Error
Msg = Failed to Open PMS port
• HMS400v2 PMSI PMS Serial Port Error. Please check your PMS setting. Error
Msg = PMS Port not found. Please make sure the port exists.
• HMS400v2 PMSI PBX Serial Port Error. Please check your PBX setting. Error
Msg = PBX port (port no) is being used by another application of program.
Please shut down and reconfigure to other port!
• HMS400v2 PMSI PBX Serial Port Error. Please check your PBX setting. Error
Msg = Failed to Open PBX port
• HMS400v2 PMSI PBX Serial Port Error. Please check your PBX setting. Error
Msg = PBX Port not found. Please make sure the port exists
• HMS400v2 PMSI Serial Port Error. Please check your PBX connection. Error
Msg i. Framing Error ii. Overrun Error iii. Receive Buffer Overflow iv. Parity
Error v. Transmit Buffer Full vi. Unknown COM Error
• HMS400v2 PMSI Serial Port Error. Please check your PMS connection. Error
Msg = (same as above 6 items)
• HMS400v2 PMSI PBX Serial Port Error. Please check your PBX setting. Error
Msg = (other system error)
Backup and Restore Traps
1. SUCCESS
• HMS400 Manual Backup Process Started
• HMS400 Auto backup Process Started
• HMS400 Manual Backup Process Finished Successfully
• HMS400 AutoBackup Process Finished Successfully
• HMS400 Restoration Process Started
• HMS400 Restoration Process Finished Successfully
2. ERRORS
• HMS400 Manual Backup Failed. An error occurred in creating the .ZIP file

Avaya Hospitality Messaging Server 400 Maintenance December 2010 27

SNMP traps

• HMS400 Restoration Process Failed. HMS400 Restore cannot find the backup
file BACKUPFILENAME.ZIP
• HMS400 Restoration Process Failed. Restoration cancelled due to a copy file
error. Files successfully copied cannot be reverted to their original copies
• HMS400 Restoration Process Failed. An error occurred while extracting files
from the backup file. The file may be corrupted or unreadable
• HMS400 Backup Restore Module cannot find the MySQL files
• HMS400 AutoBackup Module cannot find the MySQL files
• HMS400 AutoBackup Failed. AutoBackup:Writing to zip file error! The
autobackup process will not continue
• HMS400 AutoBackup encountered an error during database backup. The
autobackup process proceeded with the rest of the files

28 Avaya Hospitality Messaging Server 400 Maintenance December 2010

Chapter 7: Windows event logs

Windows event logs include both applications events and system events.
Navigation
• Application events on page 29
• System events on page 34

Application events
1. When HMS400 is launched – VoiceEngine module is started

2. When HMS400 is launched – Orion module is started

Avaya Hospitality Messaging Server 400 Maintenance December 2010 29

Windows event logs

3. When HMS400 is launched – PMSI module is started

4. When HMS400 Backup (Manual or Scheduled) process is started

5. When HMS400 Restore module is started

30 Avaya Hospitality Messaging Server 400 Maintenance December 2010

 Application events

6. When HMS400 is stopped – VoiceEngine module is closed

7. When HMS400 is stopped – Orion module is closed

8. When HMS400 Backup process is completed

Avaya Hospitality Messaging Server 400 Maintenance December 2010 31

Windows event logs

9. When HMS400 Restore process is completed

10. When HMS400 Backup process encounters errors

32 Avaya Hospitality Messaging Server 400 Maintenance December 2010

 Application events

11. When HMS400 Restore process encounters errors

Avaya Hospitality Messaging Server 400 Maintenance December 2010 33

Windows event logs

System events
1. When VoiceEngine is started/closed

34 Avaya Hospitality Messaging Server 400 Maintenance December 2010

 System events

2. When Orion is started/closed

3. When PMSI is started/closed

Avaya Hospitality Messaging Server 400 Maintenance December 2010 35

Windows event logs

36 Avaya Hospitality Messaging Server 400 Maintenance December 2010