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!

Programming Aastra 417 Hotel phones

This one had me stumped for a while. To program one of the buttons ensure the Programming button is enables (switch under the phone). The programming sequence is as follows:

1. Lift handset.
2. Press PROGRAM.
3. Press the desired key.
4. Enter the number to be dialled.
5. Press PROGRAM again.
6. Test, it should be working.

Welcome me hearty!

A huge welcome to the FIRST follower on the technical blog! It is going to be great having your support. Please place comments, questions, etc as you see a need! Hope you enjoy the pic, LONG LIVE LINUX!

MD110 SPU2 Software upgrade

I recently upgraded the software on a BC11 system's SPU2. In transferring the file from my PC to the PABX, I found that it could not handle the full file name (CAAxxxxx_R11A.HEX). It would copy the entire file over, so the file size would be accurate. However, on the PABX, the file would not have the full name, including the .HEX. Renaming the file does not affect how the PABX sees it, and this was the only way to maintian the file name with its .HEX. If the postfix is missing, you will not be able to load the software from the NIU2 to the desired board.

Exchange via Evolution on Lenny!!!

Good news at last! I managed to get my Exchange account to work on Evolution 2.22.3.1 with my Debian Lenny OS. The following is what worked in my situation:

1. The exchange server has OWA (Online Web Access) enabled for my account.
2. I entered the proxy address for internet access because Evolution is going to go via the internet to retrieve mail.
3. My exchange server setup was http://mail.exchangeserver.com, my user name being my standard Windows logon name. Pressing authenticate, entering the mail password and then the proxy password and your mailbox name will be displayed (usually the same as your logon name).
4. Password is set to secure password.
5. I also setup the receiving options to poll for new messages every 2 minutes.

The only problem I have experienced is that my alternate folders are not updated, but the main Inbox works, so no major grief!!

CCS Call Processor

Once again another run-in with Call Centre Supervisor. Upon uninstalling CCS and deleting the directory and doing a brand new install of CCS, when starting CCS manually the Call Processor application opens momentarily before closing again. Bear in mind that the Aladdin driver provided does not work for the HASP. So I loaded the correct driver and canncelled the setup of the CCS initiated install. Apparently this was the fault. When (re)installing CCS, the following worked for me:

1. Uninstall CCS via the Control Panel -> Add remove Programs.

2. Delete the CCS directory in Program Files\Ericsson.

3. Install the HASP GUI Runtime driver (downloaded from their site).

4. Run the CCS install, including the Aladdin driver install.

5. Restart computer.

All should start up fine.