| Sending more that 70 chars arabic SMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | ||||||
| ram Unregistered guest |
Hi is there some parameter that i have to set to send a message more than 70 chars over the HTTp request from my application. it is working fine from the the web interface but i get the erro "Message Length is invalid" where submetting using the HTTP request in my application thanks in advance | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3672 Registered: 10-2002 |
NowSMS won't return that error, as it will automatically segment the message to be sent using concatenated SMS. Therefore, I need more clarification about your configuration. Where exactly are you seeing this error message? | ||||||
| ram Unregistered guest |
Hi Bryce i am seeing this error messagee in the SMSOUT log file (file attached)
also the message is attached
| ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3682 Registered: 10-2002 |
Hi Ram, That is bizarre. The SMPP server is rejecting the messages, returning an error response that states that the message length is invalid. But it clearly is not. In fact, looking at the first example, it is only 132 bytes, when the limit is actually 140. I tried submitting the same message to an SMPP account that I have ... only changed the recipient phone number ... and it was sent and received correctly. (Well, I received Arabic text, followed by a "..." indicating that I had only received part of a multipart message.) So I think something is wrong at your service provider, and how they are handling the receipt of Unicode messages. What happens if you try some shorter messages? For example, try sending a message of exactly 70 characters. Does that work? (It should be sent out as only a single message.) Assuming that it does not work, try shorter messages to attempt to determine what the limit is with your provider. We could probably break the messages at a smaller limit, but this should not technically be required. -bn | ||||||
| ram Unregistered guest |
Hi the shorter message is already working and users recive the 1 sms message kindly tell me what to check with the operator to make sure i can send larger messages thanks ram | ||||||
| ram Unregistered guest |
Hi also with the long english messages i recive trash not regular text , and i found in the logs that the nowsms treats the long english messages as binary messages if you like i can send you all the logs and debug files it is very very urgent Please advice thanks | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3773 Registered: 10-2002 |
ram, Apologies for the delay. For the long English text messages coming out as trash, there is a setting under "Advanced Settings" in the SMPP configuration. You want to UNcheck "Encode long text messages with 7-bit packed encoding". We default to this setting, but there is ambiguity in the SMPP specifications, and different servers can implement things slightly different. However, this doesn't get us any closer on the long Unicode message problem. An SMPPDEBUG.LOG might be helpful. Just X out the data that contains your username and password. Also, can you please answer my question above. Send a message of exactly 70 unicode characters. Does that work? -bn | ||||||
| ram Unregistered guest |
HI thanks for your replay, the exactly 70 arabic messages are working fine, the problem is in the larger than 70 chars messages attached is the SMPPDEBUG file as per your request
| ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3783 Registered: 10-2002 |
Unfortunately the debug log just shows connecting and disconnecting ... no attempt to send a message. Make sure the debug logs are enabled ... edit SMSGW.INI, and under [SMSGW] add Debug=Yes. | ||||||
sms out log
sms file 1
