User Community Feedback

Also seeing this issue after migrating from Jabber. Jabber updated the caller ID as soon as caller B completes the transfer (even if it’s mid-ringing). Webex doesn’t.

The blindXfer softkey resolves this isssue and the far end sees the original callerID. It would be great if the Transfer key updated the callerID once the originator completes the transfer (during the ring).

Thank you Sanjay for your follow up comments!

I forgot to mention in my original comment, that User B presses Transfer, extension and then transfer again, thus completing the consult transfer. If user C didn't answer, the missed call appearing on user C's desk is User B's caller ID and not User A.

That's the way consult transfer works. Unless the transferor completes the transfer, there is not information available on the 2nd leg to update the caller-id information with the connected party. The use case above will be met when transferor completes transfer which the transfer-target is ringing. The very essence of consult transfer is to ensure that the transfer target is available before completing the transfer.

I have a similar issue. Let's say User A called into a company and User B Answered. User B wants to transfer the call to User C.
User B attempts the transfer but for some reason User C doesn't answer.
When User C return to their desk, they find a missed call from User B and not User A.

On behalf of Sanjay Sinha,

Can you please explain in detail the call flow of the transfer operation?

Call transfer operation is:
a) Initial Call Leg is active between user A & User B
b) User A wants to transfer user B to User C
c) User A puts call leg with user B on hold, dials User C's number
d) User A gets notification that User C is alerting. User C has not answered yet
e) User A completes transfer
f) Caller-Id on User C should be updated to show User B's number

If this is not happening, it is a defect. Please work with TAC to open a defect