Yup, Office Communicator is the messenger suited for the coporate envionment. It is just that I am required to reinvent the well for my project.
Thanks for your comment..
quote:
Originally posted by matty
Messenger also doesn't encrypt the video stream transmission and it is easily recordable. Such features would degrade the overall quality. IMO adding such encryption features, in regards to both Windows Live Messenger and Messenger Plus! Live, would bloat the software. Everyone already experiences delays due to the network transmission adding features that need to encrypt the data then decrypt it will cause "lag" so to speak.
From here on in; Windows Live Messenger will be referred to as WLM and Messenger Plus! Live will be referred to as Plus!.
WLM is not a service that should in any case be used within a corporate environment. There is very little control a Network Administrator has over the application as a hole. They cannot block the adding of external contacts which would mean data would have to be routed using an unencrypted network transmission protocol through the Microsoft Servers then to the external contacts ISP then to the contact themselves.
For instance Office Communicator 2007 is an internal service which relies on Active Directory and if I am not mistaken has the ability of allowing only domain accounts as contacts which means no external contacts can be added. Therefore encryption is not needed as everything transmitted is sent to a local server and routed accordingly.
I am not sure if this is where you were taking this thread but I thought I would add my two cents.
Note I have not setup Office Communicator yet therefore I am unsure if adding external clients is possible I would assume not.
