Summary
BC Break: since this is a major release we used the opportunity to fix some API design issues. When creating a call call_ref was renamed to contact_ref because contact_ref implies its your custom reference, this is one of the few cases where we won't provide backwards support for call_ref.
WebRTC Support added. WebRTC allows integrators to completely bring the call control into their application, stopping agents from misbehaving with desktop softphones and reducing support loads.
It also allows a level of workflow control that previously wasn't possible with standalone softphones. WebRTC is the recommended way to integrate, but by no means will we do away with the Rest API, both will be supported.
In the process of adding WebRTC, key infrastructure components needed to be upgraded. Making Asterisk 13 a minimum requirement for the PBX that C2D is installed on.
This does mean that rolling out Click2Dial v3 from v2 can require coordination with the PBX provider.
Also unfortunately a bug exists in Asterisk 13 ASTERISK-24620 that makes durations on outbound calls placed through the Rest API buggy, and with no good solution. Thus durations on outbound calls placed through the Rest API will be off by 1-2 seconds for the majority to a maximum of 10sec. All other durations are still accurate.
All updates for this release
Features
- WebRTC
- Specifying X-Platforma-Outbound-ID and X-Platforma-Contact-Ref for a call will work the same way as if it were specified in a Rest API call.
Bugfixes
- BC Break: Call: when creating a call call_ref was renamed to contact_ref
Limitations
- No custom headers are passed back for inbound calls in this release.
- Rest API Outbound calls duration is inaccurate by 1-2 sec to a maximum of 10 sec due to an infrastructure bug that is currently unfixable.
Recommended Changes
- Update call_ref to contact_ref on call create.
- Using a built in WebRTC phone in a web application allows far more flexibility than ever possible with a desktop client softphone.