RTC? What the heck are people thinking? Here is another good example why no one should use RTC or LCS exclusively. MS are rumored once again of making noises about disrupting business for their own customers. No surprise here.
Why anyone would tie themselves down to RTC / LCS exclusively is beyond me. reSIProcate, SIMPLE and XCAP are already in-hand. There is no reason for this at all. If you are a customer and you are dealing with an RTC user base you should be looking for an endpoint that is more open standards minded and build some RTC functionality into that product. I can hardly believe I just said that but if you must deal with RTC and LCS then you should at the very least interop with other SIP, SIMPLE and XCAP end points and services. Every customer we have been working with, the biggest in the world, are all bailing out of RTC and LCS because of it’s severe limitations.
Xten will be providing demos of a new version of eyeBeam at VON with support for SIMPLE and XCAP in 2 weeks. The proof is in the pudding.
————————Excerpt————————-
Microsoft officials have described LCS 2005 as “a next-generation enterprise instant messaging (IM) and presence-awareness server.”
But Microsoft also will use LCS 2005 as a way to gain a toehold in the voice-over-IP (VOIP) space, according to sources claiming familiarity with the company’s plans.
“Microsoft’s end game is to become a telephony provider and give Vonage, Verizon, etc., a run for their money,” said one source close to the company, who requested anonymity. “They are going SIP (Session Initiation Protocol) in a big way. And because SIP is multi-media capable (start with voice, switch to video, conferencing, etc. in mid stream), it’s a nice protocol for them.”