Agent Alert Filename Inbound Campaign

[IanGP]

Hi There,
We are setting up our call centre to run several inbound campaigns.
Agents will be handling multiple campaigns.
As it stands, the Agent Alert is the default 'Ding', but we want each inbound campaign to have a custom Agent Alert.
For example, "Incoming Call For Campaign xxx" and "Incoming Call For Campaign yyy" etc....

Custom files have been created in the required format (16bit Mono 8k PCM WAV), uploaded via Voice Files and selected via the Audio Chooser in Inbound.
Agent Alert Delay is set to 5000 (the length of the recording).
Went to Admin > Servers > Sounds Update.

But still the default 'Ding' is the only sound heard.

Any ideas as to how to get my custom file playing?

I've searched Vicidial forum, posted on GoAutodial forum, purchased the Managers Manual.... and have found no solution yet.

Thanks
Ian

Vicidial
VERSION: 2.9-441a
BUILD: 140612-1628

[williamconley]

selected via the Audio Chooser in Inbound.

I don't see where you set the Ingroup's "Agent Alert Filename". Also, have you verified that the calls in question are actually passing through the Ingroup which you changed?

CLI output from a single instance would be very useful (not 3000 lines of unrelated code or mixed in other phone calls, just a single instance of this type of call from beginning to end ...)

Version 2.9 is fairly old. You should consider upgrading and/or reinstalling with Vicibox's .iso installer. I also don't see your Installer with Version which is often very helpful.

[IanGP]

Thanks for the reply.
Perhaps the newer versions of Vicidial have the "Agent Alert Filename" elsewhere, but on 2.9 it's under Inbound > Show In-Groups > [select the in-group in question and scroll through detailed options]

The call is definitely going through the correct ingroup.

Cheers
Ian

[williamconley]

You earlier listed things that you changed, and that setting was not among those listed. So I assumed you didn't make that change.

Next up: You could post a CLI example of a single call (not 3000 lines of unrelated logging, no other calls on the system, as a test).

Do remember that this support forum is for Technical support. Details are where this stuff is resolved. Not listing them leads to assumptions ... which is often why a failure occurred in the first place. So posting all relevant configuration information and test steps is a good idea (and avoiding posting excessive/unrelated data is useful, too).