ERROR: SMS Provider Specific Error Code 0x00000101

ERROR: SMS Provider Specific Error Code 0x00000101 SearchSearch
Author Message
binit bhaskar
New member
Username: Binitbhaskar

Post Number: 1
Registered: 04-2014
Posted on Wednesday, April 16, 2014 - 08:37 am:   

Hi,

I am trying to send sms using nowSms text application (127.0.0.1:8800/ ) but its not sending messages.

I have done the following steps
- configuring SMSC gateway, the Test connection was successful.
-Create sms user group

ANd then tried to send message using nowSms web applicaiton ( 127.0.0.1/8800) .
But I wonder, the web interface did not ask for username and password configured in sms user group of nowSms naive applciation.

After sending message using web apps, i can see the folowing message in the outbound queue..
ERROR: SMS Provider Specific Error Code 0x00000101

And the following information is present in the Event log
Warning...... No SMSC defined to route message

Please let me know if you need more info
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4870
Registered: 08-2008
Posted on Wednesday, April 16, 2014 - 01:46 pm:   

Hi Binit,

You seem to be experiencing 3 different issues, so let me explain them separately.


quote:

ANd then tried to send message using nowSms web applicaiton ( 127.0.0.1/8800) .
But I wonder, the web interface did not ask for username and password configured in sms user group of nowSms naive application.




There is a setting on the "Web" tab of the NowSMS configuration that says "Require authentication for web interface". This setting should be checked to require username/password. Historically this has defaulted to off/unchecked, but we are changing the default to on/checked in the next release.


quote:

After sending message using web apps, i can see the folowing message in the outbound queue..
ERROR: SMS Provider Specific Error Code 0x00000101




This means that when we tried to submit this message over the SMSC connection defined, the provider rejected the message with error code 101 hex or 257 decimal. This error code is not one defined in the SMPP protocol, but providers are allowed to add their own error codes (which is why we say it is "Provider Specific"). Unfortunately, this means only the provider can explain why you are getting this error code.

The most common issues for unknown errors relate to sender/source address issues.

Do you have a "Default Sender Address" defined for the connection? This is used as the sender/source address if none is present in the message submission (or is always used if "Allow Sender Address Override" is UNchecked). A blank sender address or a sender address that the provider will not allow you to use will sometimes result in a provider specific error.

Related to this is TON/NPI issues. NowSMS does a good job of automatically deciding the correct TON/NPI values based upon the number (more info here http://www.nowsms.com/ton-and-npi-settings-for-smpp-and-ucpemi).

TON stands for "Type Of Number" ... and essentially the types that are in common use are unknown, national, international, short code and alphanumeric.

One issue that can cause unusual errors is if a sender address is national, unknown or a short code, and the recipient is international. Similarly if the sender is international, but he recipient is in national or unknown format, some providers might not like it.

Did your provider give you TON/NPI instructions? If so, what were those instructions? You my want to try different sender/recipient combinations.

Of course, I am still just guessing about the problem, because we don't know what error code 0x101 (257) means to your provider.


quote:

And the following information is present in the Event log
Warning...... No SMSC defined to route message




NowSMS routes by recipient address.

It sounds like at this time you only have one SMSC connection, but you could have multiple and NowSMS needs to know how to route which messages to which connection.

Under properties for your SMPP connection there is a setting “Support any outbound message traffic”. If this is checked, then the connection is a default route ... any outbound message can be sent through it. If it is not checked, then only recipients listed in the “Preferred SMSC Connection for” list will be routed to this connection.

There is more explanation here http://www.nowsms.com/routing-sms-messages-to-a-specifc-smsc-route

Essentially what that error means is that for that particular message there was no SMSC connection defined that could route that message. (No default route)

--
Des
NowSMS Support