LYNC NOT WORKING

HI MY DOMAIN NAME IS SATWIC.COM
LYNC IS NOT WORKING IN OFFICE 365.GETTING BELOW ERROR
LImited functionality available due to server issue
Need your help to rectify this error.
Waiting for your reply.

Hi ,
As Michael stated, 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
Also you should check the network configurations for Lync Online.
Set
up your network for Lync Online
Best regards,
Eric
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

Microsoft Lync not working thru Anyconnect client

We are trying to establish video connection thru Anyconnect client. When made request from one user to another user on Anyconnect, one user does receive a request, but no connection get established. Any suggestion would be helpful.

Do you have "same-security-traffic permit intra-interface" configured on ASA?
Yers
Also, are you able to ping between the 2 AnyConnect clients when they are both connected?
Yes
Do you have any Windows personal firewall or any other personal firewall that might be blocking inbound connection towards the PC where you connect from?
No
One can initiate a session, but it just doesn't establish.

Call is not working Cisco-CUCM8.6 to Lync

Hi,
I am facing issue with CUCM.
Lync to CUCM call works.
But CUCM to Lync not working.
Logs :-
TL_INFO(TF_PROTOCOL) [1]0868.0F1C::07/12/2014-06:22:03.292.0000002f (S4,SipMessage.DataLoggingHelper:sipmessage.cs(686))[3168828821]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_310339F>], 172.29.55.162:5068<-172.29.58.15:47485
INVITE sip:[email protected]:5068 SIP/2.0
FROM: "Deepak Srivastava" <sip:[email protected]>;tag=35075~3a834c6d-74d2-4f7c-89b1-cae86be13da3-48284953
TO: <sip:[email protected]>
CSEQ: 101 INVITE
CALL-ID: [email protected]
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 172.29.58.15:5066;branch=z9hG4bK10663aa09f0
ALLOW-EVENTS: presence
CONTACT: <sip:[email protected]:5066;transport=tcp>
CONTENT-LENGTH: 1187
DATE: Sat, 12 Jul 2014 06:22:03 GMT
EXPIRES: 180
SUPPORTED: timer,resource-priority,replaces
SUPPORTED: X-cisco-srtp-fallback
SUPPORTED: Geolocation
USER-AGENT: Cisco-CUCM8.6
CONTENT-TYPE: multipart/mixed;boundary=uniqueBoundary
ALLOW: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
P-ASSERTED-IDENTITY: "Deepak Srivastava" <sip:[email protected]>
MIME-VERSION: 1.0
Min-SE: 1800
Cisco-Guid: 3581525248-0000065536-0000000053-0255466924
Session-Expires: 1800
Geolocation: <cid:[email protected]>;inserted-by="172.29.58.15"
Remote-Party-ID: "Deepak Srivastava" <sip:[email protected]>;party=calling;screen=yes;privacy=off
--uniqueBoundary
Content-Type: application/sdp
v=0
o=CiscoSystemsCCM-SIP 35075 1 IN IP4 172.29.58.15
s=SIP Call
c=IN IP4 172.29.58.15
t=0 0
m=audio 28288 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
--uniqueBoundary
Content-Type: application/pidf+xml
Content-ID: [email protected]
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:cl=" urn:ietf:params:xml:ns:pidf:geopriv10:civicLoc"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:caps="urn:ietf:params:xml:ns:pidf:caps"
xmlns:cisco="http://www.cisco.com"
entity="pres:[email protected]">
<dm:device id="sg89ae">
<caps:devcaps>
<cisco:gateway>false</cisco:gateway>
</caps:devcaps>
<gp:geopriv>
<gp:location-info>
<cl:civicAddress>
<cl:country>NO</cl:country>
</cl:civicAddress>
</gp:location-info>
<gp:usage-rules>
<gp:retransmission-allowed>yes</gp:retransmission-allowed>
<gp:retention-expiry>2014-07-13T06:22:03Z</gp:retention-expiry>
</gp:usage-rules>
</gp:geopriv>
<timestamp>2014-07-12T06:22:03Z</timestamp>
</dm:device>
</presence>
--uniqueBoundary--
------------EndOfIncoming SipMessage
TL_INFO(TF_PROTOCOL) [0]0868.08B8::07/12/2014-06:22:03.351.000000bf (S4,SipMessage.DataLoggingHelper:sipmessage.cs(613))[3168828821]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTcpConnection_310339F>], 172.29.55.162:5068->172.29.58.15:47485
SIP/2.0 488 Not Acceptable Here
FROM
: "Deepak Srivastava"<sip:[email protected]>;tag=35075~3a834c6d-74d2-4f7c-89b1-cae86be13da3-48284953
TO
: <sip:[email protected]>;epid=E254C31B54;tag=e8831d44ab
CSEQ
: 101 INVITE
CALL-ID
: [email protected]
VIA
: SIP/2.0/TCP 172.29.58.15:5066;branch=z9hG4bK10663aa09f0
CONTENT-LENGTH
: 0
SERVER
: RTCC/4.0.0.0 MediationServer
------------EndOfOutgoing SipMessage
TL_INFO(TF_PROTOCOL) [0]0868.0F1C::07/12/2014-06:22:03.532.000002a7 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(686))[3358199169]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_2F779B4>], 172.29.55.162:59333<-172.29.55.24:5061
SIP/2.0 404 Not Found
FROM: <sip:031986;[email protected];user=phone>;epid=A6D7517671;tag=38bdbeec1c
TO: <sip:031986;[email protected];user=phone>;tag=D911B6138F470C253AEC6130E12D8647
CSEQ: 151 SERVICE
CALL-ID: e240b47e04744efaa88c778f9dcabe1d
VIA: SIP/2.0/TLS 172.29.55.162:59333;branch=z9hG4bK894ba852;ms-received-port=59333;ms-received-cid=4896700
CONTENT-LENGTH: 0
SERVER: RTC/4.0
ms-diagnostics: 1003;reason="User does not exist";TargetUri="[email protected]";source="sip.abc.com"
ms-edge-proxy-message-trust: ms-source-type=EdgeProxyGenerated;ms-ep-fqdn=edge.abc.com;ms-source-verified-user=verified
------------EndOfIncoming SipMessage
Thanks,
Deepak

According to this log, the call is going to this number:
031986
in conference bridge) with that number? That said, typically you would be normalizing those phone numbers to E164 via Dial Plans before Reverse Number Lookup occurs. So I would ensure you have a dial-plan for your PSTN Gateway (add a new dial
plan, select pool and choose the PSTN gateway). Make sure you have a normalization rule to add a + to all inbound numbers from the gateway. And your LineURI is something like tel:+031986.
Thanks,
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

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

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.

Office 2010 MUI in Finnish and Save and Send function not working after upgrading to Lync 2013 MUI

Problem is as follows. Used to have Office 2010, Outlook 2010 and Lync 2010, everything was working. People used it in Finnish and seemly quite a many of them used the Talleta ja lähetä (Save and Send in Finnish) in Office products.
After upgrading Lync to 2013 version, with Finnish language pack installed with it, the Save and send does not work in Office 2010 if it is used with Finnish as display language. When you try to use it you get a Mapi error and reason is undefined or something,
hard to say what it is exactly in english as the error message is in finnish. On those machines if the display language is changed back to english the Save and send works as it should.
Any ideas?

The problem was caused by the Language Packs for Lync 2013 or Office 2013. Without them all works.
And if you want to just unisntall the 2013 lang packs, then you also need to repair install the office 2010 ones to make it work again.

TAPIOVERRIDE not working w/Outlook 2010 64-bit & Lync 2013 64-bit

Hi all,
I have a Win7 64-bit machine with Office 2010 Standard 64-bit and Lync 2013 64-bit. The user would like to use the Windows Dialer instead of Lync to call from his Outlook contacts. Prior to my installing Lync for him, this worked very well. However, thereafter
Lync attempts to do the calling.
There are dozens of threads out there for using the TAPIOVERRIDE registry fix (http://support.microsoft.com/kb/959625/en-us) to correct this issue, but it is not working for me and I assume it's due to my combination of application versions. I've confirmed
both approaches (HKLM\Software\Microsoft\... -vs- HKLM\Software\Wow6432Node\Microsoft\...) fail to work even after rebooting entirely - for the record, I would assume the "32-bit approach" is what I need.
Has anyone gotten the TAPIOVERRIDE fix to work with the aforementioned software versions? Can anyone else make a recommendation on a TAPI add-in for Outlook which would inherently override Lync's calling functionality?
Thanks!

Aaron0001,
Good news. As an Office365 subscriber, I was able to open a service ticket on this issue, and I believe we've got a solution. As it turns out, these Call Integration/TAPIOVERRIDE keys do work (as a precaution, I created both); however, it appears
they have to be in-place when you install Lync to have any effect. I'm guessing that these keys may impact how Lync installs, but have no effect if Lync is already installed.
I had uninstalled Lync so that I could use Outlook with Windows dialer ... dialing functionality was restored as soon as I uninstalled Lync. However, when I got online with the Microsoft technician he had me reinstall Lync 64bit (after the keys had
already been created) and, presto, Outlook is still using Windows dialer rather than contacting Lync to try to place the call.
I hope this is helpful to you, or to anyone else who happens upon this page with the same problem.
All the best,
Kevin

Lync 2013 Mobility continues to not work

Having issues getting mobility to work.
Simple environment:
Single server Edge pool
Single server EE pool
SQL clustered backend
All Lync 2013 CU1 at this point in time.
Potentially required reading:
Deploying Mobility (Technet)
Lync Mobility Deep dive
(based on 2010, but nearly the same in 2013)
http://masteringlync.com/2011/08/13/using-fiddler-to-troubleshoot-address-book-download-issues/
http://blogs.technet.com/b/nexthop/archive/2012/11/09/understanding-lync-server-autodiscover-to-support-the-lync-windows-store-app.aspx
Windows RT app uses the same method as IOS, and is more wiresharkable/tracable, so I am using that.
Client end errors:
Windows RT app (15.0.4481.1503) - this client version cannot log in.
iOS - Can't sign in. Please check your account information and try again.
I don't have a windows phone or android, so working with the clients I have. (I understand these also do not work)
Fiddler trace of Windows RT app session:
From the W3svc logs:
2013-03-20 03:53:17 1.2.3.4 GET /Autodiscover/AutodiscoverService.svc/root/user [email protected] 4443 - 75.122.79.199
LyncImm/15.0.4481.1503+(Microsoft+Lync) 401 0 0 35
LyncImm is
NOT a user agent listed in the CSCP - google "user agent" +lyncIMM turned up nothing. Dead lead?
Lync connectivity analyzer shows it repeats the same webticket 401 over and over with:
Cookie found in autodiscover response: StatusCode: 401, ReasonPhrase: 'Unauthorized', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
X-Ms-diagnostics: 28032;source="LyncFE.company.local";reason="The web ticket is invalid.";faultcode="wsse:InvalidSecurityToken"
X-MS-WebTicketURL:
https://lyncweb.company.com/WebTicket/WebTicketService.svc
X-MS-WebTicketSupported: cwt,saml
X-MS-Server-Fqdn: LyncFE.company.local
X-Content-Type-Options: nosniff
Cache-Control: no-cache
Date: Wed, 20 Mar 2013 04:12:20 GMT
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Content-Length: 1293
Content-Type: text/html
LCA: from inside, choosing Windows App - success!
LCA: from inside, choosing Lync Mobile Apps- fail:
Failed to obtain the WS-Metadata Exchange (MEX) document using GET for
https://lyncweb.company.com/Mcx/McxService.svc/mex.
The service did not require authorization.
LCA, from outside, choosing Windows App - hangs repeatedly on the HTTPS external channel. (repeating 401's on webticket service)
LCA, from outside, choosing Choosing Lync Mobile apps - failed, same as from inside #2
Here's what the LCA failure looked like:
2013-03-20 04:59:12
1.2.3.4 POST /WebTicket/WebTicketService.svc/mex - 4443 - 75.122.79.199 - 200 0
0 134
2013-03-20 04:59:12
1.2.3.4 POST /WebTicket/WebTicketService.svc/Auth - 4443 - 75.122.79.199 - 200
0 0 155
2013-03-20 04:59:12
1.2.3.4 GET /Autodiscover/AutodiscoverService.svc/root/user
[email protected] 4443 - 75.122.79.199 -
401 0 0 35
2013-03-20 04:59:13
1.2.3.4 POST /WebTicket/WebTicketService.svc/mex - 4443 - 75.122.79.199 - 200 0
0 126
2013-03-20 04:59:13
1.2.3.4 POST /WebTicket/WebTicketService.svc/Auth - 4443 - 75.122.79.199 - 200
0 0 158
2013-03-20 04:59:13
1.2.3.4 GET /Autodiscover/AutodiscoverService.svc/root/user
[email protected] 4443 - 75.122.79.199 -
401 0 0 31
2013-03-20 04:59:13
1.2.3.4 POST /WebTicket/WebTicketService.svc/mex - 4443 - 75.122.79.199 - 200 0
0 126
2013-03-20 04:59:13
1.2.3.4 POST /WebTicket/WebTicketService.svc/Auth - 4443 - 75.122.79.199 - 200
0 0 148
2013-03-20 04:59:13
1.2.3.4 GET /Autodiscover/AutodiscoverService.svc/root/user
[email protected] 4443 - 75.122.79.199 -
401 0 0 33
2013-03-20 04:59:13
1.2.3.4 POST /WebTicket/WebTicketService.svc/mex - 4443 - 75.122.79.199 - 200 0
0 121
2013-03-20 04:59:13
1.2.3.4 POST /WebTicket/WebTicketService.svc/Auth - 4443 - 75.122.79.199 - 200
0 0 155
2013-03-20 04:59:13
1.2.3.4 GET /Autodiscover/AutodiscoverService.svc/root/user
[email protected] 4443 - 75.122.79.199 -
401 0 0 31
2013-03-20 04:59:15
1.2.3.4 POST /WebTicket/WebTicketService.svc/mex - 4443 - 75.122.79.199 - 200 0
0 125
2013-03-20 04:59:15
1.2.3.4 POST /WebTicket/WebTicketService.svc/Auth - 4443 - 75.122.79.199 - 200
0 0 147
2013-03-20 04:59:15
1.2.3.4 GET /Autodiscover/AutodiscoverService.svc/root/user
[email protected] 4443 - 75.122.79.199 -
401 0 0 32
2013-03-20 04:59:15
1.2.3.4 POST /WebTicket/WebTicketService.svc/mex - 4443 - 75.122.79.199 - 200 0
0 120
2013-03-20 04:59:15
1.2.3.4 POST /WebTicket/WebTicketService.svc/Auth - 4443 - 75.122.79.199 - 200
0 0 151
Similar thread:
http://social.technet.microsoft.com/Forums/en-US/ocsmobility/thread/96c3fc3a-2f80-435a-8368-1a83dcd56e55/
http://msdn.microsoft.com/en-us/library/ff595929%28v=office.12%29.aspx
IOS attempt at sign on (version 4.3.8000.0000)
IIS log files:
2013-03-20 04:26:08
1.2.3.4 GET / sipuri=sip:[email protected] 4443 - 166.137.151.211
Lync%202010/1.6+CFNetwork/609.1.4+Darwin/13.0.0 200 0 0 1382013-03-20 04:26:08
1.2.3.4 POST /webticket/webticketservice.svc - 4443 - 166.137.151.211
Lync%202010/1.6+CFNetwork/609.1.4+Darwin/13.0.0 401 0 0 802013-03-20 04:26:08
1.2.3.4 POST /webticket/webticketservice.svc - 4443 - 166.137.151.211
Lync%202010/1.6+CFNetwork/609.1.4+Darwin/13.0.0 401 1 2148074254 1292013-03-20 04:26:08
1.2.3.4 POST /webticket/webticketservice.svc - 4443 - 166.137.151.211
Lync%202010/1.6+CFNetwork/609.1.4+Darwin/13.0.0 401 1 2148074252 882013-03-20 04:26:08
1.2.3.4 POST /webticket/webticketservice.svc - 4443 - 166.137.151.211
Lync%202010/1.6+CFNetwork/609.1.4+Darwin/13.0.0 401 1 2148074254 782013-03-20 04:26:08
1.2.3.4 POST /webticket/webticketservice.svc - 4443 - 166.137.151.211
Lync%202010/1.6+CFNetwork/609.1.4+Darwin/13.0.0 401 1 2148074252 882013-03-20 04:26:09
1.2.3.4 POST /webticket/webticketservice.svc - 4443 - 166.137.151.211
Lync%202010/1.6+CFNetwork/609.1.4+Darwin/13.0.0 401 1 2148074254 782013-03-20 04:26:09
1.2.3.4 POST /webticket/webticketservice.svc - 4443 - 166.137.151.211
Lync%202010/1.6+CFNetwork/609.1.4+Darwin/13.0.0 401 1 2148074252 84
IOS log file was too large to post in message.
Running test-cmdlets:
$passwd1 = ConvertTo-SecureString "supersecure" -AsPlainText -Force $passwd2 = ConvertTo-SecureString "notontheinternet" -AsPlainText -Force $tuc1 = New-Object Management.Automation.PSCredential("domain\user1",
$passwd1) $tuc2 = New-Object Management.Automation.PSCredential("domain\user2", $passwd2) Test-CsMcxP2PIM -TargetFqdn lyncfe.company.local -Authentication Negotiate -SenderSipAddress sip:[email protected] -SenderCredential $tuc1 -ReceiverSipAddress
sip:[email protected] -ReceiverCredential $tuc2 -v
From <http://technet.microsoft.com/en-us/library/hh690024.aspx>
Results:
Target Fqdn : lyncfe.company.com
Target Uri :
https://lyncfe.company.com:443/mcx
Result : Failure
Latency : 00:00:00
Error Message : No response received for Web-Ticket service.
 Inner Exception:The HTTP request is unauthorized with client
 authentication scheme 'Ntlm'. The authentication header
 received from the server was 'Negotiate,NTLM'.
 Inner Exception:The remote server returned an error: (401)
 Unauthorized.
Diagnosis :
 Inner Diagnosis:X-MS-Server-Fqdn : lyncfe.company.com
 Cache-Control : private
 Content-Type : text/html; charset=utf-8
 Server : Microsoft-IIS/7.5
 WWW-Authenticate : Negotiate,NTLM
 X-Powered-By : ASP.NET
 X-Content-Type-Options : nosniff
 Date : Wed, 20 Mar 2013 04:39:44 GMT
 Content-Length : 6639
Verbose comments on it:
Trying to get web ticket.
Web Service Url :
https://lyncfe.company.com:443/WebTicket/WebTicketService.svc
Using NTLM\Kerberos authentication.
Could not get a web ticket
CHECK:
- Web service Url is valid and the web services are functional
- If using Phone Number\PIN to authenticate, make sure they match the user uri
- If using NTLM\Kerberos authentication, make sure you provided valid
credentials
URLs and ports all look OK, all services started.
Not using phone/PIN
I provided valid creds - the virtual directories show anon/NTLM for the Webticket vdir.
Any help is welcome - really want this issue put to bed!

I know this is an old thread, but I was struggling with the same error for mobility, and I hope this may help others in the same situation.
On my scenario the issue was caused because the customer didn't use any reverse-proxy solution, instead the FE external website was directly published using a FortiGate box.
Given that scenario, there were 2 different certs installed on the FE server, 1 (internal RootCA) certificate was applied to the internal website, and another one issued by Godaddy was assigned to the external website manually from IIS console.
---I know this is far from a supported solution, but I was able to get it working after some investigation---
To solve the issue I use this article:
http://technet.microsoft.com/en-us/library/jj205253.aspx it explains how to check and assign the certificates for oAuth and I used these cmdlets to specify the Godaddy cert to the "WebServiceExternal" & "OAuthTokenIssuer" websites.
After that the mobility access for internal and external users started to work as expected, I've validated it with "Lync Connectivity Analyzer" and with different mobile clients on Android, IOS and Windows Store.
Hope this information may be useful.
Performance, Security & Design

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

Microsof VX 3000 or 6000 Webcam does not work with Lync 2013 under Windows 8.1

Hi,
The problem is that i cannot use the Microsoft VX-3000 or VX-6000 with Lync 2013 under Windows 8.1.
If i go in settings under Video i can see the preview from the webcam just fine, so it works there no problem.
Wenn i try to enable my camera in a conference it does not work, i get an error: Your video cannot be started.
Now, there are no Windows 8.1 drivers for the Webcam so i installed the latest Windows 7 drivers. Because of that this webcam does not work with apps, that is fine i understand the driver problem and the way the new apps work.
But this Webcam works with skype under Windows 8.1 and it works with Lync 2010 client.
The same Webcam works just fine with Lync 2013 under Windows 7.
Is there anything i could do so that i get this Webcam to work with Lync 2013 desktop client under Windows 8.1?
Thanks

Hi,
According to your description, it may be caused by driver.
You can try to install the latest version of Display Driver to fix the display issue.
Since there is no driver for Windows 8.1, I suggest you wait for updating.
You can also post a case on Windows 8 forum, thank you for your understanding:
http://social.technet.microsoft.com/Forums/en-US/home?forum=W8ITProPreRel%2Cw81previtpro&filter=alltypes&sort=lastpostdesc
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync to Lync calls not working when users outside of network. But calls from Lync to external numbers do work.

Hello,
We are having the following issue: when our lync users are outside of our network, just connected to their home internet or a public WiFi and not on VPN, they cannot place calls to other
Lync users inside our network. They get a poor network connection message on the call window. But they are able to make calls from Lync to external numbers without a problem.
Inside our network, Lync to Lync calls work perfectly fine, the same for calls from Lync to external numbers.
Does anybody know what could be the cause of our issue? Perhaps I'm missing a setting on our Edge server. What should be the first thing I should check on my Lync servers?
Thanks for any help!

Have you opened up ports on your firewall from your internal clients to the edge on UDP/3478 and TCP/443? This sounds like you might have a problem there. Can you internal clients properly route to this subnet and resolve the pool name of your
edge pool?
Ports and protocols poster, check out in A/V section client traffic to edge showing UDP/3478 and TCP/443:
http://www.microsoft.com/en-us/download/details.aspx?id=39968
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".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Creating a Lync meeting not working in outlook 210 client

We use office 365 environment and pushed lync 2013 client to user who uses Outlook 2010 Client still. Anyway the default domain work address the user is able to go to calendar, click new meeting button and fill out the meeting email then click LYNC Meeting,
which works, but when he adds another domain email account in his outlook and tries doing that, he gets an error "The request failed. Please try again. Make sure that you are signed in to Microsoft Lync" in which he is signed in.
I deleted sip, reinstalled Lync 2013, redid the outlook profile, not sure what is triggering this. His other domain account uses Office 365.
Any ideas?
Best regards, Joe C Partner Online Technical Community ----------------------------------------------------------------------------------------- We hope you get value from
our new forums platform! Tell us what you think: <a href="http://social.microsoft.com/Forums/en-US/partnerfdbk/threads">http://social.microsoft.com/Forums/en-US/partnerfdbk/threads 
</a>------------------------------------------------------------------------------------------ This posting is provided "AS IS" with no warranties, and confers no rights <hr>

Correction:
The error happens when he sends a lync meeting to his own second domain or anyone within the domain.
So he has two email addresses in outlook
1 domain 1 (default) which he connects to Lync with this and this is our domain
2 domain 2 this is his other domain email address in which he added to Outlook.
So when he goes on domain 1 calendar and creates a meeting and licks on New Lync meeting to someone in Domain 2 that is when Outlook throws an error that he is not signed into Lync in which he is. It;s odd.
Sorry for the confusion.
Funny thing is when he removes Domain 2 email account, lync meetings work fine to send. So something with domain 2 email address added to his outlook is triggering this.
Best regards, Joe C Partner Online Technical Community ----------------------------------------------------------------------------------------- We hope you get value
from our new forums platform! Tell us what you think: <a href="http://social.microsoft.com/Forums/en-US/partnerfdbk/threads">http://social.microsoft.com/Forums/en-US/partnerfdbk/threads 
</a>------------------------------------------------------------------------------------------ This posting is provided "AS IS" with no warranties, and confers no rights <hr>

ISight not working with Webex, GoToMeeting or Lync...BUT works with Skype, Facetime, Photobooth (June 2013 MBA)

Brand new MacBook Air (June 2013, 8MB RAM, 500GB SSD)
iSight not working with Cisco Webex, Citrix GoToMeeting or Microsoft Lync (error = webcam not detected); BUT iSight works with Skype, Facetime and Photobooth.
3 hours of phone support with Webex - no luck.
Tried SMC and PRAM reset - no luck.
Tried erasing disk and reinstalling OSX 10.8.4 and apps manually with latest versions - no luck.
Apple phone support says it's not Apple's problem because Apple apps work.
Exchanged at Apple Store for another new MacBook Air, again installed apps manually with latest version (not from time machine) - STILL NO LUCK!!!
Is there an update Apple or Cisco, Citrix and Microsoft need to put out for the new MBAs or do I just have 2 lemons???

You're welcome.
1wave wrote: ... an external webcam which might be a cheaper alternative ...
It will be interesting to see what the vendors say about using a Mac-compatible external webcam.
If not, some netbook or other Windows® device might offer compatibility at a much lower cost than a compatible Apple notebook.
We will watch for your update(s). What the vendors tell you will be very helpful to others who share this or similar issues with their new MBAs.
Message was edited by: EZ Jim
Mac OSX 10.8.4

Lync 2013 (Oct CU update) Dial-in Webpage not working. This content cannot be displayed in a frame

today we found an issue with our Lync 2013 deployment while investigating another issue.
ok se we have/had Lync 2013 setup along with IIS ARR. All seems to be working fine.
with the exception of our Dial in page.
no matter what i do it does not work. We have a near identical setup for our other domain & they have no issues. (i copied the Bin folder from the "C:\Program Files\Microsoft Lync Server 2013\Web Components\Dialin Page\Ext" of the working site.
then tracked it down to the "\bin\" folder. which contains the "Micrsoft.RTC.nternal.Conference,dll"
file. If i copy this into our US folder the site works as it should.
So now the kicker....our US file is the newest (5.0.8308.556) where as the other domain is "5.0.8308.301"
with that said, & with our correct version (.556) of the conference.dll file, this is the page that loads...which we can then click the link & it opens our conference page as it should.
This content cannot be displayed in a frame
To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.
What you can try:
Open this content in a new window
So somthing is a miss, & i think it is related to the Oct CU....but have no evidence at the moment.....
any help would be great

yes, IE will shows the warning page, but then lets you click the link.
chrome shows noting. When running Debugger, chrome states:
Refused to display 'https://fepool.company.local/Dialin/Conference.aspx' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'..
the issue is definatley stemming from the new .dll from the CU update. as i compared it against the older version. the newer version is throwing the "X-Frame-options:
SAMEORIGIN"....
I am not sure if that is intended or not.
also i have not been able to find out what the specific purpose of the conferenceproxy.aspx file that the dialin page
uses as its default document. It appears that the page only stands to serve up the Conference.aspx page in the Iframe..
if we swap our default page to be the Conference.aspx all works as expected.

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

LYNC NOT WORKING

Similar Messages

Maybe you are looking for