toml-lcskid Live Communications Server

After working on this issue I am not sure I can truly say I am a Mac novice but for the purposes of this audience I will mention that I do not use the Mac on a daily basis. Although the new iMac 24" with Bootcamp and Parallels for Vista is being discussed with my financial advisor (wife) :)

Ok so onto the problem - There can be many different behaviors reported and include:
1) Windows workstations with Office Communicator are unable to send an IM successfully to the Mac Messenger workstation. The Mac Messenger client will never receive the IM and Office Communicator will generate an error about not delivering the IM between 1-3 minutes.
2) The Mac client can send the OC client an IM and the OC client will receive it but be unable to reply. The experience will be a one way conversation where OC receives all IMs sent from the MAC and the MAC will receive no replies.
3) We did see other behaviors when testing that could not be duplicate and that included an initial IM from the MAC received by Communicator with out the actual text. The IM "toast" (small popup at the bottom of the screen) included the text but the IM conversation window did not.
4) Intermittent IM between the MAC and OC clients in which some of the OC messages were received by the MAC user but not all.

The resolution is easy enough - wait and watch for the Mac Messenger 6.0 release. Thanks to Michele and Eric for their patience and diligence in working with me and providing the necessary information to reproduce this issue. Included below is the technical analysis of the issue with the root cause.

As the issue was not affecting all Mac Workstations we focused on what made these few workstations unique. The root cause of this problem appeared to be the customer's IP scheme which placed the problem Mac Messenger 5.1.1 systems on a supernet of IP and Subnet. The issues have all been resolved, at the time of this writing, with the beta version of Mac Messenger 6.0. There is always the rare possibility that between now and the RTM of the client this issue could reoccur (I hope not).

Below is the analyzed LCS Server logs for a failed IM from the OC client to the Mac Messenger client -
Invite received at the LCS Server from Communicator client

$$begin_record
LogType: protocol
Date: 2006/08/18 14:20:52
Direction: Incoming
Peer: 128.244.3.172:3786
Message-Type: Request
Start-Line: INVITE sip:mac-user@contoso.local SIP/2.0
To: <sip:mac-user@contoso.local>
From: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 INVITE
Contact: <sip:oc-user@contoso.local:3786;maddr=128.244.3.172;transport=tls>proxy=replace
Via: SIP/2.0/TLS 128.244.3.172:3786
Max-Forwards: 70
Content-Length: 126
Content-Type: application/sdp
Other-Headers: User-Agent: LCC/1.3
Other-Headers: Ms-Conversation-ID: 32D6496A-67A3-469C-8725-F08D53E6B33C
Other-Headers: Ms-Text-Format: text/plain; charset=UTF-8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AaQBjAHIAbwBzAG8AZgB0ACUAMgAwAFMAYQBuAHMAJQAyADAAUwBlAHIAaQBmADsAIABFAEYAPQBCADsAIABDAE8APQA4ADAAOAAwADAAMAA7ACAAQwBTAD0AMAA7ACAAUABGAD0AMgAyAA0ACgANAAoA;ms-body=MQ==
Other-Headers: Supported: ms-delayed-accept
Other-Headers: Supported: ms-renders-gif
Other-Headers: Roster-Manager: sip:oc-user@contoso.local
Other-Headers: EndPoints: "Office Communicator" <sip:oc-user@contoso.local>, <sip:mac-user@contoso.local>
Other-Headers: Supported: com.microsoft.rtc-multiparty
Other-Headers: Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="83A4EBBE", crand="eee6f6c1", cnum="174", targetname="sip/lcsserver.contoso.local", response="602306092a864886f71201020201011100ffffffffdc9c0c5e2de239e852186353977bb739"
Message-Body: v=0\no=- 0 0 IN IP4 128.244.3.172\ns=session\nc=IN IP4 128.244.3.172\nt=0 0\nm=message 5060 sip sip:oc-user@contoso.local
$$end_record

$$begin_record
LogType: diagnostic
Date: 2006/08/18 14:20:52
Severity: information
Text: Response successfully routed
SIP-Start-Line: SIP/2.0 100 Trying
SIP-Call-ID: 8ade0e910e814353abb38a91dac0de3a
SIP-CSeq: 1 INVITE
Peer: 128.244.3.172:3786
$$end_record

LCS Server replying to Communicator user workstation with 100 trying (note IP address)

$$begin_record
LogType: protocol
Date: 2006/08/18 14:20:52
Direction: Outgoing
Origin: Local
Peer: 128.244.3.172:3786
Message-Type: Response
Start-Line: SIP/2.0 100 Trying
To: <sip:mac-user@contoso.local>
From: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 INVITE
Via: SIP/2.0/TLS 128.244.3.172:3786;ms-received-port=3786;ms-received-cid=4000
Content-Length: 0
Other-Headers: Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF37CA39454D553FFA4BA312C4A3B9692A", srand="A81AEFCF", snum="373", opaque="83A4EBBE", qop="auth", targetname="sip/lcsserver.contoso.local", realm="SIP Communications Service"
$$end_record

$$begin_record
LogType: diagnostic
Date: 2006/08/18 14:20:52
Severity: information
Text: Routed a request on behalf of APIEM
SIP-Start-Line: INVITE sip:128.244.153.234:50372;transport=tls;ms-received-cid=24C00 SIP/2.0
SIP-Call-ID: 8ade0e910e814353abb38a91dac0de3a
SIP-CSeq: 1 INVITE
Peer: 128.244.153.234:50372
$$end_record

LCS Server sending Invite to mac user workstation (note IP address)

$$begin_record
LogType: protocol
Date: 2006/08/18 14:20:52
Direction: Outgoing
Peer: 128.244.153.234:50372
Message-Type: Request
Start-Line: INVITE sip:128.244.153.234:50372;transport=tls;ms-received-cid=24C00 SIP/2.0
To: <sip:mac-user@contoso.local>epid=0cb058af1a
From: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 INVITE
Contact: <sip:oc-user@contoso.local:3786;maddr=128.244.3.172;transport=tls;ms-received-cid=4000>
Via: SIP/2.0/TLS 128.244.198.22:5061;branch=z9hG4bKE31744A0.D6BB86C4;branched=FALSE;ms-internal-info="cajr5x1Tczx6BVg_53FGSW0odPQTsA"
Via: SIP/2.0/TLS 128.244.3.172:3786;ms-received-port=3786;ms-received-cid=4000
Max-Forwards: 69
Content-Length: 126
Content-Type: application/sdp
Other-Headers: Authentication-Info: NTLM rspauth="01000000682E08737855AFF764000000", srand="3C7DC434", snum="13", opaque="4252F741", qop="auth", targetname="lcsserver.contoso.local", realm="SIP Communications Service"
Other-Headers: Record-Route: <sip:lcsserver.contoso.local:5061;transport=tls;lr;ms-route-sig=cahdKz7QJ46fNofDr-EoVUodVA6qes>tag=AEF3CEF743455F6E8E381050237A9AEE
Other-Headers: User-Agent: LCC/1.3
Other-Headers: Ms-Conversation-ID: 32D6496A-67A3-469C-8725-F08D53E6B33C
Other-Headers: Ms-Text-Format: text/plain; charset=UTF-8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AaQBjAHIAbwBzAG8AZgB0ACUAMgAwAFMAYQBuAHMAJQAyADAAUwBlAHIAaQBmADsAIABFAEYAPQBCADsAIABDAE8APQA4ADAAOAAwADAAMAA7ACAAQwBTAD0AMAA7ACAAUABGAD0AMgAyAA0ACgANAAoA;ms-body=MQ==
Other-Headers: Supported: ms-delayed-accept
Other-Headers: Supported: ms-renders-gif
Other-Headers: Roster-Manager: sip:oc-user@contoso.local
Other-Headers: EndPoints: "Office Communicator" <sip:oc-user@contoso.local>, <sip:mac-user@contoso.local>
Other-Headers: Supported: com.microsoft.rtc-multiparty
Message-Body: v=0\no=- 0 0 IN IP4 128.244.3.172\ns=session\nc=IN IP4 128.244.3.172\nt=0 0\nm=message 5060 sip sip:oc-user@contoso.local
$$end_record

LCS server receiving 100 trying from mac user workstation

$$begin_record
LogType: protocol
Date: 2006/08/18 14:20:52
Direction: Incoming
Peer: 128.244.153.234:50372
Message-Type: Response
Start-Line: SIP/2.0 100 Trying
To: <sip:mac-user@contoso.local>epid=0cb058af1a;tag=c0f5fe982ec411db8d2f0014510d30fe
From: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 INVITE
Via: SIP/2.0/TLS 128.244.198.22:5061;branch=z9hG4bKE31744A0.D6BB86C4;branched=FALSE;ms-internal-info="cajr5x1Tczx6BVg_53FGSW0odPQTsA"
Via: SIP/2.0/TLS 128.244.3.172:3786;ms-received-port=3786;ms-received-cid=4000
Content-Length: 0
Other-Headers: User-Agent: RTC/1.3
Other-Headers: Proxy-Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="4252F741", crand="43d57ff6", cnum="11", targetname="lcsserver.contoso.local", response="01000000ca284c89fc709a0064000000"
$$end_record

LCS server receiving 200 ok from mac user workstation

$$begin_record
LogType: protocol
Date: 2006/08/18 14:20:52
Direction: Incoming
Peer: 128.244.153.234:50372
Message-Type: Response
Start-Line: SIP/2.0 200 OK
To: <sip:mac-user@contoso.local>epid=0cb058af1a;tag=c0f5fe982ec411db8d2f0014510d30fe
From: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 INVITE
Contact: <sip:mac-user@contoso.local:50372;maddr=128.244.153.234;transport=tls>proxy=replac?
Via: SIP/2.0/TLS 128.244.198.22:5061;branch=z9hG4bKE31744A0.D6BB86C4;branched=FALSE;ms-internal-info="cajr5x1Tczx6BVg_53FGSW0odPQTsA"
Via: SIP/2.0/TLS 128.244.3.172:3786;ms-received-port=3786;ms-received-cid=4000
Record-Route: <sip:lcsserver.contoso.local:5061;transport=tls;lr;ms-route-sig=cahdKz7QJ46fNofDr-EoVUodVA6qes>tag=AEF3CEF743455F6E8E381050237A9AEE
Content-Length: 128
Content-Type: application/sdp
Other-Headers: User-Agent: RTC/1.3
Other-Headers: Supported: com.microsoft.rtc-multiparty
Other-Headers: Proxy-Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="4252F741", crand="5c6e7d9a", cnum="12", targetname="lcsserver.contoso.local", response="01000000b921c0335c4b850e64000000"
Message-Body: v=0\no=- 0 0 IN IP4 128.244.153.234\ns=session\nc=IN IP4 128.244.153.234\nt=0 0\nm=message 5060 sip sip:mac-user@contoso.local
$$end_record

Error processing the incoming 200 ok. No error back to Mac client, no response to Communicator client

$$begin_record
LogType: security
Date: 2006/08/18 14:20:52
Text: Error processing message
Result-Code: 0xc3ed1810 SIPPROXY_E_INVALID_CONTACT_PARAMS
SIP-Start-Line: SIP/2.0 200 OK
SIP-Call-ID: 8ade0e910e814353abb38a91dac0de3a
SIP-CSeq: 1 INVITE
$$end_record

LCS server receiving Bye from mac user workstation due to delay

$$begin_record
LogType: protocol
Date: 2006/08/18 14:21:25
Direction: Incoming
Peer: 128.244.153.234:50372
Message-Type: Request
Start-Line: BYE sip:lcsserver.contoso.local:5061;transport=tls;lr;ms-route-sig=cahdKz7QJ46fNofDr-EoVUodVA6qes SIP/2.0
To: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
From: <sip:mac-user@contoso.local>epid=0cb058af1a;tag=c0f5fe982ec411db8d2f0014510d30fe
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 BYE
Via: SIP/2.0/TLS 128.244.153.234:50372
Route: <sip:oc-user@contoso.local:3786;maddr=128.244.3.172;transport=tls;ms-received-cid=4000>
Max-Forwards: 70
Content-Length: 0
Other-Headers: User-Agent: RTC/1.3
Other-Headers: Proxy-Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="4252F741", crand="4c75f6bf", cnum="13", targetname="lcsserver.contoso.local", response="01000000f6ca5eb6709b750064000000"
$$end_record

$$begin_record
LogType: diagnostic
Date: 2006/08/18 14:21:25
Severity: information
Text: Routed a request using signed route headers
SIP-Start-Line: BYE sip:oc-user@contoso.local:3786;maddr=128.244.3.172;transport=tls;ms-received-cid=4000 SIP/2.0
SIP-Call-ID: 8ade0e910e814353abb38a91dac0de3a
SIP-CSeq: 1 BYE
Peer: 128.244.3.172:3786
$$end_record

LCS sending Bye to Communicator user workstation

$$begin_record
LogType: protocol
Date: 2006/08/18 14:21:25
Direction: Outgoing
Peer: 128.244.3.172:3786
Message-Type: Request
Start-Line: BYE sip:oc-user@contoso.local:3786;maddr=128.244.3.172;transport=tls;ms-received-cid=4000 SIP/2.0
To: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
From: <sip:mac-user@contoso.local>epid=0cb058af1a;tag=c0f5fe982ec411db8d2f0014510d30fe
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 BYE
Via: SIP/2.0/TLS 128.244.198.22:5061;branch=z9hG4bK6A79BB21.93EB5D17;branched=FALSE;ms-internal-info="caLD7SdtVt-EY6ragkVNDUT4dPQTsA"
Via: SIP/2.0/TLS 128.244.153.234:50372;ms-received-port=50372;ms-received-cid=24c00
Max-Forwards: 69
Content-Length: 0
Other-Headers: Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF21F61AEE9B22E3197E9CB9CE3E60EA21", srand="D2A21167", snum="375", opaque="83A4EBBE", qop="auth", targetname="sip/lcsserver.contoso.local", realm="SIP Communications Service"
Other-Headers: User-Agent: RTC/1.3
$$end_record

LCS receives 481 as Communicator client does not have the call leg setup given the above failure with 200 ok (her workstation needed that 200 ok for the call to be established)

$$begin_record
LogType: protocol
Date: 2006/08/18 14:21:25
Direction: Incoming
Peer: 128.244.3.172:3786
Message-Type: Response
Start-Line: SIP/2.0 481 Call Leg/Transaction Does Not Exist
To: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
From: <sip:mac-user@contoso.local>epid=0cb058af1a;tag=c0f5fe982ec411db8d2f0014510d30fe
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 BYE
Via: SIP/2.0/TLS 128.244.198.22:5061;branch=z9hG4bK6A79BB21.93EB5D17;branched=FALSE;ms-internal-info="caLD7SdtVt-EY6ragkVNDUT4dPQTsA"
Via: SIP/2.0/TLS 128.244.153.234:50372;ms-received-port=50372;ms-received-cid=24c00
Content-Length: 0
Other-Headers: User-Agent: LCC/1.3
Other-Headers: Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="83A4EBBE", crand="f5aa6aee", cnum="175", targetname="sip/lcsserver.contoso.local", response="602306092a864886f71201020201011100ffffffffb07bcf5412d9bc0c14931cce04c827c6"
$$end_record

$$begin_record
LogType: diagnostic
Date: 2006/08/18 14:21:25
Severity: information
Text: Response successfully routed
SIP-Start-Line: SIP/2.0 481 Call Leg/Transaction Does Not Exist
SIP-Call-ID: 8ade0e910e814353abb38a91dac0de3a
SIP-CSeq: 1 BYE
Peer: 128.244.153.234:50372
$$end_record

LCS sends the Mac a 481 response from Communicator client

$$begin_record
LogType: protocol
Date: 2006/08/18 14:21:25
Direction: Outgoing
Peer: 128.244.153.234:50372
Message-Type: Response
Start-Line: SIP/2.0 481 Call Leg/Transaction Does Not Exist
To: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
From: <sip:mac-user@contoso.local>epid=0cb058af1a;tag=c0f5fe982ec411db8d2f0014510d30fe
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 BYE
Via: SIP/2.0/TLS 128.244.153.234:50372;ms-received-port=50372;ms-received-cid=24c00
Content-Length: 0
Other-Headers: Authentication-Info: NTLM rspauth="01000000898048FC93C8E6D464000000", srand="99E5A17D", snum="15", opaque="4252F741", qop="auth", targetname="lcsserver.contoso.local", realm="SIP Communications Service"
Other-Headers: User-Agent: LCC/1.3
$$end_record

LCS receives Cancel from Communicator user workstation (due to timeout I believe)

$$begin_record
LogType: protocol
Date: 2006/08/18 14:23:37
Direction: Incoming
Peer: 128.244.3.172:3786
Message-Type: Request
Start-Line: CANCEL sip:mac-user@contoso.local SIP/2.0
To: <sip:mac-user@contoso.local>
From: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 CANCEL
Via: SIP/2.0/TLS 128.244.3.172:3786
Max-Forwards: 70
Content-Length: 0
Other-Headers: User-Agent: LCC/1.3
Other-Headers: Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="83A4EBBE", crand="d918a105", cnum="176", targetname="sip/lcsserver.contoso.local", response="602306092a864886f71201020201011100ffffffff3e6fd0b7603791178c16ffe12b716a79"
$$end_record

$$begin_record
LogType: diagnostic
Date: 2006/08/18 14:23:37
Severity: information
Text: Response successfully routed
SIP-Start-Line: SIP/2.0 481 Call leg unavailable
SIP-Call-ID: 8ade0e910e814353abb38a91dac0de3a
SIP-CSeq: 1 CANCEL
Peer: 128.244.3.172:3786
$$end_record

LCS Server responds to Communicator client with 481 as the call-leg is no longer available due to the Bye sent by Mac

$$begin_record
LogType: protocol
Date: 2006/08/18 14:23:37
Direction: Outgoing
Origin: Local
Peer: 128.244.3.172:3786
Message-Type: Response
Start-Line: SIP/2.0 481 Call leg unavailable
To: <sip:mac-user@contoso.local>tag=AEF3CEF743455F6E8E381050237A9AEE
From: "Office Communicator" <sip:oc-user@contoso.local>tag=27b77a6f2b;epid=dffd569509
Call-ID: 8ade0e910e814353abb38a91dac0de3a
CSeq: 1 CANCEL
Via: SIP/2.0/TLS 128.244.3.172:3786;ms-received-port=3786;ms-received-cid=4000
Content-Length: 0
Other-Headers: Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFFE58D11FFE9566CD206299D97C14A5D7A", srand="DE150E43", snum="376", opaque="83A4EBBE", qop="auth", targetname="sip/lcsserver.contoso.local", realm="SIP Communications Service"
$$end_record

Analyzing the error code provided this result -
10301 | $$begin_record
10302 | LogType: security
10303 | Date: 2006/08/18 14:20:52
10304 | Text: Error processing message
10305 | Result-Code: 0xc3ed1810 SIPPROXY_E_INVALID_CONTACT_PARAMS
10306 | SIP-Start-Line: SIP/2.0 200 OK
10307 | SIP-Call-ID: 8ade0e910e814353abb38a91dac0de3a
10308 | SIP-CSeq: 1 INVITE
10309 | $$end_record

C:\Program Files\Microsoft LC 2005\ResKit>lcserror 0xc3ed1810
0xc3ed1810 -> (SIPPROXY_E_INVALID_CONTACT_PARAMS) No description text found
0xc3ed1810 -> (SIPPROXY_E_INVALID_CONTACT_PARAMS) Bad request having an invalid contact parameter.

So for those of you out there with the Mac Messenger client, I hope that you can see how you can troubleshoot those clients with the LCS Server logging option and by using the same method of analysis to narrow the issue further.

TomL the MACKid  :)

Edit - adding the actual url :)

http://blogs.technet.com/uc

Sometimes a delay is a good thing and with the RTC blog never really getting off the ground there was room for improvement. Having such a big delay means we now get to focus a bit more on the new technology coming with Office Communications Server 2007.

Gurdeep has posted the first post for the official ribbon cutting (virtual of course). I don't know what we will get on the blog but I am hoping we take lessons from the Exchange team.

One thing to remember is that Gurdeep is head of the RTC technologies in Unified Communications so you will need to continue monitoring the Exchange group blog for the Exchange portion of Unified Communications. So if you see UC-RTC you will know that is how we refer to ourselves.

TomL LCSKid - pretty soon I will need a new UC* alias :)

<edits for minor grammatical errors>

It isn't entirely what you are thinking. My time as a beta engineer has come to a halt. I was fortunate to work the entire Communicator Web Access beta and the team graciously provided a Ship It award to me for my involvement. This is a plaque that holds up to 8 small metal squares with the product you helped have an impact on for shipping. While you might think that a beta engineer would get this routinely we don't. If you ship a lot of products due to be a developer this might be another plaque in the office but for those of us who don't get them it is an honor to receive that recognition. I know a group that lobbied for their team to get them and I have to say they put a lot of effort in it so having the product team do this without a prompt really made me feel as though the efforts were worth it.

I also worked on the Communicator Mobile release, near the end my other team mate Matt stepped in to back me up when I was on vacation and he really stepped in strong. He put together our training webcast of walking through setup and logging. He also built a virtual machine with Visual Studio and device emulation already configured for the devices we support.

While on these betas I also got looped in on "Live" Server, now Microsoft Office Communications Server 2007 (or as we say OCS) but that was such a long product cycle I knew my time was short lived. Beta 2 was the cutoff so the 3rd week of July was my last week supposedly to help with the 3 weeks of deployment. Well it is now the 3rd week of August and I think the 3 team members are just now starting to see customer issue volume. I went to TechReady3 by invitation of Jerry in our readiness team. He requested I co-speak in a chalk talk on telephony, specifically the remote call control (RCC, or 3rd Party Call Control 3PCC). Anyone who knew the 4 of us up there knew the Bob and Sam were the talent and Barry and I were the good looking ones ;) Seriously Bob and Sam came from other companies with real deployment experience and they KNOW this stuff.

So I then had a week of vacation since I didn't really get one in my time on beta (hard for the 1 support guy to not be there) and this week I was working on cleaning out our hardware closests, this of course because I wasn't scheduled for phones or customer time. Given that we have the family beach trip at the end of the month my manager and I have been discussing what next. The thought is of course to leverage my knowledge of LCS (given I have supported since the day it released) and to focus on this technology heavy, you have to know that our team supports all networking stuff (wireless, dns, dhcp, wins, network browsing, vpn, rras).

So this week I inherited a Mac Messenger with SIP issue and a PIC issue. Next week I get a few cases from team members on vacation and other issues that have hung around too long.

So the answer to the question has not been given yet, I expect it to be more of the same but you never know what other ideas management has with increasing scope and impact.

I am testing the new Writer beta for the blog. Nice compact window and rather simple options for the most used features I can think of using.

I don't think I can insert pictures on this site but let's try the process. So the insert is rather easy and if successful it is a black and white picture of my daughter.

And that fails because the sites don't allow for image upload. Now to figure out how to redirect uploads to another location... hmmmm..

I will have to test this with the personal blog, I like this a lot.

I really appreciate knowing that a lot of folks find the blog useful and am happy to have had opporunity to share the vouchers with you. I have received the 10 requests for vouchers.

TomL LCSKid

I received an email via the blogs from Arun this week about the options he has to connect to LCS while running a UNIX/Linux OS.

The Microsoft solution is Communicator Web Access, but this is a server install enabling browser support for clients. Like many of us Arun is not that admin so this is not an option.

3rd party clients is the only other way to go -

Trillian and Gaim are the two options I am aware of, and from an earlier post you can see that I use Trillian personally due to my support for Public Internet Connectivity (PIC) which requires me to be able to test AOL, MSN, Yahoo! accounts with customers. Trillian also offers a SIP plug-in for which I have used successfully while internal to our corporate network (it does not work when I am home via the Access Proxy for some reason).  Trillian is also a Windows only client so this won't be an option for any of the UNIX/Linux users.

Gaim offers a Windows and Open Source solution and I have tried both. I am not by any means someone you should think knows anything on Linux but I use the Ubuntu distro for my testing in a Virtual Machine. Our investigation on this issue appears to show that the way Gaim combines the server and alias information assumes information about the server deployment. What Arun and I have found in our testing shows that the client queries for the server but the server based on the alias won't work with a typical LCS deployment.

For example my alias is toml (at) microsoft (dot) com so there is a DNS SRV query for microsoft.com but our servers for lcs are host.microsoft.com so there will not be a valid connection.

What I said to Arun is that I believe the Gaim client was not likely written for the LCS product but for the other SIP products (open source) available. Thus we are at a stand still and if you have any info or thoughts let me know. Remember I am NOT a developer :)

TomL LCSKid

Yes we listen to your feedback about lacking support for various topologies or technologies and yes we work on it. For everyone who called support and spoke to our team you heard the "not supported" answer. What you have to remember is we feed that information through our Supportability Program Managers directly and also through our support call statistics. In this customers also feed the information through the sales team and that gets communicated via a few other internal channels and there is also the customers who say it is mandatory or else and they file Design Change Requests.

Nothing moves as fast as anyone wants but today we have reached the point of giving what you have asked for -

The RTC Product Group has now completed testing of Live Communications Server 2005 SP1 with SQL Server 2005 SP1, and is pleased to announce that LCS 2005 SP1 Enterprise Edition can now be deployed using either SQL 2000 SP3a and above or SQL 2005 SP1.

We’re also able at this time to communicate support for LCS 2005 SP1 (both Standard and Enterprise Editions) on Windows Server 2003 R2.

This means that customers who have standardized on SQL 2005, or beginning to deploy Windows Server 2003 R2, can now more readily deploy Live Communications Server.  

• LCS 2005 system requirements and supported environments http://www.microsoft.com/office/livecomm/prodinfo/sysreq.mspx
• Knowledge Base article #911996 details the pre-requisite steps required prior to deploying SQL 2005 SP1.

Supported Scenarios: LCS 2005 Enterprise Edition and LCS 2005 SP1 Enterprise Edition

• Database requirements: Installation of Live Communications Server 2005 Enterprise Edition requires a separate server running SQL Server 2000 Standard Edition, SQL Server 2000 Enterprise Edition with service pack 3a, SQL Server 2005 SP1 Standard Edition, or SQL Server 2005 SP1 Enterprise Edition.
• Archiving service requires: SQL Server 2000 Standard Edition, SQL Server 2000 Enterprise Edition, SQL Server 2005 SP1 Standard Edition, or SQL Server 2005 SP1 Enterprise Edition.

No changes have been made to the supported scenarios for LCS Standard Edition with respect to SQL 2005. This is of course due to the fact setup for Standard Edition installs MSDE and does not support a SQL back-end.

The product group released an update to Communicator Mobile on June 23. I believe this was a situation of taking advantage of our product cycle along with the localized versions but thought you might want to know. Typically if you have an issue the first words from us support folks will be "Did you test the latest version"? The reason for this is that any fix will be against the latest version.

Description of the update for Communicator Mobile: June 23, 2006

http://support.microsoft.com/?kbid=919950

Issues that the update fixes

This update for Communicator Mobile fixes the following issues:

•	919873 (http://support.microsoft.com/kb/919873/) You are not notified that a "File Transfer" or a "Remote Assistance" request from Communicator 2005 to Communicator Mobile could not be delivered
•	919874 (http://support.microsoft.com/kb/919874/) The home screen layout on a Moto Q device changes when Communicator Mobile is installed
•	919875 (http://support.microsoft.com/kb/919875/) A "Call Computer" request in Communicator 2005 is not established when the recipient is a Communicator Mobile user
•	919877 (http://support.microsoft.com/kb/919877/) Nothing occurs when you single-tap the "My Status" screen in Communicator Mobile on a Pocket PC
•	919878 (http://support.microsoft.com/kb/919878/) ActiveSync may try to install the incorrect version of Communicator Mobile on a device
•	919879 (http://support.microsoft.com/kb/919879/) Updated phone forward settings may not be displayed on a Windows Mobile-based Smartphone that uses Communicator Mobile
•	921460 (http://support.microsoft.com/kb/921460/) The bottom of the text in the second row of a contact note is truncated in Communicator Mobile

I would have bet that at one time I received all comments in email so I have just thought folks were viewing and consuming the blog posts. Thanks to Steve he mentioned having a problem. Turns out my comment settings were not correct.

I have attempted to resolve this and will monitor closer. At any time you have a question about a post you can always email my alias at microsoft, just strip off the lcskid piece!

TomL LCSKid

We recently had 2 customers encounter a very painful and labor intesive process working through issues with failed PIC configurations. Turns out they had an underscore in their pool names, you know something like - lcs_pool.domain.com.

So there shouldn't be a problem right? I mean the OS didn't stop me, the LCS setup didn't stop me, my remote users work and now 2 of 3 (MSN and Yahoo) can't work?

Turns out that the underscore is a character that we don't support. In some brief discussions it was mentioned that it was a non SIP compliant character but in my quick glances and searches through RFC's I don't know if that is true or not. So at this time let me say that it won't work.

Now I have to give credit to the team that always comes through on this for us - JB, CW and JU. For any customer who has ever been to a Microsoft event where the product group presents JB is the one talking about LCS and Certs and CW and JU have presented on our tools and troubleshooting. I say all this because I am fortunate enough to be able to email, im or call any of them for questions and they will always help if they have the time. JB of course had already entered a bug for the next product version to either support the underscore or block it during setup. Please recognize that this is for tracking and due to priority could be "punted" so this is not a post making any promises.

Have a great one,

This post is not about LCS and Communicator specifically but about IM in general. Due to my unique role in supporting our PIC customers (Public Internet Connectivity), I need to have an account on AOL/MSN/Yahoo! in order to test with the customer what they are experiencing. I don't really use any of the three accounts for IM but I given my employment and all 3 being free I of course make use of MSN (Hotmail) for email and IM.

I actually purchased Trillian Pro because of the SIP plug-in it offered. This allows me to start a Virtual PC with Windows XP and then load Trillian to my corporate account and all 3 cloud accounts. By the way to give you a screen shot of the client check out http://tomllcskid.blogspot.com/ I forgot about being able to upload a pic with each post and thought I might revisit the use of that site.

All of these background to point out an interesting article today about Trillian no longer being in the Google Pack. Maybe I am exposing the rock I live under but I had not heard of this pack although this could simply be due to the fact I am very wary of free software. So without knowing more than what this article says, what strikes me is how Google describes the products in their pack - Free, reputation for excellence and evaluated to meet Google Software Principles... it makes me wonder what Trillian failed to do or really what is Google about to offer that they are a competitive threat?

http://www.pcworld.com/resource/article/0,aid,125813,pg,1,RSS,RSS,00.asp

Have a terrific day and tell your wife/husband that you love them!

Toml LCSKid

Skills Assessment Title: AS35: Introduction to Microsoft Office Live Communications Server 2005

Skills Assessment Number: AS35A-100

Language: English

Instructions for the Assessment -

Go to http://www.microsoft.com/assessment

Click àAssess Yourself

Click àI already know my topic area

Sign in with your Passport account

Click àMicrosoft Office Live Communications Server 2005

Click àTake the Assessment

I  took this exam the other night and it did take me about 30 minutes. I ran into an odd experience in which a survey prompt came up as I was ready to score or assess myself and I chose cancel on the survey and lost my test. I would not suggest hitting cancel on that popup! 

TomL LCSKid  

Product Relationships:

Microsoft Events

·  TechNet Webcast: DNS Setup for Live Communications Server 2005 (Level 300)

·  TechNet Webcast: Managing Microsoft Office Live Communications Server 2005 Certificates (Level 300)

·  TechNet Webcast: Microsoft Office Communicator Technical Overview (Level 200)

·  TechNet Webcast: Public Cloud Federation (Level 200)

Microsoft Partner Learning Center

·  Microsoft Partner Readiness: Microsoft Real-Time Communications Overview (LCS 2005 SP1, Live Meeting 2005, Office Communicator 2005)

Microsoft PressPass

·  Live Communications Server 2005 Document: Active Directory Preparation Guide

·  Live Communications Server 2005 Document: Deploying Access Proxy and Director

·  Live Communications Server 2005 Document: Planning Guide

·  Live Communications Server 2005 Enterprise Edition Document: Lab Quick Start

·  Live Communications Server 2005 Trial Software

·  Live Communications Server Proxy Deployment Guide

·  Office Communicator 2005: Microsoft Office Communicator Getting Started

·  Office Communicator Web Access: Microsoft Office Communicator Web Access Planning and Deployment Guide

The beta version of this exam is 71-262. Please note that when registering.

Read below for details – use this code when registering for the Free Beta Exam -  TS262

<toml lcskid>

I took this test Friday April 28 and with my comments on various questions it took me 1.5 hours to complete.

<toml lcskid>

Beta Exam 71-262: TS: Microsoft® Office Live Communications Server 2005 - Implementing, Managing, and Troubleshooting

Audience – IT Pros/Architects

You are invited to Exam 70-262 in its beta version. As a benefit to you for demonstrating your expertise by passing specific Microsoft certification exams or by other means, this beta exam is offered to you free. This beta exam will not be offered to the general public, and is only available to a certain number of candidates. Each seat will be assigned on a first come first serve basis.

By participating in beta exams, you have the opportunity to provide the Microsoft Certification program with feedback about exam content, which is integral to development of exams in their released version. We depend on the contributions of experienced IT professionals and developers as we continually improve exam content and maintain the value of Microsoft certifications.

**Registration Information**

Note: You will be given four hours to complete the beta exam. Please plan accordingly.

Testing is held at Prometric and Pearson VUE testing centers worldwide, although this exam may not be available in all countries. You must register at least 24 hours prior to taking the exam. Contact your exam provider for seat availability. (Please note: all testing centers will have the capability to offer this exam in its live version.)

Please read carefully the following registration information as the schedules vary depending on which testing center you choose:

Registration begins:

April 15, 2006

Beta exam period runs:

April 27 – May 10, 2006

Please use the following promotional code when registering for the exam: TS262

These beta periods are subject to change; please check the exam preparation guides for the most up-to-date information:

http://www.microsoft.com/Learning/exams/70-262.asp

To register for this exam or for information about testing centers in your area, call:

• Prometric: (800) 755-EXAM (800-755-3926)
• VUE: 800 TEST REGistration (800-837-8734)

Outside the U.S./Canada, please visit the following Web sites for registration information:

• Prometric: http://www.register.prometric.com/ClientInformation.asp
• VUE: http://www.vue.com/ms/

Microsoft Certified Professional (MCP) Information on the World Wide Web

For more information, visit the MCP Web site at http://www.microsoft.com/mcp/, write to MCPHelp@microsoft.com or call 800-636-7544.

Specific pages that answer some frequently asked questions are listed below.

What is a beta exam?

http://www.microsoft.com/traincert/mcpexams/faq/procedures.asp

Where can I learn more about the registration process?

http://www.microsoft.com/traincert/mcpexams/register/default.asp

How do I prepare for this exam?

http://www.microsoft.com/traincert/exams/70-262.asp

When will my beta exam results be available?

http://www.microsoft.com/traincert/mcpexams/faq/procedures.asp#D

Where can I learn more about the beta exam invitation process?

http://www.microsoft.com/traincert/mcpexams/status/beta.asp

How can I learn more about the new and improved item types?

http://www.microsoft.com/traincert/mcpexams/faq/innovations.asp.

Where can I learn more about the MCSE on Windows Server 2003 certification?

http://www.microsoft.com/traincert/mcp/mcse/default.asp

If you have further questions regarding this exam or the MCP program, send e-mail to MCPHelp@microsoft.com or call 800-636-7544.

Introduction

Installation

ISSUE: Installation Prerequisites cause problems when not addressed.

In addition to the software and hardware requirements specified in the Microsoft Office Communicator Mobile 2007 Planning and Deployment Guide, the following are installation pre-requisites for the Communicator Mobile client:

§  You must not install Communicator Mobile on a storage card.

§  The folder to which you download the Communicator Mobile Windows Installer package (.msi) must not be encrypted.

§  Communicator Mobile must not already be installed on the mobile device. Remove previous installations of Communicator Mobile before you reinstall or install a new release.

§  Ensure that there is sufficient space on the mobile device to which you are trying to install. The Communicator Mobile installation for devices running Windows Mobile 5.0 requires approximately 7 MB of space. The Communicator Mobile installation for devices running Windows Mobile 2003 SE (Second Edition) requires approximately 3.4 MB of space.

ISSUE: ActiveSync Add/Remove Programs options do not remove Communicator Mobile installer file from the desktop computer.

When you use ActiveSync Add/Remove Programs and click Remove, Communicator Mobile is removed from the device, but the installer file is not removed from the desktop computer that was used to install Communicator Mobile. In order to remove the installer file from the desktop computer, you also have to remove the program using Add or Remove Programs in Control Panel.

If you remove Communicator Mobile from the device, but do not remove the installer file from the desktop computer, the next time you run the installer, you will be prompted to uninstall.

ISSUE: When Communicator Mobile is installed to a storage card on a Pocket PC, there are problems with the Pocket PC Today screen add-in.

We do not support installation of Communicator Mobile to a storage card. However, ActiveSync, when used with a Pocket PC running Windows Mobile 2003 SE, displays the option to install to a storage card. When you install Communicator Mobile to a storage card, the Today screen add-in disappears or displays incorrectly and cannot be used. Install Communicator Mobile to device memory instead.

Sign-in and Sign-out

ISSUE: The sign-in process takes a long time.

If you have 200 or more contacts on your Contacts list, the Communicator Mobile sign-in process can take longer. Having a large number of contacts on your Contacts list can also cause Communicator Mobile to stop responding altogether. If Communicator Mobile has stopped responding, delete contacts by using Office Communicator 2005, and then restart your mobile device before you try to sign in again.

ISSUE: Communicator Mobile is unresponsive after a phone call.

After a phone call, Communicator Mobile may not immediately respond. This is due to the automatic sign-in behavior of Communicator Mobile, where it tries to sign in immediately after the phone call ends (attempting to reconnect synchronously with the GPRS data reconnection). While Communicator Mobile reconnects, it seems unresponsive or is slow to respond.

ISSUE: On some Cingular 2125 smartphone devices, pressing END (call) button disconnects the GPRS data connection.

When you make or receive a call on a Windows Mobile powered device, the GPRS connection is put on hold. However, on some Cingular 2125 smartphone devices, when you press the END (call) button, the GPRS connection is disconnected. Communicator Mobile relies on the GPRS connection and is, therefore, signed out when GPRS is disconnected. If Communicator Mobile is configured to automatically sign in, Communicator Mobile will retry signin five times, beginning 15 seconds after it is initially disconnected.

If you do not want to disconnect GPRS with the END (call) button, you can set the value of the following registry key to 1:

HKEY_LOCAL_MACHINE\Comm\ConnMgr\Providers\{7C4B7A38-5FF7-4bc1-80F6-5DA7870BB1AA}\Connections\(GPRS connection name)\AlwaysOn

Conversations

ISSUE: Communicator Mobile supports a limited number of emoticons.

Communicator Mobile does not support the full spectrum of emoticons. Only the following emoticons are supported by Communicator Mobile:

:)     Smiley

:(     Sad smiley

:o    Surprised smiley

:d    Open-mouthed smiley

:p    Smile with tongue out

;)     Winking smile

Emoticons that are not supported appear as text.

ISSUE: “Failed to establish session” error message displays

A message delivery error “Failed to establish session” sometimes displays when you reply to an incoming instant message (IM). The error message displays when the user tries to send a message before Communicator Mobile has successfully established a session with the server.

This behavior is occasionally observed on high latency networks such as GPRS. When the session has been established, a “talking bubble” icon is displayed next to the participant name or list in the conversation window.

ISSUE: Messages cannot be sent or received while ActiveSync is actively synching mail.

When you try to send a message while ActiveSync is actively synching mail, you  receive a non-delivery error message. If another user tries to send you a message while your device is synching mail, the other user will receive a non-delivery error message. The reason is because ActiveSync takes up too much bandwidth. The synch process normally lasts for only a few seconds. After ActiveSync is done synching, you can resend messages.

ISSUE: Message toasts are not displayed

Communicator Mobile toasts are not displayed when they are received at the same time that a toast for another program (for example, e-mail or SMS) is actively displayed. This is to ensure that active notifications from other applications are not overwritten by Communicator Mobile’s toasts.

If there is an active toast from another application currently being displayed, the Communicator Mobile toast is added to the Notifications tray at the top of the Today screen. For example:

In order to view a toast that has been sent to the Notifications tray, you have to tap the Notifications tray on the Today screen. Any toasts that are queued in the Notifications tray when you sign out of or exit Communicator Mobile are discarded.

ISSUE: IMs fail when both users send messages to each other at the same time

When two Communicator Mobile users send messages to each other at the same time, both receive a toast for the session. If the users both accept the incoming message and try to use the conversation window to send more messages, a message delivery error: “Unable to Establish Session” displays.

At the SIP protocol level, each Communicator Mobile client receives a 487 Request Terminated message and the INVITE is cancelled.

In order to send messages to each other, the users must end the conversation and then start a new conversation, as described in the Communicator Mobile Help topics or Microsoft Office Communicator Mobile Getting Started Guide.

ISSUE:  Problems removing Communicator Mobile using ActiveSync Add/Remove Programs on a Windows Server 2003 computer

When you use ActiveSync on a Windows Server 2003 computer to install Communicator Mobile on a smartphone running Windows Mobile 5.0, future attempts to remove Communicator Mobile using ActiveSync’s Add/Remove programs will not succeed on the first attempt. It will, however, succeed if you re-run ActiveSync Add/Remove Programs. You can also remove Communicator Mobile by using the device’s Remove Programs feature as well as by using the Windows Installer file (.msi).

ISSUE:  Toast for incoming conversation stops displaying when you press the HOME key on a smartphone

If you press the HOME key when you receive a toast for an incoming conversation, the toast stops displaying and can no longer be accessed. You can check the Current Conversations list in your Contacts list to see if the conversation was automatically accepted by Communicator Mobile. If the toast was for an incoming IM conversation, the message is automatically accepted on the most active Communicator endpoint at the time.

Presence and Contacts

ISSUE: Presence status is not displayed for some or all contacts

Presence status for contacts can be unavailable if you have a very large contact list or if your device is low on memory. Exit programs that you are not currently using, or delete some contacts in order to optimize your Contacts list. Communicator Mobile does not explicitly define any limit to the number of contacts on your Contacts list; however, on some devices, Communicator Mobile is unable to display presence status because of memory limitations.

Device Interaction

ISSUE: Battery life is impacted by Communicator Mobile usage.

While it is not possible to accurately predict battery life and consumption because these vary across devices, there have been observations of battery life reduction of between 25% to 39% when Communicator Mobile is constantly signed in over the GPRS data connection. Enabling Communicator Mobile’s "Automatically log in" option may lead to reduced battery life and higher data usage.

Office Communicator Mobile just released to web and is now available for download from http://www.microsoft.com/downloads/details.aspx?FamilyId=BC89EC5E-5F3B-47D2-955B-B0C1DEAC94D8.

I will be adding an issues posting that was not included in the release notes or documentation for the product. They will be public KB articles shortly.

Toml LCS Kid