[cisco-voip] can dial vm pilot, but not forward to it?

[Lelio Fulgenzi]

OK. After some testing with different CSS's I realized it had to do more with whether or not the destination was a number or the voice mail pilot (check box). If it was a number (as in the CTI route point mentioned below) forwarding worked. If it was the check box, it didn't. 

I recall a while back someone (Wes? Ryan?) posting that when the vm pilot is used as a destination target, the CSS of the vm pilot is used, otherwise, if it's a explicitly entered DN (even if that DN is the voice mail pilot!) the FWD CSS is used. 

Well, in my version 4 config, the VM Pilot is <none> and this all worked. I thought that if it was set to <none> it piggy-backed on the FWD CSS of the DN. 

Updating my VM Pilot CSS to match the FWD CSS that I've used on the lines fixes the problems. 

Have I been doing it wrong all this time? Was there a bug out there that allowed this to work? Or did they make a change somewhere? 

hmmmmmm 

Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
To: "Cisco VoIP Group" <cisco-voip at puck.nether.net> 
Sent: Monday, February 7, 2011 12:01:10 PM 
Subject: [cisco-voip] can dial vm pilot, but not forward to it? 



hi everyone, i'm trying to get my head around this one. 

background: 

    • imported data from v4 to v7 cluster 
    • integrated around 6 vm ports from unity connection to new v7 cluster 
    • we have three hunt groups (auto-attendant, vm, call handlers) 
    • modify vm pilot and call handler translation to point to first auto-attendant group b/c there are not enough ports to populate all hunt groups 

working: 

    • i can call the vm pilot (either vm button, or number) and connection answers appropriate, i.e. enter your pin 
    • i can call a CTI route point which is forwarded to the call handler translation and the appropriate call handler answers 

issue: 

    • when i call an extension and it rings no answer, i get the following error from CUCM: "Your call can not be completed as dialed. Please consult your directory.... blah blah blah" 

The only difference on the version 7 cluster is the fact that there are less connection ports registered and that i had to make those changes to the translation patterns. 

I'm not sure why a phone that is forwarded to the VM pilot wouldn't work, but the CTI route point does. 

I'm going to check the CSS of the CTI route points, but this thing should work as configured. 

Thoughts? 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 



_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110207/d2209987/attachment.html>