ive been at this for 2 days with no success. i tried using im+ and it never connects. i tried changed the plists but im corrupting the app by doing so… 
has anyone SUCCESSFULLY got a mobile client to work, and could you list the steps? thanks in advance 
btw im on a jailbroken iphone 5 running iOS 6.1
no. escargot doesnt support the protocol it uses & crosstalk doesn’t support the login
Escargot and Crosstalk do support the login protocol it uses, EXT_STS and RST2 are the same thing however I think Ext_STS has the added support of registering the device to the Microsoft Passport Servers. In theory it should work however something is wrong in both implementations which makes the app crash. As far as I know I am probably the only group of people to deep dive into how authentication and how the device registers itself on the MSNP Servers (FYI its all gateway with polling that is also broken with crosstalk)
I have managed to get it working with a friend but it doesn’t do much other then login and send messages (Need to add SDG receive)
I’ve taken a look at the app too (not too in depth, i have other things in my life), I do know that at least on Crosstalk when you do login using RST2, it crashes due to an array being index of 9, instead of an index of 10, and I think I have the section where it happens, but IDA was fighting me & preventing me from confirming.
I also know the extSTS.srf was active till sometime after March 2025, since Microsoft login worked (:O, if only i didnt loose where I put my network dumps of that/didnt give up taking them since charles sux), but very interesting you got it to actually send a message (now don’t show that to the legacy children or you’ll never hear the end of it 
)
well in terms of their base schema, yes they’re both http://schemas.xmlsoap.org/ws/2005/02/trust.
In theory most RSTx requests should still work if you use an app password and the passport configurations for the domains are still valid (some aren’t, which causes login errors without filtering the request).
Most of the problems come to RST2’s incessant need on later versions of IDCRL to be encrypted, sure, it’s not a problem on IDCRL v4, but it is on v5+ (including 6.5, which is what we’re on now?).
It was during November 2025 They shut down all RST2 Logins using legacy IDCRL (eg WLM 2009, WLM for IOS etc)
Looks beautiful
I just got an iPhone 4S in today running iOS 6.1.3 that I’ll be using to testbed WLM iOS support, stay tuned
Thanks jimmy
Oops was meant to reply to Super Mario
(body min length why)
