| Mblox parameters in 2-Way response |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Marcos Nowosad New member Username: Mnowosad Post Number: 3 Registered: 08-2006 |
Hi, I am using NowSMS as the SMS gateway and mBlox as the SMSC in for our SMS application. The mBlox protocol requires the mblox_operator parameter to be included in the SMPP message. I have already included this parameter in the[SMPPOptions] section of the SMSGW.INI file. The mblox technical support guy explained that in a Mobile-Originated (MO) message, mBlox includes the "mblox_operator" value in the SMPP block, to inform the operator id of the device that originated the message. However, after this message is processed by the associated 2-way command, the "mblox_operator" that came in the message is not included in the SMPP block that is sent back to the mblox. Without this value, the SMS message is rejected by mblox and does not reach the mobile device. As a temporary solution, I assigning a default value for the "mblox_operator" parameter in the "DefaultSMPPOptions" clause (I am using the Verizon id, since this is the one we are using for testing). Of course, this will NOT work in production. So I want to know how I can make NowSMS use the "mblox_operator" value received in the SMS message and include it in the SMS message sent back to the device. Thanks, Marcos | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6464 Registered: 10-2002 |
Hi Marcos, If you have the mblox_operator parameter defined in the [SMPPOptions] section of SMSGW.INI (which it appears that you do) ... and an SMS message is received which includes this parameter, then the parameter is automatically appended to the 2-way command URL (you would see &SMPPOption_mblox_operator= appended to the 2-way URL if this particular parameter is present). So the first question would be ... are you seeing this in the 2-way command? (Please note that this parameter is only available for HTTP-based 2-way commands ... not command line executables.) If you are not seeing this parameter in the 2-way command, then I'd like to see debug logs from your system to see if there is something unexpected about the way this parameter is coming back to you from mBlox. Enable the SMSDEBUG.LOG from the "Serial #" page of the configuration dialog. And then I would like to see both the SMSDEBUG.LOG and SMPPDEBUG.LOG files that are generated when you receive a message. You can either post them in reply here, or e-mail them to nowsms@now.co.uk with a subject line of "Attention Bryce" (be sure to reference this thread in the e-mail, so I know why I wanted to look at the logs). If you are getting the "&SMPPOption_mblox_operator=" parameter in your 2-way command, and you're just not sure how to send it back out ... then what you need to do is use the "redirect technique" for sending out messages from a 2-way command, instead of simply returning response text. In this approach, you build a URL that gets returned back to NowSMS to tell it to send a message, and you can include this parameter as part of your URL. For some more information on this technique, see http://www.nowsms.com/support/bulletins/tb-nowsms-003.htm. -bn | |||
| Marcos Nowosad New member Username: Mnowosad Post Number: 4 Registered: 08-2006 |
Hi Bryce, I did not know I had to use the "Redirect Technique" in this case, forwarding the value of the "SMPPOption_mblox_operator" parameter I received from NowSMS. I was just using the normal "Response Text" technique. Now it is working fine. Thanks for the tip! Marcos | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6478 Registered: 10-2002 |
Marcos, Glad to hear it is working now. Yes, we cannot assume that all optional parameters should be returned in the reply. Hopefully this explanation will help others, as we seem to be getting a fair number of similar questions recently. -bn | |||
