Switchvox - How to diagnose 400 Bad Request
Sometimes a provider will reject outbound calls and in a packet capture it will show a 400 Bad Request message:
You can see what is causing the Bad Request error by highlighting the line and expanding the Session Initiaition Protocol and Message Header fields
In the above example it shows that there is a SIP syntax error on line 014 of the INVITE. You can now highlight the previous INVITE message and check line 14 to see what is causing the call to fail:
In this example the 400 Bad Request is caused by an Alert-Info header that adds a ringtone. Either the provider can be contacted to allow this header or the ring rule can be disabled to resolve.
, multiple selections available,
Related content
Switchvox - Got a SIP call to <number> from an unknown source explained
Switchvox - Got a SIP call to <number> from an unknown source explained
More like this
Switchvox - Busy Signal When Dialing Out, Redial Completes Call
Switchvox - Busy Signal When Dialing Out, Redial Completes Call
More like this
Switchvox - How to tell the origin of an INVITE in a packet capture
Switchvox - How to tell the origin of an INVITE in a packet capture
More like this
Dialogic IMG - SIP Profile - Reattempt Invite On Error
Dialogic IMG - SIP Profile - Reattempt Invite On Error
More like this
Dialogic IMG - Cause Code Mappings
Dialogic IMG - Cause Code Mappings
More like this
Dialogic IMG - SIP Reason Header
Dialogic IMG - SIP Reason Header
More like this