Getting ERROR_NO_BINARY_SUPPORT when sending XML Settings Document

Getting ERROR_NO_BINARY_SUPPORT when sending XML Settings Document SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through April 16, 2015 » Getting ERROR_NO_BINARY_SUPPORT when sending XML Settings Document « Previous || Next »
Author Message
Wai Wong
New member
Username: Nakawilson

Post Number: 1
Registered: 01-2015
Posted on Thursday, January 29, 2015 - 09:36 pm:   

I have an Android device setup as the NowSMS modem version 2015.01.17. I am getting the below error message everytime when I try to send a XML Settings Document. Do you know what could be the cause to this error? I am using android HTC One M8 with android version 4.4.3.

Here is the SMSDebug.log:
14:20:57:356 [19] CheckPreferredRoute: Available Route
14:20:57:356 [19] CheckPreferredRoute: NowSMSModem - 10.105.137.74
14:20:57:356 [19] ThreadProcessModem: Processing 54C98420.req...
14:21:00:403 [19] InetServerConnect: Connected to 10.105.137.74 (10.105.137.74:8990)
14:21:00:403 [19] BuildSMSPDU: 41220B814152890552F400F5600605040B8423F021062F1F2DB69181923243334230423743353737 373643323735384239373937383644314438323538323637453245394500030B6A0045C650035365 637572697479506F6C6963790001870503343130350006033900010101
14:21:00:404 [19] ThreadProcessModem: POST / HTTP/1.1
Content-Type: application/x-nowsms-outboundmessage-sms
Host: nowsmsmodem_10.105.137.74
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: 285


14:21:00:404 [19] ThreadProcessModem: úß‘¶{
xoYx}gjst@5$'"/!Z..!YWzG@QPAh
14:21:59:506 [19] HttpResponseWait: Ok
14:21:59:506 [19] ThreadProcessModem: HTTP/1.1 503 Service Unavailable
X-NowSMS-DeviceID: +14692226894
X-NowSMS-DeviceName: MOTest
Content-Type: text/html
Date: Thu, 29 Jan 2015 22:21:58 GMT+00:00
Content-Length: 91
Connection: Close

<html><head></head><body><p>ERROR_NO_BINARY_SUPPORT,Recipient=1425XXXXXXX</p></b ody></html>
14:21:59:507 [19] WaitForSocketClose: WinSock reported ioctlsocket complete
14:21:59:507 [19] ThreadProcessModem: Error: HTTPSMSC: Connection failed, HTTP status code = 503.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5181
Registered: 08-2008
Posted on Friday, January 30, 2015 - 03:53 pm:   

Hi,

Is it running the stock HTC firmware (I think they call it HTC Sense)? Or is it a Google Play edition?

The binary SMS support is only in the HTC firmware. We have an HTC One M8 that we use for testing. It was running 4.4.3, but I updated it to Android 5.0 (actually 5.0.1) recently so that we could verify that binary SMS was still supported. It is still supported.

Settings/About/Software Information reports Android 5.0.1 and HTC Sense 6.0.

If you do have a Google Play edition, the following site explains the steps to convert to HTC Sense:

http://htc-one.wonderhowto.com/how-to/convert-your-google-play-edition-htc-one-i nto-htc-one-with-sense-no-bloat-0148220/

--
Des
NowSMS Support
Wai Wong
New member
Username: Nakawilson

Post Number: 2
Registered: 01-2015
Posted on Friday, January 30, 2015 - 05:55 pm:   

I am using the HTC Sense version of HTC One M8. From Settings/About/Software Information, my device shows Android 4.4.3, HTC Sense 6.0, Software Number 2.25.599.1 and HTC SDK API level 6.25.

Any idea?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5185
Registered: 08-2008
Posted on Friday, January 30, 2015 - 06:12 pm:   

Hmm....I am wondering if perhaps the device is OK, but the mobile operator is blocking mobile originated WAP Push (like AT&T in the US).

In the SMSDEBUG.LOG, you should see the modem being periodically polled with an /init request, like shown below.

If the response includes "X-NowSMS-PDUMode: Yes", then this means the binary SMS API is available in the device.

13:50:48:017 [21] InetServerConnect: Connected to nowsmsmodem_HTCOneM8 (192.168.0.101:80)
13:50:48:017 [21] ThreadProcessModem: GET /init HTTP/1.0
Accept: */*
Connection: close
Host: nowsmsmodem_HTCOneM8
X-NowSMS-ReceiveSMS: Yes
X-NowSMS-ReceiveSMSPort: 8990
X-NowSMS-ReceiveMMS: Yes


13:50:48:138 [21] HttpResponseWait: Ok
13:50:48:138 [21] ThreadProcessModem: HTTP/1.0 200 OK
X-NowSMS-MCCMNC: 310260
X-NowSMS-MMSURL: http://wholesale.mmsmvno.com/mms/wapenc
X-NowSMS-DeviceID: +99999999
X-NowSMS-DeviceName: HTCOneM8
X-NowSMS-PDUMode: Yes
Content-Type: text/html
Date: Fri, 30 Jan 2015 18:50:46 GMT+00:00
Content-Length: 53
Connection: close

<html><head></head><body><p>INIT OK</p></body></html>
Wai Wong
New member
Username: Nakawilson

Post Number: 3
Registered: 01-2015
Posted on Friday, January 30, 2015 - 08:24 pm:   

oh, I am in US and I was using an AT&T SIM. Do you know which operator in US does not block WAP? I can try acquire a different SIM if you know which operator would work from your experience?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5187
Registered: 08-2008
Posted on Friday, January 30, 2015 - 09:29 pm:   

T-Mobile is the only major one that supports mobile originated WAP Push. And it can only be delivered to another T-Mobile subscriber, no cross network support.

Login Login / Register Logout Logout Search Last 30 Days Topics Topics