Le Cloud de Christophe BOUCETTA

Voici le blog sur les communications unifiées et la collaboration Microsoft par un MVP nominé depuis 11 ans
  • [Microsoft Lync Server 2013] Mise à jour Lync Room System -November 2014 - (KB3011144)

    Microsoft vient de publier une mise à jour pour Lync Room System: http://support2.microsoft.com/kb/3011144

    This update provides the following improvements for Lync Room System:

    • Adds functionality to make public switch telephone network (PSTN) calls and adds a Find a contact button in the In-meeting dial pad.
    • Adds functionality to the "Where is my join button" feature so that users can create a meeting by using the existing meeting information from the console. 
    • Adds functionality to reduce the number of Lync Room System restarts for future device updates that are later than the November 2014 update (version 15.12.0). 
    • Adds functionality to monitor Lync Room Systems in a workgroup by using System Center Operations Manager.
    • Improves some UI colors on the console and front of room screens. Before the UI colors are improved, some buttons appear dimmed and disabled even though they are active.

  • [Microsoft Lync Server 2013] Installer une cumulative update

    C'est une question qui ressort fréquemment lors des transferts de compétences.

    Deux options sont possibles pour mettre à jour votre environnement:

    -Microsoft Update/WSU: Étant automatique, le risque d'oublier d'appliquer la commande de mise à niveau des bases de données est importantes. De plus, mettre à jour un système de téléphonie de manière transparente et sans contrôle comporte un risque;

    - LyncServerUpdateInstaller.exe:

    Cette exécutable rassemble l'ensemble des dernières mises à jours et s'applique manuellement;

    Le fichier est le même que votre environnement est en version Standard et Entreprise;

    Vous devez appliquer les mises à jours sur l'ensemble de vos serveurs Lync;

    Vous pouvez télécharger le fichier ici: http://www.microsoft.com/en-us/download/details.aspx?id=36820;

    Pour une application du fichier de mise à jour dans un environnement EntReprise, il faut prendre en considération que les serveurs frontaux d’un pool sont organisés en domaines de mise à niveau. Il s’agit de sous-ensembles des serveurs frontaux dans le pool. Les domaines de mise à niveau sont créés automatiquement par le Générateur de topologie. Quand vous effectuez la mise à niveau des serveurs, vous devez procéder un domaine de mise à niveau à la fois. Arrêtez chaque serveur dans un domaine de mise à niveau, effectuez sa mise à niveau, puis redémarrez-le avant de passer au domaine de mise à niveau suivant. Veillez à assurer un suivi des serveurs et domaines de mise à niveau déjà mis à niveau.

    Utilisez le diagramme de flux suivant dans la cadre de la mise à niveau de chaque serveur.

    1- Sur le serveur frontal du pool, appliquer la commande suite pour vérifier si vous pouvez passer les mises à jours en toute sécurité

    Get-CsPoolUpgradeReadinessState

    PoolUpgradeState=  Busy, vérifier les informations remontés avec la commande pouvant indiquer un problème dans votre environnement devant être résolu avant d'appliquer les mises à jours.

    PoolUpgradeState=  Ready, vous pouvez passer à l’étape 2.

    La commande Stop-CsWindowsService -Graceful -Verbose vous permet d'interrompre les nouvelles connexions aux serveurs frontaux que vous allez mettre à niveau.

    2- Appliquer LyncServerUpdateInstaller.exe:

    Il est possible de préciser des options lors du lancement de l'application:

    /silentmode: Applique toutes les mises à jours en arrière plan;

    /silentmode /forcereboot: Applique toutes les mises à jours en arrière plan et redémarre le serveur si nécessaire;

    /extractall: extrait les mises à jours dans un sous-répertoire nommé "Extracted";

    Lancer l'exécutable:

    Vous êtes en mesure de vérifier votre versions actuelles applicatives, un indicateur visuel permet d'indiquer si un composant est en dernière version ou non.

    Appuyer sur -Install Updates- lancent automatiquement la mise à niveau des composants vers la dernière version:


    Un redémarrage du serveur est nécessaire:

    2- Appliquer les mises à jours sur les bases de données:

    Lync Server 2013 Standard Edition: Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose

    Lync Server 2013 Enterprise Edition: Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose

    Lync Server 2013 Persistent Chat Databases: Install-CsDatabase -DatabaseType PersistentChat -SqlServerFqdn PChatBE.fqdn -SqlInstanceName DBInstance -Verbose

    Lync Server 2013 Monitoring/Archiving/Persistent Chat Databases: Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn SQLServer.FQDN -Verbose

    3- Appliquer les mises à niveaux sur le CMS:

    Dans le cas ou vous avez déjà appliqué la mise à jour de février 2013, il n'est pas nécessaire de procéder à cette étape.

    Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn CMS.FQDN -SqlInstanceName DBInstanceName -Verbose

    4- Activer la mobilité:

    Dans le cas ou vous avez déjà appliqué la mise à jour de février 2013, il n'est pas nécessaire de procéder à cette étape.

    Enable-CsTopology

    5- Activer UCWA

    Dans le cas ou vous avez déjà appliqué la mise à jour de février 2013, il n'est pas nécessaire de procéder à cette étape.

    %ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe

  • [SKYPE] Skype for Web (Beta)

    Skype vient d'annoncer l'arrivée imminente des fonctionnalités web en version bétà.

    Simply sign in to Skype for Web on Skype.com and you’ll be able to connect and start instant messaging directly from your browser.

    You can connect to Skype for Web from Internet Explorer, Chrome on Windows, Firefox or Safari on your computer –

    Once you’ve signed in on Skype.com, you can start instant messaging friends straight away. Making great quality voice or video calls is just as easy; simply press the call button to connect.

    Known issues:

    Category Description
    Browser availability Skype for Web works onWindows: Internet Explorer 10 and above and the latest versions of Chrome and Firefox.Mac OS: Safari 6 and above.
    Battery life Issue with battery consumption when running Skype for Web on a Mac.
    Video call connection times Outgoing Skype calls can take longer than normal to ring.

    Information ici: http://blogs.skype.com/2014/11/14/please-welcome-skype-for-web-beta/

  • [Microsoft Lync Server 2013] IIS Crypto

    IIS Crypto est un outil gratuit intéressant.

    Description:

    IIS Crypto is a free tool that gives administrators the ability to enable or disable protocols, ciphers, hashes and key exchange algorithms on Windows Server 2003, 2008 and 2012. It also lets you reorder SSL/TLS cipher suites offered by IIS, implement best practices with a single click and test your website.

    Features:

    •     Single click to secure your site using best practices
    •     Stop BEAST and POODLE attacks
    •     Easily disable SSL 2.0 and SSL 3.0
    •     Enable TLS 1.1 and 1.2
    •     Disable other weak protocols and ciphers
    •     Enable forward secrecy
    •     Reorder cipher suites
    •     Templates for compliance with government and industry regulations - FIPS 140-2 and PCI

    Url: https://www.nartac.com/Products/IISCrypto/

  • [Microsoft Lync Server 2013] Configuring the Windows Server 2012 Web Application Proxy as a Reverse Proxy for Lync Server

    Microsoft vient de publier un nouveau document concernant la configuration de Windows Server 2012 Web Application Proxy en tant que reverse proxy pour lync.

    Description:

    Version: Nov2014
    File Name: Configuring_the_Windows_Server_2012_Web_Application_Proxy_as_a_Reverse_Proxy_for_Lync_Server.doc
    Date Published: 11/12/2014
    File Size: 2.4 MB

    This whitepaper describes how to configure the Windows Server 2012 R2 Web Application Proxy as a reverse proxy for Lync Server. The service allows internal applications such as Microsoft Lync and Exchange to be published for external access. The Web Application Proxy service functions as both a reverse proxy and an Active Directory Federation Services (AD FS) proxy.

    Lien: http://www.microsoft.com/en-us/download/details.aspx?id=44940

  • [Microsoft Lync Server 2013] Skype for Business

    Microsoft vient de publier quelques nouvelles concernant la prochaine version de Lync: Skype for Business

    Vous pouvez accèder à l'article d'introduction ici: http://blogs.office.com/2014/11/11/introducing-skype-business/

    In the first half of 2015, the next version of Lync will become Skype for Business with a new client experience, new server release and updates to the service in Office 365.

    Skype for Business keeps and improves on all of the capabilities of Lync, including content sharing and telephony.  For example, transferring a call now takes only one touch or click instead of three

    For example, as you can see in the screenshots, we’re adopting the familiar Skype icons for calling, adding video and ending a call

    Current Lync Server customers will be able to take advantage of these capabilities simply by updating from Lync Server 2013 to the new Skype for Business Server in their datacenters

    No new hardware is required.

  • [Microsoft Lync Server 2013] Polycom Soundpoint: TLS-DSK: Setting of Client Certificate failed due to (33558531) error:02001003

    Tout juste revenu du MVP Summit la semaine dernière, j'ai du me pencher vendredi sur le processus de récupération de plusieurs centaines de Polycom Soundpoint existant dans le cadre d'un de nos projets de migration toip Lync actuel.

    Contexte:

    Les premiers tests avec le firmware Polycom UC Software 4.0.2 permettent l'enregistrement de l'utilisateur dans le nouvel environnement Lync.

    Pour corriger quelques irritants (principalement les reboot) et accèder aux nouvelles fonctionnalités, le firmware Polycom UC Software 4.1.1 du mois de Juin est testé aussi.

    Description Polycom UC Software 4.1.1:

    Polycom UC Software 4.1.1 is for use with Microsoft Lync Server and using a single registered line only.
    UC Software 4.1.1 supports the following Polycom devices:
    ● SoundPoint IP 321, 331, 335, 450, 550, 560, and 650 desktop phones. The SoundPoint IP 670 is not supported.
    ● SoundStation IP 5000 conference phones
    ● SoundStation Duo conference phones

    Polycom UC Software 4.1.1 does not support VVX 300/310, VVX 400/410, VVX 500, VVX 600, and VVX 1500 business media phones. For more support on these platforms, refer to the UC Software/SIP Software Release Matrix.

    New or Enhanced Features
    90757 Add support for pin authentication (applies to SoundPoint IP 450, 550, 560, 650, SoundStation IP 5000 and SoundStation Duo).

    Enhanced Capabilities
    92710 The phone now successfully attends the call routed through Exchange Auto Attendant and no longer causes any de-registration issue on the phone.
    92708/88402 The phone now obeys the Lync 2013 normalization rules and goes offhook or onhook within the configured time.
    92707/87064 In a Lync 2010 environment, the phone now dials the extention format number without any issue (applies to SoundPoint IP331).
    92705/84764 In a Lync 2010 environment, the TLS transport option is now available on the phone when it is installed in the Russian SKU.
    92621 Filtering for the exposed debug UDP port to address security issues is working as expected for the customers running port scans on Polycom devices. The phone no longer exposes UDP 17185.
    92558/91447/91564 Local and remote ringback tone is no longer heard on outgoing calls after receiving 183 and 180 responses.
    92221/91183 In a Lync 2010 environment, performance of the SoundStation IP 5000 phone is improved, and it no longer freezes after 12 hours of idle time.
    91408 In a Lync 2013 environment, the SoundPoint IP 321/331/335 phones no longer freeze or reboot randomly.


    Problème:

    Suite aux changement de software, aucun des utilisateurs de tests ne peuvent s'enregistrer sur les serveurs Lync.

    Erreurs dans les téléphones Polycom:

    1107144149|sip  |4|03|TLS-DSK: Setting of Client Certificate failed due to (33558531) error:02001003:system library:fopen:errno = 0x3
    1107144149|sip  |4|03|TLS-DSK: Setting of Client Private key failed due to (537346050) error:20074002:BIO routines:FILE_CTRL:system lib


    Erreurs dans les traces Lync:

    Résolution:

    La réponse vient de cette discussion sur le forum polycom: http://community.polycom.com/t5/VoIP/Certificate-Error/td-p/55828

    UCS 4.1.1 added Pin Auth to several SPIP models and therefore the standard software setting for loginCredentialType is PinAuth.

    Dans le fichier de configuration du téléphone, préciser le mode d'enregistrement: reg.1.auth.loginCredentialType="usernameAndPassword"

  • [Microsoft Lync Server 2013] AudioCodes Mediant SBC Configuration Wizard

    Précedemment, j'avais déjà évoquer l'outil fourni par Audiocodes permettant de génerer la configuration de base d'une passerelle SBC: http://microsofttouch.fr/default/b/christophe/archive/2014/07/15/microsoft-lync-server-2013-audiocodes-sbc-wizard.aspx

    Depuis la publication de cette article, le nombre de template disponible est de plus en plus important.

    L'outil est actuellement en version 1.21, la dernière version de template en 1.48.

    Dernière mise a jour de l'outil:

    v1.21 (Oct 26, 2014)
    Fixed SRTP configuration for Remote Users application
    Added optional Local Prefix configuration for IP-PBX
    Added spacing to routing table
    v1.20 (Oct 6, 2014)
    Fixed NAT configuration for Remote Users application
    v1.19 (Sep 15, 2014)
    Added template pack version history
    Switched to Qt5 library

    Vous pouvez même demander à Audiocodes l'ajout de template via l'adresse courriel interop@audiocodes.com

    La liste complète des templates est disponible ici:

    v1.48 (Nov 3 2014)
    Added "Genesys SIP Server - CenturyLink SIP Trunk" template
    Fixed "Genesys SIP Server - AireSpring SIP Trunk" template
    v1.47 (Oct 27 2014)
    Fixed "Microsoft Lync 2013 - Telenor SIP Trunk" template
    v1.46 (Oct 26 2014)
    Added "Genesys SIP Server - AireSpring SIP Trunk" template
    Added "Microsoft Lync 2013 - Telenor SIP Trunk" template
    Added "Microsoft Lync 2013 - Intelepeer SIP Trunk" template
    v1.45 (Oct 2 2014)
    Added "BroadSoft - Generic SIP Trunk" template
    v1.44 (Sep 28 2014)
    Fixed "Alcatel-Lucent Remote Users" template
    v1.43 (Sep 15 2014)
    Added "Microsoft Lync 2013 - Avaya CS1000" template
    v1.42 (Sep 8 2014)
    Added "Ericsson-LG IPECS MFIM - Telkom SA Premium SIP Trunk" template
    Added "Ericsson-LG IPECS MFIM - Telkom SA Standard SIP Trunk" template
    Added "Microsoft Lync 2013 - Neotel SIP Trunk" template
    Added "NEC 3C PBX Remote Users" template
    Fixed media ports range in the following templates:
    "Microsoft Lync 2010 - AT&T IP Toll Free SIP Trunk"
    "Microsoft Lync 2010 - AT&T IP Toll Free SIP Trunk"
    "Vocalcom Call Center - Belgacom SIP Trunk"
    v1.41 (Aug 5 2014)
    Added "ShoreTel PBX - Telecom NZ SIP Trunk" template
    All Lync templates renamed to indicate Lync version
    v1.40 (Jul 31 2014)
    Added "Microsoft Lync - Hong Kong Broadband" template
    Added "Microsoft Lync - SingTel SIP Trunk" template
    Added "Microsoft Lync - UPC Nederland" template
    v1.39 (Jul 22 2014)
    Updated "Microsoft Lync - Verizon SIP Trunk" template
    Updated "Microsoft Lync 2013 - Bell Canada SIP Trunk" template
    v1.38 (Jul 21 2014)
    Added "Alcatel-Lucent Remote Users" template
    Added "Microsoft Lync - Skype SIP Trunk" template
    v1.37 (Jun 19 2014)
    Fixed "Microsoft Lync - Netia SIP Trunk" template
    v1.36 (Jun 18 2014)
    Fixed "Microsoft Lync - Swisscom VoIP Gate" template - added reference to LTRT document
    v1.35 (Jun 17 2014)
    Added "Microsoft Lync - Swisscom VoIP Gate" template
    Added "Microsoft Lync - Netia SIP Trunk" template
    Fixed "Microsoft Lync - BluIP SIP Trunk" template - added SIPGATEWAYNAME
    v1.34 (Jun 11 2014)
    Added "Microsoft Lync 2013 - Bell Canada SIP Trunk" template
    Renamed "Microsoft Lync - Bell Canada SIP Trunk" template to "Microsoft Lync 2010 - Bell Canada SIP Trunk"
    v1.33 (Jun 10 2014)
    Update for Wizard v1.15 - removed remote FEU port from all relevant templates
    v1.32 (Jun 5 2014)
    Added "Genesys SIP Server - Colt SIP Trunk" template
    Added "Microsoft Lync - Vodafone NZ SIP Trunk" template
    Added "Microsoft Lync - TELUS SIP Trunk" template
    v1.31 (May 7 2014)
    Added "Microsoft Lync - Telstra SIP Enterprise" template
    v1.30 (Apr 30 2014)
    Added "Microsoft Lync - BT BV IP Connect" template
    Added "Microsoft Lync - G12 SIP Trunk" template
    Added "SAP Contact Center - Colt SIP Trunk" template
    v1.29 (Feb 23 2014)
    Added "Alcatel-Lucent OXE - Colt SIP Trunk" template
    Added "Alcatel-Lucent OXE - Gamma SIP Trunk" template
    Changed NAT configuration syntax to match Wizard v1.14
    v1.28 (Jan 21 2014)
    Obscured usernames and primary lines in all templates
    v1.27 (Jan 15 2014)
    Fixed "Microsoft Lync - Virginmedia SIP Trunk" template
    v1.26 (Jan 7 2014)
    Added "Microsoft Lync - Virginmedia SIP Trunk" template
    v1.25 (Nov 28 2013)
    Added "Microsoft Lync - Tipicall SIP Trunk" template
    v1.24 (Nov 17 2013)
    Added "Microsoft Lync - BCX SIP Trunk" template
    Added "Microsoft Lync - Mitel 3300 MXE III Call Center" template
    Added "Microsoft Lync - Telavox SIP Trunk" template
    Added "Microsoft Lync - VOX SIP Trunk" template
    Added "Mitel 3300 MXE III Call Center - BCX SIP Trunk" template
    Added "Mitel 3300 MXE III Call Center - VOX SIP Trunk" template
    Added "MTN Hosted IP-PBX" template
    v1.23 (Nov 12 2013)
    Added "Alcatel-Lucent OXE - Counterpath Softphones" template
    Added "Avaya IP-PBX - Office 365 Exchange Online" template
    Added "Cisco CUCM - Office 365 Exchange Online" template
    Added "Genesys SIP Server - SIPUS SIP Trunk" template
    Added "Microsoft Lync - Alphalink SIP Trunk" template
    Added "Microsoft Lync - Gamma SIP Trunk" template
    Added "Microsoft Lync - IP Directions SIP Trunk" template
    Added "Vocalcom Call Center - Belgacom SIP Trunk" template
    v1.22 (Oct 27 2013)
    Added "Microsoft Lync - Hipcom SIP Trunk" template
    Fixed account configuration in BellCanada templates
    v1.21 (Oct 23 2013)
    Added "Asterisk - XO SIP Trunk" template
    Added "Avaya IP-PBX - Alcatel-Lucent OXE" template
    Added "Avaya IP-PBX - Bell Canada SIP Trunk" template
    Added "Avaya IP-PBX - Cisco CUCM" template
    Added "Avaya IP-PBX - Verizon SIP Trunk" template
    Added "Cisco CUCM - AT&T Enhanced IPFR" template
    Added "Genesys SIP Server - Alcatel-Lucent OXE" template
    Added "Genesys SIP Server - Avaya IP-PBX" template
    Added "Genesys SIP Server - Cisco CUCM" template
    Added "Microsoft Lync - Interactive Intelligence" template
    Updated "Microsoft Lync - Windstream SIP Trunk" template
    Modified all templates - removed "redundant" domain names
    v1.20 (Oct 17 2013)
    Added "Microsoft Lync - AT&T Enhanced IPFR" template
    Added "Microsoft Lync - Alteva SIP Trunk" template
    v1.19 (Oct 16 2013)
    Added "Microsoft Lync - Alcatel-Lucent OXE" template
    Added "Microsoft Lync - Cisco CUCM" template
    Added "Alcatel-Lucent OXO - IP Directions SIP Trunk" template
    Added "Alcatel-Lucent OXE - Completel SIP Trunk" template
    Added "Microsoft Lync - Tele2 SIP Trunk" template
    Added "Cisco CUCM - Completel SIP Trunk" template
    Added "Avaya IP-PBX - Completel" template
    Added "DuPont Hosted IP-PBX" template
    Added "Microsoft Lync - MWEB SIP Trunk" template
    Cleaned up "Alcatel-Lucent - Broadvox SIP Trunk" template
    v1.18 (Oct 13 2013)
    Added "Microsoft Lync - BluIP SIP Trunk" template
    v1.17 (Oct 6 2013)
    Fixed "Alcatel-Lucent - Broadvox SIP Trunk" template
    v1.16 (Sep 23 2013)
    Renamed "Microsoft Lync - GTS-CE SIP Trunk" to "Microsoft Lync - GTS-Hungary SIP Trunk"
    v1.15 (Sep 23 2013)
    Added "Microsoft Lync - GTS-CE SIP Trunk" template
    Added "Microsoft Lync - MTS Allstream SIP Trunk" template
    v1.14 (Sep 10 2013)
    Added "Genesys SIP Server - AT&T IPTF" template
    Added "Genesys SIP Server - Verizon SIP Trunk" template
    Renamed "Genesys SRV" templates to "Genesys SIP Server"
    Added "Avaya Session Manager - Microsoft Office 365" template
    v1.13 (Aug 6 2013)
    Added "Microsoft Lync - BT One Voice" template
    v1.12 (Aug 1 2013)
    Added "Microsoft Lync - Verizon SIP Trunk" template
    Fixed SRTP configuration in all Lync templates to use explicit Media Protocol configuration
    v1.11 (Jul 30 2013)
    Added "ShoreTel PBX - MWEB SIP Trunk" template
    Added "Microsoft Lync - Avaya S8700" template
    Changed beta status for templates confirmed by FAEs
    v1.10 (Jul 29 2013)
    Added "Microsoft Lync - OVH SIP Trunk" template
    Added "Microsoft Lync - Neotel SIP Trunk" template
    Fixed SRTP configuration in all Lync templates - the section is present only when SRTP is actually used
    v1.9 (Jul 17 2013)
    Added "Microsoft Lync - Internet Solutions SIP Trunk" template
    Fixed "Toshiba IP Edge - TM SIP Trunk" template
    v1.8 (Jul 11 2013)
    Added "Microsoft Lync - CogecoData SIP Trunk" template
    Fixed "Genesys SRV - AT&T Enhanced IPFR" template
    Fixed "Genesys SRV - AT&T IPFR" template
    Fixed "Microsoft Lync - In Technology SIP Trunk" template
    Fixed "Microsoft Lync - QSC AG SIP Trunk" template
    Fixed "Microsoft Lync - XO Communications SIP Trunk" template
    Fixed "Microsoft Lync - Telstra SIPConnect" template
    Fixed "Toshiba IP Edge - TM SIP Trunk" template
    v1.7 (Jul 10 2013)
    Added "Microsoft Lync - Telstra SIPConnect" template
    v1.6 (Jul 8 2013)
    Added "Toshiba IP Edge - TM SIP SIP Trunk" template
    Obscured IP addresses in "Genesys - AT&T" templates
    Added support for Remote Users to "Genesys - AT&T" templates
    v1.5 (Jul 2 2013)
    Added "Alcatel-Lucent - Broadvox SIP Trunk" template
    Added labels to all templates (to be shown on setup picture)
    v1.4 (Jul 2 2013)
    Fixed "Genesys SRV - AT&T Enhanced IPFR" template
    Fixed "Genesys SRV - AT&T IP Flexible Reach" template
    Removed "Alcatel-Lucent OmniPCX" template
    v1.3 (Jun 30 2013)
    Added "Alcatel-Lucent OmniPCX" template
    v1.2 (Jun 30 2013)
    Added "Genesys SRV - AT&T Enhanced IPFR" template
    v1.1 (Jun 27 2013)
    Added "Genesys SRV - AT&T IP Flexible Reac

  • [Microsoft Lync Server 2013] Lync RGS Emergency Failover Script

    Paul partage un script intéressant dans gallery.technet.microsoft.com.

    Nom du script: Lync RGS Emergency Failover Script

    Description:

    What happens to my Response Group Calls when we have to suddenly evacuate the building?

    This script refers to failing over the DDI that accesses the RGS so effectivly PSTN access to the RGS Workflow in question. Simply stated, a preconfigured Emergency Workflow complete with announcements and failover otions is configured prior to using this script. This script fails over the Line URI from an active RGS Workflow to an Emergency Workflow and vice versa depending on the menu selection by the administrator.

    Téléchargeable ici: https://gallery.technet.microsoft.com/Lync-RGS-Emergency-b48c1647

    Merci à l'auteur.


  • [SKYPE] Inscription pour le Skype's real-time voice translation preview

    Il est actuellement possible de s'incrire pour la preview Skype concernant la traduction vocale.

    L'inscription est simple et disponible sur cette URL: http://www.skype.com/en/translator-preview/

    Description du service:

    Speak another language without learning another language. Simply set up a Skype video or voice call with someone who speaks another language to you and start talking.

    Your conversation is translated into their language in real time.

    And what they say is translated back in your language.

    An on-screen transcript of your call is displayed.

    Instant message chats in 45 languages can be translated.

    Vidéo:


    Inscription vraiment simple:

  • [Microsoft Lync Server 2013] Vulnérabilité SSL 3.0

    Le 29 octobre, Microsoft a annoncé la fin du support du protocole SSL 3.0 dans Office 365 à partir du 1er décembre 2014: http://blogs.office.com/2014/10/29/protecting-ssl-3-0-vulnerability/

    Description:

    To help protect our customers further, we will be disabling fallback to SSL 3.0 in IE, disabling SSL 3.0 by default in IE, and across Microsoft online services, over the coming months.

    Starting on December 1, 2014, Office 365 will begin disabling support for SSL 3.0. This means that from December 1, 2014, all client/browser combinations will need to utilize TLS 1.0 or higher to connect to Office 365 services without issues. This may require certain client/browser combinations to be updated.


    Décision logique suite Security Advisory 3009008 du 14 octobre 2014: https://technet.microsoft.com/en-us/library/security/3009008.aspx

    Executive Summary

    Microsoft is aware of detailed information that has been published describing a new method to exploit a vulnerability in SSL 3.0. This is an industry-wide vulnerability affecting the SSL 3.0 protocol itself and is not specific to the Windows operating system. All supported versions of Microsoft Windows implement this protocol and are affected by this vulnerability. Microsoft is not aware of attacks that try to use the reported vulnerability at this time. Considering the attack scenario, this vulnerability is not considered high risk to customers.

    We are actively working with partners in our Microsoft Active Protections Program (MAPP) to provide information that they can use to provide broader protections to customers.

    Microsoft is announcing that SSL 3.0 will be disabled in the default configuration of Internet Explorer and across Microsoft online services over the coming months. We recommend customers migrate clients and services to more secure security protocols, such as TLS 1.0, TLS 1.1 or TLS 1.2. .


    Une importante faille de sécurité a été découverte dans la version du protocole SSL par une équipe de chercheurs travaillant chez Google. Elle pourrait permettre à des pirates de s’insérer entre un serveur et un client pour récupérer des informations chiffrées. La seule protection efficace semble être la désactivation totale du protocole. Ce n'est pas une vulnérabilité venu du code de Lync, mais c'est une faille de sécurité venant de l'OS. SSL 3.0 est un protocole ayant 18 ans qui a été supplanté par TLS, dont la version 1.0 a été publiée en 1999 par l’IETF.

    Je ne suis pas un expert sécurité, mais je me dois de livrer des services UC sécurisés à mes clients.

    Que faire?


    Vous pouvez déjà commencer par vérifier votre déploiement avec https://www.digicert.com/help/:

    Si vous déployer sur des versions OS Windows Serveur 2012 ou Windows Serveur 2012 R2, vous pouvez désactiver SSL 3.0 avec la commande suivante:

    reg add "HKLM\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server" /v Enabled /t REG_DWORD /d 0 /f

    Un redémarrage des services est nécessaires.

    Manipulations effectuées dans notre environnement de production sur les serveurs Lync FE, edge, reverse proxy et WAC.

    Si vous avez Windows Serveur 2008R2, vous pouvez trouver ici un script activant TLS: http://masteringlync.com/files/2014/10/EnableTLS.txt

    # Add and Enable TLS 1.0 for client and server SCHANNEL communications
    md 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0' -Force
    md 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server' -Force
    New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server' -name 'Enabled' -value '0xffffffff' -PropertyType 'DWord' -Force
    New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server' -name 'DisabledByDefault' -value 0 -PropertyType 'DWord' -Force
     
    # Add and Enable TLS 1.1 for client and server SCHANNEL communications
    md 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1' -Force
    md 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server' -Force
    md 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client' -Force
    New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server' -name 'Enabled' -value '0xffffffff' -PropertyType 'DWord' -Force
    New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server' -name 'DisabledByDefault' -value 0 -PropertyType 'DWord' -Force
    New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client' -name 'Enabled' -value 1 -PropertyType 'DWord' -Force
    New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client' -name 'DisabledByDefault' -value 0 -PropertyType 'DWord' -Force
     
    # Add and Enable TLS 1.2 for client and server SCHANNEL communications
    md 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2' -Force
    md 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server' -Force
    md 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -Force
    New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server' -name 'Enabled' -value '0xffffffff' -PropertyType 'DWord' -Force
    New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server' -name 'DisabledByDefault' -value 0 -PropertyType 'DWord' -Force
    New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -name 'Enabled' -value 1 -PropertyType 'DWord' -Force
    New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -name 'DisabledByDefault' -value 0 -PropertyType 'DWord' -Force

    La lecture de son article sur le sujet est vraiment intéressant: http://masteringlync.com/2014/10/20/poodle-and-lync-server-2013/

    Après manipulations, tests digicert avec les Edge:

  • [Microsoft Lync Server 2013] TechEd Europe 2014 - Vidéo

    Les TechEd Europe 2014 ont eu lieu la semaine dernière, les vidéos concernant les sessions Lync sont disponibles ici: http://channel9.msdn.com/Events/TechEd/Europe/2014?sort=sequential&direction=desc&term=lync#theSessions

  • [Microsoft Lync Server 2013] Attendant Pro pour Lync

    Matt Landis propose une console opératrice pour Lync vraiment sympa supportant maintenant le BTOE avec l'ensemble des modèles de téléphones IP qualifiés.

    Vidéo ici:

    Plus d'information ici: http://landiscomputer.com/attendantpro

  • [Microsoft Lync Server 2013] Reset factory d'un modèle Audiocodes série 400HD

    Les identifiants par défaut sont admin avec le mot de passe 1234.

    Plusieurs options pour faire un reset factory d'un modèle 400HD Audiocodes:

     -Au boot du téléphone:


    1 Redémarrer le téléphone
    2 Presser les touches OK + MENU pendant 5 seconds.
    3 Relacher les touches OK + MENU, le téléphone passe automatiquement en configuration d'usine

    - Sur le téléphone:

    Aller chercher l'option dans MENU > Administration > Restore Defaults:

    - Sur l'interface web:

    Aller chercher l'option dans Management > Administration > Restore Defaults:

  • [Microsoft Lync Server 2013] Mise à jour d'un firmware SNOM avec Pumpkin

    Pour diverses raisons, tests, pilotes, prêt de téléphones ou vous avez besoin de mettre à jour le micro logiciel d'un téléphone SNOM vers la version UC Edition, vous pouvez utiliser Pumpkin si le téléchargement directement à partir du lien internet échoue avec l'erreur « File not found ».

    Téléchargement de Pumpkin ici: http://kin.klever.net/pumpkin/#.VExMgMkgA00

    Fonctionnalités de Pumpkin:

    •     Fully standard-compliant TFTP file transfer
    •     Unlimited simultaneous transfers both for TFTP server and client
    •     Support for TFTP blocksize option allows transfer of large files if both TFTP server and client support it
    •     Convenient GUI
    •     Combines TFTP server and TFTP client
    •     Can run in background, taking up a 256 pixels of screen nicely packed as a 16x16 square in your notification tray area (windows only)
    •     Open source for those willing to add missing features, fix bugs and examine code for potential flaws and fun
    •     You're free to torture it the way you want to as long as you preserve original author's credentials
    •     It would cost you nothing unless you're willing to monetarily express your gratitude and make a donation (yes, it means "free" or "freeware", just go and download it)
    •     The download size is about that of the high quality screenshot below (windows only — Mac version is bigger, due to graphics supplied for way too many resolutions).


    Téléchargement du firmware SNOM UC Edition ici: http://www.snom.com/en/your-personal-menu/snom-uc-edition-firmware-center/snom-uc-edition-front-desk/

    Renommer le fichier au format suivant (exemple):

    •     snom710 8.7.3.25 -->  Rename to snom710-r.bin
    •     snom715 8.7.5.8.2 --> Rename to snom715-r.bin
    •     snom720 8.7.3.25 -->  Rename to snom720-r.bin
    •     snom760 8.7.3.25 -->  Rename to snom760-r.bin

    Lancer l'application:

    • Préciser l'emplacement de votre répertoire
    • Choisir Give all files
    • Choisir Take all files

    Allumer le téléphone en restant appuyer sur la touche # jusqu'à l'apparition du mode "Rescue mode";

    Presser 2 Recovery via Network;

    Préciser les paramêtres réseaux et l'ip de votre serveur ftp Pumpkin:


    Choisir l'option 3

    Téléchargement du firmware

  • [Microsoft Lync Server 2013] Fédération “Presence Unknown“

    Petit bug du jour.

    Contexte:

    Support chez un client, toutes les fédérations ne sont plus opérationnels.

    Après quelques tests basiques, il s'avère qu'il n'est pas non plus possible de se connecter par le biais du edge.

    Erreur dans les logs:

    L'ensemble des partenaires fédérés rejettent les tentatives de connection TLS:


    La trace sip pointe un problème au niveau certificat:

    L'origine du problème est identifée dans les logs de nos serveurs Edge, étant aussi un des partenaire fédéré:

    Le certificat a était révoqué!

    Résolution:

    Télécharger le nouveau certificat avec la nouvelle clé, importer le dans les serveurs Edge du pool et redémarrer les services Lync.

  • [Microsoft Lync Server 2013] Réparer un certificat à clé publique

    Vous réimporter un nouveau certificat à clé publique sur votre serveur mais la clé privée n'est pas associé au certificat?

    Vous pouvez utiliser l'outil de Digicert DigiCert Certificate Utility téléchargeable ici: https://www.digicert.com/util/

    Les étapes sont simples:

  • [Microsoft Lync Server 2013] Lync 2013 Now Supports Falling Back to the Lync Web App

    A lire!


    Description:

    We recently made a change to the Lync 2013 client to support the ability to fall back to the Lync Web App in the event that a user has Lync installed but has never signed in. This was frequently a challenge because various versions of Office 2013 come with Lync 2013 installed by default. There are ways that IT pros and administrators can control this however many installations include Lync 2013 by default.

    The change was first introduced in Lync 2013 version 15.0.4623.1001 so if you install any version that was released after that your Lync client will contain this change. You can find a link to the most recent Lync updates at the following URL: http://technet.microsoft.com/en-us/office/dn788954.aspx.

    http://blogs.technet.com/b/scottstu/archive/2014/10/30/lync-2013-now-supports-falling-back-to-the-lync-web-app.aspx

  • [Microsoft Lync Server 2013] Mise à jour Lync Serveur 2013 5.0.8308.831 – Octobre 2014

    Microsoft vient d'annoncer une mise a jour pour Microsoft Lync Serveur 2013 pour ce mois d'Octobre 2014, la version est 5.0.8308.831.


    Description:

    Mise à jour:

    • Update for Standard or Enterprise Edition server (Front End Servers and Edge Servers): 3001616 October 2014 Cumulative Update 5.0.8308.831 for Lync Server 2013 (Front End Server and Edge Server)

    The cumulative update resolves the following issues:

      • 3003346 Cannot see presence status or send instant messages when OWA is integrated with Lync Server 2013 instant messaging
      • 3003347 User cannot dial out to a PSTN number as a guest in an online meeting in a Lync Server 2013 environment
      • 3003350 Cannot search users by using a keyword that differs from Lync Server 2013 AD DS display name format in a Lync client
      • 3003347 User cannot dial out to a PSTN number as a guest in an online meeting in a Lync Server 2013 environment

    • Update for Core Components: 3003358 October 2014 Cumulative Update 5.0.8308.831 for Lync Server 2013 core components

    The cumulative update resolves the following issue:

      • 3008181 Centralized Logging Service Agent Service cannot start after you install a September 2014 update for Lync Server 2013

    Téléchargement:  http://www.microsoft.com/en-us/download/details.aspx?id=36820

    KB3001616: http://support.microsoft.com/kb/3001616

  • [Microsoft Lync Server 2013] Update client Lync pour Mac 14.0.10

    Microsoft vient d'annoncer la release Lync pour Mac 14.0.10

    Les principaux points de ce KB sont:

    • Support for Yosemite (OSX 10.10)
    • Conversation History now stored in Exchange
    • Media resiliency – Automatic resuming of calls/meeting when momentary network interruptions occur

     

     Product

     Version

    KB

    Download

    Lync for Mac

    14.0.10

    3007876

    MS download

    This update resolves the following issues:

    •     3007886 Update enables users to view call history in Lync for Mac 2011
    •     3007885 Update for Lync for Mac 2011 enables users to store conversation history on an Exchange server
    •     3007884 Location is not displayed in Lync for Mac 2011 when users join a wireless network
    •     3007883 Error "One or more selected contacts cannot receive your calls" when you forward calls in Lync for Mac 2011
    •     3007881 Delegation relationship is broken after a delegate signs in to Lync for Mac 2011
    •     3007879 Computer shutdown is not processed when Lync for Mac 2011 is running
    •     3007878 Update implements media resiliency mode in Lync for Mac 2011
    •     3007877 Dial pad disappears when a user who is not enabled for EV joins a video conference or a video call in Lync for Mac 2011
    •     2909659 Update enables users to interact with a contact from the call history in Lync for Mac 2011
  • [Microsoft Lync Server 2013] Magic Quadrant for Corporate Telephony 2014

    Microsoft est classé pour la première fois dans les leaders par le Magic Quadrant for Corporate Telephony paru le 21 octobre 2014:

    Le rapport est disponible ici: http://www.gartner.com/technology/reprints.do?id=1-23HXCI1&ct=141022&st=sb

    Comment fonctionne le quadrant: http://www.gartner.com/technology/research/methodologies/research_mq.jsp

    On note les points encourageants suivants:

    “Telephony platforms are migrating to software-based solutions that are tightly integrated within a UC suite.” 

    “Enterprises looking to upgrade legacy systems can use this research to decide whether to stay with an incumbent vendor or consider alternative suppliers.”

    Dans les “Cautions”, on retrouve des conclusions qui enfonces des portes ouvertes:

    ” Gartner clients report challenges in providing high availability with Microsoft Lync for basic telephony. Poor call quality, dropped calls and system outages plague some implementations that did not utilize a qualified Microsoft Lync integrator.”

    Je doute que les entreprises choisissant de déployer un système de communication unifiée Avaya ou Cisco choisissent un intégrateur spécialisé infrastructure (AD, Exchange, Sharepoint,...), ils font affaire avec des professionnels de la téléphonie, il doit en être de même avec Lync.


    Du chemin qui reflète l'intérêt croissant des entreprises pour Lync que l'on constate dans notre quotidien d'intégrateur.

    Belle évolution depuis les trois derniers rapports:

    2011:

    2012:

    2013:

  • [Microsoft Lync Server 2013] Web Apps Server Removal from Download Center

    A partir du 24 novembre, microsoft vient d'annoncer que Office Web Apps ne sera plus disponible sur le centre de téléchargement Microsoft, l'application sera disponible pour les clients ayant un agrément Volume Licensing.

    Décision accessible ici: http://blogs.technet.com/b/office_sustained_engineering/archive/2014/10/22/web-apps-server-removal-from-download-center.aspx

    Description:

    As of 11-24-2014 Office Web Apps Server will be removed from the Microsoft Download Center.  At that time it will only be available for download under Volume Licensing agreements.  For more information please read the FAQ below or visit the site Volume Licensing Service Center.


    FAQ

    Why is Web Apps Server being removed from the Microsoft Download Center?

    VLSC is best suited as the location from which to serve all customers according to their agreements with Microsoft.

    What about existing installations?  Do I need to re-license them?

    No.  Existing Web Apps Server installations will continue to be licensed for free viewing.

    Will there be an evaluation version for Developers and IT Pros?

    Evaluation availability will continue on MSDN for subscribers.  Additionally, Volume License agreements allow for product evaluation.

  • [Microsoft Lync Server 2013] Lync KHI importer

    Venant aussi des galleries Technet, un script intéressant est le Lync KHI importer de wilfried van oosterhout

    CQM est une méthodologie pour Lync 2013 et 2010 qui vous aide à trouver et éliminer les problèmes qui affectent la qualité de l'appel et l'expérience utilisateur dans les implémentations voix.

    Johan a fait un super boulot décrivant l'utilisation de cette méthodologie dans une série d'article disponible ici: http://blog.enowsoftware.com/solutions-engine/bid/186171/Lync-Call-Quality-Methodology-to-enhance-the-Call-Quality-and-User-Satisfaction-Part-I-CQM

    Lync KHI importer vous permet d'importer automatiquement les résultats du script “Create_KHI_Collection.ps1”

    L'outil est disponible ici: https://gallery.technet.microsoft.com/Lync-KHI-importer-0c1dbfa5

    Description:

    he script will read CSV files that are created with the Lync 2013 KHI script: Create_KHI_Collection.ps1

    It will process the CSV files and put the data in the by Microsoft supplied excel sheet: Lync_Server_2013_Key_Health_Indicators.xlsx

    A csv file is required for input. The csv file should contain all the files you want to process with the corresponding servertype.

    The servertype can be any off the following:

              1 Lync Front-End Server

              2 Lync Mediation Server

              4 Lync Front-End Server collocated with meditation server

              8 Lync Edge Server

            16 SQL Back-End Server

     

    For every CSV file a new entry is added to the sheets in the excel sheet Lync_Server_2013_Key_Health_Indicators.xlsx. Existing data is preserved.

    Some servers have multiple NICs, multiple drive letters etc. The script will calculate the maximum/average of each of the similar items
    e.g. NICs and will take the highest maximum/average value of these.

     

    Example how to use the script

                    import_khi_data.ps1 -CSVFile <csvfile> -KHIFile <excelfile>

                    Will run the script and only uses the servername from the csv files for identifying the servers in the Excel sheet

                    import_khi_data.ps1 -CSVFile <csvfile> -KHIFile <excelfile> -SingleServer

                    Will run the script and uses the servername + date section from the csv files for identifying the servers in the Excel sheet.

                    This is helpfull if you are doing an analysis over a period of time for a single server.

     

    Requirements on the system were the script is run:

       Excel 2010
       Powershell
       Lync_Server_2013_Key_Health_Indicators.xlsx (can be downloaded here: http://go.microsoft.com/fwlink/p/?LinkID=390677)

       How to setup KHI is well explained on the web for instance here:  http://guybachar.wordpress.com/2014/05/28/how-to-use-lync-key-health-indicators/

  • [Microsoft Lync Server 2013] Optimizing VVX deployment with pre configured configuration files

    Les gallery de technet sont une mine d'or pour les intégrateurs.

    Un partage intéressant fait par Thamara.Wijesinghe qui vous fourni les fichiers de configurations de bases pour un déploiement de masse Polycom VVX.

    Vous pouvez les télécharger ici: https://gallery.technet.microsoft.com/Optimizing-VVX-deployment-83684920

    In this article, I have shared a set of pre configured and optimized .cfg files that can be used with any Lync server deployment. Granted that some of the parameters need to be changed according to the environment and I will explain what need to be changed and why.

    There are 6 configurations files all together which address different segment of the device configuration.

    Starting with Device.cfg. This configuration file set to configure following parameters in VVX device,

    • Set Device Base Profile as Lync
    • Change default administrator password (In version 5.1.1 Revision B, Device comes up with warning message if the Administrator password remains as default)
    • Enable Device update
    • Specify device update location
    • Time server configuration

    The Feature.cfg file specify the common set of features on the device such as, Call lists, Miss call alerts, Contact Directory. In this file, the specified parameters are below,

    • Removed the “Corporate Directory” option on the device. Within “Directory”, the device will have “Lync Directory” option so that the contacts can be searched and called. In many cases, I have seen users get confused with two different set of directory options hence removing the “Corporate Directory” option
    • URI Dialling disabled. VVX generally have URI dialling enabled. When this feature is enabled, all inbound and outbound calls display as the full SIP URI (sip:+6123456789@contoso.com.au). Users who are used to have legacy PBX end points does not like this at all. They want to see just the number or the name without any other information

    Sip-Interop.cfg is the most important one. This one controls the device registry intervals as well as the SIP Proxy server related parameters. In this configuration file, most of the parameters haven’t changed. But, the ones that were changed are below,

    • Device registration expiry interval. Default device registration expiry interval is 3600 seconds. If the devices is registered in an SBA, then if the SBA goes down, the devices still shows as signed in but, it actually be in an unknown condition till the registration expires. Have 3600 seconds is too much in that scenario. In this configuration file, the interval has changed to 120 seconds. This cannot be less than that. If it’s less, then users will experience the frequent device sign in and sign out.
    •   VOIP Server configuration. Here, the VOIP server interoperability is set to Lync 2010 and the transport method is set to TLS.
    • SDP early media disabled. I have noticed when this parameter is enabled, device sometimes does not provide a ringing tone to the end user. The dialled call will be blank till it get picks up.
    • Apply Digitmap Locally. Enabling this parameter will make the device to adhere to the Lync server normalization rules which are assigned to the user.

    The Site.cfg file is configured to set daylight saving time in to the device. If the daylight saving is applicable, the start and stop times need to be configured,

    • SNTP address of the time Server
    • Daylight saving enable or disable. If enabled, start and stop times

    Lync.cfg file configured to set BToE enabled. But, in version 5.1.1 Revision B, Polycom have set the BToE as disabled and given that the configuration file version is 5.2, this configuration file doesn’t really enable BToE on version 5.1.1 Revision B firmware. But, it can be used on Version 5.2.

    The Cer.cfg is set to import the root CA in to the device. 90% of the devices that I have deployed were able to get the certificate without uploading manually. In case the device fail to pick up the certificate, copy and paste the hash file of the CA certificate in to the configuration parameter.

    Finally, the Master configuration file 000000000000.cfg. All the above mentioned configuration files are specified in this master configuration file. When the device boots up, it will fetch the configuration mentioned on this files and get configured based on parameters which are configured on each sub configuration file.

  • [Microsoft Lync Server 2013] Audiocodes IP Phone - Firmware 2.0.7

    Avec la version 2.0.7 pour les modèles 400HD, 420HD et 440HD, Audiocodes supporte officiellement le BTOE.

    Les fonctionnalités disponibles dans cette version:

    - Boss Admin

    - Better Together over Ethernet

    - Automatic mass provisioning and management using the Audiocodes Element Management System

    - New Acoustic Echo Canceller

    - New ways of dialing

    Release notes et firmware disponible ici: http://www.audiocodes.com/downloads


    Un step by step pour le btoe est a venir très rapidement sur mon blog.