Nowsms + Mblox + OPPC + | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 08, 2009 ⬆ |
◄ ► |
Author | Message | |||
Shade Bach New member Username: Shadebach Post Number: 1 Registered: 02-2009 |
Hi, how can i use nowsms and mblox, and how do i setup nowsms to use OPPC? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 498 Registered: 08-2008 |
Hi, This document talks about how to configure NowSMS to use advanced mBlox parameter settings: http://blog.nowsms.com/2008/10/mblox-and-nowsms.html OPPC is, I believe, at AT&T specific implementation. And I believe mBlox supports it via extended SMPP parameters, like they do for similar offerings from different operators. If you encounter any additional parameters that aren't mentioned in the link above, please reply back and I'll try to clarify how they would be configured. -- Des NowSMS Support | |||
Peeter Madrus New member Username: Peeterm Post Number: 1 Registered: 01-2009 |
We need this to work as well. The parameter that needs to be manipulated for OPPC is: product code (0x1520) An optional VeriSign-specific parameter used if this is a premium message. There's no mention of this param in the referenced page. Can you shed some light on how we could set this value ? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 538 Registered: 08-2008 |
Hi Peeter & Shade, I have asked a contact for more information about additional mBlox parameter settings. So far, I haven't got any information about "product code (0x1520)". And based upon other information, it appears that this is a Verisign parameter, not an mBlox parameter. I would expect that mBlox would use the mblox_tariff parameter for this information, like they do for other mobile operator specific tariffs. To enable support for all known additional mBlox parameters in NowSMS, manually edit the SMSGW.INI file and and add the following section: [SMPPOptions] mblox_operator=1402,String,5 mblox_tariff=1403,String,5 mblox_sessionid=1404,String mblox_servicedesc=1405,String mblox_contenttype=1406,String mblox_serviceid=1407,String mblox_imei=1501,String mblox_imode=1502,String mblox_SubID=1503,String mblox_HostNet=1504,String mblox_NewSub=1505,String mblox_SubRef=1506,String mblox_SubDate=1509,String mblox_UAProf=1513,String mblox_BillId=1519,String mblox_SessionID=1521,String mblox_reasonCode=1522,String mblox_reasonMsg=1523,String mblox_Command=1524,String mblox_AVStatus=1526,String mblox_ProdDesc=1527,String user_message_reference=204,Integer,2 All of these additional parameters work just like the parameters that are described in: http://blog.nowsms.com/2008/10/mblox-and-nowsms.html To specify a value for the mblox_tariff, you would include "&SMPPOption_mblox_tariff=" in your URL. And if this value were present in a message that you receive, this parameter would be added to your 2-way command URL. If you want to specify a default value for this parameter, you can use the "DefaultSMPPOptions=" setting described in the posting that I referenced above. Please let me know how this works. I'd like to share any updated information with others ... -- Des NowSMS Support | |||
Peeter Madrus New member Username: Peeterm Post Number: 2 Registered: 01-2009 |
Thanks for the quick response. I should have mentioned the reference I was using - VeriSign's "SMS Gateway API Reference v2.4.pdf" dated 2/20/2009. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 539 Registered: 08-2008 |
Hi Peeter, So you're not using mBlox? Or maybe you are ... I'm working off of v2.3 of the mBlox SMPP API Reference. Could you e-mail me that PDF? Send it to nowsms@nowsms.com, and put "Attention: Des" in the subject line. That way I can confirm the correct encoding for the parameter. Thanks! -- Des NowSMS support | |||
Peeter Madrus New member Username: Peeterm Post Number: 3 Registered: 01-2009 |
The .PDF is on the way. I was focusing on the OPPC rather than the mBlox aspect in this post. Hopefully the answer applies to both: could I use the mBlox_ parameters for setting values in communicating with VeriSign? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 540 Registered: 08-2008 |
Hi Peeter, These settings are different for every provider. They usually implement them using similar optional parameter encoding, but different enough. I don't know about OPPC (And I wish the following would stop going through my head each time it is mentioned: "Are you down with OPPC? Yeah, you know me.") But I expect that with mBlox, the mblox_tariff parameter would be used. For Verisign, it is definitely the product code parameter that you reference. Looking over the Verisign documentation, to enable support for all of their documented parameters in NowSMS, manually edit the SMSGW.INI file and and add the following section: [SMPPOptions] verisign_product_code=1520,String verisign_output_code=1530,String verisign_error_message=1531,String verisign_auth_code=1532,String verisign_auth_message=1533,String verisign_carrier_id=1402,String verisign_carrier_name=1404,String All of these additional parameters work just like the mBlox parameters that are described in: http://blog.nowsms.com/2008/10/mblox-and-nowsms.html To specify a value for product code using the 0x1520 field, you would include "&SMPPOption_verisign_product_code=" in your URL. And if this value were present in a message that you receive, this parameter would be added to your 2-way command URL. Out of the above list of parameters, it appears that verisign_product_code is the only one that can be included in a submit message. The other parameters can appear in received messages, so you would see them as 2-way command parameters if you add the SMPPOptions section above to your SMSGW.INI file. If you want to specify a default value for this parameter, you can use the "DefaultSMPPOptions=" setting described in the posting that I referenced above. -- Des NowSMS Support |