If my current time is 11/16/2018 , 8AM , it checks and comeback as working day ( Holiday set to false) , But if the current time is 11/16/2018 , 10 AM , it comeback as working day instead of closed ( Holiday set to true) . We cannot push this to production. Need help to check the script.
It sounds like what you are describing, that it's working as designed.
The Holiday document's intention is to close the call center for the entire day, unless a new set of open and close hours are specified, in which case, the call center will be open during those hours, and closed otherwise.
Are you expecting the opposite? Like, if you specified an open and closed time for a day, those are the hours you want to close the call center, and otherwise, it should be open?
If that's the case, then you'll just need to either:
A) re-write the logic to its inverse
B) Use two dates/tome for each date
<!-- First part of the day, we're closed -->
<!-- The inbetween time (7:00am to 9:00am) we're open -->
<!-- The second part of the day, we're closed again -->
Please use the star ratings to help drive great content to the top of searches.
Im new to this i have deployed expressway E & C all clients are good anroid apple whatever they can register and place and receive calls while registered to cucm my question is if someone on the internet in a different domain wants to uri dial on phon...
Cisco IOS support for voice traffic and voice routing has transit a long road since Cisco started to add voice support to a device that was originally design to route data packets only.
Originally only H.323 session was supported using H225...
attached a brief questionnaire to gather basic data for a Cisco IPTel/UC solution (can be filled by customer or partner). This is v1 - based on feedback I will optimize further.
Need a quick summary of CUCM/BE6K licensing?
Below you can find one slide summarizing user cases and CUCM licensing requirements (can find it also as attachment)
Slides include also some explanation notes and below summary: