Publication aujourd'hui dans le blog technet: Étape par étape : Configuration d’Office Online Server avec Skype for Business 2015

En FR: https://blogs.technet.microsoft.com/canitpro/2016/06/16/tape-par-tape-configuration-doffice-online-server-avec-skype-for-business-2015/

En EN: https://blogs.technet.microsoft.com/canitpro/2016/06/16/step-by-step-configuring-office-online-server-with-skype-for-business-2015/

CUCM 11.5 est disponible depuis quelques jours au téléchargement depuis un CCO,

La release notes de la version 11.5 pour CUCM et IM & Presence est disponible ici: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/cucm_b_release-notes-cucm-imp-1151.html

Points a prendre en considération:

Deprecated Phone Models:

As of Cisco Unified Communications Manager Firmware Release 11.5, the following phones are not supported:

•     Cisco IP Phone 12 SP+ and related models
•     Cisco IP Phone 30 VIP and related models
•     Cisco Unified IP Phone 7902
•     Cisco Unified IP Phone 7905
•     Cisco Unified IP Phone 7910
•     Cisco Unified IP Phone 7910SW
•     Cisco Unified IP Phone 7912
•     Cisco Unified Wireless IP Phone 7920
•     Cisco Unified IP Conference Station 7935

If you use any of these phone models on an older release of Cisco Unified Communications Manager and you upgrade to Release 11.5, the phone will not work after the upgrade completes.

IM and Presence Service Interoperability with Expressway-C

To interoperate Cisco Unified IM and Presence Service Release 11.5(1) and Expressway-C, you must be running a minimum version of Expressway-C X8.8. IM and Presence Service 11.5(1) does not support earlier versions of Expressway-C.

If you are upgrading from an earlier release where you are already interoperating with Expressway-C, upgrade your Expressway-C system to X8.8. After upgrading Expressway-C, you can upgrade your IM and Presence Service.

Cisco IP Phone 7800 and 8800 Series Features

The phone Firmware Release 11.5 is not embedded in the Cisco Unified Communications Manager Release 11.5. The phone firmware needs to be downloaded from Cisco.com and installed separately.

Remote Call Control using Upgraded Skype for Business Clients

With this release, the Remote Call Control feature of IM and Presence Service supports Skype for Business 2015 clients that were upgraded from Lync 2013 clients, and which are registered to a Lync 2013 server. With this feature, users can use the upgraded Skype for Business client to control their Cisco Unified IP Phone.

The Skype for Business 2015 client must have been upgraded from a Lync 2013 client, and must be registered to a Lync 2013 server

Le calendrier des Microsoft Ignite 2016 a Atlanta est disponible.

Information et inscription possible ici: https://ignite.microsoft.com/#fbid=JY100P1tTD5

39 sessions dédiées a Skype for Business seront offertes: https://myignite.microsoft.com/sessions?q=skype&f=%5B%7B%22name%22:%22Skype%20for%20Business%22,%22facetName%22:%22products%22%7D%5D

Contexte:

Migration d'un environnement Lync 2013 vers Skype for Business en mode HA et DR.

Problème:

Lors de la migration des utilisateurs vers le nouvel environnement HA et DR avec la commande move-csuser, le warning suivant en fin d'opération est visible:

L'event suivant est visible pour un utilisateur sur les serveurs Skype for Business:

Résolution:

https://support.microsoft.com/en-us/kb/3070789

Les étapes:

• Télécharger l'application Skype for Business Server 2015, Post Move Cleanup Tool
• Ouvrir une fenêtre command promp avec des privilèges élevés
• Lancer la commande PostMoveCleanup.exe -SummaryFile <Path of summary file> [-MachineFqdn <Fqdn of server>] [-LogFile <Path of log file>]

Notes:

• You must provide to the tool the summary file that is generated by the Move-CsUser cmdlet.
• The -MachineFqdn parameter refers to the fully qualified domain name (FQDN) of the server that the tool is connected to for cleanup of the local database. This parameter is optional. If it is not specified, it points to the local server on which the tool is running.
• The -LogFile parameter refers the path of the file that the tool writes logs to. The tool will append logs to the file if the file exists. This parameter is optional. If it is not specified, the tool creates a new log file.
• There may be more than one summary file in the same folder that is generated by multiple uses of the Move-CsUser cmdlet. Make sure that the correct summary file is provided. You can find the summary file path in the Move-CsUser cmdlet output.
  
  For example, results from this operation can be found in the following path:
  
  C:\Users\administrator\AppData\Local\Temp\2\MoveResults-986d45c2-0035-485c-9cf7-f753380cf281.csv

Microsoft a publié une mise a jour pour le client Skype for Business 2016.

Source: https://support.microsoft.com/en-us/kb/3115087

Numéro de version: 16.0.4393.1002

Date: 7 juin 2016

Corrections:

• 3169044 Skype for Business 2016 freezes when you are in a desktop sharing process
• 3166231 Skype for Business 2016 crashes when you try to open the contact card of a consumer user
• 3166230 Missing notifications of missed calls when Exchange UM isn't enable in Skype for Business 2016
• 3166228 Skype for Business 2016 crashes during call transfer
• 3159724 Skype for Business 2016 freezes or crashes when you start a desktop sharing
• 3159723 Skype for Business 2016 freezes when you switch the language from English to Thai if MAPI profile is set

Téléchargement:

• Download the 32-bit Lync update package now.
• Download the 64-bit Lync update package now.

Prérequis:

Il est nécessaire d'avoir déja installé la mise a jour suivante:

December 8, 2015, security update (KB3114372) for Skype for Business 2016.

Erreur:

Pendant l'installation de RTMT sur un windows 10: " installer user interface mode not supported"

Correction: exécuter le programme en mode compatibilité Windows 7

Cela fonctionne maintenant:

Procédure d'installation RTMT ici: http://microsofttouch.fr/default/b/christophe/archive/2015/08/29/cisco-uc-installer-rtmt

Annoncé dans le blog office, la capacité de préchargement des pièces jointes d'une réunion Skype for Business directemetn dans l'invitation fais partie des mises a jour du moi de mai.

Description:

Pre-populated attachments in Skype Meetings—Files you attach to a Skype Meeting request in Outlook 2016 or Outlook on the web now automatically load into the Skype Meeting document bin as soon as participants join. Cloud attachments automatically assign permissions to meeting attendees. That way everybody can collaborate during the Skype Meeting

Lien annonce: https://blogs.office.com/2016/05/25/new-to-office-365-in-may-skype-for-business-chat-integration-in-the-web-updates-to-outlook-and-more/

Notes: Don't see this feature in your Skype for Business client yet? Stay tuned. It will be rolling out to you in an upcoming Office 365 update.

Simple, il suffit de rajouter une pièce jointe durant la phase de création de la conférence dans Outlook.

Faire insérer - joindre un ficher:

Lorsque les participants rejoignent la conférence, les pièces jointes sont accessibles et disponibles immédiatement:

Informations disponibles ici: https://support.office.com/en-gb/article/Preload-attachments-for-a-Skype-for-Business-meeting-fd3d9f9d-b448-4754-b813-02e49393f251?ui=en-US

Microsoft a publié un article intéressant "Media Quality and Network Connectivity Performance in Skype for Business Online"

Description:

This topic defines the set of network performance requirements for Skype for Business Online services and how you can choose to use the Internet or ExpressRoute for connectivity between your network and Skype for Business Online based your assessment of the network connectivity. If you have decided to deploy Azure ExpressRoute for dedicated connectivity to Office 365, this document also provides guidance on how to plan your ExpressRoute connections in different Skype for Business Online deployment scenarios.

Lien: https://support.office.com/en-us/article/Media-Quality-and-Network-Connectivity-Performance-in-Skype-for-Business-Online-5fe3e01b-34cf-44e0-b897-b0b2a83f0917?ui=en-US&rs=en-US&ad=US

Microsoft vient de publier un KB concernant le problème suivant:

Conferencing modalities no longer function in Lync Server 2010, Lync Server 2013, or Skype for Business Server 2015 after you install Security Bulletin MS16-065

Les fonctionnalités impactées:

• Whiteboards
• Uploading PowerPoint Presentations
• Sharing Notes
• Polls
• Q&A

Les messages d'erreurs:

• We can’t connect to the server for presenting right now.
• Network issues are keeping you from sharing notes and presenting whiteboards, polls and uploaded Pow…
• An error occurred during the Skype Meeting.

KB: 3165438

Lien: https://support.microsoft.com/en-us/kb/3165438

Cela tombe bien pour moi, dans un nouveau projet, j'ai exactement vécu ce probleme cette semaine.

Dans une conférence, les fonctionnalités comme le sondage ou le tableau blanc affiche un message d'erreur lors des tests d'utilisations:

A ce stade, suivant le KB, la résolution est la suivante:

1/ Localiser le répertoire d'installation de DATAMCUSVC.exe sur votre serveur

Par défaut:

2/ Ajouter une clé de registre

Dans l'emplacement:

HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\v4.0.30319\System.Net.ServicePointManager.SchSendAuxRecord

Dans mon cas, j'ai du créer moi la sous clé "System.Net.ServicePointManager.SchSendAuxRecord"

Créer le DWORD suivant:

DWORD Name: C:\Program Files\Skype for Business Server 2015\Web Conferencing\DATAMCUSVC.exe
DWORD Value: 0

3/ Rédemarrer le service Skype for Business Server Web Conferencing service (RTCDATAMCU)

4/ Depuis votre client lync/skype, déconnectez et reconnectez vous

Le test fonctionne maintenant:

Microsoft a rendu disponible les outils du kit de ressource pour Skype for Business Server 2015.

KB Articles: KB2905053

Téléchargement: https://www.microsoft.com/en-us/download/details.aspx?id=52631&WT.mc_id=rss_office_servicepacks&tduid=%2882818df84421b40df4a2960d0b5cd4a5%29%28266696%29%281503186%29%28skim725X175X0f4e51516011077306ddc7e5a33887b6

Description:

The Microsoft Skype for business Server 2015 Resource Kit Tools contain the following tools. The details of each tool and their usage are described in the accompanying documentation.

• ABSConfig
• Audio Extractor
• Bandwidth Policy Service Monitor
• Bandwidth Utilization Analyzer
• Call Parkometer
• Cleanup Storage Service Data
• DBAnalyze
• Import Storage Service Data
• LCSSync
• Lookup User Console
• MsTurnPing
• Network Configuration Viewer
• Response Group Agent Live
• SEFAUtil
• Unassigned Number Announcements Migration
• Watson Support Tool for Lync Phone Edition
• Web Conf Data

Microsoft a publié une mise a jour de l'interface SDN, la derniere version est donc maintenant la 2.4.1.

Téléchargement: https://www.microsoft.com/en-us/download/confirmation.aspx?id=51195

Description des nouvelles fonctionnalités:

• Powershell interface for provisioning: Windows Start Menu contains a Powershell shell that allows execution of provisioning commands similar to the command line provisioning interface. In addition, a SubscriberStatus and Status API has been added to allow querying some basic statistics for the overall service and each subscriber. See section on Powershell Provisioning for details.
• Per Subscriber PII Obfuscation: You can now set an obfuscation seed for each subscriber ensuring that the feed provided contains unique identifiers representing your SIP aliases and telephone numbers. See section on Per Subscriber Obfuscation for details.
• Schema Preview: Some new requested fields have been added to Schema D. This might break backward compatibility with some receivers and therefore requires a specific activation using a hidden schemapreview setting. These fields will be included in the next major schema revision. We have added QualityUpdate and IncallQuality messages containing Subnet, TenantId (online only) and, if traceroute is active in SfB, an attribute will give the round-trip time (RTT) for every hop. The latest provided schema definition (SDNInterface.Schema.D.xsd) allows for these new fields optionally.Note: This is NOT a supported feature but a preview for a schema change targeted in our next 3.0 release. See section on Schema Preview for details.
• Auditing: EventLog will receive entries for changes to any SDN Manager or Dialog Listener settings as a result of provisioning activities. Eventlogs will also contain warnings 90 days before a (client) certificate being used is due to expire.
• 0 values: In previous releases, fields containing 0 were ignored, but this release now provides fields containing 0 if 0 is a valid value and if provided by the clients. This allows better differentiation on whether a field was provided at all or not.
• Activation of InCallQoE: Installing DialogListener on Skype for Business 2016 Server will automatically activate sending InCallQoE reports from all W16 clients. For testing and development, you can also activate InCallQoE in W16 clients if the server is an older version by adding the control files (see Configuring InCallQoE Messages). For details about how to restrict the number of InCallQoE messages, see In-call QoE algorithm and throttling.
• Redis: This version consists of an upgraded Redis client.
• Identifier and settings names are now case insensitive for backward compatibility.

Corrections bugs:

• Security fix: If Redis is used with a password, the password now won’t be logged into theSDNManager logs.
• Fixed issue when SDN Manager has schema C and schema D subscribers provisioned at the sametime.
• Connection field "wired" will now consistently be "Ethernet".
• Traceroute hops won’t be mirrored anymore in IncallQuality messages because the route from one endpoint is not necessarily the reverse of the other, as a given route may just be a partial route.
• Security fix: When obfuscation is enabled (hidepii=true) in some cases PAI was not being obfuscated. This has been addressed.
• ConferenceID field would sometimes not be populated. This has been fixed.
• Fixed some race conditions around saving settings state that prevented settings from beingupdated correctly in an SDNManager pool.
• Removed inconsequential errors reported in the logs.
• Specific to SfB Online, filtering by TenantID and reporting was not handled correctly and hence wasnot being presented in InCallQoE messages. This has been addressed but needs to be enabled with the schema preview config. See section on Schema Preview for details.
• Addressed an issue where Schema validation errors may cause messages to be dropped.
• Schema validation has been disabled on the Dialog Listener, based on which Dialog Listener needs to be upgraded.
• In 2.4.1 and earlier versions, the API occasionally failed to associate endpoints from a previous message to a current message. This resulted in either applying the  UserAgent and Contact headers from an incorrect endpoint or dropping the current message, whenever the expected endpoint was not found. The resulting error is ‘Writing to datastore failed after multiple retries’. This issue has been addressed in 2.4.1.
• Addressed an issue with the Dialog Listener MSPL script, which in certain situations may affect the processing of messages on the Front End.
• Enhanced Redis connection handling to prevent Redis connection errors specifically to lua script, added more logging and improved connectability of the SDN Managers with the Redis datastore.
• Schema D now mentions which fields are obsolete.
• Protocol options namely TCP-ACT and TCP-PASS are not being sent to the receiver. Only protocol option TCP will be sent for active and passive sessions

Notes et problèmes connus:

• Support for Lync 2010 is now deprecated.
• After installing version 2.4.1 in an active deployment, there may be some errors reported in the logs and reports lost for some calls due to a change in how QoE reports are kept in the data store. Only reports for events during the time of the upgrade may be affected.
• InCallQoE is referred to as InCallQoS in the SfB front-end Powershell configuration, which can be misleading.
• Due to some changes to how we store state for calls, during an upgrade, some failures may be reported for ongoing calls during the upgrade.
• For an unattended install of SdnManager, it is required to specify the LOGPATH parameter to set the log directory.
• For an unattended install of SdnManager, it is required to specify all the parameters including LOGPATH.
• The AllData.log generated by the DialogListeners has some fields missing (e.g. VIA and REPLACES) hence using these logs for replay by the DialogListener is unreliable. As an alternative, use SIP logs generated by SfB or ALLManagerInput.log generated by the SDN Manager.

Belle nouvelle, Audiocodes propose une solution globale embarquant dans le meme chassis Mediant SBC ou traditionnel l'infrastructure Skype for Business Cloud Connector Edition.

Descriptions:

The AudioCodes Mediant 800 CCE Appliance bundles our proven Session Border Controllers (SBC) and Gateways with the Skype for Business Cloud Connector Edition into an elegantly packaged 1U chassis that is easy to deploy and manage.

For organizations, or enterprise branches with typically up to 1000 users the AudioCodes Mediant 800 with the Open Solution Network (OSN) Server can host the Cloud Connector on the same self-contained appliance with up to 185 sessions.

Spécifications:

Si vous utilisez Skype for Business pour Mac en Preview et constater quelques irritants avec le client, la liste des problemes connus est disponible ici: https://support.office.com/en-us/article/Known-Issues-Skype-for-Business-for-Mac-Preview-494ac5d5-50be-4aa7-8f5a-669c71c98c9a?ui=en-US&rs=en-US&ad=US&fromAR=1

Un nouveau modèle de téléphone Audiocodes devrait faire son apparition sur le marché d'ici cet été certifié Skype for Business, le AudioCodes 450HD.

Description:

The 450HD IP Phone is a high end, executive IP phone, built with a large 5’’ touch main color display, integrated BT and optional connectivity to color touch screen expansion modules.

Fonctionnalités:

• Large 5’’ Color TFT main screen (800 X 480) with multi lingual support
• Touch oriented user interface allowing up to 8 programmable keys and soft keys
• Up to 3 concatenated expansion modules, with 5’’ Color TFT screen (480 X 854)
• Full duplex speakerphone and headset connectivity
• Integrated BT for wireless headset connectivity
• 8 lines
• GbE Support
• USB Headset support
• PoE or external power supply

Spécifications physiques:

Unit Dimension (WxDxH): 234 x 190 x 170/195 mm (9.21 x 7.48 x 6.69/7.67 in.)

Unit Weight: 1.284Kg (2.83 lb)

Beaucoup de nouveautés a venir du côté des téléphones Audiocodes, a suivre

AudioCodes a publié une mise a jour concernant son interface de gestion - 1.1.12.84 - pour sa gamme de produits Mediant Survivable Branch Appliance (SBA).

Cette version offre les améliorations suivantes:

Support ProConnect : Avec cette version, l'interface de gestion SBA informe le serveur ProConnect si la nouvelle image a été installé avec succès ou non
Un seul fichier d'installation (exe) pour les deux versions Mediant 800 et Mediant 1000

Notice accessible ici: http://www.audiocodes.com/loginpage?fileId=7208217

Cisco a rendu disponible publiquement lors de ce mois d'Avril 2016 la version 11.5 de Cisco Prime Collaboration Deployment

J'ai déja partagé par le passé 3 blogs sur cette solution applicative Cisco PCD:

Installation:

http://microsofttouch.fr/default/b/christophe/archive/2014/06/09/cisco-installation-cisco-prime-collaboration-deployment

Migration:

http://microsofttouch.fr/default/b/christophe/archive/2014/07/14/cisco-migration-cucm-avec-cisco-prime-collaboration-deployment

Sftp:

http://microsofttouch.fr/default/b/christophe/archive/2015/01/13/cisco-sftp-cisco-prime-collaboration-deployment

Cisco PCD est une application conçue pour aider à la gestion des applications de communications unifiées. Il permet d'effectuer des tâches telles que la migration des anciennes versions applicatives vers de nouvelles machines virtuelles, planifier des nouvelles installations ou encore effectuer la mises à niveau de clusters existants.

Les nouveautés sont listés dans la release notes accessible ici: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/PCD/11_0_1/CUCM_BK_P10B55E7_00_pcd-rns-1151/CUCM_BK_P10B55E7_00_pcd-rns-1151_chapter_01.html

Tâches supportées dans cette nouvelle release:

Microsoft a rendu disponible au publique la version 1.1 de Real-Time Statistics Manager (StatsMan).

Téléchargement ici: https://www.microsoft.com/en-us/download/details.aspx?id=49491

Les nouveautés:

• A new scenario feature has been added to create a more data centric view into what is happening with your environment. For example, the Pool Failover scenario (shown on the right) allows relevant failover statistics for two pools to be viewed side by side for easy comparison.  The table values update in real time, and any cell in the table can be added to the chart to see history for that counter.
• Improved event logging is now in place for the Listener and Agent services, allowing easier troubleshooting of your StatsMan deployment.  Detailed troubleshooting information can also be found on TechNet: https://technet.microsoft.com/en-us/library/mt703767.aspx

Full StatsMan 1.1 Changelog

• Features:
• Scenario views have been added for Edge Media, Fabric Health, Pool Failover and Registration scenarios.
• Command line PerfAgentStorageManager.exe (installed with the Listener) can now export counter data as a CSV.
• Many new additional counters added for SQL servers, Windows Fabric, and S4B usage counters, etc.
• Watcher node integration for the StatsMan Agent – if the Agent is installed on a watcher node, it will report synthetic transaction statistics as counters back to StatsMan.

Bug fixes:

• UI/Server/Agent - Numerous significant reliability / performance improvements
• UI - Main filter control now sorts correctly with different cases (was leading people to think certain servers weren’t in the system when they were):
• Server - Server components will now install on non-English servers.
• Server/Agent - In some cases, agent and server components would not install with .NET errors due to a specific version of .NET 4.0.  This has been resolved.
• Agent – Extended event logging added for the StatsMan Agent.  The agent will no longer crash when installed on a server not in the topology, this will now be logged in the event log, along with many other possible error conditions.

Microsoft vient de publier une série de mise a jour pour Lync Serveur 2010.

Téléchargement ici: https://www.microsoft.com/en-us/download/details.aspx?id=11551 

KB2493736: https://support.microsoft.com/en-us/kb/2493736

Mise a jour: KB 3148805 April 2016 cumulative update 4.0.7577.726 for Lync Server 2010, core components

Corrections (pas vraiment d'informations..):

This article describes a cumulative update that improves the reliability, stability, and performance of Microsoft Lync Server 2010 core components.

Mise a jour: KB 3148802 April 2016 cumulative update 4.0.7577.726 for Lync Server 2010, Web Components Server

Corrections:

• KB 3155593 Can't join an online meeting in a local client through Google Chrome in Lync Server 2010
• KB 3155850 Cross-site scripting (XSS) vulnerability through User-Agent header in Lync Server 2010
• KB 3126487 You can't join a meeting from outside Lync 2013, Lync 2010, or Skype for Business on iOS 9.2 and later
• KB 3097592 You can't join a meeting from outside Lync 2013, Lync 2010, or Skype for Business on iOS 9 or 9.1

Mise a jour: KB 3148801 April 2016 Cumulative update 4.0.7577.726 for Lync Server 2010

Corrections:

The cumulative update fixes an issue that triggers elevated CPU usage for the Rtcsrv.exe process on a Lync Server 2010 front-end server.

Petite erreur du jour lors d'une migration Lync Server 2013 vers Online lors de la tentative d'ouverture d'un powershell remote a Skype for Business Online:

Get-CsPowerShellEndpoint : Unable to query AutoDiscover URL..

Correction:

KB: 2909536

Lien: https://support.microsoft.com/en-us/kb/2909536

Administrators who have a Lync hybrid deployment may receive the following error message when they try to connect to Skype for Business Online (formerly Lync Online) Remote PowerShell: 

$cssession = New-CsOnlineSession –Credentials $cred –OverrideAdminDomain "contoso.onmicrosoft.com"

Cisco Cloud Collaboration Meeting Rooms (CMR)  permet de lancer ou rejoindre une réunion WebEx programmée ou instantanée, depuis n’importe quel navigateur ou système et application de visioconférence standard.

CMR support Lync et Skype for Business que ce soit pour des organisations ayant une infrastructure Microsoft on premise ou cloud, tout en étant capable de délivrer un partage de contenu dans les deux sens.

Fonctionnalités supporté dans CMR pour Lync/Skype:

- Audio: G.722
- Vidéo: H.263 (CIF) ou H.264 UC (720p/30)
    CMR Cloud converts H.264 SVC to H.264 AVC
- Content: 2-way contecnt sharing:
    To Lync/Skype: CMR Cloud encodes content in main video - composite layout
    From Lync/Skype: Microsfot's RDP to BFCF interoperability - in the content channel
- In-Meeting features: Participant list not available
- Own the session: Lync/Skype can start/host the CMR Cloud session

Les versions Lync/Skype supportées:

Flow avec environnement on-premise:

Flow avec environnement dans O365:

Pour rejoindre un meeting hebergé par CMR, un URI spécifique est nécessaire pour le client Lync/Skype:

Microsoft a rendu disponible cette semaine au téléchargement.

Avec le cloud PBX, il est maintenant possible d’offrir aux organisations utilisant Skype for Business Online des fonctionnalités de contrôle des appels et de téléphonie directement depuis Office365.

Plusieurs options pour offrir la téléphonie avec le cloud pbx, l'utilisation du Cloud Connection Edition est l'un des scénarios possibles.

Skype for Business Cloud Connector Edition est un ensemble de machines virtuelles qui permet d’intégrer les fonctionnalités de téléphone Cloud PBX avec les équipements et liens PSTN présent localement sur site.
Les utilisateurs s’enregistrent et consomment les ressources Skype for Business dans Office 365, sont activés pour le Cloud PBX, mais les appels entrants et sortants transitent par le Cloud Connector Edition via le site local de l’organisation.

Cloud Connector Edition est une architecture hybride qui se compose d'un ensemble de machines virtuelles emballés (VM) permettant la connectivité avec l’infrastructure téléphonique existante locale.

CCE est un ensemble de machines virtuelles installant une topologie basique Skype for Business composé des machines virtuelles avec les modules suivants :

• Edge component – Communication between the on-premises topology and the online services goes through the Edge component, which includes the following components:

  • Access Edge – Provides SIP routing between the on-premises deployment and Skype for Business Online.

  • Media Relay – Provides routing of media between the Mediation component and other media endpoints.

  • Media Relay Authentication / MRAS – Generates tokens for access to media relay.

• Outbound Routing – Provides routing to gateways based on policies. Only global policies which are based on destination (outbound) PSTN numbers are supported.

• Central Management Store (CMS) role – Includes the configuration store for the topology components, including CMS File Transfer.

• Central Management Store (CMS) replica – Synchronizes configuration information from the global CMS DB on the CMS role server.

• Domain controller – Cloud Connector Active Directory Domain Services to store all the global settings and groups necessary to deploy Cloud Connector components. One forest will be created for each instance of Cloud Connector. The domain controller should not have any connections with the production Active Directory. Active Directory services include:

  • Active Directory Domain Services

  • Active Directory Certificate Services to issue internal certificates

• Mediation component – Implements SIP and Media gateway mapping protocol between Skype for Business and PSTN gateways. Also includes a CMS replica that synchronizes configuration from the global CMS database.

Les fonctionnalités offertes avec Cloud PBX étant en constante évolution, il est important de suivre les annonces de Microsoft concernant les ajouts de fonctionnalités dans cette nouvelle approche de la téléphonie.

Le lien ci-dessous résume les fonctionnalités offertes actuellement par cloud pbx:

https://support.office.com/en-us/article/Here-s-what-you-get-with-Cloud-PBX-bc9756d1-8a2f-42c4-98f6-afb17c29231c?ui=en-US&rs=en-US&ad=US

La roadmap:

Points à prendre en considération pour un projet Skype for Business Cloud PBX hybride avec Cloud Connector Edition :

• CCE, c'est donc quatre machines virtuelles par instance sur une machine hôte physique, placé dans la DMZ;
• Le seul hyperviseur supporté est Hyper-V, Les quatre machines virtuelles Windows qui sont provisionnés sur un seul hôte physique Windows Server 2012 R2 Datacenter Edition exécutant Hyper-V dans la DMZ. Ceci est une exigence by design, pas de Vmware, pas d'Azure, pas d'Amazon, pas de XenServer. La configuration du Cloud Connector nécessite d'exécuter du powershell a partir du serveur hôte qui va procéder a la totalité de l'installation.
• Au cours du déploiement, le processus crée sa propre forêt;
• Pas de dépendance à l'égard du domaine AD interne;
• Plan de numérotation attribué dans Skype for Business Online basé sur l'emplacement de l'utilisateur;
• Option pour restreindre les appels internationaux;
• Aucune coexistence avec un déploiement Skype For Business on premise déja existant dans l'organisation n'est possible pour l'instant;
• Le flux voix transite toujours par le serveur de médiation CCE (pas de media bypass pour l'instant);
• Les utilisateurs peuvent être créés dans les locaux et synchronisés en ligne en utilisant DirSync ou créés en ligne;
• Pour pouvoir offrir les fonctionnalités dialin Conferencing, il est nécessaire de souscrire par utilisateur a l’option PSTN Conferencing ou utiliser les services d’un partenaire ACP;
• Cloud Connector est disponible mondialement;
• Les utilisateurs sont hébergés dans Office 365;
• Les organisations peuvent conserver leurs opérateurs téléphoniques existants;
• CCE ne nécessite pas de licence a acquérir;
• Hosting Cloud Connector non supporté pour l'instant;
• Coexistance avec d'autres VM non supportée;

En terme d'architecture, il est possible d'avoir 4 instances CCE (3 actives + 1 en attente) par site permettant de pouvoir offrir 1,500 appels simultannées.

De nouvelles commandes powershell sont disponibles avec CCE:

Cloud Connector Edition exige les prérequis suivants:

• Une image de Windows Server 2012 R2 ISO (.iso). Les deux édition standard et Data Center sont pris en charge. L'ISO sera converti en VHD pour les machines virtuelles qui exécuteront Skype for Business Connector Couverture Édition;
• PBX ou passerelles de téléphonies supporté par Microsoft;
• Un certification pour les listeners externes du Edge obtenu par une autorité de certification publique;
• Prérequis materiel pour un environnement pour supporter 500 appels simultannées:
  • 64-bit dual processor, six core (12 real cores), 2.50 gigahertz (GHz) or higher
  • 64 gigabytes (GB) ECC RAM
  • Four 600 GB (or better) 10K RPM 128M Cache SAS 6Gbps disks, configured in a RAID 5 configuration
  • Three 1 Gbps RJ45 high throughput network adapters
• Prérequis materiel pour un environnement pour supporter 50 appels simultannées:
  • Intel i7 4790 quad core with Intel 4600 Graphics (no high end graphics needed)
  • 32 GB DDR3-1600 non ECC
  • 2: 1TB 7200RPM SATA III (6 Gbps) in RAID 0

    Plus d'informations ici: https://technet.microsoft.com/EN-US/library/mt605227.aspx

Microsoft vient de publier une série de mise a jour pour Lync Serveur 2013.

Téléchargement ici: https://support.microsoft.com/en-us/kb/3140581?sd=rss&spid=16660#bookmark-issues

Mise a jour:April 2016 cumulative update 5.0.8308.949 for the Lync Server 2013 Response Group service

Corrections:

• KB 3148956 Lync Server 2013 announcement service can't transfer an incoming call from iOS device
• KB 3148256 Event ID 31128 occurs when RGS can't synchronize an Agent Group member's SIP address

Mise a jour: April 2016 cumulative update 5.0.8308.949 for Lync Server 2013, Shared Line Appearance

Mise a jour: April 2016 cumulative update 5.0.8308.949 for Lync Server 2013, Core Components

Corrections:

• KB 3148961 Event ID 56417 when the window title of combined programs exceeds 128 characters in Lync Server 2013
• KB 3148960 "New sharer joined the conference" message when you try to share your desktop in an online meeting in Lync Server 2013
• KB 3148959 Bootstrapper.exe doesn't start on a non-English version of Lync Server 2013 RTM
• KB 3148950 Contacts and meeting dates are lost on Lync Server 2013 Front End server
• KB 3141122 Debug-CsInterPoolReplication returns "BATCHES OUT OF SYNC" error in Skype for Business Server 2015 or Lync Server 2013

Mise a jour: April 2016 cumulative update 5.0.8308.949 for Lync Server 2013, Front End Server and Edge Server

Corrections:

• KB 3148962 Stop error D1 when you try to stop Lync Edge services gracefully in Lync Server 2013
• KB 3148950 Contacts and Meetings dates may be lost on Lync Server 2013 Front End server

Mise a jour: April 2016 cumulative update 5.0.8308.949 for the Lync Server 2013, Mediation Server

Corrections: You hear noise or nothing at all when a call is forked to a PSTN number in Lync Server 2013.

Microsoft vient de publier une mise a jour de sécurité pour Skype for Business 2016

Date: 12 avril 2016

KB Skype for Business 2016: https://support.microsoft.com/fr-fr/kb/3114960

Améliorations et corrections:

• 3153360 Buffer may overrun when you use Skype for Business 2016
• 3153361 Black screen or slow screen updating during desktop sharing in Skype for Business 2016

Téléchargement:

• Download the security update for Skype for Business 2016 (32-bit) package now.
• Download the security update for Skype for Business 2016 (64-bit) package now.

KB Lync 2013 (Skype for Business): https://support.microsoft.com/fr-fr/kb/3114944

Bulletin de sécurité MS16-039: https://technet.microsoft.com/library/security/MS16-039 

Améliorations et corrections:

• 3153357 Buffer may overrun when you use Lync 2013 or Skype for Business
• 3153356 Can't join a Lync online's audio/video meeting in Skype for Business that has a proxy server set

Téléchargement:

• Download the security update KB3114944 for Lync 2013 (32-bit) (Skype for Business) now.
• Download the security update KB3114944 for Lync 2013 (64-bit) (Skype for Business) now.

Mise a jour Office: https://support.microsoft.com/en-us/kb/3150264?sd=rss&spid=16924