we have call manager 4. There was not upgrade, this worked but now it is not working?

I would start at the unity call viewer. Do a test call with the * and four digits then see what digits are really showing up in the call viewer.

Have you added any route/translation/dn patterns that could be conflicting with the *XXXX pattern? I would also try using DNA (Dialed Number Analyzer) to make sure the call is being routed properly through CallManager. If you have never used DNA before be sure to activate it on a CCM server that has some processing power to spare as it can be a bit of a resource hog.

Keithknowles is semi right, you install DNA via Plugin in CCMA, it has no activation. Once installed it will show up as a Service in the Windows Service Console. You can install on ANY server in the Cluster. My guess is that you may have entered a Route Pattern or Translation Pattern that either blocks or overides the existing one. Good thing to check out anyways. If no updates, then was their any Route changes and/or adds or changes to Translation Patterns? Hope this helps.

My apologies, my DNA instructin were for a 5.X system where you run it from the CUCM. In 4.X i guess you install it as a plugin.

Hey which exact version of CallManager you have

we filed a bug that affect that functionality?

Give me the version and will let you know if in fact you are affected

it is version 4.1.3sr2

This is an example of how to get this working on callmanager 6.1

Thanks Rob.

Fixed my issue.

Saved me a TAC case. +5