Communicator 2007 R2 Desktop Sharing Not Working
We are having problems with users sharing desktops through Office Communicator across the WAN. What makes it hard to nail down is that the issue is not always present. Users will initiate the share and when it is accepted it will just hang with a white screen then eventually time out.
Here is a log from the computer trying to initiate the connection:
A SIP request made by Communicator failed in an unexpected manner (status code 0). More information is contained in the following technical data:
RequestUri: sip:ITUser@xxxx.com;opaque
From: sip:ConfRoomPBO@xxx.com;ta
To: sip:ituser@xxxx.com;tag=64
Call-ID: f74d357e529c44dcbee026adc4
Content-type: application/sdp;call-type=
v=0
o=- 0 0 IN IP4 192.168.6.52
s=session
c=IN IP4 192.168.6.52
b=CT:99980
t=0 0
m=applicationsharing 3266 TCP/RTP/AVP 127
a=ice-ufrag:IG7k
a=ice-pwd:897caAwnnC8FrM3T
a=candidate:1 1 TCP-PASS 2120613887 192.168.6.52 17365 typ host
a=candidate:1 2 TCP-PASS 2120613374 192.168.6.52 17365 typ host
a=candidate:2 1 TCP-ACT 2121006591 192.168.6.52 3266 typ host
a=candidate:2 2 TCP-ACT 2121006078 192.168.6.52 3266 typ host
a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:oZbvKJH4uaS2XXtihqx
a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:3Ipq0qxuRzvP1p1UtNJ
a=setup:active
a=connection:new
a=rtcp:3266
a=mid:1
a=rtpmap:127 x-data/90000
a=x-applicationsharing-ses
a=x-applicationsharing-rol
a=x-applicationsharing-med
Response Data:
180 Ringing
0 (null)
Ms-client-diagnostics: 52031; reason="Call terminated on media connectivity failure"
Here is a log from the computer trying to initiate the connection:
A SIP request made by Communicator failed in an unexpected manner (status code 0). More information is contained in the following technical data:
RequestUri: sip:ITUser@xxxx.com;opaque
From: sip:ConfRoomPBO@xxx.com;ta
To: sip:ituser@xxxx.com;tag=64
Call-ID: f74d357e529c44dcbee026adc4
Content-type: application/sdp;call-type=
v=0
o=- 0 0 IN IP4 192.168.6.52
s=session
c=IN IP4 192.168.6.52
b=CT:99980
t=0 0
m=applicationsharing 3266 TCP/RTP/AVP 127
a=ice-ufrag:IG7k
a=ice-pwd:897caAwnnC8FrM3T
a=candidate:1 1 TCP-PASS 2120613887 192.168.6.52 17365 typ host
a=candidate:1 2 TCP-PASS 2120613374 192.168.6.52 17365 typ host
a=candidate:2 1 TCP-ACT 2121006591 192.168.6.52 3266 typ host
a=candidate:2 2 TCP-ACT 2121006078 192.168.6.52 3266 typ host
a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:oZbvKJH4uaS2XXtihqx
a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:3Ipq0qxuRzvP1p1UtNJ
a=setup:active
a=connection:new
a=rtcp:3266
a=mid:1
a=rtpmap:127 x-data/90000
a=x-applicationsharing-ses
a=x-applicationsharing-rol
a=x-applicationsharing-med
Response Data:
180 Ringing
0 (null)
Ms-client-diagnostics: 52031; reason="Call terminated on media connectivity failure"
avishar
These WAN users are external internet users or internal users ?
do you have application sharing port opened between the sites http://technet.microsoft.com/en-us/library/dd425238(office.13).aspx
ASKER
They are users on our LAN connected via private lines. They are on different subnets.
There are no ports closed between the sites. And the fact that it works sometimes confuses me.
There are no ports closed between the sites. And the fact that it works sometimes confuses me.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We do have riverbeds. I will have to look into that. It is very likely that is the issue.
ASKER
The riverbeds were the issue. We limited the port range of communicator and then added them to pass-through in the riverbed