# Reserved error codes The error codes that SMSC returns in response to BIND and **SUBMIT\_SM** packets are tabled below. | **Error code** | **Error message text** | **Description** | | -------------- | --------------------------- | --------------------------------------------------------------------------- | | 0x00000005 | ЕSME already in bound state | Session with system\_id is deemed active | | 0x0000000A | Invalid Source Address | Invalid sender ID (short number, source address) | | 0x0000000B | Invalid Dest Addr | Invalid recepient’s name (MSISDN, dest address) | | 0x0000000D | Bind failed | Selected connection type is no supported, produced BIND packet is incorrect | | 0x0000000E | Invalid password | Invalid password to connect to the SMSC | | 0x0000000F | Invalid System ID | Specified connection parameters are invalid | | 0x00000500 | Bad character code | Content contains bad words | Below are tabled the error codes that the SMSC returns in response to the **DELIVER\_SM** packet for SMS. | Error code | Error message text | Description | | ---------- | -------------------------------- | ----------------------------------------------------------------------------------------------------- | | 11 | error-address-format | Recipient phone number is wrong or not existing | | 127 | Timeout of getting status | Getting message status has expired | | 453 | Block list msisdn | The message is rejected due to blocklisted msisdn. This error code is also relevant for Flashcall. | | 454 | Block list sender | The message is rejected due to blocklisted sender ID. This error code is also relevant for Flashcall. | | 455 | - | Sending messages in this direction is restricted. | | 456 | - | The subscriber's phone number does not exist. | | 457 | - | The sender's ID is not registered. | | 458 | - | Traffic is blocked on the platform. | | 501, 1501 | Unknown subscriber | Phone number does not exist or is not in service | | 502, 1502 | SMSC failure | Internal routing error on the operator's side | | 503, 1503 | Region not supported | SMS delivery to this region is not available for the operator | | 504, 1504 | Teleservice not provisioned | The subscriber's device does not support SMS | | 505, 1505 | Call barred service activated | The subscriber has blocked incoming messages or is restricted by the operator | | 506, 1506 | Illegal subscriber | The subscriber is blocked by the operator or SMS service is not provided | | 508, 1508 | Absent subscriber | Subscriber is unavailable (switched off or out of coverage) | | 509, 1509 | Roaming restrictions | Subscriber is roaming or lacks roaming agreements | | 510, 1510 | Subscriber barred during mnp | Bank SMS blocked due to recent SIM card change (24-hour restriction) | | 511, 1511 | Message queue full | The operator's message queue for the subscriber is full | | 513, 1513 | Oper invsrcaddr | Sender name is blocked by the operator | | 515, 1515 | Equipment protocol error | Subscriber's device cannot receive SMS due to a technical issue | | 517, 1517 | Memory capacity exceeded | Subscriber's phone memory is full | | 520, 1520 | Msisdn blacklisted | The number is blacklisted by the operator | | 522, 1522 | Black list | Sender name is blacklisted or not allowed for the recipient | | 523, 1523 | Subscriber is busy | The subscriber's device is busy and cannot receive SMS | | 526, 1526 | Unknown equipment | Device (IMEI) is unknown or not allowed in the network | | 527, 1527 | SMSC timeout | Delivery report not received within the expected time (network/device issue) | | 529, 1529 | Unauthorized subscriber | Recipient is on an opt-out list | | 532, 1532 | Duplicate error | Message blocked as duplicate | | 561, 1561 | Invalid subscriber | Invalid number format (landline, unsupported numbering, or recent operator change) | | 564, 1564 | Template not allowed | Message blocked by spam filters (forbidden words or sender restrictions) | | 575, 1575 | Fraud | Number blocked due to suspected fraud (auto-unblock in 24h) | | 601 | Not viber user | The recipient is not a Viber user | | 605 | Status error user blocked | The recipient has blocked notifications | | 607 | No suitable device | The app version does not support service messages | | 614 | Error caption too long | Button caption exceeds the allowed length | | 616 | Message limit exceeded | Maximum allowed messages delivered | | 617 | Not template match | No matching message template found | | 618 | Filtered | Message contains prohibited words | | 621 | Marketing template undeliverable | Marketing message limit reached for the recipient | | 644 | Not whatsapp user | The recipient is not a WhatsApp user | | 662 | User is part of an experiment | User is in a test group with restricted marketing messages | | 663 | Message undeliverable | Generic WhatsApp delivery failure (exact cause unknown) | | 680 | Session not started | Template issues: blocked, warned, or mismatched | | 681 | Media download error | Failed to download media from the provided link | | 682 | Generic whatsapp error | Unknown WhatsApp error (no specific details) | | 724 | Image is invalid | Invalid image or missing text in the message | | 733 | Generic MMS error | General MMS delivery failure (contact support) | | 734 | No success status | MMS center did not return a success status | | 735 | Invalid MMS | MMS creation failed (invalid content) | | 736 | MMS center error | Failed to send request to the MMS center | | 737 | File too large | File size exceeds the allowed limit | | 738 | Image resolution exceeded | Image resolution is too high | | 739 | Unsupported file type | File type is not supported | | 740 | Delivery not confirmed | No delivery confirmation (device issue or undownloaded MMS) | | 741 | MMS without image | Invalid message due to missing image | | 999 | Unknown Error | Unknown error | Below are tabled the error codes the SMSC returns in response to the DELIVER\_SM packet for Flashcall. | Error code | Error message text | Description | | ---------- | ------------------------ | ----------------------------------------------------------------------------------------------- | | 263 | unknown-error | Unknown error | | 265 | invalid-message | Invalid message | | 266 | destination-denied | Destination or operator is not supported | | 267 | number-generation-failed | Code transmission number has not been generated | | 268 | duplicate | Message is duplicate (duplicating is sending a message to the same number within a minute) | | 269 | sending error | Request has been received but not sent to the operator due to an unexpected system failure | | 270 | rejected | Call cannot be made (the phone number is busy with another call, or other SIP-error has arisen) | Below are tabled the error codes for Telegram Gateway. | Error code | Error message text | Description | | ---------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | 1400 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1401 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1402 | phone-number-invalid | Incorrect phone number | | 1403 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1404 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1405 | ttl-invalid | Incorrect TTL value | | 1406 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1407 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1408 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1409 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1410 | gateway-ttl-expired | The expired status returned in the message delivery report. TTL expired on the Gateway API side, the message was deleted from the chat | | 1411 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1412 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1413 | flood-wait-retries-exceeded | Telegram blocked sending after repeated attempts | | 1414 | submit-retries-exceeded | Telegram did not respond to the request after repeated attempts | | 1415 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1416 | authorization-code-not-found | The code was not found in the message text | | 1417 | gateway-error | Temporary difficulties in delivery on the Telegram side | | 1418 | phone-number-not-available | Unavailable phone number | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://smsc.revicom.ltd/how-to-work-with-smsc/reserved-error-codes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.