What Are NDD Calls? Understanding Non-Delivery and Its Impact

What are NDD Calls? Understanding Non-Delivery and Its Impact

I remember the frustration vividly. I’d meticulously crafted an email, poured over every detail, and hit send, expecting a swift reply from a crucial contact. Hours turned into days, and still, silence. It wasn't just a matter of them being busy; the email simply hadn't arrived. This is the kind of experience that can make you wonder, "What are NDD calls?" NDD calls, short for Non-Delivery or Non-Delivery Due to network issues, are the invisible roadblocks in our digital communication, impacting everything from personal messages to critical business transactions. Essentially, an NDD call signifies that a communication, most commonly an SMS or MMS message, failed to be delivered to its intended recipient. This can be due to a myriad of reasons, and understanding these can be the key to troubleshooting and ensuring your messages get through.

In the realm of telecommunications, especially with the widespread use of mobile devices and messaging applications, the seamless delivery of messages is something we often take for granted. However, when a message doesn't arrive, it can lead to confusion, missed opportunities, and significant operational disruptions. The term "NDD calls" primarily refers to situations where a Short Message Service (SMS) or Multimedia Messaging Service (MMS) message experiences a delivery failure. This isn't just about a delayed message; it's about a message that never reached its destination, potentially due to a technical glitch, network congestion, or recipient-side issues. For businesses relying on SMS for customer notifications, marketing campaigns, or two-factor authentication, understanding NDD calls is paramount for maintaining reliable communication channels.

This article aims to demystify what NDD calls are, explore the various reasons behind them, and delve into their implications across different sectors. We'll uncover the technical intricacies involved, the roles of different network components, and the practical strategies for mitigating their occurrence. My own experiences, both as a user encountering undelivered messages and as someone involved in managing communication systems, have highlighted the critical need for a comprehensive understanding of this often-overlooked aspect of digital communication.

Deconstructing the NDD Call: What It Means in Practice

Defining Non-Delivery in the Context of Mobile Networks

At its core, an NDD call, or a non-delivery report (NDR), is a notification sent back to the sender by the network or the messaging service indicating that a message could not be successfully delivered to the recipient's device. This notification is often automated and is a critical feedback mechanism. It’s not just a simple "message failed" blurb; it can contain specific error codes or descriptions that hint at the root cause of the failure. For instance, a sender might receive a code indicating the recipient's mailbox is full, or that the recipient's device is unreachable. This feedback loop is vital because, without it, a sender would have no way of knowing their message never arrived, leading to assumptions of receipt and potential breakdowns in communication.

When we talk about NDD calls, we're typically referring to the signaling and reporting mechanisms within the Short Message Service (SMS) and Multimedia Messaging Service (MMS) infrastructure. These services, though seemingly simple, involve a complex interplay of mobile devices, cell towers, Short Message Service Centers (SMSCs), and the broader telecommunications network. An NDD call signifies a break in this chain. It’s the network’s way of saying, "I tried, but I couldn't get this message to where it needed to go." Understanding the difference between a temporary issue (like network congestion) and a persistent problem (like an invalid number) is key to effectively addressing NDDs. The terminology can sometimes be fluid; you might hear it referred to as a "delivery failure," "undeliverable message," or simply an "NDR." Regardless of the exact phrasing, the underlying meaning is the same: the message did not reach its intended destination.

The Journey of a Message and Where It Can Go Wrong

To truly grasp what NDD calls are, it’s helpful to visualize the path a message takes. When you send an SMS or MMS, it doesn't travel directly from your phone to the recipient's. Instead, it's routed through a series of network components:

Your Mobile Device: You compose and send the message.
Cell Tower: Your device connects to the nearest cell tower, which forwards the message to your carrier's network.
Short Message Service Center (SMSC): This is the central hub for SMS messages. It receives your message, stores it temporarily, and then attempts to deliver it to the recipient's mobile network. The SMSC is responsible for managing message queues, handling delivery reports, and retrying delivery if necessary.
Recipient's Mobile Network: If the recipient is on a different network, the message is forwarded to their carrier.
Recipient's Cell Tower: The recipient's network routes the message to their specific cell tower.
Recipient's Mobile Device: The cell tower delivers the message to the recipient's phone.

An NDD call can occur at any point along this journey. For example, if the SMSC is experiencing a backlog of messages, it might fail to process your outgoing message promptly. Or, if the recipient's phone is switched off or out of network coverage, their network cannot deliver the message, leading to an NDD report back to the SMSC and eventually to you.

Distinguishing NDD Calls from Other Message Failures

It's important to distinguish NDD calls from other types of message-related issues. For instance:

Delayed Messages: A message might be temporarily held up due to network congestion but will eventually be delivered. This is not an NDD call.
Spam Filtering: Some messages might be blocked by the recipient's carrier or device as spam before they even reach the SMSC. While this also results in non-delivery, the reporting mechanism might differ from a standard NDD report.
Application-Specific Errors: If you're using a messaging app like WhatsApp or Signal, the delivery failures are managed by the app's servers, not the traditional SMS/MMS infrastructure. While the principle of non-delivery remains, the technical underpinnings and reporting are different.

NDD calls specifically pertain to the underlying SMS/MMS network's inability to complete the delivery. This understanding is crucial, especially for businesses that might use various communication channels and need to pinpoint where a failure is occurring.

Common Causes of NDD Calls: A Deep Dive

The reasons behind a non-delivery report can be diverse, ranging from simple user errors to complex network infrastructure problems. Identifying the specific cause is the first step toward resolution. Let's break down some of the most frequent culprits.

Recipient-Side Issues: When the Problem Isn't with the Sender

Often, the issue lies with the recipient's device or account, and this is a significant category of NDD causes.

Recipient's Phone is Off or Out of Coverage: This is perhaps the most straightforward reason. If the recipient's phone is powered off, has a dead battery, or is in an area with no mobile signal, the network cannot deliver the message. The SMSC will typically hold the message for a certain period (e.g., 24-72 hours) and retry delivery. If delivery is still unsuccessful after this period, an NDD report is generated.
Recipient's Inbox is Full: Mobile phones and SIM cards have a limited capacity for storing messages. If a recipient has a large backlog of unread messages, their inbox can become full, preventing new messages from being received. This is more common with older devices or with users who rarely clear their message history.
Recipient's Phone Number is Incorrect or Invalid: A simple typo when entering a phone number is a classic cause of NDD. The network will attempt delivery, but since the number doesn't exist or isn't active, the delivery will fail, triggering an NDD report. It's also possible that a number was once valid but has since been deactivated by the carrier.
Recipient Has Blocked the Sender: Many mobile devices and carriers offer functionality to block unwanted calls and messages from specific numbers. If a recipient has blocked your number, any messages you send will be rejected by their network or device, resulting in an NDD.
Recipient Has Moved to a Different Network: If a recipient has ported their number to a new carrier, and the routing information hasn't been updated correctly, messages might fail to reach them. While number portability aims to prevent this, occasional glitches can occur.
Recipient's Device Settings: In some cases, specific device settings, such as airplane mode being constantly enabled, or certain message blocking features within the phone's OS, can prevent message delivery.

Sender-Side Issues: When the Problem Originates from Your End

While less common for individual users, sender-side issues are particularly relevant for businesses sending bulk messages.

Invalid Sender ID/Short Code: For certain types of messaging (like promotional SMS), a specific sender ID or short code is used. If this is not properly registered or configured, messages may be rejected by the network.
Message Content Violations: Some carriers have strict content policies for SMS/MMS. Messages containing spam-like keywords, phishing attempts, or adult content might be automatically flagged and blocked, leading to NDD. This is a form of proactive network security.
Over-Subscription or Sending Limits: If a sender is attempting to send a very high volume of messages in a short period, they might hit sending limits imposed by their carrier or messaging provider. This can result in subsequent messages being dropped.
Incorrect SMSC Configuration: For businesses managing their own messaging gateways, an improperly configured SMSC can lead to delivery failures.

Network and Infrastructure Issues: The Invisible Bottlenecks

The telecommunications network itself, while generally robust, can experience problems that lead to NDD calls.

Network Congestion: During peak times, such as holidays or major events, mobile networks can become heavily congested. This can lead to delays in message processing and, in some cases, outright delivery failures. While typically temporary, severe congestion can result in NDDs.
SMSC Overload or Malfunction: The SMSC is a critical component. If it's overloaded with messages to process, or if it experiences a technical fault, it can fail to deliver messages correctly, leading to NDD reports.
Inter-Carrier Routing Problems: When messages need to travel between different mobile carriers, there are complex routing agreements and systems in place. Glitches or failures in these inter-carrier connections can cause messages to get lost.
Temporary Network Outages: Like any complex infrastructure, cell towers or parts of the mobile network can experience temporary outages due to technical issues, maintenance, or environmental factors. During these outages, messages routed through the affected areas will fail to deliver.
International Gateway Issues: For international messages, the gateways that connect different countries' networks can also be points of failure.

Specifics for MMS: The Added Complexity

MMS messages, which can include images, videos, and audio, are more complex than SMS and have additional potential failure points:

File Size Limits: MMS has strict file size limitations. If an attached file exceeds the allowed size, the message will fail to send.
File Format Incompatibility: The recipient's device might not support the format of the media file attached.
MMS Gateway Issues: MMS relies on specific gateways (MMSCs) which can also experience congestion or malfunctions.
Data Connection Requirement: For MMS delivery, both the sender and receiver typically need an active data connection (either cellular data or Wi-Fi calling if supported and configured). If either party lacks this, delivery can fail.

The Impact of NDD Calls: Why They Matter

The consequences of an NDD call can range from a minor inconvenience to a significant business disruption. Understanding these impacts helps to underscore the importance of reliable message delivery.

For Individuals: Missed Connections and Frustration

On a personal level, NDD calls can lead to:

Missed Important Information: Not receiving a message from a friend about a change of plans, an urgent request from family, or a notification about an appointment can be frustrating and lead to missed opportunities or misunderstandings.
Feeling Ignored: If messages consistently fail to deliver, the sender might feel like they are being ignored, even if the issue is technical.
Wasted Effort: Spending time crafting a message only for it to never be received is a direct waste of effort.

For Businesses: Financial and Reputational Damage

For businesses, the implications of NDD calls are often far more severe:

Lost Sales and Revenue: If customers don't receive promotional messages, order confirmations, shipping updates, or password reset links, they may abandon purchases, experience issues with orders, or be unable to access their accounts. This directly impacts revenue.
Poor Customer Experience: Unreliable communication erodes customer trust and satisfaction. Customers expect timely and accurate information, especially regarding their transactions. Persistent NDDs lead to complaints and negative reviews.
Operational Inefficiencies: Businesses often use SMS for critical operational communications, such as appointment reminders, service alerts, or delivery notifications. If these messages fail, it can lead to missed appointments, service disruptions, and increased costs associated with manual follow-ups.
Compliance and Regulatory Issues: In certain industries, timely notifications are a regulatory requirement. Failure to deliver due to NDDs could lead to non-compliance and potential penalties.
Brand Damage: A reputation for poor communication can be difficult to repair. If a brand is perceived as unreliable, customers will likely turn to competitors.
Increased Support Costs: When messages fail, customers often contact support desks seeking information or assistance, increasing the load on support teams and incurring additional operational costs.

Specific Business Scenarios Affected by NDDs

Consider these specific scenarios:

Two-Factor Authentication (2FA): If a 2FA code SMS fails to deliver, a customer cannot log into their account, leading to immediate frustration and potential security concerns if they perceive their account is compromised.
Appointment Reminders: A missed appointment reminder can result in a no-show for a doctor's office, a salon, or a service technician, leading to lost revenue for the business and inconvenience for the customer.
Urgent Alerts: Banks sending fraud alerts, or utilities sending outage notifications, rely on immediate message delivery. NDDs in these cases can have significant consequences.
Marketing Campaigns: While perhaps less critical than transactional messages, failed delivery of marketing SMS means missed opportunities to engage customers and drive sales.

The cumulative effect of these issues can be substantial, impacting a business's bottom line and its long-term viability.

Diagnosing and Troubleshooting NDD Calls: A Practical Guide

When you suspect NDD calls are happening, a systematic approach to diagnosis and troubleshooting is essential. This is where the rubber meets the road, and understanding how to investigate can save significant time and resources.

For Individual Users: Simple Checks First

If you're experiencing undelivered messages as an individual, start with these simple steps:

Verify the Recipient's Number: Double-check that you have the correct phone number, including the country code if necessary. Even a single digit error can cause a delivery failure.
Check Your Signal Strength: Ensure you have a stable mobile signal when sending messages.
Restart Your Phone: A simple reboot can often resolve temporary glitches in your device or network connection.
Check Your Message Inbox: Make sure your own message inbox isn't full.
Verify Recipient's Phone Status: If possible, confirm with the recipient that their phone is on, has battery, and is in an area with coverage.
Try Sending a Different Message: Sometimes, the content of the message itself can be an issue (though this is rarer for basic SMS). Try sending a short, simple text.
Check for Blocked Numbers: Ensure you haven't accidentally blocked the recipient or that they haven't blocked you.
Test with Another Recipient: Send a message to a different, known working number to see if the issue is specific to one recipient or a broader problem.

For Businesses: A More Technical Approach

Businesses relying on SMS/MMS for communication need a more robust strategy for identifying and addressing NDDs. This often involves working with their mobile carrier or messaging service provider.

Step-by-Step Troubleshooting Checklist for Businesses:

Implement Delivery Reporting (DLRs): Ensure your messaging platform is configured to request and receive Delivery Receipt Reports (DRRs) from the network. These reports provide detailed status updates, including whether a message was delivered, failed, or is pending.
Monitor NDD Reports Regularly: Establish a system for monitoring incoming NDD reports. This might involve automated alerts or regular manual checks of logs.
Analyze NDD Error Codes: NDD reports often come with specific error codes (e.g., 0x80070002, 140, 550). Understand what these codes signify. Your messaging provider or carrier should be able to provide a lookup table for these codes. Common codes might indicate:
- Number Not Found/Invalid Number: The phone number is incorrect or no longer in service.
- Message Rejected by Network: The message was blocked due to content policies or network restrictions.
- Recipient's Device Unreachable: The recipient's phone was off or out of coverage for an extended period.
- Message Store Full: The recipient's message inbox was full.
- Network Congestion: Temporary issues within the mobile network.
Maintain an Up-to-Date Contact List: Regularly clean and validate your contact database. Remove numbers that are known to be invalid or disconnected. Use services that can help verify phone number validity.
Segment Your Audience for Testing: When launching a new campaign or sending critical messages, consider sending to a small, representative segment of your audience first to catch any delivery issues before a full rollout.
Collaborate with Your Messaging Provider/Carrier: If you are consistently seeing NDDs for specific numbers or in general, engage with your SMS gateway provider or mobile carrier. They can investigate network-level issues, routing problems, or potential blocks on their end.
Test Different Messaging Types: If you use both SMS and MMS, test their delivery separately to pinpoint if the issue is specific to one service.
Review Message Content: If NDDs are occurring for specific messages, review the content for any keywords or patterns that might trigger network filters. Avoid excessive use of special characters, ALL CAPS, or common spam phrases.
Investigate Sender ID Issues: Ensure your Sender ID (alphanumeric or short code) is properly registered and approved by carriers, especially if you're sending to users in different countries.
Implement Retry Logic: For non-critical messages, your messaging platform should have built-in logic to retry sending messages that fail due to temporary network issues. However, be cautious not to overwhelm the network with excessive retries.
Monitor Network Status and Outages: Stay informed about any reported outages or maintenance impacting your carrier or key network partners.

Understanding Delivery Receipt Reports (DRRs)

DRRs are the feedback mechanism that tells you about message delivery status. They are essential for identifying NDDs. A typical DRR might contain fields like:

Message ID: A unique identifier for the message.
Recipient Number: The phone number the message was sent to.
Status: This is the crucial part. It can be:

Delivered: The message successfully reached the recipient's device.
Failed: The message could not be delivered. This is where the NDD report comes in.
Pending: The message is still being processed and has not yet been delivered or definitively failed.
Expired: The message could not be delivered within the retention period and has expired.

Error Code: If the status is 'Failed,' an error code will usually be provided to indicate the reason.
Timestamp: When the status was updated.

Effectively processing and acting upon these DRRs is key to managing message delivery for any business.

NDD Calls in the Context of Modern Communication: Beyond SMS

While NDD calls are traditionally associated with SMS and MMS, the concept of message delivery failure extends to other communication channels, albeit with different technical underpinnings and terminology.

Over-the-Top (OTT) Messaging Apps

Apps like WhatsApp, Telegram, Signal, and Facebook Messenger operate on an internet connection rather than the cellular SMS network. When a message fails to deliver in these apps:

Reasons: Typically due to the recipient being offline, having a poor internet connection, or having uninstalled the app. The app's servers manage the delivery status.
Indicators: Apps usually provide visual cues (e.g., a single checkmark for sent, double checkmarks for delivered, often specific colors or icons for read status) to indicate delivery progress. A failure might simply mean the second checkmark never appears, or the message remains in a "sending" state.
Reporting: Direct NDD reports back to the sender in the traditional sense are less common. Instead, the app itself indicates the delivery failure.

While the technology differs, the *impact* of non-delivery—missed communication, confusion—remains the same.

Email Delivery Failures

Email systems also have mechanisms for reporting delivery failures, often through an "undeliverable" bounce-back message or an error code. These failures can be due to:

Invalid Email Address: The recipient's email address doesn't exist.
Mailbox Full: The recipient's inbox has exceeded its storage limit.
Spam Filtering: The recipient's mail server or client flagged the email as spam.
Server Issues: Temporary problems with the recipient's mail server.
Recipient Server Rejection: The recipient's server might reject the email for various reasons (e.g., sender reputation, IP address blocklisting).

These email failures, like NDD calls for SMS, highlight the persistent challenge of ensuring digital messages reach their intended destination.

API-Based Messaging and Enterprise Solutions

Businesses using Application Programming Interfaces (APIs) to send messages (SMS, email, push notifications, etc.) rely heavily on delivery reports provided by the API provider. These reports are the modern equivalent of NDD calls, offering structured data on delivery success or failure. A robust API integration will meticulously log and analyze these reports to manage communication flow and identify issues. The underlying causes of failure can still be the same as described for SMS or email, but the reporting and programmatic handling are more sophisticated.

Mitigation Strategies: Proactive Measures Against NDD Calls

Preventing NDD calls is always better than dealing with their aftermath. For businesses, implementing proactive strategies is crucial for maintaining reliable communication.

1. Data Hygiene and Validation

The most common cause of sender-side NDDs is an invalid or incorrect phone number. Implementing rigorous data hygiene practices is paramount:

Real-time Number Verification: Utilize services that can verify phone number validity in real-time at the point of data capture (e.g., during signup forms). This checks if a number is active and can receive messages.
Regular Data Cleansing: Periodically audit your contact database to identify and remove disconnected or invalid numbers.
Opt-in Mechanisms: Ensure you have proper consent and confirmation from users when they provide their phone numbers, ideally through a double opt-in process where they confirm their number via SMS. This not only ensures validity but also compliance with regulations like TCPA.

2. Strategic Messaging Practices

How you send messages can significantly impact their delivery success:

Sending Volume Management: Avoid sending massive volumes of messages in very short bursts. Pace your campaigns, especially if you're sending to a large list.
Throttling and Rate Limiting: Implement internal rate limiting on your sending systems to avoid overwhelming network gateways.
Time Zone Awareness: Send messages at appropriate times for the recipient's time zone to avoid issues with devices being off or in a state where they might not receive notifications.
Message Content Optimization: Craft clear, concise messages that are less likely to be flagged as spam. Avoid jargon or excessively promotional language that might trigger filters.

3. Choosing the Right Communication Partner

The service provider you work with for your SMS/MMS communication plays a critical role:

Reputable Providers: Partner with established and reputable A2P (Application-to-Person) messaging providers that have strong relationships with mobile carriers and understand network regulations.
Robust Delivery Reporting: Ensure your provider offers comprehensive and timely delivery reports, including detailed error codes.
Support and Expertise: Choose a provider that offers strong technical support and can assist in diagnosing and resolving NDD issues.
Network Quality: Inquire about the provider's network infrastructure and their direct connections to various carriers. Direct connections often lead to better delivery rates.

4. Understanding Carrier Regulations and Compliance

Mobile carriers have specific rules for message sending, especially for commercial traffic. Adhering to these is crucial:

Sender ID Registration: In many regions, alphanumeric sender IDs must be registered and approved by carriers. Short codes also require a formal application process.
Opt-Out Mechanisms: For marketing messages, providing a clear and easy opt-out mechanism (e.g., "Text STOP to unsubscribe") is often mandatory and helps maintain a healthy subscriber list.
Content Restrictions: Be aware of and comply with carrier policies regarding prohibited content (e.g., illegal activities, hate speech, adult content).

5. Leveraging Advanced Messaging Technologies

While SMS and MMS are reliable, they have limitations. Consider alternatives or complementary channels:

Rich Communication Services (RCS): As RCS becomes more widely adopted, it offers a richer messaging experience with read receipts, typing indicators, and rich media capabilities, all managed over IP. While not a direct replacement for SMS in all scenarios, it's a promising evolution.
Integration with Other Channels: For critical communications, consider a multi-channel approach. If an SMS fails, you might have a fallback to email or a push notification via a mobile app.

Frequently Asked Questions about NDD Calls

How do I know if my message has failed to deliver due to an NDD?

If you are an individual user, you might not always receive explicit notifications for every failed SMS. However, if you've sent a message and haven't received a reply and suspect it wasn't delivered, you can try the troubleshooting steps mentioned earlier. For businesses using an A2P messaging platform or API, delivery status is typically provided through Delivery Receipt Reports (DRRs). These reports will explicitly state the status of each message sent, with 'Failed' or specific error codes indicating an NDD. Your messaging platform should provide a dashboard or logs to view these statuses.

Why is my SMS message being marked as undeliverable?

An SMS message can be marked as undeliverable for a multitude of reasons, falling broadly into recipient-side issues, sender-side issues, and network problems. The most common recipient-side issues include the recipient's phone being switched off, out of network coverage, or having a full message inbox. Incorrect or invalid phone numbers are also a frequent culprit. Sender-side issues might involve an invalid sender ID or content that violates carrier policies. Network congestion or temporary outages within the mobile operator's infrastructure can also lead to delivery failures. For businesses, improper configuration of their messaging gateway or exceeding sending limits can also cause messages to be marked as undeliverable.

Can I resend a message that resulted in an NDD call?

Yes, in many cases, you can resend a message that resulted in an NDD call. However, it's crucial to understand *why* it failed first. If the failure was due to a temporary issue, like the recipient's phone being off, resending after a short while might be successful. If the number is permanently invalid, resending will only result in another failure and potentially incur additional costs. For businesses, automated retry logic can be implemented for certain types of failures (e.g., temporary network errors). However, it's generally advisable to investigate the root cause of the NDD before repeatedly resending, especially if the failure is persistent.

What is the difference between an NDD and a delayed message?

The key difference lies in the final outcome. A delayed message is one that is taking longer than usual to reach its destination, often due to network congestion or temporary issues, but is expected to be delivered eventually. An NDD call, or non-delivery report, signifies that the message *failed* to be delivered within the network's defined parameters and is unlikely to reach the recipient. It's a definitive notification of failure, whereas a delay is a temporary status. SMS networks have a built-in retention period for undelivered messages, during which they will attempt retries. If delivery is not achieved within this period, it escalates to a non-delivery status.

How can businesses improve their SMS delivery rates and reduce NDDs?

Businesses can significantly improve their SMS delivery rates and reduce NDDs through a multi-faceted approach. Firstly, maintaining high data hygiene by regularly validating and cleansing contact lists is essential to ensure messages are sent to active and correct phone numbers. Secondly, partnering with a reputable A2P messaging provider that has strong carrier relationships and offers robust delivery reporting is crucial. Implementing smart sending practices, such as managing sending volumes, respecting time zones, and optimizing message content to avoid spam filters, also plays a vital role. Finally, understanding and adhering to carrier regulations, including proper sender ID registration and opt-out mechanisms, can prevent messages from being blocked by the network. Proactive monitoring of delivery reports and swift investigation of recurring NDDs are also key to continuous improvement.

What are common error codes associated with NDD calls?

Error codes associated with NDD calls provide specific insights into the reason for delivery failure. While the exact codes can vary between carriers and messaging protocols, some common categories and examples include:

Invalid Number/Unassigned Number: Codes indicating the phone number itself is incorrect, no longer in service, or not assigned. Examples might include codes like '12' (Unknown subscriber) or '140' (Invalid number format).
Network/Routing Issues: Codes related to problems within the mobile network or between networks. This could encompass congestion, temporary outages, or routing errors.
Recipient Device Issues: Codes indicating problems on the recipient's end, such as a full message inbox or a device that is unreachable for an extended period. Codes like '27' (Invalid message reference) or '22' (Network error) can sometimes point to these issues.
Message Rejected by Network: Codes signifying that the message was blocked by the carrier due to policy violations, spam detection, or other network-imposed restrictions.

It is highly recommended to consult the documentation provided by your specific SMS gateway provider or mobile carrier for a definitive list and explanation of error codes they utilize, as these can be quite specific and technical.

Does NDD apply to MMS messages as well as SMS?

Yes, the concept of non-delivery, which leads to an NDD report, absolutely applies to MMS (Multimedia Messaging Service) messages as well as SMS (Short Message Service). In fact, MMS messages have additional complexities and potential failure points due to their multimedia content. Reasons for MMS non-delivery can include exceeding file size limits for attachments, incompatible media formats on the recipient's device, issues with the MMS Gateway (MMSC), or the recipient's device not supporting MMS. When an MMS message fails to deliver, the network infrastructure will still generate a non-delivery report back to the sender, indicating the failure, much like with SMS.

The investigation into why an NDD occurred for an MMS message would involve checking not only the standard SMS delivery factors but also the specific aspects of the multimedia content and the MMS transmission pathway. Therefore, while the underlying principle of non-delivery is the same, the specific causes and troubleshooting steps for MMS NDDs can be more involved.

In conclusion, understanding what NDD calls are is fundamental for anyone relying on mobile messaging for communication, whether personal or professional. It's about recognizing that messages don't always reach their destination and knowing why that happens. By delving into the causes, understanding the impacts, and employing diligent troubleshooting and mitigation strategies, we can navigate the complexities of digital communication more effectively and ensure our messages get through.