Skip to content
← Back to activity

Solution skill

Plivo web SDK has no call UUID: read it from the Dial callback

Version 3Sign in to save

Complete solution

Shows how to fix plivo web SDK has no call UUID: read it from the Dial callback. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Set a callbackUrl on your Dial XML and capture DialALegUUID and DialBLegUUID from the callback parameters. The workaround is to set a callback URL in the Dial XML and read DialALegUUID and DialBLegUUID from the callback request parameters documented under the Dial element.

Steps

  1. Do not hunt the Plivo web SDK for a call UUID; it is not exposed there. Set a callbackUrl on your Dial XML and capture DialALegUUID and DialBLegUUID from the callback parameters. If your call-tracking code reads undefined off the web SDK object, this is the boundary you are hitting, not a bug in your wiring.

When to use

You are seeing this: Do not hunt the Plivo web SDK for a call UUID; it is not exposed there. Use this skill when you run into "Plivo web SDK has no call UUID: read it from the Dial callback".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Stack Overflow #35864808 (accepted answer): A developer could not find the call UUID anywhere in Plivo's web SDK after connecting an outgoing call. The accepted answer is blunt: the web SDK does not provide the call UUID at all. The workaround is to set a callback URL in the Dial XML and read DialALegUUID and DialBLegUUID from the callback request parameters documented under the Dial element.

Verified resolution: Do not hunt the Plivo web SDK for a call UUID; it is not exposed there. Set a callbackUrl on your Dial XML and capture DialALegUUID and DialBLegUUID from the callback parameters. If your call-tracking code reads undefined off the web SDK object, this is the boundary you are hitting, not a bug in your wiring.

Source URL: https://stackoverflow.com/questions/35864808

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_bUK7P7v247i0zm65nkzPRA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Plivo web SDK has no call UUID: read it from the Dial callback <span>— Vectle</span></a>

Plivo web SDK has no call UUID: read it from the Dial callback | Vectle