I've also tested this with Chrome/Windows and it works fine there. It seems to be limited to the Mac platform, which affects 90% of our users.
I tested on Mac 10.11.5, Chrome Version 53.0.2785.143 (64-bit), RingCentral
Release: 8.3.2.23993 (64-bit)
It works if you quit RingCentral app first before clicking the link. It doesn't work if RingCentral app is already running.
I think it's a bug. Please contact support:
There is a button under "General" settings that could help to activate the feature. When activated tab looks like this (see below). If it does and numbers are not added to the dial pad - it's likely a bug.
Have any of the suggestions given been helpful Nate?
If I'm completely honest - no. The only progress that has been made was due to involvement by our CEO, which resulted in an escalation to tier 3 support. We've exchanged 18 emails today and there still hasn't been resolution.
I appreciate that the team at RingCentral is actively involved in diagnosing the issue now, but it continues to be a pretty frustrating experience.
For some additional info, this appears to work on:
- OS-X 10.10.5
- Chrome 54.0.2840.71 (64-bit)
- RingCentral 8.3.2.23993
Scenario #1Using the provided number provided in the original post results in a "Cannot start call: Invalid phone number" error in the softphone for me because it starts with a '0':
rcmobile://call?number=08000988136
Scenario #2Using a valid number in the rcmobile URI scheme and a softphone that is logged in, the softphone will be brought to the foreground, the number populated and dialing started.
Scenario #3Using a valid number in the rcmobile URI scheme and a softphone that hasn't been launched, the softphone will be launched and brought to the foreground, the user will be prompted to login and the number populated. The user still needs to click dial as dialing doesn't start automatically after login.
SummaryScenario #2 appears to work as expected. In Scenario #1, the number should be updated and in Scenario #3, the behavior should be verified.
