Lync 2013 PSTN calling not working with Sonus SBC 1000 over TLS and SRTP

Dear All,
We have recently installed Lync 2013 Enterprise Edition with a Pool of 3 FE Servers (MEDIATION COLLOCATED).
We need to implement TLS and SRTP with Sonus SBC 1000. However calls are not routing b/w SBC and Lync.
We are using wild card certificate with multiple SIP Domains as SAN(s), for internal FE servers as well SBC.
Also i would like to mentioned here that inbound and outbound calls are routing properly when we tested it over TCP.
When I move to TLS Only calls from Lync to SBC (outgoing) are working without encryption.
Here are the OCS Logger traces for incoming calls which are not landing on lync:
TL_INFO(TF_PROTOCOL) [1]2C5C.0D30::04/30/2014-14:35:18.020.00026518.020.00026518.020.00026518.020.00026518.020.00026518.020.00026518.020.00026518.020.000265d2
(S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[3491463749]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_AE0419>], 10.10.0.11:5067->10.10.7.50:25678
SIP/2.0 400 Bad Request
FROM: "3158222726"<sip:[email protected]>;tag=ac3201ce-4d7
TO: <sip:[email protected]:5067>;epid=D2091CF753;tag=f373543c
CSEQ: 2 INVITE
CALL-ID: [email protected]
VIA: SIP/2.0/TLS 10.10.7.50:5067;branch=z9hG4bK-UX-ac32-01ce-0b14
CONTENT-LENGTH: 0
SERVER: RTCC/5.0.0.0 MediationServer
------------EndOfOutgoing SipMessage
TL_INFO(TF_PROTOCOL) [1]2C5C.0D30::04/30/2014-14:35:18.027.00026518.027.00026518.027.00026518.027.00026518.027.00026518.027.00026518.027.00026518.027.000265d7
(S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[2666394843]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_370F030>], 10.10.0.11:58059->10.10.0.13:5061
SERVICE sip:2138797082;[email protected];user=phone SIP/2.0
FROM: <sip:2138797082;[email protected];user=phone>;epid=DCFDB95F4C;tag=17d286a93
TO: <sip:2138797082;[email protected];user=phone>
CSEQ: 3 SERVICE
CALL-ID: de750f98bdd94e908be5f2f975228ff7
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 10.10.0.11:58059;branch=z9hG4bKd47f1d3c
CONTACT: <sip:[email protected];gruu;opaque=srvr:MediationServer:CiGdW3iH5FiI3Qvr3PIKGQAA>
CONTENT-LENGTH: 630
SUPPORTED: gruu-10
USER-AGENT: RTCC/5.0.0.0 MediationServer
CONTENT-TYPE: application/msrtc-reporterror+xml
<?xml version="1.0" encoding="us-ascii"?>
<reportError xmlns="http://schemas.microsoft.com/2006/09/sip/error-reporting">
<error callId="[email protected]" fromUri="sip:3158222726;[email protected];user=phone" toUri="sip:2138797082;[email protected];user=phone" fromTag="ac3201ce-4d7"
toTag="" requestType="INVITE" contentType="application/sdp;call-type=audio" responseCode="400"><diagHeader>10013;reason="Gateway peer in inbound call is not found in topology document or does not depend
on this Mediation Server"</diagHeader><progressReports /></error></reportError>------------EndOfOutgoing SipMessage
Call
Send SMS
Add to Skype
You'll need Skype CreditFree via Skype

@Paul, Thanks for you response.
All ports / IP Add / DNS are defined properly. Telenet on listening port is working.
We are using Public Certificate for 3 Domains (wild card) and same is loaded and verified in SBC
I've not reviewed the OCS logs properly posted above.
What i've found or seems to me is that in a TLS Calls:
After receiving SIP Invite from SBC, mediation server started TLS Negotiation Process b/w Lync 2013 Server Pool and it fails.
SIP Domains:
contoso.com (default)
fabrikam.com
Lync FE Pool (lync.contoso.com
Here are the some more logs.
TL_INFO(TF_PROTOCOL) [0]2DF8.2930::05/01/2014-11:50:31.612.00025e49 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[2716989131]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_103DFE0>], 10.10.0.11:5067<-10.10.7.50:24591
INVITE sip:[email protected]:5067 SIP/2.0
FROM: "3158222726" <sip:[email protected]>;tag=ac3201ce-ae
TO: <sip:[email protected]:5067>
CSEQ: 2 INVITE
CALL-ID: [email protected]
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 10.10.7.50:5067;branch=z9hG4bK-UX-ac32-01ce-010c
CONTACT: <sip:[email protected]:5067;transport=TLS>
CONTENT-LENGTH: 406
SUPPORTED: replaces,update,100rel
USER-AGENT: SONUS SBC1000 3.1.2v293 Sonus SBC
CONTENT-TYPE: application/sdp
ALLOW: INVITE, ACK, CANCEL, BYE, NOTIFY, OPTIONS, REFER, REGISTER, UPDATE, PRACK
P-ASSERTED-IDENTITY: "3158222726" <sip:[email protected]>
v=0
o=SBC 9 1001 IN IP4 10.10.7.50
s=VoipCall
c=IN IP4 10.10.7.50
t=0 0
m=audio 16418 RTP/AVP 8 0 101 13
c=IN IP4 10.10.7.50
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:13 CN/8000
a=ptime:20
a=tcap:1 RTP/SAVP
a=pcfg:1 t=1
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:pqL6Tke8pVmXPuplJ1G3+Sr9jM97H8R7iBagWzzh|2^31|1:1
a=sendrecv
------------EndOfIncoming SipMessage
TL_INFO(TF_PROTOCOL) [1]2DF8.0E04::05/01/2014-11:50:31.665.00025e8e (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[2716989131]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_103DFE0>], 10.10.0.11:5067->10.10.7.50:24591
SIP/2.0 100 Trying
FROM: "3158222726"<sip:[email protected]>;tag=ac3201ce-ae
TO: <sip:[email protected]:5067>
CSEQ: 2 INVITE
CALL-ID: [email protected]
VIA: SIP/2.0/TLS 10.10.7.50:5067;branch=z9hG4bK-UX-ac32-01ce-010c
CONTENT-LENGTH: 0
------------EndOfOutgoing SipMessage
TL_INFO(TF_CONNECTION) [1]184C.0EFC::05/01/2014-11:50:32.652.00025f32 (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(454))[946832530] $$begin_record
Severity: information
Text: TLS negotiation started
Local-IP: 10.10.0.11:5061
Peer-IP: 10.10.0.11:52529
Connection-ID: 0x10BE00
Transport: TLS
$$end_record
TL_INFO(TF_PROTOCOL) [1]184C.0EFC::05/01/2014-11:50:32.669.00026236 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[1853494582] $$begin_record
Trace-Correlation-Id: 1853494582
Instance-Id: 425D
Direction: incoming
Peer: 10.10.0.11:52529
Message-Type: request
Start-Line: NEGOTIATE sip:127.0.0.1:5061 SIP/2.0
FROM: <sip:contoso.com>;ms-fe=LYNCFE1.fabrikam.com
TO: <sip:contoso.com>
CALL-ID: aa53739ef9b34b93ba9c97d3ee56cb99
CSEQ: 1 NEGOTIATE
VIA: SIP/2.0/TLS 10.10.0.11:52529
MAX-FORWARDS: 0
CONTENT-LENGTH: 0
SUPPORTED: NewNegotiate
SUPPORTED: ECC
REQUIRE: ms-feature-info
SERVER: RTC/5.0
$$end_record
TL_INFO(TF_CONNECTION) [1]184C.0EFC::05/01/2014-11:50:32.669.0002636e (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(383))[946832530] $$begin_record
Severity: information
Text: Connection established
Peer-IP: 10.10.0.11:52529
Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
Peer-Cert: contoso.com(LYNCFE1.fabrikam.com)
Transport: M-TLS
Data: alertable="yes"
$$end_record
TL_WARN(TF_CONNECTION) [1]184C.0EFC::05/01/2014-11:50:32.669.00026387 (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(386))[946832530] $$begin_record
Severity: warning
Text: The pool FQDN provided by the peer in its NEGOTIATE feature information does not match the pool configured in CMS for the server FQDN that it provided
Peer-IP: 10.10.0.11:52529
Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
Peer-Cert: contoso.com(LYNCFE1.fabrikam.com)
Transport: M-TLS
Data: fqdn="LYNCFE1.fabrikam.com";pool="contoso.com";expected-fqdn="lync.contoso.com";info="Possible server configuration issue"
$$end_record
TL_INFO(TF_DIAG) [1]184C.0EFC::05/01/2014-11:50:32.670.000265be (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(802))[1853494582] $$begin_record
Severity: information
Text: Routed a locally generated response
SIP-Start-Line: SIP/2.0 200 OK
SIP-Call-ID: aa53739ef9b34b93ba9c97d3ee56cb99
SIP-CSeq: 1 NEGOTIATE
Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
$$end_record
TL_INFO(TF_PROTOCOL) [1]184C.0EFC::05/01/2014-11:50:32.670.00026615 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[1853494582] $$begin_record
Trace-Correlation-Id: 1853494582
Instance-Id: 425E
Direction: outgoing;source="local"
Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
Message-Type: response
Start-Line: SIP/2.0 200 OK
FROM: <sip:contoso.com>;ms-fe=LYNCFE1.fabrikam.com
To: <sip:contoso.com>;tag=C3A751556F332F7265E9BA2517C878D4
CALL-ID: aa53739ef9b34b93ba9c97d3ee56cb99
CSEQ: 1 NEGOTIATE
Via: SIP/2.0/TLS 10.10.0.11:52529;ms-received-port=52529;ms-received-cid=10BE00
Content-Length: 0
Require: ms-feature-info
Supported: NewNegotiate,OCSNative,ECC,IPv6,TlsRecordSplit
Server: RTC/5.0
$$end_record
TL_INFO(TF_PROTOCOL) [1]2DF8.1078::05/01/2014-11:50:32.671.000266da (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[720988281]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_F8A09B>], 10.10.0.11:52529->10.10.0.11:5061
SERVICE sip:2138797082;[email protected];user=phone SIP/2.0
FROM: <sip:2138797082;[email protected];user=phone>;epid=16FEE4A02E;tag=22fd877f3a
TO: <sip:2138797082;[email protected];user=phone>
CSEQ: 3 SERVICE
CALL-ID: ac0f7bc4cdc94c1dbd0bb51c7c02c890
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 10.10.0.11:52529;branch=z9hG4bK67a4c9d1
CONTACT: <sip:[email protected];gruu;opaque=srvr:MediationServer:CiGdW3iH5FiI3Qvr3PIKGQAA>
CONTENT-LENGTH: 628
SUPPORTED: gruu-10
USER-AGENT: RTCC/5.0.0.0 MediationServer
CONTENT-TYPE: application/msrtc-reporterror+xml
- <reportError xmlns="http://schemas.microsoft.com/2006/09/sip/error-reporting">
- <error callId="[email protected]"
fromUri="sip:3158222726;[email protected];user=phone"
toUri="sip:2138797082;[email protected];user=phone"
fromTag="ac3201ce-ae"
toTag=""
requestType="INVITE"
contentType="application/sdp;call-type=audio"
responseCode="400">
<diagHeader>10013;reason="Gateway peer in inbound call is not found in topology document or does not depend on this Mediation Server"</diagHeader>
<progressReports/>
- </error>
------------EndOfOutgoing SipMessage

Similar Messages

  • Lync 2013 /w Edge not working properly (internal/external same domain name and all "external" users"

    Hi,
    I've got some issues with a Lync 2013 setup.
    The config consists of 2 lync servers. One FE and one Edge. All seems to work except audio in meetings and Sip.
    The setup is like this (fake ip's used):
    Front End:
    Internal IP: 172.16.0.10
    External IP: x.x.185.10
    All ports open in Cisco ASA
    internal AD DNS: dialin/lync/meet/lyncdiscover to Front end internal ip. edge/lsedge/sip points to edge internal ip
    EDGE:
    Interal IP: 172.16.0.11 (no gateway configured)
    External IPS: x.x.185.11, x.x.185.12, x.x.185.13
    All external IP's are direct internet facing, no NAT (a firewall is in place).
    All external interfaces are using a wildcard certificate.
    All server are running in a remote data center, so basically no internal users. We all connect to the external interfaces. The Windows domain name (AD) is the same as our External DNS (companyname.com).
    Autodiscover works, we can logon, chat but there is no audio. The audio test failes. Also SIP is not working with a sip trunk.
    External DNS: sip/webconf/av are pointing to their external ip's. sipexternal is a cname to sip. lyncdiscover/lync/dialin/meet all point to the Frond end External ip.
    _sip._tls/_sipfederationtls.tcp/_xmpp-server.tcp all point to the sip.companyname.com ip.
    I just can't figure out what is wrong.

    @PSingh123 I'll try the logs in a minute and get back with the results.
    @PaulB_NZ Thanks for the input. In my opinion the FE does need an external IP. How else will you be able to connect if you are a remote worker?
    The Edge is (asfar as i know) needed for Enterprise voice and Federation with other (external) sip domains. It's not needed for basic (chat/video/whiteboard etc) Lync functionality for both internal and external (remote) users.
    The Edge is to communicate with services/users outside the origanisation.
    I do still think that the basic topology (FE with internal IP and Nat'ed external ip working with an Edge with internal IP and 1 external IP nat'ed to 3 DMZ ip's) is correct in this case.
    I can be wrong and in that case would like to be pointed to the correct configuration.
    75           
    Points
    Top 15
    PSingh123        
    Partner        
    Joined  Jun 2007        
    9
    PSingh123's threads
    Show activity

  • Problem Lync 2013 File Transfer not working with externally connected users

    I've a Single consolidated edge with private IP addresses using NAT in Lync Server 2013 and I'm facing some problem during File Transfer with all users outside my network both federated user or user of my lync infrastructure externally connected.
    I drag and drop a file into the conversation, I press enter then the receiver see only the icon without the "save as" option

    Hi,
    Did you receive any error on FE Server or Edge Server when the issue happen?
    Make sure all Lync Services started on Edge Server (especially for Lync Server Web conferencing Edge).
    Check if CMS status on Edge Server update to the latest status.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Click to call not working with Firefox 31 in Windo...

    Hello All,
    I have a problem with Click to Call in my new computer.
    Windows 8.1
    Skype 6.20.0.104
    Click to call 7.3.16540.9015
    Firefox 31
    Click to Call not working with Firefox.
    With IE11 it ok.
    When I directly copy the URL "skype:+48xxxxxxxxx?call"  into address field of my Firefox, then automatically opening Skype with only 1 window- contacts, but not opened window with call phone, and not started to call.
    When I do this same in IE11 , Skype opened 2 windows ( contacts and call phone) and start call to phone number.
    I don't know why. because in my second computer ( this same Firefox, Skype, click to call) but Windows 7, Click to Call working with Firefox.
    Please help me.
    Maybe someone have a solution ?
    Best Regards
    Jarek
    ps. Sorry for my english

    Sounds that you have installed a Firefox Beta release and thus are on the beta update channel, see Help > About.<br />
    The Beta update channel receives an update twice a week.
    You need to install the current release to switch the update channel to release.
    Download a fresh Firefox copy and save the file to the desktop.
    *Firefox 27: http://www.mozilla.org/en-US/firefox/all.html
    If possible uninstall your current Firefox version to cleanup the Windows registry and settings in security software.
    *Do NOT remove personal data when you uninstall your current Firefox version, because all profile folders will be removed and you lose personal data like bookmarks and passwords from profiles of other Firefox versions.
    Your bookmarks and other personal data are stored in the Firefox profile folder and won't be affected by an uninstall and (re)install, but make sure that "remove personal data" is NOT selected when you uninstall Firefox.

  • Lync Server 2010 conference not working with Windows 8.1 and IE 10

    Hello,
    The problem is that whenever a Windows 8.1 user tries to join a Lync server 2010 conference using Internet Explorer 10 (or 11, tried that too) the user can't join the conference. If the conference is created by a Lync server 2013 user joining works fine.
    When using Lync 2010 client we get the following error in the client: "error id 87 source id 7".
    When using Lync 2013 client we end up with a blank conversation window.
    There are no traces in server log, client log or event log.
    Below is a set of use cases that may help you to understand what is the problem scenario. Each of these works or does not work with both Lync 2010 and Lync 2013 client.
    - Lync server 2010 conference, windows 7, Chrome, Firefox, IE 10 or 11 --> Works.
    - Lync server 2010 conference, windows 8.1, IE 10 or 11 --> Does not work.
    - Lync server 2010 conference, windows 8.1, Chrome or Firefox --> Works.
    - Lync server 2013 conference, windows 8.1, Chrome, Firefox, IE 10 or 11 --> Works.
    It does not help to add the meet address to IE compatibility list (Compatibility View Settings).
    If i press F12 in IE and change the document mode of the meet page to IE 9 version then i can join meetings with Windows 8.1 and IE 10. Unfortunately i cannot make that as a default setting for the meet website.
    Any ideas on how to get Lync server 2010 meetings working with Windows 8.1 and IE 10 or 11?
    IE is the company default browser. Windows 8.1 is not a default operating system but we have increasing number of Windows 8.1 computers in our environment (mainly directors).

    According to your description, it is hard to tell whether the issue is related with IE or Lync Server 2010 or both.
    Compare the log when Lync client on Window 8.1 with IE 10 or IE 11 join Lync server 2010 conferencing and Lync Server 2013 conferencing.
    Lisa Zheng
    TechNet Community Support

  • Graphite base station not working with my Intel Based Mac Mini and iPhone.

    My Airport Express died after 2 years of use. I had to resort to plugging in my old but still functioning Graphite Airport base station. Since the set up assisant on my Mac mini does not work with the older base station, I used my G4 400 tower to set it up. I got it working and tested the connection. On to testing my iPhone. It sees the new network. Password is entered and the wifi icon shows full signal strength, but does not connect to the web. Next I try my Mac mini out on the new network and it too sees the network, but does not connect to the web. I double check the older G4 and the connection is still strong and fast. I shut the G4 down thinking that maybe the Graphite can only support one computer at a time, and the Mac mini and iPhone still can't connect to the web. I'm not sure what to do with this one. Is there a setting that I need to use? As far as security goes, the Graphite base station was set up with a WEP password. Any help would be great
    Message was edited by: Soriano

    I suggest using AirPort Admin Utility (version 4.2) to check the base station settings and change them, if necessary. (AirPort Admin Utility should be able to configure a Graphite base station from a computer running Mac OS X 10.4, even though AirPort Setup Assistant can't.)
    In the Network pane of AirPort Admin Utility, please make sure that "Distribute IP addresses" and "Share a single IP address (using DHCP and NAT)" are checked, and that everything else is unchecked. I am assuming that the Graphite is the only router in your local network and that there are no computers connected via Ethernet.
    The Access Control pane of AirPort Admin Utility should list either all of the relevant AirPort ID's or nothing. You can find the AirPort ID of an OS X computer by looking at System Preferences>Network>Show:AirPort>AirPort.
    The Internet pane of AirPort Admin Utility should be set in accordance with your Internet provider's requirements. Most likely, it should be set to Connect Using:Ethernet and Configure:Using DHCP.
    After verifying the settings, power down the computers, base station and cable or DSL modem for a few minutes, then start them up sequentially, leaving time for each to get fully up and running: first the modem, then the base station, and finally the computers.
    The network preferences on the Mac Mini and the iPhone are also relevant. I assume that the preferences are unchanged from those that worked with the AirPort Express.
    I hope this helps.

  • Lync 2013 A/V not working federated partner

    Hi,
    I have an interesting problem. I cant make video calls / desktop sharing via only federated
    domain. But IM working properly. There is a problem only A/V call.
    in my lync organization :
    1 front-end
    1 edge
    1 reverse proxy
    From
    To
    Type
    Result
    My Lync User ( Inside )
    My Lync User ( Outside )
    IM & A/V & Desktop Sharing
    Success
    My Lync User ( Inside or Outside ) from PC
    Federated Lync domain
    IM
    Success
    My Lync User ( Inside or Outside ) from PC
    Federated Lync domain
    A/V & Desktop Sharing
    Fail due network isses
    My Lync User ( Inside or Outside ) from Lync Mobile  to Federated Lync domain, type: Audio / Video call. result:
    success
    If you sign in from Lync mobile client and start video call to federated domain worked successfully. But if you sign in from PC Lync 2013 client and start video call, to federated domain,
    fail. Video invitation is reached federated domain and connection established but after a few seconds, A/V failed due network issues or audio video device not configured.
    During issue, i collected log using OcsLogger on the Edge Server. I examined the collected log but I could not find a error line.
    please help
    thanks

    Hi,
    From your description above, there is something wrong during the deployment of Edge Server.
    To avoid routing issues, make sure there are at least two network adapters in your Edge Servers and that the default gateway is set only on the network adapter associated with the external interface.
    You can configure two network adapters in your Edge Server as follows:
    Network adapter 1 (Internal Interface)
    For example: Internal interface with 172.25.33.10 assigned.
    No default gateway is defined.
    Ensure that there is a route from the network containing the Edge internal interface to any networks that contain servers running Lync Server 2013 or Lync Server 2013 clients.
    Network adapter 2 (External Interface)
    Three private IP addresses are assigned to this network adapter, for example 10.45.16.10 for Access Edge, 10.45.16.20 for Web Conferencing Edge, 10.45.16.30 for AV Edge.
    More details:
    http://technet.microsoft.com/en-us/library/gg412787.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Lync 2013 Edge replication not working

    hi, I have a Lync 2013 Edge replication issue - it is simply not working.
    UpToDate           : False
    ReplicaFqdn        : LyncEdge.contoso.com
    I have already checked the following:
    1) telnet from FEP servers to the Edge sever on port 4443 is working
    2) Certificates are installed correctly - Lync Federation, Voice/Video to Skype, Lync Mobile is all working fine.
    3) Replication traffic checking showing the following error in XDS logs:
    (000000000126DB35)[FileTransferTask(11, 9/03/2015 2:44:24 PM): {TASK_NOT_STARTED, fromReplica, [lyncedge.contoso.com, HttpsWebService, 4443], 0}] Failed to copy files from replica. Exception: [System.ServiceModel.Security.MessageSecurityException: The HTTP
    request was forbidden with client authentication scheme 'Anonymous'. ---> System.Net.WebException: The remote server returned an error: (403) Forbidden.
       at System.Net.HttpWebRequest.GetResponse()
       at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       --- End of inner exception stack trace ---
    Server stack trace:
       at System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication(HttpWebRequest request, HttpWebResponse response, WebException responseException, HttpChannelFactory factory)
       at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException, ChannelBinding channelBinding)
       at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.Rtc.Xds.Replication.Common.IReplicationWebService.DownloadFiles(String senderFqdn, String sourceDirPath, String tempDirPath)
       at Microsoft.Rtc.Xds.Replication.FileTransfer.FileTransferTask.CopyFilesFromReplicaUsingWcf(String fromDir, String tmpDir, String toDir)]
    I have checked certificate stores: there are only 34 certificates in the Root folder and the SendTrustedIssuerList reg. key has been configured, which did not solve the issue.
    Any idea how to troubleshoot this or possible root causes?

    Try Test-CsComputer on the Frontend Servers and the Edge Servers. This should check Windows Firewall exceptions are correct. Then check permissions on your Lync fileshare. You can also try to reinstall CMS Database with the following command (user must be
    memeber of CsAdministrator group and sysadmin group of SQL Server)
    Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn CMS.FQDN 
    -SqlInstanceName DBInstance -Verbose

  • Lync 2013 External Mobility Not Working

    Hello,
    The issue I seem to be having is in regards to the external mobility access. 
    So far everything else in our environment seems to be functioning properly. 
    The Lync desktop client works both internally as well as externally. 
    The Lync internal mobility also works.  The only issue seems to be with the external mobility part.
    I tried going to the external autodiscover address for our system, https://lyncdiscover.mydomain.com but it doesn’t return anything either. 
    I think the issue lies somewhere with DNS or my reverse proxy, however I’m having a hard time being able to just start changing settings seeing as how I don’t want to break everything that is currently working for our users.
    I’ve been through a lot of the post here but I still can’t seem to find the settings to fix the issue I’m having.
    Here is a breakdown of my settings I feel are in question:
    1 – Lync 2013 FE Server (LYNC01)
    1 – Lync Edge Server (EDGE01)
    1 – Reverse Proxy Server (RPROXY01)
    Public DNS:
    A Records
    SIP.mydomain.com                          
    205.XXX.XXX.91 (Access Service on EDGE01)
    AccessEdge.mydomain.com              
    205.XXX.XXX.91 (Access Service on EDGE01)
    WebConfEdge.mydomain.com            205.XXX.XXX.92 (WebConf Service on EDGE01)
    AVEdge.mydomain.com                    
    205.XXX.XXX.93 (A/VEdge Service on EDGE01)
    meet.mydomain.com                        
    205.XXX.XXX.94 (Reverse Proxy Server)
    dialin.mydomain.com                        
    205.XXX.XXX.94 (Reverse Proxy Server)
    lync.mydomain.com                          
    205.XXX.XXX.94 (Reverse Proxy Server)
    lyncdiscover.mydomain.com               205.XXX.XXX.94 (Reverse Proxy
    Server)
    SRV
    _sip._tls.mydomain.com:443                                     
    AccessEdge.mydomain.com
    _sipfederationtls._tcp.mydomain.com:5061             
    AccessEdge.mydomain.com
    _xmpp-server._tcp.mydomain.com                          
    AccessEdge.mydomain.com
    Private DNS:
    A Records
    LYNC01                                            
    172.XXX.XXX.65 (LYNC01 FE Server)
    Admin                                              
    172.XXX.XXX.65 (LYNC01 FE Server)
    Dialin                                               
    172.XXX.XXX.65 (LYNC01 FE Server)
    LyncDiscoverInternal                         
    172.XXX.XXX.65 (LYNC01 FE Server)
    Meet                                                
    172.XXX.XXX.65 (LYNC01 FE Server)
    Sip                                                  
    172.XXX.XXX.65 (LYNC01 FE Server)
    EDGE01                                            
    172.XXX.XXX.66 (EDGE01 Server)
    RPROXY01                                        
    172.XXX.XXX.70 (Reverse Proxy Server)
    Lync                                                 
    205.XXX.XXX.94 (Reverse Proxy Server)
    LyncDiscover  
    (CNAME)                    
    lync.gmsd.k12.pa.us
    SRV
    _xmpp-server._tcp.mydomain.com                          
    Sip.mydomain.com
    _sipinternaltls._tcp.mydomain.com:5061                 
    LYNC01.mydomain.com
    Lync Server Services Addresses
    Lync FE Server:                      \\
    LYNC01.mydomain.com (172.XXX.XXX.65)
    File Store:                              \\
    LYNC01.mydomain.com\Share
    Office Web Apps Server:
             \\lyncowa.mydomain.com
    External Web Services:
               \\lync.mydomain.com
    Edge Server Services Addresses
    Edge Server:                  
    \\ EDGE01.mydomain.com (172.XXX.XXX.66)
    Access Edge Service:       
    \\AccessEdge.mydomain.com (172.XXX.XXX.67, 205.XXX.XXX.91)
    Web Conference Service:  \\WebConfEdge.mydomain.com (172.XXX.XXX.68, 205.XXX.XXX.92)
    A/V Edge Service:            \\WebConfEdge.mydomain.com
    (172.XXX.XXX.69, 205.XXX.XXX.93)
    Reverse Proxy Server Addresses
    Reverse Proxy Server:            
    RPROXY01.mydomain.com (172.XXX.XXX.70, 205.XXX.XXX.94)
    Server Farms:
    Dialin.mydomain.com:
    Dialin.mydomain.com (LYNC01)
    Meet.mydomain.com:
    Meet.mydomain.com (LYNC01)
    LyncDiscover.mydomain.com:
               LYNC01.mydomain.com (LYNC01)
    Lync.mydomain.com:                       
    LYNC01.mydomain.com (LYNC01)
    Edge External Cert
    AccessEdge.mydomain.com
    Sip.mydomain.com
    WebConfEdge.mydomain.com
    Reverse Proxy Cert
    lync.mydomain.com
    meet.mydomain.com
    dialin.mydomain.com
    lyncdiscover.mydomain.com
    lyncowa.mydomain.com
    With everything else working as it should, this external mobility part is just not really making sense to me.  I have also verified that the correct ports are being using on the reverse proxy as well for the server farms,
    8080 and 4443.  Any help would be greatly appreciated.  Thank you.

    I'm also attaching the log file from running Lync Connectivity Analyzer if it helps.
    [6/10/2014 7:30:18 AM] [DEBUG] Logging test parameters:
    [6/10/2014 7:30:18 AM] [DEBUG] SIP Uri: [email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] User Name:
    [6/10/2014 7:30:18 AM] [DEBUG] Discovery Type: Automatic Discovery
    [6/10/2014 7:30:18 AM] [DEBUG] Network access: NetworkAccessExternal
    [6/10/2014 7:30:18 AM] [DEBUG] Selected client: ApplicationLyncMobile2010
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting Lync server autodiscovery
    [6/10/2014 7:30:18 AM] [INFO] Please wait; this test may take several minutes to complete...
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting automatic discovery for secure (HTTPS) internal channel
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lyncdiscoverinternal.mydomain.com/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      Pragma: no-cache
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 670
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL https://lyncdiscoverinternal.mydomain.com/[email protected].  Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="Internal"><Root><Link token="Domain" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/domain" /><Link token="User" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user"
    /><Link token="OAuth" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/oauth/user" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /></Root></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover URL https://lyncdiscoverinternal.mydomain.com/[email protected] redirected to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 401, ReasonPhrase: 'Unauthorized', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      X-MS-WebTicketURL: https://lync01.mydomain.com/WebTicket/WebTicketService.svc
      X-MS-WebTicketSupported: cwt,saml
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-Powered-By: ASP.NET
      Content-Length: 1293
      Content-Type: text/html
    [6/10/2014 7:30:18 AM] [DEBUG] Authorization required for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Obtaining WebTicket from https://lync01.mydomain.com/WebTicket/WebTicketService.svc
    [6/10/2014 7:30:18 AM] [DEBUG] On-premises WebTicket server: https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] AcquireTicketAsync succeeded for https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] WebTicket: <saml:Assertion MajorVersion="1" MinorVersion="1" AssertionID="SamlSecurityToken-4e51bf2a-2849-4779-a595-a5040c22ff1b" Issuer="https://lync01.mydomain.com/63b16135-930c-5e0b-998c-7ed6bc68b6f8" IssueInstant="2014-06-10T11:30:18.173Z"
    xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"><saml:Conditions NotBefore="2014-06-10T11:30:18.173Z" NotOnOrAfter="2014-06-10T19:23:01.173Z"><saml:AudienceRestrictionCondition><saml:Audience>https://lync01.mydomain.com/</saml:Audience></saml:AudienceRestrictionCondition></saml:Conditions><saml:AuthenticationStatement
    AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:unspecified" AuthenticationInstant="2014-06-10T11:30:18.173Z"><saml:Subject><saml:NameIdentifier Format="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/uri">sip:[email protected]</saml:NameIdentifier><saml:SubjectConfirmation><saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:holder-of-key</saml:ConfirmationMethod><KeyInfo
    xmlns="http://www.w3.org/2000/09/xmldsig#"><e:EncryptedKey xmlns:e="http://www.w3.org/2001/04/xmlenc#"><e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#kw-aes256"></e:EncryptionMethod><KeyInfo><KeyName>63b16135-930c-5e0b-998c-7ed6bc68b6f8:8d152b04ce7ddbf</KeyName></KeyInfo><e:CipherData><e:CipherValue>7M3R6naVg1ifGvuQKTMS+4EjHlJrdZeQqsqobNZUhMxHE9y7klUmXw==</e:CipherValue></e:CipherData></e:EncryptedKey></KeyInfo></saml:SubjectConfirmation></saml:Subject></saml:AuthenticationStatement><Signature
    xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></CanonicalizationMethod><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></SignatureMethod><Reference
    URI="#SamlSecurityToken-4e51bf2a-2849-4779-a595-a5040c22ff1b"><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"></Transform><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></Transform></Transforms><DigestMethod
    Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"></DigestMethod><DigestValue>otvulmCO6kY0HQdwfqQXUZT/pdmKSdVZJTU0f/MS0N8=</DigestValue></Reference></SignedInfo><SignatureValue>WUGQOtUzu6RtuSKdHHCQZWxiOFVf8HT181U6tS8IVifyyAzA046lm0SBKbFpLzwMEAXsf3ZmkHQkzK/AfS6WJ92WkAz3LLEsqSqGBGQoxe5WPXMlfA9J4+1lnT6Zsfq7fb9aLqZch2oSga3yj0CeQgsbcmppQhQO86zJ468YskVyAk4Y/oIOyThKg/+Ce8V4tFw575+zYatuSzKvUtgHq+DKJRO7T2M8r0aoCx65ZgfCxJpA+bqalDz3BesqOzMKfWTn33fwArVh8JMF1ohNkliwOegTeEEq4aH2Sg04N7ZfLrhoFlWeXuZWn1AzWppyl+FBfwlbLOVbQgP6/3NdMQ==</SignatureValue><KeyInfo><o:SecurityTokenReference
    xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1">/YVCIdf+YFyKopRflv61uWov2vs=</o:KeyIdentifier></o:SecurityTokenReference></KeyInfo></Signature></saml:Assertion>
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      Pragma: no-cache
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 1646
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected].  Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="Internal"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess
    fqdn="AccessEdge.mydomain.com" port="5061" /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker"
    href="https://lync01.mydomain.com/Reach/sip.svc" /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root"
    /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc" /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications"
    /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [INFO] Server discovery has completed for https://lyncdiscoverinternal.mydomain.com/.
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover full response for URL https://lyncdiscoverinternal.mydomain.com/ is <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    AccessLocation="Internal"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess fqdn="AccessEdge.mydomain.com" port="5061"
    /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker" href="https://lync01.mydomain.com/Reach/sip.svc"
    /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc"
    /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications" /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications"
    /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] SendRequest failed for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [INFO] Automatic discovery results for https://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [INFO] Access Location                          : Internal
    [6/10/2014 7:30:18 AM] [INFO] SIP Server Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Server External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] Internal Auth broker service             : https://lync01.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] External Auth broker service             : https://lync.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal Auto discover service           : https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] External Auto discover service           : https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] Internal MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] External MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal UCWA service                    : https://lync01.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] External UCWA service                    : https://lync.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] Internal Webscheduler service            : https://lync01.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] External Webscheduler service            : https://lync.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] Total server discovery time: 0.1 seconds
    [6/10/2014 7:30:18 AM] [SUMMARY_SUCCESS] Server discovery succeeded for secure (HTTPS) internal channel against URL https://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting automatic discovery for unsecure (HTTP) internal channel
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to http://lyncdiscoverinternal.mydomain.com/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      Pragma: no-cache
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 670
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL http://lyncdiscoverinternal.mydomain.com/[email protected].  Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="Internal"><Root><Link token="Domain" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/domain" /><Link token="User" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user"
    /><Link token="OAuth" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/oauth/user" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /></Root></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover URL http://lyncdiscoverinternal.mydomain.com/[email protected] redirected to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 401, ReasonPhrase: 'Unauthorized', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      X-MS-WebTicketURL: https://lync01.mydomain.com/WebTicket/WebTicketService.svc
      X-MS-WebTicketSupported: cwt,saml
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-Powered-By: ASP.NET
      Content-Length: 1293
      Content-Type: text/html
    [6/10/2014 7:30:18 AM] [DEBUG] Authorization required for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Obtaining WebTicket from https://lync01.mydomain.com/WebTicket/WebTicketService.svc
    [6/10/2014 7:30:18 AM] [DEBUG] On-premises WebTicket server: https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] AcquireTicketAsync succeeded for https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] WebTicket: <saml:Assertion MajorVersion="1" MinorVersion="1" AssertionID="SamlSecurityToken-1b6331e1-4be5-4749-869a-21feb4b7198a" Issuer="https://lync01.mydomain.com/63b16135-930c-5e0b-998c-7ed6bc68b6f8" IssueInstant="2014-06-10T11:30:18.238Z"
    xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"><saml:Conditions NotBefore="2014-06-10T11:30:18.238Z" NotOnOrAfter="2014-06-10T19:20:24.238Z"><saml:AudienceRestrictionCondition><saml:Audience>https://lync01.mydomain.com/</saml:Audience></saml:AudienceRestrictionCondition></saml:Conditions><saml:AuthenticationStatement
    AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:unspecified" AuthenticationInstant="2014-06-10T11:30:18.238Z"><saml:Subject><saml:NameIdentifier Format="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/uri">sip:[email protected]</saml:NameIdentifier><saml:SubjectConfirmation><saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:holder-of-key</saml:ConfirmationMethod><KeyInfo
    xmlns="http://www.w3.org/2000/09/xmldsig#"><e:EncryptedKey xmlns:e="http://www.w3.org/2001/04/xmlenc#"><e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#kw-aes256"></e:EncryptionMethod><KeyInfo><KeyName>63b16135-930c-5e0b-998c-7ed6bc68b6f8:8d152b04ce7ddbf</KeyName></KeyInfo><e:CipherData><e:CipherValue>NrQOUA0JAXMmR/4ACrZ8LyVN79jUZbR6Fz+sGlbAdWXgQF/u24DLlw==</e:CipherValue></e:CipherData></e:EncryptedKey></KeyInfo></saml:SubjectConfirmation></saml:Subject></saml:AuthenticationStatement><Signature
    xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></CanonicalizationMethod><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></SignatureMethod><Reference
    URI="#SamlSecurityToken-1b6331e1-4be5-4749-869a-21feb4b7198a"><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"></Transform><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></Transform></Transforms><DigestMethod
    Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"></DigestMethod><DigestValue>WnZZN/Vbfrget92urYd1+HmyXX/vYQ6CjHN4lLEXxK0=</DigestValue></Reference></SignedInfo><SignatureValue>BiFjeIuG7TW/DqIdklMNdaqRJLgbenphBcb51HGGH4WCdThgj2Oizkvfa6NRAwsE74qmyVLcfJIO2TK+if1yelHzUEde8ZvLwcruIFYWecK3OXDSDiGpYa3WdPwNUZrSRySSiCyb+fyYgz8BvZq3JjQRulOXnFhz4X3wXzoS6xMovmmVsOrdVTMjvT7l7ydEo1ucnEl5zjEnKih7WjCoElYENwEeG2HGf4Xqi43piaWXa9k7GY9k1idyrfJ7too+u7O7fhnhJ9OR0GR1KydbAPdSi5hmpZcziLn6xKCVW64w2bGCsT4N2vr+f5AhknSmjDa+9Wnyiar2uuLk+7eLmQ==</SignatureValue><KeyInfo><o:SecurityTokenReference
    xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1">/YVCIdf+YFyKopRflv61uWov2vs=</o:KeyIdentifier></o:SecurityTokenReference></KeyInfo></Signature></saml:Assertion>
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      Pragma: no-cache
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 1646
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected].  Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="Internal"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess
    fqdn="AccessEdge.mydomain.com" port="5061" /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker"
    href="https://lync01.mydomain.com/Reach/sip.svc" /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root"
    /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc" /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications"
    /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [INFO] Server discovery has completed for http://lyncdiscoverinternal.mydomain.com/.
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover full response for URL http://lyncdiscoverinternal.mydomain.com/ is <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    AccessLocation="Internal"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess fqdn="AccessEdge.mydomain.com" port="5061"
    /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker" href="https://lync01.mydomain.com/Reach/sip.svc"
    /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc"
    /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications" /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications"
    /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] SendRequest failed for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [INFO] Automatic discovery results for http://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [INFO] Access Location                          : Internal
    [6/10/2014 7:30:18 AM] [INFO] SIP Server Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Server External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] Internal Auth broker service             : https://lync01.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] External Auth broker service             : https://lync.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal Auto discover service           : https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] External Auto discover service           : https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] Internal MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] External MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal UCWA service                    : https://lync01.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] External UCWA service                    : https://lync.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] Internal Webscheduler service            : https://lync01.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] External Webscheduler service            : https://lync.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] Total server discovery time: 0.1 seconds
    [6/10/2014 7:30:18 AM] [SUMMARY_SUCCESS] Server discovery succeeded for unsecure (HTTP) internal channel against URL http://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting automatic discovery for secure (HTTPS) external channel
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:30:39 AM] [DEBUG] Exception encountered while sending an HTTP request to https://lyncdiscover.mydomain.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException:
    An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period
    of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    [6/10/2014 7:30:39 AM] [ERROR] An error occurred while sending the request.
    Unable to connect to the remote server
    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:443
    [6/10/2014 7:30:39 AM] [INFO] For troubleshooting, try using a browser to open the server discovery URL https://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:30:39 AM] [DEBUG] System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed
    because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
    [6/10/2014 7:30:39 AM] [SUMMARY_ERROR] Server discovery failed for secured external channel against https://lyncdiscover.mydomain.com/
    [6/10/2014 7:30:39 AM] [SUBHEADING] Starting automatic discovery for unsecure (HTTP) external channel
    [6/10/2014 7:30:39 AM] [DEBUG] Sending HTTP request to http://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:31:00 AM] [DEBUG] Exception encountered while sending an HTTP request to http://lyncdiscover.mydomain.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException:
    An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period
    of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:80
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    [6/10/2014 7:31:00 AM] [ERROR] An error occurred while sending the request.
    Unable to connect to the remote server
    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:80
    [6/10/2014 7:31:00 AM] [INFO] For troubleshooting, try using a browser to open the server discovery URL http://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:31:00 AM] [DEBUG] System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed
    because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:80
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
    [6/10/2014 7:31:00 AM] [SUMMARY_ERROR] Server discovery failed for unsecured external channel against http://lyncdiscover.mydomain.com/
    [6/10/2014 7:31:00 AM] [DEBUG] None, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST, MobilityMCXInternalLMXCheckGET,
    MobilityMCXInternalLMXCheckPOST, MobilityMCXExternalLMXCheckGET, MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
    [6/10/2014 7:31:00 AM] [SUMMARY]
    [6/10/2014 7:31:00 AM] [SUMMARY_ERROR] Automatic discovery meant for external network access failed. Please verify the server requirements at http://go.microsoft.com/fwlink/?LinkId=278998 .
    [6/10/2014 7:31:00 AM] [SUMMARY] Automatic discovery meant for internal network access succeeded from an external network which could be a potential security concern.
    [6/10/2014 7:31:00 AM] [MAINHEADING] Starting the requirement tests for Lync Mobile 2010 App
    [6/10/2014 7:31:00 AM] [INFO] Please wait; this test may take several minutes to complete...
    [6/10/2014 7:31:00 AM] [INFO] Testing the app requirements using the following discovery response:
    [6/10/2014 7:31:00 AM] [INFO] Access Location                          : Internal
    [6/10/2014 7:31:00 AM] [INFO] SIP Server Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] SIP Server External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] SIP Client Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] SIP Client External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] Internal Auth broker service             : https://lync01.mydomain.com/Reach/sip.svc
    [6/10/2014 7:31:00 AM] [INFO] External Auth broker service             : https://lync.mydomain.com/Reach/sip.svc
    [6/10/2014 7:31:00 AM] [INFO] Internal Auto discover service           : https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:31:00 AM] [INFO] External Auto discover service           : https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:31:00 AM] [INFO] Internal MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] External MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] Internal UCWA service                    : https://lync01.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:31:00 AM] [INFO] External UCWA service                    : https://lync.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:31:00 AM] [INFO] Internal Webscheduler service            : https://lync01.mydomain.com/Scheduler
    [6/10/2014 7:31:00 AM] [INFO] External Webscheduler service            : https://lync.mydomain.com/Scheduler
    [6/10/2014 7:31:00 AM] [SUBHEADING] Starting tests for Mobility (MCX) service
    [6/10/2014 7:31:00 AM] [INFO] Verifying internal Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] Successfully obtained the WS-Metadata Exchange (MEX) document using GET. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [INFO] Verifying external Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] Successfully obtained the WS-Metadata Exchange (MEX) document using GET. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [INFO] Verifying internal Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [WARNING] Failed to obtain the WS-Metadata Exchange (MEX) document using POST for https://lync01.mydomain.com/Mcx/McxService.svc/mex. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [INFO] Verifying external Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [WARNING] Failed to obtain the WS-Metadata Exchange (MEX) document using POST for https://lync01.mydomain.com/Mcx/McxService.svc/mex. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [SUMMARY] Completed tests for Mobility (MCX) service
    [6/10/2014 7:31:00 AM] [DEBUG] None, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST, MobilityMCXInternalLMXCheckPOST,
    MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
    [6/10/2014 7:31:00 AM] [SUMMARY]
    [6/10/2014 7:31:00 AM] [SUMMARY_SUCCESS]
    Your deployment meets the minimum requirements for Lync Mobile 2010 App.

  • Lync 2013 Group Chat not working

    We have a 2010 server and when I move people over to 2013 group chat does not work. I can select the people I want to talk to, but they don't see any of the conversations. When I move the back to the 2010 it works again.
    We are running office 2013, lync 2013 and exchange 2010. 
    Any suggestions?

    Have you installed Persistent Chat in Lync 2013? You'll need to migrate the group chat data to the Persistent Chat pool and setup a Persistent Chat Endpoint for the legacy 2010 group chat clients, see: http://technet.microsoft.com/en-us/library/jj204901.aspx
    Please mark posts as answers/helpful if it answers your question.
    Blog
    Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

  • Lync 2013 domain discovery not working, but Lync 2010 works flawlessly

    We are using Lync 2013 and Lync 2010 in our company. Upon installation Lync 2010 can connect absolutely fine with for example [email protected], but when we use Lync 2013 we receive a DNS error saying it cannot resolve the domain when using the same
    method. I have to manually enter the internal and external servers on each deployment of Lync 2013 to sipdir.online.lync.com:443 in order for successfully login to Lync 2013. We are upgrading all users to Lync 2013 and I want to avoid having to do this
    on every deployment. This has always been an issue and not something that recently became an issue.
    I have double checked my CNAME and SRV from my host provider and everything is as it should be. Contacting MS support they made me change my preferred DNS to 8.8.8.8 on the network adapter for the PC, but that breaks everything you connect to internally and
    is not a solution to this issue.
    Any ideas?

    Hi,
    The forum you posted is for Lync Server On Premise only. The issue is more related to Lync online, you can also post a question on Office365 forum for assistance. Thank you for your understanding.
    http://community.office365.com/en-us/f/166.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Lync 2013 Desktop SHaring Not working from Internet

    Hi,
    I am facing one issue, my Desktop Sharing is not working for Internet Clients, error message comes is "we could not connect to the presentation because of network issues" Internally it is working fine even I from Edge Server.
    I am using single Public IP Configuration on Edge Server with Port 5061,444,443,3478.
    Any suggestions, on I can check are welcome.
    Best Regards, Ranjit Singh

    Hello Ranjit, 
    Application Sharing/Desktop Sharing happens  through SRTP  through the A/V edge Server hence checking the Port Range is very important
    Following Port reachability to be checked first
    Public --> Edge server:
    TCP/443
    UDP/3478
    TCP/50,000-59,999 (Outbound only)
    From the Front End pool to the internal Edge:
    TCP/5062
    TCP/443
    UDP/3478
    From the internal Edge to the Front End Pool:
    TCP/5065
    TCP/49152-65335 (Inbound/Outbound)
    More Detailed info can be seen here
    http://blogs.technet.com/b/nexthop/archive/2012/11/05/lyncmd-troubleshooting-lync-server-2010-application-sharing-internal-and-remote-scenarios.aspx

  • Microsoft Word 2013 Dictionary App not working with "compatible" Browser

    My Microsoft Word English Dictionary App is not working. It keeps giving me the excuse that my browser is not compatible but I checked and the minimum is Firefox 12. I have Firefox 33. Any ideas on how to fix this?

    Hi rosedoc12,
    I have done some research and I have found a document that will show you how to disable or lock the fn key.
    http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&​lc=en&docname=c02035108
    Thank you,
    Please click “Accept as Solution ” if you feel my post solved your issue.
    Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
    Thank you,
    BHK6
    I work on behalf of HP

  • New i6 is not working with Acura - have tried a reset and still not working. This is urgent as I must be able to connect via bluetooth in my vehicle

    My i6 is not connecting to handsfree in vehicle - have reset a few times-still not working as handsfree. Can dial but then goes to device. Also continues to disconnect.
    Verizon carrier
    Acura MDX 2014
    i6
    ios 8
    Please help ASAP!

    You have to go to autherized iPhone agent.

  • INTERSECT funcation in MDX not working with if we INTERSECT Parent SET and lower leval Set

    Hi All,
    INTERSECT funcation is not working if i filter Parent attribute and simple attribute
    ex.
    SET a as
    INTERSECT(
    [DimCustomerBuyer].[ParentProvince].[ParentProvince],[DimCustomerBuyer].[Province].[Province])
    Query (99, 1) Members, tuples or sets must use the same hierarchies in the INTERSECT function.
    is there any  work around
    parent Provence we use for Parent child attribute but Province is normal attribute
    Regards,
    Manish

    Hi manishcal16PPS,
    According to your description, you want to use the INTERSECT() function for different hierarchy members. Right?
    In MDX, when using INTERSECT() function, the two sets must have same dimensionality. Which means the two set of members must be under same hierarchy, otherwise they will be not comparable to SSAS so that it can't return the intersect part
    of members. This is the limitation of INTERSECT() function.
    Reference:
    Intersect (MDX)
    Intersect(MDX)
    Regards,
    Simon Hou
    TechNet Community Support

Maybe you are looking for

  • Ipod classic not shown in itunes

    I have recently been having A LOT of problems with my 3 month old 80gb ipod classic. i used to get the (-48) error and then i started to get the (-69) error. i tried some suggestions and nothing seemed to be working and then earlier this week i got t

  • Counting Rows of a Specific Type

    I have the following dataset and I was wondering if someone could help me out with the following problem: <data> <row type="A">item1</row> <row type="B">item1</row> <row type="B">item2</row> <row type="C">item1</row> <row type="C">item2</row> <row ty

  • How to enhance 0HR_PT_2 DataSource.

    I need to add a Field from table PA2001 to 0HR_PT_2 datasource Field is KALTG ( Calendar Days ) this field is not available in the DS. I have enhanced the Structure I add the field like ZZKALTG. I need to write abap code to populate the data from PA2

  • Are JPEG 3504x2336 pixel pictures too high resolution for the photo books?

    Hi, I am done creating my photo book and I am ready to order, but I'd like to know if my pictures are too high resolution. They are professional wedding pictures so they are 7.4 mb each JPEG 3504x2336 pixel pictures. (Last time, I printed through MyP

  • Error opening file on iCloud

    This error happens when I try to open a document on icloud (with ML); the document is created on mac and moved to icloud. If I open with my iPad it works fine... Also with a different mac all works as expected... If I move back yo my desktop I can op