- Joined
- May 8, 2019
- Messages
- 19
- Reaction score
- 0
Good afternoon all,
We had a somewhat annoyed client on the phone yesterday after a strange occurrence on their recently installed 3CX v18 system.
When the system was installed after Christmas, they were using the v16 Desktop App and have been successfully for the past month. We had a need to upgrade them to the new v18 Desktop App and they were shown the process of attended transfers, several test calls made, etc. Call queues are set up, with two agents in the queue, to act as reception. 10 minutes after leaving site the client received a call, which needed to be transferred to an employee internally. They are stating they performed an attended transfer but that the caller was able to hear the conversation between reception and the internal employee. We've carried out several other tests and each time the attended transfer call is made, the original call always goes on hold.
When we look at the call details report for a call which worked fine we always get the below four steps (names and numbers redacted):

However, the call in question shows the below:

We don't have verbose logging turned on, given that the recommendation is only to have this on when replicating an issue (which we can't now replicate)
Has anyone else come across something similar? My suspicion is user error but given just the call report can't really pin down exactly what they may have done.
Thanks in advance
Adrian
We had a somewhat annoyed client on the phone yesterday after a strange occurrence on their recently installed 3CX v18 system.
When the system was installed after Christmas, they were using the v16 Desktop App and have been successfully for the past month. We had a need to upgrade them to the new v18 Desktop App and they were shown the process of attended transfers, several test calls made, etc. Call queues are set up, with two agents in the queue, to act as reception. 10 minutes after leaving site the client received a call, which needed to be transferred to an employee internally. They are stating they performed an attended transfer but that the caller was able to hear the conversation between reception and the internal employee. We've carried out several other tests and each time the attended transfer call is made, the original call always goes on hold.
When we look at the call details report for a call which worked fine we always get the below four steps (names and numbers redacted):

However, the call in question shows the below:

We don't have verbose logging turned on, given that the recommendation is only to have this on when replicating an issue (which we can't now replicate)
Has anyone else come across something similar? My suspicion is user error but given just the call report can't really pin down exactly what they may have done.
Thanks in advance
Adrian
