Response status and error codes

Message has been successfully sent from our platform to the operator's end, but we are awaiting a delivery report from their end. In case the delivery itself is impacted, the causes can be the availability of the destination, network issues and congestions, or additional setup requirements.

Message has been successfully accepted and processed by our platform, and it has been forwarded to the next instance, which specifically involves the mobile operator.

Message is in a pending state after being accepted by the system and waiting for further processing or delivery confirmation from the operator.

Message was rejected by the operator and deemed undeliverable, possibly due to network glitch or restrictions imposed by the operator. Resolution steps include contacting the Support for further clarification or resolution.

9

Message was not delivered to the intended recipient and considered undeliverable, typically due to factors such as an invalid or unreachable destination number. Resolution steps involve verifying the accuracy of the recipient's number. If the issue persists, contact Support for assistance.

The phone number you provided is listed as deactivated, which means it is no longer active and cannot receive messages. If you included the mobileOperatorId in your request, you can perform an operator lookup to check if the number was ported to a new operator. If you did not include the mobileOperatorId, we have already performed the lookup and confirmed that the number is permanently deactivated. It is crucial to refrain from sending any further messages to this number. For more details, refer to the guidelines on handling deactivated phone numbers.

Message has been successfully delivered to the operator's system and awaits further processing or delivery to the recipient's handset.

Message has been successfully delivered to the recipient's handset.

Message was received and sent to the operator. However, it has been pending until the validity period has expired or the operator returned the EXPIRED status in the meantime. Resolution steps include contacting the Support for further clarification or resolution.

Message has expired, and the delivery status is unknown, indicating that the delivery report or confirmation was not received or could not be determined. Resolution steps involve contacting Support for further assistance to resolve the unknown delivery status.

Message has been rejected due to an anti-fraud mechanism.

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, or reach out at [email protected].

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 or reach out at [email protected].

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.

The destination address has been blocklisted either at the operator request or on your account via web interface. Remove the blocklist 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 or reach out at [email protected] 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, or reach out at [email protected] to get more info.

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 or at [email protected].

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.

Machine detection is not enabled. Contact your dedicated Account manager or reach out at [email protected].

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

Status is returned when notifyUrl parameter is not formatted properly.

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

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.

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.

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.

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.

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. Find more information about User Data on the following links: 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.

Typically indicates that the subscriber or recipient of the message is unknown or not recognized by the network. It means that the provided subscriber information, such as the phone number, does not exist or is an unknown user in the network's database. To resolve this error, it is recommended to verify the accuracy of the subscriber details by dialing the provided number. If the number is available, contact support for assistance.

Suggests an error involving an unidentified or unrecognized base station, often in the context of network or communication systems. This could be due to a missing or inaccessible base station.

This can occur for various reasons, such as an invalid or unregistered number, incomplete or incorrect subscriber information, or technical issues retrieving subscriber details. Resolving this error typically involves verifying and correcting the subscriber information and if the destination is correct and available, contact Support for assistance.

This indicates that the destination numbers provided during the submissions were unreachable (not properly connected on the operator's network) or powered off or located in an area with limited/low coverage or subject to roaming restrictions. Resolving this error ensuring that the subscriber's device is turned on and has a stable network connection.

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.

Indicates that the mobile station failed authentication, often due to the subscriber's number being blacklisted or subscribed. Resolving this error typically involves investigating and addressing the underlying reasons for the subscriber's illegal status, which may involve contacting the network operator or contact Support for assistance.

This indicates that the mobile subscription associated with this number does not support the short message service (SMS). It means that the requested service, such as SMS, is not available or activated for the subscriber's account. Resolving this error usually involves contacting the service provider or network operator to ensure the necessary teleservice is provisioned and activated for the subscriber's account.

The IMEI check on the handset failed, indicating that the IMEI of the device is either blacklisted or unauthorized according to the system. Resolving this error typically involves ensuring the use of authorization.

The operator suspended the subscriber's service, usually because of unpaid invoices. Resolving this error usually involves checking the subscriber's account status, ensuring sufficient balance or subscription plan, and contacting the network operator to lift any call barring restrictions if necessary.

The requested functionality or service is not supported by the handset or the network being used due to limitations, restrictions, or incompatibility. Resolving this error typically involves verifying the supported facilities or services, ensuring the subscriber's compatibility with the requested feature, handset devices restart, and applying the newest software/firmware updates.

This indicates that the destination numbers provided during the submissions were unreachable (not properly connected on the operator's network) or powered off or located in an area with limited/low coverage or subject to roaming restrictions. Resolving this error involves ensuring that the subscriber's device is turned on and has a stable network connection.

Subscriber Busy For Mt SMS

Indicates that there was a failure in delivering an SMS message to the intended recipient. The exact reason for the failure may be related to the recipient's unavailability, memory capacity issues, or temporary communication issues between the operator and the end user. Resolving this error may involve verifying recipient details, or contact Support to investigate any potential network or configuration issues.

Message Waiting List Full

System Failure

Data Missing

Unexpected Data Value

Unknown Error

Indicates that the message inbox on the recipient's mobile phone is currently full, preventing the storage of new messages. To resolve this issue, delete the messages and clear the message inbox on the end-user handset.

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.

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.

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.

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.

Temporary handset failure.

Destination address unable to receive SMS.

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.

The request type was invalid.

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.

Invalid request - destination address country code is not recognized.

Message text is too long.

Invalid source address value. The mobile operator rejected the message with an invalid MT source address error. Contact your Account Manager or reach out at [email protected] to determine if your MT source address should be supported by the end user's mobile operator.

Source address (recipient) is blocked or is not provisioned.

Account access denied.

''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 or reach out at [email protected] to get the TFN verified.

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.

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.

Program ID or campaign ID is not provisioned for this mobile operator or is not active.

Account not provisioned to use SMS demo short code.

Exceeded the time limit for using SMS demo.

Destination address not in whitelist for SMS demo.

Exceeded the maximum number of demo requests.

Invalid global campaign ID.

Account is not provisioned with the address that can reach the destination.

Interaction not supported for message destination.

Account is not provisioned for global two-way SMS.

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.

Content blocked by campaign blocklist.

This message was identified as spam and cannot be delivered

The message has been rejected due to an anti-fraud mechanism. It means that the risk score of the destination hit the defined threshold and the system blocked the message. In case of a false positive, you can use Signals API to add it to the trusted list.

IMSI blocklisted

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.

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.

Invalid PDU Format

Your account monthly credit limit has been reached. For further financial assistance, contact your Account Manager or reach out at [email protected].

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.

As per the flooding filter rule, you can send 6 messages with the same content to the same destination in a period of one hour while or you can send up to 20 messages with different content to the same destination in a period of one hour. If there is a valid reason for the traffic to bypass the filter, your Account Manager can assist you with adjusting these limitations, or reach out at [email protected].

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

Suggests that the requested bearer service is not available or activated for the user or device attempting to access it. This can be due to service unavailability in the subscription, lack of network support, or configuration/provisioning issues. Resolving this error typically involves contacting the service provider or network operator to ensure the necessary bearer service is provisioned and activated for the subscriber's account.

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

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.

Invalid Response Received

Mobile operator blocking the end user from this Short Code

Content blocked by mobile operator for this end user.

Short code not provisioned with mobile operator. Contact your dedicated Account Manager or reach out at [email protected] if you believe that you are provisioned for the operator or if you want to begin provisioning.

Short code expired with mobile operator. Contact your dedicated Account Manager or reach out at [email protected] if you believe that you are provisioned for the operator or if you want to begin provisioning.

• 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 or reach out at [email protected] if you are unsure why you received this error.

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.

Destination address not provisioned for SMS.

Destination address suspended by the mobile operator.

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 or reach out at [email protected] if you are unsure why you received this error.

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.

Destination overloaded.

Mobile operator network error.

SMS rejected by the mobile operator for attempted destination address.

Message failed due to an unknown mobile operator error.

Failed message delivery.

Message expired before it reached handset.

Message submitted to but not acknowledged by the mobile operator.

Time Out

The numbers were identified as blacklisted in the operator's DND (Do Not Disturb) database, provided by the operator, or the operator reverted the same error code. Resolving this error typically involves reviewing the blacklist status of the destination address, checking for any legitimate reasons for blacklisting, and taking appropriate actions to remove it.

Text blocklisted

Messages not passed to any operator and failed at Infobip platform

Not Submitted To Smpp Channel

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

The voice call was successfully answered by the recipient. No further action is required.

The voice call was answered by a machine or voicemail system. You may consider adjusting your communication strategy for machine-answered calls.

Temporary unavailability of the voice service or recipient currently unavailable. Retry the operation later or contact Support for assistance.

The call was declined by the recipient or the end user rejected the call or is currently unavailable for the call. Consider alternative methods of communication or try reaching out again later.

The recipient's phone line is busy. You can try calling again at a later time or explore other communication channels.

The recipient did not answer the call. You may try calling again later or choose an alternative communication method.

An error occurred while downloading the audio file for playback. Verify the file's accessibility and format. If the issue persists, contact Support for further assistance.

The audio format is not supported. Check the audio format requirements, use supported types and ensure compatibility with the voice service.

The voice call request was malformed or contained invalid parameters. Review the request or ensure it is properly formatted and check the API documentation for the correct request structure.

The voice call request was rejected by the operator. Contact Support for further assistance.

The destination for the voice call was not found or is invalid. Double-check the recipient's phone number or destination details.

Proxy authentication is required to establish the voice call. Contact Support for further assistance.

The voice call request timed out before a response was received or the end user could not be found in time during the call. Contact Support for further assistance.

The requested voice call resource is no longer available. Ensure the recipient's phone number is valid and accessible or contact Support for further assistance.

The voice call request entity (e.g., audio file) is too large. Reduce the size of the request entity and try again.

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

The media type used in the voice call is not supported. Ensure you are using a compatible media type for the voice call.

The voice call record/transaction does not exist. Contact Support for further assistance.

The address (e.g., destination number) provided for the voice call is incomplete or invalid. Make sure the address is correctly formatted.

The voice call request was terminated with a cancel button or the end user refused to receive a voice call.

The voice call request is not acceptable on the operator’s end. Contact Support for further assistance.

The voice call request is pending and waiting for further processing. Wait for the request to be processed or check the status later.

The requested voice call feature is not implemented or supported. Contact Support for further assistance.

The voice call service is temporarily unavailable. Retry the request later or contact Support for further information.

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

The call was answered on another device or platform. Verify the call status on the intended device or investigate further if needed.

The voice call was answered by a machine or voicemail system. You may consider adjusting your communication strategy for machine-answered calls.

A human answered the call. You can take appropriate action based on the call's purpose.

The call reached the maximum allowed duration. If needed, initiate a new call or adjust the call duration settings and contact Support for further assistance.

The device (camera and/or microphone) used for the call is not allowed or blocked. Check device permissions or restrictions and take appropriate action.

The device (camera and/or microphone) for the call could not be found or is unavailable. Ensure the device is accessible and try again.

The device (camera and/or microphone) for the call is currently unavailable.

An error occurred with the media during the call (e.g., an audio issue). Check the media settings and equipment, and troubleshoot as necessary.

The call has been successfully delivered to the end-user device; however, it was not answered by the end-user.

The call has been successfully delivered to the end-user's device, but the end-user's device indicates that they are currently busy and unable to answer the incoming call.

The call was canceled at the origination end before it could be successfully routed to the end-user.

The call was rejected/declined by the end-user at the receiving end.

The end user was unavailable to receive the call at the moment. The operator attempted to connect the call but encountered an issue with the end user's connection or availability, resulting in the call not being successfully connected. It is advisable to verify if the phone number provided is valid and reachable to ensure effective communication in the future.

The received request was rejected. Contact Support for further assistance.

The account you are using does not have sufficient credits or funds available to initiate the phone call you are attempting to make. In order to proceed with the call, you will need to ensure that there are enough credits or funds in your account.

The caller's credentials or access rights are invalid or insufficient to initiate the call. To resolve this, ensure that the caller provides valid authentication credentials or obtain proper authorization for making the call.

The server was unable to locate the destination number you dialed. This could be due to an incorrect country prefix or an invalid number format. To resolve this issue, double-check the country prefix and ensure that the number you dialed is accurate and in the correct format.

The destination number you attempted to call is currently unavailable to receive incoming calls. To address this situation, it is recommended to verify if the number you dialed is valid and reachable.

The server was unable to locate the destination number you dialed. This could be due to an incorrect country prefix or an invalid number format. To resolve this issue, double-check the country prefix and ensure that the number you dialed is accurate and in the correct format.

The call request is invalid or malformed. Review the request parameters and structure, and make necessary adjustments.

The call request timed out without a response. For more specific details and assistance, contact the Support team that can provide further information and guidance.

An error occurred in the network during the call. Check the network connection and contact Support for further investigation.

The call service is temporarily unavailable. Contact Supportt for assistance.

An unknown error occurred during the call. Contact Support for further investigation and assistance.

The requested call feature is not available or supported. Consider alternative features or methods for communication or contact Support for assistance.

The call could not be completed due to network congestion or overload. Contact Support for further investigation and assistance.

The requested URL for the call was not found. Verify the URL and make necessary corrections.

The requested URL for the call is unreachable. Check the network connectivity and URL accessibility.

The response received during the call is invalid or unexpected. Contact Support for assistance.

The call has been received and answered.

The call was answered on another device.

The peer connection has not been established.

Invalid DTMF configuration (no audio track).

DTMF options is not available.

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

Local stream was not initialized.

The audio track is missing.

The video track is missing.

Display media API is not available.

Unknown screen share error.

The end user received the call but did not answer it.

The end user is currently busy and not able to receive the call.

Permission to use camera and/or microphone was denied.

Device does not have a camera and/or microphone connected/enabled.

Camera or microphone is already in use.

The end user received an incoming call while they were on another active call.

Call terminated.

The end user is already joined on another device.

The maximum number of users was already reached.

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

Could not read the client's URL.

Could not reach the client's URL.

The received request was rejected.

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

The server could not process the request because of an unexpected error.

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

The service is temporary unavailable.

The server has a pending request from the same dialog.

The specified destination number is incomplete.

The destination address is currently unavailable.

There has been a connection error.

There has been an unknown WebRTC error.

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

MMS provider general error.

System error.

MSISDN is not registered by the operator.

Message is deferred. The end user's handset has retrieved the MMS header, but not downloaded the full message.

The end user has forwarded the MMS to another address without retrieving it.

Mobile operator could not contact the handset before reaching the expiry time.

Content cannot be downloaded on handset.

MMS provider delivery error.

Recipient not found on mobile operator.

Source address not provisioned with the operator.

Recipient blocked by receiving MMS by the operator.

DRM not supported.

MMS content blocked or unsupported by the operator.

Invalid MMS subject in request.

End user has blocked traffic from this specific SC.

Unable to determine the mobile operator.

Recipient is deactivated.

Recipient is suspended from the service.

MMS is not supported on handset.

Campaign blocked by mobile operator.

Campaign information is not provisioned for this mobile operator.

Cannot retrieve MMS as the URL attachment is too large.

Failed to route MMS message.

Could not retrieve remote content.

Internal error trying to fetch remote content.

Invalid MMS message type.

Invalid MMS destination address.

Invalid MMS source address.

Invalid MMS subject parameter.

Your sending domain or IP was or still is listed on a blacklist. Remove any blacklistings before sending again to this recipient or contact Infobip Support for further assistance.

The email content is flagged as spam. Review and modify the content to comply with email deliverability best practices and contact Support for further assistance.

The recipient's email address is unsubscribed, indicating their preference to not receive emails. To resolve this, check their subscription status and If the recipient indicated they want to be subscribed again.

The email could not be delivered to the recipient's address and was bounced back. Verify the email address for accuracy or contact Support for further assistance.

The email was dropped and not delivered due to various reasons. e.g., the recipient had previously bounced, unsubscribed, or complained of spam. Review the email's content, recipient list, and sender reputation to resolve the issue or contact Support for further assistance.

The sender's domain is blocked, preventing emails from being sent which indicates the sender's domain has exceeded the bounce threshold. Review or remove the invalid recipient's address or you can follow the link for Best Practices to Improve Email Deliverability https://www.infobip.com/blog/10-best-practices-to-improve-your-email-deliverability or contact Support for further assistance.

The IP address used for sending emails is blacklisted. Check the IP's reputation and request removal from the blacklist to resume email sending or you can follow the link for Best Practices to Improve Email Deliverability https://www.infobip.com/blog/10-best-practices-to-improve-your-email-deliverability or contact Support for further assistance. 

The request made to the email gateway is invalid. Ensure the request parameters and data are correct before resending or contact Support for further assistance.

There is an error in the handlebars syntax used in the email template. Fix the handlebars syntax and try sending the email again or contact Support for further assistance.

The recipient's email address provided is invalid. Verify the recipient's email address format and correct any errors before resending the email.
or you can use our email validation service to validate the recipient's email address.

The recipient's mailbox is temporarily unavailable. Retry sending the email later when the mailbox is accessible.

The email delivery is deferred due to insufficient storage in the recipient's mailbox. Wait until storage becomes available and resend the email.

The recipient's mailbox is currently unavailable. Check for any temporary issues with the mailbox or verify the email address and try sending the email later.

The recipient's mailbox storage limit has been exceeded. Advise the recipient to clear their mailbox or consider alternative means of delivering the email.

The email was permanently rejected and bounced back due to the recipient's email address being invalid. The recipient's email address will automatically be unsubscribed from further email communication.

The email was temporarily rejected and bounced back. To resolve this, contact Support for further assistance.

A temporary error occurred while sending the email. Retry sending the email after a brief interval.

A permanent error occurred while sending the email. Review the domain used as the sender is active and registered or contact Support for further assistance.

An error occurred while trying to send the email. Contact Support for further assistance.

The specified email template could not be found. Verify the template's existence, correct identifier or expired and correct any reference errors.

The tracking parameters used in the email are invalid. Review and fix the tracking parameters before resending the email.

The size of the placeholders on the landing page exceeds the allowed limit (256 characters). Adjust the size of the placeholders to fit within the limit.

The headers of the email are invalid or improperly formatted. Check the headers and ensure they meet the required format.

The email parsing process failed due to an error. Review the email's content and structure to identify and rectify any parsing issues or contact Support for further assistance.

The email sender is invalid or unauthorized to send emails. To resolve this issue, check the sender domain for spelling mistakes and ensure that the domain is active and properly configured.

The specified landing page is invalid or inaccessible. Confirm the landing page's URL and availability before using it in the email or contact Support for further assistance.

The preserved recipients in the email are invalid. Check the recipient list and ensure all preserved recipients are valid and limit reached or contact Support for further assistance.

The email has expired and is no longer valid due to an internal error. To resolve this, contact Support for further assistance.

Indicates an error related to an improperly formatted email address. This typically means the provided email address does not adhere to the required structure or contains invalid characters.

Indicates that the requested application is unknown or not recognized. Resolution steps involve verifying the application details, ensuring proper configuration, and contacting the appropriate support channels for assistance.

Signifies that the user is unknown or not registered. To resolve this error, verify the user's details or ensure that the MSISDN is correct and belongs to an active user.

Indicates that the user has been blocked or restricted from accessing the messages. Resolution steps involve investigating the reason for the user block, reviewing any violation or restriction policies, and taking appropriate actions such as unblocking or contacting support for further assistance.

Denotes unauthorized access or unrecognized service access credentials. To resolve this error, investigate the unauthorized access attempt, ensure proper authentication/credentials, and contact support for further assistance.

Indicates that access to the requested resource or service is forbidden. Resolution steps involve verifying the user's access rights and permissions, that the application is allowed to send messages, and that it is published or approved by the provider.

The server cannot process the request due to invalid syntax or parameters. Verify the request data and ensure it follows the required format or check the API documentation for the correct request structure or contact our customer support for additional guidance.

Indicates that the content of the submitted message does not align with the registered traffic type of the sender. This could be due to the use of incompatible media elements or not understanding any restrictions or guidelines related to traffic types. For more specific details and assistance, contact the support team who can provide further information and guidance.

Denotes invalid or missing parameters in a message template. To resolve this error, review the template structure, ensure all required parameters are provided, and correct any invalid or missing parameters.

Signifies an invalid on an incorrect message template. Resolution steps involve reviewing the template and making the necessary modifications or corrections.

Indicates that the session has not been initiated or has expired. To resolve this error, establish a valid session by authenticating the user or application, ensure a new session, or extend the existing session by the user or application.

Signifies an issue or problem related to the user's account. Resolution steps involve investigating the account-related problem and contacting support for further assistance.

Denotes an error or issue with the deployment or configuration of the system or service. To resolve this error, contact support for further assistance.

Indicates an error or problem related to media hosting or storage. Resolution steps involve verifying the media hosting setup, ensuring proper connectivity, and resolving any hosting-related issues.

Signifies an error or problem encountered during media upload. To resolve this error, check for any network or connectivity issues, and ensure the media file meets the specified requirements.

Denotes an error or issue with the metadata associated with media files. Resolution steps involve reviewing the metadata information, ensuring content type, and size, and resolving any metadata-related problems.

Message failed because there are restrictions related to the sender quality rating on how many messages can be sent from this sender to unique end users during the period defined by the provider.

Signifies that the number of requests from the application has exceeded the allowed limit. To resolve this error, reduce the frequency or number of requests, adhere to rate limits, and consider optimizing the request flow if necessary.

Denotes an internal error related to mapping or data structures within the system. Resolution steps involve investigating the mapping issue, reviewing and resolving any inconsistencies or errors in the mapping process, and contacting support for further assistance.

Indicates an error or problem with the billing process or integration with the provider. To resolve this error, review the billing setup, ensure proper integration and configuration with the provider, and address any billing-related issues or errors.

Signifies an error or problem related to displaying content on the end user device. To resolve this error, check network connectivity and refresh the content, clear the cache and update the app or software, or verify device compatibility and contact support if the error persists.

Denotes limited functionality or restricted access to certain features or services on the Meta side. To resolve this error, review the functionality restriction on the Meta side.

Indicates that the media file or format is not supported by Meta. Resolution steps involve verifying the supported media formats, converting the media file to a supported format if necessary, and ensuring compatibility with Meta's media requirements.

Signifies a mismatch or inconsistency in the data local or remotely. To resolve this error, validate its accuracy and consistency, and address any mismatches or inconsistencies,  consider reaching out to our support team for additional assistance.

Denotes an error where the sending time for the message is not allowed or falls outside the permitted time window. Resolution steps involve reviewing the sending time restrictions or policies, adjusting the sending time if necessary, and ensuring compliance with the permitted time frames.

Indicates that the mobile app version being used is not supported by the Meta. To resolve this error, update the mobile app to a supported version, ensure compatibility with the Meta requirements, and address any version-related issues towards support for further assistance.

Denotes that the message type or category has been exhausted or reached the supplier's API limit. Resolution steps involve reviewing the message type limitations and managing message usage within the allocated limits.

Signifies that the content of the message is blocked or restricted due to policy violations or content filtering. To resolve this error, review the message content, ensure compliance with content guidelines, modify the content if necessary, and address any policy violations.

Indicates that the user's identity or authentication details have changed or become invalid. Resolution steps involve verifying the user's identity, updating authentication information if necessary, and ensuring proper user identification and authentication.

The receiving user has blocked a specific template.

Indicates a data mismatch or inconsistency, whether it's in a local or remote context. To resolve this issue, first, verify the accuracy and consistency of the data. If you identify any discrepancies or inconsistencies, consider reaching out to our support team for additional assistance.

Denotes an unsupported or incompatible device attempting to access the service. To resolve this error, verify the device compatibility requirements, and address any device-related issues or limitations.

Indicates an internal error or issue within the provider's system or infrastructure that is affecting the processing of messages. If you encounter this error, it is recommended to wait for some time and If the issue persists, it is advised to reach out to Support for further assistance and investigation.

Signifies a timeout or connection issue with the provider and Infobip's platform. To resolve this error,  It is recommended to contact customer support for assistance in resolving the issue and investigating the underlying cause.

Denotes an error or problem related to the provider's delivery report mechanisms or processes. Resolution steps involve contacting support for further assistance.

EC_BLOCKED_BY_DLT

This error indicates that a message has been blocked by the DLT Provider due to regulatory compliance issues, sender registration, template registration, etc.

EC_DLT_SCRUBBING_TIMEOUT

Timeout while performing DLT Scrubbing.

EC_SENDER_BLOCKED_BY_DLT

The error typically indicates that the sender of a message has been blocked by the DLT Provider. This means that the sender has been restricted from sending messages due to non-compliance with regulations, insufficient registration, or other factors determined by the DLT Provider.

EC_TELEMARKETER_BLOCKED_BY_DLT

Telemarketer blocked by DLT Scrubbing.

EC_ENTITY_BLOCKED_BY_DLT

The error typically indicates that the principal entity ID of a message has been blocked by the DLT Provider. This means that the entity has been restricted from sending messages due to non-compliance with regulations, insufficient registration, or other factors determined by the DLT Provider.

EC_TEMPLATE_BLOCKED_BY_DLT

The error typically indicates that the template or content of a message has been blocked by the DLT Provider. This means that the message template or content has been restricted from sending messages due to non-compliance with regulations, insufficient registration, or other factors determined by the DLT Provider.

EC_ENTITY_NOT_FOUND 

Indicates that the requested principal entity ID could not be found or located. This means that the DLT Provider was unable to locate the specific PE ID being referenced. It could be due to various reasons, such as an incorrect identifier, a non-existent entity, or a misconfiguration.

EC_ENTITY_NOT_REGISTERED

No entry of entity on the platform. 

EC_ENTITY_INACTIVE

This error code indicates that the principal entity in question is inactive or disabled. This could be due to various reasons, such as principal entity ID suspension, temporary deactivation, or restrictions. Resolving this error typically check with DLT Provider. 

EC_ENTITY_BLACKLISTED

This error code indicates that the requested principal entity has been blacklisted. It means that the entity is restricted or prohibited on DLT Provider, such as violation of policies, non-compliance, or suspicious activity.

EC_INVALID_ENTITY_ID

This error code suggests that the provided Principal entity ID is an invalid or wrong format or does not exist in the DLT Provider. It means that the principal entity ID is incorrect or unrecognized. Verifying the accuracy of the entity ID or resolving any issues related to the entity's DLT provider can help resolve this error.

EC_ENTITY_ID_NOT_ALLOWED_FOR_TM

Principal entity is not allowed for the TM.

EC_TELEMARKETER_NOT_REGISTERED

No entry of TMID on the platform.

EC_TELEMARKETER_INACTIVE

Telemarketer is inactive on the platform.

EC_TELEMARKETER_BLACKLISTED

Telemarketer is blocklisted on all platforms.

EC_HEADER_NOT_FOUND

This error code signifies that the requested header/Sender ID information was not found. It means that the DLT Provider could not locate the required header in the given context or request. Review the request structure, and ensure the presence of the necessary headers.

EC_HEADER_INACTIVE

This error code indicates that the requested header is inactive or disabled. It means that the header, typically used to send messages, is currently inactive. Activating the required header or checking for any configuration or permission-related issues on DLT Provider can help resolve this error.

EC_HEADER_BLACKLISTED

This error code suggests that the requested header has been blacklisted, meaning it is restricted or prohibited from being used. It could be due to policy violations, non-compliance, or suspicious activity.

EC_PEID_NOT_MATCHED_WITH_HEADER

This error code indicates that the provided PEID (Principal Entity ID) does not match the header/Sender ID information. It means that there is a mismatch between the specified PEID and the associated header in the request. Verifying the accuracy and alignment of the PEID and header on the DLT Provider can help resolve this error.

EC_HEADER_IN_FREEPOOL

Header in free pool. 

EC_TEMPLATE_NOT_FOUND

This error code signifies that the requested template could not be found. It means that the DLT Provider was unable to locate the specified template, which is typically used for standardized message formats or content. Verifying the template's existence, and correct identifier, or troubleshooting any issues related to template retrieval can help address this error.

EC_TEMPLATE_INACTIVE

This error code suggests that the requested template is inactive or disabled. It means that the template, which is typically used for predefined message structures, is currently not active on DLT Provider. Activating the required template or addressing any configuration or permission-related issues with DLT Provider can help resolve this error.

EC_TEMPLATE_BLACKLISTED

This error code indicates that the requested template has been blacklisted, meaning it is restricted or prohibited from being used. It could be due to policy violations, non-compliance, or suspicious activity.

EC_TEMPLATE_NOT_MATCHED

This error code suggests that the requested template does not match the provided content or message. It means that there is a mismatch between the specified template and the actual content being sent. Ensuring the alignment between the registered template and the actual content being sent can help resolve this error.

EC_HEADER_NOT_REGISTERED_FOR_TEMPLATE

This error code signifies that the specified header is not registered or associated with the requested template. It means that the header being used does not align with the template requirements or associations. Verifying the registration and linkage between the header and template can help address this error.

EC_TEMPLATE_VARIABLE_EXCEEDED_MAX_LENGTH

This error code indicates that a variable within the template exceeds the maximum allowed length. It means that variables used within the template exceed the defined character limit. Adjusting the character length can help resolve this error.

EC_ERROR_IDENTIFYING_TEMPLATE

Error in identifying the template.

EC_INVALID_TEMPLATE_ID

This error code suggests that the provided template ID is invalid or does not exist in the system. It means that the template ID/Content ID used to reference a specific template is incorrect or unrecognized. Verifying the accuracy of the template ID or troubleshooting any issues related to the template's existence can help address this error.

EC_TEMPLATE_NOT_REGISTERED_TO_ENTITY

This error code signifies that the requested template is not registered or associated with the specified principal entity ID. It means the template being used does not link to the intended principal entity. Verifying the registration and association between the template and principal entity ID can help resolve this error.

EC_PROMOTIONAL_TEMPLATE_USED_ON_OTHERS_HEADER

Promotional Template used on other/transaction header.

EC_INVALID_TEMPLATE_TYPE

Invalid template type.

EC_PREFERENCE_NOT_MATCHED

This error code indicates that the requested preference does not match the specified criteria on the end user number. It means that the preference being used does not align with the end user number.

EC_INVALID_PROMO_TIME

This error code suggests that the provided promotional time is invalid or outside the allowed range (9 PM to 10 AM). It means that the specified promotional time period does not adhere to the defined constraints or rules.

EC_SE_CATEGORY_BLOCK

This error code indicates that the requested category of service entity (SE) has been blocked. It means that the particular category or type of service entity is restricted or prohibited from being used. Resolving this error typically check the category of service entity or DND consent on a specific number.

EC_CONSENT_FAILED

General error code for Consent.

EC_SCRUBBING_FAILED

General error code in case of any exceptions.

EC_TLV_PEID_NOT_FOUND

This error code suggests that the requested Principal Entity ID (PEID) within the TLV structure was not found. It means that the system or service could not locate the specified PEID within the TLV data. Verifying the correct usage and presence of the PEID within the TLV structure in the SMPP request can help resolve this error.

EC_TLV_TMPID_NOT_FOUND

This error code signifies that the requested Template ID within the TLV structure was not found. It means that the system or service was unable to locate the specified Template ID within the TLV data. Verifying the correct usage and presence of the Template ID within the TLV structure in the SMPP request can help address this error.

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.

EC_HEADER_SUSPENDED_DUE_TO_VALIDITY

This error signifies that the header has been suspended due to validity issues concerning DLT compliance. To resolve this, review and ensure that the header information complies with DLT regulations.

EC_HEADER_SUSPENDED_DUE_TO_USAGE

This error occurs when the header is suspended due to excessive usage that violates DLT regulations. Evaluate your SMS sending practices, consider reducing the volume of messages sent, and adhere to DLT guidelines.

EC_HEADER_SUSPENDED_DUE_TO_CUSTOMER

This error suggests that the header has been suspended due to issues related to the customer's DLT account. Contact your DLT service provider or support team to address and resolve customer-specific DLT compliance concerns.

EC_TEMPLATE_SUSPENDED_DUE_TO_VALIDITY

This error indicates that the template has been suspended due to validity problems concerning DLT compliance. To rectify this, review and correct the template content to ensure it aligns with DLT regulations and standards.

EC_TEMPLATE_SUSPENDED_DUE_TO_USAGE

This error arises when the template is suspended due to excessive usage that violates DLT regulations. Optimize your SMS templates or reduce the frequency of template usage to comply with DLT guidelines.

EC_TEMPLATE_SUSPENDED_DUE_TO_CUSTOMER

This error implies that the template has been suspended due to issues related to the customer's DLT compliance status. Engage with your DLT service provider or support team to address and resolve customer-specific DLT compliance matters.

REJECTED_INVALID_CONTACT 

REJECTED_VARIABLE_MISSED

REJECTED_PERSON_ALREADY_IN_FLOW

REJECTED_PERSON_NOT_ALLOWED_TO_REENTER

REJECTED_FLOW_ERROR_UNKNOWN

REJECTED_NOT_ENOUGH_CREDITS