| Was there a change to DCS=4 versus DCS=F5 as default for messages |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 21, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Stone New member Username: Stone Post Number: 6 Registered: 01-2010 |
Hi I downloaded a test version of nowsms in January. We had to set BinaryDCS=4 in out SMSGW.ini in order to correctly talk to the SMPP. By default nowsms would send F5 which was not accepted by the SMPP. Now we use a different SMSC and I wanted to send DCS=F5 so I removed the entry in the INI file. But it looks NOWSMS still sends DCS=4. I have to say that we just recently donloaded a newer version 2010.02.09 (don't remember the previous version) but it seems I cannot get NOWSMS to send F5 anymore??? even if setting BinaryDCS=F5 in the INI file. Was there a change made in that area? I didn't find anything in the release notes. If this is not a problem with the release what could be my problem? Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1903 Registered: 08-2008 |
Are you using WDP Adaptation? | |||
| Stone New member Username: Stone Post Number: 7 Registered: 01-2010 |
Yes...but I always used it. should I try without? Does WDP enable DCS=4 by default? I thought I used it before and got F5 as default. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1904 Registered: 08-2008 |
Hi Stone, I don't have all the details in front of me right now, but someone pointed out to us that the WDP Adaptation spec specifies a data_coding value of 4. Checking use TLV parmameters will do similar encoding to WDP adaptation, except that it segments. Check the readme file included with the update, as there is a new BinaryDCS parm that works per connection. I'm just not sure if it works with WDP Adaptation as more details are hard coded for it. (I will investigate more tomorrow ... just wanted to give some quick preliminary feedback.) -- Des | |||
| Stone New member Username: Stone Post Number: 8 Registered: 01-2010 |
OK. I checked the readme but couldn't find anything related to BinaryDCS.if you find out more tomorrow that would be great. Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1906 Registered: 08-2008 |
Hi Stone, I've done some research on this issue, and found a few relevant discussions (and history lesson) on this issue: http://support.nowsms.com/discus/messages/1/41812.html http://support.nowsms.com/discus/messages/1/13877.html http://support.nowsms.com/discus/messages/1/42172.html Here's a synopsis. Beginning with NowSMS 2006, NowSMS began defaulting to using DCS=4 for WAP Push messages when WDP Adaptation is used. This is done because that is what the WDP Adaptation specification says. In 2009, we accidentally broke this automatic F5 to 4 remapping for WDP Adaptation when adding a new configuration setting. Late in 2009, we fixed this to go back to the automatic remapping. While there is a configuration setting to override the binary DCS value on a per-SMSC connection basis, I have tested it and it will not work when WDP Adaptation is used for a connection and the DCS value is F5. F5 is always remapped to 4 when WDP Adaptation is enabled. We could probably fix the DCS override setting to allow and override of F5, but I'm wondering if this can be resolved in a different way. Why are you using WDP Adaptation? One of the primary reasons that people use it is to have the upstream SMSC segment a long message instead of having NowSMS segment it. Is this what you need to do? Does the value of 4 not work for your messages? (We have noticed that many operator MMSCs use a DCS value of 4 when sending out their WAP Push/MMS Notification messages, so it is somewhat common.) -- Des NowSMS Support | |||
