Dialer Release v1.1
Summary
Stability focussed release, the other being exclusively used in integration testing.
All integrations are highly recommended to upgrade to this version at minimum.
Important highlights from this release
- Campaign ending refactored completely
- Campaign stopping|stopped notifications timing fixed, now sends stopping once the process is initiated, and stopped once all agents are done with their active calls.
- Campaign auto stopping fixed
- All callees in the queue WILL be handled by agents before the campaign ends.
BC break: New mappings for end_reason implemented to make them more human readable
OLD end_reason NEW end_reason hangup_command agent_hangup hangup callee_hangup - New Notification: agent status offline, when the agent goes offline the status change is confirmed by the dialer (after the agents active call is completed)
- CDR Notification: added callee number to the CDR
All updates for this release
User Story
- DIAL-105RESOLVED As a TFI I want offline agent status notifications at campaign start so that i can ensure my agents are in the correct state
- DIAL-89RESOLVED As an integrator I want the dialed number available in the CDR so that it is easier for third parties to make use of the information
- DAP-7RESOLVED As TF we want an API call to get recordings so that we have an easier integration
Bug
- DIAL-119 RESOLVED Status mappings inaccurate
- DIAL-111 RESOLVED manually stopping campaign causes callees to stay on hold forever
- DIAL-107 RESOLVED Campaign immediately ends
- DAP-8 RESOLVED Map hangup_command to hangup
Backported fixes
- DIAL-145 RESOLVED API Manager Crashes After shutting down call loop
- DIAL-158 RESOLVED Force Enabled CDR Redis notifications for legacy SIP based Integrations
- DAP-41 RESOLVED As TF I want another CDR redis list so that I can add CDR's to the dialer PBX
- DIAL-181 RESOLVED API Crashes were causing campaigns not to start