<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>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.<br><br>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.<br><br>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.<br><br>Updating my VM Pilot CSS to match the FWD CSS that I've used on the lines fixes the problems.<br><br>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?<br><br>hmmmmmm<br><br><span>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Lelio Fulgenzi" <lelio@uoguelph.ca><br><b>To: </b>"Cisco VoIP Group" <cisco-voip@puck.nether.net><br><b>Sent: </b>Monday, February 7, 2011 12:01:10 PM<br><b>Subject: </b>[cisco-voip] can dial vm pilot, but not forward to it?<br><br><style>p { margin: 0; }</style><div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);"><br>hi everyone, i'm trying to get my head around this one.<br><br>background: <br><ul><li>imported data from v4 to v7 cluster</li><li>integrated around 6 vm ports from unity connection to new v7 cluster</li><li>we have three hunt groups (auto-attendant, vm, call handlers)</li><li>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</li></ul>working:<br><ul><li>i can call the vm pilot (either vm button, or number) and connection answers appropriate, i.e. enter your pin</li><li>i can call a CTI route point which is forwarded to the call handler translation and the appropriate call handler answers</li></ul>issue:<br><ul><li>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"</li></ul>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.<br><br>I'm not sure why a phone that is forwarded to the VM pilot wouldn't work, but the CTI route point does.<br><br>I'm going to check the CSS of the CTI route points, but this thing should work as configured.<br><br>Thoughts?<br><span><br><span></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span></span><br></span><br></div><br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>