Is there any reason you can't just put in a translation pattern for the old extension in CCM, changing the called number to the new extension?<br><br>Not sure if that will work for you, but it might be worth trying.<br>
<br><div class="gmail_quote">On Tue, May 5, 2009 at 5:46 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">alternate extensions in Unity/Unity Connection will do the trick.<br><br>if you are using a third party VM, you can use custom voicemail profiles.<br>
<br>this is the ONE things that Cisco removed from CCM 3.2 or something like that. in CCM 3.x you had a "voicemail box" field in every DN config page. IT WAS AWESOME! <br><br>then it was replaced by "voice mail profiles" which is not scalable if you want 3000 custom voicemail boxes.<br>
<br>alternate extensions aren't ideal because Unity/Unity Connection AA will never ring the alternate extension.<br><br>that being said, Unity Connection now has partitions, soooooooooo, you should be able to set up the search space of the "attempt forward" routing rule to include alternate extension partitions, but leave the partition out of any AA search space.<br>
<br>haven't tested that yet.<br><br><br>---<br><font color="#888888">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>"Bad grammar makes me [sic]" - Tshirt</font><div><div></div><div class="h5"><br><br><br>----- Original Message -----<br>From: "Jim Reed" <<a href="mailto:jreed@swiftnews.com" target="_blank">jreed@swiftnews.com</a>><br>
To: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>Sent: Tuesday, May 5, 2009 5:35:32 PM GMT -05:00 US/Canada Eastern<br>Subject: [cisco-voip] Getting To The Right Voicemail<br>
<br>We have several people who are changing extensions. I am setting up their<br>old extensions as phantoms which Call Forward All to their new extension.<br>Is there a way in the Device setup to force the new extension voicemail to<br>
take the message instead of it trying to revert back to voicemail for the<br>old extension or will I have to create a call handler for each of the old<br>extensions with the new extension as the covering voicemail?<br>-- <br>
Jim Reed<br>Swift Communications, Inc.<br>970-683-5646 (Direct)<br>775-772-7666 (Cell)<br><br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></div></div></div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>