Il est temps pour moi de me reposer un peu, ce post pour vous informer que l'activité du blog reprendra à mon retour de vacances le 7 septembre.

Merci pour votre fidélité.

Microsoft vient de publier des mises à jours pour l'édition Lync Phone:

This cumulative update resolves the following issues:

• 2988196

  (http://support.microsoft.com/kb/2988196/ )

  The lock feature does not prevent users from making calls on a Lync Phone Edition telephone
• 2988195

  (http://support.microsoft.com/kb/2988195/ )

  Incoming call from a PSTN number is disconnected when you put the call on hold on a Lync Phone Edition telephone
• 2988193

  (http://support.microsoft.com/kb/2988193/ )

  Update enables users who are not enabled for UC or EV to sign in to Lync Phone Edition telephone
• 2988192

  (http://support.microsoft.com/kb/2988192/ )

  Receive incorrect message when you call a user whose line is busy on a Japanese version of Lync Phone Edition telephone

J'apprécie les outils qui permettent de se simplifier la vie, Anthony Caragol vient d'en partager un nouveau: Lync 2013 Common Area Phone Management Tool

Cet outil permet d'offrir une interface graphique afin de gérer les téléphones de zones communes.

Description:

I created this tool to allow you to add, modify, and remove Lync common area phones with an easy to use graphical front end.  This functionality is not available within the Lync Control Panel and even modifications via the Lync Management Shell can be difficult or time consuming.

Because this is the initial release of the tool, you may find bugs and not all errors are being caught.  Before you rate this, if you find any issues or have any usability improvements, please suggest them in the Q/A section and I will address them.  If you like it right out of the box, please rate it with 5 stars.  :)

My own future thoughts for improvement include a multi-select mode where you could select multiple phones and modify them as a group.  Let me know if you'd like to see this implemented.

This tool will load fastest when triggered from a Lync Management Shell prompt.  As with any free tool you find on the Internet, use at your own risk.

Téléchargement ici: http://gallery.technet.microsoft.com/lync/Lync-2013-Common-Area-57bc4ff1

Suite à la mise à jour publiée hier par Microsoft (KB2881070): http://microsofttouch.fr/default/b/christophe/archive/2014/08/12/microsoft-lync-server-2013-lync-2013-august-2014-update.aspx, deux nouveaux paramêtres sont disponibles dans la configuration des stratégies clients: DefaultEnableIMAutoArchiving et DefaultEnableCallLogAutoArchiving

Commande:
Set-CsClientPolicy –Identity global –DefaultEnableIMAutoArchiving $false –DefaultEnableCallLogAutoArchiving $false

Description:

This article describes an update for Microsoft Lync 2013 that adds the DefaultEnableIMAutoArchiving and the DefaultEnableCallLogAutoArchiving in-band settings for a client policy. After you install this update, the following check boxes can be set to be unselected as default in Lync 2013. Additionally, an endpoint user can select or click to clear the check boxes in the Lync 2013 client.

• The Save IM conversation in my email Conversation History folder check box
• The Save call logs in my email Conversation History folder check box

Lien: http://support.microsoft.com/kb/2981750

Microsoft vient de publier des mises à jour pour le client Lync 2013:

Nouvelle version: 15.0.4641.1000

KB2881070:

• 2985514

  (http://support.microsoft.com/kb/2985514/ )

  Lync 2013 signs out and then signs in every 30 minutes
• 2985513

  (http://support.microsoft.com/kb/2985513/ )

  Lync 2013 crashes when you manipulate a pivot table field during an Excel worksheet presentation
• 2985512

  (http://support.microsoft.com/kb/2985512/ )

  Error "Event ID from source Lync cannot be found" instead of event logs from Lync 2013 appears in Event Viewer
• 2981755

  (http://support.microsoft.com/kb/2981755/ )

  Cannot join a meeting by using Lync 2013 when the ACP MCU services are running on multiple front-end servers
• 2981754

  (http://support.microsoft.com/kb/2981754/ )

  Cannot send CER data when a user cannot join meetings in Lync 2013
• 2981753

  (http://support.microsoft.com/kb/2981753/ )

  Lync 2013 meeting issues after you install Lync Meeting Add-in for Office 2013
• 2981752

  (http://support.microsoft.com/kb/2981752/ )

  Cannot select audio device during a VoIP call in Lync 2013 when a user is enabled for RCC
• 2981751

  (http://support.microsoft.com/kb/2981751/ )

  Lync 2013 does not display telephone number of an Outlook 2010 contact in the contact card
• 2981750

  (http://support.microsoft.com/kb/2981750/ )

  An update enables Lync 2013 users to select the default unselected check boxes for saving instant message and call logs
• 2981749

  (http://support.microsoft.com/kb/2981749/ )

  Artifacts remain in chat input area in Lync 2013 after an instant message is sent
• 2981748

  (http://support.microsoft.com/kb/2981748/ )

  Lync 2013 dials the number that calls are forwarded to instead of the last dialed number
• 2981747

  (http://support.microsoft.com/kb/2981747/ )

  A user's work number is listed in the "Forward Calls To" list in Lync 2013
• 2981746

  (http://support.microsoft.com/kb/2981746/ )

  Cannot paste data from a webpage to Lync 2013 conversation window
• 2981745

  (http://support.microsoft.com/kb/2981745/ )

  Can’t join online meeting that is created in a non-federated organization by using Lync 2013
• 2981743

  (http://support.microsoft.com/kb/2981743/ )

  Can't sign in to Lync 2013 by using a cached certificate in Lync online hybrid deployment

KB2881083:

Note To resolves these issues, after you install the update KB2881083, you must also install the following update KB2881070 for Lync 2013:

• 2981753

  (http://support.microsoft.com/kb/2981753/ )

  Lync 2013 meeting issues after you install Lync Meeting Add-in for Office 2013
• 2985514

  (http://support.microsoft.com/kb/2985514/ )

  Lync 2013 signs out and then signs in every 30 minutes

J'ai constaté lors de plusieurs projets différents Lync serveur 2013 avec une intégration non IP avec un ou des PBX existants, le problème suivant:

Lorsqu'un utilisateur Lync reçoit un appel venant d'un téléphone du PBX en intégration non IP, le client Lync mobile notifie l'usager de l'appel entrant, mais avec le mauvais nom d'appelant. L'ensemble des autres clients Lync présente le nom correctement sauf lui. Étrange, le client Lync systématiquement montre le nom du premier contact de la liste de l'utilisateur, nous avons fait des tests avec pleins usagers différents, même constat.

Les PBX sont des Mitel, Avaya et Nortel, les passerelles des Audiocodes ou Dialogic.

Évidemment, on pense tout de suite à un probleme de RNL, mais c'est bien plus que cela.

A part cas exceptionnel, je configure toujours mes environnements voix en me basant sur les préconisations Microsoft concernant le format E.164.

J'ai ouvert un case il y a maintenant 6 mois de cela, après 4 mois d'explication et d'envoi divers de logs, Microsoft a confirmé que cela est un bug, la raison est la suivant

Lorsque le client Lync mobile reçoit l'appel, le symptôme est associé à une routine qui détermine le numéro de téléphone à partir du telURI. Cette routine emploie une expression régulière simple, qui ignore complètement l’extension présente dans le numéro en format E164. Par la suite, la recherche locale effectuée identifiera de manière consistante le même contact.

INFO APPLICATION CUcmpParticipant.cpp/2048:CUcmpParticipant::startRNLQuery()

INFO APPLICATION CUcmpParticipant.cpp/572:tel uri rnl search started

INFO APPLICATION CUcmpConversation.cpp/6986:Add a new participant to active participant collection. sipUri: [tel:+1514XXXXXXX;ext=1111] remoteHref: [/ucwa/v1/applications/...] displayName: [+1 (514) XXX-XXXX] personKey: [/ucwa/v1/applications/...]

INFO APPLICATION CPersonsAndGroupsSearchQuery.cpp/1159:Local search started. queryType=1; lookupKeyword=; lookupUri=; lookupEmail=; lookupPhone=+1514XXXXXXX

INFO APPLICATION CUcmpParticipant.cpp/2187:Displayname from local rnl search is Admin Lync

INFO APPLICATION CUcmpConversation.cpp/2744:tel uri rnl search completed

Je viens d'être notifié aujourd'hui que le bug vient d’être accepté par l'équipe de développement et sera corrigé dans une version ultérieure (reste à savoir laquelle!).

En suivant le lien http://gallery.technet.microsoft.com/office/Lync-Certificates-Reporter-502fefaf vous pouvez trouver un script très pratique vous permettant d'afficher un rapport des certificats présents sur chacun des serveurs dans une page web.

Vraiment pratique, je l'ai utilisé ce matin pour faire le tour de l'existant d'un client souhaitant ajouter la téléphonie dans son environnement.

Description:

The following script will query for every Lync server in the Environment Which is a Registrar, an EDGE or OWAS, and will pull the following information on the certificates exists under the Local Machine:

• Friendly Name
• Issuer
• Thumbprint
• Subject Name
• Issue Date
• Expiration Date
• Expires In (Days)

Script Features:

• The script pulls the information from every server by query the Local Machine container to an HTML report file
• Certificates which are about to expired in the next 30 days will be colored in Red
• The script can also be configured to send email as well as being a scheduled task in order to be notified on a weekly/monthly basis.

The current caveats in this version of the script

• Does not pull EDGE Certificates information
• Does not have Lync Certificates assignment awareness (Does not know which certificate is currently assigned)

Le but de cette article est d'installer un environnement Cisco Unity Connection et de l'intégrer en SIP au cluster cucm 10.5 existant.

1/ Installation Cisco Unity Connection 10.5:

Choisir le fuseau horaire:

Définir le nom du serveur et son adressage:

Activation du DNS:

Indiquer votre serveur DNS et le nom de domaine:

Définir les identifiants d'administrations:

Même principe que lors de l'installation d'un cucm, dans notre cas, le serveur est donc en tant que premier noeud, le publisher:

Préciser vos serveurs NTP:

Préciser le mot de passe de sécurité:

2/ Configuration au niveau du Call Manager:

- Configuration d'une jonction SIP entre le cluster CUCM et Cisco Unity Connection:

Connecter vous sur la page d'administration d'un CUCM, selectionner System- Security - SIP Trunk Security Profile et faire "Add New":

Cocher les options:

Accept presence subscription
Accept out-of-dialog refer
Accept unsolicited notification
Accept replaces header

- Dans le menu Device - Device Settings - SIP Profile, créer un nouveau profil:

Laissez les options par défaut.

Si vous souhaitez activer le monitoring sur le trunk, avec l'option dans le profil SIP:

- Dans le menu Device, séléctionner Trunk et ajouter un SIP Trunk:

Activer l'option Redirecting Diversion Header Delivery – Outbound field.

Dans mon scenario, mon lab inclut un cluster de deux serveurs Unity Connection:

- Configurer une route pattern pour offrir la fonctionnalité de messagerie vocale:

Call Routing - Route/Hunt - Route pattern:

- Déclarer le numéro de la messagerie vocale:

Dans le menu, sélectionner Advanced features - voice mail - voice mail pilot:

et créer ensuite le profile, Advanced features - voice mail - voice mail profile:

3/ Configuration au niveau du Unity Connection:

Dans la page d'administration, sélectionner "Telephony Integrations" - Phone System et cliquer sur PhoneSystem:

Cliquer ensuite sur Add Port Group:

Changer le protocole et préciser l'adresse IP du premier CUCM

Vous pouvez vérifier votre configuration en cliquant sur Check Telephony Configuration:

Fin de cette partie:

N'oublier pas d'activer les services, et il ne reste plus que l'importation ou la création des utilisateurs dans le système pour faire vos tests.

Parfois, sur certains projets, on frappe malheureusement toute une série de bugs, je suis actuellement sur un de ces projets.

Problème:

Dans le cadre de la migration des cucm vers 10.5, on a mis a jour les firmwares des téléphones 7941 et 7942 pour être en conformité avec la matrix de comptabilité Cisco. Problème, si le headset est sélectionné, on ne peut pas transférer les appels....

Cela correspond au bug CSCun26289: Problems transferring/answering calls when using headset with 79XX phone

Symptom:
- When a user attempts to transfer a call, the original call is placed on hold, but the user is not able to dial the transfer destination.
- When a user already has an active call on their phone, they are unable to answer a new incoming call. The original call is placed on hold, and the new call is simply disconnected.

Conditions:
- Using a headset with a 7900 series phone
- Running firmware 9.3(1)SR4

Workaround:
- Do not use a headset
- Rollback to 9.3(1)SR3 or earlier

Le "workaround" n'est pas fantastique, donc il faut que ouvrir un case chez Cisco afin d'obtenir le tout dernier firmware non encore disponible au téléchargement.

Petite erreur de la semaine, rien de méchant, mais étant visible par l'ensemble des utilisateurs.

Début d'un nouveau projet Lync en début de semaine, objectif, remplacer la très ancienne téléphonie des 6 sites par une infrastructure Lync centralisée sur le site principal avec des passerelles Audiocodes SBA dans les sites secondaires. Rien d'innovant, sauf le contexte environnemental du déploiement qui fera l'objet d'un autre article surement.

Le client ayant migré lui même son environnement 2010 vers 2013 trainé l'erreur suivante visible par l'ensemble des utilisateurs depuis un an:

La résolution est simple, même si le pertinent chat est à l'étude mais non déployé pour l'instant, dans la stratégie globale, l'option enable pertinent chat était activée:

Désactiver l'option, déconnexion/reconnexion du client Lync, et plus d'erreur.

La dernière analyse est disponible depuis le 4 aout ici: http://www.gartner.com/technology/reprints.do?id=1-1YWQWK0&ct=140806&st=sb

On peut constater que Microsoft commence à se démarquer par rapport à Cisco pour les critères “Completeness of Vision” et “Ability to Execute”.

Cisco

Cisco offers a full UC suite, as well as a broad range of additional communications functions. Key parts of the UC suite include Cisco Unified Communications Manager; Cisco Jabber, which includes the mobile and desktop client; Cisco Unity Connection; Cisco WebEx, which is now also available as an on-premises server; multiple video options; and a broad range of fixed and mobile client and device options. The vendor's entire portfolio is now offered virtually on VMware, operating on both Cisco Unified Computing System servers and other qualified servers. Cisco offers several virtual desktop integration (client virtualization) options, and offers additional integrated communications and collaboration functionality, including in its contact center, Cisco WebEx conferencing integrated with Cisco TelePresence and via a recent agreement with Jive. Finally, Cisco leverages its UC software into a cloud portfolio branded Cisco Hosted Collaboration Solution (Cisco HCS), which allows Cisco HCS partners to create UCaaS offerings as well as hybrid on-premises-cloud options.

Key additions to the portfolio during the past year include several in the video area, spanning new desktop systems (DX Series), room systems (MX Series), the TelePresence SX10 Quick Set (a rapidly deployed, easily installed room video system), improved packaged offers (Business Edition 6000 for midmarket and Business Edition 7000 for enterprise), and TelePresence Video Communication Server Expressway, allowing teleworkers and remote Jabber users to access services without requiring a VPN connection.

Cisco UC is an attractive solution for midsize, large and multinational corporations requiring strong voice and video capabilities. It is also attractive to enterprises that require full UC client support on leading mobile platforms and on Apple Macs, and those that wish to leverage Cisco's networking infrastructure.

Strengths

• Cisco offers a full UC suite with strong, globally scalable support for IM/presence, video, telephony and multiple conferencing options. Additionally, full UC functionality is available on leading mobile platforms.
• Prime Collaboration provides unified management for voice and video networks including automated, accelerated deployment, provisioning, real-time monitoring, proactive troubleshooting, license management and long-term trending and analytics. Prime Collaboration can scale to 150,000 endpoints per server instance
• Cisco's large data infrastructure client base, along with its strong global channel, service and system integration (SI) partners, position it well within enterprise UC buying and decision-making groups, including many IT and operations departments.
• Through carrier and service provider partners, Cisco is advancing attractive hybrid on-premises and cloud options. HCS is based on the same software as Cisco's on-premises offering, and both support the same Jabber client. Additionally, Cisco has agreements for transferring licenses from on-premises to hosted environments.

Cautions

• Cisco's solution is based on a series of separate products and acquisitions over the years, including Cisco Unified Communications Manager, WebEx, Jabber and Tandberg. One result of this is that some user and administrator experiences are fragmented, rather than seamless.
• Cisco's Unified Workspace Licensing (CUWL) is a useful package to profile user requirements. It offers attractive pricing, compared with buying competitive UC components separately. However, it's important to size requirements accurately based on user needs, in order to avoid overinvesting in capabilities that then go unused.
• The Collaboration Technology Group must advance new and innovative software and a compelling vision for the UCC industry to retain its strong leadership position. However, this may prove challenging as the group must operate within a company, and with channels, that are heavily focused on network-centric architectures and services.

Microsoft

Microsoft Lync offers a full suite of UC functionality that Microsoft continues to improve with each release. It integrates with Office applications, Active Directory and Skype. Microsoft has a broad set of additional business applications that will increasingly be leveraged, including Office Graph (which uses machine learning to define the context and connect users with relevant documents, conversations and people) and Cortana (a digital assistant).

The Lync partner ecosystem expanded at a rapid pace; however, more importantly, the partners' skill level and experience in complex deployments that include voice and video also improved significantly year over year. Lync's improved federation capabilities have proven an effective way for groups to collaborate across organizational boundaries. For cloud delivery, Microsoft offers Lync Online as part of the Office 365 suite, as well as in private cloud configurations; in both cases, partners can be leveraged for telephony. However, enterprises should be aware that Lync Online offers only a subset of the on-premises Lync solution, most notably with limited PSTN connectivity.

Enterprises that have a significant number of employees that can benefit from Lync's collaboration model should consider the Lync solution and understand how it might change their business processes and worker productivity. Enterprises considering deploying Lync telephony or video should understand the topology and infrastructure requirements, how they will support branch offices, and (if relevant) how they will deploy and obtain global third-party support. Enterprises with advanced telephony feature requirements should also ensure that the needed functions are supported.

Strengths

• Microsoft Lync continues to make significant gains in the market and is attractive to a broad range of enterprises. In many cases, it is initially deployed for its IM, presence and Web conferencing functionalities, with gradual incremental deployments of telephony and video added as follow-on phased deployments for specifically targeted groups or regions.
• The vendor has significantly improved its go-to-market strategy for Lync during the last year, positioning itself to more adequately address the real-time communications requirements of enterprises over the next several years.
• Microsoft has added video capabilities, including support for Lync room-based video systems and interoperability of standards-based video endpoints.
• Customers report that Lync functions can be readily integrated into business processes and applications, providing new, different and effective ways to perform tasks. Often, these new functions are achieved by deploying Lync enhancements from a growing list of ecosystem partners.

Cautions

• Few IT managers report that they have completely eliminated their PBXs in Lync implementations. Typically, Lync IM/presence and Web conferencing are deployed across the broader employee base, while telephony is deployed only for a subset of employees. Microsoft's stated telephony strategy is to leverage partners for functions like endpoints, gateways and contact center; therefore, enterprises interested in PBX-level capabilities should be prepared to also invest in a number of partner solutions to achieve advanced functionality.
• Gartner clients report users with non-Microsoft endpoints, such as Mac workstations, are not satisfied with the functionality and quality of the Lync UX.
• Gartner clients deploying Lync with in-house staff often report that multiple partners are required to obtain a complete deployment, and that this poses challenges (for example, different partners for telephones, gateways, servers, remote support and network monitoring); additionally, it can lead to release-level incompatibilities. This can also result in difficulty obtaining an accurate total cost for Lync service and support.
• Some enterprises express concern that Microsoft's bundling, combined with proprietary protocols, will leave them locked in a closed circle of choices. Bundling includes Exchange, Lync, SharePoint, Office, Skype and Yammer. While the video interoperability is a good sign, it also serves to emphasize the lack of standards-based capabilities in the other areas, such as standard SIP endpoints and WebRTC.

Microsoft vient de publier une mise à jour pour Lync Serveur 2013 - cumulative update 5:

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

KB: http://support.microsoft.com/kb/2809243

Cette mise à jour ne comporte aucune nouvelles fonctionnalités

Liste des rôles de serveur et les mises à jour qui s'y appliquent

• Lync Server 2013 - serveur Standard Edition server
• Serveur frontal de Lync Server 2013 - Enterprise Edition - et le serveur principal
• Lync Server 2013 - serveur de transport Edge
• Lync Server 2013 - serveur de médiation autonome
• Lync Server 2013 - serveur directeur
• Lync Server 2013 - Chat persistant le serveur frontal
• Lync Server 2013 - outils d'Administration

Lync Server 2013 - serveur Standard Edition server

• Mise à jour pour les composants principaux: KB 2881682
• Mise à jour pour l'API managée de Communications unifiées 4.0, Core Runtime 64 bits: KB 2881685
• Mise à jour pour le serveur frontal et le serveur de transport Edge (server Édition Standard ou Enterprise): 2881684 Ko
• Mise à jour pour le serveur de conférence: KB 2835434
• Mise à jour pour le serveur de composants Web: KB 2881688
• Mise à jour pour le serveur de conférence Web: KB 2835507
• Mise à jour pour le serveur de médiation: KB 2881699
• Mise à jour pour le Service d'appel Park: KB 2881703

Serveur frontal de Lync Server 2013 - Enterprise Edition - et serveur Back-End

• Mise à jour pour les composants principaux: KB 2881682
• Mise à jour pour l'API managée de Communications unifiées 4.0, Core Runtime 64 bits: KB 2881685
• Mise à jour pour le serveur frontal et le serveur de transport Edge (server Édition Standard ou Enterprise): 2881684 Ko
• Mise à jour pour le serveur de conférence: KB 2835434
• Mise à jour pour le serveur de composants Web: KB 2881688
• Mise à jour pour le serveur de conférence Web: KB 2835507
• Mise à jour pour le serveur de médiation: KB 2881699
• Mise à jour pour le Service d'appel Park: KB 2881703

Lync Server 2013 - serveur de transport Edge

• Mise à jour pour les composants principaux: KB 2881682
• Mise à jour pour l'API managée de Communications unifiées 4.0, Core Runtime 64 bits: KB 2881685
• Mise à jour pour le serveur frontal et le serveur de transport Edge (server Édition Standard ou Enterprise): 2881684 Ko

Serveur de médiation de Lync Server 2013 - autonome

• Mise à jour pour les composants principaux: KB 2881682
• Mise à jour pour l'API managée de Communications unifiées 4.0, Core Runtime 64 bits: KB 2881685
• Mise à jour pour le serveur de médiation: KB 2881699

Lync Server 2013 - serveur directeur

• Mise à jour pour les composants principaux: KB 2881682
• Mise à jour pour l'API managée de Communications unifiées 4.0, Core Runtime 64 bits: KB 2881685
• Mise à jour pour le serveur frontal et le serveur de transport Edge (server Édition Standard ou Enterprise): 2881684 Ko
• Mise à jour pour le serveur de composants Web: KB 2881688

Lync Server 2013 - serveur persistant Front-End conversation

• Mise à jour pour les composants principaux: KB 2881682
• Mise à jour pour l'API managée de Communications unifiées 4.0, Core Runtime 64 bits: KB 2881685

Lync Server 2013 - outils d'Administration

• Mise à jour pour les composants principaux: KB 2881682