We have a 2851 MGCP PRI gateway connected to CallManager 4.1.3. About once a day, outbound calls will stop routing and we have to do a "no mgcp" and "mgcp" to get the PRI back up. We have changed IOS to see if it is possible bug. I really don't want to call TAC and thought I would see if anyone has seen this?
When it fails, does CCM show the gateway endpoints registered or not, and what does router say (show ccm-man) ?
Have you looked at the router log?
I have seen several voice/MGCP bugs in 12.4 code and later 12.3(14)T, so I tend to stray from using 12.4 at moment unless needed but a 2851 is one model where you need newer IOS versions.
I would do this when it fails, get the above info plus...
capture 'show isdn stat' , 'show ccm-man',
Do a 'debug isdn q931' and 'debug mgcp packet' and place some calls that fail, hopefully those captures will be point to problem. Also have CCM detailed traces turned on the call manager server so you can compare the router debug to CCM trace.
What do the router config look like for ccm-manager commands and global mgcp commands?
Are you binding the MGCP traffic to a interface or just taking default one it uses? I see theres 2 gig interfaces, There's a mgcp bind bug to fixed in 12.4(5).
If you have a syslog server, it may worthwhile running the 'debug mgcp packet' to a syslog server constantly until the problem happens with CCM detailed traces running on server. Disable console/monitor logging and buffered if you want.
Am watching this with interest. We have 2851 and have tried different IOS versions. Our PRI is attached via H.323 and no problems. An 8-port FXS/DID for faxes uses MGCP and randomly freezes (every 1-3 days). This is the first posting I've seen that may be associated with our problem.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.