#296 Disconnects/reconnects on sent messages (and it fails to delivers it)

[Olivier Bilodeau]

Every time I send a message I get disconnected and the message is not delivered. I tried searching for a FAQ entry and didn't find any. Looking at the logs and googling error messages didn't reveal anything useful.

Back-end: A business on Office 365

Running Arch Linux with sipe 1.20.1-1 and pidgin 2.10.11-6.

[Stefan Becker]

Does look like a server error or problem on the remote side. Log shows that for the INVITE attempt under Call-ID: 9826gF660aE774iB5F4m4DD3tC057bC674x0E3Ex the server aborts after a while with an error message:

MESSAGE START <<<<<<<<<< SIP - 2015-11-09T20:30:05.090964Z
SIP/2.0 504 Server time-out
...
From: "Olivier Bilodeau"<sip:obilodeau@[domain]>;tag=746662575;epid=1df2b110f763
To: <sip:mdube@[domain]>;epid=98b97c7f0e;tag=4129E5C1C1FAC29207B56A4E0549905E
Call-ID: 9826gF660aE774iB5F4m4DD3tC057bC674x0E3Ex
CSeq: 1 INVITE
Server: RTC/6.0
ms-diagnostics: 1006;reason="Error routing on client connection";winsock-code="10057(WSAENOTCONN)";winsock-info="The socket is no longer connected";Peer="mdube@[domain]" Destination="10.8.148.7";source="BL20A09FES13.infra.lync.com"

Can't fix server or remote error in SIPE. Closing as INVALID.

[Olivier Bilodeau]

Server is microsoft's own office 365 infrastructure. We are using their hosted service for business.

Server and remote works as I can reach that same user with Lync 2013 on Android. Tried pidgin-sipe (failed) then lync on android (success) and then pidgin-sipe (failed) successively so it's not that something changed on their end.

So no problem in either server or remote if using the right client. This is what I would categorize as a SIPE problem (or a configuration issue on my end that would be undocumented in your FAQ).

[Stefan Becker]

Unfortunately there is a flaw in your test procedure. All that you have proven is that another client on some other device works using a different transport path. The client might even talk to another server.

I can only base my conclusions on the log you provided: SIPE sends an INVITE and after some transient responses the server responds with a fatal 504 error that includes a diagnostic pointing to a problem with the remote side.

To prove that the bug is in SIPE you would need to

• run SIPE and Lync on the same machine.
• perform the same action in both clients, and
• compare the SIP logs from both clients to show that SIPE is missing to sent some relevant protocol data and/or is sending some incorrect protocol data.