Issue: Skype for Business Client Will Not Perform Transfer

This one was brought up on the TechNet forums by Igor Kravchenko and others.  MVP Richard Brynteson ( and has brought it to Microsoft’s attention previously, so they are aware of the issue though I haven’t seen any word on when or if it will be fixed.

The issue itself is when transferring a call with the Skype for Business UI, if you search for a contact, right click, and try to choose the number or voicemail you’d like, nothing happens.  You’re still stuck in the transfer window.  This has left plenty of users confused and frustrated.

Figure 1: Wrong Way


There is however a proper way to perform the transfer and is another great example of why user training and enablement is so critical.  If you hover over or right click the contact’s picture, you’ll see a phone icon.  Clicking the phone icon gives you the same menu, however this time it’s functional.

Figure 2: Right Way


Hopefully that help if you were confused.  If you’re an admin who has or is considering switching to the SkypeUI interface, it’s worth your time to make sure your users are aware of this quirk before they struggle.


10 thoughts on “Issue: Skype for Business Client Will Not Perform Transfer

  1. Pingback: NeWay Technologies – Weekly Newsletter #160 – August 13, 2015 | NeWay

  2. Pingback: NeWay Technologies – Weekly Newsletter #160 – August 14, 2015 | NeWay

  3. Mark Vale


    This problem seems to exist with the Skype for Business 2016 app as well as the patched Lync client. In the 2016 client the problem is somewhat worse in that if you attempt to right click and choose a number to transfer e.g mobile number the Skype for Business client will crash and restart.


  4. Pingback: Skype for Business – 2o16 Client Still Cannot Transfer Calls Properly | Mark Vale's Blog

  5. Aaron


    This is exactly the issue we were experiencing! Our Skype for Business client was crashing when trying to transfer to a voicemail or it was sit there and do nothing!

    Your solution worked well!


  6. NerdBrick

    Thank you for posting this! SFB 2016 (16.0.6001.1068) still has this problem, but I’m sure we will see it fixed by MS soon. (fingers crossed)

  7. Anthony

    I still see this issue with SFB 2016 (16.0.4366.1000). Office 2016 Standard fully patched as well. See this on both x86 and x64 version off Office/SFB. The only difference is that the x86 version will point to a different .dll file then the x64 version on the application crash log. Anyone have any luck?

Comments are closed.