Forum Discussion
Odd Issue with Response Groups and Calls Transfered to RG Causes S4B to Crash on Computer
We have a similar issue after the latest update, though not related to Response Groups but to Unassigned Numbers instead.
We have an Unassigned Number that transfers the call to an external number. When we dial this Unassigned Number from Skype for Business, lync.exe crashes when the transfer is initiated. Calling from a Common Area Phone works fine though.
Skype for Business on Windows:
- Call unassigned number
- On hold
- Crash
Common Area Phone:
- Call unassigned number
- On hold
- Transfer to destination number
- Ringing
The program lync.exe version 16.0.4666.1000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 53e4 Start Time: 01d3cb07db905394 Termination Time: 66 Application Path: C:\Program Files\Microsoft Office\Office16\lync.exe Report Id: c1e90ceb-db3e-49c4-bfa1-d8dcda1e7c16 Faulting package full name: Faulting package-relative application ID:
Stephan,
That does sound similar. We have not checked again after the March Microsoft updates and preparing to release April Microsoft updates, so we will check whether this is happening again. It does appear it worked for a while back in February or so after updates, but then broke with later Microsoft updates.
I am surprised no one else is reporting or seeing this issue. I think it is similar what you describe to what we are seeing. The callers into the response group would be unassigned numbers that call into the response group and then transfer to another assigned number in the university where we see the S4B client on the computer crash; however, the call connects with where we are transferring the call, but the client crashes on the computer.
John