De plus en plus, venant aussi du fait de concurrence les challengers habituels de la téléphonie IP, les clients souhaitent être en mesure de surveiller en temps réel l'activité des serveurs Microsoft Lync.

Par surveillance, il est entendu que je fais référence au recueil et l'affichage de toutes les données, des conditions relatives au fonctionnement et au comportement des équipements ainsi que desapplications incluant toutes les informations et les procédures requises pour faciliter
l'entretien et le bon fonctionnement des applications.

Pour une organisation ayant Solarwinds, il existe déjà des templates tout prêt pour effectuer ces tâches pour les rôles suivants:

Front-End: http://thwack.solarwinds.com/servlet/JiveServlet/downloadBody/155345-102-2-2778/Microsoft%20Lync%20Server%20(Front-End%20Role).apm-template

Description: http://thwack.solarwinds.com/docs/DOC-155345

Mediation: http://thwack.solarwinds.com/servlet/JiveServlet/downloadBody/155347-102-2-2779/Microsoft%20Lync%20Server%20(Mediation%20Role).apm-template

Description: http://thwack.solarwinds.com/docs/DOC-155347

Edge: http://thwack.solarwinds.com/servlet/JiveServlet/downloadBody/155346-102-2-2777/Microsoft%20Lync%20Server%20(Edge%20Role).apm-template

Description: http://thwack.solarwinds.com/docs/DOC-155346

Front-End:

Service: Lync Server Audio Test Service

This component monitor returns the CPU and memory usage of the Lync Server Audio Test Service. This service offers users the ability to subjectively test the quality of a call before placing the call. The user checks the call quality by making a test call.

Service: Lync Server File Transfer Agent

This component monitor returns the CPU and memory usage of the Lync Server File Transfer Agent. The File Transfer Agent is responsible for replicating configuration settings with the Replica Replicator Agent that runs on every Lync Server.

Service: Lync Server Front-End

This component monitor returns the CPU and memory usage of the Front-End Lync Server. The Front-End Servers maintain transient information, such as logged-on state and control information for an IM, Web, or audio/video (A/V) conference.

Service: Lync Server IM Conferencing

This component monitor returns the CPU and memory usage of the Lync Server IM Conferencing. The IM Conferencing service is responsible for multiplexing the instant messages data feed from the leader to all participants in the session.

Service: Lync Server Master Replicator Agent

This component monitor returns the CPU and memory usage of the Lync Server Master Replicator Agent. This service is used by File Transfer Agent for replication configuration settings.

Service: Lync Server Replica Replicator Agent

This component monitor returns the CPU and memory usage of the Lync Server Replica Replicator Agent. This service is used by the File Transfer Agent for replication configuration settings.

SIP Peers: Connections Active

This component monitor returns the number of established connections that are currently active. A connection is considered established when peer credentials are verified (e.g. via MTLS), or the peer receives a 2xx response. You will need to baseline this counter by testing and monitoring the user load. This returned value should be less than 15,000 connections per Front-End.

SIP Peers: TLS Connections Active

This component monitor returns the number of established TLS connections that are currently active. A TLS connection is considered established when the peer certificate, and possibly the host name, are verified for a trust relationship. You will need to baseline this counter by testing and monitoring the user load.

SIP Peers: Sends Outstanding

This component monitor returns the number of messages that are currently present in the outgoing queues. If you receive error message 504, investigate the results from this counter. Doing so will indicate which servers are having problems. To do so, you will need to change the instance from _Total, to the server hostname. You can check this within perfmon.exe

SIP Peers: Average Outgoing Queue Delay

This component monitor returns the average time, in seconds, that messages have been delayed in outgoing queues. Check the Outgoing Queue Delay for delays in sending messages to other servers or clients that could be causing messages to be accumulated in the server. The server will drop client connections if it is in a throttle state and messages stay in the outgoing queue for more than 32 seconds.

SIP Peers: Flow-controlled Connections Dropped

This component monitor returns the total number of connections dropped because of excessive flow-control. You will need to baseline this counter by testing and monitoring the server's health. The returned value should be as low as possible.

SIP Peers: Average Flow-Control Delay

This component monitor returns the average delay, in seconds, in message processing when the socket is flow-controlled. You will need to baseline this counter by testing and monitoring the server's health. The returned value should be as low as possible.

SIP Peers: Incoming Requests/sec

This component monitor returns the rate of received requests, per second. You will need to baseline this counter by testing and monitoring the user load.

SIP Protocol: Incoming Messages/sec

This component monitor returns the rate of received messages, per second. You will need to baseline this counter by testing and monitoring the user load.

SIP Protocol: Events In Processing

This component monitor returns the number of SIP transactions, or dialog state change events, that are currently being processed. You will need to baseline this counter by testing and monitoring the user load.

SIP Responses: Local 500 Responses/sec

This component monitor returns the rate of 500 responses generated by the server, per second. This can indicate that there is a server component that is not functioning correctly.

SIP Responses: Local 503 Responses/sec

This component monitor returns the rate of 503 responses generated by the server, per second. The 503 code corresponds to the server being unavailable. On a healthy server, you should not receive this code at a steady rate. However, during ramp up, after a server has been brought back online, there may be some 503 responses. Once all users get back in and the server returns to a stable state, there should no longer be any 503 responses returned.

SIP Responses: Local 504 Responses/sec

This component monitor returns the rate of 504 responses generated by the server, per second. A few 504 responses to clients (for clients disconnecting abruptly) is to be expected, but this counter mainly indicates connectivity issues with other servers. It can indicate connection failures or delays connecting to remote servers.

SIP Load Management: Average Holding Time For Incoming Messages

This component monitor returns the average time that the server held the incoming messages currently being processed. This should usually be less than one second, on average, but it is normal to see short spikes of up to three seconds. The server will throttle new incoming messages after going above the high watermark and until the number of messages falls below the low watermark. The server starts rejecting new connections when the average holding time is greater than overload time of 15 seconds.

SIP Load Management: Address space usage

This component monitor returns the percentage of available address space currently in use by the server process. The returned value should be as low as possible.

SIP Load Management: Page file usage

This component monitor returns the percentage of available page file space currently in use by the server process. The returned value should be as low as possible.

IM Conferences: Active Conferences

This component monitor returns the number of active conferences. You will need to baseline this counter by testing and monitoring the user load.

IM Conferences: Connected Users

This component monitor returns the number of connected users in all conferences. You will need to baseline this counter by testing and monitoring the user load.

IM Conferences: Throttled Sip Connections

This component monitor returns the number of throttled Sip connections. If the value is greater than ten, it could indicate that Peer is not processing requests in a timely fashion. This can happen if the peer machine is overloaded. Peer is defined as the connected servers, adjacent Front-End servers, or MCUs in the same EE Pool. The same set of counters apply.

IM MCU Health And Performance: MCU Health State

This component monitor returns the current health of the MCU.

Possible values:
0 = Normal.
1 = Loaded.
2 = Full.
3 = Unavailable.

IM MCU Health And Performance: MCU Draining State

This component monitor returns the current draining status of the MCU.

Possible values:
0 = Not requesting to drain.
1 = Requesting to drain.
2 = Draining.

When a server is drained, it stops taking new connections and calls. These new connections and calls are routed through other servers in the pool. A server being drained allows its sessions on existing connections to continue until they naturally end. When all existing sessions have ended, the server is ready to be taken offline.

User Services - DBStore: Queue Latency (msec)

This component monitor returns the average time, in milliseconds, that a request is held in the database queue. This counter represents the time that a request spends in the queue of the Back-End Database Server. If the topology is healthy, this counter averages less than 100 ms. Occasional spikes are acceptable. The value will be higher on Front-End Servers that are located at the site opposite the location of the Back-End Database Servers. This value can increase if the Back-End Database Server is having performance problems or if network latency is too high. If the returned value is high, check both network latency and the health of the Back-End Database Server. Server health decreases as latency increases to 12 seconds, when server throttling begins.

User Services - DBStore: Sproc Latency (msec)

This component monitor returns the average time, in milliseconds, it takes to execute a stored procedure call. A healthy state is considered to be less than 100 ms. Server health decreases as latency increases to 12 seconds, when server throttling begins.

User Services - Https Transport: Number of failed connection attempts / Sec

This component monitor returns the rate of connection attempt failures, per second. You will need to baseline this counter by testing and monitoring the server's health.

 

Mediation:

Service: Lync Server Replica Replicator Agent

This component monitor returns the CPU and memory usage of the Lync Server Replica Replicator Agent. This service is used by the File Transfer Agent for replication configuration settings.

Outbound Calls: Current

This component monitor returns the total number of active calls going through the Mediation Server.

Outbound Calls: Active media bypass calls

This component monitor returns the total number of active calls going through Mediation Server that are in Media Bypass mode. Calls using Media Bypass use significantly fewer Mediation Server resources because the media is not flowing through the Mediation Server.

Inbound Calls: Current

This component monitor returns the number of inbound calls in progress.

Inbound Calls: Active media bypass calls

This component monitor returns the number of media bypass calls in progress.

Media Relay: Media Connectivity Check Failure

This component monitor returns the number of calls where media connectivity between the Mediation Server and the remote endpoints could not be established. The returned value should be as low as possible.

Health Indices: Load Call Failure Index

This component monitor returns the scaled index between zero and 100 that is related to all call failures due to Global Health Index as a heavy load.

Global Counters: Current audio channels with PSM quality reporting

This component monitor returns the total number of active channels that are having Phase Shift Modulation (PSM) quality reported. Calculating PSM quality has a processing overhead so this should be taken into account when measuring performance.

Total failed calls caused by unexpected interaction from the Proxy

This component monitor returns the number of calls that failed because of an unexpected response from the Front End Server. The returned value should be as low as possible.

Total failed calls caused by unexpected interaction from a gateway

This component monitor returns the number of calls that failed because of an unexpected response from a gateway peer. The returned value should be as low as possible.

Edge:

Service: Lync Server Replica Replicator Agent

This component monitor returns the CPU and memory usage of the Lync Server Replica Replicator Agent. This service is used by the File Transfer Agent for replication configuration settings.

SIP Peers: Connections Active

This component monitor returns the number of established connections that are currently active. A connection is considered established when peer credentials are verified (e.g. via MTLS), or the peer receives a 2xx response. You will need to baseline this counter by testing and monitoring the user load. This returned value should be less than 15,000 connections per Front-End.

SIP Peers: TLS Connections Active

This component monitor returns the number of established TLS connections that are currently active. A TLS connection is considered established when the peer certificate, and possibly the host name, are verified for a trust relationship. You will need to baseline this counter by testing and monitoring the user load.

SIP Peers: Average Outgoing Queue Delay

This component monitor returns the average time, in seconds, that messages have been delayed in outgoing queues. Check the Outgoing Queue Delay for delays in sending messages to other servers or clients that could be causing messages to be accumulated in the server. The server will drop client connections if it is in a throttle state and messages stay in the outgoing queue for more than 32 seconds.

SIP Peers: Incoming Requests/sec

This component monitor returns the rate of received requests, per second. You will need to baseline this counter by testing and monitoring the user load.

SIP Protocol: Incoming Messages/sec

This component monitor returns the rate of received messages, per second. You will need to baseline this counter by testing and monitoring the user load.

SIP Load Management: Average Holding Time For Incoming Messages

This component monitor returns the average time that the server held the incoming messages currently being processed. This should usually be less than one second, on average, but it is normal to see short spikes of up to three seconds. The server will throttle new incoming messages after going above the high benchmark and until the number of messages falls below the low benchmark. The server starts rejecting new connections when the average holding time is greater than overload time of 15 seconds.

SIP Access Edge Server: External Messages/sec With Internally Supported Domain

This component monitor returns the per-second rate of messages received at the external edge with an internally supported domain.

SIP Access Edge Server: External Messages/sec Received With Allowed Partner Server Domain

This component monitor returns the per-second rate of messages received at the external edge with an allowed partner server domain.

SIP Access Edge Server: External Messages/sec Received With a Configured Allowed Domain

This component monitor returns the per-second rate of messages received at the external edge with a configured allowed domain.

A/V Edge UDP: Active Relay Sessions - Authenticated

This component monitor returns the number of active relay sessions over UDP.

A/V Edge UDP: Active Relay Sessions - Allocated Port

This component monitor returns the number of active relay sessions with a UDP port allocation.

A/V Edge UDP: Active Relay Sessions - Data

This component monitor returns the number of active relay data sessions over UDP.

A/V Edge UDP: Allocated Port Pool Count

This component monitor returns the number of UDP ports available in the Allocated Port Pool. This monitor should be more than zero. If it reaches zero there is a resource issue.

A/V Edge UDP: Allocate Requests/sec

This component monitor returns the per-second rate of Allocate Requests over UDP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge UDP: Authentication Failures/sec

This component monitor returns the per-second rate of failed attempts to authenticate with the relay over UDP. The returned value should be as low as possible.

A/V Edge UDP: Allocate Requests Exceeding Port Limit

This component monitor returns the number of allocate requests over UDP that exceeded the port limit. If the value is greater than zero, this could indicate an attempt to misuse the port.

A/V Edge UDP: Packets Received/sec

This component monitor returns the number of packets, received per second, by the relay over UDP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge UDP: Packets Sent/sec

This component monitor returns the number of packets sent per second by the relay over UDP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge UDP: Average Data Packet Latency (milliseconds)

This component monitor returns the average latency for a valid data request over UDP in milliseconds. The returned value should be as low as possible.

A/V Edge UDP: Packets Dropped/sec

This component monitor returns the per-second rate of packets over UDP dropped by the relay. The returned value should be as low as possible.

This error occurs when an unexpectedly high rate of User Datagram Protocol (UDP) packets is received at the Media Relay (A/V Edge server)  causing some packets to be discarded. This could be the result of system overload or an indication of an attempt to misuse the MR.

To resolve this, check that the profile of network traffic to the MR is in line with expected usage. If the traffic exceeds 250 Mbps per interface, increase the Receive and Transmit buffer size on the associated network adapter network adapters to three times the default values.

If the cause is a general system overload, increase the capacity of the deployed MR function. A network level trace can be used to determine if there is an unusual amount of traffic originating from a single source. If the situation persists, enable tracing to check the network source of sessions exceeding the bandwidth limits to allow further troubleshooting of the cause.

A/V Edge TCP: Active Relay Sessions - Authenticated

This component monitor returns the number of active relay sessions over TCP.

A/V Edge TCP: Active Relay Sessions - Allocated Port

This component monitor returns the number of active relay sessions with a TCP port allocation.

A/V Edge TCP: Active Relay Sessions - Data

This component monitor returns the number of active relay data sessions over TCP.

A/V Edge TCP: Allocated Port Pool Count

This component monitor returns the number of TCP ports available in the Allocated Port Pool. This monitor should be greater than zero. If zero is reached, a resource issue exists.

A/V Edge TCP: Allocate Requests/sec

This component monitor returns the per-second rate of Allocate Requests over TCP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge TCP: Authentication Failures/sec

This component monitor returns the per-second rate of failed attempts to authenticate with the relay over TCP. The returned value should be as low as possible.

A/V Edge TCP: Allocate Requests Exceeding Port Limit

This component monitor returns the number of allocate requests over TCP that exceeded the port limit. If the value is greater than zero, this could indicate an attempt to misuse the port.

A/V Edge TCP: Packets Received/sec

This component monitor returns the number of packets received per second by the relay over TCP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge TCP: Packets Sent/sec

This component monitor returns the number of packets sent per second by the relay over TCP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge TCP: Average Data Packet Latency (milliseconds)

This component monitor returns the average latency for a valid data request over TCP in milliseconds. The returned value should be as low as possible.

A/V Edge TCP: Packets Dropped/sec

This component monitor returns the per-second rate of packets over TCP dropped by the relay. The returned value should be as low as possible.

This error occurs when an unexpectedly high rate of User Datagram Protocol (UDP) packets is received at the Media Relay (A/V Edge server)  causing some packets to be discarded. This could be the result of system overload or an indication of an attempt to misuse the MR.

To resolve this, check that the profile of network traffic to the MR is in line with expected usage. If the traffic exceeds 250 Mbps per interface, increase the Receive and Transmit buffer size on the associated network adapter network adapters to three times the default values.

If the cause is a general system overload, increase capacity of the deployed MR function. A network level trace can be used to determine if there is an unusual amount of traffic originating from a single source. If the situation persists, enable tracing to check the network source of sessions

Fournir un codes d’autorisation pour un usager lui donnant accès à sa classe de service peu importe le téléphone utilisé n'est pas possible de base avec Lync contrairement à la fonctionnalité FAC (Forced Authorization Codes) de Cisco par exemple ou fournit par d'autres IPBX.

Un éditeur propose une solution permettant de contourner cette problématique, il s'agit du produit "tel:+pin" (il est vrai que le nom n'est pas forcément exceptionnel).

Vous pouvez avoir plus d'informations ici: http://www.idc.it/solutions/telpin

Une vidéo de présentation:

Datasheet: http://www.idc.it/telpluspin_datasheet.pdf

Le whitepaper "Delivering Lync Real-Time Communications over Wi-Fi" est maintenant disponible au téléchargement.

Ce guide fournit des éléments importants pour un sujet d'actualité que celui de faire passer de l'audio et de la vidéo sur un réseau Wireless.

Il est disponible ici: http://www.microsoft.com/en-us/download/confirmation.aspx?id=35401

Le contenu est le suivant:

• Usage Scenarios

• Enterprise Wi-Fi usage scenarios
• Home Wi-Fi usage scenarios
• Public Wi-Fi hotspots usage scenarios

• Issues that Affect Wi-Fi Performance for Real-Time Application

• General issues (wireless NIC drivers, wireless NIC chipsets and hardware, legacy interoperability issues)
• Issues in enterprise Wi-Fi deployments
• Issues in public Wi-Fi hotspots
• Issues in home Wi-Fi deployments

• Enterprise Wi-Fi

• Mixed or Wi-Fi-only enterprise deployment
• Device types, usage patterns, legacy devices
• Usage patterns in enterprise Wi-Fi
• Legacy devices in enterprise Wi-Fi
• WMM QoS and Power Save support
• Enterprise WLAN controller
• Recommended Wi-Fi feature support and Wi-Fi configuration settings
• Wi-Fi policies
• Wireless network card recommendations
• Enterprise Voice Certifications

• Home Wi-Fi

• Home Wi-Fi deployment recommendations

• Public hotspot Wi-Fi

• Basic hotspot configurations

Les premières sessions de formation Lync 2013 Voice Ignite pour le Canada sont connus, elles se dérouleront dans les villes suivantes:

- Toronto,ON,Canada du 27 novembre 2012 08:30:00 EST au 30 novembre 2012 17:30:00 EST

- Calgary,AB,Canada du 27 novembre 2012 08:30:00 EST au 30 novembre 2012 17:30:00 EST

- Montréal,QC,Canada du 3 décembre 2012 08:30:00 EST au 6 décembre 2012 17:30:00 EST

Je ferais bien entendu partie de la session de Montréal!

La documentation Lync Serveur 2013 est aussi disponible pour la version RTM.

Les liens de téléchargements sont:

Lync 2013 RTM Documentation:

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

En ligne: http://technet.microsoft.com/en-us/library/gg398616(OCS.15).aspx

Lync 2013 Visio Shapes:

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

Préparant activement le ccnp voice, je suis tombé sur cette article très intéressant préposant des liens gratuits de formation sur le sujet:

Cisco Quick Learning Module
CCVP CVOICE
	Introducing Voice over IP
	CTT-TAC: Basic Analog-to-Digital Voice over IP
	CTT-TAC: Basic Analog-to-Digital Voice over IP” href=”http://www.cisco.com/web/learning/le31/le20/ssat/cim/tac_voice_basic.html”>CTT-TAC: Basic Analog-to-Digital Voice over IP
	Understanding Gateway Dial Peers
	Understanding Dial Plans
CCVP CIPT1
	Implementing Features in Cisco Unified Communications Manager
	Configuring Presence-Enabled Speed Dials and Call Lists
	Implementing Partitions and Calling Search Spaces
CCVP CIPT2
	Implementing AAR for Locations-Based CAC in Cisco Unified Communications Manager 6.0
	Examining Remote Site Redundancy Options
	Implementing TEHO with PSTN Backup in Cisco Unified Communications Manager v6.0
	Cisco Unified Communications Express as Survivable Remote Site Telephony
CCVP TUC
	Gathering Information for Troubleshooting
	Troubleshooting Common Gateway Registration Issues
	Troubleshooting Common Cisco Unity Integration Issues
CCVP QoS
	Introduction to Modular QoS CLI
	Congestion Management Configuring CBWFQ and LLQ
	Congestion Avoidance Introducing RED and WRED

Source: http://bsoftbangalore.wordpress.com/2012/10/24/ccnp-voice-free-training/

Merci à lui!

Bonne surprise ce matin, la version Lync Server 2013 est disponible au téléchargement!

On retrouve aussi Exchange 2013, Sharepoint 2013, Office 2013, Visio 2013....

Il arrive que des fois, lors d'une phase de coexistence Lync ocs, que l'on supprime un peu vite les anciennes stratégies.

Le résultat est le suivant lors de la phase de migration d'un utilisateur concerné par la legacy policy supprimée: Move-CsLegacyUser : All policies of type "DialPlan" are not migrated

Il est pas forcément pertinent de relancer la commande d'import des anciennes stratégies, on peut bypasser cela avec les options suivantes:

-ExcludeVoicePolicy -ExcludeDialPlan -ExcludeConferencingPolicy

Source: http://support.microsoft.com/kb/2441886

De gros changement concernant les futurs certifications Lync Server 2013, le programme est maintenant le suivant:

Donc adieu aux titre de mcts et mctip, obligation de passer une certification purement OS avec le mcsa Windows Server 2012 ce qui est pour un quelqu'un des télécoms, pas forcément une bonne nouvelle.

Le processus MCSA Windows Server 2010 est le suivant, à noter que pour les MCTIP Lync Server 2010, il est heureusement possible de le valider en passant l'examen 417.

Les deux examens 336 et 337 devrait être disponible pour la mi-novembre 2012.

Voici la liste des dernières mises à jours Microsoft pour Lync Server 2010:

- Lync 2010 (64 bit client):

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

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

            Version : 4.0.7577.4356

Lync 2010 (32 bit client):

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

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

            Version : 4.0.7577.4356

Lync Server 2010 :

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

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

            Version : 4.0.7577.205

Lync Server Attendee (Installation utilisateur) :

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

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

            Version : 4.0.7577.4356

Lync Server Attendee (Installation Administrateur) :

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

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

            Version : 4.0.7577.4356

Bien penser à l'update SQL suite à l'application des cumulatives updates!

D'après "The Lync Team Blog" de Microsoft, le client Lync 2013 est finalisé en terme de développement.

Il devrait être disponible quelque part dans le 1ier trimestre 2013

Source: http://blogs.technet.com/b/lync/archive/2012/10/11/lync-2013-is-finished.aspx

We wanted to let all of our blog readers know that the engineering team has signed off on the Release to Manufacturing (RTM) build of Lync 2013, as-of today, October 11th, 2012! General availability is planned for the first quarter of 2013. Starting October 19, any customer purchasing Office 2010 in retail will receive the new Office for free upon availability. Customers will see a preview version of the new Office on Windows RT devices, beginning with the Windows 8 launch on October 26.

Lundi 8 octobre a eu lieu la grande messe Polycom "NASDAQ Strategy Day".

Ce fut une présentation vraiment intéressante des nouvelles technologies arrivant sur le marché, en tant que consultant UC, on est tout de suite conscient que ces produits vont fortement influencé le marché.

On y découvre la technologie "RealPresence CloudAXIS" :

CloudAxis is a Web-based application that lets the host of a call set up credentials to the services he or she subscribes to, creating a presence directory. To set up a conference call, the host drags the names of people to be called onto the screen and the software fires an instant message to them. The IM includes a secure Web link for the call.

Users only need a browser plug-in to participate. Up to 40 people can be on a conference call, which allows a shared desktop.

A piece of the CloudAxis suite called the Flexible Resource Broker deals with bandwidth, sets up resources and links to the RMX and DMA servers. An Access Director sets up the presence directory and enables firewall traversal.

“It gives as a host the capability to call out to anybody at anytime without firewall hassles,” 

Ce produit devrait être disponible pour la fin du 1ier trimestre 2013.

Datasheet: http://www.polycom.com/content/dam/polycom/www/documents/data-sheets/rp-cloudaxis-suite-ds-enus.pdf

Polycom devrait supporter le standard H.264 SVC pour beaucoup de ces produits par un update software, ce qui tombe bien puisque Lync 2013 aussi.

L'ensemble de la présentation est visible ici: http://www.polycom.com/company/features/video-collaboration-20121008-player.html

On y retrouve des informations sur les nouvelles technologies suivantes:

• Polycom RealPresence Collaboration Server 800s, Virtual Edition
• Polycom RealPresence Group Series 300
• Polycom RealPresence Mobile 2.0
• Polycom RealPresence Desktop for Windows and Mac

Actuellement, la documentation technique n'est pas trop fourni, mais je suis curieux de voir le futur couplage avec Microsoft Lync. A suivre!

Une série d’articles concernant le déploiement de Lync 2013 seront publiées très prochainement.

 

Commençons par les prérequis :

 

Au niveau hardware, on reste sur les mêmes préconisations, il faut prendre en compte les nouveaux points suivants qui auront des incidences sur le sizing:

 

-        La centralisation du rôle de Front-end et Audio/Vidéo sur le même serveur

-        La colocalisation de la passerelle XMPP

-        Les nouvelles fonctionnalités HD et multi-vue très consommateurs en ressources CPU

 

En phase Béta, les capacités annoncées pour l’instant sont les suivantes :

-        12 à 20 serveurs par pool

-        12 500 utilisateurs par Front-end (dépend du modèle utilisateur)

 

Prérequis hardware pour un serveur Front-end :

 

Il faut prévoir 4gb pour les databases RTCLOCAL et LYNCLOCAL.

 

Prérequis hardware pour un serveur Directeur, archivage ou Monitoring :

 

Prérequis hardware pour un serveur Back-End :

 

Recommandations pour les cartes réseaux :

-        Minimum supporté : Une seule carte 1 Gbps (Ethernet)

-        Recommandé : Deux cartes 1 Gbps (Teamed Ethernet)

-        Media Server : 4 cartes 1 Gbps (NIC Teaming)

Il faudra quand même valider un point avec Microsoft, le Teaming de NIC HP pour des serveurs physiques m’ayant était très intensivement recommandé de ne pas l’utiliser dans les versions ultérieures.

 

Prérequis OS pour l’installation des rôles Lync Serveur 2013:

-        Windows Server 2008 R2 SP1 minimum

-        Windows Server 2012

 

Prérequis Back end :

-        SQL Server 2008 R2 SP1 minimum

-        SQL Server 2012

 

SQL Mirroring est supporté.

Lync Serveur 2013 installe automatiquement SQL Serveur 2012 Express sur chaque Front-End.

 

Prérequis software :

 

Niveau fonctionnel Forêt/Domaine Active Directory :

-        Windows Server 2003

-        Windows Server 2008

-        Windows Server 2008 R2

-        Windows Server 2012

 

Infrastructure : Dans le cadre d’un déploiement de plusieurs serveurs Front-End, un HLB sera toujours nécessaire pour les services Web

 

Virtualisation :

            Hyperviseurs supportés :

-        Windows Server 2008 R2 SP1 Hyper-V minimum

-        VMWare ESX 5

 

Fonctionnalités non supportés :

-        Quick/Live Migration

-        Dynamic Memory

-        VM Replica

Les conférences Lync 2013 se dérouleront du 18 au 21 février 2013 à San Diego, Californie,

L'agenda est disponible ici: http://www.lyncconf.com/agenda.aspx

L'inscription: http://www.lyncconf.com/register.aspx

With the growing adoption of Unified Communications (UC), many people now rely on laptop PCs and other untethered computing devices as their primary phones. The service provided by IntelePeer and 911 Enable is ideal for organizations housed in corporate campuses or other facilities where Microsoft Lync users often take their devices with them. When the user places an emergency call, the companies’ technologies work together to seamlessly and automatically provide the caller’s location information to the 911 operator at the geographically appropriate Public Safety Answering Point (PSAP), ensuring that emergency personnel can quickly and accurately respond.

 “With the proliferation of Unified Communications across corporate campuses, it’s important to ensure that seamless E911 support is available regardless of the user’s device,” said Lev Deich, director, 911 Enable. “Our E911 offerings help organizations to comply with state and federal regulations and are qualified by Microsoft, giving customers who use Microsoft Lync with IntelePeer SIP Trunking a proven, high-quality solution that delivers peace of mind.”

source: http://www.intelepeer.com/news/article.php?DID=180

J'ai étais récemment nommé et sélectionné par Microsoft en tant que Virtual Technology Specialist (V-TSP) pour Lync concernant la partie voix sur IP.
Les V-TSP Lync sont divisés en deux groupes, IM/présence et Voice, il n'y avait qu'une place au Québec apparement pour la seconde spécialisation, cela peut-être une belle expérience.

Le programme V-TSP?

The Microsoft Virtual Technology Specialist Program (VTSP) is a select group chosen from the elite in Microsoft’s partner community, whose focus is to augment Microsoft’s internal Technology Specialist team. Their primary role is to communicate the value of Microsoft Solutions to customers and to provide architectural guidance for Enterprise Integration solutions. The Microsoft VTSP program was designed to create a deeper relationship with Microsoft Partners, the Product Teams at Microsoft Corporate, and Regional Microsoft Offices, in order to provide highly skilled solution specialists to Microsoft customers. It is designed to enable a high performance team of partner-based resources to deliver pre-sale activities and resources to empower customers and help them meet their solution and integration needs.


Alors qu'est-ce que cela signifie pour moi? En tant que VTSP,  je vais avoir accès aux ressources, la documentation technique interne, l'accès VPN, un badge pour les locaux ainsi qu'une adresse e-mail microsoft.com.


Je suis vraiment heureux de faire partie du programme et de découvrir les nouvelles opportunités et défis que cela va amener!

J'ai eu l'opportunité d'implémenter  un nombre important d'environnement Lync Server 2010, que ce soit des entités n'ayant pas d'univers UC ou migrant depuis Office Communication Server 2007 R1 ou R2, Live Meeting était relativement peu utilisé pour diverses raisons (interface pas très friendly, pas si simple à appréhender,...), abandonner ce client pour Lync 2010 ne fut jamais un problème, au contraire même, la simplicité du client le rendant plus accessible.

Dans le cadre d'une migration OCS 2007 R1 vers Lync Server 2010, j'ai eu l'occasion de travailler récemment pour une organisation utilisant Live Meeting à grande échelle, pouvant aller jusqu'à 500 personnes dans une session (le serveur OCS 2007 R1 étant virtualisé et ayant 1gb de ram).

Il est vrai que si on regarde de plus près, la transition pour certaine fonctionnalité n'est pas si simple. Voici un tableau présentant les fonctions manquantes:

Certains points ne sont pas insurmontables, mais connaitre ces limitations est important.

Source du tableau: http://www.csvep.com/wp-content/uploads/Microsoft-Office-Live-Meeting-to-Lync.pdf

Il est possible de visionner des vidéos très intéressantes concernant la nouvelle version Lync Server 2013 venant directement des sessions qui se sont déroulés au TechEd en Australie.

Les sujets et les vidéos associés sont répertoriés ici:

Lync 2013 Architecture (EXL314) – here

Lync 2013 Meeting Improvements (EXL316) - here

Lync 2013 Deployment (EXL321) – here

Lync 2013 Voice Improvements (EXL325) – here

Demystifying Integration of Lync to your Existing PABX (EXL231) – here

Lync 2013 and Enterprise Networking (EXL334) – here

Il arrive pour diverses raisons (migration et changement de domaine sip par exemple), que l'on doit jongler avec plusieurs domaines sip.

Ce qui peut causer cet pop-up sur certains postes clients:

Pour que l'utilisateur final ne soit pas déstabilisé par l'apparition de cette fenêtre, il faut modifier la valeur de Registre TrustModelData dans l'emplacement  "HKEY_CURRENT_USER\Software\Microsoft\Communicator\" et inclure le nom du pool.

Une chose intéressante depuis l'annonce en fin d'année dernière du firmware polycom permettant d'intégrer ces modèles avec Lync server, les modèles Polycom VVX500 IP et SpectraLink sont officiellement qualifiés pour Lync :

SpectraLink:

VVX500:

Je ne vais pas pouvoir faire de retour rapide sur ces deux modèles, récemment, j'ai plutôt privilégier des kirks que les spectralink sur un nouveau projet de migration téléphonique vers Lync vu le contexte du client, mais je ne manquerais pas de le faire à l'occasion

Ceci n'est pas une très bonne nouvelle pour ceux ayant acquis des téléphones de standard type SNOM 360, mais ce modèle de ne fera pas partie des nouveaux firmwares 8.8.1.11 dit "Apollo" (UC Edition firmware.

http://forum.snom.com/index.php?showtopic=10337

Raison: "Unfortunately, the snom 360 is no longer supported by the Apollo release, because of hardware limitations."

Ce qui l'écarte définitivement de faire partie des téléphones qualifiées pour Lync 2010/2013.

C'est un élément important lors d'une phase de propositon, le support snom étant très peu réactif. Pour l'avoir déjà déployé, ce type de téléphone présente des problèmes d'intégration, il faut beaucoup de patience...

Le blog fut un peu délaissé ces derniers temps, pris par des projets Cisco wifi d'envergure et le passage de ma certification CCNA Wireless, je n'ai pu le maintenir à jour, mais son activité reprends à partir de ce week-end:

Au vue de futur projet UC cisco, je en préparation du CCNP Voice, donc cela va surement amené des articles sur le sujet, même si ma dominante technologique reste les technologies UC Microsoft.

Cette semaine, Microsoft a publié le CU Septembre 2012 pour OCS 2007 R2 Group Chat. La liste des différentes mises à jour peuvent être trouvées ci-dessous.

OCS 2007 R2 Group Chat Server
Version: 3.5.6907.265
KB2701664
http://www.microsoft.com/en-us/download/details.aspx?id=12180

OCS 2007 R2 Group Chat Admin
Version: 3.5.6907.265
KB2701664
http://www.microsoft.com/en-us/download/details.aspx?id=12180
    
OCS 2007 R2 Group Chat Client
Version: 3.5.6907.265
KB2493736
http://www.microsoft.com/en-us/download/details.aspx?id=12180

Cela fait maintenant quelques semaines (j'ai un peu de retard sur mon blog), le RMX 1500 de Polycom fait enfin partie du programme UCOIP pour Lync, même si beaucoup d'entre nous avait déjà pas mal d'intégration de ce genre que ce soit avec Lync ou OCS.

Cette qualification est arrivé avec le nouveau firmware 7.7 qui apporte les nouveautés suivantes:

• Polycom, Microsoft and Cisco bridge interoperability – this is the ability to host multi-party video conferences on the RMX with video endpoints from multiple vendors. In the case of Cisco, signalling is handled via the integration of Cisco Unified Call Manager (CUCM) and Polycom’s Distributed Media Application (DMA).
• Microsoft RTV forward error correction (FEC) support – with this feature the RMX is able to support Lync error correction in scenarios where there is connection instability.
• ICE over TCP – When ICE over UDP is blocked by a Firewall, the ICE connection automatically uses TCP.
• Media over TCP – as with above, when media is unable to utilise UDP due to Firewall policies etc., the RMX will automatically switch to TCP.
• Additional Virtual Meeting Room (VMR) presence mode – prior to this release VMRs enabled for presence would only display as available, the 7.7 update introduces the busy state when busy or in use.
• Error recovery – RMX 7.7 can automatically recover from short duration network errors (up to 5 seconds), enabling video or audio conference calls in Microsoft Lync to continue without disconnecting.
• Lync AVMCU to RMX Cascading – Last but not least (and a personal favourite) the ability to connect a Lync video conference call to the RMX by transparently joining the two meetings, hosted on their respective MCUs, via end-user drag/drop within the Lync client

Bien entendu, cela s'applique aussi avec les RMX 2000 et 4000.

La release notes est ici: http://downloads.polycom.com/bridging_collab/rmx/relnotes/RMX_Release_Notes_V_7_7_CP.pdf

Depuis quelques semaines déjà, Polycom a rendu disponible le firmware 1.1 pour son système de salle CX7000 spécialisé dans infrastructures Lync Serveur.

Cette mise à jour apporte les nouveautés suivantes:

• Support for Office 365 (both Shared and Dedicated) – more on this later!
• Standalone-mode – sign into Lync without the need to add the system to the domain (previously required)
• Ability to daisy-chain either Polycom HDX Microphone Array or Ceiling Microphones (in both cases up to two can be linked together)
• Hot-desking capability (User Sign In) – idle session timeout can be set here so the CX7000 dedicated account will switch back for those using the room scheduling
• Utilise the CX5000 (RoundTable) for video input—including support for panoramic video—and as microphone and speaker
• Improved audio performance via Polycom Audio Echo Cancellation (AEC) enhancements
• Lync client is updated from CU4 to CU5 – more on this here
• Support for 11 user interface languages (English, French, German, Spanish, Italian, Portuguese, Russian, Japanese, Korean, Simplified Chinese and Traditional Chinese
• Ability for users to select a different input language for IM and contact search, reverts to system language after each conversation ends.
• Ability to override the Exchange Web Services autodiscover address and/or provide alternate e-mail/Exchange credentials
• Bandwidth reduction for VGA-based content
  sharing – reduction is from 6MB to as low as 1MB, in situations where the content is static

L'update en 1.1 nécessite impérativement d'être en firmware 1.0.2:

"If your system is running version 1.0.1 software, update to version 1.0.2 software before you install version 1.1 software"

La release note est ici: http://downloads.polycom.com/video/cx7000/cx7000_rel_1_1_0.pdf

Le guide d'administration ici: http://support.polycom.com/global/documents/support/setup_maintenance/products/video/cx7000_admin_guide.pdf