| Special charcters |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Omar New member Username: Kfsmart Post Number: 39 Registered: 01-2008 |
I have a virtual mobile number hosted at one providers,I'm receiving SMS from different operators,but for users Libyana mobile operator I'm receiving some messages with strange characters as below: 2010-05-24 00:08:40,+21892xxxxx,Text,4Xlv,xxxx 2010-05-24 00:41:09,+21892xxxxx,Text,4XLF,xxx Can you please advise how this problem can happen?And what can I do for it? Note: I contacted the hosted company and they told they are receiving the same then no problem at my nowsms configuration. | |||
| Omar New member Username: Kfsmart Post Number: 40 Registered: 01-2008 |
The expected message must be 40125,40175,40254 and if there is a text inside the message then it will be ok. as an example one user sent only numbers,I received as : 21892xxxxxx,Text,4XLF,xxxx then he sent the same message with same text and then it was received ok: 2010-05-+2189xxxxxx,Binary,063106420645002006270644062E0644063706470020003400300 03100320034,xxxx | |||
| Omar New member Username: Kfsmart Post Number: 41 Registered: 01-2008 |
This is the reply of the SMPP provider ,hope it help "The sending SMSC are passing the messages in ISO 8859-1 (Latin) format. 2010-05-29 11:22:14|0|+xxxxx|+967xxxxxx|936:V2|0201013458ACFAA5 2010-05-29 11:22:38|0|+xxxxx|+967xxxxxx|936:V2|0201013458ACFAA5 We sent messages transparently." | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2175 Registered: 08-2008 |
Hi Omar, I need more detail. For example, I do not understand what the text is that is sent, and what it is that is received. "We sent messages transparently" might be a clue. There are some old SMSCs that expect all messages to be submitted using 7-bit packed encoding. Have you tried the 7-bit packed encoding options on the "Advanced Settings" page the SMPP configuration? -- Des NowSMS Support | |||
| Omar New member Username: Kfsmart Post Number: 42 Registered: 01-2008 |
Hi Des, I'm expecting to receive message begins with 40 and then 1,2 or 3 digits like 401,40120,4011,etc but I'm receiving for libyna mobile and yemen mobile users 4Xlvor 4XlF, if the user send any word after the above mentioned keyword then it will be received correctly. How this is clear | |||
| Omar New member Username: Kfsmart Post Number: 43 Registered: 01-2008 |
**Hope this clear thanks | |||
| Omar New member Username: Kfsmart Post Number: 44 Registered: 01-2008 |
To not get in misunderstanding I will summarize the case. we have a virtual mobileno and hosted at one of the companies and we are connecting with it through SMPP. At this mobile number we are receiving SMS from many operators and the expected message to be received from the user 40 plus 1,2,or 3 other digits like 401,402,405,40100,4015,etc.. but at some operators ,many times, we are receiving like this 4Xl ,4X 6,4Xlv or 4XlF. I contacted the SMPP provider and It said that it is submitting what he received and this is what it received : 2010-05-29 11:22:14|0|+xxxxx|+967xxxxxx|936:V2|0201013458ACFAA5 2010-05-29 11:22:38|0|+xxxxx|+967xxxxxx|936:V2|0201013458ACFAA5 My problem that I didn't know where is the problem exactly ,Is it at operator side or at SMPP provider or at myside(nowsms) thanks. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2181 Registered: 08-2008 |
Hi Omar, OK ... I guess this is what I do not understand: 2010-05-29 11:22:14|0|+xxxxx|+967xxxxxx|936:V2|0201013458ACFAA5 2010-05-29 11:22:38|0|+xxxxx|+967xxxxxx|936:V2|0201013458ACFAA5 I'm not sure what that means. It appears to be some log format from their system, but what those hex numbers mean is not known to me. I suspect that they are sending you messages in 7-bit packed format. Here's what I'd suggest. Edit SMSGW.INI, and under the [SMPP - x:###] header for that connection, add this: GSMPackReceive=Yes Restart the NowSMS service, and try sending in another message. If that doesn't resolve the problem, then I'd like to see an SMPPDEBUG.LOG showing the messages being received. (It would help if you also tell me what text is expected in the message that you are receiving.) The SMPPDEBUG.LOG is enabled when you enable the SMSDEBUG.LOG. If you want to send it via e-mail instead of posting it publicly, send it to nowsms@nowsms.com with "Attention: Des" in the subject line. -- Des NowSMS Support | |||
| Omar New member Username: Kfsmart Post Number: 45 Registered: 01-2008 |
Hi Des, 020101 is the header 3458ACFAA5 is the text.(ISO 8859-1 (Latin) format) | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2184 Registered: 08-2008 |
Hi Omar, In iso-8859-1: 34 = 4 58 = X AC = ¬ FA = ú A5 = ¥ So I think it is safe to say that the text is not actually encoded in iso-8859-1/Latin format. I suspect that it is 7-bit packed. Have you tried the GSMPackReceive=Yes setting under the [SMPP - server:port] header that I mentioned previously? Can I see an SMPPDEBUG.LOG to better understand what is actually being received? -- Des NowSMS Support | |||
| Omar New member Username: Kfsmart Post Number: 46 Registered: 01-2008 |
hi, I just added GSMPackReceive=Yes and by the way I sent you SMPPdebug.log by mail. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2187 Registered: 08-2008 |
I need to see an SMPPDEBUG.LOG that shows a message being received, so try again. (Make sure that SMSDEBUG.LOG is enabled, otherwise the SMPPDEBUG.LOG will only show test binds from when the connection was last added/edited.) | |||
| Omar New member Username: Kfsmart Post Number: 47 Registered: 01-2008 |
Hi Des, I sent you. Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2191 Registered: 08-2008 |
Hi Omar, Ok ... now I'm really confused. The message format coming in from the provider looks perfectly normal to me. There should be no need for special settings. However, having GSMPackReceive=Yes in the configuration, like I suggested above, would cause NowSMS to corrupt the message, like what is shown in your logs. However, if GSMPackReceive=Yes is NOT in the configuration, then I would expect the message should be processed normally. Remove GSMPackReceive=Yes from the configuration, and generate another SMSDEBUG.LOG/SMPPDEBUG.LOG. Also let me see all of the parameters that are set in the [SMPP - server:port] section for that particular SMSC connection. -- Des NowSMS Support | |||
| Omar New member Username: Kfsmart Post Number: 48 Registered: 01-2008 |
Hi Des, I removed GSMPackReceive=Yes and I sent you the logs you requested | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2204 Registered: 08-2008 |
Hi Omar, That one is definitely a bug/problem in the other system. They are not setting the "data_coding" header to indicate that the message is encoded in Unicode format. Instead "data_coding" is set to 0, which indicates default text encoding. I can't see any way for us to know that this message was supposed to be in Unicode. -- Des NowSMS Support | |||
| Omar New member Username: Kfsmart Post Number: 49 Registered: 01-2008 |
Thanks DES Really apperciate it. | |||
