Response Status and Error Codes

• 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.

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

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

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

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

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

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

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• The sender ID has been blacklisted on your account via Infobip websites portals. Remove the blacklist on your account or contact Support for further assistance.

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

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

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

• 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.

• 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.

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

• 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.

• 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

• 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.

• 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.

• 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.

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

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

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

• 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.

• 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.

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

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

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

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

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

• Actions submitted in HTTP API request are invalid.

• Action groups submitted in HTTP API request are invalid.

• 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.

• 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.

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

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

• Unidentified Subscriber

• 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.

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

• 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.

• Illegal Subscriber

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

• Illegal Equipment

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

• Facility Not Supported

• 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.

• Subscriber Busy For Mt SMS

• SM Delivery Failure

• Message Waiting List Full

• System Failure

• Data Missing

• Unexpected Data Value

• Unknown Error

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

• There has been a mobile subscriber equipment error.

• There has been a mobile subscriber equipment error.

• There has been a mobile subscriber equipment error.

• There has been a mobile subscriber equipment error.

• There has been a mobile subscriber equipment error.

• There has been a mobile subscriber equipment error.

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

• 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• No Translation For This Specific Address

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• IMSI blacklisted

• The destination number has been blacklisted either at the operator`s request or on your account via the Infobip web interface - go to the Infobip web interface to remove the blacklist on your account or contact Support for more information.

• The sender number has been blacklisted either at the operator request or on your account via Infobip web portals - go to the Infobip web interface to remove the blacklist on your account or contact Support for more information.

• Source address is blacklisted on the Infobip account.

• Invalid PDU Format

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

• 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.

• 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.

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

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

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

• Bearer Service Not Provisioned

• SS Incompatibility

• 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.

• Unknown Alphabet

• Invalid Response Received

• Time Out

• The number was found blacklisted in the DND (Do Not Disturb) blacklist provided by the operator, or the same error code was reverted by the operator.

• Text blacklisted

• Not Submitted To GMSC

• Not Submitted To Smpp Channel

• The call has been received and answered.

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

• Destination address is currently not available.

5603 

false         

EC_DECLINE

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

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

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

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

• The format of the file specified is not supported.

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

• The received request was rejected by the operator.

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

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

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

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

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

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

• Format of the file is not supported.

• Specified destination number is incomplete.

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

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

• Server has some pending request from the same dialog.

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

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

• The service failed to complete the request.

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

• 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.

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

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

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

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

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

• 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.

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

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

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

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

• 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.

• Emails are dropped due to spam content.

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

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

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

• Sender name is not a valid one - Either invalid characters or either invalid domain was used.

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

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

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

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

• 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.

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

• Sending email failed due to internal error.

• 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.

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

• Receiving user has blocked communication.

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

• 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.

• Attempt to send a message with not allowed type.

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

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

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

• Problem with account

• Issue with WhatsApp deployment

• Provided media link has issues related to hosting.

• Issue with media upload to provider

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

• Message is being rejected due to spam

• Sending speed is too high

• Internal bad request

• Billing error on provider`s side (for now Viber only)

• Error displaying content on the end-user device

• Product functionality limited on the provider`s side.

EC_MEDIA_UNSUPPORTED

• The media format is not supported.

• Facebook’s Phone matching option not enabled for the application. Check out the Facebook documentation to see if your application is eligible for this paid feature.

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

• Internal service provider error.

• Connection to service provider timed out.

EC_PROVIDER_DR_ERROR

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