Recently in Cisco CallManager Category

I put this here primarily for my reference. I always end up forgetting one of the global commands when configuring a voice gateway for MGCP...this assumes a Cisco CallManager @ 172.30.100.104:

Router(config)#mgcp
Router(config)#mgcp call-agent 172.30.100.104
Router(config)#ccm-manager mgcp

!Now, the redundant CCM hosts:

Router(config)#ccm-manager redundant-host 172.30.100.105 172.30.100.106

!Now, the TFTP server configuration...gateway should be configured in CCM by this point.

Router(config)#ccm-manager config server 172.30.100.104
Router(config)#ccm-manager config

!In newer IOS/CCM versions, voice dial-peers are created automatically...older versions need this to place each port under MGCP control.

Router(config)#dial-peer voice 5000 pots
Router(config-dial-peer)#port 0/0/0 !FXS port
Router(config-dial-peer)#service MGCPAPP !or application MGCPAPP on older IOS versions

Sorry for the lack of posting as of late. All my time has been consumed in finishing up the CIPT (CallManager) series for CBTNuggets. While CallManager 4.X currently owns the market (and probably will for years to come), it looks as though Cisco is producing a pretty killer solution in Callmanager 6.X versions. So...I bought the software off Ebay and found this link detailing instructions on getting 6.X versions of CallManager running in VMware. What surprised me is that these instructions are from Cisco TAC!!! Hurrah for Cisco finally realizing that people will be running CCM in lab environments! No more registry hacks (not that you could with Linux anyhow). Cisco even provides the VMWare environment file that sets up VMWare exactly like you need it for CCM 6.X. Nice!

Here's the link: Click right here

Also, right on this link, Cisco's approval for running CCM in VMWare for demo/lab purposes: Click right here

UPDATE: I've attached the VMWare Environment file right here.

UPDATE #2: How funny - during the installation, the CCM 6 software recognized that I am running this in VMWare:

Also equally funny: I tried to install the CCM 6.X software on my MCS-7815 server from Cisco and it gave me an unsupported hardware message. VMWare works; older Cisco hardware does not :).

This post has been a long time in coming, but after Cisco Networkers 2006, I thought I'd put together the high points of the changes that are appearing in Cisco CallManager 5.X versions. Bullets always work best for me!

• Underlying Operating System – this is, by far, the biggest change to Cisco CallManager. Cisco has moved the software to an appliance model (I’m sure some industry pressure forced this). The CallManager runs on top of the RedHat Linux operating system; however, you will have no direct access to the operating system. What does this do?
  
  
  
  • Easier installations & upgrades
    
  • Increased security and reliability
    
  • You can only access the CallManager via Cisco approved tools & interfaces
    
  
  

I did it. I finally did it. I've got a Cisco CallManager 4.1(3) server running natively on a Dell Optiplex 270GX. Now, I'm not talking about the old registry hack forcing you to install Windows 2000, hack the registry, and then put the Cisco CallManager software on top of it. Doing this causes a host of problems because the base windows operating system does not have the correct services running and permissions set.

I'm talking about a hack that allows you to install the Cisco CallManager Windows image straight from the CD-ROM, setting all the correct permissions and giving you a working Cisco CallManager on a non-MCS server. Here's what I did: