ā06-01-2015 02:39 AM - edited ā03-17-2019 03:11 AM
All,
I am experiencing a problem with the following setup:
Partition: Internal
Time Schedule: NONE
Directory Number: 12345 -> Call Forward All -> Unity Call Handler
Partition: Out Of Hours
Time Schedule/Period: 'Out Of Hours' 20:00-08:00
Translation Pattern: 12345 -> Out Of Hours Answering Service 01234 123456
When I dial out of hours, the Directory Number seems to take precedence and I end up hitting the Unity Call Handler.
We have this working in the exact same way with other dialling entities (A Translation Pattern in Internal and Out Of Hours), however this is the first one we have setup with a Directory Number to hit the Unity Call Handler.
Does anyone have any ideas as to why this isn't working?
Thanks
D
Solved! Go to Solution.
ā06-01-2015 04:52 AM
Is the out of hours partition listed higher than the internal partition within the calling search space?
Try one schedule from 20:00 to 24:00
and another schedule 00:00 to 8:00
instead of 20:00 to 8am
See link below. Good document duscussing time of day routing.
https://supportforums.cisco.com/document/32171/cucm-night-service-design-using-time-day-call-routing
Hope this helps,
Please rate helpful posts.
Thanks.
ā06-01-2015 04:52 AM
Is the out of hours partition listed higher than the internal partition within the calling search space?
Try one schedule from 20:00 to 24:00
and another schedule 00:00 to 8:00
instead of 20:00 to 8am
See link below. Good document duscussing time of day routing.
https://supportforums.cisco.com/document/32171/cucm-night-service-design-using-time-day-call-routing
Hope this helps,
Please rate helpful posts.
Thanks.
ā06-02-2015 12:59 AM
Thanks for the reply Charles. In this example the CSS being used on the Translation Pattern for both day and night service is called 'CSS-INTERNAL-ALL'.
As I write this Im guessing the OOH Partitions need to be higher in the CSS that PT-Internal?
Thanks for the link, very helpful and this does show day/night partitions higher than the Internal partition.
Dean
ā06-02-2015 12:42 PM
All,
I managed to resolve this by essentially starting again... :) The link provided was a great read thank you.
The fix for the problem was a combination of wrongly ordered partitions and also the night service Translation Pattern in the OOH partition didn't have the correct calling privileges to ring the required PSTN number. This is now resolved!
D
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