| Android modem - concatenated sms - error |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Lite Support ⬆ |
◄ ► |
| Author | Message | |||
| peter chanq New member Username: Qqblog Post Number: 41 Registered: 10-2012 |
below error message happens when we send concatenated sms. retry pending - httpsmsc : connection failed, http status code = 503 after a few retry, the sms could be sent ok. this happens for version 2014.06.* and 2014.05.* nowsms lite and nowsms android modem. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5114 Registered: 08-2008 |
Hi Peter, Have you tried different devices and/or SIM cards from different operators? I've tried a number of different combinations, but have never seen this issue. To get an idea of what the underlying failure code is, please enable the SMSDEBUG.LOG. There should be a log of an HTTP transaction with the device. I am specifically interested in details of the HTTP response from the device, which is reporting this as a 503 error. A normal response looks like this: 18:57:07:597 [18] ThreadProcessModem: HTTP/1.1 200 OK X-NowSMS-DeviceID: xxxxxxxxxx X-NowSMS-DeviceName: yyyyyyyy Content-Type: text/html Date: Wed, 19 Nov 2014 23:57:08 GMT+00:00 Content-Length: 71 Connection: close <html><head></head><body><p>OK,Recipient=zzzzzzzzzzz</p></body></html> The 503 response should have an additional error code in the HTML section of the response. What do you see? -- Des NowSMS Support | |||
| peter chanq New member Username: Qqblog Post Number: 43 Registered: 10-2012 |
here is smsdebug log for concatenated sms <html><head></head><body><p>ERROR_GENERIC_FAILURE,Recipient=xxxxxxxx</p></body>< /html> 15:29:27:451 [16] WaitForSocketClose: WinSock reported ioctlsocket complete 15:29:27:451 [16] ThreadProcessModem: Error: HTTPSMSC: Connection failed, HTTP status code = 503. 15:29:27:451 [16] ThreadProcessModem: Processing SAR-xxxxxxxx-547467d6-2-1.req... 15:29:27:457 [16] InetServerConnect: Connected to xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx:8990) 15:29:27:457 [16] ThreadProcessModem: POST / HTTP/1.1 Content-Type: application/x-nowsms-outboundmessage-sms Host: nowsmsmodem_xxx.xxx.xxx.xx User-Agent: Now SMS/MMS Gateway v2014.06.30 X-NowSMS-ReceiveSMS: Yes X-NowSMS-ReceiveSMSPort: 8990 X-NowSMS-ReceiveMMS: Yes Accept: */* Connection: close Content-Length: 1135 15:29:27:457 [16] ThreadProcessModem: !¦¾+¿:Ak|{n^y~furwA2$;%5/~,*))+ ym~kyT5¢”SŒ h 6 rqpf|}cq l|i{wjiwfpyf|cyez"#G!kæÞ7’:O/KZ5T@KQM7R@<_9EX==¥ÇǦ¼½£²±¬¼Î©´¶ªÓ¨·¥Ñ°Â¾}Úyw+¨˜„æš ã‚ë‘èîˆèê•óŠ–ò“‚ýœøƒ™þ‡šö„çõ…àó…w ô¢ûUèk6ôä–ñ”îòà˜ÿã™øÅØÛÆÓ ÃÞÐÌ®©Éիʶ ×µÌÐòÝÏæߪ¯ M;!FD"NL/24(JN5&W6,,3V <,^9Y':ca 15:29:27:644 [16] HttpResponseWait: Ok 15:29:27:644 [16] ThreadProcessModem: HTTP/1.1 503 Service Unavailable X-NowSMS-DeviceID: 353106062536451 X-NowSMS-DeviceName: Ssneo Content-Type: text/html Date: Thu, 04 Dec 2014 07:29:34 GMT+00:00 Content-Length: 86 Connection: Close | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5128 Registered: 08-2008 |
What is the device and version of Android? Do you sometimes see similar problems if you try sending long messages via the built-in messaging app? From some internet searching, it seems some people are having this type of problem with some Samsung devices on 4.4.x Android versions, and it can be recreated using the built-in messaging app, suggesting it is a system level bug. If this is the case, the only work-around (other than a firmware update) we could potentially explore would be to divide the message and send the parts separately. But then the receiver would not see a single long message. We'll do some more research, but it would help to know the device and version. -- Des NowSMS Support | |||
| peter chanq New member Username: Qqblog Post Number: 44 Registered: 10-2012 |
android 4.4.4 samgung S3 neo model number : GT-I9300I | |||
| L Zau Khum New member Username: Zau Post Number: 4 Registered: 01-2017 |
Which Android version or android phone should use to avoid concatenated sms - error. Currently i am using Now SMS Gateway Lite Edition (2014.05.30) Thanks Zau | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5845 Registered: 08-2008 |
Hi Zau, This discussion thread is the only report that I am aware of regarding this problem/issue. We were never able to recreate this problem (but we never acquired this specific device). That said, there have been many code changes since 2014...both in Android and NowSMS. Android 4.4 was current at the time of our 2014 release...but most phones on the market now are running later versions. Generally speaking, we have seen more stable behavior on Android 5.x, 6.x and 7.x, compared to earlier versions. From the NowSMS side, there were issues in the 2014 version, where in some situations, we were submitting messages faster than some devices could process, resulting in sporadic failure/retry behavior. You may want to try the 2016 version of the Android app, which should work with the 2014 software. To download, go to https://www.nowsms.com/download-free-trial and scroll down to previous releases. -- Des NowSMS Support | |||
