Le Cloud de Christophe BOUCETTA

Voici le blog sur les communications unifiées et la collaboration Microsoft par un MVP nominé depuis 11 ans
  • [Microsoft Lync Server 2010] Client Lync Mobile

    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:

    1. A set of backend servers talking to Lync, AD and Exchange.
    2. A web-service, exposting REST endpoints – talking JSON to ease interopability (custom development towards it) and reduce bandwidth.

    Les pré-requis:

    1. Lync.
    2. The backend has been developed, run and tested on Windows Server 2008 R2. We haven’t done anything on our side to prevent 2008 or 2003 R2 to prevent stuff working there.
    3. .NET 3.5 SP1 is required on the server running connection to the Lync server in the backend.
    4. .NET 4.0 on the other servers – the frontend/gateway is implemented in WCF4, so .NET 4, IIS and needs to be visible/exposed on the internet.

    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

     

     

     

     

     

  • [Microsoft Lync Server 2010] SNOM 870, l'appel coupe au bout de 6 minutes

    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

  • [Microsoft Lync Server 2010] Support SQL Server 2008 R2

    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.

  • [Microsoft Lync Server 2010] snom OCS edition 8.6.6.4

    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

    • Improved display of presence state of contacts on snom 8xx models.
    • Ability to dial by selecting a contact and pressing ü key. 
    • Phone now enforces PIN lock per "Active Directory" requirements 
    • By default, phone web access is only by HTTPS. 
    • Added Microsoft Office Communications Server 2007 R2 / Lync 2010 server side addressbook search
    1. Added presence support to call history
    2. Added security support for serverside enforced keyboard lock
    3. Added support for MWI with Exchange 2010 SP1
  • [Microsoft Lync Server 2010] Web scheduler

    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:

    • Scheduling a new online Lync meeting.
    • Listing all existing Lync Server 2010 meetings that the user has organized.
    • Viewing and modifying details of an existing meeting.
    • Deleting an existing meeting.
    • Sending an email invitation to meeting participants by using a configured SMTP mail server.
    • Joining an existing conference.
  • [Microsoft Lync Server 2010] Virtualisation du client Lync 2010

    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-NONE

    Audio 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 “AllowIPVideo" 

    - 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-NONE

    Application remoting:

    Audio, vidéo et enregistement non supporté





    Normal 0 21 false false false FR X-NONE X-NONE
  • [Microsoft Lync Server 2010] Guide de sécurité

    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:

    • Key Security Enhancements in Lync Server 2010
    • Common Security Threats for Lync Server 2010
    • Security Framework for Lync Server 2010
    • Addressing Threats to Your Core Infrastructure
    • Addressing Threats to Your Internet Boundary
    • Addressing Threats to On-Premises Conferencing
    • Addressing Threats to Group Chat
    • Addressing Threats to Lync Web App
    • Addressing Threats to Enterprise Voice
    • Securing Clients for Lync Server 2010
    • Additional Security Resources for Lync Server 2010

     

    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

  • [Microsoft Lync Server 2010] Personnaliser le message d'une réunion en ligne

    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:

    • By adding custom text to a meeting request by using a Microsoft Exchange Server 2010 or Microsoft Exchange Server 2007 Hub Transport Server transport rule
    • By configuring available meeting options and meeting-option defaults by using Microsoft Lync Server 2010 in-band provisioning

    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:

    CSConferencingPolicy Meeting Option Parameters

    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.

    CSMeetingConfiguration Meeting Option Parameters

    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.

    Gg398638.note(en-us,OCS.14).gifNote:
    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!

  • [Microsoft Lync Server 2010] cumulative update (CU2)

    De nouvelles mises à jours sont disponibles:

    Normal 0 21 false false false FR X-NONE X-NONE

    Server-side updates

    Client-side updates

  • [Microsoft Lync Server 2010] Resource Kit: SharePoint Integration

    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