I know its been a long time, but I just wanted to do an update on our (as yet unsuccessful) efforts to get encrypted server-to-server messaging going between Openfire 3.10.0 Alpha and MS Lync 2013. First, we finally did get fully encrypted s2s between two Openfire servers, one running 3.9.3 and the other 3.10.0. This was with everything completely locked down (TLS mandatory, Dialback not available, etc.). I was then able to (briefly) get a message from a Spark client talking to Openfire out through Lync and to my Lync client. But when I tried to reply Lync barked that "This message was not delivered to mytest@devchat.example.com because the service is not available". At first I thought that mean that Openfire wasn't available, but all my Openfire clients were still happily chatting away. Then my partner on the Windows side advised that the Lync XMPP service had crashed. He cranked Lync XMPP back up and we both tried going back and forth a few times with the same results. My network people tell me that their firewalls and load balancers (BigIP LTMs) shouldn't be causing any issues. Keep in mind that we were successfully able to do messaging and exchange presence info between this same Lync cluster and Openfire 3.9.3 so long as we kept TLS disabled and allowed Dialback. The Openfire logs (including debug) and wireshark traces don't show anything obviously amiss (in fact they demonstrate successful TLS handshaking and acceptance of messages right up until Lync stops listening). If anyone can think of a reason Openfire might be doing something untoward here to Lync, let me know. Right now my working theory is that this is a Lync problem, but since I'm unable to find evidence that anyone else has ever got encrypted s2s working between Openfire and Lync this is still unchartered territory.
↧