Time-of-Day routing routes calls to different locations based on the time of day when a call is made. For example, during business hours, calls can route to an office, and after hours, calls can go directly to a voice-messaging system or to a home number.
Understanding Time-of-Day Routing
Time-of-Day routing comprises individual time periods that the administrator defines and groups into time schedules. The administrator associates time schedules with a partition. In the Partition Configuration window, the administrator chooses either the time zone of the originating device or any specific time zone for a time schedule. The system checks the chosen time zone against the time schedule when the call gets placed to directory numbers in this partition. The Time Period and Time Schedule menu items exist in the Route Plan menu under the Class of Control submenu. The Partition and Calling Search Space menu items also have moved to the Class of Control submenu.
A time period comprises a start time and end time. The available start times and end times comprise 15-minute intervals on a 24-hour clock from 00:00 to 24:00. Additionally, a time period requires definition of a repetition interval. Repetition intervals comprise the days of the week (for example, Monday through Friday) or a day of the calendar year (for example, June 9).
You can define time period weekdayofficehours as 08:00 to 17:00 from Monday to Friday.
You can define time period newyearsday as 00:00 to 24:00 on January 1.
You can define time period noofficehours that has no office hours on Wednesdays. For this time period, the associated partition is not active on Wednesdays.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.