Installing Cisco MeetingPlace Express on unsupported hardware

1. You must copy files from instalation media, we should do this with tar to preserve file permissions. The command could be like this (if you run it from root folder of installation CD/DVD) tar -cvpf /where-to-put-file/mpe.tar.gz /
2. You must untar files, preserving file permissions (do not untar to NTFS volume this would break file permissions). tar -xv --preserve-permissions -f mpe.tar.gz
3. You should patch file hwdetect in /Cisco/vendor/misc/bin according to your server HW (personaly I changed CPU's speed to 2800MHz instead of real 3000MHz). Beware to keep the permissions of file after changing it.
   
4. Make on iso of new installation, I use this command: mkisofs -o mpe2.0.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-info-table -l -f -allow-lowercase -allow-multidot -boot-load-size 4 -d -R /root-directory-with-you-MPE-files/. You should make on iso so that all files on it appear as on original CD/DVD (same letter case, same format, and so on). You should pay attention that Cisco uses symlinks on it's CD/DVD so you must keep them on your iso file.
   

Fixing Firefox certificate error

It is really annoying when you can't connect to your equipment (ex. via HP iLo) or site via https using Firefox because it says sec_error_ca_cert_invalid or sec_error_reused_issuer_and_serial. Sometimes even after deleting stored certificates in Preferences -> Advanced -> Encryption - View Certificates -> Servers you can't connect.
One more thing you should check is the Certification centers tab (next to Servers tab). Make sure that there is no certificates or centers that may conflict with your site's or equipment's certificate. Delete all unnecessary certificates from that tab as well, pay special attention to Software Security Device objects. Hope that will help you get connected to where you want.

Convert ATA 186 from SIP/H323 to SCCP/MGCP

Main idea:

1. Download needed image from Cisco.com or from CUCM TFTP (usually file with .zup extension)
2. Get ata186us.exe file (it may be found in zip archive with images for ATA on Cisco.com)
3. Execute ata186us.exe <image_to_upload_on_ATA> -d3 -any2
   You can run ata186us.exe without parameters to get help on usage.
4. Pick up the handset of the phone attached to ATA.
5. Press the function button on ATA (you should hear IVR prompts in handset after that).
6. Press on the ATA phone keypad 100#<IP_address_of_PC>*8000#
   <IP_address_of_PC> - is IP address of PC on which you run ata186us.exe (while entering IP address on the phone separate octets with * button).

After upgrade you should hear prompt in handset with upgrade result (success/fail).

PS. Make sure you have routing between ATA ond PC. Also you may check ATA parameters through web - http://ATA_IP_address

Another way to replace image files on ATA is to make config file in which you point the firmware you want to upload. See contents of zip archive with images for ATA on Cisco.com for information and details.

Делаем скринкасты

Долго мучился с размером получаемых CamStudio скринкастов презентаций, пытался делать родным CamStudio'вским Loosless кодеком, получались очень большие файлы, даже с включенным максимальным сжатием и частотой кадров 1 кадр/сек. Вчера вдруг осенило - поставил K-Lite Codec Pack в варианте Lots of Stuff. В результате в CamStudio появилась возможность выбора новых видеокодеков.
В итоге: скринкаст часовой интернет-презентации со звуком (56kbit/s, stereo, mp3), частотой - 2 кадр/сек, разрешением 640х480 и использованием кодека H.264 занимает 35Mb.

Ставим Cisco IP Telephony OS на несертифицированное железо

Ставим Cisco IP Telephony OS 2000/2003 на несертифицированное железо

1. Находим на диске с оригинальной Cisco OS файл WinPE.iso
2. Открываем его какой-нибудь програмкой и находим в этом ISOшнике в папке Scripts файл OSINST.VBE
3. Извлекаем этот файл.
4. Файл надо расшифровать скриптом ScriptDEcoder.vbs, который можно взять здесь (внимательнее со скриптом у меня такое ощущение, что он работает только с файлами с именами в нижнем регистре и лучше вообще проводить все операции в корневой папке).
5. Расшифрованный файл открываем текстовым редактором и правим его в соответствии с конфигурацией нашего сервера.
6. Исправленый файл зашифровываем обратно скриптом ScriptDEcoder.vbs (регистр имени измененного файла желательно оставить таким же как и незашифрованного)
7. Кладем исправленный файл вместо исходного обратно в WinPE.iso
8. Если снимали образ с инсталяционного диска, то кладем новый WinPE.iso в этот образ вместо старого.
9. Пишем образ, ставим OS.
   

Управляем Cisco IP Phone удаленно!

Нашел бесплатную программу, которая позволяет удаленно управлять Cisco IP Phone. Поддерживает CUCM 3.X, 4.X, 5.X и телефоны 7940/7960 Firmware 7.1(2) и выше, 7941, 7961, 7970, 7971. Для управления нужен пользователь на CUCM, и ассоциация управляемого телефона с этим юзером.
Взять программу можно здесь.
Там же программы для установки фоновых изображжений и рингтонов на телефоны (тоже бесплатные), правда эти программы для новых версий CUCM не столь актуальны.

Using multiple IPBlue Phones on one PC

The IPBlue phones are very handy for the vmware/dynamips simulated voice lab. However, the problem is that when you start up a second instance, it defaults to the first MAC address available and the first and second instances start flapping trying to re-register to the call manager using the same MAC address. Here is a quick and 'not so dirty' solution:

The phone basically reads its configuration from the windows registry when started. The trick is to make sure the appropriate MAC address is in the registry (assuming you have 2 or 3 NICs or Virtual vmnet interfaces in case of VMware) before you start the application each time. The settings are stored under HKEY_CURRENT_USER\Software\IPblue\ in the registry. Follow the procedure below to create multiple phone 'profiles' first

1. Launch the IPblue phone
2. Choose one of the available MAC addresses.
3. Make sure settings on CCM / CCME is set correctly and verify that the phone registers.
4. I usually also select the Cisco skin for the phone and select 'Mini View Mode' from the File menu, so that the compact view is used, allowing 3 or 4 phones to be displayed simultaneously on my desktop.
5. Run the regedit tool ('Start', 'Run', regedit.exe)
6. Browse to HKEY_CURRENT_USER\Software and select IPblue'
7. From the 'Registry' menu, choose 'Export Registry File' - Make sure you have the'Selected Branch' option selected - you DON'T even want to think about exporting the whole darn thing - it's humongous.
8. Give it an appropriate name - I usually choose the primary extension - example 1001.reg
9. Go back to the phone configuration and choose another MAC address.
10. Repeat steps 3 to 8 and create the next registry file (example 2001.reg, 3001,reg etc..)

A little bit of theory again.. Now you have a bunch of registry files that has the full configuration for a phone in the way you want it. If these entries are in the right place when the phone starts up, it will appropriately launch the right phone/extension. Double clicking on the registry file from explorer will give you a warning, and will import the content to registry when you accept the warning, and again shows up another annoying message about how it updated the registry. All settings under 'IPBlue' will now be updated from the registry file that you imported.

I usually keep all my phone registry files in the same directory and do the following steps to activate the phones (assuming the CCM configuration is completed for the phones).

• Double click the first registry file to import phone configuration.
• Run IPblue phone and wait until it registers. (Tip: Starting ipblue phone with a '/d' option lets you launch multiple phones - otherwise it will throw an error and bring the active one to the front)
• Double click the second registry file to import second phone configuration.
• Run IPblue phone again from the shortcut and it will launch a second instance, now with the configuration for second phone. Verify registration of the phone..
• and so on.. limited by the number of MAC address/CCM pair.

That's brings another interesting discussion. You CAN re-use the MAC addresses, assuming they are registering to different CCM clusters. For instance, with 2 MAC addresses you can have 4 phones, two registered to CCM and two registered to CCME. Just follow the same procedure as above with the tftp server address pointing to CCME router, and reuse the MAC addresses for your CME phones.

The sound quality is not the greatest at all times, but it does work - I still have my virtual lab on my laptop.

Взято отсюда