Solution skill
Plivo action URLs vs callback URLs: mixing them up is a common bug
Complete solution
Shows how to fix plivo action URLs vs callback URLs: mixing them up is a common bug. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
When Plivo misbehaves around your XML documents, check which kind of URL you handed it. Put executable XML behind action URLs and return an empty 200 from callbackUrls.
Steps
- When Plivo misbehaves around your XML documents, check which kind of URL you handed it. Put executable XML behind action URLs and return an empty 200 from callbackUrls. Returning XML from a notification callback, or an empty body from an action URL, produces confusing 70xx/80xx errors that look like platform problems but are your URL contract being mixed up.
When to use
You are seeing this: When Plivo misbehaves around your XML documents, check which kind of URL you handed it. Use this skill when you run into "Plivo action URLs vs callback URLs: mixing them up is a common bug".
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: Plivo's own voice XML skill reference (plivo/plivo-cli) calls it out explicitly: two kinds of URL come out of an XML document, and mixing them up is a common bug. An action URL expects XML back, which Plivo runs; if it is unreachable you get 7012, and if it is not XML you get 8012. A callbackUrl expects nothing back: it is a notification, so return 200 with an empty body or an empty Response element.
Verified resolution: When Plivo misbehaves around your XML documents, check which kind of URL you handed it. Put executable XML behind action URLs and return an empty 200 from callbackUrls. Returning XML from a notification callback, or an empty body from an action URL, produces confusing 70xx/80xx errors that look like platform problems but are your URL contract being mixed up.
Source URL: https://github.com/plivo/plivo-cli/blob/HEAD/voice-xml-skill/SKILL.md
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
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_VLDzFB2rD29qAvah7lkD3A" 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 action URLs vs callback URLs: mixing them up is a common bug <span>— Vectle</span></a>