[cisco-voip] Time Of Day Routing

[Mike King]

Yea.  In the time I took to write the first email, I know I could have done
it in Unity Connection.

I was looking to try and not use Unity Connection, since it adds
a dependency on the system.

I also don't want to have to touch all the CSS, so Unity is looking better
and better.

MIke

On Mon, May 14, 2012 at 12:42 PM, Haas, Neal <nhaas at co.fresno.ca.us> wrote:

>  Did that, will not do it again, make the Time of Day control in Unity,
> much easier – less hassle!****
>
> I use a CTI Route Point to send to Unity. In unity Create a Call Handler
> called FIRSTSTEP, our main line number is 5151, and our transfer number
> that appears on the phone is 5150. I know its crazy…****
>
> In FIRSTSTEP create the Call Handler and give it the number of 5151 .
> Select EDIT and TRANSFER RULES. You will see CLOSED and STANDARD those are
> the ones that you want to use. Under TRANSFER ACTION select Extension.
> Let’s say that our true main line extension is 5151, ****
>
> Under Greetings select Standard – After greeting select Call Handler 2. I
> always select “Attempt Transfer”, if you select “Go Directly to Greetings”
> I usually get problems.****
>
> Create a new CH called STEP TWO give it the extension 5150. Select EDIT
> and TRANSFER RULES Unselect ALTERNATE greeting! Give the extension for the
> standard Greeting!****
>
> Under Greetings and Standard under Caller Hears “Nothing”****
>
> After Greeting Call Action “Route from Next Call Routing Rule”****
>
> EDIT greeting, “AFTER GREETING”. Then select Attempt Transfer 5150.
> Transfer Rules, uncheck alternate and closed.****
>
> Test, You should be up and running.****
>
> For calendar controller, Set your Calendar in the 1st call Handler since
> this is the one that really does not control the flow. The second call
> handler just creates the transfer.****
>
> ** **
>
> http://www.newsoverload.com/?p=1179****
>
> ** **
>
> Neal ****
>
> ** **
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Mike King
> *Sent:* Monday, May 14, 2012 9:38 AM
> *To:* Cisco VoIPoE List
> *Subject:* [cisco-voip] Time Of Day Routing****
>
> ** **
>
> I have a huntlist i'm trying to setup that during business hours, it does
> one thing, and during night hours, does another thing.  It should
> be dial-able by all extensions, and external devices.****
>
> ** **
>
> Perfect opportunity to teach myself something (or so I hoped)****
>
> ** **
>
> Checked out some docs on Time of Day routing, and I think I have a
> workable plan.****
>
> ** **
>
> Here's where I need some guidiance.****
>
> ** **
>
> So all of my existing extensions are in a partition called ALL_DN.****
>
> ** **
>
> I've:****
>
>      Made time periods, and schedules****
>
>      Made two partitions, OnHours_PT, and Offhours_PT, and
> assigned appropriate schedules to them.****
>
> ** **
>
> Now I believe I have to create a CSS, and here's where I get a headache.**
> **
>
> ** **
>
> I was assuming I would make two Huntpilots, one in the Onhours partitions,
> and one in the Offhours partition, based on the example I was using.  But
> the example also put the end devices into the same CSS.****
>
> ** **
>
> If all my phones (and trunks) are in the ALL_DN parition, would I have to
> add the Onhours_PT and the OffHours_PT to all the CSS's (With OnHours
> first)? (Which is alot of CSS's)****
>
> ** **
>
> Is there a better way?****
>
> ** **
>
> Mike****
>
> ** **
>
> ** **
>
> ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120514/73c4dbe9/attachment.html>