Hello. Self updating here in the event it helps others in the long run. We have a custom Salesforce Domain/URL. But Salesforce moved our org from one SF instance to another. There are very few settings that contain URL that need to be tweak when our Instance is changed....this is one of them. So this was not a RingCentral issue...it was a Salesforce setting issue.
Thanks for sharing @Jonathan O'Neill
@Jonathan O'Neill can you explain where you had to make this change? I also am having this issue.
We have a new SF org, which has been set up with the 'My Domain' thing turned on.
The interesting part is that when we first set up the Ringcentral integration in SF, the click to dial feature dose not work, even though the CTI Adapter URL is showing the correct format
https://MyDomainName--rcsfl.vf.force.com/apex/OpenCTIIndex
We ended up just re-type in the exact same CIT Adpater URl and save it in the call center, and it is now working properly... Really don't know why but just want to share this with anyone who is having the same issue when first time set up Ringcentra in SF.
This fixed my Click-to-Dial in Salesforce!! Here are the steps I took to resolve Disabled Click-to-Dial:
1. Click the gear icon
2. Click setup
3. Quick-find "Call Centers"
4. Locate RingCenntral and click "Edit"
5. Under "CTI Adapter URL," copy the address into a notepad. Change the URL based on the below example:
https://MYDOMAIN--rcsfl.visualforce.com/apex/OpenCTIIndex (this is the OLD, pre-populated URL)
https://MYDOMAIN--rcsfl.vf.force.com/apex/OpenCTIIndex (this is the NEW, changed URL)
6. Click "Save"
7. Kill all instances of your browser, reopen the browser, and log back in
8. Click to dial is now enabled!!
Thank you all so much for getting this solved! You guys rock, I've struggled with this for 2+ months. This is going to create a LOT of process efficiencies for my organization.
Is it an extra paid feature to enable click-to-dial?
Heads up to those that come here and do this - this did not work for me and it -broke- being able to use RingCentral in Salesforce so I had to change it back.
This fixed our org's issue exactly.
