You could open all canvases you need and switch the display by using a vbscript or program which simulates keystrokes. Sending ALT+ESC switches to the next application. A program like Winmacro records key and mouse events which you could play back in a loop.
The AlertManager doesn't execute a script it gets the data through a native interface from the ACD.
The log messages are stored in formatted text files. The contents is shown through the web interface.
If you have a Contact Server link to the ACD and the IVR supports it, sending a TCR (Transfer Call Request) would transfer call x into a new CCT and possibly an agent if you want. All trunk allocations between ACD-IVR are resolved and at no point 2 trunks are used between ACD-IVR. You don't need...
the rolling DNIS is for transferring the call, not for making the decision if a transfer should happen.
ECS 5.2 comes with Realtime Grabber which picks up Infograms and writes them into timesten tables. So no need to develop, just install and configure. Configuring could be more intuitive...
if you have ACD 1 and 2 on a the same network you can use the Rolling DNIS / Dynamic DNIS method.
Reserve a number of DNIS numbers on the destination ACD 2. Call goes in ACD 1, kick off an eFlow, reserve on DNIS on ACD 2, store data using the DNIS as a key in the repositry. Transfer the call...
first consider where your calls come from and where they need to go. if your IVR is behind the switch you mean the Aspect ACD ? If all calls go to the ACD first and are transferred to the IVR, the new IVR also needs to provide trunks (T1 Channels or whatever will physically endpoint). This...
the real time data of the ACD can't be broken down to that level of detail. You would need Contact Server (eFlow, realtime grabber, ODBC & ACD contributor) to get this level of detail. Or Enterprise Contact Server. A custom application using the Contact Server Realtime Control would display the...
to find out is a procedure was run or not the ACD activity log is the place to go. It will show the begin/end of procedure 5:
01012005 060000 SYSINFO Background procedure activity(Begin/Comp Action BEGIN ProcNum 5
01012005 060000 SYSINFO Background procedure...
dur_idle shows idle time since midnight no matter which reason code.
filtering reason_num for 1-99 should work, however if the last agent leaves the state (reason code) you are filtering for, the sum of zero fields is nothing. An aggregate sum() field would show ??? as there is nothing to sum...
upgrade to 9.0 SP3 CM3+ better the latest available.
There was an issue which I don't want to explain, otherwise people may want to try this out. Check the release notes
you can optionally pass a variant array with the winset settings (com-port, language, ...). The online help has an example.
winset.LocalAdapter.SignOnLocalAdapter("7075", "2444") would also work, if the agent did the settings with the Winset Gui before.
one of many ways, either on call disconnect or on agent state event idle/wrap-up you could popup a box filled with codes/descriptions. Send a workflow request to the eflow with your parameters, intrument, agent id, code and the eflow can enter it in your database.
If you want to data in the ACD...
- you can play sounds if a call is waiting. Obvioulsly you won't see waiting indicator when the application is not visible, but when the SDK comes out you can do your own popups. Till then a CTI application can do that
- I don't understand the headset issue. Uniphi Connect gives you a callback...
Since Genesys T-Servers requires to be connected to a Aspect Contact Server, since the application bridge which previous version of T-Server used is not supported any more. Unless you look for features Genesys has and Aspect doesn't you'll have two products do the same.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.