Regarding SMS Provider Specific Error Code 0x00000009

Regarding SMS Provider Specific Error Code 0x00000009 SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through August 22, 2012 » Regarding SMS Provider Specific Error Code 0x00000009 « Previous || Next »
Author Message
Johnny
New member
Username: Johny

Post Number: 32
Registered: 02-2009
Posted on Friday, August 03, 2012 - 07:16 am:   

Hi

I’m use Now SMS v2011.07.05

I have a problem

Today, when I send text message, I don’t receive the message.

So I check log messssage.

Log message is as follow

2012-08-03 14:51:14,479D3EDF.req,121.50.xx.xx,24001216,Retry Pending - ERROR: SMS Provider Specific Error Code 0x00000009 -- SMPP - 203.229.xxx.xx:xxx,Sender=1110
2012-08-03 14:57:14,479D3EDF.req,121.50.xx.xx,24001216,Retry Pending - ERROR: Timeout waiting for response from server or lost connection -- SMPP - 203.229.247.33:6208,Sender=1110

After I check this log message, I reboot Now SMS server.
Message is sent and received.
But NowSMS cant’ send message after 30minute.
Message is stored in the Q folder.
And error message is same.
This situation is repeated

What is the problem?

Now, Many people don’t send message.

Please answer ASAP

Thanks
application/octet-stream
SMPPDEBUG.LOG (76.0 k)
application/octet-stream
SMSDEBUG.LOG (87.0 k)
application/octet-stream
SMSOUT-20120803.LOG (36.2 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4056
Registered: 08-2008
Posted on Monday, August 06, 2012 - 07:18 pm:   

Hi Johnny,

Assuming that you haven't changed any settings, you need to ask your SMPP provider. SMPP error 9 is a "reserved" error code, so it is not a normal error code that a provider should be returning.

If all messages are being rejected, I would suspect a system error on the other system, or an issue specific to your account on that system.

However, in your case, only some messages are failing. And the messages that encounter problems are failing on each retry. This leads me to suspect that there is something about these messages that your provider does not like.

I've spent some time looking at some of the messages in the debug logs ... 479D3F18.req and 479D3EDF.req.

And it looks to me like invalid UDH.

I see a PID value of 41, and a DCS value of D8.

UDH is indicated to be present, but it seems to be null.

What exactly is the content of these messages? (REQ file contents? How exactly were they submitted to NowSMS?)

Are you sure the content is valid?

I suspect your provider may just be rejecting them because the UDH is invalid.

Other messages appear to be going through, but these invalid ones are being failing.

--
Des
NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics