Le Cloud de Christophe BOUCETTA (MVP Lync/Skype for Business, CCNP Voice, CCNP Collaboration)

Voici le blog sur les communications unifiées
    • 30/7/2010

    [Cisco CME] Nouvelle version CME 8.1

    La nouvelle release de la version Cisco CallManager Express 8 est prévu pour le 31 juillet 2010 et embarquera l'IOS 15.1.2(T).

    Les nouvelles fonctionnalités prévues:

          - Security Capabilities Improved toll-fraud prevention enhancements
          - Video Support for video telephony on Cisco® Unified IP Phone 6921, 6941, and 6961 endpoints
          - System Functions Localization enhancements with 4 new languages Latvian, Lithuanian,     Estonian, Arabic Localization
          - support for 7937 IP Phones Localization of mobility service

    • 28/7/2010

    [Office Communication Server 2007 R2] Live Communications Applications Module Error code: C3E83201 (SIPPROXY_E_SHUTDOWN_REQUESTED)

    Aie, encore un problème...

    Cela vient de la présence de la KB 967831 sans que MSMQ soit présent sur le serveur.  Consultez cette page pour plus d'infos:

    http://blog.tiensivu.com/aaron/archives/1867-RtcQmsAgent-fails-to-start-on-OCS-2007-R2-server-and-causes-KB-967831-April-2009-update-for- Front-End-Server-composants-install-à-fail.html

    • 28/7/2010

    [Office Communication Server 2007 R2] The component Live Communications User Services reported a critical error: code C3EE78F8

    Event ID: 30968
    Source: Live Communications User Services
    Details: The component Live Communications User Services reported a critical error: code C3EE78F8 (Enterprise Edition Server successfully registered with the back-end, but a stored procedure version mismatch was detected. The service will not start until this problem is resolved. Cause: The database schema and the Enterprise Edition Server were updated by different installation packages. Resolution: Ensure both the Enterprise Edition Server and back-end were installed or modified by the same installation package. The service has to stop.

    Voilà ce qui se passe lorsque l'on installe les dernieres mises a jour sur un serveur avant que l'importante mise a jour http://support.microsoft.com/kb/969834 ne soit présente. Donc petit coup de stress, le service front-end ne voulant plus démarrer!

    Pas de panique, il faut installer OCS2009-DBUpgrade.msi, relancer le serveur et le service est up!

    Ce n'est pas mentionné dans la release notes de la derniere cumulative update mais il est indispensable que cette uptdate soit passé avant.

    • 28/7/2010

    [Office Communication Server 2007 R2] communicator cannot synchronize address book because the corporate address book file appears to be damaged

    Nouveau petit problème aujourd'hui,impossible de recuperer le carnet d'adresse d'entreprise, et une fenetre d'authentification s'ouvre en permanence :

     

    La solution a etait de mettre les mises a jours des clients communicator et du serveur frontal au même niveau.

    Mises a jour :http://microsofttouch.fr/blogs/christophe/archive/2010/04/26/mise-224-jour-office-communications-server-2007-r2.aspx

    Supprimer la galcontacts :

    Vista,W7
    %userprofile%\AppData\Local\Microsoft\Communicator\sip_user@domain.com\galcontacts.db
    XP
    %userprofile%\Local Settings\Application Data\Local\Microsoft\Communicator\sip_user@domain.com\galcontacts.db

     

    • 20/7/2010

    [Cisco] QM FSM Error

    Et oui, je ne fais pas que de la Communication Unifiée Microsoft, j'interviens aussi bcp sur des projets réseaux et voip cisco entre deux projets :) (bientot aussi sur la partie communication unifiée Cisco).

    Aujourdhui, création d'un vpn pour un client entre un site francais (asa) et un site américain (sonicwall), l'erreur suivante suite a sa création apparait en boucle :

    Il s'averait que le PFS (perfect forward secrecy) était activé sur l'autre élément!


    Voici une configuration vpn de base pour un pix ou asa :

    PHASE1
    crypto isakmp policy 1
    authentication pre-share
    encryption 3des
    hash sha
    group 2
    lifetime 86400

    tunnel-group x.x.x.x type ipsec-l2l
    tunnel-group x.x.x.x ipsec-attributes
    pre-shared-key *hidden*

    PHASE2
    crypto map vpn match address partner
    crypto map vpn set pfs
    crypto map vpn set peer x.x.x.x
    crypto map vpn set transform-set ESP-3DES-SHA
    crypto map vpn set security-association lifetime seconds 3600

    Encryption Network:
    access-list partner extended permit ip 192.168.10.1 255.255.255.0 192.168.20.0 255.255.255.0

    • 7/7/2010

    Webcast Microsoft Communication Server 14

    Voici toute une série de webcast tres intéressant sur la nouvelle version Microsoft Communication Server 14 :

    UNC311 CS “14”: Architecture

    UNC312 CS “14”: Network Considerations

    UNC313 CS “14”: Voice Architecture and Planning for High Availability

    UNC314 CS “14”: Voice Deployment

    UNC315 CS “14”: Setup and Deployment

    UNC316 CS “14”: Monitoring and Reporting

    UNC317 CS “14”: Management Experience

    UNC318 CS “14”: What’s New in Conferencing Experience & Backend

    UNC320 CS “14”: What’s New in Communicator “14” Experience & Backend

    UNC321 CS “14”: Interoperability: Voice, Video, Conferencing, IM, & Presence

    UNC208 CS “14”: What’s New in Devices

    • 7/7/2010

    Integration Cisco Call Manager avec Exchange 2010

    Les notes de configurations Microsoft d'une intégration en direct Sip entre un Cisco Call Manager 7 et Exchange 2010 sont disponibles en téléchargement :

    http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=d5db0297-7850-4f52-b965-b8006b4c05f5&displayLang=en

    Il n'y a pas de grosse différence avec les configurations d'intégrations ultérieur vu que j'avais validé cette partie il y a quelque temps quand même, mais c'est une documentation très instructive.

     

    • 5/7/2010

    Survivable Appliance Branch avec une Dialogic DMG 4000 et Microsoft Communication Server "14"

    La fonctionnalité de sba (survivable Appliance Branch) est tres attendu avec la nouvelle release de Microsoft Communication Server "14" qui est comparable au srst Cisco, la question du lien Wan qui tombe avec un repli de secours PSTN étant une question qui revient très souvent lors d'une proposition d'infrastructure voix OCS.

    Pour les passerelles dmg 4000 déjà en place avec une architecture ocs 2007 R2, un simple upgrade logiciel active les fonctionnalités de passerelles SBA et installe le server SBA.

    Here is a summary of the advantages of using DMG4000 Gateways as SBAs:
    • Broad, scalable hybrid gateway product line
    • Proven support for Microsoft UC
    • Field software upgradeable to operate as an SBA (availability expected Q4 2010)
    • Flexible, cost-effective support for analog devices (availability expected in 2010)
    • PBX, PSTN, IP, and fax protocol support
    • Exceeds security requirements for audio transcoding and SIP signaling
    • Robust Windows Server 2008 platform
    • Centralized management system (availability expected in 2010)
    • Global sales and support network (over 40 locations)

     

    • 2/7/2010

    Communicator File Transfers Across a Firewall Not Supported

    Une bonne nouvelle, le transfert de fichier entre un utilisateur distant connecté a travers un serveur Edge (donc hors cas vpn) avec un utilisateur local ou distant sera supporté avec Microsoft Communication Server 14.

     

    • 2/7/2010

    Nouveautés de Microsoft Communications Server 14

    Summary:

    • The live meeting conferencing functionality will be rolled into Communicator “14″.  There will be one client, Communicator, for all media modalities and the associated features.
    • There will be a new Silverlight-based web client available for those users wanting to joing a web conference, but don’t have the rich Communicator client installed.  This is a new client and not a replacement for Communicator Web Access.
      • When a user clicks to join a meeting from a link, it detects whether the Communicator client is installed. If it is not, you can join via the Silverlight client.
      • Participation via the Silverlight client is anonymous (i.e there is no sign-in required).  This is a powerfull feature that will make it a whole lot easier for external (to your organization) attendees join a meeting.
    • MCS 14 will federate with Windows Live “Wave 4″ and will support Audio and Video with Windows Live Messenger contacts.
    • All MCS 14 features were designed ground-up to work on-premise, cloud, or hybrid:
      • both in terms of supporting a percentage of MCS users on-premise, in the cloud, and,
      • in terms of having some or all Exchange & SharePoint services in the cloud
    • Supported virtualization for all server roles in MCS 14 (with the normal audio and video caveats;  i.e. you must closely follow the virtualization guidelines to support audio and video, and even then it could be more suceptible to jitter and latency)
    • The MCS 14 will support a media bypass feature which will allow a consolidated MCS “14″ front-end server to go direct SIP to a supported IP-PBX’s without having to through a mediation server when the call is going to a locally dialed PSTN number.
      • the Media by-pass, coupled with the branch office survivability will remove the need for Mediation servers in most local or branch sites (in most cases)
    • Multiple SIP Gateways can be connected to one Mediation server.
    • Communicator “14″ will support the G.711 codec and will be able to talk to certified MCS “14″ media Gateways to go out local PSTN access points.
    • The visual Presence circle is changing to a square in Communicator “14″!  :-)

    Office Communicator “14″

    Management

    • A new Silverlight web-based management console (Communication Server Control Panel) that is built on a new set of Communications Server PowerShell cmdlets.
      • Support for Role Based Access Control administration (similar to Exchange 2010)
      • Support for cut-and-paste in the UI (i.e. easily copy Normalization Rules)
      • Can easily see all the Policies (i.e. Voice, Conferencing, Client) for a particular user in one place
    • A new Central Management Store (CMS)
      • a central database the holds XML documents that describe your deployment
      • all topology changes get written to the CMS, and a read-only copy is pushed to all servers in the topology
      • the topology is pushed out via a file transfer agent and via HTTPS for the the Edge role
    • New tools to help with certificates!
    • New support for ’server maintenance’ – a server can be put into maintenance mode for O/S and hardware maintenance
    • New PowerShell cmdlet’s
      • Everything in the new UI can be done through PowerShell
      • Cmdlets to manage users, configuration, devices, policies
      • Support for synthetic transactions (test phone calls, sip registrations, simple conferencing)

    Topology Changes

    • More support for role collocation.  More roles, including the Mediation role and CWA, can be installed with the Front-End
    • A new “Site” topology entity which can be used to represent a geographic boundary such as a center or branch location.  A site contains one or more pools
    • Similar roles as OCS 2007 R2 (i.e. a backend role that defines a pool, Edge Mediation, AV Conferencing, Archiving, Monitoring, Director, Group Chat)
    • The Director role now streamlined and includes a local SQL Express database – removing the need for a separate back-end SQL database.
    • The concept of Standard and Enterprise edition still exists
    • Support for DNS load balancing within a pool
    • New Topology Builder UI which helps you build your topology document

    Virtualization

    • Support for the virtualization of almost all roles
    • Client virtualization support is similar to Communicator 2007 R2 (i.e. IM and application sharing but audio/video is not supported)
    • Cannot virtualize the new branch office workload

    Monitoring

    • New SCOM 2007 R2 management pack:
      • Support for synthetic transactions (monitor the user experience)
      • Media quality alerts
      • Call failure alerts
      • Actionable alerts
    • Monitoring role can be collocated with the front-end role
    • The ability to ‘heal’ the audio of a particular end-point if the Monitoring role detects degradation in quality.

    Office Communications Online

    • Second-half of 2010:
      • Peer-to-Peer Audio/Video and File Transfer across the firewall
      • Communicator Mobile
    • First-half of 2011:
      • Federation and PIC
      • IM Archiving
      • Recording and Playback
      • Application Sharing
      • Unified Voicemail
      • ACP Integration