Dialer Release v1.6
- Rijnhard Hessel
Owned by Rijnhard Hessel
Summary
Call Blending has been implemented, with the major case importance being that the integrator needs to handle a Call Connection notification with a null contact_ref.
All updates for this release
Bugs
- DIAL-158 RESOLVED Force Enabled CDR Redis notifications for legacy SIP based Integrations
Features
DIAL-147 RESOLVED CDR Notification: added dial_number entry to see the number that was used by the dialer
- Outbound: the outbound_call_id that was used on an outbound call from the dialer
- Inbound: the (DID) number that was dialed by the caller
- DIAL-70 RESOLVED Blended Call Support:
- Blending is forced to always on, unless otherwise configured in the PBX
- CDR and Call Connection Notification:
- will send inbound for call_dir on inbound calls
- will send null for contact_ref as there no reference for inbound callers on a number
- Campaigns can accept incoming calls by transferring to the dialer by either:
dialing the SIP address of the number the dialer is using for outbound_call_id:
#SIP/dialer/<outbound_call_id> SIP/dialer/0120001234
dialing the SIP address of the campaign_ref of the running campaign
#SIP/dialer/<campaign_ref> SIP/dialer/my_campaign_0001
- DAP-41 RESOLVED As TF I want another CDR redis list so that I can add CDR's to the dialer PBX
Recommended Changes
- Handle null contact_ref for inbound calls
- Educate clients about how to configure the PBX to send calls to running campaigns.
Maintenance
- New internal API in the Dialer Core
Backported fixes
- DIAL-181 RESOLVED API Crashes were causing campaigns not to start
- DIAL-188 RESOLVED RecordingMonitor is crashing when a file doesn't exist
- DAP-49 RESOLVED recording file does not include extension
- DIAL-212 RESOLVED Backport upgrade to Electric Slide for v1.6