Ce que l’on peut encore dire : l’interface n’est pas intuitive, et la formation des utilisateurs pourrait s’av\u00e9rer corn\u00e9lienne. De plus, l’int\u00e9gration avec les PABX traditionnels semble reposer sur un terrain fertile aux mauvaises surprises… Mais qui dit identit\u00e9 num\u00e9rique unique, dit solution unique, en amont avec Exchange, Active Directory, etc., et d\u00e9sormais en aval\u2026 N’est-ce pas, Monsieur Microsoft ?<\/p>\n
L’outil repose sur un changement dynamique de codecs en fonction de la bande passante disponible, plut\u00f4t que sur la fiabilit\u00e9 du LAN\/WAN (VLAN, etc., notamment chez Cisco).<\/p>\n
Voici ce que pense Tom Keating<\/strong> (CTO, VP, fondateur de TMC Labs et journaliste pour Internet Telephony Magazine) \u00e0 propos de Microsoft Office Communicator<\/a> :<\/p>\n Lisez ses conclusions\u2026<\/strong><\/p>\n<\/blockquote>\n Bill Gates \u00e9voque la fin des PABX sur ChannelWeb<\/a>.<\/p>\n\n
\n Deploying OCS 2007 now takes the “crown” from Exchange Server as the most complex piece of Microsoft software to install. It requires installing more components than you can shake a stick at, including schema changes to Active Directory, installation of a Certificate Server & certificates, knowledge of regular expressions for dial plans, deployment of a Mediation Server for connecting to the PSTN, knowledge of VoIP and SIP configuration, and more.
\n <\/em><\/p>\n
\n That being said, Microsoft has abstracted a lot of the complexity of installing OCS 2007 using a very easy to use wizard that guides you through all of the steps. It’s a bit similar to the Exchange deployment wizard, but much more comprehensive. You still have to know what the heck you are doing though. This isn’t simply clicking Next, Next, Finish kind of wizard.
\n <\/em><\/p>\n