We have updated to v20 U5 recently. We actively use mobile apps. Previously, when you pressed transfer button during the call, the call was put on hold, (the music on hold started playing) and then you could choose normal or blind transfer, then either dial or search for contact.
Now, on iOS app when you press Transfer button the call is placed on hold (music starts playing). And as soon as you choose one of the following options: Transfer or Blind transfer, the call returns back (music stops playing and you can speak to the caller) but you still can either dial or choose the contact. So, the caller is placed on hold 2 times: after the pressing the Transfer Button, and again after choosing another extension for transfer.
With Android users there doesn't seem to be this problem.
And in PWA the situation is the same: the call is not put on hold (no music is playing) at all after pressing the Transfer button. So the caller In the new Windows store app - it seems to work normally.
Is it a bug? Or how can we have a caller put on hold during the whole process of transferring?
Now, on iOS app when you press Transfer button the call is placed on hold (music starts playing). And as soon as you choose one of the following options: Transfer or Blind transfer, the call returns back (music stops playing and you can speak to the caller) but you still can either dial or choose the contact. So, the caller is placed on hold 2 times: after the pressing the Transfer Button, and again after choosing another extension for transfer.
With Android users there doesn't seem to be this problem.
And in PWA the situation is the same: the call is not put on hold (no music is playing) at all after pressing the Transfer button. So the caller In the new Windows store app - it seems to work normally.
Is it a bug? Or how can we have a caller put on hold during the whole process of transferring?
