Greg Anthony's Blog

Why hasn't Greg blogged anything lately

2010-04-12T16:35:00Z

I've been busy working on another project. In the meantime I suggest that you check out NextHop which is a centralized portal for all things relating to Microsoft Unified Communications.

LCS/OCS Public IM Connectivity (PIC) with Yahoo! Domains YMail.com and Rocketmail.com

2010-01-22T14:26:01Z

Yahoo! has added two additional domains (ymail.com and rocketmail.com) that users can choose from when creating a Yahoo! ID.

In order for instant messaging and presence to work correctly with Yahoo! user accounts created in those domains you will need to add entries on the Allow tab of your Live Communications Server 2005 SP1 Access Proxy or Office Communications Server 2007/R2 Access Edge.

The entries would be entered as Domain ymail.com and Access Edge lcsap.msg.yahoo.com and Domain rocketmail.com and Access Edge lcsap.msg.yahoo.com.

A restart of the Access Proxy or Access Edge Service may be required.

Office Communications Server 2007 R2: Response Group Service Does Not Start

2010-01-06T14:46:59Z

The following symptoms are observed. Response Group Service doesn’t start. When starting manually it stops again as soon as it has been started.

The following event is logged in the Office Communications Server event log in Event Viewer on the affected server:

Event Type: Error
Event Source: OCS Application Server
Date:         Date
Time:        Time
Event-ID:   32003
Category:(1055)
Computer: <computer name>

Description:
The Application Host failed to start an application.

The Application Host could not start the application Microsoft.Rtc.Applications.Acd. Exception information: Exception: System.Reflection.TargetInvocationException
> Message: …caused an exception

> StackTrace:    bei System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   bei System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Microsoft.Rtc.ApplicationServerCore.EventQueueEntry.ExecutionContextRunCallback(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at Microsoft.Rtc.ApplicationServerCore.EventQueueEntry.InvokeEvent(Boolean executingSynchronously, EventSerializer serializer)
   at Microsoft.Rtc.ApplicationServerCore.EventSerializer.ProcessEvent(Boolean executingSynchronously, EventQueueEntry entry)
   at Microsoft.Rtc.ApplicationServerCore.EventSerializer.ProcessEvents(EventQueueEntry entry)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
> Source: mscorlib
Inner Exception: System.IO.FileNotFoundException
> Message: File or Assembly "System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" or a dependency was not found.

System can’t file the file specified (file not found)

> FileName: System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

Cause: Startup errors.
Resolution:
Check the events prior to this to resolve the service startup issue.

Even though it is not listed as a prerequisite, the resolution for this issue is to install Microsoft .NET Framework 3.0.

Failed to activate Office Communications Server Standard Edition Server

2009-11-24T12:23:05Z

When you deploy a new installation of Standard Edition Server activation fails if security update 974571 is installed and the fix mentioned in http://support.microsoft.com/kb/974571 has not been applied to the server.

The following is logged in the Office Communications Server 2007 R2 Deployment Log

Failure [0xC3EC796C] One or more errors occurred during the execution of the wizard; the wizard was unable to complete successfully. Please check the log file for more information.

The following is logged in the Activate Standard Edition Server Log.

Failure [0xC3EC78DB] Failed to read the Office Communications Server version information. This can happen if the computer clock is not set to correct date and time.

The following event is logged in the Office Communications Server event log in Event Viewer on the affected server:

Event Type:    Warning
Event Source:    OCS Setup
Event Category:    (1007)
Event ID:    30502
Date:        Date
Time:        Time
User:        N/A
Computer:    Computer
Description:
Failed to activate Office Communications Server Standard Edition Server on machine Computer.
Error: C3EC78D8
Description: Failed to read the Office Communications Server version information. This can happen if the computer clock is not set to correct date and time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Additionally, during an installation of Live Communications Server 2005 SP1 when setup for a new LCS installation and Windows Security update 97451 is installed and the OCSASNFIX.exe fix referenced in http://support.microsoft.com/kb/974571 has not been applied to the server Setup.exe may close unexpectedly with no warning.

The following events may be logged in the Application event log in Event Viewer on the affected server:

Event Type:    Error
Event Source:    Application Error
Event Category:    (100)
Event ID:    1000
Date:        12/29/2009
Time:        7:54:50 AM
User:        N/A
Computer:    Computer
Description:
Faulting application Setup.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.4455, fault address 0x0002a776.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 53 65 74   ure Set
0018: 75 70 2e 65 78 65 20 30   up.exe 0
0020: 2e 30 2e 30 2e 30 20 69   .0.0.0 i
0028: 6e 20 6e 74 64 6c 6c 2e   n ntdll.
0030: 64 6c 6c 20 35 2e 32 2e   dll 5.2.
0038: 33 37 39 30 2e 34 34 35   3790.445
0040: 35 20 61 74 20 6f 66 66   5 at off
0048: 73 65 74 20 30 30 30 32   set 0002
0050: 61 37 37 36               a776

Event Type:    Information
Event Source:    DrWatson
Event Category:    None
Event ID:    4097
Date:        12/29/2009
Time:        7:54:51 AM
User:        N/A
Computer:   Computer
Description:
The application, \\computer\files\Live Communications Server 2005 with SP1\Standard\Setup\I386\Setup.exe, generated an application error The error occurred on 12/29/2009 @ 07:54:51.468 The exception generated was c0000005 at address 7C82A776 (ntdll!wcslen)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

OCS 2007 R2: Error Accessing User Communications Tab Properties

2009-11-23T12:28:36Z

Problem

After migrating a user from Live Communications Server 2005 Service Pack 1 to Office Communications Server 2007 R2 you are unable to view or change the user’s Communications Tab properties.

Symptoms

When you click one of the configure buttons you receive a Validation Failed message.

Validation failed with HRESULT = 0xC3EC7E02 – Accessing OCS 2007 R2 User Properties.

Cause

Invalid TEL URI on the migrated account from when the account was previously enabled for Remote Call Control in LCS 2005 SP1.

Resolution

Moved user account back to Live Communications Server 2005 Pool and open user properties and in User Advance Settings enable Remote Call Control and remove the entry from TEL URI: and remove the entry from Remote Call Control SIP URI then uncheck Enable Remote Call Control and save. Move user back to OCS 2007 R2 and verify you can access user properties in OCS 2007 R2.

More Information

Enable Office Communications Server Debug Logging on the Pool for LcManagedtaskhandler, LcManagedTaskShell, LcsAdUcSnapin, LcsSnapin, LCSWizard, LcsTaskHandler and reproduce the issue.
Viewed all the log files combined.
In the logs you should find trace information similar to the following;
TL_NOISE(TF_STACKTRACE) [3]0F08.19D4::11/10/2009-14:07:20.176.00000767 ((Shared),UserSettingValidationHelper:ValidatorUtils.cpp(3460))Entering
TL_INFO(TF_COMPONENT) [3]0F08.19D4::11/10/2009-14:07:20.176.00000768 ((Shared),UserSettingValidationHelper:ValidatorUtils.cpp(3700))Line URI is present
when UC is enabled - it will be validated
TL_ERROR(TF_COMPONENT) [3]0F08.19D4::11/10/2009-14:07:20.176.0000076b ((Shared),UserSettingValidationHelper:ValidatorUtils.cpp(3705))Line URI
tel:3048;phone-context=cdp.udp is not valid for UC -- returning error 0xC3EC7E02(LC_VALIDATION_E_INVALID_TEL_URI)
TL_NOISE(TF_STACKTRACE) [3]0F08.19D4::11/10/2009-14:07:20.176.0000076c ((Shared),UserSettingValidationHelper:ValidatorUtils.cpp(3719))Leaving with hr =
0xC3EC7E02(LC_VALIDATION_E_INVALID_TEL_URI)
TL_ERROR(TF_COMPONENT) [3]0F08.19D4::11/10/2009-14:07:20.176.0000076d ((Shared),UserSettingCustomClassValidator:CustomValidators.cpp(2542))Call to
UserSettingValidationHelper failed, 0xC3EC7E02(LC_VALIDATION_E_INVALID_TEL_URI)
TL_NOISE(TF_STACKTRACE) [3]0F08.19D4::11/10/2009-14:07:20.176.0000076e ((Shared),UserSettingCustomClassValidator:CustomValidators.cpp(2547))Leaving with hr
= 0xC3EC7E02(LC_VALIDATION_E_INVALID_TEL_URI)
TL_ERROR(TF_COMPONENT) [3]0F08.19D4::11/10/2009-14:07:20.176.0000076f ((Shared),ValidateClassFromMmc:ClassValidate.cpp(2903))Call to custom class
validator -- 0xC3EC7E02(LC_VALIDATION_E_INVALID_TEL_URI)
TL_NOISE(TF_STACKTRACE) [3]0F08.19D4::11/10/2009-14:07:20.176.00000770 ((Shared),ValidateClassFromMmc:ClassValidate.cpp(3036))Leaving with hr = 0xC3EC7E02
(LC_VALIDATION_E_INVALID_TEL_URI)

How to issue certificate for Office Communications Server 2007 R2 when the Web Server Template has been disabled on the Certificate Authority

2009-11-23T12:09:11Z

Problem

You receive an error trying to issue a certificate via the Certificate Wizard because the default web server template has been disabled on the certification authority.

Symptom

You may see the following error in the Certificate Authority Server logs. "Denied by Policy Module 0x80094800. The request was for a certificate template that is not supported by the Certificate Services policy."

Cause

Web Server template has been disabled and the Office Communications Server Certificate Wizard is hard coded to use the Web Server template.

Resolution

Use the LCSCMD.exe /Cert command line utility to request the certificate and specify the custom template to use.

LCSCmd.exe /Cert /Action:Request /OU: /org: /sn: /country: /state: /city: [/online[:{TRUE|FALSE}]] [/friendlyName:] [/bitLength:] [/exportable[:{TRUE|FALSE}]] [/san:] [/Filename:] [/ca:\>] [/caAccount:\ or \>] [/caPassword:] [/autoAppendSNToSAN[:{TRUE|FALSE}]] [/enableClientEKU[:{TRUE|FALSE}]] [/assign:{TRUE|FALSE}] [/Components:{AP | DP | MR | INTERNAL}] [/L:] [/XML[:{TRUE|FALSE}]] [/?[:{TRUE|FALSE}]] /Template:
Such as:
LCSCmd.exe /Cert /Action:Request /OU:Marketing /Org:Contoso /sn:eepool1.contoso.com
/country:US /city:Redmond /state:Washington /Template:WebServer2

More Information

The /Template switch is undocumented and not supported. For more information on managing certificates from the command line see http://technet.microsoft.com/en-us/library/dd572468(office.13).aspx.

When running Active Directory Users and Computers on a machine where LCS 2005 SP1 Administration tools have been installed you click Live Communications tab on user account properties and receive “Failed to read the user’s settings”

2009-10-02T14:19:50Z

Cause

LCS 2005 SP1 Servers have been updated with KB 911996 which requires any LCS 2005 SP1 Administration Tools installation to also be updated.

Resolution

Apply KB 911996 update to machines that have the LCS 2005 SP1 Administration Tools Installation.

Updating Microsoft Office Communications Server 2007 Best Practices Analyzer

2009-09-17T14:40:38Z

When you launch the OCS 2007 BPA Tool for the first time after installation you have the option to set the tool to “Check for updates on startup (recommended)” or to “Do not check for updates on startup”.

Once you have selected an option then the following registry keys are set.

HKEY_CURRENT_USER\Software\Microsoft\RTCBPA

ShowedUpdateOption REG_DWORD (0 on first run, 1 after first run)

VersionCheckAlways REG_DWORD (0 = disabled – Do not check for updates, 1 = enabled – Check for updates)

So you can flip the bit on VersionCheckAlways to change the update behavior.

Now if your machine where you have it installed does not have internet access you can install the BPA Tool on a machine that has internet access and allow it to check for updates. Then you can copy the files from the updated BPA tool installation directory (typically C:\Program Files\Microsoft Office Communications Server 2007\BPA) to the installation directory on the machine that doesn’t have internet access. This is particularly useful for OCS Edge Server Environments where internet access is blocked.

Note: The OCS 2007 BPA Tool only detects the OCS 2007 Edge Server Role if the machine is member of a workgroup. If the OCS 2007 Edge Server is domain joined it will not detect the OCS 2007 Edge Role. Following is an excerpt from the Microsoft Office Communications Server 2007 Edge Server Deployment Guide. “ Deploy edge servers in a workgroup rather than a domain. Doing so simplifies installation and keeps the Active Directory® Domain Services out of the perimeter network. Locating Active Directory in the perimeter network can present a significant security risk.”

Communicator 2007 R2 Desktop Sharing Call Flow Part 1 – Peer to Peer

2009-09-08T20:58:02Z

I had worked on a case recently where a firewall existed between the OCS 2007 R2 Pool and the internal Communicator 2007 R2 clients concerning call flow and what direct ports needed to be open in the firewall (inbound, outbound, or both) using the Communicator Policies for enabling minimum and maximum media ports.

That said I’m going to cover basic call flow with no policy set just to show what is happening behind the scenes from an initial peer-to-peer desktop sharing which is elevated to a multiparty session by adding a third user.

My environment consists of an OCS 2007 R2 Standard Edition server with the latest QFE2 updates and three machines with Communicator 2007 R2 (logging enabled) and several test accounts (r2user1, r2user2, and r2user3).

r2user1 right clicks contact r2user2 and selects the Share/Share Desktop as shown in the following screen shot.

r2user2 click to accepts the toast

and now r2user2 sees r2user1’s desktop.

So what happened behind the scenes?

Opening up the Communicator-uccapi-0.uccapilog (found in %userprofile%\tracing on workstation) in Snooper.exe (found in OCS 2007 R2 Resource Kit) I find the SIP INVITE to user r2user2 information in the client log for r2user1.

Looking at the same client log for r2user2 I find the matching conversation to the SIP dialog.

First we’ll look at the SIP INVITE from r2user1 to r2user2

=================================================================

08/25/2009|13:47:02.915 17B4:15C0 INFO :: Sending Packet - 192.168.100.69:5061 (From Local Address: 192.168.100.65:2217) 1852 bytes:
08/25/2009|13:47:02.915 17B4:15C0 INFO :: INVITE sip:r2user2@aj.local SIP/2.0
Via: SIP/2.0/TLS 192.168.100.65:2217
Max-Forwards: 70
From: <sip:r2user1@aj.local>;tag=c19d554b25;epid=10e9cc7f1f
To: <sip:r2user2@aj.local>
Call-ID: da937b708b5844869143c7c325110766
CSeq: 1 INVITE
Contact: <sip:r2user1@aj.local;opaque=user:epid:zKV7abW3A1uSjfYfC9sbQQAA;gruu>
User-Agent: UCCAPI/3.5.6907.37 OC/3.5.6907.37 (Microsoft Office Communicator 2007 R2)
Ms-Conversation-ID: AcolrAxlCSZJMA0BQP2a06VfCBBNKQ==
Supported: timer
Supported: histinfo
Supported: ms-safe-transfer
Supported: ms-sender
Supported: ms-early-media
ms-keep-alive: UAC;hop-hop=yes
Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REFER, NOTIFY, BENOTIFY, OPTIONS
Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="C29EF240", targetname="sip/AJ-SE-HS-R2.aj.local", crand="b37ce389", cnum="10", response="602306092a864886f71201020201011100fffffffff4fec35d826eb40b6d98ebc9df978058"
Content-Type: application/sdp
Content-Length: 854

v=0
o=- 0 0 IN IP4 192.168.100.65
s=session
c=IN IP4 192.168.100.65
b=CT:99980
t=0 0
m=applicationsharing 50019 TCP/RTP/AVP 127
a=ice-ufrag:WnBn
a=ice-pwd:Eu5diRjJD53zZ0s9aIuKX1WZ
a=candidate:1 1 TCP-PASS 2120613887 192.168.100.65 50016 typ host
a=candidate:1 2 TCP-PASS 2120613374 192.168.100.65 50016 typ host
a=candidate:2 1 TCP-ACT 2121006591 192.168.100.65 50019 typ host
a=candidate:2 2 TCP-ACT 2121006078 192.168.100.65 50019 typ host
a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:Gz/jt1b6x3OSCjVoPxEA4tpCEQsv2mMgopkdcnDM|2^31|1:1
a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:alLwpSEgI558l41mbr5Kt4WMhJQ0mLFIW5kdMHR6|2^31|1:1
a=setup:active
a=connection:new
a=rtcp:50019
a=mid:1
a=rtpmap:127 x-data/90000
a=x-applicationsharing-session-id:1
a=x-applicationsharing-role:sharer
a=x-applicationsharing-media-type:rdp

08/25/2009|13:47:02.915 17B4:15C0 INFO :: End of Sending Packet - 192.168.100.69:5061 (From Local Address: 192.168.100.65:2217) 1852 bytes

=================================================================

Note: To gain a further understanding of the Session Description Protocol (SDP) session level descriptions and attributes see RFC4566 and [MS-SDPEXT]: Session Description Protocol (SDP) Version 2.0 Protocol Extensions.

In the above SIP INVITE we see that the media type is applicationsharing which indicates that user r2user1 wants to share their desktop with r2user2. Also note the role of sharer and media-type of rdp in the a-=x-applicationssharing attributes.

The SIP INVITE also includes a list of ICE candidates (IP addresses and port) for establishing connectivity. In the a=candidate list you see TCP-PASS and TCP-ACT on the candidate pairs passed.When the user agents perform address allocations to gather TCP-based candidates, two types of candidates can be obtained. These are active candidates (TCP-ACT) or passive candidates (TCP-PASS). An active candidate is one for which the agent will attempt to open an outbound connection, but will not receive incoming connection requests. A passive candidate is one for which the agent will receive incoming connection attempts, but not attempt a connection.

When r2user2 accepts the invite by accepting the toast their Office Communicator client sends back a SIP/2.0 200 OK that includes their list of ICE candidates.

=================================================================

08/25/2009|13:47:05.652 F40:B70 INFO :: Sending Packet - 192.168.100.69:5061 (From Local Address: 192.168.100.80:2125) 2047 bytes:
08/25/2009|13:47:05.652 F40:B70 INFO :: SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.100.69:5061;branch=z9hG4bKDEE5EF7A.BF6B243466DDFB06;branched=FALSE;ms-internal-info="caRyyi_UkbLXmM_cwQl-4yVh2nkcs0JGu_zXOeeAAA"
Via: SIP/2.0/TLS 192.168.100.65:2217;ms-received-port=2217;ms-received-cid=27300
From: "r2user1"<sip:r2user1@aj.local>;tag=c19d554b25;epid=10e9cc7f1f
To: <sip:r2user2@aj.local>;epid=a95e9231f2;tag=f5691fb8af
Call-ID: da937b708b5844869143c7c325110766
CSeq: 1 INVITE
Record-Route: <sip:AJ-SE-HS-R2.aj.local:5061;transport=tls;opaque=state:T:F:Ci.R27400;lr;ms-route-sig=ecz81J8HcFoT0Zh-VRdvOjXurWDYo0JGu_ODrQ8gAA>;tag=54291250A705C55B30D9DD2028FEF17F
Contact: <sip:r2user2@aj.local;opaque=user:epid:cBiHrFl9wlyErbCkKxK1lAAA;gruu>
User-Agent: UCCAPI/3.5.6907.37 OC/3.5.6907.37 (Microsoft Office Communicator 2007 R2)
Supported: histinfo
Supported: ms-safe-transfer
Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REFER, NOTIFY, BENOTIFY, OPTIONS
Session-Expires: 720;refresher=uac
Supported: ms-conf-invite
Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="B617E06D", targetname="sip/AJ-SE-HS-R2.aj.local", crand="aae59dcd", cnum="13", response="602306092a864886f71201020201011100fffffffff937df89260fd7afe33f261d9dd45f8c"
Content-Type: application/sdp
Content-Length: 755

v=0
o=- 0 0 IN IP4 192.168.100.80
s=session
c=IN IP4 192.168.100.80
b=CT:99980
t=0 0
m=applicationsharing 24042 TCP/RTP/SAVP 127
a=ice-ufrag:ooWD
a=ice-pwd:nRmXmAExInRQb86LlNM0DNYx
a=candidate:1 1 TCP-PASS 2120613887 192.168.100.80 18851 typ host
a=candidate:1 2 TCP-PASS 2120613374 192.168.100.80 18851 typ host
a=candidate:2 1 TCP-ACT 2121006591 192.168.100.80 24042 typ host
a=candidate:2 2 TCP-ACT 2121006078 192.168.100.80 24042 typ host
a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:bB8NYCDMHg5gku25YjWVFCJI5qmXIek9tG2ldHJN|2^31|1:1
a=setup:active
a=connection:existing
a=rtcp:24042
a=mid:1
a=rtpmap:127 x-data/90000
a=x-applicationsharing-session-id:1
a=x-applicationsharing-role:viewer
a=x-applicationsharing-media-type:rdp

08/25/2009|13:47:05.652 F40:B70 INFO :: End of Sending Packet - 192.168.100.69:5061 (From Local Address: 192.168.100.80:2125) 2047 bytes

=================================================================

r2user1 client sends back an acknowledgement to r2user2 clients acceptance of the invite.

Then r2user1 sends a new SIP INVITE message that contains the winning IP address for that workstation as shown below.

==========================================================

08/25/2009|13:47:06.038 17B4:15C0 INFO :: Sending Packet - 192.168.100.69:5061 (From Local Address: 192.168.100.65:2217) 1863 bytes:
08/25/2009|13:47:06.038 17B4:15C0 INFO :: INVITE sip:r2user2@aj.local;opaque=user:epid:cBiHrFl9wlyErbCkKxK1lAAA;gruu SIP/2.0
Via: SIP/2.0/TLS 192.168.100.65:2217
Max-Forwards: 70
From: <sip:r2user1@aj.local>;tag=c19d554b25;epid=10e9cc7f1f
To: <sip:r2user2@aj.local>;epid=a95e9231f2;tag=f5691fb8af
Call-ID: da937b708b5844869143c7c325110766
CSeq: 2 INVITE
Route: <sip:AJ-SE-HS-R2.aj.local:5061;transport=tls;opaque=state:F:T:Eu:Ci.R27300;lr;ms-route-sig=ec-QNRPqugyjLhqIvpyd2ADcGOcFU0JGu_ODrQ8gAA>
Contact: <sip:r2user1@aj.local;opaque=user:epid:zKV7abW3A1uSjfYfC9sbQQAA;gruu>
User-Agent: UCCAPI/3.5.6907.37 OC/3.5.6907.37 (Microsoft Office Communicator 2007 R2)
Supported: ms-dialog-route-set-update
Ms-Conversation-ID: AcolrAxlCSZJMA0BQP2a06VfCBBNKQ==
Supported: timer
Supported: histinfo
Supported: ms-safe-transfer
Supported: ms-sender
Supported: ms-early-media
ms-keep-alive: UAC;hop-hop=yes
Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="C29EF240", targetname="sip/AJ-SE-HS-R2.aj.local", crand="4a1cc8bd", cnum="12", response="602306092a864886f71201020201011100ffffffffc701b54e409b3e5822bfeb459eee9dbd"
Content-Type: application/sdp
Content-Length: 686

v=0
o=- 0 0 IN IP4 192.168.100.65
s=session
c=IN IP4 192.168.100.65
b=CT:99980
t=0 0
m=applicationsharing 50009 TCP/RTP/SAVP 127
a=ice-ufrag:WnBn
a=ice-pwd:Eu5diRjJD53zZ0s9aIuKX1WZ
a=candidate:2 1 TCP-ACT 2121006591 192.168.100.65 50009 typ host
a=candidate:2 2 TCP-ACT 2121006078 192.168.100.65 50009 typ host
a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:alLwpSEgI558l41mbr5Kt4WMhJQ0mLFIW5kdMHR6|2^31|1:1
a=remote-candidates:1 192.168.100.80 18851 2 192.168.100.80 18851
a=setup:active
a=connection:existing
a=rtcp:50009
a=mid:1
a=rtpmap:127 x-data/90000
a=x-applicationsharing-session-id:1
a=x-applicationsharing-role:sharer
a=x-applicationsharing-media-type:rdp

08/25/2009|13:47:06.038 17B4:15C0 INFO :: End of Sending Packet - 192.168.100.69:5061 (From Local Address: 192.168.100.65:2217) 1863 bytes

=================================================================

You may notice that the From: and To: information doesn’t change as the From: indicates the initiator of the request and this may be different than the initiator of the dialog.

r2user1 acknowledges and establishes a SRTP session over TCP communication as seen in the network trace below.

As an informational aside r2user2 could have chosen the Redirect option on the toast if they were currently busy or wanted more info before viewing r2user1’s desktop.

Also if they choose to ignore the toast it will expire within about 30 seconds.

The Communicator-uccapilog would show the following in a no response scenario.

=================================================================

09/04/2009|11:17:17.838 15B4:125C INFO :: Sending Packet - 192.168.100.69:5061 (From Local Address: 192.168.100.65:4997) 671 bytes:
09/04/2009|11:17:17.838 15B4:125C INFO :: CANCEL sip:r2user2@aj.local SIP/2.0
Via: SIP/2.0/TLS 192.168.100.65:4997
Max-Forwards: 70
From: <sip:r2user1@aj.local>;tag=a8b738f224;epid=10e9cc7f1f
To: <sip:r2user2@aj.local>
Call-ID: 1e5c04dabc1b47a58c98f8e5e54e0e87
CSeq: 1 CANCEL
User-Agent: UCCAPI/3.5.6907.37 OC/3.5.6907.37 (Microsoft Office Communicator 2007 R2)
Ms-client-diagnostics: 52023; reason="Caller timeout on no response"
Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="92595B50", targetname="sip/AJ-SE-HS-R2.aj.local", crand="148aefdf", cnum="16", response="602306092a864886f71201020201011100ffffffff159cfea53f6a348e36d4997cc65623bb"
Content-Length: 0

09/04/2009|11:17:17.838 15B4:125C INFO :: End of Sending Packet - 192.168.100.69:5061 (From Local Address: 192.168.100.65:4997) 671 bytes

================================================================

09/04/2009|11:17:18.088 15B4:125C INFO :: Data Received - 192.168.100.69:5061 (To Local Address: 192.168.100.65:4997) 708 bytes:
09/04/2009|11:17:18.088 15B4:125C INFO :: SIP/2.0 487 Request terminated
Proxy-Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF88D59A08B2142ABC250A46B13688B954", srand="891C7171", snum="23", opaque="92595B50", qop="auth", targetname="sip/AJ-SE-HS-R2.aj.local", realm="SIP Communications Service"
From: <sip:r2user1@aj.local>;tag=a8b738f224;epid=10e9cc7f1f
To: <sip:r2user2@aj.local>;tag=54291250A705C55B30D9DD2028FEF17F
Call-ID: 1e5c04dabc1b47a58c98f8e5e54e0e87
CSeq: 1 INVITE
Via: SIP/2.0/TLS 192.168.100.65:4997;ms-received-port=4997;ms-received-cid=88700
ms-diagnostics: 5002;reason="Request was cancelled";source="AJ-SE-HS-R2.aj.local";AppUri="http://www.microsoft.com/LCS/ApiModule"
Content-Length: 0

09/04/2009|11:17:18.088 15B4:125C INFO :: End of Data Received - 192.168.100.69:5061 (To Local Address: 192.168.100.65:4997) 708 bytes

Office Communicator 2007 and R2 File Transfer when Forefront Security for Office Communications Server is installed.

2009-08-10T20:54:11Z

Communicator 2007 or Communicator 2007 R2 File transfers no longer occur peer-to-peer after installation of Forefront Security for Office Communications Server 2007.

By default, IM-based file transfers occur as a peer-to-peer file copy between two instances of Office Communicator. When FSOCS is installed, it redirects the file transfer through the server it is deployed on so the file can be evaluated against filters and scanned for malware before it is sent to the intended recipient.

Firewall ports, both inbound and outbound, on the server where an instance of FSOCS is installed need to be opened for the TCP connections. The default port range includes ports 6891 through 6901.
More information on configuring the default file transfer port range can be found in the File Transfers topic in the Introduction to FSOCS section of the FSOCS user guide.