none
Problems calling between External and Internal

    Question

  • I've been through every post and blog I can find on the subject, and I'm stuck.

    I cannot successfully connect a call between Lync users when one is external and one is internal.  IM works.  PSTN calling works. 

    Excerpt from cilent tracing log (external client):

    ms-client-diagnostics: 21; reason="Call failed to establish due to a media connectivity failure where one endpoint is of unknown type";CalleeMediaDebug="audio:ICEWarn=0x222,LocalSite=192.168.1.3:20006,LocalMR=67.210.230.173:56802,RemoteSite=192.168.200.100:23519,PortRange=20000:20039,LocalMRTCPPort=56802,LocalLocation=1,RemoteLocation=0,FederationType=0,NetworkName=McCarthy_WiFi,Interfaces=4,BaseInterface=4,BaseAddress=192.168.1.3:20012"

    One thing in that error that I can't make sense of (besides all of it...) is the 'RemoteSite' IP -- that does not exist in our topology?

    Any and all help is appreciated, this is the only major roadblock left to my first Lync deployment.

    Thank you!

    -Sean

    Saturday, September 21, 2013 3:08 PM

Answers

  • Well I spent the morning tearing apart the edge server and reconfiguring.  After modifying and verifying DNS and certificates, and restarting services a number of times, I am able to call in and out between internal and external clients now.  Can't say for sure which step solved it, but DNS and certs make or break Lync.

    -Sean

    Saturday, September 21, 2013 8:51 PM

All replies

  • Do you have static routes on your edge server to each of the subnets that have Internal clients? Take a Look at Ken Lasko's blog: http://ucken.blogspot.ca/2012/01/lync-edge-server-static-routes.html


    Saturday, September 21, 2013 5:31 PM
  • Is 67.210.230.173 your A\V edge external IP and is it correct?
    Saturday, September 21, 2013 5:36 PM
  • I have static routes on the edge server, along with host file entries for all servers it needs to access. I can ping between the edge server and all other servers (mediation, front end, exchange, dc).

    67.210.230.173 is indeed my AV edge external IP.

    I should mention, the edge server is behind a TMG as well.

    Saturday, September 21, 2013 6:48 PM
  • Do you get any errors when running the Lync remote connectivity analyzer tests? https://www.testexchangeconnectivity.com/
    Saturday, September 21, 2013 7:00 PM
  • When I ran tests yesterday I did not get any errors from the connectivity tests.  I ran it just now and get a sign-in error.  Which is very odd, considering I'm signed in on my laptop and my android phone right now...
    Saturday, September 21, 2013 7:37 PM
  • Well I spent the morning tearing apart the edge server and reconfiguring.  After modifying and verifying DNS and certificates, and restarting services a number of times, I am able to call in and out between internal and external clients now.  Can't say for sure which step solved it, but DNS and certs make or break Lync.

    -Sean

    Saturday, September 21, 2013 8:51 PM
  • if this media pass through the cooperate firewall you should have to open the appropriate ports to work. 

    http://technet.microsoft.com/en-us/library/gg195662(v=ocs.14).aspx

    Sunday, September 22, 2013 4:33 AM