| Problem sending the mblox_contenttype parameter to mblox |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 23, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Shade Bach New member Username: Shadebach Post Number: 2 Registered: 02-2009 |
Hi, We are having problems sending the mblox_contenttype parameter to mblox as described here: http://blog.nowsms.com/2008/10/mblox-and-nowsms.html The weird thing is that other parameters works except for the mblox_contenttype. Mblox suggested to add the 0x, for example: mblox_contenttype=0x1406,String instead of mblox_contenttype=1406,String but we are not sure if this is gonna work. Please advise | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1393 Registered: 08-2008 |
Hi, No ... adding the "0x" will confuse things. NowSMS assumes the "1406" value is hexadecimal. Is it possible for me to see a debug log showing an attempt to use this parameter? Enable the SMSDEBUG.LOG (checkbox on the "Serial #" page). Restart the NowSMS service. Then try sending another message. E-mail both the SMSDEBUG.LOG and SMPPDEBUG.LOG to nowsms@nowsms.com with "Attention: Des" in the subject line. Also, post a follow-up reply here so that I know to look for the e-mail. Once I get a chance to look at the log, that will let me make sure that everything is configured the way that we think it should be, and that there are no typos. In the meantime, I'm going to see what other information I can find on this parameter. What are typical values that you are trying to set it for? Most other SMPP providers that use these types of parameters use the "CString" (null terminated) type instead "String". So after generating the debug logs for me, you might want to try this instead: mblox_contenttype=1406,CString I doubt it will make a difference, but that's the first idea that comes to my mind without looking at the logs. -- Des NowSMS Support | |||
