Calls transferred to VM but exten. is not configured for it.

Unanswered Question
May 30th, 2008
User Badges:

i placed an extension on a 7911 that does not have voicemail configured for it but it still goes to voicemail after the alotted rings. i have no idea how or why it's doing this can anyone help.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Rob Huffman Fri, 05/30/2008 - 09:31
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Marsha,


Just a couple of thoughts here :) Have you tried removing the DN in question from the phone and then removing it completely from the database via the Route Plan Report (unused DN's) Then starting over from scratch. It seems to me that something is referenced somewhere with this DN that may be causing you problems.


The other thing to try if you are running a 4.1(3) with sr version is just setting a Call Forward All to any number on this 7911 and then un-setting it. There is a related bug with this symptom.


Hope this helps!

Rob


mlarrimore Fri, 05/30/2008 - 11:15
User Badges:

hi Rob thank you so much. i do have ccm4.1.3 and i tried the second solution first and that worked. so thank you once again.


Marsha.

Rob Huffman Sat, 05/31/2008 - 06:39
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Marsha,


You are most welcome my friend :) Here is the bug that causes this issue;


CSCsj30852 Bug Details


CM 4.x - Inactive or Unassigned DN with CFA still forwards calls


Symptom:

Calls placed to a DN that has been deleted from a phone are forwarded to the CFA destination set on the DN when it was deleted.


Conditions:

This was observed in CM 4.1(3) sr5b

A phone has a DN assigned to it and the phone has a CFA destination configured. The DN on the phone is deleted from the phone, but CM still routes calls to the CFA destination


Workaround:

Add the DN back to the phone, remove the CFA setting and update the phone. This will remove the improper CFA and the DN can then be removed without this issue. Status

Fixed


Severity

3



1st Found-In

4.2(3)

4.3(1)

4.1(3)SR5


Fixed-In

4.3(1.80)

4.3(1)ES10

4.1(3)ES119

4.2(3)ES39


Hope this helps!

Rob


Actions

This Discussion