601 ошибка http

You need to setup the connection to the bearer. Here are the minimum setup commands that have worked for me (based on trial/error and searching around on the internet).

AT+SAPBR=3,1,"APN","wap.cingular"
AT+SAPBR=1,1

The correct value for the APN may be different for you, depending on your network and service provider. I’m using AT&T prepaid SIM cards. Once that’s working, then you can do the HTTP setup commands as you already have…

AT+HTTPINIT
AT+HTTPPARA="URL","http://www.google.com"
AT+HTTPACTION=0

Status codes above 600 (and some in the 500 range) are unassigned in the HTTP standard. In the AT command manual for the SIM908, status meanings are given in the notes on the HTTPACTION command:

600 Not HTTP PDU
601 Network Error
602 No memory
603 DNS Error
604 Stack Busy

You can query the bearer connection status of CID 1 with AT+SAPBR=2,1 and the related parameters with AT+SAPBR=4,1. You can also check that you’re attached to the GPRS network with AT+CGATT?. If everything indicates that you are connected and you are still getting a 601 status code, then check that your service plan has data and that it hasn’t run out. I have found that even when my account has a few hundred k of data showing on the balance that I start to get a 601 status until I add more data to my prepaid phone plan. If the SIM module has been on the whole time and you add more data, you’ll need to close and re-open your connection (AT+SAPBR=0,1 followed by AT+SAPBR=1,1) and then your HTTP* commands will start working again without having to set the HTTPPARA settings again and without having to restart with HTTPINIT.

Источник

Page semi-protected

From Wikipedia, the free encyclopedia

This is a list of Hypertext Transfer Protocol (HTTP) response status codes. Status codes are issued by a server in response to a client’s request made to the server. It includes codes from IETF Request for Comments (RFCs), other specifications, and some additional codes used in some common applications of the HTTP. The first digit of the status code specifies one of five standard classes of responses. The optional message phrases shown are typical, but any human-readable alternative may be provided, or none at all.

Unless otherwise stated, the status code is part of the HTTP standard (RFC 9110).

The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.[1]

All HTTP response status codes are separated into five classes or categories. The first digit of the status code defines the class of response, while the last two digits do not have any classifying or categorization role. There are five classes defined by the standard:

  • 1xx informational response – the request was received, continuing process
  • 2xx successful – the request was successfully received, understood, and accepted
  • 3xx redirection – further action needs to be taken in order to complete the request
  • 4xx client error – the request contains bad syntax or cannot be fulfilled
  • 5xx server error – the server failed to fulfil an apparently valid request

1xx informational response

An informational response indicates that the request was received and understood. It is issued on a provisional basis while request processing continues. It alerts the client to wait for a final response. The message consists only of the status line and optional header fields, and is terminated by an empty line. As the HTTP/1.0 standard did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 compliant client except under experimental conditions.

100 Continue
The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request’s headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in response before sending the body. If the client receives an error code such as 403 (Forbidden) or 405 (Method Not Allowed) then it should not send the request’s body. The response 417 Expectation Failed indicates that the request should be repeated without the Expect header as it indicates that the server does not support expectations (this is the case, for example, of HTTP/1.0 servers).[2]
101 Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
102 Processing (WebDAV; RFC 2518)
A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet.[3] This prevents the client from timing out and assuming the request was lost.
103 Early Hints (RFC 8297)
Used to return some response headers before final HTTP message.[4]

2xx success

This class of status codes indicates the action requested by the client was received, understood, and accepted.[1]

200 OK
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.
201 Created
The request has been fulfilled, resulting in the creation of a new resource.[5]
202 Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.
203 Non-Authoritative Information (since HTTP/1.1)
The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin’s response.[6][7]
204 No Content
The server successfully processed the request, and is not returning any content.
205 Reset Content
The server successfully processed the request, asks that the requester reset its document view, and is not returning any content.
206 Partial Content
The server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
207 Multi-Status (WebDAV; RFC 4918)
The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.[8]
208 Already Reported (WebDAV; RFC 5842)
The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.
226 IM Used (RFC 3229)
The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.[9]

3xx redirection

This class of status code indicates the client must take additional action to complete the request. Many of these status codes are used in URL redirection.[1]

A user agent may carry out the additional action with no user interaction only if the method used in the second request is GET or HEAD. A user agent may automatically redirect a request. A user agent should detect and intervene to prevent cyclical redirects.[10]

300 Multiple Choices
Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation). For example, this code could be used to present multiple video format options, to list files with different filename extensions, or to suggest word-sense disambiguation.
301 Moved Permanently
This and all future requests should be directed to the given URI.
302 Found (Previously «Moved temporarily»)
Tells the client to look at (browse to) another URL. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect with the same method (the original describing phrase was «Moved Temporarily»),[11] but popular browsers implemented 302 redirects by changing the method to GET. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours.[10]
303 See Other (since HTTP/1.1)
The response to the request can be found under another URI using the GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a new GET request to the given URI.
304 Not Modified
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.
305 Use Proxy (since HTTP/1.1)
The requested resource is available only through a proxy, the address for which is provided in the response. For security reasons, many HTTP clients (such as Mozilla Firefox and Internet Explorer) do not obey this status code.
306 Switch Proxy
No longer used. Originally meant «Subsequent requests should use the specified proxy.»
307 Temporary Redirect (since HTTP/1.1)
In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, a POST request should be repeated using another POST request.
308 Permanent Redirect
This and all future requests should be directed to the given URI. 308 parallel the behaviour of 301, but does not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly.

4xx client errors

A The Wikimedia 404 message

This class of status code is intended for situations in which the error seems to have been caused by the client. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user.

400 Bad Request
The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).
401 Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication. 401 semantically means «unauthorised», the user does not have valid authentication credentials for the target resource.
Some sites incorrectly issue HTTP 401 when an IP address is banned from the website (usually the website domain) and that specific address is refused permission to access a website.[citation needed]
402 Payment Required
Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, as proposed, for example, by GNU Taler,[13] but that has not yet happened, and this code is not widely used. Google Developers API uses this status if a particular developer has exceeded the daily limit on requests.[14] Sipgate uses this code if an account does not have sufficient funds to start a call.[15] Shopify uses this code when the store has not paid their fees and is temporarily disabled.[16] Stripe uses this code for failed payments where parameters were correct, for example blocked fraudulent payments.[17]
403 Forbidden
The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action (e.g. creating a duplicate record where only one is allowed). This code is also typically used if the request provided authentication by answering the WWW-Authenticate header field challenge, but the server did not accept that authentication. The request should not be repeated.
404 Not Found
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
405 Method Not Allowed
A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource.
406 Not Acceptable
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. See Content negotiation.
407 Proxy Authentication Required
The client must first authenticate itself with the proxy.
408 Request Timeout
The server timed out waiting for the request. According to HTTP specifications: «The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.»
409 Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource, such as an edit conflict between multiple simultaneous updates.
410 Gone
Indicates that the resource requested was previously in use but is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a «404 Not Found» may be used instead.
411 Length Required
The request did not specify the length of its content, which is required by the requested resource.
412 Precondition Failed
The server does not meet one of the preconditions that the requester put on the request header fields.
413 Payload Too Large
The request is larger than the server is willing or able to process. Previously called «Request Entity Too Large» in RFC 2616.[18]
414 URI Too Long
The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. Called «Request-URI Too Long» previously in RFC 2616.[19]
415 Unsupported Media Type
The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.
416 Range Not Satisfiable
The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. Called «Requested Range Not Satisfiable» previously RFC 2616.[20]
417 Expectation Failed
The server cannot meet the requirements of the Expect request-header field.[21]
418 I’m a teapot (RFC 2324, RFC 7168)
This code was defined in 1998 as one of the traditional IETF April Fools’ jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee.[22] This HTTP status is used as an Easter egg in some websites, such as Google.com’s «I’m a teapot» easter egg.[23][24][25] Sometimes, this status code is also used as a response to a blocked request, instead of the more appropriate 403 Forbidden.[26][27]
421 Misdirected Request
The request was directed at a server that is not able to produce a response (for example because of connection reuse).
422 Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.[8]
423 Locked (WebDAV; RFC 4918)
The resource that is being accessed is locked.[8]
424 Failed Dependency (WebDAV; RFC 4918)
The request failed because it depended on another request and that request failed (e.g., a PROPPATCH).[8]
425 Too Early (RFC 8470)
Indicates that the server is unwilling to risk processing a request that might be replayed.
426 Upgrade Required
The client should switch to a different protocol such as TLS/1.3, given in the Upgrade header field.
428 Precondition Required (RFC 6585)
The origin server requires the request to be conditional. Intended to prevent the ‘lost update’ problem, where a client GETs a resource’s state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.[28]
429 Too Many Requests (RFC 6585)
The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.[28]
431 Request Header Fields Too Large (RFC 6585)
The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.[28]
451 Unavailable For Legal Reasons (RFC 7725)
A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.[29] The code 451 was chosen as a reference to the novel Fahrenheit 451 (see the Acknowledgements in the RFC).

5xx server errors

The server failed to fulfil a request.

Response status codes beginning with the digit «5» indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.

500 Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
501 Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-service API).
502 Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503 Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.[30]
504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505 HTTP Version Not Supported
The server does not support the HTTP version used in the request.
506 Variant Also Negotiates (RFC 2295)
Transparent content negotiation for the request results in a circular reference.[31]
507 Insufficient Storage (WebDAV; RFC 4918)
The server is unable to store the representation needed to complete the request.[8]
508 Loop Detected (WebDAV; RFC 5842)
The server detected an infinite loop while processing the request (sent instead of 208 Already Reported).
510 Not Extended (RFC 2774)
Further extensions to the request are required for the server to fulfil it.[32]
511 Network Authentication Required (RFC 6585)
The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., «captive portals» used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).[28]

Unofficial codes

The following codes are not specified by any standard.

419 Page Expired (Laravel Framework)
Used by the Laravel Framework when a CSRF Token is missing or expired.
420 Method Failure (Spring Framework)
A deprecated response used by the Spring Framework when a method has failed.[33]
420 Enhance Your Calm (Twitter)
Returned by version 1 of the Twitter Search and Trends API when the client is being rate limited; versions 1.1 and later use the 429 Too Many Requests response code instead.[34] The phrase «Enhance your calm» comes from the 1993 movie Demolition Man, and its association with this number is likely a reference to cannabis.[citation needed]
430 Request Header Fields Too Large (Shopify)
Used by Shopify, instead of the 429 Too Many Requests response code, when too many URLs are requested within a certain time frame.[35]
450 Blocked by Windows Parental Controls (Microsoft)
The Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the requested webpage.[36]
498 Invalid Token (Esri)
Returned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token.[37]
499 Token Required (Esri)
Returned by ArcGIS for Server. Code 499 indicates that a token is required but was not submitted.[37]
509 Bandwidth Limit Exceeded (Apache Web Server/cPanel)
The server has exceeded the bandwidth specified by the server administrator; this is often used by shared hosting providers to limit the bandwidth of customers.[38]
529 Site is overloaded
Used by Qualys in the SSLLabs server testing API to signal that the site can’t process the request.[39]
530 Site is frozen
Used by the Pantheon Systems web platform to indicate a site that has been frozen due to inactivity.[40]
598 (Informal convention) Network read timeout error
Used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.[41]
599 Network Connect Timeout Error
An error used by some HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy.

Internet Information Services

Microsoft’s Internet Information Services (IIS) web server expands the 4xx error space to signal errors with the client’s request.

440 Login Time-out
The client’s session has expired and must log in again.[42]
449 Retry With
The server cannot honour the request because the user has not provided the required information.[43]
451 Redirect
Used in Exchange ActiveSync when either a more efficient server is available or the server cannot access the users’ mailbox.[44] The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server.[45]

IIS sometimes uses additional decimal sub-codes for more specific information,[46] however these sub-codes only appear in the response payload and in documentation, not in the place of an actual HTTP status code.

nginx

The nginx web server software expands the 4xx error space to signal issues with the client’s request.[47][48]

444 No Response
Used internally[49] to instruct the server to return no information to the client and close the connection immediately.
494 Request header too large
Client sent too large request or too long header line.
495 SSL Certificate Error
An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate.
496 SSL Certificate Required
An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided.
497 HTTP Request Sent to HTTPS Port
An expansion of the 400 Bad Request response code, used when the client has made a HTTP request to a port listening for HTTPS requests.
499 Client Closed Request
Used when the client has closed the request before the server could send a response.

Cloudflare

Cloudflare’s reverse proxy service expands the 5xx series of errors space to signal issues with the origin server.[50]

520 Web Server Returned an Unknown Error
The origin server returned an empty, unknown, or unexpected response to Cloudflare.[51]
521 Web Server Is Down
The origin server refused connections from Cloudflare. Security solutions at the origin may be blocking legitimate connections from certain Cloudflare IP addresses.
522 Connection Timed Out
Cloudflare timed out contacting the origin server.
523 Origin Is Unreachable
Cloudflare could not reach the origin server; for example, if the DNS records for the origin server are incorrect or missing.
524 A Timeout Occurred
Cloudflare was able to complete a TCP connection to the origin server, but did not receive a timely HTTP response.
525 SSL Handshake Failed
Cloudflare could not negotiate a SSL/TLS handshake with the origin server.
526 Invalid SSL Certificate
Cloudflare could not validate the SSL certificate on the origin web server. Also used by Cloud Foundry’s gorouter.
527 Railgun Error
Error 527 indicates an interrupted connection between Cloudflare and the origin server’s Railgun server.[52]
530
Error 530 is returned along with a 1xxx error.[53]

AWS Elastic Load Balancer

Amazon’s Elastic Load Balancing adds a few custom return codes

460
Client closed the connection with the load balancer before the idle timeout period elapsed. Typically when client timeout is sooner than the Elastic Load Balancer’s timeout.[54]
463
The load balancer received an X-Forwarded-For request header with more than 30 IP addresses.[54]
561 Unauthorized
An error around authentication returned by a server registered with a load balancer. You configured a listener rule to authenticate users, but the identity provider (IdP) returned an error code when authenticating the user.[55]

Caching warning codes (obsoleted)

The following caching related warning codes were specified under RFC 7234. Unlike the other status codes above, these were not sent as the response status in the HTTP protocol, but as part of the «Warning» HTTP header.[56][57]

Since this «Warning» header is often neither sent by servers nor acknowledged by clients, this header and its codes were obsoleted by the HTTP Working Group in 2022 with RFC 9111.[58]

110 Response is Stale
The response provided by a cache is stale (the content’s age exceeds a maximum age set by a Cache-Control header or heuristically chosen lifetime).
111 Revalidation Failed
The cache was unable to validate the response, due to an inability to reach the origin server.
112 Disconnected Operation
The cache is intentionally disconnected from the rest of the network.
113 Heuristic Expiration
The cache heuristically chose a freshness lifetime greater than 24 hours and the response’s age is greater than 24 hours.
199 Miscellaneous Warning
Arbitrary, non-specific warning. The warning text may be logged or presented to the user.
214 Transformation Applied
Added by a proxy if it applies any transformation to the representation, such as changing the content encoding, media type or the like.
299 Miscellaneous Persistent Warning
Same as 199, but indicating a persistent warning.

See also

  • Custom error pages
  • List of FTP server return codes
  • List of HTTP header fields
  • List of SMTP server return codes
  • Common Log Format

Explanatory notes

  1. ^ Emphasised words and phrases such as must and should represent interpretation guidelines as given by RFC 2119

References

  1. ^ a b c «Hypertext Transfer Protocol (HTTP) Status Code Registry». Iana.org. Archived from the original on December 11, 2011. Retrieved January 8, 2015.
  2. ^ Fielding, Roy T. «RFC 9110: HTTP Semantics and Content, Section 10.1.1 «Expect»«.
  3. ^ Goland, Yaronn; Whitehead, Jim; Faizi, Asad; Carter, Steve R.; Jensen, Del (February 1999). HTTP Extensions for Distributed Authoring – WEBDAV. IETF. doi:10.17487/RFC2518. RFC 2518. Retrieved October 24, 2009.
  4. ^ Oku, Kazuho (December 2017). An HTTP Status Code for Indicating Hints. IETF. doi:10.17487/RFC8297. RFC 8297. Retrieved December 20, 2017.
  5. ^ Stewart, Mark; djna. «Create request with POST, which response codes 200 or 201 and content». Stack Overflow. Archived from the original on October 11, 2016. Retrieved October 16, 2015.
  6. ^ «RFC 9110: HTTP Semantics and Content, Section 15.3.4».
  7. ^ «RFC 9110: HTTP Semantics and Content, Section 7.7».
  8. ^ a b c d e Dusseault, Lisa, ed. (June 2007). HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV). IETF. doi:10.17487/RFC4918. RFC 4918. Retrieved October 24, 2009.
  9. ^ Delta encoding in HTTP. IETF. January 2002. doi:10.17487/RFC3229. RFC 3229. Retrieved February 25, 2011.
  10. ^ a b «RFC 9110: HTTP Semantics and Content, Section 15.4 «Redirection 3xx»«.
  11. ^ Berners-Lee, Tim; Fielding, Roy T.; Nielsen, Henrik Frystyk (May 1996). Hypertext Transfer Protocol – HTTP/1.0. IETF. doi:10.17487/RFC1945. RFC 1945. Retrieved October 24, 2009.
  12. ^ «The GNU Taler tutorial for PHP Web shop developers 0.4.0». docs.taler.net. Archived from the original on November 8, 2017. Retrieved October 29, 2017.
  13. ^ «Google API Standard Error Responses». 2016. Archived from the original on May 25, 2017. Retrieved June 21, 2017.
  14. ^ «Sipgate API Documentation». Archived from the original on July 10, 2018. Retrieved July 10, 2018.
  15. ^ «Shopify Documentation». Archived from the original on July 25, 2018. Retrieved July 25, 2018.
  16. ^ «Stripe API Reference – Errors». stripe.com. Retrieved October 28, 2019.
  17. ^ «RFC2616 on status 413». Tools.ietf.org. Archived from the original on March 7, 2011. Retrieved November 11, 2015.
  18. ^ «RFC2616 on status 414». Tools.ietf.org. Archived from the original on March 7, 2011. Retrieved November 11, 2015.
  19. ^ «RFC2616 on status 416». Tools.ietf.org. Archived from the original on March 7, 2011. Retrieved November 11, 2015.
  20. ^ TheDeadLike. «HTTP/1.1 Status Codes 400 and 417, cannot choose which». serverFault. Archived from the original on October 10, 2015. Retrieved October 16, 2015.
  21. ^ Larry Masinter (April 1, 1998). Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0). doi:10.17487/RFC2324. RFC 2324. Any attempt to brew coffee with a teapot should result in the error code «418 I’m a teapot». The resulting entity body MAY be short and stout.
  22. ^ I’m a teapot
  23. ^ Barry Schwartz (August 26, 2014). «New Google Easter Egg For SEO Geeks: Server Status 418, I’m A Teapot». Search Engine Land. Archived from the original on November 15, 2015. Retrieved November 4, 2015.
  24. ^ «Google’s Teapot». Retrieved October 23, 2017.[dead link]
  25. ^ «Enable extra web security on a website». DreamHost. Retrieved December 18, 2022.
  26. ^ «I Went to a Russian Website and All I Got Was This Lousy Teapot». PCMag. Retrieved December 18, 2022.
  27. ^ a b c d Nottingham, M.; Fielding, R. (April 2012). «RFC 6585 – Additional HTTP Status Codes». Request for Comments. Internet Engineering Task Force. Archived from the original on May 4, 2012. Retrieved May 1, 2012.
  28. ^ Bray, T. (February 2016). «An HTTP Status Code to Report Legal Obstacles». ietf.org. Archived from the original on March 4, 2016. Retrieved March 7, 2015.
  29. ^ alex. «What is the correct HTTP status code to send when a site is down for maintenance?». Stack Overflow. Archived from the original on October 11, 2016. Retrieved October 16, 2015.
  30. ^ Holtman, Koen; Mutz, Andrew H. (March 1998). Transparent Content Negotiation in HTTP. IETF. doi:10.17487/RFC2295. RFC 2295. Retrieved October 24, 2009.
  31. ^ Nielsen, Henrik Frystyk; Leach, Paul; Lawrence, Scott (February 2000). An HTTP Extension Framework. IETF. doi:10.17487/RFC2774. RFC 2774. Retrieved October 24, 2009.
  32. ^ «Enum HttpStatus». Spring Framework. org.springframework.http. Archived from the original on October 25, 2015. Retrieved October 16, 2015.
  33. ^ «Twitter Error Codes & Responses». Twitter. 2014. Archived from the original on September 27, 2017. Retrieved January 20, 2014.
  34. ^ «HTTP Status Codes and SEO: what you need to know». ContentKing. Retrieved August 9, 2019.
  35. ^ «Screenshot of error page». Archived from the original (bmp) on May 11, 2013. Retrieved October 11, 2009.
  36. ^ a b «Using token-based authentication». ArcGIS Server SOAP SDK. Archived from the original on September 26, 2014. Retrieved September 8, 2014.
  37. ^ «HTTP Error Codes and Quick Fixes». Docs.cpanel.net. Archived from the original on November 23, 2015. Retrieved October 15, 2015.
  38. ^ «SSL Labs API v3 Documentation». github.com.
  39. ^ «Platform Considerations | Pantheon Docs». pantheon.io. Archived from the original on January 6, 2017. Retrieved January 5, 2017.
  40. ^ «HTTP status codes — ascii-code.com». www.ascii-code.com. Archived from the original on January 7, 2017. Retrieved December 23, 2016.
  41. ^
    «Error message when you try to log on to Exchange 2007 by using Outlook Web Access: «440 Login Time-out»«. Microsoft. 2010. Retrieved November 13, 2013.
  42. ^ «2.2.6 449 Retry With Status Code». Microsoft. 2009. Archived from the original on October 5, 2009. Retrieved October 26, 2009.
  43. ^ «MS-ASCMD, Section 3.1.5.2.2». Msdn.microsoft.com. Archived from the original on March 26, 2015. Retrieved January 8, 2015.
  44. ^ «Ms-oxdisco». Msdn.microsoft.com. Archived from the original on July 31, 2014. Retrieved January 8, 2015.
  45. ^ «The HTTP status codes in IIS 7.0». Microsoft. July 14, 2009. Archived from the original on April 9, 2009. Retrieved April 1, 2009.
  46. ^ «ngx_http_request.h». nginx 1.9.5 source code. nginx inc. Archived from the original on September 19, 2017. Retrieved January 9, 2016.
  47. ^ «ngx_http_special_response.c». nginx 1.9.5 source code. nginx inc. Archived from the original on May 8, 2018. Retrieved January 9, 2016.
  48. ^ «return» directive Archived March 1, 2018, at the Wayback Machine (http_rewrite module) documentation.
  49. ^ «Troubleshooting: Error Pages». Cloudflare. Archived from the original on March 4, 2016. Retrieved January 9, 2016.
  50. ^ «Error 520: web server returns an unknown error». Cloudflare.
  51. ^ «527 Error: Railgun Listener to origin error». Cloudflare. Archived from the original on October 13, 2016. Retrieved October 12, 2016.
  52. ^ «Error 530». Cloudflare. Retrieved November 1, 2019.
  53. ^ a b «Troubleshoot Your Application Load Balancers – Elastic Load Balancing». docs.aws.amazon.com. Retrieved August 27, 2019.
  54. ^ «Troubleshoot your Application Load Balancers — Elastic Load Balancing». docs.aws.amazon.com. Retrieved January 24, 2021.
  55. ^ «Hypertext Transfer Protocol (HTTP/1.1): Caching». datatracker.ietf.org. Retrieved September 25, 2021.
  56. ^ «Warning — HTTP | MDN». developer.mozilla.org. Retrieved August 15, 2021. CC BY-SA icon.svg Some text was copied from this source, which is available under a Creative Commons Attribution-ShareAlike 2.5 Generic (CC BY-SA 2.5) license.
  57. ^ «RFC 9111: HTTP Caching, Section 5.5 «Warning»«. June 2022.

External links

  • «RFC 9110: HTTP Semantics and Content, Section 15 «Status Codes»«.
  • Hypertext Transfer Protocol (HTTP) Status Code Registry

Response status and error codes

When using our API, you may encounter certain status and error codes that you need to understand or troubleshoot. This page contains a list of all codes with thorough descriptions and action steps you need to take if you are looking to resolve a problem. 

TIP

Use the page Search field or the Find option to quickly locate the code name you are looking for.

HTTP status codes

Every HTTP transaction has a status code sent back by the server to define how the server has handled the transaction. The most common statuses you may encounter are 200 OK, 404 Not Found, or 401 Unauthorized.

Check out the list of the HTTP status codes to learn more.

API status codes

Besides the standard HTTP status code, the status object may be returned as part of the API response message, delivery report, or message log.

Status object example:

  • JSON
{  
   "groupId":3,
   "groupName":"DELIVERED",
   "id":5,
   "name":"DELIVERED_TO_HANDSET",
   "description":"Message delivered to handset"
}

General status codes

PENDING (group id: 1) — general status codes

The message has been processed and sent to the next instance, i.e., a mobile operator.

ID Status
3 PENDING_WAITING_DELIVERY

  • Message has been processed and sent to the next instance, i.e., a mobile operator with request acknowledgment from their platform. The delivery report has not yet been received and is awaited, so the status is still pending.
7 PENDING_ENROUTE

  • Message has been processed and sent to the next instance, i.e., mobile operator.
26 PENDING_ACCEPTED

  • Message has been accepted and processed, and it`s ready to be sent to the next instance, i.e., operator.

UNDELIVERABLE (group id: 2) — general status codes

The message has not been delivered.

ID Status
4 UNDELIVERABLE_REJECTED_OPERATOR

  • Message has been sent to the operator, whereas the request was rejected, or a delivery report with status REJECTED was reverted.
9 UNDELIVERABLE_NOT_DELIVERED

  • Message has been sent to the operator but has failed to deliver since a delivery report with status UNDELIVERED was reverted from the operator. 

DELIVERED (group id: 3) — general status codes

The message has been successfully processed and delivered.

ID Status
2 DELIVERED_TO_OPERATOR

  • Message has been successfully sent and delivered to the operator.
5 DELIVERED_TO_HANDSET

  • Message has been successfully processed and delivered to the recipient.

EXPIRED (group id: 4) — general status codes

The message has been sent and has either expired due to pending past its validity period (our platform default is 48 hours), or the delivery report from the operator has reverted the expired as a final status.

ID Status
15 EXPIRED_EXPIRED

  • Message was received and sent to the operator. However, it has been pending until the validity period has expired or the operator returned EXPIRED status in the meantime.
29 EXPIRED_DLR_UNKNOWN

  • Message has been received and forwarded to the operator for delivery. However, the delivery report from the operator has not been formatted correctly or has not been recognized as valid.

REJECTED (group id: 5) — general status codes

The message has been received but has either been rejected by Infobip or the operator has reverted REJECTED as final status.

ID Status
6 REJECTED_NETWORK

  • Message has been received, but the network is either out of our coverage or is not set up on your account. Your Account Manager can inform you about the coverage status or set up the network in question.
8 REJECTED_PREFIX_MISSING

  • Message has been received but has been rejected as the number is not recognized due to an incorrect number prefix or number length. This information is different for each network and is regularly updated.
10 REJECTED_DND

  • Message has been received and rejected due to the user being subscribed to DND (Do Not Disturb) services, disabling any service traffic to their number.
11 REJECTED_SOURCE

  • Your account is set to accept only registered sender IDs, and the sender ID defined in the request has not been registered on your account.
12 REJECTED_NOT_ENOUGH_CREDITS

  • Your account is out of credits for further submission. Top up your account. For further assistance in topping up or applying for an online account top-up service, you may contact your Account Manager.
13 REJECTED_SENDER

  • The sender ID has been blocklisted on your account via Infobip web interface. Remove the blocklist on your account or contact Support for further assistance.
14 REJECTED_DESTINATION

  • The destination number has been blocklisted either at the operator request or on your account via web interface, please remove the blocklist on your account via Infobip web interface or contact Support for more information.
17 REJECTED_PREPAID_PACKAGE_EXPIRED

  • Account credits are past their validity period. Top up your sub-account with credits to extend the validity period.
18 REJECTED_DESTINATION_NOT_REGISTERED

  • Your account has been set up for submission only to a single number for testing purposes, contact your Account Manager to remove the limitation.
19 REJECTED_ROUTE_NOT_AVAILABLE

  • Message has been received on the system. However, your account has not been set up to send messages, i.e., no routes on your account are available for further submission. Your Account Manager will be able to set up your account based on your preference.
20 REJECTED_FLOODING_FILTER

  • Message has been rejected due to an anti-flooding mechanism. By default, a single number can only receive 20 varied messages and 6 identical messages per hour. If there is a requirement, the limitation can be extended per account on request to your Account Manager.
21 REJECTED_SYSTEM_ERROR

  • The request has been rejected due to an expected system error. Retry the submission or contact our technical support team for more details.
23 REJECTED_DUPLICATE_MESSAGE_ID

  • The request has been rejected due to a duplicate message ID specified in the submit request; the message IDs should be a unique value. For more information, refer to SMS on the Infobip API Developer Hub.
24 REJECTED_INVALID_UDH

  • Message has been received and our system detected the message was formatted incorrectly because of either an invalid ESM class parameter (fully featured binary message API method) or an inaccurate amount of characters when using esmclass:64 (UDH). For more information, visit the articles below or contact our Support team for clarification.
    User Data Header
    Concatenated SMS
25 REJECTED_MESSAGE_TOO_LONG

  • Message has been received, but the total message length is more than 25 parts or the message text exceeds 4000 bytes as per our system limitation.
51 MISSING_TO

  • The request has been received, however, the to parameter has not been set or it is empty, i.e., there must be valid recipients to send the message.
52 REJECTED_DESTINATION

  • The request has been received, however, the destination is invalid—the number prefix is not correct as it does not match a valid number prefix by any mobile operator. Number length is also taken into consideration when verifying number validity.

Voice status codes

REJECTED (group id: 5) — Voice status codes

The message has been received but has either been rejected by Infobip or the operator has reverted rejected as the final status.

ID Status
53 REJECTED_INVALID_AUDIO_FILE_URL

  • The URL of the audio file is invalid and could not be read properly.
54 REJECTED_UNSUPPORTED_LANGUAGE

  • The language submitted within the request is not supported and request couldn’t be processed correctly.
55 REJECTED_MESSAGE_IS_EMPTY

  • Native to Voice services, this status is returned in case there is no text sent in your Voice message request.
56 REJECTED_INVALID_NOTIFY_URL

  • Native to Voice services, this status is returned in case the notifyUrl parameter is not formatted properly. Refer to Send Voice over API for more information.
57 REJECTED_INVALID_NOTIFY_CONTENT_TYPE

  • Native to Voice services, this status is returned in case the notifyContentType parameter is not formatted properly. Refer to Send Voice over API for more information.
58 REJECTED_INVALID_DTMF_SIGN

  • Defined value for repeating message is invalid and must be a positive number.
59 REJECTED_INVALID_DTMF_TIMEOUT

  • Defined value for the waiting period is invalid and must be a positive number.
60 REJECTED_INVALID_RING_TIMEOUT

  • Defined value for the duration of the call is invalid and must be a positive number.
61 REJECTED_INVALID_CALL_TIMEOUT

  • Defined value for the total period of the call is invalid and must be a positive number.
62 REJECTED_INVALID_MACHINE_DETECTION

  • The action which attempts to detect answering machines at the beginning of the call is invalid.
63 REJECTED_INVALID_ACTIONS

  • Actions submitted in HTTP API request are invalid.
64 REJECTED_INVALID_ACTION_GROUPS

  • Action groups submitted in HTTP API request are invalid.
83 REJECTED_MACHINE_DETECTION_DISABLED

  • Machine detection is not enabled. Contact your dedicated Account manager.
87 REJECTED_INVALID_DELIVERY_TIME_WINDOW

  • Invalid deliveryTimeWindow. The time gap between from and to cannot be less than 1 hour.

MMS status codes

REJECTED (group id: 5) — MMS status codes

The message has been received but has either been rejected by Infobip or the operator has reverted rejected as the final status.

ID Status
56 REJECTED_INVALID_NOTIFY_URL

  • Status is returned when notifyUrl parameter is not formatted properly.
77 REJECTED_MESSAGE_TEXT_TOO_LONG

  • Message has been received, but the textual part of message length exceeds 1600 characters set as our system limitation.

Email status codes

REJECTED (group id: 5) — Email status codes

The email has been received but has either been rejected by Infobip or the operator has reverted rejected as the final status.

ID Status
75 REJECTED_FREE_TRIAL_EXCEEDED

  • This status code is returned by the API when a user’s free trial has been exceeded. It means that the user has exceeded the allowed number of messages or other usage limits during the trial period and must upgrade to their plan to continue using the service.
88 REJECTED_DATA_TRANSFORMATION_FAILED

  • This status code is returned by the API when there is an error in the data transformation process while creating the data needed to proceed with sending a mail. The error can be caused by the placeholders size exceeding limits, or data failing to parse, for example, custom headers.
89 REJECTED_INTERNAL_ERROR

  • This status code is returned by the API when there is an internal error with the system processing a message. It is set when a message goes over the limit of retries or when internal data fails to parse.
90 REJECTED_VALIDATION_FAILED

  • This status code is returned by the API when a validation check fails during the message processing. The validation error can be caused by issues such as an invalid sender, an invalid landing page, invalid preserved recipients, a missing template, and so on.

Push notifications status codes

UNDELIVERABLE (group id: 2) — push notifications status codes

The message has not been delivered.

ID Status
66 UNDELIVERABLE_NO_DESTINATION

  • The status occurs when in a Push API call in object TO defined filter which doesn’t resolve any pushRegistrationIds as destinations for Push delivery. Field to is used to query the message recipient segment. For example, you can try to target according to a “tag” which doesn’t exist at any of instances of the requested ApplicationCode; it will return no destinations as we couldn’t find anything that would satisfy the requested conditions in our database. In another example, you may want to target all application instances (devices) with the Android OS. In this case, you have to use CloudType: GCM and API internally will resolve all destinations and will send the message to all Android devices linked to the requested ApplicationCode. You can also check your valid registrations by using filtering in our web interface. You can more information about User Data at our SDK pages: iOS and Android.

REJECTED (group id: 5) — push notifications status codes

The message has been received but has either been rejected by Infobip, or the operator has reverted rejected as final status.

ID Status
65 REJECTED_NO_APPLICATION

  • The status occurs when an invalid or non-existent ApplicationCode is used in the field from in a Push API call. Each application profile has its own unique ApplicationCode. ApplicationCode is used in SDK as a key identifier for the Application installed on an end user’s device able to communicate with our platform. For the paired device + installed app, pushRegistrationId is issued and it is uniquely linked to ApplicationCode. You should be able to get all available applications or check the configuration.

Error codes

Error object can be returned as part of the send message response or Delivery report response.

Error object example:

  • JSON
{  
   "groupId":0,
   "groupName":"OK",
   "id":0,
   "name":"NO_ERROR",
   "description":"No Error",
   "permanent":false
}

General error codes

OK (group id: 0) — general error codes

The request has been completed successfully.

ID Permanent Error
0 false NO_ERROR

  • There is no error description provided. Mostly returned for successful delivery, or when error code was not returned by the operator.

HANDSET_ERRORS (group id: 1) — general error codes

The request has not been completed due to handset-related issues.

ID Permanent Error
1 true EC_UNKNOWN_SUBSCRIBER

  • The number does not exist or it has not been assigned to any active subscriber in the operator’s user database.
5 false EC_UNIDENTIFIED_SUBSCRIBER

  • Unidentified Subscriber
6 false EC_ABSENT_SUBSCRIBER_SM

  • The subscriber is detected unavailable as there was no paging response from the handset. This is often due to the handset being switched off or low signal area. Applies to MAP protocol version 3.
7 false EC_UNKNOWN_EQUIPMENT

  • The mobile device has not been recognized by EIR (Equipment Identity Register) during device verification on the MAP protocol level at operator’s infrastructure.
8 false EC_ROAMING_NOT_ALLOWED

  • The subscriber is currently in roaming in another country or other operator’s infrastructure — roaming delivery is not guaranteed due to lack of roaming agreements between many different operators.
9 true EC_ILLEGAL_SUBSCRIBER

  • Illegal Subscriber
11 true EC_TELESERVICE_NOT_PROVISIONED

  • The subscriber’s mobile service has been suspended by the operator.
12 true EC_ILLEGAL_EQUIPMENT

  • Illegal Equipment
13 false EC_CALL_BARRED

  • Message is rejected due to barring of message service; blocking is set by operator or subscriber for the number.
21 false EC_FACILITY_NOT_SUPPORTED

  • Facility Not Supported
27 false EC_ABSENT_SUBSCRIBER

  • The subscriber is offline in the network, as confirmed by the handset’s paging response. This is often due to the handset being switched off.
31 false EC_SUBSCRIBER_BUSY_FOR_MT_SMS

  • Subscriber Busy For Mt SMS
32 false EC_SM_DELIVERY_FAILURE

  • SM Delivery Failure
33 false EC_MESSAGE_WAITING_LIST_FULL

  • Message Waiting List Full
34 false EC_SYSTEM_FAILURE

  • System Failure
35 false EC_DATA_MISSING

  • Data Missing
36 false EC_UNEXPECTED_DATA_VALUE

  • Unexpected Data Value
255 false EC_UNKNOWN_ERROR

  • Unknown Error
256 false EC_SM_DF_MEMORYCAPACITYEXCEEDED

  • There has been a mobile subscriber equipment error whereas the handset memory has been exceeded.
257 false EC_SM_DF_EQUIPMENTPROTOCOLERROR

  • There has been a mobile subscriber equipment error.
258 false EC_SM_DF_EQUIPMENTNOTSM_EQUIPPED

  • There has been a mobile subscriber equipment error.
259 false EC_SM_DF_UNKNOWNSERVICECENTRE

  • There has been a mobile subscriber equipment error.
260 false EC_SM_DF_SC_CONGESTION

  • There has been a mobile subscriber equipment error.
261 false EC_SM_DF_INVALIDSME_ADDRESS

  • There has been a mobile subscriber equipment error.
262 false EC_SM_DF_SUBSCRIBERNOTSC_SUBSCRIBER

  • There has been a mobile subscriber equipment error.
500 false EC_PROVIDER_GENERAL_ERROR

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
502 false EC_NO_RESPONSE

  • The message has been successfully processed and forwarded to the operator, but no response was returned from the operator upon the message submit request, or such error was reverted by the operator. The error also applies to similar errors on SS7 network level.
503 false EC_SERVICE_COMPLETION_FAILURE

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
504 false EC_UNEXPECTED_RESPONSE_FROM_PEER

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
507 false EC_MISTYPED_PARAMETER

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
508 false EC_NOT_SUPPORTED_SERVICE

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
509 false EC_DUPLICATED_INVOKE_ID

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
565 true EC_CANNOT_RECEIVE_SC

  • End users connected to this MVNO cannot receive Short Code messages. The mobile operator rejected the message as the end user is connected to their network via a mobile virtual network operator (MVNO). This restriction is on Short Code messages.
573 true EC_SC_BLOCKED_BY_END_USER

  • The end user has asked their mobile operator to block any messages sent from your Short Code. Additional messages from the same Short Code must not be sent to the phone number unless the end user opts in again.
581 false EC_USER_OUT_OF_CREDIT

  • End user out of prepay credit. The end user does not have enough credit on their phone account to receive the message. Message sending can be retried every 24 hours for no more than seven days.
628 true EC_TEMPORARY_HANDSET_FAILURE

  • Temporary handset failure.
629 true EC_DEST_ADDRESS_UNABLE_TO_RECEIVE_SMS

  • Destination address unable to receive SMS.
1024 false EC_OR_APPCONTEXTNOTSUPPORTED

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
1025 false EC_OR_INVALIDDESTINATIONREFERENCE

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
1026 false EC_OR_INVALIDORIGINATINGREFERENCE

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
1027 false EC_OR_ENCAPSULATEDAC_NOTSUPPORTED

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
1028 false EC_OR_TRANSPORTPROTECTIONNOTADEQUATE

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
1029 false EC_OR_NOREASONGIVEN

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
1030 false EC_OR_POTENTIALVERSIONINCOMPATIBILITY

  • General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.
1031 false EC_OR_REMOTENODENOTREACHABLE

  • Mobile subscriber was not reachable due to a network operator protocol error.
1152 false EC_NNR_NOTRANSLATIONFORANADDRESSOFSUCHNATURE

  • Mobile subscriber was not reachable due to a network operator protocol error.
1153 false EC_NNR_NOTRANSLATIONFORTHISSPECIFICADDRESS

  • No Translation For This Specific Address
1154 false EC_NNR_SUBSYSTEMCONGESTION

  • Mobile subscriber was not reachable due to a network operator protocol error.
1155 false EC_NNR_SUBSYSTEMFAILURE

  • Mobile subscriber was not reachable due to a network operator protocol error.
1156 false EC_NNR_UNEQUIPPEDUSER

  • Mobile subscriber was not reachable due to a network operator protocol error.
1157 false EC_NNR_MTPFAILURE

  • Mobile subscriber was not reachable due to a network operator protocol error.
1158 false EC_NNR_NETWORKCONGESTION

  • Mobile subscriber was not reachable due to a network operator protocol error.
1159 false EC_NNR_UNQUALIFIED

  • Mobile subscriber was not reachable due to a network operator protocol error.
1160 false EC_NNR_ERRORINMESSAGETRANSPORTXUDT

  • Mobile subscriber was not reachable due to a network operator protocol error.
1161 false EC_NNR_ERRORINLOCALPROCESSINGXUDT

  • Mobile subscriber was not reachable due to a network operator protocol error.
1162 false EC_NNR_DESTINATIONCANNOTPERFORMREASSEMBLYXUDT

  • Mobile subscriber was not reachable due to a network operator protocol error.
1163 false EC_NNR_SCCPFAILURE

  • Mobile subscriber was not reachable due to a network operator protocol error.
1164 false EC_NNR_HOPCOUNTERVIOLATION

  • Mobile subscriber was not reachable due to a network operator protocol error.
1165 false EC_NNR_SEGMENTATIONNOTSUPPORTED

  • Mobile subscriber was not reachable due to a network operator protocol error.
1166 false EC_NNR_SEGMENTATIONFAILURE

  • Mobile subscriber was not reachable due to a network operator protocol error.
1281 false EC_UA_USERSPECIFICREASON

  • Message was aborted by network peer because of a network protocol error.
1282 false EC_UA_USERRESOURCELIMITATION

  • Message was aborted by network peer because of a network protocol error.
1283 false EC_UA_RESOURCEUNAVAILABLE

  • Message was aborted by network peer because of a network protocol error.
1284 false EC_UA_APPLICATIONPROCEDURECANCELLATION

  • Message was aborted by network peer because of a network protocol error.
1536 false EC_PA_PROVIDERMALFUNCTION

  • Message was aborted due to other network protocol errors.
1537 false EC_PA_SUPPORTINGDIALOGORTRANSACTIONREALEASED

  • Message was aborted due to other network protocol errors.
1538 false EC_PA_RESSOURCELIMITATION

  • Message was aborted due to other network protocol errors.
1539 false EC_PA_MAINTENANCEACTIVITY

  • Message was aborted due to other network protocol errors.
1540 false EC_PA_VERSIONINCOMPATIBILITY

  • Message was aborted due to other network protocol errors.
1541 false EC_PA_ABNORMALMAPDIALOG

  • Message was aborted due to other network protocol errors.
1792 false EC_NC_ABNORMALEVENTDETECTEDBYPEER

  • Message was aborted due to other network protocol errors.
1793 false EC_NC_RESPONSEREJECTEDBYPEER

  • Message was aborted due to other network protocol errors.
1794 false EC_NC_ABNORMALEVENTRECEIVEDFROMPEER

  • Message was aborted due to other network protocol errors.
1795 false EC_NC_MESSAGECANNOTBEDELIVEREDTOPEER

  • Message was aborted due to other network protocol errors.
1796 false EC_NC_PROVIDEROUTOFINVOKE

  • Message was aborted due to other network protocol errors.

USER_ERRORS (group id: 2) — general error codes

User error occurred.

ID Permanent Error
323 true EC_INVALID_REQUEST_TYPE

  • The request type was invalid.
351 false EC_INVALID_DESTINATION_ADDRESS

  • Invalid destination address. Possible reasons for receiving this error for the following mobile operators might be:
    Any operator:
    -The mobile number is not on the mobile operator’s network.
    -The mobile number has been deactivated.
    T-Mobile and MetroPCS:
    -The phone number belongs to a prepaid user who does not have enough credit to receive a message.
    T-Mobile:
    -The end user is not provisioned to receive a message from all short codes (or from specific short codes).
    -The end user is on an MVNO connected via T-Mobile.
    -T-Mobile does not deliver messages from short codes to end users on MVNOs.
    AT&T (US):
  • The phone number belongs to a prepaid user who does not have enough credit to receive a message, the phone number is not provisioned for any messages, or the phone number could be blocked due to a spam complaint.
352 true EC_INVALID_REQUEST_DESTINATION

  • Invalid request — destination address country code is not recognized.
355 true EC_MSG_TEXT_TOO_LONG

  • Message text is too long.
368 true EC_INVALID_SOURCE_ADDRESS

  • Invalid source address value. The mobile operator rejected the message with an invalid MT source address error. Contact your account manager to determine if your MT source address should be supported by the end user’s mobile operator.
375 true EC_SOURCE_ADDRESS_IS_BLOCKED

  • Source address (recipient) is blocked or is not provisioned.
433 true EC_ACCOUNT_ACCESS_DENIED

  • Account access denied.
488 true EC_TF_NUMBER_NOT_VERIFIED

  • »Toll-Free Number Not Verified» which indicates that the number has either gone over the limit or they are trying to send to Canada and the number is not verified. Contact your account manager to get the TFN verified.
541 false EC_LIMIT_REACHED

  • Carrier sending limit has been reached. The message was blocked by AT&T because the TPS (transactions per second) limit on your messaging campaign has been exceeded.
542 false EC_QUOTA_REACHED

  • Carrier daily quota reached. The message was blocked by T-Mobile because the daily volume limit for your brand has been exceeded. You cannot resend the message until the next day.
572 true EC_CAMPAIGNID_NOT_PROVISIONED

  • Program ID or campaign ID is not provisioned for this mobile operator or is not active.
577 true EC_ACC_NOT_PROVISIONED_TO_SMS_DEMO_SC

  • Account not provisioned to use SMS demo short code.
578 true EC_EXCEEDED_THE_TIME_LIMIT_OF_SMS_DEMO

  • Exceeded the time limit for using SMS demo.
579 true EC_DEST_ADDRESS_NOT_IN_SMS_DEMO

  • Destination address not in whitelist for SMS demo.
580 true EC_EXCEEDED_THE_MAX_NUMBER

  • Exceeded the maximum number of demo requests.
594 true EC_INVALID_GLOBAL_CAMPAIGN_ID

  • Invalid global campaign ID.
597 true EC_ACC_HAS_NO_ADRESS_FOR_DESR

  • Account is not provisioned with the address that can reach the destination.
598 true EC_INTERACTION_NOT_SUPPORTED

  • Interaction not supported for message destination.
601 true EC_ACC_NOT_2_WAY

  • Account is not provisioned for global two-way SMS.
603 true EC_CONTENT_BLOCKED

  • Content blocked by user opt-out (MO: STOP). This code can be returned in a delivery receipt for an MT originating from a North American, SMS-enabled toll-free number or an SMS-enabled landline number. Messaging can resume to the end user if the end user opts back in to your program.
604 true EC_BLOCKED_BY_CAMPAIGN_BLACKLIST

  • Content blocked by campaign blocklist.
607 true EC_BLOCKED_AS_SPAM

  • This message was identified as spam and cannot be delivered
2049 true EC_IMSI_BLACKLISTED

  • IMSI blocklisted
2052 true EC_BLACKLISTED_DESTINATIONADDRESS

  • The destination number has been blocklisted either at the operator`s request or on your account via the Infobip web interface. Go to the Infobip web interface to remove the blocklist on your account or contact Support for more information.
2053 true EC_BLACKLISTED_SENDERADDRESS

  • The sender number has been blocklisted either at the operator request or on your account via Infobip web interface. Go to the Infobip web interface to remove the blocklist on your account or contact Support for more information.
2053 true EC_SOURCE_ADDRESS_BLACKLISTED

  • Source address is blocklisted on the Infobip account.
4096 true EC_INVALID_PDU_FORMAT

  • Invalid PDU Format
4099 true EC_MONTHLY_LIMIT_REACHED

  • Your account monthly credit limit has been reached. For further financial assistance, please contact your account manager.
4100 true EC_MESSAGE_CANCELED

  • The request was received, but has not been sent to the next instance within its validity period and has expired with the appropriate error code EC_MESSAGE_CANCELED, or the same error code was reverted from the operator.
4101 true EC_VALIDITYEXPIRED

  • The message was sent to the next instance and has not been delivered within the message validity period, thus it has expired with the appropriate error code EC_VALIDITYEXPIRED or the error code was reverted from the operator.
4102 true EC_NOTSUBMITTEDTOSMPPCHANNEL

  • Inbound SM can not be transferred via SMPP due to the lack of SMPP connectivity.
4103 true EC_DESTINATION_FLOODING

  • Related to status REJECTED_FLOODING_FILTER, the message is rejected due to the number of messages sent to a single number.
4104 true EC_DESTINATION_TXT_FLOODING

  • Related to status REJECTED_FLOODING_FILTER, the message is rejected due to the number of identical messages sent to a single number.

OPERATOR_ERRORS (group id: 3) — general error codes

The request has not been completed due to operator issues.

ID Permanent Error
10 true EC_BEARER_SERVICE_NOT_PROVISIONED

  • Bearer Service Not Provisioned
20 false EC_SS_INCOMPATIBILITY

  • SS Incompatibility
51 true EC_RESOURCE_LIMITATION

  • Indicates that invoked MAP operation could not be finished due to the network congestion — this is an SS7 network congestion error on the MAP protocol level.
71 false EC_UNKNOWN_ALPHABET

  • Unknown Alphabet
345 true EC_OPERATOR_NOT_FOUND

  • Mobile operator not found for the destination address. The service performed a dynamic carrier lookup for the destination address, but it could not be identified; or, the MT source address is not a North American toll-free phone number or landline.
501 false EC_INVALID_RESPONSE_RECEIVED

  • Invalid Response Received
560 true EC_SC_BLOCKED_FOR_END_USER

  • Mobile operator blocking the end user from this Short Code
561 true EC_CONTENT_BLOCKED_BY_OPERATOR

  • Content blocked by mobile operator for this end user.
562 true EC_SC_NOT_PROVISIONED

  • Short code not provisioned with mobile operator. Contact your dedicated Account Manager if you believe that you are provisioned for the operator or if you want to begin provisioning.
563 true EC_SC_EXPIRED

  • Short code expired with mobile operator. Contact your dedicated Account Manager if you believe that you are provisioned for the operator or if you want to begin provisioning.
564 true EC_SC_BLOCKED

  • Short Code blocked by mobile operator. The mobile operator rejected the message as the Short Code is currently blocked from sending messages across their network. Contact your dedicated Account Manager if you are unsure why you received this error.
566 true EC_DESTINATION_BLOCKED_BY_OPERATOR

  • The mobile operator is blocking the phone number from receiving messages from Short Codes. This is likely due to the end-user’s account being suspended or barred in some way.
568 true EC_DESTINATION_NOT_SMS_PROVISIONED

  • Destination address not provisioned for SMS.
569 true EC_DEST_ADDRESS_SUSPENDED

  • Destination address suspended by the mobile operator.
571 false EC_CAMPAIGN_ID_REJECTED

  • Program ID or Campaign ID rejected by mobile operator. This error applies to messages sent to US mobile operators. The error indicates the program ID or campaign ID in the message request is not provisioned with the mobile operator. Contact your dedicated Account Manager if you are unsure why you received this error.
574 true EEC_BLOCKED_NEW_SUBSCRIPTIONS_FOR_SC

  • New subscriptions for this short code are blocked by the mobile operator. Indicates that for a given Short Code, new subscribers are not allowed to receive or send messages. However, existing subscribers are still allowed to receive and send messages.
630 true EC_DEST_OVERLOADED

  • Destination overloaded.
631 true EC_MOBILE_OPERATOR_NETWORK_ERROR

  • Mobile operator network error.
632 true EC_SMS_REJECTED_BY_MOBILE_OPERATOR

  • SMS rejected by the mobile operator for attempted destination address.
633 true EC_UNKNOWN_MOBILE_OPERATOR

  • Message failed due to an unknown mobile operator error.
810 true EC_FAILED_MESSAGE_DELIVERY

  • Failed message delivery.
811 true EC_MESSAGE_EXPIRED

  • Message expired before it reached handset.
815 true EC_MESSAGE_SUBMITTED_NOT_ACKED

  • Message submitted to but not acknowledged by the mobile operator.
2048 false EC_TIME_OUT

  • Time Out
2050 true EC_DEST_ADDRESS_BLACKLISTED

  • The number was flagged as blocklisted in the DND (Do Not Disturb) blocklist provided by the operator, or the same error code was reverted by the operator.
2051 false EC_INVALIDMSCADDRESS

  • Text blocklisted
4097 false EC_NOTSUBMITTEDTOGMSC

  • Not Submitted To GMSC
4102 true EC_NOTSUBMITTEDTOSMPPCHANNEL

  • Not Submitted To Smpp Channel
5492 true EC_DUPLICATE_MESSAGE

  • The same message has already been sent to this destination address.

Voice error codes (legacy)

OK (group id: 0) — voice error codes

The request has been completed successfully.

ID Permanent Error
5000 true VOICE_ANSWERED

  • The call has been received and answered.
5001 true VOICE_ANSWERED_MACHINE

  • The call has been received and answered by a voice machine.

HANDSET_ERRORS (group id: 1) — voice error codes

The request has not been completed due to handset related issues.

ID Permanent Error
5480 false EC_VOICE_ERROR_TEMPORARILY_NOT_AVAILABLE

  • Destination address is currently not available.
5603 false EC_DECLINE

  • Destination does not wish to participate in the call or cannot do so.

OPERATOR_ERRORS (group id: 3) — voice error codes

The request has not been completed due to operator issues.

ID Permanent Error
5002 true EC_VOICE_USER_BUSY

  • The end user is currently busy to receive the Voice call.
5003 true EC_VOICE_NO_ANSWER

  • The end user received a call but didn’t answer it.
5004 true EC_VOICE_ERROR_DOWNLOADING_FILE

  • The file specified in the HTTP request is inaccessible and could not have been downloaded.
5005 true EC_VOICE_ERROR_UNSUPPORTED_AUDIO_FORMAT

  • The format of the file specified is not supported.
5400 false EC_VOICE_ERROR_BAD_REQUEST

  • The received request was rejected because it wasn’t formatted correctly.
5403 false EC_VOICE_ERROR_FORBIDDEN

  • The received request was rejected by the operator.
5404 false EC_VOICE_ERROR_DESTINATION_NOT_FOUND

  • The server has definitive information that the user does not exist at the domain specified in the Request-URI.
5407 false EC_VOICE_ERROR_PROXY_AUTHENTICATION_REQUIRED

  • The request requires user authentication on the operator’s end.
5408 false EC_VOICE_ERROR_REQUEST_TIMEOUT

  • There was no coverage for a specific destination number or the end user couldn’t be found in time during the call.
5410 false EC_VOICE_ERROR_GONE

  • The user existed once, but operator doesn’t support destination address anymore.
5413 false EC_VOICE_ERROR_REQUEST_ENTITY_TOO_LARGE

  • Request entity-body is larger than the server is willing or able to process.
5414 false EC_VOICE_ERROR_REQUEST_URI_TOO_LONG

  • The server is refusing to process the request because the Request-URI is longer than the server is willing to interpret (destination too long).
5415 false EC_VOICE_UNSUPPORTED_MEDIA_TYPE

  • Format of the file is not supported.
5481 false EC_VOICE_ERROR_CALL_DOES_NOT_EXIST

  • Call or Transaction does not exist.
5484 false EC_VOICE_ERROR_ADDRESS_INCOMPLETE

  • Specified destination number is incomplete.
5487 false EC_VOICE_ERROR_REQUEST_TERMINATED

  • Request has been terminated with a cancel button and end user refused to receive a voice call.
5488 false EC_VOICE_ERROR_NOT_ACCEPTABLE_HERE

  • The format of the request is not acceptable on the operator’s end.
5491 false EC_VOICE_ERROR_REQUEST_PENDING

  • Server has some pending request from the same dialog.
5501 true EC_VOICE_NOT_IMPLEMENTED

  • The submitted request is not supported on the operator’s end.
5503 true EC_VOICE_SERVICE_UNAVAILABLE

  • The service failed to complete the request.

Voice and WebRTC error codes

OK (group id: 0)

The request has been completed successfully.

ID Permanent Error
10000 true NORMAL_HANGUP

  • The call ended due to a hangup initiated by the caller, callee, or API.
10001 true ANSWERED_ELSEWHERE

  • Another device answered the call.
10002 true MACHINE_DETECTED

  • A voice machine answered the call.
10003 true HUMAN_DETECTED

  • A person (not a voice machine) answered the call.
10004 true MAX_DURATION_REACHED

  • Max call or conference duration reached.

HANDSET_ERRORS (group id: 1)

The request has not been completed due to handset-related issues.

ID Permanent Error
10100 true DEVICE_FORBIDDEN

  • Permission to use camera and/or microphone was denied.
10101 true DEVICE_NOT_FOUND

  • Camera and/or microphone not found.
10102 true DEVICE_UNAVAILABLE

  • Camera and/or microphone not available.
10103 true MEDIA_ERROR

  • Media invalid or unavailable.

USER_ERRORS (group id: 2)

User error occurred.

ID Permanent Error
10200 true NO_ANSWER

  • The end user received a call but didn’t answer it.
10201 true BUSY

  • The end user is currently busy to receive the voice call.
10202 true CANCELED

  • The end user canceled the call.
10203 true REJECTED

  • The destination cannot join the call at the moment.
10204 true TEMPORARILY_UNAVAILABLE

  • The destination is temporarily unavailable.

OPERATOR_ERRORS (group id: 3)

The request has not been completed due to operator issues.

ID Permanent Error
10300 true FORBIDDEN

  • The received request was rejected.
10301 true INSUFFICIENT_FUNDS

  • Insufficient funds to make a call.
10302 true UNAUTHENTICATED

  • The request requires user authentication on the operator’s end.
10303 true DESTINATION_NOT_FOUND

  • The server has definitive information that the user does not exist.
10304 true DESTINATION_UNAVAILABLE

  • The destination is currently out of service.
10305 true INVALID_DESTINATION

  • The specified destination is invalid.
10306 true INVALID_REQUEST

  • The format of the request is invalid.
10307 true REQUEST_TIMEOUT

  • There was no coverage for a specific destination, or the end user could not be reached in time for the call.
10308 true NETWORK_ERROR

  • There has been a network connection error.
10309 true SERVICE_UNAVAILABLE

  • Service is currently unavailable.
10310 true UNKNOWN

  • The call has ended due to an unknown reason.
10311 true FEATURE_UNAVAILABLE

  • The requested feature is not enabled.
10312 true CONGESTION

  • Service is currently congested.
10400 true URL_NOT_FOUND

  • The specified application URL does not exist or cannot be found.
10401 true URL_UNREACHABLE

  • The specified application URL is unreachable.
10402 true INVALID_RESPONSE

  • Specified application returned a response with an invalid format.

WebRTC error codes (legacy)

OK (group id: 0) — WebRTC error codes. The request has been completed successfully.

ID Permanent Error
5700 true ANSWERED

  • The call has been received and answered.
5701 true EC_CALL_ANSWERED_ON_ANOTHER_DEVICE

  • The call was answered on another device.

HANDSET_ERRORS (group id: 1) — WebRTC error codes

The request has not been completed due to handset related issues.

ID Permanent Error
5720 true EC_NO_PEER_CONNECTION

  • The peer connection hasn’t been established.
5721 true EC_INVALID_DTMF_CONFIG_NO_AUDIO_TRACK

  • Invalid DTMF configuration (no audio track).
5722 true EC_DTMF_UNAVAILABLE

  • DTMF options is not available.
5723 true EC_DTMF_INVALID_TONE

  • Invalid DTMF tone sent. Allowed tones are digits 1-9, * and #.
5724 true EC_NO_LOCAL_STREAM

  • Local stream was not initialized.
5725 true EC_NO_AUDIO_TRACK

  • The audio track is missing.
5726 true EC_NO_VIDEO_TRACK

  • The video track is missing.
5727 true EC_NO_DISPLAY_MEDIA

  • Display media API is not available.
5728 true EC_UNKNOWN_SCREEN_SHARE_ERROR

  • Unknown screen share error.

USER_ERRORS (group id: 2) — WebRTC error codes

User error occurred.

ID Permanent Error
5800 true EC_NO_ANSWER

  • The end user received the call but did not answer it.
5801 true EC_USER_BUSY

  • The end user is currently busy and not able to receive the call.
5802 true EC_PERMISSION_DENIED

  • Permission to use camera and/or microphone was denied.
5803 true EC_DEVICE_NOT_FOUND

  • Device does not have a camera and/or microphone connected/enabled.
5804 true EC_DEVICE_NOT_AVAILABLE

  • Camera or microphone is already in use.
5805 true EC_ACTIVE_CALL_ON_INCOMING_CAL

  • The end user received an incoming call while they were on another active call.
5806 true EC_CALL_TERMINATED

  • Call terminated.
5850 true EC_USER_ALREADY_JOINED

  • The end user is already joined on another device.
5851 true EC_MAX_USERS_LIMIT_REACHED

  • The maximum number of users was already reached.
5852 true EC_VIDEO_PUBLISHERS_LIMIT_REACHED

  • The maximum number of users that are publishing a video was already reached.

OPERATOR_ERRORS (group id: 3) — WebRTC error codes

The request has not been completed due to operator issues.

ID Permanent Error
5768 true EC_CLIENT_URL_READ_FAILURE

  • Could not read the client’s URL.
5769 true EC_CLIENT_URL_REACH_FAILURE

  • Could not reach the client’s URL.
5900 true EC_FORBIDDEN

  • The received request was rejected.
5901 true EC_REQUEST_TIMEOUT

  • There was no coverage for a specific destination number, or the end user could not be reached in time for the call.
5902 true EC_INTERNAL_SERVER_ERROR

  • The server could not process the request because of an unexpected error.
5903 true EC_DESTINATION_NOT_FOUND

  • The server has definitive information that the end user does not exist within the domain specified in the Request-URI.
5904 true EC_SERVICE_TEMPORARY_UNAVAILABLE

  • The service is temporary unavailable.
5905 true EC_REQUEST_PENDING

  • The server has a pending request from the same dialog.
5906 true EC_ADDRESS_INCOMPLETE

  • The specified destination number is incomplete.
5907 true EC_TEMPORARILY_NOT_AVAILABLE

  • The destination address is currently unavailable.
5990 true EC_CONNECTION_ERROR

  • There has been a connection error.
5991 true EC_UNKNOWN_WEBRTC_ERROR

  • There has been an unknown WebRTC error.

Push notification error codes

Registration error (group id: 1) — push notification error codes

Messages not sent due to device registration problems (e.g., in cases of uninstalled applications).

ID Permanent Error
8001 true EC_DEVICE_APP_UNINSTALL

  • User has uninstalled the application on device or device cloud token expired.
8002 true EC_GCM_MISMATCH_SENDER_ID

  • FCM responded with MismatchSenderId in response error field. Sender ID is a unique numerical value created when you create your Firebase project, available in the Cloud Messaging tab of the Firebase console`s Settings panel. The sender ID is used to identify each app server that can send messages to the client app. Check your application build configuration.
8003 true EC_NO_APPLICATION_FOUND

  • Application with provided ApplicationCode is not found at Infobip Push service. Check your message target parameters.
8004 true EC_NO_REGISTRATION_ID_FOUND

  • Registration with provided PushRegistrationId does not exist or has expired.

Cloud error (group id: 3) — push notification error codes

Messages not sent due to Clouds communication issues.

Id Permanent Error
8005 true EC_SYS_ERROR_FROM_CLOUD

  • Failed to send push notification. Cloud (FCM or APNS) responded with error while processing the request.
8006 true EC_INVALID_GCM_AUTH_DATA

  • Invalid cloud authentication data (Server Key). FCM responded with status 401 (Unauthorized). Check your Application configuration for Android on the Infobip web interface.
8007 true EC_INVALID_APNS_CERT

  • Invalid certificate for APNS. Check your Application configuration for iOS on the Infobip web interface.
8008 true EC_APPLICATION_CLOUD_TYPE_DISABLED

  • Cloud type was disabled by client for the application. Request is targeted to registration with cloud type that was disabled by the client. Check your Application configuration on the Infobip web interface.
8009 true EC_PUSH_INTERNAL_REQUEST_ERROR

  • Internal error. Please try again later and, if the problem persists, contact Support for further assistance.
8010 true EC_INVALID_PUSH_PAYLOAD

  • Invalid push payload data. Please contact Support for further assistance.
8011 true EC_PUSH_INTERNAL_GW_ERROR

  • Internal error. Please try again later and if problem persists, contact Support for further assistance.
8012 true EC_PUSH_CLOUD_TEMP_UNAVAILABLE

  • Push Cloud (FCM or APNS) is temporarily unavailable. Message is pending in retry.

Email error codes

Dropped (group id: 1) — email error codes

The request has not been completed successfully as emails were dropped by the mail delivery system on the end-user side.

ID Permanent Error
6001 true EC_EMAIL_BLACKLISTED

  • The sender name used is a part of real-time database which consists of forbidden domains/sender names/IPs that are categorized as spam-friendly.
6002 true EC_EMAILS_SPAM_CONTENT

  • Emails are dropped due to spam content.
6003 true EC_EMAIL_UNSUBSCRIBED_EMAIL_ADDRESS

  • Got Bounced message as sender possibly is being unsubscribed by recipient.
6004 true EC_BOUNCED_EMAIL_ADDRESS

  • Confirmation that email cannot be delivered as bounce message was reverted on the previous attempt.
6005 true EC_EMAIL_DROPPED

  • Recipient had previously bounced, unsubscribed, or complained of spam so we will not attempt delivery and the message will be dropped.
6016 true EC_EMAIL_SENDER_DOMAIN_BLOCKED

  • Sender domain blocked. This generally happens when the sender domain exceeds the bounce threshold.
6017 true EC_EMAIL_IP_BLACKLISTED

  • Sender IP address is blocklisted, in which case the IP needs delisting.
6018 true EC_INVALID_GATEWAY_REQUEST

  • There are one or more validation errors present when forming the email gateway request. Contact support.
6021 true EC_EMAIL_HANDLE_BARS_ERROR

  • There are one or more Handlebars syntax errors.

Bounced (group id: 2) — email error codes

The request has not been completed successfully and we received NDR (Non-delivery receipt).

ID Permanent Error
6006 true EC_INVALID_EMAIL_ADDRESS

  • End-user’s name is not a valid one — Either invalid characters or either invalid domain was used.
6007 true EC_MAILBOX_TEMPORARY_UNAVAILABLE

  • End-user’s mailbox might be temporarily unavailable on the server.
6008 true EC_DEFERRED_DUE_TO_INSUFFICIENT_STORAGE

  • End-user’s mailbox has reached its full capacity defined on the server.
6009 true EC_MAILBOX_UNAVAILABLE

  • End-user’s mailbox might have restricted access or simply does not exist on the server.
6010 true EC_STORAGE_LIMIT_EXCEEDED

  • End-user’s mailbox has reached its full capacity defined on the server.
6012 true EC_HARD_BOUNCE

  • We received a bounced message (Non-delivery receipt). Possible reasons: Recipient email address does not exist; Domain name does not exist; Recipient email server has completely blocked delivery.

System Error (group id: 3) — email error codes

The request has not been completed successfully due to system-related errors.

ID Permanent Error
6011 false EC_SOFT_BOUNCE

  • Email has been undelivered even though the recipient’s email address is correct.
6013 false EC_TEMPORARY_SENDING_ERROR

  • Temporary Sending Error. The system will retry sending.
6014 true EC_PERMANENT_SENDING_ERROR

  • Most commonly the issue lies within the domain used as the sender as it probably has not been registered yet.
6015 true EC_EMAIL_GATEWAY_ERROR

  • Sending email failed due to internal error.
6020 true EC_EMAIL_TEMPLATE_NOT_FOUND

  • Email template cannot been found.
6025 true EMAIL_INVALID_TRACKING_PARAMS

  • Email contains invalid tracking parameters.
6026 true LANDING_PAGE_PLACEHOLDERS_SIZE_EXCEEDED

  • Landing page placeholders size is exceeded.
6027 true INVALID_HEADERS

  • Email contains invalid custom headers.
6028 true EMAIL_PARSING_FAILED

  • Email response parsing has failed.
6029 true INVALID_SENDER

  • Email has been sent from an invalid sender.
6030 true INVALID_LANDING_PAGE

  • Email contains an invalid landing page.
6031 true INVALID_PRESERVED_RECIPIENTS

  • The preserved recipients are invalid.
6032 true EMAIL_EXPIRED

  • Email has expired due to an internal error.

Chat error codes

(RCS, WhatsApp, Facebook messenger, LINE, Viber)

Client error (group id: 1) — chat error codes

The request has not been completed successfully due to application misconfiguration or a bad/invalid request issued by the client.

ID Permanent Error
7001 true EC_UNKNOWN_APPLICATION

  • Application used to send the message does not exist. Make sure you have created the application and that you are using a valid application key.
7002 true EC_UNKNOWN_USER

  • Receiving user does not exist. Check that the user has subscribed to the service and that you are using the correct user key.
7003 true EC_BLOCKED_USER

  • Receiving user has blocked communication.
7004 true EC_UNAUTHORIZED_ACCESS

  • Invalid or unrecognized service access credentials. Make sure that you are using the correct access credentials issued by the service provider.
7005 true EC_FORBIDDEN_ACCESS

  • Authentication was recognized, but not allowed. Check that your application is allowed to send messages, and that it is published or approved by the provider.
7006 true EC_BAD_REQUEST

  • The received request was incomplete or invalid (invalid parameter value, consecutive spaces etc.)
7007 true EC_ILLEGAL_TRAFIC_TYPE

  • Attempt to send a message with not allowed type.
7008 true EC_INVALID_TEMPLATE_ARGS

  • Message does not match the template. Check template arguments and text.
7009 true EC_INVALID_TEMPLATE

  • Template used to send the message does not exist. Make sure the template is created and that you are using a valid template.
7010 true EC_NO_SESSION

  • User did not initiate a session and therefore cannot be contacted.
7011 true EC_ACCOUNT_ISSUE

  • There is a problem with your account. Contact our Support team for more information.
7012 false EC_DEPLOYMENT_CONFIGURATION_ERROR

  • Issue with WhatsApp deployment
7013 false EC_MEDIA_HOSTING_ERROR

  • Provided media link has issues related to hosting.
7014 false EC_MEDIA_UPLOAD_ERROR

  • Issue with media upload to provider
7015 true EC_MEDIA_METADATA_ERROR

  • Issue with provided media metadata, content-type, size, etc.
7016 true EC_SPAM_RATE

  • Message failed because there are restrictions (related to WhatsApp sender quality rating) on how many messages can be sent from this sender to unique end users during the rolling 24 hour period.
7017 false EC_TOO_MANY_REQUESTS

  • Sending speed is too high
7018 true EC_INTERNAL_BAD_MAPPING

  • Internal bad request
7019 true EC_PROVIDER_BILLING_ERROR

  • Billing error on provider`s side (for now Viber only)
7020 true EC_DEVICE_REPRODUCTION ERROR

  • Error displaying content on the end-user device
7021 true EC_LIMITED_FUNCTIONALITY

  • Product functionality limited on the provider`s side.
7022  true EC_MEDIA_UNSUPPORTED

  • The media format is not supported.
7023  true EC_DATA_MISMATCH

  • Data mismatch between local and remotely synced source.
7024  false EC_NOT_ALLOWED_SENDING_TIME

  • Message sent outsite of allowed time window.
7025  true EC_UNSUPPORTED_MOBILE_APP_VERSION

  • Unsupported mobile application version.
7026  true EC_MESSAGE_TYPE_EXHAUSTED

  • Supplier API limit exhausted for specific message type.
7027 true EC_BLOCKED_CONTENT

  • Message content has been blocked.
7029 true

EC_USER_IDENTITY_CHANGED

  • User identity has changed.
7102 true EC_DATA_MISMATCH

  • Data mismatch between local and remotely synced source.
7201 true EC_UNSUPPORTED_DEVICE

  • The receiving user does not have a device that can receive this type of message.

Provider error (group id: 2) — chat error codes

The request has not been completed successfully due to a service provider error.

ID Permanent Error
7050 false EC_PROVIDER_INTERNAL_ERROR

  • Internal service provider error.
7051 false EC_PROVIDER_TIMEOUT

  • Connection to service provider timed out.
7052 true EC_PROVIDER_DR_ERROR

  • Provider error in delivery report, non-retryable due to platform limitations.

System Error (group id: 3) — chat error codes

The request has not been completed successfully due to a system-related error.

ID Permanent Error
7080 true EC_INTERNAL_ERROR

  • Internal error on the Infobip web interface. Contact Support to resolve the issue.
7081 true EC_CONFIGURATION_ERROR

  • Internal configuration error. Contact Support to resolve the issue.
7082 true EC_TEMPORARY_GATEWAY_ERROR

  • Temporary internal error. Contact our Support for more information.
7083 true EC_SERVICE_NOT_ACTIVATED

  • Service not active. Contact Support to resolve the issue.
7084 true EC_MISSING_SENDER_METADATA

  • Missing sender metadata. Contact our Support to perform the necessary adjustment.
7280 true EC_DUPLICATE_REQUEST

  • Identical message was recently sent to the user.
7281 true EC_BAD_ORIGIN

  • Request was sent from an unapproved origin. Contact Support to resolve the issue.

Twitter error codes

User error (group id: 2) — Twitter error codes

User error occurred.

ID Permanent Error
16001  true EC_CANNOT_SEND_TO_THIS_USER

  • Unable to send message to this user (blocked or not followed).
16002  true EC_USER_NOT_FOLLOWING

  • User is not following you.
16003 true EC_TEXT_SIZE_OVER_LIMIT

  • Text size over limit.

Mobile Identity error codes

ID Value Description
100 EC_NO_COVERAGE No coverage for requested phone number.
101 EC_GATEWAY_OPERATION_FAILED Provider service failed.
102 EC_OPERATION_RESTRICTED Operation restricted.
103 EC_ATP_ATTRIBUTE_QUERY_FAILED ATP attribute query failed
200 EC_INVALID_REQUEST Validation failed for requested arguments.
201 EC_INVALID_TOKEN The token is invalid or does not exist.
202 EC_CONSENT_NOT_GRANTED User consent not granted.
300 EC_MI_ACCOUNT_DISABLED User account is disabled for Mobile Identity service. Contact sales to enable it.
301 EC_OPERATION_NOT_ALLOWED Service not allowed for this account. Contact sales to enable it.
302 EC_COUNTRY_NOT_ALLOWED Destination country is not allowed for this account. Contact sales to enable it.
303 EC_GATEWAY_NOT_ALLOWED Provider is not allowed for this account. Contact sales to enable it.
304 EC_REJECTED_NOT_ENOUGH_CREDITS Not enough credits for this service.
305 EC_MOBILE_DEVICE_TIMEOUT Timeout occurred during a mobile device redirect.
306 EC_REJECTED_INVALID_IP_ADDRESS IP address not in MNO data range.
307 EC_OTP_SMS_SEND_FAILED Failed to send an SMS message.
308 EC_NI_ATTRIBUTE_NOT_ALLOWED Requested Number Intelligence attribute is not allowed for this account. Contact sales to enable it.
309 EC_SIM_SWAP_CHECK_FAILED Failed to execute SIM Swap check request due to an error on the MNO side. Contact support@infobip.com for more details.
310 EC_SIM_SWAP_DETECTED No coverage for requested phone number.
1000 EC_INTERNAL_ERROR Internal error on the Infobip platform. Contact Support to resolve the issue.

DLT error codes

INFO

Applicable only to the India region.

ID Status Description
4106 EC_BLOCKED_BY_DLT Message blocked by DLT Scrubbing.
4 — Message sent, not delivered.
4107 EC_DLT_SCRUBBING_TIMEOUT Timeout while performing DLT Scrubbing.
4 — Message sent, not delivered.
4108 EC_SENDER_BLOCKED_BY_DLT Sender blocked by DLT Scrubbing.
4 — Message sent, not delivered.
4109 EC_TELEMARKETER_BLOCKED_BY_DLT Telemarketer blocked by DLT Scrubbing.
4 — Message sent, not delivered.
4110 EC_ENTITY_BLOCKED_BY_DLT Entity blocked by DLT Scrubbing.
4 — Message sent, not delivered.
4111 EC_TEMPLATE_BLOCKED_BY_DLT Template blocked by DLT Scrubbing.
4 — Message sent, not delivered.
4112 EC_ENTITY_NOT_FOUND  No record found with EID as primary key. 
4 — Message sent, not delivered.
4113 EC_ENTITY_NOT_REGISTERED  No entry of entity on the platform. 
4 — Message sent, not delivered.
4114 EC_ENTITY_INACTIVE  Entity is inactive on the platform.               
4 — Message sent, not delivered.
4115 EC_ENTITY_BLACKLISTED  Entity is blocklisted on all platforms.
4- Message sent, not delivered.
4116 EC_INVALID_ENTITY_ID  Received wrong entity id format or no entity.
4-Message sent, not delivered.
4117 EC_ENTITY_ID_NOT_ALLOWED_FOR_TM Principal entity is not allowed for the TM.
4 — Message sent, not delivered.
4118 EC_TELEMARKETER_NOT_REGISTERED No entry of TMID on the platform.
4 — Message sent, not delivered.
4119 EC_TELEMARKETER_INACTIVE  Telemarketer is inactive on the platform.
4  -Message sent, not delivered
4120 EC_TELEMARKETER_BLACKLISTED  Telemarketer is blocklisted on all platforms.
4 — Message sent, not delivered
4121 EC_HEADER_NOT_FOUND  No record found with header (case sensitive).
4 — Message sent, not delivered.
4122 EC_HEADER_INACTIVE  Header is inactive on the platform.
4- Message sent, not delivered.
4123 EC_HEADER_BLACKLISTED  Header is blocklisted on all platforms.
4 — Message sent, not delivered.
4124 EC_PEID_NOT_MATCHED_WITH_HEADER Principle Entity Id is not matched with Header Id.
4 — Message sent, not delivered
4125 EC_HEADER_IN_FREEPOOL  Header in free pool. 
4 — Message sent, not delivered.
4126 EC_TEMPLATE_NOT_FOUND  No record found with Template Id as primary key/no template found.
4 — Message sent, not delivered. 
4127 EC_TEMPLATE_INACTIVE  Template is inactive on the platform.
4 — Message sent, not delivered.
4128 EC_TEMPLATE_BLACKLISTED  Template is blocklisted on all platforms.
4 — Message sent, not delivered.
4129 EC_TEMPLATE_NOT_MATCHED  Template not matched for given Template Id. 
4 — Message sent, not delivered.
4130 EC_HEADER_NOT_REGISTERED_FOR_TEMPLATE Header is not registered for the template.
4 — Message sent, not delivered.
4131 EC_TEMPLATE_VARIABLE_EXCEEDED_MAX_LENGTH Variable length exceeded the max configured length.
4 — Message sent, not delivered.
4132 EC_ERROR_IDENTIFYING_TEMPLATE Error in identifying the template.
4 — Message sent, not delivered.
4133 EC_INVALID_TEMPLATE_ID  Received wrong Template Id format or no Template Id tag.
4 — Message sent, not delivered.
4134 EC_TEMPLATE_NOT_REGISTERED_TO_ENTITY Template does not belong to PE.
4 — Message sent, not delivered.
4135 EC_PROMOTIONAL_TEMPLATE_USED_ON_OTHERS_HEADER Promotional Template used on other/transaction header.
4 — Message sent, not delivered.
4136 EC_INVALID_TEMPLATE_TYPE  Invalid template type. 
4 — Message sent, not delivered.
4137 EC_PREFERENCE_NOT_MATCHED  Blocked in preferences with MSISDN as PK.
4 — Message sent, not delivered.
4138 EC_INVALID_PROMO_TIME  Block promo hours (9PM to 10AM). 
4 — Message sent, not delivered.
4139 EC_SE_CATEGORY_BLOCK  SE category blocking on fully DND, if consent not available.
4 — Messsage sent, not delivered.
4140 EC_CONSENT_FAILED  General error code for Consent.
4 — Message sent, not delivered.
4141 EC_SCRUBBING_FAILED  General error code in case of any exceptions.
4 — Message sent, not delivered.
4142 EC_TLV_PEID_NOT_FOUND  TLV PEID missing/empty/null.
4 — Message sent, not delivered.
4143 EC_TLV_TMPID_NOT_FOUND  TLV TMPID missing/empty/null.
4 — Message sent, not delivered.
4144 EC_CONTENT_MULTIPART_INCOMPLETE_BY_DLT  Undelivered/expired.
If the DLT has not received long SMS parts or if any part is missing, the DLT shows this code.

Live Chat error codes

Below are the possible error codes for:

  • Web Widget
  • Enable Authenticated Customer Session With Widget API
  • Invalidate Authenticated Customer Session
ID Status Description
1001 mandatory field missing Param ‘widgetId’ is required in the method.
1011 widget initializing error Widget already initialized.
1012 widget initializing error Error in the widget configuration.
1013 widget initializing error Already authenticated with another widget id.
1031 widget visibility error Initializing on pages that are not allowed.
1032 widget visibility error Auth customers only.
1033 widget visibility error Outside working hours.
1101 mandatory field missing ‘token’ parameter is required in the method.
1102 mandatory field missing ‘ski’ field is required in JWT.
1103 mandatory field missing ‘sub’ field is required in JWT.
1104 mandatory field missing ‘iss’ field is required in JWT.
1105 mandatory field missing ‘iat’ field is required in JWT.
1106 mandatory field missing ‘jti’ field is required in JWT.
1111 field in wrong type ‘iat’ should be a ‘number’ type and should be in seconds.
1112 field in wrong type ‘exp’ should be a ‘number’ type and should be in seconds.
1113 field in wrong type ‘stp’ should be one of [’email’, ‘msisdn’, ‘externalPersonId’].
1114 field in wrong format Check ‘sub’ for ‘stp’ type.
1121 method invocation error User is already authenticated.
1122 method invocation error JWT payload is broken.
1123 method invocation error ‘ski’ is wrong, no widget key with this id.
1124 method invocation error ‘alg’ is incorrect. 
1125 method invocation error There’s something wrong with the encryption.
1126 method invocation error ‘iss’ differs from the initialized widget id.
1127 method invocation error ‘iat’ is not valid, should be earlier than now.
1128 method invocation error ‘exp’ is not valid, should be later than now.
1198 connection issue Failed to authenticate. Please try again later.
1199 request error Request failed with status ${status}.
1321 method invocation error User is already logged out.
Источник
  • Below are lists of REST API error codes, and an explanation of how errors are returned back to applications.

Contents

  1. Handling and Logging Exceptions
  2. Error Types
    1. HTTP-Level
    2. Response-Level
      1. Error Codes
    3. Record-Level
      1. Error Codes

Handling and Logging Exceptions

When developing for Marketo, it’s very important that requests and responses get logged when an unexpected exception is encountered.  While certain types of exceptions, such as expired authentication can be safely handled by reauthentication, others may require support interactions, and requests and responses will always be requested in this scenario.

Error Types

The Marketo REST API can return three different types of errors under normal operation:

  • HTTP-Level – These errors are indicated by a 4xx code.
  • Response-Level – These errors are included in the “errors” array of the JSON response.
  • Record-Level – These errors are included in the “result” array of the JSON response, and are indicated on an individual record basis with the “status” field and “reasons” array.

For Response-Level and Record-Level error types, an HTTP status code of 200 is returned.  For all error types, the HTTP reason phrase should not be evaluated as it is optional and subject to change.

HTTP-Level

Under normal operating circumstances Marketo should only return two HTTP status code errors, 413 Request Entity Too Large, and 414 Request URI Too Long.  These are both recoverable through catching the error, modifying the request and retrying, but with smart coding practices, you should never encounter these in the wild.

Marketo will return 413 if the Request Payload exceeds 1MB, or 10MB in the case of Import Lead.  In most scenarios it unlikely to hit these limits, but adding a check to the size of the request and moving any records which cause the limit to be exceeded to a new request should prevent any circumstances which lead to this error being returned by any endpoints.

414 will be returned when the URI of a GET request exceeds 8KB.  To avoid it, check against the length of your query string to see if it exceeds this limit.  If it does change your request to a POST method, then input your query string as the request body with the additional parameter ‘_method=GET’.  This forgoes the limitation on URIs.  It’s rare to hit this limit in most cases, but is somewhat common when retrieving large batches of records with long individual filter values such as a GUID.

The Identity endpoint can return a 401 Unauthorized error. This is typically due to an invalid Client Id or invalid Client Secret.

HTTP-Level Error Codes

Response Code

Description

Comment
413 Request Entity Too Large Payload exceeded 1MB limit.
414 Request-URI Too Long URI of the request exceeded 8k. The request should be retried as a POST with param _method=GET in the URL, and the rest of the querystring in the body of the request.

Response-Level

Response level errors are present when the “success” parameter of the response is set to false, and will be structured like this:

{

    «requestId»: «e42b#14272d07d78»,

    «success»: false,

    «errors»: [

        {

            «code»: «601»,

            «message»: «Unauthorized»

        }

    ]

}

Each object in the “errors” array has two members, “code,” which is a quoted integer from 601 to 799 and a “message” giving the plaintext reason for the error.  6xx codes always indicate that a request failed completely and were not executed.  An example of this is a 601, “Access token invalid,” which is recoverable by re-authenticating and passing the new access token with the request.  7xx errors indicate that the request failed, either because no data was returned, or the request was incorrectly parameterized, such as including an invalid date, or missing a required parameter.

Response-Level Error Codes

* An API call that returns this response code is not counted against your daily quota, or your rate limit

Response Code

Description

Comment
502 Bad Gateway The remote server returned an error. Likely a timeout. The request should be retried with exponential backoff.
601* Access token invalid An Access Token parameter was included in the request, but the value was not a valid access token.
602* Access token expired The Access Token included in the call is no longer valid due to expiration.
603 Access denied Authentication is successful but user doesn’t have sufficient permission to call this API. Additional permissions may need to be assigned to the user role, or Allowlist for IP-Based API Access may be enabled.
604* Request timed out The request was running for too long (e.g. encountered database contention), or exceeded the time-out period specified in the header of the call.
605* HTTP Method not supported GET is not supported for Sync Leads endpoint, POST must be used.
606 Max rate limit ‘%s’ exceeded with in ‘%s’ secs The number of calls in the past 20 seconds was greater than 100
607 Daily quota reached Number of calls today exceeded the subscription’s quota (resets daily at 12:00AM CST).

Your quota can be found in your Admin->Web Services menu.  You can increase your quota through your account manager.
608* API Temporarily Unavailable
609 Invalid JSON The body included in the request is not valid JSON.
610 Requested resource not found The URI in the call did not match a REST API resource type. This is often due to an incorrectly spelled or incorrectly formatted request URI
611* System error All unhandled exceptions
612 Invalid Content Type If you see this error, add a content type header specifying JSON format to your request. For example, try using “content type: application/json”. Please see this StackOverflow question for more details.
613 Invalid Multipart Request The multipart content of the POST was not formatted correctly
614 Invalid Subscription The destination subscription cannot be found or is unreachable.  This usually indicates temporary inaccessibility.
615 Concurrent access limit reached At most 10 requests can be processed by any subscription at a time. This will be returned if there are already 10 requests for the subscription ongoing.
616 Invalid subscription type The appropriate Marketo subscription type is required to access the Custom Object Metadata API.  Please consult your CSM for details.
701 %s cannot be blank The reported field must not be empty in the request
702 No data found for given search scenario No records matched the given search parameters.

Note: Many failed search operations will return “success = true” and no errors and set a warnings informational string.
703 Feature is not enabled for the subscription A beta feature that has not been in enabled in a user’s subscription
704 Invalid date format
  • A date was specified that was not in the correct format
  • An invalid dynamic content id was specified
709 Business Rule Violation The call cannot be fulfilled because it violates a requirement to create or update an asset, e.g. trying to create an email without a template. It is also possible to get this error when trying to:

  • Retrieve content for landing pages that contain social content.
  • Clone a program that contains certain asset types (see Program Clone for more information).
  • Approve an asset that has no draft (i.e. has already been approved).
710 Parent Folder Not Found The specified parent folder could not be found
711 Incompatible Folder Type The specified folder was not of the correct type to fulfill the request
712 Merge to person Account operation is invalid A Merge Leads call failed because of an attempt to merge leads that are Salesforce Person Accounts.   Salesforce Person Accounts must be merged in Salesforce.
713 Transient Error A system resource was temporarily unavailable at the time of the API call.  When this error is encountered, it is advised to wait for a period of time and then retry the request.
714 Unable to find default record type A Merge Leads call failed because it was unable to find a default record type.
718 ExternalSalesPersonID not found A Sync Opportunities call was made with a non-existant ExternalSalesPersonID  value.
719 Lock wait timeout exception A Clone Program call was made and timed out waiting for a lock.

Record-Level

Record level errors indicate that an operation could not be completed for an individual record, but the request itself was valid.  A response with record-level errors will follow this pattern:

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

{  

   «requestId»:«e42b#14272d07d78»,

   «success»:true,

   «result»:[  

      {  

         «id»:50,

         «status»:«created»

      },

      {  

         «id»:51,

         «status»:«created»

      },

      {  

         «status»:«skipped»,

         «reasons»:[  

            {  

               «code»:«1005»,

               «message»:«Lead already exists»

            }

         ]

      }

   ]

}

Records included in the result array of calls will be ordered in the same way as the input array of a request.

Each record in a successful request may succeed or fail on an individual basis which is indicated by the status field of each record included in the result array of a response.  The “status” field of these records will be “skipped” and a “reasons” array will be present.  Each reason contains a “code” member, and a “message” member.  The code will always be 1xxx, and the message will indicate why the record was skipped.  An example would be where a Sync Leads request has “action” set to “createOnly” but a lead already exists for one of the keys in the submitted records.  This case will return a code of 1005, and a message of “Lead already exists” as displayed above.

Record-Level Error Codes

Response Code Description Comment
1001 Invalid value ‘%s’. Required of type ‘%s’ Error is generated whenever parameter value has type mismatch. For example string value specified for integer parameter.
1002 Missing value for required parameter ‘%s’ Error is generated when required parameter is missing from the request
1003 Invalid data When the data submitted is not a valid type for the given endpoint or mode; such as when id is submitted for a lead with action designated as createOnly or when using Request Campaign on a batch campaign.
1004 Lead not found For syncLead, when action is “updateOnly” and if lead is not found
1005 Lead already exists For syncLead, when action is “createOnly” and if lead already exists
1006 Field ‘%s’ not found An included field in the call is not a valid field.
1007 Multiple leads match the lookup criteria Multiple leads match the lookup criteria. Updates can only be performed when the key matches a single record
1008 Access denied to partition ‘%s’ The user for the custom service does not have access to a workspace with the partition where the record exists.
1009 Partition name must be specified
1010 Partition update not allowed The specified record already exists in a separate lead partition.
1011 Field ‘%s’ not supported When lookup field or filterType specified with unsupported standard fields (ex: firstName, lastName ..etc)
1012 Invalid cookie value ‘%s’ Can  occur when calling the Associate Lead with an invalid value for cookie parameter.

Can also occur when calling Get Leads by Filter Type with filterType=cookies and invalid valid value for filterValues parameter.
1013 Object not found Get object (list, campaign ..etc) by id will return this error code
1014 Failed to create Object Failed to create Object (list, ..etc)
1015 Lead not in list The designated lead is not a member of the target list
1016 Too many imports There are too many imports queued. A maximum of 10 is allowed
1017 Object already exists Creation failed because the record already exists
1018 CRM Enabled The action could not be carried out, because the instance has a native CRM integration enabled.
1019 Import in progress The target list is already being imported to
1020 To many clone to program The subscription has reached the alotted uses of cloneToProgramName in Schedule Program for the day
1021 Company update not allowed Company update not allowed during syncLead
1022 Object in use Delete is not allowed when an object is in use by another object
1025 Program status not found A status was specified to Change Lead Program Status that did not match a status available for the program’s channel.
1026 Custom object not enabled The action could not be carried out, because the instance does not have custom objects integration enabled.
1027 Max Activity Type Limit Reached The subscription has reached the maximum number of available custom activity types.
1028 Max field limit reached Custom activities have a maximum of 20 secondary attributes.
1029
  • Too many jobs in queue
  • Export daily quota exceeded
  • Subscriptions are allowed a maximum of 10 bulk extract jobs in the queue at any given time.
  • By default extract jobs are limited to 500MB per day (resets daily at 12:00AM CST).
1035 Unsupported filter type In some subscriptions, the following Bulk Lead Extract filter types are not supported:  updatedAt, smartListId, smartListName.
1036 Duplicate object found in input A call was made to update two or more records using the same foreign key.  e.g. a Sync Companies call using the same externalCompanyId for more than one company.
1037 Lead was skipped The Lead was skipped because it is already in or past this status.
1042 Invalid runAt date The runAt date specified for Schedule Campaign was too far into the future (maximum is 2 years).
1048 Custom Object Discard Draft Failed A call was made to discard the draft version of a custom object.
1049 Failed to Create Activity Attributes array too long

The array of attributes passed to the record exceeded the max length of 65536 bytes
1076 Merge Leads call with mergeInCRM flag is true. You are creating a duplicate record. We recommend you use an existing record instead.

This is the error msg which Marketo receives when merging in Salesforce.
1077 Merge Leads call failed due to <SFDC Field> length A Merge Leads call with mergeInCRM set to true failed due to <SFDC Field> exceeding limit of allowed characters. To correct, reduce length of <SFDC Field>, or set mergeInCRM to false.
1078 Merge Leads call failed due to deleted entity, not a lead/contact, or field filter criteria doesn’t match. Merge failure, unable to perform merge operation in natively-synced CRM

This is the error msg which Marketo receives when merging in Salesforce.
Источник

General errors

0 — ERROR_NO_ERROR

No error has occurred.

1 — ERROR_FAILED

Will be raised when a general error occurred.

2 — ERROR_SYS_ERROR

Will be raised when operating system error occurred.

3 — ERROR_OUT_OF_MEMORY

Will be raised when there is a memory shortage.

4 — ERROR_INTERNAL

Will be raised when an internal error occurred.

5 — ERROR_ILLEGAL_NUMBER

Will be raised when an illegal representation of a number was given.

6 — ERROR_NUMERIC_OVERFLOW

Will be raised when a numeric overflow occurred.

7 — ERROR_ILLEGAL_OPTION

Will be raised when an unknown option was supplied by the user.

8 — ERROR_DEAD_PID

Will be raised when a PID without a living process was found.

9 — ERROR_NOT_IMPLEMENTED

Will be raised when hitting an unimplemented feature.

10 — ERROR_BAD_PARAMETER

Will be raised when the parameter does not fulfill the requirements.

11 — ERROR_FORBIDDEN

Will be raised when you are missing permission for the operation.

12 — ERROR_OUT_OF_MEMORY_MMAP

Will be raised when there is a memory shortage.

13 — ERROR_CORRUPTED_CSV

Will be raised when encountering a corrupt csv line.

14 — ERROR_FILE_NOT_FOUND

Will be raised when a file is not found.

15 — ERROR_CANNOT_WRITE_FILE

Will be raised when a file cannot be written.

16 — ERROR_CANNOT_OVERWRITE_FILE

Will be raised when an attempt is made to overwrite an existing file.

17 — ERROR_TYPE_ERROR

Will be raised when a type error is encountered.

18 — ERROR_LOCK_TIMEOUT

Will be raised when there’s a timeout waiting for a lock.

19 — ERROR_CANNOT_CREATE_DIRECTORY

Will be raised when an attempt to create a directory fails.

20 — ERROR_CANNOT_CREATE_TEMP_FILE

Will be raised when an attempt to create a temporary file fails.

21 — ERROR_REQUEST_CANCELED

Will be raised when a request is canceled by the user.

22 — ERROR_DEBUG

Will be raised intentionally during debugging.

25 — ERROR_IP_ADDRESS_INVALID

Will be raised when the structure of an IP address is invalid.

27 — ERROR_FILE_EXISTS

Will be raised when a file already exists.

28 — ERROR_LOCKED

Will be raised when a resource or an operation is locked.

29 — ERROR_DEADLOCK

Will be raised when a deadlock is detected when accessing collections.

30 — ERROR_SHUTTING_DOWN

Will be raised when a call cannot succeed because a server shutdown is already in progress.

31 — ERROR_ONLY_ENTERPRISE

Will be raised when an Enterprise Edition feature is requested from the Community Edition.

32 — ERROR_RESOURCE_LIMIT

Will be raised when the resources used by an operation exceed the configured maximum value.

33 — ERROR_ARANGO_ICU_ERROR

will be raised if ICU operations failed.

34 — ERROR_CANNOT_READ_FILE

Will be raised when a file cannot be read.

35 — ERROR_INCOMPATIBLE_VERSION

Will be raised when a server is running an incompatible version of ArangoDB.

36 — ERROR_DISABLED

Will be raised when a requested resource is not enabled.

37 — ERROR_MALFORMED_JSON

Will be raised when a JSON string could not be parsed.

38 — ERROR_STARTING_UP

Will be raised when a call cannot succeed because the server startup phase is still in progress.

39 — ERROR_DESERIALIZE

Will be raised when a data structure cannot be deserialized, e.g. because the input is invalid.

HTTP error status codes

400 — ERROR_HTTP_BAD_PARAMETER

Will be raised when the HTTP request does not fulfill the requirements.

Will be raised when authorization is required but the user is not authorized.

403 — ERROR_HTTP_FORBIDDEN

Will be raised when the operation is forbidden.

404 — ERROR_HTTP_NOT_FOUND

Will be raised when an URI is unknown.

405 — ERROR_HTTP_METHOD_NOT_ALLOWED

Will be raised when an unsupported HTTP method is used for an operation.

406 — ERROR_HTTP_NOT_ACCEPTABLE

Will be raised when an unsupported HTTP content type is used for an operation, or if a request is not acceptable for a leader or follower.

408 — ERROR_HTTP_REQUEST_TIMEOUT

Will be raised when a timeout occured.

409 — ERROR_HTTP_CONFLICT

Will be raised when a conflict occurs in an HTTP operation.

410 — ERROR_HTTP_GONE

Will be raised when the requested content has been permanently deleted.

412 — ERROR_HTTP_PRECONDITION_FAILED

Will be raised when a precondition for an HTTP request is not met.

420 — ERROR_HTTP_ENHANCE_YOUR_CALM

Will be raised when too many requests were sent to a rate-limited API.

500 — ERROR_HTTP_SERVER_ERROR

Will be raised when an internal server is encountered.

501 — ERROR_HTTP_NOT_IMPLEMENTED

Will be raised when an API is called this is not implemented in general, or not implemented for the current setup.

503 — ERROR_HTTP_SERVICE_UNAVAILABLE

Will be raised when a service is temporarily unavailable.

504 — ERROR_HTTP_GATEWAY_TIMEOUT

Will be raised when a service contacted by ArangoDB does not respond in a timely manner.

HTTP processing errors

600 — ERROR_HTTP_CORRUPTED_JSON

Will be raised when a string representation of a JSON object is corrupt.

601 — ERROR_HTTP_SUPERFLUOUS_SUFFICES

Will be raised when the URL contains superfluous suffices.

Internal ArangoDB storage errors

1000 — ERROR_ARANGO_ILLEGAL_STATE

Internal error that will be raised when the datafile is not in the required state.

1004 — ERROR_ARANGO_READ_ONLY

Internal error that will be raised when trying to write to a read-only datafile or collection.

1005 — ERROR_ARANGO_DUPLICATE_IDENTIFIER

Internal error that will be raised when a identifier duplicate is detected.

External ArangoDB storage errors

1100 — ERROR_ARANGO_CORRUPTED_DATAFILE

Will be raised when a corruption is detected in a datafile.

1101 — ERROR_ARANGO_ILLEGAL_PARAMETER_FILE

Will be raised if a parameter file is corrupted or cannot be read.

1102 — ERROR_ARANGO_CORRUPTED_COLLECTION

Will be raised when a collection contains one or more corrupted data files.

1104 — ERROR_ARANGO_FILESYSTEM_FULL

Will be raised when the filesystem is full.

1107 — ERROR_ARANGO_DATADIR_LOCKED

Will be raised when the database directory is locked by a different process.

General ArangoDB storage errors

1200 — ERROR_ARANGO_CONFLICT

Will be raised when updating or deleting a document and a conflict has been detected.

1202 — ERROR_ARANGO_DOCUMENT_NOT_FOUND

Will be raised when a document with a given identifier is unknown.

1203 — ERROR_ARANGO_DATA_SOURCE_NOT_FOUND

Will be raised when a collection or View with the given identifier or name is unknown.

1204 — ERROR_ARANGO_COLLECTION_PARAMETER_MISSING

Will be raised when the collection parameter is missing.

1205 — ERROR_ARANGO_DOCUMENT_HANDLE_BAD

Will be raised when a document identifier is corrupt.

1207 — ERROR_ARANGO_DUPLICATE_NAME

Will be raised when a name duplicate is detected.

1208 — ERROR_ARANGO_ILLEGAL_NAME

Will be raised when an illegal name is detected.

1209 — ERROR_ARANGO_NO_INDEX

Will be raised when no suitable index for the query is known.

1210 — ERROR_ARANGO_UNIQUE_CONSTRAINT_VIOLATED

Will be raised when there is a unique constraint violation.

1212 — ERROR_ARANGO_INDEX_NOT_FOUND

Will be raised when an index with a given identifier is unknown.

1213 — ERROR_ARANGO_CROSS_COLLECTION_REQUEST

Will be raised when a cross-collection is requested.

1214 — ERROR_ARANGO_INDEX_HANDLE_BAD

Will be raised when a index identifier is corrupt.

1216 — ERROR_ARANGO_DOCUMENT_TOO_LARGE

Will be raised when the document cannot fit into any datafile because of it is too large.

1217 — ERROR_ARANGO_COLLECTION_NOT_UNLOADED

Will be raised when a collection should be unloaded, but has a different status.

1218 — ERROR_ARANGO_COLLECTION_TYPE_INVALID

Will be raised when an invalid collection type is used in a request.

1220 — ERROR_ARANGO_ATTRIBUTE_PARSER_FAILED

Will be raised when parsing an attribute name definition failed.

1221 — ERROR_ARANGO_DOCUMENT_KEY_BAD

Will be raised when a document key is corrupt.

1222 — ERROR_ARANGO_DOCUMENT_KEY_UNEXPECTED

Will be raised when a user-defined document key is supplied for collections with auto key generation.

1224 — ERROR_ARANGO_DATADIR_NOT_WRITABLE

Will be raised when the server’s database directory is not writable for the current user.

1225 — ERROR_ARANGO_OUT_OF_KEYS

Will be raised when a key generator runs out of keys.

1226 — ERROR_ARANGO_DOCUMENT_KEY_MISSING

Will be raised when a document key is missing.

1227 — ERROR_ARANGO_DOCUMENT_TYPE_INVALID

Will be raised when there is an attempt to create a document with an invalid type.

1228 — ERROR_ARANGO_DATABASE_NOT_FOUND

Will be raised when a non-existing database is accessed.

1229 — ERROR_ARANGO_DATABASE_NAME_INVALID

Will be raised when an invalid database name is used.

1230 — ERROR_ARANGO_USE_SYSTEM_DATABASE

Will be raised when an operation is requested in a database other than the system database.

1232 — ERROR_ARANGO_INVALID_KEY_GENERATOR

Will be raised when an invalid key generator description is used.

1233 — ERROR_ARANGO_INVALID_EDGE_ATTRIBUTE

will be raised when the _from or _to values of an edge are undefined or contain an invalid value.

1235 — ERROR_ARANGO_INDEX_CREATION_FAILED

Will be raised when an attempt to create an index has failed.

1237 — ERROR_ARANGO_COLLECTION_TYPE_MISMATCH

Will be raised when a collection has a different type from what has been expected.

1238 — ERROR_ARANGO_COLLECTION_NOT_LOADED

Will be raised when a collection is accessed that is not yet loaded.

1239 — ERROR_ARANGO_DOCUMENT_REV_BAD

Will be raised when a document revision is corrupt or is missing where needed.

1240 — ERROR_ARANGO_INCOMPLETE_READ

Will be raised by the storage engine when a read cannot be completed.

1241 — ERROR_ARANGO_OLD_ROCKSDB_FORMAT

Will be raised by the storage engine when an operation cannot be performed because the old, deprecated, little endian key encoding format is still used and an operation is tried which is not supported by this format.

Checked ArangoDB storage errors

1301 — ERROR_ARANGO_EMPTY_DATADIR

Will be raised when encountering an empty server database directory.

1302 — ERROR_ARANGO_TRY_AGAIN

Will be raised when an operation should be retried.

1303 — ERROR_ARANGO_BUSY

Will be raised when storage engine is busy.

1304 — ERROR_ARANGO_MERGE_IN_PROGRESS

Will be raised when storage engine has a datafile merge in progress and cannot complete the operation.

1305 — ERROR_ARANGO_IO_ERROR

Will be raised when storage engine encounters an I/O error.

ArangoDB replication errors

1400 — ERROR_REPLICATION_NO_RESPONSE

Will be raised when the replication applier does not receive any or an incomplete response from the leader.

1401 — ERROR_REPLICATION_INVALID_RESPONSE

Will be raised when the replication applier receives an invalid response from the leader.

1402 — ERROR_REPLICATION_LEADER_ERROR

Will be raised when the replication applier receives a server error from the leader.

1403 — ERROR_REPLICATION_LEADER_INCOMPATIBLE

Will be raised when the replication applier connects to a leader that has an incompatible version.

1404 — ERROR_REPLICATION_LEADER_CHANGE

Will be raised when the replication applier connects to a different leader than before.

1405 — ERROR_REPLICATION_LOOP

Will be raised when the replication applier is asked to connect to itself for replication.

1406 — ERROR_REPLICATION_UNEXPECTED_MARKER

Will be raised when an unexpected marker is found in the replication log stream.

1407 — ERROR_REPLICATION_INVALID_APPLIER_STATE

Will be raised when an invalid replication applier state file is found.

1408 — ERROR_REPLICATION_UNEXPECTED_TRANSACTION

Will be raised when an unexpected transaction id is found.

1409 — ERROR_REPLICATION_SHARD_SYNC_ATTEMPT_TIMEOUT_EXCEEDED

Will be raised when the synchronization of a shard takes longer than the configured timeout.

1410 — ERROR_REPLICATION_INVALID_APPLIER_CONFIGURATION

Will be raised when the configuration for the replication applier is invalid.

1411 — ERROR_REPLICATION_RUNNING

Will be raised when there is an attempt to perform an operation while the replication applier is running.

1412 — ERROR_REPLICATION_APPLIER_STOPPED

Special error code used to indicate the replication applier was stopped by a user.

1413 — ERROR_REPLICATION_NO_START_TICK

Will be raised when the replication applier is started without a known start tick value.

1414 — ERROR_REPLICATION_START_TICK_NOT_PRESENT

Will be raised when the replication applier fetches data using a start tick, but that start tick is not present on the logger server anymore.

1416 — ERROR_REPLICATION_WRONG_CHECKSUM

Will be raised when a new born follower submits a wrong checksum

1417 — ERROR_REPLICATION_SHARD_NONEMPTY

Will be raised when a shard is not empty and the follower tries a shortcut

1418 — ERROR_REPLICATION_REPLICATED_LOG_NOT_FOUND

Will be raised when a specific replicated log is not found

1419 — ERROR_REPLICATION_REPLICATED_LOG_NOT_THE_LEADER

Will be raised when a participant of a replicated log is ordered to do something only the leader can do

1420 — ERROR_REPLICATION_REPLICATED_LOG_NOT_A_FOLLOWER

Will be raised when a participant of a replicated log is ordered to do something only a follower can do

1421 — ERROR_REPLICATION_REPLICATED_LOG_APPEND_ENTRIES_REJECTED

Will be raised when a follower of a replicated log rejects an append entries request

1422 — ERROR_REPLICATION_REPLICATED_LOG_LEADER_RESIGNED

Will be raised when a leader instance of a replicated log rejects a request because it just resigned. This can also happen if the term changes (due to a configuration change), even if the leader stays the same.

1423 — ERROR_REPLICATION_REPLICATED_LOG_FOLLOWER_RESIGNED

Will be raised when a follower instance of a replicated log rejects a request because it just resigned. This can also happen if the term changes (due to a configuration change), even if the server stays a follower.

1424 — ERROR_REPLICATION_REPLICATED_LOG_PARTICIPANT_GONE

Will be raised when a participant instance of a replicated log is no longer available.

1425 — ERROR_REPLICATION_REPLICATED_LOG_INVALID_TERM

Will be raised when a participant tries to change its term but found a invalid new term.

1426 — ERROR_REPLICATION_REPLICATED_LOG_UNCONFIGURED

Will be raised when a participant is currently unconfigured, i.e. neither a leader nor a follower.

1427 — ERROR_REPLICATION_REPLICATED_STATE_NOT_FOUND

Will be raised when a specific replicated state was not found.

1428 — ERROR_REPLICATION_REPLICATED_STATE_NOT_AVAILABLE

Will be raised when a specific replicated state was accessed but is not (yet) available.

1429 — ERROR_REPLICATION_WRITE_CONCERN_NOT_FULFILLED

Will be raised when there are not enough replicas of a shard available to fulfill the write-concern for a write operation.

ArangoDB cluster errors

1446 — ERROR_CLUSTER_NOT_FOLLOWER

Will be raised when an operation is sent to a non-following server.

1447 — ERROR_CLUSTER_FOLLOWER_TRANSACTION_COMMIT_PERFORMED

Will be raised when a follower transaction has already performed an intermediate commit and must be rolled back.

1448 — ERROR_CLUSTER_CREATE_COLLECTION_PRECONDITION_FAILED

Will be raised when updating the plan on collection creation failed.

1449 — ERROR_CLUSTER_SERVER_UNKNOWN

Will be raised on some occasions when one server gets a request from another, which has not (yet?) been made known via the Agency.

1450 — ERROR_CLUSTER_TOO_MANY_SHARDS

Will be raised when the number of shards for a collection is higher than allowed.

1454 — ERROR_CLUSTER_COULD_NOT_CREATE_COLLECTION_IN_PLAN

Will be raised when a Coordinator in a cluster cannot create an entry for a new collection in the Plan hierarchy in the Agency.

1456 — ERROR_CLUSTER_COULD_NOT_CREATE_COLLECTION

Will be raised when a Coordinator in a cluster notices that some DB-Servers report problems when creating shards for a new collection.

1457 — ERROR_CLUSTER_TIMEOUT

Will be raised when a Coordinator in a cluster runs into a timeout for some cluster wide operation.

1458 — ERROR_CLUSTER_COULD_NOT_REMOVE_COLLECTION_IN_PLAN

Will be raised when a Coordinator in a cluster cannot remove an entry for a collection in the Plan hierarchy in the Agency.

1460 — ERROR_CLUSTER_COULD_NOT_CREATE_DATABASE_IN_PLAN

Will be raised when a Coordinator in a cluster cannot create an entry for a new database in the Plan hierarchy in the Agency.

1461 — ERROR_CLUSTER_COULD_NOT_CREATE_DATABASE

Will be raised when a Coordinator in a cluster notices that some DB-Servers report problems when creating databases for a new cluster wide database.

1462 — ERROR_CLUSTER_COULD_NOT_REMOVE_DATABASE_IN_PLAN

Will be raised when a Coordinator in a cluster cannot remove an entry for a database in the Plan hierarchy in the Agency.

1463 — ERROR_CLUSTER_COULD_NOT_REMOVE_DATABASE_IN_CURRENT

Will be raised when a Coordinator in a cluster cannot remove an entry for a database in the Current hierarchy in the Agency.

1464 — ERROR_CLUSTER_SHARD_GONE

Will be raised when a Coordinator in a cluster cannot determine the shard that is responsible for a given document.

1465 — ERROR_CLUSTER_CONNECTION_LOST

Will be raised when a Coordinator in a cluster loses an HTTP connection to a DB-Server in the cluster whilst transferring data.

1466 — ERROR_CLUSTER_MUST_NOT_SPECIFY_KEY

Will be raised when a Coordinator in a cluster finds that the _key attribute was specified in a sharded collection the uses not only _key as sharding attribute.

1467 — ERROR_CLUSTER_GOT_CONTRADICTING_ANSWERS

Will be raised if a Coordinator in a cluster gets conflicting results from different shards, which should never happen.

1468 — ERROR_CLUSTER_NOT_ALL_SHARDING_ATTRIBUTES_GIVEN

Will be raised if a Coordinator tries to find out which shard is responsible for a partial document, but cannot do this because not all sharding attributes are specified.

1469 — ERROR_CLUSTER_MUST_NOT_CHANGE_SHARDING_ATTRIBUTES

Will be raised if there is an attempt to update the value of a shard attribute.

1470 — ERROR_CLUSTER_UNSUPPORTED

Will be raised when there is an attempt to carry out an operation that is not supported in the context of a sharded collection.

1471 — ERROR_CLUSTER_ONLY_ON_COORDINATOR

Will be raised if there is an attempt to run a Coordinator-only operation on a different type of node.

1472 — ERROR_CLUSTER_READING_PLAN_AGENCY

Will be raised if a Coordinator or DB-Server cannot read the Plan in the Agency.

1473 — ERROR_CLUSTER_COULD_NOT_TRUNCATE_COLLECTION

Will be raised if a Coordinator cannot truncate all shards of a cluster collection.

1474 — ERROR_CLUSTER_AQL_COMMUNICATION

Will be raised if the internal communication of the cluster for AQL produces an error.

1477 — ERROR_CLUSTER_ONLY_ON_DBSERVER

Will be raised if there is an attempt to run a DB-Server-only operation on a different type of node.

1478 — ERROR_CLUSTER_BACKEND_UNAVAILABLE

Will be raised if a required DB-Server can’t be reached.

1481 — ERROR_CLUSTER_AQL_COLLECTION_OUT_OF_SYNC

Will be raised if a collection/view needed during query execution is out of sync. This currently can happen when using SatelliteCollections, Arangosearch links or inverted indexes.

1482 — ERROR_CLUSTER_COULD_NOT_CREATE_INDEX_IN_PLAN

Will be raised when a Coordinator in a cluster cannot create an entry for a new index in the Plan hierarchy in the Agency.

1483 — ERROR_CLUSTER_COULD_NOT_DROP_INDEX_IN_PLAN

Will be raised when a Coordinator in a cluster cannot remove an index from the Plan hierarchy in the Agency.

1484 — ERROR_CLUSTER_CHAIN_OF_DISTRIBUTESHARDSLIKE

Will be raised if one tries to create a collection with a distributeShardsLike attribute which points to another collection that also has one.

1485 — ERROR_CLUSTER_MUST_NOT_DROP_COLL_OTHER_DISTRIBUTESHARDSLIKE

Will be raised if one tries to drop a collection to which another collection points with its distributeShardsLike attribute.

1486 — ERROR_CLUSTER_UNKNOWN_DISTRIBUTESHARDSLIKE

Will be raised if one tries to create a collection which points to an unknown collection in its distributeShardsLike attribute.

1487 — ERROR_CLUSTER_INSUFFICIENT_DBSERVERS

Will be raised if one tries to create a collection with a replicationFactor greater than the available number of DB-Servers.

1488 — ERROR_CLUSTER_COULD_NOT_DROP_FOLLOWER

Will be raised if a follower that ought to be dropped could not be dropped in the Agency (under Current).

1489 — ERROR_CLUSTER_SHARD_LEADER_REFUSES_REPLICATION

Will be raised if a replication operation is refused by a shard leader.

1490 — ERROR_CLUSTER_SHARD_FOLLOWER_REFUSES_OPERATION

Will be raised if a replication operation is refused by a shard follower because it is coming from the wrong leader.

1491 — ERROR_CLUSTER_SHARD_LEADER_RESIGNED

Will be raised if a non-replication operation is refused by a former shard leader that has found out that it is no longer the leader.

1492 — ERROR_CLUSTER_AGENCY_COMMUNICATION_FAILED

Will be raised if after various retries an Agency operation could not be performed successfully.

1495 — ERROR_CLUSTER_LEADERSHIP_CHALLENGE_ONGOING

Will be raised when servers are currently competing for leadership, and the result is still unknown.

1496 — ERROR_CLUSTER_NOT_LEADER

Will be raised when an operation is sent to a non-leading server.

1497 — ERROR_CLUSTER_COULD_NOT_CREATE_VIEW_IN_PLAN

Will be raised when a Coordinator in a cluster cannot create an entry for a new View in the Plan hierarchy in the Agency.

1498 — ERROR_CLUSTER_VIEW_ID_EXISTS

Will be raised when a Coordinator in a cluster tries to create a View and the View ID already exists.

1499 — ERROR_CLUSTER_COULD_NOT_DROP_COLLECTION

Will be raised when a Coordinator in a cluster cannot drop a collection entry in the Plan hierarchy in the Agency.

ArangoDB query errors

1500 — ERROR_QUERY_KILLED

Will be raised when a running query is killed by an explicit admin command.

1501 — ERROR_QUERY_PARSE

Will be raised when query is parsed and is found to be syntactically invalid.

1502 — ERROR_QUERY_EMPTY

Will be raised when an empty query is specified.

1503 — ERROR_QUERY_SCRIPT

Will be raised when a runtime error is caused by the query.

1504 — ERROR_QUERY_NUMBER_OUT_OF_RANGE

Will be raised when a number is outside the expected range.

1505 — ERROR_QUERY_INVALID_GEO_VALUE

Will be raised when a geo index coordinate is invalid or out of range.

1510 — ERROR_QUERY_VARIABLE_NAME_INVALID

Will be raised when an invalid variable name is used.

1511 — ERROR_QUERY_VARIABLE_REDECLARED

Will be raised when a variable gets re-assigned in a query.

1512 — ERROR_QUERY_VARIABLE_NAME_UNKNOWN

Will be raised when an unknown variable is used or the variable is undefined the context it is used.

1521 — ERROR_QUERY_COLLECTION_LOCK_FAILED

Will be raised when a read lock on the collection cannot be acquired.

1522 — ERROR_QUERY_TOO_MANY_COLLECTIONS

Will be raised when the number of collections or shards in a query is beyond the allowed value.

1524 — ERROR_QUERY_TOO_MUCH_NESTING

Will be raised when a query contains expressions or other constructs with too many objects or that are too deeply nested.

1539 — ERROR_QUERY_INVALID_OPTIONS_ATTRIBUTE

Will be raised when an unknown attribute is used inside an OPTIONS clause.

1540 — ERROR_QUERY_FUNCTION_NAME_UNKNOWN

Will be raised when an undefined function is called.

1541 — ERROR_QUERY_FUNCTION_ARGUMENT_NUMBER_MISMATCH

Will be raised when the number of arguments used in a function call does not match the expected number of arguments for the function.

1542 — ERROR_QUERY_FUNCTION_ARGUMENT_TYPE_MISMATCH

Will be raised when the type of an argument used in a function call does not match the expected argument type.

1543 — ERROR_QUERY_INVALID_REGEX

Will be raised when an invalid regex argument value is used in a call to a function that expects a regex.

1550 — ERROR_QUERY_BIND_PARAMETERS_INVALID

Will be raised when the structure of bind parameters passed has an unexpected format.

1551 — ERROR_QUERY_BIND_PARAMETER_MISSING

Will be raised when a bind parameter was declared in the query but the query is being executed with no value for that parameter.

1552 — ERROR_QUERY_BIND_PARAMETER_UNDECLARED

Will be raised when a value gets specified for an undeclared bind parameter.

1553 — ERROR_QUERY_BIND_PARAMETER_TYPE

Will be raised when a bind parameter has an invalid value or type.

1561 — ERROR_QUERY_INVALID_ARITHMETIC_VALUE

Will be raised when a non-numeric value is used in an arithmetic operation.

1562 — ERROR_QUERY_DIVISION_BY_ZERO

Will be raised when there is an attempt to divide by zero.

1563 — ERROR_QUERY_ARRAY_EXPECTED

Will be raised when a non-array operand is used for an operation that expects an array argument operand.

1568 — ERROR_QUERY_COLLECTION_USED_IN_EXPRESSION

Will be raised when a collection is used as an operand in an AQL expression.

1569 — ERROR_QUERY_FAIL_CALLED

Will be raised when the function FAIL() is called from inside a query.

1570 — ERROR_QUERY_GEO_INDEX_MISSING

Will be raised when a geo restriction was specified but no suitable geo index is found to resolve it.

1571 — ERROR_QUERY_FULLTEXT_INDEX_MISSING

Will be raised when a fulltext query is performed on a collection without a suitable fulltext index.

1572 — ERROR_QUERY_INVALID_DATE_VALUE

Will be raised when a value cannot be converted to a date.

1573 — ERROR_QUERY_MULTI_MODIFY

Will be raised when an AQL query contains more than one data-modifying operation.

1574 — ERROR_QUERY_INVALID_AGGREGATE_EXPRESSION

Will be raised when an AQL query contains an invalid aggregate expression.

1575 — ERROR_QUERY_COMPILE_TIME_OPTIONS

Will be raised when an AQL query contains OPTIONS that cannot be figured out at query compile time.

1576 — ERROR_QUERY_DNF_COMPLEXITY

Will be raised internally when a too complex FILTER/PRUNE condition is encountered during the DNF conversion of the condition.

1577 — ERROR_QUERY_FORCED_INDEX_HINT_UNUSABLE

Will be raised when forceIndexHint is specified, and the hint cannot be used to serve the query.

1578 — ERROR_QUERY_DISALLOWED_DYNAMIC_CALL

Will be raised when a dynamic function call is made to a function that cannot be called dynamically.

1579 — ERROR_QUERY_ACCESS_AFTER_MODIFICATION

Will be raised when collection data are accessed after a data-modification operation.

AQL user function errors

1580 — ERROR_QUERY_FUNCTION_INVALID_NAME

Will be raised when a user function with an invalid name is registered.

1581 — ERROR_QUERY_FUNCTION_INVALID_CODE

Will be raised when a user function is registered with invalid code.

1582 — ERROR_QUERY_FUNCTION_NOT_FOUND

Will be raised when a user function is accessed but not found.

1583 — ERROR_QUERY_FUNCTION_RUNTIME_ERROR

Will be raised when a user function throws a runtime exception.

AQL query registry errors

1590 — ERROR_QUERY_BAD_JSON_PLAN

Will be raised when an HTTP API for a query got an invalid JSON object.

1591 — ERROR_QUERY_NOT_FOUND

Will be raised when an Id of a query is not found by the HTTP API.

1593 — ERROR_QUERY_USER_ASSERT

Will be raised if and user provided expression fails to evaluate to true

1594 — ERROR_QUERY_USER_WARN

Will be raised if and user provided expression fails to evaluate to true

1595 — ERROR_QUERY_WINDOW_AFTER_MODIFICATION

Will be raised when a window node is created after a data-modification operation.

ArangoDB cursor errors

1600 — ERROR_CURSOR_NOT_FOUND

Will be raised when a cursor is requested via its id but a cursor with that id cannot be found.

1601 — ERROR_CURSOR_BUSY

Will be raised when a cursor is requested via its id but a concurrent request is still using the cursor.

ArangoDB schema validation errors

1620 — ERROR_VALIDATION_FAILED

Will be raised when a document does not pass schema validation.

1621 — ERROR_VALIDATION_BAD_PARAMETER

Will be raised when the schema description is invalid.

ArangoDB transaction errors

1650 — ERROR_TRANSACTION_INTERNAL

Will be raised when a wrong usage of transactions is detected. this is an internal error and indicates a bug in ArangoDB.

1651 — ERROR_TRANSACTION_NESTED

Will be raised when transactions are nested.

1652 — ERROR_TRANSACTION_UNREGISTERED_COLLECTION

Will be raised when a collection is used in the middle of a transaction but was not registered at transaction start.

1653 — ERROR_TRANSACTION_DISALLOWED_OPERATION

Will be raised when a disallowed operation is carried out in a transaction.

1654 — ERROR_TRANSACTION_ABORTED

Will be raised when a transaction was aborted.

1655 — ERROR_TRANSACTION_NOT_FOUND

Will be raised when a transaction was not found.

User management errors

1700 — ERROR_USER_INVALID_NAME

Will be raised when an invalid user name is used.

1702 — ERROR_USER_DUPLICATE

Will be raised when a user name already exists.

1703 — ERROR_USER_NOT_FOUND

Will be raised when a user name is updated that does not exist.

1705 — ERROR_USER_EXTERNAL

Will be raised when the user is authenticated by an external server.

Service management errors (legacy)

1752 — ERROR_SERVICE_DOWNLOAD_FAILED

Will be raised when a service download from the central repository failed.

1753 — ERROR_SERVICE_UPLOAD_FAILED

Will be raised when a service upload from the client to the ArangoDB server failed.

LDAP errors

1800 — ERROR_LDAP_CANNOT_INIT

can not init a LDAP connection

1801 — ERROR_LDAP_CANNOT_SET_OPTION

can not set a LDAP option

1802 — ERROR_LDAP_CANNOT_BIND

can not bind to a LDAP server

1803 — ERROR_LDAP_CANNOT_UNBIND

can not unbind from a LDAP server

1804 — ERROR_LDAP_CANNOT_SEARCH

can not search the LDAP server

1805 — ERROR_LDAP_CANNOT_START_TLS

can not star a TLS LDAP session

1806 — ERROR_LDAP_FOUND_NO_OBJECTS

LDAP didn’t found any objects with the specified search query

1807 — ERROR_LDAP_NOT_ONE_USER_FOUND

LDAP found zero ore more than one user

1808 — ERROR_LDAP_USER_NOT_IDENTIFIED

LDAP found a user, but its not the desired one

1809 — ERROR_LDAP_OPERATIONS_ERROR

LDAP returned an operations error

1820 — ERROR_LDAP_INVALID_MODE

cant distinguish a valid mode for provided LDAP configuration

Task errors

1850 — ERROR_TASK_INVALID_ID

Will be raised when a task is created with an invalid id.

1851 — ERROR_TASK_DUPLICATE_ID

Will be raised when a task id is created with a duplicate id.

1852 — ERROR_TASK_NOT_FOUND

Will be raised when a task with the specified id could not be found.

Graph / traversal errors

1901 — ERROR_GRAPH_INVALID_GRAPH

Will be raised when an invalid name is passed to the server.

1906 — ERROR_GRAPH_INVALID_EDGE

Will be raised when an invalid edge id is passed to the server.

1909 — ERROR_GRAPH_TOO_MANY_ITERATIONS

Will be raised when too many iterations are done in a graph traversal.

1910 — ERROR_GRAPH_INVALID_FILTER_RESULT

Will be raised when an invalid filter result is returned in a graph traversal.

1920 — ERROR_GRAPH_COLLECTION_MULTI_USE

an edge collection may only be used once in one edge definition of a graph.

1921 — ERROR_GRAPH_COLLECTION_USE_IN_MULTI_GRAPHS

is already used by another graph in a different edge definition.

1922 — ERROR_GRAPH_CREATE_MISSING_NAME

a graph name is required to create or drop a graph.

1923 — ERROR_GRAPH_CREATE_MALFORMED_EDGE_DEFINITION

the edge definition is malformed. It has to be an array of objects.

1924 — ERROR_GRAPH_NOT_FOUND

a graph with this name could not be found.

1925 — ERROR_GRAPH_DUPLICATE

a graph with this name already exists.

1926 — ERROR_GRAPH_VERTEX_COL_DOES_NOT_EXIST

the specified vertex collection does not exist or is not part of the graph.

1927 — ERROR_GRAPH_WRONG_COLLECTION_TYPE_VERTEX

the collection is not a vertex collection.

1928 — ERROR_GRAPH_NOT_IN_ORPHAN_COLLECTION

Vertex collection not in list of orphan collections of the graph.

1929 — ERROR_GRAPH_COLLECTION_USED_IN_EDGE_DEF

The collection is already used in an edge definition of the graph.

1930 — ERROR_GRAPH_EDGE_COLLECTION_NOT_USED

The edge collection is not used in any edge definition of the graph.

1932 — ERROR_GRAPH_NO_GRAPH_COLLECTION

collection _graphs does not exist.

1935 — ERROR_GRAPH_INVALID_NUMBER_OF_ARGUMENTS

Invalid number of arguments. Expected:

1936 — ERROR_GRAPH_INVALID_PARAMETER

Invalid parameter type.

1938 — ERROR_GRAPH_COLLECTION_USED_IN_ORPHANS

The collection is already used in the orphans of the graph.

1939 — ERROR_GRAPH_EDGE_COL_DOES_NOT_EXIST

the specified edge collection does not exist or is not part of the graph.

1940 — ERROR_GRAPH_EMPTY

The requested graph has no edge collections.

1941 — ERROR_GRAPH_INTERNAL_DATA_CORRUPT

The _graphs collection contains invalid data.

1943 — ERROR_GRAPH_CREATE_MALFORMED_ORPHAN_LIST

the orphan list argument is malformed. It has to be an array of strings.

1944 — ERROR_GRAPH_EDGE_DEFINITION_IS_DOCUMENT

the collection used as a relation is existing, but is a document collection, it cannot be used here.

1945 — ERROR_GRAPH_COLLECTION_IS_INITIAL

the collection is used as the initial collection of this graph and is not allowed to be removed manually.

1946 — ERROR_GRAPH_NO_INITIAL_COLLECTION

during the graph creation process no collection could be selected as the needed initial collection. Happens if a distributeShardsLike or replicationFactor mismatch was found.

1947 — ERROR_GRAPH_REFERENCED_VERTEX_COLLECTION_NOT_USED

the _from or _to collection specified for the edge refers to a vertex collection which is not used in any edge definition of the graph.

1948 — ERROR_GRAPH_NEGATIVE_EDGE_WEIGHT

a negative edge weight was found during a weighted graph traversal or shortest path query

Session errors

1950 — ERROR_SESSION_UNKNOWN

Will be raised when an invalid/unknown session id is passed to the server.

1951 — ERROR_SESSION_EXPIRED

Will be raised when a session is expired.

Simple Client errors

2000 — ERROR_SIMPLE_CLIENT_UNKNOWN_ERROR

This error should not happen.

2001 — ERROR_SIMPLE_CLIENT_COULD_NOT_CONNECT

Will be raised when the client could not connect to the server.

2002 — ERROR_SIMPLE_CLIENT_COULD_NOT_WRITE

Will be raised when the client could not write data.

2003 — ERROR_SIMPLE_CLIENT_COULD_NOT_READ

Will be raised when the client could not read data.

2019 — ERROR_WAS_ERLAUBE

Will be raised if was erlaube?!

internal AQL errors

2200 — ERROR_INTERNAL_AQL

Internal error during AQL execution

2201 — ERROR_WROTE_TOO_FEW_OUTPUT_REGISTERS

An AQL block wrote too few output registers

2202 — ERROR_WROTE_TOO_MANY_OUTPUT_REGISTERS

An AQL block wrote too many output registers

2203 — ERROR_WROTE_OUTPUT_REGISTER_TWICE

An AQL block wrote an output register twice

2204 — ERROR_WROTE_IN_WRONG_REGISTER

An AQL block wrote in a register that is not its output

2205 — ERROR_INPUT_REGISTERS_NOT_COPIED

An AQL block did not copy its input registers

Foxx management errors

3000 — ERROR_MALFORMED_MANIFEST_FILE

The service manifest file is not well-formed JSON.

3001 — ERROR_INVALID_SERVICE_MANIFEST

The service manifest contains invalid values.

3002 — ERROR_SERVICE_FILES_MISSING

The service folder or bundle does not exist on this server.

3003 — ERROR_SERVICE_FILES_OUTDATED

The local service bundle does not match the checksum in the database.

3004 — ERROR_INVALID_FOXX_OPTIONS

The service options contain invalid values.

3007 — ERROR_INVALID_MOUNTPOINT

The service mountpath contains invalid characters.

3009 — ERROR_SERVICE_NOT_FOUND

No service found at the given mountpath.

3010 — ERROR_SERVICE_NEEDS_CONFIGURATION

The service is missing configuration or dependencies.

3011 — ERROR_SERVICE_MOUNTPOINT_CONFLICT

A service already exists at the given mountpath.

3012 — ERROR_SERVICE_MANIFEST_NOT_FOUND

The service directory does not contain a manifest file.

3013 — ERROR_SERVICE_OPTIONS_MALFORMED

The service options are not well-formed JSON.

3014 — ERROR_SERVICE_SOURCE_NOT_FOUND

The source path does not match a file or directory.

3015 — ERROR_SERVICE_SOURCE_ERROR

The source path could not be resolved.

3016 — ERROR_SERVICE_UNKNOWN_SCRIPT

The service does not have a script with this name.

3099 — ERROR_SERVICE_API_DISABLED

The API for managing Foxx services has been disabled on this server.

JavaScript module loader errors

3100 — ERROR_MODULE_NOT_FOUND

The module path could not be resolved.

3101 — ERROR_MODULE_SYNTAX_ERROR

The module could not be parsed because of a syntax error.

3103 — ERROR_MODULE_FAILURE

Failed to invoke the module in its context.

Enterprise Edition errors

4000 — ERROR_NO_SMART_COLLECTION

The requested collection needs to be smart, but it isn’t.

4001 — ERROR_NO_SMART_GRAPH_ATTRIBUTE

The given document does not have the SmartGraph attribute set.

4002 — ERROR_CANNOT_DROP_SMART_COLLECTION

This smart collection cannot be dropped, it dictates sharding in the graph.

4003 — ERROR_KEY_MUST_BE_PREFIXED_WITH_SMART_GRAPH_ATTRIBUTE

In a smart vertex collection _key must be prefixed with the value of the SmartGraph attribute.

4004 — ERROR_ILLEGAL_SMART_GRAPH_ATTRIBUTE

The given smartGraph attribute is illegal and cannot be used for sharding. All system attributes are forbidden.

4005 — ERROR_SMART_GRAPH_ATTRIBUTE_MISMATCH

The SmartGraph attribute of the given collection does not match the SmartGraph attribute of the graph.

4006 — ERROR_INVALID_SMART_JOIN_ATTRIBUTE

Will be raised when the smartJoinAttribute declaration is invalid.

4007 — ERROR_KEY_MUST_BE_PREFIXED_WITH_SMART_JOIN_ATTRIBUTE

when using smartJoinAttribute for a collection, the shard key value must be prefixed with the value of the SmartJoin attribute.

4008 — ERROR_NO_SMART_JOIN_ATTRIBUTE

The given document does not have the required SmartJoin attribute set or it has an invalid value.

4009 — ERROR_CLUSTER_MUST_NOT_CHANGE_SMART_JOIN_ATTRIBUTE

Will be raised if there is an attempt to update the value of the smartJoinAttribute.

4010 — ERROR_INVALID_DISJOINT_SMART_EDGE

Will be raised if there is an attempt to create an edge between separated graph components.

4011 — ERROR_UNSUPPORTED_CHANGE_IN_SMART_TO_SATELLITE_DISJOINT_EDGE_DIRECTION

Switching back and forth between Satellite and Smart in Disjoint SmartGraph is not supported within a single AQL statement. Split into multiple statements.

Agency errors

20001 — ERROR_AGENCY_MALFORMED_GOSSIP_MESSAGE

Malformed gossip message.

20002 — ERROR_AGENCY_MALFORMED_INQUIRE_REQUEST

Malformed inquire request.

20011 — ERROR_AGENCY_INFORM_MUST_BE_OBJECT

The inform message in the Agency must be an object.

20012 — ERROR_AGENCY_INFORM_MUST_CONTAIN_TERM

The inform message in the Agency must contain a uint parameter ‘term’.

20013 — ERROR_AGENCY_INFORM_MUST_CONTAIN_ID

The inform message in the Agency must contain a string parameter ‘id’.

20014 — ERROR_AGENCY_INFORM_MUST_CONTAIN_ACTIVE

The inform message in the Agency must contain an array ‘active’.

20015 — ERROR_AGENCY_INFORM_MUST_CONTAIN_POOL

The inform message in the Agency must contain an object ‘pool’.

20016 — ERROR_AGENCY_INFORM_MUST_CONTAIN_MIN_PING

The inform message in the Agency must contain an object ‘min ping’.

20017 — ERROR_AGENCY_INFORM_MUST_CONTAIN_MAX_PING

The inform message in the Agency must contain an object ‘max ping’.

20018 — ERROR_AGENCY_INFORM_MUST_CONTAIN_TIMEOUT_MULT

The inform message in the Agency must contain an object ‘timeoutMult’.

20021 — ERROR_AGENCY_CANNOT_REBUILD_DBS

Will be raised if the readDB or the spearHead cannot be rebuilt from the replicated log.

20030 — ERROR_AGENCY_MALFORMED_TRANSACTION

Malformed agency transaction.

Supervision errors

20501 — ERROR_SUPERVISION_GENERAL_FAILURE

General supervision failure.

Scheduler errors

21003 — ERROR_QUEUE_FULL

Will be returned if the scheduler queue is full.

21004 — ERROR_QUEUE_TIME_REQUIREMENT_VIOLATED

Will be returned if a request with a queue time requirement is set and it cannot be fulfilled.

Maintenance errors

6002 — ERROR_ACTION_OPERATION_UNABORTABLE

This maintenance action cannot be stopped once it is started

6003 — ERROR_ACTION_UNFINISHED

This maintenance action is still processing

Backup/Restore errors

7001 — ERROR_HOT_BACKUP_INTERNAL

Failed to create hot backup set

7002 — ERROR_HOT_RESTORE_INTERNAL

Failed to restore to hot backup set

7003 — ERROR_BACKUP_TOPOLOGY

The hot backup set cannot be restored on non matching cluster topology

7004 — ERROR_NO_SPACE_LEFT_ON_DEVICE

No space left on device

7005 — ERROR_FAILED_TO_UPLOAD_BACKUP

Failed to upload hot backup set to remote target

7006 — ERROR_FAILED_TO_DOWNLOAD_BACKUP

Failed to download hot backup set from remote source

7007 — ERROR_NO_SUCH_HOT_BACKUP

Cannot find a hot backup set with this Id

7008 — ERROR_REMOTE_REPOSITORY_CONFIG_BAD

The configuration given for upload or download operation to/from remote hot backup repositories is wrong.

7009 — ERROR_LOCAL_LOCK_FAILED

Some of the DB-Servers cannot be reached for transaction locks.

7010 — ERROR_LOCAL_LOCK_RETRY

Some of the DB-Servers cannot be reached for transaction locks.

7011 — ERROR_HOT_BACKUP_CONFLICT

Conflict of multiple hot backup processes.

7012 — ERROR_HOT_BACKUP_DBSERVERS_AWOL

One or more DB-Servers could not be reached for hot backup inquiry

Plan Analyzers errors

7021 — ERROR_CLUSTER_COULD_NOT_MODIFY_ANALYZERS_IN_PLAN

Plan could not be modified while creating or deleting Analyzers revision

Licensing

9001 — ERROR_LICENSE_EXPIRED_OR_INVALID

The license has expired or is invalid.

9002 — ERROR_LICENSE_SIGNATURE_VERIFICATION

Verification of license failed.

9003 — ERROR_LICENSE_NON_MATCHING_ID

The ID of the license does not match the ID of this instance.

9004 — ERROR_LICENSE_FEATURE_NOT_ENABLED

The installed license does not cover this feature.

9005 — ERROR_LICENSE_RESOURCE_EXHAUSTED

The installed license does not cover a higher number of this resource.

9006 — ERROR_LICENSE_INVALID

The license does not hold features of an ArangoDB license.

9007 — ERROR_LICENSE_CONFLICT

The license has one or more inferior features.

9008 — ERROR_LICENSE_VALIDATION_FAILED

Could not verify the license’s signature.

Источник

Я пытаюсь получить доступ к веб-сайту с помощью GSM-модуля sim900. Это список команд

AT+CSQ      
+CSQ: 16,0          

OK  
AT+HTTPINIT           
OK  
AT+HTTPPARA="CID",1                   
OK  
AT+HTTPPARA="URL","www.google.com"                                  
OK  
AT+HTTPACTION=0               
OK  

+HTTPACTION:0,601,0                         

AT+HTTPACTION=0
OK

+HTTPACTION:0,601,0

Невозможно получить доступ к Google. Код 601 показывает ошибку сети. Как избавиться от этой ошибки?

2013-04-12 15:16

9
ответов

Вам необходимо настроить соединение с каналом-носителем. Вот минимальные команды установки, которые сработали для меня (на основе проб / ошибок и поиска в интернете).

AT+SAPBR=3,1,"APN","wap.cingular"
AT+SAPBR=1,1

Правильное значение для APN может отличаться для вас, в зависимости от вашей сети и поставщика услуг. Я использую предоплаченные SIM-карты AT&T. Как только это сработает, вы можете выполнять команды настройки HTTP, как у вас уже есть…

AT+HTTPINIT
AT+HTTPPARA="URL","http://www.google.com"
AT+HTTPACTION=0

Коды состояния выше 600 (а некоторые в диапазоне 500) не назначаются в стандарте HTTP. В руководстве по AT-команде для SIM908 значения состояния приведены в примечаниях к HTTPACTION команда:

600 Not HTTP PDU
601 Network Error
602 No memory
603 DNS Error
604 Stack Busy

Вы можете запросить состояние соединения на предъявителя CID 1 с AT+SAPBR=2,1 и связанные параметры с AT+SAPBR=4,1, Вы также можете проверить, что вы подключены к сети GPRS с AT+CGATT?, Если все указывает на то, что вы подключены и все еще получаете код состояния 601, убедитесь, что в вашем плане обслуживания есть данные и что он не исчерпан. Я обнаружил, что даже когда в моем аккаунте есть несколько сотен тысяч данных, отображаемых на балансе, я начинаю получать статус 601, пока не добавлю больше данных в свой тарифный план с предоплатой. Если модуль SIM был включен все время и вы добавляете больше данных, вам необходимо закрыть и заново открыть соединение (AT+SAPBR=0,1 с последующим AT+SAPBR=1,1) а потом твой HTTP* Команды снова начнут работать без установки HTTPPARA настройки снова и без необходимости перезапуска HTTPINIT,

2014-05-09 22:33

Я обнаружил, что при вызове http на веб-сайт только https он выдаст ошибку 601 на сим. Остерегайтесь, у некоторых сим-устройств есть ssl, а у некоторых нет. Использовать AT+HTTPSSL=? допросить. устройство с ssl ответит как «HTTPSSL 1». Если вы получили ошибку, ваше устройство не имеет ssl. Мне потребовалась определенная работа с фабрикой, чтобы определить это.

Вы также должны использовать, чтобы попасть на сайт ssl. Я использую клиент wifi101 ssl.

fona.setHTTPSRedirect (истина); Dy3

2016-11-13 15:08

Я тоже допустил эту ошибку. Причиной проблемы может быть то, что на счете телефонного номера недостаточно денег. Вы можете проверить это.

2016-08-02 05:23

Обычно после этой команды AT+SAPBR=3,1,»CONTYPE»,»GPRS» вы вводите данные «APN», «USR» и «PWD», также используя SAPBR=3,1 и т. д. Эти данные должны соответствовать SIM-карте. / оператор сотовой связи.

Затем рекомендуется проверить, что ваше устройство теперь получило IP-адрес. Иногда это не сразу. Используйте AT+SAPBR=2,1 для запроса, и это вернет ваш IP-адрес, который вы должны проверить для подтверждения.

Получив IP-адрес, вы можете ввести AT+HTTPINIT, AT+HTTPPARA=»CID»,1 и т. д.

Теперь, чтобы использовать GET, вы должны включить «?» после URL-адреса, чтобы предоставить вашему php-скрипту пару ключ = значение.

Таким образом, в вашем случае это что-то вроде AT+HTTPPARA=»URL»,»http://<Public_Ip_Address>:8080/folder/savedata.php?A=1001″, где A — ключ, а 1001 — значение.

Теперь отправьте AT+HTTPACTION=0, и вы должны получить ответ +HTTPACTION: 0,200,1000, где 200 — это OK, а 1000 — размер полезной нагрузки. AT+HTTPREAD позволит вам прочитать ответ, если это необходимо.

2021-10-10 07:26

На тот случай, если кто-то столкнется с этой проблемой и наткнется на этот пост 4 года спустя: в моем случае у модуля была маленькая антенна типа «стикер», и он как-то повредился.

Я мог подключиться к сети, но когда я попытался использовать HTTP в сетях GPRS, я получил только код возврата 601 (ошибка сети) или 603 (не удалось разрешить DNS).

Как только я заменил антенну на новую, все заработало отлично.

2017-11-23 11:29

Опять же, в случае, если у кого-то есть такая же проблема. В моем случае это была опечатка в URL:
AT+HTTPPARA="URL"," http://www.google.com"
Вы заметили пространство раньше http? Несколько часов я тоже этого не замечал.

2018-09-27 19:52

Я провел много часов с этим модулем прямо сейчас.

По моему опыту, когда вы не получаете 200 ответа от удаленного сервера, вы должны проверить IP-адрес, чтобы убедиться, что вы все еще находитесь в сети, отправляя эхо-запрос на работающий сервер (AT+CIPPING="XX.XX.XX.XX").

Если это удастся: попробуйте AT+SAPBR=2,1 а также AT+CIFSR, Вы должны получить один и тот же адрес для обеих команд.

Если вы не получили тот же адрес, войдите снова в netword/ сервис с AT+CIPCSGP=1, "yourapn.com", "user", "password",

Если ничего не работает, выключите модуль. Подождите пару минут и перезапустите снова.

2017-03-01 14:33

Изменить URL. 601 является URL has been moved, Это редирект.

2013-07-19 08:57

Другие вопросы по тегам
gsm

Источник

Понравилась статья? Поделить с друзьями:
  • 600e ошибка бмв х6 е71
  • 6008 ошибка виндовс 10 что означает
  • 6005 ошибка wargaming
  • 6008 ошибка виндовс 10 перезагружается
  • 6008 ошибка windows server 2019