| NowSMS is unable to handle special character. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||||
| Ti Shng New member Username: Tishng Post Number: 1 Registered: 09-2006 |
Hi, I'm using NowSMS v5.50. I tried sending a SMS containing "|" character to my NowSMS server, it seems to treat it as invalid character. I have checked the NowSMS logs, it has received the character as "|". But NowSMS sends out as ".@" to my application server based on the packet that I have captured. Is that any encoding that I need to set inorder for NowSMS to be able to handle this special character? | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6593 Registered: 10-2002 |
Hi, The current version of NowSMS is NowSMS 2006. I might be able to help you if I had some idea of what protocols you are using on each side of the connection. Note that the "|" character is encoded as 0x7C in the standard ISO Latin character set. However, in the GSM character set, it is encoded as 2 characters ... 0x1B 0x40. 0x40 = "@" in the ISO Latin character set, which might explain part of what you are seeing. I'm guessing that you are connecting to a service provider via SMPP ... and that the service provider wants you to use the ISO Latin character set instead of the GSM character set. You're using NowSMS v5.50, which is quite old. I don't think v5.50 supported anything other than the GSM character set when connecting to an SMPP SMSC. (If it does, it is configured under "Advanced Settings" under the "Properties" for the SMPP connection.) But if you are having a character set issue with a message being received from an SMPP SMSC, then it looks like v5.51b was the first version to also apply this character set handling for received messages as well as sending messages. So you would need to update to at least v5.51b. v5.51b was a free update for NowSMS v5.50. I can provide you with this update if you send an e-mail to nowsms@now.co.uk with a subject of "Attention: Bryce" and include your serial number and company name. The current version, NowSMS 2006, is a paid upgrade from previous versions. -bn | |||||
| Ti Shng New member Username: Tishng Post Number: 2 Registered: 09-2006 |
Hi Bryce, Thanks for the update. Sorry I didn't make my problem clear enough. I'm using a GPRS modem as my SMSC connection type and then using SMPP protocol to transfer the message to my application server. How do I address the character set issue that I'm having now? If there any configuration file that I can just edit manually? Thanks, - TS | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6605 Registered: 10-2002 |
Hi TS, I might need you to enable the SMSDEBUG.LOG, so that I can see the message flow. You can enable this log on the "Serial #" page of the configuration dialog. Enabling this log will also enable the SMPPDEBUG.LOG automatically, and I would be interested in seeing both files. However, I think I understand what is happening. NowSMS always uses the GSM character for transmitting messages to an SMPP client. So it is encoding "|" as 0x1B 0x40. Check your SMPP client software to see if there is a setting to handle the GSM character set. (We don't have a setting to force the character set to iso-8859-1/Latin for clients connecting to NowSMS as the server ... only for NowSMS connecting to another SMPP server as a client.) -bn | |||||
| Ti Shng New member Username: Tishng Post Number: 3 Registered: 09-2006 |
Hi Bryce, Attached are the requested
| |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6628 Registered: 10-2002 |
Hi TS, That is as I expected (at least in my more recent reply ... not the first reply). NowSMS always uses the GSM character set for delivering text messages to an SMPP client. So it is encoding "|" as 0x1B 0x40, because that is the correct encoding for the GSM (IA5) character set. Unfortunately, there is not an option to change the character set that NowSMS uses when delivering messages to SMPP clients. (You can change the character set when NowSMS is connecting as an SMPP client to an SMPP server, but not when NowSMS is the SMPP server.) We should add similar character set configurability when acting as an SMPP server, so I'm investigating getting that added in a future version. But right now, the SMPP server is stuck using the GSM character set. -bn | |||||
| Ti Shng New member Username: Tishng Post Number: 4 Registered: 09-2006 |
Hi Bryce, Thanks for the information and really appreciated your help. Guess I just had to live with that now. Will there be any patches available or free upgrade from my current NowSMS version in the future to cater for the SMPP server? Thanks, TS | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6637 Registered: 10-2002 |
Hi TS, I don't expect any further updates to be released for the SMS components of the v5.5x version. I can confirm that we have added configuration settings for the character set used by the SMPP server in the next update of NowSMS 2006, so you might want to investigate upgrading. For more information on what has been added between v5.51 and NowSMS 2006, see the following links: http://support.nowsms.com/discus/messages/53/14150.html http://support.nowsms.com/discus/messages/53/15129.html -bn | |||||
| Ti Shng New member Username: Tishng Post Number: 5 Registered: 09-2006 |
Hi Bryce, Would you mind sending a email to me on the upgrading pricing. I will discuss with my management whether we want to upgrade our NowSMS. | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6657 Registered: 10-2002 |
TS, I've asked one of my colleagues to follow-up with you via e-mail. If you don't receive anything, try sending an e-mail directly to nowsms@now.co.uk. -bn | |||||
SMPPDEBUG
