hi all,
I've an ejabberd 2.1.5.3 on debian 6 with a s2s connection to a xmpp gateway (connected to a lync server).
the users on the lync side can see the users on the ejabberd side, and vice versa. even the presence states
are _always_ updated in both directions. but only one or two messages pass between the two domains
(even if presence state updates are running normally....).
this is a message from a presence state change on the linux side (tcpdump...):
<presence from="james.bond@lynclab1.local" to="spectre@localcedat85.com"> <show>dnd</show> <priority>1</priority></presence>
and on the pidgin client I see the change almost immediately (and the same if I change the state on
pidgin...).
but messages flow through the servers (I see them with tcpdump on linux), but are not delivered. like this one from lync to pidgin:
<iq from='spectre@localcedat85.com' to='james.bond@lynclab1.local' type='error'><query xmlns='http://jabber.org/protocol/disco#info'/><error code='503' type='cancel'><service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>
or this one from pidgin to lync:
<message from='spectre@localcedat85.com/mctaurino' to='james.bond@lynclab1.local' type='chat' id='purple582942a3'><active xmlns='http://jabber.org/protocol/chatstates'/><body>123 123 123 123 </body></message>
whisi is different, but _not_ delivered.....
any ideas? (besides throwing out lync...)
many thanks!
francesco
At what point do these
At what point do these messages disappear? I mean, do you see them between ejabberd and pidgin, or between ejabberd and gateway?
And what is in ejabberd logs and client XML console?
hi, the "presence" messages
hi,
the "presence" messages "flow" without problems.
the "chat" messages go from the pidgin client to the ejabberd server then to the xmpp gw, where they stop.
or from the lync client to the edge server to the xmpp gw to the ejabberd server, where they stop with that
error message. and are not delivered to clients.
f