Custom paramater field | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 23, 2009 ⬆ |
◄ ► |
Author | Message | |||
Alex Kaiser New member Username: Alex_k Post Number: 50 Registered: 07-2006 |
Hello, Is there any progress on that field? Or any ideas how to transfrer custom data beetween callbacks? Regards, Alex K. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7864 Registered: 10-2002 |
Hi Alex, It is in the queue, I don't have a real good estimate yet. The "target" is the end of next week (November 6). This is related to the "flexible" user accounting callbacks that allow you to return a route charge in the PreAuth callback. The concept is that the PreAuth callback response can also contain additional parameters (e.g., "ExtraParm=...") that will be returned back in the SmsSend callback. My understanding is that the PreAuth response can include something like this: ExtraParm=XXXX=abc&YYYYY=123456789&ZZ=xyz And the SmsSend callback would then include the following in its URL request: &XXXX=abc&YYYYY=123456789&ZZ=xyz -bn | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 51 Registered: 07-2006 |
Hi Bryce! Thank you for the response. Yes, we have the same vision. But i believe there is a need to put "ExtraParm" also in SmsOut callback in order to track all cycles of outbound message. Regards, Alex K. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7866 Registered: 10-2002 |
Hi Alex, Including this info in the "SmsOut" callback is a bit of a challenge. I'm not sure that it is possible. (Well, everything is possible, but there is the question of how much development effort is required to make it happen.) Passing the information between the PreAuth and SmsSend was a minor effort because we were already doing this with the "RouteCharge" parameter. So we'll have to go back and re-investigate the "SmsOut" issue. -bn | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 52 Registered: 07-2006 |
Hi Bryce, Ok, let's try that feature with PreAuth & SmsSend callbacks first. If any updates would be necessary, i'll write detailed explanations. Regards, Alex K. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1399 Registered: 08-2008 |
Hi Alex, We've got an update for you. PreAuth & SmsSend callbacks only. It doesn't work like Bryce suggested it might above. Instead it works like this: The concept is that the PreAuth callback response can also contain additional parameters (e.g., "ExtraParm=...") that will be returned back in the SmsSend callback. The PreAuth response can include "UserData=" in its response, similar to how it can include "RouteCharge=": UserData=xyasdfjfdljfdlajfd When this data is present in the PreAuth, the SmsSend callback would then include the following in its URL request: &UserData=xyasdfjfdljfdlajfd Be sure to terminate "UserData=" in your response with a line break. NowSMS considers all data after "UserData=" up to the line break as user data. -- Des NowSMS Support | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1400 Registered: 08-2008 |
Oops. I forgot to post the link. http://www.nowsms.com/download/alexk.zip | |||
Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 53 Registered: 07-2006 |
Hi Bryce and Des, So, in that version we can put only 1 parameter into callback or we need to use some internal encoding if we want to make several parameters. Is it correct? Regards, Alex K. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1402 Registered: 08-2008 |
Hi Alex, Yes, that is correct. After further analysis, we thought the approach described by Bryce above was too inconsistent with how the other callback parameters work. So essentially, you return a parameter, and we pass it back. If you want to specify several parameters, you would need to use some sort of encoding so that you could distinguish them when they are passed back. -- Des NowSMS Support |