| Default DCS=48 instead of 8 for Unicode sms |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 26, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| KKW New member Username: Kkw Post Number: 21 Registered: 01-2009 |
Hi Support, currently our nowsms gw connected to operator's USSD gw via smpp connection, when we reply subscriber's ussd request with unicode message, operator side need us using DCS value 48 intead of 8, is it possible to set this DCS value 48 for unicode message as default for this smpp conneciton ? thx kk | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7779 Registered: 10-2002 |
Hi kk, I cannot think of any good way to do this. The only thing that I could think of would be for you to use the redirect technique in your 2-way command, instead of a direct command response. (See http://www.nowsms.com/support/bulletins/tb-nowsms-003.htm) Using this approach, you return a NowSMS submit URL back in a redirect header. Here you can use NowSMS URL parameters to explicitly set the DCS to 48. When you do this, you would have to encode the Unicode text as a hex string in the "Data=" URL parameter. Also be sure to include "Binary=Yes" in the URL parameters, so that we know that the "Data=" parameter should be interpreted as a hex string. -bn | |||
| KKW New member Username: Kkw Post Number: 22 Registered: 01-2009 |
Hi Bryce, i know the way u suggested and tested ok already, however my application was written in visual basic 6 and i don't know how to convert the text to unicode hex string in vb6, do u have any idea how to do that ? kk | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7790 Registered: 10-2002 |
Hi kk, I don't know of any VB6 code to easily do this. But I might be able to do something simple for you. I just sent an updated SMSGWS.EXE to your e-mail. If you submit Unicode text to it, with DCS=48, then it should leave the DCS value alone instead of changing it to 8. If you don't get this e-mail, then please send a message to nowsms@nowsms.com with "Attention: Bryce" in the subject line, and I'll reply to your message with the file. -bn | |||
| KKW New member Username: Kkw Post Number: 23 Registered: 01-2009 |
Hi Bryce, thx a lot for yr help, tested ok, will use this as work around first. with best regards, kk | |||
| KKW New member Username: Kkw Post Number: 25 Registered: 01-2009 |
Hi Bryce, accroding to GSM 03.38 V7.0.0 Alphabets and language-specific information, Unicode USSD Message should encoded with Data Coding Scheme (DCS) value of 0x48 for long term solution, can NowSMS using DCS=48 instead of DCS=8 for Unicode message when i set the ServiceType=USSD ? thx & regards, kk | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7803 Registered: 10-2002 |
Hi kk, We've been working off an older version of that spec that didn't mention USSD, so we'll study and see what might be done to help in USSD environments. -bn | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 955 Registered: 08-2008 |
Hi kk, It took me awhile to notice this ... but I see that there is a reference that indicates that USSD can use the same DCS values as cell broadcast. I assume you are setting the "service type" value to "USSD" via a setting in the SMSGW.INI file? Is your provider ok with a data coding value of 0x40 for non-Unicode messages? I'm thinking that when service_type = USSD we could map 0x00 to 0x40 (because a value of "0" would actually mean German) ... and 0x08 to 0x48. Do you agree? -- Des NowSMS Support | |||
| KKW New member Username: Kkw Post Number: 26 Registered: 01-2009 |
Hi Des, yes we setting the "service type" value to "USSD" in SMSGW.INI for non-Unicode message with 0x40 just tested seems problem, in the handset ussd session ended without any display. if using 0x00 can have connect message display. how about only replace 0x08 with 0x48 for Unicode message and non-Unicode message just keep it as 0x00 ? thx kk | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7817 Registered: 10-2002 |
That's interesting kk ... I would expect that if 0x48 works for Unicode, then 0x40 should work for text. Technically, I think for text we should be using 0x0F (which I believe is what you are receiving). I'm a little weary of hard coding any DCS conversions like this, so I had another idea. We recently added a configuration setting to allow users to force the binary message DCS value to "2" instead of "4" because some SMSCs require this. We could add text DCS and unicode DCS overrides on a per connection basis as well. In my mind, that would be preferable to hardcoding for USSD. Stay tuned. -bn | |||
| KKW New member Username: Kkw Post Number: 27 Registered: 01-2009 |
hi Bryce, if can have text DCS and unicode DCS overrides on a per connection basis will be great and more flexable then hardcoding for USSD. thx kk | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 975 Registered: 08-2008 |
Hi kk, The changes that Bryce referenced above have been applied in an update at http://www.nowsms.com/download/nowsms2009rc.zip (v2009.06.30). Basically, on a per-connection basis, we allow you to specify data_coding (DCS) override values for text, binary and/or Unicode messages. * SMPP: Add configuration settings to force certain message types to use a particular DCS (data_coding) value on a per SMPP connection basis. DCS override values can be defined for all 7-bit text, binary and/or Unicode messages. For example, 0x0F is often the preferred DCS value for USSD text messages, and 0x48 is the preferred DCS for USSD unicode messages. When an override is applied, all messages of the specified type (text, binary or Unicode) will have their DCS value converted to the override value. To apply this setting for all messages routed to a specific SMSC, edit SMSGW.INI, and under the SMSC specific section (e.g., [SMPP - server:port]), add TextDCS=##, BinaryDCS=## or UnicodeDCS=## as appropriate, where ## is the DCS value in hex, e.g., TextDCS=F or UnicodeDCS=48. -- Des NowSMS Support | |||
| KKW New member Username: Kkw Post Number: 28 Registered: 01-2009 |
Hi Des, sorry for late reply, tested working great, thx a lot for yr help. kk | |||
