Looking at what ECM is printing in the way of error messages I saw the following:
config = { server: { host: 'localhost', port: 6280 },
client: { port: 8280 },
misc: { prefixLength: 32 } }
server is now listening to port 8280
now connected to localhost:6280
0000000409|00000000000000000000|POST /http-bind/ HTTP/1.1
Host: ubuntu2
User-Agent: Pidgin 2.6.6 (libpurple 2.6.6)
Content-Encoding: text/xml; charset=utf-8
Content-Length: 225
<body content='text/xml; charset=utf-8' secure='true' to='ubuntu2' xml:lang='en' xmpp:version='1.0' ver='1.6' xmlns:xmpp='urn:xmpp:xbosh' rid='2535528048031658' wait='60' hold='1' xmlns='http://jabber.org/protocol/httpbind'/>
sendToServer
This gibberish means that I have to make up less stuff to fill out a blog posting, but it also means that ECM is able to connect to Megaphone and furthermore that I was able to send some fairly credible looking data to Megaphone.
Looking at the ejabberd log I get the following:
=INFO REPORT==== 2012-02-23 10:48:39 ===
D(<0.368.0>:megaphone:57) : megaphone is starting up with Socket = #Port<0.3805>
This means that at least megaphone was able to start up in response to ECM. I don't see anything from Megaphone in response to the packet sent from Pidgin, which means it's back to the source code to put in more debugging statements.
When taken together what this all means is that the damn thing isn't working, but I am making some progress. One can infer a number of things from this, but I choose to think that I am making titanic, frog-like leaps of progress through a swamp of confusing messages.
Really.
Next time: more debugging statements from inside Megaphone.
No comments:
Post a Comment