[cisco-voip] Attendant Console and Hunt List

[Israel Lang]

My only concern with TOD is that it is a hard and fast rule? Or is my
assumption incorrect?

For example what if for some reason I have a receptionist in after 5 or on a
weekend for some reason. Anyway the AC can take precedence over the TOD
partition?

As always, thanks for your insight Ryan.

On 4/3/07, Ryan Ratliff <rratliff at cisco.com> wrote:
>
> You could put the hunt pilot for the broadcast line group in a TOD
> partition and make it the same dn as the AC pilot point.  In all of
> your CSS' make sure the TOD partition is higher than the AC pilot
> point partition.  This way when the TOD partition is active (non-
> business hours) calls route to the broadcast hunt pilot.  When the
> TOD partition is inactive calls route to AC.
>
> -Ryan
>
> On Apr 3, 2007, at 11:30 AM, Israel Lang wrote:
>
> I have a 4.1(3) CM cluster and am trying to develop a call routing
> plan that will do the following:
>
> During normal business hours (M-F 8-5) a couple of receptionists are
> available and use AC to log in and out of the hunt group as well as
> see who is on the phone etc.
>
> After hours we would like calls to be broadcast to eight different
> phones throughout the facility.
>
> What is the best way to accomplish this?
>
> I have been able to add a dummy extension to the AC hunt group that
> forwards to a hunt pilot that then uses the appropriate hunt lists
> and line groups to do the broadcasting. This seems to be a bit clumsy
> and was wondering if there was a more efficient and/or elegant way to
> do this.
>
> Thanks.
>
> --
> Have a great day!!!!!!!!!!
> zephy316_gmail.com
>
> Replace the _ with an @ symbol
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>



-- 
Have a great day!!!!!!!!!!
zephy316_gmail.com

Replace the _ with an @ symbol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070403/0925870e/attachment.html