| SMSC Character Issue |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Ganesan New member Username: Ganesan Post Number: 19 Registered: 09-2006 |
We need to set the SMSC characterset to ASCII.But in the SMPP Configuration setup there are three character set are viewed(Default,IA5(GSM),iso 8859(Latin). The reason is when i send text with @ symbol,i am able to only get the SMS with text upto @ symbol.(When i look into the SMSOUT log the text is submited well to smpp providers) Our SMPP provider wants we set to ASCII character set. How can i sent the Character Set? Can Anyone help me. Thanks Ganesh | |||
| Ganesan New member Username: Ganesan Post Number: 20 Registered: 09-2006 |
This is urgent please anyone help me | |||
| Ganesan New member Username: Ganesan Post Number: 21 Registered: 09-2006 |
We are facing another problem with Character set. Our NOWSMS has Two SMSC Connection 1) GSM Phone 2)SMPP Connection When we send text with @ symbol like "my emailID ganesan@gistme.com" to our GSM Phone,it is logged the text exactly we send to phone in SMSIN folder. But when we send to text to Shortcode,it is logged not well. i.e timbayhome¡yahoo.com instead of timbayhome@yahoo.com This is urgent problem Please help me to solve the issue. Thanks Ganesh | |||
| Malcolm - Now Support New member Username: Malcolm Post Number: 7 Registered: 12-2006 |
Ganesh, ASCII is the lower 7-bit (0 thru 127) of iso-8859-1 ... basically the "English" characters of that character set. It is likely that this is what the service provider is asking you to use, but they are calling it "ASCII". In the GSM character set (which we use as the default), the "@" character is encoded as null. When a system is expecting ISO-8859-1, it interprets the null character as the end of the string. As you will find in other postings out here, the usual solution to this problem is to change the "SMSC Character Set" setting to "iso-8859-1 (Latin)".
This is a related issue. It happens if the SMSC is using "iso-8859-1", but we are expecting it to be using the GSM character set. Change the character set of the SMSC connection to "iso-8859-1", and it should resolve the issue. -- Malcolm Now Wireless Support | |||
| Ganesan New member Username: Ganesan Post Number: 22 Registered: 09-2006 |
We have changed to the iso-8859-1 character set. Now The text after the @ symbol is alos sent.But the problem is when we send text with @ symbol,we got the message without the @ symbol.(i.e if we send ganesan@novantus.com the result sms is ganesannovantus.com) The Other problem is We need to send the following text "GistAbuja:correct.U’ve 4925 points Osun State is in which zone(A-South-South,B-South-West,C-North-West)Txt A,B,orC to 35440 earn 15 more points" The is the URL Encoded text http://127.0.0.1:8800/?PhoneNumber=919894710352&Text=GistAbuja%3acorrect.U%e2%80 %99ve+4925+points+Osun+State+is+in+which+zone(A-South-South%2cB-South-West%2cC-North-West)Txt+A%2cB%2corC+to+35440+earn+15+mo re+points&SMSCRoute=SMPPGateWayGateway&Sender=35440 When we see the SMSOUT Log after submit the URL it is logged as follows 2006-12-16 06:32:29,SAR-919894710352-7b-3-1.req,127.0.0.1,919894710352,OK -- SMPP - smpp.clickatell.com:2345,Sender=35440;SMSCMsgId=ea62654c5fb8b1da42ee8cfe2b00119c ;Binary=1;DCS=8;UDH=0500037B0301;Data=0047006900730074004100620075006A0061003A00 63006F00720072006500630074002E00552019007600650020003400390032003500200070006F00 69006E007400730020004F00730075006E0020005300740061007400650020006900730020006900 6E0020007700680069006300680020007A006F006E00650028 2006-12-16 06:32:30,SAR-919894710352-7b-3-2.req,127.0.0.1,919894710352,OK -- SMPP - smpp.clickatell.com:2345,Sender=35440;SMSCMsgId=18dd2c7a5ed42ba4afeb01bc670d7a98 ;Binary=1;DCS=8;UDH=0500037B0302;Data=0041002D0053006F007500740068002D0053006F00 7500740068002C0042002D0053006F007500740068002D0057006500730074002C0043002D004E00 6F007200740068002D0057006500730074002900540078007400200041002C0042002C006F007200 4300200074006F002000330035003400340030002000650061 2006-12-16 06:32:32,SAR-919894710352-7b-3-3.req,127.0.0.1,919894710352,OK -- SMPP - smpp.clickatell.com:2345,Sender=35440;SMSCMsgId=b34f92464a99dd8f0037ccba950f8355 ;Binary=1;DCS=8;UDH=0500037B0303;Data=0072006E0020003100350020006D006F0072006500 200070006F0069006E00740073 after that we got the 3 understandablle sms with Ascii chars or Empty text. We need to log the exact text we send in smsout LOG. Please Help me solve this issue Thanks Ganesh | |||
| Malcolm - Now Support New member Username: Malcolm Post Number: 30 Registered: 12-2006 |
This may be a problem with your service provider. (And it may be a problem specific to your service provider's connection to a particular mobile operator.) I think you will need to ask them. There are only two options for how the "@" character can be encoded in an SMPP message submission. The default for NowSMS is to use the GSM character set, which encodes "@" as null. The alternative is to use iso-8859-1/ascii which encodes it as it's ascii value of 0x40. I believe you may need to ask your service provider for further assistance. For the second issue, I think I can provide more explanation. NowSMS analyses the message submission to determine whether or not the message text contains only characters in the GSM character set. If the message contains characters outside of the GSM character set, then the message is submitted in Unicode format. It appears that your service provider either does not support the Unicode format, or it does not support the Unicode format for delivery to your destination mobile operator. However, the only reason that NowSMS is trying to use Unicode is because of the ’ character, which is non-standard. Can you not use the standard ' character instead? -- Malcolm Now Wireless Support | |||
