| SMPP issue |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 23, 2009 ⬆ |
◄ ► |
| Author | Message | |||||
| Muhammad Adnan farooq New member Username: Adnan Post Number: 1 Registered: 10-2009 |
I am running into an issue while tying to send sms messages, they are being rejected with an error code 0x0A. Looking at the NowSMS website: http://blog.nowsms.com/search/label/SMPP%20errors I see this is an indication of an invalid source address. Here is the data being submitted to the SMSC: 00 00 00 3d 00 00 00 04 00 00 00 00 00 00 00 02 00 00 01 00 00 01 31 32 30 34 39 36 32 35 31 35 32 00 00 00 00 00 00 00 00 00 00 11 74 65 73 74 20 6d 65 73 73 61 67 65 20 61 73 64 66 The source address data I am using: source TON - 0 source NPI - 1 source address - 0 The registered_delivery flag is not set, so this appears to be correct. Can you see what I am missing? Please find the attached SMPP log file.
| |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1357 Registered: 08-2008 |
Hi, Most SMPP providers require a source/sender address. Others apply an account default if you leave it blank. In the properties for the SMPP connection in NowSMS, set the Default Sender Address with an appropriate value. -- Des NowSMS Support | |||||
| Muhammad Adnan farooq New member Username: Adnan Post Number: 2 Registered: 10-2009 |
Customer is unable to send SMS to US & Canada SIMs both. Please find the attached SMPP log for sending SMS to US SIM. can you please let us know the actual root cause of this SMS failure. | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1363 Registered: 08-2008 |
Hi, The rejection is coming from your service provider, so they would need to explain it. I have no visibility into your service provider's system, so I can only guess why the messages are being rejected: My guesses ... 1.) The sender address is still blank. So I would repeat the previous advice:
2.) In this latest log, the message appears to be getting rejected with SMPP error code 66 ESME_RX_R_APPN (ESME Receiver Reject Message Error Code). This means that the provider is actively rejecting the message for some reason. Only the provider knows why ... it could be #1, or my other guess is that the phone number is not valid ... "500" is an unusual USA area code, and the number is likely invalid. (http://en.wikipedia.org/wiki/Area_code_500) -- Des NowSMS Support | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1364 Registered: 08-2008 |
I also notice that the log you are including appears to be a client log, not a NowSMS log. It would help to see the SMPPDEBUG.LOG generated by NowSMS, so that we could see the actual interaction between NowSMS and your service provider. It is possible that you have configured a sender address in NowSMS, and that #1 is not a problem. However, the sender address you are using might not be valid/acceptable for USA/Canada recipients. Your provider may have rules about what a valid sender address is for those countries. In particular, in many cases there are rules about "unreply-able" messages. In particular, alphanumeric sender is not generally acceptable in North America. -- Des NowSMS Support | |||||
| Muhammad Adnan farooq New member Username: Adnan Post Number: 3 Registered: 10-2009 |
Please find the attached logs at server end for different dates. Please compare them with the client logs & let us know the root cause. Thanks Muhammad | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1379 Registered: 08-2008 |
Hi Muhammed, These logs don't tell me that much. (It would be useful to see an SMPPDEBUG.LOG. That log file is only generated if the SMSDEBUG.LOG is enabled.) But, what they do show me is this ... 1.) If you send to a phone number without specifying that it is international (no "+"), the SMPP provider returns error code 0x0A (ESME_RINVSRCADR - invalid source address). 2.) If you send to a US phone number in international format, the SMPP provider returns error code 0x66 (ESME_RX_R_APPN - Receiver Reject Message Error Code). I think your sender address is a problem. It looks like this is the sender address value you are using ... 41080161. That number is too long to be a short code. I suspect the error 0x66 is occurring because you're specifying a sender address in national number format (and an invalid number at that), but the recipient address is in international format. The 0x0A error is occurring because the sender address is not valid. If you are unsure what value is valid for your sender address, then you really should ask your SMPP provider. -- Des NowSMS Support | |||||
| Muhammad Adnan farooq New member Username: Adnan Post Number: 4 Registered: 10-2009 |
41080161 is a US short code & customer should be able to send sms to US numbers by using this code. But it should not be able to send sms to canadian number as they are using US short code only. Please guide why they are unable to send sms to US SIMs even they are using US short code. | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1380 Registered: 08-2008 |
That may be the important piece of information that was missing! Edit SMSGW.INI, and under the [SMSGW] header, add MaxSMPPShortCodeLen=8 This is going to set the TON for the sender address to indicate that the sender is a short code. -- Des NowSMS Support | |||||
| Muhammad Adnan farooq New member Username: Adnan Post Number: 5 Registered: 10-2009 |
Please find the debud log for your views. Please let us know if you find any thing. Please note one thing that we have number of customers using NowSMS & are working fine. They are using the same length of short code but different ones & with no issues. So, please let us know if you still want us to modify SMSGW header azs mentioned above or not. | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1382 Registered: 08-2008 |
Whether or not you need to modify that INI file, I can't say for certain. I can explain what it means. It has to do with the sender TON (type of number) value that is sent to the upstream SMSC connection. The following article talks about it some more: http://blog.nowsms.com/2009/01/ton-and-npi-settings-for-smpp-and.html To summarise the above article for your situation, this setting affects the source (sender) TON value. By default, if the sender address starts with "+", we use source TON = 1. If the sender address doesn't start with "+", then source TON = 0 ... unless the number is less than or equal to the MaxSMPPShortCodeLen (default=5) length, in which case source TON = 3. I am suspecting that the upstream SMSC wants to see source TON = 3 since 41080161 is a short code. (Not all SMSCs that support short codes require this, but some do ... that is why I can't say for certain this is your problem.) I don't know if you've changed any settings or not ... but looking at your debug log, 41080161 is now receiving successful delivery receipts. The only non-delivery reports are going to 0365. If you didn't make any changes, it is very possible that your provider did not have everything fully provisioned on their end until now. ... or we might just be experiencing a temporary set of successes in that log fragment ... Hopefully it is the former. -- Des NowSMS Support | |||||
| Muhammad Adnan farooq New member Username: Adnan Post Number: 6 Registered: 10-2009 |
DES We are having some SMPP issue over here & we want NowSMS team to join our conference bridge call. Please let me know if it is possible for you to join us. I have tried to call support lines for Now SMS at UK Telephone : +44 208 286 8080 US Telephone : +1.410.833.8711 but unable to get any response. Please advice. Thanks Muhammad | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7863 Registered: 10-2002 |
It's currently after hours. (If you do have a 7x24 support agreement, use those details for emergency contact.) Is there any additional information beyond what has been posted here? Please understand that it is your upstream SMS provider that is rejecting the message. If it is not clear why from these error codes, they should be able to provide more information. I concur with Des' analysis thus far. If there are additional logs that cannot be posted publicly they can be emailed to nowsms@nowsms.com with "Attention: Bryce" in the subject line. Post a note here if you do send any such logs so that we know to look for them. -bn | |||||
SMPP log
SMPP log - server end
