34002: Callee Busy
API
ERROR
Twilio received a busy indication from the destination when attempting to complete a voice call. The called party was already on another call or the destination network reported the callee as unavailable because the line was busy.
- The destination phone number is currently in use
- The destination carrier returned a busy response for the call attempt
- The called device or PBX rejected the call with a busy status
- Call forwarding or downstream routing sent the call to a busy endpoint
- Retry the call later when the destination is available
- Confirm that you are dialing the correct phone number in valid
E.164format - Review your call logs and call status to verify that the call ended with a busy result
- If you call a SIP endpoint or PBX, verify that the destination is registered, reachable, and not configured to reject calls as busy
- If the issue happens repeatedly for the same destination, contact the destination carrier or system administrator to confirm the line status and call routing