Skip to main content
Solved

Where to find DeviceID of RingCentral App. (Not the softphone)

  • July 14, 2020
  • 14 replies
  • 2531 views

Hello,


I am able to find the all of the DeviceID's assigned to an extension by calling this endpoint:

https://platform.devtest.ringcentral.com/restapi/v1.0/account/accountId/extension/extensionId/device


I can then use these DeviceID's to place a call using my chosen device by calling this endpoint and supplying the DeviceID:

https://platform.devtest.ringcentral.com/restapi/v1.0/account/accountId/telephony/call-out


My question:

How do I find the DeviceID of the RingCentral App?

https://www.ringcentral.co.uk/desktop-app.html


The /extension/~/extensionId/device EndPoint only returns the ID's for Softphones and Hardphones


Thank you


Best answer by PhongVu

Unfortunately, right now the RingCentral desktop app and the RingCentral mobile app do not register their device id. Thus, you cannot get the device Id of those "phones".

I have not further info as when or if we are going to support this. But once I have the info, I will be more than happy to share with developers.

14 replies

PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • Answer
  • July 15, 2020

Unfortunately, right now the RingCentral desktop app and the RingCentral mobile app do not register their device id. Thus, you cannot get the device Id of those "phones".

I have not further info as when or if we are going to support this. But once I have the info, I will be more than happy to share with developers.


  • Author
  • The First Step
  • July 15, 2020

Hi @Phong Vu,


Ok, thanks for clarifying that


It's my understanding that the Softphone is slowly being phased out, and we are encouraged to switch to the RingCentral Desktop App https://www.ringcentral.co.uk/desktop-app.html

If we switch to the desktop app, this will render many functions of the API useless, am I right?

Will it ever be possible to use the CallOut EndPoint with the Desktop App?


Thank you



This type of similar query is already in the forum.

For reference: https://forums.developers.ringcentral.com/questions/10052/callout-using-mobiledesktop-app.html


Are the API limitations for each of your products documented?

This is obviously critical information that our clients would need before we could sell a custom solution.


  • Author
  • The First Step
  • August 16, 2021

Hello RingCentral,

With the latest email regarding the EOL of the RC Meetings app we are forced to switch the the RC unified app, has the issue regarding the lack of DeviceID been resolved?


Thank you


@Phong Vu


PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • August 16, 2021

Unfortunately, the RC unified app still does not support device id. But I am not sure how this is related to the EOL of the RC Meetings app? Do you need the device id to make a call-out using API? Let me know your use cases.


  • The First Step
  • November 5, 2021

I'd be interested in following this as well. I'm attempting an integration between RingCentral and another cloud system, and I've found that the users must have the RingCentral Phone app installed in order to present a deviceID to get a handle on and use MakeCall. If we're being pushed to use the new unified app, which doesn't have a deviceID, this is going to have a major impact on the way the company does business


Has the status of this changed at all? It would be really useful for our users if we could expose the RC mobile app as a device for them.


PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • January 22, 2024

Sorry, still no support for this because of the dynamic device id from WebRTC app.


  • New Participant
  • July 29, 2024

Any change in this?


  • Participating Frequently
  • May 19, 2026

With the notifcation that the RingCentral Phone desktop app has been retired, can we get the deviceId for theunified desktop app? How do we use the CallOut endpoint now?

 

https://platform.ringcentral.com/restapi/v1.0/account/accountId/telephony/call-out

 


PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • May 20, 2026

With the notifcation that the RingCentral Phone desktop app has been retired, can we get the deviceId for theunified desktop app? How do we use the CallOut endpoint now?

 

https://platform.ringcentral.com/restapi/v1.0/account/accountId/telephony/call-out

 

A new solution will be available soon. I will let you know when it’s released.


  • Participating Frequently
  • May 22, 2026

With the notifcation that the RingCentral Phone desktop app has been retired, can we get the deviceId for theunified desktop app? How do we use the CallOut endpoint now?

 

https://platform.ringcentral.com/restapi/v1.0/account/accountId/telephony/call-out

 

A new solution will be available soon. I will let you know when it’s released.

 

 

Thank you, hopefully it will be released soon.

Are there any interim solutions or new API endpoints available that will allow us to contnue our CRM click-call functionality? We use the deviceId to set the correct outbound caller Id, then place the call.


PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • May 22, 2026

With the notifcation that the RingCentral Phone desktop app has been retired, can we get the deviceId for theunified desktop app? How do we use the CallOut endpoint now?

 

https://platform.ringcentral.com/restapi/v1.0/account/accountId/telephony/call-out

 

A new solution will be available soon. I will let you know when it’s released.

 

 

Thank you, hopefully it will be released soon.

Are there any interim solutions or new API endpoints available that will allow us to contnue our CRM click-call functionality? We use the deviceId to set the correct outbound caller Id, then place the call.

If your CRM uses/embeds the RingCentral embeddable for voice calls, then it’s possible to use the embeddable device Id to implement the call out.


Another workaround solution is to make an outbound call manually and detect the device ID from the telephony session event. But this is a weak solution as the user first needs to make a call, and the dynamic device ID may change.