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

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

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

---

[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é

Documentation: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=f865e66d-1163-46ef-ba9c-d585376dfbae

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

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

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

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. 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:

• For Exchange 2010, see http://go.microsoft.com/fwlink/?LinkId=202494.
• For Exchange 2007, see http://go.microsoft.com/fwlink/?LinkId=202498

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

• Lync 2010 Group Chat Server – KB2500447 - download
• Lync 2010 Group Chat Admin – KB2500445 - download

Client-side updates

• Lync 2010 (Communicator) – KB2496325 – download (x86 / x64)
• Lync 2010 Phone Edition (Tanjay) – KB2529974 - download
• Lync 2010 Phone Edition (Aries-Aastra) – KB2529978 - download
• Lync 2010 Phone Edition (Aries-Polycom) – KB2529977 - download
• Lync 2010 Attendee (Admin Install) – KB2500438 - download
• Lync 2010 Attendee (User mode install) – KB2500440 - download
• Lync 2010 Attendant – KB2496326 - download (x86 & x64 combined)
• Lync 2010 Group Chat Client – KB2500446 - download

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:

Voice chat using Voice-over-IP. This feature of Lync is much like using a telephone. It enables users to chat in real time using a headset or USB telephone connected to their computer or thin client.
Video conferencing as an observer (voice-only participant). A user may choose to join in a video conference as a voice-only participant. The user can view the video conference and participate in the conversation but does not use a webcam.
Video chat using a webcam.

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 :

What's new in BlackBerry Enterprise Server 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

Les webcasts pour ceux qui n'ont pas assisté aux techdays 2011(comme moi étant en projet) ou qui souhaitent revoir ces sessions sont disponibles sur ce lien:

http://www.linkedin.com/news?viewArticle=&articleID=426573894&gid=3620761&type=member&item=47357507&articleURL=http%3A%2F%2Fbit.ly%2Fh5UCKw&urlhash=_Hvn&goback=.gde_3620761_member_47357507

Que la version lync mobile est attendu! C'est une question que l'on me pose en permanence que ce soit lors d'une prestation,en avant-vente, au centre des usages....

Un client "unofficial" est sorti sur le store Windows.

Il est possible de voir une vidéo ici http://forums.thoughtsmedia.com/f398/unofficial-lync-windows-phone-7-client-coming-soon-105200.html

Des screenshots/exemples de fonctionnalités ici: http://www.marketplacebrowser.com/277762/lp?amp&amp

Fonctionnalités:

a. Perform normal chat, presence management, note editing etc.
b. Manage contacts, groups etc. in Lync.
c. View contacts’ calendars.
d. Search contacts in AD.
e. Manage multiple profiles – ideal for ie. Consultants and others who could connect to multiple locations. Some of you who notice that we store credentials on the phone (AES enctrypted)…. The server can set a policy preventing this on the devices, and the devices honor that.
2. A server bundle consisting of:
a. Backend services facilitating Lync integration via UCMA 3.0.
b. Backend services facilitating contact calendar integration via managed EWS.
c. Gateway service exposing all functionality to backend as REST services – called from WP7 app.

Je ne l'ai pas encore testé mais je devrais faire un article plus complet prochainement.

J'avais déjà auparavant parlé de l'intégration ocs-lync/polycom.

L'intégration d'un système de salle HDX est relativement accessible mais oblige a prendre certains points en compte, comme l'obligation d'acquérir une licence multipoint (possibilité d'une conférence avec 3 clients lync - 3+1 ), l'impossibilité pour un système de salle de rejoindre une conférence hébergé par Lync (très problématique), une qualité de la vidéo en CIF.

La future sortie prévu en juin 2011 de la wave 4.1 supportera le RTV et donc pourra venir rejoindre une réunion hébergé par un mcu lync.

Cette option sera soumis à licence, mais n'obligera plus l'acquisition d'une licence multipoint, reste à savoir maintenant les limitations à tout cela.

Actuellement avec  Wave version 4 seulement CIF (Common Intermediate Format) est pris en charge qui est un standard de l'industrie de résolution de visioconférence H.263 (352 × 288 pixels), avec l'arrivée de la version 4,1, RTV VGA sera utilisé par défaut, lorsqu'elles sont disponibles. Cela améliore la qualité sur la résolution CIF beaucoup. A 640 × 480 (4:3); Il sera egalement disponible avec RTV est une résolution de 720p HD 1280 × 720 (16:9).

Plutôt une bonne nouvelle qui va rendre l'intégration encore plus accessible que ce soit pour l'intégrateur ou le client.

Une erreur arrive systématiquement lorsque vous activez un utilisateur ayant des droits d'administrateur:

Pour pouvoir malgré tout l'activé pour qu'il bénéficie des services fourni par Lync Server, il suffit de cocher dans l'onglet securité -> avancée de l'utilisateur:

Un outil sympa est disponible pour le client Lync: Lync 2010 Translator téléchargeable ici http://translator.gotuc.net/

Suite à l'installation de la clé de registre sur le poste client, vous aurez un outil de traduction directement intégré dans votre client :

Il suffit juste d'indiquer la langue source et destination, et le tour est joué!

Voici un petit utilitaire de tchat que j'avais évoqué avec OCS 2007 R2: Pidgin.

Il fonctionne aussi avec Lync Server 2010.

Le client se télécharge ici: http://www.pidgin.im/

Il faut aussi télécharger SIPE: http://sourceforge.net/projects/sipe/files/sipe/

La dernière version de SIPE ne contient pas deux fichiers indispensables pour avoir l'option "Office Communicator" iconv.dll et  libxml2.dll téléchargeable ici:  http://sourceforge.net/projects/sipe/files/sipe/pidgin-sipe-1.10.0/

Il faudra mettre ces deux fichiers dans le répertoire racine d'installation de pidgin.

On peut maintenant ajouter un compte dans pidgin pour se connecter au serveur Lync:

Sélectionner "use kerberos" et décocher "Use Single Sign-On"

Et voilà!

Un outil gratuit qui fonctionne aussi sous linux, par contre, pas d'audio ni vidéo.

Un outils pour faciliter le déploiement des postes téléphoniques IP Snom est disponible ici sous le nom de snomtastic: http://snomtastic.codeplex.com/releases

Sa description:

Snomtastic helps make your deployment of Snom VOIP handset with OCS / MCS (Microsoft Office Communications Server) 2007 R2 and Lync deployment easy!

This code complete application has a web service and client app to make deploying, managing, and configuring your Snoms easy!

Plus de documentation ici: http://snomtastic.codeplex.com/documentation

Un descriptif ici: http://www.snomchannel.com/voip-news/ocs-down-under-the-sydney-harbour-foreshore-authority-chooses-snom-ocs-edition/

Je ferais bientôt un article plus complet décrivant avec copie d'écran son fonctionnement.

Microsoft vient de rendre disponible un white paper très intéressant sur la Virtualization avec Lync Server 2010, vous pouvez le télécharger ici: Normal 0 21 false false false FR X-NONE X-NONE MicrosoftInternetExplorer4 http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2905fd33-e29c-4709-a012-e55ea8db63e4

Suite à un problème de téléchargement de sa configuration, j'ai eu un téléphone qui est resté dans l'état "SOS Phone in Recovery Mode".

Pas de panique, il suffit de récupérer l'utilitaire SPA50xG IP Phone Recovery: https://csc-test1.cisco.com/servlet/JiveServlet/download/10011-1-66712/spa50x-7-4-4-recovery.zip

Il faut suivre la procédure suivante:

When the phone is trying to access the “last upgrade URL”, it will not be able to handle a recovery request from the PC. Once the phone gives up, you will be able to successfully use the recovery utility:

1. Make sure the default TFTP port (69) is not occupied on the computer. For example if you have a TFTP server such as Pumpkin or SolarWinds running, shut the TFTP service down.
2. You might have to disable the firewall or other security measures on the PC to allow TFTP to function properly.
3. Run the recovery utility and enter the phone’s SN when prompted. You can use “FFFFFFFFFFFF” (12 ‘F’s) instead of the phone's serial number.
4. The recovery utility should find the phone in recovery mode.
5. Follow the instructions on screen to start the recovery process.
6. Once the phone has recovered and rebooted, you can upgrade to the desired version of firmware.

Et voilà, votre téléphone redémarre correctement!

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

Plantronics a sorti une nouvelle gamme de téléphone plutôt originaux, les Calisto 800 :

Ils sont déclinés en 3 modéles:

- P825-M (PC + mobile phone with wireless mic)

- P830-M (PC + mobile phone + home landline)

- P820-M (PC + mobile phone)

Un très intéressant descriptif du produit couplé à du Lync est disponible sur ce lien: http://voipnorm.blogspot.com/2011/02/device-review-plantronics-calisto-825m.html

Microsoft vient de mettre à disposition en téléchargement BPA pour Microsoft Lync Server 2010.

Vous pouvez utiliser Lync Server 2010 Best Practices Analyzer pour vérifier les composants de votre environnement.

Basé sur un ensemble complet de règles pour permettre une sélection poussée des environnements Lync, BPA fournit des conseils pour l'installation, l'utilisation et la mise à jour, ainsi que des informations sur les principales questions que vous pouvez utiliser pour dépanner et résoudre des problèmes spécifiques.

Il est disponible en téléchargement à partir de ce lien: Normal 0 21 false false false FR X-NONE X-NONE http://go.microsoft.com/fwlink/?LinkID=211230

Lync Server 2010 étant tout récent, les livres décrivant le sujet ne sont pas légion. Microsoft Lync Server 2010 Unleashed coécrit par Alex Lewis, Andrew Abbate et Tom Pacyk devrait être disponible à partir d'avril 2011.

La description: