Problems interfacing a SMSC

Problems interfacing a SMSC SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 31, 2007 » Problems interfacing a SMSC « Previous || Next »
Author Message
Carlos Mercado
New member
Username: Cmercado

Post Number: 2
Registered: 05-2007
Posted on Friday, June 22, 2007 - 03:25 pm:   

I'm sending messages trough this SMSC without setting &Sender=. Massages are received ok. Once I set the &Sender=29960 messages are not delivered, the SMSC returns ok, but debugging at the SMSC we found the below problem (encoding???). Why adding a variable will cause a encoding problem? Can you tech team can point me to a possible solution?

===============================================
Query Result
===============================================
Status : WAITING_DELIVERY
Destination MSISDN : 7877173224
External reference # : NONE
Internal reference # : 2
MessageID : 185711216
Originator MSISDN : 29960
Callback Number : 29960
Priority : SMS_PRI_ZERO
Deferred Delivery time : NONE
Expiration time : Fri Jun 22 17:01:44 2007
Max. delivery attempt # : 167
# of delivery attempts : 154
Data Coding Scheme : ASCII
Notifications : -----------
Submit time : Mon Jun 18 17:01:44 2007
Query time : Tue Jun 19 15:52:58 2007
Last delivery time : Tue Jun 19 15:35:37 2007
Last failure reason : ENCODING_PROBLEM
Length of the text msg : 5
Short Message : wepa2
===============================================
Carlos Mercado
New member
Username: Cmercado

Post Number: 3
Registered: 05-2007
Posted on Friday, June 22, 2007 - 03:45 pm:   

Quick update -- I just receive an e-mail form Lisa Smith and indicate to test using the "Default Sender Address" at the SMPP connection def. I just did that instead of using the &Sender and still have the problem.
Carlos Mercado
New member
Username: Cmercado

Post Number: 4
Registered: 05-2007
Posted on Friday, June 22, 2007 - 04:03 pm:   

Update- This SMSC has other NOWSMS instances that could use the Sender parameter. So I'm suspicion that might be something on the configuration.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7260
Registered: 10-2002
Posted on Friday, June 22, 2007 - 04:19 pm:   

Hi Carlos,

My guess would be that the sender value that you are using is not considered to be valid (for your account) by this provider.

So let me ask you some questions ... to determine what does work, and what does not work ... and better understand your configuration.

a.) "Default Sender Address" blank. No "&Sender=" parameter in the URL submission. Works? (I think you indicated "Yes".)

b.) "Default Sender Address" blank. "&Sender=29960" in the URL submission. Works? (I think you indicated "No".)

c.) "Default Sender Address" = "29960". No "&Sender=" parameter in the URL submission. Works? (I think you indicated "No".)

If I am correct that "a" works, but "b" and "c" do not ... then my conclusion would be that the SMS provider here does not think that "29960" is a valid sender/source address for you to use. There may be restrictions on what values are allowed ... and this is outside of our control, and outside of your control ... it is under the control of the provider.

When you send using approach "a", what is the sender address shown as on the receiving handset? This may provide a clue as to what the provider is expecting for the sender address value.

Now, if the provider swears that "29960" should be a valid sender address for you to use, there is one other idea that I have. When the sender address is numeric, and 5 digits or less, NowSMS, by default, applies source_addr_ton=3 for the type of sender address. (This is the value that is normally used for short codes, indicating that the type of number in the sender address is "network specific"). You may want to try going into "Advanced Settings" for the SMPP Connection in NowSMS, and setting the "Source TON" to 0 for unknown.

You may also want to ask the provider for more details about what SMPP values they expect you to use for the connection. Tell us these details, and we can usually figure out how to translate from their terminology into ours.

-bn
Carlos Mercado
New member
Username: Cmercado

Post Number: 5
Registered: 05-2007
Posted on Friday, June 22, 2007 - 06:30 pm:   

Bryce,
Thanks for your point. I just troubleshoot with the provider and catch that I have leave default(blank) the TON and NPI. The carrier only support NPI set 1. When I do sent without the Sender the is NPI = 0 so it pass. When I did include the sender variable the then is NPI = 3 and then the SMSC give the very "accurate and illustrative" message of ENCODING PROBLEM. I just force to the the NPI to 1 for the SMPP connection and works fine.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7261
Registered: 10-2002
Posted on Friday, June 22, 2007 - 07:15 pm:   

Hi Carlos,

That is interesting. I hadn't thought that the NPI setting might be an issue.

If the sender is alpha, a short code (5 digits or less), or blank, we use NPI=0. In all other situations we use NPI=1.

-bn

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