Updates to Call Control Webhooks

We're always working to make your experience better. Part of this work involves unifying your developer experience between our Elastic SIP Trunking and Call Control products.

As part of this unification, we're making a change to webhooks associated with calls that use our Voice API, Call Control.

What is changing?

Webhooks associated with calls that use Call Control contain a call_control_id field, which associates a unique identifier with the call and its corresponding API activity. They also contain a call_leg_id field, which associates a separate unique identifier with the call and its SIP activity.

This call_control_id field currently takes the form "call_control_id": "v2:ujuK_2BDm1w5jJLz--bMGbZ-TuMfo86BmKCDk0KllxoYLrxh1HGf3g".

After this change takes effect, the call_control_id field will contain the same data as the call_leg_id field in any given webhook, and will take this form:

"call_control_id": "d14dbcee-880b-11eb-8204-02420a0f7568".

How can I ensure my communications are unaffected by this change?

If your Voice API application parses the call_control_id field from Call Control webhooks, you may need to update your application to accommodate the new format of data contained in this field.

When is this change happening?

This change is being rolled out in phases. If your account is set to be part of a migration phase, you'll receive a notification from your account manager, or at the email address associated with your account.

Who can I contact for more information?

As always — our technical team is available 24/7 via live chat in our Portal, or Slack if you have any questions.