Twilio Reporting "487 Request Terminated" When cal...
# support
o
I have code in Twilio that routes calls to Vapi depending on the number that's calling. Once the logic is executed within Twilio, if the call is supposed to go to Vapi, it forwards it to my Vapi number. This has worked fine for months, but in the past 2 weeks, every call has failed. The logic works fine in Twilio, but when it forwards the call to Vapi, all the calls result in a SIP response of "487 Request Terminated" according to my Twilio dashboard. How do I fix this?
k
To help track down this issue, could you share one or two: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
n
@openvault A
SIP 487 Request Terminated
error is reported when to originating side decides to abandon the call (
SIP CANCEL
). I suggest that you examine your Twilio callflow and make sure that the time required to call VAPI is long enough, for the VAPI side to fully answer the call.
s
@openvault Just checking if you were able to resolve this on your end.
2 Views