Navigation:  How-To Procedures > Avaya ACM > Passing PMS Data to the ACM >

Verify the Link

Previous pageReturn to chapter overviewNext page

Once you have finished configuring both the ACM and the DV2000/DV4 and both systems are up and running with the new configurations, you should first verify that the link has been established.  There are several ways you can do this.

 

On the ACM

You can check the status of the PMS link on the ACM by issuing the following command:

 

status pms-link

 

This will display the current status of the PMS link, as shown below:

 

ACM0013

 

If the link is connected and working properly, both Physical Link State and Protocol State should report up (as they do in the figure above).

 

If either or both settings report down and you have verified that the DV2000/DV4 believes it did establish the connection, you can issue the following command to review possible error messages:

 

list pms-down

 

Discussion of the often-cryptic Avaya error messages is beyond the scope of this document.  You many find some help in interpreting these messages by consulting the GuestWorks and DEFINITY Enterprise Communications Server Release 9 Technician Handbook for Hospitality Installations (document number 555-231-743) or a similar document.  The list pms-down error messages are documented in Appendix C of that document.

 

On the DV2000

To check if the DV2000/DV4 thinks the link is up and running, you need to run the Trace Display application and review the ACMSRVR (ACM server) log file.  You can access that program by selecting Start | All Programs | DuVoice | TraceDisplay.

 

Select File | Open from the main menu, navigate to the C:\DUVOICE\TraceLogs folder and select the log file ACMSRVR.LTT to view the most-recent log data.  The figure below shows a typical ACMSRVR log file:

 

ACM0014

 

The first line displayed in the figure states Built on Feb 1 2011 in the Data column; this line indicates when the ACMSRVR application was started by the DV2000/DV4.  It is the ACMSRVR application that opens the link to the ACM and handles all communication with the ACM.

 

The next two lines shows that the DV2000/DV4 sent a Status Inquiry packet to the ACM and received an acknowledgment back from the ACM.  The two lines after that show the ACM sent a Status Inquiry response packet to the DV2000/DV4 and the DV2000/DV4 responded back with an ACK.  This is normal communication activity between the two systems and shows that the link is up and working correctly.

 

If no activity is logged following the Built on... line, or if there are any error messages logged, that may indicate that there is a problem with the link.

 

Using Ping

If either or both systems appear to indicate a problem with the link, one simple method of determining if the ACM server is even "visible" to the DV2000/DV4 is to ping the ACM from the DV2000/DV4.  You can do this from a command window on the DV2000/DV4 system.

 

To open a command window, select Start | All Programs | Accessories | Command Prompt.

 

In the Command window, type the ping command followed by the IP address assigned to the ACM.  The following is only an example; the IP address of your ACM will likely be different:

 

ping 192.168.11.70

 

If the ACM is on the same LAN as the DV2000/DV4 and can be pinged, it should display data similar to that shown in the figure below:

 

ACM0015

 

If the ping command returns an error it may mean the ACM is not on the same LAN as the DV2000/DV4 and therefore the link cannot be established.  However, it is also possible that ping is being blocked, so an unsuccessful ping may or may not actually indicate an error.

 

Using Netstat

Another command line tool that can be used to verify the link is actually connected is netstat.  To run this command, open a command window by selecting Start | All Programs | Accessories | Command Prompt.  Then type in the command netstat and press Enter.

 

In the resulting output, look for a line that includes the DV2000/DV4's IP address and the port number you assigned to the DV2000/DV4-ACM PMS link.   The figure below shows an example using the default port number 5000:

 

ACM0016

 

In this case, you can see that the connection is Established.  If you cannot find an entry for your IP address and port number combination, then the link is not active.

 

Troubleshooting

If the DV2000/DV4 IP address is not on the same LAN as the ACM a connection cannot be made.
Use Ping from the DV2000/DV4 PC to verify the ACM's IP address is visible to the DV2000/DV4.
Use the NETSTAT command from DV2000/DV4 PC to see if the link is connected.
Use the Status command in ACM to check current link status
Check the Firewall on the DV2000/DV4 (disable if necessary), and the network's firewall, to verify that the TCP port you assigned to the link (on both the ACM and the DV2000/DV4) is not being blocked.