Twilio Invalid 'StatusCallbackEvent' Error - 21626
up vote
0
down vote
favorite
One or more of the StatusCallbackEvents provided were invalid.
invalidStatusCallbackEvents "canceled no-answer busy failed"
I removed those 4 events from above since they do not seem to ever be valid according to:
- https://support.twilio.com/hc/en-us/articles/223132267-Tracking-the-call-status-of-an-outbound-call
- the invalid callback events are actually finalized call statuses: https://support.twilio.com/hc/en-us/articles/223132547-What-are-the-Possible-Call-Statuses-and-What-do-They-Mean-
Is this the correct way to fix the issue? Or are those 4 StatusCallbackEvents valid under some context?
twilio
asked Nov 22 at 12:48
Răzvan Flavius Panda
16k1285136
add a comment |
up vote
0
down vote
favorite
One or more of the StatusCallbackEvents provided were invalid.
invalidStatusCallbackEvents "canceled no-answer busy failed"
I removed those 4 events from above since they do not seem to ever be valid according to:
- https://support.twilio.com/hc/en-us/articles/223132267-Tracking-the-call-status-of-an-outbound-call
- the invalid callback events are actually finalized call statuses: https://support.twilio.com/hc/en-us/articles/223132547-What-are-the-Possible-Call-Statuses-and-What-do-They-Mean-
Is this the correct way to fix the issue? Or are those 4 StatusCallbackEvents valid under some context?
twilio
asked Nov 22 at 12:48
Răzvan Flavius Panda
16k1285136
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
One or more of the StatusCallbackEvents provided were invalid.
invalidStatusCallbackEvents "canceled no-answer busy failed"
I removed those 4 events from above since they do not seem to ever be valid according to:
- https://support.twilio.com/hc/en-us/articles/223132267-Tracking-the-call-status-of-an-outbound-call
- the invalid callback events are actually finalized call statuses: https://support.twilio.com/hc/en-us/articles/223132547-What-are-the-Possible-Call-Statuses-and-What-do-They-Mean-
Is this the correct way to fix the issue? Or are those 4 StatusCallbackEvents valid under some context?
twilio
asked Nov 22 at 12:48
Răzvan Flavius Panda
16k1285136
One or more of the StatusCallbackEvents provided were invalid.
invalidStatusCallbackEvents "canceled no-answer busy failed"
I removed those 4 events from above since they do not seem to ever be valid according to:
- https://support.twilio.com/hc/en-us/articles/223132267-Tracking-the-call-status-of-an-outbound-call
- the invalid callback events are actually finalized call statuses: https://support.twilio.com/hc/en-us/articles/223132547-What-are-the-Possible-Call-Statuses-and-What-do-They-Mean-
Is this the correct way to fix the issue? Or are those 4 StatusCallbackEvents valid under some context?
twilio
twilio
asked Nov 22 at 12:48
Răzvan Flavius Panda
16k1285136
asked Nov 22 at 12:48
Răzvan Flavius Panda
16k1285136
asked Nov 22 at 12:48
Răzvan Flavius Panda
16k1285136
asked Nov 22 at 12:48
Răzvan Flavius Panda
16k1285136
asked Nov 22 at 12:48
Răzvan Flavius Panda
16k1285136
16k1285136
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Twilio developer evangelist here.
You're correct, none of those are events, they are statuses. In fact, they are all statuses that could be sent as part of the "completed" event.
The call events you can register for callbacks for are: initiated, ringing, answered and completed.
answered Nov 23 at 4:47
philnash
36.6k93353
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Twilio developer evangelist here.
You're correct, none of those are events, they are statuses. In fact, they are all statuses that could be sent as part of the "completed" event.
The call events you can register for callbacks for are: initiated, ringing, answered and completed.
answered Nov 23 at 4:47
philnash
36.6k93353
add a comment |
up vote
1
down vote
accepted
Twilio developer evangelist here.
You're correct, none of those are events, they are statuses. In fact, they are all statuses that could be sent as part of the "completed" event.
The call events you can register for callbacks for are: initiated, ringing, answered and completed.
answered Nov 23 at 4:47
philnash
36.6k93353
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Twilio developer evangelist here.
You're correct, none of those are events, they are statuses. In fact, they are all statuses that could be sent as part of the "completed" event.
The call events you can register for callbacks for are: initiated, ringing, answered and completed.
answered Nov 23 at 4:47
philnash
36.6k93353
Twilio developer evangelist here.
You're correct, none of those are events, they are statuses. In fact, they are all statuses that could be sent as part of the "completed" event.
The call events you can register for callbacks for are: initiated, ringing, answered and completed.
answered Nov 23 at 4:47
philnash
36.6k93353
answered Nov 23 at 4:47
philnash
36.6k93353
answered Nov 23 at 4:47
philnash
36.6k93353
answered Nov 23 at 4:47
philnash
36.6k93353
36.6k93353
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53431399%2ftwilio-invalid-statuscallbackevent-error-21626%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
