Hey Tom, thanks for setting this up! The beta of the collectivesoftware SIP filter will be released VERY shortly (emails going out to the first round of customers interested as soon as tomorrow!).
It is focused on not only providing an additional layer of security to the SIP communications, but even more importantly allowing secure P2P communications between your LCS clients. First it must fix up references to internal IPs that can propogate in the SIP traffic. Second it will allow you to establish secure P2P connections for File transfers, app sharing and Audio/Video without having to open up tons of ports on your firewall (it can dynamically open the connection for the right clients for that session only) and map the connection to the proper internal clients even with NAT in place!
The first version of LCS-Bridge is very much focused on the needs of corporate customers (small and large) that have implemented LCS and are using SIP enabled clients (Windows Messenger and Office Communicator). How LCS and SIP work are very different than the public clouds and we recommend that customers that are concerned about security and compliance deploy LCS and federate with the public clouds.
For those customers that are interested in supporting certain features of the public messenger clients (such as MSN messenger) - we are interested in feedback at www.collectivesoftware.com since customer demand ultimately drives features and products! Customers interested in participating in the private beta should contact email@example.com
From: San Rafael, CA
Know if they are going to support soft phones? I'm about ready to go into limited production release of a website with a softphone imbedded in the page. It'd be really great to be able to use my own product behind our ISA 2004 firewall.
I remember looking at LCS-bridge when this discussion went up, at the time of looking our business need for it went away, so we didn't buy it, however we now have a need for it, but the collectivesoftware.com site doesn't show the product any longer.
Has it been pulled, or replaced? If its not longer available, does anyone know of another product that allows external Office Comminicator clients to connect to an internal LCS server?
ORIGINAL: bjblackmore Has it been pulled, or replaced? If its not longer available, does anyone know of another product that allows external Office Comminicator clients to connect to an internal LCS server?
LCS-bridge was retired. It is a very limited filter that only is useful when ISA is the edge firewall (very rare, unfortunately), and only works with LCS. Most customers wanted to use it with their VoIP phones or SIP trunk, or to somehow make SIP work across some other firewall when ISA was not at the edge. Support became a nightmare and the product didn't sell well enough to maintain.
Now: If you can't get connected to your server at all, it sounds like there's a problem with your publishing rule. The bridge filter wouldn't have solved that problem; it is used to enable media connections across the firewall. The basic logon to LCS, presence awareness, and chatting should all work fine if you have your server published through ISA properly.
Microsoft has a SIP filter in their upcoming TMG. This may be helpful as well.
Oh right, so external Live Comms clients CAN connect through ISA 2006? I was under the impression that was what Communicator Web Access was for, and I though LCS-bridge was the filter that allowed Communicator clients to connect through. If chat/presence & file transfer work through ISA 2006 anyway, then that great, we don't really use video or VoIP with LCS yet. Is there an article on how to publish an LCS server through ISA?