03-26-2010 07:26 AM - edited 03-15-2019 09:59 PM
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
Solved! Go to Solution.
03-29-2010 12:13 PM
Java's catch is an example why I recommend avoiding
Java, great catch (+5 to you crazy man).
Regards,
Bill
Please remember to rate helpful responses and identify
03-26-2010 07:41 AM
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
03-26-2010 08:25 AM
Hi Rob,
Thanks for the info.
The video does not work. I have tried it on IE7 & Mozilla. Any other suggestions?
Thanks,
Jaime
03-26-2010 08:35 AM
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:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmsys/a03tod.html#wpxref46259
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmcfg/b03tipd.html
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
03-26-2010 08:47 AM
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
Cheers!
Rob
03-26-2010 12:30 PM
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
03-26-2010 12:36 PM
Basically if DNs are in the partition.
03-26-2010 01:03 PM
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
03-26-2010 01:16 PM
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
03-26-2010 01:25 PM
Thanks Rob! I must have over looked that link.
Jaime
03-29-2010 06:44 AM
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
03-29-2010 09:41 AM
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.
Please remember to rate helpful responses and identify
03-29-2010 11:23 AM
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
03-29-2010 12:52 PM
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
03-29-2010 01:03 PM
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
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.
Please remember to rate helpful responses and identify
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide