Share your ideas with us
Make sure to check out our terms of use and how to submit and vote for products ideas
Currently, when a call comes into our main line, the caller ID is shown. This is extremely helpful when receiving a call. However, if the call is received by a receptionist (or the wrong person) and is immediately forwarded to another extension, the original caller ID is lost and replaced by the receptionists extension name/number. The original caller ID is now lost, meaning the name and/or number of the original caller is gone from view. It would be extremely helpful to keep the original caller ID on a simple transfer.
Product Line | RingCentral Phone |
Hello everyone, this has been implemented in 22.3.1. This version of the app was rolled out to all accounts over 8/25-8/31. No additional action is required to initiate the feature on the app, please confirm you are on 22.3.1.
This feature allows for caller ID to transfer in these scenarios.
Warm/Consultative Transfer:
- Incoming call from PSTN/RC # to RingCentral and transferred to RC number
Blind Transfer:
- Incoming call from PSTN/RC # to RingCentral and transferred to RC number
- Incoming call from PSTN/RC # to RingCentral and transferred to RC voicemail
The feature requires the following endpoints to work successfully. This applies to both the user invoking the transfer as well as the user who is the destination of the transfer.
Desk phones: Any Poly, Avaya or Unify models.
RingCentral App: Version 21.4.30 or later
RingCentral Mobile App: Version 22.1.10 or later
RingCentral Phone App: Version 22.2 or later
This feature does not work with Cisco or Yealink phones.
This feature has not been formally tested on Mitel phones, it may or may not work.
What is the update with getting this function to work with Yealink phones? We previously had Intermedia and this feature worked just fine.
Please work with Yealink and provide update asap. We have lots of unhappy outside reps who misses the original caller ID.
Please add this for Yealink phones. This is causing a lot of confusion within our company.
Why would you not make this work for every model phone you offer?
Please add Yealink. We just signed up with RC and didn't know Yealink was excluded from Caller ID transfers.
Please add this to Yealink phones.
Hi, Team
We are hoping that this feature once *implemented this August, would extend to MS Team and PBX platforms.
Thank you!
Hi, Team
We are hoping that this feature once implement this August, it would extension to MS Team and PBX platforms.
Thank you!
Actually, this feature does work for Yealink phones. We currently use the T46S and T54W phones. We previously had Intermedia as our phone provider and the original caller ID was saved when the call was transfered. Please request to have Ringcentral update their system.
This was working for us, using Poly phones. Recently, it has stopped working. No setting changes have been able to bring it back.
For people using Yealink phones; we have found a solution that appears to be working for us. On either the phone's web portal or YMCS change the setting for Caller ID Source to "PAI-RPID-FROM". If this could be implemented by RingCentral to be the default for all users that would resolve this issue.
I just figured out that on the Mitel Phones if you press transfer then manually enter the extension number then transfer again the caller id will show up. The issue is in using the soft keys to transfer. Sounds like a programming issue on RingCentral's part. Mitel worked way better than RingCentral's system.
This still doesnt work for the Mitel Phones - any idea when this will be implemented?
Though this indicates that it works for Warm/Consultative Transfer, it does not. We are on Version 22.4.21 and when we process a Warm/Consultative Transfer the outsider caller ID is lost and replaced with the caller ID of the internal person. I have a case open, since October, and now am being told it is not a functional feature.
Need this for Warm/Consultative transfers on Yealink phones please.
Any updates on if this will ever be implemented for Yealink phones?
Will this ever be implemented for Cisco phones? We have all Cisco phones and really need this feature.
I have the same questions about forwarded voicemails. Right now when our receptionist (Polycom VVX250) receives a voicemail, it contains the inbound Caller ID. But when she forwards that voicemail internally to another extension, the Caller ID becomes her own extension, which is not especially helpful.
I see that someone else new to Ring Central and the Yealink phone is having the same issue are. We just started with Ring Central 3 weeks ago. Support hasn't told us that this basic function doesn't work with the Yealink phone. A phone that they quickly recommended to us. The sad thing is that I had to read about in in the above note. WHAT IS RING CENTRAL GOING TO DO TO ENGINEER THIS BASIC FUNCTION TO WORK?
We are new to RingCentral (Migrated from Mitel) why is this not a feature on all phones? We have yealink phones and when a call is transferred it only shows the person who transferred the call to you not the caller on the other line. When will this feature be implemented for yealink phones???