| ä %C3%A4 and ö = %C3%B6 Special Character Issue |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 03, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Vishal Unregistered guest |
Hi Bryce, I am facing a problem on this 2 special characters. ä %C3%A4 and ö = %C3%B6. Other speical characters are wroking viz å is working fine. But this 2 only dont work. Have gone though each and every thread and tried everything. Viz I tried ETSI GSM 03.38, iso-8859-1, us-ascii, big5, big-5, gbk, gb2312, gb2312-80, shift-jis, shift_jis, iso-8859-2, iso-8859-4, iso-8859-5, iso-8859-6, iso-8859-7, iso-8859-8, iso-8859-9. But I was not successful. I am connecting via SMPP. Can you let me know the precise definition of the contents of the SMPP 3.4 submit_sm fields data_coding and short_message. Thanks in advance. Vishal Sharma | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2942 Registered: 10-2002 |
Hi Vishal, Let's take this step-by-step. Are you able to send those characters correctly using the web interface of NowSMS (the "Send Text Message" form)? If not, then we'll have to troubleshoot the connection from NowSMS to your SMSC. (What type of connection is it?) If that does work properly, then we can troubleshoot your SMPP connection into NowSMS. NowSMS expects ETSI GSM 03.38 encoding for SMPP submissions. So in an SMPP submission, it would expect ä = 7B and ö = 7C. (NowSMS as an SMPP server expects data_coding to be 0.) | |||
| Vishal Unregistered guest |
Hi Bryce The GSM 3.38 chars B7 and C7 are not displaying properly as ä and ö but as three letters {¹@ Tested via web interfact but the Messages did not terminate. Tried via NOWSMS HTTP URL. The message did come through but there was no special characters. If data_coding was not 0 when submitted would it have been an issue??? Let me know on this and also let me know what parameter should be passed for short_message? Am connecting via SMPP 3.4 to the SMSC. Thanks for your help. Regards Vishal | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2949 Registered: 10-2002 |
Hi Vishal, I think I am going to need to see some log files to fully understand this. I am particularly concerned that if a message cannot be properly submitted via the NowSMS web interface, then I would not expect a submission from an SMPP client to work properly. But before we get into the log files, am I correct that you are using NowSMS to also connect to an SMSC via SMPP? That SMSC might require that the character set be explicitly set. We made a recent update to NowSMS to allow it to explicitly set the character set on an SMPP connection. This update is not yet ready for release, but I would like to try it in your setup to see if it makes a difference. Please send an e-mail to nowsms@now.co.uk referencing this thread, and I will e-mail you the update to try. -bn | |||
| Vishal Unregistered guest |
Hi Bryce Thanks for your email. Will test it out and let you know the feedback. One more issue i wanted to know about. Is there a way where the users defined in the SMS users can view/check their status Online via a HTTP URL. Viz http://IP:8800/?user=XXXX&password=XXXX&status This would help the users to keep on checking their account details periodically. Thanks a lot. Vishal | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2984 Registered: 10-2002 |
Hi Vishal, I assume that you are referring to the available credit balance? We did add a feature in v5.50, where this value is displayed at the bottom of the "Send Text Message" form in the web menu interface. It would be nice to have a separate URL that would just report this value back, but for users to check, the web menu interface would work. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2985 Registered: 10-2002 |
Vishal, I'm also curious if this ability to set the character set for SMPP submissions addressed your problem. This feature is now included in the v5.50c patch that is available: http://www.nowsms.com/download/nowsms550c.zip And it will be included in future post-v5.50 versions. -bn | |||
| vishal Unregistered guest |
Hi Bryce, Regrets for the delay. I was not keeping well. Tested the patch which you emailed and am facing the same problem. I did as advised by you in ur email. "Try setting this to "IA5 (GSM)". This is the default that we use for text messages (unless the message uses characters outside of this character set, in which case UCS-2 is used automatically) ... but by default we do not set a flag to indicate that this is the character set we are using." This did not work. Also regarding available credit balance. I think you are talking about the credit characters left per SMS. I was talking about available account balance. I mean lets say I have 1000 credits for one user. How can the user know how many credits are balance if he would like to check. Do let me know Thanks in advance. Vishal Sharma | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3099 Registered: 10-2002 |
Hi Vishal, Let's take a look at your debug logs, and make sure that the two different settings options are being set properly, and the text that goes out is correct. (To enable the debug log, manually edit SMSGW.INI and add Debug=Yes under the [SMSGW] header. Then restart the NowSMS service. NowSMS will now produce SMPPDEBUG.LOG and SMSDEBUG.LOG as it runs. I am interested in the SMPPDEBUG.LOG.) Set the flag that I mentioned to indicate that IA5 (GSM) is being used as the character set. ä should go out as 0x7B, and ö should go out as 0x7C. (If you need help with the debug logs figuring out if things are being sent out correctly, just post excerpts in reply.) It might be that your provider's SMSC doesn't support the GSM character set. That would be unusual, but it's not impossible. I have seen one SMS provider's SMPP implementation that only supported iso-8859-1 (Latin). We also have a setting for using iso-8859-1 as the character set instead, so give that a try. (The service needs to be restarted after making this change, and the SMPPDEBUG.LOG will be overwritten, so save the previous copy of this file before making that change.) Using that setting, ä should go out as 0xE4, and ö should go out as 0xF6. However, with this setting, some characters that are part of the standard GSM character set (especially Greek characters) will not be able to be sent. å needs to be sent out using Unicode ... forcing the entire message to go out in Unicode format (limit of 70 characters per message instead of 160 when this format is used). So that is why that character is working. If the above settings don't get you anywhere, then we can try adding a setting to force all messages with selected characters to go out in Unicode format (but messages containing these characters will be limited to 70 charcters per message instead of 160). It may also be worth attempting to talk to your SMS service provider to find out what the character set is that they support. -bn | |||
