UserData paramater | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2010 ⬆ |
◄ ► |
Author | Message | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 86 Registered: 07-2006 |
Hi! We faced some problems, NowSMS recognizes UserData parameter from PreAuth callback and passes it forward to SMSSend BUT NowSMS doesn't accept it when submitting message (from URL), for example: http://127.0.0.1:8800/Send%20Text%20Message.htm?PhoneNumber=1234567890&Sender=SE NDER&Text=TEXT&UserData=USERDATA Message will be placed into queue but without UserData parameter. I believe you have to fix that issue. Regards, Alex K. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1865 Registered: 08-2008 |
Hi Alex, That parameter is related to the "RouteCharge" parameter. It was added to provide a way to match the pre-auth callback with the standard send callback. If the pre-auth callback returns "UserData=" in its response, this data is sent back to the SMS send callback. It was never designed to work the way that you describe. -- Des NowSMS Support | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 87 Registered: 07-2006 |
Hi Des, Thanks for the response! But if some foreign application needs to provide self-generated data like TranID, for example: unite messages into marketing campaign or provide some which will be considered with routing engine. What do you think? I believe that’s useful feature. Regards, Alex K. | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 88 Registered: 07-2006 |
Hi Des! Any updates with that issue? Regards, Alex K. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1900 Registered: 08-2008 |
Hi Alex, It's unfortunate that we named this parameter "UserData", as this does not properly represent its purpose. Its purpose was strictly to provide a way for an accounting callback processor to correlate the PreAuth callback with the SmsSend callback. It probably should have been called "CallbackData" or something similar. I agree that there would be uses for a more general "UserData" parameter, but that is a bit larger in scope ... at least the way that we've envisioned it. You might be just trying to get the parameter passed to an accounting callback, which would be useful. However, we'd also like to see the value saved and retained so that it can be passed back in delivery receipts. We'd also like to see a way that it could be implemented such that it could also work with the more limited SMPP user_message_reference parameter. So I'm probably thinking about more than you're asking for. However, internally when we discuss this ... we relate it to this larger idea ... something that we have wanted to do, but that we have not been able to justify getting into the development schedule. Perhaps if it was scaled back to only pass the details to the accounting callback (no receipt tracking), it would be more manageable for implementation. Maybe you could describe in more detail what you'd like to see, and then maybe we will see a simpler way to implement than the full scope I described. -- Des NowSMS Support | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 89 Registered: 07-2006 |
Hi Des! Thanks for the response! I believe at that stage our task is to deliver custom data from foreign application submitting SMS over HTTP at least to SMSSend callback and write it to DB. Also it would be great if you include custom SMPP parameters (TLV) into PreAuth, SMSSend, SMSIn & SMSDR callbacks. Many thanks in advance! Regards, Alex K. | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 91 Registered: 07-2006 |
Hi Des, Any decision on that param? Regards, Alex K. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1921 Registered: 08-2008 |
Hi Alex, I don't have any news. It's a good idea, but we have yet to evaluate the full scope of how much development effort is involved. Based upon the number of current development work items and priorities, I don't think this can be fully evaluated for a few weeks. -- Des NowSMS Support | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 92 Registered: 07-2006 |
Hi Des, That is bad, because i think without passing to NowSMS parameters "UserData"'s functionality looks far reduced. I hope that you're able to find some space in your schedule to complete that issue. Regards, Alex K. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1926 Registered: 08-2008 |
Hi Alex, I wish it could be quicker. But if you recall the history of this particular parameter, you asked us for the ability to pass a custom parameter between callbacks: http://support.nowsms.com/discus/messages/1/41913.html What you are asking for now is different. From what I understand, our developers have added an internal hook for an additional data field. And they are trying to add some of this while making other changes. We just can't give a firm timetable at this time. -- Des NowSMS Support | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 93 Registered: 07-2006 |
Hi Des, Yes, i agree with you. Our previous task was slightly different but during the implementation we realized that ability is necessary. Simple example: Messages are being submitted over HTTP but from different source (Web-GUI and HTTP/XML services) with additional parameter we can identify exact data source but without it, we need to use tricky techniques. Regards, Alex K. | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 96 Registered: 07-2006 |
Hello Des and Bryce, Could you please tell, is there any chance to get update on that field? We need to look closer to our implementation schedule. Regards, Alex K. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7898 Registered: 10-2002 |
Hi Alex, Unfortunately this week is a popular holiday week in our organisation. We should be able to give you a timeframe at some point in the middle of next week. -bn | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2021 Registered: 08-2008 |
Hi Alex, A little later than planned for a follow-up, but I think we're still looking at 2 to 3 weeks. It is supposed to enter the engineering process next week. We have been working on fixing performance issues with large message queues and large numbers of outbound SMSC connections, and this work is currently taking longer than planned. To avoid confusion ... the current plan for this feature is as follows: An additional HTTP URL parameter will be supported, "AcctInfo=". The accounting callbacks are to include "AcctInfo=" if it was included in the submitted message. While this is being implemented, we will investigate the feasibility of also including TLV parameters in the accounting callback. This part may or may not be implemented at this time, depending on its complexity. -- Des NowSMS Support | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 97 Registered: 07-2006 |
Hi Des, That's brilliant news, thank you! Regards, Alex K. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2037 Registered: 08-2008 |
Hi Alex, Support for the "AcctInfo" parameter has been added in the update at http://www.nowsms.com/download/nowsmsrc.zip. TLV parameters are not passed to accounting callbacks, but "AcctInfo" is. -- Des NowSMS Support | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2055 Registered: 08-2008 |
Additional follow-up ... support for passing the TLV parameters in SMS accounting callbacks will be forthcoming. Possibly as early as mid next week. -- Des NowSMS Support |