Cisco Learnings

Archive for the ‘Cisco Voice’ Category

One of the very common question often asked by either recuriment agency agent or in a job interview is ‘how Cisco IP Phone Boots up’ ??  Well, to answer that, its a 6 step process and you should know them by your finger tips;

1. If you connect Cisco IP Phone to Cisco Inline Power Switch, it is detected as unpowered device and switch supplies power.
2. Phone power’s ON and boots up image software, during bootup process,
3. Phone request VLAN info which is supplied by Switch via CDP, Once Phone has its VLAN ID,
4. Phone send DHCP request and recieve IP & TFTP information from DHCP server.
5. Phone contact TFTP server to receive its configuration
6. Phone contact first Call Manager listed in the configuration file and take the rest of the setting such SRST, Softkey Templates, MOH etc.

Advertisements

To install Cisco Call Manager 4.1 or IPCC Express 4.5 on Windows 2000 Server, All you need to do is add these settings to your registry.

This setting is to fool Call Manager thinking that it is a Cisco MCS or compatibale hardware.

 [HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Model]
 “Hardware“=”MCS7835”
 “Memory”=”1024”
 “Speed”=”733”

This setting below are OS requirement for Call Manger.

[HKEY_LOCAL_MACHINE\SOFTWARE\Spirian\System Info\OS Image]
 Version = 2000.2.7a

I havent actually tried it on a Windows XP or any other OS, but I think it should work and get installed after adding the above settings to your registry.

Try and let me know your feedback.

Cool Lab Tutorial Videos of Cisco Voice related troubleshooting from IP Expert.

I have uploaded them to my webserver, click here

Here is a good reference notes for Implmenting & Designing IPCC Express from Cisco click here

I happens to implement CUCM quite often and one of the feature that every body wants is Extension Mobility. Which is fine, but I alway have to dig deeper to find Service URL. For me to make my life easier, let me just upload it here to refer to;

http://<IP Address of Extension Mobility server>:8080/emapp/EMAppServlet?device=#DEVICENAME#

This is for CUCM 5 or Above, I think this differ on Call Manager 4.

I think its bit difficult to follow systematic troubleshooting approach when you are in the line fire, but believe me it helps, I know its not fast remedy, but it will really save huge time by looking into things that might have nothing to do with the actual problem.

All you have to keep in mind is – DGCCIVD

1. Define the Problem

2.Gather Facts

3.Consider Possible Causes

4.Create Effective Action Plan

5.Implement Action Plan

6.Verfy Action Plan – (Is it working or its just getting worse)

7.Document the Problem & Resolution (Eg. Write you actions in notepad.i.e restart Call Manager, Gateway, Reset ACL, Config Changes etc)