Wednesday, February 22, 2012 1:26 AM
Starting with the March 2012 release, all XMPP apps connecting to xmpp.messenger.live.com must handle the defined stream error condition “see-other-host”. For details, see the “see-other-host” section in RFC6120: XMPP: Core.
This is a breaking change. All apps, including those built upon the December 2011 release functionality, must handle “see-other-host”. Any app that uses the Messenger XMPP service but doesn’t also implement “see-other-host” will no longer be able to log in to the service.
Please let us know if you have any questions about this upcoming breaking change.
Wednesday, February 22, 2012 8:32 AM
Hello Casey & Dare,
Connection to XMPP messenger.live.com indeed returns :
<stream:error xmlns:stream="http://etherx.jabber.org/streams"><see-other-host xmlns="urn:ietf:params:xml:ns:xmpp-streams">beta.gateway.messenger.live.com</see-other-host><text xmlns="urn:ietf:params:xml:ns:xmpp-streams">re-directing</text></stream:error>
So, after trying to connect on beta.gateway.messenger.live.com, using port 5222, it is failling again.
More over, trying a DNS check on the server returns : beta.xmpp.messenger.live.com:5222
I've try to use DNS discovery mode (and to hardcode url + port), none of them works.
A problems still exists, what is the good way to connect to XMPP service ?
Wednesday, February 22, 2012 9:13 AM
I have the same problem.
When received see-other-host( which is beta.gateway.messenger.live.com), I try follow steps
1)new socket which address is beta.gateway.messenger.live.com and port is still 5222
3) beginreceive:catch exception as follow:
System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host
Does these steps right? how to fix the problem?
Wednesday, February 22, 2012 3:08 PM
Wednesday, February 22, 2012 4:04 PM
We apologize for the inconvenience. We are investigating why this isn't working, and I'll post an update on the issue before the end of the day.
We appreciate your patience as we work through this.
Wednesday, February 22, 2012 7:50 PM
Thanks for the update. We have around 1800 connections that are down (more sign up every day).
Of separate note, we really, REALLY, ReAlLy, reaLLY would like to have an escalation path besides these forums. We are, figuratively speaking, a canary in the mine. We are perfectly willing to inform you of the canary's death the moment we detect it, if that helps.
We also talked about the see-other-host issue in this thread (from 2.5 weeks ago:
In fact, I think it was a "breaking" issue then. We have always supported see-other-host redirection. We tried to suppress server redirection when we noticed the new server just hung during connection, but found that the "old" server refused to talk to us after it gave us the "see-other-thread" error.
We use this API rather intensively already. We certainly would have information of use to Microsoft from a stability standpoint.
John Carroll Director of Technology ForgetMeNot Software
- Edited by John Carroll in LA Wednesday, February 22, 2012 7:51 PM
Wednesday, February 22, 2012 11:13 PM
Thanks again for your patience as we work through this issue. We have been able to reproduce the issue on our side, and we have identified two changes that we need to make to get this back up and running for all affected users.
One of these changes has already been completed, and we can observe that users are starting to come back into the system.
The second configuration change is in progress but will take more time to complete. We expect that it will be complete within 24 hours. This should fix the issue for the remainder of users who aren't unblocked by the first configuration change.
Some users should already be unblocked, but others will continue to receive errors until the second change is complete. I'll update this thread again once the second and final change has been completed.
Thursday, February 23, 2012 12:41 AM
We have finished applying both changes to our service. The issue should be resolved.
XMPP applications should now be able to connect to Messenger via xmpp.messenger.live.com.
Please let us know if this issue persists for you. Again, thank you all for your patience as we worked through this issue.
Thursday, February 23, 2012 1:53 AM
It works good now, Thank you and your team!
Thursday, February 23, 2012 7:29 AM
It works again, thank you for your attention and quick response.
Thursday, February 23, 2012 8:06 AM
pleased too see that service is back.
Tuesday, February 28, 2012 10:28 AM
since last upgrade on your gate, it seems that token duration (refresh_token) isn't stable, in fact for some reason my token is frequently rejected so I should make a Oatuth from scratch (which is not user friendly).