Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Time of Day Routing

I am trying to use TOD for the following:

I need DN 2880 to ring normally between the hours of 8:30am - 5:15pm Monday - Friday.

Between the hours of 5:15pm - 8:30am Monday - Friday & all hours Saturday - Sunday I need DN 2880 to route/forward calls to an external number.

Can somebody please provide me with some info on what would be my best bet on the config?

Currently running on CUCM 6.1.3

Thanks,

Jaime

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Time of Day Routing

Java's catch is an example why I recommend avoiding partitions and CSS configurations.  There are cases where the CSS may be used (such as line level restrictions, i.e. "unrestricted" lines).  But, I have never found a good reason to use for route patterns/translation patterns/directory numbers/etc.  It is just too problematic.

Java, great catch (+5 to you crazy man).

Regards,
Bill

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

21 REPLIES
Hall of Fame Super Red

Re: Time of Day Routing

Hi Jaime,

This should work using ToD (Time of day Routing), why don't you go through this excellent presentation on Time of Day Routing (it includes a great step by step and examples);

http://www.cisco.com/E-Learning/bulk/public/celc/CMToD/player.html

Hope this helps!

Rob

PS:If you have trouble opening it try using Mozilla

Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com/docs/DOC-8727

New Member

Re: Time of Day Routing

Hi Rob,

Thanks for the info.

The video does not work.  I have tried it on IE7 & Mozilla.  Any other suggestions?

Thanks,

Jaime

Cisco Employee

Re: Time of Day Routing

Must be something on your machine, just tested the link and the video works fine..

Try another machine/browser (I use firefox) or read the guide:

Time-of-Day Routing

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmsys/a03tod.html#wpxref46259

Time Period Configuration

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmcfg/b03tipd.html

Time Schedule Configuration

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmcfg/b03tisch.html

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
Hall of Fame Super Red

Re: Time of Day Routing

Hi Jaime,

Sorry about that, it worked for me last week, but it's a little

"hit and miss". It's too bad as it's a great presentation.

This doc is pretty good as well

Unified Communications Manager 6.x: Time-Of-Day Routing Configuration Example

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_example09186a0080a7bc96.shtml

Cheers!

Rob

New Member

Re: Time of Day Routing

Rob,

I recently moved to this company.  The current setup here is that Directory Numbers are not assigned to Route Partitions.  How would the calls be routed then?  Would that mean Route Partitions are assigned to the Gateways?  I having issues setting up ToD when assigning Route Partitions to Directory Numbers.  Should I be trying something different?

Thanks,

Jaime

Super Bronze

Re: Time of Day Routing

Basically if DNs are in the partition.

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
New Member

Re: Time of Day Routing

Does it make a difference when trying to setup ToD if all DNs are not assigned to Partitions and only 1 Translation Pattern is created for the whole block of DIDs?

Thanks,

Jaime

Hall of Fame Super Red

Re: Time of Day Routing

Hi Jaime,

Are you using the doc I sent in my second post? It shows the step by step

for this config and assigns "new" Partitions and "new" CSS - Calling Search Spaces

The relationship between a DN and Partition is built via the CSS, so the "new" required CSS

is assigned to the DN as the last step in the config.

Make sense?

Cheers!

Rob

New Member

Re: Time of Day Routing

Thanks Rob!  I must have over looked that link.

Jaime

New Member

Re: Time of Day Routing

Hi Rob,

Thanks for that link.  It made complete sense but unfortunately it did not work.  I think that the issue might be that we only have one Translation Pattern created for my whole block of DIDs.  Something along these lines ( 708455.XXXX) and the Called Party Transform Mask is XXXX.  Could this be causing an issue when I create my 2 separate Translation Pattern like stated in the documentation?

Jaime

Re: Time of Day Routing

Jaime/Rob,

Forgive me if I am coming out of left field on this. You are in good hands with Rob (+5 to Rob for great references) and hopefully I am adding value as opposed to adding confusion here!

If I follow the thread, Jaime is looking for a way to enable ToD routing for a broad range of extensions.  Is this correct?  If so, then you could adjust your dial plan to accomodate this requirement.  Your present DP design will determine how much of an adjustment you would need.

When I think of ToD routing I take the approach of using Schedules that "enable" the route partition during the "closed hours" rather than the other way around, which I see in most Cisco docs.  A sample call flow is attached (the follow example uses the example call flow).

The idea is that the voice gateways have a CSS assigned which is configured with two partitions:

1. TOD-Sample_PT

2. Tenant-Extern_PT

Partition #1 is on a schedule that will "hide" it during normal hours and "expose" it during closed hours.  Both partitions contain an identical translation pattern.  But the translation pattern for TOD-Sample_PT will send callers to an "after hours" call treatment on a Unity system (for example).  During normal hours, the translation pattern in Tenant-Extern_PT will send the calls to IP phones.

Basically, the TOD-Sample_PT is intended to store patterns that are either as specific as those in Tenant-Extern_PT or more specific.  If patterns are identical in the two partitions (as shown in the sample diagram) then the TOD-Sample_PT is preferred since it holds the highest priority position in the PSTN-In_CSS.  If you find you want to exclude certain numbers/ranges from the default TOD treatment then you simply add more specific patterns in Tenant-Extern_PT.  If, you only want TOD treatment on a small subset of the overall range, then you do the opposite.  Put a generic range on Tenant-Extern_PT and a more specific range on TOD-Sample_PT.

A key concept here is that the example uses the partition priority and digit matching rules of CUCM to accomplish the objective.  We enable ToD schedules so that patterns intercept or redirect calls away from normal destinations when the schedules are enabled.  It is a subtle difference from how most Cisco docs present the topic, but I tend to prefer the approach discussed above.

Another key concept, is that we are catching the call for ToD analysis as it enters the system and we are putting a "control" mechanism between the call origination point and final destination.  This is key.  Think of it as making a preliminary routing decision based on ToD and then making a final routing decision based on the translated number.

As far as 10-digit versus 4-digit.  In the example I use all 10-digits (that is because for NANP, 10d is the only way to fly (IMO)).  That being said, if you configured both translation patterns to truncated the called party number to 4d, it would still work like a champ.

HTH.

Regards,
Bill

Please remember to rate helpful posts.

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

Hall of Fame Super Red

Re: Time of Day Routing

Hey Bill,

Really,really fine answer here! One of the best (if not the best!) ToD explanations I have

ever seen +5 for this great work!

Cheers!

Rob

New Member

Re: Time of Day Routing

Bill,

I will be using the following procedure you provided.  Thanks by the way!  Great info.

ADD:

*1.Partition: "DID to EXT AfterHours" *

**

*Schedule*: *Non_Business_hrs_TS (note: if you prefer, use Non_Business_par)

*

*2.* *Translation Pattern: 7084552880*

*Partition: (DID to EXT AfterHours)*

*Calling  Search Space: (NONE) [note: you could still use none, but see advice above]

*

*Called Party Transform  Mask: (5880)*

MODIFY:

Your existing gateway CSS (e.g. Gateway_CSS) to include the following partitions:

Partition Order 1: DID to EXT AfterHours (or use Non_Business_par if you prefer) Partition Order 2: DID to EXT

REMOVE:

1. Translation: 2880/Business_par

2. Translation: 2880/Non_Business_par

3. Schedule: Business Hrs TP (unnecessary at this point)

Now, without other info on your design the above would apply ToD rules for ingress calls from the PSTN but allow your IP phones to route bypass the ToD rules.  Meaning, an IP phone using CSS1 and calling 2880 will reach 2880 all the time and never be re-routed to 5880.

Quick question:

My Gateway is using CCS (Chicago-International).  CCS (Chicago International) has several Selected Partitions including DID to EXT.  Would adding Partition (DID to EXT After hours) affect any other calls associated with the CCS (Chicago International)?  Can you please let me know before I make the change.

Thank,

Jaime

Re: Time of Day Routing

Jaime,

Ensure you put the "DID to EXT AfterHours" in a postion that is higher than "DID to EXT" and you should be fine as long as you don't have any numbers in or the other partitions in the Chicago gateway CSS that have a leading digit string of "7084", "70845", etc.  Technically, even this wouldn't present a problem unless urgent priority comes into play.  But, if you do have an overlap look at it closely before applying changes to be sure.

Note that you can use DNA as another check point if that makes you feel more comfortable.  I believe that DNA can take the ToD routing into consideration.

DNA (if you are unsure of what this is) is a tool that analyzes dial plans.  It is relatively simplistic.  You can select gateways, phones, lines, etc. or just a CSS and then enter a phone number to "dial".  The tool will kick out a report on what would happen to the call based on the configuration in the CUCM.  DNA stands for Dialed Number Analyzer.  You can get to it on your CUCM using the following url:  https://yourcucmnode/dna.  You do have to enable DNA in the Service Activation page on the CUCM before you can use it.  On CCO, you can search for Dialed Number Analyzer to get all kinds of text on how to use the tool.

HTH.

Regards,
Bill

Please remember to rate helpful posts.

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

New Member

Re: Time of Day Routing

Bill,

All DNs are in the (NONE) Partition.  Half of the IP Phones have the CCS (Chicago International) assigned to them.  Also, 708455 is the prefix to all DIDs.  Is that going to be an issue?  I have been here for about 6 weeks.  A consultant company setup the VoIP a few years back.  Not sure why they configured DNs without Partitions and all DIDs to use 1 TP.

Thanks,

Jaime

Re: Time of Day Routing

Jaime,

Again, you can use DNA to check call flow issues.  You can also run a Route Plan report to check for overlaps.  If your phone DNs are all assigned 4-digits and your translation is handling 10-digits then you want to see if any 4-digit phone line DNs overlap with NPANXX assigned to the 10-digit DIDs.

HTH.


Regards,
Bill

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

New Member

Re: Time of Day Routing

Bill,

Ok will do.  Thanks for the info.

Jaime

New Member

Re: Time of Day Routing

Bill,

Thanks for all the useful knowledge.  Below is what I am trying to accomplish and what I have configured.

I need ext. 2880 to take calls from 8:15am - 5:30pm.  Between the hours of 5:30pm - 8:15am I need the calls entered to 2880 routed to ext. 5880.

I created the following:

3 Time Periods:

Business Hrs TP:             Time Of Day Start: 8:15   Time of Day End: 17:30  Monday - Friday

Non Business Hrs TP1:     Time Of Day Start: 17:30   Time of Day End: 24:00  Monday - Friday

Non Business Hrs TP2:     Time Of Day Start: 00:00  Time of Day End: 8:15  Monday - Friday

2 Time Schedules:

Business_HRS_TS:          Selected Time Periods - Business Hrs TP

Non_Business_hrs_TS:     Selected Time Periods - Non Business Hrs TP1 & Non Business Hrs TP2

2 Partitions:

Business_par:                 Time Schedule (Business_HRS_TS)

Non_Business_par:         Time Schedule (Non_Business_hrs_TS)

1 Calling Search Space:

CCS1:                            Selected Partitions: (Business_par & Non_Business_par)

2 Translation Patterns:

2880

Partition: (Business_par)

Calling Search Space: (CCS1)

Called Party Transform Mask: (2880)

2880

Partition: (Non_Business_par)

Calling Search Space: (CCS1)

Called Party Transform Mask: (5880)

Existing Translation Pattern:

708455.XXXX

Partition: (DID to EXT)

Calling Search Space: (NONE)

Called Party Transform Mask: (XXXX)

Discard Digits: (PreDot)

Please let me know if this is the proper config for what I am trying to do.  The only other thing I have configured is the IP Phone to use Calling Search Space: (CCS1).  The Directory Number is not assigned to any Partition.

Thanks,

Jaime

Cisco Employee

Re: Time of Day Routing

If you already have a 2880 with no partitions the TP 2880=2880 just loops.

A no partition DN is always at the bottom of the CSS, while you already have 2x2880 that will have a higher preference at all times.

Best match rule, you will always reach a TP but never the 2880 with no partition. The 2880=2880 matches over and over until the hop count drops the call.

The CSS from TP 2880=2880 needs to be blank to reach the original 2880 with no partition.

If 5880 is in no partition you should be able to reach it with no problem, if it's in a partition then fix the CSS from that TP to reach it.

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi

Re: Time of Day Routing

Java's catch is an example why I recommend avoiding partitions and CSS configurations.  There are cases where the CSS may be used (such as line level restrictions, i.e. "unrestricted" lines).  But, I have never found a good reason to use for route patterns/translation patterns/directory numbers/etc.  It is just too problematic.

Java, great catch (+5 to you crazy man).

Regards,
Bill

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

Re: Time of Day Routing

Jaime,

Well, using the CSS and partition is a bad idea in general.  At least, that is my opinion.  Except for some corner cases, I always recommend that a customer uses actual partition and CSS assignments.  It becomes a fundamental necessity for dial plans that start having a need for any degree of complexity or scalability.  So, take that for what its worth.

[EDIT:  Note Java's catch on the loop as an example]

Given the config you have below, I have to assume that your gateways have a CSS assigned that includes the partition "DID to EXT" at a minimum.  So, given that configuration/assumption I would consider the following.

ADD:

1.Partition: "DID to EXT AfterHours"

Schedule: Non_Business_hrs_TS (note: if you prefer, use Non_Business_par)

2. Translation Pattern: 7084552880

Partition: (DID to EXT AfterHours)

Calling  Search Space: (NONE) [note: you could still use none, but see advice above]

Called Party Transform  Mask: (5880)

MODIFY:

Your existing gateway CSS (e.g. Gateway_CSS) to include the following partitions:

Partition Order 1: DID to EXT AfterHours (or use Non_Business_par if you prefer)

Partition Order 2: DID to EXT

REMOVE:

1. Translation: 2880/Business_par

2. Translation: 2880/Non_Business_par

3. Schedule: Business Hrs TP (unnecessary at this point)

Now, without other info on your design the above would apply ToD rules for ingress calls from the PSTN but allow your IP phones to route bypass the ToD rules.  Meaning, an IP phone using CSS1 and calling 2880 will reach 2880 all the time and never be re-routed to 5880.

If you require both PSTN and On-Net people to conform to the ToD routing rules, then do this:

MODIFY:

1. Existing 708455.XXXX translation pattern

Calling Search Space: CSS1

2. Modify CSS1 calling search space to include  the following partitions:

Partition Order 1: Non_Business_par

Partition Order 2: Phone_par (Move all phones to a phone partition to avoid loop/overlap/etc.)

3. Phones

Add all phone DNs to partition: Phone_par

KEEP:

1. Translation: 2880/Non_Business_par

REMOVE:

1.  Translation: 2880/Business_par

2. Schedule: Business Hrs TP (unnecessary at  this point)

Again, the above assumes nothing else is going on in the dial-plan worth mentioning.  I definitely recommend that you move away from using partitions and calling search spaces.  Even if this is in your lab environment, you should apply a dial plan with a little more structure.  It will make your life easier in the long run.

HTH.

Regards,
Bill

Please remember to rate helpful posts.

Message was edited by: William Bell

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

4117
Views
25
Helpful
21
Replies
CreatePlease to create content