Jan 06 2019 01:27 PM
Jan 06 2019 01:27 PM
I recently spoke about Call Park as a ‘coming soon’ feature. It seems that Microsoft has just pressed the ‘go’ button on it, as it’s now showing as a Launched capability, according to the Microsoft 365 roadmap:
There is also a Microsoft Support page, which explains how it works.
To place a call on hold on one device and pick it up from another device, also known as parking a call, click More actions in your call window and select Call park .
After you park the call, Teams will give you a unique code you can use to retrieve the call.
To retrieve a parked call, go to the speed dial tab, click Unpark , and enter the park code.
Jan 19 2019 10:10 AM
Thank you, this is great news! Will Call Park and Unpark be available for Teams telephones also?
Mar 18 2019 11:17 AM
@Tom Morgan One of my colleagues who was on the Microsoft Calling Plan and I migrated to Direct Routing--his default behavior for his "Hold" button actually parks the call rather than holding it. I'm trying to figure how to control that behavior, but I haven't seen anyone else report that issue. Any thoughts?
Oct 22 2020 12:03 PM
We have Teams Direct Routing setup using AudioCodes SBC appliance in Azure. The Call Park feature does NOT work on Desktop nor Web clients... From the Desktop client, it gives us a message "Call couldn't be parked" and from the Web client it puts the call On Hold instead of parking it... Though, it works fine when using the Teams mobile app; it parks calls just fine. I opened so many support tickets with MS and no success in figuring out the issue! I don't know what to do next... Any thoughts?
Jan 21 2021 10:44 PM - edited Jan 21 2021 10:46 PM
@Hacene Djelid, this is most likely an issue with Audiocodes SBC configuration.
I would get the person who manages your Audiuocodes to check what happens in the SIP ladder when a call is placed on a call park. It could be that the client is trying to place the call on hold but fails and disconnects the call.
We had to ensure a REFER rule pointing the traffic back to Microsoft to correctly place calls on hold.
Your AudioCodes admin should be able to find the issue by reviewing the SIP ladder and Syslog.