*xxxx transfer is not working

Unanswered Question
Mar 19th, 2008

This used to work, but now it does not work. When users try to transfer a call using *xxxx we get a generic unity greating. "Welecome you have reach the unity system, etc etc.." It is properly setup in Call manager.

How do we fix this, this used to work.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
shirwaziri1_2 Wed, 03/19/2008 - 09:12

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

Imad Dandis Wed, 03/19/2008 - 12:21

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.

keithknowles Wed, 03/19/2008 - 21:28

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.

vince.castro Mon, 04/28/2008 - 17:39

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.

keithknowles Tue, 10/14/2008 - 11:58

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.

gogasca Fri, 03/21/2008 - 15:19

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


This Discussion