Translate

When this option is set to YES, the following manager events will be generated: AgentCalled, AgentDump, AgentConnect and AgentComplete.
SourceTranslationState
203
When set to 'Yes' agents who are on an occupied phone will be skipped as if the line were returning busy. This means that Call Waiting or multi-line phones will not be presented with the call and in the various hunt style ring strategies, the next agent will be attempted. <br />When set to 'Yes + (ringinuse=no)' the queue configuration flag 'ringinuse=no' is set for this queue in addition to the phone's device status being monitored. This results in the queue tracking remote agents (agents who are a remote PSTN phone, called through Follow-Me, and other means) as well as PBX connected agents, so the queue will not attempt to send another call if they are already on a call from any queue. <br />When set to 'Queue calls only (ringinuse=no)' the queue configuration flag 'ringinuse=no' is set for this queue also but the device status of locally connected agents is not monitored. The behavior is to limit an agent belonging to one or more queues to a single queue call. If they are occupied from other calls, such as outbound calls they initiated, the queue will consider them available and ring them since the device state is not monitored with this option. <br /><br />WARNING: When using the settings that set the 'ringinuse=no' flag, there is a NEGATIVE side effect. An agent who transfers a queue call will remain unavailable by any queue until that call is terminated as the call still appears as 'inuse' to the queue UNLESS 'Agent Restrictions' is set to 'Extensions Only'.
204
When set to YES, the following manager event will be generated: QueueMemberStatus
205
When set to Yes agents devices that report busy upon a call attempt will be considered as a missed call and auto paused immediately or after the auto pause delay if configured
206
When set to Yes agents devices that report congestion upon a call attempt will be considered as a missed call and auto paused immediately or after the auto pause delay if configured
207
When set to Yes, the CID Name will be prefixed with the total wait time in the queue so the answering agent is aware how long they have waited. It will be rounded to the nearest minute, in the form of Mnn: where nn is the number of minutes.
Impostando su Sì questa opzione, l'ID Chiamante avrà come prefisso il tempo totale di attesa nella coda cosìcchè l'agente che risponde potrà sapere in anticipo quanto ha aspettato il chiamante. Sarà arrotondato al minuto, nella forma Mnn: dove nn rappresenta il numero di minuti.
208
When this option is set to YES, the following manager events will be generated: AgentCalled, AgentDump, AgentConnect and AgentComplete.
Quando questa impostazione è attivata, saranno generati i seguenti eventi del manager: AgentCalled, AgentDump, AgentConnect e AgentComplete
209
When to schedule this job. Note enabling 'Random' overrides these settings
210
Where calls should fail to
211
Whether this queue uses an IVR Break Out Menu or a Queue Callback. Queue Callbacks can also be achieved through an IVR, but requires extra configuration.
212
While queue calls are distributed, any member has FM/FM(Find Me/Follow Me) enabled, Ringer Volume value will set based on the 'Ringer Volume Override Mode(RVOM)'.
213
Wrap-Up-Time

Loading…

Loading…

Things to check

Glossary

Source Translation
No related strings found in the glossary.

Source information

Source string location
views/​form.php:635
Source string age
6 years ago
Translation file
i18n/​it_IT/​LC_MESSAGES/​queues.po, string 208
String priority
Medium