Skip to Content

Cisco CallManager

Free Cisco Press Chapter - Designing Voicemail Systems with Cisco Unity Connection

Wed, 2011-08-17 07:10

Cisco Press has been nice enough to offer us all a free chapter from the book Cisco Unity Connection.

The chapter covers the following topics:

  • Design Considerations: Understand the capability of Cisco Unity Connection as it pertains to current users, network design, codecs, voicemail ports, and projected growth.
  • Active-Active Cluster Pair: Explore the high availability and redundancy feature of Cisco Unity Connection using the active-active cluster pair configuration.
  • Voice-Messaging Design: Design the voice-messaging system using Cisco Unity Connection platform overlays by determining the proper server sizing, equipment, codec, feature, and capabilities.
  • Voice-Messaging Networking: Understand the various networking options available in Cisco Unity Connection version 8.x software.

MGCP Configuration for Voice Gateways

Wed, 2008-12-10 07:41

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.

What's New in CallManager 5.X?

Mon, 2006-07-10 06:17

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

CallManager on Non-MCS Equipment

Wed, 2006-06-14 13:25

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:

Syndicate content


Dr. Radut