That is pretty much what I gathered. I'm a lurker on this list for quite a few years.
It's going to take a couple of months for Office 365 to be put in place, so I'll explore this more when everything is ready to go. At the very least call forking so the desktop and Lync client ring at the same time should be possible. This would also make it work on mobile devices. I'll start a new thread on the dev list when I have the resources in place. Geoff Van Brunt From: [email protected] [mailto:[email protected]] On Behalf Of Tony Graziano Sent: Wednesday, July 25, 2012 4:11 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] FW: MS Lync and Exchange 2010 fyi - this has pretty much been discussed before, on-list and such a few times as I recall. Realize at the same time these are two "competing" products. How MS handles both their sip stack (which is tcp only I think) and how they handle authentication has changed several times (various ways in various SP levels of the "same" product). The better way to ensure interoperability would be to place a commercial SBC (which is known to work with Lync too) in bewteen. At least, I think that is the shortcut answer to get to the nirvana you might seek. Neither O365 nor Lync are exactly "open". Though I do understand why someone would want to do what you are attempting. Until someone has a working Lync server to test with against sipx AND provides details which will help either the devs or users craft a way to make them work (or determine it is still impractical), I'm not sure what can be accomplished. If there are issues with the certificate, it should be discussed. I think the users list is a great place to start that discussion and would look forward to it taking place. On Wed, Jul 25, 2012 at 4:11 PM, John Lightfoot <[email protected]> wrote: Hey Geoff, I have an O365 E3 account I've tried to setup UM against. Haven't really looked at the Lync but I assume if you have the telephony on Sipx, you might be able to dispense with Lync on premises and keep it all in the cloud. As for the UM, I'm trying with 4.6 and have been unable to negotiate a TLS session (require for Exchange online). The client cert is requested from the Sipx but isn't being properly provided in the handshake. I suppose an issue needs to be created for it. In any event, I'd be happy to email or talk off-list and pass on what I've learned (including some fun with Microsoft TAC). My email should be publicly visible. John Lightfoot _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
