Le Cloud de Christophe BOUCETTA

Voici le blog sur les communications unifiées et la collaboration Microsoft par un MVP nominé depuis 11 ans
  • [Skype for Business] Bulletin de sécurité Microsoft MS15-104

    Le bulletin de sécurité Microsoft MS15-104 du 8 septembre 2015 concerne directement Skype pour entreprise et Lync Serveur 2013:

    Cette mise à jour de sécurité corrige des vulnérabilités dans Skype Entreprise Server et Microsoft Lync Server. La plus grave des vulnérabilités pourrait permettre une élévation de privilèges si un utilisateur cliquait sur une URL spécialement conçue. Un attaquant devrait convaincre l'utilisateur de cliquer sur un lien dans un message instantané ou un message électronique qui le redirige vers le site web affecté par le biais d'une URL spécialement conçue.

    Cette mise à jour de sécurité est de niveau « Important » pour toutes les éditions prises en charge de Skype Entreprise Server 2015 et Microsoft Lync Server 2013. Pour plus d'informations, consultez la section Logiciels concernés.

    Cette mise à jour de sécurité corrige les vulnérabilités en mettant à jour jQuery dans Skype Entreprise Server et Lync Server pour nettoyer correctement les entrées utilisateur et en modifiant la manière dont Skype Entreprise Server et Lync Server nettoient les entrées utilisateur. Pour plus d'informations sur les vulnérabilités, consultez la section Informations par vulnérabilité.

    https://technet.microsoft.com/library/security/MS15-104

    KB pour Skype for Business et Lync Serveur 2013: https://support2.microsoft.com/kb/3089952/en-us?sd=rss&spid=924

    This security update resolves vulnerabilities in Skype for Business and Microsoft Lync Server. The most severe of these vulnerabilities could allow elevation of privilege if a user clicks a specially crafted URL. An attacker would have to convince users to click a link in an instant messenger or email message that directs them to an affected website by way of a specially crafted URL. To learn more about the vulnerability, see Microsoft Security Bulletin MS15-104.

  • [Skype] Skype redessinée pour Android, iPhone et iPad

    Microsoft a publié une nouvelle version de skype mobile redessinée pour Android, iPhone et iPad.

    Android: https://play.google.com/store/apps/details?id=com.skype.raider

    iPhone: https://itunes.apple.com/in/app/skype/id304878510?mt=8

    Version: 6.0

    Nouveautés:

    ·   Beautiful redesign - built for iPhone.
    ·   New simple navigation, making it easier to use the Skype features you love.
    ·   More powerful search, so you can quickly find conversation content, groups and contacts.
    ·   Better multi-tasking - easily switch between your call and chat screens to share photos, web links, your location and more while you talk.

    iPad:  https://itunes.apple.com/app/skype-for-ipad/id442012681

    Version 6.0:

    Nouveautés:

    ·    Beautiful redesign - built for iPad.
    ·    New simple navigation, making it easier to use the Skype features you love.
    ·    Tons of new features, including location sharing, new large animated emoticons, starting groups and chats, interacting with notifications, and sharing and receiving photos more easily.
    ·    Automatically add contacts from your iPad address book
    ·    More powerful search, so you can quickly find conversation content, groups and contacts.
    ·    Better multi-tasking - easily switch between your call and chat screens to share photos, web links, your location and more while you talk.


    Vous pouvez trouver une review ici :http://blogs.skype.com/2015/09/03/skype-redesigned-for-android-iphone-and-ipad/


  • [Cisco UC] Backup DRS

    Basiquement, le Disaster Recovery System (DRS) assure la sauvegarde complète des données et des capacités de restauration pour tous les serveurs d'un cluster Cisco Unified Communications Manager, vous pouvez effectuer des sauvegardes de données planifiées ou les invoquer manuellement.

    DRS effectue une sauvegarde de l'ensemble des serveurs du cluser dans un emplacement central.

    Les sauvegardes inclut les composants suivants:

    •     Platform
    •     Music On Hold (MOH) Audio Files
    •     BAT Bulk Provisioning Service (BPS)
    •     CCM Preference Files (CCMPREFS)
    •     TFTP Phone device files (TFTP)
    •     SNMP Syslog Component (SYSLOGAGT SNMP)
    •     SNMP CDP Subagent (CDPAGT SNMP)
    •     Trace Collection Tool (TCT)
    •     Cluster Manager (CLM)
    •     Cisco Extended Functions (CEF)
    •     Reporter

    Comment procéder?

    Connectez vous sur la page Disaster Recovery System avec vos informations d'informations de l'OS.

    Sélectionner Backup > Backup Device et faire Add New:

    Précisez les informations de serveur SFTP:

    Vous pouvez lancer un backup manuel en sélectionnant Backup > Manual Backup:

    Lors du premier backup, vous ne pouvez pas utiliser l'option d'estimation de la taille de la sauvegarde.

    Sauvegarde finalisée:

    L'option d'estimation vous fourni les informations suivantes:

    Note cisco: Be aware that the calculated size is not an exact value but an estimated size of the backup tar. Size is calculated based on the actual backup size of a previous successful backup and may vary if the configuration changed since the last backup.

    Note cisco: Be aware that if no backup history exists for one or more of the selected features, Cisco Unified Communications Manager cannot estimate the size of the backup tar.

    Vous pouvez créer jusqu'à quatorze planifications de sauvegardes. Chaque planification ayant ces propres propriétés, caractéristiques et emplacement de stockage.

    Naviguez dans Backup > Scheduler et faire Add New.

    Préciser le nom de la planification (non modifiable ensuite), le nom du périphérique de sauvegarde crée précédemment (1ere étape).

    Définir la planification des dates, temps et répétition.

    Aprés avoir sauvegardé, ne pas oublier de cliquer sur "Enable Schedule"

  • [Cisco UC] Troubleshooting avec TranslatorX

    Dans le cadre d'intégrations ou de projet full Cisco, je suis régulièrement amener a devoir faire du troubleshooting.

    Je me rends compte a chaque fois que peu de client connaisse (et donc n'utilise pas) TranslatorX

    J'ai déjà fait une introduction de cet outil ici: http://microsofttouch.fr/default/b/christophe/archive/2014/04/30/cisco-unified-translatorx

    Vous pouvez télécharger le client ici: http://translatorx.org/downloads.html

    Au moment de l'article, les versions suivantes sont disponibles:


    Comment utiliser TranslatorX?


    1- Configurer les traces dans votre cucm:

    Aller dans Serviceability -> Trace -> Configuration

    Sélectionner:

    Définir le niveau de log a "Detailed". Si vous souhaitez faire une trace SIP, sélectionner la case "Enable SIP Stack Trace"

    2- Connexion avec le client RTMT pour télécharger les fichiers de log:

    Aller dans Trace & Log Central -> Collect Files et séléctionner Cisco Callmanager


    Ne rien sélectionner dans System Services/Applications.




    Séléctionner la plage de temps souhaitée:

    3- Importer les traces dans TranslatorX:

    Simplement un drag and drop des fichiers de logs collectés dans l'application.

    Décompresser le fichier sdl et importer le dans TranslatorX

    Les traces sont maintenant visible de manière plus conviviale:

    Possibilité d'utiliser des filtres:

    Possibilité aussi de générer des diagrammes de flow:

  • [Skype for Business] Nouveau client syslog audiocodes

    Audiocodes maintenant propose un nouvel outil syslog en lieu et place de Acsyslog120.

    Le nouveau client est Syslog Viewer: http://www.audiocodes.com/products/management-utilities

    Description:

    A comprehensive troubleshooting tool designed to collect, view and analyze syslog messages coming from AudioCodes devices.

    •     High scale real time syslog collection from AudioCodes devices with pause and resume options
    •     Graphical SIP ladder diagrams are displayed on selected SIP sessions
    •     Save syslog messages to a file which can be loaded later for further offline investigation
    •     Formatted color display according to different message severity
    •     Intuitive and yet comprehensive search and filtering
    •     Network impairments resiliency
    •     Connects to multiple devices in real time and shows each device logs in a different tab
    •     Can open and show logs collected also by 3rd party utilities


    L'outil est réellement plus convivial comparativement à l'interface austère de acsyslog:

    Un diagramme des flow SIP est accessible avec la capacité de commuter entre les différentes sessions:


    Il était vraiment temps d'avoir un outil convivial!


    A télécharger sur le site de Audiocodes

  • [Cisco UC] Installer RTMT

    RTMT est un outil puissant et utile dans un environnement de communication Cisco qui permet de vérifier les différentes informations concernant l'état de santé et les performances des systèmes.


    Ou trouver l'application?

    Dépendemment de l'environnement, l'acces au plugin est résumé ci-dessous:

    1/ Diriger vers dans l'interface d'administration a Application - Plugins:

    2/ Seléctionner le téléchargement du plugin en fonction de votre OS:

    3/ Lancer l'installation:

    Accepter l'agrément.

    Séléctionner le répertoire d'installation.

    Répertoire par défaut:

    •Windows—C:\Program Files\Cisco\Unified-Communications-Manager Serviceability\JRtmt

    •Linux—/opt/ Cisco/Unified-Communications-Manager_Serviceability/JRtmt

    L'installation finaliser, vous pouvez maintenant préciser l'IP du serveur souhaité et ensuite préciser vos informations de connexion:

  • [Cisco UC] Modifier le type de vNIC avant une migration

    Dans le cadre d'une migration cisco 8.6 vers 10.5, il est nécessaire de changer le type de carte réseau virtuelle du serveur de "Flexible" a "VMXNET3".

    Dans mon cas, les adresses MAC étant toutes définies en automatique, une opérateur est nécessaire a effectuer dans VMWare pour y parvenir.

    L'état avant la procédure:


    - L'option manuelle:

    Les étapes:

     1/ Naviguer vers l'onglet summary de la VM adéquate, faire un click droit sur le storage volume et choisir "Browse this datastore"



    2/ Selectionner le dossier de votre VM, localiser le fichier vmx, faire un clique droit et télécharge le sur votre poste de travail.



    3/ Faire une copy de ce fichier depuis un cli pour être en mesure de faire un retour en arrière:

    copy "ccm02.vmx" backup_ccm02_temp_file.vmx


    4/ Éditer le fichier vmx pour changer le type à VMXNET3:

    findstr /V /R "^ethernet0.virtualDev.*" backup_ccm01_temp_file.vmx > "ccm02.vmx"
    echo ethernet0.virtualDev = "vmxnet3" >> "ccm02.vmx"

    5/ Importer le fichier vmx NOM dans le datastore en sélectionnant le repertoire de la VM:



    Accepter l'écrasement du fichier d'origine


    6/ Dans la fenetre principale du client vSphere, sélectionner la VM et choisir "Remove from Inventory"


    7/ Retourner dans le navigateur du datastore, selectionner le répertoire de la VM, faites un clique droit sur le vmx NOM, et choisir  "Add to Inventory"



    Conserver le nom d'origine et sélectionner son emplacement

    8/ Vous pouvez maintenant vérifier dans "Edit Settings..", "Network adapter" et valider le type de la carte réseau:

    - Option en powershell VMware:

    1/ Installation des outils VMware vSphere PowerCLI: http://www.vmware.com/support/developer/PowerCLI/


      2/ Depuis le menu Start -> All Programs -> VMware -> VMware vSphere PowerCLI, lancer VMware vSphere PowerCLI

      3/ Connexion au serveur host avec la commande: Connect-VIServer <virtual_machine_host>

    Lors du popup, préciser vos informations de connexions

    L'état en mode connecté:

    4/ La commande suivante permet de modifier le type de la carte: get-vm "<virtual_machine_name>" | get-networkadapter | set-networkadapter -type "vmxnet3"


    5/ Un reload de la machine est nécessaire avec la commande:   Get-View -ViewType VirtualMachine -Filter @{"Name" = "<virtual_machine_name>"} | %{$_.reload()}

    Voilà, tout cela pour se résultat:


  • [Lync Serveur 2013] Mise a jour documentation

    Microsoft a publié hier une mise à jour de sa documentation.

    File: LyncServer2013_ITPro.exe

    Date: 25/08/2015

    Description:

    This download contains a compiled help file (.chm) of all the available Lync Server 2013 IT professional documentation in the Technical Library.

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

  • [Cisco UC] Cisco Prime Collaboration Deployment 11.0

    Précedemment, j'ai déjà écrit trois articles sur la solution 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 Prime Collaboration Deployment est maintenant disponible en version 11.0.1, la release notes est accessible ici: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/PCD/11_0_1/CUCM_BK_R2085610_00_pcd_rns_1101.pdf

    Cisco PCD  a toujours les mêmes 4 principales fonctionnalités:

    • Migrate an existing cluster of Unified Communications servers to a new 11.x cluster (this may be MCS to virtual or virtual to virtual)
    • Perform operations on existing clusters (8.6.1 or higher). Examples of these operations include:
        Upgrade the cluster to a new version of software
        Switch version
        Restart the cluster
    • Changing IP addresses or hostnames in the cluster on existing Release 10.x clusters
    • Fresh install a new Release 10.x Unified Communications cluster

    Support de cette nouvelle version:

    Un step by step a venir bientot pour l'utilisation de cette outil pour la migration de mon environnement vers la version 11

  • [Cisco UC] Prérequis IPSession et Cisco CallManager 10.5.2

    Dans le cadre d'un projet de migration de la téléphonie Cisco Call Manager et Unity connection 8.6 vers 10.5.2, un systeme de paging IPSession de IPCelerate est présent dans le décor, utilisé pour de la pagination vers les différents haut-parleurs et téléphones IP dans les écoles gérées par la commission scolaire.

    La compatibilité des différentes versions de IPSession avec celles des Call Manager est résumé ci-dessous:


    La compatibilités des modèles de téléphones est résumé dans le tableau suivant:

    Les prérequis et recommandations pour la migration vers IPSession 7.1 sont les suivants:

    • Current IPsession version 6.0 – 6.2. If you are running version 5.8 of IPsession; please use the upgrade procedures for 5.8 to 7.1.
    • SQL Server 2005 or 2008 Express must be installed. IPsession 7.X will not work with MSDE or SQL Server Desktop Engine.
    • Disable IIS from running on the windows server.       If IIS is running on the server this will cause the IPsession homepage to fail after the upgrade.
    • Windows Server 2003/2008 latest service pack installed and all critical/important windows updates.
    • During the upgrade you may be prompted to enter the password for the SA user account for SQL Express.
    • If you are running IPsession on a virtual server, take a snapshot before upgrading to 7.X.
  • [Cisco Prime Collaboration Deployment] The Platform Administrative Web Services (PAWS) is not available

    Probleme:

    Lors de la phase de recherche de l'iso de l'application cible à utilisation dans le processus de migration ou upgrade avec Cisco Prime Collaboration Deployment, vous avez l'erreur suivante:

    La documentation Cisco annonce l'information suivante:

    Platform Administrative Web Services (PAWS)

    Error messages:

        "The Platform Administrative Web Services (PAWS) is not available."
        " Unable to access node {0} via the Platform Administrative Web Services (PAWS) interface."

    Possible actions to correct issues:

    Ensure that the server is reachable, and that the PAWS service is active on the node. When you use Cisco Prime Collaboration Deployment to perform an upgrade, switch version, or restart task on an application server (for example, to upgrade a Unified Communications Manager server), the Platform Administrative Web Service on the application must be active. Otherwise, the Cisco Prime Collaboration Deployment server cannot communicate with the Unified Communications Manager application server.

    Solution:

    Option 1: Activate from Serviceability GUI
        Listed under Database and Admin Services
        PAWS service can be activated, started and stopped

    Activez Platform SOAP Services.


    Option 2: Activate from the Command Line Interface (CLI):
        utils service activate Platform Administrative Web Service
        utils service deactivate Platform Administrative Web Service


        To start and stop an already activated PAWS service from the CLI:
            utils service start Platform Administrative Web Service
            utils service stop Platform Administrative Web Service

  • [Skype for Business] Skype for business mobile pour iOS et Android disponible en preview

    Microsoft vient d'annoncer aujourd'hui la disponibilité en preview de la version mobile de Skype for business pour iOS et Android

    Une introduction est accessible ici: https://blogs.office.com/2015/08/11/announcing-the-technical-preview-of-skype-for-business-apps-for-ios-and-android/

    Pour essayer l'application, enregistrez vous ici: https://www.skypepreview.com/

  • [Skype for Business] Exploring Skype Meeting Broadcast

    Il y a quelques mois, j'ai eu la chance de voir les portes s'ouvrir pour publier des articles pour le The Microsoft MVP Award Program Blog.

    Le premier article est publié depuis aujourd'hui: Exploring Skype Meeting Broadcast

    Accessible ici: http://blogs.msdn.com/b/mvpawardprogram/archive/2015/08/11/exploring-skype-meeting-broadcast.aspx

  • [Skype for Business] Cisco Expressway 8.6 supporte le partage de bureau

    Avec la nouvelle release 8.6 de la solution Expressway, Cisco maintenant le partage de bureau avec Lync:

    Description:

    The Expressway now supports desktop or application sharing from Lync clients with conference participants using Cisco Collaboration endpoints.
    The Expressway does the transcoding of the Microsoft Remote Desktop Protocol (RDP), originating from the Lync client, into the Binary Floor Control Protocol (BFCP) used by many standards-based endpoints. The Expressway does not perform the reverse


    Plus d'informations ici: http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/release_note/Cisco-Expressway-Release-Note-X8-6.pdf

  • [Skype for Business] Upgrade d'un firmware Sonus SBC 1000/2000

    Comment mettre a niveau le micrologiciel d'une passerelle Sonus SBC 1000/2000?


    En tant qu'intégrateur, cela est une tâche courant, pour une organisation devant supporter toutes une multitudes de systèmes différents, c'est un point important a aborder dans le cadre d'un transfert de compétence.

    1- Téléchargement du micrologiciel

    Depuis le portail sonus (http://www.sonus.net/en/channel-portal-login), procéder à la demande d'accès au téléchargement de la version de mise à niveau souhaitée:

    Choisir "Request Download"

    Préciser vos informations d'entreprises:

    Apres un temps assez court, vous devriez recevoir la confirmation d'acces par courriel:

    L'accès obtenu, de retour sur le portail, sélectionnez l'applicatif nécessaire à la mise à niveau, sbc1000-release-5.0.0.build395.img dans le cas de cet exemple:

    2/ Mise à niveau du micrologiciel:

    Dans Tasks, Firmware upgrade, il est nécessaire de faire un backup avant de procéder à la mise à niveau:

    Sélectionner le fichier télécharger sbc1000-release-5.0.0.build395.img et faire Upgrade:

    Le processus en 5 étapes commence:

    Redémarrage automatique de la passerelle:

    Dès le retour en activité de la passerelle, vérifiez la version du micrologiciel:

  • [CCIE COLLABORATION] Configuration Jabber

    Parfait pour la préparation du lab du CCIE Collaboration, la vidéo suivante explique le fonctionnement et la configuration du serveur IM et présence

  • [Skype for Business] Skype for Business User Tips & Tricks for Anyone

    Matt Landis a partagé un super document orienté utilisateur: Skype for Business User Tips & Tricks for Anyone

    Téléchargement ici: https://gallery.technet.microsoft.com/office/Skype-for-Business-User-600b52ba

  • [Skype for Business] Configuration QoS dans un environnement sans-fil Cisco

    La technologie AVC (Application Visibility and Control) permet de classifier et prioriser le flux des différents clients lync dans un WLAN

    Technologie utilisant NBAR2 (Based Application Recognition) classifie le flux applicative via une base de signatures, vous pouvez identifier la version de Lync 2013 et également sous-classer les différents trafic (video, audio,...) et appliquer la stratégie adéquate.

    Le trafic sans fil Wi-Fi est identifié par un identificateur d'ensemble de services (SSID). Dans la définition d'un SSID particulier, il ya une plage de classes de priorité d'utilisateur WMM (0-7) qui correspondent à peu près au classe de priorités 802.1Q.

    AVC DSCP marque seulement les paquets originaux dans le controlêur dans les deux directions (upstream and downstream).

    Description (source cisco):

    Upstream

    1. Packet comes with or without inner DSCP from wireless side (wireless client).
    2. AP will add DSCP in the CAPWAP header that is configured on WLAN (QoS based configuration).
    3. WLC will remove CAPWAP header.
    4. AVC module on the controller will overwrite the DSCP to the configured marked value in the AVC profile and send it out.

    Downstream

    1. Packet comes from switch with or without inner DSCP wired side value.
    2. AVC module will overwrite the inner DSCP value.
    3. Controller will compare WLAN QoS configuration (as per 802.1p value that is actually 802.11e) with inner DSCP value that NBAR had overwritten. WLC will choose the lesser value and put it into CAPWAP header for DSCP.
    4. WLC will send out the packet to AP with QoS WLAN setting on the outer CAPWAP and AVC inner DSCP setting.
    5. AP strips the CAPWAP header and sends the packet on air with AVC DSCP setting; if AVC was not applied to an application then that application will adopt the QoS setting of the WLAN.

    Depuis la version 7.6, des applications AVC sont disponibles pour Lync, vous pouvez les trouver dans Wireless - Application Visibility and Control - Profil AVC:

    La configuration est rapide:

    1/ Créer un AVC Profiles et lier les applications AVC suivantes:

    2/ Lier le profil AVC au

  • [Lync Serveur 2013] July 2015 cumulative update 5.0.8308.920 pour Lync Server 2013 UCMA 3.0 Workflow APIs

    Microsoft vient de publier une cumulative update pour Lync Serveur 2013.

    Composant:UCMA 3.0 Workflow APIs

    Version: 5.0.8308.920

    Date: 30 juillet 2015

    Installation:

    To apply this cumulative update, install the UcmaWorkflowRuntime.msp package on computers that are running the following server roles:

    • Lync Server 2013 - Standard Edition Server
    • Lync Server 2013 - Enterprise Edition - Front End Server
    • Lync Server 2013 - Edge Server

    Lien: http://support2.microsoft.com/kb/3070378/en-us?sd=rss&spid=924

  • [Skype for Business] Mise à jour Key Health Indicators pour Lync Server 2013 et Skype for Business Server 2015

    Microsoft vient de publier une mise à jour du package KHI pour Lync Server 2013 et Skype for Business Server 2015.

    Version: 2.0

    File Name: KHI_Resources.zip

    Date Published: 7/29/2015
    File Size: 1.2 MB
    Description:
    An updated version of the Key Health Indicators for Lync Server 2013 and Skype for Business Server 2015. Key Health Indicators (KHI) are Performance Counters with recommended thresholds aimed at revealing problems that can impact the user experience.
    The resources in this download contain the KHI Guide, which outlines the operational process and remediation steps. A sample PowerShell script used to configure KHI Data Collectors. Lastly, the Analysis and Definitions Workbook which can analyze KHI performance data.
  • [Skype for Business] Sonus SBC firmware version 5

    Sonus a publié un nouveau firmware pour les versions SBC 1000/2000:

    Version: 5.0.0

    Nouvelles fonctionnalités:

    ASM Enhancements: The ASM now supports images based on Microsoft Windows Server 2012R2.

    Skype for Business: Sonus SBC 1000/2000 is now certified for Microsoft's Skype for Business.  All existing Sonus 1000/2000 features and Lync 2010/2013 features interoperate with Skype for Business. Also, all features released in Skype for Business are compatible with Sonus SBC 1000/2000.

    Third Party Skype/Lync Presence: The Third Party Skype/Lync Presence feature enables the status of non-Lync endpoints to be communicated on behalf of Lync Clients. Presence will be updated when a call is connected to indicate “On-the-Phone/Busy”. At the end of a call, Presence will be updated to clear the Busy status.

    NTTCom Support: Several enhancements are now included for NTTCom certifications.
        
    NFS Storage: The Sonus 1000/2000 provides storage for the Sonus SBC 1000/2000's internal files. This feature is applicable only if the Sonus SBC 1000/2000 has an ASM module installed.

    NAT Traversal/NTP Latching: The NAT Traversal/NTP Latching feature enables SIP endpoints that are behind NAT routers to register and communicate with the Sonus SBC 1000/2000. This feature handles NAT Traversal for both signaling (SIP) and media (RTP).

    Split DNS: The SBC1000/2000 can now be configured to use a Primary DNS Server, a Secondary DNS Server, and a Domain Specific DNS Server (Split-DNS) to resolve FQDNs.

    Direct Media: Direct Media support for SIP-to-SIP calls enables SIP Signaling to go through the SBC 1000/2000 without media being passed through the SBC. Endpoints on either side are reachable directly and negotiates the codecs and media capabilities, without any need for the SBC support for the media path (audio streams run directly between the endpoints).

    Connected Name Support: Connected Name is now supported in SIP and QSIG ISDN. The SIP Connected Name is derived from the To header.

    Packet Capture: Packet Capture is a new diagnostic feature in the Sonus SBC 1000/2000, which captures IP traffic to troubleshoot problems, such as SIP, AD, etc. Through Packet Capture configuration, select what should be included in the packet capture, such as interface, protocols, media, and hosts.

    Easy Configuration: The Sonus SBC 1000/2000 Web interface now includes a built-in step-by-step setup Easy Configuration wizard, which enables end-users to quickly deploy SBC1000/2000 within a couple of minutes. Depending on the scenario or application in which the SBC is deployed, the Easy Configuration Wizard configures the SBC, Skype for Business/Lync, IP Phones, or ISDN in a very easy manner.
        
    Auto Configuration with BroadSoft Web Services: Sonus SBC 1000/2000 now enables configuration and and updating of SBC 1k/2k remotely from a BroadSoft Server, using SIP NOTIFY message. Configuring, firmware, and software updates are supported. This feature uses password authentication and HTTPS for accessing files, and updates are performed only if required.

    SIP Registration and Subscription WebUI: A new feature has been added to the Sonus SBC 1000/2000 to monitor selected SIP register and subscribe sessions.

    Initial Setup Enhancement: The Initial Setup Enhancement features provides the ability to configure Ethernet 2 in the Initial Setup, along with Additional Routes apart from the Default Route in the Initial Setup Page.

    Alarm and Event History: The Alarm/Event History display provides diagnostics and troubleshooting capabilities for the Sonus SBC 1000/2000 by rendering the latest alarms/events in the system.


    La release notes est disponible ici: https://support.sonus.net/display/UXDOC50/SBC+1000-2000+5.0+Release+Notes

  • [Skype for Business] Cisco WLC et SDN

    Avec la version de firmware 8.1.102.0, les controleurs sans-fil Cisco supporte le SDN Lync:

    Cisco WLC integration with Lync SDN API —This feature enables a Cisco WLC to integrate with a Microsoft Lync Server. Using Microsoft Lync SDN API, the Lync Server sends a notification when a Lync event, such as a voice call, video call, file transfer, or Desktop sharing, occurs on the network. The Cisco WLC interprets the API message, to take the appropriate QoS actions, and provides more visibility (mean opinion score [MOS] or Lync Client Heath) into the Lync events on the wireless network using the Lync SDN dashboard.

    Observation:

    In Cisco Wireless Release 8.1.102.0, Microsoft Lync SDN API 2.0 is supported (with backward compatibility flag set to “true”).

    The Cisco WLC integration with Lync SDN API feature is not supported on Cisco 2504 Wireless Controller.

    Release notes: http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn81.html

    Bulletin: http://www.cisco.com/c/en/us/products/collateral/wireless/8500-series-wireless-controllers/bulletin-c25-734449.html

  • [Skype for Business] Mise à jour Lync pour Mac 2011 - KB3074981 -

    Microsoft vient de publier une mise à jour pour Mac 2011 

    Publication: 24 Juillet 2015

    Version: 14.1.1

    KB3074981: https://support.microsoft.com/en-us/kb/3074981#bookmark-issue

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

    This update resolves the following issues:

  • [Skype for Business] AudioCodes 400HD IP Phone Generic SIP Software Version 2.2.2

    Audiocodes vient d'annoncer la publication d'un nouveau firmware pour les modèles 400HD: AudioCodes 400HD IP Phone Generic SIP Software Version 2.2.2

    Nouveautés:

    • European and American date formats are both now supported. The format is configurable in the phone's LCD as well as in the Web interface.
    • The European date format is DDMMYYYY. The American format is MMDDYYYY.
    • Japanese is now supported. Japanese features three different input modes: Kanji, Hiragana, and Katakana. A submenu for Kanji opens, depending on what base characters are entered.
    • If the receiver is placed on-hook after a call is put on hold, the call is by default put on speaker rather than being disconnected. The default can be changed so that if the receiver is placed onhook after the call is put on hold, the call is disconnected.
    • Icons in the phone's LCD now indicate if line keys are configured in a Shared Call Appearance group, or as private lines. A hollow icon indicates a phone configured in an SCA group. A solid icon indicates a phone configured as private. Applies only to 430HD and 440HD phones.
    • The Restart option is now also available under the 'Settings' menu, as well as under the'Administration' menu.
    • When a phone is in a Multi Line configuration, VOICEMAIL indication per line is now supported.
    • Direct access to MENU key items is now available when pressing the menu item's number. Users can for example press the 4 key on the phone after pressing the MENU key, for direct access to the 'Settings' options (Language, Ring Tone, Call Waiting, etc.).
    • Users are disabled from configuring Programmable Keys as Line Keys. The first two Programmable Keys are by default set to lines. The other four Programmable Keys are by default empty. Users cannot configure all six as Line Keys, neither in the phone LCD nor in the Web interface. The option to assign a line (SIP account) is removed. Applies only to 430HD and 440HD phones.
    • BroadSoft
      • 'Forward No Reply' timeout is now also configurable as 'number of rings' by configuring the ini file parameter 'voip/line/0/call_forward/timeout_mode' to RINGS_COUNT instead of to the default SECONDS. If configured as RINGS_COUNT, the phone will by default ring 2r (2 rings) before the call is forwarded. The setting can be changed according to user preference to (for example) 4r (4 rings). The feature allows compliance with BroadSoft's Feature Key Synchronization method.
      • The local 'Forward' functionality accessed from the phone's LCD idle screen when Feature Key Synchronization is disabled, can also be configured as rings or seconds in the same way.
    • A new format has been applied to the 'user agent' values, and new hardware information has also been added, namely, '-RevX' string. Previously, the 'user agent' value was AUDC-IPPhone/2.0.8.49 (420HD; 00908F480AFC).

    The following information has been added to it:
    • Exact model and Rev (added to the 420HD model running on DSP AC494 with a fast clock)
    • AUDC-IPPhone/2.0.8.49 (420HD-RevX; 00908F480AFC) (resistors information, added to the
    420HD model)
    • AUDC-IPPhone/2.0.8.49 (420HD-RevX-AC494; 00908F480AFC) (added to the 420HD model)


    Problèmes connus:

    • 420HD IP phone: Upgrading from a version earlier than 2.0.2.22 forces a Restore to Default. To upgrade to version 2.2.0 without losing the phone's configuration, a “via version” called 420HD_2.0.2.22.6 can be used. This file is available from: ftp://vop-c11:IPP420@ftp.audiocodes.com/Release/420_via_ver/
    • Phone tone volumes revert to their default values after a firmware upgrade is performed.
    • TR-069: The phone supports TR-098 (Internet Gateway Device Data Model for TR-069) instead of TR-181 (Device Data Model for TR-069).
    • Incoming DTMF tones are played at 300 ms (hardcoded value) via SIP INFO, instead of ideally being set according to the 'Duration' field in the incoming SIP INFO packet.
    • When in an existing call, you cannot make a second call by dialing via the Call Log and Corporate/Personal Directory.
    • 430HD/440HD IP phones: The phone's Dialed Calls screen is sometimes updated incorrectly; new calls are displayed lowermost in the list of Dialed Calls.
    • The Multicast Group Paging doesn’t function correctly in this version.
    • BroadSoft environment:

    • When 'SIP Proxy' and 'Default Gateway' are configured with an IP address instead of a Hostname, the Blind Transfer feature does not function correctly.
    • Feature Key Synchronization - the Call Forward and Do Not Disturb functionalities can be configured from the BroadSoft Server Web Interface or from the phone's LCD screen; however, they cannot be configured via the phone's Web interface.
    • Shared Call Appearance - the user cannot toggle between two incoming calls using Programmable Key 1 and Programmable Key 2. Toggling can only be performed using the
    Navigation Key.

    • It is recommended to configure 802.1x EAP-TLS from the configuration file and not from phone UI.
    • Asterisk environment only – When the phone has an active call and the call is placed on hold, the caller may hear the remote party speaking while the call is still on hold.
    • 420HD – In rare scenarios, the phone UI may show an existing call in the LCD in Idle mode, although the call has ended.HTTPS provisioning is not supported when server-side authentication (mutual authentication) is enabled.
    • Reporting Quality of Service Events:

    • The SIP PUBLISH message doesn’t function correctly in a Conference call (Conference holder or remote parties).
    • The SIP PUBLISH message doesn’t function correctly when two concurrent calls exist.
    • A DNS A query is sent instead of an SRV query with priorities ignored.
    • The Jitter buffer increases when Music On Hold is played.

    • After TCP (TLS) retransmissions, the device (only SIP 100 phones) is unanswered and no failover or any other frame is sent. The device's LED flashes blue, indicating that it is trying to register.
    • In some environments, the phone may send a request for a new IP address once every three DHCP lease time cycles.

    Résolve les problèmes suivants:

    • The calling party now hears a busy tone if the called party's line is busy. Previously, if the called party's line was busy, the calling party's phone's LCD reverted to idle without any indication that the called party's line was busy. The new busy tone complies with international telcom standards in traditional non-VOIP telephony systems.
    • BroadSoft environment:

    • Automatic switching is now implemented by default, i.e., users do not need to press the 9 key, for example, in order to "get an external line", they dial directly the number of the party they want. To allow the feature, the ini file parameter 'voip/dialing/secondary_dial_tone/enabled' is by default now set to 0 and the Web interface parameter 'Secondary Dial Tone' to Disable. Manual switching is implemented if the default is changed, i.e., users will need to press the 9 key, for example, to get a line to outside the enterprise; after pressing the key, they'll hear a secondary tone, and then they'll dial the number they need.
    • When using the new 'Populate the BLF List' feature, the phone couldn't acquire more than 12 extensions on the BLF Resource List, or couldn't acquire 12 or fewer extensions which were too long.
    • Multiple lines configuration - only the first line could use Remote Conferencing. Other lines could only use Local Conferencing.
    • When canceling a "Remote Conference" call, the phone continued to ring after the call had ended (Idle mode).
    • Failover: Phone did not diagnose the 50x SIP message response as "timeout". This did not result in a retry as it should have.

    • Drop From Conference failed when the first call to the originator was incoming and the second outgoing.
    • ACD-Hoteling (420HD only): After recovering from LAN link failure, the phone displayed the host name and not the agent username.
    • When using Handsfree mode and both parties tried to end the call together, one side would get a dial tone (their speaker would be activated and they'd need to deactivate it).
    • 802.1X - after reconnecting the LAN cable, the phone didn't perform CDP/LLDP.
    • When disconnecting an Ethernet cable and then connecting it again, the phone did not send an HTTP request to the provisioning HTTP server.
    • CWRR (Call Waiting Reminder Ringtone) did not ring when the call to the third party was regretted (before the third party answered) and the phone returned to the call on hold.
    • Calling a non-existent number caused an "automatic disconnect" instead of a busy tone. As a result, users missed the reason why the call failed to establish.

    • The clock shown in the phone's idle screen was incorrect when using AM/PM format.

    • A DNS SRV query was not sent when using any UDP port except the default port (5060).