Lync 2013 on RDP

I am running in a terminal server environment with Citrix XenApp, on Windows 2008 R2, with Lync 2013 client installed. When I attempt to do a screen share, the screen shows the desktop of the TS server.
I attempted to load the VDI plugin for Lync, but it seems to be for desktop OS. Is my configuration supported, and if so, what do I need to do in order to redirect video from the server desktop to end-client?

Hi,
Thank you for posting in Windows Server Forum.
To support enterprise-grade audio and video over VDI with Lync 2013, Microsoft implemented a new Media Redirection architecture and built a VDI plugin that runs on thin clients and pairs with the Lync client running in the remote desktop to which the end user
has connected.
In addition to TP’s reply, please check below articles for information.
XenDesktop 7, XenApp 6.x and Citrix Receiver 4.0 Support for Microsoft Lync 2013 VDI Plug-in
http://support.citrix.com/article/CTX138408.html
Update: Microsoft Lync 2013 in a Virtual Desktop Infrastructure
http://blogs.technet.com/b/nexthop/archive/2012/07/31/microsoft-lync-2013-preview-in-a-virtual-desktop-infrastructure.aspx
Deployment Details for the Lync VDI Plug-in
http://blogs.technet.com/b/nexthop/archive/2013/09/23/deployment-details-for-lync-vdi-plugin.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Similar Messages

Can't Log In with Lync 2013 Windows 8 App over VPN

Howdy,
I've downloaded the Lync 2013 App to Windows 8.1. When I type in my work email, I can't sign in. I get that the server isn't available or doesn't support Lync.
The error is attached.
I can't find a forum for the Lync App itself so I'm hoping to be redirected or since this has to be an easy question, someone might answer it here.
I'm logged in on our VPN and I'm working around this issue right now with RDP to my desktop and signing in to Lync 2010 there. This is for the purpose of doing my class this next week from home and showing Yep, I'm really available over Lync.
What is really desired is to get Lync on my remote machine working but there's no real Settings page on the App.
Apparently it does pick up the VPN and tries to sign me in:
However, there's not much of a way to configure anything. I can't find a "Settings" page. Tried uninstall/reinstall to see if I didn't fat finger something.
Lync 2010 is set up on company laptops to work over VPN correctly from home so I can't imagine it's this hard. I think the "oversimplified" approach of just putting in the email address and (I'm theorizing) letting Lync detect VPN or not,
can I log in, etc. or whatever it does, this isn't working. And of course, it's Encapsulated. :)
OK, I have a work around, it's not a do or die issue here. I'll RDP to my desktop, sign in and Lync will show me available. I'll set my location as Home during the hours of the class.
But ... it's always REALLY annoying when you KNOW it's a simple setup procedure and if that's just found ...
Thanks for any help.
Michael Durthaler

Check that you configure requirement for Lync windows store App as exist in below link
http://technet.microsoft.com/en-us/library/jj823129.aspx
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"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Lync 2013 vdi RDS windows 2008R2

Hi, I have installed VDI on win2008R2 server with RDS make all configuration and it Works fine.
I have Win7 RDP installed VDI and updateted all RDP. I have USB WEBCAM and I configured remoteFx to use USB webcam and it Works with Win2008R2 RDS audio and Video.
I have Win 8.1 only installed VDI and change settings in RDP with WEBCAM internal and it Works.
I have another win 8.1 and installed VDI driver OS=64bit but VDI driver=32bit - local office = 32bit. I have configuret RemoteFX in local Group Polices. In RDP I can see USB internal WEBCAM -
Then I connect RDP I get Audio but not any Video.
I have tried to remove RemoteFX config in Local GRP, no effect.
Is there a conflict with Office 2010/office 2013 Lync and DVI or VDI driver should be 64Bit or ??,
I can connect from diffrent machines to same USER and that Works, but not from One machine.
Please help me

Hi ERAVN,
If you are using Remote Desktop Services, the Lync VDI plug-in bitness (that is, whether the application is 32-bit or 64-bit) must match the local computer’s operating system bitness. The bitness
of the operating system on the local computer and the operating system on the virtual machine do not need to match.
For more details, please refer to the following articles.
Deployment Details for the Lync VDI Plug-in
http://blogs.technet.com/b/nexthop/archive/2013/09/23/deployment-details-for-lync-vdi-plugin.aspx
Update: Microsoft Lync 2013 in a Virtual Desktop Infrastructure
http://blogs.technet.com/b/nexthop/archive/2012/07/31/microsoft-lync-2013-preview-in-a-virtual-desktop-infrastructure.aspx
Best regards,
Eric

Lync 2013 Edge and routing algorithm

Hi
I have problem with Lync 2013 Edge server. I'm tring resolve problem but for now I 'm totally lost.
Short description for a problem:
What works:
IM and presence communication to Internet and federation
A/V conferences with remote users and federated organizations.
File transfer to remote users and federated org.
What doesn't work:
Audio and video P2P connections to remote user and federated org. SIP signalization works, but media connection doesn't.
Tracing at wireshark shows that Edge server trying establish stun connection to INTERNAL clients on EXTERNAL interface.
Persistent route for internal subnets are added to routing table on server.
All ports are opened on firewall between DMZ and LAN.
I can ping and connect via RDP to stations on internal network.
Why A/V Edge service trying establish connection on external interface ?
What is algorithm/mechanism for network interface selection
Regards
Mawik

Hi,
Please check if all server settings were correct (check if Global Settings had the A/V Edge server defined and assigned as the A/V Authentication Service in the pool properties).
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 Server / Roles & Components

Lync
2013 Server / Roles & Components
Front End
User authentication and registration
Presence information and contact card exchange
Address book services and distribution list expansion
IM functionality, including multiparty IM conferences
Web conferencing, PSTN Dial-in conferencing and A/V conferencing (if deployed)
Application hosting, for both applications included with Lync Server (for example, Conferencing Attendant and Response Group application), and third-party applications
Primary store for user and conference data. Information about each user is replicated among Front End Servers in the pool
Optionally, Monitoring, to collect usage information in the form of call detail records (CDRs) and call error records (CERs). This information provides metrics about the quality of the media (audio and video) traversing your network for both Enterprise
Voice calls and A/V conferences.
Web components to supported web-based tasks such as web scheduler and join launcher.
One Front End pool runs the Central Management Server DB, which manages and deploys basic configuration data to all servers running Lync
Optionally, Archiving, to archive IM communications and meeting content for compliance reasons.
Optionally, if Persistent chat is enabled, Persistent Chat Web Services for Chat Room Management and Persistent Chat Web Services for File Upload/Download.
Back End
Database server running Microsoft SQL Server
Provide the DB services for the Front End pool
Acts as backup store for the pool’s user and conference data
Primary stores for other DB’s like Response Group
High Availability for the BE DB is provided via SQL Mirroring
Optional Witness to enable automatic failover for BE
SQL Sever 2008 R2 or higher required for SQL Mirroring
Edge Server
Enable users to communicate and collaborate with users outside the organization’s firewall
Comprises four separate server roles
Access Edge – Acts as a secure proxy for all remote Lync signaling traffic
Remote Access
Federation
Public IM Connectivity (PIC)
Web Conferencing Edge – Enable remote users to participate in Web conferences with internal or remote workers
A/V Edge – Responsible for secure relay of A/V media among internal, external, and federated contacts
XMPP Gateway – Allows IM/P with XMPP federated contacts
Reverse Proxy
Simple URL Publishing – Required for users to join Lync meetings
Web Conferencing Content – Users download meeting content (PowerPoint, Whiteboard, and Poll data) via Lync Web Services when in meeting
Address Book & Distribution List Expansion – Required for users to download Lync Address Book and perform DL expansion
User Certificates – Provides client certificate authentication via Lync Web Services
Device Updates – Provides software updates to Lync IP endpoints
Mobility – Provides connectivity for mobile clients via Lync Web Services
Mediation Server
Translates signaling and media between Lync Server and PSTN, IP-PBX, or SIP Trunk
Can be co-located on Front End or separated as stand-alone Server dependent on call volume
Role facilitates dial-in conferencing
Capacity
Co-located = 150 Concurrent Calls
Standalone = 1100 Concurrent Calls
Persistent Chat
Enable users to participate in multiparty, topic-based conversations that persist over time
Pchat Front End server role runs persistent chat service
Pchat Back End server stores chat content and compliance events
Geographic DR is provided via stretched pool and SQL log shipping to replicate DB info
150k provisioned users / 80k concurrent users
Archiving
Uses SQL Server 2008 R2 or SQL Server 2012 for DB
Capable of archiving the following:
Peer-to-peer IM
Multiparty IM
Web Conferences, including uploaded content and events
A/V for peer-to-peer IM and web conferences
Web conferencing annotations and polls
Monitoring
Agent that runs on each Front End Server that collects and manages information from the Front End and Mediation Servers
Stored on SQL Server DB
Leverages SQL Server Reporting Services for creation of reports related to call quality and metrics
Office Web Apps Server
External server leveraged for rendering PowerPoint slides within the Lync client and Lync Web App
Typically leveraged within SharePoint deployments to deliver browser-based versions of Microsoft Office applications
System Center Ops Mgr
Health configuration in Lync Server 2013 is built around System Center Operations Manager and the use of Lync Server Management Packs. These Management Packs include a number of new features and enhancements, including:
Feature
Description
Synthetic Transactions
Windows PowerShell cmdlets that can be run from various locations to ensure that end user scenarios such as sign-in, presence, IM, and conferencing are readily available to end users.
Call Reliability Alerts
Database queries for Call Detail Records (CDR). These records are written by Front End Servers to reflect whether end users were able to connect to a call or why a call was terminated. These queries result in alerts that indicate when a wide range of end
users are experiencing connectivity issues for peer-to-peer calls or basic conferencing functionality.
Media Quality Alerts
Database queries that look at Quality of Experience (QoE) reports published by clients at the end of each call. These queries result in alerts that pinpoint scenarios where users are likely to be experiencing poor media quality during calls and conferences.
The data is built upon key metrics such as packet latency and loss, metrics that are known to directly contribute to call quality.
Component Health
Individual server components raise alerts by using event logs and performance counters. These alerts indicate failure conditions that can severely impact one or more end user scenarios. These alerts can also indicate a variety of other failure conditions,
including services not running, high failure rates, high message latency, or connectivity issues.
Dependency Health
Failures can occur for a variety of external reasons. The management packs now monitor and collect data for some of the critical external dependencies that might indicate severe issues, including IIS availability, CPU and memory usage of servers and processes,
and disk metrics.
Exchange UM
http://www.contactcenterarchitects.com/lync-2013-server-roles-components/

Hi,
Thank you for sharing the information. It is useful for others who not understand Lync Server Roles and Components. You time and effort are appreciated.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Office web Apps server Lync 2013 Certificate

Hi,
I'll be installing Office web app (OWA) server with Lync 2013 std edition. External users access is disabled but federation is enabled, mean OWA will be exposed to internet as wabweb.contoso.com, the interal host name of OWA server is owa.contoso.local
Does the certificate on the on OWA server need to have owa.contoso.local and certificate principle name and wabweb.contoso.com as SAN? or only owa.contoso.local is enough?

It really depends on how you publish the server to the internet. You have some options. If you are publishing this via a reverse proxy, internally you would have a private cert with .local on it and the public name on the reverse proxy. If you are
punching a firewall hole/NAT directly to the server your best option is to use a public cert on that server directly.
That all said, personally I like to make both the internal and external farm URL the same, and use a public cert on the server (if no reverse proxy is in play). So I would actually enter the OWAS Farm as wabweb.contoso.com in topology builder, than
when creating the farm via PowerShell make that both the internal and external URL and get a certificate with a single name on it of wabweb.contoso.com.
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Lync 2013 meeting invitation customizations not working for some users

Hello Microsoft TechNet Forms,
I have a strange problem that I am totally stumped on. I made some modifications to the Lync 2013 meeting configuration to add in my company's logo, a footer and set a custom help Lync URL. Now everything seemed to work expect for myself and
one other person I tested with. If I try creating a new Lync 2013 meeting via my Outlook 2013 the normal stock Lync meeting invite appears. Yet testing with any other user everything I have changed appears as expected and I am at a total loss to why.
I have so far from troubleshooting determined it must be something with my account that is causing it but I have just not been able to determine what. As signing into a different machine yields the same result yet testing with another account that is
known to work on the exact same machine works correctly with the different account. I have tired deleting and re-crating my Lync account just in case that had something to do with it but that didn't fix the problem. I have tired repairing Office 2013 to
running windows update on Office 2013 which didn't help.
The changes I made to the meeting configuration are global scoped. I have so far not found anything online from anyone ever reporting a similar issue to this. At this point I am stuck on what I should be looking for with regards to what is stopping
the meeting invite updating for myself and the other person. Given I don't know what mechanism is involved with updating the Lync meeting invite on Outlook 2013 I am stumped. I am open to any suggestions someone might have as to what to do next or what might
be the cause of this problem.
Nicholas,

Hi Nicholas,
Can you compare your account with other’s and check if your account is applied any special policy in Lync Control Panel ?
Best regards,
Eric

Lync 2013 Front-End HA

We are currently in a co-existence environment with both Lync 2010 and 2013 running side-by-side.
There are 2 FE pools with pool pairing setup for Lync 2013. We have been carrying out some testing before migrating all of our users over.
We have an issue where when we take out one of the 2013 front end servers the client does not automatically reconnect to one of the other servers in the pool, occasionally it will but can take 10-15 mins to do this. If we simulate a similar test on the 2010
front ends the client reconnects in seconds.
I am using the Lync 2013 client

Thanks for your replies.
I have setup DNS LB for the pool name (this is working correctly) and I am using a kemp load balancer for the internal web services FQDN
I checked the EndPointConfiguration.Cache file and it just had the name of the front end server I was connected to. I deleted it and restarted my client now the EndPointConfiguration.Cache file has the name of the pool, the front end server that I am connected
to and the IP addresses of the servers in the pool, is that correct?
I tested the failure of the server I was connected to by removing the network adapter in VMware.
It took 44 seconds for my client to sign out and 1:15 after that to sign back in. My LPE took 2:18 to sign out and 1:22 after that to sign back in. Surely this cant be right?
During the time the failure happens and the client signs out, it is unusable.
I have had a look in the snooper logs but it is difficult to see the wood for the trees.
Thanks for your help.

Lync 2013 Enterprise load balancing on the front end and edge pool

Hi,
I am setting up a Lync 2013 Enterprise deployment consisting of a Front End pool (x2 FE servers) and an Edge pool (x2 Edge servers). I'm seeing some conflicting advice regarding load balancing using hardware or DNS for the front end and the edge.
On the front end I have 2 internal DNS records 'lyncfepool1.contoso.local' each of which map to one of the IPs of the FE servers. I've used my details to populate the Detailed Design Planner excel spreadsheet and am told that I require a HLB to load
balance my front end pool. I'm aware of the need to load balance HTTPS traffic internally (which will be done by TMG) however other traffic to the front end (SIP, etc) can be balanced by DNS only, and not require a HLB?
Can someone clarify the front end requirement?
Also - looking now at the edge pool - this site again have two edge servers in a pool. We are using a total of six private IP addresses, two per edge service (2 x av.contoso.com, 2 x sip.contoso.com and 2 x webcon.contoso.com). These will be
NAT'ed by the external firewall and directed to the respective external (DMZ) IP addresses on the Edge servers on port 443. I know this isn't true roundrobin due to the intelligence of the Lync client when connecting (in that the Lync client will connect
to one of the public IPs and if it can't connect, it will know to connect to the other service IP), however I want to clarify this set up, particularly the need to direct the external public IP traffic at the DMZ Edge IP specified in the topology builder.
I've attached a basic diagram of the external/DMZ/Edge side which hopefully helps with this question
Persevere, Persevere, Per..

That is because you will always need HLB for a front-end server since it hosts the Lync webservices which use HTTP/HTTPS traffic.
The description on the calculation tool also describes this correctly:
Supports Standard and Enterprise pools (up to 12 nodes), with pure device-based load balancing or a combination of DNS load balancing and device-based load balancing (for
Lync web services)
You can use either Hardware or DNS loadbalancing for SIP traffic only, but you will always need a HLB for the webservices. Both are applicable for the Front-End so you have either
full HLB for both SIP and HTTP(S) traffic
DNS LB for SIP traffic and HLB for HTTP(S) traffic
Hope this is more clear :-)
Lync Server MVP | MCITP Lync Server 2010 | If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.

Lync 2013 updating databases after updating Front End servers

We have a front-end server pool consisting of 3 Lync 2013 servers and a back end of 2 SQL servers using SQL mirroring. All servers are Windows 2008 R2.
Following the instructions in
http://support2.microsoft.com/kb/2809243 , I verified that the servers were all ready for updates, then I ran the
Stop-CsWindowsService -Graceful cmdlet to stop the Lync services on the first FE server, then I ran LyncServerUpdateInstaller.exe to install the updates. After the updates were installed, I restarted the server, waited for Lync services
to all start, then repeated the process on the next 2 servers in turn. This was all successful.
I am now looking at step 2 in this document, applying the back-end database updates, and I have a problem and some questions. The problem is that all the databases had the principal copy on the mirrored SQL server. I ran the recommended Invoke-CsDatabaseFailover
-NewPrincipal Primary cmdlet repeatedly, using all the database types I could find, but I still have two databases (database names
xds and lis) on the mirrored server. Since the cmdlet requires a database type, what type of databases are the xds and the lis databases?
Once I get that done, I an still unsure of exactly what to run to update the databases. The KB article states to run Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose .  Do I type this in exactly
as stated, or is FEBE.FQDN a variable for our SQL server or some other entity in our environment? If I do use the actual SQL Server name in that, do I run it twice, using the name of the mirrored SQL server the second time?
Thank you very much for your help.

Hi Logan Burt,
Central Management store database files
Data file or log purpose
                Xds.ldf
Transaction log file for the Central Management store
                Xds.mdf
Maintains the configuration of the current Lync Server 2013 topology, as defined and published by Topology Builder
                Lis.mdf
Location Information service data file
                Lis.ldf
Transaction log for the Location Information service data file
And you could verify if Lync Server 2013 database updates have completed successfully.
How to Verify if Lync Server 2013 Database Updates Completed Successfully
http://blogs.technet.com/b/dodeitte/archive/2013/07/02/how-to-verify-if-lync-server-2013-database-updates-completed-successfully.aspx
Best regards,
Eric

Unable to search GAL on Lync 2013 Front End Pool through Lync 2013 client

I'm in the beginning of a 2010 to 2013 migration and I'm currently testing co-existence functionality between pools. I've noticed that users cannot search the GAL from their Lync client after being moved to the 2013 pool.
When trying to access the internal URL https://fepool13.domain.com/abs/handler the user is prompted to login and after three failed attempts, receives "401 - Unauthorized: Access is denied due to invalid credentials. You do not have permission
to view this directory or page using the credentials that you supplied".
Searching withing a Lync 2010 or Lync 2013 client returns no results, but there are no errors as well as nothing in the event logs or tracing folder regarding not being able to search.
The 2010 pool has been in production for a few years now and when accessing its internal ABS URL https://fepool10.domain.com/abs/handler the user is granted access after a successful login.
In the IIS logs there are slightly more detailed 401 error codes, but I’m not sure what to make of them.
The rtcab database appears to have user information and all three front end servers appear to be syncing with active directory. I say the rtcab database appears to have user info because the AbUserEntry table is filled with User ID'd, GUID's and a
bunch of other stuff.
The authentication on 2013 front end servers “internal lync website/abs/handler” is set to 1. Negotiate, 2. Ntlm - which is the same as the 2010 front end servers.
Any ideas?

Hi,
Which step did you do among migration from Lync Server 2010 to Lync Server 2013?
Did you already move CMS from Lync Server 2010 to Lync Server 2013?
Please create a new Lync account on Lync Server 2013 pool and test the issue again.
Please check if User Replication has completed with the help of the link below:
http://technet.microsoft.com/en-us/library/jj204680.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

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

Iphone and ipad Lync Client Randomly cannot sign in to Lync 2013 Server

I have a Lync 2013 environment that will allow all clients to connect from inside and outside of the network except for ios devices. iOS devices are sometimes able to connect and sometimes not. When they are not able to sign in they receive a message stating,
"An Error Occurred in Lync. Please retry. If the problem persists, contact your support department"
I have run tests using the Microsoft Remote Connectivity Analyzer and all tests come back green. I have also used the Lync Connectivity Analyzer and get the results below:
Starting Lync server autodiscovery
Starting automatic discovery for secure (HTTPS) internal channel
Server discovery failed for secured internal channel against
https://lyncdiscoverinternal.earenfroe.com/
Starting automatic discovery for unsecure (HTTP) internal channel
Server discovery failed for unsecured internal channel against
http://lyncdiscoverinternal.earenfroe.com/
Starting automatic discovery for secure (HTTPS) external channel
Server discovery succeeded for secure (HTTPS) external channel against URL
https://lyncdiscover.earenfroe.com/
Starting automatic discovery for unsecure (HTTP) external channel
Server discovery failed for unsecured external channel against
http://lyncdiscover.earenfroe.com/
Starting the requirement tests for Lync Mobile 2013 App
Starting tests for Mobility (UCWA) service
Completed tests for Mobility (UCWA) service
Your deployment meets the minimum requirements for Lync Mobile 2013 App.
Anyone have any suggestions on where to go next? Troubleshooting an intermittent connection issue that only affects one mobile platform is tough...especially when all the testing tools say everything is configured correctly :)
Thanks in advance!
Tom

I have the same problem, and we have netscaller as revrse proxy solution and we have the required records created for mobility.
with lync2010 mobility it is working fine, but with lync 2013 mobiltity we have intermittent issue with error e2-3-33 error
raghu
I had the same problem (e2-3-33 on mobile devices at random times) and it turns out it was McAfee antivirus causing the UCWA service to crash repeatedly. The workaround for it is outlined in the below blog entry I found as well as the below Microsoft document.
Long story short you want to run follow the steps outlined in the workaround section below (I copied it from the linked MSFT document)
http://support.microsoft.com/kb/2997513
http://lynclounge.blogspot.com/2014/07/lync-mobility-issues-event-ids-1309.html
WORKAROUND
he following procedures must be performed on all Lync Server 2013 FE server and Director Lync 2013 server roles. To
perform these procedures, first open a command prompt as an administrator.
Windows Server 2008 R2
On the Start menu, type cmd.exe in the Windows search feature, and then press Enter.
Right-click cmd.exe, and then click Run as administrator.
Windows Server 2012
Press the Windows key to access the Start page.
Use the Windows search feature to locate cmd.exe.
Right-click cmd.exe, and then click Run as administrator.
In the Command Prompt window, follow these steps:
Navigate to the %install drive%:\Windows\System32\inetsrv> directory prompt.
Enter the following command, and then press Enter:
appcmd set config /section:applicationPools /[name='LyncUcwa'].recycling.disallowOverlappingRotation:true
Enter the following command, and then press Enter:
appcmd set config /section:applicationPools /[name='LyncUcwa'].processModel.shutdownTimeLimit:0.00:00:30
To confirm the changes from steps 2–3, enter the following command, and then press Enter:
appcmd list apppools lyncucwa /config
The following information should be returned to the console to confirm the update to the LyncUcwa application pool
settings:
<add name="LyncUcwa" autoStart="true" managedRuntimeVersion="v4.0" managedPipelneMode="Integrated" startMode="AlwaysRunning">
<processModel identityType="NetworkService" idleTimeout="00:00:00" shutdownTieLimit="00:00:30" />
<recycling disallowOverlappingRotation="true">
<periodicRestart time="00:00:00">
<schedule>
</schedule>
</periodicRestart>
</recycling>
<failure />
<cpu />
</add>

Voice problems with Lync 2013 Mobile

Hi
I have a situation where Lync 2013 on both iPhone & Android has started giving problems with making and receiving voice calls. There are no problems with Windows, Mac or Phone Edition clients that I'm aware of. I have not tested anything over the VPN,
but this should not be a factor.
For receiving calls - If the user is connected to the LAN via Wi-Fi AND the call is from an internal user, all works fine. If the call is from an external user OR the user is connected via 3G, then the call just shows "Connecting" indefinitely.
This includes transferred calls.
For making calls - If the user is connected to the LAN via Wi-FI and calls either an internal or external users, all works fine. If the user is connected via 3G and calls either an internal or external user, the phone rings, but when it's answered it shows
call ended.
I have ran RUCT on a computer outside the network, with the following findings:
DNS:
Record
Type
Hostname
IP Address
Port
Weight
Priority
_sip._tls.domain.com
SRV
sip.domain.com
Edge External IP
443
100
0
sip.domain.com
A
sip.domain.com
Edge External IP
sipexternal.domain.com
A
sipexternal.domain.com
Edge External IP
meet.domain.com
A
meet.domain.com
<null>
_ntp._udp.domain.com
SRV
pool.ntp.org
NTP Server IP
123
100
0
_sipfederationtls._tcp.domain.com
SRV
sip.domain.com
Edge External IP
5061
100
0
lyncdiscover.domain.com
A
sip.domain.com
Edge External IP
lyncdiscover.domain.com
CNAME
sip.domain.com
I have ran Test Port on each entry where there is a port with successful results. Ping works on all entries.
If I query Certificate Information on sip.domain.com with port 5061 or 444, it succeeds and returns the certificate with subject sip.domain.com. If I query 443, it fails with error "An error occurred while retrieving the certificate. Unable to read
data from the transport connection: An existing connection was forcibly closed by the remote host."
On Microsoft Remote Connectivity Analyzer, all tests pass except for the certificate test:
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server sip.domain.com on port 443
The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
Running netstat on Lync Edge gives me the following with regards to port 443:
TCP <Internal IP>:443 Lync2:0 LISTENING
TCP <External IP>:443 Lync2:0 LISTENING
Firewall allows connections on port 443 and I've tried disabling the firewall as well. Trying to open https://sip.domain.com in the browser on the Lync Edge fails also, telnet succeeds, but no data is returned.
I've restarted the AV service and also rebooted the Lync Edge server, no change. In the topology builder, I can see that AV is configured to listen on port 443.
Any ideas would be most welcome.
Regards
Lionel
MCP Windows Server MCTS .NET

I have ran a large amount of additional tests. On my latest round of testing, I have obtained the following results:
Call received via PSTN gateway on user DID, answered by desktop client inside LAN - works.
Call received via PSTN gateway on response group, answered by desktop client inside LAN - works.
Call received via PSTN gateway on user DID, answered by desktop client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by desktop client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by mobile client inside LAN - does not work.
Call received via PSTN gateway on response group, answered by mobile client inside LAN - does not work.
Call received via PSTN gateway on user DID, answered by mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on response group, answered by mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client inside LAN - does not work.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client inside LAN - does not work.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client outside LAN (3G) - does not work.
Call made through PSTN gateway from desktop client inside LAN - works.
Call made through PSTN gateway from desktop client outside LAN (behind NAT, DSL router) - works.
Call made through PSTN gateway from mobile client inside LAN - does not work.
Call made through PSTN gateway from mobile client outside LAN (behind NAT, DSL router) - works.
Call made through PSTN gateway from mobile client outside LAN (3G) - does not work.
Call from desktop client inside LAN to desktop or mobile client (regardless of location) - works.
Call from desktop or mobile client (regardless of location) to desktop client inside LAN - works.
Call from desktop or mobile client (regardless of location) to desktop or mobile client (regardless of location) - works.
There is no difference in behaviour between normal calls and conference calls. Reproducing the problem seems to require the following:
1. PSTN gateway needs to be involved
2. One party needs to be on mobile client
3. The mobile client needs to be inside the LAN or on a 3G connection, but not behind NAT on a DSL connection
The only conclusion I can make is that somehow NAT makes the problem go away, but it does not affect desktop clients (on the LAN or Wi-Fi at least, I do not have a way to test them on 3G).
The PSTN gateway (Cisco UCM) could also be the problem, but it works fine in all other cases. It has 4 trunks and makes all kinds of routing decisions, but once a call is routed to/from Lync, it should not make a difference on what type of device it is answered.
I'm really baffled by this one. Perhaps the 3G thing is a service provider issue and the issue on the LAN has something to do with the internal DNS combined with the behaviour of the mobile client. Just not sure exactly what.
MCP Windows Server MCTS .NET

Issues with Hosted Exchange, UM and Lync 2013.

Hello everyone!
I am trying to deploy UM with Office 365 Hosted Exchange. We are using one Lync 2013 Standard Edition FE and have deployed one edge server. We have set up our firewall to host the Reverse Proxy.
We do not use wildcard certs. External DNS resolves the _sipfederation and sip._tls SRV records to the external face of the edge server. The edge server functions as it should for remote users and mobility.
I have tried to follow these instructions to the letter three times over to no avail.
http://y0av.me/2014/01/07/lyncum365/
Neither Snooper or Event Viewer show any particular issue, though when I try to dial out to voice mail I will get one to two rings and then 5 seconds of silence a fast busy, and finally "Call Unsuccessful".
When checking the firewall logs I notice a seemingly random 10.x.x.x address being sent to the firewall by the external leg of the edge server. Wireshark captures it as STUN packets on port 3478 being sent to port 3478. These are being dropped by our firewall.
I believe them to be RTP packets but I do not know if this is normal behavior. Has anyone any ideas?

My mistake. Here is the snooper result.
TL_INFO(TF_PROTOCOL) [edge\edge]0C4C.05E4::06/18/2014-15:43:34.153.0000000C (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265)) [3770767507]
Trace-Correlation-Id: 3770767507
Instance-Id: 2E5A
Direction: incoming;source="external edge";destination="internal edge"
Peer: exap.um.outlook.com:5061
Message-Type: response
Start-Line: SIP/2.0 488 Compression algorithm refused
From: sip:sip.domain.net;tag=08FB9ED133BA396696FE6546EA6F3031
To: sip:exap.um.outlook.com;tag=B8FFE4E9267ED6ECB78ADCC60126B53F
Call-ID: 66602CE1F9980BFA94AD
CSeq: 1 NEGOTIATE
Via: SIP/2.0/TLS 10.11.11.23:50752;branch=z9hG4bK2132316E.5B3AF52DE2753A36;branched=FALSE;received=207.46.5.9;ms-received-port=50752;ms-received-cid=60172700
Content-Length: 0
Server: RTC/5.0
TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000D (SIPStack,NegotiateLogic::SetCompressionType:NegotiateLogic.cpp(2701)) [559249495]( 00000079B1274FB8 ) Compression type is now CompOff
TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000E (SIPStack,NegotiateLogic::ProcessCompressionResponse:NegotiateLogic.cpp(2217)) [559249495]( 00000079B1274FB8 ) Peer refused [488] our request for compression
TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000F (SIPStack,NegotiateLogic::AdvanceOutboundNegotiation:NegotiateLogic.cpp(910)) [559249495]( 00000079B1274FB8 ) Outbound negotiation sequence is complete
$$end_record
And finally..
TL_INFO(TF_PROTOCOL) [edge\edge0C4C.05E4::06/18/2014-15:43:49.379.0000002E (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265)) [962697980]
Trace-Correlation-Id: 962697980
Instance-Id: 2E61
Direction: incoming;source="internal edge";destination="external edge"
Peer: fe1.domain.net:61254
Message-Type: request
Start-Line: BYE sip:uminternal.um.prod.outlook.com:5066;transport=Tls;ms-fe=CO1PR02MB111.namprd02.prod.outlook.com SIP/2.0
From: <sip:[email protected]>;tag=b736386270;epid=9bcee72318
To: <sip:[email protected];opaque=app:voicemail>;tag=eced411395;epid=07C3F2A933
Call-ID: 4266a095bdef8280d67c7e7df58446fc
CSeq: 2 BYE
Via: SIP/2.0/TLS 10.10.10.25:61254;branch=z9hG4bKC848F11A.A88BCA6858661A50;branched=FALSE
Via: SIP/2.0/TLS 10.10.10.125:49156;ms-received-port=49156;ms-received-cid=401200
Route: <sip:edge.domain.net:5061;transport=tls;opaque=state:Si;lr>
Route: <sip:exap.um.outlook.com:5061;transport=tls;epid=07C3F2A933;lr;ms-key-info=AAEAARc45bIQE6UJAYvPAR8eV4QTvCH3EE2Kxtie7I2PMCSj-2aArKHP8dStYlJe-9jphIkz_mDEkCD_v8hY-mghQEHD6-F12E7E14YG-TJ2gEcQE0Bx2r_rDB3LrzRZzgQ0WVvxreLPWGI80elWF-xfbc_X3JE8mOR2OB9KQM8-e9WOjfq2kj6CnDGeL0yzgz4OB8zm-ao03Yo4gMZ-BpwaxC3BNuvvVDJo9wqrYftq_Z3MIVewWrqcDt5Td4vxCsMiXdwEqtEIRKVvQoqboleBJAyQl-C3qGgfEoSkUnApFuTSnQYRa4kbZ1iPaACpdKT-VTQGjc9HXfps48YJCsIXW0Ab_NSM2uvhUyw900men1ukXSmoZoWZbwqe5siuWVUcFoQl1h1Jcy4lCyZUfDZoqPzDioLqTk9iUmS8fa-PAJjsq72yGjVB_y1aJSxtHVsw7MiDqOGOPqT3dmF-sINkeyuokCy8UCf_cQHmEHwVzZLUJqaVccr3QNCLsBzhcWSypnC60ZZphOKuwl6RvUXWICPf0ubLTL2ppC3tWEgFdUUWOPVd84uGlMcqRLKGb1qrmpj8Nu6Lte7t5n2pMEBCfgAe79t4GO0C5KScdKT_XBM1iIBRXdNkPKHfSgC-wPQgRikdw7vRD-hOWlN5Lay7-zkQ4Ag6rauszFTAwbft99OieAOxKIsgYcxXxcG6;ms-route-sig=fiEMuzbN4_PyEz_I5gG3g8FtqNAonwgZCoRnOq-ByfYEtywTZp-Hk_eAAA>
Max-Forwards: 69
Content-Length: 0
ms-client-diagnostics: 22; reason="Call failed to establish due to a media connectivity failure when both endpoints are internal";CallerMediaDebug="audio:ICEWarn=0x40003a0,LocalSite=10.10.10.125:6735,LocalMR=10.11.11.23:51430,RemoteSite=10.27.46.15:5286,RemoteMR=207.46.5.80:54106,PortRange=1025:65000,LocalMRTCPPort=51430,RemoteMRTCPPort=54106,LocalLocation=2,RemoteLocation=2,FederationType=0"
$$end_record

Lync 2013 on RDP

Similar Messages

Maybe you are looking for