"SIP" traffic refers to the signalling used to control multimedia communication sessions in applications of Internet telephony for voice and video calls. The most common reason you will see a SIP error is there is a network connection issue with your internet.
Please follow the troubleshooting steps here before contacting Jet Support.
If you follow the steps above and are still seeing a SIP error, please search the table below for the SIP error code you are seeing.
Some error codes may have specific additional troubleshooting steps in red.
Please follow these before contacting Support.
1xx—Provisional Responses
For all 1xx error codes, please wait for the request to either complete or timeout and a new error code to display.
2xx—Successful Responses
No action is needed for any 2xx codes.
3xx—Redirection Responses
For all 3xx error codes, contact Jet Support.
4xx—Client Failure Responses
Most 4xx error codes are generated from the client device side (ie you). The most common issue here would be a network connection error, which you can read more about here.
The full list of error codes is below, however, if you see any 4xx error codes, please check or change your network connection (ie: use 4G instead of wifi) and try again before contacting Jet Support.
| CODE | REASON | DESCRIPTION | HOW TO RESOLVE |
|---|---|---|---|
| 400 | Bad Request | The request could not be understood due to malformed syntax | Please check the number you are dialling and try again. |
| 401 | Unauthorized |
The request requires user authentication. |
Check your login details and try again. |
| 402 | Payment Required | Unauthorised. | Check your payment method is up to date and try again later. |
| 403 | Forbidden | The server understood the request, but is refusing to fulfill it. Sometimes (but not always) this means the call has been rejected by the receiver. | Try again later |
| 404 | Not Found |
The request could not find a response on the other side. |
Please check the number you are dialling and try again. |
| 405 | Method Not Allowed | The method specified in the Request-Line is understood, but not allowed for the address identified by the Request-URI. | |
| 406 | Not Acceptable | The resource identified by the request is only capable of generating response entities that have content characteristics but not acceptable according to the fields sent in the request. | Check your details are correct in the Phone User page in Jet Hub. If they are, contact Jet Support. |
| 407 | Proxy Authentication Required | The request requires user authentication. | |
| 408 | Request Timeout |
Couldn't find the user in time. The server could not produce a response within a suitable amount of time, for example, if it could not determine the location of the user in time. The client may repeat the request without modifications at any later time. |
This is most commonly a Network error. Please check or change your network connection and try again. Note - this is most commonly seen on wifi networks. |
| 409 | Conflict |
User already registered. |
Log out of any other devices that may be using your credentials. |
| 410 | Gone |
The user existed once, but is not available here any more.
|
Check your details are correct in the Phone User page in Jet Hub. If they are, contact Jet Support. |
| 411 | Length Required | The server will not accept the request without a valid Content-Length. | |
| 412 | Conditional Request Failed | The given precondition has not been met. | Contact Jet Support. |
| 413 | Request Entity Too Large |
Request body too large. |
If you receive these errors when sending an SMS, try breaking the message into smaller pieces and sending as multiple messages. |
| 414 | Request-URI Too Large | The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. | |
| 415 | Unsupported Media Type | Request body in a format not supported. | Remove all media sources from your request (ie: links, images). |
| 416 | Unsupported URI Scheme | Request-URI is unknown to the server. | Contact Jet Support. |
| 417 | Unknown Resource-Priority | There was a resource-priority option tag, but no Resource-Priority header. | |
| 418 | Not Allowed | Login error, request refused. |
You are using an old version of our application and this is no longer supported. Please upgrade the version of the application you are using. Up-to-date versions can be found on our Downloads page. View system requirements here. |
| 420 | Bad Extension | Bad SIP Protocol Extension used, not understood by the server. | Contact Jet Support. |
| 421 | Extension Required | The server needs a specific extension not listed in the Supported header. | Check your details are correct in the Phone User page in Jet Hub. If they are, contact Jet Support. |
| 422 | Session Interval Too Small | The received request contains a Session-Expires header field with a duration below the minimum timer. | Contact Jet Support. |
| 423 | Interval Too Brief | Expiration time of the resource is too short. | |
| 424 | Bad Location Information | The request's location content was malformed or otherwise unsatisfactory. | |
| 428 | Use Identity Header | The server policy requires an Identity header, and one has not been provided. | |
| 429 | Provide Referrer Identity | The server did not receive a valid Referred-By token on the request. | |
| 430 | Flow Failed | A specific flow to a user agent has failed, although other flows may succeed. This response should be treated as a 400 Bad Request response. | |
| 433 | Anonymity Disallowed | The request has been rejected because it was anonymous. | |
| 436 | Bad Identity-Info | The request has an Identity-Info header, and the URI scheme in that header cannot be dereferenced. | |
| 437 | Unsupported Certificate | The server was unable to validate a certificate for the domain that signed the request. |
You are using an old version of our application and this is no longer supported. Please upgrade the version of the application you are using. Up-to-date versions can be found on our Downloads page. View system requirements here. |
| 438 | Invalid Identity Header | The server obtained a valid certificate that the request claimed was used to sign the request, but was unable to verify that signature. | Contact Jet Support. |
| 439 | First Hop Lacks Outbound Support | The first outbound proxy the user is attempting to register through does not support the necessary "outbound" feature, although the registrar does. | |
| 440 | Max-Breadth Exceeded | The request had insufficient Incoming Max-Breadth to carry out a desired parallel fork, and no fork or redirect was sent. The request did not reach all possible destinations. | |
| 469 | Bad Info Package | The UA has not indicated willingness to receive the INFO requests. | |
| 470 | Consent Needed | The source of the request did not have the permission of the recipient to make such a request. | |
| 480 | Temporarily Unavailable | Callee currently unavailable. | Please try your call at a later time. |
| 481 | Call/Transaction Does Not Exist | Server received a request that does not match any dialog or transaction. | Contact Jet Support. |
| 482 | Loop Detected | Server received a request that does not match any dialog or transaction. | |
| 483 | Too Many Hops | Max-Forwards header has reached the value '0'. | |
| 484 | Address Incomplete | Request-URI incomplete. | |
| 485 | Ambiguous | Request-URI is ambiguous. | |
| 486 | Busy Here | Callee is busy. | Try again later. |
| 487 | Request Terminated | Request has terminated by bye or cancel. | This call has ended from the callee's side. |
| 488 | Not Acceptable Here | Some aspect of the session description or the Request-URI is not acceptable. |
Try again later. If the issue persists, contact Jet Support. |
| 489 | Bad Event | The server did not understand an event package specified in an Event header field. | |
| 491 | Request Pending |
Please wait for the request to complete or timeout. |
|
| 493 | Undecipherable | Request contains an encrypted MIME body, which the recipient can not decrypt. | |
| 494 | Security Agreement Required | The server has received a request that requires a negotiated security mechanism. | This device is not supported. |
5xx—Server Failure Responses
Most 4xx error codes are generated from the client's network side (ie your network/internet connection). The most common issue here would be a network connection error, which you can read more about here.
| CODE | REASON | DESCRIPTION | HOW TO FIX |
|---|---|---|---|
| 500 | Internal Server Error | The server could not fulfill the request due to some unexpected condition. |
This is most commonly a Network error. Please check or change your network connection and try again. |
| 501 | Not Implemented | The server does not have the ability to fulfill the request, such as because it does not recognize the request method. (Compare with 405 Method Not Allowed, where the server recognizes the method but does not allow or support it.) | |
| 502 | Bad Gateway |
The server is acting as a gateway or proxy, and received an invalid response from a downstream server while attempting to fulfill the request. |
|
| 503 | Service Unavailable | The server is undergoing maintenance or is temporarily overloaded and so cannot process the request. A "Retry-After" header field may specify when the client may reattempt its request. | |
| 504 | Server Time-out |
The server attempted to access another server in attempting to process the request and did not receive a prompt response. |
Contact Jet Support. |
| 505 | Version Not Supported | The SIP protocol version in the request is not supported by the server. |
Check you are running the latest version of the Jet Soft Phone app. Download from HERE or view the Jet App System Requirements & Compatibility |
| 513 | Message Too Large | The request message length is longer than the server can process. | If you receive these errors when sending an SMS, try breaking the message into smaller pieces and sending as multiple messages. |
| 555 | Push Notification Service Not Supported | The server does not support the push notification service identified in a 'pn-provider' SIP URI parameter. | This is most commonly a Network error. Please check or change your network connection and try again. |
| 580 | Precondition Failure | The server is unable or unwilling to meet some constraints specified in the offer. |
6xx—Global Failure Responses
For all 6xx responses, please contact Jet Support.
| CODE | REASON | DESCRIPTION | HOW TO RESOLVE |
|---|---|---|---|
| 600 | Busy Everywhere | All possible destinations are busy. There are no alternative destinations (such as a voicemail server) able to accept the call. | Please check the number you are dialling and try again. |
| 603 | Decline | The destination does not wish to participate in the call, or cannot do so, and additionally the destination knows there are no alternative destinations willing to accept the call. | Contact the called party to resolve, this is usually a system offline on their end. |
| 604 | Does Not Exist Anywhere | The server has authoritative information that the requested user does not exist anywhere. | Check the number you are trying to contact and try again. |
| 606 | Not Acceptable | The user's agent was contacted successfully but some aspects of the session description such as the requested media, bandwidth, or addressing style were not acceptable | Contact the called party to resolve, this is usually a system offline on their end. |
| 607 | Unwanted | The called party did not want this call from the calling party. Future attempts from the calling party are likely to be similarly rejected. | Contact the called party to resolve, this is usually a system rejection on their end. |
| 608 | Rejected | An intermediary machine or process rejected the call attempt. |