<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>The great thing about CTI route points is that (as far as I know) you can assign them to ccmuser IDs and have users modify the call forward all setting if required. <br><br>---<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>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Dane" <dane@pktloss.net><br>To: "Wes Sisk" <wsisk@cisco.com><br>Cc: cisco-voip@puck.nether.net<br>Sent: Sunday, April 26, 2009 9:44:06 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] Fake phones - Call Forwarding?<br><br>Glad to read the responses so far! CTI route points was the direction<br>I was heading and is what I have used in the past for this. However I<br>wasn't sure how licensing might affect things nor was I sure about<br>system resources, limitations (can you configure only x number of) or<br>device weight of one option over another which is why I was seeking<br>the advice of the collective since we have some very wise people on<br>the list. :-)<br><br>So far of the three responses all have mentioned and suggested CTI<br>route points which makes me feel a bit more comfortable about my own<br>decision to use those.<br><br>Thanks for the responses so far they have been very helpful.<br><br><br><br>On Sun, Apr 26, 2009 at 12:49 PM, Wes Sisk <wsisk@cisco.com> wrote:<br>> You can use CTI ports instead of phones which are not licensed. One<br>> obstacle down.<br>><br>> You could attempt to use unassigned DN's but that will not work due to:<br>> CSCsj95732 CM 5.x / 6.x - Inactive or Unassigned DN with CFA still<br>> forwards calls<br>><br>> Either CTI Ports or straight up number translation will likely be best<br>> approach. Number translation via translation pattern in CM or<br>> translation-rule on your h.323 gateway.<br>><br>> /Wes<br>><br>> On Sunday, April 26, 2009 12:01:55 PM, Dane <dane@pktloss.net> wrote:<br>>><br>>> Got a CM 4.1(3) system that I inherited that was setup with a bunch of<br>>> fake phones to do call forwarding on old extensions / DIDs.<br>>><br>>> The story is that when they moved buildings they setup a new<br>>> CallManager system with new extensions and DID's for the<br>>> administrative office phones / users. This allowed them to setup and<br>>> test everything in advance.<br>>><br>>> When they moved they ported the old DID's over and set up fake phones<br>>> to match the old ext. and then set the CallFwdAll to the users new<br>>> extension.<br>>><br>>> There is no easy way of mapping old DID's to the new ones. Also a lot<br>>> of these fake phones forward to another legacy system that runs the<br>>> call center agents.<br>>><br>>> Anyway.. despite how I may feel about what was done and why I need to<br>>> get past that. :-)<br>>><br>>> The point of sharing this is I need a better way to handle and setup<br>>> these forwards. Why? Mainly because I am planning to move to CM 7 by<br>>> the end of the year. In my discussions with Cisco sales guys they<br>>> informed me how different licensing is now in the new versions and<br>>> kept asking for phone count since the licensing is impacted by phone<br>>> count.<br>>><br>>> I can't give them a good count right now due to the shear number of<br>>> fake phones that are setup to do this call forwarding.<br>>><br>>> There are many ways to do this but I am not sure what the best way is,<br>>> especially when factoring in licensing.<br>>><br>>> Thoughts or ideas on best way to handle call forwards without setting<br>>> up a fake phone? And ensure I don't run into another issue that would<br>>> impact licensing like fake phones would?<br>>><br>>> Obviously I am not just talking about a handful of phones. We are<br>>> talking hundreds of these fake phones that just do call forwarding.<br>>><br>>> Thanks in advance.<br>>> _______________________________________________<br>>> cisco-voip mailing list<br>>> cisco-voip@puck.nether.net<br>>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>>><br>><br>><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>