After you upgrade to the Skype for Business for iOS application on your iPhone or iPad, you notice that +1 is now automatically added to the number entry field. This may cause a problem for customers who dial by using an extension or who have other custom dialing behaviors. 

For example, if customers are used to dialing 5000 to call an external DID, the dialing rules may not expect +15000, and therefore the call may fail for this user.

https://support.microsoft.com/en-us/kb/3101663

Candidate Behavior

First let's take a look at what this behavior actually looks like. If you have ever looked at UCCAPI client logs before this patch you noticed when negotiating final candidates for RTP you would see one port used for RTP and a separate port used for RTCP (Figure 1). Now with the introduction to the April client patch you only see a single UDP Port being used (Figure 2). If you look at the initial invite SDP we will still send with both ports (Figure 3) because we are unsure if the other side will be an updated client and understand the multiplexing RTP behavior.

Figure 1: RTP Candidates prior to the April 14^th, 2015 update

Figure 2: RTP Candidates with the April 14th, 2015 Patch installed - Multiplexing UDP port

Figure 3: Initial Invite SDP

Traffic Classification Impact (QoS)

If your customers are using a Lync/Skype for Business traffic classification solution to prioritize voice and video communication relying on the separate RTC or RTCP traffic¹, the solution will not work in new Lync 2013/Skype for Business 2015. Traffic might not be prioritized as expected and call quality might be impacted.  Please advise your network infrastructure providers and customers to re-evaluate their solution.

¹Using RTP or RTCP to classify the Lync/Skype for Business was never been recommended, tested, nor supported way of determining Lync media heuristics.

 Modalities Impacted

Currently only the following modalities are impacted, but more will follow with future updates:

• Joining an AV conference from a Lync 2013/Skype for Business 2015 client with the April 2015 update on a Skype for Business Server 2015 or Skype for Business Online.
• Two clients running Lync 2013/Skype for Business 2015 client with the April 2015 update.

Microsoft recommendation on Lync/Skype for Business traffic classification

Microsoft recommends two different ways to prioritize traffic:

• Using Quality of Service (QoS) by marking traffic with DSCP.
• Using network equipment that can leverage Software Defined Networking (SDN) and integrate it with the SDN API that Lync/Skype for Business offers

Both options are explained in detailed in the Lync Server Networking Guide.

Key Health Indicators - Analysis and Definitions Workbook - excel workbook that will help analyze and crunch KHI collection data.

Key Health Indicators Guide - this guide provides a sample process to operationalize, covers how to the use the Analysis and Definitions Workbook and provide next steps for remediating identified areas of concern.

http://www.microsoft.com/en-us/download/details.aspx?id=46895

KHI Feedback - LyncKHI@Microsoft.com

After researching this issue it had to do with permissions on the network profiles keys within the Registry.

Resolution:

http://blogs.technet.com/b/networking/archive/2009/06/19/missing-network-map-under-network-and-sharing-center-in-windows-vista-or-windows-server-2008.aspx

1. Right Click over the registry location: HKLM\Software\Microsoft\WindowsNT\CurrentVersion\NetworkList\ and then choose Permissions
2. Click Add
3. Please choose your computer for "From this location:" instead of your Active Directory domain, by clicking on Locations
4. Under "Enter the object names to select" type NT SERVICE\netprofm and then click on Check Names (make sure you type the username exactly how it's shown or it will not work)
5. Press OK to confirm
6. Once we have netprofm in place, click on Advanced as we need to specify special permissions (as per the below figure) for netprofm.

      7. Reboot the Workstation

Hope this helps!!!

Peer to Peer Media Establishment (Federated):  CustomerA IS federated with CustomerB. CustomerA initiates a call to CustomerB.

What are the possible call flow paths?

Calling Party<->CalledParty – this would more than likely only be possible if the users from CustomerA and CustomerB were sitting on the same network.

Calling Party<->CallingPartyEdge<->CalledPartyEdge<->CalledParty – FTURN – this is the most common scenario that would work.

Calling Party<->CalledPartyEdge<->CalledParty – if 50K port range was opened for the Called party Edge.

Calling Party<->CallingPartyEdge<->CalledParty – if 50K port range was opened for the Calling party Edge.

Conferencing Media Establishment (Non-Federated):  CustomerA is NOT federated with CustomerB. CustomerB creates a Lync meeting and sends it to CustomerA. CustomerA joins the meeting.

1. Customer A is joining using the Lync 2010 client – CustomerA (attendee) will connect to the AV Edge of CustomerB (organizer). So media will be from CustomerA to CustomerB either using the 50K port range or tunneled on UDP 3478 or TCP 443 just like a remote user connecting to the edge.
   1. Calling Party (attendee) <-> CalledPartyEdge (organizer) <-> AV MCU (organizer) – this would succeed if 50K port range was open.
   2. Calling Party (attendee) <-> CalledPartyEdge (organizer) <-> AV MCU (organizer) – tunneled via UDP 3478 or TCP 443
       
2. Customer A is joining using the Lync 2013 client - CustomerA will try to tunnel media traffic to its own Edge which will then do FTURN with CustomerB's Edge. If the FTURN is successful, the media will be between CompanyA's Edge and CompanyB's Edge on 3478 -3478 for audio and 50k source to 443 destination for desktop sharing. If FTURN fails then media between the Edge servers will try to use 50k range ports.
   1. Calling Party (attendee) <-> CalledParty (AV MCU) - Unlikely, but possible. The non-Federated user would have to be internal to the network where the conference is hosted
   2. Calling Party (attendee) <-> CalledPartyEdge<->CalledParty (AV MCU) – would mean the AV MCU can directly connect to 50k of the attendee Edge
   3. Calling Party (attendee) <-> CallingPartyEdge<->CalledPartyEdge<-> AV MCU (organizer) - FTURN – this is the most common scenario that would work.

Conferencing Media Establishment (Federated):  CustomerA IS federated with CustomerB. CustomerB creates a Lync meeting and sends it to CustomerA. CustomerA joins the meeting.

1. Customer A is joining using the Lync 2010 client – CustomerA (attendee) will connect to CustomerA's Edge then to CustomerB's (organizer) Edge and finally onto the MCU provisioned for the meeting from the organizer pool
   1. Calling Party (attendee) <-> CallingPartyEdge (attendee Edge) <-> CalledPartyEdge (organizer) <-> MCU (organizer)
2. Customer A is joining using the Lync 2013 client - CustomerA will try to tunnel media traffic to its own Edge which will then do FTURN with CustomerB's Edge. If the FTURN is successful, the media will be between CompanyA's Edge and CompanyB's Edge on 3478 -3478 for audio and 50k source to 443 destination for desktop sharing. If FTURN fails then media between the Edge servers will try to use 50k range ports.
   1. Calling Party (attendee) <-> CalledParty (AV MCU) - Unlikely, but possible. The non-Federated user would have to be internal to the network where the conference is hosted
   2. Calling Party (attendee) <-> CallingPartyEdge<->CalledParty (AV MCU) - Very unlikely. Would mean the AV MCU can directly connect to 50k of the attendee Edge
   3. Calling Party (attendee) <-> CallingPartyEdge<->CalledPartyEdge<-> AV MCU (organizer) - FTURN – this is the most common scenario that would work.
   4. Calling Party (attendee) <->CalledPartyEdge<-> AV MCU (organizer) - If attendee can connect directly to 50k of the AV MCU Edge

References –

Thomas Binder Edge Session - https://aka.ms/AVEdge

Scott Stubberfield Anonymous Join Blog - http://blogs.technet.com/b/scottstu/archive/2015/04/03/anonymous-join-from-skype-for-business-and-lync-clients.aspx

4098

Microsoft Lync Server 2013, Backup Service central management backup module has backup data that never gets imported by backup pool.

Backup data file: \\domain.com\Lync\ShareData\Pool01\1-BackupService-98\BackupStore\CentralMgmt\CMSMaster\Data\Backup.zip

Cause: Import issue in the backup pool. Please check event log of Microsoft Lync Server 2013, Backup Service in the backup pool for more

Resolution: Fix import issue in the backup pool

4071

Microsoft Lync Server 2013, Backup Service user store backup module has backup data that never gets imported by backup pool.

Backup data file: \\domain.com \Lync\ShareData\Pool01\1-BackupService-98\BackupStore\UserServices\PresenceFocus\Data\Backup.zip

Cause: Import issue in the backup pool. Please check event log of Microsoft Lync Server 2013, Backup Service in the backup pool for more information.

Resolution: Fix import issue in the backup pool

4052

Microsoft Lync Server 2013, Backup Service data content backup module has backup data that never gets imported by backup pool.

Backup data file: \\domain.com\Lync\ShareData\Pool01\1-BackupService-98\BackupStore\ConfServices\DataConf\Data\Backup.zip

Cause: Import issue in the backup pool. Please check event log of Microsoft Lync Server 2013, Backup Service in the backup pool for more information.

Resolution: Fix import issue in the backup pool

http://support2.microsoft.com/kb/2889929

3001551 - Lync 2013 crashes when it hits "LyncDesktopViewModel.dll"

3001545 - Issues occur when a user selects content in a history conversation window in Lync 2013

2998659 - Update to add recording and gallery view feature in a conversation in Lync 2013 basic

2996298 - Update adds a tab in the "Lync – Options" dialog box to manage instant message window related settings in Lync 2013

2996296 - Application sharing without audio or video is slow in Lync 2013 when bandwidth is low

2996294 - Recorded audio or video content is low-quality or incorrect in Lync 2013

2996293 - Update changes the default layout of a Lync 2013 instant message conversation window to narrow mode

2996292 - Unexpected time stamps appear when you paste messages from a conversation window in Lync 2013

2996290 - Memory leaks during a video call in Lync 2013 when camera's capture resolution is 720p or higher

2996289 - PSTN call is disconnected in Lync 2013 when you enable the media bypass setting

2996288 - Update enables viewers to automatically rejoin a desktop sharing session in a Lync 2013 conference

2996287 - Emoticons generated or typed text loses color or formatting when you paste text in an IM conversation in Lync 2013

2996286 - Update changes the format of an instant message that is copied from Lync 2013

2996285 - Error "Problem Event Name: APPCRASH, Application Name: lync.exe" when you view desktop sharing in Lync 2013

2996284 - A memory leak occurs when a remote user joins video conference in gallery mode in Lync 2013

2996283 - Audio or video call stops responding or disconnects in Lync 2013

2996281 - Online user can't sign in to Lync 2013 when another user has logged on to Windows by using a federated domain account

2996280 - Update enables Lync 2013 to collect telemetry data during a meeting or for a meeting join attempt

2996279 - Lync 2013 crashes or stops responding when it starts an application or accesses video-related features

2996278 - Error "Event Type: BEX" "Bucket Id: 81661691731" for Lync 2013 occurs

Debug-CsAddressBookReplication – PoolFqdn <value>

The value listed under Task Owner Fqdn will be the current Address Book master for the specified pool.