BMS and License files

Funny how some errors catch you totally off guard. For example, I found that I could not load license files (IPU and CPU) to the systems I was connecting to. At first we thought the files were corrupt and had them resent. After much evaluating and deliberations however, it became apparent that the fault was on my laptop, as my Manager's laptop transferred the licenses successfully! Wonderful, another little idiosyncratic Windows error for me to solve.

I will skip the details, I had success after the following actions:

1. Disabling the Internet Explorer Compatibility View.

2. Reinstalling BMS.

I doubt the latter made a difference unless some or other batch file for uploading Licenses got corrupted. Very likely the Compatibility View corrupts a part of (a) the uploaded file or (b) the HTML page acting as a transit page.

Either way, License uploading works!

Unified Messaging essentials

After much battling with Unified Messaging from Aastra, I have found that the software (plugins) requires the following:

Windows XP SP3
DotNet 2
Fax services

If after the installation of the Unified Messaging plug-in the Fax Monitor does not appear on transmitting of faxes, try Repairing option of DotNet 2. Failing this, all faxes can be monitored by the fax console (found in Windows under Printers and Faxes).

Test any suspected network connectivity problems the following manner:

1. After setting up the IP of the UM Server, close and reopen the plugin config. If there is no Network connectivity the following error will appear:

2. Still battling, but Network test above passes? After entering the User's extension and password, click apply and then select the "Settings" tab. If the extension or password does not correspond to the Server or PABX settings the error appears:

All of the best with the troubleshooting!