CallManager 5.1 can't forward to voicemail / call forward

Unanswered Question

I have CallManager 5.11b right out of the box. Has anyone seen an issue where you cannot call forward all or forward to voicemail. I have checked partitions and CSS and they are fine. I can hit the messages button on the phone and it works fine, but if I try to do a cfwall it will not work and it gets the "Call Cannot be completed as dialed." Even when someone else calls the phone and there is a ring no answer, i get the same message. I know it sounds like a CSS issue, but it is not. Any ideas?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Rob Huffman Thu, 05/17/2007 - 08:22
User Badges:
  • Super Red, 40000 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Jesse/Steve,

Maybe you are hitting this bug;

CSCse57203 Bug Details

Call Forward stops functioning after Line description added


Call Forward No Answer/Busy stops functioning after Line Description added. The phone still displays that it is forwarding but it is not working any more.


Seen with CallManager 5.0(4) may alos be present with earlier versions


delete Call Forward settings in Destination strings of the Call Forward and Call Pick up settings paragraph, save it, create them there again, save them.

1st Found-In






Hope this helps!


trevis.brian Sat, 05/19/2007 - 10:53
User Badges:


You have specified a CFNA CSS haven't you? The combined CSS of line+phone is different to the CSS of CFNA. Being able to dial the VM pilot does not mean that youe can CFNA to VM..........

lwai Sat, 05/19/2007 - 20:06
User Badges:

Dear All,

I and our colleague have the same issue on two sites. Both sites are running CM5.1b.

TAC replied the issue is caused by bug ID CSCsh18194.

The workaround is unchecked the busy no ans. box and click update; and undo preious step and click update. It will solve this issue.

TAC provided us a SR cisco-ipt-k9-patch5.1.1.3112-4.tar.gz.sgn(485184KB size), we had put it in a testing server, it solve the issue.

The CM was upgraded and the issue was solved.

My colleague will put it on end user's production server today.


This Discussion