12.07.2015 Views

Admin Guide - Mizu Voip

Admin Guide - Mizu Voip

Admin Guide - Mizu Voip

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

- Waituntillconnected: if set to false, than will dropp started call when no more operator waiting (no more "No free operator on predective"disconnect reason)4.9.12. Outgoing callbackThere are two types of callbacks:1. operator set Recall (1) manually2. server receive an incoming call and set to Callback (2) automaticallyClient records will be marked when callbacks or recalls are needed. The following values are defined for the „needrecall” field:-0: not set-1: recall set by operator-2: callback set because incoming call-4: recalled-5: callback completedCallbak numbers:Special A numbers are the followings:- callbacknumber- predective dialer number- identityrewrite number for outgoing proxythese should be set to the same number. By default it is loaded from „callbacknumber” global setting*if the callbacknumber is not set, the predictive dialer will use “1111” by default* identityrwmode global setting should be set to 1 for callcenters*if the CLI is hided, than there will be NO incoming calls,to enable CLIP you must set the “identityrwmode” setting to 1 or set the CLI for users to 1The „callbackhandling” global setting will determine how incoming calls to callbacknumber will be handled. Incoming calls when the caller is not found inany campaign will be inserted to the client table with a name set to “unknown callback”.Make sure to setup the callback number on the main server to be routed to the actual virtual server! (check faq)4.9.13. Incoming callsIncoming calls can be handled in different ways:1. Simple distribution across operators

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!