SMS Accounting Callback - Type=SMSOUT issue

SMS Accounting Callback - Type=SMSOUT issue SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through November 14, 2013 » SMS Accounting Callback - Type=SMSOUT issue « Previous || Next »
Author Message
Nelson Lam
New member
Username: Nelsonlam

Post Number: 7
Registered: 02-2013
Posted on Thursday, October 17, 2013 - 01:16 am:   

Dear support,

While we are testing on the Callback Accounting, we found an interesting issue

Our program will return the destination route using parameter SMSCRoute=XXXXX .

When XXXXX is defined in SMSGW.INI , we will got the following querystring :

Type=SMSOut&From=AAAAAA&To=888888888888&MessageID=52035148.req&SubmitIP=17.1.1.1 &Sender=99999999999&Text=C&SMSCRouteName=XXXXX&SMSCMsgId=35800f0e&SMSCName=SMPP% 20-%2016.16.2.10:50&Status=OK

When XXXXX is not defined in SMSGW.INI , we will got the following querystring :

Type=SMSOut&From=AAAAAA&To=%252B888888888888%26MessageID=SAR-%252B888888888888-5 2034d5d-4-1.req%26SubmitIP=17.1.1.1%26Sender=%252B62&MessageID=SAR-%2B8888888888 88-52034d5d-4-1.req&SubmitIP=17.1.1.1&Sender=%252B99999999999%26DCS=8%26UDH=0500 03100401%26Text=%25E8%25A8%258A%25E6%2581%25AF:%2520%25E4%25B8%2580%25E4%25BA%25 8C%25E4%25B8%2589%25E5%259B&DCS=8&UDH=050003100401&Text=%E8%A8%8A%E6%81%AF:%20%E 4%B8%80%E4%BA%8C%E4%B8%89%E5%9B%9B%E4%BA%94%E5%85%AD%E4%B8%83%E5%85%AB%E4%B9%9D% E5%8D%81%E4%B8%80%E4%BA%8C%E4%B8%89%E5%9B%9B%E4%BA%94%E5%85%AD%E4%B8%83%E5%85%AB %E4%B9%9D%E5%8D%81%E4%B8%80%E4%BA%8C%E4%B8%89%E5%9B%9B%E4%BA%94%E5%85%AD%E4%B8%8 3%E5%85%AB%E4%B9%9D%E5%8D%81%E4%B8%80%E4%BA%8C%E4%B8%89%E5%9B%9B%E4%BA%94%E5%85% AD%E4%B8%83%E5%85%AB%E4%B9%9D%E5%8D%81%E4%B8%80%E4%BA%8C%E4%B8%89%E5%9B%9B%E4%BA %94%E5%85%AD%E4%B8%83%E5%85%AB%E4%B9%9D%E5%8D%81%E4%B8%80%E4%BA%8C%E4%B8%89%E5%9 B%9B%E4%BA%94%E5%85%AD%E4%B8%83%E5%85%AB%E4%B9%9D%E5%8D%81%E4%B8%80%E4%BA%8C%E4% B8%89&SMSCName=SYSTEM&Status=Error:%20%20No%20SMSC%20defined%20to%20route%20mess age

What we think is some "&" had been decode as "%26" in the querystring, e.g.
%26MessageID=
%26SubmitIP=
%26Sender=

Any ideas on why the querystring will have such outcome ?

Thank you.}
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4693
Registered: 08-2008
Posted on Thursday, October 17, 2013 - 04:50 pm:   

Hi Nelson,

I have not had any luck recreating this problem.

When this happens, is the SMSOUT-yyyymmdd.LOG entry also corrupt, or is only the SMSOUT accounting callback affected?

To speed resolution, could you enable the SMSDEBUG.LOG ... then restart the SMS service ... then recreate the problem, and e-mail me the complete SMSDEBUG.LOG. That will help me understand what it is about your configuration is triggering this problem. E-mail that log file to nowsms@nowsms.com with Attention: Des in the subject line. If you could also post a follow-up reply here that would be helpful to remind me to look for the e-mail.

--
Des
NowSMS Support
Nelson Lam
New member
Username: Nelsonlam

Post Number: 8
Registered: 02-2013
Posted on Friday, October 18, 2013 - 08:46 am:   

Hi Des,

Below are the information captured in SMSOUT-XXXXX.log & URL QueryString :

SMSSend Accounting Callback querystring :
Type=SMSSend&From=user123&To=%2B62855748900000&MessageID=52035149.req&SubmitIP=x xx.xx.x.xx&Sender=%2B85251609872&Text=E

& Our program return : SMSCRoute=DROP
which 'DROP' is not defined in SMSGW.INI

SMSOut querystring :
Type=SMSOut&From=user123&To=%252B62855748900000%26MessageID=52035149.req%26Submi tIP=xxx.xx.x.xx%26Sender=%252B85251609872%26Text=E&MessageID=52035149.req&Submit IP=xxx.xx.x.xx&Sender=%252B85251609872%26Text=E&Text=E&SMSCName=SYSTEM&Status=Er ror:%20%20No%20SMSC%20defined%20to%20route%20message


SMSOUT-20131017.LOG :
2013-10-17 09:56:33,52035149.req,xxx.xx.x.xx,%2B62855748900000&MessageID=52035149.req&Submi tIP=172.xx.x.xx&Sender=%2B85251609872&Text=E,Error: No SMSC defined to route message -- SYSTEM,SubmitUser=user123;SMSCRouteName=SYSTEM;Sender=%2B85251609872&Text=E;Text ="E"


Hope these information can help in your investigation.

Thank you
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4694
Registered: 08-2008
Posted on Friday, October 18, 2013 - 03:55 pm:   

Hi Nelson,

Do you have SMSAccountingAllowChanges=Yes set in SMSGW.INI? Can you temporarily disable that setting? (The setting allows an accounting callback to change To, Sender and SMPPOption values.)


I think what is happening is that your callback response is echoing the URL back in the response ... because SMSAccountingAllowChanges=Yes is set, NowSMS is parsing the To= and thinking that the callback wants to change the recipient address.

In that case the solution would be to remove that setting ... or change the callback response so that it does not echo back the URL request.

--
Des
NowSMS Support
Nelson Lam
New member
Username: Nelsonlam

Post Number: 10
Registered: 02-2013
Posted on Monday, October 21, 2013 - 07:43 am:   

Hi Des,

Thanks for your quick response.

As per our situation, we cannot disable SMSAccountingAllowChanges=Yes since we need to translate either the OA or DA to another number before we send the SMS out.

On the other hand, it seems the problem will not happen if we do have the corresponding "SMSCRoute" defined in SMSGW.INI

Apart from disabling SMSAccountingAllowChanges , will there be other solutions for this problem ?

Thank you.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4696
Registered: 08-2008
Posted on Monday, October 21, 2013 - 05:05 pm:   

Hi Nelson,

As I mentioned previously, change the callback response so that it does not echo back the URL request.

Without seeing an SMSDEBUG.LOG showing all related accounting callbacks, I think what is happening is that your callback response is echoing the URL back in the response. Because SMSAccountingAllowChanges=Yes is set, NowSMS is parsing the To= from that extra bit being echoed back from the callback request and thinking that the callback wants to change the recipient address ... but getting a bunch of garbage data from the unexpected URL string included in the callback response.

If you cannot remove that setting ... change the callback response so that it does not echo back the URL request.

--
Des
NowSMS Support

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