The mentioned permission "VoIP Calling" in "Configuring your RingCentral app" does not exists for WebPhone

Hey Benjamin,
We currently have a passing public server application but we need to also use browser calling and don't want to manage two sessions/apps

Hey team, we've got a product to ship. Can you please have someone respond to our issues?

Janielle,

RingCentral does not grant "Direct RingOut", "Interoperability", or "Read Client Info" API permissions to any external developers. If you need the "Number Lookup" API Permission, you will need to provide us with a detailed use case about how you will use this API Permission in order for us to consider granting one of your applications this Advanced API Permission.

We will not make any further modifications to application(s) which have already been approved for production access. Our graduation process will not delay you in any way towards getting your updated application(s) approved for production. In fact, the moment your application has successfully achieved the requirements to apply for production and you have applied, just add a reply here letting me know, and if everything is in order I will graduate your applications immediately.

Following our best practices, which I outlined above, will not require you to manage two sessions/apps.  You will just change your configuration/environment files to use the new API keys. You should be able to do this in the Sandbox account for development with these applications as they have the necessary API permissions to do both RingOut and WebRTC voice calling:

Statflo Business Connect (Web Phone)
Statflo Business Connect (Web Phone) - Private App

Sincerely,
Benjamin

Thanks Benjamin.

I found out why we can't get the demo to work.

I followed the demo apps documentation, which says we needed to created an app and set it's Platform Type to Browser-Based. The problem is, is that a browser based app does not support Password Flow and the demo is setup to only use password flow.

You should ask the developers to fix the documentation or get them to add Password Flow as an authentication type for Browser-Based app

Is there another demo somewhere that shows how to use the Authorization Flow?

And in the mean time could you add the voip calling permission to an app called ringcentral-web-phone (Private, Mobile/Only) please,

Thanks,

Unfortunately we can't use https://github.com/ringcentral/ringcentral-js-cti-demo to test in-browser calling since it only supports ringout and URI

It would be nice to test with https://github.com/bdeanindy/ringcentral-webrtc-crm-demo but it requires Interoperability

How would you suggest we get started with in-browser calling without starting from scratch? We'd like to give something to our UI/UX team to work with while we develop against the sdk in parallel

Interoperability is no longer required to operate WebRTC, only VOIPCalling.

Interoperability is no longer required to operate WebRTC, only VOIPCalling.

Thanks Benjamin,

Do you know of any demo we can try that support in-browser calling using a public app?

Yes, the RingCentral for Google Chrome application on App Gallery does this very thing.
https://developers.ringcentral.com/app-gallery.html/app/312709020-312709020-7gufiGT3T3CCuCP37hMDaQ~K...