Voice - WebRTC FAQ

General

Is WebRTC traffic encrypted?

Yes. All WebRTC communication using RingCentral is encrypted in transit.

Does WebRTC include Call Control API support?

Yes. With WebRTC you can take control of the call with the following capabilities: initiate call, accept incoming call, adding callees via DTMF, hold / unhold, mute / unmute, park, flip, transfer, forward calls, start / stop recording and barge/whisper. These are documented in the ringcentral-web-phone WebRTC SDK.

Can I set Caller ID with WebRTC?

Yes. You can set Caller ID (CLID) using the ringcentral-web-phone WebRTC SDK. Just set the desired number as the fromNumber in the webPhone.userAgent.invite() method call.

Can WebRTC support area code matching for Caller ID?

Yes. You will need to supply your own area-code matching algorithm, but as long as you have matching numbers for use in your account, you can set the CLID as you wish. One approach is to store your area-code CLID numbers as Auto-Receptionist Company Numbers.

Are WebRTC call events captured via the event system?

Yes. Voice calls via WebRTC, RingOut and RingCentral endpoints are all captured via the event system. To check the presence status of an extension, you can call the extension presence API endpoint or subscribe to presence events via the subscription API or webhoks API.

Can a single browser-based app support both RingOut and WebRTC?

Yes. RingOut and WebRTC are two different ways to connect voice calls and both can be supported in single web app without authenticating each time. To do this using the RingCentral JavaScript SDK have the user authorize with the JavaScript SDK and then pass in the JavaScript SDK when instantiating the RingCentral WebRTC WebPhone SDK. An example implementaiton of this is the RingCentral for Google browser app.