Disable DR Accounting Callback

Disable DR Accounting Callback SearchSearch
Author Message
Nelson Lam
New member
Username: Nelsonlam

Post Number: 12
Registered: 02-2013
Posted on Tuesday, November 19, 2013 - 04:21 am:   

Hi Support,

Currently we are using v2013.09.26 NowSMS , we found that the handling of DR with Accounting Callback is different from previous version (we are using v2009.07.09 before upgrade).

DR will call Accounting Callback in this new version while the old version won't (provided that we are using the same set of SMSGW.INI in both versions). So my questions are :

Is there any setting / way to disable DR Accounting Callback ?

And, how will DR route to it's destination if we don't have any default route set in "SMSC Connection" ?

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

Post Number: 4747
Registered: 08-2008
Posted on Wednesday, November 20, 2013 - 03:14 pm:   

Hi Nelson,

I am not aware of any situation where an SMS delivery report would not have generated an accounting callback in earlier versions, but does in more recent versions. But we are talking 4 years of differences, so I can't be certain.

I assume you are referring to an SMSIN callback? I do see a change note where a ReceiptUser parameter was added to the SMSIN callback to indicate what account the receipt was being routed to.

But the short answer would be, no there is no setting to suppress these callbacks for delivery reports.

To better understand your situation, I'd probably need to better understand the overall routing path.

SMS delivery reports tend to be difficult to get working properly in configurations where you are hubbing messages between two SMSCs. The reason for this partially due to routing, but more to do with the fact that message IDs are changed with every SMPP hop. NowSMS automatically tracks this message ID chain, but if a message ever gets routed SMSC -> ESME, the SMPP deliver_sm PDU breaks the chain.

It's a rather complicated subject to explain.

If you have SMPP clients (these are ESME connections defined under "SMS Users") who send messages out through NowSMS, and those messages are routed from NowSMS out to an SMSC connection, then the delivery reports will be routed properly as long as the upstream SMSC doesn't mangle message IDs.

But you run into problems if messages go SMSC -> ESME with a delivery report requested because the message ID tracking chain will be broken.

There's more explanation of the issue and how to handle it here: http://www.nowsms.com/sms-hubbing-considerations

--
Des
NowSMS Support