- Joined
- Jun 22, 2021
- Messages
- 8
- Reaction score
- 1
Hello everyone,
I'm reaching out to the community for some assistance regarding a recent issue we've encountered following an upgrade of our phone system to version V20. Since this upgrade, we've been experiencing significant problems with the attended transfer functionality on all of our SNOM IP Phones from the 7* series.
Previously, when we received a call, it was straightforward to transfer it to a colleague by simply searching for their name in the company phonebook or using the BLF. However, post-upgrade, this functionality seems to be disabled. Now, the only way to perform an attended transfer is by manually entering the extension number of the person to whom the call is being transferred. Phonebook and BLF are transfering unattended.
This change has significantly impacted our workflow and efficiency. We are keen to find out if anyone else has encountered this problem and, more importantly, if there is a known solution or workaround.
Any advice, insights, or suggestions would be greatly appreciated. We're also open to recommendations for alternative methods or settings adjustments that could restore the previous functionality.
I'm reaching out to the community for some assistance regarding a recent issue we've encountered following an upgrade of our phone system to version V20. Since this upgrade, we've been experiencing significant problems with the attended transfer functionality on all of our SNOM IP Phones from the 7* series.
Previously, when we received a call, it was straightforward to transfer it to a colleague by simply searching for their name in the company phonebook or using the BLF. However, post-upgrade, this functionality seems to be disabled. Now, the only way to perform an attended transfer is by manually entering the extension number of the person to whom the call is being transferred. Phonebook and BLF are transfering unattended.
This change has significantly impacted our workflow and efficiency. We are keen to find out if anyone else has encountered this problem and, more importantly, if there is a known solution or workaround.
Any advice, insights, or suggestions would be greatly appreciated. We're also open to recommendations for alternative methods or settings adjustments that could restore the previous functionality.
