| Binary messages: with no encoding and DCS=2 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 14, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Bill Fulton New member Username: Wafulton Post Number: 1 Registered: 10-2010 |
We have a customer that insists on using DCS of '2' with binary SMS messages. I've read the postings here that say this is not valid (and agree), but we can not convince them to change it. We use the web interface to send binary SMS messages. We act as an SMPP client, connecting to the cusomer's SMSC. When we send a binary SMS message with DCS set to '2', the message data is encoded. When we send SMS message with DCS of '4', then the data is not encoded (as we would like). I've read the posting describing the 'BinaryDCS=2' option for SMSGW.INI. I tried doing that, and setting the DCS to '4' in the web interface while sending, but what I see happening is that the DCS is, indeed, changed to '2' in the outgoing message, but the binary message data is still encoded. In other words; it seems that, when using the BinaryDCS=2 in the INI file, the DCS "translation" from 4 to 2 occurs before NowSMS decides whether or not the message data needs to be encoded. Is there a way to convince NowSMS to not encode the binary data, but still set the outboing DCS value to '2'? I know that everyone has been asking for their own favorite way to "spoof" the DCS, but I'm hoping there's one more little tuning, somewhere, that will do what we need. Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2588 Registered: 08-2008 |
Hi Bill, I'm not sure what you mean by the message data being "encoded". When a message is in binary format, it is simply binary ... no encoding or decoding occurs. Maybe you can give me an example to help me understand? -- Des NowSMS Support | |||
| Bill Fulton New member Username: Wafulton Post Number: 2 Registered: 10-2010 |
Hi Des, When we use the web interface to send a binary SMS message (of type "other"), and specify a DCS value of 4, then the message data that is sent to the SMPP server is, as you say, just binary data - it is not modified in any way. When we do the same and specify a DCS of 2, then the (binary) message data is "7-bit packed" (I'm calling that "encoded" - maybe bad terminology), just as if it were a text SMS message, when it is sent. We would like to be able to send a binary message with a DCS of '2', but have the message data left unmodified. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2589 Registered: 08-2008 |
Hi Bill, I think I understand the confusion. Use the BinaryDCS=2 setting for the S MSC but when you submit to NowSMS, use a DCS value of 4. | |||
| Bill Fulton New member Username: Wafulton Post Number: 3 Registered: 10-2010 |
Hi Des, Sorry - I was not clear in my message. That is the procedure that we are following - i.e. specify DCS of '4' in the web interface and use the BinaryDCS=2 in the INI file. What we are seeing is that, even though we specify a DCS of '4' in the web interface, the message data is "encoded" when it is sent (and a DCS of '2' is sent) if the BinaryDCS=2 is present in the INI file. If the BinaryDCS=2 is not present in the INI file, and DCS of '4' is specified in the web interface, then the message data is _not_ encoded (as expected). This is what lead me to believe that the BinaryDCS=2 "operation" was applied first, before NowSMS decides whether or not the message data needs to be encoded before sending. What I was hoping would happen, with this INI file modification, is that the BinaryDCS=2 operation would _only_ mean that the DCS value in the outbound message would be "jammed" to '2', regardless of the DCS specified in the web interface, but that the DCS value that was specified in the web interface would determine what, if any, encoding was done on the message data. I realize it's difficult to satisfy everyone's desires for these tunings; I was just hoping that I was missing something or somehow mis-applying the INI modifications. (I am adding the "BinaryDCS=2" INI line under the "[SMPP - host:port]" section header, which is where I understand it should be.) | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2590 Registered: 08-2008 |
Hi Bill, Ok. I'll be out of the office tomorrow, so maybe to save some time resolving this you can send me some log files to help me understand. No encoding should be taking place, so I must be overlooking something. Go to the Serial # page and enable the smsdebug.log. Submit one of these mes sages. Then send the smsdebug.log and smppdebug.log to nowsms@nowsms.com wit h a subject line of Attention: Des It most definitely should not be encoded, so I'm hoping the logs will point o ut something that I am not thinking of. -- Des | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2595 Registered: 08-2008 |
Hi Bill, Thanks for sending the logs. I ran some tests earlier today and can confirm that there is definitely a problem with this BinaryDCS=2 setting. Some other values are ok, but BinaryDCS=2 results in the message data being misinterpreted and corrupted. The fix should not be difficult, but I want to make sure we better understand how this got broken, as the setting apparently worked at one point in time. We should have a fix available by Monday or Tuesday. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2622 Registered: 08-2008 |
Hi Bill, Apologies for the delay in response. The fix availability took longer than expected. It has been posted to http://www.nowsms.com/download/nowsms20101104.zip. -- Des NowSMS Support | |||
