WorkMan HVS - Troubleshooting for tech

HVS Problems

Wakeup isn't triggered

Try to restart the service "WorkMan HVS Voice" and see if that solves the problem. Contact support otherwise.

I don't hear an echo while calling echo-test (1907)

Validate that the shortcode is created and the SIP-trunk password is correct.

I hear an error message when calling wakeup (1900)

Verify that you have actually checked in the room and check the log-file in HVS Voice folder. It might be that you are using internal data or something wrong in SIP Trunk configuration which means that HVS doesn't get the proper extensionsnumber.

I hear a busy signal from the PBX

First of all make sure that you have monitor up and running so you can see the SIP-traffic. Then take note of where the call ends and look into the following:

• In some versions of Avaya IP Office there might be an issue with other ports than 5060.
• Make sure the SIP service is up and running
• Make sure the ACL is allowing traffic from IP Office (typically unauthorized in SIP-logs).

IP Office Problems

I only get busy signal from the public PSTN

It's possible that at some stage the WorkManFS has registered that it supports uPnP to the firewall which opens up those ports and forward all calls to WorkManFS instead. To solve it disable uPnP in the firewall or remove those entries. The firewall should forward calls to the IP Office according to firewall rules but uPnP might override it depending on what firewall is being used.

TAPI isn't displayed in the TAPI-devices list

Try some of these things:

• Make sure that the TAPI driver has been installed (Avaya TAPI2 Service Provider)
• Validate that a TAPI license is installed in the PBX