CUCM 6.1 call transfer problem

Unanswered Question

Hi all,

we're experiencing an annoying problem with Cisco UCM 6.1 (version

The problem is that now and then call transfer function stops working - you press the softkey and no result follows. Can be cured by restarting CallManager service on the publisher server. The cluster is comprised of two identical MCSs, on the same switch so it can't be related to sync problems. Of course it's not about css/partitions as phones and numbers remain the same.

Any suggestions?

Thanks in advance.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Afragoso2009 Sun, 02/15/2009 - 17:47
User Badges:

I had the same Problem but with the PSTN call :

I had uncked the MEDIA TERMINATION POINT REQUIRED on the Gateway

Plea try

david-lima Sun, 02/15/2009 - 18:06
User Badges:
  • Bronze, 100 points or more

Hi, check if you have a database replication problemsor alerts using the RTMT or cli options.

Hope this help


pemelend Sun, 02/15/2009 - 23:22
User Badges:
  • Cisco Employee,


does it fail with all phones, or just some?

Do you see any specific error on the ip phone?



homewreka71 Mon, 02/16/2009 - 14:28
User Badges:

Could anyone please e-mail me if they find a fix, I am having the same issue. Thanks..

What I'm thinking about is that it first started when we applied a 'cisco-cheat code' provided by cisco to enable pickups within hunt groups. It is a special string that you enter in the field in system settings. It is said that it might cause some bugs and that though provided by cisco you use it on your own risk.

Did you enter any codes in the field "cisco support use"?

tjungwir Thu, 04/09/2009 - 03:13
User Badges:

Hi, have you found any solution yet?

As I can confirm the same problem on very similar configuration as you've posted (one MCS is a year older than the other).

And yes I have to restart Callmanager service once a week as well. The only applied patch was ciscocm.CSCsm71662.cimserver.snmp.leak.cop.sgn to fix cim process memory leak.

Has anyone tried to upgrade to 6.1.3?


This Discussion