| Binary SMS message is not forwarded correctly |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| David Bartelt New member Username: Dbartelt Post Number: 1 Registered: 06-2010 |
When I bind directly to Verizon I can receive binary SMS message with no problems and correctly process them. However when I use nowSMS to bind to Verizon and then forward those messages to my application based on the short code, the data seems to be corrupted. When Messages come to me they are set to BinaryDCS=2 and it seems that NowSMS is converting to a DCS of 4 This is a problem that has been seen before and we are using the clint.zip patch. http://support.nowsms.com/discus/messages/1/24851.html Maybe I missed something in the configuration, but it seems like I am back to that same problem. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2237 Registered: 08-2008 |
Hi David, Are you working with the person in the other thread? Or are you experiencing a similar issue? I would recommend that you DO NOT USE the patch referenced in that other thread. That patch is not compatible with current NowSMS product versions. (I've deleted it so that others do not accidentally download it.) Rather than patching individual DLLs, we try to package updates that include all EXE and DLL files to avoid compatibility problems and issues ... however Bryce must have been in a hurry posting that particular one. I would suggest that you re-install the current version of NowSMS to avoid problems. Now on to your issue. In the SMPP specification, data_coding values of "2" and "4" both mean binary (octet unspecified). Because "2" is not a valid data_coding value on GSM systems, or with other types of SMSC connections, NowSMS automatically remaps "2" to "4". If you have an application (or an SMSC connection) that does not understand that both "2" and "4" are equivalent data_coding values, then the settings described in that other thread are valid in current versions of NowSMS. If NowSMS is using a data_coding value of 4 for sending binary messages out to an SMSC connection, you can edit SMSGW.INI, and under the [SMPP - server:port] section header for that connection, add BinaryDCS=2. If you want NowSMS to use a data_coding value of 2 for delivering binary messages to an SMPP client application that is connecting to NowSMS, then you need to edit SMSGW.INI, and under an [SMPP] section header, add BinaryDCS=2. Note that this section header is simply [SMPP] without a server name listed. You may need to add this section header to the SMSGW.INI file, as it may not be present until you add it. [SMPP - server:port] ...other settings... BinaryDCS=2 [SMPP] BinaryDCS=2 ...other settings... -- Des NowSMS Support | |||
| David Bartelt New member Username: Dbartelt Post Number: 2 Registered: 06-2010 |
Hi Des, Sorry for the late replay. I did go back to the orginal version of the SMSMPP.DLL and it did not work. So I have gone back to the SMSMPP.DLL specified by the clint.zip patch. Are you sure the current version of the SMSMPP.DLL has Clint's fix for the problem specified in the thread? My SMSGW.ini file has the setting as suggested. This is the same system and configuration as specified by the other person, just a different site location. Please look at Bryce Norwood's comments on the situation. Thank you very much -Dave | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2339 Registered: 08-2008 |
Hi David, Yes, I just tried it, and it is working as expected. Maybe there is something that I'm missing about your setup. Your application is connecting to NowSMS as an SMPP client, correct? (An account is defined on the "SMS Users" page?) If you have a BinaryDCS=2 under a header of [SMPP] (not [SMPP - server:port]) in SMSGW.INI, then you should be seeing a data_coding value of 2 in your application. The only thing I can think of ... is are you looking at SMSGW.INI in the correct directory? Windows can sometimes play games with user rights and create copies of INI files. For Windows Vista, Windows 7 and Windows 2008, SMSGW.INI is found in the ProgramData\NowSMS directory. For Windows XP & 2003, SMSGW.INI is found in the Program Files\NowSMS (or Program Files (x86)\NowSMS) directory. Open a command prompt window with administrator access (right click on "Command Prompt" and choose "Run as Administrator"). Then change to the appropriate directory and type NOTEPAD SMSGW.INI to edit. This should ensure that you are seeing the actual SMSGW.INI if Windows rights have somehow caused multiple copies to be created. Assuming that SMSGW.INI is correct, make sure there is only one [SMPP] header. If you're not making any progress, enable the SMSDEBUG.LOG. Then, have another binary message sent in to your application. E-Mail me the SMSGW.INI, SMSDEBUG.LOG and SMPPDEBUG.LOG files. Send them to nowsms@nowsms.com with "Attention: Des" in the subject line. Also post a follow-up note here to tell me to look for that e-mail. -- Des NowSMS Support | |||
