| Problems with "underscore" character |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Marcos Nowosad New member Username: Mnowosad Post Number: 6 Registered: 08-2006 |
When we are sending Mobile-Terminated (MT) messages through nowSMS, we are getting some problems with the underscore ( _ ) character. Depending on the carrier, we have different (incorrect) results: - In Verizon devices, we get the single quote ( ' ) character. - In Cingular Orange, we get the paragraph (§) character. We are currently using the ISO 8859-1 char set, as recommended by our SMSC (mBlox). Every other character is transmitted correctly. Have you heard about this problem? Is there a workaround? Thanks, Marcos | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6563 Registered: 10-2002 |
Hi Marcos, Do you get the correct character with other carriers? In the ISO-8859-1 character set, the _ (underscore) character uses code 0x5F. In the GSM character set, character code 0x5F is § (paragraph). And the underscore is 0x11. (0x11 is not valid in ISO-8859-1.) So I suspect that there may be some character set confusion with mBlox's upstream SMSC connection ... in other words, the connection from mBlox to these mobile operators. As a sanity check, you might want to enable the SMSDEBUG.LOG in NowSMS ... and take a cursory look at the SMPPDEBUG.LOG to verify that the _ character is going out as 0x5F (there is a hex dump of the SMPP transactions in this log, so you should be able to verify this fairly easy). Unfortunately, I don't have any other suggestions. I haven't heard any reports of this before, but maybe others will see this thread and report back if they see any issues. -bn | |||
