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

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.

Context: 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.

Matched source

Source: Published skill Original query: "Plivo web SDK has no call UUID: read it from the Dial callback" Key terms: call, callback, dial, plivo, read, uuid

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