Microsoft vient de publier un nouveau firmware pour la Roundtable.
Le lien de téléchargement: http://www.microsoft.com/download/en/details.aspx?id=17500
1. Download the .msi file.
2. Double click to launch.
3. Please read the EULA carefully and accept to install only if you agree with the terms.
4.
After the installation of the firmware, please refer to the Microsoft
RoundTable Deployment Guide for the image update procedures.
Une fonctionnalité intéressante dans certains contexte est le mode privacy.
Cela permet aux utilisateurs de restreindre leurs présence à seulement les utilisateurs présents dans leurs listes de contacts.
Très simple a activer en powershell:
Get-CsPrivacyConfiguration | Set-CsPrivacyConfiguration -EnablePrivacyMode
Dans le cas ou un environnement OCS 2007 R2 et Lync sont en coexistence, les utilisateurs ocs n'auront pas cette fonctionnalité.
Voici un petit outil pratique pour les intégrateurs Lync qui permet de faire un check rapide des prérequis avant l'installation de l'environnement: Microsoft IT Environemnt Health Scanner
Téléchargeable ici: http://www.microsoft.com/download/en/details.aspx?id=10116
Et oui, tout le monde n'a pas encore migré sur Lync Server 2010.
Microsoft vient de sortir le cumulative Update 9 pour Office Communication Server 2007 R2:
Serveur Office Communications Server 2007 R2 :
Description:http://support.microsoft.com/kb/968802
Téléchargement:http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b3b02475-150c-41fa-844a-c10a517040f4
Client Office Communicator 2007 R2:
Description:http://support.microsoft.com/kb/2549042
Téléchargement:http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=515d6dba-4c6a-48bb-a06a-d99c5742676d
Group Chat Server 2007 R2:
Description:http://support.microsoft.com/kb/2549044
Téléchargement:http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e5924bf9-b042-4c53-b4a6-79c7e5c9749b&displaylang=en
Group Chat Cient 2007 R2:
Description:http://support.microsoft.com/kb/2549043
Téléchargement:http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e5924bf9-b042-4c53-b4a6-79c7e5c9749b&displaylang=en
Certification passée ce jour et réussi avec un score de 850.
Je recommande vraiment ces deux guide non officiels qui m'ont beaucoup aidé pour préparer cette certification:
La certification comprend 3 scénarios avec entre 8 et 15 question chacun + 25 questions générales.
Cela tourne surtout autour de la haute disponibilité, de la mise en place de la téléphonie, des backups et design.
Accessible pour ceux faisant pas mal d'architecture.
Ayez, certification passée et réussie.
Certification pas vraiment inaccessible, ce lien m'a permit de voir les points importants pour réussir cette examen:
Descriptif de la certification ici: http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-664#tab2
Jeudi, au tour du MCITP Microsoft Lync Server 2010 Administrator, encore deux bonnes nuits de préparation
L'utilitaire de translation intégré à Lync fait peau neuve avec la sortie de Lync Guistic:
Ce petit outil intégré à Lync va vous permettre de dialoguer avec un contact sans avoir une maîtrise totale de sa langue.
Il est téléchargeable ici avec un petit tutoriel de démonstration: http://lyncguistic.cloudapp.net/
Microsoft supporte officiellement depuis mi-mai une entrée wilcard dans le san du certificat (et non pas pour le subject name).
Le wilcard san est supporté pour ces cas là:
Vous trouverez plus d'informations dans la documentation officielle:
http://technet.microsoft.com/en-us/library/hh202161.aspx
On peut installer 20 fois un produit est tombé sur une erreur jamais rencontré auparavant.
L'erreur du weekend dans le cadre de mon lab concernant du nlb en environnement haute disponibilité est la suivante:
La réponse est dans le KB2522454: http://www.mskbarticles.com/index.php?kb=2522454
Il faut saisir cette commande avec un niveau de privilège élevé:
%systemroot%\system32\dism.exe /online /add-package
/packagepath:%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
/ignorecheck
Et rebooter le système.
iDialog v2.0 est un client mobile compatible Microsoft Lync pour Apple IPhone, iPad ou iPod Touch.
Il est disponible en téléchargement depuis le 13 mai 2011 sur iTunes.
Les nouveautés:
Par contre, ce client continue a ce services des fonctionnalités de web access pour se connecter a un environnement OCS/Lync.
Lync n'ayant plus de web access, il faut installer un cwa 2007 ou 2007 R2 pour pouvoir utiliser ce type de client.
Source: http://www.modalitysystems.com/blog/?p=157
J'ai recemment rencontré un problème bloquant pour les utilisateurs à l'exterieur du réseau d'entreprise, ils ne pouvaient ni accéder au carnet d'adresses d'entreprise, que ce soit en web recherche ou en le téléchargeant en local, impossible aussi d'accèder aux partages lors d'une visioconférence:
La première chose à laquelle on pense est au reverse proxy, les fonctionnalités suivantes passe par lui pour les remotes users:
Mais l'ensemble de mes tests faisant ressortir des résultats correctes, les traces réseaux à partir du pc client ne faisant jamais ressortir l'ip du reverse proxy et surtout le fait qu'un log remontant l'ip du pc m'ont fait dirigé vers une autre piste.
Cela peut faire gagner beaucoup de temps, mais il manquait étrangement sur le edge la mise à jour windows suivante:
https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=26146
C'était un problème de certificat.
Le support du codec RTV (Real-Time Video ) et du protocole CCCP (Centralized Conferencing Control Protocol ) par les systèmes de salles HDX prévu à l'origine pour juin 2011 est maintenant effectif.
Il faut passer le firmware en version 3.0.1 et acquérir la licence Normal 0 21 false false false FR X-NONE X-NONE HDX RTV/CCCP.
Votre équipement doit être au minimum en révision C.
Un système HDX peut maintenant rejoindre une conférence hébergée par un MCU Lync.
Que ce client se fait attendre! Il est annoncé courant de l'année 2011 mais déjà beaucoup de clients l'attendent.
En attendant, une version non officielle est disponible pour Windows Phone, il s'agit de LP.
LP nécéssite un serveur supplémentaire, si on prends les informations de la faq :
En quoi consiste le serveur:
Les pré-requis:
La faq est accessible ici : http://blogs.msdn.com/b/mwo/archive/2011/03/11/lync-client-for-wp7-faq.aspx
Voilà pour la partie technique, mais qu'apporte le client?
A première vue, pas mal de fonctionnalités bien pratiques, voici une série de vidéo intéressantes:
Configuration: http://www.youtube.com/watch?v=n9h4v5xxtsg
Carte de visite: http://www.youtube.com/watch?v=so3eKPpEae8
Recherche d'un contact: http://www.youtube.com/watch?v=12CtXK9KprY
Balise + fonction "call via work": http://www.youtube.com/watch?v=ltvjWb5WYwc
"Call via work" via le menu de contact:http://www.youtube.com/watch?v=DaWZ6r9W6U0
"Call via work" via la carte de visite: http://www.youtube.com/watch?v=hYtgnnoHZzo
"Call via work" via l'historique: http://www.youtube.com/watch?v=G9ECVWQHBVg
LP est en version 2.0 depuis début avril: http://blogs.msdn.com/b/mwo/archive/2011/04/05/lp-v2-0-coming-up.aspx
La documentation et les binaires sont ici: http://ucma3restsample.codeplex.com/releases/view/65008
Les téléphones SNOM en environnement OCS/Lync, toute une histoire!
Normal 0 21 false false false FR X-NONE X-NONE MicrosoftInternetExplorer4
Depuis quelques temps, des clients se plaignent du comportement du téléphone SNOM 870, lors d’un appel entre un 870 et un client Communicator/Lync, l’appel s’arrête au bout exactement de 6 minutes, coupé depuis le 870, pourtant, aucun timer de ce genre n’apparait dans le fichier XML de configuration et cela n'arrive pas lors d'un appel depuis ou vers un SNOM 870 et un téléphone portable par exemple.
Ce phénomène se produit aussi dans l'environnement Lync Server monté par Microsoft dans notre centre des usages, sachant qu’avec les autres modèles, cela marche très bien (Polycom et Aastra).
Avec les 300,370, M9, le problème ne se posent pas (enfin celui là de problème).
Les traces sip sont clair, le snom coupe l'appel sans envoyé de sip bye, le client lync ou communicator lui, se considère toujours en appel, le téléphone affiche "SIP/2.0 500 Server Internal Error":
Normal 0 21 false false false FR X-NONE X-NONE MicrosoftInternetExplorer4
Received from tls:192.168.4.66:5061 at 20/4/2011 16:47:16:616 (6756 bytes):
BENOTIFY sip:ocruchot@192.168.4.50:3451;transport=tls;line=snzn8sqm;ms-received-cid=3A6400;grid SIP/2.0
Via: SIP/2.0/TLS 192.168.4.66:5061;branch=z9hG4bKAA25B019.B6EEB5F382677B0A;branched=FALSE
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="EF126ACB", snum="37", rspauth="0100000049b585fc598af77f64000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
Max-Forwards: 70
To: <sip:ocruchot@immersion.fr>;tag=x2zkxhe4b3;epid=00041341205501
Content-Length: 5972
From: <sip:ocruchot@immersion.fr>;tag=E9260080
Call-ID: 7770263c94b916cfb3fc340b44383431
CSeq: 7 BENOTIFY
Require: eventlist
Content-Type: application/vnd-microsoft-roaming-self+xml
Event: vnd-microsoft-roaming-self
subscription-state: active;expires=3474
<roamingData xmlns="http://schemas.microsoft.com/2006/09/sip/roaming-self" xmlns:cat="http://schemas.microsoft.com/2006/09/sip/categories">
<categories xmlns="http://schemas.microsoft.com/2006/09/sip/categories" uri="sip:ocruchot@immersion.fr">
<category name="state" instance="1" publishTime="2011-04-20T14:47:06.437" container="2" version="6" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>6500</availability><activity token="on-the-phone" /></state>
</category>
<category name="state" instance="268435456" publishTime="2011-04-20T14:45:01.453" container="2" version="1" expireType="user">
<state xsi:type="aggregateMachineState" endpointId="39590d11-9e9f-53ca-ad2a-7244afb3af99" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="state" instance="1351495144" publishTime="2011-04-20T14:45:01.453" container="2" version="1" expireType="endpoint" endpointId="39590D11-9E9F-53CA-AD2A-7244AFB3AF99">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="false" xsi:type="machineState">
<availability>3500</availability>
</state>
</category>
<category name="state" instance="1440448903" publishTime="2011-04-20T14:47:06.437" container="2" version="1" expireType="endpoint" endpointId="39590D11-9E9F-53CA-AD2A-7244AFB3AF99">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="false" xsi:type="phoneState">
<availability>6500</availability>
<activity token="on-the-phone" minAvailability="6500" maxAvailability="8999"></activity></state>
</category>
<category name="state" instance="536870912" publishTime="2010-12-10T11:16:59.600" container="2" version="1" expireType="static">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="true" xsi:type="userState"><availability>3500</availability></state>
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:47:06.437" container="3" version="6" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>6500</availability><activity token="on-the-phone" /></state>
</category>
<category name="state" instance="1351495144" publishTime="2011-04-20T14:45:01.453" container="3" version="1" expireType="endpoint" endpointId="39590D11-9E9F-53CA-AD2A-7244AFB3AF99">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="false" xsi:type="machineState">
<availability>3500</availability>
</state>
</category>
<category name="state" instance="1440448903" publishTime="2011-04-20T14:47:06.437" container="3" version="1" expireType="endpoint" endpointId="39590D11-9E9F-53CA-AD2A-7244AFB3AF99">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="false" xsi:type="phoneState">
<availability>6500</availability>
<activity token="on-the-phone" minAvailability="6500" maxAvailability="8999"></activity></state>
</category>
<category name="state" instance="536870912" publishTime="2010-12-10T11:16:59.600" container="3" version="1" expireType="static">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="true" xsi:type="userState">
<availability>3500</availability>
</state>
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:47:06.437" container="100" version="6" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>6500</availability></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:47:06.437" container="100" version="6" expireType="user">
<legacyInterop availability="6500" />
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:47:06.437" container="200" version="6" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>6500</availability><activity token="on-the-phone" /></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:47:06.437" container="200" version="6" expireType="user">
<legacyInterop availability="6500" token="on-the-phone" />
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:47:06.437" container="300" version="6" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>6500</availability><activity token="on-the-phone" /></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:47:06.437" container="300" version="6" expireType="user">
<legacyInterop availability="6500" token="on-the-phone" />
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:47:06.437" container="400" version="6" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>6500</availability><activity token="on-the-phone" /></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:47:06.437" container="400" version="6" expireType="user">
<legacyInterop availability="6500" token="on-the-phone" />
</category>
</categories>
</roamingData>
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:47:16:645 (617 bytes):
SIP/2.0 100 Trying
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="0BC83341", snum="38", rspauth="010000008ecaee8e72cd51bd64000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 1 INVITE
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-l13zcmi8z7eg;rport;ms-received-port=3451;ms-received-cid=3A6400
Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FInterClusterRouting
Content-Length: 0
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:47:16:934 (681 bytes):
SIP/2.0 183 Session Progress
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="6BBC734D", snum="39", rspauth="010000009ed794da2c3a569664000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
Content-Length: 0
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-l13zcmi8z7eg;rport;ms-received-port=3451;ms-received-cid=3A6400
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 1 INVITE
Ms-Forking: Active
Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting(Microsoft Lync Server 2010 4.0.7577.0)
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:47:17:210 (746 bytes):
SIP/2.0 101 Progress Report
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="D3FC87F9", snum="40", rspauth="010000005a20e0c2a7beef8f64000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
Content-Length: 0
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-l13zcmi8z7eg;rport;ms-received-port=3451;ms-received-cid=3A6400
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 1 INVITE
ms-diagnostics: 13004;reason="Request was proxied to one or more registered endpoints";source="CDU-LYNC-4.Immersion.fr";Count="2";appName="InboundRouting"
Server: InboundRouting/4.0.0.0
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:47:17:530 (648 bytes):
SIP/2.0 180 Ringing
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="2AADA9CD", snum="41", rspauth="0100000089e463582552d5a164000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-l13zcmi8z7eg;rport;ms-received-port=3451;ms-received-cid=3A6400
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>;epid=c6095d7456;tag=ef7fb3f90e
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 1 INVITE
User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
Content-Length: 0
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:47:17:841 (668 bytes):
SIP/2.0 180 Ringing
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="DD4EC3C7", snum="42", rspauth="0100000034931a6d20a8966b64000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-l13zcmi8z7eg;rport;ms-received-port=3451;ms-received-cid=3A6400
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>;epid=ef62879640;tag=b370e914fa
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 1 INVITE
User-Agent: CPE/4.0.7577.107 OCPhone/4.0.7577.107 (Microsoft Lync 2010 Phone Edition)
Content-Length: 0
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:47:23:483 (1660 bytes):
SIP/2.0 200 OK
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="1F64DD89", snum="43", rspauth="0100000097e98a694de51ff164000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
P-Asserted-Identity: <sip:amorel@immersion.fr>, <tel:+33970197566>
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-l13zcmi8z7eg;rport;ms-received-port=3451;ms-received-cid=3A6400
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>;epid=c6095d7456;tag=ef7fb3f90e
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 1 INVITE
Record-Route: <sip:CDU-LYNC-4.Immersion.fr:5061;transport=tls;opaque=state:T:F:Ci.R3a6400;lr;ms-route-sig=debuYGXrLsivZzX6tLuUZswCEwE4bU5Bff_EIWKaLklvfHl_zCf0puvQAA>
Contact: <sip:amorel@immersion.fr;opaque=user:epid:cjBo86X3Wl6DerBRMo1OGwAA;gruu>
User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
Supported: histinfo
Supported: ms-safe-transfer
Supported: ms-dialog-route-set-update
Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REFER, NOTIFY, BENOTIFY, OPTIONS
Session-Expires: 720;refresher=uac
ms-endpoint-location-data: NetworkScope;ms-media-location-type=Intranet
Supported: ms-bypass
Supported: replaces
Content-Type: application/sdp
Content-Length: 344
v=0
o=- 0 0 IN IP4 192.168.4.54
s=call
c=IN IP4 192.168.4.54
b=CT:99980
t=0 0
m=audio 6270 RTP/SAVP 0 8 9 101
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:wGOn1ByyFOdVq7iKwgnbcNYcBVB8naOguBAKYOAh|2^31|1:1
a=maxptime:200
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
--------------------------------------------------------------------------------
Sent to tls:192.168.4.66:5061 at 20/4/2011 16:47:23:547 (941 bytes):
ACK sip:amorel@immersion.fr;opaque=user:epid:cjBo86X3Wl6DerBRMo1OGwAA;gruu SIP/2.0
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-1x4ju0bbo4ny;rport
Route: <sip:CDU-LYNC-4.Immersion.fr:5061;transport=tls;opaque=state:T:F:Ci.R3a6400;lr;ms-route-sig=debuYGXrLsivZzX6tLuUZswCEwE4bU5Bff_EIWKaLklvfHl_zCf0puvQAA>
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>;tag=ef7fb3f90e;epid=c6095d7456
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 1 ACK
Max-Forwards: 70
Contact: <sip:ocruchot@immersion.fr;opaque=user:epid:EQ1ZOZ-eylOtKnJEr7OvmQAA;gruu>;reg-id=1
P-Preferred-Identity: "Olivier Cruchot" <sip:ocruchot@immersion.fr>, <tel:+15623669719>
Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="4F0C4B50", targetname="CDU-LYNC-4.Immersion.fr", crand="777a8552", cnum="22", response="01000000b37360350ff8a65464000000"
Content-Length: 0
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:47:25:085 (1641 bytes):
BENOTIFY sip:ocruchot@192.168.4.50:3451;transport=tls;line=snzn8sqm;ms-received-cid=3A6400;grid SIP/2.0
Via: SIP/2.0/TLS 192.168.4.66:5061;branch=z9hG4bK46396C10.4AFC76C884856B13;branched=FALSE
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="2428E9F9", snum="44", rspauth="0100000009eae53b1b31a9e764000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
Max-Forwards: 70
To: <sip:ocruchot@immersion.fr>;tag=zpgyxhdrmi;epid=00041341205501
Content-Length: 880
From: <sip:ocruchot@immersion.fr>;tag=29000080
Call-ID: 7870263c001fe733960166b7863a7e51
CSeq: 5 BENOTIFY
Require: eventlist
Content-Type: application/msrtc-event-categories+xml
Event: presence
subscription-state: active;expires=3465
<categories xmlns="http://schemas.microsoft.com/2006/09/sip/categories" uri="sip:amorel@immersion.fr"><category xmlns="http://schemas.microsoft.com/2006/09/sip/categories" name="state" instance="1" publishTime="2011-04-20T14:47:15.160">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>6500</availability><activity token="on-the-phone" /><endpointLocation>Je travaille à la maison</endpointLocation><delimiter xmlns="http://schemas.microsoft.com/2006/09/sip/commontypes" /><timeZoneBias>-120</timeZoneBias><timeZoneName>Paris, Madrid (heure d’été)</timeZoneName><timeZoneAbbreviation>Paris, Madrid (heure d’été)</timeZoneAbbreviation><device>computer</device><end xmlns="http://schemas.microsoft.com/2006/09/sip/commontypes" /></state>
</category>
</categories>
--------------------------------------------------------------------------------
Sent to tls:192.168.4.66:5061 at 20/4/2011 16:53:23:557 (1822 bytes):
INVITE sip:amorel@immersion.fr;opaque=user:epid:cjBo86X3Wl6DerBRMo1OGwAA;gruu SIP/2.0
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-4vonm2nu1abz;rport
Route: <sip:CDU-LYNC-4.Immersion.fr:5061;transport=tls;opaque=state:T:F:Ci.R3a6400;lr;ms-route-sig=debuYGXrLsivZzX6tLuUZswCEwE4bU5Bff_EIWKaLklvfHl_zCf0puvQAA>
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>;tag=ef7fb3f90e;epid=c6095d7456
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 2 INVITE
Max-Forwards: 70
Contact: <sip:ocruchot@immersion.fr;opaque=user:epid:EQ1ZOZ-eylOtKnJEr7OvmQAA;gruu>;reg-id=1
X-Serialnumber: 000413412055
P-Preferred-Identity: "Olivier Cruchot" <sip:ocruchot@immersion.fr>, <tel:+15623669719>
P-Key-Flags: resolution="31x13", keys="4"
User-Agent: snom870/8.6.6.4-OCS
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, BENOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE
Allow-Events: talk, hold, refer, call-info
Supported: timer, 100rel, replaces, from-change
Session-Expires: 720;refresher=uac
Min-SE: 90
Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="4F0C4B50", targetname="CDU-LYNC-4.Immersion.fr", crand="7ab08042", cnum="23", response="01000000544570b599ad895a64000000"
Content-Type: application/sdp
Content-Length: 462
v=0
o=root 1606082940 1606082940 IN IP4 192.168.4.50
s=call
c=IN IP4 192.168.4.50
t=0 0
m=audio 62844 RTP/AVP 0 8 3 106 18 9 101
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:fqJPvMDUps7+QZqA1ndDMwiNWDlc2VUfDbOAcHP9|2^31|1:1
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:106 G726-32/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:53:23:564 (647 bytes):
SIP/2.0 100 Trying
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="C08C9954", snum="45", rspauth="010000003c0408374f0a0f5964000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-4vonm2nu1abz;rport;ms-received-port=3451;ms-received-cid=3A6400
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>;tag=ef7fb3f90e;epid=c6095d7456
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 2 INVITE
User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
Content-Length: 0
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:53:23:855 (739 bytes):
SIP/2.0 500 Server Internal Error
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="2B2545AC", snum="46", rspauth="0100000014b2085eeafc06db64000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-4vonm2nu1abz;rport;ms-received-port=3451;ms-received-cid=3A6400
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>;tag=ef7fb3f90e;epid=c6095d7456
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 2 INVITE
User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
ms-client-diagnostics: 52001;reason="Client side general processing error."
Content-Length: 0
--------------------------------------------------------------------------------
Sent to tls:192.168.4.66:5061 at 20/4/2011 16:53:23:862 (941 bytes):
ACK sip:amorel@immersion.fr;opaque=user:epid:cjBo86X3Wl6DerBRMo1OGwAA;gruu SIP/2.0
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-4vonm2nu1abz;rport
Route: <sip:CDU-LYNC-4.Immersion.fr:5061;transport=tls;opaque=state:T:F:Ci.R3a6400;lr;ms-route-sig=debuYGXrLsivZzX6tLuUZswCEwE4bU5Bff_EIWKaLklvfHl_zCf0puvQAA>
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=19vxp4osmj;epid=00041341205501
To: <sip:amorel@immersion.fr>;tag=ef7fb3f90e;epid=c6095d7456
Call-ID: f570263c334afc2cb808bb051e790185
CSeq: 2 ACK
Max-Forwards: 70
Contact: <sip:ocruchot@immersion.fr;opaque=user:epid:EQ1ZOZ-eylOtKnJEr7OvmQAA;gruu>;reg-id=1
P-Preferred-Identity: "Olivier Cruchot" <sip:ocruchot@immersion.fr>, <tel:+15623669719>
Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="4F0C4B50", targetname="CDU-LYNC-4.Immersion.fr", crand="702b8ae3", cnum="24", response="0100000094c3cfdd1f0589e664000000"
Content-Length: 0
--------------------------------------------------------------------------------
Sent to tls:192.168.4.66:5061 at 20/4/2011 16:53:29:019 (1138 bytes):
SERVICE sip:ocruchot@immersion.fr SIP/2.0
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-g0bsk48s4unx;rport
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=0ek4h8rbqf;epid=00041341205501
To: "Olivier Cruchot" <sip:ocruchot@immersion.fr>
Call-ID: 6a72263ca003931c6bd66040bdb66484
CSeq: 7 SERVICE
Max-Forwards: 70
Contact: <sip:ocruchot@immersion.fr;opaque=user:epid:EQ1ZOZ-eylOtKnJEr7OvmQAA;gruu>;reg-id=1
User-Agent: snom870/8.6.6.4-OCS
Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="4F0C4B50", targetname="CDU-LYNC-4.Immersion.fr", crand="e1776463", cnum="25", response="01000000cd1948aeb47afa9764000000"
Content-Type: application/msrtc-category-publish+xml
Content-Length: 405
<publish xmlns="http://schemas.microsoft.com/2006/09/sip/rich-presence">
<publications uri="sip:ocruchot@immersion.fr">
<publication categoryName="state" instance="1440448903" container="2" version="1" expireType="time" expires="0" >
</publication>
<publication categoryName="state" instance="1440448903" container="3" version="1" expireType="time" expires="0" >
</publication>
</publications>
</publish>
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:53:29:288 (5444 bytes):
SIP/2.0 200 OK
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="0A4A3B94", snum="47", rspauth="01000000c0e74397984e962e64000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
Content-Length: 4780
From: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=0ek4h8rbqf;epid=00041341205501
To: "Olivier Cruchot" <sip:ocruchot@immersion.fr>;tag=173F0C3DC46743B948008B07F870781F
Call-ID: 6a72263ca003931c6bd66040bdb66484
CSeq: 7 SERVICE
Via: SIP/2.0/TLS 192.168.4.50:3451;branch=z9hG4bK-g0bsk48s4unx;rport;ms-received-port=3451;ms-received-cid=3A6400
Content-Type: application/vnd-microsoft-roaming-self+xml
<roamingData xmlns="http://schemas.microsoft.com/2006/09/sip/roaming-self" xmlns:cat="http://schemas.microsoft.com/2006/09/sip/categories">
<categories xmlns="http://schemas.microsoft.com/2006/09/sip/categories" uri="sip:ocruchot@immersion.fr">
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="2" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="state" instance="268435456" publishTime="2011-04-20T14:45:01.453" container="2" version="1" expireType="user">
<state xsi:type="aggregateMachineState" endpointId="39590d11-9e9f-53ca-ad2a-7244afb3af99" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="state" instance="1351495144" publishTime="2011-04-20T14:45:01.453" container="2" version="1" expireType="endpoint" endpointId="39590D11-9E9F-53CA-AD2A-7244AFB3AF99">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="false" xsi:type="machineState">
<availability>3500</availability>
</state>
</category>
<category name="state" instance="536870912" publishTime="2010-12-10T11:16:59.600" container="2" version="1" expireType="static">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="true" xsi:type="userState"><availability>3500</availability></state>
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="3" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="state" instance="1351495144" publishTime="2011-04-20T14:45:01.453" container="3" version="1" expireType="endpoint" endpointId="39590D11-9E9F-53CA-AD2A-7244AFB3AF99">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="false" xsi:type="machineState">
<availability>3500</availability>
</state>
</category>
<category name="state" instance="536870912" publishTime="2010-12-10T11:16:59.600" container="3" version="1" expireType="static">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="true" xsi:type="userState">
<availability>3500</availability>
</state>
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="100" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:53:19.063" container="100" version="7" expireType="user">
<legacyInterop availability="3500" />
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="200" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:53:19.063" container="200" version="7" expireType="user">
<legacyInterop availability="3500" />
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="300" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:53:19.063" container="300" version="7" expireType="user">
<legacyInterop availability="3500" />
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="400" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:53:19.063" container="400" version="7" expireType="user">
<legacyInterop availability="3500" />
</category>
</categories>
</roamingData>
--------------------------------------------------------------------------------
Received from tls:192.168.4.66:5061 at 20/4/2011 16:53:29:311 (5564 bytes):
BENOTIFY sip:ocruchot@192.168.4.50:3451;transport=tls;line=snzn8sqm;ms-received-cid=3A6400;grid SIP/2.0
Via: SIP/2.0/TLS 192.168.4.66:5061;branch=z9hG4bKAB25B019.D77B79F8DCD5DC7F;branched=FALSE
Authentication-Info: NTLM qop="auth", opaque="4F0C4B50", srand="2EF290DF", snum="48", rspauth="010000002096bad9ccffd0da64000000", targetname="CDU-LYNC-4.Immersion.fr", realm="SIP Communications Service", version=4
Max-Forwards: 70
To: <sip:ocruchot@immersion.fr>;tag=x2zkxhe4b3;epid=00041341205501
Content-Length: 4780
From: <sip:ocruchot@immersion.fr>;tag=E9260080
Call-ID: 7770263c94b916cfb3fc340b44383431
CSeq: 8 BENOTIFY
Require: eventlist
Content-Type: application/vnd-microsoft-roaming-self+xml
Event: vnd-microsoft-roaming-self
subscription-state: active;expires=3101
<roamingData xmlns="http://schemas.microsoft.com/2006/09/sip/roaming-self" xmlns:cat="http://schemas.microsoft.com/2006/09/sip/categories">
<categories xmlns="http://schemas.microsoft.com/2006/09/sip/categories" uri="sip:ocruchot@immersion.fr">
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="2" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="state" instance="268435456" publishTime="2011-04-20T14:45:01.453" container="2" version="1" expireType="user">
<state xsi:type="aggregateMachineState" endpointId="39590d11-9e9f-53ca-ad2a-7244afb3af99" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="state" instance="1351495144" publishTime="2011-04-20T14:45:01.453" container="2" version="1" expireType="endpoint" endpointId="39590D11-9E9F-53CA-AD2A-7244AFB3AF99">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="false" xsi:type="machineState">
<availability>3500</availability>
</state>
</category>
<category name="state" instance="536870912" publishTime="2010-12-10T11:16:59.600" container="2" version="1" expireType="static">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="true" xsi:type="userState"><availability>3500</availability></state>
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="3" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="state" instance="1351495144" publishTime="2011-04-20T14:45:01.453" container="3" version="1" expireType="endpoint" endpointId="39590D11-9E9F-53CA-AD2A-7244AFB3AF99">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="false" xsi:type="machineState">
<availability>3500</availability>
</state>
</category>
<category name="state" instance="536870912" publishTime="2010-12-10T11:16:59.600" container="3" version="1" expireType="static">
<state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" manual="true" xsi:type="userState">
<availability>3500</availability>
</state>
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="100" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:53:19.063" container="100" version="7" expireType="user">
<legacyInterop availability="3500" />
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="200" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:53:19.063" container="200" version="7" expireType="user">
<legacyInterop availability="3500" />
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="300" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:53:19.063" container="300" version="7" expireType="user">
<legacyInterop availability="3500" />
</category>
<category name="state" instance="1" publishTime="2011-04-20T14:53:19.063" container="400" version="7" expireType="user">
<state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"><availability>3500</availability></state>
</category>
<category name="legacyInterop" instance="1" publishTime="2011-04-20T14:53:19.063" container="400" version="7" expireType="user">
<legacyInterop availability="3500" />
</category>
</categories>
</roamingData>
Très embettant en production, le support snom n'étant pas très réactif sur le sujet.
Donc la résolution est la suivante:
- Passer en firware 8.4.4.6
- Dans Identity -> RTP: désactiver Symmetrical RTP et RTP Encryption
Normal 0 21 false false false FR X-NONE X-NONE MicrosoftInternetExplorer4
Normal 0 21 false false false FR X-NONE X-NONE MicrosoftInternetExplorer4
Lors d'une réunion d'avant projet Lync vendredi de la semaine dernière, cette question était justement abordé, est-ce que l'on peut utiliser SQL Server 2008 R2?
Conformément aux environnements base de donnée supporté par Microsoft (pour rappel: http://technet.microsoft.com/en-us/library/gg398990.aspx), la réponse fut non, cela ne sera plus le cas maintenant.
Cela devrait apparaitre très prochainement dans l'ensemble des ressources techniques publiés par Microsoft.
Mise à jour des firmwares OCS snom édition pour les modèles 8XX et Meeting point.
Description:
Summary – snom 8.6.6.4 OCS Edition introduces these OCS Enhanced Features
Microsoft vient de mettre en ligne la version web scheduler pour Lync, pour rappel, cela permet au travers d'un navigateur de programmer une réunion avec Lync.
Le msi et la documentation sont téléchargeables ici: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b7d8f948-fa64-4c51-8b54-2223954d1fa4&displaylang=en
Description:
Lync Web Scheduler is a resource kit tool for Microsoft® Lync Server 2010. It provides a Web-based alternative to the add-in for the Microsoft Office Outlook® messaging and collaboration client for the purpose of scheduling a meeting using Lync Server 2010. It also provides a browser-based conference management experience that includes operations such as the following:
Microsoft vient de publier un document intéressant concernant les fonctionnalités supportées dans le cadre de la virtualization du client Lync 2010 (donc ne concerne pas la partie serveur Lync).
Qu'est-ce que la virtualisation du client:
Client virtualization (also known as desktop virtualization), as a concept, separates a PC desktop environment from the device used to access the environment, by using a client/server model of computing. This model stores the resulting “virtualized” desktop on a remote server instead of on the local storage of the access device. Therefore, when users work from their access device, all applications, processes, and data are kept and run on the server. Client virtualization lets users access their desktops on any capable device, for example, a PC, notebook computer, smartphone, or thin client. The main benefits of client virtualization are improved manageability, data security, and “anywhere” data access for end-users.
Les clients supportés sont :
- Lync 2010
- Lync group chat 2010
La partie attendee, la console opérateur/opératrice, Lync Wep App ne sont pas supportés par Microsoft.
Seul les environnements suivants sont supportés dans le cadre de la virtualisation du client Lync 2010 et Lync Group Chat 2010:
Normal 0 21 false false false FR X-NONE X-NONE
|
Vendor |
Product |
Microsoft Lync 2010 |
Microsoft Lync 2010 Group Chat |
|
Microsoft |
Remote Desktop Services (RDS) |
Supported |
Supported |
|
App-V |
Supported |
Not supported |
|
|
Citrix |
XenDesktop |
Supported |
Supported |
|
XenApp |
Supported |
Not supported |
Voici un petit récapitulatif des environnements:
Normal 0 21 false false false FR X-NONE X-NONE
Full Desktop Remoting: In this mode, the entire desktop is remotely accessed by using either session virtualization or VDI.
Application Remoting: In this mode, a given application or a set of applications run on a remote server and accessed without remoting the entire desktop.
Application Streaming: In this mode, an application is virtualized by sequencing it, and deploying the sequenced version in the data center, in such a way that users can access and run the application on their local device without installing the application.
avec les fonctionnalités supportées pour chaque type d'environnement et client:
Lync 2010:
Normal 0 21 false false false FR X-NONE X-NONE
|
Feature |
Full Desktop Remoting |
Application Remoting |
Application Streaming [1] |
|
Presence |
Supported |
Supported |
Supported |
|
Instant Messaging |
Supported |
Supported |
Supported |
|
Desktop Sharing |
Supported |
Not Supported |
Supported |
|
Application Sharing |
Supported |
Not Supported |
Supported |
|
Sharing PowerPoint Presentations |
Supported |
Not Supported |
Supported |
|
Sharing Whiteboards |
Supported |
Supported |
Supported |
|
File Transfer |
Supported |
Supported |
Supported |
|
Audio |
Desk phone paired using USBR[2] |
Not Supported |
Supported |
|
Recording |
Not Supported |
Not Supported |
Supported |
|
Video |
Not Supported |
Not Supported |
Supported |
|
Online Meetings |
Supported [3] |
Supported ³ |
Supported [4] |
[1] Application Streaming was verified on Microsoft products. For details, see the “Vendor Support” section earlier in this document.
[2] Audio is supported only in a VDI environment. Audio is not supported in a session-based desktop delivery environment such as Microsoft RDS.
[3] Communication modes for Online Meetings are limited by peer-to-peer communication modes supported for the specified architecture. For example, if audio is not supported on the specified architecture, audio will not work in Online Meetings.
[4] Joining online meetings from Microsoft Outlook meeting reminder and/or meeting invitation is not supported.
Lync Group Chat 2010:
Normal 0 21 false false false FR X-NONE X-NONE
|
Feature |
Full Desktop Remoting |
Application Remoting |
Application Streaming |
|
Presence |
Supported |
Supported |
Not Supported |
|
Instant Messaging |
Supported |
Supported |
|
|
Chat Message |
Supported |
Supported |
|
|
File Upload |
Supported |
Supported |
|
|
Creating and Managing Chat Rooms |
Supported |
Supported |
|
|
Admin Tool |
Supported |
Supported |
Table 4 Supported features for Lync 2010 Group Chat client in a virtualized environment
On en vient maintenant aux limitations:
En full destkop remoting:
Pour la partie Audio:
Normal 0 21 false false false FR X-NONE X-NONEAudio is supported only through pairing of desk phones running Lync 2010 Phone Edition with USBR.
Pour la partie Vidéo:
Non supporté. Microsoft nous recommande même dans la stratégie client de désactiver ces fonctions:
Normal 0 21 false false false FR X-NONE X-NONE- Turn off “EnableP2PVideo”
Pour l'enregistrement:
Non supporté, il faut désactiver la fonction aussi : Turn off “AllowRecording”
Normal 0 21 false false false FR X-NONE X-NONEApplication remoting:
Audio, vidéo et enregistement non supporté
Microsoft vient de publier un guide de sécurité instructif dans le cadre d'un environnement Lync Server 2010.
Description:
Even if your Lync Server 2010 deployment is modest, you probably have
components in your network that are the subject of books devoted to
their security. Therefore, it is unlikely that this guide covers all
aspects of security for all components and areas that are pertinent to
your deployment.
Use this Security Guide as a starting point to
help secure and maintain a secure Lync Server 2007 deployment. This
guide provides general guidelines, including best practices, for
assessing and managing the most common security risks for Lync Server
2010. As new threats and solutions arise, you should supplement or
replace outdated documents, solutions, and methods with new ones.
The Security Guide addresses the following:
Vous pouvez le télécharger ici: http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=1400504e-8b2e-4d75-b091-1bf9f7bbc46f&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+MicrosoftDownloadCenter+%28Microsoft+Download+Center%29
Comment personnaliser le message générer lors de la création d'une réunion? c'est une question qui revient systématiquement.
La documentation Microsoft ne laisse pas beaucoup de solution: http://technet.microsoft.com/en-us/library/gg398638.aspx
You can customize the Online Meeting Add-in for Microsoft Lync 2010 in the following ways:
In addition, users can change the language of the meeting invitation to English, when non-English versions of the Microsoft Outlook messaging and collaboration client and Microsoft Lync 2010 are installed.
Les possibilités de la deuxième option ne laisse pas trop de place à une personnalisation du message:
| Parameter | Default | Description |
|---|---|---|
|
AllowAnonymousParticipantsInMeetings |
True |
If False, the access option Everyone including people outside my company (no restrictions) is unavailable. |
|
AllowIPAudio |
True |
If False, the access option People dialing in by phone bypass the lobby is unavailable. |
|
EnableDialInConferencing |
True |
If False, the access option People dialing in by phone bypass the lobby is unavailable. |
|
AllowAnonymousUsersToDialOut |
False |
If True, unauthenticated users can join the meeting by having Lync Server call them. |
| Parameter | Default | Description |
|---|---|---|
|
PstnCallersBypassLobby |
True |
If False, the access option People dialing in by phone bypass the lobby is unavailable. |
|
DesignateAsPresenter |
Company |
The other settings are None and Everyone. If None, the presenter option Organizer only is the default. If Everyone, the presenter option Everyone including people outside my organization (there are no restrictions) is the default. |
|
EnableAssignedConferenceType |
True |
If False, the creation of meetings that have a set conference ID specific to the organizer is disabled. If True, the same conference ID is used for every meeting where the organizer has not changed the default meeting options. |
|
AssignedConferenceTypeByDefault |
True |
If False, each new meeting is given a unique meeting ID.  Note:
This parameter has no effect if EnableAssignedConferenceType is set to False.
|
|
AdmitAnonymousUsersByDefault |
True |
If False, the access option Everyone including people outside my company (no restrictions) is unavailable. This global setting is used if no specific conferencing policy has been created. |
Voici un exemple de personnalisation avec une règle de transport effectué dans un environnement de test Lync Server 2010/Exchange 2010 (pas très beau mon exemple je sais):
C'est de l'html, donc les possibilités de personnalisation sont larges.
Cela peut-être effectué sous Exchange 2007 ou 2010:
Dans mon exemple avec Exchange 2010, cela se fait facilement avec EMC:
Préciser la valeur dans la condition: Every Lync 2010 meeting request contains a hidden text identifier, [!OC([1033])!]
L'action:
J'ai mis un exemple relativement simple:
<b>Vous pouvez télécharger le client Lync Attendee si vous avez les droits d'administrateurs ici: <A HREF="URL">http://www.microsoft.com/downloads/fr-fr/confirmation.aspx?FamilyID=1772a5ad-9688-4861-8387-ec30411bf455</A>
<br>
<br>
Si vous n'avez pas les droits d'administrateur: <A HREF="URL">http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=68a3ca04-a058-4e47-98ea-9e9af7ebd6e3&displaylang=en</A>
</b><br><br>
<hr>
<b>%%DisplayName%%</b><br>
<font size=small>
%%Department%% - %%Company%% <br>
%%StreetAddress%% - %%City%% - %%StateOrProvince%% - %%PostalCode%% <br>
Telephone: %%Phone%% / Fax: %%Fax%% / Mobile: %%MobilePhone%%<br><br>
<h5> <font color=gray>
The content of this e-mail (including any attachments) is strictly confidential and may be commercially sensitive. If you are not, or believe you may not be, the intended recipient, please advise the sender immediately by return e-mail, delete this e-mail and destroy any copies.
</h5>
Je suis tout a fait preneur d'une autre solution!
De nouvelles mises à jours sont disponibles:
Normal 0 21 false false false FR X-NONE X-NONE
Server-side updates
Client-side updates
The Lync Server 2010 Resource Kit is the technical reference for the product. This book extends the product planning, deploying, and managing documentation in the Lync Technical Library. This book serves as a companion to the product documentation to learn how the product works under the hood.
Normal 0 21 false false false EN-US X-NONE X-NONE
Integration of Lync 2010 with SharePoint Server provides users a seamless experience with the following SharePoint features:
· Presence within SharePoint site collections
· Skill search
· SharePoint pictures displayed in Lync 2010
· Export meeting recordings to SharePoint asset libraries
Documentation:
Sharepoint Integration Ressource Kit: http://www.microsoft.com/downloads/info.aspx?na=46&SrcFamilyId=8C64A1E1-F0B3-479C-A265-E480875C61D8&SrcDisplayLang=en&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f9%2f4%2fE%2f94ED1EF4-A2EF-4686-9841-B0390072D524%2fSharePoint_Integration.docx
Citrix vient d'annoncer et de publier un document très interessant concernant la mise en place d'un environnement Lync Server avec Citrix XenDesktop 5.0: http://support.citrix.com/article/CTX128831
Summary
This article provides guidelines for configuring XenDesktop 5 to deliver Microsoft Lync (formerly Microsoft Office Communicator). Microsoft Lync is a unified communications client used with Microsoft Lync Server that provides instant messaging, voice chat and desktop video conferencing. Citrix XenDesktop with HDX RealTime allows users to communicate using the voice chat and video chat features of Microsoft Lync.
There are three scenarios where HDX RealTime is used with Lync:
This article describes how to get the best results from both products in these scenarios. It is split into two sections; the first section deals with any configuration changes needed to the XenDesktop 5 environment and the second section looks at Microsoft Lync itself.
For information on using XenApp 6 to deliver Microsoft Office Communicator, see CTX124655 - Best Practice: How to Configure XenApp 6 for Microsoft Office Communicator 2007 R2.
Blackberry supporte officiellement Microsoft Lync Server 2010 et Office Communication Server 2007 R2 dans sa version 5.0 SP3 :
Source: http://docs.blackberry.com/en/admin/deliverables/25751/New_in_this_release_503_1311756_11.jsp
Configuration: http://docs.blackberry.com/en/admin/deliverables/25747/Provisioning_BCS_as_a_trusted_application_1396931_11.jsp
Un produit très interessant a été développé autour de Lync Server 2010, il s'agit de wave Lync Communicator.
WAVE Lync Communicator s'étend Lync en ajoutant la connectivité push-to-talk (PTT) entre les users dans un bureau et leurs collègues "mobiles" qui utilisent des talkies-walkies et les téléphones intelligents. De cette façon, WAVE Lync Communicator se dégrade très réels obstacles à la communication trouvé avec la radio bidirectionnelle et d'autres systèmes de communication propriétaires et permet de connecter les personnes en toute sécurité quand et où les communications en direct est indispensable.
Les utilisateurs de Microsoft Lync peuvent également instantanément PTT avec les utilisateurs de smartphones équipés d'une application WAVE Mobile Communicator.
Le WAVE Communicator Mobile pour Windows Mobile, Blackberry et d'autres plates-formes de smartphone leader offre des capacités de PTT et LMR, les dispositifs peuvent être pleinement intégrés dans tout scénario de la communication comme un combiné radio complémentaire ou de remplacement.
Le WAVE Lync Communicator a également la possibilité d'afficher les informations de présence directement sur une carte des utilisateurs de Bing WAVE communicateurs mobiles et les utilisateurs de radio-GPS pris en charge par le push-to-talk. Cette capacité est extrêmement important où il est essentiel de savoir où vos ressources sont déployées sur le terrain
Je n'ai pas encore détecté de projet nécessistant ce type d'extention à l'environnement mais si j'ai l'occasion de le deployer en production, cela serait une belle expérience.
Plus d'information ici: http://www.twistpair.com/index/wave-lync-communicator
Vidéo ici: http://www.twistpair.com/index/wave-lync-video
