It seems odd that there has to be a specific manner in which a transfer is done for the external caller ID to follow the transfer. Logic would suggest that when you push the transfer button, the caller ID data will go with the transfer being at "warm" (speak with the receiving party before transferring) transfer or a "cold" (just transferring without speaking to the receiving party) transfer. Having to use the "##" option to transfer, which was not identified in any documentation that I could find to be the way to transfer, is greatly inconvenient. Upon learning about the "##" manner of transfer, it was told to me that this manner is for "cold" transfers.

As I have mentioned, the vast majority of calls being transferred in our organization are calls that first go to the receptionist and then are transferred to the appropriate person. The receptionist used the transfer button on the T54W device, but the external caller ID data never followed the transfer (warm or cold). When I told the receptionist about the "##" manner to transfer (only available for "cold" transfers), the external caller ID data followed. The difficulty with this is that "warm" transfers are preferred, that way if the receiving person answers the transfer and speaks to the receptionist but identifies that they cannot take the call at that moment, they can let the receptionist know to send them to voicemail.

Having used various analog phone systems throughout the years, both making and receiving transfer calls, it is surprising that the RC transfer feature doesn't seem to have the capabilities that its predecessor had. Caller ID data doesn't follow the transfer unless done in a specific, non-traditional manner, warm transfers cannot be "rescinded" (connected but declined by the receiving person to have the call put through - the transferring party takes the call back to either assist or offer voice mail), and the transfer feature on the desk phone device is rendered unnecessary because to transfer with the caller's ID data the non-traditional "##" cold transfer manner has to be used.

I appreciate the continued dialogue about this and hope that there can be a resolution to the issue that maximizes the efficiency of both the RC system and the desktop phone device (in our case, the Yealink T54W).