I have a problem I want to solve with the "always hold" call handler option.<br>Question is:<br>Once the call is placed into hold, can I have a time out configured to force the call back to a given extension or <br>call handler?<br><br>Someone please tell me I can do this.<br><br>Scott<br><br><br>
the hold conversation comes back after finishing the hold music prompt (there are 10 of these) and gives the caller the opportunity to continue holding or bailing out. There's no way to limit how long they can choose to hang out on hold, they can do it all day if they want.
We are trying come up with a poor man customer service queue. Ext. 1000 rolls to 2000 rolls to 3000 using sup. transfer. If all are busy go to hold for "a while" and loop back to 1000 to start over again.
You should be able to do that with supervised transfers and a chain of call handlers... make call handlers for each extension, activate the alternate greeting and transfer rule (which will keep them active all the time), select blank greeting and set the after greeting action to try to transfer to the next call handler in the chain. The last call handler can play a greeting such as "press 1 to leave a message" or "you're call is important to us, please continue to hold" and then have it try the extension for the first call handler again or something along those lines.
the supervised transfer will get a busy event right away when it goes to try the extension so it should whip through those extensions in nothing flat... be sure to have a decent greeting recorded (you can copy in the hold music even if you want) before restarting at the begining of the chain again...
you can eyeball the status monitor manually and see how many calls are cruising through the handler list real time. The Handler Traffic report will also give you some insight into how many folks are tied up in here.
I'm guessing, however, you want to be able to limit how many folks can be chewing up ports doing this and there is no way to do that.
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...