![]() ![]() (Was 'h1' in '')Īt .parse(BodyParserXmlPull.java:98) : Could not parse body:Īt .parse(BodyParserXmlPull.java:132)Īt .fromString(StaticBody.java:114)Īt .awaitResponse(ApacheHTTPResponse.java:246)Īt .getBody(ApacheHTTPResponse.java:192)Īt .processExchange(BOSHClient.java:1124)Īt .processMessages(BOSHClient.java:1000)Īt .access$300(BOSHClient.java:102)Īt $n(BOSHClient.java:1729)Ĭaused by: : Root element was not 'body' in the '' namespace. QWok+fvQjhOm+7nP0LLPqFpcVZ7f6ls41gURHroFqVpBbBNhNQUCSBpS7l/Odnu/wcQxpggsTanVFJXkCHOICw=īZzrSoMmL0L29FVpJFVO8UrjE7UAYNYWU5pzSYNQDn1TīWnG9r6a2SNH8qvfcL9u+RIdXvOPt1ITHyH/cE5UcLNiīS/Az4hezhq+cqXYIciFiqqjQ4GeuvRavvtK7eecubBuīWo3LzQ1Wi9Yxj+1e1lbREdcAnJ8tIVzXDLOKuKlvSlCīRS1eE/9pfADbcjzdpYC71zydVvFiCQ+Py2eA2sndjpf = aTalk BOSH connection via mobile network = (with certificate signed by ) when switches to a registered account on, so far they seem to have no problem. Instead of using the registered test accounts on my home server i.e.It seems that the body data is not being sent at all. There is actually no trace of any pubsub prekeys data in the ejabberd debug log. The problem does not seem to be caused by (my initial suspect)Įjabberd debug log shows that there is no data being received (reported by low level mod_bosh.erl). The resend ‘published prekeys’ always failed no matter how many attempts has been made.įound that ejabberd reports the error incorrectly should be as perīOSHClient will do the following without re-attempt, checkForTerminalBindingConditions(body, respCode) Wonder whether it is appropriate for jbosh to reconsider to make a reattempt to resend the last failed stanza.Īctually I modified the BOSHClient source, so it re-attempts to send the last stanza on bad-request failure, but without any success. This causes the whole login process to restart by ReconnectionManager. There is no attempt by jbosh to retry to resend the last bad-request stanza. Subsequent attempts to reconnect by ReconnectionManager, they too and always failed at the exact same location.īoshClient does not provide any special handler when server reported The BOSH connection always (>95%) failed when sending large amount of data to server (publish prekeys size is 9476 bytes) at a very specific location as shown in the log below during i.e.When android device is connected to network via mobile network: Steam:error is correctly reported to the upper app level.ī.ReconnectionManager is also working when WiFi connection is temporary disrupted or when switching from Mobile network to WiFi network.The XMPPBOSHConnection is able and always has no problem of a successfully login via BOSH protocol.When android device is connected to network via local WiFi network: ![]() The patched XMPPBOSHConnected has been tested using aTalk client with the following observations i.e.Ī. Problem in handling the “error” in BOSHPacketReader#responseReceived().Call notif圜onnectionError() while it is not connected.However, this may not be mandatory.Attached is the latest patch for the XMPPBOSHConnection to resolve two new problems found i.e.: Ssh to your FBX and restart your ejabberd service with sudo systemctl restart ejabberdĪs a precaution, I also created a CNAME for subdomain “conference” pointing to my main domain. “Access-Control-Allow-Headers”: “Content-Type” “Access-Control-Allow-Origin”: “ “GET,HEAD,PUT,OPTIONS” Ssh to your FBX and sudo nano /etc/ejabberd/ejabberd.yml to edit the ejabberd configuration file as follows (parts of file provided - correct indentations are not provided here, please make sure to follow the files indentation rules): ![]() Give ownership of the newly created folder to ejabberd with sudo chown -R ejabberd:ejabberd /var/www/uploadĬhange mod of your new folder with sudo chmod -R 775 /var/www/upload Ssh into your FBX and sudo mkdir /var/www/upload If you have a router, forward TCP port 5443 to your FBX. Though, this has not impacted any of my use of XMPP via clients and I am able to transfer files both to and from MUC as well as contacts.Īccess Cockpit > Networking > Firewall > Edit Rules and Zones and add TCP port 5443 to your list of services. Please note that I believe this may have harmed bosh, as I am receiving errors on the diagnostic report. Here’s how I enabled http_upload (XEP-0363).
0 Comments
Leave a Reply. |