- Joined
- Sep 2, 2020
- Messages
- 10
- Reaction score
- 2
We have users who are attempting to use the ATT transfer function to talk to the destination extension before transferring. Users process: on their Grandstream GXP2135 phones, they are answering call -->Selecting transfer --> inputting extension #-->hitting ATT transfer soft key.
When the user is available, it acts accordingly where the destination answers, verifies the info, and originating user completes the transfer.
However, when that same user is busy or away, it goes directly to VM with no way for the originating user to recover the call. These are handset users only, so there is no WebClient to verify info with prior to attempting the transfer.
Is there a config on the system that can help with bouncing call back on ATT transfer if the extension is in busy, away, or dnd status?
Our System Notes:
When the user is available, it acts accordingly where the destination answers, verifies the info, and originating user completes the transfer.
However, when that same user is busy or away, it goes directly to VM with no way for the originating user to recover the call. These are handset users only, so there is no WebClient to verify info with prior to attempting the transfer.
Is there a config on the system that can help with bouncing call back on ATT transfer if the extension is in busy, away, or dnd status?
Our System Notes:
- 3CX Version: Professional Standard 16.0.9
- Server OS: Linux
- Is the 3CX Server Hosted and where?: Hosted Server in our Data Center
- IP Phone: Grandstream GXP2135 Version 1.0.11.35
- Provisioning Method: SBC