Some special charactors are not going | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 14, 2010 ⬆ |
◄ ► |
Author | Message | |||
Neeraj Kalyan New member Username: Nk1967in Post Number: 10 Registered: 06-2006 |
Sir, I am using nowSMS ver 2006.10.31 I am sending normal text it goes ok but when I try to send @ at the rate or _ (under Score) it cut short the Message from the spl char. If I use encoding ISO-8859-1 In smsc advance settings It use the encoding and increase the length of the SMS or bifurcate the SMS. The SMSC count it as 2 or 3 SMSs which is again a loss. Please guide me what all I can do to send The spl chars. Thanks in advance. | |||
Neeraj Kalyan New member Username: Nk1967in Post Number: 11 Registered: 06-2006 |
any hints??? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2600 Registered: 08-2008 |
I'm sorry, but it is very difficult for me to support old product versions. I don't always recall or remember what options are available in older versions. Try setting the character set to "GSM" instead of "default". This will explicitly set the "data_coding" value of the SMPP request to indicate that we are using the GSM character set. The "@" character is encoded as a null character in the GSM character set, so the fact that it is being truncated at this character suggests that the SMSC is not expecting the GSM character set to be used. Another possible solution is to configure the SMSC connection to use "iso-8859-1". However, after setting this in the configuration program (and saving/applying the change) ... manually edit the SMSGW.INI file. Look for the [SMPP - server:port] section of the file where you should see SMSCCharset=iso-8859-1. Right underneath this setting, on a new line, add: SMSCCharsetDefault=Yes This extra setting will tell NowSMS to use the iso-8859-1 character set, but NOT to set the data_coding value to indicate that this character set is being used, instead just indicating a value of "default". My guess would be that your SMSC does not properly understand the data_coding parameter. -- Des NowSMS Support |