cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
319
Views
0
Helpful
3
Replies

CME4.2 call forward to local DN do not work some times

konasanimurali
Level 1
Level 1

Hi Pro's

Software Version: 12.4(11)XW9 + 4.2 CME + 2801


We are unable to get the  CAFW NOAN and CAFW Busy  working.   As our users are configured
for extension mobility  we have created a simple flow that  looks  like

ephone-dn 6
no huntstop
huntstop channel
call-forward busy 610
call-forward noan 610 timeout 10

number 606
name John

description John EU
label 606
preference 0 secondary 9
call-waiting beep
cor incoming user-domestic
cor outgoing call6XX
transfer-mode consult


ephone-dn 10 dual-line
no huntstop
huntstop channel
call-forward busy 600
call-forward noan 600 timeout 10
number 610
name Mark TS
description Mark TS
label 610
preference 0 secondary 9
call-waiting beep
cor incoming user-international
cor outgoing call6XX
hold-alert 15 originator
transfer-mode consult

Problem here is when i try calling "606" (as the user is logout )   from any
extension  initially  it correctly reaches to 610 as the 606 user is offline. but in
subsequent attempts it fails and  says  "There is no mail box associated with this
extension good bye" ( however 610 has it own Voice mail box at 600 (CUE) )

This is completly random and  i dont understand why it doestnt  work.

Appreciate your help and suggestions.

3 Replies 3

paolo bevilacqua
Hall of Fame
Hall of Fame

Recommend you update to 15.0(1)M3. Then if still troubles, open a TAC case.

Steven Holl
Cisco Employee
Cisco Employee

Sounds like the diversion header isn't matching the phonenumber for a valud CUE mailbox when it hits a certain call flow.

Doubt it's a bug.  Upgrade to 15.x likely won't change behavior.

Get the output of the following for a failure:

debug ccsip mess

debug voip ccap inout

Look at the diversion header and cisco-rdn fields in the debugs for the failure.  Compare it to a working call.

OP stated:

This is completly random and  i dont understand why it doestnt  work.

Cannot rule out a bug.