Friday, November 28, 2008

Cisco CallManager Change Server IP Address

This post applies to the Cisco CallManager Linux appliances, not the older 4.X Windows based systems. I had the opportunity to test it on version 6.1.1. See below:

There are some posts hanging around the Internet regarding changing the IP address on a CallManager server running in VMWare. The problem reported is that although you can very easily change the server address from an SSH session using set network ip eth0 your_server_ip_address your_subnet_mask or from Cisco Unified OS Administration, you cannot login to the Cisco Unified CM Administration page after the change.

You will be able to SSH to the new address but when you run utils service list you will find Cisco CallManager is stopped. If you haven't noticed by now, your phones are also dead (or running on SRST if so configured).

Do not panic. You probably need to get your hands on a serviceability guide.

Let's assume your CallManager was at 10.3.1.100 and worked. Then you changed it to 10.101.10.5 and it didn't...

1. Use the same procedure you used to set a new IP address on your server and break it to set it back to the old one (change it back to 10.3.1.100 from 10.101.10.5).

2. Reboot the server (if not forced to automatically).



3. Access the Cisco Unified CM Administration web page via the old IP address (10.3.1.100).

4. Go to System | Server and change the IP address there (change it from 10.3.1.100 to 10.101.10.5). This is what you didn't do the first time.

5. Access the Cisco Unified OS Administration page at the still functioning original address (10.3.1.100).

6. Go to Settings | IP | Ethernet and change the address to the new one there (from 10.3.1.100 to 10.101.10.5).



7. Wait for system to reboot.

8. Enjoy your server at the new address (10.101.10.5).

Monday, October 27, 2008

Display message class in Outlook / IPM.Note.voice.unity

In Outlook 2007, highlight your inbox (or any folder),
Choose View | Current View | Customize Current View,
Click Fields,
Choose All Mail Fields from the drop down,
Move Message Class to the right,
Change your Number of Lines to an appropriate value, or move up the Message Class.

Enjoy viewing your message classes!

Saturday, October 25, 2008

C# Excel OLEDB and Could not find installable ISAM

So you have chosen to manipulate Excel spreadsheets with C#, and rather than using Excel Automation you are using OLEDB. Now you find you receive "Could not find installable ISAM" when bebugging.

I will bet it has to do with escaping the quotes surrounding the "Extended Properties" in your connection string. Personally, things worked fine for me util I added the HDR or IMEX variables.

The Excel references at www.connectionstrings.com are very helpful and indicate the quotes are an issue, but don't provide specific working examples.

Here you are:

String sConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\\Test.xls;Extended Properties=\"Excel 8.0;HDR=No;IMEX=1;\"";

or maybe more helpfully:

String sFile = "C:\\Test.xls";

String sConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" + sFile + ";Extended Properties=\"Excel 8.0;HDR=No;IMEX=1;\"";


Notice the \" escapes surrounding Excel 8.0;HDR=No;IMEX=1;

Hope that helps.

Friday, September 26, 2008

Unity 5.X default template

Before you get excited and add all your Unity subscribers, please take a moment to at least review the default subscriber template.

Other than maybe changing default passwords if you haven't thought about it during the install, you may notice interesting items in the call transfer section.

The default for all types (standard, closed, alternate) is "No (send directly to greeting)". Check the "Yes, ring extension for:" if you really need most mailboxes to transfer to lines. Then build them.

Wednesday, September 24, 2008

Altigen OE 4.5 Agent Log Out on Reboot

For those of you happy with and hanging on to your old Altigen software level, here's a tip for when you need to rebuild.

On 4.5, agents are logged out of workgroups when a system reboots. There is a registry setting to maintain their status, or even automatically log them all in after a reboot.

The key is located at:

HKLM\Software\Altigen Communications Inc.\Altiware\DisableAgentAutoLogout

0 = logout all agents on reboot (default)
1 = maintain agent login status
2 = login all agents after reboot (this is what older versions did)

You need to edit the key and reboot the server (not just restart the services).