I’ve been running Cisco CallManager Express for almost a year now and it’s worked pretty well. I hadn’t installed Unity yet so I was still using a good old answering machine off of a Cisco ATA 186. Time to start learning CallManager though, so I went through setting up CM. My FXO port is still on the 1760-V though so I needed to network that to CM as my PSTN gateway. The most obvious way to do this is to configure CM to “manage” the router as an MGCP device. Here’s Cisco’s instructions for doing this. Work’s nicely as the CM will then push config changes to the router based on configuration’s on the CM. The only problem I had was that Caller-ID quit working. I found a link on Cisco’s site that flat out said it’s not supported on CM4.1 and MGCP to a VIC2-FXO2. How much does that suck.

My solution was to reconfigure the router as a CallManager Express box with very little config. All I really have is:

telephony-service
fxo hook-flash
max-conferences 4

Of course, you still have to have some basic dial-patterns configured.


dial-peer voice 2000 voip
destination-pattern 2…
session target ipv4:192.168.169.10
codec g711ulaw
no vad
!
dial-peer voice 8 pots
destination-pattern 8.T
port 0/0

And the FXO port:

voice-port 0/0
timing hookflash-out 50
connection plar 2100
caller-id enable

Then, in CM, I set up CME as an Inter-Cluster Trunk (non-gatekeeper controlled). The configuration is pretty simple in there. Caller ID now works again.

Leave a comment

Your email address will not be published. Required fields are marked *