I have an application that I need to know the expected delay for the call that is currently in the queue (in other words, how much the call will need time till be removed from the queue and routed to the agent)?
I found the ExpectedDelay and the AvgDelayQNow variables, but both of them does not give me the needed time for the specific call, because the ExpectedDelay gives the needed time for the new call entered the queue, and the AvgDelayQNow gives the average delay for the call in the queue.
Any one can advise for a variable in the DB that I can read it from the CRS to use it in my CRS script, this variable gives the expected time for a specific call existed currently in the queue?
I am looking to know the expected wait time for the caller in the queue, to know if to give him the option to leave the queue and we can call him back or no need for the option to be prompted (in case the expected wait time is less than specific value).
I was trying to know the position in the queue so I can use it to calculate, but I did not find any possibility to know the position in the queue for the caller, so now I am tying to know the expected call delay of the caller in the queue directly if possible?
ED is expected delay and you need a custom script for it.
Basically you would need a Get Reporting statistics step to check on the estimated wait time, and on top of it use an If step to check if -1 got returned indicating an inability to calculate due to insufficient short historical data (the contact center just opened or there are no agents logged in). If it is -1, then don't announce anything.
All this is material for the dev support services group.
Try a search in the forum, it might be a couple of possible samples of similar scripts have been posted already.
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...