Jan Gehrke Posted July 12, 2021 #1 Share Posted July 12, 2021 I got the following scenario: People in our company use a headset when working at their workspace/computer and carry around a DECT phone, when moving around the company. A lot of times people accept a call while not being at their workspace (maybe they were just getting a coffee), but will proceed to move to their workspace after accepting the call with their DECT phone. They asked time and time again for a way to transfer the call from their DECT phone to their headset for comfort. Which doesn't seem possible from a technical standpoint, transfering calls between separate devices. I then figured: Well this could be solved easily. Why not transfer the call into a queue and have the queue call you back? I created a dummy user with an internal number and created a GSE setup for him with a queue. Now if you wanted to transfer the call to yourself, all you had to do is redirect it to the dummy. Technically it works. Problem is, I can't manage to read the number of the person that redirected the call. I can only get the number of the original caller and the number of the dummy user that received the call in order to process it via call routing. It doesn't appear to be stored anywhere easily accessible in the API. Does someone know a way to receive the number of the person that transfered the call? Or, alternatively, has a more clever solution for my problem in the first place? Thanks a lot Link to comment Share on other sites More sharing options...
Most Valued User Solution SvenS Posted July 12, 2021 Most Valued User Solution #2 Share Posted July 12, 2021 just dial ##70* and all other logged on devices will ring. https://help.swyx.com/cpe/latest.version/Client/Swyx/en-US/index.html#page/help/Appendix_FeatureCodes.html# Link to comment Share on other sites More sharing options...
Jan Gehrke Posted July 15, 2021 Author #3 Share Posted July 15, 2021 Thanks for the reply SvenS. I wasn't aware a function like this exists, that's actually very handy. Unfortunately I feel like the process of connecting a call with this is a bit too difficult for most users in this company, since it requires you to call yourself on another line, take that call and then connect the original call. Directly connecting the call to ##70* does unfortunately not work with our setup. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now