Given your examples, I assume that there is some pre-existing script logic that handles the standard open/close event. I am not sure how that logic is instantiated in the script. In scripts I have put together, the open/close/holiday/etc. checks are done right after accepting the contact.
Assuming you are doing something similar then what I would suggest is that you leverage a boolean variable to control the open/close handling. What I like to do is create the boolean variable (e.g. blnClosed) and set it to false (i.e. open by default). Then you add your test conditions to see if the CC is closed. Something like:
set blnClosed = false;
/*test for open/closed rules*/
if (blnClosed) goto CLOSED
/*handle the closed event*/
The test section will vary depending on how complex your rules are and if you have several scripts governed by the same open/close rules. You may even be callign a sub-routine that applies rules such as holidays. Getting to the specific test cases you are asking about. You will want to look at the "Day of Week" and "Time of Day" steps. You can find them here:
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...