Lync 2013 - re-connecting is un-muting microphone, is that a bug or a feature?

Every time Lync 2013 re-connects (very often sadly) the microphone is un-muted.
Is that a bug or a feature?
I'm using a Plantronics Voyager UC headset (Lync certified), doesn't know if it happens with others too.
Please advise if there's a solution, I have to disconnect from Lync every time I'm in a conf call using another software like Cisco Webex.
Quite annoying and very embarassing sometimes...
Thanks

Hi,
When Lync change the status of Mute/Un-Mute, it change the Audio value with the following path: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio
Please check if Cisco Webex also use the same parameter for Mute\Un-Mute. If the two use the same parameter, it can cause the issue.
Also, if the re-connection issue only happen to you, please try to update Lync to the latest version and then test again.
If the re-connection issue happen for multiple users, please check the Lync Server performance and network situation as well.
Best Regards,
Eaosn Huang
Eason Huang
TechNet Community Support

Similar Messages

Lync 2013 client connectivity to Lync Edge Pool

Hi all,
I have a question regarding Lync 2013 topology deployment
I have read somewhere that
The external interfaces of the Edge Server must not be routable by either clients or servers on the internal corporate network. The internal interface of the Edge Server must not be routable from the Internet. These routing principles must be enforced by deploying
firewalls between the Edge Servers (an internal and an external firewall) or by enforcing strict routing at the network layer.
Is the statement true? If it is, then there is no way for the internal client to talk directly to Edge server: its internal network interface doesn't have default route, so this interface can't talk to any client/server that is located on different subnet.
(unless I have to manually add-route in command line for all the subnets in the internal network, which is not preferable)
Any advise is greatly appreciated. Thanks

The mentioned statement is true. You need to manually add static routes in to the Edge server. Only the external interface must have a Gateway configured.
http://thamaraw.com

Lync 2013 Client Not Display Numbers in Contact Card

Hi
I have a problem where Lync 2013 client connecting to Lync 2010 backend appears not download the contact list completely. Lync 2010 clients are all operating normally. On Lync 2010 client, you can view all contact details including Enterprise Voice
numbers and cell numbers for all users. However on Lync 2013 clients, Lync contact details for some users do not populate completely. In most cases, Enterprise numbers/Work Numbers/Mobile Numbers are missing. If the contact is pinned then the details
are retrieved.
In cases where Work/Voice/Cell numbers are not displayed, affected users is limited to making lync to lync calls only. The user can still dial the number and get through without any issues.
I have deleted and contacts cache on Lync 2013 but this has not helped.
Regards

Hi,
How about check the contact of “Outlook Test” user from the Lync 2010 client?
According to the second screenshot, since it’s an external account, the information will be limited.
Thanks,
Simon Wu
TechNet Community Support

Cisco VCS/Codian MCU and Lync 2013 integration

Hi,
I would like to know if Lync 2013 is supported to work with:
- Cisco Tandberg VCS version x6.1
- Cisco Codian 4.1 (comp. 6.16)
Is it necessary to update both devices to be supported/homologated/qualified?
Thanks

Hi, Kent ... From what I'm seeing so far the challenges of integrating Cisco/Tandberg equipment and Lync 2013 are the same as what you may have already encountered with Lync 2010. Since the Cisco endpoints and MCU cannot register directly to Lync 2010
or 2013, you will need to leverage the VCS systems as your SIP gateway between them and Lync clients. In Lync 2010 there were limitations as to the interoperability of the H.263/264 codec used by Cisco gear and the RTV codec that Lync was restricted
to, and we often experienced frozen video feeds from Lync clients or an inability to connect to individual Cisco endpoints or conferences hosted by the Codian MCU. Even though Lync 2013 will use H.264 as a codec for the video stream, I anticipate there
will still be challenges interconnecting through the VCS as well as providing content between Lync and Cisco endpoints. However, I expect an increase in the video quality since Lync 2013 supports higher resolutions and also uses a non-proprietary codec.
I expect content to still be unreliable for the Lync participant, even when using a Codian MCU.
You will still need to setup your VCS with a separate Neighbor zone for the Lync 2013 server just as you did for Lync 2010. I wouldn't hold my breath for Cisco to update the VCS software to accomodate the specific needs of Lync 2013, but at least the
VCS will get the correct video codec and connect your call. I don't know about you but I had to put my Cisco units and MCU into a separate SIP domain from the Lync pool, and then create a static route for the Cisco SIP domain on the Lync 2010 front-end
server. I expect to do the same in Lync 2013.
Ideally, Microsoft and Cisco would agree that SIP is SIP, and whether an endpoint registers with VCS, UCM or Lync shouldn't be relevant. Alas, it'll be a long, long time before that is true, certainly not as long as Microsoft and Polycom have
such a tight bond. I plan on implementing Lync 2013 in the next few months and will gladly post any progress here. At this point my plan is to simply mirror the static route and configuration I have with Lync 2010. My VCS and Codian units
are running software versions just a little ahead of yours and work fine.
Good luck!

OCS Migration to Lync 2013 Delegate which Director that authenticates

Hello - I am in the middle of a migration from OCS 07 to Lync 2013. Everything is working pretty well. I have a new Lync Server with some users migrated over to it already and communication is fine between the Lync Desktop Clients and the OCS Desktop Clients.
We now want to use the Mobile Lync Client so I have installed Lync 2013 Client on my iPhone 5S. I was able to install the root cert on the phone however, when I try to sign in, I am getting the following error:
"We can't sign you in because your organization doesn't support this version of Lync. Please install Lync 2010 from your mobile store."
I am running Lync 2013 Standard Edition and I am running Lync 2013 Client for iOS. I can only assume that because the OCS director is still running it is handling authentication and its not compatible with Lync 2013. Is this a correct assumption?
That being said, and if that's indeed the issue, is there a way to delegate the Lync 2013 Director to take over authentication?
Thank you!
Russ, MCSE

Hi there,
Lync 2013 Mobile clients relies on UCWA services to connect to Lync server 2013 services, also Lync mobile autodiscovery depends on Lync web services publishing. Therefore you should make sure that lyncdiscover.sipdomain and lyncdiscoverinternal.sipdomain
points to Lync server 2013 web services and not OCS 2007.
specifically Lyncdiscover.sipdomain should point to the public IP address on which the Lync External WebServices are published.
so it is quite sure that if the above requirements are not met and especially the DNS configuration for Lyncdiscover and lyncdiscoverinternal mobile clients will not be able to connect.
Regards,
Charbel Hanna
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Lync 2013 Front End SIP/2.0 500 Compression algorithm refused

I've deployed a brand new Lync 2013 environment hosted on Windows Server 2012 R2 that is currently in co-existence mode with my Lync 2010 environment.
I have SCOM 2012 monitoring the environment and it recently started reporting that one or more of my front end servers
was in a critical state. Diving into it revealed the following perf counter threshold was being tripped:
Time Sampled: 3/26/2014 2:33:30 PM
Object Name: LS:SIP - Responses
Counter Name: SIP - Local 500 Responses
Instance Name:
First Value: 14287
Last Value: 14340
Delta Value: 53
Using OCSLOGGER.exe on the front end to capture logs, i trapped the following:
TL_INFO(TF_PROTOCOL) [11]9138.1C58::03/26/2014-19:12:39.098.0022c780 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[120713120] $$begin_record
Trace-Correlation-Id: 120713120
Instance-Id: 7D80EB
Direction: outgoing;source="local"
Peer: poolA.contoso.com:63820
Message-Type: response
Start-Line: SIP/2.0 500 Compression algorithm refused
FROM: <sip:poolA.contoso.com>;ms-fe=FEserver1.contoso.com
To: <sip:poolA.contoso.com>;tag=F8B88CAB38613EB380773027C56D94AF
CALL-ID: 986f9f568c794ce39d33d7158376157b
CSEQ: 1 NEGOTIATE
Via: SIP/2.0/TLS 10.154.228.225:63820;ms-received-port=63820;ms-received-cid=C3D7C00
Content-Length: 0
ms-diagnostics: 2;reason="See response code and reason phrase";HRESULT="0xC3E93C0F(SIP_E_REACHED_CONFIGURED_LIMIT)";source="FEserver1.contoso.com"
Server: RTC/5.0
$$end_record
The only recent change made to the front end servers was making the registry change outlined in this article:
http://support.microsoft.com/kb/2901554/en-us so i'm wondering if that has something to do with it.

The MSFT support person said to re-apply CU5 to the Director servers and reboot. Since this is impactful to the environment and I would have to do reboots anyway, I opted to go the route of installing the more recent update so....
Last weekend I updated my Lync environment with what I think is considered CU6, the September 2014 updates for Lync 2013 Server (https://support.microsoft.com/kb/2809243) and still no luck. The front
end servers are fine; no excess SIP 500 errors occurring there but within 30 minutes of removing the SCOM override on the Director servers the alerts started firing again.
I reinstated the override in SCOM for the Directors and had my case with Premier support un-archived. The MSFT support person said if the alerts didn't go away she was going to have to engage the Lync product group for help. We'll see where it
goes from here.
JKuta

Lync 2013 client doesn't read proxy.pac file Lync exclusions

Hi all,
I have a very annoying issue where by the Lync 2013 client ignores the proxy.pac file exclusions set below:
(host == "lync.test.domain") || (host == "lyncdiscoverinternal.test.domain") ||
(host == "lyncwacdca.test.domain") ||
(host == "lyncwacdcb.test.domain") ||
(host == "lyncwebintdca.test.domain") ||
(host == "lyncwebintdcb.test.domain")
IE is set to use automatic configuration script of
http://proxy.test.domain:8083/proxy.pac This file can be reached through and IE browser, downloaded and it's syntax read.
If I set my proxy server and exclusions manually within IE9 then they are adhered to. That is Lync 2013 is able to read.
My thinking: that some application may be iterferring with Lync 2013 getting to
http://proxy.test.domain:8083/proxy.pac or reading in the exclusions set within the file.
If I enter https://lync.test.domain into the browser URL search field I can see that it is being sent straight out to the proxy as opposed to bypassing it.
Does anyone have an example of their proxy.pac exclusion set for Lync 2013 just in case my syntax is not looking the best.
Cheers

Update to this issue - solution was to move the proxy exclusions to the top of the proxy.pac
Outcome resulted in Windows WinHTTP processing the the Lync proxy exclusions prior to the Lync.exe firing during logon. I don't believe you would see this in a typical infrastructure. Since initially looking into this issue I have been
able to show through packet traces, large periods of latency in delivery of desktop profile items due to backend profile storage issues.
In eddition this moving the exclusions to the top of the pac file I made use of substrings. I don't believe the use of substrings is any better or worst, but just easier for others to understand what the exclusion allows specifically.
Example of pac exclusion now:
if (url.substring(0,39) == "http://lyncdiscoverinternal.testdomain.") { return "DIRECT"; } //matches 31 characters including last . or period
I entered similar entries for all required exclusions. The result was Lync signing in within 6 seconds as opposed to the 40 second (through the user of legacy SRV records).

Lync 2013: SQL instance - Shared or Not Shared !?

I'll keep this straight to the point... I'm implementing Lync 2013 at my company and we stumbled on one SQL Cluster situation that's causing some questions on the DBA team.
So the situation is....
Background:
We currently have a two node SQL 2008 R2 (SP2) Cluster with two instances in it that are shared for other applications.
Question:
Is it recommended by Microsoft (or any Lync Expert at all) to use one of these instances for Lync 2013 databases, or should it be a separated instance to host Lync 2013 Databases?
Note: If to be created the new instance, that instance will be living in the same cluster.
Thank you all in advance for comments on this.

Thanks to both for the replies. It does help me thinking about the subject.
I've meanwhile opened an advisory case with MS to check what they say about it. (I'm posting the results afterwards of course to share their advice)
I agree with both of you, and in fact I don't really like the idea of having a shared instance for Lync 2013 with other products (specially one of them that's in there that is Sharepoint 2013). I'm quite curious on knowing how will the instance behave once
Sharepoint 2013 decides to "eat up" all the resources...
I think that having the separated instance adds at least 2 very good (and important values) that is:
1 - Security (at the instance level.. no unwanted sysadmin's - we have persistent chat by some God forsaken reason... though I don't like the idea that a DBA with the right knowledge to read our C*O's chat's going around...)
2 - Resource assignment control (better memory control, possibility of "shifting" the instance to another place if necessary + if someone "brings down" the shared instance for any reason, lync can continue to function)
The IO concern regarding lots of SQLServer.exe running around, it's also a valid concern in my opinion, though at IO level is basically the same story because what matters is the DB file read-write operations that are ongoing and that will consume the same
resources either you're in a dedicated instance or separated one...
Still our DBA brings up the fact that we need to use a shared instance for everything and he wants me to put Lync all together with the other DB's (Sharepoint 2013 included...).
What are your thoughts about this?
Thanks once again for your time and comments.

Mixed environment migration (OCS\Lync 2010 to Lync 2013) retaining BES Integration

Hi All,
I have an existing OCS 2007R2 and Lync 2010 environment which contains BES Collaboration for Enterprise IM on Blackberry devices. I want to migrate this environment to Lync 2013 whilst retaining the BES integration. Understanding that tri-existence is not supported
I've been going through the process of decommissioning all of my legacy OCS servers, which I have now completed, in readiness for starting the Lync 2013 deployment and prepping AD.
Here's my issue - The BES collaboration service was integrating with an old OCS CWA server. I removed the CWA server and migrated the Collaboration service to a new server so that I could configure it to directly communicate directly with the Lync 2010 pool,
however I still needed to install OCS components on the new server in order to achieve that integration. Now I've run the final step of Merging the OCS 2007R2 Topology with the Lync 2010 topology in preparation for deleting the BackCompatSite, the old OCS
servers have gone, but the new Collaboration server has now appeared as a trusted application server within the BackCompatSite. I've done an LDIFDE export of the RTC Service container and have had a look through the contents. I can see that the new BES Collaboration
server is there and that it has an msRTCSIP-TrustedServerVersion value of 4, whereas all the Lync 2010 values are 5, which I'm guessing is what the Lync Topology is using to establish that the BackCompatSite needs to be populated with that Trusted Server entry.
So my question is this - What do I need to do in order to successfully remove the BackCompatSite entry and migrate my environment to Lync 2013 whilst retaining integration with BES and keeping the Enterprise IM service service running on Blackberry devices?
Here's some options that I've thought about - Using ADSIEdit to remove the Trusted Server Application for the new BES Collaboration server so I can merge the Topology and delete the BackCompatSite, although will this break the Enterprise IM service? Temporarily
changing the value of the msRTCSIP-TrustedServerVersion for the Collaboration server from 4 to 5, merging the Topology, deleting the BackCompatSite and then changing the msRTCSIP-TrustedServerVersion back to 4 afterwards? Over a weekend\out of hours, removing
the BES Collaboration server and service altogether, going through the Topology merge\BackCompatSite deletion and then reinstalling the Collaboration service?
Has anyone else gone through this process, or got any advice\experience to pass on before I start working through my list of options?

I've asked this question several times:
Does the 2007 R2 CWA server count as tri-coexistence?
I've asked that both in MCM rotations and directly of people on the PG and the answer is always something along the lines of "nope, it's a trusted app server and not a pool". When I've run into this issue in other deployments, we simply left the backcompatsite
in the deployment into production.
I've never found the above as a publically approved statement just something I've asked previously and been told is OK to do. This is one of those situations that will work but was most likely not tested.
Thanks,
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Save locally conversation history in Lync 2013

Hi,
is it posibble to save Lync 2013 client conversation history, locally on computer? That is when client dont have Outlook, because he is using webmail or some other mail client.
Thank you,
Ivan.

If you didn’t install Outlook client, you can also see history conversation tab in Lync main Window.
You can copy the message to your email. You need to do it manually.
Lisa Zheng
TechNet Community Support

Move Users from OCS 2007 R2 to New Lync 2013

I am trying to move users from OCS to Lync 2013 from within the Lync 2013 Control Panel and am getting an error that states "Cannot find Registrar pool. Verify that "FQDN of old pool" is a valid registrar pool.

Give this Lync powershell command a go:
Move-CsLegacyUser <user> -Target <Lync2013 Pool Name>
Move-CsLegacyUser -Identity "Pilar Ackerman" -Target "atl-cs-001.litwareinc.com"
Have you reviewed the OCS to 2013 migration documents?
http://technet.microsoft.com/en-us/library/jj205375.aspx
Did you add the OCS pool to the 2013 topology?
Have you visited Lync News lately? All of the latest Lync news, articles, and tips collected in one giant aggregator. http://lyncne.ws

Lync 2010 client connecting to 2013 persistent chat server

Since we never had Group Chat in our 2010 environment, I have no idea how it works and now that we have 2013 Persistent Chat, I am struggling with getting the Lync 2010 connected. The 2013 client works just fine as it is integrated into the client. I found
out Lync 2010 needs a separate Chat client to run along side the IM client.
I installed this client but from there I have no idea how to connect it to the 2013 Chat server. I created the endpoint on the Lync 2013 server according to the article
http://technet.microsoft.com/en-us/library/jj204901.aspx but something else needs to be done. I just don't know what. Not even sure where to start looking. Many of our Lync clients have
to use 2010 because the OS is XP so I need to find out how to get these users to work with Persistent Chat.
I am not sure what the point is of creating the End point according to the article. I am sure its necessary but not sure how it fits into the clients using it to connect. What does the article mean when it says "Next, configure Persistent Chat clients
to use that SIP address as their contact object". Do you need Group Chat functioning in 2010 for this to even work?
The problem is we never had Group Chat with 2010 so I am sure there are some settings missing like DNS records etc...

If you have users running legacy clients (such as Microsoft Lync 2010 these users might find the default Persistent Chat URIs difficult to work with and difficult to use when pointing their legacy client towards the pool. Because of this,
administrators need to use the New-CsPersistentChatEndpoint cmdlet to create an additional contact object for the pool, a contact object that provides a friendlier, easier-to-use URI.
Lisa Zheng
TechNet Community Support

Lync 2011 for MAC not connecting externally to On-Premise Lync 2013

Hello,
Hopefully someone has some idea on this or a better direction for me to follow. So currently I have an issue where Lync 2011 for MAC clients will not connect when external to my On-Premise Lync 2013 servers. Everything to do with my Windows based clients
and even cell phone based client’s works just fine. It is currently only Lync 2011 for MAC which will not correct externally.
I did initially have the logon problem internally as noted by other posts online when using an internal CA certificate with Lync. But with the internal certificate imported onto the MAC when internally connected Lync 2011 will login just fine. Now in my
setup I do have a TMG server that clients are connecting to that forwards the connections onto my Lync servers when connecting externally. When I review live real time logs to see what’s connecting to the external URL for Windows based clients I can see them
connect in on port 443 no problem.
But with the MAC I don’t see any attempt from it to connect to the URL like I see with the Windows clients. Now below is what shows up in the Microsoft-Lync.log generated by the MAC. Now initially looking at the log I thought my problem was the fact when
Lync 2011 tires to connect when external that it was doing so on port 5061 which we don’t have open. So I tired entering external.mydomain.com:443 in for my external server in the setup.
And while rechecking the log after doing so shows like it is now trying to connect on port 443. When reviewing TMG I again see no connection attempt by the MAC to connect to the Lync external url or on port 443. Further research so far into the problem has
come up empty on the subject. And most other cases where people report problems connecting externally they are using some form of online service like Office 365. So at this point I am not even sure if Lync 2011 for MAC is supposed to work externally with On-Premise
Lync 2013 deployments or not. If anyone has an thought’s or idea’s please share them as at this point I am stuck on this issue.
Microsoft Lync 14.0.10 (141024)
MacOS version 10.7.5 (build 11G63)
2015/01/08 08:51:11.807 SIPService::OnEvent(IApplicationLayerEvent &), type: 0, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:12.670 SIPService::OnEvent(NModel::ILogonSessionEvent), hr: 0x0, oldState: 0, newState: 10, direction: 0
2015/01/08 08:51:12.682 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:12.685 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:20.192 Office Communications Server LOGON STARTED: USER = {nsayewich}
2015/01/08 08:51:20.197 SIPService::Logon
2015/01/08 08:51:20.281 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:20.543 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:20.543 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:20.566 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:20.566 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:20.568 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:20.568 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:20.600 SIPService::OnEvent(NModel::ILogonSessionEvent), hr: 0x0, oldState: 10, newState: 20, direction: 0
2015/01/08 08:51:21.535 InternalConnect, NLResolveAddress returned: -3176
2015/01/08 08:51:21.537 IsLocalAddress, 'internal.mydomain.com' is not a local address
2015/01/08 08:51:21.537 FShouldUseProxy, is returning 1
2015/01/08 08:51:21.537 Connecting to internal.mydomain.com (port 0)
2015/01/08 08:51:21.537 InternalConnect, NLCreateConnection returned: -3176,
2015/01/08 08:51:21.537 FUsingHttpsTunnelProxies, returning: 0
2015/01/08 08:51:21.537 Listening thread got exception -3176
2015/01/08 08:51:23.632 InternalConnect, NLResolveAddress returned: 0
2015/01/08 08:51:23.633 IsLocalAddress, 'external.mydomain.com' is not a local address
2015/01/08 08:51:23.633 FShouldUseProxy, is returning 1
2015/01/08 08:51:23.633 Connecting to external.mydomain.com (port 5061)
2015/01/08 08:51:38.004 InternalConnect, NLCreateConnection returned: -3259,
2015/01/08 08:51:38.004 FUsingHttpsTunnelProxies, returning: 0
2015/01/08 08:51:38.004 Listening thread got exception -3259
2015/01/08 08:51:38.005 InternalConnect, NLResolveAddress returned: 0
2015/01/08 08:51:38.006 IsLocalAddress, 'external.mydomain.com' is not a local address
2015/01/08 08:51:38.006 FShouldUseProxy, is returning 1
2015/01/08 08:51:38.006 Connecting to external.mydomain.com (port 5061)
2015/01/08 08:51:53.008 InternalConnect, NLCreateConnection returned: -3259,
2015/01/08 08:51:53.008 FUsingHttpsTunnelProxies, returning: 0
2015/01/08 08:51:53.008 Listening thread got exception -3259
2015/01/08 08:51:55.026 SIPService::OnEvent(NModel::ILogonSessionEvent), hr: 0x80072743, oldState: 20, newState: 10, direction: 1
2015/01/08 08:51:55.026 Login (1) failed with error: (0.-2147014845)
2015/01/08 08:51:55.036 SIPService::OnEvent(IApplicationLayerEvent &), type: 8, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:55.036 SIPService::OnEvent(IApplicationLayerEvent &), type: 2, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:55.036 SIPService::OnEvent(IApplicationLayerEvent &), type: 4, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:55.037 SIPService::OnEvent(IApplicationLayerEvent &), type: 6, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:55.037 SIPService::OnEvent(IApplicationLayerEvent &), type: 4, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:55.038 SIPService::OnEvent(IApplicationLayerEvent &), type: 6, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:55.038 SIPService::OnEvent(IApplicationLayerEvent &), type: 4, HasSignedIn(): 0, HasSignedOut: 0
2015/01/08 08:51:55.040 SIPService::OnEvent(IApplicationLayerEvent &), type: 6, HasSignedIn(): 0, HasSignedOut: 0

Hi Nicholas Sayewich,
I tested in my lab and without any problem.
I also use TMG as Reverse Proxy and without configuring SRV records (My ISP don’t support SRV), after importing the root certificate onto MacBook, I can sign into Lync everywhere(internal
and external).
Please make sure that the certificate is set up to
Always Trust .
http://blogs.technet.com/b/nexthop/archive/2008/03/05/how-to-install-a-trusted-root-ca-certificate-on-osx-leopard-for-use-with-messenger-for-macintosh.aspx
And my log for your reference:
Microsoft Lync 14.0.10 (141024)
MacOS version 10.10.1 (build 14B25)
2015/01/09 22:40:15.802 SIPService::OnEvent(IApplicationLayerEvent &), type: 0, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:16.486 SIPService::OnEvent(NModel::ILogonSessionEvent), hr: 0x0, oldState: 0, newState: 10, direction: 0
2015/01/09 22:40:16.493 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:16.496 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:32.595 Office Communications Server LOGON STARTED: USER = {MyDomain\LyncUser1}
2015/01/09 22:40:32.596 SIPService::Logon
2015/01/09 22:40:32.633 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:32.737 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:32.738 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:32.743 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:32.743 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:32.744 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:32.744 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:32.754 SIPService::OnEvent(NModel::ILogonSessionEvent), hr: 0x0, oldState: 10, newState: 20, direction: 0
2015/01/09 22:40:33.080 InternalConnect, NLResolveAddress returned: 0
2015/01/09 22:40:33.082 IsLocalAddress, 'sipinternal.MyDomain.com' is not a local address
2015/01/09 22:40:33.082 FShouldUseProxy, is returning 1
2015/01/09 22:40:33.082 Connecting to sipinternal.MyDomain.com (port 5061)
2015/01/09 22:40:48.008 InternalConnect, NLCreateConnection returned: -3259,
2015/01/09 22:40:48.008 FUsingHttpsTunnelProxies, returning: 0
2015/01/09 22:40:48.010 Listening thread got exception -3259
2015/01/09 22:40:50.043 InternalConnect, NLResolveAddress returned: 0
2015/01/09 22:40:50.044 IsLocalAddress, 'sip.MyDomain.com' is not a local address
2015/01/09 22:40:50.044 FShouldUseProxy, is returning 1
2015/01/09 22:40:50.044 Connecting to sip.MyDomain.com (port 443)
2015/01/09 22:40:50.896 InternalConnect, NLCreateConnection returned: 0,
2015/01/09 22:40:50.896 InternalConnect, NLCopyConnectionBinding returned: 0,
2015/01/09 22:40:52.980 InternalConnect, NLResolveAddress returned: 0
2015/01/09 22:40:52.981 IsLocalAddress, 'sip.MyDomain.com' is not a local address
2015/01/09 22:40:52.981 FShouldUseProxy, is returning 1
2015/01/09 22:40:52.981 Connecting to sip.MyDomain.com (port 5061)
2015/01/09 22:40:53.291 InternalConnect, NLCreateConnection returned: 0,
2015/01/09 22:40:53.291 InternalConnect, NLCopyConnectionBinding returned: 0,
2015/01/09 22:40:53.522 HRESULT GetLinkSpeed(DWORD, DWORD*, WIN_BOOL*): ip 192.168.100.187, link speed 0
2015/01/09 22:40:53.522 HRESULT GetLinkSpeed(DWORD, DWORD*, WIN_BOOL*): Working around 0 link speed
2015/01/09 22:40:53.526 SIPService::OnEvent(NModel::ILogonSessionEvent), hr: 0x0, oldState: 20, newState: 30, direction: 0
2015/01/09 22:40:53.528 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.529 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.536 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.536 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.536 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.536 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.536 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.536 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.555 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.555 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.583 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.584 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.592 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.592 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.615 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.615 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.622 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.622 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.784 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.784 SIPService::OnEvent(IApplicationLayerEvent &), type: 1, HasSignedIn(): 0, HasSignedOut: 0
2015/01/09 22:40:53.786 SIPService::OnEvent(IApplicationLayerEvent &), type: 3, HasSignedIn(): 1, HasSignedOut: 0
2015/01/09 22:40:53.787 virtual void SIPService::OnIdleHandleLogonSucceeded()
2015/01/09 22:40:53.792 Office Communications Server LOGON ENDED: USER = { MyDomain\LyncUser1}
2015/01/09 22:40:54.151 IsLocalAddress, 'lyncpool01' is not a local address
2015/01/09 22:40:54.151 FShouldUseProxy, is returning 1
2015/01/09 22:40:54.379 IsLocalAddress, 'lyncpool01' is not a local address
2015/01/09 22:40:54.379 FShouldUseProxy, is returning 1
2015/01/09 22:40:55.082 IsLocalAddress, 'lyncpool01' is not a local address
2015/01/09 22:40:55.082 FShouldUseProxy, is returning 1
2015/01/09 22:40:55.440 IsLocalAddress, 'lyncpool01' is not a local address
2015/01/09 22:40:55.440 FShouldUseProxy, is returning 1
2015/01/09 22:40:55.683 IsLocalAddress, 'lyncpool01' is not a local address
2015/01/09 22:40:55.683 FShouldUseProxy, is returning 1
2015/01/09 22:40:57.238 IsLocalAddress, 'lyncpool01' is not a local address
2015/01/09 22:40:57.238 FShouldUseProxy, is returning 1
2015/01/09 22:40:57.239 IsLocalAddress, 'lyncpool01' is not a local address
2015/01/09 22:40:57.239 FShouldUseProxy, is returning 1
2015/01/09 22:40:57.241 IsLocalAddress, 'lyncpool01' is not a local address
2015/01/09 22:40:57.241 IsLocalAddress, 'lyncpool01' is not a local address
2015/01/09 22:40:57.241 IsLocalAddress, 'lyncpool01' is not a local address
2015/01/09 22:40:57.241 FShouldUseProxy, is returning 1
2015/01/09 22:40:57.241 FShouldUseProxy, is returning 1
2015/01/09 22:40:57.241 FShouldUseProxy, is returning 1
Best regards,
Eric

Unable to connect as a formal agent to a Response Group after Migration to Lync 2013

We are in the process of migrating our Lync 2010 servers to Lync 2013. Everything seems to go well, but problems started to appear after we migrated the Lync 2010 response groups to Lync 2013. Now only those groups with informal agents work. All the groups
with formal agent, when they try select their group through the web page, they all get the error:
You are not a member of any group. For assistance, contact your support team"
Did anyone experience such an issue ?
Thanks,
Antonio

We had this problem with our recent migration of c. 350 response groups, many of which had formal agent groups. The cause appears to be that after the migration, the formal agent registration screen sees both the 'old' and the 'new' formal agent groups of
which the current user is a member and resolves these to only one entry on the registration screen (which is understandable). But the entry seems to be connected to the 'old' and not the 'new' agent group. We were able to verify this by checking in the old
and new pool database (rgsdyn) and seeing that even after the migration the formal agents were signing in to the old pool and not the new one. One solution is to delete the members from the old formal agent groups so that future registrations are forced to
take place in the new pool database. However, if you do this, bear in mind that if you have to back out the migration, you have to restore these.
We were also had to abandon one migration attempt because of another problem where the migration tool does not support the migration of agents who are defined indirectly in the agent group through a mail distribution group.
tags: Move-CsRgsConfiguration ; formal agent groups ; lync2013 ;

Lync 2013 Connectivity Problems

We have one computer that will not let anyone sign into Lync 2013. We have re-installed Lync, repaired Lync, tried using the manual configuration with the lync servers, compared registry settings from a machine that does work, compared certificates to
machine that works, and looked at network settings on the computer with no luck. When you attempt to login, you enter your email address which is <[email protected] and then get prompted for a password. Once you enter your password, you just see the
message "Connecting to server and signing in." This will just sit here to many many minutes and not ever do anything. We are using Office 365, Office 2013, and using a hosted exchange environment with dirsync with password sync. Can anyone help with
this issue? It is definitely something local to this computer because the user can login to Lync on other computers. Thanks.

Get sign in automatic configuration and download lync from office 365 portal
Then try again to sign in if still have problem try to use the following
For Problem acquiring a personal certificate that is required to sign in If the user’s sign address has recently changed, they may need to delete cached sign-in data. Ask users to run the automated
Fix it wizard in
Microsoft Knowledge Base article 2698626.
Please remember, if you see a post that helped you please click (Vote As Helpful" and if it answered your question, please click (Mark As Answer).

Lync 2013 - re-connecting is un-muting microphone, is that a bug or a feature?

Similar Messages

Maybe you are looking for