Sonata Dialer: Broadcast Campaigns, how does it work?

Hello dear team

Since Broadcast Campaigns feature was added to Sonata Dialer, it seams like the Wiki doesnt mentionne it yet.

How does this really work?
We created a broadcast campaing for testing and linked it to IVR and tried others “Destinations”, but no call was done, maybe we did it wrong?

We would need to link it to a preregistered voice note or an IVR, so when the campaign will be launched, people called can here an audio preregistered

Thanks for you help

1 Like

Will destination announcement or just an IVR with instructions work?
Or what do you need exactly?

1 Like

Hello dear @mo10

Thanks for your feedback

The initial idea is to make listen to an announcement !
And if it’s also possible to redirect it to an IVR, will also be fine!

Also, the other thing we want to understand is, whenever we create the campaign and we click on Acrivate, are we able to say we want it to start at 12:00?

Best regards

1 Like

Hello!

We will work on the documentation for this module so you can better understand how it functions.

First, make sure you have set your timezone in the S. Dialer: Settings > General Settings.

Then, run the command: systemctl restart sonata-dialer-worker

Afterward, please check your outbound route settings. Create a new campaign and select “IVR” (left field) for the destination, then select the IVR (right field) you configured in VitalPBX.

Regards!

The S. Dialer checks if the current date and time are within the active campaign(s) parameters.

For example, if it is 10:00 AM on July 1st, and this date and time fall within the range configured in the campaign (start date, end date, start shift, end shift), then the Dialer will generate calls if there are pending contacts to be called in that campaign.

It’s worth noting that the S. Dialer usually starts making calls 5 minutes after it detects that the current date and time are within the campaign’s working hours.

3 Likes

You can do an announcement and add the ivr to its final destination.
But check welcome message and instructions message on ivr. Should be what you need.

1 Like

Hello dear @maynor abd @mo10

Thanks for valuable feedback.
We tested the suggested ways and was able to move forward, but when the campaign launches, call failed as there is not specified Extension (from) and the CallerId. Please see on attached screenshots.


Thanks again

1 Like

Hello,

We are working on making the CID name and CID number configurable.

We will release a new version as soon as possible.

Regards,

1 Like

Hello dear @maynor

Do you have any news regarding this please?

Best regards

1 Like

Hello!

The new version is now available: Sonata Dialer (v4.0.1-6) update available!

Regards,

Hello dear

Thanks for this great news
While testing, we found an issue. Note that:

  • Routing and outbound trunks was found to be ok as we tested the same using VitXi and working fine

Find a small screen capture bellow (and small vidéo on this link: https://youtu.be/wIEtOe6zcWs)

Best regards

1 Like

Please share screenshots of the latest log file located in /usr/share/dialer/backend/storage/logs/ (ensure to hide any sensitive information)

Hello dear @maynor

Will upload it here, meanwhile, bellow are the some suspicious likes found in that file:

[previous exception] [object] (Doctrine\\DBAL\\Driver\\PDO\\Exception(code: 42S22): SQLSTATE[42S22]: Column not found: 1054 Unknown column 'cid_name' in 'field list' at /usr/share/dialer/backend/vendor/doc>
[stacktrace]

[previous exception] [object] (PDOException(code: 42S22): SQLSTATE[42S22]: Column not found: 1054 Unknown column 'cid_name' in 'field list' at /usr/share/dialer/backend/vendor/doctrine/dbal/lib/Doctrine/DB>
[stacktrace]

1 Like

I have added the complete file in the HelpDesk ticket itself

Please check

Please run the following commands:

cd /usr/share/dialer/backend/
php artisan migrate --force

Afterwards, reload the app and try again

1 Like

This is done

Let’s test again

1 Like

dear @maynor

We have scheduled some campaigns as we done before but they stick in Pending mode

  1. Start shift time : we usually put 10 minutes after the current Time
  2. TimeZone is correct

1 Like

Check if you have selected the correct time zone in Settings > General Settings.

Also, have you performed the call test before creating the campaign?

1 Like

Also, run the command:

systemctl restart sonata-dialer-worker

and try again (with a new campaign)

Timezone was correctely selected before

Also, the test call failed as well as you can see on this screenshot

1 Like