Solved

Lync application sharing not (always) working

Posted on 2013-01-08
6
4,287 Views
Last Modified: 2013-11-29
I have an otherwise fully-functional Lync 2010 deployment, with Edge services on a public IP (no NAT) though at the moment I'm skipping the reverse-proxy and routing to the FE pool web services directly (yes I know it isn't recommended.)  Using public UC certificate.  FE and Edge servers are both Win 2008 R2.

All services are functional except application/screen sharing  - but it only fails when one participant is inside the LAN and the other participant is outside.  

LAN Client <-> LAN Client = application sharing works
Remote Client <-> Remote Client = application sharing works
LAN Client <-> Remote Client = app sharing fails with "network issues" error

I've enabled Lync logging on the client but a lot of it is incomprehensible to me.  This particular section though I believe is relevant:

01/08/2013|13:16:01.621 BF0:BE8 TRACE :: New mpss created: 077C3680, stack=0359DE08, 0
01/08/2013|13:16:01.621 BF0:BE8 INFO  :: MSP.SetMultipartySsnRole[077C3680] 0->0
01/08/2013|13:16:01.621 BF0:BE8 TRACE :: MULTIPARTY_SESSION::SetConnectParams[077C3680] n=(null), uri=administrator@mydomain.com
01/08/2013|13:16:01.621 BF0:BE8 INFO  :: CUccEndpoint::GetMediaPortRange - retrieved range min: 1025, max: 65000
01/08/2013|13:16:01.621 BF0:BE8 INFO  :: CRTCMediaSession::SetMediaPortRange - input media type: 1, minPort: 1025, maxPort: 65000
01/08/2013|13:16:01.621 BF0:BE8 INFO  :: CUccEndpoint::GetMediaPortRange - retrieved range min: 1025, max: 65000
01/08/2013|13:16:01.621 BF0:BE8 INFO  :: CRTCMediaSession::SetMediaPortRange - input media type: 2, minPort: 1025, maxPort: 65000
01/08/2013|13:16:01.621 BF0:BE8 INFO  :: CRTCMediaSession::SetMediaPortRange - input media type: 32, minPort: 1025, maxPort: 65000
01/08/2013|13:16:01.621 BF0:BE8 WARN  :: CUccEndpoint::GetMediaPortRange - port range not set for media type 4
01/08/2013|13:16:01.621 BF0:BE8 ERROR :: CUccMediaSession::SetMediaPortRange: HRESULT failed: 80ee0058 = hr. failed to get port range for Ucc meda
01/08/2013|13:16:01.621 BF0:BE8 WARN  :: CUccEndpoint::GetMediaPortRange - port range not set for media type 8
01/08/2013|13:16:01.621 BF0:BE8 ERROR :: CUccMediaSession::SetMediaPortRange: HRESULT failed: 80ee0058 = hr. failed to get port range for Ucc meda
01/08/2013|13:16:01.621 BF0:BE8 INFO  :: CUccEndpoint::GetMediaPortRange - retrieved range min: 1025, max: 65000
01/08/2013|13:16:01.621 BF0:BE8 INFO  :: CRTCMediaSession::SetMediaPortRange - input media type: 4, minPort: 1025, maxPort: 65000
01/08/2013|13:16:01.621 BF0:BE8 INFO  :: CUccEndpoint::GetMediaPortRange - retrieved range min: 1025, max: 65000
01/08/2013|13:16:01.621 BF0:BE8 INFO  :: CRTCMediaSession::SetMediaPortRange - input media type: 64, minPort: 1025, maxPort: 65000
01/08/2013|13:16:01.621 BF0:BE8 ERROR :: failed to get the remote participant
01/08/2013|13:16:01.684 BF0:BE8 TRACE :: CUccSession::InternalAddParticipant - Adding participant sip:codell@mydomain.com
01/08/2013|13:16:01.684 BF0:BE8 INFO  :: CUccIceServerSetup::GetHttpProxyServerFromSignalingSettings - didn't find http proxy in signaling path
01/08/2013|13:16:01.684 BF0:BE8 INFO  :: CUccIceServerSetup::SetUpMediaSessionIceServers MR-INFO - 2 media relay infos found on UccEndpoint
01/08/2013|13:16:01.684 BF0:BE8 INFO  :: CUccIceServerSetup::SetUpMediaSessionIceServers MR-INFO - List of media relays to be used for this call:

Am I correct in my understanding that application sharing uses the FE pool web services rather than the Edge gateway?  Currently I forward only 443 and 80 to the FE External website; I'm using a second internal IP and have adjusted the listening ports from 4443 and 8080.  From the internet you can reach the FE web services, and address book downloading works like it should.

What is the above trying to tell me?
0
Comment
Question by:HydrofarmIT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
6 Comments
 

Author Comment

by:HydrofarmIT
ID: 38760059
I did more testing this morning, with firewalls disabled on both the Edge and external client, and it appears that the external client is trying to route directly to the internal IP of the other app-sharing participant.  Or at least, when I try to initiate a screensharing session I see the external client attempting to connect to the internal client address 192.168.1.27, instead of the Edge.  

I also started the logging tool on the Edge server, capturing the error shown below.


TL_INFO(TF_NETWORK) [0]08D8.10F4::01/09/2013-18:02:08.550.0000025a (SIPStack,CRecvContext::ProcessCompletion:RecvContext.cpp(155))( 0000000004B01A60 ) Received 373 bytes
TL_INFO(TF_PROTOCOL) [0]08D8.10F4::01/09/2013-18:02:08.550.0000025c (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 1784782406
Instance-Id: 00096CA9
Direction: incoming;source="external edge";destination="internal edge"
Peer: 70.199.84.120:28805
Message-Type: request
Start-Line: BYE sip:codell@mydomain.com;opaque=user:epid:PLwfL5RCTFyFfpqN_R38DgAA;gruu SIP/2.0
From: <sip:mwallace@mydomain.com>;tag=3e90890416;epid=b8bd564b40
To: <sip:codell@mydomain.com>;epid=aadbd21391;tag=e502928ce6
CSeq: 2 BYE
Call-ID: d2f8da3a28914298af2bc3878a207269
Via: SIP/2.0/TLS 192.168.1.2:49459
Max-Forwards: 70
Route: <sip:lyncedge.mydomain.com:5061;transport=tls;opaque=state:Ci.Rcd700;lr;ms-route-sig=co4Btw0TKnYcr1xmKkwC_MsvnXOvw__pIavKQES6mYijyw2ZcEcFqQTAAA>
Route: <sip:SQL2.mydomain.com:5061;transport=tls;opaque=state:T:F:Eu;lr;received=192.168.1.56;ms-received-cid=CB800>
User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
ms-client-diagnostics: 23; reason="Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote";CallerMediaDebug="application-sharing:ICEWarn=0x320,LocalSite=70.199.84.120:28800,LocalMR=69.12.217.231:57425,RemoteSite=192.168.1.27:2642,PortRange=1025:65000,LocalMRTCPPort=57425,LocalLocation=1,RemoteLocation=2,FederationType=0"
Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="AABF84BD", targetname="SQL2.mydomain.com", crand="7d7715af", cnum="41", response="276dcb1810390e7e67300fa2266652f5a34aef70"
Content-Length: 0
Message-Body: –
$$end_record
0
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 38765175
Yes, your topology is broken. The use of the reverse proxy and the external and internal URLs was done on purpose so that the client can determine if it is being NATed or not. By bypassing that topology requirement, not only is it "not recommended" ...it is not supported. For a reason. Until you fix your topology setup, there is no reliable way to make this work. It is a fundamental limitation of the SIP protocol and not Lync specific, but which Lync does use for signal control.
0
 

Author Closing Comment

by:HydrofarmIT
ID: 38765305
Ok, thank you, I was wagering that the lack of reverse proxy was central to my problems but hadn't yet been able to grasp precisely why.  Was trying to get around it just because I don't have a 3rd server to bring into the mix just to run the proxy.
0
 

Author Comment

by:HydrofarmIT
ID: 38842601
Actually the reverse proxy seems to have nothing to do with my problem.  I've reconfigured with Forefront on a separate box, functioning as it should.  My problem with application sharing (and also file-transfer, I've noticed) remains.
0
 

Author Comment

by:HydrofarmIT
ID: 38851806
In the end, topology had nothing to do with this; Kaspersky anti-virus was interfering.  After excluding the communicator.exe process from monitoring this problem went away.
0

Featured Post

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Technology opened people to different means of presenting information, but PowerPoint remains to be above competition. Know why PPT still works today.
Know what services you can and cannot, should and should not combine on your server.
Viewers will learn the different options available in the Backstage view in Excel 2013.
The viewer will learn how to create two correlated normally distributed random variables in Excel, use a normal distribution to simulate the return on different levels of investment in each of the two funds over a period of ten years, and, create a …

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question