Skip to main content

Hello, we have implemented a simple auto-dialer which uses the CallOut api to initiate a call on a specific device. It works great for any hardware phones that we have, but we are wondering if there's a way for it to work with softphones too? I got it working with the RingCentral Phone desktop app, but it doesn't appear to work with either the regular RingCentral desktop or mobile apps, or the RC Phone android app.

Basically, the issue is that they never appears in the list of devices (using RestClient.Restapi().Account().Extension().Device().Get() ), or it always shows as offline. Is there something simple i'm missing, or is what i'm trying to do not possible?

Thanks in advance!

Andy

Hi Andy,

Sorry for this long delayed response.

The RC mobile apps and the RC Desktop app do not register a device id so that you cannot find it from the extension device list. This is the current issue w/o a solution. I will work with the eng. team to see how we can overcome this and update you once I get a solution.

Hi, is there maybe an update on this post?

I too would like an update on this. Obviously with so much of the workforce working remotely and using the RC Desktop app on their laptops, the support for CallOut from the app rather than a hard phone is imperative for the API to even provide the most basic value.

Unfortunately, it is still unsupported for the RC mobile and desktop app. For desktop environment, all you can do right now is to install the RingCentral Desktop phone app (soft-phone) and you can make a call-out from that device.

@Phong Vu

I was wondering if there is an answer to this yet? (To get the device id of the desktop app). When the RC desktop app makes calls then we see its device id in the event output, so we can find out the id by that method. And using the id (after we found it in the events) can then be used in CallOut. But waiting for an event is not exactly a reliable method.

Unfortunately, the RC desktop app, RC mobile app and other WebRTC phone apps still do not register their dynamic device id. The only way to get the device id of those apps is to use that weak workaround solution. We are still working on a solution for this but at this point in time, I have no ETA yet.

Following the recent blog post on the unified app improvements, does the RC app now support deviceID ?


https://www.ringcentral.com/us/en/blog/ringcentrals-redesigned-app/



Unfortunately, it is still not supported.

The only workaround solution is to implement an app "setup" step. The app setup requires the user to use the RC app to make an outbound call to any number and the user can hangup when the call is ringing (or even before ringing). Your app need to subscribe for the telephony/sessions event notification. You will catch the notification of that outbound call and you can detect the device id from the "from": { "deviceId": "xxxx" }

However, the device id will be different if the user closes the browser tab (if the browser app is being used). Or close and restart the RC app desktop! So one has to build a logic to setup and update the dynamic device id.

Any chance support has been added for this, I tried your workaround just now and that does work. But can’t you implement a way to get the device ID even if it changes, just as long as the ringcentral app is online? This should be basic functionality in the API, to place calls out to specific softphones

Any chance support has been added for this, I tried your workaround just now and that does work. But can’t you implement a way to get the device ID even if it changes, just as long as the ringcentral app is online? This should be basic functionality in the API, to place calls out to specific softphones

Unfortunately, this is still not supported.

Can you elaborate on the work around? I'm trying to build a click to dial that dials from the softphone, is this possible?

Reply


Terms & ConditionsCookie settings