T5XW - Caller ID on Attended Transfer

[stevemiller]

We have the Yealink T5XW series phones deployed with our hosted offering. Is there a way to have the Original Calling Party Number to display as caller ID on attended transfers?

This is the behavior on blind transfers but during attended transfers, only the extension number of the transferring phone is displayed.

555-555-1212 calls the direct number of extension 4000. Extension 4000 answers the call and performs an attended transfer to extension 4100. When extension 4100 rings, the display shows "4100" instead of "555-555-1212".

[complex1]

(01-26-2023 05:56 AM)stevemiller Wrote:  We have the Yealink T5XW series phones deployed with our hosted offering. Is there a way to have the Original Calling Party Number to display as caller ID on attended transfers?

This is the behavior on blind transfers but during attended transfers, only the extension number of the transferring phone is displayed.

555-555-1212 calls the direct number of extension 4000. Extension 4000 answers the call and performs an attended transfer to extension 4100. When extension 4100 rings, the display shows "4100" instead of "555-555-1212".

Maybe this is the answer to your question?
http://forum.yealink.com/forum/showthrea...e=threaded

[stevemiller]

Thanks for the response complex1.

Yeah, I ran across that thread before posting.

I was hoping that wasn't the actual answer because if so, the answer is 'no' you can't update Caller-ID on completion of an attended transfer. And if that's the case, it's fine...I just wish someone from Yealink would answer the question directly and finally and just say that the behavior we want to see is officially unsupported.

Thanks again!

[complex1]

(01-26-2023 11:26 PM)stevemiller Wrote:  Thanks for the response complex1.

Yeah, I ran across that thread before posting.

I was hoping that wasn't the actual answer because if so, the answer is 'no' you can't update Caller-ID on completion of an attended transfer. And if that's the case, it's fine...I just wish someone from Yealink would answer the question directly and finally and just say that the behavior we want to see is officially unsupported.

Thanks again!

If you want an answer directly from Yealink, then I suggest submitting a support ticket.
https://ticket.yealink.com/