| DCS values being changed |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 23, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Chris New member Username: Chrisc Post Number: 10 Registered: 12-2008 |
Hi We've discovered an issue with some handsets experiencing a different variety of issues when we send messages to them. Once we enquired the route we connected to, they informed us that the DCS value they receive is 241, yet we've set our DCS values to 11 before we submit the message(s) to NowSMS. Yet the actual DCS that needs to be submitted is 17.We submit the message(s) to NowSMS via HTTP. Is there some other way of ensuring that the correct DCS value is used when submitting messages through a particular SMPP bind? Thanks Chris | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1374 Registered: 08-2008 |
Hi Chris, I can explain this. SMPP data_coding values do not map directly to GSM DCS values. Rather than using decimal DCS values, I'm going to explain the issue in hex. DCS value 0x0B (11 decimal) is not valid in either GSM or SMPP ... it would be a reserved value in both. I suspect you're actually trying to submit a DCS value of 0x11 (17 decimal). In GSM, this value means that it is a class 1 message. However, in SMPP, 0x11 is not a valid data_coding value, and many providers will reject or corrupt the message. In SMPP, GSM message class control is defined as using DCS values 0xF?. Therefore, NowSMS converts DCS 0x11 to data_coding 0xF1 (241 decimal). In ETSI GSM 03.38, DCS values 0x11 and 0xF1 have the same meaning ... message class 1, default alphabet. The problem is that data_coding value 0x11 is not valid in SMPP, so we have to convert it. -- Des NowSMS Support | |||
| Chris New member Username: Chrisc Post Number: 11 Registered: 12-2008 |
Hi Des Thanks for responding back. The problem is, however, the route in question is expecting a DCS of decimal 17 instead of 241. When we submit messages to them carrying this value, it causes a few issues with the receiving handsets. Is there any way we can do this? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1377 Registered: 08-2008 |
Hi Chris, We can probably add a configuration switch to prevent the conversion. There's an interim update due today, so let me see if a switch can be added. I do know that years ago (before this remapping was added) we ran into problems with this because technically according to the SMPP spec, these values are not valid. -- Des NowSMS Support | |||
| Chris New member Username: Chrisc Post Number: 12 Registered: 12-2008 |
Thanks Des Please let me know when you have an update Chris | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1381 Registered: 08-2008 |
Chris, I just uploaded an interim release 2009.10.23 to http://www.nowsms.com/download/nowsmsupdate.zip. It includes the following setting which should address your requirement: * SMPP: Add configuration setting to prevent NowSMS from remapping GSM message class DCS values which are invalid in SMPP to valid SMPP values. To apply this setting for a specific SMSC, edit SMSGW.INI, and under the SMSC specific section (e.g., [SMPP - server:port]), add RemapMessageClassDCS=No. -- Des NowSMS Support | |||
