| SMPPOptions in Accounting Callbacks? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Frank Danielson New member Username: Fdanielson Post Number: 5 Registered: 02-2006 |
We've been taking advantage of the features that were added to support adding TLV parameters for SMS aggregators and it has been working quite well. Now we're trying to implement Accounting Callbacks to perform accounting for premium rated SMS messages but have run in to a roadblock in getting the rating information. We have TLV parameter 1403 defined as mblox_tariff in the smsgw.ini in addition to parameter 1402, mblox_operator. When accounting callbacks are turned on the values of those parameters are not being passed in the PreAuth callback so we can not authorize or deny the message based on the rating information passed in the mblox_tariff TLV. Here is an example of a request for a message rated at $9.99- Request- http://nowsmshost:8800/?PhoneNumber=4075551212&Text=test+message&SMPPOption_mblo x_operator=csky&SMPPOption_mblox_tariff=999&SMSCRoute=local PreAuth Callback- http://callbackurl.com/?PreAuth=Yes&Type=SMSSend&From=test&To=4075551212&MsgCoun t=1&SubmitIP=127.0.0.1&SMSCRoute=local&Text=test%20message We are running V2009.07.09 in production and I downloaded and tested V2010.02.09 with the same results. Is this something that should work? -Frank | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2052 Registered: 08-2008 |
Hi Frank, No, unfortunately the TLV parameters are not included in the accounting callbacks. That said, this is a capability that others have requested, and it is currently in the engineering queue to be added along with some other additions to the accounting callbacks. I don't have an exact estimate yet, but I am expecting to see it in update that is scheduled for mid to late May. -- Des NowSMS Support | |||
| Frank Danielson New member Username: Fdanielson Post Number: 6 Registered: 02-2006 |
Thanks for the information. It looks like a few other folks have been looking for the same thing. I'll keep an eye out for the update. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2093 Registered: 08-2008 |
Hi Frank, This update has been posted at http://www.nowsms.com/download/nowsmsupdate.zip. -- Des NowSMS Support | |||
| Frank Danielson New member Username: Fdanielson Post Number: 8 Registered: 02-2006 |
Thanks for the quick turnaround. We'll get it in the lab and test it out. | |||
| Frank Danielson New member Username: Fdanielson Post Number: 9 Registered: 02-2006 |
I haven't been able to test every combination of incoming and outgoing messages yet but it appears that the routing parameters sent in the PreAuth callback vary somewhat. I've seen SMSCRoute, SMSCName, and SMPPOption_mblox_operator supplied under different circumstances. Is there a description available of the logic NowSMS uses to decide which parameter to supply? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2153 Registered: 08-2008 |
Hi Frank, Any of the "SMPPOption_" parameters are going to be present in the callback only if they are present in the message. If the parameter is not set for the message, then it will not be present. (Note however, that if you are using a DefaultSMPPOptions parameter to set a default value for one of these parameters when it is not present, this default value will still be applied to the outgoing message, even if it is not in the callback. The callback only records this parameter if it is explicitly set in the submission.) "SMSCRoute=" is included in the callback only if an explicit route has been requested in the message submission. I don't think "SMSCName=" can be included in a PreAuth callback. At least I cannot think of a scenario in which it could be included. It is present for the "SMSOut" and "SMSIn" callbacks which tells you which SMSC connection was involved when a message was dispatched out or received in. -- Des NowSMS Support | |||
