Expired errors

Expired errors SearchSearch
Author Message
Muhammad Adnan farooq
Frequent Contributor
Username: Adnan

Post Number: 56
Registered: 10-2009
Posted on Friday, November 05, 2010 - 06:03 pm:   


We are receiving expired errors with one of our customers using NowSMS SMPP platform.
Following are the 2 errors:
Expired err:023
Expired err:108

Please advise what does these error means.
Is there any way to avoid these expired erors in the future?
We believe that one of the expired error is received when the validity of SMS has expired. But we need to know which one is that & what does the other reflect to.

Please advise at your earliest convenience.

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7929
Registered: 10-2002
Posted on Friday, November 05, 2010 - 08:34 pm:   

Hi Adnan,

The errors are coming from your SMS provider.

They are not being generated by NowSMS, NowSMS is simply relaying them.

And they aren't necessarily errors. They are non-delivery receipts indicating that your SMS provider (or one of their upstream SMS providers) could not deliver the message within the message expiry (also known as validity) period ... most likely because a device is turned off. In other words, the error in this situation may be that the receiving device is powered off or is experiencing some other technical fault.

Let's talk about what the expiry period is.

Most SMS providers have a default expiry period for messages that you submit. It might be 3 days, 7 days, or in some cases, it may even be less.

That policy is set by your provider.

Additionally, some providers allow you to request a different validity period, up to a maximum validity period allowed by their system.

I would be hesitant to take any action without you first talking to your SMS service provider to determine their default expiry period, and their maximum expiry period.

That said, often it is hard to talk to someone at an SMS provider that understands this terminology.

So ... it may be possible to determine the default expiry period by examining the full text of these receipts. The de-facto standard receipt format includes two date/time stamps in the delivery or non-delivery receipt. "submit date:" is the yymmddhhmm on which the SMSC received the message, and "done date:" is the yymmddhhmm on which the SMSC delivered the message, or in this case, failed to deliver the message. (Note: Some providers use a 4 digit year instead of a 2 digit year.) For expired messages, you can determine the expiry period that was applied based upon the time difference between submit and done dates.

Once you've determined the default expiry period, you can make a decision as to whether or not you want to use a higher value when submitting to your provider.

NowSMS allows you to override the default expiry (or validity) period on a per outbound SMSC basis by adding the following setting to the [SMPP - server:port] section of SMSGW.INI:


The format of this parameter comes from the SMPP 3.4 specification. Basically change the 1 to 7 to make it a 7 day expiry.

All this said... You're only experiencing this problem with one of your customers, right?

In that case, while my explanation may be informative, it is possible that your customer is overriding the default validity period when they submit messages to you. NowSMS accepts the validity period override submitted by an SMPP client and relays that to an upstream provider. In this case, that value indicated by the customer will take precedence over your provider's default validity period setting, and over any value you set in SMSGW.INI.

So what you want to do is see what the difference is between the submit and done dates, and determine after what interval the messages are being expired.

If the value is small, then the problem may be that this customer is indicating a low validity period when they submit messages to you. And if they don't want their messages to be expired so quickly, they need to change it.

If the value is a day, or 3, or 7, then it may be the default validity period of your SMS provider. In that case, you need to make a decision as to whether or not the provider's default is ok for your system, or if you need to increase it with the SMSGW.INI setting that I mentioned above. (FYI ... this is not the type of setting that I would recommend changing late on a Friday afternoon ... you need to do some homework first.)