The system will playback whatever you specify to incoming callers. A table of different strategies can be found below. The strategy defines how calls are distributed in a queue. If defined to true, we'll delete all the tiers when the module is loaded. If defined to true, we'll delete all the agents when the module is loaded. This is useful if you're manipulating agent state external to mod_callcenter.
If defined to true, agent state is changed to Reserved if the old state is Receiving, the call will only be sent to him if the state get's changed. If the agent does not answer the call, wait this defined time before trying him again. If the agent is on Do Not Disturb, wait this defined time before trying him again. If the agent presses the reject button on her phone, wait this defined time amount. The amount of time to wait before putting the agent back in the available queue to receive another call, to allow her to complete notes or other tasks. If the agent fails to answer calls this number of times, his status is changed to On Break automatically.
Check the Agents Status table for more information. contactĪ simple dial string can be put in here, like: If using verto: statusĭefine the current status of an agent. uuid-standby will try to bridge the call directly using the agent uuid. callback will try to reach the agent via the contact fields value. We currently support 2 types, 'callback' and 'uuid-standby'. Useful to put into a ram disk for better performance. This is to specify a different name or path and name of the SQLite database. The callcenter will use the supplied ODBC database instead of the default behavior, which is to use the internal SQLite database.
0 kommentar(er)
