| CallBack Number |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 02, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| walter Betances New member Username: Wbetances Post Number: 12 Registered: 04-2005 |
Bryce, NowSMS is not sending Callback number in Optional parameters (smpp.callback_num) I'm sending SMS over an SMPP connection from nowsms to SMSC. When SMSC sends the message to the phone the Callback is not been sent.That SMSC is expecting to receive from nowsms the Callback number in Optional parameters (smpp.callback_num) | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5387 Registered: 10-2002 |
Walter, That particular parameter is very rarely used. If you do have a need to use this parameter, it is what is known as an optional "TLV" (tag/length/value) parameter. For information on how to configure this type of parameter, refer to the description of the [SMPPOptions] section of SMSGW.INI in the following thread: http://support.nowsms.com/discus/messages/1/5972.html In the context of this specific parameter (callback_num), the following configuration would be required: [SMPPOptions] callback_num=381,String When this setting is present, an additional parameter is supported when submitting a message to NowSMS via an HTTP URL request. "&SMPPOption_callback_num=" will specify a value for the SMPP callback_num parameter. When this SMSGW.INI file setting is present, NowSMS will also route this parameter to HTTP-based 2-way commands. If a message is received which contains a value for this setting, NowSMS will automatically append "&SMPPOption_callback_num=value" to the 2-way URL. It is not necessary to add any variables to the 2-way command template, as this value will be appended automatically if present in a received message. In addition to supporting these options via HTTP URL request, it is possible to configure default settings for this option for each outbound SMPP connection. To define default settings, manually edit the SMSGW.INI, and in the section header for an SMPP connection (e.g., [SMPP - ip.address:port]), add a "DefaultSMPPOptions=" setting, where the value of this setting can contain any of the "SMPPOptions" settings. For example, "DefaultSMPPOptions=callback_num=12345". To include multiple options (if you are using multiple options), separate the entries with a ";", for example, "DefaultSMPPOptions=callback_num=00000;user_message_reference=1". -bn | |||
| walter Betances New member Username: Wbetances Post Number: 15 Registered: 04-2005 |
Bryce, Thanks for the info. I tested it and it works via HTTP-based. But it does not look like that I could apply this solution form my case. I’m receiving several messages from one SMSC in nowsms then I route them thru different SMSC connection. This connection comes in thru SMS users and goes out thru SMSC. If I use "DefaultSMPPOptions=callback_num=00000" under SMPP connection in SMSGW.ini the callback would be static for all messages. I need something like "DefaultSMPPOptions=callback_num=source_addr" something that would make the callback_num the same as the sender address in each message sent. Thnaks, | |||
| walter Betances New member Username: Wbetances Post Number: 16 Registered: 04-2005 |
Bryce, Is there any other way to proceed with this? Thanks, | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5450 Registered: 10-2002 |
Hi Walter, I'm not sure how to deal with this. We'd have to add some replaceable parameter support in the "DefaultSMPPOptions" parameter, which sounds a bit tricky. Is the callback_num option set in the message coming from the original SMSC? The reason I ask is because if this option is set as present in the [SMPPOptions] section, then when receiving from an SMPP connection, we will preserve the value of this option, and preserve it if the message gets routed back out another SMPP connection. -bn | |||
| walter Betances New member Username: Wbetances Post Number: 17 Registered: 04-2005 |
Regarding your question, The Originating SMSC is not sending this parameter, that’s why I need to add it. Can you add an Advance setting under SMPP settings that indicate that would send the callback_num = to sender address. That is for the case that the Originating SMSC doesn’t send that parameter. Regards, WB | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5453 Registered: 10-2002 |
Walter, I've done a little more investigation on this. We could add support for a parameter setting of "DefaultSMPPOptions=callback_num=@@SENDER@@" pretty easily. But I fear that the callback_num encoding is a little more complicated than this. Reading the specification, it looks like it would require the following: 0x01 (callback number is ASCII digits) source_addr_ton source_addr_npi source_addr Do you agree? I've never worked with this particular parameter before, so I'd like to try to confirm that we're doing it correctly if we attempt to add a configuration setting for this. -bn | |||
| walter Betances New member Username: Wbetances Post Number: 18 Registered: 04-2005 |
Ok, If you need to do some testing I could help. The thing is that it works via HTTP-based, so I guess it could also work. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5513 Registered: 10-2002 |
Walter, Because of the unusual fomatting of this particular field, I can't see any generic way of implementing this feature. But, it doesn't look like it is all that difficult to implement a setting that just does exactly what you want, which is to include a callback_num parameter that matches the sender address. There is an update patch for NowSMS v5.51 at http://www.nowsms.com/download/walter.zip. In this version, you can manually edit SMSGW.INI, and under the [SMPP - server:port] header, add InsertSenderAsCallbackNum=Yes. When this parameter is set, all messages that are sent via this SMSC link have the callback_num field inserted, with a value that matches the message sender. So give that a try. -bn | |||
| walter Betances New member Username: Wbetances Post Number: 19 Registered: 04-2005 |
Thanks Bryce, It is working perfect. Will this be available in the new release 2006. Walter, | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5593 Registered: 10-2002 |
Hi Walter, Yes, this feature is incorporated into the NowSMS 2006 release. This INI setting didn't make the documentation, but it is supported. -bn | |||
